Overview

Overview

Cisco UCS uses firmware obtained from and certified by Cisco to support the endpoints in a Cisco UCS domain. Each endpoint is a component in the Cisco UCS domain, and requires firmware to function. This guide explains how to obtain firmware and upgrade the endpoints in a Cisco UCS domain by using Cisco UCS Manager. It also details the best practices to be followed while upgrading these endpoints.

Cisco UCS Manager Release 6.0(1b) introduces support for Cisco UCS 6664 Fabric Interconnects, delivering high-performance, scalable connectivity for modern data centers. The Cisco UCS 6664 is a 64-port, 2RU top-of-rack switch that offers unified management and flexible integration of both LAN and SAN environments. This release ensures seamless management of Cisco UCS X-Series servers and C-Series servers in a single and highly available domain.

Cisco UCS Manager Release 4.3(4b) introduces the support for Cisco UCS Fabric Interconnects 9108 100G (Cisco UCS X-Series Direct) platform offers a compact and integrated solution for smaller-scale data centers by incorporating networking and management directly within the chassis, eliminating the need for separate Fabric Interconnects.

Cisco UCS Manager Release 4.2(3p) introduces the Cisco UCS 6536 Fabric Interconnect to Cisco UCS 6500 Series Fabric Interconnects. Cisco releases unified Cisco UCS Manager software and firmware upgrades for each of the following platforms with every release of Cisco UCS Manager:

Cisco UCS Manager Release 4.1(1) introduces the Cisco UCS 64108 Fabric Interconnect to Cisco UCS 6400 Series Fabric Interconnects.

Cisco releases unified Cisco UCS Manager software and firmware upgrades for each of the following platforms with every release of Cisco UCS Manager:

  • Cisco UCS 6664 Fabric Interconnect with Cisco UCS X-Series and C-Series servers

  • Cisco UCS Fabric Interconnects 9108 100G with Cisco UCS X-Series and C-Series servers

  • Cisco UCS 6500 Series Fabric Interconnect with Cisco UCS B-Series, C-Series, and X-Series servers

  • Cisco UCS 6400 Series Fabric Interconnect with Cisco UCS B-Series, and C-Series servers

Components That Support Firmware Upgrade

The various platforms that are supported by Cisco UCS Manager have different components that support firmware upgrade.

  • Fabric Interconnects:

    • Cisco UCS 6664 Fabric Interconnect

    • Cisco UCS X-Series Direct (UCSX-S9108-100G)

    • Cisco UCS 6536

    • Cisco UCS 64108

    • Cisco UCS 6454

  • Chassis components:

    • Blade server chassis:

      • I/O Modules/FI-IO Modules


        Note

        • I/O Modules are not supported on the Cisco UCS X-Series Direct, which uses the FI-I/O Modules instead.

      • Power Supply Unit

    • Cisco UCS S3260 chassis:

      • Chassis Management Controller (CMC)

      • Chassis Adapter

      • SAS Expander

      • Board Controller

  • Server components:

    • Blade and Rack server:

      • Adapter

      • Cisco Integrated Management Controller (CIMC)

      • BIOS

      • Storage Controller

      • Board Controller

    • Cisco UCS S3260 storage server node:

      • Cisco Integrated Management Controller (CIMC)

      • BIOS

      • Board Controller

      • Storage Controller

Firmware Version Terminology

The firmware version terminology used depends upon the type of endpoint, as follows:

Firmware Versions in CIMC, I/O Modules, BIOS, CIMC, and Adapters

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 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. 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 is 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. 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 Cisco UCS Manager

You can only activate the fabric interconnect firmware and Cisco UCS Manager on the fabric interconnect. The fabric interconnect and 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 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.

Cross-Version Firmware Support

The Cisco UCS Manager A bundle software (Cisco UCS Manager, Cisco NX‑OS, IOM and FEX firmware) can be mixed with previous B or C bundle releases on the servers (host firmware [FW], BIOS, Cisco IMC, adapter FW and drivers). To help you quickly verify valid combinations, this release includes an interactive compatibility tool, available here:

Cisco UCS Manager Cross Version Firmware Matrix

