Wired Intelligent Edge

Greetings!

 

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!

Hi,

 

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"

Hi Matt

 

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?

 

Thanks

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

- Wait

- Only master works; all others get stuck on boot.

 

 

What release ?

FL.10.04.0030

do you have open a cases to TAC ?

no need for TAC.

Cli:

write memory

App:

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 ?

Has any progress been made with the app for VSF?  10.05.0030 and still not able to stack two new switches, using the SFP56 DAC interconnects.  As Ricardo said nearly a year ago, the configuration appears to work up until commit time.  Then the member switch times out and a failure message is presented.

After manually rebooting (power off/on), the secondary joins, but attempting to login using its console puts the admin in "member02" low-level console, rather than backup.  Rebooting with the DAC link disconnected results in the secondary not being able to complete the boot.

Stacking at the CLI seems to work as intended.

I've seen the same behaviour using the app with the 6200, and have configured them at the CLI successfully.

Feels like a TAC call coming on...

Solved - needed to define a secondary/standby.  Did that and things worked well.  Missed the checkbox in the app.  Can do this from the app by editing the member and checking the box, or using the CLI to declare which member is the standby member.

------------------------------
Timothy Leadbetter
------------------------------

Original Message:
Sent: Feb 21, 2020 06:42 PM
From: Ricardo Duarte
Subject: VSF Best Practices for the Aruba CX 6300 Switch Series

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

- Wait

- Only master works; all others get stuck on boot.