[Nut-upsdev] SNMPv3

[Tim Rice]

Updating an old thread. History here.
http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-January/006391.html
http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006394.html
http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006398.html

On Fri, 1 Feb 2013, Tim Rice wrote:

[snip]
> 
> In all my testing I discovered the APC AP9630 is kind of flaky when
> it comes to SNMP v3.
> I have 
>    snmpget -Cf -v 3 -u tfsnmpprof1 -l authPriv \
>    -a MD5 -A ralow6moHet7zoboP8 \
>    -x AES -X tuseL8Pakaz9degim7 \
>    tfapc01 .1.3.6.1.4.1.318.1.1.1.1.1.1.0
> work one day and the next day fail.
> 
> So I will revisit SNMP v3 when I get my hands on a non APC ups that
> supports SNMP v3.
> 
> Thanks for all your help.
> 
> A note for the archives: To get snmpget working I had to rename the
> v3 profile I had set up on the APC and create a new one with all the same
> info. Then it worked.
> When it stopped working (when I came back to it days later) , I renamed
> that one and set up a third one again with all the same info. Once again
> it started working.  Strange.

APC has released new firmware (v6.0.6) for the ap9630 card.
With snmpget now working correctly even after rebooting the ap9630 card I
attempted to get NUT to talk to it.

Doing a "/sbin/snmp-ups  -D -D -D -D -a tfapc01" produced
Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5)
   0.000000     debug level is '4'
   0.000385     SNMP UPS driver : entering upsdrv_initups()
   0.000402     SNMP UPS driver : entering nut_snmp_init(snmp-ups)
   0.044948     SNMP UPS driver : entering load_mib2nut(apcc)
   0.044957     load_mib2nut: trying classic method with 'apcc' mib
   0.044961     Entering nut_snmp_get_str()
   0.044965     nut_snmp_get(.1.3.6.1.4.1.318.1.1.1.1.1.1.0)
   0.051353     Unknown mibs value: apcc


Now in the months between the last post and this, I had the opportunity
to successfully test SNMPv3 using an Eaton Network Card-MS in an
evolution 850. Now what was different (besides all the hardware).
I remembered that the Eaton card did not have the option of using AES
for the privProtocol. So I changed the privProtocol from AES to DES
and updated usp.conf and now NUT seems willing to talk to the ap9630.

So we've got a problem setting privProtocol = AES

Now to do my power fail / shutdown testing.

-- 
Tim Rice				Multitalents	(707) 456-1146
tim at multitalents.net