Configuring Mpls Te Tunnel With Dynamic Signaling Protocol - 3Com MSR 50 Series Configuration Manual

3com msr 30-16: software guide
Hide thumbs Also See for MSR 50 Series:
Table of Contents

Advertisement

Configuring MPLS TE
Tunnel with Dynamic
Signaling Protocol
To do...
Create a static
CR-LSP on your
device
depending on
its location in
the network
n
The tunnel-name argument specifies the name of the MPLS TE tunnel carried
over the static CR-LSP.
The tunnel-name argument in the static-cr-lsp ingress command is case
sensitive. Suppose you create a tunnel interface with the interface tunnel 2
command. To specify it for the tunnel-name in the static-cr-lsp ingress
command, you must input its name in the form of Tunnel2. Otherwise, your
tunnel establishment attempt will fail. This restriction however does not apply
to transit and egress nodes.
The next hop address cannot be a local public address when configuring the
static CR-LSP on the ingress or a transit node.
Dynamic signaling protocol can adapt the path of a TE tunnel to network changes
and implement redundancy, FRR, and other advanced features.
The following describes how to create an MPLS TE tunnel with a dynamic signaling
protocol:
Configure MPLS TE properties for links and advertise them through IGP TE
extension to form a TEDB.
Configure tunnel constraints.
Use the CSPF algorithm to calculate a preferred path based on the TEDB and
tunnel constraints.

Configuring MPLS TE Tunnel with Dynamic Signaling Protocol

Use the command...
At the ingress
static-cr-lsp ingress
tunnel-name destination
dest-addr { nexthop
next-hop-addr |
outgoing-interface
interface-type
interface-number }
out-label out-label-value
[ bandwidth [ bc0 | bc1 ]
bandwidth-value ]
On the transit
static-cr-lsp transit
node
tunnel-name
incoming-interface
interface-type
interface-number in-label
in-label-value { nexthop
next-hop-addr |
outgoing-interface
interface-type
interface-number }
out-label out-label-value
[ bandwidth [ bc0 | bc1 ]
bandwidth-value ]
At the egress
static-cr-lsp egress
tunnel-name
incoming-interface
interface-type
interface-number in-label
in-label-value [ lsrid
ingress-lsr-id tunnel-id
tunnel-id ]
1361
Remarks
Required
Use any of the commands
depending on the location
of your device in the
network.

Hide quick links:

Advertisement

Table of Contents

Troubleshooting

loading
Need help?

Need help?

Do you have a question about the MSR 50 Series and is the answer not in the manual?

Table of Contents