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
Next revision Both sides next revision
netmap [2012/09/17 11:28]
norangshol Updated the first part, still work in progress
netmap [2012/09/18 11:33]
bredal [Map]
Line 4: Line 4:
  
 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 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 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 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.  ​
 +
 +===== Features =====
 +
  
 Netmap has these features (in no particular order): Netmap has these features (in no particular order):
Line 12: Line 15:
    * Filtering of netboxes based on categories. These categories are set from the categories you have in the database. ​    * 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) ​    * Filtering orphans (netboxes not linking to anything) ​
-   ​* ​* Note: elink is a fictive category, and Netmap itself detects where the elink should be based on NAV's known topology.  +     * Note: elink 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. +     ​* 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    * 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 ;-)    * 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 ;-)
Line 21: Line 24:
    * Fix or unfix all node positions. (this is position metadata that is saved to a view)    * Fix or unfix all node positions. (this is position metadata that is saved to a view)
    * Views    * Views
-   ​* ​* User specific views and possibility to share em among other users +     * User specific views and possibility to share em among other users 
-   * * Delete your own views +     ​* Delete your own views 
-   * * Update current view +     ​* Update current view 
-   * * Create new view from selected view (incase you want a modify a view that isn't yours) +     ​* Create new view from selected view (incase you want a modify a view that isn't yours) 
-   * * Select a favorite view +     ​* Select a favorite view 
-   * * Administrator can set a global favorite view for users who does not have an favorite view selected.+     ​* 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.     * Different info templates for selected netbox or selected link. 
    * Traffic gradient popup (will be nice when RRD/traffic load is refreshed every x min.     * Traffic gradient popup (will be nice when RRD/traffic load is refreshed every x min. 
Line 34: Line 37:
 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  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.  $NAV_ROOT/​share/​htdocs/​images/​netmap/​ in the png format. Note: use lower case filename of the category name. 
- 
  
 ===== Brief user guide===== ===== Brief user guide=====
  
-The netmap is available from the toolbox. ​Clicking ​it will launch ​the Java applet.+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 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 ==== 
 + 
 +  * Nodes can be positioned to your liking by clicking and dragging it. 
 +  * To view information about a node or a link, just click on it. 
 +  * You may zoom the map by using the scroll-wheel on your mouse. 
 + 
 + 
 +==== Left navigation bar ==== 
 + 
 +Starting on the left navigation bar, your presented with a: 
 + 
 + 
 + 
 +=== Searchbox === 
 + 
 +Type in part of the sysname of the box your looking for, it run loop thru it dataset and stop on the first match it hits and fetch it's graph position and translate the node to be centered in the graph. At the moment the search is quite simple, but in the _future_ ​it will have support for finding the bounding box for all matches and translate the bounding box to it's view port and set correct zoom level. Zoom to extent will try it's best to position the bounding box for the whole graph in the center of the view port and scale out so you can see it. A tip is to just click it a few times so it gets it right ;-) (or wait for the layout algorithm to finish)  
 + 
 +=== Layer box === 
 + 
 +Radio button to toggle which network topology view you want to view, either layer 2 or layer 3.  
 +Shouldn'​t require any further explanation,​ if you need .. look into the [[http://​en.wikipedia.org/​wiki/​OSI_model|OSI model]].  
 + 
 +=== Categories === 
 + 
 +You can run filters on the loaded network topology graph, pr. default the GSW,​GW,​SW,​OTHER,​WLAN,​SRV,​ and EDGE categories are selected on by default. Here you can deactivate active filters, and nodes of the deactivated filters will disappear. You can toggle this filters back and forth without having to reload the network topology graph, it will only '​bounce'​ the layout algorithm to make sure the nodes aren't colliding.  
 + 
 +== Filter options , orphans == 
 + 
 +As you play around with filters, or NAV '​topology analyzer'​ ([[http://​nav.uninett.no/​backendprocesses#​ipdevpoll|ipdevpoll]] / [[http://​nav.uninett.no/​backendprocesses#​topology|topology]]) there is certain to render single instance nodes which is nodes who has no relations to any other nodes in the current state of active filters. ​ Here you have the option to disable or enable em.  
 + 
 +=== Mark by position === 
 + 
 +Option to mark other related nodes that are either 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 === 
 + 
 +If your on either running a old version of Firefox (known to have poor javascript performance in our experience) or equipped with a «bad computer from the past», you have a option to pause the layout algorithm here.  
 + 
 +You can resume it by drag and dropping a node, unfix a node, unfix all nodes etc.  
 + 
 +=== UI options === 
 + 
 +  * Show topology errors, option to render network topology errors like a link between two netboxes who doesn'​t run on the same interface speed which might cause network congestion etc 
 + 
 +== Mouseover options == 
 + 
 +Enable or disable auto clicking of a node when simply hovering a link or node. This can also be toggled with the keyboard shortcuts «n» or «l» (lowercase of L).  
 + 
 +=== Traffic gradient === 
 + 
 +A button to open the traffic load scale used in netmap in a popup.  
 + 
 + 
 +==== Right navigation bar ==== 
 + 
 +=== Available views === 
 + 
 +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.  
 + 
 +== 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
  
-The applet will take some time to loaddepending on the scale of your network. If it takes more than 10 seconds, please ensure ​that your rrd_file-table has an index on the value-field,​ if not create ​it ( CREATE INDEX rrd_file_value ON rrd_file(value);​ ).+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
  
-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. These category-checkboxes define what kind of netboxes that are visible on screen. Typically you'd want to select GW, GSW and SW, but thats up to you. Then select what kind of linktypes you want to see. 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. 
  
-Every element in the page can be clicked for more information about it, both the netboxes themselves and the edges (links) that connect them.+== Link view ==
  
-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".+If layer3, render netident ​and netdescription together with active prefixes over this link
  
-When you are satisfied with how the network has spread it self, you can freeze the layout in the "​Actions"​ menu.+Renders from  netbox [interface] to netbox [interface]
  
-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.+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 ===== ===== Troubleshooting =====
 1. Rendering is horrible slow 1. Rendering is horrible slow
-This kind of problem can be two things (or both). ​Either cpu-bound problems, ​or gpu-bound problemsThe 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 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