Configuring Static LSPs

Static LSPs Configuration

Contents
6.10.1 Static LSPs Configuration
6.10.1.1 Introduction
6.10.1.1.1 Overview
6.10.1.1.2 Static LSP Features Supported by the ATN 950B
6.10.1.2 Configuring Static LSPs
6.10.1.2.1 Before You Start
6.10.1.2.2 Configuring the LSR ID
6.10.1.2.3 Enabling MPLS
6.10.1.2.4 Configuring the Ingress for a Static LSP
6.10.1.2.5 Configuring the Transit Node for a Static LSP
6.10.1.2.6 Configuring the Egress for a Static LSP
6.10.1.2.7 Checking the Configuration
6.10.1.3 Configuring Static BFD for Static LSP
6.10.1.3.2 Enabling Global BFD Capability
6.10.1.3.3 Configuring BFD with Specific Parameters on Ingress
6.10.1.3.4 Configuring BFD with Specific Parameters on Egress
6.10.1.4 Maintaining Static LSPs
6.10.1.4.1 Checking the LSP Connectivity and Reachability
6.10.1.4.2 Enabling the LSP Trap Function
6.10.1.5 Configuration Examples
file:///G|/ATN%20General/Configuring%20Static%20LSPs.html (1 de 54) [13/11/2016 13:42:22]
6.10.1.5.1 Example for Configuring Static LSPs

6.10.1.5.2 Example for Configuring Static BFD for Static LSP
6.10.1 Static LSPs Configuration

You can set up a static LSP by manually assigning labels to LSRs. The static LSP applies stable, small-scale networks.
Introduction
Labels can be assigned manually to LSRs to establish static LSPs.
Configuring Static LSPs

A static LSP can be established only after each LSR is manually configured.
Configuring Static BFD for Static LSP

This section describes how to configure a static BFD session to monitor static LSPs. By configuring static BFD for
static LSPs, you can monitor the connectivity of static LSPs.
Maintaining Static LSPs

Static LSP maintenance involves deleting MPLS statistics, checking the connectivity or reachability of an LSP,
and configuring the trap function on an LDP LSP.
Configuration Examples
The following sections provide several examples of the static LSP configurations.
Parent topic: MPLS
6.10.1.1 Introduction
Labels can be assigned manually to LSRs to establish static LSPs.
Overview
The static LSP cannot be established using a label distribution protocol but can be established by an administrator.
Static LSPs can be used in stable, small-scaled networks with a simple topology.
Static LSP Features Supported by the ATN 950B

This section describes static LSPs features supported by the ATN 950B. The features include configuring static LSPs
and static BFD for static LSP.
Parent topic: Static LSPs Configuration
6.10.1.1.1 Overview
The static LSP cannot be established using a label distribution protocol but can be established by an administrator.
Static LSPs can be used in stable, small-scaled networks with a simple topology.
When configuring a static LSP, the administrator must manually allocate labels for each LSR ensuring that the value of
the outgoing label of the previous node is equal to the value of the incoming label of the next node. LSRs on the
static LSP cannot detect the changes in other LSRs on the same LSP. Therefore, the static LSP is a local concept.
Static LSPs are set up without using label distribution protocols and do not need to exchange control packets.
Therefore, they consume a few resources and are transmitted on small-scale networks with simple and stable
topology. Static LSPs are not automatically adjusted when the network topology changes. The administrator must
adjust the static LSP according to the network topology.
Parent topic: Introduction
Static LSP Features Supported by the 6.10.1.1.2 ATN 950B

This section describes static LSPs features supported by the ATN 950B. The features include configuring static LSPs
and static BFD for static LSP.
Static LSPs
Static LSPs must be configured manually by an administrator. LSRs on the static LSP cannot detect the changes in
other LSRs on the same LSP. Therefore, the static LSP is a local concept. Static LSPs are not automatically
adjusted when the network topology changes. The administrator must adjust the static LSP according to the
network topology.
Static BFD for Static LSPs

The ATN 950B supports static bidirectional forwarding detection (BFD) for static LSPs. When static BFD monitors
static LSPs that are unidirectional, reverse links can be either IP links or static LSPs.
Parent topic: Introduction
6.10.1.2 Configuring Static LSPs

A static LSP can be established only after each LSR is manually configured.
Before You Start

Before configuring a static LSP, familiarize yourself with the usage scenario, complete the pre-configuration tasks,
and obtain the data required for the configuration.
Configuring the LSR ID

Before enabling MPLS, configure the LSR ID.
Enabling MPLS
MPLS features can be configured only after MPLS is enabled.
Configuring the Ingress for a Static LSP

This section describes how to configure a static LSP on the ingress. Before you set up a static LSP, configure the
ingress manually.
Configuring the Transit Node for a Static LSP

This section describes how to configure a transit node manually for a static LSP.
Configuring the Egress for a Static LSP
This section describes how to configure a static LSP on the egress. Before you set up a static LSP, configure the
egress manually.
Checking the Configuration

