This document describes system requirements, new features, resolved caveats, known caveats and workarounds for Cisco UCS Manager software Release 2.2. This document also includes the following: • Current information that became available after the technical documentation was published • Related firmware and BIOS on blade and rack servers and other Cisco Unified Computing System (UCS) components associated with the release Use this release note as a supplement with the other documents listed in documentation roadmaps: • • Contents of the various bundles for this release are described in: • Make sure to review other available documentation on Cisco.com to obtain current information on Cisco UCS Manager. Table 1 Online Change History Date Description December 12, 2013 Created release notes for Cisco UCS Manager, Release 2.2(1b). December 20, 2013 Added additional caveats. February 9, 2014 Updated release notes for Cisco UCS Software Release 2.2(1c).

February 19, 2014 Updated release notes for Catalog Release 2.2.1c.T. April 2, 2014 Updated release notes for Catalog Release 2.2.1d.T. April 10, 2014 Updated release notes for Cisco UCS Software Release 2.2(1d).

May 16, 2014 Added CSCuo78883 to Open Caveats for release 2.2(1d). May 22, 2014 Updated release notes for Cisco UCS Software Release 2.2(2c). May 24, 2014 Updated to include additional Open Caveats for Cisco UCS Software Release 2.2(2c).

Nov 25, 2017. Now hiring CDL Class A Drivers for OTR work out of Saint Paul, MN! Trillium Drivers are. 2,600 - 3,000 miles per week Running mostly in the Midwest and Southeast Brand New Equipment Paid Orientation - Have your own hotel room! Rider Policy. NEW PAY PACKAGE 11/5/17*.

May 30, 2014 Modified several Caveat descriptions. June 18, 2014 Added CSCul74278 to 2.2(1b) Open Caveats and to 2.2(2c) Resolved Caveats; added ‘Behavior Changes’ section; and corrected three items in Servers list. August 1, 2014 Updated release notes for Cisco UCS Software Release 2.2(1e).

August 21, 2014 Added B22 PID support and updated PID support for other servers in Version Mapping table for 2.2(2c); added ‘Chassis’ section to Internal Dependencies table; added UCSB-5108-AC2, -DC2, and -HVDC to New Hardware Features section; added note to Upgrade section for CSCud81176 consideration; added CSCuj81245 to 2.2(1b) Open Caveats table and to 2.2(2c) Resolved Caveats table. September 8, 2014 Updated release notes for Cisco UCS Software Release 2.2(3a).

September 11, 2014 Updated release notes for Cisco UCS Software Release 2.2(2d); updated the Recommended Minimum Software in Table 4. October 9, 2014 Updated release notes for Cisco UCS Software Release 2.2(3b). October 24, 2014 Updated release notes for Cisco UCS Software Release 2.2(2e) and 2.2(3c). October 31, 2014 Updated release notes for Cisco UCS Software Release 2.2(1f). November 10, 2014 Added CSCuo60330 to 2.2(3a) resolved caveats. November 17, 2014 Added missing 2.2(3c) adapter to Internal Dependencies table.

December 4, 2014 Updated release notes for Catalog Release 2.2.3b.T. December 22, 2014 Updated release notes for Cisco UCS Software Release 2.2(1g) and 2.2(3d). January 13, 2015 Updated first affected bundle for CSCuq20755.

March 4, 2015 Updated release notes for Cisco UCS Software Release 2.2(3e). March 18, 2015 Updated the New Hardware Features list for Release 2.2(3a).

March 20, 2015 Updated release notes for Cisco UCS Software Release 2.2(3f). April 15, 2015 Updated the Recommended Software Version for C260 and C460 M2 servers.

May 14, 2015 Updated release notes for Cisco UCS Software Releases 2.2(3g) and 2.2(4b). May 26, 2015 Added CSCus10255 to the Resolved Caveats for Cisco UCS Software Release 2.2(4b).

June 5, 2015 Updated release notes for Cisco UCS Software Release 2.2(5a). June 15, 2015 Updated release notes for Cisco UCS Software Release 2.2(1h). June 30, 2015 Updated the Capability Catalog and New Hardware Features sections with information about Cisco 12G SAS Modular RAID Controller.

Updated the Resolved Caveats for 2.2(4b). July 10, 2015 Added CSCuv04436 to the Open Caveats for 2.2(4b) and 2.2(5a). This issue has a software advisory associated with it. July 17, 2015 Updated release notes for Cisco UCS Software Release 2.2(4c). July 30, 2015 Updated release notes for Cisco UCS Software Release 2.2(5b).

August 27, 2015 Updated release notes for Cisco UCS Software Release 2.2(5c). September 11, 2015 Updated the Behavior Changes section for Release 2.2(4b). Updated the Resolved and Open Caveats for Release 2.2(5c).

Added CSCus81832 to the list of Resolved Caveats for Release 2.2(4b). September 22, 2015 Added CSCus73196 to the list of Open Caveats for Release 2.2(3d). September 25, 2015 Updated release notes for Cisco UCS Software Release 2.2(3h). October 8, 2015 Updated release notes for Cisco UCS Software Release 2.2(6c).

October 17, 2015 Added CSCuv45173 to the Known Limitations table. This issue has a software advisory associated with it. November 4, 2015 Updated release notes for Cisco UCS Software Release 2.2(6d).

November 16, 2015 Updated release notes for Cisco UCS Software Release 2.2(5d). December 14, 2015 Updated release notes for Cisco UCS Catalog Release 2.2.6e.T. December 16, 2015 Updated release notes for Cisco UCS Software Release 2.2(6e).

January 18, 2016 Updated the Behavior Changes section for Release 2.2(6c). February 2, 2016 Updated release notes for Cisco UCS Software Release 2.2(6f). February 9, 2016 Updated release notes for Cisco UCS Software Release 2.2(3j). February 29, 2016 Updated release notes for Cisco UCS Software Release 2.2(6g).

March 31, 2016 Updated release notes for Cisco UCS Software Release 2.2(7b). April 18, 2016 Updated the New Software Features description for Release 2.2(7b). May 13, 2016 Updated release notes for Cisco UCS Software Release 2.2(3k). May 18, 2016 Updated release notes for Cisco UCS Software Release 2.2(6i). May 24, 2016 Added CSCuz74973 to the Open Caveats for Cisco UCS Software Release 2.2(3b), and updated the workaround for CSCut63966.

June 2, 2016 Updated release notes for Cisco UCS Software Release 2.2(7c). June 13, 2016 Updated the note in Updating Cisco UCS Release.

June 17, 2016 Added CSCut46044 and CSCup58725 to the Open Caveats for Cisco UCS Software Release 2.2(3a). Added CSCuj84274 to the Open Caveats for Cisco UCS Software Release 2.2(1a). Added CSCut46044 to the Security Fixes for Cisco UCS Software Release 2.2(7b). June 20, 2016 Removed note for UCS-ML-1X324RU-G and UCS-ML-1X644RU-G. Added a note for UCS-ML-1X324RV-A and UCS-ML-1X644RV-A. July 5, 2016 Updated release notes for Cisco UCS Software Release 2.2(6j). July 13, 2016 Updated release notes for Cisco UCS Software Release 2.2(8a).

Updated the Recommended Software Version for C200, C210, and C250 M2 servers. July 29, 2016 Updated release notes for Cisco UCS Software Release 2.2(7d). August 8, 2016 Updated the New Software Features description for Release 2.2(7b). August 12, 2016 Added CSCva87230 to the list of open caveats for release 2.2(8a). August 24, 2016 Updated release notes for Cisco UCS Software Release 2.2(8b). Added software advisory associated with CSCva87230.

August 26, 2016 Updated release notes for Cisco UCS Software Release 2.2(7e). September 29, 2016 Updated release notes for Cisco UCS Software Release 2.2(8c). October 18, 2016 Updated release notes for Cisco UCS Software Release 2.2(8d).

November 21, 2016 Added CSCuz74973 to the Resolved Caveats for Cisco UCS Software Release 2.2(7b). November 23, 2016 Updated release notes for Cisco UCS Software Release 2.2(8e)T. December 22, 2016 Updated release notes for Cisco UCS Software Release 2.2(8f). January 30, 2017 Updated release notes for Cisco UCS Software Release 2.2(3l).

March 14, 2017 Updated release notes for Cisco UCS Software Release 2.2(8g). September 12, 2017 Updated the list of security fixes with CSCvf35705. November 21, 2017 Updated release notes for Cisco UCS Software Release 2.2(8i). December 15, 2017 Updated the Resolved Caveat version for CSCuu33864. To use Cisco UCS Manager your computer must meet or exceed the following minimum system requirements: • The Cisco UCS Manager GUI is a Java-based application which requires Java Runtime Environment 1.6 or later.

• Cisco UCS Manager uses web start and supports the following web browsers: • Microsoft Internet Explorer 9.0 or higher • Mozilla Firefox 7.0 or higher • Google Chrome 14.0 or higher • Adobe Flash Player 10 or higher is required for some features • Cisco UCS Manager is supported on the following operating systems: • Microsoft Windows 7 with minimum 4.0 GB memory • Red Hat Enterprise Linux 5.0 or higher with minimum 4.0 GB memory • Cisco UCS Central integration: • Cisco UCS Manager Release 2.2(1) and 2.2(2) can only be registered with Cisco UCS Central, Release 1.1(1b) or higher. • Cisco UCS Manager Release 2.2(3) and later releases can only be registered with Cisco UCS Central, Release 1.2(1a) or higher. • Cisco UCS Manager Release 2.2(7) and later releases require Cisco UCS Central, Release 1.4(1b) or higher. Note For more information, see the Feature Support Matrix section of the.

The Cisco UCS Manager uses the catalog to update the display and configurability of server components such as newly qualified DIMMs and disk drives. The Cisco UCS Manager Capability Catalog is a single image, but it is also embedded in Cisco UCS Manager. Cisco UCS Manager 2.2(x) releases work with any 2.2(x) catalog file, but not the 1.x, 2.0 or 2.1 catalog versions. If a server component is not dependent on a specific BIOS version, using it and having it recognized by Cisco UCS Manager is primarily a function of the catalog version.

The catalog is released as a single image in some cases for convenience purposes in addition to being bundled with UCS infrastructure releases. See Table 5 for details on the mapping of versions to bundles.

Release 2.2(4b) adds support for the following: • Cisco UCS VIC 1227T adapter modular LOM (mLOM) for Cisco UCS C220 M4 and C240 M4 servers • Cisco UCS VIC 1225T adapter for C-Series servers 1 • Cisco UCS VIC 1340 and VIC 1380 adapters for Cisco UCS B420 M3 server 2 • Cisco UCSC-PCIE-Q8362 adapter for all M3 and M4 C-Series servers • Cisco Nexus 2232TM-E 10GE Fabric Extender with support for Cisco UCS VIC 1225T and VIC 1227T adapters. 1 Except for Cisco UCS C22 M3, C24 M3 and C420 M3 servers 2 Cisco UCS VIC 1340 and VIC 1380 adapters only support Cisco 6200 Series Fabric Interconnects and later models. Release 2.2(2c) adds support for the following: • B22 M3 servers shipping with Intel E5-2400 v2 CPUs. • B420 M3 servers shipping with Intel E5-4600 v2 CPUs. • B260 M4 servers shipping with two Intel E7-2800 v2 or E7-4800 v2 or E7-8800 v2 CPUs. • B460 M4 servers shipping with four Intel E7-4800 v2 or E7-8800 v2 CPUs.

• C22 M3/C24 M3 servers shipping with Intel E5-2400 v2 CPUs. • C460 M4 servers shipping with two or four Intel E7-4800 v2 or E7-8800 v2 CPUs. • Chassis with updated backplane and High Voltage DC support (200v DC - 380v DC) - UCSB-5108-HVDC. Release 2.2(8a) adds support for the following: • Next Boot—The maintenance policy now provides an On Next Boot option. This option is used in combination with either User Ack or Timer Automatic.

With the On Next Boot option enabled, one of the following conditions can trigger the associated FSM to apply the changes waiting for the User Ack, or the Timer Automatic maintenance window. • If the host OS reboots, shuts down, or resets, initiated from an external, non-UCS source • If the server resets, or shuts down • 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. • Health monitoring of end points—Enhanced health monitoring of end points for fabric interconnects, IOMs, FEXes, blade servers, and rack servers. • 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. The power sync policy applies to all the service profiles by default. You can edit the default policy, but cannot delete it. You can also create your own policies and apply them to service profiles.

• Factory reset of blade servers—You can now reset a blade server to its factory settings. By default, the factory reset operation does not affect storage drives and flexflash drives. This is to prevent any loss of data. However, you can also choose to reset these devices to a known state.

• Support for 160 LDAP group maps—Cisco UCS Manager now supports a maximum of 160 LDAP group maps. • Virtual Volume Support—Virtual volume support is now supported for ESXi 5.5 and higher. Release 2.2(7b) adds support for the following: • Firmware Upgrade Checks the VIF/Interface Status After Fabric Interconnect Reboot—During firmware upgrade, to ensure proper functioning of all services on the fabric interconnect, it is essential to ensure that port configurations and services that go down when the fabric interconnect reboots are re-established after the fabric interconnect comes back up. Cisco UCS Manager displays any service that is not re-established after the last reboot of a fabric interconnect. • 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.

• Ability to perform UCS Manager initial configuration without console connectivity based on DHCP lease availability. • 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 • Locator LED support for server hard-disks—You can now identify where a specific disk is inserted in a blade or rack server using the local locator LED.

• When you add new servers or adapters to an existing Cisco UCS system with a Cisco UCS Manager release that does not support these servers and adapters, discovery of the system may fail. In case of such a failure, the FSM will display an error message that the server or adapter is not supported on the current UCS firmware version. To resolve this issue, do one of the following: • Update the Capability Catalog to the latest compatible release • Upgrade the Cisco UCS Manager infrastructure firmware to the version required by the new hardware. • Provision to Reset Peer I/O Modules to Factory Defaults—Sometimes, I/O module upgrades can result in failures or I/O modules can become unreachable from Cisco UCS Manager due to memory leaks. You can now reboot an I/O module that is unreachable through its peer I/O module.

Resetting the I/O module restores the I/O module to factory default settings, deletes all cache files and temporary files, but retains the size-limited OBFL file. • vNIC template CDN Source—Enables you to select the Consistent Naming Device (CDN) Source as the vNIC Name, which in turn can either be customized or derived from the vNIC instance. • 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. • PCH SSD Controller Definition—Cisco UCS Manager Platform Controller Hub (PCH) Solid State Drive (SSD) Controller Definition provides a local storage configuration in storage profiles where you can configure all the disks in a single RAID or in a JBOD disk array. • Host Firmware Package Enhancement—You can now exclude firmware of specific components from a host firmware package either when creating a new host firmware package or when modifying an existing host firmware package. For example, if you do not want to upgrade RAID controller firmware through the host firmware package, you can exclude RAID controller firmware from the list of firmware package components.

Local disk firmware is excluded from the host firmware package by default. • Installed Firmware Tab Enhancement—The Installed Firmware tab now displays all the firmware available on the blade server, including SAS controller firmware, FlexFlash controller firmware, and Disk firmware. • Provision to suppress VIF down alert—When a blade server that is associated with a service profile is shut down, the VIF down alert F0283 and F0479 are automatically suppressed. • EFI Shell as a Boot Device—You can create a boot policy with an EFI Shell as the boot device.

Booting from an EFI Shell prevents loss of data and provides more options to script, debug, and control various booting scenarios. EFI Shell is supported as a boot device only in the Uefi boot mode. • Multicast Hardware Hash—In a port channel, by default, ingress multicast traffic on any port in the fabric interconnect (FI) 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.

• Reset All Memory Errors—Provides the ability to clear all the errors from the UCS Manager. • CPLD Update of the UCSB-MRAID12G Storage Controller—Starting with Cisco UCS Manager Release 2.2(7b), the infrastructure bundle now supports a CPLD component update. The CPLD update for the UCSB-MRAID12G storage controller can be triggered by doing one of the following: • Re-acknowledging the server—If the server did not go through a deep-assoc after upgrading to the Cisco UCS Manager 2.2(7) or later releases. • Updating the associated HFP with a supported B bundle—If the server was associated after upgrading to the Cisco UCS Manager 2.2(7) or later releases. • VM-FEX Support—Support for ESX VM-FEX added. The support matrix in the Hardware and Software Interoperability Matrix for this release provides more details. • SHA-2 Certificate Support—Support for SHA-2 certificate added.

Release 2.2(4b) adds support for the following: • Server Pack—This feature allows you to support new server platforms* on existing infrastructure without requiring a complete firmware upgrade. In this model, new B/C server bundles enabling the new servers will be supported on the previous infrastructure A bundle. For example, Release 2.2(5) B/C server bundles are supported with Release 2.2(4) infrastructure A bundle as highlighted in. New features introduced in the B/C bundles may only become available after upgrading the A bundle to the respective version. The Server Pack feature provides the additional flexibility of adding new server platforms to active UCS domains without incurring the operational overhead of upgrading firmware across the whole domain. *The feature will apply to select server platforms. • RDMA over Converged Ethernet (RoCE) for Microsoft SMB Direct—RoCE is a link layer protocol, and hence, it enables communication between any two hosts in the same Ethernet broadcast domain.

RoCE delivers superior performance compared to traditional network socket implementations because of lower latency, lower CPU utilization and higher utilization of network bandwidth. RoCE for Microsoft SMB Direct is supported only on Windows 2012 R2 with Cisco UCS VIC 1340 and 1380 adapters. • LLDP Support for Fabric Interconnect vEthernet Interfaces—You can enable and disable LLDP on a vEthernet interface and retrieve information about LAN uplink neighbors. When using Cisco UCS with Cisco Application Centric Infrastructure (ACI), LAN uplinks of the Fabric Interconnect are connected to ACI leaf nodes. Enabling LLDP on a vEthernet interface will help the Application Policy Infrastructure Controller (APIC) to identify the servers connected to the Fabric Interconnect by using vCenter. • Policy-Based Port Error Handling—If Cisco UCS Manager detects any errors on active IOM Network Interface (NIF) ports, and if the Error-disable setting is enabled, Cisco UCS Manager automatically disables the respective FI port that is connected to the IOM NIF port that had errors. When a FI port is error disabled, it is effectively shut down and no traffic is sent or received on that port.

• Advanced Local Storage Configuration: • Configuration of Storage Profiles and multiple virtual drives—To allow flexibility in defining the number of storage disks, roles and usage of these disks, and other storage parameters, you can create and use storage profiles. A storage profile encapsulates the storage requirements for one or more service profiles. You can also configure multiple virtual drives. • Configuration of a local LUN or a JBOD as the primary boot device • Support for local storage configuration on multiple storage controllers • Support for out-of-band configuration for local storage • Pass-through Capability for Gen 3 Fusion IO Mezzanine Cards—Cisco UCS Manager now supports the pass-through capability of Gen 3 Fusion IO Mezzanine cards for blade servers. Pass-through for Mezzanine cards is a hardware capability that extends the available ports for the Cisco UCS VIC 1340 or VIC 1240 adapter though the Mezzanine slot, and brings the total I/O bandwidth of the VIC 1340 or VIC 1240 adapters to dual 4 x 10 GbE.

