Supermicro H12SSL-i, H12SSL-C, H12SSL-NT, H12SSL-CT boards - notes, experiences
- Thread starter lihp
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Should work. That ram is crucial based ECC RDimms, which is what the board calls for.
Hmmm. LE1 blinks then shut off, BMC comes online and heartbeat blinks.
When I try to start via ipmi it fails, post code FF.
On PSU power cycle the fans start up and processor gets warm, ipmi reads power is on but it doesn't post.
Thought it must be ram but now I have no idea.
Board is brand new and tested from supermicro (previous board was actually defective)
EDIT: Turns out the CPU was also defective (both board and CPU were defective!). New one works great.
When I try to start via ipmi it fails, post code FF.
On PSU power cycle the fans start up and processor gets warm, ipmi reads power is on but it doesn't post.
Thought it must be ram but now I have no idea.
Board is brand new and tested from supermicro (previous board was actually defective)
EDIT: Turns out the CPU was also defective (both board and CPU were defective!). New one works great.
Last edited:
Hello!
I bought a used MBD-H12SSL-CT-B off of ebay, and I cannot for the life of me figure out what is going on with the LAN ports. I have a Ubiquiti Enterprise 24 port PoE switch. OS is Ubuntu 22.04.4 .
IPMI connected, and works great. Obtains IP address correctly from my router.
The onboard LAN ports show a green link status, but never any activity lights. Ethtool <interface> shows the link speed, and shows it's active. However, it never obtains an IP address. sudo dhclient <interface> hangs, and does nothing.
In the BIOS - Network stack is enabled, each network interfaces DHCP setting is enabled too. Both LAN 1/2 MAC addresses appear in IPMI dashboard.
I've tried the following:
(1) Connecting to 3 different switches/ports - 10 gbe Ubiquiti, 1 gbe Netgear, 1 gbe Ubituiti.
(2) Flashing BIOS to latest version.
(3) Trying different cat 6 cables.
On the router side it shows a port occupied, but it does not obtain the MAC address from the on board LAN.
Am I missing something obvious? Or is this board's onboard LAN toast?
Thank you!
I bought a used MBD-H12SSL-CT-B off of ebay, and I cannot for the life of me figure out what is going on with the LAN ports. I have a Ubiquiti Enterprise 24 port PoE switch. OS is Ubuntu 22.04.4 .
IPMI connected, and works great. Obtains IP address correctly from my router.
The onboard LAN ports show a green link status, but never any activity lights. Ethtool <interface> shows the link speed, and shows it's active. However, it never obtains an IP address. sudo dhclient <interface> hangs, and does nothing.
In the BIOS - Network stack is enabled, each network interfaces DHCP setting is enabled too. Both LAN 1/2 MAC addresses appear in IPMI dashboard.
I've tried the following:
(1) Connecting to 3 different switches/ports - 10 gbe Ubiquiti, 1 gbe Netgear, 1 gbe Ubituiti.
(2) Flashing BIOS to latest version.
(3) Trying different cat 6 cables.
On the router side it shows a port occupied, but it does not obtain the MAC address from the on board LAN.
Am I missing something obvious? Or is this board's onboard LAN toast?
Thank you!
Thanks for the response - The jumper is on pins JPL1 1-2. Everything is enabled in the BIOS as far as I can tell.
Isn't the BIOS Network stack only for EFI boot and using network in EFI shell?
Also what happens when you assign a static IP address in whatever OS you are using (Linux/Windows) ? The LAN chipset is BCM57416, IIRC Ubuntu had problems with it but the later versions work fine
try lspci -vvv to check which driver is in use for the card. IIRC, Ubuntu needs the linux-modules-extra package for the bnxt kernel module
or then load windows to check if the OS is a problem
Both the intel 550 and the BCM 574xxx are quite sturdy but they are susceptible to heat. I’ve had my H12 and also my x550 chipset shut down because of cooling issues but they came back up after a reboot.
The LAN chipset on that motherboard definitely needs forced airflow. When I used Noctua fans in my 2U SM case, the LAN misbehaved often. Am wondering if the chipset on your board is somehow damaged
I propose to compare IPMI sensors with real H12SSL devices. During tests (such as mprime, for example), the following sensors have the greatest heating:
- SOC_VRM Temp
- VRMABCD Temp
- VRMEFGH Temp
Attachments
Last edited:
My H12 series failure rate is really high...
Another H12SSL-NT stopped working and will have to be RMAd. No sign of life (tested with a different PSU), not even BMC Heartbeat.
Another H12SSL-NT stopped working and will have to be RMAd. No sign of life (tested with a different PSU), not even BMC Heartbeat.
Thanks for the review... in my personal experience with the "be quiet! MC1 Pro, M.2 SSD-heatsink" and the H12SSL-i , I managed to get them pressed down under pressure but they did not fit even without the small screws on the sides that touch, and were not even recognised by the motherboard, personally would not be happy with having the 2 x M.2 ports under pressure due to the heatsinks, nor having the heatsink contact the pins near to the bios battery. I would recommend some heatsinks that sit on top of the drives only with nothing on the sides. Also bear in mind longer PCIE cards may not fit above the drives with heatsinks mounted.
Saw this asked a few times in the thread and a link to the official >Supermicro 55cm Slimline x8 to 2x U.2 PCIE with Power Cable (CBL-SAST-0953) cable and the Amazon option, but only in relation to attaching 1 x u.2. Did anyone ever manage to connect 2 x u.2 drives with the 8i SlimSAS port on the H12SSL-i?
Last edited:
of course. The port has 8 lanes and supports 2 drives just fine.
No. Auto lets the jumper located at the PCIe slot decide (NVMe or SATA)