similar to: placement of ups shutdown command for snmp systems

Hi, we do have APC Smart-UPS each with AP9617 and latest FW. As we found out we are not able to shutdown the UPS via SNMP - neither immediately nor delayed. And we cannot set values, but we can read them correctly. So it seems as we are not able to write to the UPS and get back strange errors. root at abex:/etc/nut# upsdrvctl -DDDD shutdown apc10001 Network UPS Tools - UPS driver controller

Hi! ? I have several mbox files (unstructured, only the big?plain mbox?files) and I would like to integrate/read these mbox files into mdbox subfolders of specific users.? This is a production system and I don't want to disturb running services and I am a bit afraid of not using the right command and maybe destroying (or whatever) their mailboxes.? I am sure it is pretty easy.? Can someone

Hallo, I have one ups with snmp and any ups without snmp. Shutdown works while network online. But some batteries are empty, so that the communication break early. Howto force shutdown if nut-snmp Communications lost? My 1. suggestion was option DEADTIME, but seem to be information only. (s. below) Any suggestions? The last way would be a ugly cronjob (like: ping || shutdown). regards Heiko

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

I've googled and RTFM'ed, but still can't solve this one. I hope you folks can. This affects my entire computer cluster, but let's start simple: I've got a computer running NUT; OS is Scientific Linux 5.5; kernel 2.6.18-274.12.1.el5xen. It connects to an APC SMART-UPS via an APC SmartCard using the snmp-ups driver. It generally works: upsmon will detect if the battery is low

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

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

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

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

> >>> where in the filesystem should I be looking for the NUT shutdown script please? >> >> It's the SHUTDOWNCMD in upsmon.conf Excellent. And in my case (default) it says SHUTDOWNCMD "/sbin/shutdown -h +0" I have tried that command and, as expected, it has shut down the pc. Then I have disconnected the power cord for one minute and plugged it back in,

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 because the UPS is well-fed now and thus won't power off and later power on to boot

On Sep 3, 2014, at 9:38 AM, Heiko L. <HL at fh-lausitz.de> wrote: > Howto force shutdown if nut-snmp Communications lost? > > My 1. suggestion was option DEADTIME, but seem to be information only. (s. below) DEADTIME expiration is a critical condition if the UPS is on battery when comms are lost, otherwise you are correct, it is only informative. What about a NOTIFYCMD script

Hi David On 4/29/20 3:28 PM, David Zomaya wrote: > Is NUT using the same SNMP v3 user as your SNMP Set or a different one? > > If it is a different one (e.g. an SNMP v1 or v2c string) does that user > / community string have read/write access? I tried setting them all with -x thing= arguments as well as letting it pull from ups.conf, same result. It's all SNMPv3 settings. sudo

Is anyone using snmp-ups with the -k option successfully? This is really starting to look like a bug somewhere in nut, not a config problem. I've just tried the same command from a FBSD box with the same unfortunate result. Mind you, it could be the UPS card, I'm using the same one for both tests. : || nomad at castle nut-2.7.4 [93] ; please drivers/snmp-ups -a nutdev1 -x

Hello there I am new to NUT I am trying to monitor an APC smart-UPS with nut. I'd like to use the ethernet with SNMP (as opposed to serial port) because it's faster and it doesn't need to authenticate with user/pwd. The snmp-ups works with our APC, however I noticed a significant problem: If snmp-ups is started when the UPS is not reachable (e.g. we have a slow switch that drops

Is this the best place to get into contact with the snmp-ups driver developers? I am trying to get the snmp-ups driver to work with a Liebert GXT2 UPS, and it works for knowing when it goes on battery and such, but when it comes to shutting down the Liebert UPS, it doesn't work. Any suggestions or docs that I need to read? -- Ronald Reed Manager of Computer Operations ARM SGP ACRF Site

On Feb 13, 2014, at 10:49 PM, ??? ????? wrote: > Slightly changed the list, took from running snmptranslate for all parameters: > snmptranslate -IR -On upsBaseIdentModel upsBaseBatteryStatus upsSmartBatteryCapacity upsSmartBatteryTemperature upsSmartInputLineVoltage upsBaseOutputStatus upsSmartOutputVoltage upsSmartOutputFrequency upsSmartOutputLoad upsSmartControlUpsOff