01-07 Seamless MPLS Configuration

S1720&S2700&S5700&S6720 Series Ethernet Switches
Configuration Guide - MPLS 7 Seamless MPLS Configuration
7 Seamless MPLS Configuration
About This Chapter
This chapter describes how to configure seamless Multiprotocol Label Switching (MPLS).
Seamless MPLS can be used to deploy a complete Label Switched Path (LSP) between the
access, aggregation, and core layers to implement end-to-end service interworking.
7.1 Overview
7.2 Principles
7.3 Applications
7.4 Configuration Notes
7.5 Configuring Intra-AS Seamless MPLS
7.6 Configuring Inter-AS Seamless MPLS
7.7 Configuring Dynamic BFD to Monitor a BGP Tunnel
BFD for BGP tunnel rapidly detects faults in E2E BGP tunnels.
7.8 Maintaining Seamless MPLS
The seamless MPLS maintenance involves checking the connectivity and reachability of
seamless MPLS networks.
7.9 Configuration Examples
7.10 References
Issue 03 (2017-07-27) Huawei Proprietary and Confidential 617

Copyright Huawei Technologies Co., Ltd.
7.1 Overview
Definition
Seamless Multiprotocol Label Switching (MPLS) is a bearer technology that extends MPLS
to access networks. Seamless MPLS establishes an end-to-end label switched path (E2E LSP)
across the access, aggregation, and core layers. All services can be encapsulated using MPLS
at the access layer and transmitted along the E2E LSP across the three layers.
Purpose
Seamless MPLS was developed out of a need for greater flexibility in scenarios where
traditional MPLS overcomplicates network management. Traditional MPLS can converge
multiple networks on an Ethernet-based infrastructure, which fully exerts the advantages of a
single-forwarding model and reduces network construction costs. MPLS has been widely used
on aggregation and core networks.
Many service providers use MPLS-based L3VPN/L2VPN solutions to construct a multi-

service bearer network. A multi-service bearer network is deployed in a three layer hierarchy
consisting of an access layer, aggregation layer, and core layer. Service packets that have been
encapsulated and transmitted over a VPN tunnel can be sent only within one layer. To
transmit service packets from one layer to another, the VPN service needs to be terminated.
The device then needs to obtain the original packets and add VLAN or QinQ tags to the
packets before sending the packets to another layer, where the packets are encapsulated and
transmitted over VPN within the destination layer. This hierarchical deployment requires
greater cooperation between different layers, makes network and service expansion more
difficult, and increases operation costs for service providers.
Using the Internet Protocol (IP) to forward packets at the access layer, will result in low
forwarding efficiency. Because complicated VLAN configurations are required to associate
with devices at the aggregation and core layers, using IP to forward packets at the access layer
results in poor service scalability. To solve the preceding issue, seamless MPLS was
developed to extend MPLS to the access layer when used with MPLS-capable devices with
higher performance.
Seamless MPLS is not an entirely new technology. It uses mature BGP, IGP, and MPLS
technologies to establish an E2E LSP across the access, aggregation, and core layers,
implementing MPLS-based service forwarding on the entire network.
Benefits
Seamless MPLS provides the following advantages:
l Helps ease communication between the access, aggregation, and core layers on an MPLS
network.
l Simplifies network provisioning, operations, and maintenance because the technology
encapsulates all services and transmits these services along an E2E LSP.
l Has high deployment flexibility and scalability. On a seamless MPLS network, an LSP
between any two nodes can be established to roll out services.

7.2 Principles
Seamless MPLS deploys a Border Gateway Protocol (BGP) LSP across the access,
aggregation, and core layers to implement end-to-end service transmission through a tunnel.
An LSP can be established between any two nodes on a seamless MPLS network to transmit
service packets upstream and downstream. This network architecture ensures high service
scalability, while only needing to deploy signaling protocols at service access points.
Seamless MPLS supports the following three networking solutions:
l Intra-AS Seamless MPLS: The access, aggregation, and core layers are within a single
AS. Intra-AS seamless MPLS applies to mobile bearer networks.
l Inter-AS Seamless MPLS: The access and aggregation layers are within a single AS,
and the core layer is in another AS. Inter-AS seamless MPLS transmits enterprise
services.
Intra-AS Seamless MPLS

l Control plane
Deploy routing protocols.
In Figure 7-1, routing protocol deployment on devices is as follows:
n An IGP (IS-IS or OSPF) is enabled on devices at each of the access,
aggregation, and core layers to implement intra-AS connectivity.
n For example, the path CSG1 -> AGG1 -> core ABR1 -> MASG1 is used. An
IBGP peer relationship is established between each pair of the following
devices:
CSG and AGG
AGG and core ABR
Core ABR and MASG
The AGG and core ABR are configured as RRs so that the CSG and MASG
can obtain routes destined for each other's loopback addresses.
n The AGG and core ABR set the next hop addresses in BGP routes to their own
addresses to prevent advertising unnecessary IGP area-specific public routes.
Figure 7-1 Deploying routing protocols for the intra-AS seamless MPLS
networking
Single AS
IBGP IBGP IBGP

OSPF/ OSPF/ OSPF/
IS-IS IS-IS IS-IS
CSG1 AGG1 Core ABR1 MASG1
NodeB/
eNodeB Aggregation
Access Core
MME/
SGW
NodeB/
eNodeB

Deploy tunnels.
In Figure 7-2, tunnel deployment is as follows:
n A public network tunnel is established using LDP in each IGP area.
n For example, the path CSG1 -> AGG1 -> core ABR1 -> MASG1 is used. An
IBGP peer relationship is established between each pair of the following
devices:
CSG and AGG
AGG and core ABR
Core ABR and MASG
These devices are enabled to advertise labeled routes and assign labels to BGP
routes that match a specified routing policy. After the devices exchange
labeled BGP routes, an E2E BGP LSP between the CSG and MASG is
established.
Figure 7-2 Deploying tunnels for the intra-AS seamless MPLS networking
Single AS
IBGP label IBGP label IBGP label
NodeB/
eNodeB Aggregation
Access Core
MME/
SGW
NodeB/
eNodeB
MPLS LDP MPLS LDP MPLS LDP
l Forwarding plane
Figure 7-3 illustrates the forwarding plane of the intra-AS seamless MPLS networking.
Seamless MPLS primarily transmits VPN packets. The following example demonstrates
how VPN packets, including labels and data, are transmitted from a CSG to an MASG
along the path CSG1 -> AGG1 -> core ABR1 -> MASG1. The process is as follows:
a. The CSG adds a BGP label and an MPLS tunnel label in sequence to each VPN
packet and forwards the packets to the AGG.
b. The AGG removes the access-layer MPLS tunnel labels from the packets and swaps
the existing BGP labels for new labels. The AGG adds an aggregation-layer MPLS
tunnel label to each packet. The AGG then forwards packets to the core ABR. If the
penultimate hop popping (PHP) function is enabled on the AGG, the CSG has
removed the MPLS tunnel labels from the packets, and therefore, the AGG receives
packets without MPLS tunnel labels.
c. The core ABR removes aggregation-layer MPLS tunnel labels from the VPN
packets and swaps the existing BGP labels for new labels. The AGG adds a core-
layer MPLS tunnel label to each packet. It then forwards the packets to the MASG.

d. The MASG removes MPLS tunnel labels and BGP labels from the VPN packets. If
the PHP function is enabled on the MASG, the core ABR has removed the core-
layer MPLS tunnel labels from the packets; therefore, the MASG receives packets
without MPLS tunnel labels. The VPN packet transmission along the intra-AS
seamless MPLS tunnel is complete.
Figure 7-3 Forwarding plane for the intra-AS seamless MPLS networking
NodeB/
eNodeB Aggregation
Access Core
MME/
SGW
NodeB/
eNodeB
VPN
MPLS tunnel label BGP label
Inter-AS Seamless MPLS

l Control plane
Deploy routing protocols.
In Figure 7-4, routing protocol deployment on devices is as follows:
n An IGP (IS-IS or OSPF) is enabled on devices at each of the access,
aggregation, and core layers to implement intra-AS connectivity.
n For example, the path CSG1 -> AGG1 -> AGG ASBR1 -> core ASBR1 ->
MASG1 is used. A BGP peer relationship is established between each pair of
the following devices:
CSG and AGG
AGG and AGG ASBR
AGG ASBR and core ASBR
Core ASBR and MASG
An EBGP peer relationship between the AGG ASBR and core ASBR is
established, and IBGP peer relationships between other devices are
established.
n The AGG is configured as an RR so that IBGP peers can exchange BGP
routes, and the CSG and MASG can obtain BGP routes destined for each
other's loopback addresses.

n If the AGG ASBR and core ASBR are indirectly connected, an IGP neighbor
relationship between them must be established to implement inter-area
connectivity.
Figure 7-4 Deploying routing protocols for the inter-AS seamless MPLS
networking
AS x AS y
IBGP IBGP EBGP IBGP

OSPF/ OSPF/ OSPF/
IS-IS IS-IS IS-IS
CSG1 AGG1 AGG ASBR1 Core ASBR1 MASG1
NodeB/
eNodeB Access Aggregation Core
MME/
SGW
NodeB/
eNodeB
Deploy tunnels.
In Figure 7-5, tunnel deployment is as follows:
n A public network tunnel is established using LDP in each IGP area.
n The CSG, AGG, AGG ASBR, and core ASBR are enabled to advertise labeled
routes and assign labels to BGP routes that match a specified routing policy.
After the devices exchange labeled BGP routes, a BGP LSP between the CSG
and core ASBR is established.
n Either of the following tunnel deployment methods in the core area can be
used:
A BGP LSP between the core ASBR and MASG is established. This BGP
LSP and the BGP LSP between the CSG and core ASBR are combined
into an E2E BGP LSP. The route to the MASG's loopback address is
installed into the BGP routing table and advertised to the core ASBR
using the IBGP peer relationship. The core ASBR assigns a label to the
route and advertises the labeled route to the AGG ASBR.
No BGP LSP between the core ASBR and MASG is established. The
core ASBR runs an IGP to learn the route destined for the MASG's
loopback address and installs the route to the routing table. The core
ASBR assigns a BGP label to the route and associates the route with an
intra-AS tunnel. The BGP LSP between the CSG and core ASBR and the
MPLS tunnel in the core area are combined into an E2E tunnel.

Figure 7-5 Deploying tunnels for the inter-AS seamless MPLS networking
AS x AS y
IBGP IBGP EBGP IBGP

