- Server Technology 3 Phase CDU
- SNMP XML
This is a greatly expanded and improved template set for Server Technology CDU (Cabinet Distribution Unit) devices. I originally created a set of templates 4 years ago for ServerTech units. The URL for those templates: http://forums.cacti.net/viewtopic.php?f=12&t=29481&hilit=ServerTech. Due to the way the data is presented via SNMP it was not possible to use a straight SNMP query to accomplish the overall goal for this template.
PLEASE NOTE: There is a bug in servertechnology-tower.xml . I haven't had a moment to fix it in the zip file. But please, change the OID/REGEXP line to: <oid_index_parse>OID/REGEXP:\.1\.3\.6\.1\.4\.1\.1718\.3\.2\.1\.1\.[0-9]\.([0-9])$</oid_index_parse>
Server Technology 3 Phase CDU - Infeeds Server Technology CDU - EMCU (Environmental Monitoring Control Unit) Server Technology CDU - Environmental Monitors Server Technology CDU - Towers
Stand-alone Graph Templates
Server Technology CDU - System Power Factor Server Technology CDU - System Total Power Server Technology CDU - System Watts per Area
Server Technology 3 Phase CDU - Infeeds (Script Based query)
Apparent Power (PIPS) Capacity Used (PIPS) Crest Factor (PIPS) Energy Consumption (PIPS) Load Phase Current (PIPS) Phase Voltage (PIPS) Power Power Factor (PIPS) Voltage
Server Technology CDU - Towers (SNMP Query)
Active Power (PIPS) Apparent Power (PIPS) Energy Consumption (PIPS) Line Frequency (PIPS) Percent Utilization (PIPS) Power Factor (PIPS)
Both Environmental Monitoring Queries are SNMP based and provide trending for attached Temperature/Humidity probes both from the CDU itself, or the optional EMCU-1-1B monitoring unit. The graph template includes a complex CDEF that will also plot the dew point on the graph given the temperature and humidity as inputs. Many thanks to Michael Burr for working out the RPN magic to make this CDEF possible.
Divide By 100 Divide By 10 Total All Data Sources Divide by 100 Divide By 10 and Convert Celsius to Fahrenheit Dew Point
It should be noted that some associated graph templates are listed explicitly with (PIPS) in the name. When using the templates with a CDU that does not support PIPS, do not create these graphs - they will end up being blank. POPS units assume all features of PIPS units. We do not utilize POPS units and thus I did not create templates with POPS functionality. I believe this would be a complete overload of information in most cases.
The graph templates and data templates are fully templated and use as much query data as possible to construct names and titles where appropriate. Make sure to name your infeeds and towers to make full use of this. I recommend naming towers after circuit IDs for best readability. Threshold data is also included and graphed on several of the templates. We did not choose to include threshold data on the temperature/humidity graph - but this can be added easily if desired.
If you were using the previous template set that I designed 4 years ago, please be careful upgrading to this set. Certainly a lot has changed, so collisions should be minimal. I believe the hash value for the temperature / humidity graph may remain the same - do during an upgrade your temperature graphs may be affected. I always recommend importing templates into a dev/test environment first to verify the correct behaviour.
Read the 'Upgrading' section if it applies to you. I would not recommend importing the included RRAs with this template set, and rather use your default. We use a very high resolution 1 Minute RRA for many of these data sources and a standard PIPS CDU can consume 1GB of RRD space. If this sounds attractive, by all means import our RRAs :) Either way, please take some time to review the set/heartbeat values for the data templates included in this set. We use a hybrid 1/5 minute poller so some data templates will have different step/heartbeat values depending upon whether we polled that data source at 1 minute or 5 minute intervals. IMHO it made no sense to poll kilowatt hours every minute, since it's a COUNTER type and increases slowly. These are the type of decisions you should consider before deploying any template into production, in general. If this terminology doesn't make sense please do not hesitate to contact me with questions - I am more than happy to help.
The nuts and bolts of installation is straightforward just like any other template set.
- Download and unzip the template set …
- copy query-servertech-infeeds-3ph.xml to $path_cacti/resource/script_queries
- copy query_servertech_infeed_3ph.php to $path_cacti/scripts/
- copy servertechnology-tower.xml to $path_cacti/resource/snmp_queries/
- copy servertechnology-env.xml to $path_cacti/resource/snmp_queries/
- copy servertechnology-env-emcu.xml to $path_cacti/resource/snmp_queries/
- import cacti_host_template_server_technology_3_phase_cdu.xml into Cacti.