On Tue, 19 Feb 2013 13:48:46 +0100 Ingeborg Hellemo ingeborg.hellemo@uit.no wrote:
morten.brekkevold@uninett.no said:
When interpreting NAV's topology data, however, it was, for some reason, unable to find the ma-gsw3 router in VLAN 103 topology.
And why is that? Where can I find out what NAVs topology looks like? Because ma-gsw3 should indeed be a part of the VLAN 103 topology.
I can't say why just from this information alone. It just means that event engine expected the router to be in the in the graph built for the VLAN 103 topology, since it determined that this was the router for that VLAN, yet it didn't find it in the graph when searching for a path.
The error message is there just for this purpose: So that we are made aware of possibly fishy topology detection and can debug the data/algorithm. In your case, we are exceptionally privileged in that we have access to debug directly on your test server :)
morten.brekkevold@uninett.no said:
If these problems are reproducible on tromso-vk, I could take a closer look at the data from here.
You will find similar errors on tromso-vk (different hosts but same type of error).
If you could drop med an e-mail with the names of some to look at, compared with information from the real world, I'll take a look.