Release Notes for Cisco UCS Manager, Release 1.3(1)
Available Languages
Table of Contents
Release Notes for Cisco UCS Manager, Release 1.3(1)
Hardware and Software Interoperability
Known Limitations and Behaviors
Caveats from Previous Releases
New Hardware Features in Release 1.3(1)
New Software Features in Release 1.3(1)
Release Notes for Cisco UCS Manager, Release 1.3(1)
First Published: June 9, 2010
Last Updated: May 16, 2014
Part Number: OL-22863-01This document describes the new features, system requirements, and caveats for Cisco UCS Manager, Release 1.3(1c), Release 1.3(1i), Release 1.3(1m), Release 1.3(1n), Release 1.3(1o), Release 1.3(1p), Release 1.3(1q), Release 1.3(1t), Release 1.3(1y),and all related firmware and BIOSes on blade servers and other Unified Computing System components associated with that release. Use this document with the documents listed in the “Related Documentation” section.
Note We sometimes update the documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates. Documentation updates and errata are also in these release notes. The documentation roadmap for this product is available at: http://www.cisco.com/go/unifiedcomputing/b-series-doc
Table 1 shows the online change history for this document.
Contents
This document includes the following sections:
- “Introduction” section
- “System Requirements” section
- “Updating Cisco UCS Versions” section
- “Hardware and Software Interoperability” section
- “Resolved Caveats” section
- “Open Caveats” section
- “New Hardware Features in Release 1.3(1)” section
- “New Software Features in Release 1.3(1)” section
- “Related Documentation” section
- “This document is to be used in conjunction with the documents listed in the “Related Documentation” section.” section
Introduction
The Cisco Unified Computing System is a next-generation data center platform that unites compute, network, storage access, and virtualization into a cohesive system designed to reduce total cost of ownership (TCO) and increase business agility. The system integrates a low-latency, lossless 10-Gigabit Ethernet unified network fabric with enterprise-class, x86-architecture servers. The system is an integrated, scalable, multi-chassis platform in which all resources participate in a unified management domain.
System Requirements
Cisco UCS Manager must meet or exceed the following minimum system requirements:
- The Cisco UCS Manager GUI is a Java-based application that requires Sun JRE 1.6 or later.
- UCS Manager uses web start and supports the following web browsers:
–
Microsoft Internet Explorer 6.0 or higher
Updating Cisco UCS Versions
Customers upgrading their Cisco UCS system from version 1.0.2 to version 1.3.1 might experience UCSM activation failures due to the depletion of compact flash memory space.
To avoid this issue, complete the following steps prior to starting the 1.3.1 firmware upgrade:
Step 1
For example, to download the ucs-dplug-upgrade.4.0.1aN2.1.2l.gbin binary file using the SCP protocol, issue the following commands:
#(local-mgmt)# copy scp://<user>@<ipaddress>/<path>/ucs-dplug-upgrade.4.0.1a.N2.1.2l.gbin volatile:xStep 2
Note If you encounter an error while completing the debug operation, contact Cisco TAC for further assistance.
To update the Cisco UCS software and firmware, see the appropriate Upgrading Cisco UCS document for your installation.
Use the scope firmware and show package filename expand CLI commands to view the contents of a given release package.
Table 2 shows the package contents for UCSM Release 1.3(1).
Hardware and Software Interoperability
For detailed information about storage switch, operating system, adapter, adapter utility, and storage array interoperability, see the Hardware and Software Interoperability Matrix for this release , located at:
http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_list.html
Note VMware ESX and ESXi 3.5 Update 4, and ESX and ESXi 4.0 are not compatible with Intel 56xx processors. 55xx processors are not affected by this limitation. See the interoperability matrix for this release for OS and other support questions.
Internal Dependencies
Table 3 shows interdependencies between UCS hardware and versions of Cisco UCS Manager. Server FRU items like DIMMs are dependent on their server type, and chassis items like fans and power supplies work with all versions of UCS Manager.
Caution You cannot mix component software versions (for example, you cannot have a B200 using the 1.0(1) BIOS with a UCS M81KR adapter running 1.0(2) firmware managed by UCS Manager 1.3(1)). Compare the minimum software version for all your components and use at least the latest of all the versions, or use the most current version of software for all components. Mixing M1 and M2 hardware versions is not an issue if they are running software at a version matching the other system components.
UCS NIC M51KR-B
UCS CNA M61KR-I 1
UCS CNA M72KR-Q
UCS CNA M72KR-ESFP-10G-SR, SFP-10G-LR
SFP-H10GB-CU1M
SFP-H10GB-CU3M
SFP-H10GB-CU5MCapability Catalog
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 UCS Manager. The latest posted 1.x catalog will work with any posted 1.3 or 1.4 release. If as a server component is not dependent on a specific BIOS version, using it and having it recognized by UCS Manager is primarily a function of the catalog version.
Note Cisco UCS Manager 1.x releases will work with any 1.x catalog file, but not the 2.0 catalog versions.
The catalog is available in UCS Manager software bundles. See Table 4 for details.
For more details, see the Cisco UCS Manager GUI Configuration Guide .
Known Limitations and Behaviors
The following known limitations in Release 1.3(1) are not otherwise documented:
- With the B-250 blade server, the displayed ESX and Linux OS HDD Boot Device Order is the reverse of the BIOS HDD Boot Order. To rectify this issue, review both the disks (and drive labels as applicable), during installations of ESX and Linux versions and choose the correct disk for installation.
- Only ports 1/1 through 1/8 on the 6120 Fabric Interconnect and 1/1 to 1/16 on the 6140 Fabric Interconnect can be configured to use 1-GB transceivers (GLC-T, GLC-SX-MM, and GLC-LH-SM). Auto-negotiation is not supported for this change, you will need to set the speed manually in Cisco UCS Manager. All member ports of a port channel must use these ports running at the same speed, so if you need to have one member port using a 1-GB port, all other members will have to change as well.
- The maximum VLAN-Port-Limit is 3000, which was not the case for previous versions. If you try to add more VLANs through service profiles, the service profile association will fail.
- Even with the Protect Configuration Flag set to Enabled, user data may not be protected during a UCS upgrade from Release 1.2(1) or earlier builds to Release 1.3(1i) for unassociated servers, the first time the servers get associated under 1.3(1i), the ProtectConfig Property (even if ProtectConfig=YES) will not protect the user data as the association will proceed without the configuration errors. Note that the subsequent associations would be blocked if the ProtectConfig = YES and the Local Disk Configuration Policy mismatches. Associated servers will not reboot and no configuration errors will be reported.
- The Protect Configuration Flag was introduced in 1.3(1c) and so after the upgrade, this flag is Enabled in the Local Disk Policy as the default. If there is no mismatch between the Local Disk Policy of the previous SP to the incoming SP, the association should go through. Make sure that there is no mismatch; otherwise, a configuration error will be reported and association will fail.
To manually disable the Protect Config Flag (only do this if you do not care about the data in the disk) to prevent the configuration errors and allow the service profile association to go through, follow these steps:
a.
Select the service profile that you will be using to associate to the server.
b.
c.
d.
Documentation Errata
In Cisco UCS Manager Command Reference 1.3(1) guide, we incorrectly stated that the range of valid values for the service profile name is 1 to 16. The correct statement is "This name can be between 2 and 32 alphanumeric characters long. You cannot use spaces or any special characters, and you cannot change this name after the object has been saved.” The next version of this book will include the correct information.
In Cisco UCS Manager Command Reference 1.3(1) guide, and prior versions, we incorrectly stated that the range of valid values for the SNMP community name is 1 to 512. We also stated that the community name string can be entered multiple times to create multiple community strings. The correct statement is "This name can be between 1 and 32 alphanumeric characters long." Also, you can create only one community string. The next version of this book will include the correct information.
Resolved Caveats
The following caveats are resolved in the 1.3(1y) release:
- If an active PSU is putting out no 12 volt current the software detects it as expected. (CSCto48803)
- The B250 M1/M2 blade will support Board Controller upgrade. (CSCtw70911)
- A B250 which make use of the DDR3 voltage regulator will no longer see uncorrectable ECC errors in logs with no DIMMs mapped out on reboot. (CSCtu01217)
The following caveats are resolved in the 1.3(1w) release:
- A protection algorithm was implemented to prevent damage in case of power transistor failure. (CSCtr05373)
The following caveats are resolved in the 1.3(1t) release:
- Invalid FRU faults are no longer generated during image upgrades and other UCS Manager operations. (CSCtn49395)
- On a B250-M2 server with all DIMM slots filled, some slots no longer intermittently fail to be recognized, requiring a power cycle to clear the problem. (CSCtn51001 and CSCtk63217)
- When a non-default Cisco UCS Manager capability catalog is installed, the catalog will now display multiple PID mapping for DIMM entries where applicable. (CSCtn47841)
- An XML request to retrieve a full hierarchical managed object tree will no longer cause httpd to crash. (CSCtn85446)
The following caveats are resolved in the 1.3(1q) release:
- When the IP MIB and the VLAN Membership MIB are being queried simultaneously, the fabric interconnect no longer crashes and produces a core file. (CSCtl08147)
- A UCS server with an M81KR adapter will now PXE boot with option 67 as expected. (CSCtl91488)
- When upgrading UCS Manager and fabric interconnect firmware, a core file is no longer generated. (CSCtl05066)
- The option to set startup version only mode for UCS Manager is now disabled. (CSCtj80887)
The following caveats are resolved in the 1.3(1p) release:
- A UCS B250-M2 with all low voltage DIMMs can now set the memory bus frequency to 1333 MHz if the BIOS Low Voltage DDR mode is set to performance mode and all of the hardware requirements are met. (CSCtj80122)
- If the CPUID of the installed CPU is 206C2, a system hang, reboot or memory ECC errors will no longer occur when exiting the package C6 state after updating the BIOS to the 1.3(1p) version. (CSCtj38908)
- ESXi boot up no longer hangs at Initializing Scheduler. (CSCtj19224)
- Remote authentication no longer fails when there are simultaneous logins. (CSCtk46727)
- A fabric extender can now report the correct reason for a reset if the reset is caused by a power level going out of tolerance. (CSCtj13227)
- After upgrading Cisco UCS 2104XP Fabric Extender firmware version to 1.3(1p), the fabric extender Status LED no longer stays amber after bootup. (CSCtk00601)
- Installed DIMMs are enabled following a reset even if this reset occurs shortly after the blade is powered up. (CSCtk63217)
The following caveats are resolved in the 1.3(1o) release:
- (CSCtf11600) UCS Manager GUI allows the kickstart and system images to be different and incompatible but will now warn users of the mismatch.
- (CSCti08803 and CSCtg88258) UCS Manager no longer gives false critical temperature warnings.
- (CSCti55763) UCS Manager now shows thermal statistics for both active and standby fabric extenders.
- (CSCtg90611) UCS Manager now clears IOM thermal faults correctly.
The following caveats are resolved in the 1.3(1n) release:
- (CSCth36056) Blade server no longer hangs at the initial bootup window after a soft reset is issued using RHEL 5.5.
- (CSCth93217) On a B200-M2 with Low Voltage DIMM and CPU, misleading amber LEDs and SEL messages no longer occur.
- (CSCth58897) During soft reset from an OS which uses port 0x64 to reboot (like SLES10), the CPU no longer reports erroneous uncorrectable memory errors.
- (CSCti35405) While processing a large number of requests (over 10,000) the LDAP Client daemon will continue processing authentication requests and not drop them. LDAP Users will be able to login to UCSM.
- (CSCth94504) Just after a firmware upgrade or other action that results in a reboot of an IOM the IOM boot sequence will no longer fail to connect to the second mezzanine card in a full-width blade.
The following caveats are resolved in the 1.3(1m) release:
- (CSCti06905) Fabric Interconnects now join together as expected after a failover.
- (CSCth89274) The fabric interconnect no longer sends both an SNMP trap and a duplicate event inform.
- (CSCth85238) Resolved a memory leak that caused a security daemon crash under a stress condition. This problem was present in UCS Manager versions 1.2 (1d) to 1.3(1i).
- (CSCth82651) If the system has been configured to be run in low voltage DIMM mode, upper critical and/or upper non-recoverable threshold crossings are no longer be asserted by the BMC causing the system fault LED to inaccurately light up amber.
The following caveats are resolved in the 1.3(1i) release:
- (CSCth70776) When using M2 processors and Low Voltage DIMMs, spurious error log messages are no longer seen for P0V75_DDR3_P1 and P1V5_DDR3_P1.
- (CSCth32605) The B440 M1 platform no longer generates memory uncorrectable ECC errors and reboots the host during the PMEM memory test.
- (CSCth41426) A blade associated with an operational service-profile will no longer de-associate and re-associate if a change of the Protect Configuration feature is done in the Local Hard drive Policy linked to that service-profile.
- (CSCth31976) Systems no longer show a loss of SAN connectivity in the log of the server when a B250 blade has one Adapter populated in Slot-2.
- (CSCth68477) Upgrading to 1.3(1i) when using a Fabric Interconnect in a non-HA configuration no longer causes server BIOS and management controller upgrades to get stuck.
- (CSCth34925) Upgrading to 1.3(1i) when servers are associated and have M71KR-E or M71KR-Q adapters installed does not cause the servers to reboot after the upgrade completes.
- (CSCth30341) The bootloader code is no longer unable to read the boot configuration or version string information, causing the blade to improperly report failures during power up.
- (CSCth53469) UCS Fabric Interconnect will no longer send an IGMP proxy report with a source address of 0.0.0.0.
- (CSCth42135) After reacknowledging the blade, thresholds are no longer changed back to pre-upgrade thresholds.
- (CSCtg34032) A B250 blade with 2 X5570 CPUs no longer shows low voltage errors.
- (CSCtd37817) Correctable DIMM errors are no longer reported in UCS Manager as "Degraded.”
- (CSCth12613) In a setup with a large number of Virtual interfaces in end-host mode, when the last border port goes down, the host interface physical ports for adapters no longer flap.
- (CSCth05961) In a UCS system with VMware ESX installed on many blades with M81KR adapters and using Hardware VN-Link, a high number of dynamic vNICs provisioned in service profiles with "protected" attribute enabled, and a high number of VMs using dynamic vethernet interfaces in the fabric interconnect switches, ESX hosts no longer show up as "disconnected" in VMware Virtual Center, and VM interfaces or VMkernel interfaces no longer lose network connectivity.
The following caveats are resolved in the 1.3(1c) release:
Red Hat Linux
- (CSCte53336) You will no longer encounter a panic when traffic forwarding and LRO are enabled, with RHEL 5.4 - xen kernel.
- (CSCte11502) After upgrading to UCSM 1.3(1), network usage (for example, SCP, FTP, web browsing, etc.) no longer causes a kernel panic on the RHEL5.4 Xen kernel (2.6.18-164.el5xen). The workaround at http://kbase.redhat.com/faq/docs/DOC-23816 is no longer needed.
- (CSCtf73779) When ESX4i is installed on a UCS blade with a M81KR Adapter, or on a Fiber Channel LUN, or ESX4i is upgraded from Update1 to Update1 Patch03 or later, the Upgrade or Install of ESX4i or Cisco VEM module will no longer fail with the following error message:
Message - Bootbank preparation failed: /sbin/bootbankstage-install.sh -v prep returned (1) Errno - 17 Description - There was an error setting up ESXi installation destinationCisco UCS Manager
- (CSCtd59353) After moving a Mirrored RAID cluster from one blade to another blade, it fails to boot as it is considered a Foreign RAID in the new blade. With Release 1.3(1), the Foreign RAID will be converted into a Native RAID. Therefore, the 'Activate Array' procedure will not be necessary assuming that the Local Disk Configuration Policy in the new Service Profile is exactly the same as the Local disk Configuration Policy that was defined in the original Service Profile before the RAID Cluster was moved.
- (CSCtc77623) The server OS on the server no longer ignores a soft shutdown request by UCS Manager.
- (CSCtd90460) If there are any changes to the LDAP hostname, it will now resolve in UCS Manager.
- (CSCte05392) The fault table behaves as expected when SEL logs are cleared.
- (CSCte36910) Keyboard strokes pressed during the boot sequence are no longer ignored by the KVM Application.
- (CSCte63284) It is no longer possible to accidentally clone a service profile or template with a name of an existing SP/SPT under the same organization.
- (CSCte99193) FTP download from UCS Manager to a remote windows server no longer gets stuck at 2% complete during download.
- (CSCtd41935) Service profiles are no longer associated when the VLAN-Port instances maximum is reached.
- (CSCtd59681) The system no longer takes several minutes to initialize when a large number of virtual interfaces are configured.
- (CSCtd86292) Removing blades that have not been previously decommissioned will no longer lead to undefined or missing slots if a new blade is subsequently inserted.
Fabric Interconnect
- (CSCtb83759) In End Host Mode, a server MAC address will now be correctly flushed and will not cause traffic problems.
- (CSCta73919) When a fabric interconnect moves from standalone mode to cluster mode the virtual IP Address will not be overwritten by the out of band IP of the primary fabric-interconnect.
- (CSCsz03030) The CIMC interface to the IOM no longer shows in pinning border/server output.
- (CSCta36817) When multiple SNMP trap hosts are configured, SNMP traps are sent to the all configured hosts.
- (CSCtg66708) An m71kr-q adapter will no longer continuously and rapidly retry logins, causing the fabric interconnect to be busy and a vHBA's fabric login to get rejected.
- (CSCtg25938) Fabric Interconnect updates to a new UCS Manager version will no longer fail if the Switchname variable contains the underscore character.
Open Caveats
Caveats opened in earlier builds of a release are still open unless noted otherwise in the bug record.
The following caveat was opened in Release 1.3(1y):
Symptom ‘Application Blocked by Security Settings’ error when starting the Cisco UCS Manager GUI or KVM Console application. (CSCuo78883)
Because the Java Code Signing Certificate expired, users on Java 7 update 40 or higher might see the following message:
Your security settings have blocked an application signed with an expired or not-yet-valid certificate from running.To fix this issue, you can either temporarily lower your Java security settings to add Cisco UCS Manager as an exception, or if you are using Java 7 update 51 or higher, you can add the Cisco UCS Manager host IP address to the Exception Site list.
To temporarily lower your security settings:
1.
2.
4.
5.
To add the IP address to the exception site list (for Java 7 version 51 and higher):
1.
2.
If you use HTTPS to access Cisco UCS Manager, ensure that you have the correct prefix.
The following caveat was opened in Release 1.3(1n):
Symptom System Inventory Callhome messages fail when the number of chassis exceeds 12.
The following caveats were opened in Release 1.3(1i):
Symptom During Server Association, the following configuration error is reported - "Missing or Incompatible BIOS Image"
Symptom FSM gets stuck in an Error Configuring the Local Disk Controller state due to various underlying conditions. Those can include but are not limited to the following:
- The Local Disks not getting discovered correctly or are "available/presence-Equipped" but not in a Ready state.
- Failures that can't be correctly communicated to Cisco UCS Manager can get reported as this type of error.
Workaround Remove and insert all of the local disks from the failing server, then re-acknowledge the server. (CSCta45805)
Symptom BMC or BIOS fails to confirm that a board is running in low voltage mode before setting threshold. When threshold is set for low voltage and the board runs at high voltage, a SEL event occurs and causes amber lights to display.
For example, here is an error message for a B200-M2 with a low voltage DIMM and CPU. Voltage levels (column 2) are similar to the boards with high voltage components. The threshold is set for LV (columns 5 and 6, 9 and 10).
Workaround None. Resolved in 1.3(1n). (CSCth93217)
The following caveats were opened in Release 1.3(1c), if they are resolved in later builds it is mentioned:
Symptom The Cisco UCS Manager GUI fails to provide the Local Disk Configuration Policy details if you make global policy changes and then select the Local Disk Configuration Policy after selecting the service profile.
Workaround Select a different service profile or a different GUI pane window and then return back to the service profile which was showing this issue. (CSCth95564)
Symptom When using M2 processors and Low Voltage DIMMs, the following error log messages may be seen for P0V75_DDR3_P1 and P1V5_DDR3_P1:
Line 418: 1a2 | 12/31/1969 19:00:36 | BMC | Voltage P1V5_DDR3_P2 #0x09 | Lower critical - going low | Asserted | Reading 1.33 < Threshold 1.44 VoltsWorkaround None. Resolved in 1.3(1i). (CSCth70776)
CIMC
Symptom The IO Module not controlling fan speed is unable to communicate with a fan for more than 10 minutes as determined by platform OHMS. The IO Module controlling the fan speeds is able to communicate to the same fan and all the fan LEDs are green. There isn't a visible indication on the fan LED or IOM health LED that a fan access has failed. In this case the IOM that is having trouble accessing a fan for greater than 10 minutes should have its health LED amber. The OHMS status bit indicates the fan access failure and this data is present in the techsupport along with data from thermal and dmserver indicating the problem I2C access.
Workaround Hot swap the fan module as this has in some cases recovered i2c access.(CSCtg85906)
RAID Controller
Symptom In a special case of a minor hard drive defect where SAS link does not come up, the LSI controller does not see the drive at all, but the CPLD sees it and reports its presence to UCS Manager. This causes UCS Manager to see the drive as present and "no fault" (operable).
Workaround If the drive went bad from a configured Disk Array, the user will see the disk array as degraded with missing drive in WebBIOS or MSM. (CSCtg42960)
UCS Manager
Symptom SNMP authentication fails when using user details configured from a third party authentication server like RADIUS and subsequently all SNMPv3 requests fail. Network management tools like Device Manager (DM), Fabric Manager (FM) will not be able to retrieve information from the UCS through SNP and are unable to display important information. SNMP only recognizes two roles "network-operator" or "vdc-admin". User accounts created on a RADIUS server who do not have these roles will not be authorized to access SNMP details.
Workaround Add "network-operator" or "vdc-admin" as roles to the user accounts in the RADIUS server. (CSCtg94770)
Symptom A standard attempt to execute Update Firmware ALL fails with a dependency on a deployed FW pack.
Workaround Follow the error message to execute Update All, i.e., Modify the policy to execute the update. (CSCtc69186)
Symptom The Cisco UCS Manager GUI shows Admin Speed (gbps) 1 and 10 for ports beyond 1/8, however if we try to set to 1Gbps it returns an error saying 1G speed is invalid for the port. Cisco's Fabric Extender Cisco UCS 6120XP only supports 8 1G ports, while the Cisco UCS 6140XP supports 16 1G ports.
Workaround The error is correctly returned when setting more than 8 ports' speed to 1G in a 6120XP Fabric Interconnect. To prevent the error message, reconfigure to use the correct number of 1G connections for your switch. (CSCtg48718)
Red Hat Linux
Symptom When installing ESX 4.0 or ESX 4.0 Update 1 on a server with more than 190GB of physical memory, booting the ESX host fails and opens the recovery shell
Workaround For ESX 4.0 and ESX 4.0 Update 1, reduce the low reserved memory by setting the boot option "memLowReservedMaxMB" to 384MB. In the bootloader console, append the following to the command line: vmkopts=memLowReservedMaxMB:384. Depending on the types of devices in your network, you may have to increase the amount of low reserved-memory to achieve a better performance. For more detail, see the document: http://kb.vmware.com/kb/1016239 (CSCtf61345)
Symptom Loading multiple driver disks during a RHEL 5.x installation fails.
Workaround See the article at http://kbase.redhat.com/faq/docs/DOC-17753 (CSCte73015)
Symptom When a vNIC is not in failover mode and a link down event occurs, the network traffic on the blades is disrupted with a system running RHEL 5.3.
Workaround This is a known issue with the ixgbe driver in RHEL 5.3 and because RHEL 5.4 is the latest release, Red Hat recommends upgrading the systems to the RHEL 5.4. If you cannot upgrade to RHEL 5.4, below are a few suggestions that has been found to work.
2.
Note that network performance may be affected since the system is running in legacy mode. (CSCte44548)
Symptom Pass-through DMA Support selection is not available in the BIOS if it was Disabled prior to the BIOS upgrade. If you had this option Disabled in previous version, the selection is hidden in the updated BIOS.
Workaround When you are in the BIOS Setup utility, press F9 to Load the BIOS defaults (CSCtb96792)
Local Disk/RAID
Symptom After the removal or insertion of one or more local disks, their full discovery fails.
Workaround Re-acknowledge the server to complete the full discovery. (CSCsy80888)
BIOS
Symptom Hubs that only use USB 1.0 may not properly present an attached USB device to the UCS server.
Workaround Avoid using USB hubs that are exclusively USB 1.0 capable. Virtually all USB hubs sold today are USB 1.0/2.0 capable. (CSCtb20301)
Symptom With the B-250 blade server, the displayed ESX and Linux OS HDD Boot Device Order is the reverse of the BIOS HDD Boot Order.
Workaround Review both the disks (and drive labels as applicable) during installations of ESX and Linux versions and choose the correct disk for installation. (CSCtd90695)
Symptom When memory mirroring configuration is disabled by removing a DIMM, the BIOS will switch to the Performance mode, and will not log a SEL that mirroring was disabled.
Workaround Check the status of the memory mirroring in BIOS Setup->Advanced -> Memory Configuration -> Memory RAS and Performance Configuration . (CSCsy54097)
Symptom When a faulty DIMM is detected in early BIOS POST (for example, the blade was powered on with a faulty DIMM), two SEL entries will be sent to the CIMC. One entry will be logged for each DIMM.
Workaround Enter BIOS Setup and navigate to Advanced -> Memory Configuration . This menu will help to distinguish a faulty DIMM from its neighbor. (CSCsy97698)
Symptom When hot plugging or removing USB devices at a BIOS Setup -> Advanced -> USB screen, the Setup Utility may freeze.
Workaround Reboot the server. (CSCsz41907)
Symptom When a NIC is not present in the system, or is not part of the boot order, the BIOS produces the prompt "Press F12 to boot from the Network".
Symptom If a single DIMM in a channel is marked faulty during BIOS POST, the entire channel is marked faulty. Even empty DIMM slots can be marked faulty.
Workaround None. This is a false positive error message, it can be safely ignored. (CSCsz73464)
Symptom Under certain conditions after clearing the CMOS, Service Profile disassociation might take up to 20 FSM iterations to finish, the virtual media KVM interface might incorrectly indicate it will boot to the EFI Shell, or the BIOS boot-order table might contain only the EFI-shell as a boot option.
Workaround Enter the following commands:
Symptom Installing EFI Native SLES 11 is not supported in this release.
Workaround Currently, there is no workaround. (CSCsz99666)
Symptom Disabling USB 2.0 through Advanced->USB could result in inconsistent information on that particular page. Some devices may not show up as expected. This does not results in functional degradation during POST.
Workaround Either don't disable USB 2.0, or ignore the resulting artifacts in the BIOS setup. (CSCta21849)
Symptom After resetting the CMOS the system date needs to be reset to current.
Adapters
Symptom Failure to PXE boot a UCS server with an M81KR adapter, and there is an indication that a boot file is not found. This is seen when the DHCP server is using option 67 (RFC 2132) to report the bootfile name to the PXE client.
Workaround Use the DHCP "filename" setting instead of the "option file-name" setting for ISC DHCP servers or the equivalent for other DHCP servers. (CSCtl91488)
Symptom With a server booting from SAN, a server crash may occur when an FC HBA is reset, or when a WWPN is zoned in or out on a core fabric switch, or a link flap event occurs either between the NPV switch and the host, or between the NPV switch and the core switch, or the core switch and storage. The symptoms of this problem include server hangs during normal operation, whether or not I/Os happen. It may either remain hung, or may panic and reboot. Upon a reboot, a vmcore file may or may not be present in /var/crash/ depending on whether sync to disk succeeded or not. Alternatively, the server may not crash or hang but can encounter a journal commit I/O error and the boot partition (located on a SAN LUN) will become a read-only file system. The server stays up, but nothing can be written to the necessary partition.
Workaround There is no workaround other than not booting from SAN. If the OS is RHEL, the fix for this issue will be in RHEL 5.5.z, and upgrading to that kernel is recommended when it releases. (CSCtf81596)
Symptom When a DCBXP peer on a physical interface sends two different unique identifiers in the Protocol data unit in the same session, a DCBXP process error disables the port.
KVM
Symptom During the Server Power-State Management, the KVM session may be aborted with a message displaying "Network Connection Dropped".
Workaround Close the KVM session(s) that have been aborted and open a new KVM session. (CSCtc53253)
Cisco UCS Manager
Symptom Information about the number of CPU cores enabled is unavailable. Along with the other processor information, the Cisco UCS Manager GUI and CLI don't show this info.
Symptom A SMASH Command with an incorrect option should result in an "INVALID OPTION" error.
Workaround No work-around required. The message displayed is "COMMAND SYNTAX ERROR". (CSCsv87256)
Symptom The PCIe Address for the Cisco UCS M81KR Virtual Interface Card is not seen in the GUI (or CLI). It causes no functional impact.
Workaround The only work around is to boot some host OS onto the blade and then determine the PCI address and map it to the MAC address (and subsequently to the VNIC). In a 2.6 kernel based Linux for instance, the /sys/class/net/<device> directory has relevant information. (CSCte58483)
Symptom Modification of trusted CoS policy in Service Profile does not get immediately applied to the server. If you modify the trusted CoS policy of an adapter profile in a service profile that is currently attached to a physical server, a server reboot is needed. Since it is unsafe to automatically reboot an associated server, UCSM currently does not.
Workaround Manually reboot the server or disassociate and reassociate the server to get the CoS policy to be applied. (CSCte44668)
Symptom Environment statistics for IO Module 1 are not shown.
Symptom For each Cisco UCS 82598KR-CI 10-GB Ethernet Adapter, 2 interfaces show up in the OS and ethtool reports Link Detected = yes for both of them. This is only seen on Cisco UCS B250 servers.
Workaround Use the MAC that has the value provisioned in the service profile. (CSCtd14055)
Symptom One vNIC defined in the service profile boot order results in two BIOS vNICs.
Workaround Avoid defining two different pxelinux.cfg/<MAC> files that have different boot/install instructions. When booted, both vNICs should execute the same PXE configuration. (CSCsz41107)
Symptom After a full restore of the primary fabric interconnect, the subordinate fabric interconnect installation may temporarily fail with the following message:
Workaround Retry the fabric interconnect installation. (CSCsz85876)
Symptom When the time-based UUID generation method is used in the UUIDgen tool, the system reports duplicate UUIDs because UUIDs are validated based on their suffix, whereas the time-stamp method creates UUIDs with unique prefixes, but non-unique suffixes.
Workaround Use the random method in the UUIDgen tool to ensure that suffixes are unique. (CSCta40790)
Symptom For a given port profile with existing VIFs, if the "Max-Ports" setting is reduced from the currently configured value to a value less than the "Used-Ports" value reported for that port profile by VMware vCenter, this is a mis-configuration. The new value for "Max-Ports" for that port profile will only be updated in Cisco UCS Manager and its update in VMware Center will fail, causing a inconsistency between Cisco UCS Manager and VMware Center Server.
Workaround If the need arises to reduce the value of "Max-Ports" of a given port profile, the new value should be at least the value of "Used-Ports" reported by the VMware Center for all the DVSes for that port profile (not lower than maximum of all the "Used-Ports" values). This constraint has to be ensured manually. (CSCte12163)
Symptom When a service profile containing 2 vNICs and having failover enabled is applied to some adapters, the fail back timeout specified in the adapter policy for the second vNIC has no effect. The fail back timeout specified in the adapter policy and applied to the first vNIC is applied to the whole adapter and effective for both vNICs.
Workaround Specify the desired timeout in the adapter policy and apply to the first vNIC. (CSCsz68887)
Symptom Cisco UCS Manager reports incorrect v NICs or VIFs associated with a given Virtual Machine if and only if the Virtual Machine is deployed from VMware Center in Fault-Tolerance (Active-Standby) mode and the Virtual Machine happens to be the standby or FT Virtual Machine.
Symptom When firmware is updated, UCSM accepts another firmware update before the completion of the current update. The new request will fail silently and lock out the selected firmware package for the next update.
Workaround Create a new host firmware package with a different name from the one that gets locked out which points to the same BIOS package. The new package with a different name, using the same BIOS will not be locked out. (CSCtc26149)
Cisco UCS Manager GUI
Symptom When upgrading from releases prior to 1.1.1, OS-specific default adapter policies will not have the current recommended default values.
Workaround After an upgrade from a release prior to 1.1.1, we recommend manually changing the adapter policy parameters to the following values:
Symptom The UCSM GUI could show all DIMMs to be in array 1, and maximum memory for a blade of 192GB for a B200.
Workaround This is a display-only issue, and does not affect functionality. DIMMs may be physically located in array 1 or array 2. (CSCta56527)
Symptom Hardware revision numbers for fabric interconnect components are not populated in the Cisco UCS Manager.
Workaround Enter the connect nxos command to connect to the native NX-OS CLI, then issue the appropriate show sprom component command and look for H/W Version: field in the command output. (CSCta12005)
Symptom In the Cisco UCS Manager GUI, you can only select port channels and individual uplink ports as pin targets, but the Cisco UCS Manager CLI allows you to also select port channel member ports as pin targets.
Workaround Port channel member ports should not be selected as pin targets, even if the Cisco UCS Manager CLI allows you to. (CSCta60495)
Symptom Even though there are no POST failures in the chassis, Cisco UCS Manager may sometimes display the overall status of the chassis as POST-failure.
Workaround Check the chassis POST messages for errors, and if there are none, ignore the Cisco UCS Manager status message. (CSCsz01878)
Symptom Statistics counters cannot be cleared using Cisco UCS Manager CLI.
Workaround Clear the counters using the Cisco UCS Manager GUI. (CSCsz47512)
Symptom The assignment of servers to dynamic pools do not automatically occur.
Workaround Re-acknowledge the server to enable it as a candidate for pool assignment. (CSCta06882)
Symptom When a cluster configuration is set up such that I/O module 1 is cabled to fabric interconnect B and I/O module 2 is cabled to fabric interconnect A, then the Ethernet devices are given ports 1 and 0. However if the setup is straight, with I/O Module 1 connected to fabric interconnect A and I/O Module 2 to fabric interconnect B, then the devices are assigned ports 0 and 1.
Workaround Connect IOM1 to fabric-interconnect A, and IOM2 to fabric-interconnect B. (CSCtb35660)
Symptom When checking for UUID uniqueness, currently only the UUID suffix is checked.
Workaround Use a single UUID prefix. (CSCtc59481)
Symptom In a Cisco UCS instance with five or more chassis, the following sequence of events may cause the system to not be in high availability ready state for a period of up to five minutes:
Workaround Wait for the HA READY state. (CSCsz40462)
Symptom Logon access is denied for user accounts where the password field was left blank during user account creation.
Workaround When creating a user account, ensure that a secure password for the account is specified. (CSCta21326)
Symptom When more than 10 Cisco UCS Manager GUI sessions are open at the same time with remote authentication for a long time (typically for a few hours), one of the Cisco UCS Manager GUI sessions may fail to re-authenticate. This causes the session that fails the re-authentication to close. The problem does not happen when local authentication is in use.
Workaround Re-login to the Cisco UCS Manager GUI session when it closes. (CSCtb05260)
Symptom If you move from subnet A to subnet B then do a cluster failover and move back to subnet A, a Virtual IP is no longer pingable.
Workaround Set the VIP to a different VIP by using the following CLI commands to set it back to the original address:
UCS Manager CLI
Symptom The UUID of the VM changes in VMware vCenter. After a VM restarts, the virtual machine node on the VM tab shows multiple instances of the same VM with one online and one offline.
Workaround After the VM retention period configured in the VM life cycle policy has passed, Cisco UCS Manager deletes the offline instance automatically. (CSCtc86297)
Symptom If multiple vHBA initiators are configured in the same zone so that they are visible to each other and can login to each other, and storage multipathing is not configured with active and standby paths through the Cisco UCS fabric interconnects (There is only one path through the primary fabric interconnect), and the primary fabric interconnect is rebooted, the vHBA driver can be exposed to a situation in which two initiators can try to login to each other at the same time, and cause a host crash.
Workaround Do not configure multiple vHBA initiators in the same zone, to ensure that they are not visible to each other. (CSCte36784)
Symptom ESX Read and Write commands sent on a vHBA keep timing out and being aborted even if the target device is logged into the network. This can happen if the link flaps very fast from up to down to up and memory allocation for the link event fails. The vHBA driver misses the link down event and it does not re-login to the fabric interconnect. The fabric interconnect, however, has no login state for the vHBA and so drops all packets from the vHBA.
Workaround Disable and reenable the port on the UCS fabric interconnect that corresponds to the vHBA. (CSCte08092)
Fabric Interconnect
Symptom Without pin group configuration, server interfaces are pinned to uplink interfaces of the fabric interconnect dynamically and the pinning is redistributed as uplink interfaces go up or down. In some situations, the distribution of server interfaces across uplink interfaces is not balanced. Potential impact is some uplinks are under utilized.
Symptom At bootup of the fabric interconnect, the following message will be displayed on the console: "The startup-config won't be used until the next reboot."
Workaround None, just ignore the message. (CSCsx13134)
Symptom Console login is treating the admin and ADMIN account as the same. Console login name on the fabric interconnect is not case sensitive, so there is no differentiation between for example, admin and ADMIN.
Workaround Implement usernames that are not case sensitive. (CSCsy15489)
Symptom When you set a TFTP core exporter IP address through Cisco UCS Manager, the fabric interconnect accepts the address even if it is malformed, e.g 1.2.3.412. This does not pose any functional impact to core exporter with valid IP addresses.
Workaround Remove the malformed core exporter IP address. (CSCsz75747)
Symptom Under high stress on the system with repeated port flapping and a default or native VLAN changing simultaneously, a process may cause the fabric interconnect to reload.
Symptom The show cdp neighbor command does not display information for CDP neighbors seen from the management interface, nor does it display the fabric interconnect CDP information corresponding to the management interface.
Symptom Under some circumstances, system messages are not shown on the terminal monitor even though logging on terminal monitor is enabled globally and on a particular session.
Workaround Use some other destination such as a console, remote server, or local log file. If using a terminal monitor as a syslog destination, re-issue the terminal monitor command from the NXOS CLI every time after changing any syslog configuration. (CSCta31689)
Symptom With FM/DM version 5.0(0.295) and UCS 1.1 release, a security user defined in Cisco UCS Manager does not get displayed on FM/DM.
Workaround None. Verify user security from Cisco UCS Manager. (CSCte25876)
TFTP
Symptom When downloading an image or bundle using TFTP, the download task appears to be stuck at 2% or sometimes fails completely. TFTP download can fail or appear stuck if the bundle is too large (for example, 450MB in size). If any image is downloaded individually, should succeed.
Workaround Either download individual images and not the bundle or use a different protocol like SCP, SFTP, or FTP. Sometimes having the TFTP server close to the fabric interconnect (on the same VLAN or subnet) may help. (CSCtf66646)
Release 1.2(1)
The following caveats were opened in Release 1.2(1):
Symptom Loading multiple driver disks during a RHEL 5.x installation fails.
Workaround See the article at http://kbase.redhat.com/faq/docs/DOC-17753 (CSCte73015)
Symptom When a vNIC is not in failover mode and a link down event occurs, the network traffic on the blades is disrupted with a system running RHEL 5.3.
Workaround This is a known issue with the ixgbe driver in RHEL 5.3 and because RHEL 5.4 is the latest release, Red Hat recommends upgrading the systems to the RHEL 5.4. If you cannot upgrade to RHEL 5.4, below are a few suggestions that has been found to work.
2.
Note that network performance may be affected since the system is running in legacy mode. (CSCte44548)
Symptom Pass-through DMA Support selection is not available in the BIOS if it was Disabled prior to the BIOS upgrade. If you had this option Disabled in previous version, the selection is hidden in the updated BIOS.
Workaround When you are in the BIOS Setup utility, press F9 to Load the BIOS defaults (CSCtb96792)
Symptom After the removal or insertion of one or more local disks, their full discovery fails.
Workaround Re-acknowledge the server to complete the full discovery. (CSCsy80888)
Symptom The Disk Fault/Error Codes, Disk Status, Alarms and the failures forwarded by the SAS Controller are not received by Cisco UCS Manager.
Symptom FSM gets stuck in an Error Configuring the Local Disk Controller state due to various underlying conditions. Those can include but are not limited to the following:
- The Local Disks not getting discovered correctly or are "available/presence-Equipped" but not in a Ready state.
- Failures that can't be correctly communicated to Cisco UCS Manager can get reported as this type of error.
Workaround Remove and insert all of the local disks from the failing server, then re-acknowledge the server. (CSCta45805)
Symptom The disk scrub policy does not meet DoD compliance.
Symptom Hubs that only use USB 1.0 may not properly present an attached USB device to the UCS server.
Workaround Avoid using USB hubs that are exclusively USB 1.0 capable. Virtually all USB hubs sold today are USB 1.0/2.0 capable. (CSCtb20301)
Symptom With the B-250 blade server, the displayed ESX and Linux OS HDD Boot Device Order is the reverse of the BIOS HDD Boot Order.
Workaround Review both the disks (and drive labels as applicable) during installations of ESX and Linux versions and choose the correct disk for installation. (CSCtd90695)
Symptom When memory mirroring configuration is disabled by removing a DIMM, the BIOS will switch to the Performance mode, and will not log a SEL that mirroring was disabled.
Workaround Check the status of the memory mirroring in BIOS Setup->Advanced -> Memory Configuration -> Memory RAS and Performance Configuration . (CSCsy54097)
Symptom When a faulty DIMM is detected in early BIOS POST (for example, the blade was powered on with a faulty DIMM), two SEL entries will be sent to the BMC. One entry will be logged for each DIMM.
Workaround Enter BIOS Setup and navigate to Advanced -> Memory Configuration . This menu will help to distinguish a faulty DIMM from its neighbor. (CSCsy97698)
Symptom When hot plugging or removing USB devices at a BIOS Setup -> Advanced -> USB screen, the Setup Utility may freeze.
Workaround Reboot the server. (CSCsz41907)
Symptom When a NIC is not present in the system, or is not part of the boot order, the BIOS produces the prompt "Press F12 to boot from the Network".
Symptom If a single DIMM in a channel is marked faulty during BIOS POST, the entire channel is marked faulty. Even empty DIMM slots can be marked faulty.
Workaround None. This is a false positive error message, it can be safely ignored. (CSCsz73464)
Symptom Under certain conditions after clearing the CMOS, Service Profile disassociation might take up to 20 FSM iterations to finish, the virtual media KVM interface might incorrectly indicate it will boot to the EFI Shell, or the BIOS boot-order table might contain only the EFI-shell as a boot option.
Workaround Enter the following commands:
Symptom Installing EFI Native SLES 11 is not supported in this release.
Workaround Currently, there is no workaround. (CSCsz99666)
Symptom Disabling USB 2.0 through Advanced->USB could result in inconsistent information on that particular page. Some devices may not show up as expected. This does not results in functional degradation during POST.
Workaround Either don't disable USB 2.0 (we are not aware of any need to disable it), or ignore the resulting artifacts in the BIOS setup. (CSCta21849)
Symptom After resetting the CMOS the system date needs to be reset to current.
Symptom With a server booting from SAN, a server crash may occur when an FC HBA is reset, or when a WWPN is zoned in or out on a core fabric switch, or a link flap event occurs either between the NPV switch and the host, or between the NPV switch and the core switch, or the core switch and storage. The symptoms of this problem include server hangs during normal operation, whether or not I/Os happen. It may either remain hung, or may panic and reboot. Upon a reboot, a vmcore file may or may not be present in /var/crash/ depending on whether sync to disk succeeded or not. Alternatively, the server may not crash or hang but can encounter a journal commit I/O error and the boot partition (located on a SAN LUN) will become a read-only file system. The server stays up, but nothing can be written to the necessary partition.
Workaround There is no workaround other than not booting from SAN. If the OS is RHEL, the fix for this issue will be in RHEL 5.5.z, and upgrading to that kernel is recommended when it releases. (CSCtf81596)
Symptom When a DCBXP peer on a physical interface sends two different unique identifiers in the Protocol data unit in the same session, a DCBXP process error disables the port.
Workaround Issue the following commands to enable the port:
Wait for a minute, the port will come up.(CSCsx42435)
Symptom During the Server Power-State Management, the KVM session may be aborted with a message displaying "Network Connection Dropped".
Workaround Close the KVM session(s) that have been aborted and open a new KVM session. (CSCtc53253)
Symptom Information about the number of CPU cores enabled is unavailable. Along with the other processor information, the Cisco UCS Manager GUI and CLI don't show this info.
Symptom A SMASH Command with an incorrect option should result in an "INVALID OPTION" error.
Workaround No work-around required. The message displayed is "COMMAND SYNTAX ERROR". (CSCsv87256)
Symptom The PCIe Address for the Cisco UCS M81KR Virtual Interface Card is not seen in the GUI (or CLI). It causes no functional impact.
Workaround The only work around is to boot some host OS onto the blade and then determine the PCI address and map it to the MAC address (and subsequently to the VNIC). In a 2.6 kernel based Linux for instance, the /sys/class/net/<device> directory has relevant information. (CSCte58483)
Symptom Modification of trusted CoS policy in Service Profile does not get immediately applied to the server. If you modify the trusted CoS policy of an adapter profile in a service profile that is currently attached to a physical server, a server reboot is needed. Since it is unsafe to automatically reboot an associated server, UCSM currently does not.
Workaround Manually reboot the server or disassociate and reassociate the server to get the CoS policy to be applied. (CSCte44668)
Symptom Environment statistics for IO Module 1 are not shown.
Symptom For each Cisco UCS 82598KR-CI 10-GB Ethernet Adapter, 2 interfaces show up in the OS and ethtool reports Link Detected = yes for both of them. This is only seen on Cisco UCS B250 servers.
Workaround Use the MAC that has the value provisioned in the service profile. (CSCtd14055)
Symptom One vNIC defined in the service profile boot order results in two BIOS vNICs.
Workaround Avoid defining two different pxelinux.cfg/<MAC> files that have different boot/install instructions. When booted, both vNICs should execute the same PXE configuration. (CSCsz41107)
Symptom After a full restore of the primary fabric interconnect, the subordinate fabric interconnect installation may temporarily fail with the following message:
Workaround Retry the fabric interconnect installation. (CSCsz85876)
Symptom When the time-based UUID generation method is used in the UUIDgen tool, the system reports duplicate UUIDs because UUIDs are validated based on their suffix, whereas the time-stamp method creates UUIDs with unique prefixes, but non-unique suffixes.
Workaround Use the random method in the UUIDgen tool to ensure that suffixes are unique. (CSCta40790)
Symptom For a given port profile with existing VIFs, if the "Max-Ports" setting is reduced from the currently configured value to a value less than the "Used-Ports" value reported for that port profile by VMware vCenter, this is a mis-configuration. The new value for "Max-Ports" for that port profile will only be updated in Cisco UCS Manager and its update in VMware Center will fail, causing a inconsistency between Cisco UCS Manager and VMware Center Server.
Workaround If the need arises to reduce the value of "Max-Ports" of a given port profile, the new value should be at least the value of "Used-Ports" reported by the VMware Center for all the DVSes for that port profile (not lower than maximum of all the "Used-Ports" values). This constraint has to be ensured manually. (CSCte12163)
Symptom When a service profile containing 2 vNICs and having failover enabled is applied to some adapters, the fail back timeout specified in the adapter policy for the second vNIC has no effect. The fail back timeout specified in the adapter policy and applied to the first vNIC is applied to the whole adapter and effective for both vNICs.
Workaround Specify the desired timeout in the adapter policy and apply to the first vNIC. (CSCsz68887)
Symptom Cisco UCS Manager reports incorrect v NICs or VIFs associated with a given Virtual Machine if and only if the Virtual Machine is deployed from VMware Center in Fault-Tolerance (Active-Standby) mode and the Virtual Machine happens to be the standby or FT Virtual Machine.
Symptom When firmware is updated, UCS Manager accepts another firmware update before the completion of the current update. The new request will fail silently and lock out the selected firmware package for the next update.
Workaround Create a new host firmware package with a different name from the one that gets locked out which points to the same BIOS package. The new package with a different name, using the same BIOS will not be locked out. (CSCtc26149)
Symptom When upgrading from releases prior to 1.1.1, OS-specific default adapter policies will not have the current recommended default values.
Workaround After an upgrade from a release prior to 1.1.1, we recommend manually changing the adapter policy parameters to the following values:
Symptom All DIMMs are reported to be in array 1, and the max memory for a blade is reported as 192GB.
Workaround DIMMs may be physically located in array 1 or array 2. This is a display-only issue, and does not affect functionality. Ignore the incorrect report. (CSCta56527)
Symptom The UCSM GUI could show all DIMMs to be in array 1, and maximum memory for a blade of 192GB for a B200.
Workaround This is a display-only issue, and does not affect functionality. DIMMs may be physically located in array 1 or array 2. (CSCta56527)
Symptom Hardware revision numbers for fabric interconnect components are not populated in the Cisco UCS Manager.
Workaround Enter the connect nxos command to connect to the native NX-OS CLI, then issue the appropriate show sprom component command and look for H/W Version: field in the command output. (CSCta12005)
Symptom In the Cisco UCS Manager GUI, you can only select port channels and individual uplink ports as pin targets, but the Cisco UCS Manager CLI allows you to also select port channel member ports as pin targets.
Workaround Port channel member ports should not be selected as pin targets, even if the Cisco UCS Manager CLI allows you to. (CSCta60495)
Symptom Even though there are no POST failures in the chassis, Cisco UCS Manager may sometimes display the overall status of the chassis as POST-failure.
Workaround Check the chassis POST messages for errors, and if there are none, ignore the Cisco UCS Manager status message. (CSCsz01878)
Symptom Statistics counters cannot be cleared using Cisco UCS Manager CLI.
Workaround Clear the counters using the Cisco UCS Manager GUI. (CSCsz47512)
Symptom The assignment of servers to dynamic pools do not automatically occur.
Workaround Re-acknowledge the server to enable it as a candidate for pool assignment. (CSCta06882)
Symptom When a cluster configuration is set up such that I/O module 1 is cabled to fabric interconnect B and I/O module 2 is cabled to fabric interconnect A, then the Ethernet devices are given ports 1 and 0. However if the setup is straight, with I/O Module 1 connected to fabric interconnect A and I/O Module 2 to fabric interconnect B, then the devices are assigned ports 0 and 1.
Workaround Connect IOM1 to fabric-interconnect A, and IOM2 to fabric-interconnect B. (CSCtb35660)
Symptom When checking for UUID uniqueness, currently only the UUID suffix is checked.
Workaround Use a single UUID prefix. (CSCtc59481)
Symptom In a Cisco UCS instance with five or more chassis, the following sequence of events may cause the system to not be in high availability ready state for a period of up to five minutes:
Workaround Wait for the HA READY state. (CSCsz40462)
Symptom Logon access is denied for user accounts where the password field was left blank during user account creation.
Workaround When creating a user account, ensure that a secure password for the account is specified. (CSCta21326)
Symptom When more than 10 Cisco UCS Manager GUI sessions are open at the same time with remote authentication for a long time (typically for a few hours), one of the Cisco UCS Manager GUI sessions may fail to re-authenticate. This causes the session that fails the re-authentication to close. The problem does not happen when local authentication is in use.
Workaround Re-login to the Cisco UCS Manager GUI session when it closes. (CSCtb05260)
Symptom If you move from subnet A to subnet B then do a cluster failover and move back to subnet A, a Virtual IP is no longer pingable.
Workaround Set the VIP to a different VIP by using the following CLI commands to set it back to the original address:
Symptom Without pin group configuration, server interfaces are pinned to uplink interfaces of the fabric interconnect dynamically and the pinning is redistributed as uplink interfaces go up or down. In some situations, the distribution of server interfaces across uplink interfaces is not balanced. Potential impact is some uplinks are under utilized.
Symptom At bootup of the fabric interconnect, the following message will be displayed on the console: "The startup-config won't be used until the next reboot."
Workaround None, just ignore the message. (CSCsx13134)
Symptom Console login is treating the admin and ADMIN account as the same. Console login name on the fabric interconnect is not case sensitive, so there is no differentiation between for example, admin and ADMIN.
Workaround Implement usernames that are not case sensitive. (CSCsy15489)
Symptom When you set a TFTP core exporter IP address through Cisco UCS Manager, the fabric interconnect accepts the address even if it is malformed, e.g 1.2.3.412. This does not pose any functional impact to core exporter with valid IP addresses.
Workaround Remove the malformed core exporter IP address. (CSCsz75747)
Symptom Under high stress on the system with repeated port flapping and a default or native VLAN changing simultaneously, a process may cause the fabric interconnect to reload.
Symptom The show cdp neighbor command does not display information for CDP neighbors seen from the management interface, nor does it display the fabric interconnect CDP information corresponding to the management interface.
Symptom Under some circumstances, system messages are not shown on the terminal monitor even though logging on terminal monitor is enabled globally and on a particular session.
Workaround Use some other destination such as a console, remote server, or local log file. If using a terminal monitor as a syslog destination, re-issue the terminal monitor command from the NXOS CLI every time after changing any syslog configuration. (CSCta31689)
Symptom With FM/DM version 5.0(0.295) and UCS 1.1 release, a security user defined in Cisco UCS Manager does not get displayed on FM/DM.
Workaround None. Verify user security from Cisco UCS Manager. (CSCte25876)
Symptom The UUID of the VM changes in VMware vCenter. After a VM restarts, the virtual machine node on the VM tab shows multiple instances of the same VM with one online and one offline.
Workaround After the VM retention period configured in the VM life cycle policy has passed, Cisco UCS Manager deletes the offline instance automatically. (CSCtc86297)
Symptom If multiple vHBA initiators are configured in the same zone so that they are visible to each other and can login to each other, and storage multipathing is not configured with active and standby paths through the Cisco UCS fabric interconnects (There is only one path through the primary fabric interconnect), and the primary fabric interconnect is rebooted, the vHBA driver can be exposed to a situation in which two initiators can try to login to each other at the same time, and cause a host crash.
Workaround Do not configure multiple vHBA initiators in the same zone, to ensure that they are not visible to each other. (CSCte36784)
Symptom ESX Read and Write commands sent on a vHBA keep timing out and being aborted even if the target device is logged into the network. This can happen if the link flaps very fast from up to down to up and memory allocation for the link event fails. The vHBA driver misses the link down event and it does not re-login to the fabric interconnect. The fabric interconnect, however, has no login state for the vHBA and so drops all packets from the vHBA.
Workaround Disable and reenable the port on the UCS fabric interconnect that corresponds to the vHBA. (CSCte08092)
Symptom When downloading an image or bundle using TFTP, the download task appears to be stuck at 2% or sometimes fails completely. TFTP download can fail or appear stuck if the bundle is too large. It almost always appears to fail with the current bundle which is 450MB in size. If any image is downloaded individually, should succeed.
Workaround Either download individual images and not the bundle or use a different protocol like SCP, SFTP, or FTP. Sometimes having the TFTP server close to the fabric interconnect (on the same VLAN or subnet) may help. (CSCtf66646)
Release 1.1(1)
The following caveat is open for Release 1.1(1l), most Release 1.1(1j) caveats also apply unless they are listed as resolved for Release 1.1(1l):
Symptom Pass-through DMA Support selection is not available in the BIOS if it was Disabled prior to the BIOS upgrade. If you had this option Disabled in previous version, the selection is hidden in the updated BIOS.
Workaround When you are in the BIOS Setup utility, press F9 to Load the BIOS defaults (CSCtb96792)
This section lists the open caveats in Release 1.1(1j).
Symptom Low Voltage DIMMs marked as Identity Not Established and are not included in the PID catalog.
Workaround None. Disregard the message, the DIMMs are fully functional and the error state is a false positive. Closed in 1.1(1m). (CSCtg86520)
Symptom With the B-250 blade server, the displayed ESX and Linux OS HDD Boot Device Order is the reverse of the BIOS HDD Boot Order.
Workaround Review both the disks (and drive labels as applicable) during installations of ESX and Linux versions and choose the correct disk for installation. (CSCtd90695)
Symptom When memory mirroring configuration is disabled by removing a DIMM, BIOS will switch to the Performance mode, and will not log a SEL that mirroring was disabled.
Workaround Check the status of the memory mirroring in BIOS Setup->Advanced -> Memory Configuration -> Memory RAS and Performance Configuration . (CSCsy54097)
Symptom When a faulty DIMM is detected in early BIOS POST (for example, the blade was powered on with a faulty DIMM), two SEL entries will be sent to the BMC. One entry will be logged for each DIMM.
Workaround Enter BIOS Setup and navigate to Advanced -> Memory Configuration . This menu will help to distinguish a faulty DIMM from its neighbor. (CSCsy97698)
Symptom When hot plugging or removing USB devices at a BIOS Setup -> Advanced -> USB screen, the Setup Utility may freeze.
Workaround Reboot the server. (CSCsz41907)
Symptom When a NIC is not present in the system, or is not part of the boot order, the BIOS produces the prompt "Press F12 to boot from the Network".
Symptom If a single DIMM in a channel is marked faulty during BIOS POST, the entire channel is marked faulty. Even empty DIMM slots can be marked faulty.
Workaround None. This is a false positive error message, it can be safely ignored. (CSCsz73464)
Symptom Installing EFI Native SLES 11 is not supported in this release.
Workaround Currently, there is no workaround. (CSCsz99666)
Symptom Disabling USB 2.0 through Advanced->USB could result in inconsistent information on that particular page. Some devices may not show up as expected. This does not results in functional degradation during POST.
Workaround Either don't disable USB 2.0 (we are not aware of any need to disable it), or ignore the resulting artifacts in the BIOS setup. (CSCta21849)
Symptom FSM gets stuck in an Error Configuring the Local Disk Controller state due to various underlying conditions. Those can include but are not limited to the following:
- The Local Disks not getting discovered correctly or are "available/presence-Equipped" but not in a Ready state.
- Failures that can't be correctly communicated to Cisco UCS Manager can get reported as this type of error.
Workaround Remove and insert all of the local disks from the failing server, then re-acknowledge the server. (CSCta45805)
Symptom The Disk Fault/Error Codes, Disk Status, Alarms and the failures forwarded by the SAS Controller are not received by Cisco UCS Manager.
Symptom After resetting the CMOS the system date needs to be reset to current.
Symptom When a vNIC is not in failover mode and a link down event occurs, the network traffic on the blades is disrupted with a system running RHEL 5.3.
Workaround This is a known issue with the ixgbe driver in RHEL 5.3 and because RHEL 5.4 is the latest release, Redhat recommends upgrading the systems to the RHEL 5.4. If you cannot upgrade to RHEL 5.4, below are a few suggestions that has been found to work.
2.
Note that network performance may be affected since the system is running in legacy mode. (CSCte44548)
Symptom When a DCBXP peer on a physical interface sends two different unique identifiers in the Protocol data unit in the same session, a DCBXP process error disables the port.
Workaround Issue the following commands to enable the port:
Wait for a minute, the port will come up.(CSCsx42435)
Symptom During the Server Power-State Management, the KVM session may be aborted with a message displaying "Network Connection Dropped".
Workaround Close the KVM session(s) that have been aborted and open a new KVM session. (CSCtc53253)
Symptom UCSM 1.1.(1j) firmware activation during UCS firmware upgrade will result in a server. reboot. Customers upgrading their systems from the 1.0.1 or 1.0.2 release to the 1.1(1j) release will experience an unexpected server reboot upon UCSM component activation. This is a result of an incorrect setting of the internal VNIC/VHBA property called lifecycle, that makes the system believe that reconfiguration of these objects is required. This reconfiguration triggers a server reboot.
Workaround No workaround currently exists. Customers can install the 1.1.(1j) release if a server reboot is acceptable for their firmware upgrade scenario and a maintenance window is scheduled. Customers that do not consider a server reboot as an acceptable condition during UCSM FW activation, should install Release 1.1(1m). (CSCtf02353)
Note Note that BIOS and interface card firmware upgrade still require a server reboot. Customers are expected to continue their operations after UCS firmware upgrade with a new BIOS and Interface Card firmware. Therefore the server reboot described in CSCtf02353 is an unexpected condition on UCSM activation, but still fits in the current firmware upgrade completion requirements.
Note CSCtf02353 will not be a problem on newly purchased systems that ship with Release 1.1.(1j).
Symptom The disk scrub policy does not meet DoD compliance.
Symptom After the removal or insertion of one or more local disks, their full discovery fails.
Workaround Re-acknowledge the server to complete the full discovery. (CSCsy80888)
Symptom One vNIC defined in the service profile boot order results in two BIOS vNICs.
Workaround Avoid defining two different pxelinux.cfg/<MAC> files that have different boot/install instructions. When booted, both vNICs should execute the same PXE configuration. (CSCsz41107)
Symptom After a full restore of the primary fabric interconnect, the subordinate fabric interconnect installation may temporarily fail with the following message:
Workaround Retry the fabric interconnect installation. (CSCsz85876)
Symptom When the time-based UUID generation method is used in the UUIDgen tool, the system reports duplicate UUIDs because UUIDs are validated based on their suffix, whereas the time-stamp method creates UUIDs with unique prefixes, but non-unique suffixes.
Workaround Use the random method in the UUIDgen tool to ensure that suffixes are unique. (CSCta40790)
Symptom For a given port profile with existing VIFs, if the "Max-Ports" setting is reduced from the currently configured value to a value less than the "Used-Ports" value reported for that port profile by VMware vCenter, this is a mis-configuration. The new value for "Max-Ports" for that port profile will only be updated in Cisco UCS Manager and its update in VMware Center will fail, causing a inconsistency between Cisco UCS Manager and VMware Center Server.
Workaround If the need arises to reduce the value of "Max-Ports" of a given port profile, the new value should be at least the value of "Used-Ports" reported by the VMware Center for all the DVSes for that port profile (not lower than maximum of all the "Used-Ports" values). This constraint has to be ensured manually. (CSCte12163)
Symptom When a service profile containing 2 vNICs and having failover enabled is applied to some adapters, the fail back timeout specified in the adapter policy for the second vNIC has no effect. The fail back timeout specified in the adapter policy and applied to the first vNIC is applied to the whole adapter and effective for both vNICs.
Workaround Specify the desired timeout in the adapter policy and apply to the first vNIC. (CSCsz68887)
Symptom Cisco UCS Manager reports incorrect v NICs or VIFs associated with a given Virtual Machine if and only if the Virtual Machine is deployed from VMware Center in Fault-Tolerance (Active-Standby) mode and the Virtual Machine happens to be the standby or FT Virtual Machine.
Symptom The UCSM GUI could show all DIMMs to be in array 1, and maximum memory for a blade of 192GB for a B200.
Workaround This is a display-only issue, and does not affect functionality. DIMMs may be physically located in array 1 or array 2. (CSCta56527)
Symptom Hardware revision numbers for fabric interconnect components are not populated in the Cisco UCS Manager.
Workaround Enter the connect nxos command to connect to the native NX-OS CLI, then issue the appropriate show sprom component command and look for H/W Version: field in the command output. (CSCta12005)
Symptom In the Cisco UCS Manager GUI, you can only select port channels and individual uplink ports as pin targets, but the Cisco UCS Manager CLI allows you to also select port channel member ports as pin targets.
Workaround Port channel member ports should not be selected as pin targets, even if the Cisco UCS Manager CLI allows you to. (CSCta60495)
Symptom Even though there are no POST failures in the chassis, Cisco UCS Manager may sometimes display the overall status of the chassis as POST-failure.
Workaround Check the chassis POST messages for errors, and if there are none, ignore the Cisco UCS Manager status message. (CSCsz01878)
Symptom Statistics counters cannot be cleared using Cisco UCS Manager CLI.
Workaround Clear the counters using the Cisco UCS Manager GUI. (CSCsz47512)
Symptom The assignment of servers to dynamic pools do not automatically occur.
Workaround Re-acknowledge the server to enable it as a candidate for pool assignment. (CSCta06882)
Symptom In Cisco UCS Manager GUI, if the Reboot on boot Order Change checkbox is checked for a boot policy, and if CD-ROM or Floppy is the last device in the boot order, then deleting or adding the device does not directly affect the boot order and the server does not reboot.
Symptom When a cluster configuration is set up such that I/O module 1 goes to fabric interconnect B and I/O module 2 goes to fabric interconnect A, then the Ethernet devices are given ports 1 and 0. However if the setup is straight, with I/O Module 1 connected to fabric interconnect A and I/O Module 2 to fabric interconnect B, then the devices are assigned ports 0 and 1.
Workaround Connect IOM1 to fabric-interconnect A, and IOM2 to fabric-interconnect B. (CSCtb35660)
Symptom When checking for UUID uniqueness, currently only the UUID suffix is checked.
Workaround Use a single UUID prefix. (CSCtc59481)
Symptom In a Cisco UCS instance with five or more chassis, the following sequence of events may cause the system to not be in high availability ready state for a period of up to five minutes:
Workaround Wait for the HA READY state. (CSCsz40462)
Symptom Logon access is denied for user accounts where the password field was left blank during user account creation.
Workaround When creating a user account, ensure that a secure password for the account is specified. (CSCta21326)
Symptom When more than 10 Cisco UCS Manager GUI sessions are open at the same time with remote authentication for a long time (typically for a few hours), one of the Cisco UCS Manager GUI sessions may fail to re-authenticate. This causes the session that fails the re-authentication to close. The problem does not happen when local authentication is in use.
Workaround Re-login to the Cisco UCS Manager GUI session when it closes. (CSCtb05260)
Symptom Without pin group configuration, server interfaces are pinned to uplink interfaces of the fabric interconnect dynamically and the pinning is redistributed as uplink interfaces go up or down. In some situations, the distribution of server interfaces across uplink interfaces is not balanced. Potential impact is some uplinks are under utilized.
Symptom At bootup of the fabric interconnect, the following message will be displayed on the console: "The startup-config won't be used until the next reboot."
Workaround None, just ignore the message. (CSCsx13134)
Symptom Console login is treating the admin and ADMIN account as the same. Console login name on the fabric interconnect is not case sensitive, so there is no differentiation between for example, admin and ADMIN.
Workaround Implement usernames that are not case sensitive. (CSCsy15489)
Symptom When you set a TFTP core exporter IP address through Cisco UCS Manager, the fabric interconnect accepts the address even if it is malformed, e.g 1.2.3.412. This does not pose any functional impact to core exporter with valid IP addresses.
Workaround Remove the malformed core exporter IP address. (CSCsz75747)
Symptom Under high stress on the system with repeated port flapping and a default or native VLAN changing simultaneously, a process may cause the fabric interconnect to reload.
Symptom The show cdp neighbor command does not display information for CDP neighbors seen from the management interface, nor does it display the fabric interconnect CDP information corresponding to the management interface.
Symptom Under some circumstances, system messages are not shown on the terminal monitor even though logging on terminal monitor is enabled globally and on a particular session.
Workaround Use some other destination such as a console, remote server, or local log file. If using a terminal monitor as a syslog destination, re-issue the terminal monitor command from the NXOS CLI every time after changing any syslog configuration. (CSCta31689)
Symptom With FM/DM version 5.0(0.295) and UCS 1.1 release, a security user defined in Cisco UCS Manager does not get displayed on FM/DM.
Workaround None. Verify user security from Cisco UCS Manager. (CSCte25876)
Symptom The UUID of the VM changes in VMware vCenter. After a VM restarts, the virtual machine node on the VM tab shows multiple instances of the same VM with one online and one offline.
Workaround After the VM retention period configured in the VM lifecycle policy has passed, Cisco UCS Manager deletes the offline instance automatically. (CSCtc86297)
Symptom If multiple vHBA initiators are configured in the same zone so that they are visible to each other and can login to each other, and storage multipathing is not configured with active and standby paths through the Cisco UCS fabric interconnects (There is only one path through the primary fabric interconnect), and the primary fabric interconnect is rebooted, the vHBA driver can be exposed to a situation in which two initiators can try to login to each other at the same time, and cause a host crash.
Workaround Do not configure multiple vHBA initiators in the same zone, to ensure that they are not visible to each other. (CSCte36784)
Symptom ESX Read and Write commands sent on a vHBA keep timing out and being aborted even if the target device is logged into the network. This can happen if the link flaps very fast from up to down to up and memory allocation for the link event fails. The vHBA driver misses the link down event and it does not re-login to the fabric interconnect. The fabric interconnect, however, has no login state for the vHBA and so drops all packets from the vHBA.
Workaround Disable and reenable the port on the UCS fabric interconnect that corresponds to the vHBA. (CSCte08092)
Release 1.0(2)
The following caveats were opened in UCS software Release 1.0(2) and are still unresolved.
Symptom If default adapter policies are used, windows OS can take a long time to boot due to non-ideal VHBA related settings.
Workaround Create an adapter policy with optimal values and use that in the service profile. (CSCtb99003)
Symptom With various Local Disk Configurations, the LSI SAS Configuration Utility fails to launch while in BIOS.
Workaround The LSI SAS Controller Utility should not be used and all of the Local Disk Policy and Service Profile operations must be executed using UCSM.(CSCtc21336)
Symptom Disabling USB 2.0 is disabled through Advanced->USB, results in various artifacts on that particular page. Some devices may not show up as expected. This results in no functional degradation during POST.
Workaround Either don't disable USB 2.0 (we are currently are not aware of any need to disable it), or ignore the resulting artifacts in the BIOS setup. (CSCta21849)
Symptom When the memory mirroring configuration is destroyed by removing a DIMM, the BIOS will switch to the Performance mode, and will not log a message that mirroring was disabled.
Workaround Check the status of the memory mirroring in BIOS Setup->Advanced -> Memory Configuration -> Memory RAS and Performance Configuration . (CSCsy54097)
Symptom When plugging or removing USB devices at BIOS Setup -> Advanced -> USB , the Setup Utility may hang.
Workaround Reboot the server. (CSCsz41907)
Symptom HTTPD process crashed, with the following event log:
Process crashed. Core file 1253640662_SAM_ucs-6120-1-A_httpd_log.3114.tar.gz (SAM/Switch Core Dump) detected on fabric interconnect A.
Symptom When more than 10 GUI sessions are open at the same time with remote authentication for a long time (typically for few hours), it has been observed that one of the GUI sessions fails to re-authenticate. This causes the session that fails re-authentication to close. Problem does not happen when local authentication is in use.
Workaround Re-login to the GUI session when it closes. (CSCtb05260)
Symptom When waking up from sleep, the Cisco UCS Manager GUI will detect an event sequencing error and display the error: "Event Sequencing is skewed" because the JRE doesn't have a sleep detection mechanism.
Workaround Always shut down the UCSM GUI before putting your computer to sleep. (CSCta94641)
Symptom When checking for UUID uniqueness, currently only the UUID suffix is checked.
Workaround Use a single UUID prefix. (CSCtc59481)
Symptom Downloads may be slow if TFTP is used.
Workaround If TFTP performance is slow, use SCP or another protocol. (CSCtb45761)
Release 1.0(1)
The following caveats were opened in UCS software Release 1.0(1e) and are still present.
Symptom Local user passwords cannot contain “$” character.
Workaround Do not include the “$” character in local user passwords. (CSCsz44814)
Symptom When using a fully qualified domain name (FQDN) of an LDAP provider, the FQDN is not resolved with DNS, and user authentication using the LDAP provider does not work.
Workaround Use an IP address instead of an FQDN when creating LDAP providers. (CSCta09972)
Symptom The IPMI user database in not backed up in the Cisco UCS Manager when you export a configuration backup.
Workaround After the configuration import is done, manually configure the IPMI user profile. (CSCta48483)
Symptom When a service profile containing two vNICs and having failover enabled is applied to QLogic or Emulex CNAs, the failback timeout specified in the adapter policy for the second vNIC has no effect. The failback timeout specified in the adapter policy and applied to the first vNIC is applied to the whole adapter and is effective for both vNICs.
Workaround Specify the desired failback timeout in the adapter policy and apply to the first vNIC. (CSCsz68887)
Symptom When a DCBXP peer on a physical interface sends two different unique identifiers in the protocol data unit in the same session, a DCBXP process error disables the port.
Workaround Enter the following commands and then wait for a minute for the port to come up:
Symptom When a blade server is powered on with a faulty DIMM, the BIOS POST detects the faulty DIMM and two SEL entries are sent to the BMC. One entry is logged for each DIMM.
Workaround Enter the BIOS setup and navigate to the Advanced > Memory Configuration menu to distinguish the faulty DIMM from its neighbor. (CSCsy97698)
Symptom Installing EFI Native SLES 11 is currently not supported in this release.
Symptom One vNIC defined in the Cisco UCS Manager service profile boot order results in two BIOS vNICs.
Workaround Avoid defining two different pxelinux.cfg/<MAC> files that have different boot/install instructions. When booted, both vNICs should execute the same PXE configuration. (CSCsz41107)
Symptom Without pin-group configuration, server interfaces are dynamically pinned to fabric interconnect uplink interfaces, and the pinning is redistributed as uplink interfaces go up or down. In some situations, the distribution of server interfaces across uplink interfaces is not even.
Symptom When a fabric interconnect boots, the “The startup-config won't be used until the next reboot” message appears on the console. Fabric interconnect configuration is controlled by the UCS Manager, so this message has no meaning on the fabric interconnect configuration and has no functional impact.
Symptom Console logon user names on the fabric interconnect are not case sensitive. For example, there is no differentiation between admin and ADMIN.
Workaround Use case insensitive user names. (CSCsy15489)
Symptom When you set TFTP core exporter IP address through the Cisco UCS Manager, the fabric interconnect accepts the address even if it is malformed; for example, 1.2.3.412. This has no functional impact to core exporter with valid IP addresses.
Workaround Remove the malformed core exporter IP address. (CSCsz75747)
Symptom When the system is under high stress, with repeated port flapping (ports rapidly going up and down) and default (native) VLAN change, the FWM process may core and cause the fabric interconnect to reload.
Symptom The show cdp neighbor CLI command does not display information for CDP neighbors seen from the management interface, nor does it display the fabric interconnect CDP information corresponding to the management interface.
Symptom Under some circumstances, syslog messages are not shown on a terminal monitor even though logging on the terminal monitor is enabled globally and on a particular session.
Workaround Use a different syslog destination, such as console, remote server, or local log file. (CSCta31689)
Symptom Even though there are no POST failures in the chassis, the Cisco UCS Manager sometimes displays the overall status of the chassis as POST-failure.
Workaround Check the chassis POST messages for errors, and if there are none, ignore the Cisco UCS Manager status message. (CSCsz01878)
Symptom In rare cases the Cisco UCS Manager reports the link absence fault between the fabric interconnect server port and the fabric extender during the internal inventory collection. The following is an example of such a fault:
Workaround Ignore the fault message; it will automatically get cleared after one minute. This will not impact the data path. (CSCta76573)
Symptom On a system with five or more chassis, the following sequence of events causes the system to not be HA ready for up to five minutes:
Workaround Wait for HA READY. (CSCsz40462)
Symptom After a full restore of the primary fabric interconnect, the subordinate fabric interconnect installation may temporarily fail with the following message:
Workaround Retry the fabric interconnect installation. (CSCsz85876)
Symptom Hardware revision numbers for fabric interconnect components are not populated in the Cisco UCS Manager.
Workaround Perform the following steps to determine the revision number for a fabric interconnect component:
1. Enter the connect nxos command to connect to the native NX-OS CLI.
2. Enter the appropriate show sprom component command and look for H/W Version: field in the command output. (CSCta12005)
Symptom All DIMMs are reported to be in array 1, and maximum memory for a blade is reported as 192-GB.
Workaround DIMMs may be physically located in array 1 or array 2, and the maximum memory is 96-GB. This is a display-only issue, and does not affect functionality. (CSCta56527)
Symptom In the Cisco UCS Manager GUI, you can only select port channels and individual uplink ports as pin targets, but the Cisco UCS Manager CLI allows you to also select port channel member ports as pin targets.
Workaround Port channel member ports should not be selected as pin targets, even if the Cisco UCS Manager CLI allows you to. (CSCta60495)
Symptom The assignment of servers to pools in a dynamic pool are not dynamically assigned. To have a server assigned to a pool, it must be re-acknowledged. This should happen automatically based on the server pool policy qualifications as soon as the qualification is associated to a pool.
Workaround Re-acknowledge the server to enable it as a candidate for pool assignment. (CSCta06882)
Symptom Local disk removal and insertion is not detected.
Workaround Select the Re-Acknowledge Server option in UCS Manager GUI to discover the server. (CSCsy80888)
Symptom The disk scrub policy needs enhancements to meet DOD compliance.
Symptom SNMP shows the fabric interconnect name rather than system name.
Symptom An SNMP user name cannot be the same as a local user name.
Workaround Select an SNMP user name that does not match any local user name. (CSCta24034)
Symptom Any SMASH command entered with wrong option should give “INVALID OPTION” error message.
Symptom Statistics counters cannot be cleared using the Cisco UCS Manager CLI.
Workaround Clear the counters using the Cisco UCS Manager GUI. (CSCsz47512)
Symptom When several KVM Consoles are launched, the SUN JRE sometimes reports an error and the KVM Console fails to launch.
Workaround Launch the KVM Console again. (CSCta38463)
Symptom In the Cisco UCS Manager GUI, if the Reboot on boot Order Change checkbox is checked for a boot policy, and if CD-ROM or Floppy is the last device in the boot order, then deleting or adding the device does not directly affect the boot order and the server does not reboot.
Symptom Fibre Channel port and server port events do not appear on the Fibre Channel port and server port Events tabs.
Workaround Look on the Admin Events tab for Fibre Channel port and server port events. (CSCta66375)
Symptom When the time-based UUID generation method is used in the uuidgen tool, the system reports duplicate UUIDs because UUIDs are validated based on their suffix, whereas time-stamp method creates UUIDs with unique prefixes, but non-unique suffixes.
Workaround Use the random method in the uuidgen tool to ensure that suffixes are unique. (CSCta40790)
New Hardware Features in Release 1.3(1)
Release 1.3(1y) adds support for:
- Version 2 of UCS B440 M1 and M2 Blade Servers. This new hardware version is part of a proactive replacement program. See Field Notice 63430 for further details.
Release 1.3(1c) adds support for the:
- Cisco UCS B-Series B440 Intel Xeon 7500-based 4-Socket blade servers
- Second generation Adapter cards:
–
–
–
New Software Features in Release 1.3(1)
Release 1.3(1t) has the following command modifications:
It is now possible to renumber the chassis number for a particular chassis as part of the recommission command.
If a chassis number is not given, the old chassis number is used.
The show chassis decommissioned command will not show the current chassis number allocated to the chassis, as in this example:
In the following example, the chassis will renumber to "6" on recommission:
The 1.3(1) release adds support for:
- UCS Manager now supports up to 14 chassis
- Blade level power capping (1c only)
- Setting additional BIOS parameters in service profiles
- Configure vCenter wizard
- 502 user configurable VLANs (excluding internal, reserved VLANs) including VLANs used for carrying up to 32 VSANs.
- SNMP traps extended to chassis and blades. UCS SNMP MIBs can be accessed here:
–
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html .
Subscribe to What’s New in Cisco Product Documentation , which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
This document is to be used in conjunction with the documents listed in the “Related Documentation” section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)