Ok, and here comes the tcp dump:
 
snmpset -c private -v 1 10.100.200.30 1.3.6.1.4.1.318.1.1.1.5.2.6.0 i 90  makes this:
14:01:02.725830 IP 10.100.200.1.40893 > 10.100.200.30.161:  C=private SetRequest(35)  .1.3.6.1.4.1.318.1.1.1.5.2.6.0=90
14:01:02.759972 IP 10.100.200.30.161 > 10.100.200.1.40893:  C=private GetResponse(35)  .1.3.6.1.4.1.318.1.1.1.5.2.6.0=90
 
and the same with upsset.cgi makes this:
13:58:40.196924 IP 10.100.200.1.38704 > 10.100.200.30.161:  C=private SetRequest(36)  .1.3.6.1.4.1.318.1.1.1.5.2.6.0="90"
13:58:40.223239 IP 10.100.200.30.161 > 10.100.200.1.38704:  C=private GetResponse(36)  badValue@1 .1.3.6.1.4.1.318.1.1.1.5.2.6.0="90"
 
So maybe a problem with "90" vs 90 ?
 
 
On May 15, 2013, at 4:16 AM, lutz.niede...@gmx.net wrote:

> root@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

The message that you trimmed was intended to explain that if you want more debug messages, you need to call the driver directly with the -D flags, e.g. "/lib/nut/snmp-ups -DDDD -a apc10001 -k".

Unfortunately, I am not familiar with the inner workings of the SNMP driver.

--
Charles Lepple
clepple@gmail


 
_______________________________________________
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Reply via email to