Hi Morten,
Yeah i am aware of that document and in the past i have tried to use the guidelines as described.
What happen with the current vlan/prefix settings if i change my config on my routers? Will it reflect/change also in NAV (i hope so :) ).
I am sure that not everyone is willing to change there convention about naming, so an option to change it in NAV would be very welcome.
As for me, i can change it tot he convention the wiki page is mentiond, but i want to make sure that it also will change in NAV.
Kind regards,
René Romijn
-----Oorspronkelijk bericht----- Van: Morten Brekkevold [mailto:morten.brekkevold@uninett.no] Verzonden: maandag 30 januari 2017 09:24 Aan: René Romijn Rene.Romijn@tabsholland.nl CC: nav-users@uninett.no Onderwerp: Re: vlan and prefix in the seeddb
On Fri, 27 Jan 2017 13:06:08 +0000 René Romijn Rene.Romijn@tabsholland.nl wrote:
Is it possible to clean up the vlan list? There are some 'empty' entries there.
Also in the prefix i do not see any entries and if i try to add a subnet mannually then it say's it allready exists. Those existing entries are shown up in the Vlan list, but i cannot use them in the IPAM tool
Have you read this guide, linked from the documentation: https://nav.uninett.no/wiki/subnetsandvlans ?
The reason you don't see any prefix entries in SeedDB, is because SeedDB will not allow you to edit automatically collected prefix information (since the next collection will overwrite your changes). Go to the prefix report to see the complete list of all registered prefixes in NAV.
The only prefix types you can add and edit manually through SeedDB are "scope" and "reserved".
I do think, however, it is time to reconsider NAV's stance on this. The only way to get meaningful metadata about assignments and usage categories of network prefixes today is to use the router interface description conventions described by the above wiki page. If you already are using a different convention that you are unwilling to change, or you don't use any convention at all (which isn't a good practice), NAV is of little help to you in this regard.
Probably, some users would rather set some of these attributes directly in NAV, and not have them overwritten by collection, so maybe we should support a global option for this. Thoughts?
-- Morten Brekkevold UNINETT