H3C Technologies H3C S10500 Series Switches - Manual (Page 110)

99
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 procedure
Follow these steps to create an MPLS TE tunnel over a CR-LSP:
To do… Use the command… Remarks
Enter system view system-view ––
Enter the interface view of an MPLS
TE tunnel
interface tunnel tunnel-number ––
Configure the tunnel to use static
CR-LSP
mpls te signal-protocol static Required
Submit the current tunnel
configuration
mpls te commit Required
Exit to system view quit ––
At the ingress
static-cr-lsp ingress tunnel-name
destination dest-addr nexthop
next-hop-addr |
outgoing-interface interface-type
interface-number
On the transit
node
static-cr-lsp transit tunnel-name
incoming-interface interface-type
interface-number in-label
in-label-value nexthop
next-hop-addr out-label
out-label-value
Create a static
CR-LSP on your
device
depending on
its location in
the network
At the egress
static-cr-lsp egress tunnel-name
incoming-interface interface-type
interface-number in-label
in-label-value
Required
Use any of the commands
according to the location of the
device in the network.
The tunnel-name argument
specifies the name of the MPLS TE
tunnel interface that uses the static
CR-LSP. For example, assume that
you have created a tunnel interface
by using the command interface
tunnel 2. The tunnel interface name
is Tunnel2.
NOTE:
•
The tunnel-name argument in the static-cr-lsp ingress command must be the same as the tunnel
interface name, including the letter case. Assume you create a tunnel interface with the interface tunnel
2 command. 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 and 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.