Trouble Creating Modified Neighbor Down Alert using Node Custom Properties

peter.lewis_NetWolves

Good afternoon everyone!

I am trying to modified the out-of-the-box neighbor down alert so that it only triggers for certain nodes based on a node custom property (CustomerName.)

When I add it to the trigger logic, it has no effect. The alert triggers regardless of the CustomerName value. When I add it to the scope, the scope is an empty list and therefore no nodes trigger. I've also tried using the Router Caption but the result is the same.

Has anyone has success using a node custom property or caption with Routing Neighbor alerts?

Your help will be greatly appreciated.

peter.lewis_NetWolves

Here is my current config summary for the alert...

7. Summary of Alert Configuration

Please review the alert configuration before saving...

Name of alert:

Edit

Alert me when a neighbor goes down

Description of alert:

GEN2 - This alert is triggered if any routing neighbor on node changes its status to down.

Type of Property to monitor

Routing Neighbors

Enabled(On/Off):

ON

Evaluation Frequency of alert:

Every minute

Severity of alert:

Warning

Alert Custom Properties: (2)

Comments:
Customer_Node_Name:

Alert owner (user who created this alert):

myuser 

Alert Limitation Category

In Development

Trigger Condition:

Edit

Alert on all objects where:
Router - Caption - starts with - THECUSTO-
The actual trigger condition:
At least one child condition must be satisfied (OR)
Routing Neighbors - Protocol Orion Status - is equal to - Down
Routing Neighbors - Is Deleted - is equal to - 1

Reset Condition:

Edit

When the trigger condition is no longer true

Time of Day schedule:

Edit

Alert is always enabled

Trigger Action:

Edit

Escalation Level 1

1. NetPerfMon Event Log : The neighbor ${NeighborIP} on Node ${Node.Caption} went down.

2. Urgent-Network-Neighbor Down

Reset Action:

Edit

1. NetPerfMon Event Log : The neighbor ${NeighborIP} on Node ${Node.Caption} went up.

2. Urgent-Network-Neighbor Up

Alert Integration

This alert would be immediately triggered on 0 object(s) in alert scope  If this behavior is not expected, try to  adjust the trigger condition

BACK SUBMIT CANCEL