The firmware version terminology used depends on the type of endpoint. Each CIMC, I/O module, BIOS, CIMC, and Cisco adapter has two slots for firmware in flash. Each slot holds a version of firmware. One slot is active, and the other is the backup slot. A component boots from whichever slot is designated as active.

The following firmware version terminology is used in the Cisco UCS Manager:

Running version: The running version is the firmware that is active and in use by the endpoint.

Startup version: The startup version is the firmware that will be used when the endpoint next boots up. The Cisco UCS Manager uses the activate operation to change the startup version.

Backup version: The backup version is the firmware in the other slot and not in use by the endpoint. This version can be firmware that you have updated to the endpoint but have not yet activated, or it can be an older firmware version that was replaced by a recently activated version. The Cisco UCS Manager uses the update operation to replace the image in the backup slot. If the endpoint cannot boot from the startup version, it boots from the backup version.

Firmware versions in the fabric interconnect and the Cisco UCS Manager: You can only activate the fabric interconnect firmware and the Cisco UCS Manager on the fabric interconnect. The fabric interconnect and the Cisco UCS Manager firmware do not have backup versions because all the images are stored on the fabric interconnect. As a result, the number of bootable fabric interconnect images is not limited to two, like the server CIMC and adapters. Instead, the number of bootable fabric interconnect images is limited by the available space in the memory of the fabric interconnect and the number of images stored there.

The fabric interconnect and the Cisco UCS Manager firmware have running and startup versions of the kernel and system firmware. The kernel and system firmware must run the same versions of firmware.

Firmware Upgrades Through Auto Install

Auto Install enables you to automatically upgrade a Cisco UCS domain to the firmware versions contained in a single package, in the following stages:

Install Infrastructure Firmware: Uses the Cisco UCS Infrastructure Software Bundle to upgrade the infrastructure components, such as the fabric interconnects, the I/O modules, and the Cisco UCS Manager. Figure 14-8 illustrates the recommended process flow to automatically install infrastructure firmware.

Figure 14-8 Automatic Infrastructure Firmware Installation Process Flow

 Install Server Firmware: Uses the Cisco UCS B-Series Blade Server Software Bundle to upgrade all blade servers in the Cisco UCS domain and/or the Cisco UCS C-Series Rack-Mount UCS-Managed Server Software Bundle to upgrade all rack servers.

These two stages are independent and can be run or scheduled to run at different times.

You can use Auto Install to upgrade the infrastructure components to one version of Cisco UCS and server components to a different version.

Direct Upgrade After Auto Install: During Auto Install, the startup version of the default infrastructure pack is configured. To successfully complete a direct upgrade or activation of the Cisco UCS Manager, fabric interconnects, and I/O modules after Auto Install, ensure that the startup version is cleared before starting a direct upgrade or activation. If the startup version of the default infrastructure pack is configured, you cannot directly upgrade or activate the Cisco UCS Manager, fabric interconnects, and I/O modules. Clearing the startup version of the Default Infrastructure Pack provides detailed steps for clearing the startup version.

Install Infrastructure Firmware: Install Infrastructure Firmware upgrades all infrastructure components in a Cisco UCS domain, including the Cisco UCS Manager, and all fabric interconnects and I/O modules. All components are upgraded to the firmware version included in the selected Cisco UCS Infrastructure software bundle. Install Infrastructure Firmware does not support a partial upgrade to only some infrastructure components in a Cisco UCS domain.

You can schedule an infrastructure upgrade for a specific time to accommodate a maintenance window. However, if an infrastructure upgrade is already in progress, you cannot schedule another infrastructure upgrade. You must wait until the current upgrade is complete before scheduling the next one.