Hey Kenneth,
(I thought I responded already, but nothing is showing up on the mailing
list and nothing is in my sent box. Anyways ...)
I've got a tar.gz out that attempts to ignore the 0xCE errors in
ipmi-sensors and ipmimonitoring. Could you check it out and LMK if it
works for you?
http://ft
Hey Kenneth,
I've got a test tar.gz here that tries to workaround/ignore sensors with
the 0xCE completion code. Could you see if this works?
http://ftp.zresearch.com/pub/freeipmi/qa-release/freeipmi-0.7.10.beta2.tar.gz
Thanks,
Al
On Tue, 2009-06-09 at 12:55 -0700, Al Chu wrote:
> Hi Kenneth,
Hey Dave,
Whew, I'm glad I have a relatively new sun board, this would have been
tough to figure out :-)
Effectively, the "opensesspriv" workaround is also needed for the Sun
boards. I've wrapped that workaround in as an automatic one for the Sun
workaround, so it should work now. Test tar.gz i
Hey Dave,
Thanks for some of the clarifications. I'd like to keep the ordering
the same b/c it's actually split up IPMI 1.5 vs. IPMI 2.0. And some of
the text was from folks at Sun. So I've done the below patch instead.
Look good?
Al
On Tue, 2009-06-09 at 15:02 +0100, Dave Love wrote:
> As fa
Hi Kenneth,
Thanks for the --debug output (was about to e-mail you for it). 0xCE ==
"Command response could not be provided.". That's certainly an odd
completion code error (compared to completion codes for "record not
present" or "parameter out of range"). I'm not sure why the HP machine
would
One more detail about the HP ProLiant DL145 G2. See
http://lists.gnu.org/archive/html/freeipmi-devel/2009-06/msg2.html for
previous details.
What follows is the tail end of "ipmi-sensors -D open --debug" showing the
requests that elicit the bad completion code "CE".
Thanks,
Ken
Hey Dave,
> OK, appended.
Hmmm. It seems the workaround just isn't working. It's possible I have
introduced a bug into the workaround. Let me see if I can figure it
out.
> I didn't mean to be critical, of course. However, I find it's a real
> practical problem with our heterogeneous HPC syst
As far as I can tell, the Sun workarounds are generic in ELOM and ILOM,
and haven't been fixed in the current versions. I have x4100 with ILOM
1.0 and 2.0, x2200M2 with ELOM 2.0, and x4200m2 and x4500 with ILOM 2.0.
All seem to need the workarounds, and have the latest firmware apart
from ILOM 1.0
Al Chu writes:
> Hey Dave,
>
> It's entirely possible there is another issue for your systems I never
> encountered before or a bug in the workaround code. If you could send
> the --debug output, that'd be great.
OK, appended.
> Ipmitool also elects to "hide"
> workarounds in its tools more of
