Differences

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

--- statustool [2007/10/07 12:27] – faltin
+++ statustool [2011/04/08 14:01] (current) – [Back-end processes] faltin
@@ Line 2: / Line 2: @@
 {{tools:status.png|}} The status tool gives an overview on operations; i.e. that all the network components and services are up and running.
 ===== Back-end processes =====
-NAV has a number of background processes that monitors the operational status of the network. They are relevant for the
+NAV has four background processes that monitors the operational status of the network. It is the events triggered from these monitors that are displayed in the status tool. The four monitors are:
-status tool display:
+  - The status monitor ([[backendprocesses#pping|pping]]) monitors basic - but fundamentally important - reachability. Are all the devices alive or are some down? \\ Since NAV has knowledge of topology, root cause in a larger breakdown can also be pinpointed. NAV distinguishes between a device being down or a device being in shadow of a more central device that is down (it is actually [[backendprocesses#eventengine|the event engine]] that is responsible for this correlation).
+  - The service monitor ([[backendprocesses#servicemon|servicemon]]) monitors services. A number of services are supported (ssh, http, ssl, imap, pop3, smtp, dns, rpc, samba, dc and more).
+  - The module monitor (modulemon within [[backendprocesses#ipdevpoll|ipdevpoll]]) monitors the operations of modules within a switch stack or within a chassis.
+  - The threshold monitor ([[backendprocesses#thresholdmon|thresholdmon]]) monitors the RRD data and send alarms if a threshold on a given value is exceeded.
-  * [[backendprocesses#the_status_monitor_pping|The status monitor]] monitors basic (and fundamentally important) reachability. Are the devices alive? Since NAV has knowledge of topology, NAV can pinpoint root cause in the case of a larger breakdown. This is done by distinguishing between a device being down or a device being in shadow of a more central device that is down.
+For more information on the event and alarm system, see [[eventandalertsystem|here]].
-  * [[backendprocesses#the_service_monitor_servicemon|The service monitor]] monitors services. A number of services are supported (ssh, http, ssl, imap, pop3, smtp, dns, rpc, samba, dc and more).
-  * The module monitor (within [[backendprocesses#getdevicedata|gDD]]) monitors the operations of modules within a switch stack or within a chassis.
-  * [[backendprocesses#the_threshold_monitor_thresholdmon|The threshold monitor]] monitors the RRD data and send alarms if a threshold on a given value is exceeded.
 ===== The status page =====
-{{screenshot:status.png?800|The status tool }}
+{{screenshot:3.3:status.png|The status tool }}
 The status tool gives an overview of all the active alarms.
-The display is divided into several sections, this is per-user configurable using the preferences tool from the tool bar. The default sections include:
+The display is divided into several sections, this is per-user configurable using [[navhome#preferences|the preferences tool]] from the tool bar. The default sections include:
   * IP devices down
@@ Line 28: / Line 29: @@
   * Services down
-In addition using the preferences tool (reached from the NAV bar) you may add:
+In addition using [[navhome#preferences|the preferences tool]] (reached from the NAV bar) you may add:
   * Thresholds exceeded
@@ Line 36: / Line 37: @@
 For each section the NAV user may also choose to filter out certain alarms based on either organization, category (GW/GSW/SW/SRV etc) or state (up/down/shadow).
-{{screenshot:preferences.png?500|Status page preferences}}
+{{screenshot:3.3:preferences.png|Status page preferences}}
 ===== History =====