CSCvm02934 Cisco UCS B-Series M2 servers are based on Intel® processors that are vulnerable to exploits that use CPU speculative processing and data cache timing to potentially identify privileged information. These exploits are collectively known as L1 Terminal Fault (L1TF). CVE-2018-3615 (affecting SGX), also known as Foreshadow, is not known to affect any existing Cisco UCS servers because Cisco UCS M5 and earlier generation servers, and HyperFlex M5 and earlier generation servers do not use Intel ® SGX technology.

CVE-2018-3620 (affecting OS/System Management Mode) and CVE-2018-3646 (affecting Virtual Machine Monitors) are referred to as L1 Terminal Fault attacks by Intel®. These vulnerabilities are mitigated by applying the updated processor microcode from Intel included in the server firmware bundle, and the relevant Operating System and Hypervisor patches from the appropriate vendors. The fix for CVE-2018-3620 (OS/SMM) and CVE-2018-3646 (VMM) requires applying the updated processor microcode from Intel® as well as the relevant Operating System and Hypervisor patches from the appropriate vendors. For more information, please see the Cisco Security Advisory available here: CPU Side-Channel Information Disclosure Vulnerabilities: August 2018 3.2(1d)B, 3.2(1d)C 3.1(1e)B, 3.1(1e)C 2.2(1b)B, 2.2(1b)C CSCvm02934 is resolved in 3.1(3j)B, 3.1(3j)C

CSCvm03356 Cisco UCS B-Series M3 servers and C-Series M3 servers are based on Intel® processors that are vulnerable to exploits that use CPU speculative processing and data cache timing to potentially identify privileged information. These exploits are collectively known as L1 Terminal Fault (L1TF). CVE-2018-3615 (affecting SGX), also known as Foreshadow, is not known to affect any existing Cisco UCS servers because Cisco UCS M5 and earlier generation servers, and HyperFlex M5 and earlier generation servers do not use Intel ® SGX technology.

CVE-2018-3620 (affecting OS/System Management Mode) and CVE-2018-3646 (affecting Virtual Machine Monitors) are referred to as L1 Terminal Fault attacks by Intel®. These vulnerabilities are mitigated by applying the updated processor microcode from Intel included in the server firmware bundle, and the relevant Operating System and Hypervisor patches from the appropriate vendors. The fix for CVE-2018-3620 (OS/SMM) and CVE-2018-3646 (VMM) requires applying the updated processor microcode from Intel® as well as the relevant Operating System and Hypervisor patches from the appropriate vendors. For more information, please see the Cisco Security Advisory available here: CPU Side-Channel Information Disclosure Vulnerabilities: August 2018 4.0(1a)B, 4.0(1a)C 3.2(1d)B, 3.2(1d)C 3.1(1e)B, 3.1(1e)C 2.2(1b)B, 2.2(1b)C CSCvm03356 is resolved in 3.1(3j)B, 3.1(3j)C

CSCvm03351 Cisco UCS B-Series M4 servers, C-Series M4 servers, S3260 M4 storage servers, and HyperFlex M4 servers are vulnerable to exploits that use CPU speculative processing and data cache timing to potentially identify privileged information. These exploits are collectively known as L1 Terminal Fault (L1TF). CVE-2018-3615 (affecting SGX), also known as Foreshadow, is not known to affect any existing Cisco UCS servers because Cisco UCS M5 and earlier generation servers, and HyperFlex M5 and earlier generation servers do not use Intel ® SGX technology.

CVE-2018-3620 (affecting OS/System Management Mode) and CVE-2018-3646 (affecting Virtual Machine Monitors) are referred to as L1 Terminal Fault attacks by Intel®. These vulnerabilities are mitigated by applying the updated processor microcode from Intel included in the server firmware bundle, and the relevant Operating System and Hypervisor patches from the appropriate vendors. The fix for CVE-2018-3620 (OS/SMM) and CVE-2018-3646 (VMM) requires applying the updated processor microcode from Intel® as well as the relevant Operating System and Hypervisor patches from the appropriate vendors. For more information, please see the Cisco Security Advisory available here: CPU Side-Channel Information Disclosure Vulnerabilities: August 2018 4.0(1a)B, 4.0(1a)C 3.2(1d)B, 3.2(1d)C 3.1(1e)B, 3.1(1e)C 2.2(1b)B, 2.2(1b)C CSCvm03351 is resolved in 3.1(3j)B, 2.2(3j)C

