Cisco Nexus 5000 Series Operation Manual page 16

Replacing a Cisco Nexus 5000 Series Switch or Cisco Nexus 2000 Fabric Extender
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
•
If the running configuration was not saved offline, you can obtain it from the peer switch if the
configuration synchronization feature is enabled. (Create a switch profile and then go to
•
If neither condition is met, manually add the configuration and then go to
Step 4
Edit the configuration file to remove the sync-peer command if using the configuration synchronization
feature.
Step 5
Configure the mgmt0 port IP address and download the configuration file.
Step 6
Copy the saved configuration file to the running configuration.
Step 7
Edit the saved configuration file and delete all commands between the configure sync command and the
commit command, including these two commands.
Step 8
Copy the new, edited configuration file to the running configuration again.
Step 9
Verify that the configuration is correct by entering the show running-config command and the show
provision failed-config slot command.
Step 10
If switch profile configuration changes were made on the peer switch while the replacement switch was
out of service, apply those configurations in the switch profile and then enter the commit command.
Step 11
Shut down all single-homed Fabric Extender vPC host ports.
Step 12
Connect the single-homed Fabric Extender topology fabric ports.
Step 13
Wait for single-homed Fabric Extenders to come online.
Step 14
Ensure the vPC role priority of the existing switch is better than the replacement switch.
Step 15
Connect the vPC peer keepalive link to the peer switch. Ensure that vPC peer keepalive link is
operational by entering the show vpc command.
If the auto-recovery feature was not disabled in
Warning
or the vPC peer-link comes up before the auto-recovery timer expires (default 240 seconds). If
this does not happen, the replacement switch will assume the vPC primary role (dual active). If
the vPC peer-link is restored in this state, there will be a vPC role change causing vPCs on the
peer switch to go down as the switch transitions to vPC secondary role. If required, with just
peer-keepalive link operational, reload the replacement switch one more time with all the other
interfaces still in the shutdown state.
Step 16
Ensure that the vPC role field is none established. Use the show vpc or show vpc role command to view
the vPC role. If the vPC role field displays Primary, then do not proceed with the replacement
procedure. Reload the switch to get the vPC role field to none established.
Step 17
Connect the vPC peer-link ports to the peer switch. Ensure that the vPC peer link is operational by
entering the show vpc command.
Step 18
Connect the dual-homed Fabric Extender topology fabric ports.
Step 19
Connect the switch vPC ports.
Step 20
Enter the no shutdown command on all single-homed Fabric Extender vPC ports.
Step 21
Verify that the replaced vPC switch and the Fabric Extenders on the replacement switch are online and
there is no traffic disruption.
Step 22
If you are using the configuration synchronization feature, add the sync-peer configuration to the switch
profile if this wasn't enabled in Step 3.
Step 23
If you are using the configuration synchronization feature, enter the show switch-profile name status
command to ensure both switches are synchronized.
Cisco Nexus 5000 Series NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1)
1-12
Chapter 1 Virtual Port Channel Operations
Step 3, ensure that either the vPC peer-keepalive
Step 11).
Step 11.