The Cisco IMC Emulator allows users to familiarize themselves with Cisco’s UCS Standalone Management platform, also known as the Cisco Integrated Management Controller (Cisco IMC). It provides access to all three management interfaces Cisco offers today – WebUI, CLI, and the XMLAPI. The Cisco IMC Emulator is supported on the following servers: C220M4, C240M4, C460M4.
The emulator enables users to do the following:
View and explore the available Cisco IMC features without the need for physical HW. For example, experiencing the new HTML5 based WebUI that launched with Cisco IMC 3.0(1c) firmware.
Become familiar with select Cisco UCS hardware and standalone management solutions before purchasing equipment.
Set up automation scripts / programmatic deployments using the XML API. This can save time for our customers.
Current Release 3.0(3f):
The latest release of the Cisco IMC Platform Emulator brings the following changes:
- Emulator is now bundled as an OVA for seamless deployment, eliminating the requirements for pre-configured Linux hosts
- Emulator now has multi-threaded QEMU support, allowing for faster interaction via the API, and overall performance increase
- ZIP file includes individual platform versions if deploying a VM is not possible. These can be run inside RHRL 7.0/CentOS 6.5 and have the same prerequisites as the initial release.
**User Guide for current release is posted in the Attachments section below. The OVA/ZIP files can be found on Box:
Cisco IMC Platform Emulator – version 3.0(3a). This release adds many new features, including the following:
- VIC Configuration
- BIOS Configuration
- WebUI based Emulator configuration (previously, this was CLI only)
- Configurable IMC Emulator MAC Address and Serial Number
- Various bug fixes
The Cisco IMC Platform Emulator is now bundled into a single .zip file. The package needs to be unpacked as before, and uses a “launch.sh” script in the root directory (cimc_emulator-3.0.3a) to launch the emulator. Individual platforms can still be accessed using the CLI by navigating to cimc_emulator-3.0.3a\prod\<desired platform>. Please reference the latest user guide for additional details.
You can access the Cisco IMC Emulator platform images from the link below:
The emulator runs from a 64bit linux host, and was tested with RHEL 7.0 and CentOS 6.5. When using Windows, you must ensure Virtual Box software is installed, and an appropriate 64 bit linux OS is provided. The host machine must have the tunctl and brctl commands to create the tap network and the bridge network, respectively (these are used for accessing/communicating with the emulated IMC). There is also a configuration file that can be modified in real time, and allows users to adjust various IMC sensor values, mimic faults, and perform device state changes.
The video below provides an overview of the Cisco IMC Emulator and also explains how to install the utility.
I moved a pair of FIs from a DR data center and was hoping to make use of them. But I noticed warningsabout ethernet port usage being in grace period. Will the ports stop working if in "grace period" state?Perhaps the engineer who installed these just nev...
Hi experts,I have a question about access speeds across the UCS fabric - or more precisely, I'm hoping someone can verify the claims made by Sebastian Rocco, who describes hmself as a "Data Center Product Specialist out of California" in a CIsco you tube ...
Hi, With the recent VCenter security vulnerability (VMware vCenter Server updates address remote code execution vulnerability in the vSphere Client (CVE-2021-21972)), one of the workaround was to disable the CIM server, could anyone advise the ...
2 weeks ago, as part of deploying a new UCS deployment with 6332-16UP FIs I upgraded the FW from 4.0(4c) to 4.1(3b) I received the below minor fault:"Partition bootflash on fabric interconnect A is clean but with errors." Code F2016After consulting some d...
Is it possible to change or define a user-defined hostname for the Hyperflex storage controller VMs? I'd like to change it from the system generated SpringPathControllerxxxxxxxxxxx without causing any issues if possible.