• Fabric Interconnect Traffic Evacuation—During upgrade, you can evacuate the secondary Fabric Interconnect traffic to ensure that there is no traffic flowing through the Fabric Interconnect from all servers attached to it through an IOM or FEX. This allows you to ensure that traffic will properly failover to the other Fabric Interconnect before you can proceed with the firmware upgrade. • Per Fabric Interconnect Chassis Reacknowledgment—You can now reacknowledge a chassis per Fabric Interconnect. This allows you to maintain connectivity to the chassis through the other Fabric Interconnect.

• TPM and TXT Configuration through UCSM—The Trusted Platform Module (TPM) is a component that can securely store artifacts, such as passwords, certificates, or encryption keys, which are used to authenticate the server. A TPM can also be used to store platform measurements that help ensure that the platform remains trustworthy. Intel Trusted Execution Technology (TXT) provides greater protection for information that is used and stored on the server. This release supports TPM and TXT configuration on Cisco UCS M4 blade and rack-mount servers through Cisco UCS Manager.

TPM is enabled by default and TXT is disabled by default. • Consistent Device Naming Support—Consistent Device Naming (CDN) allows Ethernet interfaces to be named in a consistent manner.

This makes Ethernet interface names more persistent when adapter or other configuration changes are made. Note CDN is supported only on Windows 2012 R2.

• Fabric Scale Improvements—Each Cisco UCS domain now supports: • Up to 8 appliance ports • 320 endpoints • Up to 320 vHBAs per Fabric Interconnect • Scriptable vMedia: • You can configure the file name of the vMedia mount image to use the name of the service profile with which the vMedia policy is associated. • You can specify the authentication protocol to be used when you select CIFS as the communication protocol with the remote server. • Support for Service Profile Migration with UEFI Boot Mode—When a service profile is migrated from one server to another, the BIOS on the destination server will continue to load the boot loader information and boot in UEFI boot mode. • NVGRE with IPv6 and VMQ—You can enable NVGRE with VMQ and NVGRE with IPv6 on the same vNIC.

• usNIC Support with Intel® MPI—Intel® Message Passing Interface (MPI) is developed for high performance computing. You can now use the Intel MPI Library version 4 or 5 with Cisco user-space NIC (Cisco usNIC) for a low-latency and high-throughput communication transport. • Other Enhancements: • While the infrastructure firmware is being upgraded, an automatic, internal, full state backup file is created. • When creating an SNMP trap, you can use an IPv4 address, or an IPv6 address, or a fully qualified domain name of an IPv4 address as the SNMP host name. • A new tech-support memory option is introduced to create a tech-support file with only server memory information gathered across the Cisco UCS domain.

• When creating a server pool qualification policy, you can now specify the storage disk type as HDD, SSD or unspecified. Release 2.2(8a) introduces the following behavior changes: • CSCux87408—Initializing the chassis seeprom takes too long to complete. • Old behavior: In a new chassis, if the chassis seeprom is not initialized, IOMs are not discovered on certain slots. The chassis seeprom takes too long to initialize. IOM behavior is as follows: • A new IOM that has never reached a stable state, and that is running any version of Cisco UCS Manager Release 2.2(6) will be stuck in uboot after 4 attempts of booting each Release 2.2(6) image. • An IOM that has previously reached a stable state, and that is running any version of Cisco UCS Manager Release 2.2(6) will go into an infinite reboot loop.

• New behavior: In a new chassis, if the chassis seeprom is not initialized, IOMs that are running any version of Cisco UCS Manager Release 2.2(x) except Release 2. Saab Wis 2010.Iso. 2(6) can now be discovered on all slots. The chassis seeprom now initializes in the expected time. IOMs running on Release 2.2(6) are discovered if the chassis seeprom is already initialized.

• Impact: The chassis seeprom now initializes in the expected time. • CSCtx87011—TPM details are inconsistent in Cisco UCS Manager GUI and CLI. • Old behavior: The following TPM details were displayed in the Cisco UCS Manager GUI, but were missing from the output of the show tpm detail command—Presence State, and Type. • New behavior: The TPM details shown in the output of the show tpm detail command and the Cisco UCS Manager GUI are now consistent. • Impact: Customers can now list all TPM details through the Cisco UCS Manager CLI as well as the Cisco UCS Manager GUI.

Release 2.2(7b) introduces the following behavior changes: • CSCtx87011—Cisco UCS backup should preserve identities by default. • Old behavior: By default, Preserve Identities is not selected in the GUI when the backup operation is initiated. • New behavior: By default, Preserve Identities is now selected in the GUI when the backup operation is initiated.

• Impact: With Preserve Identities selected by default, allocated identities such MAC addresses, UUIDs, WWxNs and server assignments will be preserved in the backup file. This will allow the system be restored with the exact same identity assignments. To perform a backup of the logical configuration that can be re-used in other systems, customers must clear this selection when performing the backup operation. Release 2.2(6c) introduces the following behavior changes: • CSCuu16791—The Firmware Auto Sync Server Policy is now set to No Actions by default. • Old behavior: The Firmware Auto Sync Server Policy was set to Auto Acknowledge by default, which attempted to push the default Host Firmware Package into blades/rack-servers during discovery. • New behavior: Withe the Firmware Auto Sync Server Policy set to No Actions by default, you not longer have to manually clear the server information from the database, and re-attempt the discovery/integration.

• Impact: The customer can now run mixed firmware environments and manage the firmware directly. • During the creation of a host firmware package, Cisco UCS Manager no longer allows checking or clearing individual components of a blade package or rack package.

• Old behavior: During creation of a host firmware package, if the customer selects the blade package, or rack package, or both, they can check or clear check boxes associated with any components, but they cannot modify the components of these packages. When they click Save Changes, Cisco UCS Manager displays the following error message: Blade Package and/or Rack package is set. Individual PackImage modification is not allowed for this Host Firmware Package. • New behavior: Starting with Cisco UCS Manager Release 2.2(6c), during creation of a host firmware package, if the customer selects the blade package, or rack package, or both, all components listed under these packages are grayed out and cannot be selected or cleared. They cannot modify the components of these packages. • Impact: The customer will now not be able to check or clear individual components listed under blade or rack packages, if the blade package, or rack package, or both, are selected during creation of a host firmware package.

Release 2.2(5a) introduces the following behavior changes: • CSCut47053—Support all VIC slots (1,2,4,5) for UCSM-managed single wire management of UCS C240 M4 rack-mount servers. • Old behavior: In UCSM mode, single wire management of UCS C240 M4 servers was only supported in Riser 1 slot 2. • New behavior: In UCSM mode, single wire management of UCS C240 M4 servers is now supported in Riser 1 (slots 1 and 2) and Riser 2 (slots 4 and 5). • Impact: The customer can now insert the VIC in Riser 1 (slots 1 and 2) and Riser 2 (slots 4 and 5) for single wire management of UCS C240 M4 rack servers. Release 2.2(4b) introduces the following behavior changes: • Cisco UCS B200 M4, B260 M4, and B460 M4 blade servers no longer support QLogic (UCSB-MEZ-QLG-03) and Emulex (UCSB-MEZ-ELX-03) mezzanine adapter cards.

• Old behavior: Cisco UCS B200, B260, and B460 M4 servers supported QLogic (UCSB-MEZ-QLG-03) and Emulex (UCSB-MEZ-ELX-03) mezzanine adapter cards with Cisco UCS Manager Release 2.2(3). • New behavior: Starting with Cisco UCSM Release 2.2(4b), Cisco UCS B200 M4, B260 M4, and B460 M4 blade servers no longer support QLogic (UCSB-MEZ-QLG-03) and Emulex (UCSB-MEZ-ELX-03) mezzanine adapter cards.

• Impact: These servers will fail to complete the discovery process if upgraded to Cisco UCS Manager Release 2.2(4b) and later releases. • CSCus73964—Infrastructure bundle download causes environment to downgrade. • Old behavior: Manual upgrade or activation of Cisco UCS Manager, Fabric Interconnects, and IOM was allowed even if the startup version of the default infrastructure bundle was set. • New behavior: If the startup version of the default infrastructure bundle is set, manual upgrade or activation of Cisco UCS Manager, Fabric Interconnects, and IOM is not allowed. • Impact: To successfully complete a manual upgrade or activation of Cisco UCS Manager, Fabric Interconnects, and IOM, the customer has to make sure that the startup version is cleared before starting manual upgrade or activation. This can be done through the Cisco UCS Manager CLI or the Cisco UCS Manager GUI.

• CSCuq78417—Change reserved VLAN range from 4030 to 4047. • Old behavior: The range of reserved VLAN IDs was from 3968 to 4047. • New behavior: The range of reserved VLAN IDs is now from 4030 to 4047. • Impact: Before downgrading from Cisco UCS Manager Release 2.2(4b), the customer has to make sure that the VLAN IDs from 3968 to 4030 are not user-configured.

VLAN IDs from 3968 to 4030 are system-reserved VLAN IDs in earlier releases. Release 2.2(2c) introduces the following behavior changes: • CSCul74278—Adding or deleting a local storage device in boot policy will cause PNUOS boot irrespective of 'Reboot on Update' flag settings. • Old behavior: PNUOS boot occurs only when local device is added and SAN device is removed (or vice versa) in boot policy.

• New behavior: PNUOS boot always occurs after a local storage device is added or removed in boot policy. • Impact: This change allows enabling or disabling of the boot BIOS on local storage controller even in the presence of SAN boot devices in boot policy. • CSCuj81638—The system no longer returns 'empty-pool' faults for empty default pools under the root org. • Old behavior: When a new system comes online for the first time, 'empty-pool ' faults get raised for all empty default pools (compute-pool-default, ip-pool-ext-mgmt, ip-pool-iscsi-initiator-pool, mac-pool-default, uuid-pool-default, wwn-pool-default, and wwn-pool-node-default) under the root org. (These fault IDs include F0463, F0464, F0465, F0466, and F0476.) • New behavior: An 'empty-pool' fault will no longer be raised for any empty default pool under the root org. Instead, the 'empty-pool' fault will only be raised for user-generated empty pools.

• Impact: This change allows default pools to remain empty when user has pools under a created org. Table 6 Security Fixes in Release 2.2 Release Defect ID CVE (s) Description 2.2(8i) CSCvb61637 CSCvb86764 CSCvb86775 CSCvb86797 CSCvb86816 CVE-2017-6600 CVE-2017-6601 CVE-2017-6602 CVE-2017-6598 CVE-2017-6597 A vulnerability in the CLI of the Cisco Unified Computing System Manager could allow an authenticated, local attacker to perform a command injection attack. The security vulnerabilities are addressed. 2.2(8i) CSCvc37931 CVE-2017-6604 The following Cisco UCS Manager and Cisco Integrated Management Controller versions may be affected by the redirection vulnerabilities: For Unified Computing System (UCS) B-Series M3 and M4 Blade Servers, this affects any of the 2.2(8) and 3.1(2) blade bundle versions. None of the 3.0 or 3.1(1) blade bundle versions are affected. For Unified Computing System (UCS) C-Series M3 and M4 Rack Servers, this affects 3.0(1c) CIMC versions. None of the 1.5 or 2.0 CIMC versions are affected.

Table 7 Resolved Caveats in Release 2.2(8i) Defect ID Description First Bundle Affected Resolved in Release CSCvg44307 Communication between two end hosts no longer fails within the same VLAN and fabric interconnect. 2.2(4b)A 2.2(8i)A CSCux49157 UCS Manager now has a user configurable option to select the TLS version. 2.2(6d)A 2.2(8i)A CSCuz98957 UCS Manager no longer incorrectly reports the amount of drive slots on B200-M2 blade servers. 2.2(7b)A 2.2(8i)A CSCva31113 After a fabric interconnect reboot, the fabric interconnect may not fully boot and become network accessible.

The Serial Console connection to the fabric interconnect may show a 'loader' prompt or show initial configuration prompts. 2.2(3d)A 2.2(8i)A CSCvb00303 During a Server discovery, Rack servers no longer get stuck and may not discover due to a lost connection status from the B side while only A side is appearing. This may occur after upgrading to 2.2(8b) and performing an Erase Samdb operation and then enabling all required server ports to bring the server up. 2.2(8b)A 2.2(8i)A CSCvc58789 A port no longer shows a disabled error after 10 consecutive DFE tuning failures.

2.2(8c)A 2.2(8i)A CSCvc92275 A kernel panic no longer occurs on the fabric interconnect which could cause a reboot. The following command: show logging onboard stack-trace Shows that the panic may occur in the process usd_mts_kthread. The call trace can be reviewed for a full match to this defect. 2.2(6e)A 2.2(8i)A CSCvd02546 During a UCS Manager upgrade from 2.2(3l) to 3.1(2) only the secondary fabric interconnect may be upgraded.

2.2(1b)A 2.2(8i)A CSCvd54116 Setting a custom cipher suite for UCS Manager HTTPS to remove the usage of TLS v1.0 and 1.1, no longer results in a 'handshake failure' error message when attempting to open a Java login to UCS Manager or a KVM session to a blade server. 2.2(8c)A 2.2(8i)A CSCve19522 UCS domains running version 3.1(3a) no longer moves to a state of lost visibility after a certificate is regenerated on UCS Central and is able to recover.

In some cases, the UCS 3.1(3a) domain registration may also get stuck in a registering state. 2.2(8g)A 2.2(8i)A CSCvg06830 After adding a secondary fabric interconnect to a standalone setup and converting it to clustered setup, the VLAN 1 may not be added to the uplink port-channel, and no longer causes the vEth on the B side to fail pinning and render the subordinate fabric interconnect unusable. Table 8 Resolved Caveats in Release 2.2(8g) Defect ID Description 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 • CD/DVD • Local Drive • Network Adapter (PXE) 2.2(3f)B 2.2(8g)B CSCvb85331 The following fault no longer occurs after a UCS Manager software upgrade. Code: F1781 Description: Management database version mismatch detected failover may not complete Affected Object: sys/mgmt-entity-B Name: Mgmt Entity Mgmt Db Version Mismatch Cause: Replication Failure Type: Management 2.2(8c)A 2.2(8g)A CSCvc39322 For B260 M4 Blades, BIOS v3.1.2.2 no longer intermittently fails Windows HLK and HCK Trusted Platform Module (TPM) tests on Windows Server 2016 and Windows Server 2012 R2.

2.2(7b)B 2.2(8g)B CSCvc10791 A DME process no longer crashes when the dynamic vNIC and static vNIC contain a different adminVcon property value. 2.2(3e)A 2.2(8g)A CSCvc89242 The Fabric Interconnect no longer reboots due to a CDP process crash. 2.2(6e)A 2.2(8g)A CSCvc46313 The remote operation of making the LUN online from UCS Central no longer fails with the error message: Global Service profile [org-root/org-GKDC/org-/ls-SP_3260_03] can not be modified from UCS domain.

Please make the changes from UCS Central that you are registered with. 2.2(4b)A 2.2(8g)A CSCvc60876 The 6248, 6296, and 6332 Series Fabric Interconnects no longer sends Smart Call Home messages in the wrong format. 2.2(8b)A 2.2(8g)A CSCvc31867 When upgrading the SSD to firmware 32F3Q, the firmware is no longer truncated and written as 2F3Q, which may cause a second request for the reboot of the server. 2.2(8a)A 2.2(8g)A CSCux96072 During heavy I/O traffic, the Cisco 12G Modular RAID controller no longer goes offline with the Storage Controller SLOT HBA inoperable error logged in CIMC event logs. 2.2(6e)C 2.2(8g)C CSCvc48423 Downloading a bundle more than 1GB in size from a local desktop no longer fails.

2.1(1a)A 2.2(8g)A. Table 9 Resolved Caveats in Release 2.2(8f) Defect ID Description First Bundle Affected Resolved in Release CSCuy81688 From Cisco UCS Manager tech-support, running /var/sysmgr/sam_logs/httpd_cimc.log on the affected fabric interconnect no longer shows the exceeded max time without restart error. From Cisco UCS Manager tech-support, running /ls_l.out on the affected fabric interconnect no longer shows the existence of a 'cimcrestart' file under /isan/apache/conf/. The modified date is now updated. 2.2(8a)A 2.2(8f)A CSCuz53730 UCSM httpd process no longer experiences high memory usage or crash with a core file showing indications of memory allocation failure. 2.2(2c)A 2.2(8f)A CSCva35757 Latency between the UCS Manager Client and fabric interconnect no longer causes the firmware page to load slowly. 2.2(7b)A 2.2(8f)A CSCvb11667 Server with UEFI BIOS enabled, no longer fails to SAN boot from a target LUN with an ID other than 0 and using T10 DIF protection.

2.2(8d)B 2.2(8f)B CSCvb16804 Booting from SAN to 4K UEFI target no longer fails. 2.2(8a)B 2.2(8f)B CSCvb08928 A fabric interconnect no longer reboots on VLAN deletion due to a FWM hap reset. 2.2(5a)A 2.2(8f)A CSCvb78971 When attempting the auto-install of UCS Manager, the fabric interconnect upgrade no longer fails when the /var/tmp usage exceeds 10%. 2.2(3k)A 2.2(8f)A CSCvb82862 EUI-64 bit addresses are now valid for storage connection policies or SAN boot targets. 2.2(8d)A 2.2(8f)A CSCvb95978 On C460 M4 servers, TPM version 1.2 no longer fails to initialize after installing ESXi OS, and enabling and activating TPM and TXT. 2.2(8d)B 2.2(8f)B CSCvc17769 The fabric interconnect no longer crashes when the bound interface of a Veth is in the Not Initialized State during a VLAN configuration change. 2.2(7c)A 2.2(8f)A.

Table 11 Resolved Caveats in Release 2.2 (8d)T Defect ID Description First Bundle Affected Resolved in Release CSCva53726 UCS Manager no longer allows the downgrade of firmware for the following rack servers installed with v4 CPU models to a version less than the minimum required version of CIMC / BIOS firmware: • UCSC-C240-M4L • UCSC-C240-M4S • UCSC-C240-M4S • UCSC-C240-M4SX • UCSC-C220-M4L • UCSC-C220-M4S • UCSC-C240-M4SNEBS After a downgrade, servers no longer fail the BIOS post. 2.2(7c)T 2.2(8d)T.

Table 12 Resolved Caveats in Release 2.2 (8c) Defect ID Description First Bundle Affected Resolved in Release CSCuu29425 In RHEL 7.0 and 7.1 the ENIC driver now properly handles packets received on the native VLAN. 2.2(4b)B 2.2(8c)B CSCuw50361 While collecting IOM tech-support by using the show platform software satctrl global output from the IOM, the HIF/NIF interfaces of an IOM no longer flap due to SDP heartbeat timeout. 2.2(4b)A 2.2(8c)A CSCux11611 Seagate hard drives left spinning idle without an operating system installed or setup with the JBOD configuration without read or write activity are no longer prone to failure. Impacted hard drives are listed here: • UCS-HD4T7KS3-E • UCSC-C3X60-HD4TB (4TB) • UCS-HDD3TI2F214 (3TB) • UCS-HDD2TI2F213 (2TB) • UCS-HDD1TI2F212 (1TB) • UCS-HD6T7KL4K • UCSC-C3X60-HD6TB • UCSC-C3X60-6TBRR 2.2(7c)B 2.2(8c)B CSCuy79306 When Cisco UCS C-Series servers with VIC 1225 or VIC 1227 are directly connected to Cisco Nexus 9000 switches, after making a large change on a switch, ports no longer flap or show as down on the switch but up on the server. 2.2(3f)B 2.2(8c)B CSCuz41121 When booting to RHEL or running system stress tests, Cisco UCS B420 M4 servers with certain Intel ® E5 v3 CPUs no longer report QPI Correctable System Event Logs with the following error message: Link Layer CRC successful reset with no degradation 2.2(8a)B 2.2(8c)B CSCuz91263 A vulnerability in the command-line interface (CLI) of the Cisco UCS Manager and UCS 6200 Series Fabric Interconnects is resolved. 2.2(1a)A 2.2(8c)A CSCuz96855 UCS M71KR cards no longer crashes with the error “E4194871”. 2.2(6e)B 2.2(8c)B CSCva27558 In scenarios such as traffic loops in external networks, a series of MAC add or delete operations no longer causes the MAC address to display in the software table, and nor in the hardware table for all the ASICs.

