NAV Wiki

User Tools

Site Tools

Trace:
navscreenshots

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
navscreenshots [2007/09/16 07:27] – faltinnavscreenshots [2014/05/08 14:21] – Replaced more screenshots lizter
Line 1: Line 1:
- 
 ====== Introduction ====== ====== Introduction ======
-This document complements the [[NAVFeatures]] document. We here show a number of screenshots taken from running NAV version 3 installations (NTNU and UNINETT). Each screenshot is accompanied by text explaining the basic funtionality. We do not go +This document complements the [[NAVFeatures]] document. We here show a number of screenshots taken from running NAV version 3 installations (NTNU and UNINETT). Each screenshot is accompanied by text explaining the basic functionality. We do not go in detail, and not every aspect of NAV is covered.
-in detail, and not every aspect of NAV is covered. +
- +
  
  
Line 11: Line 7:
 In the example no alarms or messages are active, meaning operation is running fine: In the example no alarms or messages are active, meaning operation is running fine:
  
-{{screenshot:frontpage.png|}}+{{screenshot:4.0:frontpage.png?1000 }}
  
  
Line 17: Line 13:
 The toolbox contains all the NAV tools and is a good starting point for navigating in NAV: The toolbox contains all the NAV tools and is a good starting point for navigating in NAV:
  
-{{screenshot:toolbox.png|}}+{{screenshot:4.0:toolbox.png?1000}}
  
  
-====== 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:4.0:netmap.png?1000|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 55: Line 35:
 the server. You may do other searches as well, for example for an entire vlan, or all equipment in a room/area and more. the server. You may do other searches as well, for example for an entire vlan, or all equipment in a room/area and more.
  
-{{screenshot:networkexplorer.png|}}+{{screenshot:4.0:network_explorer.png?1000|}} 
  
  
 ====== The machine tracker ====== ====== The machine tracker ======
  
-NAV has historic data on the whereabouts of all the machines (IP adresses / mac adresses) in the network for the last 30 days.+NAV has historic data on the whereabouts of all the machines (IP adresses / mac adresses) in the network.
 You can locate a machine down to the switchport the machine is directly attached to. The machine tracker tool allows you to You can locate a machine down to the switchport the machine is directly attached to. The machine tracker tool allows you to
 search for the location of a given machine, or a set of machines. An example is given: search for the location of a given machine, or a set of machines. An example is given:
  
-{{screenshot:machinetracker.png|}}+{{screenshot:4.0:machine_tracker.png?1000|}}
  
  
 ====== Traffic measurements ====== ====== Traffic measurements ======
 +FIXME NAV does not use Cricket anymore
 +
 NAV does not collect traffic data itself, but depends on Cricket and RRD. NAV does however automate the process of NAV does not collect traffic data itself, but depends on Cricket and RRD. NAV does however automate the process of
 generating the Cricket configuration tree, which is a tedious process to keep up to date in large (and ever changing) generating the Cricket configuration tree, which is a tedious process to keep up to date in large (and ever changing)
Line 77: Line 60:
  
  
-====== 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:devcenter.png|}}+{{:screenshot:4.0:ipdevinfo.png?1000|}}
  
 +Switch ports and router ports on devices are displayed in a graphical fashion, grouped by modules.
  
 +{{:screenshot:4.0:sw_ports.png?500|}}
 +{{:screenshot:4.0:sw_port_act.png?500|}}
 ====== 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 91: Line 75:
 By following the links in the report you can drill down to new reports for further details. By following the links in the report you can drill down to new reports for further details.
  
-{{screenshot:equipmtypes.png|}}+{{screenshot:4.0:report2.png?1000|}}
  
 The next example gives an overview of all routers, switches, servers, etc, that are managed by the NAV installation. The next example gives an overview of all routers, switches, servers, etc, that are managed by the NAV installation.
 The number of attached modules and ports are shown with the possibility to drill down for details. The number of attached modules and ports are shown with the possibility to drill down for details.
  
-{{screenshot:dev_in_op.png|}}+{{screenshot:4.0:report1.png?1000|}}
  
 The router interface report shows all connected interfaces with respecting adress scope and description. The router interface report shows all connected interfaces with respecting adress scope and description.
 Note that static routes to external routers/firewalls are included. Note that static routes to external routers/firewalls are included.
  
-{{screenshot:gwports.png|}}+{{screenshot:4.0:report3.png?1000|}}
  
 The switch port report gives data on link, speed, duplex, port name, vlan and trunk information. The report also The switch port report gives data on link, speed, duplex, port name, vlan and trunk information. The report also
Line 107: Line 91:
 in interest. in interest.
  
-{{screenshot:swports.png|}}+{{screenshot:4.0:report4.png?1000|}}
  
  
  
-====== 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:
  
-{{screenshot:prefixmatrix.png|}}+{{screenshot:4.0:subnetmatrix.png?1000|}}
  
  
Line 129: Line 113:
 The status page gives an overview of all the active alarms. A historic view is also available. The status page gives an overview of all the active alarms. A historic view is also available.
  
-{{screenshot:status.png|}}+{{screenshot:4.0:status.png?1000|}}
  
  
Line 137: Line 121:
 (head of the) status page. Thus the NAV home page is the place to go for an updated (head of the) status page. Thus the NAV home page is the place to go for an updated
 view of the operational status of IT operations! view of the operational status of IT operations!
 +
 +The screen shot below shows a listing of historic messages:
 +
 +{{screenshot:4.0:messages.png?1000|}}
 +
 +====== Maintenance Tasks ======
  
 In the case of planned work NAV allows you to put equipment on maintenance for a given time period, In the case of planned work NAV allows you to put equipment on maintenance for a given time period,
 meaning NAV will not send any alarms regarding the device. meaning NAV will not send any alarms regarding the device.
  
-The screen shot below shows an example tab in the messages tool that lists historic messages by subject: +The screen shot below shows a listing of historic maintenance tasks:
- +
-{{screenshot:messages.png|}}+
  
 +{{screenshot:4.0:maintenance.png?1000|}}
  
 ====== Alert Profiles ====== ====== Alert Profiles ======
Line 154: Line 143:
 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.
  
-{{screenshot:alertprofiles.png|}} 
  
-====== Device Management ====== +{{screenshot:4.0:alertprofiles.png?1000|}} 
-The device management 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' + 
-for the devices NAV maintains important historic information. Typical examples are ordering, arrival, on shelf, +====== Device History ====== 
-in operation, error events, end of operations. Some of these events are detected automatically by the system, +The device history tool has a focus on the physical network devices identified by their unique 
-others require manual recordings.+serial number (as opposed to the logical devices identified by IP addresses). The Device History tool lets you 
 +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:
  
-http://domen.uninett.no/~faltin/nav/nav3screenshots/devmngt.png+The screenshot is outdated, please FIXME
  
-We may for instance have repeating error occurance for a device, where fixes are done by different staff. Device +{{screenshot:4.0:devicehistory.png?1000|}}
-management then serves as a place to get the overall picture.+
  
 +We may for instance have repeating error occurrence for a device, where fixes are done by different staff. Device
 +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:
  
  
-http://domen.uninett.no/~faltin/nav/nav3screenshots/editdb.png+{{screenshot:4.0:seeddb.png?1000|}}
  
 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).+
  
-http://domen.uninett.no/~faltin/nav/nav3screenshots/addbox.png+{{screenshot:4.0:seeddb_addip.png?1000|}}
  
 You may of course delete or edit the seed information you input. Here is an example where you can edit the known You may of course delete or edit the seed information you input. Here is an example where you can edit the known
 list of equipment types with corresponding data: list of equipment types with corresponding data:
  
-http://domen.uninett.no/~faltin/nav/nav3screenshots/edittypes.png+{{screenshot:3.3:edittypes.png|}}
  
  
Line 200: Line 191:
 The included example is therefore from a NAV v2 installation: The included example is therefore from a NAV v2 installation:
  
-http://domen.uninett.no/~faltin/nav/nav3screenshots/sysloganalyze.png+{{screenshot:4.0:syslog.png?1000|}}
  
  
Line 215: Line 206:
 can tune the information he would like to include on the status page: can tune the information he would like to include on the status page:
  
- +{{screenshot:4.0:statuspref.png?1000|}}
-http://domen.uninett.no/~faltin/nav/nav3screenshots/preferences.png +
navscreenshots.txt · Last modified: by lizter
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki