This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
statustool [2007/10/08 20:39] faltin |
statustool [2011/04/08 14:01] faltin [Back-end processes] |
||
---|---|---|---|
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 20: | Line 9: | ||
- | - [[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). | + | - 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). |
- | - [[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 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#getdevicedata|gDD]]) monitors the operations of modules within a switch stack or within a chassis. | + | - The module monitor (modulemon within [[backendprocesses#ipdevpoll|ipdevpoll]]) monitors the operations of modules within a switch stack or within a chassis. |
- | - [[backendprocesses#thresholdmon|The threshold monitor]] (thresholdmon) monitors the RRD data and send alarms if a threshold on a given value is exceeded. | + | - The threshold monitor ([[backendprocesses#thresholdmon|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]]. | For more information on the event and alarm system, see [[eventandalertsystem|here]]. | ||
Line 30: | Line 19: | ||
- | {{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 status tool gives an overview of all the active alarms. | ||
Line 48: | 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). | 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 ===== | ===== History ===== |