01-07 Seamless MPLS Configuration
01-07 Seamless MPLS Configuration
Purpose
Seamless MPLS was developed out of a need for greater flexibility in scenarios
where traditional MPLS overcomplicates network management. Traditional MPLS
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:
● Helps ease communication between the access, aggregation, and core layers
on an MPLS network.
● Simplifies network provisioning, operations, and maintenance because the
technology encapsulates all services and transmits these services along an E2E
LSP.
● Has high deployment flexibility and scalability. On a seamless MPLS network,
an LSP between any two nodes can be established to roll out services.
● Intra-AS Seamless MPLS: The access, aggregation, and core layers are within
a single AS. Intra-AS seamless MPLS applies to mobile bearer networks.
● 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.
▪ 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.
▪ 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
NodeB/
eNodeB
Access Aggregation Core
MME/
SGW
CSG2 AGG2 Core ABR2 MASG2
NodeB/e
NodeB
– Deploy tunnels.
In Figure 7-2, tunnel deployment is as follows:
▪ 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
NodeB/
eNodeB
Access Aggregation Core
MME/
SGW
CSG2 AGG2 Core ABR2 MASG2
NodeB/e
NodeB
MPLS LDP MPLS LDP MPLS LDP
● 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
Access Aggregation Core
MME/
SGW
CSG2 AGG2 Core ABR2 MASG2
NodeB/e
NodeB
VPN
▪ 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.
▪ 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
NodeB/e
NodeB Core
Access Aggregation
MME/
SGW
CSG2 AGG2 AGG ASBR2 Core ASBR2 MASG2
NodeB/e
NodeB
– Deploy tunnels.
In Figure 7-5, tunnel deployment is as follows:
▪ 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.
Figure 7-5 Deploying tunnels for the inter-AS seamless MPLS networking
AS x AS y
NodeB/e
NodeB Core
Access Aggregation
MME/
SGW
CSG2 AGG2 AGG ASBR2 Core ASBR2 MASG2
NodeB/e
NodeB
MPLS LDP MPLS LDP MPLS LDP
● 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/e
NodeB Core
Access Aggregation
MME/
SGW
CSG2 AGG2 AGG ASBR2 Core ASBR2 MASG2
NodeB/e
NodeB
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/e
NodeB Core
Access Aggregation
MME/
SGW
CSG2 AGG2 AGG ASBR2 Core ASBR2 MASG2
NodeB/e
NodeB
VPN
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.
AS x AS y
NodeB/e
NodeB Core
Access Aggregation
MME/
SGW
CSG2 AGG2 AGG ASBR2 Core ASBR2 MASG2
NodeB/e LSP
NodeB
License Requirements
Seamless MPLS is a basic feature of a switch and is not under license control.
Version Requirements
NOTE
To know details about software mappings, see Hardware Query Tool.
Feature Limitations
When deploying seamless MPLS on the S5720-EI, S6720-EI, or S6720S-EI, you
must run the label advertise implicit-null command to enable the egress node to
distribute an implicit null label to the PHP node.
Pre-configuration Tasks
Before configuring intra-AS seamless MPLS, complete the following tasks:
Configuration Procedure
To configure intra-AS seamless MPLS, perform the following operations in
sequence.
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
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
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
The ability to exchange labeled IPv4 routes with a BGP peer is enabled.
----End
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
● Perform the following steps on each CSG and MASG:
a. Run system-view
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
This route is labeled and advertised along a path over which a BGP LSP is
established.
● Perform the following steps on each AGG and core ABR:
a. Run system-view
NOTE
----End
If both LDP FRR and BGP Auto FRR functions are configured, only BGP Auto FRR takes
effect.
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 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.
NOTE
Perform this step on each CSG and MASG to enable the protection switching function for
the whole BGP LSP.
----End
Prerequisites
Intra-AS seamless MPLS has been configured.
Procedure
● Run the display ip routing-table command on the CSG and MASG to check
the route to each other.
● Run the display mpls lsp command to check LSP information.
----End
Pre-configuration Tasks
Before configuring inter-AS seamless MPLS, complete the following tasks:
Configuration Procedure
To configure inter-AS seamless MPLS, perform the following operations in
sequence.
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 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
Procedure
● Perform the following steps on each CSG, AGG, and MASG:
a. Run system-view
The system view is displayed.
Procedure
● Perform the following steps on each CSG and MASG:
a. Run system-view
The system view is displayed.
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 bgp { as-number-plain | as-number-dot }
The BGP view is displayed.
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
NOTE
----End
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
Labeled BGP IPv4 unicast routes can participate in route selection only when their
next hops are iterated to tunnels.
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
● Run the display ip routing-table command on the CSG and MASG to check
the route to each other.
Pre-configuration Tasks
Before configuring dynamic BFD to monitor a BGP tunnel, configure basic MPLS
functions.
Configuration Procedure
Configure dynamic BFD to monitor a BGP tunnel according to the following
sequence.
Procedure
● Perform the following steps on the ingress of an E2E BGP tunnel:
a. Run system-view
The system view is displayed.
b. Run bfd
BFD is enabled globally, and the BFD view is displayed
c. Run quit
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 (Optional) Run 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
The MPLS view is displayed.
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
Procedure
Step 1 Run system-view
The system view is displayed.
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
Return to the system view.
Step 5 Run mpls
The MPLS view is displayed.
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:
● 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 }
● 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 }
● Local BFD detection period = Effective local interval at which BFD packets are
received x Remotely configured BFD detection multiplier
----End
Procedure
● 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.
● Run the display mpls lsp protocol bgp verbose command to check the BFD
session status of BGP LSPs.
----End
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 ] * bgp destination-
address mask-length [ ip-address ] command to check BGP LSP connectivity.
● 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
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 vlanif 400
[CSG-Vlanif400] ip address 10.1.1.1 24
[CSG-Vlanif400] 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
[CSG] interface gigabitethernet0/0/2
[CSG-GigabitEthernet0/0/2] port link-type trunk
[CSG-GigabitEthernet0/0/2] port trunk allow-pass vlan 400
[CSG-GigabitEthernet0/0/2] 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] network 172.1.1.0 0.0.0.255
[CSG-ospf-1-area-0.0.0.0] quit
[CSG-ospf-1] quit
Step 4 Establish IBGP peer relationships at each layer and enable devices to exchange
labeled routes.
# Configure the CSG.
[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
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.
# Configure the AGG.
[AGG] bgp 100
[AGG-bgp] peer 1.1.1.9 reflect-client
[AGG-bgp] peer 1.1.1.9 next-hop-local
[AGG-bgp] peer 3.3.3.9 reflect-client
[AGG-bgp] peer 3.3.3.9 next-hop-local
[AGG-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] peer 3.3.3.9 route-policy policy1 export
[AGG-bgp] quit
# Create a routing policy on the Core_ABR and apply the routing policy to its peer.
Step 7 Establish an MP-IBGP peer relationship between a CSG and MASG for VPNv4
route information exchange.
# Configure the CSG.
[CSG] bgp 100
[CSG-bgp] peer 4.4.4.9 as-number 100
[CSG-bgp] peer 4.4.4.9 connect-interface LoopBack 1
[CSG-bgp] ipv4-family vpnv4
[CSG-bgp-af-vpnv4] peer 4.4.4.9 enable
[CSG-bgp-af-vpnv4] quit
[CSG-bgp] quit
Run the display mpls lsp command on the CSG or MASG to check the LSP
configuration.
The display on the CSG is used as an example.
[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
----End
Configuration Files
● 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 GigabitEthernet0/0/2
port link-type trunk
port trunk allow-pass vlan 400
#
interface LoopBack1
bgp 100
peer 1.1.1.9 as-number 100
peer 1.1.1.9 connect-interface LoopBack1
peer 3.3.3.9 as-number 100
peer 3.3.3.9 connect-interface LoopBack1
#
ipv4-family unicast
undo synchronization
peer 1.1.1.9 enable
peer 1.1.1.9 route-policy policy1 export
peer 1.1.1.9 reflect-client
peer 1.1.1.9 next-hop-local
peer 1.1.1.9 label-route-capability
peer 3.3.3.9 enable
peer 3.3.3.9 route-policy policy1 export
peer 3.3.3.9 reflect-client
peer 3.3.3.9 next-hop-local
peer 3.3.3.9 label-route-capability
#
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
#
route-policy policy1 permit node 1
if-match mpls-label
apply mpls-label
#
return
● 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 GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 200
#
interface GigabitEthernet0/0/2
port link-type trunk
port trunk allow-pass vlan 300
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
isis enable 1
#
bgp 100
peer 2.2.2.9 as-number 100
peer 2.2.2.9 connect-interface LoopBack1
ipv4-family unicast
undo synchronization
network 4.4.4.9 255.255.255.255
peer 1.1.1.9 enable
peer 3.3.3.9 enable
peer 3.3.3.9 route-policy policy1 export
peer 3.3.3.9 label-route-capability
#
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
#
route-policy policy1 permit node 1
apply mpls-label
#
return
Networking Requirements
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.
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 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 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.
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, AGG_ASBR, Core_ASBR, 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
[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] network 172.1.1.0 0.0.0.255
[CSG-ospf-1-area-0.0.0.0] quit
[CSG-ospf-1] quit
[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
Step 4 Establish IBGP peer relationships at each layer and enable devices to exchange
labeled routes.
Step 5 Establish an EBGP peer relationship between the AGG_ASBR and Core_ASBR and
enable devices to exchange labeled routes.
# Configure the AGG_ASBR.
[AGG_ASBR] interface vlanif 300
[AGG_ASBR-Vlanif300] ip address 172.3.1.1 24
[AGG_ASBR-Vlanif300] mpls
[AGG_ASBR-Vlanif300] quit
[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
Step 6 Configure the AGG as the RR to enable the CSG and MASG to obtain loopback
routes from each other through route reflection.
# Configure the AGG.
[AGG] bgp 100
[AGG-bgp] peer 1.1.1.9 reflect-client
[AGG-bgp] peer 1.1.1.9 next-hop-local
[AGG-bgp] peer 3.3.3.9 reflect-client
[AGG-bgp] peer 3.3.3.9 next-hop-local
[AGG-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] 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] peer 3.3.3.9 route-policy policy1 export
[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
[Core_ASBR-bgp] quit
Run the display mpls lsp command on the CSG or MASG to check the LSP
configuration.
----End
Configuration Files
● CSG configuration file
#
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 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
#
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
#
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 GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 100
#
interface GigabitEthernet0/0/2
port link-type trunk
port trunk allow-pass vlan 200
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
isis enable 1
#
bgp 100
peer 1.1.1.9 as-number 100
peer 1.1.1.9 connect-interface LoopBack1
peer 3.3.3.9 as-number 100
peer 3.3.3.9 connect-interface LoopBack1
#
ipv4-family unicast
undo synchronization
peer 1.1.1.9 enable
peer 1.1.1.9 route-policy policy1 export
peer 1.1.1.9 reflect-client
peer 1.1.1.9 next-hop-local
peer 1.1.1.9 label-route-capability
peer 3.3.3.9 enable
peer 3.3.3.9 route-policy policy1 export
peer 3.3.3.9 reflect-client
peer 3.3.3.9 next-hop-local
peer 3.3.3.9 label-route-capability
#
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
#
route-policy policy1 permit node 1
if-match mpls-label
apply mpls-label
#
return
● AGG_ASBR configuration file
#
sysname AGG_ASBR
#
vlan batch 200 300
#
interface GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 300
#
interface GigabitEthernet0/0/2
port link-type trunk
port trunk allow-pass vlan 400
#
interface LoopBack1
ip address 4.4.4.9 255.255.255.255
#
bgp 200
peer 5.5.5.9 as-number 200
peer 5.5.5.9 connect-interface LoopBack1
peer 172.3.1.1 as-number 100
#
ipv4-family unicast
undo synchronization
peer 5.5.5.9 enable
peer 5.5.5.9 route-policy policy1 export
peer 5.5.5.9 label-route-capability
peer 172.3.1.1 enable
peer 172.3.1.1 route-policy policy1 export
peer 172.3.1.1 label-route-capability check-tunnel-reachable
#
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
#
route-policy policy1 permit node 1
if-match mpls-label
apply mpls-label
#
return
● MASG configurations file
#
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 GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 400
#
interface LoopBack1
ip address 5.5.5.9 255.255.255.255
#
bgp 200
peer 4.4.4.9 as-number 200
peer 4.4.4.9 connect-interface LoopBack1
#
ipv4-family unicast
undo synchronization
network 5.5.5.9 255.255.255.255
peer 4.4.4.9 enable
peer 4.4.4.9 route-policy policy1 export
peer 4.4.4.9 label-route-capability
#
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
#
route-policy policy1 permit node 1
apply mpls-label
#
return
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.
GE0/0/2 GE0/0/2
VLANIF10 VLANIF20
192.168.1.1 Martini 192.168.1.2
CE1(NodeB) CE2(MME/SGW)
Configuration Roadmap
The configuration roadmap is as follows:
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 CE1, CE2, 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 10 100
[CSG] interface vlanif 100
[CSG-Vlanif100] ip address 172.1.1.1 24
[CSG-Vlanif100] quit
[CSG] interface gigabitethernet 0/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
[CSG] interface gigabitethernet 0/0/2
[CSG-GigabitEthernet0/0/2] port link-type trunk
[CSG-GigabitEthernet0/0/2] port trunk allow-pass vlan 10
[CSG-GigabitEthernet0/0/2] 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] network 172.1.1.0 0.0.0.255
[CSG-ospf-1-area-0.0.0.0] quit
[CSG-ospf-1] 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
Step 4 Establish IBGP peer relationships at each layer and enable devices to exchange
labeled routes.
# Configure the CSG.
[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
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.
# Configure the AGG.
[AGG] bgp 100
[AGG-bgp] peer 1.1.1.9 reflect-client
[AGG-bgp] peer 1.1.1.9 next-hop-local
[AGG-bgp] peer 3.3.3.9 reflect-client
[AGG-bgp] peer 3.3.3.9 next-hop-local
[AGG-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] route-policy policy1 permit node 1
[AGG-route-policy] if-match mpls-label
Run the display mpls lsp command on the CSG or MASG to check the LSP
configuration.
The display on the CSG is used as an example.
[CSG] display mpls lsp
-------------------------------------------------------------------------------
LSP Information: BGP LSP
-------------------------------------------------------------------------------
FEC In/Out Label In/Out IF Vrf Name
1.1.1.9/32 4099/NULL -/-
4.4.4.9/32 NULL/4106 -/-
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] interface vlanif 10
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.
----End
Configuration Files
● CE1 configuration file
#
sysname CE1
#
vlan batch 10
#
interface Vlanif10
ip address 192.168.1.1 255.255.255.0
#
interface GigabitEthernet0/0/2
port link-type trunk
port trunk allow-pass vlan 10
#
return
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 GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 100
#
interface GigabitEthernet0/0/2
port link-type trunk
port trunk allow-pass vlan 10
#
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
#
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
● 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 GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 100
#
interface GigabitEthernet0/0/2
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
isis enable 1
#
bgp 100
peer 2.2.2.9 as-number 100
peer 2.2.2.9 connect-interface LoopBack1
peer 4.4.4.9 as-number 100
peer 4.4.4.9 connect-interface LoopBack1
#
ipv4-family unicast
undo synchronization
peer 2.2.2.9 enable
peer 2.2.2.9 route-policy policy1 export
peer 2.2.2.9 reflect-client
peer 2.2.2.9 next-hop-local
peer 2.2.2.9 label-route-capability
peer 4.4.4.9 enable
peer 4.4.4.9 route-policy policy1 export
peer 4.4.4.9 reflect-client
peer 4.4.4.9 next-hop-local
peer 4.4.4.9 label-route-capability
#
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
#
route-policy policy1 permit node 1
if-match mpls-label
apply mpls-label
#
return
● MASG configurations file
#
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 GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 300
#
interface GigabitEthernet0/0/2
port link-type trunk
port trunk allow-pass vlan 20
#
interface LoopBack1
ip address 4.4.4.9 255.255.255.255
#
bgp 100
peer 3.3.3.9 as-number 100
peer 3.3.3.9 connect-interface LoopBack1
#
ipv4-family unicast
undo synchronization
network 4.4.4.9 255.255.255.255
peer 3.3.3.9 enable
peer 3.3.3.9 route-policy policy1 export
peer 3.3.3.9 label-route-capability
#
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
#
route-policy policy1 permit node 1
apply mpls-label
#
return
NodeB MME/SGW
Configuration Roadmap
The configuration roadmap is as follows:
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.
Step 4 Establish IBGP peer relationships at each layer and enable devices to exchange
labeled routes.
# Configure CSG.
[CSG] bgp 100
[CSG-bgp] peer 2.2.2.2 as-number 100
[CSG-bgp] peer 2.2.2.2 connect-interface LoopBack 0
[CSG-bgp] peer 2.2.2.2 label-route-capability
Step 5 Establish an EBGP peer relationship between the AGG ASBR and core ASBR and
enable these devices to exchange labeled routes.
Step 6 Configure each AGG as an RR to help the CSG and MASG obtain the route
destined for each other's loopback interface.
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] 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.2 route-policy policy1 export
[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] 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.1 route-policy policy1 export
[AGG-bgp] peer 3.3.3.3 route-policy policy1 export
[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
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
-------------------------------------------------------------------------------
LSP Information: BGP LSP
-------------------------------------------------------------------------------
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
● CSG configuration file
#
sysname CSG
#
bfd
#
mpls lsr-id 1.1.1.1
mpls
mpls bgp bfd enable
mpls bgp bfd-trigger-Tunnel host
#
mpls ldp
#
interface GigabitEthernet0/0/1
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
peer 2.2.2.2 as-number 100
peer 2.2.2.2 connect-interface LoopBack0
#
ipv4-family unicast
undo synchronization
network 1.1.1.1 255.255.255.255
peer 2.2.2.2 enable
peer 2.2.2.2 route-policy policy1 export
peer 2.2.2.2 label-route-capability
#
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
#
route-policy policy1 permit node 1
apply mpls-label
#
return
● AGG configuration file
#
sysname AGG
#
mpls lsr-id 2.2.2.2
mpls
#
mpls ldp
#
isis 1
network-entity 10.0001.0020.0200.2002.00
#
interface GigabitEthernet0/0/1
undo portswitch
ip address 10.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface GigabitEthernet0/0/2
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
peer 1.1.1.1 as-number 100
peer 1.1.1.1 connect-interface LoopBack0
peer 3.3.3.3 as-number 100
peer 3.3.3.3 connect-interface LoopBack0
#
ipv4-family unicast
undo synchronization
peer 1.1.1.1 enable
peer 1.1.1.1 route-policy policy1 export
peer 1.1.1.1 reflect-client
peer 1.1.1.1 next-hop-local
peer 1.1.1.1 label-route-capability
peer 3.3.3.3 enable
peer 3.3.3.3 route-policy policy1 export
peer 3.3.3.3 reflect-client
peer 3.3.3.3 next-hop-local
peer 3.3.3.3 label-route-capability
#
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
#
route-policy policy1 permit node 1
if-match mpls-label
apply mpls-label
#
return
● 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
#
interface GigabitEthernet0/0/1
undo portswitch
ip address 10.2.1.2 255.255.255.0
isis enable 1
mpls
mpls ldp
#
interface GigabitEthernet0/0/2
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
peer 2.2.2.2 as-number 100
peer 2.2.2.2 connect-interface LoopBack0
peer 10.3.1.2 as-number 200
#
ipv4-family unicast
undo synchronization
peer 2.2.2.2 enable
peer 2.2.2.2 route-policy policy1 export
peer 2.2.2.2 label-route-capability
peer 10.3.1.2 enable
peer 10.3.1.2 route-policy policy1 export
peer 10.3.1.2 label-route-capability check-tunnel-reachable
#
route-policy policy1 permit node 1
if-match mpls-label
apply mpls-label
#
return
● Core ASBR configuration file
#
sysname Core ASBR
#
mpls lsr-id 4.4.4.4
mpls
#
mpls ldp
#
interface GigabitEthernet0/0/1
undo portswitch
ip address 10.3.1.2 255.255.255.0
mpls
#
interface GigabitEthernet0/0/2
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
peer 5.5.5.5 as-number 200
peer 5.5.5.5 connect-interface LoopBack0
peer 10.3.1.1 as-number 100
#
ipv4-family unicast
undo synchronization
peer 5.5.5.5 enable
peer 5.5.5.5 route-policy policy1 export
peer 5.5.5.5 label-route-capability
peer 10.3.1.1 enable
peer 10.3.1.1 route-policy policy1 export
peer 10.3.1.1 label-route-capability check-tunnel-reachable
#
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
#
route-policy policy1 permit node 1
if-match mpls-label
apply mpls-label
#
return
● MASG configuration file
#
sysname MASG
#
bfd
mpls-passive
#
mpls lsr-id 5.5.5.5
mpls
#
mpls ldp
#
interface GigabitEthernet0/0/1
undo portswitch
ip address 10.4.1.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0