MPLS Manager performs impact analysis on RemotePings and Layer 3 VPN objects, and generates impact events when a remote ping fails. The impact events are imported by the Global Manager and displayed in the Notification Log Console.

RemotePing impact events generated by MPLS Manager lists the impact events that are generated by MPLS Manager for a failed remote ping, including the condition for each event.

Table 1. RemotePing impact events generated by MPLS Manager

Managed object

Event

Condition

RemotePing

Impaired

Caused by one of the following conditions:

  • The source device did not receive ping responses from the destination device or the destination VRF for two or more pings that were sent during the last polling interval, or performance thresholds were exceeded.

  • Flapping event on underlying interfaces, generated by IP Availability Manager.

Down

Caused by one of the following conditions:

  • The source device did not receive ping responses from the destination device or the destination VRF for all pings that were sent during the last polling interval.

  • Down event on underlying interfaces, generated by IP Availability Manager.

  • Down event on the device that is hosting the destination device.

VPN (L3VPN only)

ImpactedByRemotePingFailure

Caused by one of the following conditions:

  • RemotePing Impaired impact event

  • RemotePing Down impact event

By default, the RemotePing Impaired and RemotePing Down events are not imported by the Global Manager and displayed in the Global Console. The MPLS Manager Configuration Guide provides the procedure for enabling the Global Manager to import these event types.