search for: privprotocol

...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

Hello again! Your suggestions the other day did work so thank you! I do have one more question for you guys though. APC AP9630 SNMP monitoring card is listed in the HCL and next to it there is privProtocol = AES. Does this mean only AES works or AES doesn't work? I saw the archived mailing lists were it looked like it only worked with the AES protocol, though in my set up it works with everything else but AES. Just want to verify which one is correct. Thanks! Shade -------------- next part -----...

...: 27.00 battery.voltage.nominal: -1.00 device.mfr: APC device.model: SMART-UPS 1400 device.serial: WS9831004667 device.type: ups driver.name: snmp-ups driver.parameter.authProtocol: MD5 driver.parameter.mibs: apcc driver.parameter.pollinterval: 2 driver.parameter.port: 192.5.37.191 driver.parameter.privProtocol: DES driver.parameter.secLevel: authPriv driver.parameter.synchronous: no driver.version: 2.7.4 driver.version.data: apcc MIB 1.2 driver.version.internal: 0.97 input.frequency: 60.00 input.sensitivity: high input.transfer.high: 132 input.transfer.low: 103 input.transfer.reason: selfTest input.volta...

On Mar 30, 2014, at 10:39 PM, Shade Alabsa wrote: > Hello again! Your suggestions the other day did work so thank you! I do have one more question for you guys though. APC AP9630 SNMP monitoring card is listed in the HCL and next to it there is privProtocol = AES. Does this mean only AES works or AES doesn't work? I saw the archived mailing lists were it looked like it only worked with the AES protocol, though in my set up it works with everything else but AES. Just want to verify which one is correct. Thanks! We rely on mailing list reports for...

...c string) does that user > / community string have read/write access? I tried setting them all with -x thing= arguments as well as letting it pull from ups.conf, same result. It's all SNMPv3 settings. sudo snmp-ups -DDDD -a nutdev1 -x secLevel=authPriv -x secName=nut -x authProtocol=MD5 -x privProtocol=DES -x authPassword=NutScan at Password43LongerWord -x privPassword=NutScan at Password43LongerWord -k The output with -DDDD is the same either way. > tcpdump to listen for packets across UDP 161 is one way to check what is > actually being sent. I guess that really is the next step, isn...

...s SNMPv3 implementation work? I have this in /etc/ups/ups.conf ...... [tfapc01] driver = snmp-ups port = tfapc01.testfest.ixorg.org mibs = apcc snmp_version = v3 secLevel = authPriv secName = tfsnmpprof1 authPassword = ralow6moHet7zoboP8 privPassword = tuseL8Pakaz9degim7 authProtocol=MD5 privProtocol=AES desc = "APC SU700 SNMP v3 device, with the highest security level" ...... Now I test /sbin/snmp-ups -DDD -a tfapc01 Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) 0.000000 debug level is '3' 0.000600 SNMP UPS driver : entering upsdrv_initups() 0.000618 SNM...

...option other than none) Privacy Protocol: DES (only option other than none) In access control I've enabled user nut. However, when I try to use nut-scanner on it: $ nut-scanner -S -s apcups --secLevel authPriv --secName nut --authProtocol MD5 --authPassword NutScan at Password43LongerWord --privProtocol DES --privPassword NutScan at Password43LongerWord Scanning SNMP bus. Error: unknown authtypeError generating Ku from authentication pass phrase snmpwalk gives a different error: $ snmpwalk -v 3 -u nut apcups -x DES -X NutScan at Password43LongerWord -a MD5 -A NutScan at Password43LongerWord snmpw...

...EL I downloaded the source and compiled for myself with the exact same result. nomad -------------- next part -------------- Script started on 2020-05-04 09:19:50-07:00 ]0;lvd at chscc-pc-052:~: || lvd at chscc-pc-052 ~ [936] ; nut-scanner -S --secLevel authPriv --secName nut --authProtocol MD5 --privProtocol DES --authPassword NutScan at P Password43LongerWord --privPassword NutScan at Password43LongerWord -s apcups Scanning SNMP bus. Error: unknown authtypeError generating Ku from authentication pass phrase ]0;lvd at chscc-pc-052:~: || lvd at chscc-pc-052 ~ [937] ; please snmp-ups -DDDD -a nutdev1 -x...

