Network Management

Routing Neighbor is Down alert does not trigger for EIGRP

This article discusses an issue with missed alerts configured to trigger on routing neighbors using EIGRP.

First published date

10/31/2018 12:42 PM

Last published date

6/21/2021 8:57 PM

Overview

When configuring an alert for routing neighbors using EIGRP, it may miss triggers when the neighbor goes down. This article discusses an issue with missed alerts configured to trigger on routing neighbors using EIGRP.

Product section

Network Performance Monitor

Cause

The Routing Neighbor Protocol Name is not specified as a scope of the alert trigger condition.

Resolution

 
  1. On the web console, go to Settings > All Settings > Manage Alerts and search for 'Neighbor is down' canned alert.
  2. Create a duplicate and edit the alert.
  3. In Trigger Conditions, specify that 'Protocol Name' is equal to 'Cisco EIGRP'. NOTE: You can also use 'Protocol Name' contains 'EIGRP'
  4. Leave the Reset Condition as "Reset this alert when the trigger condition is no longer true"
  5. Complete the rest of the alert according to your preferences and then verify that the alert works correctly by simulating the email trigger.