Great questions. I'll start with a short description about how the Mimosa MIBs are structured.
MIMOSA-MIB is a top-level MIB which describes the root of Mimosa, Mimosa product IDs and Mimosa specific traps.
MIMOSA-MIB-B5 describes values unique to the Mimosa Backhaul product family.
Near the top of the MIMOSA-MIB, there is a section called IMPORTS which shows that we support SNMPv2-SMI, SNMPv2-CONF, RFC1155-SMI and IF-MIB. We didn't write these MIBs, and they are not specific to us, but we respond to requests for the values they contain.
In particular, IF-MIB contains Ethernet interface counters, which is what I think you are after.
For standard MIBs, object names are substituted for OIDs at the time of snmpwalk, so you first determine the interface of interest, and then find the corresponding counters. Below is an example.
Determine the if-index of the interface from the snmpwalk
IF-MIB::ifDescr.9 = STRING: wifi0
IF-MIB::ifDescr.3 = STRING: eth1_emac1
Identify counters for the if-index
IF-MIB::ifInOctets.3 = Counter32: 4089553984 (Input packets for eth)
IF-MIB::ifInOctets.9 = Counter32: 2579367802 (Input packets for wifi)
IF-MIB::ifInUcastPkts.3 = Counter32: 46461110 (Unicast packets for eth1_emac1)
IF-MIB::ifInUcastPkts.9 = Counter32: 61415436 (Unicast packets for wifi)
Note that these are all Counter32, as provided by Net-SNMP. We have no current plans to migrate to Counter64.
The MIMOSA-MIB-B5 file contains the relevant RF statistics from the Chains and Streams tables, and these are probably the most important things to monitor (Rx Power, SNR, PHY rates, MCS Index, EVM).
However, with B5-Lite firmware 1.3.1, we found and fixed a bug where SNMP did not return these properly. The fix will be available in the upcoming 1.4.0 release in a few weeks. There is a beta available now for those who need it, and it can be obtained by contacting support via chat or email.
Are there any other Cacti or pure SNMP experts out there on the community that would like to share their knowledge and experience here?