Table Of Contents
Release Notes for Cisco UCS E-Series Servers, Release 1.0(2)
New Features Introduced in This Release
Router, E-Series Server, and Cisco IOS Software Version Compatibility
Important Information About VMWare FL-SRE-V-HOST License
Software Release Version Mismatch
Command Change for Determining the MAC Address in the Linux Operating System
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco UCS E-Series Servers, Release 1.0(2)
June 19, 2013OL-28686-02
This document provides new features, system requirements, compatibility information, and open caveats for the Cisco UCS E-Series Server software release1.0(2). Use this document in conjunction with the documents in the Related Documentation section.
Note Documentation is sometimes updated after original publication; therefore, review the documentation on Cisco.com for any updates.
Contents
This document contains the following sections:
•New Features Introduced in This Release
•Router, E-Series Server, and Cisco IOS Software Version Compatibility
•Important Information About VMWare FL-SRE-V-HOST License
•Software Release Version Mismatch
•Command Change for Determining the MAC Address in the Linux Operating System
•Obtaining Documentation and Submitting a Service Request
Introduction
The Cisco UCS E-Series Servers (E-Series Servers) are the next generation of Cisco UCS Express servers. E-Series Servers are a family of size, weight, and power-efficient blade servers that are housed within the Generation 2 Cisco Integrated Services Routers (ISR G2) and the Cisco 4451-X Integrated Services Router (Cisco ISR 4451-X). These servers provide a general purpose compute platform for branch-office applications deployed either as bare-metal on operating systems, such as Microsoft Windows or Linux, or as virtual machines on hypervisors, such as VMware vSphere Hypervisor™, Microsoft Hyper-V, or Citrix XenServer.
New Features Introduced in This Release
The following new features are introduced in this release:
•Windows 2012 Server support
Note With Windows 2012, you do not need to install extra drivers, such as LSI and network drivers.
•Citrix XenServer 6.1 certification
•New platform support—Cisco ISR 4451-X
•New document—Getting Started Guide for Cisco UCS E-Series Servers, Release 1.0(2)—Installed in Cisco ISR 4451-X.
Note If the E-Series Server is installed in a Cisco ISR 4451-X, use the Getting Started Guide for Cisco UCS E-Series Servers, Release 1.0(2)—Installed in Cisco ISR 4451-X.
Note If the E-Series Server is installed in a Cisco 2900 or 3900 ISR G2, see the Getting Started Guide for Cisco UCS E-Series Servers, Release 1.0.
•Cisco IOS CLI activation
Table 1 shows the Cisco IOS CLIs that are activated in this release. For details about each command, such as command history, usage guidelines, and examples, see the Cisco IOS Interface and Hardware Component Command Reference at: http://www.cisco.com/en/US/docs/ios-xml/ios/interface/command/ir-t2.html.
System Requirements
This section describes the hardware and software requirements. It contains the following information:
Hardware Requirements
E-Series Servers reside in the Cisco 2900 series or 3900 series ISR G2 and in the Cisco ISR 4451-X. The following E-Series Servers are supported:
•UCS-E140S—Single-wide E-Series Server
•UCS-E140D—Double-wide E-Series Server, 4 core CPU
•UCS-E160D—Double-wide E-Series Server, 6 core CPU
•UCS-E140DP—Double-wide E-Series Server, 4 core CPU, with PCIe
•UCS-E160DP—Double-wide E-Series Server, 6 core CPU, with PCIe
Table 2 provides hardware information for the E-Series Servers.
Table 2 E-Series Server Hardware at a Glance
Feature UCS-E140S
Single-Wide E-Series Server) UCS-E140D and UCS-E160DDouble-Wide E-Series Servers UCS-E140DP and UCS-E160DP
Double-Wide E-Series Servers with PCIeForm Factor
Single-wide SM
Double-wide SM
Double-wide SM
CPU
Intel XeonTM
E3-1105C
Intel XeonTM
E5-2418L and E5-2428L
Intel XeonTM
E5-2418L and E5-2428L
CPU Cores
4 Core
4 Core and 6 Core
4 Core and 6 Core
Memory DIMM Slots
2 Slots
3 Slots
3 Slots
RAM
8 GB to16 GB
Supports DDR3 1333 MHz VLP UDIMM 1.5 V, 4 GB, and 8 GB
8 GB to 48 GB
Supports DDR3 1333 MHz RDIMM 1.35 V, 4 GB, 8 GB, and 16 GB
8 GB to 48 GB
Supports DDR3 1333 MHz RDIMM 1.35 V, 4 GB, 8 GB, and 16 GB
RAID
RAID 0 and RAID 1
RAID 0, RAID 1, and RAID 5
RAID 0 and RAID 1
Storage Type
SATA, SAS, SSD, and SED
SATA, SAS, SSD, and SED
SATA, SAS, SSD, and SED
HDD
SAS 10K RPM, SATA 7200 RPM, and SAS SSD Drives1
Supports 2 Drives
SAS 10K RPM, SATA 7200 RPM, and SAS SSD Drives1
Supports 3 Drives
SAS 10K RPM, SATA 7200 RPM, and SAS SSD Drives1
Supports 2 Drives
Storage Capacity
200 GB to 2 TB
200 GB to 3 TB
200 GB to 2 TB
Internal Network Interface
2 Gigabit Ethernet Interfaces
2 Gigabit Ethernet Interfaces
2 Gigabit Ethernet Interfaces
External Interfaces
1 USB Connector
1 RJ-45 Gigabit Ethernet Connector
1 Management Port
1 KVM Port (Supports VGA,
1 USB, 1 Serial DB9)2 USB Connectors
2 RJ-45 Gigabit Ethernet Connectors
1 Management Port
1 VGA Port
1 Serial DB9
2 USB Connectors
2 RJ-45 Gigabit Ethernet Connectors
1 Management Port
1 VGA Port
1 Serial DB9
Router Platforms
2911, 2921, 2951, 3925, 3925e, 3945, 3945e, 4451-X
2921, 2951, 3925, 3925e, 3945, 3945e, 4451-X
2921, 2951, 3925, 3925e, 3945, 3945e, 4451-X
Maximum Number of E-Series Servers Per Router
2911 ISR G2—1 E-Series Server
2921 ISR G2—1 E-Series Server
2951 ISR G2—2 E-Series Servers
3925 ISR G2—2 E-Series Servers
3925e ISR G2—2 E-Series Servers
3945 ISR G2—4 E-Series Servers
3945e ISR G2—4 E-Series Servers
ISR 4451-X—2 E-Series Servers
2911 ISR G2—None
2921 ISR G2—1 E-Series Server
2951 ISR G2—1 E-Series Server
3925 ISR G2—1 E-Series Servers
3925e ISR G2—1 E-Series Server
3945 ISR G2—1 E-Series Server
3945e ISR G2—1 E-Series Server
ISR 4451-X—1 E-Series Server
Note The Cisco 2921 and 2951 ISR G2 support 4-core only.
2911 ISR G2—None
2921 ISR G2—1 E-Series Server
2951 ISR G2—1 E-Series Server
3925 ISR G2—1 E-Series Servers
3925e ISR G2—1 E-Series Server
3945 ISR G2—1 E-Series Server
3945e ISR G2—1 E-Series Server
ISR 4451-X—1 E-Series Server
Note The Cisco 2921 and 2951 ISR G2 support 4-core only.
1 All hardware drives within the E-Series Server must be installed with the same type of storage device; either all SAS drives or all SATA drives.
Table 3 shows the Cisco EtherSwitch Enhanced High-Speed WAN Interface Cards (EHWICs) and
Cisco EtherSwitch Service Modules that are supported on the E-Series Server.
Software Requirements
E-Series Servers require three major software systems:
•Operating System or Hypervisor
CIMC Firmware
Cisco Integrated Management Controller (CIMC) is a management module, which is built into the motherboard. A dedicated ARM-based processor, separate from the main server CPU, runs the CIMC firmware. The system ships with a running version of the CIMC firmware. You can update the CIMC firmware, but no initial installation is needed.
CIMC is the management service for the E-Series Servers. CIMC runs within the server. You can use CIMC to access, configure, administer, and monitor the server.
BIOS Firmware
BIOS initializes the hardware in the system, discovers bootable devices, and boots them in the provided sequence. It boots the operating system and configures the hardware for the operating system to use. BIOS manageability features allow you to interact with the hardware and use it. In addition, BIOS provides options to configure the system, manage firmware, and create BIOS error reports. The system ships with a running version of the BIOS firmware. You can update the BIOS firmware, but no initial installation is needed.
Operating System or Hypervisor
The main server CPU runs on an operating system such as Microsoft Windows, Linux, or Hypervisor. You can purchase an E-Series Server with a preinstalled operating system such as Microsoft Windows or VMware vSphere HypervisorTM, or you can install your own operating system.
The following operating systems are supported on the E-Series Servers:
•Microsoft Windows:
–Windows Server 2008 R2 Standard 64-bit
–Windows Server 2008 R2 Enterprise 64-bit
–Windows Server 2012 Standard 64 bit
•Linux:
–Red Hat Enterprise Linux 6.2
–SUSE Linux Enterprise 11, service pack 2
–Oracle Enterprise Linux 6.0, update 2
•Hypervisor:
–VMware vSphere HypervisorTM 5.0, update 1
–Hyper-V (Windows 2008 R2)
–Citrix XenServer 6.1
E-Series Server Options
E-Series Servers are available in the following options:
•Option 1—E-Series Server without preinstalled operating system or hypervisor
•Option 2—E-Series Server with preinstalled Microsoft Windows Server
At the time of purchase, you can choose the appropriate RAID option that you want enabled on the E-Series Server.
Note If you purchase this option, the Microsoft Windows Server license is preactivated.
•Option 3—E-Series Server with preinstalled VMware vSphere HypervisorTM
At the time of purchase, you can choose the appropriate RAID option that you want enabled on the E-Series Server.
Router, E-Series Server, and Cisco IOS Software Version Compatibility
Table 4 provides the router, E-Series Server, and Cisco IOS software version compatibility information.
Important Information About VMWare FL-SRE-V-HOST License
If you are using VMware FL-SRE-V-HOST license (equivalent to VMware vSphere Hypervisor™ 5.X), make sure that the RAM that you are using is 32 GB or less. If the RAM is more than 32 GB, you will get an error message, and you will not be able to apply the license. If you want to use 48 GB RAM, upgrade your license to FL-SRE-V-HOSTVC.
Software Release Version Mismatch
Even though the software version you download from Cisco.com is release 1.0(2), the CIMC GUI and CIMC CLI display the software version as 1.0(4). There is no effect on product functionality. Please ignore this version mismatch.
Command Change for Determining the MAC Address in the Linux Operating System
The command to determine the MAC address in the Linux operating system is documented as
ipconfig all in the Getting Started Guide for Cisco UCS E-Series Servers, Release 1.0, which is incorrect.To determine the MAC address of an interface in the Linux operating systems, open a terminal window, and then enter the ifconfig -a command to display the MAC address of all interfaces or
ifconfig interface-name to display the MAC address of a particular interface.
Open Caveats
Table 5 lists the caveats that are open for the E-Series Servers.
Table 5 Open Caveats in E-Series Servers
Bug ID Summary Additional InformationCSCug24890
E-Series Server in "out of service" state after CIMC reboot.
Symptom After rebooting or activating the CIMC image, you use the show platform command from the router, and the command output displays that the state of the E-Series Server as "out of service".
Conditions This problem occurs when you enter the following commands:
1. hw-module subslot x/y maintenance enable to make sure that the E-Series Server does not power cycle when the newly installed CIMC image reboots or activates.
2. Reboot or activate the CIMC image.
3. After CIMC boots up, enter the hw-module subslot x/y maintenance disable to disable the maintenance CLI.
4. Enter the show platform command from the router and the command output displays that the E-Series Server state as "out of service".
Workaround There is no workaround.
Note Even though the state of the E-Series Server displays as "out of service", communication between the router and E-Series Server remains operational.
CSCud44335
The imc config file command does not work.
Symptom The imc config file command does not work.
Conditions The imc config file command is not active.
imc config file ?flash0: Module configuration IOS File nameflash1: Module configuration IOS File nameflash: Module configuration IOS File nameWorkaround There is no workaround. This problem will be fixed in the next release.
CSCuf61866
Hardware failure displayed in technical logs.
Symptom CIMC does not boot up. The following status displays: Waiting BIOS POST.
Conditions This problem could occur because of a failed hardware, such as a failed DIMM, which can cause the POST to not complete.
Workaround To resolve this problem, remove the server from the router, and then try different DIMMs to determine which one is causing the problem.
CSCug77757
The Mega RAID Controller BIOS is disabled.
Symptom After BIOS POST screen, the "Adapter BIOS Disabled" error message displays, and the server is unable to boot from the RAID adapter.
Conditions This problem might occur in some of the E-Series Servers that shipped between February and May, 2013.
Workaround To resolve this problem, you must first disable and then enable the Controller BIOS. You can use either the WebBIOS or the Mega RAID CLI to perform this task.
•From the WebBIOS, do the following:
a. Choose Controller Property.
b. Choose Controller BIOS disable.
c. Click Submit.
d. Choose Controller Property.
e. Choose Controller BIOS enable.
f. Click Submit.
•From the Mega RAID CLI, use the following commands:
a. To disable the Controller BIOS, use the /MegaCli -AdpBIOS -Dsbl -a0 command.
b. To enable the Controller BIOS, use the/MegaCli -AdpBIOS -Enbl -a0 command.
CSCug59769
Kernel back trace when CIMC firmware is activated or rebooted.
Symptom The CIMC console shows kernel back trace when CIMC is rebooting.
Conditions This problem occurs when the newly installed CIMC firmware is activated or when CIMC is rebooted.
Workaround In most cases, CIMC will reboot itself. If CIMC does not reboot, power cycle CIMC either by using the router's OIR commands or by power cycling the router itself.
CSCug49179
KVM console display does not refresh.
Symptom When the E-Series Server is power cycled, the virtual KVM screen turns black, and then briefly flashes back to the old screenshot before it displays the BIOS pages.
Conditions This problem occurs when the E-Series Server is power cycled and the virtual KVM is used to monitor the console output.
Workaround There is no workaround. This is a known problem. Besides the brief flashing back of the old screen, there is no effect on the server performance.
CSCuh18187
RBCP registration fails on the single-wide E-Series Server.
Symptom On the single-wide E-Series Server (UCS-E140S) after the server is power cycled (especially the first time after the router is powered on), the link between the router and E-Series Server does not come up, and the commands sent from the router do not complete. The show link state command displays the following:
ucs-e140s-m1 /cimc/network # show link-stateInterface State------------------------------ --------------------Console No Link DetectedGE1 No Link DetectedGE2 No Link DetectedDedicated No Link DetectedConditions This problem occurs occasionally after a single-wide E-Series Server is power cycled.
Workaround To resolve this problem, change the ResumeOnACPowerLoss setting to Power Off.
Further Problem Description This problem occurs because the firmware that is installed on the Broadcom 5719 is out-of-date. You can upgrade the firmware from Linux or Windows OS using Broadcom tools. The Broadcom tools are available at: http://developer.cisco.com/web/ucse/documentation.
You can also use Cisco's Host Upgrade Utility to upgrade the firmware.
Note The latest version for the NCSI firmware is release, 1.2.15. The latest version for the bootcode is release, 1.34.
CSCug75113
Exiting from the ucse configuration mode does not return to global configuration mode.
Symptom When you enter the exit command from the ucse subslot configuration mode on the Cisco ISR4451-X, you return to the exec mode instead of the global configuration mode.
Workaround To get back to the global configuration mode, enter configure terminal at the command prompt.
CSCug78059
UCSE temperature alert when the temperature is not above the maximum threshold.
Symptom Temperature sensor P1_TEMP_SENS shows a non-recoverable error, even though the temperature has not reached the warning threshold.
Conditions This problem occurs on single-wide E-Series Servers (UCS-E140S-M1/K9).
Workaround To resolve this problem, reset CIMC to factory default settings, which will clear the error state. However, this problem will recur the next time you power cycle the server. This problem will be fixed in the next release of the CIMC software.
Further Problem Description CIMC does not measure the processor temperature correctly. However, the Intel processor has its own internal temperature monitoring and throttling, which takes effect when the temperature starts to get too high. Therefore, there is no concern about overheating due to this error in CIMC.
CSCub97383
Cannot download ISO or DIAG images after you click unmap from the CIMC GUI.
Symptom Cannot download ISO or DIAG images.
Conditions This problem occurs when there is no image installed and you click unmap from the CIMC GUI, and then you try to download an image.
Workaround To resolve this problem, reload CIMC; or from the vKVM console, unmap all the devices that are mapped, and then try to download the image.
CSCud08529
WHEA test fails for Windows 2012 HCK certification.
Symptom The Windows 2012 HCK certification test fails.
Conditions WHEA fatal error is displayed if you are using a JBOD single disk or if there is a hardware failure.
Workaround There is no workaround.
CSCud63080
The server reset boot url flash command does not work.
Symptom The server reset boot url flash command does not work.
Conditions The server reset boot url flash command is not effective.
Workaround There is no workaround.
CSCud65253
The show imc filesystem command does not display all downloaded files.
Symptom The show imc filesystem command output displays only five files.
Conditions When you use the show imc filesystem command, all of the downloaded files are not displayed.
Workaround There is no workaround.
CSCud75221
Operating system displays 2x core count on single-wide E-Series Servers.
Symptom The operating system displays 2x core count in single-wide E-Series Servers.
Conditions When you disable Hyperthreading from the BIOS or CIMC menu, the operating system displays 2x core count in single-wide E-Series Servers.
Workaround There is no workaround.
CSCud44380
File download progress status not displayed on Cisco IOS.
Symptom File download progress status is not displayed on Cisco IOS.
Conditions When you use the CIMC GUI to download a file, the download progress status is not displayed in Cisco IOS.
Workaround File downloaded status can only been seen on the CIMC GUI page. To view the file download status, check the CIMC GUI.
CSCud48758
P1_TEMP_SENS sensor displays a very high value in CIMC.
Symptom The P1_TEMP_SENS sensor displays a very high value in CIMC.
Conditions When running the Redhat memory test on a single-wide E-Series Server that is installed in a Cisco 2951 router, the P1_TEMP_SENS sensor displays a very high value.
Workaround To resolve this problem, format the CIMC SD, and then reinstall CIMC.
CSCud46445
Restoring the configuration file from flash does not work.
Symptom The imc config restore flash command does not restore the CIMC configuration file from IOS.
Conditions You copy a file, and then you use the imc config restore flash command to restore the configuration, but the configuration is not restored.
Workaround There is no workaround.
CSCud48807
File with img extension is not visible in the imc file system after it is downloaded.
Symptom File with img extension is not visible in the imc file system in Cisco IOS.
Conditions .This problem occurs when you are downloading a file with an img extension into the imc file system using Cisco IOS.
Workaround Use the CIMC GUI to download a file that has an img extension.
CSCud51345
Missing image information in CIMC GUI when the image is downloaded from Cisco IOS.
Symptom Image information is missing in CIMC GUI.
Workaround Image information is missing in CIMC GUI when the image is downloaded from Cisco IOS.
Workaround There is no workaround.
CSCud44355
Downloading an ISO file that is larger than the available space does not display proper error message.
Symptom Cannot download an ISO file that is larger than the available free space.
Conditions You cannot download an ISO file larger than the free space that is available in the file system. Also, the error message takes a long time to display.
Workaround There is no workaround.
CSCud48942
Image name appended with (GUI) in the imc file system.
Symptom Image name is appended with (GUI) in the imc file system.
Conditions When you download an ISO file using the CIMC GUI, the image name is appended with (GUI) in the imc file system.
Workaround There is no workaround.
CSCud44414
Wrong error message displays if a file does not exist and you use the server reset boot URL ftp command.
Symptom The following error message displays if a file does not exist and you use the server reset boot URL ftp command:
Server will be booted after image downloading is complete.
Conditions You use the server reset boot URL ftp command when a file does not exist on the ftp server and you get a wrong error message.
Workaround There is no workaround.
CSCud63080
The server reset boot URL ftp command does not work.
Symptom The server ip address command does not work.
Conditions The server ip address command is no longer applicable.
Workaround Do not use this command.
CSCud44151
The server ip address command does not work.
Symptom The server ip address command does not work.
Conditions The server ip address command is no longer applicable. It will be removed in the next release.
Workaround Do not use this command.
CSCub58962
The imc config file command does not work.
Symptom The imc config file command does not work.
Conditions The imc config file command is no longer applicable. It will be removed in the next release.
Workaround Do not use this command.
CSCud48826
Error message does not display when a file does not have read permission and you use the server reset boot command.
Symptom An error message does not display when a file does not have read permission and you use the server reset boot command.
Conditions File does not have read permission and you use the server reset boot command. An error message should display, but it does not.
Workaround Do not use this command.
CSCtz86835
The virtual drive information is missing after a CIMC upgrade.
Symptom The virtual drive information may not show any virtual drives that were configured previously.
Conditions This may occur immediately after a CIMC upgrade.
Workaround Refresh GUI page. If that does not help, reboot host and enter into LSI WebBIOS to verify the virtual drives.
CSCty86334
The VMware vSphere Hypervisor 5.0 installation crashes with purple screen if Virtual D rive stripe size is less than 64 KB.
Symptom The VMware vSphere Hypervisor installation fails with Purple Screen of Death (PSOD).
Conditions The raid array was created with a stripe size of less than 64 KB.
Workaround Use the default 64 KB stripe size during raid array creation.
CSCty61983
The rebuild is stuck at 0% when the host is in pre-boot environment.
Symptom The rebuild does not proceed and seems to get stuck.
Conditions The host is not booted up and is not at LSI WebBIOS environment.
Workaround Boot the host, or press Ctrl+H to enter LSI WebBIOS. The rebuild reconstruction will now proceed.
CSCtz71108
Cannot create (secure) virtual drive from CIMC GUI using SED drives.
Symptom The raid arrays that were created from CIMC GUI are not secured even if SED physical drives were used.
Conditions Using CIMC GUI to create raid array on SED drives does not create secure drives.
Workaround Use LSI WebBIOS to create the raid array.
CSCua29947
The inventory of memory does not display correct information in the web.
Symptom On E-Series single-wide servers, some of the information under
Server > Inventory > Memory is not correct, such as the memory manufacturer, serial number, asset tag and part number.Workaround There is no workaround.
CSCub20023
The lock power button locks the reset button.
Symptom The front panel reset button does not work.
Conditions The lock power button is active in CIMC.
Workaround Unlock the power button from CIMC.
CSCtz81924
The clear configuration does not clean all the partitions created by an old operating system.
Symptom The installation of a newer operating system can still see some of the partitions that were created by the previous operating system.
Conditions This happens while trying to install Windows operating system on a system that previously had VMware vSphere Hypervisor on it. The Windows operating system installation may show several partitions that does not correspond to the created raid arrays / JBOD disks.
Workaround Perform the following steps to delete old partitions created by an old operating system:
1. Use Drive options (advanced) from the windows installation window.
2. Delete all the other partitions that have the name Disk _ Partition _. Do not delete the Disk _ Unallocated Space partition.
3. After all the other partitions are deleted, the Unallocated Space partition should show full drive capacity.
4. Windows installation should now proceed as expected.
Another way to avoid running into this issue is to do a full initialization at the time of raid array creation. Note that full initialization takes several hours to complete depending on the disk size.
CSCua29511
The full initialization on STEC SSD reports offline array and failed drives.
Symptom After creating a raid array, it appears offline and all the drives in the physical drive information page appears failed.
Conditions This happens when a full initialization is issued on STEC SSDs at the time of raid array creation.
Workaround The full initialization on STEC SSD drives is not currently supported. Use quick initialization instead to create optimal raid arrays.
CSCub37825
The Windows installation using IDE DVD or KVM failed with 0x80070570.
Symptom The installation of windows 2008 R2 sometimes fail with windows code 0x80070570.
Conditions The failure occurs when using IDE drive and mount it to install windows via KVM.
Workaround Use direct USB drive and connect it to UCSE USB port.
CSCua37395
The software becomes unreponsive when booting Centos live in CD.
Symptom The CIMC on UCS-E becomes unresponsive if you boot Centos 5.6 or lower versions on X86.
Conditions Installed a Centos 5.6 or lower version IOS through virtual media or external CD drive.
Workaround Only the Centos version 5.7 or higher versions are supported on the UCS-E platforms. The Centos 5.6 or lower versions are not supported on the UCS-E platforms because of the incompatibility in the network drivers packaged in the version for BCM5719.
CSCuc11612
Wake on LAN is not working in Windows 2008 R2.
Symptom Wake on LAN is not working.
Conditions In Windows 2008 R2.
Workaround This feature is not supported. There is no workaround.
Resolved Caveats
Table 6 lists the caveats from 1.0 that are resolved in the1.0 (2) release.
Related Documentation
The following related documentation is available for E-Series Servers:
•Documentation Guide for Cisco UCS E-Series Servers—provides links to the following documents:
–Release Notes for Cisco UCS E-Series Servers, Release 1.0(2) (this document)
–Getting Started Guide for Cisco UCS E-Series Servers, Release 1.0—Installed in Cisco 2900 and 3900 Integrated Services Routers (ISR G2)
–Getting Started Guide for Cisco UCS E-Series Servers, Release 1.0(2)—Installed in Cisco ISR 4451-X
–Hardware Installation Guide for Cisco UCS E-Series Servers
–Cisco Network Modules, Server Modules, and Interface Cards Regulatory Compliance and Safety Information
–GUI Configuration Guide for Cisco UCS E-Series Servers Integrated Management Controller, Release 1.0
–CLI Configuration Guide for Cisco UCS E-Series Servers Integrated Management Controller, Release 1.0
–Troubleshooting Guide for Cisco UCS E-Series Servers
–Open Source Used in Cisco UCS E-Series Servers, Release 1.0
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 a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
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 Cisco Systems, Inc. All rights reserved.