Beruflich Dokumente
Kultur Dokumente
V600R003C00
02
Date
2011-09-10
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 02 (2011-09-10)
l This document takes interface numbers and link types of the NE40E-X8 as an example. In working
situations, the actual interface numbers and link types may be different from those used in this
document.
l On NE80E/40E series excluding NE40E-X1 and NE40E-X2, line processing boards are called Line
Processing Units (LPUs) and switching fabric boards are called Switching Fabric Units (SFUs). On
the NE40E-X1 and NE40E-X2, there are no LPUs and SFUs, and NPUs implement the same functions
of LPUs and SFUs to exchange and forward packets.
Related Versions
The following table lists the product versions related to this document.
Product Name
Version
HUAWEI NetEngine80E/40E
Router
V600R003C00
Intended Audience
The intended audience of this document is:
l
Commissioning Engineer
Issue 02 (2011-09-10)
ii
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
DANGER
WARNING
CAUTION
TIP
NOTE
Command Conventions
The command conventions that may be found in this document are defined as follows.
Issue 02 (2011-09-10)
Convention
Description
Boldface
Italic
[]
{ x | y | ... }
[ x | y | ... ]
{ x | y | ... }*
[ x | y | ... ]*
&<1-n>
iii
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in previous issues.
MPLS TE Configuration
3.17.3 (Optional) Configuring the Path Overlapping Function for Hot-standby
CR-LSPs is added in this chapter to describe how to configure the path overlapping
function. The path overlapping function can be configured for hot-standby CR-LSPs,
allowing a hot-standby CR-LSP to use links of a primary CR-LSP. After the hot-standby
CR-LSP is established, it can protect traffic on the primary CR-LSP.
The section Configuring a Timer for LDP FRR Protection is deleted because the timer
for LDP FRR protection is not supported.
Issue 02 (2011-09-10)
iv
Contents
Contents
About This Document.....................................................................................................................ii
1 Static LSPs Configuration............................................................................................................1
1.1 Introduction to Static LSPs.................................................................................................................................2
1.1.1 Overview of Static LSPs............................................................................................................................2
1.1.2 Static LSPs Features Supported by the NE80E/40E.................................................................................2
1.2 Configuring Static LSPs.....................................................................................................................................2
1.2.1 Establishing the Configuration Task.........................................................................................................2
1.2.2 Configuring the LSR ID............................................................................................................................3
1.2.3 Enabling MPLS.........................................................................................................................................4
1.2.4 Configuring the Ingress for a Static LSP...................................................................................................4
1.2.5 Configuring the Transit for a Static LSP...................................................................................................5
1.2.6 Configuring the Egress for a Static LSP....................................................................................................5
1.2.7 Checking the Configuration.......................................................................................................................6
1.3 Configuring Static BFD for Static LSP..............................................................................................................6
1.3.1 Establishing the Configuration Task.........................................................................................................7
1.3.2 Enable Global BFD Capability..................................................................................................................7
1.3.3 Configuring BFD with Specific Parameters on Ingress............................................................................8
1.3.4 Configuring BFD with Specific Parameters on Egress...........................................................................10
1.3.5 Checking the Configuration.....................................................................................................................12
1.4 Maintaining Static LSPs...................................................................................................................................12
1.4.1 Clearing MPLS Statistics.........................................................................................................................12
1.4.2 Checking the LSP Connectivity and Reachability..................................................................................13
1.4.3 Enabling the Trap Function of LSP.........................................................................................................13
1.5 Configuration Examples...................................................................................................................................13
1.5.1 Example for Configuring Static LSPs.....................................................................................................14
1.5.2 Example for Configuring Static BFD for Static LSP..............................................................................21
Contents
vi
Contents
vii
Contents
3 MPLS TE Configuration...........................................................................................................180
3.1 Introduction to MPLS TE...............................................................................................................................183
3.1.1 MPLS TE Overview..............................................................................................................................183
3.1.2 MPLS TE Features Supported by the NE80E/40E................................................................................183
3.2 Configuring Static CR-LSP............................................................................................................................186
3.2.1 Establishing the Configuration Task.....................................................................................................186
3.2.2 Enabling MPLS TE...............................................................................................................................187
3.2.3 (Optional) Configuring Link Bandwidth...............................................................................................188
3.2.4 Configuring the MPLS TE Tunnel Interface.........................................................................................189
3.2.5 Configuring the Ingress of the Static CR-LSP......................................................................................190
3.2.6 Configuring the Transit of the Static CR-LSP.......................................................................................191
3.2.7 Configuring the Egress of the Static CR-LSP.......................................................................................191
3.2.8 Checking the Configuration...................................................................................................................192
3.3 Configuring a Static Bidirectional Co-routed LSP.........................................................................................193
3.3.1 Establishing the Configuration Task.....................................................................................................193
3.3.2 Enabling MPLS TE...............................................................................................................................194
3.3.3 (Optional) Configuring Link Bandwidth...............................................................................................195
3.3.4 Configuring a Tunnel Interface on the Ingress......................................................................................195
3.3.5 Configure the Ingress of a Static Bidirectional Co-routed LSP............................................................197
3.3.6 Configure a Transit Node of a Static Bidirectional Co-routed LSP......................................................197
3.3.7 Configure the Egress of a Static Bidirectional Co-routed LSP.............................................................198
3.3.8 Configuring the Tunnel Interface on the Egress....................................................................................199
3.3.9 Checking the Configuration...................................................................................................................199
3.4 Configuring an RSVP-TE Tunnel..................................................................................................................200
3.4.1 Establishing the Configuration Task.....................................................................................................200
3.4.2 Enabling MPLS TE and RSVP-TE.......................................................................................................201
3.4.3 (Optional) Configuring Link Bandwidth...............................................................................................202
3.4.4 Configuring OSPF TE...........................................................................................................................203
3.4.5 Configuring IS-IS TE............................................................................................................................204
3.4.6 (Optional) Configuring an MPLS TE Explicit Path..............................................................................205
3.4.7 Configuring the MPLS TE Tunnel Interface.........................................................................................206
Issue 02 (2011-09-10)
viii
Contents
ix
Contents
Contents
xi
Contents
xii
Contents
xiii
Contents
A Glossary......................................................................................................................................617
B Acronyms and Abbreviations.................................................................................................623
Issue 02 (2011-09-10)
xiv
Issue 02 (2011-09-10)
Static LSPs
Static LSPs need to be configured manually by the administrator. Each LSR on the static LSP
cannot sense the status of the entire LSP, because the static LSP is a local concept. A static LSP
cannot vary with the change of a route dynamically. The administrator then needs to adjust the
static LSP.
Applicable Environment
A static LSP works normally only after all the LSRs along the LSP are configured.
Issue 02 (2011-09-10)
The setup of static LSPs does not require the label distribution protocol or exchange any control
packet. Thus, the static LSPs consume little resources and are applicable to small-scale networks
with simple and stable topology. The static LSPs cannot vary with the network topology
dynamically. The administrator, therefore, needs to adjust the static LSPs according to the
network topology.
Static LSPs and static CR-LSPs share the same label space (16 - 1023).
Static LSPs are used over the MPLS L2VPN.
For information about the MPLS L2VPN configuration, refer to the HUAWEI NetEngine80E/
40E Router Configuration Guide - VPN.
Pre-configuration Tasks
Before configuring static LSPs, complete the following tasks:
l
Configuring the static unicast route or an IGP to connect LSRs on the network layer
Data Preparation
To configure static LSPs, you need the following data.
No.
Data
Incoming interface, next hop address, or outgoing interface on the transit node
Context
When configuring an LSR ID, note the following:
l
The LSR ID must be configured before other MPLS commands are run.
The LSR ID does not have a default value, and must be configured manually.
It is recommended to use the address of the loopback interface of the LSR as the LSR ID.
To modify the configured LSR ID, you must run the undo mpls command in the system
view to delete all the MPLS configurations.
Procedure
Step 1 Run:
system-view
Context
Do as follows on each LSR in an MPLS domain:
Procedure
Step 1 Run:
system-view
Context
Do as follows on the LSR to be configured as the ingress:
Procedure
Step 1 Run:
system-view
It is recommended to set up a static LSP by specifying a next hop. In addition, ensure that the local routing
table contains the route entries, including the destination IP address and the IP address of the next hops,
which exactly match the specified destination IP address and next hop address of the LSP to be set up.
----End
Context
Do as follows on the LSR to be configured as a transit node:
Procedure
Step 1 Run:
system-view
It is recommended to set up a static LSP by specifying a next hop. In addition, ensure that the local routing
table contains the route entries, including the destination IP address and the IP address of the next hops,
which exactly match the specified destination IP address and next hop address of the LSP to be set up.
----End
Context
Do as follows on the LSR to be configured as the egress:
Procedure
Step 1 Run:
system-view
Prerequisite
The configurations of the static LSP function are complete.
Procedure
l
Run the display mpls static-lsp [ lsp-name ] [ { include | exclude } ip-address masklength ] [ verbose ] command to check the static LSP.
----End
Example
If the configurations succeed, run the preceding commands, and you can view as follows:
l
When the display mpls static-lsp command, information about the static LSP
configuration is displayed, including the name of the static LSP, FEC, values of the
incoming label and the outgoing label, and the incoming and outgoing interfaces. In
addition, you can view that the status of the LSP is Up.
<HUAWEI> display mpls static-lsp
TOTAL
: 1
STATIC LSP(S)
UP
: 1
STATIC LSP(S)
DOWN
: 0
STATIC LSP(S)
Name
FEC
I/O Label
lsp1
3.3.3.9/32
NULL/100
I/O If
-/GE1/0/0
Stat
Up
Applicable Environment
BFD is used to detect the connectivity of the static LSP that is established manually.
NOTE
When the static BFD works on the static LSP, the BFD session can be created for non-host routes.
BFD for LSP can function properly though the forward path is an LSP and the backward path is an IP link.
The forward path and the backward path must be established over the same link; otherwise, if a fault occurs,
BFD cannot identify the faulty path. Before deploying BFD, ensure that the forward and backward paths
are over the same link so that BFD can correctly identify the faulty path.
Pre-configuration Tasks
Before configuring static BFD for static LSP, complete the following tasks:
l
For the static CR-LSP bound to an MPLS TE tunnel, the BFD is available after it is bound to the MPLS
TE tunnel.
Data Preparations
Before configuring static BFD for a static LSP, you need the following data.
No.
Data
Context
Do as follows on each LSR at both ends of the link to be detected:
Procedure
Step 1 Run:
system-view
This node is enabled with the global BFD function. The BFD global view is displayed.
----End
Context
Do as follows on the ingress of the static LSP:
Procedure
Step 1 Run:
system-view
2.
Run the mpls command to globally enable MPLS and the enter the MPLS view.
3.
Run the mpls bfd min-tx-interval interval command to adjust the minimum interval for
the local device to send BFD packets.
Issue 02 (2011-09-10)
The minimum interval for the local device to send BFD packets is set.
By default, the value is 1000 milliseconds.
If the backward link is an IP link, this parameter is not applicable.
Actual interval for the local device to send BFD packets = MAX { Locally configured
interval for sending BFD packets, Remotely configured interval for receiving BFD
packets}; Actual interval for the local to receive BFD packets = MAX {Remotely
configured interval for sending BFD packets, Locally configured interval for receiving
BFD packets}; Local detection period = Actual interval for the local device to Receive BFD
packets x Remotely configured BFD detection multiple.
For example, assume that the values of parameters are as follows:
l On the local device, the interval for sending BFD packets is set to 200 ms, the interval
for receiving BFD packets is set to 300 ms, and the detection multiple is set to 4.
l On the peer device, the interval for sending BFD packets is 100 ms, the interval for
receiving BFD packets is 600 ms, and the detection multiple is 5.
Then,
l On the local device, the actual interval for sending BFD packets is 600 ms calculated
by using the formula max {200 ms, 600 ms}, the interval for receiving BFD packets is
300 ms calculated by using the formula max {100 ms, 300 ms}, and the detection period
is 1500 ms calculated by 300 ms multiplied by 5.
l On the peer device, the actual interval for sending local BFD packets is 300 ms obtained
by using the formula max {100 ms, 300 ms}, the interval for receiving BFD packets is
600 ms obtained by using the formula max {200 ms, 600 ms}, and the detection period
is 2400 ms obtained by 600 ms multiplied by 4.
4.
Run the mpls bfd min-rx-interval interval command to adjust the minimum interval for
receiving BFD packets.
The minimum interval for receiving BFD packets is adjusted on the local device.
By default, the value is 1000 milliseconds.
If the backward link is an IP link, this parameter is not applicable.
5.
Run the mpls bfd detect-multiplier multiplier command to adjust the local BFD detection
multiple.
The default value is 3.
6.
7.
Run the bfd cfg-name command to enter the BFD session view.
Step 5 Run:
process-pst
When configuring the BFD session of the static LSP, note the following:
l When the static LSP status goes Up, a BFD session is renewed.
l When the static LSP status goes Down, the BFD session becomes Down too.
l When the static LSP is deleted, the session and configuration entries of BFD are deleted.
----End
Context
The IP link, LSP, or TE tunnel can be used as the reverse tunnel to inform the ingress of a fault.
To avoid affecting BFD detection, an IP link is preferentially selected to inform the ingress of
an LSP fault. The process-pst command is prohibited when a reverse tunnel is configured. If
the configured reverse tunnel requires BFD detection, you can configure a pair of BFD sessions
for it.
Do as follows on the egress of the LSP:
Procedure
Step 1 Run:
system-view
10
1.
2.
Run the mpls command to globally enable MPLS and the enter the MPLS view.
3.
Run the mpls bfd min-tx-interval interval command to adjust the minimum interval for
the local device to send BFD packets.
The minimum interval for the local device to send BFD packets is set.
By default, the value is 1000 milliseconds.
If the backward link is an IP link, this parameter is not applicable.
Actual interval for the local device to send BFD packets = MAX { Locally configured
interval for sending BFD packets, Remotely configured interval for receiving BFD
packets}; Actual interval for the local to receive BFD packets = MAX {Remotely
configured interval for sending BFD packets, Locally configured interval for receiving
BFD packets}; Local detection period = Actual interval for the local device to Receive BFD
packets x Remotely configured BFD detection multiple.
For example, assume that the values of parameters are as follows:
l On the local device, the interval for sending BFD packets is set to 200 ms, the interval
for receiving BFD packets is set to 300 ms, and the detection multiple is set to 4.
l On the peer device, the interval for sending BFD packets is 100 ms, the interval for
receiving BFD packets is 600 ms, and the detection multiple is 5.
Then,
l On the local device, the actual interval for sending BFD packets is 600 ms calculated
by using the formula max {200 ms, 600 ms}, the interval for receiving BFD packets is
300 ms calculated by using the formula max {100 ms, 300 ms}, and the detection period
is 1500 ms calculated by 300 ms multiplied by 5.
l On the peer device, the actual interval for sending local BFD packets is 300 ms obtained
by using the formula max {100 ms, 300 ms}, the interval for receiving BFD packets is
600 ms obtained by using the formula max {200 ms, 600 ms}, and the detection period
is 2400 ms obtained by 600 ms multiplied by 4.
4.
Run the mpls bfd min-rx-interval interval command to adjust the minimum interval for
receiving BFD packets.
The minimum interval for receiving BFD packets is adjusted on the local device.
By default, the value is 1000 milliseconds.
If the backward link is an IP link, this parameter is not applicable.
5.
Run the mpls bfd detect-multiplier multiplier command to adjust the local BFD detection
multiple.
The default value is 3.
6.
7.
Run the bfd cfg-name command to enter the BFD session view.
Step 5 Run:
commit
11
Prerequisite
The configurations of the static BFD for static LSP function are complete.
Procedure
l
Run the display bfd configuration { all | static } [ for-lsp ] command to check the BFD
configuration.
Run the display bfd session { all | static } [ for-lsp ] command to check information about
the BFD session.
Run the display bfd statistics session { all | static } [ for-ip | for-lsp ] command to check
information about BFD statistics.
Run the display mpls static-lsp [ lsp-name ] [ { include | exclude } ip-address masklength ] [ verbose ] command to check the status of the static LSP.
----End
Context
CAUTION
MPLS statistics cannot be restored after being cleared. Therefore, confirm the action before you
run the following commands.
Procedure
l
Run the reset mpls statistics interface { interface-type interface-number | all } command
in the user view to clear the statistics of the MPLS interface.
Run the reset mpls statistics lsp { lsp-name | all } command in the user view to clear LSP
statistics.
----End
Issue 02 (2011-09-10)
12
Context
You can run the following commands in any view to perform MPLS ping and MPLS tracert.
Procedure
l
Run:
ping lsp [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m
interval | -r reply-mode | -s packet-size | -t time-out | -v ] * ip destinationaddress mask-length [ ip-address ] [ nexthop nexthop-address | draft6 ]
Run:
tracert lsp [ -a source-ip | -exp exp-value | -h ttl-value | -r reply-mode | t time-out ] * ip destination-address mask-length [ ip-address ] [ nexthop
nexthop-address | draft6 ]
Context
Run the following commands in the system view to notify the Network Management System
(NMS) of the LSP status change.
By default, the trap function is disabled during the setup of the LDP LSP.
Procedure
l
----End
13
Follow-up Procedure
NOTE
This document takes interface numbers and link types of the NE40E-X8 as an example. In working
situations, the actual interface numbers and link types may be different from those used in this document.
Networking Requirements
As shown in Figure 1-1, the LSRs support MPLS and OSPF as an IGP running on the MPLS
backbone network.
Bidirectional static LSPs are set up between LSRA and LSRD. The LSP from LSRA to LSRD
is LSRA -> LSRB -> LSRD; the LSP from LSRD to LSRA is LSRD -> LSRC -> LSRA.
Figure 1-1 Networking diagram of configuring static LSPs
Loopback1
2.2.2.9/32
/0
1/0 /30
S
2
PO 1.1.
.
0
0
Loopback1
/0/ 30 1
1
/
S
1.1.1.9/32 O
1
P 1.1.
.
10
P
LSRA 1 OS
0.3 2/0
.1. /0
1/3
0 POS
10
.3. 1/0/
1.2 0
/30
P
10 OS2
.2. /0
1.1 /0
/30 P
Loopback1
LSRB
10 OS1
.2. /0/ 4.4.4.9/32
1.2 0
/30
LSRC
/0
2/0 /30
S
PO 4.1.1
.
10
/0 LSRD
2/0 /30
S
2
PO 4.1.
.
10
Loopback1
3.3.3.9/32
Configuration Roadmap
The configuration roadmap is as follows:
1.
Issue 02 (2011-09-10)
Configure the IP address of each interface, set the loopback address as the LSR ID, and use
OSPF to advertise the network segments to which the interfaces are connected and the LSR
ID host route.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
14
2.
3.
4.
Specify the destination address, outgoing interface or next hop, outgoing label for the LSP
on the ingress LSR.
5.
Specify the incoming interface, outgoing label corresponding to the incoming label of the
last, outgoing interface or next hop of the LSP on the transit.
6.
Specify the incoming interface and the incoming label that is the same as the outgoing label
from the last LSR of the LSP on the egress.
Data Preparation
To complete the configuration, you need the following data:
l
IP addresses of the interfaces on each LSR as shown in Figure 1-1, OSPF process ID, and
area ID
Procedure
Step 1 Configure the IP address of each interface.
According to Figure 1-1, configure the IP address and the mask of the interfaces, including the
loopback interface. The configuration details are not mentioned here.
Step 2 Use OSPF to advertise the network segments to which the interfaces are connected and the LSR
ID host route.
# Configure LSRA.
[LSRA] ospf 1
[LSRA-ospf-1] area 0
[LSRA-ospf-1-area-0.0.0.0]
[LSRA-ospf-1-area-0.0.0.0]
[LSRA-ospf-1-area-0.0.0.0]
[LSRA-ospf-1-area-0.0.0.0]
[LSRA-ospf-1] quit
# Configure LSRB.
[LSRB] ospf 1
[LSRB-ospf-1] area 0
[LSRB-ospf-1-area-0.0.0.0]
[LSRB-ospf-1-area-0.0.0.0]
[LSRB-ospf-1-area-0.0.0.0]
[LSRB-ospf-1-area-0.0.0.0]
[LSRB-ospf-1] quit
# Configure LSRC.
[LSRC] ospf 1
[LSRC-ospf-1] area 0
[LSRC-ospf-1-area-0.0.0.0]
[LSRC-ospf-1-area-0.0.0.0]
[LSRC-ospf-1-area-0.0.0.0]
[LSRC-ospf-1-area-0.0.0.0]
[LSRC-ospf-1] quit
# Configure LSRD.
[LSRD] ospf 1
Issue 02 (2011-09-10)
15
[LSRD-ospf-1] area 0
[LSRD-ospf-1-area-0.0.0.0]
[LSRD-ospf-1-area-0.0.0.0]
[LSRD-ospf-1-area-0.0.0.0]
[LSRD-ospf-1-area-0.0.0.0]
[LSRD-ospf-1] quit
After the configuration, run the display ip routing-table command on the LSRs, and you can
view that the LSRs already learn routes from each other.
Take the display on LSRA as an example.
[LSRA] display ip routing-table
Route Flags: R - relay, D - download to fib
-----------------------------------------------------------------------------Routing Tables: Public
Destinations : 14
Routes : 15
Destination/Mask
Proto Pre Cost
Flags NextHop
Interface
1.1.1.9/32 Direct 0
0
D 127.0.0.1
InLoopBack0
2.2.2.9/32 OSPF
10
2
D 10.1.1.2
Pos1/0/0
3.3.3.9/32 OSPF
10
2
D 10.3.1.2
Pos2/0/0
4.4.4.9/32 OSPF
10
3
D 10.1.1.2
Pos1/0/0
OSPF
10
3
D 10.3.1.2
Pos2/0/0
10.1.1.0/30 Direct 0
0
D 10.1.1.1
Pos1/0/0
10.1.1.1/32 Direct 0
0
D 127.0.0.1
InLoopBack0
10.1.1.2/32 Direct 0
0
D 10.1.1.2
Pos1/0/0
10.2.1.0/30 OSPF
10
2
D 10.1.1.2
Pos1/0/0
10.3.1.0/30 Direct 0
0
D 10.3.1.1
Pos2/0/0
10.3.1.1/32 Direct 0
0
D 127.0.0.1
InLoopBack0
10.3.1.2/32 Direct 0
0
D 10.3.1.2
Pos2/0/0
10.4.1.0/30 OSPF
10
2
D 10.3.1.2
Pos2/0/0
127.0.0.0/8
Direct 0
0
D 127.0.0.1
InLoopBack0
127.0.0.1/32 Direct 0
0
D 127.0.0.1
InLoopBack0
The next hop or outgoing interface of the static LSP on 4.4.4.9/32 from LSRA to LSRD is
determined by the routing table. It is shown in boldface. In this example, the next hop IP address
is 10.1.1.2/30.
Take the display on LSRD as an example.
[LSRD] display ip routing-table
Route Flags: R - relay, D - download to fib
-----------------------------------------------------------------------------Routing Tables: Public
Destinations : 14
Routes : 15
Destination/Mask
Proto Pre Cost
Flags NextHop
Interface
1.1.1.9/32 OSPF
10
3
D 10.2.1.1
Pos1/0/0
OSPF
10
3
D 10.4.1.1
Pos2/0/0
2.2.2.9/32 OSPF
10
2
D 10.2.1.1
Pos1/0/0
3.3.3.9/32 OSPF
10
2
D 10.4.1.1
Pos2/0/0
4.4.4.9/32 Direct 0
0
D 127.0.0.1
InLoopBack0
10.1.1.0/30 OSPF
10
2
D 10.2.1.1
Pos1/0/0
10.2.1.0/30 Direct 0
0
D 10.2.1.2
Pos1/0/0
10.2.1.1/32 Direct 0
0
D 10.2.1.1
Pos1/0/0
10.2.1.2/32 Direct 0
0
D 127.0.0.1
InLoopBack0
10.3.1.0/30 OSPF
10
2
D 10.4.1.1
Pos2/0/0
10.4.1.0/30 Direct 0
0
D 10.4.1.2
Pos2/0/0
10.4.1.1/32 Direct 0
0
D 10.4.1.1
Pos2/0/0
10.4.1.2/32 Direct 0
0
D 127.0.0.1
InLoopBack0
127.0.0.0/8
Direct 0
0
D 127.0.0.1
InLoopBack0
127.0.0.1/32 Direct 0
0
D 127.0.0.1
InLoopBack0
The next hop or outgoing interface of the static LSP on 1.1.1.9/32 from LSRD to LSRA is
determined by the routing table. It is shown in boldface. In this example, the next hop IP address
is 10.4.1.1/30.
Step 3 Configure the basic MPLS capability on each LSR.
Issue 02 (2011-09-10)
16
# Configure LSRA.
[LSRA] mpls lsr-id 1.1.1.9
[LSRA] mpls
[LSRA-mpls] quit
# Configure LSRB.
[LSRB] mpls lsr-id 2.2.2.9
[LSRB] mpls
[LSRB-mpls] quit
# Configure LSRC.
[LSRC] mpls lsr-id 3.3.3.9
[LSRC] mpls
[LSRC-mpls] quit
# Configure LSRD.
[LSRD] mpls lsr-id 4.4.4.9
[LSRD] mpls
[LSRD-mpls] quit
# Configure LSRB.
[LSRB] interface pos 1/0/0
[LSRB-Pos1/0/0] mpls
[LSRB-Pos1/0/0] quit
[LSRB] interface pos 2/0/0
[LSRB-Pos2/0/0] mpls
[LSRB-Pos2/0/0] quit
# Configure LSRC.
[LSRC] interface pos 1/0/0
[LSRC-Pos1/0/0] mpls
[LSRC-Pos1/0/0] quit
[LSRC] interface pos 2/0/0
[LSRC-Pos2/0/0] mpls
[LSRC-Pos2/0/0] quit
# Configure LSRD.
[LSRD] interface pos 1/0/0
[LSRD-Pos1/0/0] mpls
[LSRD-Pos1/0/0] quit
[LSRD] interface pos 2/0/0
[LSRD-Pos2/0/0] mpls
[LSRD-Pos2/0/0] quit
17
After the configuration, run the display mpls static-lsp verbose or display mpls lsp command
on the LSRs to view the status of the LSP.
Take the display on LSRA as an example.
[LSRA] display mpls static-lsp
TOTAL
: 1
STATIC LSP(S)
UP
: 1
STATIC LSP(S)
DOWN
: 0
STATIC LSP(S)
Name
FEC
I/O Label I/O If
RAtoRD
4.4.4.9/32
NULL/20
-/Pos1/0/0
Stat
Up
As the LSP is unidirectional, you need to configure a static LSP from LSRD to LSRA.
Step 6 Establish the static LSP from LSRD to LSRA.
In the same method, configure the static LSP from LSRD to LSRA.
# Configure the ingress LSRD.
[LSRD] static-lsp ingress RDtoRA destination 1.1.1.9 32 nexthop 10.4.1.1 out-label
30
Issue 02 (2011-09-10)
I/O If
Pos1/0/0/-/Pos2/0/0
Stat
Up
Up
18
No
:
LSP-Name
:
LSR-Type
:
FEC
:
In-Label
:
Out-Label
:
In-Interface
:
Out-Interface :
NextHop
:
Static-Lsp Type:
Lsp Status
:
2
RDtoRA
Ingress
1.1.1.9/32
NULL
30
Pos2/0/0
10.4.1.1
Normal
Up
----End
Configuration Files
l
Issue 02 (2011-09-10)
19
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.1.0 0.0.0.3
network 10.2.1.0 0.0.0.3
#
static-lsp transit RAtoRD incoming-interface Pos1/0/0 in-label 20 nexthop
10.2.1.2 out-label 40
#
return
Issue 02 (2011-09-10)
20
area 0.0.0.0
network 4.4.4.9 0.0.0.0
network 10.2.1.0 0.0.0.3
network 10.4.1.0 0.0.0.3
#
static-lsp egress RAtoRD incoming-interface Pos1/0/0 in-label 40
static-lsp ingress RDtoRA destination 1.1.1.9 32 nexthop 10.4.1.1 out-label 30
#
return
Networking Requirements
As shown in Figure 1-2:
l
Without MPLS OAM, test the connectivity of the static LSP. When the static LSP fails, PE1
can receive the advertisement within 50 ms.
Figure 1-2 Networking diagram of configuring static BFD for static LSP
Loopback1
2.2.2.2/32
0
Loopback1
/0/ 24
1
S
1.1.1.1/32 O
1/
P 1.1.
.
10
P
PE1 10 OS
.1. 1/0/
2.1 1
/24
/0
1/0 /24
S
2
PO 1.1.
.
10
P1
P
10 OS1
.1. /0
5.2 /2
/24
Static LSP
P
10 OS1
.1. /0/
2.2 0
/24
P
Loopback1
10 OS1
.1. /0/ 4.4.4.4/32
5.1 0
/24
P2
/2
1/0 /24
S
PO 1.4.2
.
10
Loopback1
3.3.3.3/32
/1 PE2
1/0 /24
S
1
PO 1.4.
.
10
Configuration Roadmap
The configuration roadmap is as follows:
1.
Issue 02 (2011-09-10)
The entire MPLS domain applies OSPF protocol and IP route is accessible to each LSR.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
21
2.
3.
Configure the BFD session on PE2, which advertises a failure on static LSP to PE1 (in this
direction, the link is an IP link).
Data Preparations
To complete the configuration, you need the following data:
l
BFD session parameters, such as configuration name, minimum detection interval between
sending and receiving packets
Procedure
Step 1 Configure the IP address and the OSPF protocol for each interface.
Configure the IP address and mask of each interface as shown in Figure 1-2, including loopback
interfaces.
Configure OSPF on all LSRs to advertise the host route of the loopback interface. The detailed
configuration is not mentioned here.
After the configuration, each LSR can ping through the other LSR ID. Run the display ip
routing-table command, and you can view the route table on each LSR.
<PE1> display ip routing-table
Route Flags: R - relay, D - download to fib
-----------------------------------------------------------------------------Routing Tables: Public
Destinations : 14
Routes : 15
Destination/Mask
Proto Pre Cost
Flags NextHop
Interface
1.1.1.1/32 Direct 0
0
127.0.0.1
InLoopBack0
2.2.2.2/32 OSPF
10
2
10.1.1.2
Pos1/0/0
3.3.3.3/32 OSPF
10
2
10.1.2.2
Pos1/0/1
4.4.4.4/32 OSPF
10
3
10.1.1.2
Pos1/0/0
OSPF
10
3
10.1.2.2
Pos1/0/1
10.1.1.0/24 Direct 0
0
10.1.1.1
Pos1/0/0
10.1.1.1/32 Direct 0
0
127.0.0.1
InLoopBack0
10.1.1.2/32 Direct 0
0
10.1.1.2
Pos1/0/0
10.1.2.0/24 Direct 0
0
10.1.2.1
Pos1/0/1
10.1.2.1/32 Direct 0
0
127.0.0.1
InLoopBack0
10.1.2.2/32 Direct 0
0
10.1.2.2
Pos1/0/1
10.1.4.0/24 OSPF
10
2
10.1.2.2
Pos1/0/1
10.1.5.0/24 OSPF
10
2
10.1.1.2
Pos1/0/0
127.0.0.0/8
Direct 0
0
127.0.0.1
InLoopBack0
127.0.0.1/32 Direct 0
0
127.0.0.1
InLoopBack0
Issue 02 (2011-09-10)
22
After the configuration, run the ping lsp ip 4.4.4.4 32 command on PE1, and you can view that
the LSP is reachable.
Step 4 Configure the BFD session to detect static LSP.
# Configure a BFD session on PE1 (ingress). The local identifier is 1 and remote identifier is 2.
The minimal intervals for sending and receiving packets are 10 seconds respectively. The
interface status table can be modified.
[PE1] bfd 1to4 bind static-lsp 1to4
[PE1-bfd-lsp-session-1to4] discriminator local 1
[PE1-bfd-lsp-session-1to4] discriminator remote 2
[PE1-bfd-lsp-session-1to4] min-tx-interval 10
[PE1-bfd-lsp-session-1to4] min-rx-interval 10
[PE1-bfd-lsp-session-1to4] process-pst
[PE1-bfd-lsp-session-1to4] commit
[PE1-bfd-lsp-session-1to4] quit
# Configure the BFD session on PE2 (egress) that advertises the static LSP failure through the
IP route.
[PE2] bfd 4to1 bind peer-ip 1.1.1.1
[PE2-bfd-session-4to1] discriminator local 2
[PE2-bfd-session-4to1] discriminator remote 1
[PE2-bfd-session-4to1] min-tx-interval 10
[PE2-bfd-session-4to1] min-rx-interval 10
[PE2-bfd-session-4to1] commit
[PE2-bfd-session-4to1] quit
# Run the display bfd session all verbose command, and you can view that the BFD on PE1 is
Up.
[PE1] display bfd session all verbose
-------------------------------------------------------------------------------Session MIndex : 256
(One Hop)State : Up
Name : 1to4
-------------------------------------------------------------------------------Local Discriminator
: 1
Remote Discriminator
: 2
Session Detect Mode
: Asynchronous Mode Without Echo Function
BFD Bind Type
: STATIC_LSP
Bind Session Type
: Static
Bind Peer Ip Address
: 4.4.4.4
NextHop Ip Address
: 10.1.1.2
Static LSP name
: 1to4
LSP Token
: 0x1002000
Bind Interface
: -FSM Board Id
: 1
TOS-EXP
: 7
Min Tx Interval (ms)
: 10
Min Rx Interval (ms)
: 10
Issue 02 (2011-09-10)
23
# Run the display bfd session all verbose command on PE2, and you can view the output of
configuration.
[PE2] display bfd session all verbose
-------------------------------------------------------------------------------Session MIndex : 256
(Multi Hop) State : Up
Name : 4to1
-------------------------------------------------------------------------------Local Discriminator
: 2
Remote Discriminator
: 1
Session Detect Mode
: Asynchronous Mode Without Echo Function
BFD Bind Type
: Peer Ip Address
Bind Session Type
: Static
Bind Peer Ip Address
: 1.1.1.1
NextHop Ip Address
: 10.1.4.2
Bind Interface
: -FSM Board Id
: 1
TOS-EXP
: 7
Min Tx Interval (ms)
: 10
Min Rx Interval (ms)
: 10
Actual Tx Interval (ms): 10
Actual Rx Interval (ms): 10
Local Detect Multi
: 3
Detect Interval (ms)
: 30
Echo Passive
: Disable
Acl Number
: Proc Interface Status : Disable
Process PST
: Disable
WTR Interval (ms)
: Local Demand Mode
: Disable
Active Multi
: 3
Local Demand Mode
: Disable
Last Local Diagnostic : Control Detection Time Expired
Bind Application
: No Application Bind
Session TX TmrID
: -Session Detect TmrID
: -Session Init TmrID
: -Session WTR TmrID
: -Session Echo Tx TmrID : PDT Index
: FSM-0|RCV-0|IF-0|TOKEN-0
Session Description
: -------------------------------------------------------------------------------Total UP/DOWN Session Number : 1/0
# Run the display bfd session all verbose command, and you can view the BFD status.
[PE2] display bfd session all verbose
-------------------------------------------------------------------------------Session MIndex : 256
(Multi Hop) State : Down
Name : 4to1
-------------------------------------------------------------------------------Local Discriminator
: 2
Remote Discriminator
: 1
Session Detect Mode
: Asynchronous Mode Without Echo Function
BFD Bind Type
: Peer Ip Address
Bind Session Type
: Static
Bind Peer Ip Address
: 1.1.1.1
Bind Interface
: -
Issue 02 (2011-09-10)
24
FSM Board Id
: 1
TOS-EXP
: 7
Min Tx Interval (ms)
: 10
Min Rx Interval (ms)
: 10
Actual Tx Interval (ms): 10
Actual Rx Interval (ms): 10
Local Detect Multi
: 3
Detect Interval (ms)
: 30
Echo Passive
: Disable
Acl Number
: Proc Interface Status : Disable
Process PST
: Disable
WTR Interval (ms)
: Local Demand Mode
: Disable
Active Multi
: 3
Local Demand Mode
: Disable
Last Local Diagnostic : Control Detection Time Expired
Bind Application
: No Application Bind
Session TX TmrID
: -Session Detect TmrID
: -Session Init TmrID
: -Session WTR TmrID
: -Session Echo Tx TmrID : PDT Index
: FSM-0|RCV-0|IF-0|TOKEN-0
Session Description
: -------------------------------------------------------------------------------Total UP/DOWN Session Number : 0/1
[PE1] display bfd session all verbose
-------------------------------------------------------------------------------Session MIndex : 256
(One Hop) State : Down
Name : 1to4
-------------------------------------------------------------------------------Local Discriminator
: 1
Remote Discriminator
: 2
Session Detect Mode
: Asynchronous Mode Without Echo Function
BFD Bind Type
: STATIC_LSP
Bind Session Type
: Static
Bind Peer Ip Address
: 4.4.4.4
NextHop Ip Address
: 10.1.1.2
Bind Interface
: -Static LSP name
: 1to4
LSP Token
: 0x1002000
FSM Board Id
: 1
TOS-EXP
: 7
Min Tx Interval (ms)
: 10
Min Rx Interval (ms)
: 10
Actual Tx Interval (ms): 10
Actual Rx Interval (ms): 30
Local Detect Multi
: 3
Detect Interval (ms)
: 3000
Echo Passive
: Disable
Acl Number
: Destination Port
: 3784
TTL
: 1
Proc Interface Status : Disable
Process PST
: Enable
WTR Interval (ms)
: Proc interface status : Disable
Active Multi
: 3
Local Demand Mode
: Disable
Last Local Diagnostic : Control Detection Time Expired
Bind Application
: LSPM OAM_MANAGER
Session TX TmrID
: -Session Detect TmrID
: -Session Init TmrID
: -Session WTR TmrID
: -Session Echo Tx TmrID : PDT Index
: FSM-B030000 | RCV-2 | IF-B030000 | TOKEN-0
Session Description
: -------------------------------------------------------------------------------Total UP/DOWN Session Number : 0/1
----End
Configuration Files
l
Issue 02 (2011-09-10)
25
mpls
#
interface Pos1/0/1
link-protocol ppp
undo shutdown
ip address 10.1.2.1 255.255.255.0
mpls
#
interface NULL0
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
ospf 100
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 10.1.1.0 0.0.0.255
network 10.1.2.0 0.0.0.255
#
static-lsp ingress 1to4 destination 4.4.4.4 32 nexthop 10.1.1.2 out-label 20
#
bfd 1to4 bind static-lsp 1to4
discriminator local 1
discriminator remote 2
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
Return
Issue 02 (2011-09-10)
26
Configuration file of P1
#
sysname P1
#
mpls lsr-id 2.2.2.2
mpls
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.2 255.255.255.0
mpls
#
interface Pos1/0/2
link-protocol ppp
undo shutdown
ip address 10.1.5.2 255.255.255.0
mpls
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
ospf 100
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 10.1.1.0 0.0.0.255
network 10.1.5.0 0.0.0.255
#
static-lsp transit 1to4 incoming-interface Pos1/0/0 in-label 20 nexthop
10.1.5.1 out-label 30
#
return
Configuration file of P2
#
sysname P2
#
mpls lsr-id 3.3.3.3
mpls
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.2.2 255.255.255.0
mpls
#
interface Pos1/0/2
link-protocol ppp
undo shutdown
ip address 10.1.4.2 255.255.255.0
mpls
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
ospf 100
area 0.0.0.0
network 3.3.3.3 0.0.0.0
network 10.1.2.0 0.0.0.255
network 10.1.4.0 0.0.0.255
#
return
Issue 02 (2011-09-10)
27
28
By configuring a policy for triggering the setup of backup LSPs, you can control the setup of
backup LSPs.
2.10 Configuring Synchronization Between LDP and IGP
By configuring LDP and IGP synchronization, you can delay the route switchback by
suppressing the setup of IGP neighbor relationship till an LDP session is established.
2.11 Configuring Synchronization Between LDP and Static Routes
By configuring synchronization between LDP and static routes, you can switch traffic from the
faulty primary link to the backup link by suppressing the activation of static routes and delay
traffic switchback to synchronize LDP and static routes.
2.12 Configuring LDP GTSM
By configuring LDP GTSM, you can detect TTLs to prevent attacks.
2.13 Configuring LDP GR
By configuring LDP GR, you can realize the uninterrupted forwarding during the master/slave
switchover or the protocol restart, which can limit the protocol flapping on the control plane.
2.14 Maintaining MPLS LDP
The operations of MPLS LDP maintenance include deleting MPLS statistics, detecting
connectivity and reachability of an LSP, and configuring the trap function on an LDP LSP.
2.15 Configuration Examples
The following sections provide several examples for configuring MPLS LDP. Familiarize
yourself with the configuration procedures against the networking diagram. Each configuration
example consists of the networking requirements, configuration precautions, configuration
roadmap, configuration procedures, and configuration files.
Issue 02 (2011-09-10)
29
LDP Sessions
Label Distribution Protocol (LDP) sessions are used between LSRs to swap labels.
l
Remote LDP session: can be set between adjacent LSRs or non-adjacent LSRs.
LDP LSP
The LDP protocol is used to create dynamic LSPs. If you need not to strictly control the setup
process of LSPs or to deploy traffic engineering (TE) on an MPLS network, you are
recommended to use LDP to set up LSPs.
Issue 02 (2011-09-10)
30
LDP Multi-Instance
LDP multi-instance is applicable to the networking of MPLS L3VPN carrier's carrier. For details
of carrier's carrier networking, refer to the HUAWEI NetEngine80E/40E Router Feature
Description - VPN.
Quick detection
At present, in the NE80E/40E, BFD can detect LSPs of the following types:
l
Static LSP
LDP LSP
TE tunnel
BFD for LSP is dedicated to public bear layer of VPN/PW and provides reliability to applications
based on MPLS network, such as VPN FRR, TE FRR, and VLL FRR, to protect services.
When BFD works in unidirectional links, such as LSP and TE, only the IP route along the
backward link needs to be reachable. Therefore, the backward link can be IP tunnels, LSPs, or
TE tunnels.
LDP FRR
The traditional IP Fast Reroute (FRR) cannot effectively protect the traffic on an MPLS network.
The NE80E/40E provides the LDP FRR function as a solution to port protection.
When the network works normally, packets are forwarded through the primary LSP. When the
outgoing interface of the primary LSP is Down, packets are forwarded through the bypass LSP.
This ensures continuous traffic for a short time before network convergence completes. The
NE80E/40E supports the LDP FRR in primary/bypass LSP mode rather than in load balancing
mode.
LDP FRR supports BFD to implement quick fault detection. For details of BFD, refer to the
HUAWEI NetEngine80E/40E Router Configuration Guide - Reliability.
31
forwarded through the standby link. After the active link is established, the standby link can be
deleted.
LDP GTSM
The Generalized TTL Security Mechanism (GTSM) protects the service above the IP layer by
checking whether the TTL value in the IP packet header is within a pre-set range. In applications,
GTSM is designed to protect the TCP/IP-based control plane (like routing protocols) from CPUusage attacks, such as CPU overload attacks.
LDP GR
Graceful Restart (GR) is a key technology to HA implementation. At present, GR is widely
applied to switchover and system upgrade.
The NE80E/40E supports LDP GR. When the system performs the switchover, the interface
board is not reset and the LDP LSP information on the data plane is stored. In this manner, the
LSP forwarding continues and the impact on forwarding the MPLS packets is minimized.
Applicable Environment
LDP sessions are classified into local LDP sessions and remote LDP sessions. These sessions
are applicable to the following scenarios:
l
Issue 02 (2011-09-10)
32
LDP timers
Hello hold timer
Hello send timer
It is used together with the Hello hold timer to maintain LDP Hello adjacencies.
Keepalive hold timer
Keepalive send timer
It is used together with the Keepalive hold timer to maintain LDP sessions.
Exponential backoff timer
It is used to control the interval for the active role to retry setting up an LDP session.
MD5 authentication
It is used to improve the security of LDP sessions. A session is set up between two LSRs
successfully only when passwords on both ends are consistent.
Keychain authentication
Keychain, an enhanced encryption algorithm, calculates a message digest for an LDP
message to prevent the message from being modified. The system automatically adopts a
new password after the previous password expires, preventing the password from being
decrypted.
Pre-configuration Tasks
Before configuring MPLS LDP sessions, complete the following tasks:
l
Data Preparation
To configure MPLS LDP sessions, you need the following data.
Issue 02 (2011-09-10)
33
No.
Data
Name and IP address of the remote peer on which a remote LDP session is to be
set up
Context
When configuring an LSR ID, note the following:
l
The LSR ID must be configured before other MPLS commands are run.
The LSR ID does not have a default value, and must be configured manually.
It is recommended to use the address of the loopback interface of the LSR as the LSR ID.
To modify the configured LSR ID, you must run the undo mpls command in the system
view to delete all the MPLS configurations.
Procedure
Step 1 Run:
system-view
34
Context
Do as follows on each LSR in an MPLS domain:
Procedure
Step 1 Run:
system-view
Context
NOTE
Before enabling the global LDP functions, you must enable global MPLS functions.
Procedure
Step 1 Run:
system-view
Issue 02 (2011-09-10)
35
MPLS LDP is enabled on the local node and the MPLS LDP view is displayed.
By default, the global LDP functions are prohibited.
Step 3 (Optional) Run:
lsr-id lsr-id
Context
If a certain LDP feature is enabled after an LDP session has been created, the LDP session and
the LSP associated with the session will be interrupted and re-negotiated when LDP dynamic
capability announcement function is not enabled.
The LDP dynamic capability announcement function dynamically enables or disables an LDP
feature that supports dynamic negotiation without interrupting an LDP session, ensuring the
stability of the LSP associated with the LDP session.
NOTE
The LDP dynamic capability announcement function does not affect the existing functions and therefore
it is recommended to be enabled immediately after LDP is enabled.
Before the LDP dynamic capability announcement function is enabled, MPLS and MPLS LDP must have
been enabled globally.
Procedure
Step 1 Run:
system-view
Issue 02 (2011-09-10)
36
The LDP dynamic capability announcement function takes effect only on the LDP features that support
LDP dynamic capability announcement function.
----End
Context
The MPLS LDP session is classified into the local LDP session and the remote LDP session.
You can choose one of the following configurations according to your demands:
l
Procedure
l
Run:
system-view
Run:
interface interface-type interface-number
Before enabling the LDP function, you must enable the MPLS function on the interface.
3.
Run:
mpls ldp
Disabling LDP on the interface may interrupt all LDP sessions on the interface. In addition, all
the LSPs based on these sessions are deleted accordingly.
Issue 02 (2011-09-10)
37
Run:
system-view
Run:
mpls ldp remote-peer remote-peer-name
The remote peer is created and the remote peer view is displayed.
3.
Run:
remote-ip ip-address
Modifying or deleting the configured address of a remote peer leads to the deletion of the related
remote LDP session.
----End
Context
LDP sessions are created on the basis of TCP connections. Before two LSRs set up an LDP
session, they need to confirm the LDP transport address of each other, and then set up a TCP
connection.
Generally, you are not recommended to modify LDP transport addresses.
To modify LDP transport addresses, do as follows on the two LSRs at both ends of an LDP
session:
Procedure
Step 1 Run:
system-view
The view of the interface on which the LDP session is set up is displayed.
Step 3 Run:
mpls ldp transport-address { interface-type interface-number | interface }
Issue 02 (2011-09-10)
38
In the case of LDP multi-instance, each instance can have a specific TCP connection.
----End
Context
CAUTION
You are recommended to set the value of a timer equal to or greater than the default value. When
many LDP sessions are set up between LSRs or the CPU usage is high, the status of LDP sessions
may frequently switch between Up and Down if the value of the timer is smaller than the default
value. Increasing the values of timers can improve the stability of LDP sessions.
LDP timers are classified into Hello hold timer, Hello send timer, Keepalive hold timer,
Keepalive send timer, and the Exponential backoff timer.
l
Issue 02 (2011-09-10)
39
Procedure
l
Run:
system-view
Run:
interface interface-type interface-number
The view of the interface on which the LDP session is set up is displayed.
3.
Run:
mpls ldp timer hello-hold interval
Run:
system-view
Run:
interface interface-type interface-number
The view of the interface on which the LDP session is to be set up is displayed.
3.
Run:
mpls ldp timer hello-send interval
Issue 02 (2011-09-10)
40
1.
Run:
system-view
Run:
mpls ldp remote-peer remote-peer-name
Run:
mpls ldp timer hello-hold interval
Run:
system-view
Run:
mpls ldp remote-peer remote-peer-name
Run:
mpls ldp timer hello-send interval
Run:
system-view
Run:
interface interface-type interface-number
The view of the interface on which the LDP session is set up is displayed.
3.
Run:
mpls ldp timer keepalive-hold interval
41
By default, the value of the Keepalive timer of the local LDP session is 45 seconds.
The value of the Keepalive timer configured on the LSR may be not equal to the value
of the timer that takes effect. The value of the timer that takes effect is equal to the
smaller value of two values of the timers configured on both ends.
NOTE
Modifying the value of KeepAlive hold timer leads to reestablish of LDP sessions and all LSPs
based on the LDP sessions.
Run:
system-view
Run:
interface interface-type interface-number
The view of the interface on which the LDP session is to be set up is displayed.
3.
Run:
mpls ldp timer keepalive-send interval
Run:
system-view
Run:
mpls ldp remote-peer remote-peer-name
Run:
mpls ldp timer keepalive-hold interval
42
NOTE
Modifying the value of KeepAlive hold timer leads to reestablish of LDP sessions and all LSPs
based on the LDP sessions.
Run:
system-view
Run:
mpls ldp remote-peer remote-peer-name
Run:
mpls ldp timer keepalive-send interval
Run:
system-view
Run:
mpls
Run:
quit
Run:
mpls ldp
Run:
backoff timer init max
43
NOTE
It is recommended that the initial value be not smaller than 15 and the maximum value be not
smaller than 120 for an Exponential backoff timer.
----End
Context
The NE80E/40E supports either LDP MD5 authentication or LDP keychain authentication.
l
You can configure either LDP MD5 authentication or LDP keychain authentication based on
their separate characteristics:
l
Issue 02 (2011-09-10)
The MD5 algorithm is easy to configure and generates a single password which can be
changed only manually. Therefore, MD5 authentication is applicable to the network
requiring short-term encryption.
44
Keychain authentication involves a set of passwords and adopts a new password when an
old one expires. Keychain authentication is complex to configure and is therefore
recommended on a network requiring high security.
NOTE
On one LDP peer, keychain authentication and MD5 authentication cannot be configured together.
Procedure
l
Run:
system-view
Run:
mpls ldp
Run:
md5-password { plain | cipher } peer-lsr-id password
Characters ^#^# and $@$@ are used to identify passwords with variable lengths. Characters
^#^# are the prefix and suffix of a new password, and characters $@$@ are the prefix and
suffix of an old password. Neither of them can be both configured at the beginning and end of
a plain text password.
CAUTION
Configuring LDP MD5 authentication causes re-establishment of an LDP session and
deletes the LSP associated with the LDP session.
l
Run:
system-view
Run:
mpls ldp
45
3.
Run:
authentication key-chain peer peer-id name keychain-name
CAUTION
Configuring LDP keychain authentication causes re-establishment of an LDP session
and deletes the LSP associated with the LDP session.
----End
Prerequisite
The configurations of the MPLS LDP sessions function are complete.
Procedure
l
Run display mpls ldp [ all ] [ verbose ] command to check information about LDP.
----End
Issue 02 (2011-09-10)
46
Example
Run the display mpls interface command, and you can view information about all the interfaces
enabled with MPLS.
<HUAWEI> display mpls interface
Interface
Status
TE Attr
Pos1/0/0
Up
Dis
LSP Count
0
Run the display mpls ldp command, and you can view information about global LDP including
all timers.
<HUAWEI> display mpls ldp
LDP Global Information
-------------------------------------------------------------------------Protocol Version
: V1
Neighbor Liveness
: 600 Sec
Graceful Restart
: Off
FT Reconnect Timer
: 300 Sec
MTU Signaling
: On
Recovery Timer
: 300 Sec
Capability-Announcement : On
Longest-match
: On
LDP Instance Information
-------------------------------------------------------------------------Instance ID
: 0
VPN-Instance
:
Instance Status
: Active
LSR ID
: 4.4.4.4
Loop Detection
: Off
Path Vector Limit
: 32
Label Distribution Mode : Ordered
Label Retention Mode : Liberal
Instance Deleting State : No
Instance Reseting State : No
--------------------------------------------------------------------------
Run the display mpls ldp interface [ verbose ] command, and you can view information about
an LDP interface, including the transport address and all timers.
<HUAWEI> display mpls ldp interface
LDP Interface Information in Public Network
Codes:LAM(Label Advertisement Mode), IFName(Interface name)
A '*' before an interface means the entity is being deleted.
-----------------------------------------------------------------------------IFName
Status
LAM
TransportAddress
HelloSent/Rcv
-----------------------------------------------------------------------------Pos1/0/0
Active
DU
172.17.1.1
2495/2514
GE2/0/0
Active
DU
172.17.1.1
1106/1094
-----------------------------------------------------------------------------<HUAWEI> display mpls ldp interface verbose
LDP Interface Information in Public Network
-----------------------------------------------------------------------------Interface Name : Pos1/0/0
LDP ID
: 1.1.1.1:0
Transport Address : 1.1.1.1
Entity Status : Active
Effective MTU : 1500
Configured Hello Hold Timer
Negotiated Hello Hold Timer
Configured Hello Send Timer
Configured Keepalive Hold Timer
Configured Keepalive Send Timer
Configured Delay Timer
Label Advertisement Mode
Hello Message Sent/Rcvd
Entity Deletion Status
:
:
:
:
:
:
:
:
:
15 Sec
15 Sec
2 Sec
45 Sec
3 Sec
0 Sec
Downstream Unsolicited
29913/29878 (Message Count)
No
------------------------------------------------------------------------------
Run the display mpls ldp session [ verbose ] command, and you can view that the status of the
LDP session is Operational.
<HUAWEI> display mpls ldp session
LDP Session(s) in Public Network
Codes: LAM(Label Advertisement Mode), SsnAge Unit(DDDD:HH:MM)
Issue 02 (2011-09-10)
47
:
:
:
:
:
:
:
45 Sec
3 Sec
438/438 (Message Count)
Downstream Unsolicited
Available/Available
0000:01:49 (DDDD:HH:MM)
No
Capability:
Capability-Announcement
: On
Run the display mpls ldp peer command and the display mpls ldp remote-peer command,
and you can view information about the peers on both ends of an LDP session.
<HUAWEI> display mpls ldp peer
LDP Peer Information in Public network
A '*' before a peer means the peer is being deleted.
-----------------------------------------------------------------------------PeerID
TransportAddress
DiscoverySource
-----------------------------------------------------------------------------2.2.2.2:0
2.2.2.2
Remote Peer : rtb
Serial0/0/0
3.3.3.3:0
3.3.3.3
Remote Peer : rtc
-----------------------------------------------------------------------------TOTAL: 2 Peer(s) Found.
<HUAWEI> display mpls ldp remote-peer
LDP Remote Entity Information
-----------------------------------------------------------------------------Remote Peer Name : lsrc
Remote Peer IP
: 3.3.3.9
LDP ID
: 1.1.1.9:0
Transport Address : 1.1.1.9
Entity Status : Active
Configured Keepalive Hold Timer
Configured Keepalive Send Timer
Configured Hello Hold Timer
Negotiated Hello Hold Timer
Configured Hello Send Timer
Configured Delay Timer
Hello Packet sent/received
Remote Peer Deletion Status
Issue 02 (2011-09-10)
:
:
:
:
:
:
:
:
45 Sec
--45 Sec
45 Sec
--0 Sec
61/59
No
48
Auto-config
: -------------------------------------------------------------------------------TOTAL: 1 Peer(s) Found.
Applicable Environment
If you need not to strictly control the setup process of LSPs or deploy TE on an MPLS network,
you can set up LSPs by using LDP as the label distribution protocol in an MPLS domain.
The number of LSPs that can be set up on an LSR depends on the capacity and performance of
the LSR. Excessive LSPs, however, may lead to unstability of the LSR.
The setup of LSPs requires that proper routes exist on the LSRs and trigger policies be set on
the LSRs. Only routes that meet the trigger policy can trigger the setup of LSPs. In this manner,
you can control the number of LSPs.
The NE80E/40E provides the following types of policies for controlling the number of LSPs:
l
The policies for setting up LSPs on the egress or ingress are as follows:
All static routes and IGP routes trigger the setup of LSPs.
Labeled BGP routes with 32-bit addresses of the public network trigger the setup of
LSPs. For more information, refer to the chapter "BGP/MPLS IP VPN Configuration"
in the HUAWEI NetEngine80E/40E Router Configuration Guide - VPN.
Host routes trigger the setup of LSPs.
The setup of LSPs is triggered on the basis of the IP prefix list.
All routes trigger the setup of LSPs with LDP being disabled.
When an LSR is a transit LSR, the IP prefix list can be used to filter routes to prevent the
generation of excessive transit LSPs. Only the routes that match the filtering policy can be
used to set up the transit LSP.
As defined in RFC 5036, the label advertisement mode of LDP is classified into two modes:
l
As defined in RFC 5036, the label distribution control mode of LDP is classified into two modes:
l
Independent
Ordered
As defined in RFC 5036, the label retention mode of LDP is classified into two modes:
l
Issue 02 (2011-09-10)
Liberal
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
49
Conservative
Pre-configuration Tasks
Before configuring an LDP LSP, complete the following task:
l
Data Preparation
To configure an LDP LSP, you need the following data.
No.
Data
Prerequisite
Configuring LDP Sessions
Context
The MPLS LDP session is created on neighboring LSRs along the LSP. After the MPLS LDP
session is created, the LDP LSP starts to be set up automatically.
Context
Perform the following operations on the LSR:
Procedure
l
Run:
system-view
Issue 02 (2011-09-10)
50
Run:
interface interface-type interface-number
Run:
mpls ldp advertisement { dod | du }
l When there are multiple links between neighbors, all the interfaces must use the same label
advertisement mode.
l Modifying the label advertisement mode causes LDP sessions to be reestablished.
----End
Context
On a large-scale network deployed with a large number of remote LDP peers, the DLSAMs that
are low-end devices at the edge of the network cannot ensure the network stability or prevent
resource wastes. In this case, you can run the remote-ip auto-dod-request command or the
remote-peer auto-dod-request command to configure the function of triggering a request to a
downstream node for a label mapping message associated with all remote LDP peers or a remote
LDP peer with a specified LSR ID in DoD mode, which can save system resources.
To disable the function of automatically triggering an LSR to send a request to a downstream
node for a label mapping message associated with a specified LSR ID in DoD mode, you can
run the remote-ip auto-dod-request block command.
NOTE
l You should configure a remote LDP session before running the remote-peer auto-dod-request or
remote-ip auto-dod-request command.
l You should run the longest-match command to configure LDP extension for inter-area LSP before
running the remote-peer auto-dod-request or remote-ip auto-dod-request command.
l The mpls ldp advertisement dod command should be run to create an LDP session with a downstream
node in DoD mode before you run the remote-peer auto-dod-request or remote-ip auto-dodrequest command.
Procedure
Step 1 Run:
system-view
Issue 02 (2011-09-10)
51
l You can perform the following procedures to enable the function of triggering a request to
a downstream node for label mapping messages associated with all remote LDP peers or a
remote LDP peer with a specified LSR ID in DoD mode.
1.
Run:
quit
Run:
mpls ldp remote-peer remote-peer-name
The remote MPLS LDP peer is created and the remote MPLS LDP peer view is
displayed.
3.
Run:
remote-ip ip-address
l The IP address of the remote LDP peer must be the LSR ID of the remote LDP peer. When
an LDP LSR ID is different from an MPLS LSR ID, the LDP LSR ID must be adopted.
l Modifying or deleting the configured address of a remote peer leads to the deletion of the
remote LDP session.
4.
Run:
remote-ip auto-dod-request
After the remote-peer auto-dod-request command have been configured globally, to disable
the function of automatically triggering an LSR to send a request to a downstream node for a
label mapping message associated with a remote LDP peer of a specified LSR ID in DoD mode,
you can run the remote-ip auto-dod-request block command.
----End
Context
The NE80E/40E does not support loop detection. However, in the scenario where its neighbor
supports the loop detection function and requires that the notification about whether the loop
detection function be consistent on the two ends, to ensure that the NE80E/40E sets up an LDP
session with such a neighbor, do as follows:
Issue 02 (2011-09-10)
52
Procedure
Step 1 Run:
system-view
The device is enabled to advertise that the device has the capable of loop detection during the
initialization of an LDP session.
NOTE
After the device is configured with the loop-detect command, the device still does not support the loop
detection function but only has the loop detection negotiation capability.
----End
Context
LDP automatically computes the minimum MTU value of all interfaces on each LSP. Based on
the minimum MTU value, MPLS determines the size of packets to be forwarded on the ingress.
This prevents the forwarding failure that is caused by large packets on the transit.
Do as follows on each LSR along an LSP:
Procedure
Step 1 Run:
system-view
53
NOTE
Enabling or disabling the sending of the MTU TLV may cause the original LDP session to be re-created.
----End
Context
By default, an LSR receives all label mapping messages, speeding up the convergence of LDP
LSPs. This, however, results in the establishment of a large number of LSPs, wasting resources.
In this case, an inbound LDP policy can be configured to reduce the number of label mapping
messages to be received, reducing the number of LSPs to be established and saving memory.
NOTE
If multiple inbound policies coexist, the first configured inbound policy takes effect on a certain peer.
Between the following inbound policies, as the peer group named group1 includes the peer with the ID
being 2.2.2.2, the first inbound policy which is configured earlier takes effect on peer 2.2.2.2.
inbound peer 2.2.2.2 fec host
inbound peer peer-group group1 fec none
If two inbound policies have been configured with the same peer parameters, the latter overwrites the
earlier. Between the following inbound policies, the latter overwrites the earlier configuration. That is, the
second inbound policy which is configured later takes effect on peer 2.2.2.2.
inbound peer 2.2.2.2 fec host
inbound peer 2.2.2.2 fec none
Before configuring an inbound policy, you must enable MPLS and MPLS LDP globally.
To delete all inbound policies at a time, run the undo inbound peer all command.
After an inbound LDP policy is configured, the LSR determines whether to receive label
mapping messages from the peer device based on the policy. When the LSR is configured not
to receive label mapping messages from the peer device, the processing mechanism varies
according to the label advertisement mode of the session established between the local device
and its peer.
l
In the case of DU, a liberal LSP is established and cannot be used as an LDP FRR backup
LSP.
In the case of DoD, the local device sends release messages to instruct the peer device to
withdraw labels.
Procedure
Step 1 Run:
system-view
Issue 02 (2011-09-10)
54
An inbound policy for allowing a specified LDP peer to receive label mapping messages for a
specified IGP route is configured.
To apply a policy associated with the same FEC range to an LDP peer group or all LDP peers
receiving label mapping messages, configure peer-group peer-group-name or all in the
command.
----End
Context
By default, an LSR sends label mapping messages to both upstream and downstream LDP peers,
speeding up the convergence of LDP LSPs. This, however, results in the establishment of a large
number of LSPs, wasting resources. In this case, an outbound LDP policy needs to be configured
to reduce the number of label mapping messages to be sent, reducing the number of LDP LSPs
to be established and saving memory.
NOTE
If multiple outbound policies coexist, the first configured outbound policy takes effect on a certain peer.
Between the following outbound policies, as the peer group named group1 includes the peer with the ID
being 2.2.2.2, the first outbound policy which is configured earlier takes effect on peer 2.2.2.2.
outbound peer 2.2.2.2 fec host
outbound peer peer-group group1 fec none
If two outbound policies have been configured with the same peer parameters, the latter overwrites the
earlier. Between the following outbound policies, the latter overwrites the earlier configuration. That is,
the second outbound policy which is configured later takes effect on peer 2.2.2.2.
outbound peer 2.2.2.2 fec host
outbound peer 2.2.2.2 fec none
Before configuring an outbound policy, you must enable MPLS and MPLS LDP globally.
To delete all outbound policies at a time, run the undo outbound peer all command.
After an outbound LDP policy is configured, the LSR determines whether to send label mapping
messages from the peer device based on the policy. The processing mechanism varies according
to the label advertisement mode of the session established between the local device and its peer.
l
In the case of DU, the local device sends valid label mapping messages to the peer device
based on the outbound LDP policy.
In the case of DoD, after receiving a label request message from an upstream device, the
local device checks whether the request matches the outbound LDP policy. If the request
matches the outbound LDP policy, the local device sends a label mapping message to the
upstream device; if the request does not match the outbound LDP policy, the local device
sends no label mapping message but a Notification message to notify the upstream device
of no route.
Procedure
1.
Run:
system-view
Issue 02 (2011-09-10)
55
Run:
mpls ldp
Run:
outbound peer { peer-id | all } split-horizon
Configure an outbound policy for allowing label mapping messages for a specified IGP
route to be sent to a specified LDP peer.
1.
Run:
system-view
Run:
mpls ldp
Run:
outbound peer { peer-id | peer-group peer-group-name | all } fec { none |
host | ip-prefix prefix-name }
Configure an outbound policy for allowing label mapping messages for a specified labeled
BGP route to be sent to a specified LDP peer.
1.
Run:
system-view
Run:
mpls ldp
Run:
outbound peer { peer-id | peer-group peer-group-name | all } bgp-labelroute { none | ip-prefix prefix-name }
56
Context
To set up an LSP according to LDP, you need to set the FEC.
NOTE
l The establishment of an LSP requires precisely matched routes on the LSR. If a loopback interface
with a 32-bit mask is used, the precisely matched host route is required to trigger the establishment of
LSPs.
l Changing LSP triggering policies during the LDP graceful restart (GR) does not take effect.
Procedure
Step 1 Run:
system-view
l To configure the policy of triggering labeled BGP routes of the public network to establish
LSPs, run:
lsp-trigger bgp-label-route [ ip-prefix ip-prefix-name ]
By default, the triggering policy is host, namely, the route of host IP with the 32-bit address
triggering to establish an LSP.
l If the triggering policy is all, all static route entries and IGP route entries trigger to establish
an LSP. BGP public routes cannot trigger to establish LSPs.
l If the triggering policy is ip-prefix, only the FEC entry filtered in the IP address prefix list
can trigger to establish an LSP.
l If the triggering policy is none, the LSP is not established.
l If the triggering policy is bgp-label-route, the labeled BGP routes of the public network
trigger to establish an LSP.
----End
Issue 02 (2011-09-10)
57
Context
Do as follows on the transit node:
Procedure
Step 1 Run:
system-view
Modifying the policy for setting up transit LSPs does not take effect during LDP GR.
----End
Prerequisite
The configurations of the LDP LSP function are complete.
Procedure
l
Run the display mpls ldp [ all ] [ verbose ] command to check all information about LDP.
Run the display mpls ldp lsp [ all ] command to check information of all LDP LSPs.
Run the display mpls lsp [ verbose ] command to check information about LSPs.
----End
Example
If the configurations succeed, you can view the following information:
Issue 02 (2011-09-10)
58
Run the display mpls ldp command, and you can view information about global LDP including
all timers.
<HUAWEI> display mpls ldp
LDP Global Information
-------------------------------------------------------------------------Protocol Version
: V1
Neighbor Liveness
: 600 Sec
Graceful Restart
: Off
FT Reconnect Timer
: 300 Sec
MTU Signaling
: On
Recovery Timer
: 300 Sec
Capability-Announcement : Off
Longest-match
: Off
LDP Instance Information
-------------------------------------------------------------------------Instance ID
: 0
VPN-Instance
:
Instance Status
: Active
LSR ID
: 4.4.4.4
Loop Detection
: Off
Path Vector Limit
: 32
Label Distribution Mode : Ordered
Label Retention Mode : Liberal
Instance Deleting State : No
Instance Reseting State : No
--------------------------------------------------------------------------
Run the display mpls ldp lsp or the display mpls lsp command, and you can view information
about LDP LSPs.
<HUAWEI> display mpls ldp lsp
LDP LSP Information
------------------------------------------------------------------------------DestAddress/Mask In/OutLabel
UpstreamPeer
NextHop
OutInterface
------------------------------------------------------------------------------3.3.3.9/32
NULL/1025
10.1.1.2
Pos1/0/0
------------------------------------------------------------------------------TOTAL: 1 Normal LSP(s) Found.
TOTAL: 0 Liberal LSP(s) Found.
TOTAL: 0 Frr LSP(s) Found.
A '*' before an LSP means the LSP is not established
A '*' before a Label means the USCB or DSCB is stale
A '*' before a UpstreamPeer means the session is in GR state
A '*' before a NextHop means the LSP is FRR LSP
<HUAWEI> display mpls lsp
---------------------------------------------------------------------LSP Information: LDP LSP
---------------------------------------------------------------------FEC
In/Out Label In/Out IF
Vrf Name
1.1.1.1/32
NULL/3
-/Pos1/0/0
Applicable Environment
In a large-scale network, multiple IGP areas usually need to be configured for flexible network
deployment and fast route convergence. In this situation, when advertising routes between IGP
areas, to prevent a large number of routes from consuming too many resources, an Area Border
Router (ABR) needs to aggregate the routes in the area and then advertises the aggregated route
Issue 02 (2011-09-10)
59
to the neighbor IGP areas. However, by default, when establishing LSPs, LDP searches the
routing table for the route that exactly matches the forwarding equivalence class (FEC) carried
in the received Label Mapping message. For aggregated routes, only liberal LDP LSPs rather
than inter-area LDP LSPs can be set up.
In this case, you can run the longest-match command to configure LDP to search for routes
according to the longest match rule to establish inter-area LDP LSPs.
Pre-configuration Tasks
Before configuring LDP Extension for Inter-Area LSP, complete the following tasks:
l
Configuring IP addresses for interfaces to make neighboring nodes reachable at the network
layer
Data Preparation
To configure LDP Extension for Inter-Area LSP, you need the following data.
No.
Data
IS-IS area ID of each nodes and levels of each nodes and interfaces
Procedure
Step 1 Run:
system-view
LDP is configured to search for routes according to the longest match rule to establish LSPs.
NOTE
----End
Issue 02 (2011-09-10)
60
Prerequisite
All configurations of LDP Extension for Inter-Area LSP are complete.
Procedure
l
Run the display mpls lsp command to view the setup of the inter-area LSP after LDP is
configured to search for routes according to the longest match rule to establish LSPs.
----End
Example
Configure LDP to search for routes according to the longest match rule to establish LSPs, and
1.3.0.1/32 and 1.3.0.2/32 are routes to other IGP area. You can view that an inter-area LSP is
established. The configuration result is as follows:
[HUAWEI] display mpls lsp
------------------------------------------------------------------------------LSP Information: LDP LSP
------------------------------------------------------------------------------FEC
In/Out Label In/Out IF
Vrf Name
1.2.0.1/32
NULL/3
-/Pos1/0/0
1.2.0.1/32
1024/3
-/Pos1/0/0
1.3.0.1/32
NULL/1025
-/Pos1/0/0
1.3.0.1/32
1025/1025
-/Pos1/0/0
1.3.0.2/32
NULL/1026
-/Pos1/0/0
1.3.0.2/32
1026/1026
-/Pos1/0/0
Applicable Environment
The LDP multi-instance is used on the BGP/MPLS VPN. To configure the LDP multi-instance,
you need to bind LDP to a created IP VPN instance.
Pre-configuration Tasks
Before configuring an LDP multi-instance, complete the following tasks:
l
Enabling MPLS
Issue 02 (2011-09-10)
61
Data Preparation
To configure an LDP multi-instance, you need the following data.
No.
Data
Context
To configure the transport address for an LDP instance, you must use the IP address of the
interfaces that are bound to the same VPN instance.
NOTE
In LDP multiple instances, you can adopt the interface address to establish a session.
Procedure
Step 1 Run:
system-view
LDP for the specified VPN instance is enabled and the MPLS LDP VPN instance view is
displayed.
Note:
l Configurations in the MPLS LDP VPN instance view have impact only on LDP-enabled
interfaces that are bound to the same VPN instance.
l Configurations in the MPLS LDP view have no impact on LDP-enabled interfaces that are
bound to the VPN instance.
Step 3 (Optional) Run:
lsr-id lsr-id
62
In most applications, you need not change the default LDP LSR ID. In some networking schemes that VPN
instances are used, for example, BGP or MPLS VPN, configure an LSR ID separately for LDP multiinstance to ensure normal establishment of the TCP connection, if the address space of the VPN overlaps
that of the public network.
----End
Prerequisite
The configurations of the LDP Multi-Instance function are complete.
Procedure
l
Run the display mpls ldp vpn-instance vpn-instance-name command to check information
about LDP of a specified VPN instance.
----End
Example
After the configuration, run the preceding command, and you can view information about the
specified LDP VPN instance.
Applicable Environment
When the static BFD works in an LDP LSP, note that:
l
The detection only supports the LDP LSP that is triggered to establish by the host route.
NOTE
BFD for LSP can function properly though the forward path is an LSP and the backward path is an IP link.
The forward path and the backward path must be established over the same link; otherwise, if a fault occurs,
BFD cannot identify the faulty path. Before deploying BFD, ensure that the forward and backward paths
are over the same link so that BFD can correctly identify the faulty path.
Issue 02 (2011-09-10)
63
Pre-configuration Tasks
Before configuring the static BFD for LDP LSP, complete the following tasks:
l
Data Preparations
Before configuring the static BFD for LDP LSP, you need the following data.
No.
Data
Context
Do as follows on each LSR on both ends of a link that to be detected:
Procedure
Step 1 Run:
system-view
This node is enabled with the global BFD function. The BFD global view is displayed.
----End
Context
Do as follows on the ingress of an LSP:
Issue 02 (2011-09-10)
64
Procedure
Step 1 Run:
system-view
When configuring static BFD for LDP LSP on a network deployed with LDP over TE, specify interface
interface-type interface-number as the tunnel interface.
The local identifier and remote identifier on both ends of a BFD session must accord with each other.
Otherwise, the session cannot be established correctly. In addition, the local identifier and remote identifier
cannot be modified after configuration.
Step 4 (Optional) Run the following commands to adjust the minimum interval for the local device to
send BFD packets, the minimum interval for receiving BFD packets and the local BFD detection
multiple:
1.
2.
Run the mpls command to globally enable MPLS and the enter the MPLS view.
3.
Run the mpls bfd min-tx-interval interval command to adjust the minimum interval for
the local device to send BFD packets.
The minimum interval for the local device to send BFD packets is set.
By default, the value is 1000 milliseconds.
If the backward link is an IP link, this parameter is not applicable.
Actual interval for the local device to send BFD packets = MAX { Locally configured
interval for sending BFD packets, Remotely configured interval for receiving BFD
packets}; Actual interval for the local to receive BFD packets = MAX {Remotely
configured interval for sending BFD packets, Locally configured interval for receiving
BFD packets}; Local detection period = Actual interval for the local device to Receive BFD
packets x Remotely configured BFD detection multiple.
For example, assume that the values of parameters are as follows:
Issue 02 (2011-09-10)
65
l On the local device, the interval for sending BFD packets is set to 200 ms, the interval
for receiving BFD packets is set to 300 ms, and the detection multiple is set to 4.
l On the peer device, the interval for sending BFD packets is 100 ms, the interval for
receiving BFD packets is 600 ms, and the detection multiple is 5.
Then,
l On the local device, the actual interval for sending BFD packets is 600 ms calculated
by using the formula max {200 ms, 600 ms}, the interval for receiving BFD packets is
300 ms calculated by using the formula max {100 ms, 300 ms}, and the detection period
is 1500 ms calculated by 300 ms multiplied by 5.
l On the peer device, the actual interval for sending local BFD packets is 300 ms obtained
by using the formula max {100 ms, 300 ms}, the interval for receiving BFD packets is
600 ms obtained by using the formula max {200 ms, 600 ms}, and the detection period
is 2400 ms obtained by 600 ms multiplied by 4.
4.
Run the mpls bfd min-rx-interval interval command to adjust the minimum interval for
receiving BFD packets.
The minimum interval for receiving BFD packets is adjusted on the local device.
By default, the value is 1000 milliseconds.
If the backward link is an IP link, this parameter is not applicable.
5.
Run the mpls bfd detect-multiplier multiplier command to adjust the local BFD detection
multiple.
The default value is 3.
6.
7.
Run the bfd cfg-name command to enter the BFD session view.
Step 5 Run:
process-pst
The BFD session status changes can be advertised to the application on the upper layer.
Step 6 Run:
commit
Follow-up Procedure
When the BFD session is established and its status is Up, the BFD starts to detect failure in an
LDP LSP.
When the LDP LSP is deleted, the BFD status turns Down.
The system does not delete BFD configuration entries and session entries until the LDP session
is deleted.
66
Context
The IP link, LSP, or TE tunnel can be used as the reverse tunnel to inform the ingress of a fault.
To avoid affecting BFD detection, an IP link is preferentially selected to inform the ingress of
an LSP fault. The process-pst command is prohibited when a reverse tunnel is configured. If
the configured reverse tunnel requires BFD detection, you can configure a pair of BFD sessions
for it.
Do as follows on the egress of the LSP:
Procedure
Step 1 Run:
system-view
The local identifier and remote identifier on both ends of a BFD session must accord with each other. The
session cannot be established correctly otherwise. In addition, the local identifier and remote identifier
cannot be modified after configuration.
Step 4 (Optional) Run the following commands to adjust the minimum interval for the local device to
send BFD packets, the minimum interval for receiving BFD packets and the local BFD detection
multiple:
1.
2.
Run the mpls command to globally enable MPLS and the enter the MPLS view.
3.
Run the mpls bfd min-tx-interval interval command to adjust the minimum interval for
the local device to send BFD packets.
The minimum interval for the local device to send BFD packets is set.
By default, the value is 1000 milliseconds.
Issue 02 (2011-09-10)
67
Run the mpls bfd min-rx-interval interval command to adjust the minimum interval for
receiving BFD packets.
The minimum interval for receiving BFD packets is adjusted on the local device.
By default, the value is 1000 milliseconds.
If the backward link is an IP link, this parameter is not applicable.
5.
Run the mpls bfd detect-multiplier multiplier command to adjust the local BFD detection
multiple.
The default value is 3.
6.
7.
Run the bfd cfg-name command to enter the BFD session view.
Step 5 Run:
commit
Prerequisite
The configurations of the static BFD for LDP LSP function are complete.
Issue 02 (2011-09-10)
68
Procedure
l
Run the display bfd configuration { all | static } [ for-lsp ] command to check the BFD
configuration.
Run the display bfd session { all | static } [ for-lsp ] command to check information about
the BFD session.
Run the display bfd statistics session { all | static } [ for-ip | for-lsp ] command to check
information about BFD statistics.
----End
Applicable Environment
With dynamic BFD for LDP LSP, failure detection speeds up and the workload of configuring
decreases. In addition, LDP FRR is well supported for the LSP for providing better services.
NOTE
When working in LDP LSP, the dynamic BFD supports only the LDP LSP that is created after the host
route is triggered.
BFD for LSP can function properly though the forward path is an LSP and the backward path is an IP link.
The forward path and the backward path must be established over the same link; otherwise, if a fault occurs,
BFD cannot identify the faulty path. Before deploying BFD, ensure that the forward and backward paths
are over the same link so that BFD can correctly identify the faulty path.
Pre-configuration Tasks
Before configuring the dynamic BFD for LDP LSP, complete the following tasks:
l
Data Preparations
To configure the dynamic BFD for LDP LSP, you need the following data.
Issue 02 (2011-09-10)
No.
Data
69
No.
Data
Context
Do as follows on the ingress and egress nodes:
Procedure
Step 1 Run:
system-view
Procedure
l
Run:
system-view
Run:
mpls
Run:
mpls bfd enable
An LDP LSP is enabled with the capability of creating BFD session dynamically.
The BFD session is not created after this command is run.
l
Run:
system-view
Issue 02 (2011-09-10)
70
Run:
bfd
Run:
mpls-passive
Context
Do as follows on the egress of an LSP to be detected:
Procedure
Step 1 Run:
system-view
The triggering policy to establish the session of dynamic BFD for LDP LSP is configured.
After the command is run, the BFD session is started to create.
There are two triggering policies to establish the session of dynamic BFD for LDP LSP:
l Host mode: is adopted when all host addresses are required to be triggered to create BFD
session. You can specify parameters of nexthop and outgoing-interface to define LSPs that
can create a BFD session.
l FEC list mode: is adopted when only a part of host addresses are required to be triggered to
create a BFD session. You can use the fec-list command to specify host addresses.
----End
Issue 02 (2011-09-10)
71
Context
Do as follows on the ingress:
Procedure
Step 1 Run:
system-view
72
Then,
l On the local device, the actual interval for sending BFD packets is 600 ms calculated by
using the formula max {200 ms, 600 ms}, the interval for receiving BFD packets is 300 ms
calculated by using the formula max {100 ms, 300 ms}, and the detection period is 1500 ms
calculated by 300 ms multiplied by 5.
l On the peer device, the actual interval for sending BFD packets is 300 ms calculated by using
the formula max {100 ms, 300 ms}, the interval for receiving BFD packets is 600 ms
calculated by using the formula max {200 ms, 600 ms}, and the detection period is 2400 ms
calculated by 600 ms multiplied by 4.
----End
Prerequisite
The configurations of the dynamic BFD for LDP LSP function are complete.
Procedure
l
Run the display bfd configuration all [ verbose ] command to check the BFD
configuration (ingress).
Run the display bfd configuration passive-dynamic [ peer-ip peer-ip remotediscriminator discriminator ] [ verbose ] command to check the BFD configuration
(egress).
Run the display bfd session all [ verbose ] command to check information about the BFD
session (ingress).
Run the display mpls bfd session [ statistics | [ protocol { ldp | cr-static | rsvp-te } ] |
[ outgoing-interface interface-type interface-number ] | [ nexthop ip-address ] | [ fec fecaddress ] | verbose | monitor ] command to check information about BFD session (ingress).
----End
Example
Run the display bfd session all command, and you can view the state of BFD session that is
established dynamically. The state of the BFD session is Up, and the type of the link that is
bound to the session is LDP_LSP.
<HUAWEI> display bfd session all verbose
-------------------------------------------------------------------------------Session MIndex : 256
State : Up
Name : dyn_8192
-------------------------------------------------------------------------------Local Discriminator
: 8192
Remote Discriminator
: 8192
Session Detect Mode
: Asynchronous Mode Without Echo Function
BFD Bind Type
: LDP_LSP
Bind Session Type
: Dynamic
Bind Peer Ip Address
: 3.3.3.3
NextHop Ip Address
: 192.168.1.2
Issue 02 (2011-09-10)
73
Bind Interface
: Pos1/0/0
LSP Token
: 0x3002001
FSM Board Id
: 3
TOS-EXP
: 6
Min Tx Interval (ms)
: 100
Min Rx Interval (ms)
: 100
Actual Tx Interval (ms): 100
Actual Rx Interval (ms): 100
Local Detect Multi
: 4
Detect Interval (ms)
: 400
Echo Passive
: Disable
Acl Number
: Destination Port
: 3784
TTL
: 1
Proc interface status : Disable
WTR Interval (ms)
: -Process PST
: Enable
Active Multi
: 3
Last Local Diagnostic : No Diagnostic
Bind Application
: VRRP | LSPM | LSPM | L2VPN | OAM_MANAGER
Session TX TmrID
: -Session Detect TmrID
: -Session Init TmrID
: -Session WTR TmrID
: -Session Echo Tx TmrID : PDT Index
: FSM-0 | RCV-0 | IF-0 | TOKEN-0
Session Description
: --------------------------------------------------------------------------------Total UP/DOWN Session Number : 1/0
Run the display bfd session passive-dynamic verbose command on the egress, and you can
view the state of BFD session that is established passively. The field of BFD bind type is peer
IP address. This indicates that the BFD packets sent from this ingress are transported through
IP routes. BFD parameters cannot be adjusted on the egress. Thus, by default, min-txinterval and min-tx-interval are 10 respectively. In fact, however, the actual interval between
sending time and the receiving time depends on the negotiation between both ends.
<HUAWEI> display bfd session passive-dynamic verbose
-------------------------------------------------------------------------------Session MIndex : 256
(Multi Hop) State : Up
Name : dyn_8192
-------------------------------------------------------------------------------Local Discriminator
: 8192
Remote Discriminator
: 8192
Session Detect Mode
: Asynchronous Mode Without Echo Function
BFD Bind Type
: Peer Ip Address
Bind Session Type
: Entire_Dynamic
Bind Peer Ip Address
: 192.168.1.1
Bind Interface
: -FSM Board Id
: 3
TOS-EXP
: 6
Min Tx Interval (ms)
: 10
Min Rx Interval (ms)
: 10
Actual Tx Interval (ms): 100
Actual Rx Interval (ms): 100
Local Detect Multi
: 3
Detect Interval (ms)
: 300
Echo Passive
: Disable
Acl Number
: Destination Port
: 3784
TTL
: 253
Proc Interface Status : Disable
Process PST
: Disable
WTR Interval (ms)
: -Local Demand Mode
: Disable
Active Multi
: 3
Last Local Diagnostic : No Diagnostic
Bind Application
Session TX TmrID
: -Session Detect TmrID
: -Session Init TmrID
: -Session WTR TmrID
: -Session Echo Tx TmrID : PDT Index
: FSM-0 | RCV-0 | IF-0 | TOKEN-0
Session Description
: --------------------------------------------------------------------------------Total UP/DOWN Session Number : 1/0
Issue 02 (2011-09-10)
74
Applicable Environment
LDP FRR provides MPLS with a fast reroute function to implement the local port-level backup.
In addition, the data loss decreases.
Pre-configuration Tasks
Before configuring LDP FRR, complete the following tasks:
l
Configuring MPLS
If the LDP FRR is based on the BFD, you need to configure the one-hop BFD.
For details of the one-hop BFD, refer to "BFD Configuration" in the HUAWEI NetEngine80E/
40E Router Configuration Guide - Reliability.
Data Preparation
To configure LDP FRR, you need the following data.
No.
Data
Name of the IP prefix list that can trigger the establishment of bypass LSPs
Context
Do as follows on the ingress:
Procedure
Step 1 Run:
system-view
75
Step 2 Run:
interface interface-type interface-number
----End
Context
The procedure is only applicable to configure the LDP FRR based on BFD.
Do as follows on the ingress:
Procedure
Step 1 Run:
system-view
76
Prerequisite
The configurations of the LDP FRR function are complete.
Procedure
l
Run the display mpls lsp command to check information about LSPs enabled with LDP
FRR.
----End
Applicable Environment
In a network where LDP Fast Reroute (FRR) is configured, traffic is fast switched to the backup
LSP when a link becomes faulty. In this case, traffic is uninterrupted and is switched within 50
ms.
There are two types of LDP FRR: manual LDP FRR and LDP Auto FRR.
l
In the mode of manual LDP FRR, you need to configure a backup LSP by specifying the
outbound interfaces or the next hops. The configuration procedure is complex, but the
backup LSP can be specified. Therefore, manual LDP FRR is more flexible, and is
applicable to the network with a simple structure.
In the mode of LDP Auto FRR, a backup LSP can be automatically generated according
to the triggering policy. The configuration procedure is more simplified. In addition, loops
that may occur during the manual configuration can be avoided. Therefore, LDP Auto FRR
is applicable to the large-scale network with a complicated structure.
Pre-configuration Tasks
Before configuring LDP Auto FRR, complete the following tasks:
Issue 02 (2011-09-10)
77
Configuring IP addresses for interfaces to ensure that neighboring nodes are reachable at
the network layer
Configuring IS-IS to advertise the network segments connecting to interfaces on each node
and to advertise the routes of hosts with Label Switching Router (LSR) IDs
Data Preparation
To configure LDP Auto FRR, you need the following data.
No.
Data
Procedure
Step 1 Run:
system-view
During LDP GR, changing the policy for triggering the setup of backup LSPs is not allowed.
----End
78
Prerequisite
All LDP Auto FRR configurations are complete.
Procedure
l
Run the display mpls lsp command to view information about the established backup LSP
after LDP Auto FRR is enabled.
----End
Example
Enable LDP Auto FRR. You can view that the backup LSP to the destination 2.2.2.9/32 has
already been set up. The configuration result is as follows:
[HUAWEI] display mpls lsp
------------------------------------------------------------------------------LSP Information: LDP LSP
------------------------------------------------------------------------------FEC
In/Out Label In/Out IF
Vrf Name
2.2.2.9/32
NULL/3
-/Pos1/0/0
**LDP FRR**
/1025
/Pos1/0/1
2.2.2.9/32
1024/3
-/Pos1/0/0
**LDP FRR**
/1025
/Pos1/0/1
3.3.3.9/32
NULL/3
-/Pos1/0/1
**LDP FRR**
/1025
/Pos1/0/0
3.3.3.9/32
1025/3
-/Pos1/0/1
**LDP FRR**
/1025
/Pos1/0/0
4.4.4.9/32
NULL/1026
-/Pos1/0/1
**LDP FRR**
/1026
/Pos1/0/0
4.4.4.9/32
1026/1026
-/Pos1/0/1
**LDP FRR**
/1026
/Pos1/0/0
10.1.3.0/24
1027/3
-/Pos1/0/1
10.1.4.0/24
1028/3
-/Pos1/0/1
**LDP FRR**
/1027
/Pos1/0/0
Applicable Environment
In the networking where primary and backup LSPs are used, synchronization between LDP and
IGP is applied to avoid traffic loss in case the primary LSP fails. The situations are as follows:
l
Issue 02 (2011-09-10)
When the primary LSP fails, the IGP traffic and LSP traffic are switched to the backup
LSP. When the primary LSP recovers, IGP converges faster than the creation of the LDP
session. Thus, IGP traffic is switched back to the primary LSP before the LDP session is
set up. This causes the loss of LSP traffic.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
79
When the primary LSP runs normally whereas the LDP sessions between the nodes along
the primary LSP fail, the LSP traffic is switched to the backup LSP. The IGP traffic,
however, is still transmitted along the primary LSP. As a result, the LSP traffic is lost.
Pre-configuration Tasks
Before configuring synchronization between LDP and IGP, complete the following tasks:
l
Data Preparation
To configure synchronization between LDP and IGP, you need the following data.
No.
Data
Type and number of the interface on which the backup LSP is set up
Timer value
Procedure
l
When OSPF runs as an IGP, do as follows on the interfaces of both ends of the link between
the crossing node of the active link and the standby link and the LDP neighboring node on
the active link:
1.
Run:
system-view
Run:
interface interface-type interface-number
Run:
ospf ldp-sync
When IS-IS runs as an IGP, do as follows on the interfaces of both ends of the link between
the crossing node of active and standby links and the LDP neighboring node on the active
link:
1.
Run:
system-view
Issue 02 (2011-09-10)
80
Run:
interface interface-type interface-number
Run:
isis enable process-id
IS-IS is enabled.
4.
Run:
isis ldp-sync
Context
Do as follows on the interface:
Procedure
l
When OSPF runs as an IGP, do as follows on the interfaces of both ends of the link between
the crossing node of active and standby links and the LDP neighboring node on the active
link:
1.
Run:
system-view
Run:
interface interface-type interface-number
Run:
ospf timer ldp-sync hold-down value
The interval OSPF should wait for an LDP session to be established is set.
By default, the hold-down timer value is 10 seconds.
l
When IS-IS runs as an IGP, do as follows on the interfaces of both ends of the link between
the crossing node of active and standby links and the LDP neighboring node on the active
link:
1.
Run:
system-view
Run:
interface interface-type interface-number
Issue 02 (2011-09-10)
81
Run:
isis timer ldp-sync hold-down value
The interval IS-IS should wait for an LDP session to be established is set.
By default, the hold-down timer value is 10 seconds.
----End
Context
Do as follows on the interface:
Procedure
l
When OSPF runs as an IGP, do as follows on the interfaces of both ends of the link between
the crossing node of active and standby links and the LDP neighboring node on the active
link:
1.
Run:
system-view
Run:
interface interface-type interface-number
Run:
ospf timer ldp-sync hold-max-cost { value | infinite }
The interval for advertising the maximum cost in the LSAs of local LSRs through
OSPF is set.
By default, the value of the hold-max-cost timer is 10 seconds.
You can choose different parameters as required.
When OSPF carries only LDP services, to ensure that the route selected by OSPF
is always the same as the LDP LSP, infinite need to be specified.
When OSPF carries multiple services including LDP services, to ensure that OSPF
route selection and other services still run normally in case the LDP session of the
primary LSP fails, value can be specified.
If this command is configured repeatedly, the latest configuration takes effect.
l
When IS-IS runs as an IGP, do as follows on the interfaces of both ends of the link between
the crossing node of active and standby links and the LDP neighboring node on the active
link:
1.
Run:
system-view
Issue 02 (2011-09-10)
82
Run:
interface interface-type interface-number
Run:
isis timer ldp-sync hold-max-cost { value | infinite }
The interval for advertising the maximum cost in the LSAs of local LSRs through ISIS is set.
By default, the value of the hold-max-cost timer is 10 seconds.
You can choose different parameters as required.
When IS-IS carries only LDP services, to ensure that the route selected by IS-IS
is always the same as the LDP LSP, infinite need to be specified.
When IS-IS carries multiple services including LDP services, to ensure that IS-IS
route selection and other services still run normally in case the LDP session of the
primary LSP fails, value can be specified.
If this command is configured repeatedly, the latest configuration takes effect.
----End
Context
Do as follows on the interfaces of both ends of the link between the crossing node of active and
standby links and the LDP neighboring node on the active link:
Procedure
Step 1 Run:
system-view
The period of waiting for the LSP setup after the establishment of the LDP session is set.
By default, the value of the delay timer is 10 seconds.
----End
Issue 02 (2011-09-10)
83
Prerequisite
The configurations of the synchronization between LDP and IGP function are complete.
Procedure
l
Run the display ospf ldp-sync interface { all | interface-type interface-number } command
to check information about synchronization between LDP and OSPF on the interface.
Run the display rm interface [ interface-type interface-number | vpn-instance vpninstance-name ] command to check information about the route management.
----End
Example
l
If the configurations succeed, run the display ospf ldp-sync or display isis ldp-sync
command, and you can view that the status of the interface configured with synchronization
between LDP and IGP is Sync-Achieved.
Run the display rm interface command, you can view that the LDP-ISIS or LDP-OSPF
is enabled.
Applicable Environment
Synchronization between LDP and static routes is applicable to an MPLS network with primary
and backup LSPs. On such an MPLS network, LSRs establish LSPs based on static routes. When
the LDP session of the primary link becomes faulty (the fault is not caused by a link failure) or
the primary link recovers, synchronization between LDP and static routes minimizes traffic loss
during traffic switchover and switchback. As shown in Figure 2-1, there is a static route between
Issue 02 (2011-09-10)
84
LSRA and LSRD, and an LSP is established between the two devices based on the static route.
Normally, the link LSRALSRBLSRD is preferred.
l
In a switchover scenario, when the LDP session of the primary link becomes faulty (the
fault is not caused by a link failure), traffic transmitted through the static route is not
switched to the backup link. As a result, MPLS traffic on the primary link is interrupted.
Normally, after an LDP session is established, MPLS traffic is forwarded along the primary
link LSRALSRBLSRD. If the LDP session between LSRA and LSRB is disconnected,
the LSP is immediately switched to the backup link LSRALSRCLSRD. Because the
link between LSRA and LSRB works properly, traffic transmitted through the static route
is not switched to the backup link. As a result, LDP is not synchronous with the static route,
and MPLS traffic is interrupted.
After synchronization between LDP and static routes is enabled, when the LDP session
goes Down, traffic is automatically switched to the backup link, thus ensuring non-stop
traffic forwarding.
In a switchback scenario, when the primary link recovers, traffic transmitted through a
static route is first switched back to the primary link because the static route converges
faster than LDP. However, the backup LSP becomes unavailable, and the primary LSP has
not been established. As a result, MPLS traffic is interrupted.
When the link between LSRA and LSRB becomes faulty, traffic is immediately switched
to the backup link LSRALSRCLSRD. After the link between LSRA and LSRB
recovers, traffic transmitted through the static route is immediately switched to the primary
link LSRALSRBLSRD. However, the backup LSP becomes unavailable, and the
primary LSP has not recovered. Therefore, traffic is interrupted.
After synchronization between LDP and static routes is enabled, when the primary LSP is
established, traffic is switched back to the primary link, thus ensuring non-stop traffic
forwarding.
Figure 2-1 Networking diagram for configuring synchronization between LDP and static routes
LSRB
LSRE
LSRD
LSRA
LSRC
Primary link
Bypass link
Issue 02 (2011-09-10)
85
Pre-configuration Tasks
Before configuring synchronization between LDP and static routes, complete the following
tasks:
l
Enabling MPLS
Data Preparation
To configure synchronization between LDP and static routes, you need the following data.
No.
Data
Time during which a static route waits for an LDP session to be established, that is,
time of the Hold-down timer
Context
With synchronization between LDP and static routes, you can switch traffic from the faulty
primary link to the backup link by suppressing the activation of static routes and delay traffic
switchback to the primary link, thus ensuring that LDP is synchronous with static routes.
NOTE
Only the static route with a specified outbound interface can be configured with synchronization between
LDP and static routes.
Procedure
Step 1 Run:
system-view
86
Context
After a Hold-down timer is set on an interface, the static route enabled with synchronization
between LDP and static routes becomes inactive temporarily and waits for an LDP session to
be established before the Hold-down timer expires. This implements synchronization between
LDP and static routes. If the Hold-down timer expires, the static route becomes active regardless
of whether the LDP session has been established.
NOTE
Procedure
Step 1 Run:
system-view
The outbound interface view of the primary link of the static route is displayed.
Step 3 Run:
static-route timer ldp-sync hold-down { timer | infinite }
Prerequisite
The configurations of synchronization between LDP and static routes are complete.
Issue 02 (2011-09-10)
87
Procedure
l
----End
Example
Run the display static-route ldp-sync command after configuring synchronization between
LDP and static routes. If the following is displayed, it means that the configuration succeeds.
<HUAWEI> display static-route ldp-sync
Total number of routes enable LDP-sync: 1
-------------------------------------------------------interface GigabitEthernet1/0/0
Enable ldp-sync static routes number: 1
Static-route ldp-sync holddown timer: 10s
Sync State: Normal
Dest = 1.1.1.1, Mask = 32, NextHop = 2.2.2.2
---------------------------------------------------------
Applicable Environment
The Generalized TTL Security Mechanism (GTSM) prevents attacks by using the TTL detection.
An attacker simulates real LDP unicast packets and sends the packets in a large quantity to a
node. After receiving the packets, an interface of the LSR directly sends the packets to LDP of
the control plane if the interface finds that the packets are sent by the local node, without checking
the validity of the packets. Because the control plane of the node needs to process the "legal"
packets, the system becomes abnormally busy and CPU usage is high.
GTSM protects the node by checking whether the TTL value in the IP packet header is within
a pre-defined range, and thus enhances the system security.
Pre-configuration Tasks
Before configuring basic LDP GTSM functions, complete the following tasks:
l
Data Preparation
To configure the basic LDP GTSM functions, you need the following data.
Issue 02 (2011-09-10)
88
No.
Data
Context
Do as follows on the two LDP peers that need to be configured with GTSM:
Procedure
Step 1 Run:
system-view
Prerequisite
The configurations of the LDP GTSM function are complete.
Procedure
l
Run the display gtsm statistics { slot-id | all } command to check the GTSM statistics.
----End
Issue 02 (2011-09-10)
89
Example
Run the display gtsm statistics command, and you can view the GTSM statistics in each slot,
including the total number of LDP, BGP, BGP4+, and OSPF packets and the number of packets
that are allowed to pass through or the number of dropped packets.
<HUAWEI> display gtsm statistics all
GTSM Statistics Table
---------------------------------------------------------------SlotId Protocol Total Counters Drop Counters Pass Counters
---------------------------------------------------------------6
BGP
0
0
0
6
BGPv6
0
0
0
6
OSPF
0
0
0
6
LDP
11
0
11
----------------------------------------------------------------
Applicable Environment
It is necessary to enable LDP GR to maintain normal forwarding and resume the LDP session
and establish LSPs after the switchover and system update.
NOTE
In practical applications, the system-level GR is usually configured in the hardware environment with dual
main control boards. In this manner, the service can be forwarded when the main control board fails.
Pre-configuration Tasks
Before configuring LDP GR, complete the following tasks:
l
Data Preparation
To configure LDP GR, you need the following data.
Issue 02 (2011-09-10)
No.
Data
90
No.
Data
Context
Do as follows on the LDP GR Restarter and its neighbor nodes:
Procedure
Step 1 Run:
system-view
The MPLS function is enabled on the local node and the MPLS view is displayed.
Step 4 Run:
quit
The LDP function is enabled on the local node and the LDP view is displayed.
Step 6 Run:
graceful-restart
----End
Issue 02 (2011-09-10)
91
Context
Do as follows on the GR restarter:
NOTE
Modifying the values of the LDP GR timers may lead to reestablishment of LDP sessions.
Procedure
Step 1 Run:
system-view
Context
Do as follows on the GR Helper:
NOTE
If any timer value related to LDP GR is modified, the LDP session is recreated.
Procedure
Step 1 Run:
system-view
92
The time of the Reconnect timer for the LDP session is set.
By default, the time of the Reconnect timer is set to 300 seconds.
Step 4 Run:
graceful-restart timer recovery time
Prerequisite
The configurations of the LDP GR function are complete.
Procedure
l
Run the display mpls graceful-restart command to check information about GR of all
protocols related to MPLS.
Run the display mpls ldp [ all ] [ verbose ] command to check information about LDP.
Run the display mpls ldp session [ all ] [ verbose ] command to check information about
the LDP session.
----End
Example
l
Run the display mpls ldp command, and you can view that the state of Graceful Restart
is On. That is, LDP GR is enabled.
Run the display mpls ldp command or the display mpls ldp session verbose command,
and you can view the values of LDP session Reconnect timer, Neighbor-liveness timer,
and LSP Recovery timer.
Issue 02 (2011-09-10)
93
Context
CAUTION
Resetting LDP may temporarily affect the reestablishment of the LSP. Take care to reset LDP.
Resetting LDP is prohibited during the LDP GR.
After you confirm to reset LDP, run the following commands in the user view.
Procedure
l
Run the reset mpls ldp command to reset configurations of the global LDP instance.
Run the reset mpls ldp vpn-instance vpn-instance-name command to reset LDP
configurations on a specified LDP instance.
Run the reset mpls ldp all command to reset configurations on all LDP instances.
Run the reset mpls ldp peer peer-id command to reset a specified peer.
Run the reset mpls ldp vpn-instance vpn-instance-name peer peer-id command to reset
the peer on a specified VPN instance.
----End
Context
CAUTION
MPLS statistics cannot be restored after being cleared. Therefore, confirm the action before you
run the following commands.
Procedure
l
Run the reset mpls statistics interface { interface-type interface-number | all } command
in the user view to clear the statistics of the MPLS interface.
Run the reset mpls statistics lsp { lsp-name | all } command in the user view to clear LSP
statistics.
----End
Issue 02 (2011-09-10)
94
Context
You can run the following commands in any view to perform MPLS ping and MPLS tracert.
Procedure
l
Run:
ping lsp [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m
interval | -r reply-mode | -s packet-size | -t time-out | -v ] * ip destinationaddress mask-length [ ip-address ] [ nexthop nexthop-address | draft6 ]
Run:
tracert lsp [ -a source-ip | -exp exp-value | -h ttl-value | -r reply-mode | t time-out ] * ip destination-address mask-length [ ip-address ] [ nexthop
nexthop-address | draft6 ]
Context
Run the following commands in the system view to notify the Network Management System
(NMS) of the LSP status change.
By default, the trap function is disabled during the setup of the LDP LSP.
Procedure
l
----End
95
Follow-up Procedure
NOTE
This document takes interface numbers and link types of the NE40E-X8 as an example. In working
situations, the actual interface numbers and link types may be different from those used in this document.
Networking Requirements
As shown in Figure 2-2, local LDP sessions are set up between LSRA and LSRB, and between
LSRB and LSRC.
Figure 2-2 Networking diagram of Local LDP session configuration
Loopback1
Loopback1
Loopback1
1.1.1.9/32
2.2.2.9/32
3.3.3.9/32
POS1/0/0 POS1/0/0
POS2/0/0 POS1/0/0
10.1.1.1/30 10.1.1.2/30
10.2.1.1/30 10.2.1.2/30
LSRA
LSRB
LSRC
Configuration Roadmap
The configuration roadmap is as follows:
1.
Enable global MPLS functions and MPLS LDP functions on each LSR.
2.
3.
Data Preparation
To complete the configuration, you need the following data:
l
IP address of each interface on each LSR as shown in Figure 2-2, OSPF process ID, and
OSPF area ID
Procedure
Step 1 Configure IP addresses of the interfaces.
Configure IP addresses and masks for all the interfaces as shown in Figure 2-2, including the
loopback interface. The detailed configuration is not mentioned here.
Issue 02 (2011-09-10)
96
Step 2 Configure the basic MPLS functions and MPLS LDP functions on each LSR.
# Configure LSRA.
[LSRA] mpls lsr-id 1.1.1.9
[LSRA] mpls
[LSRA-mpls] quit
[LSRA] mpls ldp
[LSRA-mpls-ldp] quit
# Configure LSRB.
[LSRB] mpls lsr-id 2.2.2.9
[LSRB] mpls
[LSRB-mpls] quit
[LSRB] mpls ldp
[LSRB-mpls-ldp] quit
# Configure LSRC.
[LSRC] mpls lsr-id 3.3.3.9
[LSRC] mpls
[LSRC-mpls] quit
[LSRC] mpls ldp
[LSRC-mpls-ldp] quit
# Configure LSRB.
[LSRB] interface pos 1/0/0
[LSRB-Pos1/0/0] mpls
[LSRB-Pos1/0/0] quit
[LSRB] interface pos 2/0/0
[LSRB-Pos2/0/0] mpls
[LSRB-Pos2/0/0] quit
# Configure LSRC.
[LSRC] interface pos 1/0/0
[LSRC-Pos1/0/0] mpls
[LSRC-Pos1/0/0] quit
Step 4 Enable the MPLS LDP functions on the interfaces of both ends of the local LDP session.
# Configure LSRA.
[LSRA] interface pos 1/0/0
[LSRA-Pos1/0/0] mpls ldp
[LSRA-Pos1/0/0] quit
# Configure LSRB.
[LSRB] interface pos
[LSRB-Pos1/0/0] mpls
[LSRB-Pos1/0/0] quit
[LSRB] interface pos
[LSRB-Pos2/0/0] mpls
[LSRB-Pos2/0/0] quit
1/0/0
ldp
2/0/0
ldp
# Configure LSRC.
[LSRC] interface pos 1/0/0
[LSRC-Pos1/0/0] mpls ldp
Issue 02 (2011-09-10)
97
[LSRC-Pos1/0/0] quit
----End
Configuration Files
l
Issue 02 (2011-09-10)
98
link-protocol ppp
ip address 10.2.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.1.0 0.0.0.3
network 10.2.1.0 0.0.0.3
#
return
Networking Requirements
As shown in Figure 2-3, a remote LDP session is established between LSR A and LSR C.
Figure 2-3 Networking diagram of establishing a remote MPLS LDP session
Loopback1
Loopback1
Loopback1
1.1.1.9/32
2.2.2.9/32
3.3.3.9/32
POS1/0/0 POS1/0/0
POS2/0/0 POS1/0/0
10.1.1.1/30 10.1.1.2/30
10.2.1.1/30 10.2.1.2/30
LSRA
Issue 02 (2011-09-10)
LSRB
LSRC
99
Configuration Roadmap
The configuration roadmap is as follows:
1.
Enable global MPLS capabilities and MPLS LDP capabilities on each LSR.
2.
Specify the name and IP address of the remote peer at LSRs on both ends of a remote LDP
session.
Data Preparation
To complete the configuration, you need the following data:
l
IP address of each interface such as Figure 2-3, OSPF process ID, and OSPF area ID
Procedure
Step 1 Configure the IP address of each interface.
As shown in Figure 2-3, configure the IP address and mask of each interface, including the
loopback interface. In addition, use OSPF to notify interfaces of the connected segments and
the routes to the host that is specified by the LSR ID. The detailed configurations are not
mentioned here.
Step 2 Configure the global MPLS function and MPLS LDP function on each LSR.
# Configure LSRA.
<LSRA> system-view
[LSRA] mpls lsr-id 1.1.1.9
[LSRA] mpls
[LSRA-mpls] quit
[LSRA] mpls ldp
[LSRA-mpls-ldp] quit
# Configure LSR B.
<LSRB> system-view
[LSRB] mpls lsr-id 2.2.2.9
[LSRB] mpls
[LSRB-mpls] quit
[LSRB] mpls ldp
[LSRB-mpls-ldp] quit
# Configure LSR C.
<LSRC> system-view
[LSRC] mpls lsr-id 3.3.3.9
[LSRC] mpls
[LSRC-mpls] quit
[LSRC] mpls ldp
[LSRC-mpls-ldp] quit
Step 3 Specify the name and IP address of the remote peer on LSRs of both ends of a remote LDP
session.
# Configure LSR A.
[LSRA] mpls ldp remote-peer LSRC
[LSRA-mpls-ldp-remote-lsrc] remote-ip 3.3.3.9
[LSRA-mpls-ldp-remote-lsrc] quit
Issue 02 (2011-09-10)
100
# Configure LSR C.
[LSRC] mpls ldp remote-peer LSRA
[LSRC-mpls-ldp-remote-lsra] remote-ip 1.1.1.9
[LSRC-mpls-ldp-remote-lsra] quit
Run the display mpls ldp remote-peer command on LSRs at both ends of the remote LDP
session, and you can view information about the remote peers of the LSRs.
Take the display on LSR A as an example.
<LSRA> display mpls ldp remote-peer
LDP Remote Entity Information
-----------------------------------------------------------------------------Remote Peer Name : LSRC
Remote Peer IP
: 3.3.3.9
LDP ID
: 1.1.1.9:0
Transport Address : 1.1.1.9
Entity Status : Active
Configured Keepalive Hold Timer : 45 Sec
Configured Keepalive Send Timer : --Configured Hello Hold Timer
: 45 Sec
Negotiated Hello Hold Timer
: 45 Sec
Configured Hello Send Timer
: --Configured Delay Timer
: 0 Sec
Hello Packet sent/received
: 10/7
Remote Peer Deletion Status
: No
Auto-config
: -------------------------------------------------------------------------------TOTAL: 1 Peer(s) Found.
----End
Configuration Files
l
Issue 02 (2011-09-10)
101
link-protocol ppp
ip address 10.1.1.1 255.255.255.252
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 10.1.1.0 0.0.0.3
#
return
Issue 02 (2011-09-10)
102
Networking Requirements
Establish an LDP LSP from LSRA to LSRC on the network as shown in Figure 2-4.
Figure 2-4 Networking diagram of configuring the LDP LSP
Loopback1
Loopback1
Loopback1
1.1.1.9/32
2.2.2.9/32
3.3.3.9/32
POS1/0/0 POS1/0/0
POS2/0/0 POS1/0/0
10.1.1.1/30 10.1.1.2/30
10.2.1.1/30 10.2.1.2/30
LSRA
LSRB
LSRC
Configuration Roadmap
The configuration roadmap is as follows:
1.
2.
Data Preparation
To complete the configuration, you need the following data:
l
Procedure
Step 1 Configure the LDP LSP.
After the configuration in Example for Configuring LDP Sessions, all the LSRs triggers the
establishment of LDP LSPs according to the host route that is the default LDP LSP trigger policy.
Run the display mpls ldp lsp command on the LSRs, and you can view that all the host routes
trigger the establishment of LDP LSPs.
Take the display on LSRA as an example.
LDP LSP Information
------------------------------------------------------------------------------DestAddress/Mask
In/OutLabel
UpstreamPeer
NextHop
OutInterface
------------------------------------------------------------------------------1.1.1.9/32
3/NULL
2.2.2.9
127.0.0.1
InLoop0
*1.1.1.9/32
Liberal
2.2.2.9/32
NULL/3
10.1.1.2
Pos1/0/0
2.2.2.9/32
1024/3
2.2.2.9
10.1.1.2
Pos1/0/0
Issue 02 (2011-09-10)
103
3.3.3.9/32
NULL/1025
10.1.1.2
Pos1/0/0
3.3.3.9/32
1025/1025
2.2.2.9
10.1.1.2
Pos1/0/0
------------------------------------------------------------------------------TOTAL: 5 Normal LSP(s) Found.
TOTAL: 1 Liberal LSP(s) Found.
TOTAL: 0 Frr LSP(s) Found.
A '*' before an LSP means the LSP is not established
A '*' before a Label means the USCB or DSCB is stale
A '*' before a UpstreamPeer means the session is in GR state
A '*' before a NextHop means the LSP is FRR LSP
NOTE
Usually, the default trigger policy is used. That is, the establishment of an LDP LSP is triggered by a host
route. You can perform the following procedures to modify the LDP LSP trigger policy according to your
demands.
# Configure LSRB.
[LSRB] mpls
[LSRB-mpls] lsp-trigger all
[LSRB-mpls] quit
# Configure LSRC.
[LSRC] mpls
[LSRC-mpls] lsp-trigger all
[LSRC-mpls] quit
Issue 02 (2011-09-10)
104
----End
Configuration Files
l
Issue 02 (2011-09-10)
105
Networking Requirements
As shown in Figure 2-5, LSR A and LSR D are at the edge of a network. To set up a PW, a
remote LDP session must be set up between LSR A and LSR D to set up a public network tunnel.
As the network is of large scale, to save the network resources, you need to configure LDP to
automatically trigger a request to a downstream node for a label mapping message associated
with a remote LDP peer in DoD mode. In this manner, you can reduce unnecessary IP and MPLS
entries.
Figure 2-5 Networking diagram of configuring LDP to automatically trigger the request in DoD
mode
Loopback0
1.1.1.1/32
POS1/0/0
10.1.1.1/24
LSRA
Issue 02 (2011-09-10)
Loopback0
2.2.2.2/32
POS1/0/1
10.1.2.1/24
POS1/0/0
10.1.1.2/24
LSRB
Loopback0
4.4.4.4/32
Loopback0
3.3.3.3/32
POS1/0/0
10.1.2.2/24
POS1/0/1
10.1.3.1/24
LSRC
POS1/0/0
10.1.3.2/24
LSRD
106
Configuration Roadmap
The configuration roadmap is as follows:
1.
Assign an IP address to each interface of each node and configure the loopback address
that is used as the LSR ID.
2.
Configure basic IS-IS functions on each backbone network device and a static route to the
neighbor of each edge device.
3.
Enable global and interface-based MPLS and MPLS LDP on each node.
4.
5.
6.
Configure a remote LDP session and enable the function of automatically triggering a
request to a downstream node for a label mapping message associated with a remote LDP
peer in DoD mode.
Data Preparation
To complete the configuration, you need the following data:
l
Procedure
Step 1 Assign an IP address to each interface of each node and configure the loopback address that is
used as the LSR ID.
As shown in Figure 2-5, configure an IP address and mask for each interface including the
loopback interface. The configuration details are not mentioned here.
Step 2 Configure basic IS-IS functions on each backbone network device and a static route to the
neighbor of each edge device.
# Configure basic IS-IS function on LSR B.
<LSRB> system-view
[LSRB] isis 1
[LSRB-isis-1] network-entity 10.0000.0000.0001.00
[LSRB-isis-1] quit
[LSRB] interface pos 1/0/1
[LSRB-Pos1/0/1] isis enable 1
[LSRB-Pos1/0/1] quit
[LSRB] interface loopback 0
[LSRB-LoopBack0] isis enable 1
[LSRB-LoopBack0] quit
Issue 02 (2011-09-10)
107
# Configure a default route with the next-hop address being 10.1.1.2 on LSR A.
<LSRA> system-view
[LSRA] ip route-static 0.0.0.0 0.0.0.0 10.1.1.2
# Configure a default route with the next-hop address being 10.1.3.1 on LSR D.
<LSRB> system-view
[LSRB] ip route-static 0.0.0.0 0.0.0.0 10.1.3.1
Proto
Pre
Cost
Static
Direct
Direct
Direct
Direct
Direct
Direct
60
0
0
0
0
0
0
0
0
0
0
0
0
0
Flags NextHop
RD
D
D
D
D
D
D
10.1.1.2
127.0.0.1
10.1.1.1
127.0.0.1
10.1.1.2
127.0.0.1
127.0.0.1
Interface
Pos1/0/0
InLoopBack0
Pos1/0/0
InLoopBack0
Pos1/0/0
InLoopBack0
InLoopBack0
You can view that the configured default route exists on LSR A.
# Run the display ip routing-table command on LSR B to view routing information.
[LSRB] display ip routing-table
Route Flags: R - relay, D - download to fib
-----------------------------------------------------------------------------Routing Tables: Public
Destinations : 12
Routes : 12
Destination/Mask
1.1.1.1/24
2.2.2.2/32
3.3.3.3/32
4.4.4.4/32
10.1.1.0/24
10.1.1.1/32
10.1.1.2/32
10.1.2.0/24
10.1.2.1/32
10.1.2.2/32
127.0.0.0/8
127.0.0.1/32
Proto
Pre
Cost
Static
Direct
ISIS-L1
ISIS-L1
Direct
Direct
Direct
Direct
Direct
Direct
Direct
Direct
60
0
15
15
0
0
0
0
0
0
0
0
0
0
10
74
0
0
0
0
0
0
0
0
Flags NextHop
RD
D
D
D
D
D
D
D
D
D
D
D
10.1.1.1
127.0.0.1
10.1.2.2
10.1.2.2
10.1.1.2
10.1.1.1
127.0.0.1
10.1.2.1
127.0.0.1
10.1.2.2
127.0.0.1
127.0.0.1
Interface
Pos1/0/0
InLoopBack0
Pos1/0/1
Pos1/0/1
Pos1/0/0
Pos1/0/0
InLoopBack0
Pos1/0/1
InLoopBack0
Pos1/0/1
InLoopBack0
InLoopBack0
You can view that the configured default route to LSR A exists on LSR B.
Step 3 Enable global and interface-based MPLS and MPLS LDP on each node.
# Configure LSR A.
<LSRA> system-view
Issue 02 (2011-09-10)
108
The configurations on LSR B, LSR C, and LSR D are the same as the those of LSR A, and the
configuration details are not mentioned here.
Step 4 Configure the DoD label distribution mode.
# Configure LSR A.
<LSRA> system-view
[LSRA] interface pos 1/0/0
[LSRA-Pos1/0/0] mpls ldp advertisement dod
[LSRA-Pos1/0/0] quit
# Configure LSR B.
<LSRB> system-view
[LSRB] interface pos 1/0/0
[LSRB-Pos1/0/0] mpls ldp advertisement dod
[LSRB-Pos1/0/0] quit
# Configure LSR C.
<LSRC> system-view
[LSRC] interface pos 1/0/1
[LSRC-Pos1/0/1] mpls ldp advertisement dod
[LSRC-Pos1/0/1] quit
# Configure LSR D.
<LSRD> system-view
[LSRD] interface pos 1/0/0
[LSRD-Pos1/0/0] mpls ldp advertisement dod
[LSRD-Pos1/0/0] quit
# Run the longest-match command on LSR D to enable LDP to set up an LSP by searching for
a route according to the longest matching rule.
<LSRD> system-view
[LSRD] mpls ldp
[LSRD-mpls-ldp] longest-match
[LSRD-mpls-ldp] quit
Step 6 Configure a remote LDP session and enable the function of automatically triggering a request
to a downstream node for a label mapping message associated with a remote LDP peer in DoD
mode.
# Configure LSR A.
<LSRA> system-view
Issue 02 (2011-09-10)
109
lsrd
remote-ip 4.4.4.4
remote-ip auto-dod-request
quit
# Configure LSR D.
<LSRD> system-view
[LSRD] mpls ldp remote-peer
[LSRD-mpls-ldp-remote-lsra]
[LSRD-mpls-ldp-remote-lsra]
[LSRD-mpls-ldp-remote-lsra]
lsra
remote-ip 1.1.1.1
remote-ip auto-dod-request
quit
Static 60
RD
10.1.1.2
Pos1/0/0
You can view that only a default route exists and no exact route to 4.4.4.4 exists in the routing
table.
# Run the display mpls ldp lsp command on LSR A to view information about the established
LSPs.
<LSRA> display mpls ldp lsp
LDP LSP Information
------------------------------------------------------------------------------DestAddress/Mask
In/OutLabel
UpstreamPeer
NextHop
OutInterface
------------------------------------------------------------------------------4.4.4.4/32
NULL/1026
10.1.1.2
Pos1/0/0
------------------------------------------------------------------------------TOTAL: 1 Normal LSP(s) Found.
TOTAL: 0 Liberal LSP(s) Found.
TOTAL: 0 Frr LSP(s) Found.
A '*' before an LSP means the LSP is not established
A '*' before a Label means the USCB or DSCB is stale
A '*' before a UpstreamPeer means the session is in GR state
A '*' before a NextHop means the LSP is FRR LSP
You can view that an LSP destined for 4.4.4.4 is set up. It indicates that LSR A automatically
requests LSR B for a label mapping message associated with the destination 4.4.4.4 and thus
LSP can be set up.
# Run the display tunnel-info all command on LSR A to view information about the established
LSPs.
<LSRA> display tunnel-info all
* -> Allocated VC Token
Tunnel ID
Type
Destination
Token
---------------------------------------------------------------------0x1000
lsp
4.4.4.4
0
You can view that the LSP from LSR A to LSR D is set up.
----End
Issue 02 (2011-09-10)
110
Configuration Files
l
Issue 02 (2011-09-10)
111
#
return
Issue 02 (2011-09-10)
112
#
return
Networking Requirements
On the network shown in Figure 2-6, MPLS LDP is configured. LSR D is a DSLAM functioning
as a low-performance access device. By default, LSR D receives label mapping messages from
all peers and then uses the routing information in these messages to establish a large number of
LSPs. As a result, memory on LSR D is overused and LSR D is overburdened. In this case, an
inbound LDP policy needs to be configured on LSR D. The policy allows LSR D to receive label
mapping messages for routes to only LSR C and to establish LSPs to LSR C, thus saving
resources.
Figure 2-6 Networking diagram of an inbound LDP policy
Loopback1
1.1.1.9/32
POS1/0/0
10.1.1.1/24
Loopback1
2.2.2.9/32
POS1/0/0
POS1/0/1
10.1.1.2/24
10.1.2.1/24
Loopback1
3.3.3.9/32
POS1/0/0
10.1.2.2/24
LSRB
LSRA
POS1/0/2
10.1.3.2/24
LSRC
Loopback1
4.4.4.9/32
POS1/0/0
10.1.3.1/24
LSRD
Configuration Roadmap
The configuration roadmap is as follows:
1.
2.
Configure OSPF to advertise the route to each network segment of each interface and to
advertise the host route to each LSR ID.
3.
Enable MPLS and MPLS LDP in the system view and interface view.
4.
Data Preparation
To complete the configuration, you need the following data:
Issue 02 (2011-09-10)
113
IP address of each interface on each LSR as shown in Figure 2-6, OSPF process ID, and
OSPF area ID
Procedure
Step 1 Assign the IP address to and configure OSPF on each interface.
Configure the IP address and mask of each interface, including the loopback interface, as shown
in Figure 2-6, and configure OSPF to advertise the route to each network segment of each
interface and to advertise the host route to each LSR ID. The detailed configurations are not
described.
Step 2 Enable MPLS and MPLS LDP in the system view and interface view.
# Configure LSR A.
<LSRA> system-view
[LSRA] mpls lsr-id 1.1.1.9
[LSRA] mpls
[LSRA-mpls] quit
[LSRA] mpls ldp
[LSRA-mpls-ldp] quit
[LSRA] interface pos 1/0/0
[LSRA-Pos1/0/0] mpls
[LSRA-Pos1/0/0] mpls ldp
[LSRA-Pos1/0/0] quit
# Configure LSR B.
<LSRB> system-view
[LSRB] mpls lsr-id 2.2.2.9
[LSRB] mpls
[LSRB-mpls] quit
[LSRB] mpls ldp
[LSRB-mpls-ldp] quit
[LSRB] interface pos 1/0/0
[LSRB-Pos1/0/0] mpls
[LSRB-Pos1/0/0] mpls ldp
[LSRB-Pos1/0/0] quit
[LSRB] interface pos 1/0/1
[LSRB-Pos1/0/1] mpls
[LSRB-Pos1/0/1] mpls ldp
[LSRB-Pos1/0/1] quit
[LSRB] interface pos 1/0/2
[LSRB-Pos1/0/2] mpls
[LSRB-Pos1/0/2] mpls ldp
[LSRB-Pos1/0/2] quit
# Configure LSR C.
<LSRC> system-view
[LSRC] mpls lsr-id 3.3.3.9
[LSRC] mpls
[LSRC-mpls] quit
[LSRC] mpls ldp
[LSRC-mpls-ldp] quit
[LSRC] interface pos 1/0/0
[LSRC-Pos1/0/0] mpls
[LSRC-Pos1/0/0] mpls ldp
[LSRC-Pos1/0/0] quit
# Configure LSR D.
<LSRD> system-view
[LSRD] mpls lsr-id 4.4.4.9
Issue 02 (2011-09-10)
114
[LSRD] mpls
[LSRD-mpls] quit
[LSRD] mpls ldp
[LSRD-mpls-ldp] quit
[LSRD] interface pos 1/0/0
[LSRD-Pos1/0/0] mpls
[LSRD-Pos1/0/0] mpls ldp
[LSRD-Pos1/0/0] quit
# After the configuration is complete, run the display mpls lsp command on LSR D to view
information about the established LSPs.
<LSRD> display mpls lsp
------------------------------------------------------------------------------LSP Information: LDP LSP
------------------------------------------------------------------------------FEC
In/Out Label In/Out IF
Vrf Name
1.1.1.9/32
NULL/1024
-/Pos1/0/0
1.1.1.9/32
1024/1024
-/Pos1/0/0
2.2.2.9/32
NULL/3
-/Pos1/0/0
2.2.2.9/32
1025/3
-/Pos1/0/0
3.3.3.9/32
NULL/1025
-/Pos1/0/0
3.3.3.9/32
1026/1025
-/Pos1/0/0
The command output shows that LSPs to LSR A, LSR B, and LSR C have been established on
LSR D.
Step 3 Configure an inbound LDP policy.
# Configure an IP prefix list on LSR D to permit the route to only LSR C to pass the inbound
LDP policy.
<LSRD> system-view
[LSRD] ip ip-prefix prefix1 permit 3.3.3.9 32
# Configure an inbound policy on LSR D to allow LSR D to send label mapping messages
carrying the route to only LSR C.
<LSRD> system-view
[LSRD] mpls ldp
[LSRD-mpls-ldp] inbound peer 2.2.2.9 fec ip-prefix prefix1
[LSRB-mpls-ldp] quit
----End
Configuration Files
l
Issue 02 (2011-09-10)
115
#
mpls lsr-id 1.1.1.9
mpls
#
mpls ldp
#
interface Pos1/0/0
ip address 10.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface NULL0
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 10.1.1.0 0.0.0.255
#
user-interface con 0
user-interface vty 0 4
user-interface vty 16 20
#
return
Issue 02 (2011-09-10)
116
Issue 02 (2011-09-10)
117
Networking Requirements
On the network shown in Figure 2-7, MPLS LDP is configured. LSR D is a DSLAM functioning
as a low-performance access device. By default, LSR D receives label mapping messages from
all peers and then uses the routing information in these messages to establish a large number of
LSPs. As a result, memory on LSR D is overused and LSR D is overburdened. In this case, an
outbound LDP policy needs to be configured on LSR B to send LSRD label mapping messages
for routes to only LSR C and to establish LSPs to LSR C, thus saving resources.
Figure 2-7 Networking diagram of an outbound LDP policy
Loopback1
1.1.1.9/32
POS1/0/0
10.1.1.1/24
Loopback1
2.2.2.9/32
POS1/0/0
POS1/0/1
10.1.1.2/24
10.1.2.1/24
Loopback1
3.3.3.9/32
POS1/0/0
10.1.2.2/24
LSRB
LSRA
POS1/0/2
10.1.3.2/24
LSRC
Loopback1
4.4.4.9/32
POS1/0/0
10.1.3.1/24
LSRD
Configuration Roadmap
The configuration roadmap is as follows:
1.
2.
Configure OSPF to advertise the route to each network segment of each interface and to
advertise the host route to each LSR ID.
3.
Enable MPLS and MPLS LDP in the system view and interface view.
4.
Data Preparation
To complete the configuration, you need the following data:
l
IP address of each interface on each LSR as shown in Figure 2-7, OSPF process ID, and
OSPF area ID
Issue 02 (2011-09-10)
118
Procedure
Step 1 Assign the IP address to and configure OSPF on each interface.
Configure the IP address and mask of each interface, including the loopback interface, as shown
in Figure 2-7, and configure OSPF to advertise the route to each network segment of each
interface and to advertise the host route to each LSR ID. The detailed configurations are not
described.
Step 2 Enable MPLS and MPLS LDP in the system view and interface view.
# Configure LSR A.
<LSRA> system-view
[LSRA] mpls lsr-id 1.1.1.9
[LSRA] mpls
[LSRA-mpls] quit
[LSRA] mpls ldp
[LSRA-mpls-ldp] quit
[LSRA] interface pos 1/0/0
[LSRA-Pos1/0/0] mpls
[LSRA-Pos1/0/0] mpls ldp
[LSRA-Pos1/0/0] quit
# Configure LSR B.
<LSRB> system-view
[LSRB] mpls lsr-id 2.2.2.9
[LSRB] mpls
[LSRB-mpls] quit
[LSRB] mpls ldp
[LSRB-mpls-ldp] quit
[LSRB] interface pos 1/0/0
[LSRB-Pos1/0/0] mpls
[LSRB-Pos1/0/0] mpls ldp
[LSRB-Pos1/0/0] quit
[LSRB] interface pos 1/0/1
[LSRB-Pos1/0/1] mpls
[LSRB-Pos1/0/1] mpls ldp
[LSRB-Pos1/0/1] quit
[LSRB] interface pos 1/0/2
[LSRB-Pos1/0/2] mpls
[LSRB-Pos1/0/2] mpls ldp
[LSRB-Pos1/0/2] quit
# Configure LSR C.
<LSRC> system-view
[LSRC] mpls lsr-id 3.3.3.9
[LSRC] mpls
[LSRC-mpls] quit
[LSRC] mpls ldp
[LSRC-mpls-ldp] quit
[LSRC] interface pos 1/0/0
[LSRC-Pos1/0/0] mpls
[LSRC-Pos1/0/0] mpls ldp
[LSRC-Pos1/0/0] quit
# Configure LSR D.
<LSRD> system-view
[LSRD] mpls lsr-id 4.4.4.9
[LSRD] mpls
[LSRD-mpls] quit
[LSRD] mpls ldp
[LSRD-mpls-ldp] quit
[LSRD] interface pos 1/0/0
[LSRD-Pos1/0/0] mpls
Issue 02 (2011-09-10)
119
# After the configuration is complete, run the display mpls lsp command on LSR D to view
information about the established LSPs.
<LSRD> display mpls lsp
------------------------------------------------------------------------------LSP Information: LDP LSP
------------------------------------------------------------------------------FEC
In/Out Label In/Out IF
Vrf Name
1.1.1.9/32
NULL/1024
-/Pos1/0/0
1.1.1.9/32
1024/1024
-/Pos1/0/0
2.2.2.9/32
NULL/3
-/Pos1/0/0
2.2.2.9/32
1025/3
-/Pos1/0/0
3.3.3.9/32
NULL/1025
-/Pos1/0/0
3.3.3.9/32
1026/1025
-/Pos1/0/0
The command output shows that LSPs to LSR A, LSR B, and LSR C have been established on
LSR D.
Step 3 Configure an outbound LDP policy.
# Configure an IP prefix list on LSR B to permit the routes to LSR C to pass the outbound LDP
policy.
<LSRB> system-view
[LSRB] ip ip-prefix prefix1 permit 3.3.3.9 32
# Configure an outbound policy on LSR B to send LSR D label mapping messages carrying the
route to only LSR C.
<LSRB> system-view
[LSRB] mpls ldp
[LSRB-mpls-ldp] outbound peer 4.4.4.9 fec ip-prefix prefix1
[LSRB-mpls-ldp] quit
----End
Configuration Files
l
Issue 02 (2011-09-10)
120
interface Pos1/0/0
ip address 10.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface NULL0
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 10.1.1.0 0.0.0.255
#
user-interface con 0
user-interface vty 0 4
user-interface vty 16 20
#
return
Issue 02 (2011-09-10)
121
sysname LSRC
#
mpls lsr-id 3.3.3.9
mpls
#
mpls ldp
#
interface Pos1/0/0
ip address 10.1.2.2 255.255.255.0
mpls
mpls ldp
#
interface NULL0
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 10.1.2.0 0.0.0.255
#
user-interface con 0
user-interface vty 0 4
user-interface vty 16 20
#
return
Issue 02 (2011-09-10)
122
Networking Requirements
As shown in Figure 2-8, an LDP LSP is set up between respective LSRs. LSRB allows only the
FEC of 4.4.4.4/32 to pass.
Figure 2-8 Networking diagram of configuring transit LSPs through the prefix list
Loopback1
3.3.3.3/32
Loopback1
2.2.2.2/32
POS2/0/0
192.168.2.2/24
LSRB
POS1/0/0
192.168.1.2/24
POS1/0/0
192.168.2.1/24
LSRC
POS2/0/0
192.168.3.1/24
POS1/0/0
192.168.3.2/24
POS1/0/0
192.168.1.1/24
LSRD
LSRA
Loopback1
1.1.1.1/32
Loopback1
4.4.4.4/32
Configuration Roadmap
The configuration roadmap is as follows:
1.
Configure the IP address of the interfaces, set the loopback address as the LSR ID, and use
OSPF to advertise the network segments to which the interfaces are connected and the LSR
ID host route.
2.
Enable MPLS and MPLS LDP globally on the LSRs, and configure the policy of triggering
the establishment of LSPs.
3.
Configure the IP prefix list according to the requirement for LSP control.
4.
Filter the transit LSP routes by using the IP prefix list on the transit node.
5.
Data Preparation
To complete the configuration, you need the following data:
l
IP prefix list name, and the routes to be filtered on the transit node
Procedure
Step 1 Configure the IP address of the interfaces, and use OSPF to advertise the network segments that
the interfaces are connected to and the LSR ID host route.
Issue 02 (2011-09-10)
123
According to Figure 2-8, configure the IP address and the mask of the interfaces, including the
loopback interface, and run OSPF. The configuration details are not mentioned here.
Step 2 Configure the IP prefix list on the transit.
# Configure the IP prefix list on the transit node LSRB. Only 4.4.4.4/32 of LSRD can be used
to establish the transit LSP.
[LSRB] ip ip-prefix FilterOnTransit permit 4.4.4.4 32
Step 3 Configure basic MPLS functions and MPLS LDP functions globally and on the interfaces.
# Configure LSRA.
[LSRA] mpls lsr-id 1.1.1.1
[LSRA] mpls
[LSRA-mpls] lsp-trigger all
[LSRA-mpls] quit
[LSRA] mpls ldp
[LSRA-mpls-ldp] quit
[LSRA] interface pos 1/0/0
[LSRA-Pos1/0/0] mpls
[LSRA-Pos1/0/0] mpls ldp
[LSRA-Pos1/0/0] quit
# Configure LSRB.
[LSRB] mpls lsr-id 2.2.2.2
[LSRB] mpls
[LSRB-mpls] lsp-trigger all
[LSRB-mpls] quit
[LSRB] mpls ldp
[LSRB-mpls-ldp] propagate mapping for ip-prefix FilterOnTransit
[LSRB-mpls-ldp] quit
[LSRB] interface pos 1/0/0
[LSRB-Pos1/0/0] mpls
[LSRB-Pos1/0/0] mpls ldp
[LSRB-Pos1/0/0] quit
[LSRB] interface pos 2/0/0
[LSRB-Pos2/0/0] mpls
[LSRB-Pos2/0/0] mpls ldp
[LSRB-Pos2/0/0] quit
The configurations of LSRC and LSRD are similar to that of LSRA and LSRB, and the
configurations are not mentioned here.
Step 4 Verify the configuration.
Run the display mpls ldp lsp command, and you can view the establishment of LSPs.
# Display the LDP LSP on LSRA.
[LSRA] display mpls ldp lsp
LDP LSP Information
------------------------------------------------------------------------------DestAddress/Mask
In/OutLabel
UpstreamPeer
NextHop
OutInterface
------------------------------------------------------------------------------1.1.1.1/32
3/NULL
2.2.2.2
127.0.0.1
InLoop0
2.2.2.2/32
NULL/3
192.168.1.2
Pos1/0/0
2.2.2.2/32
1024/3
2.2.2.2
192.168.1.2
Pos1/0/0
4.4.4.4/32
NULL/1026
192.168.1.2
Pos1/0/0
4.4.4.4/32
1026/1026
2.2.2.2
192.168.1.2
Pos1/0/0
192.168.1.0/24
3/NULL
2.2.2.2
192.168.1.1
Pos1/0/0
*192.168.1.0/24
Liberal
192.168.2.0/24
NULL/3
192.168.1.2
Pos1/0/0
192.168.2.0/24
1027/3
2.2.2.2
192.168.1.2
Pos1/0/0
-------------------------------------------------------------------------------
Issue 02 (2011-09-10)
124
Issue 02 (2011-09-10)
125
*192.168.2.0/24
Liberal
192.168.3.0/24
3/NULL
2.2.2.2
192.168.3.1
Pos2/0/0
192.168.3.0/24
3/NULL
4.4.4.4
192.168.3.1
Pos2/0/0
*192.168.3.0/24
Liberal
------------------------------------------------------------------------------TOTAL: 15 Normal LSP(s) Found.
TOTAL: 7 Liberal LSP(s) Found.
TOTAL: 0 Frr LSP(s) Found.
A '*' before an LSP means the LSP is not established
A '*' before a Label means the USCB or DSCB is stale
A '*' before a UpstreamPeer means the session is in GR state
A '*' before a NextHop means the LSP is FRR LSP
The preceding information shows that after the configuration of the LSP control policy, each
LSR has only the LDP LSP destined for 4.4.4.4/32 passing through the transit LSRB, and other
LDP LSPs that do not take LSRB as the transit node.
----End
Configuration Files
l
Issue 02 (2011-09-10)
126
Issue 02 (2011-09-10)
127
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
ospf 1
area 0.0.0.0
network 192.168.2.0 0.0.0.255
network 192.168.3.0 0.0.0.255
network 3.3.3.3 0.0.0.0
#
return
Networking Requirements
As shown in Figure 2-9, there are two IGP areas, Area 10 and Area 20. It is required to establish
the inter-area LSPs from LSRA to LSRB and from LSRA to LSRC. It is required to configure
inter-area LSP on LSRA so that LSRA can search for routes according to the longest match rule
to establish LSPs.
Issue 02 (2011-09-10)
128
Figure 2-9 Networking diagram of configuring LDP Extension for Inter-Area LSP
Loopback0
1.3.0.1/32
Loopback0
1.1.0.1/32
POS1/0/0
10.1.1.1/24
LSRA
IS-IS
Area20
0/1
Loopback0 S1/ /24
/0 LSRB
1
O
1/0 /24
1.2.0.1/32 P .1.1.
S
2
20
PO 1.1.
.
IS-IS
20
PO
Area10
20 S1
.1. /0/
POS1/0/0
2.1 2
10.1.1.2/24 LSRD
/24
Loopback0
1.3.0.2/32
PO
20 S1
.1. /0/
2.2 0
/24
LSRC
Configuration Roadmap
The configuration roadmap is as follows:
1.
Assign IP addresses to interfaces on each node and configure the loopback addresses that
are used as LSR IDs.
2.
Enable IS-IS.
3.
4.
Enable global and interface-based MPLS and MPLS LDP on each node.
5.
Data Preparation
To complete the configuration, you need the following data:
l
IS-IS area ID of each nodes and levels of each nodes and interfaces
Procedure
Step 1 Assign IP addresses to interfaces on each node and configure the loopback addresses that are
used as LSR IDs.
As described in Figure 2-9, configure an IP address and a mask for each interface, including a
loopback interface. The configuration details are not mentioned here.
Issue 02 (2011-09-10)
129
# Configure LSRB.
<LSRB> system-view
[LSRB] isis 1
[LSRB-isis-1] is-level level-1
[LSRB-isis-1] network-entity 10.0010.0300.0001.00
[LSRB-isis-1] quit
[LSRB] interface pos 1/0/0
[LSRB-Pos1/0/0] isis enable 1
[LSRB-Pos1/0/0] quit
[LSRB] interface loopback 0
[LSRB-LoopBack0] isis enable 1
[LSRB-LoopBack0] quit
# Configure LSRC.
<LSRC> system-view
[LSRC] isis 1
[LSRC-isis-1] is-level level-1
[LSRC-isis-1] network-entity 10.0010.0300.0002.00
[LSRC-isis-1] quit
[LSRC] interface pos 1/0/0
[LSRC-Pos1/0/0] isis enable 1
[LSRC-Pos1/0/0] quit
[LSRC] interface loopback 0
[LSRC-LoopBack0] isis enable 1
[LSRC-LoopBack0] quit
# On LSRA, run the display ip routing-table command. You can view route information.
[LSRA] display ip routing-table
Issue 02 (2011-09-10)
130
Proto
Pre
Cost
Direct
ISIS-L1
ISIS-L1
ISIS-L1
Direct
Direct
Direct
ISIS-L1
ISIS-L1
Direct
Direct
0
15
15
15
0
0
0
15
15
0
0
0
10
20
20
0
0
0
20
20
0
0
Flags NextHop
D
D
D
D
D
D
D
D
D
D
D
127.0.0.1
10.1.1.2
10.1.1.2
10.1.1.2
10.1.1.1
127.0.0.1
10.1.1.2
10.1.1.2
10.1.1.2
127.0.0.1
127.0.0.1
Interface
InLoopBack0
Pos1/0/0
Pos1/0/0
Pos1/0/0
Pos1/0/0
InLoopBack0
Pos10/0/0
Pos1/0/0
Pos1/0/0
InLoopBack0
InLoopBack0
# On LSRA, run the display ip routing-table command. You can view route information.
Route Flags: R - relay, D - download to fib
-----------------------------------------------------------------------------Routing Tables: Public
Destinations : 10
Routes : 10
Destination/Mask
1.1.0.1/32
1.2.0.1/32
1.3.0.0/24
10.1.1.0/24
10.1.1.1/32
10.1.1.2/32
20.1.1.0/24
20.1.2.0/24
127.0.0.0/8
127.0.0.1/32
Proto
Pre
Cost
Direct
ISIS-L1
ISIS-L1
Direct
Direct
Direct
ISIS-L1
ISIS-L1
Direct
Direct
0
15
15
0
0
0
15
15
0
0
0
10
20
0
0
0
20
20
0
0
Flags NextHop
D
D
D
D
D
D
D
D
D
D
127.0.0.1
10.1.1.2
10.1.1.2
10.1.1.1
127.0.0.1
10.1.1.2
10.1.1.2
10.1.1.2
127.0.0.1
127.0.0.1
Interface
InLoopBack0
Pos1/0/0
Pos1/0/0
Pos1/0/0
InLoopBack0
Pos1/0/0
Pos1/0/0
Pos1/0/0
InLoopBack0
InLoopBack0
The command output shows that the host routes to LSRB and LSRC have been aggregated.
Step 4 Configure global and interface-based MPLS and MPLS LDP on each node so that the network
can forward MPLS traffic, and view the setup of the LSP.
# Configure LSRA.
[LSRA] mpls lsr-id 1.1.0.1
[LSRA] mpls
[LSRA-mpls] quit
[LSRA] mpls ldp
[LSRA-mpls-ldp] quit
[LSRA] interface pos 1/0/0
[LSRA-Pos1/0/0] mpls
[LSRA-Pos1/0/0] mpls ldp
[LSRA-Pos1/0/0] quit
Issue 02 (2011-09-10)
131
1/0/0
ldp
1/0/1
ldp
1/0/2
ldp
# Configure LSRB.
[LSRB] mpls lsr-id 1.3.0.1
[LSRB] mpls
[LSRB-mpls] quit
[LSRB] mpls ldp
[LSRB-mpls-ldp] quit
[LSRB] interface pos 1/0/0
[LSRB-Pos1/0/0] mpls
[LSRB-Pos1/0/0] mpls ldp
[LSRB-Pos1/0/0] quit
# Configure LSRC.
[LSRC] mpls lsr-id 1.3.0.2
[LSRC] mpls
[LSRC-mpls] quit
[LSRC] mpls ldp
[LSRC-mpls-ldp] quit
[LSRC] interface pos 1/0/0
[LSRC-Pos1/0/0] mpls
[LSRC-Pos1/0/0] mpls ldp
[LSRC-Pos1/0/0] quit
# After the configuration is complete, run the display mpls lsp command on LSRA to view the
established LSP.
[LSRA] display mpls lsp
------------------------------------------------------------------------------LSP Information: LDP LSP
------------------------------------------------------------------------------FEC
In/Out Label In/Out IF
Vrf Name
1.2.0.1/32
NULL/3
-/Pos1/0/0
1.2.0.1/32
1024/3
-/Pos1/0/0
The preceding command output shows that by default, LDP does not establish the inter-area
LSPs from LSRA to LSRB and from LSRA to LSRC.
Step 5 Configure LDP Extension for Inter-Area LSP.
# Run the longest-match command on LSRA to configure LDP to search for a route according
to the longest match rule to establish an inter-area LDP LSP.
[LSRA] mpls ldp
[LSRA-mpls-ldp] longest-match
[LSRA-mpls-ldp] quit
Issue 02 (2011-09-10)
132
The preceding command output shows that LDP establishes the inter-area LSPs from LSRA to
LSRB and from LSRA to LSRC.
----End
Configuration Files
l
Issue 02 (2011-09-10)
133
Issue 02 (2011-09-10)
134
isis 1
is-level level-1
network-entity 10.0010.0300.0002.00
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 20.1.2.2 255.255.255.0
isis enable 1
mpls
mpls ldp
#
interface LoopBack0
ip address 1.3.0.2 255.255.255.255
isis enable 1
#
return
Networking Requirements
As shown in Figure 2-10, an LDP LSP is set up along the path of PE1 P1 PE2 and the path
of PE2 P2 PE1 works as an IP link. Static BFD sessions are required to detect the
connectivity of the LDP LSP.
Figure 2-10 Networking diagram of configuring static BFD for LDP LSP
Loopback1
2.2.2.9/32
0
Loopback1
/0/ 4
1.1.1.9/32 OS1 .1/2
P 1.1
.
10
P
PE1 10 OS
.1. 1/0/
2.1 1
/24
Issue 02 (2011-09-10)
0
/0/ 24
1
S 2/
PO 1.1.
.
10
P1
P
10 OS1
.1. /0
5.2 /1
/24
LDP LSP
P
10 OS1
.1. /0/
2.2 0
/24
P
Loopback1
10 OS1
.1. /0/ 4.4.4.9/32
5.1 0
/24
P2
/1
1/0 /24
S
PO 1.4.2
.
10
Loopback1
3.3.3.9/32
1
/0/ 24 PE2
1
S 1/
PO 1.4.
.
10
135
Configuration Roadmap
The configuration roadmap is as follows:
1.
The entire MPLS domain applies OSPF and the IP link is accessible to each LSR.
2.
3.
Configure PE1 with a BFD session that is bound to the LDP LSP.
4.
Configure PE2 with a BFD session that is bound to the IP link to notify PE1 of the detected
LDP LSP faults.
Data Preparations
To complete the configuration, you need the following data:
l
Procedure
Step 1 Configure the IP address and the OSPF protocol for each interface
Configure the IP address and mask of each interface as shown in Figure 2-10, including loopback
interfaces.
Configure OSPF on all LSRs to advertise the host route of the loopback interface. The detailed
configuration is omitted here.
After configuration, each LSR can ping through the other LSR ID. Run the display ip routingtable command, and you can view the route table on each LSR.
<PE1> display ip routing-table
Route Flags: R - relay, D - download to fib
-----------------------------------------------------------------------------Routing Tables: Public
Destinations : 14
Routes : 15
Destination/Mask
1.1.1.9/32
2.2.2.9/32
3.3.3.9/32
4.4.4.9/32
10.1.1.0/24
10.1.1.1/32
10.1.1.2/32
10.1.2.0/24
10.1.2.1/32
10.1.2.2/32
10.1.4.0/24
10.1.5.0/24
127.0.0.0/8
127.0.0.1/32
Proto
Pre
Cost
Direct
OSPF
OSPF
OSPF
OSPF
Direct
Direct
Direct
Direct
Direct
Direct
OSPF
OSPF
Direct
Direct
0
10
10
10
10
0
0
0
0
0
0
10
10
0
0
0
2
2
3
3
0
0
0
0
0
0
2
2
0
0
Flags NextHop
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
127.0.0.1
10.1.1.2
10.1.2.2
10.1.2.2
10.1.1.2
10.1.1.1
127.0.0.1
10.1.1.2
10.1.2.1
127.0.0.1
10.1.2.2
10.1.2.2
10.1.1.2
127.0.0.1
127.0.0.1
Interface
InLoopBack0
Pos1/0/0
Pos1/0/1
Pos1/0/1
Pos1/0/0
Pos1/0/0
InLoopBack0
Pos1/0/0
Pos1/0/1
InLoopBack0
Pos1/0/1
Pos1/0/1
Pos1/0/0
InLoopBack0
InLoopBack0
Issue 02 (2011-09-10)
136
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls] quit
[PE1]interface pos 1/0/0
[PE1-Pos1/0/0] mpls
[PE1-Pos1/0/0] mpls ldp
[PE1-Pos1/0/0] quit
# Configure P1.
<P1> system-view
[P1] mpls lsr-id 2.2.2.9
[P1] mpls
[P1-mpls] quit
[P1] mpls ldp
[P1-mpls] quit
[P1]interface pos 1/0/0
[P1-Pos1/0/0] mpls
[P1-Pos1/0/0] mpls ldp
[P1-Pos1/0/0] quit
[P1]interface pos 1/0/1
[P1-Pos1/0/1] mpls
[P1-Pos1/0/1] mpls ldp
[P1-Pos1/0/1] quit
# Configure PE2.
<PE2> system-view
[PE2] mpls lsr-id 4.4.4.9
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls] quit
[PE2]interface pos 1/0/0
[PE2-Pos1/0/0] mpls
[PE2-Pos1/0/0] mpls ldp
[PE2-Pos1/0/0] quit
# Run the display mpls ldp lsp command, and you can view that an LDP LSP destined for
4.4.4.9/32 is set up on PE1.
<PE1> display mpls ldp lsp
LDP LSP Information
------------------------------------------------------------------------------DestAddress/Mask
In/OutLabel
UpstreamPeer
NextHop
OutInterface
------------------------------------------------------------------------------1.1.1.9/32
3/NULL
2.2.2.9
127.0.0.1
InLoop0
*1.1.1.9/32
Liberal
2.2.2.9/32
NULL/3
10.1.1.2
Pos1/0/0
2.2.2.9/32
1024/3
2.2.2.9
10.1.1.2
Pos1/0/00
4.4.4.9/32
NULL/1025
10.1.1.2
Pos1/0/0
4.4.4.9/32
1025/1025
2.2.2.9
10.1.1.2
Pos1/0/0
------------------------------------------------------------------------------TOTAL: 5 Normal LSP(s) Found.
TOTAL: 1 Liberal LSP(s) Found.
TOTAL: 0 Frr LSP(s) Found.
A '*' before an LSP means the LSP is not established
A '*' before a Label means the USCB or DSCB is stale
A '*' before a UpstreamPeer means the session is in GR state
A '*' before a NextHop means the LSP is FRR LSP
Step 3 Enable global BFD functions on LSRs at both ends of the detected link.
# Configure PE1.
<PE1> system-view
[PE1] bfd
[PE1-bfd] quit
Issue 02 (2011-09-10)
137
# Configure PE2.
<PE2> system-view
[PE2] bfd
[PE2-bfd] quit
Step 4 On the ingress, set up a BFD session that is bound to the LDP LSP.
# Configure PE1.
<PE1> system-view
[PE1] bfd 1to4 bind ldp-lsp peer-ip 4.4.4.9 nexthop 10.1.1.2 interface pos 1/0/0
[PE1-bfd-lsp-session-1to4] discriminator local 1
[PE1-bfd-lsp-session-1to4] discriminator remote 2
[PE1-bfd-lsp-session-1to4] process-pst
[PE1-bfd-lsp-session-1to4] commit
[PE1-bfd-lsp-session-1to4] quit
Step 5 On the egress, create a BFD session that is bound to the IP link to notify the ingress of LDP LSP
faults.
# Configure PE2.
<PE2> system-view
[PE2] bfd 4to1 bind peer-ip 1.1.1.9
[PE2-bfd-session-4ot1] discriminator local 2
[PE2-bfd-session-4ot1] discriminator remote 1
[PE2-bfd-session-4ot1] commit
[PE2-bfd-session-4ot1] quit
Issue 02 (2011-09-10)
138
# After the configuration, run the display bfd session all verbose command on the egress, and
you can view that Up is displayed in the (MultiHop) State field and Peer IP Address is
displayed in the BFD Bind Type field.
<PE2> display bfd session all verbose
-------------------------------------------------------------------------------Session MIndex : 256
(Multi Hop) State : Up
Name : 4to1
-------------------------------------------------------------------------------Local Discriminator
: 2
Remote Discriminator
: 1
Session Detect Mode
: Asynchronous Mode Without Echo Function
BFD Bind Type
: Peer IP Address
Bind Session Type
: Static
Bind Peer IP Address
: 1.1.1.9
Bind Interface
: FSM Board Id
: 6
TOS-EXP
: 6
Min Tx Interval (ms)
: 10
Min Rx Interval (ms)
: 10
Actual Tx Interval (ms): 10
Actual Rx Interval (ms): 10
Local Detect Multi
: 3
Detect Interval (ms)
: 3000
Echo Passive
: Disable
Acl Number
: Proc Interface Status : Disable
Process PST
: Disable
WTR Interval (ms)
: Local Demand Mode
: Disable
Active Multi
: 3
Last Local Diagnostic : No Diagnostic
Bind Application
: No Application Bind
Session TX TmrID
: 75
Session Detect TmrID
: 76
Session Init TmrID
: Session WTR TmrID
: Session Echo Tx TmrID : PDT Index
: FSM-0 | RCV-0 | IF-0 | TOKEN-0
Session Description
: -------------------------------------------------------------------------------Total UP/DOWN Session Number : 1/0
----End
Configuration Files
l
Issue 02 (2011-09-10)
139
#
bfd 1to4 bind ldp-lsp peer-ip 4.4.4.9 nexthop 10.1.1.2 interface Pos1/0/0
discriminator local 1
discriminator remote 2
process-pst
commit
#
return
Configuration file of P1
#
sysname P1
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 10.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface Pos1/0/1
undo shutdown
link-protocol ppp
ip address 10.1.5.2 255.255.255.0
mpls
mpls ldp
Issue 02 (2011-09-10)
140
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.1.0 0.0.0.255
network 10.1.5.0 0.0.0.255
#
return
Configuration file of P2
#
sysname P2
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 10.1.2.2 255.255.255.0
#
interface Pos1/0/1
undo shutdown
link-protocol ppp
ip address 10.1.4.2 255.255.255.0
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 10.1.4.0 0.0.0.255
network 10.1.2.0 0.0.0.255
#
return
Networking Requirements
As shown in Figure 2-11, LSRA, LSRB, and LSRC locates at one MPLS domain. An LDP LSP
is established between LSRA and LSRC that requires dynamic BFD for LDP LSP. The time to
detect a failure is within 50 ms.
Figure 2-11 Networking diagram of configuring dynamic BFD for LDP LSP
Loopback1
1.1.1.9/32
POS1/0/0
192.168.1.1/24
LSRA
Issue 02 (2011-09-10)
Loopback1
2.2.2.9/32
Loopback1
3.3.3.9/32
POS2/0/0
192.168.2.1/24
POS1/0/0
192.168.1.2/24 LSRB
POS1/0/0
192.168.2.2/24 LSRC
141
Configuration Roadmap
The configuration roadmap is as follows:
1.
Enable basic MPLS function on each LSR and establish the LDP LSP links.
2.
3.
Data Preparations
Before configuring, you need the following data:
l
BFD parameters
Procedure
Step 1 Configure the IP address for each interface. The configuration details are not mentioned here.
Step 2 Configure OSPF. The configuration details are not mentioned here.
Step 3 Configure basic MPLS functions
# Configure LSRA.
<LSRA> system-view
[LSRA] mpls lsr-id 1.1.1.9
[LSRA] mpls
[LSRA-mpls] quit
[LSRA] mpls ldp
[LSRA-mpls-ldp] quit
[LSRA] interface pos 1/0/0
[LSRA-Pos1/0/0] mpls
[LSRA-Pos1/0/0] mpls ldp
[LSRA-Pos1/0/0] quit
# The configuration on LSRB and LSRC is the same as that on LSRA. The configuration details
are not mentioned here.
After the configuration, run the display mpls ldp lsp command on LSR A, and you can view
that an LDP LSP is set up between LSR A and LSR C.
Take the display on LSR A as an example.
<LSRA> display mpls ldp lsp
LDP LSP Information
------------------------------------------------------------------------------DestAddress/Mask
In/OutLabel
UpstreamPeer
NextHop
OutInterface
------------------------------------------------------------------------------1.1.1.9/32
3/NULL
2.2.2.9
127.0.0.1
InLoop0
*1.1.1.9/32
Liberal
2.2.2.9/32
NULL/3
192.168.1.2
Pos1/0/0
2.2.2.9/32
1024/3
2.2.2.9
192.168.1.2
Pos1/0/0
3.3.3.9/32
NULL/1025
192.168.1.2
Pos1/0/0
3.3.3.9/32
1025/1025
2.2.2.9
192.168.1.2
Pos1/0/0
------------------------------------------------------------------------------TOTAL: 5 Normal LSP(s) Found.
TOTAL: 1 Liberal LSP(s) Found.
TOTAL: 0 Frr LSP(s) Found.
A '*' before an LSP means the LSP is not established
A '*' before a Label means the USCB or DSCB is stale
Issue 02 (2011-09-10)
142
Step 4 Configure dynamic BFD for LDP LSP from LSRA to LSRC.
# Configure an FEC list on LSRA to ensure that the BFD for LDP LSP only from LSRA to
LSRC is triggered.
[LSRA] fec-list tortc
[LSRA-fec-list-tortc] fec-node 3.3.3.9
# Enable BFD on LSRA. Specify the FEC list that triggers a BFD session dynamically. Adjust
BFD parameters.
[LSRA] bfd
[LSRA-bfd] quit
[LSRA] mpls
[LSRA-mpls] mpls bfd-trigger fec-list tortc
[LSRA-mpls] mpls bfd enable
[LSRA-mpls] mpls bfd min-tx-interval 600 min-rx-interval 600 detect-multiplier 4
# Display the status of BFD session created dynamically on LSRC. The field of BFD bind type
is Peer IP Address. This indicates the BFD packets sent by LSRC are transported through IP
route.
<LSRC> display bfd session passive-dynamic verbose
----------------------------------------------------------Session MIndex : 257
(Multi Hop) State : Up
Name : dyn_8193
Issue 02 (2011-09-10)
143
----------------------------------------------------------Local Discriminator
: 8193
Remote Discriminator
: 8192
Session Detect Mode : Asynchronous Mode Without Echo Function
BFD Bind Type
: Peer Ip Address
Bind Session Type
: Entire_Dynamic
Bind Peer Ip Address
: 1.1.1.9
Bind Interface
: -FSM Board Id
: 1
TOS-EXP
: 6
Min Tx Interval (ms)
: 100
Min Rx Interval (ms)
: 100
Actual Tx Interval (ms): 600
Actual Rx Interval (ms): 100
Local Detect Multi
: 3
Detect Interval (ms)
: 400
Echo Passive
: Disabl Acl Number
: -Proc interface status : Disable
Process PST
: Disable
WTR Interval (ms)
: -Local Demand Mode
: Disable
Active Multi
: 4
Last Local Diagnostic : No Diagnostic
Bind Application
Session TX TmrID
: 75
Session Detect TmrID
: 76
Session Init TmrID
: -Session WTR TmrID
: -Session Echo Tx TmrID : -PDT Index
: FSM-0 | RCV-0 | IF-0 | TOKEN-0
Session Description
: -----------------------------------------------------------Total UP/DOWN Session Number : 1/0
----End
Configuration Files
l
Issue 02 (2011-09-10)
144
Issue 02 (2011-09-10)
145
Networking Requirements
As shown in Figure 2-12, two LSPs are required from LSRA to LSRC. One is the primary LSP
along the path LSRA -> LSRC and another is the bypass LSP along the path LSRA -> LSRB > LSRC. Manual LDP FRR is required on LSRA for local interface backup to reduce data loss.
Here, only LSRA must support Manual LDP FRR.
NOTE
In networking of Manual LDP FRR, the bypass LSP must be in liberal state. That is, on an LSR that is
enabled with FRR, run the display ip routing-table ip-address verbose command to view the route state
of the bypass LSP is "Inactive Adv".
Loopback1
2.2.2.9/32
LSRA
0
/0/ 30
1
S 1/
PO 1.1.
.
10
P
10 OS2
.3. /0
1.1 /0
/30
PO
10 S1
.3. /0/
1.2 0
/30
LSRB
POS2/0/0 POS2/0/0
10.2.1.1/30 10.2.1.2/30
Loopback1
1.1.1.9/32
/0
1/0 /30
S
2
PO 1.1.
.
0
1
LSRC
Primary LSP
Loopback1
3.3.3.9/32
Bypass LSP
Configuration Roadmap
The configuration roadmap is as follows:
1.
Configure the IP address of the interfaces, set the loopback address as the LSR ID, and use
OSPF to advertise the network segments that the interfaces are connected to and the LSR
ID host route.
2.
3.
4.
Specify the next hop address that is used by Manual LDP FRR for generating the backup
LSP on the protected interface.
Data Preparation
To complete the configuration, you need the following data:
Issue 02 (2011-09-10)
146
Procedure
Step 1 Configure the IP address for each interface.
Configure the IP address and mask for each interface, including each Loopback interface as
shown in Figure 2-12. The detailed configuration is not mentioned here.
Step 2 Configure OSPF to advertise the LSR ID host route and network segments that the interfaces
are connected to.
# Configure LSRA.
<LSRA> system-view
[LSRA] ospf 1
[LSRA-ospf-1] area 0
[LSRA-ospf-1-area-0.0.0.0]
[LSRA-ospf-1-area-0.0.0.0]
[LSRA-ospf-1-area-0.0.0.0]
[LSRA-ospf-1-area-0.0.0.0]
[LSRA-ospf-1] quit
# Configure LSRB.
<LSRB> system-view
[LSRB] ospf 1
[LSRB-ospf-1] area 0
[LSRB-ospf-1-area-0.0.0.0]
[LSRB-ospf-1-area-0.0.0.0]
[LSRB-ospf-1-area-0.0.0.0]
[LSRB-ospf-1-area-0.0.0.0]
[LSRB-ospf-1] quit
# Configure LSRC.
<LSRC> system-view
[LSRC] ospf 1
[LSRC-ospf-1] area 0
[LSRC-ospf-1-area-0.0.0.0]
[LSRC-ospf-1-area-0.0.0.0]
[LSRC-ospf-1-area-0.0.0.0]
[LSRC-ospf-1-area-0.0.0.0]
[LSRC-ospf-1] quit
After the configuration, run the display ip routing-table command on each LSR, and you can
view that the LSRs learn the routes from each other.
Take the display on LSRA as an example.
<LSRA> display ip routing-table
Route Flags: R - relay, D - download to fib
-----------------------------------------------------------------------------Routing Tables: Public
Destinations : 12
Routes : 13
Destination/Mask
Proto Pre Cost
Flags NextHop
Interface
1.1.1.9/32 Direct 0
0
D 127.0.0.1
InLoopBack0
2.2.2.9/32 OSPF
10
2
D 10.1.1.2
Pos1/0/0
3.3.3.9/32 OSPF
10
2
D 10.3.1.2
Pos2/0/0
10.1.1.0/30 Direct 0
0
D 10.1.1.1
Pos1/0/0
10.1.1.1/32 Direct 0
0
D 127.0.0.1
InLoopBack0
10.1.1.2/32 Direct 0
0
D 10.1.1.2
Pos1/0/0
10.2.1.0/30 OSPF
10
2
D 10.3.1.2
Pos2/0/0
Issue 02 (2011-09-10)
147
10.3.1.0/30
10.3.1.1/32
10.3.1.2/32
127.0.0.0/8
127.0.0.1/32
OSPF
Direct
Direct
Direct
Direct
Direct
10
0
0
0
0
0
2
0
0
0
0
0
D
D
D
D
D
D
10.1.1.2
10.3.1.1
127.0.0.1
10.3.1.2
127.0.0.1
127.0.0.1
Pos1/0/0
Pos2/0/0
InLoopBack0
Pos2/0/0
InLoopBack0
InLoopBack0
Step 3 Configure the MPLS and MPLS LDP functions on the nodes globally and on the interfaces to
forward the MPLS traffic over the network.
# Configure LSRA.
[LSRA] mpls lsr-id 1.1.1.9
[LSRA] mpls
[LSRA-mpls] quit
[LSRA] mpls ldp
[LSRA-mpls-ldp] quit
[LSRA] interface pos 1/0/0
[LSRA-Pos1/0/0] mpls
[LSRA-Pos1/0/0] mpls ldp
[LSRA-Pos1/0/0] quit
[LSRA] interface pos 2/0/0
[LSRA-Pos2/0/0] mpls
[LSRA-Pos2/0/0] mpls ldp
[LSRA-Pos2/0/0] quit
# Configure LSRB.
[LSRB] mpls lsr-id 2.2.2.9
[LSRB] mpls
[LSRB-mpls] quit
[LSRB] mpls ldp
[LSRB-mpls-ldp] quit
[LSRB] interface pos 1/0/0
[LSRB-Pos1/0/0] mpls
[LSRB-Pos1/0/0] mpls ldp
[LSRB-Pos1/0/0] quit
[LSRB] interface pos 2/0/0
[LSRB-Pos2/0/0] mpls
[LSRB-Pos2/0/0] mpls ldp
[LSRB-Pos2/0/0] quit
# Configure LSRC.
[LSRC] mpls lsr-id 3.3.3.9
[LSRC] mpls
[LSRC-mpls] quit
[LSRC] mpls ldp
[LSRC-mpls-ldp] quit
[LSRC] interface pos 1/0/0
[LSRC-Pos1/0/0] mpls
[LSRC-Pos1/0/0] mpls ldp
[LSRC-Pos1/0/0] quit
[LSRC] interface pos 2/0/0
[LSRC-Pos2/0/0] mpls
[LSRC-Pos2/0/0] mpls ldp
[LSRC-Pos2/0/0] quit
After the configuration, LDP sessions are established between neighboring LSRs. Run the
display mpls ldp session command on each LSR, and you can view that Status is displayed as
Operational.
Take the display on LSRA as an example.
<LSRA> display mpls ldp session
LDP Session(s) in Public Network
Codes: LAM(Label Advertisement Mode), SsnAge Unit(DDDD:HH:MM)
A '*' before a session means the session is being deleted.
------------------------------------------------------------------------------
Issue 02 (2011-09-10)
148
PeerID
Status
LAM SsnRole SsnAge
KASent/Rcv
-----------------------------------------------------------------------------2.2.2.9:0
Operational DU
Passive 0000:00:01 8/8
3.3.3.9:0
Operational DU
Passive 0000:00:01 6/6
-----------------------------------------------------------------------------TOTAL: 2 session(s) Found.
Step 4 Enable Manual LDP FRR on the POS 2/0/0 on LSRA, and specify the next hop address for
generating the backup LSP.
# Configure LSRA.
[LSRA] interface pos 2/0/0
[LSRA-Pos2/0/0] mpls ldp frr nexthop 10.1.1.2
[LSRA-Pos2/0/0] quit
----End
Configuration Files
l
Issue 02 (2011-09-10)
149
Issue 02 (2011-09-10)
150
Return
Networking Requirements
With the development of networks, new services that have stringent requirements for real-time
transmission are emerging, for example, Voice over IP (VoIP) and on-line video services. A
large number of services are based on VPN. Currently, VPN services are generally implemented
by using LDP tunnels. In case of data loss due to faults over the link, these services will be
seriously affected.
The Manual LDP FRR is a technique that ensures that when a fault occurs, service traffic on the
public network is forwarded along the backup LSP before routes are converged and a new
primary LSP is established. This mechanism ensures that the service interruption lasts for only
as long as it takes the fault to be detected and traffic to be switched to the backup LSP. Therefore,
packet loss lasts for less than 50 ms. But the time that is required for VPN services to be switched
to a new LSP after routes convergence is completed depends on the actual VPN implementation.
This means that the speed at which VPN services are switched to the new primary LSP must be
raised so as to ensure that VPN services are interrupted for less than 50 ms. This issue can be
solved by configuring LDP Auto FRR.
As shown in Figure 2-13, the primary and backup LSPs are set up between LSRA and LSRC.
The primary LSP is along the path from LSRA to LSRC, and the backup LSP is along the path
LSRA -> LSRB -> LSRC. When the primary LSP becomes faulty, traffic must be rapidly
switched to the backup LSP. After LDP Auto FRR is configured on LSRA, in case of a fault
over the link, a backup LSP is automatically set up to reduce traffic loss.
Figure 2-13 Networking diagram of configuring LDP Auto FRR
LSRA
Loopback0
1.1.1.9/32
Issue 02 (2011-09-10)
POS1/0/1
10.1.2.1/24
P
10 O S
.1 1/
.3 0/
.1 1
/2
LSRB
4
backup LSP
/2
/ 0 24
S1 .2/
PO .1.3
10
P
10 O S
.1 1/
.1 0/
.1 0
/2
4
P
10 O S
.1 1/
.1 0/
.2 0
/2
4
Loopback0
2.2.2.9/32
LSRD
POS1/0/0
10.1.4.1/24
POS1/0/0
POS1/0/1
10.1.4.2/24
10.1.2.2/24
Loopback0
Loopback0
3.3.3.9/32
4.4.4.9/32
primary LSP
LSRC
151
Configuration Roadmap
The configuration roadmap is as follows:
1.
Assign IP addresses to interfaces on each node and configure the loopback address that is
used as the LSR ID.
2.
Configure IS-IS to advertise the network segments connecting to interfaces on each node
and to advertise the routes of hosts with LSR IDs.
3.
Enable global and interface-based MPLS and MPLS LDP on each node.
4.
Enable IS-IS Auto FRR on the LSR from which the protected traffic is originated.
5.
Change the LSP triggering policy to trigger the setup of LSPs for all routes.
6.
Configure a policy for triggering the setup of backup LSPs on the LSR from which the
protected traffic is originated.
Data Preparation
To complete the configuration, you need the following data:
l
IP addresses of the interfaces on each node, as listed in Figure 2-13, IS-IS process IDs,
and the area where each nodes resides
Procedure
Step 1 Assign an IP address to each interface.
As described in Figure 2-13, configure an IP address and a mask for each interface, including
a loopback interface. The detailed configuration procedure is not mentioned here.
Step 2 Enable IS-IS to advertise the network segments connecting to interfaces on each node and to
advertise the routes of hosts with LSR IDs.
# Configure LSRA.
<LSRA> system-view
[LSRA] isis 1
[LSRA-isis-1] network-entity 10.0000.0000.0001.00
[LSRA-isis-1] quit
[LSRA] interface pos 1/0/0
[LSRA-Pos1/0/0] isis enable 1
[LSRA-Pos1/0/0] quit
[LSRA] interface pos 1/0/1
[LSRA-Pos1/0/1] isis enable 1
[LSRA-Pos1/0/1] quit
[LSRA] interface loopBack 0
[LSRA-LoopBack0] isis enable 1
[LSRA-LoopBack0] quit
# Configure LSRB.
<LSRB> system-view
[LSRB] isis 1
[LSRB-isis-1] network-entity 10.0000.0000.0002.00
[LSRB-isis-1] quit
[LSRB] interface pos 1/0/0
[LSRB-Pos1/0/0] isis enable 1
[LSRB-Pos1/0/0] quit
[LSRB] interface pos 1/0/1
[LSRB-Pos1/0/1] isis enable 1
[LSRB-Pos1/0/1] quit
Issue 02 (2011-09-10)
152
# Configure LSRC.
<LSRC> system-view
[LSRC] isis 1
[LSRC-isis-1] network-entity 10.0000.0000.0003.00
[LSRC-isis-1] quit
[LSRC] interface pos 1/0/0
[LSRC-Pos1/0/0] isis enable 1
[LSRC-Pos1/0/0] quit
[LSRC] interface pos 1/0/1
[LSRC-Pos1/0/1] isis enable 1
[LSRC-Pos1/0/1] quit
[LSRC] interface pos 1/0/2
[LSRC-Pos1/0/2] isis enable 1
[LSRC-Pos1/0/2] quit
[LSRC] interface loopBack 0
[LSRC-LoopBack0] isis enable 1
[LSRC-LoopBack0] quit
# Configure LSRD.
<LSRD> system-view
[LSRD] isis 1
[LSRD-isis-1] network-entity 10.0000.0000.0004.00
[LSRD-isis-1] quit
[LSRD] interface pos 1/0/0
[LSRD-Pos1/0/0] isis enable 1
[LSRD-Pos1/0/0] quit
[LSRD] interface loopBack 0
[LSRD-LoopBack0] isis enable 1
[LSRD-LoopBack0] quit
Step 3 Configure global and interface-based MPLS and MPLS LDP on each node. Enable the network
to forward MPLS traffic and view the setup of the LSPs.
# Configure LSRA.
[LSRA] mpls lsr-id 1.1.1.9
[LSRA] mpls
[LSRA-mpls] quit
[LSRA] mpls ldp
[LSRA-mpls-ldp] quit
[LSRA] interface pos 1/0/0
[LSRA-Pos1/0/0] mpls
[LSRA-Pos1/0/0] mpls ldp
[LSRA-Pos1/0/0] quit
[LSRA] interface pos 1/0/1
[LSRA-Pos1/0/1] mpls
[LSRA-Pos1/0/1] mpls ldp
[LSRA-Pos1/0/1] quit
# Configure LSRB.
[LSRB] mpls lsr-id 2.2.2.9
[LSRB] mpls
[LSRB-mpls] quit
[LSRB] mpls ldp
[LSRB-mpls-ldp] quit
[LSRB] interface pos 1/0/0
[LSRB-Pos1/0/0] mpls
[LSRB-Pos1/0/0] mpls ldp
[LSRB-Pos1/0/0] quit
[LSRB] interface pos 1/0/1
[LSRB-Pos1/0/1] mpls
[LSRB-Pos1/0/1] mpls ldp
[LSRB-Pos1/0/1] quit
Issue 02 (2011-09-10)
153
# Configure LSRC.
[LSRC] mpls lsr-id 3.3.3.9
[LSRC] mpls
[LSRC-mpls] quit
[LSRC] mpls ldp
[LSRC-mpls-ldp] quit
[LSRC] interface pos 1/0/0
[LSRC-Pos1/0/0] mpls
[LSRC-Pos1/0/0] mpls ldp
[LSRC-Pos1/0/0] quit
[LSRC] interface pos 1/0/1
[LSRC-Pos1/0/1] mpls
[LSRC-Pos1/0/1] mpls ldp
[LSRC-Pos1/0/1] quit
[LSRC] interface pos 1/0/2
[LSRC-Pos1/0/2] mpls
[LSRC-Pos1/0/2] mpls ldp
[LSRC-Pos1/0/2] quit
# Configure LSRD.
[LSRD] mpls lsr-id 4.4.4.9
[LSRD] mpls
[LSRD-mpls] quit
[LSRD] mpls ldp
[LSRD-mpls-ldp] quit
[LSRD] interface pos 1/0/0
[LSRD-Pos1/0/0] mpls
[LSRD-Pos1/0/0] mpls ldp
[LSRD-Pos1/0/0] quit
# After the configuration is complete, run the display mpls lsp command on LSRA to view the
established LSP.
[LSRA] display mpls lsp
------------------------------------------------------------------------------LSP Information: LDP LSP
------------------------------------------------------------------------------FEC
In/Out Label In/Out IF
Vrf Name
2.2.2.9/32
NULL/3
-/Pos1/0/0
2.2.2.9/32
1024/3
-/Pos1/0/0
3.3.3.9/32
NULL/3
-/Pos1/0/1
3.3.3.9/32
1025/3
-/Pos1/0/1
4.4.4.9/32
NULL/1026
-/Pos1/0/1
4.4.4.9/32
1026/1026
-/Pos1/0/1
The preceding command output shows that by default, the setup of LSPs is triggered by LDP
for the routes with 32-bit addresses.
Step 4 Enable IS-IS Auto FRR on LSRA. View the routing information and the setup of the LSPs.
# Enable IS-IS Auto FRR on LSRA.
[LSRA] isis
[LSRA-isis-1] frr
[LSRA-isis-1-frr] loop-free-alternate
[LSRA-isis-1-frr] quit
[LSRA-isis-1] quit
# Display information about the route between LSRA and the link connecting LSRC and LSRD.
[LSRA] display ip routing-table 10.1.4.0 verbose
Route Flags: R - relay, D - download to fib
-----------------------------------------------------------------------------Routing Table : Public
Summary Count : 1
Issue 02 (2011-09-10)
154
Destination: 10.1.4.0/24
Protocol: ISIS
Process ID:
Preference: 15
Cost:
NextHop: 10.1.2.2
Neighbour:
State: Active Adv
Age:
Tag: 0
Priority:
Label: NULL
QoSInfo:
IndirectID: 0x0
RelayNextHop: 0.0.0.0
Interface:
TunnelID: 0x0
Flags:
BkNextHop: 10.1.1.2
BkInterface:
BkLabel: NULL
SecTunnelID:
BkPETunnelID: 0x0
BkPESecTunnelID:
BkIndirectID: 0x0
1
20
0.0.0.0
00h05m38s
low
0x0
Pos1/0/1
D
Pos1/0/0
0x0
0x0
The preceding command output shows that a backup IS-IS route is generated after IS-IS Auto
FRR is enabled.
# Run the display mpls lsp command on LSRA to view the setup of the LSPs.
[LSRA] display mpls lsp
------------------------------------------------------------------------------LSP Information: LDP LSP
------------------------------------------------------------------------------FEC
In/Out Label In/Out IF
Vrf Name
2.2.2.9/32
NULL/3
-/Pos1/0/0
**LDP FRR**
/1025
/Pos1/0/1
2.2.2.9/32
1024/3
-/Pos1/0/0
**LDP FRR**
/1025
/Pos1/0/1
3.3.3.9/32
NULL/3
-/Pos1/0/1
**LDP FRR**
/1025
/Pos1/0/0
3.3.3.9/32
1025/3
-/Pos1/0/1
**LDP FRR**
/1025
/Pos1/0/0
4.4.4.9/32
NULL/1026
-/Pos1/0/1
**LDP FRR**
/1026
/Pos1/0/0
4.4.4.9/32
1026/1026
-/Pos1/0/1
**LDP FRR**
/1026
/Pos1/0/0
The preceding command output shows that by default, the setup of a backup LSP is triggered
by LDP for the routes with 32-bit addresses.
Step 5 Run the lsp-trigger command on LSRC to change the LSP triggering policy to trigger the setup
of LSPs for all routes. Then, view the setup of the LSPs.
# Run the lsp-trigger command on LSRC to change the LSP triggering policy to trigger the
setup of LSPs for all routes.
[LSRC] mpls
[LSRC-mpls] lsp-trigger all
[LSRC-mpls] quit
# Run the display mpls lsp command on LSRA to view information about the established LSPs.
[LSRA] display mpls lsp
------------------------------------------------------------------------------LSP Information: LDP LSP
------------------------------------------------------------------------------FEC
In/Out Label In/Out IF
Vrf Name
2.2.2.9/32
NULL/3
-/Pos1/0/0
**LDP FRR**
/1025
/Pos1/0/1
2.2.2.9/32
1024/3
-/Pos1/0/0
**LDP FRR**
/1025
/Pos1/0/1
3.3.3.9/32
NULL/3
-/Pos1/0/1
**LDP FRR**
/1025
/Pos1/0/0
3.3.3.9/32
1025/3
-/Pos1/0/1
Issue 02 (2011-09-10)
155
**LDP FRR**
4.4.4.9/32
**LDP FRR**
4.4.4.9/32
**LDP FRR**
10.1.3.0/24
10.1.4.0/24
/1025
NULL/1026
/1026
1026/1026
/1026
1027/3
1028/3
/Pos1/0/0
-/Pos1/0/1
/Pos1/0/0
-/Pos1/0/1
/Pos1/0/0
-/Pos1/0/1
-/Pos1/0/1
The preceding command output shows that the setup of LSPs is triggered by LDP for the routes
with 24-bit addresses.
Step 6 Configure a triggering policy to trigger the setup of backup LSPs for all backup routes.
# Run the auto-frr lsp-trigger command on LSRA to trigger the setup of backup LSPs for all
backup routes.
[LSRA] mpls ldp
[LSRA-mpls-ldp] auto-frr lsp-trigger all
[LSRA-mpls-ldp] quit
The preceding command output shows that backup LSP is set up between LSRA and the link
connecting LSRC and LSRD.
----End
Configuration Files
l
Issue 02 (2011-09-10)
156
authorization-scheme default
#
accounting-scheme default
#
domain default
#
#
isis 1
frr
loop-free-alternate level-1
loop-free-alternate level-2
network-entity 10.0000.0000.0001.00
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.1 255.255.255.0
isis enable 1
mpls
mpls ldp
#
interface Pos1/0/1
link-protocol ppp
undo shutdown
ip address 10.1.2.1 255.255.255.0
isis enable 1
mpls
mpls ldp
#
interface NULL0
#
interface LoopBack0
ip address 1.1.1.9 255.255.255.255
isis enable 1
#
oam-mgr
#
user-interface con 0
user-interface vty 0 4
user-interface vty 16 20
#
return
Issue 02 (2011-09-10)
157
mpls
mpls ldp
#
interface Pos1/0/1
link-protocol ppp
undo shutdown
ip address 10.1.3.1 255.255.255.0
isis enable 1
mpls
mpls ldp
#
interface NULL0
#
interface LoopBack0
ip address 2.2.2.9 255.255.255.255
isis enable 1
#
oam-mgr
#
user-interface con 0
user-interface vty 0 4
user-interface vty 16 20
#
return
Issue 02 (2011-09-10)
158
mpls ldp
#
interface NULL0
#
interface LoopBack0
ip address 3.3.3.9 255.255.255.255
isis enable 1
#
oam-mgr
#
user-interface con 0
user-interface vty 0 4
user-interface vty 16 20
#
return
159
Networking Requirements
As shown in Figure 2-14, two links are established between PE1 and PE2. The link PE1 -> P1
-> P2 -> PE2 is an active link and the link PE1 -> P1 -> P3 -> PE2 is a standby link.
Configure synchronization between LDP and IGP on interfaces of P1 and P2. P1 and P2 are the
crossing node of active and standby links and the LDP neighbor node of the active link
respectively. After the active link recovers from the fault, configuring synchronization can
shorten the time of traffic switch from the standby link to the active link and limit the time within
milliseconds.
Figure 2-14 Networking diagram of configuring synchronization between LDP and IGP
Loopback1
2.2.2.9/32
0
/0/ 30
1
S 2/
PO 1.1.
Loopback1
.
0
P2
1.1.1.9/32 1/0/ 010
3
/
S
1
PO 1.1.
.
10
PE1
P1
P
10 OS2
.3. /0
1.1 /0
/30 P
10 OS1
.3. /0
1.2 /0
/30
P
10 OS2
.2. /0/
1.1 0
Loopback1
/30 P
10 OS1 4.4.4.9/32
.2. /0/
1.2 0
/30
P3
0
/0/ 30
2
S .1/
PO .4.1
10
Loopback1
3.3.3.9/32
/0 PE2
/ 0 30
2
S .2/
PO .4.1
10
Primary link
Bypass link
Configuration Roadmap
The configuration roadmap is as follows:
1.
Establish LDP sessions between neighboring nodes and between P1 and PE2.
2.
Configure LDP and IGP synchronization on interfaces of P1 and P2. P1 and P2 are the
crossing node of active and standby links and the LDP neighboring node of the active link
respectively.
3.
Configure the values of hold-down, hold-max-cost, and delay for the timer on interfaces
of P1 and P2. P1 and P2 are the crossing node of active and standby links and the LDP
neighboring node of the active link respectively.
Data Preparation
To complete the configuration, you need the following data:
Issue 02 (2011-09-10)
160
Procedure
Step 1 Assign IP addresses for the interfaces of the nodes and the address of the loopback interface as
the LSR ID, and advertise routes by OSPF. The detailed configurations are not mentioned here.
The link PE1 -> P1 -> P2 -> PE2 is an active link and the link PE1 -> P1 -> P3 -> PE2 is a
standby link. The cost value of POS 2/0/0 on P1 is 1000.
After the configuration, run the display ip routing-table command on each node, and you can
view that they have learnt routes from each other. The out interface of P1 route is POS 1/0/0.
Take the display on P1 as an example.
<P1> display ip routing-table
Route Flags: R - relay, D - download to fib
-----------------------------------------------------------------------------Routing Tables: Public
Destinations : 14
Routes : 14
Destination/Mask
Proto Pre Cost
Flags NextHop
Interface
1.1.1.9/32 Direct 0
0
D 127.0.0.1
InLoopBack0
2.2.2.9/32 OSPF
10
2
D 10.1.1.2
Pos1/0/0
3.3.3.9/32 OSPF
10
4
D 10.1.1.2
Pos1/0/0
4.4.4.9/32 OSPF
10
3
D 10.1.1.2
Pos1/0/0
10.1.1.0/30 Direct 0
0
D 10.1.1.1
Pos1/0/0
10.1.1.1/32 Direct 0
0
D 127.0.0.1
InLoopBack0
10.1.1.2/32 Direct 0
0
D 10.1.1.2
Pos1/0/0
10.2.1.0/30 OSPF
10
2
D 10.1.1.2
Pos1/0/0
10.3.1.0/30 Direct 0
0
D 10.3.1.1
Pos2/0/0
10.3.1.1/32 Direct 0
0
D 127.0.0.1
InLoopBack0
10.3.1.2/32 Direct 0
0
D 10.3.1.2
Pos2/0/0
10.4.1.0/30 OSPF
10
3
D 10.1.1.2
Pos1/0/0
127.0.0.0/20 Direct 0
0
D 127.0.0.1
InLoopBack0
127.0.0.1/32 Direct 0
0
D 127.0.0.1
InLoopBack0
Step 2 Enable MPLS and MPLS LDP globally and on all the interfaces on the nodes.
# Configure P1.
<P1> system-view
[P1] mpls lsr-id 1.1.1.9
[P1] mpls
[P1-mpls] quit
[P1] mpls ldp
[P1-mpls-ldp] quit
[P1] interface pos 1/0/0
[P1-Pos1/0/0] mpls
[P1-Pos1/0/0] mpls ldp
[P1-Pos1/0/0] quit
[P1] interface pos 2/0/0
[P1-Pos2/0/0] mpls
[P1-Pos2/0/0] mpls ldp
[P1-Pos2/0/0] quit
# Configure P2.
<P2> system-view
[P2] mpls lsr-id 2.2.2.9
[P2] mpls
[P2-mpls] quit
[P2] mpls ldp
[P2-mpls-ldp] quit
[P2] interface pos 1/0/0
[P2-Pos1/0/0] mpls
Issue 02 (2011-09-10)
161
# Configure P3.
<P3> system-view
[P3] mpls lsr-id 3.3.3.9
[P3] mpls
[P3-mpls] quit
[P3] mpls ldp
[P3-mpls-ldp] quit
[P3] interface pos 1/0/0
[P3-Pos1/0/0] mpls
[P3-Pos1/0/0] mpls ldp
[P3-Pos1/0/0] quit
[P3] interface pos 2/0/0
[P3-Pos2/0/0] mpls
[P3-Pos2/0/0] mpls ldp
[P3-Pos2/0/0] quit
# Configure PE2.
<PE2> system-view
[PE2] mpls lsr-id 4.4.4.9
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
[PE2] interface pos 1/0/0
[PE2-Pos1/0/0] mpls
[PE2-Pos1/0/0] mpls ldp
[PE2-Pos1/0/0] quit
[PE2] interface pos 2/0/0
[PE2-Pos2/0/0] mpls
[PE2-Pos2/0/0] mpls ldp
[PE2-Pos2/0/0] quit
After the configuration, LDP sessions are set up between the adjacent nodes. Run the display
mpls ldp session command on each node, and you can view that the Status is Operational.
Take the display on P1 as an example.
<P1> display mpls ldp session
LDP Session(s) in Public Network
Codes: LAM(Label Advertisement Mode), SsnAge Unit(DDDD:HH:MM)
A '*' before a session means the session is being deleted.
-----------------------------------------------------------------------------PeerID
Status
LAM SsnRole SsnAge
KASent/Rcv
-----------------------------------------------------------------------------2.2.2.9:0
Operational DU
Passive 0000:00:56 227/227
3.3.3.9:0
Operational DU
Passive 0000:00:56 227/227
-----------------------------------------------------------------------------TOTAL: 2 session(s) Found.
Step 3 Enable synchronization between LDP and IGP on interfaces of P1 and P2. P1 and P2 are the
crossing node of active and standby links and the LDP neighbor node of the active link
respectively.
# Configure P1.
<P1> system-view
[P1] interface pos 1/0/0
[P1-Pos1/0/0] ospf ldp-sync
[P1-Pos1/0/0] quit
Issue 02 (2011-09-10)
162
# Configure P2.
<P2> system-view
[P2] interface pos 1/0/0
[P2-Pos1/0/0] ospf ldp-sync
[P2-Pos1/0/0] quit
Step 4 Set a hold-down value of the timer on interfaces of P1 and P2. P1 and P2 are the crossing node
of active and standby links and the LDP neighbor node of the active link respectively.
# Configure P1.
<P1> system-view
[P1] interface pos 1/0/0
[P1-Pos1/0/0] ospf timer ldp-sync hold-down 8
[P1-Pos1/0/0] quit
# Configure P2.
<P2> system-view
[P2] interface pos 1/0/0
[P2-Pos1/0/0] ospf timer ldp-sync hold-down 8
[P2-Pos1/0/0] quit
Step 5 Set a hold-max-cost value for the timer on interfaces of P1 and P2. P1 and P2 are the crossing
node of active and standby links and the LDP neighbor node of the active link respectively.
# Configure P1.
<P1> system-view
[P1] interface pos 1/0/0
[P1-Pos1/0/0] ospf timer ldp-sync hold-max-cost 9
[P1-Pos1/0/0] quit
# Configure P2.
<P2> system-view
[P2] interface pos 1/0/0
[P2-Pos1/0/0] ospf timer ldp-sync hold-max-cost 9
[P2-Pos1/0/0] quit
Step 6 Set a delay value of the timer on interfaces of P1 and P2. P1 and P2 are the crossing node of
active and standby links and the LDP neighbor node of the active link respectively.
# Configure P1.
<P1> system-view
[P1] interface pos 1/0/0
[P1-Pos1/0/0] mpls ldp timer igp-sync-delay 6
[P1-Pos1/0/0] quit
# Configure P2.
<P2> system-view
[P2] interface pos 1/0/0
[P2-Pos1/0/0] mpls ldp timer igp-sync-delay 6
[P2-Pos1/0/0] quit
----End
Issue 02 (2011-09-10)
163
Configuration Files
l
Configuration file of P1
#
sysname P1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls ldp
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.1 255.255.255.252
ospf ldp-sync
ospf timer ldp-sync hold-down 8
ospf timer ldp-sync hold-max-cost 9
mpls
mpls ldp
mpls ldp timer igp-sync-delay 6
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 10.3.1.1 255.255.255.252
ospf cost 1000
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 10.1.1.0 0.0.0.3
network 10.3.1.0 0.0.0.3
#
return
Configuration file of P2
#
sysname P2
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.2 255.255.255.252
ospf ldp-sync
ospf timer ldp-sync hold-down 8
ospf timer ldp-sync hold-max-cost 9
mpls
mpls ldp
mpls ldp timer igp-sync-delay 6
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 10.2.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
Issue 02 (2011-09-10)
164
Configuration file of P3
#
sysname P3
#
mpls lsr-id 3.3.3.9
mpls
#
mpls ldp
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.3.1.2 255.255.255.252
mpls
mpls ldp
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 10.4.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 10.3.1.0 0.0.0.3
network 10.4.1.0 0.0.0.3
#
return
Issue 02 (2011-09-10)
165
#
ospf 1
area 0.0.0.0
network 4.4.4.9 0.0.0.0
network 10.2.1.0 0.0.0.3
network 10.4.1.0 0.0.0.3
#
return
Networking Requirements
On an MPLS network with primary and backup LSPs, LSRs establish LSPs based on static
routes. When the LDP session of the primary link becomes faulty (the fault is not caused by a
link failure) or the primary link recovers, unsynchronization between LDP and static routes
causes MPLS traffic to be interrupted temporarily.
As shown in Figure 2-15, there are two static routes from LSRA to LSRD, which pass through
LSRB and LSRC respectively. LDP sessions are established based on the static routes. Link A
is the primary link, and Link B is the backup link. It is required that synchronization between
LDP and static routes be configured to ensure non-stop MPLS traffic forwarding when the LDP
session on Link A is disconnected or Link A recovers.
Figure 2-15 Networking diagram for configuring synchronization between LDP and static
routes
Loopback0
LSRB
PO
S2
Loopback0
/0/0
/0
/0
0
0
/
/
S1 OS1
PO
P
PO
LinkA
S1
/0/
0
PO
LinkB
S2/
0/0
/0
0
LSRA
/0/ S2/0 LSRD
2
S PO
PO
S1/
PO
0/0
Loopback0
LSRC
Loopback0
Device
Interface
IP Address
Device
Interface
IP Address
LSRA
POS 1/0/0
10.1.1.1/30
LSRC
POS 1/0/0
20.1.1.2/30
POS 2/0/0
20.1.1.1/30
POS 2/0/0
40.1.1.2/30
Loopback0
1.1.1.1/32
Loopback0
3.3.3.3/32
POS 1/0/0
10.1.1.2/30
POS 1/0/0
30.1.1.2/30
LSRB
Issue 02 (2011-09-10)
LSRD
166
POS 2/0/0
30.1.1.1/30
POS 2/0/0
40.1.1.2/30
Loopback0
2.2.2.2/32
Loopback0
4.4.4.4/32
Configuration Roadmap
The configuration roadmap is as follows:
1.
2.
Enable MPLS and MPLS LDP in the system view and interface view.
3.
Configure synchronization between LDP and static routes and verify the configuration.
Data Preparation
To complete the configuration, you need the following data:
l
Procedure
Step 1 Configure an IP address for each interface.
# Configure IP addresses for interfaces according to Figure 2-15. The configuration details are
not described here.
Step 2 Configure static routes on devices to ensure network connectivity.
# On LSRA, configure two static routes with different priorities to LSRD, and on LSRD,
configure two static routes with different priorities to LSRA.
# Configure LSRA.
[LSRA]
[LSRA]
[LSRA]
[LSRA]
[LSRA]
[LSRA]
ip
ip
ip
ip
ip
ip
route-static
route-static
route-static
route-static
route-static
route-static
2.2.2.2 32 pos1/0/0
3.3.3.3 32 pos2/0/0
30.1.1.1 30 pos1/0/0
40.1.1.1 30 pos2/0/0
4.4.4.4 32 pos1/0/0 preference 40
4.4.4.4 32 pos2/0/0 preference 60
# Configure LSRB.
[LSRB] ip route-static 1.1.1.1 32 pos1/0/0
[LSRB] ip route-static 4.4.4.4 32 pos2/0/0
# Configure LSRC.
[LSRC] ip route-static 1.1.1.1 32 pos1/0/0
[LSRC] ip route-static 4.4.4.4 32 pos2/0/0
# Configure LSRD.
[LSRD]
[LSRD]
[LSRD]
[LSRD]
[LSRD]
Issue 02 (2011-09-10)
ip
ip
ip
ip
ip
route-static
route-static
route-static
route-static
route-static
2.2.2.2 32 pos1/0/0
3.3.3.3 32 pos2/0/0
10.1.1.2 30 pos1/0/0
20.1.1.2 30 pos2/0/0
1.1.1.1 32 pos1/0/0 preference 40
167
# After the preceding configurations, run the display ip routing-table protocol static command
on each LSR. The command output shows the configured static routes. Take the display on
LSRA as an example.
[LSRA] display ip routing-table protocol static
Route Flags: R - relay, D - download to fib
-----------------------------------------------------------------------------Public routing table : Static
Destinations : 5
Routes : 6
Configured Routes : 6
Static routing table status : <Active>
Destinations : 5
Routes : 5
Destination/Mask
2.2.2.2/32
3.3.3.3/32
4.4.4.4/32
30.1.1.0/30
40.1.1.0/30
Proto
Pre
Cost
Static
Static
Static
Static
Static
60
60
40
60
60
0
0
0
0
0
Flags NextHop
D
D
D
D
D
10.1.1.1
20.1.1.1
10.1.1.1
10.1.1.1
20.1.1.1
Interface
Pos1/0/0
Pos2/0/0
Pos1/0/0
Pos1/0/0
Pos2/0/0
Proto
Pre
Cost
Static
60
Flags NextHop
20.1.1.1
Interface
Pos2/0/0
The configurations of LSRB, LSRC, and LSRD are similar to the configuration of LSRA, and
are not described here. For configuration details, see "Configuration Files."
# Run the display mpls ldp session command on each LSR. The command output shows that
the status of LDP sessions is Operational. This indicates that LDP sessions have been
established. Take the display on LSRA as an example.
[LSRA] display mpls ldp session
LDP Session(s) in Public Network
Codes: LAM(Label Advertisement Mode), SsnAge Unit(DDDD:HH:MM)
A '*' before a session means the session is being deleted.
-----------------------------------------------------------------------------PeerID
Status
LAM SsnRole SsnAge
KASent/Rcv
-----------------------------------------------------------------------------2.2.2.2:0
Operational DU
Passive 0000:00:00 1/1
3.3.3.3:0
Operational DU
Passive 0000:00:02 12/12
-----------------------------------------------------------------------------TOTAL: 2 session(s) Found.
Step 4 Configure synchronization between LDP and static routes on LSRA and LSRD.
Issue 02 (2011-09-10)
168
# Configure LSRA.
[LSRA] ip route-static 4.4.4.4 32 pos1/0/0 ldp-sync
[LSRA] interface pos1/0/0
[LSRA-Pos1/0/0] static-route timer ldp-sync hold-down 20
[LSRA-Pos1/0/0] quit
# Configure LSRD.
[LSRD] ip route-static 1.1.1.1 32 pos1/0/0 ldp-sync
[LSRD] interface pos1/0/0
[LSRD-Pos1/0/0] static-route timer ldp-sync hold-down 20
[LSRD-Pos1/0/0] quit
The preceding display shows that the status of synchronization between LDP and static routes
is Normal. This indicates that synchronization between LDP and static routes has been
configured.
l If the LDP session of the primary link (Link A) is disconnected, traffic is immediately
switched to the backup link (Link B) to synchronize LDP and static routes. This ensures nonstop traffic forwarding.
l After the primary link recovers, the static route with the next-hop address being 10.1.1.1 is
not preferred immediately. Instead, the static route becomes active only after the LDP session
of the primary link has been established and the Hold-down timer expires (the timeout period
of the timer is 20 seconds). This synchronizes static routes and LDP, thus ensuring non-stop
MPLS traffic forwarding.
----End
Configuration Files
l
Issue 02 (2011-09-10)
169
mpls
mpls ldp
#
interface loopback0
ip address 1.1.1.1 255.255.255.255
#
ip route-static 2.2.2.2 255.255.255.255 Pos1/0/0
ip route-static 3.3.3.3 255.255.255.255 Pos2/0/0
ip route-static 4.4.4.4 255.255.255.255 Pos1/0/0 preference 40 ldp-sync
ip route-static 4.4.4.4 255.255.255.255 Pos2/0/0 preference 60
ip route-static 30.1.1.0 255.255.255.252 Pos1/0/0
ip route-static 40.1.1.0 255.255.255.252 Pos2/0/0
#
return
Issue 02 (2011-09-10)
170
#
return
Networking Requirements
As shown in Figure 2-16, each node runs MPLS and MPLS LDP. It is required to enable GTSM
on LSR B.
Figure 2-16 Networking diagram for configuring LDP GTSM
Loopback1
Loopback1
Loopback1
1.1.1.9/32
2.2.2.9/32
3.3.3.9/32
POS1/0/0 POS1/0/0
POS2/0/0 POS1/0/0
10.1.1.1/30 10.1.1.2/30
10.2.1.1/30 10.2.1.2/30
LSRA
Issue 02 (2011-09-10)
LSRB
LSRC
171
Configuration Roadmap
The configuration roadmap is as follows:
l
Data Preparation
To complete the configuration, you need the following data:
l
Procedure
Step 1 Configure an IP address for each interface. The configuration details are not mentioned here.
Step 2 Configure OSPF to advertise the network segments connected to the interfaces of the LSRs and
host routes of LSR IDs. The configuration details are not mentioned here.
Step 3 Configure each device with MPLS and MPLS LDP functions on each interface. The
configuration details are not mentioned here.
After the preceding configurations, run the display mpls ldp session command on each node,
and you can view the setup of LDP sessions. Take LSR A as an example.
<LSRA> display mpls ldp session
LDP Session(s) in Public Network
Codes: LAM(Label Advertisement Mode), SsnAge Unit(DDDD:HH:MM)
A '*' before a session means the session is being deleted.
-----------------------------------------------------------------------------PeerID
Status
LAM SsnRole SsnAge
KASent/Rcv
-----------------------------------------------------------------------------2.2.2.9:0
Operational DU
Passive 0000:00:02 9/9
-----------------------------------------------------------------------------TOTAL: 1 session(s) Found.
# On LSR B, configure the range of valid TTL values carried in the LDP packets received from
LSR A to be from 252 to 255, and the range of valid TTL values carried in LDP packets received
from LSR C to be from 251 to 255.
<LSRB> system-view
[LSRB] mpls ldp
[LSRB-mpls-ldp] gtsm peer 1.1.1.9 valid-ttl-hops 4
[LSRB-mpls-ldp] gtsm peer 3.3.3.9 valid-ttl-hops 5
# On LSR C, configure the range of valid TTL values carried in LDP packets received from LSR
B to be from 250 to 255.
<LSRC> system-view
[LSRC] mpls ldp
[LSRC-mpls-ldp] gtsm peer 2.2.2.9 valid-ttl-hops 6
Issue 02 (2011-09-10)
172
Then, if the host PC simulates the LDP packets of LSR A to attack LSR B, LSR B discards the
packets directly because the TTL values carried in the LDP packets are not within the range of
252 to 255. In the GTSM statistics on LSR B, the number of discarded packets increases.
----End
Configuration Files
l
Issue 02 (2011-09-10)
173
Networking Requirements
As shown in Figure 2-17, LSRA, LSRB, and LSRC are LSRs with dual main control boards.
The three LSRs belong to the same OSPF area and are interconnected through OSPF. All of
them support the GR mechanism.
After establishing the LDP sessions between them, LSRA, LSRB, and LSRC start to establish
the LDP GR sessions. When the main control board of LSRB fails and is switched, the LDP GR
mechanism is used in synchronization with neighbor LSRs.
Figure 2-17 Networking diagram of configuring LDP GR
Loopback1
Loopback1
Loopback1
1.1.1.9/32
2.2.2.9/32
3.3.3.9/32
POS1/0/0 POS1/0/0
POS2/0/0 POS1/0/0
10.1.1.1/30 10.1.1.2/30
10.2.1.1/30 10.2.1.2/30
LSRA
Issue 02 (2011-09-10)
LSRB
LSRC
174
Configuration Roadmap
The configuration roadmap is as follows:
1.
Configure IP address of each interface on the LSRs and the Loopback address used as the
LSR ID, and configure OSPF to advertise the network segments that the interfaces are
connected to and the LSR ID host route.
2.
3.
4.
5.
6.
7.
Data Preparation
To complete the configuration, you need the following data:
l
OSPF GR interval
Procedure
Step 1 Configure the IP address for each interface. The configuration details are not mentioned here.
Step 2 Configure OSPF to advertise the network segments that the interfaces are connected to and the
LSR ID host route. The configuration details are not mentioned here.
Step 3 Configure the OSPF GR function.
# Configure LSRA.
<LSRA> system-view
[LSRA] ospf 1
[LSRA-ospf-1] opaque-capability enable
[LSRA-ospf-1] graceful-restart
[LSRA-ospf-1] quit
# Configure LSRB.
<LSRB> system-view
[LSRB] ospf 1
[LSRB-ospf-1] opaque-capability enable
[LSRB-ospf-1] graceful-restart
[LSRB-ospf-1] quit
# Configure LSRC.
<LSRC> system-view
[LSRC] ospf 1
[LSRC-ospf-1] opaque-capability enable
[LSRC-ospf-1] graceful-restart
[LSRC-ospf-1] quit
Issue 02 (2011-09-10)
175
Step 4 Configure the MPLS and MPLS LDP functions on each node globally.
# Configure LSRA.
[LSRA] mpls lsr-id 1.1.1.9
[LSRA] mpls
[LSRA-mpls] quit
[LSRA] mpls ldp
[LSRA-mpls-ldp] quit
# Configure LSRB.
[LSRB] mpls lsr-id 2.2.2.9
[LSRB] mpls
[LSRB-mpls] quit
[LSRB] mpls ldp
[LSRB-mpls-ldp] quit
# Configure LSRC.
[LSRC] mpls lsr-id 3.3.3.9
[LSRC] mpls
[LSRC-mpls] quit
[LSRC] mpls ldp
[LSRC-mpls-ldp] quit
Step 5 Configure the MPLS and MPLS LDP functions on each interface.
# Configure LSRA.
[LSRA] interface pos 1/0/0
[LSRA-Pos1/0/0] mpls
[LSRA-Pos1/0/0] mpls ldp
[LSRA-Pos1/0/0] quit
# Configure LSRB.
[LSRB] interface pos
[LSRB-Pos1/0/0] mpls
[LSRB-Pos1/0/0] mpls
[LSRB-Pos1/0/0] quit
[LSRB] interface pos
[LSRB-Pos2/0/0] mpls
[LSRB-Pos2/0/0] mpls
[LSRB-Pos2/0/0] quit
1/0/0
ldp
2/0/0
ldp
# Configure LSRC.
[LSRC] interface pos 1/0/0
[LSRC-Pos1/0/0] mpls
[LSRC-Pos1/0/0] mpls ldp
[LSRC-Pos1/0/0] quit
After the preceding configuration is complete, the local LDP sessions are established between
LSRA and LSRB, and between LSRB and LSRC.
Run the display mpls ldp session command on each LSR, and you can view the established
LDP session.
Take the display on LSRA as an example.
[LSRA] display mpls ldp session
LDP Session(s) in Public Network
Codes: LAM(Label Advertisement Mode), SsnAge Unit(DDDD:HH:MM)
A '*' before a session means the session is being deleted.
-----------------------------------------------------------------------------PeerID
Status
LAM SsnRole SsnAge
KASent/Rcv
-----------------------------------------------------------------------------2.2.2.9:0
Operational DU
Passive 0000:00:02 9/9
Issue 02 (2011-09-10)
176
# Configure LSRB.
[LSRB] mpls ldp
[LSRB-mpls-ldp] graceful-restart
Warning: All the related sessions will be deleted if the operation is performed
!Continue? (y/n)y
[LSRB-mpls-ldp] quit
# Configure LSRC.
[LSRC] mpls ldp
[LSRC-mpls-ldp] graceful-restart
Warning: All the related sessions will be deleted if the operation is performed
!Continue? (y/n)y
[LSRC-mpls-ldp] quit
reconnect 300
be deleted if the operation is performed
neighbor-liveness 600
be deleted if the operation is performed
recovery 300
be deleted if the operation is performed
Issue 02 (2011-09-10)
:
:
:
:
:
:
:
45 Sec
3 Sec
1/1 (Message Count)
Downstream Unsolicited
Available/Available
0000:00:00 (DDDD:HH:MM)
No
177
Capability:
Capability-Announcement
: Off
: NULL
2.2.2.9
------------------------------------------------------------------------------
Alternatively, run the display mpls ldp peer verbose command on the LSR, and you can view
that On is displayed in the Peer FT Flag field.
Take the display on LSRA as an example.
[LSRA] display mpls ldp peer verbose
LDP Peer Information in Public network
-----------------------------------------------------------------------------Peer LDP ID
: 2.2.2.9:0
Peer Max PDU Length : 4096
Peer Transport Address
: 2.2.2.9
Peer Loop Detection : Off
Peer Path Vector Limit
: ---Peer FT Flag
: On
Peer Keepalive Timer
: 45 Sec
Recovery Timer
: 300 Sec
Reconnect Timer
: 300 Sec
Peer Type
: Local
Peer Label Advertisement Mode : Downstream Unsolicited
Peer Discovery Source
: Pos1/0/0
Peer Deletion Status
: No
Capability-Announcement
: Off
------------------------------------------------------------------------------
----End
Configuration File
l
Issue 02 (2011-09-10)
178
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
graceful-restart
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.2 255.255.255.252
mpls
mpls ldp
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 10.2.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
opaque-capability enable
graceful-restart
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.1.0 0.0.0.3
network 10.2.1.0 0.0.0.3
#
return
Issue 02 (2011-09-10)
179
3 MPLS TE Configuration
MPLS TE Configuration
180
3 MPLS TE Configuration
181
3 MPLS TE Configuration
Issue 02 (2011-09-10)
182
3 MPLS TE Configuration
TE
Network resource insufficiency and load imbalance result in congestion on a network, affecting
the performance of a backbone network. TE prevents network congestion and optimizes the
network resources.
TE dynamically monitors traffic and load on network elements and adjusts parameters relevant
to traffic control, routing, and resource constraints in real time. This optimizes utilization of
network resources and prevents imbalance-triggered congestion.
MPLS TE
As a combination of MPLS and TE, MPLS TE load-balances traffic on a network by setting up
an LSP over a specified path to reserve resources for traffic that will not pass through congested
nodes.
An LSP with a higher priority preempts bandwidth resources of LSPs with lower priorities,
providing sufficient bandwidth for services on the LSP with a higher priority in the case of
bandwidth insufficiency.
If a link fault or a node fault occurs, MPLS TE uses path backup and fast reroute (FRR) to ensure
uninterrupted traffic.
Administrators use MPLS TE to create LSPs to eliminate network congestions and use special
offline utility to analyze traffic if the number of LSPs increases to a certain extent.
This section describes MPLS TE features that are supported by the NE80E/40E. For details about MPLS
TE features, see the section "MPLS TE" in the HUAWEI NetEngine80E/40E Router Feature Description
- MPLS.
183
3 MPLS TE Configuration
Static MPLS TE tunnels have the highest priority among tunnels and therefore their bandwidth
is not preemptive. In addition, static MPLS TE tunnels do not preempt bandwidth of other types
of CR-LSPs.
RSVP-TE Tunnel
RSVP-TE tunnels are set up by the RSVP-TE signaling protocol and change dynamically
according to the network topology.
RSVP-TE features supported by the NE80E/40E are as follows:
l
Path calculation
On the NE80E/40E, the path of a TE tunnel is calculated by using CSPF. If there are several
paths with the same metric, CSPF selects one of them based on the number of hops and the
user configured tie-breaking.
In addition to the reservable bandwidth and management group attributes, the following
attributes are configurable:
Tunnel bandwidth
Affinity attribute
Explicit path
Maximum hop limit
Shared Risk Link Group (SRLG)
Signaling mechanism
RSVP-TE reserves resources in either fixed filter (FF) or shared-explicit (SE) mode. The
following extended RSVP mechanisms are supported by the NE80E/40E to relieve network
burden and improve reliability:
Confirmation and retransmission for RSVP messages
Summary refreshing
Hello mechanism
In addition, RSVP authentication is supported by the NE80E/40E to improve network
security.
Traffic forwarding
VPN traffic is directed to TE tunnels by using configured policy-based routes. Non-VPN
traffic is directed to TE tunnels by using static routes, policy-based routes, IGP shortcut,
or forwarding adjacency.
Issue 02 (2011-09-10)
184
3 MPLS TE Configuration
Reliability
The NE80E/40E supports the following reliability features applied to MPLS TE tunnels:
l
FRR
FRR is a local protection mechanism in RSVP-TE. FRR protects traffic on CR-LSP links
and nodes if faults occur. FRR is classified into manual FRR and automatic FRR.
CR-LSP backup
CR-LSP backup protects traffic on an entire RSVP-TE CR-LSP from end to end. If the
primary CR-LSP fails, traffic will be switched to the backup CR-LSP. If the backup CRLSP also fails, a best-effort path will be generated so that traffic can be switched to the
best-effort path.
BFD
BFD detects a fault in a CR-LSP at millisecond level. BFD allows rapid detection,
requirements for which hardware detection does not satisfy.
RSVP GR
RSVP GR is a status recovery mechanism for RSVP-TE tunnels. If a switchover on the
control plane triggered by a fault or an operation, RSVP GR helps the system to properly
forwarding data on the forwarding plane and restore the RSVP-TE LSP on the control plane.
FRR is supported by the NE80E/40E during the GR process.
For configurations of an MPLS tunnel protection group, see the section "MPLS OAM."
NSR
If a software or hardware fault occurs on the control plane, NSR ensures the uninterrupted
forwarding and the uninterrupted connection of the control plane. In addition, the control
plane of a neighbor does not sense the fault.
DS-TE
DS-TE maps different service types of traffic (such as voice, video, or data traffic) to LSPs. The
path through which traffic passes is consistent with traffic engineering constraints of a specific
service type.
DS-TE supports either non-IETF or IETF mode on the NE80E/40E.
l
Issue 02 (2011-09-10)
The non-IETF (non-standard) mode supports combinations between two CTs (CT0 and
CT1) and eight priorities (0 to 7) and the Bandwidth Constraints models (RDM and MAM).
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
185
3 MPLS TE Configuration
Class-Type (CT) refers to the class mapped to a service. The priority refers to the LSP
preemption priority.
l
The IEFT (standard) mode supports combinations between eight CTs (CT0 to CT7) and
eight priorities (0 to 7). In addition, it supports the following Bandwidth Constraints
models: RDM, MAM, and extended-MAM.
A DS-TE tunnel supports TE FRR, hot standby, protection group, and CT traffic statistics.
Applicable Environment
The configuration of a static CR-LSP is a simple process. Labels are manually allocated, and no
signaling protocol or exchange of control packets are needed. The setup of a static CR-LSP
consumes a few resources. In addition, you need to configure neither the IGP TE nor CSPF for
the static CR-LSP.
The static CR-LSP cannot dynamically adapt to a changing network. Therefore, its application
is very limited.
The static CR-LSP is a special static LSP that has the similar.
Pre-configuration Tasks
Before configuring a static CR-LSP, complete the following tasks:
l
Configuring the static route or IGP to ensure the reachability between LSRs
Enabling basic MPLS functions on each LSR globally and on each interface
Data Preparation
To configure a static CR-LSP, you need the following data.
Issue 02 (2011-09-10)
No.
Data
186
3 MPLS TE Configuration
No.
Data
NOTE
The value of the outgoing label on each node is the value of the incoming label of its next node.
The destination address of a static CR-LSP is the destination address of the TE tunnel interface.
Context
Do as follows on each node along the static CR-LSP:
Procedure
Step 1 Run:
system-view
187
3 MPLS TE Configuration
Step 7 Run:
mpls te
When the MPLS TE is disabled in the interface view, all the CR-LSPs on the current interface change to
Down.
When the MPLS TE is disabled in the MPLS view, the MPLS TE on each interface is disabled, and all
CR-LSPs are deleted.
----End
Context
NOTE
To constrain the bandwidth of CR-LSPs, the procedure is mandatory. In addition, the mpls te lsp-tp
outbound command must be run on the corresponding tunnel interface.
By default, the maximum reservable bandwidth on the link is 0 bit/s. If the maximum reservable bandwidth
is not configured, when the bandwidth of the CR-LSP is constrained, the bandwidth of the CR-LSP is more
than the maximum reservable bandwidth. Therefore, the CR-LSP cannot be set up.
Procedure
Step 1 Run:
system-view
Issue 02 (2011-09-10)
188
3 MPLS TE Configuration
NOTE
l The maximum reservable bandwidth of a link cannot be greater than the actual bandwidth of the link.
A maximum of 80% of the actual bandwidth of the link is recommended for the maximum reservable
bandwidth of the link.
l Neither the BC0 bandwidth nor the BC1 bandwidth can be greater than the maximum reservable
bandwidth of the link.
l If an MPLS TE tunnel to be set up requires the bandwidth that is larger than 67105 kbit/s, it is
recommended that the reserved bandwidth be one thousandth more that the bandwidth to be configured.
----End
Context
Do as follows on the ingress node of a static CR-LSP:
Procedure
Step 1 Run:
system-view
The tunnel interface is created and the tunnel interface view is displayed.
Step 3 To configure the IP address of the tunnel interface, select one of the following commands.
l Run:
ip address ip-address { mask | mask-length } [ sub ]
Because the type of the packet forwarded by the MPLS TE tunnel is MPLS, the commands, such as ip
urpf commands, related to IP packet forwarding configured on this interface are invalid.
Step 4 Run:
tunnel-protocol mpls te
189
3 MPLS TE Configuration
Step 5 Run:
destination ip-address
The destination address of the tunnel is configured, which is usually the LSR ID of the egress
node.
Different types of tunnels need different destination addresses. When the tunnel protocol is
changed to MPLS TE from other different protocols, the configured destination is deleted
automatically and needs to be reconfigured.
Step 6 Run:
mpls te tunnel-id tunnel-id
If MPLS TE parameters on a tunnel interface are modified, you need to run the mpls te commit command
to activate them.
----End
Context
Do as follows on the ingress of a static CR-LSP:
Procedure
Step 1 Run:
system-view
190
3 MPLS TE Configuration
tunnel interface-number specifies the MPLS TE tunnel interface that uses this static CR-LSP.
By default, the Bandwidth Constraints value is ct0, and the value of bandwidth is 0. The
bandwidth used by the tunnel cannot be higher than the maximum reservable bandwidth of the
link.
The value of tunnel-name cannot be spaces or abbreviations. For example, if a tunnel interface
named Tunnel 2/0/0 is specified in the interface tunnel 2/0/0 command, tunnel-name specified
in the static-cr-lsp ingress command must be Tunnel2/0/0; otherwise, the tunnel cannot be set
up. For the transit and egress, tunnel name consistency is not required.
The next hop or outgoing interface is determined by the route from the ingress to the egress. For
the difference between the next hop and outgoing interface, refer to "Static Route Configuration"
in the HUAWEI NetEngine80E/40E Router Configuration Guide - IP Routing.
----End
Context
If the static CR-LSP has only the ingress and egress, this configuration is not needed. If the static
CR-LSP has one or more transits, do as follows on the transit node:
Procedure
Step 1 Run:
system-view
The LSR is set as the transit node of the specified static CR-LSP.
No restriction is specified for the lsp-name of the transit and the egress, but the lsp-name should
not be a duplicate of the existing tunnel name on the node.
----End
Context
Do as follows on the egress of the static CR-LSP:
Issue 02 (2011-09-10)
191
3 MPLS TE Configuration
Procedure
Step 1 Run:
system-view
Prerequisite
The configurations of the static MPLS TE tunnel function are complete.
Procedure
l
Run the display mpls static-cr-lsp [ lsp-name ] [ { include | exclude } ip-address masklength ] [ verbose ] command to check information about the static CR-LSP.
Run the display mpls te tunnel [ destination ip-address ] [ lsp-id ingress-lsr-id sessionid local-lsp-id | lsr-role { all | egress | ingress | remote | transit } ] [ name tunnel-name ]
[ { incoming-interface | interface | outgoing-interface } interface-type interfacenumber ] [ te-class0 | te-class1 | te-class2 | te-class3 | te-class4 | te-class5 | te-class6 | teclass7 ] [ verbose ] command to check information about the tunnel.
Run the display mpls te tunnel statistics or display mpls lsp statistics command to check
the tunnel statistics.
----End
Example
If the configurations succeed, run the preceding commands, and you can view the following
information:
l
Information about the static CR-LSP name, the incoming and outgoing labels, and the
incoming and outgoing interfaces. The status of CR-LSP is Up.
Details of the tunnel interface, including the tunnel name, state description, and attributes.
The tunnel attributes include the LSP ID, ingress, egress, and signaling protocol.
Issue 02 (2011-09-10)
192
3 MPLS TE Configuration
Applicable Environment
A static bidirectional co-routed LSP is applicable to MPLS Transport Profile (TP) networks,
improving network maintainability.
A static CR-LSP is easy to configure: labels are manually allocated, and no signaling protocol
is used to exchange control packets. The setup of a static CR-LSP consumes only a few resources,
and you do not need to configure IGP TE or CSPF for the static CR-LSP. However, static CRLSP application is quite limited. A static CR-LSP cannot dynamically adapt to network changes,
and it uses the same label range (16 to 1023) as a common static LSP.
Pre-configuration Tasks
Before configuring a static bidirectional co-routed LSP, complete the following tasks:
l
Configuring unicast static routes or an IGP to ensure the reachability between LSRs
Data Preparation
To configure a static bidirectional co-routed LSP, you need the following data.
Issue 02 (2011-09-10)
No.
Data
Inbound interface and next-hop address or outbound interface on each transit node
193
3 MPLS TE Configuration
NOTE
The value of the outgoing label on each node is the value of the incoming label on its next hop.
The destination address of a static bidirectional co-routed LSP is the destination address specified
on the tunnel interface.
Context
Do as follows on each node along the static CR-LSP:
Procedure
Step 1 Run:
system-view
When the MPLS TE is disabled in the interface view, all the CR-LSPs on the current interface change to
Down.
When the MPLS TE is disabled in the MPLS view, the MPLS TE on each interface is disabled, and all
CR-LSPs are deleted.
----End
Issue 02 (2011-09-10)
194
3 MPLS TE Configuration
Context
NOTE
To constrain the bandwidth of CR-LSPs, the procedure is mandatory. In addition, the mpls te lsp-tp
outbound command must be run on the corresponding tunnel interface.
By default, the maximum reservable bandwidth on the link is 0 bit/s. If the maximum reservable bandwidth
is not configured, when the bandwidth of the CR-LSP is constrained, the bandwidth of the CR-LSP is more
than the maximum reservable bandwidth. Therefore, the CR-LSP cannot be set up.
Procedure
Step 1 Run:
system-view
l The maximum reservable bandwidth of a link cannot be greater than the actual bandwidth of the link.
A maximum of 80% of the actual bandwidth of the link is recommended for the maximum reservable
bandwidth of the link.
l Neither the BC0 bandwidth nor the BC1 bandwidth can be greater than the maximum reservable
bandwidth of the link.
l If an MPLS TE tunnel to be set up requires the bandwidth that is larger than 67105 kbit/s, it is
recommended that the reserved bandwidth be one thousandth more that the bandwidth to be configured.
----End
Context
Perform the following steps on the ingress of a static bidirectional co-routed LSP:
Issue 02 (2011-09-10)
195
3 MPLS TE Configuration
Procedure
Step 1 Run:
system-view
The destination address is configured for the tunnel. It is usually the LSR ID of the egress.
Various types of tunnels have different requirements for destination addresses. If a tunnel
protocol is changed to MPLS TE, the destination address set using the destination command is
automatically deleted and needs to be reconfigured.
Step 6 Run:
mpls te tunnel-id tunnel-id
196
3 MPLS TE Configuration
NOTE
Each time an MPLS TE parameter is changed, the mpls te commit command must be run to make the
configuration take effect.
----End
Context
Perform the following steps on the ingress of a static bidirectional co-routed LSP:
Procedure
Step 1 Run:
system-view
A static bidirectional co-routed LSP is created and the static bidirectional LSP view is displayed.
Step 3 Run:
forward { nexthop next-hop-address | outgoing-interface interface-type interfacenumber } out-label out-label-value [ bandwidth [ channel ] bandwidth ]
197
3 MPLS TE Configuration
Context
Skip this procedure if a static bidirectional co-routed LSP has only an ingress and an egress. If
a static bidirectional co-routed LSP has a transit node, perform the following steps on this transit
node:
Procedure
Step 1 Run:
system-view
A static bidirectional co-routed LSP is created and the static bidirectional LSP view is displayed.
Step 3 Run:
forward in-label in-label-value { nexthop next-hop-address | outgoing-interface
interface-type interface-number } out-label out-label-value [ bandwidth [ channel ]
bandwidth ]
Context
Perform the following steps on the egress of a static bidirectional co-routed LSP:
Procedure
Step 1 Run:
system-view
A static bidirectional co-routed LSP is created and the static bidirectional LSP view is displayed.
Step 3 Run:
forward in-label in-label-value lsrid ingress-lsrid tunnel-id ingress-sessionid
Issue 02 (2011-09-10)
198
3 MPLS TE Configuration
Context
Perform the following steps on the egress of a static bidirectional co-routed LSP:
Procedure
Step 1 Run:
system-view
Prerequisite
The configurations of a static bidirectional co-routed LSP are complete.
Issue 02 (2011-09-10)
199
3 MPLS TE Configuration
Procedure
l
Run the display mpls te protection tunnel { aps | all | tunnel-id | interface { tunnel
interface-name | interface-type interface-number | interface-name } } verbose to view
information about a specified working tunnel and its protection tunnel.
----End
Example
Run the display mpls te bidirectional command to view information about a static bidirectional
co-routed LSP.
<HUAWEI> display
TOTAL
:
UP
:
DOWN
:
Name
Tunnel0/0/1
Stat
Up
Run the display mpls te protection tunnel command to view information about a specified
working tunnel and its protection tunnel in a tunnel protection group.
<HUAWEI> display mpls te protection tunnel 100
-----------------------------------------------------------------------No. Work-tunnel status /id Protect-tunnel status /id
Switch-Result
-----------------------------------------------------------------------1
in defect
/100
non-defect
/300 protect-tunnel
Applicable Environment
A dynamic signaling protocol adjusts the path of a TE tunnel on the basis of network topology
changes. To implement advanced features such as TE FRR and CR-LSP backup, establishing
an MPLS TE tunnel by using the RSVP-TE signaling protocol is recommended.
Pre-configuration Tasks
Before configuring an RSVP-TE tunnel, complete the following tasks:
l
Issue 02 (2011-09-10)
200
3 MPLS TE Configuration
Data Preparation
To configure an RSVP-TE tunnel, you need the following data.
No.
Data
Tunnel ID
Context
NOTE
l If MPLS TE is disabled in the interface view, all CR-LSPs on the current interface go Down.
l If MPLS TE is disabled in the MPLS view, MPLS TE on each interface is disabled and all CR-LSPs
go Down.
l If RSVP-TE on a node is disabled, RSVP-TE on all interfaces of this node is disabled.
Procedure
Step 1 Run:
system-view
Issue 02 (2011-09-10)
201
3 MPLS TE Configuration
Context
NOTE
To constrain the bandwidth of CR-LSPs, the procedure is mandatory. In addition, the mpls te lsp-tp
outbound command must be run on the corresponding tunnel interface.
By default, the maximum reservable bandwidth on the link is 0 bit/s. If the maximum reservable bandwidth
is not configured, when the bandwidth of the CR-LSP is constrained, the bandwidth of the CR-LSP is more
than the maximum reservable bandwidth. Therefore, the CR-LSP cannot be set up.
Procedure
Step 1 Run:
system-view
202
3 MPLS TE Configuration
NOTE
l The maximum reservable bandwidth of a link cannot be greater than the actual bandwidth of the link.
A maximum of 80% of the actual bandwidth of the link is recommended for the maximum reservable
bandwidth of the link.
l Neither the BC0 bandwidth nor the BC1 bandwidth can be greater than the maximum reservable
bandwidth of the link.
l If an MPLS TE tunnel to be set up requires the bandwidth that is larger than 67105 kbit/s, it is
recommended that the reserved bandwidth be one thousandth more that the bandwidth to be configured.
----End
Context
By default, an OSPF area does not support TE.
The OSPF TE extension uses Opaque Type 10 LSA to carry the TE attribute of a link. Therefore,
the Opaque capability of OSPF must be enabled. TE LSAs are generated only when at least one
neighbor is in the FULL state.
NOTE
If OSPF TE is not configured, no TE LSA exists and thus no TEDB is generated on a network. In this case,
a CR-LSP is established by using IGP routes not routes calculated by CSPF calculation.
Procedure
Step 1 Run:
system-view
The MPLS LSR ID is advertised to multiple OSPF areas. This step is necessary only on an Area
Border Router (ABR) in multiple OSPF areas.
Step 5 Run:
area area-id
Issue 02 (2011-09-10)
203
3 MPLS TE Configuration
Context
Do as follows on each node along a TE tunnel:
Procedure
Step 1 Run:
system-view
IS-IS TE is enabled.
By default, IS-IS does not support TE.
If a level is not specified after IS-IS TE is enabled, IS-IS TE is valid for both Level-1 and Level-2.
Step 5 (Optional) Run:
te-set-subtlv { bw-constraint value | lo-multiplier value | unreserve-bw-sub-pool
value }*
The TLV type for the sub-TLVs used to carry the DS-TE parameters is set.
By default, the BW-constraint sub-TLV is 252; the Local Overbooking Multipliers (LOM) subTLV is 253; the unreserve-BW-sub-pool sub-TLV is 251.
----End
Issue 02 (2011-09-10)
204
3 MPLS TE Configuration
Context
An explicit path consists of a series of nodes. These nodes form a vector path in the sequence
of configuration.
The IP address of an explicit path is the IP address of an interface on the node. Often, the IP
address of a loopback interface on the egress node is used as the destination address of the explicit
path.
Adjacent nodes are connected in the following modes on an explicit path:
l
The strict mode and the loose mode are used separately or together.
By default, the include strict mode is used. This means that the next hop added to the explicit
path must be directly connected to the previous node. A constraint for an explicit path is that the
nodes through which traffic must pass or cannot pass are selectable.
include indicates that an established LSP must pass through the specified nodes.
exclude indicates that an established LSP cannot pass through the specified nodes.
TE tunnels are classified into intra-area tunnels and inter-area tunnels.
l
Intra-area tunnel: indicates that TE tunnels are in a single area. An area is either an OSPF
area or an IS-IS area, not a BGP AS.
Inter-area tunnel: indicates that TE tunnels traverse through multiple areas. Areas are OSPF
areas or IS-IS areas not BGP ASs.
A loose explicit path must be used to establish an inter-area TE tunnel and the next node of the
explicit path must be an ABR or an ASBR.
Do as follows on the ingress of a TE tunnel:
Procedure
Step 1 Run:
system-view
The explicit path is created and the explicit path view is displayed.
Step 3 Run:
next hop ip-address [ include [ strict | loose ] | exclude ]
205
3 MPLS TE Configuration
l Run:
add hop ip-address1 [ include [ strict | loose ] | exclude ] { after | before }
ip-address2
Context
Do as follows on the ingress node of a TE tunnel:
Procedure
Step 1 Run:
system-view
CAUTION
Configuring a tunnel interface on the main control board is recommended. The slot ID of the
main control board is the slot ID in interface-number, which is usually 0. In the situation where
a tunnel interface is configured on an interface board, the tunnel interface will be deleted if the
interface board is pulled out.
NOTE
If the shutdown command is run on the tunnel interface, all tunnels established on the tunnel interface will
be deleted.
Step 3 To configure the IP address of a tunnel interface, run one of the following commands.
Issue 02 (2011-09-10)
206
3 MPLS TE Configuration
The secondary IP address of the tunnel interface is configured only after the primary IP
address is configured.
l To use an unnumbered IP address, run:
ip address unnumbered interface interface-type interface-number
Because the type of the packet forwarded by the MPLS TE tunnel is MPLS, the commands, such as ip
urpf commands, related to IP packet forwarding configured on this interface are invalid.
Step 4 Run:
tunnel-protocol mpls te
The destination address of a tunnel is configured, which is usually the LSR ID of the egress
node.
NOTE
CSPF calculation will fail if the destination address of a tunnel is not the LSR ID of the egress.
Different types of tunnels have different requirements for a destination address. If the tunnel protocol is
changed to MPLS TE, the configuration of the destination command is deleted automatically and needs
to be re-configured.
Step 6 Run:
mpls te tunnel-id tunnel-id
rsvp-te
If MPLS TE parameters on a tunnel interface are changed, run the mpls te commit command to make them
take effect.
----End
207
3 MPLS TE Configuration
Context
Do as follows on the ingress of a TE tunnel:
Procedure
Step 1 Run:
system-view
| ct1 ct1-bw-value ]
[ flow-queue flow-
Context
Do as follows on the ingress of a TE tunnel:
Issue 02 (2011-09-10)
208
3 MPLS TE Configuration
Procedure
Step 1 Run:
system-view
Context
Do as follows on the ingress of a TE tunnel:
NOTE
Configuring CSPF on all the transit nodes is recommended, preventing incomplete path computation on
the ingress.
Procedure
Step 1 Run:
system-view
209
3 MPLS TE Configuration
Prerequisite
The configurations of the RSVP-TE tunnel function are complete.
Procedure
l
Run the display mpls te link-administration bandwidth-allocation [ interface interfacetype interface-number ] command to check the allocation of the link bandwidth.
Run the display ospf [ process-id ] mpls-te [ area area-id ] [ self-originated ] command
to check OSPF TE information.
Run the display isis traffic-eng advertisements [ { level-1 | level-2 | level-1-2 } | { lspid | local } ] * [ process-id | vpn-instance vpn-instance-name ] command to check the ISIS TE status.
Run the display isis traffic-eng link [ { level-1 | level-2 | level-1-2 } | verbose ] * [ processid | vpn-instance vpn-instance-name ] command to check the IS-IS TE status.
Run the display isis traffic-eng network [ level-1 | level-2 | level-1-2 ] [ process-id | vpninstance vpn-instance-name ] command to check the IS-IS TE status.
Run the display isis traffic-eng statistics [ process-id | vpn-instance vpn-instancename ] command to check the IS-IS TE status.
Run the display isis traffic-eng sub-tlvs [ process-id | vpn-instance vpn-instancename ] command to check the IS-IS TE status.
Run the display explicit-path [ path-name ] [ verbose ] command to check the explicit
path.
Run the display mpls te cspf destination ip-address [ affinity properties [ mask maskvalue ] | bandwidth { ct0 ct0-bandwidth | ct1 ct1-bandwidth | ct2 ct2-bandwidth | ct3 ct3bandwidth | ct4 ct4-bandwidth | ct5 ct5-bandwidth | ct6 ct6-bandwidth | ct7 ct7bandwidth }* | explicit-path path-name | hop-limit hop-limit-number | metric-type
{ igp | te } | priority setup-priority | srlg-strict exclude-path-name | tie-breaking
{ random | most-fill | least-fill } ]* command to check path information for CSPF.
Run the display mpls te cspf tedb { all | area area-id | interface ip-address | networklsa | node [ router-id ] } command to check TEDB information for CSPF.
Issue 02 (2011-09-10)
210
3 MPLS TE Configuration
Run the display mpls rsvp-te peer [ interface interface-type interface-number ] command
to check RSVP information of neighbors.
Run the display mpls rsvp-te request [ interface interface-type interface-number peerip-address ] command to check information about the resources that are requsted.
Run the display mpls rsvp-te sender [ interface interface-type interface-number peer-ipaddress ] command to check information about the RSVP sender.
Run the display mpls rsvp-te statistics { global | interface [ interface-type interfacenumber ] } command to check statistics about RSVP-TE.
Run the display mpls te link-administration admission-control [ interface interfacetype interface-number | stale-interface interface-index ] command to check the tunnel
permitted by the local node.
Run the display mpls te tunnel [ destination ip-address ] [ lsp-id ingress-lsr-id sessionid local-lsp-id | lsr-role { all | egress | ingress | remote | transit } ] [ name tunnel-name ]
[ { incoming-interface | interface | outgoing-interface } interface-type interfacenumber ] [ verbose ] command to check tunnel information.
Run the display mpls te tunnel statistics or display mpls lsp statistics command to check
tunnel statistics.
----End
Example
If the configurations succeed, run the preceding commands, and you can view the following
information:
l
Information about links, including the physical bandwidth and available bandwidth of the
link
Information about MPLS RSVP-TE timers, the status of interfaces enabled RSVP-TE, the
bandwidth, the parameters for RSVP neighbors, sender information, and statistics
Tunnel name, incoming and outgoing labels, and incoming and outgoing interfaces.
Detailed information about the tunnel interface on the tunnel ingress, including the tunnel's
name, status, and attributes (including the LSP ID, ingress, and egress)
Issue 02 (2011-09-10)
211
3 MPLS TE Configuration
Applicable Environment
You can create a CR-LSP by using the following methods:
l
The preceding two methods can be used together. If the TE attribute configured in the tunnel interface view
and the TE attribute configured through a CR-LSP attribute template coexist, the former takes precedence
over the latter.
Pre-configuration Tasks
Before using a CR-LSP attribute template to set up a CR-LSP, complete the following tasks:
l
Enable MPLS, MPLS TE, and RSVP TE on the MPLS backbone network
Data Preparation
To use a CR-LSP attribute template to set up a CR-LSP, you need the following data.
Issue 02 (2011-09-10)
No.
Data
(Optional) Affinity value and affinity mask of the CR-LSP attribute template
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
212
3 MPLS TE Configuration
No.
Data
(Optional) Setup priority and hold priority of the CR-LSP attribute template
Context
Do as follows on the ingress of the CR-LSP:
Steps 3 to 10 are optional.
Procedure
Step 1 Run:
system-view
A CR-LSP attribute template is created and the LSP attribute view is displayed.
NOTE
A CR-LSP attribute template can be deleted only when it is not used by any tunnel interface.
The bandwidth is set for the CR-LSP attribute template. The optional bandwidth type varies with
DS-TE modes. In non-DS-TE mode, only CT0 and CT1 are supported. In DS-TE mode, if no
TE-Class mapping table is configured, only CT0, CT1, CT2, and CT3 are supported; if a TEClass mapping table is configured, the CT types configured in the TE-Class mapping table are
adopted.
NOTE
If an MPLS TE tunnel to be set up requires a bandwidth larger than 67105 kbit/s, it is recommended that
the 1/1000 of the configured bandwidth to be reserved.
Issue 02 (2011-09-10)
213
3 MPLS TE Configuration
The setup priority and hold priority are set for the CR-LSP attribute template.
By default, both the setup priority and the hold priority are 7.
Step 7 (Optional) Run:
hop-limit hop-limit
Before enabling or disabling FRR for the CR-LSP attribute template, note the following:
l After FRR is enabled, the route recording function is automatically enabled for the CR-LSP.
l After FRR is disabled, attributes of the bypass tunnel are automatically deleted.
The route recording function is enabled for the CR-LSP attribute template.
By default, the route recording function is disabled.
NOTE
The undo mpls te record-route command can take effect only when FRR is disabled.
The bypass tunnel attributes are configured for the CR-LSP attribute template.
By default, the bypass tunnel attributes are not configured.
Issue 02 (2011-09-10)
214
3 MPLS TE Configuration
NOTE
This command can take effect only when the following conditions are met:
l The CR-LSP attribute template has been enabled with FRR allowing bandwidth protection.
l The bandwidth for the bypass tunnel is lower than or equal to the bandwidth for the CR-LSP attribute
template.
l The setup priority and hold priority of the bypass tunnel are smaller than the setup priority and hold
priority of the CR-LSP attribute template.
Step 11 Run:
commit
----End
Context
Do as follows on the ingress of the CR-LSP:
Procedure
Step 1 Run:
system-view
The primary CR-LSP is set up through the specified CR-LSP attribute template.
If dynamic is used, it indicates that when a CR-LSP attribute template is used to set up a primary
CR-LSP, all attributes in the template adopt the default values.
Step 4 (Optional) Run:
mpls te hotstandby-lsp-constraint number { dynamic | lsp-attribute lsp-attributename }
Issue 02 (2011-09-10)
215
3 MPLS TE Configuration
The hot-standby CR-LSP is set up by using the specified CR-LSP attribute template.
A maximum of three CR-LSP attribute templates can be used to set up a hot-standby CR-LSP.
The hot-standby CR-LSP must be consistent with the primary CR-LSP in the attributes of the
setup priority, hold priority, and bandwidth type. To set up a hot-standby CR-LSP, you should
keep on attempting to use CR-LSP attribute templates one by one in ascending order of the
number of the attribute templates until the hot-standby CR-LSP is set up.
If dynamic is used, it indicates that the hot-standby CR-LSP is assigned the same bandwidth
and priority as the primary CR-LSP, but specified with a different path from the primary CRLSP.
Step 5 (Optional) Run:
mpls te backup hotstandby-lsp-constraint wtr interval
The Wait to Restore (WTR) time is set for the traffic to switch back from the hot-standby CRLSP to the primary CR-LSP.
By default, the WTR time for the traffic to switch back from the hot-standby CR-LSP to the
primary CR-LSP is 10 seconds.
NOTE
The hot-standby CR-LSP specified in the mpls te backup hotstandby-lsp-constraint wtr command must
be an existing one established by running the mpls te hotstandby-lsp-constraint command.
The ordinary backup CR-LSP is set up by using the specified CR-LSP attribute template.
A maximum of three CR-LSP attribute templates can be used to set up an ordinary backup CRLSP. The ordinary backup CR-LSP must be consistent with the primary CR-LSP in the attributes
of the setup priority, hold priority, and bandwidth type. To set up an ordinary backup CR-LSP,
you should keep on attempting to use CR-LSP attribute templates one by one in ascending order
of the number of the attribute template until the ordinary backup CR-LSP is set up.
If dynamic is used, it indicates that the ordinary backup CR-LSP is assigned the same bandwidth
and priority as the primary CR-LSP.
Step 7 Run:
mpls te commit
Prerequisite
All configurations of the CR-LSP set up by using the CR-LSP attribute template are complete.
Issue 02 (2011-09-10)
216
3 MPLS TE Configuration
Procedure
Step 1 Run the display explicit-path [ path-name ] [ tunnel-interface | lsp-attribute | verbose ]
command to view information about the explicit path configured for the CR-LSP attribute
template.
Step 2 Run the display mpls te tunnel-interface lsp-constraint [ tunnel interface-number ] command
to view information about the CR-LSP attribute template on the TE tunnel interface.
Step 3 Run the display mpls te tunnel-interface [ auto-bypass-tunnel tunnel-name | tunnel interfacenumber ] command to view information about the MPLS TE tunnel using the CR-LSP attribute
template.
----End
Example
If the configurations succeed, you can view the following information:
l
List of CR-LSP attribute templates that use the specified explicit path
Information about the CR-LSP attribute templates on the specified TE tunnel interface
Information about the CR-LSPs that are set up through the specified CR-LSP attribute
template
Applicable Environment
RSVP TE supports diversified signaling parameters. It ensures reliability and network resource
efficiency, and offers certain MPLS TE advanced features.
Before performing the configuration tasks described in this section, you must know in detail the
purpose of each task and the influences they have on networks.
Pre-configuration Tasks
Before optimizing the RSVP-TE tunnel, complete the following task:
l
Data Preparation
To optimize the RSVP TE tunnel, you need the following data.
Issue 02 (2011-09-10)
217
3 MPLS TE Configuration
No.
Data
Context
Do as follows on each node along the TE tunnel:
Procedure
Step 1 Run:
system-view
218
3 MPLS TE Configuration
Step 6 Run:
quit
Context
Do as follows on each node along the TE tunnel:
Procedure
Step 1 Run:
system-view
219
3 MPLS TE Configuration
Context
Enabling Srefresh in the interface view or the mpls view on two nodes that are the neighbors of
each other can reduce the cost and improve the performance of a network. In the interface view,
Srefresh can be enabled only on this interface; in the MPLS view, Srefresh can be enabled on
the entire device. After Srefresh is enabled, the retransmission of Srefresh messages is
automatically enabled on the interface or the device.
Assume that a node initializes the retransmission interval as Rf seconds. If receiving no ACK
message within Rf seconds, the node retransmits the RSVP message after (1 + Delta) x Rf
seconds. The value of Delta depends on the link rate. The node retransmits the message until it
receives an ACK message or the times of retransmission reach the threshold (that is,
retransmission increment value).
Procedure
Step 1 Run:
system-view
The Srefresh mechanism that is configured in the interface view takes effect only on the
current interface.
l
The Srefresh mechanism that is configured in the MPLS view takes effect globally. The
Srefresh mechanism in MPLS view is applied to the TE FRR networking. By doing this,
both the usage of network resources and the reliability of the Srefresh mechanism can be
improved.
Step 3 Run:
mpls rsvp-te srefresh
Srefresh is enabled.
By default, Srefresh is disabled on the interface.
Step 4 (Optional) Run:
mpls rsvp-te timer retransmission { increment-value increment | retransmit-value
interval } *
220
3 MPLS TE Configuration
Context
Do as follows on the egress of the TE tunnel:
Procedure
Step 1 Run:
system-view
Receiving ResvConf messages does not mean that the resource reservation succeeds. It means that,
however, resources are reserved successfully only on the farthest upstream node where this Resv message
arrives. These resources may be preempted by other applications later.
----End
Procedure
l
Run the display mpls rsvp-te psb-content [ ingress-lsr-id tunnel-id lsp-id ] command to
check information about RSVP-TE PSB.
Run the display mpls rsvp-te rsb-content [ ingress-lsr-id tunnel-id lsp-id ] command to
check information about RSVP-TE RSB.
Run the display mpls rsvp-te statistics { global | interface [ interface-type interfacenumber ] } command to check RSVP-TE statistics.
----End
Issue 02 (2011-09-10)
221
3 MPLS TE Configuration
Example
If the configurations succeed, run the preceding commands and you can view the following
information:
l
Confirmation of the resource reservation, the state of the Hello extension, and the
configurations of RSVP-TE status timers.
Applicable Environment
RSVP key authentication prevents an unauthorized node from setting up RSVP neighbor
relationships with the local node or generating forged packets to attack the local node.
RSVP key authentication prevents the following unauthorized means of setting up RSVP
neighbor relationships, protecting the local node from attacks (such as malicious reservation of
high bandwidth):
l
An unauthorized node attempts to set up a neighbor relationship with the local node.
A remote node generates and sends forged RSVP messages to set up a neighbor relationship
with the local node.
The message window function and the handshake function, together with RSVP key
authentication, prevent anti-replay attacks or authentication interruption between RSVP
neighbors resulted from RSVP message mis-sequence during network congestion.
The RSVP authentication lifetime is configured, preventing unceasing RSVP authentication. In
the situation where no CR-LSP exists between RSVP neighbors, the neighbor relationship is
kept Up until the RSVP authentication lifetime expires.
Pre-configuration Tasks
Before configuring RSVP authentication, complete the following task:
l
Data Preparation
To configure RSVP authentication, you need the following data.
Issue 02 (2011-09-10)
222
3 MPLS TE Configuration
No.
Data
Context
RSVP authentication uses authentication objects in RSVP messages to authenticate the RSVP
messages, preventing malicious attacks initiated by the modified or forged RSVP messages and
improving the network reliability and security.
The RSVP key authentication is configured either in the interface view or the MPLS RSVP-TE
neighbor view:
l
In the interface view, RSVP key authentication configured is performed between directlyconnected nodes.
In the MPLS RSVP-TE neighbor view, the RSVP key authentication is performed between
neighboring nodes, which is recommended.
Characters ^#^# and $@$@ are used to identify passwords with variable lengths. Characters ^#^# are the
prefix and suffix of a new password, and characters $@$@ are the prefix and suffix of an old password.
Neither of them can be both configured at the beginning and end of a plain text password.
Procedure
l
The configurations must be complete on either of the two directly-connected interfaces within a
period of time three times the interval at which a Path Refresh message is sent; otherwise, the RSVP
session goes Down.
Issue 02 (2011-09-10)
223
1.
3 MPLS TE Configuration
Run:
system-view
Run:
interface interface-type interface-number
Run:
mpls rsvp-te authentication { { { cipher | plain } auth-key } | keychain
keychain-name }
The configurations must be complete on either of the two directly-connected interfaces within a
period of time three times the interval at which a Path Refresh message is sent; otherwise, the RSVP
session goes Down.
1.
Run:
system-view
Run:
mpls rsvp-te peer ip-address
Run:
mpls rsvp-te authentication { { { cipher | plain } auth-key } | keychain
keychain-name }
Issue 02 (2011-09-10)
224
3 MPLS TE Configuration
Context
RSVP neighbors to remain the neighbor relationship when no CR-LSP exists between them until
the RSVP authentication lifetime expires. Configuring the RSVP authentication time does not
affect the existing CR-LSPs.
Do as follows on each node along the tunnel:
Procedure
Step 1 Run:
system-view
The RSVP authentication lifetime that is configured in the interface view takes effect only
on the current interface.
l
If ip-address is specified as an interface address but not the LSR ID of the RSVP
neighbor, the RSVP authentication lifetime takes effect only on the interface.
If ip-address is specified as an address equal to the LSR ID, the RSVP authentication
lifetime takes effect on the entire device.
Step 3 Run:
mpls rsvp-te authentication lifetime lifetime
Context
Do as follows on each node along a tunnel:
Issue 02 (2011-09-10)
225
3 MPLS TE Configuration
Procedure
Step 1 Run:
system-view
The handshake function that is configured in the interface view takes effect only on the
current interface.
l
When ip-address is specified as an interface address but not the LSR ID of the RSVP
neighbor, the handshake function is configured based on the neighbor interface address.
In this case, the handshake function takes effect only on the interface.
When ip-address is specified as an address equal to the LSR ID of the neighbor, the
handshake function is configured based on the neighbor LSR ID. In this case, the
handshake function takes effect on the entire device.
Step 3 Run:
mpls rsvp-te authentication handshake local-secret
If you run the mpls rsvp-te authentication lifetime command after configuring the handshake function,
note that the RSVP authentication lifetime must be greater than the interval for sending RSVP refresh
messages.
If the RSVP authentication lifetime is smaller than the interval for sending RSVP refresh messages, the
RSVP authentication relationship may be deleted because no RSVP refresh message is received within the
RSVP authentication lifetime. In such a case, after the next RSVP refresh message is received, the
handshake operation is triggered. Repeated handshake operations may cause RSVP tunnels unable to be
set up or cause RSVP tunnels to be deleted.
----End
226
3 MPLS TE Configuration
Context
The default window size is 1, which means that a device saves only the largest sequence number
of the RSVP message from neighbors.
When window-size is larger than 1, it means that a device accepts several valid sequence
numbers.
Do as follows on each node along a tunnel:
Procedure
Step 1 Run:
system-view
The message window function that is configured in the interface view takes effect only on
the current interface.
l
When ip-address is specified as an interface address but not the LSR ID of an RSVP
neighbor, the message window function is configured based on the neighbor interface
address. In this case, the handshake function takes effect only on the interface.
When ip-address is specified as an address equal to the LSR ID of the RSVP neighbor,
the message window function is configured based on the neighbor LSR ID. In this case,
the message window function takes effect on the entire device.
Step 3 Run:
mpls rsvp-te authentication window-size window-size
If RSVP is enabled on an Eth-Trunk interface or an IP-Trunk interface, only one neighbor relationship is
established on the trunk link between RSVP neighbors. Therefore, any member interface of the trunk
interface receives RSVP messages in a random order, resulting in RSVP message mis-sequence.
Configuring RSVP message window size prevents RSVP message mis-sequence.
The window size larger than 32 is recommended. If the window size is set too small, the RSVP packets
are discarded because the sequence number is beyond the range of the window size, causing an RSVP
neighbor relationship to be terminated.
----End
Issue 02 (2011-09-10)
227
3 MPLS TE Configuration
Prerequisite
The configurations of RSVP key authentication are complete.
Procedure
Step 1 Run the display mpls rsvp-te peer [ interface interface-type interface-number ] command to
view information about the RSVP neighbor on an RSVP-TE-enabled interface.
----End
Example
After the configurations are successful, run the display mpls rsvp-te peer command on an
interface, and you can view that the number of RSBs in the RSVP-TE neighbor information is
not zero.
Applicable Environment
CSPF uses the TEDB and constraints to calculate appropriate paths and establishes CR-LSPs
through the signaling protocol. MPLS TE provides many methods to affect CSPF computation
to adjust the CR-LSP path, including the following modes:
l
Tie-breaking
CSPF calculates only a shortest path to reach the tunnel destination. During the path
computation, if there are several paths with the same metric, the device select one of them.
Tie-breaking methods for selecting the path are as follows:
Most-fill: selects a link with the largest ratio of the used bandwidth to the maximum
reservable bandwidth. This method ensures that bandwidth resources are used
effectively.
Least-fill: selects the link with the smallest ratio of the used bandwidth to the maximum
reservable bandwidth. This method ensures that links use bandwidth resources evenly.
Random: selects the link at random. This method can distribute LSPs evenly over links
regardless of the bandwidth.
Issue 02 (2011-09-10)
228
3 MPLS TE Configuration
NOTE
Tie-breaking selects the link based on bandwidth ratio. If the ratios are the same, such as no reservable
bandwidth or the equal bandwidth is used, the link that is found firstly is selected, even if least-fill
or most-fill is configured.
Route pinning
A successfully-established CR-LSP does not vary with the route change. This is called
route pinning.
SRLG
A shared risk link group (SRLG) is a set of links which are likely to fail concurrently due
to sharing a physical resource. Links in the group have a shared risk. That is, if one of the
links fails, other links in the group may fail too.
In MPLS TE, SRLG is a feature that enhances the path reliability for hot-standby tunnel
or the TE FRR tunnel. The two or more links can have a common risk when they share
common physical resource. For example, the sub-interfaces share the risk with their main
interface since the sub-interface definitely goes down when its main interface goes down.
If the backup or bypass tunnel goes through a link which shares a same risk with the primary
tunnel, the probability of backup tunnel going down along with the primary tunnel is high.
Hop limit
Hop limit is a rule for path selection for setting up a CR-LSP. It limits the number of hops
that a CR-LSP allows.
Re-optimization
Dynamically optimizing a CR-LSP is to periodically recompute routes for the CR-LSP. If
the route in recomputation is better than the route in use, then a new CR-LSP is established
according to the recomputed route. Meanwhile, services are switched from the old CR-LSP
to the new CR-LSP, and the old one is deleted.
Pre-configuration Tasks
The configuration tasks described in this section are some special configurations for CSPF in
MPLS TE. Before performing these configuration tasks, you need to know their influences on
the system.
Before adjusting the selection of the CR-LSP, complete the following task:
l
Data Preparation
To adjust the selection of the CR-LSP, you need the following data.
Issue 02 (2011-09-10)
No.
Data
229
3 MPLS TE Configuration
No.
Data
Context
Do as follows on the ingress of the CR-LSP tunnel:
Procedure
Step 1 Run:
system-view
230
3 MPLS TE Configuration
Follow-up Procedure
The modification of administrative group takes effect only on LSPs that are established after
modification.
After the modified affinity property is committed, the established LSP in this tunnel may be
affected and the system recalculates the path for the TE tunnel.
Context
Configuring SRLG includes:
l
Procedure
Do as follows on the links which are in the same SRLG.
1.
Run:
system-view
Run:
interface interface-type interface-number
Run:
mpls te srlg srlg-number
Run:
system-view
Run:
mpls
Run:
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
231
3 MPLS TE Configuration
l If you specify the strict keyword, the CSPF always considers the SRLG as a constraint
when calculating the path for the backup CR-LSP or the hot-standby CR-LSP.
l If you specify the preferred keyword, CSPF tries to calculate the path which avoids the
links in the same SRLG as the protected interface(s); if the calculation fails, CSPF does
not consider the SRLG as a constraint anymore.
----End
Context
Do as follows on the ingress of the CR-LSP:
Procedure
Step 1 Run:
system-view
Procedure
l
Run:
system-view
Issue 02 (2011-09-10)
232
3 MPLS TE Configuration
Run:
interface tunnel interface-number
Run:
mpls te path metric-type { igp | te }
Run:
mpls te commit
Run:
quit
(Optional) Run:
mpls
(Optional) Run:
mpls te path metric-type { igp | te }
The path metric type used by the tunnel during route selection is specified.
If the mpls te path metric-type command is not run in the tunnel interface view, the
metric type in the MPLS view is adopted; otherwise, the metric type in the tunnel
interface view is used.
By default, path metric type used by the tunnel during route selection is TE.
l
Run:
system-view
Run:
interface interface-type interface-number
Run:
mpls te metric value
233
3 MPLS TE Configuration
Context
Do as follows on the ingress of the CR-LSP tunnel:
Procedure
Step 1 Run:
system-view
234
3 MPLS TE Configuration
Context
CSPF uses a locally-maintained traffic-engineering database (TEDB) to calculate the shortest
path to the destination address. Then, the signaling protocol applies for and reserves resources
for the path. In the case of a link on a network is faulty, if the routing protocol fails to notify
CSPF of updating the TEDB in time, this may cause the path calculated by CSPF to contain the
faulty link.
As a result, the control packets, such as RSVP Path messages, of a signaling protocol are
discarded on the faulty link. Then, the signaling protocol returns an error message to the upstream
node. Receiving the link error message on the upstream node triggers CSPF to recalculate a path.
The path recalculated by CSPF and returned to the signaling protocol still contains the faulty
link because the TEDB is not updated. The control packets of the signaling protocol are still
discarded and the signaling protocol returns an error message to trigger CSPF to recalculate a
path. The procedure repeats until the TEDB is updated.
To avoid the preceding situation, when the signaling protocol returns an error message to notify
CSPF of a link failure, CSPF sets the status of the faulty link to INACTIVE and enables a failed
link timer. Then, CSPF does not use the faulty link in path calculation until CSPF receives a
TEDB update event or the failed link timer expires.
Before the failed link timer expires, if a TEDB update event is received, CSPF deletes the failed
link timer.
Do as follows on the ingress along a CR-LSP tunnel:
Procedure
Step 1 Run:
system-view
235
3 MPLS TE Configuration
Context
In the loop detection mechanism, a maximum number of 32 hops are allowed on an LSP. If
information about the local LSR is recorded in the path information table, or the number of hops
on the path exceeds 32, this indicates that a loop occurs and the LSP fails to be set up.
Do as follows on the ingress of the CR-LSP tunnel:
Procedure
Step 1 Run:
system-view
Context
By default, route pinning is disabled.
NOTE
If route pinning is enabled, the MPLS TE re-optimization cannot be used at the same time.
Procedure
Step 1 Run:
system-view
Issue 02 (2011-09-10)
236
3 MPLS TE Configuration
Prerequisite
All configurations of adjusting the patch for CR-LSP are complete.
Procedure
Step 1 Run the display mpls te tunnel-interface [ tunnel interface-number ] command to check
information about the tunnel interface.
----End
Example
If the configuration is successful, run the preceding command and you can view the following
items:
l
Tie-breaking policy
If re-optimization is enabled, the status is displayed as "Enabled" and the interval is also
displayed
237
3 MPLS TE Configuration
Applicable Environment
During the establishment of an MPLS TE tunnel, specific configurations are required in the
practical application. This section describes the special configuration.
Pre-configuration Tasks
Note that tasks introduced in this section are of special configuration in MPLS TE. Before
performing these configuration tasks, you must know their influences on the system.
Before adjusting the establishment of the MPLS TE tunnel, complete the following task:
l
Data Preparation
To adjust the establishment of the MPLS TE tunnel, you need the following data.
No.
Data
Context
Do as follows on the ingress of the CR-LSP tunnel:
Procedure
Step 1 Run:
system-view
Issue 02 (2011-09-10)
238
3 MPLS TE Configuration
The value of the setup priority must not be less than that of the holding priority. That is, the setup priority
should not be higher than the holding priority.
Step 4 Run:
mpls te commit
Context
NOTE
l If the re-optimization is enabled, the route pinning cannot be used at the same time.
l The CR-LSP re-optimization cannot be configured when the resource reservation style is FF.
Procedure
Step 1 Run:
system-view
239
3 MPLS TE Configuration
Step 5 Run:
return
Context
Do as follows on the ingress of the CR-LSP tunnel:
Procedure
Step 1 Run:
system-view
240
3 MPLS TE Configuration
If the establishment of a tunnel fails, the system attempts to reestablish the tunnel within the set
interval and the maximum number of attempts is the set reestablishment times.
----End
Context
By default, routes and labels are not recorded.
Do as follows on the ingress of the CR-LSP tunnel:
Procedure
Step 1 Run:
system-view
The route and label are recorded when establishing the tunnel.
Step 4 Run:
mpls te commit
Context
Do as follows on each node on which multiple RSVP CR-LSPs need to be reestablished:
Procedure
Step 1 Run:
system-view
Issue 02 (2011-09-10)
241
3 MPLS TE Configuration
Prerequisite
All configurations of adjusting the establishment of an MPLS TE tunnel are complete.
Procedure
Step 1 Run the display mpls te tunnel-interface [ tunnel interface-number ] command to view
information about the tunnel interface.
----End
Example
If the configurations are successful, run the preceding commands, and you can view the
following items:
l
The route record and label record of the tunnel are enabled.
242
3 MPLS TE Configuration
Applicable Environment
In MPLS TE, traffic forwarding is affected by the configurations that changes the path through
which IP traffic or MPLS traffic passes or the configuration that can limit traffic types of the TE
tunnel.
This section describes several measures to adjust traffic forwarding in MPLS TE.
Pre-configuration Tasks
The configuration described in this section should be used together with CSPF and the dynamic
signaling protocol (such as RSVP-TE).
Before adjusting the traffic forwarding, complete the following task:
l
Data Preparation
To adjust the traffic forwarding, you need the following data.
No.
Data
Context
NOTE
The IGP shortcut and the Forwarding Adjacency cannot be used together.
Procedure
Step 1 Run:
system-view
Issue 02 (2011-09-10)
243
3 MPLS TE Configuration
Step 4 Run:
mpls te igp metric { absolute | relative } value
Context
The routing protocol performs bidirectional detection on a link. When using the forwarding
adjacency to advertise LSP links to other nodes, configure another tunnel for transferring data
packets in the reverse direction. Then, enable the forwarding adjacency on these two tunnels.
NOTE
244
3 MPLS TE Configuration
Procedure
Step 1 Run:
system-view
Step 5 Run:
mpls te commit
Context
MPLS TE adopts a make-before-break mechanism. When attributes of an MPLS TE tunnel such
as bandwidth and path change, a new CR-LSP with new attributes, also called Modified LSP,
must be established. To prevent data loss during traffic switching, the new CR-LSP must be
established before the original CR-LSP is torn down. Through the make-before-break
mechanism, the system does not need to calculate the bandwidth to be reserved for the new CRLSP. That is, the new CR-LSP shares the bandwidth with the original CR-LSP.
Issue 02 (2011-09-10)
245
3 MPLS TE Configuration
In practical applications, if the upstream nodes are not as busy as the downstream nodes, the
original CR-LSP may be deleted in advance, causing temporary traffic interruption.
To avoid this problem, you can configure the switch delay and deletion delay on the ingress of
the tunnel.
Do as follows on the ingress:
Procedure
Step 1 Run:
system-view
Applicable Environment
To form a uniform TE database in an IGP domain, OSPF-TE and ISIS-TE need to be enabled
to update and flood information about the traffic engineering database (TEDB) when the
remaining bandwidth changes on the MPLS interface.
When a number of tunnels that need reservable bandwidth are set up on a node, the system
frequently updates and floods information about the TEDB. For example, suppose that the
bandwidth of a certain link is 100 Mbit/s. When 100 TE tunnels whose bandwidth is 1 Mbit/s
are set up, the flooding is performed for 100 times.
The system provides the following mechanism to suppress the frequency of TEDB update and
flooding.
l
Issue 02 (2011-09-10)
When the ratio of the reserved bandwidth for an MPLS TE tunnel on a link to the remaining
bandwidth of the link in the TEDB is equal to or greater than the set threshold (that is, flood
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
246
3 MPLS TE Configuration
threshold of the bandwidth), OSPF TE and IS-IS TE flood the link information to all the
nodes within the domain and update the TEDB.
l
When the ratio of the released bandwidth of the MPLS TE tunnel on a link to the remaining
bandwidth of the link in the TEDB is equal to or greater than the set threshold, OSPF TE
and IS-IS TE flood the link information to all the nodes within the domain and update the
TEDB.
By default, the flood threshold is 10%. Its value can be modified through command lines.
Pre-configuration Tasks
Before adjusting the flood threshold of the bandwidth, complete the following task:
l
Data Preparation
To adjust the flood threshold of the bandwidth, you need the following data.
No.
Data
Context
The bandwidth flooding threshold indicates the ratio of the link bandwidth occupied or released
by a TE tunnel to the link bandwidth remained in the TEDB.
If the link bandwidth changes little, bandwidth flooding wastes network resources. For example,
if link bandwidth is 100 Mbit/s and 100 TE tunnels (with bandwidth as 1 Mbit/s) are created
along this link, bandwidth flooding need be performed for 100 times.
If the flooding threshold is set to 10%, bandwidth flooding is not performed when tunnel 1 to
tunnel 9 are created. When tunnel 10 is created, the bandwidth of tunnel 1 to tunnel 10 (10 Mbit/
s in total) is flooded. Similarly, bandwidth flooding is not performed when tunnel 11 to tunnel
18 are created. When tunnel 19 is created, the bandwidth of tunnel 11 to tunnel 19 is flooded.
Therefore, configuring bandwidth flooding threshold can reduce the times of bandwidth flooding
and hence ensure the efficient use of network resources.
By default, on a link, IGP flood information about this link and CSPF updates the TEDB
accordingly if one of the following conditions is met:
l
The ratio of the bandwidth reserved for an MPLS TE tunnel to the bandwidth remained in
the TEDB is equal to or higher than 10%.
The ratio of the bandwidth released by an MPLS TE tunnel to the bandwidth remained in
the TEDB is equal to or higher than 10%.
247
3 MPLS TE Configuration
Procedure
Step 1 Run:
system-view
Applicable Environment
When the automatic bandwidth adjustment is enabled, the bandwidth of the tunnel can be
automatically adjusted according to traffic.
The system periodically collects the traffic rates of outgoing interfaces on the tunnel and
calculates the average bandwidth of the tunnel within a period of time. The establishment of an
LSP is requested according to the bandwidth constraint of the sampled maximum value of
average bandwidth. After the LSP is set up, the old LSP is torn down through the make-beforebreak feature and the traffic is switched to the new LSP.
Pre-configuration Tasks
Before configuring the bandwidth automatic adjustment, complete the following task:
l
Data Preparation
To configure the automatic adjustment of the tunnel bandwidth, you need the following data.
Issue 02 (2011-09-10)
248
3 MPLS TE Configuration
No.
Data
Sampling interval
Context
By default, automatic bandwidth adjustment is disabled.
The sampling interval is configured in the MPLS view, and is valid for all MPLS TE tunnels.
The rate of the outgoing interface on an MPLS TE tunnel is recorded at each sampling interval.
The actual average bandwidth allocated to the MPLS TE tunnel in a sampling interval can thus
be obtained.
After automatic bandwidth adjustment is enabled, running the mpls te timer auto-bandwidth
command to configure periodic sampling obtains the average bandwidth of the MPLS TE tunnel
during a sampling interval. The system recalculates an average bandwidth based on sampling
during a sampling interval and uses the bandwidth to establish an MPLS TE tunnel. After the
MPLS TE tunnel is established, traffic switches to the new MPLS TE tunnel, and the original
MPLS TE tunnel is deleted. If the MPLS TE tunnel fails to be established, traffic is still being
transmitted along the original MPLS TE tunnel. The bandwidth will be adjusted after the next
sampling interval expires.
Configuring the parameter threshold controls whether to adjust the bandwidth of an MPLS TE
tunnel.
The system checks whether the difference between the sampled average bandwidth and the actual
bandwidth, if the ratio of the difference to the actual bandwidth is larger than the value of
threshold. If the difference is equal to or larger than the value of threshold, the system
automatically adjusts the bandwidth.
If traffic volume changes frequently on a network but the bandwidth does not need to be adjusted
accordingly, set the value of threshold to a large value.
NOTE
The mpls te auto-bandwidth command cannot be configured together with any of the following commands
on one tunnel interface:
l
mpls te route-pinning
mpls te backup
mpls te resv-style ff
249
3 MPLS TE Configuration
Procedure
Step 1 Run:
system-view
The automatic bandwidth adjustment is enabled and the sampling interval is specified.
By default, the system automatically adjusts bandwidth every 24 hours and bandwidth range is
not restricted unless interval is specified.
Step 4 Run:
quit
The frequency and allowable bandwidth range for adjustment are configured.
l Run:
mpls te auto-bandwidth collect-bw [ frequency interval ] [ max-bw max-bandwidth
min-bw min-bandwidth ]
The frequency and allowable bandwidth range for collection are configured.
Step 7 Run:
mpls te commit
Prerequisite
All configurations of the automatic adjustment of the tunnel bandwidth are complete.
Issue 02 (2011-09-10)
250
3 MPLS TE Configuration
Procedure
Step 1 Run the display current-configuration command to check configuration information about
automatic adjustment of the tunnel bandwidth.
----End
Example
After the configuration is successful, run the display current-configuration command on the
ingress of the tunnel, and you can view the following configuration information about the tunnel.
l
Automatically-adjusted frequency
Applicable Environment
For a physical link of a TE tunnel, besides traffic on the TE tunnel, the physical link may bear
MPLS traffic of other TE tunnels, MPLS traffic of other non-CR-LSPs, or even IP traffic
simultaneously. To limit the TE tunnel traffic within a bandwidth range that is actually
configured, you need to set a limit rate for TE tunnel traffic.
After the configuration of the limit rate, TE traffic is limited to a bandwidth range that is actually
configured; otherwise, TE traffic of which the bandwidth is higher than the set bandwidth is
dropped.
Pre-configuration Tasks
Before configuring the limit rate of MPLS TE traffic, complete the following task:
l
Data Preparation
To configure the limit rate of MPLS TE traffic, you need the following data.
Issue 02 (2011-09-10)
No.
Data
251
3 MPLS TE Configuration
Context
NOTE
Before configuring the limit rate of MPLS TE traffic, you need to run the mpls te bandwidth command
on a corresponding tunnel interface. Otherwise, the limit rate of TE traffic is unavailable.
Procedure
Step 1 Run:
system-view
Prerequisite
The configurations of the limit rate of MPLS TE traffic function are complete.
Procedure
l
----End
Example
Run the display mpls te tunnel-interface command, and you can view that the CAR policy is
enabled.
Issue 02 (2011-09-10)
252
3 MPLS TE Configuration
Applicable Environment
MPLS TE tunnel application may has the following four scenarios:
l
One TE tunnel bears all types (such as, video, voice, and data) of non-VPN services.
MPLS TE tunnel without Diff-Serv (Differentiated Services) cannot provide the QoS according
to each traffic type. For example, voice flow and video flow are transmitted over a TE tunnel.
The video data frames may be transmitted more repeatedly than the voice flow. Thus, the video
data requires a higher drop precedence than the voice data. The MPLS TE tunnel, however,
allocates the same drop precedence for voice and video flows irrespective of traffic types.
To prevent service interference in one tunnel, you can set up a TE tunnel for each type of each
VPN or non-VPN service. This scheme may waste resources because multiple tunnels need to
be set up if there are large numbers of VPNs bearing different types of services over the network.
In the above listed scenarios, deployment of DS-TE tunnels is the best scheme. The edge nodes
in the DS-TE area divide the traffic into several classes, and add the class information into the
DSCP field in packets. The internal node chooses a proper PHB (Per Hop Behavior) for the
packet according to the DSCP value.
DS-TE optimizes network resources, classify service types, and reserve resources for different
types of services. One DS-TE tunnel can carry up to 8 types of service.
NOTE
l To configure standard DS-TE tunnel services, you need to configure the ingress and egress to support
HQoS. This, however, is not required on the Non-standard DS-TE tunnel.
l When services of the same type of multiple VPNs are carried on the same CE of the DS-TE tunnel,
you can limit the bandwidth of each type of services for each VPN on the access CE to prevent source
competition among services of the same type of multiple VPNs.
l To prevent non-VPN services and VPN services from completing resources, you can configure DSTE to carry VPN services only or configure the bandwidth for non-VPN services in DS-TE.
Pre-configuration Tasks
Before configuring DS-TE, you need to complete the following tasks:
Issue 02 (2011-09-10)
253
3 MPLS TE Configuration
Configuring unicast static routes or IGP on each LSR to guarantee the reachability between
LSRs at the network layer
Enabling MPLS TE and MPLS RSVP-TE in system view and interface view on each LSR
Data Preparation
To configure DS-TE, you need the following data.
No.
Data
DS-TE mode
Link bandwidth
Context
Do as follows on each LSR in a DS-TE domain:
Procedure
Step 1 Run:
system-view
254
3 MPLS TE Configuration
Follow-up Procedure
In the NE80E/40E, the non-IETF mode and the IETF mode can be switched to each other. When
the IETF mode is switched to the Non-IETF mode, part LSPs may be deleted or the interworking
may fail. Therefore, be cautious when using the switch command.
NOTE
When the non-IETF DS-TE mode is switched to the IETF DS-TE mode, the user configurations cannot be
lost or modified; however, when the IETF DS-TE mode is switched to the non-IETF DS-TE mode, the
user configurations that are supported in the non-IETF mode but are not supported in the non-IETF mode
are lost or modified as follows:
l The extended-MAM configured in IETF DS-TE mode is automatically switched to the MAM. which
may cause an interworking problem.
l The interface bandwidth values set for BC2 to BC7 in IETF DS-TE mode are deleted.
l The configured mpls te commit command on the tunnel interface is deleted.
Change in
the
bandwidth
constraint
s model
Change in
the
bandwidth
TE-class
mapping
table
NOTE
For information about the default TEclass mapping table, see Table 3-2.
LSP
deletion
Issue 02 (2011-09-10)
255
3 MPLS TE Configuration
Context
Do as follows on each LSR in a DS-TE domain:
Procedure
Step 1 Run:
system-view
Context
This configuration procedure is unnecessary to the non-IETF DS-TE.
For IETF DS-TE, it is recommended that the TE-class mapping tables applied to the entire DSTE domain are the same. Otherwise, Some LSPs may not be set up correctly.
Do as follows on each LSR of a DS-TE domain in DS-TE IETF mode:
Procedure
Step 1 Run:
system-view
Issue 02 (2011-09-10)
256
3 MPLS TE Configuration
A TE-class mapping table is configured and the TE-Class mapping table view is displayed.
Step 3 Run one or multiple commands as follows to configured TE-Classes:
l To configure TE-Class0, run:
te-class 0 class-type { ct0 | ct1 | ct2 | ct3 | ct4 | ct5 | ct6 | ct7 }
priority priority [ description description-info ]
When configuring a TE-class mapping table, pay attention to the following information:
l Each DS-TE node has one TE-class mapping table at most.
l TE-class is a global concept, that is , TE-class is applied to all DS-TE tunnels of the LSR.
l A TE-class indicates the combination of a Class-Type (CT) and priority. The priority
indicates the priority for CR-LSP preemption rather than the value of the EXP field in the
MPLS packet header. The value of the preemption priority ranges from 0 to 7. The smaller
the value is, the higher the priority is. A CR-LSP can be set up only when both the combination
of its CT and setup priority (<CT, setup-priority>) and the combination of its CT and holding
priority (<CT, hold-priority>) exist in the TE-class mapping table. For example, suppose the
TE-class mapping table of a certain node contains only TE-Class[0] = <CT0, 6> and TEClass[1] = <CT0, 7>. Only the following types of CR-LSPs can be set up successfully:
Class-Type = CT0, setup-priority = 6, hold-priority = 6
Class-Type = CT0, setup-priority = 7, hold-priority = 6
Class-Type = CT0, setup-priority = 7, hold-priority = 7
NOTE
The setup-priority cannot be higher than the hold-priority. Therefore, the LSP , whose Class-Type is
CT0, setup-priority is 6, holding priority is 7, does not exist.
l In the MAM and extended-MAM, the CT of a higher priority can preempt the bandwidth of
CTs of the same type. CTs of different types do not preempt the bandwidth of each other.
l In the RDM, the preemption of bandwidth among CTs is determined by the preemption
priority and the corresponding bandwidth constraint. Assume m and n are preemption
priorities (0<=m<n<=7) and i and j are CT values (0<=i<j<=7).
Issue 02 (2011-09-10)
257
3 MPLS TE Configuration
CTi with priority m can preempt the bandwidth of CTi with priority n or the bandwidth
of CTj with priority n.
The total bandwidth of CTi is equal to or less than the bandwidth of BCi.
l When the bandwidth of all CTs along an LSP meets the requirements, the preemption can
be performed and the LSP can be set up.
In DS-TE IETF mode, when the TE-class mapping table is not configured, the default TE-class
mapping table is applied. See Table 3-2.
Table 3-2 Default TE-class mapping table
TE-Class
CT
Priority
TE-Class[0]
TE-Class[1]
TE-Class[2]
TE-Class[3]
TE-Class[4]
TE-Class[5]
TE-Class[6]
TE-Class[7]
NOTE
After a TE-class is configured, you can run the { te-class0 | te-class1 | te-class2 | te-class3 | te-class4 | teclass5 | te-class6 | te-class7 } description description-info command to modify the TE-class description.
----End
Context
Do as follows on each outgoing interface along the LSP in a DS-TE domain:
Procedure
Step 1 Run:
system-view
258
3 MPLS TE Configuration
Step 3 Run:
mpls te bandwidth max-reservable-bandwidth bw-value
Follow-up Procedure
In different bandwidth constraints models, the relationships between the reservable bandwidth
and the bandwidth of each BC are different.
l
In the RDM: max-reservable-bandwidth >= bc0-bw-value >= bc1-bw-value >= bc2-bwvalue >= bc3-bw-value >= bc4-bw-value >= bc5-bw-value >= bc6-bw-value >= bc7-bwvalue
In the MAM: max-reservable-bandwidth >= bc0-bw-value + bc1-bw-value + bc2-bwvalue + bc3-bw-value + bc4-bw-value + bc5-bw-value + bc6-bw-value + bc7-bw-value
BC is the bandwidth constraint for outgoing interface, while CT bandwidth is the bandwidth of
the class type of DS-TE tunnel. The total bandwidth of BCi (0 <= i <= 7) of an interface is equal
to or greater than the CTi bandwidth of all tunnels passing through this outgoing interface. For
example, three LSPs of CT1 pass through a link and their bandwidth values are x, y, and z
respectively. The bandwidth of BC1 of the link should be equal to or greater than the total
bandwidth of x, y, and z.
Context
Do as follows on the ingress of a TE tunnel:
Procedure
Step 1 Run:
system-view
The tunnel interface is created and the tunnel interface view is displayed.
Step 3 (Optional) Run:
description text
Issue 02 (2011-09-10)
259
3 MPLS TE Configuration
The LSR ID of the egress is configured as the destination address of the tunnel.
By default, the tunnel is a GRE tunnel. Different tunnels require different destination addresses.
When the tunnel protocol is changed from another protocol to MPLS TE, the preceding
destination address is deleted and a new one needs to be configured.
Step 7 Run:
mpls te tunnel-id tunnel-id
The setup priority should not be higher than the holding priority. When the holding priority is not specified,
it is the same as the setup priority.
Step 10 Run:
mpls te commit
260
3 MPLS TE Configuration
When the MPLS TE parameters are modified each time, you need to run the mpls te commit
command to commit the configuration.
----End
Procedure
l
Run:
system-view
Run:
static-cr-lsp ingress { tunnel-interface tunnel interface-number | tunnelname } destination destination-address { nexthop next-hop-address |
outgoing-interface interface-type interface-number } out-label out-label
bandwidth { ct0 | ct1 | ct2 | ct3 | ct4 | ct5 | ct6 | ct7 } bandwidth
The ingress of the static CR-LSP is configured and its CT and the bandwidth are
specified.
NOTE
l tunnel interface-number is the interface number of the MPLS TE tunnel of the static CRLSP.
l The static CR-LSP supports eight CTs in DS-TE IETF mode and supports only CT0 and
CT1 in DS-TE non-IETF mode. That is, the CT of the static CR-LSP in IETF mode can be
whichever of the CT0 to CT7; the static CR-LSP in non-IETF mode can only be CT0 or
CT1.
l The tunnel bandwidth cannot exceed the max-reservable bandwidth of the link.
l tunnel-name must be the same as that in the interface tunnel interface-number command.
The value is a case-sensitive string without blank space or abbreviation. Assume a tunnel
interface is created through the interface tunnel 2/0/0 command. The tunnel name is
Tunnel 2/0/0 and the parameter of the ingress of the static CR-LSP must be Tunnel 2/0/0.
Otherwise, the tunnel is set up incorrectly. This rule is inapplicable to transit LSRs or the
egress.
The static CR-LSP supports the single CT only in DS-TE IETF mode. The static CR-LSP
has the highest priority whose value is zero, and does not support bandwidth preemption.
That is, when a static CR-LSP is being set up, it does not preempt the resources of other
LSPs regardless whether the unreserved bandwidth of its out interface is enough or not. In
addition, after a static CR-LSP is set up, its bandwidth cannot be preempted by other LSPs.
On one node (ingress, transit LSR, or egress) in any Bandwidth Constraints model, the total
bandwidth of CTi is not more than the bandwidth of BCi (0 <= i <= 7). That is, CTi can
use only bandwidth of BCi.
For instance, the bandwidth of BC1 on PE is x. Two static CR-LSPs with the CT1 bandwidth
being y and z respectively are set up on the PE. The total bandwidth of CT1s (y + z) is not
more than the bandwidth of BC1 (x).
Issue 02 (2011-09-10)
261
3 MPLS TE Configuration
NOTE
If the bandwidth of the MPLS TE tunnel is configured more than 28630 kbit/s, the actual bandwidth
allocation on the MPLS TE tunnel may be not precise. The MPLS TE tunnel, however, can be set
up successfully.
Run:
system-view
Run:
static-cr-lsp transit lsp-name incoming-interface interface-type
interface-number in-label in-label-value { nexthop next-hop-address |
outgoing-interface interface-type interface-number } out-label out-labelvalue bandwidth { ct0 | ct1 | ct2 | ct3 | ct4 | ct5 | ct6 | ct7 } bandwidth
Run:
system-view
Run:
static-cr-lsp egress lsp-name incoming-interface interface-type interfacenumber in-label in-label [ lsrid ingress-lsr-id tunnel-id tunnel-id ]
Procedure
l
Configuring IGP-TE
For detailed configurations, see the section Configuring OSPF TE or Configuring IS-IS
TE.
Configuring CSPF
For detailed configurations, see the section Configuring CSPF.
Issue 02 (2011-09-10)
262
1.
3 MPLS TE Configuration
Run:
system-view
Run:
interface tunnel interface-number
Run one of the following commands to configure the bandwidth of the MPLS TE
tunnel interface.
To configure the single CT, run:
mpls te bandwidth { ct0 bw-value [ flow-queue ] | ct1 bw-value [ flowqueue ] | ct2 bw-value | ct3 bw-value | ct4 bw-value | ct5 bw-value |
ct6 bw-value | ct7 bw-value }
NOTE
l If you specify the name of the flow queue template referenced by the tunnel in this
command, traffic over the tunnel is then scheduled and assigned bandwidth based on
the flow queue template.
l If the flow queue template referenced by the tunnel is not specified, the system
automatically generates the flow queue template referenced by the tunnel according to
the CT and flow queue mapping configured in the ct-flow-mapping view.
If the flow queue template needs to be referenced when the single CT is configured, configure
the flow queue template first. For detailed configurations of the flow queue template, refer to
the HUAWEI NetEngine80E/40E Router Configuration Guide - QoS.
In tunnel policy, the multiple class type (multi-CT) CR-LSP supports only the VPN tunnel
binding mode rather than the select-sequence mode.
4.
Run:
mpls te commit
If the bandwidth of the MPLS TE tunnel is configured as more than 28630 kbit/s, the bandwidth
allocation on the MPLS TE tunnel may be not precise. The MPLS TE tunnel, however, can be set
up successfully.
Create and configure the explicit path. See Configuring MPLS-TE Explicit Path.
2.
Run:
quit
Issue 02 (2011-09-10)
263
3 MPLS TE Configuration
Run:
interface tunnel interface-number
Run:
mpls te path explicit-path path-name
Run:
mpls te commit
Procedure
Step 1 Run:
system-view
The template of mappings between CTs and flow queues is created and the ct-flow-mapping
view is displayed.
Step 3 Run:
map ct ct-number to { cs7 | cs6 | ef | af4 | af3 | af2 | af1 | be } [ pq | wfq |
lpq ]
Issue 02 (2011-09-10)
264
3 MPLS TE Configuration
NOTE
Step 4 Run:
ct-flow-mapping commit
The mappings between CTs and flow queues defined in the template are committed. Thus, the
mappings can take effect.
Step 5 Run:
quit
The interface is the physical interface that is bound to the DS-TE tunnel on the ingress.
Step 7 Run:
mpls te ct-flow-mapping mapping-name
The template of mappings between CTs and flow queues is applied to the interface.
Step 8 (Optional) Run:
mpls te ct-bandwidth unshared
The interface enabled with DS-TE is configured that CTs do not share the bandwidth of each
other.
Issue 02 (2011-09-10)
265
3 MPLS TE Configuration
NOTE
l When the interface enabled with DS-TE is configured to share bandwidths of CTs, it indicates that eight
CTs of a DS-TE tunnel can share the bandwidth of each other. In this manner, the bandwidth of the DS-TE
tunnel is efficiently used. Thus, it is recommended you to adopt the shared attribute by default.
l When CTs can share the bandwidth of each other on the interface enabled with DS-TE, the shaping parameter
of the flow queue parameters is the CIR of SQ, that is, the total bandwidths of CTs.
l When CTs cannot share the bandwidth of each other on the interface enabled with DS-TE, the shaping
parameter of the flow queue parameters is the bandwidth of the CT.
l When an interface supports DS-TE and is selected as the outgoing interface of a tunnel working in Up state,
you need to reset the tunnel to take the modification of the shared or unshared attribute on the interface into
effect.
----End
l The interface class queue is an interface-specific scheduling policy. You can configure according to the
network scheme.
l It is recommended that traffic of the same service type applies the same queue scheduling mode to the flow
queue and the class queue.
Procedure
Step 1 Run:
system-view
A port WRED object is created and the port WRED view is displayed.
Step 3 Run:
color { green | yellow | red } low-limit low-limit-value high-limit high-limitvalue discard-percentage discard-percentage-value
A WRED object for a class queue is configured and the upper limit, the lower limit, and the
discard probability are set for packets of different colors.
NOTE
l If you do not configure a WRED object for a class queue, the system uses the default tail-drop policy.
l You can create multiple port-wred objects to be referenced by class queues as required. The system
provides one default port-wred object. In addition, you can configure a maximum of seven port-wred
objects.
Step 4 Run:
quit
266
3 MPLS TE Configuration
Step 5 Run:
interface interface-type interface-number
A class queue is configured and a scheduling policy is set for queues of different priorities.
You can configure scheduling parameters for eight class queues on one interface.
If you do not configure a class queue template, the system uses the default class queue template.
The default class queue template contains the following parameters:
l By default, the system performs PQ on the class queues ef, cs6, and cs7.
l The system performs WFQ on the class queues be, af1, af2, af3, and af4. The scheduling
weight is 10:10:10:15:15.
l The default shaping value is the maximum bandwidth of the interface.
l The default discard policy is tail drop.
----End
Prerequisite
The configurations of the DS-TE tunnel function are complete.
Procedure
l
Run display mpls te te-class-tunnel { all | { ct0 | ct1 | ct2 | ct3 | ct4 | ct5 | ct6 | ct7 }
priority priority } command to check TE tunnels associated with the TE-classes.
Run the display interface tunnel interface-number command to check information about
traffic of each CT on the tunnel interface.
NOTE
Before viewing traffic information about each CT configured for a DS-TE tunnel, run the mpls te
lsp-tp outbound command in the tunnel interface view to limit the rate at which TE traffic is
transmitted.
----End
Example
After the configuration, run the following commands, and you can view the information.
l
Issue 02 (2011-09-10)
Run the display mpls te ds-te command on the ingress of the tunnel, and you can view
information about DS-TE.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
267
3 MPLS TE Configuration
Run the display mpls te te-class-tunnel command on the ingress of the tunnel, and you
can view TE tunnels associated with the TE-classes.
Run the display interface tunnel interface-number command on the ingress of the tunnel,
and you can view information about traffic of each CT on the tunnel.
Applicable Environment
MPLS TE Fast ReRoute (FRR) is a local protection technique.
NOTE
The RSVP-TE tunnel of SE style supports FRR; the static TE tunnel does not support FRR.
Additional bandwidth is occupied because the bypass tunnel used by the FRR needs to be preestablished. When idle network bandwidth is insufficient, the FRR should be used only for
important nodes or links.
l
When the interface where the LSP or CR-LSP resides is deleted, or when the board where the interface
resides is pulled out, the interface goes to the Stale state and becomes a staled interface. If the number
of staled interfaces on a node reaches the maximum specified in the license, the node cannot provide
FRR protection for the primary tunnel in the following cases:
l The undo mpls command is run on the outgoing interface of the primary tunnel.
l The interface board where the outgoing interface of the primary tunnel resides is pulled out or
the interface board fails.
Issue 02 (2011-09-10)
268
3 MPLS TE Configuration
During the RSVP GR, the Down event of the outgoing interface on the tunnel triggers FRR
switchover.
l
When configuring a bypass LSP, you must specify the link or node protected by the bypass LSP
and ensure that this bypass LSP does not pass through the link or node it protects. Otherwise,
the protection does not take effect.
Pre-configuration Tasks
Before configuring MPLS TE fast reroute, complete the following tasks:
l
Enabling MPLS TE and RSVP TE in the MPLS view and physical interface view of the
node along the bypass tunnel (See Enabling MPLS TE and RSVP TE.)
Data Preparation
To configure TE FRR, you need the following data.
No.
Data
Protection policy of FRR, that is, a node or a link that is the object to be protected
Context
By default, the TE FRR is disabled.
Do as follows on the ingress node along the primary LSP:
Issue 02 (2011-09-10)
269
3 MPLS TE Configuration
Procedure
Step 1 Run:
system-view
FRR is enabled.
NOTE
The primary tunnel in a tunnel protection group can be configured with the TE FRR for dual protection.
On the ingress, the tunnel protection group and TE FRR cannot be configured together. Otherwise, neither
the tunnel protection group nor TE FRR takes effect. The protection tunnel in the tunnel protection group,
however, cannot be configured with the TE FRR.
For example, assume Tunnel 1/0/0 and Tunnel 2/0/0 are MPLS TE tunnel interfaces and the ID of Tunnel
2/0/0 is 200. The mpls te protection tunnel 200 and mpls te fast-reroute commands can be run on Tunnel
1/0/0. That is, Tunnel 1/0/0 can be the primary tunnel in the protection group and the TE FRR function.
When the mpls te protection tunnel 200 command is run on Tunnel 1/0/0, the mpls te fast-reroute
command cannot be run on Tunnel 2/0/0.
Step 4 Run:
mpls te commit
Context
Do as follows on the PLR node:
Procedure
Step 1 Run:
system-view
270
3 MPLS TE Configuration
To forward traffic, the tunnel interface must be configured with an IP address. An MPLS TE tunnel is
unidirectional and no peer address exists. Therefore, a tunnel interface needs not to be assigned with
an IP address. The tunnel interface borrows the loopback interface address that is used as the LSR ID
of the local node.
Step 4 Run:
tunnel-protocol mpls te
The destination address of the bypass tunnel is configured as the LSR ID of the MP node.
Step 6 Run:
mpls te tunnel-id tunnel-id
One tunnel interface cannot serve as the bypass tunnel and backup tunnel at the same time, nor as the bypass
tunnel and the protect tunnel in a protection group. That is, the mpls te bypass-tunnel and mpls te
backup commands cannot be configured on the same interface, and the mpls te bypass-tunnel and mpls
te protection tunnel commands also cannot be configured on the same interface.
Step 10 Run:
Issue 02 (2011-09-10)
271
3 MPLS TE Configuration
The mpls te protected-interface and mpls te backup commands cannot be run on the same tunnel interface
at the same time.
Step 11 Run:
mpls te commit
Follow-up Procedure
After the bypass tunnel is configured, the route record is enabled.
One bypass tunnel protects up to six physical interfaces. After a tunnel is specified to protect a
physical interface, its corresponding LSP becomes the bypass LSP. The establishment of a
bypass LSP can be triggered when an explicit path on the PLR is configured.
During the FRR period, if the bypass LSP goes Down, the protected data cannot be forwarded
over an MPLS network; thus traffic may be interrupted and the FRR fails. Even after the bypass
LSP goes Up again, traffic cannot be forwarded. Traffic can be forwarded only after the primary
LSP is restored or re-established.
NOTE
l The mpls te fast-reroute command and the mpls te bypass-tunnel command cannot be configured
on the same interface.
l The mpls te reoptimization command and the mpls te bypass-tunnel command cannot be configured
on the same interface.
l If the FRR switching occurs, the data flow is switched from the primary LSP to the bypass LSP. During
the period when the data flow is forwarded through the bypass LSP, the bypass LSP must be in Up
state. Otherwise, the FRR fails.
Context
Do as follows on the PLR node:
Procedure
Step 1 Run:
system-view
Issue 02 (2011-09-10)
272
3 MPLS TE Configuration
Context
Do as follows on each node along the tunnel to support the FRR during the RSVP GR:
Procedure
Step 1 Run:
system-view
The timeout multiplier of the path state block (PSB) and reserved state block (RSB) is configured.
The timeout multiplier of the PSB and RSB is recommended to be equal to or greater than five
to avoid the PSB and RSB loss because of large numbers of RSVP LSPs.
----End
273
3 MPLS TE Configuration
Prerequisite
The configurations of the MPLS TE FRR function are complete.
Procedure
l
Run the display mpls lsp [ lsp-id ingress-lsr-id session-id lsp-id ] [ verbose ] command
to check information about the primary LSP.
Run the display mpls lsp attribute { bypass-inuse { inuse | not-exists | exists-notused } | bypass-tunnel tunnel-name } command to check information about the bypass
LSP or bypass tunnel.
Run the display mpls te tunnel path [ [ tunnel-name ] [ lsp-id ingress-lsr-id session-id
local-lsp-id ] | fast-reroute { local-protection-available | local-protection-inuse } ]
command to check information about paths of the primary tunnel or bypass tunnel.
----End
Applicable Environment
On the network that requires high reliability, the FRR protection is configured to improve the
reliability of the network. If the network topology is complex and multiple links need to be
configured, the configuration procedure is complicated. The Auto FRR can set up a bypass tunnel
automatically to meet the requirements to reduce the workload and improve the network
reliability.
Similar to the common MPLS TE FRR, MPLS TE Auto FRR also supports board hot pullingout protection and FRR during RSVP GR. For details, see Configuring MPLS TE FRR.
Pre-configuration Tasks
Before configuring the Auto FRR, complete the following tasks:
l
Enabling MPLS, MPLS TE and RSVP TE globally and in the physical interface view of
the node along the bypass tunnel (See Enabling MPLS TE and RSVP TE.)
Enabling CSPF on the ingress node and the transit node of the primary tunnel
Issue 02 (2011-09-10)
274
3 MPLS TE Configuration
Data Preparation
To configure the MPLS Auto FRR, you need the following data.
No.
Data
Protection policy of the Auto FRR, that is, the link or the node to be protected
Context
Do as follows on the ingress node of the tunnel:
Procedure
Step 1 Run:
system-view
The interface view of the outgoing interface of the primary tunnel is displayed.
Step 6 (Optional) Run:
mpls te auto-frr { link | node | default }
The TE Auto FRR is enabled on the outgoing interface on the ingress node of the primary tunnel.
By default, after Auto FRR is enabled globally, all the MPLS TE interfaces are automatically
configured with the mpls te auto-frr default command. To disable Auto FRR on some
interfaces, run the undo mpls te auto-frr command on these interfaces. Then, these interfaces
no longer have Auto FRR capability even if Auto FRR is enabled or is to be re-enabled globally.
Issue 02 (2011-09-10)
275
3 MPLS TE Configuration
l If the mpls te auto-frr default command is configured in the interface view, the Auto FRR capability
of the interface is consistent with the global Auto FRR capability.
l After the node protection is enabled, if the topology does not meet the requirement to set up an automatic
bypass tunnel for node protection, the penultimate hop (but not other hops) on the primary tunnel
attempts to set up an automatic bypass tunnel for link protection.
----End
Context
Do as follows on the ingress node of the primary tunnel:
Procedure
Step 1 Run:
system-view
Issue 02 (2011-09-10)
276
3 MPLS TE Configuration
NOTE
l The bypass tunnel attributes can be configured only after the mpls te fast-reroute bandwidth
command is run on the primary tunnel.
l The bandwidth of the bypass tunnel cannot be greater than the bandwidth of the primary tunnel.
l When the attributes of the automatic bypass tunnel are not configured, by default, the bandwidth of the
automatic bypass tunnel is the same as the bandwidth of the primary tunnel.
l The setup priority of the bypass tunnel cannot be higher than the holding priority. Both priorities cannot
be higher than the priority of the primary tunnel.
l When the bandwidth of the primary tunnel is changed or the FRR is disabled, the attributes of the
bypass tunnel are cleared automatically.
l On one TE tunnel interface, the bandwidth of the bypass tunnel cannot be configured together with the
multi-CT.
Step 5 Run:
mpls te commit
Context
Do as follows on the PLR node:
Procedure
Step 1 Run:
system-view
277
3 MPLS TE Configuration
if the protected LSP is restored or another LSP is established, traffic is switched to the original
LSP or the newly-established LSP.
----End
Context
Do as follows on each node along the tunnel to support the FRR during the RSVP GR:
Procedure
Step 1 Run:
system-view
The timeout multiplier of the path state block (PSB) and reserved state block (RSB) is configured.
The timeout multiplier of the PSB and RSB is recommended to be equal to or greater than five
to avoid the PSB and RSB loss because of large numbers of RSVP LSPs.
----End
Prerequisite
The configurations of the MPLS TE auto FRR function are complete.
Procedure
l
Run the display mpls te tunnel verbose command to check binding information about the
primary tunnel and the auto bypass tunnel.
Run the display mpls te tunnel-interface [ tunnel interface-number | auto-bypasstunnel tunnel-name ] command to check detailed information about the auto bypass tunnel.
Run the display mpls te tunnel path [ [ tunnel-name ] [ lsp-id ingress-lsr-id session-id
local-lsp-id ] | fast-reroute { local-protection-available | local-protection-inuse } ]
command to check path information about the primary tunnel and the auto bypass tunnel.
----End
Issue 02 (2011-09-10)
278
3 MPLS TE Configuration
Applicable Environment
A backup CR-LSP provides an end-to-end path protection over an entire LSP.
A backup CR-LSP is classified into the following types:
l
Ordinary backup CR-LSP: An ordinary backup CR-LSP is set up only after the primary
CR-LSP fails. No additional bandwidth is needed in ordinary backup mode. If the primary
CR-LSP fails, traffic switches only after the backup CR-LSP has been successfully set up.
Best-effort path: If the primary CR-LSP has failed but a backup CR-LSP fails to be
established or no backup CR-LSP is established, the system establishes a temporary CRLSP, also called a best-effort path, and switches traffic to this best-effort path. On the
network shown in Figure 3-1, the primary CR-LSP is along the path PE1 -> P2 -> P1 ->
PE2 and the backup CR-LSP is along the path PE1 -> P2 -> PE2. If both of them fail, a
best-effort path is established along the path PE1 -> P2 -> P1 -> PE2.
P1
PE1
P2
PE2
Primary path
Secondary path
Best-effort path
Pre-configuration Tasks
Before configuring CR-LSP backup, complete the following tasks:
Issue 02 (2011-09-10)
279
3 MPLS TE Configuration
Enabling MPLS, MPLS TE, and RSVP TE globally and in the interface view of each node
along a backup CR-LSP (See Enabling MPLS TE and RSVP TE.)
Data Preparation
To configure CR-LSP backup, you need the following data.
No.
Data
Backup mode
Context
By default, the CR-LSP backup is not enabled. After the CR-LSP backup is configured on the
ingress of a tunnel, the system automatically selects the path of the backup CR-LSP without
manual interruption.
Do as follows on the ingress node of the primary tunnel:
Procedure
Step 1 Run:
system-view
A primary CR-LSP cannot function as a bypass tunnel or a backup CR-LSP for another CR-LSP. That is,
the mpls te protected-interface or mpls te bypass-tunnel are mutually exclusive.
280
3 MPLS TE Configuration
NOTE
When an explicit path is used to set up a hot-standby CR-LSP, it cannot completely overlap the path of the
primary CR-LSP; otherwise, the hot-standby CR-LSP cannot protect the primary CR-LSP.
Context
The path overlapping function can be configured for hot-standby CR-LSPs. This function allows
a hot-standby CR-LSP to use links of a primary CR-LSP. After the hot-standby CR-LSP is
established, it can protect traffic on the primary CR-LSP.
Procedure
Step 1 Run:
system-view
The path overlapping function takes effect only on hot-standby CR-LSPs to be established.
It allows a hot-standby CR-LSP to use some links of the primary CR-LSP. This hot-standby CR-LSP can
use all links of the primary CR-LSP if an explicit path is configured for it.
Issue 02 (2011-09-10)
281
3 MPLS TE Configuration
Step 4 Run:
mpls te commit
Context
The system provides three prioritized attribute templates for a hot-standby backup CR-LSP and
three for an ordinary backup CR-LSP. If an existing backup CR-LSP is set up using a lowerpriority attribute template, the system automatically attempts to set up a new backup CR-LSP
using a higher-priority attribute template.
When a specified attribute template is locked, the system does not use a higher-priority attribute
template to re-establish a CR-LSP even though the existing CR-LSP is set up using a lowerpriority attribute template. This avoids unnecessary traffic switchover and thus saves system
resources.
Do as follows on the ingress of the primary CR-LSP:
Procedure
Step 1 Run:
system-view
Step 5 Run one of the following commands to lock the attribute template that is used by an ordinary
backup CR-LSP or a hot-standby CR-LSP:
Issue 02 (2011-09-10)
282
3 MPLS TE Configuration
For the attribute template that is used to set up an ordinary backup CR-LSP, run:
mpls te backup ordinary-lsp-constraint lock
For the attribute template that is used to set up a hot-standby CR-LSP, run:
mpls te backup hotstandby-lsp-constraint lock
Step 6 Run:
mpls te commit
Follow-up Procedure
If you run the undo mpls te backup ordinary-lsp-constraint lock command or the undo mpls
te backup hotstandby-lsp-constraint lock command to unlock the attribute template, the
system continues trying a higher-priority attribute template to set up a backup CR-LSP.
Context
With the dynamic bandwidth function, a hot-standby CR-LSP occupies bandwidth resources
only when taking over traffic from a faulty primary CR-LSP, rather than when the primary CRLSP works normally.
You can configure the dynamic bandwidth function for a hot-standby CR-LSP on the ingress of
a primary CR-LSP.
Procedure
l
Run:
system-view
Run:
interface tunnel interface-number
Run:
tunnel-protocol mpls te
Run:
mpls te backup hot-standby dynamic-bandwidth
283
5.
3 MPLS TE Configuration
Run:
mpls te commit
Run:
system-view
Run:
interface tunnel interface-number
Run:
tunnel-protocol mpls te
Run:
mpls te backup hotstandby-lsp-constraint dynamic-bandwidth
Run:
mpls te commit
Follow-up Procedure
After the preceding configuration, the system can establish a new hot-standby CR-LSP using
the required bandwidth according to the make-before-break mechanism to replace the hotstandby CR-LSP with bandwidth at 0 bit/s.
You can run the undo mpls te backup hot-standby dynamic-bandwidth command to delete
the dynamic bandwidth function for the hot-standby CR-LSP, thus allowing the hot-standby CRLSP to re-occupy bandwidth.
Context
In best-effort mode, do as follows on the ingress node of the TE tunnel:
Procedure
Step 1 Run:
system-view
284
3 MPLS TE Configuration
Step 2 Run:
interface tunnel interface-number
The mpls te backup ordinary best-effort command and the mpls te backup ordinary command cannot
be configured on the same tunnel interface.
Follow-up Procedure
After a best-effort LSP is configured, the device triggers the setup of a best-effort LSP when
both the primary LSP and the backup LSP fail.
Procedure
l
Run the display mpls te hot-standby state { all [ verbose ] | interface tunnel interfacenumber } command to check the hot standby status.
Run the display mpls te tunnel [ destination ip-address ] [ lsp-id ingress-lsr-id sessionid local-lsp-id ] [lsr-role { all | egress | ingress | remote | transit } ] [ name tunnelname ] [ { incoming-interface | interface | outgoing-interface } interface-type interfacenumber ] [ te-class0 | te-class1 | te-class2 | te-class3 | te-class4 | te-class5 | te-class6 | teclass7 ] [ verbose ] command to check information about the tunnel.
----End
Issue 02 (2011-09-10)
285
3 MPLS TE Configuration
Example
In hot standby mode, after the configuration, run the display mpls te tunnel-interface
command, and you can view information about a backup CR-LSP.
[HUAWEI] display mpls te tunnel-interface
================================================================
Tunnel1/0/0
================================================================
Tunnel State Desc
: UP
Active LSP
: Hot-Standby LSP
Session ID
: 100
Ingress LSR ID
: 4.4.4.4
Egress LSR ID: 3.3.3.3
Admin State
: UP
Oper State
: UP
Primary LSP State
: DOWN
Main LSP State
: SETTING UP
Hot-Standby LSP State : UP
Main LSP State
: READY
LSP ID : 32769
Modify LSP State
: SETTING UP
Run the display mpls te hot-standby state command, and you can view information about the
hot standby.
<HUAWEI> display mpls te hot-standby state interface Tunnel 1/0/0
---------------------------------------------------------------Verbose information about the Tunnel1/0/0 hot-standby state
---------------------------------------------------------------session id
: 100
main LSP token
: 0x100201a
hot-standby LSP token
: 0x100201b
HSB switch result
: Best-Effort LSP
WTR
: 15s
Run the display mpls te tunnel to check information about the tunnel.
<HUAWEI> display mpls te tunnel verbose
No
: 1
Tunnel-Name
: Tunnel1/0/0
TunnelIndex
: 0
LSP Index
: 1024
Session ID
: 100
LSP ID
: 1
Lsr Role
: Ingress
LSP Type
: Primary
Ingress LSR ID
: 1.1.1.1
Egress LSR ID
: 2.2.2.2
In-Interface
: Out-Interface
: Pos1/0/0
Sign-Protocol
: Static CR
Resv Style
:
IncludeAnyAff
: 0x0
ExcludeAnyAff
: 0x0
IncludeAllAff
: 0x0
LspConstraint
: 1
ER-Hop Table Index
: AR-Hop Table Index: C-Hop Table Index
: PrevTunnelIndexInSession: NextTunnelIndexInSession: PSB Handle
: 0
Created Time
: 2008/04/03 19:31:14
-------------------------------DS-TE Information
-------------------------------Bandwidth Reserved Flag : Unreserved
CT0 Bandwidth(Kbit/sec) : 0
CT1 Bandwidth(Kbit/sec): 0
CT2 Bandwidth(Kbit/sec) : 0
CT3 Bandwidth(Kbit/sec): 0
CT4 Bandwidth(Kbit/sec) : 0
CT5 Bandwidth(Kbit/sec): 0
CT6 Bandwidth(Kbit/sec) : 0
CT7 Bandwidth(Kbit/sec): 0
Setup-Priority
: 0
Hold-Priority
: 0
-------------------------------FRR Information
-------------------------------Primary LSP Info
TE Attribute Flag
: 0xe3
Protected Flag
: 0x04
Bypass In Use
: Not Exists
Issue 02 (2011-09-10)
286
3 MPLS TE Configuration
Bypass Tunnel Id
: BypassTunnel
: Bypass Lsp ID
: FrrNextHop
: ReferAutoBypassHandle
: FrrPrevTunnelTableIndex : FrrNextTunnelTableIndex: Bypass Attribute(Not configured)
Setup Priority
: Hold Priority
: HopLimit
: Bandwidth
: IncludeAnyGroup
: ExcludeAnyGroup
: IncludeAllGroup
: Bypass Unbound Bandwidth Info(Kbit/sec)
CT0 Unbound Bandwidth
: CT1 Unbound Bandwidth: CT2 Unbound Bandwidth
: CT3 Unbound Bandwidth: CT4 Unbound Bandwidth
: CT5 Unbound Bandwidth: CT6 Unbound Bandwidth
: CT7 Unbound Bandwidth: -------------------------------BFD Information
-------------------------------NextSessionTunnelIndex : PrevSessionTunnelIndex: NextLspId
: PrevLspId
: -
Application Environment
To protect important links and nodes, you can configure the TE FRR bypass tunnel and the endto-end backup CR-LSP together. The backup CR-LSP is more reliable than the TE FRR bypass
tunnel. Therefore, to improve the security of the tunnel, you are recommended to configure
synchronization of the TE FRR bypass tunnel and the backup CR-LSP.
l
Issue 02 (2011-09-10)
287
3 MPLS TE Configuration
If the backup CR-LSP is in the Down state, the processing of hot standby is the same
as the processing of ordinary backup.
When the primary CR-LSP is Up and the hot standby CR-LSP is also in the Up state, more
bandwidth resources are needed. The ordinary CR-LSP is set up only when the primary CR-LSP
is in the FRR-in-use state. That is, when the primary CR-LSP works normally, no more
bandwidth resources are needed. Therefore, the ordinary backup is recommended.
Pre-configuration Tasks
Before configuring synchronization of the bypass tunnel and the backup CR-LSP, you need to
complete the following tasks:
l
Configuring manual MPLS TE FRR or MPLS TE Auto FRR (See the section Configuring
MPLS TE FRR or the section Configuring MPLS Auto TE FRR.)
Configuring the backup CR-LSP (except for the best-effort path) in either hot standby mode
or ordinary backup mode (See the section Configuring CR-LSP Backup.)
Data Preparation
To configure synchronization of the bypass tunnel and the backup CR-LSP, you need the
following data.
No.
Data
Protection policy of TE FRR, that is, to protect the link or the node
Backup mode
Context
Do as follows on the ingress LSR of the primary tunnel:
NOTE
Before the configuration, you must configure the end-to-end protection (except for the best-effort path) in
either hot standby mode or ordinary backup mode and the TE FRR partial protection.
Procedure
Step 1 Run:
system-view
288
3 MPLS TE Configuration
Step 2 Run:
interface tunnel interface-number
When the primary CR-LSP is faulty (that is, the primary CR-LSP is in FRR-in-use state), the
system starts the TE FRR bypass tunnel and tries to restore the primary CR-LSP. At the same
time, the system tries to set up a backup CR-LSP.
Step 4 Run:
mpls te commit
Prerequisite
All configurations of synchronization of the bypass tunnel and the backup CR-LSP are complete.
Procedure
l
Run the display mpls te tunnel-interface [ tunnel interface-number | auto-bypasstunnel tunnel-name ] command, and you can view information about the tunnel.
----End
Applicable Environment
When an RSVP node performs an active/standby switchover, an RSVP adjacency relationship
between the local node and its neighbor is torn down because of signaling protocol timeout,
resulting in removal of a CR-LSP and a temporary traffic interruption.
Issue 02 (2011-09-10)
289
3 MPLS TE Configuration
RSVP GR resolves the preceding problem. The RSVP GR mechanism allows the adjacency
relationship to be reestablished between neighbors without tearing down RSVP sessions.
On the NE80E/40E, FRR switching is performed during the RSVP GR process. FRR protects
traffic if a switchover is performed on the PLR node, PLR upstream node, MP, or MP
downstream node and the outgoing interface of the PLR primary tunnel fails, reducing the fault
period.
NOTE
When FRR is performed during the RSVP GR process, setting the timeout multiplier in the PSB and RSB
to a value equal to or greater than five is recommended, preventing PSB and RSB loss due to oversized
data. For detailed configurations, see (Optional) Modifying the PSB and RSB Timeout Multiplier.
Pre-configuration Tasks
Before configuring RSVP GR, complete the following tasks:
l
Data Preparation
To configure RSVP GR, you need the following data.
No.
Data
IGP parameters:
l IS-IS: IS-IS process ID, Network Entity Title (NET), and IS-IS level of each node
l OSPF: OSPF process ID and AS number
Context
Do as follows on a GR node and its neighboring nodes:
Procedure
Step 1 Run:
system-view
290
3 MPLS TE Configuration
Step 2 Run:
mpls
Context
Do as follows on a GR node:
Procedure
Step 1 Run:
system-view
The RSVP GR function and the function of supporting RSVP GR on a neighbor are enabled.
By default, the RSVP GR function and RSVP GR support function are disabled.
----End
Issue 02 (2011-09-10)
291
3 MPLS TE Configuration
Context
RSVP GR takes effect on the RSVP GR-enabled neighbor automatically after the neighbor is
enabled with RSVP full GR. If the GR node's neighbor is a GR node, do not perform the following
steps. If the GR node's neighbor is not a GR node, do as follows:
Procedure
Step 1 Run:
system-view
RSVP-TE is enabled.
Step 4 Run:
mpls rsvp-te hello
Context
If TE FRR is deployed, a hello session is required between a PLR and an MP. Do as follows on
the PLR and MP:
Procedure
Step 1 Run:
system-view
292
3 MPLS TE Configuration
Step 2 Run:
mpls
RSVP-TE is enabled.
Step 4 Run:
mpls rsvp-te hello
Context
After an active/standby switchover starts, an RSVP GR node has an RSVP smoothing period,
during which the data plane continues forwarding data if the control plane is not restored. After
RSVP smoothing is completed, a restart timer is started.
Restart timer value = Basic time + Number of ingress LSPs x 60 ms
In this formula, the default basic time is 90 seconds and is configurable by using a command
line, and the number of LSPs is the number of LSPs with the local node being the ingress.
After the restart timer expires, the recovery timer is started.
Recovery timer = Restart time + Total number of LSPs x 40 ms
Do as follows on the GR node to modify the basic time:
Procedure
Step 1 Run:
system-view
Issue 02 (2011-09-10)
293
3 MPLS TE Configuration
Procedure
l
Run the display mpls rsvp-te graceful-restart command to check the status of the local
RSVP GR.
Run the display mpls rsvp-te graceful-restart peer [ { interface interface-type interfacenumber | node-id } [ ip-address ] ] command to check the status of RSVP GR on a neighbor.
----End
Example
Run the display mpls rsvp-te graceful-restart command on a restarted node. If "GR-Self GRSupport" is displayed in the Graceful-Restart Capability field, it means that the local device has
the RSVP GR function. During the GR process, in the output of the display mpls rsvp-te
graceful-restart command, "Restart time going on" or "Recovery time going on" is displayed
in the GR Status field.
Run the display mpls rsvp-te graceful-restart peer command on the restarted node.
Information displayed in the Neighbor Capability field has specific meanings:
l
Can Do Self GR: means that the neighbor node is enabled with the RSVP GR capability.
Can Support GR: means that the neighbor node is enabled with the RSVP GR supporting
capability.
Both "Can Do Self GR" and "Can Support GR": mean that the neighbor node is enabled
with the RSVP GR function and the RSVP GR support function.
Run the ping lsp te tunnel command on the neighbor node and immediately run the slave
switchover command in the system view on the restarted node, and you can view that data
forwarded through the TE tunnel is not interrupted during GR.
294
3 MPLS TE Configuration
Applicable Environment
BFD detects the following types of CR-LSPs:
l
Static CR-LSP
RSVP CR-LSP
BFD for static CR-LSP and BFD for RSVP CR-LSP can be used to replace MPLS OAM to
detect the MPLS TE tunnel protection groups and trigger primary/backup CR-LSP switchover.
BFD for CR-LSP is applicable to the hot-standby CR-LSP. It detects the primary and backup
CR-LSPs and triggers CR-LSPs switchover.
For details about MPLS OAM configuration, refer to the chapter "MPLS OAM Configuration"
in the Configuration Guide - MPLS.
NOTE
For the same CR-LSP, MPLS OAM and BFD cannot be configured simultaneously.
In the scenario that static BFD for CR-LSP is applied and the BFD status is Up, if the tunnel interface to
which CR-LSP belongs is shut down, the BFD status remains Up.
BFD for LSP can function properly though the forward path is an LSP and the backward path is an IP link.
The forward path and the backward path must be established over the same link; otherwise, if a fault occurs,
BFD cannot identify the faulty path. Before deploying BFD, ensure that the forward and backward paths
are over the same link so that BFD can correctly identify the faulty path.
Pre-configuration Tasks
Before configuring static BFD for CR-LSP, complete the following task:
l
For details about the configuration of the MPLS TE tunnel protection group for the MPLS TE tunnel, refer
to the chapter "MPLS OAM Configuration" in the HUAWEI NetEngine80E/40E Router Configuration
Guide - MPLS.
Data Preparation
To configure static BFD for CR-LSP, you need the following data.
Issue 02 (2011-09-10)
No.
Data
Backward channel (IP link, dynamic LSP, static LSP, or MPLS TE tunnel)
295
3 MPLS TE Configuration
Context
Do as follows on the ingress node and egress node of the tunnel:
Procedure
Step 1 Run:
system-view
Context
Do as follows on the ingress node of a tunnel:
Procedure
Step 1 Run:
system-view
BFD is configured to detect the primary or backup CR-LSP bound to a specified tunnel.
The parameter backup means that backup CR-LSPs are to be checked.
Step 3 Run:
discriminator local discr-value
296
3 MPLS TE Configuration
The local minimum interval at which BFD packets are sent is set.
The default value is specified in the license.
Step 6 (Optional) Run:
min-rx-interval interval
The local minimum interval at which BFD packets are received is set.
The default value is specified in the license.
Step 7 (Optional) Run:
detect-multiplier multiplier
The system is enabled to change the port status table (PST) when the BFD status changes.
When the BFD status changes, BFD notifies the application of the change, triggering a fast
switchover between the primary and bypass CR-LSPs.
Step 9 Run:
commit
Actual local sending interval = MAX { Configured local sending interval, Configured remote receiving
interval }
Actual local receiving interval = MAX { Configured remote sending interval, Configured local receiving
interval }
Actual local detection interval = Actual local receiving interval x Configured remote detection multiplier
For example:
l The local sending and receiving intervals are set to 200 ms and 300 ms respectively and the detection
multiplier is set to 4.
l The remote sending and receiving intervals are set to 100 ms and 600 ms respectively and the detection
multiplier is set to 5.
Then,
l Actual local sending interval = MAX {200 ms, 600 ms} = 600 ms; Actual local receiving interval =
MAX {100 ms, 300 ms} = 300 ms; Actual local detection interval is 300 ms x 5 = 1500 ms.
l Actual remote sending interval = MAX {100 ms, 300 ms} = 300 ms; Actual remote receiving interval
= MAX {200 ms, 600 ms} = 600 ms; Actual remote detection interval is 600 ms x 4 = 2400 ms.
----End
297
3 MPLS TE Configuration
Context
Do as follows on the egress node of a tunnel:
Procedure
Step 1 Run:
system-view
Step 3 Run:
discriminator local discr-value
The minimum interval at which the local end sends BFD packets is set.
The default value is specified by the license.
Step 6 (Optional) Run:
min-rx-interval interval
The minimum interval at which the local end receives BFD packets is set.
The default value is specified by the license.
Step 7 (Optional) Run:
detect-multiplier multiplier
298
3 MPLS TE Configuration
Step 8 Run:
commit
Procedure
l
Run the display bfd configuration mpls-te interface tunnel interface-number te-lsp
[ verbose ] command to check BFD configurations on the ingress.
Run the display bfd session mpls-te interface tunnel interface-number te-lsp
[ verbose ] command to check BFD session configurations on the ingress.
Run the following commands to check BFD session configurations on the egress:
Run the display bfd session all [ for-ip | for-lsp | for-te ] [ slot slot-id | verbose ]
command to check all the BFD configurations.
Run the display bfd session static [ for-ip | for-lsp | for-te ] [ slot slot-id | verbose ]
command to check the static BFD configurations.
Run the display bfd session peer-ip peer-ip [ vpn-instance vpn-instance-name ]
[ slot slot-id | verbose ] command to check the configurations of BFD with the backward
channel being an IP link.
Run the display bfd session static-lsp lsp-name [ verbose ] command to check the
configurations of BFD with the backward channel being a static LSP.
Issue 02 (2011-09-10)
299
3 MPLS TE Configuration
Run the display bfd session ldp-lsp peer-ip peer-ip [ interface interface-type
interface-number ] [ verbose ] command to check the configurations of BFD with the
backward channel being an LDP LSP.
Run the display bfd session mpls-te interface tunnel interface-number te-lsp
[ verbose ] command to check the configurations of BFD with the backward channel
being a CR-LSP.
Run the display bfd session mpls-te interface tunnel interface-number [ verbose ]
command to check the configurations of BFD with the backward channel being a TE
tunnel.
l
----End
Example
After the configuration, run the preceding commands to check BFD session status, and you can
view that the BFD session is Up.
Applicable Environment
BFD for TE allows applications such as VPN FRR or VLL FRR to fast switch traffic if the
primary tunnel fails, preventing service interruption.
Issue 02 (2011-09-10)
300
3 MPLS TE Configuration
NOTE
Pre-configuration Tasks
Before configuring static BFD for TE, complete the following task:
l
Data Preparation
To configure static BFD for TE, you need the following data.
No.
Data
Backward channel (IP link, dynamic LSP, static LSP, or MPLS TE tunnel)
Context
Do as follows on the ingress and egress of a tunnel:
Procedure
Step 1 Run:
system-view
301
3 MPLS TE Configuration
Context
Do as follows on the ingress of a tunnel:
Procedure
Step 1 Run:
system-view
The local minimum interval at which BFD packets are sent is set.
The default value is determined by the license.
Step 6 (Optional) Run:
min-rx-interval interval
The local minimum interval at which BFD packets are received is set.
The default value is specified in the license.
Step 7 (Optional) Run:
detect-multiplier multiplier
Issue 02 (2011-09-10)
302
3 MPLS TE Configuration
If the status of the tunnel to be checked is Down, the BFD session cannot be set up.
Actual local sending interval = MAX { Configured local sending interval, Configured remote receiving
interval }
Actual local receiving interval = MAX { Configured remote sending interval, Configured local receiving
interval }
Actual local detection interval = Actual local receiving interval x Configured remote detection multiplier.
For example:
l The local sending and receiving intervals are set to 200 ms and 300 ms respectively and the detection
multiplier is set to 4.
l The remote sending and receiving intervals are set to 100 ms and 600 ms respectively and the detection
multiplier is set to 5.
Then,
l Actual local sending interval = MAX {200 ms, 600 ms} = 600 ms; Actual local receiving interval =
MAX {100 ms, 300 ms} = 300 ms; actual local detection interval is 300 ms x 5 = 1500 ms.
l Actual remote sending interval = MAX {100 ms, 300 ms} = 300 ms; Actual remote receiving interval
= MAX {200 ms, 600 ms} = 600 ms; Actual remote detection interval is 600 ms x 4 = 2400 ms.
----End
Context
Do as follows on the egress node of a tunnel:
Procedure
Step 1 Run:
system-view
303
3 MPLS TE Configuration
Step 3 Run:
discriminator local discr-value
The local minimum interval at which BFD packets are sent is set.
The default value is determined by the License.
Step 6 (Optional) Run:
min-rx-interval interval
The local minimum interval at which BFD packets are received is set.
The default value is specified in the license.
Step 7 (Optional) Run:
detect-multiplier multiplier
Procedure
l
Issue 02 (2011-09-10)
304
3 MPLS TE Configuration
Run the display bfd configuration ldp-lsp peer-ip peer-ip nexthop nexthop [
interface interface-type interface-number ] [ verbose ] command to check the
configurations of BFD with the backward channel being an LDP LSP.
Run the display bfd configuration mpls-te interface tunnel interface-number te-lsp
[ verbose ] command to check the configurations of BFD with the backward channel
being a CR-LSP.
Run the display bfd configuration mpls-te interface tunnel interface-number
[ verbose ] command to check the configurations of BFD with the backward channel
being a TE tunnel.
l
Run the display bfd session mpls-te interface tunnel interface-number [ verbose ]
command to check BFD session configurations on the ingress.
Run the following commands to check BFD session configurations on the egress:
Run the display bfd session all [ for-ip | for-lsp | for-te ] [ slot slot-id | verbose ]
command to check all BFD configurations.
Run the display bfd session static [ for-ip | for-lsp | for-te ] [ slot slot-id | verbose ]
command to check the configurations of static BFD.
Run the display bfd session peer-ip peer-ip [ vpn-instance vpn-instance-name ]
[ slot slot-id | verbose ] command to check the configurations of BFD with the backward
channel being an IP link.
Run the display bfd session static-lsp lsp-name [ verbose ] command to check the
configurations of BFD with the backward channel being a static LSP.
Run the display bfd session ldp-lsp peer-ip peer-ip [ interface interface-type
interface-number ] [ verbose ] command to check the configurations of BFD with the
backward channel being an LDP LSP.
Run the display bfd session mpls-te interface tunnel interface-number te-lsp
[ verbose ] command to check the configurations of BFD with the backward channel
being a CR-LSP.
Run the display bfd session mpls-te interface tunnel interface-number [ verbose ]
command to check the configurations of BFD with the backward channel being a TE
tunnel.
----End
Issue 02 (2011-09-10)
305
3 MPLS TE Configuration
Example
After the configuration, run the preceding commands to check BFD session status, and you can
view that the BFD session is Up.
Applicable Environment
Compared with static BFD, dynamically creating BFD sessions simplifies configurations and
reduces configuration errors.
BFD detects faults in the following CR-LSPs:
l
Static CR-LSP
RSVP CR-LSP
Currently, dynamic BFD for CR-LSP cannot detect faults in the entire TE tunnel.
NOTE
MPLS OAM and BFD cannot be configured together for one CR-LSP.
If a dynamic BFD session for CR-LSP is Up but the tunnel interface of the detected CR-LSP is shut down,
the BFD session is still Up.
BFD for LSP can function properly though the forward path is an LSP and the backward path is an IP link.
The forward path and the backward path must be established over the same link; otherwise, if a fault occurs,
BFD cannot identify the faulty path. Before deploying BFD, ensure that the forward and backward paths
are over the same link so that BFD can correctly identify the faulty path.
Pre-configuration Tasks
Before configuring dynamic BFD for CR-LSP, complete the following tasks:
l
Data Preparation
To configure dynamic BFD for CR-LSP, you need the following data.
Issue 02 (2011-09-10)
No.
Data
306
3 MPLS TE Configuration
Context
Do as follows on the ingress and the egress of a TE tunnel:
Procedure
Step 1 Run:
system-view
Context
Enabling the capability of dynamically creating BFD sessions on a TE tunnel can be
implemented in either of the following methods:
l
Enabling MPLS TE BFD Globally if most TE tunnels on the ingress need to dynamically
create BFD sessions
Enabling MPLS TE BFD on the Tunnel Interface if certain TE tunnels on the ingress
need to dynamically create BFD sessions
Procedure
Do as follows on the ingress:
1.
Run:
system-view
Run:
mpls
Issue 02 (2011-09-10)
307
3 MPLS TE Configuration
Run:
mpls te bfd enable
(Optional) Block the capability of dynamically creating BFD sessions for TE on the
tunnel interfaces of the TE tunnels that do not need dynamic BFD for TE.
(1) Run:
interface tunnel interface-number
Run:
system-view
Run:
interface tunnel interface-number
Run:
mpls te bfd enable
Run:
mpls te commit
308
3 MPLS TE Configuration
Context
Do as follows on the egress:
Procedure
Step 1 Run:
system-view
Context
BFD parameters are adjusted on the ingress of a TE tunnel either of the following modes:
l
Adjusting Global BFD Parameters if most TE tunnels on the ingress use the same BFD
parameters
Actual local sending interval = MAX { Configured local sending interval, Configured remote receiving
interval }
Actual local receiving interval = MAX { Configured remote sending interval, Configured local receiving
interval }
Actual local detection interval = Actual local receiving interval x Configured remote detection multiplier
On the egress of the TE tunnel enabled with the capability of passively creating BFD sessions, the default
values of the receiving interval, sending interval and detection multiplier cannot be adjusted. The default
values of these three parameters are the minimum configurable values on the ingress. Therefore, the BFD
detection interval on the ingress and that on the egress of a TE tunnel are as follows:
l Actual detection interval on the ingress = Configured receiving interval on the ingress x 3
l Actual detection interval on the egress = Configured sending interval on the ingress x Configured
detection multiplier on the ingress
Issue 02 (2011-09-10)
309
3 MPLS TE Configuration
Procedure
l
Run:
system-view
Run:
mpls
Run:
mpls te bfd { min-tx-interval tx-interval | min-rx-interval tx-interval |
detect-multiplier multiplier }*
Run:
system-view
Run:
interface tunnel interface-number
Run:
mpls te bfd { min-tx-interval tx-interval | min-rx-interval rx-interval |
detect-multiplier multiplier }*
Run:
mpls te commit
Procedure
l
Run the display bfd configuration dynamic [ verbose ] command to check the
configuration of dynamic BFD on the ingress.
Run the display bfd configuration passive-dynamic [ peer-ip peer-ip remotediscriminator discriminator ] [ verbose ] command to check the configuration of dynamic
BFD on the egress.
Run the display bfd session dynamic [slot slot-id ] [ verbose ] command to check
information about the BFD session on the ingress.
Issue 02 (2011-09-10)
310
3 MPLS TE Configuration
Run the display mpls bfd session [ statistics | [ protocol { ldp | cr-static | rsvp-te } ] |
[ outgoing-interface interface-type interface-number ] | [ nexthop ip-address ] | [ fec fecaddress ] | verbose | monitor ] command to check information about the MPLS BFD
session.
----End
Example
Run the display bfd session all verbose command on the ingress, and you can view that the
status of the BFD sessions is Up and the links bound to the sessions are TE LSPs.
Run the display bfd session passive-dynamic verbose command on the egress, and you can
view that the BFD session created on the egress is a multi-hop BFD session bound to the peer
IP address.
Applicable Environment
BFD for RSVP is applied to a scenario where TE FRR is used and a Layer 2 device exists on
the primary LSP between a PLR and its downstream neighbors. On a network where GR is
enabled on the PLR and MP, BFD for RSVP is also recommended.
By default, the interval at which RSVP Hello messages are sent is 3 seconds. The interval at
which a neighbor is declared Down is three times the interval at which RSVP Hello messages
are sent. This allows devices to detect a fault in an RSVP neighbor at seconds level.
If a Layer 2 device exists on a link between RSVP neighboring nodes, the neighboring node
cannot rapidly detect the fault after the link fails, resulting in a great loss of data.
BFD detects faults at millisecond level in protected links or nodes. BFD for RSVP rapidly detects
faults in an RSVP neighbor, allowing packets to switch to a backup LSP rapidly.
Issue 02 (2011-09-10)
311
3 MPLS TE Configuration
NOTE
BFD for LSP can function properly though the forward path is an LSP and the backward path is an IP link.
The forward path and the backward path must be established over the same link; otherwise, if a fault occurs,
BFD cannot identify the faulty path. Before deploying BFD, ensure that the forward and backward paths
are over the same link so that BFD can correctly identify the faulty path.
Pre-configuration Tasks
Before configuring BFD for RSVP, complete the following tasks:
l
Data Preparation
To configure BFD for RSVP, you need the following data.
No.
Data
When modifying BFD session parameters, select the parameters for the BFD sessions shared by
different protocols as follows:
l
If the interval at which BFD packets are sent, interval at which BFD packets are received,
and local detection multiplier are set globally and on the interfaces of a node, the parameters
configured on the interfaces are used by a local RSVP protocol.
If BFD for RSVP and other protocols share a BFD session on a node, the node selects the
smallest time parameters among all protocols as the local parameters.
Context
Do as follows on the two RSVP neighboring nodes between which a Layer 2 device resides:
Issue 02 (2011-09-10)
312
3 MPLS TE Configuration
Procedure
Step 1 Run:
system-view
Context
Enabling BFD for RSVP in the following manners:
l
Enabling BFD for RSVP Globally if most RSVP interfaces on a node need BFD for
RSVP.
Enabling BFD for RSVP on the RSVP Interface if certain RSVP interfaces on a node
need BFD for RSVP.
Procedure
Do as follows on both RSVP neighboring nodes between which a Layer 2 device resides:
1.
Run:
system-view
Run:
mpls
Run:
mpls rsvp-te bfd all-interfaces enable
(Optional) Block BFD for RSVP on the RSVP interfaces that need not BFD for RSVP.
(1) Run:
interface interface-type interface-number
Issue 02 (2011-09-10)
313
3 MPLS TE Configuration
Run:
system-view
Run:
interface interface-type interface-number
Run:
mpls rsvp-te bfd enable
Context
BFD for RSVP parameters are adjusted on the ingress of a TE tunnel either of the following
modes:
l
Adjusting Global BFD Parameters if most RSVP interfaces on a node use the same BFD
parameters
Procedure
Do as follows on the two RSVP neighboring nodes between which a Layer 2 device resides:
1.
Run:
system-view
Run:
mpls
Run:
mpls rsvp-te bfd all-interfaces { min-tx-interval tx-interval | min-rxinterval rx-interval | detect-multiplier multiplier }*
314
3 MPLS TE Configuration
NOTE
Run:
system-view
Run:
interface interface-type interface-number
Run:
mpls rsvp-te bfd { min-tx-interval tx-interval | min-rx-interval rxinterval | detect-multiplier multiplier }*
Procedure
l
Run the display mpls rsvp-te bfd session { all | interface interface-type interfacenumber | peer ip-address } [ verbose ] command to check information about the BFD for
RSVP session.
Run the display mpls rsvp-te peer [ interface interface-type interface-number ] command
to check information about the RSVP neighbor.
Run the display mpls rsvp-te statistics { global | interface [ interface-type interfacenumber ] } command to check statistics about RSVP-TE.
----End
Issue 02 (2011-09-10)
315
3 MPLS TE Configuration
Example
If the configurations are successful, you can view that the status of the BFD session for RSVP
is Up.
NOTE
Information about the BFD session can be checked only after the BFD session parameters are configured
and the session is created successfully.
Applicable Environment
On an MPLS network, if LDP is enabled on the edge LSR and TE is supported only on the core
LSR, LDP over TE is recommended. In LDP over TE, a TE tunnel is considered as one hop
along the entire LDP LSP.
NOTE
On a network deployed with LDP over TE, static or dynamic BFD is used to detects faults in an LDP LSP.
If the shutdown command is run on a tunnel interface through which the LDP LSP passes when the BFD
status is Up, the BFD status remains Up.
Pre-configuration Tasks
Before configuring LDP over TE, complete the following tasks:
l
Data Preparation
To configure LDP over TE, you need the following data.
Issue 02 (2011-09-10)
No.
Data
316
3 MPLS TE Configuration
Context
The routing protocol performs bidirectional detection on a link. When using the forwarding
adjacency to advertise LSP links to other nodes, configure another tunnel for transferring data
packets in the reverse direction. Then, enable the forwarding adjacency on these two tunnels.
NOTE
Procedure
Step 1 Run:
system-view
Step 5 Run:
mpls te commit
317
3 MPLS TE Configuration
Context
Do as follows on the ingress and egress of a TE tunnel:
Procedure
Step 1 Run:
system-view
Context
Do as follows on the ingress and egress of a TE tunnel:
Procedure
Step 1 Run:
system-view
318
3 MPLS TE Configuration
Step 3 Run:
lsp-trigger { all | host | ip-prefix ip-prefix-name | none }
Procedure
Step 1 Run the display mpls ldp lsp [ all | [ vpn-instance vpn-instance-name ] destination-address
mask-length ] command to check information about the tunnel interface on the ingress of an
LDP LSP.
----End
Example
After the configurations are successful, run the display mpls ldp lsp command, and you can
view that LDP LSP over TE is added.
Prerequisite
The configurations of the TE tunnel detection are complete.
Procedure
l
Run the ping lsp [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m interval | -r
reply-mode | -s packet-size | -t time-out | -v ] * te tunnel interface-number [ hotstandby ] [ draft6 ] command to check the connectivity of the TE tunnel between the
ingress and egress.
Run the tracert lsp [ -a source-ip | -exp exp-value | -h ttl-value | -r reply-mode | -t timeout ] * te tunnel interface-number [ hot-standby ] [ draft6 ] command to trace the hops
of a TE tunnel.
----End
Example
After configuring MPLS TE, run the ping lsp command on the ingress of the TE tunnel, and
you can view whether or not the ingress pings the egress. If the ping fails, run the tracert lsp
Issue 02 (2011-09-10)
319
3 MPLS TE Configuration
command to locate the fault. If the hot-standby parameter is specified, the hot-standby CR-LSP
can be tested. If draft6 is specified, the command is implemented in compliance with draft-ietfmpls-lsp-ping-06. By default, the command is implemented in compliance with RFC 4379.
Context
After configuring MPLS TE, you can use NQA to check the connectivity and jitter of the TE
tunnel. For detailed configurations, see the chapter "NQA Configuration" in the HUAWEI
NetEngine80E/40E Router Configuration Guide - System Management.
Context
If an RSVP-TE tunnel interface goes Down, you can run the following command to view
information about tunnel faults.
Procedure
Step 1 Run display mpls te tunnel-interface last-error [ tunnel-name ] command to view information
about tunnel faults.
----End
Example
Run the display mpls te tunnel-interface last-error command on the ingress, and you can view
last errors of a local node or last errors carried in a PathErr message received from the
downstream node. The errors can be as follows:
l
This command shows the last five recorded errors of the TE tunnel.
Context
Run the reset command in the user view to clear the operation information.
Issue 02 (2011-09-10)
320
3 MPLS TE Configuration
Procedure
Step 1 Run the reset mpls rsvp-te statistics { global | interface [ interface-type interface-number ] }
command in the user view to clear statistics about RSVP-TE.
----End
Context
To make the tunnel-related configuration take effect, you can run the mpls te commit command
in the tunnel interface view and run the reset command in the user view.
NOTE
If the configuration is modified in the interface view of the TE tunnel but the mpls te commit command
is not configured, the system cannot execute the reset mpls te tunnel-interface tunnel command to reestablish the tunnel.
Procedure
Step 1 Run the reset mpls te tunnel-interface tunnel interface-number command to reset the tunnel
interface.
----End
Context
CAUTION
Resetting the RSVP process results in the release and reestablishment of all RSVP CR-LSPs.
To re-establish all RSVP CR-LSPs or verify the operation process of RSVP, run the following
reset command.
Procedure
l
Run the reset mpls rsvp-te command to reset the RSVP process.
----End
321
3 MPLS TE Configuration
Context
In a scenario where MPLS TE Auto FRR is used, you can run the following reset command to
release or re-establish bypass tunnels.
Procedure
l
Run the reset mpls te auto-frr { lsp-id ingress-lsr-id tunnel-id | name bypass-tunnelname } command to delete or reset the Auto FRR bypass tunnel.
----End
Context
Run the following commands in the system view to notify the Network Management System
(NMS) of the LSP status change.
By default, the trap function is disabled during the setup of the LDP LSP.
Procedure
l
----End
Follow-up Procedure
NOTE
This document takes interface numbers and link types of the NE40E-X8 as an example. In working
situations, the actual interface numbers and link types may be different from those used in this document.
Networking Requirements
On the network shown in Figure 3-2, a static TE tunnel from LSR A to LSR C and a static TE
tunnel from LSR C to LSR A need to be set up. The bandwidth of both tunnels is 10 Mbit/s.
Issue 02 (2011-09-10)
322
3 MPLS TE Configuration
Loopback1
1.1.1.1/32
ATM1/0/0
2.1.1.1/24
LSRA
Loopback1
2.2.2.2/32
ATM1/0/0
ATM2/0/0
2.1.1.2/24
3.2.1.1/24
Loopback1
3.3.3.3/32
ATM2/0/0
3.2.1.2/24
LSRB
LSRC
Configuration Roadmap
The configuration roadmap is as follows:
1.
Assign an IP address to each interface on each LSR, configure the loopback address as the
MPLS LSR ID, and configure OSPF to advertise the route to the network segment
connecting to each interface and LSR ID.
2.
Configure the LSR ID and globally enable MPLS and MPLS TE on each node and interface.
3.
Configure the maximum reservable bandwidth and BC0 bandwidth for the link on each
outgoing interface of each LSR along the tunnel (assume the tunnel obtains bandwidth from
BC0).
4.
Create a tunnel interface on the ingress and specify the IP address of the tunnel, tunnel
protocol, destination address, tunnel ID, and the signaling protocol used for establishing
the tunnel.
5.
Configure a static LSP associated with the tunnel, and specify the outgoing label and nexthop address on the ingress, the incoming interface, next-hop address, and outgoing label
on the transit node, and the incoming label and incoming interface on the egress to set up
the LSP.
NOTE
l The outgoing label of each node is the incoming label of the next node.
l When running the static-cr-lsp ingress { tunnel-interface tunnel interface-number | tunnel-name }
destination destination-address { nexthop next-hop-address | outgoing-interface interface-type
interface-number } out-label out-label-value [ bandwidth [ ct0 | ct1 ] bandwidth ] command to
configure the ingress of a CR-LSP, note that tunnel-name must be the same as the tunnel name created
by using the interface tunnel interface -number command. tunnel-name is a case-sensitive character
string in which spaces are not supported. For example, the name of the tunnel created by using the
interface tunnel 2/0/0 command is Tunnel2/0/0. In this case, the parameter of the static CR-LSP on
the ingress is Tunnel2/0/0, ensuring that the tunnel is successfully created. This restriction does not
apply to transit nodes or egresses.
Data Preparation
To complete the configuration, you need the following data:
l
Tunnel interface names, tunnel interface IP addresses, destination addresses, tunnel IDs,
and tunnel signaling protocol (CR-Static) on LSR A and LSR C
Next-hop address and outgoing label of the ingress on the static CR-LSP
Issue 02 (2011-09-10)
323
3 MPLS TE Configuration
Incoming interface, next-hop address, and outgoing label of the transit node on the static
CR-LSP
Procedure
Step 1 Configure the IP address of each interface and a routing protocol.
# Configure the IP address of each interface and the routing protocol as shown in Figure 3-2 to
ensure the reachability between LSRs.
The detailed configuration is not provided here.
Step 2 Configure the basic MPLS functions and enable MPLS TE.
# Configure LSR A.
[LSRA] mpls lsr-id 1.1.1.1
[LSRA] mpls
[LSRA-mpls] mpls te
[LSRA-mpls] quit
[LSRA] interface atm 1/0/0
[LSRA-Atm1/0/0] pvc 1/100
[LSRA-atm-pvc-Atm1/0/0-1/100] map ip 2.1.1.2 broadcast
[LSRA-atm-pvc-Atm1/0/0-1/100] quit
[LSRA-Atm1/0/0] ospf network-type p2p
[LSRA-Atm1/0/0] mpls
[LSRA-Atm1/0/0] mpls te
[LSRA-Atm1/0/0] quit
The configurations of LSR A, LSR B, and LSR C are similar, and are not provided here.
Step 3 Configure MPLS-TE bandwidth attributes for links.
# Configure the maximum reservable bandwidth for links and BC0 bandwidth on each outgoing
interface of each LSR along the tunnel. The BC0 bandwidth of links must be greater than the
tunnel bandwidth (10 Mbit/s).
# Configure LSR A.
[LSRA] interface atm 1/0/0
[LSRA-Atm1/0/0] mpls te bandwidth max-reservable-bandwidth 100000
[LSRA-Atm1/0/0] mpls te bandwidth bc0 100000
[LSRA-Atm1/0/0] quit
# Configure LSR B.
[LSRB] interface atm
[LSRB-Atm1/0/0] mpls
[LSRB-Atm1/0/0] mpls
[LSRB-Atm1/0/0] quit
[LSRB] interface atm
[LSRB-Atm2/0/0] mpls
[LSRB-Atm2/0/0] mpls
[LSRB-Atm2/0/0] quit
1/0/0
te bandwidth max-reservable-bandwidth 100000
te bandwidth bc0 100000
2/0/0
te bandwidth max-reservable-bandwidth 100000
te bandwidth bc0 100000
# Configure LSR C.
[LSRC] interface atm 2/0/0
[LSRC-Atm2/0/0] mpls te bandwidth max-reservable-bandwidth 100000
[LSRC-Atm2/0/0] mpls te bandwidth bc0 100000
[LSRC-Atm2/0/0] quit
324
3 MPLS TE Configuration
Issue 02 (2011-09-10)
325
3 MPLS TE Configuration
-----------------------------------------------------------------------------Ingress LsrId
Destination
LSPID
In/Out Label
R Tunnel-name
-----------------------------------------------------------------------------20/30
I Tunnel1/0/0
120/130
I Tunnel2/0/0
[LSRC] display mpls te tunnel
-----------------------------------------------------------------------------Ingress LsrId
Destination
LSPID
In/Out Label
R Tunnel-name
-----------------------------------------------------------------------------3.3.3.3
1.1.1.1
1
NULL/120
I Tunnel2/0/0
30/NULL
I Tunnel1/0/0
Run the display mpls lsp or display mpls static-cr-lsp command on each LSR. You can view
the establishment status of the static CR-LSP.
# View the configuration on LSR A.
[LSRA] display mpls lsp
---------------------------------------------------------------------LSP Information: STATIC CRLSP
---------------------------------------------------------------------FEC
In/Out Label In/Out IF
Vrf Name
3.3.3.3/32
NULL/20
-/Atm1/0/0
-/130/NULL
Atm1/0/0/[LSRA] display mpls static-cr-lsp
TOTAL
: 2
STATIC CRLSP(S)
UP
: 2
STATIC CRLSP(S)
DOWN
: 0
STATIC CRLSP(S)
Name
FEC
I/O Label I/O If
Stat
Tunnel1/0/0
3.3.3.3/32
NULL/20
-/Atm1/0/0
Up
tunnel2/0/0
-/130/NULL
Atm1/0/0/Up
Issue 02 (2011-09-10)
326
3 MPLS TE Configuration
When the static CR-LSP is used to establish the MPLS TE tunnel, the packets on the transit node
and the egress are forwarded directly based on the specified incoming label and outgoing label.
Therefore, no information about FECs is displayed on LSR B or LSR C.
----End
Configuration Files
l
Issue 02 (2011-09-10)
327
3 MPLS TE Configuration
Issue 02 (2011-09-10)
328
3 MPLS TE Configuration
Context
MPLS-TP is widely used on transport networks. Although MPLS-TP supports OAM, OAM
itself only supports the network element-level management system, which cannot meet the
requirements for network management over public telecommunication networks. MPLS-TP
OAM supporting static bidirectional co-routed LSP is an effective operation and management
method and can detect, identify, and locate faults in the MPLS-TP user plane.
This example only describes the configuration procedure for a static bidirectional co-routed LSP.
For information about MPLS-TP OAM, see the description in Configuring MPLS-TP OAM.
As shown in Figure 3-3, a static bidirectional co-routed LSP originates from LSR A and
terminates on LSR C. OAM PDUs travel through this LSP and any transit node can send a
response along the same path in the opposite direction. The links for the static bidirectional corouted LSP between LSR A and LSR C has the bandwidth of 10 Mbit/s.
Figure 3-3 Networking diagram for a static bidirectional co-routed LSP
Loopback1
1.1.1.1/32
Loopback1
2.2.2.2/32
POS1/0/0
2.1.1.1/24
POS1/0/0
2.1.1.2/24
LSRA
Loopback1
3.3.3.3/32
POS2/0/0 POS1/0/0
3.2.1.1/24 3.2.1.2/24
LSRB
LSRC
Configuration Roadmap
The configuration roadmap is as follows:
1.
2.
3.
4.
5.
Configure the ingress, a transit node, and the egress for the static bidirectional co-routed
LSP.
6.
Bind the tunnel interface configured on LSR C to the static bidirectional co-routed LSP.
Data Preparation
To complete the configuration, you need the following data:
l
Issue 02 (2011-09-10)
Tunnel interface's name and IP address, destination address, tunnel ID, and static CR-LSP
signalling on LSR A and LSR C
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
329
3 MPLS TE Configuration
Inbound interface, next-hop address, and outgoing label on the transit node
Procedure
Step 1 Assign an IP address to each interface and configure a routing protocol.
# Configure an IP address and a mask for each interface and configure OSPF so that all LSRs
can interconnect with each other.
The configuration details are not provided here.
Step 2 Configure basic MPLS functions and enable MPLS TE.
# Configure LSR A.
[LSRA] mpls lsr-id 1.1.1.1
[LSRA] mpls
[LSRA-mpls] mpls te
[LSRA-mpls] quit
[LSRA] interface pos 1/0/0
[LSRA-Pos1/0/0] mpls
[LSRA-Pos1/0/0] mpls te
[LSRA-Pos1/0/0] quit
The configurations on LSR B and LSR C are similar to the configuration on LSR A.
Step 3 Configure MPLS TE attributes for links.
# Configure the maximum reservable bandwidth and BC0 bandwidth for the link on the outbound
interface of each LSR. The BC0 bandwidth of links must be greater than the tunnel bandwidth
(10 Mbit/s).
# Configure LSR A.
[LSRA] interface pos 1/0/0
[LSRA-Pos1/0/0] mpls te bandwidth max-reservable-bandwidth 100000
[LSRA-Pos1/0/0] mpls te bandwidth bc0 100000
[LSRA-Pos1/0/0] quit
# Configure LSR B.
[LSRB] interface pos
[LSRB-Pos1/0/0] mpls
[LSRB-Pos1/0/0] mpls
[LSRB-Pos1/0/0] quit
[LSRB] interface pos
[LSRB-Pos2/0/0] mpls
[LSRB-Pos2/0/0] mpls
[LSRB-Pos2/0/0] quit
1/0/0
te bandwidth max-reservable-bandwidth 100000
te bandwidth bc0 100000
2/0/0
te bandwidth max-reservable-bandwidth 100000
te bandwidth bc0 100000
# Configure LSR C.
[LSRC] interface pos 2/0/0
[LSRC-Pos2/0/0] mpls te bandwidth max-reservable-bandwidth 100000
[LSRC-Pos2/0/0] mpls te bandwidth bc0 100000
[LSRC-Pos2/0/0] quit
Issue 02 (2011-09-10)
330
3 MPLS TE Configuration
[LSRA-Tunnel1/0/0]
[LSRA-Tunnel1/0/0]
[LSRA-Tunnel1/0/0]
[LSRA-Tunnel1/0/0]
[LSRA-Tunnel1/0/0]
[LSRA-Tunnel1/0/0]
[LSRA-Tunnel1/0/0]
[LSRA-Tunnel1/0/0]
Step 5 Configure the ingress, a transit node, and the egress of the static bidirectional co-routed LSP.
# Configure LSR A as the ingress.
[LSRA] bidirectional static-cr-lsp ingress Tunnel/0/0
[LSRA-bi-static-ingress-Tunnell/0/0] forward nexthop 2.1.1.2 out-label 20
bandwidth ct0 10000
[LSRA-bi-static-ingress-Tunnell/0/0] backward in-label 20
Step 6 Bind the tunnel interface on LSR C to the static bidirectional co-routed LSP.
[LSRC] interface Tunnel2/0/0
[LSRC-Tunnel2/0/0] mpls te passive-tunnel
[LSRC-Tunnel2/0/0] mpls te binding bidirectional static-cr-lsp egress lsp1
[LSRC-Tunnel2/0/0] mpls te commit
[LSRC-Tunnel2/0/0] quit
331
3 MPLS TE Configuration
Run the display mpls te bidirectional static-cr-lsp command on each LSR. Information about
the static bidirectional co-routed LSP is displayed.
# Check the configuration results on LSR A.
[LSRA] display
TOTAL
UP
DOWN
Name
Tunnel1/0/0
I/O If
-/Pos1/0/0
Pos1/0/0-
Stat
I/O If
-/Pos1/0/0
Pos2/0/0-
Stat
Up
Up
I/O If
Pos1/0/0/-/Pos1/0/0
Stat
Up
When a static bidirectional co-routed LSP is established, packets on a transit node (LSR B) and
the egress (LSR C) are forwarded directly based on the incoming and outgoing labels specified
on the nodes. Therefore, the FEC-relevant contents are empty in the display on LSR B and LSR
C.
After completing the configurations, run the ping command on LSR A. The static bidirectional
co-routed LSP is reachable.
[LSRA] ping lsp te Tunnel 1/0/0
LSP PING FEC: TE TUNNEL IPV4 SESSION QUERY
s CTRL_C to break
Reply from 3.3.3.3: bytes=100 Sequence=1
Reply from 3.3.3.3: bytes=100 Sequence=2
Reply from 3.3.3.3: bytes=100 Sequence=3
Reply from 3.3.3.3: bytes=100 Sequence=4
Reply from 3.3.3.3: bytes=100 Sequence=5
Tunnel1/0/0 : 100
time
time
time
time
time
=
=
=
=
=
110 ms
70 ms
60 ms
80 ms
60 ms
--- FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel1/0/0 ping statistics ---
Issue 02 (2011-09-10)
332
3 MPLS TE Configuration
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 60/76/110 ms
----End
Configuration Files
l
Issue 02 (2011-09-10)
333
3 MPLS TE Configuration
Context
Figure 3-4 shows an MPLS network. APS is configured on PE1 and PE2. The working tunnel
is established along the path PE1 -> PE2 and the protection tunnel is established along the path
PE1 -> P -> PE2. When the MPLS network operates properly, the working tunnel transmits
MPLS traffic. If the working tunnel fails, MPLS traffic switches to the protection tunnel.
Issue 02 (2011-09-10)
334
3 MPLS TE Configuration
Figure 3-4 Networking diagram for a 1:1 bidirectional tunnel protection group
Loopback1
3.3.3.3/32
P
G E 1/0/0
10.1.1.2/24
G E 2/0/0
10.1.2.2/24
G E 2/0/0
10.1.1.1/24
G E 2/0/0
10.1.2.1/24
PE1
PE2
G E 1/0/0
10.1.3.1/24
Loopback1
1.1.1.1/32
G E 1/0/0
10.1.3.2/24
Loopback1
2.2.2.2/32
P rim ary path
B ackup path
Configuration Roadmap
The configuration roadmap is as follows:
1.
2.
3.
4.
Configure the ingress, a transit node, and the egress for the static bidirectional co-routed
LSP of primary tunnel.
5.
Configure the ingress, a transit node, and the egress for the static bidirectional co-routed
LSP of protect tunnel.
6.
7.
Configure APS.
Data Preparation
To complete the configuration, you need the following data:
l
Tunnel interface's name and IP address, destination address, tunnel ID, and static CR-LSP
signaling on PE1 and PE2
Inbound interface, next-hop address, and outgoing label on the transit node
Issue 02 (2011-09-10)
335
3 MPLS TE Configuration
Procedure
Step 1 Assign an IP address to each interface and configure a routing protocol.
Configure an IP address and a mask for each interface and configure OSPF to allow all LSRs to
interconnect with each other.
The configuration details are not provided here.
Step 2 Configure basic MPLS functions and enable MPLS TE.
# Configure PE1.
[PE1] mpls lsr-id 1.1.1.1
[PE1] mpls
[PE1-mpls] mpls te
[PE1-mpls] quit
[PE1] interface GigabitEthernet
[PE1-GigabitEthernet1/0/0] mpls
[PE1-GigabitEthernet1/0/0] mpls
[PE1-GigabitEthernet1/0/0] quit
[PE1] interface GigabitEthernet
[PE1-GigabitEthernet2/0/0] mpls
[PE1-GigabitEthernet2/0/0] mpls
[PE1-GigabitEthernet2/0/0] quit
1/0/0
te
2/0/0
te
1/0/0
te bandwidth max-reservable-bandwidth 100000
te bandwidth bc0 100000
2/0/0
te bandwidth max-reservable-bandwidth 100000
te bandwidth bc0 100000
# Configure P.
[P] interface GigabitEthernet
[P-GigabitEthernet1/0/0] mpls
[P-GigabitEthernet1/0/0] mpls
[P-GigabitEthernet1/0/0] quit
[P] interface GigabitEthernet
[P-GigabitEthernet2/0/0] mpls
[P-GigabitEthernet2/0/0] mpls
[P-GigabitEthernet2/0/0] quit
1/0/0
te bandwidth max-reservable-bandwidth 100000
te bandwidth bc0 100000
2/0/0
te bandwidth max-reservable-bandwidth 100000
te bandwidth bc0 100000
# Configure PE2.
[PE2] interface GigabitEthernet
[PE2-GigabitEthernet1/0/0] mpls
[PE2-GigabitEthernet1/0/0] mpls
[PE2-GigabitEthernet1/0/0] quit
[PE2] interface GigabitEthernet
[PE2-GigabitEthernet2/0/0] mpls
[PE2-GigabitEthernet2/0/0] mpls
[PE2-GigabitEthernet2/0/0] quit
Issue 02 (2011-09-10)
1/0/0
te bandwidth max-reservable-bandwidth 100000
te bandwidth bc0 100000
2/0/0
te bandwidth max-reservable-bandwidth 100000
te bandwidth bc0 100000
336
3 MPLS TE Configuration
Step 4 Configure the ingress, a transit node, and the egress for the static bidirectional co-routed LSP
of primary tunnel.
# Configure PE1 as the ingress.
[PE1] bidirectional static-cr-lsp ingress Tunnel1/0/0
[PE1-bi-static-ingress-Tunnel1/0/0] forward nexthop 10.1.1.2 out-label 20
bandwidth ct0 10000
[PE1-bi-static-ingress-Tunnel1/0/0] backward in-label 20
# Bind the tunnel interface on PE2 to the static bidirectional co-routed LSP.
[PE2] interface Tunnel1/0/0
[PE2-Tunnel1/0/0] mpls te passive-tunnel
[PE2-Tunnel1/0/0] mpls te binding bidirectional static-cr-lsp egress Tunnel1/0/0
[PE2-Tunnel1/0/0] mpls te commit
[PE2-Tunnel1/0/0] quit
Step 5 Configure the ingress, a transit node, and the egress for the static bidirectional co-routed LSP
of protect tunnel.
# Configure PE1 as the ingress.
[PE1] bidirectional static-cr-lsp ingress Tunnel2/0/0
[PE1-bi-static-ingress-Tunnel2/0/0] forward nexthop 10.1.3.2 out-label 80
bandwidth ct0 10000
[PE1-bi-static-ingress-Tunnel2/0/0] backward in-label 90
[PE1-bi-static-ingress-Tunnel2/0/0] quit
# Bind the tunnel interface on PE2 to the static bidirectional co-routed LSP.
[PE2] interface Tunnel2/0/0
[PE2-Tunnel2/0/0] mpls te passive-tunnel
[PE2-Tunnel2/0/0] mpls te binding bidirectional static-cr-lsp egress Tunnel2/0/0
[PE2-Tunnel2/0/0] mpls te commit
[PE2-Tunnel2/0/0] quit
337
3 MPLS TE Configuration
----End
Issue 02 (2011-09-10)
338
3 MPLS TE Configuration
Configuration Files
l
l
Issue 02 (2011-09-10)
Configuration file of P
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
339
3 MPLS TE Configuration
#
sysname P
#
mpls lsr-id 3.3.3.3
mpls
mpls te
#
bidirectional static-cr-lsp transit lsp1
forward in-label 20 nexthop 10.1.2.1 out-label 40 bandwidth ct0 10000
backward in-label 16 nexthop 10.1.1.1 out-label 20 bandwidth ct0 10000
#
interface GigabitEthernet1/0/0
undo shutdown
ip address 10.1.1.2 255.255.255.0
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
#
interface GigabitEthernet2/0/0
undo shutdown
ip address 10.1.2.2 255.255.255.0
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
ospf 1
area 0.0.0.0
network 10.1.1.0 0.0.0.255
network 10.1.2.0 0.0.0.255
network 10.1.3.0 0.0.0.255
network 1.1.1.1 0.0.0.0
network 2.2.2.2 0.0.0.0
network 3.3.3.3 0.0.0.0
network 1.1.1.9 0.0.0.0
#
return
Issue 02 (2011-09-10)
340
3 MPLS TE Configuration
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
interface Tunnel1/0/0
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 1.1.1.1
mpls te signal-protocol cr-static
mpls te tunnel-id 100
mpls te bidirectional
mpls te passive-tunnel
mpls te binding bidirectional static-cr-lsp egress Tunnel1/0/0
mpls te commit
#
interface Tunnel2/0/0
ip address 1.1.1.9 255.255.255.255
tunnel-protocol mpls te
destination 1.1.1.1
mpls te signal-protocol cr-static
mpls te tunnel-id 200
mpls te bidirectional
mpls te passive-tunnel
mpls te binding bidirectional static-cr-lsp egress Tunnel2/0/0
mpls te commit
#
ospf 1
area 0.0.0.0
network 10.1.1.0 0.0.0.255
network 10.1.2.0 0.0.0.255
network 10.1.3.0 0.0.0.255
network 1.1.1.1 0.0.0.0
network 2.2.2.2 0.0.0.0
network 3.3.3.3 0.0.0.0
network 1.1.1.9 0.0.0.0
#
return
Networking Requirements
On the network shown in Figure 3-5, IS-IS is run on LSR A, LSR B, LSR C, and LSR D. They
are all Level 2 devices.
RSVP-TE is used to establish a TE tunnel from LSR A to LSR D. The bandwidth is 20 Mbit/
s. The maximum reservable bandwidth of links along the tunnel is 100 Mbit/s. The bandwidth
constraints model is the default RDM and the bandwidth of BC0 is 100 Mbit/s.
Issue 02 (2011-09-10)
341
3 MPLS TE Configuration
Loopback1
1.1.1.9/32
Loopback1
4.4.4.9/32
LSRA
LSRD
GE1/0/0
10.1.1.1/24
GE1/0/0
10.1.1.2/24
Loopback1
2.2.2.9/32
GE1/0/0
30.1.1.2/24
GE1/0/0
30.1.1.1/24
POS2/0/0
POS2/0/0
20.1.1.1/24 20.1.1.2/24
LSRB
Loopback1
3.3.3.9/32
LSRC
Configuration Roadmap
The configuration roadmap is as follows:
1.
Configure IP addresses for the interfaces on each LSR and configuring loopback address
as the LSR ID.
2.
Enable IS-IS globally, configure the name of network entity, change cost type, enable ISIS TE and enable IS-IS on all interfaces including loopback interfaces.
3.
Configure LSR ID and enable MPLS, MPLS TE, MPLS RSVP-TE, and MPLS TE CSPF
globally.
4.
5.
Configure the maximum reservable bandwidth and BC bandwidth for the links on each
LSR along the tunnel.
6.
Create the tunnel interface on the ingress and specifying the IP address, tunnel protocol,
destination address, tunnel ID, dynamic signaling protocol RSVP-TE, and tunnel
bandwidth.
Data Preparation
To complete the configuration, you need the following data:
l
IS-IS area ID of each LSR, originating system ID, and IS-IS level
Maximum reservable bandwidth and BC bandwidth for the links along the tunnel
Tunnel interface name, IP address, destination address, tunnel ID, tunnel signaling protocol
(RSVP-TE), and tunnel bandwidth
Configuration Procedure
1.
2.
Issue 02 (2011-09-10)
342
3 MPLS TE Configuration
# Configure LSR A.
[LSRA] isis 1
[LSRA-isis-1] network-entity 00.0005.0000.0000.0001.00
[LSRA-isis-1] is-level level-2
[LSRA-isis-1] quit
[LSRA] interface gigabitethernet 1/0/0
[LSRA-GigabitEthernet1/0/0] isis enable 1
[LSRA-GigabitEthernet1/0/0] quit
[LSRA] interface loopback 1
[LSRA-LoopBack1] isis enable 1
[LSRA-LoopBack1] quit
# Configure LSR B.
[LSRB] isis 1
[LSRB-isis-1] network-entity 00.0005.0000.0000.0002.00
[LSRB-isis-1] is-level level-2
[LSRB-isis-1] quit
[LSRB] interface gigabitethernet 1/0/0
[LSRB-GigabitEthernet1/0/0] isis enable 1
[LSRB-GigabitEthernet1/0/0] quit
[LSRB] interface pos 2/0/0
[LSRB-Pos2/0/0] isis enable 1
[LSRB-Pos2/0/0] quit
[LSRB] interface loopback 1
[LSRB-LoopBack1] isis enable 1
[LSRB-LoopBack1] quit
# Configure LSR C.
[LSRC] isis 1
[LSRC-isis-1] network-entity 00.0005.0000.0000.0003.00
[LSRC-isis-1] is-level level-2
[LSRC-isis-1] quit
[LSRC] interface gigabitethernet 1/0/0
[LSRC-GigabitEthernet1/0/0] isis enable 1
[LSRC-GigabitEthernet1/0/0] quit
[LSRC] interface pos 2/0/0
[LSRC-Pos2/0/0] isis enable 1
[LSRC-Pos2/0/0] quit
[LSRC] interface loopback 1
[LSRC-LoopBack1] isis enable 1
[LSRC-LoopBack1] quit
# Configure LSR D.
[LSRD] isis 1
[LSRD-isis-1] network-entity 00.0005.0000.0000.0004.00
[LSRD-isis-1] is-level level-2
[LSRD-isis-1] quit
[LSRD] interface gigabitethernet 1/0/0
[LSRD-GigabitEthernet1/0/0] isis enable 1
[LSRD-GigabitEthernet1/0/0] quit
[LSRD] interface loopback 1
[LSRD-LoopBack1] isis enable 1
[LSRD-LoopBack1] quit
After the configuration, run the display ip routing-table command on each LSR, and you
can view that LSRs learned routes from each other.
Take the display on LSR A as an example.
[LSRA] display ip routing-table
Route Flags: R - relay, D - download to fib
-----------------------------------------------------------------------------Routing Tables: Public
Destinations : 10
Routes : 10
Destination/Mask Proto Pre Cost Flags
NextHop
Interface
1.1.1.9/32 Direct 0
0
D
127.0.0.1
InLoopBack0
2.2.2.9/32 ISIS-L2 15
10
D
10.1.1.2
GigabitEthernet1/0/0
3.3.3.9/32 ISIS-L2 15
20
D
10.1.1.2
GigabitEthernet1/0/0
4.4.4.9/32 ISIS-L2 15
30
D
10.1.1.2
GigabitEthernet1/0/0
10.1.1.0/24 Direct 0
0
D
10.1.1.1
GigabitEthernet1/0/0
Issue 02 (2011-09-10)
343
3 MPLS TE Configuration
10.1.1.1/32 Direct 0
20.1.1.0/24 ISIS-L2 15
30.1.1.0/24 ISIS-L2 15
127.0.0.0/8
Direct 0
127.0.0.1/32 Direct 0
3.
0
20
30
0
0
D
D
D
D
D
127.0.0.1
10.1.1.2
10.1.1.2
127.0.0.1
127.0.0.1
InLoopBack0
GigabitEthernet1/0/0
GigabitEthernet1/0/0
InLoopBack0
InLoopBack0
Configure the basic MPLS functions and enable MPLS TE, RSVP-TE, and CSPF.
# Enable MPLS, MPLS TE, and RSVP-TE globally on each LSR, enable MPLS, MPLS
TE, and RSVP-TE on all tunnel interfaces, and enable CSPF in the system view on the
ingress.
# Configure LSR A.
[LSRA] mpls lsr-id 1.1.1.9
[LSRA] mpls
[LSRA-mpls] mpls te
[LSRA-mpls] mpls rsvp-te
[LSRA-mpls] mpls te cspf
[LSRA-mpls] quit
[LSRA] interface gigabitethernet 1/0/0
[LSRA-GigabitEthernet1/0/0] mpls
[LSRA-GigabitEthernet1/0/0] mpls te
[LSRA-GigabitEthernet1/0/0] mpls rsvp-te
[LSRA-GigabitEthernet1/0/0] quit
# Configure LSR B.
[LSRB] mpls lsr-id 2.2.2.9
[LSRB] mpls
[LSRB-mpls] mpls te
[LSRB-mpls] mpls rsvp-te
[LSRB-mpls] quit
[LSRB] interface gigabitethernet 1/0/0
[LSRB-GigabitEthernet1/0/0] mpls
[LSRB-GigabitEthernet1/0/0] mpls te
[LSRB-GigabitEthernet1/0/0] mpls rsvp-te
[LSRB-GigabitEthernet1/0/0] quit
[LSRB] interface pos 2/0/0
[LSRB-Pos2/0/0] mpls
[LSRB-Pos2/0/0] mpls te
[LSRB-Pos2/0/0] mpls rsvp-te
[LSRB-Pos2/0/0] quit
# Configure LSR C.
[LSRC] mpls lsr-id 3.3.3.9
[LSRC] mpls
[LSRC-mpls] mpls te
[LSRC-mpls] mpls rsvp-te
[LSRC-mpls] quit
[LSRC] interface gigabitethernet 1/0/0
[LSRC-GigabitEthernet1/0/0] mpls
[LSRC-GigabitEthernet1/0/0] mpls te
[LSRC-GigabitEthernet1/0/0] mpls rsvp-te
[LSRC-GigabitEthernet1/0/0] quit
[LSRC] interface pos 2/0/0
[LSRC-Pos2/0/0] mpls
[LSRC-Pos2/0/0] mpls te
[LSRC-Pos2/0/0] mpls rsvp-te
[LSRC-Pos2/0/0] quit
# Configure LSR D.
[LSRD] mpls lsr-id 4.4.4.9
[LSRD] mpls
[LSRD-mpls] mpls te
[LSRD-mpls] mpls rsvp-te
[LSRD-mpls] quit
[LSRD] interface gigabitethernet 1/0/0
[LSRD-GigabitEthernet1/0/0] mpls
[LSRD-GigabitEthernet1/0/0] mpls te
[LSRD-GigabitEthernet1/0/0] mpls rsvp-te
Issue 02 (2011-09-10)
344
3 MPLS TE Configuration
[LSRD-GigabitEthernet1/0/0] quit
4.
# Configure LSR B.
[LSRB] isis 1
[LSRB-isis-1] cost-style wide
[LSRB-isis-1] traffic-eng level-2
[LSRB-isis-1] quit
# Configure LSR C.
[LSRC] isis 1
[LSRC-isis-1] cost-style wide
[LSRC-isis-1] traffic-eng level-2
[LSRC-isis-1] quit
# Configure LSR D.
[LSRD] isis 1
[LSRD-isis-1] cost-style wide
[LSRD-isis-1] traffic-eng level-2
[LSRD-isis-1] quit
5.
# Configure LSR B.
[LSRB] interface pos2/0/0
[LSRB-Pos2/0/0] mpls te bandwidth max-reservable-bandwidth 100000
[LSRB-Pos2/0/0] mpls te bandwidth bc0 100000
[LSRB-Pos2/0/0] quit
# Configure LSR C.
[LSRC] interface gigabitethernet 1/0/0
[LSRC-GigabitEthernet1/0/0] mpls te bandwidth max-reservable-bandwidth 100000
[LSRC-GigabitEthernet1/0/0] mpls te bandwidth bc0 100000
[LSRC-GigabitEthernet1/0/0] quit
6.
Issue 02 (2011-09-10)
345
7.
3 MPLS TE Configuration
Run the display mpls te tunnel-interface command on LSR A to display the information
on the tunnel.
[LSRA] display mpls te tunnel-interface tunnel1/0/0
No
: 1
Tunnel-Name
: Tunnel1/0/0
TunnelIndex
: 0
LSP Index
: 2048
Session ID
: 100
LSP ID
: 1
Lsr Role
: Ingress
Lsp Type
: Primary
Ingress LSR ID
: 1.1.1.9
Egress LSR ID
: 4.4.4.9
In-Interface
: Out-Interface
: GE1/0/0
Sign-Protocol
: RSVP TE
Resv Style
: SE
IncludeAnyAff
: 0x0
ExcludeAnyAff
: 0x0
IncludeAllAff
: 0x0
LspConstraint
: ER-Hop Table Index
: AR-Hop Table Index: C-Hop Table Index
: 0
PrevTunnelIndexInSession: NextTunnelIndexInSession: PSB Handle
: 1024
Created Time
: 2010/06/07 16:01:18 UTC-08:00
-------------------------------DS-TE Information
-------------------------------Bandwidth Reserved Flag : Reserved
CT0 Bandwidth(Kbit/sec) : 2000
CT1 Bandwidth(Kbit/sec): 0
CT2 Bandwidth(Kbit/sec) : 0
CT3 Bandwidth(Kbit/sec): 0
CT4 Bandwidth(Kbit/sec) : 0
CT5 Bandwidth(Kbit/sec): 0
CT6 Bandwidth(Kbit/sec) : 0
CT7 Bandwidth(Kbit/sec): 0
Setup-Priority
: 7
Hold-Priority
: 7
-------------------------------FRR Information
-------------------------------Primary LSP Info
TE Attribute Flag
: 0x3
Protected Flag
: 0x0
Bypass In Use
: Not Exists
Bypass Tunnel Id
: BypassTunnel
: Bypass Lsp ID
: FrrNextHop
: ReferAutoBypassHandle
: FrrPrevTunnelTableIndex : FrrNextTunnelTableIndex: Bypass Attribute(Not configured)
Setup Priority
: Hold Priority
: HopLimit
: Bandwidth
: IncludeAnyGroup
: ExcludeAnyGroup
: IncludeAllGroup
: Bypass Unbound Bandwidth Info(Kbit/sec)
CT0 Unbound Bandwidth
: CT1 Unbound Bandwidth: CT2 Unbound Bandwidth
: CT3 Unbound Bandwidth: CT4 Unbound Bandwidth
: CT5 Unbound Bandwidth: CT6 Unbound Bandwidth
: CT7 Unbound Bandwidth: -------------------------------BFD Information
-------------------------------NextSessionTunnelIndex : PrevSessionTunnelIndex: NextLspId
: PrevLspId
: -
Issue 02 (2011-09-10)
346
3 MPLS TE Configuration
Run the display mpls te cspf tedb all command on LSR A to display the link information
in the TEDB.
[LSRA] display mpls te cspf tedb all
Maximum Node Supported: 128
Maximum Link Supported: 256
Current Total Node Number: 4
Current Total Link Number: 6
Id
Router-Id
IGP
Process-Id
Area
Link-Count
1
3.3.3.9
ISIS
1
Level-2
2
2
2.2.2.9
ISIS
1
Level-2
2
3
4.4.4.9
ISIS
1
Level-2
1
4
1.1.1.9
ISIS
1
Level-2
1
Configuration Files
l
Issue 02 (2011-09-10)
347
3 MPLS TE Configuration
interface GigabitEthernet1/0/0
ip address 10.1.1.2 255.255.255.0
isis enable 1
mpls
mpls te
mpls rsvp-te
#
interface Pos2/0/0
link-protocol ppp
clock master
ip address 20.1.1.1 255.255.255.0
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
mpls rsvp-te
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
isis enable 1
#
return
Issue 02 (2011-09-10)
348
3 MPLS TE Configuration
#
isis 1
is-level level-2
cost-style wide
network-entity 00.0005.0000.0000.0004.00
traffic-eng level-2
#
interface GigabitEthernet1/0/0
ip address 30.1.1.2 255.255.255.0
isis enable 1
mpls
mpls te
mpls rsvp-te
#
interface LoopBack1
ip address 4.4.4.9 255.255.255.255
isis enable 1
#
return
Networking Requirements
On the network shown in Figure 3-6, a primary CR-LSP is set up, with LSR A being the ingress
and LSR D being the egress. The primary CR-LSP needs to be configured with a hot-standby
CR-LSP and an ordinary backup CR-LSP. In this manner, when the primary CR-LSP fails, traffic
can be switched to the hot-standby CR-LSP or ordinary backup CR-LSP.
Figure 3-6 Networking diagram of setting up a CR-LSP by using a CR-LSP attribute template
LSRC
PO
/0
10. S2/0
1/0 24
S
1.4 /0
PO .1.2/
.1/2 PO
1
0
.
/
S
41
0
0
/
1
1.1.1.1/32 S1
0.1 1/0/0 4.4.4.4/32
4
2
/
.
O
4.2
P .1.1
/24
1
POS2/0/0 LSRE POS2/0/0
10.
10.1.3.1/24
10.1.6.2/24
POS1/0/0
POS2/0/0
PO
/0
10.1.3.2/24
10.1.6.1/24
LSRA 10 S3/
3/0 /24 LSRD
S
.1.
0/0
2.1
PO .5.2
/24 PO
.1
0
0/ 4 10
10 S1/
/
2
.1. 0/0
S
/2
2.2
PO .5.1
/24
.1
10
LSRB
Configuration Roadmap
The configuration roadmap is as follows:
Issue 02 (2011-09-10)
349
3 MPLS TE Configuration
1.
Configure an IP address and a routing protocol for each interface so that they can
communicate with each other at the network layer.
2.
Enable MPLS and MPLS TE in the system view and in each interface view.
3.
4.
Create a CR-LSP on the TE tunnel interface by using the CR-LSP attribute template.
Data Preparation
To complete the configuration, you need the following data:
l
IP address of the tunnel interface, destination address of the tunnel, and tunnel ID
Procedure
Step 1 Configure an IP address and an IGP for each interface so that they can communicate with each
other at the network layer.
The configuration details are not provided here.
Step 2 Configure the LSR ID for each device, and enable MPLS and MPLS TE in the system and
interface views on each device.
# Configure LSR A.
<LSRA> system-view
[LSRA] mpls lsr-id 1.1.1.1
[LSRA] mpls
[LSRA-mpls] mpls te
[LSRA-mpls] mpls rsvp-te
[LSRA-mpls] quit
[LSRA] interface pos1/0/0
[LSRA-Pos1/0/0] mpls
[LSRA-Pos1/0/0] mpls te
[LSRA-Pos1/0/0] mpls rsvp-te
[LSRA-Pos1/0/0] quit
[LSRA] interface pos2/0/0
[LSRA-Pos2/0/0] mpls
[LSRA-Pos2/0/0] mpls te
[LSRA-Pos2/0/0] mpls rsvp-te
[LSRA-Pos2/0/0] quit
[LSRA] interface pos3/0/0
[LSRA-Pos3/0/0] mpls
[LSRA-Pos3/0/0] mpls te
[LSRA-Pos3/0/0] mpls rsvp-te
[LSRA-Pos3/0/0] quit
NOTE
The configurations of LSR B, LSR C, LSR D, and LSR E are similar to those of LSR A, and are not provided
here.
Issue 02 (2011-09-10)
350
3 MPLS TE Configuration
The priorities of the CR-LSP attribute templates configured on the same tunnel interface must be the same.
Step 4 Set up a CR-LSP by using the CR-LSP attribute template, with LSR A being the ingress and
LSR D being the egress.
# Set up a CR-LSP, with LSRA being the ingress and LSRD being the egress.
[LSRA] interface tunnel1/0/0
[LSRA-Tunnel1/0/0] tunnel-protocol mpls te
[LSRA-Tunnel1/0/0] destination 4.4.4.4
[LSRA-Tunnel1/0/0] mpls te tunnel-id 100
[LSRA-Tunnel1/0/0] mpls te primary-lsp-constraint lsp-attribute lsp_attribute_1
[LSRA-Tunnel1/0/0] mpls te hotstandby-lsp-constraint 1 lsp-attribute
lsp_attribute_2
[LSRA-Tunnel1/0/0] mpls te ordinary-lsp-constraint 1 lsp-attribute lsp_attribute_3
[LSRA-Tunnel1/0/0] mpls te commit
Issue 02 (2011-09-10)
351
3 MPLS TE Configuration
# Run the display mpls te tunnel verbose on LSR A. You can see that the LSP attribute template
is used to set up a CR-LSP.
<LSRA> display mpls te tunnel verbose
No
: 1
Tunnel-Name
: Tunnel1/0/0
TunnelIndex
: 0
LSP Index
: 2048
Session ID
: 100
LSP ID
: 1
Lsr Role
: Ingress
Lsp Type
: Primary
Ingress LSR ID
: 1.1.1.1
Egress LSR ID
: 4.4.4.4
In-Interface
: Out-Interface
: Pos1/0/0
Sign-Protocol
: RSVP TE
Resv Style
: SE
IncludeAnyAff
: 0x0
ExcludeAnyAff
: 0x0
IncludeAllAff
: 0x0
LspConstraint
: 1
ER-Hop Table Index
: 0
AR-Hop Table Index: 0
C-Hop Table Index
: PrevTunnelIndexInSession: 1
NextTunnelIndexInSession: PSB Handle
: 1024
Created Time
: 2010/07/01 17:40:35 UTC-08:00
-------------------------------DS-TE Information
-------------------------------Bandwidth Reserved Flag : Unreserved
CT0 Bandwidth(Kbit/sec) : 0
CT1 Bandwidth(Kbit/sec): 0
CT2 Bandwidth(Kbit/sec) : 0
CT3 Bandwidth(Kbit/sec): 0
CT4 Bandwidth(Kbit/sec) : 0
CT5 Bandwidth(Kbit/sec): 0
CT6 Bandwidth(Kbit/sec) : 0
CT7 Bandwidth(Kbit/sec): 0
Setup-Priority
: 5
Hold-Priority
: 5
-------------------------------FRR Information
-------------------------------Primary LSP Info
TE Attribute Flag
: 0x3
Protected Flag
: 0x0
Bypass In Use
: Not Exists
Bypass Tunnel Id
: BypassTunnel
: Bypass Lsp ID
: FrrNextHop
: ReferAutoBypassHandle
: FrrPrevTunnelTableIndex : FrrNextTunnelTableIndex: Bypass Attribute(Not configured)
Setup Priority
: Hold Priority
: HopLimit
: Bandwidth
: IncludeAnyGroup
: ExcludeAnyGroup
: IncludeAllGroup
: Bypass Unbound Bandwidth Info(Kbit/sec)
CT0 Unbound Bandwidth
: CT1 Unbound Bandwidth: CT2 Unbound Bandwidth
: CT3 Unbound Bandwidth: CT4 Unbound Bandwidth
: CT5 Unbound Bandwidth: CT6 Unbound Bandwidth
: CT7 Unbound Bandwidth: -------------------------------BFD Information
-------------------------------NextSessionTunnelIndex : PrevSessionTunnelIndex: NextLspId
: PrevLspId
: No
Tunnel-Name
TunnelIndex
Session ID
Lsr Role
Ingress LSR ID
Egress LSR ID
In-Interface
Out-Interface
Sign-Protocol
Issue 02 (2011-09-10)
:
:
:
:
:
:
:
:
:
:
2
Tunnel1/0/0
1
100
Ingress
1.1.1.1
4.4.4.4
Pos3/0/0
RSVP TE
LSP Index
LSP ID
Lsp Type
Resv Style
: 2049
: 32770
: Hot-Standby
SE
352
3 MPLS TE Configuration
IncludeAnyAff
: 0x0
ExcludeAnyAff
: 0x0
IncludeAllAff
: 0x0
LspConstraint
: 1
ER-Hop Table Index
: 1
AR-Hop Table Index: 1
C-Hop Table Index
: PrevTunnelIndexInSession: NextTunnelIndexInSession: 0
PSB Handle
: 1025
Created Time
: 2010/07/01 17:40:36 UTC-08:00
-------------------------------DS-TE Information
-------------------------------Bandwidth Reserved Flag : Unreserved
CT0 Bandwidth(Kbit/sec) : 0
CT1 Bandwidth(Kbit/sec): 0
CT2 Bandwidth(Kbit/sec) : 0
CT3 Bandwidth(Kbit/sec): 0
CT4 Bandwidth(Kbit/sec) : 0
CT5 Bandwidth(Kbit/sec): 0
CT6 Bandwidth(Kbit/sec) : 0
CT7 Bandwidth(Kbit/sec): 0
Setup-Priority
: 5
Hold-Priority
: 5
-------------------------------FRR Information
-------------------------------Primary LSP Info
TE Attribute Flag
: 0x3
Protected Flag
: 0x0
Bypass In Use
: Not Exists
Bypass Tunnel Id
: BypassTunnel
: Bypass Lsp ID
: FrrNextHop
: ReferAutoBypassHandle
: FrrPrevTunnelTableIndex : FrrNextTunnelTableIndex: Bypass Attribute(Not configured)
Setup Priority
: Hold Priority
: HopLimit
: Bandwidth
: IncludeAnyGroup
: ExcludeAnyGroup
: IncludeAllGroup
: Bypass Unbound Bandwidth Info(Kbit/sec)
CT0 Unbound Bandwidth
: CT1 Unbound Bandwidth: CT2 Unbound Bandwidth
: CT3 Unbound Bandwidth: CT4 Unbound Bandwidth
: CT5 Unbound Bandwidth: CT6 Unbound Bandwidth
: CT7 Unbound Bandwidth: -------------------------------BFD Information
-------------------------------NextSessionTunnelIndex : PrevSessionTunnelIndex: NextLspId
: PrevLspId
: -
# After shutting down POS 1/0/0 on LSR C and POS 1/0/0 on LSR B, you can see that the LSP
attribute template is used to set up an ordinary CR-LSP.
<LSRA> display mpls te tunnel verbose
No
: 1
Tunnel-Name
: Tunnel1/0/0
TunnelIndex
: 0
LSP Index
: 2048
Session ID
: 100
LSP ID
: 32771
Lsr Role
: Ingress
Lsp Type
: Ordinary
Ingress LSR ID
: 1.1.1.1
Egress LSR ID
: 4.4.4.4
In-Interface
: Out-Interface
: Pos2/0/0
Sign-Protocol
: RSVP TE
Resv Style
: SE
IncludeAnyAff
: 0x0
ExcludeAnyAff
: 0x0
IncludeAllAff
: 0x0
LspConstraint
: 1
ER-Hop Table Index
: 2
AR-Hop Table Index: 0
C-Hop Table Index
: PrevTunnelIndexInSession: NextTunnelIndexInSession: PSB Handle
: 1212
Created Time
: 2010/07/02 15:24:18 UTC-08:00
-------------------------------DS-TE Information
-------------------------------Bandwidth Reserved Flag : Unreserved
Issue 02 (2011-09-10)
353
3 MPLS TE Configuration
CT0 Bandwidth(Kbit/sec) : 0
CT1 Bandwidth(Kbit/sec): 0
CT2 Bandwidth(Kbit/sec) : 0
CT3 Bandwidth(Kbit/sec): 0
CT4 Bandwidth(Kbit/sec) : 0
CT5 Bandwidth(Kbit/sec): 0
CT6 Bandwidth(Kbit/sec) : 0
CT7 Bandwidth(Kbit/sec): 0
Setup-Priority
: 5
Hold-Priority
: 5
-------------------------------FRR Information
-------------------------------Primary LSP Info
TE Attribute Flag
: 0x3
Protected Flag
: 0x0
Bypass In Use
: Not Exists
Bypass Tunnel Id
: BypassTunnel
: Bypass Lsp ID
: FrrNextHop
: ReferAutoBypassHandle
: FrrPrevTunnelTableIndex : FrrNextTunnelTableIndex: Bypass Attribute(Not configured)
Setup Priority
: Hold Priority
: HopLimit
: Bandwidth
: IncludeAnyGroup
: ExcludeAnyGroup
: IncludeAllGroup
: Bypass Unbound Bandwidth Info(Kbit/sec)
CT0 Unbound Bandwidth
: CT1 Unbound Bandwidth: CT2 Unbound Bandwidth
: CT3 Unbound Bandwidth: CT4 Unbound Bandwidth
: CT5 Unbound Bandwidth: CT6 Unbound Bandwidth
: CT7 Unbound Bandwidth: -------------------------------BFD Information
-------------------------------NextSessionTunnelIndex : PrevSessionTunnelIndex: NextLspId
: PrevLspId
: -
----End
Configuration Files
l
Issue 02 (2011-09-10)
354
3 MPLS TE Configuration
#
lsp-attribute lsp_attribute_3
explicit-path middle_path
priority 5
commit
#
interface Pos1/0/0
ip address 10.1.1.1 255.255.255.0
mpls
mpls te
mpls rsvp-te
#
interface Pos2/0/0
ip address 10.1.3.1 255.255.255.0
mpls
mpls te
mpls rsvp-te
#
interface Pos3/0/0
ip address 10.1.2.1 255.255.255.0
mpls
mpls te
mpls rsvp-te
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
interface Tunnel1/0/0
tunnel-protocol mpls te
destination 4.4.4.4
mpls te tunnel-id 100
mpls te primary-lsp-constraint lsp-attribute lsp_attribute_1
mpls te hotstandby-lsp-constraint 1 lsp-attribute lsp_attribute_2
mpls te ordinary-lsp-constraint 1 lsp-attribute lsp_attribute_3
mpls te commit
#
ospf 1
opaque-capability enable
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 10.1.1.0 0.0.0.255
network 10.1.2.0 0.0.0.255
network 10.1.3.0 0.0.0.255
mpls-te enable
#
return
Issue 02 (2011-09-10)
355
3 MPLS TE Configuration
opaque-capability enable
area 0.0.0.0
network 10.1.2.0 0.0.0.255
network 10.1.5.0 0.0.0.255
mpls-te enable
#
return
Issue 02 (2011-09-10)
356
3 MPLS TE Configuration
area 0.0.0.0
network 4.4.4.4 0.0.0.0
network 10.1.4.0 0.0.0.255
network 10.1.5.0 0.0.0.255
network 10.1.6.0 0.0.0.255
mpls-te enable
#
return
Networking Requirements
On the network shown in Figure 3-7, Eth-Trunk 1 member interfaces on LSR A and LSR B are
GE 1/0/0, GE 2/0/0, and GE 3/0/0. An MPLS TE tunnel using RSVP is established between
LSR A and LSR C.
The handshake function is required to implement RSVP key authentication between LSR A and
LSR B and prevent forged RSVP requests for reserving resources from causing resource
exhaustion. In addition, the message window function is required to prevent RSVP message missequence.
Issue 02 (2011-09-10)
357
3 MPLS TE Configuration
Loopback1
Loopback1
1.1.1.1/32
2.2.2.2/32
Eth-Trunk 1 Eth-Trunk 1
10.1.1.1/24 10.1.1.2/24
LSRA
GE1/0/0
GE2/0/0
GE3/0/0
Loopback1
3.3.3.3/32
GE4/0/0
GE1/0/0
GE1/0/0
LSRB 20.1.1.1/24 20.1.1.2/24 LSRC
GE2/0/0
GE3/0/0
Configuration Roadmap
The configuration roadmap is as follows:
1.
2.
3.
4.
Configure the window size on every interface to enable the interface to save 32 sequence
numbers.
NOTE
Setting the size of a sliding window to be a value larger than 32 is recommended. If the size of a sliding
window is too small, received RSVP messages with the sequence number beyond the window size are
discarded, resulting in the termination of an RSVP neighbor relationship.
Data Preparation
To complete the configuration, you need the following data:
l
Procedure
Step 1 Configure the IP address for each interface.
Configure the IP address and mask of each interface as shown in Figure 3-7. For detailed
configuration, see configuration files in this example.
Step 2 Configure OSPF.
Configure OSPF on all LSRs to advertise the route to the network segment of each interface and
the host route of each LSR ID. For detailed configuration, see configuration files in this example.
After the configuration, run the display ip routing-table command on each LSR. You can view
that the LSRs have learned routes from each other.
Step 3 Configure basic MPLS functions and enable MPLS TE, MPLS RSVP-TE, and CSPF.
# Configure LSR A.
Issue 02 (2011-09-10)
358
3 MPLS TE Configuration
The configurations of LSR B and LSR C are similar to that of LSR A, and are not provided here.
# Configure LSR B.
[LSRB] ospf 1
[LSRB-ospf-1] opaque-capability enable
[LSRB-ospf-1] area 0
[LSRB-ospf-1-area-0.0.0.0] mpls-te enable
[LSRB-ospf-1-area-0.0.0.0] quit
# Configure LSR C.
[LSRC] ospf 1
[LSRC-ospf-1] opaque-capability enable
[LSRC-ospf-1] area 0
[LSRC-ospf-1-area-0.0.0.0] mpls-te enable
[LSRC-ospf-1-area-0.0.0.0] quit
After the configuration, run the display interface tunnel command on LSR A. You can view
the tunnel interface is Up.
[LSRA] display interface tunnel 1/0/0
Tunnel1/0/0 current state : UP
Line protocol current state : UP
Last up time: 2007-9-27, 16:38:41
Description : Tunnel1/0/0 Interface, Route Port
...
Step 6 Configure the RSVP authentication on interfaces of the MPLS TE links on LSR A and LSR B.
# Configure LSR A.
[LSRA] interface eth-trunk 1
Issue 02 (2011-09-10)
359
3 MPLS TE Configuration
# Configure LSR B.
[LSRB] interface eth-trunk 1
[LSRB-Eth-Trunk1] mpls rsvp-te authentication plain 123456789
[LSRB-Eth-Trunk1] mpls rsvp-te authentication handshake 12345678
[LSRB-Eth-Trunk1] mpls rsvp-te authentication window-size 32
eth-trunk 1
Interface Index: 0x406
Used-BW: 0
Num of Neighbors: 1
SRefresh Interval: 30 sec
Retransmit Interval: 500 msec
WindowSize: 32
Key ID: d5d7adf41800
Bfd Min-Tx: 10
Bfd Detect-Multi: 3
----End
Configuration Files
l
Issue 02 (2011-09-10)
360
3 MPLS TE Configuration
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
interface Tunnel1/0/0
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 3.3.3.3
mpls te tunnel-id 1
mpls te commit
#
ospf 1
opaque-capability enable
area 0.0.0.0
network 10.1.1.0 0.0.0.255
network 1.1.1.1 0.0.0.0
mpls-te enable
#
return
l
Issue 02 (2011-09-10)
361
3 MPLS TE Configuration
#
sysname LSRC
#
mpls lsr-id 3.3.3.3
mpls
mpls te
mpls rsvp-te
#
interface GigabiEthernet1/0/0
ip address 20.1.1.2 255.255.255.0
mpls
mpls te
mpls rsvp-te
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
ospf 1
opaque-capability enable
area 0.0.0.0
network 20.1.1.0 0.0.0.255
network 3.3.3.3 0.0.0.0
mpls-te enable
#
Return
Networking Requirements
Figure 3-8 Networking diagram of configuring tunnel properties
Loopback1
1.1.1.1/32
Loopback1
Loopback1
2.2.2.2/32
3.3.3.3/32
POS2/0/0
POS1/0/0
192.168.2.1/24 192.168.2.2/24
POS1/0/0
192.168.1.1/24
POS1/0/0
POS2/0/0 LSRC
LSRA
192.168.1.2/24 LSRB POS3/0/0
192.168.3.1/24 192.168.3.2/24
On the network shown in Figure 3-8, the maximum reservable bandwidth is 100 Mbit/s. The
RDM is used and the bandwidth of BC0 is 100 Mbit/s.
LSR A has two tunnels to LSR C, namely, Tunnel 1/0/0 and Tunnel 1/0/1, each of which requires
the bandwidth of 40 Mbit/s. These two tunnels provide the total bandwidth of 80 Mbit/s, greater
than the bandwidth (50 Mbit/s) of the link between LSR A and LSR B. In addition, Tunnel 1/0/1
has a higher priority than Tunnel 1/0/0, and preemption is allowed.
It is required to use the tunnel affinity property and mask based on the administrative group
property. Tunnel 1/0/0 on LSR A uses one physical link from LSR B to LSR C and Tunnel 1/0/1
uses another physical link from LSR B to LSR C.
Issue 02 (2011-09-10)
362
3 MPLS TE Configuration
Configuration Roadmap
The configuration roadmap is as follows:
1.
2.
Configure the administrative group properties of the outgoing interface of the tunnel on
each node along the tunnel.
3.
Determine the affinity property and the mask of each tunnel based on the administrative
group properties and the networking requirements.
4.
Data Preparation
To complete the configuration, you need the following data:
l
Maximum reservable bandwidth and BC bandwidth for the link along the tunnel
Administrative group property of the link LSR A --> LSR B and administrative group
property of the link LSR B --> LSR C
Tunnel interface name, IP address, destination address, tunnel ID, tunnel bandwidth, tunnel
priority, and tunnel signaling protocol (by default, RSVP-TE is used.)
Procedure
Step 1 Configure IP addresses for the interfaces.
On the network shown in Figure 3-8, configure the IP address and mask for interfaces, including
the loopback interface.
The detailed configuration is not provided here.
Step 2 Configure the IGP protocol.
Configure OSPF on all LSRs to advertise the route to network segment of each interface and
LSR ID.
The detailed configuration is not provided here.
Step 3 Configure the basic MPLS functions, and enable MPLS TE, RSVP-TE, and OSPF TE. Enable
CSPF on the ingress.
# Configure the basic MPLS functions, and enable MPLS TE and RSVP-TE on LSR A, LSR B,
and LSR C.
Take LSR A as an example.
[LSRA] mpls lsr-id 1.1.1.1
[LSRA] mpls
[LSRA-mpls] mpls te
[LSRA-mpls] mpls rsvp-te
[LSRA-mpls] quit
[LSRA] interface pos 1/0/0
[LSRA-Pos1/0/0] mpls
[LSRA-Pos1/0/0] mpls te
[LSRA-Pos1/0/0] mpls rsvp-te
Issue 02 (2011-09-10)
363
3 MPLS TE Configuration
[LSRA-Pos1/0/0] quit
# Configure OSPF TE on LSR A, LSR B, and LSR C. Use the display on LSR A as an example.
[LSRA] ospf
[LSRA-ospf-1] opaque-capability enable
[LSRA-ospf-1] area 0
[LSRA-ospf-1-area-0.0.0.0] mpls-te enable
[LSRA-ospf-1-area-0.0.0.0] quit
[LSRA-ospf-1] quit
The configurations of LSR B and LSR C are similar to that of LSR A, and are not provided here.
# Enable CSPF on LSR A, the ingress node.
[LSRA] mpls
[LSRA-mpls] mpls te cspf
[LSRA-mpls] quit
# Set the administrative group property to 0x10001 for the link on LSR A.
[LSRA-Pos1/0/0] mpls te link administrative group 10001
[LSRA-Pos1/0/0] quit
2/0/0
te bandwidth max-reservable-bandwidth 100000
te bandwidth bc0 100000
te link administrative group 10101
3/0/0
te bandwidth max-reservable-bandwidth 100000
te bandwidth bc0 100000
After the configuration, check the TEDB on LSR A for the following properties:
l Maximum bandwidth
l Maximum reservable bandwidth
l Color field, that is, the administrative group property of the links
[LSRA] display mpls te cspf tedb node
Router ID: 1.1.1.1
IGP Type: OSPF
Process Id: 1
MPLS-TE Link Count: 1
Link[1]:
Interface IP Address(es): 192.168.1.1
Peer IP Address: 192.168.1.2
Peer Router Id: 2.2.2.2
Peer OSPF Router Id: 2.2.2.2
IGP Area: 0
Link Type: point-to-point Link Status: Active
IGP Metric: 1
TE Metric: 1
Color: 0x10001
Bandwidth Allocation Model : Russian Doll Model
Maximum Link-Bandwidth: 100000 (kbps)
Maximum Reservable Bandwidth: 100000 (kbps)
Bandwidth Constraints:
Local Overbooking Multiplier:
BC[0]: 100000
(kbps)
LOM[0]: 1
Issue 02 (2011-09-10)
364
3 MPLS TE Configuration
BC[1]: 0
BW Unreserved:
Class ID:
(kbps)
LOM[1]:
[0]:
100000 (kbps),
[1]:
100000 (kbps)
[2]:
100000 (kbps),
[3]:
100000 (kbps)
[4]:
100000 (kbps),
[5]:
100000 (kbps)
[6]:
100000 (kbps),
[7]:
100000 (kbps)
[8]:
0 (kbps),
[9]:
0 (kbps)
[10]:
0 (kbps),
[11]:
0 (kbps)
[12]:
0 (kbps),
[13]:
0 (kbps)
[14]:
0 (kbps),
[15]:
0 (kbps)
BW Unreserved:
Class ID:
[0]:
0 (kbps),
[1]:
0 (kbps)
[2]:
0 (kbps),
[3]:
0 (kbps)
[4]:
0 (kbps),
[5]:
0 (kbps)
[6]:
0 (kbps),
[7]:
0 (kbps)
[8]:
0 (kbps),
[9]:
0 (kbps)
[10]:
0 (kbps),
[11]:
0 (kbps)
[12]:
0 (kbps),
[13]:
0 (kbps)
[14]:
0 (kbps),
[15]:
0 (kbps)
Router ID: 2.2.2.2
IGP Type: OSPF
Process Id: 1
MPLS-TE Link Count: 3
Link[1]:
Interface IP Address(es): 192.168.2.1
Peer IP Address: 192.168.2.2
Peer Router Id: 3.3.3.3
Peer OSPF Router Id: 3.3.3.3
IGP Area: 0
Link Type: point-to-point Link Status: Active
IGP Metric: 1
TE Metric: 1
Color: 0x10101
Bandwidth Allocation Model : Russian Doll Model
Maximum Link-Bandwidth: 100000 (kbps)
Maximum Reservable Bandwidth: 100000 (kbps)
Bandwidth Constraints:
Local Overbooking Multiplier:
BC[0]: 100000
(kbps)
LOM[0]: 1
BC[1]: 0
(kbps)
LOM[1]: 1
BW Unreserved:
Class ID:
[0]:
100000 (kbps),
[1]:
[2]:
100000 (kbps),
[3]:
[4]:
100000 (kbps),
[5]:
[6]:
100000 (kbps),
[7]:
[8]:
0 (kbps),
[9]:
[10]:
0 (kbps),
[11]:
[12]:
0 (kbps),
[13]:
[14]:
0 (kbps),
[15]:
BW Unreserved:
Class ID:
[0]:
0 (kbps),
[1]:
[2]:
0 (kbps),
[3]:
[4]:
0 (kbps),
[5]:
[6]:
0 (kbps),
[7]:
[8]:
0 (kbps),
[9]:
[10]:
0 (kbps),
[11]:
[12]:
0 (kbps),
[13]:
[14]:
0 (kbps),
[15]:
Link[2]:
Interface IP Address(es): 192.168.1.2
Peer IP Address: 192.168.1.1
Peer Router Id: 1.1.1.1
Peer OSPF Router Id: 1.1.1.1
IGP Area: 0
Link Type: point-to-point Link Status: Active
IGP Metric: 1
TE Metric: 1
Bandwidth Allocation Model : Russian Doll Model
Issue 02 (2011-09-10)
100000
100000
100000
100000
0
0
0
0
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
0
0
0
0
0
0
0
0
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
Color: 0x0
365
3 MPLS TE Configuration
Issue 02 (2011-09-10)
[1]:
[3]:
[5]:
[7]:
[9]:
[11]:
[13]:
[15]:
100000
100000
100000
100000
0
0
0
0
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
[1]:
[3]:
[5]:
[7]:
[9]:
[11]:
[13]:
[15]:
0
0
0
0
0
0
0
0
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
366
3 MPLS TE Configuration
Color: 0x0
Multiplier:
0
0
0
0
0
0
0
0
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
0
0
0
0
0
0
0
0
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
Color: 0x0
Multiplier:
0
0
0
0
0
0
0
0
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
0
0
0
0
0
0
0
0
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
(kbps)
Issue 02 (2011-09-10)
367
3 MPLS TE Configuration
[LSRA-Tunnel1/0/0]
[LSRA-Tunnel1/0/0]
[LSRA-Tunnel1/0/0]
[LSRA-Tunnel1/0/0]
[LSRA-Tunnel1/0/0]
[LSRA-Tunnel1/0/0]
destination 3.3.3.3
mpls te tunnel-id 100
mpls te bandwidth ct0 40000
mpls te affinity property 10101 mask 11011
mpls te commit
quit
The tunnels use the default setup and holding priorities, which are the lowest priority with the
value being 7.
The affinity property of the tunnel is 0x10101, and the mask is 0x11011, both of which match
the administrative group property of the links along the tunnel.
After the configuration, check the status of the tunnel on LSR A.
[LSRA] display mpls te tunnel-interface
================================================================
Tunnel1/0/0
================================================================
Tunnel State Desc
: UP
Active LSP
: Primary LSP
Session ID
: 100
Ingress LSR ID
: 1.1.1.1
Egress LSR ID: 3.3.3.3
Admin State
: UP
Oper State
: UP
Primary LSP State
: UP
Main LSP State
: READY
LSP ID : 1
Check the TEDB. You can view the change of bandwidth used by the links.
[LSRA] display mpls te cspf tedb node
Router ID: 1.1.1.1
IGP Type: OSPF
Process Id: 1
MPLS-TE Link Count: 1
Link[1]:
Interface IP Address(es): 192.168.1.1
Peer IP Address: 192.168.1.2
Peer Router Id: 2.2.2.2
Peer OSPF Router Id: 2.2.2.2
IGP Area: 0
Link Type: point-to-point Link Status: Active
IGP Metric: 1
TE Metric: 1
Color: 0x10001
Bandwidth Allocation Model : Russian Doll Model
Maximum Link-Bandwidth: 100000 (kbps)
Maximum Reservable Bandwidth: 100000 (kbps)
Bandwidth Constraints:
Local Overbooking Multiplier:
BC[0]: 100000
(kbps)
LOM[0]: 1
BC[1]: 0
(kbps)
LOM[1]: 1
BW Unreserved:
Class ID:
[0]:
100000 (kbps),
[1]:
100000 (kbps)
[2]:
100000 (kbps),
[3]:
100000 (kbps)
[4]:
100000 (kbps),
[5]:
100000 (kbps)
[6]:
100000 (kbps),
[7]:
60000 (kbps)
[8]:
0 (kbps),
[9]:
0 (kbps)
[10]:
0 (kbps),
[11]:
0 (kbps)
[12]:
0 (kbps),
[13]:
0 (kbps)
[14]:
0 (kbps),
[15]:
0 (kbps)
BW Unreserved:
Class ID:
[0]:
0 (kbps),
[1]:
0 (kbps)
[2]:
0 (kbps),
[3]:
0 (kbps)
[4]:
0 (kbps),
[5]:
0 (kbps)
[6]:
0 (kbps),
[7]:
0 (kbps)
[8]:
0 (kbps),
[9]:
0 (kbps)
[10]:
0 (kbps),
[11]:
0 (kbps)
[12]:
0 (kbps),
[13]:
0 (kbps)
[14]:
0 (kbps),
[15]:
0 (kbps)
Router ID: 2.2.2.2
IGP Type: OSPF
Process Id: 1
Issue 02 (2011-09-10)
368
3 MPLS TE Configuration
Issue 02 (2011-09-10)
369
3 MPLS TE Configuration
Link[3]:
Interface IP Address(es): 192.168.3.1
Peer IP Address: 192.168.3.2
Peer Router Id: 3.3.3.3
Peer OSPF Router Id: 3.3.3.3
IGP Area: 0
Link Type: point-to-point Link Status: Active
IGP Metric: 1
TE Metric: 1
Color: 0x10011
Bandwidth Allocation Model : Russian Doll Model
Maximum Link-Bandwidth: 100000 (kbps)
Maximum Reservable Bandwidth: 100000 (kbps)
Bandwidth Constraints:
Local Overbooking Multiplier:
BC[0]: 100000
(kbps)
LOM[0]: 1
BC[1]: 0
(kbps)
LOM[1]: 1
BW Unreserved:
Class ID:
[0]:
100000 (kbps),
[1]:
100000 (kbps)
[2]:
100000 (kbps),
[3]:
100000 (kbps)
[4]:
100000 (kbps),
[5]:
100000 (kbps)
[6]:
100000 (kbps),
[7]:
100000 (kbps)
[8]:
0 (kbps),
[9]:
0 (kbps)
[10]:
0 (kbps),
[11]:
0 (kbps)
[12]:
0 (kbps),
[13]:
0 (kbps)
[14]:
0 (kbps),
[15]:
0 (kbps)
BW Unreserved:
Class ID:
[0]:
0 (kbps),
[1]:
0 (kbps)
[2]:
0 (kbps),
[3]:
0 (kbps)
[4]:
0 (kbps),
[5]:
0 (kbps)
[6]:
0 (kbps),
[7]:
0 (kbps)
[8]:
0 (kbps),
[9]:
0 (kbps)
[10]:
0 (kbps),
[11]:
0 (kbps)
[12]:
0 (kbps),
[13]:
0 (kbps)
[14]:
0 (kbps),
[15]:
0 (kbps)
Router ID: 3.3.3.3
IGP Type: OSPF
Process Id: 1
MPLS-TE Link Count: 2
Link[1]:
Interface IP Address(es): 192.168.2.2
Peer IP Address: 192.168.2.1
Peer Router Id: 2.2.2.2
Peer OSPF Router Id: 2.2.2.2
IGP Area: 0
Link Type: point-to-point Link Status: Active
IGP Metric: 1
TE Metric: 1
Color: 0x0
Bandwidth Allocation Model : Russian Doll Model
Maximum Link-Bandwidth: 0 (kbps)
Maximum Reservable Bandwidth: 0
(kbps)
Bandwidth Constraints:
Local Overbooking Multiplier:
BC[0]: 0
(kbps)
LOM[0]: 1
BC[1]: 0
(kbps)
LOM[1]: 1
BW Unreserved:
Class ID:
[0]:
0 (kbps),
[1]:
0 (kbps)
[2]:
0 (kbps),
[3]:
0 (kbps)
[4]:
0 (kbps),
[5]:
0 (kbps)
[6]:
0 (kbps),
[7]:
0 (kbps)
[8]:
0 (kbps),
[9]:
0 (kbps)
[10]:
0 (kbps),
[11]:
0 (kbps)
[12]:
0 (kbps),
[13]:
0 (kbps)
[14]:
0 (kbps),
[15]:
0 (kbps)
BW Unreserved:
Class ID:
[0]:
0 (kbps),
[1]:
0 (kbps)
[2]:
0 (kbps),
[3]:
0 (kbps)
[4]:
0 (kbps),
[5]:
0 (kbps)
[6]:
0 (kbps),
[7]:
0 (kbps)
[8]:
0 (kbps),
[9]:
0 (kbps)
[10]:
0 (kbps),
[11]:
0 (kbps)
Issue 02 (2011-09-10)
370
3 MPLS TE Configuration
[12]:
0 (kbps),
[13]:
0 (kbps)
[14]:
0 (kbps),
[15]:
0 (kbps)
Link[2]:
Interface IP Address(es): 192.168.3.2
Peer IP Address: 192.168.3.1
Peer Router Id: 2.2.2.2
Peer OSPF Router Id: 2.2.2.2
IGP Area: 0
Link Type: point-to-point Link Status: Active
IGP Metric: 1
TE Metric: 1
Color: 0x0
Bandwidth Allocation Model : Russian Doll Model
Maximum Link-Bandwidth: 0 (kbps)
Maximum Reservable Bandwidth: 0 (kbps)
Bandwidth Constraints:
Local Overbooking Multiplier:
BC[0]: 0
(kbps)
LOM[0]: 1
BC[1]: 0
(kbps)
LOM[1]: 1
BW Unreserved:
Class ID:
[0]:
0 (kbps),
[1]:
0 (kbps)
[2]:
0 (kbps),
[3]:
0 (kbps)
[4]:
0 (kbps),
[5]:
0 (kbps)
[6]:
0 (kbps),
[7]:
0 (kbps)
[8]:
0 (kbps),
[9]:
0 (kbps)
[10]:
0 (kbps),
[11]:
0 (kbps)
[12]:
0 (kbps),
[13]:
0 (kbps)
[14]:
0 (kbps),
[15]:
0 (kbps)
BW Unreserved:
Class ID:
[0]:
0 (kbps),
[1]:
0 (kbps)
[2]:
0 (kbps),
[3]:
0 (kbps)
[4]:
0 (kbps),
[5]:
0 (kbps)
[6]:
0 (kbps),
[7]:
0 (kbps)
[8]:
0 (kbps),
[9]:
0 (kbps)
[10]:
0 (kbps),
[11]:
0 (kbps)
[12]:
0 (kbps),
[13]:
0 (kbps)
[14]:
0 (kbps),
[15]:
0 (kbps)
BW Unreserved for Class type 0 indicates the available bandwidth from the maximum
reservable bandwidth for various priorities. The command output shows that the unreserved
bandwidth changes for CT 7 on the outgoing interfaces on each LSR along the tunnel. This
means that some tunnels succeed in reserving 40 Mbit/s bandwidth with the priority being 7.
The bandwidth allocation also shows the path that the tunnel uses. This indicates that the affinity
property and the mask of the tunnel must match the administrative group property of the links.
Run the display mpls te tunnel command on LSR B. You can view the outgoing interface of
the tunnel.
[LSRB] display mpls te tunnel
-----------------------------------------------------------------------------Ingress LsrId
Destination
LSPID
In/Out Label
R Tunnel-name
-----------------------------------------------------------------------------1.1.1.1
3.3.3.3
1
3/-I Tunnel1/0/0
Issue 02 (2011-09-10)
371
3 MPLS TE Configuration
----End
Configuration Files
l
Issue 02 (2011-09-10)
372
3 MPLS TE Configuration
mpls te commit
#
ospf 1
opaque-capability enable
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 192.168.1.0 0.0.0.255
mpls-te enable
#
return
Issue 02 (2011-09-10)
373
3 MPLS TE Configuration
interface Pos1/0/0
link-protocol ppp
ip address 192.168.2.2 255.255.255.0
mpls
mpls te
mpls rsvp-te
#
interface Pos2/0/0
link-protocol ppp
ip address 192.168.3.2 255.255.255.0
mpls
mpls te
mpls rsvp-te
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
ospf 1
opaque-capability enable
area 0.0.0.0
network 3.3.3.3 0.0.0.0
network 192.168.2.0 0.0.0.255
network 192.168.3.0 0.0.0.255
mpls-te enable
#
return
Networking Requirements
Figure 3-9 shows a networking diagram of an MPLS network. An RSVP-TE tunnel has been
set up between PE1 and PE2, the path of the tunnel is PE1 --> P1 --> PE2, and the outbound
interface of the tunnel on P1 is GE 2/0/0.
Links to network segments 10.2.1.0/30 and 10.5.1.0/30 are in SRLG 1.
To enhance the reliability of the tunnel, it is required that TE Auto FRR be enabled on P1 and
that the auto bypass tunnel's path is preferred to avoid the links that have a member in the same
SRLG as the link of the primary tunnel. If no path is available, the path calculation is performed
regardless of the SRLG attribute.
Issue 02 (2011-09-10)
374
3 MPLS TE Configuration
Loopback1
2.2.2.2/32
P2
GE1/0/0
10.3.1.2/30
Loopback1
4.4.4.4/32
GE4/0/0
10.3.1.1 /30
P1
PE1
G
10 E2/
.4. 0/0
1.1
/30
10 GE3
.4.
1.2 /0/0
/30
GE2/0/0
GE1/0/0
SRLG 2
10.2.1.1/30
10.2.1.2/30
PE2
SRLG1
GE2/0/0
GE3/0/0
SRLG1
GE1/0/0
GE1/0/0
10.1.1.1/30
10.1.1.2/30
10.5.1.2/30
10.5.1.1/30
Loopback1
Loopback1
1.1.1.1/32
5.5.5.5/32
Path of the primary CR-LSP
Configuration Roadmap
The configuration roadmap is as follows:
1.
2.
Enable MPLS, MPLS TE and MPLS RSVP-TE globally and in the interfaces view of each
node.
3.
Configure IS-IS TE on each node and enable CSPF on PE1 and P1.
4.
5.
Configure the SRLG path calculation mode in the system view on the PLR node.
6.
Set up an RSVP-TE tunnel between PE1 and PE2, with the explicit path being PE1 --> P1
--> PE2.
7.
Enable TE FRR in the tunnel interface view of the ingress and enable TE Auto FRR on the
outbound interface of the primary tunnel on PLR node.
Data Preparation
To complete the configuration, you need the following data:
l
SRLG number
Procedure
Step 1 Configure an IP address for each interface.
Issue 02 (2011-09-10)
375
3 MPLS TE Configuration
As shown in Figure 3-9, configure an IP address for each interface, create loopback interface
on each node, and then configure the IP address of the loopback interface as the MPLS LSR ID.
For configuration details, see the configuration file of this example, and are not provided here.
Step 2 Configure an IGP.
Configure OSPF or IS-IS on each node to ensure that nodes can communicate with each other.
The example in this document use IS-IS. For configuration details, see the configuration file of
this example.
Step 3 Configure basic MPLS functions.
On each node, configure an LSR ID and enable MPLS in the system view. Enable MPLS in the
interface view. For configuration details, see the configuration file of this example.
Step 4 Configure basic MPLS TE functions.
On each node, enable MPLS-TE and MPLS RSVP-TE in the MPLS view and in the interface
view. Configure the maximum bandwidth and maximum reservable bandwidth for each
interface. For configuration details, see the configuration file of this example.
Step 5 Configure IS-IS TE and CSPF.
Configure IS-IS TE on each node and CSPF on PE1 and P1. For configuration details, see the
configuration file of this example.
Step 6 Configure SRLG
# On P1, add links to network segments 10.2.1.0/30 10.5.1.0/30 to SRLG 1.
[P1] interface gigabitethernet
[P1-GigabitEthernet2/0/0] mpls
[P1-GigabitEthernet2/0/0] quit
[P1] interface gigabitethernet
[P1-GigabitEthernet3/0/0] mpls
[P1-GigabitEthernet3/0/0] quit
2/0/0
te srlg 1
3/0/0
te srlg 1
# Run the display mpls te srlg command on P1, and you can view information about the SRLG
and the interfaces that belong to the SRLG.
[P1] display mpls te srlg all
Total SRLG supported : 512
Total SRLG configured : 2
SRLG
1:
GE2/0/0
GE3/0/0
# Run the display mpls te link-administration srlg-information command on P1, and you can
view information about the SRLG memberships of the interfaces.
[P1] display mpls te link-administration srlg-information
SRLGs on GigabitEthernet2/0/0:
1
SRLGs on GigabitEthernet3/0/0:
1
# Run the display mpls te cspf tedb srlg command on P1, and you can view TEDB information
of the specified SRLG.
Issue 02 (2011-09-10)
376
3 MPLS TE Configuration
Area
1
1
2
2
# Run the display interface tunnel 1/0/0 command on PE1, and you can see that the status of
the tunnel is Up.
[PE1] display interface tunnel 1/0/0
Tunnel1/0/0 current state : UP
Line protocol current state : UP
...
NOTE
Take note of the preceding items that appear in the display interface tunnel 1/0/0 command output.
Information in "..." can be ignored.
Run the display mpls te tunnel path Tunnel1/0/0 command on PE1, and you can see that the
local protection is available on the outbound interface (10.2.1.1) of the primary tunnel on P1.
Issue 02 (2011-09-10)
377
3 MPLS TE Configuration
:
:
:
3072
1
Primary
:
:
SE
0x0
Issue 02 (2011-09-10)
378
3 MPLS TE Configuration
-------------------------------NextSessionTunnelIndex : NextLspId
: -
PrevSessionTunnelIndex:
PrevLspId
: -
# Run the display mpls te tunnel path Tunnel0/0/2048 command on the P1 to check the path
of the bypass tunnel, you can see that the path of the bypass tunnel is P1-->P2-->PE2.
[P1] display mpls te tunnel path Tunnel0/0/2048
Tunnel Interface Name : Tunnel0/0/2048
Lsp ID : 1.1.1.1 :2049 :1
Hop Information
Hop 0
10.3.1.1
Hop 1
10.3.1.2
Hop 2
2.2.2.2
Hop 3
10.4.1.1
Hop 4
10.4.1.2
Hop 5
5.5.5.5
# Run the display interface tunnel 1/0/0 command on PE1, and you can see that the status of
the primary tunnel is Up.
[PE1] display interface tunnel 1/0/0
Tunnel1/0/0 current state : UP
Line protocol current state : UP
...
NOTE
Take note of the preceding items that appear in the display interface tunnel 1/0/0 command output.
Information in "..." can be ignored.
# Run the display mpls te tunnel name Tunnel1/0/0 verbose command on P1, and you can
see that the primary tunnel is still bound with the tunnel 0/0/2048 and the FRR next hop is
10.5.1.2.
<P1> display mpls te tunnel name Tunnel1/0/0 verbose
No
: 1
Tunnel-Name
: Tunnel1/0/0
TunnelIndex
: 1
LSP Index
: 2048
Session ID
: 100
LSP ID
: 1
Lsr Role
: Transit
Ingress LSR ID
: 4.4.4.4
Egress LSR ID
: 5.5.5.5
In-Interface
: GE1/0/0
Out-Interface
: GE2/0/0
Sign-Protocol
: RSVP TE
Resv Style
: SE
IncludeAnyAff
: 0x0
ExcludeAnyAff
: 0x0
IncludeAllAff
: 0x0
ER-Hop Table Index
: AR-Hop Table Index: 5
C-Hop Table Index
: PrevTunnelIndexInSession: NextTunnelIndexInSession:
PSB Handle
: 65547
Created Time
: 2009/03/30 09:52:03
-------------------------------DS-TE Information
-------------------------------Bandwidth Reserved Flag : Reserved
CT0 Bandwidth(Kbit/sec) : 10000
CT1 Bandwidth(Kbit/sec):
CT2 Bandwidth(Kbit/sec) : 0
CT3 Bandwidth(Kbit/sec):
CT4 Bandwidth(Kbit/sec) : 0
CT5 Bandwidth(Kbit/sec):
CT6 Bandwidth(Kbit/sec) : 0
CT7 Bandwidth(Kbit/sec):
Setup-Priority
: 7
Hold-Priority
: 7
--------------------------------
Issue 02 (2011-09-10)
0
0
0
0
379
3 MPLS TE Configuration
FRR Information
-------------------------------Primary LSP Info
TE Attribute Flag
: 0x63
Protected Flag
: 0x1
Bypass In Use
: Not Used
Bypass Tunnel Id
: 201359400
BypassTunnel
: Tunnel Index[Tunnel0/0/2048], InnerLabel[3]
Bypass Lsp ID
: FrrNextHop
: 10.5.1.2
ReferAutoBypassHandle
: 2049
FrrPrevTunnelTableIndex : FrrNextTunnelTableIndex: Bypass Attribute(Not configured)
Setup Priority
: Hold Priority
: HopLimit
: Bandwidth
: IncludeAnyGroup
: ExcludeAnyGroup
: IncludeAllGroup
: Bypass Unbound Bandwidth Info(Kbit/sec)
CT0 Unbound Bandwidth
: CT1 Unbound Bandwidth: CT2 Unbound Bandwidth
: CT3 Unbound Bandwidth: CT4 Unbound Bandwidth
: CT5 Unbound Bandwidth: CT6 Unbound Bandwidth
: CT7 Unbound Bandwidth: -------------------------------BFD Information
-------------------------------NextSessionTunnelIndex : PrevSessionTunnelIndex: NextLspId
: PrevLspId
: -
# Run the display mpls te tunnel path Tunnel0/0/2048 command on P1, you can see the path
of the auto bypass tunnel.
[P1] display mpls te tunnel path Tunnel0/0/2048
Tunnel Interface Name : Tunnel0/0/2048
Lsp ID : 123.1.1.1 :2049 :2
Hop Information
Hop 0
10.5.1.1
Hop 1
10.5.1.2
Hop 2
5.5.5.5
# You can see that the path of the auto bypass tunnel is P1-->PE2 rather than P1-->P2-->PE2.
That is because that the SRLG path calculation mode is configured as preferred. Therefore,
CSPF tries to calculate the path of the bypass tunnel to avoid the links in the same SRLG as the
protected interface(s); if the calculation fails, CSPF does not take the SRLG as a constraint.
----End
Configuration Files
l
Issue 02 (2011-09-10)
380
3 MPLS TE Configuration
Configuration file of P1
#
sysname P1
#
mpls lsr-id 1.1.1.1
mpls
mpls te
mpls rsvp-te
mpls te srlg path-calculation preferred
mpls te cspf
#
isis 1
cost-style wide
network-entity 10.0000.0000.0001.00
traffic-eng level-1-2
#
interface GigabitEthernet1/0/0
ip address 10.1.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls rsvp-te
#
interface GigabitEthernet2/0/0
ip address 10.2.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te auto-frr link
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls te srlg 1
mpls rsvp-te
#
interface GigabitEthernet3/0/0
ip address 10.5.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls te srlg 1
mpls rsvp-te
Issue 02 (2011-09-10)
381
3 MPLS TE Configuration
#
interface GigabitEthernet4/0/0
ip address 10.3.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls rsvp-te
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
isis enable 1
#
return
Configuration file of P2
#
sysname P2
#
mpls lsr-id 2.2.2.2
mpls
mpls te
mpls rsvp-te
#
isis 1
cost-style wide
network-entity 10.0000.0000.0002.00
traffic-eng level-1-2
#
interface GigabitEthernet1/0/0
ip address 10.3.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls rsvp-te
#
interface GigabitEthernet2/0/0
ip address 10.4.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls rsvp-te
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
isis enable 1
#
return
Issue 02 (2011-09-10)
382
3 MPLS TE Configuration
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls rsvp-te
#
interface GigabitEthernet2/0/0
ip address 10.5.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls rsvp-te
#
interface GigabitEthernet3/0/0
ip address 10.4.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls rsvp-te
#
interface LoopBack1
ip address 5.5.5.5 255.255.255.255
isis enable 1
#
return
Networking Requirements
Figure 3-10 shows a networking diagram of an MPLS network. An RSVP-TE tunnel has been
set up between the PE1 and PE2 and the path of the tunnel is PE1 --> P4 --> PE2.
The link PE1 --> P1--> P2 --> P4 and the link PE1 --> P4 are in the same SRLG (SRLG1 for
example); the link P4 --> PE2 and the link P4 --> P2 --> P3 --> PE2 are in the same SLRG (take
SRLG2 for example.)
To enhance the reliability of the tunnel, a hot standby CR-LSP is required and the backup tunnel's
path should avoid the links that have a member in the same SRLG as the link of the primary
tunnel.
Issue 02 (2011-09-10)
383
3 MPLS TE Configuration
Loopback1
Loopback1
Loopback1
2.2.2.2/32
3.3.3.3/32
1.1.1.1/32
GE1/0/0
GE2/0/0
GE2/0/0 GE1/0/0
10.4.1.1/30 10.4.1.2/30
10.2.1.1/3010.2.1.2/30
P1
GE1/0/0
10.1.1.2/30
P2
SRLG 2
GE3/0/0
10.5.1.1/30
P3
GE2/0/0
10.7.1.1/30
SRLG 1
GE1/0/0
10.1.1.1/30
PE1
P4
GE2/0/0
10.5.1.2 /30
PE2
GE2/0/0
10.7.1.2/30
GE3/0/0
GE1/0/0
GE3/0/0
GE1/0/0
GE3/0/0
GE2/0/0
10.8.1.2/30
10.3.1.1/30 10.3.1.2/30
10.6.1.1/30 10.6.1.2/30
10.8.1.1/30
Loopback1
Loopback1
Loopback1
5.5.5.5/32
4.4.4.4/32
6.6.6.6/32
Path of the primary CR-LSP
Configuration Roadmap
The configuration roadmap is as follows:
1.
2.
Enable MPLS, MPLS TE and MPLS RSVP-TE globally and in the interface view on all
nodes.
3.
Set up an RSVP-TE tunnel between PE1 and PE2, and the explicit path is PE1 --> P1 -->
PE2.
4.
Configure SRLG number on the outbound interface of the link that is in the same SRLG
as the link of the primary tunnel.
5.
Configure SRLG path calculation mode in the system view on the ingress.
6.
Data Preparation
To complete the configuration, you need the following data:
l
SRLG number
Procedure
Step 1 Configure an IP address for each interface.
As shown in Figure 3-10, configure an IP address for each interface, create the loopback
interface on each node, and then configure the IP addresses of the loopback interfaces as the
MPLS LSR ID. For configuration details, see the configuration file of this example.
Issue 02 (2011-09-10)
384
3 MPLS TE Configuration
Run the display interface tunnel 1/0/0 command on PE1, and you can see that the status of the
tunnel is Up.
[PE1] display interface tunnel 1/0/0
Tunnel1/0/0 current state : UP
Line protocol current state : UP
...
Issue 02 (2011-09-10)
385
3 MPLS TE Configuration
Take note of the preceding items that appear in the display interface tunnel 1/0/0 command
output. Information in "..." can be ignored.
Step 8 Configure SRLG
# Configure SRLG1 for the link PE1 --> P1 and the link PE1 --> P4.
[PE1] interface gigabitethernet
[PE1-GigabitEthernet1/0/0] mpls
[PE1-GigabitEthernet1/0/0] quit
[PE1] interface gigabitethernet
[PE1-GigabitEthernet2/0/0] mpls
[PE1-GigabitEthernet2/0/0] mpls
1/0/0
te srlg 1
2/0/0
te srlg 1
te srlg 2
Run the display mpls te srlg command, and you can view information about the SRLG and the
interfaces that belong to that SRLG.
[P1] display mpls te srlg all
Total SRLG supported : 512
Total SRLG configured : 2
SRLG
1:
GE1/0/0
SRLG
2:
GE2/0/0
GE2/0/0
Run the display mpls te link-administration srlg-information command, and you can view
information about the memberships on the interface.
[PE1] display mpls te link-administration srlg-information
SRLGs on GigabitEthernet1/0/0:
SRLGs on GigabitEthernet2/0/0:
Run the display mpls te cspf tedb srlg command, and you can view TEDB information of the
specified SRLG.
Take the display on PE1 as an example.
[PE1] display mpls te cspf tedb srlg 1
Interface-Address
IGP-Type
10.1.1.1
ISIS
10.1.1.1
ISIS
10.3.1.1
ISIS
10.3.1.1
ISIS
[PE1] display mpls te cspf tedb srlg 2
Interface-Address
IGP-Type
10.3.1.1
ISIS
10.3.1.1
ISIS
10.4.1.1
ISIS
10.4.1.1
ISIS
Area
1
2
1
2
Area
1
2
1
2
386
3 MPLS TE Configuration
Run the display mpls te hot-standby state interface tunnel 1/0/0 command on PE1, and you
can view information about the hot standby.
[PE1] display mpls te hot-standby state interface tunnel 1/0/0
---------------------------------------------------------------Verbose information about the Tunnel1/0/0 hot-standby state
---------------------------------------------------------------session id
main LSP token
hot-standby LSP token
HSB switch result
WTR
using same path
:
:
:
:
:
100
0x100201a
0x100201b
Primary LSP
10s
: --
# Run the display mpls te hot-standby state interface tunnel 1/0/0 command on PE1 again,
and you can see that the hot-standby LSP token is 0x0. This means that the hot-standby LSP is
not set up even though there are paths for setting up the hot-standby LSP.
[PE1] display mpls te hot-standby state interface tunnel 1/0/0
---------------------------------------------------------------Verbose information about the Tunnel1/0/0 hot-standby state
---------------------------------------------------------------session id
main LSP token
hot-standby LSP token
HSB switch result
WTR
using same path
:
:
:
:
:
:
100
0x100201c
0x0
Primary LSP
10s
--
----End
Configuration Files
l
Issue 02 (2011-09-10)
387
3 MPLS TE Configuration
#
interface GigabitEthernet1/0/0
ip address 10.1.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls te srlg 1
mpls rsvp-te
#
interface GigabitEthernet2/0/0
ip address 10.2.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls te srlg 1
mpls te srlg 2
mpls rsvp-te
#
interface GigabitEthernet3/0/0
ip address 10.8.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls rsvp-te
#
interface LoopBack1
ip address 5.5.5.5 255.255.255.255
isis enable 1
#
interface Tunnel1/0/0
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 6.6.6.6
mpls te tunnel-id 100
mpls te record-route
mpls te bandwidth ct0 10000
mpls te path explicit-path main
mpls te backup hot-standby
mpls te commit
#
return
Configuration file of P1
#
sysname P1
#
mpls lsr-id 1.1.1.1
mpls
mpls te
mpls rsvp-te
#
isis 1
cost-style wide
network-entity 10.0000.0000.0001.00
traffic-eng level-1-2
#
interface GigabitEthernet1/0/0
ip address 10.1.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls rsvp-te
Issue 02 (2011-09-10)
388
3 MPLS TE Configuration
#
interface GigabitEthernet2/0/0
ip address 10.2.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls rsvp-te
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
isis enable 1
#
return?
Configuration file of P2
#
sysname P2
#
mpls lsr-id 2.2.2.2
mpls
mpls te
mpls rsvp-te
#
isis 1
cost-style wide
network-entity 10.0000.0000.0002.00
traffic-eng level-1-2
#
interface GigabitEthernet1/0/0
ip address 10.2.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls rsvp-te
#
interface GigabitEthernet2/0/0
ip address 10.4.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls te srlg 2
mpls rsvp-te
#
interface GigabitEthernet3/0/0
ip address 10.5.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls rsvp-te
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
isis enable 1
#
return
Configuration file of P3
#
sysname P3
#
mpls lsr-id 3.3.3.3
mpls
Issue 02 (2011-09-10)
389
3 MPLS TE Configuration
mpls te
mpls rsvp-te
#
isis 1
cost-style wide
network-entity 10.0000.0000.0003.00
traffic-eng level-1-2
#
interface GigabitEthernet1/0/0
ip address 10.4.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls rsvp-te
#
interface GigabitEthernet2/0/0
ip address 10.7.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls rsvp-te
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
isis enable 1
#
return
Configuration file of P4
#
sysname P4
#
mpls lsr-id 4.4.4.4
mpls
mpls te
mpls rsvp-te
#
isis 1
cost-style wide
network-entity 10.0000.0000.0004.00
traffic-eng level-1-2
#
interface GigabitEthernet1/0/0
ip address 10.3.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls rsvp-te
#
interface GigabitEthernet2/0/0
ip address 10.5.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 50000
mpls rsvp-te
#
interface GigabitEthernet3/0/0
ip address 10.6.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
Issue 02 (2011-09-10)
390
3 MPLS TE Configuration
391
3 MPLS TE Configuration
The limit rate of TE traffic needs to be limited at 20 Mbit/s or lower. TE traffic at greater than
20 Mbit/s is dropped.
Figure 3-11 Networking diagram of an RSVP-TE tunnel
Loopback1
1.1.1.9/32
Loopback1
4.4.4.9/32
LSRA
LSRD
GE1/0/0
10.1.1.1/24
GE1/0/0
10.1.1.2/24
Loopback1
2.2.2.9/32
GE1/0/0
30.1.1.2/24
GE1/0/0
30.1.1.1/24
POS2/0/0
POS2/0/0
20.1.1.1/24 20.1.1.2/24
LSRB
LSRC
Loopback1
3.3.3.9/32
Configuration Roadmap
The configuration roadmap is as follows:
1.
2.
Data Preparation
To complete the configuration, you need the following data:
l
IS-IS area IDs, initial system IDs, and IS-IS levels of each LSR
Interface number, IP address, destination IP address, tunnel ID, tunnel signaling protocol
(RSVP-TE), and bandwidth of the tunnel
Configuration Procedure
1.
2.
3.
Issue 02 (2011-09-10)
392
3 MPLS TE Configuration
After the configuration, run the display current-configuration command in the tunnel
interface view of Tunnel1/0/0 on LSR A. You can view that the mpls te lsp-tp
outbound command configuration is displayed in the command output.
Configuration File
l
Issue 02 (2011-09-10)
393
3 MPLS TE Configuration
interface Pos2/0/0
link-protocol ppp
clock master
ip address 20.1.1.1 255.255.255.0
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
mpls rsvp-te
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
isis enable 1
#
return
Issue 02 (2011-09-10)
394
3 MPLS TE Configuration
interface GigabitEthernet1/0/0
ip address 30.1.1.2 255.255.255.0
isis enable 1
mpls
mpls te
mpls rsvp-te
#
interface LoopBack1
ip address 4.4.4.9 255.255.255.255
isis enable 1
#
return
Networking Requirements
As shown in Figure 3-12, PEs and P on the MPLS backbone network are enabled with OSPF
to interwork with each other. PE1 accesses VPN-A and PE2 accesses VPN-B. VPN-A transmits
EF traffic and VPN-B transmits BE traffic. The QoS requirements of different types of traffic
are as follows:
Traffic
Bandwidth
Jitter
EF traffic on VPN-A
100 Mbit/s
Shorter than 50 ms
BE traffic on VPN-B
200 Mbit/s
None
A static DS-TE tunnel between PE1 and PE2 is required to be set up in non-IETF mode to
transmit the preceding traffic. The bandwidth constraints model is required to be MAM and the
bandwidth preemption is not allowed between CTs.
Issue 02 (2011-09-10)
395
3 MPLS TE Configuration
AS: 65410
VPN-A
AS: 65430
CE1
CE3
GE1/0/0
10.1.1.1/24
GE1/0/0
10.1.1.2/24
Loopback1
1.1.1.9/32
GE2/0/0
10.2.1.2/24
GE1/0/0
10.3.1.1/24
Loopback1
2.2.2.9/32
GE2/0/0 PE2
PE1 GE1/0/0
172.1.1.2/24
172.2.1.1/24
GE3/0/0
GE3/0/0
172.2.1.2/24
172.1.1.1/24
P
MPLS backbone
AS: 100
GE1/0/0
10.2.1.1/24
GE1/0/0
10.3.1.2/24
Loopback1
3.3.3.9/32
GE2/0/0
10.4.1.2/24
GE1/0/0
10.4.1.1/24
CE4
CE2
VPN-B
VPN-A
AS: 65420
AS: 65440
VPN-B
Configuration Roadmap
The configuration roadmap is as follows:
1.
A static CR-LSP is set upfor each type of traffic on each VPN because the static TE tunnel
supports the single CT only.
2.
Two static CR-LSPs are created in non-IETF mode, with tunnel interfaces of static CRLSPs being tunnel 3/0/0 and tunnel 3/0/1 and CTs being CT0 and CT1 separately.
3.
Tunnel 3/0/0 is configured to transmit EF traffic of VPN-A and tunnel 3/0/1 is configured
to transmit BE traffic of VPN-B.
4.
The reservable bandwidth of the link should be equal to or greater than the total bandwidth
of BCs. Thus, the reservable bandwidth of the link is equal to or greater than 300 Mbit/s.
Data Preparation
To configure DS-TE in MAM, you need the following data.
l
Values of the maximum reservable bandwidth and bandwidth values for BCs on each link
VPN instance name, Route-Distinguisher (RD), VPN target, and name of the tunnel policy
of VPN-A and VPN-B
Issue 02 (2011-09-10)
396
3 MPLS TE Configuration
Procedure
Step 1 Configure IP addresses for interfaces on the PEs and P. Enable OSPF to ensure that the PEs and
P can communicate with each other.
Configuration details are not provided here.
After the configurations, OSPF adjacencies can be created between PE1, P, and PE2. By using
the display ospf peer command, you can see that the status of the adjacency is Full. By using
the display ip routing-table command, you can see that PEs can learn the route to Loopback1
from each other.
Step 2 Configure LSR ID and enable MPLS and MPLS-TE on each PE and P.
# Configuration PE1.
<PE1> system-view
[PE1] mpls lsr-id 1.1.1.9
[PE1] mpls
[PE1-mpls] mpls te
[PE1-mpls] quit
[PE1] interface gigabitethernet 3/0/0
[PE1-GigabitEthernet3/0/0] mpls
[PE1-GigabitEthernet3/0/0] mpls te
[PE1-GigabitEthernet3/0/0] quit
# Configure P.
<P> system-view
[P] mpls lsr-id 2.2.2.9
[P] mpls
[P-mpls] mpls te
[P-mpls] quit
[P] interface gigabitethernet
[P-GigabitEthernet1/0/0] mpls
[P-GigabitEthernet1/0/0] mpls
[P-GigabitEthernet1/0/0] quit
[P] interface gigabitethernet
[P-GigabitEthernet2/0/0] mpls
[P-GigabitEthernet2/0/0] mpls
[P-GigabitEthernet2/0/0] quit
1/0/0
te
2/0/0
te
# Configure PE2.
<PE2> system-view
[PE2] mpls lsr-id 3.3.3.9
[PE2] mpls
[PE2-mpls] mpls te
[PE2-mpls] quit
[PE2] interface gigabitethernet 3/0/0
[PE2-GigabitEthernet3/0/0] mpls
[PE2-GigabitEthernet3/0/0] mpls te
[PE2-GigabitEthernet3/0/0] quit
Step 3 Configure the DS-TE mode and the bandwidth constraints model on each PE and P.
# Configure PE1.
[PE1] mpls
[PE1-mpls] mpls te ds-te mode non-ietf
[PE1-mpls] mpls te ds-te bcm mam
[PE1-mpls] quit
# Configure P.
[P] mpls
[P-mpls] mpls te ds-te mode non-ietf
Issue 02 (2011-09-10)
397
3 MPLS TE Configuration
# Configure PE2.
[PE2] mpls
[PE2-mpls] mpls te ds-te mode non-ietf
[PE2-mpls] mpls te ds-te bcm mam
[PE2-mpls] quit
After the configuration, run the display mpls te ds-te summary command on a PE or P, and
you can view information about DS-TE configuration.
Take the display on PE1 as an example.
[PE1] display mpls te ds-te summary
DS-TE IETF Supported :YES
DS-TE MODE
:NON-IETF
Bandwidth Constraint Model :MAM
# Configure P.
[P] interface gigabitethernet
[P-GigabitEthernet1/0/0] mpls
[P-GigabitEthernet1/0/0] mpls
[P-GigabitEthernet1/0/0] quit
[P] interface gigabitethernet
[P-GigabitEthernet2/0/0] mpls
[P-GigabitEthernet2/0/0] mpls
[P-GigabitEthernet2/0/0] quit
1/0/0
te bandwidth max-reservable-bandwidth 300000
te bandwidth bc0 100000 bc1 200000
2/0/0
te bandwidth max-reservable-bandwidth 300000
te bandwidth bc0 100000 bc1 200000
# Configure PE2.
[PE2] interface gigabitethernet 3/0/0
[PE2-GigabitEthernet3/0/0] mpls te bandwidth max-reservable-bandwidth 300000
[PE2-GigabitEthernet3/0/0] mpls te bandwidth bc0 100000 bc1 200000
[PE2-GigabitEthernet3/0/0] quit
Issue 02 (2011-09-10)
398
3 MPLS TE Configuration
3
0
3
0
100000
0
4
0
4
0
100000
0
5
0
5
0
100000
0
6
0
6
0
100000
0
7
0
7
0
100000
0
8
1
0
0
200000
0
9
1
1
0
200000
0
10
1
2
0
200000
0
11
1
3
0
200000
0
12
1
4
0
200000
0
13
1
5
0
200000
0
14
1
6
0
200000
0
15
1
7
0
200000
0
----------------------------------------------------------------------
# Configure PE2.
[PE2] interface tunnel3/0/0
[PE2-Tunnel3/0/0] description For VPN-A_EF
[PE2-Tunnel3/0/0] ip address unnumbered interface loopback 1
[PE2-Tunnel3/0/0] tunnel-protocol mpls te
[PE2-Tunnel3/0/0] destination 1.1.1.9
[PE2-Tunnel3/0/0] mpls te tunnel-id 300
[PE2-Tunnel3/0/0] mpls te signal-protocol cr-static
[PE2-Tunnel3/0/0] mpls te commit
[PE2-Tunnel3/0/0] quit
[PE2] interface tunnel3/0/1
[PE2-Tunnel3/0/1] description For VPN-B_BE
[PE2-Tunnel3/0/1] ip address unnumbered interface loopback 1
[PE2-Tunnel3/0/1] tunnel-protocol mpls te
[PE2-Tunnel3/0/1] destination 1.1.1.9
[PE2-Tunnel3/0/1] mpls te tunnel-id 301
[PE2-Tunnel3/0/1] mpls te signal-protocol cr-static
[PE2-Tunnel3/0/1] mpls te commit
Issue 02 (2011-09-10)
399
3 MPLS TE Configuration
# Configure P.
[P] static-cr-lsp
label 100 nexthop
[P] static-cr-lsp
label 200 nexthop
[P] static-cr-lsp
label 101 nexthop
[P] static-cr-lsp
label 201 nexthop
inininin-
Configure PE2.
[PE2] static-cr-lsp egress VPN-A_EF incoming-interface gigabitethernet 3/0/0 inlabel 100
[PE2] static-cr-lsp egress VPN-B_BE incoming-interface gigabitethernet 3/0/0 inlabel 200
[PE2] static-cr-lsp ingress tunnel-interface tunnel 3/0/0 destination 1.1.1.9
nexthop 172.2.1.1 out-label 101 bandwidth ct0 100000
[PE2] static-cr-lsp ingress tunnel-interface tunnel 3/0/1 destination 1.1.1.9
nexthop 172.2.1.1 out-label 201 bandwidth ct1 200000
After the configuration, run the display mpls static-cr-lsp command on a PE, and you can see
that the static CR-LSP goes Up.
Take tunnel 3/0/0 on PE1 as an example.
[PE1] display mpls static-cr-lsp Tunnel3/0/0
TOTAL
: 1
STATIC CRLSP(S)
UP
: 1
STATIC CRLSP(S)
DOWN
: 0
STATIC CRLSP(S)
Name
FEC
I/O Label I/O If
Tunnel3/0/0
3.3.3.9/32
NULL/100 -/S1/0/1
Stat
Up
Run the display interface tunnel interface-number command on a PE, and you can see that the
tunnel interface goes Up.
Take tunnel 3/0/0 on PE1 as an example.
[PE1] display interface tunnel 3/0/0
Tunnel3/0/0 current state : UP
Line protocol current state : UP
Last up time: 2008-05-23, 10:03:07
Description :For VPN-A_EF
Route Port,The Maximum Transmit Unit is 1500
Internet Address is unnumbered, using address of LoopBack1(1.1.1.9/32)
Encapsulation is TUNNEL, loopback not set
Tunnel destination 3.3.3.9
Tunnel up/down statistics 1
Tunnel protocol/transport MPLS/MPLS, ILM is available,
primary tunnel id is 0x8201002c, secondary tunnel id is 0x0
...
Run the display mpls te link-administration bandwidth-allocation command again, and you
can view that the bandwidth has been allocated for CT0 and CT1 with priorities being 0.
[PE1] display mpls te link-administration bandwidth-allocation interface
gigabitethernet 3/0/0
Link ID: GigabitEthernet3/0/0
Bandwidth Constraint Model
: Maximum Allocation Model (MAM)
Maximum Link Reservable Bandwidth(Kbit/sec): 300000
Reservable Bandwidth BC0(Kbit/sec)
: 100000
Reservable Bandwidth BC1(Kbit/sec)
: 200000
Downstream Bandwidth (Kbit/sec)
: 300000
IPUpdown Link Status
: UP
PhysicalUpdown Link Status
: UP
---------------------------------------------------------------------TE-CLASS CT
PRIORITY
BW RESERVED
BW AVAILABLE
DOWNSTREAM
(Kbit/sec)
(Kbit/sec) RSVPLSPNODE COUNT
Issue 02 (2011-09-10)
400
3 MPLS TE Configuration
---------------------------------------------------------------------0
0
0
100000
0
0
1
0
1
0
0
0
2
0
2
0
0
0
3
0
3
0
0
0
4
0
4
0
0
0
5
0
5
0
0
0
6
0
6
0
0
0
7
0
7
0
0
0
8
1
0
200000
0
0
9
1
1
0
0
0
10
1
2
0
0
0
11
1
3
0
0
0
12
1
4
0
0
0
13
1
5
0
0
0
14
1
6
0
0
0
15
1
7
0
0
0
----------------------------------------------------------------------
# Configure P.
[P] interface gigabitethernet 1/0/0
[P-GigabitEthernet1/0/0] trust upstream default
[P-GigabitEthernet1/0/0] quit
[P] interface gigabitethernet 2/0/0
[P-GigabitEthernet2/0/0] trust upstream default
[P-GigabitEthernet2/0/0] quit
# Configure PE2.
[PE2] interface gigabitethernet 1/0/0
[PE2-GigabitEthernet1/0/0] trust upstream default
[PE2-GigabitEthernet1/0/0] quit
[PE2] interface gigabitethernet 2/0/0
[PE2-GigabitEthernet2/0/0] trust upstream default
[PE2-GigabitEthernet2/0/0] quit
[PE2] interface gigabitethernet 3/0/0
[PE2-GigabitEthernet3/0/0] trust upstream default
[PE2-GigabitEthernet3/0/0] quit
After the configuration, run the display diffserv domain default command on a PE, and you
can view information about the default traffic policy for traffic classification in a DS domain.
Take the display on PE1 as an example.
[PE1] display diffserv domain default
Diffserv domain name:default
...
mpls-exp-inbound 0 phb be green
mpls-exp-inbound 1 phb af1 green
mpls-exp-inbound 2 phb af2 green
mpls-exp-inbound 3 phb af3 green
mpls-exp-inbound 4 phb af4 green
mpls-exp-inbound 5 phb ef green
mpls-exp-inbound 6 phb cs6 green
Issue 02 (2011-09-10)
401
3 MPLS TE Configuration
Take note of the preceding items that appear in the display diffserv domain default command output.
Information in "..." can be ignored.
Step 8 Configure the mapping of the CT and service type on the PEs and P.
# Configure PE1.
[PE1] ct-flow-mapping mapping1
[PE1-ct-flow-mapping-mapping1] map ct 0 to ef pq
[PE1-ct-flow-mapping-mapping1] map ct 1 to be lpq
[PE1-ct-flow-mapping-mapping1] ct-flow-mapping commit
[PE1-ct-flow-mapping-mapping1] quit
[PE1] interface gigabitethernet 3/0/0
[PE1-GigabitEthernet3/0/0] mpls te ct-flow-mapping mapping1
[PE1-GigabitEthernet3/0/0] mpls te ct-bandwidth unshared
[PE1-GigabitEthernet3/0/0] quit
# Configure PE2.
[PE2] ct-flow-mapping mapping1
[PE2-ct-flow-mapping-mapping1] map ct 0 to ef pq
[PE2-ct-flow-mapping-mapping1] map ct 1 to be lpq
[PE2-ct-flow-mapping-mapping1] ct-flow-mapping commit
[PE2-ct-flow-mapping-mapping1] quit
[PE2] interface gigabitethernet 3/0/0
[PE2-GigabitEthernet3/0/0] mpls te ct-flow-mapping mapping1
[PE2-GigabitEthernet3/0/0] mpls te ct-bandwidth unshared
[PE2-GigabitEthernet3/0/0] quit
# After the configuration, run the display ct-flow-mapping command on PEs, and you can view
the mapping relationship between CTs and flow queues.
Take the display on PE1 as an example.
[PE1] display ct-flow-mapping all
Totle template: 2
template-name:default
map CT 0 to be lpq
map CT 1 to af1 wfq
map CT 2 to af2 wfq
map CT 3 to af3 wfq
map CT 4 to af4 wfq
map CT 5 to ef pq
map CT 6 to cs6 pq
map CT 7 to cs6 pq
template-name:mapping1
Issue 02 (2011-09-10)
402
3 MPLS TE Configuration
map CT 0 to ef pq
map CT 1 to be lpq
Step 9 Create the MP-IBGP peer relationship between PEs, and create the EBGP peer relationship
between PEs and CEs.
# Configure PE1.
[PE1] bgp 100
[PE1-bgp] peer 3.3.3.9 as-number 100
[PE1-bgp] peer 3.3.3.9 connect-interface loopback 1
[PE1-bgp] ipv4-family vpnv4
[PE1-bgp-af-vpnv4] peer 3.3.3.9 enable
[PE1-bgp-af-vpnv4] quit
[PE1-bgp] ipv4-family vpn-instance vpna
[PE1-bgp-vpna] peer 10.1.1.1 as-number 65410
[PE1-bgp-vpna] import-route direct
[PE1-bgp-vpna] quit
[PE1-bgp] ipv4-family vpn-instance vpnb
[PE1-bgp-vpnb] peer 10.2.1.1 as-number 65420
[PE1-bgp-vpnb] import-route direct
[PE1-bgp-vpnb] quit
NOTE
The configuration of PE2 is similar to that of PE1. The configuration detail is not provided here.
# Configure CE1.
[CE1] bgp 65410
[CE1-bgp] peer 10.1.1.2 as-number 100
[CE1-bgp] import-route direct
NOTE
The configuration of other CEs (CE2, CE3, and CE4) is similar to that of CE1. The configuration details
are not provided here.
After the configuration, run the display bgp vpnv4 all peer command on the PE, and you can
see that the BGP peer relationship is created between PEs and its status is Established.
[PE1] display bgp vpnv4 all peer
BGP local router ID : 1.1.1.9
Local AS number : 100
Total number of peers : 3
Peer
V
AS MsgRcvd
3.3.3.9
4
100
Peer of vpn instance:
vpn instance vpna :
10.1.1.1
4 65410
vpn instance vpnb :
10.2.1.1
4 65420
MsgSent
12
18
0 00:09:38 Established
25
25
0 00:17:57 Established
21
22
0 00:17:10 Established
# Configure PE2.
[PE2] tunnel-policy policya
[PE2-tunnel-policy-policya] tunnel binding destination 1.1.1.9 te tunnel 3/0/0
[PE2-tunnel-policy-policya] quit
[PE2] tunnel-policy policyb
Issue 02 (2011-09-10)
403
3 MPLS TE Configuration
# Configure PE2.
[PE2] ip vpn-instance vpna
[PE2-vpn-instance-vpna] ipv4-family
[PE2-vpn-instance-vpna-af-ipv4] route-distinguisher 200:1
[PE2-vpn-instance-vpna-af-ipv4] vpn-target 111:1 both
[PE2-vpn-instance-vpna-af-ipv4] tnl-policy policya
[PE2-vpn-instance-vpna-af-ipv4] quit
[PE2-vpn-instance-vpna] quit
[PE2] ip vpn-instance vpnb
[PE2-vpn-instance-vpnb] ipv4-family
[PE2-vpn-instance-vpnb-af-ipv4] route-distinguisher 200:2
[PE2-vpn-instance-vpnb-af-ipv4] vpn-target 222:2 both
[PE2-vpn-instance-vpnb-af-ipv4] tnl-policy policyb
[PE2-vpn-instance-vpnb-af-ipv4] quit
[PE2-vpn-instance-vpnb] quit
[PE2] interface gigabitethernet 1/0/0
[PE2-GigabitEthernet1/0/0] ip binding vpn-instance vpna
[PE2-GigabitEthernet1/0/0] ip address 10.3.1.2 24
[PE2-GigabitEthernet1/0/0] quit
[PE2] interface gigabitethernet 2/0/0
[PE2-GigabitEthernet2/0/0] ip binding vpn-instance vpnb
[PE2-GigabitEthernet2/0/0] ip address 10.4.1.2 24
[PE2-GigabitEthernet2/0/0] quit
# Configure IP addresses for interfaces of CEs. The configuration details are not provided here.
After the configuration, run the display ipvpn-instance verbose command on the PE, and you
can view the configuration of VPN instances. PEs can ping through the CEs connecting to the
PEs.
Step 12 Verify the configuration.
After the configuration, connect CE1, CE2, CE3, and CE4 to port 1, port 2, port 3, and port 4
of a tester. Inject EF traffic from port 1 and port 2 to port 2 and port 1 respectively, with the
Issue 02 (2011-09-10)
404
3 MPLS TE Configuration
bandwidth being 100 Mbit/s. Inject BE traffic from port 3 and port 4 to port 2 and port 1
respectively, with the bandwidth being 200 Mbit/s. All the packets are not discarded and the
jitter of EF traffic is shorter than 50 ms.
----End
Configuration Files
l
Issue 02 (2011-09-10)
405
3 MPLS TE Configuration
Configuration file of P
#
sysname P
#
mpls lsr-id 2.2.2.9
mpls
mpls te
mpls te ds-te bcm mam
#
interface GigabitEthernet1/0/0
undo shutdown
ip address 172.1.1.2 255.255.255.0
mpls
Issue 02 (2011-09-10)
406
3 MPLS TE Configuration
mpls te
mpls te bandwidth max-reservable-bandwidth 300000
mpls te bandwidth bc0 100000 bc1 200000
trust upstream default
#
interface GigabitEthernet2/0/0
undo shutdown
ip address 172.2.1.1 255.255.255.0
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 300000
mpls te bandwidth bc0 100000 bc1 200000
trust upstream default
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
opaque-capability enable
area 0.0.0.0
network 172.1.1.0 0.0.0.255
network 172.2.1.0 0.0.0.255
network 2.2.2.9 0.0.0.0
mpls-te enable
#
static-cr-lsp transit VPN-A_EF-1to2 incoming-interface gigabitethernet1/0/0
in-label 100 nexthop 172.2.1.2 out-label 100 bandwidth ct0 100000
static-cr-lsp transit VPN-B_BE-1to2 incoming-interface gigabitethernet1/0/0
in-label 200 nexthop 172.2.1.2 out-label 200 bandwidth ct1 200000
static-cr-lsp transit VPN-A_EF-2to1 incoming-interface gigabitethernet2/0/0
in-label 101 nexthop 172.1.1.1 out-label 101 bandwidth ct0 100000
static-cr-lsp transit VPN-B_BE-2to1 incoming-interface gigabitethernet2/0/0
in-label 201 nexthop 172.1.1.1 out-label 201 bandwidth ct1 200000
#
return
Issue 02 (2011-09-10)
407
3 MPLS TE Configuration
interface GigabitEthernet2/0/0
undo shutdown
ip binding vpn-instance vpnb
ip address 10.4.1.2 255.255.255.0
trust upstream default
#
interface GigabitEthernet3/0/0
undo shutdown
ip address 172.2.1.2 255.255.255.0
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 300000
mpls te bandwidth bc0 100000 bc1 200000
trust upstream default
mpls te ct-flow-mapping mapping1
mpls te ct-bandwidth unshared
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
interface Tunnel3/0/0
description For VPN-A_EF
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 1.1.1.9
mpls te tunnel-id 300
mpls te signal-protocol cr-static
mpls te commit
#
interface Tunnel3/0/1
description For VPN-B_BE
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 1.1.1.9
mpls te tunnel-id 301
mpls te signal-protocol cr-static
mpls te commit
#
bgp 100
peer 1.1.1.9 as-number 100
peer 1.1.1.9 connect-interface LoopBack1
#
ipv4-family unicast
undo synchronization
peer 1.1.1.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.9 enable
#
ipv4-family vpn-instance vpna
peer 10.3.1.1 as-number 65430
import-route direct
#
ipv4-family vpn-instance vpnb
peer 10.4.1.1 as-number 65440
import-route direct
#
ospf 1
opaque-capability enable
area 0.0.0.0
network 172.2.1.0 0.0.0.255
network 3.3.3.9 0.0.0.0
mpls-te enable
#
static-cr-lsp egress VPN-A_EF incoming-interface gigabitethernet 3/0/0 inlabel 100
static-cr-lsp egress VPN-B_BE incoming-interface gigabitethernet 3/0/0 inlabel 200
Issue 02 (2011-09-10)
408
3 MPLS TE Configuration
Issue 02 (2011-09-10)
409
3 MPLS TE Configuration
#
interface GigabitEthernet1/0/0
undo shutdown
ip address 10.4.1.1 255.255.255.0
#
bgp 65440
peer 10.4.1.2 as-number 100
#
ipv4-family unicast
undo synchronization
import-route direct
peer 10.4.1.2 enable
#
return
Networking Requirements
As shown in Figure 3-13, PEs and P on the MPLS backbone network are enabled with OSPF
to communicate with each other. The P, however, does not support MPLS LDP. PE1 accesses
VPN-A and PE2 accesses VPN-B. An LDP LSP needs to be set up along the path PE3 --> PE1
--> P --> PE2 --> PE4. As shown in Figure 3-13, VPN-A transmits EF and AF traffic; VPN-B
transmits EF, AF, and BE traffic; the LDP LSP transmits BE traffic. The QoS requirements of
different types of traffic are as follows:
Traffic
Bandwidth
Jitter
EF traffic on VPN-A
100 Mbit/s
Shorter than 50 ms
AF traffic on VPN-A
50 Mbit/s
EF traffic on VPN-B
100 Mbit/s
Shorter than 50 ms
AF traffic on VPN-B
50 Mbit/s
BE traffic on VPN-B
50 Mbit/s
None
50 Mbit/s
None
The networking requires that a DS-TE tunnel be set up between PE1 and PE2 to transmit the
preceding traffic and meet different QoS requirements of different traffic types. The bandwidth
constraints model is RDM. CTi can preempt the bandwidth of CTj (0 <= i < j <= 7). This means
that bandwidths will first be allocated for CTs with higher priorities.
Issue 02 (2011-09-10)
410
3 MPLS TE Configuration
AS 65430
VPN-A
CE3
AS 65410
VPN-A
CE1
GE1/0/0
10.1.1.1/24
GE1/0/0
10.1.1.2/24
GE1/0/0
10.3.1.1/24
Loopback 1
1.1.1.9/32
Loopback 1 PE1
4.4.4.9/32
GE4/0/0
10.5.1.1/24
PE3
GE1/0/0
10.5.1.2/24
GE3/0/0
172.1.1.1/24
GE1/0/0
172.1.1.2/24
GE2/0/0
10.2.1.2/24
GE3/0/0
172.2.1.2/24
P
GE2/0/0
172.2.1.1/24
GE2/0/0
10.4.1.2/24
GE1/0/0
10.2.1.1/24
CE2
GE1/0/0
10.3.1.2/24
Loopback
PE2
5.5.5.9/32
GE4/0/0
10.6.1.1/24
PE
GE1/0/0
10.6.1.2/24
GE1/0/0
10.4.1.1/24
CE4
VPN-B
AS 65440
VPN-B
AS 65420
Configuration Roadmap
NOTE
l In this example, the bandwidth and delay time are guaranteed for all service traffic of each VPN in DSTE tunnels.
l If you need to guarantee the bandwidth and delay time for all service traffic only in DS-TE tunnels
irrespective of VPNs, you can set up only one DS-TE tunnel to transmit all the traffic.
l You can limit the service traffic of different VPNs in DS-TE tunnels by limiting the ingress PE to
access VPNs and the service traffic of VPNs.
2.
Set up different tunnels for VPN-B and the LDP LSP when VPN-B and LDP LSP have
same traffic.
3.
Set up one TE tunnel when VPN-A and the LDP LSP have three types of traffic.
4.
Set up two RSVP-TE tunnels on tunnel 3/0/0 and tunnel 3/0/1. Each tunnel is configured
with three CTs with the priority being 0, that is, CT0, CT1, and CT2. CT0, CT1, and CT2
bear EF, AF, and BE traffic respectively.
Issue 02 (2011-09-10)
411
3 MPLS TE Configuration
5.
CT2 and CT1 of tunnel 3/0/0 transmit EF and AF traffic of VPN-A. CT0 of tunnel 3/0/0
transmits BE traffic of the LDP LSP. CT2, CT1, and CT0 of tunnel 3/0/1 transmit EF, AF,
and BE traffic of VPN-B.
6.
Paths of the two tunnels are the same. Thus, the BCi bandwidth should be equal to or greater
than the total bandwidth of CTi to CT7 of all the TE tunnels. In addition, the maximum
reservable bandwidth for links should be equal to or greater than the bandwidth of BC0.
Therefore, the bandwidth relationships between BCi and CT1 to CT7 is as follows:
Bandwidth of BC2 on the link => Bandwidth of CT2 of Tunnel 3/0/0 and Tunnel 3/0/1 =
100 Mbit/s
Bandwidth of BC1 => Bandwidth of BC2 + CT1 of Tunnel 3/0/0 and Tunnel 3/0/1 = 200
Mbit/s
Bandwidth of BC0 => Bandwidth of BC1 + Bandwidth of CT0 of Tunnel 3/0/0 + Bandwidth
of CT0 of Tunnel 3/0/1 = 400 Mbit/s
Reservable bandwidth of the link = Bandwidth of BC0 = 400 Mbit/s
7.
Services of the same type in two TE tunnels require the same bandwidth and jitter.
Therefore, the CT template is used to configure the TE tunnel.
Data Preparation
To configure a DS-TE tunnel in IETF mode (RDM), you need the following data.
l
VPN-A instance name, VPN-B instance name, route-distinguisher, VPN target, and name
of the tunnel policy
Procedure
Step 1 Configure IP addresses for interfaces on PEs and the P. Enable OSPF to ensure that PEs and the
P can communicate with each other.
The configuration details are not provided here.
After the configurations, OSPF adjacencies can be created between PE1, P, and PE2. By using
the display ospf peer command, you can view that the status of the adjacency is Full. By using
the display ip routing-table command, you can see that PEs can learn the Loopback1 route
from each other.
Step 2 Configure LSR ID and enable MPLS on each PE and P. Enable MPLS TE and RSVP-TE on
PE1, PE2, and the P. Enable MPLS LDP on all PEs.
# Configure PE3.
<PE3> system-view
[PE3] mpls lsr-id 4.4.4.9
[PE3] mpls
[PE3-mpls] quit
[PE3] mpls ldp
[PE3-mpls-ldp] quit
[PE3] interface gigabitethernet 1/0/0
[PE3-GigabitEthernet1/0/0] mpls
[PE3-GigabitEthernet1/0/0] mpls ldp
[PE3-GigabitEthernet1/0/0] quit
Issue 02 (2011-09-10)
412
3 MPLS TE Configuration
# Configure PE1.
<PE1> system-view
[PE1] mpls lsr-id 1.1.1.9
[PE1] mpls
[PE1-mpls] mpls te
[PE1-mpls] mpls rsvp-te
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
[PE1] interface gigabitethernet
[PE1-GigabitEthernet3/0/0] mpls
[PE1-GigabitEthernet3/0/0] mpls
[PE1-GigabitEthernet3/0/0] mpls
[PE1-GigabitEthernet3/0/0] quit
[PE1] interface gigabitethernet
[PE1-GigabitEthernet4/0/0] mpls
[PE1-GigabitEthernet4/0/0] mpls
[PE1-GigabitEthernet4/0/0] quit
3/0/0
te
rsvp-te
4/0/0
ldp
# Configure the P.
<P> system-view
[P] mpls lsr-id 2.2.2.9
[P] mpls
[P-mpls] mpls te
[P-mpls] mpls rsvp-te
[P-mpls] quit
[P] interface gigabitethernet
[P-GigabitEthernet1/0/0] mpls
[P-GigabitEthernet1/0/0] mpls
[P-GigabitEthernet1/0/0] mpls
[P-GigabitEthernet1/0/0] quit
[P] interface gigabitethernet
[P-GigabitEthernet2/0/0] mpls
[P-GigabitEthernet2/0/0] mpls
[P-GigabitEthernet2/0/0] mpls
[P-GigabitEthernet2/0/0] quit
1/0/0
te
rsvp-te
2/0/0
te
rsvp-te
# Configure PE2.
<PE2> system-view
[PE2] mpls lsr-id 3.3.3.9
[PE2] mpls
[PE2-mpls] mpls te
[PE2-mpls] mpls rsvp-te
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls] quit
[PE2] interface gigabitethernet
[PE2-GigabitEthernet3/0/0] mpls
[PE2-GigabitEthernet3/0/0] mpls
[PE2-GigabitEthernet3/0/0] mpls
[PE2-GigabitEthernet3/0/0] quit
[PE2] interface gigabitethernet
[PE2-GigabitEthernet4/0/0] mpls
[PE2-GigabitEthernet4/0/0] mpls
[PE2-GigabitEthernet4/0/0] quit
3/0/0
te
rsvp-te
4/0/0
ldp
# Configure PE4.
<PE4> system-view
[PE4] mpls lsr-id 5.5.5.9
[PE4] mpls
[PE4-mpls] quit
[PE4] mpls ldp
[PE4-mpls-ldp] quit
[PE4] interface gigabitethernet 1/0/0
[PE4-GigabitEthernet1/0/0] mpls
Issue 02 (2011-09-10)
413
3 MPLS TE Configuration
After the configuration, run the display mpls rsvp-te interface command on PE1, PE2, or the
P, and you can view interfaces enabled with RSVP and information about RSVP. Run the display
mpls ldp lsp command on PE1, PE2, PE3, or PE4, and you can see that an LDP LSP exists
between PE3 and PE1, and between PE2 and PE4.
Step 3 Configure OSPF TE on PE1, PE2, and the P and enable CSPF.
# Configure OSPF TE on PE1, PE2, and the P and enable CSPF on the ingress of the TE tunnel.
# Configure PE1.
[PE1] ospf 1
[PE1-ospf-1] opaque-capability enable
[PE1-ospf-1] area 0
[PE1-ospf-1-area-0.0.0.0] mpls-te enable
[PE1-ospf-1-area-0.0.0.0] quit
[PE1-ospf-1] quit
[PE1] mpls
[PE1-mpls] mpls te cspf
# Configure P.
[P] ospf 1
[P-ospf-1] opaque-capability enable
[P-ospf-1] area 0
[P-ospf-1-area-0.0.0.0] mpls-te enable
[P-ospf-1-area-0.0.0.0] quit
[P-ospf-1] quit
# Configure PE2.
[PE2] ospf 1
[PE2-ospf-1] opaque-capability enable
[PE2-ospf-1] area 0
[PE2-ospf-1-area-0.0.0.0] mpls-te enable
[PE2-ospf-1-area-0.0.0.0] quit
[PE2-ospf-1] quit
[PE2] mpls
[PE2-mpls] mpls te cspf
[PE2-mpls] quit
After the configuration, run the display ospf mpls-te command, and you can view the TE LSA
information in the OSPF Link State Database (LSDB).
Step 4 Configure the DS-TE mode and the bandwidth constraints model on PE1, PE2, and the P.
# Configure PE1.
[PE1] mpls
[PE1-mpls] mpls te ds-te mode ietf
[PE1-mpls] mpls te ds-te bcm rdm
[PE1-mpls] quit
# Configure P.
[P] mpls
[P-mpls] mpls te ds-te mode ietf
[P-mpls] mpls te ds-te bcm rdm
[P-mpls] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] mpls te ds-te mode ietf
[PE2-mpls] mpls te ds-te bcm rdm
[PE2-mpls] quit
Issue 02 (2011-09-10)
414
3 MPLS TE Configuration
After the configuration, run the display mpls te ds-te summary command on a PE or P, and
you can view information about DS-TE configuration.
Take the display on PE1 as an example.
[PE1] display mpls te ds-te summary
DS-TE IETF Supported :YES
DS-TE MODE
:IETF
Bandwidth Constraint Model :RDM
TEClass Mapping (default):
TE-Class ID
Class Type
Priority
TE-Class 0
0
0
TE-Class 1
1
0
TE-Class 2
2
0
TE-Class 3
3
0
TE-Class 4
0
7
TE-Class 5
1
7
TE-Class 6
2
7
TE-Class 7
3
7
# Configure the P.
[P] interface gigabitethernet
[P-GigabitEthernet1/0/0] mpls
[P-GigabitEthernet1/0/0] mpls
[P-GigabitEthernet1/0/0] quit
[P] interface gigabitethernet
[P-GigabitEthernet2/0/0] mpls
[P-GigabitEthernet2/0/0] mpls
[P-GigabitEthernet2/0/0] quit
1/0/0
te bandwidth max-reservable-bandwidth 400000
te bandwidth bc0 400000 bc1 200000 bc2 100000
2/0/0
te bandwidth max-reservable-bandwidth 400000
te bandwidth bc0 400000 bc1 200000 bc2 100000
# Configure PE2.
[PE2] interface gigabitethernet 3/0/0
[PE2-GigabitEthernet3/0/0] mpls te bandwidth max-reservable-bandwidth 400000
[PE2-GigabitEthernet3/0/0] mpls te bandwidth bc0 400000 bc1 200000 bc2 100000
[PE2-GigabitEthernet3/0/0] quit
Issue 02 (2011-09-10)
415
3 MPLS TE Configuration
---------------------------------------------------------------------TE-CLASS CT
PRIORITY
BW RESERVED
BW AVAILABLE
DOWNSTREAM
(Kbit/sec)
(Kbit/sec) RSVPLSPNODE COUNT
---------------------------------------------------------------------0
0
0
0
400000
0
1
1
0
0
200000
0
2
2
0
0
100000
0
3
0
7
0
400000
0
4
1
7
0
200000
0
5
2
7
0
100000
0
6
7
8
9
10
11
12
13
14
15
----------------------------------------------------------------------
After the configuration, run the display mpls te ds-te te-class-mapping command on a PE, and
you can view information about the TE-class mapping table.
Take the display on PE1 as an example.
[PE1] display mpls te ds-te te-class-mapping
TE-Class ID
Class Type
Priority
TE-Class0
0
0
TE-Class1
1
0
TE-Class2
2
0
TE-Class3
TE-Class4
TE-Class5
TE-Class6
TE-Class7
-
Description
For-EF
For-AF
For-BE
-
# Configure PE2.
[PE2] explicit-path path1
[PE2-explicit-path-path1]
[PE2-explicit-path-path1]
[PE2-explicit-path-path1]
[PE2-explicit-path-path1]
Issue 02 (2011-09-10)
416
3 MPLS TE Configuration
After the configuration, run the display explicit-path command on a PE, and you can view
information about the explicit path.
Take the display on PE1 as an example.
[PE1] display explicit-path path1
Path Name : path1
Path Status : Enabled
1
172.1.1.2
Strict
Include
2
172.2.1.2
Strict
Include
3
3.3.3.9
Strict
Include
# Configure PE2.
[PE2] interface tunnel3/0/0
[PE2-Tunnel3/0/0] description For VPN-A & Non-VPN
[PE2-Tunnel3/0/0] ip address unnumbered interface loopback 1
[PE2-Tunnel3/0/0] tunnel-protocol mpls te
[PE2-Tunnel3/0/0] destination 1.1.1.9
[PE2-Tunnel3/0/0] mpls te tunnel-id 300
[PE2-Tunnel3/0/0] mpls te signal-protocol rsvp-te
[PE2-Tunnel3/0/0] mpls te path explicit-path path1
[PE2-Tunnel3/0/0] mpls te priority 0
[PE2-Tunnel3/0/0] mpls te bandwidth ct0 100000 ct1 50000 ct2 50000
[PE2-Tunnel3/0/0] mpls te commit
[PE2] interface tunnel3/0/1
[PE2-Tunnel3/0/1] description For VPN-B
[PE2-Tunnel3/0/1] ip address unnumbered interface loopback 1
[PE2-Tunnel3/0/1] tunnel-protocol mpls te
[PE2-Tunnel3/0/1] destination 1.1.1.9
[PE2-Tunnel3/0/1] mpls te tunnel-id 301
[PE2-Tunnel3/0/1] mpls te signal-protocol rsvp-te
[PE2-Tunnel3/0/1] mpls te path explicit-path path1
[PE2-Tunnel3/0/1] mpls te priority 0
[PE2-Tunnel3/0/1] mpls te bandwidth ct0 100000 ct1 50000 ct2 50000
[PE2-Tunnel3/0/1] mpls te commit
Run the display interface tunnel interface-number command on a PE, and you can see that the
tunnel interface goes Up.
Take tunnel 3/0/0 on PE1 as an example.
Issue 02 (2011-09-10)
417
3 MPLS TE Configuration
Run the display mpls te te-class-tunnel command on a PE, and you can check the TE tunnel
associated with the TE-class.
Take the display on PE1 as an example.
[PE1] display mpls te te-class-tunnel all
-----------------------------------------------------------------------No. CT
priority
status
tunnel name
tunnel commit
-----------------------------------------------------------------------1
CT0
0
Valid
Tunnel3/0/0
Yes
2
CT0
0
Valid
Tunnel3/0/1
Yes
3
CT1
0
Valid
Tunnel3/0/0
Yes
4
CT1
0
Valid
Tunnel3/0/1
Yes
5
CT2
0
Valid
Tunnel3/0/0
Yes
6
CT2
0
Valid
Tunnel3/0/0
Yes
default
default
default
default
# Configure P.
[P] interface gigabitethernet 1/0/0
[P-GigabitEthernet1/0/0] trust upstream default
[P-GigabitEthernet1/0/0] quit
[P] interface gigabitethernet 2/0/0
[P-GigabitEthernet2/0/0] trust upstream default
[P-GigabitEthernet2/0/0] quit
# Configure PE2.
[PE2] interface gigabitethernet 1/0/0
[PE2-GigabitEthernet1/0/0] trust upstream
[PE2-GigabitEthernet1/0/0] quit
[PE2] interface gigabitethernet 2/0/0
[PE2-GigabitEthernet2/0/0] trust upstream
[PE2-GigabitEthernet2/0/0] quit
[PE2] interface gigabitethernet 4/0/0
[PE2-GigabitEthernet4/0/0] trust upstream
[PE2-GigabitEthernet4/0/0] quit
[PE2] interface gigabitethernet 3/0/0
[PE2-GigabitEthernet3/0/0] trust upstream
[PE2-GigabitEthernet3/0/0] quit
Issue 02 (2011-09-10)
default
default
default
default
418
3 MPLS TE Configuration
After the configuration, run the display diffserv domain default command on a PE, and you
can view information about the default traffic policy for traffic classification in a DS domain.
Take the display on PE1 as an example.
[PE1] display diffserv domain default
Diffserv domain name:default
...
mpls-exp-inbound 0 phb be green
mpls-exp-inbound 1 phb af1 green
mpls-exp-inbound 2 phb af2 green
mpls-exp-inbound 3 phb af3 green
mpls-exp-inbound 4 phb af4 green
mpls-exp-inbound 5 phb ef green
mpls-exp-inbound 6 phb cs6 green
mpls-exp-inbound 7 phb cs7 green
mpls-exp-outbound be green map 0
mpls-exp-outbound af1 green map 1
mpls-exp-outbound af1 yellow map 1
mpls-exp-outbound af1 red map 1
mpls-exp-outbound af2 green map 2
mpls-exp-outbound af2 yellow map 2
mpls-exp-outbound af2 red map 2
mpls-exp-outbound af3 green map 3
mpls-exp-outbound af3 yellow map 3
mpls-exp-outbound af3 red map 3
mpls-exp-outbound af4 green map 4
mpls-exp-outbound af4 yellow map 4
mpls-exp-outbound af4 red map 4
mpls-exp-outbound ef green map 5
mpls-exp-outbound cs6 green map 6
mpls-exp-outbound cs7 green map 7
...
NOTE
Take note of the preceding items that appear in the display diffserv domain default command output.
Information in "..." can be ignored.
Step 10 Configure the mapping of the CT and service type on the PEs and P.
# Bind the outbound interface of services with the DS domain on PEs for simple traffic
classification.
# Configure PE1.
[PE1] ct-flow-mapping mapping1
[PE1-ct-flow-mapping-mapping1] map ct 0 to ef pq
[PE1-ct-flow-mapping-mapping1] map ct 1 to af1 wfq
[PE1-ct-flow-mapping-mapping1] map ct 2 to be lpq
[PE1-ct-flow-mapping-mapping1] ct-flow-mapping commit
[PE1-ct-flow-mapping-mapping1] quit
[PE1] interface gigabitethernet 3/0/0
[PE1-GigabitEthernet3/0/0] mpls te ct-flow-mapping mapping1
[PE1-GigabitEthernet3/0/0] quit
# Configure PE2.
[PE2] ct-flow-mapping mapping1
[PE2-ct-flow-mapping-mapping1] map ct 0 to ef pq
[PE2-ct-flow-mapping-mapping1] map ct 1 to af1 wfq
[PE2-ct-flow-mapping-mapping1] map ct 2 to be lpq
[PE2-ct-flow-mapping-mapping1] ct-flow-mapping commit
[PE2-ct-flow-mapping-mapping1] quit
[PE2] interface gigabitethernet 3/0/0
[PE2-GigabitEthernet3/0/0] mpls te ct-flow-mapping mapping1
[PE2-GigabitEthernet3/0/0] quit
# After the configuration, run the display ct-flow-mapping command on PEs, and you can view
the mapping relationship of CTs and traffic queues.
Issue 02 (2011-09-10)
419
3 MPLS TE Configuration
# Configure PE2.
[PE2] interface gigabitethernet 3/0/0
[PE2-GigabitEthernet3/0/0] port-queue ef pq shaping 220000 outbound
[PE2-GigabitEthernet3/0/0] port-queue af1 wfq weight 15 shaping 120000 outbound
[PE2-GigabitEthernet3/0/0] port-queue be lpq shaping 150000 outbound
[PE2-GigabitEthernet3/0/0] quit
# Configure PE2.
[PE2] interface tunnel3/0/0
[PE2-Tunnel3/0/0] mpls te igp advertise
[PE2-Tunnel3/0/0] mpls te igp metric absolute 1
[PE2-Tunnel3/0/0] mpls te commit
[PE2-Tunnel3/0/0] mpls
[PE2-Tunnel3/0/0] quit
[PE2] ospf 1
[PE2-ospf-1] enable traffic-adjustment advertise
[PE2-ospf-1] quit
[PE2-] mpls ldp remote-peer pe2tope1
[PE2-mpls-ldp-remote-pe2tope1] remote-ip 1.1.1.9
Issue 02 (2011-09-10)
420
3 MPLS TE Configuration
After the configuration, run the display ip routing-table command on PE1 or PE2, and you can
view route information. The outbound interface destined for 5.5.5.9 is tunnel 3/0/0 on PE1 and
the outbound interface destined for 4.4.4.9 is tunnel 3/0/0 on PE2.
Step 13 Create the MP-IBGP remote peer relationship between PEs, and create the EBGP peer
relationship between PEs and CEs.
# Configure PE1.
[PE1] bgp 100
[PE1-bgp] peer 3.3.3.9 as-number 100
[PE1-bgp] peer 3.3.3.9 connect-interface loopback 1
[PE1-bgp] ipv4-family vpnv4
[PE1-bgp-af-vpnv4] peer 3.3.3.9 enable
[PE1-bgp-af-vpnv4] quit
[PE1-bgp] ipv4-family vpn-instance vpna
[PE1-bgp-vpna] peer 10.1.1.1 as-number 65410
[PE1-bgp-vpna] import-route direct
[PE1-bgp-vpna] quit
[PE1-bgp] ipv4-family vpn-instance vpnb
[PE1-bgp-vpnb] peer 10.2.1.1 as-number 65420
[PE1-bgp-vpnb] import-route direct
[PE1-bgp-vpnb] quit
NOTE
The configuration of PE2 is similar to that of PE1. The configuration details are not provided here.
# Configure CE1.
[CE1] bgp 65410
[CE1-bgp] peer 10.1.1.2 as-number 100
[CE1-bgp] import-route direct
NOTE
The configuration of other CEs (CE2, CE3, and CE4) is similar to that of CE1. The configuration details
are not provided here.
After the configuration, run the display bgp vpnv4 all peer command on the PE, and you can
see that the BGP peer relationship is created between PEs and its status is Established.
[PE1] display bgp vpnv4 all peer
BGP local router ID : 1.1.1.9
Local AS number : 100
Total number of peers : 3
Peer
V
AS MsgRcvd
3.3.3.9
4
100
Peer of vpn instance:
vpn instance vpna :
10.1.1.1
4 65410
vpn instance vpnb :
10.2.1.1
4 65420
MsgSent
12
18
0 00:09:38 Established
25
25
0 00:17:57 Established
21
22
0 00:17:10 Established
# Configure PE2.
[PE2] tunnel-policy policya
[PE2-tunnel-policy-policya] tunnel binding destination 1.1.1.9 te tunnel 3/0/0
Issue 02 (2011-09-10)
421
3 MPLS TE Configuration
[PE2-tunnel-policy-policya] quit
[PE2] tunnel-policy policyb
[PE2-tunnel-policy-policyb] tunnel binding destination 1.1.1.9 te tunnel 3/0/1
[PE2-tunnel-policy-policyb] quit
# Configure PE2.
[PE2] ip vpn-instance vpna
[PE2-vpn-instance-vpna] ipv4-family
[PE2-vpn-instance-vpna-af-ipv4] route-distinguisher 200:1
[PE2-vpn-instance-vpna-af-ipv4] vpn-target 111:1 both
[PE2-vpn-instance-vpna-af-ipv4] tnl-policy policya
[PE2-vpn-instance-vpna-af-ipv4] quit
PE2-vpn-instance-vpna] quit
[PE2] ip vpn-instance vpnb
[PE2-vpn-instance-vpnb] ipv4-family
[PE2-vpn-instance-vpnb-af-ipv4] route-distinguisher 200:2
[PE2-vpn-instance-vpnb-af-ipv4] vpn-target 222:2 both
[PE2-vpn-instance-vpnb-af-ipv4] tnl-policy policyb
[PE2-vpn-instance-vpnb-af-ipv4] quit
[PE2-vpn-instance-vpnb] quit
[PE2] interface gigabitethernet 1/0/0
[PE2-GigabitEthernet1/0/0] ip binding vpn-instance vpna
[PE2-GigabitEthernet1/0/0] ip address 10.3.1.2 24
[PE2-GigabitEthernet1/0/0] quit
[PE2] interface gigabitethernet 2/0/0
[PE2-GigabitEthernet2/0/0] ip binding vpn-instance vpnb
[PE2-GigabitEthernet2/0/0] ip address 10.4.1.2 24
[PE2-GigabitEthernet2/0/0] quit
# Configure IP addresses for interfaces of CEs. The configuration details are not provided here.
After the configuration, run the display ipvpn-instance verbose command on the PE, and you
can view the configuration of VPN instances. PEs can ping CEs connecting to PEs.
Step 16 Verify the configuration.
Issue 02 (2011-09-10)
422
3 MPLS TE Configuration
After the configuration, connect the tester to PE3, PE4, and all CEs and inject the following
traffic to the connected interfaces.
Traffic
Type
Bandwidth
EF
100 Mbit/s
AF
50 Mbit/s
EF
100 Mbit/s
AF
50 Mbit/s
BE
50 Mbit/s
BE
50 Mbit/s
You can see that all packets are not discarded. The jitter of EF traffic is shorter than 50 ms, and
the jitter of AF traffic is shorter than 200 ms.
----End
Configuration Files
l
Issue 02 (2011-09-10)
423
3 MPLS TE Configuration
ct-flow-mapping commit
#
te-class-mapping
te-class0 class-type ct0 priority 0 description For-BE
te-class1 class-type ct1 priority 0 description For-AF
te-class2 class-type ct2 priority 0 description For-EF
#
interface GigabitEthernet1/0/0
undo shutdown
ip binding vpn-instance vpna
ip address 10.1.1.2 255.255.255.0
trust upstream default
#
interface GigabitEthernet2/0/0
undo shutdown
ip binding vpn-instance vpnb
ip address 10.2.1.2 255.255.255.0
trust upstream default
#
interface GigabitEthernet3/0/0
undo shutdown
ip address 172.1.1.1 255.255.255.0
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 4000000
mpls te bandwidth bc0 400000 bc1 300000 bc2 200000
mpls rsvp-te
trust upstream default
mpls te ct-flow-mapping mapping1
port-queue ef pq shaping 220000 outbound
port-queue af1 wfq weight 15 shaping 120000 outbound
port-queue be lpq shaping 150000 outbound
#
interface GigabitEthernet4/0/0
undo shutdown
ip address 10.5.1.1 255.255.255.0
mpls
mpls ldp
trust upstream default
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
interface Tunnel3/0/0
description For VPN-A & Non-VPN
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 3.3.3.9
mpls te tunnel-id 300
mpls te priority 0
mpls te bandwidth ct0 50000 ct1 50000 ct2 100000
mpls te path explicit-path path1
mpls te igp advertise
mpls te igp metric absolute 1
mpls te commit
mpls
#
interface Tunnel3/0/1
description For VPN-B
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 3.3.3.9
mpls te tunnel-id 301
mpls te priority 0
mpls te bandwidth ct0 50000 ct1 50000 ct2 100000
mpls te path explicit-path path1
mpls te commit
#
bgp 100
Issue 02 (2011-09-10)
424
3 MPLS TE Configuration
Issue 02 (2011-09-10)
425
3 MPLS TE Configuration
area 0.0.0.0
opaque-capability enable
network 172.1.1.0 0.0.0.255
network 172.2.1.0 0.0.0.255
network 2.2.2.9 0.0.0.0
mpls-te enable
#
return
Issue 02 (2011-09-10)
426
3 MPLS TE Configuration
mpls te
mpls te bandwidth max-reservable-bandwidth 400000
mpls te bandwidth bc0 400000 bc1 200000 bc2 100000
mpls rsvp-te
trust upstream default
mpls te ct-flow-mapping mapping1
port-queue ef pq shaping 220000 outbound
port-queue af1 wfq weight 15 shaping 120000 outbound
port-queue be lpq shaping 150000 outbound
#
interface GigabitEthernet4/0/0
undo shutdown
ip address 10.6.1.1 255.255.255.0
mpls
mpls ldp
trust upstream default
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
interface Tunnel3/0/0
description For VPN-A & Non-VPN
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 1.1.1.9
mpls te tunnel-id 300
mpls te priority 0
mpls te bandwidth ct0 100000 ct1 50000 ct2 50000
mpls te path explicit-path path1
mpls te commit
#
interface Tunnel3/0/1
description For VPN-B
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 1.1.1.9
mpls te tunnel-id 301
mpls te priority 0
mpls te bandwidth ct0 100000 ct1 50000 ct2 50000
mpls te path explicit-path path1
mpls te commit
#
bgp 100
peer 1.1.1.9 as-number 100
peer 1.1.1.9 connect-interface LoopBack1
#
ipv4-family unicast
undo synchronization
peer 1.1.1.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.9 enable
#
ipv4-family vpn-instance vpna
peer 10.3.1.1 as-number 65430
import-route direct
#
ipv4-family vpn-instance vpnb
peer 10.4.1.1 as-number 65440
import-route direct
#
ospf 1
opaque-capability enable
enable traffic-adjustment advertise
area 0.0.0.0
network 172.2.1.0 0.0.0.255
network 10.6.1.0 0.0.0.255
network 3.3.3.9 0.0.0.0
Issue 02 (2011-09-10)
427
3 MPLS TE Configuration
mpls-te enable
#
tunnel-policy policya
tunnel binding destination 1.1.1.9 te Tunnel3/0/0
#
tunnel-policy policyb
tunnel binding destination 1.1.1.9 te Tunnel3/0/1
#
return
Issue 02 (2011-09-10)
428
3 MPLS TE Configuration
#
ipv4-family unicast
undo synchronization
import-route direct
peer 10.1.1.2 enable
#
return
429
3 MPLS TE Configuration
Networking Requirements
On the network shown in the following figure, two static DS-TE tunnels between PE1 and PE2
are set up in non-IETF mode for transmitting EF traffic of VPN-A and BE traffic of VPN-B.
The DS-TE tunnel set up in non-IETF mode supports only the single CT, namely, CT0 or CT1.
In the case of network expansion, it is required that the non-IETF mode be switched to the IETF
mode supporting eight CTs.
Figure 3-14 Networking diagram of switching the non-IETF mode to the IETF mode
AS: 65410
VPN-A
AS: 65430
CE1
CE3
GE1/0/0
10.1.1.1/24
GE1/0/0
10.1.1.2/24
Loopback1
1.1.1.9/32
GE2/0/0
10.2.1.2/24
GE1/0/0
10.3.1.1/24
Loopback1
2.2.2.9/32
GE2/0/0 PE2
PE1 GE1/0/0
172.1.1.2/24
172.2.1.1/24
GE3/0/0
GE3/0/0
172.2.1.2/24
172.1.1.1/24
P
MPLS backbone
AS: 100
GE1/0/0
10.2.1.1/24
GE1/0/0
10.3.1.2/24
Loopback1
3.3.3.9/32
GE2/0/0
10.4.1.2/24
GE1/0/0
10.4.1.1/24
CE4
CE2
VPN-B
VPN-A
AS: 65420
AS: 65440
VPN-B
Configuration Roadmap
The configuration roadmap is as follows:
NOTE
l In this example, the bandwidth and delay time are guaranteed for all service traffic of each VPN in DSTE tunnels.
l If you need to guarantee the bandwidth and delay time for all service traffic only in DS-TE tunnels
irrespective of VPNs, you can set up only one DS-TE tunnel to transmit all the traffic.
l You can limit the service traffic of different VPNs in DS-TE tunnels by limiting the ingress PE to
access VPNs and the service traffic of VPNs.
1.
Issue 02 (2011-09-10)
When the non-IETF mode is switched to the IETF mode, the system automatically deletes
the CR-LSPs whose combination of <CT, set-priority> or combination of <CT, holdpriority> does not exist in the TE-class mapping table. If the TE-class mapping table is
improperly configured, the CR-LSP that transmits traffic may be deleted incorrectly,
resulting in service interruption. Therefore, before switching the DS-TE mode, you need
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
430
3 MPLS TE Configuration
to check the CTs, setup priority, and holding priority of the ingress and transit CR-LSPs,
and the configuration of TE-class mapping table.
2.
For certain CR-LSPs, if the combination of the CT and setup priority or the combination
of the CT and holding priority does not exist in the TE-class mapping table, you need to
configure or modify the TE-class mapping table.
3.
4.
Data Preparation
None
Procedure
Step 1 Run the display current-configuration | include static-cr-lsp ingress and display currentconfiguration | include static-cr-lsp transit commands on PE1, P, and PE2, and you can view
the CTs of the static ingress and transit CR-LSPs, and the TE-class mapping table.
NOTE
l For static CR-LSPs, both the setup priority and the holding priority are 0 and the two priorities need
not to be checked.
l For RSVP CR-LSPs, run the display current-configuration interface tunnel command, and you can
view the configured mpls te bandwidth and mpls te priority commands, CTs, setup priority, and
holding priority on each tunnel interface.
# Run the display current-configuration | include static-cr-lsp ingress and display currentconfiguration | include static-cr-lsp transit commands on the PE and P, and you can view
CTs, setup and holding priorities of the static ingress and transit CR-LSPs. Then, run the display
mpls te ds-te te-class-mapping config command, and you can view the configuration of the
TE-class mapping table.
# Take the display on PE1 as an example. The operation on other nodes is similar to that on PE1
and therefore is not provided here.
<PE1> display current-configuration | include static-cr-lsp ingress
static-cr-lsp ingress tunnel-interface Tunnel 3/0/0 destination 3.3.3.9 nexthop
172.1.1.2 out-label 100 bandwidth ct0 100000
static-cr-lsp ingress tunnel-interface tunnel 3/0/1 destination 3.3.3.9 nexthop
172.1.1.2 out-label 200 bandwidth ct1 200000
<PE1> display current-configuration | include static-cr-lsp transit
<PE1> display mpls te ds-te te-class-mapping config Info: Configure TE-Class first.
NOTE
The display current-configuration | include static-cr-lsp transit command output is null, indicating that
no static transit CR-LSP is set up on PE1.
The display mpls te ds-te te-class-mapping config command output shows "Info: Configure TE-Class
first.", indicating that no TE-class mapping table is configured on PE1.
# The command output indicates that the static CR-LSPs of CT0 and CT1 are set up on PE1. In
addition, because the setup and holding priorities of the static CR-LSPs are 0, the following TEclasses must exist in the TE-class mapping table:
l <CT = CT0, Priority = 0>
l <CT = CT1, Priority = 0>
Step 2 Configure TE-classes on PE1, P, and PE2.
Issue 02 (2011-09-10)
431
3 MPLS TE Configuration
In this example, the TE-classes of <CT = CT0, Priority = 0> and <CT = CT1, Priority = 0> need
to be configured. Because the two TE-classes already exist in the default TE-class mapping table,
no other TE-class mapping table needs to be configured in this example. After the non-IETF
mode is switched to the IETF mode, the system uses the default TE-class mapping table.
NOTE
For information about the default TE-class mapping table, see Table 3-2.
# Configure P.
[P] mpls
[P-mpls] mpls te ds-te mode ietf
[P-mpls] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] mpls te ds-te mode ietf
[PE2-mpls] quit
NOTE
After the non-IETF mode is switched to the IETF mode, the bandwidth constraints model remains
unchanged and does not need to be configured again.
In addition, related configurations of DS-TE and services accesses are required according to the service.
The configurations are not provided in this example.
----End
Configuration Files
l
Issue 02 (2011-09-10)
432
3 MPLS TE Configuration
#
interface GigabitEthernet1/0/0
undo shutdown
ip binding vpn-instance vpna
ip address 10.1.1.2 255.255.255.0
trust upstream default
#
interface GigabitEthernet2/0/0
undo shutdown
ip binding vpn-instance vpnb
ip address 10.2.1.2 255.255.255.0
trust upstream default
#
interface GigabitEthernet3/0/0
undo shutdown
ip address 172.1.1.1 255.255.255.0
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 300000
mpls te bandwidth bc0 100000 bc1 200000
trust upstream default
mpls te ct-flow-mapping mapping1
mpls te ct-bandwidth unshared
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
interface Tunnel3/0/0
description For VPN-A_EF
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 3.3.3.9
mpls te tunnel-id 300
mpls te signal-protocol cr-static
mpls te commit
#
interface Tunnel3/0/1
description For VPN-B_BE
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 3.3.3.9
mpls te tunnel-id 301
mpls te signal-protocol cr-static
mpls te commit
#
bgp 100
peer 3.3.3.9 as-number 100
peer 3.3.3.9 connect-interface LoopBack1
#
ipv4-family unicast
undo synchronization
peer 3.3.3.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 3.3.3.9 enable
#
ipv4-family vpn-instance vpna
peer 10.1.1.1 as-number 65410
import-route direct
#
ipv4-family vpn-instance vpnb
peer 10.2.1.1 as-number 65420
import-route direct
#
ospf 1
opaque-capability enable
area 0.0.0.0
network 172.1.1.0 0.0.0.255
Issue 02 (2011-09-10)
433
3 MPLS TE Configuration
Issue 02 (2011-09-10)
434
3 MPLS TE Configuration
Issue 02 (2011-09-10)
435
3 MPLS TE Configuration
Networking Requirements
On the network shown in Figure 3-15, the primary LSP is along the path LSR A --> LSR B -> LSR C --> LSR D, and the link from LSR B to LSR C requires a link protection by using FRR.
A bypass LSP is set up over the path LSR B --> LSR E --> LSR C. LSR B is a PLR, and LSR
C is an MP.
An explicit path is used to establish the MPLS TE primary and the bypass tunnels. The RSVPTE signaling protocol is adopted.
Issue 02 (2011-09-10)
436
3 MPLS TE Configuration
Loopback1
4.4.4.4/32
LSRD
GE1/0/0
4.1.1.2/24
Loopback1
1.1.1.1/32
Loopback1
2.2.2.2/32
Loopback1
3.3.3.3/32
GE1/0/0
4.1.1.1/24
LSRB
LSRA
GE2/0/0
GE2/0/0
GE1/0/0
GE1/0/0
3.1.1.1/24 3.1.1.2/24
2.1.1.1/24 2.1.1.2/24
POS3/0/0
Loopback1
3.2.1.1/24
5.5.5.5/32
Primary LSP
Bypass LSP
LSRC
POS3/0/0
3.3.1.2/24
POS2/0/0
3.3.1.1/24
POS1/0/0
3.2.1.2/24
LSRE
Configuration Roadmap
The configuration roadmap is as follows:
1.
Establish the primary tunnel and enable TE FRR in the tunnel interface view.
2.
Configure the bypass tunnel on the PLR (LSRB) and specify the protectable bandwidth
and the interface to be protected.
Data Preparation
To complete the configuration, you need the following data:
l
IS-IS area ID on each LSR, original system ID, and IS-IS level
Maximum reservable bandwidth and BC bandwidth for the link along the tunnel
Interface names, IP addresses, destination addresses, tunnel IDs, tunnel signaling protocol
(RSVP-TE) of the primary and bypass tunnels
Bandwidth that the bypass tunnel can protect and the protected link interface
Procedure
Step 1 Configure IP address on each interface.
The IP address and mask on each interface including the loopback interface are configured as
shown in Figure 3-15. The detailed configuration is not mentioned here.
Issue 02 (2011-09-10)
437
3 MPLS TE Configuration
The configurations of LSR B, LSR C, LSR D, and LSR E are similar to those of LSR A and LSR B, and
are not provided here.
Only LSR A and LSR B need to be enabled CSPF.
# Configure LSR B.
[LSRB] interface gigabitethernet 2/0/0
[LSRB-GigabitEthernet2/0/0] mpls te bandwidth max-reservable-bandwidth 100000
[LSRB-GigabitEthernet2/0/0] mpls te bandwidth bc0 100000
[LSRB-GigabitEthernet2/0/0] quit
[LSRB] interface pos 3/0/0
[LSRB-Pos3/0/0] mpls te bandwidth max-reservable-bandwidth 100000
[LSRB-Pos3/0/0] mpls te bandwidth bc0 100000
[LSRB-Pos3/0/0] quit
# Configure LSR C.
[LSRC] interface gigabitethernet 1/0/0
[LSRC-GigabitEthernet1/0/0] mpls te bandwidth max-reservable-bandwidth 100000
[LSRC-GigabitEthernet1/0/0] mpls te bandwidth bc0 100000
[LSRC-GigabitEthernet1/0/0] quit
# Configure LSR E.
[LSRE] interface pos 2/0/0
[LSRE-Pos2/0/0] mpls te bandwidth max-reservable-bandwidth 100000
[LSRE-Pos2/0/0] mpls te bandwidth bc0 100000
Issue 02 (2011-09-10)
438
3 MPLS TE Configuration
[LSRE-Pos2/0/0] quit
next
next
next
next
quit
hop
hop
hop
hop
2.1.1.2
3.1.1.2
4.1.1.2
4.4.4.4
# Enable FRR.
[LSRA-Tunnel1/0/0] mpls te fast-reroute
[LSRA-Tunnel1/0/0] mpls te commit
[LSRA-Tunnel1/0/0] quit
After the configuration, run the display interface tunnel command on LSR A. The status of
Tunnel 1/0/0 is Up.
[LSRA] display interface tunnel 1/0/0
Tunnel1/0/0 current state : UP
Line protocol current state : UP
Last up time: 2009-01-12, 09:35:10
Description : Tunnel1/0/0 Interface, Route Port
...
Run the display mpls te tunnel verbose command on LSR A. You can view information about
the tunnel interface.
[LSRA] display mpls te tunnel verbose
No
: 1
Tunnel-Name
: Tunnel1/0/0
TunnelIndex
: 0
LSP Index
: 2048
Session ID
: 100
LSP ID
: 1
Lsr Role
: Ingress
Lsp Type
: Primary
Ingress LSR ID
: 1.1.1.1
Egress LSR ID
: 4.4.4.4
In-Interface
: Out-Interface
: GE1/0/0
Sign-Protocol
: RSVP TE
Resv Style
: SE
IncludeAnyAff
: 0x0
ExcludeAnyAff
: 0x0
IncludeAllAff
: 0x0
LspConstraint
: ER-Hop Table Index
: 0
AR-Hop Table Index: 0
C-Hop Table Index
: 0
PrevTunnelIndexInSession: NextTunnelIndexInSession: PSB Handle
: 1081
Created Time
: 2010/07/01 15:02:57 UTC-08:00
-------------------------------DS-TE Information
-------------------------------Bandwidth Reserved Flag : Reserved
CT0 Bandwidth(Kbit/sec) : 50000
CT1 Bandwidth(Kbit/sec): 0
CT2 Bandwidth(Kbit/sec) : 0
CT3 Bandwidth(Kbit/sec): 0
CT4 Bandwidth(Kbit/sec) : 0
CT5 Bandwidth(Kbit/sec): 0
Issue 02 (2011-09-10)
439
3 MPLS TE Configuration
CT6 Bandwidth(Kbit/sec) : 0
CT7 Bandwidth(Kbit/sec): 0
Setup-Priority
: 7
Hold-Priority
: 7
-------------------------------FRR Information
-------------------------------Primary LSP Info
TE Attribute Flag
: 0x63
Protected Flag
: 0x0
Bypass In Use
: Not Exists
Bypass Tunnel Id
: BypassTunnel
: Bypass Lsp ID
: FrrNextHop
: ReferAutoBypassHandle
: FrrPrevTunnelTableIndex : FrrNextTunnelTableIndex: Bypass Attribute(Not configured)
Setup Priority
: Hold Priority
: HopLimit
: Bandwidth
: IncludeAnyGroup
: ExcludeAnyGroup
: IncludeAllGroup
: Bypass Unbound Bandwidth Info(Kbit/sec)
CT0 Unbound Bandwidth
: CT1 Unbound Bandwidth: CT2 Unbound Bandwidth
: CT3 Unbound Bandwidth: CT4 Unbound Bandwidth
: CT5 Unbound Bandwidth: CT6 Unbound Bandwidth
: CT7 Unbound Bandwidth: -------------------------------BFD Information
-------------------------------NextSessionTunnelIndex : PrevSessionTunnelIndex: NextLspId
: PrevLspId
: -
After the configuration, run the display interface tunnel command on LSR B. You can view
that the status of the Tunnel 3/0/0 interface is Up.
Run the display mpls lsp command on all LSRs to check LSP entries. You can view that LSPs
pass through LSR B and LSR C.
[LSRA] display mpls lsp
-----------------------------------------------------------------LSP Information: RSVP LSP
Issue 02 (2011-09-10)
440
3 MPLS TE Configuration
-----------------------------------------------------------------FEC
In/Out Label In/Out IF
Vrf Name
4.4.4.4/32
NULL/1024
-/GE1/0/0
[LSRB] display mpls lsp
-----------------------------------------------------------------LSP Information: RSVP LSP
-----------------------------------------------------------------FEC
In/Out Label In/Out IF
Vrf Name
4.4.4.4/32
1024/1024
GE1/0/0/GE2/0/0
3.3.3.3/32
NULL/1024
-/Pos3/0/0
[LSRC] display mpls lsp
-----------------------------------------------------------------LSP Information: RSVP LSP
-----------------------------------------------------------------FEC
In/Out Label In/Out IF
Vrf Name
4.4.4.4/32
1024/3
GE2/0/0/GE1/0/0
3.3.3.3/32
3/NULL
Pos3/0/0/[LSRD] display mpls lsp
-----------------------------------------------------------------LSP Information: RSVP LSP
-----------------------------------------------------------------FEC
In/Out Label In/Out IF
Vrf Name
4.4.4.4/32
3/NULL
GE1/0/0/[LSRE] display mpls lsp
-----------------------------------------------------------------LSP Information: RSVP LSP
-----------------------------------------------------------------FEC
In/Out Label In/Out IF
Vrf Name
3.3.3.3/32
1024/3
Pos1/0/0/Pos2/0/0
Run the display mpls te tunnel command on all the LSRs to check the establishment status of
the tunnel. You can view that two tunnels pass through LSR B and LSR C.
[LSRA] display mpls te tunnel
-----------------------------------------------------------------------------Ingress LsrId
Destination
LSPID
In/Out Label
R Tunnel-name
-----------------------------------------------------------------------------1.1.1.1
4.4.4.4
1
--/3
I Tunnel1/0/0
[LSRB] display mpls te tunnel
-----------------------------------------------------------------------------Ingress LsrId
Destination
LSPID
In/Out Label
R Tunnel-name
-----------------------------------------------------------------------------1.1.1.1
4.4.4.4
1
1026/3
I Tunnel1/0/0
2.2.2.2
3.3.3.3
1
--/3
I Tunnel3/0/0
[LSRC] display mpls te tunnel
-----------------------------------------------------------------------------Ingress LsrId
Destination
LSPID
In/Out Label
R Tunnel-name
-----------------------------------------------------------------------------1.1.1.1
4.4.4.4
1
1024/3
I Tunnel1/0/0
2.2.2.2
3.3.3.3
1
3/-I Tunnel3/0/0
[LSRE] display mpls te tunnel
-----------------------------------------------------------------------------Ingress LsrId
Destination
LSPID
In/Out Label
R Tunnel-name
-----------------------------------------------------------------------------2.2.2.2
3.3.3.3
1
1025/3
I Tunnel3/0/0
Run the display mpls te tunnel name Tunnel1/0/0 verbose command on LSR B. You can view
that the bypass tunnel is bound to GE 2/0/0 and remains unused.
[LSRB] display mpls te tunnel name Tunnel1/0/0
No
: 1
Tunnel-Name
: Tunnel1/0/0
TunnelIndex
: 1
LSP
Session ID
: 100
LSP
Lsr Role
: Transit
LSP
Issue 02 (2011-09-10)
verbose
Index
ID
Type
:
:
:
4098
1
Primary
441
3 MPLS TE Configuration
Ingress LSR ID
: 1.1.1.1
Egress LSR ID
: 4.4.4.4
In-Interface
: GE1/0/0
Out-Interface
: GE2/0/0
Sign-Protocol
: RSVP TE
Resv Style
: SE
IncludeAnyAff
: 0x0
ExcludeAnyAff
: 0x0
IncludeAllAff
: 0x0
LspConstraint
: ER-Hop Table Index
: AR-Hop Table Index: 2
C-Hop Table Index
: 1
PrevTunnelIndexInSession: NextTunnelIndexInSession: PSB Handle
: 65546
Created Time
: 2009/01/12 09:42:04
-------------------------------DS-TE Information
-------------------------------Bandwidth Reserved Flag : Reserved
CT0 Bandwidth(Kbit/sec) : 100000
CT1 Bandwidth(Kbit/sec): 0
CT2 Bandwidth(Kbit/sec) : 0
CT3 Bandwidth(Kbit/sec): 0
CT4 Bandwidth(Kbit/sec) : 0
CT5 Bandwidth(Kbit/sec): 0
CT6 Bandwidth(Kbit/sec) : 0
CT7 Bandwidth(Kbit/sec): 0
Setup-Priority
: 7
Hold-Priority
: 7
-------------------------------FRR Information
-------------------------------Primary LSP Info
TE Attribute Flag
: 0x63
Protected Flag
: 0x1
Bypass In Use
: Not Used
Bypass Tunnel Id
: 67141670
BypassTunnel
: Tunnel Index[Tunnel3/0/0], InnerLabel[1024]
Bypass Lsp ID
: 9
FrrNextHop
: 3.3.1.2
ReferAutoBypassHandle
: FrrPrevTunnelTableIndex : FrrNextTunnelTableIndex: Bypass Attribute(Not configured)
Setup Priority
: Hold Priority
: HopLimit
: Bandwidth
: IncludeAnyGroup
: ExcludeAnyGroup
: IncludeAllGroup
: Bypass Unbound Bandwidth Info(Kbit/sec)
CT0 Unbound Bandwidth
: CT1 Unbound Bandwidth: CT2 Unbound Bandwidth
: CT3 Unbound Bandwidth: CT4 Unbound Bandwidth
: CT5 Unbound Bandwidth: CT6 Unbound Bandwidth
: CT7 Unbound Bandwidth: -------------------------------BFD Information
-------------------------------NextSessionTunnelIndex : PrevSessionTunnelIndex: NextLspId
: PrevLspId
: -
Run the display interface tunnel 1/0/0 command on LSR A. You can view the status of the
primary LSP. The status of the tunnel interface is still Up.
Run the tracert lsp te tunnel 1/0/0 command on LSR A. You can view the path over which the
tunnel is established.
[LSRA] tracert lsp te tunnel 1/0/0
LSP Trace Route FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel1/0/0 , press CTRL_C to
break.
TTL
Replier
Time
Type
Downstream
Issue 02 (2011-09-10)
442
3 MPLS TE Configuration
2.1.1.2
3.2.1.2
3.3.1.2
4.1.1.2
1 ms
16 ms
1 ms
1 ms
Ingress
Transit
Transit
Transit
Egress
2.1.1.2/[13312 ]
The preceding information shows that the link is already switched to the bypass tunnel.
NOTE
After FRR swithing, run the display mpls te tunnel-interface command immediately, and you can view
that two CR-LSPs are in the Up state because FRR establishes a new LSP by using make-before-break.
The old LSP is deleted only after the new LSP has been established successfully.
Run the display mpls te tunnel name Tunnel1/0/0 verbose command on LSR B. You can view
that the bypass tunnel is used.
[LSRB] display mpls te tunnel name Tunnel1/0/0 verbose
No
: 1
Tunnel-Name
: Tunnel1/0/0
TunnelIndex
: 1
LSP Index
: 4098
Session ID
: 100
LSP ID
: 1
Lsr Role
: Transit
Ingress LSR ID
: 1.1.1.1
Egress LSR ID
: 4.4.4.4
In-Interface
: GE1/0/0
Out-Interface
: GE2/0/0
Sign-Protocol
: RSVP TE
Resv Style
: SE
IncludeAnyAff
: 0x0
ExcludeAnyAff
: 0x0
IncludeAllAff
: 0x0
ER-Hop Table Index
: 3
AR-Hop Table Index: 12
C-Hop Table Index
: 50
PrevTunnelIndexInSession: NextTunnelIndexInSession: PSB Handle
: 66000
Created Time
: 2009/01/12 10:09:10
-------------------------------DS-TE Information
-------------------------------Bandwidth Reserved Flag : Unreserved
CT0 Bandwidth(Kbit/sec) : 100000
CT1 Bandwidth(Kbit/sec): 0
CT2 Bandwidth(Kbit/sec) : 0
CT3 Bandwidth(Kbit/sec): 0
CT4 Bandwidth(Kbit/sec) : 0
CT5 Bandwidth(Kbit/sec): 0
CT6 Bandwidth(Kbit/sec) : 0
CT7 Bandwidth(Kbit/sec): 0
Setup-Priority
: 7
Hold-Priority
: 7
-------------------------------FRR Information
-------------------------------Primary LSP Info
TE Attribute Flag
: 0x63
Protected Flag
: 0x1
Bypass In Use
: In Use
Bypass Tunnel Id
: 67141670
BypassTunnel
: Tunnel Index[Tunnel3/0/0], InnerLabel[1024]
Bypass Lsp ID
: 9
FrrNextHop
: 3.3.1.2
ReferAutoBypassHandle
: FrrPrevTunnelTableIndex : FrrNextTunnelTableIndex: Bypass Attribute(Not configured)
Setup Priority
: Hold Priority
: HopLimit
: Bandwidth
: IncludeAnyGroup
: ExcludeAnyGroup
: IncludeAllGroup
: Bypass Unbound Bandwidth Info(Kbit/sec)
CT0 Unbound Bandwidth
: CT1 Unbound Bandwidth: CT2 Unbound Bandwidth
: CT3 Unbound Bandwidth: CT4 Unbound Bandwidth
: CT5 Unbound Bandwidth: CT6 Unbound Bandwidth
: CT7 Unbound Bandwidth: -------------------------------BFD Information
-------------------------------NextSessionTunnelIndex : PrevSessionTunnelIndex: NextLspId
: PrevLspId
: -
Issue 02 (2011-09-10)
443
3 MPLS TE Configuration
Run the display interface tunnel 1/0/0 command. You can view the status of the primary LSP
on LSR A. The tunnel interface is in Up state.
After a while, run the display mpls te tunnel name Tunnel1/0/0 verbose command on LSR B.
You can view that Tunnel 3/0/0 is bound to GE 2/0/0 and remains unused.
----End
Configuration Files
l
Issue 02 (2011-09-10)
444
3 MPLS TE Configuration
return
Issue 02 (2011-09-10)
445
3 MPLS TE Configuration
l
Issue 02 (2011-09-10)
446
3 MPLS TE Configuration
#
sysname LSRE
#
mpls lsr-id 5.5.5.5
mpls
mpls te
mpls rsvp-te
#
isis 1
is-level level-2
cost-style wide
network-entity 00.0005.0000.0000.0005.00
traffic-eng level-2
#
interface Pos1/0/0
link-protocol ppp
clock master
ip address 3.2.1.2 255.255.255.0
isis enable 1
mpls
mpls te
mpls rsvp-te
#
interface Pos2/0/0
link-protocol ppp
clock master
ip address 3.3.1.1 255.255.255.0
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
mpls rsvp-te
#
interface LoopBack1
ip address 5.5.5.5 255.255.255.255
isis enable 1
#
return
Networking Requirements
On the network shown in Figure 3-16, a primary tunnel is set up over the explicit path LSR A
--> LSR B --> LSR C. A bypass tunnel is set up on the headend LSR A for node protection and
a bypass tunnel is set up on the transit LSR B for link protection, and both of them provide
bandwidth protection.
Issue 02 (2011-09-10)
447
3 MPLS TE Configuration
Loopback1
1.1.1.1/32
LSRA
GE1/0/0
10.1.1.2/24
Loopback1
2.2.2.2/32
Loopback1
3.3.3.3/32
GE3/0/0
GE2/0/0
3.1.1.2/24
3.1.1.1/24
GE3/0/0
2.1.1.2/24
GE2/0/0
LSRB
2.1.1.1/24 GE1/0/0
Loopback1
3.2.1.1/24
4.4.4.4/32
GE3/0/0
3.2.1.2/24
LSRC
GE1/0/0
10.1.1.1/24
GE2/0/0
4.1.1.2/24
GE2/0/0
4.1.1.1/24
LSRE
Configuration Roadmap
The configuration roadmap is as follows:
1.
Set up a primary tunnel, enable TE FRR in the tunnel interface view, and enable TE Auto
FRR in the MPLS view.
2.
Specify the bandwidth that the bypass tunnel can protect and the setup and holding priorities
of the bypass tunnel.
Data Preparation
To complete the configuration, you need the following data.
l
Name of the primary tunnel interface, IP address, destination address, tunnel ID, tunnel
signaling protocol (RSVP-TE), and tunnel bandwidth
Procedure
Step 1 Configure the IP address for each interface.
Configure the IP address and mask for each interface including Loopback interfaces as shown
in Figure 3-16. The detailed configuration is not provided here.
Step 2 Configure OSPF on all LSRs to advertise the routes of each network segment and the host route
of each LSR ID.
Configure OSPF on all LSRs to advertise the host route of each LSR ID. The detailed
configuration is not provided here.
After the configuration, run the display ip routing-table command on each LSR. You can view
that the LSRs have learned the host routes of LSR IDs from each other.
Issue 02 (2011-09-10)
448
3 MPLS TE Configuration
Step 3 Configure the basic MPLS functions and enable MPLS TE, RSVP-TE, and CSPF.
# Configure LSR A.
[LSRA] mpls lsr-id 1.1.1.1
[LSRA] mpls
[LSRA-mpls] mpls te
[LSRA-mpls] mpls rsvp-te
[LSRA-mpls] mpls te cspf
[LSRA-mpls] quit
[LSRA] interface gigabitethernet
[LSRA-GigabitEthernet2/0/0] mpls
[LSRA-GigabitEthernet2/0/0] mpls
[LSRA-GigabitEthernet2/0/0] mpls
[LSRA-GigabitEthernet2/0/0] quit
[LSRA] interface gigabitethernet
[LSRA-GigabitEthernet1/0/0] mpls
[LSRA-GigabitEthernet1/0/0] mpls
[LSRA-GigabitEthernet1/0/0] mpls
[LSRA-GigabitEthernet1/0/0] quit
2/0/0
te
rsvp-te
1/0/0
te
rsvp-te
NOTE
The configurations of LSR B, LSR C, and LSR D are similar to that of LSR A, and are not provided here.
CSPF is enabled only on LSR A and LSR B.
# Configure LSR B.
[LSRB] ospf
[LSRB-ospf-1] opaque-capability enable
[LSRB-ospf-1] area 0
[LSRB-ospf-1-area-0.0.0.0] mpls-te enable
[LSRB-ospf-1-area-0.0.0.0] quit
[LSRB-ospf-1] quit
# Configure LSR C.
[LSRC] ospf
[LSRC-ospf-1] opaque-capability enable
[LSRC-ospf-1] area 0
[LSRC-ospf-1-area-0.0.0.0] mpls-te enable
[LSRC-ospf-1-area-0.0.0.0] quit
[LSRC-ospf-1] quit
# Configure LSR D.
[LSRD] ospf
[LSRD-ospf-1] opaque-capability enable
[LSRD-ospf-1] area 0
[LSRD-ospf-1-area-0.0.0.0] mpls-te enable
[LSRD-ospf-1-area-0.0.0.0] quit
[LSRD-ospf-1] quit
449
3 MPLS TE Configuration
# Configure LSR A.
[LSRA] interface gigabitethernet 2/0/0
[LSRA-GigabitEthernet2/0/0] mpls te bandwidth max-reservable-bandwidth 10000
[LSRA-GigabitEthernet2/0/0] mpls te bandwidth bc0 10000 bc1 3000
The outgoing interfaces on the link through which the primary and bypass tunnels pass use are
similar to these configurations, and are not provided here.
Step 6 Configure the explicit path for the primary tunnel.
[LSRA] explicit-path master
[LSRA-explicit-path-master] next hop 2.1.1.2
[LSRA-explicit-path-master] next hop 3.1.1.2
# Configure LSR B.
[LSRB] mpls
[LSRB-mpls] mpls te auto-frr
verbose
Index
ID
Type
:
:
:
3072
1
Primary
Ingress LSR ID
: 1.1.1.1
Egress LSR ID
: 3.3.3.3
In-Interface
: Out-Interface
: GE2/0/0
Sign-Protocol
: RSVP TE
Resv Style
: SE
IncludeAnyAff
: 0x0
ExcludeAnyAff
: 0x0
IncludeAllAff
: 0x0
LspConstraint
: ER-Hop Table Index
: AR-Hop Table Index: 2
C-Hop Table Index
: PrevTunnelIndexInSession: NextTunnelIndexInSession:
PSB Handle
: 65546
Created Time
: 2009/03/30 09:52:03
-------------------------------DS-TE Information
Issue 02 (2011-09-10)
450
3 MPLS TE Configuration
You can view that the primary tunnel is bound to the Auto bypass tunnel, that is, Tunnel 0/0/2048.
Run the display mpls te tunnel name Tunnel0/0/2048 verbose command. You can view
detailed information about the Auto bypass tunnel. The bandwidth, setup priority, and holding
priority of the Auto bypass tunnel are the same as the bypass-attributes of the primary tunnel.
[LSRA] display mpls te tunnel name Tunnel0/0/2048 verbose
No
: 1
Tunnel-Name
: Tunnel0/0/2048
TunnelIndex
: 3
LSP Index
: 2051
Session ID
: 1026
LSP ID
: 1
Lsr Role
: Ingress
Lsp Type
: Primary
Ingress LSR ID
: 1.1.1.1
Egress LSR ID
: 3.3.3.3
In-Interface
: Out-Interface
: GE1/0/0
Sign-Protocol
: RSVP TE
Resv Style
: SE
IncludeAnyAff
: 0x0
ExcludeAnyAff
: 0x0
IncludeAllAff
: 0x0
LspConstraint
: ER-Hop Table Index
: AR-Hop Table Index: 3
C-Hop Table Index
: 3
PrevTunnelIndexInSession: NextTunnelIndexInSession: PSB Handle
: 1027
Created Time
: 2010/07/01 13:35:53 UTC-08:00
-------------------------------DS-TE Information
-------------------------------Bandwidth Reserved Flag : Reserved
CT0 Bandwidth(Kbit/sec) : 200
CT1 Bandwidth(Kbit/sec): 0
CT2 Bandwidth(Kbit/sec) : 0
CT3 Bandwidth(Kbit/sec): 0
CT4 Bandwidth(Kbit/sec) : 0
CT5 Bandwidth(Kbit/sec): 0
CT6 Bandwidth(Kbit/sec) : 0
CT7 Bandwidth(Kbit/sec): 0
Setup-Priority
: 5
Hold-Priority
: 4
--------------------------------
Issue 02 (2011-09-10)
451
3 MPLS TE Configuration
FRR Information
-------------------------------Primary LSP Info
TE Attribute Flag
: 0x3
Protected Flag
: 0x0
Bypass In Use
: Not Exists
Bypass Tunnel Id
: BypassTunnel
: Bypass Lsp ID
: FrrNextHop
: ReferAutoBypassHandle
: FrrPrevTunnelTableIndex : FrrNextTunnelTableIndex: Bypass Attribute(Not configured)
Setup Priority
: Hold Priority
: HopLimit
: Bandwidth
: IncludeAnyGroup
: ExcludeAnyGroup
: IncludeAllGroup
: Bypass Unbound Bandwidth Info(Kbit/sec)
CT0 Unbound Bandwidth
: CT1 Unbound Bandwidth: CT2 Unbound Bandwidth
: CT3 Unbound Bandwidth: CT4 Unbound Bandwidth
: CT5 Unbound Bandwidth: CT6 Unbound Bandwidth
: CT7 Unbound Bandwidth: -------------------------------BFD Information
-------------------------------NextSessionTunnelIndex : PrevSessionTunnelIndex: NextLspId
: PrevLspId
: -
You can view that the Auto bypass tunnel protects traffic on GE 2/0/0 but not other three
interfaces on the primary tunnel. The bandwidth of the Auto bypass tunnel is 200 kbit/s, and its
setup and holding priorities are 5 and 4 respectively.
Run the display mpls te tunnel path command on LSR A. You can view information about the
primary tunnel and the Auto bypass tunnel, and node and bandwidth protection that are provided
for the outgoing interface of the primary tunnel.
[LSRA] display mpls te tunnel path
Tunnel Interface Name : Tunnel2/0/0
Lsp ID : 1.1.1.1 :200:1
Hop Information
Hop 0
2.1.1.1 Local-Protection available | bandwidth | node
Hop 1
2.1.1.2 Label 106497
Hop 2
2.2.2.2
Hop 3
3.1.1.1 Local-Protection available | bandwidth
Hop 4
3.1.1.2 Label 3
Hop 5
3.3.3.3
Tunnel Interface Name : Tunnel0/0/2048
Lsp ID : 2.2.2.2 :2049 :2
Hop Information
Hop 0
2.2.2.2
Hop 1
3.2.1.1
Hop 2
3.2.1.2
Hop 3
4.4.4.4
Hop 4
4.1.1.1
Hop 5
4.1.1.2
Hop 6
3.3.3.3
Tunnel Interface Name : Tunnel0/0/2048
Lsp ID : 1.1.1.1 :2049:3
Hop Information
Hop 0
10.1.1.2
Hop 1
10.1.1.1
Hop 2
3.3.3.3
----End
Configuration Files
l
Issue 02 (2011-09-10)
452
3 MPLS TE Configuration
sysname LSRA
#
mpls lsr-id 1.1.1.1
mpls
mpls te
mpls te auto-frr
mpls rsvp-te
mpls te cspf
#
explicit-path master
next hop 2.1.1.2
next hop 3.1.1.2
#
interface GigabitEthernet1/0/0
ip address 10.1.1.2 255.255.255.0
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 10000
mpls te bandwidth bc0 10000 bc1 3000
mpls rsvp-te
#
interface GigabitEthernet2/0/0
ip address 2.1.1.1 255.255.255.0
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 10000
mpls te bandwidth bc0 10000 bc1 3000
mpls rsvp-te
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
interface Tunnel2/0/0
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 3.3.3.3
mpls te tunnel-id 200
mpls te record-route label
mpls te bandwidth ct0 400
mpls te path explicit-path master
mpls te priority 4 3
mpls te fast-reroute bandwidth
mpls te bypass-attributes bandwidth 200 priority 5 4
mpls te commit
#
ospf 1
opaque-capability enable
area 0.0.0.0
network 10.1.1.0 0.0.0.255
network 2.1.1.0 0.0.0.255
network 1.1.1.1 0.0.0.0
mpls-te enable
#
return
Issue 02 (2011-09-10)
453
3 MPLS TE Configuration
Issue 02 (2011-09-10)
454
3 MPLS TE Configuration
#
return
Networking Requirements
On the network shown in Figure 3-17, the primary tunnel is along the path LSR A -> LSR B > LSR C -> LSR D, and FRR is required on the link between LSR B and LSR C for protection.
A bypass tunnel is set up along the path LSR B -> LSR E -> LSR C. LSR B functions as the
PLR and LSR C functions as the MP.
The primary and bypass MPLS TE tunnels are set up by using explicit paths. RSVP-TE is used
as the signaling protocol.
The RSVP authentication needs to be configured on LSR B and LSR C. In this example, LSR
B and LSR C are configured as neighboring nodes by using their LSR IDs, and RSVP key
authentication is enabled to achieve higher reliability.
Issue 02 (2011-09-10)
455
3 MPLS TE Configuration
Figure 3-17 Networking diagram of the MPLS TE FRR-based RSVP key authentication
Loopback1
4.4.4.4/32
LSRD
GE1/0/0
4.1.1.2/24
Loopback1
2.2.2.2/32
Loopback1
1.1.1.1/32
Loopback1
3.3.3.3/32
GE1/0/0
4.1.1.1/24
LSRB
LSRA
GE2/0/0
GE2/0/0
GE1/0/0
GE1/0/0
3.1.1.1/24 3.1.1.2/24
2.1.1.1/24 2.1.1.2/24
POS3/0/0
3.2.1.1/24
Primary LSP
Bypass LSP
LSRC
POS3/0/0
3.3.1.2/24
POS2/0/0
3.3.1.1/24
POS1/0/0
3.2.1.2/24
LSRE
Loopback1
5.5.5.5/32
Configuration Roadmap
The configuration roadmap is as follows:
1.
2.
Configure RSVP key authentication on LSR B and LSR C of the tunnel, preventing forged
Resv messages from consuming network resources.
Data Preparation
To complete the configuration, you need the following data:
l
Procedure
Step 1 Configure MPLS TE FRR.
Configure the primary tunnel and bypass tunnel based on Example for Configuring MPLS TE
FRR and then bind the two tunnels.
Issue 02 (2011-09-10)
456
3 MPLS TE Configuration
Step 2 Configure RSVP key authentication on LSR B and LSR C to enhance security of packet
transmission. In addition, check whether the RSVP key authentication is successfully
configured, configure the RSVP-TE handshake function, and set a local password.
# Configure RSVP key authentication on LSR B.
[LSRB] mpls rsvp-te peer 3.3.3.3
[LSRB-mpls-rsvp-te-peer-3.3.3.3] mpls rsvp-te authentication plain huawei
[LSRB-mpls-rsvp-te-peer-3.3.3.3] mpls rsvp-te authentication handshake beijingHW
RSB CleanupTimeOutCounter: 0
RecPacketCounter: 216
RecCreatePathCounter: 57
RecRefreshPathCounter: 28
RecCreateResvCounter: 4
RecRefreshResvCounter: 49
RecResvConfCounter: 0
RecHelloCounter: 0
RecAckCounter: 0
RecPathErrCounter: 0
RecResvErrCounter: 0
RecPathTearCounter: 1
RecResvTearCounter: 1
RecSrefreshCounter: 0
RecAckMsgCounter: 0
RecChallengeMsgCounter: 1
RecResponseMsgCounter: 1
RecErrMsgCounter: 0
Bfd session count: 0
# Run the display interface tunnel 1/0/0 command on LSR A to view the status of the primary
tunnel. You can see that the tunnel interface is Up.
# Run the tracert lsp te tunnel 1/0/0 command on LSR A. You can view the path by which the
tunnel passes.
[LSRA] tracert lsp te tunnel 1/0/0
LSP Trace Route FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel1/0/0 , press CTRL_C to
break.
TTL
Replier
Time
Type
Downstream
Issue 02 (2011-09-10)
457
3 MPLS TE Configuration
2.1.1.2
3.2.1.2
3.3.1.2
4.1.1.2
1 ms
16 ms
1 ms
1 ms
Ingress
Transit
Transit
Transit
Egress
2.1.1.2/[13312 ]
3.2.1.2/[13312 13312 ]
3.3.1.2/[3 ]
4.1.1.2/[3 ]
The command output shows that traffic is switched to the bypass tunnel.
# Run the display mpls te tunnel name tunnel1/0/0 verbose command on LSR B. You can see
that the bypass tunnel is working.
[LSRB] display mpls te tunnel name tunnel1/0/0 verbose
No
: 1
Tunnel-Name
: Tunnel1/0/0
TunnelIndex
: 1
LSP Index
: 4098
Session ID
: 100
LSP ID
: 1
Lsr Role
: Transit
LSP Type
: Primary
Ingress LSR ID
: 1.1.1.1
Egress LSR ID
: 4.4.4.4
In-Interface
: GE1/0/0
Out-Interface
: GE2/0/0
Sign-Protocol
: RSVP TE
Resv Style
: SE
IncludeAnyAff
: 0x0
ExcludeAnyAff
: 0x0
IncludeAllAff
: 0x0
ER-Hop Table Index
: 3
AR-Hop Table Index: 12
C-Hop Table Index
: 50
PrevTunnelIndexInSession: NextTunnelIndexInSession: PSB Handle
: 66000
Created Time
: 2009/01/12 10:09:10
-------------------------------DS-TE Information
-------------------------------Bandwidth Reserved Flag : Unreserved
CT0 Bandwidth(Kbit/sec) : 50000
CT1 Bandwidth(Kbit/sec): 0
CT2 Bandwidth(Kbit/sec) : 0
CT3 Bandwidth(Kbit/sec): 0
CT4 Bandwidth(Kbit/sec) : 0
CT5 Bandwidth(Kbit/sec): 0
CT6 Bandwidth(Kbit/sec) : 0
CT7 Bandwidth(Kbit/sec): 0
Setup-Priority
: 7
Hold-Priority
: 7
-------------------------------FRR Information
-------------------------------Primary LSP Info
TE Attribute Flag
: 0x63
Protected Flag
: 0x1
Bypass In Use
: In Use
Bypass Tunnel Id
: 67141670
BypassTunnel
: Tunnel Index[Tunnel3/0/0], InnerLabel[1024]
Bypass Lsp ID
: 9
FrrNextHop
: 3.3.1.2
ReferAutoBypassHandle
: FrrPrevTunnelTableIndex : FrrNextTunnelTableIndex: Bypass Attribute(Not configured)
Setup Priority
: Hold Priority
: HopLimit
: Bandwidth
: IncludeAnyGroup
: ExcludeAnyGroup
: IncludeAllGroup
: Bypass Unbound Bandwidth Info(Kbit/sec)
CT0 Unbound Bandwidth
: CT1 Unbound Bandwidth: CT2 Unbound Bandwidth
: CT3 Unbound Bandwidth: CT4 Unbound Bandwidth
: CT5 Unbound Bandwidth: CT6 Unbound Bandwidth
: CT7 Unbound Bandwidth: -------------------------------BFD Information
-------------------------------NextSessionTunnelIndex : PrevSessionTunnelIndex: NextLspId
: PrevLspId
: -
# Run the display mpls rsvp-te peer command. You can see whether the bypass tunnel is
successfully set up.
[LSRB] display mpls rsvp-te peer
Remote Node id Neighbor
Issue 02 (2011-09-10)
458
3 MPLS TE Configuration
NbrSrcInstance: 0x0
RSB Count: 0
NbrSrcInstance: 0x0
RSB Count: 0
NbrSrcInstance: 0x0
RSB Count: 0
NbrSrcInstance: 0x0
RSB Count: 1
The command output shows that the number of RSBs on POS 1/0/0 of LSR B is not zero. This
indicates that RSVP key authentication is successfully configured on LSR B and its neighbor
LSR E, and the resources are successfully reserved.
----End
Configuration Files
l
Issue 02 (2011-09-10)
459
3 MPLS TE Configuration
mpls rsvp-te
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
isis enable 1
#
interface Tunnel1/0/0
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 4.4.4.4
mpls te record-route label
mpls te path explicit-path pri-path
mpls te tunnel-id 100
mpls te bandwidth ct0 50000
mpls te fast-reroute
mpls te commit
#
return
Issue 02 (2011-09-10)
460
3 MPLS TE Configuration
Issue 02 (2011-09-10)
461
3 MPLS TE Configuration
mpls te
mpls rsvp-te
#
isis 1
is-level level-2
cost-style wide
network-entity 00.0005.0000.0000.0004.00
traffic-eng level-2
#
interface GigabitEthernet1/0/0
ip address 4.1.1.2 255.255.255.0
isis enable 1
mpls
mpls te
mpls rsvp-te
#
interface LoopBack1
ip address 4.4.4.4 255.255.255.255
isis enable 1
#
return
Issue 02 (2011-09-10)
462
3 MPLS TE Configuration
Networking Requirements
As shown in Figure 3-18, the primary tunnel is along the path LSR A -> LSR B -> LSR C ->
LSR D, and the link between LSR B and LSR C requires FRR for protection. In addition, the
summary refresh (Srefresh) function needs to be configured on LSR B and LSR C.
A bypass tunnel is set up along the path LSR B -> LSR E -> LSR C. LSR B functions as the
PLR and LSR C functions as the MP.
The primary and bypass MPLS TE tunnels are set up by using explicit paths. RSVP-TE is used
as the signaling protocol.
The Srefresh function needs to be configured on LSR B and LSR C. In addition, RSVP key
authentication is configured in the MPLS view. This helps the Srefresh function to achieve higher
reliability.
Figure 3-18 Networking diagram of the MPLS TE FRR-based Srefresh function
Loopback1
4.4.4.4/32
LSRD
GE1/0/0
4.1.1.2/24
Loopback1
1.1.1.1/32
Loopback1
2.2.2.2/32
Loopback1
3.3.3.3/32
GE1/0/0
4.1.1.1/24
LSRB
LSRA
GE2/0/0
GE2/0/0
GE1/0/0
GE1/0/0
3.1.1.1/24 3.1.1.2/24
2.1.1.1/24 2.1.1.2/24
POS3/0/0
3.2.1.1/24
Primary LSP
Bypass LSP
POS1/0/0
3.2.1.2/24
LSRC
POS3/0/0
3.3.1.2/24
POS2/0/0
3.3.1.1/24
LSRE
Loopback1
5.5.5.5/32
Issue 02 (2011-09-10)
463
3 MPLS TE Configuration
Configuration Roadmap
The configuration roadmap is as follows:
1.
2.
Configure the Srefresh function on the PLR and MP along a tunnel to enhance transmission
reliability of RSVP messages and improve resource usage.
Data Preparation
To complete the configuration, you need the following data:
Data listed in "Data Preparation" of Example for Configuring MPLS TE FRR
Procedure
Step 1 Configure MPLS TE FRR.
You can configure the primary and bypass MPLS TE tunnels based on Example for
Configuring MPLS TE FRR, and then bind the two tunnels.
Step 2 Configure the Srefresh function on LSR B functioning as the PLR and LSR C functioning as
the MP.
# Configure the Srefresh function on LSR B.
[LSRB] mpls
[LSRB-mpls] mpls rsvp-te srefresh
[LSRB-mpls] quit
Issue 02 (2011-09-10)
RSB CleanupTimeOutCounter: 0
RecPacketCounter: 216
RecCreatePathCounter: 57
RecRefreshPathCounter: 28
RecCreateResvCounter: 4
RecRefreshResvCounter: 49
RecResvConfCounter: 0
RecHelloCounter: 0
RecAckCounter: 0
RecPathErrCounter: 0
RecResvErrCounter: 0
RecPathTearCounter: 1
RecResvTearCounter: 1
464
3 MPLS TE Configuration
SendSrefreshCounter: 1
SendAckMsgCounter: 6
SendChallengeMsgCounter: 0
SendResponseMsgCounter: 0
SendErrMsgCounter: 1
ResourceReqFaultCounter: 0
Bfd neighbor count: 1
RecSrefreshCounter: 6
RecAckMsgCounter: 16
RecChallengeMsgCounter: 0
RecResponseMsgCounter: 0
RecErrMsgCounter: 0
Bfd session count: 0
# Run the display interface tunnel 1/0/0 command on LSR A to view the status of the primary
tunnel. You can view that the tunnel interface is Up.
# Run the tracert lsp te tunnel 1/0/0 command on LSR A. You can view the path by which the
tunnel passes.
[LSRA] tracert lsp te tunnel 1/0/0
LSP Trace Route FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel1/0/0 , press CTRL_C to
break.
TTL
Replier
Time
Type
Downstream
0
Ingress
2.1.1.2/[13312 ]
1
2.1.1.2
1 ms
Transit
3.2.1.2/[13312 13312 ]
2
3.2.1.2
16 ms
Transit
3.3.1.2/[3 ]
3
3.3.1.2
1 ms
Transit
4.1.1.2/[3 ]
4
4.1.1.2
1 ms
Egress
# The command output shows that traffic is switched to the bypass tunnel.
# Run the display mpls te tunnel name tunnel1/0/0 verbose command on LSR B. You can
view that the bypass tunnel is working.
[LSRB] display mpls te tunnel name tunnel1/0/0 verbose
No
: 1
Tunnel-Name
: Tunnel1/0/0
TunnelIndex
: 1
LSP Index
: 4098
Session ID
: 100
LSP ID
: 1
Lsr Role
: Transit
LSP Type
: Primary
Ingress LSR ID
: 1.1.1.1
Egress LSR ID
: 4.4.4.4
In-Interface
: GE1/0/0
Out-Interface
: GE2/0/0
Sign-Protocol
: RSVP TE
Resv Style
: SE
IncludeAnyAff
: 0x0
ExcludeAnyAff
: 0x0
IncludeAllAff
: 0x0
ER-Hop Table Index
: 3
AR-Hop Table Index: 12
C-Hop Table Index
: 50
PrevTunnelIndexInSession: NextTunnelIndexInSession: PSB Handle
: 66000
Created Time
: 2009/01/12 10:09:10
-------------------------------DS-TE Information
-------------------------------Bandwidth Reserved Flag : Unreserved
CT0 Bandwidth(Kbit/sec) : 50000
CT1 Bandwidth(Kbit/sec): 0
CT2 Bandwidth(Kbit/sec) : 0
CT3 Bandwidth(Kbit/sec): 0
CT4 Bandwidth(Kbit/sec) : 0
CT5 Bandwidth(Kbit/sec): 0
CT6 Bandwidth(Kbit/sec) : 0
CT7 Bandwidth(Kbit/sec): 0
Setup-Priority
: 7
Hold-Priority
: 7
-------------------------------FRR Information
-------------------------------Primary LSP Info
TE Attribute Flag
: 0x63
Protected Flag
: 0x1
Bypass In Use
: In Use
Bypass Tunnel Id
: 67141670
BypassTunnel
: Tunnel Index[Tunnel3/0/0], InnerLabel[1024]
Issue 02 (2011-09-10)
465
3 MPLS TE Configuration
Bypass Lsp ID
: 9
FrrNextHop
: 3.3.1.2
ReferAutoBypassHandle
: FrrPrevTunnelTableIndex : FrrNextTunnelTableIndex: Bypass Attribute(Not configured)
Setup Priority
: Hold Priority
: HopLimit
: Bandwidth
: IncludeAnyGroup
: ExcludeAnyGroup
: IncludeAllGroup
: Bypass Unbound Bandwidth Info(Kbit/sec)
CT0 Unbound Bandwidth
: CT1 Unbound Bandwidth: CT2 Unbound Bandwidth
: CT3 Unbound Bandwidth: CT4 Unbound Bandwidth
: CT5 Unbound Bandwidth: CT6 Unbound Bandwidth
: CT7 Unbound Bandwidth: -------------------------------BFD Information
-------------------------------NextSessionTunnelIndex : PrevSessionTunnelIndex: NextLspId
: PrevLspId
: -
# Run the display mpls rsvp-te statistics global command. You can view the statistics about
the Srefresh function.
[LSRB]display mpls rsvp-te statistics global
LSR ID: 2.2.2.2
LSP Count: 2
PSB Count: 2
RSB Count: 2
RFSB Count: 1
Total Statistics Information:
PSB CleanupTimeOutCounter: 0
SendPacketCounter: 28
SendCreatePathCounter: 3
SendRefreshPathCounter: 9
SendCreateResvCounter: 3
SendRefreshResvCounter: 4
SendResvConfCounter: 0
SendHelloCounter: 0
SendAckCounter: 0
SendPathErrCounter: 1
SendResvErrCounter: 0
SendPathTearCounter: 0
SendResvTearCounter: 0
SendSrefreshCounter: 14
SendAckMsgCounter: 8
SendChallengeMsgCounter: 0
SendResponseMsgCounter: 0
SendErrMsgCounter: 0
ResourceReqFaultCounter: 0
Bfd neighbor count: 2
RSB CleanupTimeOutCounter: 0
RecPacketCounter: 61
RecCreatePathCounter: 18
RecRefreshPathCounter: 6
RecCreateResvCounter: 2
RecRefreshResvCounter: 10
RecResvConfCounter: 0
RecHelloCounter: 0
RecAckCounter: 0
RecPathErrCounter: 0
RecResvErrCounter: 0
RecPathTearCounter: 0
RecResvTearCounter: 0
RecSrefreshCounter: 8
RecAckMsgCounter: 18
RecChallengeMsgCounter: 0
RecResponseMsgCounter: 0
RecErrMsgCounter: 0
Bfd session count: 0
After the Srefresh function is configured on LSR B and LSR C globally, the Srefresh function
on LSR B and LSR C takes effect when the primary tunnel fails.
----End
Configuration Files
l
Issue 02 (2011-09-10)
466
3 MPLS TE Configuration
Issue 02 (2011-09-10)
467
3 MPLS TE Configuration
Issue 02 (2011-09-10)
468
3 MPLS TE Configuration
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
isis enable 1
#
return
Issue 02 (2011-09-10)
469
3 MPLS TE Configuration
interface LoopBack1
ip address 5.5.5.5 255.255.255.255
isis enable 1
#
return
Networking Requirements
Figure 3-19 shows the networking diagram of MPLS TE FRR. The primary tunnel is along PLR
LSR1 MP LSR3, and its bypass tunnel is along PLR LSR2 MP. After the interface
board where POS 1/0/0 of the PLR resides is removed, TE traffic of the primary tunnel needs
to switch to the bypass tunnel, and after the interface board is installed back, traffic switches
back to the primary tunnel.
Figure 3-19 Networking diagram for configuring MPLS TE FRR
Loopback 1
2.2.2.2/32
PO
3
0
S
/
0
.1. 2/0
1/0 /30
S
1
Loopback 1
Loopback 1
Loopback 1
.1/ /0
PO 1.1.2
30 PO 4.4.4.4/32
5.5.5.5/32
.
1.1.1.1/32 /0
LSR1
30 S1
/0 0 10
.
1
/
1
S
.1. 0/0
/3
POS3/0/0
2/3
PO 1.1.1
.
0
50.1.1.1/30
0
1
POS1/0/0
P
/0 MP 50.1.1.2/30 LSR3
PLR 2 OS
0
/
2 30
0.1 2/0
.1. /0
OS .1.2/
P
1/3
LSR2
.1
0 POS
/0
40
0
20
/
1
2 30
.1. /0/0
1.2
OS .1.1/
P
/30
.1
: primary LSP
40
: bypass LSP
Loopback 1
3.3.3.3/32
Configuration Roadmap
The configuration roadmap is as follows:
1.
Configure the tunnel interfaces of the primary and bypass tunnels on the master control
board.
2.
Specify the explicit paths of the primary tunnel and the bypass tunnel when configuring
MPLS TE FRR. The explicit paths of the primary tunnel and the bypass tunnel must pass
through different interface boards of the PLR and the primary tunnel cannot be on the board
to be removed; otherwise, board hot removal protection cannot be implemented.
Issue 02 (2011-09-10)
470
3 MPLS TE Configuration
Data Preparation
To complete the configuration, you need the following data:
l
Procedure
Step 1 Configure IP address on each interface.
The IP address and mask on each interface including the loopback interface are configured as
shown in Figure 3-19. The detailed configuration is not provided here.
Step 2 Configure OSPF on all LSRs to advertise the routes of each network segment and the host route
of each LSR ID.
Configure OSPF on all LSRs to advertise the host route of each LSR ID. The detailed
configuration is not provided here.
After the configuration, run the display ip routing-table command on each LSR. You can view
that the LSRs learn the host route of the LSR ID from each other.
Step 3 Configure the basic MPLS functions and enable MPLS TE and RSVP-TE.
# Configure a PLR.
[PLR] mpls lsr-id 1.1.1.1
[PLR] mpls
[PLR-mpls] mpls te
[PLR-mpls] mpls rsvp-te
[PLR-mpls] quit
[PLR] interface pos 1/0/0
[PLR-Pos1/0/0] mpls
[PLR-Pos1/0/0] mpls te
[PLR-Pos1/0/0] mpls rsvp-te
[PLR-Pos1/0/0] quit
[PLR] interface pos2/0/0
[PLR-Pos2/0/0] mpls
[PLR-Pos2/0/0] mpls te
[PLR-Pos2/0/0] mpls rsvp-te
[PLR-Pos2/0/0] quit
NOTE
The configurations on LSR1, LSR2, the MP, and LSR3 are similar to the configuration on the PLR, and
are not provided here.
Step 4 Configure OSPF TE on all LSRs and enable CSPF on the ingress of the primary tunnel.
# Configure OSPF TE.
[PLR] ospf
[PLR-ospf-1] opaque-capability enable
[PLR-ospf-1] area 0
[PLR-ospf-1-area-0.0.0.0] mpls-te enable
[PLR-ospf-1-area-0.0.0.0] quit
[PLR-ospf-1] quit
NOTE
The configurations on LSR1, LSR2, the MP, and LSR3 are similar to the configuration on a PLR, and are
not provided here.
Issue 02 (2011-09-10)
471
3 MPLS TE Configuration
Step 5 Configure the reservable bandwidth for the interfaces on each link.
Set the maximum reservable bandwidth of the link to 10 Mbit/s, the BC0 bandwidth to 10 Mbit/
s, and the BC1 bandwidth to 3 Mbit/s.
# Configure the PLR.
[PLR] interface pos
[PLR-Pos1/0/0] mpls
[PLR-Pos1/0/0] mpls
[PLR-Pos1/0/0] quit
[PLR] interface pos
[PLR-Pos2/0/0] mpls
[PLR-Pos2/0/0] mpls
[PLR-Pos2/0/0] quit
1/0/0
te bandwidth max-reservable-bandwidth 10000
te bandwidth bc0 10000 bc1 3000
2/0/0
te bandwidth max-reservable-bandwidth 10000
te bandwidth bc0 10000 bc1 3000
# Configure link bandwidth on all the outgoing interfaces of the link along the primary and
bypass tunnels. The configurations are not provided here.
Step 6 Configure the primary tunnel.
# Configure the explicit path for the primary tunnel on the PLR.
[PLR] explicit-path master
[PLR-explicit-path-master]
[PLR-explicit-path-master]
[PLR-explicit-path-master]
[PLR-explicit-path-master]
[PLR-explicit-path-master]
next
next
next
next
quit
hop
hop
hop
hop
10.1.1.2
30.1.1.2
50.1.1.2
5.5.5.5
# Run the display interface tunnel command on PLR. You can view the status of Tunnel 0/0/1
of the primary tunnel is Up.
[PLR] display interface tunnel 0/0/1
Tunnel0/0/1 current state : UP
Line protocol current state : UP
Last up time: 2009-03-29, 16:35:10
Description : Tunnel0/0/1 Interface, Route Port
...
Issue 02 (2011-09-10)
472
3 MPLS TE Configuration
# Run the display interface tunnel command on PLR. You can view the status of Tunnel 0/0/2
of the bypass tunnel is Up.
<PLR> display interface tunnel 0/0/2
Tunnel0/0/2 current state : UP
Line protocol current state : UP
Last up time: 2009-03-29, 16:43:34
Description : Tunnel0/0/2 Interface, Route Port
...
# After the interface board where the outgoing interface of the primary tunnel (POS 1/0/0) resides
is removed, run the display interface tunnel and display mpls te tunnel stale-interface
interface-index verbose commands. You can view that the tunnel interface of the primary tunnel
remains Up.
# Run the display mpls te tunnel stale-interface command on the PLR. You can view that the
outgoing interface of the primary tunnel is in the Stale state.
<PLR> display mpls stale-interface
Stale-interface
Status
TE Attri
LSP Count CRLSP Count Effective MTU
0x018000106
Up
Dis
0
1
<PLR> display mpls te tunnel stale-interface 18000106 verbose
No
: 1
Tunnel-Name
: Tunnel0/0/1
TunnelIndex
: 0
LSP Index
: 2048
Session ID
: 100
LSP ID
: 1
Lsr Role
: Ingress
LSP Type
: Ingress LSR ID
: 1.1.1.1
Egress LSR ID
: 5.5.5.5
In-Interface
: Out-Interface
: 0x800086
Sign-Protocol
: RSVP TE
Resv Style
: SE
IncludeAnyAff
: 0x0
ExcludeAnyAff
: 0x0
IncludeAllAff
: 0x0
LspConstraint
: -
Issue 02 (2011-09-10)
473
3 MPLS TE Configuration
# Run the display mpls te tunnel path command on the PLR. You can view the path information
of the primary tunnel.
<PLR> display mpls te tunnel path Tunnel0/0/1
Tunnel Interface Name : Tunnel0/0/1
Lsp ID : 1.1.1.1 :100 :1
Hop Information
Hop 0
20.1.1.1 Local-Protection in use
Hop 1
20.1.1.2 Label 65536
Hop 2
3.3.3.3 Label 65536
Hop 3
40.1.1.1
Hop 4
40.1.1.2 Label 131072
Hop 5
4.4.4.4 Label 131072
Hop 6
50.1.1.1
Hop 7
50.1.1.2 Label 3
Hop 8
5.5.5.5 Label 3
# Run the tracert lsp te tunnel command. You can view TE traffic is transmitted through the
bypass tunnel.
<PLR> tracert lsp te tunnel 0/0/1
LSP Trace Route FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel0/0/1 , press CTRL_C to
break.
TTL
Replier
Time
Type
Downstream
0
Ingress
20.1.1.2/[65536 15360 ]
1
20.1.1.2
50 ms
Transit
40.1.1.2/[131073 ]
2
40.1.1.2
50 ms
Transit
30.1.1.1/[3 ]
3
30.1.1.1
4 ms
Transit
Issue 02 (2011-09-10)
474
3 MPLS TE Configuration
30.1.1.2
11.1.1.1
15 ms
6 ms
Transit
Egress
50.1.1.2/[3 ]
# After the interface board where the outgoing interface of the primary tunnel resides is replugged in, run the tracert lsp te tunnel command. You can view that traffic switches back to
the primary tunnel.
<PLR> tracert lsp te tunnel 0/0/1
LSP Trace Route FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel6/0/0 , press CTRL_C to
break.
TTL
Replier
Time
Type
Downstream
0
Ingress
10.1.1.2/[65537 ]
1
10.1.1.2
40 ms
Transit
30.1.1.2/[131074 ]
2
30.1.1.2
50 ms
Transit
50.1.1.2/[3 ]
3
5.5.5.5
60 ms
Egress
----End
Configuration Files
l
Issue 02 (2011-09-10)
475
3 MPLS TE Configuration
Issue 02 (2011-09-10)
476
3 MPLS TE Configuration
mpls rsvp-te
#
interface Pos1/0/0
link-protocol ppp
ip address 20.1.1.2 255.255.255.252
mpls
mpls te
mpls rsvp-te
#
interface Pos2/0/0
link-protocol ppp
ip address 40.1.1.1 255.255.255.252
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 10000
mpls te bandwidth bc0 10000 bc1 3000
mpls rsvp-te
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
ospf 1
opaque-capability enable
area 0.0.0.0
network 20.1.1.0 0.0.0.3
network 30.1.1.0 0.0.0.3
network 3.3.3.3 0.0.0.0
mpls-te enable
#
return
Issue 02 (2011-09-10)
477
3 MPLS TE Configuration
40.1.1.0 0.0.0.3
50.1.1.0 0.0.0.3
4.4.4.4 0.0.0.0
enable
#
return
Networking Requirements
Figure 3-20 shows an MPLS VPN. A TE tunnel from PE1 functioning as the ingress to PE2
functioning as the egress, CR-LSP hot backup, and best-effort LSPs need to be configured. The
following LSPs need to be established:
l
If the primary CR-LSP fails, traffic switches to the backup CR-LSP. After the primary CR-LSP
recovers from the fault, traffic switches back to the primary CR-LSP in 15 seconds. If both the
primary CR-LSP and backup CR-LSP fail, traffic switches to the best-effort LSP.
Issue 02 (2011-09-10)
478
3 MPLS TE Configuration
Loopback1
1.1.1.1/32
GE1/0/0
P1
10.1.1.1/30
GE3/0/0
GE2/0/0
10.2.1.1/30
10.4.1.2/30
Loopback1
2.2.2.2/32
GE1/0/0
P2
10.1.1.2/30
GE3/0/0
GE2/0/0
10.3.1.2/30
10.5.1.1/30
GE2/0/0
10.5.1.2 /30
GE2/0/0
10.4.1.1/30
GE1/0/0
10.3.1.1/30
PE1
GE1/0/0
10.2.1.2/30
Loopback1
4.4.4.4/32
PE2
Loopback1
3.3.3.3/32
: Primary path
: Backup path
: Best-effort path
Configuration Roadmap
The configuration roadmap is as follows:
1.
2.
3.
Specify explicit paths for the primary and backup CR-LSPs on PE1.
4.
Create the tunnel interface with PE2 as the egress on PE1 and specify the explicit path.
Enable hot standby. Enable system to try to create a best-effort LSP to protect traffic if both
the primary and backup CR-LSPs fail. Set the switching delay time to 15 seconds.
Data Preparation
To complete the configuration, you need the following data:
l
MPLS LSR ID
Issue 02 (2011-09-10)
479
3 MPLS TE Configuration
Procedure
Step 1 Configure an IP address for each interface.
Configure an IP address for each interface, create loopback interfaces on LSRs, and then
configure the IP addresses of loopback interfaces as MPLS LSR IDs as shown in Figure 3-20.
For detailed configuration, see configuration files in this example.
Step 2 Configure an IGP.
Configure OSPF or IS-IS on each LSR to enable communication between LSRs. In this example,
IS-IS is configured. For detailed configuration, see configuration files in this example.
Step 3 Configure basic MPLS functions.
On each LSR, configure an LSR ID and enable MPLS in the system view and in the interface
view. For detailed configuration, see configuration files in this example.
Step 4 Configure basic MPLS TE functions.
Enable MPLS-TE and MPLS RSVP-TE in the MPLS view and the interface view on each LSR.
Set the maximum reservable bandwidth of links to 100 Mbit/s and the bandwidth of BC0 to 100
Mbit/s. For detailed configurations, see configuration files in this example.
Step 5 Configure IS-IS TE and CSPF.
Configure IS-IS TE on each LSR and CSPF on PE1. For detailed configuration, see configuration
files in this example.
Step 6 Configure the explicit paths for the primary and backup CR-LSPs respectively.
# Configure the explicit path for the primary CR-LSP on PE1.
<PE1> system-view
[PE1] explicit-path main
[PE1-explicit-path-main]
[PE1-explicit-path-main]
[PE1-explicit-path-main]
[PE1-explicit-path-main]
480
3 MPLS TE Configuration
# Configure hot standby on the tunnel interface, configure the switch delay time to 15 seconds,
specify the explicit path, and configure the best-effort LSP.
[PE1-Tunnel1/0/0]
[PE1-Tunnel1/0/0]
[PE1-Tunnel1/0/0]
[PE1-Tunnel1/0/0]
[PE1-Tunnel1/0/0]
mpls
mpls
mpls
mpls
quit
te
te
te
te
Run the display mpls te tunnel-interface tunnel 1/0/0 command on PE1. You can see that the
primary and backup CR-LSPs have been established.
[PE1] display mpls te tunnel-interface tunnel 1/0/0
================================================================
Tunnel1/0/0
================================================================
Tunnel State Desc
: UP
Active LSP
: Primary LSP
Session ID
: 100
Ingress LSR ID
: 4.4.4.4
Egress LSR ID: 3.3.3.3
Admin State
: UP
Oper State
: UP
Primary LSP State
: UP
Main LSP State
: READY
LSP ID : 1
Hot-Standby LSP State : UP
Main LSP State
: READY
LSP ID : 32770
# Run the ping lsp te command to check the connection of the backup CR-LSP.
[PE1] ping lsp te tunnel 1/0/0 hot-standby
LSP PING FEC: TE TUNNEL IPV4 SESSION QUERY
CTRL_C to break
Reply from 3.3.3.3: bytes=100 Sequence=1
Reply from 3.3.3.3: bytes=100 Sequence=2
Reply from 3.3.3.3: bytes=100 Sequence=3
Reply from 3.3.3.3: bytes=100 Sequence=4
Reply from 3.3.3.3: bytes=100 Sequence=5
Tunnel1/0/0 : 100
time
time
time
time
time
=
=
=
=
=
380 ms
130 ms
70 ms
120 ms
120 ms
--- FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel1/0/0 ping statistics --5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 70/164/380 ms
# Run the tracert lsp te command to trace the path of the backup CR-LSP.
[PE1] tracert lsp te tunnel 1/0/0 hot-standby
LSP Trace Route FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel1/0/0 , press CTRL_C to
break.
TTL
Replier
Time
Type
Downstream
0
Ingress
10.3.1.2/[13313 ]
Issue 02 (2011-09-10)
481
3 MPLS TE Configuration
10.3.1.2
3.3.3.3
90 ms
130 ms
Transit
Egress
10.5.1.2/[3 ]
After attaching the cable into GE 2/0/0, you can see that traffic switches back to the primary
CR-LSP in 15 seconds.
After you remove the cable from GE 2/0/0 on PE1 or P1 and the cable from GE 2/0/0 on PE2
or P2, the tunnel interface goes Down and then Up. This means that the best-effort has been set
up successfully, allowing traffic to switch to the best-effort LSP.
[PE1] display mpls te tunnel-interface tunnel 1/0/0
================================================================
Tunnel1/0/0
================================================================
Tunnel State Desc
: UP
Active LSP
: Best-Effort LSP
Session ID
: 100
Ingress LSR ID
: 4.4.4.4
Egress LSR ID: 3.3.3.3
Admin State
: UP
Oper State
: UP
Primary LSP State
: DOWN
Main LSP State
: SETTING UP
Hot-Standby LSP State : DOWN
Main LSP State
: SETTING UP
Best-Effort LSP State : UP
Main LSP State
: READY
LSP ID : 32773
[PE1] display mpls te tunnel path
Tunnel Interface Name : Tunnel1/0/0
Lsp ID : 4.4.4.4 :100 :32776
Hop Information
Hop 0
10.3.1.1
Hop 1
10.3.1.2
Hop 2
2.2.2.2
Hop 3
10.1.1.2
Hop 4
10.1.1.1
Hop 5
1.1.1.1
Hop 6
10.2.1.1
Hop 7
10.2.1.2
Hop 8
3.3.3.3
----End
Configuration Files
l
Issue 02 (2011-09-10)
482
3 MPLS TE Configuration
Configuration file of P1
#
sysname P1
#
mpls lsr-id 1.1.1.1
mpls
mpls te
mpls rsvp-te
#
isis 1
cost-style wide
network-entity 10.0000.0000.0001.00
Issue 02 (2011-09-10)
483
3 MPLS TE Configuration
traffic-eng level-1-2
#
interface GigabitEthernet1/0/0
ip address 10.1.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls rsvp-te
#
interface GigabitEthernet2/0/0
ip address 10.4.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls rsvp-te
#
interface GigabitEthernet3/0/0
ip address 10.2.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000 bc1 50000
mpls rsvp-te
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
isis enable 1
#
return
Configuration file of P2
#
sysname P2
#
mpls lsr-id 2.2.2.2
mpls
mpls te
mpls rsvp-te
#
isis 1
cost-style wide
network-entity 10.0000.0000.0002.00
traffic-eng level-1-2
#
interface GigabitEthernet1/0/0
ip address 10.1.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000 bc1 50000
mpls rsvp-te
#
interface GigabitEthernet2/0/0
ip address 10.5.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000 bc1 50000
mpls rsvp-te
#
interface GigabitEthernet3/0/0
ip address 10.3.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls rsvp-te
#
Issue 02 (2011-09-10)
484
3 MPLS TE Configuration
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
isis enable 1
#
return
Networking Requirements
On a network as shown in Figure 3-21, a primary CR-LSP needs to be set up from LSR A to
LSR D, and a hot-standby CR-LSP needs to be set up for the primary CR-LSP.
A maximum of three attribute templates can be created for a backup CR-LSP. In the event that
a CR-LSP established using any of the three templates is stable, you can lock a CR-LSP attribute
template, thus avoiding unnecessary traffic switchover and reducing consumption of system
resources.
When an attribute template for hot-standby CR-LSPs is locked, the following effects can be
achieved:
l
Issue 02 (2011-09-10)
485
3 MPLS TE Configuration
When the attribute template of hot-standby CR-LSPs is unlocked, the system uses a higherpriority attribute template to create a new hot-standby CR-LSP according to the makebefore-break mechanism.
LSRC
PO
/0
10. S2/0
1/0 24
S
1.4 /0
PO .1.2/
.1/2 PO
1
0
.
/
S
41
1.1.1.1/32 S1/0 4 10
0.1 1/0/0 4.4.4.4/32
2
/
.
4.2
PO .1.1
/24
1
POS2/0/0 LSRE POS2/0/0
.
0
1
10.1.3.1/24
10.1.6.2/24
POS1/0/0
POS2/0/0
PO
/0
10.1.3.2/24
10.1.6.1/24
LSRA 10 S3/
3/0 /24 LSRD
S
.1.
0/0
2.1
PO .5.2
/24 PO
.1
0
0/ 4 10
10 S1/
/
2
.1. 0/0
S
/2
2.2
PO .5.1
/24
.1
10
LSRB
Configuration Roadmap
The configuration roadmap is as follows:
1.
Configure IP addresses and a routing protocol for interfaces to ensure the connectivity on
the network layer.
2.
Enable MPLS, MPLS TE, RSVP-TE, and CSPF in the system view and the interface view.
3.
4.
Use CR-LSP attribute templates to establish CR-LSPs on a tunnel interface, and lock a CRLSP attribute template of hot-standby CR-LSPs.
Data Preparation
To complete the configuration, you need the following data:
l
IP address of the tunnel interface, destination address of the tunnel, and tunnel ID
Procedure
Step 1 Configure IP addresses and an IGP (OSPF, in this example) for interfaces to ensure connectivity
at the network layer.
The configuration details are not mentioned here.
Step 2 Configure the MPLS LSR ID for each device, and enable MPLS and MPLS TE in the system
view and in each interface view of each device.
# Configure LSR A.
Issue 02 (2011-09-10)
486
3 MPLS TE Configuration
<LSRA> system-view
[LSRA] mpls lsr-id 1.1.1.1
[LSRA] mpls
[LSRA-mpls] mpls te
[LSRA-mpls] mpls rsvp-te
[LSRA-mpls] mpls te cspf
[LSRA-mpls] quit
[LSRA] interface pos1/0/0
[LSRA-Pos1/0/0] mpls
[LSRA-Pos1/0/0] mpls te
[LSRA-Pos1/0/0] mpls rsvp-te
[LSRA-Pos1/0/0] quit
[LSRA] interface pos2/0/0
[LSRA-Pos2/0/0] mpls
[LSRA-Pos2/0/0] mpls te
[LSRA-Pos2/0/0] mpls rsvp-te
[LSRA-Pos2/0/0] quit
[LSRA] interface pos3/0/0
[LSRA-Pos3/0/0] mpls
[LSRA-Pos3/0/0] mpls te
[LSRA-Pos3/0/0] mpls rsvp-te
[LSRA-Pos3/0/0] quit
NOTE
The configurations of LSR B, LSR C, LSR D, and LSR E are similar to those of LSR A, and are not
mentioned here.
# On LSR A, configure the explicit path named down_path as LSR A LSR B LSR D.
[LSRA] explicit-path down_path
[LSRA-explicit-path-down_path] next hop 10.1.2.2
[LSRA-explicit-path-down_path] next hop 10.1.5.2
[LSRA-explicit-path-down_path] quit
# On LSR A, configure the explicit path named middle_path as LSR A LSR E LSR D.
[LSRA] explicit-path middle_path
[LSRA-explicit-path-middle_path] next hop 10.1.3.2
[LSRA-explicit-path-middle_path] next hop 10.1.6.2
[LSRA-explicit-path-middle_path] quit
487
3 MPLS TE Configuration
The priorities of the CR-LSP attribute templates configured on the same tunnel interface must be the same.
Step 4 Use a CR-LSP attribute template to set up a CR-LSP with LSR A being the ingress and LSR D
being the egress.
# To trigger LSR A to use a lower-priority attribute template to set up a hot-standby CR-LSP,
run the shutdown command to shut down the explicit path named down_path.
[LSRA] interface POS3/0/0
[LSRA-Pos3/0/0] shutdown
[LSRA-Pos3/0/0] quit
# Set up a CR-LSP from LSR A to LSR D, and lock an attribute template for hot-standby CRLSPs.
[LSRA] interface tunnel1/0/0
[LSRA-Tunnel1/0/0] tunnel-protocol mpls te
[LSRA-Tunnel1/0/0] destination 4.4.4.4
[LSRA-Tunnel1/0/0] mpls te tunnel-id 100
[LSRA-Tunnel1/0/0] mpls te primary-lsp-constraint lsp-attribute lsp_attribute_1
[LSRA-Tunnel1/0/0] mpls te hotstandby-lsp-constraint 1 lsp-attribute
lsp_attribute_3
[LSRA-Tunnel1/0/0] mpls te hotstandby-lsp-constraint 2 lsp-attribute
lsp_attribute_2
[LSRA-Tunnel1/0/0] mpls te backup hotstandby-lsp-constraint lock
[LSRA-Tunnel1/0/0] mpls te commit
[LSRA-Tunnel1/0/0] quit
# On LSR A, run the undo shutdown command on POS 3/0/0 to reenable the explicit path
named down_path and make the attribute template named lsp_attribute_3 effective.
[LSRA] interface pos3/0/0
[LSRA-Pos3/0/0] undo shutdown
[LSRA-Pos3/0/0] quit
# After the traffic switchover, run the tracert lsp te tunnel command on LSR A. You can view
that the hot-standby CR-LSP is set up by using the explicit path configured in the attribute
template named lsp_attribute_2.
<LSRA> tracert lsp te tunnel
LSP Trace Route FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel1/0/0 , press CTRL_C to
break.
TTL
Replier
Time
Type
Downstream
0
Ingress
10.1.3.2/[1024 ]
1
10.1.3.2
120 ms Transit
10.1.6.2/[3 ]
2
4.4.4.4
100 ms Egress
# Run the display mpls te tunnel verbose command on LSR A. You can view that the hotstandby CR-LSP is set up by using the attribute template named lsp_attribute_2 that is not
upgraded.
Issue 02 (2011-09-10)
488
3 MPLS TE Configuration
# Run the undo mpls te backup hotstandby-lsp-constraint lock command on LSR A to unlock
the attribute template of hot-standby CR-LSPs.
[LSRA] interface tunnel 1/0/0
[LSRA-Tunnel1/0/0] undo mpls te backup hotstandby-lsp-constraint lock
[LSRA-Tunnel1/0/0] mpls te commit
[LSRA-Tunnel1/0/0] quit
# Run the tracert lsp te tunnel1/0/0 command on LSR A. You can view that the hot-standby
CR-LSP is set up by using the explicit path configured in the attribute template named
lsp_attribute_3.
<LSRA> tracert lsp te tunnel1/0/0
Issue 02 (2011-09-10)
489
3 MPLS TE Configuration
LSP Trace Route FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel1/0/0 , press CTRL_C t
o break.
TTL
Replier
Time
Type
Downstream
0
Ingress
10.1.2.2/[1024 ]
1
10.1.2.2
90 ms
Transit
10.1.5.2/[3 ]
2
4.4.4.4
100 ms Egress
# Run the display mpls te tunnel verbose command on LSR A. You can view that the hotstandby CR-LSP is set up by using the attribute template named lsp_attribute_1 that is not
upgraded. This indicates that the system automatically upgrades the attribute template after the
attribute template of hot-standby CR-LSPs is unlocked.
<LSRA> display mpls te tunnel verbose
No
: 1
Tunnel-Name
: Tunnel1/0/0
TunnelIndex
: 0
LSP Index
: 2048
Session ID
: 100
LSP ID
: 32929
Lsr Role
: Ingress
Lsp Type
: Hot-Standby
Ingress LSR ID
: 1.1.1.1
Egress LSR ID
: 4.4.4.4
In-Interface
: Out-Interface
: Pos1/0/2
Sign-Protocol
: RSVP TE
Resv Style
: SE
IncludeAnyAff
: 0x0
ExcludeAnyAff
: 0x0
IncludeAllAff
: 0x0
LspConstraint
: 1
ER-Hop Table Index
: 1
AR-Hop Table Index: 0
C-Hop Table Index
: 0
PrevTunnelIndexInSession: NextTunnelIndexInSession: PSB Handle
: 1182
Created Time
: 2010/02/21 18:14:23
-------------------------------DS-TE Information
-------------------------------Bandwidth Reserved Flag : Unreserved
CT0 Bandwidth(Kbit/sec) : 0
CT1 Bandwidth(Kbit/sec): 0
CT2 Bandwidth(Kbit/sec) : 0
CT3 Bandwidth(Kbit/sec): 0
CT4 Bandwidth(Kbit/sec) : 0
CT5 Bandwidth(Kbit/sec): 0
CT6 Bandwidth(Kbit/sec) : 0
CT7 Bandwidth(Kbit/sec): 0
Setup-Priority
: 5
Hold-Priority
: 5
-------------------------------FRR Information
-------------------------------Primary LSP Info
TE Attribute Flag
: 0x3
Protected Flag
: 0x0
Bypass In Use
: Not Exists
Bypass Tunnel Id
: BypassTunnel
: Bypass Lsp ID
: FrrNextHop
: ReferAutoBypassHandle
: FrrPrevTunnelTableIndex : FrrNextTunnelTableIndex: Bypass Attribute(Not configured)
Setup Priority
: Hold Priority
: HopLimit
: Bandwidth
: IncludeAnyGroup
: ExcludeAnyGroup
: IncludeAllGroup
: Bypass Unbound Bandwidth Info(Kbit/sec)
CT0 Unbound Bandwidth
: CT1 Unbound Bandwidth: CT2 Unbound Bandwidth
: CT3 Unbound Bandwidth: CT4 Unbound Bandwidth
: CT5 Unbound Bandwidth: CT6 Unbound Bandwidth
: CT7 Unbound Bandwidth: -------------------------------BFD Information
-------------------------------NextSessionTunnelIndex : PrevSessionTunnelIndex: NextLspId
: PrevLspId
: -
----End
Issue 02 (2011-09-10)
490
3 MPLS TE Configuration
Configuration Files
l
Issue 02 (2011-09-10)
491
3 MPLS TE Configuration
Issue 02 (2011-09-10)
492
3 MPLS TE Configuration
mpls-te enable
#
return
Issue 02 (2011-09-10)
493
3 MPLS TE Configuration
Networking Requirements
Figure 3-22 is a networking diagram of CR-LSP hot standby. A TE tunnel is established from
PE1 to PE2. The tunnel is enabled with hot standby and configured with the best-effort path. In
this manner, traffic is switched to the backup CR-LSP when the primary CR-LSP fails. If the
backup CR-LSP also fails, this triggers the establishment of a best-effort path, and then the traffic
switches to the best-effort path.
It is required that the dynamic bandwidth function for a hot-standby CR-LSP be configured on
the tunnel interface. This can achieve the following effects:
l
When the primary CR-LSP works properly, the hot-standby CR-LSP does not occupy
bandwidth, saving bandwidth resources.
If the primary tunnel fails, traffic switches to the hot-standby CR-LSP and then forwarded
in a best-effort manner. The system then sets up a new CR-LSP with user-requested
bandwidth according to the make-before-break mechanism. After the new hot-standby CRLSP is set up, the system switches traffic to this CR-LSP and deletes the hot-standby CRLSP with bandwidth at 0 bit/s.
Issue 02 (2011-09-10)
494
3 MPLS TE Configuration
Figure 3-22 Networking diagram of the dynamic bandwidth function of a hot-standby CR-LSP
Loopback1
1.1.1.1/32
GE1/0/0
P1
10.1.1.1/30
GE3/0/0
GE2/0/0
10.2.1.1/30
10.4.1.2/30
Loopback1
2.2.2.2/32
GE1/0/0
P2
10.1.1.2/30
GE3/0/0
10.3.1.2/30
GE2/0/0
10.5.1.1/30
GE2/0/0
10.5.1.2 /30
GE2/0/0
10.4.1.1/30
GE1/0/0
10.3.1.1/30
PE1
Loopback1
4.4.4.4/32
GE1/0/0
10.2.1.2/30
PE2
Loopback1
3.3.3.3/32
: Primary path
: Backup path
: Best-effort path
Configuration Roadmap
The configuration roadmap is as follows:
1.
Configure CR-LSP hot standby according to Example for Configuring CR-LSP Hot
Standby.
2.
Data Preparation
To complete the configuration, you need the following data:
Data in "Data Preparation" of Example for Configuring CR-LSP Hot Standby
Procedure
Step 1 Configure CR-LSP hot standby.
Configure a primary CR-LSP, a backup CR-LSP, and a best-effort path according to Example
for Configuring CR-LSP Hot Standby.
Step 2 Configure the dynamic bandwidth function for a hot-standby CR-LSP.
# Configure PE1.
[PE1] interface tunnel 1/0/0
Issue 02 (2011-09-10)
495
3 MPLS TE Configuration
[PE1-Tunnel1/0/0]
[PE1-Tunnel1/0/0]
[PE1-Tunnel1/0/0]
[PE1-Tunnel1/0/0]
tunnel-protocol mpls te
mpls te backup hot-standby dynamic-bandwidth
mpls te commit
quit
Issue 02 (2011-09-10)
:
:
2
Tunnel1/0/0
496
3 MPLS TE Configuration
TunnelIndex
: 1
LSP Index
: 2049
Session ID
: 100
LSP ID
: 32769
Lsr Role
: Ingress
Lsp Type
: Hot-Standby
Ingress LSR ID
: 4.4.4.4
Egress LSR ID
: 3.3.3.3
In-Interface
: Out-Interface
: GE1/0/1
Sign-Protocol
: RSVP TE
Resv Style
: SE
IncludeAnyAff
: 0x0
ExcludeAnyAff
: 0x0
IncludeAllAff
: 0x0
LspConstraint
: ER-Hop Table Index
: 1
AR-Hop Table Index: 1
C-Hop Table Index
: 1
PrevTunnelIndexInSession: NextTunnelIndexInSession: 0
PSB Handle
: 1025
Created Time
: 2010/02/22 11:29:15
-------------------------------DS-TE Information
-------------------------------Bandwidth Reserved Flag : Unreserved
CT0 Bandwidth(Kbit/sec) : 0
CT1 Bandwidth(Kbit/sec): 0
CT2 Bandwidth(Kbit/sec) : 0
CT3 Bandwidth(Kbit/sec): 0
CT4 Bandwidth(Kbit/sec) : 0
CT5 Bandwidth(Kbit/sec): 0
CT6 Bandwidth(Kbit/sec) : 0
CT7 Bandwidth(Kbit/sec): 0
Setup-Priority
: 7
Hold-Priority
: 7
-------------------------------FRR Information
-------------------------------Primary LSP Info
TE Attribute Flag
: 0x3
Protected Flag
: 0x0
Bypass In Use
: Not Exists
Bypass Tunnel Id
: BypassTunnel
: Bypass Lsp ID
: FrrNextHop
: ReferAutoBypassHandle
: FrrPrevTunnelTableIndex : FrrNextTunnelTableIndex: Bypass Attribute(Not configured)
Setup Priority
: Hold Priority
: HopLimit
: Bandwidth
: IncludeAnyGroup
: ExcludeAnyGroup
: IncludeAllGroup
: Bypass Unbound Bandwidth Info(Kbit/sec)
CT0 Unbound Bandwidth
: CT1 Unbound Bandwidth: CT2 Unbound Bandwidth
: CT3 Unbound Bandwidth: CT4 Unbound Bandwidth
: CT5 Unbound Bandwidth: CT6 Unbound Bandwidth
: CT7 Unbound Bandwidth: -------------------------------BFD Information
-------------------------------NextSessionTunnelIndex : PrevSessionTunnelIndex: NextLspId
: PrevLspId
: [PE1] display mpls te link-administration bandwidth-allocation
Link ID: GigabitEthernet1/0/0
Bandwidth Constraint Model
: Russian Dolls Model (RDM)
Maximum Link Reservable Bandwidth(Kbits/sec): 0
Reservable Bandwidth BC0(Kbits/sec)
: 0
Reservable Bandwidth BC1(Kbits/sec)
: 0
Downstream Bandwidth (Kbits/sec)
: 0
IPUpdown Link Status
: UP
PhysicalUpdown Link Status
: UP
---------------------------------------------------------------------TE-CLASS CT
PRIORITY
BW RESERVED
BW AVAILABLE
DOWNSTREAM
(Kbit/sec)
(Kbit/sec) RSVPLSPNODE COUNT
---------------------------------------------------------------------0
0
0
0
0
0
1
0
1
0
0
0
2
0
2
0
0
0
3
0
3
0
0
0
4
0
4
0
0
0
Issue 02 (2011-09-10)
497
3 MPLS TE Configuration
5
0
5
0
0
0
6
0
6
0
0
0
7
0
7
0
0
0
8
1
0
0
0
0
9
1
1
0
0
0
10
1
2
0
0
0
11
1
3
0
0
0
12
1
4
0
0
0
13
1
5
0
0
0
14
1
6
0
0
0
15
1
7
0
0
0
---------------------------------------------------------------------Link ID: GigabitEthernet2/0/0
Bandwidth Constraint Model
: Russian Dolls Model (RDM)
Maximum Link Reservable Bandwidth(Kbits/sec): 100000
Reservable Bandwidth BC0(Kbits/sec)
: 100000
Reservable Bandwidth BC1(Kbits/sec)
: 50000
Downstream Bandwidth (Kbits/sec)
: 10000
IPUpdown Link Status
: UP
PhysicalUpdown Link Status
: UP
---------------------------------------------------------------------TE-CLASS CT
PRIORITY
BW RESERVED
BW AVAILABLE
DOWNSTREAM
(Kbit/sec)
(Kbit/sec) RSVPLSPNODE COUNT
---------------------------------------------------------------------0
0
0
0
100000
0
1
0
1
0
100000
0
2
0
2
0
100000
0
3
0
3
0
100000
0
4
0
4
0
100000
0
5
0
5
0
100000
0
6
0
6
0
100000
0
7
0
7
10000
90000
1
8
1
0
0
50000
0
9
1
1
0
50000
0
10
1
2
0
50000
0
11
1
3
0
50000
0
12
1
4
0
50000
0
13
1
5
0
50000
0
14
1
6
0
50000
0
15
1
7
0
50000
0
----------------------------------------------------------------------
# Run the shutdown command on PE1 to shut down the primary CR-LSP.
[PE1] interface gigabitethernet2/0/0
[PE1-GigabitEthernet1/0/0] shutdown
[PE1-GigabitEthernet1/0/0] quit
# Run the display mpls te tunnel-interface command on PE1. You can view that the hot-standby
CR-LSP goes Up and is being reestablished after the primary CR-LSP fails.
[PE1-GigabitEthernet1/0/0] display mpls te tunnel-interface
================================================================
Tunnel1/0/0
================================================================
Tunnel State Desc
: UP
Active LSP
: Hot-Standby LSP
Session ID
: 100
Ingress LSR ID
: 4.4.4.4
Egress LSR ID: 3.3.3.3
Admin State
: UP
Oper State
: UP
Primary LSP State
: DOWN
Main LSP State
: SETTING UP
Hot-Standby LSP State : UP
Main LSP State
: READY
LSP ID : 32769
Modify LSP State
: SETTING UP
Issue 02 (2011-09-10)
498
3 MPLS TE Configuration
# After the successful reestablishment, run the display mpls te tunnel verbose command and
the display mpls te link-administration bandwidth-allocation command on PE1. You can
view that the hot-standby CR-LSP occupies the bandwidth.
[PE1] display mpls te tunnel verbose
No
: 1
Tunnel-Name
: Tunnel1/0/0
TunnelIndex
: 0
LSP Index
: 2048
Session ID
: 100
LSP ID
: 32773
Lsr Role
: Ingress
Lsp Type
: Hot-Standby
Ingress LSR ID
: 4.4.4.4
Egress LSR ID
: 3.3.3.3
In-Interface
: Out-Interface
: GE1/0/1
Sign-Protocol
: RSVP TE
Resv Style
: SE
IncludeAnyAff
: 0x0
ExcludeAnyAff
: 0x0
IncludeAllAff
: 0x0
LspConstraint
: ER-Hop Table Index
: 1
AR-Hop Table Index: 0
C-Hop Table Index
: 0
PrevTunnelIndexInSession: NextTunnelIndexInSession: PSB Handle
: 1026
Created Time
: 2010/02/22 14:22:36
-------------------------------DS-TE Information
-------------------------------Bandwidth Reserved Flag : Reserved
CT0 Bandwidth(Kbit/sec) : 10000
CT1 Bandwidth(Kbit/sec): 0
CT2 Bandwidth(Kbit/sec) : 0
CT3 Bandwidth(Kbit/sec): 0
CT4 Bandwidth(Kbit/sec) : 0
CT5 Bandwidth(Kbit/sec): 0
CT6 Bandwidth(Kbit/sec) : 0
CT7 Bandwidth(Kbit/sec): 0
Setup-Priority
: 7
Hold-Priority
: 7
-------------------------------FRR Information
-------------------------------Primary LSP Info
TE Attribute Flag
: 0x3
Protected Flag
: 0x0
Bypass In Use
: Not Exists
Bypass Tunnel Id
: BypassTunnel
: Bypass Lsp ID
: FrrNextHop
: ReferAutoBypassHandle
: FrrPrevTunnelTableIndex : FrrNextTunnelTableIndex: Bypass Attribute(Not configured)
Setup Priority
: Hold Priority
: HopLimit
: Bandwidth
: IncludeAnyGroup
: ExcludeAnyGroup
: IncludeAllGroup
: Bypass Unbound Bandwidth Info(Kbit/sec)
CT0 Unbound Bandwidth
: CT1 Unbound Bandwidth: CT2 Unbound Bandwidth
: CT3 Unbound Bandwidth: CT4 Unbound Bandwidth
: CT5 Unbound Bandwidth: CT6 Unbound Bandwidth
: CT7 Unbound Bandwidth: -------------------------------BFD Information
-------------------------------NextSessionTunnelIndex : PrevSessionTunnelIndex: NextLspId
: PrevLspId
: [PE1] display mpls te link-administration bandwidth-allocation
Link ID: GigabitEthernet1/0/0
Bandwidth Constraint Model
: Russian Dolls Model (RDM)
Maximum Link Reservable Bandwidth(Kbits/sec): 100000
Reservable Bandwidth BC0(Kbits/sec)
: 100000
Reservable Bandwidth BC1(Kbits/sec)
: 50000
Downstream Bandwidth (Kbits/sec)
: 10000
IPUpdown Link Status
: UP
PhysicalUpdown Link Status
: UP
---------------------------------------------------------------------TE-CLASS CT
PRIORITY
BW RESERVED
BW AVAILABLE
DOWNSTREAM
Issue 02 (2011-09-10)
499
3 MPLS TE Configuration
(Kbit/sec)
(Kbit/sec) RSVPLSPNODE COUNT
---------------------------------------------------------------------0
0
0
0
100000
0
1
0
1
0
100000
0
2
0
2
0
100000
0
3
0
3
0
100000
0
4
0
4
0
100000
0
5
0
5
0
100000
0
6
0
6
0
100000
0
7
0
7
10000
90000
1
8
1
0
0
50000
0
9
1
1
0
50000
0
10
1
2
0
50000
0
11
1
3
0
50000
0
12
1
4
0
50000
0
13
1
5
0
50000
0
14
1
6
0
50000
0
15
1
7
0
50000
0
---------------------------------------------------------------------Link ID: GigabitEthernet2/0/0
Bandwidth Constraint Model
: Russian Dolls Model (RDM)
Maximum Link Reservable Bandwidth(Kbits/sec): 100000
Reservable Bandwidth BC0(Kbits/sec)
: 100000
Reservable Bandwidth BC1(Kbits/sec)
: 50000
Downstream Bandwidth (Kbits/sec)
: 0
IPUpdown Link Status
: DOWN
PhysicalUpdown Link Status
: DOWN
---------------------------------------------------------------------TE-CLASS CT
PRIORITY
BW RESERVED
BW AVAILABLE
DOWNSTREAM
(Kbit/sec)
(Kbit/sec) RSVPLSPNODE COUNT
---------------------------------------------------------------------0
0
0
0
100000
0
1
0
1
0
100000
0
2
0
2
0
100000
0
3
0
3
0
100000
0
4
0
4
0
100000
0
5
0
5
0
100000
0
6
0
6
0
100000
0
7
0
7
0
100000
0
8
1
0
0
50000
0
9
1
1
0
50000
0
10
1
2
0
50000
0
11
1
3
0
50000
0
12
1
4
0
50000
0
13
1
5
0
50000
0
14
1
6
0
50000
0
15
1
7
0
50000
0
----------------------------------------------------------------------
----End
Configuration Files
l
Issue 02 (2011-09-10)
500
3 MPLS TE Configuration
Configuration file of P1
#
sysname P1
#
mpls lsr-id 1.1.1.1
mpls
mpls te
mpls rsvp-te
#
isis 1
cost-style wide
network-entity 10.0000.0000.0001.00
traffic-eng level-1-2
#
interface GigabitEthernet1/0/0
ip address 10.1.1.1 255.255.255.252
isis enable 1
mpls
Issue 02 (2011-09-10)
501
3 MPLS TE Configuration
mpls te
mpls rsvp-te
#
interface GigabitEthernet2/0/0
ip address 10.4.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls rsvp-te
#
interface GigabitEthernet3/0/0
ip address 10.2.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000 bc1 50000
mpls rsvp-te
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
isis enable 1
#
return
Configuration file of P2
#
sysname P2
#
mpls lsr-id 2.2.2.2
mpls
mpls te
mpls rsvp-te
#
isis 1
cost-style wide
network-entity 10.0000.0000.0002.00
traffic-eng level-1-2
#
interface GigabitEthernet1/0/0
ip address 10.1.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000 bc1 50000
mpls rsvp-te
#
interface GigabitEthernet2/0/0
ip address 10.5.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000 bc1 50000
mpls rsvp-te
#
interface GigabitEthernet3/0/0
ip address 10.3.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls rsvp-te
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
isis enable 1
#
return
Issue 02 (2011-09-10)
502
3 MPLS TE Configuration
Networking Requirements
On the network shown in Figure 3-23, a primary tunnel is set up by using the explicit path LSR
A --> LSR B --> LSR C. A TE FRR bypass tunnel is set up on the transit LSR B along the path
LSR B --> LSR E --> LSR C; an ordinary CR-LSP is set up on the ingress LSR A along the path
LSR A --> LSR C.
After the link between LSR B and LSR C is faulty, the system starts the TE FRR bypass tunnel
(the primary CR-LSP is in FRR-in-use state) and tries to restore the primary CR-LSP. At the
same time, the system tries to set up the backup CR-LSP.
Issue 02 (2011-09-10)
503
3 MPLS TE Configuration
Figure 3-23 Networking diagram of configuring synchronization of the bypass tunnel and the
backup CR-LSP
Loopback1
1.1.1.1/32
LSRA
GE1/0/0
10.1.1.2/24
Loopback1
2.2.2.2/32
Loopback1
3.3.3.3/32
GE3/0/0
GE2/0/0
3.1.1.1/24 3.1.1.2/24
GE3/0/0
2.1.1.2/24
GE2/0/0
LSRB
2.1.1.1/24 GE1/0/0
Loopback1
3.2.1.1/24
4.4.4.4/32
GE3/0/0
3.2.1.2/24
LSRC
GE1/0/0
10.1.1.1/24
GE2/0/0
4.1.1.2/24
GE2/0/0
4.1.1.1/24
LSRE
Configuration Roadmap
The configuration roadmap is as follows:
1.
2.
On the transit LSR B, set up a TE FRR bypass tunnel along the path LSR B --> LSR E -> LSR C to protect the link between LSR B and LSR C.
3.
On the ingress LSR A, set up an ordinary CR-LSP along the path LSR A --> LSR C.
4.
Configure synchronization of the bypass tunnel and the backup CR-LSP in the tunnel
interface view.
Data Preparation
To complete the configuration, you need the following data:
l
Name and IP address of the primary tunnel interface, destination address, tunnel ID, tunnel
signaling protocol (RSVP-TE), and tunnel bandwidth
Procedure
Step 1 Configure the IP address for each interface.
Configure the IP address and mask for each interface including each Loopback interface as
shown in Figure 3-23. Configuration details are not provided here.
Step 2 Enable an IGP.
Issue 02 (2011-09-10)
504
3 MPLS TE Configuration
Enable OSPF or IS-IS on each LSR to ensure connectivity between devices. The example in this
document uses OSPF as IGP. For configuration details, see the configuration files in this
example.
Step 3 Configure basic MPLS functions.
On each LSR, configure an LSR ID and enable MPLS in the system and interface views. For
configuration details, see the configuration files in this example.
Step 4 Configure basic MPLS TE functions.
On each LSR, enable MPLS-TE and MPLS RSVP-TE in the MPLS view and interface views
of the link. Set the maximum reservable bandwidth of the link to 100 Mbit/s and the bandwidth
of BC0 to 100 Mbit/s. For configuration details, see the configuration files in this example.
Step 5 Enable OSPF TE and configure the CSPF.
Enable OSPF TE on each LSR and configure the CSPF on LSR A and LSR B. For configuration
details, see Configuring the RSVP-TE Tunnel.
Step 6 Configure the explicit paths of the primary and backup CR-LSPs.
# Configure the explicit path of the primary CR-LSP on LSR A.
[LSRA] explicit-path master
[LSRA-explicit-path-master] next hop 2.1.1.2
[LSRA-explicit-path-master] next hop 3.1.1.2
# Configure LSR B.
[LSRB] interface gigabitethernet2/0/0
[LSRB-GigabitEthernet2/0/0] mpls te auto-frr link
[LSRB-GigabitEthernet2/0/0] quit
After the configurations, run the display mpls te tunnel path lsp-id 1.1.1.1 1 1 command on
LSR A, and you can see that the bypass tunnel is set up successfully.
Issue 02 (2011-09-10)
505
3 MPLS TE Configuration
Step 10 Configure synchronization of the bypass tunnel and the backup CR-LSP on the ingress LSR A
of the primary CR-LSP.
# Configure LSR A.
[LSRA] interface tunnel2/0/0
[LSRA-Tunnel2/0/0] mpls te backup frr-in-use
[LSRA-Tunnel2/0/0] mpls te commit
[LSRA-Tunnel2/0/0] quit
Run the display mpls te tunnel-interface tunnel2/0/0 command on the ingress LSR A, and you
can view information about the primary CR-LSP.
[LSRA] display mpls te tunnel-interface tunnel2/0/0
================================================================
Tunnel2/0/0
================================================================
Tunnel State Desc
: UP
Active LSP
: Primary LSP
Session ID
: 1
Ingress LSR ID
: 1.1.1.1
Egress LSR ID: 3.3.3.3
Admin State
: UP
Oper State
: UP
Primary LSP State
: UP
Main LSP State
: READY
LSP ID : 2
Run the display mpls te tunnel-interface command on LSR A, and you can see that the tunnel
status is Up. The primary tunnel is in FRR-in-use state; the ordinary CR-LSP is being set up;
the primary CR-LSP is being restored.
================================================================
Tunnel2/0/0
================================================================
Tunnel State Desc
: UP
Issue 02 (2011-09-10)
506
3 MPLS TE Configuration
Active LSP
Session ID
Ingress LSR ID
Admin State
Primary LSP State
Main LSP State
Modify LSP State
Ordinary LSP State
Main LSP State
:
:
:
:
Primary LSP
1
1.1.1.1
UP
: UP
: READY
: SETTING UP
: DOWN
: SETTING UP
3.3.3.3
UP
: 5
: 6
When the primary CR-LSP is faulty (the primary CR-LSP is in FRR-in-use state), the system
starts the TE FRR bypass tunnel and tries to restore the primary CR-LSP. At the same time, the
system tries to set up a backup CR-LSP.
----End
Configuration Files
l
Issue 02 (2011-09-10)
507
3 MPLS TE Configuration
mpls te commit
#
ospf 1
opaque-capability enable
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 10.1.1.0 0.0.0.255
network 2.1.1.0 0.0.0.255
mpls-te enable
#
return
Issue 02 (2011-09-10)
508
3 MPLS TE Configuration
mpls te
mpls rsvp-te
mpls te cspf
#
interface GigabitEthernet2/0/0
undo shutdown
ip address 4.1.1.2 255.255.255.0
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 1000
mpls te bandwidth bc0 1000
mpls rsvp-te
#
interface GigabitEthernet1/0/0
undo shutdown
ip address 10.1.1.1 255.255.255.0
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 1000
mpls te bandwidth bc0 1000
mpls rsvp-te
#
interface GigabitEthernet3/0/0
undo shutdown
ip address 3.1.1.2 255.255.255.0
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 1000
mpls te bandwidth bc0 1000
mpls rsvp-te
#
interface LoopBack0
ip address 3.3.3.3 255.255.255.255
#
ospf 1
opaque-capability enable
area 0.0.0.0
network 3.3.3.3 0.0.0.0
network 3.1.1.0 0.0.0.255
network 4.1.1.0 0.0.0.255
network 10.1.1.0 0.0.0.255
mpls-te enable
#
return
Issue 02 (2011-09-10)
509
3 MPLS TE Configuration
Networking Requirements
On the network shown in Figure 3-24, LSR A, LSR B, and LSR C are equipped with dual main
control boards. Three LSRs learn routes from each other through the IS-IS protocol, and then
use the RSVP protocol to set up a TE tunnel from LSR A to LSR C.
RSVP GR is required to ensure that MPLS forwarding is not interrupted when the master/slave
switchover of main control boards occurs on LSR A, LSR B, or LSR C.
Figure 3-24 Example for Configuring RSVP-TE GR
Loopback1
Loopback1
Loopback1
2.2.2.2/32
3.3.3.3/32
1.1.1.1/32
GE2/0/0
GE1/0/0
GE2/0/0
GE1/0/0
20.1.1.1/24 20.1.1.2/24
10.1.1.1/24 10.1.1.2/24
LSRB
LSRA
LSRC
Configuration Roadmap
The configuration roadmap is as follows:
1.
Configure IP addresses for interfaces on each LSR and loopback addresses that function
as the LSR IDs.
2.
3.
4.
5.
Enable MPLS, MPLS TE, and MPLS RSVP-TE on each interface, and configure bandwidth
attributes of the MPLS TE link.
6.
Enable MPLS CSPF on the ingress node. Create the tunnel interface at the ingress node.
Specify the tunnel IP address, tunnel protocol, destination address, tunnel ID, and signaling
protocol.
Issue 02 (2011-09-10)
510
3 MPLS TE Configuration
7.
8.
Data Preparation
To complete the configuration, you need the following data:
l
IS-IS network entity and IS-IS level which each node belongs to
Tunnel interface number of the Ingress node, tunnel ID, and tunnel bandwidth
Procedure
Step 1 Configure IP addresses for interfaces on each LSR. Details for the configuration are not provided
here.
Step 2 Configure basic IS-IS functions.
# Configure LSR A.
[LSRA] isis 1
[LSRA-isis-1] network-entity 00.0005.0000.0000.0001.00
[LSRA-isis-1] is-level level-2
[LSRA-isis-1] quit
[LSRA] interface gigabitethernet 1/0/0
[LSRA-GigabitEthernet1/0/0] isis enable 1
[LSRA-GigabitEthernet1/0/0] quit
[LSRA] interface loopback 1
[LSRA-LoopBack1] isis enable 1
[LSRA-LoopBack1] quit
# Configure LSR B.
[LSRB] isis 1
[LSRB-isis-1] network-entity 00.0005.0000.0000.0002.00
[LSRB-isis-1] is-level level-2
[LSRB-isis-1] quit
[LSRB] interface gigabitethernet 1/0/0
[LSRB-GigabitEthernet1/0/0] isis enable 1
[LSRB-GigabitEthernet1/0/0] quit
[LSRB] interface gigabitethernet 2/0/0
[LSRB-GigabitEthernet2/0/0] isis enable 1
[LSRB-GigabitEthernet2/0/0] quit
[LSRB] interface loopback 1
[LSRB-LoopBack1] isis enable 1
[LSRB-LoopBack1] quit
# Configure LSR C.
[LSRC] isis 1
[LSRC-isis-1] network-entity 00.0005.0000.0000.0003.00
[LSRC-isis-1] is-level level-2
[LSRC-isis-1] quit
[LSRC] interface gigabitethernet 2/0/0
[LSRC-GigabitEthernet2/0/0] isis enable 1
[LSRC-GigabitEthernet2/0/0] quit
[LSRC] interface loopback 1
[LSRC-LoopBack1] isis enable 1
[LSRC-LoopBack1] quit
Issue 02 (2011-09-10)
511
3 MPLS TE Configuration
After the configuration, run the display ip routing-table command on each LSR, and you can
see that LSRs have learned routes from each other.
Step 3 Configure basic MPLS capability and enable MPLS TE, RSVP-TE, and CSPF. Configure
maximum bandwidth and maximum reservable bandwidth of interfaces.
# Configure LSR A.
[LSRA] mpls lsr-id 1.1.1.1
[LSRA] mpls
[LSRA-mpls] mpls te
[LSRA-mpls] mpls rsvp-te
[LSRA-mpls] mpls te cspf
[LSRA-mpls] quit
[LSRA] interface gigabitethernet
[LSRA-GigabitEthernet1/0/0] mpls
[LSRA-GigabitEthernet1/0/0] mpls
[LSRA-GigabitEthernet1/0/0] mpls
[LSRA-GigabitEthernet1/0/0] mpls
[LSRA-GigabitEthernet1/0/0] mpls
[LSRA-GigabitEthernet1/0/0] quit
1/0/0
te
rsvp-te
te bandwidth max-reservable-bandwidth 100000
te bandwidth bc0 100000
# Configure LSR B.
[LSRB] mpls lsr-id 2.2.2.2
[LSRB] mpls
[LSRB-mpls] mpls te
[LSRB-mpls] mpls rsvp-te
[LSRB-mpls] quit
[LSRB] interface gigabitethernet
[LSRB-GigabitEthernet1/0/0] mpls
[LSRB-GigabitEthernet1/0/0] mpls
[LSRB-GigabitEthernet1/0/0] mpls
[LSRB-GigabitEthernet1/0/0] quit
[LSRB] interface gigabitethernet
[LSRB-GigabitEthernet2/0/0] mpls
[LSRB-GigabitEthernet2/0/0] mpls
[LSRB-GigabitEthernet2/0/0] mpls
[LSRB-GigabitEthernet2/0/0] mpls
[LSRB-GigabitEthernet2/0/0] mpls
[LSRB-GigabitEthernet2/0/0] quit
1/0/0
te
rsvp-te
2/0/0
te
rsvp-te
te bandwidth max-reservable-bandwidth 100000
te bandwidth bc0 100000
# Configure LSR C.
[LSRC] mpls lsr-id 3.3.3.3
[LSRC] mpls
[LSRC-mpls] mpls te
[LSRC-mpls] mpls rsvp-te
[LSRC-mpls] quit
[LSRC] interface gigabitethernet 2/0/0
[LSRC-GigabitEthernet2/0/0] mpls
[LSRC-GigabitEthernet2/0/0] mpls te
[LSRC-GigabitEthernet2/0/0] mpls rsvp-te
[LSRC-GigabitEthernet2/0/0] quit
cost-style wide
is-name LSRA
traffic-eng level-2
graceful-restart
quit
# Configure LSR B.
[LSRB] isis 1
Issue 02 (2011-09-10)
512
3 MPLS TE Configuration
cost-style wide
is-name LSRB
traffic-eng level-2
graceful-restart
quit
# Configure LSR C.
[LSRC] isis 1
[LSRC-isis-1]
[LSRC-isis-1]
[LSRC-isis-1]
[LSRC-isis-1]
[LSRC-isis-1]
cost-style wide
is-name LSRC
traffic-eng level-2
graceful-restart
quit
After the configuration, run the display interface tunnel command on LSR A, and you can see
that the interface status of the MPLS TE tunnel is Up.
[LSRA] display interface tunnel
Tunnel1/0/0 current state : UP
Line protocol current state : UP
Last up time: 2007-10-29, 16:35:10
Description : Tunnel1/0/0 Interface
...
# Configure LSR B.
[LSRB] mpls
[LSRB-mpls] mpls rsvp-te hello
[LSRB-mpls] mpls rsvp-te hello full-gr
[LSRB-mpls] quit
[LSRB] interface gigabitethernet 1/0/0
[LSRB-GigabitEthernet1/0/0] mpls rsvp-te hello
[LSRB] interface gigabitethernet 2/0/0
[LSRB-GigabitEthernet2/0/0] mpls rsvp-te hello
# Configure LSR C.
[LSRC] mpls
[LSRC-mpls] mpls rsvp-te hello
[LSRC-mpls] mpls rsvp-te hello full-gr
[LSRC-mpls] quit
[LSRC] interface gigabitethernet 2/0/0
[LSRC-GigabitEthernet2/0/0] mpls rsvp-te hello
Issue 02 (2011-09-10)
513
3 MPLS TE Configuration
Run the display mpls rsvp-te graceful-restart peer command on LSR B, and you can view
the GR status of the neighboring LSR.
[LSRB] display mpls rsvp-te graceful-restart peer
Neighbor on Interface GigabitEthernet1/0/0
Neighbor Addr: 10.1.1.1
SrcInstance: 47860
NbrSrcInstance: 49409
Neighbor Capability:
Can Do Self GR
Can Support GR
GR Status:
Normal
Restart Time: 90060 Milli Second
Recovery Time: 0 Milli Second
Stored GR message number: 0
If the master/slave switchover is performed, you can see that during the graceful-restart Tunnel
1/0/0 keeps up.
Run the display this interface command on LSR A, and you can view that the value of Tunnel
up/down statistics is 0, indicating that the tunnel has never flapped.
[LSRA] display this interface
Tunnel1/0/0 current state : UP
Line protocol current state : UP
Last line protocol up time : 2010-07-13 16:10:09
Description: Tunnel1/0/0 Interface
Route Port,The Maximum Transmit Unit is 1500
Internet protocol processing : disabled
Encapsulation is TUNNEL, loopback not set
Tunnel destination 3.3.3.3
Tunnel up/down statistics 0
Tunnel protocol/transport MPLS/MPLS, ILM is available,
...
# Run the slave switchover command on LSR B to forcibly perform the master/slave switchover
of main control boards.
[LSRB] slave switchover enable
[LSRB] slave switchover
Caution!!! Confirm switch slave to master[Y/N] ?
[LSRB] y
Run the display this interface command on LSR A again, and you can view that the value of
Tunnel up/down statistics is still 0, indicating that the tunnel did not flap after the master/slave
switchover of main control boards on LSR B. This means that RSVP GR has been configured
successfully.
[LSRA] display this interface
Issue 02 (2011-09-10)
514
3 MPLS TE Configuration
----End
Configuration Files
l
Issue 02 (2011-09-10)
515
3 MPLS TE Configuration
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls rsvp-te hello full-gr
#
isis 1
graceful-restart
is-level level-2
cost-style wide
is-name LSRB
network-entity 00.0005.0000.0000.0002.00
traffic-eng level-2
#
interface GigabitEthernet1/0/0
ip address 10.1.1.2 255.255.255.0
isis enable 1
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
#
interface GigabitEthernet2/0/0
ip address 20.1.1.1 255.255.255.0
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
mpls rsvp-te
mpls rsvp-te hello
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
isis enable 1
#
return
Issue 02 (2011-09-10)
516
3 MPLS TE Configuration
return
Networking Requirements
Figure 3-25 is a networking diagram of CR-LSP hot standby. A TE tunnel with PE1 as ingress
and PE2 as egress is established on PE1. The tunnel is enabled with hot standby and configured
with the best-effort LSP. If the primary CR-LSP fails, traffic can be switched to the backup CRLSP. After the primary CR-LSP recovers, traffic can be switched back to the primary CR-LSP
in 15 seconds. If both the primary and the backup CR-LSPs fail, traffic can be switched to the
best-effort LSP.
Two static BFD sessions are required to detect the primary and backup CR-LSPs. After the
configuration, the following objects should be achieved:
l
If the primary CR-LSP fails, traffic can be switched to the backup CR-LSP at milliseconds
level.
If the backup CR-SLP fails within 15 seconds after the primary CR-LSP recovers, traffic
is switched back to the primary CR-LSP.
Loopback1
1.1.1.1/32
GE1/0/0
P1
10.1.1.1/30
GE3/0/0
GE2/0/0
10.2.1.1/30
10.4.1.2/30
Loopback1
2.2.2.2/32
GE1/0/0
P2
10.1.1.2/30
GE3/0/0
10.3.1.2/30
GE2/0/0
10.5.1.2 /30
GE2/0/0
10.4.1.1/30
PE1
GE1/0/0
10.3.1.1/30
Loopback1
4.4.4.4/32
Issue 02 (2011-09-10)
GE2/0/0
10.5.1.1/30
GE1/0/0
10.2.1.2/30
PE2
Loopback1
3.3.3.3/32
: Primary path
: Backup path
: Best-effort path
517
3 MPLS TE Configuration
Configuration Roadmap
The configuration roadmap is as follows:
1.
Configure CR-LSP hot standby based on Example for Configuring CR-LSP Hot.
2.
On PE1, create two BFD sessions and bind the two sessions to the primary and backup CRLSPs respectively; on PE2, create two BFD sessions and bind the two sessions to the IP
link (PE2 --> PE1).
Data Preparation
To complete the configuration, you need the following data:
l
For other data, see Example for Configuring CR-LSP Hot Standby
Procedure
Step 1 Configure CR-LSP hot standby.
Configure the primary CR-LSP, backup CR-LSP, and best-effort LSP based on Example for
Configuring CR-LSP Hot Standby.
Step 2 Configuring BFD for CR-LSP.
# Create BFD sessions on PE1 and PE2 to detect the primary and backup CR-LSPs respectively.
Bind the BFD session on PE1 to the primary CR-LSP and the backup CR-LSP respectively; bind
the BFD session on PE2 to the IP link. Set the minimum intervals at at which BFD packets are
sent and received to 100 milliseconds and the local BFD detection multiplier to 3.
# Configure PE1.
[PE1] bfd
[PE1-bfd] quit
[PE1] bfd mainlsptope2 bind mpls-te interface tunnel1/0/0 te-lsp
[PE1-bfd-lsp-session-mainlsptope2] discriminator local 413
[PE1-bfd-lsp-session-mainlsptope2] discriminator remote 314
[PE1-bfd-lsp-session-mainlsptope2] min-tx-interval 100
[PE1-bfd-lsp-session-mainlsptope2] min-rx-interval 100
[PE1-bfd-lsp-session-mainlsptope2] detect-multiplier 3
[PE1-bfd-lsp-session-mainlsptope2] process-pst
[PE1-bfd-lsp-session-mainlsptope2] commit
[PE1-bfd-lsp-session-mainlsptope2] quit
[PE1] bfd backuplsptope2 bind mpls-te interface tunnel1/0/0 te-lsp backup
[PE1-bfd-lsp-session-backuplsptope2] discriminator local 423
[PE1-bfd-lsp-session-backuplsptope2] discriminator remote 324
[PE1-bfd-lsp-session-backuplsptope2] min-tx-interval 100
[PE1-bfd-lsp-session-backuplsptope2] min-rx-interval 100
[PE1-bfd-lsp-session-backuplsptope2] detect-multiplier 3
[PE1-bfd-lsp-session-backuplsptope2] process-pst
[PE1-bfd-lsp-session-backuplsptope2] commit
[PE1-bfd-lsp-session-backuplsptope2] quit
# Configure PE2.
[PE2] bfd
[PE2-bfd] quit
[PE2] bfd mainlsptope2 bind peer-ip 4.4.4.4
[PE2-bfd-lsp-session-mainlsptope2] discriminator local 314
Issue 02 (2011-09-10)
518
3 MPLS TE Configuration
# Run the display bfd session discriminator local-discriminator-value command on PE1 and
PE2. The command output shows that the status of BFD sessions is Up.
Take the command output on PE1 as an example:
[PE1] display bfd session discriminator 413
-------------------------------------------------------------------------------Local Remote PeerIpAddr
InterfaceName
State
Type
-------------------------------------------------------------------------------413
314
3.3.3.3
Tunnel1/0/0
Up
S_TE_LSP
-------------------------------------------------------------------------------[PE1] display bfd session discriminator 423
-------------------------------------------------------------------------------Local Remote PeerIpAddr
InterfaceName
State
Type
-------------------------------------------------------------------------------423
324
3.3.3.3
Tunnel1/0/0
Up
S_TE_LSP
--------------------------------------------------------------------------------
Configuration Files
l
Issue 02 (2011-09-10)
519
3 MPLS TE Configuration
Configuration file of P1
#
sysname P1
#
mpls lsr-id 1.1.1.1
mpls
mpls te
mpls rsvp-te
#
isis 1
Issue 02 (2011-09-10)
520
3 MPLS TE Configuration
cost-style wide
network-entity 10.0000.0000.0001.00
traffic-eng level-1-2
#
interface GigabitEthernet1/0/0
ip address 10.1.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls rsvp-te
#
interface GigabitEthernet2/0/0
ip address 10.4.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls rsvp-te
#
interface GigabitEthernet3/0/0
ip address 10.2.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
mpls rsvp-te
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
isis enable 1
#
return
Configuration file of P2
#
sysname P2
#
mpls lsr-id 2.2.2.2
mpls
mpls te
mpls rsvp-te
#
isis 1
cost-style wide
network-entity 10.0000.0000.0002.00
traffic-eng level-1-2
#
interface GigabitEthernet1/0/0
ip address 10.1.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
mpls rsvp-te
#
interface GigabitEthernet2/0/0
ip address 10.5.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
mpls rsvp-te
#
interface GigabitEthernet3/0/0
ip address 10.3.1.2 255.255.255.252
isis enable 1
mpls
mpls te
Issue 02 (2011-09-10)
521
3 MPLS TE Configuration
mpls rsvp-te
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
isis enable 1
#
return
Issue 02 (2011-09-10)
522
3 MPLS TE Configuration
Networking Requirements
Figure 3-26 shows an MPLS network where a switch (a Layer 2 device) exists between PE1
and PE2. PE1 is enabled with VPN FRR and configured with an MPLS TE tunnel. The primary
path of VPN FRR is PE1 Switch PE2; the backup path of VPN FRR is PE1 PE3. In
normal situations, VPN traffic is transmitted over the primary path. If the primary path fails,
VPN traffic switches to the backup path. BFD for TE is required to detect the TE tunnel over
the primary path and enable VPN to rapidly detect tunnel faults. Thus, traffic can rapidly switch
between the primary path and backup path in the case of faults, and fault recovery is shortened.
Figure 3-26 Networking diagram of static BFD for TE
Loopback1
2.2.2.2/32
0/0
S1/ /30
O
P
.1
.1.1
0
1
PE1
CE1
0/0
S1/ 30
O
P
/
.1.2
10.1
el
tunn
y
r
a
ond
Sec
PE3
CE2
Prim
a
ry tun
GE2
/0
nel
10.2 /0
PE2
.1.1/2
Loopback1
4
G
1.1.1.1/32
Switch 10 E2/0/0
.2.1.
2/24
Loopback1
3.3.3.3/32
NOTE
For simplicity, IP addresses of interfaces connecting PEs to CEs are not shown in Figure 3-26.
Configuration Roadmap
The configuration roadmap is as follows:
1.
Configure basic MPLS functions, and establish bi-directional TE tunnels between PE1 and
PE2, and between PE1 and PE3.
2.
3.
4.
Configure a BFD session on PE1 to detect the TE tunnel over the primary path.
5.
Configure a BFD session on each of PE2 and PE3 and specify the TE tunnel as the BFD
backward channel.
Data Preparation
To complete the configuration, you need the following data:
l
Issue 02 (2011-09-10)
523
3 MPLS TE Configuration
MPLS LSR ID
Tunnel interface number, bandwidth for the tunnel, and explicit paths
Data required for configuring VPN FRR, such as IP prefix name and routing policy name
Procedure
Step 1 Configure an IP address for each interface.
Configure an IP address for each interface as shown in Figure 3-26, create loopback interfaces
on LSRs, and configure IP addresses of the loopback interfaces as MPLS LSR IDs, . For
configuration details, see the configuration file of this example.
Step 2 Configure the switch.
Configure the switch so that PE1 and PE2 can communicate with each other. Details for this
configuration procedure are not provided here.
Step 3 Configure an IGP.
Configure OSPF or IS-IS on each LSR so that PE1 and PE2, and PE1 and PE3 can communicate
with each other. Examples in this document use OSPF. For configuration details, see the
configuration file of this example.
Step 4 Configure basic MPLS functions.
Configure the LSR ID and enable MPLS in the system view on each LSR, and enable MPLS in
the interface view. For configuration details, see the configuration file of this example.
Step 5 Configure basic MPLS TE functions.
Enable MPLS-TE and MPLS RSVP-TE in the MPLS and interface views on each LSR. Set the
maximum reservable bandwidth for the MPLS TE on outbound interfaces of links along the
tunnel to 100 Mbit/s and the BC bandwidth to 100 Mbit/s. For configuration details, see the
configuration file of this example.
Step 6 Configure OSPF TE and CSPF.
Configure OSPF TE on each LSR and CSPF on PE1. For configuration details, see the
configuration file of this example.
Step 7 Configure the tunnel interface.
# Specify explicit paths on PE1, PE2, and PE3. Two explicit paths are required on PE1.
# Configure PE1.
<PE1> system-view
[PE1] explicit-path tope2
[PE1-explicit-path-tope2] next hop 10.2.1.2
[PE1-explicit-path-tope2] next hop 3.3.3.3
[PE1-explicit-path-tope2] quit
[PE1] explicit-path tope3
Issue 02 (2011-09-10)
524
3 MPLS TE Configuration
# Configure PE2.
<PE2> system-view
[PE2] explicit-path tope1
[PE2-explicit-path-tope1] next hop 10.2.1.1
[PE2-explicit-path-tope1] next hop 1.1.1.1
[PE2-explicit-path-tope1] quit
# Configure PE3.
<PE3> system-view
[PE3] explicit-path tope1
[PE3-explicit-path-tope1] next hop 10.1.1.1
[PE3-explicit-path-tope1] next hop 1.1.1.1
[PE3-explicit-path-tope1] quit
# Create tunnel interfaces on PE1, PE2, and PE3, specify explicit paths, and configure the tunnel
bandwidth to 10 Mbit/s. Bind the tunnel to the specified VPN. Two tunnel interfaces must be
created on PE1.
# Configure PE1.
[PE1] interface tunnel 2/0/0
[PE1-Tunnel2/0/0] ip address unnumbered interface loopback 1
[PE1-Tunnel2/0/0] tunnel-protocol mpls te
[PE1-Tunnel2/0/0] destination 3.3.3.3
[PE1-Tunnel2/0/0] mpls te tunnel-id 200
[PE1-Tunnel2/0/0] mpls te path explicit-path tope2
[PE1-Tunnel2/0/0] mpls te bandwidth ct0 10000
[PE1-Tunnel2/0/0] mpls te reserved-for-binding
[PE1-Tunnel2/0/0] mpls te commit
[PE1-Tunnel2/0/0] quit
[PE1] interface tunnel 1/0/0
[PE1-Tunnel1/0/0] ip address unnumbered interface loopback 1
[PE1-Tunnel1/0/0] tunnel-protocol mpls te
[PE1-Tunnel1/0/0] destination 2.2.2.2
[PE1-Tunnel1/0/0] mpls te tunnel-id 100
[PE1-Tunnel1/0/0] mpls te path explicit-path tope3
[PE1-Tunnel1/0/0] mpls te bandwidth ct0 10000
[PE1-Tunnel1/0/0] mpls te reserved-for-binding
[PE1-Tunnel1/0/0] mpls te commit
[PE1-Tunnel1/0/0] quit
# Configure PE2.
[PE2] interface tunnel 2/0/0
[PE2-Tunnel2/0/0] ip address unnumbered interface loopback 1
[PE2-Tunnel2/0/0] tunnel-protocol mpls te
[PE2-Tunnel2/0/0] destination 1.1.1.1
[PE2-Tunnel2/0/0] mpls te tunnel-id 200
[PE2-Tunnel2/0/0] mpls te path explicit-path tope1
[PE2-Tunnel2/0/0] mpls te bandwidth ct0 10000
[PE2-Tunnel2/0/0] mpls te reserved-for-binding
[PE2-Tunnel2/0/0] mpls te commit
[PE2-Tunnel2/0/0] quit
# Configure PE3.
[PE3] interface tunnel 1/0/0
[PE3-Tunnel1/0/0] ip address unnumbered interface loopback 1
[PE3-Tunnel1/0/0] tunnel-protocol mpls te
[PE3-Tunnel1/0/0] destination 1.1.1.1
[PE3-Tunnel1/0/0] mpls te tunnel-id 100
[PE3-Tunnel1/0/0] mpls te path explicit-path tope1
[PE3-Tunnel1/0/0] mpls te bandwidth ct0 10000
Issue 02 (2011-09-10)
525
3 MPLS TE Configuration
# Run the display mpls te tunnel-interface tunnel interface-number command on PEs, and
you can see that the status of Tunnel 1/0/0 and Tunnel 2/0/0 on PE1, Tunnel 2/0/0 on PE2, and
Tunnel 1/0/0 on PE3 is "Up."
Step 8 Configure VPN FRR.
# Create VPN instances on PE1, PE2, and PE3 separately. Configure all VPN instance names
to vpn1, RDs to 100:1, 100:2, and 100:3 separately, and all RTs to 100:1. Configure CEs to
access PEs. The configuration details are not provided here.
# Establish MP IBGP peer relationship between PE1 and PE2, and between PE1 and PE3. The
BGP AS number of PE1, PE2, and PE3 are 100. The loopback interface Loopback1 is used as
the interface to set up BGP sessions. The configuration details are not provided here.
# Configure tunnel policies for PE1, PE2, and PE3 and apply the policies to the VPN instances.
# Configure PE1.
[PE1] tunnel-policy policy1
[PE1-tunnel-policy-policy1] tunnel binding destination 3.3.3.3 te tunnel 2/0/0
[PE1-tunnel-policy-policy1] tunnel binding destination 2.2.2.2 te tunnel 1/0/0
[PE1-tunnel-policy-policy1] quit
[PE1] ip vpn-instance vpn1
[PE1-ip-vpn-instance-vpn1] ipv4-family
[PE1-ip-vpn-instance-vpn1-af-ipv4] tnl-policy policy1
[PE1-ip-vpn-instance-vpn1-af-ipv4] quit
[PE1-ip-vpn-instance-vpn1] quit
# Configure PE2.
[PE2] tunnel-policy policy1
[PE2-tunnel-policy-policy1] tunnel binding destination 1.1.1.1 te tunnel 2/0/0
[PE2-tunnel-policy-policy1] quit
[PE2] ip vpn-instance vpn1
[PE2-ip-vpn-instance-vpn1] ipv4-family
[PE2-ip-vpn-instance-vpn1-af-ipv4] tnl-policy policy1
[PE2-ip-vpn-instance-vpn1-af-ipv4] quit
[PE2-ip-vpn-instance-vpn1] quit
# Configure PE3.
[PE3] tunnel-policy policy1
[PE3-tunnel-policy-policy1] tunnel binding destination 1.1.1.1 te tunnel 1/0/0
[PE3-tunnel-policy-policy1] quit
[PE3] ip vpn-instance vpn1
[PE3-ip-vpn-instance-vpn1] ipv4-family
[PE3-ip-vpn-instance-vpn1-af-ipv4] tnl-policy policy1
[PE3-ip-vpn-instance-vpn1-af-ipv4] quit
[PE3-ip-vpn-instance-vpn1] quit
Issue 02 (2011-09-10)
526
3 MPLS TE Configuration
# After the configuration, CEs can communicate with each other, and traffic passes through PE1,
switch, and PE2. After the cable of any interface connecting PE1 and PE2 is plugged out, or the
switch or PE2 fails, VPN traffic switches to the backup path PE1 PE3. Time taken in fault
recovery is close to the IGP convergence time.
Step 9 Configure BFD for TE.
# Configure a BFD session on PE1 to detect the TE tunnel of the primary path. Set the minimum
interval at which BFD packets are sent and received to 100 milliseconds and the local BFD
detection multiplier to 3.
[PE1] bfd
[PE1-bfd] quit
[PE1] bfd test bind mpls-te interface tunnel2/0/0
[PE1-bfd-lsp-session-test] discriminator local 12
[PE1-bfd-lsp-session-test] discriminator remote 21
[PE1-bfd-lsp-session-test] min-tx-interval 100
[PE1-bfd-lsp-session-test] min-rx-interval 100
[PE1-bfd-lsp-session-test] detect-multiplier 3
[PE1-bfd-lsp-session-test] process-pst
[PE1-bfd-lsp-session-test] commit
# Configure a BFD session on PE2 and specify the TE tunnel as the BFD backward channel. Set
the minimum interval at which BFD packets are sent and received to 100 milliseconds and the
local BFD detection multiplier to 3.
[PE2] bfd
[PE2-bfd] quit
[PE2] bfd test bind mpls-te interface tunnel2/0/0
[PE2-bfd-lsp-session-test] discriminator local 21
[PE2-bfd-lsp-session-test] discriminator remote 12
[PE2-bfd-lsp-session-test] min-tx-interval 100
[PE2-bfd-lsp-session-test] min-rx-interval 100
[PE2-bfd-lsp-session-test] detect-multiplier 3
[PE2-bfd-lsp-session-test] commit
# Run the display bfd session { all | discriminator discr-value | mpls-te | [ slot slot-id ]
[ verbose ] command on PE1 and PE2, and you can see that the status of the BFD sessions is
Up.
Step 10 Verify the configuration.
Connect port 1 and port 2 on a tester to CE1 and CE2 respectively. Inject traffic from port 1 to
port 2, and you can see that a fault can be recovered at milliseconds level.
----End
Configuration Files
NOTE
Configuration files of CE1, CE2, and switch are not listed here. Configurations related to CE accessing PE
are also not listed.
Issue 02 (2011-09-10)
527
3 MPLS TE Configuration
#
bfd
#
mpls lsr-id 1.1.1.1
mpls
mpls te
mpls rsvp-te
mpls te cspf
#
explicit-path tope2
next hop 10.2.1.2
next hop 3.3.3.3
#
explicit-path tope3
next hop 10.1.1.2
next hop 2.2.2.2
#
interface GigabitEthernet2/0/0
undo shutdown
ip address 10.2.1.1 255.255.255.0
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
mpls rsvp-te
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 10.1.1.1 255.255.255.252
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
mpls rsvp-te
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
interface Tunnel1/0/0
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 2.2.2.2
mpls te tunnel-id 100
mpls te bandwidth ct0 10000
mpls te path explicit-path tope3
mpls te reserved-for-binding
mpls te commit
#
interface Tunnel2/0/0
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 3.3.3.3
mpls te tunnel-id 200
mpls te bandwidth ct0 10000
mpls te path explicit-path tope2
mpls te reserved-for-binding
mpls te commit
#
bgp 100
peer 2.2.2.2 as-number 100
peer 2.2.2.2 connect-interface LoopBack1
peer 3.3.3.3 as-number 100
peer 3.3.3.3 connect-interface LoopBack1
#
ipv4-family unicast
undo synchronization
peer 2.2.2.2 enable
peer 3.3.3.3 enable
Issue 02 (2011-09-10)
528
3 MPLS TE Configuration
#
ipv4-family vpnv4
policy vpn-target
peer 2.2.2.2 enable
peer 3.3.3.3 enable
#
ipv4-family vpn-instance vpn1
import-route direct
#
ospf 1
opaque-capability enable
area 0.0.0.0
network 10.1.1.0 0.0.0.3
network 10.2.1.0 0.0.0.255
network 1.1.1.1 0.0.0.0
mpls-te enable
#
route-policy vpn_frr_rp permit node 10
if-match ip next-hop ip-prefix vpn_frr_list
apply backup-nexthop 2.2.2.2
#
ip ip-prefix vpn_frr_list permit 3.3.3.3 32
#
tunnel-policy policy1
tunnel binding destination 3.3.3.3 te Tunnel2/0/0
tunnel binding destination 2.2.2.2 te Tunnel1/0/0
#
bfd test bind mpls-te interface Tunnel2/0/0
discriminator local 12
discriminator remote 21
min-tx-interval 100
min-rx-interval 100
process-pst
commit
#
#
return
Issue 02 (2011-09-10)
529
3 MPLS TE Configuration
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
interface Tunnel2/0/0
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 1.1.1.1
mpls te tunnel-id 200
mpls te bandwidth ct0 10000
mpls te path explicit-path tope1
mpls te reserved-for-binding
mpls te commit
#
bgp 100
peer 1.1.1.1 as-number 100
peer 1.1.1.1 connect-interface LoopBack1
#
ipv4-family unicast
undo synchronization
peer 1.1.1.1 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.1 enable
#
ipv4-family vpn-instance vpn1
import-route direct
#
ospf 1
opaque-capability enable
area 0.0.0.0
network 10.2.1.0 0.0.0.255
network 3.3.3.3 0.0.0.0
mpls-te enable
#
tunnel-policy policy1
tunnel binding destination 1.1.1.1 te Tunnel2/0/0
#
bfd test bind mpls-te interface Tunnel2/0/0
discriminator local 21
discriminator remote 12
min-tx-interval 100
min-rx-interval 100
commit
#
return
Issue 02 (2011-09-10)
530
3 MPLS TE Configuration
link-protocol ppp
ip address 10.1.1.2 255.255.255.252
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
mpls rsvp-te
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
interface Tunnel1/0/0
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 1.1.1.1
mpls te tunnel-id 100
mpls te bandwidth ct0 10000
mpls te path explicit-path tope1
mpls te reserved-for-binding
mpls te commit
#
bgp 100
peer 1.1.1.1 as-number 100
peer 1.1.1.1 connect-interface LoopBack1
#
ipv4-family unicast
undo synchronization
peer 1.1.1.1 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.1 enable
#
ipv4-family vpn-instance vpn1
import-route direct
#
ospf 1
opaque-capability enable
area 0.0.0.0
network 10.1.1.0 0.0.0.3
network 2.2.2.2 0.0.0.0
mpls-te enable
#
tunnel-policy policy1
tunnel binding destination 1.1.1.1 te Tunnel1/0/0
#
return
Networking Requirements
Figure 3-27 is a networking diagram of CR-LSP hot standby. A TE tunnel is established between
PE1 and PE2. The tunnel is enabled with hot standby and configured with a best-effort LSP. If
the primary CR-LSP fails, traffic can be switched to the backup CR-LSP. After the primary CRLSP recovers, traffic can be switched back to the primary CR-LSP in 15 seconds. If both the
primary and backup CR-LSPs fail, traffic can be switched to the best-effort LSP.
Dynamic BFD for CR-LSP is required to detect the primary and backup CR-LSPs. After the
configuration, the following objects should be achieved:
Issue 02 (2011-09-10)
531
3 MPLS TE Configuration
If the primary CR-LSP fails, traffic can be switched to the backup CR-LSP at the
millisecond level.
If the backup CR-LSP fails within 15 seconds after the primary CR-LSP recovers, traffic
is switched back to the primary CR-LSP.
NOTE
Compared with static BFD, dynamic BFD is simpler in terms of configurations. In addition, dynamic BFD
can reduce the number of BFD sessions, and thus occupies less network resources because only one BFD
session can be created on a tunnel interface.
Loopback1
1.1.1.1/32
GE1/0/0
P1
10.1.1.1/30
GE3/0/0
GE2/0/0
10.2.1.1/30
10.4.1.2/30
Loopback1
2.2.2.2/32
GE1/0/0
P2
10.1.1.2/30
GE3/0/0
10.3.1.2/30
GE2/0/0
10.5.1.2 /30
GE2/0/0
10.4.1.1/30
PE1
GE2/0/0
10.5.1.1/30
GE1/0/0
10.3.1.1/30
Loopback1
4.4.4.4/32
GE1/0/0
10.2.1.2/30
PE2
Loopback1
3.3.3.3/32
: Primary path
: Backup path
: Best-effort path
Configuration Roadmap
The configuration roadmap is as follows:
1.
Configure CR-LSP hot standby based on Example for Configuring CR-LSP Hot.
2.
Enable BFD on the ingress of the tunnel. Configure MPLS TE BFD. Set the minimum
interval at which BFD packets are sent and received, and the local BFD detection multiplier.
3.
Data Preparation
To complete the configuration, you need the following data:
Issue 02 (2011-09-10)
532
3 MPLS TE Configuration
Minimum intervals at which BFD packets are sent and received on the ingress (The default
values are specified in the License.)
Local BFD detection multiplier (The default values are specified in the License.)
For other data, see Example for Configuring CR-LSP Hot Standby
Procedure
Step 1 Configure CR-LSP hot standby.
Configure the primary CR-LSP, backup CR-LSP, and best-effort LSP based on Example for
Configuring CR-LSP Standby.
Step 2 Enable BFD on the ingress of the tunnel and configure MPLS TE BFD.
# Enable MPLS TE BFD on the tunnel interface of PE1. Set the minimum intervals at which
BFD packets are sent and received to 100 milliseconds and the local BFD detection multiplier
to 3.
<PE1> system-view
[PE1] bfd
[PE1-bfd] quit
[PE1] interface tunnel
[PE1-Tunnel1/0/0] mpls
[PE1-Tunenl1/0/0] mpls
multiplier 3
[PE1-Tunenl1/0/0] mpls
1/0/0
te bfd enable
te bfd min-tx-interval 100 min-rx-interval 100 detectte commit
Step 3 Enable the capability of passively creating BFD sessions on the egress of the tunnel.
<PE2> system-view
[PE2] bfd
[PE2-bfd] mpls-passive
[PE2-bfd] quit
# Run the display bfd session discriminator local-discriminator-value command on PE1 and
PE2, and you can see that the status of BFD sessions is Up.
[PE1] display bfd session mpls-te interface Tunnel 1/0/0 te-lsp
-------------------------------------------------------------------------------Local Remote PeerIpAddr
InterfaceName
State
Type
-------------------------------------------------------------------------------8208
8217
3.3.3.3
Tunnel1/0/0
Up
D_TE_LSP
-------------------------------------------------------------------------------Total UP/DOWN Session Number : 1/0
Configuration Files
l
Issue 02 (2011-09-10)
533
3 MPLS TE Configuration
#
mpls lsr-id 4.4.4.4
mpls
mpls te
mpls rsvp-te
mpls te cspf
#
explicit-path backup
next hop 10.3.1.2
next hop 10.5.1.2
next hop 3.3.3.3
#
explicit-path main
next hop 10.4.1.2
next hop 10.2.1.2
next hop 3.3.3.3
#
isis 1
cost-style wide
network-entity 10.0000.0000.0004.00
traffic-eng level-1-2
#
interface GigabitEthernet1/0/0
ip address 10.3.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
mpls rsvp-te
#
interface GigabitEthernet2/0/0
ip address 10.4.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
mpls rsvp-te
#
interface LoopBack1
ip address 4.4.4.4 255.255.255.255
isis enable 1
#
interface Tunnel1/0/0
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 3.3.3.3
mpls te tunnel-id 100
mpls te bfd enable
mpls te record-route
mpls te bandwidth ct0 10000
mpls te path explicit-path main
mpls te path explicit-path backup secondary
mpls te backup hot-standby wtr 15
mpls te backup ordinary best-effort
mpls te commit
#
return
Configuration file of P1
#
sysname P1
#
mpls lsr-id 1.1.1.1
mpls
mpls te
mpls rsvp-te
#
isis 1
Issue 02 (2011-09-10)
534
3 MPLS TE Configuration
cost-style wide
network-entity 10.0000.0000.0001.00
traffic-eng level-1-2
#
interface GigabitEthernet1/0/0
ip address 10.1.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls rsvp-te
#
interface GigabitEthernet2/0/0
ip address 10.4.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls rsvp-te
#
interface GigabitEthernet3/0/0
ip address 10.2.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
mpls rsvp-te
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
isis enable 1
#
return
Configuration file of P2
#
sysname P2
#
mpls lsr-id 2.2.2.2
mpls
mpls te
mpls rsvp-te
#
isis 1
cost-style wide
network-entity 10.0000.0000.0002.00
traffic-eng level-1-2
#
interface GigabitEthernet1/0/0
ip address 10.1.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
mpls rsvp-te
#
interface GigabitEthernet2/0/0
ip address 10.5.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
mpls rsvp-te
#
interface GigabitEthernet3/0/0
ip address 10.3.1.2 255.255.255.252
isis enable 1
mpls
mpls te
Issue 02 (2011-09-10)
535
3 MPLS TE Configuration
mpls rsvp-te
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
isis enable 1
#
return
Networking Requirements
Figure 3-28 shows an MPLS network where a switch (a Layer 2 device) exists between P1 and
P2. An MPLS TE tunnel is established between PE1 and PE2. TE FRR with P1 as PLR and PE2
as MP is configured. The primary CR-LSP is PE1 --> P1 --> Switch --> P2 --> PE2; the bypass
CR-LSP is P1 --> P3 --> PE2. In addition, each device is configured with RSVP GR.
GE 2/0/0 on P1 cannot receive RSVP Hello messages from its neighbors if either of the following
conditions are met:
l
Issue 02 (2011-09-10)
536
3 MPLS TE Configuration
In this situation, P1 cannot identify whether the failure in receiving RSVP Hello messages is
because a fault on the link or switch or because its neighbor is performing RSVP GR; therefore,
P1 cannot determine whether to perform the TE FRR switchover or not.
By default, the interval at which RSVP Hello messages are sent is 3 seconds. The interval at
which a neighbor going Down is declared is three times longer than the interval at which Hello
messages are sent. That means that an LSR can sense a fault on an RSVP neighbor at seconds
level. BFD, however, can detect a fault at milliseconds level.
If BFD for RSVP is configured on the preceding network, P1 can rapidly detect the fault on the
link or switch between P1 and P2 and then perform the TE FRR switchover accordingly.
Figure 3-28 Networking diagram of configuring BFD for RSVP
Loopback1
4.4.4.4/32
Loopback1
1.1.1.1/32
POS1/0/0
10.1.1.1/30
PE1
/0
3/0 /30
S
PO 3.1.1
10.
P1
GE2
POS1/0/0
10.2 /0/0
.1.1
10.1.1.2/30
/24
Loopback1
2.2.2.2/32
/0/0
S1 /30
O
P 1.2
3.
10.
P3
PO
10. S2/0
5.1 /0
.1/3
0
PO
10. S2/0
5.1 /0
.2/3
0
PE2
Switch
/0
1/0 0
S
PO 1.2/3
.4.
GE2
0
/0/ 010 Loopback1
10.2
/0/0
1
S
3
.1.2
PO 4.1.1/
/24
5.5.5.5/32
.
10
Loopback1
3.3.3.3/32
: Primary CR-LSP
: Bypass CR-LSP
P2
Configuration Roadmap
The configuration roadmap is as follows:
1.
Configure an IP address for each interface and enable IGP on each LSR so that LSRs can
communicate with each other. Enable IGP GR to support RSVP GR.
2.
3.
4.
Create a TE primary tunnel interface and enable TE FRR on PE1. Configure the bypass
tunnel on P1.
5.
Configure RSVP GR on all LSRs and establish a Hello session between P1 and PE2.
Issue 02 (2011-09-10)
537
3 MPLS TE Configuration
NOTE
On a network configured with TE FRR, a Hello session is required between a PLR and an MP of the
bypass tunnel if you want to configure RSVP GR. If the Hello session is not configured, when traffic
switches to the bypass tunnel because the primary tunnel fails, the primary tunnel turns Down if the
PLR or MP performs RSVP GR.
6.
Data Preparation
To complete the configuration, you need the following data:
l
MPLS LSR ID
Primary tunnel interface number, bandwidth for the primary tunnel, and explicit path
Bypass tunnel interface number, bandwidth for the bypass tunnel, and explicit path
Minimum intervals at which BFD packets are sent and received (The default values are
specified in the License.)
Local BFD detection multiplier (The default values are specified in the License.)
Procedure
Step 1 Configure an IP address for each interface.
Configure an IP address for each interface as shown in Figure 3-28, create loopback interfaces
on LSRs, and then configure the IP addresses of the loopback interfaces as MPLS LSR IDs. For
configuration details, see the configuration file of this example.
Step 2 Configure the switch.
Configure the switch so that P1 and P2 can communicate with each other. Details for this
configuration procedure are not provided here.
Step 3 Configure an IGP and IGP GR.
Configure OSPF or IS-IS on each LSR so that LSRs can communicate with each other. Configure
IGP GR to support RSVP GR. Examples in this document use OSPF. For configuration details,
see the configuration file of this example.
Step 4 Configuring basic MPLS functions.
Configure the LSR ID and enable MPLS in the system view on each LSR, and enable MPLS in
the interface view. For configuration details, see the configuration file of this example.
Step 5 Configure basic MPLS TE functions.
Enable MPLS-TE and MPLS RSVP-TE in the MPLS and interface views on each LSR. Set the
maximum reservable bandwidth for the outbound interfaces of links along the tunnel to 100
Mbit/s and the BC0 bandwidth to 100 Mbit/s. For configuration details, see the configuration
file of this example.
Step 6 Configure OSPF TE and CSPF.
Issue 02 (2011-09-10)
538
3 MPLS TE Configuration
Enable OSPF TE on each node and configure CSPF on PE1 and PE2. For configuration details,
see Configuring the RSVP-TE Tunnel.
Step 7 Configure the primary tunnel.
# Specify an explicit path for the primary tunnel on PE1.
<PE1> system-view
[PE1] explicit-path tope2
[PE1-explicit-path-tope2]
[PE1-explicit-path-tope2]
[PE1-explicit-path-tope2]
[PE1-explicit-path-tope2]
[PE1-explicit-path-tope2]
next
next
next
next
quit
hop
hop
hop
hop
10.1.1.2
10.2.1.2
10.4.1.2
5.5.5.5
# Create a tunnel interface on PE1, specify an explicit path, set the tunnel bandwidth to 10 Mbit/
s, and enable TE FRR.
[PE1] interface tunnel 1/0/0
[PE1-Tunnel1/0/0] ip address unnumbered interface loopback 1
[PE1-Tunnel1/0/0] tunnel-protocol mpls te
[PE1-Tunnel1/0/0] destination 5.5.5.5
[PE1-Tunnel1/0/0] mpls te tunnel-id 100
[PE1-Tunnel1/0/0] mpls te path explicit-path tope2
[PE1-Tunnel1/0/0] mpls te bandwidth ct0 10000
[PE1-Tunnel1/0/0] mpls te fast-reroute
[PE1-Tunnel1/0/0] mpls te commit
[PE1-Tunnel1/0/0] quit
# Run the display mpls te tunnel-interface tunnel interface-number command on PE1, and
you can see that the status of tunnel 1/0/0 on PE1 is "Up."
Step 8 Configure the bypass tunnel.
# Specify the explicit path for the bypass tunnel on P1.
<P1> system-view
[P1] explicit-path tope2
[P1-explicit-path-tope2]
[P1-explicit-path-tope2]
[P1-explicit-path-tope2]
[P1-explicit-path-tope2]
# Configure a bypass tunnel interface and specify an explicit path for the bypass tunnel. Set the
tunnel bandwidth to 20 Mbit/s and the protected bandwidth to 10 Mbit/s. Specify the physical
interface to be protected by the bypass tunnel.
[P1] interface tunnel 3/0/0
[P1-Tunnel3/0/0] ip address unnumbered interface loopback 1
[P1-Tunnel3/0/0] tunnel-protocol mpls te
[P1-Tunnel3/0/0] destination 5.5.5.5
[P1-Tunnel3/0/0] mpls te tunnel-id 300
[P1-Tunnel3/0/0] mpls te path explicit-path tope2
[P1-Tunnel3/0/0] mpls te bandwidth ct0 20000
[P1-Tunnel3/0/0] mpls te bypass-tunnel
[P1-Tunnel3/0/0] mpls te protected-interface gigabitethernet 2/0/0
[P1-Tunnel3/0/0] mpls te commit
[P1-Tunnel3/0/0] quit
Issue 02 (2011-09-10)
539
3 MPLS TE Configuration
# Configure P1.
[P1] mpls
[P1-mpls] mpls rsvp-te hello
[P1-mpls] mpls rsvp-te hello full-gr
[P1-mpls] mpls rsvp-te hello nodeid-session 5.5.5.5
[P1-mpls] quit
[P1] interface pos1/0/0
[P1-Pos1/0/0] mpls rsvp-te hello
[P1-Pos1/0/0] quit
[P1] interface gigabitethernet 2/0/0
[P1-GigabitEthernet2/0/0] mpls rsvp-te hello
[P1-GigabitEthernet2/0/0] quit
[P1] interface pos 3/0/0
[P1-Pos3/0/0] mpls rsvp-te hello
[P1-Pos3/0/0] quit
# Configure P2.
[P2] mpls
[P2-mpls] mpls rsvp-te hello
[P2-mpls] mpls rsvp-te hello full-gr
[P2-mpls] quit
[P2] interface pos1/0/0
[P2-Pos1/0/0] mpls rsvp-te hello
[P2-Pos1/0/0] quit
[P2] interface gigabitethernet 2/0/0
[P2-GigabitEthernet2/0/0] mpls rsvp-te hello
[P2-GigabitEthernet2/0/0] quit
# Configure P3.
[P3] mpls
[P3-mpls] mpls rsvp-te hello
[P3-mpls] mpls rsvp-te hello full-gr
[P3-mpls] quit
[P3] interface pos1/0/0
[P3-Pos1/0/0] mpls rsvp-te hello
[P3-Pos1/0/0] quit
[P3] interface pos 2/0/0
[P3-Pos2/0/0] mpls rsvp-te hello
[P3-Pos2/0/0] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] mpls rsvp-te hello
[PE2-mpls] mpls rsvp-te hello full-gr
[PE2-mpls] mpls rsvp-te hello nodeid-session 2.2.2.2
[PE2-mpls] quit
[PE2] interface pos1/0/0
[PE2-Pos1/0/0] mpls rsvp-te hello
[PE2-Pos1/0/0] quit
[PE2] interface pos 2/0/0
[PE2-Pos2/0/0] mpls rsvp-te hello
[PE2-Pos2/0/0] quit
Issue 02 (2011-09-10)
540
3 MPLS TE Configuration
[P1-bfd] quit
[P1] interface gigabitethernet 2/0/0
[P1-GigabitEthernet2/0/0] mpls rsvp-te bfd enable
[P1-GigabitEthernet2/0/0] mpls rsvp-te bfd min-tx-interval 100 min-rx-interval 100
detect-multiplier 3
[P1-GigabitEthernet2/0/0] quit
# Configure P2.
[P2] bfd
[P2-bfd] quit
[P2] interface gigabitethernet 2/0/0
[P2-GigabitEthernet2/0/0] mpls rsvp-te bfd enable
[P2-GigabitEthernet2/0/0] mpls rsvp-te bfd min-tx-interval 100 min-rx-interval 100
detect-multiplier 3
[P2-GigabitEthernet2/0/0] quit
# Run the display mpls rsvp-te bfd session { all | interface interface-name | peer ip-addr }
command on PE1 and PE2, and you can see that the status of the BFD sessions is Up.
Step 11 Verify the configuration.
Connect port 1 and port 2 on a tester to PE1 and PE2 respectively. Inject MPLS traffic from port
1 to port 2 (Note the setting of the label value). After the cable is removed from any interface
on P1 and P2, you can see that the fault recovers at milliseconds level.
----End
Configuration Files
NOTE
Issue 02 (2011-09-10)
541
3 MPLS TE Configuration
tunnel-protocol mpls te
destination 5.5.5.5
mpls te tunnel-id 100
mpls te bandwidth ct0 10000
mpls te path explicit-path tope2
mpls te fast-reroute
mpls te commit
#
ospf 1
opaque-capability enable
graceful-restart
area 0.0.0.0
network 10.1.1.0 0.0.0.3
network 1.1.1.1 0.0.0.0
mpls-te enable
#
return
Configuration file of P1
#
sysname P1
#
mpls lsr-id 2.2.2.2
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls rsvp-te hello full-gr
mpls rsvp-te hello nodeid-session 5.5.5.5
mpls te cspf
#
explicit-path tope2
next hop 10.3.1.2
next hop 10.5.1.2
next hop 5.5.5.5
#
bfd
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 10.1.1.2 255.255.255.252
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
#
interface GigabitEthernet2/0/0
undo shutdown
ip address 10.2.1.1 255.255.255.0
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
mpls rsvp-te
mpls rsvp-te hello
mpls rsvp-te bfd enable
#
interface Pos3/0/0
undo shutdown
link-protocol ppp
ip address 10.3.1.1 255.255.255.252
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
mpls rsvp-te
mpls rsvp-te hello
#
interface LoopBack1
Issue 02 (2011-09-10)
542
3 MPLS TE Configuration
Configuration file of P2
#
sysname P2
#
mpls lsr-id 3.3.3.3
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls rsvp-te hello full-gr
#
bfd
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 10.4.1.1 255.255.255.252
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
mpls rsvp-te
mpls rsvp-te hello
#
interface GigabitEthernet2/0/0
undo shutdown
ip address 10.2.1.2 255.255.255.0
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls rsvp-te bfd enable
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
ospf 1
opaque-capability enable
graceful-restart
area 0.0.0.0
network 10.2.1.0 0.0.0.255
network 10.4.1.0 0.0.0.3
network 3.3.3.3 0.0.0.0
mpls-te enable
#
Issue 02 (2011-09-10)
543
3 MPLS TE Configuration
return
Configuration file of P3
#
sysname P3
#
mpls lsr-id 4.4.4.4
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls rsvp-te hello full-gr
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 10.3.1.2 255.255.255.252
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
#
interface Pos2/0/0
undo shutdown
link-protocol ppp
ip address 10.5.1.1 255.255.255.252
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
mpls rsvp-te
mpls rsvp-te hello
#
interface LoopBack1
ip address 4.4.4.4 255.255.255.255
#
ospf 1
opaque-capability enable
graceful-restart
area 0.0.0.0
network 10.3.1.0 0.0.0.3
network 10.5.1.0 0.0.0.3
network 4.4.4.4 0.0.0.0
mpls-te enable
#
return
Issue 02 (2011-09-10)
544
3 MPLS TE Configuration
link-protocol ppp
ip address 10.5.1.2 255.255.255.252
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
#
interface LoopBack1
ip address 5.5.5.5 255.255.255.255
#
ospf 1
opaque-capability enable
graceful-restart
area 0.0.0.0
network 10.4.1.0 0.0.0.3
network 10.5.1.0 0.0.0.3
network 5.5.5.5 0.0.0.0
mpls-te enable
#
return
Networking Requirements
On the network shown in Figure 3-29, LDP is run between LSR A and LSR B, and between
LSR D and LSR E. LDP does not run between LSR B, LSR C and LSR D. RSVP tunnels from
LSR B to LSR D and from LSR D to LSR B are established. It is required that traffic between
LSR A and LSR E pass transmitted over tunnels.
LDP is not run between LSR B, LSR C, and LSR D.
Figure 3-29 Networking diagram of LDP over TE configuration
Loopback1
2.2.2.2/32
POS2/0/0
20.1.1.1/24
LSRB
POS2/0/0
30.1.1.1/24
POS1/0/0
20.1.1.2/24 LSRC
POS1/0/0
10.1.1.2/24
Loopback1
4.4.4.4/32
Loopback1
3.3.3.3/32
LSRD
POS1/0/0
30.1.1.2/24
POS1/0/0
10.1.1.1/24
POS1/0/0
40.1.1.1/24
POS2/0/0
40.1.1.2/24
Loopback1
5.5.5.5/32
Loopback1
1.1.1.1/32
LSRA
LSRE
Configuration Roadmap
The configuration roadmap is as follows:
1.
Issue 02 (2011-09-10)
Configure IP addresses for interfaces on each LSR, configure loopback address as the LSR
IDs, and enable IGP.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
545
3 MPLS TE Configuration
2.
Enable OSPF TE or IS-IS TE in the area supporting TE and create an MPLS TE tunnel.
3.
Enable MPLS LDP in the area that does not support TE and configure LDP remote peer
on the border of TE.
4.
Data Preparation
To complete the configuration, you need the following data.
l
Policy for triggering the establishment of the LSP (in this example the policy is all)
Tunnel interface names, IP addresses, destination addresses, tunnel IDs, tunnel signaling
protocols (default RSVP-TE), tunnel bandwidths, TE metric values, and link cost values
of LSR B and LSR D
Procedure
Step 1 Configure an IP address for each interface.
Configure the IP address and mask for each interface as shown in Figure 3-29, including the
loopback interface.. Details for these configurations are not provided here.
Step 2 Configure IGP.
Configure IS-IS on all LSRs to advertise LSR ID.
# Configure LSR A.
[LSRA] isis 1
[LSRA-isis-1] network-entity 86.1111.1111.1111.00
[LSRA-isis-1] is-level level-2
[LSRA-isis-1] cost-style wide
[LSRA-isis-1] quit
[LSRA] interface loopback 1
[LSRA-LoopBack1] isis enable 1
[LSRA-LoopBack1] quit
[LSRA] interface pos 1/0/0
[LSRA-Pos1/0/0] isis enable 1
[LSRA-Pos1/0/0] quit
# Configure LSR B.
[LSRB] isis 1
[LSRB-isis-1] network-entity 86.2222.2222.2222.00
[LSRB-isis-1] is-level level-2
[LSRB-isis-1] cost-style wide
[LSRB-isis-1] traffic-eng level-2
[LSRB-isis-1] quit
[LSRB] interface loopback 1
[LSRB-LoopBack1] isis enable 1
[LSRB-LoopBack1] quit
[LSRB] interface pos 1/0/0
[LSRB-Pos1/0/0] isis enable 1
[LSRB-Pos1/0/0] quit
[LSRB] interface pos 2/0/0
[LSRB-Pos2/0/0] isis enable 1
[LSRB-Pos2/0/0] quit
# Configure LSR C.
Issue 02 (2011-09-10)
546
3 MPLS TE Configuration
[LSRC] isis 1
[LSRC-isis-1] network-entity 86.3333.3333.3333.00
[LSRC-isis-1] is-level level-2
[LSRC-isis-1] cost-style wide
[LSRC-isis-1] traffic-eng level-2
[LSRC-isis-1] quit
[LSRC] interface loopback 1
[LSRC-LoopBack1] isis enable 1
[LSRC-LoopBack1] quit
[LSRC] interface pos 1/0/0
[LSRC-Pos1/0/0] isis enable 1
[LSRC-Pos1/0/0] quit
[LSRC] interface pos 2/0/0
[LSRC-Pos2/0/0] isis enable 1
[LSRC-Pos2/0/0] quit
# Configure LSR D.
[LSRD] isis 1
[LSRD-isis-1] network-entity 86.4444.4444.4444.00
[LSRD-isis-1] is-level level-2
[LSRD-isis-1] cost-style wide
[LSRD-isis-1] traffic-eng level-2
[LSRD-isis-1] quit
[LSRD] interface loopback 1
[LSRD-LoopBack1] isis enable 1
[LSRD-LoopBack1] quit
[LSRD] interface pos 1/0/0
[LSRD-Pos1/0/0] isis enable 1
[LSRD-Pos1/0/0] quit
[LSRD] interface pos 2/0/0
[LSRD-Pos2/0/0] isis enable 1
[LSRD-Pos2/0/0] quit
# Configure LSR E.
[LSRE] isis 1
[LSRE-isis-1] network-entity 86.5555.5555.5555.00
[LSRE-isis-1] is-level level-2
[LSRE-isis-1] cost-style wide
[LSRE-isis-1] quit
[LSRE] interface loopback 1
[LSRE-LoopBack1] isis enable 1
[LSRE-LoopBack1] quit
[LSRE] interface pos 1/0/0
[LSRE-Pos1/0/0] isis enable 1
[LSRE-Pos1/0/0] quit
After the configuration, run the display ip routing-table command on each LSR, and you can
see that LSRs can learn routes from each other.
Take the display on LSR A as an example.
[LSRA] display ip routing-table
Route Flags: R - relay, D - download to fib
-----------------------------------------------------------------------------Routing Tables: Public
Destinations : 13
Routes : 13
Destination/Mask
Proto Pre Cost Flags
NextHop
Interface
1.1.1.1/32 Direct 0
0
D
127.0.0.1
InLoopBack0
2.2.2.2/32 ISIS
15
10
D
10.1.1.2
Pos1/0/0
3.3.3.3/32 ISIS
15
20
D
10.1.1.2
Pos1/0/0
4.4.4.4/32 ISIS
15
30
D
10.1.1.2
Pos1/0/0
5.5.5.5/32 ISIS
15
40
D
10.1.1.2
Pos1/0/0
10.1.1.0/24 Direct 0
0
D
10.1.1.1
Pos1/0/0
10.1.1.1/32 Direct 0
0
D
127.0.0.1
InLoopBack0
10.1.1.2/32 Direct 0
0
D
10.1.1.2
Pos1/0/0
20.1.1.0/24 ISIS
15
20
D
10.1.1.2
Pos1/0/0
30.1.1.0/24 ISIS
15
30
D
10.1.1.2
Pos1/0/0
40.1.1.0/24 ISIS
15
40
D
10.1.1.2
Pos1/0/0
Issue 02 (2011-09-10)
547
3 MPLS TE Configuration
127.0.0.0/8
127.0.0.1/32
Direct 0
Direct 0
0
0
D
D
127.0.0.1
127.0.0.1
InLoopBack0
InLoopBack0
Step 3 Configure basic MPLS functions on all LSRs, enable LDP on LSR A, LSR B, LSR D, and LSR
E, and enable RSVP on LSR B, LSR C, and LSR D.
# Configure LSR A.
[LSRA] mpls lsr-id 1.1.1.1
[LSRA] mpls
[LSRA-mpls] quit
[LSRA] mpls ldp
[LSRA-mpls-ldp] quit
[LSRA] interface pos 1/0/0
[LSRA-Pos1/0/0] mpls
[LSRA-Pos1/0/0] mpls ldp
[LSRA-Pos1/0/0] quit
# Configure LSR B.
[LSRB] mpls lsr-id 2.2.2.2
[LSRB] mpls
[LSRB-mpls] mpls te
[LSRB-mpls] mpls rsvp-te
[LSRB-mpls] mpls te cspf
[LSRB-mpls] quit
[LSRB] mpls ldp
[LSRB-mpls-ldp] quit
[LSRB] interface pos 1/0/0
[LSRB-Pos1/0/0] mpls
[LSRB-Pos1/0/0] mpls ldp
[LSRB-Pos1/0/0] quit
[LSRB] interface pos 2/0/0
[LSRB-Pos2/0/0] mpls
[LSRB-Pos2/0/0] mpls te
[LSRB-Pos2/0/0] mpls rsvp-te
[LSRB-Pos2/0/0] quit
# Configure LSR C.
[LSRC] mpls lsr-id 3.3.3.3
[LSRC] mpls
[LSRC-mpls] mpls te
[LSRC-mpls] mpls rsvp-te
[LSRC-mpls] quit
[LSRC] interface pos 1/0/0
[LSRC-Pos1/0/0] mpls
[LSRC-Pos1/0/0] mpls te
[LSRC-Pos1/0/0] mpls rsvp-te
[LSRC-Pos1/0/0] quit
[LSRC] interface pos 2/0/0
[LSRC-Pos2/0/0] mpls
[LSRC-Pos2/0/0] mpls te
[LSRC-Pos2/0/0] mpls rsvp-te
[LSRC-Pos2/0/0] quit
# Configure LSR D.
[LSRD] mpls lsr-id 4.4.4.4
[LSRD] mpls
[LSRD-mpls] mpls te
[LSRD-mpls] mpls rsvp-te
[LSRD-mpls] mpls te cspf
[LSRD-mpls] quit
[LSRD] mpls ldp
[LSRD-mpls-ldp] quit
[LSRD] interface pos 1/0/0
[LSRD-Pos1/0/0] mpls
[LSRD-Pos1/0/0] mpls te
[LSRD-Pos1/0/0] mpls rsvp-te
Issue 02 (2011-09-10)
548
3 MPLS TE Configuration
[LSRD-Pos1/0/0] quit
[LSRD] interface pos 2/0/0
[LSRD-Pos2/0/0] mpls
[LSRD-Pos2/0/0] mpls ldp
[LSRD-Pos2/0/0] quit
# Configure LSR E.
[LSRE] mpls lsr-id 5.5.5.5
[LSRE] mpls
[LSRE-mpls] quit
[LSRE] mpls ldp
[LSRE-mpls-ldp] quit
[LSRE] interface pos 1/0/0
[LSRE-Pos1/0/0] mpls
[LSRE-Pos1/0/0] mpls ldp
[LSRE-Pos1/0/0] quit
After the configuration, the LDP session is established successfully between LSR A and LSR
B, and between LSR D and LSR E.
Run the display mpls ldp session command on LSR A, LSR B, LSR D, and LSR E, and you
can view whether LDP sessions are established.
Run the display mpls ldp peer command, and you can view whether LDP peers have been set
up.
Run the display mpls lsp command, and you can view that RSVP LSP is not set up.
Take the display on LSR A as an example.
[LSRA] display mpls ldp session
LDP Session(s) in Public Network
Codes: LAM(Label Advertisement Mode), SsnAge Unit(DDDD:HH:MM)
A '*' before a session means the session is being deleted.
-----------------------------------------------------------------------------PeerID
Status
LAM SsnRole SsnAge
KASent/Rcv
-----------------------------------------------------------------------------2.2.2.2:0
Operational DU
Passive 000:00:00
1/1
-----------------------------------------------------------------------------TOTAL: 1 session(s) Found.
[LSRA] display mpls ldp peer
LDP Peer Information in Public network
A '*' before a peer means the peer is being deleted.
-----------------------------------------------------------------------------PeerID
TransportAddress
DiscoverySource
-----------------------------------------------------------------------------2.2.2.2:0
2.2.2.2
Pos1/0/0
-----------------------------------------------------------------------------TOTAL: 1 Peer(s) Found.
[LSRA] display mpls lsp
---------------------------------------------------------------------LSP Information: LDP LSP
---------------------------------------------------------------------FEC
In/Out Label In/Out IF
Vrf Name
2.2.2.2/32
NULL/3
-/Pos1/0/0
2.2.2.2/32
1024/3
-/Pos1/0/0
4.4.4.4/32
NULL/1026
-/Pos1/0/0
4.4.4.4/32
1027/1026
-/Pos1/0/0
3.3.3.3/32
NULL/1028
-/Pos1/0/0
3.3.3.3/32
1029/1028
-/Pos1/0/0
5.5.5.5/32
NULL/1029
-/Pos1/0/0
5.5.5.5/32
1030/1029
-/Pos1/0/0
Step 4 Configure the LDP remote session between LSR B and LSR D.
# Configure LSR B.
[LSRB] mpls ldp remote-peer LSRD
Issue 02 (2011-09-10)
549
3 MPLS TE Configuration
# Configure LSR D.
[LSRB] mpls ldp remote-peer LSRB
[LSRB-mpls-ldp-remote-LSRB] remote-ip 2.2.2.2
[LSRB-mpls-ldp-remote-LSRB] quit
After the configuration, run the display mpls ldp remote-peer command on LSR B or LSR D,
and you can view the remote session is set up successfully between LSR B and LSR D.
Take the display on LSR B as an example.
[LSRB] display mpls ldp remote-peer LSRD
LDP Remote Entity Information
-----------------------------------------------------------------------------Remote Peer Name : lsrd
Remote Peer IP
: 4.4.4.4
LDP ID
: 2.2.2.2:0
Transport Address : 2.2.2.2
Entity Status : Active
Configured Keepalive Hold Timer : 45 Sec
Configured Keepalive Send Timer : --Configured Hello Hold Timer
: 45 Sec
Negotiated Hello Hold Timer
: 45 Sec
Configured Hello Send Timer
: --Configured Delay Timer
: 0 Sec
Hello Packet sent/received
: 19/16
Remote Peer Deletion Status
: No
------------------------------------------------------------------------------
Step 5 Configure the bandwidth attributes for the outbound interfaces of links along the TE tunnel.
# Configure LSR B.
[LSRB] interface pos 2/0/0
[LSRB-Pos2/0/0] mpls te bandwidth max-reservable-bandwidth 20000
[LSRB-Pos2/0/0] mpls te bandwidth bc0 20000
[LSRB-Pos2/0/0] quit
# Configure LSR C.
[LSRC] interface pos
[LSRC-Pos1/0/0] mpls
[LSRC-Pos1/0/0] mpls
[LSRC-Pos1/0/0] quit
[LSRC] interface pos
[LSRC-Pos2/0/0] mpls
[LSRC-Pos2/0/0] mpls
[LSRC-Pos2/0/0] quit
1/0/0
te bandwidth max-reservable-bandwidth 20000
te bandwidth bc0 20000
2/0/0
te bandwidth max-reservable-bandwidth 20000
te bandwidth bc0 20000
# Configure LSR D.
[LSRD] interface pos 1/0/0
[LSRD-Pos1/0/0] mpls te bandwidth max-reservable-bandwidth 20000
[LSRD-Pos1/0/0] mpls te bandwidth bc0 20000
[LSRD-Pos1/0/0] quit
Issue 02 (2011-09-10)
550
3 MPLS TE Configuration
[LSRB-Tunnel1/0/0]
[LSRB-Tunnel1/0/0]
[LSRB-Tunnel1/0/0]
[LSRB-Tunnel1/0/0]
[LSRB-Tunnel1/0/0]
mpls
mpls
mpls
mpls
isis
# Run the display mpls lsp command on LSR B, LSR C, and LSR D, and you can see that the
RSVP LSP has been set up between them.
Take the display on LSR B as an example.
[LSRB] display mpls lsp
------------------------------------------------------------------------LSP Information: RSVP LSP
------------------------------------------------------------------------FEC
In/Out Label In/Out IF
Vrf Name
4.4.4.4/32
NULL/1024
-/Pos2/0/0
------------------------------------------------------------------------LSP Information: LDP LSP
------------------------------------------------------------------------FEC
In/Out Label In/Out IF
Vrf Name
3.3.3.3/32
1024/NULL
-/1.1.1.1/32
NULL/3
-/Pos1/0/0
1.1.1.1/32
1028/3
-/Pos1/0/0
4.4.4.4/32
NULL/3
-/Tun1/0/0
4.4.4.4/32
1025/3
-/Tun1/0/0
5.5.5.5/32
NULL/1029
-/Tun1/0/0
5.5.5.5/32
1026/1029
-/Tun1/0/0
----End
Configuration Files
l
Issue 02 (2011-09-10)
551
3 MPLS TE Configuration
mpls ldp
#
isis 1
is-level level-2
cost-style wide
network-entity 86.1111.1111.1111.00
#
interface Pos1/0/0
link-protocol ppp
ip address 10.1.1.1 255.255.255.0
isis enable 1
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
isis enable 1
#
return
Issue 02 (2011-09-10)
552
3 MPLS TE Configuration
mpls te commit
isis enable 1
#
return
Issue 02 (2011-09-10)
553
3 MPLS TE Configuration
isis enable 1
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 20000
mpls te bandwidth bc0 20000
mpls rsvp-te
#
interface Pos2/0/0
link-protocol ppp
ip address 40.1.1.1 255.255.255.0
isis enable 1
mpls
mpls ldp
#
interface LoopBack1
ip address 4.4.4.4 255.255.255.255
isis enable 1
#
interface Tunnel1/0/0
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 2.2.2.2
mpls te tunnel-id 100
mpls te bandwidth ct0 10000
mpls te igp advertise
mpls te igp metric absolute 1
mpls te commit
isis enable 1
#
return
554
3 MPLS TE Configuration
that a tunnel be set up on LSR A and LSR C separately destined for LSR B and that IGP shortcut
be enabled on LSR A and LSR C so that routes on LSR A and LSR C to LSR B use the tunnel
interfaces as the outbound interfaces.
Figure 3-30 Networking for configuring inter-area tunnels
Loopback1
Loopback1
Loopback1
2.2.2.2/32
3.3.3.3/32
1.1.1.1/32
GE2/0/0
GE2/0/0
GE1/0/0
GE1/0/0
20.0.0.1/24 20.0.0.2/24
10.0.0.1/24 10.0.0.2/24
LSRA
LSRB
LSRC
Configuration Roadmap
The configuration roadmap is as follows:
1.
Configure an IP address for each interface on the LSRs and the loopback interface address
used as the LSR ID, and configure OSPF to advertise the network segments connected to
the interfaces on the LSRs and host routes of LSR IDs.
2.
Configure the LSR ID of each LSR and enable MPLS, MPLS TE, and MPLS RSVP-TE
on each LSR and interface.
3.
Set up a tunnel destined to LSR B on LSR A and LSR C separately and enable IGP shortcut
on LSR A and LSR C.
4.
Run the advertise mpls-lsr-id command on LSR B so that the host route 2.2.2.2, an interarea route, is advertised to both Area 0 and Area 1.
Data Preparation
To complete the configuration, you need the following data:
l
Interface number, IP address, destination address, and tunnel ID of each tunnel interface
on LSR A and LSR C
Procedure
Step 1 Configure an IP address for each interface on the LSRs and configure OSPF.
Configure an IP address and a mask for each interface and configure OSPF so that all LSRs can
communicate with each other.
The configuration details are not provided here.
Step 2 Configure basic MPLS functions and enable MPLS TE and MPLS RSVP-TE.
# Configure LSR A.
[LSRA] mpls lsr-id 1.1.1.1
[LSRA] mpls
[LSRA-mpls] mpls te
[LSRA-mpls] mpls rsvp-te
Issue 02 (2011-09-10)
555
3 MPLS TE Configuration
[LSRA-mpls] quit
[LSRA] interface gigabitethernet
[LSRA-GigabitEthernet1/0/0] ospf
[LSRA-GigabitEthernet1/0/0] mpls
[LSRA-GigabitEthernet1/0/0] mpls
[LSRA-GigabitEthernet1/0/0] mpls
[LSRA-GigabitEthernet1/0/0] quit
1/0/0
network-type p2p
te
rsvp-te
The configuration performed on LSR B and LSR C is similar to that on LSR A, and thus are not
provided here.
Step 3 Configure an MPLS TE tunnel and IGP shortcut.
# Set up an MPLS TE tunnel from LSR A to LSR B and configure IGP shortcut. The OSPF cost
of the tunnel is smaller than that of the physical link.
[LSRA] interface tunnel 1/0/0
[LSRA-Tunnel1/0/0] ip address unnumbered interface loopback 1
[LSRA-Tunnel1/0/0] tunnel-protocol mpls te
[LSRA-Tunnel1/0/0] destination 2.2.2.2
[LSRA-Tunnel1/0/0] mpls te tunnel-id 100
[LSRA-Tunnel1/0/0] mpls te igp shortcut ospf
[LSRA-Tunnel1/0/0] mpls te igp metric absolute 1
[LSRA-Tunnel1/0/0] mpls te commit
[LSRA-Tunnel1/0/0] quit
# Set up an MPLS TE tunnel from LSR C to LSR B and configure IGP shortcut. The OSPF cost
of the tunnel is smaller than that of the physical link.
[LSRC] interface tunnel 2/0/0
[LSRC-Tunnel2/0/0] ip address unnumbered interface loopback 1
[LSRC-Tunnel2/0/0] tunnel-protocol mpls te
[LSRC-Tunnel2/0/0] destination 2.2.2.2
[LSRC-Tunnel2/0/0] mpls te tunnel-id 200
[LSRC-Tunnel2/0/0] mpls te igp shortcut ospf
[LSRC-Tunnel2/0/0] mpls te igp metric absolute 1
[LSRC-Tunnel2/0/0] mpls te commit
[LSRC-Tunnel2/0/0] quit
After the configurations are complete, run the display interface tunnel command on LSR A.
You can see that the tunnel interface is Up.
# Run the display mpls te tunnel command on LSR A and LSR C. You can view information
about each MPLS TE tunnel.
<LSRA> display mpls te tunnel
-----------------------------------------------------------------------------Ingress LsrId
Destination
LSPID
In/Out Label
R Tunnel-name
-----------------------------------------------------------------------------1.1.1.1
2.2.2.2
1
--/3
I Tunnel1/0/0
<LSRC> display mpls te tunnel
-----------------------------------------------------------------------------Ingress LsrId
Destination
LSPID
In/Out Label
R Tunnel-name
-----------------------------------------------------------------------------3.3.3.3
2.2.2.2
1
--/3
I Tunnel2/0/0
Step 4 Configure the ABR so that LSR B can advertise MPLS LSR IDs to multiple OSPF areas.
[LSRB] ospf 1
[LSRB-ospf-1] advertise mpls-lsr-id
556
3 MPLS TE Configuration
# Run the display ip routing-table 2.2.2.2 command on LSR A. You can see that in the routing
table, the outbound interface of the route to 2.2.2.2 is a tunnel interface.
<LSRA> display ip routing-table 2.2.2.2
Route Flags: R - relay, D - download to fib
-----------------------------------------------------------------------------Routing Table : Public
Summary Count : 1
Destination/Mask
Proto Pre Cost
Flags NextHop
Interface
2.2.2.2/32
OSPF
10
1.1.1.1
Tunnel1/0/0
OSPF
10
3.3.3.3
Tunnel2/0/0
----End
Configuration Files
l
Issue 02 (2011-09-10)
557
3 MPLS TE Configuration
Issue 02 (2011-09-10)
558
3 MPLS TE Configuration
destination 2.2.2.2
mpls te tunnel-id 200
mpls te igp shortcut ospf
mpls te igp metric absolute 1
mpls te commit
#
ospf 1 router-id 3.3.3.3
opaque-capability enable
enable traffic-adjustment
area 0.0.0.1
network 20.0.0.0 0.0.0.255
network 3.3.3.3 0.0.0.0
mpls-te enable
#
return
Networking Requirements
On the network shown in Figure 3-31,
l
A TE tunnel is established from LSR A to LSR E using RSVP-TE. The tunnel traverses
the IS-IS area with the bandwidth of 20 Mbit/s.
The maximum reservable bandwidth of the link that the tunnel traverses is 100 Mbit/s and
the BC0 bandwidth is 100 Mbit/s.
Issue 02 (2011-09-10)
Loopback1
5.5.5.5/32
559
3 MPLS TE Configuration
Configuration Roadmap
The configuration roadmap is as follows:
1.
Configure IP addresses for interfaces on each LSR, configure loopback address as LSR
IDs.
2.
3.
Configure the loose explicit path including ABR (LSR B, LSR C, and LSR D).
4.
5.
Configure the bandwidth attributes for the outbound interfaces of links along the TE tunnel.
6.
Establish the tunnel interface on the ingress, specify the IP address of the tunnel, the tunnel
protocol, the destination address, the tunnel ID, the RSVP-TE protocol, and the tunnel
bandwidth.
Data Preparation
To complete the configuration, you need the following data.
l
IS-IS area ID of each LSR, originating system ID, and IS-IS level
Maximum reservable bandwidth and BC bandwidth for outbound interfaces of links along
the tunnel
Name of the tunnel interface, IP address, destination address, tunnel ID, tunnel signaling
protocol (RSVP-TE), and tunnel bandwidth
Procedure
Step 1 Configure an IP address for each interface.
Configure the IP address and mask for each interface, including the loopback interface as shown
in Figure 3-31.
The configuration details are not provided here.
Step 2 Configure the IS-IS protocol to advertise routes.
# Configure LSR A.
[LSRA] isis 1
[LSRA-isis-1] network-entity 00.0005.0000.0000.0001.00
[LSRA-isis-1] is-level level-1
[LSRA-isis-1] quit
[LSRA] interface gigabitethernet 1/0/0
[LSRA-GigabitEthernet1/0/0] isis enable 1
[LSRA-GigabitEthernet1/0/0] quit
[LSRA] interface loopback 1
[LSRA-LoopBack1] isis enable 1
[LSRA-LoopBack1] quit
# Configure LSR B.
[LSRB] isis 1
[LSRB-isis-1] network-entity 00.0005.0000.0000.0002.00
[LSRB-isis-1] is-level level-1-2
[LSRB-isis-1] import-route isis level-2 into level-1
[LSRB-isis-1] quit
[LSRB] interface gigabitethernet 1/0/0
[LSRB-GigabitEthernet1/0/0] isis enable 1
[LSRB-GigabitEthernet1/0/0] quit
[LSRB] interface pos 2/0/0
Issue 02 (2011-09-10)
560
3 MPLS TE Configuration
# Configure LSR C.
[LSRC] isis 1
[LSRC-isis-1] network-entity 00.0006.0000.0000.0003.00
[LSRC-isis-1] is-level level-2
[LSRC-isis-1] quit
[LSRC] interface gigabitethernet 1/0/0
[LSRC-GigabitEthernet1/0/0] isis enable 1
[LSRC-GigabitEthernet1/0/0] quit
[LSRC] interface pos 2/0/0
[LSRC-Pos2/0/0] isis enable 1
[LSRC-Pos2/0/0] quit
[LSRC] interface loopback 1
[LSRC-LoopBack1] isis enable 1
[LSRC-LoopBack1] quit
# Configure LSR D.
[LSRD] isis 1
[LSRD-isis-1] network-entity 00.0007.0000.0000.0004.00
[LSRD-isis-1] is-level level-1-2
[LSRD-isis-1] import-route isis level-2 into level-1
[LSRD-isis-1] quit
[LSRD] interface gigabitethernet 1/0/0
[LSRD-GigabitEthernet1/0/0] isis enable 1
[LSRD-GigabitEthernet1/0/0] quit
[LSRD] interface gigabitethernet 2/0/0
[LSRD-GigabitEthernet2/0/0] isis enable 1
[LSRD-GigabitEthernet2/0/0] quit
[LSRD] interface loopback 1
[LSRD-LoopBack1] isis enable 1
[LSRD-LoopBack1] quit
# Configure LSR E.
[LSRE] isis 1
[LSRE-isis-1] network-entity 00.0007.0000.0000.0005.00
[LSRE-isis-1] is-level level-1
[LSRE-isis-1] quit
[LSRE] interface gigabitethernet 1/0/0
[LSRE-GigabitEthernet1/0/0] isis enable 1
[LSRE-GigabitEthernet1/0/0] quit
[LSRE] interface loopback 1
[LSRE-LoopBack1] isis enable 1
[LSRE-LoopBack1] quit
Step 3 Configure basic MPLS functions, enable MPLS TE, RSVP-TE, and enable CSPF on the ingress
of the tunnel.
# Configure LSR A.
[LSRA] mpls lsr-id 1.1.1.1
[LSRA] mpls
[LSRA-mpls] mpls te
[LSRA-mpls] mpls rsvp-te
[LSRA-mpls] mpls te cspf
[LSRA-mpls] quit
[LSRA] interface gigabitethernet 1/0/0
[LSRA-GigabitEthernet1/0/0] mpls
[LSRA-GigabitEthernet1/0/0] mpls te
[LSRA-GigabitEthernet1/0/0] mpls rsvp-te
[LSRA-GigabitEthernet1/0/0] quit
# Configure LSR B.
Issue 02 (2011-09-10)
561
3 MPLS TE Configuration
# Configure LSR C.
[LSRC] mpls lsr-id 3.3.3.3
[LSRC] mpls
[LSRC-mpls] mpls te
[LSRC-mpls] mpls rsvp-te
[LSRC-mpls] quit
[LSRC] interface gigabitethernet 1/0/0
[LSRC-GigabitEthernet1/0/0] mpls
[LSRC-GigabitEthernet1/0/0] mpls te
[LSRC-GigabitEthernet1/0/0] mpls rsvp-te
[LSRC-GigabitEthernet1/0/0] quit
[LSRC] interface pos 2/0/0
[LSRC-Pos2/0/0] mpls
[LSRC-Pos2/0/0] mpls te
[LSRC-Pos2/0/0] mpls rsvp-te
[LSRC-Pos2/0/0] quit
# Configure LSR D.
[LSRD] mpls lsr-id 4.4.4.4
[LSRD] mpls
[LSRD-mpls] mpls te
[LSRD-mpls] mpls rsvp-te
[LSRD-mpls] quit
[LSRD] interface gigabitethernet
[LSRD-GigabitEthernet1/0/0] mpls
[LSRD-GigabitEthernet1/0/0] mpls
[LSRD-GigabitEthernet1/0/0] mpls
[LSRD-GigabitEthernet1/0/0] quit
[LSRD] interface gigabitethernet
[LSRD-GigabitEthernet2/0/0] mpls
[LSRD-GigabitEthernet2/0/0] mpls
[LSRD-GigabitEthernet2/0/0] mpls
[LSRD-GigabitEthernet2/0/0] quit
1/0/0
te
rsvp-te
2/0/0
te
rsvp-te
# Configure LSR E.
[LSRE] mpls lsr-id 5.5.5.5
[LSRE] mpls
[LSRE-mpls] mpls te
[LSRE-mpls] mpls rsvp-te
[LSRE-mpls] quit
[LSRE] interface gigabitethernet 1/0/0
[LSRE-GigabitEthernet1/0/0] mpls
[LSRE-GigabitEthernet1/0/0] mpls te
[LSRE-GigabitEthernet1/0/0] mpls rsvp-te
[LSRE-GigabitEthernet1/0/0] quit
Issue 02 (2011-09-10)
562
3 MPLS TE Configuration
# Configure LSR B.
[LSRB] isis 1
[LSRB-isis-1] cost-style wide
[LSRB-isis-1] traffic-eng level-1-2
[LSRB-isis-1] quit
# Configure LSR C.
[LSRC] isis 1
[LSRC-isis-1] cost-style wide
[LSRC-isis-1] traffic-eng level-2
[LSRC-isis-1] quit
# Configure LSR D.
[LSRD] isis 1
[LSRD-isis-1] cost-style wide
[LSRD-isis-1] traffic-eng level-1-2
[LSRD-isis-1] quit
# Configure LSR E.
[LSRE] isis 1
[LSRE-isis-1] cost-style wide
[LSRE-isis-1] traffic-eng level-1
[LSRE-isis-1] quit
next
next
next
next
hop
hop
hop
hop
10.1.1.2
20.1.1.2
30.1.1.2
40.1.1.2
include
include
include
include
loose
loose
loose
loose
# Configure the maximum bandwidth and the maximum reservable bandwidth for the link on
LSR B.
[LSRB] interface pos 2/0/0
[LSRB-Pos2/0/0] mpls te bandwidth max-reservable-bandwidth 100000
[LSRB-Pos2/0/0] mpls te bandwidth bc0 100000
[LSRB-Pos2/0/0] quit
# Configure the maximum bandwidth and the maximum reservable bandwidth for the link on
LSR C.
[LSRC] interface gigabitethernet 1/0/0
[LSRC-GigabitEthernet1/0/0] mpls te bandwidth max-reservable-bandwidth 100000
[LSRC-GigabitEthernet1/0/0] mpls te bandwidth bc0 100000
[LSRC-GigabitEthernet1/0/0] quit
# Configure the maximum bandwidth and the maximum reservable bandwidth for the link on
LSR D.
[LSRD] interface gigabitethernet 2/0/0
[LSRD-GigabitEthernet2/0/0] mpls te bandwidth max-reservable-bandwidth 100000
Issue 02 (2011-09-10)
563
3 MPLS TE Configuration
# Run the display mpls te tunnel verbose command on LSR A to display information about
the tunnel.
[LSRA] display mpls te tunnel verbose
No
: 1
Tunnel-Name
: Tunnel1/0/0
TunnelIndex
: 0
LSP Index
: 2048
Session ID
: 100
LSP ID
: 1
Lsr Role
: Ingress
Lsp Type
: Primary
Ingress LSR ID
: 1.1.1.1
Egress LSR ID
: 5.5.5.5
In-Interface
: Out-Interface
: GE1/0/0
Sign-Protocol
: RSVP TE
Resv Style
: SE
IncludeAnyAff
: 0x0
ExcludeAnyAff
: 0x0
IncludeAllAff
: 0x0
LspConstraint
: ER-Hop Table Index
: 0
AR-Hop Table Index: C-Hop Table Index
: 0
PrevTunnelIndexInSession: NextTunnelIndexInSession: PSB Handle
: 1024
Created Time
: 2010/09/09 16:40:44 UTC-08:00
-------------------------------DS-TE Information
-------------------------------Bandwidth Reserved Flag : Reserved
CT0 Bandwidth(Kbit/sec) : 20000
CT1 Bandwidth(Kbit/sec): 0
CT2 Bandwidth(Kbit/sec) : 0
CT3 Bandwidth(Kbit/sec): 0
CT4 Bandwidth(Kbit/sec) : 0
CT5 Bandwidth(Kbit/sec): 0
CT6 Bandwidth(Kbit/sec) : 0
CT7 Bandwidth(Kbit/sec): 0
Setup-Priority
: 7
Hold-Priority
: 7
-------------------------------FRR Information
-------------------------------Primary LSP Info
TE Attribute Flag
: 0x3
Protected Flag
: 0x0
Bypass In Use
: Not Exists
Bypass Tunnel Id
: BypassTunnel
: -
Issue 02 (2011-09-10)
564
3 MPLS TE Configuration
Bypass Lsp ID
: FrrNextHop
: ReferAutoBypassHandle
: FrrPrevTunnelTableIndex : FrrNextTunnelTableIndex: Bypass Attribute(Not configured)
Setup Priority
: Hold Priority
: HopLimit
: Bandwidth
: IncludeAnyGroup
: ExcludeAnyGroup
: IncludeAllGroup
: Bypass Unbound Bandwidth Info(Kbit/sec)
CT0 Unbound Bandwidth
: CT1 Unbound Bandwidth: CT2 Unbound Bandwidth
: CT3 Unbound Bandwidth: CT4 Unbound Bandwidth
: CT5 Unbound Bandwidth: CT6 Unbound Bandwidth
: CT7 Unbound Bandwidth: -------------------------------BFD Information
-------------------------------NextSessionTunnelIndex : PrevSessionTunnelIndex: NextLspId
: PrevLspId
: -
----End
Configuration Files
l
Issue 02 (2011-09-10)
565
3 MPLS TE Configuration
Issue 02 (2011-09-10)
566
3 MPLS TE Configuration
mpls te
mpls rsvp-te
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
isis enable 1
#
return
Issue 02 (2011-09-10)
567
3 MPLS TE Configuration
Issue 02 (2011-09-10)
568
Issue 02 (2011-09-10)
569
MPLS Ping/Traceroute
The MPLS Ping and Traceroute help to detect LSP faults and locate the faulty nodes.
Similar to IP Ping and Traceroute, MPLS Ping and Traceroute use the echo request and echo
reply messages to detect the availability of the LSP. Echo request and echo reply messages are
transferred in User Datagram Protocol (UDP) datagram with the port number being 3503.
Issue 02 (2011-09-10)
570
Applicable Environment
MPLS TTL process is related to the following aspects:
l
For details information about HoVPN and SPE, refer to the HUAWEI NetEngine80E/40E Router
Configuration Guide - VPN.
Pre-configuration Tasks
Before configuring the MPLS TTL process mode, complete the following task:
l
Data Preparation
To configure the MPLS TTL process mode, you need the following data.
Issue 02 (2011-09-10)
No.
Data
571
No.
Data
Context
The effect of configuring the MPLS uniform mode and that of configuring the IP TTL copy
function are the same. The TTL of a packet transmitted in an MPLS network decreases by one
at each hop.
Procedure
l
Run:
system-view
Run:
ip vpn-instance vpn-instance-name
Run:
ttl-mode uniform
Context
The effect of configuring the MPLS Pipe mode and that of disabling the MPLS IP TTL
propagation function are the same. That is, when packets pass through an MPLS network, the
ingress and egress are perceived as directly connected. The IP TTL decreases by one only on
the ingress and the egress respectively.
Do as follows on the ingress PE:
Procedure
Step 1 Run:
Issue 02 (2011-09-10)
572
system-view
Context
Do as follows on the ingress PE and the egress PE:
Procedure
Step 1 Run:
system-view
Issue 02 (2011-09-10)
573
Applicable Environment
On an existing MPLS network, devices in the core area support TE and devices in other areas
use LDP. LDP over TE is applied and allows a TE tunnel to function as a hop of an entire LDP
LSP. On MPLS VPNs where LDP is widely used, LDP over TE is used to prevent VPN traffic
congestion on some nodes. If multiple tunnels on a transit node have the same downstream node,
load balancing can be configured on the transit node. This allows each link to carry traffic based
on the proportion of the specific weight to the total weight.
Pre-configuration Tasks
Before configuring load balancing of MPLS Layer 3 forwarding, complete the following tasks:
l
Enabling MPLS
Data Preparation
None.
Context
Do as follows on the transit:
Procedure
Step 1 Run:
system-view
574
If multiple equal-cost links of different bandwidths exist, traffic can be proportionally balanced
over these links. In this manner, all links can transmit traffic in proportion to their bandwidths,
realizing more reasonable load balancing.
Step 3 Run:
load-balance unequal-cost weight
Applicable Environment
MPLS has many basic parameters that can be adjusted in different environments:
l
PHP
The Penultimate Hop Popping (PHP) is configured on the egress. The label is distributed
according to the PHP features that the PHP node supports.
Pre-configuration Tasks
Before adjusting the MPLS parameters, complete the following task:
l
Issue 02 (2011-09-10)
575
Data Preparation
To adjust the MPLS parameters, you need the following data.
No.
Data
Context
Do as follows on the egress:
Procedure
Step 1 Run:
system-view
The modification of the PHP feature takes effect only on the LSP that is set up later than the modification.
----End
576
Context
The relationship between the MPLS MTU and the MTU of an interface is as follows:
l
By default, if the MPLS MTU value is not set, the value of the MPLS MTU is that of the
interface MTU.
If the MPLS MTU value is set, the smaller one between the MPLS MTU value and the
interface MTU value is adopted. If not, the interface MTU value is adopted.
Procedure
Step 1 Run:
system-view
Context
Do as follows on each LSR in an MPLS domain:
Procedure
Step 1 Run:
system-view
577
Prerequisite
The configurations of the optimizing MPLS function are complete.
Procedure
Step 1 Run the display mpls interface [ interface-type interface-number ] [ verbose ] command to
check information about the interface enabled with MPLS.
----End
Example
If the configurations are successful, you can view the following information:
<HUAWEI> display mpls interface
Interface
Status
TE Attr
GE1/0/0
Up
Dis
LSP Count
0
Context
Run the following reset commands in the user view to clear the running information.
Procedure
l
Run reset mpls statistics lsp { lsp-name | all } command to clear LSP statistics.
----End
Context
You can run the following commands in any view to perform MPLS ping and MPLS tracert.
Issue 02 (2011-09-10)
578
Procedure
l
Run:
ping lsp [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m
interval | -r reply-mode | -s packet-size | -t time-out | -v ] * ip destinationaddress mask-length [ ip-address ] [ nexthop nexthop-address | draft6 ]
Run:
tracert lsp [ -a source-ip | -exp exp-value | -h ttl-value | -r reply-mode | t time-out ] * ip destination-address mask-length [ ip-address ] [ nexthop
nexthop-address | draft6 ]
Issue 02 (2011-09-10)
579
Issue 02 (2011-09-10)
580
Performing protection switching in the case of link or node failure to shorten the defect
duration and improves the availability.
For details about requirements for OAM functionality for MPLS networks, refer to the ITU-T
Recommendation Y.1710. For details about OAM mechanism for MPLS networks, refer to the
ITU-T Recommendation Y.1711.
CV
/F
F
D
FF
/
CV
Ingress
Egress
I
BD
BD
I
As shown in Figure 5-1, procedures of MPLS OAM connectivity detection are as follows:
Issue 02 (2011-09-10)
581
1.
The ingress sends a CV or an FFD detection packet to the egress along the LSP to be
detected.
2.
The egress judges whether the received packet is correct by comparing the packet type,
frequency, and TTSI in the received packet with expected values recorded on the egress.
It counts the number of the correct packets and the error packets received within a certain
period, and thus monitors the LSP connectivity.
3.
When the egress detects a defect on the LSP, it analyzes the defect type and sends a
Backward Defect Indication (BDI) () packet carrying the defect information to the ingress
through the backward tunnel. This enables the ingress to know the defect status in real time.
If a protection group has been configured in the correct manner, the corresponding
switching is triggered.
Backward Tunnel
When configuring the basic OAM detection function, bind a backward tunnel to the detected
LSP.
A backward tunnel is an LSP with its ingress and egress being converse to the ingress and egress
of the detected LSP. It also can be a non-MPLS path connected to the ingress and egress of the
detected LSP.
There are three types of backward tunnels:
l
If the OAM function on the LSP ingress starts later than that on the LSP egress, or the
egress is enabled with the OAM function but the ingress is not, the egress generates a Loss
of Connectivity Verification defect (dLOCV) alarm.
If the OAM function is disabled on the ingress whereas is enabled on the egress, the egress
generates a dLOCV alarm .
To modify the type of the detection packet or the frequency at which detection packets are
sent, you must disable the OAM function on the egress and the ingress separately.
OAM parameters need to be configured separately on the ingress and egress. This may
cause the detection packet type and the frequency at which detection packets are sent to be
different on the ingress and egress.
The NE80E/40E uses the OAM auto-protocol to solve problems existing in the ITU-T Y.1710.
The OAM auto-protocol is configured on the egress. It provides functions of initial packet
triggering and dynamic enabling or disabling.
Protection Switching
In protection switching, a protection tunnel (backup tunnel) is set up for the working tunnel
(primary tunnel). A working tunnel and a protection tunnel compose a protection group. When
Issue 02 (2011-09-10)
582
the working tunnel fails, the data flow switches to the protection tunnel; thus improving the
network reliability.
The difference between protection switching and CR-LSP backup are as follows:
l
Protection switching uses one tunnel to protect another tunnel. Attributes of every tunnel
in the tunnel protection group are independent. For example, the protection tunnel with the
bandwidth being 10 Mbit/s can protect the working tunnel that requires 100 Mbit/s
bandwidth protection.
CR-LSP backup has the primary and backup CR-LSPs in the same tunnel group. The
backup CR-LSP protects the primary CR-LSP. Except for TE FRR, attributes of the primary
and backup CR-LSPs, such as the bandwidth, setup priority, and holding priority, are
identical.
Protection Mode
The NE80E/40E supports the following protection switching modes:
l
1:1 protection
One working tunnel and one protection tunnel exist between the ingress and the egress.
Data is generally forwarded through the working tunnel.
When the working tunnel fails, the ingress performs protection switching and switches
the data flow to the protection tunnel for transmission.
N:1 protection
As shown in Figure 5-2, one tunnel provides protection for several working tunnels.
This mode is applicable to a mesh network for saving bandwidth.
Figure 5-2 N:1 protection mode
Working tunnel-1
RouterA
Working tunnel-2
RouterB
Protection tunnel
Backward tunnel
: Traffic of working tunnel-1
: Traffic of working tunnel-2
As shown in Figure 5-3, when one of the working tunnels fails, its traffic switches to the
shared protection tunnel.
Issue 02 (2011-09-10)
583
Working tunnel-1
Working tunnel-2
Ingress
Egress
Protection tunnel
Backward tunnel
: Traffic of Working tunnel-1
: Traffic of Working tunnel-2
: Working tunnel-1 is failed
Applicable Environment
The NE80E/40E provides MPLS OAM to detect the connectivity of an RSVP-TE LSP, a static
CR-LSP, and a static LSP.
To implement MPLS OAM functions, you need to create a backward LSP for bearing BDI
packets. The type of the backward LSP can be different from that of the tested LSP, but the
backward LSP must be bound to a TE tunnel.
Pre-configuration Tasks
Before configuring basic MPLS OAM functions, complete the following tasks:
l
Creating a forward LSP, the LSP to be detected by OAM and is bound to the TE tunnel
If the forward LSP is static and the backward LSP is dynamic, and the backward LSP is in the shared mode,
you must specify lsrid ingress-lsr-id and tunnel-id tunnel-id when running the static-lsp egress command
or the static-cr-lsp egress command to create a forward LSP. For creating the LSP bound to a TE tunnel,
refer to the chapter "MPLS TE Configuration."
Issue 02 (2011-09-10)
584
Data Preparation
To configure basic MPLS OAM functions, you need the following data.
No.
Data
Egress: Number of the tunnel interface that is bound to the backward LSP and the
protection mode
NOTE
l The backward LSP must be specified on the egress; otherwise, BDI packets cannot be correctly sent
to the source end.
l If a shared backward LSP is used, you do not need to specify the backward LSP on the ingress.
Context
Do as follows on the ingress of the LSP:
Procedure
Step 1 Run:
system-view
585
Step 2 Run:
mpls
If the backward LSP is a static LSP or a static CR-LSP, you cannot configure it in private
mode.
If lsrid ingress-lsr-id and tunnel-id tunnel-id are specified when you run the static-lsp
egress lsp-name incoming-interface interface-type interface-number in-label in-label
[ lsrid ingress-lsr-id tunnel-id tunnel-id ] command or the static-cr-lsp egress lsp-name
incoming-interface interface-type interface-number in-label in-label [ lsrid ingress-lsr-id
tunnel-id tunnel-id ] command to create a backward LSP, you can use these two
parametersspecify parameters in this step; otherwise, you can specifyonly the parameter lspname lsp-name.
By default, the type of the detection packet is CV. The frequency at which CV packets are
sent is one second.
Step 6 Run:
mpls oam ingress enable { all | tunnel interface-number }
586
Context
Do as follows on the egress of the LSP:
Procedure
Step 1 Run:
system-view
OAM parameters is configured for the egress when the auto-protocol extension of OAM is
disabled.
If lsrid ingress-lsr-id and tunnel-id tunnel-id are specified when you run the static-lsp egress
lsp-name incoming-interface interface-type interface-number in-label in-label [ lsrid ingresslsr-id tunnel-id tunnel-id ] command or the static-cr-lsp egress lsp-name incominginterface interface-type interface-number in-label in-label [ lsrid ingress-lsr-id tunnel-id
tunnel-id ] command to create a forward tunnel, you can use these two parameters in this step;
otherwise, you can specify only the parameter lsp-name lsp-name.
By default, the auto-protocol function of OAM is enabled. The timeout period for the first packet
to wait for response is five minutes.
By default, the backward LSP is in the shared mode. When the backward LSP is a static LSP or
a CR-LSP, it is in the private mode.
By default, the frequency at which BDI packets are sent through the backward LSP is detectfreq.
Issue 02 (2011-09-10)
587
NOTE
If a shared backward LSP is used to enable the OAM auto-protocol extension in Step 5, Step 6 is not
necessary. When the egress receives the first CV/FFD packet, it automatically records the packet type and
the frequency at which CV/FFD packets are sent, and starts to detect the connectivity.
Step 6 Run:
mpls oam egress enable { all | lsp-name lsp-name | lsr-id ingress-lsr-id tunnel-id
tunnel-id }
Prerequisite
The configurations of basic MPLS OAM functions are complete.
Procedure
l
Run display mpls oam ingress { all | tunnel interface-number } [ slot slot-id | verbose ]
command to view MPLS OAM information on the ingress.
Run display mpls oam egress { all | lsp-name lsp-name | lsr-id ingress-lsr-id tunnel-id
tunnel-id } [ slot slot-id | verbose ] command to view MPLS OAM information on the
egress.
----End
Example
If the configurations succeed, run the commands mentioned above and you can view the
following results:
l
Basic information about the LSP, including the tunnel name, LSP type, LSP ingress LSR
ID, and LSP tunnel ID
Basic information about OAM, including the tunnel name, TTSI, packet type, and
frequency
OAM detection information, including the packet type, frequency at which detection
packets are sent, detection status, and defect status. If the link works properly, the detection
status is Start and the defect status is non-defect
Information about backward LSP, including the sharing mode and configurations of the
backward LSP
588
Applicable Environment
If the tunnel requires high availability, you can configure the MPLS OAM protection switching
to protect the tunnel.
MPLS OAM protection switching enables one tunnel to protect one or multiple tunnels. The
tunnel under protection is a working tunnel, and the tunnel providing protection is a protection
tunnel. A working tunnel and a protection tunnel compose a protection group.
One protection tunnel can protect one or more working tunnels. The protection mechanism in
which one protection tunnel protects only one working tunnel is called 1:1 protection; one
protection tunnel protects two or more working tunnel is called N:1 protection. "N" indicates
the number of the working tunnels in the same protection group. Working tunnels in the same
protection group use the same ingress and egress.
The NE80E/40E supports 1:1 protection and N:1 protection.
l
Issue 02 (2011-09-10)
Switch Request
Order of Priority
Description
Clear
Highest
Signal Fail
589
Switch Request
Order of Priority
Description
Manual Switch
Wait To Restore
No Request
Lowest
Pre-configuration Tasks
Before configuring MPLS OAM protection switching, complete the following tasks:
l
Data Preparation
To configure MPLS OAM protection switching, you need the following data.
No.
Data
Parameters for the protection group, such as the hold off time, revertive mode, and
WTR time
Issue 02 (2011-09-10)
590
Context
Do as follows on the ingress of the tunnel:
Procedure
Step 1 Run:
system-view
Multiplying 100 milliseconds by holdoff-time, you can get the hold-off time.
l Non-revertive mode indicates that traffic does not switch back to the working tunnel even
though the working tunnel recovers.
l Revertive mode indicates that traffic switches back to the working tunnel when the working
tunnel recovers.
By default, the protection group is in revertive mode.
l Wait to Restore time (WTR time) indicates the time to be waited before traffic switching.
The WTR time ranges from 0 to 30 minutes. The default value is 12. The parameter wtrtime indicates the number of steps. The value of each step is 30, in seconds.
NOTE
Multiplying 30 seconds by wtr-time, you can get the value of WTR time.
NOTE
If the number of the working tunnels in the same protection group is N, perform Step 2 and Step 3 for N
times by using different interface-number.
Step 4 Run:
mpls te commit
591
Follow-up Procedure
Configurations described in this section are also applicable in modifying the configuration of
the tunnel protection group.
Besides configuring a tunnel protection group to protect the working tunnel, you can configure
TE FRR on the working tunnel in the protection group to provide dual protection for the working
tunnel. The protection tunnel cannot serve as the working tunnel to be protected by other tunnels.
In addition, the protection tunnel cannot be enabled with TE FRR.
Context
Pay attention to the switch request criteria before configuring the protection switching trigger
mechanism.
Do as follows on the ingress of the tunnel protection group as required:
Procedure
Step 1 Run:
system-view
clear
Step 4 Run:
mpls te commit
592
Context
Before performing the following configurations, configure backward LSPs for the working and
protection tunnels. The working LSP and protection LSP, and their reverse LSPs compose
bidirectional LSPa.
NOTE
The backward LSP must be a static LSP or static CR-LSP. The working LSP and protection LSP can be a
static LSP, static CR-LSP, or RSVP LSP.
It is recommended that the LSP and the backward LSP of a bidirectional LSP be both static LSPs or both
static CR-LSPs; the protection LSP and the backward LSP are all static LSPs or all static CR-LSPs.
On the ingress, the inbound interface of the backward LSP and the outbound interface of the working LSP
or the protection LSP must be the same.
Procedure
l
Enable MPLS OAM to detect the bidirectional LSP of the working tunnel.
Do as follows on the ingress of the working tunnel:
1.
Run:
system-view
Run:
interface tunnel interface-number
Run:
mpls te reverse-lsp lsp-name lsp-name
Run:
mpls te commit
Enable MPLS OAM to detect the bidirectional LSP of the protection tunnel.
Do as follows on the ingress of the protection tunnel:
1.
Run:
system-view
Run:
interface tunnel interface-number
Run:
mpls te reverse-lsp lsp-name lsp-name
Run:
mpls te commit
Issue 02 (2011-09-10)
593
Prerequisite
The configurations of the MPLS OAM protection switching function are complete.
Procedure
l
Run display mpls te protection tunnel { all | tunnel-id | interface tunnel interfacenumber } [ verbose ] command to check information about a tunnel protection group.
----End
Example
After the configuration succeeds, run the preceding commands to view information about the
protection group.
Context
In routine maintenance, you can run the following commands in any view to check the MPLS
OAM operation status.
Procedure
l
Run the display mpls oam egress { all | lsp-name lsp-name | lsr-id ingress-lsr-id tunnelid tunnel-id } [ slot slot-id | verbose ] command to view information about the current
status and configuration of the OAM-enabled LSP on the egress.
Run the display mpls oam ingress { all | tunnel interface-number } [ slot slot-id |
verbose ] command to view information about the MPLS OAM parameters and status of
the LSP on the ingress.
Run the display mpls oam oam-index index-value [ slot slot-id ] command to view
information about parameters and status of MPLS OAM.
----End
Issue 02 (2011-09-10)
594
Context
In routine maintenance, you can run the following commands in any view to check the operating
status of the protection group.
Procedure
l
Run the display mpls te protection tunnel { all | tunnel-id | interface tunnel interfacenumber } [ verbose ] command to view information about the tunnel protection group.
----End
Follow-up Procedure
NOTE
This document takes interface numbers and link types of the NE40E-X8 as an example. In applications,
the actual interface numbers and link types may be different from those used in this document.
Networking Requirements
As shown in Figure 5-4, on an MPLS network, a static LSP along LSR A -> LSR B -> LSR C
is set up.
MPLS OAM is configured to detect the static LSP so that when a connectivity fault occurs, the
egress LSR C can notify the ingress LSR A of the fault.
Issue 02 (2011-09-10)
595
Loopback1
4.4.4.4/32
/0
/0 /24
1
S .1
Loopback1 PO .1.1
1.1.1.1/32 10
P
/0
10 OS
/0 /24
1
.1 2/0
S .2
.4
LSRD
.1 /0
PO .1.1
/2
0
4
1
T
Tu unn
nn el
el- 1/0
id /0
10
0
PO
10 S
.1 1/0
.4
.2 /0 Loopback1
/2
4 3.3.3.3/32
Loopback1
2.2.2.2/32
POS1/0/0
POS2/0/0
10.1.2.2/24
10.1.3.1/24
POS2/0/0
POS2/0/0
LSRB
LSRA 10.1.2.1/24
10.1.3.2/24 LSRC
Tunnel 2/0/0
Tunnel-id 200
Configuration Roadmap
The configuration roadmap is as follows:
1.
2.
3.
4.
Data Preparation
To complete the configuration, you need the following data:
l
IP addresses for interfaces on each LSR, the tunnel interface name, and the tunnel ID
Procedure
Step 1 Configure IP addresses and the routing protocols for interfaces.
According to Figure 5-4, configure IP addresses and masks for interfaces including the loopback
interfaces.
Configure OSPF on all LSRs to advertise routes of their loopback interfaces. The detailed
procedures are not mentioned here.
After the configuration, LSRs can ping each other. Run the display ip routing-table command
on each LSR to display routes to each LSR-ID.
Take the display on LSR A as an example.
Issue 02 (2011-09-10)
596
# Configure LSR A to be the ingress of the static LSP and enable the TE tunnel.
[LSRA] static-lsp ingress tunnel-interface tunnel 2/0/0 destination 3.3.3.3 nexthop
10.1.2.2 out-label 20
# Configure LSR C to be the egress of the static LSP and specify lsr-id and tunnel-id.
<LSRC> system-view
[LSRC] static-lsp egress oamlsp incoming-interface pos 2/0/0 in-label 30 lsrid
1.1.1.1 tunnel-id 200
Issue 02 (2011-09-10)
597
After the configuration, run the display mpls te tunnel-interface command on LSR A, and you
can view that the TE tunnel is Up.
[LSRA] display mpls te tunnel-interface
================================================================
Tunnel2/0/0
================================================================
Tunnel State Desc
: UP
Active LSP
: Primary LSP
Session ID
: 200
Ingress LSR ID
: 1.1.1.1
Egress LSR ID: 3.3.3.3
Admin State
: UP
Oper State
: UP
Primary LSP State
: UP
Main LSP State
: READY
LSP ID : 1
Run the display mpls static-lsp command on LSR A, and you can view that the static LSP
corresponding to Tunnel 2/0/0 is Up.
[LSRA] display
TOTAL
UP
DOWN
Name
Tunnel2/0/0
mpls static-lsp
: 1
STATIC LSP(S)
: 1
STATIC LSP(S)
: 0
STATIC LSP(S)
FEC
I/O Label
3.3.3.3/32
NULL/20
I/O If
-/Pos2/0/0
Stat
Up
# Configure LSR A to be the egress of the static CR-LSP and specify lsr-id and tunnel-id.
[LSRA] static-cr-lsp egress Tunnel1/0/0 incoming-interface pos 1/0/0 in-label 80
lsrid 3.3.3.3 tunnel-id 100
After the configuration, run the display mpls te tunnel-interface command on LSR C, and you
can view that the backward tunnel is Up.
[LSRC] display mpls te tunnel-interface
================================================================
Tunnel1/0/0
================================================================
Tunnel State Desc
: UP
Active LSP
: Primary LSP
Session ID
: 100
Ingress LSR ID
: 3.3.3.3
Egress LSR ID: 1.1.1.1
Admin State
: UP
Oper State
: UP
Primary LSP State
: UP
Main LSP State
: READY
LSP ID : 1
Issue 02 (2011-09-10)
598
Run the display mpls static-cr-lsp command on LSR C, and you can view that the static CRLSR is Up.
[LSRC] display
TOTAL
UP
DOWN
Name
Tunnel1/0/0
mpls static-cr-lsp
: 1
STATIC CRLSP(S)
: 1
STATIC CRLSP(S)
: 0
STATIC CRLSP(S)
FEC
I/O Label
1.1.1.1/32
NULL/70
I/O If
-/Pos1/0/0
Stat
Up
mpls oam
quit
oam ingress Tunnel 2/0/0
oam ingress enable all
# Configure the OAM auto-protocol on LSR C to detect the LSP named oamlsp. The backward
tunnel is the LSP bound to tunnel 1/0/0. It is in the private mode.
[LSRC] mpls oam egress lsp-name oamlsp auto-protocol backward-lsp tunnel 1/0/0
private
After the OAM auto-protocol is configured on the egress, OAM is enabled automatically when
the egress receives the first correct detention packet.
After the configuration, check the MPLS OAM parameters and status of LSPs on LSR A and
LSR C. You can view that both ingress and egress are active in normal detection status.
[LSRA] display mpls oam ingress all verbose
------------------------------------------------------------------------Verbose information about the 1th oam at the ingress
------------------------------------------------------------------------lsp basic information:
oam basic information:
--------------------------------------------------------------------Tunnel-name
: Tunnel2/0/0
Oam-Index
: 256
Lsp signal status
: Up
Oam select board
: 1
Lsp establish type : Static lsp
Enable-state
: Manual enable
Lsp ingress lsr-id : 1.1.1.1
Ttsi/lsr-id
: 1.1.1.1
Lsp tnl-id/Lsp-id
: 200/1
Ttsi/tunnel-id
: 200
oam detect information:
oam backward information:
--------------------------------------------------------------------Type
: CV
Share attribute
: Private
Frequency
: 1 s
Lsp-name
: Tunnel1/0/0
Detect-state
: Start
Lsp ingress lsr-id : 3.3.3.3
Defect-state
: Non-defect
Lsp tnl-id/lsp id
: 100/1
Available-state
: available
Lsp-inLabel
: 80
Unavailable time (s): 0
Lsp signal status
: Up
------------------------------------------------------------------------Total Oam Num:
1
Total Start Oam Num:
1
Total Defect Oam Num:
0
Total Unavaliable Oam Num:
0
[LSRC] display mpls oam egress all verbose
------------------------------------------------------------------------Verbose information about the 1th oam at the egress
------------------------------------------------------------------------lsp basic information:
oam basic information:
Issue 02 (2011-09-10)
599
--------------------------------------------------------------------Lsp name
: oamlsp
Oam-Index
: 256
Lsp signal status
: Up
Oam select board
: 1
Lsp establish type : Static lsp
Enable-state
: -Lsp incoming Label : 30
Auto-protocol
: Enable
Lsp ingress lsr-id : 1.1.1.1
Auto-overtime (s)
: 300
Lsp tnl-id/lsp-id
: 200/1
Ttsi/lsr-id
: 1.1.1.1
Lsp Incoming-int
Pos 2/0/0
Ttsi/tunnel-id
: 200
oam detect information:
oam backward information:
--------------------------------------------------------------------Type
: CV
Tunnel name
: Tunnel1/0/0
Frequency
: 1 s
Share attribute
: Private
Detect-state
: Start
Lsp signal status
: Up
Defect-state
: Non-defect
Bdi-frequency
: Detect-freq
Available state
: Available
Unavailable time (s): 0
------------------------------------------------------------------------Total Oam Num:
1
Total Start Oam Num:
1
Total Defect Oam Num:
0
Total Unavaliable Oam Num:
0
# Run the display mpls oam egress all verbose command on LSR C, and you can view that
LSR C has detected the link fault and changed its status to In-defect.
<LSRC> display mpls oam egress all verbose
------------------------------------------------------------------------Verbose information about the 1th oam at the egress
------------------------------------------------------------------------lsp basic information:
oam basic information:
--------------------------------------------------------------------Lsp name
: oamlsp
Oam-Index
: 256
Lsp signal status
: Up
Oam select board
: 1
Lsp establish type : Static lsp
Enable-state
: -Lsp incoming Label : 30
Auto-protocol
: Enable
Lsp ingress lsr-id : 1.1.1.1
Auto-overtime (s)
: 300
Lsp tnl-id/lsp-id
: 200/1
Ttsi/lsr-id
: 1.1.1.1
Lsp Incoming-int
Pos 2/0/0
Ttsi/tunnel-id
: 200
oam detect information:
oam backward information:
-------------------------------------------------------------------Type
: CV
Tunnel name
: Tunnel1/0/0
Frequency
: 1 s
Share attribute
: Private
Detect-state
: Start
Lsp signal status
: Up
Defect-type
: dLocv
Bdi-frequency
: Detect-freq
Available state
: Unavailable
Unavailable time (s): 0
------------------------------------------------------------------------Total Oam Num:
1
Total Start Oam Num:
1
Total Defect Oam Num:
1
Total Unavaliable Oam Num:
1
----End
Configuration Files
l
Issue 02 (2011-09-10)
600
mpls
mpls te
mpls oam
#
interface Pos1/0/0
link-protocol ppp
ip address 10.1.1.1 255.255.255.0
mpls
mpls te
#
interface Pos2/0/0
link-protocol ppp
ip address 10.1.2.1 255.255.255.0
mpls
mpls te
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
interface Tunnel2/0/0
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 3.3.3.3
mpls te signal-protocol static
mpls te tunnel-id 200
mpls te commit
#
ospf 1
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 10.1.1.0 0.0.0.255
network 10.1.2.0 0.0.0.255
#
static-lsp ingress tunnel-interface Tunnel2/0/0 destination 3.3.3.3 nexthop
10.1.2.2 out-label 20
static-cr-lsp egress tunnel1/0/0 incoming-interface Pos1/0/0 in-label 80
lsrid 3.3.3.3 tunnel-id 1
#
mpls oam ingress Tunnel2/0/0
mpls oam ingress enable Tunnel2/0/0
#
return
Issue 02 (2011-09-10)
601
Issue 02 (2011-09-10)
602
Networking Requirements
As shown in Figure 5-5, on an MPLS network, there are three bidirectional static CR-LSPs
between PE1 and PE2. These bidirectional static CR-LSPs are bound to tunnel 1/0/10, tunnel
1/0/11, and tunnel 1/0/12 respectively. Tunnel 1/0/10 and tunnel 1/0/11 serve as working tunnels.
Tunnel 1/0/12 serves as a protection tunnel.
MPLS OAM protection switching is enabled on the MPLS network. Tunnel 1/0/12 protects
tunnel 1/0/10 and tunnel 1/0/11 simultaneously. When either of the working tunnels (tunnel
1/0/10 and tunnel 1/0/11) fails, traffic on the failed working tunnel switches to the protection
tunnel (tunnel 1/0/12).
Issue 02 (2011-09-10)
603
Loopback1
2.2.2.2 GE2/0/0
10.1.5.2/30
P2
GE1/0/0
10.1.1.2/30
GE1/0/0
10.1.1.1/30
PE1
Loopback1
GE1/0/0 5.5.5.5
10.1.5.1/30
PE2
/0
2/0
E
G
1
GE4/0/0
ack
b
0/0 /30 10.1.6.1/30
op 3.3
/
o
0
3
/
L .3.
GE 1.8.1
4/ 0 / 30
3
.
GE 1.7.2
10
.
0
10 0
/
/0
30
3
.1/ GE1 .8.2/
0
/
7
.
0
.1
2/
30 .1
10
GE .2.2/ 10
.1
10
P1
0
/0
/
0
3/0 .2/30
2/ /30
E
E
G 1.3
G 2.1
GE2/0/0
.
.1.
10
0
/
0
0
1
0
/
10.1.6.2/30
3
/3
GE 1.3.1
.
10
P3
GE4/0/0
GE1/0/0
Loopback1 10.1.4.1/30
1.1.1.1/32
10.1.4.2/30 Loopback1
4.4.4.4/32
Working tunnel-1
Reverse working tunnel-1
Working tunnel-2
Reverse working tunnel-2
Protection tunnel
Reverse protection tunnel
Configuration Roadmap
The configuration roadmap is as follows:
1.
2.
3.
Create three TE tunnel interfaces (tunnel 1/0/10, tunnel 1/0/11 and tunnel 1/0/12) on PE1
and PE2. Two of them serve as working tunnels and the third one serves as a protection
tunnel.
4.
Configure two static CR-LSPs from PE1 to PE2, and bind one of them with tunnel 1/0/10
and bind the other one with tunnel 1/0/12.
5.
6.
Configure three static CR-LSPs from PE2 to PE1, and bind them with tunnel 1/0/10, tunnel
1/0/11 and tunnel 1/0/12 respectively on PE2.
7.
Set OAM parameters and enable MPLS OAM to detect bidirectional LSPs.
Data Preparation
To complete the configuration, you need the following data:
Issue 02 (2011-09-10)
604
Parameters for a protection group, including the delay of the protection switching, revertive
mode, and WTR time
Procedure
Step 1 Configure IP addresses and routing protocols on interfaces.
As shown in Figure 5-5, configure IP addresses and masks for interfaces, including loopback
interfaces.
Configure the OSPF protocol on all LSRs to advertise host routes of their loopback interfaces.
The detailed configuration is not mentioned here.
After the configuration, LSRs can ping the LSR ID of each other.
Step 2 Enable MPLS and MPLS TE globally and on the physical interfaces.
The detailed configuration is not mentioned here.
Step 3 Configure TE tunnel interfaces.
# On PE1 and PE2, configure tunnel 1/0/10 and tunnel 1/0/11 as working tunnels and tunnel
1/0/12 as a protection tunnel. Tunnel 1/0/12 protects tunnel 1/0/10 and tunnel 1/0/11
simultaneously. The signaling protocol of tunnel 1/0/11 is RSVP-TE and the signaling protocol
of tunnel 1/0/10 and tunnel 1/0/12 is CR-Static.
# Configure PE1.
<PE1> system-view
[PE1] interface tunnel1/0/10
[PE1-Tunnel1/0/10] description Working tunnel-1 to PE2
[PE1-Tunnel1/0/10] ip address unnumbered interface loopback 1
[PE1-Tunnel1/0/10] tunnel-protocol mpls te
[PE1-Tunnel1/0/10] destination 5.5.5.5
[PE1-Tunnel1/0/10] mpls te signal-protocol cr-static
[PE1-Tunnel1/0/10] mpls te tunnel-id 1010
[PE1-Tunnel1/0/10] mpls te commit
[PE1-Tunnel1/0/10] quit
[PE1] interface tunnel1/0/11
[PE1-Tunnel1/0/11] description Working tunnel-2 to PE2
[PE1-Tunnel1/0/11] ip address unnumbered interface loopback 1
[PE1-Tunnel1/0/11] tunnel-protocol mpls te
[PE1-Tunnel1/0/11] destination 5.5.5.5
[PE1-Tunnel1/0/11] mpls te signal-protocol rsvp-te
[PE1-Tunnel1/0/11] mpls te tunnel-id 1011
[PE1-Tunnel1/0/11] mpls te commit
[PE1-Tunnel1/0/11] quit
[PE1] interface tunnel1/0/12
[PE1-Tunnel1/0/12] description Protection tunnel to PE2
[PE1-Tunnel1/0/12] ip address unnumbered interface loopback 1
[PE1-Tunnel1/0/12] tunnel-protocol mpls te
[PE1-Tunnel1/0/12] destination 5.5.5.5
[PE1-Tunnel1/0/12] mpls te signal-protocol cr-static
[PE1-Tunnel1/0/12] mpls te tunnel-id 1012
[PE1-Tunnel1/0/12] mpls te commit
[PE1-Tunnel1/0/12] quit
# Configure PE2.
<PE2> system-view
[PE2] interface tunnel1/0/10
[PE2-Tunnel1/0/10] description Working tunnel-1 to PE1
Issue 02 (2011-09-10)
605
Step 4 Configure three static CR-LSPs from PE1 to PE2, and bind them to the tunnel interfaces on PE1.
# Configure PE1.
[PE1] static-cr-lsp ingress tunnel-interface Tunnel1/0/10 destination 5.5.5.5
nexthop 10.1.2.2 out-label 10
[PE1] static-cr-lsp ingress tunnel-interface Tunnel1/0/12 destination 5.5.5.5
nexthop 10.1.4.2 out-label 30
# Configure P1.
<P1> system-view
[P1] static-cr-lsp transit PE1toPE2-2 incoming-interface gigabitethernet2/0/0 inlabel 10 nexthop 10.1.7.1 out-label 11
# Configure P3.
<P3> system-view
[P3] static-cr-lsp transit PE1toPE2-3 incoming-interface gigabitethernet1/0/0 inlabel 30 nexthop 10.1.6.1 out-label 31
# Configure PE2.
[PE2]
label
[PE2]
label
static-cr-lsp egress PE1toPE2-2 incoming-interface gigabitethernet2/0/0 in11 lsrid 1.1.1.1 tunnel-id 1010
static-cr-lsp egress PE1toPE2-3 incoming-interface gigabitethernet4/0/0 in31 lsrid 1.1.1.1 tunnel-id 1012
After the configuration, run the display mpls te tunnel command on PE1 and PE2, and you can
view the created TE tunnel.
Take the display on PE1 as an example.
[PE1] display mpls te tunnel
LSP-Id
Destination
1.1.1.1:1012:1
5.5.5.5
1.1.1.1:1010:1
5.5.5.5
In/Out-If
-/GE4/0/0
-/GE2/0/0
Issue 02 (2011-09-10)
606
# Configure P1.
[P1] mpls
[P1-mpls] mpls rsvp-te
[P1-mpls] mpls te cspf
[P1-mpls] quit
[P1] interface gigabitethernet3/0/0
[P1-GigabitEthernet3/0/0] mpls rsvp-te
[P1-GigabitEthernet3/0/0] quit
[P1] interface gigabitethernet1/0/0
[P1-GigabitEthernet1/0/0] mpls rsvp-te
[P1-GigabitEthernet1/0/0] quit
[P1] ospf 1
[P1-ospf-1] opaque-capability enable
[P1-ospf-1] area 0
[P1-ospf-1-area-0.0.0.0] mpls-te enable
[P1-ospf-1-area-0.0.0.0] quit
[P1-ospf-1] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] mpls rsvp-te
[PE2-mpls] mpls te cspf
[PE2-mpls] quit
[PE2] interface gigabitethernet3/0/0
[PE2-GigabitEthernet3/0/0] mpls rsvp-te
[PE2-GigabitEthernet3/0/0] quit
[PE2] ospf 1
[PE2-ospf-1] opaque-capability enable
[PE2-ospf-1] area 0
[PE2-ospf-1-area-0.0.0.0] mpls-te enable
[PE2-ospf-1-area-0.0.0.0] quit
[PE2-ospf-1] quit
Run the display mpls te tunnel-interface command to view information oabout tunnel 1/0/11.
[PE1] display mpls te tunnel-interface tunnel1/0/11
================================================================
Tunnel1/0/11
================================================================
Tunnel State Desc
: UP
Active LSP
: Primary LSP
Session ID
: 1011
Ingress LSR ID
: 1.1.1.1
Egress LSR ID: 5.5.5.5
Admin State
: UP
Oper State
: UP
Primary LSP State
: UP
Main LSP State
: READY
LSP ID : 1
Step 6 Configure three static CR-LSPs from PE2 to PE1, and bind them to the tunnel interfaces on PE2.
# Configure PE2.
[PE2] static-cr-lsp ingress tunnel-interface Tunnel1/0/10 destination 1.1.1.1
nexthop 10.1.7.2 out-label 11
[PE2] static-cr-lsp ingress tunnel-interface Tunnel1/0/11 destination 1.1.1.1
nexthop 10.1.8.2 out-label 21
Issue 02 (2011-09-10)
607
# Configure P1.
[P1] static-cr-lsp transit PE2toPE1-2 incoming-interface gigabitethernet4/0/0 inlabel 11 nexthop 10.1.2.1 out-label 10
[P1] static-cr-lsp transit PE2toPE1-1 incoming-interface gigabitethernet1/0/0 inlabel 21 nexthop 10.1.3.1 out-label 20
# Configure P2.
<P2> system-view
[P2] static-cr-lsp transit PE2toPE1-3 incoming-interface gigabitethernet2/0/0 inlabel 31 nexthop 10.1.1.1 out-label 30
# Configure PE1.
[PE1]
label
[PE1]
label
[PE1]
label
static-cr-lsp egress PE2toPE1-2 incoming-interface gigabitethernet2/0/0 in10 lsrid 1.1.1.1 tunnel-id 1010
static-cr-lsp egress PE2toPE1-1 incoming-interface gigabitethernet3/0/0 in20 lsrid 1.1.1.1 tunnel-id 1011
static-cr-lsp egress PE2toPE1-3 incoming-interface gigabitethernet1/0/0 in30 lsrid 1.1.1.1 tunnel-id 1012
# Configure PE2.
[PE2] interface tunnel1/0/10
[PE2-Tunnel1/0/10] mpls te reverse-lsp lsp-name PE1toPE2-1
[PE2-Tunnel1/0/10] mpls te commit
[PE2-Tunnel1/0/10] quit
[PE2] interface tunnel1/0/11
[PE2-Tunnel1/0/11] mpls te reverse-lsp lsp-name PE1toPE2-2
[PE2-Tunnel1/0/11] mpls te commit
[PE2-Tunnel1/0/11] quit
[PE2] interface tunnel1/0/12
[PE2-Tunnel1/0/12] mpls te reverse-lsp lsp-name PE1toPE2-3
[PE2-Tunnel1/0/12] mpls te commit
[PE2-Tunnel1/0/12] quit
Issue 02 (2011-09-10)
mpls oam
quit
oam ingress Tunnel1/0/10
oam ingress Tunnel1/0/11
oam ingress Tunnel1/0/12
oam ingress enable all
oam egress lsp-name PE2toPE1-1
oam egress lsp-name PE2toPE1-2
608
# Configure PE2.
[PE2] mpls
[PE2-mpls]
[PE2-mpls]
[PE2] mpls
[PE2] mpls
[PE2] mpls
[PE2] mpls
[PE2] mpls
[PE2] mpls
[PE2] mpls
[PE2] mpls
mpls oam
quit
oam ingress Tunnel1/0/10
oam ingress Tunnel1/0/11
oam ingress Tunnel1/0/12
oam ingress enable all
oam egress lsp-name PE1toPE2-1
oam egress lsp-name PE1toPE2-2
oam egress lsp-name PE1toPE2-3
oam egress enable all
After the configuration, run the display mpls oam ingress all verbose command to view the
MPLS OAM parameters and status of LSPs on PE1 and PE2. You can view that the LSP to be
detected is in the "Non-Defect" state.
Take the display on PE1 as an example.
[PE1] display mpls oam ingress all verbose
-------------------------------------------------------------------------------Verbose information about NO.1 oam at the ingress
-------------------------------------------------------------------------------lsp basic information:
--------------------------------------Tunnel-name
: Tunnel1/0/10
Lsp signal status
: Up
Lsp establish type : Static lsp
Lsp ingress lsr-id : 1.1.1.1
Lsp tnl-id/Lsp-id
: 1010/1
Issue 02 (2011-09-10)
609
-------------------------------------------------------------------------------Total
Total
Total
Total
Oam Num:
Start Oam Num:
Defect Oam Num:
Unavailable Oam Num:
3
3
0
0
# After the configuration, run the display mpls te protection tunnel all command on PEs, and
you can view that interfaces of all tunnels are in the Non-defect state and traffic is forwarded
through the working tunnel.
Take the display on PE1 as an example.
[PE1] display mpls te protection tunnel all
-----------------------------------------------------------------------No. Work-tunnel status /id Protect-tunnel status /id
Switch-Result
-----------------------------------------------------------------------1
non-defect
/1010
non-defect
/1012
work-tunnel
2
non-defect
/1011
non-defect
/1012
work-tunnel
# Run the display mpls te protection binding protect-tunnel command on PEs, and you can
view that tunnel 1/0/12 protects tunnel 1/0/10 and tunnel 1/0/11 simultaneously.
Take the display on PE1 as an example.
[PE1] display mpls te protection binding protect-tunnel 1012
-----------------------------------------------------------------------Binding information of( tunnel id: 1012 )
-----------------------------------------------------------------------Protect-tunnel id
:1012
Issue 02 (2011-09-10)
610
Protect-tunnel name
:Tunnel1/0/12
Maximum number of bound work-tunnels :8
Currently bound work-tunnels
:Total( 2 )
:Tunnel1/0/10
:Tunnel1/0/11
# Run the mpls te protect-switch manual work-lsp command on tunnel 1/0/10 of PE1 to
perform traffic switching.
[PE1] interface tunnel1/0/10
[PE1] mpls te protect-switch manual work-lsp
# Run the display mpls te protection tunnel allcommand on PE1, and you can view that the
Switch-Result of tunnel 1/0/10 is protect-tunnel.
[PE1] display mpls te protection tunnel all
-----------------------------------------------------------------------No. Work-tunnel status /id Protect-tunnel status /id
Switch-Result
-----------------------------------------------------------------------1
non-defect
/1010
non-defect
/1012
protect-tunnel
2
non-defect
/1011
non-defect
/1012
work-tunnel
# Run the shutdown command on the GE 4/0/0 on PE1 to simulate the physical link failure on
the protection tunnel.
[PE1] interface gigabitethernet4/0/0
[PE1-GigabitEthernet4/0/0] shutdown
[PE1-GigabitEthernet4/0/0] quit
# Run the display mpls te protection tunnel all command on PE1, and you can view that the
Protect-tunnel status of tunnel 1/0/10 is in-defect, and the Switch-Result is work-tunnel.
[PE1] display mpls te protection tunnel all
-----------------------------------------------------------------------No. Work-tunnel status /id Protect-tunnel status /id
Switch-Result
-----------------------------------------------------------------------1
non-defect
/1010
in-defect
/1012
work-tunnel
2
non-defect
/1011
non-defect
/1012
work-tunnel
Issue 02 (2011-09-10)
611
NOTE
When all tunnels work properly, and the mpls te protect-switch manual work-lsp command is configured
on the tunnel interface view of the working tunnel, traffic switches to the protection tunnel. In this case, if
the link of the protection tunnel fails, traffic switches back to the working tunnel and the mpls te protectswitch manual work-lsp command on the tunnel interface view of the working tunnel is deleted. That is
because the link failure belongs to signaling failure and the priority of signaling failure is higher than that
of manual switching.
----End
Configuration Files
l
Issue 02 (2011-09-10)
612
#
interface Tunnel1/0/12
description Protection tunnel to PE2
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 5.5.5.5
mpls te signal-protocol cr-static
mpls te tunnel-id 1012
mpls te reverse-lsp lsp-name PE2toPE1-3
mpls te commit
#
ospf 100
opaque-capability enable
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 10.1.1.0 0.0.0.255
network 10.1.2.0 0.0.0.255
network 10.1.3.0 0.0.0.255
network 10.1.4.0 0.0.0.255
mpls-te enable
#
static-cr-lsp ingress tunnel-interface Tunnel1/0/10 destination 5.5.5.5
nexthop 10.1.2.2 out-label 10
static-cr-lsp ingress tunnel-interface Tunnel1/0/12 destination 5.5.5.5
nexthop 10.1.4.2 out-label 30
static-cr-lsp egress PE2toPE1-2 incoming-interface gigabitethernet2/0/0 inlabel 10 lsrid 1.1.1.1 tunnel-id 1010
static-cr-lsp egress PE2toPE1-1 incoming-interface gigabitethernet3/0/0 inlabel 20 lsrid 1.1.1.1 tunnel-id 1011
static-cr-lsp egress PE2toPE1-3 incoming-interface gigabitethernet1/0/0 inlabel 30 lsrid 1.1.1.1 tunnel-id 1012
#
mpls oam ingress Tunnel1/0/10
mpls oam ingress Tunnel1/0/11
mpls oam ingress Tunnel1/0/12
mpls oam ingress enable all
mpls oam egress lsp-name PE2toPE1-1
mpls oam egress lsp-name PE2toPE1-2
mpls oam egress lsp-name PE2toPE1-3
mpls oam egress enable all
#
return
Configuration file of P2
#
sysname P2
#
mpls lsr-id 2.2.2.2
mpls
mpls te
#
interface GigabitEthernet1/0/0
ip address 10.1.1.2 255.255.255.0
mpls
mpls te
#
interface GigabitEthernet2/0/0
ip address 10.1.5.2 255.255.255.0
mpls
mpls te
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
ospf 100
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 10.1.1.0 0.0.0.255
network 10.1.5.0 0.0.0.255
#
Issue 02 (2011-09-10)
613
Configuration file of P1
#
sysname P1
#
mpls lsr-id 3.3.3.3
mpls
mpls te
mpls rsvp-te
mpls te cspf
#
interface GigabitEthernet1/0/0
ip address 10.1.8.2 255.255.255.0
mpls
mpls te
mpls rsvp-te
#
interface GigabitEthernet2/0/0
ip address 10.1.2.2 255.255.255.0
mpls
mpls te
#
interface GigabitEthernet3/0/0
ip address 10.1.3.2 255.255.255.0
mpls
mpls te
mpls rsvp-te
#
interface GigabitEthernet4/0/0
ip address 10.1.7.2 255.255.255.0
mpls
mpls te
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
ospf 100
opaque-capability enable
area 0.0.0.0
network 3.3.3.3 0.0.0.0
network 10.1.1.0 0.0.0.255
network 10.1.2.0 0.0.0.255
network 10.1.7.0 0.0.0.255
network 10.1.8.0 0.0.0.255
mpls-te enable
#
static-cr-lsp transit PE1toPE2-2 incoming-interface gigabitethernet2/0/0 inlabel 10 nexthop 10.1.7.1 out-label 11
static-cr-lsp transit PE2toPE1-2 incoming-interface gigabitethernet4/0/0 inlabel 11 nexthop 10.1.2.1 out-label 10
static-cr-lsp transit PE2toPE1-1 incoming-interface gigabitethernet1/0/0 inlabel 21 nexthop 10.1.3.1 out-label 20
#
return
Configuration file of P3
#
sysname P3
#
mpls lsr-id 4.4.4.4
mpls
mpls te
#
interface GigabitEthernet1/0/0
ip address 10.1.4.2 255.255.255.0
mpls
Issue 02 (2011-09-10)
614
mpls te
#
interface GigabitEthernet2/0/0
ip address 10.1.6.2 255.255.255.0
mpls
mpls te
#
interface LoopBack1
ip address 4.4.4.4 255.255.255.255
#
ospf 100
area 0.0.0.0
network 4.4.4.4 0.0.0.0
network 10.1.4.0 0.0.0.255
network 10.1.6.0 0.0.0.255
#
static-cr-lsp transit PE1toPE2-3 incoming-interface gigabitethernet1/0/0 inlabel 30 nexthop 10.1.6.1 out-label 31
#
return
Issue 02 (2011-09-10)
615
destination 1.1.1.1
mpls te signal-protocol cr-static
mpls te tunnel-id 1011
mpls te protection tunnel 1/0/12 mode revertive wtr 4
mpls te commit
#
interface Tunnel1/0/12
description Protection tunnel to PE1
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 1.1.1.1
mpls te signal-protocol cr-static
mpls te tunnel-id 1012
mpls te reverse-lsp lsp-name PE1toPE2-3
mpls te commit
#
ospf 100
opaque-capability enable
area 0.0.0.0
network 5.5.5.5 0.0.0.0
network 10.1.5.0 0.0.0.255
network 10.1.6.0 0.0.0.255
network 10.1.7.0 0.0.0.255
network 10.1.8.0 0.0.0.255
mpls-te enable
#
static-cr-lsp ingress tunnel-interface Tunnel1/0/10 destination 1.1.1.1
nexthop 10.1.7.2 out-label 11
static-cr-lsp ingress tunnel-interface Tunnel1/0/11 destination 1.1.1.1
nexthop 10.1.8.2 out-label 21
static-cr-lsp ingress tunnel-interface Tunnel1/0/12 destination 1.1.1.1
nexthop 10.1.5.2 out-label 31
static-cr-lsp egress PE1toPE2-2 incoming-interface gigabitethernet2/0/0 inlabel 11 lsrid 1.1.1.1 tunnel-id 1010
static-cr-lsp egress PE1toPE2-3 incoming-interface gigabitethernet4/0/0 inlabel 31 lsrid 1.1.1.1 tunnel-id 1012
#
mpls oam ingress Tunnel1/0/10
mpls oam ingress Tunnel1/0/11
mpls oam ingress Tunnel1/0/12
mpls oam ingress enable all
mpls oam egress lsr-id 1.1.1.1 tunnel-id 1011
mpls oam egress lsp-name PE1toPE2-2
mpls oam egress lsp-name PE1toPE2-3
mpls oam egress enable all
#
return
Issue 02 (2011-09-10)
616
A Glossary
Glossary
Description
A
Administrative group
B
Bandwidth protection
Best-effort path
When both primary and backup CR-LSPs fail, a temporary CRLSP, also called a best-effort path, is set up to protect the traffic.
C
Constraint-based Routed
Label Switched Path
D
Dynamic Bidirectional
Forwarding Detection
Issue 02 (2011-09-10)
617
A Glossary
Glossary
Description
E
Explicit path
Egress
F
Facility backup
Flooding threshold
FTN
G
Graceful Restart
Issue 02 (2011-09-10)
618
A Glossary
Glossary
Description
Hot standby
I
Incoming Label Map
Ingress
Issue 02 (2011-09-10)
Label
Label distribution
Label space
LDP identifier
LDP peer
Link color
Link protection
619
A Glossary
Glossary
Description
LSP tunnel
M
Make-before-break
Merge point
N
NHLFE
Node protection
O
Ordinary backup
Still the ingress LSR is informed that the primary LSP failed, a
backup LSP starts to be established.
P
Point of Local Repair
Pre-emption
Issue 02 (2011-09-10)
620
A Glossary
Glossary
Description
R
Re-optimization
Route pinning
RSVP
RSVP-TE
S
Soft State
Static Bidirectional
Forwarding Detection
An explicit path in which the last hop and the next hop are directly
connected. It can precisely specify the LSRs on the LSP.
Summary Refresh
Issue 02 (2011-09-10)
621
Issue 02 (2011-09-10)
A Glossary
Glossary
Description
TE FRR
Tie-breaking
During the CSPF path computation, if there are several paths with
the same metric, CSPF selects one of them. This process is called
tie-breaking.
Traffic trunk
Tunnel interface
622
This appendix collates frequently used acronyms and abbreviations in this document.
Acronyms and Abbreviations Description
A
AF
Assured Forwarding
AS
Autonomous System
ASIC
ATM
B
BC
Bandwidth Constraint
BDI
BFD
BGP
Issue 02 (2011-09-10)
CE
Customer Edge
CLNP
CMD
CR
Constraint-based Routing
CSPF
CT
Class Type
CV
Connectivity Verification
623
Downstream-on-Demand
DU
Downstream Unsolicited
E
EF
Expedited Forwarding
ER
Explicit Route
ERO
F
FDI
FEC
FF
Fixed-Filter
FFD
FIB
FR
Frame Relay
FRR
Fast ReRoute
FS
Forced Switch
FTN
FEC to NHLFE
G
GR
Graceful Restart
GRE
H
HA
High Availability
HoVPN
Hierarchy of VPN
Issue 02 (2011-09-10)
ICMP
IGP
ILM
624
IP Telecommunication Network
IPX
IS-IS
L
L2TP
LAM
LDP
LER
LFIB
LOM
LoP
Lockout of Protection
LSA
LSP
LSR
M
MA
Management Area
MAM
MD5
Message Digest 5
MP
Merge Point
MPLS
MS
Manual Switch
MTU
N
NHLFE
Issue 02 (2011-09-10)
OAM
OSPF
625
P
PDU
PE
Provider Edge
PHP
PLR
PSB
Q
QoS
Quality of Service
R
RDM
RLSN
RM
Resource Management
RRO
RSB
RSVP
RSVP-TE
RSVP-Traffic Engineering
S
SDH
SE
Shared-Explicit
SF
Signal Fail
SLA
SPF
SPE
Issue 02 (2011-09-10)
TCP
TE
Traffic Engineering
TEDB
626
Type-Length-Value
ToS
Type of Service
TTL
Time To Live
TTSI
U
UDP
V
VCI
VLL
VPI
VPN
W
WTR
Issue 02 (2011-09-10)
Wait To Restore
627