On Wed, Aug 20, 2008 at 07:25:40PM +0200, Vidar Faltinsen wrote:
Tim Chown wrote:
When we do add the 6509, how should we enter the prefix/scope information? I'm a little confused as to the meaning of static/reserved/scope for the 'Add prefix' option in the Edit Database. We have maybe 25 vlans and subnets, and I assume we need to add them all here. I assume we use 'scope' for devices we manage?
When you add a router to NAV with ditto subnets, you simple add the router (add IP device in Edit Databe) as category GW or GSW (the latter if it also has layer 2 switch ports, in which a 6509 typically has).
The subnets will then be autodetected and added to NAV. In cases where the interfaces are virtual, NAV will also derive the subnet to vlan mapping, i.e. Interface Vlan10 is a routerport for vlan 10.
Hi Vidar, thanks for the explanation. That is indeed what happened when we added our router device(s). The vlan database was also populated and we can still edit scope data via the vlan editor (the two are quite closely coupled :)
You do not have to add a scope to NAV, if you do you do it for one reason only, to give outer scope information to "the IP address scope - graphical view" linked from the report tool. Read; http://metanav.uninett.no/reporttool#ip_address_scope_-_graphical_view
Ah, OK, so (for example) we could manually add our campus prefix of 126.96.36.199/16 and the other scopes would then be listed underneath (whether manually entered or autodiscovered)? That's nice.
Second main question is on the traffic maps. It seems at first glance that these show traffic between router interfaces. Is it possible to have the traffic map show loads between trunk ports that connect switch stacks? That would be very useful for us if it could be configured.
The traffic map of today is soon to be replaced with a new one, and this will be able to show the traffic between trunk ports. When I say soon, hopefully 3.5 in September, it may not be feature complete at that time, but hopefully this will be in place.
That would be really useful :)
You may be able to see the trunk port traffic on todays map as well if you drill down on a relevant subnet to see the layer 2 structure.
The information as you imply is all there, 'just' need a view of it.
Certainly enjoying exploring NAV, it's very useful so far, many thanks for all the team's work on it :)