Overview
Learn how to decommission a Cisco APIC controller from a cluster using the GUI for APIC releases prior to version 6.0(2), ensuring the controller is unregistered and removed from service.
Decommissioning a controller removes its membership from the cluster and takes it out of service.
This task applies to APIC releases prior to version 6.0(2). For APIC release 6.0(2) or later, refer to the updated procedure.
Follow these steps to decommission a Cisco APIC in the cluster using the GUI:
Before you begin
-
Make sure you are running a Cisco APIC release prior to 6.0(2).
-
Ensure you are not logged in to the controller that you plan to decommission.
Procedure
| 1. | Go to System > Controllers in the main menu. |
|
| 2. | Select an APIC node that is in the cluster (but not the one you want to decommission), and expand Cluster as Seen by Node . |
|
| 3. | In the APIC Cluster tab, confirm that the Health State for Active Controllers is Fully Fit . |
|
| 4. | In the Active Controllers table, right-click the controller you want to remove and select Decommission . |
|
| 5. | In the confirmation dialog box, click Yes . |
The controller’s operational state shows Unregistered . It is no longer visible in the cluster and is taken out of service.
What to do next
-
Power down and physically disconnect the controller from the fabric.
-
Perform a factory reset on the controller before returning it to service.
-
For clusters using Layer 4-Layer 7 services, reboot the decommissioned controller before re-commissioning.
-
After all appliances are decommissioned operational cluster size shrinks. Verify the operational state and size of the cluster and ensure that the controller is unregistered and removed..