2.2(5c)A 2.2(8c)A CSCva34343 UCS Manager no longer reports false alerts due to P0V75_STBY sensor in Cisco B200 and M4 Blade Servers. 2.2(6e)B 2.2(8c)B CSCva38476 An infrastructure software upgrade to UCS Manager 2.2(7b) or higher no longer fails when both fabric interconnects are incompatible or when one of the fabric interconnects is unresponsive. 2.2(7b)A 2.2(8c)A CSCva71801 UCS Manager no longer fails to synchronize with IPv6 NTP server. 2.2(8a)A 2.2(8c)A CSCva96740 Changes in adapter policy from UCS Manager now triggers a server redeploy. 2.2(8b)A 2.2(8c)A CSCvb35827 Upgrade failure no longer occurs when a Cisco UCS system is configured with more than 128 LDAP groups and upgrade is performed either from Cisco UCS Manager Release 2.2.8 to Cisco UCS Manager Release 3.1(2b) or from Cisco UCS Manager Release 3.1(2b) to a later release. 2.2(8a)A 2.2(8c)A.

Table 13 Resolved Caveats in Release 2.2 (8b) Defect ID Description First Bundle Affected Resolved in Release CSCuu40978 The syslog is now truncated after it reaches the configured maximum size. It no longer fills up the Fabric Interconnect file system. 2.2(3d)A 2.2(8b)A CSCuz54661 Cisco B200 M3 Server no longer fails to post if NUMA is disabled. 2.2(6g)B 2.2(8b)B CSCuz86450 The server no longer reboots because the system does not accept user input on the order property of adaptorHostIf. 1.4(1j)A 2.2(8b)A CSCva08256 Cisco CIMC and BIOS no longer get stuck updating or activating with the host firmware pack when the new host firmware pack has the same name and version as the system being updated. 2.2(7b)A 2.2(8b)A CSCva34426 Cisco UCS 3X60 Server no longer fails to boot from LSI RAID controller managed disk slots 1 or 2, when the disks are in JBOD mode.

2.2(7c)A 2.2(8b)A CSCva36835 A board controller update now ensures proper functionality of the LSI controller during a warm reboot or reset signal when using the Cisco B460 M4 or B260 M4 blade servers. 2.2(8a)B 2.2(8b)B CSCva54957 A reboot is no longer triggered without a “user -ack” when modifying a service profile that requires a reboot while shallow association is failing. 2.1(3a)A 2.2(8b)A CSCva67159 Cisco UCS Manager httpd no longer fails to start when the default keyring was deleted.

2.2(8a)A 2.2(8b)A CSCva72096 Cisco UCS servers running Intel E5 Xeon v4 CPUs no longer crash with a signature pointing to internal parity errors, page fault, general detect, or undefined opcode exceptions. 2.2(4b)B 2.2(8b)B CSCva87230 A temporary loss in server connectivity no longer occurs when performing a Cisco UCS Manager upgrade to release 2.2(8a) from a build that does not contain the fix for CSCuq57142. 2.2(8a)A 2.2(8b)A. Table 14 Resolved Caveats in Release 2.2 (8a) Defect ID Description First Bundle Affected Resolved in Release CSCuv13019 When the desired power state of a service profile was set to Power ON, and Cisco UCS Manager triggered shallow discovery for the blade server, server shutdown from the OS was powered ON by Cisco UCS Manager. This issue is now resolved.

2.1(1f)B 2.2(8a)B CSCuv31912 UCS Manager iptables are no longer duplicating rules in the FORWARD table. 2.2(3d)A 2.2(8a)A CSCuw16950 FSM failures no longer trigger the addition of duplicate entries in IP tables.

2.2(3b)A 2.2(8a)A CSCux59912 A Cisco UCS system with servers connected to a Cisco Nexus 2232 FEX no longer experiences bladeAG cores. 2.2(5c)C 2.2(8a)C CSCux63909 FC abort is no longer observed while running uplink port flap test on uplink Ethernet port-channel from an FI to a Cisco Nexus 7000 switch. 2.0(2m)B 2.2(8a)B CSCuy98678 Cisco UCS 6296 fabric interconnect no longer crashes unexpectedly with kernel panic, and impact any devices connected the fabric interconnect. 2.2(6c)A 2.2(8a)A CSCuz92668 Vulnerabilities affecting various versions of NTPd are now resolved. 2.2(1a)A 2.2(8a)A CSCva04106 Removing a SAN port channel member no longer causes SAN ports to go down. 2.2(3d)A 2.2(8a)A. Table 16 Resolved Caveats in Release 2.2(7d) Defect ID Description First Bundle Affected Resolved in Release CSCuz69100 Disk Firmware update no longer fails for local disks on a C240 rack server that has an UCSC-SAS12GHBA storage controller.

2.2(7b)A 2.2(7d)A CSCuz86450 The server no longer reboots because the system does not accept user input on the order property of adaptorHostIf. 1.4(1j)A 2.2(7d)A CSCuz65286 Cisco UCS Manager firmware upgrade failed with the following message UCSM upgrade validation failed when the default value for IO throttle count in the FC adapter policy had a value of 16.

This issue is resolved. The default IO throttle count is now set to 256.

2.2(3a)A 2.2(7d)A CSCuv45574 After downgrading the controller firmware on C220/C240 M3 systems with LSI 9271-8i controller, the GUID of virtual disks no longer change and the virtual machines running on the ESXi OS no longer become inaccessible. 2.2(6f)A 2.2(7d)A CSCux53224 A fatal error may be observed when creating or removing virtual drives with RAID 5 and RAID 6 controller combinations. This issue is now resolved. 2.2(7c)C 2.2(7d)C CSCva01733 PXE in Legacy Boot mode no longer hangs with excessive unicast or multicast high background traffic with a packet size larger than MTU directed to the client server. This was seen with ESXi Autodeploy on a specific setup which likely had unusually high multicast traffic directed at the client server.

This traffic was not from the PXE server for file transfer, but from some other source. Table 17 Resolved Caveats in Release 2.2 (7c) Defect ID Description First Bundle Affected Resolved in Release CSCul97240 When a UCS rack server is present in a UCS setup, DHCP renewal now triggers Information level syslog messages to be sent to the syslog server configured on Cisco UCS Manager. 2.2(1a)A 2.2(7c)A CSCuq57142 In a port channel universe, the following no longer happen: • A port channel ID may sometimes not be released after use.

This could eventually lead to the universe of port channel IDs being empty, and no port channel IDs being available for use. • After an upgrade, power loss, FI reboot or failover, the empty port channel universe is incorrectly interpreted as a new installation, and repopulated. This leads to duplicate port channel ID allocation when a server is attached to the FI, or when a server is re-acknowledged.

2.2(3a)A 2.2(7c)A CSCuq74472 Unnecessary thermal events on IOM stating “Thermal sensor reading not available” are no longer seen. 2.1(3c)B 2.2(7c)B CSCux58865 DIMM temperature readings are no longer missed when CPUs are in a low power (or “sleep”) mode. 2.1(3d)B 2.2(7c)B CSCuy01645 DIMM temperature readings are no longer not available when more than 16 degrees Centigrade different than the previous reading. 2.2(5b)B 2.2(7c)B CSCux63909 FC abort is no longer observed while running an uplink port flap test on an uplink Ethernet port-channel from an FI to a Cisco Nexus 7000 switch. 2.0(2m)B 2.2(7c)B CSCuy34161 Any DIMM that is functioning correctly is no longer disabled after the reboot of the UCS B250 M2 blade server. 2.0(5c)B 2.2(7c)B CSCuy62783 In a UCS setup with a VIC13xx adapter on blade servers or rack-mount servers, the server or VIC adapter no longer becomes unresponsive after running IO across network file systems.

2.2(3a)B 2.2(7c)B CSCuy64856 The Cisco UCS fabric interconnects (FI) are no longer rebooted with the reboot reason FWM hap reset. 2.1(3h)A 2.2(7c)A CSCuy93451 VLANs are now deleted from the vNICs if they are deleted from the updating vNIC template. 2.2(7b)A 2.2(7c)A CSCuz69373 CATERR faults due to cpu lockup in VIC 1340 no longer occur. 2.2(7b)B 2.2(7c)B. Table 18 Resolved Caveats in Release 2.2 (7b) Defect ID Description First Bundle Affected Resolved in Release CSCuz74973 When you use a B200 M4 server with a UCSB-MRAID12G SAS RAID controller and a CPLD firmware version earlier than version 05D, the B200 M4 server no longer powers off unexpectedly. 2.2(3b)B 2.2(7b)B CSCud75506 The UUID display on ESXi 5.1 is now consistent with the UUID display on UCSM when upgrading ESXi to version 5.1 on UCS B200 M3, B22 M3 and B420 M3 blade servers.

2.0(2r)B 2.2(7b)B CSCuv43349 During server discovery, Cisco UCS Blade server association or disassociation, the following failures are no longer reported: • Waiting for BIOS Post Completion • Unable to get SCSI Device Information from the system 2.2(6e)B 2.2(7b)B CSCuw36128 The buffer overflow condition that caused the statsAG mts queue to leak is now fixed. 2.2(1d)A 2.2(7b)A CSCuw46478 The Local disk Locator LED remains OFF, although enabled in Cisco UCS Manager. 2.2(6j)B 2.2(7b)B CSCuw55142 Cisco UCS B420M4 server with the UCSB-MRAID12G-HE no longer reports the following critical fault: Controller 1 on server is inoperable. Reason: Device non-responsive 2.2(6c)B 2.2(6f)B, 2.2(7b)B CSCux05389 After upgrading to release 2.2(7b) and rebooting the subordinate fabric interconnect, occasional VSAN misconfiguration will no longer occur. 2.2(3f)A 2.2(7b)A CSCux07578 Cisco UCS Blade servers B400 M1 or B400 M2 running on Liberator firmware version 4.10 with SATA drives, no longer experience data consistency failures.

2.2(6f)B 2.2(7b)A CSCux21413 When you remove and reinsert a drive in the same slot, the Locator Storage Locator LED no longer remains on all the time. 2.2(6j)B 2.2(7b)A CSCux66675 After rebooting a Cisco UCS 6296UP FI, all physical interfaces will no longer connect incorrectly with the Cisco UCS C460 M4 servers. 2.2(6c)A 2.2(7b)A CSCux85580 Fabric Interconnect cores will no longer be seen on IGMP. 2.2(3b)A 2.2(7b)A CSCux65310 During blade discovery or CIMC controller reset, a chassis thermal critical fault can be generated due to the time it takes for reconnecting from the IOM to the CIMC.

However, after several minutes this fault clears on its own. 3.1(1e)B 2.2(7b)B CSCut46044 Cisco Unified Computing Server Management Software (UCSM) includes a version of OpenSSL that is affected by the vulnerability identified by the Common Vulnerability and Exposures (CVE) IDs: • CVE-2015-0286 • CVE-2015-0287 • CVE-2015-0289 • CVE-2015-0292 • CVE-2015-0293 • CVE-2015-0209 • CVE-2015-0288 This issue is now fixed. 2.2(3a)A 2.2(7b)A CSCuw19082 During Cisco UCS Manager initial setup, while configuring the fabric interconnect, setup will assume the GUI configuration method if a DHCP lease is obtained for the mgmt interface. In addition, an url will be provided for the setup of the fabric interconnect. 2.2(6c)A 2.2(7b)A.

Table 19 Resolved Caveats in Release 2.2 (6j) Defect ID Description First Bundle Affected Resolved in Release CSCux63909 FC abort is no longer observed while running an uplink port flap test on an uplink Ethernet port-channel from an FI to a Cisco Nexus 7000 switch. 2.0(2m)B 2.2(6j)B CSCva01733 PXE in Legacy Boot mode no longer hangs with excessive unicast or multicast high background traffic with a packet size larger than MTU directed to the client server. This was seen with ESXi Autodeploy on a specific setup which likely had unusually high multicast traffic directed at the client server. This traffic was not from the PXE server for file transfer, but from some other source.

2.2(6e)B 2.2(6j)B. Table 20 Resolved Caveats in Release 2.2 (6i) Defect ID Description First Bundle Affected Resolved in Release CSCuw36128 The buffer overflow condition that caused the statsAG mts queue to leak is now fixed. 2.2(1d)A 2.2(6i)A CSCuw44595 DIMMs with correctable ECC errors are marked Inoperable or Degraded even though correctable errors do not affect normal system operation. This issue is now resolved. 2.2(3a)A 2.2(6i)A CSCuy01645 DIMM temperature readings are no longer missed when the temperature is 16 degrees Centigrade more than the previous reading.

2.2(5b)B 2.2(6i)B CSCuj71400 Cisco UCS Manager no longer displays the “FCoE or FC uplink is down on VSAN X” fault when the member ports for the VSAN are up. 2.2(1a)A 2.2(6i)A CSCuy62783 In a UCS setup with a VIC13xx adapter on blade servers or rack-mount servers, the server or VIC adapter no longer becomes unresponsive after running IO across network file systems. 2.2(3a)B 2.2(6i)B CSCuy34161 Any DIMM that is functioning correctly is no longer disabled after the reboot of the UCS B250 M2 blade server. 2.0(5c)B 2.2(6i)B CSCux58865 DIMM temperature readings are no longer missed when the temperature is 10 degrees Centigrade more than the previous reading. 2.1(3d)B 2.2(6i)B CSCuu40978 The syslog is now truncated after it reaches the configured maximum size.

It no longer fills up the Fabric Interconnect file system. 2.2(3d)A 2.2(6i)A CSCux45723 UCS SNMP memory leaks no longer occur when polling FC interfaces and SNMP processes (Walk/Get/Get Bulk) that parse any of the following SNMP MIBs: • fcIfNonLipF8Out • fcIfTimeOutDiscards • fcIfOutDiscards • fcIfCreditLoss • fcIfTxWtAvgBBCreditTransitionToZero 2.2(3a)A 2.2(6i)A CSCuq57142 In a port channel universe, the following no longer happen: • A port channel ID may sometimes not be released after use. This could eventually lead to the universe of port channel IDs being empty, and no port channel IDs being available for use. • After an upgrade, power loss, FI reboot or failover, the empty port channel universe is incorrectly interpreted as a new installation, and repopulated. This leads to duplicate port channel ID allocation when a server is attached to the FI, or when a server is re-acknowledged. 2.2(3a)A 2.2(6i)A CSCuw02439 When using Cisco UCS M81KR VIC adapters on a system running Cisco UCS Manager Release 2.2(2c), the adapters no longer crash and generate core files. 2.2(2c)B 2.2(6i)B CSCux59298 When using UCS B200 M3 servers with VIC 1240 on a system running Cisco UCSM Release 2.2(2c), network and SAN no longer lose connectivity.

2.2(2c)B 2.2(6i)B CSCuy64856 The Cisco UCS fabric interconnects (FI) are no longer rebooted with the reboot reason FWM hap reset. 2.1(3h)A 2.2(6i)A CSCuz20650 When syslog messages are generated continuously, the syslog suspend timer does not recover.

Thus, no events are sent to the remote syslog server. This issue is now resolved. 2.2(3a)A 2.2(6i)A CSCuu40291 When debug logging is enabled, Cisco UCS Manager tech-support showed that syslogd_debug files were present, but the show debug logfile syslogd_debugs CLI command failed with the following error: Logfile(syslogd_debugs) does not exist This issue is now resolved. 2.2(3a)A 2.2(6i)A. Table 21 Resolved Caveats in Release 2.2 (6g) Defect ID Description First Bundle Affected Resolved in Release CSCux98751 Anytime a new blade is inserted into the chassis, or a blade CIMC controller reboots, a chassis thermal fault is no longer generated because of the time taken to reconnect from the IOM to the CIMC.

2.2(6c)B 2.2(6g)B CSCuv20324 The FCoE storage no longer becomes unavailable or performs very poorly after a reset of either host-attached switch in the case of standalone systems, or after the reset of an IOM or FI in UCS-managed systems when the IOM or FI sends configuration information to the adapter later than 5 seconds after link-up. 2.2(1b)B 2.2(6g)B CSCuv89839 When the fabric interconnect is in switch mode with direct attached storage, and its FC uplinks to the direct attached storage are up, these FC uplinks now allow traffic to pass. 2.2(3f)A 2.2(6g)A CSCuv97713 After upgrading Cisco UCS Manager, in rare cases, the IOM may core in the sysmgr process leading to IOM reboot. This is now resolved. 2.2(3j)A 2.2(6g)A CSCux68679 When a UCS B460 M4 server is configured with Fusion IO cards installed in same mezzanine slot of the master and slave blades, actions such as Cisco UCS Manager upgrade, cluster failover, fabric interconnect reboot no longer trigger server reboot.

2.2(3a)A 2.2(6g)A CSCux96432 Discovery no longer fails on UCS B420 M4 servers with a 2-CPU configuration and a Fusion IO card in adapter slot 3. 2.2(5b)B 2.2(6g)B CSCux76128 Firmware Auto Install upgrade validation fails as expected when upgrading to Cisco UCS Manager Release 2.2(6g) with deprecated hardware. Auto Install can now be initiated by using the force option either through the GUI or the CLI. 2.1(3j)A 2.2(6g)A. Table 23 Resolved Caveats in Release 2.2 (6e) Defect ID Description First Bundle Affected Resolved in Release CSCuw44524 The server reboot issues related to clear CMOS BIOS operation in Cisco UCS Manager Release 2.2(5a), 2.2(5b), 2.2(5c) or 2.2(6c) for E7 v2 processors on the C460 M4, B260 M4, and B460 M4 servers are resolved. 2.2(5a)B 2.2(6e)B CSCuw23829 When inserting a HDD into the final disk slot of a C240 M4 server with 8 supported slots for disks, Cisco UCS Manager no longer displays a disk in the 9th slot.

2.2(4b)A 2.2(6e)A CSCux10203 When you decommission a C-Series server after it was discovered in direct attached configuration, and the direct attached switch port was changed from Ethernet to FC mode, the following error message no longer appears: Warning: if_index 0x1a01a000[Ethx/x] does not exists in VLAN database#ERROR 2.2(3h)A 2.2(3j)A, 2.2(6e)A CSCuw84010 Integrated C-Series rack servers with Seagate drives no longer fail association when using the host firmware policy in a service profile. 2.2(3h)A 2.2(3j)A, 2.2(6e)A CSCuw59409 The DME crash issue that you may experience when you upgrade a directly connected C-Series rack server without decommissioning to 2.2(5c), and connect the server to FI port, is resolved. 2.2(3h)A 2.2(3j)A, 2.2(6e)A CSCuv55823 Faults no longer occur when incompatible combinations of CIMC firmware and UCS Manager firmware are installed at the same time. 2.2(1a)A 2.2(6e)A CSCuv32417 Cisco B200 M4 and B420 M4 blade servers that run on UEFI OS will not reboot unexpectedly.

