Migration of Nodes From a First Generation Switch to a Second Generation Switch
Introduction
When upgrading a switch hardware in the ACI fabric, there are multiple scenarios to consider:
-
Scenario 1 - Upgrade the hardware of spine switches.
-
Scenario 2 - Upgrade the hardware of leaf switches without vPC.
-
Scenario 3 - Upgrade the hardware of leaf switches with vPC.
Each scenario has two variations depending on the supported software versions of the old and new switch hardware.
Variation 1 - Old and new switches can run the same ACI software version.
Variation 2 - Old and new switches cannot run the same ACI software versions.
Whenever possible, it is recommended to run the same software version on both old and new switches (Variation 1). Variation 2 is for a specific situation when the old switch hardware is no longer supported by the software versions that support the new switch hardware.
An example of "Variation 2 - Old and new switches cannot run the same ACI software versions".
As mentioned above, Variation 2 is for specific situations when the old switch hardware is no longer supported by the software versions that support the new switch hardware.
The most common scenario is when migrating from the first-generation Cisco Nexus 9000 series switches to newer generation Cisco Nexus 9000 series switches. The first-generation switches are no longer supported starting on Cisco ACI switch software 15.0(1) or later releases while some of the newer generation switches are supported only from 15.0(1) or later.
 Note |
|
General Guidelines
-
To determine which transceivers, adapters, and cables support this switch, see the Cisco Transceiver Modules Compatibility Information document.
-
To see the transceiver specifications and installation information, see Transceiver Module Installation Guides.
-
Due to potential traffic loss, it is recommended that you perform the hardware replacement during a maintenance window.
-
It is recommended to move any Cisco Application Policy Infrastructure Controllers (APICs) that are connected to the switches that you are replacing to any other switches in the fabric and wait for the Cisco APIC cluster to become "Fully Fit".
-
When the Auto Firmware Update feature is used, make sure to set the Default Firmware Version to your target version. If the node ID is part of an upgrade group, make sure that the upgrade group is set with your target version, or delete the upgrade group. See Auto Firmware Update for details.
-
The number of ports and port types of the new switches must match the old switch that you are replacing. If the number does not match, then you must change the configuration to accommodate the new ports or port types.
Note |
You may experience traffic loss for shared services when you upgrade from Cisco APIC 4.2 to Cisco APIC 5.2. To avoid this you can configure communication between tenants as well as communication between VRF instances within a tenant by using the constructs available within the fabric. |
Spine Switches
Old and new switches can run the same ACI software version
The procedure is the same as Return Material Authorization (RMA).
See "Procedures and verification" in "Troubleshoot ACI Fabric Discovery - Device Replacement" for details.
Old and new switches cannot run the same ACI software version
-
Upgrade the APIC cluster to the software version that can run the new switch hardware.
-
Upgrade switches that are not to be replaced to the same version as the APIC cluster.
-
Follow the same procedure as RMA with the existing switch running the old version and the new switch running the new version.
See "Procedures and verification" in "Troubleshoot ACI Fabric Discovery - Device Replacement" for details.
Leaf Switches Without vPC
Old and new switches can run the same ACI software version
Same as Spine Switches above.
Old and new switches cannot run the same ACI software version
Same as Spine Switches above.
フィードバック