3 ms·
Not sure I agree with you 100% on your police work there, Lou. I worked with a good number of SuperMicro servers that - to my surprise - the IPMI interface was
by assttoasstmgr 5y ago
Not sure I agree with you 100% on your police work there, Lou.
I worked with a good number of SuperMicro servers that - to my surprise - the IPMI interface was by default set to "fail over to bridge to primary interface". That is to say if the IPMI port was disconnected, it would bridge onto your primary NIC with a second MAC address. The way to disable it was to download an obscure utility from SuperMicro's website, which only ran under Windows, and to pass an equally obscure hexadecimal command line flag.
Fortunately in my case, these ran on a network with no DHCP server, but I can't assume that's true in every case.
- throwawayboise 5y agoYes SuperMicro machines are configured that way. Some don't even have a dedicated separate IPMI interface.
- dnautics 5y agoYeah those supermicros scared the bejeezus out of me when I saw them in the catalog. I mean, yeah, you can configure the switch to listen onto different vlan ids, but what if something weird happens and that stateful information is lost or corrupted?
- IYasha 5y agoYeah, that's why I never put WAN on a shared interface. HP DOES THIS TOO. At least, they did. For example, on some g6 servers iLO/LO100 physical interface was optional (a small but costly add-on card) and, when not installed, iLO was shared with normal eth. If someone manages to hack a server enough to reset the shared iLO, at least it shouldn't immediately pop up into internet.
- GekkePrutser 5y agoiLO as the remote management tech from HP doesn't do that though, at least not on any of the servers I've seen. IPMI is a very different thing.
- jwiz 5y agoYou can use ipmiutil with smcoem commands nowadays.
- deleted 5y ago[deleted]