Note BIOS POST not being set as complete, which causes the next shallow discovery to reboot the server, has been resolved. Shallow discovery can occur because of different events including Cisco UCS Manager cluster failover, CIMC reset, or chassis reacknowledgment. 2.2(4b)B 2.2(6e)B. Table 25 Resolved Caveats in Release 2.2 (6c) Defect ID Description First Bundle Affected Resolved in Release CSCuw03000 PXE boot fails with BSOD when RoCE is enabled. 2.2(5a)B 2.2(6c)B CSCut78943 When making changes to vNICs or vHBAs that will be provisioned on Cisco Virtual Interface Cards (VICs) 1340 and 1380 adapters, a warning on the placement order impact appears. 2.2(3c)A 2.2(6c)A CSCuu33864 When upgrading to UCS Manager 2.2(6c) or later, the FI boots successfully without the possibility of causing a file system corruption on the SSD if the FI is equipped with a Unigen SSD. 2.2(3b)A 2.2(6c)A, 3.1(1e), 3.1(2b) CSCum50468 After upgrading the UCS Manager to version 2.2(6c) or higher, false faults for Fabric VSAN Membership Down are cleared.

2.2(1b)A 2.2(6c)A CSCut37134 A Cisco UCS B200 M4 server running ESXi 5.5 no longer crashes when you boot locally. 2.2(3a)A 2.2(6c)A CSCur79257 During an FI bootup, the RACE condition no longer causes UCS Manager configure interface vethernet 0” to switch. 2.2(3a)A 2.2(6c)A CSCup95855 FSM tasks are no longer stuck in the throttled state in Cisco UCS Manager during Cisco UCS C240 M3 server upgrade. 2.2(1d)A 2.2(3j)A, 2.2(6c)A CSCuv51214 Messages log are no longer overfilled with BMC is suspecting that palo is in the boot block. Leaving I2C bus alone messages.

2.2(3g)B 2.2(6c)B CSCuo93591 For a fabric interconnect in end-host mode, the MAC address table aging time no longer gets stuck at 300 regardless of the configuration. The value got stuck at 300 regardless of the configuration. This was the issue which was resolved. This value can be changed through UCSM GUI or CLI. 2.2(1c)A 2.2(6c)A CSCuu68351 The updated BIOS in UCS M3 B-Series Servers is compatible when running the Snow Inventory client on Windows OS, and does not hang. 2.0(1m)B 2.2(6c)B CSCut88909 The KVM option, Virtual Media >Activate Virtual Devices is now available.

2.2(3b)A 2.2(6c)A CSCuu55899 When the VLAN port-count optimization is enabled, and an uplink Ethernet is in a port channel, traffic is now able to flow to the available members in the port channel when there is a link flap on one of its members. 2.2(3b)A 2.2(6c)A CSCuq63868 When creating a vNIC in a LAN connectivity policy, the show configuration command no longer generates a software error. 2.2(2a)A 2.2(6c)A CSCut35123 After high-availability failover, chassis-seeprom local IO failures are no longer triggered.

2.2(4b)A 2.2(6c)A. Table 26 Resolved Caveats in Release 2.2 (5d) Defect ID Description First Bundle Affected Resolved in Release CSCuw50417 After upgrading the BIOS of Cisco UCS B200 M3 servers to Release 2.2(5d), the OS no longer displays the following error message if the OS boot time is exceptionally slow: Initializing Power Management. Power: 2568: No supported CPU power management technology detected Intel Enhanced SpeedStep is supported but disabled in BIOS 2.2(4b)B 2.2(5d)B CSCuv20999 When Cisco UCS Manager is managed by Cisco UCS Central, and there is a global service profile associated with a blade server, global VLANs can now be successfully assigned to a particular uplink interface through Cisco UCS Manager (VLAN Uplink Manager >VLANs >VLAN Manager) without an error message being displayed.

2.2(4b)A 2.2(5d)A CSCuw13170 When auto-deploying the installation of ESX on Ivy Bridge-EX platforms, some platforms that enforce ACS violations strictly will no longer generate a non-maskable interrupt (NMI) and crash the host OS. 2.2(5c)B 2.2(5d)B. Table 27 Resolved Caveats in Release 2.2 (5c) Defect ID Description First Bundle Affected Resolved in Release CSCuu89283 You can create LUNs with certain non-default virtual drive policy attributes, such as read-policy, write-policy, and cache-policy, which are managed through storage profiles for rack servers with a UCSC-MRAID12G storage controller. You can modify such virtual drive policy attributes for these LUNs as well without causing service profile association to fail. 2.2(4b)A 2.2(5c)A CSCuv00089 After upgrading the Fabric Interconnect (FI) to Cisco UCS Manager Release 2.2(5c), systems that have OS-based NIC teaming configured as Active-Standby no longer experience network connectivity issues.

Note Network connectivity issues still occur on systems that have OS-based NIC teaming configured as Active-Standby when you upgrade the FI to Cisco UCS Manager Release 2.2(4). 2.2(4b)A 2.2(5c)A CSCuv49345 When a server is discovered from only one Fabric Interconnect (FI), and the DME primary instance is the other FI, disassociation of the associated service profile no longer fails. 2.2(1a)A 2.2(5c)A CSCuu60867 Cisco UCS C240 M3 servers with dual RAID controllers can now be discovered on SimpliVity solutions with OmniStack cards. 2.2(3f)A 2.2(5c)A CSCuv13545 If Cisco UCS Manager is registered with Cisco UCS Central, and the service profile refers to a global host firmware pack policy, UCSM no longer downloads images during shallow discovery. 2.2(4b)A 2.2(5c)A CSCuv28540 When you run Cisco UCS Manager Releases between 2.2(1) and 2.2(3) with catalog version 2.2(5b)T, the VIC PCI slot ID is now populated correctly.

Hence, SAN boot no longer fails on servers where the boot vHBAs are placed on a VIC. Note This issue still occurs when you run UCSM Releases between 2.2(1) and 2.2(3) with catalog versions 2.2(4b)T and 2.2(5a)T. 2.2(4b)T 2.2(5b)T CSCuu15250 Toggling the locator LED for a Fabric Interconnect in UCSM no longer fails. 2.2(1d)A 2.2(5c)A. Table 29 Resolved Caveats in Release 2.2 (5a) Defect ID Description First Bundle Affected Resolved in Release CSCus03683 The Cisco UCS 6200 series primary and subordinate FIs no longer reboot unexpectedly due to high volume traffic impacting the management interface.

2.2(1d)A 2.2(5a)A, 2.2(4b)A CSCut54652 During service profile association, firmware upgrade on third-party Converged Network Adapters (CNA) no longer fails with the following error: Unable to find VNIC Device 2.2(4b)A 2.2(5a)A CSCuu37369 Storage profiles can now be created within a sub-organization in Cisco UCS Manager. 2.2(4b)A 2.2(5a)A CSCuu42945 Service profiles created from service profile templates with local storage profiles no longer fail association with server pools. 2.2(4b)A 2.2(5a)A CSCuu52001 In Cisco UCS C240 M3 rack mount servers with external LSI RAID controllers, service profile association no longer fails.

2.2(4b)A 2.2(5a)A CSCuu53920 In Cisco UCS B260 M4 and B 460 M4 servers, LUN creation and service profile association no longer fails. 2.2(4b)A 2.2(5a)A CSCuu65128 Continuous reboots of Cisco UCS 6200 series Fabric Interconnect are no longer observed after configuring more than 64 vNICs (excluding dynamic vNICs) on a single server. 2.2(4b)A 2.2(5a)A. Table 31 Resolved Caveats in Release 2.2 (4b) Defect ID Description First Bundle Affected Resolved in Release CSCus03683 The Cisco UCS 6200 series primary and subordinate FIs no longer reboot unexpectedly due to high volume traffic impacting the management interface. 2.2(1d)A 2.2(4b)A, 2.2(5a)A CSCus81832 Using a Cisco UCS VIC 1340 or VIC 1380 adapter with a Sandy Bridge CPU in a Cisco UCS B420 or UCS B200 M3 server no longer causes the server to hang. Red Hat Enterprise Linux 6.5 or 7.0 now installs successfully.

2.2(3c)B 2.2(4b)B CSCus18092 IOMs that are connected to a Fabric Interconnect no longer reboot due to a software-controlled reset. 2.1(3e)A 2.2(4b)A CSCus10255 The number of licenses used by ports is now displayed correctly.

2.2(3a)A 2.2(4b)A, 2.2(6c)A CSCup88161 Cisco UCS 6248 Fabric Interconnect crashes with no cores are no longer observed when new blade servers are being added to the environment. 2.2 (1d)A 2.2(4b)A CSCus72177 After changing the IP address of the KVM pool and Fabric Interconnect from one subnet to another, KVM launches successfully.

2.2(3d)A 2.2(4b)A CSCus40519 Changing the Fibre Channel trunking mode when the Fibre Channel port-channel is active no longer impacts the Fabric Interconnect expansion module. 2.2(3c)A 2.2(4b)A CSCur39162 When you run the show platform fwm info hw-stm asic num command on a Fabric Interconnect, the FWM process no longer crashes and reboots the Fabric Interconnect. 2.0(1q)A 2.2(4b)A CSCup99955 In a scale Cisco UCS environment, the Call Home process no longer crashes and reboots the Fabric Interconnect due to a memory leak. 2.2(1b)A 2.2(4b)A CSCut04941 Cisco UCS clusters scheduled for an update from Cisco UCS Central will conform to the user acknowledgment setting. 2.2(1b)A 2.2(4b)A CSCur79565 On a Cisco UCS B-Series server running Cisco UCS Manager Release 2.2(3b) or later versions, Netflow data is now sent to the collector. 2.2(3b)A 2.2(4b)A CSCut03052 IP QoS core may happen in a VM-FEX scale set up, when you reboot Fabric Interconnects back to back.

2.2(1b)A 2.2(4b)A CSCva43666 Whenever the chassis IOM is reset, the FI server port no longer gets into Error disable state. 2.2(3a)A 2.2(4b)A. Table 32 Resolved Caveats in Release 2.2 (3l) Defect ID Description First Bundle Affected Resolved in Release CSCuu66595 It is now possible to perform multiple backups to the same host. 2.2(3f)A 2.2(3l)A CSCuu99255 The “show fabric-interconnect inventory expand” command no longer displays the ethernet port with a role of “Unknown” instead of “Server” on a fabric interconnect with a GEM card. 2.1(1a)A 2.2(3l)A CSCuw78008 Web sessions no longer remain on after the Web Session Timeout period specified in the authentication option under user management in the Admin tab. 2.1(3a)A 2.2(3l)A CSCuz55693 When you attempt to reset memory errors using ucs-fi chassis/server # reset-all-memory-errors Cisco UCS Manager no longer generates a 'Managed object does not exist' error.

2.2(1b)A 2.2(3l)A CSCuz86450 The server no longer reboots because the system does not accept user input on the order property of adaptorHostIf. 1.4(1j)A 2.2(3l)A CSCvb78971 When attempting the auto-install of UCS Manager, the fabric interconnect upgrade no longer fails when the /var/tmp usage exceeds 10%. 2.1(3k)A 2.2(3l)A CSCvb85544 A race condition in the Linux kernel's memory subsystem that handled the copy-on-write (COW) of read-only memory mappings no longer occurs on fabric interconnects.

This vulnerability is documented in Common Vulnerability and Exposures (CVE) CVE-2016-5195. 2.2(1a)A 2.2(3l)A. Table 33 Resolved Caveats in Release 2.2 (3k) Defect ID Description First Bundle Affected Resolved in Release CSCuv03557 During Cisco UCS Manager upgrade, FI activation no longer fails with the following error: Pre-Upgrade check failed.

Insufficient free space in /var/tmp. Less than required 90%. 2.1(3a)A 2.2(3k)A CSCuv46749 When using Cisco B200 M4 blade servers with the UCSB-MRAID12G storage controller, the following random, incorrect transient alerts or faults are no longer reported: • Critical Fault [F1004] Controller Inoperable, Reason: Device reported • Critical Fault [F1004] Controller Inoperable, Reason: Device non-responsive 2.2(3g)B 2.2(3k)B CSCuv53399 After IOM firmware upgrade, or after an IOM reset while running effected firmware, Cisco UCS Manager will no longer show Major fault F0481 indicating the IOM encountered a POST failure.

2.2(3a)A 2.2(3k)A CSCuv89839 When the fabric interconnect is in switch mode with direct attached storage, and its FC uplinks to the direct attached storage are up, these FC uplinks now allow traffic to pass. 2.2(3f)A 2.2(3k)A CSCuv97713 After upgrading Cisco UCS Manager, in rare cases, the IOM may core in the sysmgr process leading to IOM reboot. This is now resolved. 2.2(3j)A 2.2(3k)A CSCuj71400 Cisco UCS Manager no longer displays the ’FCoE or FC uplink is down on VSAN X' fault when the member ports for the VSAN are up. 2.2(1a)A 2.2(3k)A CSCuo93591 For a fabric interconnect in end-host mode, the MAC address table aging time no longer gets stuck at 300 regardless of the configuration.

The value got stuck at 300 regardless of the configuration. This issue in now resolved. This value can be changed through UCSM GUI or CLI. 2.2(1c)A 2.2(3k)A CSCus34689 When using Cisco UCS Manager with C-Series integration, Cisco UCSM GUI no longer displays the following message on hovering between the C-Series servers and FIs: 2.2(1b)A 2.2(3k)A CSCuw36128 The buffer overflow condition that caused the statsAG mts queue to leak is now fixed. 2.2(1d)A 2.2(3k)A CSCuw44595 DIMMs with correctable ECC errors are marked Inoperable or Degraded even though correctable errors do not affect normal system operation. This issue is now resolved. 2.2(3a)A 2.2(3k)A CSCur39162 When you run the show platform fwm info hw-stm asic num command on a Fabric Interconnect, the FWM process no longer crashes and reboots the Fabric Interconnect.

2.0(1q)A 2.2(3k)A CSCus59926 You can see the following issues with Call Home messages, although Smart Call Home registers successfully: • Call Home messages are not generated. • Test inventory is not sent. This issue is now resolved. 2.2(3a)A 2.2(3k)A CSCus76125 Global service profile now resolves the LAN ping group even when the ping group is created in Cisco UCS Manager. 2.2(3d)A 2.2(3k)A CSCuv20324 The FCoE storage no longer becomes unavailable or performs very poorly after a reset of either host-attached switch in the case of standalone systems, or after the reset of an IOM or FI in UCS-managed systems when the IOM or FI sends configuration information to the adapter later than 5 seconds after link-up. 2.2(1b)B 2.2(3k)A CSCux68679 When a UCS B460 M4 server is configured with Fusion IO cards installed in same mezzanine slot of the master and slave blades, actions such as Cisco UCS Manager upgrade, cluster failover, fabric interconnect reboot no longer trigger server reboot.

2.2(3a)A 2.2(3k)A CSCuq57142 In a port channel universe, the following no longer happen: • A port channel ID may sometimes not be released after use. This could eventually lead to the universe of port channel IDs being empty, and no port channel IDs being available for use. • After an upgrade, power loss, FI reboot or failover, the empty port channel universe is incorrectly interpreted as a new installation, and repopulated.

This leads to duplicate port channel ID allocation when a server is attached to the FI, or when a server is re-acknowledged. 2.2(3a)A 2.2(3k)A CSCux45723 UCS SNMP memory leaks no longer occur when polling FC interfaces and SNMP processes (Walk/Get/Get Bulk) that parse any of the following SNMP MIBs: • fcIfNonLipF8Out • fcIfTimeOutDiscards • fcIfOutDiscards • fcIfCreditLoss • fcIfTxWtAvgBBCreditTransitionToZero 2.2(3a)A 2.2(3k)A CSCux59298 When using UCS B200 M3 servers with VIC 1240 on a system running Cisco UCSM Release 2.2(2c), network and SAN no longer lose connectivity. 2.2(2c)B 2.2(3k)A CSCuy64856 The Cisco UCS fabric interconnects (FI) are no longer rebooted with the reboot reason FWM hap reset.

2.1(3h)A 2.2(3k)A CSCuu40291 When debug logging is enabled, Cisco UCS Manager tech-support showed that syslogd_debug files were present, but the show debug logfile syslogd_debugs CLI command failed with the following error: Logfile(syslogd_debugs) does not exist This issue is now resolved. 2.2(3a)A 2.2(3k)A CSCuu40978 The syslog is now truncated after it reaches the configured maximum size. It no longer fills up the Fabric Interconnect file system. 2.2(3d)A 2.2(3k)A CSCuw02439 When using Cisco UCS M81KR VIC adapters on a system running Cisco UCS Manager Release 2.2(2c), the adapters no longer crash and generate core files.

2.2(2c)B 2.2(3k)A CSCuw44595 DIMMs with correctable ECC errors are marked Inoperable or Degraded even though correctable errors do not affect normal system operation. This issue is now resolved. 2.2(3a)A 2.2(3k)A CSCux58865 DIMM temperature readings are no longer missed when the temperature is 10 degrees Centigrade more than the previous reading. 2.1(3d)B 2.2(3k)A CSCuz20650 When syslog messages are generated continuously, the syslog suspend timer does not recover. Thus, no events are sent to the remote syslog server.

This issue is now resolved. 2.2(3a)A 2.2(3k)A CSCuy34161 Any DIMM that is functioning correctly is no longer disabled after the reboot of the UCS B250 M2 blade server. 2.0(5c)B 2.2(3k)A. Table 34 Resolved Caveats in Release 2.2 (3j) Defect ID Description First Bundle Affected Resolved in Release CSCus55944 While updating a service profile template, the service profile no longer reboots without a warning when you create and add a VLAN to a rack server that is associated with an inherited service profile. 2.2(3a)A 2.2(3j)A CSCuw78688 The failure to load configuration that caused system outage when upgrading Cisco UCS Manager to 2.2(5c) is resolved. 2.2(3a)A 2.2(3j)A CSCus11782 After rebooting a Cisco UCS 6248UP Fabric Interconnect (FI) that is operating in the FC end-host mode, all member links of the SAN port channel come up.

2.2(1d)A 2.2(3j)A, 2.2(5b)A CSCus85186 After activating Cisco Trusted Platform Module (TPM), the enable and active statuses now remain as disabled and deactivated. 2.2(1d)B 2.2(1h)B,2.2(3j)B CSCuv06504 The svc_sam_dme process is no longer crashing during a steady state of operation when a database (db) corruption is detected primarily on the subordinate fabric interconnect. 2.2(3d)A 2.2(3j)A, 2.2(6c)A CSCuv72975 When upgrading the Cisco UCS Manager infrastructure bundle and using VIC-1340 or VIC-1380, the backplane port of the IOM and VIC is no longer down.

2.2(3a)B 2.2(3j)B CSCuw59409 The DME crash issue that you may experience when you upgrade a directly connected C-Series rack server without decommissioning, and connect the server to FI port, is resolved. 2.2(3h)A 2.2(3j)A, 2.2(6e)A CSCuw84010 Integrated C-Series rack servers with Seagate drives no longer fail association when using the host firmware policy in a service profile. 2.2(3h)A 2.2(3j)A, 2.2(6e)A CSCux10203 When you decommission a C-Series server after it was discovered in direct attached configuration, and the direct attached switch port was changed from Ethernet to FC mode, the following error message no longer appears: Warning: if_index 0x1a01a000[Ethx/x] does not exists in VLAN database#ERROR 2.2(3h)A 2.2(3j)A, 2.2(6e)A CSCup95855 FSM tasks are no longer stuck in the throttled state in Cisco UCS Manager during Cisco UCS C240 M3 server upgrade.

