Re: [Freeipmi-users] Problem accessing Supermicro X9DRT-HF+

[Al Chu]

On Fri, 2012-09-07 at 18:40 -0700, Alastair Young wrote:
> I spoke too soon. When I applied the parameter change to the
> monitoring some of the old boxes went sideways.
> 
> Some machines first said "/usr/sbin/ipmimonitoring: k_g invalid " and
> then said "ipmi_ctx_open_outofband_2_0: BMC busy"

I know some of the older Supermicros need the "opensesspriv" workaround
when using IPMI 2.0.  The "authcap" workaround may work as well.  The
"BMC busy" error is perplexing, perhaps some of the systems just can't
handle IPMI 2.0 too well.

> And this locks them up from web access too....
> 
> So selective application of '-D lan20' is in order.

I wish we could get to the bottom of it, but glad its working for you.
I imagine there's some subtle bug in the firmware that just isn't
obvious.

Al

> 
> Alastair N. Young | Senior Ground Control
> 
> Rocket Fuel Inc.
> 
> address@hidden
> 650.517.8834 p
> 925.784.0812 m
> www.rocketfuel.com 
> 
> 
> 
> 
> 
> 
> On Fri, Sep 7, 2012 at 6:21 PM, Alastair Young <address@hidden>
> wrote:
>         We tried resets and power cycles already. And it doesn't work
>         with admin either.
>         
>         However "-D lan20" works!
>         
>         And that works on my old boxes too, so we'll just add that to
>         our params.
>         
>         many thanks!
>         
>         
>         
>         
>         Alastair N. Young | Senior Ground Control
>         
>         Rocket Fuel Inc.
>         
>         address@hidden
>         650.517.8834 p
>         925.784.0812 m
>         www.rocketfuel.com 
>         
>         
>         
>         
>         
>         
>         
>         On Fri, Sep 7, 2012 at 5:19 PM, Albert Chu <address@hidden>
>         wrote:
>                 Hi Alistair,
>                 
>                 Everything seems to be configured correctly.  There
>                 certainly could be a
>                 bug/issue on the motherboard.  I have two guesses on
>                 the issue and ways
>                 to see if we can get things to work:
>                 
>                 1) I've seen some motherboards that did not seem to
>                 "take" new
>                 configuration until the BMC was reset by a hard power
>                 cycle (i.e. button
>                 push) or a cold reset (/usr/sbin/bmc-device
>                 --cold-reset).  It's worth a
>                 try.
>                 
>                 2) The BMC incorrectly expects a perfect combination
>                 of inputs to
>                 function.  Does user ADMIN work?  What happens if you
>                 change the
>                 privilege level (-l admin or -l operator) or
>                 authentication type (-a md2
>                 or -a straight_password_key) or using IPMI 2.0 (-D
>                 lan20).
>                 
>                 Unfortunately I've seen a number of motherboards where
>                 #2 happens to the
>                 case.  Despite a perfectly legal & correct combination
>                 of options given
>                 the configuration, the BMC just gets confused and
>                 won't allow a
>                 connection.
>                 
>                 Al
>                 
>                 
-- 
Albert Chu
address@hidden
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory