Event Masking and Device Dependencies

Iotellect Network Manager has a special implementation of Event Masking strategy that solves the following tasks:

• Disables polling of network hosts that are not available from the Iotellect Server due to failures of intermediate device(s)
• Suppresses alert initiation by devices that are currently unavailable due to intermediate device failures

The event masking technology is based on device-to-parent relationships that are defined by Device Connectivity model included into Iotellect Network Manager distribution. This model:

• Adds Parent Devices table and Connectivity Expression variable to every Network Host device.
• Sets Dependency Expression property of every newly created network host device so that its connectivity check is performed in the beginning of every synchronization cycle. Device synchronization (polling) is disabled if connectivity check fails.
• Configures connectivity check functions so that the device is deemed unavailable due to parent device failures if ping to device itself and its parents fails.

The basic configuration of event/alert masking and suppression is very simple:

• Right-click on a Network Host device
• Select Edit Additional Properties
• Switch to the Device Connectivity tab
• Open Parent Devices table
• Fill table with network device(s) that is (or could be -- in case of dynamic routing) the next hop on the network route from the device being configured to the Iotellect Network Manager server

This model enables event masking and suppression of alerts initiated by devices that are unavailable due to failures of some intermediate network devices.

Was this page helpful?

Tell us more

Send

Thank you!