Normal operation, relatively quiet -- more of a hum from the fans. All 12 cores utilized, it's like a jet.
$127 Cisco ENCS5412/K9 Xeon-D 1557 (12 core), 32G ram
- Thread starter RobstarUSA
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Give me a day or two. I will verify on a real ESXi Install instead of having you test it. But you will need NFVIS 4.15.x iso as part of generating the iso/ vmdk image. Essentially my tool extracts the necessary packages from an official image and adds custom scripts to the final image. I didn't want to distribute the image with Cisco software and get into licensing issues.
Last edited:
Yeah, wise move there. I was able to get 4.13.1 before I lost my partner level access to CCO. Lemme reach out to some of my contacts.
I'll PM you the link. 4.13.1 should work as well to be honest, but might as well use one of the newer ones if it's available. No bios or firmware upgrade needed for this to work. I'm still on the original bios and ENCS firmware.
Last edited:
This doesn't seem to work for me. Followed the steps exactly and each time I get "Invalid Password." I've also tried setting the password to blank before flashing 3.06 as well.
I tested it with esxi 8u3, you want to take a look at this
Last edited:
Holy hell, LOVE that write-up! Extremely thorough!
Only thing stopping me from deploying this "Right Now(tm)" is the fact that I'm currently not physically close to the one box I'd deploy it on. I've got the ENCS on a switchable PDU, so I could "remove power" if absolutely necessary, but it's not like I'm going to be making any network connections to it until I get there. In my spare time, this would be fun to get implemented though. Thank you!!
No problem. Just let me know when you get around to it if you run into issues or if you find bugs with the TUI.
Alright this whole password mess is easily solved. Currently running bios 4.03 and CIMC 3.2.14.27 (both extracted from 4.15.16 NFVIS). 4.03 doesn't have any issues preventing you from going into bios from boot screen. DEL works fine.
Here are the steps you want to take if you want to update both (redundant as some of you may already know but putting it here for reference for new users):
1. Log into CIMC -> Admin -> Firmware Management.
2. Check BMC and upload the your new CIMC bin. Once it's done You'll see it appear in the Backup Version. 3.2(14.27) is my version. Check BMC again and Activate. CIMC will reboot and the new version will be active.
3. From the same Firmware Management, check BIOS and upload the new bios bin. Once it's done uploading pull the power and let the server reboot and the new firmware will be active.
3a. It doesn't matter whether you have a previous password set or not. Starting with bios 2.11 an update will wipe the old password. This is why I haven't been able to get it working. But doesn't matter.
4. SSH into CIMC: ssh -o HostKeyAlgorithms=+ssh-rsa -o PubkeyAcceptedAlgorithms=+ssh-rsa admin@<CIMC IP>
4a. Once you're in type the following:
Bash:
scope bios
set password <your password>
commitset password)Warning:
Strong Password Policy is enabled!
For CIMC protection your password must meet the following requirements:
The password must have a minimum of 8 and a maximum of 20 characters.
The password must not contain the User's Name.
The password must contain characters from three of the following four categories.
English uppercase characters (A through Z)
English lowercase characters (a through z)
Base 10 digits (0 through 9)
Non-alphabetic characters (!, @, #, $, %, ^, &, *, -, _, +, =)
FYI to anyone using my ENCS-Switch port on Proxmox and ESXi, updating the bios might change the Marvel Switch PCI address which invalidates the setup.
Proxmox user: run encs-switch-tui --update to update to version 0.2.3 then run encs-switch-tui --update again to apply the fix. Shutdown your VMs, pull the AC plug. Everything should go back to normal.
ESXi user: You're not affected, patched the issue and as to my knowledge, no one is using it at the moment.
Proxmox user: run encs-switch-tui --update to update to version 0.2.3 then run encs-switch-tui --update again to apply the fix. Shutdown your VMs, pull the AC plug. Everything should go back to normal.
ESXi user: You're not affected, patched the issue and as to my knowledge, no one is using it at the moment.
Side question... 4.15.16 NFVIS? Typo for 4.15.6?
Was going to ask about where you were extracting those files from, but found in your script where that's happening. Inside the ISO image, locate the nfvis-fwupdate rpm in /packages. The files are inside that RPM in /opt/fwupdate/.
Great job on the TUI @foureight84 ! Stripped it enough to just control .0 endpoint, can share back.
Also can someone please share the latest nfvis to poke? I'm working on booting it thru ESXi in a way where I can install c8000v and pass LTE NIM thru. It's a ..chore. Thank you! (or just up to c**s maybe?)
Also can someone please share the latest nfvis to poke? I'm working on booting it thru ESXi in a way where I can install c8000v and pass LTE NIM thru. It's a ..chore. Thank you! (or just up to c**s maybe?)
4.15.5 is in there, that's the most recent they have for the 5412. 4.15.6 is the only thing later, I haven't found that anywhere.
Haha. Typo. 4.15.6, what I meant to saySide question... 4.15.16 NFVIS? Typo for 4.15.6?
Was going to ask about where you were extracting those files from, but found in your script where that's happening. Inside the ISO image, locate the nfvis-fwupdate rpm in /packages. The files are inside that RPM in /opt/fwupdate/.
Version 0.2.4 released Release encs-host 0.2.4 · foureight84/encs5400-almalinux
build.sh now allows for building the Proxmox qcow2 with seabios instead of ovmf:
build.sh --firmware seabios|ovmf|both (default both)
Update by either downloading the release or git pull from the cloned project folder (main branch).
The seabios version allows for 256mb VM memory usage where as the ovmf will need to run with 384mb. ESXi image already only requires 256mb of memory.
I don't recall how much memory NFVIS takes up but this should be less (maybe by a considerable amount; might be 2GB? if someone could let me know). If you run into issues, just file it on Github so we don't pollute this thread.
build.sh now allows for building the Proxmox qcow2 with seabios instead of ovmf:
build.sh --firmware seabios|ovmf|both (default both)
Update by either downloading the release or git pull from the cloned project folder (main branch).
The seabios version allows for 256mb VM memory usage where as the ovmf will need to run with 384mb. ESXi image already only requires 256mb of memory.
I don't recall how much memory NFVIS takes up but this should be less (maybe by a considerable amount; might be 2GB? if someone could let me know). If you run into issues, just file it on Github so we don't pollute this thread.