I'm looking to monitor temperature on some various Cisco equipment (2821,
3750, 4948, 6509, etc). I've looked at the check_catalyst_temp.pl and
check_env_stats.py plugins, which both look in .1.3.6.1.4.1.9.9.13.1. I see
and understand the basic mechanisms of these checks.
What I don't understand is why both require warning and critical thresholds.
From what I can tell, both walk ciscoEnvMonTemperatureStatusDescr, check
ciscoEnvMonTemperatureState (and alert accordingly) AND also check
ciscoEnvMonTemperatureStatusValue
to see if it's out of the warning and critical thresholds specified on the
command line. I understand why one would want to be able to set custom
thresholds (that would override "normal" and "warning" states). What I
don't understand is why are they required? Is there a reason, or is it just
an oversight? I don't have much experience monitoring network equipment, so
I'm wondering if there's a reason for it.
On that same note, does anyone know where those thresholds are stored? I
see in the same OID that there is ciscoEnvMonTemperatureThreshold, but
that's an absolute upper bound before a forced shutdown occurs. I'm
assuming that the thresholds for "warning" and "critical"
ciscoEnvMonTemperatureState
must be stored somewhere else. Does anyone know where that is?
Unless there's a good reason for requiring -w and -c, I'll probably change
one of the plugins to not require them.
Thanks in advance,
Jeffrey.
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Nagios-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
