B5 SNMP Results Change Between 1.4.4 and 1.4.6


#1

There appear to be undocumented changes in the returned results for mimosaRxPower and mimosaSNR, at least. Firmware 1.4.4 returns these as 2-digit numbers, firmware 1.4.6 returns these as 3-digit numbers. Examples:

A version 1.4.4 host responds:

.1.3.6.1.4.1.43356.2.1.2.1.3.0 = STRING: “1.4.4”
.1.3.6.1.4.1.43356.2.1.2.6.1.1.3.1 = INTEGER: -68
.1.3.6.1.4.1.43356.2.1.2.6.1.1.3.2 = INTEGER: -68
.1.3.6.1.4.1.43356.2.1.2.6.1.1.3.3 = INTEGER: -68
.1.3.6.1.4.1.43356.2.1.2.6.1.1.3.4 = INTEGER: -68
.1.3.6.1.4.1.43356.2.1.2.6.1.1.5.1 = INTEGER: 24
.1.3.6.1.4.1.43356.2.1.2.6.1.1.5.2 = INTEGER: 24
.1.3.6.1.4.1.43356.2.1.2.6.1.1.5.3 = INTEGER: 24
.1.3.6.1.4.1.43356.2.1.2.6.1.1.5.4 = INTEGER: 24

A version 1.4.6 host responds:

.1.3.6.1.4.1.43356.2.1.2.1.3.0 = STRING: “1.4.6

.1.3.6.1.4.1.43356.2.1.2.6.1.1.3.1 = INTEGER: -681
.1.3.6.1.4.1.43356.2.1.2.6.1.1.3.2 = INTEGER: -691
.1.3.6.1.4.1.43356.2.1.2.6.1.1.3.3 = INTEGER: -686
.1.3.6.1.4.1.43356.2.1.2.6.1.1.3.4 = INTEGER: -682
.1.3.6.1.4.1.43356.2.1.2.6.1.1.5.1 = INTEGER: 208
.1.3.6.1.4.1.43356.2.1.2.6.1.1.5.2 = INTEGER: 198
.1.3.6.1.4.1.43356.2.1.2.6.1.1.5.3 = INTEGER: 188
.1.3.6.1.4.1.43356.2.1.2.6.1.1.5.4 = INTEGER: 192

Please note the extra trailing newline at the end of the firmware result, as well. Please advise what the intended behavior going forward is and/or when/if it will be reverted.


#2

Dan,

We did some checking into this, and found that there was a syntax deviation in 1.4.4 from a prior firmware version, which had been corrected in 1.4.6 and later firmware. We are going change the way the newline character is handled in future firmware version.


#3

Ok, thanks! Good to know what to expect going forward!


#4

So 1.4.6 is consistent with the original MIB?
You do have to be careful there – the rule of MIBs is that once a value is assigned to an OID, it never, ever changes. You add, but don’t change. All OIDs go into one global list.