Unable to connect to VNXe3200 via IPMITool. RAKP 2 HMAC is invalid #344
Comments
@Rennekww It looks to me like your BMC is returning a wrong RAKP2 HMAC key. Please try an up to date source from github rather than some old 1.8.18. Also try to experiment with different cipher suites (the -c option). |
I took the sources from here https://github.com/ipmitool/ipmitool and just recently, 3 days ago. C0: Loading IANA PEN Registry...
BUILDING A v1.5 COMMAND
bmc_rand (16 bytes)
IPMIv2 / RMCP+ SESSION OPENED SUCCESSFULLY
BUILDING A v2 COMMAND
BUILDING A v2 COMMAND
All the others end up the same. Loading IANA PEN Registry...
BUILDING A v1.5 COMMAND
bmc_rand (16 bytes)
c:\ipmitool>ipmitool.exe -vvvvvv -I lanplus -C 17 -U console -P FCNBC152200435 -H 128.221.1.252 sol activate Loading IANA PEN Registry...
BUILDING A v1.5 COMMAND
bmc_rand (16 bytes)
|
Good afternoon.
I can't connect to the SPA storage process at VNXe3200.
Using IPMITool version 1.8.18. Compiled built on windows 7. I'm trying to connect from another PC, but also Windows 10.
Below is the information displayed when trying to connect.
c:\ipmitool>ipmitool.exe -vvv -I lanplus -C3 -U console -P FCNBC152200435 -H 128.221.1.252 sol activate
ipmitool version 1.8.18
Loading IANA PEN Registry...
IANA PEN registry open failed: No such file or directory
BUILDING A v1.5 COMMAND
<<OPEN SESSION RESPONSE
<< Message tag : 0x00
<< RMCP+ status : no errors
<< Maximum privilege level : admin
<< Console Session ID : 0xa0a2a3a4
<< BMC Session ID : 0x0200ca00
<< Negotiated authenticatin algorithm : hmac_sha1
<< Negotiated integrity algorithm : hmac_sha1_96
<< Negotiated encryption algorithm : aes_cbc_128
<<RAKP 2 MESSAGE
<< Message tag : 0x00
<< RMCP+ status : no errors
<< Console Session ID : 0xa0a2a3a4
<< BMC random number : 0x5e0c4cb451702dd2d188ddea78bdb136
<< BMC GUID : 0x20000102027f00000000000000000000
<< Key exchange auth code [sha1] : 0x167046d02953f9fe32674e602587b72afbe98970
bmc_rand (16 bytes)
5e 0c 4c b4 51 70 2d d2 d1 88 dd ea 78 bd b1 36
The text was updated successfully, but these errors were encountered: