To manually finish an upgrade and continue rebooting nodes that were not rebooted,
complete the following steps:
-
Determine which partition was
booted for each node by entering the show slot detail
command.
The
include keyword can be used to simplify the output. In
the following example, only one of the Stanby nodes (Slot-3) was rebooted and is
running the newer software
version:
# show slot detail | include "information|Image|State|ver:"
Slot-1 information:
State: Operational
Current State: MASTER
Image Selected: primary
Image Booted: secondary
Primary ver: 31.3.1.22
Secondary ver: 31.3.0.106
Slot-2 information:
State: Operational
Current State: BACKUP (In Sync)
Image Selected: primary
Image Booted: secondary
Primary ver: 31.3.1.22
Secondary ver: 31.3.0.106
Slot-3 information:
State: Operational
Current State: STANDBY
Image Selected: primary
Image Booted: primary
Primary ver: 31.3.1.22
Secondary ver: 31.3.0.106
Slot-4 information:
State: Operational
Current State: STANDBY
Image Selected: primary
Image Booted: secondary
Primary ver: 31.3.1.22
Secondary ver: 31.3.0.106
-
Reboot any Standby nodes running the old software version individually,
ensuring that the rebooted node is operational before moving on to the next
node.
-
When all the Standby nodes are
running the new software version and the network has converged, reboot the
Backup node and allow it to go back “In-Sync” with the Primary node.
Note
After each reboot, allow a few minutes for the network to converge before
proceeding.
-
Failover control of the stack from the Primary node to the Backup node by
entering the run failover command.
When all nodes are running the newer software version, the
upgrade is finished. At this point, all nodes should have both their selected and booted
partitions set to the partition that contains the newer software version.