label label label label
NodeB/
MME/
SGW
NodeB/
eNodeB
MPLS LDP MPLS LDP MPLS LDP
l Forwarding plane
Figure 7-6 illustrates the forwarding plane of the inter-AS seamless MPLS networking
with a core-layer BGP LSP established. Seamless MPLS primarily transmits VPN
packets. The following example demonstrates how VPN packets, including labels and
data, are transmitted from a CSG to an MASG along the path CSG1 -> AGG1 -> AGG
ASBR1 -> core ASBR1 -> MASG1.
a. The CSG adds a BGP label and an MPLS tunnel label in sequence to each VPN
packet and forwards the packets to the AGG.
b. The AGG removes the access-layer MPLS tunnel labels from the packets and swaps
the existing BGP labels for new labels. The AGG adds an aggregation-layer MPLS
tunnel label to each packet. The AGG then forwards the packets to the AGG ASBR.
If the PHP function is enabled on the AGG, the CSG has removed the MPLS tunnel
labels from the packets; therefore, the AGG receives packets without MPLS tunnel
labels.
c. The AGG ASBR then removes the MPLS tunnel labels from the packets and swaps
the existing BGP label for a new label in each packet. It then forwards the packets
to the core ASBR. If the PHP function is enabled on the AGG ASBR, the AGG has
removed the MPLS tunnel labels from the packets, and therefore, the AGG ASBR
receives packets without MPLS tunnel labels.
d. After the core ASBR receives the packets, it swaps a BGP label for a new label and
adds a core-layer MPLS tunnel label to each packet. It then forwards the packets to
the MASG.
e. The MASG removes MPLS tunnel labels, BGP labels, and VPN labels from the
packets. If the PHP function is enabled on the MASG, the core ASBR has removed
the MPLS tunnel labels from the packets; therefore, the MASG receives packets
without MPLS tunnel labels. The VPN packet transmission along the inter-AS
seamless MPLS tunnel is complete.

Figure 7-6 Forwarding plane for the inter-AS seamless MPLS networking with a BGP
LSP established in the core area
NodeB/
MME/
SGW
NodeB/
eNodeB
VPN
Figure 7-7 illustrates the forwarding plane for the inter-AS seamless MPLS networking
without a BGP LSP established in the core area. The process of transmitting packets on
this network is similar to that on the network with a BGP LSP established. The
difference is that without a BGP LSP in the core area, the core ASBR only removes BGP
labels from packets, while adding MPLS tunnel labels to these packets.
Figure 7-7 Forwarding plane for the inter-AS seamless MPLS networking without a
BGP LSP established in the core area
NodeB/
MME/
SGW
NodeB/
eNodeB
VPN

7.3 Applications
7.3.1 Application of Seamless MPLS in VPN
Because MPLS technologies see widespread use, many service providers use MPLS-based
L3VPN/L2VPN solutions to construct a multi-service bearer network. To allow service
providers to quickly provision services over the bearer network and reduce their service
deployment costs to improve market competitiveness, seamless MPLS establishes an end-to-
end LSP across the access, aggregation, and core layers, implementing MPLS-based service
forwarding on the entire network.
Figure 7-8 shows a long term evolution (LTE) network. The access, aggregation, and core
layers of this network belong to two ASs. Different VPN instances are configured for
different services on the CSG and MASG to connect them to NodeB (WCDMA 3G site)/
eNodeB (LTE site) and Mobility Management Entity (MME)/Service Gateway (SGW)
respectively.
To transmit VPN services on the network, the inter-AS seamless MPLS solution establishes
an LSP between the CSG and MASG to implement interworking between NodeB/eNodeB
and MME/SGW. If the low performance CSG cannot meet the network requirements,
configuring HVPN between the CSG and AGG helps to reduce the load of the CSG. As a
result, there is no need to replace the CSG with a higher performance device, lowering the
networking cost.
Figure 7-8 Application of the seamless MPLS networking
AS x AS y
NodeB/e
NodeB Access Aggregation Core
MME/
SGW
NodeB/ LSP
eNodeB
7.4 Configuration Notes

Involved Network Elements
Other network elements are not required.
License Support
Seamless MPLS is a basic feature of a switch and is not under license control.

Version Support
Table 7-1 Products and versions supporting seamless MPLS
Produc Product Model Software Version

t
S1700 S1720GFR, S1720GW-E, S1720GWR-E, Not supported

S1720X-E
S2700 S2700SI, S2700EI, S2710SI, S2720EI, S2750EI, Not supported
S3700 S3700SI, S3700EI, S3700HI Not supported
S5700 S5700LI, S5700S-LI, S5710-C-LI, S5710-X-LI, Not supported

S5700SI, S5700EI, S5710EI, S5720LI, S5720S-
LI, S5720SI, S5720S-SI, S5700HI, S5710HI
S5720EI, S5720HI V200R011C00,

V200R011C10
S6700 S6720LI, S6720S-LI, S6720SI, S6720S-SI, Not supported

S6700EI
S6720EI, S6720S-EI V200R011C00,

V200R011C10
NOTE
To know details about software mappings, see Version Mapping Search for Huawei Campus
Switches.
Feature Dependencies and Limitations

You must run the label advertise implicit-null command to enable the egress node to
distribute an implicit null label to the PHP node when deploying seamless MPLS.
7.5 Configuring Intra-AS Seamless MPLS

Pre-configuration Tasks
Before configuring intra-AS seamless MPLS, complete the following tasks:
l Configure IGP protocols to implement connectivity at the access, aggregation, and core
layers and enable MPLS LDP to implement the MPLS forwarding on a public network.
l Configure IBGP peer relationships between each CSG and AGG, between each AGG
and Core ABR, and between each Core ABR and MASG.
In the intra-AS seamless MPLS networking, the access, aggregation, and core layers are
within a single AS. A BGP LSP is established across the three layers within the AS to
implement E2E service connectivity.

Configuration Process
To configure intra-AS seamless MPLS, perform the following operations in sequence.
7.5.1 Configuring AGG and Core ABR as RRs
Context
To enable the CSG and MASG to learn loopback routes to each other on an intra-AS seamless
MPLS network, configure an AGG and a core ABR as reflectors, specify a CSG and the core
ABR as the AGG's clients, and specify the AGG and an MASG as the core ABR's clients. The
loopback routes can be used to set up an MP-IBGP peer relationship between the CSG and
MASG.
Procedure
Step 1 Run:
system-view
The system view is displayed.
Step 2 Run:
bgp { as-number-plain | as-number-dot }
The BGP view is displayed.
Step 3 Run:
ipv4-family unicast
The IPv4 unicast address family view is displayed.
Step 4 Run:
peer { ipv4-address | group-name } reflect-client
An RR is configured, and the peer is specified as a client.
By default, no RR or specified client is configured for BGP.
Step 5 Run:
peer { ipv4-address | group-name } next-hop-local
BGP is configured to use its own IP address as the next hops of routes when advertising these
routes to its clients.
By default, when BGP advertises routes to an EBGP peer, it uses its own IP address as the
next hops. When BGP advertises routes to an IBGP peer, it does not change the next hop
attribute.
To enable the AGG or core ABR to advertise routes with the next hop address set to a local
address, run the peer next-hop-local command on the AGG or core ABR.
----End

7.5.2 Enabling BGP Peers to Exchange Labeled IPv4 Routes
Context
On a seamless MPLS network, before an E2E BGP LSP is established, BGP peers must be
enabled to exchange labeled IPv4 routes with each other.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
peer { ipv4-address | group-name } label-route-capability [ check-tunnel-
reachable ]
The ability to exchange labeled IPv4 routes with a BGP peer is enabled.
By default, the capability of exchanging labeled IPv4 routes is disabled.
The check-tunnel-reachable parameter helps prevent a data forwarding failure when the
CSG and MASG successfully set up an MP-EBGP peer relationship but a section along the
LSP between them fails to be established.
l If the check-tunnel-reachable parameter is specified:

When a tunnel between a local and remote device is unreachable, the local device
advertises an IPv4 unicast route to its peer. When the tunnel is reachable, the local device
advertises a labeled IPv4 route.
l If the check-tunnel-reachable parameter is not specified:
The local device advertises a labeled IPv4 route, regardless of whether a tunnel between
the local and remote devices is reachable.
----End
7.5.3 Configuring a BGP LSP
Context
Before a BGP LSP is established, a routing policy must be configured to control label
distribution. The egress of the BGP LSP to be established needs to distribute an MPLS label
to the route advertised to an upstream node. If a transit node receives a labeled IPv4 route
from downstream, the downstream node must re-distribute an MPLS label to the transit node
and advertises the label upstream.
Procedure
l Perform the following steps on each CSG and MASG:

a. Run:
system-view

b. Run:
route-policy route-policy-name permit node node
A Route-Policy node is created.

c. Run:
apply mpls-label
The local device is enabled to distribute MPLS labels to IPv4 routes.

By default, the action of distributing MPLS labels to public routes is not configured
in the routing policy.
d. Run:
quit
Return to the system view.

e. Run:

f. Run:
peer { ipv4-address | group-name } route-policy route-policy-name export
A routing policy for advertising routes matching Route-Policy conditions to a BGP

peer (group) is configured.
By default, no routing policy for filtering routes from its BGP peer (group) or routes
to be advertised to its BGP peer (group) is configured.
NOTE
Repeat this step for each BGP peer.

g. Run:
network ip-address [ mask | mask-length ] [ route-policy route-policy-
name ]
The route destined for the loopback interface address is advertised.

This route is labeled and advertised along a path over which a BGP LSP is
established.
l Perform the following steps on each AGG and core ABR:
a. Run:
system-view

b. Run:

c. Run:
if-match mpls-label
A matching rule based on the MPLS label is created.

By default, no matching rule based on the MPLS label is configured.

d. Run:
apply mpls-label

e. Run:
quit

f. Run:

g. Run:

NOTE
----End
7.5.4 (Optional) Configure BGP Auto FRR
Context
On an intra-AS seamless MPLS network that has protection switching enabled, if a link or
node fails, traffic switches to a backup path, which implements uninterrupted traffic
transmission.
NOTE
If both LDP FRR and BGP Auto FRR functions are configured, only BGP Auto FRR takes effect.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
ipv4-family unicast

The BGP-IPv4 unicast address family view is displayed.

Step 4 Run:
auto-frr
BGP Auto FRR is enabled for IPv4 unicast routes.

Step 5 Run:
bestroute nexthop-resolved tunnel
Labeled BGP IPv4 unicast routes can participate in route selection only when their next hops
are iterated to tunnels.
Step 6 (Optional) Run:
ingress-lsp protect-mode bgp-frr
BGP FRR is enabled for BGP LSPs.
NOTE
Perform this step on each CSG and MASG to enable the protection switching function for the whole
BGP LSP.
----End
7.5.5 Checking the Configurations

Prerequisites
Intra-AS seamless MPLS has been configured.
Procedure
l Run the display ip routing-table command on the CSG and MASG to check the route to
each other.
l Run the display mpls lsp command to check LSP information.
----End
7.6 Configuring Inter-AS Seamless MPLS

Before configuring inter-AS seamless MPLS, complete the following tasks:
l Configure IGP protocols to implement connectivity at the access, aggregation, and core
layers and enable MPLS LDP to implement the MPLS forwarding on a public network.
l Configure an EBGP peer relationship between each pair of an AGG ASBR and core
ASBR and an IBGP peer relationship between each pair of the following nodes:
CSG and AGG
AGG and AGG ASBR
Core ASBR and MASG
In the inter-AS seamless MPLS networking, the access and aggregation layers belong to one
AS, and the core layer belong to another AS. An inter-AS BGP LSP is established across the
three layers to implement E2E service connectivity.

