ifInOctets and ifOutOctets counters not increasing for vlans

[Fabien_Brillard]

Hi,

the traffic counters do not increase (all = 0) for all vlans I created on Summit X480-48t (EXOS 15.7.2.9)

according to https://extremeportal.force.com/ExtrArticleDetail?an=000088473
ifInUcastPkts and IfInNUcastPkts are not supported.
But nothing about ifInOctets and ifOutOctets

On my Summit X480-48t, for example, the UP_MGW vlan is created with the following commands:
create vlan UP_MGW
configure vlan UP_MGW tag 651
configure vlan UP_MGW add ports 7 tagged
configure ports 7 monitor vlan UP_MGW

In the snmpwalk printout, ifInOctets and ifOutOctets counters (among others) are not incremented for this vlan, although I am sure there is traffic on this vlan.
Same issue for all created vlans : their counters are frozen at 0.

For instance for the UP_MGW vlan ;
IF-MIB::ifDescr.1000086 = STRING: VLAN 00651 (UP_MGW)
IF-MIB::ifInOctets.1000086 = Counter32: 0
IF-MIB::ifOutOctets.1000086 = Counter32: 0

Indexes from 1000001 to 1000090 corresponds to the vlans I created by CLI commands (for instance "UP_MGW"). Those indexes are "dynamics".

Indexes from 1001 to 1048 corresponds to the 48 physical ports of the switch.
For those indexes, IF-MIB::ifInOctets and IF-MIB::ifOutOctets work fine, they are increasing.

But all ifInOctets and ifOutOctets are blocked to zero:
IF-MIB::ifInOctets.1000001 = Counter32: 0
...
IF-MIB::ifInOctets.1000111 = Counter32: 0

IF-MIB::ifOutOctets.1000001 = Counter32: 0
...
IF-MIB::ifOutOctets.1000111 = Counter32: 0

How to "activate" the counters related to user-created vlans that we can fetch with snmp ?

Thanks
Fabien-

[Anderson_Vaugha]

Hi Fabien,

I took a look at your query and following some tests in the lab I can confirm that the article below is correct.
https://extremeportal.force.com/ExtrArticleDetail?an=000088473

From my lab, the MIB "ifDesc" shows port 13 and the VLAN named mib as below respectively:-

x.x.0.38 ifDescr 1013 Display String X460-48p Port 13 X460-48p Port 13

x.x.0.38 ifDescr 1000023 Display String VLAN 00333 (mib) VLAN 00333 (mib)

And when I get those MIBs on the switch the output is as you described.

* X460-48p.3 # show snmp get 1.3.6.1.2.1.2.2.1.10.1013
ifTable.1.10.1013 = 14058399

* X460-48p.3 # show snmp get 1.3.6.1.2.1.2.2.1.10.1000023
ifTable.1.10.1000023 = 0

The confusion may be because the tab in the link you mentioned; where this looks to be working, is for our S-Series Product.

However a "feature request" has been opened with our Product Management to consider adding those counter for VLANs on EXOS Products.

Regards

Andy Vaughan.

[Fabien_Brillard]

Hi,
thanks both for your replies., I appreciate your feedback

@ Mike :
I need counters on vlans , not on ports, because traffic types on vlan#1, vlan2, etc from a same equimement (getting in he Summit on a same port) are different, and I need to build KPI's with counters for the different traffic types.

I already have the in/out unicast counters for vlans, with CLI.
So EXOS is already counting bytes on each vlans. To me it does not seem so hard, in the code, to duplicate those counters into snmp.
(for information, for my current project, I do the same (I fetch user-created vlans counters by snmp) on Ericsson routers and it worls fine.)

@Paul :
you're right, I do have the in/out unicast counters for vlans, with CLI ("show port X vlan statistics", initialized by "configure port X monitor vlan..."), and they work fine.

But not with snmp : I went through the entire snmpwalk printout , found the counters that have been dynamically created by EXOS (OID IF-MIB::ifInOctets. with index=1000001..1000090), but values are blocked to zero.

(for comparision, the same counters for the physical ports have fixed indexes, from 1001 to 1048, under the same OID.
Extract of swmpwalk printout :
IF-MIB::ifInOctets.1001 = Counter32: 14124053 <-- port 1 (counter OK)
IF-MIB::ifInOctets.1002 = Counter32: 6511416 <-- port 2 (counter OK)
...
IF-MIB::ifInOctets.1048 = Counter32: 6259359 <-- port 48 (counter OK)
IF-MIB::ifInOctets.1049 = Counter32: 56854 <-- port management (counter OK)
IF-MIB::ifInOctets.1000001 = Counter32: 0 <-- vlan #1 created by user (counter=0)
IF-MIB::ifInOctets.1000002 = Counter32: 0 <-- vlan #2 created by user (counter=0)
IF-MIB::ifInOctets.1000003 = Counter32: 0
...
same for ifOutOctets)

I will look deeper in your comments regarding " EXTREME-VLAN-MIB , , extremePortVlanTotalReceivedBytesCounter , extremePortVlanTotalTransmittedBytesCounter", I haven't seen such counters so far.

Maybe, user-created vlans dynamic counters fetchable by snmp are not completely implemented (counters are successfully created, but not updated with values).
But I found a post, on a different subject, but with a snapshot showing ifInOctets *NON zero* under .1.3.6.1.2.1.2.2.1.10 (IF-MIB::ifInOctets) with index = 12001.
As the index with rather big (> 1049), I believe this corresponds to a dynamic counters (I mean created by EXOS, besides the fixed counters for the physical ports), and I guess this is for a vlan (what else could it be ?):
https://community.extremenetworks.com/extreme/topics/oid_for_interface_counters?topic-reply-list[set...

So now I understand it must be working, somehow ... ?
Maybe we have to initialize something, exactly as we have to do get those counters by CLI ("configure port X monitor vlan...")

Best regards
Fabien-

[Paul_Thornton]

Hi,

That part of the interface MIB has never worked, as far as I can remember (back to Extremeware days). We wanted to use it in 1999 for data centre customer billing and failed!

The good news is that you can use per-vlan statistics to see this information via the CLI - however, there is more bad news in that there's a bug that stops that from working properly in SNMP on some platforms. I have made this work on an X670V, but couldn't do it on an X460 - it may work out OK on an X480.

Repeat this commans for all the ports/VLANs you want to get stats for:
configure port X monitor vlan

Then look in the EXTREME-VLAN-MIB - specifically, extremePortVlanTotalReceivedBytesCounter and extremePortVlanTotalTransmittedBytesCounter entries.

On the CLI you can see things with: show port X vlan statistics

Michael - I have an open case 01095802 about this issue.

Paul.

[Mike_D]

Hello Fabien,

I'll research this next week forward results.

Best regards,
Mike

ps:
Your request seems straightforward enough - but packet and byte counts make more sense to me at the port level. What you see is what you get.
Vlan traffic on the other hand - thats a project.
Of interest are counters per vlan and per vlan per port. Counters for routed traffic, ACL activity, encapsulations, L3 checksum etc.
Local traffic into and out of the vlan needs calculation. Flooded unicast will ingress once but replicate for n-1 vlan ports. Similar issues with broadcast and multicast. Seems like all this should be possible but I cant picture how it might work.
I'd be interested to hear others' experience with this info.