The ArubaStack feature enables simplified management by presenting a set of Mobility Access Switches as one entity, and reduces the operational complexity of managing multiple redundant links between access and distribution layer switches. Since the ArubaStack appears as one network node, loop prevention protocols are not required.
An ArubaStack is a set of interconnected Mobility Access Switches using stacking ports to form an ArubaStack. A stacking port is a physical port configured to run the stacking protocol.
In some situation or during the replacement, the new switch were able to form a stacking with the Primary controller. But in some rare situation the new switch might got stuck in dormant state with reason as Version Mismatch [V]—This member’s version of ArubaOS does not match that of the primary member.
So in this situation we might need to upgrade and reboot the Single Switch along. So this article will explain how to upgrade and reboot the single switch alone.
Currently, all members of a stack must be running identical software release including maintenance and patch number (e.g. 7.1.x.y). Otherwise, the member will be in dormant state
If the version of a member does not match the primary, however it is running at least 7.1 release, the primary will be able to “see” the new member (with mis-matched software version) and user can simply upgrade the new member by copying over the image to the new member
If the version of the software on new “member” is not at least 7.1 (e.g. 7.0.2.0), then user must upgrade the unit by itself as it will not be visible from the stack primary.
Environment :
There may be instances where a user would want to “add” another member to an existing stack. For instance, the stack has three members (with member IDs 0, 1, and 2). Recommended procedure is as follows:
Upgrade the software image on the new member to match the primary if possible If the new member unit is not out-of-box (i.e. was part of another stack), “factory-default” the new member by using the following CLI command:
(ArubaS3500) #restore factory_default stacking
Add the new member to the stack (new member can be turned either on/off)
The new member will then obtain member ID 3 which is next available member ID
Once the member is added to the stack, all configuration related to interfaces 3/0/* will apply to the newly added unit.
Network Topology : Stacking Switch. Primary--Secondary--New Line card
To upgrade single Switch in Stacking:
(ArubaS2500-24P) #copy tftp: 10.1.1.1 ArubaOS_MAS_7.3.2.2_44718 ?
flash: Copy to the flash file system
member: Copy to a Stack member <-- We need to use this syntax and need to mention exact member which got stuck in "Dormant" state.
system: System Partition
usb: Copy to external USB
(ArubaS2500-24P) #copy tftp: 10.1.1.1 ArubaOS_MAS_7.3.2.2_44718 member: ?
<id> Number(0-7) or 'all' for all members
To reload single Switch in Stacking:
(ArubaS2500-24P) #reload ?
<member> Coldstart a particular member in stack.
local Coldstart the local switch
<cr>
To upgrade single Switch in Stacking:
#copy tftp: 10.1.1.1 ArubaOS_MAS_7.3.2.2_44718 member: 2 system: partition 1
To reload single Switch in Stacking:
(ArubaS2500-24P) #reload 2
ArubaS3500)# show stacking members
Stack: Active, Id: 000b866c31804e4e50d5
Member-id Role Mac-addr Priority State
--------- ---- -------- -------- -----
0 * Primary 000b.866c.6980 250 Active
1 Linecard 000b.866c.2cc0 128 Dormant [V] <--
[S] - Split
[V] - Version Mismatch
[D] - Depleted Slots
#copy tftp: 10.1.1.1 ArubaOS_MAS_7.3.2.2_44718 member: 1 system: partition
#reload 1