$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.
enp5s0 is a X552 10gb nic integrated in the xeon processor afaik, but it is not exposed anywhere externally.
11ab:be00 is the PCI vendor/device ID for the Marvell Ethernet switch. 0000:0e:00 is the PCI address, but I have seen this change after messing around in the BIOS.
If it gets far enough for the "Service CPU not ready" I typically have only seen that when the switch has already been bootstrapped. I have not yet found a way to reset the switch without power cycling the entire box.
Should be the dedicated and then plug into "CIMC MGMT" I have had some issues when you unplug and plug in the CPU MGMT port causing issues with it. The shared option is supposed to use the GE ports but I'm not sure if it will work or not if you aren't using the NFVIS software. There is an extra interface that shows up under Proxmox that doesn't seem to have a physical presence on the box so that might be what the CIMC uses for the "shared" connection.
The onboard ports are connected to the PCH SATA controller. For SAS, you have to upgrade with their SAS RAID HBA that I have never seen in the wild.
So after playing around for a few hours I was able to get Proxmox to output to the serial over LAN connection but not from the actual console port. It appears the serial over LAN port is ttyS0 but I can't seem to find what device is assigned to the console port on the chassis. But the basics were to add "console=ttyS0,9600" to the grub CMDLINE and then set GRUB_TERMINAL="serial console" and "update_grub" and then run "systemctl enable serial-getty@ttyS0.service" you'll have to reboot but then you should get full output to the serial console from "connect host" on the CIMC. I'm going to keep trying to figure out how to get the console port working but I don't see any other ttyS interfaces getting configured in dmesg.
Last edited:
If you need to reset the CIMC password you can do the following:
Connect to the CIMC serial interface and boot up the system.
When it prompts, press *** press enter and run
Once it reaches the login go ahead and login as root and run the following:
Reboot the system and it will reset the credentials to default aka admin/password.
Connect to the CIMC serial interface and boot up the system.
When it prompts, press *** press enter and run
boot current recovery.Once it reaches the login go ahead and login as root and run the following:
mount /dev/cydisk0a3 /mnt/jffs2
mv /mnt/jffs2/avct_ems_cfg/etc/userdb /mnt/jffs2/avct_ems_cfg/etc/userdb_old
umount /dev/cydisk0a3Reboot the system and it will reset the credentials to default aka admin/password.
Last edited:
I'm keeping this one in the vault. I ended up finding another procedure that completely reset the CIMC (which was ok since I didn't know nor care what was in there anyway).
What procedure was used for that? I installed Proxmox on one of my servers and went to CIMC to see if I can iKVM or such and learned I couldn't log in.
Great work in here. Just out of curiosity, what's the draw with these? something like an HP t740 with a 10gb NIC would draw half the power, have twice the single thread CPU processing power, and have twice the bandwidth than all the 1g ports on this thing combined. Is it just the challenge? I can definitely understand that 