On Mon, 14 Mar 2016 10:19:34 +0200 Mattias Söderholm mattias.soderholm@malax.fi wrote:
Sorry, yes it's two rows. The correct chassi comes from ENTITY-MIB (this one is marked as DOWN i NAV) and the wrong empty chassi comes from SNMPv2-MIB (this one is ok in NAV).
That explains it. The ipdevpoll `system` plugin attempts to parse device software versions from the sysDescr OID (for cases where there is no ENTITY-MIB support in the device).
To store the software version, it needs to have a chassis entity to attach it to, unless one already exists. If the plugin cannot see that NAV already knows a chassis for this device, it will create one marked with "SNMPv2-MIB" as its source (since this is the MIB that defines the sysDescr object).
For some reason, the plugin doesn't see that a chassis did come from ENTITY-MIB, and creates an extra chassis instance. We haven't properly tested how NAV behaves when multiple MIBs are used to source entity information; it seems it's time to take a closer look at just that.