How to Configure Stacking on Aruba Instant On 1960 Switches

[@CheekyMiner]

What if you add a third 1960, do you need to delete the aggregation, rewire then perform link aggregation again? I have the exact same setup. Thanks. Actually using the Aruba Portal since the switch is 1000's of miles away.

[@stevenschuurman6731]

Nice video 🙂 Why do you need to create the Link aggregation uplink on port 24? The stack is already connected with 4 ports and can be seen as 1 switch? Thx Steven

[@Joghurt-mit-der-Ecke]

This is no longer about the actual stack. Here, another device is connected to the switch that should be highly available. This can be another switch, for example. However, LACP must also be configured on the other device. If the upper switch fails, the lower switch continues operation without (or perhaps only with a brief) interruption. This is because if you have only connected a device to one of the two switches, it will fail if this switch fails.

[@tiagoolv5115]

do these settings work on the 1830? great video

[@NetworkingDojo_AION]

Hi Tiago, 1830s are not stackable so this config will not apply.

[@danielsan4777]

Can you tell me how to physically wire 4 switches for stacking? and which ports do i put on link aggregation?

[@danielsan4777]

any chance you can answer me?

[@andrearossetti4496]

Hi, is it possible to configure a LACP with 2 port of two different switch in stack using the cloud management?

[@sutty101]

Looking for this answer my-self. Setting up a 3 member stack of 1960's at the moment and I only seem to be able to make a LACP trunk from a single member from the cloud managment. But want it from Conductor and the 3rd member so I can link both to a Firewall LACP trunk for all VLAN's with device reduncancy on the switch side.

[@NetworkingDojo_AION]

Not at this stage, I believe this feature is being worked on and will be available in 2024.

[@pronettechnologies]

Hi Dojo, i have 2 aruba switches 1930, is it necesary to configure trunk port in order to get comunication between the VLANS in the switches?

[@NetworkingDojo_AION]

yes

[@breakingcustombc2925]

I'm assuming you don't have to tag the VLAN's on the stacking ports?

[@NetworkingDojo_AION]

No need to tag/untag VLANs on stacking links when configuring true stacking, all VLANs should be carried by default.

[@isuruamalka2258]

After the stacking what is use mgt ip.30 or 31.

[@NetworkingDojo_AION]

In this instance it will be .131. Management address will be the address of the primary stack member after stack has been formed.

[@ivalleysupport1151]

This does not work 100%. There is a bug in the firmware. Stacking works only when using the app, but after switching to local management, it wipes out the stacking configuration. Attempting to reconfigure the stacking as described in this video and after a reboot of the switches, all ports on all switches will start blinking red and never respond. Factory reset is the only way to get the switches back. Perhaps this worked a year ago when this video was released, but at this time, using 1 JL805A (1960 aggregate switch) and 3 JL809A (1960 access switches) connected as shown in the documentation (ring configuration A-B-C-D-A), it does not work without the cloud.😔

[@ivalleysupport1151]

BTW, this does not mean stacking does not work, it just means you must use the app (cloud configuration) for this to work. Unfortunately, this now creates a possible security hole in the network. Anything accessible in your network from an outside source is a potential security risk. The switches are currently running firmware 2.8.0, which is the latest at this time.

[@NetworkingDojo_AION]

You should only use app (cloud) or local management modes. You are not able to switch between these two without having to go back to factory defaults.