Auto Firmware Update on APIC Discovery
Beginning with the Cisco Application Policy Infrastructure Controller (APIC) 6.0(2) release, when you add a new Cisco APIC to the fabric either through product a return merchandise authorization (RMA), cluster expansion, or commission, the Cisco APIC is automatically upgraded to the same release as the existing cluster. As the new Cisco APIC goes through the upgrade process, the Cisco APIC may take additional time to be upgraded and join the cluster. If the auto upgrade fails, the Cisco APIC raises a fault and you will be alerted.
Prerequisites and conditions for the automatic Cisco APIC firmware update on discovery feature:
-
All the commissioned Cisco APICs in the cluster must be running the same release, which must be 6.0(2) or later.
-
The Cisco APIC image of the same release as the commissioned Cisco APICs in the cluster must be available in the firmware repository of the commissioned Cisco APICs in the cluster.
-
The CIMC IP address of the new Cisco APIC must be configured and reachable from the commissioned Cisco APICs in the cluster.
-
You must complete using the Initial Setup Utility using the Cisco APIC console that sets the fabric name, Cisco APIC ID and so on, on the new Cisco APIC if the new Cisco APIC is running a release earlier than 6.0(2). If the new Cisco APIC is also running release 6.0(2) or later, you do not no need to use the Initial Setup Utility.
-
Auto firmware update on APIC discovery is supported only on Cisco APIC release 4.2(1) and later.
-
-
When your APIC cluster is running 6.1(2) or a newer version and a new standby APIC that is running a version older than 6.0(2) is added to the APIC cluster, you must run the following command on the new standby APIC for the Auto Firmware Update on APIC Discovery to work.
-
Log in to the CLI of the new APIC.
Note
If the new APIC is not node-1, log in as "rescue-user" without a password. This is because after Initial Setup Utility was completed on the new APIC, it doesn't have the admin password (or any other configuration) synchronized yet.
-
Run acidiag vapicjoin -n <Active APIC OOB IP> -u admin -p <admin password>,
where <Active APIC OOB IP> is the out-of-band IP address of one of the APICs that is already in the cluster.
-
When the standby APIC is auto upgraded to the same version as the rest of the APICS on the APIC cluster, you must delete the active APICs, perform a factory reset, and add the active APIC back to the cluster.
-
When you add a new Cisco APIC to the fabric through product a return merchandise authorization (RMA) repeat steps 1 and 2. See Replacing a Cisco APIC in a Cluster Using the CLI for more information.
-