Upgrade Process for a vPC Topology on the Primary Switch
The following list summarizes the upgrade process on a primary switch in a vPC topology. Steps that differ from a switch upgrade in a non-vPC topology are in bold.
 Note |
In vPC topologies, the two peer switches must be upgraded individually. An upgrade on one peer switch does not automatically update the vPC peer switch. |
Procedure
|
Step 1 |
The install all command issued on the vPC primary switch triggers the installation upgrade. |
|
Step 2 |
The compatibility checks display the impact of the upgrade. |
|
Step 3 |
The installation proceeds or not based on the upgrade impact. |
|
Step 4 |
The configuration is locked on both vPC peer switches. |
|
Step 5 |
The current state is saved. |
|
Step 6 |
The system unloads and runs the new image. |
|
Step 7 |
The stateful restart of the system software and application occurs. |
|
Step 8 |
The installer resumes with the new image. |
|
Step 9 |
The FEXs are upgraded sequentially. |
|
Step 10 |
The installation is complete. |
What to do next
When the installation is complete, the vPC primary switch and the FEXs that are connected to the primary switch are upgraded. The single-homed FEXs and the dual-homed FEXs are now running the upgraded software.
Note |
The dual-homed FEXs are now connected to the primary and secondary switches that are running two different versions of the Cisco NX-OS software. The vPC primary switch is running the upgraded version and the vPC secondary switch is running the original software version. |
Feedback