Configuring Lsp Hierarchy - Cisco CRS Configuration Manual
Ios xr mpls configuration guide
Hide thumbs
Also See for CRS:
- User manual (304 pages) ,
- Configuration manual (292 pages) ,
- Command reference manual (155 pages)
Table of Contents
Advertisement
Implementing MPLS Traffic Engineering
Command or Action
Step 5
match identifier tunnel number
Example:
RP/0/RP0/CPU0:router(config-if)#
match identifier gmpls1_t1
Step 6
destination ip-address
Example:
RP/0/RP0/CPU0:router(config-if)#
destination 10.1.1.1
Step 7
Use the commit or end command.
Configuring LSP Hierarchy
These tasks describe the high-level steps that are required to configure LSP hierarchy.
LSP hierarchy allows standard MPLS-TE tunnels to be established over GMPLS-TE tunnels.
Consider the following information when configuring LSP hierarchy:
• LSP hierarchy supports numbered optical TE tunnels with IPv4 addresses only.
• LSP hierarchy supports numbered optical TE tunnels using numbered or unnumbered TE links.
Before you can successfully configure LSP hierarchy, you must first establish a numbered optical tunnel
Note
between the headend and tailend routers.
To configure LSP hierarchy, you must perform a series of tasks that have been previously described in this
GMPLS configuration section. The tasks, which must be completed in the order presented, are as follows:
1 Establish an optical TE tunnel.
Purpose
Configures the match identifier. You must enter the hostname for the head
router then underscore _t, and the tunnel number for the head router. If
tunnel-te1 is configured on the head router with a hostname of gmpls1, CLI is
match identifier gmpls1_t1.
The match identifier must correspond to the tunnel-gte number
Note
configured on the headend router. Together with the address specified
using the destination command, this identifier uniquely identifies
acceptable incoming tunnel requests.
Assigns a destination address on the new tunnel.
• Destination address is the remote node's MPLS-TE router ID.
• Destination address is the merge point between backup and protected
tunnels.
commit—Saves the configuration changes, and remains within the configuration
session.
end—Prompts user to take one of these actions:
• Yes— Saves configuration changes and exits the configuration session.
• No—Exits the configuration session without committing the configuration
changes.
• Cancel—Remains in the configuration mode, without committing the
configuration changes.
Cisco IOS XR MPLS Configuration Guide for the Cisco CRS Router, Release 5.1.x
Configuring GMPLS
263
Advertisement
Table of Contents
