Accessing the Dashboard
You can access the dashboard, which shows you the firmware status of the APIC nodes and switches in your fabric, by navigating to .
The dashboard also shows the usage of firmware repository on each APICs.
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.
![]() Note |
Ensure that you check and follow these guidelines: |
![]() Note |
Beginning with Cisco APIC release 6.2(1), policy-based downgrade is not supported when you select the 6.2(1) image as the target firmware. |
You can access the dashboard, which shows you the firmware status of the APIC nodes and switches in your fabric, by navigating to .
The dashboard also shows the usage of firmware repository on each APICs.
This procedure downloads images to the Cisco APIC firmware repository from an external file server or your local machine. The supported image types are listed below:
Cisco APIC firmware image
Cisco ACI swtich firmware image
Cisco CIMC HUU image for APIC CIMC
External additional rules for pre-upgrade validations
If you are downgrading the software on the Cisco APICs, the process is identical to the process for upgrading the software, except that the target release that you choose will be earlier than the currently installed release. The text for dialogs, fields, buttons, and other controls in the Cisco APIC GUI specify "upgrade" even though you are downgrading the software.
![]() Note |
In the Cisco APIC release 6.0(2) and later, download both the 32-bit and 64-bit Cisco ACI-mode switch images to the Cisco APIC. Downloading only one of the images may result in errors during the upgrade process. For more information, see Guidelines and limitations for upgrading or downgrading. In the Cisco ACI-mode switch 16.x releases, the 64-bit switch software has the same image name as the 32-bit software when installed on the switch. To verify which version is running on the switch, use the md5sum command against the image file on switch. Compare this md5sum hash to the switch image contained in the /firmware/fwrepos/fwrepo directory of the Cisco APIC. On subsequent upgrades, the 64-bit and 32-bit image names are differentiated on the switch. |
|
Step 1 |
Download the desired target version from the Cisco Software Download site (for example, 5.2(1g) release) to your file server or local machine. |
||
|
Step 2 |
On the menu bar, choose . |
||
|
Step 3 |
Click Images in the left navigation bar. |
||
|
Step 4 |
Click the Actions icon and select Add Firmware from the drop-down menu. |
||
|
Step 5 |
Determine if you want to import the firmware image from a local or a remote location.
|
||
|
Step 6 |
Click Submit. The Cisco APICs begins downloading the specified firmware images from the configured source. The download progress is shown in the Download Status column |
Starting with Cisco ACI release 6.2(1), the system includes an integrated, orchestrated CIMC upgrade workflow. This feature allows you to upgrade CIMCs of APICs in a cluster directly from the APIC user interface.
Prior to upgrading the Cisco APIC software in your Cisco ACI fabric, you may also need to update the CIMC version running on your fabric. To ensure compatibility, review the Cisco APIC Release Notes for a list of supported CIMC software versions for each release. The Cisco APIC Release Notes can be found on the APIC documentation page.
Ensure that you check and follow these guidelines:
Review all pre-upgrade checklists and guidelines relevant to your environment. See Pre-Upgrade/Downgrade Checklists for more information.
Review the Guidelines and limitations for upgrading or downgrading.
Download the required CIMC HUU image to the APIC as described in the Download APIC, APIC CIMC, Switch and additional rules for pre-upgrade validation on APICs section.
![]() Note |
CIMC upgrades through APIC are supported only with specific CIMC HUU versions listed in the catalog object compatRsSuppHw. For example, when your APIC model is APIC-G5 (apicg5) and the APIC version is 6.2(1), the only CIMC HUU version supported by the APIC CIMC upgrade workflow is C225M8 6.0(1.250131). An example output of the catalog object is listed below. The APIC release notes may list additional supported CIMC HUU versions. If you need to use one of these other versions, you must upgrade CIMC through the CIMC user interface.
|
|
Step 1 |
Go to the section in the APIC user interface. |
|
Step 2 |
Select from the navigation pane. |
|
Step 3 |
In the Upgrade Component area, choose CIMC. |
|
Step 4 |
Your APIC nodes show up in the table below along with the current CIMC version and its Status. When the corresponding CIMC version is available in the APIC's firmware repository, the Status column shows Upgrade Available. Click Validate for each APIC with the Upgrade Available status. The Validate CIMC firmware slider appears. In the Validate CIMC firmware slider, provide the CIMC Username, Password and IP address along with the target CIMC HUU image version, then click Validate. This will validate whether the APIC has access to the CIMC to perform the CIMC upgrade with the provided image. |
|
Step 5 |
Once all APIC nodes show Validated in the Status column, click Next. If some of your APIC nodes are already running the compatible CIMC version, the Status column shows Upgraded and you do not need to validate it to click Next. |
|
Step 6 |
The Step 2 - Validation Results view appears. Wait for the pre-upgrade validations to complete. Make sure that all validations are passed. If there is a validation that failed with severity Catastrophic, you must fix it to proceed to the next step |
|
Step 7 |
The Step 3 - Summary view appears. Review your selections then click Submit to start the CIMC upgrade. |
|
Step 8 |
The Progress view appears. Monitor it and wait until it shows Completed for all steps. |
Starting with Cisco ACI release 6.2(1), the APIC upgrade process has been enhanced with a streamlined and orchestrated processing compared to the previous upgrade process with each APIC node upgrading semi-individually without a central orchestration point. Optimized APIC reboot process enables faster upgrade experience.
![]() Note |
Downgrading Cisco APICs from Cisco APIC 6.2 or newer releases to a release older than 6.2(1) is not supported. See Checklists for Downgrade for details. |
The pre-upgrade validation step was also enhanced with the additional rules that can be imported separately, which always provides the latest and greatest rule sets.
In the new process, APIC 1 acts as the central orchestration point of the entire cluster for the upgrade. For this reason, to perform the APIC cluster upgrade, you must be on the APIC1's user interface.
See ACI Upgrade or Downgrade Architecture section for the details of the upgrade processes behind the scenes.
External Validation Rules
Prior to ACI release 6.2(1), it was recommended for users to manually download and run the python script from ACI Pre-Upgrade Validation Script. This script should be used in addition to, and separately from, the built-in validations performed during the upgrade workflow in the APIC GUI
Starting with ACI release 6.2(1), the upgrade workflow in the APIC GUI can load the additional external rules equivalent to ACI Pre-Upgrade Validation Script and run them along with the built-in rules.
There are two options to load the external rules.
Manually download the rule bundle image (a tar ball file) from cisco.com and upload it by following the instructions in Download APIC, APIC CIMC, Switch and additional rules for pre-upgrade validation on APICs section. APIC looks for the image during the upgrade workflow.
Integrate and fetch the script directly from Intersight.
During the upgrade workflow, APIC automatically tries to download the rule bundle image (a tar ball file) from Cisco Intersight if the APIC is claimed by Cisco Intersight and has IP reachability. See Cisco APIC and Intersight Device Connector for details about the connectivity to Cisco Intersight.
You must have the external rule bundle image from either option to proceed with the actual upgrade.
During the pre-upgrade validation step in the APIC upgrade workflow, APIC always attempts to use the Cisco Intersight option first. If it can download the external rules, it compares the version to any other external rules in its local firmware repository and uses the latest version. Using Cisco Intersight is highly recommended, as it ensures your APIC always has the most up-to-date rules without requiring you to manually check cisco.com.
Ensure that you check and follow these guidelines:
Review the Upgrading or Downgrading Cisco ACI Fabrics.
Review all pre-upgrade checklists and guidelines relevant to your environment. See Pre-Upgrade/Downgrade Checklists for more information.
Review the Guidelines and limitations for upgrading or downgrading.
|
Step 1 |
Go to the section in the APIC user interface. |
||
|
Step 2 |
Select from the navigation pane. |
||
|
Step 3 |
In the Upgrade Component area, choose either Controller. |
||
|
Step 4 |
To upgrade or downgrade the main firmware, select Regular Upgrade, choose the desired firmware image from the Firmware Image drop-down. |
||
|
Step 5 |
The Step 2 - Validation view appears. APIC runs the built-in pre-upgrade validations along with the external validation rules. Make sure that all validations are passed or make sure that appropriate actions were performed for the failed validations. If there is a validation that failed with severity Catastrophic, you must fix it to proceed to the next step. As mentioned in the External Validation Rules section, APIC can get the external rules either from Cisco Intersight or from its local firmware repository.
|
||
|
Step 6 |
Once you have addressed all failed validations in Step 2 - Validation, click Next. |
||
|
Step 7 |
In the Step 3 - Upgrade view, review your selections then click Submit. |
||
|
Step 8 |
Monitor the controller and cluster upgrade/downgrade status.
|
||
|
Step 9 |
To view the upgrade details for the previous upgrades, select the tab. |
All controllers in the cluster are upgraded or downgraded to the target firmware version. The APIC cluster becomes fully fit and operational on the new release.
After completion, verify cluster health and review upgrade logs or audit trails for any additional actions or validations.
This procedure describes how to download switch images to leaf and spine switches from APIC’s firmware repository at your own timing without starting the actual upgrade (i.e. software installation) or downgrade. This is called pre-download.
During this operation, switches will remain up and no reboot will be performed.
![]() Note |
When you upgrade a switch from one release to the next release, the fault code F1821 is displayed as the bootflash memory increases. Ignore this fault as it is auto cleared after the switch upgrade. |
If you are downgrading the software on the Cisco APICs, the process is identical to the process for upgrading the software, except that the target release that you choose will be earlier than the currently installed release. The text for dialogs, fields, buttons, and other controls in the Cisco APIC GUI specify “upgrade” even though you are downgrading the software.
Ensure that you check and follow these guidelines:
Wait until all the controllers are upgraded or downgraded to the new firmware version before proceeding to upgrade or downgrade the switch firmware.
|
Step 1 |
On the menu bar, choose . |
||
|
Step 2 |
In the left navigation window, click . |
||
|
Step 3 |
Click the Actions icon and select Create Update Group from the scroll down menu. |
||
|
Step 4 |
In the Setup Switch Update Group window appears, enter a name for the Upgrade Group Name. |
||
|
Step 5 |
In the Switch Selection step, click the Add Switches button, then select the switches that need to be upgraded / downgraded and then click OK, then click Next. |
||
|
Step 6 |
In the Version Selection step, select an Update Type, then in the Select Firmware section select an image that you want to upgrade/downgrade. |
||
|
Step 7 |
(Optional) If you need any of the advanced options listed below, click Advanced Settings to bring up the Advanced Settings window. Note that typically there is no need to set these advanced options. We recommend that you disable the options or use the default values. In the Advanced Settings window, perform any of the following actions if needed:
Click Done when you have finished performing any of the actions in the Advanced Settings window. You are then returned to the main Firmware page. |
||
|
Step 8 |
When you have verified that everything in the Version Selection step is correct, click Next. |
||
|
Step 9 |
Review the information provided in the Validation step. Any faults or issues that might affect your upgrade are displayed in this page. We recommend that you address any faults or issues that you see displayed before proceeding with the upgrade. See the Pre-Upgrade/Downgrade Checklists for details. After you have addressed the faults or issues raised in the Validation step, click Next to go to the Confirmation step. |
||
|
Step 10 |
In the Confirmation step, verify that the information is correct, then click Begin Download. The system begins downloading the software to all of the nodes that you selected in the previous screen, and displays the download status for each node.
|
||
|
Step 11 |
Verify that the download was completed successfully for all of the nodes that you want to upgrade in the group. If any nodes are shown as Failed in the Status column, you have several options:
See Common Reasons for Download Failure for troubleshooting. When you see the status of Download Complete for all the nodes in your group, you will see Ready to Install at the top of the screen. |
After the pre-download on all switches is done and their upgrade status show Ready to Install, you can perform the procedure to trigger the upgrade, which will install the firmware and reboot the switches.
Typically, you would perform a pre-download hours or days before this procedure. Make sure that you did not violate any validations since the pre-upgrade validations were performed at the time of pre-download. If you want to perform pre-upgrade validations again at this point, use the Script because the APIC built-in pre-upgrade validator will result in the re-downloading of the switch image.
Ensure that you check and follow these guidelines:
You must first finish the pre-download procedures in Pre-Download Images to the Leaf and Spine Switches.
|
Step 1 |
When you have a maintenance window where you are able to have the nodes reboot as part of the upgrade process, click Actions, then Begin Install to begin the software installation. You can monitor the progress of the upgrade for the nodes in the upgrade group in the Node Firmware Update window. You can also close this window and click Nodes in the left navigation window to check the overall status of the upgrade group in the Status column in the table. |
|
Step 2 |
When all of the nodes are shown with a status of Completed, click Done and proceed with the next update group. |