<<O>>  Difference Topic IPMI (r1.1 - 14 Jul 2008 - MarcosASeco)
Line: 1 to 1
META TOPICPARENT ConfigurationSteps

-- MarcosASeco - 14 Jul 2008

SOL with ipmitool
Robin Humble rjh+dellpe at cita.utoronto.ca
Wed Jan 17 01:17:59 CST 2007

On Tue, Jan 09, 2007 at 05:24:31PM -0500, clockwork at sigsys.org wrote:
> in general. When I connect to the 2950 I am using as a testbed I get nothing
> on the sol session. I can control the system's power and get sensor data,
> sol info and so on. So I run ipmitool like so:
> ipmitool -I lanplus -H -U username sol activate

what does adding -v tell you?
-vv is probably too verbose. there's also an ipmi list you can ask. eg.
ah, I see you have already asked there...

unfortunately errors from ipmitool are generally crap, but googling or looking at the ipmitool src might tell you what's failing.

SOL via ipmitool on 1950 is definitely possible, as we have it working on a 1950 and a pile of fairly similar SGI xe210's (Intel 5000P chipset) here.

I only have access/experience with the SGI's though - let me know if the below doesn't help and I'll try to find out more about the 1950's setup.

a (not yet fully debugged) ipmi setup from scratch on the SGI looks something like:

load up the IPMI 'open' kernel modules
   /etc/init.d/ipmi start

setup IP and access:
   ipmitool channel info 1
   ipmitool lan set 1 ipaddr <someIP>
   ipmitool lan set 1 netmask
   ipmitool lan set 1 auth ADMIN MD5,PASSWORD
   ipmitool lan set 1 ipsrc static
   ipmitool lan set 1 arp respond on
   ipmitool lan set 1 arp generate on
   ipmitool lan set 1 arp interval 5
   ipmitool lan print 1
   ipmitool lan set 1 access on

and then setup a user called 'admin'
   ipmitool user set name 2 admin
   ipmitool user set password 2 <some passwd>
   #ipmitool user priv 2 4 1
   ipmitool channel setaccess 1 2 callin=on ipmi=on link=on privilege=4
   ipmitool user list 1
   ipmitool user enable 2

and the sol setup continues over the lanplus interface:
   ipmitool -I lanplus -H <someIP> -U admin -P <some passwd> -v -o intelplus sol info
   ipmitool -I lanplus -H <someIP> -U admin -P <some passwd> -v -o intelplus sol set privilege-level admin
   ipmitool -I lanplus -H <someIP> -U admin -P <some passwd> -v -o intelplus sol set non-volatile-bit-rate 115.2
   ipmitool -I lanplus -H <someIP> -U admin -P <some passwd> -v -o intelplus sol set volatile-bit-rate serial
   ipmitool -I lanplus -H <someIP> -U admin -P <some passwd> -v -o intelplus sol set force-encryption true
   ipmitool -I lanplus -H <someIP> -U admin -P <some passwd> -v -o intelplus sol set enabled true
   ipmitool -I lanplus -H <someIP> -U admin -P <some passwd> -v -o intelplus sol set retry-interval 2
   ipmitool -I lanplus -H <someIP> -U admin -P <some passwd> -v -o intelplus sol payload enable 1 2

for the Dell you'd drop the '-o intelplus' but the rest should still apply. channel numbers might vary (the above is 1), and the SGI BIOS talks to ttyS1 instead of ttyS0.

but there's something wrong with the above setup as someone with the wrong passwd can currently power cycle the machine(!) sigh

> Which produces nothing. It connects okay, and I can pull info from the bmc,
> and power control works. I have the entry in inittab that I believe I need
> (RHEL 4.x based distro inittab entry: s0:2345:respawn:/sbin/agetty ttyS0
> 115200,9600 linux) and I believe I have all the BIOS options setup. If

I think this is most likely for the Dell:
   /sbin/agetty -L 57600 ttyS0
and maybe a vt000 on the end. Dells don't seem to like the -h for hardware flow control to over serial.


Revision -
Revision r1.1 - 14 Jul 2008 - 16:52 - MarcosASeco