1. Home
  2. Service Check Reference
  3. Check Interface Status Check

Check Interface Status Check

Object Type: Service Check

Service Check Category: Interface Checks

Passive: No

Description: Add this service check to a device template to automatically monitor interface availability on the hosts that the template is applied to. When the device template is applied to a host (on repoll), for each of the host’s active interfaces, this service check automatically adds a passive service check to the host to monitor the availability of that interface. The added passive check will generate an alarm if its interface goes down.

Device Template Only

This service check is designed to be added to devices using device templates only. Do not add this check directly to a device using that device’s administrative settings.

Please note that a passive service check added by this check will not be deleted if its interface goes away (administratively down, index shuffling, etc.). Any passive check that permanently loses its interface will need to be removed manually. This check will, however, automatically add new passive checks for any “new” interfaces it finds when the host is repolled.

If this service check is removed from a device template, OmniCenter will automatically remove the passive checks added by it (except as noted above).

To clarify: Under normal circumstances, this active service check manages the addition and removal of the passive service checks that actually monitor individual availability for each interface on the host. If, for some reason, an interface disappears, or its index is shuffled within OmniCenter, the active check can no longer associate that interface with the passive service check that was monitoring it, and so will not remove the passive check. That is why, under those circumstances, you will have to remove a disassociated passive check manually.

When this service check is added to a device template, it offers 3 configuration options for filtering which interfaces on the host will be monitored:

  • Interface Name/Description – Looks for matches in the “Interface Description” as displayed in the “Current Interfaces” panel of the device administration dashboard. Enter a regular expression or string in the FILTER BY field (if using this option do not leave this field blank). Only interfaces that match the filter will receive passive checks. Enter a 1 in the INVERT field to add passive checks only to interfaces that don’t match the filter.
  • CDP Layer 2 Adjacency – Only interfaces with CDP Layer 2 connections will receive passive checks and be monitored.
  • Interface Tag – Only interfaces with a matching tag assigned to them will receive passive checks and be monitored. Begin typing a tag name in the FILTER BY TAG field, a list of available matching tags will appear, allowing you to select an appropriate one (if using this option do not leave this field blank). If you type a tag name that does not exists, a new tag will be created and added to the list of existing OmniCenter tags. But, you will still need to manually assign that tag to the appropriate interfaces. Only one tag is allowed per service check. To monitor multiple tags, assign this check multiple times using this option with different tags.

Unlike other service checks added to hosts by device templates, this active service check will not show up in the “Active Service Checks” table of the device administration dashboard. Only the passive service checks created for each interface will show up as expected in the “Passive Service Checks” table.

The passive service checks added by this check have no options available to the user. They will display a lock icon in the ACTIONS column of the “Passive Service Checks” table, indicating that those checks are controlled by a device template.

Note

If a device interface is administratively turned off (removing it from the “Active Interfaces” list), but still exists on the device (still in the “All Interfaces” list), an existing passive check for that interface will not be deleted. The passive check will need to be manually deleted. Meaning, if that check is causing alerts, it will continue to cause alerts until it is manually deleted.

Updated on November 22, 2019

Was this article helpful?

Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Contact Support

Leave a Reply