After a static LSP is set up, you can view that the static LSP is Up and the route status is Ready.

Before configuring a static LSP, familiarize yourself with the usage scenario, complete the pre-configuration tasks,
and obtain the data required for the configuration.
Usage Scenario
A static LSP works properly only after all the LSRs along the LSP are configured.
Setting up static LSPs does not require the label distribution protocol or the exchange of any control packets.
Therefore, static LSPs consume few resources and can be used on small-scale networks with a simple and
stable topology. Static LSPs are not automatically adjusted when the network topology changes. The administrator
needs to adjust the static LSPs according to the network topology.
Static LSPs and static CR-LSPs share the same label space .
Static LSPs are used over MPLS L2VPNs.
For information about the MPLS L2VPN configuration, see the ATN 950BMulti-service Access
EquipmentConfiguration Guide - VPN.
Pre-configuration Tasks
Before configuring static LSPs, configure a static unicast route or an IGP to connect LSRs at the network layer.
Data Preparation
To configure static LSPs, you need the following data.
No.
Data
Name of the static LSP
Destination address and mask
Value of an incoming or outgoing label on each LSR
Next hop address or outbound interface on the ingress
Inbound interface, next hop address, or outbound interface on a transit node
Inbound interface on the egress
Parent topic: Configuring Static LSPs
6.10.1.2.2 Configuring the LSR ID

Before enabling MPLS, configure the LSR ID.
Context
When configuring an LSR ID, note the following issues:
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.
Using the address of the loopback interface of the LSR as the LSR ID is recommended.
To modify the configured LSR ID, run the undo mpls command in the system view to delete all the MPLS configurations.
Perform the following steps on each LSR in an MPLS domain:
Procedure
1. Run:
system-view
The system view is displayed.
2. Run:
mpls lsr-id lsr-id
The LSR ID of the local node is configured.
lsr-id: A number in dotted decimal notation that identifies an LSR.
6.10.1.2.3 Enabling MPLS

MPLS features can be configured only after MPLS is enabled.
Context
Perform the following steps on each LSR in an MPLS domain:
Procedure
1. Run:
system-view

2. Run:
mpls
MPLS is enabled globally and the MPLS view is displayed.
3. Run:
quit
Return to the system view.
4. Run:
interface interface-type interface-number
The interface to participate in MPLS forwarding is specified.
5. Run:
mpls
MPLS is enabled on the interface.
6.10.1.2.4 Configuring the Ingress for a Static LSP

This section describes how to configure a static LSP on the ingress. Before you set up a static LSP, configure the
ingress manually.
Context
Perform the following steps on the LSR to be configured as the ingress:
Procedure
1. Run:
system-view
2. Run:
static-lsp ingress lsp-name destination ip-address { mask-length
| mask } [ nexthop
next-hop-address [ outgoing-interface interface-type interface-number ] |

outgoing-interface interface-type interface-number nexthop next-hop-address ] outlabel out-label
The LSR is configured as the ingress on the specified LSP.
To modify the destination destination-address, nexthop next-hop-address, outgoing-interface interfacetype interface-number, or out-label out-label, run the static-lsp ingress command to set a new value. There is
no need to run the undo static-lsp ingress command before changing a configured value.
NOTE:
It is recommended to set up a static LSP by specifying a next hop. Ensure that the local routing table contains the
route entries, including the destination IP address and the next hop IP addresses of the LSP to be established.
6.10.1.2.5 Configuring the Transit Node for a Static LSP

This section describes how to configure a transit node manually for a static LSP.
Context
Perform the following steps on the LSR to be configured as a transit node:
Procedure
1. Run:
system-view
2. Run:
static-lsp transit lsp-name incoming-interface interface-type interface-number inlabel in-label [ nexthop next-hop-address [ outgoing-interface interface-type
interface-number ] | outgoing-interface interface-type interface-number nexthop nexthop-address] out-label out-label
The LSR is configured as the transit node on the specified LSP.
To modify the incoming-interface interface-type interface-number, in-label in-label, next-hop-address,
outgoing-interface interface-type interface-number, or out-label out-label, run the static-lsp transit command
to set a new value. There is no need to run the undo static-lsp transit command before changing a configured value.
NOTE:
It is recommended to set up a static LSP by specifying a next hop address. In addition, ensure that the local routing
table contains the route entries, including the destination IP address and the next hop IP address of the LSP to
be established.
6.10.1.2.6 Configuring the Egress for a Static LSP

This section describes how to configure a static LSP on the egress. Before you set up a static LSP, configure the
egress manually.
Context
Perform the following steps on the LSR to be configured as the egress:
Procedure
1. Run:
system-view
2. Run:
static-lsp egress lsp-name incoming-interface interface-type interface-number in-label
in-label [ lsrid ingress-lsr-id tunnel-id tunnel-id ]
The LSR is configured as the egress on the specified LSP.
To modify the incoming-interface interface-type interface-number or in-label in-label or lsrid ingress-lsr-id
tunnel-id tunnel-id, run the static-lsp egress command to set a new value. There is no need to run the undo
static-lsp egress command before changing a configured value.

