This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
statustool [2007/10/07 12:31] faltin |
statustool [2007/10/08 20:39] 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. | {{tools:status.png|}} The status tool gives an overview on operations; i.e. that all the network components and services are up and running. | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
Line 11: | Line 20: | ||
- | * [[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. | + | - [[backendprocesses#pping|The status monitor]] (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). |
- | * [[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). | + | - [[backendprocesses#servicemon|The service monitor]] (servicemon) 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. | + | - The module monitor (modulemon 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. | + | - [[backendprocesses#thresholdmon|The threshold monitor]] (thresholdmon) monitors the RRD data and send alarms if a threshold on a given value is exceeded. |
+ | |||
+ | For more information on the event and alarm system, see [[eventandalertsystem|here]]. | ||
===== The status page ===== | ===== The status page ===== | ||
Line 22: | Line 33: | ||
The status tool gives an overview of all the active alarms. | 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 | * IP devices down | ||
Line 29: | Line 40: | ||
* Services down | * 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 | * Thresholds exceeded |