Cisco Systems 3.6.6 manual Service Impact Analysis For MPLS-Based VPN Services, L3 VPN Report

Chapter 8 Impact Analysis in MPLS Networks

Service Impact Analysis For MPLS-Based VPN Services

Note The reported impact severities vary between fault scenarios. For more information about specific support for each fault scenario, see Supported Fault Scenarios, page 8-3.

Note After the alarm clears, no Clear state for the affected services is generated. However, you can verify that the alarm cleared by checking the Alarm Clear State column in the Affected Parties tab of the Ticket Properties window. For more information about the Affected Parties tab of the Ticket Properties window, see the Cisco Active Network Abstraction 3.6.6 User Guide.

Cisco ANA provides “what-if” scenarios for determining the possible effect of network failures. This enables on-demand calculation of affected VPN sites for physical links in the network, thus enabling an immediate service availability check and analysis for potential impact and identification of critical network links. After executing a what-if scenario, Cisco ANA initiates an end-to-end flow to identify all the potentially affected edges in the affected VPNs. Proactive impact analysis is available from the following:

•Link Properties dialog box when selecting a physical link.

•Topological Link Properties window when selecting a physical link in the links view.

For more information about proactive impact analysis, see the Cisco Active Network Abstraction 3.6.6 User Guide.

Service Impact Analysis For MPLS-Based VPN Services

An MPLS network with PE routers is supported, where the PE routers implement either of the following:

•Layer 3 VPN (VRFs are affected)

•Pseudowire (L2 VPN tunnels are affected) These scenarios are described in the following topics:

•L3 VPN Report, page 8-2

•Pseudowire (L2 VPN) Report, page 8-3

Note Descriptions provided in these scenarios refer only to faults in the MPLS core and not to faults in access networks.

L3 VPN Report

When the Cisco ANA impact analysis identifies the affected parties, the VRFs are displayed as the affected parties on the PE routers that lost connectivity between them in the Ticket Properties window. The number of affected parties that are reported is calculated from the pairs of VRFs and are reported in the Ticket Properties window. The structure of the edge point ID is Device ID \VRF ID\Subinterface (or interface) ID. (The subinterface or interface ID is optional.)

Note VRF sites are not reported as affected pairs.

Cisco Active Network Abstraction 3.6.6 MPLS User Guide

8-2 OL-19192-01