F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

Philipp_Stadler's avatar
Philipp_Stadler
Icon for Nimbostratus rankNimbostratus
May 02, 2014

SNMP VLAN Statistics

I'm playing around with SNMP monitoring to get traffic statistics by VLAN. Now I figured out, that almost all VLAN interfaces have the same bytes in counters (also all other counters are the same abo...
application delivery
LTM
management
Jacky_Hung_1606's avatar
Jacky_Hung_1606
Icon for Nimbostratus rankNimbostratus
Jun 12, 2014

I had 11.3.0 some issue of sysVlanStatTable or sysVlanxStatTable.

snmpwalk -m F5-BIGIP-SYSTEM-MIB -c public -v 2c f5_host .1.3.6.1.4.1.3375.2.1.2.13.2.2.1

F5-BIGIP-SYSTEM-MIB::sysVlanMemberVmname."/Common/HA"."1.3" = STRING: 1.3
F5-BIGIP-SYSTEM-MIB::sysVlanMemberVmname."/Common/LAN"."1.4" = STRING: 1.4
F5-BIGIP-SYSTEM-MIB::sysVlanMemberVmname."/Common/WAN"."1.1" = STRING: 1.1
F5-BIGIP-SYSTEM-MIB::sysVlanMemberVmname."/Common/WAN2"."1.2" = STRING: 1.2
F5-BIGIP-SYSTEM-MIB::sysVlanMemberVmname."/Common/WAN3"."1.2" = STRING: 1.2
F5-BIGIP-SYSTEM-MIB::sysVlanMemberParentVname."/Common/HA"."1.3" = STRING: /Common/HA
F5-BIGIP-SYSTEM-MIB::sysVlanMemberParentVname."/Common/LAN"."1.4" = STRING: /Common/LAN
F5-BIGIP-SYSTEM-MIB::sysVlanMemberParentVname."/Common/WAN"."1.1" = STRING: /Common/WAN
F5-BIGIP-SYSTEM-MIB::sysVlanMemberParentVname."/Common/WAN2"."1.2" = STRING: /Common/WAN2
F5-BIGIP-SYSTEM-MIB::sysVlanMemberParentVname."/Common/WAN3"."1.2" = STRING: /Common/WAN3
F5-BIGIP-SYSTEM-MIB::sysVlanMemberTagged."/Common/HA"."1.3" = INTEGER: false(0)
F5-BIGIP-SYSTEM-MIB::sysVlanMemberTagged."/Common/LAN"."1.4" = INTEGER: false(0)
F5-BIGIP-SYSTEM-MIB::sysVlanMemberTagged."/Common/WAN"."1.1" = INTEGER: false(0)
F5-BIGIP-SYSTEM-MIB::sysVlanMemberTagged."/Common/WAN2"."1.2" = INTEGER: true(1)
F5-BIGIP-SYSTEM-MIB::sysVlanMemberTagged."/Common/WAN3"."1.2" = INTEGER: true(1)
F5-BIGIP-SYSTEM-MIB::sysVlanMemberType."/Common/HA"."1.3" = INTEGER: interface(0)
F5-BIGIP-SYSTEM-MIB::sysVlanMemberType."/Common/LAN"."1.4" = INTEGER: interface(0)
F5-BIGIP-SYSTEM-MIB::sysVlanMemberType."/Common/WAN"."1.1" = INTEGER: interface(0)
F5-BIGIP-SYSTEM-MIB::sysVlanMemberType."/Common/WAN2"."1.2" = INTEGER: interface(0)
F5-BIGIP-SYSTEM-MIB::sysVlanMemberType."/Common/WAN3"."1.2" = INTEGER: interface(0)


snmpwalk -m F5-BIGIP-SYSTEM-MIB -c public -v 2c f5_host .1.3.6.1.4.1.3375.2.1.2.13.6.2.1.3

F5-BIGIP-SYSTEM-MIB::sysVlanStatBytesIn."/Common/HA" = Counter64: 14227914980
F5-BIGIP-SYSTEM-MIB::sysVlanStatBytesIn."/Common/LAN" = Counter64: 1083712031397
F5-BIGIP-SYSTEM-MIB::sysVlanStatBytesIn."/Common/WAN" = Counter64: 300664146409
F5-BIGIP-SYSTEM-MIB::sysVlanStatBytesIn."/Common/WAN2" = Counter64: 142056782281
F5-BIGIP-SYSTEM-MIB::sysVlanStatBytesIn."/Common/WAN3" = Counter64: 142056782281


snmpwalk -m F5-BIGIP-SYSTEM-MIB -c public -v 2c f5_host .1.3.6.1.4.1.3375.2.1.2.13.7.2.1.6

F5-BIGIP-SYSTEM-MIB::sysVlanxStatHcInOctets."/Common/HA" = Counter64: 14227919270
F5-BIGIP-SYSTEM-MIB::sysVlanxStatHcInOctets."/Common/LAN" = Counter64: 1083712916719
F5-BIGIP-SYSTEM-MIB::sysVlanxStatHcInOctets."/Common/WAN" = Counter64: 300664161169
F5-BIGIP-SYSTEM-MIB::sysVlanxStatHcInOctets."/Common/WAN2" = Counter64: 142056798677
F5-BIGIP-SYSTEM-MIB::sysVlanxStatHcInOctets."/Common/WAN3" = Counter64: 142056798677

Can see WAN2 and WAN3 at the 1.2, but they have the same statistical value.

Philipp_Stadler's avatar
Philipp_Stadler
Icon for Nimbostratus rankNimbostratus
Jun 16, 2014
I've got an answer to my case: ID382157 states that the statistics exposed via tables sysVlanStatTable and sysVlanxStatTable represent the sum of the vlan's interfaces/ifx stats, not the stats for the individual vlan. In reality this means that any vlans enabled for the same interfaces, will display the same stats. If there is anything unclear, please let me know and I will try to answer your question. Unfortunately there is no fix or workaround available for this issue. so this means there is a bug, which confirms this behaviour and it will be fixed only in 11.5.