on 05-26-2022 11:36 AM
Cisco UCS Platform Emulator, Release 4.2(2aPE1)
CONFIGURATION IMPORT NOTE: Importing configuration backups (All, System, or Logical) taken from the UCS Platform Emulator (UCSPE) to physical UCS Manager domains is not recommended or supported by Cisco TAC. UCSPE backups should only be imported to UCSPE domains.
New Features and Significant Changes in Cisco UCS PE, Release 4.2(2aPE1)
Hardware Feature Summary
Known Limitations
IMPORTANT CONFIGURATION NOTE: Backup/Import of UCSM Configuration
Firmware Management: UCSPE supports uploading B-Series and C-Series server firmware bundles. Because of the large file sizes of the firmware bundles, UCSPE only supports uploading of stripped-down versions (link below). Stripped-down versions include only the firmware metadata (not the actual firmware binaries).
Download Instructions
MD5 hashes for downloads:
Hello,
Thank you for these tools,
It is useful for testing, training and knowledge
Are there plans to have a new version of the simulator?
Regards,
Thanks!
Hi Anyone can take a look at below. The link between servers and FEX are down. Did I miss some step? Thanks
Will the new "X" series hardware be available in the emulator in future releases?
Guess that would technically now be called USCX?
The world is waiting : )
It's the best sales pitch and confidence possible for those of us on the fence.
Hello folks, I've had a VM built and things were working fine. However, I reset it to factory defaults and now I'm being prompted for a password that I don't have, didn't set, and can't locate a google search with the answer.
When I try and go to the CLI, I'm now being prompted for the samcontainer account password and I would like to know what that is...
Update: I'm also seeing this:
Logging in ...
Failed to open default netns file./apebox/menu.sh: line 63: 5041 Segmentation fault $UCSSH_CMD
Press any key to return to menu
When trying to access the CLI via SSH...
Any help would be highly appreciated!
@dsoper
Was a resolution ever published for the netns file issue when accessing the CLI?
Failed to open default netns file./apebox/menu.sh:
If so could you please post it. I see 2 users have same issue but don't see any resolution/workaround presented.
Would greatly appreciate your assistance.
Unfortunately I don't have a workaround for CLI login issues when UCSPE reports "Failed to open default netns file./apebox/menu.sh". That message and the segfault indicate issues with UCSPE processes and a new VM deployment would be needed if VM reboots don't resolve the issue.
Unfortunately, I've had the VM rebuilt three times...the cli issue still exists with each build.
What virtualization environment are you using (vSphere or other platform version)? I'll see if I can duplicate the issue.
@dsoper We're using vSphere...I tried it again a few times today, still no joy. Downloaded the OVA again just in case that was an issue. Thank you for looking into this, I appreciate it.
@dsoper VMware vCenter / ESXi 7.x. I and another college both tried to deploy multiple times.
I've duplicated the CLI segfault with vSphere 8.0u2, and unfortunately I haven't found a work-around. The GUI appears functional with vSphere 8.0u2 and would need to be used instead of the CLI. Sorry for the issue blocking CLI access.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: