supermicro BMC/IPMI becomes inaccessible after power is on and OS is up

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

lovefxspot

New Member
Jan 24, 2023
8
2
3
Hi guys, newbie to BMC/IPMI stuff here. So I got x13sae-f + 13900k. BMC is always accessible when power is off but once power is on and OS is up BMC becomes inaccessible...

anybody knows what's going on? sent supermicro support an email but so far has not heard anything
 

oneplane

Well-Known Member
Jul 23, 2021
844
484
63
What does accessible mean to you?

For some it means "access iKVM" for others "iSoL" and for more others "COM1" and for more different others "pings on the network" and even more more different others "ipmitool can talk to it".

Generally if it is network related, it means something is happening with port sharing.
 

RolloZ170

Well-Known Member
Apr 24, 2016
5,155
1,548
113
IPMI on x13sae-f is dedocated, no sharing.
how is the IPMI LAN configured ? DHCP, fixed IP ?
 

lovefxspot

New Member
Jan 24, 2023
8
2
3
What does accessible mean to you?

For some it means "access iKVM" for others "iSoL" and for more others "COM1" and for more different others "pings on the network" and even more more different others "ipmitool can talk to it".

Generally if it is network related, it means something is happening with port sharing.
BMC can't be accessed by web gui. Ping not working eithor
 

oneplane

Well-Known Member
Jul 23, 2021
844
484
63
If the BMC stops doing network things once the OS is loaded, it stands to reason that the OS is doing something. Luckily, the OS can talk to the BMC as well, so start there. Also make sure all your firmwares are up to date, it wouldn't be the first time that merely loading a KCS state machine crashes it until the next power off.
 

lovefxspot

New Member
Jan 24, 2023
8
2
3
If the BMC stops doing network things once the OS is loaded, it stands to reason that the OS is doing something. Luckily, the OS can talk to the BMC as well, so start there. Also make sure all your firmwares are up to date, it wouldn't be the first time that merely loading a KCS state machine crashes it until the next power off.
the problem is ubuntu can't find it...below is ipmitool output
ipmitool mc info
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory

also tried supermicro own IPMICFG but it needs IP as parameter and IP inaccessible

also insalled supermicro's graphic driver and still same...
 

VMman

Active Member
Jun 26, 2013
125
45
28
the problem is ubuntu can't find it...below is ipmitool output
ipmitool mc info
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory

also tried supermicro own IPMICFG but it needs IP as parameter and IP inaccessible

also insalled supermicro's graphic driver and still same...
Have you tried to retrieve the IP using the IPMICFG -m ?

I have no exp with X13 but on the older boards you had to sometimes use an older version of IPMICFG to work.
You could also run a factory reset with network and then set the static IP using IPMICFG.
 

oneplane

Well-Known Member
Jul 23, 2021
844
484
63
Keep in mind that a driver issue might simply an age thing. Lots of the AST white label firmware packages only work on old kernels. CentOS == old kernel, and Ubuntu tends to be quite far ahead. Then again, without more details we're just guessing. Even just a dmesg log would help.