We are currently doing some testing on some EX4300 switches before replacing Cisco in our production.
Today I tested uppgrading with NSSU, and then rolling back. This is an importan feature in case the new version contains something that has a negative effect on our environment.
However the solution I came up with did not seem to work as well as I thought.
The current setup is 2 nodes in VC preprovisioned, both are possible RE
The procedure is now:
1. Start NSSU
2. NSSU completed, VC cluster is OK
We now have the current version on the primary slice, and the old on the backup slice.
We need to reboot each member on the backup slice
# Check which member is master and which is backup
show virtual-chassis
(let's pretend Member 0 is backup, and Member 1 is master)
# Request to reboot backup member on alternate slice which contains previous version
request system reboot member 0 slice alternate
(reboot successfull)
Here I get stuck
Member 0 comes back up, but is in Status: Inactive and in Role: Linecard
####
root@SW> show virtual-chassis
Preprovisioned Virtual Chassis
Virtual Chassis ID: 496a.6dfa.4bea
Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID Interface
0 (FPC 0) Inactive SN ex4300-48t 129 Linecard N VC 1 vcp-255/1/0
1 vcp-255/1/1
1 (FPC 1) Prsnt SN ex4300-48t 129 Master* N VC 0 vcp-255/1/0
0 vcp-255/1/1
{master:1}
root@SW>
####
Since it does not sync with Master I cannot roll back the master.
Does anyone know what I did wrong, and how I can change the procedure for it to work? To be able to rollback is an important step in a production environment.