SNMP conflict?

[ericbergan]

I'm currently running .46 on a AC87R. I've downloaded and installed net-snmp, figured out the OIDs I needed for WAN xmit/rcv counts and configured my monitoring software.

If I load .47, am I going to have a conflict with my existing net-snmp installation? I'm reading ASUS' implementation may not have the interface objects, which are what I am currently monitoring. Thanks.

eric

 

[RMerlin]

I'm currently running .46 on a AC87R. I've downloaded and installed net-snmp, figured out the OIDs I needed for WAN xmit/rcv counts and configured my monitoring software.

If I load .47, am I going to have a conflict with my existing net-snmp installation? I'm reading ASUS' implementation may not have the interface objects, which are what I am currently monitoring. Thanks.

eric

You definitely can't run both at the same time since they will try to share the same port. How if you don't enable the built-in one, it might be OK.

Look if it's possible to enable interface support in the built-in SNMP implementation. If you can provide instructions on how to do so, I can probably include it in a future release. I just lack the time and the expertise to look into this at this time (as I would have to start from the beginning and familiarize myself with SNMP first).

 

[ericbergan]

Ok, I'll try it in the next day or so and let you know what I see.

 

[ericbergan]

I upgraded the firmware. The net-snmp daemon was still running, so I started by not touching the Admin->SNMP stuff. But, my monitoring program could no longer access the SNMP data.

So I used Admin->SNMP to start that daemon. It apparently automatically killed the net-snmp version. But I was unsuccessful in getting my monitoring program to be able to find any OIDs.

So I turned back off the ASUS SNMP, uninstalled and reinstalled net-snmp, and started debugging. The interface numbers had changed (relative to .46), and the send and rcv numbers had flipped. Changed those in my monitoring software, and everything is more or less working again.

So this is far from scientific, but my current belief (with only 50/50 confidence) is that the ASUS firmware upgrade changed the reporting that the net-snmp daemon was reading, and the ASUS native snmp isn't currently working for capturing vlan traffic.

If anyone else reads this and has success with the ASUS SNMP reporting WAN send/receive traffic numbers, I'd be interested in knowing what you did, what OIDs were used, etc. Thanks!

eric

 

[jernau]

The issue around the new inbuilt SNMPD daemon not providing interface metrics is due to the mibs included at compile time. If I run net-snmp-config --configure-options I see the following;

'--with-mib-modules=asus-mib/wireless,asus-mib/lan,asus-mib/wan,asus-mib/ipv6,asus-mib/vpn,asus-mib/firewall,asus-mib/administration,asus-mib/systemLog,asus-mib/guestNetwork,asus-mib/trafficManager,asus-mib/parentalControl,asus-mib/quickInternetSetup'

All the referenced mibs are asus specific. Unfortunately I can't do the same command against the entware snmpd daemon I have running on the router but if I do the same on a Linux box I get;

'--with-mibdirs=/root/.snmp/mibs:/usr/share/snmp/mibs:/usr/share/snmp/mibs/iana:/usr/share/snmp/mibs/ietf:/usr/share/mibs/site:/usr/share/snmp/mibs:/usr/share/mibs/iana:/usr/share/mibs/ietf:/usr/share/mibs/netsnmp'

I suspect the ifindex mibs are part of the iana or ietf mib set. Not sure if the asus SNMPD daemon could be recompiled to include those additional mibs.

 

[RMerlin]

Thanks. I will have to see if it's possible to add those standard mibs without creating any conflict.

 

[RMerlin]

BTW, here's the Asus MIB for their extensions:

https://github.com/RMerl/asuswrt-me...c/router/net-snmp-5.7.2/mibs/RT-AC66U-MIB.txt

If your client lets you load a MIB file, this will make it easier afterward to browse through the router's SNMP tree.

 

[RMerlin]

I just added a bunch of modules based on the list used by OpenWRT:

https://github.com/RMerl/asuswrt-merlin/commit/b4ad5185e0d8959a0c1f589740d2ca8df1185ffc

That should expose everything needed now for uses such as bandiwdth monitoring and more.