Before You Begin
Power up replacement switch with no cables other than mgmt0 and console cable connected to the switch.
Copy the required Cisco NX-OS kickstart/system files into the switch bootflash.
If you have a backup of the switch configuration, copy it to new switch bootflash.
Enable the FEX pre-provisioning feature on the switch in the vPC topology.
Enable the configuration synchronization feature on the switch and apply all the switch profile configurations except for the sync peer destination IP address.
To replace a Cisco Nexus 5000 Series switch in a vPC topology, follow these steps:
Step 1 Boot the replacement switch.
The new switch comes up without a configuration. Ensure the software version is upgraded to match the existing switch.
Step 2 Enable FEX pre-provisioning for all single or dual homed Fabric Extender modules on the replacement switch.
Note Ensure that you unconfigure the system default switchport shutdown command on the replacement switch. Otherwise, when Fabric Extender Modules are coming online on the replacement switch, dual-homed FEX ports on the primary switch will flap causing traffic disruption.
Step 3 Configure the replacement switch as follows:
Note Before you configure the replacement switch using any of the following method, disable the vPC auto-recovery feature on both the vPC peers using the no auto-recovery command under the vPC domain. This is to ensure that there is no vPC role change because of the sticky bit feature, when the replacement switch is brought up. vPC auto-recovery feature is enabled by default in Cisco NX-OS release 7.x and later.
If the running configuration was saved offline, go to Step 4 to Step 10 to apply the configuration.
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 Step 11).
If neither condition is met, manually add the configuration and then go to Step 11.
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
command and the
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
command and the
show provision failed-config
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
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
Warning If the auto-recovery feature was not disabled in Step 3, ensure that either the vPC peer-keepalive 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
. Use the
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
Step 18 Connect the dual-homed Fabric Extender topology fabric ports.
Step 19 Connect the switch vPC ports.
Step 20 Enter the
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
command to ensure both switches are synchronized.
Step 24 If vPC auto recovery was disabled, enable auto recovery using the
command under vPC domain on both switches.
Replacing a Fabric Extender in a Dual-Homed Fabric Extender vPC Topology
Because the hosts behind a Fabric Extender in a dual-homed Fabric Extender vPC topology are by definition singly-connected, traffic disruption will occur for those hosts.
If the replacement Fabric Extender is a different model, the Cisco Nexus 5000 Series switch does not allow you to pre-provision a new type until you disconnect the old Fabric Extender.
To retain the configuration on both Cisco Nexus 5000 Series peer switches in the vPC topology, follow these steps.
Step 1 Save the configuration for the Fabric Extender interfaces to a file.
Step 2 Disconnect the Fabric Extender fabric ports and wait until the Fabric Extender is offline.
Step 3 Pre-provision the slot with the new Fabric Extender model.
Step 4 Modify the configuration file if necessary for the new Fabric Extender if the configurations are incompatible.
Note For vPC ports, this step might affect consistency.
Step 5 Copy the file to the running configuration.
Step 6 Connect the Fabric Extender fabric and host ports and then wait for the Fabric Extender to come online.
Step 7 Verify that all ports are up with the correct configuration.
Installing a New Cisco Nexus 2000 Series Fabric Extender
With pre-provisioning, you can fully configure the new Fabric Extender before the Fabric Extender is connected to a Cisco Nexus 5000 Series switch.
To install a new Cisco Nexus 2000 Series Fabric Extender, follow these steps:
Step 1 Pre-provision the slot with the Fabric Extender model.
Step 2 Configure the interfaces as though the Fabric Extender is connected.
Step 3 Connect the Fabric Extender and wait for it to come online.
Step 4 Verify that all configurations are applied correctly
Note The switch applies all configurations serially in a best-effort fashion when the Fabric Extender comes online.