similar to: snmp-ups shutdowns

Hi Jim, On Tue, 18 Feb 2014, Jim Klimov wrote: > Hello all, > > I was asked about a proper way to ensure powerfail shutdown of a blade > server fed off an APC SmartUPS, which is monitored by all hosts over > SNMP. In particular, they'd like to avoid the "untimely" return of > utility power - when the OSes are already shutting down, and would > stay down

On 2014-02-19 03:04, Tim Rice wrote: > If you've got a AP9630 card these notes may be useful. > > # APC ap9630 notes: > # Use firmware 6.0.6 or later if you want SNMPv3 > # Configuration->Shutdown > # In "Start of Shutdown" section, set "Low Battery Duration" and > # "Shutdown Delay" to get enough grace time for the ESXI shutdown > #

On 2014-02-27 14:21, Charles Lepple wrote: > On Feb 27, 2014, at 7:07 AM, jimklimov at cos.ru <mailto:jimklimov at cos.ru> > wrote: > >> This apparently implies that, unlike some docs say, the snmp-ups >> driver can send the shutdown signals (is not crippled by design)? ;) > > We're working on it: > >

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=".1.3.6.1.4.1.318.1.1.1.6.2.2.0 integer 3" > > # turn off UP gracefully (APC) (stays

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) >>>

On Feb 27, 2014, at 9:43 AM, Jim Klimov wrote: >>>>> # turn off UP gracefully (APC) (stays off even if power is restored) >>>>> #UPS_OID=".1.3.6.1.4.1.318.1.1.1.6.2.1.0 integer 3" >> >> This should map to the "shutdown.stayoff" instant command. > > And this means that the current code in the repository would not work > as

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? Thanks, //Jim Typos courtesy of my Samsung Mobile -------- ???????? ????????? -------- ??: Charles Lepple <clepple at gmail.com> ????: 2014.02.25 13:08 (GMT+01:00) ????:

On Feb 27, 2014, at 7:07 AM, jimklimov at cos.ru wrote: > This apparently implies that, unlike some docs say, the snmp-ups driver can send the shutdown signals (is not crippled by design)? ;) We're working on it: http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/docs/man/snmp-ups.html#_shutdown A quick check says that the implementation has been there since v2.6.4, and

Updating an old thread. History here. http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-January/006391.html http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006394.html http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006398.html On Fri, 1 Feb 2013, Tim Rice wrote: [snip] > > In all my testing I discovered the APC AP9630 is kind of flaky when >

nut-2.6.5 Scientific Linux 6.3 APC AP9630 management card My basic question is, does nut's SNMPv3 implementation work? I have this in /etc/ups/ups.conf ...... [tfapc01] driver = snmp-ups port = tfapc01.testfest.ixorg.org mibs = apcc snmp_version = v3 secLevel = authPriv secName = tfsnmpprof1 authPassword = ralow6moHet7zoboP8 privPassword = tuseL8Pakaz9degim7 authProtocol=MD5

Hello: I have APC AP9630 UPS, use nut, but the execution failed, my ups.conf setting right? thank! nut2.7.3 net-snmp5.2.1 openssl0.9.8 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20160419/032eedd5/attachment.html> -------------- next part -------------- A non-text attachment was

(Note that I mentioned this *was* previously working with an older version of Nut). [irs2-ups1] driver = snmp-ups port = irs2-ups1.sum.naoj.org mibs = auto community = private irs2-ups1.sum.naoj.org responds to pings. On Tue, Oct 8, 2013 at 3:55 PM, Tim Rice <tim at multitalents.net> wrote: > On Tue, 8 Oct 2013, Philip Tait wrote: > > > Here is the upsc

This is slightly off-topic, I guess, but I'm not sure who better to ask for help. I'm active within the FreeNAS community and involved in their (FreeBSD based) documentation work. There is a long standing bug ticket - years old now - to update their "network ups tools" docs page, to cover Ethernet attached UPS that use nut for the link. Currently the docs mainly describes

Here is the upsc output: # /usr/local/ups/bin/snmp-ups -DD -a irs2-ups1 Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) 0.000000 debug level is '2' 0.000327 SNMP UPS driver : entering upsdrv_initups() 0.000341 SNMP UPS driver : entering nut_snmp_init(snmp-ups) 0.056112 SNMP UPS driver : entering load_mib2nut(auto) 0.056126 trying the new

On Tue, 8 Oct 2013, Philip Tait wrote: > Here is the upsc output: > > # /usr/local/ups/bin/snmp-ups -DD -a irs2-ups1 > Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) > 0.000000 debug level is '2' > 0.000327 SNMP UPS driver : entering upsdrv_initups() [snip] > 4.457750 No supported device detected I'm using a APC smart ups with a

Hello again! Your suggestions the other day did work so thank you! I do have one more question for you guys though. APC AP9630 SNMP monitoring card is listed in the HCL and next to it there is privProtocol = AES. Does this mean only AES works or AES doesn't work? I saw the archived mailing lists were it looked like it only worked with the AES protocol, though in my set up it works with

Hello One our customer has two Linux HP-branded servers powered from "clasic" APC Smart-UPS 2200 RM 2U (p/n SUA2200RMI2U). It is connected to first server via RS232c port with APC-branded cable. We have installed NUT 2.6.4 with apcsmart driver. This setup works fine for months. Two weeks ago all the hardware powered from the UPS started to switch off occasionally while on line

I'm in the process of trying to get NUT to manage an APC SmartUPS. Monitoring of the UPS is working fine: $ upsc nutdev1 at localhost Init SSL without certificate database ambient.1.humidity.alarm.high: 60.00 ambient.1.humidity.alarm.low: 30.00 ambient.1.temperature.alarm.high: 40.00 ambient.1.temperature.alarm.low: 10.00 battery.charge: 94.00 battery.charge.restart: 0 battery.current: 0.00

On Mar 30, 2014, at 10:39 PM, Shade Alabsa wrote: > Hello again! Your suggestions the other day did work so thank you! I do have one more question for you guys though. APC AP9630 SNMP monitoring card is listed in the HCL and next to it there is privProtocol = AES. Does this mean only AES works or AES doesn't work? I saw the archived mailing lists were it looked like it only worked with the

I'm trying to get SNMPv3 management working for an APC AP9617 card. It is newly refurbed, running sumx v3.7.2 and aos v3.7.3. In the SNMPv3 user profiles section I have (I don't care about the password leaking, it's temporary): User Name: nut Authentication Passphrase: NutScan at Password43LongerWord Privacy Passphrase: NutScan at Password43LongerWord Authentication protocol: