Discussion:
[Ipmitool-devel] Serial-over-LAN on SuperMicro IMPI 2.0 BMC Card
Jared Smith
2005-04-07 16:37:05 UTC
Permalink
Whew! That subject is a mouthful, isn't it. Has anyone had any success
getting SOL working on a SuperMicro BMC card? The one I'm using is IMPI
2.0 compliant, but when I connect using "lanplus" I get the following:

[***@box ~]# ipmitool -I lanplus -H 10.10.40.12 -U ADMIN -P ADMIN sol
activate
Error: Unable to establish IPMI v2 / RMCP+ session
Error: No response activating SOL payload

Here's what I get for the BMC info using the "lan" (IMPI 1.5) interface:

[***@jsmith ~]# ipmitool -I lan -H 10.10.40.12 -U ADMIN -P ADMIN bmc
info
Device ID : 32
Device Revision : 0
Firmware Revision : 14.40
IPMI Version : 2.0
Manufacturer ID : 2168
Product ID : 0 (0x0000)
Device Available : yes
Provides Device SDRs : no
Additional Device Support :
Sensor Device
SDR Repository Device
SEL Device
FRU Inventory Device
IPMB Event Receiver
IPMB Event Generator
Bridge
Aux Firmware Rev Info :
0x00
0x00
0x00
0x00

Any ideas or help would be greatly appreciated. If you want me to, I
can provide traffic dumps from the Java client.

-Jared
Albert Chu
2005-04-07 16:45:30 UTC
Permalink
Hi Jared,

The Supermicro IPMI 2.0 BMC cards don't support IPMI 2.0 as of the
firmware revisions from earlier this year. The SOL on their Java Client
uses their IPMI 1.5 proprietary protocol.

I'm not sure if Supermicro has released a new firmware update or not to
support IPMI 2.0.

Al

--
Albert Chu
***@llnl.gov
Lawrence Livermore National Laboratory

----- Original Message -----
From: Jared Smith <***@jaredsmith.net>
Date: Thursday, April 7, 2005 9:37 am
Subject: [Ipmitool-devel] Serial-over-LAN on SuperMicro IMPI 2.0 BMC Card
Post by Jared Smith
Whew! That subject is a mouthful, isn't it. Has anyone had any
successgetting SOL working on a SuperMicro BMC card? The one I'm
using is IMPI
activate
Error: Unable to establish IPMI v2 / RMCP+ session
Error: No response activating SOL payload
Here's what I get for the BMC info using the "lan" (IMPI 1.5)
info
Device ID : 32
Device Revision : 0
Firmware Revision : 14.40
IPMI Version : 2.0
Manufacturer ID : 2168
Product ID : 0 (0x0000)
Device Available : yes
Provides Device SDRs : no
Sensor Device
SDR Repository Device
SEL Device
FRU Inventory Device
IPMB Event Receiver
IPMB Event Generator
Bridge
0x00
0x00
0x00
0x00
Any ideas or help would be greatly appreciated. If you want me to, I
can provide traffic dumps from the Java client.
-Jared
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real
users.Discover which products truly live up to the hype. Start
reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Jakob Sandgren
2005-04-07 19:48:09 UTC
Permalink
Hi,

No, the IPMI 2.0 card does still not support IPMI 2.0(!), unless
something has changed the last few days.

However they do have a command line tool that works in Linux with
their proprietary protocol. However, the version on the CD (and their
website) is very buggy, we have just worked with them and has recevied
fixes for their bios and client that makes it work pretty well.

