vPC Upgrade and Downgrade Procedure 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, Cisco NX-OS Releases 7.0(3)F3(3c) and 7.0(3)F3(4) are not compatible with Cisco NX-OS Release 9.2(x) for vPC peer switches. Both vPC peers must be upgraded simultaneously to Cisco 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 Cisco NX-OS Release 7.0(3)F3(4), you can use the following procedure to minimize the traffic impact during upgrade.
vPC Role Although both vPC switches appear as a single switch to a downstream device, among themselves two vPC switches have clearly defined vPC roles: vPC Primary and vPC Secondary.
vPC roles are non-preemptive, which means a device can be configured as vPC primary, but operate as vPC secondary peer device. This can happen in this scenario:
When the original primary device fails, the secondary vPC device becomes the new primary device. When the system recovers itself, the previously primary device is now the secondary device and vice versa. vPC role defines which of the two vPC peer devices processes Bridge Protocol Data Units (BPDUs) and responds to Address Resolution Protocol (ARP) requests. vPC role also defines a set of actions to be taken by vPC primary and vPC secondary in response to vPC peer-link down situation.
VDC Properties Each VDC is treated as standalone device with limited resources Each VDC will have MAC address assigned to it which uniquelyidentifies a VDC in a network VDC 1 (DEFAULT_VDC) is the “Default Virtual Device Context”.Ports in sy...