Vpc Interactions With Other Features; Configuring Vpc Peer Links And Links To The Core - Cisco nexus 5000 series Configuration Manual

Configuring Virtual Port Channels
On each vPC peer switch, you assign the same vPC number to the EtherChannel that connects to the downstream
switch. You will experience minimal traffic disruption when you are creating vPCs. To simplify the
configuration, you can assign the vPC ID number for each EtherChannel to be the same as the EtherChannel
itself (that is, vPC ID 10 for EtherChannel 10).
Note The vPC number that you assign to the EtherChannel that connects to the downstream switch from the
vPC peer switch must be identical on both vPC peer switches.

vPC Interactions with Other Features

Configuring vPC Peer Links and Links to the Core

Configure the command line interface by using a track object and a track list that is associated with the Layer
3 link to the core and on all vPC peer links on both vPC peer devices. You use this configuration to avoid
dropping traffic if that particular module goes down because when all the tracked objects on the track list go
down, the system does the following:
• Stops the vPC primary peer device sending peer-keepalive messages which forces the vPC secondary
• Brings down all the downstream vPCs on that vPC peer device, which forces all the traffic to be rerouted
Once you configure this feature and if the module fails, the system automatically suspends all the vPC links
on the primary vPC peer device and stops the peer-keepalive messages. This action forces the vPC secondary
device to take over the primary role and all the vPC traffic to go to this new vPC primary device until the
system stabilizes.
Create a track list that contains all the links to the core and all the vPC peer links as its object. Enable tracking
for the specified vPC domain for this track list. Apply this same configuration to the other vPC peer device.
Before You Begin
To configure a track list to switch over vPC to the remote peer when all related interfaces fail:
OL-25842-01
peer device to take over.
in the access switch toward the other vPC peer device.
Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.1(3)N1(1)
vPC Interactions with Other Features
111