MIBs do not affect the data the device reports, they just make it easier to identify and work with the data.
MIBs are like DNS, all they really do is provide a hierarchy, a name<>number translation and sometimes some hints about the format of the data returned. They're not really useful by themselves in enabling support for new things, like a driver would be. They're rather more like the technical specification used to write the driver.
It's possible they have moved this data to a new location on newer MIBs, or added new OIDs with more useful data. It's strange they'd be returning erroneous data in old tables though, but tis difficult to say without examples.
Adding support for new things requires writing code and/or definitions for the new data. This isn't a zero-effort thing, and usually occurs based on greatest demand (or commercial sponsorship).
Mike/Tom: I think we should come up with a generic "new stuff" template form or something, and include the "mibs don't do shit" boilerplate in the mailing list sign-up process somewhere. I think this would go some way to mitigating these open ended things.
Adam.
Sent from BlueMail
On 8 May 2018, 21:15, at 21:15, Serge Caron scaron@pcevolution.com wrote:
Greetings!
Quote from Adam : "The archives died during a server move, and the mailing list software is voodoo, so they never came back". Apologies for asking something that is probably old news.
The Community Edition ships with Senao (Engenius) MIBs dated 2013.11.25.
This is fine for older devices such as the EAP9550 and we get proper data (such as number of wireless clients).
However, it seems all modern dual band devices such as the (older) EAP600 and the (newer) ECB1750 always report 1 as the number of wireless clients (as well as other broken stats).
Are there updated MIBs compatible to observium for these products?
Regards,
Serge Caron
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium