On Thu, 24 Jan 2019 13:13:42 +0100 Per-Olof Axelsson <Per-Olof.Axelsson@hb.se> wrote:
> However, I get the following error message in the log file
> ipdevpoll.log
> ---
> 2019-01-24 11: 33: 09,664 [WARNING nav.mibs.entity_mib.entitymib]
> [statuscheck ex035.inet.hb.se] device response has bad table index
> .19.48 in ENTITY-MIB :: entPhysicalTable, ignoring
> ---
> What does this mean? Is there a solution?
This message can safely be ignored.
It means that the device's response from the `entPhysicalTable` includes
a column that does not exist in the MIB definition NAV is using. This
message tells you that NAV is ignoring the 19th column value, since it
doesn't know what it's for.
NAV implements ENTITY-MIB as defined by RFC 4133 (published
2005). However, the IETF revised the ENTITY-MIB in RFC 6933 (published
2013), which now includes a new 19th column in the
`entPhysicalTable`. I've added an issue to our tracker:
https://github.com/Uninett/nav/issues/1818
> Are extreme switches supported by NAV?
As far as I know, yes. I am given to understand Extreme switches have
some proprietary MIB for VLAN information, which NAV does actually
implement - but otherwise, standard MIBs will be used, if supported by
your Extreme switches.
--
mvh
Morten Brekkevold
Uninett