IPMI is Awesome. But, it is underused. Most sysadmins don’t even enable it. If they do enable it, they probably enable it by manually going into the BIOS, and then probably only using the Web interface. LAME.
There is no need to go to the BIOS to configure ipmi. You can use IPMItool to configure it in-band. This is my first underused command:
(disclaimer: not all IPMI interfaces / bios versions / hardware platforms are equal. Don’t complain in a comment that your hardware doesn’t support all of these cool things)
1. ipmitool lan set 1 ipsrc dhcp
(Set your ipmi interface to grab an IP via DHCP)
Do it. Script it. Make a puppet module. There is no reason not to have IPMI configured on every server that supports it. Except laziness. Don’t forget to set a password and enable at least one user. Seriously, this is probably the #1 under-utilized command, just configuring the darn thing.
2. ipmitool -H server-ipmi -U root -P root chassis power reset
(Remote reboot via IPMI)
Once you have IPMI configured, doing a remote reboot is the next cool thing. Seriously, never press the power button, bother a noc tech, telnet to an APC, again. Notice that you need -H, -U, -P, etc. as this command must be run over the lan interface to a remote server.
3. ipmitool -H server-ipmi -U root -p root chassis identify 1
(Blink the chassis LED)
Freak out a NOC tech by running this command on all your servers as soon as they replace a harddrive. Make a special Christmas youtube video with your server farm’s chassis LEDs.
4. ipmitool -H server-ipmi -U root -P root chassis bootparam set bootflag force_bios
(Make your server go directly into bios on next reboot)
Now we are getting fancy! We’ve all been there. Waiting for a slow-ass HP super server to boot, waiting and waiting for the signal to start frantically pounding the F2 key to enter the bios. Then missing it because the VGA didn’t show up in time. Reboot again. Repeat.
Fuck that noise. I don’t wait for servers. The servers wait for me! Also works for EFI shell, PXE, disk, etc.
Maybe someday I’ll combine this command with the next command (SOL) and generate bios setting macros, sending perfect sequences of keystrokes to set the BIOS like some sort of tool-assisted-server-configuring-speed-run (YES. THIS IS HOW WE SHOULD CONFIGURE SERVERS). Or if I’m lucky, just configure the bios from Linux itself.
5. ipmitool -H server01-ipmi -I lanplus -U root -P root sol activate
(Connect to the remote server’s serial console)
You know that fancy KVM over IP you have? The one that probably works like crap, needs to be rebooted all the time, lots of extra cables, special dongles, bla bla bla? You don’t need it man. All a server needs is power, and network.
SOL or serial-over-lan allows you to use the server’s serial console over ipmi. Configure the bios to do serial console redirection, configure your boot loader and OS to do the same, and you are set. Then load up a screen full of them and use the serial console like a boss. Special props for using the magic-sysrq over SOL.
6. ipmitool -H ipmihost -U root -P root delloem powermonitor
(Get server power measurements)
Yes. On some platforms you can actually measure how much power your server is using. Scrape that shit and pump it to graphite man! I’m trying to collect the different ways to do this, as there are different vendor specific implementations.
7. ipmitool -H ipmihost -U root -P root sensor list
(Retrieve low level hardware sensor output)
If you suspect you are having hardware issues, this can be super valuable. Combined with automatic sensor monitoring via nagios, and you are an IPMI pro.Comment via email