After firmware upgrade snmp-ups unable to get values from APC SMART UPS network card AOS AP9617 about nut HOT 10 OPEN

Seems you have a typo:

0.022477 [D2] load_mib2nut: skip the "apc" entry from the mapping table which is not "apcc" (and which in turn is not "auto")

from nut.

Hm, this is from snmp-ups -DD output using my [apcv3] config. Nothing I wrote ... (hence whose typo is it)

from nut.

Try mibs=apc (not apcc).

from nut.

with mibs = apc the result is still:

root@db3:/download/nut# snmp-ups -DD -a apcv3
Network UPS Tools - Generic SNMP UPS driver 1.30 (2.8.1)
...
0.323917 Requested 'mibs' value 'apc' did not match this device [apcv3] (host 192.168.100.220)
0.324026 upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it

root@db3:/etc/nut# systemctl status nut-driver

• nut-driver.service - Network UPS Tools - power device driver controller
  Loaded: loaded (/lib/systemd/system/nut-driver.service; static)
  Active: failed (Result: exit-code) since Tue 2023-12-19 20:34:57 CET; 1min 28s ago
  Process: 2710515 ExecStart=/sbin/upsdrvctl start (code=exited, status=1/FAILURE)
  CPU: 27ms

Dec 19 20:34:57 db3 systemd[1]: Starting Network UPS Tools - power device driver controller...
Dec 19 20:34:57 db3 upsdrvctl[2710516]: [apcv3] Warning: type error exception (OID = .1.1.30.2.1.1.4.1)
Dec 19 20:34:57 db3 upsdrvctl[2710516]: Requested 'mibs' value 'apc' did not match this device [apcv3] (host 192.168.100.220)
Dec 19 20:34:57 db3 upsdrvctl[2710516]: upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it
Dec 19 20:34:57 db3 upsdrvctl[2710516]: Network UPS Tools - Generic SNMP UPS driver 1.30 (2.8.1)
Dec 19 20:34:57 db3 upsdrvctl[2710515]: Driver failed to start (exit status=1)
Dec 19 20:34:57 db3 upsdrvctl[2710515]: Network UPS Tools - UPS driver controller 2.8.1
Dec 19 20:34:57 db3 systemd[1]: nut-driver.service: Control process exited, code=exited, status=1/FAILURE
Dec 19 20:34:57 db3 systemd[1]: nut-driver.service: Failed with result 'exit-code'.
Dec 19 20:34:57 db3 systemd[1]: Failed to start Network UPS Tools - power device driver controller.

The problem is still that an base OID of .iso.3.6.1.4.1.318 still fails on the device.

snmpv3walk iso.3.6.1.2.1.1.5.0 = STRING: "APC_SMART_UPS"

from nut.

Oh, so naybe we do have both apc and apcc mappings, per earlier "screenshot". I'm in mountains now so not reading too well.

Anyhow, you can try to remove (comment away) the mibs=... line and so have the driver pick each mapping it already knows. As a fallback, ietf would likely match when tried last.

If no vendor-specific subdriver fits, docs (and scripts in NUT sources) elaborate on walking the device to generate sources for a new one.

from nut.

That's what I did anyway (commenting the mibs line). Didn't work either.
I suspect the APC USP controller card AP9617 firmware update was somehow incomplete (left me without https gui and APC MIB bits). It's old hw (2006). Right now I'm trying to contact my German supplier to get some info on that firmware update.
Thank you for your comments. Have a nice stay in the mountains and keep away from the wolves.

from nut.

from nut.

CC @aquette - maybe similar to #734 ?

from nut.

Found the solution (I hope). The firmware upgrade utility didn't do its job.
The USP firmware part was not installed - for whatever reason?
When old hardware meets a self made RS232 cable?
I renamed apc_hw02_aos394_sumx393.exe to apc_hw02_aos394_sumx393.zip.
I Compared the content of the driver card FTP listing to the files available in this EXEC/ZIP file.
The I put the the non existent file apc_hw02_sumx_393.bin from the ZIP file to the controller and voila iso.3.6.1.4.1.318 became a readable OID.
Now snmp-ups mibs=apcc does what it should.
Saved me from trying to create a new sub-driver ...
Thank you and everybody on the NUT team for your work and support!

from nut.

I indeed remember that APC was using specific serial wiring and selling not cheap their cables...
Glad to hear it's fixed

from nut.