- Preface
- Overview
-
- 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
- Direct Firmware Upgrade at Endpoints
- Updating the Firmware on Multiple Endpoints
- Updating the CMC Firmware on a Chassis
- Activating the CMC Firmware on a Chassis
- Updating the Shared Adapter Firmware on a Chassis
- Activating the Shared Adapter Firmware on a Chassis
- Activating the Storage Controller Firmware on a Chassis
- Activating the Board Controller Firmware on a Chassis
- Updating the BIOS Firmware on a Server
- Activating the BIOS Firmware on a Server
- Updating the CIMC Firmware on a Server
- Activating the CIMC Firmware on a Server
- Activating the Board Controller Firmware on a Server
- Activating the Cisco UCS Manager Software
- Activating the Firmware on a Subordinate Fabric Interconnect
- Activating the Firmware on a Primary Fabric Interconnect
- Activating the Firmware on a Standalone Fabric Interconnect
- Verifying Firmware Versions on Components
Directly Upgrading Firmware at Endpoints
This chapter includes the following sections:
- Direct Firmware Upgrade at Endpoints
- Updating the Firmware on Multiple Endpoints
- Updating the CMC Firmware on a Chassis
- Activating the CMC Firmware on a Chassis
- Updating the Shared Adapter Firmware on a Chassis
- Activating the Shared Adapter Firmware on a Chassis
- Activating the Storage Controller Firmware on a Chassis
- Activating the Board Controller Firmware on a Chassis
- Updating the BIOS Firmware on a Server
- Activating the BIOS Firmware on a Server
- Updating the CIMC Firmware on a Server
- Activating the CIMC Firmware on a Server
- Activating the Board Controller Firmware on a Server
- Activating the Cisco UCS Manager Software
- Activating the Firmware on a Subordinate Fabric Interconnect
- Activating the Firmware on a Primary Fabric Interconnect
- Activating the Firmware on a Standalone Fabric Interconnect
- 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 CIMC and BIOS 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 | 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:
-
Cisco UCS Manager
-
Fabric interconnects
-
CMC
-
Shared Adapter
-
Board controllers for chassis and server
-
Storage controller
-
CIMC
-
BIOS
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.
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 fabric interconnect reboot.
Outage Impact of a Cisco UCS Manager Firmware Upgrade
A firmware upgrade to Cisco UCS Manager causes the following disruptions:
Outage Impact of a CMC Firmware Upgrade
When you upgrade the firmware for CMC in a chassis you do not cause any outage.
Outage Impact of a Shared Adapter Firmware Upgrade
If you activate the firmware for a shared adapter, you cause the following outage impacts and disruptions:
Outage Impact of a Storage Controller Firmware Upgrade
If you activate the firmware for a storage controller, you cause the following outage impacts and disruptions:
Outage Impact of a Board Controller Firmware Upgrade
If you activate the firmware for a board controller, you cause the following outage impacts and disruptions:
Outage Impact of a BIOS Firmware Upgrade
A firmware upgrade to the BIOS causes the server to reboot.
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 a Board Controller Firmware Upgrade on a Server
If you activate the firmware for a board controller on a server, you cause the server to be powered off during the upgrade and powered on after the upgrade is complete.
While activating the storage controller, board controller and shared adapter firmware, it is recommended that you power down the servers. In case you do not power down the servers during activation, Cisco UCSM will attempt to power down the servers and wait for a maximum of 16 minutes. During this time, if Cisco UCSM still finds that the servers are not powered down, FSM will fail and Cisco UCSM will not power up the servers that it powered down. FSM will try to come up after 8 minutes.
If UCSM successfully powers down the servers, it will power up the associated servers, based on their desired power states, after activation is complete.
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.
Updating the CMC Firmware on a Chassis
What to Do Next
Activate the firmware.
Activating the CMC Firmware on a Chassis
Updating the Shared Adapter Firmware on a Chassis
Gracefully power down the servers.
What to Do Next
Activate the firmware.
Activating the Shared Adapter Firmware on a Chassis
Activating the Storage Controller Firmware on a Chassis
Activating the Board Controller Firmware on a Chassis
Gracefully power down the servers.
Updating the BIOS Firmware on a Server
What to Do Next
Activate the firmware.
Activating the BIOS Firmware on a Server
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.
Activating the Board Controller Firmware on a Server
This can be done only on servers in the Cisco UCSME-2814 cartridge.
Gracefully power down the servers.
Activating the Cisco UCS Manager Software
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, 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 the Equipment tab. | ||||||||||
| 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. For a standalone fabric interconnect, this disrupts all data traffic in the Cisco UCS domain.



Feedback