Filter
Top Products
Per-VLAN Consistency Check
Beginning with Cisco NX-OS Release 5.0(2)N2(1), some Type-1 consistency checks are performed on a
per-VLAN basis when spanning tree is enabled or disabled on a VLAN. VLANs that do not pass the consistency
check are brought down on both the primary and secondary switches while other VLANs are not affected.
vPC Auto-Recovery
Beginning with Cisco NX-OS Release 5.0(2)N2(1), the vPC auto-recovery feature re-enables vPC links in
the following scenarios:
When both vPC peer switches reload and only one switch reboots, auto-recovery allows that switch to assume
the role of the primary switch and the vPC links will be allowed to come up after a predetermined period of
time. The reload delay period in this scenario can range from 240-3600 seconds.
When vPCs are disabled on a secondary vPC switch due to a peer-link failure and then the primary vPC switch
fails or is unable to forward traffic, the secondary switch re-enables the vPCs. In this scenario, the vPC waits
for three consecutive keep-alive failures to recover the vPC links.
The vPC auto-recovery feature is disabled by default.
vPC Peer Links
A vPC peer link is the link that is used to synchronize the states between the vPC peer devices.
You must configure the peer-keepalive link before you configure the vPC peer link or the peer link will
not come up.
Note
vPC Peer Link Overview
You can have only two switches as vPC peers; each switch can serve as a vPC peer to only one other vPC
peer. The vPC peer switches can also have non-vPC links to other switches.
To make a valid configuration, you configure an EtherChannel on each switch and then configure the vPC
domain. You assign the EtherChannel on each switch as a peer link. For redundancy, we recommend that you
should configure at least two dedicated ports into the EtherChannel; if one of the interfaces in the vPC peer
link fails, the switch automatically falls back to use another interface in the peer link.
We recommend that you configure the EtherChannels in trunk mode.Note
Many operational parameters and configuration parameters must be the same in each switch connected by a
vPC peer link. Because each switch is completely independent on the management plane, you must ensure
that the switches are compatible on the critical parameters. vPC peer switches have separate control planes.
After configuring the vPC peer link, you should display the configuration on each vPC peer switch to ensure
that the configurations are compatible.
Cisco Nexus 5000 Series NX-OS Interfaces Configuration Guide, Release 5.2(1)N1(1)
74 78-26881-OL
Configuring Virtual Port Channels
Per-VLAN Consistency Check