Cisco APIC Installation and ACI Upgrade and Downgrade Guide

PDF

Cisco APIC Installation and ACI Upgrade and Downgrade Guide

Guidelines and limitations for mixed versions on Cisco ACI-mode switches

Want to summarize with AI?

Log in

This topic explains the guidelines and limitations for using mixed software versions on Cisco ACI-mode switches, including APIC release definitions and operational impacts.


This topic provides definitions for Cisco APIC releases and describes operational limitations when using mixed software versions on Cisco ACI-mode switches.

  • The following definitions are used to describe a Cisco APIC release:

    • A Cisco APIC major release contains support for new software features and additional hardware updates. Examples of major releases include 2.2(1n) and 2.1(1h).

    • A Cisco APIC minor or maintenance release (MR) contains the bugs fixes and patches from the existing release. Examples of minor or maintenance releases include 2.0(1m) and 2.0(2f).

    • A Cisco APIC patch release contains fixes for specific defects. Examples of patch releases include 2.1(1h) and 2.1(1i).

  • Prior to Cisco APIC release 3.0, a red banner warning is displayed, informing you of version differences on the Cisco ACI nodes in the fabric. This banner warning has been removed since Cisco APIC release 3.0.

  • If your Cisco APIC is running the 5.2(4) release or later and your switches are running an Cisco ACI -mode switch software release that is earlier than 15.2(4), a vPC domain's interfaces become suspended/down when its peer node is decommissioned. Graceful insertion (maintenance mode) of the vPC peer node will also lead to the same issue because the switch is automatically decommissioned, rebooted, and recommissioned. In the following example scenarios, you will encounter this issue: