[Nut-upsuser] APC AP9617 SNMP returns strange errors

lutz.niederer at gmx.net lutz.niederer at gmx.net
Wed May 15 08:16:24 UTC 2013


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 2.6.4
   0.000000
If you're not a NUT core developer, chances are that you're told to enable debugging [...]
   0.000280     Shutdown UPS: apc10001
   0.000304     exec:  /lib/nut/snmp-ups -a apc10001 -k
Network UPS Tools - Generic SNMP UPS driver 0.66 (2.6.4)
Detected Smart-UPS 1000 on host 10.100.200.30 (mib: apcc 1.1)
Initiating UPS shutdown
[apc10001] nut_snmp_set: can't set .1.3.6.1.4.1.318.1.1.1.6.1.1.0: Error in packet: (genError) A general failure occured
Shutdown failed!
   0.099067     Driver failed to start (exit status=1)

If I use upscmd for shutdown it says "OK" but does nothing.
I sent an snmp command directly to the ups (1.3.6.1.4.1.318.1.1.1.6.2.1 i 2) and the ups turned off as expected.  

I tried to set values via upsset.cgi in the ups and see the following in the logs even if the cgi says "ok":
May 15 09:54:30 abex upsd[7788]: Set variable: admin at 10.100.200.1 set battery.charge.restart on apc10001 to 90
May 15 09:54:30 abex snmp-ups[7785]: [apc10001] nut_snmp_set: can't set .1.3.6.1.4.1.318.1.1.1.5.2.6.0: Error in packet: (badValue) The value given has the wrong type or length.

But I can read that value correctly.  We cannot set any values but read them all.  community is ok as I can see auth messages in the ups if I use the wrong community.  When get those errors above, I do not see any errors in the UPS' logs.

I have no clue what's happening here.  I can see this on both UPS which have 1kVA and 1.5kVA and AP9617 (that is the same as AP9618 that is supported with the exception of env montoring).

We are using Debain wheezy (not yet the stable) and nut 2.6.4-1 and snmp-stuff 5.4.3-dfsg-2.5.

Is there someone who can help, please?!

Thanks a lot,
-lutzn



More information about the Nut-upsuser mailing list