To configure the system to monitor the track-list object that contains all the virtual port-channel (vPC) links to the core and to the vPC peer link when you are using only a single module for all links, use the track command. To return to the default, use the no form of this command.
no track track-object-id
Track-list object that you already configured.
vpc configuration mode
This command was introduced.
Beginning with Release 4.2, if you must configure all the vPC peer links and core-facing interfaces on a single N7K-M132XP-12 module, you should configure 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 can 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 to 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 PC peer device.
This command does not require a license.
This example shows how to put the previously configured track-list object into the vPC domain on the vPC peer device:
switch# configure terminal switch(config)# vpc domain 5 switch(config-vpc-domain)# track object 5