This is an old revision of the document!
Netmap was introduced in NAV 3.5 written in Java and replaced the old traffic map (vlanplot). Netmap got rewritten from scratch using open standards as HTML, JavaScript and SVG (Scalable Vector Graphics in XML markup).
Netmap is based on the D3JS library, and uses its ForceBasedLayout-engine for finding the optimal graphical layout for the network topology. Netmap should work in all new common browsers that support SVG (IE9 and newer), Firefox (3.5 (really recommend a newer version, as the firefox javascript engine is having performance issues) and up), Chrome (auto updates, testing with Chromium in Debian Squeeze at least). Opera has some issues that we will look into later.
Netmap has these features (in no particular order):
NOTE: Icons for the following categories are included GSW, GW, OTHER, SRV, SW, WLAN, EDGE and the fictive category ELINK. If you have other categories, put an icon with the category name in $NAV_ROOT/share/htdocs/images/netmap/ in the png format. Note: use lower case filename of the category name.
The netmap is available from the toolbox.
Netmap consists of two navigation bars, one on each side of the screen, and the map itself. The navigation bars can be toggled by clicking the “«” or “»” links. You can toggle fullscreen with CTRL+SHIFT+F.
The load colors1) on edges represent traffic load based on the link's capacity, and the link's thickness represents the link speed.
The left navigation bar has options for filtering and controlling the behaviour of the map.
This searches for the name of a netbox and centers the map on it. If the search hits several netboxes the map will center on the first.
Zoom to extent will try to position the whole graph in the center of the view port and scale out so you can see it.
Toggle if you want to see layer 2 or layer 3 topology 2).
Choose what categories of netboxes you want to see.
Open the traffic load scale used in netmap in a popup.
A drop down / combi box which shows your available views. Your own views are listed at the top and public views are listed below it. The selected view is always rendered as the first choice in the drop down.
If the view has a description, it will be shown below the “Save” and “Favorite” buttons.
The save button is a button for updating changes to a selected view, if the view isn't saved it will trigger a “Save new as”. You probably also noticed the “+” and “-” buttons on the right side, the “+” button is always known as “Save new as” and the “-” button is known for “Delete active view”. Careful, there is no confirmation dialog when deleting a view and as an administrator you are allowed to delete any view!
A heart will popup if the selected view is the user's favorite view.
= Save new view =
Popups up a modal form, where you can enter title for the view (shown in dropdown) and a longer description if that is needed. A checkbox is available to select if the view should be open for other users in netmap or private.
This is the view that will render with a Netbox or Link template for a selected netbox or link. If your an administrator, a link to the administration area will be available at the bottom here. Depending on which network topology layer you have active, it will render a bit different information.
Renders the sysname and it's management IP first together with the “pping” indicator of the netbox is up or down. (this is atm only loaded at network topology graph load, in the future this will automagically refresh)
A checkbox for knowing if the node's position is fixed or unfixed in the graph. Fixed positions is what get's saved when your saving a view.
Category is the netbox's category.
(Missing atm: Device type ;-( )
Room and location information.
If layer2, render VLAN information and option to select a vlan. When clicking on a VLAN, it will mark other nodes and links that is member of the current VLAN in it's broadcast domain.
If layer3, render netident and netdescription together with active prefixes over this link.
Renders from netbox [interface] to netbox [interface]
Link speed of the link.
Traffic in and out. (from: in , out: to) Example: netbox A and B, a is listed first. That means you will read it like this: netbox A A is receiving 200mbps in and transfers 400mbps out to B.
1. Rendering is horrible slow This kind of problem can be two things (or both). Using an old outdated browser with poor javascript performance or having a old computer. (the layout algorithm is quite CPU intensive). Chrome is known to have the best javascript engine, so we recommend the use of chrome webbrowser.