Overview

Diagrams Illustrating Cisco UCS Platforms

Figure 1: Cisco UCS 6454 Fabric Interconnect with Cisco UCS B-Series and C-Series Servers

This diagram illustrates a network architecture. A central 'UCS 6400 Series Fabric Interconnect' is shown. It connects to a 'UCS 5108 chassis', a 'FEX' (Fabric Extender), 'B-Series Servers', and 'C-Series Servers'. Arrows indicate the flow of connection from the Fabric Interconnect to these components.

Figure 2: Cisco UCS 6300 Series Fabric Interconnect with Cisco UCS B-Series and C-Series Servers

This diagram illustrates a network architecture similar to Figure 1. A central 'UCS 6300 Series Fabric Interconnect' is shown. It connects to a 'UCS 5108 chassis', a 'FEX', 'B-Series Servers', and 'C-Series Servers'. Arrows indicate the flow of connection.

Figure 3: Cisco UCS 6200 Series Fabric Interconnect with Cisco UCS B-Series, and C-Series Servers

This diagram illustrates a network architecture. A central 'UCS 6200 Series Fabric Interconnect' is shown. It connects to a 'UCS 51xx chassis', a 'FEX', 'B-Series Servers', and 'C-Series Servers'. Arrows indicate the flow of connection.

Figure 4: Cisco UCS 6324 Fabric Interconnect with Cisco UCS B-Series Servers and C-Series Servers

This diagram illustrates a network architecture. A central 'UCS 6324 Fabric Interconnect (UCS Mini)' is shown. It connects to a 'UCS 51xx chassis', 'B-Series Servers', and 'C-Series Servers'. Arrows indicate the flow of connection.

These figures illustrate the various platforms and the firmware bundles supported by Cisco UCS Manager Release 4.0. Each release has the following firmware bundles:

Firmware Bundles

Infrastructure software bundle (A bundle): This bundle contains the firmware images required by the fabric interconnects, I/O Modules, and Cisco UCS Manager. Cisco UCS Manager 4.0 and later releases include three separate infrastructure bundles:

• Cisco UCS 6454 Fabric Interconnect: ucs-6400-k9-bundle-infra.4.0.x.xxx.A.bin
• Cisco UCS 6300 Series Fabric Interconnect: ucs-6300-k9-bundle-infra.4.0.x.xxx.A.bin
• Cisco UCS 6200 Series Fabric Interconnect: ucs-k9-bundle-infra.4.0.x.xxx.A.bin
• Cisco UCS 6324 Fabric Interconnect: ucs-mini-k9-bundle-infra.4.0.x.xxx.A.bin

B-Series server software bundle (B bundle): This bundle contains firmware for B-Series blade servers, including adapter, BIOS, CIMC, and board controller firmware. Refer to 'Release Bundle Contents for Cisco UCS Manager, Release 4.0' for details.

Note: Starting with Cisco UCS Manager Release 3.1(2), firmware for common endpoints like local disk is available in both B-Series and C-Series bundles.

C-Series server software bundle (C bundle): This bundle contains firmware for C-Series rack-mount servers, including adapter, BIOS, CIMC, and board controller firmware. It also includes firmware for Cisco UCS S3260 storage servers. Refer to 'Release Bundle Contents for Cisco UCS Manager, Release 4.0' for details.

Note: Starting with Cisco UCS Manager Release 3.1(2), firmware for common endpoints like local disk is available in both B-Series and C-Series bundles.

Capability catalog software bundle (T bundle): This bundle specifies implementation-specific tunable parameters, hardware specifics, and feature limits. Cisco UCS Manager uses the capability catalog to update server component display and configurability. Cisco UCS Manager Release 4.0 and later releases are compatible with any 4.0 catalog file, but not with 3.2 or 3.1 catalog versions. The catalog can be bundled with infrastructure releases or released as a standalone image.

The upgrade order for endpoints in a Cisco UCS domain depends on the upgrade path. Consult the required order of steps for your specific upgrade path.

Components That Support Firmware Upgrade

Cisco provides best practices for managing firmware images and updates, detailed in this document and the technical note 'Unified Computing System Firmware Management Best Practices'.