To configure inter-AS seamless MPLS, perform the following operations in sequence.
7.6.1 Configuring AGG as the RR
Context
On an inter-AS seamless MPLS network, configuring an AGG as a reflector and specifying a
CSG and an AGG ASBR as the AGG's clients enable the AGG to transmit loopback routes
from the CSG to the AGG ASBR. The AGG then transmits the routes to the core layer
through an EBGP peer. The loopback routes can be used to set up an MP-EBGP peer
relationship between the CSG and MASG.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
ipv4-family unicast
The IPv4 unicast address family view is displayed.
Step 4 Run:
peer { ipv4-address | group-name } reflect-client
An RR is configured, and the CSG and core ASBR are specified as clients.
By default, no RR or specified client is configured for BGP.
Step 5 Run:
peer { ipv4-address | group-name } next-hop-local
The device is configured to use its own IP address as the next-hop address of routes when
advertising these routes.
By default, when BGP advertises routes to an EBGP peer, it uses its own IP address as the
next hops. When BGP advertises routes to an IBGP peer, it does not change the next hop
attribute.
To enable the AGG to advertise routes with the next hop address set to a local address, run the
peer next-hop-local command on the AGG.
----End

7.6.2 Enabling BGP Peers to Exchange Labeled IPv4 Routes

Context
On a seamless MPLS network, before an E2E BGP LSP is established, BGP peers must be
enabled to exchange labeled IPv4 routes with each other.
Procedure
l Perform the following steps on each CSG, AGG, and MASG:
a. Run:
system-view

b. Run:

c. Run:
reachable ]
The capability of exchanging labeled IPv4 routes with devices in the local AS is
enabled.
The check-tunnel-reachable parameter helps prevent a data forwarding failure
when the CSG and MASG successfully set up an MP-EBGP peer relationship but a
section along the LSP between them fails to be established.
n If the check-tunnel-reachable parameter is specified:
When a tunnel between a local and remote device is unreachable, the local
device advertises an IPv4 unicast route to its peer. When the tunnel is
reachable, the local device advertises a labeled IPv4 route.
n If the check-tunnel-reachable parameter is not specified:
The local device advertises a labeled IPv4 route, regardless of whether a tunnel
between the local and remote devices is reachable.
l Perform the following steps on each AGG ASBR and core ASBR:
a. Run:
system-view

b. Run:
interface interface-type interface-number
The view of the interface connected to the peer ASBR is displayed.

c. Run:
ip address ip-address { mask | mask-length }
An IP address is assigned to the interface.

d. Run:
mpls

MPLS is enabled.
e. Run:
quit

f. Run:

g. Run:
reachable ]
The capability of exchanging labeled IPv4 routes between BGP peers, including the
peer ASBR and the devices in the local AS, is enabled.
n If the label-route-capability is specified, a local device advertises an IPv4
unicast route to its peer if a tunnel between the local and remote devices is
unreachable and advertises a labeled IPv4 route if the tunnel is reachable. This
parameter helps prevent a data forwarding failure when an MP-EBGP peer
relationship between the CSG and MASG is established but an LSP over the
peer relationship fails to be established.
n If the label-route-capability parameter is not specified, the local device
advertises a labeled IPv4 route, regardless of whether a tunnel between the
local and remote devices is unreachable.
h. (Optional) Run:
supernet label-route advertise disable
The ASBR is disabled from advertising BGP supernet labeled routes.

By default, BGP supernet labeled routes can be preferentially selected and
advertised.
First disable the ASBR from advertising BGP supernet labeled routes, to advertise
the loopback address route of a PE in the local AS to a PE in another AS. Next, run
the network command on the ASBR to advertise the BGP route to the loopback
address of the PE in the same AS.
i. (Optional) Establishing an LDP LSP for the Labeled BGP Routes of the Public
Network
An IBGP peer relationship between the PE and the ASBR is unnecessary in this
solution. An ASBR learns the labeled public BGP routes of the remote AS from the
peer ASBR. Then these labeled public BGP routes are imported to IGP to trigger
the establishment of an LDP LSP. A complete LDP LSP can then be established
between the two PEs.
i. Run:
quit
ii. Run:
mpls
The MPLS view is displayed.

iii. Run:
lsp-trigger bgp-label-route [ ip-prefix ip-prefix-name ]
An LDP LSP is established for the labeled BGP routes of the public network
that is filtered by the IP prefix list.
By default, LDP does not allocate labels to labeled BGP routes on the public
network.
----End
7.6.3 Configuring a BGP LSP
Context
Before a BGP LSP is established, a routing policy must be configured to control label
distribution. The egress of the BGP LSP to be established needs to distribute an MPLS label
to the route advertised to an upstream node. If a transit node on the BGP LSP receives a
labeled IPv4 route from its downstream node, the transit node must re-distribute an MPLS
label to the labeled IPv4 route before advertising the route to an upstream node.
Procedure
l Perform the following steps on each CSG and MASG:
a. Run:
system-view

b. Run:

c. Run:
apply mpls-label

d. Run:
quit

e. Run:

f. Run:


NOTE

g. Run:
network ip-address [ mask | mask-length ] [ route-policy route-policy-
name ]
The route destined for the loopback interface address is advertised.

This route is labeled and advertised along a path over which a BGP LSP is
established.
h. (Optional) Run:
ingress-lsp trigger route-policy route-policy-name
The function to create ingress LSPs for labeled BGP routes based on routing
policies is configured.
By default, ingress LSPs are created based on all received BGP labeled routes.
On a MAN where the hybrid access mode is used, a large number of labeled BGP
routes are used to establish end-to-end LSPs. On certain intermediate nodes where
VPN services do not need to be supported, excessive ingress LSPs are created,
which waste network resources. In this case, you can run the ingress-lsp trigger
command to create ingress LSPs based on a routing policy to save network
resources.
i. (Optional) Run:
peer { group-name | ipv4-address } mpls-local-ifnet disable
The ability to establish an MPLS local IFNET tunnel between a CSG and MASG is
disabled.
In the inter-AS seamless MPLS network transmitting L3VPN services, a CSG and
MASG establish an MP-EBGP peer relationship. Therefore, an MPLS local IFNET
tunnel between the CSG and MASG is established over the MP-EBGP peer
relationship. The MPLS local IFNET tunnel fails to transmit traffic because the
CSG and MASG are indirectly connected.
If a fault occurs on the BGP LSP between the CSG and MASG, traffic is iterated to
the MPLS local IFNET tunnel, not an FRR bypass tunnel. As the MPLS local
IFNET tunnel cannot forward traffic, traffic is interrupted. To prevent the traffic
interruption, run the peer mpls-local-ifnet disable command to disable the
establishment of an MPLS local IFNET tunnel between the CSG and MASG.
l Perform the following steps on each AGG, AGG ASBR, and core ASBR:
a. Run:
system-view

b. Run:

c. Run:
if-match mpls-label
A matching rule based on the MPLS label is created.

By default, no matching rule based on the MPLS label is configured.

d. Run:
apply mpls-label

e. Run:
quit

f. Run:

g. Run:

NOTE
----End
7.6.4 (Optional) Configure BGP Auto FRR
Context
On an inter-AS seamless MPLS network that has protection switching enabled, if a link or
node fails, traffic switches to a backup path, which implements uninterrupted traffic
transmission.
NOTE
If both LDP FRR and BGP Auto FRR functions are configured, only BGP Auto FRR takes effect.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
ipv4-family unicast
The BGP-IPv4 unicast address family view is displayed.

Step 4 Run:
auto-frr
BGP Auto FRR is enabled for IPv4 unicast routes.
Step 5 Run:
bestroute nexthop-resolved tunnel
Labeled BGP IPv4 unicast routes can participate in route selection only when their next hops
are iterated to tunnels.

ingress-lsp protect-mode bgp-frr
BGP FRR is enabled for BGP LSPs.
NOTE
Perform this step on each CSG and MASG to enable the protection switching function for the whole
BGP LSP.
----End
Prerequisites
Inter-AS seamless MPLS has been configured.
Procedure
l Run the display ip routing-table command on the CSG and MASG to check the route to
each other.
l Run the display mpls lsp command to check LSP information.
----End
7.7 Configuring Dynamic BFD to Monitor a BGP Tunnel

BFD for BGP tunnel rapidly detects faults in E2E BGP tunnels.
Context
On an IP/MPLS network transmitting VPN services, PEs establish a multi-segment MPLS
tunnel between each other. Therefore VPN services are sent to multiple PEs. In this case,
VPN service provision on PEs becomes complex, and the VPN service scalability decreases.
As PEs establish BGP peer relationships, a routing policy can be used to assign MPLS labels
for BGP routes so that an E2E BGP tunnel can be established. The BGP tunnel consists of a
primary BGP LSP and a backup BGP LSP. VPN services can travel along the E2E BGP
tunnel, which simplifies service provision and improves VPN service scalability.
To rapidly detect faults in an E2E BGP tunnel, BFD for BGP tunnel is used. BFD for BGP
tunnel establish a dynamic BFD session, also called a BGP BFD session, which is bound to
both the primary and backup BGP LSPs. If both BGP LSPs fail, the BGP BFD session detects
the faults and triggers VPN FRR switching.

Before configuring dynamic BFD to monitor a BGP tunnel, configure basic MPLS functions.
Configure dynamic BFD to monitor a BGP tunnel according to the following sequence.
7.7.1 Enabling an MPLS Device to Dynamically Establish a BGP

BFD Session
Context
Before a dynamic BGP BFD session is established, the capability to dynamically establish
BGP BFD sessions must be enabled on each MPLS devices.
Procedure
l Perform the following steps on the ingress of an E2E BGP tunnel:
a. Run:
system-view

b. Run:
bfd
BFD is enabled globally, and the BFD view is displayed

c. Run:
quit

d. Run:
mpls

e. Run:
mpls bgp bfd enable
The ability to dynamically establish BGP BFD sessions is enabled on the ingress.
The mpls bgp bfd enable command does not create a BFD session. A BGP BFD
session can only be dynamically established only after a policy for dynamically
establish BGP BFD session is configured.
l Perform the following steps on the egress of an E2E BGP tunnel:
a. Run:
system-view

b. Run:
bfd
BFD is enabled globally, and the BFD view is displayed.

c. Run:
mpls-passive
The capability of passively creating a BFD session is configured on the egress.
The mpls-passive command does not create a BGP BFD session. The egress has to
receive an LSP ping request carrying a BFD TLV before creating a BGP BFD
session with the ingress.
----End
7.7.2 Configuring a Policy for Dynamically Establishing a BGP

BFD Session
Context
The policies for dynamically establishing BGP BFD sessions are as follows:
l Host address-based policy: used when all host addresses are available to trigger the
creation of BGP BFD sessions.
l IP address prefix list-based policy: used when only some host addresses can be used to
establish BFD sessions.
Perform the following steps on the ingress of an E2E BGP tunnel:
Procedure
Step 1 Run:
system-view

ip ip-prefix ip-prefix-name [ index index-number ] { permit | deny } ipv4-
address mask-length [ match-network ] [ greater-equal greater-equal-value ]
[ less-equal less-equal-value ]
An IPv4 address prefix list is configured, and list entries are configured.
You can perform this step when you want to use an IP address prefix list to dynamically
establish BGP BFD sessions.
Step 3 Run:
mpls
Step 4 Run:
mpls bgp bfd-trigger-tunnel { host | ip-prefix ip-prefix-name }
A policy for dynamically establishing a BGP BFD session is configured.
After a policy is configured, the device starts to dynamically establish a BGP BFD session.
----End

