In this example, a cable between two routers that are running BGP services goes down. The example assumes that the cable connects two physical interfaces that each have one BGP protocol endpoint, which means that the cable supports one BGP session.

In this example, IP Availability Manager:

  • Diagnoses a Cable Down problem.

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

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

  • Exports a Cable DownOrFlapping event-type status to Network Protocol Manager for BGP.

    Network Protocol Manager for BGP:

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

  • Detects a disconnected BGP session for which the Cable DownOrFlapping event-type status is associated with the two physical interfaces that are underlying the disconnected BGP session.

    As indicated in GUID-54856BF8-77ED-44E8-9747-13BDBF142F9D.html#GUID-54856BF8-77ED-44E8-9747-13BDBF142F9D___NPM_BGP_USER_CROSS_COR_EVENT_79289, Network Protocol Manager for BGPperceives the Cable DownOrFlapping event-type status as a problem-type status.

    Network Protocol Manager for BGPthen:

  • Generates a BGPSession Disconnected event.

  • Generates a Cable DownOrFlapping problem.

  • Correlates the BGPSession Disconnected event with the Cable DownOrFlapping problem and marks the event as an impact of the problem.

  • Exports the Cable DownOrFlapping problem and the BGPSession Disconnected event to the Global Manager.

    The Global Manager:

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

  • Receives the Cable DownOrFlapping problem and the BGPSession Disconnected event from Network Protocol Manager for BGP.

  • Combines the Cable DownOrFlapping event from IP Availability Managerwith the Cable DownOrFlapping problem from Network Protocol Manager for BGPto form one notification that has two sources.

  • Associates the Cable DownOrFlapping notification as an impact of the Cable Down notification.

  • Associates the BGPSession Disconnected notification from Network Protocol Manager for BGPas an impact of the Cable Down notification.

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

  • IP Availability Managerevents:

  • Problem: Cable Down

  • Event (impact): Cable DownOrFlapping

  • Network Protocol Manager for BGPevents:

  • Problem: Cable DownOrFlapping

  • Event (impact): BGPSession Disconnected

  • Global Managernotifications:

  • Root cause: Cable Down

  • Impacts: Cable DownOrFlapping and BGPSession Disconnected

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

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