Definitions for firmware management:

• Update: Copies the firmware image to the backup partition on an endpoint.
• Activate: Sets the firmware in the backup partition as the active firmware version, potentially requiring a reboot.

Note: For capability catalog upgrades, update and activate occur simultaneously.

The following platforms and components support firmware upgrade via Cisco UCS Manager:

Fabric Interconnects:

• Cisco UCS 6454
• Cisco UCS 6332
• Cisco UCS 6332-16 UP
• Cisco UCS 6248 UP
• Cisco UCS 6296 UP
• Cisco UCS 6324

Chassis Components:

Blade Server Chassis:

• I/O Modules

Note: I/O Modules are not supported on the primary Cisco UCS Mini chassis but are supported on the secondary Cisco UCS Mini chassis.

• Power Supply Unit

Cisco UCS S3260 Chassis:

• Chassis Management Controller (CMC)
• Chassis Adapter
• SAS Expander

Server Components:

Blade and Rack Servers:

• Adapter
• Cisco Integrated Management Controller (CIMC)
• BIOS
• Storage Controller

Note: Storage controller is not a supported server component in Cisco UCS Mini.

• Board Controller

Cisco UCS S3260 Storage Server Node:

• Cisco Integrated Management Controller (CIMC)
• BIOS
• Board Controller
• Storage Controller

Firmware Version Terminology

Firmware version terminology varies by endpoint type.

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

Each CIMC, I/O module, BIOS, and Cisco adapter has two firmware slots in flash, each holding a firmware version. One slot is active, and the other is the backup slot. The component boots from the active slot.

Cisco UCS Manager uses the following terminology:

• Running Version: The firmware that is active and in use by the endpoint.
• Startup Version: 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 firmware in the other slot, not currently in use. This can be a recently updated but unactivated version or an older version replaced by an activated one. 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.

Fabric Interconnect and Cisco UCS Manager Firmware Versions: Fabric interconnect and Cisco UCS Manager firmware do not have backup versions as all images are stored on the fabric interconnect. The number of bootable images is limited by available memory. These components have running and startup versions for kernel and system firmware, which must match.

Cross-Version Firmware Support

The Cisco UCS Manager A bundle software (including Cisco UCS Manager, Cisco NX-OS, IOM, and FEX firmware) can be mixed with previous B or C bundle releases on servers (host firmware, BIOS, Cisco IMC, adapter firmware, and drivers).

Table 1: Mixed Cisco UCS Releases Supported on Cisco UCS 6200, 6300, 6454 Fabric Interconnects

Table 2: Mixed Cisco UCS Releases Supported on Cisco UCS Mini Fabric Interconnects

Table 3: Mixed B, C Bundles Supported on All Platforms with the 4.0(4)A Bundle

Table 4: Mixed B, C Bundles Supported on All Platforms with the 4.0(1)A Bundle

Important: Ensure that configurations for the Cisco UCS domain are supported by the firmware version on the server endpoints when implementing cross-version firmware.

Server Pack

Server Pack allows dynamic support for new server platforms on existing infrastructure without a complete firmware upgrade, using a Cisco UCS Manager catalog image. This enables new B-Series or C-Series server bundles to be supported on previous infrastructure A bundles. New features in B or C bundles may only be available after upgrading the infrastructure A bundle.

The following servers currently support Server Pack:

• B-Series Servers: UCS B200 M4, B260 M4, B420 M4, B460 M4
• C-Series Servers: UCS C220 M4, C240 M4, C460 M4

If a peripheral is not supported by the existing infrastructure bundle, it will not be supported via Server Pack. Peripheral support requires an infrastructure bundle upgrade. Server Pack provides flexibility by allowing new server platforms to be added without the operational overhead of a full domain firmware upgrade.

Light Weight Upgrades

Introduced in Cisco UCS Manager Release 3.1(3), Light Weight Upgrades enhance firmware upgrades by:

• Updating a component's firmware only if it has been modified.
• Providing security updates through service packs.
• Allowing updates within a service pack to apply to specific components, potentially without a fabric interconnect reboot.

