Hi Al,
you are absolutely right!
In this way it works:
[r...@tpw ~]# ipmimonitoring -V
ipmimonitoring - 0.7.12.beta2
Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC.
Copyright (C) 2006-2007 The Regents of the University of California.
This program is free software; you may
Hi Werner,
Great to hear.
I have configured the IPMI settings and IPMI user via the Intel
Server Deployment CD:
http://*downloadcenter.intel.com/Detail_Desc.aspx?agr=YInst=YesProductID=2451DwnldID=17974strOSs=38OSFullName=OS%20Independentlang=eng
Ugh ... that's sort of disappointing. Once
Hi Al,
sorry for my late reply. Now I'm back in the office. You find my results
below:
On Mon, 2009-08-24 at 10:40 -0700, Al Chu wrote:
Hi Werner,
Thanks for the feedback.
[r...@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p
relation
Could you run --debug with the -W
Hey Werner,
Actually, your default config may be the issue afterall, not the
motherboard. Your default config is not allowing authentication by any
privilege level other than admin. How about trying ipmimonitoring
with the -l admin, to tell ipmimonitoring to use the admin privilege
level.
Out
Hi Al,
thanks for the updated tar.gz. I tried it, but somehow it still seems to
cause problems (see below). I'll be two days out of office - so I can do
further tests on Thursday.
thanks for your support!
[r...@tpw ~]# rpm -q freeipmi
freeipmi-0.7.12.beta2-1.fc9.i386
[r...@tpw ~]#
Hi Werner,
I've got a test tar.gz here:
http://ftp.gluster.com/pub/freeipmi/qa-release/freeipmi-0.7.12.beta2.tar.gz
This makes it so the 'authcap' workaround should work for you. Can you
give it a shot to make sure it works?
Thanks,
Al
On Fri, 2009-08-21 at 08:44 -0700, Al Chu wrote:
Hi
Dear freeipmi users/developers,
I'm trying to monitor an Intel SR2500 server (this server has the Intel
S5000PAL mainboard in it).
While I can monitor it using ipmitool, I keep getting errors with
ipmimonitoring from freeipmi. Also using the -W parameter for
workarounds (as described in the
Hi Werner,
It's possible the motherboard is not reporting supported authentication
types correctly. You could give the authcap workaround a shot.
However, if this is being non-compliant in the way that I think it is,
the authcap workaround won't work (b/c it currently handles a
different