[BUG] NAV 5.8.0 cannot read data from Eaton V4.38 version SNMP card with SNMPv1

[szucsdl]

Describe the bug

In the software, we monitor several types of Eaton UPS, each of which has a ConnectUPS Web/SNMP Card V4.38 management card. NAV use 1.3.6.1.4.1.534.1 OID to read data from device.
In NAV version 5.8.0, it is not possible to read data from this type of card with SNMPv1 (with V4.38 firmware).
The Connectivity Check test in the Edit Device menu results in a successful connection

Screenshots

Environment:

• OS on the NAV server Debian 11.8
• NAV version installed 5.8.0
• Method of installation from repository

[lunkwill42]

@szucsdl I suspect this is a duplicate of #2767. Have you checked the status of your background processes (nav status), is ipdevpoll up?

Please upgrade to 5.8.1 ASAP.

[szucsdl]

@lunkwill42 I installed the latest version of NAV today (5.8.2). Of course, the services are up:) the other (several hundred) managed devices (other EATONs, Cisco, Alcatel-Lucent, etc.) can be managed as usual. There is still a problem only with Eaton v4.38 firmware cards managed via SNMPv1
In version 5.8.2, the error can still be found, the settings on the UPS card are good, the connectivity check is successful in the edit device menu

Thanks for your support

[lunkwill42]

There is still a problem only with Eaton v4.38 firmware cards managed via SNMPv1

Then the next step is to see whether there are any interesting messages about these devices in ipdevpoll.log. The job status indicators you posted do not indicate any error running the jobs - it basically indicates that the jobs just aren't running at all (or, at least they are not completing in a timely manner).

[lunkwill42]

I think we may have found your problem, @szucsdl - see #2779

[lunkwill42]

Fixed by #2780

[szucsdl]

@lunkwill42 thank you so much for your work

In Edit Device menu Connectivity check is still works correctly
Devices that can only communicate via SNMPv1 works fine after install NAV 5.8.3

My first assumptions were wrong. As you wrote, an error in SNMPv1 caused the problem. The error only occurred in half of the devices because the other Eaton mgmt cards were able to respond via SNMPv2c. (There were a few more affected devices, but now I was only focused on the Eatons)