We're kicking off 2020 by releasing our latest best practices guide — this time, we're covering VSF deployment and maintenance on the Aruba CX 6300 switch family. Deploy, maintain, and troubleshoot 6300 VSF stacks using either the Aruba CX mobile app or switch CLI.
As always, feel free to provide feedback or suggestions in this thread!
Thanks Matthew !
(the link on ASP don't work... redirect to HPE Internal Web site : https://asp.arubanetworks.com/downloads/documents/RmlsZTpkZjUxY2E5MC0yZDgyLTExZWEtOTBjNS03NzgwYTEwNTMzODM%3D )
Should it be possible to stack switches with copper cables? At least the mobile app doesn't seem to recognize other member if I use 1Gbps ethernet from ports 23 -> 24 and 24 -> 23.
Asking as I haven't received the proper DAC cables yet but would like to try VSF
Only the SFP56 ports can be used for VSF links.
Is there a 'unsupported-transceiver' command for 6300F :)?
Contacted today with our presales engineer and the answer is "not yet"
Am I reading it right that these new products do not have a method for an 'in service' or fast software upgrade when the switches are stacked in pair.. or am I missing something in the documentation/oversight in the documentation?
Yes no ISSU or fast software upgrade on 6300
My experience with 6300M VSF:
- Configure everything either manually or using the Mobile App
- Everything is working
- Remove power from the switches.
- Connect the switches to power
- Only master works; all others get stuck on boot.
What release ?
do you have open a cases to TAC ?
no need for TAC.
Copy running to startup
Tried both methods.
And as told, Master does have configuration. Hostname is set, vsf links are set, etc.
It's only the Slaves that do not keep the config. They get stuck on boot. If I CTRL+C the boot proceeds, but the switch config is empy.
Only way to recover the switches is to wipe to factory defaults (erase zeroise).
ok, thank you for such clarification.
Then, indeed, a case must be opened.
You need to do a "copy running startup" before power-off.
This is achieved on the CX mobile app here attached.
Yes, the configuration is saved.
Master config is intact after power-down / power-up.
Only secondary and slaves get stuck.
How did you save configuration before power-off ?
It was confirmed on this thread that the copper ports on the 6300 devices cannot be used to form the VSF link as the SFP56 ports are the only ones supported for such feature, however I would like to know if this restriction applies to the 6300M JL658A (use any of the SFP+ ports for VSF link).
Also, is it still recommended to have a "chain" topology in a 2 member VSF (I can inherit it from the guide "If the stack will contain more than two members, configure VSF link 2 as well:", however it is not specifically indicated).