By selecting a Fabric Interconnect model along with the desired Infrastructure (A Bundle) and Host Firmware (B and C Bundles) releases, the tool dynamically displays whether each combination is a supported configuration.


Note

Beginning with Cisco UCS Manager Release 6.0(1b), Cisco UCS 6300 Series FI and Cisco UCS 6332 FI are not supported.

Table 1. Mixed Cisco UCS Releases Supported on Cisco UCS 6664, 6536, and 6400 series Fabric Interconnects

Infrastructure Versions (A Bundles)

Host FW Versions (B or C Bundles)

4.2(1)

4.2(2)

4.2(3)

4.3(2)

4.3(3)

4.3(4)

4.3(5)

4.3(6)

6.0(1)

6.0(1)

—

—

—

—

—

—

—

—

6664, 6536, 6454, 64108

4.3(6)

—

—

—

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6664, 6536, 6454, 64108

4.3(5)

—

—

—

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6664, 6536, 6454, 64108

4.3(4)

—

—

—

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6664, 6536, 6454, 64108

4.3(3)

—

—

—

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6664, 6536, 6454, 64108

4.3(2)

—

—

—

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6664, 6536, 6454, 64108

4.2(3)

6200, 6332, 6332-16UP, 6454, 64108

6200, 6332, 6332-16UP, 6454, 64108

6200, 6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6332, 6332-16UP, 6454, 64108, 6536

6664, 6536, 6454, 64108

4.2(2)

6200, 6332, 6332-16UP, 6454, 64108

6200, 6332, 6332-16UP, 6454, 64108

6200, 6332, 6332-16UP, 6454, 64108

6332, 6332-16UP, 6454, 64108

6332, 6332-16UP, 6454, 64108

6332, 6332-16UP, 6454, 64108

6332, 6332-16UP, 6454, 64108

6332, 6332-16UP, 6454, 64108

—

4.2(1)

6200, 6332, 6332-16UP, 6454, 64108

6200, 6332, 6332-16UP, 6454, 64108

6200, 6332, 6332-16UP, 6454, 64108

6332, 6332-16UP, 6454, 64108

6332, 6332-16UP, 6454, 64108

6332, 6332-16UP, 6454, 64108

6332, 6332-16UP, 6454, 64108

6332, 6332-16UP, 6454, 64108

—

Table 2. Mixed Cisco UCS Releases Supported on Cisco UCS X-Series Direct

Host FW Versions (B Bundles)

Infrastructure Versions (A Bundles)

4.3(4)

4.3(5)

4.3(6)

6.0(1)

6.0(1)

—

—

—

UCSX-S9108-100G

4.3(6)

UCSX-S9108-100G

UCSX-S9108-100G

UCSX-S9108-100G

UCSX-S9108-100G

4.3(5)

UCSX-S9108-100G

UCSX-S9108-100G

UCSX-S9108-100G

UCSX-S9108-100G

4.3(4)

UCSX-S9108-100G

UCSX-S9108-100G

UCSX-S9108-100G

UCSX-S9108-100G

You may also view the extended version of the Mixed Cisco UCS Releases Supported on Cisco UCS Fabric Interconnects at Cisco UCS Manager Cross-Version Firmware Support 6.0.

For reference, the Cisco UCS Equivalency Matrix for Cisco Intersight, Cisco IMC, and Cisco UCS Manager outlines the release timeline for Cisco Intersight, Cisco Integrated Management Controller (Cisco IMC), and Cisco UCS Manager. It includes essential information such as the date each patch was posted, the specific patch version, and the platforms that are supported by each release. By referring to this matrix, you can identify the appropriate firmware and software versions required for your servers before migrating them to Cisco Intersight. This ensures that your server infrastructure remains supported and operates efficiently during and after the transition.

Server Pack

Server Pack allows you to dynamically support new server platforms1 on existing infrastructure without requiring a complete firmware upgrade. This support is provided by a Cisco UCS Manager catalog image. Through this model, new B-Series, or C-Series server bundles that enable the new servers are supported on the previous infrastructure A bundle.

