snmp-ups (8) - Linux Man Pages
snmp-ups: Multi-MIB Driver for SNMP UPS equipment
snmp-ups - Multi-MIB Driver for SNMP UPS equipment
This man page only documents the hardware-specific features of the snmp-ups driver. For information about the core driver, see nutupsdrv(8).
The snmp-ups driver automatically detects and supports a wide range of devices by loading various MIBS:
- UPS that is RFC 1628 (UPS MIB) compliant, e.g. MGE UPS SYSTEMS, Liebert, perhaps others (default)
- MGE UPS SYSTEMS and MGE Office Protection Systems devices with SNMP cards (ref 66062, 66045, 66074 and 66244)
- APC AP9605, AP9606, AP9617, and AP9618 APC network management cards, as well as any others supporting the APC POWERNET MIB
- Socomec Sicon UPS with Netvision Web/SNMP management card/external box
- Powerware devices with ConnectUPS SNMP cards
- Eaton Powerware ePDU Monitored
- Eaton Powerware ePDU Managed
- Various Raritan PDUs
- Various BayTech PDUs
- HP/Compaq AF401A management card, perhaps others
- Cyberpower RMCARD201. Should also support RMCARD100 (net version), RMCARD202 and RMCARD301
This driver supports the following optional settings in the ups.conf(5):
- Set MIB compliance (default=auto, allowed entries: refer to SUPPORTED HARDWARE above). With "auto", the driver will try a select set of SNMP objects until it finds one that the device responds to. Note that since NUT 2.6.2, snmp-ups has a new method that uses sysObjectID (which is a pointer to the prefered MIB of the device) to detect supported devices. This renders void the use of "mibs" option.
- Set community name (default = public). Note that a RW community name is required to change UPS settings (as for a powerdown).
- Set SNMP version (default = v1, allowed: v2c, v3)
- Set polling frequency in seconds, to reduce network flow (default=30)
- Disable the monitoring of the low and high voltage transfer OIDs in the hardware. This will remove input.transfer.low and input.transfer.high from the list of variables. This should only be used on APCC Symmetra equipment which has strangeness in the three-phase power reporting.
- Set the securityLevel used for SNMPv3 messages (default=noAuthNoPriv, allowed: authNoPriv,authPriv)
- Set the securityName used for authenticated SNMPv3 messages (no default)
- Set the authentication pass phrase used for authenticated SNMPv3 messages (no default)
- Set the privacy pass phrase used for encrypted SNMPv3 messages (no default)
- Set the authentication protocol (MD5 or SHA) used for authenticated SNMPv3 messages (default=MD5)
- Set the privacy protocol (DES or AES) used for encrypted SNMPv3 messages (default=DES)
You will need to install the Net-SNMP package from http://www.net-snmp.org/ before building this driver.
SNMP v3 also requires OpenSSL support from http://www.openssl.org.
The shutdown sequence should be tested before relying on NUT to send a shutdown command to the UPS. The problem is that the host network stack may have been torn down by the time the driver is invoked to send the shutdown command. The driver attempts to send shutdown.return, shutdown.reboot, and load.off.delay commands to the UPS in sequence, stopping after the first supported command.
The hostname of the UPS is specified with the "port" value in ups.conf:
[snmpv1] driver = snmp-ups port = snmp-ups.example.com community = public snmp_version = v1 pollfreq = 15 desc = "Example SNMP v1 device"
[snmpv3] driver = snmp-ups port = 188.8.131.52 snmp_version = v3 secLevel = authPriv secName = mysecurityname authPassword = myauthenticationpassphrase privPassword = myprivatepassphrase desc = "Example SNMP v3 device, with the highest security level"