Installing IPMITOOLS on Debian or Centos 5

/
Tags: , ,

Introduction

Had a dodgy disk playing up in one of our production servers, thought that the quickest way to check it out would be to use the  servers’ Intelligent Platform Management Interface (IPMI) interface.  I am running Debian Etch server on a DELL 1850 with a Baseboard Management Controller (BMC) card.

Instructions

First install the lm_sensors package, (if it isnt installed you can always check using dpkg -l | grep ipmitools)

mojo:~#apt-get install ipmitool

You then need to create a charcter special file.

mojo:~#mknod -m 0600 /dev/ipmi0 c 254 0

If  all goes well you should have the correct modules loaded, often a reboot helps this. To check this issue the following commands:

mojo:~#depmod -A

mojo:~#lsmod | grep ipmi

Below is the correct output:

ipmi_devintf            8552  0
ipmi_si                33708  0
ipmi_msghandler        31520  2 ipmi_devintf,ipmi_si

Don’t worry if it’s not running you can always load the modules on the fly:

mojo:~#modprobe ipmi_si

mojo:~#modprobe ipmi_devintf

To give it a quick test, issue the following command:
mojo:~# ipmitool sdr
Temp | -54 degrees C | cr
Planar Temp | 27 degrees C | ok
CMOS Battery | 3.03 Volts | ok
VCORE | 0x01 | ok
PROC VTT | 0x01 | ok
1.5V PG | 0x01 | ok
1.8V PG | 0x01 | ok
Presence | 0x01 | ok
PROC Fan | 3075 RPM | ok
DIMM Fan | 3075 RPM | ok
PCI Fan | 1350 RPM | ok
Status | 0x80 | ok
VRM | 0x01 | ok
OS Watchdog | 0x00 | ok
SEL | Not Readable | ns
Intrusion | 0x00 | ok
Temp Interface | Not Readable | ns
ECC Corr Err | Not Readable | ns
ECC Uncorr Err | Not Readable | ns
I/O Channel Chk | Not Readable | ns
PCI Parity Err | 0xc0 | ok
PCI System Err | Not Readable | ns
SBE Log Disabled | Not Readable | ns
Logging Disabled | Not Readable | ns
Unknown | Not Readable | ns
PROC Protocol | Not Readable | ns
PROC Bus PERR | Not Readable | ns
PROC Init Err | Not Readable | ns
PROC Machine Chk | Not Readable | ns
Memory Spared | Not Readable | ns
Memory Mirrored | 0x01 | ok
Memory RAID | 0x01 | ok
Memory Added | 0x01 | ok
Memory Removed | 0x01 | ok
PCIE Fatal Err | Not Readable | ns
Chipset Err | Not Readable | ns
Err Reg Pointer | Not Readable | ns

Done like a dinner!

Note

I have a couple of CentOS 5 production servers and downloaded and installed the following RPM.

OpenIPMI-tools-2.0.6-6.el5.i386.rpm

# yum install OpenIPMI-tools
Loading "fastestmirror" plugin
Loading "priorities" plugin
Loading mirror speeds from cached hostfile
* ourdelta: cc.us.mirror.ourdelta.org
* rpmforge: fr2.rpmfind.net
* base: mirrors.easynews.com
* updates: mirror.fdcservers.net
* addons: mirrors.tummy.com
* extras: mirrors.tummy.com
0 packages excluded due to repository priority protections
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
--> Running transaction check
---> Package OpenIPMI-tools.i386 0:2.0.6-6.el5_2.2 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

=============================================================================
Package                 Arch       Version          Repository        Size
=============================================================================
Installing:
OpenIPMI-tools          i386       2.0.6-6.el5_2.2  updates           330 k

Transaction Summary
=============================================================================
Install      1 Package(s)
Update       0 Package(s)
Remove       0 Package(s)

Total download size: 330 k
Is this ok [y/N]: y
Downloading Packages:
(1/1): OpenIPMI-tools-2.0 100% |=========================| 330 kB    00:00
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Installing: OpenIPMI-tools               ######################### [1/1]

Installed: OpenIPMI-tools.i386 0:2.0.6-6.el5_2.2
Complete!
#

Now on one of our heavily patched servers it installed perfectly for the newly installed CENTOS 5 server I had to create the special character file and manually load the correct drivers. So always check that everything installed correctly and never assume the package installation always works.

Author:

Related Articles