Previously, patch releases involved downloading and activating the complete firmware bundle, leading to unnecessary updates and reboots.

Service Packs

Service packs are patches for applying security updates to Cisco UCS Manager infrastructure and server components. They are specific to a base release and cannot be installed independently.

A service pack is a single bundle for infrastructure and server components. Updates can be applied via Infrastructure and Server Auto Install. In Release 3.1(3), service packs offer non-disruptive updates for infrastructure components (though fabric interconnect reboots may be needed for specific fixes like OpenSSL). Server component updates are disruptive and require downtime.

Service packs are cumulative for a maintenance release, containing all fixes from previous service packs for that release. Service packs can be removed or updated via the Cisco UCS Manager GUI or CLI.

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

Service Pack Versions

Guidelines for service pack versions:

• A service pack can only be applied to its base bundle (e.g., 3.1(3)SP2 on 3.1(3), not 3.1(4)).
• Version numbering in separate maintenance releases is unrelated (e.g., 3.1(3)SP2 and 3.1(4)SP2 are distinct).
• The same fix may be available in separate service packs for different maintenance releases.
• Service packs are cumulative; the latest version includes fixes from earlier ones (e.g., 3.1(3)SP3 includes fixes from 3.1(3)SP2 and 3.1(3)SP1).
• Downgrading service packs to versions below the default is not permitted.
• If a service pack upgrade or downgrade fails, the default service pack version for that maintenance release becomes the running version.

Example:

• Base Bundle Version: 3.1(3b)
• Default Service Pack Version: 3.1(3)SP2(Default)
• Running Service Pack Version: 3.1(3)SP3

Service Pack Rollback

A service pack applied to a base release can be rolled back. The following scenarios describe changes to bundle and service pack versions during rollback:

Remove Service Pack

• Bundle Version: No change.
• Service Pack Version: Reverts to the default version included with the bundle.

Downgrade Infrastructure Bundle to an Earlier Maintenance Release

• Bundle Version: Changes to the earlier maintenance release version.
• Service Pack Version: Removed, as it is not valid for the earlier release.

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

• Bundle Version: Changes to the version of the maintenance release patch.
• Service Pack Version: Removed if a corresponding service pack version is not specified during Auto-Install for an upgrade or downgrade.

Guidelines and Restrictions for Service Packs

• If upgrading from one service pack requiring an FI reboot to another requiring an FI reboot, the FI will reboot twice.
• Server Auto Sync Policy is not supported for service packs.
• Auto sync of a service pack is not supported if the subordinate FI runs a release earlier than 3.1(3).

Firmware Auto Sync for FI Cluster

When adding a secondary Fabric Interconnect (FI) to form a cluster (replacement or standby to HA), the infrastructure bundle firmware versions must match. Firmware Auto Sync allows administrators to automatically upgrade or downgrade the infrastructure bundle to match the survivor FI's version when the replacement is added as standby to HA. This feature requires the software package (firmware) on the survivor FI to be Cisco UCS Release 1.4 or later, and the Fabric Interconnects must be of the same model number.

Implementation: Previously, users had to manually configure the replacement FI in standalone mode if versions mismatched. With Auto Sync, users can synchronize software packages of the replacement FI with the survivor FI. The survivor FI's packages are copied to the replacement FI, activated, and then the FI is added to the cluster. Database and configuration synchronization occurs through usual mechanisms after the HA cluster is formed.

Firmware Auto Sync Benefits: Ensures the replacement FI matches the survivor's revision with minimal user interaction and clear feedback.

Options for Firmware Upgrades

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

Note: For detailed upgrade steps, refer to the appropriate Cisco UCS upgrade guide. Contact Cisco Technical Assistance Center (TAC) if no guide is provided, as direct upgrades may not be supported.

Upgrading a Cisco UCS Domain through Cisco UCS Manager

Choose from the following upgrade options:

