Incorrect SNMP reading in v1.4.4


#1

We have detected that in B5 with version 1.4.4 they are returning mistaken values in SNMP queries.

It looks like “TxWidth” OID are missing and since them all OID are misplaced (90MHz TxWidth should be 90Mbps RxPhy, and so on).

Here is a sample of an affected equipment:

# snmpwalk  -c xxxx -v 2c yyyyyyyy .1.3.6.1.4.1.43356.2.1.2.6.2.1
MIMOSA-NETWORKS-BFIVE-MIB::mimosaTxPhy.1 = INTEGER: 90 Mbps
MIMOSA-NETWORKS-BFIVE-MIB::mimosaTxPhy.2 = INTEGER: 90 Mbps
MIMOSA-NETWORKS-BFIVE-MIB::mimosaTxPhy.3 = INTEGER: 90 Mbps
MIMOSA-NETWORKS-BFIVE-MIB::mimosaTxPhy.4 = INTEGER: 0 Mbps
MIMOSA-NETWORKS-BFIVE-MIB::mimosaTxMCS.1 = INTEGER: 4
MIMOSA-NETWORKS-BFIVE-MIB::mimosaTxMCS.2 = INTEGER: 4
MIMOSA-NETWORKS-BFIVE-MIB::mimosaTxMCS.3 = INTEGER: 4
MIMOSA-NETWORKS-BFIVE-MIB::mimosaTxMCS.4 = INTEGER: -1
MIMOSA-NETWORKS-BFIVE-MIB::mimosaTxWidth.1 = INTEGER: 90 MHz
MIMOSA-NETWORKS-BFIVE-MIB::mimosaTxWidth.2 = INTEGER: 90 MHz
MIMOSA-NETWORKS-BFIVE-MIB::mimosaTxWidth.3 = INTEGER: 90 MHz
MIMOSA-NETWORKS-BFIVE-MIB::mimosaTxWidth.4 = INTEGER: 90 MHz
MIMOSA-NETWORKS-BFIVE-MIB::mimosaRxPhy.1 = INTEGER: 4 Mbps
MIMOSA-NETWORKS-BFIVE-MIB::mimosaRxPhy.2 = INTEGER: 4 Mbps
MIMOSA-NETWORKS-BFIVE-MIB::mimosaRxPhy.3 = INTEGER: 4 Mbps
MIMOSA-NETWORKS-BFIVE-MIB::mimosaRxPhy.4 = INTEGER: 4 Mbps
MIMOSA-NETWORKS-BFIVE-MIB::mimosaRxMCS.1 = INTEGER: -189
MIMOSA-NETWORKS-BFIVE-MIB::mimosaRxMCS.2 = INTEGER: -170
MIMOSA-NETWORKS-BFIVE-MIB::mimosaRxMCS.3 = INTEGER: -184
MIMOSA-NETWORKS-BFIVE-MIB::mimosaRxMCS.4 = INTEGER: -177

Note that snmpwalk stops here, but it should be returning more values.

Other versions (like 1.4.1) return values according to MIB file.


#2

This is a known issue. Channel width was inserted into the MIMO Status table, and the old MIB file was updated. The next version of firmware will address this bug and correct the MIB file discrepancy.


#3