Bug in SNMP Value


#1

I noticed that the value for TotalRXPower is being returned times 10, where the value for Chain/Stream RX Power is correct:

# snmpwalk -v1 -c mycommunitystring 10.10.124.240 .1.3.6.1.4.1.43356.2.1.2.6.6
    iso.3.6.1.4.1.43356.2.1.2.6.6.0 = INTEGER: -594

# snmpwalk -v1 -c mycommunitystring 10.10.124.240 .1.3.6.1.4.1.43356.2.1.2.6.1.1.3
    iso.3.6.1.4.1.43356.2.1.2.6.1.1.3.1 = INTEGER: -63
    iso.3.6.1.4.1.43356.2.1.2.6.1.1.3.2 = INTEGER: -62

#2

Hi Nick,

Great catch!

There is a bug with the Rx power per chain data. It should be three digits to match the total Rx power per our MIB definition, but the chain data was inadvertently divided by 10 while formatting the data in a table. We’ll fix that to make them consistent.

Three-digit integers help to communicate decimal precision without floating point operations which would otherwise increase CPU loading.

There are other values like this described in both the MIB and the footnotes on our OID list: http://backhaul.help.mimosa.co/snmp-oid-reference


#3