Example of physical interface down

In this example, a physical interface on a router that is running an OSPF service goes down. The example assumes that the physical interface supports one OSPF interface and one OSPF neighbor relationship.

In this example, IP Availability Manager:

• Diagnoses an Interface Down problem.

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

• Exports the Interface Down problem and the NetworkConnection DownOrFlapping event to the Global Manager.

• Exports an Interface Down problem-type status and a NetworkConnection DownOrFlapping event-type status to Network Protocol Manager for OSPF.

  Network Protocol Manager for OSPF:

• Receives the Interface Down problem-type status and the NetworkConnection DownOrFlapping event-type status from IP Availability Manager.

• Detects an alarming OSPF neighbor relationship for which the Interface Down problem-type status is associated with one of the physical interfaces that is underlying the alarming OSPF neighbor relationship.

  Network Protocol Manager for OSPF then:

• Generates an OSPFNeighborRelationship NeighborStateAlarm event.

• Generates an Interface Down problem.

• Correlates the OSPFNeighborRelationship NeighborStateAlarm event with the Interface Down problem and marks the event as an impact of the problem.

• Exports the Interface Down problem and the OSPFNeighborRelationship NeighborStateAlarm event to the Global Manager.

  The Global Manager:

• Receives the Interface Down problem and the NetworkConnection DownOrFlapping event from IP Availability Manager.

• Receives the Interface Down problem and the OSPFNeighborRelationship NeighborStateAlarm event from Network Protocol Manager for OSPF.

• Combines the Interface Down problem from both IP Availability Manager and Network Protocol Manager for OSPF to form one notification that has two sources.

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

• Associates the OSPFNeighborRelationship NeighborStateAlarm notification from Network Protocol Manager for OSPF as an impact of the Interface Down notification.

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

• IP Availability Manager events:

• Problem: Interface Down

• Event (impact): NetworkConnection DownOrFlapping

• Network Protocol Manager for OSPF events:

• Problem: Interface Down

• Event (impact): OSPFNeighborRelationship NeighborStateAlarm

• Global Manager notifications:

• Root cause: Interface Down

• Impacts: NetworkConnection DownOrFlapping and

•      OSPFNeighborRelationship NeighborStateAlarm

  Figure 1. Notification Properties dialog box that shows an Interface Down problem

  

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