Administrator's Guide v4.1.1 Manual

NOTE
Because the fabric principal and multicast rood nodes have already been identified previously as
"even" nodes, we reload the "odd" nodes first, then the "even" nodes. In the example below, sw87
and sw81 are reloaded at the same time. Refer to Understanding traffic outages on page 130 for
details of the traffic outages that occurred at different phases of the process in the tested topology.
4. Wait at least 5 minutes for the switches (in our example sw81 and sw87) to come back up.
NOTE
The time required for the switches to come back up with the configuration replay complete depends
on the number of configuration lines that must be read. Refer to Understanding traffic outages on
page 130 for example traffic-outage times.
5. Wait at least 10 minutes for the fabric to converge and all back-end processes to be completed.
NOTE
At this point in the process, sw79 and sw86 are at 3.0.1c, while sw87 and sw81 are at 4.1.1.
6. Verify that all four nodes are part of the same cluster, by using the show fabric all command.
7. At this point, reboot all the "even" nodes, including the principal and the multicast root node. Refer
to Understanding traffic outages on page 130 for example traffic-outage times.
8. Wait at least 10 minutes for the fabric to converge and all back-end processes to be completed.
NOTE
At this point, all nodes are at 4.1.1.
9. Verify that all nodes have joined the fabric, by using the show fabric all and show vcs commands.
ATTENTION
Ensure that there are no traffic outages.
10.Verify that system health is as discussed in Step 4 of Preparing for the maintenance window on
page 125.
11.Evaluate the state of the upgrade process at this point. The upgraded firmware should have been
downloaded onto the primary partition, while the original firmware should be present in the second
partition.
12.To complete the process commit the firmware, by using the firmware commit command.
13.If an unexpected development occurs, you can roll back to the original firmware. Refer to Restoring
firmware in the VCS Fabric on page 131.
Understanding traffic outages
For example traffic-outage times as measured by various traffic-analysis tools, note the following.
1. Note the following traffic-outage times that occurred when the "odd" switches, sw87 and sw81, were
reloaded.
Understanding traffic outages
130 Network OS Administrator’s Guide
53-1003225-04