ER605 (TL-R605) - incorrect data of send\receive via SNMP (MIB wanted)
TL-R605 is edge router, it connect to managed switch D-Link.
I use Zabbix (and LibreNMS too) to monitor utilization of network device.
And I see strangerous things: when switch's port utilization shows 25 Mbps (for example), router's port utilization is 100 Kbps only.
Accordingly I have two questions - in which units port utilization is measuring, and where to find MIB file for ER605?
Router port utilization:
Switch port utilization (yellow):
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
The data from the switch is not always sent to the gateway, right?
Also, as far as I know, the ER605 uses the public MIB.
- Copy Link
- Report Inappropriate Content
The graphs above show the dynamics of incoming packets on the router port to which the switch port is connected, and outgoing packets on the switch port.
These graphs must match.
In practice, these charts not only don't match, they don't even match trends.
Hence the conclusion - the router in the "standard" OIDs gives garbage.
- Copy Link
- Report Inappropriate Content
@mzd6 Have you had any success with this ? I am receiving the exact same issue on my ER605, namely that standard SNMP monitoring of an interface is not returning figures indicative of the traffic actually passing through that interface.
-Pete
- Copy Link
- Report Inappropriate Content
unfortunately, no..
- Copy Link
- Report Inappropriate Content
@mzd6 any updates? here i have the same issue.
- Copy Link
- Report Inappropriate Content
Nope. Moreover, there were two times that the router stopped sending SNMP data until I rebooted it.
- Copy Link
- Report Inappropriate Content
You may be experiencing counter wrapping. I don't know how Zabbix or LibreNMS handle that. Debugging a similar situation on my NMS, the following is the raw data polled from SNMP from an OID that is supposed to be HC In Octets:
While the data is coming from the HC OIDs, the actual values are not 64 bit. They seem to be wrapping on the router itself in a 32 bit data type.
If I'm right about this, the only way this can be fixed is with a firmware update on the router.
- Copy Link
- Report Inappropriate Content
Also having the same problem trying to monitor this unit.
Is TP-LINK going to chime in on this issue and provide a fix?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1735
Replies: 8
Voters 0
No one has voted for it yet.