Configuring Changes In Vpc Topologies - Cisco Nexus 5000 Series Operation Manual

Chapter 1 Virtual Port Channel Operations
S e n d d o c u m e n t a t i o n c o m m e n t s t o n 5 k d o c f e e d b a c k @ c i s c o . c o m
Enables restoring of vPCs in a peer-detached state after reload, will wait for 240
seconds (by default) to determine if peer is un-reachable
This example shows how to display the status of the auto-recovery feature:
switch(config-vpc-domain)# show running-config vpc
!Command: show running-config vpc
!Time: Tue Dec
version 5.0(2)N2(1)
feature vpc
vpc domain 10
peer-keepalive destination 10.193.51.170
auto-recovery

Configuring Changes in vPC Topologies

One of the challenges with vPC topologies is how to make configuration changes with minimum traffic
disruption. Due to the consistency check, the configuration made on one vPC switch could potentially
lead to consistency check failure and traffic disruption.
Beginning with Cisco NX-OS Release 5.0(2)N2(1), you can use the following procedure to make
configuration changes for Type 1 consistency check parameters on a Cisco Nexus 5000 Series switch.
We recommend that you perform the following procedure during a maintenance window because it might
reduce the vPC bandwidth by half for a short duration.
Note
A graceful consistency-check does not apply to dual-homed FEX ports. As a result, both switches keep
the port down for the duration of an inconsistency. Using the configuration synchronization feature
reduces the duration of the inconsistency.
To make configuration changes for Type 1 consistency-check parameters, follow these steps:
Step 1
Enable graceful consistency-check in a vPC domain.
Step 2
Enable the configuration synchronization feature on both vPC peer switches.
For details on using the configuration synchronization feature, see the "Configuration Synchronization
Operations" chapter.
Step 3
Perform all configuration changes in the switch profile.
When you commit switch profile configurations on the local switch, the configuration is also sent to the
vPC peer switch to reduce misconfigurations when changes are made on only one vPC switch and to
reduce the downtime because the configuration is applied rapidly. When there is a short mismatch
duration, a graceful consistency-check keeps the primary side forwarding traffic.
7 02:38:44 2010
switch# config term
switch(config)# vpc domain 10
switch(config-vpc-domain)# graceful consistency-check
switch# config sync
switch(config-sync)# switch-profile abc
switch(config-sync-sp)# interface Port-channel 100
switch(config-sync-sp-if)# switchport mode trunk
switch(config-sync-sp-if)# commit
Cisco Nexus 5000 Series NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1)
Configuring Changes in vPC Topologies
1-9