Sentry CDU Monitor

Up to Documents in ZenPacks

Currently Being Moderated

VERSION 5

Created on: Sep 14, 2009 1:31 PM by chudler - Last Modified: Feb 19, 2010 3:44 PM by Matt Ray

Submitted by:

Colin Hudler

Description:

This is complete rewrite of the old-style 1.0 SentryCDU Zenpack. This pack provides:

Sentry3 MIBs
Device class /Power/SentryCDU
CDU Hardware tab on the device, which includes:
- Installed Towers, with component template for load graph and thresholds
- Each stack with template for load graph/thresh
- Environmental sensor node template with Humidity and Temp graph/thresh
CDU Device template with total device load graph/thresh
SentryCDU Reports organizer with graph reports of:
- All Temperatures (single graph)
- All Humidity (single graph)
- All CDUs aggregate load (one graph per CDU)
Sentry Tower Map modeler for associating Towers (and infeeds) with device
Sentry Sensor map modeler for associating probes with CDUs

Additional Enhancements:

Addition or removal of probes, stacks, and feeds automatically creates associated components and templates when the device is remodeled, so no more dealing with -1 values, or stacks not present. This should also handle a wider ranges of Sentry3-compatible equipment.
Now works with distributed collectors.

Limitations/Known Problems:

The Zenpack can be installed along with v1.0 because it uses SentryCDU class-names instead of "Sentry CDU", but the devices will have to be deleted and added in the new class (/Devices/Power/SentryCDU). Moving them and remodeling will not work. Additionally, the graphs are part of components, instead of the device, so previously-collected data will not be visible. The admin can delete v1.0 at their discretion.
Some Sentry devices do not report Stacks or Infeeds. You can verify this with snmpwalk, and upgrade the firmware as appropriate.
Only TempHumidity probe is supported at this time (no water-sensor, contact_closure, etc).
ONLY supports Sentry3-compatible devices. The author does not have any first or second generation devices to test with.
Thresholds on each template must be adjusted to taste. /Devices/Tower, /Devices/SentrySensor, /Devices/InFeed, and /Devices/Power/SentryCDU/SentryCDU are the templates.
It is not capable of adjusting to the correct amps unit. This will be fixed in the next version. Until then, it may be necessary to use RPN on certain datapoints.
It can inexplicably fail to update datapoints. This *will* be fixed in the next version, but has not been reliably duplicated to troubleshoot.
Viewing the Tower component template page sometimes displays an error about "unable to parse command line arguments", but only when zenperfsnmp is cycling. This is likely a threading problem around an unsynchronized variable, and may be fixed by Zenoss, if they are aware of it.

Tested With: