NAV Wiki

User Tools

Site Tools

Trace: • navref_131119
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
navscreenshots [2011/04/07 18:36] – [The device center] faltinnavscreenshots [2014/05/08 14:27] (current) – Reworked some text to reflect the screenshot changes lizter
Line 7: 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:3.3:frontpage.png| }}+{{screenshot:4.0:frontpage.png?1000 }}
  
  
Line 13: 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:3.3:toolbox.png|}}+{{screenshot:4.0:toolbox.png?1000}}
  
  
Line 22: Line 22:
 =====  Netmap ===== =====  Netmap =====
  
-{{:screenshot:netmap.png|NAV's netmap tool}}+{{:screenshot:4.0:netmap.png?1000|NAV's netmap tool}}
  
 ===== Geomap ===== ===== Geomap =====
Line 31: Line 31:
 ====== The network explorer ====== ====== The network explorer ======
 The network explorer complements the traffic map. It does not show load, nor does it show layer 3 topology, but it has The network explorer complements the traffic map. It does not show load, nor does it show layer 3 topology, but it has
-a superior overview of the layer 2 network. You can explore the network by clicking on a router interface or switch port in interest and thus open a new branch to the tree. You may also search for a node in the network. In the example we have searched for +a superior overview of the layer 2 network. You can explore the network by clicking on a router interface or switch port in interest and thus open a new branch to the tree. You may also search for a node in the network. You may do searches as well, for example for an entire vlan, or all equipment in a room/area and more.
-the server 'ludvig'. The server was found and the relevant part of the topology was expanded to illustrate the path to +
-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|}}
  
  
Line 45: Line 43:
 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:3.3: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 58: Line 58:
  
  
-====== The IP Device Info ====== +====== IP Device Info ====== 
-The IP device info 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:+
  
-This is an old screenshot, please FIXME +{{:screenshot:4.0:ipdevinfo.png?1000|}}
- +
-{{screenshot:3.3:devcenter.png|}}+
  
 +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 74: Line 73:
 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:3.3:equipmenttypes.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:3.3: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:3.3: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 90: Line 89:
 in interest. in interest.
  
-{{screenshot:3.3: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:3.3:prefixmatrix.png|}}+{{screenshot:4.0:subnetmatrix.png?1000|}}
  
  
Line 112: Line 111:
 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:3.3:status.png|}}+{{screenshot:4.0:status.png?1000|}}
  
  
Line 121: Line 120:
 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:+The screen shot below shows an archived message:
  
-{{screenshot:3.3:messages.png|}}+{{screenshot:4.0:messages.png?1000|}}
  
 ====== Maintenance Tasks ====== ====== Maintenance Tasks ======
Line 130: Line 129:
 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 a listing of historic maintenance tasks:+The screen shot below shows an archived maintenance task:
  
-{{screenshot:3.3:maintenance.png|}}+{{screenshot:4.0:maintenance.png?1000|}}
  
 ====== Alert Profiles ====== ====== Alert Profiles ======
Line 142: Line 141:
 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:3.3:alertprofiles.png|}} 
  
 +{{screenshot:4.0:alertprofiles.png?1000|}}
  
-====== Device Management ====== + 
-The device management tool has a focus on the physical network devices identified by their unique +====== Device History ====== 
-serial number (as opposed to the logical devices identified by IP addresses). By registering 'milestone events' +The device history tool has a focus on the physical network devices identified by their unique 
-for the devices NAV maintains important historic information. Typical examples are ordering, arrival, on shelf, +serial number (as opposed to the logical devices identified by IP addresses). The Device History tool lets you 
-in operation, error events, end of operations. Some of these events are detected automatically by the system, +see the history of devices, register error events or delete outdated modules.
-others require manual recordings.+
  
 The example shows the tab for registering a particular error event: The example shows the tab for registering a particular error event:
  
-{{screenshot:3.3:devmngt.png|}}+{{screenshot:4.0:devicehistory.png?1000|}}
  
-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:
  
-{{screenshot:3.3: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).+
  
-{{screenshot:3.3: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 +
-list of equipment types with corresponding data: +
- +
-{{screenshot:3.3:edittypes.png|}}+
  
  
Line 186: Line 179:
 structured interface to all the collected syslog messages. structured interface to all the collected syslog messages.
  
-The syslog analyzer is ported to NAV v3, but our example installation has no data at the time of writing. +{{screenshot:4.0:syslog.png?1000|}}
-The included example is therefore from a NAV v2 installation: +
- +
-{{screenshot:3.3:sysloganalyze.png|}}+
  
  
Line 204: Line 194:
 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:3.3:preferences.png|}}+{{screenshot:4.0:statuspref.png?1000|}}
navscreenshots.1302201414.txt.gz · Last modified: by faltin
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki