The 64-bit unicast packet counters on SG300 are broken (tested on SG300-10SFP, software 1.4.8.6), showing zero:
$ snmpget -v2c -c $somecommunity $someswitch IF-MIB::ifHCInUcastPkts.58 IF-MIB::ifHCInMulticastPkts.58 IF-MIB::ifHCInBroadcastPkts.58 IF-MIB::ifHCOutUcastPkts.58 IF-MIB::ifHCOutMulticastPkts.58 IF-MIB::ifHCOutBroadcastPkts.58
IF-MIB::ifHCInUcastPkts.58 = Counter64: 0
IF-MIB::ifHCInMulticastPkts.58 = Counter64: 0
IF-MIB::ifHCInBroadcastPkts.58 = Counter64: 0
IF-MIB::ifHCOutUcastPkts.58 = Counter64: 0
IF-MIB::ifHCOutMulticastPkts.58 = Counter64: 0
IF-MIB::ifHCOutBroadcastPkts.58 = Counter64: 0
While at the same time, the 32-bit packet counters contain sensible-looking data:
$ snmpget -v2c -c $somecommunity $someswitch IF-MIB::ifInUcastPkts.58 IF-MIB::ifInMulticastPkts.58 IF-MIB::ifInBroadcastPkts.58 IF-MIB::ifOutUcastPkts.58 IF-MIB::ifOutMulticastPkts.58 IF-MIB::ifOutBroadcastPkts.58
IF-MIB::ifInUcastPkts.58 = Counter32: 132508965
IF-MIB::ifInMulticastPkts.58 = Counter32: 406754
IF-MIB::ifInBroadcastPkts.58 = Counter32: 393313
IF-MIB::ifOutUcastPkts.58 = Counter32: 52782133
IF-MIB::ifOutMulticastPkts.58 = Counter32: 127726
IF-MIB::ifOutBroadcastPkts.58 = Counter32: 101125
(The octet counters are ok, both 32-bit and 64-bit.)
According to the Cisco FAQ on SNMP counters and the RFC it refers to, 64-bit counters (both packet and octet counters) should be used on gigabit ports, so this seems to be a bug in the switch software.
I wonder if this issue affects all of the SG300 series models (and SG350 and SG500 etc), and if it could be fixed in firmware? Or are we doomed to suffer missing counters or hacky workarounds on the client side?
