<div dir="ltr">Hi Tim<br><div class="gmail_extra"><br><br><div class="gmail_quote">2013/8/22 Tim Rice <span dir="ltr"><<a href="mailto:tim@multitalents.net" target="_blank">tim@multitalents.net</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Updating an old thread. History here.<br>
<a href="http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-January/006391.html" target="_blank">http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-January/006391.html</a><br>
<a href="http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006394.html" target="_blank">http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006394.html</a><br>
<a href="http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006398.html" target="_blank">http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006398.html</a><br>
<div class="im"><br>
On Fri, 1 Feb 2013, Tim Rice wrote:<br>
<br>
[snip]<br>
><br>
</div>> In all my testing I discovered the APC AP9630 is kind of flaky when<br>
<div class="im">> it comes to SNMP v3.<br>
> I have<br>
> snmpget -Cf -v 3 -u tfsnmpprof1 -l authPriv \<br>
> -a MD5 -A ralow6moHet7zoboP8 \<br>
> -x AES -X tuseL8Pakaz9degim7 \<br>
> tfapc01 .1.3.6.1.4.1.318.1.1.1.1.1.1.0<br>
> work one day and the next day fail.<br>
><br>
> So I will revisit SNMP v3 when I get my hands on a non APC ups that<br>
> supports SNMP v3.<br>
><br>
> Thanks for all your help.<br>
><br>
> A note for the archives: To get snmpget working I had to rename the<br>
> v3 profile I had set up on the APC and create a new one with all the same<br>
> info. Then it worked.<br>
> When it stopped working (when I came back to it days later) , I renamed<br>
> that one and set up a third one again with all the same info. Once again<br>
> it started working. Strange.<br>
<br>
</div>APC has released new firmware (v6.0.6) for the ap9630 card.<br>
With snmpget now working correctly even after rebooting the ap9630 card I<br>
attempted to get NUT to talk to it.<br>
<br>
Doing a "/sbin/snmp-ups -D -D -D -D -a tfapc01" produced<br>
<div class="im">Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5)<br>
</div> 0.000000 debug level is '4'<br>
0.000385 SNMP UPS driver : entering upsdrv_initups()<br>
0.000402 SNMP UPS driver : entering nut_snmp_init(snmp-ups)<br>
0.044948 SNMP UPS driver : entering load_mib2nut(apcc)<br>
0.044957 load_mib2nut: trying classic method with 'apcc' mib<br>
0.044961 Entering nut_snmp_get_str()<br>
0.044965 nut_snmp_get(.1.3.6.1.4.1.318.1.1.1.1.1.1.0)<br>
0.051353 Unknown mibs value: apcc<br>
<br>
<br>
Now in the months between the last post and this, I had the opportunity<br>
to successfully test SNMPv3 using an Eaton Network Card-MS in an<br>
evolution 850. Now what was different (besides all the hardware).<br>
I remembered that the Eaton card did not have the option of using AES<br>
for the privProtocol. So I changed the privProtocol from AES to DES<br>
and updated usp.conf and now NUT seems willing to talk to the ap9630.<br>
<br>
So we've got a problem setting privProtocol = AES<br>
<br>
Now to do my power fail / shutdown testing.</blockquote><br></div><div class="gmail_quote">thanks for updating us, much appreciated.<br></div><div class="gmail_quote">I've just committed an HCL entry:<br><a href="https://github.com/networkupstools/nut/commit/7ab6c65872f663eefa9c6cd0fc73942c3540b5b8">https://github.com/networkupstools/nut/commit/7ab6c65872f663eefa9c6cd0fc73942c3540b5b8</a><br>
<br></div><div class="gmail_quote">Let us know how the shutdown testing has gone.<br><br></div><div class="gmail_quote">cheers,<br>Arno<br></div></div></div>