After a static LSP is set up, you can view that the static LSP is Up and the route status is Ready.
Prerequisites
The configurations of the static LSP function are complete.
Procedure
Run the display mpls static-lsp [ lsp-name ] [ { include | exclude } ip-address mask-length ]
[ verbose ] command to check the static LSP.
Run the display mpls route-state [ vpn-instance vpn-instance-name ] [ { exclude | include } { idle | ready
| settingup } * | destination-address mask-length ] [ verbose ] command to check the LSP route on the ingress.
6.10.1.3 Configuring Static BFD for Static LSP

This section describes how to configure a static BFD session to monitor static LSPs. By configuring static BFD for
static LSPs, you can monitor the connectivity of static LSPs.
Before You Start

Before configuring static BFD for static LSPs, familiarize yourself with the usage scenario, complete the preconfiguration tasks, and obtain the data required for the configuration.
Enabling Global BFD Capability

You can enable BFD globally on both ends of a link to be monitored.
Configuring BFD with Specific Parameters on Ingress

To monitor a static LSP using a static BFD session, configure BFD parameters on the ingress of a static LSP.
Configuring BFD with Specific Parameters on Egress

This section describes how to configure BFD parameters on the egress. Before using a static BFD session to monitor
a static LSP, configure BFD parameters on the egress of the static LSP.
Checking the Configuration

After the configuration of detecting a static LSP through a static BFD session, you can view the BFD configuration,
BFD session information, BFD statistics, and the status of the static LSP.

Before configuring static BFD for static LSPs, familiarize yourself with the usage scenario, complete the preconfiguration tasks, and obtain the data required for the configuration.
Usage Scenario
BFD is used to monitor the connectivity of static LSPs established manually.
NOTE:
When static BFD is being used for a static LSP, you can create a static BFD session for non-host routes.
Static BFD for static LSPs can function properly even if the forward path is an LSP and the reverse path is an IP link.
The forward and reverse paths must be established over the same link. If they use different links and a fault occurs,
BFD cannot identify the faulty path.
Pre-configuration Tasks
Before configuring static BFD for static LSP, configure a static LSP.
NOTE:
For static CR-LSPs bound to an MPLS TE tunnel, BFD is available after it is bound to the MPLS TE tunnel.
Data Preparations
Before configuring static BFD for static LSP, you need the following data.
No.
Data
Name of a static LSP
BFD configuration name
Parameters of the reverse link:
IP link: IP address of egress, outbound interface (optional), and source IP address (optional)
Dynamic LSP: IP address of egress, next hop address of the LSP, and egress (optional)
Static LSP: LSP name
MPLS TE: ID of an MPLS TE tunnel
Local and remote discriminators of a BFD session
Parent topic: Configuring Static BFD for Static LSP
6.10.1.3.2 Enabling Global BFD Capability

You can enable BFD globally on both ends of a link to be monitored.
Context
Perform the following steps on each LSR at both ends of the link to be monitored:
Procedure
1. Run:
system-view
2. Run:
bfd
This node is enabled with the global BFD function. The global BFD view is displayed.
6.10.1.3.3 Configuring BFD with Specific Parameters on Ingress

To monitor a static LSP using a static BFD session, configure BFD parameters on the ingress of a static LSP.
Context
Perform the following steps on the ingress of a static LSP:
Procedure
1. Run:
system-view
2. Run:
bfd cfg-name bind static-lsp lsp-name
The BFD session is bound to the static LSP.
3. Configure the discriminators.
Run:
discriminator local discr-value

