Network Management

BGP alert not matching on the device where a trigger condition is causing the trigger to fail

This article provides information when an alert for BGP is not triggering correctly if it goes down or the neighbor is missing.

First published date

11/13/2018 10:37 PM

Last published date

12/22/2025 11:45 PM

Overview

An alert created for BGP if it goes down or the neighbor is missing is not firing correctly, where the alert was created for nodes where the custom property is using a specific value.

Product section

Network Performance Monitor

Cause

Incorrect Trigger Condition

Resolution



1. Use either - is equal to OR contains - <Specific value> when using a Custom Property to trigger on Nodes on a BGP Alert (Not equal to OR Does not contain may not work).

2. Make sure the Nodes to be triggered have the correct Custom Property value <Specific value>. You can check the values on Settings > All Settings > Manage Custom Properties
 

Use SWIS http://servername/Orion/admin/swis.aspx to confirm that those are expected to be triggered. 

Add an action to send an email, and add a variable so it will tell you the following:

 

Node Name

Neighbor IP

Neighbor status

Neighbor state

Is Missing

 

Save the alert and confirm it triggers as expected.