Best Regards,
Jakob Sandgren
South Pole AB
Post by Albert Chu
Hi Jared,
The Supermicro IPMI 2.0 BMC cards don't support IPMI 2.0 as of the
firmware revisions from earlier this year. The SOL on their Java Client
uses their IPMI 1.5 proprietary protocol.
I'm not sure if Supermicro has released a new firmware update or not to
support IPMI 2.0.
Al
--
Albert Chu
Lawrence Livermore National Laboratory
----- Original Message -----
Date: Thursday, April 7, 2005 9:37 am
Subject: [Ipmitool-devel] Serial-over-LAN on SuperMicro IMPI 2.0 BMC Card
Post by Jared Smith
Whew! That subject is a mouthful, isn't it. Has anyone had any
successgetting SOL working on a SuperMicro BMC card? The one I'm
using is IMPI
activate
Error: Unable to establish IPMI v2 / RMCP+ session
Error: No response activating SOL payload
Here's what I get for the BMC info using the "lan" (IMPI 1.5)
info
Device ID : 32
Device Revision : 0
Firmware Revision : 14.40
IPMI Version : 2.0
Manufacturer ID : 2168
Product ID : 0 (0x0000)
Device Available : yes
Provides Device SDRs : no
Sensor Device
SDR Repository Device
SEL Device
FRU Inventory Device
IPMB Event Receiver
IPMB Event Generator
Bridge
0x00
0x00
0x00
0x00
Any ideas or help would be greatly appreciated. If you want me to, I
can provide traffic dumps from the Java client.
-Jared
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real
users.Discover which products truly live up to the hype. Start
reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
--
Jakob Sandgren South Pole AB
Phone: +46 8 51420420 Gelbjutarvägen 5
Fax: +46 8 51420429 SE - 17148 Solna
e-mail: ***@southpole.se www.southpole.se
Jared Smith
2005-04-07 16:51:49 UTC
Permalink
Post by Albert Chu
The Supermicro IPMI 2.0 BMC cards don't support IPMI 2.0 as of the
firmware revisions from earlier this year. The SOL on their Java Client
uses their IPMI 1.5 proprietary protocol.
That's good to know.
Post by Albert Chu
I'm not sure if Supermicro has released a new firmware update or not to
support IPMI 2.0.
I'll check it out, and see what I can find. In the meantime, is there
any hope of any linux client talking their proprietary 1.5 protocol? (I
know, I'm probably asking the impossible here -- but I have to ask.)

-Jared
H***@fujitsu-siemens.com
2005-04-08 09:08:29 UTC
Permalink
Jared,
could you please provide a v2 trace from the RMCP+ open session (e.g.
add -vv to your commandline).

This will at least answer the question, if they support any IPMI 2.0
features (independend from SOL). Also, you could try the -o intelplus
option.

Netmon or ethereal sniffs would be helpful as well.

Best Regards

Holger Liebig
ADMIN sol activate
Error: Unable to establish IPMI v2 / RMCP+ session
Error: No response activating SOL payload
Here's what I get for the BMC info using the "lan" (IMPI 1.5)
ADMIN bmc info
Device ID : 32
Device Revision : 0
Firmware Revision : 14.40
IPMI Version : 2.0
Manufacturer ID : 2168
Product ID : 0 (0x0000)
Device Available : yes
Provides Device SDRs : no
Sensor Device
SDR Repository Device
SEL Device
FRU Inventory Device
IPMB Event Receiver
IPMB Event Generator
Bridge
0x00
0x00
0x00
0x00
Any ideas or help would be greatly appreciated. If you want
me to, I can provide traffic dumps from the Java client.
-Jared
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide Read honest &
candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Jared Smith
2005-04-08 17:47:51 UTC
Permalink
Post by H***@fujitsu-siemens.com
could you please provide a v2 trace from the RMCP+ open session (e.g.
add -vv to your commandline).
Here's what happens when I try to connect with the lanplus interface

[***@jsmith ~]$ ipmitool -I lanplus -H 10.10.40.12 -U ADMIN -P ADMIN
-vv sol activate
IPMI LAN host 10.10.40.12 port 623
Post by H***@fujitsu-siemens.com
Sending IPMI command payload
netfn : 0x06
command : 0x38
data : 0x8e 0x04
sending packet (23 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 09 20 18
c8 81 00 38 8e 04 b5
<< Received data (22 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 08 81 1c
63 20 00 38 cc dc
Post by H***@fujitsu-siemens.com
Sending IPMI command payload
netfn : 0x06
command : 0x38
data : 0x0e 0x04
sending packet (23 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 09 20 18
c8 81 00 38 0e 04 35
<< Received data (30 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 10 81 1c
63 20 00 38 00 01 06 04 02 00 00 00 00 9b
This BMC does not support IPMI v2 / RMCP+
Error: Unable to establish IPMI v2 / RMCP+ session
Error: No response activating SOL payload


Here's the same thing, only with the "-o intelplus" option:

[***@jsmith ~]$ ipmitool -I lanplus -H 10.10.40.12 -U ADMIN -P ADMIN
-vv -o intelplus sol activate
IPMI LAN host 10.10.40.12 port 623
Post by H***@fujitsu-siemens.com
Sending IPMI command payload
netfn : 0x06
command : 0x38
data : 0x8e 0x04
sending packet (23 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 09 20 18
c8 81 00 38 8e 04 b5
<< Received data (22 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 08 81 1c
63 20 00 38 cc dc
Post by H***@fujitsu-siemens.com
Sending IPMI command payload
netfn : 0x06
command : 0x38
data : 0x0e 0x04
sending packet (23 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 09 20 18
c8 81 00 38 0e 04 35
<< Received data (30 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 10 81 1c
63 20 00 38 00 01 06 04 02 00 00 00 00 9b
This BMC does not support IPMI v2 / RMCP+
Error: Unable to establish IPMI v2 / RMCP+ session
Error: No response activating SOL payload

Here's the v1.5 bmc info with -vv:

[***@jsmith ~]$ ipmitool -I lan -H 10.10.40.12 -U ADMIN -P ADMIN -vv bmc info IPMI LAN host 10.10.40.12 port 623
Sending IPMI/RMCP presence ping packet
Received IPMI/RMCP response packet:
IPMI Supported
ASF Version 1.0
RMCP Version 1.0
RMCP Sequence 255
IANA Enterprise 4542

Channel 01 Authentication Capabilities:
Privilege Level : ADMINISTRATOR
Auth Types : MD2 MD5
Per-msg auth : enabled
User level auth : enabled
Non-null users : enabled
Null users : disabled
Anonymous login : disabled

Proceeding with AuthType MD5
Opening Session
Session ID : 02006c00
Challenge : 1a2e9b6b879b08dfed016e56102384c4
Privilege Level : ADMINISTRATOR
Auth Type : MD5

Session Activated
Auth Type : MD5
Max Priv Level : ADMINISTRATOR
Session ID : 02006d00
Inbound Seq : 00000001

Set Session Privilege Level to ADMINISTRATOR

Device ID : 32
Device Revision : 0
Firmware Revision : 14.40
IPMI Version : 2.0
Manufacturer ID : 2168
Product ID : 0 (0x0000)
Device Available : yes
Provides Device SDRs : no
Additional Device Support :
Sensor Device
SDR Repository Device
SEL Device
FRU Inventory Device
IPMB Event Receiver
IPMB Event Generator
Bridge
Aux Firmware Rev Info :
0x00
0x00
0x00
0x00
Closed Session 02006d00

-Jared
Oscar Gueta
2005-04-08 17:32:29 UTC
Permalink
Hello,

Same problem here... Ethereal shows malformed
packets sent by ipmitool and from BMC as well. I am
using a Harwich (intel) system. Three retries sent by
impitool but not respond to RAKP 1 (according to
ethereal message response is also malformed ).

[***@localhost ipmitool-1.6.0]# ipmitool -I lanplus
-H myhost -P password bmc info -vv
IPMI LAN host myhost port 623
Sending IPMI command payload
netfn : 0x06
command : 0x38
data : 0x8e 0x04
BUILDING A v1.5 COMMAND
sending packet (23 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 09 20 18
c8 81 00 38 8e 04 b5
<< Received data (30 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 10 81 1c
63 20 00 38 00 01 84 0e 03 00 00 00 00 12
SENDING AN OPEN SESSION REQUEST
sending packet (48 bytes)
06 00 ff 07 06 10 00 00 00 00 00 00 00 00 20 00
00 00 00 00 a4 a3 a2 a0 00 00 00 08 01 00 00 00
01 00 00 08 01 00 00 00 02 00 00 08 01 00 00 00
<< Received data (52 bytes)
06 00 ff 07 06 11 00 00 00 00 00 00 00 00 24 00
00 00 00 00 a4 a3 a2 a0 30 6a d2 00 00 00 00 08
01 00 00 00 01 00 00 08 01 00 00 00 02 00 00 08
01 00 00 00
<< OPEN SESSION RESPONSE
<< Message tag : 0x00
<< RMCP+ status : no errors
<< Maximum privilege level : Unknown
(0x00)
<< Console Session ID : 0xa0a2a3a4
<< BMC Session ID : 0x00d26a30
<< Negotiated authenticatin algorithm : hmac_sha1
<< Negotiated integrity algorithm : hmac_sha1_96
<< Negotiated encryption algorithm : aes_cbc_128
Console generated random number (16 bytes)
70 71 72 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f
SENDING A RAKP 1 MESSAGE
sending packet (59 bytes)
06 00 ff 07 06 12 30 6a d2 00 01 00 00 00 2b 00
00 00 00 00 30 6a d2 00 70 71 72 73 74 75 76 77
78 79 7a 7b 7c 7d 7e 7f 14 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00
sending packet (59 bytes)
06 00 ff 07 06 12 30 6a d2 00 01 00 00 00 2b 00
00 00 00 00 30 6a d2 00 70 71 72 73 74 75 76 77
78 79 7a 7b 7c 7d 7e 7f 14 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00
sending packet (59 bytes)
06 00 ff 07 06 12 30 6a d2 00 01 00 00 00 2b 00
00 00 00 00 30 6a d2 00 70 71 72 73 74 75 76 77
78 79 7a 7b 7c 7d 7e 7f 14 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00
sending packet (59 bytes)
06 00 ff 07 06 12 30 6a d2 00 01 00 00 00 2b 00
00 00 00 00 30 6a d2 00 70 71 72 73 74 75 76 77
78 79 7a 7b 7c 7d 7e 7f 14 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00
Error: no response from RAKP 1 message
Error: Unable to establish IPMI v2 / RMCP+ session
Error in BMC Get Device ID Command
Jared,
could you please provide a v2 trace from the RMCP+
open session (e.g.
add -vv to your commandline).
This will at least answer the question, if they
support any IPMI 2.0
features (independend from SOL). Also, you could try
the -o intelplus
option.
Netmon or ethereal sniffs would be helpful as well.
Best Regards
Holger Liebig
-U ADMIN -P
ADMIN sol activate
Error: Unable to establish IPMI v2 / RMCP+ session
Error: No response activating SOL payload
Here's what I get for the BMC info using the "lan"
(IMPI 1.5)
ADMIN -P
ADMIN bmc info
Device ID : 32
Device Revision : 0
Firmware Revision : 14.40
IPMI Version : 2.0
Manufacturer ID : 2168
Product ID : 0 (0x0000)
Device Available : yes
Provides Device SDRs : no
Sensor Device
SDR Repository Device
SEL Device
FRU Inventory Device
IPMB Event Receiver
IPMB Event Generator
Bridge
0x00
0x00
0x00
0x00
Any ideas or help would be greatly appreciated.
If you want
me to, I can provide traffic dumps from the Java
client.
-Jared
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest &
candid reviews on hundreds of IT Products from
real users.
Discover which products truly live up to the hype.
Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT
Products from real users.
Discover which products truly live up to the hype.
Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
__________________________________
Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun.
http://www.advision.webevents.yahoo.com/emoticontest
Duncan Laurie
2005-04-08 17:46:13 UTC
Permalink
Post by Oscar Gueta
Hello,
Same problem here... Ethereal shows malformed
packets sent by ipmitool and from BMC as well. I am
using a Harwich (intel) system. Three retries sent by
impitool but not respond to RAKP 1 (according to
ethereal message response is also malformed ).
I have not yet updated the ethereal packet dissectors to understand
IPMIv2 packet format so they will likely mess up on the new packet
types.

Can you try the 1.8.1 release from sourceforge together with the
"-o intelplus" command line option? There have been a number of IPMIv2
related changes between 1.6.0 and 1.8.1...

-duncan
Oscar Gueta
2005-04-08 20:25:53 UTC
Permalink
Hello,

This is the outup I get with impitool 1.8.1 . I
apologize for my ignorance, but, do I have to set an
AES key into BMC and also pass it also to impitool?
Seems my system does actually support IMPI 2.0.

[***@localhost root]# ipmitool -I lanplus -H myhost
-P passwd bmc info -vv
IPMI LAN host myhost port 623
Sending IPMI command payload
netfn : 0x06
command : 0x38
data : 0x8e 0x04
sending packet (23 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 09 20 18
c8 81 00 38 8e 04 b5
<< Received data (30 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 10 81 1c
63 20 00 38 00 01 84 0e 03 00 00 00 00 12
SENDING AN OPEN SESSION REQUEST
sending packet (48 bytes)
06 00 ff 07 06 10 00 00 00 00 00 00 00 00 20 00
00 00 00 00 a4 a3 a2 a0 00 00 00 08 01 00 00 00
01 00 00 08 01 00 00 00 02 00 00 08 01 00 00 00
<< Received data (52 bytes)
06 00 ff 07 06 11 00 00 00 00 00 00 00 00 24 00
00 00 00 00 a4 a3 a2 a0 04 48 14 0a 00 00 00 08
01 00 00 00 01 00 00 08 01 00 00 00 02 00 00 08
01 00 00 00
<<OPEN SESSION RESPONSE
<< Message tag : 0x00
<< RMCP+ status : no errors
<< Maximum privilege level : Unknown
(0x00)
<< Console Session ID : 0xa0a2a3a4
<< BMC Session ID : 0x0a144804
<< Negotiated authenticatin algorithm : hmac_sha1
<< Negotiated integrity algorithm : hmac_sha1_96
<< Negotiated encryption algorithm : aes_cbc_128
Console generated random number (16 bytes)
d1 cd 84 fa bf 25 51 59 4b 09 f5 a9 11 a3 52 86
SENDING A RAKP 1 MESSAGE
sending packet (44 bytes)
06 00 ff 07 06 12 00 00 00 00 00 00 00 00 1c 00
00 00 00 00 04 48 14 0a d1 cd 84 fa bf 25 51 59
4b 09 f5 a9 11 a3 52 86 14 00 00 00
<< Received data (76 bytes)
06 00 ff 07 06 13 00 00 00 00 00 00 00 00 3c 00
00 00 00 00 a4 a3 a2 a0 79 5e 85 a9 4f 8f 43 71
66 3b c1 45 08 7b ce 5a ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff fe db e4 25 72 d3 75 33
02 fa 0b 05 df 5c c2 60 a4 a5 ac 72
<<RAKP 2 MESSAGE
<< Message tag : 0x00
<< RMCP+ status : no errors
<< Console Session ID : 0xa0a2a3a4
<< BMC random number :
0x795e85a94f8f4371663bc145087bce5a
<< BMC GUID :
0xffffffffffffffffffffffffffffffff
<< Key exchange auth code [sha1] :
0xfedbe42572d3753302fa0b05df5cc260a4a5ac72

bmc_rand (16 bytes)
79 5e 85 a9 4f 8f 43 71 66 3b c1 45 08 7b ce 5a
session integrity key input (34 bytes)
d1 cd 84 fa bf 25 51 59 4b 09 f5 a9 11 a3 52 86
79 5e 85 a9 4f 8f 43 71 66 3b c1 45 08 7b ce 5a
14 00
Generated session integrity key (20 bytes)
5e 4c bd ca f8 a1 97 54 ca ce 51 17 d2 9d 36 59
5c 6a 62 4e
Generated K1 (20 bytes)
e7 1a 13 fd 4c f1 6a 4c 2d a2 99 67 4d 0a 4c 80
9f 42 3f 4c
Generated K2 (20 bytes)
58 4f fd b2 e4 58 5b 34 fb 8e a5 44 ca 97 ee fa
e9 10 37 e5
SENDING A RAKP 3 MESSAGE
sending packet (44 bytes)
06 00 ff 07 06 14 00 00 00 00 00 00 00 00 1c 00
00 00 00 00 04 48 14 0a 6e f2 57 13 cc 38 df ef
d3 c8 eb 41 1b 0a 99 2c b1 b6 27 f1
<< Received data (24 bytes)
06 00 ff 07 06 15 00 00 00 00 00 00 00 00 08 00
00 0f 00 00 a4 a3 a2 a0
<<RAKP 4 MESSAGE
<< Message tag : 0x00
<< RMCP+ status : invalid integrity
check value
<< Console Session ID : 0xa0a2a3a4
<< Key exchange auth code [sha1] :
0x005e85a94f8f4371663bc145

RAKP 4 message indicates an error : invalid integrity
check value
Error: Unable to establish IPMI v2 / RMCP+ session
Get Device ID command failed


Thanks
/Oscar
On Fri, 2005-04-08 at 11:08 +0200,
could you please provide a v2 trace from the RMCP+
open session (e.g.
add -vv to your commandline).
Here's what happens when I try to connect with the
lanplus interface
10.10.40.12 -U ADMIN -P ADMIN
-vv sol activate
IPMI LAN host 10.10.40.12 port 623
Sending IPMI command payload
netfn : 0x06
command : 0x38
data : 0x8e 0x04
sending packet (23 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 09 20 18
c8 81 00 38 8e 04 b5
<< Received data (22 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 08 81 1c
63 20 00 38 cc dc
Sending IPMI command payload
netfn : 0x06
command : 0x38
data : 0x0e 0x04
sending packet (23 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 09 20 18
c8 81 00 38 0e 04 35
<< Received data (30 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 10 81 1c
63 20 00 38 00 01 06 04 02 00 00 00 00 9b
This BMC does not support IPMI v2 / RMCP+
Error: Unable to establish IPMI v2 / RMCP+ session
Error: No response activating SOL payload
Here's the same thing, only with the "-o intelplus"
10.10.40.12 -U ADMIN -P ADMIN
-vv -o intelplus sol activate
IPMI LAN host 10.10.40.12 port 623
Sending IPMI command payload
netfn : 0x06
command : 0x38
data : 0x8e 0x04
sending packet (23 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 09 20 18
c8 81 00 38 8e 04 b5
<< Received data (22 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 08 81 1c
63 20 00 38 cc dc
Sending IPMI command payload
netfn : 0x06
command : 0x38
data : 0x0e 0x04
sending packet (23 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 09 20 18
c8 81 00 38 0e 04 35
<< Received data (30 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 10 81 1c
63 20 00 38 00 01 06 04 02 00 00 00 00 9b
This BMC does not support IPMI v2 / RMCP+
Error: Unable to establish IPMI v2 / RMCP+ session
Error: No response activating SOL payload
-U ADMIN -P ADMIN -vv bmc info IPMI LAN host
10.10.40.12 port 623
Sending IPMI/RMCP presence ping packet
IPMI Supported
ASF Version 1.0
RMCP Version 1.0
RMCP Sequence 255
IANA Enterprise 4542
Privilege Level : ADMINISTRATOR
Auth Types : MD2 MD5
Per-msg auth : enabled
User level auth : enabled
Non-null users : enabled
Null users : disabled
Anonymous login : disabled
Proceeding with AuthType MD5
Opening Session
Session ID : 02006c00
Challenge : 1a2e9b6b879b08dfed016e56102384c4
Privilege Level : ADMINISTRATOR
Auth Type : MD5
Session Activated
Auth Type : MD5
Max Priv Level : ADMINISTRATOR
Session ID : 02006d00
Inbound Seq : 00000001
Set Session Privilege Level to ADMINISTRATOR
Device ID : 32
Device Revision : 0
Firmware Revision : 14.40
IPMI Version : 2.0
Manufacturer ID : 2168
Product ID : 0 (0x0000)
Device Available : yes
Provides Device SDRs : no
Sensor Device
SDR Repository Device
SEL Device
FRU Inventory Device
IPMB Event Receiver
IPMB Event Generator
Bridge
0x00
0x00
0x00
0x00
Closed Session 02006d00
-Jared
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT
Products from real users.
Discover which products truly live up to the hype.
Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
__________________________________
Do you Yahoo!?
Yahoo! Personals - Better first dates. More second dates.
http://personals.yahoo.com
H***@fujitsu-siemens.com
2005-04-11 06:13:42 UTC
Permalink
RAKP 4 message indicates an error : invalid integrity check value
Error: Unable to establish IPMI v2 / RMCP+ session Get Device
ID command failed
The -o intelplus option was introduced to handle the Intel BMC
specifics. IPMItool with RMCP+ should work fine with the Harwich System.

But SOL will need some more investigations and some extra setup.

Holger
Oscar Gueta
2005-04-11 15:40:58 UTC
Permalink
Hello,

It doesn't work, even using "-o intelplus".

[***@localhost root]# ipmitool -I lanplus -H
10.5.99.135 -P patula chassis status -vv -o intelplus
IPMI LAN host 10.5.99.135 port 623
Sending IPMI command payload
netfn : 0x06
command : 0x38
data : 0x8e 0x04
sending packet (23 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 09 20 18
c8 81 00 38 8e 04 b5
<< Received data (30 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 10 81 1c
63 20 00 38 00 01 84 0e 03 00 00 00 00 12
SENDING AN OPEN SESSION REQUEST
sending packet (48 bytes)
06 00 ff 07 06 10 00 00 00 00 00 00 00 00 20 00
00 00 00 00 a4 a3 a2 a0 00 00 00 08 01 00 00 00
01 00 00 08 01 00 00 00 02 00 00 08 01 00 00 00
<< Received data (52 bytes)
06 00 ff 07 06 11 00 00 00 00 00 00 00 00 24 00
00 00 00 00 a4 a3 a2 a0 fc ec 8f 01 00 00 00 08
01 00 00 00 01 00 00 08 01 00 00 00 02 00 00 08
01 00 00 00
<<OPEN SESSION RESPONSE
<< Message tag : 0x00
<< RMCP+ status : no errors
<< Maximum privilege level : Unknown
(0x00)
<< Console Session ID : 0xa0a2a3a4
<< BMC Session ID : 0x018fecfc
<< Negotiated authenticatin algorithm : hmac_sha1
<< Negotiated integrity algorithm : hmac_sha1_96
<< Negotiated encryption algorithm : aes_cbc_128
Console generated random number (16 bytes)
8d 0e d3 dc c8 b2 25 6e 58 25 00 8a 75 13 80 f5
SENDING A RAKP 1 MESSAGE
sending packet (44 bytes)
06 00 ff 07 06 12 00 00 00 00 00 00 00 00 1c 00
00 00 00 00 fc ec 8f 01 8d 0e d3 dc c8 b2 25 6e
58 25 00 8a 75 13 80 f5 14 00 00 00
<< Received data (76 bytes)
06 00 ff 07 06 13 00 00 00 00 00 00 00 00 3c 00
00 00 00 00 a4 a3 a2 a0 f6 fc aa 8f ab f4 84 c1
22 39 16 d9 7f 73 23 92 ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff a8 b4 ba 80 aa 2c df c9
96 c0 90 cc 36 8b 40 5b 31 c9 a6 62
<<RAKP 2 MESSAGE
<< Message tag : 0x00
<< RMCP+ status : no errors
<< Console Session ID : 0xa0a2a3a4
<< BMC random number :
0xf6fcaa8fabf484c1223916d97f732392
<< BMC GUID :
0xffffffffffffffffffffffffffffffff
<< Key exchange auth code [sha1] :
0xa8b4ba80aa2cdfc996c090cc368b405b31c9a662

bmc_rand (16 bytes)
f6 fc aa 8f ab f4 84 c1 22 39 16 d9 7f 73 23 92
session integrity key input (34 bytes)
8d 0e d3 dc c8 b2 25 6e 58 25 00 8a 75 13 80 f5
f6 fc aa 8f ab f4 84 c1 22 39 16 d9 7f 73 23 92
14 00
Generated session integrity key (20 bytes)
fe d1 c3 53 0b 00 bc 38 ef 01 75 50 61 37 76 18
f4 a8 0d 59
Generated K1 (20 bytes)
d5 bb a6 0e bf 80 40 a7 c9 e3 8d 0f 0f 37 b2 51
f0 39 96 ba
Generated K2 (20 bytes)
69 54 9b 52 2d 2f ce 03 78 4b c6 70 e5 a4 6f 82
cb 40 5a 66
SENDING A RAKP 3 MESSAGE
sending packet (44 bytes)
06 00 ff 07 06 14 00 00 00 00 00 00 00 00 1c 00
00 00 00 00 fc ec 8f 01 94 a4 a6 dd 42 76 08 27
83 86 f2 c5 c7 f7 e9 b7 35 35 2a 30
<< Received data (24 bytes)
06 00 ff 07 06 15 00 00 00 00 00 00 00 00 08 00
00 0f 00 00 a4 a3 a2 a0
<<RAKP 4 MESSAGE
<< Message tag : 0x00
<< RMCP+ status : invalid integrity
check value
<< Console Session ID : 0xa0a2a3a4
<< Key exchange auth code [sha1] :
0x00fcaa8fabf484c1223916d9

RAKP 4 message indicates an error : invalid integrity
check value
Error: Unable to establish IPMI v2 / RMCP+ session
Error sending Chassis Status command
RAKP 4 message indicates an error : invalid
integrity check value
Error: Unable to establish IPMI v2 / RMCP+ session
Get Device
ID command failed
The -o intelplus option was introduced to handle the
Intel BMC
specifics. IPMItool with RMCP+ should work fine with
the Harwich System.
But SOL will need some more investigations and some
extra setup.
Holger
__________________________________
Yahoo! Mail Mobile
Take Yahoo! Mail with you! Check email on your mobile phone.
http://mobile.yahoo.com/learn/mail
H***@fujitsu-siemens.com
2005-04-11 18:44:13 UTC
Permalink
Post by Oscar Gueta
Hello,
It doesn't work, even using "-o intelplus".
Hmmm, that's to bad. I have to verify the current sources from cvs with
my saved copy. There are 2 things I have noticed:

- you are trying to connect without specifying the username (or you have
omited this from the trace). In case no username is given, a role lookup
is specified during session handshake and performed (e.g configured
password for NULL user). The BMC has to support this, and I never tried
this before with ipmitool.

Also you can try to connect without authentication during RAKP stage
(e.g. use -C 0). This will turn off Integrity code and encryption as
well.

Could you also please provide an ethereal sniff with -C 2 (not
encrypted, but authenticated during RAKP and integrity) and/or a log
with verbose > 2 (e.g. -vvv)

Thank you,

Holger

P.S. Which BMC version you are using?
Oscar Gueta
2005-04-11 21:17:43 UTC
Permalink
Holger,

Thanks for your suggestions. I am going to set up
the user and try to connect. In te meantime this is
the output with "-C 2" along with the ethereal trace
attached.

Using "-C 0" completes the authentication phase
succesfully, but when executing the ipmi command, BMC
responds with an error, reported as "Error sending
Chassis Status command: Invalid command" by ipmitool.

/Oscar

[***@localhost ipmitool-1.8.1.orig]# ipmitool -I
lanplus -H 10.5.99.135 -P patula chassis status -vvv
-o intelplus -C 2
IPMI LAN host 10.5.99.135 port 623
Post by H***@fujitsu-siemens.com
Sending IPMI command payload
netfn : 0x06
command : 0x38
data : 0x8e 0x04
BUILDING A v1.5 COMMAND
Post by H***@fujitsu-siemens.com
IPMI Request Session Header
Authtype : NONE
Sequence : 0x00000000
Session ID : 0x00000000
IPMI Request Message Header
Rs Addr : 20
NetFn : 06
Rs LUN : 0
Rq Addr : 81
Rq Seq : 00
Rq Lun : 0
Command : 38
sending packet (23 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 09 20 18
c8 81 00 38 8e 04 b5
<< Received data (30 bytes)
06 00 ff 07 00 00 00 00 00 00 00 00 00 10 81 1c
63 20 00 38 00 01 84 0e 03 00 00 00 00 12
<< IPMI Response Session Header
<< Authtype : NONE
<< Payload type : IPMI (0)
<< Session ID : 0x00000000
<< Sequence : 0x00000000
<< IPMI Msg/Payload Length : 16
<< IPMI Response Message Header
<< Rq Addr : 81
<< NetFn : 07
<< Rq LUN : 0
<< Rs Addr : 20
<< Rq Seq : 00
<< Rs Lun : 0
<< Command : 38
<< Compl Code : 0x00
Post by H***@fujitsu-siemens.com
SENDING AN OPEN SESSION REQUEST
sending packet (48 bytes)
06 00 ff 07 06 10 00 00 00 00 00 00 00 00 20 00
00 00 00 00 a4 a3 a2 a0 00 00 00 08 01 00 00 00
01 00 00 08 01 00 00 00 02 00 00 08 00 00 00 00
<< Received data (52 bytes)
06 00 ff 07 06 11 00 00 00 00 00 00 00 00 24 00
00 00 00 00 a4 a3 a2 a0 4a 8f 0d 05 00 00 00 08
01 00 00 00 01 00 00 08 01 00 00 00 02 00 00 08
00 00 00 00
<<OPEN SESSION RESPONSE
<< Message tag : 0x00
<< RMCP+ status : no errors
<< Maximum privilege level : Unknown
(0x00)
<< Console Session ID : 0xa0a2a3a4
<< BMC Session ID : 0x050d8f4a
<< Negotiated authenticatin algorithm : hmac_sha1
<< Negotiated integrity algorithm : hmac_sha1_96
<< Negotiated encryption algorithm : none
Post by H***@fujitsu-siemens.com
Console generated random number (16 bytes)
59 f1 8a ea 6b f4 e3 f7 58 dd 6c 83 a4 9e ac 5d
Post by H***@fujitsu-siemens.com
SENDING A RAKP 1 MESSAGE
sending packet (44 bytes)
06 00 ff 07 06 12 00 00 00 00 00 00 00 00 1c 00
00 00 00 00 4a 8f 0d 05 59 f1 8a ea 6b f4 e3 f7
58 dd 6c 83 a4 9e ac 5d 14 00 00 00
<< Received data (76 bytes)
06 00 ff 07 06 13 00 00 00 00 00 00 00 00 3c 00
00 00 00 00 a4 a3 a2 a0 11 38 c7 a0 2d 9f 16 ac
11 61 aa eb d7 34 8e dc ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff 9c da e6 05 51 97 a2 b0
3e 29 06 86 f5 f9 d1 13 72 31 18 43
<<RAKP 2 MESSAGE
<< Message tag : 0x00
<< RMCP+ status : no errors
<< Console Session ID : 0xa0a2a3a4
<< BMC random number :
0x1138c7a02d9f16ac1161aaebd7348edc
<< BMC GUID :
0xffffffffffffffffffffffffffffffff
<< Key exchange auth code [sha1] :
0x9cdae6055197a2b03e290686f5f9d11372311843

bmc_rand (16 bytes)
11 38 c7 a0 2d 9f 16 ac 11 61 aa eb d7 34 8e dc
Post by H***@fujitsu-siemens.com
rakp2 mac input buffer (58 bytes)
a4 a3 a2 a0 4a 8f 0d 05 59 f1 8a ea 6b f4 e3 f7
58 dd 6c 83 a4 9e ac 5d 11 38 c7 a0 2d 9f 16 ac
11 61 aa eb d7 34 8e dc ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff 14 00
Post by H***@fujitsu-siemens.com
rakp2 mac key (20 bytes)
70 61 74 75 6c 61 00 00 00 00 00 00 00 00 00 00
00 00 00 00
Post by H***@fujitsu-siemens.com
rakp2 mac as computed by the remote console (20
bytes)
9c da e6 05 51 97 a2 b0 3e 29 06 86 f5 f9 d1 13
72 31 18 43
Post by H***@fujitsu-siemens.com
rakp3 mac input buffer (22 bytes)
11 38 c7 a0 2d 9f 16 ac 11 61 aa eb d7 34 8e dc
a4 a3 a2 a0 04 00
Post by H***@fujitsu-siemens.com
rakp3 mac key (20 bytes)
70 61 74 75 6c 61 00 00 00 00 00 00 00 00 00 00
00 00 00 00
generated rakp3 mac (20 bytes)
49 62 e5 f4 5c 28 9e 81 32 c7 11 eb 2c dc ef b8
02 3f cb e7
session integrity key input (34 bytes)
59 f1 8a ea 6b f4 e3 f7 58 dd 6c 83 a4 9e ac 5d
11 38 c7 a0 2d 9f 16 ac 11 61 aa eb d7 34 8e dc
14 00
Generated session integrity key (20 bytes)
49 2c ac 02 18 81 95 c5 4e ec 75 f7 3a 69 13 c6
1a a6 7f 39
Generated K1 (20 bytes)
6c 4d 64 2f 75 38 29 32 4f a6 2a 02 d8 01 c4 eb
7a 5e 61 07
Generated K2 (20 bytes)
75 ee 57 5d 85 e2 d6 12 4b 82 ec b7 34 c5 c3 77
3e 48 93 03
Post by H***@fujitsu-siemens.com
SENDING A RAKP 3 MESSAGE
sending packet (44 bytes)
06 00 ff 07 06 14 00 00 00 00 00 00 00 00 1c 00
00 00 00 00 4a 8f 0d 05 49 62 e5 f4 5c 28 9e 81
32 c7 11 eb 2c dc ef b8 02 3f cb e7
<< Received data (24 bytes)
06 00 ff 07 06 15 00 00 00 00 00 00 00 00 08 00
00 0f 00 00 a4 a3 a2 a0
<<RAKP 4 MESSAGE
<< Message tag : 0x00
<< RMCP+ status : invalid integrity
check value
<< Console Session ID : 0xa0a2a3a4
<< Key exchange auth code [sha1] :
0x0038c7a02d9f16ac1161aaeb

RAKP 4 message indicates an error : invalid integrity
check value
Error: Unable to establish IPMI v2 / RMCP+ session
Error sending Chassis Status command
Post by H***@fujitsu-siemens.com
Hello,
It doesn't work, even using "-o intelplus".
Hmmm, that's to bad. I have to verify the current
sources from cvs with
- you are trying to connect without specifying the
username (or you have
omited this from the trace). In case no username is
given, a role lookup
is specified during session handshake and performed
(e.g configured
password for NULL user). The BMC has to support
this, and I never tried
this before with ipmitool.
Also you can try to connect without authentication
during RAKP stage
(e.g. use -C 0). This will turn off Integrity code
and encryption as
well.
Could you also please provide an ethereal sniff with
-C 2 (not
encrypted, but authenticated during RAKP and
integrity) and/or a log
with verbose > 2 (e.g. -vvv)
Thank you,
Holger
P.S. Which BMC version you are using?
-------------------------------------------------------
Post by H***@fujitsu-siemens.com
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT
Products from real users.
Discover which products truly live up to the hype.
Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Duncan Laurie
2005-04-11 21:31:20 UTC
Permalink
Post by Oscar Gueta
Holger,
Thanks for your suggestions. I am going to set up
the user and try to connect. In te meantime this is
the output with "-C 2" along with the ethereal trace
attached.
Can you try this patch:

--- src/plugins/lanplus/lanplus.c 21 Mar 2005 09:33:52 -0000 1.33
+++ src/plugins/lanplus/lanplus.c 11 Apr 2005 21:26:52 -0000
@@ -2528,7 +2528,7 @@
memset(msg, 0, IPMI_OPEN_SESSION_REQUEST_SIZE);

msg[0] = 0; /* Message tag */
- msg[1] = 0; /* Give us highest privlg level based on supported
algorithms */
+ msg[1] = session->privlvl;
msg[2] = 0; /* reserved */
msg[3] = 0; /* reserved */

I wonder if the BMC doesn't like the 'highest based on algorithms'
Post by Oscar Gueta
<<OPEN SESSION RESPONSE
<< Message tag : 0x00
<< RMCP+ status : no errors
<< Maximum privilege level : Unknown
(0x00)
This isn't really an ideal solution because there should be a way to
specify this to ipmitool but for now it might help your situation.
Post by Oscar Gueta
Using "-C 0" completes the authentication phase
succesfully, but when executing the ipmi command, BMC
responds with an error, reported as "Error sending
Chassis Status command: Invalid command" by ipmitool.
This might have authenticated at a bad privilege level, possibly due to
the same thing as above.

-duncan
Oscar Gueta
2005-04-11 22:41:43 UTC
Permalink
Duncan,

Works fantastic after patching!
Thanks.

/Oscar

[***@localhost ipmitool-1.8.1]# ipmitool -I lanplus
-H 10.5.99.135 -P two -U two bmc info -o intelplus
Device ID : 32
Device Revision : 1
Firmware Revision : 0.21
IPMI Version : 2.0
Manufacturer ID : 343
Product ID : 260 (0x0104)
Device Available : yes
Provides Device SDRs : no
Additional Device Support :
Sensor Device
SDR Repository Device
SEL Device
FRU Inventory Device
IPMB Event Receiver
Chassis Device
Aux Firmware Rev Info :
0x00
0x11
0x00
0x3a
On Mon, 2005-04-11 at 14:17 -0700, Oscar Gueta
Post by Oscar Gueta
Holger,
Thanks for your suggestions. I am going to set
up
Post by Oscar Gueta
the user and try to connect. In te meantime this
is
Post by Oscar Gueta
the output with "-C 2" along with the ethereal
trace
Post by Oscar Gueta
attached.
--- src/plugins/lanplus/lanplus.c 21 Mar 2005
09:33:52 -0000 1.33
+++ src/plugins/lanplus/lanplus.c 11 Apr 2005
21:26:52 -0000
@@ -2528,7 +2528,7 @@
memset(msg, 0,
IPMI_OPEN_SESSION_REQUEST_SIZE);
msg[0] = 0; /* Message tag */
- msg[1] = 0; /* Give us highest privlg level
based on supported
algorithms */
+ msg[1] = session->privlvl;
msg[2] = 0; /* reserved */
msg[3] = 0; /* reserved */
I wonder if the BMC doesn't like the 'highest based
on algorithms'
Post by Oscar Gueta
<<OPEN SESSION RESPONSE
<< Message tag : 0x00
<< RMCP+ status : no errors
<< Maximum privilege level : Unknown
(0x00)
This isn't really an ideal solution because there
should be a way to
specify this to ipmitool but for now it might help
your situation.
Post by Oscar Gueta
Using "-C 0" completes the authentication
phase
Post by Oscar Gueta
succesfully, but when executing the ipmi command,
BMC
Post by Oscar Gueta
responds with an error, reported as "Error sending
Chassis Status command: Invalid command" by
ipmitool.
This might have authenticated at a bad privilege
level, possibly due to
the same thing as above.
-duncan
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
H***@fujitsu-siemens.com
2005-04-12 10:47:54 UTC
Permalink
Post by Oscar Gueta
Duncan,
Works fantastic after patching!
Thanks.
Good to hear it's working after all.

Holger Liebig

Loading...