Example of router down

In this example, a router that is running an EIGRP service goes down. The example assumes that the device has multiple physical interfaces that have multiple EIGRP protocol endpoints, which means that the device supports multiple EIGRP sessions.

In this example, IP Availability Manager:

• Diagnoses a Router Down problem.

• Generates multiple Router Unresponsive events as impacts of the Router Down problem.

• Generates a NetworkConnection DownOrFlapping event as an impact of the Router Down problem.

• Exports the Router Down problem, the multiple Router Unresponsive events, and the NetworkConnection DownOrFlapping event to the Global Manager.

• Exports multiple NetworkConnection DownOrFlapping event-type statuses and a NetworkConnection DownOrFlapping event-type status to Network Protocol Manager for EIGRP.

  Network Protocol Manager for EIGRP:

• Receives the multiple Router Unresponsive event-type statuses from IP Availability Manager.

• Receives the NetworkConnection DownOrFlapping event-type status from IP Availability Manager.

• Detects disconnected EIGRP sessions for which the Router Unresponsive event-type statuses are associated with the physical interfaces that are underlying the disconnected EIGRP sessions.

  As indicated in GUID-E7FAB2EA-5BD6-4302-80A3-88A7168F9C4C.html#GUID-E7FAB2EA-5BD6-4302-80A3-88A7168F9C4C___NPM_EIGRP_USER_CROSS_COR_EVENT_79289, Network Protocol Manager for EIGRP perceives the Router Unresponsive event-type status as a problem-type status.

  Network Protocol Manager for EIGRP then:

• Generates multiple EIGRPSession Disconnected events.

• Generates multiple Router Unresponsive problems.

• Correlates each EIGRPSession Disconnected event with the associated Router Unresponsive problem and marks the event as an impact of the problem.

• Exports the Router Unresponsive problems and the EIGRPSession Disconnected events to the Global Manager.

  The Global Manager:

• Receives the Router Down problem and the Router Unresponsive and NetworkConnection DownOrFlapping events from IP Availability Manager.

• Receives the Router Unresponsive problems and the EIGRPSession Disconnected events from Network Protocol Manager for EIGRP.

• Combines each Router Unresponsive event from IP Availability Manager with the identical Router Unresponsive problem from Network Protocol Manager for EIGRP to form one notification that has two sources.

• Associates the multiple Router Unresponsive notifications as impacts of the Router Down notification.

• Associates the multiple EIGRPSession Disconnected notifications from Network Protocol Manager for EIGRP as impacts of the Router Down notification.

• Associates the NetworkConnection DownOrFlapping notification from IP Availability Manager as an impact of the Router Down notification.

  What follows is a summary of the notifications that are created for the Router Down problem, followed by a display in Notification Properties dialog box that shows a Router Down problem that shows how the Global Manager associates the network and EIGRP events as impacts of the Router Down problem:

• IP Availability Manager events:

• Problem: Router Down

• Event (impact): Router Unresponsive, Router Unresponsive,

•      NetworkConnection DownOrFlapping

• Network Protocol Manager for EIGRP events:

• Problem: Router Unresponsive, Router Unresponsive,

• Event (impact): EIGRPSession Disconnected, EIGRPSession Disconnected,

• Global Manager notifications:

• Root cause: Router Down

• Impacts: Router Unresponsive, Router Unresponsive,

•      NetworkConnection DownOrFlapping, EIGRPSession Disconnected,

•      EIGRPSession Disconnected,

  Figure 1. Notification Properties dialog box that shows a Router Down problem

  

  Chapter 2, Viewing EIGRP Analysis Results and Topology, provides instructions on viewing detailed notification information.