...Y_iS-v_t9g8PHVkn8Px_wyaupZGfQ&m=VdKSS_Vk98WT0ADZ-mQe_3zCfrLacAAuMS7JSj5wn1w&s=hM67G_Mcn7oW5yo4o44Na9wyw26mxM8hKXFExeGyhJQ&e=>: snmp-ups driver.parameter.authProtocol: MD5 driver.parameter.mibs: apcc driver.parameter.pollinterval: 2 driver.parameter.port: 192.5.37.191 driver.parameter.privProtocol: DES driver.parameter.secLevel: authPriv driver.parameter.synchronous: no driver.version: 2.7.4 driver.version.data: apcc MIB 1.2 driver.version.internal: 0.97 input.frequency: 60.00 input.sensitivity: high input.transfer.high: 132 input.transfer.low: 103 input.transfer.reason: selfTest input.volta...

...ot;APC Smart-UPS 5000 SNMP in rack 1 - AP9617" driver = snmp-ups mibs = apcc port = [ups1...] # snmp_version = v1 # community = [xxx] snmp_version = v3 secLevel = authPriv secName = [xxx] authPassword = [xxx] authProtocol = MD5 privPassword = [xxx] privProtocol = DES [ups2] desc = "APC Smart-UPS 5000 SNMP in rack 2 - AP9619" driver = snmp-ups mibs = apcc port = [ups2...] snmp_version = v1 community = [xxx] # snmp_version = v3 # secLevel = authPriv # secName = [xxx] # authPassword = [xxx] # authProtocol = M...

...y.packs: 1.00 battery.runtime: 2974.00 battery.runtime.low: 120 battery.voltage: 135.00 device.mfr: APC device.model: Smart-UPS X 3000 device.serial: <obfuscated> device.type: ups driver.name: snmp-ups driver.parameter.pollinterval: 2 driver.parameter.port: <obfuscated> driver.parameter.privProtocol: AES driver.version: 2.7.1 driver.version.data: apcc MIB 1.2 driver.version.internal: 0.70 input.frequency: 60.00 input.sensitivity: low input.transfer.high: 136 input.transfer.low: 97 input.transfer.reason: blackout input.voltage: 120.30 input.voltage.maximum: 121.00 input.voltage.minimum: 120.30...

...Port: ups6.domain.name (also tried 192.168.24.9)                 Snmp_version = v3                 secLevel = authPriv                 secName = ups6                 authPassword = PASSWORDSTRING                 authProtocol = MD5                 privPassword = PASSWORDSTRING                 privProtocol = AES                 pollfreq = 15                 desc = “apc ups” But when I run the service, I get this error # /usr/sbin/upsdrvctl start Network UPS Tools – UPS driver controller 2.7.2 Network UPS Tools – Generic SNMP UPS driver 0.72 (2.7.2) No support device detected Driver f...

...option other than none) Privacy Protocol: DES (only option other than none) In access control I've enabled user nut. However, when I try to use nut-scanner on it: $ nut-scanner -S -s apcups --secLevel authPriv --secName nut --authProtocol MD5 --authPassword NutScan at Password43LongerWord --privProtocol DES --privPassword NutScan at Password43LongerWord Scanning SNMP bus. Error: unknown authtypeError generating Ku from authentication pass phrase snmpwalk gives a different error: $ snmpwalk -v 3 -u nut apcups -x DES -X NutScan at Password43LongerWord -a MD5 -A NutScan at Password43LongerWord snmpw...

...I've just tried the same command from a FBSD box with the same unfortunate result. Mind you, it could be the UPS card, I'm using the same one for both tests. : || nomad at castle nut-2.7.4 [93] ; please drivers/snmp-ups -a nutdev1 -x secLevel=authPriv -x secName=nut -x authProtocol=MD5 -x privProtocol=DES -x authPassword=NutScan at Password43LongerWord -x privPassword=NutScan at Password43LongerWord -k Network UPS Tools - Generic SNMP UPS driver 0.97 (2.7.4) No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.2.10'! Please report it to NUT developers, with an 'upsc' output for...

Hi, Every time that I have to restart the nut-server it's a nightmare. For example, after editing ups.conf In many cases the only "solution" is to reboot the system. These are the errors: systemctl -l status nut-driver ? nut-driver.service - Network UPS Tools - power device driver controller Loaded: loaded (/usr/lib/systemd/system/nut-driver.service; static; vendor preset:

...snmp_version = v3 secLevel = authPriv # 4 lowercase ascii letters secName = xxxx # # 16 lower case ascii letters authPassword = xxxxxxxxxxxxxxxx # 15 lower case ascii letters privPassword = yyyyyyyyyyyyyyy authProtocol = SHA privProtocol = AES [..] * driver debug output and tcpdump attached in nuttrace & nut.pcap Searching for 9630 i found some similar reports to mailing list nut-upsuser from 2013, 2014 and 2016 indicating that others have this problem too. The oldest report suggests to use DES instead of AES which kinda w...