Restrictions For Path Protection; Restrictions For Explicit Path Protection - Cisco CRS Configuration Manual

Ios xr mpls configuration guide
Hide thumbs Also See for CRS:
Table of Contents

Advertisement

Implementing MPLS Traffic Engineering
Related Topics
Configure Tunnels for Path Protection: Example, on page 352

Restrictions for Path Protection

• Only Point-to-Point (P2P) tunnels are supported.
• Point-to-Multipoint (P2MP) TE tunnels are not supported.
• A maximum of one standby LSP is supported.
• There can be only one secondary path for each dynamic path option.
• Explicit path option can be configured for the path protected TE with the secondary path option as
dynamic.
• Do not use link and node protection with path protection on the headend router.
• A maximum number of path protected tunnel TE heads is 2000.
• A maximum number of TE tunnel heads is equal to 4000.
• When path protection is enabled for a tunnel, and the primary label switched path (LSP) is not assigned
a backup tunnel, but the standby LSP is assigned fast-reroute (FRR), the MPLS TE FRR protected value
displayed is different from the Cisco express forwarding (CEF) fast-reroute value.
• Inter-area is not supported for path protection.
Related Topics
Configure Tunnels for Path Protection: Example, on page 352

Restrictions for Explicit Path Protection

Explicit paths are used to create backup autotunnels. Explicit path protection provides a recovery mechanism
to protect explicit paths for MPLS-TE tunnels. These restrictions are listed to protect an explicit path:
• Only one explicit protecting path is supported per path-option.
• Link or node path diversity is not ensured for explicit protecting paths.
• An explicit protecting path cannot protect a dynamic path option.
• All options such as verbatim, lockdown are supported for the protecting path as long as it's explicit.
• An explicit path cannot be protected by its own path option level.
• An explicit path can be protected by a path option level that references the same explicit path name or
identifier, because it is considered another path-option.
• Enhanced path protection is not supported.
Related Topics
Configure Tunnels for Path Protection: Example, on page 352
Cisco IOS XR MPLS Configuration Guide for the Cisco CRS Router, Release 5.1.x
Path Protection
189

Advertisement

Table of Contents
loading

Table of Contents