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
Next revision
Previous revision
navscreenshots [2014/05/08 15:56]
lizter Swapped some screenshots that were from 3.3 to 4.0
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 113: 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 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:​3.3:​maintenance.png|}}+{{screenshot:​4.0:​maintenance.png?1000|}}
  
 ====== Alert Profiles ====== ====== Alert Profiles ======
Line 143: 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.
  
-This is an old screenshot, please FIXME 
  
-{{screenshot:​3.3:​alertprofiles.png|}}+{{screenshot:​4.0:​alertprofiles.png?1000|}}
  
  
Line 155: Line 152:
 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:​3.3:devmngt.png|}}+
  
 We may for instance have repeating error occurrence 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
Line 176: 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 189: 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 207: 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.1399557364.txt.gz · Last modified: 2014/05/08 15:56 by lizter