Home
Support
Product Support
Cloud and Systems Management
Cisco Application Policy Infrastructure Controller (APIC)
Configuration Guides

Cisco APIC Getting Started Guide, Release 6.2(x)

Releases

6.2(x)
6.1(x)
6.0(x)
5.3(x)
5.2(x)
5.1(x)
5.0(x)
4.2(x)
2.x
2.x
1.3(x)
1.0 and 1.1

View all Saved Content

PDF

Is this content helpful?

Helpful Unhelpful

Suggestions for Improvement

Thank you for your feedback. Your response has been recorded.

Ask about this content

Cisco APIC Getting Started Guide, Release 6.2(x)

Expand all sections

About this content

Trademarks

What's changed in this guide

What's changed in this guide

Initial setup

Additional documents
APIC configuration methods
Change the default BIOS password
Cisco Application Centric Infrastructure
Local serial connection for basic configuration
Access the APIC GUI
Access REST API
Access the NX-OS style CLI
Access the object model CLI

APIC GUI overview

The APIC GUI
Menu bar and submenu bar
Navigation pane
Work pane
Personalize the APIC GUI
Deployment warning and policy usage information
Graphical configuration of ports
View an API interchange
APIC GUI icons
Next generation APIC GUI
Preview the new APIC GUI
Enhancements and improvements to the APIC GUI

Fabric initialization and switch discovery

Fabric initialization
Multi-tier fabric topologies example
Change the external routable subnet
Switch discovery with the APIC
Cisco NX-OS to Cisco ACI POAP auto-conversion
Cisco N 9000 switch secure erase

Cisco APIC cluster management

APIC clusters
Cisco Fabric Controller cluster expansion
Best practices for cluster management
Expand the Fabric Controller cluster using the GUI
Expand the APIC cluster using the add node option
Contract the APIC Cluster using the GUI
Contract APIC nodes using the delete node option
Commission a Cisco APIC in the cluster using the GUI
Commission a Cisco APIC in the cluster
Decommission a Cisco APIC in the cluster using the GUI
Decommission a Cisco APIC in the cluster
Shut down all APICs in a cluster
Bring back the APICs in a cluster
Cold standby clusters
Guidelines for standby Cisco APICs
Verify cold standby status using the GUI
Switch over an active APIC with a standby APIC
Warm standby for a Cisco APIC cluster
Guidelines for using Warm Standby Cisco APICs
Change the standby APIC type using the GUI
Add a standby APIC
Delete a standby from the cluster
Recover the APIC cluster using Warm Standby and the GUI
APIC migration types
Manage APIC cluster at boot using the GUI
Nexus dashboard cluster from APIC GUI

Configure the cisco APIC using the CLI

Best practices for cluster management
Replace a Cisco APIC in a cluster using the CLI
Cisco APIC cluster contractions
Switch over active APIC with standby APIC using CLI
Verify Cold Standby Status Using the CLI
Change the hybrid switch role before discovery
Register an unregistered switch using the CLI
Add a switch before discovery using the CLI
Remove a switch to maintenance mode using the CLI
Insert a switch to operation mode using the CLI
Configure a remote location using the NX-OS style CLI
Find the switch inventory using the NX-OS CLI
Verify the Cisco APIC cluster using the CLI

Configure the cisco APIC using the REST API

Expand the APIC cluster using the REST API
Contract the APIC cluster using the REST API
Switch over the active APIC with the standby APIC using the REST API
Register an unregistered switch using the REST API
Add a switch before discovery using the REST API
Remove a switch to maintenance mode using the REST API
Insert a switch to operational mode using the REST API
Configure a remote location using the REST API
Send an on-demand tech support file using the REST API
Find your switch inventory using the REST API

Cisco APIC Getting Started Guide, Release 6.2(x)

Commission a Cisco APIC in the cluster

Updated: January 12, 2026

Want to summarize with AI?

Use this procedure to commission a Cisco APIC in an existing controller cluster running release 6.0(2) or later, whether for normal provisioning or as part of an RMA workflow. Follow the steps to ensure the APIC is operational and fully integrated into the cluster.

