Overview
Upgrade or downgrade vPC peer switches in Nexus 9000 -R series, ensuring compatibility and minimizing traffic impact.
In vPC topologies, the two peer switches usually must be upgraded individually. An upgrade on one peer switch does not automatically update the vPC peer switch.
However, NX-OS Releases 7.0(3)F3(3c) and 7.0(3)F3(4) are not compatible with NX-OS Release 9.2(x) for vPC peer switches. Both vPC peers must be upgraded simultaneously to NX-OS Release 9.2(x) to avoid one switch running a 7.0(3)F3(x) release and the other switch running 9.2(x). Optionally, if the switches are being upgraded from NX-OS Release 7.0(3)F3(4), you can use the following procedure to minimize the traffic impact during upgrade.
This procedure not to be used on Broadcom or Cloudscale-based switches.
Procedure
| 1. | Switch A and B are running a NX-OS release. Switch A is the primary switch, and switch B is the secondary switch. On both the switches, use the copy r s command to save the running configuration. Example:
|
|
| 2. | Bring down the peer link (PL) on the primary switch. The secondary switch brings down its vPC legs. Example:
|
|
| 3. | Configure vPC auto-recovery under the vPC domain on the secondary switch. Enable vpc upgrade (exec command). Example:
|
|
| 4. | After Layer 3 routes are learned on the secondary switch, reload the primary switch with the new release image. The secondary switch takes over the primary role and brings up its vPC legs in approximately 5 seconds. Example:
|
|
| 5. | When the primary switch comes back up, the peer link on it is operationally up. Example:
For downgrade, reload both switches at the same time. |