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
peer device to take over.
• Brings down all the downstream vPCs on that vPC peer device, which forces all the traffic to be rerouted
in the access switch toward the other vPC peer device.
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:
Procedure
PurposeCommand or Action
Enters global configuration mode.switch# configure terminal
Step 1
Enters interface configuration mode.
switch(config)# interface type slot/port
Step 2
Configures the track objects on an interface
(Layer 3 to core).
switch(config-if)# track track-id interface
type slot/port line-protocol
Step 3
Tracks the objects on an interface (Layer 3 to
core).
switch(config-track)# track track-id
interface type slot/port line-protocol
Step 4
Configures the track objects on a port channel
(vPC peer link).
switch(config)# track track-id interface
port-channel port line-protocol
Step 5
Creates a track list that contains all the interfaces
in the track list using the Boolean OR to trigger
switch(config)# track track-id list boolean
[OR | AND]
Step 6
when all the objects fail. or trigger a switchover
when any core interface or peer-link goes down
using Boolean AND.
Specifiecs the object number.
switch(config-track)# object number
Step 7
Cisco Nexus 5000 Series NX-OS Interfaces Configuration Guide, Release 5.2(1)N1(1)
76 78-26881-OL
Configuring Virtual Port Channels
vPC Interactions with Other Features
