MBB V600R005C00 ATN+CX IDEAL (Seamless MPLS) Solution Configuration Guide (CLI) 03-C

MBB ATN+CX IDEAL(Seamless MPLS) Solution
V600R005C00
Configuration Guide (CLI)
Issue 03
Date 2014-10-20
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2014. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 03 (2014-10-20) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
Configuration Guide (CLI) About This Document
About This Document
Intended Audience
This document describes the principle, data planning, and procedure for configuring services in
the ATN+CX mobile broadband IDEAL (Seamless MPLS) solution.
This document uses the CX600 as an example. The configurations also apply to the
NetEngine40E (NE40E).
This document is intended for the following readers:
l Network planning engineers

l Commissioning engineers
l Data configuration engineers
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in previous issues.
Issue 03(2014-10-20)
This issue is the third official release.
Updates include:
l Added description about change of MED values in sections 6.1.1 MPLS Tunnel
Deployment Solution, 6.2.1 Tunnel Deployment Solution, 8.1.1 E2E Ethernet Service
Deployment Solution, and 8.2.1 E2E Ethernet Service Deployment Solution.
l Added description about routing policies in sections 6.1.3 Configuring BGP LSPs and
6.2.3 Configuring BGP LSPs.
Issue 02 (2014-06-09)
This issue is the second official release.
Updates include:
Issue 03 (2014-10-20) Huawei Proprietary and Confidential ii

Configuration Guide (CLI) About This Document
l Modified the example loopback interface of a CSG in 7.1.1 Deploying Public DCN Using
IS-IS (U2000 Connected to the IPCore Network).
l Modified "apply tag 20000" into "apply tag 2000" for the routing policy with the name of
"2000" on an ASBR at the aggregation layer in 7.1.1 Deploying Public DCN Using IS-IS
(U2000 Connected to the IPCore Network).
Issue 01 (2014-04-30)
This issue is the first official release.
Issue 03 (2014-10-20) Huawei Proprietary and Confidential iii

Configuration Guide (CLI) Contents
Contents
About This Document.....................................................................................................................ii

1 Networking Requirements..........................................................................................................1
1.1 Service Requirements and Solutions..............................................................................................................................2
1.2 Introduction to Products Used in the ATN+CX Bearer Solution...................................................................................3
1.3 Network Topology Example and Data Planning for Interfaces......................................................................................6
2 Introduction..................................................................................................................................11
3 Basic Configurations...................................................................................................................12
3.1 Configuring Device Information..................................................................................................................................13
3.2 Configuring User Interfaces.........................................................................................................................................13
3.3 Configuring AAA Users...............................................................................................................................................14
3.4 Configuring SNMP.......................................................................................................................................................16
3.5 Configuring Global BFD..............................................................................................................................................16
4 Configuring IGP..........................................................................................................................17
4.1 Configuring IS-IS.........................................................................................................................................................18
4.1.1 IS-IS Deployment Solution.......................................................................................................................................18
4.1.2 Configuration Principle.............................................................................................................................................19
4.1.3 Data Planning............................................................................................................................................................21
4.1.4 Configuring Basic IS-IS Functions and BFD for IGP...............................................................................................24
5 Deploying MPLS tunnel (RSVP TE and LDP)......................................................................31

5.1 Tunnel Deployment Solution........................................................................................................................................32
5.2 Configuration Principle................................................................................................................................................36
5.3 Data Planning...............................................................................................................................................................37
5.4 Deploying MPLS LDP.................................................................................................................................................41
5.4.1 Configuring MPLS LDP LSP....................................................................................................................................41
5.5 Deploying MPLS TE....................................................................................................................................................45
5.5.1 Configuring MPLS-TE..............................................................................................................................................45
5.5.2 Configuring BFD for TE LSP...................................................................................................................................55
5.5.3 Configuring BFD for TE...........................................................................................................................................58
6 Deploying MPLS Tunnels (BGP LSPs)...................................................................................61

6.1 Deploying MPLS Tunnels (HVPN+Labeled BGP)......................................................................................................62
Issue 03 (2014-10-20) Huawei Proprietary and Confidential iv

6.1.1 MPLS Tunnel Deployment Solution.........................................................................................................................62

6.1.2 Data Planning............................................................................................................................................................65
6.1.3 Configuring BGP LSPs.............................................................................................................................................67
6.1.4 Configuring BFD for BGP Tunnel............................................................................................................................80
6.1.5 Verifying the Configuration......................................................................................................................................81
6.2 Deploying MPLS Tunnels (Labeled BGP to Edge).....................................................................................................84
6.2.1 Tunnel Deployment Solution.....................................................................................................................................84
6.2.2 Data Planning............................................................................................................................................................87
6.2.3 Configuring BGP LSPs.............................................................................................................................................89
6.2.4 Configuring BFD for BGP Tunnel............................................................................................................................94
6.2.5 Verifying the Configuration......................................................................................................................................95
7 Deploying DCN...........................................................................................................................97
7.1 Deployment of a Public DCN.......................................................................................................................................98
7.1.1 Deploying Public DCN Using IS-IS (U2000 Connected to the IPCore Network)....................................................98
7.2 Deploying a DCN VRF Solution................................................................................................................................112
7.2.1 Deploying the DCN Automatically Available Solution (U2000 Connected to the IPCore Network)....................112
7.2.2 Deploying DCN VRF for a Large Network (U2000 Connected to the IPCore Network)......................................118
8 Deploying Mobile Backhaul Services...................................................................................130

8.1 Deploying E2E Mobile Backhaul Services (HVPN+Labeled BGP)..........................................................................131
8.1.1 E2E Ethernet Service Deployment Solution...........................................................................................................131
8.1.2 Configuration Principle...........................................................................................................................................133
8.1.3 Data Planning..........................................................................................................................................................134
8.1.4 Configuring MP-BGP..............................................................................................................................................136
8.1.5 Configuring an L3VPN...........................................................................................................................................144
8.1.6 Deploying Bearer and Protection for Services Between MASGs and SGWs/MMEs.............................................145
8.1.6.1 Configuring VRRP Protection..............................................................................................................................146
8.1.6.2 Configuring Active and Standby Routes for Protection.......................................................................................155
8.1.7 Configuring Protection Switching (at the VPN Layer)...........................................................................................159
8.2 Deploying E2E Mobile Backhaul Services (Labeled BGP to Edge)..........................................................................160
8.2.1 E2E Ethernet Service Deployment Solution...........................................................................................................160
8.2.2 Configuration Principle...........................................................................................................................................163
8.2.3 Data Planning..........................................................................................................................................................163
8.2.4 Configuring MP-BGP..............................................................................................................................................165
8.2.5 Configuring an L3VPN...........................................................................................................................................169
8.2.6 Deploying Bearer and Protection for Services Between MASGs and SGWs/MMEs.............................................170
8.2.6.1 Configuring VRRP Protection..............................................................................................................................171
8.2.6.2 Configuring Active and Standby Routes for Protection.......................................................................................179
8.2.7 Configuring Protection Switching (at the VPN Layer)...........................................................................................184
8.3 Deploying Local Switching Ethernet Service Bearer and Protection (HVPN+Labeled BGP)..................................185
8.3.1 Local Switching Ethernet Service Deployment Solution........................................................................................185
8.3.2 Data Planning..........................................................................................................................................................187
Issue 03 (2014-10-20) Huawei Proprietary and Confidential v

8.3.3 Deploying an L3VPN and Protection......................................................................................................................188

8.4 Deploying Local Switching Ethernet Service Bearer and Protection (Labeled BGP to Edge)..................................191
8.4.1 Local Switching Ethernet Service Deployment Solution........................................................................................191
8.4.2 Data Planning..........................................................................................................................................................193
8.4.3 Deploying an L3VPN and Protection......................................................................................................................194
8.5 Deploying QoS...........................................................................................................................................................198
8.5.1 Deploying QoS for Ethernet Services.....................................................................................................................198
8.5.1.1 Configuration Roadmap.......................................................................................................................................198
8.5.1.2 Data Planning.......................................................................................................................................................199
8.5.1.3 Configuring Priority Mapping..............................................................................................................................200
8.5.1.4 Configuring Queue Scheduling and Bandwidth (Optional).................................................................................203
9 Deploying Enterprise Services................................................................................................205

9.1 P2P Enterprise Service Deployment Solution (HVPN+Labeled BGP)......................................................................206
9.1.1 Deploying Ethernet Service Bearer and Protection.................................................................................................206
9.1.1.1 Configuration Principle........................................................................................................................................206
9.1.1.2 Data Planning.......................................................................................................................................................207
9.1.1.3 Configuring MS-PWs (Ethernet Services)...........................................................................................................207
9.1.1.4 Configuring BFD for PW.....................................................................................................................................217
9.1.2 Deploying TDM Service Bearer and Protection......................................................................................................218
9.1.2.2 Data Planning.......................................................................................................................................................219
9.1.2.3 Configuring MS-PWs...........................................................................................................................................221
9.1.2.4 Configuring BFD for PW.....................................................................................................................................223
9.1.2.5 Verifying the Configuration.................................................................................................................................224
9.2 P2P Enterprise Service Deployment Solution (Labeled BGP to Edge).....................................................................227
9.2.1 Deploying Ethernet Service Bearer and Protection.................................................................................................227
9.2.1.2 Data Planning.......................................................................................................................................................227
9.2.1.3 Configuring SS-PWs............................................................................................................................................228
9.2.2 Deploying TDM Service Bearer and Protection......................................................................................................231
9.2.2.2 Data Planning.......................................................................................................................................................232
9.2.2.3 Configuring SS-PWs............................................................................................................................................233
9.3 MP2MP Enterprise Service Deployment Solution (HVPN+Labeled BGP)..............................................................237
9.3.1 MP2MP Enterprise Service Deployment Solution..................................................................................................238
9.3.2 Data Planning..........................................................................................................................................................238
9.3.3 Configuring H-VPLS...............................................................................................................................................240
9.3.4 Configuring BFD for PW........................................................................................................................................248
9.4 MP2MP Enterprise Service Deployment Solution (Labeled BGP to Edge)..............................................................249
Issue 03 (2014-10-20) Huawei Proprietary and Confidential vi

9.4.1 MP2MP Enterprise Service Deployment Solution..................................................................................................249

9.4.2 Data Planning..........................................................................................................................................................250
9.4.3 Configuring VPLS...................................................................................................................................................251
10 Deploying Clocks....................................................................................................................258
10.1 Configuration Roadmap...........................................................................................................................................259
11 Configuration Files.................................................................................................................261
11.1 Basic Configuration Files.........................................................................................................................................262
11.1.1 Basic Configuration Files (Deployed IGP in ISIS mode).....................................................................................262
11.1.1.1 CSG1 Configuration File....................................................................................................................................263
11.1.1.2 ASG3 Configuration File....................................................................................................................................266
11.1.1.4 (Aggregation layer) ASBR1 Configuration File................................................................................................275
11.1.1.5 (Aggregation Layer) ASBR2 Configuration File...............................................................................................279
11.1.1.6 (Core Layer) ASBR3 Configuration File...........................................................................................................283
11.1.1.8 (Core Layer) RR3 Configuration File................................................................................................................291
11.1.1.9 (Core Layer) RR4 Configuration File................................................................................................................291
11.1.1.10 MASG1 Configuration File..............................................................................................................................292
11.1.2 BGP LSP Configuration File (HVPN+Labeled BGP)..........................................................................................300
11.1.2.4 (Aggregation Layer) RR1 Configuration File....................................................................................................303
11.1.2.10 (Core Layer) RR3 Configuration File..............................................................................................................308
11.1.3 BGP LSP Configuration File (Labeled BGP to Edge)..........................................................................................310
Issue 03 (2014-10-20) Huawei Proprietary and Confidential vii


11.2 E2E Mobile Backhaul Services Configuration File (HVPN+Labeled BGP)...........................................................322
11.2.1 CSG1 Configuration File.......................................................................................................................................323
11.2.2 ASG3 Configuration File.......................................................................................................................................324
11.2.4 (Aggregation Layer) RR1 Configuration File.......................................................................................................327
11.2.6 (Core Layer) RR3 Configuration File...................................................................................................................327
11.2.8 MASG1 Configuration File...................................................................................................................................328
11.3 E2E Mobile Backhaul Services Configuration File (Labeled BGP to Edge)...........................................................332
11.4 Local Switching Ethernet Service Configuration File (HVPN+Labeled BGP).......................................................341
11.5 Local Switching Ethernet Service Configuration File (Labeled BGP to Edge).......................................................342
11.6 P2P Enterprise Service (HVPN+Labeled BGP) Configuration File........................................................................344
11.6.1 Ethernet Service ....................................................................................................................................................344
11.6.1.1 (IPRAN AS100) CSG1 Configuration File........................................................................................................345
11.6.1.2 (IPRAN AS100) ASG3 Configuration File........................................................................................................346
Issue 03 (2014-10-20) Huawei Proprietary and Confidential viii

11.6.1.4 (IPRAN AS300) ASG33 Configuration File......................................................................................................346

11.6.1.6 (IPRAN AS300) CSG31 Configuration File......................................................................................................347
11.6.2 TDM Service.........................................................................................................................................................347
11.7 P2P Enterprise Service (Labeled BGP to Edge) Configuration File........................................................................350
11.7.1 Ethernet Service ....................................................................................................................................................350
11.7.2 TDM Service ........................................................................................................................................................352
11.8 MP2MP Enterprise Service (HVPN+Labeled BGP) Configuration File.................................................................354
11.8.1 (IPRAN AS100) CSG1 Configuration File...........................................................................................................355
11.8.3 (IPRAN AS100) ASG3 Configuration File...........................................................................................................356
11.8.4 (IPRAN AS100) ASG4 Configuration File...........................................................................................................357
11.8.5 (IPRAN AS300) ASG33 Configuration File.........................................................................................................357
11.8.6 (IPRAN AS300) ASG34 Configuration File.........................................................................................................358
11.8.7 (IPRAN AS300) CSG31 Configuration File.........................................................................................................359
11.9 MP2MP Enterprise Service (Labeled BGP to Edge) Configuration File.................................................................359
Issue 03 (2014-10-20) Huawei Proprietary and Confidential ix

Configuration Guide (CLI) 1 Networking Requirements
1 Networking Requirements
About This Chapter
1.1 Service Requirements and Solutions

The MBB ATN+CX solution is designed by Huawei for IP Radio Access Networks (IPRANs).
The Intelligent Dynamic Edge Architecture for LTEHaul (IDEAL) solution is a solution for
ATN+CX networks. This section introduces the IDEAL solution.
1.2 Introduction to Products Used in the ATN+CX Bearer Solution

This section describes the roles, functions, and product models of the devices that are used in
the ATN+CX bearer solution, and the network layers where the devices are used.
1.3 Network Topology Example and Data Planning for Interfaces

Planning proper data for interfaces according to the network topology is the basics of network
configuration.
Issue 03 (2014-10-20) Huawei Proprietary and Confidential 1

1.1 Service Requirements and Solutions

The MBB ATN+CX solution is designed by Huawei for IP Radio Access Networks (IPRANs).
The Intelligent Dynamic Edge Architecture for LTEHaul (IDEAL) solution is a solution for
ATN+CX networks. This section introduces the IDEAL solution.
Service Requirements
In the LTE architecture, there is no RNC. The positions of ePCs (MMEs or SGWs) are higher
than those of BSCs or RNCs. An ePC (MME/SGW) and the SGSN/GGSN of a GSM/UMTS
network belong to the core layer on a wireless network. Normally, they are deployed in the same
equipment room. Therefore, LTE services need to be transmitted across ASs/domains (IPRAN
and IPCore networks). Inter-AS/domain services are the basic drive for inter-AS/domain
streamlining.
Fixed Mobile Convergence (FMC) is a trend of wireless service bearer. More and more private
line and private network services need to be transmitted across metropolitan area networks. In
the private line and private network services, enterprise services are the most important services,
which include:
l P2P L2 enterprise services
l MP2MP L2 enterprise services
l L3 enterprise services
With deployment of an IPRAN, base stations are easy to be homed to base station controllers,
and more options are available for carriers to plan their networks and share resources. RNCs
generally belong to the core layer or other RANs (namely, remote RNC scenarios).
Solution Overview
The IDEAL solution supports E2E MPLS (Seamless MPLS), which eliminates boundaries
between ASs by opening and expanding the original topologies. This solution can significantly
decreases the workload on cooperation and negotiation between network layers during service
deployment, so that carriers can quickly deploy services at lower cost.
The core layer (IPCore) and the aggregation+access layers (IPRAN) belong to different ASs.
Currently, this networking is adopted by most carriers. This manual will mainly use this scenario
as an example. If the core, aggregation, and access layers belong to the same AS, refer to the
HVPN solution.
The IDEAL solution includes two sub-solutions:
l Sub-solution 1: HVPN+Labeled BGP: Segmented tunnels are deployed. A segment of

LDP LSP or TE tunnel is deployed at the access layer; an inter-AS tunnel (BGP LSP set
up using Labeled BGP) is set up between an ASG and MASG; the HVPN solution is used
between the access layer and the aggregation+core layers.

Figure 1-1 HVPN+Labeled BGP sub-solution
AS y AS x
Labeled iBGP Labeled eBGP Labeled iBGP
eNodeB CSGAccesss layer ASG Aggregation layer ASBR 1 ASBR 3 Core layer MASG
IGP domain IGP domian IGP domain
SGW/MME
eNodeB CSG ASG ASBR 2 ASBR 4 MASG
TE/LDP TE/LDP TE/LDP

LSP LSP LSP
HVPN+Labeled BGP LSP
swap
BGP LSP
swap
BGP LSP
BGP solution
L3VPN swap Inter-AS L3VPN
NOTE
Mobile Aggregation Site Gateway (MASG) is named in TR-221: Technical Specifications for MPLS in
Mobile Backhaul Networks.
l Sub-solution 2: Labeled BGP to Edge (E2E L3VPN): RFC 3107 (Option C) is configured
for CSGs to deploy host routes between CSGs and MASGs. E2E L3VPN is deployed at
the service layer.
Figure 1-2 Labeled BGP to Edge sub-solution
AS y AS x
Labeled iBGP Labeled iBGP Labeled eBGP Labeled iBGP
eNodeB CSG Access layer ASG Aggregation layer ASBR 1 ASBR 3 Core layer MASG
IGP domain IGP domain IGP domian
SGW/MME
eNodeB CSG ASG ASBR 2 ASBR 4 MASG
TE/LDP TE/LDP TE/LDP
LSP LSP LSP

swap swap swap
Labeled BGP BGP LSP BGP LSP BGP LSP BGP LSP
to Edge
E2E Inter-AS L3VPN
1.2 Introduction to Products Used in the ATN+CX Bearer

Solution
This section describes the roles, functions, and product models of the devices that are used in
the ATN+CX bearer solution, and the network layers where the devices are used.

Table 1-1 Mapping between solution versions and equipment models and versions
Equipment Role Equipment Model Version
Core Node (P) NE40E-X8/X16 V600R008C00
Core Edge Node (PE) NE40E-X8/X16 V600R008C00
Mobile Aggregation Service CX600-X8/X16

V600R008C00
Gateway (MASG) NE40E-X8/X16
CX600-X3/X8 V600R008C00
Aggregation Node (ASG)
NE40E-X3/X8 V600R008C00
ATN 905/910/910B/910I/
950/950B
Cell Site Gateway (CSG) NOTE V200R003C10
ATN 905s are subordinate to
CSGs.
Network Management
iManager U2000 V200R001C00
System (NMS)
Network Layer Equipment Role Function
User side User equipment (UE) Terminal of a mobile

backhaul network
Base station Base transceiver station BTSs refer to all 2G base

(BTS) stations. A mobile
communication system
consists of a mobile station
(MS), a BTS sub-system, and
a network sub-system. A BTS
sub-system consists of a BTS
and a base station controller
(BSC).
NOTE
A CDMA2000 (3G) base
station is also called a BTS.

NodeB (3G base station) Refers to a base station on a

3G mobile network. NodeBs
interconnect with RNCs
through standard Iub
interfaces and communicate
with UEs through Uu
interfaces, to process
physical-layer protocols of
Uu interfaces and protocols
of Iub interfaces.
eNodeB (E-UTRAN NodeB, Refers to a Long Term

an LTE base station) Evolution (LTE) base station.
Access network Cell site gateway (CSG) Receives and processes

various service signals from
base stations and forwards
them to devices at the
aggregation layer.
Aggregation network Aggregation Site Gateway Aggregates service signals

(ASG) from CSGs and forwards
them.
Radio Service Gateway Connects to base station

(RSG) controllers.
Core network Base Station Controller Mainly manage wireless

(BSC) network resources, cell
documents, positioning units
and switching units, and
control power.
Radio Network Controller Refers to a key node on a 3G

(RNC) network. As part of an access
network, an RNC manages
mobility, links, and the
switching mechanism, and
processes calls.
Mobility management entity MMEs are the key control

(MME) points on an LTE access
network complying with the
3GPP protocol. MMEs are
used to locate idle UEs and
process paging (including
relay).

Service gateway (SGW) Is a type of gateway. An SGW

provides the functionality of
a proxy and a gateway to
implement Wireless
Application Protocol (WAP)
service access, user
authentication, service
control, and service
scheduling. In addition, an
independent SGW can use the
WAP protocol to perform
content-based or volume-
based accounting.
O system NMS Helps users manage and

maintain networks.
Others Autonomous System Refers to a router that

Boundary Router (ASBR) exchanges route information
with other ASs.
Mobile Aggregation Service -

Gateway (MASG)
1.3 Network Topology Example and Data Planning for

Interfaces
Planning proper data for interfaces according to the network topology is the basics of network
configuration.
Network Topology
Create a network based on the topology, set NE names and NE IP addresses, and configure
service interfaces and user interfaces, as shown in Figure 1-3 and Figure 1-4.

Figure 1-3 Network topology
AS 100 AS 200
Access Aggregation Core
RR1 RR3
CSG1 ASG3 ASBR1 ASBR3 MASG1

GE0/2/16 GE2/1/0 GE1/0/1 GE1/0/1
GE1/1/2 GE1/0/0 GE1/0/0 GE1/0/0
GE1/0/0 GE2/0/1 GE2/0/1
GE0/2/17
Eth-Trunk 1
GE0/2/17 GE2/0/1 SGW/MME
GE1/0/0 GE2/0/1
GE1/1/2 GE1/0/0 GE1/0/0 GE1/0/0
GE2/1/0 GE1/0/1 GE1/0/1
GE0/2/16
RR2
RR4
Figure 1-4 Network devices and IP address planning for interfaces

AS 100 AS 200
11.11.11.11//32 13.13.13.13//32
1.1.1.1/32 3.3.3.3/32 5.5.5.5/32 7.7.7.7/32 9.9.9.9/32

10.1.3.0/30 10.3.5.0/30 10.5.7.0/30 10.7.9.0/30
10.9.10.0/30
10.1.2.0/30
10.3.4.0/30
10.5.6.0/30
10.7.8.0/30
10.2.4.0/30 10.4.6.0/30
10.6.8.0/30 10.8.10.0/30
2.2.2.2/32 4.4.4.4/32 6.6.6.6/32 8.8.8.8/32 10.10.10.10/32
12.12.12.12//32 14.14.14.14//32
NOTE
l The data provided in this section is used as an example, which may differ in practice due to the difference
of the network scale and topology.
l RRs are mainly used to set up BGP connection with other routers and to reflect BGP routes. The physical
connections to RRs are diversified. Therefore:
l In this document, only the network positions and loopback0 interface addresses of RRs are
provided. The physical connections, interface addresses, and physical addresses of RRs are not
described in details.
l This document only provides the BGP configuration of RRs. The basic configuration and IGP
configuration of RRs are not described.

Table 1-2 NE IP interface list
NE Role Local Interface IP Address Interface

Description
CSG1 Loopback0 1.1.1.1/32 -
GigabitEthernet0/2/ 10.1.3.1/30 Interface connected

16 to ASG3
GE interface

17 to CSG2
GE interface
CSG2 Loopback0 2.2.2.2/32 -

16 to ASG4
GE interface

17 to CSG1
GE interface
ASG3 Loopback0 3.3.3.3/32 -
GigabitEthernet 10.3.5.1/30 Interface connected

2/1/0 to ASBR1
10GE interface

1/1/2 to CSG1
GE interface

0.1 vlan-type dot1q 1 to ASG4
Sub-interface
Access-side interface

1/0/0 to ASG4
10GE interface
Aggregation-side
interface
ASG4 Loopback0 4.4.4.4/32 -

2/1/0 to ASBR2
10GE interface


Description

2 to CSG2
GE interface

0.1 vlan-type dot1q 1 to ASG3
Sub-interface

1/0/0 to ASG3
10GE interface
RR1 Loopback0 11.11.11.11/32 -
RR2 Loopback0 12.12.12.12/32 -
ASBR1 Loopback0 5.5.5.5/32 -

1/0/1 to ASBR3
10GE interface

1/0/0 to ASG3
10GE interface

2/0/1 to ASBR2
10GE interface

1/0/1 to ASBR4
10GE interface

1/0/0 to ASG4
10GE interface

2/0/1 to ASBR1
10GE interface

1/0/1 to MASG1
10GE interface


Description

1/0/0 to ASBR1
10GE interface

2/0/1 to ASBR4
10GE interface

1/0/1 to MASG2
10GE interface

1/0/0 to ASBR2
10GE interface

2/0/1 to ASBR3
10GE interface
RR3 Loopback0 13.13.13.13/32 -
RR4 Loopback0 14.14.14.14/32 -
MASG1 Loopback0 9.9.9.9/32 -

1/0/0 to ASBR3
10GE interface
GigabitEthernet Eth-Trunk 1.1 Interface connected

1/0/1 10.9.10.1/30 to MASG2
GigabitEthernet vlan-type dot1q 1 10GE interface
2/0/1
MASG2 Loopback0 10.10.10.10/32 -

1/0/0 to ASBR4
10GE interface
GigabitEthernet Eth-Trunk 1.1 Interface connected

1/0/1 10.9.10.2/30 to MASG1
GigabitEthernet vlan-type dot1q 1 10GE interface
2/0/1

Configuration Guide (CLI) 2 Introduction
2 Introduction
In this configuration guide, AS 100 and AS 200 are used as examples to describe how to configure
the HVPN+Labeled BGP and Labeled BGP to Edge sub-solutions of the IDEAL solution.

Configuration Guide (CLI) 3 Basic Configurations
3 Basic Configurations
About This Chapter
For HVPN+Labeled BGP solution and Labeled BGP to Edge solution, configuration is the same.
3.1 Configuring Device Information

Device information mainly includes the host name.
3.2 Configuring User Interfaces

VTY user interfaces need to be configured when users need to log in to a router by means of
Telnet or SSH.
3.3 Configuring AAA Users

This topic describes how to configure user authentication, such as creating user accounts, setting
user passwords, and authenticating users.
3.4 Configuring SNMP

This topic describes how to configure SNMP which allows devices to communicate with the
network management system (NMS).
3.5 Configuring Global BFD

The global bidirectional forwarding detection (BFD) function needs to be configured to detect
faults.

3.1 Configuring Device Information

Device information mainly includes the host name.
Data Planning
NOTE
Set parameter values based on the network conditions such as the network dimensioning and network
topology. The following parameter values are recommended ones in this example and only for reference.
Configure device information on all routers based on the network topology.
Device information includes site names, device models, device roles, and device numbers. Each
device is named in the format of AA-BB-CC.
l AA: device model, for example, ATN910 or CX600-X8

l BB: sit name, for example, AA
l CC: device number, starting from 001
For example, ATN910-AA-001 refers to an ATN910 numbered 001 at site AA.
NOTE
Device roles are used to simplify description. For example, CSG1 stands for ATN910-AA-001. For details,
see "Network Topology" and "Data Planning" in "Service Requirements and Networking".
Parameter Value Description
sysname ATN910-AA-001 Host name
Configuration Procedure
sysname ATN910-AA-001
3.2 Configuring User Interfaces

VTY user interfaces need to be configured when users need to log in to a router by means of
Telnet or SSH.
Data Planning
NOTE

user-interface maximum- 15 Sets the maximum number of

vty users that are allowed to log
in to a router to 15.
NOTE
If the maximum number is set
to 0, no user is allowed to log in
to a router by means of Telnet
or SSH.
user-interface vty 0 14 Indicates that the maximum

number of VTY user
interfaces is the total number
of Telnet and SSH users.
authentication-mode aaa Sets the authentication mode

to AAA authentication for
users that log in to a router.
user privilege level 15 Specifies the command level

to level 15.
idle-timeout 50 Sets the timeout period for

login users.
1. Set the maximum number of VTY user interfaces.
user-interface maximum-vty 15 //Set the maximum number of VTY user interfaces.
2. Configure VTY interface attributes.

In this example, configure SSH as the login method for the user.
user-interface vty 0 14 //Configure VTYs 0-14.
authentication-mode aaa
user privilege level 15
idle-timeout 5 0
protocol inbound ssh
3.3 Configuring AAA Users

This topic describes how to configure user authentication, such as creating user accounts, setting
user passwords, and authenticating users.
Data Planning
NOTE
Create AAA users on all routers.

aaa - Enters the AAA view to

create a user, set a user level,
or configure an
authentication scheme, an
authorization scheme, an
accounting scheme, or a
domain.
User name root Adds a local user root.
Password Changeme_123 -
Local-user level 3 Sets a user level for the local

user. The system manages
commands by command
level. A user can only use the
commands whose levels are
lower than or equal to the user
level.
Configure SSH as the login method for the AAA user.
l Configure the CSG as follows:

aaa
local-user root password cipher Changeme_123//Configure the user name and
password.
local-user root service-type ssh//Configure SSH as the login method for the
user.
local-user root level 15//Configure the user level.
#
stelnet server enable//Enable the STelnet service on the SSH server.
ssh user root//Add an SSH user.
ssh user root authentication-type password//Configure an authentication mode
for the SSH user.
ssh user root service-type stelnet//Configure STelnet as the login method for
the SSH user.
ssh client first-time enable//Enable the first-time authentication on the SSH
client. Thus, when the SSH client is connected to the SSH server for the first
time, the client does not check the validity of the RSA public key of the
server.
#
l Configure the ASG, RR, ASBR and MASG as follows:

aaa
local-user root password irreversible-cipher Changeme_123
local-user root service-type ssh
local-user root level 15
#
stelnet server enable
ssh user root
ssh user root authentication-type password
ssh user root service-type stelnet
ssh client first-time enable

#
undo nap slave enable
NOTE
Requirements on user names and passwords for ATN products:
l If user-security-policy command has been executed, a local user name has 1-253 characters.
Otherwise, a local user name has 6-253 characters.
l Requirements on passwords:
l A password must have eight characters at least.
l A password must contain digits, upper-case and lower-case letters, and special characters
(excluding question mark ? and spaces).
l The password cannot be the same as the user name or the user name inverted.
3.4 Configuring SNMP

This topic describes how to configure SNMP which allows devices to communicate with the
network management system (NMS).
SFor detailed configurations, see the Deploying DCN.
3.5 Configuring Global BFD

The global bidirectional forwarding detection (BFD) function needs to be configured to detect
faults.
Enable the global BFD function on CSGs, ASGs, ASBRs and MASGs. The following
configuration uses CSG1 as an example.
bfd

Configuration Guide (CLI) 4 Configuring IGP
4 Configuring IGP
About This Chapter
Interior Gateway Protocol (IGP) can be deployed in two modes: IS-IS multi-processes and OSPF
multi-areas. This document uses the IS-IS multi-processes as an example. For HVPN+Labeled
BGP solution and Labeled BGP to Edge solution, IGP configuration is the same.
4.1 Configuring IS-IS

his topic describes how to configure different IS-IS processes.

4.1 Configuring IS-IS

his topic describes how to configure different IS-IS processes.
4.1.1 IS-IS Deployment Solution

This topic describes selection and principles of the IS-IS deployment solution
Figure 4-1 is a network diagram of the IS-IS multi-process deployment solution.
Configure different processes for the aggregation ring and its subordinate access rings to isolate
routes from each other. This is to relieve routing burden on CSGs.
The IGP design for the core layer is independent, and it is isolated from the access layer and the
aggregation layer.
Set the cost to control route selection.
Figure 4-1 Network diagram of the IS-IS multi-process solution
AS 100 RR1 AS 200 RR3

Cost 10 Cost 10
Cost 100
IS-IS 1 IS-IS 100

Cost 100
Cost 2000
Cost 25
Cost 10
IS-IS 1000
Cost 10
Cost 25
L2 L2 L2
SGW/MME
Cost 100 Cost 10 Cost 10

RR2 RR4
ISIS interface of Access
ISIS interface of Aggregation
ISIS interface of Core
Use the following principles to configure IS-IS multi-process for the access layer and the
aggregation layer:
1. IS-IS process
l Enable IS-IS for routers in the access ring and configure IS-IS process 1 to advertise
Level-2 routes.
l Enable IS-IS for routers in the aggregation ring and configure IS-IS process 100 to
advertise Level-2 routes.
2. Setting of the cost ensures that routes on the local access ring or the local aggregation ring
are preferred for forwarding IP signaling packets and that IP signaling packets are not
looped through routes between ASGs or ASBRs.
l The cost of an access-layer link is 100. The cost of an aggregation-layer link (including
P devices) is 10. It is recommended that the cost be set to 50 for 1 Gbit/s links, 10 for

10 Gbit/s links, 2 for 40 Gbit/s links, and 1 for 100 Gbit/s links if links of these rates
coexist.
l An AS consists of multiple levels of rings. The cost value of a link on a lower level ring
must be higher than the total cost value of all links on an upper level ring. For example,
in Figure 4-1, the minimum cost value of a link on an access ring is 100, which is greater
that the total cost value (55) of all links on the aggregation ring. Rings in different AS
do not comply with this principle.
l Cost value of the link between the main and standby ASGs of an access ring is 2000,
which is greater than the total cost value of the other links on the ring, so that tunnels
from the CSG to the main and standby ASGs do not share the same path.
l The value cost of the link between the two ASBRs (on the aggregation ring side)
complies with the following principle: (n-1)*10 < cost < n*10, in which n (between
ASBRs) equals to the total number of links on the aggregation ring except for the link
between ASBRs. For example, in Figure 4-1, the cost value of the link between ASBRs
is 25, complying with: (3-1)*10 < 25 < 3*10.
NOTE
The number 10 is the cost vlaue of the links on the aggregation ring (excluding the links between
ASBRs) and is only for reference. Set parameter values based on the network conditions such as the
network dimensioning and network topology.
Use the following principles to configure IS-IS multi-process for the core layer:
1. Enable IS-IS for routers in the access ring and configure IS-IS process 1000 to advertise
Level-2 routes.
2. The value cost of the link between the two MASGs complies with the following principle:
(n-1)*10 < cost < n*10, in which n (between MASGs) equals to the total number of links
on the core ring except for the link between MASGs. For example, in Figure 4-1, the cost
value of the link between MASGs is 25, complying with: (3-1)*10 < 25 < 3*10.
NOTE
The number 10 is the cost vlaue of the links on the core ring (excluding the links between MASGs) and
is only for reference. Set parameter values based on the network conditions such as the network
dimensioning and network topology.
4.1.2 Configuration Principle

This topic provides principles for configuring IS-IS multi-process.
Use the following principles to configure IS-IS multi-process:

Figure 4-2 IS-IS multi-process networking
The access area and the aggregation area

l Enable IS-IS for routers in the access ring and configure IS-IS process 1 to advertise Level-2
routes.
l Enable IS-IS for routers in the aggregation ring and configure IS-IS process 100 to advertise
Level-2 routes.
l Enable NSR on routers in the aggregation area.
l Configure interface IP addresses and loopback interface addresses for devices in the access
and aggregation areas.
l Enable IS-IS and set the cost value for all interfaces in the access and aggregation areas.
l Deploy BFD for IS-IS network-wide to accelerate IS-IS convergence.
l Configure loopback interface addresses on ASGs and configure the ASGs to advertise the
loopback interface addresses to the access area.
The core area

l Enable IS-IS for routers in the core area and configure IS-IS process 1000 to advertise
Level-2 routes.
l Enable NSR on routers in the aggregation area.
l Configure interface IP addresses and loopback interface addresses for devices
l Enable IS-IS and set the cost value for all interfaces
l Deploy BFD for IS-IS network-wide to accelerate IS-IS convergence.
4.1.3 Data Planning

This topic provides the data plan for IS-IS configuration.
NOTE
Table 4-1 IS-IS parameter
Parameter Value Remarks
IS-IS process ID l Access layer: 1 IS-IS processes are enabled.

l Aggregation layer: 100
l Core layer: 1000

network-entity Access layer A Network Entity Title

l CSG1: (NET) is set.
49.0001.0010.0100.1001 NOTICE
.00 The system ID must be unique
on the entire network. Obtain
l ASG3: the system ID using the IP
49.0001.0030.0300.3003 address of the loopback0
.00 interface. The NETs must be
unique. If a NET is not unique,
l ASG4: route flapping may occur.
49.0001.0040.0400.4004
.00
Aggregation layer
l ASG3:
49.0002.0030.0300.3003
.00
l ASG4:
49.0002.0040.0400.4004
.00
l ASBR1:
49.0002.0050.0500.5005
.00
l ASBR2:
49.0002.0060.0600.6006
.00
Core layer
l ASBR3:
49.0003.0070.0700.7007
.00
l ASBR4:
49.0003.0080.0800.8008
.00
l MASG1:
49.0003.0090.0900.9009
.00
l MASG2:
49.0003.0100.1001.0010
.00
is-level Level-2 The level of the router is

configured.
cost-style Wide Routes with the cost style as

wide are received or
advertised.

is-name Same as the device name, for A dynamic host name is

example, is-name is set to configured for the IS-IS
ASG3 for ASG3. process.
isis cost l The cost of links on the Link costs are specified for
access ring except links SPF calculation.
between ASGs is set to
100.
l The cost of links between
ASGs on the access ring
is set to 2000.
ASBRs on the
aggregation ring is set to
25 and the cost of other
links on the aggregation
ring is set to 10.
MASGs on the core ring
is set to 25 and the cost of
other links on the core
ring is set to 10.
timer spf 1 50 50 The maximum delay is set to

1s, the initial delay to 50 ms,
and the incremental delay to
50 ms for SPF calculation.
timer lsp-generation 1 50 50 The maximum delay is set to

1s, the initial delay to 50 ms,
and the incremental delay to
50 ms for generating an LSP.
flash-flood level-2 The LSP fast flooding

function is enabled to
accelerate the convergence of
an IS-IS network..
set-overload on-startup - Set IS-IS processes to be in

the overload state when IS-IS
processes start up.
set-overload on-startup Configured on ASGs. Allows IP prefixes learned

allow external from other protocols to be
advertised when allow is
configured.
bfd all-interfaces enable - Enable BFD for IS-IS.

4.1.4 Configuring Basic IS-IS Functions and BFD for IGP

This topic describes how to deploy the multi-process IS-IS in different ASs.
Configuring the CSGs

The following uses CSG1 as an example to describe how to configure IS-IS.
NOTE
CSGs use ATN devices. ATN devices enable NSR by default.
l Enable IS-IS globally.
isis 1
is-level level-2 //Configure the device as a Level-2 router.
cost-style wide //Set the cost style of the received and sent IS-IS routes to
wide.
timer lsp-generation 1 50 50 level-2 //Set the delay in generating LSPs.
flash-flood level-2 //Enable LSP fast flooding to accelerate IS-IS network
convergence.
bfd all-interfaces enable //Configure BFD for IS-IS.
bfd all-interfaces min-tx-interval 100 min-rx-interval 100 //Configure the
BFD detection period as 100 ms.
network-entity 49.0001.0010.0100.1001.00 //Configure NET.
is-name CSG1 //Configure a dynamic host name for IS-IS processes.
timer spf 1 50 50 //Configure the delay in route computation using SPF.
traffic-eng level-2 //Enable IS-IS TE.
log-peer-change //Turn on the IS-IS peer state change output switch and write
the IS-IS peer state change in the log.
set-overload on-startup //Set IS-IS processes to be in the overload state when
IS-IS processes start up.
l Configure the IP address of an interface.

#
interface GigabitEthernet0/2/16
description To asg3
undo shutdown
ip address 10.1.3.1 255.255.255.252
#
#
description To csg2
undo shutdown
ip address 10.1.2.1 255.255.255.252
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.255
l Enable IS-IS on the interface.

#
isis enable 1
isis cost 100
#
isis enable 1
isis cost 100
#
interface LoopBack0
isis enable 1
#
NOTE
The configurations of the other CSGs are similar to those of the CSG1 and are not mentioned here.

Configuring the ASGs

The following uses ASG3 as an example to describe how to configure IS-IS.
l Enable the device to support NSR.

switchover mode nonstop-routing //Enable the CX device to support NSR.

#
isis 1 //Configure an IS-IS process on the access ring.
is-level level-2
cost-style wide
timer lsp-generation 1 50 50 level-2
flash-flood level-2
bfd all-interfaces enable
bfd all-interfaces min-tx-interval 100 min-rx-interval 100
network-entity 49.0001.0030.0300.3003.00
is-name ASG3
timer spf 1 50 50
traffic-eng level-2
log-peer-change
set-overload on-startup allow external//Configure IS-IS process 1 to enter the
overload
state during the startup, allows IP
prefixes learned from other protocols to be advertised.
#
isis 100 //Configure an IS-IS process on the aggregation ring.
is-level level-2
cost-style wide
flash-flood level-2
network-entity 49.0002.0030.0300.3003.00
is-name ASG3
timer spf 1 50 50
traffic-eng level-2
log-peer-change
set-overload on-startup

#interface GigabitEthernet2/1/0
description To asbr1
undo shutdown
ip address 10.3.5.1 255.255.255.252
#
#interface GigabitEthernet1/1/2
description To csg1
undo shutdown
ip address 10.1.3.2 255.255.255.252
#
#
interface GigabitEthernet1/0/0 //interface on the aggregation ring.
description To asg4
undo shutdown
ip address 10.3.4.5 255.255.255.252
#
#
interface GigabitEthernet1/0/0.1 //interface on the access ring.
vlan-type dot1q 1
description To asg4
undo shutdown
ip address 10.3.4.1 255.255.255.252
#

#interface LoopBack0
ip address 3.3.3.3 255.255.255.255
#

isis enable 100
isis enable 1
isis cost 100
interface GigabitEthernet1/0/0 //interface on the aggregation ring.
isis enable 100
interface GigabitEthernet1/0/0.1 //interface on the access ring.
isis enable 1
isis cost 2000
interface LoopBack0
isis enable 100
l Configure a routing policy to advertise the Loopback0 route of ASG to the access area.
– Configure the ip-prefix list.
ip ip-prefix loopback0 index 10 permit 3.3.3.3 32
– Configure the routing policy.

#
route-policy loopback0 permit node 10
if-match ip-prefix loopback0
#
– Import the loopback0 route of ASG3 to IS-IS processes of access area.

isis 1
import-route direct cost 10000 route-policy loopback0//Import the
loopback0 route with the cost of 10000 to IS-IS 1.
NOTE
The configurations of the master ASG (ASG3) are similar to those of the slave ASG (ASG4) and are not
mentioned here.
Configuring RRs at the Aggregation Layer

RRs are mainly used to set up BGP connection with other routers and to reflect BGP routes. The
physical connections to RRs are diversified. The requirement on connections to an RR is as
follows:
l The ping command must be run on ASGs and ASBRs at the aggregation layer to test the
network connectivity. The ASGs and ASBRs and the Loopback0 interface of the RR can
ping each other successfully.
Configuring ASBRs at the Aggregation Layer

The following uses ASBR1 as an example to describe how to configure IS-IS.
switchover mode nonstop-routing

isis 100
is-level level-2
cost-style wide
flash-flood level-2
network-entity 49.0002.0050.0500.5005.00

is-name ASBR1
timer spf 1 50 50
traffic-eng level-2
log-peer-change

port-tx-enabling-delay 300000 //Enable the signal sending delay function and
configure the signal sending delay.
undo shutdown
ip address 10.5.7.1 255.255.255.252
#
#
description To asg3
undo shutdown
ip address 10.3.5.2 255.255.255.252
#
#
undo shutdown
ip address 10.5.6.1 255.255.255.252
#
NOTE
If the links between ASBRs are GE interfaces that work in full duplex mode or 10GE interfaces that do
not support 802.3ae, configure BFD for the interfaces on the links between ASBRs in the aggregation
layer and ASBRs in the core layer.
#
bfd link_01 bind peer-ip default-ip interface Gigabitethernet 1/0/1
discriminator local 507
discriminator remote 705
min-tx-interval 10
min-rx-interval 10
process-pst
process-interface-status
commit
#
interface LoopBack0
ip address 5.5.5.5 255.255.255.255

isis enable 100
isis enable 100
isis cost 25
interface LoopBack0
isis enable 100
NOTE
The configurations of the slave ASBR (ASBR2) are similar to those of the master ASBR (ASBR1) and are
not mentioned here.
Configuring ASBRs at the Core Layer

The following uses ASBR3 as an example to describe how to configure IS-IS.



isis 1000
is-level level-2
cost-style wide
flash-flood level-2
bfd all-interfaces
enable
network-entity 49.0003.0070.0700.7007.00
is-name ASBR3
timer spf 1 50 50
traffic-eng level-2
log-peer-change

#
port-tx-enabling-delay 300000 //Enable the signal sending delay function and
configure the signal sending delay.
undo shutdown
ip address 10.5.7.2 255.255.255.252
#
description To masg1
undo shutdown
ip address 10.7.9.1 255.255.255.252
#
#
undo shutdown
ip address 10.7.8.1 255.255.255.252
#
NOTE
If the links between ASBRs are GE interfaces that work in full duplex mode or 10GE interfaces that do
not support 802.3ae, configure BFD for the interfaces on the links between ASBRs in the aggregation
layer and ASBRs in the core layer.
#
bfd link_01 bind peer-ip default-ip interface Gigabitethernet 1/0/0
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
interface LoopBack0
ip address 7.7.7.7 255.255.255.255

isis enable 1000
#
isis enable 1000
#
interface LoopBack0
isis enable 1000

NOTE
The configurations of the slave ASBR (ASBR4) are similar to those of the master ASBR (ASBR3) and are
not mentioned here.
Configuring RRs at the Core Layer

RRs are mainly used to set up BGP connection with other routers and to reflect BGP routes. The
physical connections to RRs are diversified. The requirement on connections to an RR is as
follows:
l Run the ping command on NASGs and ASBRs at the core layer to test the network
connectivity. The MASGs and ASBRs and the Loopback0 interface of the RR can ping
each other successfully.
Configuring MASGs at the Core Layer

The following uses MASG1 as an example to describe how to configure IS-IS.


isis 1000
is-level level-2
cost-style wide
flash-flood level-2
bfd all-interfaces
enable
network-entity 49.0003.0090.0900.9009.00
is-name MASG1
timer spf 1 50 50
traffic-eng level-2
log-peer-change

undo shutdown
ip address 10.7.9.2 255.255.255.252
#
interface Eth-trunk 1 //Create an ETH-trunk interface.
#
undo shutdown
eth-trunk 1//Add the current interface to Eth-trunk 1.
#
undo shutdown
eth-trunk 1//Add the current interface to Eth-trunk 1.
#
interface Eth-trunk 1.1
vlan-type dot1q 1
undo shutdown
ip address 10.9.10.1 255.255.255.252
#
interface LoopBack0
ip address 9.9.9.9 255.255.255.255


#
isis enable 1000
#
isis enable 1000
isis cost 25
#
interface LoopBack0
isis enable 1000
NOTE
The configurations of the slave MASG (MASG2) are similar to those of the master MASG (MASG1) and
are not mentioned here.

Configuration Guide (CLI) 5 Deploying MPLS tunnel (RSVP TE and LDP)
5 Deploying MPLS tunnel (RSVP TE and LDP)
About This Chapter
This topic describes how to deploy MPLS and create MPLS tunnels to bear services. Configuring
both TE tunnels and LDP LSPs to bear services is recommended in this solution. End-to-end
services are carried over TE tunnels, and local switching services are carried over LDP LSPs.
5.1 Tunnel Deployment Solution

This topic describes how to deploy outer MPLS tunnels. Deploying both RSVP TE tunnels and
LDP LSPs is recommended.
5.2 Configuration Principle

This topic provides principles for configuring outer MPLS tunnels.
5.3 Data Planning

This topic provides the data plan for configuring MPLS tunnels.
5.4 Deploying MPLS LDP

This topic describes how to deploy MPLS LDP to generate LSPs for carrying services.
5.5 Deploying MPLS TE

This topic describes how to deploy Multi-Protocol Label Switching Traffic Engineer (MPLS
TE) to create TE tunnels for carrying services.

5.1 Tunnel Deployment Solution

This topic describes how to deploy outer MPLS tunnels. Deploying both RSVP TE tunnels and
LDP LSPs is recommended.
For IDEAL solution, in the same AS, the outer tunnel is MPLS TE or LDP tunnel; There is no
outer MPLS TE or LDP tunnel between the ASBRs connecting different ASs.
MPLS tunnels can be RSVP-TE tunnels or LDP LSPs.

l The LDP protocol is simple, and therefore LDP LSPs are easy to configure. You only need
to enable LDP on interfaces, and do not need to configure LSPs in point-to-point mode.
l The RSVP-TE protocol is complex, and therefore RSVP-TE tunnels are complex to
configure. RSVP-TE tunnels must be configured in point-to-point mode.
RSVP TE+LDP LSP Deployment Solution (Recommended)

RSVP-TE+LDP can be used to bear LTE services. As S1 services have high requirement for
protection switching and X2 services need to be transmitted through the shortest path, use TE
tunnels to bear S1 services and LDP LSPs to bear X2 services.
Figure 5-1 RSVP-TE LSP networking (AS100)
Last Mile Access Aggregation

CSG1 A ASG3 B ASBR1
1 2
4
7
3
E
5
C 6
CSG2 ASG4 D ASBR2
Working Tunnel
Backup Tunnel
NOTE
Interfaces A through E in the preceding figure are constrained interfaces of TE tunnels 1 through 7.
Table 5-1 Constrained interfaces of TE tunnels
TE Tunnel Constrained Interface Constraint Mode
TE1 A Loose

TE2 B Loose
TE3 C Loose
TE4 B Loose
TE5 D Loose
TE6 D Loose
TE7 E Strict
RSVP-TE is deployed network-wide, with IGP fast convergence and network-wide deployment
of BFD for IGP. to accelerate node protection.
l Configure loose explicit paths for MPLS TE tunnels.
l Configure hot standby for MPLS TE tunnel protection.
l Enable IGP fast convergence.
l Configure BFD FOR TE-LSP and BFD for TE on the access and aggregation rings. (BFD
FOR TE-LSP and BFD for TE needn't to be configured on the tunnel between ASGs and
the tunnel between ASBRs in the aggregation layer.)
l For the TE tunnel between an ASBR pair (TE7 in this example), configure a strictly
constrained interface for both the upstream and downstream directions only of the primary
LSP. In this example, configure the strictly constrained interface E for both the upstream
and downstream directions only of the primary LSP of TE tunnel 7.
Figure 5-2 LDP LSP networking (AS100)

CSG1 A ASG3 B ASBR1
1 2
4
7
3
5 E
C 6
CSG2 ASG4 D ASBR2
Working Tunnel
Backup Tunnel

Basic LDP LSP configurations are performed, with IGP fast convergence to accelerate node
protection. And deployment of BFD for IGP on the access ring.
l BFD FOR LDP LSP is not required on the access and aggregation rings.
l Configure LDP-IGP synchronization to ensure synchronous revertive switching.
l Set prefix-priority to high for all host routes identified by LSR-IDs if LSP convergence is
too slow. This configuration is optional and not needed in most cases.
Figure 5-3 RSVP-TE LSP networking (AS200)
Core
ASBR3 I MASG1
10
12 13
F 9 H
11
ASBR4 G MASG2
Working Tunnel
Backup Tunnel
NOTE
Interfaces F through I in the preceding figure are constrained interfaces of TE tunnels 8 through 13.
Table 5-2 Constrained interfaces of TE tunnels
TE8 I Loose
TE9 G Loose
TE10 I Loose
TE11 G Loose

TE12 F Strict
TE13 H Strict
RSVP-TE is deployed network-wide, with IGP fast convergence and network-wide deployment
of BFD for IGP. to accelerate node protection.
l Configure loose explicit paths for MPLS TE tunnels.
l Configure hot standby for MPLS TE tunnel protection.
l Configure BFD FOR TE-LSP and BFD for TE. (BFD FOR TE-LSP and BFD for TE needn't
to be configured on the tunnel between MASGs and the tunnel between ASBRs in the core
layer.)
l For the TE tunnel between an ASBR pair (TE12 and TE13in this example), configure a
strictly constrained interface for both the upstream and downstream directions only of the
primary LSP. In this example, configure the strictly constrained interface E for both the
upstream and downstream directions only of the primary LSP of TE tunnel 12 adn TE
tunnel13.
Figure 5-4 LDP LSP networking (AS200)
Core
ASBR3 MASG1
ASBR4 MASG2

Basic LDP LSP configurations are performed, with IGP fast convergence to accelerate node
protection.
l Configure LDP-IGP synchronization to ensure synchronous revertive switching.
l Set prefix-priority to high for all host routes identified by LSR-IDs if LSP convergence is
too slow. This configuration is optional and not needed in most cases.
5.2 Configuration Principle

This topic provides principles for configuring outer MPLS tunnels.

Figure 5-5 Flowchart for configuring both MPLS TE tunnels and LDP LSPs to carry services
5.3 Data Planning

This topic provides the data plan for configuring MPLS tunnels.
NOTE
Set parameter values based on the network conditions such as the network dimensioning and network topology.
The following parameter values are recommended ones in this example and only for reference.

MPLS TE Tunnel Data Planning
Table 5-3 MPLS parameters
MPLS LSR ID Configure the IP address of Configuring LSR IDs for

loopback0 on the LSR as the devices is the prerequisite for
LSR ID. running MPLS commands.
MPLS label allocation mode non-null The ATN device at the egress
allocates the non-null label to
the penultimate hop.
Therefore, run this command
on the CX to ensure that the
ATN interconnects to the CX
device by using MPLS.
MPLS TE mpls te Enable MPLS TE.
MPLS RSVP-TE mpls rsvp-te Enable MPLS RSVP-TE.
RSVP-TE Hello mechanism mpls rsvp-te hello Enable the RSVP-TE Hello
mechanism.
MPLS TE CSPF algorithm mpls te cspf Enable the MPLS TE CSPF

algorithm.
MPLS RSVP-TE summary mpls rsvp-te srefresh Enable MPLS RSVP-TE

refreshing summary refreshing.
BFD for RSVP-TE mpls rsvp-te bfd all- Enable MPLS RSVP-TE
interfaces enable BFD.
BFD period 100 ms Set this parameter to 100 ms.
Table 5-4 MPLS TE tunnel parameters
Name of a tunnel interface Tunnel ID: interface Tunnel Create a tunnel interface.
0/0/XY
XY: device numbers for the
source and destination nodes
Tunnel interface IP address ip address unnumbered Set the tunnel interface IP

interface LoopBack0 address to the IP address of
the Loopback0 interface.
Tunnel protocol mpls te Set the tunnel type to CR-

LSP.

Tunnel destination address IP address of the remote Specifies a destination IP

Loopback0 interface address.
Tunnel ID Tunnel ID format: XY Specifies a tunnel ID.

XY: device numbers for the
source and destination nodes
TunnelHSB mode mpls te backup hot-standby Currently, the tunnels work

mode revertive wtr 60 in HSB mode. Set the back-
switch time (for example:
60s) according to actual
scenarios.
Tunnel re-optimization mpls te reoptimization It is recommended to set the

frequency 3600 interval of tunnel re-
optimization to 3600s.
Tunnel policy tunnel-policy XXX

Tunnel policy name: IPRAN
tunnel select-seq cr-lsp
load-balance-number 1
BFD for TE-LSP bfd bind mpls-te interface Configure BFD detection and
Tunnel0/0/XY te-lsp the active LSP bound to the
Local discriminator: active VPN tunnel.
discriminator local Set the local discriminator
Remote discriminator: and the remote discriminator
discriminator remote to the same value. For ATNs,
Set the BFD period to 10 ms: the value range of a local
min-tx-interval 10 , min-rx- discriminator is 1 to 255. For
interval 10. CX600s, the value range of a
local discriminator is 1 to
Modify the port status table 8191.
(PST): process-pst.
Set the minimum interval at
Commit the configurations: which BFD packets are sent
commit. as required. Detection period
= Detection multiplier x
Interval at which BFD
packets are sent (3 x 10 ms)
Allow the BFD session to
change the PST to speed up
the switching.

BFD for TE bfd bind mpls-te interface Configure the active VPN
Tunnel0/0/XY tunnel used for BFD.
Local discriminator: Set the local discriminator
discriminator local and the remote discriminator
Remote discriminator: to the same value. For ATNs,
discriminator remote the value range of a local
Set the BFD period to 50 ms: discriminator is 1 to 255. For
min-tx-interval 50 , min-rx- CX600s, the value range of a
interval 50. local discriminator is 1 to
8191.
Modify the PST: process-
pst. Set the minimum interval at
which BFD packets are sent
Commit the configurations: as required. Detection period
commit. = Detection multiplier x
Interval at which BFD
packets are sent (3 x 50 ms)
Allow the BFD session to
change the PST to speed up
the switching.
Table 5-5 MPLS TE tunnel list
Tunnel Tunnel Interface tunnel ID
TE1 CSG1: Tunnel0/0/13 13

ASG3: Tunnel0/0/31 31
TE2 ASG3: Tunnel0/0/35 35

ASBR1: Tunnel0/0/53 53
TE3 CSG1: Tunnel0/0/14 14

ASG4: Tunnel0/0/41 41





Tunnel Tunnel Interface tunnel ID
TE8 ASBR3: Tunnel0/0/79 79

MASG1: Tunnel0/0/97 97




TE13 MASG1: Tunnel0/0/910 910

MPLS LDP LSP Data Planning
Table 5-6 MPLS parameters
Table 4 MPLS parameters Value Remarks

Parameter
mpls lsr-id The IP address of loopback 0 Before running other MPLS

is specified as the LSR ID. commands, configure LSR
IDs for devices.
label advertise non-null Configure the function that

the egress assigns non-null
labels to the penultimate hop.
ATN devices function as that
by default.
lsp-trigger host A policy of establishing LSPs

is to trigger FEC for all IGP
routes.
5.4 Deploying MPLS LDP

This topic describes how to deploy MPLS LDP to generate LSPs for carrying services.
5.4.1 Configuring MPLS LDP LSP

This topic describes how to configure MPLS LDP LSP in different ASs.

Configuring the CSG

The following uses CSG1 as an example to describe how to configure MPLS LDP.
1. Enable MPLS globally.

mpls lsr-id 1.1.1.1
mpls
lsp-trigger host //Set the mechanism to trigger LSP to host (default).
2. Enable MPLS LDP globally.

mpls ldp
3. Enable MPLS LDP on the interface.

mpls
mpls ldp
mpls
mpls ldp
4. Configure LDP route selection to be consistent with IGP route selection.

isis ldp-sync
isis timer ldp-sync hold-max-cost 60 //Configure an interval at which IS-IS
sends Link State PDUs (LSPs) with the maximum route cost. The default value is
10s.
isis ldp-sync
isis timer ldp-sync hold-max-cost 60
Configuring the ASG

The following uses ASG3 as an example to describe how to configure MPLS LDP.

mpls lsr-id 3.3.3.3
mpls
label advertise non-null //Configure the function that the egress assigns non-
null labels to the penultimate hop.
//ATN devices function as that by default.

mpls ldp

mpls
mpls ldp
mpls
mpls ldp
mpls
mpls ldp

isis ldp-sync
isis ldp-sync

isis ldp-sync
interface GigabitEthernet1/0/0.1
isis ldp-sync
Configuring an ASBR at the Aggregation Layer

The following uses ASBR1 as an example to describe how to configure MPLS LDP.

mpls lsr-id 5.5.5.5
mpls
label advertise non-null
lsp-trigger host

mpls ldp

mpls
mpls ldp
mpls
mpls ldp

isis ldp-sync
isis ldp-sync

There are two scenarios for configuring an RR:
l If the RR is mounted to an ASG or ASBR at the aggregation layer, it is not a P and MPLS
LDP does not need to be configured for the RR.
l If the RR is deployed between an ASG and ASBR at the aggregation layer, it is a P of the
aggregation layer and MPLS LDP must be configured it. For details about the configuration,
see the part for ASGs.
Configuring an ASBR at the Core Layer

The following uses ASBR3 as an example to describe how to configure MPLS LDP.

mpls lsr-id 7.7.7.7
mpls
lsp-trigger host

mpls ldp

mpls
mpls ldp
mpls
mpls ldp

isis ldp-sync
isis ldp-sync
Configring RRs at the Core Layer

l If the RR is mounted to an MASG or ASBR at the core layer, it is not a P and MPLS LDP
does not need to be configured for the RR.
l If the RR is deployed between an MASG and ASBR at the core layer, it is a P of the core
layer and MPLS LDP must be configured it. For details about the configuration, see the
part for MASGs.
Configuring an MASG at the Core Layer

The following uses MASG1 as an example to describe how to configure MPLS LDP.

mpls lsr-id 9.9.9.9

mpls
mpls ldp

mpls
mpls ldp
interface Eth-Trunk 1.1
mpls
mpls ldp

isis ldp-sync
interface Eth-Trunk 1.1
isis ldp-sync
Checking the Configuration

Run the display mpls ldp session all command to query the status of MPLS LDP sessions.
>display mpls ldp session all
LDP Session(s) in Public Network

Codes: LAM(Label Advertisement Mode), SsnAge Unit(DDDD:HH:MM)
A '*' before a session means the session is being deleted.

------------------------------------------------------------------------------
PeerID Status LAM SsnRole SsnAge KASent/Rcv
------------------------------------------------------------------------------
1.1.1.1:0 Operational DU Active 0002:22:59
17038/17042
4.4.4.4:0 Operational DU Passive 0000:18:11 4365/4364
5.5.5.5:0 Operational DU Passive 0003:05:11
18525/18525
------------------------------------------------------------------------------
TOTAL: 3 session(s) Found.
5.5 Deploying MPLS TE

This topic describes how to deploy Multi-Protocol Label Switching Traffic Engineer (MPLS
TE) to create TE tunnels for carrying services.
5.5.1 Configuring MPLS-TE

This topic describes how to configure explicit paths for MPLS TE tunnels in different ASs.
Configuring the CSG

The following uses CSG1 as an example to describe how to configure MPLS TE for CSGs on
the access ring.
1. Enable IGP TE.

The IGP TE has been enabled during IGP deployment.
2. Configure global MPLS.

mpls lsr-id 1.1.1.1 //Configure an MPLS LSR ID. The address of a loopback
interface is recommended.
mpls //Enable MPLS globally.
mpls te //Enable MPLS TE globally.
mpls rsvp-te //Enable RSVP-TE.
mpls rsvp-te bfd all-interfaces enable //Enable BFD for RSVP-TE.
mpls rsvp-te bfd all-interfaces min-tx-interval 100 min-rx-interval 100 //
Configure the BFD detection period as 100 ms.
mpls rsvp-te hello //Enable the Hello mechanism for RSVP-TE globally.
mpls te cspf //Enable the CSPF algorithm.
mpls rsvp-te srefresh //Enable the RSVP-TE Srefresh feature.
3. Enable MPLS TE on interfaces.

mpls //Enable MPLS for interfaces.
mpls te //Enable MPLS TE on interfaces.
mpls rsvp-te //Enable RSVP-TE for interfaces.
mpls rsvp-te hello //Enable the Hello mechanism for RSVP-TE on interfaces.
mpls //Enable MPLS for interfaces.
mpls te //Enable MPLS TE on interfaces.
mpls rsvp-te //Enable RSVP-TE for interfaces.
mpls rsvp-te hello //Enable the Hello mechanism for RSVP-TE on interfaces.
4. Configure explicit paths.

explicit-path main_1to3 //Specify the primary CR-LSP that is from CSG1 to
ASG3.
next hop 10.1.3.2 include loose //Set the next hop of the LSP to the IP address
of the interface that connects the master ASG and the access ring.
//The path constraint mode is loose
constraint.
//The loose profile is recommended for configuring

explicit paths to facilitate node addition in future.

explicit-path main_1to4 //Specify the primary CR-LSP that is from CSG1 to
ASG4.
of the interface that connects the slave ASG and the access ring.
constraint.
5. Configure MPLS TE tunnels.
#
interface Tunnel0/0/13 //Specify the tunnel that is from CSG1 to ASG3 (master
ASG).
ip address unnumbered interface LoopBack0 //Use the IP address of a loopback
interface for the IP address of the tunnel.
tunnel-protocol mpls te //Set the tunnel protocol to MPLS TE.
destination 3.3.3.3 //Set the destination address of the tunnel to the IP
address of ASG3.
mpls te tunnel-id 13 //Configure the tunnel ID. The tunnel ID must be valid
and unique on the local device.
mpls te record-route label //Enable the record of routes and labels. The
recorded information is used for maintenance.
mpls te path explicit-path main_1to3 //Specify the primary CR-LSP that is from
CSG1 to ASG3.
mpls te backup hot-standby mode revertive wtr 60 //Set the tunnel mode to hot-
standby. The default WTR time is 10s. Set the WTR to a required value.
//In this example, the WTR
time is set to 60s.
mpls te backup hot-standby overlap-path path //Configure hot-standby CR-LSP
overlap for the working tunnel to maximize protection for the tunnel
when non-overlap paths are
faulty.
mpls te reoptimization //Enable the re-optimization function for the working
tunnel and the re-optimization interval uses default value 3600s.
mpls te commit //Commit all MPLS TE configurations for the tunnel. The
configurations can take effect only after this command is executed.
#
#
interface Tunnel0/0/14 //Specify a tunnel interface for the tunnel between CSG1
and ASG4 (slave ASG).
ip address unnumbered interface
LoopBack0
tunnel-protocol mpls
te
destination 4.4.4.4
mpls te tunnel-id
14
mpls te record-route
label
mpls te path explicit-path main_1to4
mpls te backup hot-standby mode revertive wtr
60
mpls te backup hot-standby overlap-
path
mpls te
reoptimization
mpls te commit
6. Configure a tunnel policy.
#
tunnel-policy IPRAN //Configure a tunnel policy.
tunnel select-seq cr-lsp lsp load-balance-number 1 //CR-LSP tunnels are
selected with preference.
#
Configuring the ASG

The following uses ASG3 as an example to describe how to configure MPLS TE for ASGs.

1. Enable IGP TE.

2. Configure global MPLS TE.
mpls lsr-id 3.3.3.3
mpls
mpls te
mpls rsvp-te
mpls rsvp-te bfd all-interfaces enable
mpls rsvp-te bfd all-interfaces min-tx-interval 100 min-rx-interval 100
mpls rsvp-te hello
label advertise non-null //Configure the function that the egress assigns non-
null labels to the penultimate hop.
// ATN devices function as that by default.
mpls te cspf
mpls rsvp-te srefresh

mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello

explicit-path main_3to1 //Specify the primary CR-LSP that is from ASG3 to
CSG1.
of the interface that connects the master ASG and the access ring.
constraint.
ASBR1.
of the interface that connects the master ASBR and the left side of the
aggregation ring.
ASBR2.
of the interface that connects the slave ASBR and the left side of the
aggregation ring.

#
interface Tunnel0/0/31
LoopBack0
te
destination 1.1.1.1
mpls te tunnel-id 31

label
mpls te path explicit-path
main_3to1
60
path
mpls te
reoptimization
mpls te
commit
#
LoopBack0
te
destination 5.5.5.5
label
main_3to5
60
path
mpls te
reoptimization
mpls te
commit
#
interface
Tunnel0/0/36
LoopBack0
te
destination 6.6.6.6
mpls te tunnel-id
36
label
main_3to6
60
path
mpls te
reoptimization
mpls te
commit
#

#
#
NOTE
The configurations of the slave ASG (ASG4) are similar to those of the master ASG (ASG3) and are not
mentioned here.


l If the RR is mounted to an ASG or ASBR at the aggregation layer, it is not a P and MPLS
TE does not need to be configured for the RR.
l If the RR is deployed between an ASG and ASBR at the aggregation layer, it is a P of the
aggregation layer and MPLS TE must be configured it. For details about the configuration,
see the part for ASGs.
– Enable IGP TE.
– Configure global MPLS TE.
– Enable MPLS TE on interfaces.
Configuring the ASBR at the Aggregation Layer

The following uses ASBR1 as an example to describe how to configure MPLS TE for ASBRs.
1. Enable IGP TE.
mpls lsr-id 5.5.5.5
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls te cspf

mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls
NOTE
Enable MPLS function on the interfaces between ASBR1 and ASBR3. Enable MPLS function on the
interfaces between ASBR2 and ASBR4.
explicit-path main_5to3 //Specify the primary CR-LSP that is from ASBR1 to
ASG3.
aggregation ring.
constraint.
ASG4.

aggregation ring.
constraint.
ASBR2.
next hop 10.5.6.2 include strict //Set the next hop of the LSP to the IP
address of the interface that connects the slave ASBR and the master ASBR.
//The path constraint mode is strict
constraint.

#
LoopBack0
te
destination 3.3.3.3
label
main_5to3
60
path
mpls te
reoptimization
mpls te
commit
#
LoopBack0
te
destination 4.4.4.4
label
main_5to4
60
path
mpls te
reoptimization
mpls te
commit
#
LoopBack0
te
destination 6.6.6.6
label
main_5to6
60

path
mpls te
reoptimization
mpls te
commit
#

#
tunnel-policy IPRAN
tunnel select-seq cr-lsp lsp load-balance-number 1
#
NOTE
The configurations of the slave ASBR (ASBR2) are similar to those of the master ASBR (ASBR1) and are not
mentioned here.
Configuring the ASBR at the Core Layer

The following uses ASBR3 as an example to describe how to configure MPLS TE for ASBRs.
1. Enable IGP TE.

mpls lsr-id 7.7.7.7
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls te cspf

mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls
NOTE
Enable MPLS function on the interfaces between ASBR1 and ASBR3. Enable MPLS function on the
interfaces between ASBR2 and ASBR4.
MASG1.
of the interface that connects the master MASG and the left side of the core
ring.
constraint.
MASG2.

next hop 10.8.10.2 include loose //Set the next hop of the LSP to the IP
address of the interface that connects the slave MASG and the left side of the
core ring.
constraint.
ASBR4.
address of the interface that connects the slave ASBR and the master ASBR.
constraint.

#
LoopBack0
te
destination 9.9.9.9
label
main_7to9
60
path
mpls te
reoptimization
mpls te
commit
#
#
interface
Tunnel0/0/710
LoopBack0
te
destination
10.10.10.10
mpls te tunnel-id
710
label
main_7to10
60
path
mpls te
reoptimization
mpls te
commit
#
LoopBack0
te
destination 8.8.8.8
label


main_7to8
60
path
mpls te
reoptimization
mpls te
commit
#

#
#
NOTE
mentioned here.
Configring RRs at the Core Layer

l If the RR is mounted to an MASG or ASBR at the core layer, it is not a P and MPLS TE
does not need to be configured for the RR.
l If the RR is deployed between an MASG and ASBR at the core layer, it is a P of the core
layer and MPLS TE must be configured it. For details about the configuration, see the part
for MASGs.
– Enable IGP TE.
– Configure global MPLS TE.
– Enable MPLS TE on interfaces.
(Core layer) Configuring the MASG

The following uses MASG1 as an example to describe how to configure MPLS TE for MASGs.
1. Enable IGP TE.

mpls lsr-id 9.9.9.9
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls te cspf

mpls
mpls te

mpls rsvp-te
mpls rsvp-te hello
interface Eth-Trunk1.1
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello

explicit-path main_9to7 //Specify the primary CR-LSP that is from MASG1 to
ASBR3.
ring.
constraint.
ASBR4.
ring.
constraint.
MASG2.
address of the interface that connects the master MASG and the slave MASG.
constraint.

#
LoopBack0
te
destination 7.7.7.7
label
main_9to7
60
path
mpls te
reoptimization
mpls te
commit
#
LoopBack0
te
destination 8.8.8.8
label
main_9to8
60
path

mpls te
reoptimization
mpls te
commit
#
interface
Tunnel0/0/910
LoopBack0
te
destination
10.10.10.10
mpls te tunnel-id
910
label
main_9to10
60
path
mpls te
reoptimization
mpls te
commit
#

#
#
NOTE
The configuration of the slave MASG (MASG2) is similar to that of the master MASG (MASG1) and are not
mentioned here.

l Run the ping lsp te tunnel command to check the CR-LSP connectivity and the forwarding
status of CR-LSPs.
Then run the following commands to check TE tunnel connectivity on the ingress and
egress.
<CSG1> ping lsp te tunnel 0/0/13 //The ping operation succeeds. The VPN tunnel
is reachable.
<CSG1> ping lsp te tunnel 0/0/13 hot-standby //The ping operation succeeds. The
VPN working tunnel with hot-standby protection is reachable.
l Run the tracert lsp te Tunnel command to check the forwarding paths of LSPs.
l Run the display mpls te tunnel-interface Tunnel x/x/x command to check the tunnel
interface information on the local node.
5.5.2 Configuring BFD for TE LSP

This topic describes how to configure BFD for LSP to speed up TE hot-standby protection
switching.

Configuring the CSG

Configure BFD for TE-LSP for all tunnels on the access ring. The following uses CSG1 as an
example.
bfd LSP13 bind mpls-te interface Tunnel0/0/13 te-lsp //Use the static BFD to detect
the status of the primary LSP of the tunnel 0/0/13.
discriminator local 113 //Specify the local discriminator. The local and remote
discriminators must be the same.
discriminator remote 131 //Specify the remote discriminator.
min-tx-interval 10 //Set the minimum interval for sending BFD packets locally to
10 ms.
min-rx-interval 10 //Set the minimum interval for receiving BFD packets locally to
10 ms.
process-pst //To speed up switchover, the BFD session is allowed to modify the
protection state table (PST).
commit //Commit BFD session configurations.
min-tx-interval 10
min-rx-interval 10
process-pst
commit
Configuring the ASG

Configure BFD for TE-LSP for all tunnels on the access ring and the aggregation ring. The
following uses ASG3 as an example.
min-tx-interval 10
min-rx-interval 10
process-pst
commit
min-tx-interval 10
min-rx-interval 10
process-pst
commit
min-tx-interval 10
min-rx-interval 10
process-pst
commit
NOTE
mentioned here.
(Aggregation layer) Configuring the ASBR

Configure BFD for TE-LSP for all tunnels on the ASBR. The following uses ASBR1 as an
example.

min-tx-interval 10
min-rx-interval 10
process-pst
commit
min-tx-interval 10
min-rx-interval 10
process-pst
commit
NOTE
mentioned here.
(Core layer) Configuring the ASBR

Configure BFD for TE-LSP for all tunnels on the ASBR. The following uses ASBR3 as an
example.
min-tx-interval 10
min-rx-interval 10
process-pst
commit
bfd LSP710 bind mpls-te interface Tunnel0/0/710 te-lsp //Use the static BFD to
detect the status of the primary LSP of the tunnel 0/0/710.
min-tx-interval 10
min-rx-interval 10
process-pst
commit
NOTE
mentioned here.

Configure BFD for TE-LSP for all tunnels on the MASG. The following uses MASG1 as an
example.
the status of the primary LSP of the tunnel 0/0/97
min-tx-interval 10
min-rx-interval 10
process-pst
commit
the status of the primary LSP of the tunnel 0/0/98

min-tx-interval 10
min-rx-interval 10
process-pst
commit
NOTE
The configurations of the slave MASG (MASG2) are similar to those of the master MASG(MASG1) and are
not mentioned here.

Run the display bfd session all for-tecommand to check the BFD status.
If the Tunnels' BFD sessions of the S_TE_LSP type are in the Up state, the BFD sessions have
been established successfully.
[CSG1]display bfd session all for-te
--------------------------------------------------------------------------------
Local Remote PeerIpAddr State Type InterfaceName
--------------------------------------------------------------------------------
113 131 3.3.3.3 Up S_TE_LSP Tunnel0/0/13
114 141 4.4.4.4 Up S_TE_LSP Tunnel0/0/14
--------------------------------------------------------------------------------
Total UP/DOWN Session Number : 2/0
5.5.3 Configuring BFD for TE

This topic describes how to configure BFD for TE.
Configuring the CSG

Configure BFD for TE for all tunnels on the access ring. The following uses CSG1 as an example.
bfd te13 bind mpls-te interface Tunnel0/0/13 //Use the static BFD to detect the
status of the tunnel 0/0/13.
discriminator local 13 //Specify the local discriminator. The local discriminator
must be the same as the remote discriminators configured on the remote device.
discriminator remote 31 //Specify the remote discriminator.
min-tx-interval 50 //Set the minimum interval for sending BFD packets locally to
50 ms.
min-rx-interval 50 //Set the minimum interval for receiving BFD packets locally to
50 ms.
process-pst //To speed up switchover, the BFD session is allowed to modify the
protection state table (PST).
commit //Commit BFD session configurations.
status of the tunnel 0/0/14.
min-tx-interval 50
min-rx-interval 50
process-pst
commit
Configuring the ASG

Configure BFD for TE for all tunnels on the access ring and aggregation ring.
The following uses ASG3 as an example.
status of the tunnel 0/0/31

min-tx-interval 50
min-rx-interval 50
process-pst
commit
min-tx-interval 50
min-rx-interval 50
process-pst
commit
min-tx-interval 50
min-rx-interval 50
process-pst
commit
NOTE
mentioned here.
(Aggregation layer) Configuring the ASBR

The following uses ASBR1 as an example.
min-tx-interval 50
min-rx-interval 50
process-pst
commit
min-tx-interval 50
min-rx-interval 50
process-pst
commit
NOTE
mentioned here.
(Core layer) Configuring the ASBR

The following uses ASBR3 as an example.
min-tx-interval 50
min-rx-interval 50
process-pst
commit


min-tx-interval 50
min-rx-interval 50
process-pst
commit
NOTE
mentioned here.

The following uses MASG1 as an example.
min-tx-interval 50
min-rx-interval 50
process-pst
commit
min-tx-interval 50
min-rx-interval 50
process-pst
commit
NOTE
The configurations of the slave MASG (MASG2) are similar to those of the master MASG (MASG) and are
not mentioned here.

Run the display bfd session all for-te command to check the BFD status.
If the Tunnels' BFD sessions of the S_TE_TNL are in the Up state, the BFD sessions have been
established successfully.
[CSG1]display bfd session all for-te
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
13 31 3.3.3.3 Up S_TE_TNL Tunnel0/0/13
14 41 4.4.4.4 Up S_TE_TNL Tunnel0/0/14
113 131 3.3.3.3 Up S_TE_LSP Tunnel0/0/13
114 141 4.4.4.4 Up S_TE_LSP Tunnel0/0/14
--------------------------------------------------------------------------------

Configuration Guide (CLI) 6 Deploying MPLS Tunnels (BGP LSPs)
6 Deploying MPLS Tunnels (BGP LSPs)
About This Chapter
This section describes how to set up inter-AS BGP LSPs using Labeled BGP.
6.1 Deploying MPLS Tunnels (HVPN+Labeled BGP)

This section describes how to set up inter-AS BGP LSPs between ASGs and MASGs using
Labeled BGP.
6.2 Deploying MPLS Tunnels (Labeled BGP to Edge)

This section describes how to set up inter-AS BGP LSPs between CSGs and MASGs using
Labeled BGP.

6.1 Deploying MPLS Tunnels (HVPN+Labeled BGP)

This section describes how to set up inter-AS BGP LSPs between ASGs and MASGs using
Labeled BGP.
6.1.1 MPLS Tunnel Deployment Solution

This section describes the solution for deploying inter-AS BGP LSPs between ASGs and
MASGs using Labeled BGP.
Figure 6-1 HVPN+Labeled BGP

Labeled iBGP
Labeled eBGP
RR1 changes the next changes the next RR3

hop to itself hop to itself
ASG4 ASBR2 ASBR4 MASG2

changes the next changes the next
hop to itself hop to itself RR4
RR2
TE/LDP Label
push POP push POP push POP
TE/LDP LSP TE/LDP LSP TE/LDP LSP
upstream
BGP Label push swap swap POP
iBGP LSP eBGP LSP iBGP LSP
POP push POP push POP push TE/LDP Label

downstream
POP swap swap push
BGP Label
In the HVPN+Labeled BGP sub-solution, deploy an inter-AS BGP LSP as follows:
1. Deploy Labeled MP-iBGP. Configure neighbor relationship in the BGP-IPv4 unicast

address family view and enable the transmission of labeled routes.
In AS 100
l Set up full-mesh MP-iBGP peer relationship between ASGs/ASBRs and the master and
slave RRs (RR1 and RR2).
In AS 200

Set up full-mesh MP-iBGP peer relationship between ASBRs and the master and slave RRs
(RR3 and RR4).
Set up full-mesh MP-iBGP peer relationship between MASGs and the master and slave
RRs (RR3 and RR4).
l Set up MP-eBGP peer relationship between ASBR1 and ASBR3 (which are directly
connected to each other).
3. MED is used as the parameter to control routes.
l Advertisement of the Loopback0 address from a master ASG to an MASG
Figure 6-2 Design of MED values
RR1 RR3
100
100 50
CSG1 ASG3 ASBR1 50 ASBR3 50 MASG1
10
50
10
50
0
- >2
00
0
10
0
10
0
10
0
10
100
ASG4 ASBR2 ASBR4 100 MASG2
100
RR4
RR2
When the master ASG advertises its loopback address to an RR at the aggregation layer,
the planned MED value is 100. The RR does not modify the MED value. When the
master ASBR at the aggregation layer advertises the address to the master ASBR at the
core layer, it modifies the MED value to 50. When the slave ASBR at the aggregation
layer advertises the value to the slave ASBR at the core layer, it modifies the value to
100. The master ASBR at the core layer does not modify the value (50) when it advertises
the address to the master RR at the core layer, and modifies the value to 200 when it
advertises the address to the slave RR. The slave ASBR at the core layer does not modify
the value (100) when it advertises the address to the master and slave RR at the core
layer. The master RR prefers the route from the master ASBR at the core layer, because
the MED value is 50. Similarly, the slave RR prefers the route from the slave ASBR at
the core layer because the MED value is 100. After the route is sent to the master and
slave MASGs, the master and slave paths are formed between the source MASGs and
destination ASGs. For example:
– The active route (plane) from the master MASG to the master ASG is: master MASG
-> ASBR3 (master ASBR at the core layer) -> ASBR1 (master ASBR at the
aggregation layer) -> ASG3;

– The standby route (plane) from the master MASG to the master ASG is: master
MASG -> ASBR4 (slave ASBR at the core layer) -> ASBR2 (slave ASBR at the
aggregation layer) -> ASG3.
l Advertisement of a loopback address from a slave ASG to an MASG
RR1 RR3
100 50
10
50
0
10
0
0
100
10
50
0
10
0
10
50 50->
10
0 100
RR4
RR2
After the route is sent to the master and slave MASGs, the master and slave paths are
formed between the source MASGs and destination ASGs. For example:
– The active route from the master MASG to the slave ASG is: master MASG ->
ASBR4 (slave ASBR at the core layer) -> ASBR2 (slave ASBR at the aggregation
layer) -> ASG4;
– The standby route from the master MASG to the slave ASG is: master MASG ->
ASBR3 (master ASBR at the core layer) -> ASBR1 (master ASBR at the aggregation
layer) -> ASG4.
l Advertisement of a loopback address from a master MASG to an ASG
RR1 RR3
50 50 100
CSG1 ASG3 ASBR1 502 MASG1ASBR3 100 MASG1
50
0
—5
0
0<
10
10
20
10
10
0
0
10
0
0
10
100<--MASG1 10
10
0
RR4
RR2
After the route is sent to the master and slave ASGs, the master and slave paths are
formed between the source ASGs and destination MASGs. For example:

– The active route from the master ASG to the master MASG is: master ASG ->
ASBR1 (master ASBR at the aggregation layer) ->ASBR3 (master ASBR at the core
layer) -> MASG1;
– The standby route from the master ASG to the master MASG is: master ASG ->
ASBR2 (slave ASBR at the aggregation layer) ->ASBR4 (slave ASBR at the core
layer) -> MASG1.
l Advertisement of a loopback address from a slave MASG to an ASG
RR1 RR3
50 100
CSG1 ASG3 ASBR1 1004MASG2ASBR3 100 MASG1
50
0
10
10
10
10
50
0
10
0
-50
200<
504MASG2 10
0
10
0 10
RR4
RR2
After the route is sent to the master and slave ASGs, the master and slave paths are
formed between the source ASGs and destination MASGs. For example:
– The active route from the master ASG to the slave MASG is: master ASG -> ASBR2
(slave ASBR at the aggregation layer) ->ASBR4 (slave ASBR at the core layer) ->
MASG2;
– The active route from the master ASG to the slave MASG is: master ASG -> ASBR1
(master ASBR at the aggregation layer) ->ASBR3 (master ASBR at the core layer)
-> MASG2.
6.1.2 Data Planning

This section provides the data plan for deploying BGP LSPs.
NOTE
The data provided in this section is used as an example, which may differ in practice due to the difference
Table 6-1 BGP parameters (AS 100)
Parameter ASG3 ASG4 RR1 RR2 ASBR1 ASBR2
BGP 100 100 100 100 100 100

process ID
router-id 3.3.3.3 4.4.4.4 11.11.11. 12.12.12. 5.5.5.5 6.6.6.6

11 12

Parameter ASG3 ASG4 RR1 RR2 ASBR1 ASBR2
iBGP peer RR1: RR1: ASG3: ASG3: RR1: RR1:

11.11.11.1 11.11.11. 3.3.3.3 3.3.3.3 11.11.11.1 11.11.11.1
1 11 ASG4: ASG4: 1 1
RR2: RR2: 4.4.4.4 4.4.4.4 RR2: RR2:
12.12.12.1 12.12.12. ASBR1: ASBR1: 12.12.12.1 12.12.12.1
2 12 5.5.5.5 5.5.5.5 2 2
ASBR2: ASBR2:
6.6.6.6 6.6.6.6
eBGP peer - - - - ASBR3: ASBR4:

10.5.7.2 10.6.8.2
Setting the - - - - ASBR1 ASBR2

next hop to sets the sets the
the local IP next hop to next hop
address itself when to itself
advertisin when
g a route to advertisin
the remote g a route to
ASBR3. the remote
ASBR1 ASBR4.
sets the ASBR2
next hop to sets the
itself when next hop
advertisin to itself
g a route to when
an RR. advertisin
g a route to
an RR.
Transmissio Enabled Enabled Enabled Enabled Enabled Enabled

n of labeled
routes
Parameter ASBR3 ASBR4 RR3 RR4 MASG1 MASG2
BGP process ID 200 200 200 200 200 200
router-id 7.7.7.7 8.8.8.8 13.13.13. 14.14.14. 9.9.9.9 10.10.10.

13 14 10

iBGP peer RR3: RR3: MASG1: MASG1: RR3: RR3:

13.13.13. 13.13.13. 9.9.9.9 9.9.9.9 13.13.13. 13.13.13.
13 13 MASG2: MASG2: 13 13
RR4: RR4: 10.10.10. 10.10.10. RR4: RR4:
14.14.14. 14.14.14. 10 10 14.14.14. 14.14.14.
14 14 ASBR3: ASBR3: 14 14
7.7.7.7 7.7.7.7
ASBR4: ASBR4:
8.8.8.8 8.8.8.8
eBGP peer ASBR1: ASBR2: - - - -

10.5.7.1 10.6.8.1
Connect-retry - - - - - -
interval of peers
Setting the next ASBR3 ASBR4 - - - -

hop to the local IP sets the sets the
address next hop next hop
to itself to itself
when when
advertisi advertisi
ng a route ng a route
to the to the
remote remote
ASBR1. ASBR2.
ASBR3 ASG4
sets the sets the
next hop next hop
to itself to itself
when when
advertisi advertisi
to an RR. to an RR.
Transmission of Enabled Enabled Enabled Enabled Enabled Enabled

labeled routes
6.1.3 Configuring BGP LSPs

This section describes how to configure BGP LSPs.
Configuring the Master ASG

Configure the MP-BGP peer of the master ASG (ASG3).
l Configure a routing policy.

route-policy label1 permit node

10
apply cost 100 //Set MED
value
apply mpls-label //Applies for a label for public network
routes.
#
10
apply cost
100
apply mpls-
label
#
NOTE
l The routing policy with the name of label1 is applied on the egress direction from ASG3 to RR1.
l The policy names are only used as examples and can be named as required in actual projects, for
example, to Label_To_MRR or Label_To_SRR.
l Configure a tunnel selector.
#
tunnel-selector IPRAN permit node
10
apply tunnel-policy IPRAN
l Configure Labeled MP-iBGP.

#
bgp 100
router-id 3.3.3.3
peer 11.11.11.11 as-number 100
peer 11.11.11.11 connect-interface LoopBack0
#
ipv4-family unicast
undo synchronization
network 3.3.3.3 255.255.255.255 //Advertises the loopback0 route
of ASG3 using Labeled BGP, so that MASGs can receive the route.
auto-frr
tunnel-selector IPRAN
ingress-lsp protect-mode bgp-frr //Sets BGP Auto FRR for the BGP Ingress
LSP.
bestroute nexthop-resolved tunnel //Sets the BGP IPv4 unicast labeled route
whose next hop is an MPLS tunnel to participate in the path selection.
peer 11.11.11.11 enable
peer 11.11.11.11 route-policy label1 export //Sets the routes advertised to
RR1 to comply with the routing policy label1.
peer 11.11.11.11 label-route-capability //Enables transmission of labeled
routes.
peer 12.12.12.12 route-policy label2 export //Sets the routes advertised to
RR2 to comply with the routing policy label2.
peer 12.12.12.12 label-route-capability //Enables transmission of labeled
routes.
#
Configuring the Slave ASG

Configure the MP-BGP peer of the slave ASG (ASG4).

#
10
apply cost
100
apply mpls-
label
#
10
apply cost
100
apply mpls-
label
#
NOTE
example, to Label_To_MRR or Label_To_SRR.
#
10

bgp 100
router-id 4.4.4.4
#
ipv4-family unicast
network 4.4.4.4 255.255.255.255
auto-frr
ingress-lsp protect-mode bgp-frr
bestroute nexthop-resolved tunnel
peer 11.11.11.11 route-policy label1 export
peer 11.11.11.11 label-route-capability
#
Configuring the Master RR at the Aggregation Layer

Configure the MP-BGP peer of the master RR (RR1).
l Configure MP-BGP.
bgp 100
router-id 11.11.11.11


peer 5.5.5.5 tracking delay 30
#
ipv4-family unicast
reflector cluster-id 100
peer 3.3.3.3 enable
peer 3.3.3.3 reflect-client
peer 4.4.4.4 enable
peer 5.5.5.5 enable
peer 6.6.6.6 enable
#
Configuring the Slave RR at the Aggregation Layer

Configure the MP-BGP peer of the slave RR (RR2).
l Configure MP-BGP.
bgp 100
router-id 12.12.12.12
#
ipv4-family unicast
peer 3.3.3.3 enable
peer 4.4.4.4 enable
peer 5.5.5.5 enable
peer 6.6.6.6 enable
#
Configuring the Master ASBR at the Aggregation Layer

Configure MP-BGP for the master ASBR (ASBR1).

l Configure an IP prefix filtering table.

#
ip ip-prefix ASG3 index 10 permit 3.3.3.3 32
#

#
10
if-match mpls-
label
apply mpls-
label
#
10
if-match mpls-
label
if-match ip-prefix
ASG3
apply cost
50
apply mpls-
label
#
15
if-match mpls-
label
if-match ip-prefix
ASG4
apply cost
100
apply mpls-
label
#
20
apply cost
50
apply mpls-
label
#
10
if-match cost
50
if-match mpls-
label
apply cost
200
apply mpls-
label
#
20
if-match mpls-
label
apply mpls-
label
#
route-policy prefer permit node
10
apply preferred-value
32768
#

NOTE
NOTE
l The routing policy with the name of label1 is applied on the egress direction from ASBR1 to RR1.
l The routing policy with the name of label2 is applied on the egress direction from ASBR1 to ASBR3.
l The routing policy with the name of prefer is applied on the ingress direction of ASBR1 (from ASBR3
to ASBR1).
#
10
l Configure Labeled MP-BGP.

#
bgp 100
router-id 5.5.5.5
peer 10.5.7.2 as-number 200 //Sets the master ASBR in AS 200 as a Labeled eBGP
peer using its interface address.
#
ipv4-family unicast
undo ebgp-interface-sensitive //Disables fast recovery of eBGP connections,
so that an eBGP directly-connected session is not deleted or set up because the
related interfaces are down or up repeatedly.
network 11.11.11.11 255.255.255.255
network 12.12.12.12 255.255.255.255
auto-frr
peer 10.5.7.2 route-policy prefer import
#
Configuring the Slave ASBR at the Aggregation Layer

Configure MP-BGP for the slave ASBR (ASBR2).
#
#
#

10
if-match mpls-
label
apply mpls-
label
#
10
if-match mpls-
label
if-match ip-prefix
ASG3
apply cost
100
apply mpls-
label
#
15
if-match mpls-
label
if-match ip-prefix
ASG4
apply cost
50
apply mpls-
label
#
20
apply cost
100
apply mpls-
label
#
10
32768
#
10
if-match cost
50
if-match mpls-
label
apply cost
200
apply mpls-
label
#
20
if-match mpls-
label
apply mpls-
label
#
NOTE
to ASBR2).


#
10

bgp 100
router-id 6.6.6.6
#
ipv4-family unicast
undo ebgp-interface-sensitive
network 11.11.11.11 255.255.255.255
network 12.12.12.12 255.255.255.255
auto-frr
Configuring the Master ASBR at the Core Layer

Configure MP-BGP for the master ASBR (ASBR3).
#
ip ip-prefix MASG1 index 10 permit 9.9.9.9 32
#

#
10
if-match mpls-
label
apply mpls-
label
#
10
if-match mpls-
label
if-match ip-prefix
MASG1
apply cost
50
apply mpls-
label

#
15
if-match mpls-
label
if-match ip-prefix
MASG2
apply cost
100
apply mpls-
label
#
20
apply cost
50
apply mpls-
label
#
10
if-match cost
50
if-match mpls-
label
apply cost
200
apply mpls-
label
#
20
if-match mpls-
label
apply mpls-
label
#
10
32768
#
NOTE
to ASBR3).
#
10

#
bgp 200
router-id 7.7.7.7

#
ipv4-family unicast
network 13.13.13.13 255.255.255.255
network 14.14.14.14 255.255.255.255
auto-frr
#
Configuring the Slave ASBR at the Core Layer

Configure the MP-BGP peer of the slave ASBR (ASBR4).
#
#

#
10
if-match mpls-
label
apply mpls-
label
#
10
if-match mpls-
label
if-match ip-prefix
MASG1
apply cost
100
apply mpls-
label
#
15
if-match mpls-
label
if-match ip-prefix
MASG2
apply cost
50
apply mpls-
label
#
20
apply cost

100
apply mpls-
label
#
10
32768
#
10
if-match cost
50
if-match mpls-
label
apply cost
200
apply mpls-
label
#
20
if-match mpls-
label
apply mpls-label
#
NOTE
to ASBR4).
#
10

bgp 200
router-id 8.8.8.8
#
ipv4-family unicast
network 13.13.13.13 255.255.255.255
network 14.14.14.14 255.255.255.255
auto-frr


Configuring the Master RR at the Core Layer


bgp 200
router-id 13.13.13.13
#
ipv4-family unicast
peer 7.7.7.7 enable
peer 8.8.8.8 enable
peer 9.9.9.9 enable
#
Configuring the Slave RR at the Core Layer


bgp 200
router-id 14.14.14.14
#
ipv4-family unicast
peer 7.7.7.7 enable

peer 8.8.8.8 enable

peer 9.9.9.9 enable
#
Configuring the Master MASG

Configure the MP-iBGP peer of the master MASG (MASG1).

#
10
apply mpls-
label
#
NOTE
The routing policy with the name of label1 is applied on the egress direction from MASG1 to RR3 and
RR4.
#
10

#
bgp 200
router-id 9.9.9.9
#
ipv4-family unicast
network 9.9.9.9 255.255.255.255 //Advertises the loopback0 route of MASG1
using Labeled BGP, so that ASGs can receive the route.
auto-frr
#
Configuring the Slave MASG

Configure the MP-BGP peer of the slave MASG (MASG2).


#
10
apply mpls-
label
#
NOTE
The routing policy with the name of label1 is applied on the egress direction from MASG2 to RR3 and
RR4.
#
10
l Configure MP-BGP.
#
bgp 200
router-id 10.10.10.10
#
ipv4-family unicast
network 10.10.10.10 255.255.255.255
auto-frr
#
6.1.4 Configuring BFD for BGP Tunnel

This section describes how to configure BFD for BGP Tunnel to speed up VPN FRR.
Configure BFD for BGP Tunnel on ASGs and MASGs.

The following uses ASG3 as an example to illustrate the configuration.
bfd
mpls-passive //Enables the creation of a BFD session passively.
mpls
mpls bgp bfd enable
mpls bgp bfd-trigger-tunnel host
mpls bgp bfd min-tx-interval 100 min-rx-interval 100
NOTE
Configure the slave ASG (ASG4) similarly as the master ASG (ASG3).

Configuring the Master RR at the aggregation Layer

bfd
mpls-passive
NOTE
Configure the slave RR (RR2) similarly as the master RR (RR1).
Configuring the Master RR at the core Layer

bfd
mpls-passive
NOTE
Configuring MASGs (at the Core Layer)

Configure BFD for BGP Tunnel on MASGs. The following uses MASG1 as an example to
illustrate the configuration.
bfd
mpls
mpls bgp bfd enable
NOTE
Configure the slave MASG (MASG2) similarly as the master MASG (MASG1).
6.1.5 Verifying the Configuration

Verify the configuration.
Run the display bfd session all command to query the BFD session status.
l Run the command on MASG1. Verify that the D_BGP_TUNNEL and E_Dynamic tunnels
between the MASG and the master and slave ASGs are in the Up state.
The D_BGP_TUNNEL type indicates that the local end is the active end and the
E_Dynamic type indicates that the local end is the passive end.
<MASG1>display bfd session all
------------------------------------------------------------------------------
--
------------------------------------------------------------------------------
--
8192 8192 10.9.13.2 Up D_IP_IF GigabitEthernet2/0/2
8193 8192 10.9.10.2 Up D_IP_IF Eth-Trunk1.1
901 1090 10.10.10.10 Up S_TE_LSP Tunnel0/0/910
910 109 10.10.10.10 Up S_TE_TNL Tunnel0/0/910
907 709 7.7.7.7 Up S_TE_LSP Tunnel0/0/97
97 79 7.7.7.7 Up S_TE_TNL Tunnel0/0/97
908 809 8.8.8.8 Up S_TE_LSP Tunnel0/0/98
98 89 8.8.8.8 Up S_TE_TNL Tunnel0/0/98
8194 0 11.11.11.11 Up D_BGP_TUNNEL -
8195 8203 3.3.3.3 Up D_BGP_TUNNEL -
8198 0 12.12.12.12 Up D_BGP_TUNNEL -
8199 8204 4.4.4.4 Up D_BGP_TUNNEL -
8200 8202 4.4.4.4 Up E_Dynamic -
8201 8197 3.3.3.3 Up E_Dynamic -

------------------------------------------------------------------------------
--
l Run the command on ASG3. Verify that the D_BGP_TUNNEL and E_Dynamic tunnels
between the ASG and the master and slave MASGs are in the Up state.
<ASG3>display bfd session all
------------------------------------------------------------------------------
--
------------------------------------------------------------------------------
--
8192 8193 10.3.4.2 Up D_IP_IF
GigabitEthernet1/0/0.1
36 63 6.6.6.6 Up S_TE_TNL Tunnel0/0/36
35 53 5.5.5.5 Up S_TE_TNL Tunnel0/0/35
305 503 5.5.5.5 Up S_TE_LSP Tunnel0/0/35
8197 8201 9.9.9.9 Up D_BGP_TUNNEL -
8198 0 13.13.13.13 Up D_BGP_TUNNEL -
8199 0 14.14.14.14 Up D_BGP_TUNNEL -
8200 8202 10.10.10.10 Up D_BGP_TUNNEL -
31 13 1.1.1.1 Up S_TE_TNL Tunnel0/0/31
301 103 1.1.1.1 Up S_TE_LSP Tunnel0/0/31
8202 8198 10.10.10.10 Up E_Dynamic -
8203 8195 9.9.9.9 Up E_Dynamic -
------------------------------------------------------------------------------
--
Run the display mpls lsp protocol bgp command to query the status of a BGP LSP.
l Run the command on MASG1.
<MASG1>display mpls lsp protocol bgp
------------------------------------------------------------------------------
-
LSP Information: BGP LSP
------------------------------------------------------------------------------
-
FEC In/Out Label In/Out IF Vrf Name
9.9.9.9/32 155672/NULL -/-
11.11.11.11/32 NULL/155681 -/-
**BGP FRR** /155683 /-
3.3.3.3/32 NULL/155682 -/-
**BGP FRR** /155684 /-
4.4.4.4/32 NULL/155689 -/-
**BGP FRR** /155682 /-
12.12.12.12/32 NULL/155688 -/-
**BGP FRR** /155680 /-
l Run the command on ASG3.

<ASG3>display mpls lsp protocol bgp

------------------------------------------------------------------------------
-
LSP Information: BGP LSP
------------------------------------------------------------------------------
-
FEC In/Out Label In/Out IF Vrf Name
3.3.3.3/32 155677/NULL -/-
14.14.14.14/32 NULL/155722 -/-
**BGP FRR** /155668 /-
10.10.10.10/32 NULL/155723 -/-
**BGP FRR** /155667 /-
9.9.9.9/32 NULL/155720 -/-
**BGP FRR** /155677 /-
13.13.13.13/32 NULL/155721 -/-
**BGP FRR** /155678 /-
Run the display ip routing-table ip-address command to query the routing table of the remote
end.
l Run the command on MASG1.

<MASG1>display ip routing-table 3.3.3.3 v
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Routing Table : Public

Summary Count : 1
Destination: 3.3.3.3/32
Protocol: IBGP Process ID: 0
Preference: 255 Cost: 50
NextHop: 7.7.7.7 Neighbour: 13.13.13.13
State: Active Adv Relied Age: 00h54m53s
Tag: 0 Priority: low
Label: 155682 QoSInfo: 0x0
IndirectID: 0x2
RelayNextHop: 0.0.0.0 Interface:
Tunnel0/0/97
TunnelID: 0x60033c01 Flags: RD
BkNextHop: 8.8.8.8 BkInterface:
Tunnel0/0/98
BkLabel: 155684 SecTunnelID: 0x0
BkPETunnelID: 0x60033c02 BkPESecTunnelID: 0x0
BkIndirectID: 0x6
l Run the command on ASG3.

<ASG3>display ip routing-table 9.9.9.9 v
------------------------------------------------------------------------------
Routing Table : Public

Summary Count : 1
IndirectID: 0x4
RelayNextHop: 0.0.0.0 Interface:
Tunnel0/0/35
TunnelID: 0x60033c02 Flags: RD

BkNextHop: 6.6.6.6 BkInterface:

Tunnel0/0/36
BkPETunnelID: 0x60033c03 BkPESecTunnelID: 0x0
BkIndirectID: 0x8
6.2 Deploying MPLS Tunnels (Labeled BGP to Edge)

This section describes how to set up inter-AS BGP LSPs between CSGs and MASGs using
Labeled BGP.
6.2.1 Tunnel Deployment Solution

This section describes the solution for deploying inter-AS BGP LSPs between CSGs and MASGs
using Labeled BGP.
Figure 6-6 Labeled BGP to Edge

Labeled iBGP
Labeled eBGP
changes the next RR1 changes the next changes the next RR3
hop to itself hop to itself hop to itself

changes the next changes the next changes the next
hop to itself hop to itself hop to itself RR4
RR2
TE/LDP Label
Upstream
BGP Label
push swap swap swap POP
iBGP LSP iBGP LSP eBGP LSP iBGP LSP
Downstream
swap
swap swap push
POP iBGP LSP iBGP LSP
eBGP LSP
BGP Label
In the Labeled BGP to Edge sub-solution, deploy an inter-AS BGP LSP as follows:
In AS 100

l Set up MP-iBGP peer relationship between CSGs and the master and slave ASGs.
l Set up full-mesh MP-iBGP peer relationship between ASGs/ASBRs and the master and
slave RRs (RR1 and RR2).
In AS 200
Set up full-mesh MP-iBGP peer relationship between ASBRs and the master and slave RRs
(RR3 and RR4).
RRs (RR3 and RR4).
l Advertisement of the Loopback0 address from a CSG to an MASG
RR1 RR3
50
50 50
50
50
50
50
- >2
50
00
- >2
100
00
0
10
0
10
0
10
100
10 0
0 10
100
100
RR4
RR2
A CSG advertises its Loopback0 route to the master and slave ASGs. The MED is set
to 50 and 100 for routes on the active and standby links respectively. The master ASG
reflects the loopback route to the master RR at the aggregation layer after changing the
next hop to itself, without modifying the MED value. The master ASG reflects the route
to the slave RR after modifying the MED value to 200 and changing the next hop to
itself. The slave ASG reflects the loopback route to the master and slave RRs after
changing the next hop to itself, without modifying the MED value. The master and slave
RRs at the aggregation layer reflect the route to the master and slave A-ASBRs without
modifying the MED value. The master ASBR at the aggregation layer advertises the
loopback route to the master ASBR at the core layer after modifying the MED value to
50 and changing the next hop to itself. The slave ASBR at the aggregation layer
advertises the loopback route to the slave ASBR at the core layer after modifying the
MED value to 100 and changing the next hop to itself. The master ASBR at the core
layer advertises the route to the master RR at the core layer without modifying the MED
value (50), and advertises the route to the slave RR after modifying the MED value to

200, after changing the next hop to itself. The slave ASBR at the core layer advertises
the route to the master and slave RRs after changing the next hop to itself, without
modifying the MED value (100). The master RR at the core layer prefers the route from
the master ASBR at thecore layer because its MED value is 50. The slave RR at the
core layer prefers the route from the slave ASBR at the core layer because its MED
value is 100. After the routes are sent to the MASGs, the master and slave paths are
formed. For example:
– The active path from the master MASG to a CSG is: master MASG -> ASBR3
（master ASBR at the core layer) -> ASBR1（master ASBR at the aggregation layer)
-> ASG3 -> CSG;
– The standby path from the master MASG to a CSG is: master MASG -> ASBR4
（slave ASBR at the core layer) -> ASBR2（slave ASBR at the aggregation layer)
-> ASG3 -> CSG.
l Figure 4-19 Advertisement of a loopback route from a master MASG to CSGs
RR1 RR3
50 50 100
50
50
100
0
—5
100
0<
20
10
0
10
10
0
0
10
0
10
100 10
10
0
RR4
RR2
After the routes are sent to the CSGs, the master and slave paths are formed.
– The active path from a CSG to the master MASG: CSG -> ASG3 -> ASBR1（master
ASBR at the aggregation layer) -> ASBR3（master ASBR at the core layer) ->
master MASG;
– The standby path from a CSG to the master MASG: CSG -> ASG4 -> ASBR1
（master ASBR at the aggregation layer) -> ASBR3（master ASBR at the core layer)
-> master MASG.
l Advertisement of a loopback route from a slave MASG to CSGs

RR1 RR3
50 100
100
50
100
0
10
50
10
50
10
0
0
0
10
0
20
50 10
10
0 100
RR4
RR2
After the routes are sent to the CSGs, the master and slave paths are formed.
– The active path from a CSG to the slave MASG: CSG -> ASG4 -> ASBR2（slave
ASBR at the aggregation layer) -> ASBR4（slave ASBR at the core layer) -> slave
MASG;
– The active path from a CSG to the slave MASG: CSG -> ASG3 -> ASBR2（slave
ASBR at the aggregation layer) -> ASBR4（slave ASBR at the core layer) -> slave
MASG.
6.2.2 Data Planning

This section provides the data plan for deploying BGP LSPs.
NOTE
Paramete CSG1 ASG3 ASG4 RR1 RR2 ASBR1 ASBR2

r
BGP 100 100 100 100 100 100 100

process ID
router-id 1.1.1.1 3.3.3.3 4.4.4.4 11.11.11 12.12.12 5.5.5.5 6.6.6.6

.11 .12

Paramete CSG1 ASG3 ASG4 RR1 RR2 ASBR1 ASBR2

r
iBGP peer ASG3: RR1: RR1: ASG3: ASG3: RR1: RR1:

3.3.3.3 11.11.11 11.11.11 3.3.3.3 3.3.3.3 11.11.11 11.11.11
ASG4: .11 .11 ASG4: ASG4: .11 .11
4.4.4.4 RR2: RR2: 4.4.4.4 4.4.4.4 RR2: RR2:
12.12.12 12.12.12 ASBR1: ASBR1: 12.12.12 12.12.12
.12 .12 5.5.5.5 5.5.5.5 .12 .12
ASBR2: ASBR2:
6.6.6.6 6.6.6.6
eBGP peer - - - - - ASBR3: ASBR4:

10.5.7.2 10.6.8.2
Setting the - ASG3 ASG4 - - ASBR1 ASBR2

next hop to sets the sets the sets the sets the
the local next hop next hop next hop next hop
IP address to itself to itself to itself to itself
when when when when
advertisi advertisi advertisi advertisi
ng a ng a ng a ng a
route to route to route to route to
an RR or an RR or the the
CSG. CSG. remote remote
ASBR3. ASBR4.
ASBR1 ASBR2
sets the sets the
next hop next hop
to itself to itself
when when
advertisi advertisi
ng a ng a
route to route to
an RR. an RR.
Transmiss Enabled Enabled Enabled Enabled Enabled Enabled Enabled

ion of
labeled
routes
BGP process ID 200 200 200 200 200 200
router-id 7.7.7.7 8.8.8.8 13.13.13. 14.14.14. 9.9.9.9 10.10.10.

13 14 10

iBGP peer RR3: RR3: MASG1: MASG1: RR3: RR3:

13.13.13. 13.13.13. 9.9.9.9 9.9.9.9 13.13.13. 13.13.13.
13 13 MASG2: MASG2: 13 13
RR4: RR4: 10.10.10. 10.10.10. RR4: RR4:
14.14.14. 14.14.14. 10 10 14.14.14. 14.14.14.
14 14 ASBR3: ASBR3: 14 14
7.7.7.7 7.7.7.7
ASBR4: ASBR4:
8.8.8.8 8.8.8.8
eBGP peer ASBR1: ASBR2: - - - -

10.5.7.1 10.6.8.1
Connect-retry - - - - - -
interval of peers
Setting the next ASBR3 ASBR4 - - - -

hop to the local IP sets the sets the
address next hop next hop
to itself to itself
when when
advertisi advertisi
to the to the
remote remote
ASBR1. ASBR2.
ASBR3 ASBR4
sets the sets the
next hop next hop
to itself to itself
when when
advertisi advertisi
to an RR. to an RR.
Transmission of Enabled Enabled Enabled Enabled Enabled Enabled

labeled routes
6.2.3 Configuring BGP LSPs

This section describes how to configure BGP LSPs.
Configuring CSGs
Configure the MP-BGP peer of CSG1.
#
route-policy label1 permit node 10

apply mpls-label
#
apply mpls-label
NOTE
l The routing policy with the name of label1 is applied on the egress direction from CSG1 to ASG3.
l The routing policy with the name of label2 is applied on the egress direction from CSG1 to ASG4.
example, Label_To_ASG3和Label_To_ASG4.
#
10
#
l Configure MP-BGP.
#
bgp 100
router-id 1.1.1.1
#
ipv4-family unicast
network 1.1.1.1 255.255.255.255 //Advertises the Loopback0 address, so that
it reaches MASGs through BGP LSPs.
auto-frr
peer 3.3.3.3 enable
peer 4.4.4.4 enable
#

l Configure the IP prefix list and the community attribute filter.

#
ip community-filter basic csg permit 1:1 //Defines the community attribute
table for identifying CSG-side public network IPv4 routes.
#

#
route-policy label1 permit node 5 //The routing policy is applied on the

egress direction from ASG3 to RR1.
if-match mpls-label //Allows the transmission of labeled routes.
if-match community-filter csg //Filters routes according to the community
attributes of CSG-side public network IPv4 routes. Qualified routes are
permitted to pass.

apply ip-address next-hop peer-address // Changes the next hop of a route to

the ASG itself.
routes.
#
if-match cost
50
if-match mpls-
label
if-match community-filter
csg
apply ip-address next-hop peer-address //Changes the next hop of a route to
the ASG itself.
apply cost
200
apply mpls-
label
#
route-policy ipv4-from-csg permit node 10
apply cost 50
apply community 1:1 additive
apply preferred-value 32768
#
route-policy ipv4-to-csg permit node 10
if-match mpls-label
if-match ip-prefix MASG1
apply cost 50
apply mpls-label
#
if-match mpls-label
apply cost 100
apply mpls-label
#

#
10
#
l Configure MP-BGP.
#bgp 100
router-id 3.3.3.3
group CSG internal
peer CSG connect-interface LoopBack0
peer 1.1.1.1 group CSG
#
ipv4-family unicast
reflect change-path-attribute
auto-frr
tunnel-selector IPRAN //Configures outer tunnels for carrying BGP LSPs.


peer 11.11.11.11 advertise-community
peer CSG enable
peer CSG route-policy ipv4-from-csg import
peer CSG route-policy ipv4-to-csg export
peer CSG reflect-client
peer CSG next-hop-local
peer CSG label-route-capability
peer 1.1.1.1 enable
#

l Configure the IP prefix list and the community attribute filter.

#
ip community-filter basic csg permit 1:1
#

#

if-match mpls-label //Allows the transmission of labeled
routes.
if-match community-filter csg //Filters routes according to the community
attributes of CSG-side public network IPv4 routes. Qualified routes are
permitted to pass.
apply ip-address next-hop peer-address // Changes the next hop of a route to
the ASG itself.
routes.
#
if-match cost
100
if-match mpls-
label
csg
the ASG itself.
apply mpls-
label
#

apply cost 100
#
if-match mpls-label


apply cost 100
apply mpls-label
#
if-match mpls-label
apply cost 50
apply mpls-label
#

#
10
#
l Configure MP-BGP.
bgp 100
router-id 4.4.4.4
group CSG internal
#
ipv4-family unicast
reflector cluster-id 102 //The cluster ID must be different from that of the
master ASG. Otherwise, routes from the slave ASG are discarded by a CSG and a
standby route cannot be generated.
auto-frr
peer CSG enable
peer 1.1.1.1 enable
#

See the related configuration in the HVPN+Labeled BGP sub-solution.










6.2.4 Configuring BFD for BGP Tunnel

This section describes how to configure BFD for BGP Tunnel to speed up VPN FRR.
Configure BFD for BGP Tunnel on CSGs and MASGs.
Configuring CSGs
The following uses CSG1 as an example to illustrate the configuration.
bfd
mpls
mpls bgp bfd enable

NOTICE
l Enable dynamic BFD session setup in passive mode for CSGs and remote PEs (MASGs).
Configuring the Master RR at the aggregation Layer

bfd
mpls-passive
NOTE
Configuring the Master RR at the core Layer

bfd
mpls-passive
NOTE
Configuring MASGs (at the Core Layer)

Configure BFD for BGP Tunnel on MASGs. The following uses MASG1 as an example to
illustrate the configuration.
bfd
mpls-passive
mpls
mpls bgp bfd enable
NOTE
Configure the slave MASG (MASG2) similarly as the master MASG (MASG1).
6.2.5 Verifying the Configuration

Verify the configuration.
Run the display bfd session all command to query the BFD session status.
l Run the command on MASG1. Verify that the D_BGP_TUNNEL and E_Dynamic tunnels
between the MASG and the master and slave CSGs are in the Up state.
<MASG1>display bfd session all
------------------------------------------------------------------------------
--
------------------------------------------------------------------------------
--
8193 8192 10.9.10.2 Up D_IP_IF Eth-Trunk1.1
901 1090 10.10.10.10 Up S_TE_LSP Tunnel0/0/910
910 109 10.10.10.10 Up S_TE_TNL Tunnel0/0/910
907 709 7.7.7.7 Up S_TE_LSP Tunnel0/0/97
97 79 7.7.7.7 Up S_TE_TNL Tunnel0/0/97

908 809 8.8.8.8 Up S_TE_LSP Tunnel0/0/98

98 89 8.8.8.8 Up S_TE_TNL Tunnel0/0/98
8225 0 11.11.11.11 Up D_BGP_TUNNEL -
8226 0 12.12.12.12 Up D_BGP_TUNNEL
-
9212 1151 1.1.1.1 Up D_BGP_TUNNEL
-
9221 1153 1.1.1.1 Up E_Dynamic -
------------------------------------------------------------------------------
--
l Run the command on CSG1. Verify that the D_BGP_TUNNEL and E_Dynamic tunnels
between the CSG and the master and slave MASGs are in the Up state.
<CSG1>display bfd session all
------------------------------------------------------------------------------
--
------------------------------------------------------------------------------
--
1024 514 10.1.2.1 Up D_IP_IF
GigabitEthernet0/2/2
1025 8215 10.2.4.2 Up D_IP_IF
204 402 4.4.4.4 Up S_TE_LSP Tunnel0/0/24
24 42 4.4.4.4 Up S_TE_TNL Tunnel0/0/24
23 32 3.3.3.3 Up S_TE_TNL Tunnel0/0/23
203 302 3.3.3.3 Up S_TE_LSP Tunnel0/0/23
1150 9221 10.10.10.10 Up E_Dynamic -
1151 9212 9.9.9.9 Up E_Dynamic -
1152 9233 10.10.10.10 Up D_BGP_TUNNEL -
1153 9221 9.9.9.9 Up D_BGP_TUNNEL -
------------------------------------------------------------------------------
--

Configuration Guide (CLI) 7 Deploying DCN
7 Deploying DCN
About This Chapter
This section describes how to deploy DCN routes on a bearer network so that the NMS can
access the managed NEs through DCN routes.
DCN routes can be deployed in different modes according to the used BGP.
l If the MP-BGP and RRs are configured, and MED values are used to distinguish route
priorities, the available DCN deployment solutions are as follows:
Public DCN solution 7.1.1 Deploying Public DCN Using IS-IS

(U2000 Connected to the IPCore
Network)
DCN VRF solution 7.2.2 Deploying DCN VRF for a Large

Network (U2000 Connected to the
IPCore Network)
7.1 Deployment of a Public DCN

The NMS manages NEs on a bearer network using reachable public network IGP routes.
7.2 Deploying a DCN VRF Solution

This topic describes how to deploy DCN VRF on equipment so that the U2000 can load and
manage the equipment.

7.1 Deployment of a Public DCN

The NMS manages NEs on a bearer network using reachable public network IGP routes.
7.1.1 Deploying Public DCN Using IS-IS (U2000 Connected to the

IPCore Network)
If IS-IS is used as the IGP of a network, DCN must be deployed using IS-IS. This section
describes how to manage NEs on an IS-IS public network using the U2000.
Configuration Roadmap
1. A management VPN is created on the backbone network. A management loopback address
is created for each backbone device and bound to the management VPN.
2. New loopback addresses (different from the LSR IDs) are planned for devices in the
IPRAN. The addresses are used as the public network management addresses of the devices.
The loopback routes are added with tags and imported into the IGP.
3. Access-side management routes are imported to the aggregation side. A-ASBRs advertise
the public network IGP of the IPRAN (or aggregation routes between management
addresses of the IPRAN) to the management VPN of the backbone network. In addition,
the A-ASBRs advertise routes of the U2000 to the IGP of the IPRAN.
The following figure shows the typical public DCN deployment: the U2000 is dual-homed to
two MASGs, and an L2 network is deployed between the MASGs and the U2000. An L3 network
may be traversed in the actual application. You need to set static routes from the MASGs to the
U2000. The gateway is located at the ingress interface of a third-party.
Figure 7-1 Deployment of a public DCN
AS 100 AS 200

GE0/2/16 GE2/1/0 GE1/0/1 VRF GE1/0/1 VRF
GE1/1/2 GE1/0/0 GE1/0/0 GE1/0/0
GE1/0/0 GE2/0/1 GE2/0/1
GE0/2/17
Eth-Trunk 1
LSW
U2000 Server
GE0/2/17 GE2/0/1 GE2/0/1 130.10.100.0/24

GE1/0/0
GE1/1/2 GE1/0/0 GE1/0/0 GE1/0/0
VRF VRF
GE2/1/0 GE1/0/1 GE1/0/1
GE0/2/16
Imports management routes of Advertises the IGP/aggregation

access layer into IGP process of routes of the IPRAN to the
the aggregation layer. NMS VPN of the IPCore.
Advertises routes of the

NMS server to the IGP of
the IPRAN

Data Plan
Table 7-1 Data plan for public DCN
Device Parameter Value
MASG NMS VPN instance __dcn_ideal__
Interfaces connecting to No.: Interfaces GE7/1/11 on MASG1 and

the U2000 MASG2
IP addresses: 130.10.100.1/24 for MASG1,
and 130.10.100.2/24 for MASG2
VRRP vrid: 22
virtual-ip: 130.10.100.10
Management interface and l MASG1:LoopBack65535,

IP address 200.0.100.9/32
l MASG2:LoopBack65535,
200.0.100.10/32
ASBRs and NMS VPN instance __dcn_ideal__

RRs at the core
layer Management interface and l RR3:LoopBack65535, 200.0.100.13/32
IP address l RR4:LoopBack65535, 200.0.100.14/32
l ASBR3:LoopBack65535,
200.0.100.7/32
l ASBR4:LoopBack65535,
200.0.100.8/32
ASBRs, RRs Management interface and l ASBR1:LoopBack65535,

and ASGs at the IP address 200.0.100.5/32
aggregation l ASBR2:LoopBack65535,
layer. CSGs at 200.0.100.6/32
the access l RR1:LoopBack65535, 200.0.100.11/32
layer.
l RR2:LoopBack65535, 200.0.100.12/32
l ASG3:LoopBack65535, 200.0.100.3/32
l ASG4:LoopBack65535, 200.0.100.4/32
l CSG1:LoopBack1000, 200.0.100.1/32
NOTE
New loopback addresses (different from the LSR
IDs) are planned for devices in the IPRAN.
U2000 Management IP address 130.10.100.20/24

NOTICE
The management IP addresses are different from the LSR IDs.
Table 7-2 SNMP parameters
snmp-agent sys-info all Enables this function in

version SNMPv1, SNMPv2C, and
SNMPv3.
snmp-agent mib-view iso The SNMP MIB view

included iso-view contains the iso subtree.
snmp-agent community cipher Huawei123! Sets read and write

read cipher mib-view iso-view community names. The NMS
can access a device only
when the community names
set on the NMS are the same
as that set on the device.
snmp-agent community cipher Huawei@123 Sets read and write

write cipher mib-view iso-view community names. The NMS
snmp-agent trap enable – Enables all traps on a device.
snmp-agent trap source Core layer equipment: Sets the LoopBack interfaces
LoopBack 65535 as the source interfaces for
sending Trap messages.
snmp-agent target-host address udp-domain Allows the SNMP agent to

trap 130.10.100.20 send SNMP trap messages to
params securityname the Huawei NMS at
Huawei@123 v2c private- 130.10.100.20.
netmanager ext-vb
snmp-agent trap enable – Enables the LLDP trap

feature-name lldp function.
snmp-agent extend error- – Opens the extended error

code enable codes of devices.
Configuring MASGs
1. Create management interfaces.

interface LoopBack65535
2. Configure SNMP.
lldp enable
#
snmp-agent
snmp-agent sys-info version all //Enables SNMP of all versions on the system.
snmp-agent mib-view included iso-view iso //The SNMP MIB view contains the iso
subtree.
snmp-agent community read cipher Huawei123! mib-view iso-view
snmp-agent community write cipher Huawei@123 mib-view iso-view //The write
attribute contains the read and right permission.
If the read
attribute community name and the write attribute community name are the same,
the read attribute
command will be overwritten by the write attribute command.
snmp-agent trap enable //Enables the SNMP agent to send trap messages.
snmp-agent trap source LoopBack65535 //Sets the source interface of Trap
messages.
snmp-agent target-host trap address udp-domain 130.10.100.20 vpn-instance
__dcn_ideal__ params securityname Huawei@123 v2c private-netmanager ext-vb
//Allows the transmission of SNMP Trap messages to
the NMS server (130.10.100.20). The community name of Huawei@123 is used. If
the NMS is a Huawei NMS, it is recommended to set the private-netmanager and
ext-vb parameters.
snmp-agent trap enable feature-name lldp
snmp-agent extend error-code enable//Enables the extend error-code function
for equipment.
3. Configure IGP on the network.

For details, see the section about IGP configuration.
4. Configure the management VPN.
l Configure the management DCN VRF.
#
ip vpn-instance __dcn_ideal__
ipv4-
family
route-distinguisher
65535:65535
vpn-target 65535:65535 export-
extcommunity
vpn-target 65535:65535 import-
extcommunity
#
l Bind a management interface to the management VRF instance.

#
interface
LoopBack65535
ip binding vpn-instance
__dcn_ideal__
ip address 200.0.100.9 255.255.255.255
#
l Bind the interfaces connected to the U2000 to the management VRF instance.
#
interface
undo
shutdown
__dcn_ideal__
ip address 130.10.100.1 255.255.255.0 //Sets the IP address, which must be
in the same network segment as the U2000 IP address.

5. (When the NE is connected to the U2000 through an L2 network) Configure a route policy
and route importing.
#
ip ip-prefix U2000 index 10 permit 130.10.100.0 24
ip ip-prefix DCN index 10 permit 200.0.100.9 32
#
route-policy U2000-DCN permit node
10
if-match ip-prefix U2000
apply community
2000:2000
#
20
if-match ip-prefix
DCN
#
l Configure route importing.

#
bgp 200
#
ipv4-family vpn-instance
__dcn_ideal__
import-route direct route-policy U2000-DCN
#
6. (When the NE is connected to the U2000 through an L3 network) Configure a route policy
and route importing.
#
#
route-policy U2000 permit node
10
if-match ip-prefix
U2000
apply community 2000:2000
#
route-policy DCN permit node
10
if-match ip-prefix
DCN
#

#
bgp 200
#
__dcn_ideal__
import-route direct route-policy DCN
import-route static route-policy U2000
#
l Configure a static route.

ip route-static vpn-instance __dcn_ideal__ 130.10.100.0 255.255.255.0
123.1.2.2 description dcn-ideal

NOTE
123.1.2.2 is the IP address of the ingress interface of the L3 network between the core layer and the
U2000.
7. Configure VRRP.
Configure VRRP for MASG1 (master) and MASG2 (slave), to ensure that NEs do not
become unreachable if MASG1 is faulty. After the configuration, run the display ip
routing-tablecommand to query routes to the U2000, aggregation ring routes, and access
ring routes.
Configure MASG1 as follows:
vrrp vrid 22 virtual-ip 130.10.100.10
vrrp vrid 22 priority 120
vrrp vrid 22 preempt-mode timer delay 300

NOTE
If DCN has been enabled globally, check whether DCN has been enabled for the master interface connected
to the U2000. If yes, disable the DCN function. The configurations are as follows:
undo dcn
8. For details about adding NEs on the U2000, see the Singe-OSS IPRAN ATN+CX (HVPN
& FMC) Network Design.
Configuring RRs at the Core Layer

2. Configure SNMP.
lldp enable
#
snmp-agent
snmp-agent sys-info version all//Enables SNMP of all versions on the system.
snmp-agent mib-view included iso-view iso//The SNMP MIB view contains the iso
subtree.
snmp-agent community write cipher Huawei@123 mib-view iso-view//The write
attribute contains the read and right permission. If the read attribute
community name and the write attribute community name are the same, the read
attribute command will be overwritten by the write attribute command.
snmp-agent trap enable//Enables the SNMP agent to send trap messages.
snmp-agent trap source LoopBack65535//Sets the source interface of Trap
messages.
ext-vb parameters.
for equipment.



#
ipv4-
family
route-distinguisher
65535:65535
extcommunity
extcommunity
#
l Configure a routing policy and route importing.

– Configure a routing policy.
#
ip community-filter basic U2000 permit 2000:2000
#
10
if-match community-filter U2000
#
route-policy DCN permit node
10
if-match ip-prefix DCN
#
– Configure route importing.

#
bgp 200
#
__dcn_ideal__
#

#
interface
LoopBack65535
__dcn_ideal__
ip address 200.0.100.13 255.255.255.255
#
l Configure BGP.
#
bgp
200
#
ipv4-family
vpnv4
reflector cluster-id
200
peer 7.7.7.7
enable
peer 7.7.7.7 route-policy U2000
export
peer 7.7.7.7 reflect-
client
peer 7.7.7.7 advertise-
community
peer 8.8.8.8

enable
export
peer 8.8.8.8 reflect-
client
#

2. Configure SNMP.
lldp enable
#
snmp-agent
subtree.
messages.
ext-vb parameters.
for equipment.

#
ipv4-
family
route-distinguisher
65535:65535
extcommunity
extcommunity
#

#
interface
LoopBack65535
__dcn_ideal__
ip address 200.0.100.7 255.255.255.255
#
l Bind sub-interfaces connected to AS 100 (of the IPRAN) to the management VRF
instance.

#
interface
vlan-type dot1q
1
__dcn_ideal__
ip address 23.5.7.2 255.255.255.252 #
l Configure BGP.
#
bgp
200
#
ipv4-family
vpnv4
undo policy vpn-
target
peer 13.13.13.13
enable
peer 14.14.14.14
enable
#
5. Configure a routing policy and route importing.

#
#
10
U2000
#
route-policy DCN permit node 10
#

#
bgp 200
#
__dcn_ideal__
peer 23.5.7.1 as-number
100
export
#

1. Configure management interface.
#
ip address 200.0.100.5
255.255.255.255
isis enable

100
2. Configure SNMP.
lldp enable
#
snmp-agent
subtree.
messages.
snmp-agent target-host trap address udp-domain 130.10.100.20 params
securityname Huawei@123 v2c private-netmanager ext-vb
ext-vb parameters.
for equipment.

4. Configure interfaces.
l Configure sub-interfaces interconnected to the core layer as follows:
#
interface
vlan-type dot1q
1
ip address 23.5.7.1
255.255.255.252
#
5. Configure BGP.
#
bgp
100
router-id
5.5.5.5

#
route-policy pref-nms permit node
10
U2000
apply preference
10
#
route-policy ipran-local permit node

10
if-match ip-prefix ipran
#
route-policy ipran-out permit node
10
#
10
U2000
apply tag 2000

#
ip ip-prefix ipran index 10 permit 200.0.100.0 24 greater-equal 24 less-
equal 32
#

#
bgp 100
#
ipv4-family
unicast
preference route-policy pref-nms //Improves the priority
of NMS routes.
import-route isis 100 route-policy ipran-local //Imports management
routes from the IPRAN.
peer 23.5.7.2 route-policy ipran-out export //Exports management
routes to the core layer.
#
l Import the U2000 routes to the IGP.

#
isis
100
import-route bgp route-policy U2000
#

#
interface
LoopBack65535
ip address 200.0.100.11
255.255.255.255
isis enable
100
2. Configure SNMP.
lldp enable
#
snmp-agent
subtree.


messages.
ext-vb parameters.
for equipment.

Configuring ASGs
#
interface
LoopBack65535
255.255.255.255
isis enable
100
2. Configure SNMP.
lldp enable
#
snmp-agent
subtree.
messages.
ext-vb parameters.
for equipment.



#
10
if-match tag
2000
apply tag
2
#
10
if-match tag
2
apply preference 255
#
route-policy acc deny node
10
if-match ip-prefix
LoopBack0
#
route-policy acc permit node
20
if-match ip-prefix acc
apply tag 2
#
ip ip-prefix LoopBack0 index 10 permit 3.3.3.3 32
ip ip-prefix acc index 10 permit 200.0.100.0 24 greater-equal 24 less-equal
32
#

#
isis
1
import-route isis 100 inherit-cost route-policy
U2000
preference route-policy pref-nms
#
isis 100
import-route isis 1 inherit-cost route-policy acc
#
Configuring CSGs
#
interface
LoopBack1000
255.255.255.255
isis enable
1
2. Configure SNMP.
lldp enable
#
snmp-agent


subtree.
messages.
ext-vb parameters.
for equipment.

Configuring Static Routes on the U2000 Server

Configure static routes on the U2000 server. Specify the virtual IP addresses of MASGs as the
gateway, so that the gateway NEs are reachable to the U2000 server through public network
routes.
On Windows, run the following command in the CMD:

route add 0.0.0.0 mask 255.255.0.0 130.10.100.10 -p
Verifying the Configuration

l Run the display ip routing-table vpn-instance vpn-instance-name command.
<MASG1>display ip routing-table vpn-instance __dcn_ideal__
Route Flags: R - relay D - download to fib
------------------------------------------------------------------------------
Routing Tables: __dcn_ideal__
Destinations : 19 Routes : 19
Destination/Mask Proto Pre Cost Flags NextHop Interface

200.0.100.1/32 IBGP 255 103 RD 7.7.7.7
200.0.100.2/32 IBGP 255 103 RD 8.8.8.8 Eth-Trunk1.1
200.0.100.3/32 IBGP 255 103 RD 7.7.7.7
200.0.100.4/32 IBGP 255 103 RD 7.7.7.7
200.0.100.5/32 IBGP 255 103 RD 7.7.7.7
200.0.100.6/32 IBGP 255 103 RD 8.8.8.8 Eth-Trunk1.1
200.0.100.7/32 IBGP 255 103 RD 7.7.7.7
200.0.100.8/32 IBGP 255 103 RD 8.8.8.8 Eth-Trunk1.1
200.0.100.9/32 Direct 0 0 D 127.0.0.1 LoopBack65535
200.0.100.10/32 IBGP 255 103 RD 10.10.10.10 Eth-Trunk1.1
200.0.100.11/32 IBGP 255 103 RD 7.7.7.7
200.0.100.12/32 IBGP 255 103 RD 8.8.8.8 Eth-Trunk1.1
200.0.100.13/32 IBGP 255 103 RD 13.13.13.13
200.0.100.14/32 IBGP 255 203 RD 14.14.14.14 Eth-Trunk1.1

130.10.100.0/24 Direct 0 0 D 130.10.100.1

130.10.100.1/32 Direct 0 0 D 127.0.0.1
130.10.100.10/32 Direct 0 0 D 127.0.0.1
130.10.100.255/32 Direct 0 0 D 127.0.0.1
255.255.255.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0
l Check the connectivity between the devices at the access layer and U2000. Run the ping
command on the CSG.
l Check the connectivity between the devices at the aggregation layer and U2000. Run the
ping command on the ASGs and ASBRs at the aggregation layer.
l Check the connectivity between the devices at the core layer and U2000. Run the ping
command on the MASGs and ASBRs at the core layer.
7.2 Deploying a DCN VRF Solution

manage the equipment.
7.2.1 Deploying the DCN Automatically Available Solution (U2000

Connected to the IPCore Network)
Devices can be loaded and managed on the U2000 after the DCN automatically available
function is enabled on the devices.
Configuration Principle
l Configure SNMP on each NE to be managed.
l Query and record the NE ID and NE IP address of each NE. If the default NE ID and NE
IP address of an NE are not used, you can plan and configure an NE ID and an NE IP
address for the NE.
l Enable DCN in the system view and interface view for each NE.
l Configure STelnet parameters for each NE.
l On the interface connecting the gateway NE and the U2000, configure a DCN VPN instance
and an IP address.
l Enable the DCN auto-reporting function on the gateway NE.
l Configure a static route leading to the IP address of the NE to be loaded on the U2000
server and ensure that the route is available.
The following figure shows how a public DCN is deployed. As shown in the figure, the U2000
server is dual-homed to two MASGs, and in the middle is the Layer 2 network. Such networking
is typical. In practice, a Layer 3 network may be deployed. If this is the case, a static route
destined to the U2000 server must be configured for each MASG, and the gateway on the static
route must be represented by the IP address of the ingress interface on a third-party router.

Figure 7-2 DCN automatically available solution
AS 100 AS 200

GE0/2/16 GE2/1/0 GE1/0/1 GE1/0/1
GE1/1/2 GE1/0/0 GE1/0/0 GE1/0/0 GE7/1/11
GE1/0/0 GE2/0/1 GE2/0/1
GE0/2/17
Eth-Trunk 1
LSW
U2000 Server
GE0/2/17 GE2/0/1 GE2/0/1 130.10.100.0/24

GE1/0/0
GE1/1/2 GE1/0/0 GE1/0/0 GE1/0/0
GE2/1/0 GE1/0/1 GE1/0/1 GE7/1/11
GE0/2/16
DCN Interfaces
Data Planning
NEID Set before the device is By default, the NE ID and NE

delivered and can be planned IP address are associated.
and configured as required. After the NE ID is changed,
the NE IP address will also
changes.
However, the NE ID does not
change after the NE IP
address is changed. In
addition, the default
association between the NE
ID and NE IP address no long
exists after the NE IP address
is once changed. In other
words, the NE IP address
does not change even if the
NE ID is changed later.
NEIP Set before the device is All NE IP addresses are in the

delivered and can be planned 128.0.0.0/8 network
and configured as required. segment.
U2000 IP address U2000: 130.10.100.20/24 -

snmp-agent sys-info all Enables the SNMP trap

version function in SNMPv1,
SNMPv2C, and SNMPv3.

snmp-agent community Huawei@123 Sets read community names.

read cipher mib-view iso-view The NMS can access a device
only when the community
names set on the NMS are the
same as those set on the
device.
snmp-agent community Huawei@123 Sets write community names.

write cipher mib-view iso-view The NMS can access a device
only when the community
names set on the NMS are the
same as those set on the
device.
snmp-agent trap enable - Enables all traps on a device.
snmp-agent trap source LoopBack x Configures the loopback

interface as the source
interface that sends trap
messages.

vpn-instance __dcn_vpn__ the Huawei NMS at
params securityname 130.10.100.20.
Huawei@123 v2c private-
netmanager ext-vb
snmp-agent trap enable - Enables the LLDP trap

snmp-agent extend error- Enables extended error

code enable codes.
DCN automatically available solution: The U2000 uses the DCN automatically available
function to manage NEs.
1. Enable DCN in the system view and interface view for each NE.
After DCN is enabled globally for ATN devices, all interfaces are enabled with DCN by
default. After DCN is enabled globally for CX devices, however, not all interfaces are

enabled with DCN by default. To query whether an interface is enabled with DCN, run the
display this command in the interface view.
The following shows the configuration of CSG1 as an example:
dcn //Enable DCN in the system view.
The following shows the configuration of ASG3 as an example:

dcn
#
display this //Query whether DCN is enabled on the interface.
//By default, DCN is enabled on the interface. DCN is enabled on
the first eight ETH interfaces by default.
ETH-trunk interfaces are used between MASGs and the interfaces are in port-switch mode
(that is, a service VLAN that can pass is configured). A DCN VLAN needs to be configured
at the main member interface and it can be set to 4094. The DCN VLAN cannot be the
same as the service VLAN.
dcn
dcn vlan 4094
dcn
dcn vlan 4094
2. Configure SNMP.
l Query the management loopback interface used by a DCN. By default, the ATN device
uses loopback1023 and the CX device uses loopback2147483647.
Run the following command to query the management loopback interface used by a
DCN.
display dcn brief
l Configure SNMP on each NE to be managed.

The following shows the configuration of MASG1:
lldp enable //Enable the LLDP trap function globally.
#
snmp-agent
snmp-agent sys-info version all //Configure the system to use SNMP of all
versions.
snmp-agent mib-view included iso-view iso //The SNMP MIB view contains the
iso subtree.
snmp-agent community write cipher Huawei@123 mib-view iso-view //The write
community has both of the write and read right.
// When the community names of write and read are the same, the
read community command will be covered by the write community command.
snmp-agent trap enable
__dcn_vpn__ params securityname Huawei@123 v2c private-netmanager ext-vb
//Configure the SNMP agent to send
SNMP trap messages to 130.10.100.20 U2000 management IP address and set
the community name to Huawei@123.
//The parameters "private-netmanager"
and "ext-vb" are advised to be configured when a Huawei NMS is used.
snmp-agent trap source LoopBack2147483647 //The DCN generates
LoopBack2147483647 automatically.
snmp-agent extend error-code enable //Enable extended error codes.
l Create VPN instances on all NEs for NE management on the U2000.

set net-manager vpn-instance __dcn_vpn__ //Configure VPN instances that the
U2000 uses for NE management.

NOTE
Previous commands indicate that the equipment uses VPN channels for interworking with the
U2000. If the equipment needs to set up an FTP connection with a public network address, the
ftp command must be run with the public-net parameter. Otherwise, the equipment uses VPN
channels for FTP communication.
3. Query and record the NE ID and NE IP address of each NE.
In this example, MASG1 and MASg2 are gateway NEs.
display dcn brief
If the default NE ID and NE IP address of an NE are not used, you can plan and configure
an NE ID and an NE IP address for the NE. The following shows the configuration of
MASG1:
Configure the NE ID in the user view.
set neid 9a0009
Configure the NE IP address in the DCN view.

dcn
ne-ip 128.154.0.9 255.255.255.255
4. Configure user login parameters on each NE, with the STelnet as the login mode.
The following shows the configuration of STelnet parameters on MASG1:
user-interface maximum-vty 15
user-interface vty 0 14
idle-timeout 5 0
aaa
local-user Root password cipher Changeme_123//Configure the user name and
password.
local-user Root service-type ssh//Configure SSH as the login method for the
user.
local-user Root level 15//Configure the user level.
#
stelnet server enable//Enable the STelnet service on the SSH server.
ssh user root//Add an SSH user.
ssh user root authentication-type password//Configure an authentication mode
for the SSH user.
ssh user root service-type stelnet//Configure STelnet as the login method for
the SSH user.
#
5. Bind the DCN VPN instance (__dcn_vpn__) to the interface connecting the gateway
NE and DCN network.
The configuration of MASG1 is provided below:
negotiation auto
description to-NMS-U2000
ip binding vpn-instance __dcn_vpn__
ip address 130.10.100.1 255.255.255.0
ospf cost 50 //Set the cost values on MASG1 and MASG2 to 50 and 100
respectively to control route selection.

NOTE
If DCN has been enabled globally, check whether DCN has been enabled for the active port connected to
the U2000. If yes, disable the DCN function.
undo dcn
ospf 65534 vpn-instance __dcn_vpn__
silent-interface GigabitEthernet7/1/11 //Set the interface that connected to
U2000 network as an silent-interface.
The configuration of MASG2 is provided below:

negotiation auto
ip address 130.10.100.2 255.255.255.0
ospf cost 100
NOTE
If DCN has been enabled globally, check whether DCN has been enabled for the active port connected to
the U2000. If yes, disable the DCN function.
undo dcn
silent-interface GigabitEthernet7/1/11
6. Enable the DCN auto-reporting function on the gateway NE. Then, you can query the
route to the U2000 by running the disp ip routing-table vpn-instance
__dcn_vpn__command.
The following shows the configuration of MASG1:
dcn
auto-report //Enable the DCN auto-reporting function.
7. Configure static routes on the U2000 server and ensure that the route between the
U2000 and the gateway NE is available.
Issue the following commands through CMD on the Windows system:

route add 128.154.0.0 mask 255.255.0.0 130.10.100.10 -p
8. Add NEs to be managed by the U2000.

9. (Optional): When a Layer-3 network needs to be passed through, set a static route to the
U2000 on the MASG. The gateway address is the IP address of the ingress interface of a
third-party router.

AS 100 AS 200

130.10.100.1/24
GE7/1/11
130.10.100.11/24
Eth-Trunk 1
U2000 Server
130.10.101.1/24
GE7/1/11
130.10.100.2/24
DCN Interfaces
a. Configure a static route to the U2000 on the MASG.

ip route-static vpn-instance __dcn_vpn__ 130.10.101.1 255.255.255.255
GigabitEthernet7/1/11 130.10.100.11 preference 5
b. onfigure the MASG to import U2000 routes. The following uses MASG1 as an
example.
#
route-policy U2000 permit node 10
#
ospf 65534
import-route static cost 1000 route-policy U2000 //Configure the master
MASG to import routes and set the cost value to 1000.
//Note that the cost
value must be set to 2000 for routes imported by the slave MASG.
c. Configure remaining data in the same way as data is configured for a Layer-2 DCN.
7.2.2 Deploying DCN VRF for a Large Network (U2000 Connected

to the IPCore Network)
manage the equipment. If the network scale is large, the network is divided for deploying DCN
VRF.
Configuration Roadmap
l Configure SNMP for all NEs to be managed.
l Query and record NE IDs and IP addresses. If the default NE IDs and IP addresses are not
used, plan new NE IDs and IP addresses.
l Enable DCN for all NEs and interfaces.
l Configure user login parameters for all NEs.
l Configure a VPN for the gateway NEs and interfaces connected to the U2000, bind the
VPN to the DCN. and configure related IP addresses.
l Enable the DCN auto-report function for the MASGs, which function as the gateway NEs.

l Configure static routes between the U2000 server and the IP addresses of the NEs to be
loaded, to make the NEs reachable to the U2000.
l On ASBRs at the core layer:
– Create an OSPF process for each connected IPRAN area.
– Bind the interfaces connected to different IPRAN areas to the corresponding OSPF
process configured with DCN VRF.
– Configure route importing for the ASBRs: import routes of the U2000 to the OSPF
process of the aggregation ring in the IPRAN area, and import routes of the OSPF
process into the core ring.
l On ASGs at the core layer of the IPRAN:
– Create an OSPF process for each connected access ring.
– Bind the interfaces connected to different access rings to the corresponding OSPF
process configured with DCN VRF.
– Configure route importing on the ASGs: import routes of the U2000 to OSPF processes
for access rings, and import routes of the OSPF processes into the aggregation ring.
The following figure shows the typical public DCN deployment: the U2000 is dual-homed to
two MASGs, and an L2 network is deployed between the MASGs and the U2000. An L3 network
may be traversed in the actual application. You need to set static routes from the MASGs to the
U2000. The gateway is located at the ingress interface of a third-party router.
Figure 7-3 DCN VRF solution
AS 100 AS 200

GE0/2/16 GE2/1/0 GE1/0/1 GE1/0/1
GE1/1/2 GE1/0/0 GE1/0/0 GE1/0/0 GE7/1/11
GE1/0/0 GE2/0/1 GE2/0/1
GE0/2/17
Eth-Trunk 1
LSW
U2000 Server
GE0/2/17 GE2/0/1 GE2/0/1 130.10.100.0/24

GE1/0/0
GE1/1/2 GE1/0/0 GE1/0/0 GE1/0/0
GE2/1/0 GE1/0/1 GE1/0/1 GE7/1/11
GE0/2/16
DCN Interfaces

Data Plan
NEID Factory default. The value By default, the IP address and

can be modified according to ID of an NE are correlated.
the network plan. If an NE ID is modified, the
NE IP address is modified
accordingly.
However, if the NE IP is
modified, the NE ID is not
modified accordingly. After
the NE IP address is
modified, the default
correlation relationship loses
effect.
NEIP Factory default. The value All NE IP addresses are in the

can be modified according to 128.0.0.0/8 network
the network plan. segment.
U2000 IP address 130.10.100.20/24 -
snmp-agent sys-info all Enables this function in

version SNMPv1, SNMPv2C, and
SNMPv3.

snmp-agent community Huawei123! Sets read and write

read cipher mib-view iso-view community names. The NMS
snmp-agent community Huawei@123 Sets read and write

write cipher mib-view iso-view community names. The NMS
snmp-agent trap enable - Enables all traps on a device.

snmp-agent trap source LoopBack x Sets a LoopBack interface as

the source interface of Trap
messages. The interfaces can
be found through query.

vpn-instance __dcn_vpn__ the Huawei NMS at
params securityname 130.10.100.20.
Huawei@123 v2c private-
netmanager ext-vb
snmp-agent trap enable - Enables the LLDP trap

snmp-agent extend error- Opens the extended error

code enable codes of devices.
DCN VRF solution: The U2000 manages NEs using a private network configured with DCN
VRF.
1. Enable DCN for all NEs and interfaces.

After DCN is enabled for all ATNs, DCN is enabled for interfaces of the ATNs by default.
After DCN is enabled for all CXs, DCN is not enabled for interfaces of the CXs by default.
Run the display this command for each interface to check whether DCN is enabled for the
interface.
dcn//Enables DCN globally.

dcn
#
display this//Checks whether DCN is enabled for the interface. By default, DCN
is enabled for the interface. By default, DCN is enabled for the first eight
ETH interfaces.
MASGs interconnect through Eth-Trunk interfaces. The port-switch command has been
run on the interfaces and the VLAN is configured to support transmission of allowed
services. In this case, DCN VLAN must be configured for the interfaces that home the Eth-
Trunk interfaces. Set the DCN VLAN ID to 4094. The DCN VLAN must be different from
the service VLAN.
dcn
dcn vlan 4094
dcn
dcn vlan 4094
2. Configure SNMP.

l Query the loopback interfaces used for DCN management. By default, the
loopback1023 interface is used on an ATN, and the loopback2147483647 interface is
used on a CX.
Run the following command to query the used interface:
display dcn brief
l Configure SNMP for all NEs to be managed.

The following uses MASG1 as an example to illustrate the configuration.
lldp enable//Enables LLDP globally.
#
snmp-agent
snmp-agent sys-info version all//Enables SNMP of all versions on the
system.
snmp-agent mib-view included iso-view iso//The SNMP MIB view contains the
iso subtree.
__dcn_vpn__ params securityname Huawei@123 v2c private-netmanager ext-vb
//Allows the transmission of SNMP
Trap messages to the U2000 (management IP address: 130.10.100.20). The
community name of Huawei@123 is used. If the NMS is a Huawei NMS, it is
recommended to set the private-netmanager and ext-vb parameters.
snmp-agent trap source LoopBack2147483647//LoopBack2147483647 is generated
in the DCN automatically.
for equipment.
l Configure a VPN instance for all NEs to facilitate management by the U2000.
set net-manager vpn-instance __dcn_vpn__//Sets the VPN instance for the NMS
to management equipment.
NOTE
Configuring the preceding commands indicates that communication between the devices and the
NMS is implemented over VPN channels. If the devices require the FTP client to access a public
network address, add the public-net parameter in the FTP command; otherwise, the devices will
use VPN channels for FTP access.
3. Query and record NE IDs and IP addresses.
In this example, MASG1 and MASG2 are gateway NEs.
display dcn brief
Plan NE IDs and IP addresses if you do not want to use the factory defaults. The following
uses MASG1 as an example to illustrate the configuration.
Enable BFD in the user view.
set neid 9a0005
NOTE
If an NE ID is manually set, the NE IP address changes with the NE ID, and there is no need to manually
modify the NE IP address.
Set NE IP addresses in the DCN view.
dcn
ne-ip 128.154.0.5 255.255.255.255

NOTE
After an NE IP address is set manually, it no longer changes when the correlated NE ID is changed.
4. Configure an OSPF process enabled with DCN VRF.
l Configure an OSPF process enabled with DCN VRF on MASGs at the core layer.
The default OSPF process enabled with DCN VRF is used. The default process ID is
65534.
#
ospf 65534 vpn-instance
__dcn_vpn__
opaque-capability
enable
vpn-instance-capability
simple
area
0.0.0.0
network 0.0.0.0 255.255.255.255
l Configure an OSPF process enabled with DCN VRF on ASBRs at the core layer.
Use the default OSPF process enabled with DCN VRF. In addition, create an OSPF
process for each IPRAN area connected to an ASBR pair. The default process ID is
65534.
The following uses ASBR3 as an example to illustrate the configuration.
#
__dcn_vpn__
opaque-capability
enable
hostname
simple
area
0.0.0.0
network 0.0.0.0
255.255.255.255
#
#
__dcn_vpn__
description DCN ospf for
IPRAN_200
opaque-capability
enable
area
0.0.0.0
#
#
interface GigabitEthernet1/0/0 //Adds an interface in the IPRAN into the
OSPF65533 process.
undo
shutdown
dcn
dcn ospf enable 65533 area 0.0.0.0
#
l Configure an OSPF process enabled with DCN VRF on ASGs at the aggregation
layer.

Use the default OSPF process enabled with DCN VRF. In addition, create an OSPF
process for each access ring connected to an ASG pair. The default process ID is 65534.
#
__dcn_vpn__
opaque-capability
enable
hostname
simple
area
0.0.0.0
network 0.0.0.0
255.255.255.255
#
#
__dcn_vpn__
description DCN ospf for
access_1
opaque-capability
enable
area
0.0.0.0
#
#
interface GigabitEthernet1/1/2 //Adds an interface connected to an access
ring into the OSPF65533 process.
undo
shutdown
dcn
dcn ospf enable 65533 area 0.0.0.0
#
5. Configure route importing.

l MASGs (core layer)
#
ip ip-prefix U2000 index 10 permit 130.10.100.0 24 ////Permits addresses in
the same network segment as the U2000 by matching the addresses with the ip
ip-prefix U2000.
#
route-policy U2000-private permit node
10
if-match ip-prefix
U2000
#
#
__dcn_vpn__
import-route direct cost 1000 route-policy U2000-private //Sets the cost
when the MASG connects to the U2000 through an L2 network. Cost is set to
2000 for MASG2.
import-route static cost 1000 route-policy U2000-private //Sets the cost
when the MASG connects to the U2000 through an L3 network. Cost is set to
2000 for MASG2.
#
l ASBRs (core layer)

#
ip ip-prefix ipran-loopback index 10 permit 0.0.0.0 0 greater-equal 32 less-
equal 32


#
route-policy U2000-tag permit node
10
if-match ip-prefix
U2000
apply tag
2000
#
#
route-policy ipran-loopback permit node
10
if-match ip-prefix ipran-loopback
apply tag
2000
#
10
if-match tag
2000
apply preference
255
#
#
__dcn_vpn__
default cost inherit-
metric
import-route ospf 65534 route-policy U2000-
tag
preference ase route-policy pref-nms
150
#
__dcn_vpn__
metric
import-route direct tag
2000
import-route ospf 65533 route-policy ipran-loopback
preference ase route-policy pref-nms 150 //Prevents
loops.
l ASGs (aggregation layer)

#
ip ip-prefix acc index 10 permit 0.0.0.0 0 greater-equal 32 less-equal 32
#
route-policy acc-loopback permit node
10
apply tag 2
#
#
route-policy U2000-tag permit node
10
if-match tag
2000
apply tag
2
#
#
10
if-match tag
2


#
#
__dcn_vpn__
metric
import-route ospf 65534 route-policy U2000-
tag
preference ase route-policy pref-nms
150
#
__dcn_vpn__
metric
import-route direct tag
2
import-route ospf 65533 route-policy acc-
loopback
preference ase route-policy pref-nms 150 //Prevents
loops.
#
6. Configure user login parameters for each NE to enable users to log in to the equipment
in STelnet mode.
idle-timeout 5 0
aaa
local-user root password cipher Changeme_123//Configures the user name and
password.
local-user root service-type ssh//Sets the user login mode to SSH.
local-user root level 15//Sets the user level.
#
stelnet server enable//Enables the STelent server.
ssh user root//Configures an SSH user.
ssh user root authentication-type password//Sets the authentication mode for
the SSH user.
ssh user root service-type stelnet//Sets the login mode of the SSH user to
STelnet.
#
7. Bind gateway NEs' interfaces that are connected to the DCN network to the VPN
instance __dcn_vpn__.
negotiation auto
ip address 130.10.100.1 255.255.255.0
ospf cost 50 //Sets the cost to 50 for routes of MASG1 and to 100 for routes
of MASG2, to implement path selection.

NOTE
undo dcn
silent-interface GigabitEthernet7/1/11 //Configures the interface connected
to the U2000 as a silent interface.

negotiation auto
ip address 130.10.100.2 255.255.255.0
ospf cost 100
NOTE
undo dcn
silent-interface GigabitEthernet7/1/11
8. Configure the DCN auto-report function for gateway NEs. After the configuration, run the
disp ip routing-table vpn-instance __dcn_vpn__ command to query routes on the U2000
server.
dcn
auto-report//Enables the DCN auto-report function.
9. Configure static routes on the U2000 server, so that the gateway NEs are reachable
to the U2000 server.
On Windows, run the following command in the CMD:

route add 128.154.0.0 mask 255.255.0.0 130.10.100.10 -p
10. For details about adding NEs on the U2000, see the Singe-OSS IPRAN ATN+CX (HVPN
& FMC) Network Design.
11. (Optional): When an L3 network needs to be passed through, you need to set static routes
destined for the U2000 for the MASGs. The gateway is located at the ingress interface of
a third-party router.

AS 100 AS 200

130.10.100.1/24
GE7/1/11
130.10.100.11/24
Eth-Trunk 1
U2000 Server
130.10.101.1/24
GE7/1/11
130.10.100.2/24
DCN Interfaces
a. Configure static routes destined for the U2000 on the MASGs.

ip route-static vpn-instance __dcn_vpn__ 130.10.101.1 255.255.255.255
GigabitEthernet7/1/11 130.10.100.11 preference 5
b. Other configurations are similar to the scenario when the DCN network is an L2
network and are not illustrated here.

l Run the display ip routing-table vpn-instance vpn-instance-name command to query a
routing table.
<MASG1>display ip routing-table vpn-instance __dcn_vpn__
------------------------------------------------------------------------------
Routing Tables: __dcn_vpn__
128.154.0.0/16 Direct 0 0 D 128.154.9.9

LoopBack2147483647
128.154.1.1/32 O_ASE 150 0 D 128.154.13.13 DCN-
Serial2/0/2:0
128.154.2.2/32 O_ASE 150 0 D 128.154.13.13 DCN-
Serial2/0/2:0
128.154.3.3/32 O_ASE 150 300 D 128.154.13.13 DCN-
Serial2/0/2:0
128.154.4.4/32 O_ASE 150 300 D 128.154.13.13 DCN-
Serial2/0/2:0
O_ASE 150 300 D 128.154.10.10 DCN-
Serial2/0/3:0
128.154.5.5/32 O_ASE 150 0 D 128.154.13.13 DCN-
Serial2/0/2:0
128.154.6.6/32 O_ASE 150 0 D 128.154.13.13 DCN-
Serial2/0/2:0
O_ASE 150 0 D 128.154.10.10 DCN-
Serial2/0/3:0
128.154.7.7/32 OSPF 10 200 D 128.154.13.13 DCN-
Serial2/0/2:0
128.154.8.8/32 OSPF 10 300 D 128.154.13.13 DCN-
Serial2/0/2:0
OSPF 10 300 D 128.154.10.10 DCN-
Serial2/0/3:0
128.154.9.9/32 Direct 0 0 D 127.0.0.1
LoopBack2147483647

128.154.10.10/32 Direct 0 0 D 128.154.10.10 DCN-

Serial2/0/3:0
128.154.11.11/32 O_ASE 150 200 D 128.154.13.13 DCN-
Serial2/0/2:0
128.154.12.12/32 O_ASE 150 200 D 128.154.13.13 DCN-
Serial2/0/2:0
O_ASE 150 200 D 128.154.10.10 DCN-
Serial2/0/3:0
128.154.13.13/32 Direct 0 0 D 128.154.13.13 DCN-
Serial2/0/2:0
128.154.14.14/32 OSPF 10 200 D 128.154.10.10 DCN-
Serial2/0/3:0
128.154.255.255/32 Direct 0 0 D 127.0.0.1
LoopBack2147483647
130.10.100.0/24 Direct 0 0 D 130.10.100.1
130.10.100.1/32 Direct 0 0 D 127.0.0.1
130.10.100.10/32 Direct 0 0 D 127.0.0.1
130.10.100.255/32 Direct 0 0 D 127.0.0.1
l Run the display dcn ne-info command to display NE information of a DCN.

<MASG1>display dcn ne-info
Network Element Info
NEID NEIP DISTANCE LIFECYCLE HOSTNAME

0.154.7.7 128.154.7.7 1 17 ASBR3
0.154.8.8 128.154.8.8 2 17 ASBR4
0.154.10.10 128.154.10.10 0 20 MASG2
0.154.13.13 128.154.13.13 0 19 RR3
0.154.14.14 128.154.14.14 1 19 RR4
Total Number: 5

Configuration Guide (CLI) 8 Deploying Mobile Backhaul Services
8 Deploying Mobile Backhaul Services
About This Chapter
For a mobile backhaul network that carries various types of wireless services, proper network
planning and deployment are very important.
8.1 Deploying E2E Mobile Backhaul Services (HVPN+Labeled BGP)

This section describes how to configure E2E mobile backhaul services in the HVPN+Labeled
BGP sub-solution.
8.2 Deploying E2E Mobile Backhaul Services (Labeled BGP to Edge)

This section describes how to deploy E2E mobile backhaul services in the Labeled BGP to Edge
sub-solution.
8.3 Deploying Local Switching Ethernet Service Bearer and Protection (HVPN+Labeled BGP)
This section describes how to configure local switching Ethernet service bearer and protection
in the HVPN+Labeled BGP solution.
8.4 Deploying Local Switching Ethernet Service Bearer and Protection (Labeled BGP to Edge)
in the Labeled BGP to Edge solution.
8.5 Deploying QoS

This chapter describes the roadmap, data plan, and procedure for configuring QoS in the DiffServ
model.

8.1 Deploying E2E Mobile Backhaul Services (HVPN

+Labeled BGP)
This section describes how to configure E2E mobile backhaul services in the HVPN+Labeled
BGP sub-solution.
8.1.1 E2E Ethernet Service Deployment Solution

This section describes the roadmap for configuring E2E Ethernet service bearer and protection.

LTE S1 service
L3VPN L3VPN
RR1 RR3
eBGP Multi-Hop VPN v4

RR4
RR2
VPNv4
In the HVPN+Labeled BGP sub-solution, the roadmap for configuring Ethernet service bearer
and protection is as follows:
1. Deploy MP-iBGP. Configure neighbor relationship in the VPNv4 address family view.
In AS 100
l Set up full-mesh MP-iBGP peer relationship between ASGs and the master and slave
RRs (RR1 and RR2).
l An ASG selectively reflects VPNv4 routes: for a route within the local access ring, the
ASG does not change the next hop; for a route destined for a node on another ring or
domain, the ASG changes the next hop of the route to itself.
In AS 200
RRs (RR3 and RR4).
2. Deploy MP-eBGP. Configure neighbor relationship in the VPNv4 address family view.
l Set up MP-eBGP peer relationship between the master RR (RR1) in AS 100 and the
master RR (RR3) in AS 200 (not directly connected).

l Set up MP-eBGP peer relationship between the slave RR (RR2) in AS 100 and the slave
RR (RR4) in AS 200 (not directly connected).
3. Configure VPN services.
l Configure a VPN instance for CSGs and MASGs.
4. Configure protection switching.
l Enable BGP Auto FRR on MASGs, ASBRs, and ASGs.
l Configure VPN FRR on MASGs and CSGs.
5. Two MASG dual-homing protection methods are available: configuring VRRP and
configuring active and standby routes. Configuring VRRP is recommended.
l Configure VRRP.
If SGWs/MMEs connect to MASGs through master and slave interfaces, VRRP over
VLANIF must be configured for the master and slave MASGs for service protection.
– Configure the interconnect interfaces between the master and slave MASGs and the
AC interface as VLANIF interfaces.
– When an MASG pair is connected to multiple pairs of SGW/MME interfaces, deploy
one or more VLANIF interfaces on the MASGs based on the SGW/MME network
segments.
l Deploy active and standby routes.
If an SGW/MME uses its logical interface (similar to the loopback interface of a router)
for communication and must support dual-receiving through master and standby
interfaces, it can support interconnection using active and standby routes.
– In this mode, configure static routes with the same priority from the master and slave
MASGs to SGW/MME, and configure static routes to be advertised to private
network IGP instances. For example, you can set the preference in static routes to
5.
– Enable the private network IGP on the subinterfaces of the interconnected interfaces
between the master and slave MASGs. Configure private network static routes and
IGP routes to be advertised to BGP.
l Advertisement of a private network route from a CSG to an MASG
103 RR1 RR3

103
103 103
10
3->
203
50
203
3
203

203
203
RR4
RR2

A private network route from an eNodeB is dually homed to the master and slave ASGs.
The MED value is set to 103 by the master ASG and to 203 by the slave ASG. The
master ASG sends the route to the master RR without modifying the MED value, and
to the slave RR after modifying the MED value from 103 to 503. The slave ASG sends
the route to the master and slave RRs without modifying the MED values. In this case,
the master RR prefers the route from the master ASG, and the slave RR prefers the route
from the slave ASG. The master and slave RRs at the aggregation layer advertise the
routes to the core layer based on the eBGP neighbor relationship. When the core layer
RRs forward the routes to the MASGs, an export policy is configured for the RRs or an
import policy is configured for the MASGs, so that the MASGs can select a route
according to the MED values.
l Advertisement of a private network route from an MASG to a CSG
RR1 RR3
103
103
3
50
103 103
20
3
203
203

203
203
RR4
RR2

The roadmap for configuring E2E Ethernet service bearer and protection is as follows:

Figure 8-4 Configuration flowchart
8.1.3 Data Planning

This section provides the data plan for L3VPN deployment.
NOTE
Table 8-1 Service interfaces
NE Role Value Remarks
CSG1 interface Ethernet0/3/0.10: -

192.168.1.1/24
MASG1 interface vlanif100: -

192.168.2.1/24

192.168.2.2/24

Table 8-2 MPLS VPN parameters
VPN instance name LTE-RAN -
RD value CSG1: 100:100 In this solution, it is

ASG3: 100:100 recommended that you
configure RDs for all devices
ASG4: 100:100 on the mobile backhaul
MASG1: 100:100 network to be the same.
MASG2: 100:100
RT CSG: Export RT 100:1, "100:1" indicates network-

Import RT 200:1 wide routes, and "200:1"
ASG: Export RT 200:1 indicates routes for E2E
100:1, Import RT 100:1 mobile backhaul services
originated from MASGs.
MASG: Export RT 200:1
100:1, Import RT 100:1
Label allocation mode apply-label per-instance Enables one VPN route label
to be allocated for each VPN.
Parameter CSG1 ASG3 ASG4 RR1 RR2
BGP process 100 100 100 100 100

ID
router-id 1.1.1.1 3.3.3.3 4.4.4.4 11.11.11.11 12.12.12.12
iBGP peer - CSG: 1.1.1.1 CSG: - -

(VPNv4 1.1.1.1
address
family)
iBGP peer ASG3: RR1: RR1: ASG3: ASG3:

(VPNv4 3.3.3.3 11.11.11.11 11.11.11.11 3.3.3.3 3.3.3.3
address ASG4: RR2: RR2: ASG4: ASG4:
family) 4.4.4.4 12.12.12.12 12.12.12.12 4.4.4.4 4.4.4.4
eBGP peer - - - RR3: RR4:

(VPNv4 13.13.13.13 14.14.14.14
address
family)
vpn-target Enabled Disabled Disabled Disabled Disabled

Setting the - Yes Yes - -

next hop to the
local IP
address
Parameter RR3 RR4 MASG1 MASG2
BGP process ID 200 200 200 200
router-id 13.13.13.13 14.14.14.14 9.9.9.9 10.10.10.10
iBGP peer (VPNv4 MASG1: MASG1: RR3: RR3:

address family) 9.9.9.9 9.9.9.9 13.13.13.13 13.13.13.13
MASG2: MASG2: RR4: RR4:
10.10.10.10 10.10.10.10 14.14.14.14 14.14.14.14
eBGP peer (VPNv4 RR1: RR2: - -

address family) 11.11.11.11 12.12.12.12
vpn-target Disabled Disabled Enabled Enabled
Setting the next hop to the - - - -

local IP address
8.1.4 Configuring MP-BGP

This section describes how to configure MP-BGP.
Configuring CSGs
Configure the MP-iBGP peer of CSG1.
l Configure MP-BGP.
#
bgp 100
router-id 1.1.1.1
peer 3.3.3.3 as-number 100 //Sets up peer relationship between a CSG and the
master ASG.
peer 3.3.3.3 tracking delay 30 //Enables BGP Peer Tracking, to implement FRR
on a network by enabling an NE to quickly detect a fault on a neighbor.
peer 4.4.4.4 as-number 100 //Sets up peer relationship between a CSG and the
slave ASG.
#
ipv4-family unicast
undo peer 3.3.3.3 enable


#
ipv4-family vpnv4
policy vpn-target //Enables VPN target filtering for the received VPNv4
routes. Only the VPNv4 route whose Export RT attribute matches the local Import
RT attribute can be added to the routing table.
peer 3.3.3.3 enable
peer 4.4.4.4 enable
#
ipv4-family vpn-target //Enables VPNv4 ORF.
peer 3.3.3.3 enable
peer 4.4.4.4 enable
#

#
ip community-filter basic epc permit 1000:1 //Defines the community attribute
filtering table of routes on the EPC side.
ip community-filter basic default permit 1000:2 //Defines the community
attribute filtering table of default routes.
#
#
route-policy to-csg-as-master permit node
10
epc
apply ip-address next-hop peer-
address
apply cost
103
#
100
apply cost
103
#
route-policy from-csg-as-master permit node 10 //Configures the receiving of
routes from CSGs. If ASG3 is the master ASG of CSG1, the MED value is set to
103.
apply cost 103
#
route-policy vpnv4-from-MRR permit node 10 //Sets the ingress routing policy
for receiving routes from the master RR, to increase the priority of EPC routes
sent from the master MASG.
if-match community-filter epc
#
#
route-policy vpnv4-to-MRR deny node
10
default
#
route-policy vpnv4-to-MRR permit node

100
the ASG itself.
#
route-policy vpnv4-to-SRR deny node
10

default
#
route-policy vpnv4-to-SRR permit node
20
if-match cost
103
the ASG itself.
apply cost
503
#
100
the ASG itself.
#
l Configure MP-iBGP.
#
bgp 100
group CSG internal //Sets up an iBGP peer group. Different group names can
be configured for different access rings.
peer CSG tracking delay 30
peer CSG timer connect-retry 300 //Sets the connect-retry time to set up BGP
neighbor relationship with a CSG.
#
ipv4-family unicast
undo peer CSG enable
#
ipv4-family vpnv4
reflect change-path-attribute //Sets an RR to modify the route attributes of
BGP routes by using the export policy.
undo policy vpn-target //Configures the receiving of all VPNv4 routes.
auto-frr
peer 11.11.11.11 route-policy vpnv4-to-MRR export
peer 11.11.11.11 route-policy vpnv4-from-MRR import
peer 12.12.12.12 route-policy vpnv4-to-SRR export
peer CSG enable
peer CSG route-policy from-csg-as-master import
peer CSG route-policy to-csg-as-master export
peer 1.1.1.1 enable
#
ipv4-family vpn-target
peer 1.1.1.1 enable

#
ip community-filter basic epc permit
1000:1

ip community-filter basic default permit 1000:2

#
#
route-policy to-csg-as-slave permit node 10
apply ip-address next-hop peer-address
apply cost 203
#
apply cost 203
#
route-policy from-csg-as-slave permit node 10
apply cost 203
#
#
10
default
#
100
address
#
10
default
#
20
if-match cost
103
address
apply cost
503
#
100
address
#
#
l Configure MP-BGP.
#
bgp 100
group CSG internal
peer CSG timer connect-retry 300
#
ipv4-family unicast
#
ipv4-family vpnv4

undo policy vpn-target
auto-frr
peer CSG enable
peer CSG route-policy from-csg-as-slave import
peer CSG route-policy to-csg-as-slave export
peer 1.1.1.1 enable
#
peer 1.1.1.1 enable

l Configure MP-BGP.
#
bgp 100
peer 13.13.13.13 as-number 200 //Sets up eBGP peer relationship with the
master RR (RR3) in AS 200.
peer 13.13.13.13 ebgp-max-hop 10 //Configures BGP to set up eBGP peer
relationships with the peers on the non-directly-connected network and
specifies the maximum number of hops.
#
ipv4-family unicast
#
ipv4-family vpnv4
peer 3.3.3.3 enable
peer 3.3.3.3 next-hop-invariable
peer 4.4.4.4 enable
#

l Configure MP-BGP.
#
bgp 100
peer 14.14.14.14 as-number 200 //Sets up eBGP peer relationship with the slave
RR in AS 200.

peer 14.14.14.14 ebgp-max-hop 10

#
ipv4-family unicast
#
ipv4-family vpnv4
peer 3.3.3.3 enable
peer 4.4.4.4 enable
#


#
ip community-filter basic epc permit 1000:1
#
route-policy vpnv4_epc_x2 permit node 10
#
l Configure MP-BGP.
#
bgp 200
#
ipv4-family unicast
#
ipv4-family vpnv4
peer 11.11.11.11 route-policy vpnv4_epc_x2 export //Advertises routes
matching with the EPC to RRs at the aggregation layer, and filters out NMS
routes or other routes with unknown sources.
peer 9.9.9.9 enable
#



#
#
#
l Configure MP-BGP.
#
bgp 200
#
ipv4-family unicast
#
ipv4-family vpnv4
peer 12.12.12.12 route-policy vpnv4_epc_x2 export //Advertises routes
matching with the EPC to RRs at the aggregation layer, and filters out NMS
routes or other routes with unknown sources.
peer 9.9.9.9 enable
#

Configure the MP-BGP peer of the master MASG (MASG1).

#
#
#
route-policy vpnv4-from-MRR permit node
10
apply cost
103
#
route-policy vpnv4-from-SRR permit node
10
apply cost
203
#
10

default
#
route-policy vpnv4-to-MRR permit node 100
#
10
default
#
20
if-match cost
103
apply cost
503
#
route-policy vpnv4-to-SRR permit node 100
#
l Configure MP-BGP.
#
bgp 200
#
ipv4-family vpnv4
policy vpn-target
peer 14.14.14.14 route-policy vpnv4-from-SRR import
#

Configure the MP-BGP peer of the slave MASG (MASG2).
#
#
#
10
apply cost
103
#
10
apply cost
203
#
route-policy vpnfrr permit node
10
apply backup-nexthop
auto
#
10
default
#

#
10
default
#
20
if-match cost
103
apply cost
503
#
#
l Configure MP-BGP.
#
bgp 200
#
ipv4-family vpnv4
policy vpn-target
#
8.1.5 Configuring an L3VPN

VPN instances must be configured to advertise VPNv4 routes and forward data to deploy an
inter-AS L3VPN.
Configuring CSGs
Configuring a CSG as follows:
1. Configure VPN instances.

Create VPN instances based on service types.
#
ip vpn-instance LTE-RAN//Creates a VPN instance.
ipv4-family
route-distinguisher 100:100//A VPN instance IPv4 address family takes effect
only after being configured with an RD.
tnl-policy IPRAN//Configures a TE tunnel as the tunnel for the VPN
instance.
apply-label per-instance//Enables one VPN route label to be allocated for
each VPN.
vpn-target 100:1 export-extcommunity
vpn-target 200:1 import-extcommunity
#
2. Bind VPN instances with specific service interfaces.

#
interface Ethernet0/3/0.10
vlan-type dot1q 10
ip binding vpn-instance LTE-RAN
ip address 192.168.1.1 255.255.255.0
#

NOTE
If DCN is enabled networkwide, check whether DCN is enabled for the interface connected to the BSC.
If yes, disable the DCN function. The configurations are as follows:
interface Ethernet0/3/0
undo dcn
3. If the eNodeB uses a logical IP address, configure a static route destined to the logical IP
address on the CSG and import the static route to the related VPN instance.
ip route-static vpn-instance LTE-RAN 120.16.1.2 255.255.255.255 192.168.1.2 //
A VPN instance must be configured before the destination IP address. Otherwise,
BGP cannot be imported.
//120.16.1.2 is the logical IP address
of the eNodeB. 192.168.1.2 is the IP address of the eNodeB connected to the
backhaul network.
4. Configure route importing to the VPN instance.

bgp 100
ipv4-family vpn-instance LTE-RAN
import-route direct
import-route static
Configuring ASGs
Because VPN ORF is enabled for the CSGs, VRF must be enabled for the ASGs. If VRF is not
enabled for the ASGs, CSGs cannot receive routes from MASGs. The following uses ASG3 as
an example to illustrate the configuration.
#
ip vpn-instance LTE-RAN
ipv4-family
route-distinguisher 100:100
tnl-policy IPRAN
apply-label per-instance
vpn-target 200:1 100:1 export-extcommunity
#
#
bgp 100
#
peer 1.1.1.1 enable
#
Configuring MASGs
The configuration of L3VPN services for an MASG is correlated with the protection mode. For
details, see Deploying Bearer and Protection for Services Between MASGs and SGWs/
MMEs.
8.1.6 Deploying Bearer and Protection for Services Between

MASGs and SGWs/MMEs
This topic describes how to deploy bearer and protection for services between MASGs and
SGWs/MMEs. Service configurations are correlative to the protection mode.
Protection mode for services between MASGs and SGWs/MMEs:
l The VRRP+VLANIF mode is used for protection.

This mode applies to the scenario in which an EPC exchanges (transmits and receives)
packets with MASGs only through one interface but provides two interfaces that work in
master/slave mode for ensuring connection between the SGW/MME and MASGs. The
master and slave interfaces share a common IP address but have different MAC addresses.
– Deploy VRRP on VLANIF interfaces of MASGs, and configure each SGW/MME to
be dual-homed to the MASGs.
– Configure the interfaces that connect an SGW/MME to the master and slave MASGs
to work in master/slave mode and configure the virtual IP address of the VRRP group
as the default gateway IP address. Of the two interfaces, only one interface can receive
packets.
l Active/Standby static routes are configured for protection.
This protection mode applies to the scenario in which an SGW/MME uses a logical interface
(similar to the loopback interface of a router) as its communication address and both the
master/slave interfaces of the SGW/MME can receive packets.
– Deploy private network IGP (either OSPF or IS-IS) between MASGs.
– Configure a static route from MASG1 and MASG2 to the logical address of an SGW/
MME respectively. The two static routes have the same priority.
– Import the static routes to private network IGP for advertisement. Advertise the static
routes and private network IGP routes to BGP.
– Ensure that an SGW/MME can receive packets from both master and slave physical
interfaces. Otherwise, packet loss is serious in the case of a protection switchback.
Deploy one protection mode according to the actual networking.
8.1.6.1 Configuring VRRP Protection

This section describes how to configure VRRP protection for master and slave MASGs to
provide dual-homing protection for an EPC.
Figure 8-5 Topology of VRRP protection
Core Vlanif 100

MBB Core
192.168.2.1/30
ASBR3 MASG1 Primary/backup
Interface address
192.168.2.101/30
00
n1
Vla Loopback0
192.168.2.100
12.12.12.1/32
virtual-ip
IPRAN
Vla SGW
n1 /MME
00
ASBR4 MASG2
Vlanif 100
192.168.2.2/30

NOTE
This section uses the VRRP group between one pair of devices at the core layer as an example. VRRP groups
can be configured in the same way for other devices at the core layer that require the protection.

Configure VRRP on MASG1.
1. Create a VLAN.
vlan 100//Creates VLAN 100.
2. Configure a VLAN Trunk between the master and slave MASGs.

interface Eth-Trunk 1
portswitch//Configures port switching.
undo shutdown
port link-type trunk//Sets the interface to be a Trunk interface.
port trunk allow-pass vlan 100//Sets the Trunk interface to allow packets from
VLAN 100.
3. Configure a VLAN Trunk between the master MASG and the BSC.
negotiation auto //Sets a GE interface connected to wireless equipment to work
in auto-negotiation mode (recommended).
portswitch
port-tx-enabling-delay 300000 //Sets the delay of switchback. This command
must be run. If the SGW/MME does not support the delay of switchback, or if
this command is not run, services will fail to be forwarded because of a
restart of the master MASG.
undo shutdown
port link-type trunk//Configures the link type consistently at both ends. The
trunk type is used in this example.
port trunk allow-pass vlan 100
4. Checks whether DCN is enabled for the interface.

If DCN is enabled globally on the device, query whether DCN is enabled on the interface
connected to the RNC. If yes, disable DCN for the interface by performing the following
operations:
undo dcn //Disable DCN.
5. Configure a VPN instance.

ipv4-family
tnl-policy IPRAN
6. Configure VRRP on a VLANIF interface.
interface Vlanif 100//Creates a VLANIF interface.

ip binding vpn-instance LTE-RAN//Binds a service interface to the VPN
instance.
ip address 192.168.2.1 255.255.255.0//Configures an IP address to the VLANIF
interface.
vrrp vrid 100 virtual-ip 192.168.2.100//Creates a VRRP backup group and
configures a virtual IP address as the MBB core-to-NodeB/eNodeB gateway IP
address.
vrrp vrid 100 priority 120//Set the priority of the NE to 120 in the VRRP
backup group to allow the NE to become the master device.

vrrp vrid 100 preempt-mode timer delay 180//Sets the preempt-mode delay on the
router in a VRRP backup group to 180s.
7. Configure BFD.
l Configure BFD for VRRP.
bfd vrrp bind peer-ip 192.168.2.2 vpn-instance LTE-RAN interface Vlanif100
source-ip 192.168.2.1
min-tx-interval 50
min-rx-interval 50
commit
8. Set the VRRP recovery delay.

vrrp recover-delay 60//Sets the delay time for restoring the status of a VRRP
backup group to 60 seconds in global mode.
9. If an EPC uses a logical IP address, configure a static route destined to the logical IP address.
If the EPC does not use a logical IP address, configure a static route destined to the IP
address of a port on the EPC.
ip route-static vpn-instance LTE-RAN 12.12.12.1 32 192.168.2.101 preference 5
description TO EPC
//A VPN instance must be
configured before the destination IP address. Otherwise, the importing will
fail.
//12.12.12.1 is the logical
IP address of the EPC. 192.168.2.101 is the IP address the EPC uses to directly
connect to the backhaul network.
NOTE
If there are multiple pairs of interconnected devices at the core layer, configure mutiple static routes as
required.
The importing of directly-connected routes and static routes is used as an example. In actual
scenarios, routing protocols can be imported as required.
l The configuration is as follows if the non-load sharing mode is used:
ip ip-prefix EPC-Master index 10 permit 12.12.12.0 24 greater-equal 24 less-
equal 32 //12.12.12.1 is the logical IP address of EPC1. The IP addresses
of interfaces on the EPCs can also be used as the routing prefix table.
equal 32 //12.12.13.1 is the logical IP address of EPC2.
route-policy EPC permit node 10
if-match ip-prefix EPC-Master
apply cost 103
apply community 1000:1 additive //Defines the community attribute of routes
on the EPC side.
apply preferred-value 32768 //Sets the MED to 103 for routes imported from
the EPC side and sets the local priority to 32768.
#
bgp 100
import-route direct route-policy EPC
import-route static route-policy EPC
l The configuration is as follows if the load sharing mode is used:

ip ip-prefix EPC-Slave index 10 permit 12.12.13.0 24 greater-equal 24 less-

apply cost 103

on the EPC side.
#
if-match ip-prefix EPC-Slave
apply cost 203
#
bgp 200

1. Create a VLAN.
vlan 100.

portswitch
undo shutdown
port link-type trunk
3. Configure a VLAN Trunk between the slave MASG and the BSC.
negotiation auto
portswitch
port-tx-enabling-delay 300000
undo shutdown
4. (Optional) Disable DCN for a service interface.

If DCN is enabled networkwide, check whether DCN is enabled for the interface connected
to the BSC. If yes, disable DCN for the interface.
l Run the display this command on the interface to check whether DCN is enabled.
display this
l If yes, disable DCN for the interface.

undo dcn

ipv4-family
tnl-policy IPRAN

interface Vlanif100//Creates a VLANIF interface.

ip address 192.168.2.2 255.255.255.0

7. Configure BFD.
source-ip 192.168.2.2
min-tx-interval 50
min-rx-interval 50
commit
8. Configure VRRP on the slave MASG to track the status of the BFD session. If the BFD
session detects a fault and goes Down, the VRRP group is notified of the status change and
changes VRRP priorities of devices. In this manner, a fast VRRP switchover is
implemented.
interface Vlanif100
vrrp vrid 100 track bfd-session 300 increased 40//Configures the VBRRP to
track the status of BFD sessions, to implement fast switchover between the
master router and the slave router.

description TO EPC //The preference value is the same as that of the master
MASG, to prevent VPN FRR flapping on ASGs because of an AC-side fault of the
MASG.
11. Configure route importing to a VPN instance and VPN auto FRR.
equal 32
equal 32
apply cost 203
#
bgp 100

equal 32
equal 32
apply cost 203

#
apply cost 103
#
bgp 200

Query the VRRP status of the MASGs. MASG1's VRRP status is Master, MASG2's VRRP
status is Backup, and the BFD session is Up.
1. <MASG1> display vrrp 100

Vlanif100 | Virtual Router 100
State : Master
Virtual IP : 192.168.2.100
Master IP : 192.168.2.1
PriorityRun : 120
PriorityConfig : 120
MasterPriority : 120
Preempt : YES Delay Time : 180
TimerRun : 1 s
TimerConfig : 1 s
Auth Type : NONE
Virtual Mac : 0000-5e00-0164
Check TTL : YES
Config type : normal-vrrp
Create time : 2012-05-13 22:41:29
Last change time : 2012-05-14 03:41:32

State : Backup
Virtual IP : 192.168.2.100
Master IP : 192.168.2.1
PriorityRun : 100
TimerRun : 1 s
TimerConfig : 1 s
Auth Type : NONE
Virtual Mac : 0000-5e00-0164
Check TTL : YES
Config track link-bfd down-number : 0
Track BFD : 300 Priority increased : 40
BFD-session state : UP
Create time : 2012-05-18 15:35:48
Last change time : 2012-05-18 20:34:30
3. Run the <MASG1> display bfd session peer-ip 192.168.2.2 vpn-instance LTE-RAN
command. The result shows that the BFD session status is UP.
------------------------------------------------------------------------------
--
------------------------------------------------------------------------------
--
300 300 192.168.2.2 Up S_IP_IF Vlanif100

------------------------------------------------------------------------------
--
4. Run the display bgp vpnv4 vpn-instance LTE-RAN routing-table command. The ASG
performs display bgp vpnv4 all routing-table. The result shows that the MED values used
for BGP route advertisement can distinguish active and standby routes.
[CSG1]display bgp vpnv4 vpn-instance LTE-RAN routing-
table
BGP Local router ID is 1.1.1.1

Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
VPN-Instance LTE-RAN, Router ID 1.1.1.1:
Total Number of Routes: 6

Network NextHop MED LocPrf PrefVal Path/Ogn
*> 192.168.1.0 0.0.0.0 0 0 ?

*> 192.168.1.1/32 0.0.0.0 0 0 ?
*>i 192.168.2.0 3.3.3.3 103 100 0 200?
* i 4.4.4.4 203 100 0 200?
*>i 192.168.2.100/32 3.3.3.3 103 100 0 200?
* i 4.4.4.4 203 100 0
200?
[ASG3]display bgp vpnv4 all routing-table

Total number of routes from all PE: 6

Route Distinguisher: 100:100
*>i 192.168.1.0 1.1.1.1 103 100 10 ?

* i 4.4.4.4 203 100 0 ?
*>i 192.168.2.0 9.9.9.9 100 0 200?
* i 10.10.10.10 100 0 200?
*>i 192.168.2.100/32 9.9.9.9 100 0 200?
* i 9.9.9.9 100 0 200?

*>i 192.168.1.0 1.1.1.1 103 100 10 ?

* i 4.4.4.4 203 100 0 ?
*>i 192.168.2.0 9.9.9.9 100 0 200?
* i 10.10.10.10 100 0 200?
*>i 192.168.2.100/32 9.9.9.9 100 0 200?
* i 9.9.9.9 100 0 200?
[MASG1]display bgp vpnv4 vpn-instance LTE-RAN routing-table



*>i 192.168.1.0 3.3.3.3 103 100 0 100?

* i 4.4.4.4 203 100 0 100?
*> 192.168.2.0 0.0.0.0 103 32768 ?
* i 10.10.10.10 203 100 0 ?
*> 192.168.2.1/32 0.0.0.0 103 32768 ?
*> 192.168.2.2/32 0.0.0.0 103 32768 ?
*> 192.168.2.7/32 0.0.0.0 103 32768 ?
*> 192.168.2.100/32 0.0.0.0 103 32768 ?
5. Run the ping -vpn-instance command on a PE to ping the remote PE.

[CSG1]ping -vpn-instance LTE-RAN 192.168.2.100
PING 192.168.2.100: 56 data bytes, press CTRL_C to
break
Reply from 192.168.2.100: bytes=56 Sequence=1 ttl=253 time=1
ms
ms
ms
ms
ms
--- 192.168.2.100 ping statistics

---
5 packet(s)
transmitted
5 packet(s)
received
0.00% packet
loss
round-trip min/avg/max = 1/1/1 ms
[MASG1]ping -vpn-instance LTE-RAN 192.168.1.1
break
ms
ms
ms
ms
ms

---
5 packet(s)
transmitted
5 packet(s)
received
0.00% packet
loss

NOTE
When a PE has multiple interfaces bound to the same VPN instance, specify the source IP address
in the ping -vpn-instance command to ping the remote PE. Otherwise, the ping may fail.
6. Run the display ip vpn-instance verbose command to check VPN instance configurations.
7. Run the display ip routing-table vpn-instance XXX command to view the routing table
of the VPN instance.
[CSG1]display ip routing-table vpn-instance LTE-
RAN
------------------------------------------------------------------------------
Routing Tables: LTE-RAN
192.168.1.0/24 Direct 0 0 D 192.168.1.1
192.168.1.1/32 Direct 0 0 D 127.0.0.1
192.168.1.255/32 Direct 0 0 D 127.0.0.1
192.168.2.0/24 IBGP 255 103 RD 3.3.3.3 Tunnel0/0/13
192.168.2.100/32 IBGP 255 103 RD 3.3.3.3 Tunnel0/0/13
[MASG1]display ip routing-table vpn-instance LTE-RAN
------------------------------------------------------------------------------
192.168.1.0/24 IBGP 255 103 RD 3.3.3.3 Tunnel0/0/97
192.168.2.0/24 Direct 0 0 D 192.168.2.1 Vlanif100
192.168.2.1/32 Direct 0 0 D 127.0.0.1 Vlanif100
192.168.2.2/32 Direct 0 0 D 192.168.2.2 Vlanif100
192.168.2.7/32 Direct 0 0 D 192.168.2.7 Vlanif100
192.168.2.100/32 Direct 0 0 D 127.0.0.1 Vlanif100
192.168.2.255/32 Direct 0 0 D 127.0.0.1 Vlanif100
8. Run the display bgp vpnv4 vpn-instance LTE-RAN routing-table community 1000:1
command on the MASGs to query advertisement of community attributes of routes on the
EPC side.
[MASG1]display bgp vpnv4 vpn-instance LTE-RAN routing-table community
1000:1


Network NextHop MED LocPrf PrefVal Community
*> 192.168.2.0 0.0.0.0 103 32768

<1000:1>
* i 10.10.10.10 203 100 0 <1000:1>
*> 192.168.2.1/32 0.0.0.0 103 32768 <1000:1>
*> 192.168.2.2/32 0.0.0.0 103 32768 <1000:1>
*> 192.168.2.7/32 0.0.0.0 103 32768
<1000:1>
*> 192.168.2.100/32 0.0.0.0 103 32768
<1000:1>

9. Run the display ip routing-table vpn-instance vpn-instance-name ip-address verbose

command to check whether the tunnels and MED values configured for the VPN instance
are correct.
[CSG1]display ip routing-table vpn-instance LTE-RAN 192.168.2.0 verbose
------------------------------------------------------------------------------
Routing Table : LTE-RAN

Summary Count : 1
IndirectID: 0x24
RelayNextHop: 0.0.0.0 Interface: Tunnel0/0/13
TunnelID: 0x1 Flags: RD
BkNextHop: 4.4.4.4 BkInterface: Tunnel0/0/14
kPETunnelID: 0x2 BkPESecTunnelID: 0x0
BkIndirectID: 0x21
8.1.6.2 Configuring Active and Standby Routes for Protection

If the master and slave interfaces have been planned for an EPC that supports dual-receiving on
the interfaces, you can configure active and standby static routes to ensure that the master/slave
MASG relationship is consistent with that on the EPC side. This guarantees millisecond-level
fault detection and protection when the master MASG or the AC link on the master MASG is
not functioning properly. In this case, the EPC uses the IP address of a logical interface as the
destination address. Static routes advertised by the master and slave interfaces of the EPC have
different priorities.
Figure 8-6 Configuring active and standby routes

NOTICE
Unlike VRRP configuration, when you configure active and standby routes, VPN instances are
imported through physical interfaces rather than VLANIF interfaces.
Configuring the Master RSG

ipv4-family
tnl-policy IPRAN
2. Bind service interfaces to the VPN instance.

interface gigabitethernet 1/1/2//Binds the L3VPN to the physical interface
connected to the EPC.
port-tx-enabling-delay 300000//Sets the delay of switchback. This command
must be run. If the EPC does not support the delay of switchback, or if this
command is not run, services will fail to be forwarded because of a restart of
the master MASG.
description to EPC
undo shutdown
ip address 192.168.2.1 30
3. Configure private network IGP.

In this section, IS-IS is used as an example.
isis 2 vpn-instance LTE-RAN
is-level level-2
cost-style wide
flash-flood level-2
network-entity 49.0003.0090.0900.9009.00
is-name MASG1
import-route static
timer spf 1 50 50
log-peer-change
4. Bind sub-interfaces between MASGs to the VPN instance and enable private network IGP.
vlan-type dot1q 5
description to MASG2
undo shutdown
ip address 192.168.2.9 30
isis enable 2
5. Configure BFD for IP to speed up service switching between the MASG and EPC.
bfd master-route bind peer-ip 192.168.2.2 vpn-instance LTE-RAN interface
GigabitEthernet 1/1/2 source-ip 192.168.2.1
//192.168.2.2 is the IP addresses
EPC1 uses to directly connect to MASG1.
commit

6. Configure static routes if the EPC or RNC uses a logical IP address.

track bfd-session master-route description TO EPC1
//A VPN instance must be configured
before the destination IP address. Otherwise, BGP cannot be imported.
//12.12.12.1 is the logical IP
address of EPC1.

apply cost 103
on the EPC side.
#
bgp 200
import-route isis 2 route-policy EPC

apply cost 103
on the EPC side.
#
apply cost 203
#
bgp 200

ipv4-family
tnl-policy IPRAN



interface gigabitethernet 1/1/2
negotiation auto
description to EPC
undo shutdown
ip address 192.168.2.5 30

is-level level-2
cost-style wide
flash-flood level-2
network-entity 49.0003.0100.1001.0010.00
is-name MASG2
import-route static
timer spf 1 50 50
log-peer-change
bfd slave-route bind peer-ip 192.168.2.6 vpn-instance LTE-RAN interface
commit
vlan-type dot1q 5
undo shutdown
ip address 192.168.2.10 30
isis enable 2
6. Configure a static route.

description TO EPC1
//The preference value is the
same as that of the master MASG, to prevent VPN FRR flapping on ASGs because
of an AC-side fault of the MASG.

equal 32
equal 32
apply cost 203
#
bgp 200



equal 32
equal 32
apply cost 203
#
apply cost 103
#
bgp 200
Configuring the EPC

The master/slave relationship on the EPC side is distinguished by priorities of static routes. For
details, see the related manual for EPCs.
8.1.7 Configuring Protection Switching (at the VPN Layer)

This section describes how to configure protection for mobile backhaul services.
Configuring CSGs
1. Configure VPN FRR.

Configure a routing policy for VPN FRR.
route-policy nms-vpn-frr permit node 10//Deploys a routing policy for the VPN
FRR.
apply backup-nexthop auto//Sets the slave next hop in the VPN to auto.
Deploy VPN FRR.

vpn frr route-policy nms-vpn-frr//Deploys VPN FRR.
NOTE
Deploy BFD for TE to speed up VPN FRR. For details about the configuration, see the chapter about
MPLS.
Configuring MASGs


route-policy nms-vpn-frr permit node 10//Deploying a routing policy for the VPN
FRR.
Deploy VPN FRR.

NOTE
Deploy BFD for BGP Tunnel to speed up VPN FRR. For details about the configuration, see the
section about configuring MPLS tunnels (BGP LSPs).

l Run the display ip routing-table vpn-instance vpn-instance-name ip-address verbose
command on a CSG or MASG, to query the standby next hop, the standby label, and the
standby tunnel ID.
<CSG1> display ip routing-table vpn-instance LTE-RAN 192.168.2.0 verbose

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

Summary Count : 1
IndirectID: 0x12
BkPETunnelID: 0x2 BkPESecTunnelID: 0x0
BkIndirectID: 0xf
8.2 Deploying E2E Mobile Backhaul Services (Labeled BGP

to Edge)
This section describes how to deploy E2E mobile backhaul services in the Labeled BGP to Edge
sub-solution.
8.2.1 E2E Ethernet Service Deployment Solution

This section describes the roadmap for configuring inter-AS Ethernet service bearer and
protection.


LTE S1 service
L3VPN
RR1 RR3

RR4
RR2
VPNv4
In the Labeled BGP to Edge sub-solution, the roadmap for configuring Ethernet service bearer
and protection is as follows:
1. Deploy MP-iBGP. Configure neighbor relationship in the VPNv4 address family view.
In AS 100
l Set up full-mesh MP-iBGP peer relationship between ASGs and the master and slave
RRs (RR1 and RR2).
l During route reflection, no node changes the next hop of routes.
In AS 200
RRs (RR3 and RR4).
2. Deploy MP-eBGP.
l Set up MP-eBGP peer relationship between the master RR (RR1) in AS 100 and the
master RR (RR3) in AS 200 (not directly connected).
l Set up MP-eBGP peer relationship between the slave RR (RR2) in AS 100 and the slave
RR (RR4) in AS 200 (not directly connected).
3. Configure VPN services.
l Configure a VPN instance for CSGs and MASGs.
4. Configure protection switching.
l Enable BGP FRR on CSGs, MASGs, ASBRs, and ASGs.
l Configure VPN FRR on MASGs and CSGs.
5. Two MASG dual-homing protection methods are available: configuring VRRP and
configuring active and standby routes. Configuring VRRP is recommended.

l Configure VRRP.
To protect the links between MASGs and the MBB core (base station controller side),
configure VRRP over VLANIF between the master and slave MASGs.
a. Configure the interfaces that connect the master and slave MASGs and the
interfaces that connect to the RNC to be Layer 2 switch interfaces, and add these
interfaces to a VLAN.
b. Create a VLANIF interface on the master and slave MASGs and configure VRRP.
c. Deploy BFD between the master and slave MASGs, to detect Layer 2
interconnection links and peer-end private network addresses, and to enable faster
protection switching.
d. Configure the hold-off time of VRRP switchback for the master MASG.
l Deploy active and standby routes.
If an SGW/MME uses its logical interface (similar to the loopback interface of a router)
for communication and must support dual-receiving through master and standby
interfaces, it can support interconnection using active and standby routes.
– In this mode, configure static routes with the same priority from the master and slave
MASGs to SGW/MME, and configure static routes to be advertised to private
network IGP instances. For example, you can set the preference in static routes to
5.
– Enable the private network IGP on the subinterfaces of the interconnected interfaces
between the master and slave MASGs. Configure private network static routes and
IGP routes to be advertised to BGP.
l Advertisement of a private network route from a CSG to an MASG
103 RR1 RR3

103
103 103
10
3->
203
50
203
3
203

203
203
RR4
RR2
A private network route from an eNodeB is dually homed to the master and slave ASGs.
The MED value is set to 103 by the master ASG and to 203 by the slave ASG. The
master ASG sends the route to the master RR without modifying the MED value, and
to the slave RR after modifying the MED value from 103 to 503. The slave ASG sends
the route to the master and slave RRs without modifying the MED values. In this case,
the master RR prefers the route from the master ASG, and the slave RR prefers the route

from the slave ASG. The master and slave RRs at the aggregation layer advertise the
routes to the core layer based on the eBGP neighbor relationship. When the core layer
RRs forward the routes to the MASGs, an export policy is configured for the RRs or an
import policy is configured for the MASGs, so that the MASGs can select a route
according to the MED values.
l Advertisement of a private network route from an MASG to a CSG
RR1 RR3
103
103
3
50
103 103
20
3
203
203

203
203
RR4
RR2

The roadmap for configuring E2E Ethernet service bearer and protection is as follows:
Figure 8-10 Configuration flowchart
8.2.3 Data Planning

This section provides the data plan for L3VPN deployment.

NOTE
NE Role Value Remarks
CSG1 interface Ethernet0/3/0.10: -

192.168.1.1/24

192.168.2.1/24

192.168.2.2/24
Table 8-6 MPLS VPN parameters
VPN instance name LTE-RAN -
RD value CSG1: 100:100 In this solution, it is

MASG1: 100:100 recommended that you
configure RDs for all devices
MASG2: 100:100 on the mobile backhaul
network to be the same.
RT CSG: Export RT 100:1, "100:1" indicates network-

Import RT 200:1 wide routes, and "200:1"
MASG: Export RT 200:1 indicates routes for E2E
100:1, Import RT 100:1 mobile backhaul services
originated from MASGs.
Label allocation mode apply-label per-instance Enables one VPN route label
to be allocated for each VPN.
BGP process 100 100 100 100 100

ID
router-id 1.1.1.1 3.3.3.3 4.4.4.4 11.11.11.11 12.12.12.12
iBGP peer - CSG: 1.1.1.1 CSG: - -

(VPNv4 1.1.1.1
address
family)

iBGP peer ASG3: RR1: RR1: ASG3: ASG3:

(VPNv4 3.3.3.3 11.11.11.11 11.11.11.11 3.3.3.3 3.3.3.3
address ASG4: RR2: RR2: ASG4: ASG4:
family) 4.4.4.4 12.12.12.12 12.12.12.12 4.4.4.4 4.4.4.4
eBGP peer - - - RR3: RR4:

(VPNv4 13.13.13.13 14.14.14.14
address
family)
vpn-target Enabled Disabled Disabled Disabled Disabled
Setting the - - - - -
next hop to the
local IP
address
Parameter RR3 RR4 MASG1 MASG2
BGP process ID 200 200 200 200
router-id 13.13.13.13 14.14.14.14 9.9.9.9 10.10.10.10
iBGP peer (VPNv4 MASG1: MASG1: RR3: RR3:

address family) 9.9.9.9 9.9.9.9 13.13.13.13 13.13.13.13
MASG2: MASG2: RR4: RR4:
10.10.10.10 10.10.10.10 14.14.14.14 14.14.14.14
eBGP peer (VPNv4 RR1:11.11.11 RR2:12.12.12 - -

address family) .11 .12
vpn-target Disabled Disabled Enabled Enabled
Setting the next hop to the - - - -

local IP address
8.2.4 Configuring MP-BGP

This section describes how to configure MP-BGP.
Configuring CSGs
In the Labeled BGP to Edge sub-solution, the basic BGP configuration (such as router IDs and
the unicast address family) for CSGs have been completed during MPLS tunnel deployment.
The following uses CSG1 as an example to describe how to configure MP-BGP for a CSG.

l Configure MP-BGP.
#
bgp100
#
peer 3.3.3.3 tracking delay 30 //Enables BGP Peer Tracking, to implement FRR
on a network by enabling an NE to quickly detect a fault on a neighbor.
#
ipv4-family vpnv4
policy vpn-target
peer 3.3.3.3 enable
peer 4.4.4.4 enable
#
import-route direct
#


#
ip community-filter basic csg-vpn permit 11:11 //Defines the community
attribute table for identifying CSG-side private network VPNv4
routes.
#
route-policy to-csg-as-master permit node 10
apply cost 103
#
100
apply cost
103
#
route-policy from-csg-as-master permit node 10 //Configures the receiving of
routes from CSGs. If ASG3 is the master ASG of the CSGs, the MED value is set
to 103.
apply cost 103
#
route-policy vpnv4-to-MRR deny node 10
if-match community-filter default
#
if-match community-filter csg-
vpn
#
route-policy vpnv4-to-SRR deny node 10
#
15
if-match community-filter csg-vpn
#

#
l Configure MP-BGP.
#
bgp 100
#
peer CSG timer connect-retry 300 //Sets the connect-retry time to set up BGP
neighbor relationship with a CSG.
#
ipv4-family vpnv4
peer CSG enable
peer 1.1.1.1 enable
#


#
ip community-filter basic csg-vpn permit 11:11
#
apply cost 203
#
apply cost 203
#
apply cost 203
#
#
if-match community-filter csg-
vpn
#
#
15

#
10
#
#
l Configure MP-BGP.
#
bgp 100
#
#
ipv4-family vpnv4
peer CSG enable
peer 1.1.1.1 enable
#











8.2.5 Configuring an L3VPN

VPN instances must be configured to advertise VPNv4 routes and forward data to deploy an
inter-AS L3VPN.
Configuring CSGs
Configuring a CSG as follows:
1. Configure VPN instances.

Create VPN instances based on service types.
ip vpn-instance LTE-RAN//Creates a VPN instance.
ipv4-family
only after being configured with an RD. The RD value must be same as the one
on the MASG. If RDs are different, VPN FRR does not take effect.
tnl-policy IPRAN//Configures a TE tunnel as the tunnel for the VPN
instance.
apply-label per-instance//Enables one VPN route label to be allocated for
each VPN.
vpn-target 200:1 import-extcommunity #
2. Bind VPN instances with specific service interfaces.

#
vlan-type dot1q 10
ip address ip address 192.168.1.1 255.255.255.0
#
NOTE
If DCN is enabled networkwide, check whether DCN is enabled for the interface connected to the BSC.
If yes, disable the DCN function. The configurations are as follows:
undo dcn

3. If the eNodeB uses a logical IP address, configure a static route destined to the logical IP
address on the CSG and import the static route to the related VPN instance.
ip route-static vpn-instance LTE-RAN 120.16.1.2 255.255.255.255 192.168.1.2 //
A VPN instance must be configured before the destination IP address. Otherwise,
BGP cannot be imported.
//120.16.1.2 is the logical IP address
of the eNodeB. 192.168.1.2 is the IP address of the eNodeB connected to the
backhaul network.

bgp 100
import-route direct
import-route static
Configuring MASGs
The configuration of L3VPN services for an MASG is correlated with the protection mode. For
details, see Deploying Bearer and Protection for Services Between MASGs and SGWs/
MMEs.
8.2.6 Deploying Bearer and Protection for Services Between

MASGs and SGWs/MMEs
This topic describes how to deploy bearer and protection for services between MASGs and
SGWs/MMEs. Service configurations are correlative to the protection mode.
Protection mode for services between MASGs and SGWs/MMEs:
l The VRRP+VLANIF mode is used for protection.

This mode applies to the scenario in which an EPC exchanges (transmits and receives)
packets with MASGs only through one interface but provides two interfaces that work in
master/slave mode for ensuring connection between the SGW/MME and MASGs. The
master and slave interfaces share a common IP address but have different MAC addresses.
– Deploy VRRP on VLANIF interfaces of MASGs, and configure each SGW/MME to
be dual-homed to the MASGs.
– Configure the interfaces that connect an SGW/MME to the master and slave MASGs
to work in master/slave mode and configure the virtual IP address of the VRRP group
as the default gateway IP address. Of the two interfaces, only one interface can receive
packets.
l Active/Standby static routes are configured for protection.
This protection mode applies to the scenario in which an SGW/MME uses a logical interface
(similar to the loopback interface of a router) as its communication address and both the
master/slave interfaces of the SGW/MME can receive packets.
– Deploy private network IGP (either OSPF or IS-IS) between MASGs.
– Configure a static route from MASG1 and MASG2 to the logical address of an SGW/
MME respectively. The two static routes have the same priority.
– Import the static routes to private network IGP for advertisement. Advertise the static
routes and private network IGP routes to BGP.
– Ensure that an SGW/MME can receive packets from both master and slave physical
interfaces. Otherwise, packet loss is serious in the case of a protection switchback.

Deploy one protection mode according to the actual networking.
8.2.6.1 Configuring VRRP Protection

This section describes how to configure VRRP protection for master and slave MASGs to
provide dual-homing protection for an EPC.
Figure 8-11 Topology of VRRP protection
Core Vlanif 100

MBB Core
192.168.2.1/30
ASBR3 MASG1 Primary/backup
Interface address
192.168.2.101/30
00
n1
Vla Loopback0
192.168.2.100
12.12.12.1/32
virtual-ip
IPRAN
Vla SGW
n1 /MME
00
ASBR4 MASG2
Vlanif 100
192.168.2.2/30
NOTE
This section uses the VRRP group between one pair of devices at the core layer as an example. VRRP groups
can be configured in the same way for other devices at the core layer that require the protection.

1. Create a VLAN.
vlan 100//Creates VLAN 100.

portswitch//Configures port switching.
undo shutdown
port link-type trunk//Sets the interface to be a Trunk interface.
port trunk allow-pass vlan 100//Sets the Trunk interface to allow packets from
VLAN 100.
3. Configure a VLAN Trunk between the master MASG and the BSC.
portswitch
port-tx-enabling-delay 300000 //Sets the delay of switchback. This command
must be run. If the SGW/MME does not support the delay of switchback, or if
this command is not run, services will fail to be forwarded because of a
restart of the master MASG.
undo shutdown

port link-type trunk//Configures the link type consistently at both ends. The
trunk type is used in this example.
4. Checks whether DCN is enabled for the interface.

If DCN is enabled globally on the device, query whether DCN is enabled on the interface
connected to the RNC. If yes, disable DCN for the interface by performing the following
operations:
undo dcn //Disable DCN.

ipv4-family
tnl-policy IPRAN
interface Vlanif 100//Creates a VLANIF interface.

ip binding vpn-instance LTE-RAN//Binds a service interface to the VPN
instance.
ip address 192.168.2.1 255.255.255.0//Configures an IP address to the VLANIF
interface.
vrrp vrid 100 virtual-ip 192.168.2.100//Creates a VRRP backup group and
configures a virtual IP address as the MBB core-to-NodeB/eNodeB gateway IP
address.
vrrp vrid 100 priority 120//Set the priority of the NE to 120 in the VRRP
backup group to allow the NE to become the master device.
vrrp vrid 100 preempt-mode timer delay 180//Sets the preempt-mode delay on the
router in a VRRP backup group to 180s.
7. Configure BFD.
source-ip 192.168.2.1
min-tx-interval 50
min-rx-interval 50
commit

description TO EPC
//A VPN instance must be
configured before the destination IP address. Otherwise, the importing will
fail.
//12.12.12.1 is the logical
IP address of the EPC. 192.168.2.101 is the IP address the EPC uses to directly
connect to the backhaul network.

NOTE
If there are multiple pairs of interconnected devices at the core layer, configure mutiple static routes as
required.
apply cost 103
on the EPC side.
#
bgp 100

apply cost 103
on the EPC side.
#
apply cost 203
#
bgp 200

1. Create a VLAN.
vlan 100.

portswitch
undo shutdown


3. Configure a VLAN Trunk between the slave MASG and the BSC.
negotiation auto
portswitch
undo shutdown
4. (Optional) Disable DCN for a service interface.

If DCN is enabled networkwide, check whether DCN is enabled for the interface connected
to the BSC. If yes, disable DCN for the interface.
l Run the display this command on the interface to check whether DCN is enabled.
display this
l If yes, disable DCN for the interface.

undo dcn

ipv4-family
tnl-policy IPRAN

interface Vlanif100//Creates a VLANIF interface.
ip address 192.168.2.2 255.255.255.0
7. Configure BFD.
source-ip 192.168.2.2
min-tx-interval 50
min-rx-interval 50
commit
8. Configure VRRP on the slave MASG to track the status of the BFD session. If the BFD
session detects a fault and goes Down, the VRRP group is notified of the status change and
changes VRRP priorities of devices. In this manner, a fast VRRP switchover is
implemented.
interface Vlanif100
vrrp vrid 100 track bfd-session 300 increased 40//Configures the VBRRP to
track the status of BFD sessions, to implement fast switchover between the
master router and the slave router.



description TO EPC //The preference value is the same as that of the master
MASG, to prevent VPN FRR flapping on ASGs because of an AC-side fault of the
MASG.
11. Configure route importing to a VPN instance and VPN auto FRR.
equal 32
equal 32
apply cost 203
#
bgp 100

equal 32
equal 32
apply cost 203
#
apply cost 103
#
bgp 200

Query the VRRP status of the MASGs. MASG1's VRRP status is Master, MASG2's VRRP
status is Backup, and the BFD session is Up.

State : Master
Virtual IP : 192.168.2.100
Master IP : 192.168.2.1
PriorityRun : 120
TimerRun : 1 s
TimerConfig : 1 s

Auth Type : NONE

Virtual Mac : 0000-5e00-0164
Check TTL : YES
Create time : 2012-05-13 22:41:29
Last change time : 2012-05-14 03:41:32

State : Backup
Virtual IP : 192.168.2.100
Master IP : 192.168.2.1
PriorityRun : 100
TimerRun : 1 s
TimerConfig : 1 s
Auth Type : NONE
Virtual Mac : 0000-5e00-0164
Check TTL : YES
Config track link-bfd down-number : 0
Track BFD : 300 Priority increased : 40
BFD-session state : UP
Create time : 2012-05-18 15:35:48
Last change time : 2012-05-18 20:34:30
3. Run the <MASG1> display bfd session peer-ip 192.168.2.2 vpn-instance LTE-RAN
command. The result shows that the BFD session status is UP.
------------------------------------------------------------------------------
--
------------------------------------------------------------------------------
--
300 300 192.168.2.2 Up S_IP_IF Vlanif100
------------------------------------------------------------------------------
--
4. Run the display bgp vpnv4 vpn-instance LTE-RAN routing-table command. The ASG
performs display bgp vpnv4 all routing-table. The result shows that the MED values used
for BGP route advertisement can distinguish active and standby routes.
[CSG1]display bgp vpnv4 vpn-instance LTE-RAN routing-
table


*> 192.168.1.0 0.0.0.0 0 0 ?

*> 192.168.1.1/32 0.0.0.0 0 0 ?
*>i 192.168.2.0 9.9.9.9 103 100 0 200?
* i 10.10.10.10 203 100 0 200?
*>i 192.168.2.100/32 9.9.9.9 103 100 0 200?
* i 10.10.10.10 203 100 0
200?
[ASG3]display bgp vpnv4 all routing-table


Total number of routes from all PE: 6

Route Distinguisher: 100:100
*>i 192.168.1.0 1.1.1.1 103 100 10 ?

* i 4.4.4.4 203 100 0 ?
*>i 192.168.2.0 9.9.9.9 100 0 200?
* i 10.10.10.10 100 0 200?
*>i 192.168.2.100/32 9.9.9.9 100 0 200?
* i 9.9.9.9 100 0 200?

*>i 192.168.1.0 1.1.1.1 103 100 10 ?

* i 4.4.4.4 203 100 0 ?
*>i 192.168.2.0 9.9.9.9 100 0 200?
* i 10.10.10.10 100 0 200?
*>i 192.168.2.100/32 9.9.9.9 100 0 200?
* i 9.9.9.9 100 0 200?
[MASG1]display bgp vpnv4 vpn-instance LTE-RAN routing-table


*>i 192.168.1.0 3.3.3.3 103 100 0 100?

* i 4.4.4.4 203 100 0 100?
*> 192.168.2.0 0.0.0.0 103 32768 ?
* i 10.10.10.10 203 100 0 ?
*> 192.168.2.1/32 0.0.0.0 103 32768 ?
*> 192.168.2.2/32 0.0.0.0 103 32768 ?
*> 192.168.2.7/32 0.0.0.0 103 32768 ?
*> 192.168.2.100/32 0.0.0.0 103 32768 ?
5. Run the ping -vpn-instance command on a PE to ping the remote PE.

[CSG1]ping -vpn-instance LTE-RAN 192.168.2.100
break
ms
ms
ms
ms


ms

---
5 packet(s)
transmitted
5 packet(s)
received
0.00% packet
loss
[MASG1]ping -vpn-instance LTE-RAN 192.168.1.1
break
ms
ms
ms
ms
ms

---
5 packet(s)
transmitted
5 packet(s)
received
0.00% packet
loss
NOTE
When a PE has multiple interfaces bound to the same VPN instance, specify the source IP address
in the ping -vpn-instance command to ping the remote PE. Otherwise, the ping may fail.
6. Run the display ip vpn-instance verbose command to check VPN instance configurations.
7. Run the display ip routing-table vpn-instance XXX command to view the routing table
of the VPN instance.
[CSG1]display ip routing-table vpn-instance LTE-
RAN
------------------------------------------------------------------------------
192.168.1.0/24 Direct 0 0 D 192.168.1.1
192.168.1.1/32 Direct 0 0 D 127.0.0.1
192.168.1.255/32 Direct 0 0 D 127.0.0.1
192.168.2.0/24 IBGP 255 103 RD 3.3.3.3 Tunnel0/0/13
192.168.2.100/32 IBGP 255 103 RD 3.3.3.3 Tunnel0/0/13
[MASG1]display ip routing-table vpn-instance LTE-RAN
------------------------------------------------------------------------------
192.168.1.0/24 IBGP 255 103 RD 3.3.3.3 Tunnel0/0/97

192.168.2.0/24 Direct 0 0 D 192.168.2.1 Vlanif100

192.168.2.1/32 Direct 0 0 D 127.0.0.1 Vlanif100
192.168.2.2/32 Direct 0 0 D 192.168.2.2 Vlanif100
192.168.2.7/32 Direct 0 0 D 192.168.2.7 Vlanif100
192.168.2.100/32 Direct 0 0 D 127.0.0.1 Vlanif100
192.168.2.255/32 Direct 0 0 D 127.0.0.1 Vlanif100
command on the MASGs to query advertisement of community attributes of routes on the
EPC side.
[MASG1]display bgp vpnv4 vpn-instance LTE-RAN routing-table community
1000:1


Network NextHop MED LocPrf PrefVal Community
*> 192.168.2.0 0.0.0.0 103 32768

<1000:1>
* i 10.10.10.10 203 100 0 <1000:1>
*> 192.168.2.1/32 0.0.0.0 103 32768 <1000:1>
*> 192.168.2.2/32 0.0.0.0 103 32768 <1000:1>
*> 192.168.2.7/32 0.0.0.0 103 32768
<1000:1>
*> 192.168.2.100/32 0.0.0.0 103 32768
<1000:1>
9. Run the display ip routing-table vpn-instance vpn-instance-name ip-address verbose

command to check whether the tunnels and MED values configured for the VPN instance
are correct.
[CSG1]display ip routing-table vpn-instance LTE-RAN 192.168.2.0 verbose
------------------------------------------------------------------------------

Summary Count : 1
IndirectID: 0x24
kPETunnelID: 0x2 BkPESecTunnelID: 0x0
BkIndirectID: 0x21
8.2.6.2 Configuring Active and Standby Routes for Protection

If the master and slave interfaces have been planned for an EPC that supports dual-receiving on
the interfaces, you can configure active and standby static routes to ensure that the master/slave
MASG relationship is consistent with that on the EPC side. This guarantees millisecond-level
fault detection and protection when the master MASG or the AC link on the master MASG is

not functioning properly. In this case, the EPC uses the IP address of a logical interface as the
destination address. Static routes advertised by the master and slave interfaces of the EPC have
different priorities.
Figure 8-12 Configuring active and standby routes
NOTICE
Unlike VRRP configuration, when you configure active and standby routes, VPN instances are
imported through physical interfaces rather than VLANIF interfaces.
Configuring the Master RSG

ipv4-family
tnl-policy IPRAN

interface gigabitethernet 1/1/2//Binds the L3VPN to the physical interface
connected to the EPC.
port-tx-enabling-delay 300000//Sets the delay of switchback. This command
must be run. If the EPC does not support the delay of switchback, or if this
command is not run, services will fail to be forwarded because of a restart of
the master MASG.
description to EPC
undo shutdown
ip address 192.168.2.1 30


is-level level-2
cost-style wide
flash-flood level-2
network-entity 49.0003.0090.0900.9009.00
is-name MASG1
import-route static
timer spf 1 50 50
log-peer-change
vlan-type dot1q 5
undo shutdown
ip address 192.168.2.9 30
isis enable 2
bfd master-route bind peer-ip 192.168.2.2 vpn-instance LTE-RAN interface
commit
6. Configure static routes if the EPC or RNC uses a logical IP address.

track bfd-session master-route description TO EPC1
//A VPN instance must be configured
before the destination IP address. Otherwise, BGP cannot be imported.
//12.12.12.1 is the logical IP
address of EPC1.

apply cost 103
on the EPC side.
#
bgp 200



apply cost 103
on the EPC side.
#
apply cost 203
#
bgp 200

ipv4-family
tnl-policy IPRAN

interface gigabitethernet 1/1/2
negotiation auto
description to EPC
undo shutdown
ip address 192.168.2.5 30

is-level level-2
cost-style wide
flash-flood level-2
network-entity 49.0003.0100.1001.0010.00
is-name MASG2
import-route static
timer spf 1 50 50
log-peer-change
bfd slave-route bind peer-ip 192.168.2.6 vpn-instance LTE-RAN interface
commit

vlan-type dot1q 5
undo shutdown
ip address 192.168.2.10 30
isis enable 2
6. Configure a static route.

description TO EPC1
//The preference value is the
same as that of the master MASG, to prevent VPN FRR flapping on ASGs because
of an AC-side fault of the MASG.

equal 32
equal 32
apply cost 203
#
bgp 200

equal 32
equal 32
apply cost 203
#
apply cost 103
#
bgp 200
Configuring the EPC

The master/slave relationship on the EPC side is distinguished by priorities of static routes. For
details, see the related manual for EPCs.

8.2.7 Configuring Protection Switching (at the VPN Layer)

This section describes how to configure protection for mobile backhaul services.
Configuring CSGs

route-policy nms-vpn-frr permit node 10//Deploys a routing policy for the VPN
FRR.
Deploy VPN FRR.

NOTE
Deploy BFD for TE to speed up VPN FRR. For details about the configuration, see the chapter about
MPLS.
Configuring MASGs

route-policy nms-vpn-frr permit node 10//Deploying a routing policy for the VPN
FRR.
Deploy VPN FRR.

NOTE
Deploy BFD for BGP Tunnel to speed up VPN FRR. For details about the configuration, see the
section about configuring MPLS tunnels (BGP LSPs).

l Run the display ip routing-table vpn-instance vpn-instance-name ip-address verbose
command on a CSG or MASG, to query the standby next hop, the standby label, and the
standby tunnel ID.
<CSG1> display ip routing-table vpn-instance LTE-RAN 192.168.2.0 verbose

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

Summary Count : 1


IndirectID: 0x12
BkPETunnelID: 0x2 BkPESecTunnelID: 0x0
BkIndirectID: 0xf
8.3 Deploying Local Switching Ethernet Service Bearer and

Protection (HVPN+Labeled BGP)
in the HVPN+Labeled BGP solution.
8.3.1 Local Switching Ethernet Service Deployment Solution

This section describes the principles to deploy local switching Ethernet service bearer and
protection.
Local switching Ethernet services are also called LTE X2 services. An IP tunnel is set up between
eNodeBs to transmit LTE X2 packets along the shortest path. LTE X2 packets make up
approximately 5% of total traffic.
LTE X2 services are subordinate to LTE S1 services and cannot be independently deployed.
LTE X2 services can be deployed only after LTE S1 services are deployed.
LTE X2 services are mainly carried over LDP LSPs. It is recommended to configure the same
VPN instance for LTE X2 and LTE S1 services. Separate VPN instances can also be configured.
Figure 8-13 LTE X2 services forwarding model

CSG1 ASG3
CSG2 ASG4
CSG3
CSGn ASGm
LTE X2 service forwarding between CSGs
LTE X2 service forwarding over ASG
LTE X2 service forwarding between ASGs
LTE X2 services can be transmitted in three modes:

l Exchanged between CSGs on the same ring along the shortest path
l Exchanged between access rings connected to the same ASG pair through the ASGs along
the shortest path
l Exchanged between access rings connected to different ASG pairs through the ASGs
Figure 8-14 Service forwarding diagram
l LTE X2 services are forwarded along the shortest paths within an access ring or across
access rings. LTE X2 services are transmitted through specific routes within an access ring
from the source CSG to the destination CSG directly.
l LTE X2 services are transmitted across access rings through default routes. Services are
forwarded to an ASG connected to the local ring and then to the ASG on the destination
ring through a specific route between the two ASGs. Then, the ASG on the destination ring
forwards services to the destination CSG.
l Private network routes advertised by a CSG are reflected by an ASG (with inline RR) to
another CSG on the same ring based on the RT value carried by the route. The ASG does
not change the next hop of the route.
l For a route destined for a node on another access ring, the ASG changes the next hop to
itself, and forwards the route to an RR, which reflects the route to another ASG.
l The ASG advertises a default route to all subordinate CSGs, to support transmission of
LTE X2 services across access rings. Therefore, VRF (IP forwarding) must be configured
for the ASG to support the advertisement of default routes.

Figure 8-15 RT planning diagram
l Use RT values to control routes of CSGs. RT values are planned by access ring (or ASG
pair) to control the advertisement of LTE X2 service routes.
l Deploy BGP ORF for the CSGs and ASGs to reduce route advertisement load and restrict
routes advertised by other rings to the local ring.
8.3.2 Data Planning

This section provides the data plan for service configurations.
NOTE
Role Value Remarks
CSG1 interface Ethernet0/3/0.100: The IP addresses of different

192.168.3.1/24 AC interfaces for X2 services
cannot be set in the same
network segment.

network segment.
It is recommended to configure the same VPN instance for LTE X2 and S1 services and plan
VPN parameters consistently for both types of services. To prevent CSGs from receiving
network-wide private network routes, RT filtering is preferred to control CSG routes. In this
case, you need to plan different RT values for CSGs connected to one ASG pair. The design can
be performed by ASG pair or by access ring.
The workload for planning RTs by access ring is heavy. Therefore, it is recommended to plan
RTs by ASG pair. The planning details are as follows:

Table 8-10 RT plan
CSG ASG MASG
Acc
RT- RT- AS RT-
ess AS RT-
impo expor G impo RT-export RT-import
Rin G export
rt t Pair rt
g
Acce
ASG
ss 1:1; 1:1; ASG 200:1;
pair 100:1
ring 200:1 100:1 3 100:1
1
1
Acce
ASG
ss 1:1; 1:1; ASG 200:1;
pair 100:1
ring 200:1 100:1 4 100:1
1
2
... ... ... ... ... ... ... 100:1 100:1
Acce
ASG
ss 1:m; 1:m; ASG 200:1;
pair 100:1
ring 200:1 100:1 5 100:1
m
m
Acce
ASG
ss 1:m; 1:m; ASG 200:1;
pair 100:1
ring 200:1 100:1 6 100:1
m
n
8.3.3 Deploying an L3VPN and Protection

This section describes how to configure an L3VPN to carry LTE X2 services and protection for
the services.
In this example, the same VPN instance is created for LTE X2 and LTE S1 services. VPN FRR
is configured. In addition, configure the network to prevent black hole routes.
Configuring CSGs
The VPN instance and VPN route advertisement have been configured. In this section, you only
need to bind service interfaces to the VPN instance.
l Configure service interfaces.
vlan-type dot1q 100
ip binding vpn-instance LTE-RAN//Binds a VPN instance with the corresponding
service interfaces.
ip address 192.168.3.1 255.255.255.0
ipv4-family

vpn-target 1:1 200:1 import-extcommunity

#
Configuring ASGs
Configure the master and slave ASGs. The following uses ASG3 (the master ASG) as an example
to illustrate the configuration.
Create a VPN instance based on the carried services.
ip vpn-instance LTE-RAN//Creates a VPN instance for ETH services.
ipv4-family
only after being configured with an RD.
tnl-policy IPRAN

route-policy nms-vpn-frr permit node 10
apply backup-nexthop auto
Deploy VPN FRR.

vpn frr route-policy nms-vpn-frr
3. Configure linkage for the default routes to prevent a black hole route.
ip route-static vpn-instance LTE-RAN 0.0.0.0 0 192.168.21.21//Associates the
default route to the private network loopback IP address of an MASG.
NOTE
Before running this command, verify that tunnels have been set up successfully between all ASGs and the
loopback IP addresses of all associated MASGs.
4. Configure VPN routes for ASGs.
route-policy preferred-value permit node 10 //Configures a routing policy so
that local default routes are preferred and sets the community attribute.
bgp 100
network 0.0.0.0 route-policy preferred-value//Advertises the default route
in the VPN.
NOTE
Configuring MASGs
The VPN instance and VPN route advertisement have been configured. Configure the MASGs
similar as configuring MASGs for S1 services. In addition, configure the network to prevent
black hole routes.
The following uses MASG1 as an example. Configure the private network loopback interface
and bind the the loopback interface to the VPN instance.
interface LoopBack5
ip address 192.168.21.21 255.255.255.255//Sets the private network loopback IP
addresses to the same for the master and slave MASGs.


1. Run the display bgp vpnv4 vpn-instance LTE-RAN routing-table command to query
the MED values on BGP routes. The MED values can distinguish active and standby routes.
Run the command on CSGs and ASGs to query the advertisement of default routes.
[CSG1]display bgp vpnv4 vpn-instance LTE-RAN routing-table
BGP Local router ID is
1.1.1.1
Status codes: * - valid, > - best, d -
damped,
h - history, i - internal, s - suppressed, S -
Stale
Origin : i - IGP, e - EGP, ? -
incomplete
VPN-Instance LTE-RAN, Router ID
2.2.2.2:
Total Number of Routes:
9
Network NextHop MED LocPrf PrefVal Path/
Ogn
*>i 0.0.0.0 3.3.3.3 103 100 0

i
* i 4.4.4.4 203 100 0 i
*>i 12.12.12.1/32 3.3.3.3 103 100
0 ?
* i 4.4.4.4 203 100
0 ?
*> 120.16.1.2/32 0.0.0.0 0
0 ?
*>i 192.168.2.0 3.3.3.3 103 100
0 ?
* i 4.4.4.4 203 100
0 ?
*>i 192.168.2.100/32 3.3.3.3 103 100
0 ?
* i 4.4.4.4 203 100
0 ?
*> 192.168.1.0 0.0.0.0 0
0 ?
*> 192.168.1.1/32 0.0.0.0 0
0 ?
*>i 192.168.21.21/32 3.3.3.3 103 100
0 ?
* i 4.4.4.4 203 100 0 ?
[ASG3]display bgp vpnv4 vpn-instance LTE-RAN routing-table
3.3.3.3
damped,
Stale
incomplete
Total number of routes from all PE:

7
Route Distinguisher:
100:100
Ogn
*> 0.0.0.0 0.0.0.0 0 32768 i
*>i 12.12.12.1/32 5.5.5.5 103 100
0 ?
* i 6.6.6.6 203 100
0 ?

*>i 120.16.1.2/32 1.1.1.1 103 100

10 ?
*>i 192.168.2.0 5.5.5.5 103 100
0 ?
* i 6.6.6.6 203 100
0 ?
*>i 192.168.2.100/32 5.5.5.5 103 100
0 ?
*>i 192.168.1.0 1.1.1.1 103 100
10 ?
*>i 192.168.21.21/32 5.5.5.5 103 100
0 ?
* i 6.6.6.6 203 100 0 ?
command on ASGs to query advertisement of community attributes of routes.
[ASG3]display bgp vpnv4 vpn-instance LTE-RAN routing-table community 1000:2
3.3.3.3
damped,
Stale
incomplete
3.3.3.3:

1
Network NextHop MED LocPrf PrefVal
Community
*> 0.0.0.0 0.0.0.0 0 32768 <1000:2>
8.4 Deploying Local Switching Ethernet Service Bearer and

Protection (Labeled BGP to Edge)
in the Labeled BGP to Edge solution.
8.4.1 Local Switching Ethernet Service Deployment Solution

This section describes the principles to deploy local switching Ethernet service bearer and
protection.
Local switching Ethernet services are also called LTE X2 services. An IP tunnel is set up between
eNodeBs to transmit LTE X2 packets along the shortest path. LTE X2 packets make up
approximately 5% of total traffic.
LTE X2 services are subordinate to LTE S1 services and cannot be independently deployed.
LTE X2 services can be deployed only after LTE S1 services are deployed.
LTE X2 services are mainly carried over LDP LSPs. It is recommended to configure the same
VPN instance for LTE X2 and LTE S1 services. Separate VPN instances can also be configured.

Figure 8-16 LTE X2 services forwarding model

CSG1 ASG3
CSG2 ASG4
CSG3
CSGn ASGm
LTE X2 service forwarding between CSGs
LTE X2 service forwarding over ASG
LTE X2 service forwarding between ASGs
LTE X2 services can be transmitted in three modes:

l Exchanged between CSGs on the same ring along the shortest path
l Exchanged between access rings connected to the same ASG pair through the ASGs along
the shortest path
l Exchanged between access rings connected to different ASG pairs through the ASGs
Figure 8-17 Service forwarding diagram
Aggregation
VRF
VRF
ASG
ASG
Access 1 Inter-ring X2
VRF Access 2
VRF
ASG
ASG
VRF Intra-ring X2
VRF VRF
CSG
eNodeB CSG CSG
eNodeB eNodeB
PDU PDU PDU

IP IP IP
ETH VRF Label ETH
LDP LSP
Label
ETH
PDU PDU PDU PDU PDU
IP IP IP IP IP
ETH VRF Label 1 VRF Label 1 VRF Label 1 ETH
BGP LSP BGP LSP BGP LSP
Label 1 Label 2 Label3
LDP/TE LSP LDP/TE LSP LDP/TE LSP
Label 1 Label 2 Label 3
ETH ETH ETH
In addition, inter-AS BGP LSPs must be set up between CSGs on different rings. The loopback
addresses of the CSGs are advertised to each other using the Labeled BGP. Routing policies

must be configured for ASGs, to control public network routes and filter routes from access
rings irrelevant to the X2 services.
Figure 8-18 RT planning diagram
Within an access ring, there are specific routes by nature. For LTE X2 services across rings,
specific routes must be configured. Therefore, based on RT design, the import RT values must
include the RT values of the neighbor rings.
8.4.2 Data Planning

This section provides the data plan for service configurations.
NOTE
Role Value Remarks

network segment.

network segment.
It is recommended to configure the same VPN instance for LTE X2 and S1 services and plan
the VPN parameters consistently.

8.4.3 Deploying an L3VPN and Protection

This section describes how to configure an L3VPN to carry LTE X2 services and protection for
the services.
In this example, the same VPN instance is created for LTE X2 and LTE S1 services. CSG1 and
CSG50 must communicate with each other. CSG1 is dual-homed to ASG3 and ASG4, and
CSG50 is dual-homed to ASG53 and ASG54.
Figure 8-19 Networking diagram
Table 8-12 RT plan example
CSG ASG MASG
Acc
RT- RT- AS RT-
ess AS RT-
impo expor G impo RT-export RT-import
Rin G export
rt t Pair rt
g
Acce ASG
1:1;1: ASG
ss 1:1;10 3,
5;200: pair - -
ring 0:1 ASG
1 1
1 4
- -
Acce ASG
1:5;1: ASG
ss 1:5;10 53,
1;200: pair - -
ring 0:1 ASG
1 5
50 54
Configuring CSG1
vlan-type dot1q 100


service interfaces.
ip address 192.168.3.1 255.255.255.0
ipv4-family
vpn-target 1:1 100:1 export-extcommunity //Adds an RT value for the exported
VPN routes to home them to ASG pair 1 (ASG3 and ASG4), so that the CSGs homed
to ASG pair 5 (ASG53 and ASG54) can receive the routes.
vpn-target 1:1 1:5 200:1 import-extcommunity //Enables an NE to receive VPN
routes from CSGs homed to ASG pair 1 and ASG pair 5.
Configuring CSG50
vlan-type dot1q 100
service interfaces.
ip address 192.168.50.1 255.255.255.0
ipv4-family
vpn-target 1:5 100:1 export-extcommunity //Adds an RT value for the exported
VPN routes to home them to ASG pair 5 (ASG53 and ASG54), so that the CSGs homed
to ASG pair 1 (ASG3 and ASG4) can receive the routes.
vpn-target 1:5 1:1 200:1 import-extcommunity //Enables an NE to receive VPN
routes from CSGs homed to ASG pair 5 and ASG pair 1.
Configuring ASG3
Configure the master and slave ASGs. The following uses ASG3 (the master ASG) as an example
to illustrate the configuration.
1. Configure MP-BGP. Configure a routing policy to control public network routes, and filter
routes from access rings irrelevant to the exchange of the X2 services, to ensure that inter-
AS BGP LSPs are set up between CSGs on different access rings.
#
ip ip-prefix MASG2 index 10 permit 10.10.10.10
32
#
ip community-filter access1 permit 1:1
ip community-filter access50 permit 1:50 //Allows the receiving of routes from
CSG50.
#
apply cost 50
apply community 1:1 additive //Adds the community attribute 1:1 to routes from
CSG1.
#
if-match mpls-label
apply cost 50
apply mpls-label
#
if-match mpls-label
apply cost 100
apply mpls-label
#


if-match mpls-label
if-match community-filter access1
if-match community-filter access50 //Allows advertising routed received from
CSG50 to CSG1.
apply cost 100
apply mpls-
label
#
bgp 100
#
ipv4-family unicast
peer CSG enable
peer 1.1.1.1 enable
#
NOTE
Configuring ASG53
For basic configurations of ASG53, see the previous part of this manual. Configure the master
and slave ASGs. The following uses ASG53 (the master ASG) as an example to illustrate the
configuration.
1. Configure MP-BGP. Configure a routing policy to control public network routes, and filter
routes from access rings irrelevant to the exchange of the X2 services, to ensure that inter-
AS BGP LSPs are set up between CSGs on different access rings.
#
ip ip-prefix MASG2 index 10 permit 10.10.10.10
32
#
#
apply cost 50
#
if-match mpls-label
apply cost 50
apply mpls-label
#
if-match mpls-label
apply cost 100
apply mpls-label
#
if-match mpls-label


apply cost 100
apply mpls-label
#
bgp 100
#
ipv4-family unicast
peer CSG enable
#

1. Run the display bgp vpnv4 vpn-instance LTE-RAN routing-table command to query
the MED values on BGP routes. The MED values can distinguish active and standby routes.
Run the command on CSGs to query the advertisement of default routes.
[CSG1]display bgp vpnv4 vpn-instance LTE-RAN routing-table
1.1.1.1
damped,
Stale
incomplete
1.1.1.1:
10
Ogn
*>i 12.12.12.1/32 3.3.3.3 103 100

0 ?
* i 4.4.4.4 203 100
0 ?
*>i 192.168.50.0 50.50.50.50 103 100
0 ?
* i 50.50.50.50 203 100
0 ?
*>i 192.168.2.100/32 3.3.3.3 103 100
0 ?
* i 4.4.4.4 203 100
0 ?
*> 192.168.1.0 0.0.0.0 0
0 ?
*> 192.168.1.1/32 0.0.0.0 0
0 ?
*>i 192.168.21.21/32 3.3.3.3 103 100
0 ?
* i 4.4.4.4 203 100 0 ?

8.5 Deploying QoS

This chapter describes the roadmap, data plan, and procedure for configuring QoS in the DiffServ
model.
The scheduling requirements on different services from base stations are different. On an
IPRAN, the transmission of high-priority services must be ensured, so it is recommended to use
the uniform mode in a DiffServ domain and disable the write-back of priorities to wireless
services according to priorities on the bearer network at egress interfaces, to ensure consistency
of DSCP values of wireless packets from end to end.
8.5.1 Deploying QoS for Ethernet Services

This section describes the roadmap, data plan, and procedure for configuring QoS for Ethernet
services using the DiffServ model.
8.5.1.1 Configuration Roadmap

This section describes the roadmap for configuring QoS for Ethernet services.
For Ethernet services on a mobile backhaul network, configure priority-based scheduling after
configuring DSCP-based simple traffic classification and priority mapping. Deploy the DiffServ
domain according to the desired priority mapping rules.
NOTE
For Ethernet services, 802.1p-based simple traffic classification be also be configured. DSCP-based simple
traffic classification is recommended in the MBB solution and is used as an example in this section.
QoS must be configured on interfaces that carry services to schedule the services by
priority. For example, configure QoS for an interface or sub-interface that carries services.
Configure QoS in the same way if an NNI or a network-side sub-interface carries services.
The major roadmap for configuring QoS in the case of simple traffic classification is as follows:
l CSG: After a DiffServ domain is deployed for a CSG according to the priority mapping
rules, the CSG performs traffic classification and priority mapping based on DSCP values,
and performs priority-based scheduling.
l ASG: An ASG performs priority mapping based on MPLS EXP values and then performs
priority-based scheduling.
l MASG: After a DiffServ domain is deployed for an MASG according to the priority
mapping rules, the MASG performs traffic classification and priority mapping based on
DSCP values, and performs priority-based scheduling.
Configure HQoS as follows if rate restriction is required for the traffic:

l Configure PHB and traffic shaping on flow queues.
l Configure a QoS profile.
l Apply the QoS profile on service interfaces.

NOTICE
Base stations and RNCs do not allow any modification to DSCP values included in IP packets
sent between them. If DSCP values are modified during transmission, base stations or RNCs
will report alarms. The DSCP has 64 optional values while the MPLS EXP has only 8 optional
values (namely, 0, 10, 18, 26, 34, 46, 48, and 56). If an IP packet from a base station or RNC
takes a DSCP value other than the eight MPLS EXP values, the DSCP value will be changed to
one of the eight MPLS EXP values at the egress interface of the router on the network. It is
recommended to set the DSCP values of IP packets from a base station or RNC to the standard
values. PHB mapping can be disabled in some scenarios.
8.5.1.2 Data Planning

This section provide the data plan for deploying QoS.
NOTE
Table 8-13 3G Ethernet service priority mapping
Service Type DSCP EXP PHB Scheduling

Mode
Real-time voice 46 5 EF PQ
services,
signaling (R99
conversational,
R99 streaming),
and clock
signals
OM and real- 26 3 AF3 PQ+WFQ

time HSDPA
services
Non-real-time 18 2 AF2 PQ+WFQ

R99 services
(R99
interactive, R99
background)
Non-real-time 0 0 BE PQ+WFQ
HSDPA
services
(HSDPA
interactive,
HSDPA
background)

Table 8-14 LTE Ethernet service priority mapping
Service Service QCI DSCP EXP Scheduling

Type Sub-type Mode
Wireless Real-time 1 46 (EF) 5 PQ

services voice service
Real-time 2 26 (AF32) 3 PQ+WFQ

video/voice
Real-time 3 34(AF41) 4 PQ+WFQ

gaming
Real-time 4 26 (AF32) 3 PQ+WFQ

video/data
IMS 5 46 (EF) 5 PQ
signaling
Non-real- 6 18 (AF21) 2 PQ+WFQ

time video
service and
TCP-related
services

time voice,
video, and
games

time video
service and 9 0 (BE) 0 PQ+WFQ
TCP-related
services
Protocol - SCTP 46 (EF) 5 PQ

control
OM - MML 46 (EF) 5 PQ
FTP 10 (AF11) 1 PQ+WFQ
IP clock - - 46 (EF) 5 PQ
Passing-by - - - - -
traffic
8.5.1.3 Configuring Priority Mapping

Priority mapping is configured to allow packets from the wireless side to enter correct queues
on the bearer network.

Configuring CSGs
1. Configure a DiffServ domain.

In this example, the priority mapping for 3G Ethernet services is used as an example. The
priority mapping rules for 3G Ethernet services are the same as the priority mapping rules
in the default DiffServ domain, so the default priority mapping rules in the default domain
are used.
If the priority mapping rules are the same as those of the default DiffServ domain, do not
modify the mapping rules in the default domain. Otherwise, modify the mapping rules in
the domain, or create a new DiffServ domain. For example, if the IP DSCP value of an
ingress queue is 62, the PHB is CS6. If the PHB of an egress queue is CSG6, the IP DSCP
is 62. The configurations are as follows:
diffserv domain example//Creates a DiffServ domain.
ip-dscp-inbound 62 phb cs6 green//Sets the priority mapping relationships.
ip-dscp-outbound cs6 green map 62
2. Bind the service ingress interface to the DiffServ domain.

interface Ethernet0/3/0.10//Enters an AC-side service interface.
trust upstream default//Binds an interface to the DiffServ domain, so that
packets that enter the interface are mapped based on the mappings of the
domain.
3. Bind the NNI to the DiffServ domain.

trust upstream default
#
Configuring ASGs

For details, see the CSG design guidelines. If a new DiffServ domain is created, it is
recommended to configure the same priority mapping rules network-wide.
qos phb disable //Disables the write-back for internal priorities of equipment
into user packets, to ensure that the priority fields (such as DSCP) of user
packets are not modified.
qos phb disable
qos phb disable


qos phb disable
qos phb disable
qos phb disable
3. Users can copy the EXP values of outer labels to EXP of inner labels as desired.
#
bgp 100
peer 10.5.7.2 exp-mode uniform //Copies the EXP values on TE tunnels
or LDP LSPs in an AS to the EXP fields of BGP LSPs based on the BGP neighbor
relationship.

qos phb disable
qos phb disable
qos phb disable
3. (Optional) Users can copy the EXP values of outer labels to EXP of inner labels as desired.
#
bgp 200
peer 10.5.7.1 exp-mode uniform //Copies the EXP values on TE tunnels
or LDP LSPs in an AS to the EXP fields of BGP LSPs based on the BGP neighbor
relationship.
Configuring MASGs
2. Bind the service ingress interface to the DiffServ domain.
l If the MASGs interconnect with the BSC in VRRP mode, configure QoS for the service
interface as follows:
trust upstream default vlan 100
qos phb disable vlan 100

l If the MASGs interconnect with the BSC through active and standby routes, configure
QoS for the service interface as follows:
qos phb disable
qos phb disable

qos phb disable
qos phb disable
8.5.1.4 Configuring Queue Scheduling and Bandwidth (Optional)

Different scheduling modes and bandwidth guarantee can be configured for different queues to
ensure the good quality of high-priority services.
After simple traffic classification is configured, if traffic shaping and bandwidth must be
configured for queues, configure HQoS as follows:
Configuring CSGs
1. Configure a flow queue profile and a QoS profile.
flow-queue csg-uni//Creates a flow queue profile. The default mapping will be
used if the mapping is not modified in the domain. Run the display flow-queue
configuration command to view default priority mappings.
queue ef pq shaping 200//Modifies the scheduling mode of a flow queue. In this
example, priority queuing (PQ) is used for EF queues, and the traffic shaping
rate is 200 kbit/s.
queue cs6 pq shaping 70
#
qos-profile csg-uni//Configures a QoS profile.
user-queue cir 4000 pir 4000 flow-queue csg-uni//Configures queue bandwidth
and binds the bandwidth to a flow queue.
2. Apply the QoS profile to an interface.

interface GigabitEthernet0/2/16//Enters an NNI.
qos-profile csg-uni outbound
Configuring ASGs and ASBRs

The ASGs and ASBRs do not need to be configured.
Configuring MASGs
1. Configure a flow queue profile and a QoS profile.
flow-queue masg-uni//Creates a flow queue profile. The default mapping will be
used if the mapping is not modified in the domain. Run the display flow-queue
configuration command to view default priority mappings.
queue ef pq shaping 2000//Modifies the scheduling mode of a flow queue. In
this example, priority queuing (PQ) is used for EF queues, and the traffic

shaping rate is 2000 kbit/s.

queue cs6 pq shaping 500
#
qos-profile masg-uni//Configures a QoS profile.
user-queue cir 10000 pir 20000 flow-queue rsg-uni//Configures queue bandwidth
and binds the bandwidth to a flow queue.
2. Apply the QoS profile to an interface.

If VRRP protection is configured on the MASG side, configure QoS for service interfaces
as follows:
interface Eth-Trunk1//Enters an AC-side interface.
qos-profile masg-uni inbound vlan 100
#
qos-profile masg-uni inbound vlan 100
If active and standby routes are configured on the MASG side, configure QoS for service
interfaces as follows:
qos-profile masg-uni inbound

Configuration Guide (CLI) 9 Deploying Enterprise Services
9 Deploying Enterprise Services
About This Chapter
Enterprise services are common in an IDEAL solution. The hierarchical VPN architecture
supports the access of massive amount of enterprise services. Most enterprise services are L2
enterprise services, including P2P enterprise services and MP2MP enterprise services.
9.1 P2P Enterprise Service Deployment Solution (HVPN+Labeled BGP)

In the HVPN+Labeled BGP solution, P2P enterprise services are carried over MS-PWs.
9.2 P2P Enterprise Service Deployment Solution (Labeled BGP to Edge)

In the Labeled BGP to Edge solution, P2P enterprise services are carried over SS-PWs.
9.3 MP2MP Enterprise Service Deployment Solution (HVPN+Labeled BGP)

H-VPLS (using VLLs) is deployed to carry MP2MP enterprise services.
9.4 MP2MP Enterprise Service Deployment Solution (Labeled BGP to Edge)

9.1 P2P Enterprise Service Deployment Solution (HVPN

+Labeled BGP)
In the HVPN+Labeled BGP solution, P2P enterprise services are carried over MS-PWs.
9.1.1 Deploying Ethernet Service Bearer and Protection

This section describes how to configure P2P enterprise Ethernet services on MS-PWs.
9.1.1.1 Configuration Principle

This section describes how to configure services on MS-PWs.
As shown in Figure 9-1, an MS-PW is set up between CSG1 and CSG31, and the intermediate
ASG is the switching node, to transmit P2P enterprise services.
Figure 9-1 Topology of MS-PW redundancy

IPRAN IPRAN
AS 200
AS 100 AS 300
Primary
Enterprise ASG33 Enterprise

CSG1 ASG3 ASBR 1 ASBR 3 Core layer ASBR5 ASBR 7 CSG31
customer Access layer Aggregation layer Aggregation layer Access layer customer
IGP domain IGP domain
IGP domain IGP domain IGP domain
CSG2 CSG32
ASG4 ASBR 2 ASBR 4 ASBR6 ASBR 8 ASG34
Secondary
TE/LDP TE/LDP TE/LDP TE/LDP TE/LDP

LSP
swap swap swap swap
BGP LSP BGP LSP BGP LSP BGP LSP
iBGP LSP
MS-PW MS-PW MS-PW
VPN TE / LDP LSP TE/ LDP LSP BGP LSP TE/ LDP LSP BGP LSP TE/ LDP LSP TE / LDP LSP VPN
The roadmap for configuring MS-PW services is as follows:
1. Configure service interfaces.

2. Enable MPLS L2VPN on the devices.
3. Configure remote LDP sessions between the CSGs and ASGs and between the ASGs and
MASGs.
l Configure the remote LDP session between CSG1 and ASG3.
l Configure the remote LDP session between ASG3 and ASG33.

4. Configure MS-PW services.

l Configure PW services on the CSGs and configure PW switching on the ASGs.
l Deploy PW redundancy (in active/standby mode) protection on CSGs.

This section provides the data plan for deploying MS-PWs.
NOTE
Table 9-1 PW ID plan
Parame CSG1 ASG3 ASG4 ASG33 ASG34 CSG31

ter
Active 500 500/502 - 502/504 - 504

PW
Standby 501 - 501/503 - 503/505 505

PW
Table 9-2 Service interface plan
CSG1 CSG31
GigabitEthernet0/2/19.1 GigabitEthernet0/2/19.1
Table 9-3 BFD for PW plan
Parameter CSG1 CSG31
Detecting the PW interface GigabitEthernet0/2/19.1 GigabitEthernet0/2/19.1
Local discriminator 51 51
Remote discriminator 51 51
9.1.1.3 Configuring MS-PWs (Ethernet Services)

This section describes how to configure MS-PWs for Ethernet services.
Configuring CSG1 (IPRAN AS 100)

1. Enable MPLS L2VPN and MPLS LDP remote sessions.
#
mpls l2vpn//Enables MPLS L2VPN.

#
mpls ldp
#
mpls ldp remote-peer 3.3.3.3//PWs use extended LDP signaling to distribute VPN
labels. Therefore, a remote MPLS LDP session needs to be configured between the
two ends of a PW.
remote-ip 3.3.3.3
#
mpls ldp remote-peer 4.4.4.4
remote-ip 4.4.4.4
#
2. Configure a PW profile.
#
pw-template
eth
control-word //Enables control words for the PW profile.

tnl-policy IPRAN//Configures the tunnel policy used by the PW.
#

#
interface
vlan-type dot1q
11
mpls l2vc 3.3.3.3 pw-template eth 500 //Configures the active

PW.
mpls l2vc 4.4.4.4 pw-template eth 501 secondary //Configures the standby
PW.
mpls l2vpn redundancy master //Sets the negotiation mode of PW redundancy to
active/
standby.
mpls l2vpn reroute delay 500 Sets the PW WTR time to

500s.
mpls l2vpn stream-dual-receiving //Allows both the active and standby PWs to
receive packets.
#
Configuring the Master ASG (IPRAN AS 100)

Configure PW switching on ASG3 (the master ASG) to set up MS-PWs.

#
mpls l2vpn
#
mpls ldp
#
remote-ip 1.1.1.1
#
remote-ip 33.33.33.33
#
2. Configure PW switching.
#
mpls switch-l2vc 33.33.33.33 502 tunnel-policy IPRAN between 1.1.1.1 500

tunnel-policy IPRAN encapsulation vlan control-word-transparent

//Specifies the encapsulation type supported by PW switching to VLAN
encapsulation and enables the transparent transmission of control words.
#
Configuring the Slave ASG (IPRAN AS 100)

Configure PW switching on ASG4 (the slave ASG) to set up MS-PWs.

#
mpls l2vpn
#
mpls ldp
#
remote-ip 1.1.1.1
#
remote-ip 34.34.34.34
#
#

#
Configuring the Master ASG (IPRAN AS 300)

Configure PW switching on ASG33 (the master ASG) to set up MS-PWs.

#
mpls l2vpn
#
mpls ldp
#
remote-ip 31.31.31.31
#
remote-ip 3.3.3.3
#
#

#
Configuring the Slave ASG (IPRAN AS 300)

Configure PW switching on ASG34 (the slave ASG) to set up MS-PWs.

#
mpls l2vpn
#
mpls ldp
#
remote-ip 31.31.31.31
#
remote-ip 4.4.4.4
#
#

#

#
#
mpls ldp
#
remote-ip 33.33.33.33
#
remote-ip 34.34.34.34
#
#
pw-template
eth

#

#
interface
vlan-type dot1q
11
mpls l2vc 33.33.33.33 pw-template eth 504 //Configures the active

PW.
mpls l2vc 34.34.34.34 pw-template eth 505 secondary //Configures the standby
PW.
mpls l2vpn redundancy master //Sets the negotiation mode of PW redundancy to
active/
standby.
mpls l2vpn reroute delay 500 //Sets the PW WTR time to

500s.
mpls l2vpn stream-dual-receiving //Allows both the active and standby PWs to

receive packets.
#

l Check the PW status.
Run the display mpls l2vc interface interface-number command on the CSGs and ASGs
to query the VC status. The result shows that the VC is in the Up state.
<CSG1>display mpls l2vc interface GigabitEthernet0/2/19.1
*client interface : GigabitEthernet0/2/19.1 is
up
Administrator PW :
no
session state :
up
AC status :
up
VC state :
up
Label state :
0
Token state :
0
VC ID :
500
VC type :
VLAN
destination :
3.3.3.3
local group ID : 0 remote group ID :

0
local VC label : 299 remote VC label :
155665
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 :
available
BFD sessionIndex : 1106 BFD state :

up
VCCV State :
up
manual fault : not

set
active state :
active
forwarding entry :
exist
OAM Protocol :
--
OAM Status :
--
OAM Fault Type :

--
PW APS ID :
0
PW APS Status :
--
TTL Value :
1
link state :
up
local VC MTU : 1500 remote VC MTU :

1500
local VCCV : cw alert ttl lsp-ping
bfd
remote VCCV : cw alert ttl lsp-ping
bfd
local control word : enable remote control word :
enable
tunnel policy name :
--
PW template name :
eth
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 : cr-lsp, TNL ID :

0x2f3
Backup TNL type : lsp , TNL ID :
0x0
create time : 0 days, 4 hours, 33 minutes, 46
seconds
up time : 0 days, 0 hours, 9 minutes, 37
seconds
last change time : 0 days, 0 hours, 9 minutes, 37
seconds
VC last up time : 2013/12/19
18:54:38
VC total up time : 0 days, 2 hours, 36 minutes, 35

seconds
CKey :
72
NKey :
71
PW redundancy mode :
master
AdminPw interface :
--
AdminPw link state :

--
Diffserv Mode :
uniform
Service Class :
--
Color :
--
DomainId :
--
Domain Name :
--

up
Administrator PW :
no
session state :
up
AC status :
up
VC state :
up
Label state :
0

Token state :
0
VC ID :
501
VC type :
VLAN
destination :
4.4.4.4

0
153092
up

up

forwarding
local status code :

0x20

up

up

forwarding

0x20

no
BFD for PW :
unavailable
VCCV State :
up
manual fault : not

set
active state :
inactive
forwarding entry :
exist
OAM Protocol :
--
OAM Status :
--
OAM Fault Type :

--

PW APS ID :
0
PW APS Status :
--
TTL Value :
1
link state :
up

1500
bfd
bfd
enable
--
PW template name :
eth
secondary
load balance type :

flow
Access-port :
false

tokens
NO.0 TNL type : cr-lsp, TNL ID :

0x2d9
0x0
seconds
seconds
seconds
19:01:06

seconds
CKey :
74
NKey :
73
master
AdminPw interface :
--

--
Diffserv Mode :
uniform
Service Class :
--
Color :
--
DomainId :
--
Domain Name :
--
Protect Resource :
available
reroute policy : delay 500

s
reason of last reroute : New LDP mapping message was

received
time of last reroute : 0 days, 2 hours, 33 minutes, 23
seconds
delay timer ID : -- residual
time :--
resume timer ID : -- residual time :--
<ASG3>display mpls switch-l2vc

Total Switch VC : 1, 1 up, 0
down
*Switch-l2vc type : LDP<----

>LDP
Peer IP Address :
33.33.33.33,1.1.1.1
VC ID : 502,
500
VC Type :
VLAN
VC State :
up
VC StatusCode |PSN |OAM | FW | |PSN |OAM | FW

|
-Local VC :| UP | UP | UP | | UP | UP | UP
|
-Remote VC:| UP | UP | UP | | UP | UP | UP
|
Session State : up,
up
Local/Remote Label : 155664/155694,

155665/299
InLabel Status : 0 ,
0

Local/Remote MTU : 1500/1500,

1500/1500
Local/Remote Control Word : Enable/Enable, Enable/
Enable
Local/Remote VCCV Capability : cw alert ttl lsp-ping bfd /cw alert ttl lsp-
ping bfd , cw alert ttl lsp-ping bfd /cw alert ttl lsp-p
ing
bfd
Switch-l2vc tunnel
info :
1 tunnels for peer

33.33.33.33
NO.0 TNL Type : lsp , TNL ID :
0x76
1 tunnels for peer
1.1.1.1
NO.0 TNL Type : cr-lsp, TNL ID :
0x6000072
CKey : 2,
4
NKey : 1,
3
Tunnel policy : --,

--
Control-Word transparent :
YES
Create time : 0 days, 0 hours, 12 minutes, 9

seconds
UP time : 0 days, 0 hours, 10 minutes, 48
seconds
Last change time : 0 days, 0 hours, 10 minutes, 48
seconds
11:16:04
VC total up time : 0 days, 0 hours, 10 minutes, 48 seconds
9.1.1.4 Configuring BFD for PW

Configure BFD for PW to speed up the switchover in the case of a fault.
NOTICE
The planned detection period of BFD for PW is 150 ms.
Configuring CSG1
l Configure BFD for the active PW on CSG1.
bfd eth_primary_pw bind pw interface GigabitEthernet0/2/19.1
min-tx-interval 150
min-rx-interval 150
commit

Configuring CSG31
min-tx-interval 150
min-rx-interval 150
commit

Run the display bfd session all for-pw command to view the BFD status.
The BFD session of the S_PW (M) type is in the Up state. The BFD session has been established
successfully.
<CSG1>display bfd session all for-pw
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
51 51 --.--.--.-- Up S_PW(M) GigabitEthernet0/2/19.1
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
51 51 --.--.--.-- Up S_PW(M) GigabitEthernet0/2/19.1
--------------------------------------------------------------------------------
9.1.2 Deploying TDM Service Bearer and Protection

This section describes how to configure P2P enterprise TDM services on MS-PWs.

This section describes how to configure services on MS-PWs.


IPRAN IPRAN
AS 200
AS 100 AS 300
Primary

CSG2 CSG32
Secondary

LSP
swap swap swap swap
iBGP LSP
MS-PW MS-PW MS-PW
The roadmap for configuring MS-PW services is as follows:

3. Configure remote LDP sessions between the CSGs and ASGs and between the ASGs and
MASGs.
4. Configure MS-PW services.
l Configure PW services on the CSGs and configure PW switching on the ASGs.
l Deploy PW redundancy (in active/standby mode) protection on CSGs.

This section provides the data plan for TDM services carried over MS-PWs.
NOTE

Table 9-4 PW parameters
mpls ldp remote-peer Set the value to the name of a Create a remote LDP session.
remote LDP session between
an ASG and a CSG.
mpls l2vpn redundancy master Set the negotiation mode of

PW redundancy to active/
standby.
Table 9-5 TDM service interface
NE Role Service Interface Remarks
CSG1 interface Serial0/2/3:0 -

controller E1 0/2/3Use a clear channel:
using e1.
CSG31 interface Serial0/2/3:0 -

using e1.
Parame CSG1 ASG3 ASG4 ASG33 ASG34 CSG31

ter
Active 1000 1000/1002 - 1002/1004 - 1004

PW
Standby 1001 - 1001/1003 - 1003/100 1005

PW 5
Table 9-7 BFD for PW plan
Detecting the PW interface interface Serial0/2/3: 0 interface Serial0/2/3: 0
Local discriminator 52 52
Remote discriminator 52 52

9.1.2.3 Configuring MS-PWs

This section describes how to configure MS-PWs to carry TDM services.

1. Enable MPLS L2VPN globally.
mpls l2vpn
2. Set up remote LDP sessions.

mpls ldp
#
remote-ip 3.3.3.3
#
remote-ip 4.4.4.4
pw-template tdm//Creates a PW profile for TDM services.
control-word//Enables the control word for TDM services to help transmit alarm
and clock information.
jitter-buffer depth 4//Sets the depth of the jitter buffer to 4 ms.
tdm-encapsulation-number 8//Sets the number of TDM frames to be encapsulated
into a PW-carried packet to 8. The number must be the same on both ends of a
PW.
4. Configure TDM service interfaces.

controller E1 0/2/3
using e1//Configures the clear channel mode.
#
interface Serial0/2/3:0
link-protocol tdm //Sets the link protocol to TDM.
5. Configure PWs.
mpls l2vc 3.3.3.3 pw-template tdm 1000//Sets up the active PW (between a CSG
and the master ASG).
mpls l2vc 4.4.4.4 pw-template tdm 1001 secondary//Sets up the standby PW
(between a CSG and the slave ASG).
mpls l2vpn oam-mapping//Enable status mapping between the AC side and the
network side.
mpls l2vpn redundancy master//Configures PW redundancy in the active/standby
mode.
mpls l2vpn reroute delay 500//Sets the PW switchback delay to 500s.
mpls l2vpn stream-dual-receiving//Allows both the active and standby PWs to
receive packets. This prevents packet loss during traffic switchback to the
primary PW.
Configuring ASG3 (IPRAN AS 100)

mpls l2vpn

mpls ldp
remote-ip 1.1.1.1
remote-ip 33.33.33.33


tunnel-policy IPRAN encapsulation satop-e1 control-word-transparent
//Specifies the encapsulation type supported by PW switching to SAToP-E1
#

mpls l2vpn

mpls ldp
remote-ip 1.1.1.1
remote-ip 34.34.34.34
#

#

mpls l2vpn

mpls ldp
#
remote-ip 33.33.33.33
#
remote-ip 34.34.34.34
PW.

controller E1 0/2/3
#
5. Configure PWs.
mpls l2vc 33.33.33.33 pw-template tdm 1004//Sets up the active PW (between a
CSG and the master ASG).

mpls l2vc 34.34.34.34 pw-template tdm 1005 secondary//Sets up the standby PW

(between a CSG and the slave ASG).
mpls l2vpn oam-mapping//Enable status mapping between the AC side and the
network side.
mode.
mpls l2vpn reroute delay 500//Sets the PW switchback delay to 500s.
mpls l2vpn stream-dual-receiving//Allows both the active and standby PWs to
receive packets. This prevents packet loss during traffic switchback to the
primary PW.

mpls l2vpn

mpls ldp
remote-ip 31.31.31.31
remote-ip 3.3.3.3
#

#

mpls l2vpn

mpls ldp
remote-ip 31.31.31.31
remote-ip 4.4.4.4
#

#
9.1.2.4 Configuring BFD for PW

Configure BFD for PW to speed up the switchover in the case of a fault.
NOTICE
The planned detection period of BFD for PW is 150 ms.


bfd tdm_primary_pw bind pw interface Serial0/2/3:0
min-tx-interval 150
min-rx-interval 150
commit

min-tx-interval 150
min-rx-interval 150
commit

Run the display bfd session all for-pw command to view the BFD status.
successfully.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
52 21 --.--.--.-- Up S_PW(M) Serial0/2/3:0
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
52 52 --.--.--.-- Up S_PW(M) Serial0/2/3:0
--------------------------------------------------------------------------------
9.1.2.5 Verifying the Configuration

Check the PW status and connectivity.

Check L2VPN connections on CSGs and MASGs. The result shows that an L2 VC is set
up and is in the Up state.
<CSG1>dis mpls l2vc interface Serial 0/2/3:0
*client interface : Serial0/2/3:0 is up
Administrator PW : no
session state : up
AC status : up
VC state : up
Label state : 0
Token state : 0
VC ID : 1000
VC type : SAT E1 over Packet
destination : 3.3.3.3
local group ID : 0 remote group ID : 0

local VC label : 43 remote VC label : 155754

local TDM Encap Num : 8 remote TDM Encap Num : 8
jitter-buffer : 4
idle-code : ff
local rtp-header : disable remote rtp-header : disable
local bit-rate : 32 remote bit-rate : 32
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 : available
BFD sessionIndex : 1034 BFD state : up
VCCV State : up
manual fault : not set
active state : active
forwarding entry : exist
OAM Protocol : --
OAM Status : --
OAM Fault Type : --
PW APS ID : 0
PW APS Status : --
TTL Value : 1
link state : up
local VC MTU : -- remote VC MTU : --
local VCCV : cw alert ttl lsp-ping bfd
remote VCCV : cw alert ttl lsp-ping bfd
local control word : enable remote control word : enable
tunnel policy name : IPRAN
PW template name : tdm
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 : cr lsp, TNL ID : 0x1
Backup TNL type : lsp , TNL ID : 0x0
create time : 0 days, 0 hours, 59 minutes, 36 seconds
up time : 0 days, 0 hours, 22 minutes, 42 seconds
last change time : 0 days, 0 hours, 22 minutes, 42 seconds
VC last up time : 2014/02/12 19:49:06
CKey : 24
NKey : 17
PW redundancy mode : master
AdminPw interface : --
AdminPw link state : --
Diffserv Mode : pipe
Service Class : ef
Color : green
DomainId : --
Domain Name : --
*client interface : Serial0/2/3:0 is up

session state : up
AC status : up
VC state : up
Label state : 0
Token state : 0
VC ID : 1001
VC type : SAT E1 over Packet
destination : 4.4.4.4

local group ID : 0 remote group ID : 0

local VC label : 44 remote VC label : 155752
local TDM Encap Num : 8 remote TDM Encap Num : 8
jitter-buffer : 4
idle-code : ff
local rtp-header : disable remote rtp-header : disable
local bit-rate : 32 remote bit-rate : 32
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 : inactive
forwarding entry : exist
OAM Protocol : --
OAM Status : --
OAM Fault Type : --
PW APS ID : 0
PW APS Status : --
TTL Value : 1
link state : up
local VC MTU : -- remote VC MTU : --
local VCCV : cw alert ttl lsp-ping bfd
remote VCCV : cw alert ttl lsp-ping bfd
local control word : enable remote control word : enable
tunnel policy name : IPRAN
PW template name : tdm
primary or secondary : secondary
load balance type : flow
Access-port : false
VC tunnel/token info : 1 tunnels/tokens
NO.0 TNL type : cr lsp, TNL ID : 0x2
Backup TNL type : lsp , TNL ID : 0x0
create time : 0 days, 0 hours, 59 minutes, 21 seconds
up time : 0 days, 0 hours, 20 minutes, 18 seconds
last change time : 0 days, 0 hours, 20 minutes, 18 seconds
VC last up time : 2014/02/12 19:51:31
CKey : 23
NKey : 19
PW redundancy mode : master
AdminPw interface : --
AdminPw link state : --
Diffserv Mode : pipe
Service Class : ef
Color : green
DomainId : --
Domain Name : --
Protect Resource : available
reroute policy : delay 30 s, resume 10 s

reason of last reroute : --
time of last reroute : -- days, -- hours, -- minutes, -- seconds
delay timer ID : -- residual time :--
resume timer ID : -- residual time :--

9.2 P2P Enterprise Service Deployment Solution (Labeled

BGP to Edge)
In the Labeled BGP to Edge solution, P2P enterprise services are carried over SS-PWs.
9.2.1 Deploying Ethernet Service Bearer and Protection

This section describes how to configure P2P enterprise Ethernet services on SS-PWs.

This section describes the roadmap for configuring services on SS-PWs.
As shown in Figure 9-3, set up an SS-PW between CSG1 and CSG31.
Figure 9-3 SS-PW service topology

IPRAN IPRAN
AS 200
AS 100 AS 300
SS-PW

IGP domain
IGP domain IGP domain IGP domain IGP domain
CSG2 CSG32

LSP
Labeled BGP swap swap swap swap swap swap
BGP LSP BGP LSP BGP LSP BGP LSP BGP LSP BGP LSP
to Edge iBGP LSP
SS-PW
The configuration roadmap for SS-PW services is as follows:
1. Enable MPLS L2VPN on the CSGs.

2. Configure the remote LDP session between CSGs.
4. Configure SS-PW services.

This section describe the data plan for SS-PW deployment.
NOTE

mpls ldp remote-peer CSG31: 31.31.31.31 CSG1: 1.1.1.1
PW 600 600
Service interface GigabitEthernet0/2/19.20 GigabitEthernet0/2/19.20
9.2.1.3 Configuring SS-PWs

This section describes how to configure SS-PWs for Ethernet services.

#
mpls ldp
#
mpls ldp remote-peer 31.31.31.31//PWs use extended LDP signaling to distribute
VPN labels. Therefore, a remote MPLS LDP session needs to be configured between
the two ends of a PW.
remote-ip 31.31.31.31
#
#
pw-template
eth

#
3. Configure SS-PWs.
#
vlan-type dot1q 12
mpls l2vc 31.31.31.31 pw-template eth 600
#

Add a node into the routing policy ipv4-to-csg sent to CSG1, so that CSG1 and CSG31 can
communicate at the public network plane.
#
ip ip-prefix CSG30 index 10 permit 31.31.31.31 32
#
if-match mpls-label
if-match ip-prefix CSG31
apply mpls-label
#

NOTE

Add a node for the routing policy ipv4-to-csg sent to CSG31, so that CSG31 and CSG1 can
#
#
if-match mpls-label
apply mpls-label
#
NOTE

#
mpls ldp
#
remote-ip 1.1.1.1
#
#
pw-template
eth
control-word
tnl-policy IPRAN
#
3. Configure SS-PWs.
#
vlan-type dot1q 12
#


Run the display mpls l2vc interface interface-number command on the CSG to view the
VC status. The result shows that the VC is in the Up state.
<CSG1>display mpls l2vc interface GigabitEthernet0/2/19.20


down
Administrator PW :
no
session state : up
AC status : up
VC state : up
Label state :
0
Token state :
0
VC ID :
600
VC type :
VLAN
destination :
31.31.31.31
0
0
up
up
local forwarding state : not
forwarding
local status code :
0x1
BFD for PW :
unavailable
VCCV State :
up
manual fault : not
set
active state :
inactive
forwarding entry : not
exist
OAM Protocol :
--
OAM Status :
--
OAM Fault Type :
--
PW APS ID :
0
PW APS Status :
--
TTL Value :
1
link state :
down
0
bfd
remote VCCV :
none
none
IPRAN
PW template name :
eth
primary

load balance type :

flow
Access-port :
false
Switchover Flag :
false
tokens
0x0
seconds
seconds
seconds
09:44:52
seconds
CKey :
9
NKey :
11
frr
AdminPw interface :
--
--
Diffserv Mode :
uniform
Service Class :
--
Color :
--
DomainId :
--
Domain Name :
--
9.2.2 Deploying TDM Service Bearer and Protection

This section describes how to configure P2P enterprise TDM services on SS-PWs.

This section describes the roadmap for configuring services on SS-PWs.


IPRAN IPRAN
AS 200
AS 100 AS 300
SS-PW

IGP domain
CSG2 CSG32

LSP
to Edge iBGP LSP
SS-PW
The configuration roadmap for SS-PW services is as follows:
1. Enable MPLS L2VPN on the CSGs.

2. Configure the remote LDP session between CSGs.
4. Configure SS-PW services.

This section provides the data plan for TDM services carried over SS-PWs.
NOTE
Table 9-9 SS-PW parameters
mpls ldp remote-peer Set the value to the name of a Create a remote LDP session.
remote LDP session between
an ASG and a CSG.
mpls l2vpn redundancy master Set the negotiation mode of

PW redundancy to active/
standby.

bfd bind pw discriminator local Set the minimum interval at

discriminator remote which BFD packets are sent
as required.
min-tx-interval
Detection interval =
min-rx-interval Multiplier x Interval at which
BFD packets are sent/
received
If TE HSB or APS protection
is deployed on the service-
bearing tunnel and if the
tunnel fault detection interval
is 3x10 ms, set the detection
interval of BFD for PW to
3x50 ms. If the service-
bearing tunnel is not
protected, set the detection
interval of BFD for PW to
3x10 ms.
Table 9-10 TDM service interface
NE Role Service Interface Remarks
CSG1 interface Serial0/2/3: 0 -

using e1.
CSG31 interface Serial0/2/3: 0 -

using e1.
PW 1000 1000
9.2.2.3 Configuring SS-PWs

This section describes how to configure SS-PWs to carry TDM services.

Configuring CSGs (IPRAN AS 100)

Configure CSGs on access rings. The following uses CSG1 as an example to illustrate the
configuration.
mpls l2vpn

#
mpls ldp
#
remote-ip 31.31.31.31
#
PW.

controller E1 0/2/3
#
5. Configure PWs.
mpls l2vc 31.31.31.31 pw-template tdm 1000//Sets up a PW (from CSG1 to
CSG31).
mpls l2vpn oam-mapping//Enables status mapping between the AC side and the
network side.

Add a node into the routing policy ipv4-to-csg sent to CSG1, so that CSG1 and CSG31 can
#
#
if-match mpls-label
apply mpls-label
#

Add a node for the routing policy ipv4-to-csg sent to CSG31, so that CSG31 and CSG1 can
#
#

if-match mpls-label
apply mpls-label
#
Configuring CSGs (IPRAN AS 300)

Configure CSGs on access rings. The following uses CSG31 as an example to illustrate the
configuration.
mpls l2vpn

#
mpls ldp
#
remote-ip 1.1.1.1
#
PW.

controller E1 0/2/3
#
5. Configure PWs.
mpls l2vc 1.1.1.1 pw-template tdm 1000//Sets up a PW (from CSG1 to CSG31).
mpls l2vpn oam-mapping//Enables status mapping between the AC side and the
network side.


Run the display mpls l2vc interface interface-number command on the CSG to view the
VC status. The result shows that the VC is in the Up state.
<CSG1>display mpls l2vc interface Serial0/2/3:0
*client interface : Serial0/2/3:0 is
up
Administrator PW :
no
session state :
up
AC status :
up

VC state :
up
Label state :
0
Token state :
0
VC ID :
1011
VC type : SAT E1 over
Packet
destination :
31.31.31.31
0
129
local TDM Encap Num : 8 remote TDM Encap Num :
8
jitter-buffer :
4
idle-code :
ff
local rtp-header : disable remote rtp-header :
disable
local bit-rate : 32 remote bit-rate :
32
up
up
forwarding
local status code :
0x0
up
up
forwarding
0x0
no
BFD for PW :
unavailable
VCCV State :
up
manual fault : not
set
active state :
active
forwarding entry :
exist
OAM Protocol :
--
OAM Status :
--
OAM Fault Type :
--
PW APS ID :
0
PW APS Status :
--
TTL Value :
1
link state :

up
local VC MTU : -- remote VC MTU :
--
bfd
bfd
enable
IPRAN
PW template name :
tdm
primary
load balance type :
flow
Access-port :
false
Switchover Flag :
false
tokens
NO.0 TNL type : lsp , TNL ID :
0x1e
0x1f
seconds
seconds
seconds
10:45:42
seconds
CKey :
19
NKey :
11
frr
AdminPw interface :
--
--
Diffserv Mode :
pipe
Service Class :
ef
Color :
green
DomainId :
--
Domain Name : --
9.3 MP2MP Enterprise Service Deployment Solution

(HVPN+Labeled BGP)
H-VPLS (using VLLs) is deployed to carry MP2MP enterprise services.

9.3.1 MP2MP Enterprise Service Deployment Solution

This section describes the roadmap for configuring MP2MP Ethernet service bearer and
protection.

IPRAN IPRAN
AS 200
AS 100 AS 300
Access layer Access layer

Enterprise
CSG1 ASG3 ASBR 1 ASBR 3 Core
layer ASBR5 ASBR7 ASG33 CSG31 Enterprise
customer
Aggregation layer IGP domain Aggregation layer customer
Enterprise CSG2 CSG

customer

LSP swap
swap swap swap
HVPN+Labeled iBGP LSP
eBGP LSP
eBGP LSP iBGP LSP
BGPsolution iBGP LSP
VPNswap VPNswap
VLL VPLS VLL
In the HVPN+Labeled BGP sub-solution, the H-VPLS (VLLs for VPLS) solution is used to
carry MP2MP L2 enterprise services.
The configuration roadmap is as follows:

2. Configure remote LDP sessions for CSGs and ASGs.
4. Configure PW redundancy services on CSGs.
5. Configure PW services from ASGs to CSGs.
6. Configure VSI services between ASGs.
7. Configure BFD for PW. Configure static BFD for PW between the UPEs and SPEs to speed
up the active/standby switchover for PWs.
9.3.2 Data Planning

This section provides the data plan for deploying H-VPLS.
NOTE

Table 9-12 Data plan for L2VPN services
AC-side interface name and CSG1: CSG: PWE3 is used to access

VLAN ID GigabitEthernet0/2/19.600 services on Ethernet
CSG2: interfaces.
GigabitEthernet0/2/19.600 The outer-layer VLAN ID of
CSG31: services must be the same.
VLAN ID of all sub-
interfaces: 600
LDP Peer CSG1: ASG3, ASG4

CSG2: ASG3, ASG4
ASG3: CSG1, CSG2
ASG4: CSG1, CSG2
ASG33: CSG31
ASG34: CSG31
CSG31: ASG33, ASG34
VC ID of a PW CSG1-ASG3: 601 VC IDs at both ends of a PW

CSG1-ASG4: 602 must be identical.
CSG2-ASG3: 603
CSG2-ASG4: 604
CSG31-ASG33: 605
CSG31-ASG34: 606
PW protection Redundancy protection (in

active/standby mode)
Table 9-13 VPLS service plan
VSI name vsi_600 -
LDP Peer ASG3: ASG4, ASG33,

ASG34
ASG4: ASG3, ASG33,
ASG34
ASG33: ASG34, ASG3,
ASG4
ASG34: ASG33, ASG3,
ASG4

VSI-ID 600 The ID of VSI services must

be the same.
9.3.3 Configuring H-VPLS

This section describes how to configure H-VPLS.
Configuring CSG1
#
mpls l2vpn
#

#
mpls ldp
#
remote-ip 3.3.3.3
#
remote-ip 4.4.4.4
#
3. Configuring service interfaces

#
display this//Checks whether DCN is enabled for the interface.
undo dcn
#
undo shutdown
vlan-type dot1q 600
#
4. Configure PWs.
#
mpls l2vc 3.3.3.3 601 tunnel-policy IPRAN//Configures the PW from a CSG to
the master ASG.
mpls l2vc 4.4.4.4 602 tunnel-policy IPRAN secondary//Configures the PW from
a CSG to the slave ASG.
mode.
mpls l2vpn reroute delay 500//Configures the WTR time for a PW.
#
Configuring CSG2
#
mpls l2vpn
#

#
mpls ldp

#
remote-ip 3.3.3.3
#
remote-ip 4.4.4.4
#

#
undo dcn
#
undo shutdown
vlan-type dot1q 600
#
4. Configure PWs.
#
mpls l2vc 3.3.3.3 603 tunnel-policy IPRAN//Configures the PW from a CSG to
the master ASG.
mpls l2vc 4.4.4.4 604 tunnel-policy IPRAN secondary//Configures the PW from
a CSG to the slave ASG.
mode.
#
Configuring ASG3
mpls l2vpn

#
mpls ldp
#
remote-ip 1.1.1.1
#
remote-ip 2.2.2.2
#
remote-ip 4.4.4.4
#
remote-ip 33.33.33.33
#
remote-ip 34.34.34.34
3. Configure a VSI instance.

#
vsi vsi_600 static
pwsignal ldp
vsi-id 600
mac-withdraw enable
upe-npe mac-withdraw enable
peer 4.4.4.4 tnl-policy IPRAN
peer 1.1.1.1 negotiation-vc-id 601 tnl-policy IPRAN upe ignore-standby-state

//Configures a PW to CSG1. Sets CSG1 as the

UPE. The PW backup status is neglected to prevent flapping of BFD for PW
sessions and speed up switching.
ignore-ac-state //Sets a VSI on an ASG to the up state because the VSI is not
bound with an AC interface.
isolate spoken//Enables isolation for packet forwarding between AC
interfaces, UPE PWs, and between AC interfaces and UPE PWs in one VSI
instance.
#
Configuring ASG4
mpls l2vpn

#
mpls ldp
#
remote-ip 1.1.1.1
#
remote-ip 2.2.2.2
#
remote-ip 3.3.3.3
#
remote-ip 33.33.33.33
#
remote-ip 34.34.34.34

#
vsi vsi_600 static
pwsignal ldp
vsi-id 600
mac-withdraw enable
ignore-ac-state
isolate spoken
#
Configuring ASG33
mpls l2vpn

#
mpls ldp
#
remote-ip 31.31.31.31
#

remote-ip 34.34.34.34
#
remote-ip 3.3.3.3
#
remote-ip 4.4.4.4
#

#
vsi vsi_600 static
pwsignal ldp
vsi-id 600
mac-withdraw enable
peer 31.31.31.31 negotiation-vc-id 605 tnl-policy IPRAN upe ignore-standby-
state
ignore-ac-state
isolate spoken
#
Configuring ASG34
mpls l2vpn

#
mpls ldp
#
remote-ip 31.31.31.31
#
remote-ip 33.33.33.33
#
remote-ip 3.3.3.3
#
remote-ip 4.4.4.4
#

#
vsi vsi_600 static
pwsignal ldp
vsi-id 600
mac-withdraw enable
peer 31.31.31.31 negotiation-vc-id 606 tnl-policy IPRAN upe ignore-standby-
state
ignore-ac-state
isolate spoken
#

Configuring CSG31
#
mpls l2vpn
#

#
mpls ldp
#
remote-ip 33.33.33.33
#
remote-ip 34.34.34.34
#

#
undo dcn
#
undo shutdown
vlan-type dot1q 600
#
4. Configure PWs.
#
mpls l2vc 33.33.33.33 605 tunnel-policy IPRAN//Configures the PW from a CSG
to the master ASG.
mpls l2vc 34.34.34.34 606 tunnel-policy IPRAN secondary//Configures the PW
from a CSG to the slave ASG.
mode.
#

l Check the PW status. Run the display mpls l2vc brief command on a CSG to check L2VPN
connections. The result shows that an L2 VC is set up and is in the Up state.
<CSG1>display mpls l2vc brief
Total LDP VC : 4 4 up 0 down
*Client Interface : GigabitEthernet0/2/19.600

AC status : up
VC State : up
Label state : 0
Token state : 0
VC ID : 601
VC Type : VLAN
session state : up
Destination : 3.3.3.3
link state : up
*Client Interface : GigabitEthernet0/2/19.600

AC status : up
VC State : up

Label state : 0
Token state : 0
VC ID : 602
VC Type : VLAN
session state : up
Destination : 4.4.4.4
link state : up
l Run the display vsi name vsi-name verbose command on an ASG to query the VSI
information. The result shows that the VSI is in the Up state.
<ASG3>display vsi name vsi_600 verbose
***VSI Name : vsi_600

Administrator VSI : no
Isolate Spoken : enable
VSI Index : 0
PW Signaling : ldp
Member Discovery Style : static
PW MAC Learn Style : unqualify
Encapsulation Type : vlan
MTU : 1500
Diffserv Mode : uniform
Service Class : --
Color : --
DomainId : 255
Domain Name :
Ignore AcState : enable
P2P VSI : disable
Multicast Fast Swicth : disable
Create Time : 0 days, 14 hours, 7 minutes, 20 seconds
VSI State : up
Resource Status : Valid
VSI ID : 600
LDP MAC-WITHDRAW : mac-withdraw Enable
: upe-npe Enable
*Peer Router ID : 4.4.4.4
ignore-standby-state : no
VC Label : 155736
Peer Type : dynamic
Session : up
Tunnel ID : 0x4200400f
Broadcast Tunnel ID : 0x4200400f
Broad BackupTunnel ID : 0x0
Tunnel Policy Name : IPRAN
CKey : 32
NKey : 33
Stp Enable : 0
PwIndex : 0
Control Word : disable
VC Label : 155737
Peer Type : dynamic
Session : up
Tunnel ID : 0x60033c0c
Broadcast Tunnel ID : 0x60033c0c
Broad BackupTunnel ID : 0x60033c0d
CKey : 6
NKey : 31
Stp Enable : 0
PwIndex : 0


VC Label : 155738
Peer Type : dynamic
Session : up
Tunnel ID : 0x60033c0e
Broadcast Tunnel ID : 0x60033c0e
Broad BackupTunnel ID : 0x60033c0f
CKey : 62
NKey : 61
Stp Enable : 0
PwIndex : 0
Negotiation-vc-id : 603
ignore-standby-state : yes
VC Label : 155739
Peer Type : dynamic
Session : up
Tunnel ID : 0x60033c10
Broadcast Tunnel ID : 0x60033c10
CKey : 64
NKey : 63
Stp Enable : 0
PwIndex : 0
Negotiation-vc-id : 601
ignore-standby-state : yes
VC Label : 155740
Peer Type : dynamic
Session : up
CKey : 66
NKey : 65
Stp Enable : 0
PwIndex : 0
**PW Information:
*Peer Ip Address : 4.4.4.4

PW State : up
Local VC Label : 155736
Remote VC Label : 155732
Remote Control Word : disable
PW Type : label
Tunnel ID : 0x4200400f
Broadcast Tunnel ID : 0x4200400f
Ckey : 0x20
Nkey : 0x21
Main PW Token : 0x4200400f
Slave PW Token : 0x0
Tnl Type : LSP
OutInterface : GigabitEthernet1/0/0
Backup OutInterface :
Stp Enable : 0
Mac Flapping : 0

PW Last Up Time : 2014/02/11 20:44:44

PW Total Up Time : 0 days, 14 hours, 1 minutes, 10 seconds
PW State : up
PW Type : label
Tunnel ID : 0x60033c0c
Broadcast Tunnel ID : 0x60033c0c
Broad BackupTunnel ID : 0x60033c0d
Ckey : 0x6
Nkey : 0x1f
Main PW Token : 0x40004010
Tnl Type : CR-LSP
OutInterface : Tunnel0/0/35
Backup OutInterface : Tunnel0/0/36
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2014/02/12 09:17:44
PW State : up
PW Type : label
Tunnel ID : 0x60033c0e
Broadcast Tunnel ID : 0x60033c0e
Broad BackupTunnel ID : 0x60033c0f
Ckey : 0x3e
Nkey : 0x3d
Tnl Type : CR-LSP
Backup OutInterface : Tunnel0/0/36
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2014/02/12 09:25:24
PW State : up
PW Type : MEHVPLS
Ckey : 0x40
Nkey : 0x3f
Tnl Type : CR-LSP
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2014/02/12 10:02:12
PW State : up

PW Type : MEHVPLS
Ckey : 0x42
Nkey : 0x41
Main PW Token : 0x4000401a
Slave PW Token : 0x4000401b
Tnl Type : CR-LSP
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2014/02/12 10:19:41
9.3.4 Configuring BFD for PW

BFD for PW can speed up the traffic switchover between the active and standby PWs.
Configuring CSG1
Configure BFD for the active PW on CSG1.
bfd pw_601 bind pw interface GigabitEthernet0/2/19.600 remote-peer 3.3.3.3 pw-ttl
auto-calculate//Configures BFD for the active PW.
min-tx-interval 50
min-rx-interval 50
commit
Configuring CSG2
auto-calculate//Configures BFD for the active PW.
min-tx-interval 50
min-rx-interval 50
commit
Configuring ASG3
Configure BFD for the active PW on ASG3.
bfd pw_601 bind pw vsi vsi_600 peer 1.1.1.1 vc-id 601 remote-peer 1.1.1.1 pw-ttl
auto-calculate
min-tx-interval 50
min-rx-interval 50
commit
auto-calculate
min-tx-interval 50
min-rx-interval 50
commit

Configuring CSG31
bfd pw_605 bind pw interface GigabitEthernet0/2/19.600 remote-peer 33.33.33.33 pw-
ttl auto-calculate//Configures BFD for the active PW.
min-tx-interval 50
min-rx-interval 50
commit
Configuring ASG33
Configure BFD for the active PW on ASG33.
bfd pw_605 bind pw vsi vsi_600 peer 31.31.31.31 vc-id 605 remote-peer 31.31.31.31
pw-ttl auto-calculate
min-tx-interval 50
min-rx-interval 50
commit

Run the display bfd session all for-pw command on a CSG or run the display bfd session all
for-vsi-pw command on an ASG to query the BFD status.
successfully. The result of the query on the ASG shows that the BFD session of the S_VSI_PW
type is in the Up state.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
45 46 3.3.3.3 Up S_PW(M) GigabitEthernet0/2/19.600
--------------------------------------------------------------------------------
<ASG3>display bfd session all for-vsi-pw
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
46 45 1.1.1.1 Up S_VSI_PW -
56 55 2.2.2.2 Up S_VSI_PW -
--------------------------------------------------------------------------------
9.4 MP2MP Enterprise Service Deployment Solution

(Labeled BGP to Edge)
9.4.1 MP2MP Enterprise Service Deployment Solution
This section describes the roadmap for configuring MP2MP Ethernet service bearer and
protection.


IPRAN IPRAN
AS 200
AS 100 AS 300
Enterprise ASG
CSG1 ASG ASBR 1 ASBR 3 ASBR5 ASBR 1 CSG31
customer Access layer Aggregation layer Access layer Enterprise
Aggregation layer Core layer
IGP domain IGP domain IGP domain customer
Enterprise CSG2 CSG32

ASG ASBR 2 ASBR 4 ASBR6 ASBR 2 ASG
customer

LSP swap
swap swap swap
Labeled BGP BGP LSP BGP LSP
BGP LSP
to Edge iBGP LSP
VPLS
VPN TE / LDP LSP TE/ LDP LSP BGP LSP TE/ LDP LSP BGP LSP TE/ LDP LSP TE / LDP LSP
The VPLS solution is adopted for MP2MP L2 enterprise services. It is recommended to receive
and transmit MP2MP services at ASGs. CSGs can be used to receive and transmit a small amount
of the services (when the network contains less than 10 nodes).
9.4.2 Data Planning

This section provides the data plan for deploying VPLS.
NOTE
Table 9-14 VPLS service planning
VSI name vsi_700 -
LDP Peer CSG1: CSG2, CSG31, -

CSG32
CSG2: CSG1, CSG31,
CSG32
CSG31: CSG32, CSG1,
CSG2
CSG32: CSG31, CSG1,
CSG2
VSI-ID 700 The ID of VSI services must

be the same.

negotiation-vc-id Between CSG1 and CSG2: The value of negotiation-vc-

701 id must be the same at both
Between CSG1 and CSG31: ends.
702
Between CSG1 and CSG32:
703
704
705
706
9.4.3 Configuring VPLS

This section describes how to configure VPLS.
Configuring CSG1
#
mpls l2vpn
#

#
mpls ldp
#
remote-ip 2.2.2.2
#
remote-ip 31.31.31.31
#
remote-ip 32.32.32.32
#

#
vsi vsi_700 static
pwsignal ldp
vsi-id 700
peer 2.2.2.2 negotiation-vc-id 701 tnl-policy IPRAN //The value of
negotiation-vc-id must be the same at both ends.
peer 31.31.31.31 negotiation-vc-id 702 tnl-policy IPRAN
#
4. Configure L2 interfaces.
#
vlan-type dot1q 700

l2 binding vsi vsi_700 //Binds an interface to a VSI instance.

#
Configuring CSG2
#
mpls l2vpn
#

#
mpls ldp
#
remote-ip 1.1.1.1
#
remote-ip 31.31.31.31
#
remote-ip 32.32.32.32
#

#
vsi vsi_700 static
pwsignal ldp
vsi-id 700
#
#
vlan-type dot1q 700
l2 binding vsi vsi_700 //Binds an interface to a VSI instance.
#
Configuring CSG31
#
mpls l2vpn
#

#
mpls ldp
#
remote-ip 1.1.1.1
#
remote-ip 2.2.2.2
#
remote-ip 32.32.32.32
#

#
vsi vsi_700 static

pwsignal ldp
vsi-id 700
#
#
vlan-type dot1q 700
l2 binding vsi vsi_700
#
Configuring CSG32
#
mpls l2vpn
#

#
mpls ldp
#
remote-ip 1.1.1.1
#
remote-ip 2.2.2.2
#
remote-ip 31.31.31.31
#

#
vsi vsi_700 static
pwsignal ldp
vsi-id 700
#
#
vlan-type dot1q 700
#

Run the display vsi name v command on a CSG to check whether the VSI status is Up.
<CSG1>display vsi name vsi_700
v
***VSI Name :
vsi_700
Administrator VSI :
no
Isolate Spoken :

disable
VSI Index :
0
PW Signaling :
ldp
Member Discovery Style :
static
PW MAC Learn Style :
unqualify
Encapsulation Type :
vlan
MTU :
1500
Diffserv Mode :
uniform
Service Class :
--
Color :
--
DomainId :
255
Domain
Name :
Ignore AcState :
disable
P2P VSI :
disable
Create Time : 1 days, 18 hours, 26 minutes, 2
seconds
VSI State :
up
VSI ID :
700
*Peer Router ID :
2.2.2.2
Negotiation-vc-id :
701
primary
ignore-standby-state :
no
VC Label :
71
Peer Type :
dynamic
Session :
up
Tunnel ID :
0x35
Broadcast Tunnel ID :
0x35
Broad BackupTunnel ID :
0x0
Tunnel Policy Name :
IPRAN
CKey :
39
NKey :
40
Stp Enable :
0
PwIndex :
0
Control Word :
disable
*Peer Router ID :

31.31.31.31
Negotiation-vc-id :
702
primary
no
VC Label :
74
Peer Type :
dynamic
Session :
up
Tunnel ID :
0x14
0x14
0x15
IPRAN
CKey :
15
NKey :
11
Stp Enable :
0
PwIndex :
0
Control Word :
disable
*Peer Router ID :
32.32.32.32
Negotiation-vc-id :
703
primary
no
VC Label :
76
Peer Type :
dynamic
Session :
up
Tunnel ID :
0x36
0x36
0x17
IPRAN
CKey :
18
NKey :
13
Stp Enable :
0
PwIndex :
0
Interface Name :
State :
up

Access Port :
false
Last Up Time : 2014/02/19
11:30:39
Total Up Time : 0 days, 22 hours, 20 minutes, 32
seconds
**PW
Information:
*Peer Ip Address :
2.2.2.2
PW State :
up
Local VC Label :
71
Remote VC Label :
320
Remote Control Word :
disable
PW Type :
label
Tunnel ID :
0x35
0x35
0x0
Ckey :
0x27
Nkey :
0x28
Main PW Token :
0x35
Slave PW Token :
0x0
Tnl Type :
LSP
OutInterface :
Backup
OutInterface :
Stp Enable :
0
PW Last Up Time : 2014/02/19
20:55:38
PW Total Up Time : 1 days, 17 hours, 44 minutes, 58
seconds
*Peer Ip Address :
31.31.31.31
PW State :
up
Local VC Label :
74
Remote VC Label :
111
disable
PW Type :
label
Tunnel ID :
0x14
0x14
0x15
Ckey :

0xf
Nkey :
0xb
Main PW Token :
0x14
Slave PW Token :
0x0
Tnl Type :
LSP
OutInterface :
Tunnel0/0/13
Tunnel0/0/14
Stp Enable :
0
09:33:17
*Peer Ip Address :
32.32.32.32
PW State :
up
Local VC Label :
75
Remote VC Label :
113
disable
PW Type :
label
Tunnel ID :
0x25
0x25
0x17
Ckey :
0xa
Nkey :
0xc
Main PW Token :
0x19
Slave PW Token :
0x0
Tnl Type :
LSP
OutInterface :
Tunnel0/0/13
Tunnel0/0/14
Stp Enable :
0
09:33:28

Configuration Guide (CLI) 10 Deploying Clocks
10 Deploying Clocks
About This Chapter
This section describes how to configure IEEE 1588v2 and synchronous Ethernet for time and
frequency synchronization. For details, see the MBB V600R005C00 ATN+CX (HVPN+)
Solution Configuration Guide (CLI).
10.1 Configuration Roadmap

Different clock deployment solutions are available for different synchronization requirements.
It is recommended to deploy clocks by area in a Seamless MPLS solution.

10.1 Configuration Roadmap

Different clock deployment solutions are available for different synchronization requirements.
It is recommended to deploy clocks by area in a Seamless MPLS solution.
IPRAN Area
Multiple technologies can be used to transparently transmit clock signals. The recommended
solution is: using 1588v2 for time synchronization, using synchronous Ethernet for frequency
synchronization, and selecting sources according to Synchronization Status Message (SSM).
The deployment is the same as that in the HVPN solution. For details, see the MBB
V600R005C00 ATN+CX (HVPN+) Solution Configuration Guide (CLI).
Figure 10-1 Networking diagram for clock deployment

Master BITS
Clock pri 10
CSG1 Clock pri 10 ASG3 Clock pri 10 P11 Clock pri 10 RSG5
FE0/3/0 GE0/2/17 GE1/1/2 GE2/1/0 GE1/0/1
GE1/0/0 GE1/0/0
Clock pri 20
GE0/2/16 GE1/0/0 GE2/0/1
Clock pri 20 Clock pri 20 Clock pri 20
Clock pri 20 Clock pri 20 Clock pri 10

GE0/2/16 GE1/0/0 Clock pri 20 GE2/0/1
GE1/0/0 GE1/0/0
GE0/2/17 GE1/1/2 GE2/1/0 GE1/0/1
CSG2 Clock pri 10 ASG4 Clock pri 10 P12 Clock pri 10 RSG6
Clock pri 20
Clock Tracking Path
Clock pri n Priority of a reference clock source at a port
Slave BITS
Based on the networking shown in Figure 10-1, the configuration roadmap is as follows:
l Connect the master BITS to the master RSG and the slave BITS to the slave RSG to form
1+1 protection for clock sources. This can prevent interruption of clock signals due to a
single node failure.
l Enable the RSG5 to input the master clock and time signals to the network. Verify that
configurations on the master RSG and slave RSG are synchronous.
– Configure synchronous Ethernet to achieve frequency synchronization.
– Configure 1588v2 to achieve time synchronization.
l Enable synchronous Ethernet and 1588v2 time synchronization on ASGs and set them to
trace the upstream clock and time. The configurations of devices other than RSGs on the
aggregation ring are similar to those of the ASGs.
l Enable synchronous Ethernet and 1588v2 time synchronization on CSGs, and set them to
trace the upstream clock and time and sent the clock and time signals to base stations.
An ATN and a base station are connected in the following ways to achieve time
synchronization:

– The clock port on the ATN device is directly connected to the base station.
– Synchronization Ethernet or 1588v2 is used on the Ethernet interface to transmit clock
information to the base station. The base station is required to support synchronous
Ethernet or 1588v2. The configuration on the base station is the same as that on the
network-side interface.
– Run the clock master command (default configuration) on the E1 and ATM interfaces
to transmit clock information to the peer.
In this example, Ethernet interfaces are used to transmit clock signals. In the networking
diagram, the connection between CSG1 and the base station is used as an example. The
configurations for each CSG are identical.

Configuration Guide (CLI) 11 Configuration Files
11 Configuration Files
About This Chapter
11.1 Basic Configuration Files

Configuration for inner MPLS tunnels (BGP LSPs) is described separately for better
understanding.
11.2 E2E Mobile Backhaul Services Configuration File (HVPN+Labeled BGP)
11.3 E2E Mobile Backhaul Services Configuration File (Labeled BGP to Edge)
11.4 Local Switching Ethernet Service Configuration File (HVPN+Labeled BGP)
11.5 Local Switching Ethernet Service Configuration File (Labeled BGP to Edge)
11.6 P2P Enterprise Service (HVPN+Labeled BGP) Configuration File
11.7 P2P Enterprise Service (Labeled BGP to Edge) Configuration File
11.8 MP2MP Enterprise Service (HVPN+Labeled BGP) Configuration File
11.9 MP2MP Enterprise Service (Labeled BGP to Edge) Configuration File

11.1 Basic Configuration Files

Configuration for inner MPLS tunnels (BGP LSPs) is described separately for better
understanding.
11.1.1 Basic Configuration Files (Deployed IGP in ISIS mode)

The solution basic configuration contains configuring device name, log-in mode, IGP, MPLS
LSP (TE+LDP), DiffServ domain to NNI interfaces, clock synchronization and public DCN.
Figure 11-1 Network topology
AS 100 AS 200
RR1 RR3

GE0/2/16 GE2/1/0 GE1/0/1 GE1/0/1
GE1/1/2 GE1/0/0 GE1/0/0 GE1/0/0
GE1/0/0 GE2/0/1 GE2/0/1
GE0/2/17
Eth-Trunk 1
GE0/2/17 GE2/0/1 SGW/MME
GE1/0/0 GE2/0/1
GE1/1/2 GE1/0/0 GE1/0/0 GE1/0/0
GE2/1/0 GE1/0/1 GE1/0/1
GE0/2/16
RR2
RR4
Figure 11-2 Network devices and interface IP addresses

AS 100 AS 200
11.11.11.11//32 13.13.13.13//32
1.1.1.1/32 3.3.3.3/32 5.5.5.5/32 7.7.7.7/32 9.9.9.9/32

10.1.3.0/30 10.3.5.0/30 10.5.7.0/30 10.7.9.0/30
10.9.10.0/30
10.1.2.0/30
10.3.4.0/30
10.5.6.0/30
10.7.8.0/30
10.2.4.0/30 10.4.6.0/30
10.6.8.0/30 10.8.10.0/30
2.2.2.2/32 4.4.4.4/32 6.6.6.6/32 8.8.8.8/32 10.10.10.10/32
12.12.12.12//32 14.14.14.14//32

Figure 11-3 Network topology of IS-IS multi-process
AS 100 RR1 AS 200 RR3

Cost 10 Cost 10
Cost 100
IS-IS 1 IS-IS 100

Cost 100
Cost 2000
Cost 25
Cost 10
IS-IS 1000
Cost 10
Cost 25
L2 L2 L2
SGW/MME
Cost 100 Cost 10 Cost 10

RR2 RR4
ISIS interface of Access
ISIS interface of Aggregation
ISIS interface of Core
11.1.1.1 CSG1 Configuration File
#
sysname ATN910-CSG1-001
#
lldp enable
#
bfd
#
mpls lsr-id 1.1.1.1
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls te cspf
#
explicit-path main_1to3
next hop 10.1.3.2 include loose
#
#
mpls ldp
#
diffserv domain default
#
aaa
local-user root password cipher Changeme_123
authentication-scheme default0
authentication-scheme default
authentication-mode local radius
#
authorization-scheme default
#
accounting-scheme default0

#
domain default0
domain default1
domain default_admin
#
#
isis 1
is-level level-2
cost-style wide
flash-flood level-2
network-entity 49.0001.0010.0100.1001.00
is-name CSG1
timer spf 1 50 50
traffic-eng level-2
log-peer-change
#
description To asg3
undo shutdown
ip address 10.1.3.1 255.255.255.252
isis enable 1
isis cost 100
isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
#
description To csg2
undo shutdown
ip address 10.1.2.1 255.255.255.252
isis enable 1
isis cost 100
isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.255
isis enable 1
#
ip address 200.0.100.1 255.255.255.255
isis enable 1
#
ip address unnumbered interface LoopBack0
tunnel-protocol mpls te
destination 3.3.3.3
mpls te record-route label
mpls te backup hot-standby mode revertive wtr 60

mpls te reoptimization
mpls te backup hot-standby overlap-path
mpls te commit
#
destination 4.4.4.4
mpls te commit
#
snmp-agent
snmp-agent sys-info version all
snmp-agent mib-view included iso-view iso
snmp-agent community write cipher Huawei@123 mib-view iso-view
snmp-agent trap source LoopBack1000
snmp-agent target-host trap address udp-domain 130.10.100.20 params securityname
Huawei@123 v2c private-netmanager ext-vb
snmp-agent extend error-code enable
#
ssh user root
#
bfd LSP13 bind mpls-te interface Tunnel0/0/13 te-lsp
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
bfd te13 bind mpls-te interface Tunnel0/0/13
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#
tunnel-policy IPRAN

#
idle-timeout 5 0
#
11.1.1.2 ASG3 Configuration File
#
sysname CX600-X3-ASG3-003
#
#
#
lldp enable
#
bfd
#
mpls lsr-id 3.3.3.3
mpls
mpls te
mpls bfd enable
mpls rsvp-te
mpls rsvp-te hello
mpls te cspf
#
#
#
#
mpls ldp
#
aaa
#
#
#
domain default0
domain default1
#
#
isis 1
is-level level-2

cost-style wide
flash-flood level-2
network-entity 49.0001.0030.0300.3003.00
import-route direct cost 10000 route-policy LoopBack0
import-route isis 100 inherit-cost route-policy U2000
is-name ASG3
timer spf 1 50 50
traffic-eng level-2
log-peer-change
set-overload on-startup allow external
#
isis 100
is-level level-2
cost-style wide
flash-flood level-2
network-entity 49.0002.0030.0300.3003.00
is-name ASG3
timer spf 1 50 50
traffic-eng level-2
log-peer-change
#
description To csg1
undo shutdown
ip address 10.1.3.2 255.255.255.252
isis enable 1
isis cost 100
isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
qos phb disable
#
undo shutdown
ip address 10.3.5.1 255.255.255.252
isis enable 100
isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
qos phb disable
#
description To asg4
undo shutdown
ip address 10.3.4.5 255.255.255.252
isis enable 100

isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
qos phb disable
#
vlan-type dot1q 1
description To asg4
undo shutdown
ip address 10.3.4.1 255.255.255.252
isis enable 1
isis cost 2000
isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
qos phb disable
#
interface LoopBack0
ip address 3.3.3.3 255.255.255.255
isis enable 100
#
interface
LoopBack65535
255.255.255.255
isis enable 100

#
destination 1.1.1.1
mpls te commit
#
destination 5.5.5.5
mpls te commit
#
destination 6.6.6.6

mpls te commit
#
route-policy looplack0 permit node 10
if-match ip-prefix LoopBack0
#
if-match tag 2000
apply tag 2
#
route-policy acc deny node 10
#
route-policy acc permit node 20
apply tag 2
#
route-policy pref-nms permit node 10
if-match tag 2
#
#
snmp-agent
#
ssh user root
#
#
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#

min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#
tunnel-policy IPRAN
#
idle-timeout 5 0
#
#
sysname CX600-X3-ASG4-004
#
#
#
lldp enable
#
bfd
#
mpls lsr-id 4.4.4.4
mpls
mpls te
mpls bfd enable
mpls rsvp-te
mpls rsvp-te hello
mpls te cspf
#


#
#
#
mpls ldp
#
aaa
#
#
#
domain default0
domain default1
#
#
isis 1
is-level level-2
cost-style wide
flash-flood level-2
network-entity 49.0001.0040.0400.4004.00
import-route direct cost 10000 route-policy LoopBack0
import-route isis 100 inherit-cost route-policy U2000
is-name ASG4
timer spf 1 50 50
traffic-eng level-2
log-peer-change
set-overload on-startup allow external
#
isis 100
is-level level-2
cost-style wide
flash-flood level-2
network-entity 49.0002.0040.0400.4004.00
is-name ASG4
timer spf 1 50 50
traffic-eng level-2
log-peer-change
#
description To csg2
undo shutdown
ip address 10.2.4.2 255.255.255.252
isis enable 1

isis cost 100

isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
qos phb disable
#
undo shutdown
ip address 10.4.6.1 255.255.255.252
isis enable 100
isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
qos phb disable
#
description To asg3
undo shutdown
ip address 10.3.4.6 255.255.255.252
isis enable 100
isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
qos phb disable
#
vlan-type dot1q 1
description To asg3
undo shutdown
ip address 10.3.4.2 255.255.255.252
isis enable 1
isis cost 2000
isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
qos phb disable
#
interface LoopBack0
ip address 4.4.4.4 255.255.255.255
isis enable 100
#
interface
LoopBack65535
255.255.255.255

isis enable 100

#
destination 1.1.1.1
mpls te commit
#
destination 6.6.6.6
mpls te commit
#
destination 5.5.5.5
mpls te commit
#
route-policy looplack0 permit node 10
#
if-match tag 2000
apply tag 2
#
route-policy acc deny node 10
#
route-policy acc permit node 20
apply tag 2
#
if-match tag 2
#
#
snmp-agent


#
ssh user root
#
#
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#
tunnel-policy IPRAN
#

idle-timeout 5 0
#
11.1.1.4 (Aggregation layer) ASBR1 Configuration File
#
sysname CX600-X8-ASBR1-005
#
#
#
lldp enable
#
bfd
#
mpls lsr-id 5.5.5.5
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls te cspf
#
#
#
next hop 10.5.6.2 include strict
#
mpls ldp
#
aaa
#
#
#
domain default0
domain default1
#
#
isis 100
is-level level-2
cost-style wide
flash-flood level-2
network-entity 49.0002.0050.0500.5005.00

is-name ASBR1
timer spf 1 50 50
traffic-eng level-2
log-peer-change
#
description To asg3
undo shutdown
ip address 10.3.5.2 255.255.255.252
isis enable 100
isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
qos phb disable
#
undo shutdown
ip address 10.5.6.1 255.255.255.252
isis enable 100
isis cost 25
isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
qos phb disable
#
undo shutdown
ip address 10.5.7.1 255.255.255.252
mpls
qos phb disable
#
vlan-type dot1q 1
ip address 23.5.7.1 255.255.255.252
#
interface LoopBack0
isis enable 100
#
255.255.255.255
isis enable 100

#
destination 3.3.3.3


mpls te commit
#
destination 4.4.4.4
mpls te commit
#
destination 6.6.6.6
mpls te commit
#
bgp 100
router-id 5.5.5.5
#
ipv4-family unicast
preference route-policy pref-
nms
import-route isis 100 route-policy ipran-local
peer 23.5.7.2 route-policy ipran-out export
#
apply preference 10
#
10
#
10
#
10
U2000
apply tag 2000
#
ip ip-prefix ipran index 10 permit 200.0.100.0 24 greater-equal 24 less-equal
32
#

snmp-agent
#
ssh user root
#
#
tunnel-policy IPRAN
#
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#
bfd link_01 bind peer-ip default-ip interface gigabitethernet 1/0/1 //(Optional. If
10GE links do not support 802.3ae or GE links
work in full-
duplex mode, BFD needs to be configured.)

min-tx-interval 10
min-rx-interval 10
process-pst
commit
#

idle-timeout 5 0
#
11.1.1.5 (Aggregation Layer) ASBR2 Configuration File
#
#
#
#
lldp enable
#
bfd
#
mpls lsr-id 6.6.6.6
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls te cspf
#
#
#
#
mpls ldp
#
aaa
#
#
#
domain default0
domain default1
#
#
isis 100
is-level level-2
cost-style wide

flash-flood level-2
network-entity 49.0002.0060.0600.6006.00
is-name ASBR2
timer spf 1 50 50
traffic-eng level-2
log-peer-change
#
description To asg4
undo shutdown
ip address 10.4.6.2 255.255.255.252
isis enable 100
isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
qos phb disable
#
undo shutdown
ip address 10.5.6.2 255.255.255.252
isis enable 100
isis cost 25
isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
qos phb disable
#
undo shutdown
ip address 10.6.8.1 255.255.255.252
mpls
qos phb disable
#
vlan-type dot1q 1
ip address 23.6.8.1 255.255.255.252
#
interface LoopBack0
isis enable 100
#
255.255.255.255
isis enable 100

#

destination 3.3.3.3
mpls te commit
#
destination 4.4.4.4
mpls te commit
#
destination 5.5.5.5
mpls te commit
#
bgp 100
router-id 6.6.6.6
#
ipv4-family unicast
preference route-policy pref-
nms
import-route isis 100 route-policy ipran-local
peer 23.6.8.2 route-policy ipran-out export
#
apply preference 10
#
10
#
10
#
10
U2000
apply tag 2000
#


ip ip-prefix ipran index 10 permit 200.0.100.0 24 greater-equal 24 less-equal
32
#
snmp-agent
#
ssh user root
#
#
tunnel-policy IPRAN
#
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#
work in full-
min-tx-interval 10
min-rx-interval 10
process-pst

commit
#
idle-timeout 5 0
#
11.1.1.6 (Core Layer) ASBR3 Configuration File
#
#
#
#
lldp enable
#
ipv4-family
#
bfd
#
mpls lsr-id 7.7.7.7
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls te cspf
#
#
mpls ldp
#
aaa
#
#
#
domain default0
domain default1

#
#
isis 1000
is-level level-2
cost-style wide
flash-flood level-2
network-entity 49.0003.0070.0700.7007.00
is-name ASBR3
timer spf 1 50 50
traffic-eng level-2
log-peer-change
#
undo shutdown
undo shutdown
ip address 10.5.7.2 255.255.255.252
mpls
qos phb disable
#
undo shutdown
ip address 10.7.8.1 255.255.255.252
isis enable 1000
isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
qos phb disable
#
undo shutdown
ip address 10.7.9.1 255.255.255.252
isis enable 1000
isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
qos phb disable
#
vlan-type dot1q 1
ip binding vpn-instance __dcn_ideal__
ip address 23.5.7.2 255.255.255.252
#
interface LoopBack0
ip address 7.7.7.7 255.255.255.255
isis enable 100

#
ip address 200.0.100.7 255.255.255.255
#
destination 9.9.9.9
mpls te commit
#
destination 10.10.10.10
mpls te commit
#
destination 8.8.8.8
mpls te commit
#
bgp 200
router-id 7.7.7.7
#
ipv4-family vpnv4
#
ipv4-family vpn-instance __dcn_ideal__
peer 23.5.7.1 route-policy U2000 export
#
#
#
#
#
snmp-agent


#
ssh user root
#
#
tunnel-policy IPRAN
#
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#
work in full-
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#

idle-timeout 5 0
#
#
#
#
#
lldp enable
#
ipv4-family
#
bfd
#
mpls lsr-id 8.8.8.8
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls te cspf
#
#
mpls ldp
#
aaa
#
#
#
domain default0
domain default1
#
#
isis 1000
is-level level-2

cost-style wide
flash-flood level-2
network-entity 49.0003.0080.0800.8008.00
is-name ASBR4
timer spf 1 50 50
traffic-eng level-2
log-peer-change
#
undo shutdown
undo shutdown
ip address 10.6.8.2 255.255.255.252
mpls
qos phb disable
#
undo shutdown
ip address 10.7.8.2 255.255.255.252
isis enable 1000
isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
qos phb disable
#
undo shutdown
ip address 10.8.10.1 255.255.255.252
isis enable 1000
isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
qos phb disable
#
vlan-type dot1q 1
ip address 23.6.8.2 255.255.255.252
#
interface LoopBack0
ip address 8.8.8.8 255.255.255.255
isis enable 100
#
ip address 200.0.100.8 255.255.255.255
#

destination 9.9.9.9
mpls te commit
#
mpls te commit
#
destination 7.7.7.7
mpls te commit
#
bgp 200
router-id 8.8.8.8
#
ipv4-family vpnv4
#
#
#
#
#
#
snmp-agent


#
ssh user root
#
#
tunnel-policy IPRAN
#
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#
work in full-
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
idle-timeout 5 0
#

11.1.1.8 (Core Layer) RR3 Configuration File

#
ipv4-family
#
ip address 200.0.100.13 255.255.255.255
#
bgp
200
#
ipv4-family vpnv4
peer 7.7.7.7 enable
peer 8.8.8.8 enable
#
#
#
#
#

#
ipv4-family
#
ip address 200.0.100.14 255.255.255.255
#
bgp
200
#
ipv4-family vpnv4
peer 7.7.7.7 enable

peer 8.8.8.8 enable

#
#
#
#
#
11.1.1.10 MASG1 Configuration File
#
sysname CX600-X8-MASG1-001
#
#
#
lldp enable
#
ipv4-family
#
bfd
#
mpls lsr-id 9.9.9.9
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls te cspf
#
#
#
#
mpls ldp
#
aaa

#
#
#
domain default0
domain default1
#
#
ipv4-family
#
#
isis 1000
is-level level-2
cost-style wide
flash-flood level-2
network-entity 49.0003.0090.0900.9009.00
is-name MASG1
timer spf 1 50 50
traffic-eng level-2
log-peer-change
#
interface Eth-trunk 1
#
vlan-type dot1q 1
undo shutdown
ip address 10.9.10.1 255.255.255.252
isis enable 1000
isis cost 25
isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
qos phb disable
#
undo shutdown
ip address 10.7.9.2 255.255.255.252
isis enable 1000
isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp


qos phb disable
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
undo shutdown
ip address 130.10.100.1 255.255.255.0
isis enable 100
isis silent
#
interface LoopBack0
ip address 9.9.9.9 255.255.255.255
isis enable 1000
#
ip address 200.0.100.9 255.255.255.255
#
Tunnel0/0/97
destination 7.7.7.7
mpls te commit
#
destination 8.8.8.8
mpls te commit
#
mpls te commit
#
snmp-agent


#
ssh user root
#
#
tunnel-policy IPRAN
#
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#
//(when the NE is connected to the U2000 through an L2 network) Configure a routing
policy and route importing
#
#
#
#

#
#
ip route-static vpn-instance __dcn_ideal__ 130.10.100.0 255.255.255.0 123.1.2.2
description dcn-ideal

#
#
10
#
20
#
#
idle-timeout 5 0
#
#
sysname CX600-X8-MASG2-002
#
#
ftp client-source -a 10.10.10.10
#
#
bfd
#
mpls lsr-id 10.10.10.10
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls te cspf
#
#
#

#
mpls ldp
#
aaa
#
#
#
domain default0
domain default1
#
#
ipv4-family
#
isis 1000
is-level level-2
cost-style wide
flash-flood level-2
network-entity 49.0003.0100.1001.0010
is-name MASG2
timer spf 1 50 50
traffic-eng level-2
log-peer-change
#
interface Eth-trunk 1
#
vlan-type dot1q 1
undo shutdown
ip address 10.9.10.2 255.255.255.252
isis enable 1000
isis cost 25
isis ldp-sync
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
qos phb disable
#
undo shutdown
ip address 10.7.9.2 255.255.255.252
#

undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
undo shutdown
ip address 130.10.100.2 255.255.255.0
isis enable 1000
isis silent
#
Tunnel0/0/108
destination 8.8.8.8
mpls te commit
#
destination 7.7.7.7
mpls te commit
#
destination 9.9.9.9
mpls te commit
#
interface LoopBack0
ip address 10.10.10.10 255.255.255.255
isis enable 1000
#
snmp-agent
#


ssh user root
#
#
tunnel-policy IPRAN
#
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
min-tx-interval 10
min-rx-interval 10
process-pst
commit
#
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#
min-tx-interval 50
min-rx-interval 50
process-pst
commit
#

#
#
#
#
#
#
ip route-static vpn-instance __dcn_ideal__ 130.10.100.0 255.255.255.0 123.1.2.2
description dcn-ideal


#
#
10
#
20
#
#
lldp enable
#
idle-timeout 5 0
#
11.1.2 BGP LSP Configuration File (HVPN+Labeled BGP)


Labeled iBGP
Labeled eBGP
RR1 changes the next changes the next RR3

hop to itself hop to itself

changes the next changes the next
hop to itself hop to itself RR4
RR2
TE/LDP Label
upstream
BGP Label push swap swap POP

downstream
POP swap swap push
BGP Label
CSG1 requires no configuration.
#
tunnel-selector IPRAN permit node 10
#
bfd
mpls-passive
#
mpls
mpls bgp bfd enable
#
bgp 100
router-id 3.3.3.3

#
ipv4-family unicast
network 3.3.3.3 255.255.255.255
auto-frr
#
#
apply cost 100
apply mpls-label
#
apply cost 100
apply mpls-label
#
#
#
bfd
mpls-passive
#
mpls
mpls bgp bfd enable
#
bgp 100
router-id 4.4.4.4
#
ipv4-family unicast
network 4.4.4.4 255.255.255.255
auto-frr
#
#
apply cost 100
apply mpls-label
#

apply cost 100

apply mpls-label
#
11.1.2.4 (Aggregation Layer) RR1 Configuration File
#
bfd
mpls-passive
#
bgp 100
router-id 11.11.11.11
#
ipv4-family unicast
peer 3.3.3.3 enable
peer 4.4.4.4 enable
peer 5.5.5.5 enable
peer 6.6.6.6 enable
#
#
bfd
mpls-passive
#
bgp 100
router-id 12.12.12.12
#
ipv4-family unicast

peer 3.3.3.3 enable
peer 4.4.4.4 enable
peer 5.5.5.5 enable
peer 6.6.6.6 enable
#
#
#
bgp 100
router-id 5.5.5.5
#
ipv4-family unicast
network 11.11.11.11 255.255.255.255
network 12.12.12.12 255.255.255.255
auto-frr
#
#
if-match mpls-label
apply mpls-label
#
if-match mpls-label
if-match ip-prefix ASG3
apply cost 50
apply mpls-label
#
if-match mpls-label
apply cost 100
apply mpls-label
#


apply cost 50
apply mpls-label
#
if-match cost 50
if-match mpls-label
apply cost 200
apply mpls-label
#
if-match mpls-label
apply mpls-label
#
route-policy prefer permit node 10
32768
#
#
#
#
bgp 100
router-id 6.6.6.6
#
ipv4-family unicast
network 11.11.11.11 255.255.255.255
network 12.12.12.12 255.255.255.255
auto-frr
#
#
if-match mpls-label
apply mpls-label
#
if-match mpls-label
apply cost 100
apply mpls-label
#


if-match mpls-label
apply cost 50
apply mpls-label
#
apply cost 100
apply mpls-label
#
#
if-match cost 50
if-match mpls-label
apply cost 200
apply mpls-label
#
if-match mpls-label
apply mpls-label
#
#
#
#
bgp 200
router-id 7.7.7.7
#
ipv4-family unicast
network 13.13.13.13 255.255.255.255
network 14.14.14.14 255.255.255.255
auto-frr
#
#
if-match mpls-label
apply mpls-label
#

if-match mpls-label
apply cost 50
apply mpls-label
#
if-match mpls-label
apply cost 100
apply mpls-label
#
apply cost 50
apply mpls-label
#
if-match cost 50
if-match mpls-label
apply cost 200
apply mpls-label
#
if-match mpls-label
apply mpls-label
#
#
#
#
#
bgp 200
router-id 8.8.8.8
#
ipv4-family unicast
network 13.13.13.13 255.255.255.255
network 14.14.14.14 255.255.255.255
auto-frr
#
#


if-match mpls-label
apply mpls-label
#
if-match mpls-label
apply cost 100
apply mpls-label
#
if-match mpls-label
apply cost 50
apply mpls-label
#
apply cost 100
apply mpls-label
#
#
if-match cost 50
if-match mpls-label
apply cost 200
apply mpls-label
#
if-match mpls-label
apply mpls-label
#
#
#
bfd
mpls-passive
#
bgp 200
router-id 13.13.13.13
#
ipv4-family unicast
peer 7.7.7.7 enable
peer 8.8.8.8 enable
peer 9.9.9.9 enable


#
#
bfd
mpls-passive
#
bgp 200
router-id 14.14.14.14
#
ipv4-family unicast
peer 7.7.7.7 enable
peer 8.8.8.8 enable
peer 9.9.9.9 enable
#
#
#
bfd
mpls-passive
#
mpls
mpls bgp bfd enable
#
bgp 200
router-id 9.9.9.9
#

ipv4-family unicast
network 9.9.9.9 255.255.255.255
auto-frr
#
#
apply mpls-label
#
#
#
bfd
mpls-passive
#
mpls
mpls bgp bfd enable
#
bgp 200
router-id 10.10.10.10
#
ipv4-family unicast
network 10.10.10.10 255.255.255.255
auto-frr
#
#
apply mpls-label
#
11.1.3 BGP LSP Configuration File (Labeled BGP to Edge)


Labeled iBGP
Labeled eBGP
changes the next RR1 changes the next changes the next RR3
hop to itself hop to itself hop to itself

changes the next changes the next changes the next
hop to itself hop to itself hop to itself RR4
RR2
TE/LDP Label
Upstream
BGP Label
push swap swap swap POP
iBGP LSP iBGP LSP eBGP LSP iBGP LSP
Downstream
swap
swap swap push
POP iBGP LSP iBGP LSP
eBGP LSP
BGP Label
#
#
bfd
mpls-passive
#
mpls
mpls bgp bfd enable
#
bgp 100
router-id 1.1.1.1
#
ipv4-family unicast
network 1.1.1.1 255.255.255.255

auto-frr
peer 3.3.3.3 enable
peer 4.4.4.4 enable
#
#
apply mpls-label
#
apply mpls-label
#
#
#
bgp 100
router-id 3.3.3.3
group CSG internal
#
ipv4-family unicast
auto-frr
peer CSG enable
peer 1.1.1.1 enable
#
#

if-match mpls-label
csg
apply mpls-label
#
if-match cost 50
if-match mpls-label
if-match community-filter csg
apply cost 200
apply mpls-label
#
apply cost 50
#
if-match mpls-label
apply cost 50
apply mpls-label
#
if-match mpls-label
apply cost 100
apply mpls-
label
#
#
#
#
bgp 100
router-id 4.4.4.4
group CSG internal
#
ipv4-family unicast
auto-frr


peer CSG enable
peer 1.1.1.1 enable
#
#

if-match mpls-label
apply mpls-label
#
if-match cost 100
if-match mpls-label
apply mpls-label
#

apply cost 100
#
if-match mpls-label
apply cost 100
apply mpls-label
#
if-match mpls-label
apply cost 50
apply mpls-label
#
#
#
bfd
mpls-passive
#
bgp 100
router-id 11.11.11.11


#
ipv4-family unicast
peer 3.3.3.3 enable
peer 4.4.4.4 enable
peer 5.5.5.5 enable
peer 6.6.6.6 enable
#
#
bfd
mpls-passive
#
bgp 100
router-id 12.12.12.12
#
ipv4-family unicast
peer 3.3.3.3 enable
peer 4.4.4.4 enable
peer 5.5.5.5 enable
peer 6.6.6.6 enable
#

#
#
bgp 100
router-id 5.5.5.5
#
ipv4-family unicast
network 11.11.11.11 255.255.255.255
network 12.12.12.12 255.255.255.255
auto-frr
#
#
if-match mpls-label
apply mpls-label
#
if-match mpls-label
apply cost 50
apply mpls-label
#
if-match mpls-label
apply cost 100
apply mpls-label
#
apply cost 50
apply mpls-label
#
if-match cost 50
if-match mpls-label
apply cost 200
apply mpls-label
#
if-match mpls-label
apply mpls-label
#

32768
#
#
#
#
bgp 100
router-id 6.6.6.6
#
ipv4-family unicast
network 11.11.11.11 255.255.255.255
network 12.12.12.12 255.255.255.255
auto-frr
#
#
if-match mpls-label
apply mpls-label
#
if-match mpls-label
apply cost 100
apply mpls-label
#
if-match mpls-label
apply cost 50
apply mpls-label
#
apply cost 100
apply mpls-label
#
#
if-match cost 50
if-match mpls-label

apply cost 200

apply mpls-label
#
if-match mpls-label
apply mpls-label
#
#
#
#
bgp 200
router-id 7.7.7.7
#
ipv4-family unicast
network 13.13.13.13 255.255.255.255
network 14.14.14.14 255.255.255.255
auto-frr
#
#
if-match mpls-label
apply mpls-label
#
if-match mpls-label
apply cost 50
apply mpls-label
#
if-match mpls-label
apply cost 100
apply mpls-label
#
apply cost 50
apply mpls-label
#

if-match cost 50
if-match mpls-label
apply cost 200
apply mpls-label
#
if-match mpls-label
apply mpls-label
#
#
#
#
#
bgp 200
router-id 8.8.8.8
#
ipv4-family unicast
network 13.13.13.13 255.255.255.255
network 14.14.14.14 255.255.255.255
auto-frr
#
#
if-match mpls-label
apply mpls-label
#
if-match mpls-label
apply cost 100
apply mpls-label
#
if-match mpls-label
apply cost 50
apply mpls-label
#


apply cost 100
apply mpls-label
#
#
if-match cost 50
if-match mpls-label
apply cost 200
apply mpls-label
#
if-match mpls-label
apply mpls-label
#
#
#
bfd
mpls-passive
#
bgp 200
router-id 13.13.13.13
#
ipv4-family unicast
peer 7.7.7.7 enable
peer 8.8.8.8 enable
peer 9.9.9.9 enable
#
#
bfd
mpls-passive
#
bgp 200

router-id 14.14.14.14
#
ipv4-family unicast
peer 7.7.7.7 enable
peer 8.8.8.8 enable
peer 9.9.9.9 enable
#
#
#
bfd
mpls-passive
#
mpls
mpls bgp bfd enable
#
bgp 200
router-id 9.9.9.9
#
ipv4-family unicast
network 9.9.9.9 255.255.255.255
auto-frr
#
#

apply mpls-label
#
#
#
bfd
mpls-passive
#
mpls
mpls bgp bfd enable
#
bgp 200
router-id 10.10.10.10
#
ipv4-family unicast
network 10.10.10.10 255.255.255.255
auto-frr
#
#
apply mpls-label
#
11.2 E2E Mobile Backhaul Services Configuration File

(HVPN+Labeled BGP)


LTE S1 service
L3VPN L3VPN
RR1 RR3

RR4
RR2
VPNv4
11.2.1 CSG1 Configuration File

#
ipv4-family
tnl-policy IPRAN
#
undo dcn
#
vlan-type dot1q 10
ip address 192.168.1.1 255.255.255.0
#
bgp 100
router-id 1.1.1.1
#
ipv4-family unicast
#
ipv4-family vpnv4
policy vpn-target
peer 3.3.3.3 enable
peer 4.4.4.4 enable
#
import-route direct

import-route static
#
peer 3.3.3.3 enable
peer 4.4.4.4 enable
#
#
#
ip route-static vpn-instance LTE-RAN 120.16.1.2 255.255.255.255 192.168.1.2
#
11.2.2 ASG3 Configuration File

#
ipv4-family
tnl-policy IPRAN
transit-vpn
#
#
bgp 100
group CSG internal
#
ipv4-family unicast
#
ipv4-family vpnv4
auto-frr
peer CSG enable
peer 1.1.1.1 enable
#
peer 1.1.1.1 enable
#

apply cost 103

#
apply cost 103
#
route-policy from-csg-as-master permit node 10
apply cost 103
#
route-policy vpnv4-from-MRR permit node 10
#
10
#

100
#
10
#
20
if-match cost 103
apply cost 503
#
100
#
#

#
ipv4-family
tnl-policy IPRAN
transit-vpn
#
#
bgp 100
group CSG internal
#
ipv4-family unicast

#
ipv4-family vpnv4
auto-frr
peer CSG enable
peer 1.1.1.1 enable
#
peer 1.1.1.1 enable
#
apply cost 203
#
apply cost 203
#
apply cost 203
#
#
10
#
100
#
10
#
20
if-match cost 103
apply cost 503
#
100
#
#
#

11.2.4 (Aggregation Layer) RR1 Configuration File

#
bgp 100
#
ipv4-family unicast
#
ipv4-family vpnv4
peer 3.3.3.3 enable
peer 4.4.4.4 enable
#

#
bgp 100
#
ipv4-family unicast
#
ipv4-family vpnv4
peer 3.3.3.3 enable
peer 4.4.4.4 enable
#
11.2.6 (Core Layer) RR3 Configuration File

#
bgp 200
#
ipv4-family unicast


#
ipv4-family vpnv4
peer 11.11.11.11 route-policy vpnv4_epc_x2 export
peer 9.9.9.9 enable
#
#
#

#
bgp 200
#
ipv4-family unicast
#
ipv4-family vpnv4
peer 9.9.9.9 enable
#
#
#
11.2.8 MASG1 Configuration File

#
vlan 100
#

vrrp recover-delay 60
#
ipv4-family
tnl-policy IPRAN
#
portswitch
#
interface Vlanif 100
ip address 192.168.2.1 255.255.255.0
#
portswitch
undo shutdown
undo dcn
#
bgp 200
router-id 9.9.9.9
#
ipv4-family vpnv4
policy vpn-target
#
#
#
10
apply cost 103
#
10
apply cost 203
#
route-policy vpnfrr permit node 10
#
10


#
#
10
#
20
if-match cost 103
apply cost 503
#
#
apply cost 103
#
apply cost 203
#
#
#
#
ip ip-prefix EPC-Master index 10 permit 12.12.12.0 24 greater-equal 24 less-equal
32
ip ip-prefix EPC-Slave index 10 permit 12.12.13.0 24 greater-equal 24 less-equal
32
#
description TO EPC
#
bfd vrrp bind peer-ip 192.168.2.2 vpn-instance LTE-RAN interface Vlanif100 source-
ip 192.168.2.1
min-tx-interval 50
min-rx-interval 50
commit
#

#
vlan 100
#
#
ipv4-family
tnl-policy IPRAN

#
portswitch
#
ip address 192.168.2.2 255.255.255.0
#
portswitch
undo shutdown
undo dcn
#
bgp 200
router-id 10.10.10.10
#
ipv4-family vpnv4
policy vpn-target
#
#
#
10
apply cost 103
#
10
apply cost 203
#
#
10
#
#
10
#
20
if-match cost 103
apply cost 503

#
#
apply cost 203
#
apply cost 103
#
#
#
#
32
32
#
description TO EPC
#
ip 192.168.2.2
min-tx-interval 50
min-rx-interval 50
commit
#
11.3 E2E Mobile Backhaul Services Configuration File



LTE S1 service
L3VPN
RR1 RR3

RR4
RR2
VPNv4

#
ipv4-family
tnl-policy IPRAN
#
vlan-type dot1q 10
ip address 192.168.1.1 255.255.255.0
#
bgp 100
#
ipv4-family vpnv4
policy vpn-target
peer 3.3.3.3 enable
peer 4.4.4.4 enable
#
import-route direct
import-route static
#
#
#
ip route-static vpn-instance LTE-RAN 120.16.1.2 255.255.255.255 192.168.1.2
#
#
bgp 100

#
ipv4-family vpnv4
peer CSG enable
peer 1.1.1.1 enable
#
#
apply cost 103
#
apply cost 103
#
route-policy from-csg-as-master permit node 10
apply cost 103
#
#
#
#
15
#
#
ip community-filter basic csg-vpn permit 11:11 //Defines the community attribute
table for identifying CSG-side private network VPNv4 routes.
#
#
bgp 100
#
ipv4-family vpnv4


peer CSG enable
peer 1.1.1.1 enable
#
#
apply cost 203
#
apply cost 203
#
apply cost 203
#
#
#
#
15
#
#
#
ip community-filter basic csg-vpn permit 11:11 //Defines the community attribute
table for identifying CSG-side private network VPNv4 routes.
#

#
bgp 100
#
ipv4-family unicast
#

ipv4-family vpnv4
peer 3.3.3.3 enable
peer 4.4.4.4 enable
#

#
bgp 100
#
ipv4-family unicast
#
ipv4-family vpnv4
peer 3.3.3.3 enable
peer 4.4.4.4 enable
#

#
bgp 200
#
ipv4-family unicast
#
ipv4-family vpnv4
peer 9.9.9.9 enable


#
#
#

#
bgp 200
#
ipv4-family unicast
#
ipv4-family vpnv4
peer 9.9.9.9 enable
#
#
#

#
vlan 100
#
#
ipv4-family
tnl-policy IPRAN
#

portswitch
#
ip address 192.168.2.1 255.255.255.0
#
portswitch
undo shutdown
undo dcn
#
bgp 200
router-id 9.9.9.9
#
ipv4-family vpnv4
policy vpn-target
#
#
#
10
apply cost 103
#
10
apply cost 203
#
#
10
#
#
10
#
20
if-match cost 103
apply cost 503
#

#
apply cost 103
#
apply cost 203
#
#
#
#
32
32
#
description TO EPC
#
ip 192.168.2.1
min-tx-interval 50
min-rx-interval 50
commit
#

#
vlan 100
#
#
ipv4-family
tnl-policy IPRAN
#
portswitch
#
ip address 192.168.2.2 255.255.255.0
#

portswitch
undo shutdown
undo dcn
#
bgp 200
router-id 10.10.10.10
#
ipv4-family vpnv4
policy vpn-target
#
#
#
10
apply cost 103
#
10
apply cost 203
#
#
10
#
#
10
#
20
if-match cost 103
apply cost 503
#
#
apply cost 203
#
apply cost 103

#
#
#
#
32
32
#
description TO EPC
#
ip 192.168.2.2
min-tx-interval 50
min-rx-interval 50
commit
#
11.4 Local Switching Ethernet Service Configuration File

(HVPN+Labeled BGP)
In this example, the same VPN instance is created for LTE X2 and LTE S1 services. VPN FRR
is configured. In addition, configure the network to prevent black hole routes.

#
ipv4-family
vpn-target 1:1 200:1 import-extcommunity
#
vlan-type dot1q 100
ip binding vpn-instance LTE-RAN/
ip address 192.168.3.1 255.255.255.0
#

#
ipv4-family
tnl-policy IPRAN
#
bgp 100
network 0.0.0.0 route-policy preferred-value

#
#
route-policy preferred-value permit node 10
#
ip route-static vpn-instance LTE-RAN 0.0.0.0 0 192.168.21.21
#

#
ipv4-family
tnl-policy IPRAN
#
bgp 100
network 0.0.0.0 route-policy preferred-value
#
#
route-policy preferred-value permit node 10
#
ip route-static vpn-instance LTE-RAN 0.0.0.0 0 192.168.21.21
#

#
interface LoopBack5
ip address 192.168.21.21 255.255.255.255
#
ip ip-prefix EPC-Master index 30 permit 192.168.21.21 32
#

#
interface LoopBack5
ip address 192.168.21.21 255.255.255.255
#
ip ip-prefix EPC-Master index 30 permit 192.168.21.21 32
#
11.5 Local Switching Ethernet Service Configuration File


In this example, the same VPN instance is created for LTE X2 and LTE S1 services.

#
ipv4-family
vpn-target 1:1 100:1 export-extcommunity //Adds an RT value for the exported VPN
routes to home them to ASG pair 1 (ASG3 and ASG4),
so that the CSGs homed to ASG pair 5
(ASG53 and ASG54) can receive the routes.
vpn-target 1:1 1:5 200:1 import-extcommunity
#
vlan-type dot1q 100
ip address 192.168.3.1 255.255.255.0
#
#
bgp 100
#
ipv4-family unicast
peer CSG enable
peer 1.1.1.1 enable
#
#
ip community-filter basic access1 permit 1:1
ip community-filter basic access50 permit 1:50 //Allows the receiving of routes
from CSG50.
#
apply cost 50
#
if-match mpls-label
apply cost 50
apply mpls-label
#
if-match mpls-label
apply cost 100
apply mpls-label
#
if-match mpls-label
apply cost 100
apply mpls-label
#


#
#
bgp 100
#
ipv4-family unicast
peer CSG enable
peer 1.1.1.1 enable
#
#
ip community-filter basic access1 permit 1:1
ip community-filter basic access50 permit 1:50 //Allows the receiving of routes
from CSG50.
#
apply cost 100
#
if-match mpls-label
apply cost 100
apply mpls-label
#
if-match mpls-label
apply cost 50
apply mpls-label
#
if-match mpls-label
apply cost 50
apply mpls-label
#
#
11.6 P2P Enterprise Service (HVPN+Labeled BGP)

Configuration File
11.6.1 Ethernet Service


IPRAN IPRAN
AS 200
AS 100 AS 300
Primary

CSG2 CSG32
Secondary

LSP
swap swap swap swap
iBGP LSP
MS-PW MS-PW MS-PW
11.6.1.1 (IPRAN AS100) CSG1 Configuration File
#
mpls ldp
#
remote-ip 3.3.3.3
#
remote-ip 4.4.4.4
#
mpls l2vpn
#
pw-template eth
control-word
tnl-policy IPRAN
#
interface
vlan-type dot1q
11
mpls l2vc 3.3.3.3 pw-template eth

500
secondary
mpls l2vpn redundancy master
mpls l2vpn reroute delay 500
mpls l2vpn stream-dual-receiving
#
min-tx-interval 150
min-rx-interval 150
commit
#

11.6.1.2 (IPRAN AS100) ASG3 Configuration File
#
mpls ldp
#
remote-ip 1.1.1.1
#
remote-ip 33.33.33.33
#
mpls l2vpn
#
mpls switch-l2vc 33.33.33.33 502 tunnel-policy IPRAN between 1.1.1.1 500 tunnel-
policy IPRAN encapsulation vlan control-word-transparent
#
#
mpls ldp
#
remote-ip 1.1.1.1
#
remote-ip 34.34.34.34
#
mpls l2vpn
#
#
#
mpls ldp
#
remote-ip 31.31.31.31
#
remote-ip 3.3.3.3
#
mpls l2vpn
#
#
#
mpls ldp
#
remote-ip 31.31.31.31

#
remote-ip 4.4.4.4
#
mpls l2vpn
#
#
#
mpls ldp
#
remote-ip 33.33.33.33
#
remote-ip 34.34.34.34
#
mpls l2vpn
#
pw-template
eth
control-word
tnl-policy IPRAN
#
interface
vlan-type dot1q
11
mpls l2vc 33.33.33.33 pw-template eth

504
secondary
mpls l2vpn redundancy
master
mpls l2vpn reroute delay

500

#
min-tx-interval 150
min-rx-interval 150
commit
#
11.6.2 TDM Service



IPRAN IPRAN
AS 200
AS 100 AS 300
Primary

CSG2 CSG32
Secondary

LSP
swap swap swap swap
iBGP LSP
MS-PW MS-PW MS-PW
#
mpls ldp
#
remote-ip 3.3.3.3
#
remote-ip 4.4.4.4
#
mpls l2vpn
#
pw-template tdm
control-word
tnl-policy IPRAN
jitter-buffer depth 4
tdm-encapsulation-number 8
#
controller E1 0/2/3
using e1
#
link-protocol tdm
mpls l2vc 3.3.3.3 pw-template tdm 1000
mpls l2vc 4.4.4.4 pw-template tdm 1001 secondary
mpls l2vpn oam-mapping
#
min-tx-interval 150
min-rx-interval 150
commit
#

#
mpls ldp
#
remote-ip 1.1.1.1
#
remote-ip 33.33.33.33
#
mpls l2vpn
#
policy IPRAN encapsulation satop-e1 control-word-transparent
#
#
mpls ldp
#
remote-ip 1.1.1.1
#
remote-ip 34.34.34.34
#
mpls l2vpn
#
#
#
mpls ldp
#
remote-ip 31.31.31.31
#
remote-ip 3.3.3.3
#
mpls l2vpn
#
#
#
mpls ldp
#
remote-ip 31.31.31.31
#
remote-ip 4.4.4.4

#
mpls l2vpn
#
#
#
mpls ldp
#
remote-ip 33.33.33.33
#
remote-ip 34.34.34.34
#
mpls l2vpn
#
pw-template tdm
control-word
tnl-policy IPRAN
#
controller E1 0/2/3
using e1
#
link-protocol tdm
mpls l2vc 34.34.34.34 pw-template tdm 1005 secondary
#
min-tx-interval 150
min-rx-interval 150
commit
#
11.7 P2P Enterprise Service (Labeled BGP to Edge)

Configuration File
11.7.1 Ethernet Service



IPRAN IPRAN
AS 200
AS 100 AS 300
SS-PW

IGP domain
CSG2 CSG32

LSP
to Edge iBGP LSP
SS-PW
#
mpls ldp
#
remote-ip 31.31.31.31
#
mpls l2vpn
#
pw-template eth
control-word
tnl-policy IPRAN
#
vlan-type dot1q 12
#
#
#
if-match mpls-label
apply mpls-label
#
#
#
if-match mpls-label

apply mpls-label
#
#
#
if-match mpls-label
apply mpls-label
#
#
#
if-match mpls-label
apply mpls-label
#
#
mpls ldp
#
remote-ip 1.1.1.1
#
mpls l2vpn
#
pw-template
eth
control-word
tnl-policy IPRAN
#
vlan-type dot1q 12
#
11.7.2 TDM Service



IPRAN IPRAN
AS 200
AS 100 AS 300
SS-PW

IGP domain
CSG2 CSG32

LSP
to Edge iBGP LSP
SS-PW

#
mpls ldp
#
remote-ip 31.31.31.31
#
mpls l2vpn
#
pw-template tdm
control-word
tnl-policy IPRAN
#
controller E1 0/2/3
using e1
#
link-protocol tdm
#

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

#

#
if-match mpls-label
apply mpls-label
#
#
#
if-match mpls-label
apply mpls-label
#
#
#
if-match mpls-label
apply mpls-label
#
#
mpls ldp
#
remote-ip 1.1.1.1
#
mpls l2vpn
#
pw-template tdm
control-word
tnl-policy IPRAN
#
controller E1 0/2/3
using e1
#
link-protocol tdm
#
11.8 MP2MP Enterprise Service (HVPN+Labeled BGP)

Configuration File

In the HVPN+Labeled BGP sub-solution, the H-VPLS (VLLs for VPLS) solution is used to
carry MP2MP L2 enterprise services.

IPRAN IPRAN
AS 200
AS 100 AS 300
Access layer Access layer

Enterprise
CSG1 ASG3 ASBR 1 ASBR 3 Core
layer ASBR5 ASBR7 ASG33 CSG31 Enterprise
customer
Aggregation layer IGP domain Aggregation layer customer
Enterprise CSG2 CSG

customer

LSP swap
swap swap swap
HVPN+Labeled iBGP LSP
eBGP LSP
eBGP LSP iBGP LSP
BGPsolution iBGP LSP
VPNswap VPNswap
VLL VPLS VLL
11.8.1 (IPRAN AS100) CSG1 Configuration File

#
mpls ldp
#
remote-ip 3.3.3.3
#
remote-ip 4.4.4.4
#
mpls l2vpn
#
undo dcn
#
undo shutdown
vlan-type dot1q 600
mpls l2vc 3.3.3.3 601 tunnel-policy IPRAN
mpls l2vc 4.4.4.4 602 tunnel-policy IPRAN secondary
#
auto-calculate
min-tx-interval 50
min-rx-interval 50
commit
#

#
mpls ldp

#
remote-ip 3.3.3.3
#
remote-ip 4.4.4.4
#
mpls l2vpn
#
undo dcn
#
undo shutdown
vlan-type dot1q 600
#
auto-calculate
min-tx-interval 50
min-rx-interval 50
commit
#
11.8.3 (IPRAN AS100) ASG3 Configuration File

#
mpls ldp
#
remote-ip 1.1.1.1
#
remote-ip 2.2.2.2
#
remote-ip 4.4.4.4
#
remote-ip 33.33.33.33
#
remote-ip 34.34.34.34
#
mpls
l2vpn
#
vsi vsi_600 static
pwsignal ldp
vsi-id 600
mac-withdraw enable
ignore-ac-state
isolate spoken
#

auto-calculate
min-tx-interval 50
min-rx-interval 50
commit
#
auto-calculate
min-tx-interval 50
min-rx-interval 50
commit
#

#
mpls ldp
#
remote-ip 1.1.1.1
#
remote-ip 2.2.2.2
#
remote-ip 3.3.3.3
#
remote-ip 33.33.33.33
#
remote-ip 34.34.34.34
#
mpls
l2vpn
#
vsi vsi_600 static
pwsignal ldp
vsi-id 600
mac-withdraw enable
ignore-ac-state
isolate spoken
#

#
mpls ldp
#
mmpls ldp remote-peer 31.31.31.31
remote-ip 31.31.31.31
#

remote-ip 34.34.34.34
#
remote-ip 3.3.3.3
#
remote-ip 4.4.4.4
#
mpls
l2vpn
#
vsi vsi_600 static
pwsignal ldp
vsi-id 600
mac-withdraw enable
ignore-ac-state
isolate spoken
#
bfd pw_605 bind pw vsi vsi_600 peer 31.31.31.31 vc-id 605 remote-peer 31.31.31.31
pw-ttl auto-calculate
min-tx-interval 50
min-rx-interval 50
commit
#

#
mpls ldp
#
remote-ip 31.31.31.31
#
remote-ip 33.33.33.33
#
remote-ip 3.3.3.3
#
remote-ip 4.4.4.4
#
mpls
l2vpn
#
vsi vsi_600 static
pwsignal ldp
vsi-id 600
mac-withdraw enable
ignore-ac-state
isolate spoken
#


#
mpls ldp
#
remote-ip 33.33.33.33
#
remote-ip 34.34.34.34
#
mpls l2vpn
#
undo dcn
#
undo shutdown
vlan-type dot1q 600
#
bfd pw_605 bind pw interface GigabitEthernet0/2/19.600 remote-peer 33.33.33.33 pw-
ttl auto-calculate
min-tx-interval 50
min-rx-interval 50
commit
#
11.9 MP2MP Enterprise Service (Labeled BGP to Edge)

Configuration File
The VPLS solution is adopted for MP2MP L2 enterprise services.

IPRAN IPRAN
AS 200
AS 100 AS 300
Enterprise ASG
CSG1 ASG ASBR 1 ASBR 3 ASBR5 ASBR 1 CSG31
customer Access layer Aggregation layer Access layer Enterprise
Aggregation layer Core layer
IGP domain IGP domain IGP domain customer
Enterprise CSG2 CSG32

ASG ASBR 2 ASBR 4 ASBR6 ASBR 2 ASG
customer

LSP swap
swap swap swap
Labeled BGP BGP LSP BGP LSP
BGP LSP
to Edge iBGP LSP
VPLS
VPN TE / LDP LSP TE/ LDP LSP BGP LSP TE/ LDP LSP BGP LSP TE/ LDP LSP TE / LDP LSP


#
mpls ldp
#
remote-ip 2.2.2.2
#
remote-ip 31.31.31.31
#
remote-ip 32.32.32.32
#
mpls l2vpn
#
vsi vsi_700 static
pwsignal ldp
vsi-id 700
#
vlan-type dot1q 700
#

#
mpls ldp
#
remote-ip 1.1.1.1
#
remote-ip 31.31.31.31
#
remote-ip 32.32.32.32
#
mpls l2vpn
#
vsi vsi_700 static
pwsignal ldp
vsi-id 700
#
vlan-type dot1q 700
#

#
mpls ldp
#
remote-ip 1.1.1.1

#
remote-ip 2.2.2.2
#
remote-ip 32.32.32.32
#
mpls l2vpn
#
vsi vsi_700 static
pwsignal ldp
vsi-id 700
#
vlan-type dot1q 700
#

#
mpls ldp
#
remote-ip 1.1.1.1
#
remote-ip 2.2.2.2
#
remote-ip 31.31.31.31
#
mpls l2vpn
#
vsi vsi_700 static
pwsignal ldp
vsi-id 700
#
vlan-type dot1q 700
#


MBB V600R005C00 ATN+CX IDEAL (Seamless MPLS) Solution Configuration Guide (CLI) 03-C

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MBB V600R005C00 ATN+CX IDEAL (Seamless MPLS) Solution Configuration Guide (CLI) 03-C

Uploaded by

Copyright:

Available Formats

MBB ATN+CX IDEAL(Seamless MPLS) Solution

Configuration Guide (CLI)

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 03 (2014-10-20) Huawei Proprietary and Confidential i

About This Document

This document is intended for the following readers:

l Network planning engineers

Issue 03 (2014-10-20) Huawei Proprietary and Confidential ii

Issue 03 (2014-10-20) Huawei Proprietary and Confidential iii

About This Document.....................................................................................................................ii

5 Deploying MPLS tunnel (RSVP TE and LDP)......................................................................31

6 Deploying MPLS Tunnels (BGP LSPs)...................................................................................61

Issue 03 (2014-10-20) Huawei Proprietary and Confidential iv

6.1.1 MPLS Tunnel Deployment Solution.........................................................................................................................62

8 Deploying Mobile Backhaul Services...................................................................................130

Issue 03 (2014-10-20) Huawei Proprietary and Confidential v

8.3.3 Deploying an L3VPN and Protection......................................................................................................................188

9 Deploying Enterprise Services................................................................................................205

Issue 03 (2014-10-20) Huawei Proprietary and Confidential vi

9.4.1 MP2MP Enterprise Service Deployment Solution..................................................................................................249

Issue 03 (2014-10-20) Huawei Proprietary and Confidential vii

11.1.3.8 (Core Layer) ASBR3 Configuration File...........................................................................................................318

Issue 03 (2014-10-20) Huawei Proprietary and Confidential viii

11.6.1.4 (IPRAN AS300) ASG33 Configuration File......................................................................................................346

Issue 03 (2014-10-20) Huawei Proprietary and Confidential ix

About This Chapter

1.1 Service Requirements and Solutions

1.2 Introduction to Products Used in the ATN+CX Bearer Solution

1.3 Network Topology Example and Data Planning for Interfaces

Issue 03 (2014-10-20) Huawei Proprietary and Confidential 1

1.1 Service Requirements and Solutions

The IDEAL solution includes two sub-solutions:

l Sub-solution 1: HVPN+Labeled BGP: Segmented tunnels are deployed. A segment of

Issue 03 (2014-10-20) Huawei Proprietary and Confidential 2

Figure 1-1 HVPN+Labeled BGP sub-solution

Labeled iBGP Labeled eBGP Labeled iBGP

eNodeB CSG ASG ASBR 2 ASBR 4 MASG

TE/LDP TE/LDP TE/LDP

L3VPN swap Inter-AS L3VPN

Figure 1-2 Labeled BGP to Edge sub-solution

Labeled iBGP Labeled iBGP Labeled eBGP Labeled iBGP

eNodeB CSG ASG ASBR 2 ASBR 4 MASG

TE/LDP TE/LDP TE/LDP

LSP LSP LSP

E2E Inter-AS L3VPN

1.2 Introduction to Products Used in the ATN+CX Bearer

Issue 03 (2014-10-20) Huawei Proprietary and Confidential 3

Equipment Role Equipment Model Version

Core Node (P) NE40E-X8/X16 V600R008C00

Core Edge Node (PE) NE40E-X8/X16 V600R008C00

Mobile Aggregation Service CX600-X8/X16

Network Layer Equipment Role Function

User side User equipment (UE) Terminal of a mobile

Base station Base transceiver station BTSs refer to all 2G base

Issue 03 (2014-10-20) Huawei Proprietary and Confidential 4

Network Layer Equipment Role Function

NodeB (3G base station) Refers to a base station on a

eNodeB (E-UTRAN NodeB, Refers to a Long Term

Access network Cell site gateway (CSG) Receives and processes

Aggregation network Aggregation Site Gateway Aggregates service signals

Radio Service Gateway Connects to base station