Table Of Contents
Release Notes for Cisco UCS Software, Release 2.0
Hardware and Software Interoperability
Known Limitations and Behaviors
Open Caveats from Prior Releases
New Hardware Features in Release 2.0(1)
New Software Features in Release 2.0(1)
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco UCS Software, Release 2.0
First Published: September 19, 2011
Updated: February 9, 2012
Part Number: OL-25363-01This document describes the new features, system requirements, and caveats for Cisco UCS Manager Release 2.0(1m), Release 2.0(1q), Release 2.0(1s), Release 2.0(1t), Release 2.0(1w) and all related firmware and BIOSes on blade servers and other Unified Computing System components associated with that release. Use this document in conjunction with the documents listed in the Documentation Roadmap.
Note
We sometimes update the documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates. Documentation updates and errata are also in these release notes. The documentation roadmap for this product is available at: http://www.cisco.com/go/unifiedcomputing/b-series-doc
Table 1 shows the online change history for this document.
Table 1 Online History Change
OL-25363-01
A0
September 19, 2011
Created release notes for Release 2.0(1m). 1
B0
October 14, 2011
Updated release notes for Release 2.0(1q).
C0
November 8, 2011
Updated release notes for Release 2.0(1s).
D0
November 29, 2011
Updated release notes for Release 2.0(1t).
E0
December 15, 2011
Updated release notes for Catalog Release 2.0.1o.T.
F0
February 9, 2012
Updated release notes for Release 2.0(1w).
1 This release was removed from the download area due to CSCts96949 and CSCts86890. See the software deferral notice.
Contents
This document includes the following sections:
•
•
•
•
•
•
•
Introduction
The Cisco® Unified Computing System is a next-generation data center platform that unites compute, network, storage access, and virtualization into a cohesive system designed to reduce total cost of ownership (TCO) and increase business agility. The system integrates a low-latency, lossless 10 Gigabit Ethernet unified network fabric with enterprise-class, x86-architecture servers. The system is an integrated, scalable, multi-chassis platform in which all resources participate in a unified management domain.
System Requirements
To install Cisco UCS Manager your computer must meet or exceed the following minimum system requirements:
•
•
–
–
Adobe Flash Player 10 or higher is required for some features
•
–
–
–
–
Updating Cisco UCS Versions
To update the Cisco UCS software and firmware, refer to the appropriate Upgrading Cisco UCS document for your installation.
Use the scope firmware and show package filename expand CLI commands to view the contents of a given release package. File names in Table 2 are accurate for the 2.0(1) release, expect small changes for subsequent patch releases.
Hardware and Software Interoperability
For detailed information about storage switch, operating system, adapter, adapter utility, and storage array interoperability, see the Hardware and Software Interoperability Matrix for this release, located at:
http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_list.html
Note
Internal Dependencies
Table 3 shows interdependencies between UCS hardware and versions of Cisco UCS Manager. Server FRU items like DIMMs are dependent on their server type, and chassis items like fans and power supplies work with all versions of UCS Manager.
Caution
Table 3 Internal Dependencies (continued)
Software
Version
Software
VersionB200 M1
1.0(1)
2.0(1)
B250 M1
1.1(1)
2.0(1)
B440 M1
1.3(1)
2.0(1)
B440 M2
1.4(3)
2.0(1)
B200 M2
1.2(1)
2.0(1)
B250 M2
1.2(1)
2.0(1)
B230 M1
1.4(1)
2.0(1)
B230 M2
1.4(3)
2.0(1)
C200 M2
1.4(1)
2.0(1)
C210 M2
1.4(1)
2.0(1)
C250 M2
1.4(1)
2.0(1)
UCS 82598KR-CI
UCS M71KR-E
UCS M71KR-Q1.0(1)
2.0(1)
UCS M81KR
1.0(2)
2.0(1)
UCS NIC M51KR-B
UCS CNA M61KR-I 1
UCS CNA M72KR-Q
UCS CNA M72KR-E1.3(1)
2.0(1)
UCS 6120XP
1.0(1)
2.0(1)
UCS 6140XP
1.1(1)
2.0(1)
UCS 6248UP
2.0(1)
2.0(1)
UCS 2104
1.0(1)
2.0(1)
UCS 2208XP
2.0(1)
2.0(1)
Nexus 2248
1.4(1)
2.0(1)
Expansion ModulesN10-E0440
N10-E0600
N10-E00801.0(1)
2.0(1)
N10-E0060
1.1(1)
2.0(1)
UCS-FI-E16UP
2.0(1)
2.0(1)
SFP-10G-SR, SFP-10G-LR
SFP-H10GB-CU1M
SFP-H10GB-CU3M
SFP-H10GB-CU5M1.0(1)
2.0(1)
SFP-H10GB-ACU7M
SFP-H10GB-ACU10M1.4(1)
2.0(1)
FET-10G
1.4(1)
2.0(1)
SFP-H10GB-ACU7M=
SFP-H10GB-ACU10M=1.4(2)
2.0(1)
DS-SFP-FC8G-SW
DS-SFP-FC8G-LW1.3(1)
2.0(1)
DS-SFP-FC4G-SW
DS-SFP-FC4G-LW1.0(1)
2.0(1)
GLC-T (V03 or higher)
GLC-SX-MM
GLC-LH-SM1.3(1)
2.0(1)
Capability Catalog
Cisco UCS Manager uses the catalog to update the display and configurability of server components such as newly qualified DIMMs and disk drives. The UCS Manager Capability Catalog is a single image, but it's also embedded in UCS Manager. The latest posted catalog should work with any posted release from release 1.3(1) onwards. This means that so long as a server component is not dependent on a specific BIOS version, using it and having it recognized by UCS Manager is primarily a function of the catalog version. The catalog is released as single image in some cases for convenience purposes in addition to being bundled with UCS infrastructure releases. Refer to Table 4 for details on the mapping of versions to bundles.
Table 4 Version Mapping
2.0(1m)
ucs-catalog.2.0.1j.T.bin
2.0(1q) and 2.0(1s)
ucs-catalog.2.0.1m.T.bin
UCS-MR-2X324RX-C on B440 M2
ucs-catalog.2.0.1o.T.bin 1
UCS-CPU-X5687 on B200 M2
UCSB-PSU-2500DC48 on the DC UCS 5108 chassis (UCSB-5108-DC)
UCS-HDD900GI2F106 on C200 and C210
UCS-HDD300GI2F105 on C200 and C210
1 Available for separate download.
Further details are in the UCS Manager GUI Configuration Guide.
Known Limitations and Behaviors
The following known limitations found in release 2.0(1) are not otherwise documented:
Cisco UCS Manager
•
•
•
•
•
•
•
•
OS
•
Fabric Interconnect
•
•
BIOS
•
Downgrade Issues
•
Resolved Caveats
The following caveats are resolved in the 2.0(1w) release:
•
•
•
•
•
•
•
•
•
The following caveats are resolved in the 2.0(1t) release:
•
•
•
•
The following caveats are resolved in the 2.0(1s) release:
•
•
•
The following caveats are resolved in the 2.0(1q) release:
Cisco UCS Manager
•
•
•
•
BIOS
•
Note
•
•
•
•
The following caveats are resolved in the 2.0(1m) release:
Cisco UCS Manager
•
•
•
•
•
•
•
•
•
Fabric Interconnect
•
Rack Integration
•
•
CIMC
•
•
Adapter Cards
•
VMware
•
•
RAID Controller
•
BIOS
•
•
Open Caveats
The following bugs were found in release 2.0(1m):
Symptom During upgrade from UCS 1.4 to 2.0, an SSLCert error may be written to the log files.
Workaround
Symptom After kernel rebuild or yum update a server configured for SAN Boot of RHEL 5.6 or RHEL 5.7 may fail to boot. This is a Red Hat issue, and ticket 744330 has been filed. It is a private ticket that may be referenced when calling Red Hat support for more information.
Workaround
Modify the /etc/modprobe.conf file to add the new entry "alias scsi_hostadapter2 fnic"
Also, if you have the entry "alias scsi_hostadapter2 usb-storage", modify it to: "alias scsi_hostadapter3 usb-storage" (CSCtq30308)
Symptom While upgrading to UCS 2.0 with QoS policies defined , critical errors will be displayed for all QoS policies and VIFs with QoS policies defined on them will be down after upgrading the subordinate interconnect but before upgrading the primary interconnect. Expect that during the upgrade there will be a period of downtime between when the primary restarts and when the secondary becomes primary and brings up its VIFs. During this time all blades will lose their connectivity to both LAN and SAN.
Workaround
Symptom A host configured for iSCSI boot will always boot off a LUN exported to the Primary iSCSI VNIC by default, as iBFT is always posted on the primary iSCSI vNIC. The secondary iSCSI vNIC will post iBFT in case the LUN discovery fails on the primary iSCSI vNIC. However, if the Secondary iSCSI vNIC comes up earlier than the Primary iSCSI vnic (due to its overlay vNIC having a lower PCI order than that of the overlay vNIC for the Primary) and LUN discovery fails on the Primary, then there is no iBFT posted and the host fails to boot.
Workaround
Symptom 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.
Workaround
Symptom After upgrade to 2.0(1m), blades with UCS M81KR adapters may show the error "initialize error 4" during FC boot.
Workaround
Open Caveats from Prior Releases
The following bugs were found in release 1.4(3q):
Symptom When a UCS M81KR or UCS M71KR-E/Q (NIV) adaptor is used, and the isolated host is communicating using a MAC configured in the service profile (and registered at the interconnect via a VIC) PVLAN traffic does not flow for an isolated host. Using the show platform fwm info hw-stm command at the NX-OS prompt shows that the isolated host MAC is learned on the isolated VLAN, but not learned on the primary VLAN.
Workaround
The following bugs were found in release 1.4(2b):
Symptom 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:
MRC - Warning Code:0x9 on Socket#1 Br#0 Ch#00, Ddr#00, Dimm#00, Rank#FF (if applicable)MRC - Warning Code:0x9 on Socket#1 Br#0 Ch#00, Ddr#01, Dimm#00, Rank#FF (if applicable)Workaround
The following bugs were found in release 1.4(1i):
High Availability
Symptom High Availability does not become ready until all 3 selected HA devices (chassis/rack-unit) have been discovered. The condition that triggers this problem is the fact that a previously functioning and fully discovered device (either chassis or rack mount server) has failed. This may be due to connectivity problems or faulty behavior. In this case the system remains in HA NOT READY state.
Workaround
Symptom When 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.
Workaround
BIOS
Symptom Blade and Rack Servers that include unequal sized HDDs or SSDs have encountered various failures intermittently. UCS Manager reports "Error Configuring Local Disk Controller" in most cases during these failures, though other errors are also seen.
Workaround
Symptom The BIOS Setup shows less memory size and some DIMMs disabled on a B230. The SMBIOS table does not report memory info in Type 17 structure for the disabled DIMMs. The UCSM reports less memory size and some DIMMS disabled. This happens when the BIOS disables some DIMMs incorrectly when DIMMs on certain slots do not have the corresponding lockstep pairs installed. For example, configurations that can cause this failure include:
1.
2.
3.
Workaround
CIMC
Symptom 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.
Workaround
Adapters
Symptom 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.
Workaround
Symptom CRC errors reported on an M81KR network interface on SLES 11 SP1. This is seen under High TX and RX traffic on SLES 11 SP1. The FIFO is not cleared as fast as it should because of some delays in the PCI path. An M81KR firmware devcmd storm from the host is also investigated to be one reason for the PCI stalls. These CRC errors are actually caused by FIFO overruns on the M81KR which are in turn caused by PCI stalls. They are not real CRC errors but truncated packets (due to FIFO overrun) flagged as CRC errors.
Workaround
UCS Manager
Symptom UCS Manager takes a long time to push configurations containing large number of port-profiles to the VMware Virtual Center (VC). This happens when large number of hosts and virtual machines (VMs) are configured (tested with 500 VMs on 60 hosts managed by same VC) and a large number of port-profiles assigned to multiple DVSes in the VCenter.
Symptom Wait until the operations complete. Configuration FSM could take more than 30 minutes. Then, configure a smaller number of port-profiles (we've measured up to 92 profiles to successfully configure in around 5 minutes in above large number of hosts and VMs situation). (CSCtk97755)
Symptom When 15 or more chassis are configured in release 1.4(1) and the system is downgraded to release 1.3(1), chassis beyond 14 are still there. This may cause some issues as the max chassis support enabled with the 1.3(1) release is 14.
Workaround
Symptom When a rack server has a local disk installed, it does not report real-time disk operability status (disk operability is reported as "N/A").
Workaround
Symptom When the UCS Manager shell mode is set to s either management or local-management mode, the CLI command terminal monitor is not available.
Workaround
Symptom The minimum power cap that can currently be set is 3400W. The chassis power cap has a lower limit of 3778 W (AC), which is internally converted to 3400 W (DC).
Workaround
Symptom The UCS Manager shell does not support redirection of show command output to a remote file system.
Workaround
Symptom In UCS Manager there is no option to change the port speed of the SPAN destination port.
Workaround
Symptom UCS Manager reports an unsupported DIMM as missing but does not raise a fault.
Workaround
Symptom If you delete an existing VMware data center objects & vCenter in the VM configuration tab, then create a new vCenter with the same IP address as previous VC server. UCS Manager sends an error stating "deletion of vCenter object is still in progress" and will not allow creation of new vCenter. The deletion of the previous vCenter had not succeeded and UCS Manager keeps retrying the deletion. Since 2 vCenters with same IP cannot exist in the system, UCS Manager disallows the second VC creation.
Workaround
UCS Manager GUI
Symptom 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. This defect has no functional impact.
Workaround
UCS Manager CLI
Symptom When VIF creation doesn't follow V-motion, NPPM doesn't move the VIF to a new dynamic and the stale VIF doesn't carry the traffic any more. This would cause the SPAN to stop monitoring the traffic from the original VM.
Workaround
Fabric Interconnect
Symptom 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.
Workaround
Symptom The server UUID displayed by ipmitool does not match that shown by the 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 UCS Manager CLI shows -
Dynamic UUID: 0699a6f3-1b81-45f8-a9f2-c1bbe089324e# ipmitool -H 10.193.142.104 -U gurudev -P password mc guidSystem GUID : f3a69906-811b-f845-a9f2-c1bbe089324eCompared to UCS Manager CLI or GUI output, the first 3 fields f3a69906-811b-f845 show up differently in the output of ipmitool.
Workaround
#ipmitool -H 10.193.142.104 -U gurudev -P password raw 0x06 0x3706 99 a6 f3 1b 81 45 f8 a9 f2 c1 bb e0 89 32 4eThe output matches the value printed by the UCS Manager CLI. (CSCtk09043)
Symptom The show port-security NXOS 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.
Workaround
Symptom 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.
Workaround
CIMC
Symptom Rack server does not show up in GUI or CLI within reasonable delay after a recommission. This happens when a rack server is recommissioned within a very short time of its decommissioning. The server has a DHCP lease expiration time from when it was decommissioned, which is a few minutes.
Workaround
Symptom The Blade CIMstic management IP address assignment is not included in backups.
Workaround
RAID/Local Disk
Symptom UCS Manager fails to report the Local Disk Failures, Faults, Alarms, Status and Disk Errors/Error Codes from the MegaRAID Controller on the B440 server.
Workaround
Symptom For the B200 and B250 blade servers, the Local Disks 'Operability' field is reported as "N/A". The 'Operability' field of the Local Disks in B200 and B250 is expected to have a correct value and should not be reporting 'N/A'.
Workaround
Symptom For the MegaRAID Controller on the B440 blade server, UCS Manager fails to report BBU Status, Properties and Errors.
Workaround
Symptom If one or more conditions are met, 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.
Workaround
Symptom 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.
Workaround
Symptom C210 and C250 rack servers are missing RAID 50 and RAID 60 support.
Workaround
Symptom UCS Manager fails to create a single disk striped RAID config in the Storage Controller 1064E environment.
Workaround
Release 1.2(1)
The following caveats were opened in Release 1.2(1):
Red Hat Linux
Symptom Loading multiple driver disks during a RHEL 5.x installation fails.
Workaround
BIOS
Symptom Hubs that only use USB 1.0 may not properly present an attached USB device to the UCS server.
Workaround
Cisco UCS Manager
Symptom The PCIe Address for the Cisco UCS M81KR Virtual Interface Card is not seen in the GUI (or CLI). It causes no functional impact.
Workaround
Symptom Modification of trusted CoS policy in Service Profile does not get immediately applied to the server. If you modify the trusted CoS policy of an adapter profile in a service profile that is currently attached to a physical server, a server reboot is needed. Since it is unsafe to automatically reboot an associated server, UCSM currently does not.
Workaround
Symptom 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.
Workaround
Cisco UCS Manager GUI
Symptom When upgrading from releases prior to 1.1.1, OS-specific default adapter policies will not have the current recommended default values.
Workaround
Eth VMWare->RSS: DisabledEth VMWarePassThru->RSS: EnabledEth default->RSS: EnabledFC (all)->FCP Error Recovery: DisabledFC (all)->Flogi Retries: 8FC (all)->Flogi Timeout: 4000FC (all)->Plogi Timeout: 20000FC (all)->IO Throttle Count: 16FC (all)->Max LUNs Per Target: 256(CSCte58155)
Symptom Logon access is denied for user accounts where the password field was left blank during user account creation.
Workaround
Release 1.1(1)
This section lists the open caveats in release 1.1(1j).
BIOS
Symptom With the B-250 blade server, the displayed ESX and Linux OS HDD Boot Device Order is the reverse of the BIOS HDD Boot Order.
Workaround
Symptom FSM gets stuck in an Error Configuring the Local Disk Controller state due to various underlying conditions. Those can include but are not limited to the following:
•
•
Workaround
Symptom The Disk Fault/Error Codes, Disk Status, Alarms and the failures forwarded by the SAS Controller are not received by Cisco UCS Manager.
Workaround
Symptom After resetting the CMOS the system date needs to be reset to current.
Workaround
Red Hat Linux
Symptom When a vNIC is not in failover mode and a link down event occurs, the network traffic on the blades is disrupted with a system running RHEL 5.3.
Workaround
1.
service network restartor
ifdown ethxifup ethx2.
•
•
•
Note that network performance may be affected since the system is running in legacy mode. (CSCte44548)
Cisco UCS Manager
Symptom After the removal or insertion of one or more local disks, their full discovery fails.
Workaround
Symptom For a given port profile with existing VIFs, if the "Max-Ports" setting is reduced from the currently configured value to a value less than the "Used-Ports" value reported for that port profile by VMware vCenter, this is a mis-configuration. The new value for "Max-Ports" for that port profile will only be updated in Cisco UCS Manager and its update in VMware Center will fail, causing a inconsistency between Cisco UCS Manager and VMware Center Server.
Workaround
Cisco UCS Manager GUI
Symptom When a cluster configuration is set up such that I/O module 1 goes to fabric interconnect B and I/O module 2 goes to fabric interconnect A, then the Ethernet devices are given ports 1 and 0. However if the setup is straight, with I/O Module 1 connected to fabric interconnect A and I/O Module 2 to fabric interconnect B, then the devices are assigned ports 0 and 1.
Workaround
UCS Manager CLI
Symptom The UUID of the VM changes in VMware vCenter. After a VM restarts, the virtual machine node on the VM tab shows multiple instances of the same VM with one online and one offline.
Workaround
Release 1.0(2)
The following caveats were opened in UCS software release 1.0(2) and are still unresolved.
BIOS
Symptom With various Local Disk Configurations, the LSI SAS Configuration Utility fails to launch while in BIOS.
Workaround
Symptom When the memory mirroring configuration is destroyed by removing a DIMM, the BIOS will switch to the Performance mode, and will not log a message that mirroring was disabled.
Workaround
Symptom When plugging or removing USB devices at BIOS Setup -> Advanced -> USB, the Setup Utility may hang.
Workaround
Fabric Interconnect
HTTP
Symptom HTTPD process crashed, with the following event log:
Process crashed. Core file 1253640662_SAM_ucs-6120-1-A_httpd_log.3114.tar.gz (SAM/Switch Core Dump) detected on fabric interconnect A
Workaround
UCS Manager GUI
Symptom When waking up from sleep, the UCS Manager GUI will detect an event sequencing error and display the error: "Event Sequencing is skewed" because the JRE doesn't have a sleep detection mechanism.
Workaround
Symptom Downloads may be slow if TFTP is used.
Workaround
Release 1.0(1)
The following caveats were opened in UCS software release 1.0(1e) and are still present.
AAA
Symptom Local user passwords can not contain "$" character.
Workaround
Adapters
Symptom When a service profile containing two vNICs and having failover enabled is applied to QLogic or Emulex CNAs, the failback timeout specified in the adapter policy for the second vNIC has no effect. The failback timeout specified in the adapter policy and applied to the first vNIC is applied to the whole adapter and is effective for both vNICs.
Workaround
BIOS
Symptom Installing EFI Native SLES 11 is currently not supported.
Workaround
Symptom One vNIC defined in the UCS Manager service profile boot order results in two BIOS vNICs.
Workaround
Fabric Interconnect
Symptom When a fabric interconnect boots, the "The startup-config won't be used until the next reboot" message appears on the console. Fabric interconnect configuration is controlled by the UCS Manager, so this message has no meaning on the fabric interconnect configuration and has no functional impact.
Workaround
Symptom Console logon user names on the fabric interconnect are not case sensitive. For example, there is no differentiation between admin and ADMIN.
Workaround
Symptom When the system is under high stress, with repeated port flapping (ports rapidly going up and down) and default (native) VLAN change, the FWM process may core and cause the fabric interconnect to reload.
Workaround
Symptom The show cdp neighbor CLI command does not display information for CDP neighbors seen from the management interface, nor does it display the fabric interconnect CDP information corresponding to the management interface.
Workaround
Faults and Alerts
Symptom In rare cases the 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: ClearedCode: F0367Last Transition Time: 2009-07-15T11:47:49ID: 646445Status: NoneDescription: No link between fabric extender port 2/1/1 and switch A:1/9Affected Object: sys/chassis-2/slot-1/fabric/port-1Name: Ether Switch Intfio Satellite Connection Absent Cause: Satellite Connection AbsentType: ConnectivityAcknowledged: NoOccurences: 1Creation Time: 2009-07-15T11:46:49Original Severity: MajorPrevious Severity: MajorHighest Severity: Major*******************************Workaround
Inventory
Symptom Hardware revision numbers for fabric interconnect components are not populated in the UCS Manager.
Workaround
1.
2.
Server
Symptom The disk scrub policy needs enhancements to meet DOD compliance.
Workaround
SNMP
Symptom SNMP shows the fabric interconnect name rather than system name.
Workaround
Symptom An SNMP user name can not be the same as a local user name.
Workaround
SMASH
Symptom Any SMASH command entered with wrong option should give "INVALID OPTION" error message.
Workaround
UCS Manager CLI
Symptom Statistics counters cannot be cleared using the UCS Manager CLI.
Workaround
UCS Manager GUI
Symptom When several KVM Consoles are launched, the SUN JRE sometimes reports an error and the KVM Console fails to launch.
Workaround
Symptom In the 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.
Workaround
Symptom Fibre Channel port and server port events do not appear on the Fibre Channel port and server port Events tabs.
Workaround
New Hardware Features in Release 2.0(1)
Release 2.0(1w) adds support for:
•
Release 2.0(1s) adds support for:
•
Release 2.0(1m) adds support for:
•
•
•
New Software Features in Release 2.0(1)
Release 2.0(1) adds support for:
•
•
•
•
•
•
•
•
•
•
Related Documentation
For related documentation, refer to this document:
•
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.
This document is to be used in conjunction with the documents listed in the Cisco UCS Documentation Roadmap.
CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website 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. (0711R)
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.
© 2011 Cisco Systems, Inc. All rights reserved.
