HP/Compaq Insight Management Agents Checker
Authored by Jason Leonard
E-mail: jason_leonard@yahoo.com


Version History
===============

	2.5
	Made code compatible with SNMPv3, improving efficiency
	and error handling along the way.

-----------------------------------------------------------------
 
	2.0
	Made code compatible with Ubuntu.

-----------------------------------------------------------------

	1.8
	After having one of our servers report a warning status 
	with no text, I realized that the memory was in warning
	status but not reporting any "errors". So I rewrote the 
	memory function to first check what i learned is an OID 
	for	overall memory condition first. Upon finding a 
	warning or critical, then the plugin does it's work to 
	report what it can.

-----------------------------------------------------------------

	1.71 
	Very minor code updates and logic fixes

-----------------------------------------------------------------

	1.7
	Had to rewrite drive checks yet again. We have a few 
	servers where the controller battery will flag a warning 
	on the system. This was causing Insight Agents to mark the 
	controller as warning, but my plugin only checks drive 
	problems on controller errors. Combined with my crappy 
	conditional coding, we were getting CRITICAL reports on 
	this. Now the plugin basically prioritizes CRITICAL
	checks, then WARNING checks.

-----------------------------------------------------------------

	1.6
	This was a major overhaul. After we had a drive failure 
	occur, and my other HP checks caught the error but this 
	one did not, I then realized something was amiss with my 
	code. What I discovered is that the global health status
	is in a different OID tree from the drives - so it does 
	not reflect drive status in any way. This means I had to 
	rewrite the oode to weigh both status indicators when 
	considering the true "global" status.

	Along with this, one or 2 variable references were corr-
	ected, and the drive checks were also updated to improve 
	how they returned status. Previously, the status codes 
	returned would have mimicked Systems Management - a 
	physical drive could have failed but the ststus return
	would still be WARNING. This means you would not be 
	e-mailed about any problems until you had a logical 
	drive in critical state - very bad news!!! Now, a failed 
	drive will make sure Nagios gets a critical state so you 
	get the e-mail you need to replace the drive BEFORE you
	are dealing with a dead logical drive.

-----------------------------------------------------------------

	1.1
	Fixed assignment statements in the	thermal status checks. 
	Added SNMP pre-flight checks after checking parameters 
	and binaries. Conformed code to a "universal standard" 
	for naming of functions and variables.

-----------------------------------------------------------------

	1.0	initial release