- Preface
- Overview
- Cautions, Guidelines, and Limitations
-
- Completing the Prerequisites for Upgrading the Firmware
- Downloading and Managing Firmware in Cisco UCS Manager
- Upgrading Firmware through Auto Install
- Using Firmware Automatic Synchronization Server Policy
- Directly Upgrading Firmware at Endpoints
- Upgrading Firmware through Firmware Packages in Service Profiles
- Managing the Capability Catalog in Cisco UCS Manager
- Verifying that the Data Path is Ready
Directly Upgrading Firmware at Endpoints
This chapter includes the following sections:
- Direct Firmware Upgrade at Endpoints
- Updating the Firmware on Multiple Endpoints
- Adapter Firmware
- BIOS Firmware
- CIMC Firmware
- IOM Firmware
- Board Controller Firmware
- Cisco UCS Manager Firmware
- Fabric Interconnect Firmware
- Verifying Firmware Versions on Components
Direct Firmware Upgrade at Endpoints
If you follow the correct procedure and apply the upgrades in the correct order, a direct firmware upgrade and the activation of the new firmware version on the endpoints is minimally disruptive to traffic in a Cisco UCS domain.
You can directly upgrade the firmware on the following endpoints:
The adapter and board controller firmware can also be upgraded through the host firmware package in the service profile. If you use a host firmware package to upgrade this firmware, you can reduce the number of times a server needs to be rebooted during the firmware upgrade process.
![]() Note | Upgrades of a CIMC through a management firmware package or an adapter through a firmware package in the service profile associated with the server take precedence over direct firmware upgrades. You cannot directly upgrade an endpoint if the service profile associated with the server includes a firmware package. To perform a direct upgrade, you must remove the firmware package from the service profile. |
Stages of a Direct Firmware Upgrade
Cisco UCS Manager separates the direct upgrade process into two stages to ensure that you can push the firmware to an endpoint while the system is running without affecting uptime on the server or other endpoints.
Update
During this stage, the system copies the selected firmware version from the primary fabric interconnect to the backup partition in the endpoint and verifies that the firmware image is not corrupt. The update process always overwrites the firmware in the backup slot.
The update stage applies only to the following endpoints:
Activate
During this stage, the system sets the specified image version (normally the backup version) as the startup version and, if you do not specify Set Startup Version Only, immediately reboots the endpoint. When the endpoint is rebooted, the backup partition becomes the active partition, and the active partition becomes the backup partition. The firmware in the new active partition becomes the startup version and the running version.
The following endpoints only require activation because the specified firmware image already exists on the endpoint:
When the firmware is activated, the endpoint is rebooted and the new firmware becomes the active kernel version and system version. If the endpoint cannot boot from the startup firmware, it defaults to the backup version and raises a fault.
![]() Caution | When you configure Set Startup Version Only for an I/O module, the I/O module is rebooted when the fabric interconnect in its data path is rebooted. If you do not configure Set Startup Version Only for an I/O module, the I/O module reboots and disrupts traffic. In addition, if Cisco UCS Manager detects a protocol and firmware version mismatch between the fabric interconnect and the I/O module, Cisco UCS Manager automatically updates the I/O module with the firmware version that matches the firmware in the fabric interconnect, and then activates the firmware and reboots the I/O module again. |
Outage Impacts of Direct Firmware Upgrades
When you perform a direct firmware upgrade on an endpoint, you can disrupt traffic or cause an outage in one or more of the endpoints in the Cisco UCS domain.
Outage Impact of a Fabric Interconnect Firmware Upgrade
When you upgrade the firmware for a fabric interconnect, you cause the following outage impacts and disruptions:
Outage Impact of a Cisco UCS Manager Firmware Upgrade
A firmware upgrade to Cisco UCS Manager causes the following disruptions:
Outage Impact of an I/O Module Firmware Upgrade
When you upgrade the firmware for an I/O module, you cause the following outage impacts and disruptions:
-
For a standalone configuration with a single fabric interconnect, data traffic is disrupted when the I/O module reboots. For a cluster configuration with two fabric interconnects, data traffic fails over to the other I/O module and the fabric interconnect in its data path.
-
If you activate the new firmware as the startup version only, the I/O module reboots when the corresponding fabric interconnect is rebooted.
-
If you activate the new firmware as the running and startup version, the I/O module reboots immediately.
-
An I/O module can take up to ten minutes to become available after a firmware upgrade.
Outage Impact of a CIMC Firmware Upgrade
When you upgrade the firmware for a CIMC in a server, you impact only the CIMC and internal processes. You do not interrupt server traffic. This firmware upgrade causes the following outage impacts and disruptions to the CIMC:
Outage Impact of an Adapter Firmware Upgrade
If you activate the firmware for an adapter and do not configure the Set Startup Version Only option, you cause the following outage impacts and disruptions:
Updating the Firmware on Multiple Endpoints
You can use this procedure to update the firmware on the following endpoints:
What to Do Next
Activate the firmware.
Adapter Firmware
Updating the Firmware on an Adapter
What to Do Next
Activate the firmware.
Activating the Firmware on an Adapter
BIOS Firmware
Updating the BIOS Firmware on a Server
What to Do Next
Activate the firmware.
Activating the BIOS Firmware on a Server
CIMC Firmware
Updating the CIMC Firmware on a Server
What to Do Next
Activate the firmware.
Activating the CIMC Firmware on a Server
The activation of firmware for a CIMC does not disrupt data traffic. However, it will interrupt all KVM sessions and disconnect any vMedia attached to the server.
IOM Firmware
Updating the Firmware on an IOM
What to Do Next
Activate the firmware.
Activating the Firmware on Multiple IOMs
This procedure ensures that the firmware activation for these endpoints causes minimal disruption to data traffic. If you do not activate the endpoints in the following order with the correct options configured, the endpoints may reboot and cause a temporary disruption in data traffic.
![]() Caution | Do not select ALL from the Filter drop-down list in the Activate Firmware dialog box to activate all endpoints simultaneously. Many firmware releases and patches have dependencies that require the endpoints to be activated in a specific order for the firmware update to succeed. This order can change depending upon the contents of the release or patch. Activating all endpoints does not guarantee that the updates occur in the required order and can disrupt communications between the endpoints, the fabric interconnects, and Cisco UCS Manager. For information about the dependencies in a specific release or patch, see the release notes provided with that release or patch. |
Activating the Firmware on an IOM
Board Controller Firmware
Board controllers maintain various programmable logic and power controllers for all B-Series blade servers, and C-Series rack servers. The board controller update utility enables you to make critical hardware updates.
Board controllers, introduced in Cisco UCS Manager Release 2.1(2a), allow you to make optimizations for components, such as voltage regulators, through an update to a digital controller configuration file by using the board controller update utility. Earlier, updating a voltage regulator required changing physical components. These updates are at a hardware level, and are designed to be backward-compatible. Therefore, having the latest version of the board controller is always preferred.
Guidelines for Activating Cisco UCS B-Series M3 and M4 Blade Server Board Controller Firmware
The following guidelines apply to Cisco UCS B-Series M3 and M4 blade server board controller firmware:
-
You never need to downgrade the board controller firmware.
-
The board controller firmware version of the blade server should be the same as or later than the installed software bundle version. Leaving the board controller firmware at a later version than the version that is currently running in your existing Cisco UCS environment does not violate the software matrix or TAC supportability.
-
Board controller firmware updates are backward compatible with the firmware of other components.
Some Cisco UCS B200 M4 blade servers running on releases prior to Release 2.2(4b) may generate a false Cisco UCS Manager alert, documented in CSCuu15465. This false board controller mismatch alert was resolved in Cisco UCS Manager Capability Catalogs 2.2(4c)T and 2.2(5b)T. You will not see this alert if you use either the 2.2(4c)T or the 2.2(5b)T capability catalog.
![]() Note | For more information, refer to https://tools.cisco.com/bugsearch/bug/CSCuu15465 |
You can apply the capability catalog update as follows:
-
Download 2.2(4c) Infra/Catalog or 2.2(5b) Infra/Catalog software bundle. Downloading and Managing Firmware in Cisco UCS Manager provides detailed information about downloading software bundles.
-
Load catalog version 2.2(4c)T or 2.2(5b)T (or the catalog version included) and activate the catalog. Activating a Capability Catalog Update provides detailed information about activating a capability catalog through Cisco UCS Manager.
-
Decommission the newly inserted blade server.
-
Associate the service profile with the host firmware pack policy that has the earlier board controller version.
When the service profile is associated with the updated host firmware pack policy, any false mismatch alert (such as the one caused by the CSCuu15465 bug) will not be raised any more.
-
Click Save.
-
Re-discover the blade server.
Guidelines for Activating Cisco UCS C-Series M3 and M4 Rack Server Board Controller Firmware
The following guidelines apply to Cisco UCS C-Series M3 and M4 rack server board controller firmware:
-
The board controller firmware and the CIMC firmware must be of the same package version.
-
When you upgrade the C-Series server firmware for Cisco UCS C220 M4 or C240 M4 servers to Cisco UCS Manager 2.2(6c), you will see the following critical alarm:
Board controller upgraded, manual a/c power cycle required on server x
This alarm, documented in CSCuv45173, is incorrectly categorized as a critical alarm. It does not impact the functionality of the server, and can be ignored.
To avoid seeing this alarm, you can do one of the following:
-
Create a custom host firmware package in Cisco UCS Manager to exclude the board controller firmware from the Cisco UCS Manager 2.2(6c) update and keep the older version.
-
Upgrade Cisco UCS Manager infrastructure (A Bundle) to Release 2.2(6c) and continue to run the host firmware (C Bundle) on any Cisco UCS C220 M4 or C240 M4 server at a lower version, according to the mixed firmware support matrix in Table 2 of the Release Notes for Cisco UCS Manager, Release 2.2.
Note
For more information, refer to https://tools.cisco.com/bugsearch/bug/CSCuv45173
-
-
If the activation status of the board controller displays Pending Power Cycle after you upgrade the board controller, a manual power cycle is required. A fault is also generated. After the power cycle is complete, the fault is cleared and the board controller activation status displays Ready.
- Activating the Board Controller Firmware on a Cisco UCS B-Series M2 Blade Server
- Activating the Board Controller Firmware on Cisco UCS B-Series M3 and M4 Blade Servers
- Activating the Board Controller Firmware on Cisco UCS C-Series M3 and M4 Rack Servers
Activating the Board Controller Firmware on a Cisco UCS B-Series M2 Blade Server
The board controller firmware controls many of the server functions, including eUSBs, LEDs, and I/O connectors.
![]() Note | This activation procedure causes the server to reboot. Depending upon whether the service profile associated with the server includes a maintenance policy, the reboot can occur immediately. Cisco recommends that you upgrade the board controller firmware through the host firmware package in the service profile as the last step of upgrading a Cisco UCS domain, along with upgrading the server BIOS. This reduces the number of times a server needs to reboot during the upgrade process. |
Activating the Board Controller Firmware on Cisco UCS B-Series M3 and M4 Blade Servers
The board controller firmware controls many of the server functions, including eUSBs, LEDs, and I/O connectors.
![]() Note | This activation procedure causes the server to reboot. Depending upon whether the service profile associated with the server includes a maintenance policy, the reboot can occur immediately. Cisco recommends that you upgrade the board controller firmware through the host firmware package in the service profile as the last step of upgrading a Cisco UCS domain, along with upgrading the server BIOS. This reduces the number of times a server needs to reboot during the upgrade process. |
The following limitations apply to M3 and M4 board controller firmware:
-
You cannot downgrade the firmware after the upgrade is complete.
-
You must be using Cisco UCS Manager, Release 2.1(2a) or greater.
-
The board controller firmware version of the blade server should be the same or newer than the installed software bundle version.
-
Leaving the board controller firmware at a later version than the version that is currently running in your existing Cisco UCS environment does not violate the software matrix or TAC supportability.
-
Board controller firmware updates are always backward compatible with the firmware of other components. However, you cannot downgrade the board controller firmware in Cisco UCS Manager.
-
If blade server components, such as CIMC, and adapter, are running a firmware version that is earlier than the firmware version of the board controller, you do not need to upgrade the blade components to match the firmware version running on the board controller.
![]() Note | For more information, please refer to https://tools.cisco.com/bugsearch/bug/CSCuu15465 |
-
Download 2.2(4c) Infra/Catalog or 2.2(5b) Infra/Catalog software bundle. Downloading and Managing Firmware in Cisco UCS Manager provides detailed information about downloading software bundles.
-
Load catalog version 2.2(4c)T or 2.2(5b)T (or the catalog version included) and activate the catalog. Activating a Capability Catalog Update provides detailed information about activating a capability catalog through Cisco UCS Manager.
-
Decommission the newly inserted blade server.
-
Associate the blade server with the host firmware pack policy that has the earlier board controller version.
No false mismatch alerts are raised because the catalog has the fix for CSCuu15465.
Note
This is a catalog-only fix
Activating the Board Controller Firmware on Cisco UCS C-Series M3 and M4 Rack Servers
The board controller firmware controls many of the server functions, including eUSBs, LEDs, and I/O connectors.
![]() Note | This activation procedure causes the server to reboot. Depending upon whether the service profile associated with the server includes a maintenance policy, the reboot can occur immediately. Cisco recommends that you upgrade the board controller firmware through the host firmware package in the service profile as the last step of upgrading a Cisco UCS domain, along with upgrading the server BIOS. This reduces the number of times a server needs to reboot during the upgrade process. |
The following limitations apply to M3 and M4 board controller firmware:
-
You must be using Cisco UCS Manager, Release 2.2(1a) or greater.
-
The board controller firmware and the CIMC firmware must be of the same package version.
-
If the activation status of the board controller displays Pending Power Cycle after you upgrade the board controller, a manual power cycle is required. A fault is also generated. After the power cycle is complete, the fault is cleared and the board controller activation status displays Ready.
Cisco UCS Manager Firmware
Consider the following guidelines and best practices while activating firmware on the Cisco UCS Manager software:
- In a cluster configuration, Cisco UCS Manager on both fabric interconnects must run the same version.
- Cisco UCS Manager activation brings down management for a brief period. All virtual shell (VSH) connections are disconnected.
- In a cluster configuration, Cisco UCS Manager on both fabric interconnects is activated.
- A Cisco UCS Manager update does not affect server application I/O because fabric interconnects do not need to be reset.
- If Cisco UCS Manager is updated while the subordinate fabric interconnect is down, the subordinate fabric interconnect is automatically updated when it comes back up.
Upgrade Validation
Cisco UCS Manager validates the upgrade or downgrade process and displays all firmware upgrade validation failures, such as deprecated hardware, in the Upgrade Validation tab. If there are upgrade validation failures, the upgrade fails, and Cisco UCS Manager rolls back to the earlier version. You must resolve these faults before continuing with the upgrade.
When upgrading or downgrading the infrastructure firmware through the Auto Install method, if you do not want Cisco UCS Manager to report issues with the upgrade or downgrade process, check the Skip Validation check box. Conversely, to report issues with the upgrade or downgrade process, clear the Skip Validation check box. The Skip Validation check box is cleared by default.
Activating the Cisco UCS Manager Software
Fabric Interconnect Firmware
Activating the Firmware on a Subordinate Fabric Interconnect
Determine which fabric interconnect in the cluster is the subordinate fabric interconnect.
What to Do Next
If the high availability status of the subordinate fabric interconnect contains the required values, update and activate the primary fabric interconnect.
Activating the Firmware on a Primary Fabric Interconnect
This procedure continues directly from Activating the Firmware on a Subordinate Fabric Interconnect and assumes you are on the Firmware Management tab.
Activate the subordinate fabric interconnect.
Step 1 | On the
Installed Firmware tab, click
Activate Firmware.
Cisco UCS Manager GUI opens the Activate Firmware dialog box and verifies the firmware versions for all endpoints in the Cisco UCS domain. This step might take a few minutes, based on the number of chassis and servers. | ||||||
Step 2 | From the Filter drop-down list on the menu bar, choose Fabric Interconnects. | ||||||
Step 3 | On the row of the Activate Firmware dialog box for the subordinate fabric interconnect, do the following: | ||||||
Step 4 |
Click Apply.
Cisco UCS Manager updates and activates the firmware and reboots the fabric interconnect and any I/O module in the data path to that fabric interconnect, disrupting data traffic to and from that fabric interconnect. However, assuming the Cisco UCS domain is configured to permit traffic and port failover, data traffic fails over to the other fabric interconnect, which becomes the primary. When it comes back up, this fabric interconnect is the subordinate fabric interconnect. | ||||||
Step 5 | Verify the high availability status of the fabric interconnect.
If the High Availability Details area for the fabric interconnect does not show the following values, contact Cisco Technical Support immediately.
|
Activating the Firmware on a Standalone Fabric Interconnect
For a standalone configuration with a single fabric interconnect, you can minimize the disruption to data traffic when you perform a direct firmware upgrade of the endpoints. However, you must reboot the fabric interconnect to complete the upgrade and, therefore, cannot avoid disrupting traffic.
![]() Tip | If you ever need to recover the password to the admin account that was created when you configured the fabric interconnects for the Cisco UCS domain, you must know the running kernel version and the running system version. If you do not plan to create additional accounts, Cisco recommends that you save the path to these firmware versions in a text file so that you can access them if required. |
Step 1 | In the Navigation pane, click Equipment. | ||||||||||
Step 2 | On the Equipment tab, click the Equipment node. | ||||||||||
Step 3 | Expand the Fabric Interconnects node and click the standalone fabric interconnect. | ||||||||||
Step 4 | On the General tab, click Activate Firmware. | ||||||||||
Step 5 | In the
Activate Firmware dialog box, complete the
following fields:
| ||||||||||
Step 6 | Click OK. |
Cisco UCS Manager activates the firmware and reboots the fabric interconnect and any I/O module in the data path to that fabric interconnect. For a standalone fabric interconnect, this disrupts all data traffic in the Cisco UCS domain.