Describes the process for upgrading or downgrading Cisco ACI fabric components through multiple intermediate software releases when a direct path is not supported.
In the Cisco ACI fabric, all nodes (APICs, leaf switches, and spine switches) should be on the same software release or on a compatible software release, where the APIC nodes have the standard release format of x.y(z), and the leaf and spine switches have the switch-specific standard release format of 1x.y(z). For example, if the APIC nodes are on software release 4.2(1), the leaf switches and spine switches should be on the switch-specific compatible software release of 14.2(1).
APIC Upgrade/Downgrade Support Matrix shows the supported upgrade and downgrade paths for your current version and the target version. If those two versions are too far apart, upgrading or downgrading directly to the target version might not be supported.
Summary
The key components involved in the multistep upgrade and downgrade process are:
-
APICs: Require upgrade or downgrade to standard release format x.y(z)
-
Leaf and spine switches: Require upgrade or downgrade to switch-specific compatible release format 1x.y(z)
-
Intermediate releases: Software versions that serve as stepping stones between current and target versions
-
Support matrix: Documentation that defines supported upgrade and downgrade paths
Workflow
These stages describe how multistep upgrades and downgrades work:
- The system identifies intermediate releases required when a direct upgrade or downgrade path is not available between the current and target software versions. When upgrading or downgrading to a release that does not have a direct path from your current release, you must upgrade or downgrade all the APICs and switches to an intermediate supported release to which there is a direct path, then upgrade or downgrade from that release to your desired release. Sometimes, you must move through multiple intermediate releases before being able to get to your desired release, upgrading or downgrading both the APICs and switches to the same release each time.
- The upgrade process executes sequential upgrades through each intermediate release, beginning with the first intermediate release identified in the support matrix.
- Upgrade the APICs to the 3.1(2) release and the switches to the 13.1(2) release.
- Verify that all APICs and switches are in the Fully Fit state and operational after the upgrade to 3.1(2)/13.1(2).
- Repeat the same steps for 4.1(2) and 14.1(2).
- Repeat the same steps for 4.2(3) and 14.2(3).