7.7.3 (Optional) Adjusting BGP BFD Parameters
Context
Perform the following steps on the ingress of an E2E BGP tunnel:
Procedure
Step 1 Run:
system-view
Step 2 Run:
bfd
The BFD view is displayed.
Step 3 Run:
mpls ping interval interval
The interval at which LSP ping packets are sent is set.
The default interval is 60s.
Step 4 Run:
quit
Step 5 Run:
mpls
Step 6 Run:
mpls bgp bfd { min-tx-interval interval | min-rx-interval interval | detect-
multiplier multiplier } *
BGP BFD time parameters are set.
By default, the minimum interval for sending BFD packets is 1000 ms, the minimum interval
for receiving BFD packets is 1000 ms, and the local detection multiplier is 3.
Effective BFD time parameters are calculated using the following formulas:
l Effective local interval at which BFD packets are sent = MAX { Locally configured
minimum interval at which BFD packets are sent, Remotely configured minimum
interval at which BFD packets are received }
l Effective local interval at which BFD packets are received = MAX { Remotely
configured minimum interval at which BFD packets are sent, Locally configured
minimum interval at which BFD packets are received }
l Local BFD detection period = Effective local interval at which BFD packets are received
x Remotely configured BFD detection multiplier
----End


Prerequisites
The dynamic BFD for BGP tunnel function has been configured.
You can view BGP BFD session information on the ingress of the BGP tunnel.
Procedure
l Run the display mpls bfd session protocol bgp [ fec fec-address [ verbose ] ] command
to check information about a BFD session with the protocol type of BGP on the ingress
on an E2E BGP tunnel.
l Run the display mpls lsp protocol bgp verbose command to check the BFD session
status of BGP LSPs.
----End
7.8 Maintaining Seamless MPLS

The seamless MPLS maintenance involves checking the connectivity and reachability of
seamless MPLS networks.
7.8.1 Checking Connectivity and Reachability of Seamless MPLS

Networks
Context
Run the following commands in any view of a BGP LSP endpoint node to check the
connectivity and reachability of a BGP LSP.
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 ] * bgp destination-address mask-length [ ip-
address ] command to check BGP LSP connectivity.
l Run the tracert lsp [ -a source-ip | -exp exp-value | -h ttl-value | -r reply-mode | -t time-
out ] * bgp destination-address mask-length [ ip-address ] command to perform an LSP
tracert operation on a BGP LSP.
----End
7.9 Configuration Examples

7.9.1 Example for Configuring Intra-AS Seamless MPLS
Networking Requirements
In Figure 7-9, the access, aggregation, and core layers belong to one AS. To enable the base
station NodeB to communicate with the MME/SGW and provide the VPN service to the

MME/SGW, the customer wants to use MPLS at the access layer, so that a complete LSP can
be set up over the three layers. To provide an end-to-end service and simplify service
configuration and network management, intra-AS seamless MPLS can be configured on the
network.
Figure 7-9 Networking for configuring intra-AS seamless MPLS

Access Aggregation Core
Loopback1 Loopback1 Loopback1 Loopback1

1.1.1.9/32 GE0/0/1 2.2.2.9/32 GE0/0/2 3.3.3.9/32 GE0/0/2 4.4.4.9/32
VLANIF100 VLANIF200 VLANIF300 MASG
172.1.1.1/24 172.2.1.1/24 172.3.1.1/24
GE0/0/1 GE0/0/1 GE0/0/1

CSG VLANIF100 AGG VLANIF200 Core_ABR VLANIF300
172.1.1.2/24 172.2.1.2/24 172.3.1.2/24
GE0/0/2 GE0/0/2
VLANIF400 VLANIF500
10.1.1.1/24 10.2.1.1/24
NodeB MME/SGW
Configuration Roadmap
The configuration roadmap is as follows:
1. Configure IGP protocols at the access, aggregation, and core layers to implement
network connectivity at each layer.
2. Configure MPLS and MPLS LDP on each device and establish an MPLS LSP.
3. Establish IBGP peer relationships at each layer and enable devices to exchange labeled
routes.
4. Configure each AGG and Core_ABR as RRs to help the CSG and MASG obtain the
route destined for each other's loopback interface.
5. Configure a routing policy to control label distribution for a BGP LSP to be established
on each device. The ingress node on the BGP LSP needs to distribute an MPLS label to
the route advertised to a downstream node. If a transit node on the BGP LSP receives a
labeled IPv4 route from its upstream node, the transit node must re-distribute an MPLS
label to the labeled IPv4 route before advertising the route to a downstream node.
6. Establish an MP-IBGP peer relationship between a CSG and MASG for VPNv4 route
information exchange.
7. Configure a VPN instance on each CSG and MASG.
Procedure
Step 1 On the devices, create a VLAN and a VLANIF interface, assign an IP address to the VLANIF
interface, and add a physical interface to the VLAN.

# Configure the CSG. The configurations of the AGG, Core_ABR, and MASG are similar to
that of the CSG, and are not mentioned here.
<HUAWEI> system-view
[HUAWEI] sysname CSG
[CSG] interface loopback 1
[CSG-LoopBack1] ip address 1.1.1.9 32
[CSG-LoopBack1] quit
[CSG] vlan batch 100 400
[CSG] interface vlanif 100
[CSG-Vlanif100] ip address 172.1.1.1 24
[CSG-Vlanif100] quit
[CSG] interface gigabitethernet0/0/1
[CSG-GigabitEthernet0/0/1] port link-type trunk
[CSG-GigabitEthernet0/0/1] port trunk allow-pass vlan 100
[CSG-GigabitEthernet0/0/1] quit
Step 2 Enable OSPF or IS-IS to advertise routes on network segments where each node locates and
routes represented by LSR IDs.
# Configure the CSG.
[CSG] ospf 1
[CSG-ospf-1] area 0
[CSG-ospf-1-area-0.0.0.0] network 1.1.1.9 0.0.0.0
[CSG-ospf-1-area-0.0.0.0] quit
[CSG-ospf-1] quit
# Configure the AGG.

[AGG] ospf 1
[AGG-ospf-1] area 0
[AGG-ospf-1-area-0.0.0.0] network 2.2.2.9 0.0.0.0
[AGG-ospf-1-area-0.0.0.0] quit
[AGG-ospf-1] quit
[AGG] isis 1
[AGG-isis-1] network-entity 10.0000.0000.0000.0010.00
[AGG-isis-1] quit
[AGG] interface vlanif 200
[AGG-Vlanif200] isis enable 1
[AGG-Vlanif200] quit
[AGG] interface loopback 1
[AGG-LoopBack1] isis enable 1
[AGG-LoopBack1] quit
# Configure the Core_ABR.

[Core_ABR] ospf 2
[Core_ABR-ospf-2] area 0
[Core_ABR-ospf-2-area-0.0.0.0] network 3.3.3.9 0.0.0.0
[Core_ABR-ospf-2-area-0.0.0.0] quit
[Core_ABR-ospf-2] quit
[Core_ABR] isis 1
[Core_ABR-isis-1] network-entity 10.0000.0000.0000.0020.00
[Core_ABR-isis-1] quit
[Core_ABR] interface vlanif 200
[Core_ABR-Vlanif200] isis enable 1
[Core_ABR-Vlanif200] quit
[Core_ABR] interface loopback 1

[Core_ABR-LoopBack1] isis enable 1

[Core_ABR-LoopBack1] quit
# Configure the MASG.

[MASG] ospf 2
[MASG-ospf-2] area 0
[MASG-ospf-2-area-0.0.0.0] network 4.4.4.9 0.0.0.0
[MASG-ospf-2-area-0.0.0.0] quit
[MASG-ospf-2] quit
Step 3 Enable MPLS and MPLS LDP globally on each device.

[CSG] mpls lsr-id 1.1.1.9
[CSG] mpls
[CSG-mpls] quit
[CSG] mpls ldp
[CSG-mpls-ldp] quit
[CSG-Vlanif100] mpls
[CSG-Vlanif100] mpls ldp
Step 4 Establish IBGP peer relationships at each layer and enable devices to exchange labeled routes.
[CSG] bgp 100
[CSG-bgp] peer 2.2.2.9 as-number 100
[CSG-bgp] peer 2.2.2.9 connect-interface LoopBack 1
[CSG-bgp] peer 2.2.2.9 label-route-capability
[CSG-bgp] network 1.1.1.9 32
[CSG-bgp] quit
[AGG] bgp 100

[AGG-bgp] peer 1.1.1.9 as-number 100
[AGG-bgp] peer 1.1.1.9 connect-interface LoopBack 1
[AGG-bgp] peer 1.1.1.9 label-route-capability
[AGG-bgp] quit

[Core_ABR] bgp 100
[Core_ABR-bgp] peer 2.2.2.9 as-number 100
[Core_ABR-bgp] peer 2.2.2.9 connect-interface LoopBack 1
[Core_ABR-bgp] peer 2.2.2.9 label-route-capability
[Core_ABR-bgp] quit

[MASG] bgp 100
[MASG-bgp] peer 3.3.3.9 as-number 100
[MASG-bgp] peer 3.3.3.9 connect-interface LoopBack 1
[MASG-bgp] peer 3.3.3.9 label-route-capability
[MASG-bgp] network 4.4.4.9 32
[MASG-bgp] quit

Step 5 Configure the AGG and Core_ABR as RRs to enable the CSG and MASG to obtain loopback
routes from each other through route reflection.
[AGG] bgp 100
[AGG-bgp] peer 1.1.1.9 reflect-client
[AGG-bgp] peer 1.1.1.9 next-hop-local
[AGG-bgp] quit

[Core_ABR] bgp 100
[Core_ABR-bgp] peer 2.2.2.9 reflect-client
[Core_ABR-bgp] peer 2.2.2.9 next-hop-local
[Core_ABR-bgp] quit
Step 6 Configure a routing policy on each device to establish BGP LSPs.

# Create a routing policy on the CSG and apply the routing policy to its peer.
[CSG] route-policy policy1 permit node 1
[CSG-route-policy] apply mpls-label
[CSG-route-policy] quit
[CSG] bgp 100
[CSG-bgp] peer 2.2.2.9 route-policy policy1 export
[CSG-bgp] quit
# Create a routing policy on the MASG and apply the routing policy to its peer.
[MASG] route-policy policy1 permit node 1
[MASG-route-policy] apply mpls-label
[MASG-route-policy] quit
[MASG] bgp 100
[MASG-bgp] peer 3.3.3.9 route-policy policy1 export
[MASG-bgp] quit
# Create a routing policy on the AGG and apply the routing policy to its peer.
[AGG] route-policy policy1 permit node 1
[AGG-route-policy] if-match mpls-label
[AGG-route-policy] apply mpls-label
[AGG-route-policy] quit
[AGG] bgp 100
[AGG-bgp] peer 1.1.1.9 route-policy policy1 export
[AGG-bgp] quit
# Create a routing policy on the Core_ABR and apply the routing policy to its peer.
[Core_ABR] route-policy policy1 permit node 1
[Core_ABR-route-policy] if-match mpls-label
[Core_ABR-route-policy] apply mpls-label
[Core_ABR-route-policy] quit
[Core_ABR] bgp 100
[Core_ABR-bgp] peer 2.2.2.9 route-policy policy1 export
[Core_ABR-bgp] peer 4.4.4.9 route-policy policy1 export
[Core_ABR-bgp] quit
Step 7 Establish an MP-IBGP peer relationship between a CSG and MASG for VPNv4 route
information exchange.
[CSG] bgp 100


[CSG-bgp] ipv4-family vpnv4
[CSG-bgp-af-vpnv4] peer 4.4.4.9 enable
[CSG-bgp-af-vpnv4] quit
[CSG-bgp] quit

[MASG] bgp 100
[MASG-bgp] ipv4-family vpnv4
[MASG-bgp-af-vpnv4] peer 1.1.1.9 enable
[MASG-bgp-af-vpnv4] quit
[MASG-bgp] quit
Step 8 Configure a VPN instance on each CSG and MASG.

# Configure the CSG. The configurations of the MASG are similar to that of the CSG, and are
not mentioned here.
[CSG] ip vpn-instance vpn1
[CSG-vpn-instance-vpn1] ipv4-family
[CSG-vpn-instance-vpn1-af-ipv4] route-distinguisher 100:1
[CSG-vpn-instance-vpn1-af-ipv4] vpn-target 1:1
[CSG-vpn-instance-vpn1-af-ipv4] quit
[CSG-vpn-instance-vpn1] quit
[CSG-Vlanif400] ip binding vpn-instance vpn1
[CSG] bgp 100
[CSG-bgp] ipv4-family vpn-instance vpn1
[CSG-bgp-vpn1] import-route direct
[CSG-bgp-vpn1] quit
[CSG-bgp] quit
Step 9 Verify the configuration.

After the configuration is complete, run the display ip routing-table command on the CSG or
MASG. You can view routes to the loopback address of each other.
The display on the CSG is used as an example.
[CSG] display ip routing-table
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Routing Tables: Public
Destinations : 7 Routes : 7
Destination/Mask Proto Pre Cost Flags NextHop Interface
1.1.1.9/32 Direct 0 0 D 127.0.0.1 LoopBack1

2.2.2.9/32 OSPF 10 1 D 172.1.1.2 Vlanif100
4.4.4.9/32 IBGP 255 0 RD 2.2.2.9 Vlanif100
127.0.0.0/8 Direct 0 0 D 127.0.0.1 InLoopBack0
172.1.1.0/24 Direct 0 0 D 172.1.1.1 Vlanif100
172.1.1.1/32 Direct 0 0 D 127.0.0.1 Vlanif100
Run the display mpls lsp command on the CSG or MASG to check the LSP configuration.
[CSG] display mpls lsp
-------------------------------------------------------------------------------
LSP Information: BGP LSP
-------------------------------------------------------------------------------
FEC In/Out Label In/Out IF Vrf Name
1.1.1.9/32 1025/NULL -/-

4.4.4.9/32 NULL/1027 -/-

-/32 1026/NULL -/- vpn1
Flag after Out IF: (I) - LSP Is Only Iterated by RLFA

-------------------------------------------------------------------------------
LSP Information: LDP LSP
-------------------------------------------------------------------------------
1.1.1.9/32 3/NULL -/-
2.2.2.9/32 NULL/3 -/Vlanif100
2.2.2.9/32 1024/3 -/Vlanif100
----End
Configuration Files
l CSG configuration file
#
sysname CSG
#
vlan batch 100 400
#
ip vpn-instance vpn1
ipv4-family
route-distinguisher 100:1
vpn-target 1:1 export-extcommunity
vpn-target 1:1 import-extcommunity
#
mpls lsr-id 1.1.1.9
mpls
#
mpls ldp
#
interface Vlanif100
ip address 172.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface Vlanif400
ip binding vpn-instance vpn1
ip address 10.1.1.1 255.255.255.0
#
interface GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 100
#
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
bgp 100
peer 2.2.2.9 as-number 100
peer 2.2.2.9 connect-interface LoopBack1
#
ipv4-family unicast
undo synchronization
network 1.1.1.9 255.255.255.255
peer 2.2.2.9 enable
peer 2.2.2.9 route-policy policy1 export
peer 2.2.2.9 label-route-capability
peer 4.4.4.9 enable
#
ipv4-family vpnv4

policy vpn-target
peer 4.4.4.9 enable
#
ipv4-family vpn-instance vpn1
import-route direct
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 172.1.1.0 0.0.0.255
#
route-policy policy1 permit node 1
apply mpls-label
#
return
l AGG configuration file
#
sysname AGG
#
vlan batch 100 200
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
#
isis 1
network-entity 10.0000.0000.0000.0010.00
#
interface Vlanif100
ip address 172.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface Vlanif200
ip address 172.2.1.1 255.255.255.0
isis enable 1
mpls
mpls ldp
#
#
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
isis enable 1
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.9 enable
peer 1.1.1.9 reflect-client
peer 1.1.1.9 next-hop-local
peer 3.3.3.9 enable


#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 172.1.1.0 0.0.0.255
#
if-match mpls-label
apply mpls-label
#
return
l Core_ABR configuration file
#
sysname Core_ABR
#
vlan batch 200 300
#
mpls lsr-id 3.3.3.9
mpls
#
mpls ldp
#
isis 1
network-entity 10.0000.0000.0000.0020.00
#
interface Vlanif200
ip address 172.2.1.2 255.255.255.0
isis enable 1
mpls
mpls ldp
#
interface Vlanif300
ip address 172.3.1.1 255.255.255.0
mpls
mpls ldp
#
#
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
isis enable 1
#
bgp 100
#
ipv4-family unicast
peer 2.2.2.9 enable
peer 4.4.4.9 enable
#
ospf 2

area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 172.3.1.0 0.0.0.255
#
if-match mpls-label
apply mpls-label
#
return
l MASG configurations file
#
sysname MASG
#
vlan batch 300 500
#
ip vpn-instance vpn1
ipv4-family
route-distinguisher 1:1
vpn-target 1:1 export-extcommunity
vpn-target 1:1 import-extcommunity
#
mpls lsr-id 4.4.4.9
mpls
#
mpls ldp
#
interface Vlanif300
ip address 172.3.1.2 255.255.255.0
mpls
mpls ldp
#
interface Vlanif500
ip binding vpn-instance vpn1
ip address 10.2.1.1 255.255.255.0
#
#
#
interface LoopBack1
ip address 4.4.4.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast
network 4.4.4.9 255.255.255.255
peer 1.1.1.9 enable
peer 3.3.3.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.9 enable
#
ipv4-family vpn-instance vpn1
import-route direct
#
ospf 2
area 0.0.0.0

network 4.4.4.9 0.0.0.0

network 172.3.1.0 0.0.0.255
#
apply mpls-label
#
return
7.9.2 Example for Configuring Inter-AS Seamless MPLS

In Figure 7-10, the access, aggregation, and core layers belong to different ASs. To enable the
base station NodeB to communicate with the MME/SGW and provide the VPN service to the
MME/SGW, the customer wants to use MPLS at the access layer, so that a complete LSP can
be set up over the three layers. To provide an end-to-end service and simplify service
configuration and network management, inter-AS seamless MPLS can be configured on the
network.
Figure 7-10 Networking for configuring inter-AS seamless MPLS
AS 100 AS 200
Loopback1 Loopback1 Loopback1 Loopback1 Loopback1

1.1.1.9/32 2.2.2.9/32GE0/0/2 3.3.3.9/32 GE0/0/2 4.4.4.9/32 GE0/0/2 5.5.5.9/32
GE0/0/1
VLANIF100 VLANIF200 VLANIF300 VLANIF400 MASG
172.1.1.1/24 172.2.1.1/24 172.3.1.1/24 172.4.1.1/24
GE0/0/1 GE0/0/1 GE0/0/1 GE0/0/1

CSG VLANIF100 AGG VLANIF200 AGG_ASBR VLANIF300 Core_ASBR VLANIF400
172.1.1.2/24 172.2.1.2/24 172.3.1.2/24 172.4.1.2/24
NodeB MME/SGW
2. Configure MPLS and MPLS LDP on each device and establish an MPLS LSP.
routes.
4. Configure an EBGP peer relationship between each pair of an AGG_ASBR and
Core_ASBR and enable these devices to exchange labeled routes across ASs.
5. Configure each AGG as an RR to help the CSG and MASG obtain the route destined for
each other's loopback interface.

6. Configure a routing policy to control label distribution for a BGP LSP to be established
on each device. The ingress node on the BGP LSP needs to distribute an MPLS label to
Procedure
# Configure the CSG. The configurations of the AGG, AGG_ASBR, Core_ASBR, and
MASG are similar to that of the CSG, and are not mentioned here.
[CSG] vlan batch 100
[CSG] ospf 1
[CSG-ospf-1] area 0
[CSG-ospf-1] quit

[AGG] ospf 1
[AGG-ospf-1] area 0
[AGG-ospf-1] quit
[AGG] isis 1
[AGG-isis-1] quit
# Configure the AGG_ASBR.

[AGG_ASBR] isis 1
[AGG_ASBR-isis-1] network-entity 10.0000.0000.0000.0020.00
[AGG_ASBR-isis-1] quit
[AGG_ASBR] interface vlanif 200
[AGG_ASBR-Vlanif200] isis enable 1
[AGG_ASBR-Vlanif200] quit

[AGG_ASBR] interface loopback 1

[AGG_ASBR-LoopBack1] isis enable 1
[AGG_ASBR-LoopBack1] quit
# Configure the Core_ASBR.

[Core_ASBR] ospf 2
[Core_ASBR-ospf-2] area 0
[Core_ASBR-ospf-2-area-0.0.0.0] network 4.4.4.9 0.0.0.0
[Core_ASBR-ospf-2-area-0.0.0.0] network 172.4.1.0 0.0.0.255
[Core_ASBR-ospf-2-area-0.0.0.0] quit
[Core_ASBR-ospf-2] quit

[MASG] ospf 2
[MASG-ospf-2] quit

[CSG] mpls
[CSG-mpls] quit
[CSG] mpls ldp
[CSG-mpls-ldp] quit

[AGG] mpls lsr-id 2.2.2.9
[AGG] mpls
[AGG-mpls] quit
[AGG] mpls ldp
[AGG-mpls-ldp] quit
[AGG-Vlanif100] mpls
[AGG-Vlanif100] mpls ldp
[AGG-Vlanif200] mpls
[AGG-Vlanif200] mpls ldp

[AGG_ASBR] mpls lsr-id 3.3.3.9
[AGG_ASBR] mpls
[AGG_ASBR-mpls] quit
[AGG_ASBR] mpls ldp
[AGG_ASBR-mpls-ldp] quit
[AGG_ASBR-Vlanif200] mpls
[AGG_ASBR-Vlanif200] mpls ldp

[Core_ASBR] mpls lsr-id 4.4.4.9
[Core_ASBR] mpls
[Core_ASBR-mpls] quit
[Core_ASBR] mpls ldp

[Core_ASBR-mpls-ldp] quit
[Core_ASBR] interface vlanif 400
[Core_ASBR-Vlanif400] mpls
[Core_ASBR-Vlanif400] mpls ldp
[Core_ASBR-Vlanif400] quit

[MASG] mpls lsr-id 5.5.5.9
[MASG] mpls
[MASG-mpls] quit
[MASG] mpls ldp
[MASG-mpls-ldp] quit
[MASG] interface vlanif 400
[MASG-Vlanif400] mpls
[MASG-Vlanif400] mpls ldp
[MASG-Vlanif400] quit
[CSG] bgp 100
[CSG-bgp] quit

[AGG] bgp 100
[AGG-bgp] quit

[AGG_ASBR] bgp 100
[AGG_ASBR-bgp] peer 2.2.2.9 as-number 100
[AGG_ASBR-bgp] peer 2.2.2.9 connect-interface LoopBack 1
[AGG_ASBR-bgp] peer 2.2.2.9 label-route-capability
[AGG_ASBR-bgp] quit

[Core_ASBR] bgp 200
[Core_ASBR-bgp] peer 5.5.5.9 as-number 200
[Core_ASBR-bgp] peer 5.5.5.9 connect-interface LoopBack 1
[Core_ASBR-bgp] peer 5.5.5.9 label-route-capability
[Core_ASBR-bgp] quit

[MASG] bgp 200
[MASG-bgp] quit
Step 5 Establish an EBGP peer relationship between the AGG_ASBR and Core_ASBR and enable
devices to exchange labeled routes.


[AGG_ASBR-Vlanif300] ip address 172.3.1.1 24
[AGG_ASBR-Vlanif300] mpls
[AGG_ASBR] bgp 100
[AGG_ASBR-bgp] peer 172.3.1.2 as-number 200
[AGG_ASBR-bgp] peer 172.3.1.2 label-route-capability check-tunnel-reachable
[AGG_ASBR-bgp] quit

[Core_ASBR] interface vlanif 300
[Core_ASBR-Vlanif300] ip address 172.3.1.2 24
[Core_ASBR-Vlanif300] mpls
[Core_ASBR-Vlanif300] quit
[Core_ASBR] bgp 200
[Core_ASBR-bgp] peer 172.3.1.1 as-number 100
[Core_ASBR-bgp] peer 172.3.1.1 label-route-capability check-tunnel-reachable
Step 6 Configure the AGG as the RR to enable the CSG and MASG to obtain loopback routes from
each other through route reflection.
[AGG] bgp 100
[AGG-bgp] quit

# Create a routing policy on the CSG and apply the routing policy to its peer.
[CSG] bgp 100
[CSG-bgp] quit
# Create a routing policy on the MASG and apply the routing policy to its peer.
[MASG] route-policy policy1 permit node 1
[MASG-route-policy] apply mpls-label
[MASG-route-policy] quit
[MASG] bgp 200
[MASG-bgp] peer 4.4.4.9 route-policy policy1 export
[MASG-bgp] quit
# Create a routing policy on the AGG and apply the routing policy to its peer.
[AGG] bgp 100
[AGG-bgp] quit
# Create a routing policy on the AGG_ASBR and apply the routing policy to its peer.
[AGG_ASBR] route-policy policy1 permit node 1
[AGG_ASBR-route-policy] if-match mpls-label
[AGG_ASBR-route-policy] apply mpls-label
[AGG_ASBR-route-policy] quit
[AGG_ASBR] bgp 100

[AGG_ASBR-bgp] peer 2.2.2.9 route-policy policy1 export

[AGG_ASBR-bgp] peer 172.3.1.2 route-policy policy1 export
[AGG_ASBR-bgp] quit
# Create a routing policy on the Core_ASBR and apply the routing policy to its peer.
[Core_ASBR] route-policy policy1 permit node 1
[Core_ASBR-route-policy] if-match mpls-label
[Core_ASBR-route-policy] apply mpls-label
[Core_ASBR-route-policy] quit
[Core_ASBR] bgp 200
[Core_ASBR-bgp] peer 5.5.5.9 route-policy policy1 export
[Core_ASBR-bgp] peer 172.3.1.1 route-policy policy1 export

------------------------------------------------------------------------------

2.2.2.9/32 OSPF 10 1 D 172.1.1.2 Vlanif100
5.5.5.9/32 IBGP 255 0 RD 2.2.2.9 Vlanif100
172.1.1.0/24 Direct 0 0 D 172.1.1.1 Vlanif100
172.1.1.1/32 Direct 0 0 D 127.0.0.1 Vlanif100
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
1.1.1.9/32 4103/NULL -/-
5.5.5.9/32 NULL/4124 -/-

-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
1.1.1.9/32 3/NULL -/-
2.2.2.9/32 NULL/3 -/Vlanif100
2.2.2.9/32 4104/3 -/Vlanif100
----End
Configuration Files
#
sysname CSG
#
vlan batch 100

#
mpls lsr-id 1.1.1.9
mpls
#
mpls ldp
#
interface Vlanif100
ip address 172.1.1.1 255.255.255.0
mpls
mpls ldp
#
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast
network 1.1.1.9 255.255.255.255
peer 2.2.2.9 enable
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 172.1.1.0 0.0.0.255
#
apply mpls-label
#
return
#
sysname AGG
#
vlan batch 100 200
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
#
isis 1
network-entity 10.0000.0000.0000.0010.00
#
interface Vlanif100
ip address 172.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface Vlanif200
ip address 172.2.1.1 255.255.255.0
isis enable 1
mpls
mpls ldp
#
#


#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
isis enable 1
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.9 enable
peer 3.3.3.9 enable
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 172.1.1.0 0.0.0.255
#
if-match mpls-label
apply mpls-label
#
return
l AGG_ASBR configuration file
#
sysname AGG_ASBR
#
vlan batch 200 300
#
mpls lsr-id 3.3.3.9
mpls
#
mpls ldp
#
isis 1
network-entity 10.0000.0000.0000.0020.00
#
interface Vlanif200
ip address 172.2.1.2 255.255.255.0
isis enable 1
mpls
mpls ldp
#
interface Vlanif300
ip address 172.3.1.1 255.255.255.0
mpls
#
#
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255

isis enable 1
#
bgp 100
#
ipv4-family unicast
peer 2.2.2.9 enable
peer 172.3.1.2 enable
peer 172.3.1.2 label-route-capability check-tunnel-reachable
#
if-match mpls-label
apply mpls-label
#
return
l Core_ASBR configuration file
#
sysname Core_ASBR
#
vlan batch 300 400
#
mpls lsr-id 4.4.4.9
mpls
#
mpls ldp
#
interface Vlanif300
ip address 172.3.1.2 255.255.255.0
mpls
#
interface Vlanif400
ip address 172.4.1.1 255.255.255.0
mpls
mpls ldp
#
#
#
interface LoopBack1
ip address 4.4.4.9 255.255.255.255
#
bgp 200
#
ipv4-family unicast
peer 5.5.5.9 enable
#
ospf 2
area 0.0.0.0
network 4.4.4.9 0.0.0.0

network 172.4.1.0 0.0.0.255

#
if-match mpls-label
apply mpls-label
#
return

#
sysname MASG
#
vlan batch 400
#
mpls lsr-id 5.5.5.9
mpls
#
mpls ldp
#
interface Vlanif400
ip address 172.4.1.2 255.255.255.0
mpls
mpls ldp
#
#
interface LoopBack1
ip address 5.5.5.9 255.255.255.255
#
bgp 200
#
ipv4-family unicast
network 5.5.5.9 255.255.255.255
peer 4.4.4.9 enable
#
ospf 2
area 0.0.0.0
network 5.5.5.9 0.0.0.0
network 172.4.1.0 0.0.0.255
#
apply mpls-label
#
return
7.9.3 Example for Configuring Intra-AS Seamless MPLS to

Transmit VLL Services
In Figure 7-11, the access, aggregation, and core layers belong to one AS. To enable the base
station NodeB to communicate with the MME/SGW and provide the VLL service, the
customer wants to use MPLS at the access layer, so that a complete LSP can be set up over
the three layers. To provide an end-to-end service and simplify service configuration and
network management, intra-AS seamless MPLS can be configured on the network.

NOTE
By default, link type negotiation is enabled globally on the device. If a VLANIF interface is used as an AC-
side interface for L2VPN, the configuration conflicts with link type negotiation. In this case, run the lnp
disable command in the system view to disable link type negotiation.
The lnp disable command has no impact on services before the device restarts. After the device restarts, the
device can only forward packets from the VLANs specified by the port default vlan command at Layer 2.
The port default vlan 1 command is configured by default, so only packets of VLAN 1 can be forwarded at
Layer 2.
Figure 7-11 Networking for configuring intra-AS seamless MPLS

Loopback1 Loopback1 Loopback1 Loopback1

1.1.1.9/32 GE0/0/1 2.2.2.9/32 GE0/0/2 3.3.3.9/32 GE0/0/2 4.4.4.9/32
VLANIF100 VLANIF200 VLANIF300 MASG
172.1.1.1/24 172.2.1.1/24 172.3.1.1/24
CSG GE0/0/1 GE0/0/1 GE0/0/1

GE0/0/2 VLANIF100 AGG VLANIF200 Core_ABR VLANIF300 GE0/0/2
VLAN 10 172.1.1.2/24 172.2.1.2/24 172.3.1.2/24 VLAN 20
GE0/0/2 GE0/0/2
VLANIF10 VLANIF20
192.168.1.1 Martini 192.168.1.2
CE1(NodeB) CE2(MME/SGW)
2. Enable MPLS and MPLS LDP on each device and establish an MPLS LSP.
routes.
4. Configure the AGG and Core_ABR as RRs to enable the CSG and MASG to obtain
loopback routes from each other through route reflection.
5. Configure a routing policy on each device to control label distribution for a BGP LSP to
be established. The ingress node on the BGP LSP needs to distribute an MPLS label to
6. Enable MPLS L2VPN on the CSG and MASG, and create a Martini connection between
them.
Procedure

# Configure the CSG. The configurations of CE1, CE2, the AGG, Core_ABR, and MASG are
similar to that of the CSG, and are not mentioned here.
[CSG] vlan batch 10 100
[CSG] interface gigabitethernet 0/0/1
[CSG] interface gigabitethernet 0/0/2
[CSG] ospf 1
[CSG-ospf-1] area 0
[CSG-ospf-1] quit

[AGG] ospf 1
[AGG-ospf-1] area 0
[AGG-ospf-1] quit
[AGG] isis 1
[AGG-isis-1] quit

[Core_ABR] ospf 2
[Core_ABR-ospf-2] area 0
[Core_ABR-ospf-2-area-0.0.0.0] quit
[Core_ABR-ospf-2] quit
[Core_ABR] isis 1
[Core_ABR-isis-1] network-entity 10.0000.0000.0000.0020.00
[Core_ABR-isis-1] quit
[Core_ABR] interface vlanif 200
[Core_ABR-Vlanif200] isis enable 1
[Core_ABR-Vlanif200] quit
[Core_ABR] interface loopback 1
[Core_ABR-LoopBack1] isis enable 1
[Core_ABR-LoopBack1] quit

[MASG] ospf 2
[MASG-ospf-2] quit

[CSG] mpls
[CSG-mpls] quit
[CSG] mpls ldp
[CSG-mpls-ldp] quit
[CSG] bgp 100
[CSG-bgp] quit
[AGG] bgp 100

[AGG-bgp] quit

[Core_ABR] bgp 100
[Core_ABR-bgp] quit

[MASG] bgp 100
[MASG-bgp] quit
Step 5 Configure the AGG and Core_ABR as RRs to enable the CSG and MASG to obtain loopback
routes from each other through route reflection.

[AGG] bgp 100

[AGG-bgp] quit

[Core_ABR] bgp 100
[Core_ABR-bgp] quit

# Create a routing policy on the CSG and apply the routing policy to its peer. The
configuration of the MASG is similar to that of the CSG, and is not mentioned here.
[CSG] bgp 100
[CSG-bgp] quit
# Create a routing policy on the AGG and apply the routing policy to its peer. The
configuration of the Core_ABR is similar to that of the AGG, and is not mentioned here.
[AGG] bgp 100
[AGG-bgp] quit
------------------------------------------------------------------------------

2.2.2.9/32 OSPF 10 1 D 172.1.1.2 Vlanif100
4.4.4.9/32 IBGP 255 0 RD 2.2.2.9 Vlanif100
172.1.1.0/24 Direct 0 0 D 172.1.1.1 Vlanif100
172.1.1.1/32 Direct 0 0 D 127.0.0.1 Vlanif100
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------


1.1.1.9/32 4099/NULL -/-
4.4.4.9/32 NULL/4106 -/-

-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
1.1.1.9/32 3/NULL -/-
2.2.2.9/32 NULL/3 -/Vlanif100
2.2.2.9/32 4097/3 -/Vlanif100
Step 7 Enable MPLS L2VPN on the CSG and MASG, and create a Martini connection between
them.
# Enable MPLS L2VPN on the CSG and establish a remote LDP session. The configuration
of the MASG is similar to that of the CSG, and is not mentioned here.
[CSG] mpls l2vpn
[CSG-l2vpn] quit
[CSG] mpls ldp remote-peer 4.4.4.9
[CSG-mpls-ldp-remote-4.4.4.9] remote-ip 4.4.4.9
[CSG-mpls-ldp-remote-4.4.4.9] quit
# Establish a Martini connection from the CSG to the MASG. The configuration of the
MASG is similar to that of the CSG, and is not mentioned here.
[CSG] lnp disable
[CSG-Vlanif10] mpls l2vc 4.4.4.9 100
[CSG-Vlanif10] quit

Check the L2VPN connection on the CSG or MASG. You can see that an L2 VC connection
is set up and is in the Up state.
[CSG] display mpls l2vc interface vlanif 10
*client interface : Vlanif10 is up
Administrator PW : no
session state : up
AC status : up
Ignore AC state : disable
VC state : up
Label state : 0
Token state : 0
VC ID : 100
VC type : VLAN
destination : 4.4.4.9
local group ID : 0 remote group ID : 0
local VC label : 23552 remote VC label : 23552
local AC OAM State : up
local PSN OAM State : up
local forwarding state : forwarding
local status code : 0x0
remote AC OAM state : up
remote PSN OAM state : up
remote forwarding state: forwarding
remote status code : 0x0
ignore standby state : no
BFD for PW : unavailable
VCCV State : up
manual fault : not set
active state : active
forwarding entry : exist
link state : up

local VC MTU : 1500 remote VC MTU : 1500

local VCCV : alert ttl lsp-ping bfd
remote VCCV : alert ttl lsp-ping bfd
local control word : disable remote control word : disable
tunnel policy name : --
PW template name : --
primary or secondary : primary
load balance type : flow
Access-port : false
Switchover Flag : false
VC tunnel/token info : 1 tunnels/tokens
NO.0 TNL type : lsp , TNL ID : 0x10031
Backup TNL type : lsp , TNL ID : 0x0
create time : 1 days, 22 hours, 15 minutes, 9 seconds
up time : 0 days, 22 hours, 54 minutes, 57 seconds
last change time : 0 days, 22 hours, 54 minutes, 57 seconds
VC last up time : 2013/09/05 19:26:37
VC total up time : 1 days, 20 hours, 42 minutes, 30 seconds
CKey : 8
NKey : 3
PW redundancy mode : --
AdminPw interface : --
AdminPw link state : --
Diffserv Mode : uniform
Service Class : --
Color : --
DomainId : --
Domain Name : --
CE1 and CE2 can ping each other.

The display on CE1 is used as an example.
[CE1] ping 192.168.1.2
PING 192.168.1.2: 56 data bytes, press CTRL_C to break
Reply from 192.168.1.2: bytes=56 Sequence=1 ttl=255 time=31 ms
--- 192.168.1.2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 2/15/31 ms
----End
Configuration Files
l CE1 configuration file
#
sysname CE1
#
vlan batch 10
#
interface Vlanif10
ip address 192.168.1.1 255.255.255.0
#
#
return
l CE2 configuration file

#
sysname CE2

#
vlan batch 20
#
interface Vlanif20
ip address 192.168.1.2 255.255.255.0
#
#
return
#
sysname CSG
#
vlan batch 10 100
#
lnp disable
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
mpls ldp
#
#
mpls ldp remote-peer 4.4.4.9
remote-ip 4.4.4.9
#
interface Vlanif10
mpls l2vc 4.4.4.9 100
#
interface Vlanif 100
ip address 172.1.1.1 255.255.255.0
mpls
mpls ldp
#
#
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast
network 1.1.1.9 255.255.255.255
peer 2.2.2.9 enable
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 172.1.1.0 0.0.0.255
#
apply mpls-label
#
return


#
sysname AGG
#
vlan batch 100 200
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
#
isis 1
network-entity 10.0000.0000.0000.0010.00
#
interface Vlanif100
ip address 172.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface Vlanif200
ip address 172.2.1.1 255.255.255.0
isis enable 1
mpls
mpls ldp
#
#
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
isis enable 1
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.9 enable
peer 3.3.3.9 enable
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 172.1.1.0 0.0.0.255
#
if-match mpls-label
apply mpls-label
#
return
l Core_ABR configuration file

#
sysname Core_ABR
#
vlan batch 200 300
#
mpls lsr-id 3.3.3.9
mpls
#
mpls ldp
#
isis 1
network-entity 10.0000.0000.0000.0020.00
#
interface Vlanif200
ip address 172.2.1.2 255.255.255.0
isis enable 1
mpls
mpls ldp
#
interface Vlanif300
ip address 172.3.1.1 255.255.255.0
mpls
mpls ldp
#
#
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
isis enable 1
#
bgp 100
#
ipv4-family unicast
peer 2.2.2.9 enable
peer 4.4.4.9 enable
#
ospf 2
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 172.3.1.0 0.0.0.255
#
if-match mpls-label
apply mpls-label
#
return
#
sysname MASG
#

vlan batch 20 300

#
mpls lsr-id 4.4.4.9
mpls
#
mpls l2vpn
#
mpls ldp
#
#
mpls ldp remote-peer 1.1.1.9
remote-ip 1.1.1.9
#
interface Vlanif20
mpls l2vc 1.1.1.9 100
#
interface Vlanif300
ip address 172.3.1.2 255.255.255.0
mpls
mpls ldp
#
#
#
interface LoopBack1
ip address 4.4.4.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast
network 4.4.4.9 255.255.255.255
peer 3.3.3.9 enable
#
ospf 2
area 0.0.0.0
network 4.4.4.9 0.0.0.0
network 172.3.1.0 0.0.0.255
#
apply mpls-label
#
return
7.9.4 Example for Configuring Dynamic BFD to Monitor a BGP

Tunnel
Seamless MPLS integrates the access, aggregation, and core layers on the same MPLS
network to transmit VPN services. Seamless MPLS establishes an E2E BGP tunnel to provide
E2E access services. To rapidly detect faults in BGP tunnels, BFD for BGP tunnel needs to be
configured.
In Figure 7-12, the access and aggregation layers belong to one AS, and the core layer
belongs to another AS. NodeBs need to communicate with an MME or SGW over a VPN. To

meet this requirement, inter-AS seamless MPLS can be configured between the CSG and
MASG. To monitor the connectivity of the BGP tunnel, BFD for BGP tunnel needs to be
configured.
Figure 7-12 Inter-AS seamless MPLS networking

Access Aggragtion Core
Loopback0 Loopback0 Loopback0 Loopback0 Loopback0

1.1.1.1/32 2.2.2.2/32 3.3.3.3/32 4.4.4.4/32 5.5.5.5/32
GE0/0/1 GE0/0/2 GE0/0/2 GE0/0/2

GE0/0/1 GE0/0/1 GE0/0/1 GE0/0/1
AGG Core
CSG AGG MASG
ASBR ASBR
AS 100 AS 200
NodeB MME/SGW
Table 7-2 Interface IP address list

Device Name Interface Name IP Address and Mask
CSG GE0/0/1 10.1.1.1/24
AGG GE0/0/1 10.1.1.2/24
AGG GE0/0/2 10.2.1.1/24
AGG ASBR GE0/0/1 10.2.1.2/24
AGG ASBR GE0/0/2 10.3.1.1/24
Core ASBR GE0/0/1 10.3.1.2/24
Core ASBR GE0/0/2 10.4.1.1/24
MASG GE0/0/1 10.4.1.2/24
1. Configure inter-AS seamless MPLS.

2. Configure BFD for BGP tunnel.
Procedure
Step 1 Assign an IP address to each interface.
Assign an IP address and mask to each interface, including each loopback interface, according
to Figure 7-12. For configuration details, see Configuration Files in this section.

Step 2 Configure an IGP.
Configure OSPF with process ID 1 at the access layer, IS-IS with process ID 1 at the
aggregation layer, and OSPF with process ID 2 at the core layer. Configure IGP protocols to
advertise the route to each network segment to which each interface is connected and to
advertise the host route to each loopback address which is used as an LSR ID. For
configuration details, see Configuration Files in this section.
Step 3 Configure basic MPLS and MPLS LDP functions.
Enable MPLS and MPLS LDP globally on each device and on interfaces in each AS. For
configuration details, see Configuration Files in this section.
# Configure CSG.
[CSG] bgp 100
[CSG-bgp] quit

[AGG] bgp 100
[AGG-bgp] quit
# Configure the AGG ASBR.

<AGG ASBR> system-view
[AGG ASBR] bgp 100
[AGG ASBR-bgp] peer 2.2.2.2 as-number 100
[AGG ASBR-bgp] peer 2.2.2.2 connect-interface LoopBack 0
[AGG ASBR-bgp] peer 2.2.2.2 label-route-capability
[AGG ASBR-bgp] quit
# Configure the core ASBR.

