@NBAus 

That should be: eth0.10 (WAN1) eth0.20(WAN2)

@John1234 

I didn't not see the WAN2 OID.  My OP lists all the interfaces I can find in the snmpwalk output.  I have tested with two ER605's.  One with OC200 and one standalone.  Both shows the same list of interfaces.  Only eth0.1 shows up.  No eth0.2, eth0.10 or eth0.20.

@NBAus 

Hmm. If you set WAN2 on your router and save the config, try again, can you find that?

@John1234 

WAN2 has been set up.  The two devices I tested with snmpwalk on are in fact in production environment.  One device for failover and another for load balancing and both are working fine. The controller shows fair amount of traffic for WAN2.   However, no SNMP OID results for the WAN2 in both cases.

@Fae 

I have read this article.  In fact I followed its instruction to get the list of interfaces in my OP.   If I followed all the instruction, it consistently gives me only 1,2,3,4,5,9 and 11 child OIDs:

$ snmpwalk -v 1 -c xxxxx xxx.xxx.xxx.xxx .1.3.6.1.2.1.2.2.1.2

iso.3.6.1.2.1.2.2.1.2.1 = STRING: "lo"
iso.3.6.1.2.1.2.2.1.2.2 = STRING: "ip6tnl0"
iso.3.6.1.2.1.2.2.1.2.3 = STRING: "sit0"
iso.3.6.1.2.1.2.2.1.2.4 = STRING: "gre0"
iso.3.6.1.2.1.2.2.1.2.5 = STRING: "gretap0"
iso.3.6.1.2.1.2.2.1.2.9 = STRING: "veth1"
iso.3.6.1.2.1.2.2.1.2.11 = STRING: "eth0.1"

$ snmpwalk -v 1 -c xxxxx xxx.xxx.xxx.xxx .1.3.6.1.2.1.2.2.1.8

iso.3.6.1.2.1.2.2.1.8.1 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.8.2 = INTEGER: 2
iso.3.6.1.2.1.2.2.1.8.3 = INTEGER: 2
iso.3.6.1.2.1.2.2.1.8.4 = INTEGER: 2
iso.3.6.1.2.1.2.2.1.8.5 = INTEGER: 2
iso.3.6.1.2.1.2.2.1.8.9 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.8.11 = INTEGER: 1

$ snmpwalk -v 1 -c xxxxx xxx.xxx.xxx.xxx .1.3.6.1.2.1.2.2.1.10

iso.3.6.1.2.1.2.2.1.10.1 = Counter32: 0
iso.3.6.1.2.1.2.2.1.10.2 = Counter32: 0
iso.3.6.1.2.1.2.2.1.10.3 = Counter32: 0
iso.3.6.1.2.1.2.2.1.10.4 = Counter32: 0
iso.3.6.1.2.1.2.2.1.10.5 = Counter32: 0
iso.3.6.1.2.1.2.2.1.10.9 = Counter32: 916924924
iso.3.6.1.2.1.2.2.1.10.11 = Counter32: 2120493252

$ snmpwalk -v 1 -c xxxxx xxx.xxx.xxx.xxx .1.3.6.1.2.1.2.2.1.16

iso.3.6.1.2.1.2.2.1.16.1 = Counter32: 0
iso.3.6.1.2.1.2.2.1.16.2 = Counter32: 0
iso.3.6.1.2.1.2.2.1.16.3 = Counter32: 0
iso.3.6.1.2.1.2.2.1.16.4 = Counter32: 0
iso.3.6.1.2.1.2.2.1.16.5 = Counter32: 0
iso.3.6.1.2.1.2.2.1.16.9 = Counter32: 383052943
iso.3.6.1.2.1.2.2.1.16.11 = Counter32: 2773338499

@Fae Hi, there.

I'm on the new firmware and it seems this wasn't changed. From what I gather interface 11 (eth0) is my LAN side and interface 9 (veth1) is WAN. But it seems like the WAN side is reported as a single virtual interface. This prevents us from collecting data of the actual WAN interfaces individually.

The reason I believe the interfaces are reporting as I described is that the traffic flow tells me data in from 9 is equal to data out from 11 and vice-versa.

Any way to get data for the actual WAN interfaces?

My firmware version:

I thought 1.3.6.1.2.1.2.2.1.8.11, the ifOperStatus id for the WAN interface, would give me the state of the WAN interface.  However, it always return '1' no matter if I plug or unplug the network cable.  Am I looking at the wrong oid for this purpose or I come across another bug?

$ snmpwalk -v 1 -c xxxxx xxx.xxx.xxx.xxx .1.3.6.1.2.1.2.2.1.8

iso.3.6.1.2.1.2.2.1.8.1 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.8.2 = INTEGER: 2
iso.3.6.1.2.1.2.2.1.8.3 = INTEGER: 2
iso.3.6.1.2.1.2.2.1.8.4 = INTEGER: 2
iso.3.6.1.2.1.2.2.1.8.5 = INTEGER: 2
iso.3.6.1.2.1.2.2.1.8.9 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.8.11 = INTEGER: 1

Fae wrote

Dear @tsestini,

 

tsestini wrote

I'm on the new firmware and it seems this wasn't changed. From what I gather interface 11 (eth0) is my LAN side and interface 9 (veth1) is WAN. But it seems like the WAN side is reported as a single virtual interface. This prevents us from collecting data of the actual WAN interfaces individually.

 

Sorry if I didn't make it clearly in the previous reply.

 

The next firmware update (ER605 FW 1.2.0) will support to obtain the WAN interfaces via SNMP, which will be probably released this month (just for your reference only). And I'll actively update this post once there is a new firmware released, welcome to subscribe~

  @Fae The FW 1.2 has been released but I am still unable to monitor the 2nd WAN port.
Can you, please, confirm this firmware has fixed this issue?