As it is now, everything is looking and working exactly the same as when we first started this tread.
I don't find anything interested in ipdevpoll.log. Do I need to enable debug for ipdevpoll?
Something I noticed was that when topo job runs for firewall it adds four lan rows in SeedDB --> Vlan that are totally empty (these are removed later by navtopology). We have a total of six interfaces in the firewall but only four of them have the NAV VLAN comment in its description field (but none of the descriptions is shown in the NAV).
/Mattias
----- Ursprungligt meddelande ----- Från: "Morten Brekkevold" morten.brekkevold@uninett.no Till: "Mattias Söderholm" mattias.soderholm@malax.fi Kopia: nav-users@uninett.no Skickat: torsdag, 9 apr 2015 14:06:23 Ämne: Re: NAV and VLAN with Virtualized firewall
On Tue, 31 Mar 2015 14:33:35 +0300 Mattias Söderholm mattias.soderholm@malax.fi wrote:
Now I have VLAN listed with the right prefixes, but some prefixes are still missing the VLAN tag (but managed by the firewall).
Also they are missing the other information like organisation and usage.
Check `ipdevpoll.log`. ipdevpoll will not create new organizational units or usage categories if the ones listed in interface description don't correctly match the ones already in the database.
And there is also LAN that have the same VLAN tags with no information (same VLAN tag as the one with the right prefixes above).
I'm not sure I understand what you are saying here. Do you mean to say that NAV has multiple VLAN entries with the same VLAN tag number? That would be normal in cases where a VLAN tag is reused across different broadcast domains. Question is whether NAV thinks one of your broadcast domains are two different broadcast domains...
I also notices that there is a lot of VLAN with the network type LAN that have no information at all.
NAV defaults to categorizing a routed VLAN as 'lan', and only changes this in the face of other information. And, of course, if NAV is unable to parse anything meaningful from a router port interface description, it will be short on details.