• Upgrade infrastructure and servers with Auto Install: Upgrades all infrastructure components first using Auto Install, then server endpoints via host firmware packages.
• Upgrade servers through firmware packages in service profiles: Upgrades all server endpoints in a single step, reducing disruption. Can be combined with deferred deployment for maintenance windows.
• Direct upgrades of infrastructure and server endpoints: Upgrades many components directly (fabric interconnects, I/O modules, adapters, board controllers). Not available for all endpoints (e.g., storage controller, HBA firmware). These require host firmware packages within service profiles.
• Upgrade chassis through chassis firmware packages in chassis profiles: Upgrades all S3260 Chassis endpoints in a single step.

Note: Chassis profiles and firmware packages apply only to S3260 Chassis.

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

Upgrade S3260 Chassis and servers via Cisco UCS Manager using:

• Upgrade infrastructure components through Auto Install: Single-step upgrade for infrastructure components like UCS Manager software and fabric interconnects.
• Upgrade chassis through chassis firmware packages in chassis profiles: Single-step upgrade for all chassis endpoints.
• Upgrade servers through firmware packages in service profiles: Single-step upgrade for server endpoints, reducing disruption. Can be combined with deferred deployment for maintenance windows.

Direct firmware upgrades are possible for infrastructure, chassis, and server endpoints, including fabric interconnects, SAS expanders, CMCs, chassis adapters, storage controllers, and board controllers. However, direct upgrade is not available for all endpoints, including storage controllers, HBA firmware, HBA option ROM, and local disk.

Upgrading a Cisco UCS Domain through Cisco UCS Central

Manage and upgrade all firmware components across registered Cisco UCS domains via Cisco UCS Central. This centralizes control and ensures all domains meet required firmware levels. Cisco UCS Central can upgrade capability catalogs, infrastructure, and host firmware globally for all registered domains configured for global firmware management. Direct endpoint firmware upgrades are not possible; use host firmware policies within global service profiles.

Options for Service Pack Updates

Upgrade Cisco UCS firmware to a service pack using these methods:

• Upgrade to a service pack through Infrastructure 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 Auto Install

Auto Install automates Cisco UCS domain upgrades to specified firmware versions in a single package, through distinct stages:

• Install Infrastructure Firmware: Uses the Cisco UCS Infrastructure Software Bundle to upgrade infrastructure components like fabric interconnects, I/O modules, and Cisco UCS Manager. Figure 5 illustrates the recommended process flow.
• Install Server Firmware: Uses Cisco UCS B-Series Blade Server Software Bundle or Cisco UCS C-Series Rack-Mount UCS-Managed Server Software Bundle to upgrade servers.

These stages are independent and can be scheduled separately. Auto Install can upgrade infrastructure and server components to different versions. Cisco recommends using Auto Install and Fabric Evacuation for Cisco UCS domain upgrades.

Figure 5: Process Flow for Automatically Installing Infrastructure Firmware

This flowchart outlines the automated infrastructure firmware installation process. It begins with creating configuration and full-state backups, downloading software packages, and disabling Smart Call Home. The process then checks if all paths are working and if UCSM faults are service-impacting. If faults exist, they must be resolved. The flow continues by checking the HA status of both fabric interconnects. If HA is ready, it proceeds to initiate Auto Install. If not, it identifies and resolves issues. The process includes steps for checking physical connectivity, acknowledging activation, and verifying new faults. If paths are not working, it prompts to check physical connectivity and resolve issues.

Firmware Upgrades through Firmware Packages in Service Profiles

Server firmware and BIOS updates across multiple servers are typically manual, serial, and time-consuming. Using host firmware packages within a service profile template allows for parallel upgrades. Changes to the template automatically update instantiated service profiles and associated servers.

Firmware on I/O modules, fabric interconnects, or Cisco UCS Manager cannot be upgraded via service profiles; direct upgrade is required.

Direct Firmware Upgrade at Endpoints

Following the correct procedure ensures direct firmware upgrades and activation are minimally disruptive. Firmware can be directly upgraded on various components depending on the target chassis:

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

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

Figure 6: Process Flow for Manually Installing Infrastructure Firmware

This flowchart details the manual infrastructure firmware installation process. It starts with creating backups and downloading packages. Key steps include evacuating subordinate and primary fabric interconnects, activating them, migrating management services, and verifying connectivity and faults. The process involves checking HA status, identifying components, and disabling evacuation.