2.2(1d)A 2.2(3j)A, 2.2(6c)A CSCur01185 The HA policy of Reset is no longer triggering the Cisco UCS 6296UP fabric interconnect to reset. 2.2(1d)A 2.2(3j)A CSCus32933 Cisco UCS Manager now displays an error message when a WILL_BOOT_FAULT event is raised because of an incorrect CPLD version. 2.2(2c)B 2.2(3j)B CSCus56140 Cisco UCS Manager now performs a successful failover if the primary out-of-band management port is detected as down for more than the Management Interface Monitoring default 5 minutes. 1.4(2b)A 2.2(3j)A CSCus73964 When you download an infrastructure software bundle onto a system where the same infrastructure software bundle was previously installed, but was subsequently deleted, the UCS Manager FIs, and IOMs no longer downgrade to that software bundle. 2.1(3e)A 2.2(3j)A CSCus93431 Adding other storage, such as a local disk or a USB to a SAN boot policy no longer deletes the SAN boot policy from Cisco UCS Manager.

2.2(3c)A 2.2(3j)A, 2.2(6c)A CSCut10525 The FlexFlash firmware version is now updating and the FFCH_ERROR_OLD_FIRMWARE_RUNNING is not longer displaying in the fault summary after you update the UCS B200 M4 server firmware using 2.2(4b). 2.2(3a)B 2.2(3j)B CSCut28278 After upgrading the infrastructure and the Cisco UCS Manager image, the subordinate fabric interconnect no longer fails the pre-upgrade check because of insufficient free space in the /var/sysmgr directory. 2.2(1d)A 2.2(3j)A CSCuv31912 UCS Manager iptables are no longer duplicating rules in the FORWARD table. 2.2(3d)A 2.2(3j)A, 2.2(6c)A, 2.2(8a)A CSCux71937 The CPU utilization always displayed 100 percent for the kernel in the output of the show system resources command.

This could happen if the system had been up for a very long time (more than 200 days, but this time-frame could vary): FI(nx-os)# show system resources Load average: 1 minute: 0.50 5 minutes: 0.71 15 minutes: 1.04 Processes: 563 total, 3 running CPU states: 0.0% user, 100.0% kernel, 0.0% idle Memory usage: 3490164K total, 3140304K used, 349860K free This has now been resolved. The output of this command now indicates the correct CPU utilization levels. 2.2(3b)A 2.2(3j)A, 2.2(6f)A.

Table 35 Resolved Caveats in Release 2.2 (3h) Defect ID Description First Bundle Affected Resolved in Release CSCus64439 Cisco UCS Manager Mezz logs and VMware vmkernel logs no longer indicate storage latency and numerous FNIC aborts. 2.2(1d)B 2.2(3h)B CSCuu15465 If the version of board controller on a UCS B200 M4 server is higher than the version in the Host Firmware Pack, Cisco UCS Manager no longer tries to downgrade firmware of board controllers on the servers. While running Cisco UCS Manager Releases 2.2(3b) to 2.2(3g), you can use catalog version 2.2(4b)T or later versions to get this fix. 2.2(3b)A 2.2(3h)A. Table 36 Resolved Caveats in Release 2.2 (3g) Defect ID Description First Bundle Affected Resolved in Release CSCus74206 After disconnecting and re-connecting a cable between the FI and IOM, the VFC interfaces on the chassis will not flap and cause any disruption in the FC traffic. 2.2(1d)A 2.2(3g)A CSCur66094 Servers will not be stuck in discovery state.

The locked CIMC connection issue causing bladeAG network thread lock up is resolved. 2.2(2c)A 2.2(3g)A CSCur96296 FEX will not be online and offline in quick succession under scaled setups. 2.2(3a)A 2.2(3g)A CSCus91342 You will not be prompted to reboot the blade server when adding a vLAN to a vNIC template. 2.2(1b)A 2.2(3g)A CSCut28626 When you import a backup file with multiple vLANs, the B200 M2 server association will not be stuck at 86%. 2.2(3e)A 2.2(3g)A CSCut FI will not reboot with kernel panic. 2.2(3c)A 2.2(3g)A CSCut54264 Server connectivity issue relative to non-reuse of connection slots is resolved.

Note The logs will show MCSERVER_LIMIT_REACHEDIN whereas netstat will show that there are only a few connections. 2.2(1c)B 2.2(3g)B CSCur19358 The firmware update on K2 NVIDIA adapter will not fail with the error message “FI unreachable”. 2.2(2e) 2.2(3g)A CSCut13146 Chassis Discovery and service profile association no longer fail during downgrade to a UCSM version 2.2(2x) or earlier, when isolated Vlans are allowed on appliance ports or vNIC service profiles. 2.2(1g)A 2.2(3g)A CSCut61527 and CSCus42584 The Cisco B200M4 blade server will not reboot unexpectedly. Note Storage Controller FRU information mismatch that causes the next shallow discovery to be converted to a deep discovery has been resolved. Shallow discovery can occur through different activities such as replacing IOM cables.

2.2(3a) and 2.2(1b)A 2.2(3g)A CSCus89837 The excessive logging of the error “error:Invalid argument” in chassis pwrmgr tech support log will not happen anymore. 2.1(3b)A 2.2(3g)A CSCut45721 FI running BladeAG will no longer need rebooting due to low kernel memory 2.1(1a)A 2.2(3g)A CSCus97608 Faults in Cisco UCS Manager such as “error accessing shared-storage” and timeout/failover warning within the “show cluster extended-state” are no longer displayed when several devices in several chassis are reporting EBUSY within the I2C logs. 2.2(3b)B 2.2(3g)A CSCut02769 dbsync between Cisco UCS Fabric Interconnects will share only the required files and will not fail when copying the files from peer FI /opt/db/flash. 2.2(3b)A 2.2(3g)A CSCur21496 After a successful firmware update, the NVIDIA GPU cards no longer display the incorrect version number. 2.2(2e)A 2.2(3g)A CSCur83866 All overlapping IP addresses are appropriately removed during deletion and deployed at creation. 2.2(1b)A 2.2(3g)A CSCut69252 Service profile disassociation no longer fails with the flexflash scrub policy with no SD cards on C220 M4 servers. 2.2(3c)A 2.2(3g)A.

Table 37 Resolved Caveats in Release 2.2 (3f) Defect ID Description First Bundle Affected Resolved in Release CSCus61659 After an IOM is reset, priority flow control on the IOM interface to a blade no longer becomes disabled. 2.1(3c)A 2.2(3f)A CSCuq95926 Fabric Interconnect failover status is no longer stuck in Switchover In Progress when the management cable is unplugged. 2.2(2c)A 2.2(3f)A CSCut11027 When using a maintenance policy with user acknowledgment, a server with a third-party adapter will not reboot without asking for user acknowledgment after a SAN boot change in the boot policy.

2.2(3c)A 2.2(3f)A CSCuq51890 Entity physical description returns correct getnext values during SNMPwalk on Entity MIB. 2.2(2c)A 2.2(3f)A. Table 38 Resolved Caveats in Release 2.2 (3e) Defect ID Description First Bundle Affected Resolved in Release CSCus69458 The heap-based buffer overflow vulnerability in the GNU C library, documented in Common Vulnerability and Exposures (CVE) CVE-2015-0235 is addressed. 1.0(1e) 2.2(3e)A CSCur70034 Service Profiles with a common VLAN name configured on one of the vNICs no longer fail with the following error: “Incorrect VLAN configuration on one of the VNICs.

2.2(3c)A 2.2(3e)A CSCuh78503 iSCSI reboot loop no longer fails with Oprom initialize error 1. 2.1(2a)B 2.2(3e)B CSCur83235 KVM login no longer fails in UCS Manager Release 2.2(3e) over Cisco AnyConnect VPN.

2.2(2c)A 2.2(3e)A CSCus55072 When C460-M4 servers are unassociated, firmware upgrade FSM no longer restarts after the BIOS POST FSM stage. 2.2(3a)A 2.2(3e)A CSCus51733 Toshiba HDD firmware version 5706 is now packaged in UCS Manager. Downgrades to version 5705 can change the status of the Toshiba HDD to Unconfigured Bad and should be avoided. 2.2(3a)B 2.2(3e)B CSCur99740 Fabric Interconnect image upgrade no longer fails when you run the reload all command from the Fabric Interconnect. 2.2(3d)A 2.2(3e)A.

Table 39 Resolved Caveats in Release 2.2 (3d) Defect ID Description First Bundle Affected Resolved in Release CSCur32075 The following new microcode for the Haswell-EP processor was added to release 2.2(3d): • M6F306F2_0000002B 2.2(3a)B 2.2(3d)B CSCur42086 Blade AG no longer cores constantly and prevents assigning a service profile. 2.2(1d)A 2.2(3d)A CSCur77716 Call Home Config FSM error no longer occurs when upgrading from 2.2(1f). 2.2(3c)A 2.2(3d)A CSCuq17289 ‘Failed to allocate exchange’ messages are no longer observed when vNICS with different COS values are used. 2.2(3c)A 2.2(3d)A CSCuq74472 Unnecessary thermal events on IOM stating that the thermal sensor reading is not available no longer occur. 2.1(3c)A 2.2(3d)A CSCur05013 Messages.log file on a Cisco UCS B200 M2 blade no longer fills with messages including ‘364:BMC lost control of the bus.[0xd 0x0]’. 2.2(2c)B 2.2(3d)B CSCur29264 The security vulnerability identified by Common Vulnerability and Exposures (CVE) CVE-2014-3566 is addressed. 2.2(3a)A 2.2(3d)A CSCur38408 Fabric interconnect HA failover no longer causes the attached Cisco UCS C460 M4 servers to reboot when a PCIe card is present in slot 2 and riser 2 is missing.

2.2(2c)A 2.2(3d)A CSCur48661 Global service profile association no longer fails with a ‘failed to copy images’ error. 2.2(3b)A 2.2(3d)A CSCun23603 UCS Manager now properly upgrades the power sequencer software. 2.2(3c)A 2.2(3d)A CSCur37260 FI upgrade or downgrade no longer fails due to lack of disk space in /mnt/pss. 2.1(3b)A 2.2(3d)A CSCuq52499 Cisco UCS Manager no longer raises a unnecessary fault on the IOM when the CPU on a blade in the chassis crosses the UNC/UC threshold. 2.1(3b)A 2.2(3d)A. Table 40 Resolved Caveats in Release 2.2 (3c) Defect ID Description First Bundle Affected Resolved in Release CSCuq35685 IGMPv2 traffic no longer causes MAC flapping on upstream switches when the FI has multiple uplinks connecting to different switches. 2.2(1b)A 2.2(3c)A CSCuq46105 UCS Manager now uses power sequencer version 3.0 to address the rare issue of an unexpected reboot to the Cisco UCS 6248 FI.

2.2(1c)A 2.2(3c)A CSCuq63086 Cisco B200 M3 no longer fails with a ‘Controller 1 on server x/y is inoperable’ error. 2.2(1e)B 2.2(3c)B CSCur08722 Firmware upgrade FSM no longer fails on the Cisco UCS C240 M3 server with the following error: IVY Bridge Processor is installed on this server, cannot downgrade to unsupported CIMC version. 2.2(3a)A 2.2(3c)A CSCup45930 When upgrading the Cisco UCS B230 M2 server from Cisco UCS Manager Release 2.2(1x) to Cisco UCS Manager Release 2.2(2x) or from Cisco UCS Manager Release 2.2(2x) to Cisco UCS Manager Release 2.2(3x), or when upgrading the Cisco UCS C460 M4 server from Cisco UCS Manager Release 2.2(2x) to Cisco UCS Manager Release 2.2(3x), association no longer fails. 2.2(1e)A 2.2(3c)A. Table 42 Resolved Caveats in Release 2.2 (3a) Defect ID Description First Bundle Affected Resolved in Release CSCuo60330 IOMs are no longer unreachable after upgrading the FI when upgrading to Cisco UCS Manager, Release 2.2(2) or later. 2.2(1d)A 2.2(3a)A CSCue93518 Cisco UCS Manager now displays an alert when users are close to reaching the VLAN port count limit. 2.1(1a)A 2.2(3a)A CSCug73260 The UCS Manager DME process no longer crashes on the subordinate FI during an upgrade or power outage.

2.1(1a)A 2.2(3a)A CSCui12868 Some conditions that result in the chassis displaying a thermal sensor reading error due to third-party applications accessing the PCH SMBus or CPU SMBus controller have been fixed. Note An additional enhancement addressing this same symptom will be included in the upcoming 2.2(3b) patch. 2.0(4b)B 2.2(3a)B CSCui53234 Call Home alerts now include alert customization and service profile information.

2.0(3a)A 2.2(3a)A CSCul69513 Interface (error) counters for the fabric ports on the IOM can now be monitored using the UCS Manager GUI and CLI. 2.1(1a)A 2.2(3a)A CSCum48026 Local vMedia mounts in progress can now be cancelled by the user instead of waiting for a timeout.

2.2(2c)B 2.2(3a)B CSCun00368 A fault is now raised if the FI has less memory than expected. 2.1(3b)A 2.2(3a)A CSCun00720 The UCS 6296 FI no longer fails to boot after a software upgrade, reload, or power cycle. 2.0(2m)A 2.2(3a)A CSCun66874 DIMM blacklisting no longer prevents the host from accessing the DIMM bus. 2.2(2c)A 2.2(3a)A CSCun84951 MCA and MCE errors are now logged when a Cisco UCS blade server reboots due to a CPU CATERR fault. 2.2(1b)B 2.2(3a)B CSCuo09991 The primary FI and secondary FI in a HA cluster no longer fail to sync after rebooting. 2.2(1b)A 2.2(3a)A CSCuo34760 vEthernet interfaces and VIFs no longer remain in down state if the primary FI in a HA cluster is rebooted and comes up as the secondary FI. 2.1(2d)A 2.2(3a)A CSCuo48978 Cisco UCS Manager now prevents downgrading the BIOS to an unsupported version on Cisco UCS C22, C24, C220, and C240 M3 servers with E5-2600 or E5-2400 v2 series CPUs.

2.1(2a)C 2.2(3a)C CSCuo51708 Cisco UCS Manager downgrade no longer fails during autoinstall. 2.2(1d)A 2.2(3a)A CSCuo76425 Ingress CRC errors are no longer seen over TwinA.x cables with rapid link-flaps on the 6248 and 6296 platforms 2.2(1c)A 2.2(3a)A CSCuo80898 When upgrading an environment from Release 2.1(1a) to newer releases, the SAN port-channels that have member ports with different max speed will not be configured and a fault is raised to indicate this.

2.1(2a)A 2.2(3a)A CSCup05019 Status of FlexFlash controller no longer shows as ‘Disconnected Partition From Host” and SD cards are now visible in the local disks option after inserting those cards into a blade with Flexflash enabled in local storage policy. 2.2(1d)A 2.2(3a)A CSCup47504 Cisco UCS VIC 1240 adapter no longer fails to complete the PXE boot process due to missing DHCP offer on a Cisco UCS 6200 FI using an ASA as the DHCP relay. 2.2(1d)B 2.2(3a)B CSCup61601 FI no longer crashes upon executing the show platform software fcoe_mgr info global command when there are too many noncontiguous VLANs configured. 2.2(1d)A 2.2(3a)A CSCup61947 MAC learning no longer fails after adding 1,000 or more VLANs with a large PV count with 120 or more virtual interfaces each with 1,000 VLANs. 2.2(1d)A 2.2(3a)A CSCup82677 Line rate is no longer limited to 10GB even when QoS line rate is set to 20GB or 40GB. 2.1(3b)A 2.2(3a)A CSCup88087 Cisco UCS B200 M3 server with a single CPU no longer reports faults for a second CPU not present in the hardware. 2.1(3a)A 2.2(3a)A CSCuo87059 After a chassis decommission and recommission, backplane ports on an IOM are no longer missing due to a NULL serial number being sent to the Cisco UCS Manager.

2.2(2c)B 2.2(3a)B. Table 43 Resolved Caveats in Release 2.2 (2e) Defect ID Description First Bundle Affected Resolved in Release CSCur01379 The security vulnerabilities identified by Common Vulnerability and Exposures (CVE) CVE-2014-7169, CVE-2014-6271, CVE-2014-6277, CVE-2014-7186, CVE-2014-7187, and CVE-2014-6278 are addressed. 2.0(1q)A 2.2(2e)A CSCur16493 The UCSC-GPU-VGXK2 GPU adapter firmware has been updated to version 80.04.F5.0552.01.08. 2.2(2a)B 2.2(2e)B CSCup45930 When upgrading the Cisco UCS B230 M2 server from Cisco UCS Manager Release 2.2(1x) to Cisco UCS Manager Release 2.2(2x) or from Cisco UCS Manager Release 2.2(2x) to Cisco UCS Manager Release 2.2(3x), or when upgrading the Cisco UCS C460 M4 server from Cisco UCS Manager Release 2.2(2x) to Cisco UCS Manager Release 2.2(3x), association no longer fails.

2.2(1e)A 2.2(2e)A. Table 44 Resolved Caveats in Release 2.2 (2d) Defect ID Description First Bundle Affected Resolved in Release CSCui12868 Some conditions that result in the chassis displaying a thermal sensor reading error due to third-party applications accessing the PCH SMBus or CPU SMBus controller have been fixed. 2.0(4b)B 2.2(2d)B CSCun25692 M71KR-Q no longer runs out of heap and causes SAN boot failure while allocating memory to critical data structure. 2.2(1b)B 2.2(2d)B CSCun79973 vNIC no longer hangs when QoS policy on a vNIC is changed while a Netflow session with transmit monitoring is active on that vNIC. 2.2(2c)A 2.2(2d)A CSCuo34760 Veths/VIFs no longer remain in down state on a Primary FI that gets rebooted and comes back up as subordinate FI.

2.1(2d)A 2.2(2d)A CSCuo79500 A vNIC with a usNIC connection policy no longer falsely shows as a Dynamic vNIC after a second vNIC with a usNIC policy is added. 2.2(1c)A 2.2(2d)A CSCuo98011 Service dcosag no longer crashes during Infra firmware upgrade (ucs-k9-bundle-infra.2.2.2c.A.bin) if upgrade is initiated from Cisco UCS Central, when Cisco UCS Manager is registered to Cisco UCS Central using IPv4 address and image bundles are not present in Cisco UCS Manager. 2.2(2c)A 2.2(2d)A CSCup07488 ECC sensors no longer read or report invalid “Upper Non-Recoverable” data when there are existing failed PECI transactions on a blade. 2.2(2c)B 2.2(2d)B CSCup61601 FCOE_MGR no longer crashes when FI is configured with too many noncontiguous VLANs. 2.2(1d)A 2.2(2d)A CSCup61947 MAC learning no longer fails after adding 1000 or more VLANs with a large PV count with 120 or more virtual interfaces each with 1000 VLANs. 2.2(1d)A 2.2(2d)A CSCup82677 A Cisco UCS system with ESXi OS is no longer limited to 10Gb speed when QoS is configured with line-rate of 20Gb or 40Gb. 2.2(1d)A 2.2(2d)A.

