Send document comments to nexus7k-docfeedback@cisco.com
7-4
Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x
OL-23435-03
Chapter 7 Configuring vPCs
Information About vPCs
the two linked Cisco Nexus devices appear as one device to a third device. The third device, or
downstream device, can be a switch, server, or any other networking device that uses a regular port
channel to connect to the vPC. If you are not using the correct module, the system displays an error
message.
Note We recommend that you configure the vPC peer links on dedicated ports of different modules to reduce
the possibility of a failure. For the best resiliency scenario, use at least two modules.
Beginning with Cisco NX-OS Release 4.2, if you must configure all the vPC peer links and core-facing
interfaces on a single module, you should configure a track object that is associated with the Layer 3 link
to the core and on all the links on the vPC peer link on both vPC peer devices. Once you configure this
feature and if the primary vPC peer device fails, the system automatically suspends all the vPC links on
the primary vPC peer device. This action forces all the vPC traffic to the secondary vPC peer device until
the system stabilizes.
Create a track object and apply that object to all links on the primary vPC peer device that connect to the
core and to the vPC peer link. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration
Guide, Release 5.x, for information on the track interface command.
The vPC domain includes both vPC peer devices, the vPC peer-keepalive link, the vPC peer link, and all
of the port channels in the vPC domain connected to the downstream device. You can have only one vPC
domain ID on each device.
In this version, you can connect each downstream device to a single vPC domain ID using a single port
channel.
Note Always attach all vPC devices using port channels to both vPC peer devices.
A vPC (see Figure 7-2) provides the following benefits:
• Allows a single device to use a port channel across two upstream devices
• Eliminates Spanning Tree Protocol (STP) blocked ports
• Provides a loop-free topology
• Uses all available uplink bandwidth
• Provides fast convergence if either the link or a device fails
• Provides link-level resiliency
• Assures high availability
To Next Page
Loading...
Need help?
General
