SOL with ipmitool

clockwork at sigsys.org clockwork at sigsys.org
Fri Jan 19 13:04:04 CST 2007


I've tried that. Where I run into issue is not with IPMI per se ... but
rather with the Dell/Linux/SOL aspect. I have getty spawned and AFAIK it
should work .... ipmitool is working for power and stats. SOL seems to
connect, and then I get nothing. Here is the -vv output:


<<RAKP 4 MESSAGE
<<  Message tag                   : 0x00
<<  RMCP+ status                  : no errors
<<  Console Session ID            : 0xa0a2a3a4
<<  Key exchange auth code [sha1] : 0xe0951c409a839e032e242f5c

IPMIv2 / RMCP+ SESSION OPENED SUCCESSFULLY


>> Sending IPMI command payload
>>    netfn   : 0x06
>>    command : 0x3b
>>    data    : 0x04

>> sending packet (64 bytes)
 06 00 ff 07 06 c0 00 65 00 02 03 00 00 00 20 00
 08 1b 73 74 aa 63 c7 d4 21 89 32 fa f0 6d e8 ad
 f3 ef eb d7 f8 3a ea f1 65 bc 7b 50 99 ae 90 4e
 ff ff 02 07 80 fc 75 1b 18 a5 d5 78 73 c3 51 51
<< Received data (64 bytes)
 06 00 ff 07 06 c0 a4 a3 a2 a0 01 00 00 00 20 00
 86 dd 74 08 2c 2f bc 5c ed 1b b3 47 6b 31 c8 5c
 5c 24 94 f3 52 e5 66 79 87 4b 89 97 d7 8c 93 00
 ff ff 02 07 9d 8b a0 b4 cb aa 24 d7 19 c2 e9 a3
Decrypted 16 encrypted bytesDecrypted this data (16 bytes)
 81 1c 63 20 04 3b 00 04 9d 01 02 03 04 05 06 06
Set Session Privilege Level to ADMINISTRATOR


>> Sending IPMI command payload
>>    netfn   : 0x06
>>    command : 0x48
>>    data    : 0x01 0x01 0xc6 0x00 0x00 0x00

>> sending packet (64 bytes)
 06 00 ff 07 06 c0 00 65 00 02 04 00 00 00 20 00
 b8 9e d9 44 30 00 33 8b ec 2c b9 a8 10 51 de bb
 85 83 92 cd 8e a2 6c b1 60 80 20 41 49 60 f0 dc
 ff ff 02 07 17 eb 19 f7 a5 cc be e6 5e b0 dc f1
<< Received data (80 bytes)
 06 00 ff 07 06 c0 a4 a3 a2 a0 02 00 00 00 30 00
 86 dd 74 08 2c 2f bc 5c ed 1b b3 47 6b 31 c8 5c
 4f 95 fd ca 1e 1b 58 7e dd 4a 15 6b 16 21 c2 ac
 de ad 9f 57 de 9d 29 0c 36 7d 0e 66 3e ce a4 66
 ff ff 02 07 1f 87 d3 7f 6c 50 98 e9 de 39 2c 81
Decrypted 32 encrypted bytesDecrypted this data (32 bytes)
 81 1c 63 20 08 48 00 00 00 00 00 32 00 ff 00 6f
 02 ff ff f0 01 02 03 04 05 06 07 08 09 0a 0b 0b
[SOL Session operational.  Use ~? for help]
>> SENDING A SOL MESSAGE

>> sending packet (64 bytes)
                             06 00 ff 07 06 c1 00 65 00 02 05 00 00 00 20 00

4e 2d 8f 13 3d 85
82 3c 75 77 a6 88 40 70 7a 72
                              23 fa 12 7f 0f e7 c7 da ee 3f 64 bc 29 76 ff
33

ff ff 02 07 af 2d
 73 b5 c5 67 02 fc b0 1a 31 88
                              << Received data (64 bytes)
                                                          06 00 ff 07 06 c1
a4 a3 a2 a0 03 00 0
0 00 20 00
           86 dd 74 08 2c 2f bc 5c ed 1b b3 47 6b 31 c8 5c
                                                           72 8a 34 ab 97 8b
11 c9 7f a9 21 d2
de b8 a8 5e
            ff ff 02 07 3b 26 91 a6 14 f9 1a e2 ce e2 74 65
                                                           Decrypted 16
encrypted bytesDecrypte
d this data (16 bytes)
                       00 01 01 00 01 02 03 04 05 06 07 08 09 0a 0b 0b
                                                                      SOL
sequence number     :
 0x00
SOL acked packet        : 0x01
SOL accepted char count : 0x01
SOL is nack             : false
SOL xfer unavailable    : false
SOL inactive            : false
SOL transmit overrun    : false
SOL break detected      : false
>> SENDING A SOL MESSAGE



This repeats a bit.  I can see the traffic on tcpdump, I just never get an
actual console.

On 1/17/07, Robin Humble <rjh+dellpe at cita.utoronto.ca> wrote:
>
> 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 10.4.3.74 -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.
>   http://www.mail-archive.com/ipmitool-devel@lists.sourceforge.net/
> 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 255.255.0.0
>   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.
>
> cheers,
> robin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20070119/2d6082ef/attachment-0001.htm 


More information about the Linux-PowerEdge mailing list