And this is the tcpdump output from the snmp-ups command:
15:22:22.063065 IP 10.100.200.1.43571 > 10.100.200.30.161: C=private GetRequest(34) .1.3.6.1.4.1.318.1.1.1.1.1.1.0
15:22:22.080085 IP 10.100.200.30.161 > 10.100.200.1.43571: C=private GetResponse(52) .1.3.6.1.4.1.318.1.1.1.1.1.1.0="Smart-UPS 1000"
15:22:22.080286 IP 10.100.200.1.43571 > 10.100.200.30.161: C=private GetRequest(34) .1.3.6.1.4.1.318.1.1.1.1.1.1.0
15:22:22.098435 IP 10.100.200.30.161 > 10.100.200.1.43571: C=private GetResponse(52) .1.3.6.1.4.1.318.1.1.1.1.1.1.0="Smart-UPS 1000"
15:22:22.098717 IP 10.100.200.1.43571 > 10.100.200.30.161: C=private SetRequest(35) .1.3.6.1.4.1.318.1.1.1.6.1.1.0=2
15:22:22.135136 IP 10.100.200.30.161 > 10.100.200.1.43571: C=private GetResponse(35) genErr@1 .1.3.6.1.4.1.318.1.1.1.6.1.1.0=2
15:22:22.080085 IP 10.100.200.30.161 > 10.100.200.1.43571: C=private GetResponse(52) .1.3.6.1.4.1.318.1.1.1.1.1.1.0="Smart-UPS 1000"
15:22:22.080286 IP 10.100.200.1.43571 > 10.100.200.30.161: C=private GetRequest(34) .1.3.6.1.4.1.318.1.1.1.1.1.1.0
15:22:22.098435 IP 10.100.200.30.161 > 10.100.200.1.43571: C=private GetResponse(52) .1.3.6.1.4.1.318.1.1.1.1.1.1.0="Smart-UPS 1000"
15:22:22.098717 IP 10.100.200.1.43571 > 10.100.200.30.161: C=private SetRequest(35) .1.3.6.1.4.1.318.1.1.1.6.1.1.0=2
15:22:22.135136 IP 10.100.200.30.161 > 10.100.200.1.43571: C=private GetResponse(35) genErr@1 .1.3.6.1.4.1.318.1.1.1.6.1.1.0=2
What don't understand is that many people are using this card or the AP9618 card...
None of them should have been able to set those values or had the ups shutdown successfully. Strange.....
-lutzn
On May 15, 2013, at 8:50 AM, lutz.niede...@gmx.net wrote:
> I tried to set "Minimum battery level for restart after power off (percent)" to 90. And this gave "90" as mentioned below. I saw in apc-mib.c that the type for this is declared as ST_FLAG_STRING. This is abolutely no string (so no 's' but 'i' would be correct).
I agree with that assessment, but what about the error for the following call?
0.055771 entering nut_snmp_set (.1.3.6.1.4.1.318.1.1.1.6.1.1.0, i, 2)
0.098838 [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
That seems to be specifying an integer, which agrees with this:
<http://www.mibdepot.com/cgi-bin/getmib3.cgi?win=mib_a&i=1&n=PowerNet-MIB&r=dell&f=powernet.mib&v=v1&t=sca&o=upsBasicControlConserveBattery>
Does this call to nut_snmp_set() not result in a proper packet as seen in tcpdump?
Since you're using Debian, and this bug would be present in the latest package version as well, I would recommend filing a bug there (and post a link to the bug here). That will make sure it doesn't fall through the cracks. We can continue to debug here as well.
It is also possible to compile NUT from source with the same options that Debian uses, and just swap in the snmp-ups driver for testing.
--
Charles Lepple
clepple@gmail
> I tried to set "Minimum battery level for restart after power off (percent)" to 90. And this gave "90" as mentioned below. I saw in apc-mib.c that the type for this is declared as ST_FLAG_STRING. This is abolutely no string (so no 's' but 'i' would be correct).
I agree with that assessment, but what about the error for the following call?
0.055771 entering nut_snmp_set (.1.3.6.1.4.1.318.1.1.1.6.1.1.0, i, 2)
0.098838 [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
That seems to be specifying an integer, which agrees with this:
<http://www.mibdepot.com/cgi-bin/getmib3.cgi?win=mib_a&i=1&n=PowerNet-MIB&r=dell&f=powernet.mib&v=v1&t=sca&o=upsBasicControlConserveBattery>
Does this call to nut_snmp_set() not result in a proper packet as seen in tcpdump?
Since you're using Debian, and this bug would be present in the latest package version as well, I would recommend filing a bug there (and post a link to the bug here). That will make sure it doesn't fall through the cracks. We can continue to debug here as well.
It is also possible to compile NUT from source with the same options that Debian uses, and just swap in the snmp-ups driver for testing.
--
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
