Mpls-Tp Links And Physical Interfaces - Cisco ASR 9000 Series Configuration Manual
Aggregation services router mpls
Hide thumbs
Also See for ASR 9000 Series:
- Command reference manual (1138 pages) ,
- Routing configuration manual (702 pages) ,
- Reference manual (696 pages)
Table of Contents
Advertisement
Implementing MPLS Transport Profile
• Continuity Check through BFD
MPLS-TP Links and Physical Interfaces
MPLS-TP link IDs may be assigned to physical interfaces only. Bundled interfaces and virtual interfaces are
not supported for MPLS-TP link IDs.
The MPLS-TP link is used to create a level of indirection between the MPLS-TP tunnel and midpoint LSP
configuration and the physical interface. The MPLS-TP link-id command is used to associate an MPLS-TP
link ID with a physical interface and next-hop node address.
Multiple tunnels and LSPs may then refer to the MPLS-TP link to indicate they are traversing that interface.
You can move the MPLS-TP link from one interface to another without reconfiguring all the MPLS-TP tunnels
and LSPs that refer to the link.
Link IDs must be unique on the router or node. For more information, see the Configuring MPLS-TP Links
and Physical Interfaces section.
Tunnel LSPs
Tunnel LSPs, whether endpoint or midpoint, use the same identifying information. However, it is entered
differently.
• A midpoint consists of a forward LSP and a reverse LSP. A MPLS-TP LSP mid point is identified by
• At the midpoint, determining which end is source and which is destination is arbitrary. That is, if you
• At the midpoint, the LSP number does not assume default values, and hence must be explicitly configured.
• At the endpoint, the local information (source) either comes from the global node ID and global ID, or
• At the endpoint, the remote information (destination) is configured using the destination command after
OL-28381-02
BFD session is automatically created on MPLS-TP LSPs with default parameters. You can override
the default BFD parameters either through global commands or per-tunnel commands. Furthermore,
you can optionally specify different BFD parameters for standby LSPs. For example, when an
LSP is in standby, BFD hello messages can be sent at smaller frequency to reduce line-card CPU
usage. However, when a standby LSP becomes active (for example, due to protection switching),
nominal BFD parameters are used for that LSPs (for example, to run BFD hello messages at higher
frequency). For more information about BFD, see the
Detection on the Cisco ASR 9000 Series Router
Services Router Interface and Hardware Component Configuration
its name, and forward LSP, reverse LSP, or both are configured under a submode.
are configuring a tunnel between your router and a coworker's router, then your router is the source.
However, your coworker considers his or her router to be the source. At the midpoint, either router could
be considered the source. At the midpoint, the forward direction is from source to destination, and the
reverse direction is from destination to source. For more information, see the Configuring MPLS-TP
LSPs at Midpoints section.
from locally configured information using the source command after you enter the interface tunnel-tp
number command, where number is the local or source tunnel-number.
you enter the interface tunnel-tp number command. The destination command includes the destination
Cisco ASR 9000 Series Aggregation Services Router MPLS Configuration Guide, Release 4.3.x
MPLS-TP Links and Physical Interfaces
Configuring Bidirectional Forwarding
in the
Cisco ASR 9000 Series Aggregation
Guide.
315
Advertisement
Table of Contents
