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:26] faltin |
statustool [2007/10/07 12:31] faltin |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== The status tool ====== | ====== The status tool ====== | ||
- | {{tools:status.png|}} | + | {{tools:status.png|}} The status tool gives an overview on operations; i.e. that all the network components and services are up and running. |
+ | |||
- | NAV has a number of background processes that monitors the operational status of the network: | ||
===== Back-end processes ===== | ===== Back-end processes ===== | ||
+ | |||
+ | 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: | ||
+ | |||
* [[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#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. |