Table Of Contents
Release Notes for Cisco UCS Manager, Release 2.2
Contents
Revision History
Introduction
System Requirements
Updating Cisco UCS Releases
Minimum B/C Bundle Version Requirements for Cisco UCS Manager Features
Hardware and Software Interoperability
Internal Dependencies
Capability Catalog
New Software Features in Release 2.2
Resolved Caveats
Open Caveats
Known Limitations
Default Zoning is Not Supported in Cisco UCS, Release 2.1(1a) and Later Releases
Cisco UCS Manager Downgrade
Known Limitations and Behaviors
Related Documentation
Release Notes for Cisco UCS Manager, Release 2.2
First Published: December 12, 2013
Updated: February 9, 2014
Part Number: OL-31127-01
This document describes system requirements, new features, resolved caveats, known caveats and workarounds for Cisco UCS Manager software Release 2.2. This document also includes the following:
•
Current information that became available after the technical documentation was published
•Related firmware and 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:
http://www.cisco.com/go/unifiedcomputing/b-series-doc
Contents of the various bundles for this release are described in:
Release Bundle Contents for Cisco UCS Software, Release 2.2
Make sure to review other available documentation on Cisco.com to obtain current information on Cisco UCS Manager.
Contents
This document includes the following sections:
•Revision History
•Introduction
•System Requirements
•Updating Cisco UCS Releases
•Internal Dependencies
•Capability Catalog
•New Software Features in Release 2.2
•Resolved Caveats
•Open Caveats
•Known Limitations
•Related Documentation
Revision History
Table 1 shows the revision history:
Table 1 Online Change History
Part Number
|
Revision
|
Release
|
Date
|
Description
|
OL-31127-01
|
A0
|
2.2(1b)
|
December 12, 2013
|
Created release notes for Cisco UCS Manager, Release 2.2(1b).
|
B0
|
2.2(1b)
|
December 20, 2013
|
Added additional caveats.
|
C0
|
2.2(1c)
|
February 9, 2014
|
Updated release notes for Cisco UCS Software Release 2.2(1c).
|
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
•Cisco UCS Central, Release 1.1(1b) is required for registering with Cisco UCS Central.
Updating Cisco UCS Releases
The Cisco UCS Manager A bundle software (Cisco UCS Manager, Cisco NX-OS, IOM firmware) can be mixed with the previous release's B or C bundles on the servers (host firmware (FW), BIOS, CIMC, adapter FW and drivers).
Table 2 lists the mixed A, B, and C bundle versions that are supported:
Table 2 Mixed Cisco UCS Releases Supported
| |
Infrastructure Versions (A Bundles)
|
Host FW Versions (B or C Bundles)
|
1.4(3)
|
1.4(4)
|
2.0(1)
|
2.0(2)
|
2.0(3)
|
2.0(4)
|
2.0(5)
|
2.1(1)
|
2.1(2)
|
2.1(3)
|
2.2(1)
|
1.4(3)
|
Yes
|
—
|
—
|
—
|
—
|
—
|
—
|
—
|
—
|
—
|
—
|
1.4(4)
|
—
|
Yes
|
—
|
—
|
—
|
—
|
—
|
—
|
—
|
—
|
—
|
2.0(1)
|
—
|
—
|
Yes
|
—
|
—
|
—
|
—
|
Yes
|
Yes
|
Yes
|
—
|
2.0(2)
|
—
|
—
|
—
|
Yes
|
—
|
—
|
—
|
Yes
|
Yes
|
Yes
|
—
|
2.0(3)
|
—
|
—
|
—
|
—
|
Yes
|
—
|
—
|
Yes
|
Yes
|
Yes
|
—
|
2.0(4)
|
—
|
—
|
—
|
—
|
—
|
Yes
|
—
|
Yes
|
Yes
|
Yes
|
—
|
2.0(5)
|
—
|
—
|
—
|
—
|
—
|
—
|
Yes
|
Yes
|
Yes
|
Yes
|
—
|
2.1(1)
|
—
|
—
|
—
|
—
|
—
|
—
|
—
|
Yes
|
Yes
|
Yes
|
Yes
|
2.1(2)
|
—
|
—
|
—
|
—
|
—
|
—
|
—
|
—
|
Yes
|
Yes
|
Yes
|
2.1(3)
|
—
|
—
|
—
|
—
|
—
|
—
|
—
|
—
|
—
|
Yes
|
Yes
|
2.2(1)
|
—
|
—
|
—
|
—
|
—
|
—
|
—
|
—
|
—
|
—
|
Yes
|
Note•A mix of servers running different B-bundles may be run with a single A-bundle. However, any given server must be running the entire B/C-bundles (with associated drivers). Example: mixing the 2.1(2)B BIOS with the 2.1(3)B CIMC on a server is not supported.
•The OS hardware and software interoperability is relative to the B/C-bundle on any given server. To see what OS is supported, see the Hardware and Software Interoperability documentation associated with the B-bundle version.
•The A-bundle version must be at or above the same version(s) of any B/C-bundles running on the servers (see Table 2). This applies for patch levels as well, even though they are not displayed on the table. For example, you can mix 2.1(1f)A with 2.1(1b)B, but you cannot mix 2.1(1b)A with 2.1(1f)B.
Minimum B/C Bundle Version Requirements for Cisco UCS Manager Features
The following Cisco UCS Manager 2.2(1b) features require the specified minimum B/C bundle version to perform expected operations:
Table 3 Minimum Required B/C Bundle Version
Feature
|
B Bundle Version
|
C Bundle Version
|
IPv6 Management Support
|
2.2(1b)B
|
2.2(1b)C
|
usNIC for Low Latency
|
2.2(1b)B
|
2.2(1b)C
|
Support for Virtual Machine Queue (VMQ)
|
2.2(1b)B
|
2.2(1b)C
|
VM-FEX for Hyper-V Management with Microsoft SCVMM
|
2.2(1b)B
|
2.2(1b)C
|
Secure Boot
|
2.2(1b)B
|
2.2(1b)C
|
Local Storage Management
|
2.2(1b)B
|
2.2(1b)C
|
Flash Adapters and HDD Firmware Management
|
2.2(1b)B
|
2.2(1b)C
|
Precision Boot Order Control
|
2.2(1b)B
|
2.2(1b)C
|
Trusted Platform Module (TPM) Inventory
|
2.2(1b)B
|
2.2(1b)C
|
DIMM Blacklisting and Correctable Error Reporting
|
2.2(1b)B
|
2.2(1b)C
|
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
http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_list.html
Internal Dependencies
Table 4 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.
Table 4 Internal Dependencies
Component
|
Recommended Minimum Software Version
|
Recommended Software Version
|
Servers
|
B22 M3
|
2.1(3b)
|
2.2(1c)
|
B200 M1
|
2.1(3b)
|
2.2(1c)
|
B200 M2
|
2.1(3b)
|
2.2(1c)
|
B200 M3
|
2.1(3b)
|
2.2(1c)
|
B230 M1
|
2.1(3b)
|
2.2(1c)
|
B230 M2
|
2.1(3b)
|
2.2(1c)
|
B250 M1
|
2.1(3b)
|
2.2(1c)
|
B250 M2
|
2.1(3b)
|
2.2(1c)
|
B420 M3
|
2.1(3b)
|
2.2(1c)
|
B440 M1
|
2.1(3b)
|
2.2(1c)
|
B440 M2
|
2.1(3b)
|
2.2(1c)
|
C22 M3
|
2.1(3b)
|
2.2(1c)
|
C22 M3L
|
2.1(3b)
|
2.2(1c)
|
C24 M3
|
2.1(3b)
|
2.2(1c)
|
C24 M3L
|
2.1(3b)
|
2.2(1c)
|
C24 M3S2
|
2.1(3b)
|
2.2(1c)
|
C200 M2
|
2.1(3b)
|
2.2(1c)
|
C200 M2 SFF
|
2.1(3b)
|
2.2(1c)
|
C210 M2
|
2.1(3b)
|
2.2(1c)
|
C220 M31
|
2.1(3b)
|
2.2(1c)
|
C240 M31
|
2.1(3b)
|
2.2(1c)
|
C260 M2
|
2.1(3b)
|
2.2(1c)
|
C250 M2
|
2.1(3b)
|
2.2(1c)
|
C460 M2
|
2.1(3b)
|
2.2(1c)
|
C420 M3
|
2.1(3b)
|
2.2(1c)
|
Adapters
|
UCS 82598KR-CI
UCS M71KR-E
UCS M71KR-Q
|
2.1(3b)
|
2.2(1c)
|
UCS M81KR
|
2.1(3b)
|
2.2(1c)
|
UCS NIC M51KR-B
UCS CNA M61KR-I2
UCS CNA M72KR-Q
UCS CNA M72KR-E
|
2.1(3b)
|
2.2(1c)
|
UCS-VIC-M82-8P
UCSB-MLOM-40G-01
UCSB-MLOM-PT-01
|
2.1(3b)
|
2.2(1c)
|
UCSC-PCIE-CSC-02
UCSB-MEZ-ELX-03
UCSB-MEZ-QLG-03
|
2.1(3b)
|
2.2(1c)
|
Fabric Interconnect
|
UCS 6120XP
|
2.2(1b)
|
2.2(1c)
|
UCS 6140XP
|
2.2(1b)
|
2.2(1c)
|
UCS 6248UP
|
2.2(1b)
|
2.2(1c)
|
UCS 6296UP
|
2.2(1b)
|
2.2(1c)
|
Fabric Extender or I/OM
|
UCS 2104
|
2.2(1b)
|
2.2(1c)
|
UCS 2208XP
|
2.2(1b)
|
2.2(1c)
|
UCS 2204XP
|
2.2(1b)
|
2.2(1c)
|
Cisco Nexus 2232PP
|
2.2(1b)
|
2.2(1c)
|
Fabric Interconnect Expansion Modules
|
N10-E0440
N10-E0600
N10-E0080
|
2.2(1b)
|
2.2(1c)
|
N10-E0060
|
2.2(1b)
|
2.2(1c)
|
UCS-FI-E16UP
|
2.2(1b)
|
2.2(1c)
|
10-GB Connections
|
SFP-10G-SR, SFP-10G-LR
SFP-H10GB-CU1M
SFP-H10GB-CU3M
SFP-H10GB-CU5M
|
2.2(1b)
|
2.2(1c)
|
SFP-H10GB-ACU7M
SFP-H10GB-ACU10M
|
2.2(1b)
|
2.2(1c)
|
FET-10G
|
2.2(1b)
|
2.2(1c)
|
SFP-H10GB-ACU7M=
SFP-H10GB-ACU10M=
|
2.2(1b)
|
2.2(1c)
|
8-GB Connections (FC Expansion Module N10-E0060)
|
DS-SFP-FC8G-SW
DS-SFP-FC8G-L
|
2.2(1b)
|
2.2(1c)
|
4-GB Connections (FC Expansion Module N10-E0080)
|
DS-SFP-FC4G-SW
DS-SFP-FC4G-LW
|
2.2(1b)
|
2.2(1c)
|
1-GB Connections
|
GLC-T (V03 or higher)
GLC-SX-MM
GLC-LH-SM
|
2.2(1b)
|
2.2(1c)
|
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.2(x) releases work with any 2.2(x) catalog file, but not the 1.x, 2.0 or 2.1 catalog versions. If a server component is not dependent on a specific BIOS version, using it and having it recognized by Cisco UCS Manager is primarily a function of the catalog version. The catalog is released as a single image in some cases for convenience purposes in addition to being bundled with UCS infrastructure releases. See Table 5 for details on the mapping of versions to bundles.
Table 5 Version Mapping
UCS Release
|
Catalog File
|
Adds Support for PID
|
2.2(1b)A
|
ucs-catalog.2.2.1b.T.bin
|
•UCS-ML-1X324RZ-A
•UCS-SD200G0KS2-EP
•UCS-SD400G0KS2-EP
•UCS-SD800G0KS2-EP
|
2.2(1c)A
|
—
|
—
|
Further details are in the Cisco UCS Manager Configuration Guides.
New Software Features in Release 2.2
Release 2.2(1b) adds support for the following:
•IPv6 Management Support
•Cisco Integrated Management Controller (CIMC) In-band Management
•Fabric scaling: VLAN, VIFs, IGMP, Network Adapter Endpoints
•Uni-Directional Link Detection (UDLD) Support
•User Space NIC (usNIC) for Low Latency
•Support for Virtual Machine Queue (VMQ)
•C-Series Servers Direct Connect to FI without FEX
•Two-factor Authentication for UCS Manager Logins
•VM-FEX for Hyper-V Management with Microsoft SCVMM
•Direct KVM Access
•Server Firmware Auto Sync
•Enhanced Local Storage Management
•Flash Adapters and HDD Firmware Management
•Precision Boot Order Control
•Secure Boot
•UEFI Boot Support
•FlexFlash (Local SD card) Support
•Trusted Platform Module (TPM) Inventory
•DIMM Blacklisting and Correctable Error Reporting
•C-Series Board Controller Firmware Management
Note If you want to refer to a list of supported OS in this release, check the Hardware and Software Interoperability Matrix for this release.
Resolved Caveats
The following caveats are resolved in Release 2.2(1c):
Table 6 Resolved Caveats in Release 2.2(1c)
Defect ID
|
Description
|
First Bundle Affected
|
Resolved in Release
|
CSCum43435
|
The Cisco VIC 1280 adapter on a Cisco UCS B440 M2 blade no longer hangs during PXE boot.
|
2.2(1b)B
|
2.2(1c)B
|
CSCul44120
|
Cisco UCS blade servers performing a PXE boot from a Citrix PVS system no longer fail after the initial bootloader initialization with a "No API found" error.
|
2.1(2a)B
|
2.2(1c)B
|
CSCum51025
|
Cisco UCS Manager domains registered in Cisco UCS Central no longer fail during scheduled backups.
|
2.2(1b)A
|
2.2(1c)A
|
CSCum25003
|
Associated local and global service profile inventory information is no longer sent to Cisco UCS Central when no changes are made.
|
2.2(1b)A
|
2.2(1c)A
|
The following caveats are resolved in Release 2.2(1b):
Table 7 Resolved Caveats in Release 2.2(1b)
Defect ID
|
Description
|
First Bundle Affected
|
Resolved in Release
|
CSCug93342
|
After rebooting the FI during an upgrade, the FI no longer boots to the Loader prompt.
Note To ensure the new power sequencer firmware is installed properly, you must power cycle the FI after the upgrade is completed.
|
2.1(3a)A
|
2.2(1b)A
|
CSCuc19701
|
The 2204 IOM no longer reboots when the FI is reset.
|
2.1(1a)A
|
2.2(1b)A
|
CSCuf90470
|
When Call Home is enabled, Online Insertion and Removal (OIR) or failure of hardware modules in the FI no longer causes the FI to reboot.
|
2.1(1b)A
|
2.2(1b)A
|
CSCui45963
|
Some of the text and controls are no longer truncated when you create a service profile or service profile template using the wizard.The edit option for storage settings is enabled.
|
2.1(2a)A
|
2.2(1b)A
|
CSCuj84421
|
Installing Java 7 update 45 no longer causes UCS Manager GUI failures.
|
2.1(1f)A
|
2.2(1b)A
|
CSCuc38783
|
Firmware upgrade no longer fails on BRCM 57712 adapter.
|
2.1(1a)A
|
2.2(1b)A
|
CSCuj77813
|
Associating service profile to a C-series server integrated with Cisco UCS Manager no longer fails.
|
2.1(3a)C
|
2.2(1b)A
|
CSCui43905
|
When you try to create an iSCSI NIC on a service profile, UCS Manager no longer displays any warning messages.
|
2.1(2a)B
|
2.2(1b)A
|
CSCuj32124
|
During normal operation IOM no longer unexpectedly reboots with CPU reset.
|
1.4(2b)A
|
2.2(1b)A
|
CSCui41165
|
Cisco UCS Manager no longer displays "error accessing shared-storage"error or have the following issues:
•Call home fan alerts are sent and cleared immediately
•Errors during IOM boot-up
|
1.4(2b)A
|
2.2(1b)A
|
CSCuj78099
|
FC traffic between a Cisco UCS FI and a Cisco MDS switch is no longer disrupted when the FI is in switch mode.
|
2.1(3a)A
|
2.2(1b)A
|
CSCuj61839
|
With the 2.2(1b)B bundle, Cisco UCS Blade servers on a Cisco M81KR VIC adapter no longer encounter "ASSERT FAILED @ mips/ecpu_pani.c:138" errors.
|
2.1(2a)A
|
2.2(1b)A
|
CSCuj10564
|
Discard TX on a FC trunk port are no longer seen after hot-swapping the Cisco UCS-FI-E16UP expansion module on the Cisco UCS 6248UP FI.
|
2.1(1f)A
|
2.2(1b)A
|
CSCuf77316
|
Windows 2012 installed on a FlexFlash card no longer fails Microsoft certifcation.
|
2.1(2a)B
|
2.2(1b)A
|
CSCui87195
|
The FLS process on Cisco CNA M72KR-E no longer cores with the following message:
130820-19:06:33.645547 fls.fc vnic 15: Local port down for lif 4.
|
2.0(5c)C
|
2.2(1b)A
|
CSCuj99958
|
During heavy FC traffic, the server no longer stops responding with an ASSERT FAILED (Exception 2 triggered!) @ mips/ecpu_panic.c:138 error.
|
2.1(1f)A
|
2.2(1b)A
|
CSCug89448
|
The tech support collection no longer fails on the Cisco UCS Manager GUI.
|
2.0(1s)A
|
2.2(1b)A
|
CSCug63368
|
PXE boot no longer fails in vPC environments if the DHCP relay agent is installed as the gateway IP address during a PXE boot instead of the HSRP IP address.
|
2.1(1d)B
|
2.2(1b)A
|
CSCui82679
|
FlexFlash storage is no longer disconnected from a Cisco B200 M3 server after booting ESX or ESXi from a FlexFlash card.
|
2.1(2a)A
|
2.2(1b)A
|
CSCuc52981
|
Downloaded license files for FIs continue to be displayed in the downloads area after installation.
|
2.0(3a)A
|
2.2(1b)A
|
CSCti39470
|
RAID 50 and RAID 60 configurations can now be created and managed by Cisco UCS Manager.
|
1.4(1i)A
|
2.2(1b)A
|
Open Caveats
The following caveats are open in Release 2.2(1c):
Table 8 Open Caveats in Release 2.2(1c)
Defect ID
|
Symptom
|
Workaround
|
First Bundle Affected
|
CSCum82888
|
After upgrading to Release 2.2(1b), you may see the following errors:
•No access to the Cisco UCS Manager GUI.
•The virtual IP is not reachable.
•The virtual IP cannot be accessed by the GUI or CLI/SSH.
•Individual FIs can be accessed using SSH but not with http.
This occurs when the default keyring is deleted before upgrade, or if the default keyring is deleted after the upgrade and the system is rebooted.
|
To avoid this issue, do not delete the default keyring.
If this issue occurs, stop the bladeAG process.
|
2.2(1b)B
|
CSCum09954
|
If an FC uplink interface is set to administratively shut, after upgrading to Release 2.2(1b) you may see a "FCoE or FC uplink is down on Vsan 202" error.
|
This issue is cosmetic and the error message can be safely ignored.
|
2.2(1b)A
|
CSCum60793
|
You may see the following fault in Cisco UCS Manager:
[FSM:STAGE:RETRY:]: Report mount suspend
success to operations manager errors
This occurs if Cisco UCS Central is not reachable or the domain has been unregistered.
|
Restore connectivity to Cisco UCS Central, or register the domain again.
|
2.1(2c)A
|
The following caveats are open in Release 2.2(1b):
Table 9 Open Caveats in Release 2.2(1b)
Defect ID
|
Symptom
|
Workaround
|
First Bundle Affected
|
CSCui67824
|
When you disable port security from a network control policy with Hyper-V port profile, security is disabled on the nested port-profile, but security remains enabled on a few interfaces.
|
This issue has no known workaround.
|
2.2(1b)A
|
CSCuj26767
|
Attempting to install UEFI OS second time sets incorrect boot order and stops installation.
|
Clean initial installation in the disk and restart installation.
|
2.2(1b)A
|
CSCui52680
|
When the blade appears to be in normal operation state, Cisco UCS Manager SEL message list might display the following error:
EFI Load Image Security Violation
|
If all blade functions appear to be normal, ignore this error message.
|
2.2(1b)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
|
CSCug25894
|
During Cisco 2100 Series IOM boot and chassis reacknowledgement, sysmgr cores are seen.
|
The system resumes normal behavior after process restart. This should take approximately three minutes.
|
2.0(4a)A
|
CSCum02561
|
When upgrading to 2.2(1b) from 2.1(3a), if you upgrade the infrastructure (A bundle) before the host firmware (B and C bundles), and then modify the service profile you may experience one or more of the following issues:
1. The configured boot order in the Cisco UCS Manager GUI does not display SAN and local disk.
2. The server reboots every time the service profile is modified.
|
1. To view missing entries for the configured boot order, use the Cisco UCS Manager CLI to scope into the server and run show boot-order.
2. To avoid server reboots, uncheck the Reboot on Boot Order Change checkbox before upgrading.
3. Upgrade the B and C bundles.
|
2.2(1b)A
|
CSCuj74570
|
A Cisco UCS B420 M3 blade with a VIC 1240 and a port expander is successfully discovered in a chassis with a 2104XP IOM, even though it is unsupported. When upgrading to the 2204XP IOM, the blade reboots for discovery.
|
This issue has no known workaround.
The B420 M3 blade with port expander is not supported with the 2104XP IOM.
|
2.1(2a)B
|
CSCul72408
|
During upgrade, the following issues occured:
•The IOM backplane ports show admin down in the Cisco UCS Manager GUI.
•The VIF's show non-participating.
•The adapter shows DCE interfaces down.
|
Reboot the IOM in the affected chassis.
|
2.1(3a)A
|
CSCul95501
|
IOM FSM failed after downgrading from 2.2(1b). Connectivity between the IOM and the FI could not be established.
|
Reboot the FI.
|
2.1(3a)A
|
CSCuh89441
|
On B420 M3, the installed OS fails to boot from SAN LUN with Gen-3 E.
|
Enable EDD 3.0 using the Emulex M73KR-E FCoE option ROM.
|
2.2(1b)A
|
CSCuj89557
|
In some rare conditions, it is observed during Cisco UCS Manager upgrade, downgrade, or FI reload in a cluster setup that Cisco UCS Manager may fail on the secondary FI due to database corruption.
|
If you detect a db corruption in the secondary FI, erase the database from the FI and reconnect it to the cluster. The secondary syncs up with the primary FI and recreates the db.
|
2.2(1b)A
|
CSCtl04654
|
Changing native VLAN on uplink ports will cause the ports state to change and traffic disruption.
|
If native VLAN changes are required on uplink ports, we recommend that they be performed during a maintenance window.
|
2.1(1a)A
|
CSCuj78615
|
The EFI Shell boot option is disabled in the BIOS Setup Utility > Boot Options page. Shell Boot option is not automatically launched by the BIOS.
|
Boot UEFI shell by using either one of the following two options:
•Enter BIOS set up utility and select Shell boot option from the Exit & Save page.
•Hit F6 to access boot override menu.
|
2.2(1b)A
|
CSCuh13333
|
When you install ESXi in UEFI mode, the OS fails to boot-up. Even when you seem to have a smooth installation, the server does not boot the ESXi OS.
|
Do the following:
1. Boot to Shell.
2. Determine fsxx (xx is where ESX is installed. It will be typically 0 i.e fs0:) Make sure you have the following:
fsxx:\EFI\Boot\BOOTX64.EFI
3. Use following command to get current list of EFI Boot Options
Note last boot option number to use
as LAST_BOOT_No +1
4. Use the following command to add new Boot Option at position LAST_BOOT_NO + 1
Last paramter in quotes can be any
description for this new Boot
Option.
This will be displayed during BIOS
F6 menu.
bcfg boot add LAST_BOOT_NO +
fsxx:\EFI\BOOT\BOOTX64.EFI "UEFI :
ESXi "
5. Make the newBoot Option for ESX as the first by using the following
bcfg boot mv LAST_BOOT_NO + 4 1
6. Issue reset command at the shell and reset the platform. Press F6 when BIOS is booting to get into BIOS Boot Selection menu. Make sure the new Boot Option is displayed and select this option to Boot EXSi.
|
2.2(1b)A
|
CSCuj31559
|
Installing Windows EFI PXE using UEFI is slow when compared to the installation using vNIC on MLOM.
|
This issue has no known workaround.
|
2.2(1b)A
|
CSCuh34516
|
Installing Linux PXE using UEFI fails with the following message:
Trying to allocate 971 pages for VMLINUZ.
|
This issue has no known workaround.
|
2.2(1b)A
|
CSCuj34520
|
TFM information in UCS Manager inventory contains invalid characters.
|
This issue has no known workaround.
|
2.1(2a)A
|
Known Limitations
Default Zoning is Not Supported in Cisco UCS, Release 2.1(1a) and Later Releases
Default zoning has been deprecated in Cisco UCS, Release 2.1(1a). 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 in Cisco UCS, Release 2.1(1a) and later releases. 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.
Cisco UCS Manager Downgrade
Before performing any upgrade or downgrade operation, make sure to perform an all configuration backup of your system. The backup will ensure a seamless downgrade or upgrade, if required.
The following defects are related to downgrade issues:
•CSCul55683 - When downgrading the Cisco UCS Manager image from Release 2.2 to any prior version, you must downgrade Cisco UCS Manager before you downgrade the infrastructure firmware on the FI. If you downgrade the FI first, some FI processes will crash.
–Contact Cisco TAC to recover from this issue.
•CSCuj87553 - If you downgrade the Cisco UCS Manager image from Release 2.2 to any version prior to Release 2.0(4) before the fabric interconnect images are downgraded, the Cisco UCS Manager GUI may not work.
–To recover from this issue, downgrade the kickstart and sytem images on the FI to the same version as the downgraded Cisco UCS Manager image. The Cisco UCS Manager GUI will be able to reconnect successfully after the FI is running the same version as Cisco UCS Manager.
•CSCul54029 - When you downgrade a B22 board controller to 2.1(2) version using auto-install, the activate status shows as failed. Also if you initiate individual board activation, the board control firmware downgrade is blocked.
–To recover from this status, use "force" option to activate the board controller to the same version as the active one. This clears the fault and brings activate status to "Ready".
Known Limitations and Behaviors
The following known limitations and behaviors are not otherwise documented:
Table 10 Known Limitations in Release 2.2
Defect ID
|
Symptom
|
Workaround
|
First Bundle Affected
|
CSCui95113
|
Blade discovery fails with the following error:
Warning F77960 2013-08-29T17:47:46.044
18211988 [FSM:STAGE:REMOTE-ERROR]: Result:
end-point-unavailable Code: unspecified
Message: sendSamDmeAdapterInfo: identify
failed(sam:dme:ComputeBladeDiscover:NicPresence
Peer)
Warning F16520 2013-08-29T17:47:35.122
18211986 [FSM:STAGE:RETRY:]: detect mezz cards
in
6/1(FSM-STAGE:sam:dme:ComputeBladeDiscover:NicP
resencePeer)
|
This issue was caused by manufacturing sending out adapters in DIAG mode.
For information on how to fix this issue, see the following Tech Zone post:
https://techzone.cisco.com/t5/B-Series/How-to-debug-and-fix-M3-blades-with-VIC-1240-1280-failing/m-p/361283
|
2.1(2a)B
|
Related Documentation
For more information, you can access related documents from the following links:
•Cisco UCS Documentation Roadmap
•Release Bundle Contents for Cisco UCS Software, Release 2.2
This document is to be used in conjunction with the documents listed in the "Known Limitations" 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.
© 2013-2014 Cisco Systems, Inc. All rights reserved.
Feedback
