First Published: November 16, 2012 Updated: May 8, 2013 Part Number: OL-28313-01
This document describes system requirements, new features, resolved caveats, known caveats and workarounds for Cisco UCS Manager software Release 2.1. This document also includes the following:
•Current information that became available after the technical documentation was published
•Related firmware and BIOSes on blade and rack servers and other Cisco Unified Computing System (UCS) components associated with the release
Use this release note as a supplement with the other documents listed in documentation roadmap:
Created release notes for Cisco UCS Software Release 2.1(1a).
B0
2.1(1a)
December 12, 2012
Added notice regarding lack of support for Default Zoning from Cisco UCS, Release 2.1(1a) onwards.
C0
2.1(1b)
March 8, 2013
Created release notes for Cisco UCS Software Release 2.1(1b).
D0
2.1(1d)
March 25, 2013
Created release notes for Cisco UCS Software Release 2.1(1d).
E0
2.1(1e)
April 18, 2013
Created release notes for Cisco UCS Software Release 2.1(1e).
F0
2.1(1e)
May 8, 2013
Updated release notes for Catalog Release 2.1.1e.T.
Introduction
Cisco UCS™ Manager provides unified, embedded management of all software and hardware components of the Cisco Unified Computing System™ (Cisco UCS) across multiple chassis, rack servers, and thousands of virtual machines. Cisco UCS Manager manages Cisco UCS as a single entity through an intuitive GUI, a command-line interface (CLI), or an XML API for comprehensive access to all Cisco UCS Manager functions.
System Requirements
To use Cisco UCS Manager your computer must meet or exceed the following minimum system requirements:
•The Cisco UCS Manager GUI is a Java-based application which requires Sun JRE 1.6 or later.
•Cisco UCS Manager uses web start and supports the following web browsers:
–Microsoft Internet Explorer 9.0 or higher
–Mozilla Firefox 7.0 or higher
–Google Chrome 14.0 or higher
Adobe Flash Player 10 or higher is required for some features
•Cisco UCS Manager is supported on the following operating systems:
–Microsoft Windows 7 with minimum 4.0 GB memory
–Red Hat Enterprise Linux 5.0 or higher with minimum 4.0 GB memory
Note Mac OS X is not supported with Cisco UCS Manager 2.1 GUI.
Updating Cisco UCS Versions
Starting with Software Release 2.1, the UCS Manager A bundle software (UCS Manager, NX-OS, IOM Firmware) can be mixed with previous release's B or C bundles on the servers (host FW, BIOS, CIMC, adapter FW & Drivers). A given server must be running the entire B-bundle, so mixing the 2.0(3a)B BIOS with the 2.0(4b)B CIMC is not supported.
The following features are exceptions:
•Single root IO virtualization
•Power capping
•C-Series Single Wire Management
For detailed instructions for updating the Cisco UCS software and firmware, see the appropriate Upgrading Cisco UCS document for your installation.
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
Table 2 shows interdependencies between the hardware and versions of Cisco UCS Manager. Server FRU items such as DIMMs are dependent on their server type, and chassis items such as fans and power supplies work with all versions of Cisco UCS Manager.
1See the Software Advisory for the minimum firmware level required on the Cisco UCS C220 M3 and Cisco UCS C240 M3.
2N20-AI0002, the Cisco UCS 82598KR-CI 10-Gb Ethernet Adapter, is not supported on the B440 server but is still available for other models. We suggest you use the Cisco UCS CNA M61KR-I Intel Converged Network Adapter in place of the Cisco UCS 82598KR-CI 10-Gb Ethernet Adapter.
3The C-series integration using the Cisco Nexus 2248 Fabric Extender is no longer supported as of Release 2.0(2). See the UCS C-Series hardware documentation for details.
Capability Catalog
The Cisco UCS Manager uses the catalog to update the display and configurability of server components such as newly qualified DIMMs and disk drives. The Cisco UCS Manager Capability Catalog is a single image, but it is also embedded in Cisco UCS Manager. Cisco UCS Manager 2.1(x) releases work with any 2.1(x) catalog file, but not the 1.x or 2.0 catalog versions. If a server component is not dependent on a specific BIOS version, using it and having it recognized by Cisco UCS Manager is primarily a function of the catalog version. The catalog is released as a single image in some cases for convenience purposes in addition to being bundled with UCS infrastructure releases. See Table 3 for details on the mapping of versions to bundles.
Table 3 Version Mapping
UCS Release
Catalog File
Adds Support for PID
2.1(1a)A
ucs-catalog.2.1.1a.T.bin
UCSC-PCIE-CSC-02 for C-Series
UCSB-MEZ-ELX-03 for Cisco UCS B22 M3 and Cisco UCS B200 M3
UCSB-MEZ-QLG-03 for M3 servers
2.1(1b)A
ucs-catalog.2.1.1d.T.bin
UCS-CPU-E5-4617
UCS-CPU-E5-4650L
2.1(1d)A
ucs-catalog.2.1.1d.T.bin
—
2.1(1e)A
ucs-catalog.2.1.1d.T.bin
—
—
ucs-catalog.2.1.1e.T.bin1
—
.1- Available for separate download.
Further details are in the Cisco UCS Manager GUI Configuration Guide.
New Hardware Features in Release 2.1
Release 2.1(1b) adds support for the following:
•Cisco UCS B200 M3 blade server configurations with a single CPU
This patch release provides support for UCS B200 M3 blade server configurations with a single CPU, in addition to the previously supported dual CPU configurations.
Release 2.1(1a) adds support for the following:
•Cisco UCS CNA M73KR-Q Adapter for B-series M3
•Cisco UCS M73KR-E Adapter for Cisco UCS B22 M3 and Cisco UCS B200 M3
•VIC 1225 Adapter for C-series
•C420 M3 Server
New Software Features in Release 2.1
Release 2.1(1b) adds support for the following:
•BIOS Policy Settings—Provides the ability to select refresh interval rate for internal memory.
•Memory Speed—Enables 1333 MHz memory speed for 8GB/16GB 1600-MHz RDIMMs populated with 3 DIMMs Per Channel/1.5v on the Cisco UCS B200 M3 blade server and Cisco UCS C240 M3 rack server.
•Call Home—Enables you to configure call home for CMOS battery voltage low alert.
Release 2.1(1a) adds support for the following:
•Storage
–UCSM based FC Zoning - Direct Connect Topologies
–Multi-Hop FCoE
–Unified Appliance Port
–Inventory and Discovery Support for Fusion-IO and LSI PCIe Mezzanine Flash Storage (for UCS M3 blades)
•C-series Single Wire Management
•Fabric
–Sequential Pool ID Assignment
–PV Count Optimization (VLAN Compression. Only available on 6248/6296 Fabric Interconnect)
–VLAN Group
–Multicast Policy with IGMP Snooping and Querier
–Org-Aware VLAN
–LAN/SAN Connectivity Policies for Service Profile Configuration
–VCON Enhancement
–Cisco CNA NIC Multi-receiving Queue Support
–VM FEX for KVM SRIOV
–VM FEX for Hyper-V SRIOV
•Operational enhancements
–Firmware Auto Install
–Mixed Version Support (For Infra and Server bundles firmware)
–Service Profile Renaming
–Fault Suppression
–UCSM Upgrade Validation Utility
–FSM Tab Enhancement
–Native JRE 64 bits Compatibility with OS and Browsers
–Lower Power Cap Minimum for B Series
–RBAC Enhancement
–CIMC is included in Host Firmware Package (Management Firmware Package deprecated).
–Implicit upgrade compatibility check
•Support for UCS Central
Default Zoning is Not Supported in Cisco UCS, Release 2.1(1a) Onwards
Default zoning has been deprecated from Cisco UCS, Release 2.1(1a) onwards. Cisco has not supported default zoning in Cisco UCS since Cisco UCS, Release 1.4 in April 2011. Fibre Channel zoning, a more secure form of zoning, is available from Cisco UCS, Release 2.1(1a) onwards. For more information about Fibre Channel zoning, see the Cisco UCS Manager configuration guides for the release to which you are planning to upgrade.
Caution All storage connectivity that relies on default zoning in your current configuration will be lost when you upgrade to Cisco UCS, Release 2.1(1a) or a later release. We recommend that you review the Fibre Channel zoning configuration documentation carefully to prepare your migration before you upgrade to Cisco UCS, Release 2.1(1a) or later. If you have any questions or need further assistance, contact Cisco TAC.
Resolved Caveats
The following caveats are resolved in the 2.1(1e) release:
Table 4 Resolved Caveats in Release 2.1(1e)
Bug ID
Description
First Affected Bundle
Resolved in
CSCuf90470
When Call Home is enabled, Online Insertion and Removal (OIR) or failure of hardware modules in the FI no longer cause the FI to reboot.
2.1(1b)A
2.1(1e)A
The following caveats are resolved in the 2.1(1d) release:
Table 5 Resolved Caveats in Release 2.1(1d)
Bug ID
Description
First Affected Bundle
Resolved in
CSCuf14193
Upon upgrade to Cisco UCS Manager 2.1(1d), the FI no longer reboots due to callhome server hap reset when Call Home is enabled.
2.1(1b)A
2.1(1d)A
The following caveats are resolved in the 2.1(1b) release:
Table 6 Resolved Caveats in Release 2.1(1b)
Bug ID
Description
First Affected Bundle
Resolved in
CSCud56660
Duplicate license IDs will no longer cause LicenseAG process to core.
2.0(4d)A
2.1(1b)A
CSCud10237
The eight default port licenses for flexible GEM on the FI will be available for use.
2.0(3c)A
2.1(1b)A
CSCue38650
The UCSM PSU policy and IOMs are no longer out of sync after the IOMs are rebooted.
2.1(1a)A
2.1(1b)A
CSCud70368
UCS Central is now correctly creating the crossdomain.xml file on UCSM member domains.
2.1(1a)A
2.1(1b)A
CSCud40412
When regenerating a new keyring or certificate, the new certificate is now successfully published to the FI webserver and can be obtained by the http process.
2.1(1a)A
2.1(1b)A
CSCud53700
The portAG process no longer crashes while activating the Fabric Interconnect NX-OS software during upgrade.
2.1(1a)A
2.1(1b)A
CSCud59230
Port channels no longer go down after upgrading to UCSM 2.1.
2.1(1a)A
2.1(1b)A
CSCub22238
The Cisco UCS 6100 Series Fabric Interconnects no longer contain a vulnerability in the Netconf interface.
2.0(1a)A
2.1(1b)A
CSCud20253
Power capping on the Cisco UCS B420 blade server can now support 32GB DIMMS.
2.1(1a)A
2.1(1b)A
CSCue46817
After upgrading to Release 2.1(1b) or higher, a Cisco UCS B440 M1/M2 blade using a RAID key attached to a LSI MegaRAID SAS 9260 will no longer generate a "Missing RAID Key" fault alert.
2.1(1a)B
2.1(1b)A
CSCud27494
Traffic to a blade server will no longer be dropped and forwarded to another working link when an uplink is shutdown either on the fabric interconnect or from the upstream switch.
2.0(4b)A
2.1(1b)A
CSCud54919
On blade servers that are not associated with a service profile, CIMC could not respond from UCS Manager at the same time.
2.0(1t)B
2.1(1b)A
CSCuc38555
Legacy USB support items can no longer be changed in the BIOS setup.
2.1(1a)B
2.1(1b)A
CSCud19629
FCoE Uplink interface faults are now visible in the Cisco UCS Manager GUI.
2.1(1a)A
2.1(1b)A
CSCud20765
When defined through a service profile template, SRIOV virtual functions (VFs) are no longer populated incorrectly in the instantiated service profiles.
2.1(1a)A
2.1(1b)A
CSCuc44209
Cisco UCS Manager no longer displays the names for PSUs connected to a Cisco Nexus 2200 Series FEX in reverse order.
1.4(3l)C
2.1(1b)A
The following caveats are resolved in the 2.1(1a) release:
Table 7 Resolved Caveats in Release 2.1(1a)
Bug ID
Description
First Affected Bundle
Resolved in
CSCub51516
DHCP will no longer fail when multiple servers are restarted at the same time.
2.0(1e)A
2.1(1a)A
CSCuc27213
After upgrading from Cisco UCS 2.0(1s) to 2.0(3a), the Cisco UCS B200 M3 blade server no longer continuously reboots.
2.0(3a)
2.1(1a)A
CSCuc26566
The Cisco UCS 6200 Series fabric interconnect no longer reboots without a final confirmation warning after configuration changes.
2.0(4a)A
2.1(1a)
CSCtz07798
A service profile no longer generates configuration failures if the blade it is associated with is removed from the server pool.
2.1(0.208)B
2.1(1a)
CSCuc69455
A core dump caused by a memory leak is no longer seen when multiple VLANs are assigned to a service profile's vNIC.
2.1(0.489)A
2.1(1a)
CSCth96721
There is no longer a 128 character limitation to the number of OUs or the length of the Distinguished Name (DN) when using LDAP authentication with Active Directory.
2.0(1w)A
2.1(1a)A
CSCtt36593
The svcmonAG process no longer fails and core dumps regularly on a 14 chassis setup.
2.0(1)A
2.1(1a)A
CSCty34034 CSCub48862 CSCub99354 CSCub16754
Discovery, association, or disassociation no longer fails after a BMC firmware update with a message about the VIC adapter.
1.0(2a)
2.1(1a)B
CSCuc00368or CSCuc87155
With RAID1 mode configured with two disks on a Cisco UCS B230 blade server, removing and reinserting one disk no longer causes the second disk to be shown as inoperable while RAID 1 rebuild is in progress.
2.0(3a)A
2.1(1a)A
CSCuc24817
After FI reboot or FI failover, vEth is no longer shown as down when NX-OS shows it as up.
2.0(3c)A
2.1(1a)A
CSCuc27213
The Cisco UCS B200 M2 no longer goes into a continuous reboot loop after upgrading from 2.0(1s) to 2.0(3a).
2.0(3)A
2.1(1a)A
CSCuc59752
The snmptable command no longer fails to return any values.
2.0(2q)A
2.1(1a)A
CSCuc09958 or CSCua17646
A Java 1.7 detected error no longer occurs when downgrading from Cisco UCSM Release 2.0(3a) and later releases running JRE 1.7 to UCSM Release 2.0(2r) and earlier releases.
2.0(4a)A
2.1(1a)A
CSCtz86513
Registration emails from the SCH portal are now received after new inventory messages are sent from Cisco UCS Manager.
1.4(2b)A
2.1(1a)A
CSCtz76897
While upgrading or discovering the Cisco UCS Manager, when the chassis discovery policy is changed to the set link-aggregation-pref port-channel policy, the FEX no longer goes offline.
2.0(1m)A
2.1(1a)A
CSCtr45130
The blade server no longer reboots when activated after upgrading from Cisco UCS Manager Release 1.4(1j) to 1.4(2b).
1.4(2b)A
2.1(1a)A
CSCub64209
FCoE packets are no longer dropped when host-control is enabled in QOS policies assigned to VNICs.
2.0.67 B
2.1(1a)B
CSCtz79579
Cisco UCS Manager no longer reports an incorrect status for faulty disks that fail to power on or link up.
2.0(2.83)B
2.1(1a)B
CSCub34939 CSCty33146
After upgrading Cisco UCS Manager, an SNMP crash no longer reboots both FIs during activation.
1.4(3s)A
2.1(1a)A
CSCuc35326
The Cisco UCS B200 M3, B22 M3, and B420 M3 Blade Servers no longer experience `Server Hardware Not Supported' or discovery errors when upgrading from Release 2.0(2) to Release 2.0(3) or 2.0(4) and the blades are inserted into a UCS DC chassis.
2.0(3a)A
2.1(1a)A
CSCtw59592
In a server using both a virtualized adapter card and a nonvirtualized card, extraneous NIC ports are no longer generated if there are fewer service profile vNICS than the minimum required physical NIC ports.
2.0(1t)A
2.1(1a)A
CSCtj62296
The minimum power cap that can be set is no longer 3400W.
1.4(1i)A
2.1(1a)A
CSCtc86297
After a VM restarts, the virtual machine node on the VM tab no longer shows multiple instances of the same VM with one online and one offline.
1.1(1j)A
2.1(1a)A
CSCta66375
Fibre Channel port and server port events now appear on the Fibre Channel port and server port Events tabs.
1.0(1e)A
2.1(1a)A
CSCtu34607
Changing the dynamic vNIC policy to change the number of vNICs no longer causes static vNICs to get reordered on PCIe bus.
2.0(2m)A
2.1(1a)A
CSCuc72049
When creating an access mode appliance port-channel in UCS Manager, the default VLAN is no longer used instead of the specified VLAN.
2.0(3a)A
2.1(1a)A
CSCtx65534 CSCua31267
Deleting a VLAN in the Fabric Interconnect no longer causes the vNICs that are carrying that VLAN to flap.
2.0(2q)A
2.1(1a)A
CSCtn87981
Cisco UCS B230 and B440 blade servers with Cisco UCS M81KR and 82598KR-CI adapters no longer fail with an "illegal fru" error.
2.0(1m)
2.1(1a)A
Open Caveats
Release 2.1(1)
Table 8 Open Caveats in Release 2.1(1e)
Bug ID
Symptom
Workaround
First Bundle Affected
CSCud60746
When Call Home is enabled, there is a low chance that the system may run out of memory. This occurs after 365,000 Call Home messages have been sent out, or approximately 4700 inventory messages are generated. This could result in one of the following:
•The primary Fabric Interconnect may reboot with the following reset reason:
Service: callhome server hap reset
•Upgrading the firmware in the primary FI may fail due to the /isan folder filling up.
To reduce the frequency of memory leaks caused by Call Home messages:
1. Reduce the number of Call Home messages by disabling any unnecessary Call Home policies or modifying alert groups and/or profile levels.
2. Reduce inventory message generation.
To completely prevent any memory leaks due to Call Home, disable Call Home.
If the primary FI firmware upgrade fails, contact Cisco TAC to cleanup the /isan directory.
2.0(2q)A
CSCuf78224
On a Cisco UCS B440-M2 server with Cisco UCS CNA M72KR-Q adapter card, VMware Auto Deploy 5.1 hangs during boot.
Using ESXi 5.0 gPXE instead of ESXi 5.1 iPXE may work under some conditions, but booting time is slow.
2.0(4b)A
CSCug26974
For servers with Cisco UCS M71KR-E or UCS CNA M71KR-Q adapters, changing ethernet adapters policy parameters can unnecessarily trigger a reboot on servers with that policy.
Avoid changing any ethernet adapter policy parameters except for Failback Timeout for servers equiped with Cisco UCS M71KR-E or UCS CNA M71KR-Q adapters.
2.1(1d)B
CSCug21589
When fabric failover occurs on a VMware ESXi host with fabric failover configured, the MAC address of the ESXi host is sent to the uplink switch. In some circumstances, the MAC address of the guest OS is not sent, which causes the network link to go down.
Generate a ping from the corresponding VM to any external hosts.
2.1(1a)T
Table 9 Open Caveats in Release 2.1(1d)
Bug ID
Symptom
Workaround
First Bundle Affected
CSCuf17523
NX-OS reports that the FI port is down, but the interface counters show it is still receiving traffic. This condition occurs when the port speed is changed when the port is administratively down.
Administratively enable and administratively disable the port.
2.1(1a)A
CSCuf07670
Latency spikes may be reported on ESXi servers due to the virtual machines losing connections to the storage datastores. This condition occurs when storage datastores are presented through the FCoE uplinks using Cisco UCS and Cisco Nexus 5000 series switches.
This issue has no known workaround.
2.1(1a)A
CSCuf01402
Modifying a service profile with two iSCSI vNIC targets defined prompts for a reboot before the second target can be configured.
To configure the second target, modify any attribute in the Service Profile. Accept the reboot prompt to configure the targets properly.
2.1(1a)A
CSCuf35678
When VLAN port count optimization (VLAN compression) is enabled on a Cisco UCS 6200 series fabric interconnect, if an uplink port channel port goes down, all traffic may stop.
Remove VLAN from VLAN compression.
2.1(1a)A
..
Table 10 Open Caveats in Release 2.1(1b)
Bug ID
Symptom
Workaround
First Bundle Affected
CSCud59815
When assigning FC ports on the 62xx FI using the slider, all ports are enabled by default. If the number of ports allocated is greater than the license allotment, license faults are generated and ports can go into grace period.
Disable the FC ports that are not actually going to be used.
2.0(2q)A
CSCue48076
If there are more than 21 IP addresses in the ext-mgmt ip pool, adding a subordinate FI to a standalone FI to convert into a cluster causes the console to hang.
Reduce the number of IP addresses in the ext-mgmt ip pool to 19 or less, and add the subordinate FI. After the cluster is formed successfully, you can add the IP addresses that were removed back into the ext-mgmt IP pool.
2.1(1a)A
CSCue47159
In a UCS chassis with one or more empty slots, UCSM may show a critical alert and a "FSM Failed" warning for a slot that has no blade.
1. Insert a spare blade into the slot which has the alert.
2. After the discovery process has completed successfully, check for the error message if it goes off.
3. Decommission the server from UCSM using the "Server Maintenance" link.
4. After the decommission process has completed successfully, remove the server from the slot.
2.1(1a)A
CSCud81176
After manually upgrading the CIMC and associating a service profile, the CIMC upgrade may fail while the status remains at Activating.
Remove the Management Firmware pack to activate the firmware of CIMC. A non-harmful fault is generated which can be acknowledged.
2.1(1a)A
CSCud75506
The UUID is translated incorrectly when you upgrade ESXi from version 4.1 or 5.1 on the Cisco UCS B200 M3, B220 M3, or B440 M3 blade servers.
This is a display issue only, and does not affect the service profiles associated with the blades.
This issue has no known workaround.
2.0(2r)A
CSCud55036
With the vNIC template, the VLAN ID is always displayed as 1 instead of the configured VLAN number.
This is a display issue only.
Use the show vlan command to obtain the correct VLAN ID.
2.0(2m)A
CSCue49366
Symptoms include transient UCSM faults related to a shared UCS Chassis I2C devices, such as a fan module, PSU, or the shared storage located in the UCS Chassis SEEPROM. These faults may include the terms "fan inoperable", "PSU", or "shared storage".
The detailed or brief tech-support command shows the chassis segment norxack count is high and increasing (hundreds or thousands depending on IOM uptime).
This high rate of i2c access errors shows that the IOM is not backing off of the shared I2C bus for the required amount of time. As a result one or both of the IOMs are interfering with each other's access to shared I2C resources and neither may be able to get useful work done.
This issue has no known workaround if uninterrupted high-availabiltiy service is desired.
If non-redundant operation is tolerable, you could pull one IOM from the chassis.
Powering down the entire chassis for 3 minutes and re-applying power may clear the condition in the short-term.
2.1(1a)B
CSCue65877
Under certain conditions when upgrading to Release 2.1(1), the storaged daemon generates core files.
This issue has no known workaround. The storaged daemon is a monitored daemon that restarts automatically. System operation continues unabated and performance is not negatively impacted.
2.1(1a)A
CSCud70315
When a port channel member transitions between up and down states, fabric channel traffic on the port channel is dropped. A SCSI timeout occurs, and the SCSI layer triggers the recovery.
This issue has no known workaround.
Proper SCSI timeout values will help in recovery.
2.0(4a)A
CSCud86528
Blades Power off during firmware update.
Use the "Boot Server" option from the service profile to keep the power states between the service profile and associated physical server in sync. Do not use the "Reset" option as displayed in Cisco UCS Manager's warning message.
2.0(3b)B
CSCue04360
After you boot, the B200 M3 servers hang after few days, with PECI errors.
Reboot the server.
2.0(3a)A
CSCue29352
When you try to change the boot order without checking the options "local storage change" and "Reboot on Boot Order Change", the server is listed in pending activities list.
Select the "Reboot on Boot Order Change" check box to trigger a server reboot.
2.0(4d)A
CSCud89583
Cisco UCS B440 Blade server running Citrix XenServer 6.0.2 with E7-4830 and all C states disabled has a "CATERR_N" error and freezes. The host IP of the blade is unreachable, and KVM, the front panel dongle and SOL do not function.
Power cycle the blade.
2.0(3a)A
CSCud27864
BIOS hangs during POST when memory mapped IO above 4 GB is enabled and UCSB-MEZ-QLG-03 is present in the blade.
Disable memory mapped I/O above 4 GB.
2.1(1a)A
CSCud74915
After creating a new service profile using VM-FEX, a duplicate VIF is seen which prevents you from connecting to the original blade server.
1. Disassociate both blades from their service profiles.
2. Reassociate only one blade.
3. Recreate the service profile for the other blade.
2.0(3a)A
.
Table 11 Open Caveats in Release 2.1(1a)
Bug ID
Symptom
Workaround
First Bundle Affected
CSCtz15707
When the Cisco UCS C24 M3 server has more than 16 hard disk drives installed, creation of RAID 10 using a CISCO UCS Manager Service Profile fails for the server. Other supported RAID levels are not affected.
Use either one of following two options:
•Reduce number of installed hard disk drives less than 17.
•Use LSI WebBIOS Configuration utility during server boot to manually create RAID 10 when more than 16 disk drives are required for RAID10 configuration. Press CTRL+H during server BIOS POST to launch LSI WebBIOS Configuration utility.
2.0(3a)
CSCud11400
On a scale setup, the fwm process on the FI may crash during server reack.
The crash can happen when a port-channel member is being brought up. On scale setups, when there are triggers which flap the ports, a race condition between multiple processes on the system results in incorrect cleanup leading to the crash. The system recovers after the process restarts.
There is no currently known workaround.
2.1(1a)A
CSCud19629
FCoE Uplink interface faults are not visible in UCSM GUI under SAN_Tab -> Fabric A -> Uplink FCoE Interfaces -> FCoE Interface.
Faults are available at the parent node level under SAN_Tab -> Fabric A, which includes FCoE uplink interface faults.
2.1(1a)A
CSCuc59299
When downloading a firmware bundle, ethpm crashes with 'Out of Memory: Killed process' error and the FI reboots.
There is no currently known workaround.
2.1(1a)A
CSCud19730 or CSCuc81667
Cisco UCS C220 and C240 servers running Cisco USM Manager Release 2.0(2) may experience a PCI bus number change when upgrading or downgrading the BIOS. This can cause the following:
•Storage controller update failure from Cisco UCS Manager when upgrading to Release 2.1.
•OS installations such as VMWARE requiring manual intervention after bus number changes are seen.
To avoid the Cisco UCS Manager update issue either via the host firmware pack or through the firmware auto install, you should update to Release 2.0(3) before upgrading to Release 2.1.
If you have already upgraded to Release 2.1 and see an "Unable to find Storage Controller Device" error, reacknowledge the servers to fix the issue.
Note It may take up to 20 minutes for the failed firmware update attempt to timeout in UCS Manager before the server reacknowledge is started. The firmware update completes successfully during the reacknowledge task.
For VMWARE installation, the PCI mapping has to be manually changed using the ESX console.
2.0(3a)A
CSCud20765
When SRIOV vNICs are defined though a vnic template which is referenced by a service profile template, then twice the number of VFs as specified in the dynamic connection policy are created in the instantiated service profiles.
When a service profile template (with update-template type) is updated, the SRIOV VFs in its instantiated services profiles will be erased.
Avoid using service profile templates for SRIOV VFs. Use service profiles directly.
2.1(1a)A
CSCud00607
IGMP membership may not be cleaned properly for some veth interfaces.
When IGMP joins for the same group are sent from multiple interfaces concurrently, sometimes the cleanup in the forwarding table doesnot happen properly. Note that the problem does not manifest when normal group expiry happens, but could happen when a re-ack of the server happens.
There is no currently known workaround.
2.1(1a)A
CSCuc59299
When downloading a firmware bundle, OOM kills ethpm causing a reboot of FI, and no core is generated. The following message is shown:
This has been seen with a setup with a very large number of VIFs. For example, a setup with >2000 VIFs. Here ethpm is a victim as the kernel ran out of memory. An ethpm crash resulted in a FI reboot. The current VIF support count is 2000.
There is no currently known workaround.
2.1(1a)A
CSCuc19701
When the Fabric Interconnect (FI) is reset, there is a small possibility that the IOM may reboot. This has been observed only with the 2204 IOM.
The IOM reboot is due to the satctrl process crashing. This is due to a race condition and is seen in scaled setups. The occurrence is rare, and the system recovers after the IOM reloads.
There is no currently known workaround.
2.1(1a)A
CSCuc67344
In a very rare case, UCSM failed to re-start due to the same UUID being allocated to two different service profiles.
So far, this is only been observed for UUID pools and not for other ID's such as Mac, WWXN , IP etc.
This could be a day-1 implementation flaw happening in rare conditions.
a) A static UUID is assigned to a service profile which is associated.
b) In the single transaction, delete the service profile and create a new
service profile (with different name) with the same UUID suffix and UUID Pool.
This can only be achieved thru import (with replace option), XMLAPI or CLI and modify the pool prefix.
The expected behavior is that the UUID is correctly assigned to the new service
profile and the pools reflect that. In some cases, the pool shows the allocated address as unassigned.
c) Define a pool with the same UUID in the pool, create additional service profiles.
This will lead the same UUID be potentially allocated to the newly created service profiles
Avoid the condition where the same UUID can be released and then allocated in the same transaction. For example, do not delete a service profile with statically assigned IDs and then create the new service profile with the same static ID in one transaction. Also avoid importing with 'replace' option when the existing configuration and the configuration to be imported have overlapping IDs being assigned to different service profiles.
If UCSM fails to re-start, contact Cisco TAC for further assistance.
2.1(1a)A
CSCub48664
Rack server with Cisco UCS VIC 1225 adapter may fail discovery after decommission and re-commission.
Power cycle the entire rack server.
2.1(1a)A
CSCuc69455
UCSM's DME process may core dump when creating large number service profiles with large number of vnics and large number of vlans on each vnic in a single operation.
On a 6200 FI, the UCSM DME process may core dump during the following large scale operations:
•Creating 300 service profiles with 32 static vnics in each service profile and 50 vlans on each vnic
•Creating 200 services profiles with 32 static vnics in each service profie and 850 vlans on each vnic and then deleting all of the service profiles and repeat this process multiple times
The same could happen on a 6100 FI with a similar or smaller scale.
There seems to be a memory leak issue which only shows up when very large of MOs are committed in a single transaction. The same issue exists in previous releases (tested with 2.0(4b)) as well.
It has been verified that there is no memory growth with reduced numbers such as:
•Creating and then deleting 100 service profiles with 2 vnic in each service profile and 100 vlans on each vnic
•Creating and then deleting 20 service profiles with 32 vnics in each service profile and 50 vlans on each vnic.
When creating large number (>100) service profiles with large number vnics (>16 ) and large number of vlans (>50) on each vnic, avoid using a single operation to create all the service profiles. Break it down into multiple operations with a smaller number (such as 20) of service profiles in each operation.
2.1(1a)A
CSCuc59062
When installing ESX 5.1 to a san lun using a M73KR-Q adapter, LUN discovery fails.
This is seen because the Qlogic drivers are not present on the standard ESX 5.1 installation ISO.
Cisco will be releasing an ESX 5.1 custom ISO that will include the required M73KR-Q driver.
2.1(1a)C
CSCuc64210
The import of an all-configuration or system-configuration file fails with the error message "System is in suspend state. Policy ownership cannot be changed to GLOBAL"
The all-configuration or system configuration file that is being used for import would have been taken when the system was registered with UCS Central and was in suspend state.
None. However, logical configurations and full-state backups taken during this state can be restored.
2.1(1a)A
CSCuc77561
A "named-policy-unresolved" fault is suppressed during pool-name resolution.
Since the resolution can happen from remote (UCS Central), we suppressed the fault for pool name resolution for the pools of type IP, WWN, UUID, MAC and IQN.
There is no currently known workaround. This is a change in behavior in the 2.1 release.
2.1(1a)A
CSCud00607
IGMP membership may not be cleaned properly for some veth interfaces.
When IGMP joins for the same group are sent from multiple interfaces concurrently, sometimes the cleanup in the forwarding table does not happen properly. Note that the problem does not manifest when normal group expiry happens, but could happen when a re-ack of the server happens.
There is no currently known workaround.
2.1(1a)A
CSCud71175
When adding an additional port to a fabric port-channel that only has a single member port, an HIF down event is triggered to accomodate the extra VNTAG space and provide extra VIF deployment.
There is no currently known workaround. This is a rare situation that typically does not happen in a traditional port-channel deployment.
CSCud70315
When a member of a port channel transitions between up and down states, there is a loss for traffic on the port channel, including fiber channel traffic. The throughput for fiber channel goes down and then recovers. This is caused by a SCSI time out and the recovery is triggered by the SCSI layer. The throughput may go down to 0 before recovery, but the application will not see any timeouts.
This issue has no known workaround. Proper SCSI timeout values help in recovery.
CSCud71175
When there is a single member port in a port channel, and an additional port is added to the fabric port channel, an HIF down event is triggered to accomodate the extra VNTAG space and provide extra VIF deployment. This occurs when the new link is added to same ASIC. The link will automatically be added and lead to the symptom. If the port is on a different ASIC, then the added link must be chassis-acknowledged. The symptom will be seen after the acknowledgement.
This issue has no known workaround. This is a rare situation that typically does not happen in a traditional port-channel deployment.
CSCud71227
FWM crash and and the switch reboots when you start with one link, add a second link on the same ASIC, then delete the second link and move it to a different chassis.
Acknowledge the chassis.
Note Acknowledging the chassis will cause traffic drop.
Open Caveats from Prior Releases
The following caveats were opened in previous UCS software releases and are still unresolved.
.
Table 12 Prior Open Caveats
Bug ID
Symptom
Workaround
First Bundle Affected
CSCud93569
When upgrading from Release 1.4, the FI firmware NX-OS code fails because the MTS queues run out of space due to SNMP messages.
Reload the FI, check the mts buffers summary, and once they are clean proceed with the upgrade again.
2.0(3a)
CSCub55065
The service profile association failed and the server is shown as "Activating/Updating" status.
This is seen when a server is running a non-interruptible configuration (such as a BIOS image update), disassociating/associating the same server may cause server configuration to stick at the "Activating/Updating" stage.
(1) Trigger "Decommission and re-commission" on the server.
(2) Recover the corrupted BIOS.
2.0(3a)B
CSCuc26744
If a blade has a boardController firmware, then cannot use "Activate Frimware All" option from GUI.
If the CIMC and BoardController firmware are activated at same time using Activate Firmware All, then activation will fail. This is known restriction from hardware. Since we use CIMC for activating BordController, if we reboot CIMC when BoardController activation is in progress, it can cause the blade to get corrupted requiring RMA.
1. After doing "Activate Firmware ALL", go to individual BoardController components and change the startup version to same as running version.
OR
2. Activate all the Board Controller components by selecting "BoardController" in the Activate Firmware filter. After this is done, then do Activate Firmware ALL for all other components
2.0(4a)A
CSCuc47156
In UCS 2.1 setup, if user configured Host Firmware Package to include CIMC, after activate UCSM to 2.0, user can't update CIMC anymore.
Manually upgrade CIMC on each server.
2.0(4b)A
CSCuc82895
When downgrading UCS Manager from Release 2.0(4b) to lower releases, for example, Release 2.0(3c), Release 1.4.4, or Release 1.3.1, the license count displayed and available might incorrectly be greater than the licenses you have obtained.
There is no currently known workaround.
2.0(4b)A
CSCuc26566
The Cisco UCS 6200 Series Fabric Interconnect reboots without a final confirmation warning after configuration changes.
There is no currently known workaround.
2.0(4a)A
CSCuc08556
A Cisco P81E CNA card installed in slot #2 on a Cisco UCS C240 might experience network disruptions with Release 2.0(2), Release 2.0(3) or Release 2.0(4).
Try one of the following:
•Move the P81E card to slot #5.
•Leave the P81E card in slot #2, and install an additional PCIe card in slot #3.
2.0(4a)A
CSCuc66914
A global VLAN goes missing on an FI after rectifying a conflicting FCoE VLAN condition after upgrade from 1.4.1 to 2.0(4a) or later.
In releases 1.4 and prior a VLAN could be configured to be used both as regular Eth VLAN and as an FCoE VLAN. In the example illustrated in this defect VLAN 20 is both an FCoE VLAN for VSAN 20 and a global VLAN.
In 2.0 and later releases, this is an unsupported configuration. VLAN 20 cannot be both an FCoE VLAN and regular Eth VLAN. Accordingly faults are raised when system is upgraded from any pre-Capitola release to Capitola or later to bring attention to the VLAN misconfiguration.
Faults observed:
VLAN default is error-misconfigured because of conflicting vlan-id with an fcoe-vlan
VLAN20 is error-misconfigured because of conflicting vlan-id with an fcoe-vlan
To rectify this, user assigned a new VLAN (2020) as the FCoE VLAN for the VSAN. This triggers re-configuration of VLAN 20 and in the process, some times, VLAN 20 may get completely removed from NXOS configuration.
Due to this any host that is carrying VLAN20 will see a service outage
There are two options based on whether you want to retain the existing VSAN-VLAN assignment or retain the VLAN as global VLAN.
1) If the intent is to retain the VLAN as a global VLAN then after changing FCoE VLAN assignment, delete and re-create the missing VLAN (20 in the example). The VLAN will get correctly reconfigured on NXOS.
Or
2) If you want to retain the VLAN as an FCoE VLAN, then assign a different VLAN for the veths using it.
This error situation can only be reached through an upgrade workflow from a pre-2.0 release. In a 2.0 or later release, you are prevented from configuring a VLAN to be both FCoE and regular VLAN. So it is better to plan the re-assignment of VLANs as part of upgrade window downtime
2.0(4a)A
CSCuc47311
When a UCS chassis using DC power supplies (PSU) abruptly loses power to the PSUs, the PSUs may exhibit a RED LED Fail status after power is restored.
Remove and reinsert the PSUs.
2.0(3c)B
CSCub20455
When testing the Twinax cables between IOMs and FIs or one of IOMs, blade discovery happens and displays B230M2"Mismatch Identity Unestablishable".
Try one of the following:
•Reset CIMC
•Change the server to a different slot.
2.0(3a)A 2.0(2r)C
CSCuc65457
In some rare conditions the bladeAG process crashes and creates a core dump.
None. The process recovers automatically after the crash as it restarts.
2.0(3a)A
CSCuc88168
6140 Fabric Interconnect reboots upon snmp crash.
The cause of this is under review. If the UCSM version is below 2.0(1t), please see CSCtt99770
Disabling SNMP on the FI may help prevent re-occurrence of the issue.
2.0(3a)A
CSCuc65457
The svc_sam_bladeAG service crashes and creates a core dump.
There is no currently known workaround.
2.0(3a)A
CSCuc52981
Downloading licence files for the Cisco UCS 6100 and 6200 Series Fabric Interconnects appears to complete successfully, but the license files are not visible.
Obtain a single license file with all licenses consolidated, and use that license file to license the FIs.
2.0(3a)A
CSCuc51258
When RedHat OS was left in idle for some time, the Keybooard/Mouse might become unresponsive with certain blades.
This is seen randomly, and might be caused by combined error conditions . No reports of ESX hanging when running similar tests on the same hardware.
When doing disable/enable cycle on Frequency scalling from RH OS kernel, it improved the system stability and the platform previously failed within 30 minutes, but will no longer fail
2.0(3)A
CSCty23519
On a UCS 6120 or 6140 Fabric Interconnect with 20 chassis, some UCSM processes such as svc_sam_dme and svc_sam_bladeAG crash with the following message:
%KERN-1-SYSTEM_MSG: Proc svc_sam_dme (5082)
with Total_VM 706000 KB Resident_Mem 544156 KB
Anon_Resident_Mem 501068 KB being killed due to
lack of memory - kernel
This issue is only seen after repeated reack, association, disassociation, decommission, and recommission of the chassis in a fully populated testbed.
This issue has no known workaround. The processes are restarted automatically.
2.0(2r)A
CSCua31847
While upgrading from Release 1.4(3l) to 2.0(2q), the controller on IOM displays an error message during the upgrade process.
There is no currently known workaround. This is a firmware issue.
2.0(2q)A
CSCua50442
Third party tools such as dmidecode, ipmitool, etc... may not parse the entire Product Info Area of the B-series FRU. If the 3rd party tool does parse the entire Product Info Area of the FRU, it may show a non-printable ASCII character in the Product Type/Version Field or leave it blank or show a replacement character for the non-printable ASCII character.
The conditions depend on the third-party tool.
At this moment, please contact Cisco technical support if the customer's IT infrastructure relies on proper display of the product type/version id in the Product Info Area.
2.0(2q)A
CSCua50442
Third party tools such as demicode, IPMItool etc. may not parse the entire product information for the B-series server. If it does parse, you may see non-printable ASCII chanracters, blank or replacement ASCII characters in the Type/Version field.
Contact Cisco technical support.
2.0(2q)A
CSCua19893 or CSCtx41004
Some of the Fibre Channel ports that are part of the san-port-channel on the Fabric Interconnect (FI) fail to come up after reboot of the Fabric Interconnect. This issue usually happens when there is a large number of member ports (for example. more than 8) in the san-port-channel.
Disable or enable the failed member ports on the Fabric Interconnect and the ports will be operationally up again.
2.0(1w)A
CSCuc58056
"Inventory is not complete" errors received after displaying FI inventory.
None.
2.0(1w)A
CSCuc82601
All IOMs connected to an FI experienced a link flap while the peer IOMs remained connected.
Recovery occurs automatically within 15 seconds. Reboot any servers that are still experiencing connection issues to resume FC connectivity.
2.0(1t)A
CSCtz93271
Some VFC interfaces are disabled with an error message after rebooting the Fabric Interconnect.
Reset the DCE interfaces on the affected adapters and ports.
2.0(1t)A
CSCuc91387
UCS fault for "FSM-STAGE:sam:dme:FabricEpMgrConfigure:begin" alarms accompanied by a momentary loss of connectivity on one fabric.
DME logs a change on nw element triggering the reconfig:
INFO][0xac30dbb0][Oct 20
02:21:11.425][app_sam_dme:setElement] nw
element operability changed (old=1)(new=0)
Check quorum chassis(s) I2C logs for inability to read PSU hub:
segment 4 psu
norxack 4
timeout 13818531
unfinished 17
lostarbitration 1
fixup 27587498
pca9541clrerrprs 3
pca9541seterr 8
pca9541postio 1
pca9541postio2 1
pca9541postio3 1
wait_gt_deadline 1298217
hub_sw_mbb 13768948 : this looks wrong
hub_sw_mbb_to 13768948 : this looks wrong
1. Upgrade to 2.0(4b)
2. Ask TAC to check system against "Transient_Chassis_Thermal_Faults_or_Fan_Problems" procedure.
2.0(1t)A
CSCub19173
When adding multiple VLANs, MAC learning fails with resource exhaustion.
Reduce the number of VLANs.
2.0(1s)A
CSCub11507
In some conditions, a blade using a UCS M81KR adapter may lose communication to UCS Manager and prevent the OS from communicating to the network.
Reboot the blade server.
2.0(1q)
CSCtq77181
The fNIC driver rate limit feature does not work for vHBA devices supported by the VIC 1280, VIC 1240, and VIC 1225 adapters.
This issue has no known workaround. Do not configure the rate limit on vHBA devices hosted by these adapters.
2.0(1m)B
CSCtw59783
LEDs for ports 1 and 2 on a UCS 6296 behave differently than other ports.
There is no currently known workaround.
2.0(1m)A
CSCtu17983
ESX boot on blades using VMWare Auto Deploy takes a long time.
There is no currently known workaround.
2.0(1m)A
CSCtl04744
Network connectivity is affected (flapping on uplink ports) on both fabrics during operations such as native VLAN change when the configuration change is done on both interconnects at the same time.
Schedule a maintenance window to perform such configuration changes, and perform the changes separately.
2.0(1m)A
CSCtz99795
When two Cisco UCS systems push the same VLAN profile, the port profile from one Cisco UCS system disappears.
Modify the maximum port in the port profile of the first Cisco UCS system and save the configuration. The port profiles are now displayed in both the Cisco UCS systems.
1.4(3u)A
CSCub58460
A PortAG crash is observed during a downgrade of UCS Manager from any release that supports a 2232 FEX, to version 1.4. This is seen when the management image is downgraded to 1.4 but system and kernel images are at 2.1.
Either decomission the 2232 FEX before doing the downgrade or just ignore the crash until the downgrade is done where in all the FI images running correspond to the prior release.
1.4(3q)A
CSCuc44209
Cisco UCS Manager displays the names for PSUs connected to a Cisco Nexus 2200 Series FEX in reverse order.
There is no currently known workaround.
1.4(3l)C
CSCth69032
When Cisco UCS Manager is operated in High Availability mode, SNMP traps stop arriving as expected if the SNMP trap IP header source address field is set to the cluster virtual IP address.
SNMP trap recipients must not use the SNMP trap IP header source address, or be prepared for it to contain the management IP address of the currently primary fabric interconnect.
1.4(1i)B
CSCtn09020
If the installed DIMMs do not have thermal sensors (the most likely cause as this warning is logged during initial system memory initialization) or the installed DIMMs exceeded the thermal threshold values programmed in either the memory controller or the Memory buffer, then the RankMargintest file in the CIMC shows the following warning code:
There is no currently known workaround. The message is informational, and can be ignored.
1.4(1i)A
CSCtj93577
The Blade CIMstic management IP address assignment is not included in backups.
Manually record the blade CIMC static management IP address assignments, and re-enter them if necessary.
1.4(1i)A
CSCtf73879
Cisco UCS B200 M3 and Cisco UCS B22 M3 servers currently do not support disk status, failures, fault codes, and alarms from the MegaRAID controller.
There is no currently known workaround.
1.4(1i)A
CSCtf84982
For the MegaRAID Controller on the B440 blade server, Cisco UCS Manager fails to report BBU Status, Properties and Errors.
There is no currently known workaround.
1.4(1i)A
CSCtj48519
If one or more conditions are met, Cisco UCS Manager fails to capture certain Local Disk errors. Conditions include: Mixing the SAS and SATA Local Disks in the same server; Disk spin-up or disks present but not reaching 'Ready' state; Missing Disks.
There is no currently known workaround.
1.4(1i)A
CSCtf17708
Cisco UCS Manager does not include the implementation for the Write Through, Write Back, and Write back with BBU MegaRAID Battery (BBU) Write Policies for the B440 server.
There is no currently known workaround.
1.4(1i)A
CSCti39470
Cisco UCS Manager currently does not support RAID 50 and RAID 60.
There is no currently known workaround.
1.4(1i)A
CSCte58483
The PCIe Address for the Cisco UCS M81KR Virtual Interface Card is not seen in the GUI (or CLI). It causes no functional impact.
The only workaround 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.
1.1(1j)A
CSCtb35660
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.
Connect IOM1 to fabric-interconnect A, and IOM2 to fabric-interconnect B.
1.1(1j)A
CSCsz41107
One vNIC defined in the Cisco UCS Manager service profile boot order results in two BIOS vNICs.
Avoid defining two different pxelinux.cfg/<MAC> files that have different boot/install instructions. When booted, both vNICs should execute the same PXE configuration.
1.0(1e)A
CSCsy20036
The disk scrub policy needs enhancements to meet DOD compliance.
There is no currently known workaround.
1.0(1e)A
CSCsv87256
Any SMASH command entered with wrong option should give "INVALID OPTION" error message.
There is no currently known workaround.
1.0(1e)A
CSCtt24695
Sometimes FEX host facing ports are not created/discovered in Cisco UCS Manager at the end of chassis/server discovery. This results in Cisco UCS Manager assuming that the adapter has connectivity to only one fabric. So that blade server cannot be used to associate with a service profile which has VNICs that require both fabric or the fabric to which connectivity is not yet discovered. This happens very rarely during chassis and server discovery.
Re acknowledge the server (or chassis) so that Cisco UCS Manager attempts discovery once again.
2.0(1o)A
CSCuc68863
Newly installed 8 GB DIMM shows as "Equipped Identity Unestablishable" and "invalid FRU" in Cisco UCS Manager.
There is no currently known workaround..
Under some rare circumstances, blade discovery fails due to FRU corruption after upgrading from Release 2.0(1s) to Release 2.0(3a).
Contact Cisco customer support to reprogram the FRU.
CSCtz07798
Under certain conditions, a service profile will generate a configuration failure and a blade that it is associated with is removed from the server pool. This condition can cause service profile re-association to other available blades in the pool.
If q service profile is displaying this condition, re-assign the blade from the server pool to the physical blade by running following command from the CLI to avoid an outage.
F340-31-9-1-B scope org
F340-31-9-1-B /org # scope
service-profile server 1/8
F340-31-9-1-B /org/service-profile
# associate server 1/8
Under certain conditions, the VIC adapter fails after upgrade due to FRU corruption.
Contact Cisco customer support.
CSCta76573
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:
***************************
Severity: Cleared
Code: F0367
Last Transition Time: 2009-07-15T11:47:49
ID: 646445
Status: None
Description: No link between fabric extender
port 2/1/1 and switch A:1/9
Ignore the fault message; it will automatically get cleared after one minute. This will not impact the data path.
Known Limitations and Behaviors
The following known limitations and behaviors are not otherwise documented:
.
Table 13 Known Limitations and Behaviors
Bug ID
Symptom
Workaround
First Bundle Affected
CSCuc22026
While creating an SNMPv3 user, if the username is already assigned to local system users, then instead of giving an error, the configuration will be accepted, but a fault is raised and the configuration will not deploy.
While creating an SNMPv2 user with a community name the same as the local system user will be accepted and deployed without any error or fault.
While creating a local system user, if the username is already assigned to an SNMPv3 user, then instead of giving an error, the configuration will be accepted, but a fault is raised and the configuration will not deploy.
This happens only when SNMPv3 username and system local user name matches.
If SNMPv3 user configuration is not deployed because of name collision with local user, then either choose a different name for the SNMPv3 user or delete the local user for the configuration to be deployed.
If a local user configuration is not deployed because of name collision with an SNMPv3 user, then either choose a different name for the local user or delete the SNMPv3 user for the configuration to be deployed.
CSCtz16082 or CSCtz99909
A server running ESX can only disable C1E when using the default BIOS policy. Once a new BIOS policy is created with C1E disabled from Cisco UCS Manager, ESX does not recognize C1E as disabled while BIOS setup menu and C-state dump from EFI all show C1E is disabled in the BIOS policy from Cisco UCS Manager. So as long as the policy is either set to default (not set) or a custom default (platform default), the problem is not seen.
Leave the policy on the default settings.
The message in ESX is being reported incorrectly by ESX and should be ignored. The root cause is that ESX is looking at the wrong pointer and thus reporting the incorrect status. This has no known ill affects to the function of ESX or the server.
2.0(2q)B
CSCub54167
Cisco UCS B230 M1 Blade Server fails the upgrade process during the storage service profile association.
Reacknowledge the blade after the BIOS upgrade is completed.
2.0(2q)A
CSCty95396
If a server is configured to boot from an iSCSI LUN, then disabling the primary and failover NIC from the host OS will result in the host losing its connection to its boot disk which can lead to a host OS panic or BSOD. This occurs when both the primary and failover vNICs are disabled from the host OS.
Do not disable the failover iSCSI vNIC from the host OS.
2.0(2m)B
CSCtz07684
Boot order in BIOS setup or F6 menus still show Local HDD even after removing Local Disk option in Cisco UCS Manager service profile. This is seen when the boot order is configured by Cisco UCS Manager service profile with PXE eth0, PXE eth1, iSCSI iscsi0, iSCSI iscsi1, Local HDD. If you decide to remove the Local HDD option by deleting it from the boot policy service profile, after server rebooting, the boot order still shows Local HDD in BIOS boot order list. This behavior does not effect booting to PXE and iSCSI devices in the order configured.
Disable Local HDD manually using the following steps:
1. Boot blade.
2. Press F2 key when message is displayed during BIOS POST.
3. Wait until BIOS completes its POST and invokes Setup utility.
4. Select the Boot Options tab.
5. Move the cursor down to Hard Drive BBS Priority and press enter to select this option.
6. Move cursor to hard drive that user want to disable and press enter to configure the drive.
7. Move cursor to Disabled option and press enter to disable the drive.
8. Save and reboot the blade.
2.0(2m)B
CSCtz07684
Boot order in BIOS setup or F6 menus still show Local HDD even after removing Local Disk option in Cisco UCS Manager service profile. This is seen when the boot order is configured by Cisco UCS Manager service profile with PXE eth0, PXE eth1, iSCSI iscsi0, iSCSI iscsi1, Local HDD. If you decide to remove the Local HDD option by deleting it from the boot policy service profile, after server rebooting, the boot order still shows Local HDD in BIOS boot order list. This behavior does not effect booting to PXE and iSCSI devices in the order configured.
Disable Local HDD manually using the following steps:
1. Boot blade.
2. Press F2 key when message is displayed during BIOS POST.
3. Wait until BIOS completes its POST and invokes Setup utility.
4. Select the Boot Options tab.
5. Move the cursor down to Hard Drive BBS Priority and press enter to select this option.
6. Move cursor to hard drive that user want to disable and press enter to configure the drive.
7. Move cursor to Disabled option and press enter to disable the drive.
8. Save and reboot the blade.
2.0(2m)B
CSCtz03288
Hard drives from one manufacturer are two to three times slower than the hard drives from another manufacturer even though both are sold under the same product ID. This issue is observed with 300 GB SAS 10K RPM SFF drives.
Use the correct LSI driver.
2.0(1m)A
CSCtz03288
Hard drives sourced from one manufacturer are two to three times slower than hard drives from another manufacturer even though both are sold under the same product id. This is seen with 300 GB SAS 10K RPM SFF drives.
Please use correct LSI driver.
2.0(1m)A
CSCtr10869
During upgrade from UCS 1.4 to 2.0, an SSLCert error may be written to the log files.
This issue has no known workaround. This is harmless and has not been found to impact functionality.
2.0(1m)A
CSCtn84926
MAC address-based port security for Emulex converged Network Adapters (N20-AE0102) is not supported. You configure MAC address-based port security through the network control policy in the service profile. When MAC address-based port security is enabled, the fabric interconnect restricts traffic to packets that contain the MAC address that it first learns. This is either the source MAC address used in the FCoE Initialization Protocol packet, or the MAC address in an ethernet packet, whichever is sent first by the adaptor. This configuration can result in either FCoE or Ethernet packets being dropped.
Disable MAC security on the service profile.
1.4(3i)
CSCti94391
When using mirroring mode, if a UCE error happens, there is a Redundancy SEL event and also a UCE SEL event. No other details are available for the Data Parity error.
There is no currently known workaround.
1.4(1i)A
CSCtj89468
The link from the rack server adapter to the fabric interconnect port remains down if the SFP type is FET (Fabric extender transceiver). Currently the FET type is supported only between a fabric extender and a fabric interconnect. If the SFP used for the link between the IOM and the rack server adapter is an FET, the link will remain down.
Replace the SFP with one of the supported SFPs for rack server adapters.
1.4(1i)A
CSCtj82918
When the Cisco UCS Manager shell mode is set to s either management or local-management mode, the CLI command terminal monitor is not available.
Use the terminal command in NX-OS mode.
1.4(1i)A
CSCtj51582
Cisco UCS Manager reports an unsupported DIMM as missing but does not raise a fault.
Verify that the DIMM is a Cisco DIMM supported on that server model.
1.4(1i)A
CSCtj57838
Non-disruptive pending changes may not be shown on a service profile. When a service profile has a maintenance policy that defers the application of disrupting changes to the server, user can see what changes are pending and make further changes. Disruptive pending changes are always visible on the service profile, whereas non-disruptive changes may not be shown. Non-disruptive pending changes are only shown for user convenience.
There is no currently known workaround. This defect has no functional impact.
1.4(1i)A
CSCtk35213
Fabric interconnect activation during a downgrade from 1.4(1) to 1.3(1) will fail if the setup has an active Nexus 2248 Fabric Extender.
Decommission all fabric extenders and rack-servers and completely decommission the FSM before downgrading the fabric interconnect image.
1.4(1i)A
CSCtk09043
The server UUID displayed by ipmitool does not match that shown by the Cisco UCS Manager CLI. UCS UUID encoding follows pre SMBIOS 2.6 specified encoding, which is big-endian encoding. Ipmitool does not work well with that encoding. The SMBIOS 2.6 specification mandates mixed encoding (first 3 fields little-endian, last 3 big-endian), which is followed by ipmitool.
For example, The server detail from Cisco UCS Manager CLI shows
# ipmitool -H 10.193.142.104 -U gurudev -P
password mc guid
System GUID :
f3a69906-811b-f845-a9f2-c1bbe089324e
Compared to Cisco UCS Manager CLI or GUI output, the first 3 fields f3a69906-811b-f845 show up differently in the output of ipmitool.
The following usage of ipmitool can be a workaround -
#ipmitool -H 10.193.142.104 -U
gurudev -P password raw 0x06 0x37
06 99 a6 f3 1b 81 45 f8 a9 f2 c1
bb e0 89 32 4e
The output matches the value printed by the Cisco UCS Manager CLI.
1.4(1i)A
CSCtj10809
The show port-security NX-OS CLI command returns a negative value for the Max Addresses. This will occur when a system is configured with more than 8192 Port VLAN instances and. port security is enabled on all interfaces such that more than 8192 MACs are secured.
Do not configure port-security such that secured Port VLAN instances is more than 8192.
1.4(1i)A
CSCti85875
When an N2XX-ACPCI01 adapter port on a C-series server is connected to an uplink port on a UCS 6100 fabric interconnect, a fault message should appear because this connection is not supported, but there is no such fault message for this situation in this release.
There is no currently known workaround.
1.4(1i)A
CSCtd14055 or CSCtf52298
For each Cisco UCS 82598KR-CI 10 Gigabit 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.
Use the MAC that has the value provisioned in the service profile.
1.1(1j)A
CSCte58155
When upgrading from releases prior to 1.1.1, OS-specific default adapter policies will not have the current recommended default values.
After an upgrade from a release prior to 1.1.1, we recommend manually changing the adapter policy parameters to the following values:
Eth VMWare->RSS: Disabled
Eth VMWarePassThru->RSS: Enabled
Eth default->RSS: Enabled
FC (all)->FCP Error Recovery:
Disabled
FC (all)->Flogi Retries: 8
FC (all)->Flogi Timeout: 4000
FC (all)->Plogi Timeout: 20000
FC (all)->IO Throttle Count: 16
FC (all)->Max LUNs Per Target: 256
1.1(1j)A
CSCtd90695
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.
Review both the disks (and drive labels as applicable) during installations of ESX and Linux versions and choose the correct disk for installation.
1.1(1j)A
CSCta45805 or CSCsy80888
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.
Remove and insert all of the local disks from the failing server, then re-acknowledge the server.
1.1(1j)A
CSCsy76853
The Disk Fault/Error Codes, Disk Status, Alarms and the failures forwarded by the SAS Controller are not received by Cisco UCS Manager.
There is no currently known workaround.
1.1(1j)A
CSCte44548
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.
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.
1. Restart the network.
service network restart
or
ifdown ethx
ifup ethx
2. Run your system with nomsi.
•Edit /etc/grub.conf
•Add pci=nomsi to the kernel line
•Restart the system with this kernel
Note that network performance may be affected since the system is running in legacy mode.
1.1(1j)A
CSCte12163
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.
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.
1.1(1j)A
CSCte73015
Loading multiple driver disks during a RHEL 5.x installation fails.
Hubs that only use USB 1.0 may not properly present an attached USB device to the UCS server.
Avoid using USB hubs that are exclusively USB 1.0 capable. Virtually all USB hubs sold today are USB 1.0/2.0 capable.
1.0(1e)A
CSCta21326
Logon access is denied for user accounts where the password field was left blank during user account creation.
When creating a user account, ensure that a secure password for the account is specified.
1.0(1e)A
CSCsy80888
After the removal or insertion of one or more local disks, their full discovery fails.
Re-acknowledge the server to complete the full discovery.
1.0(1e)A
CSCtc21336
With various Local Disk Configurations, the LSI SAS Configuration Utility fails to launch while in BIOS.
The LSI SAS Controller Utility should not be used and all of the Local Disk Policy and Service Profile operations must be executed using Cisco UCS Manager.
1.0(1e)A
CSCsz41907
When plugging or removing USB devices at BIOS Setup -> Advanced -> USB, the Setup Utility may hang.
Reboot the server.
1.0(1e)A
CSCsz41907
When plugging or removing USB devices at BIOS Setup -> Advanced -> USB, the Setup Utility may hang.
Reboot the server.
1.0(1e)A
CSCta94641
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 does not have a sleep detection mechanism.
Always shut down the UCSM GUI before putting your computer to sleep.
1.0(1e)A
CSCtb45761
Downloads may be slow if TFTP is used.
If TFTP performance is slow, use SCP or another protocol.
1.0(1e)A
CSCsz68887
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.
Specify the desired failback timeout in the adapter policy and apply to the first vNIC.
1.0(1e)A
CSCsz99666
Installing EFI Native SLES 11 is currently not supported.
There is no currently known workaround.
1.0(1e)A
CSCsx13134
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.
There is no currently known workaround.
1.0(1e)A
CSCsy15489
Console logon usernames on the fabric interconnect are not case sensitive. For example, there is no differentiation between admin and ADMIN.
Use case insensitive usernames.
1.0(1e)A
CSCta09325
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.
There is no currently known workaround.
1.0(1e)A
CSCta09325
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.
There is no currently known workaround.
1.0(1e)A
CSCta25287
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.
There is no currently known workaround.
1.0(1e)A
CSCta12005
Hardware revision numbers for fabric interconnect components are not populated in the Cisco UCS Manager.
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 spromcomponent command and look for H/W Version: field in the command output.
1.0(1e)A
CSCta22029
SNMP shows the fabric interconnect name rather than system name.
There is no currently known workaround.
1.0(1e)A
CSCta24034
An SNMP username cannot be the same as a local username.
Select an SNMP username that does not match any local username.
1.0(1e)A
CSCsz47512
Statistics counters cannot be cleared using the Cisco UCS Manager CLI.
Clear the counters using the Cisco UCS Manager GUI.
1.0(1e)A
CSCta38463
When several KVM Consoles are launched, the SUN JRE sometimes reports an error and the KVM Console fails to launch.
Launch the KVM Console again.
1.0(1e)A
CSCta54895
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.
There is no currently known workaround.
1.0(1e)A
CSCtw67182
A blade with a UCS M81KR adapter shows the error "initialize error 1" during iSCSI boot.
There is no currently known workaround.
2.0(1s)A
Related Documentation
For more information, you can access related documents from the following links:
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.
Feedback
Current information that became available after the technical documentation was published