Adapter and board controller firmware can also be upgraded via host firmware packages in service profiles, reducing server reboots. Upgrades via service profiles take precedence over direct upgrades; direct upgrades require removing the firmware package from the service profile.

Firmware Upgrade While Migrating from Cisco UCS 6200 Series Fabric Interconnects to Cisco UCS 6454 Fabric Interconnects

Follow these guidelines when migrating:

• Upgrade Cisco UCS 6200 Series fabric interconnects to Cisco UCS Manager Release 4.0(1) or later.
• The Cisco UCS 6454 fabric interconnect must have the same build version as the 6200 Series interconnect it replaces.
• Migration is supported from 6200 Series to 6454 Series, but not vice-versa. Migration is also not supported between:
• Cisco UCS 6332 and 6332 16UP fabric interconnects
• Cisco UCS 6332 and 6454 fabric interconnects
• Cisco UCS 6332 16UP and 6454 fabric interconnects
• All fabric interconnects must share the same kickstart, system, and UCSM image versions.

Note: UCS 6400 Series fabric interconnects use a unified image for kickstart and system images.

• Upgrade the fabric interconnect before upgrading to a new FEX or virtual interface card.
• For cluster configurations, fabric interconnects must have symmetrical connection topologies with FEXes.
• Standalone installations should expect downtime, as fabric interconnect upgrades are traffic disruptive.
• Perform a full configuration and software backup before this hardware upgrade.

Software Feature Configuration Changes for Cisco UCS 6454 Fabric Interconnects

The Cisco UCS 6454 Fabric Interconnects do not support certain features previously available on UCS 6200 and 6300 Series in Cisco UCS Manager 3.2 and earlier:

• Chassis Discovery Policy in Non-Port Channel Mode (6454 supports only Port Channel mode).
• Multicast Hardware Hash.
• Service Profiles with Dynamic vNICs.
• Multicast Optimize for QoS.
• NetFlow.
• Port profiles and DVS Related Configurations.

Feature configurations have changed for Cisco UCS 6454 Fabric Interconnects:

• Unified Ports: Cisco UCS 6454 supports up to 8 unified ports (configurable as FC), appearing at the module's beginning. UCS 6200 Series has all ports as unified. Ethernet ports must be contiguous, followed by contiguous FC Ports.
• VLAN Optimization: On Cisco UCS 6454, VLAN port count optimization occurs via port VLAN (VP) grouping when the PV count exceeds 16000.

When the Cisco UCS 6454 Fabric Interconnect is in Ethernet switching mode:

• VLAN Port Count Optimization Enabled is not supported.
• Supports 16000 PVs when VLAN Port Count Optimization is Disabled.
• Reserves 128 additional VLANs for system purposes.

Firmware Upgrade to Cisco UCS Manager Release 4.0

Scenarios for Firmware Upgrade to Cisco UCS Manager Release 4.0

Upgrading the Infrastructure software bundle (A bundle) directly to Cisco UCS Manager Release 4.0(x) is supported from Release 2.2(8) and 3.1(3) and later. For Cisco UCS Mini, direct upgrade to 4.0(x) is supported from Release 3.1(3) and later.

Table 5: Upgrade Paths to Release 4.0

Important: You can replace an FI in a cluster with one running Cisco UCS Manager Release 2.1(2) or later and upgrade it directly to 3.2(x) using Auto Sync, without needing to upgrade to 2.2(8) first.

Prerequisites for Upgrade to Cisco UCS Manager Release 4.0

• Ensure existing infrastructure and server bundles are on Cisco UCS Manager Release 2.2(8) or 3.1(3) or later. For Cisco UCS Mini, upgrade to 4.0 from any 3.1(3) or 3.2(x) release.
• Ensure the key ring in use has a modulus size of 2048 bits or more. Verify using commands:

UCS-A# scope security
UCS-A /security # scope keyring keyring-name
UCS-A /security/keyring # show detail

If the default key ring has a modulus size less than 2048 bits, reconfigure it:

