navscreenshots
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 | ||
|
navscreenshots [2010/03/09 06:59] marboi |
navscreenshots [2012/10/19 06:22] bredal [IP Device Info] |
||
|---|---|---|---|
| Line 16: | Line 16: | ||
| - | ====== The traffic map ====== | + | ====== Traffic maps ====== |
| - | The traffic map tool (also referred to as network load map or vlanplot) gives a good overview of the network topology. It displays all the routers with interconnected links. Popups on links and nodes give detailed information (this example shows the Northern part of the UNINETT network): | + | |
| - | {{screenshot:trafficmap_uninord.png|}} | + | There are two traffic maps tools in NAV; Netmap and Geomap. More info will follow later. |
| - | In the example the links are black, indicating that traffic load is not available. At the time of writing we have not | + | ===== Netmap ===== |
| - | yet ported the function that retrieves the load data from RRD (todo soon). To illustrate what load visualization will look | + | |
| - | like, we give three examples from a version 2 installation at NTNU. | + | |
| - | The first shows the layer 3 network. Each link is | + | {{:screenshot:netmap.png|NAV's netmap tool}} |
| - | logically divided in two, where the part nearest a given router shows the load **out** from that router. The scale may | + | |
| - | be either absolute or relative to the total bandwidth. The default view displays the current (last 5 minute average) | + | |
| - | traffic pattern, but you can easily swap to another timeframe. | + | |
| - | {{screenshot:trafficmap_ntnu.png|}} | + | ===== Geomap ===== |
| - | The top view only shows the subnets that interconnects the routers, i.e. the network core. To see all the connected | + | {{:screenshot:geomap_trd.png|NAV's Geomap tool}} |
| - | subnets you need to drill down to a "routercentric view". By clicking on a router in interest you will enter a new | + | |
| - | view that shows the connected subnets and neigboring routers. Load is of course still visualized: | + | |
| - | + | ||
| - | {{screenshot:trafficmap_rfb-gw.png|}} | + | |
| - | + | ||
| - | A further drill down on a particular subnet/vlan is also possible. The example shows vlan 190 at NTNU as it is seen from rfb-sw. | + | |
| - | You may explore the topology and traffic load further by clicking on other switches and routers and thus walk around in the | + | |
| - | network (note that spanning tree blocked ports are indicated as seen on the link to kjemi-sw). | + | |
| - | + | ||
| - | {{screenshot:trafficmap_rfb-sw.png|}} | + | |
| Line 74: | Line 58: | ||
| - | ====== The device center ====== | + | ====== IP Device Info ====== |
| - | The device center is basically an overview page showing lots of collected information regarding a particular IP device. | + | IP device info summarizes most of what NAV knows about a single IP device (or arbitrary IP address within your network) on a single page. |
| - | In the case of switches | + | |
| - | all switch ports with corresponding speed, duplex, link etc is also shown: | + | |
| - | {{screenshot:3.3:devcenter.png|}} | + | {{:ipdevinfo-ss.png?600|}} |
| + | Switch ports and router ports on devices are displayed in a graphical fashion, grouped by modules. | ||
| + | {{:screenshot:swportstatus.png?300|}} | ||
| + | {{:screenshot:swportactivity.png?300|}} | ||
| ====== Reports ====== | ====== Reports ====== | ||
| NAV has a number of reports (and with a little knowledge it is easy to make new reports). We give four report examples below. | NAV has a number of reports (and with a little knowledge it is easy to make new reports). We give four report examples below. | ||
| Line 108: | Line 93: | ||
| - | ====== IP address scope - graphical view ====== | + | ====== Subnet matrix ====== |
| For large networks the task of maintaining the total IP address scope may be a challenge in itself. It is useful | For large networks the task of maintaining the total IP address scope may be a challenge in itself. It is useful | ||
| - | to have an overview of all the subnets in operation, and whats more, how full they are, i.e. how many machines | + | to have an overview of all the subnets in operation, and what's more, how full they are, i.e. how many machines |
| - | do they contain. NAV introduces a tabular view that gives an excellent overview on a single page: | + | do they contain. NAV introduces the subnet matrix that gives an excellent overview on a single page: |
| + | |||
| + | FIXME Old screenshot | ||
| {{screenshot:3.3:prefixmatrix.png|}} | {{screenshot:3.3:prefixmatrix.png|}} | ||
| Line 155: | Line 142: | ||
| Note that alarms from external systems may be sent to NAV and thus included in the alert profile setup. | Note that alarms from external systems may be sent to NAV and thus included in the alert profile setup. | ||
| + | |||
| + | This is an old screenshot, please FIXME | ||
| {{screenshot:3.3:alertprofiles.png|}} | {{screenshot:3.3:alertprofiles.png|}} | ||
| - | ====== Device Management ====== | + | ====== Device History ====== |
| - | The device management tool has a focus on the physical network devices identified by their unique | + | The device history tool has a focus on the physical network devices identified by their unique |
| - | serial number (as opposed to the logical devices identified by IP addresses). By registering 'milestone events' | + | serial number (as opposed to the logical devices identified by IP addresses). The Device History tool lets you |
| - | for the devices NAV maintains important historic information. Typical [[http://www.college-paper.org/custom-essay.html | college essay]] examples are ordering, arrival, on shelf, in operation, error events, end of operations. Some of these events are detected automatically by the system, others require manual recordings. | + | see the history of devices, register error events or delete outdated modules. |
| The example shows the tab for registering a particular error event: | The example shows the tab for registering a particular error event: | ||
| + | |||
| + | The screenshot is outdated, please FIXME | ||
| {{screenshot:3.3:devmngt.png|}} | {{screenshot:3.3:devmngt.png|}} | ||
| - | We may for instance have repeating error occurance for a device, where fixes are done by different staff. Device | + | We may for instance have repeating error occurrence for a device, where fixes are done by different staff. Device |
| - | management then serves as a place to get the overall picture. | + | history then serves as a place to get the overall picture. |
| - | ====== Edit Database ====== | + | ====== Seed Database ====== |
| NAV does not fully autodiscover the network. You need to seed the database with key information, the most important | NAV does not fully autodiscover the network. You need to seed the database with key information, the most important | ||
| being the IP address and SNMP community string of the devices you would like NAV to manage. The home page og | being the IP address and SNMP community string of the devices you would like NAV to manage. The home page og | ||
| - | the edit database tool looks like this: | + | the seed database tool looks like this: |
| + | |||
| + | The screenshots of Seed Database are outdated, please FIXME | ||
| {{screenshot:3.3:editdb.png|}} | {{screenshot:3.3:editdb.png|}} | ||
| Below follows an example of the form used to add a new box (ip device) to NAV. Note that we allow bulk import | Below follows an example of the form used to add a new box (ip device) to NAV. Note that we allow bulk import | ||
| - | of seed data from a text file format. This is useful if you have a large number of devices in your network | + | of seed data from a text file format. This is useful if you have a large number of devices in your network. |
| - | (or if you are migrating from a NAV v2 installation). | + | |
| {{screenshot:3.3:addbox.png|}} | {{screenshot:3.3:addbox.png|}} | ||
navscreenshots.txt · Last modified: 2014/05/08 14:27 by lizter
Page Tools
