16.01.2013 Views

Ipswitch WhatsUp Gold User Guide - Ipswitch Documentation Server

Ipswitch WhatsUp Gold User Guide - Ipswitch Documentation Server

Ipswitch WhatsUp Gold User Guide - Ipswitch Documentation Server

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Ipswitch</strong> <strong>WhatsUp</strong> <strong>Gold</strong> <strong>User</strong> <strong>Guide</strong><br />

Note: Up and Down device dependencies take precedence over critical monitor polling; if<br />

<strong>WhatsUp</strong> <strong>Gold</strong> detects device dependencies, the configured dependencies are respected.<br />

When critical monitoring is enabled, and you specify a critical polling order, you now receive<br />

only one alert when a device loses its network connectivity.<br />

Note: When a monitor is placed in the unknown state, assigned actions are not fired.<br />

Likewise, when a monitor comes out of the unknown state into an up state, assigned actions<br />

are not fired.<br />

Only monitors that you specify as critical follow a specific polling order; non-critical monitors<br />

are not polled in any specific order. Additionally, if multiple non-critical monitors fail, all<br />

associated actions fire.<br />

Critical active monitors can be viewed and configured from the Device Properties - Active<br />

Monitors (on page 123) dialog.<br />

Note: Independent poll frequency for all monitors is ignored when a monitor is specified as<br />

critical.<br />

xxvii) Configuring a critical polling path<br />

To configure a critical polling path for device active monitors:<br />

1 Right-click the device for which you want to configure a critical polling path in the<br />

Details or Map View and select Properties. The Device Properties dialog appears.<br />

2 Select Active Monitors. The Device Properties - Active Monitors dialog appears.<br />

229

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!