2N IP Force SNMPv3 add request

Device Requests
1

Please provide ALL info asked for here.

Hi, snmpwalk returns timeout on latest version of 2N IP Force Helios intercoms. SNMPv3 was added recently, but not useable by librenms. Only SNMP v1 works.
Hope I’m doing everything correctly… Here are the requested files :

./discovery.php -h HOSTNAME -d | ./pbin.sh
https://p.libren.ms//view//99c18f21

lnms device:poll HOSTNAME -vv | ./pbin.sh
https://p.libren.ms//view//d70aa680

snmpwalk -v1 -c COMMUNITY HOSTNAME . | ./pbin.sh
https://p.libren.ms//view//78a361ff

MIB
https://p.libren.ms/view/72656057

Like I said, first time I try this. Hope everthing is there. Thanks.

I’m not totally a newby (my libnms is ok with a second poller and more than 500 device monitored), but my knowledge of coding and working behind GUI web is rather limited. I need help for this part.

2

Unfortunately if an snmpwalk is timing out for the device then that’s a vendor issue and you’ll need to raise it to them.

2N devices more generally are detected ok in LibreNMS.

3

If snmp v1 only is working when 2N device provides 1, 2c and 3, it’s not informations missing from librenms and I need to contact 2N support ? Is that what you’re saying ?

4

If you have snmp v2 configured on the device but can’t do an snmpbulkwalk against it then that’s a device issue. LibreNMS just uses snmp commands under the hood so if you can’t get them to work on their own then we can’t do much.

5

I opened a case at axis support and here’s the reply after a few mails with tech support :
After analyzing this issue, we have found the probable reason why is not working on SNMPv3.
It requires one parameter: msgUserName, which we currently don’t support.
The earliest date for update to work with Librenms would be the end of this year.

I’ll be testing the firmwares in 2026.