The local discriminator is set.
Run:
discriminator remote discr-value
The remote discriminator is set.
4. (Optional) Run:
min-tx-interval interval
The local minimum interval at which BFD packets are sent is set.
The default value is 10 milliseconds.
5. (Optional) Run:
min-rx-interval interval
The local minimum interval at which BFD packets are received is set.
6. (Optional) Run:
detect-multiplier multiplier
The local detection multiplier is set.
The default value is 3.
NOTE:
Actual sending and detection intervals on the local and peer devices are obtained in the following two steps.
a. Calculate the sending and detection intervals based on the configured interval and detection multiplier. The formula is
as follows:
Actual interval at which BFD packets are sent on the local device = MAX {Locally configured interval at which
BFD packets are sent, Remotely configured interval at which BFD packets are received}
Actual interval at which BFD packets are received on the local device = MAX {Remotely configured interval at which
BFD packets are sent, Locally configured interval at which BFD packets are received}
Local detection multiplier = Actual interval at which BFD packets are received on the local device x Configured
BFD detection multiplier on the peer device
For example:
On the local device, the interval at which BFD packets are sent is set to 20 ms, the interval at which BFD packets
are received is set to 80 ms, and the detection multiplier is 4.
On the peer device, the interval at which BFD packets are sent is set to 40 ms, the interval at which BFD packets
are received is set to 240 ms, and the detection multiplier is 2.
Then:
The actual interval at which BFD packets are sent on the local device is 240 ms calculated using the formula MAX {20
ms, 240 ms}, the interval at which BFD packets are received is 80 ms calculated using the formula MAX {40 ms, 80
ms}, and the detection multiplier is 160 ms calculated by 80 ms multiplied by 2.
The actual interval at which BFD packets are sent on the peer device is 80 ms calculated using the formula MAX {40
ms, 80 ms}, the interval at which BFD packets are received is 240 ms calculated using the formula MAX {20 ms, 240
ms}, and the detection multiplier is 960 ms calculated by 240 ms multiplied by 4.
b. Compare sending and detection intervals obtained in step 1 with intervals reported by the device to obtain the
final intervals.
The sending intervals reported by the ATN are 3.3 ms, 10 ms, 20 ms, 50 ms, 100 ms, and 1000 ms, and the
reported detection intervals are 10 ms, 30 ms, 60 ms, 150 ms, 300 ms, and 3000 ms. Compare the intervals obtained
in step 1 with these reported intervals. If the obtained interval falls between two intervals, the final sending interval is
the smaller interval, and the detection interval is the larger interval.
For example,
Based on the intervals obtained in step 1, if the actual sending interval on the local device is 240 ms which is between
100 ms and 1000 ms, the final interval is 100 ms. The actual detection interval is 160 ms which is between 150 ms
and 300 ms, the final detection interval is 300 ms.
Based on the intervals obtained in step 1, if the actual sending interval on the peer device is 80 ms which is between
50 ms and 100 ms, the final sending interval is 50 ms. The actual detection interval is 960 ms which is between 300
ms and 3000 ms, the final detection interval is 3000 ms.
7. Run:
process-pst
If the BFD session status changes, the protection status table is modified.
8. Run:
commit
The configuration is committed.
The BFD session monitors the static LSP as follows:
If the static LSP status goes Up, the BFD session is reestablished.
If the static LSP status goes Down, the BFD session also goes Down.
6.10.1.3.4 Configuring BFD with Specific Parameters on Egress

This section describes how to configure BFD parameters on the egress. Before using a static BFD session to monitor
a static LSP, configure BFD parameters on the egress of the static LSP.
Context
The egress can use an IP link, LSP, or TE tunnel as a reverse tunnel to notify the ingress of a fault. To ensure that
the forward and reverse paths travel through the same link, an LSP is preferentially selected to notify the ingress of
an LSP fault.
Perform the following steps on the egress of an LSP:
Procedure
1. Run:
system-view
2. Configure BFD sessions.
For an IP link, run:

bfd cfg-name bind peer-ip peer-ip [ vpn-instance vpn-instance-name ]
[ interface interface-type interface-number ] [ source-ip source-ip ]
For a dynamic LSP, run:

bfd cfg-name bind ldp-lsp peer-ip ip-address nexthop ip-address [ interface
interface-type interface-number ]
For a static LSP, run:

bfd cfg-name bind static-lsp lsp-name
For an MPLS TE tunnel, run:

bfd cfg-name bind mpls-te interface tunnel interface-number [ te-lsp [ backup ] ]
3. Configure the discriminators.

To set a local discriminator, run:

discriminator local discr-value
To set a remote discriminator, run:

discriminator remote discr-value
4. (Optional) Run:
min-tx-interval interval
The local minimum interval at which BFD packets are sent is set.
5. (Optional) Run:
min-rx-interval interval
The local minimum interval at which BFD packets are received is set.
6. (Optional) Run:
detect-multiplier multiplier
The local detection multiplier is set.
The default value is 3.
7. (Optional) Run:
process-pst
The device is enabled to modify the PST if the BFD session status changes.
If an LSP or a TE tunnel is used as a reverse tunnel to notify the ingress of a fault, you can run this command to allow
the reverse tunnel to switch traffic if the BFD session goes Down. If a single-hop IP link is used as a reverse tunnel,
this command can be configured, because the process-pst command can only be configured for BFD singlelink detection.
8. Run:
commit
The configuration is committed.

After the configuration of detecting a static LSP through a static BFD session, you can view the BFD configuration,
BFD session information, BFD statistics, and the status of the static LSP.
Prerequisites
The configurations of the static BFD for static LSP function are complete.
Procedure
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 mask-length ]
[ verbose ] command to check the status of the static LSP.
6.10.1.4 Maintaining Static LSPs

Static LSP maintenance involves deleting MPLS statistics, checking the connectivity or reachability of an LSP,
and configuring the trap function on an LDP LSP.
Checking the LSP Connectivity and Reachability

You can monitor the connectivity or reachability of an LSP by running the ping or tracert command.
Enabling the LSP Trap Function

By configuring the trap function on an LSP, you can notify the NMS of the changes in the LSP status.
6.10.1.4.1 Checking the LSP Connectivity and Reachability

