Wired Intelligent Edge

Hi,

We have one switch 2930M JL322A which we want to stack with the existing already stacked 2930M switches. We want the new switch to join as the member of the stack neither standby nor commander.

The existing switches has the software version of WC.16.04.0011 (2 switches) while the new switch has the software version WC.16.10.0002. My first question is that can we make all of them stacked together by keeping their existing version as it is (Existing stack version  WC.16.04.0011 and the new switch version WC.16.10.0002.) and will they work fine ?

Hi! VSF Members must run on the same ArubaOS-Switch version (e.g. WC.16.04.001 OR WC.16.10.0002), VSF doesn't admit some members to run on a newer/older Software version compared to the one of the VSF Commander (with the assumption that VSF Commander and Standby already share the same software version).

The new added VSF Member is going to be upgraded or downgraded to align its software version to the one used by the current VSF Commander.

My suggestion is: upgrade the actual VSF Stack to latest WC available (say WC.16.10.0011 or the like) and only then add the third Aruba 2930M (already updated and aligned or not)...it's a pity (and a danger) to run a VSF stack by using such old WC.16.04.

Hi Mate, the stacking technology is not VSF its BPS. 

https://help.central.arubanetworks.com/latest/documentation/online_help/content/switches/switch-stack/switch_stack.htm

And I dont have the option to first upgrade the stack and then add the new member. So can you please help me in this regard. Thanks 

Hi,

It is the same idea for VSF and BPS

we can try to add the new switch, it will be downgrade firmware

but i think it is better to upgrade actual firmware on the stack

Doesnt the switch auto-downgrade once connected with the stack ?

Yeah, sorry mate...was early morning and I missed the M at the end of Aruba 2930. So you're right...we're dealing with Backplane Stacking and not VSF (Frontplane Stacking)...but, as @alagoutte pointed out above, the principle is mostly the same.

You could:

(a) (down)grade the third switch you're going to add

(b) (up)grade the BPS Members and, consequently, (up)grade the third switch to (that is if you want to stay on the edge with the latest fresh new WC.16.10 software release)

(c) (up)grade the BPS Members to the actual version of software running on the third switch and, consequently, leave this third switch as-is.

IMHO working with WC.16.04 (on two switches) and WC.16.10 on the third you want to add is a no-go (and goes against any common best practices too)...for sure the third switch is going to be aligned with the first two to form a three members BPS.

So what you are trying to say that we have to downgrade first then add, but I read in the document that teh switch will downgrade automatically, isnt it the case ?

Mate, it will be downgraded (or upgraded) automatically...OR you can do it manually BEFORE you try to add it to the stack.

Either procedures are good: one happens automatically (I don't know if you like it that way or you like to have some sort of control over that), the other is not automatic (because you decide to do that in advance knowing the state of your stack and the state of the member you're going to add). For sure stack will check WHAT version the new member has and acts accordingly (alignment to version running on the current Commander).

hopefully this may answer your questions..go with the best practices

https://community.arubanetworks.com/t5/Wired-Intelligent-Edge-Campus/Backplane-Stacking-and-VSF-Best-Practices-for-ArubaOS-Switch/td-p/500559