jgreco
Resident Grinch
- Joined
- May 29, 2011
- Messages
- 18,680
I think you need to sit back, drop all your preconceived notions, and start fresh. You're either not listening or not comprehending. Either is fine, one of them we can fix, and people here are generally happy to do so if you want.
The IPMI system is an almost entirely independent miniature embedded computer that lives on your system mainboard. It is something that is approximately like a low-end Raspberry Pi, in that it has a network port, can speak IP, and can do some nifty tricks.
Because typical desktop boards and gamer boards do not have this, they typically make some halfarse arrangement for the host CPU to be able to monitor and control things like fan speeds, power supply voltages, etc. , or, worse, they make you buy "fan controller" modules or crap like that.
By way of comparison, the IPMI subsystem is not closely tied to the system mainboard, despite living on the system mainboard. The host system does have a communications channel it can use to talk to the IPMI subsystem, which is how tools like "ipmitool" work on a local host. I previously suggested you try to use "ipmitool" locally to check out what the settings were, because this is generally effective at resetting IP's, passwords, etc., on the IPMI system.
The IPMI system also has a dedicated LAN port, which in some cases may instead optionally be configured to be a shared port with the host. This is somewhat harder to leverage, but I suggested configuring a PC or laptop on the network that is being shown to you in the static IP displayed in the BIOS. You haven't indicated what this is, and there are potentially some addresses which won't be usable if you do that.
The IPMI is basically a parasite on the main system and has its tendrils going into many things, and has direct access and control over things like the host console, the fans, power supply readings, ability to overwrite the BIOS, etc. It is very powerful for the various things it is able to do.
You can access the IPMI in various ways over the network, including using the dedicated IPMI protocol, or using the HTTP/HTTPS webserver. In order to do that, you need to be able to set up a PC or laptop on the same network as the IPMI, and then you should be able to connect to the IPMI controller.
However, it is entirely possible that the IPMI has some sort of broken static IP configuration, in which case you are best off loading a copy of TrueNAS, FreeBSD, or Linux on the server, and using the local ipmitool or ipmicfg tools to reset the BMC to default, or setting it via the host BIOS interface. That's described on page 2-3 of the manual:
We're all very familiar with the Supermicro IPMI systems here, everybody that has answered you so far is at least "expert hobbyist". I work with this stuff professionally and still actively manage racksful of X9 systems. So what you really need to do is to just put the brakes on and see if you can latch on and provide some detailed feedback. We can get you straightened out.
1) Try loading TrueNAS, or FreeBSD, or Linux, or Windows, or any convenient OS on the host system. Use that to install either impitool (a generic tool) or ipmicfg (Supermicro's tool). Some commands for ipmicfg are listed starting on page 2-4 of the manual above. Start simple and see if you can get the IPMI to regurgitate something simple like the network configuration. You can move on from there to actually setting variables. Expect to be frustrated numerous times, take small steps, and experiment only with the obvious stuff, but you should be able to both configure IP and clear any existing user password. Tell us which thing you end up using and we can probably give you more specific guidance.
<<<or>>>
2) Try connecting a PC or laptop to the IPMI port, configuring the PC/laptop to be on the same network that the IPMI alleges to be on. This implies you need to set a static IP address on the PC/laptop. Ping that address. If it does not ping, move the PC connection to each of the host ports and try again. I don't recall which one the IPMI system uses in shared mode offhand.
Report back with more details about what worked and what didn't.
The IPMI system is an almost entirely independent miniature embedded computer that lives on your system mainboard. It is something that is approximately like a low-end Raspberry Pi, in that it has a network port, can speak IP, and can do some nifty tricks.
Because typical desktop boards and gamer boards do not have this, they typically make some halfarse arrangement for the host CPU to be able to monitor and control things like fan speeds, power supply voltages, etc. , or, worse, they make you buy "fan controller" modules or crap like that.
By way of comparison, the IPMI subsystem is not closely tied to the system mainboard, despite living on the system mainboard. The host system does have a communications channel it can use to talk to the IPMI subsystem, which is how tools like "ipmitool" work on a local host. I previously suggested you try to use "ipmitool" locally to check out what the settings were, because this is generally effective at resetting IP's, passwords, etc., on the IPMI system.
The IPMI system also has a dedicated LAN port, which in some cases may instead optionally be configured to be a shared port with the host. This is somewhat harder to leverage, but I suggested configuring a PC or laptop on the network that is being shown to you in the static IP displayed in the BIOS. You haven't indicated what this is, and there are potentially some addresses which won't be usable if you do that.
The IPMI is basically a parasite on the main system and has its tendrils going into many things, and has direct access and control over things like the host console, the fans, power supply readings, ability to overwrite the BIOS, etc. It is very powerful for the various things it is able to do.
You can access the IPMI in various ways over the network, including using the dedicated IPMI protocol, or using the HTTP/HTTPS webserver. In order to do that, you need to be able to set up a PC or laptop on the same network as the IPMI, and then you should be able to connect to the IPMI controller.
However, it is entirely possible that the IPMI has some sort of broken static IP configuration, in which case you are best off loading a copy of TrueNAS, FreeBSD, or Linux on the server, and using the local ipmitool or ipmicfg tools to reset the BMC to default, or setting it via the host BIOS interface. That's described on page 2-3 of the manual:
We're all very familiar with the Supermicro IPMI systems here, everybody that has answered you so far is at least "expert hobbyist". I work with this stuff professionally and still actively manage racksful of X9 systems. So what you really need to do is to just put the brakes on and see if you can latch on and provide some detailed feedback. We can get you straightened out.
1) Try loading TrueNAS, or FreeBSD, or Linux, or Windows, or any convenient OS on the host system. Use that to install either impitool (a generic tool) or ipmicfg (Supermicro's tool). Some commands for ipmicfg are listed starting on page 2-4 of the manual above. Start simple and see if you can get the IPMI to regurgitate something simple like the network configuration. You can move on from there to actually setting variables. Expect to be frustrated numerous times, take small steps, and experiment only with the obvious stuff, but you should be able to both configure IP and clear any existing user password. Tell us which thing you end up using and we can probably give you more specific guidance.
<<<or>>>
2) Try connecting a PC or laptop to the IPMI port, configuring the PC/laptop to be on the same network that the IPMI alleges to be on. This implies you need to set a static IP address on the PC/laptop. Ping that address. If it does not ping, move the PC connection to each of the host ports and try again. I don't recall which one the IPMI system uses in shared mode offhand.
Report back with more details about what worked and what didn't.