Table 45 Resolved Caveats in Release 2.2 (2c) Defect ID Description First Bundle Affected Resolved in Release CSCtf73879 Cisco UCS Manager (GUI or CLI) no longer fails to report the local disk failures, faults, alarms, status, or disk errors/error codes from MegaRAID controller. 1.4(1) 2.2(2c) CSCuh89441 RHEL6.3 SAN boot on M73KR-E no longer fails. 2.2(1b) 2.2(2c) CSCuh92027 The cluster no longer gets stuck in switchover in progress mode when unplugging the primary FI's management port.

2.1(1a)A 2.2(2c)A CSCuh99542 New SNMP user configured via Cisco UCS Manager now shows up in UCS NX-OS CLI. 2.1(1e)A 2.2(2c)A CSCuj74570 B420 M3 with UCSB-MLOM-PT-01 installed no longer reboots for discovery when first IOM is upgraded to 2204XP. 2.1(2a)B 2.2(2c)B CSCuj81245 OS kernel and adapter logs no longer report multiple FNIC aborts when user starts a heavy write operation to SAN disk. 2.2(1b)B 2.2(2c)B CSCuj81385 GUI no longer returns PSUs have failed, please check input fault. 2.1(3a)B 2.2(2c)B CSCuj84543 IOM no longer incorrectly reports that grid redundancy is lost while all PSUs are in Active PS state. 2.1(3a)A 2.2(2c)A CSCul03508 Kernel memory no longer runs out and causes FI to reboot when running CA AIM tool with Cisco UCS Manager. 2.1(1d)A 2.2(2c)A CSCul15865 Remote user logged in as admin with valid locales is now able to create, modify, and delete in other organizations apart from the locales downloaded so long as locales restriction is not applied to the admin profile.

2.2(1b)A 2.2(2c)A CSCul44421 Error no longer encountered when accessing shared-storage during FI reboot, upgrade, or IOM reset. 2.1(2d)A 2.2(2c)A CSCul74278 The server no longer fails to boot from the local disk in cases where the boot policy was initially configured only for SAN devices and is later modified to add local disk or local HDD device. 2.2(1b)A 2.2(2c)A CSCul87625 FI no longer reports PSU failure when there is no real outage.

2.1(3a)A 2.2(2c)A CSCul95341 Server no longer becomes unreachable after vNIC failover/failback. 2.2(1b)A 2.2(2c)A CSCum10869 IO throttle count option on the FC adapter policy is now 256 by default and range changed to ‘256 to 1024’ to remove confusion caused by default value of 16, which was interpreted by driver to mean 2048. 2.1(1f)A 2.2(2c)A CSCum18805 Error message no longer received when pinging from peer FI's local-mgmt.

2.2(1b) 2.2(2c)A CSCum19106 HDDs are displayed appropriately now in both Cisco UCS Manager and in BIOS for B200 M3. 2.2(1b)B 2.2(2c)B CSCum19132 httpd_cimc.sh crash no longer seen when changing switch mode from End-Host to Switch mode and vice versa. 2.2(1b)A 2.2(2c)A CSCum20965 Service profile now correctly disassociates from the blade when selecting “Disassociate Service Profile” from Cisco UCS Manager GUI.

2.2(1b) 2.2(2c)A CSCum51302 User no longer receives 'switchport trunk allowed vlan none' configuration error on vEthernet configuration for VLAN change. 2.2(1b)A 2.2(2c)A CSCum57954 Ping requests no longer timeout when configuring a B200 M3 with Cisco UCS VIC 1240 and Cisco UCS VIC 1280 with VM-FEX on the ESXi DVS while vMotioning a VM between two blades. 2.2(1b) 2.2(2c)A CSCum60793 Cisco UCS Manager no longer reports ‘mount suspend success’ to operations manager errors when UCS becomes unreachable or unregistered with Cisco UCS Central. 2.1(2c) 2.2(2c)A CSCum63448 A Cisco UCS compute blade no longer requests a reboot for minor changes when a component firmware in an Activating state after an upgrade is completed. 2.1(2c)A 2.2(2c)A CSCum82385 Allowed VLANs in vNIC now matches the allowed VLANs in vEthernet in NX-OS and vNICs no longer get updated when the service-profile is renamed.

2.1(3a)A 2.2(2c)A CSCum84239 No longer have to be logged in as admin to be able to connect adapter. 2.2(1b)A 2.2(2c)A CSCum84618 Installation of Win2008R2 no longer fails to reload after loading the disk.sys driver, preventing final installation steps to be completed. 2.1(3a)B 2.2(2c)B CSCum87525 The httpd.sh process on the subordinate FI no longer crashes after upgrading to 2.2(2c) from 2.1(3a) via auto install.

2.2(1b)A 2.2(2c)A CSCum95778 Incorrect sorting results are no longer displayed when attempting to sort a listing of service profiles and ORGs. 2.2(1b)A 2.2(2c)A CSCum98771 User no longer receives config failure message ‘Flexflash controller error, probably not supported, not equipped or inoperable’ when Cisco UCS Manager is updated from 2.1(2a) or above to 2.2(1) with FlexFlash State enabled. 2.2(1b)A 2.2(2c)A CSCun13327 A Cisco UCS system with a high number of blade or rack-servers no longer experiences a high number of messages collected in the bladeAG logs, causing logs to overflow and prevent user from collecting necessary data for troubleshooting purposes.

2.1(3a)A 2.2(2c)A CSCun14140 UCSB-B200-M3 Kernel no longer panics or hangs. 2.1(3b)B 2.2(2c)B CSCun19372 User is no longer prevented from adding interface from both fabrics to the VLAN when launching the LAN Uplink Manager from the Equipment >Interconnects >Fabric Interconnect A (or B) path. 2.2(1b)A 2.2(2c)A CSCun24381 Customers using the Cisco UCS PowerTool will no longer experience problems when scraping the Java log file for XML parsing of config changes when running Java version 7 update 45. 2.2(1b)A 2.2(2c)A CSCun25187 Cisco UCS Manager no longer becomes Lost-Visibility in Cisco UCS Central when keyring with certificate chain is configured for https communication if third-party certificates are signed by subordinate CA instead of root CA. 2.1(2a)A 2.2(2c)A CSCun42280 Messages log no longer overfilled with BMC is suspecting that palo is in boot block.

Leaving I2C bus alone. 2.1(2a)B 2.2(2c)B CSCun43320 Linux PXE server no longer fails to boot from gPXE server. 2.1(2a)B 2.2(2c)A CSCun46196 A Cisco UCS running 2.2(2c) that has a M1 or M2 blade no longer reports a minor fault related to Inband configuration when there is actually no Inband configuration intended for that blade. 2.2(1b) 2.2(2c)A CSCun94906 The Cisco UCS Manager DME no longer crashes when a SP is referring to a SP template and Cisco UCS Manager is connected to Cisco UCS Central during policy ownership conflict checks. 2.2(1b)B 2.2(2c)B CSCun95096 During association, the service profile no longer fails with an error stating that the RAID configuration is invalid due to an attempt to mix different drive technologies simply because one drive has an incorrect capability catalog technology field (set to HDD when it should be set to SSD). 2.2(1b)T 2.2(2c)T CSCuo06886 Cisco UCS Manager no longer populates the Created at field with a strange number in the wrong format instead of the date when exporting events in CSV format. 2.2(1b)A 2.2(2c)A CSCuo09527 A blade running on a 2-socket B420 M3 no longer boots to the BIOS screen after an update if the boot order is configured in the Cisco UCS Manager and the BIOS is set to strict mode.

2.2(1b)A 2.2(2c)A CSCuo12965 KVM console no longer fails to launch when user tries to launch from the Equipment tab in Cisco UCS Manager or from the KVM Launch Manager due to erroneous ‘No management IP address set’ error message when server has no management IP addresses assigned but the associated service profile does. 2.2(1b)A 2.2(2c)A CSCuo23630 User no longer receives “There are uncommitted changes” prompt after applying a port license to FI and, then, trying to move to another screen. 2.2(1c)A 2.2(2c)A CSCuo30572 Intel v2 processors no longer cause PSOD with Microsoft Windows 2008 R2 VM guests. 2.1(3a)A 2.2(2c)A CSCuo36008 User no longer receives the ‘peer connectivity: disconnected’ warning after re-seating the IOM(A). 2.2(1c)A 2.2(2c)A CSCuo78883 Cisco UCS Manager and KVM users or admins using JRE version 1.7 update >= 40 no longer encounter a pop-up window with the 'Application Blocked by Security Settings' dialog.

2.0(1m)A 2.2(2c)A. Table 46 Resolved Caveats in Release 2.2 (1h) Defect ID Description First Bundle Affected Resolved in Release CSCut63966 Switch will not stop at loader prompt upon reboot due to incorrect boot variables or /opt corruption. 2.2(1b)A 2.2(1h)A, 2.2(3g)A CSCur88952 svc_sam_dme core is no longer found after upgrading from or downgrading to Cisco UCS Manager Release 2.1(1b). 2.1(3g)A 2.2(1h)A, 2.2(3f)A CSCus83447 Cisco UCS Fabric Interconnect reload or switchover due to a leap second update no longer occurs. 2.2(1b)A 2.2(1h)A,2.2(3e)A CSCus85186 After activating Cisco Trusted Platform Module (TPM), the enable and active statuses will not remain as disabled and deactivated. 2.2(1d)B 2.2(1h)B, 2.2(3j)B, 2.2(4b)B CSCut03086 In a VM-FEX scale set up with over 100 servers, when you use auto install infrastructure firmware bundle and UCS Manager FI upgrades, DME core will not happen.

2.2(2c)A 2.2(1h)A, 2.2(3g)A CSCur54705 Cisco UCS Manager will no longer send UCS Manager username and password hashes to the configured SYSLOG server every 12 hours. 2.1(1a)A 2.2(1h)A,2.2(3e)A CSCut09151, CSCut21914 and CSCut08605 Traffic from the host and CIMC will no longer collide on the shared System Management BUS(SMBUS). As a result, certain system failures such as false thermal alarms will not happen. 2.1(3a)B 2.2(1h)A, 2.2(3f)B CSCuo50049 Cisco UCS Manager will not experience HA cluster failover after upgrading from Release 1.4.

2.0(5g)A 2.2(1h)A, 2.2(3d)A. Table 47 Resolved Caveats in Release 2.2 (1g) Defect ID Description First Bundle Affected Resolved in Release CSCuo51708 UCSM autoinstall downgrade no longer fails while reverting firmware during autoinstall process. 2.1(1f)A 2.2(1g)A CSCuq70724 DIMM I2C controller is automatically reset if there are invalid I2C transactions that prevent the chassis from obtaining temperature readings from blades (which can cause fan speeds to spin at 100%). 2.1(1a)B 2.2(1g)B CSCuq20755 Race conditions no longer occur due to DME crashing and restarting.

2.0(1q)A 2.2(1g)A CSCuq74472 Unnecessary thermal events on IOM stating that the thermal sensor reading is not available no longer occur. 2.1(3c)A 2.2(1g)A CSCur37260 FI upgrade or downgrade no longer fails due to lack of disk space in /mnt/pss. 2.1(3b)A 2.2(1g)A. Table 48 Resolved Caveats in Release 2.2 (1f) Defect ID Description First Bundle Affected Resolved in Release CSCuq35685 IGMPv2 traffic no longer causes MAC flapping on upstream switches when the FI has multiple uplinks connecting to different switches. 2.2(1b)A 2.2(1f)A CSCur01379 The security vulnerabilities identified by Common Vulnerability and Exposures (CVE) CVE-2014-7169, CVE-2014-6271, CVE-2014-6277, CVE-2014-7186, CVE-2014-7187, and CVE-2014-6278 are addressed. 2.0(1q)A 2.2(1f)A CSCuo34760 vEthernet interfaces and VIFs no longer remain in down state if the primary FI in a HA cluster is rebooted and comes up as the secondary FI.

2.1(2d)A 2.2(1f)A CSCuq63086 Cisco B200 M3 no longer fails with a ‘Controller 1 on server x/y is inoperable’ error. 2.2(1e)B 2.2(1f)B. Table 49 Resolved Caveats in Release 2.2 (1e) Defect ID Description First Bundle Affected Resolved in Release CSCup61947 MAC learning no longer fails after adding 1000 or more VLANs with a large PV count with 120 or more virtual interfaces each with 1000 VLANs.

2.2(1d)A 2.2(1e)A, 2.2(2d)A CSCul44421 Error no longer encountered when accessing shared-storage during FI reboot, upgrade, or IOM reset. 2.0(5f)B 2.2(1e)B CSCum98771 User no longer receives config failure message ‘Flexflash controller error, probably not supported, not equipped or inoperable’ when Cisco UCS Manager is updated from 2.1(2a) or above to 2.2(1) with FlexFlash State enabled. 2.2(1b)A 2.2(1e)A CSCun24381 Customers using the Cisco UCS PowerTool will no longer experience problems when scraping the Java log file for XML parsing of config changes when running Java version 7 update 45. 2.2(1b)A 2.2(1e)A CSCun25187 Cisco UCS Manager no longer becomes Lost-Visibility in Cisco UCS Central when keyring with certificate chain is configured for https communication if third-party certificates are signed by subordinate CA instead of root CA. 2.1(2a)A 2.2(1e)A CSCun25692 M71KR-Q no longer runs out of heap and causes SAN boot failure while allocating memory to critical data structure. 2.2(1b)B 2.2(1e)B, 2.2(2d)B CSCun83328 vNIC PCI addresses no longer get changed when downgrading from release 2.2(1e) to 2.0(5).

2.2(1d)B 2.2(1e)B CSCun84897 Server reboots are no longer triggered when vNIC template is used with global service profile and customer changes MTU setting. 2.1(3a)A 2.2(1e)A CSCuo78883 Cisco UCS Manager and KVM users or admins using JRE version 1.7 update >= 40 no longer encounter a pop-up window with the 'Application Blocked by Security Settings' dialog. 2.0(1m)A 2.2(1e)A CSCuo79500 Cisco UCS Manager no longer falsely displays information that indicates a vNIC with a usNIC connection policy was automatically changed to dynamic vNIC when a customer adds a second vNIC with a usNIC policy.

2.2(1c)A 2.2(1e)A. Table 50 Resolved Caveats in Release 2.2 (1d) Defect ID Description First Bundle Affected Resolved in Release CSCui31011 VIFs and vNICs on the subordinate no longer fail to come up after FI failover.

2.1(2a)A 2.2(1d)A CSCul38768 “Management services are unresponsive” fault no longer displayed in Cisco UCS Manager unless there is actually an HA condition failure. 2.1(1e)A 2.2(1d)A CSCul96021 Frequent crashing of dcosAG process no longer occurs after Cisco UCS Manager upgrade.

2.2(1b)A 2.2(1d)A CSCum02561 Server no longer reboots after infra-only upgrade that is followed by a service profile change. 2.2(1b)A 2.2(1d)A CSCum04646 FI no longer reboots while doing SNMP Walk with LDAP configuration enabled. 2.2(1b)A 2.2(1d)A CSCum09954 Erroneous minor faults “FCoE” or “FC uplink is down” are no longer displayed in Cisco UCS Manager when FC uplink interfaces are admin shut. 2.2(1b)A 2.2(1d)A CSCum75266 FIs no longer go to bash prompt during upgrade to 2.2 release.

2.2(1b)A 2.2(1d)A CSCum82888 Access to Cisco UCS Manager, FIs, and Virtual IP is no longer blocked after upgrade or reboot if default keyring was deleted. 2.2(1b)A 2.2(1d)A CSCun01514 Boot Order change via CLI or XML API no longer fails between SAN and other devices.

2.2(1b)A 2.2(1d)A CSCun19289 The mgmt0 interface on an FI no longer drops traffic coming from blades behind that FI. 2.2(1b)B 2.2(1d)B CSCun21077 Blades running ESXi OS will no longer hit a speed cap of 10GB when running on hardware that allows for higher speeds. 2.2(1b)A 2.2(1d)A CSCun59192 Secure properties, such as authentication passwords and community strings, are no longer reset when importing a backup configuration that was created while being registered to Cisco UCS Central with admin policies managed globally. 2.2(1c)A 2.2(1d)A. Table 51 Resolved Caveats in Release 2.2 (1c) Defect ID Description First Bundle Affected Resolved in Release CSCum43435 The Cisco UCS VIC 1280 adapter on a Cisco UCS B440 M2 blade no longer hangs during PXE boot. 2.2(1b)B 2.2(1c)B CSCul44120 Cisco UCS blade servers performing a PXE boot from a Citrix PVS system no longer fail after the initial bootloader initialization with a “No API found” error.

2.1(2a)B 2.2(1c)B CSCum51025 Cisco UCS Manager domains registered in Cisco UCS Central no longer fail during scheduled backups. 2.2(1b)A 2.2(1c)A CSCum25003 Associated local and global service profile inventory information is no longer sent to Cisco UCS Central when no changes are made. 2.2(1b)A 2.2(1c)A. Table 52 Resolved Caveats in Release 2.2 (1b) Defect ID Description First Bundle Affected Resolved in Release CSCug93342 After rebooting the FI during an upgrade, the FI no longer boots to the Loader prompt.

Note To ensure the new power sequencer firmware is installed properly, you must power cycle the FI after the upgrade is completed. 2.1(3a)A 2.2(1b)A CSCuc19701 The 2204 IOM no longer reboots when the FI is reset. 2.1(1a)A 2.2(1b)A CSCuf90470 When Call Home is enabled, Online Insertion and Removal (OIR) or failure of hardware modules in the FI no longer causes the FI to reboot. 2.1(1b)A 2.2(1b)A CSCui45963 Some of the text and controls are no longer truncated when you create a service profile or service profile template using the wizard.The edit option for storage settings is enabled.

2.1(2a)A 2.2(1b)A CSCuj84421 Installing Java 7 update 45 no longer causes UCS Manager GUI failures. 2.1(1f)A 2.2(1b)A CSCuc38783 Firmware upgrade no longer fails on BRCM 57712 adapter. 2.1(1a)A 2.2(1b)A CSCuj77813 Associating service profile to a C-series server integrated with Cisco UCS Manager no longer fails. 2.1(3a)C 2.2(1b)A CSCui43905 When you try to create an iSCSI NIC on a service profile, UCS Manager no longer displays any warning messages. 2.1(2a)B 2.2(1b)A CSCuj32124 During normal operation IOM no longer unexpectedly reboots with CPU reset. 1.4(2b)A 2.2(1b)A CSCui41165 Cisco UCS Manager no longer displays “error accessing shared-storage”error or have the following issues: • Call home fan alerts are sent and cleared immediately • Errors during IOM boot-up 1.4(2b)A 2.2(1b)A CSCuj78099 FC traffic between a Cisco UCS FI and a Cisco MDS switch is no longer disrupted when the FI is in switch mode. 2.1(3a)A 2.2(1b)A CSCuj61839 With the 2.2(1b)B bundle, Cisco UCS Blade servers on a Cisco M81KR VIC adapter no longer encounter ASSERT FAILED @ mips/ecpu_pani.c:138 errors.

2.1(2a)A 2.2(1b)A CSCuj10564 Discard TX on a FC trunk port are no longer seen after hot-swapping the Cisco UCS-FI-E16UP expansion module on the Cisco UCS 6248UP FI. 2.1(1f)A 2.2(1b)A CSCuf77316 Windows 2012 installed on a FlexFlash card no longer fails Microsoft certification. 2.1(2a)B 2.2(1b)A CSCui87195 The FLS process on Cisco CNA M72KR-E no longer cores with the following message: 130820-19:47 fls.fc vnic 15: Local port down for lif 4.

2.0(5c)C 2.2(1b)A CSCuj99958 During heavy FC traffic, the server no longer stops responding with an ASSERT FAILED (Exception 2 triggered!) @ mips/ecpu_panic.c:138 error. 2.1(1f)A 2.2(1b)A CSCug89448 The tech support collection no longer fails on the Cisco UCS Manager GUI. 2.0(1s)A 2.2(1b)A CSCug63368 PXE boot no longer fails in vPC environments if the DHCP relay agent is installed as the gateway IP address during a PXE boot instead of the HSRP IP address.

2.1(1d)B 2.2(1b)A CSCui82679 FlexFlash storage is no longer disconnected from a Cisco B200 M3 server after booting ESX or ESXi from a FlexFlash card. 2.1(2a)A 2.2(1b)A CSCuc52981 Downloaded license files for FIs continue to be displayed in the downloads area after installation. 2.0(3a)A 2.2(1b)A CSCti39470 RAID 50 and RAID 60 configurations can now be created and managed by Cisco UCS Manager.

1.4(1i)A 2.2(1b)A. Defect ID Description First Bundle Affected Resolved in Release CSCvb48577 UCS Manager includes a version of OpenSSL that is affected by the vulnerability identified by the Common Vulnerability and Exposures (CVE) IDs: CVE-2016-6304 CVE-2016-6305 CVE-2016-2183 CVE-2016-6303 CVE-2016-6302 CVE-2016-2182 CVE-2016-2180 CVE-2016-2177 CVE-2016-2178 CVE-2016-2179 CVE-2016-2181 CVE-2016-6306 CVE-2016-6307 CVE-2016-6308 CVE-2016-6309 CVE-2016-7052 There is no known workaround. 2.2(8g)B Resolved in 2.2(8i)B CSCvb61637 A vulnerability in the CLI of the Cisco Unified Computing System Manager could allow an authenticated, local attacker to perform a command injection attack. The vulnerability is due to insufficient input validation for the affected command. An authenticated local attacker could exploit this vulnerability by injecting crafted command arguments into a redirect of a vulnerable CLI command.

An exploit could allow the attacker to execute arbitrary system commands with the privileges of the authenticated user. UCS Manager is affected by the vulnerability identified by the Common Vulnerability and Exposures (CVE) IDs: CVE-2017-6600 There is no known workaround. 2.2(8g)A Resolved in 2.2(8i)A CSCvb86764 A vulnerability in the CLI of the Cisco UCS Manager could allow an authenticated, local attacker to perform a command injection attack. The vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by injecting crafted command arguments into a vulnerable CLI command. An exploit could allow the attacker to read or write arbitrary files at the user's privilege level outside of the user's path.

UCS Manager is affected by the vulnerability identified by the Common Vulnerability and Exposures (CVE) IDs: CVE-2017-6601 There is no known workaround. 2.2(8g)A Resolved in 2.2(8i)A CSCvb86775 A vulnerability in CLI of the Cisco Unified Computing System Manager could allow an authenticated, local attacker to perform a command injection attack.

The vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by injecting crafted command arguments into a vulnerable CLI command. An exploit could allow the attacker to read or write arbitrary files at the user?s privilege level outside the expected path and gain access to other devices. The vulnerability is identified by the following Common Vulnerability and Exposures (CVE) IDs: CVE ID CVE-2017-6602 There is no known workaround.

2.2(8g)A Resolved in 2.2(8i)A CSCvb86797 A vulnerability in the debug plugin functionality of the Cisco Unified Computing System Manager could allow an authenticated, local attacker to execute arbitrary commands. The vulnerability is due to inadequate integrity checks for the debug plugin. An attacker could exploit this vulnerability by crafting a debug plugin and load it using elevated privileges.

An exploit could allow the attacker to run malicious code that would allow for the execution of arbitrary commands as root. The vulnerability is identified by the following Common Vulnerability and Exposures (CVE) IDs: CVE ID CVE-2017-6598 There is no known workaround. 2.2(8g)A Resolved in 2.2(8i)A CSCvb86816 A vulnerability in local-mgmt CLI of the Cisco Unified Computing System Manager could allow an authenticated, local attacker to perform a command injection attack. The vulnerability is due to insufficient input validation for the affected command. An authenticated local attacker could exploit this vulnerability by injecting crafted command arguments into a vulnerable CLI command. An exploit could allow the attacker to execute arbitrary system commands with the privileges of the authenticated user.

The vulnerability is identified by the following Common Vulnerability and Exposures (CVE) IDs: CVE ID CVE-2017-6597 There is no known workaround. 2.2(8g)A Resolved in 2.2(8i)A CSCvc37931 Unvalidated redirects and forwards may be possible when UCS Manager accepts untrusted input that could cause it to redirect the request to a URL contained within untrusted input. By modifying untrusted URL input to a malicious site, an attacker may successfully launch a phishing scam and steal user credentials. Unvalidated redirect and forward attacks can also be used to maliciously craft a URL that would pass the application�s access control check and then forward the attacker to privileged functions that they would normally not be able to access.

The vulnerability is identified by the following Common Vulnerability and Exposures (CVE) IDs: CVE ID CVE-2017-6604 Impacted Unified Computing System (UCS) B-Series M3 and M4 Blade Servers Affects any of the 2.2(8) and 3.1(2) blade bundle versions. None of the 3.0 or 3.1(1) blade bundle versions. Impacted Unified Computing System (UCS) C-Series M3 and M4 Rack Servers Affects 3.0(1c) CIMC versions. None of the 1.5 or 2.0 CIMC versions. There is no known workaround.

2.2(8g)A Resolved in 2.2(8i)A CSCvc58789 A port may get a disabled error from 10 consecutive DFE tuning failures. If this is encountered, try the following steps: • Unplug and re-insert cable or SFP • Try replacing the cable or SFP. • Disable and then re-enable the link from UCSM (equivalent of shut / no shut from NxOS). 2.2(8g)A Resolved in 2.2(8i)A CSCvc94686 UCS Manager includes a version of OpenSSL that is affected by the vulnerability identified by the Common Vulnerability and Exposures (CVE) IDs: CVE-2017-3731 - Truncated packet could crash via OOB read. This product is not affected by the following vulnerabilities: CVE-2017-3730 - DHE parameters cause a client crash CVE-2017-3732 - BN_mod_exp may produce incorrect results on x86_64 There is no known workaround. 2.2(8g)A Resolved in 2.2(8i)A CSCvc96103 UCS Manager includes a version of OpenSSL that is affected by the vulnerability identified by one or more of the following Common Vulnerability and Exposures (CVE) IDs: CVE-2017-3731 CVE-2017-3730 CVE-2017-3732 And disclosed in There is no known workaround.

2.2(8g)A Resolved in 2.2(8i)A CSCve19522 UCS Domains running version 3.1(3a) may move to a state of lost visibility after a certificate is regenerated on UCS Central and could fail to recover. In some cases, the UCS 3.1(3a) domain registration may also get stuck in a registering state. Use one of the following workarounds to recover the system: • Upgrade to UCSM 3.1(3b). • Load debug plugin in UCSM and restart the httpd process manually. • UCSM# ps -aef grep -i httpd.sh ==>To get the process id for httpd.sh • UCSM# kill -9 • Perform a pmon restart on both nodes of UCSM, which will intern restart the httpd along with other processes.

2.2(8g)A Resolved in 2.2(8i)A. Table 53 Open Caveats in Release 2.2(8d) Defect ID Symptom Workaround First Bundle Affected CSCvb11667 Server with UEFI BIOS enabled, may fails to SAN boot from a target LUN with an ID other than 0 and using T10 DIF protection. When this issue occurs, set the BIOS to legacy mode or use LUN ID 0. 2.2(8d)B Resolved in 2.2(8f)B CSCvb82862 EUI-64 bit addresses were invalid for storage connection policies or SAN boot targets. There is no known workaround.

2.2(8d)A Resolved in 2.2(8f)A CSCvb95978 On C460 M4 servers, TPM version 1.2 may fail to initialize after installing ESXi OS, and enabling and activating TPM and TXT. There is no known workaround.

2.2(8d)B Resolved in 2.2(8f)B. Table 54 Open Caveats in Release 2.2(8c) Defect ID Symptom Workaround First Bundle Affected CSCvd54116 Setting a custom cipher suite for UCS Manager HTTPS to remove the usage of TLS v1.0 and 1.1, may result in a 'handshake failure' error message when attempting to open a Java login to UCS Manager or a KVM session to a blade server. Explicitly allow AES128-SHA in the custom cipher to allow logins to UCS Manager. This does not affect UCS Manager versions that have the HTML5 login higher than 3.1, as the custom suite is adhered to. However, if a KVM session is opened then the failure will be seen as well, as this is still uses Java. 2.2(8c)A Resolved in 2.2(8i)A CSCvb85331 The following fault may occur after a UCS Manager software upgrade. Code: F1781 Description: Management database version mismatch detected failover may not complete Affected Object: sys/mgmt-entity-B Name: Mgmt Entity Mgmt Db Version Mismatch Cause: Replication Failure Type: Management Restart the process monitor on the subordinate FI with the following commands: connect local-mgmt (A/B) pmon stop pmon start show pmon state 2.2(8c)A Resolved in 2.2(8g)A CSCvb47285 In the process of rebooting the fabric interconnect and collection of tech support logs, a core file was generated.

There is no known workaround. Table 55 Open Caveats in Release 2.2(8b) Defect ID Symptom Workaround First Bundle Affected CSCvb00303 During a Server discovery, Rack servers may get stuck and may not discover due to a lost connection status from B side while only A side is appearing. This may occur after upgrading to 2.2(8b) and performing an Erase Samdb operation and then enabling all required server ports to bring the server up. There is no known workaround. 2.2(8b)A Resolved in 2.2(8h)A CSCvc60876 The 6248, 6296, and 6332 Series Fabric Interconnects may send Smart Call Home messages in the wrong format. Contact the Smart Call Home support team to fix the XML file and reprocess the message. 2.2(8b)A Resolved in 2.2(8g)A CSCva96740 Changes in adapter policy from UCS Manager did not trigger a server redeploy.

Manually schedule a reboot for the Service Profile for the FC Adaptor policies to be reflected. 2.2(8b)A Resolved in 2.2(8c)A. Defect ID Symptom Workaround First Bundle Affected CSCuz52483 UCS Manager includes a version of OpenSSL that may be affected by the vulnerabilities identified by the Common Vulnerability and Exposures (CVE) IDs: CVE-2016-2108 CVE-2016-2107 CVE-2016-2105 CVE-2016-2106 CVE-2016-2109 CVE-2016-2176 There is no known workaround.

2.2(8a)A Resolved in 2.2(8i)A CSCvc31867 When upgrading the SSD to firmware 32F3Q, the firmware may be truncated and written as 2F3Q, which may cause a second request for the reboot of the server. Exclude the Local Disk Firmware update from the Host Firmware Package (HFP) in the associated Service Profile. 2.2(8a)A Resolved in 2.2(8g)A CSCuy81688 From Cisco UCS Manager tech-support, running /var/sysmgr/sam_logs/httpd_cimc.log on the affected fabric interconnect may show the exceeded max time without restart error.

From Cisco UCS Manager tech-support, running /ls_l.out on the affected fabric interconnect may show the existence of a 'cimcrestart' file under /isan/apache/conf/. The modified date is now updated.

If this issue occurs, do the following: • Using the debug plugin, delete the file /isan/apache/conf/cimcrestart. • Stop and start the UCSM processes using 'pmon stop'/'pmon start'. 2.2(8a)A Resolved in 2.2(8f)A CSCvb16804 Booting from SAN to 4K UEFI target may fail.

There is no known workaround. 2.2(8a)B Resolved in 2.2(8f)B CSCuy65407 The VIC adapter may go into an inaccessible state while flapping RNICs that run high block size read/write workloads. When this issue occurs, power cycle the server to reboot the VIC. 2.2(8a)B, 2.2(8a)C CSCuz41121 When booting to RHEL or running system stress tests, Cisco UCS B420 M4 servers with certain Intel ® E5 v3 CPUs may report QPI Correctable System Event Logs with the following error message: Link Layer CRC successful reset with no degradation These System Event Logs are benign and do not impact system operation.

There is no known workaround. 2.2(8a)B Resolved in 2.2(8c)B CSCuz76717 The ESX host reboot hangs while loading the ENIC module with NetFlow enabled. If this issue occurs, do the following: • Disable Netflow • Reboot the system • Enable NetFlow 2.2(8a)B, 2.2(8a)C CSCuz79138 The host becomes unresponsive when using second generation VIC adapters while running FCOE traffic and Ethernet traffic on the same side of the fabric with NetFlow enabled. No known workaround for second generation VIC adapters. You can enable NetFlow with third generation VIC adapters or later generation adapters.

2.2(8a)B, 2.2(8a)C CSCva36835 When using Cisco B460 M4 or B260 M4 blade servers, a warm boot does not reset the LSI controller. There is no known workaround. 2.2(8a)B Resolved in 2.2(8b)B CSCva38325 C460 M4 systems under heavy CPU/memory load can report Machine Check Exceptions in Linux syslog and/or correctable QPI errors in the System Event Log. These MCE and SEL are benign and do not impact system operation. There is no known workaround.

2.2(8a)C CSCva67159 Cisco UCS Manager httpd failed to start when the default keyring was deleted. If this issue occurs, do the following: • Create default certificate. • Disable and Enable http and https service from CLI If http-redirect is disabled, then disable and enable http-redirect service. At this stage, user will be able to access UCSM GUI • UCSM GUI will be still referencing default self-signed certificate.

Table 56 Open Caveats in Release 2.2(7c)T Defect ID Symptom Workaround First Bundle Affected CSCva53726 UCS Manager allows downgrade of firmware for the following rack servers installed with v4 CPU models to a version less than the minimum required version of CIMC / BIOS firmware: • UCSC-C240-M4L • UCSC-C240-M4S • UCSC-C240-M4S • UCSC-C240-M4SX • UCSC-C220-M4L • UCSC-C220-M4S • UCSC-C240-M4SNEBS After a downgrade, servers may fail during the BIOS post. If the service profile is using the host firmware package policy with an older version, remove the older version from the policy. If UCS Manager is configured with auto-sync firmware policy, remove the older version from the auto-sync policy. After making the above changes, upgrade and activate the CIMC and BIOS to a minimum required version or via host firmware policy. Minimum CIMC / BIOS version required for v4 CPU model can be found in the following documents: • Cisco UCS B200 M4 Server Upgrade Guide for E5-2600 v4 Series CPUs • Cisco UCS C-Series Servers Upgrade Guide for Intel Xeon v4 Series CPUs 2.2(7c)T Resolved in 2.2(8d)T.

Table 57 Open Caveats in Release 2.2(7c) Defect ID Symptom Workaround First Bundle Affected CSCvc17769 The fabric interconnect may crash when the bound interface of a Veth is in the Not Initialized State during a VLAN configuration change. If the bound interface of Veth is not initialized, then do not perform a VLAN configuration change on the Veth. 2.2(7c)A Resolved in 2.2(8f)A CSCva34426 Cisco UCS 3X60 Server failed to boot from the LSI RAID controller managed disk slots 1 or 2, when the disks were in JBOD mode. If this issue occurs remove the internal riser based SSDs and reacknowledge the server. 2.2(7c)A Resolved in 2.2(8b)A CSCva53726 UCS Manager allows downgrade of firmware for the following rack servers installed with v4 CPU models to a version less than the minimum required version of CIMC / BIOS firmware: • UCSC-C240-M4L • UCSC-C240-M4S • UCSC-C240-M4S • UCSC-C240-M4SX • UCSC-C220-M4L • UCSC-C220-M4S • UCSC-C240-M4SNEBS After a downgrade, servers may fail during the BIOS post.

If the service profile is using the host firmware package policy with an older version, remove the older version from the policy. If UCS Manager is configured with auto-sync firmware policy, remove the older version from the auto-sync policy. After making above changes, upgrade and activate the CIMC and BIOS to minimum required version or via host firmware policy. Minimum CIMC / BIOS version required for v4 CPU model can be found in the following documents: • Cisco UCS B200 M4 Server Upgrade Guide for E5-2600 v4 Series CPUs • Cisco UCS C-Series Servers Upgrade Guide for Intel Xeon v4 Series CPUs 2.2(7c)T Resolved in 2.2(8d)T CSCux11611 Seagate hard drives left spinning idle without an operating system installed or setup with the JBOD configuration without read or write activity were prone to failure.

Impacted hard drives are listed here: • UCS-HD4T7KS3-E • UCSC-C3X60-HD4TB (4TB) • UCS-HDD3TI2F214 (3TB) • UCS-HDD2TI2F213 (2TB) • UCS-HDD1TI2F212 (1TB) • UCS-HD6T7KL4K • UCSC-C3X60-HD6TB • UCSC-C3X60-6TBRR Do not leave idle systems powered on for extended periods of time. Either install an OS with all drives formatted or configure drives in a RAID configuration other than JBOD or JBOD equivalent and fully initialize the Virtual Drive(s). 2.2(7c)B Resolved in 2.2(8c)B CSCux53224 A fatal error may be observed when you create or remove virtual drives with RAID 5 and RAID 6 controller combination. No known workaround. 2.2(7c)C Resolved in 2.2(7d)C. Defect ID Symptom Workaround First Bundle Affected CSCuz98957 UCS Manager may incorrectly report the amount of drive slots on B200-M2 blade servers.

There is no known workaround. 2.2(7b)A Resolved in 2.2(8i)A CSCvc39322 For B260 M4 Blades, BIOS v3.1.2.2 may intermittently fail Windows HLK and HCK Trusted Platform Module (TPM) tests on Windows Server 2016 and Windows Server 2012 R2.

Toggle the BIOS 'TXT Support' setting to disable. 2.2(7b)B Resolved in 2.2(8g)B CSCva35757 Latency between the UCS Manager Client and fabric interconnect may cause the firmware page to load slowly. Use the CLI to complete upgrade or downgrade procedures. 2.2(7b)A Resolved in 2.2(8f)A CSCvb05762 UCS Manager GUI and CLI may fail to respond when the Data Management Engine (DME) hangs with a WaitOnLimit log message. Restarting the process monitor on the primary node resolves the issue.

2.2(7b)A Resolved in 2.2(8d)A CSCva08256 Cisco CIMC and BIOS no longer get stuck updating or activating with the host firmware pack when the new host firmware pack has the same name and version as the system being updated. Create a host firmware pack with a different name than the one already in the organization or the sub-organization levels. 2.2(7b)A Resolved in 2.2(8b)A CSCva38476 An infrastructure software upgrade to UCS Manager 2.2(7b) or higher can fail when both fabric interconnects are incompatible or when one of the fabric interconnects are unresponsive.

Contact TAC to apply a workaround. 2.2(7b)A Resolved in 2.2(8c)A CSCuy93451 When you create a vNIC from an updating vNIC template, and then delete vLANs from the updating vNIC template, these VLANs are not deleted from the vNIC. When this issue occurs, do the following: • Unbind the vNIC from the vNIC template on the service profile or service profile template. • Delete the VLANs from the vNIC.

