User Tools

Site Tools


statustool

This is an old revision of the document!


The status tool

NAV has a number of background processes that monitors the operational status of the network:

  • 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.
  • 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 monitors the operations of modules within a switch stack or within a chassis.
  • The threshold monitors the RRD data and send alarms if a threshold on a given value is exceeded.

The status page

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:

  • IP devices down
  • IP devices in shadow (shadow means that the device is behind a device that is down and the status is thus unknown)
  • Modules down
  • Services down

In addition using the preferences tool (reached from the NAV bar) you may add:

  • Thresholds exceeded
  • IP devices on maintenance
  • Services on maintenance

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).

Status page preferences

History

From each status page section a link to history is provided. You may also see individual histories using the link provided on each line in the listing. The history view goes per default 7 days back, but can be increased to a maximum of 30 days.

Service Matrix

For the services section you may in addition go to a matrix view that shows red and green lights for all monitored services.

Configuration files

For the webfront - none. But the data the status page shows is supplied from backend processes such as pping, servicemon, etc. They have configuration files that can alter their behavior, for details see backendprocesses.

statustool.1190914966.txt.gz · Last modified: 2007/09/27 19:42 by faltin