Cisco Systems 3.6.6 Broken LSP Discovered Scenario, MPLS TE Tunnel Down Scenario, Description

Chapter 8 Impact Analysis in MPLS Networks

Supported Fault Scenarios

•Router D notes that the ID of Router B is no longer learned through interface 2.

•No impact analysis is performed.

Broken LSP Discovered Scenario

Table 8-4shows the impacted calculations and reported affected severities for a broken LSP discovered fault scenario.

Table 8-4 Broken LSP Discovered Scenario

Impact and Affected Severity	Description
Impact calculation	Initiates an affected flow to determine all the affected parties using
	the LSP.
Reported affected severity	Only reports on Real Affected. When the Link Down is cleared, all
	the correlated broken LSP alarms are auto-cleared.

MPLS TE Tunnel Down Scenario

Table 8-5shows the impacted calculations and reported affected severities for an MPLS TE tunnel down fault scenario.

Table 8-5 MPLS TE Tunnel Down Scenario

Impact and Affected Severity	Description
Impact calculation	Initiates a flow to look for affected parties.
Reported affected severity	Only reports on real affected.

Pseudowire MPLS Tunnel Down Scenario

Table 8-6shows the impacted calculations and reported affected severities for a pseudowire MPLS tunnel down fault scenario.

Table 8-6 Pseudowire MPLS Tunnel Down

Impact and Affected Severity	Description
Impact calculation	Initiates a flow to look for the affected parties.
Reported affected severity	Only reports on real affected on the MPLS domain.

Cisco Active Network Abstraction 3.6.6 MPLS User Guide

OL-19192-01 8-7