Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > 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: 3,283 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