Objectives
The simulator ticks each one as soon as the network meets it.
On N1, show vpc consistency-parameters global and find the type-1 parameter that differs.
Make N2 match N1: spanning-tree mode rapid-pvst.
show vpc on N2: configuration consistency success, vPC 10 up, and SW3 bundles both uplinks.
Ping PC2 (192.168.10.20) from PC1.
Before you start
Global type-1 parameters (STP mode, STP-disabled VLANs, MST region, vPC system-priority…) apply to every vPC at once. On a mismatch the secondary suspends all its vPCs (graceful consistency check), so the domain looks healthy while half the uplinks sit idle.
Concept
vPC pairing rules: keepalive VRF, type-1 checks, peer-switch, peer-gateway
Two Nexus switches become vPC peers only when they agree: the same domain ID, a trunk peer-link that is up, and a peer-keepalive they have both heard. The keepalive runs in VRF management (mgmt0) unless told otherwise. Once paired, global and per-vPC type-1 parameters must match, or vPCs are suspended. peer-switch and peer-gateway make the pair behave as one switch for spanning tree and for routing.
Concept
vPC: one port-channel across two Nexus switches
A virtual port-channel lets a downstream switch or server bundle links that end on two different Nexus switches. The two switches form a vPC domain: they synchronise over a peer-link and check each other is alive over a separate peer-keepalive. Toward the access switch they act as one LACP partner, so both uplinks forward and spanning tree blocks nothing.
