Before You Begin
Ensure that you enable pre-provisioning and the configuration synchronization feature on the switch in the vPC topology.
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 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:
- If the running configuration was saved offline, go to Step 7 to Step 13 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 14).
- If neither condition is met, manually add the configuration and then go to Step 14.
Step 4 If vPC auto-recovery is enabled, disable it on both vPC peers using the no auto-recovery command under the vPC domain. This is to ensure that there is no vPC role change when the replacement switch is brought up.
Note vPC auto-recovery is enabled by default in Cisco NX-OS release 7.x and later.
Step 5 Bring up the vPC peer keepalive interface. Ensure that vPC peer keepalive is operational by entering the show vpc command.
Step 6 Bring up vPC peer link. Ensure that vPC peer link is operational by entering the show vpc command.
Step 7 Edit the configuration file to remove the sync-peer command if using the configuration synchronization feature.
Step 8 Configure the mgmt0 port IP address and download the configuration file.
Step 9 Copy the saved configuration file to the running configuration.
Step 10 Edit the saved configuration file and delete all commands between the configure sync command and the commit command, including these two commands.
Step 11 Copy the new, edited configuration file to the running configuration again.
Step 12 Verify that the configuration is correct by entering the show running-config command and the show provision failed-config slot command.
Step 13 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 14 Shut down all single-homed Fabric Extender vPC host ports.
Step 15 Connect the single-homed Fabric Extender topology fabric ports.
Step 16 Wait for single-homed Fabric Extenders to come online.
Step 17 Ensure the vPC role priority of the existing switch is better than the replacement switch.
Step 18 Connect the peer-link ports to the peer switch.
Step 19 Connect the dual-homed Fabric Extender topology fabric ports.
Step 20 Connect the switch vPC ports.
Step 21 Enter the no shutdown command on all single-homed Fabric Extender vPC ports.
Step 22 Verify that all vPC switches and the Fabric Extenders on the replacement switch come online and that there is no disruption in traffic.
Step 23 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 24 If you are using the configuration synchronization feature, enter the show switch-profile name status command to ensure both switches are synchronized.
Step 25 If vPC auto recovery was disabled in step 4, enable auto recovery using the auto-recovery 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.