As now in SeedDB --> VLAN it looks like when we first started this tread. I have all the prefixes there but two of the prefixes has its VLAN number correctly and two prefixes missing its VLAN number (all other information fields are empty). So NAV can't use the information commented on the interface at the firewall, and I have the comments correctly entered for the organisation and usage! I notice when ipdevpoll runs the topo job for the firewall it add 5 rows in SeedDB --> VLAN with only LAN as net type and everything else empty (Not even a prefix). There is two interfaces on the firewall that do not have comments in it for NAV (some other text there). We have a total of 6 interfaces on the firewall right now.
I don't find any interesting in ipdevpoll.log file, do I need to set log level to Debug?
From navtopology.log this is shown for today: 2015-04-09 01:35:05,081 [INFO nav.topology.detector] deleting unused vlans: [<Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>] 2015-04-09 02:35:03,690 [INFO nav.topology.detector] deleting unused vlans: [<Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, '...(remaining elements truncated)...'] 2015-04-09 03:35:03,081 [INFO nav.topology.detector] deleting unused vlans: [<Vlan: N/A>] 2015-04-09 04:35:03,881 [INFO nav.topology.detector] deleting unused vlans: [<Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>] 2015-04-09 05:35:02,816 [INFO nav.topology.detector] deleting unused vlans: [<Vlan: N/A>] 2015-04-09 07:35:03,331 [INFO nav.topology.detector] deleting unused vlans: [<Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>] 2015-04-09 08:35:03,580 [INFO nav.topology.detector] deleting unused vlans: [<Vlan: N/A>, <Vlan: 605>, <Vlan: 602>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, '...(remaining elements truncated)...'] 2015-04-09 09:35:03,800 [INFO nav.topology.detector] deleting unused vlans: [<Vlan: N/A>] 2015-04-09 10:35:02,919 [INFO nav.topology.detector] deleting unused vlans: [<Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>] 2015-04-09 11:35:04,708 [INFO nav.topology.detector] deleting unused vlans: [<Vlan: N/A>] 2015-04-09 13:35:05,931 [INFO nav.topology.detector] deleting unused vlans: [<Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>] 2015-04-09 14:35:03,692 [INFO nav.topology.detector] deleting unused vlans: [<Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, <Vlan: N/A>, '...(remaining elements truncated)...'] 2015-04-09 15:35:05,160 [INFO nav.topology.detector] deleting unused vlans: [<Vlan: N/A>]
/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.