User Tools

Site Tools


netmap

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
netmap [2008/04/29 15:14]
klette
netmap [2012/09/18 12:46]
bredal [Right navigation bar]
Line 1: Line 1:
-====== Netmap ======+====== Netmap ​- the network weather map ======
  
-Netmap ​is the vlanPlot ​(TrafficMapreplacement currently under development.+{{tools:​vlanplot.png|}} ​Netmap ​was introduced in NAV 3.5 written in Java and replaced ​the old traffic map ([[trafficmap|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 prefuse ​library, and uses its ForceBasedLayout-engine for finding the optimal graphical layout for the network. ​The netmap itself is an Java Applet, and should ​run on both Java 5 and Java 6Java is required to build the Netmap-applet.+Netmap is based on the [[http://​d3js.org|D3JS]] ​library, and uses its [[https://​github.com/​mbostock/​d3/​wiki/​Force-Layout|ForceBasedLayout-engine]] for finding the optimal graphical layout for the network ​topologyNetmap ​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 
  
-Included in NAV 3.4 is a beta-version of Netmap, it includes these features:+===== Features =====
  
-   * Dynamic generation of network-topology based upon prefixes for gwports, and the to_swportid field for swports (discovered by networkDiscovery). 
-   * Fetching of rrd-load data for links between netboxes 
-   * View load based upon relative usage or on fixed rates (0-100, 100-512,​512-2048,​2048-4096,>​4096 Mbit/s) - the rates are hardcoded, but can be made configurable on high demand. 
-   * Filtering of netboxes based on categories. These categories are set from the categories you have in the database. 
-   * Searching. One can search after netboxes based on sysname, room or ip. 
-   * Freezing of layout to preserve cpu-load. The layout-engine does require some cpu-power, so enabling this when your satisfied with the layout is a good idea. 
  
 +Netmap has these features (in no particular order):
  
-Known issues:+   * Dynamic generation of network-topology based upon prefixes for gwports, and the to_swportid field for swports (discovered by [[backendprocesses#​ipdevpoll|ipdevpoll inventory job]] and [[backendprocesses#​topology|topology]] (cronjob running every hour)). 
 +   * Fetching of rrd-load data for links between netboxes (links are colored by relative usage for it's interface speed) 
 +   * Links capacity between netboxes shown with fixed rates (0-100, 100-512,​512-2048,​2048-4096,>​4096 Mbit/s) on it's line-width/​weight. 
 +   * Filtering of netboxes based on categories. These categories are set from the categories you have in the database.  
 +   * Filtering orphans (netboxes not linking to anything)  
 +     * Noteelink is a fictive category, and Netmap itself detects where the elink should be based on NAV's known topology.  
 +     * Note2: can't save metadata / positions of elink nodes, since there is no relation to them as it is a fictive node.  
 +   * Searching. One can search after netboxes based on sysname 
 +   * Option to pause the layout engine to preserve cpu-load. This should not be needed as the layout engine should stabilize the graph rather quickly in a newer browser and modern PC. In case your living in the past, there'​s an option to pause it ;-) 
 +   * Toggle sidebars by a click of a mouse button.  
 +   * Toggle '​fullscreen'​ by clicking CTRL+SHIFT+F (hides sidebars and NAVs header and footer) 
 +   * Mark nodes located in same room or location as the selected node.  
 +   * Fix or unfix all node positions. (this is position metadata that is saved to a view) 
 +   * Views 
 +     * User specific views and possibility to share em among other users 
 +     * Delete your own views 
 +     * Update current view 
 +     * Create new view from selected view (incase you want a modify a view that isn't yours) 
 +     * Select a favorite view 
 +     * Administrator can set a global favorite view for users who does not have an favorite view selected. 
 +   * Different info templates for selected netbox or selected link.  
 +   * Traffic gradient popup (will be nice when RRD/traffic load is refreshed every x min.  
 +   * Show topology errors (mark links/​nodes) red if there'​s something unusual in your network topology. ie, different interface speeds between the links can cause to network congestion 
 +   * Mouse over UI actions, «Auto-clicks» a node or link by simply hoovering em.
  
 +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. 
  
-===== Quickstart ​=====+===== Brief user guide=====
  
-The netmap ​should be available ​at the bottom of your toolbox ​after a successful install, clicking it will launch the applet.+The netmap ​is available ​from the toolbox.
  
-The applet will take some time to load, depending on the scale of your network. If it takes more than 10 secondsplease ensure that your rrd_file-table has an index on the value-fieldif not create it ( CREATE INDEX rrd_file_value ON rrd_file(value);​ ).+Netmap consists ​of two navigation barsone on each side of the screenand the map itself. The navigation bars can be toggled by clicking the "<<"​ or ">>"​ links. ​ You can toggle fullscreen with CTRL+SHIFT+F.
  
-The first thing you see will be a blank page with a menubar. If you select the "Filters" ​menu you've got two choices, Categories and Linktypes. Linktypes is not enabled in the beta, so you'll have to make due with the Categories-menu. These category-checkboxes define what kind of netboxes that are visible ​on screen. Typically you'd want to select GWGSW and SW, but thats up to you. What you'll see now is a bunch of nodes appearing at the center of the screen and moving outwards. Netmap now applies physical properties to the netboxes and applies negative gravity on each of them. You can zoom in and out of the map by holding your right mousebutton and moving your mouse up and down. You can tell netmap to try zooming for best fit by double-clicking your right mouse-button. Panning the map is done by holding the left mouse-button and moving ​the mouse.+The load colors((Click ​"Show gradient" to get an overview of what the colors indicate)) ​on edges represent traffic load based on the link's capacity, and the link's thickness represents ​the link speed 
 +==== Map ====
  
-Every element in the page can be clicked for more information about itboth the netboxes themselves and the edges (links) that connect them.+  * Nodes can be positioned to your liking by clicking and dragging it. 
 +  * To view information about a node or a linkjust click on it. 
 +  * You may zoom the map by using the scroll-wheel on your mouse.
  
-The load colors on the edges defaults to fixed-rate colors. To change this go to the "​Visualization"​-menu and select "Show load based on relative usage"​. 
  
-When you are satisfied with how the network has spread it self, you can freeze the layout in the "​Actions"​ menu.+==== Left navigation bar ====
  
-Searching is done in the text field on the menu bar. Netmap starts searching as soon as you type, and tries to zoom in on the objects that match. So, if you would like to zoom into a part of your network, say every netbox in 10.0.10.*, you'd type 10.0.10. in the search field, and netmap should zoom into that section. The same applies for sysnames and rooms.+The left navigation ​bar has options for filtering ​and controlling ​the behaviour ​of the map.
  
-===== Troubleshooting ​===== +=== Searchbox ​===
-1. Rendering is horrible slow +
-This kind of problem can be two things (or both). Either cpu-bound problems, or gpu-bound problems. The CPU-part is hard to combat except with filtering out more devices. The GPU-bound problems can cause massive cpu-load also though (fallback to software-rendering). For these kind of problems try various combinations of http://​java.sun.com/​j2se/​1.5.0/​docs/​guide/​2d/​flags.html in the java-plugin control-panel (under Runtime-settings).+
  
 +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 ===
  
 +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.
  
 +=== Layer box ===
  
 +Toggle if you want to see layer 2 or layer 3 topology (([[http://​en.wikipedia.org/​wiki/​OSI_model|OSI model]])).
 +
 +=== Categories ===
 +
 +Choose what categories of netboxes you want to see.
 +
 +=== Filter options ===
 +
 +  * **Filter orphans**: Uncheck this to hide nodes with no links to other nodes.
 +  * **Mark by position**: Mark nodes that are located in the same room or location. This is shown by drawing a red circle around the nodes who are related to the selected node.
 +  * **Pause force algorithm**:​ Pause the layout algorithm by clicking the button. A green icon indicates active algorithm, a red an inactive algorithm. Resume it by drag and dropping a node, unfix a node, unfix all nodes or clicking the button again.
 +  * **Fix or unfix all nodes**: Set all nodes to fixed or unfixed. Fixed nodes will not move when running the algoritm.
 +
 +=== UI options ===
 +
 +  * **Show topology errors**: for instance mark links with differing speed set on the netbox inerfaces
 +  * **Mouseover options**: Enable or disable auto selection when hovering a link or node. This can also be toggled with the keyboard shortcuts «n» or «l» (lowercase of L). 
 +
 +=== Traffic gradient ===
 +
 +Open the traffic load scale used in netmap in a popup. ​
 +==== Right navigation bar ====
 +
 +=== Views ===
 +
 +Choose active view from the drop-down menu.
 +
 +== Actions ==
 +  * The save button will update a selected view. If the view isn't saved it will trigger a "Save new as".
 +  * The "​+"​ button will create and save a new view.
 +  * The "​-"​ button will delete the active view.
 +  * The "​Favourite"​ button will mark this view as your favourite. This view will then be the default view. The favourite view is marked with a heart.
 +
 +== Save new view ==
 +
 +Enter a title and optionally a description for the new view. You can also set if the view is public or not.
 +
 +=== Map info ===
 +
 +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. ​
 +
 +== Netbox view ==
 +
 +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. ​
 +
 +
 +== Link view ==
 +
 +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. 
 +===== Troubleshooting =====
 +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. ​
  
  
netmap.txt · Last modified: 2012/09/18 12:56 by bredal