[Nut-upsdev] snmp-ups shutdowns

jimklimov at cos.ru jimklimov at cos.ru
Thu Feb 27 12:07:21 UTC 2014

This apparently implies that, unlike some docs say, the snmp-ups driver can send the shutdown signals (is not crippled by design)? ;)

Also, are those oids apc-private or commonly used/standard among snmp upses?


Typos courtesy of my Samsung Mobile

-------- Исходное сообщение --------
От: Charles Lepple <clepple at gmail.com> 
Дата: 2014.02.25  13:08  (GMT+01:00) 
Кому: nut-upsdev at lists.alioth.debian.org 
Тема: Re: [Nut-upsdev] snmp-ups shutdowns 
On Feb 19, 2014, at 11:18 AM, Tim Rice wrote:

> On Wed, 19 Feb 2014, Jim Klimov wrote:
>> On 2014-02-19 03:04, Tim Rice wrote:
>>> Now here are the OIDs (pick one) to actually turn the UPS off
>>> after the shutdown delay.
>>> # reboot gracefully (APC) (stays off until utility power is restored)
>>> UPS_OID=". integer 3"

This OID is curiously commented out in drivers/apc-mib.c, and has been since the beginning of our revision control history. I don't see why we couldn't add it back in as an instant command.

I wonder if there was some confusion with . (upsBasicControlConserveBattery), which is currently mapped to "shutdown.return"

>>> # turn off UP gracefully (APC) (stays off even if power is restored)
>>> #UPS_OID=". integer 3"

This should map to the "shutdown.stayoff" instant command.

Charles Lepple
clepple at gmail

Nut-upsdev mailing list
Nut-upsdev at lists.alioth.debian.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20140227/a904b8d7/attachment.html>

More information about the Nut-upsdev mailing list