ER605 V2.20 unable to monitor all the interfaces using SNMP

ER605 V2.20 unable to monitor all the interfaces using SNMP

ER605 V2.20 unable to monitor all the interfaces using SNMP
ER605 V2.20 unable to monitor all the interfaces using SNMP
Friday - last edited 22 hours ago
Tags: #SNMP
Model: ER605 (TL-R605)  
Hardware Version: V2
Firmware Version: ER605(UN)_V2.20_2.3.1 Build 20251015

Hi All,

 

Using Linux to do the SNMP walk for ER605, however, I am unable to fetch all the interface.

 

It seems like there is a limitation by the firmware / hardware.

 

:~$ snmpwalk -v2c -c public 192.168.1.1 | grep eth


iso.3.6.1.2.1.2.2.1.2.1026 = STRING: "default/eth0"
iso.3.6.1.2.1.2.2.1.2.1027 = STRING: "default/eth1"
iso.3.6.1.2.1.2.2.1.2.1034 = STRING: "default/veth0"
iso.3.6.1.2.1.2.2.1.2.1035 = STRING: "default/veth1"
iso.3.6.1.2.1.31.1.1.1.1.1026 = STRING: "default/eth0"
iso.3.6.1.2.1.31.1.1.1.1.1027 = STRING: "default/eth1"
iso.3.6.1.2.1.31.1.1.1.1.1034 = STRING: "default/veth0"
iso.3.6.1.2.1.31.1.1.1.1.1035 = STRING: "default/veth1"

 

 

Firmware Version: 2.3.0 Build 20250428 Rel.18967

Hardware Version:ER605 v2.20

  0      
  0      
#1
Options
1 Accepted Solution
Re:ER605 V2.20 unable to monitor all the interfaces using SNMP-Solution
22 hours ago - last edited 22 hours ago

  @navwork 

You're only seeing four logical interfaces (eth0, eth1, veth0, veth1) because the ER605 (TL-R605) V2 firmware does not expose the individual LAN/WAN ports via SNMP. Instead, it aggregates them into internal virtual interfaces (default/ethX) and hides the switch-port details from standard MIB-2 tables like ifTable and ifXTable.This is by design, not a misconfiguration on your side.

Recommended Solution
  0  
  0  
#2
Options
1 Reply
Re:ER605 V2.20 unable to monitor all the interfaces using SNMP-Solution
22 hours ago - last edited 22 hours ago

  @navwork 

You're only seeing four logical interfaces (eth0, eth1, veth0, veth1) because the ER605 (TL-R605) V2 firmware does not expose the individual LAN/WAN ports via SNMP. Instead, it aggregates them into internal virtual interfaces (default/ethX) and hides the switch-port details from standard MIB-2 tables like ifTable and ifXTable.This is by design, not a misconfiguration on your side.

Recommended Solution
  0  
  0  
#2
Options