* Liebig, Holger ([EMAIL PROTECTED]) [071005 17:39] wrote:
> Jacek,
> It's hard to tell, since send and receive responses are mixed in the verbose 
> output. IMHO it seems that your BMC responds with the response to the Get 
> Channel Auth Capabilities twice, this might resulting in a session handshake 
> out of order error in ipmitool. ipmitool should recover from this (see 
> ipmi_lan_poll_recv() in lanplus.c), but I'm not sure if it realy does.
> 
> > IPMI Request Match NOT FOUND
> 
> ==> Doublicate Response to Get Channel Auth Capabilities

OK, I have found why that duplication occured (I have connected both NICs to
same lan and set some bmc option to 'redundant' or sth like that - ipmi
packets were transmitted on both NICs).
Unfortunately I still can't establish ipmi session with lanplus interface:

debian:~/ipmitool-1.8.9# ipmitool -vv -I lanplus -U admin -H 192.168.10.11
-P pass sol activate
IPMI LAN host 192.168.10.11 port 623

>> Sending IPMI command payload
>>    netfn   : 0x06
>>    command : 0x38
>>    data    : 0x8e 0x04

>> SENDING AN OPEN SESSION REQUEST

<<OPEN SESSION RESPONSE
<<  Message tag                        : 0x00
<<  RMCP+ status                       : no errors
<<  Maximum privilege level            : admin
<<  Console Session ID                 : 0xa0a2a3a4
<<  BMC Session ID                     : 0x02006700
<<  Negotiated authenticatin algorithm : hmac_sha1
<<  Negotiated integrity algorithm     : hmac_sha1_96
<<  Negotiated encryption algorithm    : aes_cbc_128

>> Console generated random number (16 bytes)
 6e 38 de 4a a0 d5 27 71 e1 fd f2 20 f9 2a a0 e6
>> SENDING A RAKP 1 MESSAGE

<<RAKP 2 MESSAGE
<<  Message tag                   : 0x00
<<  RMCP+ status                  : no errors
<<  Console Session ID            : 0xa0a2a3a4
<<  BMC random number             : 0x9053a355844797c7fabd0d669154a44b
<<  BMC GUID                      : 0x44454c4c320010378042b1c04f34334a
<<  Key exchange auth code [sha1] :
0x2b4178f06a5648720aaa6cf14f61040de76defac

session integrity key input (39 bytes)
 6e 38 de 4a a0 d5 27 71 e1 fd f2 20 f9 2a a0 e6
 90 53 a3 55 84 47 97 c7 fa bd 0d 66 91 54 a4 4b
 14 05 61 64 6d 69 6e
Generated session integrity key (20 bytes)
 a0 3c 83 95 75 29 86 b3 38 4b 6c 83 1f 05 ee 8a
 10 44 07 2c
Generated K1 (20 bytes)
 9d be 9a b6 af 44 14 7f fe e5 c0 52 34 8a 52 5c
 47 a9 72 dc
Generated K2 (20 bytes)
 d4 61 f6 fb 59 b5 ca cc 50 aa 51 fa 25 59 1b c3
 87 0f f3 45
>> SENDING A RAKP 3 MESSAGE

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

> RAKP 4 message has invalid integrity check value
Error: Unable to establish IPMI v2 / RMCP+ session
Error: No response activating SOL payload




debian:~/ipmitool-1.8.9# ipmitool -I lan -U admin -H 192.168.10.11 -P pass
bmc info
Device ID                 : 32
Device Revision           : 0
Firmware Revision         : 1.33
IPMI Version              : 2.0
Manufacturer ID           : 674
Manufacturer Name         : Unknown (0x2a2)
Product ID                : 256 (0x0100)
Device Available          : yes
Provides Device SDRs      : yes
Additional Device Support :
    Sensor Device
    SDR Repository Device
    SEL Device
    FRU Inventory Device
    IPMB Event Receiver
    Bridge
    Chassis Device
Aux Firmware Rev Info     :
    0x00
    0x00
    0x00
    0x00




-- 
        Jacek


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Ipmitool-devel mailing list
Ipmitool-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel

Reply via email to