In the message dated: Fri, 05 Apr 2013 10:17:10 -0500,
The pithy ruminations from Dave Caplinger on 
<[lopsa-tech] IMPI (was Re: OpenManage)> were:
=> On Apr 5, 2013, at 9:26 AM, Jon Dustin <jdus...@usm.maine.edu> wrote:
=> 
=> > On 4/5/2013 at 10:19 AM, Matt Lawrence <m...@technoronin.com> wrote:
=> >> Yet another monitoring question.  Since I work in an environment that is 
=> >> almost exclusively Dell, and I'm looking for a monitoring solution, I'm 
=> >> wondering if any of the popular monitoring solutions out there leverage 
=> >> the various tools in the OpenManage family...
=> > I've installed OMSA on Linux servers, then used some command-line scripts 
to parse status and send to another monitoring system. This way I'm not saddled 
with a "Dell-centric" monitoring console, yet still can see inside these 
servers.
=> 
=> Have you (or anyone else on the list) had any success using 'impitool'

Yes.

=> (from OpenIPMI; already in many Linux distros) to get at these events
=> instead?  It  would be nice to have a vendor-agnostic means to get

Yes.

=> this data, though certainly getting it from OpenManage's 'omreport'
=> tool works too.  Also, if I understand correctly, IMPI may work even in
=> cases where there is no iDRAC, since it talks directly to the Baseboard
=> Management Controller (BMC).

Yes.

I've used ipmitool, and continue to use it on non-Dell machines. On the Dell
boxes, I've stopped using ipmitool in favor of OpenManage, as the level of
detail from OpenManage is much better. This may be due to differences in the
Nagios checks, but if you look at the raw output from ipmitool, it's much
harder to decipher.

For example, right now, one of my machines is reporting the following through
the OpenManage Nagios plugin:

        CRITICAL: Memory module 6 [DIMM_B3, 8192 MB] needs attention: 
Single-bit warning error rate exceeded, 

whereas the ipmitool output doesn't give the same level of detail:

         Memory ECC Uncorr Err | Uncorrectable ECC | Asserted

Sure, that's enough to trigger a change in the status as reported to Nagios,
but it then requires further investigation (login to the machine, use
additional tools to determine which DIMM was an issue, etc., etc.).

Thanks,

Mark

=> - Dave
=> _______________________________________________
=> Tech mailing list
=> Tech@lists.lopsa.org
=> https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
=> This list provided by the League of Professional System Administrators
=>  http://lopsa.org/
=> 

-- 
Mark Bergman    Biker, Rock Climber, Unix mechanic, IATSE #1 Stagehand
'94 Yamaha GTS1000A^2
berg...@panix.com

http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=bergman%40panix.com

I want a newsgroup with a infinite S/N ratio! Now taking CFV on:
rec.motorcycles.stagehands.pet-bird-owners.pinballers.unix-supporters
15+ So Far--Want to join? Check out: http://www.panix.com/~bergman 
_______________________________________________
Tech mailing list
Tech@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to