Submit a ticketCall us

Bridging the ITSM Divide
Integrated help desk and remote support software for faster resolution

Join us on Wednesday, November 29, 2017 at 11 a.m. CT, as we discuss the benefits of effectively integrating your help desk software with remote support solutions to help increase the efficiency of IT administration, improve communication, and decrease mean time to resolution (MTTR) for IT issues of all sizes. This directly impacts end-user satisfaction and your business’ bottom line. Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Routing Neighbor Down alert does not trigger for EIGRP

Routing Neighbor Down alert does not trigger for EIGRP

Created by Leif Amland, last modified by MindTouch on Jun 23, 2016

Views: 531 Votes: 0 Revisions: 4

Overview

The Routing Neighbor Down alert does not trigger for EIGRP.

The Web Console does not log an error and the user does not receive an email when the Cisco EIGRP protocol fails.

Environment

NPM v11.5.2

Cause 

The canned alert is not used and the alert being used is only for specified BGP and not the EIGRP.

Resolution

  1. Create a copy of the Routing Neighbor Down alert by highlighting the canned alert and making a duplicate.
  2. In Trigger Conditions, specify that 'Protocol Name' is equal to 'Cisco EIGRP'.
  3. Specify the same information for the Reset Conditions.
  4. Complete the rest of the alert according to your preferences and then verify that the alert works correctly by simulating the email trigger.

 

Last modified

Tags

Classifications

Public