For example, in Release 3.1(1) and later releases, B, or C server bundles will be supported with Release 3.1(1) infrastructure A bundle. However, B, or C server bundles in Release 3.1(1) and later releases are not supported with the infrastructure A bundle of any release earlier than Release 3.1(1).

The Release Notes for Cisco UCS Manager for a particular release provides the complete matrix of cross-version firmware support for that release. New features introduced in the B, or C server bundles may only become available after upgrading the infrastructure A bundle to the respective version.

The following servers currently support Server Pack:

  • X-Series Servers—Cisco UCS X210c M6, UCS X210c M7, UCS X410c M7UCS X210c M8, and UCS X215c M8

  • B-Series Servers—Cisco UCS B200 M5, UCS B480 M5, and UCS B200 M6

  • C-Series Servers—Cisco UCS C220 M5, C240 M5, C480 M5, C220 M6, C240 M6, C225 M6, C245 M6, C220 M7, C240 M7, C225 M8, C245 M8, C240 M8, and C220 M8

If a peripheral is not supported by the existing infrastructure bundle, it will not be supported through the Server Pack feature. You must upgrade the infrastructure bundle to support this peripheral. For example, if a server is installed with new adapters that are not supported by the existing infrastructure bundle, support for these adapters requires an upgrade to the infrastructure bundle. These adapters cannot be supported through the Server Pack feature.

Because a new catalog image can be used without disrupting any hardware or software components, Server Pack provides the additional flexibility of adding new server platforms to active UCS domains without incurring the operational overhead of upgrading firmware across the whole domain.

Light Weight Upgrades

Until Cisco UCS Manager Release 3.1(3), upgrading the firmware to a patch release involved downloading and activating the complete firmware bundle even when changes were made only to specific components. The firmware versions of all components were modified even though there were no fixes made to some components. This triggered unnecessary updates for that component firmware.

Security updates to the system were also delivered through patches and lead to rebooting of the fabric interconnect and downtime.

Cisco UCS Manager Release 3.1(3) introduces light weight upgrades, which enhances firmware upgrade in the following ways:

  • The firmware version of a component will be updated only if it has been modified.

  • Security updates will be provided through service packs. In Release 3.1(3), light weight upgrade supports only security updates.

  • Within a service pack, updates may only apply to certain components. These components may, at times, be upgraded without a fabric interconnect reboot.

  • Infrastructure and server components updates are delivered through a common service pack bundle. For servers components, only the modified firmware images will be part of the service pack bundle. This results in smaller-sized service pack bundles, compared to the traditional B-Series and C-Series bundles.

Service Packs

Service packs are patches that you can use to apply security updates to Cisco UCS Manager infrastructure and server components. Service packs are specific to a base release. You can apply a service pack on a base release, but you cannot install the service pack independently.

A service pack is provided as a single bundle for infrastructure and server components. You can update all relevant infrastructure, chassis and server components by applying the service pack through Infrastructure, Chassis and Server Auto Install. In Cisco UCS Manager Release 3.1(3), the service pack bundle provides non-disruptive updates only for infrastructure components. Among the infrastructure components, the fabric interconnect update to a service pack may require fabric interconnect rebooting in some specific scenarios such as OpenSSL fixes. The updates for server components are disruptive and will involve application downtime.

Service packs are cumulative for a maintenance release. The latest service pack will contain all the fixes from the previous service packs released for the specific maintenance release.

You can remove or update a previously applied service pack through the Cisco UCS Manager GUI and the Cisco UCS Manager CLI. Consequently, the component firmware version will be from the base release bundle.

Service packs are not applicable to maintenance releases earlier than Cisco UCS Manager Release 3.1(3).

Service Pack Versions

