UNSOLVED

stemplar444

updated

12 years ago

S

stemplar444

1 Rookie

•

14 Posts

0

39163

February 23rd, 2015 01:00

OME 2.0.1, Power-On with IPMI and key fails with 'RAKP 4 message has invalid integrity check value'

I seem to be affected by the same thing as in

http://en.community.dell.com/techcenter/systems-management/f/4469/t/19596212

Using the ipmitools -I lanplus -vvv .... I'll get

...

> RAKP 4 message has invalid integrity check value
Error: Unable to establish IPMI v2 / RMCP+ session
Error sending Chassis Status command

 That's the message (Error: Unable to establish IPMI v2 / RMCP+ session) I see in OME. Does anybody have an idea?

I was trying to use '-o intelplus' as suggested elsewhere, but this does not help. After looking at the code of ipmitools.exe on github, I'm under the impression, that using a key for IPMI seems simply not possible (at least with iDRAC7, 1.66.65)

 

  • DELL-Rob C

    4 Apprentice

    •

    2843 Posts

    2963

    0

    Posted February 23rd, 2015 08:00

    Hi and thanks for the post.  

    Just to confirm, are you testing this IPMItool command in a dos/cmd window outside of OME first to confirm that it works?

    Or are you saying that even running outside of OME from a dos/cmd window that it is failing as you indicate in your post.

    Thanks,

    Rob

    delltechcenter.com/ome

  • stemplar444

    1 Rookie

    •

    14 Posts

    2963

    0

    Posted February 23rd, 2015 12:00

    Hi Rob,

    I started with IPMI in OME, but then proceeded to the console. So yes, ipmitool fails in both situations.

    Only in the command prompt I can use additional flags like -vv or even -vvv to get more details. It could be a version thing, but my desire to go through all kind of combinations is limited, especially, because I'm using latest and greatest from my point of view. And with -vvv, one can see that the hashes are different. I tried two different keys (with different even length) without success. In contrast, the IPMI test in the DELL troubleshooting tool works against the same iDRAC configuration.

    -Simon

  • DELL-Rob C

    4 Apprentice

    •

    2843 Posts

    2963

    0

    Posted February 24th, 2015 11:00

    Hi,

    I just updated the original thread you reference in your first post.

    Rob

    --

    • Just looking at this now...

      iDRAC uses hexidemial keys. So we expect to use -x option for ipmitool to work wtih keys.

      Something like:

      ipmitool -I lanplus -H 10.1.1.1 -U root -P yourPasswd -x 00AADD0000000000000000000000000000000000 chassis power status

      Thanks,

      Rob

  • stemplar444

    1 Rookie

    •

    14 Posts

    2963

    1

    Posted February 25th, 2015 03:00

    Thanks for the hint. I do not understand why three different options are available to pass a key. This is just asking for troubles:

    -k key         Use Kg key for IPMIv2 authentication
    -x key         Use Kg key in hex value
    -y hex_key     Use hexadecimal-encoded Kg key for IPMIv2 authentication

    To recap

    Tool/Comment command line option

    Result 

    I was using -y

    Fails with

    Error: Unable to establish IPMI v2 / RMCP+ session
    Error sending Chassis Status command

    OME is using

    verified with procmon

    -k

    Fails with

    Results:  Beendungscode:1. Ausgabe von Befehl (stderr): Error: Unable to establish IPMI v2 / RMCP+ session Unable to set Chassis Power Control to Up/On

    Your suggestion -x This actually works, but in the help, this is the only option which does not mention IPMIv2. Are we really on IPMI v2 by doing this?

     

    The conclusion for me is simple, basically none of the OME 2.0.1 built in 'Power Tasks' work when IPMI keys in place.

     -Simon

  • DELL-Pupul M

    2 Intern

    •

    1004 Posts

    2963

    0

    Posted March 5th, 2015 01:00

    Hi Simon,

    Thanks for the observation. OME does not use IPMI for all the built in power tasks. It is just the Power ON task which uses IPMI connection. Other tasks make use of OMSA connection.

    Also, -k option does not take the values in the hex format. Instead, it needs to be converted properly to the supported format. I did find information about ipmitool on sourceforge (sourceforge.net/.../6480441) on the same saying -k needs the value to be converted to ASCII but not sure about the authenticity of the same. I am trying to get more information here. I'll get back.