[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Freeipmi-users] possible causes for "ipmi_ctx_open_outofband: BMC b

From: Werner Fischer
Subject: Re: [Freeipmi-users] possible causes for "ipmi_ctx_open_outofband: BMC busy"
Date: Fri, 22 Apr 2011 10:17:44 +0200

Hi Al,

thanks for this info.
I now got the info that this user is using FreeIPMI only for Nagios, but
is using ipmitool for his cacti monitoring. I assume that he does not
use the SDR cache function of ipmitool, as it has to be used manually
and that this is the root cause.

I told him to use "ipmitool sdr dump" and then "ipmitool -S" - I think
this will solve his problem.

Thanks for your help,

On Thu, 2011-04-21 at 10:00 -0700, Albert Chu wrote:
> Hi Werner,
> The "BMC Busy" error code comes directly from the remote system.  As you
> might imagine, it's typically when the BMC has too many IPMI requests to
> handle and can't handle all of them.  That's the scenario I've
> personally seen them the most on.
> Al
> On Thu, 2011-04-21 at 02:15 -0700, Werner Fischer wrote:
> > Hi Al,
> > 
> > one of our customers monitors his Supermicro servers with FreeIPMI (with
> > both Nagios using the plugin, and also using cacti). As both Nagios and
> > cacti are monitoring the machines, it could be that two IPMI requests
> > reach the BMC at the same time.
> > 
> > For two systems (with X8DT3-LN4F and X8DTL-3F mainboards) he gets many
> > times the following error:
> >     ipmi_ctx_open_outofband: BMC busy
> > 
> > As it works for other systems, I assume that this could be a hardware
> > problem.
> > 
> > But I just wanted to know what the possibles reasons could be for such
> > an error ("BMC busy")
> > 
> > Best regards,
> > Werner
> > 
> > PS: for the SR1625 question I got know feedback yet. I assume that the
> > new beta works, but this customer can tell me for sure in about two
> > weeks (than he can test the current beta)
> > 

: Werner Fischer
: Technology Specialist
: Thomas-Krenn.AG | The server-experts
: |

reply via email to

[Prev in Thread] Current Thread [Next in Thread]