CSCvj59299 CSCvj59301 Cisco UCS B-Series and C-Series M2 servers are based on Intel® Xeon® 5500, 5600, and EX series processors that are vulnerable to variants of an exploit that uses CPU speculative processing and data cache timing to efficiently leak information, known as Spectre. CVE-2018-3639 (Spectre/Variant #4) and CVE-2018-3640 (Spectre/Variant #3a) are addressed by relevant Operating System patches using an interface provided by updated processor microcode included in the server firmware bundle. The fix for CVE-2018-3639 (Spectre/Variant #4) and CVE-2018-3640 (Spectre/Variant #3a) requires applying the updated microcode from Intel as well as the relevant Operating System and Hypervisor patches from the appropriate vendors. For more information, see the Cisco Software Advisory at: CPU Side-Channel Information Disclosure Vulnerabilities: May 2018 3.1(1e)B, 3.1(1e)C 3.2(1d)B, 3.2(1d)C 2.2(1b)B, 2.2(1b)C CSCvj59299 is resolved in 3.1(3j)B and 3.1(3j)C

CSCvj54880 CSCvj54847 CSCvj54187 Cisco UCS M3 and M4 servers, and Hyperflex M4 servers are based on Intel® processors that are vulnerable to variants of an exploit that uses CPU speculative processing and data cache timing to efficiently leak information, known as Spectre. CVE-2018-3639 (Spectre/Variant #4) and CVE-2018-3640 (Spectre/Variant #3a) are addressed by relevant Operating System patches using an interface provided by updated processor microcode included in the server firmware bundle. The fix for CVE-2018-3639 (Spectre/Variant #4) and CVE-2018-3640 (Spectre/Variant #3a) requires applying the updated microcode from Intel as well as the relevant Operating System and Hypervisor patches from the appropriate vendors. For more information, see the Cisco Software Advisory at: CPU Side-Channel Information Disclosure Vulnerabilities: May 2018 3.1(1e)B, 3.1(1e)C 3.2(1d)B, 3.2(1d)C 2.2(1b)B, 2.2(1b)C 3.0(1c)B, 3.0(1c)C - Only for M3, M4 EP Resolved in 3.1(3j)B and 3.1(3j)C

CSCvh22485 After a vMotion or virtual machine migration in a VMFEX setup, virtual machines may be unable to receive broadcast or multicast packets, including ARP packets. The issue has been resolved. Do not perform a vMotion or VM migration. If needed, power-off, migrate the VM, and then power-on again. If the issue happens again, power cycle the VM after vMotion. 2.2(8g)A Resolved in 3.1(3f)A

CSCvg44307 Stale entries in IOM may cause a communication failure within the same VLAN and fabric interconnect. Reboot the IOM to recover from this condition. 2.2(4b)A Resolved in 3.1(3f)A

CSCuw09993 ESXi may report a fatal error while loading /s.v00 during the "Loading VMware Hypervisor" Screen. Ensure that your primary boot path is the SAN boot LUNs "Optimized Path" to the array. If the issue is encountered, this means that the LUN was sitting on a "Non-Optimized Path" and failed when the implicit transfer occurred to make it the "Optimized Path". Since the boot path is now the "Optimized Path" a reboot will result in the OS booting properly this time. 2.2(3a)B Resolved in 3.1(3f)B

CSCvg44307 Communication may fail within the same VLAN and FI for two hosts that are part of the same chassis. The same devices were able to communicate with other devices within the same VLAN but not with each other. Reboot the IOM to recover from this condition. 2.2(4b)A Resolved in 3.1(3f)A

CSCvg98077 During a TPM firmware update, the process may be interrupted by a UCS Manager event. If this event occurs, the TPM firmware flash may fail, resulting in a unresponsive state. There is no known workaround. 2.2(8i)B Resolved in 3.1(3f)B

CSCvf59328 The fNIC no longer reports DATA_CNT_MISMATCH when the TASK_SET_FULL SCSI command is received from the storage array. There is no known workaround. 3.1(1e)B Resolved in 3.1(3f)B

CSCvd54828 The RAID controller may encounter an error and resets. This may occur when an external SATA solid state drive (SSD) is used instead of a SAS SSD. There is no known workaround. 3.0(3a)C Resolved in 3.1(3d)C

CSCve23500 UCS B200 M4 Bladeserver may crash with SD Card Connectivity issues. The FlexFlash Scrub needs to be performed with the following steps. Warning: Scrubbing will erase the contents of SD card. Enable FlexFlash Scrub in the Scrub Policy / Create a new Scrub Policy with FlexFlash Scrub set to 'Yes' and use it in Service Profile Server Maintenance -> Re-acknowledge Once Server discovery and re-association finishes, set FlexFlash Scrub to 'No' in Scrub Policy used in the Service Profile. 2.2(3d)B Resolved in 3.1(3d)B

CSCve14926 The following configuration error occurs while associating a service profile with UCSC-C240M4-SX or UCSC-C240-M4L servers: Controller does not support out of band configuration Controller sys/<rack-unit-[the rack server id]>/board/storage-PCH-1 does not support OOB This error occurs only when the following conditions are met: The server has internal SSD(s) in slot 1 and 2 of the internal riser card, which are managed by the onboard PCH controller

The server has disks in external slot 1 and slot 2, which are managed by PCI slot based storage controller

The disk group policy, configured in the service profile, is set as Disk Group Configuration (Manual)

External disks 1 and 2 are selected in the manual disk group policy Configure the disk group policy as Disk Group Configuration (Automatic). 3.1(1e)A Resolved in 3.1(3c)A

CSCvd91302 UCS Mini and the Fabric Interconnect may loose connection after a change in the MTU value in BM and DQ. Reload the fabric interconnect. 3.1(1e)A Resolved in 3.1(3b)A, 3.1(2h)A

CSCva31113 After a fabric interconnect reboot, a file system corruption may occur on systems that contain an Indilinx controller. In most cases the underlying file system corruption can be fixed by booting into the kickstart image and running a file system check. A pre-upgrade package containing a script and a kernel module was developed for 62xx Fabric Interconnects running 2.2(x) firmware to ensure proper SSD shutdown prior to the reboot required during the upgrade process. With this deployed, the risk to run into a file system corruption issue during reboot is reduced, however not eliminated. There is no guaranteed preventative workaround. Although corruption may still occur, it is recommended to use the pre-upgrade package to send proper SSD shutdown commands prior to reboot. Please contact Cisco TAC for assistance with recovery or the pre-upgrade script. Note The pre-upgrade script will NOT work on 61xx FIs or 2.1(x) UCS firmware. 2.1(1a)A Resolved in 3.1(2h)A, 3.1(3b)A

CSCuv43292 The fabric interconnect may crash due to a sleeping function called within an interrupt context. There is no known workaround. Both 2.2(4a) and 2.2(5a) are affected but not 2.2(6), 2.2(7), and 2.2(8). Resolved in 3.1(2h)A

CSCvd54116 Setting a custom cipher suite for UCSM may result in a "handshake failure" error message when attempting to open a Java login to UCSM or a KVM session to a blade server. Explicitly allow AES128-SHA in the custom cipher to allow login to UCS Manager. This only affects the UCS Manager Java GUI. 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 3.1(2h)A

CSCvb14641 Power policies may be out of synchronization between UCS Manager and CMC after the master IOM is rebooted. Force a PSU redundancy config deployment from UCS Manager then flip the policy to GRID and back. 3.0(2c)A Resolved in 3.1(2h)A, 3.1(3a)A

CSCvb61558 UCSB-PSU-2500ACDV may display incorrect power readings in the PSMI register. There is no known workaround. 3.1(1e)A Resolved in 3.1(2h)A

CSCvb92941 UCS-IOM-2304 may fail to capture kernel cores in the obfl_raw partition. There is no known workaround. 3.1(1e)A Resolved in 3.1(2h)A

CSCvd93200 A random reboot due to a spinlock lockup may occur on Cisco UCS 2304. There is no known workaround. 3.1(1e)A Resolved in 3.1(2h)A

CSCva89402 An incorrect fault may be generated in UCS Manager when the power supply input source shows "unknown". There is no known workaround. 3.1(1e)B Resolved in 3.1(2h)B

CSCvc99135 The UCS Fabric Interconnect generates IGMP proxy reports where the source mac address of the data packets is replaced by the Fabric Interconnect, but the IP address is still the same as the VM. The data packets reach the upstream switch with the same IP address. This creates multiple entries in the IP-mac table for the IP in the uplink switch, which results in end point movement. There is no known workaround. 3.1(1e)B Resolved in 3.1(3a)B

CSCvd71484 The 6332 Fabric Interconnect input error counter may display a very high value for the port-channel interface. When this issue occurs, do one of the following: Clear the counters by using the NxOS CLI command clear counters

Ignore the Input Error Count on the port-channel and use the Input Error Count(s) of the members of the port-channel. 3.1(1e)A

CSCvd24782 When the poweroff module is available for less than 15 seconds, all of the poweron commands time out. The poweroff module <module_number> is then seen in the list of installed features on the FI through NXOS: version 5.2(3)N2(2.27b) feature fcoe poweroff module 4 The module appears to no longer work after it reboots. When this issue occurs, do the following: Contact TAC to load the debug plugin and power the module on manually Reboot the FI 3.1(1e)A Resolved in 3.1(3a)A

CSCvb93384 When running the vnic placement tests through multiple iterations, the HIF port may intermittently encounter an error. The port auto recovery mechanism should be enabled. If any HIF port encountered the error-disabled state, the port should automatically recover in 60 seconds. 3.1(1e)B

CSCvd42163 During a Fabric Interconnect upgrade or reload, the following error may occur. ERROR: bootflash: has unrecoverable error; please do "format bootflash:" There is no known workaround. 3.1(1e)A Resolved in 3.1(2g)A

CSCvd20170 A Cisco UCS Manager power group change implemented through the HTML5 GUI may show 0W for a blade server in the chassis. Perform the power group change through the Java GUI or CLI. 3.1(1e)A Resolved in 3.1(2g)A

CSCvc02297 The power cap application may fail for a Bladeserver when the server is powered on or off from outside of Cisco UCS Manager. The fault can be ignored. During the maintenance window, shutdown the Bladeserver from the OS and power on the server from the UCS Manager GUI or CLI. 3.1(1e)A Resolved in 3.1(2g)A

CSCvb79455 The critical fault code F1000227 may occur on both the primary and subordinate FI during upgrade. This issue can occur when the expansion module from the FI was removed. Reinsert the GEM card back to the previous slot. 3.1(1e)A Resolved in 3.1(2g)A

CSCvc05615 FI-6396UP with FC 16G interfaces (individual/port-channel) may incorrectly report discard frame count. The issue was a cosmetic one where-in the discard count (both input and output) used to increase every few minutes. The interfaces themselves are not impacted and remain up. There is no known workaround. 3.1(1e)A Resolved in 3.1(2g)A

CSCvc46313 The remote operation of making the LUN online from UCS Central may fail with the error message: Global Service profile [org-root/org-GKDC/org-<name>/ls-SP_3260_03] can not be modified from UCS domain. Please make the changes from UCS Central that you are registered with. Contact Cisco TAC for a workaround. 2.2(4b)A Resolved in 3.1(2f)A

CSCva14937 M4 blades installed with SD cards instead of a hard disk may halt at 'Local Drive' for automated deployments with the following boot policy: Boot Policy CD/DVD

Local Drive

Network Adapter (PXE) There is no known workaround. 2.2(3f)B Resolved in 3.1(2f)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 and downgrade procedures. 2.2(7b)A Resolved in 3.1(2f)A

CSCvb22090 During a disk firmware upgrade, when an unconfigured bad drive is encountered, the upgrade may stop and the remaining drives on the UCS Rack server are not updated. There is no known workaround. Verify that all the hard drives are setup correctly before the firmware update. 2.2(3a)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 3.1(2f)A

CSCvc10791 A DME process may crash when the dynamic vNIC and static vNIC contain a different adminVcon property value. Collect UCS Manager tech support logs from the local-mgmt CLI and contact TAC. connect local-mgmt show tech-support ucsm detail 2.2(3e)A Resolved in 3.1(2f)A

CSCvc14810 Systems with 6300 Fabric Interconnects and Windows Server 2012 virtual machines may experience intermittent packet loss due to missing VLAN translate entries. Contact TAC for a temporary workaround. A permanent fix is only available for UCS Manager version 3.1(2f) or higher. 3.1(1e)A Resolved in 3.1(2f)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 3.1(2f)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 3.1(2f)B

CSCvc46313 Remote operation from UCS Central no longer fails with the error message: Global Service profile [org-root/org-GKDC/org-<name>/ls-SP_3260_03] can not be modified from UCS domain. Please make the changes from UCS Central that you are registered with. Workaround: There is no known workaround. Contact TAC for assistance. 2.2(4b)A Resolved in 3.1(2f)A

CSCvc60876 The 6248, 6296, and 6332 Series Fabric Interconnect 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 3.1(2f)A

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 3.1(2f)A

CSCva71801 UCS Manager may fail to synchronize with the IPv6 NTP server. If possible, drop into the debug plugin. Restart the process ntpd by issuing the command: killall ntpd Or change the IPv6 NTP server to a IPv4 NTP server. 2.2(8a)A Resolved in 3.1(1l) A

CSCuy52691 After upgrading to Cisco UCS Manager Release 3.1(1e), the blade server may fail to power on with the following fault: Description: Insufficient power available to power-on server x/y Affected Object: sys/chassis-x/blade-y/budget Name: Power Budget Power Budget Unavailable Change the power control policy in Service Profile to "cap" with a default priority value of "5". 3.1(1e)A Resolved in 3.1(1l) A

CSCuu99255 The "show fabric-interconnect inventory expand" command may display the ethernet port with a role of “Unknown” instead of "Server". The role can be recovered by disabling and enabling the port. 2.1(1a)A Resolved in 3.1(1l) 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. 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 3.1(1l)A, 3.1(2b)A

CSCvb18143 ACL Fabric Manager core maybe seen during Cisco UCS Manager upgrade or downgrade to 3.1(1l) or higher. There is no known workaround. 2.2(8c)A Resolved in 3.1(1l)A, 3.1(2b)A

CSCuz53730 Under heavy load on httpd, either from API, Cisco UCS Central and/or Cisco UCS Manager sessions, Cisco UCS Manager httpd process may experience high memory usage or crash with a core file showing indications of memory allocation failure. If the issue is encountered, memory usage can be minimised by: Reducing the volume of simultaneous requests to HTTPD by API polling and open UCSM sessions. Resolving UCS Manager faults (large numbers can cause increased memory usage).

UCSM will automatically restart process until it reaches failure threshold (typically 4). After that, it is advised to failover to the subordinate FI and either reboot or restart management on the previous primary. 2.2(2c)A Resolved in 3.1(1l)A

CSCul97240 When a UCS rack server is present in a UCS setup, DHCP renewal may trigger Information level syslog messages to be sent to the syslog server configured on Cisco UCS Manager. There is no known workaround. 2.2(1a)A Resolved in 3.1(1l)A

CSCva56277 During downgrade of Cisco UCS Manager A bundle, the slots 3 and 4 in the fabric interconnect may be reported as powered off. There is no known workaround. 2.2(3a)A Resolved in 3.1(1l)A

CSCva85907 During discovery of Cisco UCS C240 M4 server with Intel x520, Emulex 11102, and Qlogic 844 converged network adapters, the Intel X520 adapter may revert to old firmware after a successful host firmware package (HFP) update. There is no known workaround. 3.1(1e)A Resolved in 3.1(1l)A, 3.1(2b)A

CSCva38476 An infrastructure software upgrade to UCS Manager 2.2(7b) or higher may fail when both fabric interconnects are incompatible or when one of the fabric interconnects is unresponsive. If you encounter this issue, contact TAC to apply a workaround. 2.2(7b)A Resolved in 3.1(1l)A

CSCva34343 Cisco UCS Manager may report false alerts due to P0V75_STBY sensor in Cisco B200 and M4 Blade Servers. There is no known workaround. 2.2(6e)B Resolved in 3.1(1l)B

CSCuz21644 When Internet Explorer 11 browser is used to download the license file through Cisco UCS Manager Admin > License Management > Download tasks > Download license file > Local File System, the local file system may fail. If you encounter this issue, try using the Chrome browser as a workaround. 3.1(1e)A Resolved in 3.1(1l)A

CSCva27558 In scenarios such as traffic loops in external networks, a series of MAC add or delete operations may cause the MAC address to display in the software table, and not 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 3.1(1l)A, 3.1(2b)A

CSCva61701 When the Cisco UCS fabric interconnect uplinks are in the individual (" I ") state, broadcast traffic received on one interface may be sent back upstream on the other interfaces. Set the "suspend individual" value to True in the LACP network policy. This will make sure that the port is suspended (s state) instead of individual (I state). 3.1(1e)A Resolved in 3.1(1l)A, 3.1(2b)A

CSCva73387 The SNMP process may crash and cause the fabric interconnects to reload when DNS is configured on the fabric interconnects and SNMP trap hosts are configured with domain names. There is no known workaround. 3.1(1e)A Resolved in 3.1(1l)A, 3.1(2b)A

CSCvb11667 Cisco UCS B200 Blade Servers with UEFI BIOS enabled, may fail to SAN boot from a target LUN with an ID other than 0 and using T10 DIF protection. If this issue occurs, you can set the BIOS to legacy mode or use LUN ID 0. 2.2(8d)B Resolved in 3.1(2e)B

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 3.1(2e)A, 3.1(1l)A

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 3.1(1l)A, 3.1(2e)A

CSCvb77811 Fault codes F0369 and F0391 may randomly appear on Cisco UCS 5108 Blade Servers and UCS 2200 Fabric Extenders. Remove a PSU from the chassis, so that chassis doesn't have extra PSUs to turn off or on. You can also ignore the fault. This won't affect functionality as long as the chassis power consumption does not exceed 5000w. 3.1(1e)A Resolved in 3.1(2e)A

CSCvb85544 A race condition in the Linux kernel's memory subsystem that handled the copy-on-write (COW) of read-only memory mappings may occur on fabric interconnects. There is no known workaround. 2.2(1a)A Resolved in 3.1(2e)A, 3.1(1l)A

CSCvc17769 The fabric interconnect no longer crashes when the bound interface of Veth is in the "Not Initialized State" during a VLAN configuration change. If the bound intf of Veth is in not initialized, do not perform a VLAN configuration change on the Veth. 2.2(7c)A Resolved in 3.1(2e)A, 3.1(1l)A

CSCvb82862 EUI-64 bit addresses were invalid when entered for storage connection policies or SAN boot targets. There is no known workaround. 2.2(8d)A Resolved in 3.1(2e)A, 3.1(1l)A

CSCuw50361 While collecting IOM tech-support by using the command "show platform software satctrl global", the HIF/NIF interfaces of an IOM no longer flap due to SDP heartbeat timeout. If you have encountered this SDP timeout during tech-support collection, take the following actions for any subsequent tech-support on the chassis that had been impacted: If troubleshooting a blade or host level issue, specify the exact blade in question to only collect the Cisco IMC and adapter logs. Note: The default chassis selection of "CIMC ID: all" will collect IOM logs as well.

If troubleshooting an IOM level issue, TAC can perform a workaround by removing the impacting command "show platform software fwmctrl trace" from the IOM tech-support generation. Contact TAC for additional assistance. 2.2(4b)A Resolved in 3.1(2e)A, 3.1(1l)A

CSCvb78971 When attempting the auto-install of UCS Manager, the fabric interconnect upgrade may fail when the /var/tmp usage exceeds 10%. There is no known workaround. 2.2(3k)A Resolved in 3.1(2e)A, 3.1(1l)A

CSCvb50641 UCS Mini backplane port may go down after firmware check fails. Option 1: At the NxOS command prompt enter: test hardware internal mtc-usd load_ucode front-port X where X is the port number.

Option 2: For the affected interface, at the NxOS command prompt enter: shut ; no shut ;

Option 3: Reboot Fabric Interconnect 3.1(1e)A Resolved in 3.1(2e)A

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 powers off unexpectedly. The OBFL displays the following log message: [platform_power_state_irq_handler]:18:VDD_PWR_GOOD: Deasserted If this issue occurs, upgrade the infrastructure and server firmware to Cisco UCS Manager Release 3.1(1g) or later releases. Note Both infrastructure and server firmware must be upgraded. If the server firmware is upgraded to a fixed release earlier than the infrastructure firmware, do one of the following after the infrastructure firmware is upgraded to the fixed release. Re-acknowledge the server

Decommission and then acknowledge the server This is required for the correct server firmware component to upgrade and prevent the issue. 3.1(1e)B

CSCux68195 VMware ESXi crash (Purple Screen of Death) during certain operations while running VM FEX. The following are possible workarounds: Delay the upgrade to Cisco UCS Manager 3.1 until the issue is resolved

Undeploy VM FEX and instead deploy VMware. See the Software Advisory. 2.2(6c)A

CSCux52184 If you use GLC-T optics for 1G port connections on port 1-16 might not link up on UCS 6332 16UP FI Use SFP-SX and SFP-T optics for 1G connectivity on port 1-16. 3.1(1e)A

CSCux48594 When you upgrade Cisco UCS Manager from release 2.5(2a) to 3.1, you will see DME core. You need not take any action when you see DME core. The upgrade process will continue and complete successfully. 3.1(1e)A

CSCux38896 After you reboot the fabric interconnect in Cisco UCS Mini, the FC port in F mode might not come up. The following are possible workarounds: Check with the storage vendor if the software version you are using will perform a FLOGI re-try if the first FLOGI fails. If not, ask the vendor for a software version that does FLOGI re-try and update the storage to that version.(Recommended)

Flap the FC port on Cisco UCS Mini. (not recommended) 3.0(2d)A

CSCux35642 When you modify any QoS policies such as queuing or scheduling or MTU on an active system, the server discovery fails. Reboot the FI and IOMs after any change to the QoS policy or MTU. 3.1(1e)A Resolved 3.1(1g)A

CSCuv46749 If you have Cisco UCS Blade servers B200 M4, B420 M4, B260 M4, B460 M4 in your environment, you will see random, transient critical faults with information such as 'Device reported corrupt data', when there are no data corruption. These faults automatically clear in 30 or 40 seconds. 2.2(3g)A

CSCux70749 When you update any driver using -ivh driver_name.rpm, kernel warnings about an unknown symbol used by an Internal Graphics Device (IGD) can be caused. This is seen for the following configurations: Cisco UCS M142 Compute Cartridge with Intel Xeon Processor CPU 1265L v2

Cisco UCS M1414 Compute Cartridge with Intel Xeon Processor CPU 1285L v2

Cisco UCS M1414 Compute Cartridge with Intel Xeon Processor CPU 1285 The kernel warnings have no impact overall on IGD functionality or overall health of the operating system. 3.1(1e)M

CSCux68398 In some cases, when you perform a hardware migration for the subordinate fabric interconnect (FI-B) from UCS 6296 UP FI to UCS 6332 16UP FI, you will not be able to create FC port on the latter. This will happen if the migration is performed in the following order: Launch Cisco UCS Manager GUI (Java or HTML) on a system with two UCS 6296 UP FIs. Begin hardware migration for the subordinate UCS 6296 UP FI to UCS 6332-16UP FI. Begin configuring FC ports using the session of Cisco UCS Manager GUI launched before migration. To avoid this issue, do the following: After the migration on FI-B is complete, exit the session of Cisco UCS Manager GUI.

Re-launch a new session of the same GUI to configure FC ports on UCS 6332 16UP FI. 3.1(1e)A

CSCux65310 In some cases, during blade Cisco IMC controller reboot, a chassis thermal fault may generate due to long reconnect from the IOM to the Cisco IMC. This fault will automatically clear by itself. 3.1(1e)A Resolved in 3.1(1g)A

CSCux64421 The Cisco UCS M4308 Modular Chassis fans may run at higher than expected speeds. This occurs when a host on a cartridge fails to complete BIOS POST within the expected interval. The fan speed returns to normal after the host completes BIOS POST, or if the host is powered off. 3.1(1e)M

CSCup09193 When equal cost multiple uplinks (FC/FCoE) to the same adjacent switch or to different adjacent switches using which same remote domain can be reached, you will see one of the following issues: All uplinks except one does not come up.

In case more than one uplinks come up, you will see traffic disruptions and IO timeouts. To avoid this issue do not use equal cost multipaths at any point of time. If you need multiple individual links to the same switch, you can add all of the ports to a port-channel. 3.1(1e)A

CSCuz46574 As a result of power-up, power-down, portgroup change, or vmotion, after a VM changes its pinning, the MAC address of that VM does not get removed immediately from the MAC address table of the Cisco UCS 6332 FI to which it was earlier pinned. This happens when the uplink is port-channel. To avoid this issue, do one of the following: Use individual uplinks, and not port channels.

Use Fabric Failover based vNIC rather than OS teaming/failover. If the above is not possible: Configure port groups on VMWare to have VM traffic pinned only to one side If this issue occurs, do one of the following: Use the "clear mac address dynamic address xxxx.xxxx.xxxx" command to clear the MAC from the FI

Flap the uplink port-channel to clear stale macs on that FI 3.1(1e)A Resolved 3.1(1h)A

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. 3.1(1e)A Resolved in 3.1(1h)A

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 workaround. 3.1(1e)B Resolved in 3.1(1h)A

CSCuz67284 When installing the ESXi 5.5 U2 custom ISO to FlexFLash, the partedUtil fails with the following error message: “Can't have a partition outside the disk! Unable to read partition table for device." Scrub the FlexFlash drives to install the ISO without any issues. 2.2(3d)

CSCuz46847 After IOM reset on chassis, Cisco UCS Manager may raise a fault, 'chassis major power error'. Chassis may seem to be in an inoperable state, however chassis is fully operable. Reacknowledge the affected IOMs to resolve the issue. 3.1(1e)A

CSCuz55693 When you attempt to reset memory errors using ucs-fi chassis/server # reset-all-memory-errors , Cisco UCS Manager may generate a 'Managed object does not exist' error. The command will work after you decommission the new blade and reacknowledge it. 3.1(1e)A Resolved in 3.1(1k)A

CSCuz08759 vniccfgd process crashes when downgrading VIC firmware to version 4.1(1d). Activate the VIC adapter firmware backup image, whose version matches Cisco UCS Manger, which was installed before the downgrade. 3.1(1e)C Resolved in 3.1(1k)C

CSCuy35745 When upgrading or downgrading a Unified Ports Capable 3rd Generation Fabric Interconnect, the upgrade or downgrade process fails with the following error message: "less space in /var/sysmgr" To resolve the issue follow the steps below: Load the debug plugin and get to the linux prompt on the fabric interconnect.

Delete the file "/var/sysmgr/tibctrl.debug".

Try the upgrade or downgrade process again. Note The system is up and running for a long time.

There are lots of QoS configuration changes.

There are lots of flaps on ports 1/1-16. The error could happen only on Unified Ports Capable 3rd Generation Fabric Interconnect. Additionally one of the following conditions need to be satisfied: 3.1(1e)A Resolved in 3.1(1k)A

CSCux62816 When any IPMI user attribute (except IPMI user password) is modified, it blocks authentication for the IPMI user and fails all the related operations that need authentication. User is unable to login, inject UC ECC error, or perform IPMI related operations with the IPMI tool. Set the IPMI user password again. 3.1(1e)A Resolved in 3.1(1k)A

CSCva17185 Under rare circumstances, 3 1/2-inch Seagate drives might fail when accessed after a long idle period, as the lubrication under the read head can become depleted. This problem only impacts C-series Unified Computing Systems (UCS's) with the following PID's: UCS-HDD1TI2F212

UCS-HDD2TI2F213

UCS-HDD3TI2F214

UCS-HD4T7KS3-E

UCSC-C3X60-HD4T

UCS-HD4TBK9

UCS-HD4TBK9" No known workaround. 2.2(3a)B

CSCuy52691 After upgrading Cisco UCS Manager to release 3.1(1e), changes to the maximum power allocated can prevent the blade server from powering on, with the following faults: Description: Insufficient power available to power-on server x/y Affected Object: sys/chassis-x/blade-y/budget Name: Power Budget Power Budget Unavailable Description: [FSM:STAGE:RETRY:]: Check if power can be allocated to server x/y(FSM-STAGE:sam:dme:ComputeBladeDiscover:CheckPowerAvailability) Affected Object: sys/chassis-x/blade-yName: Fsm Sam Dme Compute Blade Discover Cause: Check Power Availability Failed If this issue occurs, do the one of the following Change the power control policy in Service Profile to "cap" with default priority value of "5".

Change PSU power policy to N+1 from GRID. 3.1(1e)A Resolved in 3.1(2b)A

CSCva09070 Some Cisco UCS Manager pages have the 'X-Frame option is missing' in the http message header which may result in click-jacking. No known workaround 3.1(1e)A Resolved in 3.1(1k)

CSCva19523 When the Peer Fabric Interconnect is down, the server discovery FSM is stuck with the following message: detect mezz cards in 1/1 (FSM-STAGE:sam:dme:ComputeBladeDiscover: NicPresencePeer) Bring up the Peer Fabric Interconnect. 3.1(1e)A Resolved in 3.1(1k)

CSCva61701 When the Cisco UCS FI uplinks are in the individual (" I ") state, broadcast traffic received on one interface is sent back upstream on the other interfaces. Set the suspend individual value to True in the LACP network policy. This makes sure that the port is suspended (" S " state) instead of individual (" I" state). 3.1(1e)A Resolved in 3.1(2b)A

CSCuu24614 FC port channel gets deleted when Cisco UCS Manager perceives a speed difference between the port and port channel. Check if the port speed matches the port channel speed, before adding the port to the port channel. In case of replacing SFP, remove the port from port channel, and then replace the SFP. Note Recheck to make sure that the port speed matches the port channel speed. 3.1(1e)A Resolved in 3.1(2b)A

CSCva47085 When using VIC1340 with 2304 IOM Native 40G backplane connection (not 4x10G), LUNs disconnect or failure occurs during FC/FCOE reboot. In the VMware vmkernel log the following message may be seen: 2016-06-21T04:32:36.106Z cpu25:33191)<3>fnic : 2 :: hdr status = FCPIO_DATA_CNT_MISMATCH In the VIC adapter log the following message may be seen: 160621-04:26:51.733255 ecom.ecom_main ecom(8:3): ox_id 41d4 rx_id 44b seq_cnt 7 seq_id 1 160621-04:26:52.066235 ecom.ecom_main ecom(8:1): fcpio_data_cnt_mismatch for exch 4202 status 1 rx_id 5f7 s_stat 0x3 xmit_recvd 0x3000 burst_offset 0x3000 sgl_err 0x0 last_param 0x2800 last_seq_cnt 0x0 tot_bytes_exp 0x8000 h_seq_cnt 0x5 exch_type 0x0 s_id 0xab800 d_id 0xab800 host_tag 0x377 Non-stomped CRC is observed coming from the IOM to adapter. The following messages may be seen in the Cisco UCS Manager CLI: connect adapter x/x/x attach-mcp dcem-macstats 0 <- check for "Rx CRC error frames not stomped" dcem-macstats 1 <- check for "Rx CRC error frames not stomped" If this issue occurs do one of the following: With VIC1340 use 4x10G only, by removing the port expander.

Use the VIC1380 adapter only. 3.1(1e)A Resolved in 3.1(2b)A

CSCuy13596 During OS installation on Cisco UCS C3260 System running Cisco VIC firmware 4.1(1d) and CMC firmware 2.0(9d), the installer fails when creating partitions or writing to LUNs. No known workaround. 3.1(1e)B 3.1(2b) A

CSCvf34463 When PXE installation is attempted on 16 or more servers at the same time, in a system with only one FI-IOM fabric link, more than two chassis with eight servers each, and more than six vNICs in a single chassis, the installation fails on a few servers. Manually reboot the servers on which PXE installation failed. 3.1(1e)A