The following guidelines apply to service pack versions:

  • A service pack can be applied only on its base bundle. For example, service pack 3.1(3)SP2 can be applied only on a 3.1(3) release. It is not compatible with a 3.1(4) release, and hence, cannot be applied on it.

  • Service pack version numbering in separate maintenance releases are unrelated. For example, service packs 3.1(3)SP2 and 3.1(4)SP2 are separate and unrelated.

  • The same fix can be made available for separate maintenance releases through separate service packs. For example, the same fix can be made available in 3.1(3)SP2 and 3.1(4)SP3.

  • Service packs are cumulative. You can use the latest service pack version with any patch version within the same maintenance release. For example, 3.1(3)SP3 will contain all the fixes that went into 3.1(3)SP2 and 3.1(3)SP1. You can apply 3.1(3)SP3 on any 3.1(3) release.

  • You cannot downgrade service packs to versions below the default service pack version for a maintenance release.

  • When an upgrade or downgrade of a service pack fails, the default service pack version for that maintenance release becomes the running service pack version. For example:

    Base Bundle Version: 3.1(3b)

    Default Service Pack Version: 3.1(3)SP2(Default)

    Running Service Pack Version: 3.1(3)SP3

    While upgrading from 3.1(3)SP3 to 3.1(3)SP4, if the upgrade fails, the running service pack version displayed is 3.1(3)SP2(Default).

The following table illustrates the Release Version and Running Version Displayed in the different situations that a service pack is applied.

Release Version

Running Version Displayed

3.1(3a)

Base Bundle Version: 3.1(3a)

Service Pack Version: 3.1(3)SP0(Default)

3.1(3)SP1

Base Bundle Version: 3.1(3a)

Service Pack Version: 3.1(3)SP1

3.1(3)SP2

Base Bundle Version: 3.1(3a)

Service Pack Version: 3.1(3)SP2

3.1(3b)

Base Bundle Version: 3.1(3b)

Service Pack Version: 3.1(3)SP2(Default)

3.1(3)SP3

Base Bundle Version: 3.1(3b)

Service Pack Version: 3.1(3)SP3

Service Pack Rollback

You can roll back a service pack that was applied to a base release. The following sections describe the changes made to the bundle version and the service pack version during various rollback scenarios.

Remove Service Pack

Bundle Version

Service Pack Version

No change is made to the bundle version.

Service pack is the default version that comes with the bundle.

Downgrade Infrastructure Bundle to an Earlier Maintenance Release

Bundle Version

Service Pack Version

Infrastructure bundle changes to the version of the earlier maintenance release.

Service pack is removed because it is not valid for the earlier maintenance release.

Downgrade Infrastructure Bundle Within the Same Maintenance Release, But with an Earlier Service Pack Version

Bundle Version

Service Pack Version

Infrastructure bundle changes to the version of the maintenance release patch.

Service pack is removed during any infrastructure upgrade or downgrade, if a corresponding service pack version is not specified during Auto-Install.

Guidelines and Restrictions for Service Packs

  • When you upgrade from one service pack that requires FI reboot to another service pack that requires FI reboot, the FI is rebooted twice - once for each service pack.

  • Server Auto Sync Policy is not supported for service packs.

  • Auto sync of a service pack is not supported if the subordinate FI is running on a release earlier than Release 3.1(3).

Firmware Auto Sync for FI Cluster

Addition of a secondary Fabric Interconnect to form a cluster – either as a replacement or a conversion from standby to HA – requires the infrastructure bundle firmware versions to match. Administrators today manually upgrade/downgrade the replacement FI to the correct version before they connect it to the cluster. Firmware Auto Sync allows the users to automatically upgrade/downgrade the infrastructure bundle to the same version as the survivor FI when the replacement is added as standby to HA. The software package is the UCS software/firmware that resides on the FI.

Implementation

With the earlier implementation, the user would compulsorily configure the replacement FI as non-cluster setup if there was a mismatch in the version of software packages. The replacement FI is manually upgraded/downgraded to the same version of software package on survivor FI through the usual upgrade/downgrade process. Then the replacement FI is added to the cluster, since the upgrade/downgrade of the replacement FI is a manual process.

You are now given an additional option of synchronization of the software packages of the replacement FI with the survivor FI along with the current option. If the user decides to Auto Sync the firmware, the software packages of the survivor FI are copied to the replacement FI. The software packages on the replacement FI are then activated and the FI is added to the cluster. The sync-up of the Cisco UCSM database and the configuration happens via the usual mechanisms once the HA cluster is formed successfully.

Firmware Auto Sync Benefits

