On Mon, 18 Feb 2013 11:31:08 +0100 Ingeborg Hellemo email@example.com wrote:
Eventengine logs a lot of topology problems of two kinds.
One regarding the NAV-server itself:
2013-02-18 11:23:37,173 [WARNING nav.eventengine.topology] NAVServer('220.127.116.11') topology problem: router ma-gsw3.infra is up, but not in VLAN graph for <Prefix: 18.104.22.168/24 (vlan 103 (nett,srv,5-nettet))>. Defaulting to 'reachable' status.
The other kind regarding some (but not all) random devices:
2013-02-18 11:23:37,740 [WARNING nav.eventengine.topology] nfh-b100-nc.prn topology problem: router nfh-gsw.infra is up, but not in VLAN graph for <Prefix: 10.253.19.0/24 (vlan 600 (uit,prn))>. Defaulting to 'reachable' status.
Is there anything we can do to in our setup to eliminate the warnings (except changing the debug level...)?
The WARNING level may be too high for these messages in the first place. They only appear when things stop responding and the event engine cannot make sense of the detected VLAN topology. I'll take your opinion on this any day.
The message tells you (or me, at least) that your NAV server is 22.214.171.124. The event engine thinks this is on VLAN 103, prefix 126.96.36.199/24 and that the default router for this VLAN is ma-gsw3. When interpreting NAV's topology data, however, it was, for some reason, unable to find the ma-gsw3 router in VLAN 103 topology.
The second message tells more or less the same story about the nfh-b100-nc device on VLAN 600 and the nfh-gsw router.
It's a shame you didn't participate in the beta testing period, Ingeborg :) If these problems are reproducible on tromso-vk, I could take a closer look at the data from here.