• Bind the vNIC back to the vNIC template. 2.2(7b)A Resolved in 2.2(7c)A CSCuz54661 Cisco B200 M3 Server failed to post if NUMA is disabled. Enable NUMA optimization in the BIOS policy. Then perform a reset CMOS from the Recover Server options. This reboots the server and must be done to recover and stop the errors. Note If NUMA must stay disabled, the only workaround is to use 2.2(6d) or lower that doesn't contain BIOS version B200M3.2.2.6c.0.50. 2.2(6g)B Resolved in 2.2(8b)B CSCuz08759 The vniccfgd process no longer crashes when upgrading the VIC firmware contained in the server bundle to version 2.2(7b)B or 2.2(7b)C.

When this issue occurs, revert back to the previous firmware version before the downgrade occurred. 2.2(7b)B 2.2(7b)C Resolved in 2.2(7c)B 2.2(7c)C CSCuz69373 During Cisco UCS Manager upgrade to release 3.1(1), you will see CATERR faults due to unresponsive eCPUs. This issue happens when the eCPUs fall into diagnostic code (debug loop) after the DINT CPU input is asserted.

No known workaround. 2.2(7b)B Resolved in 2.2(7c)B CSCuy74364 When the CIMC version in the server is earlier than the 2.2(7) C Series bundle CIMC version, or, when the BIOS version in the server is later than the 2.2(6) C Series BIOS version, the host reboot is triggered along with a BIOS upgrade even for any unrelated service profile modification. To avoid this issue, ensure that the server has BIOS and CIMC versions from the same C Series bundle.

2.2(7b)C CSCva29365 Enabling stateless offloads for NVGRE in a 3rd generation Cisco VIC adapters’ configuration with UCSM/CIMC leads to inaccessible vNIC interfaces in the host OS for the following 3rd generation VIC adapters: • UCSC-C3260-SIOC • UCSB-VIC-M83-8P • UCSB-MLOM-40G-02 • UCSB-MLOM-40G-03 • UCSC-PCIE-C40Q-03 • UCSC-MLOM-C40Q-03 This affects only the managed UCS deployments and standalone NIV mode deployments. Classical Ethernet operation is unaffected. Disable stateless offloads for NVGRE in a 3rd generation Cisco VIC adapters. 2.2(7b)B Resolved in 2.2(7d)B CSCuz69100 Disk Firmware update fails on a C240 rack server with a UCSC-SAS12GHBA storage controller in one of the following scenarios: • when more than ten disks are discovered • when certain Seagate HDD models are used This issue occurs if Cisco UCS Manager fails to map the local disk to its native SCSI device name because of a mismatched serial number between them. No known workaround. 2.2(7b)A Resolved in 2.2(7d)A CSCuz65286 Cisco UCS Manager firmware upgrade fails with the following message UCSM upgrade validation failed if the default value for IO throttle count in the FC adapter policy has a value of 16. Before starting the upgrade, change the following: • Change the maintenance policy to user-ack.

• Change the IO throttle count value to 256. 2.2(3a)A Resolved in 2.2(7d)A. Table 58 Open Caveats in Release 2.2(6f) Defect ID Symptom Workaround First Bundle Affected CSCux21413 When you remove and reinsert a drive in the same slot, the Locator Storage Locator LED may remain on all the time.

There is no known workaround. 2.2(6f)B Resolved in 2.2(7b)A CSCux07578 Cisco UCS Blade servers B400 M1 or B400 M2 running on firmware version 4.10 with SATA drives, may experience data consistency failures. There is no known workaround. 2.2(6f)B Resolved in 2.2(7b)A CSCuw46478 The Local disk Locator LED remains OFF, although enabled in Cisco UCS Manager. There is no known workaround. 2.2(6f)B Resolved in 2.2(7b)B CSCuv45574 On C220/C240 M3 systems with LSI 9271-8i controller, after downgrading the firmware to Release 2.0(3f) or lower with HUU update all, the virtual machines running on the ESXi OS become inaccessible.

SUSE operating systems are also impacted and will not boot after upgrade. See the following VMware knowledge base: (vSphere handling of LUNs detected as snapshot LUNs (1011387)) 2.2(6f)A Resolved in 2.2(7d)A.

Defect ID Symptom Workaround First Bundle Affected CSCvc92275 A kernel panic may occur on the Fabric Interconnect and could cause a reboot. The command: show logging onboard stack-trace shows that the panic may occur in the process usd_mts_kthread.

The call trace can be reviewed for a full match to this defect. Apply rate limiting or other QOS policies upstream to prevent large amounts of traffic from hitting the mgmt interfaces of the fabric interconnects. Apply ACL on upstream devices to only allow connectivity to mgmt interfaces from approved or identified bastion hosts.

2.2(6e)A Resolved in 2.2(8i)A CSCux96072 During heavy I/O traffic, the Cisco 12G Modular RAID controller may go offline with the Storage Controller SLOT HBA inoperable error logged in the CIMC event logs. A fix is available in UCS Manager 2.0.10e and 2.0.13. Upgrade the Storage controller firmware and its corresponding driver. 2.2(6e)C Resolved in 2.2(8g)C CSCvc89242 The Fabric Interconnect may reboot due to a CDP process crash. If CDP still crashes immediately after the fabric interconnect reboot, execute the following commands to avoid another FI reboot. Connect nxos system no hap-reset Contact TAC with the CDP core dump files if the reboot occurs again. 2.2(6e)A Resolved in 2.2(8g)A CSCuv43349 During server discovery, Cisco UCS Blade server association or disassociation, the following failures may be reported: • Waiting for BIOS Post Completion • Unable to get SCSI Device Information from the system When this issue occurs, do the following: • Remove all of the Local Disks from the failed blade server.

• Reboot the server without any Local Disks. 2.2(6e)B Resolved in 2.2(7b)B CSCuz96855 UCS M71KR cards could crash with the error “E4194871”. Reduce the number of targets zoned with the initiator. 2.2(6e)A Resolved in 2.2(8c)B CSCva34343 The P0V75_STBY sensor may throw an alert incorrectly on Cisco B200M4 servers. There is no known workaround.

2.2(6e)B Resolved in 2.2(8c)B CSCux47667 Service profile association to a server fails if the service profile was previously associated to a different server, and a LUN was deployed. Automotive Sensors John Turner Pdf To Excel on this page. Delete the LUN configuration of the service profile before associating to a different server. 2.2(6e)A Resolved in 2.2(6f)A CSCva01733 PXE in Legacy Boot mode fails if there is an excessive unicast or multicast high background traffic with a packet size larger than MTU directed to the client server. This was seen with ESXi Autodeploy on a specific setup which likely had unusually high multicast traffic directed at the client server. This traffic was not from the PXE server for file transfer, but from some other source.

Reduce excessive unicast or multicast background traffic directed to the client server. 2.2(6e)B Resolved in 2.2(6j)B 2.2(7d)B. Defect ID Symptom Workaround First Bundle Affected CSCvg06830 After adding a secondary fabric interconnect to a standalone setup and converting it to clustered setup, the VLAN 1 may not be added to the uplink port-channel, and could cause vEth on the B side to fail pinning and render the subordinate FI unusable. If vNIC uplink pinning is not occurring on the subordinate fabric interconnect, consider removing the VLAN (in this case VLAN 1) configuration from the vNIC to allow uplink pinning and high availability.

2.2(6c)A Resolved in 2.2(8i)A CSCvc88543 Cisco UCS Manager includes a version of the Apache HTTP Server software that is affected by the vulnerabilities identified by the following Common Vulnerability and Exposures (CVE) IDs: CVE-2016-0736, CVE-2016-2161, CVE-2016-5387,CVE-2016-8740, CVE-2016-8743 There is no known workaround. 2.2(6c)A Resolved in 2.2(8i)A CSCuw19082 During Cisco UCS Manager initial setup, while configuring the fabric interconnect, setup will assume the GUI configuration method if a DHCP lease is obtained for the mgmt interface. In addition, an url will be provided for the setup of the fabric interconnect. There is no known workaround. 2.2(6c)A Resolved in 2.2(7b)A CSCux66675 Rebooting a Cisco UCS 6296UP FI causes all physical interfaces to connect incorrectly with the Cisco UCS C460 M4 servers.

Reacknowledge the servers to resolve this issue. 2.2(6c)A Resolved in 2.2(7b)A CSCux98751 Anytime a new blade is inserted into the chassis, or a blade CIMC controller reboots, a chassis thermal fault may get generated because of the long time taken to reconnect from the IOM to the CIMC. This issue is caused by added time for BIOS Power Capping and SMBUS protection abilities.

This fault will clear by itself, and has no known workaround. 2.2(6c)B Resolved in 2.2(6g)B CSCuw44524 Server reboot with 'Uncorrectable error ECC errors' may occur when you initiate a 'clear CMOS' operation in Cisco UCS Manager Release 2.2(5a), 2.2(5b), 2.2(5c) or 2.2(6c) for E7 v2 processors on the C460 M4, B260 M4, and B460 M4 servers. Use the HUU or IMC interfaces to upgrade the BIOS again to any version, activate the BIOS, then reboot the system. 2.2(6c)A Resolved in 2.2(6e)A CSCuv45173 When you upgrade C-series server firmware for C220-M4, C240-M4 to Cisco UCS Manager 2.2(6c), you will see the following critical alarm: Board controller upgraded, manual a/c power cycle required on server x. The alarm seen is mistakenly categorized as a critical alarm.

It does not impact the functionality of the server and can be ignored. 2.2(6d)C CSCuw13352 If you set the Processor C6 Report to enabled in the BIOS policy, the system hangs during the OS boot process. When configuring the Processor C6 Report in the BIOS policy, accept the default value of disabled. 2.2(6c)A CSCuu78398 All blades running with the Storage Controller Firmware that does not support 4K native drives are showing the wrong virtual drive block size. This issue has no known workaround. 2.2(6c)A CSCuv18630 Cisco UCS B420 M3 servers with the firmware for UCSB-MRAID12G installed reports a nonfunctional Toshiba hard drive as Missing in Cisco UCS Manager.

This issue has no known workaround. 2.2(6c)A CSCuv25760 On CPU 4830 and 4850, the P-state is not changing when running the linpack benchmark on Redhat, which results in the frequency not increasing. This issue has no known workaround. 2.2(6c)A CSCuv27475 The UCS B-Series Blade Servers include a version of Unified Extensible Firmware Interface (UEFI) that is affected by the vulnerabilities identified by the Common Vulnerability and Exposures (CVE) IDs: CVE-2014-8274. This issue has no known workaround. 2.2(6c)A CSCuv27587 The import configuration fails when call home is not configured while performing a backup operation. Note Call home is configured in the system where UCS Manager imports the configuration.

Configure call home before taking a backup. 2.2(6c)A CSCuv38136 The platform might hang if there are any errors during the boot loader phase when in UEFI boot mode and using a Fibre Channel (FC) boot. Error conditions that require re-discovery/login for the FC LUN path during the BIOS boot phase, until the OS takes over, are currently not handled by VIC Oprom UEFI Driver. This results in a hang when the OS is being loaded by the BIOS using a VIC UEFI driver. Shutdown and reboot the server. 2.2(6c)A CSCuv59487 SPAN does not capture broadcast packets when you add vNIC as source. Use the HIF port where the Virtual Network Interface (vEth) is bound as the SPAN source.

2.2(6c)A CSCuv62162 The Power Technology token in UCS Manager BIOS policy has no effect on relevant CPU power performance option, such as EIST, Turbo Mode, P-States, and C-States. Each setup option that is meant to be controlled by the Power Technology token should be set manually in UCS Manager. 2.2(6c)A CSCuv76884 The Adaptor policies of dynamic vNICs created for a Global Service Profile (GSP) vNIC on UCS Manager are incorrect when there are two Dynamic vNIC policies with the same name created in different organization levels. Change the Global Service Profile label to update the service profile vNICs.

Note This might cause the server to reboot. 2.2(6c)A CSCuv88433 UCS Manager displays a different sets of I2C data based on whether the data is from the master IOM or the slave IOM that is connected to the primary fabric.

Note If UCS Manager primary is connected to the master IOM, the correct set of 12C data is collected. There is no workaround for this issue. 2.2(6c)A CSCuw10623 SBR firmware updates for servers with LSI9271-8i adapter appear to have a loss of datastore in the ESXi host. There is no workaround for this issue. 2.2(6c)A CSCuy98678 Cisco UCS 6296 fabric interconnect may crash unexpectedly with kernel panic, and impact any devices connected the fabric interconnect. Reboot the fabric interconnect to restore connectivity.

2.2(6c)A Resolved in 2.2(8a)A CSCuw55142 Cisco UCS B420M4 server with the UCSB-MRAID12G-HE no longer reports the following critical fault: Controller 1 on server is inoperable. Reason: Device non-responsive There is no workaround for this issue. 2.2(6c)B Resolved in 2.2(6f)B, 2.2(7b)B.

Table 59 Open Caveats in Release 2.2(5c) Defect ID Symptom Workaround First Bundle Affected CSCva27558 In scenarios such as traffic loops in external networks, a series of MAC add or delete operations may cause a missing MAC address in the software table, or in the hardware table for all the ASICs. Avoid traffic loops in the external network. Once the problem is encountered, the MAC address can be manually cleared from the CLI to fix the issue. Example: ESC-POD-OO25-A(nxos)# clear mac address-table dynamic address 0050.56b2.4db2 vlan 205 2.2(5c)A Resolved in 2.2(8c)A CSCux59912 A Cisco UCS system with servers connected to a Cisco Nexus 2232 FEX experiences bladeAG cores that are displayed in the switch logs. If this issue occurs, restart bladeAG through dplug or restart PMON. 2.2(5c)C Resolved in 2.2(8a)C CSCuw13170 When auto-deploying the installation of ESX on Ivy Bridge-EX platforms, some platforms that enforce ACS violations strictly will generate a non-maskable interrupt (NMI), and the host OS may crash. There is no known workaround.

2.2(5c)B Resolved in 2.2(5d)B. Table 60 Open Caveats in Release 2.2(5b) Defect ID Symptom Workaround First Bundle Affected CSCuy01645 DIMM temperature readings are reported as NA when the temperature is 16 degree Celsius more than the previous reading. This results in missed temperature readings, which in turn results in Cisco UCS Manager generating thermal alerts. This issue has no known workaround. 2.2(5b)B Resolved in 2.2(6i)B, 2.2(7c)B CSCux96432 Discovery fails on UCS B420 M4 servers with a 2-CPU configuration and a Fusion IO card in adapter slot 3. To resolve this issue, update the BIOS to version 2.2.6d.0 or later versions.

Resolved in 2.2(6g)B 2.2(5b)B CSCux40478 When installing a Cisco B200 M3 blade server with a UCSB-MLOM-40G-01 40G VIC and either a UCSB-F-FIO-1300MP or a UCSB-F-1600MS ioMemory PCIe flash Mezzanine card, in a chassis with an N20-I6584 IOM, blade discovery fails with an “Invalid adapter-iocard combination” error. When this issue occurs, remove the flash Mezzanine card to be able to continue installation. 2.2(5b)B Resolved in 2.2(6f)B. Table 61 Open Caveats in Release 2.2(5a) Defect ID Symptom Workaround First Bundle Affected CSCvb08928 A fabric interconnect may reboot from a VLAN deletion due to a FWM hap reset. Avoid deleting a VLAN. 2.2(5a)A Resolved in 2.2(8f)A CSCuw44524 When using Cisco UCS Manager Release 2.2(5a), 2.2(5b), 2.2(5c) or 2.2(6c) for E7 v2 processors on the C460 M4, B260 M4, and B460 M4 servers, while you perform a clear CMOS BIOS operation, the following error may occur, which eventually causes the server to reboot or crash: System Software event: Memory sensor, Uncorrectable ECC error, DIMM socket 1, Channel A, Memory Riser 2, Processor Socket 1. Was asserted Note This issue is specific to Cisco UCS Manager B and C server bundles.

When this issue occurs, downgrade to Cisco UCS Manager Release 2.2(4c). Note This issue will not be seen when using versions prior to Cisco UCS Manager release 2.2(5a), since support for both E7 v2 and v3 processors is available from Cisco UCS Manager release 2.2(5a). 2.2(5a)B 2.2(5a)C Resolved in 2.2(6e) CSCuv04436 Cisco UCS B200 M4 servers with the following CPUs may experience performance degradation: • E5-2667 v3 • E5-2643 v3 • E5-2640 v3 • E5-2637 v3 • E5-2630 v3 • E5-2630L v3 • E5-2623 v3 • E5-2620 v3 • E5-2609 v3 There is no workaround for this issue.

See the Software Advisory. A patch will be released in July, 2015. 2.2(4b)B CSCuu38206 If you disable and enable TXT several times, the state of TXT in the Cisco UCS Manager BIOS policy and the actual tboot state may get out of sync. When this occurs, do the following: • Clear the CMOS • Re-apply the Cisco UCS Manager BIOS policy 2.2(5a)B CSCuu58282 In Cisco UCS B420 M4 servers with UCSB-MRAID12G and UCSB-LSTOR-PT RAID controllers, in the rare event that Online Controller Reset (OCR) is triggered during normal I/Os on JBOD drives, excessive Fast Path IO failures may be seen after the controller is reset. When this occurs, reboot the host. 2.2(5a)B Resolved in 2.2(5b)B CSCuu35687 In Cisco UCS B420 M4 servers with UCSB-MRAID12G and UCSB-LSTOR-PT RAID controllers, the Fault/Locator LEDs for disks 3 and 4 are swapped.

This issue has no known workaround. 2.2(5a)B Resolved in 2.2(5b)B CSCuu49909 If you disable TXT in the Cisco UCS Manager BIOS policy after installing ESX with TXT enabled, ESX becomes unresponsive and displays the following message: Relocating modules and starting up the kernel. When this issue occurs, do one of the following: • Re-enable TXT • Re-flash BIOS 2.2(5a)B CSCuu61885 CSCuu71563 When UCS C460 M4 servers with Intel® Haswell processors are in UCSM mode, if the boot order policy is configured to boot from SAN, and the network adapter connected to it is installed on any PCIe slot other than PCIe slot 4, the BIOS may not show the SAN boot device in the boot order, and the system may fail to boot from SAN. As a result of SAN boot failure, the system may become unresponsive at the end of the BIOS POST, or attempt to boot from other boot devices configured in the boot order policy. If the system is booted from some other boot device, for example, Local HDD, the SAN LUN will still be accessible and usable. When this issue occurs, do the following: • Install the network adapter on PCIe slot 4 • Re-acknowledge the server • Re-configure the boot order policy • If the issue still persists, try rebooting the system a few times. Table 62 Open Caveats in Release 2.2(4b) Defect ID Symptom Workaround First Bundle Affected CSCvg44307 Communication between two end hosts may fail within the same VLAN and fabric interconnect.

Reboot the IOM to recover from this condition. 2.2(4b)A Resolved in 2.2(8i)A CSCvc46313 Remote operation from UCS Central no longer fails with the error message: Global Service profile [org-root/org-GKDC/org-/ls-SP_3260_03] can not be modified from UCS domain. Please make the changes from UCS Central that you are registered with. There is no known workaround. Contact TAC for assistance.

2.2(4b)A Resolved in 2.2(8g)A CSCuu29425 Prior to RHEL 7.0, packets received on the native VLAN were.