Overview
This chapter outlines procedures for expanding, contracting, and migrating controller clusters to maintain fabric stability and high availability. It enables users to manage node lifecycles, configure standby redundancy, and perform disaster recovery across physical and virtual environments to ensure continuous network operations.
APIC clusters
This topic explains the integration and management of Cisco SD-WAN with Cisco ACI, detailing the processes for mapping and unmapping ACI sites, attaching and detaching devices, and managing controllers to ensure seamless policy application and network control.
Cisco Fabric Controller cluster expansion
This topic explains the process of expanding the Cisco Fabric Controller cluster to accommodate network growth, maintain redundancy, and improve performance by automatically adding controllers within approved size limits once the operator sets the desired administrative cluster size and connects the appropriate controllers.
Cisco APIC cluster contractions
This topic explains the cluster contraction procedure, which involves reducing a cluster's size by removing nodes sequentially, increasing the load on remaining nodes, and making decommissioned slots unavailable until re-enabled by operator input.
Best practices for cluster management
This topic explains best practices for cluster management, focusing on maintaining controller health, ensuring firmware consistency, and safeguarding data integrity during configuration, maintenance, and scaling operations to prevent data loss and cluster instability.
Expand the Fabric Controller cluster using the GUI
Use this procedure to add new APICs to an existing Fabric Controller cluster using the GUI for software releases prior to Cisco APIC release 6.0(2). Ensure the cluster is Fully Fit before expanding, and verify all APICs are operational and healthy after addition.
Expand the APIC cluster using the add node option
Learn how to expand an existing Cisco Application Policy Infrastructure Controller (APIC) cluster using the Add Node option introduced in Cisco APIC release 6.0(2), ensuring the node is clean or factory-reset for seamless integration.
Contract the APIC Cluster using the GUI
Use this procedure to ensure the cluster health state is Fully Fit and identify which controllers should remain in the cluster for releases prior to Cisco APIC release 6.0(2). Follow the steps to contract the Fabric Controller cluster, verify the health state, and decommission controllers in the correct order.
Contract APIC nodes using the delete node option
Use this procedure to contract a Cisco APIC cluster by removing nodes using the Delete Node option, introduced in Cisco APIC release 6.0(2). Ensure the cluster maintains a minimum of three nodes, as a two-node cluster is not supported.
APIC migration types
This topic explains the process of migrating APIC clusters, including transitions between physical and virtual clusters, support for mixed cluster types, and the migration of standby nodes, with details on supported scenarios and platform specifics.
Manage APIC cluster at boot using the GUI
Learn how to build a new cluster, add a node to an existing cluster, or replace a node in an existing cluster using the APIC GUI, ensuring seamless integration and management of your network infrastructure.
Nexus dashboard cluster from APIC GUI
This topic explains the direct navigation feature from the APIC GUI to a registered Nexus Dashboard cluster, available from APIC Release 6.1.4, requiring both systems to meet specific version requirements and granting super admin privileges to remote users with admin-write access.