Cisco UCS Manager
Cisco UCS™ Manager, release 3.1 provides unified, embedded management of all software and hardware components of the Cisco Unified Computing System™ (Cisco UCS) across multiple chassis, Cisco UCS servers, and thousands of virtual machines. Cisco UCS Manager manages Cisco UCS as a single entity through an intuitive GUI, a command-line interface (CLI), or an XML API for comprehensive access to all Cisco UCS Manager functions. For more information on Cisco UCS Manager, see Cisco UCS Manager on Cisco.com.
This document contains information on new features, resolved caveats, open caveats, and workarounds for Cisco UCS Manager, Release 3.1. This document also includes the following:
-
Current information that became available after the technical documentation was published
-
Related firmware and BIOSes on blade, rack and modular servers and other Cisco Unified Computing System (UCS) components associated with the release
Support for Web User Interface Post Deprecation of Adobe Flash
The Web user interface of Cisco UCS Manager releases earlier than 3.1(3a) — including the releases on the 2.2 release train — are Java-based and may not be accessible on browser versions that will deprecate support for Adobe Flash on Dec 31, 2020. For more details on the problem description and workarounds, refer to the Field Notice: FN72012.
Revision History
Release |
Date |
Description |
---|---|---|
3.1(1e) |
January 20, 2016 |
Created release notes for Cisco UCS Manager, Release 3.1(1e). |
January 22, 2016 |
Updated Cisco UCS Central integration requirements. |
|
February 15, 2016 |
Updated release notes to include support for Cisco UCS 420 M4 on Cisco UCS Mini. |
|
March 9, 2016 |
Updated release notes to include support for 3.8TB 2.5 inch Enterprise Value 6G SATA SSD. Added CSCuy46062 to 3.1(1e) Behavior Changes and Known Limitations. |
|
May 18, 2018 |
Updated the Resolved Caveats for Release 3.1(1e) with CSCun07367. |
|
May 28, 2018 |
Updated the Open Caveats for Release 3.1(1e) with CSCvj59299, CSCvj59301, CSCvj54880, CSCvj54847, CSCvj54187, and their Software Advisory. |
|
3.1(1g) |
March 31, 2016 |
Updated release notes for Cisco UCS Software Release 3.1(1g). |
April 05, 2016 |
Updated release notes to include support for UCS-IOM-2304 on Cisco UCS Chassis N20-C6508. |
|
April 18, 2016 |
Updated release notes for key ring modulus size support. Updated list of power supplies for Cisco UCS FIs. |
|
3.1(1h) |
May 20, 2016 |
Updated release notes for Cisco UCS Software Release 3.1(1h). |
May 24, 2016 |
Added CSCuz74973 to the Open Caveats for Cisco UCS Software Release 3.1(1e). |
|
June 14, 2016 |
Updated the versions for the first bundle affected in the Open Caveats section for Cisco UCS Software Release 3.1(1e). |
|
June 17, 2016 |
Corrected a note regarding UCS-ML-1X324RU-G and UCS-ML-1X644RU-G support. |
|
June 20, 2016 |
Corrected a note regarding UCS-ML-1X324RV-A and UCS-ML-1X644RV-A support. |
|
June 21, 2016 |
Added section for Cisco UCS Mini support. |
|
3.1(1k) |
August 29, 2016 |
Updated release notes for Cisco UCS Software Release 3.1(1k). |
3.1(2b) |
September 17, 2016 |
Updated release notes for Cisco UCS Software Release 3.1(2b). |
September 19, 2016 |
Added CSCvb35827 to the Open Caveats for Cisco UCS Software Release 3.1(2b). |
|
September 22, 2016 |
Added CSCvz91263 to the Security Fixes section. |
|
September 26, 2016 |
Added CSCvb44879 to the Open Caveats section for Cisco UCS Software Release 3.1(2b). |
|
September 27, 2016 |
Updated New Software Features for 3.1(2b) section for VXLAN support. |
|
October 13, 2016 |
Added CSCuy13596 to the Resolved Caveats section for Cisco UCS Software Release 3.1(2b). |
|
May 18, 2018 |
Updated the Resolved Caveats for Release 3.1(2b) with CSCun07367. |
|
3.1(2c) |
October 7, 2016 |
Updated release notes for Cisco UCS Software Release 3.1(2c). |
3.1(2e) |
November 23, 2016 |
Updated release notes for Catalog Release 3.1.2e.T. |
3.1(2e) |
December 23, 2016 |
Updated release notes for Cisco UCS Software Release 3.1(2e). |
3.1(1l) |
January 26, 2017 |
Updated release notes for Cisco UCS Software Release 3.1(1l). |
3.1(2f) |
February 28, 2017 |
Updated release notes for Cisco UCS Software Release 3.1(2f). |
3.1(2g) |
April 19, 2017 |
Updated release notes for Cisco UCS Software Release 3.1(2g). |
3.1(3a) |
April 27, 2017 |
Updated release notes for Cisco UCS Software Release 3.1(3a). |
May 02, 2017 |
Removed CSCvd71484 from the Resolved Caveats section for Cisco UCS Software Release 3.1(3a). |
|
June 25, 2018 |
Added CSCvf32853 to the Open Caveats section for Cisco UCS Software Release 3.1(3a). |
|
February 27, 2019 |
Updated the information for CSCvf32853 in the Open Caveats section for Cisco UCS Software Release 3.1(3a). |
|
3.1(2h) |
June 29, 2017 |
Updated release notes for Cisco UCS Software Release 3.1(2h). |
3.1(3b) |
June 29, 2017 |
Updated release notes for Cisco UCS Software Release 3.1(3b). |
3.1(3c) |
July 24, 2017 |
Updated release notes for Cisco UCS Software Release 3.1(3c). |
3.1(3d) |
October 13, 2017 |
Updated release notes for Cisco UCS Software Release 3.1(3d). |
3.1(3e) |
November 29, 2017 |
Updated release notes for Cisco UCS Software Release 3.1(3e). |
December 4, 2017 |
Updated the Upgrade and Downgrade Guidelines section for the minimum supported S3260 release. |
|
3.1(3f) |
March 21, 2018 |
Updated release notes for Cisco UCS Software Release 3.1(3f). |
3.1(3h) |
May 14, 2018 |
Updated release notes for Cisco UCS Software Release 3.1(3h). |
July 6, 2018 |
Updated the Cross-Version Firmware Support to for 2.2(7) and 2.2(8) B and C bundles. |
|
3.1(3j) |
July 20, 2018 |
Updated release notes for Cisco UCS Software Release 3.1(3j). |
August 27, 2018 |
Added the L1 Terminal Fault caveats — CSCvm02934, CSCvm03356, CSCvm03351, and CSCvm03339 — to the list of Security Fixes. |
|
3.1(3k) |
September 11, 2018 |
Updated release notes for Cisco UCS Software Release 3.1(3k). |
June 3, 2019 |
Added a known limitation - UCS 6300 Series Fabric Interconnect ASIC Limitation with Passive Cables. |
|
3.1(3l) |
January 13, 2020 |
Updated release notes for Cisco UCS Software Release 3.1(3l). |
December 20, 2020 |
Added notice: Support for Web User Interface Post Deprecation of Adobe Flash. |
Top Reasons to Move to Cisco UCS Manager Release 3.1
Here are the top reasons to move to Cisco UCS Manager Release 3.1:
-
Support for new hardware, including UCS 6332 Series Fabric Interconnects, S3260 storage servers, Secure Encrypted Drives, and numerous peripherals.
-
Support for HTML5 user interface.
-
Support for HTML5 KVM client to facilitate improved management of KVM.
-
Cisco UCS Manager Release 3.1(3) is the patch point for the Cisco UCS Manager 3.1 release train.
New Features in Release 3.1
Cisco UCS Manager, Release 3.1 is a unified software release for all supported UCS hardware platforms. The release adds support for HTML5 interface in addition to the Java interface, both of which are available across all platforms.
Note |
Beginning with Cisco UCS Manager Release 3.1(3a), the Cisco UCS Manager GUI is no longer available as a Java-based application. |
New Hardware Features
-
New Hardware in Release 3.1(3l) — None
-
New Hardware in Release 3.1(3k) — None
-
New Hardware in Release 3.1(3j) — None
-
New Hardware in Release 3.1(3h) — None
-
New Hardware in Release 3.1(3e) — None
-
New Hardware in Release 3.1(3c) — None
-
New Hardware in Release 3.1(3b) — None
-
New Hardware in Release 3.1(2h) — None
-
New Hardware in Release 3.1(2g) — None
-
New Hardware in Release 3.1(2f) — None
-
New Hardware in Release 3.1(2c) — None
-
New Hardware in Release 3.1(1l) — None
-
New Hardware in Release 3.1(1k) — None
-
New Hardware in Release 3.1(1h) — None
New Software Features
-
New Software Features in Release 3.1(3l) — None
-
New Software Features in Release 3.1(3k) — None
-
New Software Features in Release 3.1(3j) — None
-
New Software Features in Release 3.1(3h) — None
-
New Software Features in Release 3.1(3e) — None
-
New Software Features in Release 3.1(3d) — None
-
New Software Features in Release 3.1(3b) — None
-
New Software Features in Release 3.1(2h) — None
-
New Software Features in Release 3.1(2g) — None
-
New Software Features in Release 3.1(2f) — None
-
New Software Features in Release 3.1(2e) — None
-
New Software Features in Release 3.1(2c) — None
-
New Software Features in Release 3.1(1l) — None
-
New Software Features in Release 3.1(1k) — None
-
New Software Features in Release 3.1(1h) — None
-
New Software Features in Release 3.1(1g) — None
New Hardware in Release 3.1(3f)
Support for the following drives:
-
UCS-HD300G10K12G
-
UCS-HD600G10K12G
-
UCS-HD1T7K12G
-
UCS-HD2T7K12G
-
UCS-HD12T7KL6GHA
-
UCS-HD12T7KL4KHM
-
UCS-HD8T7KL4KSM
-
UCS-HD10T7KL4KSM
-
UCS-HY480GIS3-EP
-
UCS-HY19TIS3-EP
-
UCS-S3260-HD12T
-
UCS-S3260-HD12TR
-
UCS-SD400GH3-EP
-
UCS-SD800GH3-EP
-
UCS-SD16TH3-EP
-
UCS-SD32TH3-EP
-
UCS-SD38TBIS6-EV
-
UCS-SD480GBIS6-EV
-
UCS-SD960GBIS6-EV
-
UCS-SD480GIS3-EP
-
UCS-SD960GIS3-EP
-
UCS-SD19TIS3-EP
-
UCS-S3260-3SSD4
-
UCS-S3260-3SSD8
-
UCS-S3260-3SSD16
-
UCS-S3260-3SSD32
-
UCS-S3260-NVM48
-
UCS-S3260-NVM416
-
UCS-S3260-NVM432
-
UCS-S3260-NVM464
New Hardware in Release 3.1(3d)
-
Support for the following drives:
-
UCS-HD8T7KL6GA
-
UCS-HD10T7KL6GA
-
UCS-S3260-G3SD24
-
UCS-S3260-G3SD48
-
UCS-S3260-G3SD160
-
UCS-HY400GSAS3-EP
-
UCS-HY800GSAS3-EP
-
UCS-HY16TSAS3-EP
-
UCS-SD240GBKS4-EB
-
UCS-SD120GBKS4-EB
-
UCS-SD480GBKS4-EB
-
UCS-SD16TBKS4-EB
-
-
Support for the following NVMe drives:
-
UCSC-NVMEM4-H800
-
UCSC-NVMEM4-H1600
-
UCSC-NVME-H32003
-
UCSC-NVME-H64003
-
UCSC-NVME-H76801
-
New Hardware in Release 3.1(3a)
-
Support for Second RAID Controller in the IO Expander on Cisco UCS S3260 (UCS-C3K-M4RAID)
-
Support for Dual HBA Controller on Cisco UCS S3260 (UCS-S3260-DHBA)
-
Support for the following Qlogic adapters:
-
Support for Qlogic QLE2742 dual-port 32G FC (UCSC-PCIE-QD32GF)
-
Support for Qlogic QLE2562 dual-port 8G FC (N2XX-AQPCI05)
-
Inventory support for Qlogic QLE2672 dual-port 16G FC (UCSC-PCIE-Q2672)
Note
Only inventory support, not management support.
-
-
Support for the following Emulex adapters:
-
Support for Emulex LPe32002 dual-port 32G FC (UCSC-PCIE-BD32GF)
-
Support for Emulex LPe32001 single-port 32G (UCSC-PCIE-BS32GF)
-
Support for Emulex LPe16002 dual-port 16G (UCSC-PCIE-E16002)
-
Support for Emulex LPe12002 dual-port 8G (N2XX-AEPCI05)
-
-
Support for Intel X550 dual-port 10GBase-T adapter (UCSC-PCIE-ID10GC)
-
Support for the following NVIDIA GPUs:
-
Support for NVIDIA M10 32GB GPU (UCSC-GPU-M10)
-
Support for NVIDIA P100 16GB GPU (UCSC-GPU-P100-16G)
-
Support for NVIDIA P100 12GB GPU (UCSC-GPU-P100-12G)
-
-
Support for AMD Firepro S7150x2 16GB GPU (UCSC-GPU-7150x2)
New Hardware in Release 3.1(2e)
Support for the following CPUs:
-
UCS-CPU-E52699AE
-
UCS-CPU-E78894E
Support for the following new drives:
-
UCS-SD480GBKS-EV
-
UCS-SD19TBKSS-EV
New Hardware in Release 3.1(2b)
-
Cisco UCS Manager support for the Cisco UCS S3260 system—The Cisco UCS S3260 is a modular, dense storage rack server with dual server nodes, optimized for large data sets used in environments such as big data, cloud, object storage, and content delivery. The Cisco UCS S3260 system is designed to operate in a standalone environment and, starting with Cisco UCS Manager 3.1(2b), as part of the Cisco Unified Computing System with Cisco UCS Manager integration. Cisco UCS C3260 Server Integration with Cisco UCS Manager, Release 3.1 provides detailed information.
-
Cisco UCS B260 and B460 M4 shipping with Intel® Xeon® Processor E7-4800 v4 and E7-8800 v4 series CPUs
-
Cisco UCS Mini support introduced for Cisco UCS B260 and B460 M4
-
Cisco UCS B420 M4 shipping with Intel® Xeon® Processor E5-4600 v4 series CPUs
-
Cisco UCS C460 M4 shipping with Intel® Xeon® Processor E7-8800 v4 series CPUs
-
Support for the following CPUs:
-
UCS-CPU-E5-4610E
-
UCS-CPU-E5-4620E
-
UCS-CPU-E5-4627E
-
UCS-CPU-E5-4640E
-
UCS-CPU-E5-4650E
-
UCS-CPU-E5-4655E
-
UCS-CPU-E5-4660E
-
UCS-CPU-E5-4667E
-
UCS-CPU-E5-4669E
-
UCS-CPU-E52650E
-
UCS-CPU-E74809E
-
UCS-CPU-E74820E
-
UCS-CPU-E74830E
-
UCS-CPU-E74850E
-
UCS-CPU-E78860E
-
UCS-CPU-E78867E
-
UCS-CPU-E78870E
-
UCS-CPU-E78880E
-
UCS-CPU-E78890E
-
UCS-CPU-E78891E
-
UCS-CPU-E78893E
-
-
Support for the following Intel® NIC adapters:
-
UCSC-PCIE-IQ10GF
-
UCSC-PCIE-ID10GF
-
UCSC-PCIE-ID40GF
-
-
Support for the following new NVMe-based PCIe storage options:
-
HGST HH-HL PCIe cards for all Cisco UCS M4 rack servers:
-
Cisco UCS (SN150) HH-HL 1900 GB NVMe-based PCIe SSD (UCSC-F-H19001)
-
Cisco UCS (SN150) HH-HL 3800 GB NVMe-based PCIe SSD (UCSC-F-H38001)
-
-
Intel HH-HL PCIe cards for all Cisco UCS M4 rack servers:
-
Cisco UCS (P3700) HH-HL 800 GB NVMe-based PCIe SSD (UCSC-F-I80010)
-
Cisco UCS (P3700) HH-HL 1600 GB NVMe-based PCIe SSD (UCSC-F-I160010)
-
Cisco UCS (P3600) HH-HL 2000 GB NVMe-based PCIe SSD (UCSC-F-I20003)
-
-
HGST 2.5” PCIe SSDs for all Cisco UCS M4 rack servers:
-
Cisco UCS (SN100) 2.5” 3800 GB NVMe-based PCIe SSD (UCS-PCI25-38001)
-
-
Intel 2.5” PCIe SSD for Cisco UCS B200 M4 blade servers and all Cisco UCS M4 rack servers:
-
Cisco UCS (P3700) 2.5” 400 GB NVMe-based PCIe SSD (UCS-PCI25-40010)
-
Cisco UCS (P3600) 2.5” 800 GB NVMe-based PCIe SSD (UCS-PCI25-8003)
-
Cisco UCS (P3700) 2.5” 800 GB NVMe-based PCIe SSD (UCS-PCI25-80010)
-
Cisco UCS (P3600) 2.5” 1600 GB NVMe-based PCIe SSD (UCS-PCI25-16003)
-
-
-
Support for 4K format disk drives as bootable drives on blade servers with Cisco UCS Manager Release 3.1(2b) and later versions.
-
Support for a 10 TB 512e disk drive (UCS-HD10T7KEM). 512e drives are 4K disk drives that can emulate a block size of 512 bytes to maintain compatibility with legacy computing components.
-
SAS HBA management support for the following:
-
Cisco UCS SAS 9300-8e 12Gb/s SAS HBA (Pass-through ) (UCSC-SAS9300-8e)
-
Cisco 12G Modular SAS HBA (Pass-through) (UCSC-SAS12GHBA) on Cisco UCS C220 M4 and C240 M4 servers
-
Cisco 12G Modular SAS HBA (Pass-through) (UCSC-PSAS12GHBA) on Cisco UCS C220 M4 and C240 M4 servers
-
-
Support for NVIDIA GPU M60 adapter on Cisco UCS C460 M4 servers
-
Support for Magma Expander on Cisco UCS C460 M4 servers
-
Support for the following SED drives:
-
SFF—2.5” HDD:
-
UCS-HD300G10K9 300GB 12G SAS 10K RPM SFF HDD (SED)
-
UCS-HD600G15K9 600GB 12G SAS 15K RPM SFF HDD (SED)
-
UCS-HD12G10K9 1.2 TB 12G SAS 10K RPM SFF HDD (SED)
-
UCS-HD18G10K9 1.8TB 12G SAS 10K RPM SFF HDD (4K,SED)
-
-
LFF—3.5” HDD:
-
UCS-HD600G15CK9 600GB 12G SAS 15K PM LFF HDD (SED)
-
UCS-HD4TBK9 4TB SAS 7.2K RPM LFF SED HDD
-
UCS-HD4T12GK9 4TB 12G SAS 7.2K RPM LFF HDD (SED)
-
UCS-HD6T12GAK9 6TB 7.2K RPM LFF HDD (4K, SED)
-
-
SFF—2.5” SSD:
-
UCS-SD400GBK9 400GB Enterprise Perf 12G SAS SFF SED SSD
-
UCS-SD400GBEK9 400GB Enterprise Perf SAS SFF SSD (10X FWPD, SED)
-
UCS-SD800GBEK9 800GB Enterprise Perf SAS SFF SSD (10X FWPD, SED)
-
UCS-SD16TBEK9 1.6TB Enterprise Perf SAS SFF SSD (10XFWPD, SED)
-
UCS-SD600GBE3K9 600GB Enterprise Perf SATA SFF SSD (3X FWPD, SED)
-
UCS-SD120GBE1K9 120GB Ent Value SFF SSD (SATA) (1X FWPD, SED)
-
UCS-SD480GBE1K9 480GB Enterprise Value SATA SFF SSD (1XFWPD, SED)
-
UCS-SD960GBE1K9 960GB Enterprise Value SATA SFF SSD (1X FWPD, SED)
-
-
LFF—3.5” SSD:
-
UCS-SD400GBCK9 400GB Enterprise Perf SAS LFF SSD (10X FWPD, SED)
-
UCS-SD800GBCK9 800GB Enterprise Perf SAS LFF SSD (10X FWPD, SED)
-
-
-
Cisco UCS 6300 switches
-
Cisco UCS M-Series servers are no longer supported with Cisco UCS Manager Release 3.1(2b) and later releases.
New Hardware in Release 3.1(1g)
-
Cisco UCS B200 M4, C220 and C240 servers shipping with Intel® Xeon® Processor E5-2600 v4 series CPUs.
-
Support for Emulex adapter (UCSC-PCIE-E14102B).
-
Support for the following CPUs for Cisco UCS B200 M4, C220 M4, and C240 M4 servers:
-
UCS-CPU-E52699E
-
UCS-CPU-E52698E
-
UCS-CPU-E52697AE
-
UCS-CPU-E52697E
-
UCS-CPU-E52695E
-
UCS-CPU-E52690E
-
UCS-CPU-E52683E
-
UCS-CPU-E52680E
-
UCS-CPU-E52667E
-
UCS-CPU-E52660E
-
UCS-CPU-E52658E
-
UCS-CPU-E52650E
-
UCS-CPU-E52650LE
-
UCS-CPU-E52640E
-
UCS-CPU-E52637E
-
UCS-CPU-E52630E
-
UCS-CPU-E52630LE
-
UCS-CPU-E52623E
-
UCS-CPU-E52637E
-
UCS-CPU-E52620E
-
UCS-CPU-E52609E
-
Please see the software advisory for this release.
New Hardware in Release 3.1(1e)
3rd Generation Fabric Interconnects
-
Support for 3rd Generation Fabric Interconnects (UCS 6332 FI, UCS 6332–16UP FI) and UCS IOM 2304
-
Support for Cisco Nexus 2348UPQ FEX
-
Support for 3rd Generation Cisco VIC 1385 in Cisco UCS Manager
-
Support for 3rd Generation VIC 1387 (40G PCIe/mLOM VIC Adapter)
Servers, Cartridge and Peripherals
-
Support for CSB-MEZ-INT8955 on B200-M4
-
Support for UCSB-GPU-M6 (Tesla) on B200-M4
Note
Certain NVIDIA Graphics Processing Units (GPU) do not support Error Correcting Code (ECC) and vGPU together. Cisco recommends that you refer to the release notes published by NVIDIA for the respective GPU to know whether it supports ECC and vGPU together.
-
Support fo PCIe SSD on B200 M4
-
Support for LSI 9286CV-8e RAID Controller ( UCS-RAID9286CV-8E )
-
Support for M-Series Broadwell DE/LGA Compute Cartridges
-
Support for UCS Mini Secondary Chassis
-
Support for QLogic QLE8442 10Gb Dual port 10GBaseT network adapter
-
Support for QLogic QLE8442 10Gb Dual port SFP+ network adapter
-
Support for NVIDIA GPU M60 adapter on Cisco UCS C240 M4 servers
Note
Certain NVIDIA Graphics Processing Units (GPU) do not support Error Correcting Code (ECC) and vGPU together. Cisco recommends that you refer to the release notes published by NVIDIA for the respective GPU to know whether it supports ECC and vGPU together.
-
Support for additional Fusion IO adapters
-
Support for Cisco UCS C240 NEBS Rack Server
-
Support for VIC 1385 network adapter
-
Support for VIC 1387 network adapter
-
Support for 3.8TB 2.5 inch Enterprise Value 6G SATA SSD (UCS-SD38TBKS4-EV)
New Software Features in Release 3.1(3f)
-
TPM 2.0 Firmware Update Capability—A new platform BIOS in the UCS Manager 3.1(3f) patch release fixes the security vulnerability with TPM 2.0 (CVE-2017-15361) for Cisco Unified Computing M4 and M5 servers.
New Software Features in Release 3.1(3c)
-
Cisco HyperFlex Support for SED Security Policies and KMIP—Self-Encrypting Drives (SEDs) have a special hardware that encrypts incoming data and decrypts outgoing data in real-time. A media encryption key controls this encryption and decryption. SEDs need to be locked by providing a security key identifier and a security key. The security key is used to encrypt the media encryption key. You can configure security keys locally, or remotely using a KMIP server. In this release, Cisco HyperFlex HX-Series servers support SED security policies and KMIP. The SED security policies and KMIP configuration must be performed only through the Cisco HyperFlex HX Connect user interface.
New Software Features in Release 3.1(3a)
-
The number of active VLANs per Cisco UCS domain was increased to 3000 for Cisco UCS 6332 fabric interconnects.
-
The number of appliance ports per fabric interconnect was increased to 16 for Cisco UCS 6200 and UCS 6332 fabric interconnects.
-
The number of primary VLANs supported in a PVLAN domain was increased from 50 to 150 for Cisco UCS 6200 Series fabric interconnects. The ratio of secondary VLANs to primary VLANs was increased from 30:1 to 200:1 for Cisco UCS 6200 Series fabric interconnects.
-
Integrated Server Diagnostics—The Cisco UCS Manager diagnostics tool enables you to verify the health of the hardware components on your servers. It also provides a variety of tests to exercise and stress the various hardware subsystems on the servers, such as memory and CPU.
-
Light Weight Upgrades—Cisco UCS Manager Release 3.1(3) introduces light weight upgrades, which delivers security updates for infrastructure and server components through a common service pack bundle. In some cases, UCS Manager service packs may be applied to the UCS fabric interconnects (infrastructure A bundle) without involving a UCS fabric interconnect reboot.
-
S3260 Rebranding—Beginning with Cisco UCS Manager Release 3.1(3), Cisco UCS C3260/C3X60 is renamed to Cisco UCS S3260. You may still see certain components in the system labeled as C3260/C3X60. For this release, the terms S3260 and C3260/C3X60 are used interchangeably. Both, S3260 and C3260/C3X60, refer to the same hardware component.
-
Server SIOC Connectivity functionality—A Cisco UCS S3260 system now supports Server SIOC Connectivity functionality. Using this functionality, you can configure the data path through both the primary and auxiliary SIOCs when the chassis has a single server and dual-SIOC setup.
-
Second RAID Controller and Dual HBA Controller—Cisco UCS S3260 systems support the following:
-
Second RAID controller in the optional I/O expander module
-
Dual HBA Controller
In a Cisco UCS S3260 system, both servers should have either dual RAID controllers or dual HBA controllers. Different controller types in servers are not supported.
-
-
SED Security Policies and KMIP Support—Self-Encrypting Drives (SEDs) have a special hardware that encrypts incoming data and decrypts outgoing data in real-time. A media encryption key controls this encryption and decryption. SEDs need to be locked by providing a security key identifier and a security key. The security key is used to encrypt the media encryption key. You can configure security keys locally, or remotely using a KMIP server. In this release, Cisco UCS Manager supports SEDs on Cisco UCS C-Series and S-Series servers.
-
Smart SSD—Cisco UCS Manager Release 3.1(3) introduces support for monitoring SSD health. This feature provides statistical information about various SSD properties. For each property, a minimum, maximum, and average value is recorded and displayed. This feature also allows you to provide a threshold limit for each property.
-
Automatic Configuration of FI-Server Ports—Starting with Cisco UCS Manager Release 3.1(3a), you can use a policy and configure the Fabric Interconnect to automatically change unconfigured ports to server ports when a UCS server is directly attached to the Fabric Interconnect.
-
Fabric Evacuation with Auto Install—Starting with Cisco UCS Manager Release 3.1(3), you can use fabric evacuation during Auto Install. If you use fabric evacuation with Auto Install, and fabric evacuation was enabled on the fabric interconnect before Auto Install, fabric evacuation is disabled after Auto Install is complete.
-
Custom User Label—Service Profiles now have a custom label field that is visible to the operating system or hypervisor running on the server through the SMBIOS asset tag field.
-
HTML5 KVM User Interface Support—Cisco UCS Manager Release 3.1(3) introduces the redesigned HTML5 user interface to facilitate improved management of KVM. HTML5 KVM is only for M3 servers and onwards running Cisco UCS Manager Release 3.1(3). M3 rack servers support HTML5 KVM in Cisco UCS Manager-managed mode only. The minimum Web browser version required for HTML5 KVM is Chrome 45, Firefox 45, IE 11, Opera 35, and Safari 9. For best results, use the latest browser version.
-
Power Transaction Enhancement—The Power Transaction Log was added which logs the last five server power transitions, the power transition source timestamp of the latest power transition, and the count of the last consecutive server power transitions from the same source.
-
VXLAN Offload—VXLAN with Receive Side-Scaling (RSS) stateless offload is supported on VIC adapters 1340, 1380, 1385, 1387, and SIOC on Cisco UCS C3260 for RHEL 7.0, CENTOS 7.0, SLES 12 SP2 and later releases. VXLAN offload is not supported for IPv6.
-
Board Aggregation Role—The Board Aggregation Role is a new feature added to identify the master and slave slots. This only applies to Cisco UCS B460 M4 blade servers.
-
Hardware Change Discovery Policy—This policy configures Cisco UCS Manager behavior when a hardware component changes. When Cisco UCS Manager detects any change in the server hardware component, a critical “hardware inventory mismatch” fault is raised. You must acknowledge the server to clear the fault and complete the hardware inventory. After you have acknowledged the server, deep discovery and deep association is triggered.
-
Cisco HyperFlex Systems Extended Support—This release supports further integration of Cisco HyperFlex Systems with Cisco UCS Manager through improved setup capabilities for HyperFlex Systems with Cisco UCS. HyperFlex Systems add support for the following Cisco UCS Manager features:
-
Automatic Configuration of FI-Server Ports—Enables you to automatically configure the fabric interconnect server ports.
-
SED Security Policies—Enables you to configure local security keys for Self-Encrypting Drives (SEDs).
-
-
Cisco UCS Manager Database Health Monitoring—Cisco UCS Manager provides proactive health check and recovery mechanisms to improve the integrity of the Cisco UCS Manager database. These mechanisms enable active monitoring of the database health.
-
Graphics Card Policies—You can now create a graphics card policy and configure the various modes for the graphics card.
-
VLAN Groups in vNIC Templates—You can select VLAN groups in addition to any individual VLAN, while creating a vNIC template.
-
Virtual Volume Support—Virtual volume support is now supported for ESXi 5.5 and higher.
-
Disk Group Policy Enhancement—With this disk group policy enhancement, you can now include JBOD drives in a disk group policy to create LUNs.
New Software Features in Release 3.1(2b)
-
Chassis Profile and Chassis Firmware Pack—Cisco UCS Manager now supports chassis profiles and chassis firmware packs to update the chassis components in Cisco UCS S3260 systems.
-
Disk Zoning—You can assign chassis level storage disk drives to the server nodes in a Cisco UCS S3260 system by using disk zoning policy.
-
Factory Reset of Servers—Cisco UCS Manager enables you to reset a server to its factory settings. By default, the factory reset operation affects only the BIOS and not the storage drives and FlexFlash drives. This is to prevent any loss of data. However, you can choose to reset these devices to a known state as well.
-
Chassis Management Controller (CMC) Secure Boot—Cisco UCS Manager enables support of CMC secure boot for Cisco UCS S3260 systems. When CMC secure boot is enabled, only Cisco-signed firmware images can be installed and run on the CMC.
-
vNIC Redundancy Pair—Supports two vNICs/vHBAs that are being configured with a common set of parameters through the vNIC/vHBA template pair. This prevents the configuration between two vNICs/vHBAs from going out of sync. Multiple vNIC/vHBA pairs can be created from the same vNIC/vHBA template pair.
- VXLAN with Receive Side-Scaling (RSS) Support for ESX 6.x—Cisco UCS Manager Release 3.1(2b) now supports VXLAN with RSS stateless offload on VIC adapters 1340, 1380, 1385, 1387, and the SIOCs on Cisco UCS S3260 for ESXi 6.0 and later releases. VXLAN offload is not supported for IPv6.
-
Consistent Device Naming (CDN) support for Red Hat Enterprise Linux—CDN support has been expanded to include Red Hat Enterprise Linux 6.X and Red Hat Enterprise Linux 7.X.
-
Host Firmware Package Enhancement—Local disk firmware is excluded from the host firmware package by default.
-
SAS Expander Support—Cisco UCS Manager Release 3.1(2b) and later releases support direct firmware upgrade and downgrade on SAS expanders for Cisco UCS C240, C220, and C460 M4 servers.
-
B-Series and C-Series Server Firmware Bundle Enhancement – In releases earlier than Cisco UCS Manager Release 3.1(2b), firmware for endpoints that were common to both the B-Series and C-Series server software bundles was available only in the B-Series server software bundle. Starting with Cisco UCS Manager Release 3.1(2b), the firmware for these common endpoints is available in both the B-Series and C-Series server software bundles. With this enhancement, customers using only C-series servers need not download the B-Series server firmware bundle anymore.
Note
Selecting only one of B-Series or C-Series package versions while using auto-install may impact the endpoints that are common to both blade and rack mount servers. To selectively update only blade or rack mount servers, select the appropriate firmware packages and review the impacted endpoints to ensure that there are no unexpected firmware changes or server reboots.
-
Power Management Enhancements—Cisco UCS Manager Release 3.1(2b) introduces the following enhancements:
-
Power management support for Cisco UCS C220 M4 and C240 M4 rack servers.
-
Power group support for Fabric Interconnects and Fabric Extenders.
-
-
Cisco usNIC—Libfabric support for Cisco usNIC in Open MPI. To benefit from Cisco usNIC, your applications must use the Message Passing Interface(MPI), or Libfabric interface instead of sockets or other communication APIs.
-
FC Zones Enhancement—Support for creating and deleting user-defined FC zones and FC zone profiles.
-
Ability to perform Cisco UCS Manager initial configuration without console connectivity based on DHCP lease availability.
-
Multicast Hardware Hash—In a port channel, by default, ingress multicast traffic on any port in the fabric interconnect selects a particular link between the IOM and the fabric interconnect to egress the traffic. To reduce potential issues with the bandwidth, and to provide effective load balancing of the ingress multicast traffic, hardware hashing is used for multicast traffic. When multicast hardware hashing is enabled, all links between the IOM and the fabric interconnect in a port channel can be used for multicast traffic.
-
Preserving the following properties during backup or import operations:
-
User-defined labels for Chassis, FEX, Rack Servers, IOMs and Blade Servers
-
Assigned IDs for Chassis, FEX and Rack Servers
-
-
NVMe PCIe SSD Inventory—Cisco UCS Manager discovers, identifies, and displays the inventory of Non-Volatile Memory Express (NVMe) Peripheral Component Interconnect Express (PCIe) SSD storage devices. You can view the health of the storage devices in the server. NVMe with PCIe SSD storage devices reduce latency, increase input/output operations per second (IOPS), and lower power consumption compared to SAS or SATA SSDs.
Note
Hot insertion and removal of NVMe SSD are not supported.
NVMe boot is not supported from Cisco UCS Manager.
-
Support for 160 LDAP Group Maps—Cisco UCS Manager now supports a maximum of 160 LDAP group maps.
-
Power Synchronization between Servers and Their Associated Service Profiles —Cisco UCS Manager includes a global (default) power sync policy to synchronize the power state between the associated service profiles and the servers when the desired power state of the service profile differs from the actual power state of the server.
-
Graceful Shutdown—When you acknowledge a server reboot using the graceful shut down options or a change in the service profile that requires the server reboot, Cisco UCS Manager waits until the time specified time in the maintenance policy before performing a hard shut down.
-
HA Version Holder Replacement—You can now specify preferred HA version holders. When you trigger a reelection of version holders, these new preferred HA devices are selected first.
Note
HA version holder replacement is not supported on Cisco UCS Mini.
-
FNIC tunables now has two new options that are available for fibre channel adapter policies for Windows environments.
-
IO Retry Timeout—This option adjusts the IO retry timeout after a pending command expires on a network device.
-
LUN Queue Depth—This setting adjusts the initial queue depth for all LUNs on the adapter.
-
-
HTML 5 Interface User Interface Improvements—Introduced the redesigned Cisco UCS Manager HTML 5 user interface to facilitate improved management of the Cisco UCS Manager ecosystem.
-
Out of Band Disk Inventory for SAS HBA—Cisco UCS now supports out-of-band inventory of disks connected to a SAS HBA 12G storage controller.
-
Drive Sled Based PID Determination—A drive sled, which is provided with a disk drive, is the electrical and mechanical contact of the disk with the slot. A PID is assigned to this combination of disk drive and sled. Disk slots for rack servers are different from the disk slots for Cisco UCS S3260 systems. Therefore, the same disk will have different drive sleds for rack servers and Cisco UCS S3260 systems, and, during inventory, will display different PIDs based on the server where it is found.
-
Cisco UCS Manager 3.1(2) introduces the capability to detect and alert users to issues relating to 40Gb link quality.
-
Attention
Starting with Cisco UCS Manager Release 3.1(2b), Cisco UCS Manager no longer supports management of Cisco UCS M-Series servers.
New Software Features in Release 3.1(1e)
-
Cisco UCS 6332 and 6332-16UP fabric interconnect with B-Series and C-Series Servers
-
128 LDAP group support
-
Cisco UCS Mini network scale improvements including support for a second UCS Chassis in a UCS Mini deployment
-
HTML5 user interface support for UCS 6332, UCS 6332 16UP, UCS 6248UP and UCS 6296UP and UCS 6324 fabric interconnects. This includes search option that enables you to search for entities in the system from this location. Using this search option, you can perform Create, List and View actions.
-
The option to exclude components has been added to Host Firmware Packages.
-
Maintenance Policy provides a On Next Boot option
-
Firmware upgrade checks the VIF/interface status after the fabric interconnect upgrade
-
Locator LED support for server hard-disks
-
Provision to reset peer IOM modules to factory defaults
-
Provision to suppress VIF down alert (code: F0283) when server OS is shutdown or server is powered off
-
Prevent firmware upgrade if unsupported or deprecated hardware components are in the Cisco UCS hardware configuration
-
Enhanced Health Monitoring includes low kernel memory and parity errors
-
Enhanced Power Capping across all platforms includes power supply redundancy method for 220 V (Watts) and 110 V (Watts), power management during Power ON operations
-
WellsBurg PCH support in Cisco UCS Manager
-
vnic template CDN feature enhancement
-
Cisco SSL FOM 4.1 version support (replacing open SSL)
-
Common criteria compliance and FIPS compliance certification
-
CSDL vulnerability and PSIRT fixes
-
SHA-2 certificate support has been added
Deprecated Hardware, Software, and Third Party Adapters Support in Cisco UCS Manager
Deprecated Hardware
Starting with Cisco UCS Manager Release 3.1(3a), Cisco UCS Manager does not support the hardware listed in the following table:
Hardware Type |
Product |
---|---|
Adapters - Blade Servers |
UCSB-MEZ-ELX-03 |
UCSB-MEZ-QLG-03 |
|
N20-AE0102 |
|
N20-AQ0102 |
|
Blade Servers |
B250 M2 (N20-B6625-2) |
Starting with Cisco UCS Manager Release 3.1(2b), Cisco UCS Manager does not support the hardware listed in the following table:
Hardware Type |
Product |
---|---|
Chassis |
UCSME-4308 modular chassis |
Cartridges |
UCSME-M142 |
UCSME-1414 |
|
UCSME-2814 |
Starting with Cisco UCS Manager Release 3.1(1e), Cisco UCS Manager does not support the hardware listed in the following table:
Hardware Type |
Product |
---|---|
Fabric Interconnects |
UCS 6120 (N10-S6100) UCS 6140 (N10-S6200) |
IO Modules |
2104 FEX (N20-I6584) |
Blade Servers |
B200 M1 (N20-B6620-1) B250 M1 (N20-B6620-2) B230 M1 (N20-B6730-1) B440 M1 (N20-B6740-2) |
Adapters |
E M71KR-E (N20-AE0002) Q M71KR-Q (N20-AQ0002) Intel 82598KR (N20-AI0002) M81KR (N20-AC0002) Broadcom M51KR-B BCM 57711 Mezz (N20-AB0002) |
Rack Mount Servers |
C210 M2 (R210-2121605W) C460 M2 (UCSC-BASE-M2-C460) C200 M2 (UCSC-BSE-SFF-C200) C250 M2 (R250-2480805W) C260 M2 (C260-BASE-2646) C420 M3 |
Adapters - Rack Servers |
N2XX-ACPCI01 Cisco UCS CNA M61KR-I Intel (N20-AI0102) Broadcom 57711 Dual Port (N2XX-ABPCI02) Cisco UCS P81E VIC (N2XX-ACPCI01) Emulex OneConnect OCe10102-F (N2XX-AEPCI01) Qlogic QLE 8152-CNA (N2XX-AQPCI01) |
Important |
Before you upgrade to Cisco UCS Manager, Release 3.1, you must decommission and remove all deprecated hardware from your system. If you have any deprecated hardware in your system, the infrastructure upgrade fails and rolls back to earlier release. Make sure to follow recommended upgrade guidelines in the Cisco UCS Manager Firmware Management Guide, Release 3.1, from Cisco UCS Manager Configuration Guides. |
Deprecated Software
Cisco UCS Manager Java GUI—Beginning with Cisco UCS Manager Release 3.1(3a), the Cisco UCS Manager GUI is no longer available as a Java-based application.
VM-FEX— Release 3.1(1e) does not support ESXi configuration on VM FEX. However, support has been added from Release 3.1(1g).
Deprecated Third Party Adapters
Adapter |
Release |
Support for Cisco UCS FI 6200 Series |
Support for Cisco UCS FI 6332, 6332-16UP, and Cisco UCS 6324 |
---|---|---|---|
UCSC-PCIE-ID10GF |
3.1(2b) |
Yes |
Yes |
UCSC-PCIE-ID40GF |
3.1(2b) |
— |
Yes |
UCSC-PCIE-IQ10GF |
3.1(2b) |
— |
— |
UCSB-MEZ-QLG-03 |
3.1(1g) |
Yes |
— |
UCSB-MEZ-ELX-03 |
3.1(1g) |
Yes |
— |
N20-AQ0102 |
3.1(1g) |
Yes |
— |
N20-AE0102 |
3.1(1g) |
Yes |
— |
Cisco UCS Manager and Cisco UCS C-Series Release Compatibility Matrix for C-Series Rack-Mount Servers
Cisco UCS C-Series Rack-Mount Servers are managed by built-in standalone software— Cisco Integrated Management Controller(Cisco IMC). However, when a C-Series Rack-Mount Server is integrated with Cisco UCS Manager, the Cisco IMC does not manage the server anymore.
Each Cisco UCS Manager release incorporates its corresponding C-Series Standalone release and some previous C-Series standalone releases. For example, Cisco UCS Manager Release 3.1(1) is integrated with C-Series Standalone Release 2.0(10) for C220 and C240 M4 servers, and Release 2.0(9) for all other M3 and M4 servers. Hence, it supports all the M4 and M3 servers supported by C-Series Standalone releases. The Internal Dependencies section provides a detailed list of servers supported by Cisco UCS Manager.
The following table lists the Cisco UCS Manager and C-Series software standalone releases for C-Series Rack-Mount Servers:
Cisco UCS Manager Release |
C-Series Standalone Release Included |
C-Series Servers Supported by the C-Series Standalone Releases |
---|---|---|
3.1(3f) - 3.1(3l) |
3.0(4) |
All M3/M41 |
3.1(3a) - 3.1(3e) |
3.0(3) |
All M3/M42 |
3.1(2) |
2.0(13) |
All M3/M4 |
3.1(1) |
2.0(10) |
C220 M4, C240 M4 only |
2.0(9) |
All other M3/M4 |
|
2.2(8) |
2.0(12) |
C460 M4 only |
2.0(10) |
C220 M4, C240 M4 only |
|
1.5(9) |
C420-M3, C260-M2, C460-M2 only |
|
2.0(9) |
For all other M3/M4 |
|
2.2(7) |
2.0(10) |
C220 M4, C420 M4 only |
1.5(8) |
C420 M3, C260 M2, C460 M2 only |
|
2.0(8) |
For all other M3/M4 |
|
2.2(6) |
1.5(8) |
C420 M3, C260 M2, C460 M2 only |
2.0(8) |
For all other M3/M4 |
|
2.2(5) |
1.5(7) |
C420 M3, C260 M2, C460 M2 only |
2.0(6) |
For all other M3/M4 |
|
2.2(4) |
1.5(7) |
C420 M3, C260 M2, C460 M2 only |
2.0(4) |
For all other M3/M4 |
|
2.2(3) |
1.5(7) |
C420 M3, C260 M2, C460 M2 only |
2.0(3) |
For all other M3/M4 |
Cisco UCS Mini Support
The following feature introduced in Cisco UCS Manager, Release 3.1(2b) is not supported on Cisco UCS Mini:
-
HA Version Holder Replacement
The following features for Cisco UCS Mini are not supported in Cisco UCS Manager, Release 3.1(1e) and later releases:
-
Traffic Monitoring Session for SAN
-
MAC Security
-
Private VLAN
-
VXLAN
-
NVGRE
-
usNIC
-
VLAN Compression
System Requirements
Cisco UCS Manager and KVM Launch Manager GUI are available only as HTML5-based applications. You can launch the KVM console from the Cisco UCS Manager GUI or KVM Launch Manager GUI as a Java application or an HTML5-based application.
The Java-based KVM client requires Java Runtime Environment (JRE) 1.7.x or higher.
Important |
Beginning with Cisco UCS Manager Release 3.1(3a), the Cisco UCS Manager GUI is no longer available as a Java-based application. |
Cisco UCS Central Integration
Cisco UCS Manager Release 3.1 can only be registered with Cisco UCS Central, Release 1. 4 or higher.
Supported Operating Systems
Operating System |
Minimum Required Memory |
---|---|
Microsoft Windows 7 or higher |
8.0 GB |
Red Hat Enterprise Linux 5.10 or higher for M3 servers Red Hat Enterprise Linux 6.4 or higher for M4 servers |
8.0 GB |
Mac OS X 10.9 or higher |
8.0 GB |
Supported Web Browsers
Cisco UCS Manager GUI |
Web Browsers |
---|---|
HTML5 |
Microsoft Internet Explorer 11 or higher Mozilla Firefox 45 or higher Google Chrome 45 or higher Apple Safari version 9 or higher Opera version 35 or higher |
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).
The following table lists the mixed A, B, and C bundle versions that are supported on Cisco UCS 6200 and 6300 fabric interconnects:
Infrastructure Versions (A Bundles) |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Host FW Versions (B or C Bundles) |
2.2(1) |
2.2(2) |
2.2(3) |
2.2(4) |
2.2(5) |
2.2(6) |
2.2(7) |
2.2(8) |
3.1(1) |
3.1(2) |
3.1(3) |
|
2.2(1) |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
|
2.2(2) |
— |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
|
2.2(3) |
— |
— |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
|
2.2(4) |
— |
— |
— |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
|
2.2(5) |
— |
— |
6200
|
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
||
2.2(6) |
— |
— |
— |
6200¹ |
6200¹ |
6200 |
6200 |
6200 |
6200 |
6200 |
6200 |
|
2.2(7) |
— |
— |
— |
6200¹ |
6200¹ |
6200¹ |
6200 |
6200 |
6200 |
6200 |
6200 |
|
2.2(8) |
— |
— |
— |
6200¹ |
6200¹ |
6200¹ |
6200 |
6200 |
6200 |
6200 |
6200 |
|
3.1(1) |
— |
— |
— |
— |
— |
— |
— |
— |
6200,6332, 6332-16UP |
6200,6332, 6332-16UP |
6200,6332, 6332-16UP |
|
3.1(2) |
— |
— |
— |
— |
— |
— |
— |
— |
6200,6332, 6332-16UP |
6200,6332, 6332-16UP |
6200,6332, 6332-16UP |
|
3.1(3) |
— |
— |
— |
— |
— |
— |
— |
— |
6200,6332, 6332-16UP |
6200,6332, 6332-16UP |
6200,6332, 6332-16UP |
Note |
For M1, M2, M3 servers, only N, N-1 cross-version firmware is supported. For example, for B200 M3 servers, the 2.2(4)A bundle will be supported with 2.1(1)B, 2.1(2)B, 2.1(3)B, 2.2(1)B, 2.2(2)B, 2.2(3)B, and 2.2(4)B bundles). |
The following table lists the mixed A, B, and C bundle versions that are supported on Cisco UCS Mini fabric interconnects:
Infrastructure Versions (A Bundles) |
|||||||
---|---|---|---|---|---|---|---|
Host FW Versions (B or C Bundles) |
3.0(1) |
3.0(2) |
3.1(1) |
3.1(2) |
3.1(3) |
||
3.0(1) |
6324 |
6324 |
6324 |
6324 |
6324 |
||
3.0(2) |
— |
6324 |
6324 |
6324 |
6324 |
||
3.1(1) |
— |
— |
6324 |
6324 |
6324 |
||
3.1(2) |
— |
— |
6324 |
6324 |
6324 |
||
3.1(3) |
— |
— |
6324 |
6324 |
6324 |
The following table lists the mixed B, C bundles that are supported on all platforms with 3.1 bundle:
Infrastructure Versions (A Bundles) |
|||
---|---|---|---|
Host FW Versions (B, C, or M Bundles) |
3.1(1) |
||
6200 |
6300 |
6324 |
|
ucs-k9-bundle-infra. 3.1.x.xxx.A.bin | ucs-6300-k9-bundle-infra. 3.1.x.xxx.A.bin | ucs-mini-k9-bundle-infra. 3.1.x.xxx.A.bin | |
2.2(1), 2.2(2), 2.2(3), 2.2(4), 2.2(5), 2.2(6) (B, C Bundles) |
Yes |
— |
— |
2.2(7), 2.2(8) (B, C Bundles) |
Yes |
— |
— |
2.5(1), 2.5(2) (M Bundle) |
Yes |
— |
— |
3.0(1), 3.0(2) (B, C Bundles) |
— |
— |
Yes |
3.1(1), 3.1(2), 3.1(3) (B, C Bundles) |
Yes |
Yes |
Yes |
3.1(1) (M Bundle) |
Yes |
— |
— |
Infrastructure Versions (A Bundles) |
|||
---|---|---|---|
Host FW Versions (B, C Bundles) |
3.1(2) |
||
6200 |
6300 |
6324 |
|
ucs-k9-bundle-infra. 3.1.x.xxx.A.bin | ucs-6300-k9-bundle-infra. 3.1.x.xxx.A.bin | ucs-mini-k9-bundle-infra. 3.1.x.xxx.A.bin | |
2.2(1), 2.2(2), 2.2(3), 2.2(4), 2.2(5), 2.2(6) (B, C Bundles) |
Yes |
— |
— |
2.2(7), 2.2(8) (B, C Bundles) |
Yes |
— |
— |
3.0(1), 3.0(2) (B, C Bundles) |
— |
— |
Yes |
3.1(1), 3.1(2), 3.1(3) (B, C Bundles) |
Yes |
Yes |
Yes |
Infrastructure Versions (A Bundles) |
|||
---|---|---|---|
Host FW Versions (B, C Bundles) |
3.1(3) |
||
6200 |
6300 |
6324 |
|
ucs-k9-bundle-infra. 3.1.x.xxx.A.bin | ucs-6300-k9-bundle-infra. 3.1.x.xxx.A.bin | ucs-mini-k9-bundle-infra. 3.1.x.xxx.A.bin | |
2.2(1), 2.2(2), 2.2(3), 2.2(4), 2.2(5), 2.2(6) (B, C Bundles) |
Yes |
— |
— |
2.2(7), 2.2(8) (B, C Bundles) |
Yes |
— |
— |
3.0(1), 3.0(2) (B, C Bundles) |
— |
— |
Yes |
3.1(1), 3.1(2), 3.1(3) (B, C Bundles) |
Yes |
Yes |
Yes |
Important |
If you implement cross-version firmware, you must ensure that the configurations for the Cisco UCS domain are supported by the firmware version on the server endpoints. |
Minimum Bundle Version Requirements for Cisco UCS Manager Features
The following Cisco UCS Manager 3.1 features require the specified minimum B,C bundle version to perform expected operations:
Feature |
Bundle version |
---|---|
Maintenance Policy provides a On Next Boot option |
3.1(1e) |
Enhanced Health Monitoring includes low kernel memory and parity errors |
3.1(1e) |
Enhanced Power Capping across all platforms includes power supply redundancy method for 220 V (Watts) and 110 V (Watts), power management during Power ON operations |
3.1(1e) |
Locator LED support for server hard-disks |
3.1(1e) |
Internal Dependencies
The following sections provide information on the interdependencies between Cisco UCS hardware and versions of Cisco UCS Manager.
-
Version dependencies for Server FRU items such as DIMMs depend on the server type.
-
Chassis items such as fans and power supplies work with all versions of Cisco UCS Manager.
6200 Series and 6332 Fabric Interconnects and Components
Blade Servers
Note |
In a mixed firmware configuration, we recommend that the minimum server bundle corresponds to the Minimum Software Version. The infrastructure must be at or above the Minimum Software Version. |
Servers |
Minimum Software Version UCS 6200 Series FI |
Minimum Software Version UCS 6332, 6332-16UP FI |
Minimum Software Version UCS 6332, 6332-16UPFI |
Recommended Software Version UCS 6200 Series FI UCS 6332, 6332-16UP FI |
---|---|---|---|---|
UCS-IOM-2204 UCS-IOM-2208 |
UCS-IOM-2204 UCS-IOM-2208 |
UCS-IOM-2304 |
UCS-IOM-2204 UCS-IOM-2208 UCS-IOM-2304 |
|
B22 M3 E5-2400 B22 M3 E5-2400 v2 |
2.2(1b) 2.2(2e) |
3.1(1e) 3.1(1e) |
3.1(1e) |
3.1(3l) |
B200 M2 |
2.2(2e) |
3.1(1e) |
3.1(1e) |
3.1(3l) |
B200 M3 E5-2600 B200 M3 E5-2600 v2 |
2.2(1b) 2.2(2e) |
3.1(1e) 3.1(1e) |
3.1(1e) |
3.1(3l) |
B200 M4 |
2.2(3a) |
3.1(1e) |
3.1(1e) |
3.1(3l) |
B230 M2 |
2.2(1b) |
3.1(1e) |
3.1(1e) |
3.1(3l) |
B260 M4 E7-2800 v2 B260 M4 E7-4800 v2 B260 M4 E7-8800 v2 B260 M4 E7-4800 v3 B260 M4 E7-8800 v3 |
2.2(2e) 2.2(2e) 2.2(2e) 2.2(5d) 2.2(5d) |
3.1(1e) 3.1(1e) 3.1(1e) 3.1(1e) 3.1(1e) |
3.1(1e) |
3.1(3l) |
B260 M4 E7-4800 v4 B260 M4 E7-8800 v4 |
2.2(8b) 2.2(8b) |
3.1(2b) 3.1(2b) |
3.1(2b) 3.1(2b) |
3.1(3l) |
B420 M3 E5-4600 B420 M3 E5-4600 v2 |
2.2(1b) 2.2(2e) |
3.1(1e) 3.1(1e) |
3.1(1e) |
3.1(3l) |
B440 M2 |
2.2(1b) |
3.1(1e) |
3.1(1e) |
3.1(3l) |
B420 M4 E5-4600 v3 B420 M4 E5-4600 v4 |
2.2(5d) 2.2(8b) |
3.1(1e) 3.1(2b) |
3.1(1e) 3.1(2b) |
3.1(3l) 3.1(3l) |
B460 M4 E7-4800 v2 B460 M4 E7-8800 v2 B460 M4 E7-4800 v3 B460 M4 E7-8800 v3 |
2.2(2e) 2.2(2e) 2.2(5d) 2.2(5d) |
3.1(1e) 3.1(1e) 3.1(1e) 3.1(1e) |
3.1(1e) |
3.1(3l) |
B460 M4 E7-4800 v4 B460 M4 E7-8800 v4 |
2.2(8b) 2.2(8b) |
3.1(2b) 3.1(2b) |
3.1(2b) |
3.1(3l) |
Rack Servers
Servers |
Minimum Software Version UCS 6200 Series FI |
Minimum Software Version UCS 6332, 6332-16UP |
Minimum Software Version UCS 6332, 6332-16UP |
Recommended Software Version UCS 6200 Series FI UCS 6332, 6332-16UP FI |
---|---|---|---|---|
UCS-IOM-2204 UCS-IOM-2208 |
UCS-IOM-2204 UCS-IOM-2208 |
UCS-IOM-2304 |
UCS-IOM-2204 UCS-IOM-2208 UCS-IOM-2304 |
|
C22 M3 and M3L |
2.2(1b) |
3.1(1e) |
3.1(1e) |
3.1(3l) |
C24 M3, M3L, and M3S2 |
2.2(1b) |
3.1(1e) |
3.1(1e) |
3.1(3l) |
C220 M3 |
2.2(1b) |
3.1(1e) |
3.1(1e) |
3.1(3l) |
C220 M4 |
2.2(3h) |
3.1(1e) |
3.1(1e) |
3.1(3l) |
C240 M3 |
2.2(1b) |
3.1(1e) |
3.1(1e) |
3.1(3l) |
C240 M4 |
2.2(3h) |
3.1(1e) |
3.1(1e) |
3.1(3l) |
C460 M4 E7-2800 v2 C460 M4 E7-4800 v2 C460 M4 E7-8800 v2 C460 M4 E7-4800 v3 C460 M4 E7-8800 v3 |
2.2(2e) 2.2(2e) 2.2(2e) 2.2(5d) 2.2(5d) |
3.1(1e) 3.1(1e) 3.1(1e) 3.1(1e) 3.1(1e) |
3.1(1e) |
3.1(3l) |
C460 M4 E7-8800 v4 |
2.2(8b) |
3.1(2b) |
3.1(2b) |
3.1(3l) |
Adapters
Adapters |
Minimum Software Version UCS 6200 Series FI |
Minimum Software Version UCS 6332, 6332-16UP |
Minimum Software Version UCS 6332, 6332-16UP |
Recommended Software Version UCS 6200 Series FI UCS 6332, 6332-16UP FI |
---|---|---|---|---|
UCS-IOM-2204 UCS-IOM-2208 |
UCS-IOM-2204 UCS-IOM-2208 |
UCS-IOM-2304 |
UCS-IOM-2204 UCS-IOM-2208 UCS-IOM-2304 |
|
UCSC-PCIE-C40Q-03 UCSC-MLOM-C40Q-03 |
2.2(7b) |
3.1(1e) |
3.1(1e) |
3.1(3l) |
UCS-VIC-M82-8P UCSB-MLOM-40G-01 UCSB-MLOM-PT-01 |
2.2(1b) |
3.1(1e) |
3.1(1e) |
3.1(3l) |
UCSB-MLOM-40G-03 UCSB-VIC-M83-8P UCSC-MLOM-CSC-02 |
2.2(3a) |
3.1(1e) |
3.1(1e) |
3.1(3l) |
UCSC-PCIE-CSC-02 |
2.2(1b) |
3.1(1e) |
3.1(1e) |
3.1(3l) |
UCSC-F-FIO-1000MP UCSC-F-FIO-1300MP UCSC-F-FIO-2600MP UCSC-F-FIO-5200MP |
2.2(3a) |
3.1(1e) |
3.1(1e) |
3.1(3l) |
UCSB-FIO-1600MS UCSB-FIO-1300MS |
2.2(3a) |
3.1(1e) |
3.1(1e) |
3.1(3l) |
UCSC-INVADER-3108 UCSC-NYTRO-200GB |
2.2(3a) |
3.1(1e) |
3.1(1e) |
3.1(3l) |
UCSC-MLOM-C10T-02 UCSC-PCIE-C10T-02 UCSC-F-FIO-785M UCSC-F-FIO-365M UCSC-F-FIO-1205M UCSC-F-FIO-3000M UCSC-F-FIO1000PS UCSC-F-FIO1300PS UCSC-F-FIO2600PS UCSC-F-FIO5200PS UCSC-F-FIO-6400SS UCSC-F-FIO-3200SS |
2.2(4b) |
3.1(1e) |
3.1(1e) |
3.1(3l) |
UCS-MEZ-QLG-03 UCSB-MEZ-ELX-03 N20-AQ0102 N20-AE0102 |
2.2(3a) |
— |
— |
3.1(3l) |
UCS-PCIE-E14102B |
2.2(7b) |
— |
— |
3.1(3l) |
UCSC-PCIE-IQ10GF UCSC-PCIE-ID10GF UCSC-PCIE-ID40GF |
— |
— |
3.1(2b) |
3.1(3l) |
UCSC-F-I80010 UCSC-F-I12003 UCSC-F-I160010 UCSC-F-I20003 UCS-PCI25-40010 UCS-PCI25-8003 UCS-PCI25-80010 UCS-PCI25-16003 UCSC-F-H19001 UCSC-F-H38001 UCS-SDHPCIE800GB UCS-SDHPCIE16TB UCS-PCI25-38001 |
— |
— |
3.1(2b) |
3.1(3l) |
UCSC-PCIE-QD32GF N2XX-AQPCI05 UCSC-PCIE-Q2672 UCSC-PCIE-BD32GF UCSC-PCIE-BS32GF UCSC-PCIE-E16002 N2XX-AEPCI05 UCSC-PCIE-ID10GC |
— |
— |
3.1(3a) |
3.1(3l) |
Other Hardware
We recommend that you use the latest software version for all Chassis, Fabric Interconnects, Fabric Extenders, Expansion Modules and Power Supplies. To determine the minimum software version for your mixed environment, see Cross-Version Firmware Support. The following is the list of other supported hardware:
Type |
Details |
---|---|
Chassis |
UCS-S3260 N20–C6508 UCSB-5108-DC UCSB-5108-AC2 UCSB-5108-DC2 UCSB-5108-HVDC |
Fabric Interconnects |
UCS 6332UP UCS 6332-16UP |
Fabric Extenders |
UCS 2208XP UCS 2204XP Cisco Nexus 2232PP Cisco Nexus 2232TM-E UCS-IOM-2304 Cisco Nexus 2348UPQ |
Power Supplies |
UCSB-PSU-2500HVDC UCSB-PSU-2500DC48 UCSC-PSU-930WDC UCSC-PSU2V2-930WDC UCSC-PSUV2-1050DC UCSC-PSU1-770W UCSC-PSU1-1050W UCSC-PSU2-1400 UCSC-PSU2V2-1400W UCSC-PSU2V2-650W UCSC-PSU2V2-1200W UCSB-PSU-2500ACPL UCSB-PSU-2500ACDV N20-PAC5-2500W |
Note |
The 40G backplane setting is not applicable for 22xx IOMs. |
Type |
Details |
---|---|
Chassis |
UCS-S3260 N20–C6508 UCSB-5108-DC UCSB-5108-AC2 UCSB-5108-DC2 UCSB-5108-HVDC |
Fabric Interconnects |
UCS 6248UP UCS 6296UP |
Fabric Extenders |
UCS 2208XP UCS 2204XP Cisco Nexus 2232PP Cisco Nexus 2232TM-E |
Expansion Modules |
UCS-FI-E16UP |
Power Supplies |
UCSB-PSU-2500HVDC UCSB-PSU-25004DC48 UCSC-PSU-930WDC UCSC-PSU2V2-930WDC UCSC-PSUV2-1050DC UCSC-PSU1-770W UCSC-PSU1-1050W UCSC-PSU2-1400 UCSC-PSU2V2-1400W UCSC-PSU2V2-650W UCSC-PSU2V2-1200W UCSB-PSU-2500ACPL UCSB-PSU-2500ACDV N20-PAC5-2500W |
GB Connector Modules
The following is the list of Gb connector modules and supported cables:
GB Connector Modules |
Cables |
---|---|
40-GB for UCS 6300 Series Fabric Interconnects |
CVR-QSFP-SFP10G QSFP-40G-CSR4 QSFP-40G-LR4 QSFP-40G-LR4-S QSFP-40G-SR-BD QSFP-40G-SR4 QSFP-40G-SR4-S QSFP-4SFP10G-CU1M QSFP-4SFP10G-CU3M QSFP-4SFP10G-CU5M QSFP-4X10G-AC10M QSFP-4X10G-AC7M QSFP-4X10G-AOC10M QSFP-4X10G-AOC1M QSFP-4X10G-AOC2M QSFP-4X10G-AOC3M QSFP-4X10G-AOC5M QSFP-4X10G-AOC7M QSFP-H40G-ACU10M QSFP-H40G-ACU7M QSFP-H40G-AOC10M QSFP-H40G-AOC15M QSFP-H40G-AOC1M QSFP-H40G-AOC2M QSFP-H40G-AOC3M QSFP-H40G-AOC5M QSFP-H40G-AOC7M QSFP-H40G-CU1M QSFP-H40G-CU3M QSFP-H40G-CU5M |
16-GB |
DS-SFP-FC16G-LW DS-SFP-FC16G-SW |
10-GB |
SFP-10G-SR SFP-10G-LR SFP-H10GB-CU1M SFP-H10GB-CU3M SFP-H10GB-CU5M SFP-H10GB-ACU7M SFP-H10GB-ACU10M FET-10G 5SFP-10G-AOC1M SFP-10G-AOC2M SFP-10G-AOC3M SFP-10G-AOC5M SFP-10G-AOC7M SFP-10G-AOC10M |
8-GB (FC Expansion Module N10-E0060) |
DS-SFP-FC8G-SW DS-SFP-FC8G-LW |
4-GB (FC Expansion Module N10-E0080) |
DS-SFP-FC4G-SW DS-SFP-FC4G-LW |
1-GB |
GLC-TE GLC-T (V03 or higher) GLC-SX-MM GLC-LH-SM |
Cisco UCS Mini and Components
UCS Mini Supported Chassis
Chassis |
Minimum Software Version |
Recommended Software Version |
---|---|---|
UCSB-5108-AC2 |
3.0(1e) |
3.1(3l) |
UCSB-5108-DC2 |
3.0(2c) |
3.1(3l) |
UCS Mini Supported Blade and Rack Servers
Servers |
Minimum Software Version |
Recommended Software Version |
---|---|---|
B200 M3 |
3.0(1d) |
3.1(3l) |
B200 M4 |
3.0(2c) |
3.1(3l) |
B260 M4 |
3.1(2b) |
3.1(3l) |
B420 M3 |
3.0(2c) |
3.1(3l) |
B420 M4 |
3.1(1e) |
3.1(3l) |
B460 M4 |
3.1(2b) |
3.1(3l) |
B22 M3 |
3.0(2c) |
3.1(3l) |
C220 M3 |
3.0(1d) |
3.1(3l) |
C240 M3 |
3.0(1d) |
3.1(3l) |
C220 M4 |
3.0(2c) |
3.1(3l) |
C240 M4 |
3.0(2c) |
3.1(3l) |
UCS Mini Supported Adapters
Adapters |
Minimum Software Version |
Recommended Software Version |
---|---|---|
UCSC-PCIE-C40Q-03 UCSC-MLOM-C40Q-03 |
3.1(1e) |
3.1(3l) |
UCS-VIC-M82-8P UCSB-MLOM-40G-01 UCSB-MLOM-PT-01 |
3.0(1d) |
3.1(3l) |
UCSB-MLOM-40G-03 UCSB-VIC-M83P-8P UCSC-MLOM-CSC-02 |
3.0(2c) |
3.1(3l) |
UCSC-PCIE-CSC-02 |
3.0(1d) |
3.1(3l) |
UCS Mini Supported Fabric Interconnects
Fabric Interconnects |
Minimum Software Version |
Recommended Software Version |
---|---|---|
Cisco UCS 6324 |
3.1(1e) |
3.1(3l) |
UCS Mini Supported Fabric Extenders for Secondary Chassis
Fabric Extenders |
Minimum Software Version |
Recommended Software Version |
---|---|---|
UCS 2204 XP |
3.1(1e) |
3.1(3l) |
UCS 2208 XP |
3.1(1e) |
3.1(3l) |
UCS Mini Supported Power Supplies
Power Supplies |
Minimum Software Version |
Recommended Software Version |
---|---|---|
UCSB-PSU-2500ACDV UCSB-PSU-2500DC48 UCSC-PSU-930WDC UCSC-PSU2V2-930WDC UCSC-PSUV2-1050DC UCSC-PSU1-770W UCSC-PSU2-1400 UCSC-PSU2V2-1400W UCSC-PSU2V2-650W UCSC-PSU2V2-1200W |
3.0(1e) |
3.1(3l) |
UCS Mini Supported Gb Connector Modules
We recommend that you use the current software version for Gb port speed connections. The following is the list of Gb connector modules and supported cables:
Gb Connector Modules |
Cables |
---|---|
40-GB |
QSFP-4SFP10G-CU1M QSFP-4SFP10G-CU3M QSFP-4SFP10G-CU5M QSFP-4X10G-AC7M QSFP-4X10G-AC10M QSFP-4X10G-AOC1M QSFP-4X10G-AOC2M QSFP-4X10G-AOC3M QSFP-4X10G-AOC5M QSFP-4X10G-AOC7M QSFP-4X10G-AOC10M |
10-GB |
SFP-10G-LR SFP-10G-LR-X SFP-10G-SR SFP-10G-SR-X SFP-H10GB-CU1M SFP-H10GB-CU3M SFP-H10GB-CU5M SFP-H10GB-ACU7M SFP-H10GB-ACU10M SFP-10G-AOC1M SFP-10G-AOC3M SFP-10G-AOC5M SFP-10G-AOC7M SFP-10G-AOC10M |
8-GB |
DS-SFP-FC8G-SW DS-SFP-FC8G-LW |
4-GB |
DS-SFP-FC4G-SW DS-SFP-FC4G-LW |
1-GB |
GLC-GE-T GLC-LH-SM GLC-SX-MM GLC-T (V03 or higher) |
Modular Server and Components
The tables list the minimum server bundle recommended for this hardware in a mixed firmware configuration, assuming the infrastructure is at the recommended software version.
Important |
Cisco UCS Manager Release 3.1(2) and later releases do not support Cisco UCS M-Series Servers. |
Chassis
Recommended minimum software versions do not consider mixed environments. To determine the minimum software version for your mixed environment, refer to “Cross-Version Firmware Support”.
Chassis |
Minimum Software Version |
Recommended Software Version |
---|---|---|
UCSME-4308 |
2.5(1a) |
3.1(1l) |
Cartridges
To use a specific cartridge, Cisco UCS Manager, CMC, and the shared adapter must be upgraded to the recommended minimum software version for that cartridge.
Cartridges |
Minimum Software Version |
Recommended Software Version |
---|---|---|
UCSME-142-M4 |
2.5(1a) |
3.1(1l) |
UCSME-2814 |
2.5(2b) |
3.1(1l) |
UCSME-1414 |
2.5(2b) |
3.1(1l) |
Fabric Interconnect
Fabric Interconnect |
Minimum Software Version |
Recommended Software Version |
---|---|---|
UCS 6248UP |
2.5(1a) |
3.1(1l) |
UCS 6296UP |
2.5(1a) |
3.1(1l) |
Note |
Cisco UCS 6332 and UCS 6332-16UP Fabric Interconnects support is not available for Cisco M-Series Modular Servers. |
Power Supply
Power Supply |
Minimum Software Version |
Recommended Software Version |
---|---|---|
UCSC-PSU2-1400W |
2.5(1a) |
3.1(1l) |
UCSC-PSU2V2-1400W |
2.5(2b) |
3.1(1l) |
Capability Catalog
The Cisco UCS Manager Capability Catalog is a set of tunable parameters, strings, and rules. Cisco UCS uses the catalog to update the display and configurability of components such as newly qualified DIMMs and disk drives for servers.
The Capability Catalog is embedded in Cisco UCS Manager, but at times it is also released as a single image file to make updates easier.
The following table lists the PIDs added in this release and maps UCS software releases to the corresponding Capability Catalog file.
UCS Release |
Catalog File Name |
PIDs |
||||
---|---|---|---|---|---|---|
3.1(1e) |
ucs-catalog.3.1.1e.T.bin |
Blade GPU: UCSB-GPU-M6 GPU M60 adapter: UCSC-GPU-K80
Crypto Card: CSB-MEZ-INT8955 C240M4 NEBS SKU: UCSC-C240-M4SNEBS NVME SSD Drives:
Qlogic network adapters:
Cisco UCS VIC adapters:
SX350 Fusion IO adaptor:
Compute Cartridge:
|
||||
3.1(1g) |
ucs-catalog.3.1.1g.T.bin |
Cisco UCS B200 M4, C220 M4, and C240 M4 CPUs
NVME SSD Drives
Memory
Drives
|
||||
3.1(1h) |
ucs-catalog.3.1.1h.T.bin |
Drives
|
||||
3.1(1k) |
— |
— |
||||
3.1(1l) |
— |
— |
||||
3.1(2b) |
ucs-catalog.3.1.2b.T.bin |
Network Adaptors
CPUs
Memory
Drives
Power Supply
Storage Controllers
Server Platforms
|
||||
3.1(2c) |
— |
— |
||||
— |
ucs-catalog.3.1.2e.T.bin |
|
||||
3.1(2e) |
ucs-catalog.3.1.2f.T.bin |
CPU
Server Platforms
|
||||
3.1(2f) |
ucs-catalog.3.1.2i.T.bin |
— |
||||
3.1(2g) |
ucs-catalog.3.1.2j.T.bin |
— |
||||
3.1(2h) |
ucs-catalog.3.1.2j.T.bin |
— |
||||
3.1(3b) |
ucs-catalog.3.1.3c.T.bin |
— |
||||
3.1(3c) |
— |
— |
||||
3.1(3d) |
ucs-catalog.3.1.3e.T.bin |
Drives:
NVMe drives:
|
||||
3.1(3e) |
ucs-catalog.3.1.3j.T.bin |
— |
||||
3.1(3f) |
ucs-catalog.3.1.3m.T.bin |
|
||||
3.1(3h) |
ucs-catalog.3.1.3n.T.bin |
Drive:
|
||||
3.1(3j) |
ucs-catalog.3.1.3p.T.bin |
— |
||||
3.1(3k) |
ucs-catalog.3.1.3q.T.bin |
— |
||||
3.1(3l) |
ucs-catalog.3.1.3q.T.bin |
— |
For 1.6 TB HGST NVME drives, when used with B200-M4 blade servers, the minimum required board controller version is 12, which is bundled with Cisco UCS Manager Release 2.2(7b)B and 3.1(1g)B.
Upgrade and Downgrade Guidelines
Make sure to review detailed upgrade, downgrade guidelines and recommendations in Cisco UCS Manager Firmware Management guide, Release 3.1 from here: Cisco UCS Manager Configuration Guides
The following are a few reminders before you plan your upgrade to Cisco UCS Manager, Release 3.1:
-
In a Cisco UCS domain with a Cisco UCS S3260 chassis, when you downgrade from Cisco UCS Manager Release 3.1(2b) to earlier releases, ensure that you decommission the Cisco UCS S3260 chassis. This is because the Cisco UCS S3260 chassis is supported only by Cisco UCS Manager Release 3.1(2b) and later releases.
If you downgrade from Cisco UCS Manager Release 3.1(2b) to earlier releases without decommissioning the chassis, upgrade validation will fail and Cisco UCS Manager will prompt you to decommission the chassis before continuing with the downgrade operation.
-
Auto-firmware upgrade is not supported in two different fabric Interconnect types in same cluster.
-
When you download A bundle for your fabric Interconnect, you must download the correct A bundle specified for the fabric Interconnect type.
-
If you have any of the deprecated hardware in your environment, the system will prevent upgrade to Cisco UCS Manager 3.1. See Deprecated Hardware, Software, and Third Party Adapters Support in Cisco UCS Manager
-
You must disable SNMP before downgrading from Cisco UCS Manager Release 3.1 to an earlier release, except in Cisco UCS Manager Release 2.2(6). The downgrade process does not begin until SNMP is disabled.
-
Once Compute Conn Policy is set to single-server-dual-sioc, you cannot downgrade Cisco UCS Manager to any release earlier than 3.1(3a). Similarly, Cisco UCS Manager prevents BMC, CMC, and BIOS downgrade to any release earlier than 3.1(3a).
-
If a Cisco UCS S3260 system has Dual HBA Controller then you cannot downgrade Cisco UCS Manager to any release earlier than 3.1(3a).
-
You cannot downgrade Cisco UCS Manager, BMC, CMC, and BIOS to any release earlier than 3.1(3a) depending on the number of disk zoned to the controllers:
Controller Configuration
Is Downgrade Possible?
Two controllers in the server (one in optional I/O expander) or one controller in the server (in optional I/O expander) and at least one disk is zoned to the controller in the optional I/O expander.
No
Two controllers in the server (one in optional I/O expander) or one controller in the server (in optional I/O expander) and at least one disk is pre-provisioned to controller in the optional I/O expander.
No
Two controllers in the server (one in optional I/O expander) or one controller in the server (in any slot) and disk are not zoned or pre-prvosioned to the controller in optional I/O expander.
Yes
Security Fixes
The following security issues are resolved:
Release |
Defect ID |
CVE |
Description |
||
---|---|---|---|---|---|
3.1(3l) |
CSCve02433 |
CVE-2018-0314 |
A vulnerability in the Cisco Fabric Services (CFS) component of Cisco FXOS Software and Cisco NX-OS Software could allow an unauthenticated, remote attacker to execute arbitrary code on an affected device. The vulnerability exists because the affected software insufficiently validates Cisco Fabric Services packet headers when the software processes packet data. An attacker could exploit this vulnerability by sending a maliciously crafted Cisco Fabric Services packet to an affected device. A successful exploit could allow the attacker to cause a buffer overflow condition on the device, which could allow the attacker to execute arbitrary code on the device. Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability. This advisory is available at the following link: Cisco FXOS and NX-OS Software Cisco Fabric Services Arbitrary Code Execution Vulnerability |
||
3.1(3l) |
CSCve02787 |
CVE-2018-0308 |
A vulnerability in the Cisco Fabric Services component of Cisco FXOS Software and Cisco NX-OS Software could allow an unauthenticated, remote attacker to execute arbitrary code or cause a denial of service (DoS) condition on an affected device. The vulnerability exists because the affected software insufficiently validates header values in Cisco Fabric Services packets. An attacker could exploit this vulnerability by sending a crafted Cisco Fabric Services packet to an affected device. A successful exploit could allow the attacker to cause a buffer overflow, which could allow the attacker to execute arbitrary code or cause a DoS condition. Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability. This advisory is available at the following link: Cisco FXOS and NX-OS Software Cisco Fabric Services Arbitrary Code Execution Vulnerability |
||
3.1(3l) |
CSCve41538 |
CVE-2018-0310 |
A vulnerability in the Cisco Fabric Services component of Cisco FXOS Software and Cisco NX-OS Software could allow an unauthenticated, remote attacker to obtain sensitive information from memory content, create a denial of service (DoS) condition, or execute arbitrary code as root. The vulnerability exists because the affected software insufficiently validates Cisco Fabric Services packet headers. An attacker could exploit this vulnerability by sending a crafted Cisco Fabric Services packet to an affected device. A successful exploit could allow the attacker to cause a buffer overflow or buffer overread condition in the Cisco Fabric Services component, which could allow the attacker to obtain sensitive memory content, create a DoS condition, or execute arbitrary code as root. Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability. These advisories are available at the following links: Cisco FXOS and NX-OS Software Cisco Fabric Services Denial of Service Vulnerability Cisco FXOS and NX-OS Software Cisco Fabric Services Arbitrary Code Execution Vulnerability |
||
3.1(3l) |
CSCve41593 |
CVE-2018-0305 |
A vulnerability in the Cisco Fabric Services (CFS) component of Cisco FXOS Software and Cisco NX-OS Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. The vulnerability exists because the affected software insufficiently validates Cisco Fabric Services packets when the software processes packet data. An attacker could exploit this vulnerability by sending a maliciously crafted Cisco Fabric Services packet to an affected device. A successful exploit could allow the attacker to force a NULL pointer dereference or cause a buffer overflow condition on the device, which could cause process crashes and result in a DoS condition on the device. Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability. This advisory is available at the following link: Cisco FXOS and NX-OS Software Cisco Fabric Services Denial of Service Vulnerability |
||
3.1(3l) |
CSCvg71290 |
CVE-2018-0291 |
A vulnerability in the Simple Network Management Protocol (SNMP) input packet processor of Cisco NX-OS Software could allow an authenticated, remote attacker to cause the SNMP application on an affected device to restart unexpectedly. The vulnerability is due to improper validation of SNMP protocol data units (PDUs) in SNMP packets. An attacker could exploit this vulnerability by sending a crafted SNMP packet to an affected device. A successful exploit could allow the attacker to cause the SNMP application to restart multiple times, leading to a system-level restart and a denial of service (DoS) condition. Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability. This advisory is available at the following link: |
||
3.1(3l) |
CSCvp28016 CSCvp27917 CSCvp30013 |
CVE-2018-12126 CVE-2018-12127 CVE-2018-12130 CVE-2019-11091 |
Cisco UCS M3 and M4 servers and Hyperflex M4 servers are vulnerable to variants of exploits that use Microarchitectural Data Sampling (MDS) to gain access to data being processed in the CPU by other applications.
This release includes BIOS revisions for the follwing servers:
These BIOS revisions include the updated microcode that is a required part of the mitigation for these vulnerabilities. |
||
3.1(3l) |
CSCvr54413 CSCvr54414 |
|
Cisco UCS B-Series M4 servers that are based on Intel® processors are affected by vulnerabilities identified by the following Common Vulnerability and Exposures (CVE) IDs:
This release includes BIOS revisions for Cisco UCS B-Series M4 servers. These BIOS revisions include the updated microcode and SINIT ACM for Cisco UCS M4 servers, which are required parts of the mitigation for these vulnerabilities. |
||
3.1(3l) |
CSCvr54411 |
CVE-2019-0151 |
Cisco UCS B-Series M3 servers that are based on Intel® processors are affected by vulnerabilities identified by the following Common Vulnerability and Exposures (CVE) ID:
This release includes BIOS revisions for Cisco UCS B-Series M3 servers. These BIOS revisions include the updated SINIT ACM for Cisco UCS M3 servers, which is a required part of the mitigation for these vulnerabilities. |
||
3.1(3k) |
CSCvj59299 CSCvj59301 |
CVE-2018-3639 CVE-2018-3640 |
Cisco UCS M2 servers that are based on Intel® EX Series processors are vulnerable to variants of an exploit that uses CPU speculative processing and data cache timing to efficiently leak information, known as Spectre. CVE-2018-3639 (Spectre/Variant #4) and CVE-2018-3640 (Spectre/Variant #3a) are addressed by applying the updated processor microcode from Intel included in the server firmware bundle, and the relevant Operating System and Hypervisor patches from the appropriate vendors. This release includes BIOS revisions for Cisco UCS M2 B-Series blade servers that are based on Intel® EP Series processors. These BIOS revisions include the updated processor microcode that is a required part of the mitigation for CVE-2018-3639 (Spectre/Variant #4) and CVE-2018-3640 (Spectre/Variant #3a).
For more information, please see the Cisco Security Advisory available here: CPU Side-Channel Information Disclosure Vulnerabilities: May 2018 |
||
3.1(3k) |
CSCvq66225 |
CVE-2019-9836 |
On the Cisco UCS C-Series servers that are based on AMD EPYC™ processors, using the user-selectable AMD secure encryption feature on a virtual machine running the Linux operating system, an encryption key could be compromised by manipulating the encryption technology’s behavior. This release includes the BIOS revision to mitigate this risk. For more information about this vulnerability, see https://www.amd.com/en/corporate/product-security. |
||
3.1(3j) |
CSCvm02934 |
CVE-2018-3615 CVE-2018-3620 CVE-2018-3646 |
Cisco UCS B-Series M2 servers are based on Intel® processors that are vulnerable to exploits that use CPU speculative processing and data cache timing to potentially identify privileged information. These exploits are collectively known as L1 Terminal Fault (L1TF).
This release includes BIOS revisions for Cisco UCS M2 generation servers. These BIOS revisions include the updated processor microcode that is a required part of the mitigation for CVE-2018-3620 (OS/SMM) and CVE-2018-3646 (VMM). Operating System and Hypervisor patches from the appropriate vendors may also be required to mitigate these vulnerabilities. For more information, please see the Cisco Security Advisory available here: CPU Side-Channel Information Disclosure Vulnerabilities: August 2018 |
||
3.1(3j) |
CSCvm03356 |
CVE-2018-3615 CVE-2018-3620 CVE-2018-3646 |
Cisco UCS B-Series M3 servers and C-Series M3 servers are based on Intel® processors that are vulnerable to exploits that use CPU speculative processing and data cache timing to potentially identify privileged information. These exploits are collectively known as L1 Terminal Fault (L1TF).
This release includes BIOS revisions for Cisco UCS M3 generation servers. These BIOS revisions include the updated processor microcode that is a required part of the mitigation for CVE-2018-3620 (OS/SMM) and CVE-2018-3646 (VMM). Operating System and Hypervisor patches from the appropriate vendors may also be required to mitigate these vulnerabilities. For more information, please see the Cisco Security Advisory available here: CPU Side-Channel Information Disclosure Vulnerabilities: August 2018 |
||
3.1(3j) |
CSCvm03351 |
CVE-2018-3615 CVE-2018-3620 CVE-2018-3646 |
Cisco UCS B-Series M4 servers, C-Series M4 servers, S3260 M4 storage servers, and HyperFlex M4 servers are vulnerable to exploits that use CPU speculative processing and data cache timing to potentially identify privileged information. These exploits are collectively known as L1 Terminal Fault (L1TF).
This release includes BIOS revisions for Cisco UCS M4 generation servers. These BIOS revisions include the updated processor microcode that is a required part of the mitigation for CVE-2018-3620 (OS/SMM) and CVE-2018-3646 (VMM). Operating System and Hypervisor patches from the appropriate vendors may also be required to mitigate these vulnerabilities. For more information, please see the Cisco Security Advisory available here: CPU Side-Channel Information Disclosure Vulnerabilities: August 2018 |
||
3.1(3j) |
CSCvd36971 |
CVE-2017-3883 |
A vulnerability in the authentication, authorization, and accounting (AAA) implementation of Cisco Firepower Extensible Operating System (FXOS) and NX-OS System Software could allow an unauthenticated, remote attacker to cause an affected device to reload. The vulnerability occurs because AAA processes prevent the NX-OS System Manager from receiving keepalive messages when an affected device receives a high rate of login attempts, such as in a brute-force login attack. System memory can run low on the FXOS devices under the same conditions, which could cause the AAA process to unexpectedly restart or cause the device to reload. An attacker could exploit this vulnerability by performing a brute-force login attack against a device that is configured with AAA security services. A successful exploit could allow the attacker to cause the affected device to reload. Cisco has now integrated the fix for this vulnerability on the UCS-FI-M-6324 platform (on UCS-FI-62xx and UCS-FI-63xx, the fix was integrated in Release 3.2(3a) already). Additionally, a remaining corner case that allowed attackers to connect using a valid password while the login block window is still active, has been addressed on all Fabric Interconnect platforms now. This advisory is available at the following link: |
||
3.1(3j) |
CSCvj59299 |
CVE-2018-3639 CVE-2018-3640 |
Cisco UCS M2 servers that are based on Intel® EP Series processors are vulnerable to variants of an exploit that uses CPU speculative processing and data cache timing to efficiently leak information, known as Spectre. CVE-2018-3639 (Spectre/Variant #4) and CVE-2018-3640 (Spectre/Variant #3a) are addressed by applying the updated processor microcode from Intel included in the server firmware bundle, and the relevant Operating System and Hypervisor patches from the appropriate vendors. This release includes BIOS revisions for Cisco UCS M2 B-Series blade servers that are based on Intel® EP Series processors. These BIOS revisions include the updated processor microcode that is a required part of the mitigation for CVE-2018-3639 (Spectre/Variant #4) and CVE-2018-3640 (Spectre/Variant #3a).
For more information, see the Cisco Software Advisory at: CPU Side-Channel Information Disclosure Vulnerabilities: May 2018 |
||
3.1(3j) |
CSCvj54880 |
CVE-2018-3639 CVE-2018-3640 |
Cisco UCS M3 servers are based on Intel® processors that are vulnerable to variants of an exploit that uses CPU speculative processing and data cache timing to efficiently leak information, known as Spectre. CVE-2018-3639 (Spectre/Variant #4) and CVE-2018-3640 (Spectre/Variant #3a) are addressed by applying the updated processor microcode from Intel included in the server firmware bundle, and the relevant Operating System and Hypervisor patches from the appropriate vendors. This release includes BIOS revisions for Cisco UCS M3 generation servers. These BIOS revisions include the updated processor microcode that is a required part of the mitigation for CVE-2018-3639 (Spectre/Variant #4) and CVE-2018-3640 (Spectre/Variant #3a). For more information, see the Cisco Software Advisory at: CPU Side-Channel Information Disclosure Vulnerabilities: May 2018 |
||
3.1(3j) |
CSCvj54847 CSCvj54187 |
CVE-2018-3639 CVE-2018-3640 |
Cisco UCS M4 servers and Hyperflex M4 servers are based on Intel® processors that are vulnerable to variants of an exploit that uses CPU speculative processing and data cache timing to efficiently leak information, known as Spectre. CVE-2018-3639 (Spectre/Variant #4) and CVE-2018-3640 (Spectre/Variant #3a) are addressed by applying the updated processor microcode from Intel included in the server firmware bundle, and the relevant Operating System and Hypervisor patches from the appropriate vendors. This release includes BIOS revisions for Cisco UCS M4 and Hyperflex M4 generation servers. These BIOS revisions include the updated processor microcode that is a required part of the mitigation for CVE-2018-3639 (Spectre/Variant #4) and CVE-2018-3640 (Spectre/Variant #3a). For more information, see the Cisco Software Advisory at: CPU Side-Channel Information Disclosure Vulnerabilities: May 2018 |
||
3.1(3h) |
CSCvh31576 CSCvh51796 |
|
Cisco UCS B-Series and C-Series M2 servers are based on Intel® Xeon® 5500, 5600, and Ex series processors that are vulnerable to variants of exploits that use CPU speculative processing and data cache timing to potentially identify privileged information. These exploits are collectively known as Spectre and Meltdown.
This release includes BIOS revisions for Cisco UCS M2 generation servers. These BIOS revisions include the updated microcode that is a required part of the mitigation for CVE-2017-5715 (Spectre/Variant 2). For more information, please see the Cisco Security Advisory at: |
||
3.1(3f) |
CSCve59744 |
CVE-2017-15361 |
The vulnerability related to TPM 2.0 is addressed. |
||
3.1(3f) |
CSCvg97965, CSCvg97979, CSCvg98015 |
|
Cisco UCS and Hyperflex servers are based on Intel processors that are vulnerable to exploits that use CPU speculative processing and data cache timing to potentially identify privileged information. These exploits are collectively known as Spectre and Meltdown.
This release includes the BIOS revisions for Cisco UCS M3 and M4 and Hyperflex M4 generation servers that include the updated microcode that is a required part of the mitigation for CVE-2017-5715 (Spectre/Variant 2). For more information, please see the Cisco Security Advisory at: |
||
3.1(3a) |
CSCvb48644 |
|
The latest CiscoSSL 6.1.188-fips (corresponding to OpenSSL 1.0.2k, and detailed in CSCvc94686) now automatically fixes the OpenSSL vulnerabilities identified by one or more of the Common Vulnerability and Exposures (CVE) IDs listed. |
||
3.1(2e) |
CSCvb85544 |
CVE-2016-5195 |
The vulnerability for a race condition that existed in the memory manager of the Linux kernel has been fixed. |
||
3.1(2b) |
CSCuz91623 |
CVE-2016-6402 |
The vulnerability associated with insufficient sanitization of user supplied input at the CLI on Cisco UCS Manager and UCS 6200 Fabric Interconnects is resolved. |
||
3.1(1l) |
CSCvb85544 |
CVE-2016-5195 |
The vulnerability for a race condition that existed in the memory manager of the Linux kernel has been fixed. |
||
3.1(1k) |
CSCuz92668 |
CVE-2016-4957, CVE-2016-4953, CVE-2016-4954, CVE-2016-4955, CVE-2016-4956 |
Vulnerabilities related to NTPd are fixed. |
||
3.1(1e) |
CSCuj84274 |
CVE-2013-4786 |
The vulnerability in Cisco Integrated Management Controller (CIMC) on the Cisco Unified Computing System Series Platforms associated with unauthenticated access is resolved. |
||
CSCut46044 |
CVE-2015-0291, CVE-2015-0204, CVE-2015-0290, CVE-2015-0207, CVE-2015-0286, CVE-2015-0208, CVE-2015-0287, CVE-2015-0289, CVE-2015-0292, CVE-2015-0293, CVE-2015-1787, CVE-2015-0285, CVE-2015-0288 |
Vulnerabilities related to OpenSSL are fixed. |
|||
CSCup58725 |
CVE-2007-6514, CVE-2007-1741, CVE-2007-1742, CVE-2007-1743, CVE-2008-0455, CVE-2008-0456, CVE-2006-4110, CVE-2013-6438, CVE-2014- 0098, CVE-2014-3470, CVE-2010-2054, CVE-2010-1937, CVE-2010-5298, CVE-2014-0076, CVE-2014-0195, CVE-2014-0198, CVE-2014-0221, CVE-2014-0224, CVE-2014- 3470, CVE-2011-3389 |
Vulnerabilities associated with SBLIM-SFCB Multiple Buffer Overflow are fixed. |
|||
CSCux00285 |
CVE-2011-2898, CVE-2014-6271, CVE-2014-7169, CVE-2014-6271, CVE-2014-7169, CVE-2014-7187, CVE-2014-6277, CVE-2011-0207, CVE-2012-0207, CVE-2011-4131, CVE-2014-2523, CVE-2012-3400, CVE-2012-1148, CVE-2011-4077, CVE-2012-0038, CVE-2014-4699, CVE-2014-0205, CVE-2013-1943, CVE-2012-4444, CVE-2012-2136, CVE-2012-0876, CVE-2014-1690, CVE-2011-4325, CVE-2012-2133, CVE-2013-4220, CVE-2012-1090, CVE-2012-2373, CVE-2012-2745, CVE-2011-3363, CVE-2012-1088, CVE-2012-1146 CVE-2012-2372, CVE-2012-3412, CVE-2012-3410, CVE-2012-3410, CVE-2012-4565, CVE-2012-5374, CVE-2013-0311, CVE-2014-7186, CVE-2011-1083, CVE-2011-3359, CVE-2012-1601, CVE-2012-2121, CVE-2012-2119, CVE-2012-3375, CVE-2012-4467, CVE-2009-3720, CVE-2009-3560, CVE-2013-1860, CVE-2012-0045, CVE-2013-1796, CVE-2012-3430, CVE-2012-2313, CVE-2012-4530, CVE-2012-1568, CVE-2012-5375 |
Security issues related to third party alerts are fixed. |
Libfabric and Open MPI
Cisco usNIC support in the Libfabric and Open MPI open source packages is readily available from their community web sites (http://libfabric.org/ and http://www.open-mpi.org/, respectively).
Cisco UCS Manager Release 3.1(3) and later releases no longer include Open MPI binary packages. Future UCS software driver bundles distributed through the usual Cisco software channels may not include binaries for the libfabric packages. Cisco engineers continue to be active, core contributors in both the Libfabric and Open MPI communities, and will actively develop and support users through the usual community or commercial ISV support mechanisms (e.g., IBM Spectrum MPI).
Resolved Caveats
The resolved bugs for a release are accessible through the Cisco Bug Search Tool. This web-based tool provides you with access to the Cisco bug tracking system, which maintains up-to-date information about bugs and vulnerabilities in this product and other Cisco hardware and software products.
Note |
You must have a Cisco.com account to log in and access the Cisco Bug Search Tool. If you do not have one, you can register for an account. |
For more information about the Cisco Bug Search Tool, see the Bug Search Tool Help & FAQ.
Resolved Caveats in Release 3.1(3l)
The following caveats are resolved in Release 3.1(3l):
Defect ID |
Description |
First Bundle Affected |
Resolved in Release |
---|---|---|---|
CSCvo49554 |
When a blade server is connected to ports 27-32 on a UCS 6332 Fabric Interconnect, or ports 35-40 on a UCS 6332-16UP Fabric Interconnect, numerous pings are lost during Fabric Interconnect reboot. This issue is resolved. |
3.1(3h)A |
3.1(3l)A |
CSCvr67027 |
When upgrading Red Hat Linux on a Cisco UCS Manager integrated S3260 M4 rack server with UCS-C3K-M4RAID RAID controller running driver 07.702.06.00-rh2, the boot drive becomes inoperable. This issue is resolved. |
3.1(3h)C |
3.1(3l)C |
CSCvf03280 |
When Cisco Fabric Services (CFS) distribution is enabled on UCS 6200 Series Fabric Interconnects, the Fabric Interconnect may reload due to a CFS process crash. This issue has been resolved. |
3.1(3a)A |
3.1(3l)A |
CSCvs43658 |
When Cisco Fabric Services (CFS) distribution wass enabled on UCS Fabric Interconnects and the Infrastructure bundle was upgraded, both Fabric Interconnects rebooted continuously due to CFS hap reset. This issue has been resolved. |
3.1(3k)A |
3.1(3l)A |
Resolved Caveats in Release 3.1(3k)
The following caveats are resolved in Release 3.1(3k):
Defect ID |
Description |
First Bundle Affected |
Resolved in Release |
---|---|---|---|
CSCvk71319 |
The message queue may become full and if the VIM misses a heartbeat can result in VIM process crash. |
3.1(3h)A |
3.1(3k)A |
CSCvj10772 |
Multicast traffic no longer drops on some Veths. The affected multicast group(s) are seen in the software but absent in the hardware. |
3.1(3h)A |
3.1(3k)A |
CSCvk51589 CSCvk73712 CSCvk75400 |
Cisco UCS 6200 and 6300 Series Fabric Interconnects no longer reloads with the message: Reset triggered due to HA policy of Reset. This error may occur if the message queue becomes full. |
3.1(3h)A |
3.1(3k)A |
CSCvh66141 |
When accessing KVM directly without first logging into UCS Manager, KVM will fail to launch if you are using non-native authentication. |
3.1(3a)B |
3.1(3k)B |
Resolved Caveats in Release 3.1(3j)
The following caveats are resolved in Release 3.1(3j):
Defect ID |
Description |
First Bundle Affected |
Resolved in Release |
---|---|---|---|
CSCvi98058 |
New OS installation in UEFI mode and BIOS version 2.2.6f.0 no longer fails. |
3.1(3h)B |
3.1(3j)A |
CSCvi96785 |
On UCS 6332-16UP and 6332 fabric interconnects, the file system was corrupted and the show logging log or show logging nvram log contained a message with the term "EXT3-fs error”. The fix in Cisco UCS Manager Release 3.1(3j) prevents this issue from occurring. |
3.2(2b)A |
3.1(3j)A 3.2(3g) |
CSCvg64592 CSCvh17112 CSCvh11759 |
Rack servers integrated with 6200 Series FI, 6300 Series FIs, and 6324 FIs have connectivity after reboot of the subordinate FI, if the VLAN range (expressed as a string of characters) applied on a port-profile exceeds 255 characters. |
3.1(3c)A |
3.1(3j)A 3.2(3a)A |
CSCvj63400 CSCvj88019 CSCvj88844 |
On UCS 6200 Series FIs, 6300 Series FIs and 6324 FIs running Cisco UCS Manager Release 3.2(2c), IOMs crashed with reset reason vic_proxy hap and generated a core. This happened when there was an invalid memory access. This issue has been resolved. |
3.2(2c)A | 3.1(3j)A, 3.2(3e)A |
CSCvd54116 |
Setting a custom cipher suite for UCS Manager no longer results in a handshake failure error message when attempting to open a Java login to UCSM or a KVM session to a blade server. |
2.2(8c)A |
3.1(3j) 3.2(3g)A |
CSCvj83780 |
Under specific low write and long idle time workloads, the following SATA SSDs no longer show read errors:
|
3.2(2b)B |
3.1(3j)B3.2(3e)B |
Resolved Caveats in Release 3.1(3h)
The following caveats are resolved in Release 3.1(3h):
Defect ID |
Description |
First Bundle Affected |
Resolved in Release |
---|---|---|---|
CSCvh60861 |
In a UCS domain running Cisco UCS Manager Release 3.1(x) or 3.2(x) code with UCS B200 M2 or B250 M2 servers, using a Host Firmware Package to perform a BIOS firmware upgrade from Release 2.5(x) or earlier versions to Release 3.1(x) or later versions no longer fails. |
3.2(2b)A | 3.1(3h)A |
Resolved Caveats in Release 3.1(3f)
The following caveats are resolved in Release 3.1(3f)
Defect ID |
Description |
First Bundle Affected |
Resolved in Release |
---|---|---|---|
CSCvb88279 |
Boot speeds are no longer slow when using a storage profile for pool LUNs on EMC VNX arrays. |
3.1(2b)B |
3.1(3f)B |
CSCvh64120 |
DME no longer crashes after an upgrade to 3.1(3) or 3.2(2). |
3.1(3a)A |
3.1(3f)A |
CSCvh22485 |
After a vMotion or virtual machine migration in a VMFEX setup, virtual machines were unable to receive broadcast or multicast packets, including ARP packets. The issue has been resolved. |
2.2(8g)A |
3.1(3f)A |
CSCvg44307 |
Stale entries in IOM no longer cause a communication failure within the same VLAN and fabric interconnect. |
2.2(4b)A |
3.1(3f)A |
CSCuw09993 |
ESXi no longer reports a fatal error while loading /s.v00 during the "Loading VMware Hypervisor" Screen. |
2.2(3a)B |
3.1(3f)B |
CSCvh56396 |
mgmt0 IP now appears in the command "show ip interface brief vrf management" or "show run interface mgmt0" from connect nxos. |
3.1(3e)A |
3.1(3f)A |
CSCve08388 |
A failure to update the local disk firmware image no longer occurs. |
3.1(3c)A |
3.1(3f)A |
CSCve68431 |
UEFI Boot Parameters are now applied on B200 M3 and M4 servers with 3.1(2f). |
3.1(2f)B |
3.1(3f)B |
CSCvf36433 |
Matrox G200e driver installation no longer produces an error on Windows 2016. |
3.1(3a)C |
3.1(3f)C |
CSCvf50470 |
Cisco VIC adapter no longer displays an Exchange Allocation Failure and WQ Errors with fibre channel traffic. |
3.1(3a)B |
3.1(3f)B |
CSCvf59328 |
TASK_SET_FULL SCSI response is no longer mishandled by FNIC. |
1.6(0.25) |
3.1(3f)B |
CSCvg25428 |
Call Home Alert messages are no longer generated for weekly occurences of CIMC cores. |
3.1(1h)C |
3.1(3f)C |
CSCvg99433 |
On UCS Mini, a fabric interconnect reboot no longer occurs from a QoS Buffer-Stuck error. |
3.1(1e)A |
3.1(3f)A |
CSCvg98077 |
A TPM firmware update no longer fails if a UCS Manager event interrupts the process. |
2.2(8i)B |
3.1(3f)B |
CSCvh07966 |
Firmware update no longer fails for Nvidia P100. |
3.1(3d)C |
3.1(3f)C |
CSCvg88563 |
Both sockets of the Rack Server with UCSC-GPU-M60 now display the same firmware version. |
3.1(3d)A |
3.1(3f)A |
Resolved Caveats in Release 3.1(3e)
The following caveats are resolved in Release 3.1(3e)
Defect ID |
Description |
First Bundle Affected |
Resolved in Release |
---|---|---|---|
CSCvf59328 |
The fNIC no longer reports DATA_CNT_MISMATCH when the TASK_SET_FULL SCSI command is received from the storage array. |
3.1(1e) |
3.1(3e) |
CSCvf50470 |
Server no longer loses FC connectivity with the datastore. |
3.1(3a) |
3.1(3e) |
Resolved Caveats in Release 3.1(3d)
The following caveats are resolved in Release 3.1(3d)
Defect ID |
Description |
First Bundle Affected |
Resolved in Release |
---|---|---|---|
CSCve23500 |
Cisco UCS B200 M4 Blade Server no longer crashes with SD Card Connectivity issues. |
2.2(3d)B |
3.1(3d)B |
CSCve30154 |
Cisco UCS B200 M4 Blade Server no longer fails to boot from the SD card mirror after the primary SD card fails. |
3.1(2e)B |
3.1(3d)B |
CSCve34690 |
A FlexFlash Failure no longer reports a "missing" fault for functional SD cards. |
3.1(2b)A |
3.1(3d)A |
CSCve41380 |
The operating system no longer fails to boot when one of the SD cards in a RAID 1 configuration is inoperable. |
3.1(1h)B |
3.1(3d)B |
CSCvd54828 |
The RAID controller encounters an error and resets. This happens when you use an external SATA solid state drive (SSD) and not an SAS SSD. |
3.0(3a)C |
3.1(3d)C |
Resolved Caveats in Release 3.1(3c)
The following caveats are resolved in Release 3.1(3c)
Defect ID |
Description |
First Bundle Affected |
Resolved in Release |
---|---|---|---|
CSCve14926 |
A configuration error no longer occurs while associating a service profile with UCSC-C240M4-SX or UCSC-C240-M4L servers, under the following conditions:
|
3.1(1e)A |
3.1(3c)A |
CSCve35785 |
The SNMP process no longer crashes on UCS after an upgrade due to high memory usage. |
3.1(3a)A |
3.1(3c)A |
CSCvf07449 |
The firmware update for the LSI 9300-8e controller no longer fails. After the update, the firmware version of the controller and the firmware version of the host firmware package are same. |
3.1(3a)A |
3.1(3c)A |
CSCvf18955 |
During clustering, if one FI runs Release 3.1(3) and the other FI runs any release earlier than Release 3.1(3), an error message indicating that the local "Admin" password is incorrect, or that the authentication mode of the working fabric is not set to "Local" is no longer displayed. |
3.1(3a)A |
3.1(3c)A |
Resolved Caveats in Release 3.1(3b)
The following caveats are resolved in Release 3.1(3b)
Defect ID |
Description |
First Bundle Affected |
Resolved in Release |
---|---|---|---|
CSCve30332 |
UCS Manager no longer becomes unresponsive when a Service Profile is associated with a server. |
3.1(3a)A |
3.1(3b)A |
CSCve15708 |
UCS domain registration no longer fails on UCS firmware when using the IPv6 address of UCS Central. |
3.1(3a)A |
3.1(3b)A |
CSCve06789 |
A service profile creation no longer fails with the SAN connectivity policy using vHBA when it is created with a redundancy pair. |
3.1(3a)A |
3.1(3b)A |
CSCve41254 |
LUN creation no longer fails using Local Disk policy with RAID 60 mode in rack servers. |
3.1(3a)A |
3.1(3b)A |
CSCve46288 |
UCS S3260 storage controller upgrade no longer fails for M3 servers during upgrades. |
3.1(3a)A |
3.1(3b)A |
CSCvd91302 |
UCS Mini and the Fabric Interconnect no longer looses connection after a change in the MTU value in BM and DQ. |
3.1(1e)A |
3.1(3b)A |
CSCve13711 |
While upgrading UCS Manager, the remote fabric interconnect no longer continuously reboots with a PCIe Device-Cisco Donner error. |
3.1(3a)A |
3.1(3b)A |
CSCva31113 |
After a fabric interconnect reboot, a file system corruption no longer occurs on systems that contain an Indilinx controller. |
2.2(1b)A |
3.1(3b)A |
Resolved Caveats in Release 3.1(3a)
The following caveats are resolved in Release 3.1(3a):
Defect ID |
Symptom |
First Bundle Affected |
Resolved in Release |
---|---|---|---|
CSCvc99135 |
The UCS Fabric Interconnect generates IGMP proxy reports where the source mac address of the data packets is replaced by the Fabric Interconnect, but the IP address is 0.0.0.0. Thus, multiple entries are not created in the IP-mac table for the IP in the uplink switch. Hence, there is no end point movement. |
3.1(1e)B |
3.1(3a)B |
CSCuz76350 |
Cisco B260 or B460 M4 servers running RHEL 6.7 no longer become unresponsive when booting with all the DIMM slots fully populated. |
3.1(2b)B |
3.1(3a)B |
CSCvb96124 |
After changes are made to the QoS policy on a Cisco UCS 6332 Fabric Interconnect, the primary FI is not rebooted until Pending Activities are acknowledged. |
3.1(2b)A |
3.1(3a)A |
CSCvb14641 |
Power policies are no longer out of synchronization between Cisco UCS Manager and CMC after the master IOM is rebooted. |
3.0(2c)A |
3.1(3a)A |
CSCvd24782 |
When the poweroff module was available for less than 15 seconds, all of the poweron commands timed out. The poweroff module <module_number> was then seen in the list of installed features on the FI through NXOS:
The module appeared to no longer work after it rebooted. This issue no longer occurs. |
3.1(1e)A |
3.1(3a)A |
CSCvb88279 |
On EMC VNX arrays, when pool-based LUNs with a frame size of 512 bytes from non-owning SPs are used, booting to non-owning SPs is no longer slow. |
3.1(2b)B |
3.1(3a)B |
CSCvb52847 |
On a B200 M4 blade platform, instead of a NVMe plane, if RAID card is plugged in, then the /var/log/messages file no longer shows "Mux write error" messages. Apart from /var/log/message flood, no functional impact to normal storage operations are noticed. |
3.1(2b)B |
3.1(3a)B 3.1(2f)B |
Resolved Caveats in Release 3.1(2h)
The following caveats are resolved in Release 3.1(2h).
Defect ID |
Description |
First Bundle Affected |
Resolved in Release |
||
---|---|---|---|---|---|
CSCuv43292 |
The fabric interconnect no longer crashes due to a sleeping function called within an interrupt context. |
Both 2.2(4a)A and 2.2(5a)A are affected but not 2.2(6)A, 2.2(7)A, and 2.2(8)A. |
3.1(2h)A |
||
CSCva31113 |
After a fabric interconnect reboot, a file system corruption no longer occurs on systems that contain an Indilinx controller. |
2.1(1a)A |
3.1(2h)A |
||
CSCva89402 |
An incorrect fault is no longer generated in UCS Manager when the power supply input source is "unknown". |
3.1(1e)B |
3.1(2h)B |
||
CSCvb14641 |
Power policies are no longer out of synchronization between Cisco UCS Manager and CMC after the master IOM is rebooted. |
3.0(2c)A |
3.1(2h)A |
||
CSCvb61558 |
UCSB-PSU-2500ACDV no longer displays incorrect power readings in the PSMI register. |
3.1(1e)A |
3.1(2h)A |
||
CSCvb92941 |
UCS-IOM-2304 no longer fails to capture kernel cores in the obfl_raw partition. |
3.1(1e)A |
3.1(2h)A |
||
CSCvb93881 |
IOM 2300 and UCSB-5108-AC2 chassis no longer displays the fault F0409 "Thermal condition on chassis x is upper-critical".
|
3.1(1g)A |
3.1(2h)A |
||
CSCvd56914 |
Microcode was added for Broadwell and Haswell EX processors support. |
3.1(2b)B |
3.1(2h)B |
||
CSCvd68198 |
Microcode was added for E5 Xeon v4 Processor support. |
3.1(2b)B |
3.1(2h)B |
||
CSCvd80748 |
For Cisco B260 or B460 Blade servers, the enable COD setting no longer causes an incorrect microcode version to appear. |
3.1(2b)B |
3.1(2h)B |
||
CSCvd91302 |
UCS Mini and the Fabric Interconnect no longer loses connection after a change in the MTU value in BM and DQ. |
3.1(1e)A |
3.1(2h)A |
||
CSCvd93200 |
A random reboot due to a spinlock lockup no longer occurs on Cisco UCS 2304. |
3.1(1e)A |
3.1(2h)A |
Resolved Caveats in Release 3.1(2g)
The following caveats are resolved in Release 3.1(2g)
Defect ID |
Description |
First Bundle Affected |
Resolved in Release |
---|---|---|---|
CSCva67630 |
False SER errors no longer occurs for FP ternary content addressable memory (TCAM) tables for Cisco UCS 6300 Series Fabric Interconnects. |
3.1(1g)A |
3.1(2g)A |
CSCvb68147 |
The IOM no longer goes offline when the host interface links are down and under constant temperature change. |
3.1(1h)A |
3.1(2g)A |
CSCvb79455 |
The critical fault code F1000227 no longer occurs on both the primary and subordinate FI during upgrade. |
3.1(1e)A |
3.1(2g)A |
CSCvc02297 |
The power cap application no longer fails for a Bladeserver when the server is powered on or off from outside of Cisco UCS Manager. |
3.1(1e)A |
3.1(2g)A |
CSCvc05615 |
FI-6396UP with FC 16G interfaces (individual/port-channel) no longer incorrectly report discard frame count. The issue was a cosmetic one where-in the discard count (both input and output) used to increase every few minutes. The interfaces themselves are not impacted and remain up. |
3.1(1e)A |
3.1(2g)A |
CSCvd05543 |
For Cisco B460 M4 and B260 M4 Blade servers, a change to the PWRSEQ_FAULT_N logic from PWRSEQ_WARN_N to Pwr fault no longer results in a discovery failure if the master and slave blades have different board controller versions. |
3.1(2f)B |
3.1(2g)B |
CSCvd20170 |
A Cisco UCS Manager power group change implemented through the HTML5 GUI no longer shows 0W for a Bladeserver in the chassis. |
3.0(2c)A |
3.1(2g)A |
CSCvd42163 |
During a Fabric Interconnect upgrade or reload, the following error no longer occurs. ERROR: bootflash: has unrecoverable error; please do "format bootflash:" |
3.1(1e)A |
3.1(2g)A |
Resolved Caveats in Release 3.1(2f)
The following caveats are resolved in Release 3.1(2f):
Defect ID |
Symptom |
First Bundle Affected |
Resolved in Release |
---|---|---|---|
CSCva14937 |
M4 blades installed with SD cards instead of a hard disk no longer halt at 'Local Drive' for automated deployments with the following boot policy: Boot Policy
|
2.2(3f)B |
3.1(2f)B |
CSCva35757 |
Latency between the UCS Manager Client and fabric interconnect no longer causes the firmware page to load slowly. |
2.2(7b)A |
3.1(2f)A |
CSCvb52847 |
On a B200 M4 blade platform, instead of a NVMe plane, if RAID card is plugged in, then the /var/log/messages file no longer shows "Mux write error" messages. Apart from /var/log/message flood, no functional impact to normal storage operations are noticed. |
3.1(2b)B |
3.1(2f)B 3.1(3a)B |
CSCvb63893 |
In a Cisco UCS Manager managed environment, the disk inventory is now able to refresh all the disks present on the system after a power cycle. |
3.1(2b)C |
3.1(2f)C |