Example of physical interface disabled

In this example, a physical interface on a router that is running an IS-IS service is administratively down (manually disabled). The example assumes that the physical interface supports one IS-IS interface and one IS-IS adjacency.

In this example, IP Availability Manager:

• Diagnoses an Interface Disabled problem.

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

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

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

  Network Protocol Manager for IS-IS:

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

• Detects an alarming IS-IS adjacency for which the Interface Disabled problem-type status is associated with one of the physical interfaces that is underlying the alarming IS-IS adjacency.

  Network Protocol Manager for IS-IS then:

• Generates an ISISAdjacency NeighborStateAlarm event.

• Generates an Interface Disabled problem.

• Correlates the ISISAdjacency NeighborStateAlarm event with the Interface Disabled problem and marks the event as an impact of the problem.

• Exports the Interface Disabled problem and the ISISAdjacency NeighborStateAlarm event to the Global Manager.

  The Global Manager:

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

• Receives the Interface Disabled problem and the ISISAdjacency NeighborStateAlarm event from Network Protocol Manager for IS-IS.

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

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

• Associates the ISISAdjacency NeighborStateAlarm notification from Network Protocol Manager for IS-IS as an impact of the Interface Disabled notification.

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

• IP Availability Manager events:

• Problem: Interface Disabled

• Event (impact): NetworkConnection DownOrFlapping

• Network Protocol Manager for IS-IS events:

• Problem: Interface Disabled

• Event (impact): ISISAdjacency NeighborStateAlarm

• Global Manager notifications:

• Root cause: Interface Disabled

• Impacts: NetworkConnection DownOrFlapping and

•      ISISAdjacency NeighborStateAlarm

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

  

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