In a UCS cluster where one Fabric Interconnect has failed, the Auto Sync feature ensures that the software package of the replacement FI is brought up to the same revision as the survivor. The whole process requires minimal end user interaction while providing clear and concise feedback.

Options for Firmware Upgrades

You can upgrade Cisco UCS firmware through one or more of the following methods:


Note

For the steps required to upgrade one or more Cisco UCS domains to a later release, see the appropriate Cisco UCS upgrade guide. If no upgrade guide is provided, contact Cisco Technical Assistance Center. A direct upgrade from that release may not be supported.

Upgrading a Cisco UCS domain through Cisco UCS Manager

If you want to upgrade a Cisco UCS domain through the Cisco UCS Manager in that domain, you can choose one of the following upgrade options:

  • Upgrade infrastructure, chassis and servers with Auto Install—This option enables you to upgrade all infrastructure components in the first stage of upgrade by using Auto Install. Then you can upgrade all chassis components through chassis firmware packages and all server endpoints through host firmware packages.

  • Upgrade servers through firmware packages in service profiles—This option enables you to upgrade all server endpoints in a single step, reducing the amount of disruption caused by a server reboot. You can combine this option with the deferred deployment of service profile updates to ensure that server reboots occur during scheduled maintenance windows.

  • Direct upgrades of infrastructure and server endpoints—This option enables you to upgrade many infrastructure and server endpoints directly, including the fabric interconnects, I/O modules/FI-IO modules, adapters, and board controllers. However, direct upgrade is not available for all endpoints, including the storage controller, HBA firmware, HBA option ROM and local disk. You must upgrade those endpoints through the host firmware package included in the service profile associated with the server.

  • Upgrade chassis through chassis firmware packages in chassis profiles—This option enables you to upgrade all S3260 Chassis endpoints in a single step.


    Note

    Chassis profiles and chassis firmware packages are applicable only to S3260 Chassis.

Upgrading S3X60 Server Nodes in a Cisco UCS domain through Cisco UCS Manager

You can upgrade a Cisco UCS domain with a S3260 Chassis and servers through Cisco UCS Manager in the following ways:

  • Upgrade infrastructure components through Auto Install—You can upgrade the infrastructure components, such as the Cisco UCS Manager software and the fabric interconnects, in a single step by using Auto Install.

  • Upgrade chassis through chassis firmware packages in chassis profiles—This option enables you to upgrade all chassis endpoints in a single step.

    Cisco UCS S3260 Server Integration with Cisco UCS Manager provides detailed information about chassis profiles and chassis firmware packages.

  • Upgrade servers through firmware packages in service profiles—This option enables you to upgrade all server endpoints in a single step, reducing the amount of disruption caused by a server reboot. You can combine this option with the deferred deployment of service profile updates to ensure that server reboots occur during scheduled maintenance windows.

You can also directly upgrade the firmware at each infrastructure, chassis, and server endpoint. This option enables you to upgrade many infrastructure, chassis, and server endpoints directly, including the fabric interconnects, SAS expanders, CMCs, chassis adapters, storage controllers, and board controllers. However, direct upgrade is not available for all endpoints, including the storage controller, HBA firmware, HBA option ROM and local disk.

Cisco UCS S3260 Server Integration with Cisco UCS Manager provides detailed information about firmware management for S3X60 Server Nodes

Upgrading a Cisco UCS domain through Cisco UCS Central

If you have registered one or more Cisco UCS domains with Cisco UCS Central, you can manage and upgrade all firmware components in those domain through Cisco UCS Central. This option allows you to centralize the control of firmware upgrades and ensure that all Cisco UCS domains in your data center are at the required levels.

You can use Cisco UCS Central to upgrade the capability catalog, infrastructure, and host firmware in all registered Cisco UCS domains that are configured for global firmware management.

You cannot directly upgrade the firmware at each endpoint. In Cisco UCS Central, you must use host firmware policy within a global service profile to upgrade host firmware components.

Options for Service Pack Updates

