netmap
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
netmap [2011/04/07 17:03] faltin [User guide] |
netmap [2012/09/17 11:28] norangshol Updated the first part, still work in progress |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Netmap ====== | + | ====== Netmap - the network weather map ====== |
| - | {{tools:vlanplot.png|}} Netmap is new in NAV 3.5 and replaces the old [[trafficmap|TrafficMap]] (vlanplot). | + | {{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 6. Java 5 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 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: | + | Netmap has these features (in no particular order): |
| - | * Dynamic generation of network-topology based upon prefixes for gwports, and the to_swportid field for swports (discovered by networkDiscovery). | + | * 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 | + | * Fetching of rrd-load data for links between netboxes (links are colored by relative usage for it's interface speed) |
| - | * 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. | + | * 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 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. | + | * Filtering orphans (netboxes not linking to anything) |
| - | * 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. | + | * * 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. | ||
| + | * 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. If you have other categories, put an icon with the category name in /usr/local/nav/apache/webroot/netmap/applet/media (or similar if custom paths are used) in the png format. EDGE type is to be included in NAV 3.4.1 | + | 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. | ||
| Line 36: | Line 55: | ||
| 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 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 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). | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
netmap.txt · Last modified: 2012/09/18 12:56 by bredal
Page Tools