UCS-A# scope security
UCS-A /security # scope keyring default
UCS-A /security/keyring # set modulus mod2048
UCS-A /security/keyring # set regenerate yes
UCS-A /security/keyring # commit-buffer
UCS-A /security/keyring # show detail

If a non-default key ring has a modulus size less than 2048 bits, delete it and create a new one with a modulus value of 2048 bits or more.

Note: A key ring in use cannot be deleted. Configure HTTPS to use another key ring first.

Cisco UCS Manager Release 3.1 and later do not support key rings with modulus sizes less than 2048 bits.

Conditions Under Which Upgrade to Cisco UCS Manager Release 4.0 Fails

Upgrades to Cisco UCS Manager Release 4.0 may fail due to:

• Insufficient free space in fabric interconnect partitions (less than 20% in /var/sysmgr or /bootflash, or less than 30% in /mnt/pss).
• Cisco UCS Manager validation failures from misconfiguration.

SNMP is Automatically Disabled During Upgrade

SNMP is automatically disabled during upgrades to Cisco UCS Manager Release 4.0. SNMP operations are suspended until the upgrade of both fabric interconnects is complete. Cisco recommends restarting SNMP operations only after both fabric interconnects are upgraded.

Firmware Upgrade to a Minor or a Patch Release

Cisco UCS Manager release numbers follow a pattern: major release identifier, minor release identifier, and patch release identifier (e.g., 4.0(2a) where 4.0 is major, 2 is minor, and 'a' is the patch). Upgrades to maintenance releases and patches within a major release are performed identically to major release upgrades.

Firmware Downgrades

Firmware downgrades are performed similarly to upgrades; the selected package or version determines the operation. Downgrading from Cisco UCS Manager Release 4.0 is not possible with Cisco UCS 6454 fabric interconnects.

Cisco UCS Domain with UCS M5 Servers

When downgrading Cisco UCS Manager from Release 3.2(1) to earlier versions on UCS M5 servers, you must decommission the M5 servers first, as they are only supported by Release 3.2(1) and later. Failure to do so will cause validation to fail, prompting server decommissioning.

Board Controller Firmware for Blade Servers

Important: Board controller firmware for Cisco UCS B-Series blade servers is not designed to be downgraded. If an error message like 'Error: Update failed: Server does not support board controller downgrade' appears during a full system downgrade, it can be safely ignored. Cisco UCS Manager will automatically skip the board controller firmware and proceed with other components. The board controller firmware version should be the same as or later than the installed software bundle version.

Unsupported Features Must Be Unconfigured Before Downgrade

Before downgrading, unconfigure any features from the current release that are not supported in the target earlier release. Failure to do so may result in features not working or the downgrade failing.

SNMP Must be Disabled Before Downgrade

SNMP must be disabled before downgrading from Cisco UCS Manager Release 3.2 to an earlier release. The downgrade process will not start until SNMP is disabled.

Recommended Order of Steps for Firmware Downgrades

1. Retrieve the configuration backup from the release to which you want to downgrade.
2. Unconfigure features not supported in the target release.
3. Create Full State and All Configuration backup files.
4. Downgrade Cisco UCS Manager.
5. Perform an erase-config.
6. Import the configuration backup from the downgraded release.

Firmware Management in Cisco UCS Central

Cisco UCS Central enables centralized management of all firmware components for registered Cisco UCS domains. To manage firmware, the global firmware management option must be enabled in Cisco UCS Manager during registration. This option can be turned on or off as needed.

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

Domains are categorized into domain groups for management. Firmware can be managed at the domain group level or from the domain group root. Cisco UCS Central supports management of:

• Capability Catalog: One catalog per domain group, used by all registered domains within that group.
• Infrastructure Firmware: One infrastructure firmware policy per domain group, defining the version used by all registered domains.
• Host Firmware: Multiple host firmware policies can exist per domain group, allowing domains to select policies. Cisco UCS Central can upgrade host firmware globally across all domains in a group simultaneously.

Note: For more details, refer to the 'Firmware Management' chapters in the Cisco UCS Central Administration Guide and Cisco UCS Central CLI Reference Manual.