Hi NAVers,
We've just installed NAV on a Debian4 r3 system for our department network that has a core Cisco 6509 and a number of satellite 3750 stacks and Cisco wireless APs.
At present our 3750 stacks are switching only, and thus in NAV we entered them as SW devices (Layer 2, many vlans).
So far in NAV we have enabled monitoring of our 3750 stacks, but not yet the core 6509, so we only have layer 2 info/configs.
We're getting data now for our switch port use, and cricket showing info on packet rates through the ports.
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?
I notice we cannot add vlans directly; I assume this is implied from the vlan information added in the prefixes?
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.
Thanks for any comments or suggestions/tips!
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.
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
The static option in Edit database is obsolete, a (very) recent and not yet available bug fix will remove that option. NAV discovers static routes on a given router and adds them to the prefix database table.
Reserved is only useful if you use the mentioned IP adress scope view and would like to indicate which, if any, of your blocks that are reserved for special purposes and thus not available for use.
I notice we cannot add vlans directly; I assume this is implied from the vlan information added in the prefixes?
Yes.
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.
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.
Thanks for any comments or suggestions/tips!
- Vidar
-
Tim Chown -
Vidar Faltinsen