SAE MPLS VPN plug-in

The SAE MPLS VPN plug-in creates Service Affected Events for MPLS VPNs.

A synthetic event is generated when a Severity 5 (critical) fault event, root cause fault event, or symptom fault event occurs on a provider edge (PE) or customer edge (CE) router or on any of the PE interfaces pointing towards a CE router in any of the discovered MPLS VPNs. The SAE generated is associated with the entity ID of the logical entity in the discovery that represents the collection of MPLS VPN devices on which the fault events occurred.

All PE to CE interfaces are added to a members list and an event on any of the interfaces in this members list causes the system to generate a synthetic MPLS VPN SAE.

You can enable the generation of SAE events based on interfaces dependencies deeper in the core network, by enabling the BGPPeerNextHopInterface discovery agent as part of your network discovery. This agent calls the AddLayer3VPNInterfaceDependency.stch stitcher.

This stitcher determines all PE to core provider router (P) interfaces and P to PE interfaces involved in a VPN. These PE -> P and P ->PE interfaces are added to a dependency list. An event on any of the interfaces in this dependency list causes the system to generate a synthetic MPLS VPN SAE. If an MPLS VPN SAE has already been generated based on an event on any of the interfaces in the members list, then any events in interfaces in the dependency list will be added as related events to that already generated MPLS VPN SAE.

Required fields

This plug-in expects events supplied by the Event Gateway to be with populated with the following fields:

• NmosEntityId
• Severity
• NmosCauseType
• NmosDomainName

Event map subscriptions

The MPLS VPN SAE plug-in subscribes to the following event state: ReSync.