Commission a Cisco APIC in the controller cluster.

Use this procedure when you need to commission an APIC in an existing cluster running release 6.0(2) or later. This may be performed for normal provisioning or as part of an RMA (Return Material Authorization) workflow.

Follow these steps to commission a Cisco APIC in the cluster:

Note
Beginning with Cisco APIC Release 6.0(2), Auto Firmware Update on APIC discovery can update a new APIC to match the existing cluster when it is added through a return merchandise authorization (RMA), cluster expansion, or commissioning. Support depends on the active cluster and new APIC release combination and on feature prerequisites. For supported release combinations and prerequisites, see Auto firmware update on APIC discovery in the Cisco APIC Installation and ACI Upgrade and Downgrade Guide.

Before you begin

Verify that the APIC is connected to the network and powered on.
Obtain required admin credentials for the APIC cluster.

Procedure

From the menu bar, choose System > Controllers .
In the Navigation pane, expand Controllers > apic_controller_name > Cluster as Seen by Node .
Select a decommissioned Cisco APIC from the Active Controllers table.
In the Active Controllers table, click the Actions icon (three dots), which is displayed at the end of the row for each Cisco APIC . From the displayed options, click Commission .

The Commission dialog box is displayed.
Enter the following details in the Commission screen:

Choose the Controller Type . Based on your choice, proceed to the relevant substep.

Put a check in the Enabled check box if you need to support IPv6 addresses.
1. When the Controller Type is Physical :
  - CIMC details pane
    - IP Address: Enter the CIMC IP address.
    - Username: Enter the username to access CIMC.
    - Password: Enter the password to access CIMC.
    - Click Validate . Validation success is displayed on successful authentication.
    This pane appears only if you configured CIMC. If you did not configure CIMC, instead perform the physical APIC login step of the Bring up the APIC cluster using the GUI procedure (step 1b) on the new node to configure out-of-band management.
  - General pane
    - Name: The name of the controller. The name is entered automatically after the CIMC validation.
    - Admin Password: Enter the admin password for the controller.
    - Controller ID: This is auto-populated based on the Cisco APIC that was decommissioned. The ID of the decommissioned node is assigned.
    - Serial Number: This is auto-populated after CIMC validation.
    - Pod ID: Enter the ID number of the pod for the Cisco APIC .
  - Out of Band Network pane
    - IPv4 Address: Enter the IPv4 address of the out-of-band network.
    - IPv4 Gateway: Enter the IPv4 gateway address of the out-of-band network.
    Note
    
    If you have selected the Enabled check box for IPv6 earlier, enter the IPv6 address and gateway.
2. When the Controller Type is Virtual :
  - Virtual Instance: Enter the management IP and click Validate .
    
    Note
    
    The management IP addresses are defined during the deployment of the VMs using ESXi/ AWS.
  - General pane
    - Name: A user-defined name for the controller.
    - Controller ID: This is auto-populated based on the Cisco APIC that was decommissioned. The ID of the decommissioned node is assigned.
    - Serial Number: The serial number of the VM is auto-populated.
  - Out of Band Network pane
    - IPv4 Address: The IP address is auto-populated.
    - IPv4 Gateway: The gateway IP address is auto-populated.
    Note
    
    If you have selected the Enabled check box for IPv6 earlier, enter the IPv6 address and gateway.
  - Infra Network pane
    - IPv4 Address: Enter the infra network address.
    - IPv4 Gateway: Enter the IP address of the gateway.
    - VLAN: (applicable only for remotely attached virtual APIC - ESXi) enter the interface VLAN ID to be used.
    Note
    
    The Infra L3 Network pane is not displayed when the virtual APIC is deployed using AWS.
Click Apply .
Verify that the commissioned Cisco APIC is in the operational state and the health state is Fully Fit .

The APIC is successfully commissioned and ready for role in the controller cluster.

What to do next

Review APIC status and connectivity. Update your records or monitoring tools as needed.

Need help?

Open a support case

(Requires a Cisco Service Contract)

Bias-free language

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.