You can monitor the connectivity or reachability of an LSP by running the ping or tracert command.
Context
You can run the following commands in any view to perform MPLS ping and MPLS tracert.
Procedure
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 ] * ip destination-address mask-length [ ip-address ] [ nexthop nexthop-address | draft6 ] command
to perform MPLS ping.
If draft6 is specified, the command complies with draft-ietf-mpls-lsp-ping-06. By default, the command complies
with RFC 4379.
Run the tracert lsp [ -a source-ip | -exp exp-value | -h ttl-value | -r reply-mode | -t time-out ] * ip destinationaddress mask-length [ ip-address ] [ nexthop nexthop-address | draft6 ] command to perform MPLS tracert.
If draft6 is specified, the command complies with draft-ietf-mpls-lsp-ping-06. By default, the command complies
with RFC 4379.
Parent topic: Maintaining Static LSPs
6.10.1.4.2 Enabling the LSP Trap Function

By configuring the trap function on an LSP, you can notify the NMS of the changes in the LSP status.
Context
Run the following commands in the system view to notify the Network Management System (NMS) of LSP status changes.
Procedure
Run the snmp-agent trap suppress feature-name lsp trap-name { mplsxcup | mplsxcdown }
trap-interval trap-interval [ max-trap-number max-trap-number ] command in the system view to enable the
trap function for the LSP and enable the debugging of excessive mplsxcup or mplsxcdown information.
Parent topic: Maintaining Static LSPs
6.10.1.5 Configuration Examples

The following sections provide several examples of the static LSP configurations.
Example for Configuring Static LSPs

This section provides an example for configuring a static LSP.
Example for Configuring Static BFD for Static LSP

This section provides an example for setting up a static LSP and configuring a static BFD session for detecting the
static LSP.
6.10.1.5.1 Example for Configuring Static LSPs