You can upgrade Cisco UCS firmware to a service pack through one of the following methods:

  • Upgrade to a service pack through Infrastructure Auto Install

  • Upgrade to a service pack through Chassis Auto Install

  • Upgrade to a service pack through Server Auto Install

  • Upgrade to a service pack through firmware packages in service profiles

  • Upgrade to a service pack through chassis firmware packages in chassis profiles

  • Directly activate a Cisco UCS Manager service pack on a base maintenance release

  • Directly activate a fabric interconnect service pack on a base maintenance release

Firmware Upgrades through Firmware Packages in Service Profiles

Server firmware and BIOS versions need periodic updating across multiple servers. If this is done manually, it must be done serially and involves many hours of downtime.

You can use host firmware packages by defining a host firmware policy as an attribute of a service profile template, which is an updating template. Any change made to the service profile template is automatically made to its instantiated service profiles. Subsequently, the servers associated with the service profiles are also upgraded in parallel with the firmware version.

You cannot upgrade the firmware on an I/O module, fabric interconnect, or Cisco UCS Manager through service profiles. You must upgrade the firmware on those endpoints directly.

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.

Depending on the target chassis that you use, you can directly upgrade the firmware on various components:

Infrastructure

UCS 5108 Chassis

UCS Rack Server

Cisco UCS S3260 Chassis

  • Cisco UCS Manager

  • Fabric interconnects

Ensure that you upgrade Cisco UCS Manager first and then the fabric interconnects.

  • I/O modules

  • Power supply unit

  • Server:

    • Adapter

    • CIMC

    • BIOS

    • Storage controller

    • Board controller

  • Adapter

  • CIMC

  • BIOS

  • Storage controller

  • Board controller

  • CMC

  • Chassis adapter

  • SAS expander

  • Chassis board controller

  • Server:

    • CIMC

    • BIOS

    • Board controller

    • Storage controller


Note

Directly upgrading firmware on server endpoints is possible only on discovered, unassociated servers and Cisco adapters.

Process Flow for Manually Installing Infrastructure Firmware, illustrates the recommended process flow.

Figure 1. Process Flow for Manually Installing Infrastructure Firmware


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 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.

Firmware Upgrade to a Minor or a Patch Release

The release number of Cisco UCS Manager software consists of a major release identifier, minor release identifier, and patch release identifier. The minor release identifier and patch release identifier are listed together in parentheses. For example, if the software version number is 6.0(1b) :

  • 6.0 is the major release identifier

  • 1 is the minor release identifier

  • b is the patch release identifier

Read together, it indicates the b patch of the first release of the 6.0 release train.

Firmware upgrade to maintenance releases and patches within a major release are released in the same way as for the major release.

For more information about what is in each maintenance release and patch, see Release Notes for Cisco UCS Manager, Release 6.0

Firmware Management in Cisco UCS Central

Cisco UCS Central enables you to manage all firmware components for all registered Cisco UCS domains.


Note

To manage Cisco UCS domains firmware from Cisco UCS Central, you must enable the global firmware management option in Cisco UCS Manager. You can enable the global firmware management option when you register Cisco UCS Manager with Cisco UCS Central. You can also turn the global management option on or off, based on your management requirements.


Important

Do not unregister a Cisco UCS domain from Cisco UCS Central.

The Cisco UCS domains are categorized into domain groups in Cisco UCS Central for management purposes. You can manage firmware for each domain group separately at the domain group level or for all domain groups from the domain group root. Cisco UCS Central provides you the option to manage the following Cisco UCS domain firmware packages:

  • Capability Catalog— One capability catalog per domain group. All Cisco UCS domains registered to a particular domain group will use the capability catalog defined in the domain group.

  • Infrastructure Firmware— One infrastructure firmware policy per domain group . All Cisco UCS domains registered to a particular domain group will use the same Infrastructure firmware version defined in the domain group.

  • Host Firmware— You can have more than one host firmware policy for the different host firmware components in a domain group. The Cisco UCS domains registered in the domain group will be able to choose any defined host firmware policy in the group. Cisco UCS Central provides you the option to upgrade the host firmware globally to all Cisco UCS domains in a domain group at the same time.


Note

For more information on managing firmware in Cisco UCS Central, see the Firmware Management chapters in the Cisco UCS Central Administration Guide and Cisco UCS Central CLI Reference Manual.

1 This feature will apply to select server platforms.