Licensing Requirements For Vpcs; Guidelines And Limitations - Cisco 7604-RSP720C-R Configuration Manual

Chapter 7 Configuring vPCs
S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m

Licensing Requirements for vPCs

The following table shows the licensing requirements for this feature:
Product License Requirement
Cisco NX-OS vPC requires no license. Any feature not included in a license package is bundled with the Cisco NX-OS
system images and is provided at no extra charge to you. For a complete explanation of the Cisco NX-OS
licensing scheme, see the Cisco NX-OS Licensing Guide.

Guidelines and Limitations

vPC has the following configuration guidelines and limitations:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
OL-23435-03
VPC peers can only operate dissimilar versions of NX-OS software during the upgrade or
downgrade process.
VPC peers running different version out of upgrade/downgrade period is not supported.
All ports for a given vPC must be in the same VDC.
You must enable vPCs before you can configure them.
You must configure the peer-keepalive link and messages before the system can form the vPC peer
link.
Only Layer 2 port channels can be in vPCs.
You must configure both vPC peer devices; the configuration is not sent from one device to the other.
To configure Multi-layer (back-to-back) vPCs, you must assign unique vPC domain ID for each
respective vPC.
Check that the necessary configuration parameters are compatible on both sides of the vPC peer link.
See the "Compatibility Parameters for vPC Interfaces" section on page 7-15
compatibility recommendations.
You may experience minimal traffic disruption while configuring vPCs.
The software does not support BIDR PIM or SSM on vPCs.
The software does not support DHCP snooping, DAI, or IPSG in a vPC environment; DHCP Relay
is supported.
The software does not support CFS regions.
Port security is not supported on port channels.
We recommend that you configure all the port channels in the vPC using LACP with the interfaces
in active mode.
Configure a separate Layer 3 link for routing from the vPC peer devices, rather than using a VLAN
network interface for this purpose.
Back-to-back, multi-layer vPC topologies require unique Domain IDs on each respective vPC.
When using vPC, we recommend that you use default timers for FHRP (HSRP, VRRP, GLBP), and
PIM configurations. There is no advantage in convergence times when using aggressive timers in
vPC configurations.
Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x
Licensing Requirements for vPCs
for information on
7-29