
53
TE Class
CT
Priority
2 2
7
3 3
7
4 0
0
5 1
0
6 2
0
7 3
0
Creating an MPLS TE tunnel over a static CR-LSP
Creating MPLS TE tunnels over static CR-LSPs does not involve configuration of tunnel constraints
or the issue of IGP TE extension or CSPF. Create a static CR-LSP and a TE tunnel using static
signaling and then associate them.
Despite its ease of configuration, the application of MPLS TE tunnels over static CR-LSPs is
restricted because they cannot dynamically adapt to network changes.
Static CR-LSPs are special static LSPs. They share the same constraints and use the same label
space.
Configuration prerequisites
Before you perform the configuration, complete the following tasks:
•
Configure static routing or an IGP protocol to ensure all LSRs are reachable.
•
Configure basic MPLS.
•
Configure basic MPLS TE.
Configuration guidelines
•
The
tunnel-name
argument specifies the name of the MPLS TE tunnel interface that uses the
static CR-LSP.
•
The
tunnel-name
argument in the
static-cr-lsp ingress
command must be the same as the
tunnel interface name, including the letter case. For example, assume that you have created a
tunnel interface by using the command
interface tunnel
2. The tunnel interface name is
Tunnel2
. The
tunnel-name
in the
static-cr-lsp ingress
command must be in the form of
Tunnel2—not tunnel2 or TUNNEL2. Otherwise, the tunnel cannot be established on the ingress
node. This restriction however does not apply to transit or egress nodes.
•
Do not configure the next hop address as a local public address when configuring the static
CR-LSP on the ingress or a transit node.
•
The incoming interface and outgoing interface of a static CR-LSP must be P2P type. To use
P2P ATM subinterfaces as the incoming and outgoing interfaces of a static CR-LSP, you must
configure IPoA mapping (with the
map ip
command) on the ATM subinterfaces.
Configuration procedure
To create an MPLS TE tunnel over a static CR-LSP: