Cisco UCS Platform Emulator Release Notes version 2.2(3aPE1)
Cisco UCS Platform Emulator Release Notes version 2.2(3aPE1)
This document describes system requirements, new features, images information, known caveats and
workarounds for Cisco UCS Platform Emulator, Release 2.2(3aPE1). This document also includes
current information that became available after the technical documentation was published.
Use this release notes as a supplement with the other documents listed in the documentation roadmap
http://www.cisco.com/go/unifiedcomputing/b-series-doc.
Make sure to review other available documentation on Cisco.com to obtain current information on Cisco
UCS Platform Emulator.
Contents
This document includes the following sections:
• Revision History, page 2
• Introduction, page 3
• New Hardware Features, page 4
• New Software Features, page 4
• Known Limitations, page 5
• Open Caveats for Release 2.2(3aPE1), page 6
• Related Documentation, page 7
Americas Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
Revision History
Revision History
Table 1 shows the revision history:
Introduction
Cisco UCS Platform Emulator is the Cisco UCS Manager application bundled into a virtual machine
(VM). The VM includes software that emulates hardware communications for the Cisco Unified
Computing System (Cisco UCS) hardware that is configured and managed by Cisco UCS Manager. For
example, you can use Cisco UCS Platform Emulator to create and test a supported Cisco UCS
configuration, or to duplicate an existing Cisco UCS environment for troubleshooting or development
purposes.
Note Cisco UCS Platform Emulator, Release 2.2(3aPE1) replaces Release 2.2 (2cPE1). You should recreate a
new Cisco UCS Platform Emulator VM with the newest Cisco UCS Platform Emulator version to use
the latest features.
System Requirements
Before installing Cisco UCS Platform Emulator, ensure the system meets the following requirements:
• 2 GB free RAM
• 8 GB disk space
• 1.8-GHz single CPU
• A Mozilla-compatible browser (Firefox or Google Chrome)
• Java Runtime Environment 1.6 or later. You can download files from http://www.java.com
• Extended Direct Connect Rack support to configure multiple and different adapters on a rack
server
• New default configuration containing a mix of M3 and M4 blade and rack servers.
Known Limitations
Cisco UCS Platform Emulator, Release 2.2(3aPE1) has the following limitations:
• Download of stripped-down version of UCS Firmware- From UCS PE 2.2(1bPE1) onwards, only
the stripped-down version of size less than 50 KB is available for download. The download of
regular (non-stripped version) version is not supported anymore.
• Import from a running Cisco UCS system and import from XML—If you import a setup with
rack servers, we recommend that the setup is either a true high-availability (HA) or a true
stand-alone setup. If there is a mixed configuration then the import may not work.
• Recommission and decommission—Chassis and blade server recommission and decommission are
not supported. Only rack servers can be recommissioned or decommissioned.
• Domain Name Server (DNS) resolution— DNS resolution is not available for Cisco UCS Platform
Emulator. All domain names must be resolved manually using a static IP address.
• Blade server discovery—When a blade server discovery is complete, performing a power ON/OFF
to boot the server is not supported.
• Syslog—Cisco UCS Platform Emulator and Cisco UCS Manager integrated with Cisco UCS
Platform Emulator does not produce a syslog.
• Data path—Cisco UCS Platform Emulator does not emulate network data flow. The software
emulates the functions that are necessary for the management plane.
• XML Export in Google Chrome—The Startup Hardware Configuration user interface allows you
to save the XML-formatted hardware configuration to a local computer. This is the client computer
that is running the browser. To save the file, click Export Configuration to XML File > Save as…
and then save the XML text to a local file. However, If you are using Google Chrome, you must save
the file as a .txt file. If you save the file in another format such as .xml, Google Chrome adds
unnecessary HTML tags in the saved file produces an incorrect XML format.
• Microsoft Internet Explorer—Microsoft Internet Explorer does not support the Cisco UCS
Platform Emulator Model Object Browser and Start-up Inventory features. To use these features,
you must use a Mozilla-compatible browsers such as Mozilla Firefox or Google Chrome. Internet
Explorer Version 8.0 and later supports other Cisco UCS Platform Emulator features.
• Cut-through interfaces—Cut-through interfaces to equipment such as IPMI and SNMP, are not
supported. Servers in a Cisco UCS domain contain integrated management controllers (CIMCs),
each of which supports an IPMI interface. The fabric interconnect components of Cisco UCS
support an SNMP interface. However, because both fabric interconnects and CIMC are considered
to be endpoints of the Cisco UCS management system, these interfaces are cut-through interfaces
that bypass Cisco UCS Manager, the central management system.
• Serial over LAN, FTP, TFTP, Telnet— Similarly to SNMP and IPMI interfaces, serial over LAN,
TFTP, FTP, and Telnet access (through user-facing or management-plane-facing Ethernet interfaces)
is not available because they bypass the management software and are considered cut-through
access. SSH is supported only to the Cisco UCS Platform Emulator management IP through the
config user for Cisco UCS Manager CLI access.
Related Documentation
For more information, you can access related documents from the following links:
• Link to bundle images document
• Cisco UCS Documentation Roadmap
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.