Cisco APIC Layer 3 Networking Configuration Guide, Release 6.2(x)

Prerequisites for downgrading remote leaf switches

Updated: April 17, 2026

Want to summarize with AI?

Before you downgrade remote leaf switches, remove the remote leaf infrastructure policies and decommission the remote leaf nodes. These prerequisites help prevent configuration conflicts when you downgrade to a software release that does not support the remote leaf feature.

Downgrading remote leaf switches is a maintenance process that requires you to remove specific infrastructure policies and decommission the remote leaf nodes.

Decommission the remote leaf nodes.
Remove the remote leaf policies, including the TEP pools.
Verify the infrastructure tenant configuration.

Required tasks before a remote leaf switch downgrade

Before you downgrade remote leaf switches, complete the following tasks:

Delete the vPC domain.
If you use SCVMM, delete the vTEP virtual network adapter.
Decommission the remote leaf nodes. Wait 10 to 15 minutes for the decommissioning process to complete.
Delete the remote leaf-to-WAN L3Out from the infra tenant.
If you use Multi-Pod, delete the infra L3Out that uses VLAN 5.
Delete the remote TEP pools.

Note

If remote leaf switches are deployed and you downgrade the APIC software from Release 3.1(1) or later to an earlier release that does not support the remote leaf feature, decommission the remote nodes and remove all remote leaf policies, including the TEP pool, before you downgrade. For information about decommissioning switches, see Decommissioning and Recommissioning Switches in the Cisco APIC Troubleshooting Guide.

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.