<Core ASBR> system-view
[Core ASBR] bgp 200
[Core ASBR-bgp] peer 5.5.5.5 as-number 200
[Core ASBR-bgp] peer 5.5.5.5 connect-interface LoopBack 0
[Core ASBR-bgp] peer 5.5.5.5 label-route-capability
[Core ASBR-bgp] quit

[MASG] bgp 200
[MASG-bgp] quit
Step 5 Establish an EBGP peer relationship between the AGG ASBR and core ASBR and enable
these devices to exchange labeled routes.
# Configure the AGG ASBR.

[AGG ASBR] interface GigabitEthernet 0/0/2

[AGG ASBR-GigabitEthernet0/0/2] mpls
[AGG ASBR-GigabitEthernet0/0/2] quit
[AGG ASBR] bgp 100
[AGG ASBR-bgp] peer 10.3.1.2 as-number 200
[AGG ASBR-bgp] peer 10.3.1.2 label-route-capability check-tunnel-reachable
[AGG ASBR-bgp] quit
# Configure the core ASBR.

[Core ASBR] interface GigabitEthernet 0/0/1
[Core ASBR-GigabitEthernet0/0/1] mpls
[Core ASBR-GigabitEthernet0/0/1] quit
[Core ASBR] bgp 200
[Core ASBR-bgp] peer 10.3.1.1 as-number 100
[Core ASBR-bgp] peer 10.3.1.1 label-route-capability check-tunnel-reachable
[Core ASBR-bgp] quit
Step 6 Configure each AGG as an RR to help the CSG and MASG obtain the route destined for each
other's loopback interface.
[AGG] bgp 100
[AGG-bgp] quit
Step 7 Configure a routing policy on each device to establish a BGP LSP in a BGP tunnel.
# Configure a routing policy for advertising routes matching Route-Policy conditions to the
CSG's BGP peer.
[CSG] bgp 100
[CSG-bgp] quit
Repeat this step for the MASG. For configuration details, see Configuration Files in this
section.
# Configure a routing policy for advertising routes matching Route-Policy conditions to the
AGG's BGP peer.
[AGG] bgp 100
[AGG-bgp] quit
Repeat this step for the AGG ASBR and core ASBR. For configuration details, see
Configuration Files in this section.
Step 8 Configure BFD for BGP tunnel.
# On the CSG, enable the MPLS capability to dynamically establish BGP BFD sessions based
on host addresses.
[CSG] bfd
[CSG-bfd] quit

[CSG] mpls
[CSG-mpls] mpls bgp bfd enable
[CSG-mpls] mpls bgp bfd-trigger-tunnel host
[CSG-mpls] quit
# On the MASG, enable the MPLS capability of passively creating a BFD session.
[MASG] bfd
[MASG-bfd] mpls-passive
[MASG-bfd] quit

After completing the preceding configurations, run the display mpls bfd session command
on the CSG to view information about the BFD session that monitors a BGP tunnel.
[CSG] display mpls bfd session protocol bgp
-------------------------------------------------------------------------------
BFD Information: BGP Tunnel
-------------------------------------------------------------------------------
FEC DISC OUT-IF NEXTHOP TUNNEL STATE
5.5.5.5 8192 - 2.2.2.2 - Up
Run the display mpls lsp protocol bgp verbose command on the CSG to view detailed
information about all BGP LSPs. The command output shows that the BFD session is Up.
[CSG] display mpls lsp protocol bgp verbose
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
No : 1
VrfIndex :
RD Value : 0:0
Fec : 1.1.1.1/32
Nexthop : 255.255.255.255
In-Label : 1025
Out-Label : NULL
In-Interface : ----------
Out-Interface : ----------
LspIndex : 7168
Token : 0x0
LsrType : Egress
Outgoing token : 0x0
Label Operation : POP
Mpls-Mtu : ------
TimeStamp : 802sec
FrrToken : 0x0
FrrOutgoingToken : 0x0
BGPKey : -------
BackupBGPKey : -------
FrrOutLabel : -------
Bfd-State : ---
Exp-Mode : ---
No : 2
VrfIndex :
RD Value : 0:0
Fec : 5.5.5.5/32
Nexthop : 2.2.2.2
In-Label : NULL
Out-Label : 1027
In-Interface : ----------
Out-Interface : ----------
LspIndex : 7169
Token : 0x48000007
LsrType : Ingress
Outgoing token : 0x48000005
Label Operation : PUSH

Mpls-Mtu : ------
TimeStamp : 425sec
FrrToken : 0x0
FrrOutgoingToken : 0x0
BGPKey : -------
BackupBGPKey : -------
FrrOutLabel : -------
Bfd-State : Up
Exp-Mode : ---
----End
Configuration Files
#
sysname CSG
#
bfd
#
mpls lsr-id 1.1.1.1
mpls
mpls bgp bfd enable
mpls bgp bfd-trigger-Tunnel host
#
mpls ldp
#
undo portswitch
ip address 10.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.255
#
bgp 100
#
ipv4-family unicast
network 1.1.1.1 255.255.255.255
peer 2.2.2.2 enable
#
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
#
apply mpls-label
#
return

#
sysname AGG
#
mpls lsr-id 2.2.2.2
mpls
#
mpls ldp
#
isis 1
network-entity 10.0001.0020.0200.2002.00

#
undo portswitch
ip address 10.1.1.2 255.255.255.0
mpls
mpls ldp
#
undo portswitch
ip address 10.2.1.1 255.255.255.0
isis enable 1
mpls
mpls ldp
#
interface LoopBack0
ip address 2.2.2.2 255.255.255.255
isis enable 1
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.1 enable
peer 3.3.3.3 enable
#
ospf 1
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 10.1.1.0 0.0.0.255
#
if-match mpls-label
apply mpls-label
#
return
l AGG ASBR configuration file
#
sysname AGG ASBR
#
mpls lsr-id 3.3.3.3
mpls
#
mpls ldp
#
isis 1
network-entity 10.0001.0030.0300.3003.00
#
undo portswitch
ip address 10.2.1.2 255.255.255.0
isis enable 1
mpls
mpls ldp
#
undo portswitch
ip address 10.3.1.1 255.255.255.0

mpls
#
interface LoopBack0
ip address 3.3.3.3 255.255.255.255
isis enable 1
#
bgp 100
#
ipv4-family unicast
peer 2.2.2.2 enable
#
if-match mpls-label
apply mpls-label
#
return
l Core ASBR configuration file
#
sysname Core ASBR
#
mpls lsr-id 4.4.4.4
mpls
#
mpls ldp
#
undo portswitch
ip address 10.3.1.2 255.255.255.0
mpls
#
undo portswitch
ip address 10.4.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 4.4.4.4 255.255.255.255
#
bgp 200
#
ipv4-family unicast
peer 5.5.5.5 enable
#
ospf 2
area 0.0.0.0
network 4.4.4.4 0.0.0.0
network 10.4.1.0 0.0.0.255
#
if-match mpls-label

apply mpls-label
#
return
l MASG configuration file

#
sysname MASG
#
bfd
mpls-passive
#
mpls lsr-id 5.5.5.5
mpls
#
mpls ldp
#
undo portswitch
ip address 10.4.1.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 5.5.5.5 255.255.255.255
#
bgp 200
#
ipv4-family unicast
network 5.5.5.5 255.255.255.255
peer 4.4.4.4 enable
#
ospf 2
area 0.0.0.0
network 5.5.5.5 0.0.0.0
network 10.4.1.0 0.0.0.255
#
apply mpls-label
#
return
7.10 References
The following table lists the references for this document.
Docume Description Remarks

nt
draft- Seamless MPLS Architecture -

leymann-
mpls-
seamless-
mpls-02


01-07 Seamless MPLS Configuration

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

01-07 Seamless MPLS Configuration

Transféré par

Droits d'auteur :

Formats disponibles

S1720&S2700&S5700&S6720 Series Ethernet Switches

Configuration Guide - MPLS 7 Seamless MPLS Configuration

7 Seamless MPLS Configuration

About This Chapter

Issue 03 (2017-07-27) Huawei Proprietary and Confidential 617

Many service providers use MPLS-based L3VPN/L2VPN solutions to construct a multi-

Issue 03 (2017-07-27) Huawei Proprietary and Confidential 618

Intra-AS Seamless MPLS

IBGP IBGP IBGP

Issue 03 (2017-07-27) Huawei Proprietary and Confidential 619

IBGP label IBGP label IBGP label

CSG1 AGG1 Core ABR1 MASG1

Issue 03 (2017-07-27) Huawei Proprietary and Confidential 620

CSG1 AGG1 Core ABR1 MASG1

MPLS tunnel label BGP label

Inter-AS Seamless MPLS

Issue 03 (2017-07-27) Huawei Proprietary and Confidential 621

IBGP IBGP EBGP IBGP

Issue 03 (2017-07-27) Huawei Proprietary and Confidential 622

IBGP IBGP EBGP IBGP

Issue 03 (2017-07-27) Huawei Proprietary and Confidential 623

CSG1 AGG1 AGG ASBR1 Core ASBR1 MASG1

MPLS tunnel label BGP label

CSG1 AGG1 AGG ASBR1 Core ASBR1 MASG1

MPLS tunnel label BGP label

Issue 03 (2017-07-27) Huawei Proprietary and Confidential 624

Figure 7-8 Application of the seamless MPLS networking

CSG1 AGG1 AGG ASBR1 Core ASBR1 MASG1

7.4 Configuration Notes

Issue 03 (2017-07-27) Huawei Proprietary and Confidential 625

Table 7-1 Products and versions supporting seamless MPLS

Produc Product Model Software Version

S1700 S1720GFR, S1720GW-E, S1720GWR-E, Not supported

S2700 S2700SI, S2700EI, S2710SI, S2720EI, S2750EI, Not supported

S3700 S3700SI, S3700EI, S3700HI Not supported

S5700 S5700LI, S5700S-LI, S5710-C-LI, S5710-X-LI, Not supported

S5720EI, S5720HI V200R011C00,

S6700 S6720LI, S6720S-LI, S6720SI, S6720S-SI, Not supported

S6720EI, S6720S-EI V200R011C00,

Feature Dependencies and Limitations

7.5 Configuring Intra-AS Seamless MPLS

Issue 03 (2017-07-27) Huawei Proprietary and Confidential 626

7.5.1 Configuring AGG and Core ABR as RRs

The system view is displayed.

The BGP view is displayed.

The IPv4 unicast address family view is displayed.

An RR is configured, and the peer is specified as a client.

By default, no RR or specified client is configured for BGP.

Issue 03 (2017-07-27) Huawei Proprietary and Confidential 627

7.5.2 Enabling BGP Peers to Exchange Labeled IPv4 Routes

The system view is displayed.

The BGP view is displayed.

By default, the capability of exchanging labeled IPv4 routes is disabled.

l If the check-tunnel-reachable parameter is specified:

7.5.3 Configuring a BGP LSP

Issue 03 (2017-07-27) Huawei Proprietary and Confidential 628

The system view is displayed.

A Route-Policy node is created.

The local device is enabled to distribute MPLS labels to IPv4 routes.

Return to the system view.

The BGP view is displayed.

A routing policy for advertising routes matching Route-Policy conditions to a BGP

Repeat this step for each BGP peer.

The route destined for the loopback interface address is advertised.