This section provides an example for configuring a static LSP.
Networking Requirements
As shown in Figure 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 Networking diagram of configuring static LSPs
Configuration Roadmap
The configuration roadmap is as follows:
1. 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.
2. Enable MPLS globally on each LSR.
3. Enable MPLS on the interfaces.
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:
IP addresses of the interfaces, OSPF process ID, and area ID
Name of the static LSP
Outgoing label of the interfaces
Procedure
1. Configure the IP address of each interface.
According to Figure 1, configure the IP address and the mask of the interfaces, including the loopback interface.
The configuration details are not mentioned here.
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] network 1.1.1.9 0.0.0.0
[LSRA-ospf-1-area-0.0.0.0] quit
[LSRA-ospf-1] quit
# Configure LSRB.
[LSRB] ospf 1
[LSRB-ospf-1] area 0
[LSRB-ospf-1-area-0.0.0.0] network 2.2.2.9 0.0.0.0
[LSRB-ospf-1-area-0.0.0.0] quit
[LSRB-ospf-1] quit
# Configure LSRC.
[LSRC] ospf 1
[LSRC-ospf-1] area 0
[LSRC-ospf-1-area-0.0.0.0] network 3.3.3.9 0.0.0.0
[LSRC-ospf-1-area-0.0.0.0] quit
[LSRC-ospf-1] quit
# Configure LSRD.
[LSRD] ospf 1
[LSRD-ospf-1] area 0
[LSRD-ospf-1-area-0.0.0.0] network 4.4.4.9 0.0.0.0
[LSRD-ospf-1-area-0.0.0.0] quit
[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
Destination/Mask
Proto
Routes : 15
Pre
Cost
Flags NextHop
Interface
1.1.1.9/32
Direct 0
127.0.0.1
InLoopBack0
2.2.2.9/32
OSPF
10
10.1.1.2
GE0/3/0
3.3.3.9/32
OSPF
10
10.3.1.2
GE0/3/1
4.4.4.9/32
OSPF
10
10.1.1.2
GE0/3/0
OSPF
10
10.3.1.2
GE0/3/1
10.1.1.0/30
Direct 0
10.1.1.1
GE0/3/0
10.1.1.1/32
Direct 0
127.0.0.1
InLoopBack0
10.1.1.2/32
Direct 0
10.1.1.2
GE0/3/0
10.2.1.0/30
OSPF
10.1.1.2
GE0/3/0
10.3.1.0/30
Direct 0
10.3.1.1
GE0/3/1
10.3.1.1/32
Direct 0
127.0.0.1
InLoopBack0
10.3.1.2/32
Direct 0
10.3.1.2
GE0/3/1
10.4.1.0/30
OSPF
10.3.1.2
GE0/3/1
10
10
127.0.0.0/8
Direct 0
127.0.0.1
InLoopBack0
127.0.0.1/32
Direct 0
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

Destinations : 14
Destination/Mask
Routes : 15
Proto
Pre
Cost
OSPF
10
10.2.1.1
Pos1/0/0
OSPF
10
10.4.1.1
Pos2/0/0
2.2.2.9/32
OSPF
10
10.2.1.1
Pos1/0/0
3.3.3.9/32
OSPF
10
10.4.1.1
Pos2/0/0
4.4.4.9/32
Direct 0
127.0.0.1
InLoopBack0
10.1.1.0/30
OSPF
10.2.1.1
Pos1/0/0
10.2.1.0/30
Direct 0
10.2.1.2
Pos1/0/0
10.2.1.1/32
Direct 0
10.2.1.1
Pos1/0/0
10.2.1.2/32
Direct 0
127.0.0.1
InLoopBack0
10.3.1.0/30
OSPF
10.4.1.1
Pos2/0/0
10.4.1.0/30
Direct 0
10.4.1.2
Pos2/0/0
10.4.1.1/32
Direct 0
10.4.1.1
Pos2/0/0
10.4.1.2/32
Direct 0
127.0.0.1
InLoopBack0
127.0.0.0/8
Direct 0
127.0.0.1
InLoopBack0
127.0.0.1/32
Direct 0
127.0.0.1
InLoopBack0
1.1.1.9/32
10
10
Flags NextHop
Interface
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.
3. Configure the basic MPLS capability on each LSR.
# 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
4. Configure the basic MPLS functions on each interface.
# Configure LSRA.
[LSRA] interface gigabitethernet 0/3/0
[LSRA-GigabitEthernet0/3/0] mpls
[LSRA-GigabitEthernet0/3/0] quit
[LSRA] interface gigabitethernet 0/3/1
[LSRA-GigabitEthernet0/3/1] mpls
[LSRA-GigabitEthernet0/3/1] quit
# Configure LSRB.
[LSRB] interface gigabitethernet 1/0/0

[LSRB-GigabitEthernet1/0/0] mpls
[LSRB-GigabitEthernet1/0/0] quit
[LSRB] interface pos 2/0/0
[LSRB-Pos2/0/0] mpls
[LSRB-Pos2/0/0] quit
# Configure LSRC.
[LSRC] interface gigabitethernet 1/0/0
[LSRC-GigabitEthernet1/0/0] mpls
[LSRC-GigabitEthernet1/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
5. Establish a static LSP from LSRA to LSRD.
# Configure the ingress LSRA.
[LSRA] static-lsp ingress RAtoRD destination 4.4.4.9 32 nexthop 10.1.1.2 out-label 20
# Configure the transit LSRB.
[LSRB] static-lsp transit RAtoRD incoming-interface gigabitethernet 1/0/0 in-label

20 nexthop 10.2.1.2 out-label 40
# Configure the egress LSRD.
[LSRD] static-lsp egress RAtoRD incoming-interface pos 1/0/0 in-label 40
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
RAtoRD
FEC
I/O Label
4.4.4.9/32
I/O If
NULL/20
-/GE0/3/0
Stat
Up
As the LSP is unidirectional, you need to configure a static LSP from LSRD to LSRA.
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
# Configure the transit LSRC.
[LSRC] static-lsp transit RDtoRA incoming-interface pos 2/0/0 in-label 30
nexthop 10.3.1.1 out-label 60
# Configure the egress LSRA.
[LSRA] static-lsp egress RDtoRA incoming-interface gigabitethernet 0/3/1 in-label 60
7. Verify the configuration

# After the configuration, run the ping lsp ip 1.1.1.9 32 on LSRD, and you can view that the LSP is reachable.
Run the display mpls static-lsp or display mpls static-lsp verbose command on the LSRs, and you can
view the status and the detailed information about the static LSP.
Take the output of LSRD as an example.
[LSRD] display mpls static-lsp
TOTAL
: 2
STATIC LSP(S)
UP
: 2
STATIC LSP(S)
DOWN
: 0
STATIC LSP(S)
Name
RAtoRD
RDtoRA
FEC
-/1.1.1.9/32
I/O Label
I/O If
Stat
40/NULL
Pos1/0/0/-
Up
NULL/30
[LSRD] display mpls static-lsp verbose

No
: 1
LSP-Name
: RAtoRD
LSR-Type
: Egress
FEC
: -/-
In-Label
: 40
Out-Label
: NULL
In-Interface
: Pos1/0/0
Out-Interface
: -
NextHop
: -
Static-Lsp Type: Normal

Lsp Status
: Up
No
: 2
LSP-Name
: RDtoRA
-/Pos2/0/0
Up
LSR-Type
: Ingress
FEC
: 1.1.1.9/32
In-Label
: NULL
Out-Label
: 30
In-Interface
: -
Out-Interface
: Pos2/0/0
NextHop
: 10.4.1.1
Static-Lsp Type: Normal

Lsp Status
: Up
Configuration Files
Configuration file of LSRA

#
sysname LSRA
#
mpls lsr-id 1.1.1.9
mpls
#
interface GigabitEthernet0/3/0
undo shutdown
ip address 10.1.1.1 255.255.255.252
mpls
#
undo shutdown
ip address 10.3.1.1 255.255.255.252
mpls
#
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
#
static-lsp ingress RAtoRD destination 4.4.4.9 32 nexthop 10.1.1.2 out-label 20
static-lsp egress RDtoRA incoming-interface GigabitEthernet0/3/1 in-label 60
#
return
Configuration file of LSRB

#
sysname LSRB
#
mpls lsr-id 2.2.2.9
mpls
#
undo shutdown
ip address 10.1.1.2 255.255.255.252
mpls
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 10.2.1.1 255.255.255.252
mpls
#
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 GigabitEthernet1/0/0 in-label 20
#
return
Configuration file of LSRC

#
sysname LSRC
#
mpls lsr-id 3.3.3.9
mpls
#
undo shutdown
ip address 10.3.1.2 255.255.255.252
mpls
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 10.4.1.1 255.255.255.252
mpls
#
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
#
static-lsp transit RDtoRA incoming-interface Pos2/0/0 in-label 30 nexthop 10.3.1.1
out-label 60
#
return
Configuration file of LSRD
#
sysname LSRD
#
mpls lsr-id 4.4.4.9
mpls
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.2.1.2 255.255.255.252
mpls
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 10.4.1.2 255.255.255.252
mpls
#
interface LoopBack1
ip address 4.4.4.9 255.255.255.255
#
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
#
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
Parent topic: Configuration Examples
6.10.1.5.2 Example for Configuring Static BFD for Static LSP

This section provides an example for setting up a static LSP and configuring a static BFD session for detecting the
static LSP.
Networking Requirements
As shown in Figure 1:
PE1, PE2, P1, and P2 are in one MPLS domain.
A static LSP is set up along the path PE1 -> P1 ->PE2.
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 Networking diagram of configuring static BFD for static LSP
Configuration Roadmap
The configuration roadmap is as follows:
1. The entire MPLS domain applies OSPF protocol and IP route is accessible to each LSR.
2. Configure the BFD session on PE1 to detect the static LSP.
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:
IP addresses of the interfaces on each LSR
OSPF process number
BFD session parameters, such as configuration name, minimum detection interval between sending and receiving packets
Procedure
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, 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
Destinations : 14
Destination/Mask
Proto
Routes : 15
Pre
Cost
Flags NextHop
Interface
1.1.1.1/32
Direct 0
127.0.0.1
InLoopBack0
2.2.2.2/32
OSPF
10
10.1.1.2
GE0/3/0
3.3.3.3/32
OSPF
10
10.1.2.2
GE0/3/1
4.4.4.4/32
OSPF
10
10.1.1.2
GE0/3/0
OSPF
10
10.1.2.2
GE0/3/1
10.1.1.1
GE0/3/0
10.1.1.0/24
Direct 0
10.1.1.1/32
Direct 0
127.0.0.1
InLoopBack0
10.1.1.2/32
Direct 0
10.1.1.2
GE0/3/0
10.1.2.0/24
Direct 0
10.1.2.1
GE0/3/1
10.1.2.1/32
Direct 0
127.0.0.1
InLoopBack0
10.1.2.2/32
Direct 0
10.1.2.2
GE0/3/1
10.1.4.0/24
OSPF
10
10.1.2.2
GE0/3/1
10.1.5.0/24
OSPF
10
10.1.1.2
GE0/3/0
127.0.0.0/8
Direct 0
127.0.0.1
InLoopBack0
127.0.0.1/32
Direct 0
127.0.0.1
InLoopBack0
2. Enable the MPLS and BFD functions on each LSR.

# Enable MPLS on PE1 globally and enable MPLS on each interface.
<PE1> system-view
[PE1] mpls lsr-id 1.1.1.1
[PE1] mpls
[PE1-mpls] quit
[PE1]interface gigabitethernet 0/3/0
[PE1-GigabitEthernet0/3/0] mpls
[PE1-GigabitEthernet0/3/0] quit
[PE1] interface gigabitethernet 0/3/1
[PE1-GigabitEthernet0/3/1] mpls
[PE1-GigabitEthernet0/3/1] quit
# Enable BFD on PE1 globally.
[PE1] bfd
[PE1-bfd] quit
Repeat preceding steps on PE2, P1, and P2.
3. Create a static LSP with PE1 being the ingress and PE2 being the egress.
# Configure a static LSP on PE1 (ingress) named 1to4.
<PE1> system-view
[PE1] static-lsp ingress 1to4 destination 4.4.4.4 32 nexthop 10.1.1.2 out-label 20
# Configure a static LSP on P1 (transit).
[P1] static-lsp transit 1to4 incoming-interface gigabitethernet 1/0/0 in-label 20
# Configure a static LSP on PE2 (egress).
[PE2] static-lsp egress 1to4 incoming-interface pos 1/0/0 in-label 30
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.
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> system-view
[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
# Configure the BFD session on PE2 (egress) that advertises the static LSP failure through the IP route.
<PE2> system-view
[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
# 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
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
Bind Interface
: --
FSM Board Id
Min Tx Interval (ms)
: 2
LSP Token
: 0x1002000
: 1
TOS-EXP
: 7
: 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
Destination Port
Proc Interface Status
: Disable
: 3784
: Disable
Acl Number
TTL
Process PST
: : 1
: Enable
WTR Interval (ms)
: -
Local Demand Mode
: Disable
Active Multi
: 3
Local Demand Mode
: Disable
Last Local Diagnostic
: Neighbor Signaled Session Down(Receive AdminDown)
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 : 1/0

# Run the display bfd session all verbose command on PE2, and you can view the output of configuration.
-------------------------------------------------------------------------------Session MIndex : 256
(Multi Hop) State : Up
Name : 4to1
: 2
Session Detect Mode
BFD Bind Type
: Peer Ip Address
Bind Session Type
: Static
: 1.1.1.1
NextHop Ip Address
: 10.1.4.2
Bind Interface
: --
FSM Board Id
: 1
TOS-EXP
: 7
: 10
: 10

: 1
Local Detect Multi
: 3
: 30
Echo Passive
: Disable
: Disable
Acl Number
Process PST
: : Disable
WTR Interval (ms)
: -
Local Demand Mode
: Disable
Active Multi
: 3
Local Demand Mode
: Disable
: Control Detection Time Expired
Bind Application
: No Application Bind
Session TX TmrID
: --
: --
Session Init TmrID
: --
Session WTR TmrID
: --
: -
PDT Index
: FSM-0|RCV-0|IF-0|TOKEN-0
Session Description
: -

5. Verify the configuration.
# Shut down POS 1/0/2 of P1 to simulate a static LSP failure.
<P1> system-view
[P1] interface pos 1/0/2
[P1-Pos1/0/2] shutdown
# Run the display bfd session all verbose command, and you can view the BFD status.
-------------------------------------------------------------------------------Session MIndex : 256
(Multi Hop) State : Down
Name : 4to1
-------------------------------------------------------------------------------file:///G|/ATN%20General/Configuring%20Static%20LSPs.html (46 de 54) [13/11/2016 13:42:23]
Local Discriminator
: 2
Session Detect Mode
BFD Bind Type
: Peer Ip Address
Bind Session Type
: Static
: 1.1.1.1
Bind Interface
: -
FSM Board Id
: 1
: 10
TOS-EXP
: 1
: 7
: 10
Local Detect Multi
: 3
: 30
Echo Passive
: Disable
: Disable
Acl Number
Process PST
: : Disable
WTR Interval (ms)
: -
Local Demand Mode
: Disable
Active Multi
: 3
Local Demand Mode
: Disable
Bind Application
: No Application Bind
Session TX TmrID
: --
: --
Session Init TmrID
: --
Session WTR TmrID
: --
: -
PDT Index
: FSM-0|RCV-0|IF-0|TOKEN-0
Session Description
: -

--------------------------------------------------------------------------------
Session MIndex : 256
(One Hop) State : Down
Name : 1to4
: 1
: 2
Session Detect Mode
BFD Bind Type
: STATIC_LSP
Bind Session Type
: Static
: 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
: 10
: 10
Local Detect Multi
: 3
: 3000
Echo Passive
Destination Port
: Disable
: 3784
: Disable
Acl Number
TTL
Process PST
: : 1
: Enable
WTR Interval (ms)
: -
Proc interface status
: Disable
Active Multi
: 3
Local Demand Mode
: Disable
Bind Application
: LSPM OAM_MANAGER
Session TX TmrID
: --
: --
Session Init TmrID
: --
Session WTR TmrID
: --
: -
PDT Index
: FSM-B030000 | RCV-2 | IF-B030000 | TOKEN-0
Session Description
: -
Configuration Files
Configuration file of PE1

#
sysname PE1
#
mpls lsr-id 1.1.1.1
mpls
#
bfd
#
undo shutdown
ip address 10.1.1.1 255.255.255.0
mpls
#
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
Configuration file of PE2

#
sysname PE2
#
mpls lsr-id 4.4.4.4
mpls
#
bfd
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.5.1 255.255.255.0
mpls
#
interface Pos1/0/1
link-protocol ppp
undo shutdown
ip address 10.1.4.1 255.255.255.0
mpls
#
interface NULL0
#
interface LoopBack1
ip address 4.4.4.4 255.255.255.255
#
bfd 4to1 bind peer-ip 1.1.1.1
discriminator local 2
discriminator remote 1
min-tx-interval 10
min-rx-interval 10
commit
#
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.5.0 0.0.0.255
#
static-lsp egress 1to4 incoming-interface Pos1/0/0 in-label 30
#
user-interface con 0
user-interface vty 0 4
#
Return
Configuration file of P1
#
sysname P1
#
mpls lsr-id 2.2.2.2
mpls
#
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 GigabitEthernet1/0/0 in-label 20
#
return
Configuration file of P2
#
sysname P2
#
mpls lsr-id 3.3.3.3
mpls
#
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
Parent topic: Configuration Examples

Configuring Static LSPs

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Configuring Static LSPs

Uploaded by

Copyright:

Available Formats

Static LSPs Configuration

Static LSPs Configuration

Static LSPs Configuration

6.10.1.5.1 Example for Configuring Static LSPs

6.10.1 Static LSPs Configuration