Network Management

How to generate an alert in NPM for interface status

This article describes how to create an alert in NPM that reports the status of your interfaces.

First published date

5/21/2019 4:03 PM

Last published date

12/5/2024 5:53 PM

Overview

This article describes how to generate an alert for interface status in NPM. The following sections provide additional background about this procedure.

Product section

Network Performance Monitor

Resolution

  1. Log in to the Orion Web Console.
  2. Click Settings > Manage Nodes.
  3. Click a node.
  4. In the Node Details page left menu, click Interfaces.
  5. Click an interface link to display the Interface Details widget.

The Interface Details page includes three types of status options:

  • Status (object status)
  • Administrative status
  • Operational status

Below is an example of the Interface Details widget.

About the status options

The widget includes three types of status options highlighted above:

  • Status (object status)
  • Administrative status
  • Operational status

The following table provides descriptions of each highlighted option.

STATUSDESCRIPTION
Status (object status)

The status of the interface as an object in the Orion Web Console.

The object status displays the worst status of any administrative and operational status in the interface. If one of them is DOWN, the object status will be DOWN.

Similarly, if any of operational and administrative status is UNKNOWN, the object status will also be UNKNOWN.

Administrative Status

The status of the interface as managed by the network administrator.

The Administrative Status can be:

  • UP when the interface is turned on.
  • SHUTDOWN when it is turned off.
  • TESTING if it is configured to be in testing state.
  • UNKNOWN when it doesn't fit into any of the first three.
Operational Status

The status of the Tx/Rx operations of the interface.

The Operational Status can be:

  • UP when there is a device ready to send/receive traffic to it.
  • DOWN if the interface was shut down by the network administrator or there is no device ready to send/receive traffic to it.
  • UNKNOWN if the status cannot be determined for some reason.

Out-Of-The-Box Alerts

Solarwinds includes two out-of-the-box alerts that check for the interface status:

  • Interface is down
  • Interface shut down

As part of best practices  on alerting in the Orion Platform, SolarWinds recommends that you duplicate these interface statuses and customize them to fit your needs.

The following section describes how to create an alert for interface status in NPM.

Steps to create the alert for interface status

  1. Log in to the Orion Web Console.
  2. Click Settings > All Settings.
  3. Under Alerts & Reports, click Manage Alerts. 
  4. Locate and select the Interface is down alert.
  5. In the toolbar, click Duplicate & Edit.
  6. In the Properties page, complete the alert properties fields and options, and click Next.
  7. In the Trigger Condition page, complete the fields and options, and click Next.
  8. In the Reset Condition page, configure the options. 
    1. (Optional) Configure the scope of the alert. If you want to limit the alert to specific devices, choose Only following set of objects, and then select the devices.

    2. Under The actual trigger condition option, click the Status drop-down menu and select Browse all Fields.

    3. Locate and select Status, Administrative Status, or Operational status, and then click Select.

    4. Click the last drop-down menu and select the appropriate status for the actual trigger condition.

    5. Click Next.
  9. (Optional) In the Time of Day page, configure the reset condition or time of the day, and then click Next.

  10. In the Trigger Actions page, configure the alert actions, and then click Next.
  11. In the Reset Actions page, configure the alert actions, and then click Next.
  12. In the Summary page, review the configuration summary and verify that the objects will be alerted immediately.

    Note: The Alert Summary can display one or more objects to be triggered based on your scope and actual trigger condition.

  13. Click Submit to commit the changes.