User Tools

Site Tools


navscreenshots

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
navscreenshots [2014/05/08 16:21]
lizter Replaced more screenshots
navscreenshots [2014/05/08 16:27] (current)
lizter Reworked some text to reflect the screenshot changes
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:​4.0:​network_explorer.png?​1000|}} {{screenshot:​4.0:​network_explorer.png?​1000|}}
Line 122: 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:​4.0:​messages.png?​1000|}} {{screenshot:​4.0:​messages.png?​1000|}}
Line 131: 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:​4.0:​maintenance.png?​1000|}} {{screenshot:​4.0:​maintenance.png?​1000|}}
Line 153: Line 151:
  
 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:​4.0:​devicehistory.png?​1000|}} {{screenshot:​4.0:​devicehistory.png?​1000|}}
Line 175: Line 171:
  
 {{screenshot:​4.0:​seeddb_addip.png?​1000|}} {{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 187: Line 178:
 and structured in a dedicated database. The syslog analyzer tool serves as a front end to this database and gives you a and structured in a dedicated database. The syslog analyzer tool serves as a front end to this database and gives you a
 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. 
-The included example is therefore from a NAV v2 installation:​ 
  
 {{screenshot:​4.0:​syslog.png?​1000|}} {{screenshot:​4.0:​syslog.png?​1000|}}
navscreenshots.1399558884.txt.gz · Last modified: 2014/05/08 16:21 by lizter