(For Customer) IPTime MBB Backhaul ATN+CX (Hierarchy VPN) Solution Configuration Guide (0 - 01, CLI)

HUAWEI IPTime MBB Backhaul ATN+CX (Hierarchy
VPN) Solution
V600R001C00
Configuration Guide(CLI)
Issue 01
Date 2011-09-20
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. 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 the 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 01 (2011-09-20) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
VPN) Solution
Configuration Guide(CLI) About This Document
About This Document
Intended Audience
This document describes the roadmap, data planning, and procedure for configuring services in
the ATN+CX mobile broadband (MBB) solution.
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 01 (2011-09-20)
This document is the first release of V600R001C00.
Issue 01 (2011-09-20) Huawei Proprietary and Confidential ii

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

1 Networking Requirements..........................................................................................................1
1.1 Service Requirements and Networking..............................................................................................................2
1.2 Introduction to Products Used in the ATN+CX Carrier Solution......................................................................6
2 Basic Configurations.....................................................................................................................9
2.1 Configuring Device Information......................................................................................................................10
2.2 Configuring Interfaces......................................................................................................................................10
2.3 Configuring AAA Users...................................................................................................................................15
2.4 Configuring User Interfaces.............................................................................................................................15
2.5 Configuring SNMP...........................................................................................................................................16
3 Deploying an IGP........................................................................................................................19
3.1 Configuration Roadmap...................................................................................................................................20
3.2 Data Planning...................................................................................................................................................21
3.3 Configuring Basic IS-IS Functions...................................................................................................................22
3.4 Controlling Route Advertisement and Import..................................................................................................25
4 Deploying MPLS.........................................................................................................................27
4.2 Data Planning...................................................................................................................................................29
4.3 Configuring MPLS TE and Hot Standby.........................................................................................................33
4.4 Configuring Static BFD for TE........................................................................................................................39
4.5 Configuring Static BFD for TE-LSP................................................................................................................41
5 Configuring Ethernet Service Bearer and Protection...........................................................44

5.2 Data Planning...................................................................................................................................................46
5.3 Configuring MP-BGP.......................................................................................................................................49
5.4 Configuring a VPN...........................................................................................................................................51
5.5 Configuring Protection Switching....................................................................................................................54
5.6 Configuring VRRP...........................................................................................................................................56
6 Deploying TDM Service Bearer and Protection....................................................................60

6.2 Data Planning...................................................................................................................................................62
Issue 01 (2011-09-20) Huawei Proprietary and Confidential iii

VPN) Solution
Configuration Guide(CLI) Contents
6.3 Configuring Multi-segment PWs......................................................................................................................65

6.4 Configuring BFD for PW.................................................................................................................................70
6.5 Configuring E-APS...........................................................................................................................................71
7 Deploying ATM Service Bearer and Protection....................................................................73

7.2 Data Planning...................................................................................................................................................75
7.3 Configuring Multi-segment PWs......................................................................................................................78
7.4 Configuring BFD for PW.................................................................................................................................82
7.5 Configuring E-APS...........................................................................................................................................83
8 Deploying QoS.............................................................................................................................85
8.1 Deploying QoS for Ethernet Services..............................................................................................................86
8.1.1 Configuration Roadmap..........................................................................................................................86
8.1.2 Data Planning..........................................................................................................................................86
8.1.3 Configuring Priority Mapping.................................................................................................................87
8.1.4 Configuring Queue Scheduling and Bandwidth......................................................................................88
8.2 Deploying QoS for ATM Services...................................................................................................................89
8.2.1 Configuration Roadmap..........................................................................................................................89
8.2.2 Data Planning..........................................................................................................................................89
8.2.3 Configuring Traffic Shaping...................................................................................................................90
9 Deploying the Clock...................................................................................................................91

9.2 Data Planning...................................................................................................................................................92
9.3 Selecting the Clock Source...............................................................................................................................93
9.4 Configuring Synchronization Ethernet to Achieve Frequency Synchronization.............................................94
9.5 Configuring 1588v2 to Achieve Time Synchronization...................................................................................94
Issue 01 (2011-09-20) Huawei Proprietary and Confidential iv

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

Hierarchy VPN (HVPN) is a bearer mode in the IPTime Mobile Broadband (MBB) ATN+CX
solution. The MBB ATN+CX solution is designed by Huawei for IP Radio Access Networks
(IPRANs).
1.2 Introduction to Products Used in the ATN+CX Carrier Solution
This section describes the roles, functions, and product models of the devices that are used in
the ATN+CX carrier solution, and the network layers where the devices are used.
Issue 01 (2011-09-20) Huawei Proprietary and Confidential 1

VPN) Solution
1.1 Service Requirements and Networking

Hierarchy VPN (HVPN) is a bearer mode in the IPTime Mobile Broadband (MBB) ATN+CX
solution. The MBB ATN+CX solution is designed by Huawei for IP Radio Access Networks
(IPRANs).
Service Requirements
As Third Generation (3G) services and Long Term Extend (LTE) services develop, mobile
operators keep building and expanding RANs. This imposes high requirements on bandwidth,
expansion, and configuration flexibility of the RANs between NodeBs and Radio Network
Controllers (RNCs). IP datacom networks, as the mainstream of datacom networks, are large in
scale and provide a variety of access modes. To maximize carriers' return on investment, reduce
network construction costs, and evolve the exiting network smoothly into an LTE network, an
IPRAN solution is worked out.
In the Hierarchy VPN solution, ATN and CX series products are deployed on a RAN. The RAN
provides excellent Fixed-Mobile Convergence (FMC) capability and has simple and flexible
networking. The hierarchical network between CSGs and RSGs can bear various types of
services. ATN devices function as Cell Site Gateways (CSGs) and are connected to form an
access network. CX600s function as aggregation devices (ASGs) and Remote site gateways
(RSGs) and are connected to form an aggregation network. All these devices can be flexibly
deployed based on 2G, 3G, and LTE service requirements.
Table 1-1 Hierarchy VPN deployment
Solution H-VPN MS-PW
Service l LTE S1/X2 l 3G ATM

l 3G ETH l 2G TDM
IGP Hierarchical IGP needs to be deployed between CSGs and

RSGs to ensure proper data forwarding. Policy-based routing
needs to be configured on ASGs to aggregate and filter routes.
This configuration saves bandwidth used for updating and
maintaining routes.
Recommended routing protocol: IS-IS multi-processes
MPLS tunnel MPLS tunnels need to be established from CSGs to ASGs,

and from ASGs to CSGs.
Recommended tunnel protocol: MPLS TE
VPN Hierarchical L3VPN needs to Multi-hop PW needs to be

be configured between CSGs configured between CSGs
and ASGs, and between and ASGs, and between
ASGs and RSGs to isolate ASGs and RSGs to isolate
services. services.
Protection switching Protection switching needs to be configured for nodes and

links to provide high availability.

VPN) Solution
Solution H-VPN MS-PW
Recommended protection Recommended protection

and detection technologies: and detection technologies:
MPLS TE hot-standby, VPN PW redundancy, BFD, and
FRR, VRRP, BFD, and GR GR
QoS End-to-end QoS needs to be configured between CSGs and

RSGs to ensure service quality.
Recommended QoS solutions: DiffServ and HQoS
Clock synchronization End-to-end clock synchronization needs to be configured

between CSGs and RSGs to ensure real-time data
transmission.
Recommended clock synchronization technologies:
synchronization Ethernet and 1588v2
Network Topology
As shown in Figure 1-1, and Figure 1-2, the network needs to be constructed based on the
topologies; the corresponding network element names, device IP addresses need to be
configured; service interfaces and user interfaces need to be enabled.
NOTE
This example describes the networking of CSG dual-homing to ASGs and the networking of ASG dual-
homing to ASGs. If only single-homing is involved, only the slave device needs to be configured and no
switchover needs to be performed.
Figure 1-1 Network topology

VPN) Solution
Figure 1-2 IP network interface topology
Data Planning
NOTE
Parameters need to be configured based on the real network conditions, such as the network scale and
network topology. The following parameter values are recommended ones in this example and only for
reference.
Table 1-2 NE IP interface list
NE Role Local Interface IP Address Interface

Description
CSG1 (ATN910- Loopback 0 1.1.1.1/32

AA-001)
GigabitEthernet 10.1.2.1/30 Interface description:
0/1/0 To csg2

0/1/1 To asg3
CSG2 (ATN950- Loopback 0 2.2.2.2/32

BB-001)
0/1/0 To csg1

0/1/1 To asg4
ASG3 (CX600- Loopback 0 3.3.3.3/32

CC-001)
1/1/2 To csg1
GigabitEthernet1/1/ 10.3.4.1/30 Interface description:

1.1 vlan-type dot1q 1 To asg4

VPN) Solution
NE Role Local Interface IP Address Interface

Description

1/1/3 To asg4

1/1/0 To rsg5
ASG4 (CX600- Loopback 0 4.4.4.4/32

DD-001)
1/1/2 To csg2
GigabitEthernet1/1/ 10.3.4.2/30 Interface description:

1.1 vlan-type dot1q 1 To asg3

1/1/3 To asg3

1/1/0 To rsg6
RSG5 (CX600- Loopback 0 5.5.5.5/32

EE-001)
1/0/0 To asg3
GigabitEthernet Eth-Trunk 1.1 Interface description:

1/0/1 10.5.6.1/30 To rsg6
GigabitEthernet vlan-type dot1q 1

1/0/3
RSG6 (CX600- Loopback 0 6.6.6.6/32

FF-001)
1/0/0 To asg4
GigabitEthernet Eth-Trunk 1.1 Interface description:

1/0/1 10.5.6.2/30 To rsg5
GigabitEthernet vlan-type dot1q 1

1/0/3
Table 1-3 NE service interface list

NE Role Service Interface Logical Interface Interface
and Address Description
CSG1 (ATN910- Ethernet0/3/0 192.168.100.1/24 Interface description:

AA-001) for eth
Ethernet0/3/1 192.168.101.1/24 Interface description:

for eth

VPN) Solution
NE Role Service Interface Logical Interface Interface

and Address Description
E1 0/2/0 Serial0/2/0:0 Interface description:

for tdm

Ima-group0/2/1.1 for atm

Ima-group0/2/1.1 for atm
RSG5 (CX600- Eth-Trunk 1 VLAN Trunk Interface description:

EE-001) VLANIF100: for trunk
GigabitEthernet
192.168.2.2/24 Interface description:
1/0/2
for eth
Cpos2/0/0 Cpos-Trunk0 Interface description:

Trunk-Serial1/1:0 for tdm
Atm3/0/0 Atm-Trunk1.1 Interface description:

for atm
RSG6 (CX600- Eth-Trunk 1 VLAN Trunk Interface description:

FF-001) VLANIF100: for trunk
GigabitEthernet
192.168.2.3/24 Interface description:
1/0/2
for eth
Cpos2/0/0 Cpos-Trunk0 Interface description:

Trunk-Serial1/1:0 for tdm
Atm3/0/0 Atm-Trunk1.1 Interface description:

for atm
1.2 Introduction to Products Used in the ATN+CX Carrier

Solution
This section describes the roles, functions, and product models of the devices that are used in
the ATN+CX carrier solution, and the network layers where the devices are used.
Network Layer Role Function Product Model
UNI side User equipment (UE) Refers to a terminal -

on a mobile network.

VPN) Solution
Base station Base transceiver Refers to a 2G base -

station (BTS) station. Mobile
communication
systems are
composed of mobile
stations, base station
subsystems (BSSs),
and network
subsystems (NSSs).
BSSs are composed
of BTSs and base
station controllers
(BSCs).
NodeB (3G base Refers to a base -

station) station on a 3G
mobile network.
NodeBs are
interconnected with
radio network
controllers (RNCs)
through standard Iub
ports and
communicate with
UE nodes through
Uu ports, processing
Uu port physical-
layer protocols and
Iub port protocols.
eNodeB (E-UTRAN Refers to an evolved -

NodeB, LTE base form of NodeB or
station) LTE base station.
Access network Cell site gateway Receives and ATN910/950

(CSG) processes various Product
service signals from version:V200R001C
base stations and 00
forwards them to
devices at the
aggregation layer.
Aggregation Aggregation site Aggregates service Quidway CX600

network gateway (ASG) signals from CSGs Product
and forwards them. version:V600R003C
00
Remote site gateway Connects to
(RSG) controllers.

VPN) Solution
Core network (MBB BSC Manages radio -

core) network resources
and cell information,
controls power, and
locates and switches
users.
RNC Refers to a key node -

on a 3G network.
Manages mobility,
processes calls,
manages links, and
switches users on the
access network.
Mobility Refers to a critical -

management entity control node on a
(MME) 3GPP LTE access
network, and locates
UE nodes in idle
mode and processes
calls (including
regeneration).
O&M system Network Operates, manages, iManager U2000

management system and maintains a Product
(NMS) network. version:V100R005C
00

VPN) Solution
Configuration Guide(CLI) 2 Basic Configurations
2 Basic Configurations
About This Chapter
Basic configurations include network environment establishment and user environment

configurations.
2.1 Configuring Device Information
Device information includes site names, device models, device roles, and device numbers.
2.2 Configuring Interfaces
Interfaces and their connectivity need to be configured based on service requirements and
networking.
2.3 Configuring AAA Users
AAA users and user passwords need to be configured for AAA authentication.
2.4 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.
2.5 Configuring SNMP
Configuring SNMP allows devices to communicate with the network management system
(NMS).

VPN) Solution
2.1 Configuring Device Information

Device information includes site names, device models, device roles, and device numbers.
Data Planning
NOTE
The data provided in this section is used as an example and for reference, and may be different from that
in the real world situations, because the network scale and topology may differ.
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-X2

l BB: site 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
2.2 Configuring Interfaces

Interfaces and their connectivity need to be configured based on service requirements and
networking.
Data Planning
NOTE
1. Configure interface description to identify physical links.

The interface description is in the following format: To [Remote device name].For
example:To csg2
2. Configure interconnected interfaces on the IP/MPLS network.

VPN) Solution
l Configure loopback interfaces and their IP addresses on CSGs, ASGs, and RSGs. The
loopback interfaces remain Up after being created, and therefore CSGs, ASGs, and
RSGs can communicate with each other using loopback interfaces.
l Configure interfaces for connecting CSGs, ASGs, and RSGs, and the IP addresses of
these interfaces, so that CSGs, ASGs, and RSGs can communicate with each other.
3. Configure Ethernet service interfaces.
l Configure main interfaces or sub-interfaces as Ethernet service interfaces (including 10
Mbit/s and 100 Mbit/s Ethernet interfaces) based on the access type at the CSG side.
l Configure Layer 2 Etherent interfaces or VLANIF interfaces as Ethernet service
interfaces (including 1000 Mbit/s and 10000 Mbit/s Ethernet interfaces) based on the
access type at the RSG side.
4. Configure TDM service interfaces.
l Configure the TDM-encapsulated E1 channel at the CSG side. You can use either the
E1 channel in clear channel mode or the E1 channel in channelized mode based on
service and bandwidth requirements.
Channel Type Description PW Encapsulation
Type
Clear channel mode Unframed mode: All 32 satop-e1: is a protocol of

(structure-agnostic) timeslots can be used to TDM PWE3. This mode is
transmit valid data. not sensitive to TDM
signal (E1, E3, or other
signals) structures. It
regards data as bit streams
at a fixed rate. These bit
streams are encapsulated
into data packets to be
transmitted over PWs.
Channelized mode l Multiframed mode: cesopsn-basic: is a

(structure-aware) Timeslot 0 and protocol of TDM PWE3.
timeslot 16 are used to The Circuit Emulation
transmit signaling. Service (CES) protocol is
Timeslots 1 to 15 and sensitive to E1 frame
timeslots 17 to 31 are structures. TDM signals
used to transmit valid (E1, E3, or other signals)
data. can be encapsulated into
l Framed mode: packets based on
Timeslot 0 is used to timeslots.
transmit frame
alignment data,
whereas the other 31
timeslots are used to
transmit valid data.
l Configure the TDM-encapsulated VC12 channel on a CPOS interface at the RSG side
based on the E1 channel at the CSG side.
5. Configure ATM service interfaces.
l Configure the ATM-encapsulated E1 channel at the CSG side. You can use only the E1
channel in channelized mode based on service and bandwidth requirements.

VPN) Solution
Channel Type Description PW Encapsulation

Type
Channelized mode l Multiframed mode: l atm-1to1-vcc

(structure-aware) Timeslot 0 and l atm-1to1-vpc
timeslot 16 are used to
transmit signaling. l atm-nto1-vcc
Timeslots 1 to 15 and l atm-nto1-vpc
timeslots 17 to 31 are
used to transmit valid
data.
l Framed mode:
Timeslot 0 is used to
transmit frame
alignment data,
l Add ATM-encapsulated synchronous interfaces to an Inverse Multiplexing over ATM

(IMA) group and create a PVC to an RSG on a sub-interface of the IMA group.
L2VPN provides four types of emulation services for ATM cell relay on serial interfaces
or sub-interfaces of an IMA group.
ATM Cell Relay Description Type of the Sub- Virtual
Mode interface of an Connection
IMA Group
1-to-1 VCC A PW transmits P2P PVC: VPI/VCI

cells of one ATM
VCC.
1-to-1 VPC A PW transmits P2P PVP: VPI

cells of one ATM
VPC.
N-to-1 VCC A PW transmits P2MP PVC: VPI/VCI

cells of multiple
ATM VCCs.
N-to-1 VPC A PW transmits P2MP PVP: VPI

cells of multiple
ATM VPCs.
l Configure the ATM interface at the RSG side based on the PVC created at the CSG
side.

VPN) Solution
CAUTION
l If a physical interface on the device is idle, without a cable being connected, run the
shutdown command to shut down the interface to prevent the interface from being interfered.
l After having configured services on an interface, run the shutdown and undo shutdown
commands in the interface view for the services to take effect.
1. Configure interconnected interfaces on the IP/MPLS network.
l Configure a loopback interface.
interface LoopBack0
ip address 1.1.1.1 255.255.255.255//Configure an IP address for the
loopback interface.
l Configure a GE interface.
interface GigabitEthernet0/1/0
ip address 10.1.2.1 255.255.255.252
l Configure a GE sub-interface.
interface GigabitEthernet1/1/1.1
vlan-type dot1q 1
ip address 10.3.4.1 255.255.255.252
l Configuring layer 2 attributes for an Eth-Trunk interface.

interface Eth-Trunk1
undo shutdown
portswitch//Set the interface to be a switched interface.
#
undo shutdown
eth-trunk 1//Add a specified GE interface to the Eth-Trunk.
#
undo shutdown
eth-trunk 1
NOTE
Before adding a Layer 2 interface on the CX device to an Eth-Trunk interface, you need to run
the undo portswitch command to switch it into a Layer 3 interface.
l Configuring layer 3 attributes for an Eth-Trunk interface.
interface Eth-trunk 1.1
vlan-type dot1q 1
ip address 10.5.6.1 255.255.255.252
2. Configure Ethernet service interfaces.

l Configure a CSG (ATN910/950).
interface Ethernet0/3/0.1
vlan-type dot1q 1
ip address 192.168.100.1 255.255.255.0
l Configure an RSG (CX600).

#Create VLANs.
vlan batch 100
# Add a Layer 2 Eth interface to a VLAN.
portswitch //Set the interface to be a switched interface.
port link-type trunk//Set the link type.
port trunk allow-pass vlan 100
#

VPN) Solution
interface Eth-Trunk1
portswitch
port link-type trunk//Set the link type.
#
interface VLANIF100
VLANIF interface. This IP address must be on a different network segment
with the IP address of the interface at the access side.
3. Configure TDM service interfaces.

# Create a serial interface in E1 clear channel mode and set the link-layer
encapsulation type of the serial interface to TDM.
controller E10/2/0
using e1//Set the CE1 interface to be in clear channel mode.
#
interface Serial0/2/0:0
link-protocol tdm//Set the link-layer encapsulation type of the serial
interface to TDM.

# Configure a CPOS-Trunk interface. Create a serial interface in CPOS-Trunk
clear mode and set the link-layer encapsulation type of the serial interface
to TDM.
controller Cpos2/0/0
cpos-trunk 0//Add a specified CPOS interface to the CPOS-Trunk.
#
interface Cpos-Trunk0
e1 1 unframed//Set the E1 channel of the CPOS-Trunk interface to be in
clear channel mode.
#
interface Trunk-Serial0/1:0
link-protocol tdm
4. Configure ATM service interfaces.

controller E10/2/1
channel-set 0 timeslot-list 1-15,17-31 //Configure a channel set,
excluding timeslots 0 and 16.
frame-format crc4//(Optional) Set the frame format to CRC4.
#
interface Serial0/2/1:0
link-protocol atm//Set the link-layer encapsulation type of the serial
interface to ATM.
ima ima-group0/2/1//Add the serial interface to an IMA group.
#
interface Ima-group0/2/1.1 p2p//Configure ATM cell relay in 1-to-1 VCC mode
on the sub-interface in the IMA group.
pvc 1/100
map pvc 1/100 bidirectional//Configure mappings between the local VPI/VCI
and remote VPI/VCI. (The configuration is only needed on the ATN910/950.)

# Add ATM interfaces to a trunk to create an ATM-Trunk.
interface Atm3/0/0
undo shutdown
atm-trunk 1
#
interface Atm-Trunk1.1 p2p//Create a PVC on the sub-interface in an ATM-
Trunk.
pvc 1/100//Configure mappings between local VPIs/VCIs and remote VPIs/
VCIs.

VPN) Solution
2.3 Configuring AAA Users

AAA users and user passwords need to be configured for AAA authentication.
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.
local-user password USER1 Adds a local user named

USER1.
local-user level 15 Sets a user level for the local

user. The system manages
commands by command
level. A user can use only the
commands whose levels are
lower than or equal to the user
level.
Add a local user named USER1.
aaa
local-user USER1 password cipher 12345678//Set the user name and password.
local-user USER1 level 15//Set a user level.
2.4 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

VPN) Solution
Configure user interfaces on all routers.
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, a router does not allow any
user to log in using 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 Configures AAA

authentication for the users
that log in to a router.
user privilege level 15 Sets the command level to 15.
idle-timeout 50 Disables the VTY timeout

disconnection function.
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.

user-interface vty 0 14 //Configure VTY 0 to VTY 14.
authentication-mode
aaa
user privilege level
15
idle-timeout 5 0
2.5 Configuring SNMP

Configuring SNMP allows devices to communicate with the network management system
(NMS).
Data Planning
NOTE
Configure the SNMP trap function on all routers.

VPN) Solution
snmp-agent sys-info all Enables the SNMP trap

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

included iso-view contains the iso subtree.
snmp-agent community read public, write private Sets read and write
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 trap enable — Enables all traps on a device.
snmp-agent trap source LoopBack 0 Configures the loopback

interface as the source
interface that sends trap
messages.
snmp-agent target-host address udp-domain 11.1.1.1 Allows the SNMP agent to

trap params securityname public send SNMP trap messages to
v2c the Huawei NMS at 11.1.1.1.
snmp-agent trap enable — Enables the LLDP trap

lldp function.
1. Configure SNMP.
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 read public mib-view iso-view
snmp-agent community write private mib-view iso-view
2. Configure the SNMP agent to send trap messages to the NMS.

snmp-agent trap enable//Enable the SNMP agent to send trap messages.
snmp-agent trap source LoopBack0//Specify a source interface that sends trap
messages.
snmp-agent target-host trap address udp-domain 11.1.1.1 params securityname
public v2c//Configure the SNMP agent to send SNMP trap messages and set the
community name to public.
snmp-agent trap enable lldp//Enable the LLDP trap function.
Checking the Configuration

1. # Check community names.
[HUAWEI] display snmp-agent community
Community name:public
Group name:public

VPN) Solution
Storage-type: nonVolatile
Community name:private
Group name:private
Storage-type: nonVolatile
2. # Check the IP address configured for the NMS that receives trap messages.
[HUAWEI] display snmp-agent target-host
Target-host NO. 1
-----------------------------------------------------------
IP-address : 11.1.1.1
VPN instance : -
Security name : public
Port : 162
Type : trap
Version : v1
Level : No authentication and privacy
NMS type : HW NMS
-----------------------------------------------------------

VPN) Solution
Configuration Guide(CLI) 3 Deploying an IGP
3 Deploying an IGP
About This Chapter
Different IS-IS processes are deployed on access and aggregation rings to isolate routes. This is
to relieve the routing burden of CSGs.
3.1 Configuration Roadmap
This section describes the IS-IS configuration roadmap.
3.2 Data Planning
To deploy IS-IS, plan the following data.
3.3 Configuring Basic IS-IS Functions
Different IS-IS processes need to be configured on CSGs, ASGs, and RSGs.
3.4 Controlling Route Advertisement and Import
A routing policy needs to be configured to control the route advertisement and import on the
access and aggregation rings.

VPN) Solution

This section describes the IS-IS configuration roadmap.
As shown in Figure 3-1, r routing policies need to be applied to routes between the access area
and the aggregation area to reduce the number of routes on access devices.
If multiple CSGs exist on the access netwwork, you can assign different cost values to interfaces
to control route selection. In this manner, CSGs select the links with lower costs, ensuring traffic
load balancing between ASGs and RSGs.
In addition, if dual control boards are configured, to ensure carrier-class reliability, GR needs
to be enabled.
Figure 3-1 Network topology of IS-IS multi-process
The configuration roadmap is as follows:

1. In the access area, enable IS-IS on routers, with IS-IS process 1 used and Level 2 routes
advertised.
2. In the aggregation area, enable IS-IS on routers, with IS-IS process 100 used and Level 2
routes advertised.
3. The master and backup ASGs import their routes of loopback 0 to IS-IS process 1 of the
access area.
4. To ensure that the CSG preferentially selects the route to the master ASG, set the cost value
of interfaces in the access area to 10 and that of the aggregation area to 100.
5. To ensure that the CSG secondly selects the link between dual-homing ASGs, set the cost
value of the link between the ASGs to 100 and the cost value of the link between the RSGs
to 1000.

VPN) Solution
NOTE
If the number of CSGs on the access ring is great, and these CSGs are dual-homed to master and backup
ASGs, adjust the cost value of the link between CSGs according to the number of CSGs, ensuring that
traffic load balancing can be implemented between ASGs. This example only discusses the situation of
only one CSG. For details on the situation of multiple CSGs, refer to the relevant solution introduction.
3.2 Data Planning

To deploy IS-IS, plan the following data.
NOTE
Parameter values need to be set based on the network conditions such as the network scale and network
topology. The following parameter values are recommended ones in this example and only for reference.
Table 3-1 IS-IS parameters
Parameter Value Remarks
isis l Access area: 1 IS-IS processes are enabled.

l Aggregation area: 100
network-entity ISIS 1 A Network Entity Title

l CSG1: (NET) is set.
49.0001.0010.0100.1001 CAUTION
.00 Converting the IP address of a
loopback interface to a NET is
l CSG2: recommended. This ensures
49.0001.0020.0200.2002 that each NET is unique on the
.00 network. If any NET is not
unique, route flapping may
l ASG3: occur. Therefore, network
49.0001.0030.0300.3003 planning in advance is
.00 important. When a Level-2 IS-
IS neighbor relationship is to be
l ASG4: established, whether the area
49.0001.0040.0400.4004 addresses are the same is not
.00 checked. When a Level-1 IS-IS
neighbor relationship is to be
ISIS 100
established, area addresses
l ASG3: must be the same. Otherwise,
49.0002.0000.0000.0003 the neighbor relationship
.00 cannot be established.
l ASG4:
49.0002.0000.0000.0004
.00
l RSG5:
49.0002.0050.0500.5005
.00
l RSG6:
49.0002.0060.0600.6006
.00
is-level Level-2 The level of the router is

configured.

VPN) Solution
cost-style Wide Routes with the cost style as

wide are received or
advertised.
isis cost It is recommended that the Link costs are specified for
link cost of the interfaces in SPF calculation.
the access area be configured
as 10, the link cost of the
interfaces in the aggregation
area as 100, link cost between
ASGs as 100, and link cost
between RSGs as 1000.
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 speed
up the convergence of an IS-
IS network.
isis enable Interfaces between network IS-IS is enabled on an

elements in the access area interface and the ID of the IS-
and aggregation area and IS process is specified to
loopback 0 are advertised. associate with the interface.
Loopback 0 of the ASG
device is advertised to the
aggregation area.
graceful-restart — GR is enabled for the IS-IS

process.
traffic-eng level-2 TE is enabled for the Level-2

IS-IS process.
3.3 Configuring Basic IS-IS Functions

Different IS-IS processes need to be configured on CSGs, ASGs, and RSGs.
Configuring CSGs
Configure CSGs on the access ring. Use the CSG1 as an example. The configuration procedure
is as follows:

VPN) Solution
1. Configure IS-IS globally.

isis 1
graceful-restart//Enable IS-IS GR.
is-level level-2//Configure the CSG1 as a Level-2 router.
cost-style wide//Set the cost style of the received and sent IS-IS routes to
wide to support IS-IS TE.
timer lsp-generation 1 50 50//Set the delay in generating LSPs.
flash-flood level-2//Enable LSP fast flooding to speed up IS-IS network
convergence.
network-entity 49.0001.0010.0100.1001.00//Configure a NET.
timer spf 1 50 50//Configure the delay in route calculation using SPF.
traffic-eng level-2//Enable IS-IS TE.
log-peer-change//Enable the output of IS-IS neighbor status change. In this
manner, the status change is logged.
2. Configure IS-IS on interfaces.

Enable IS-IS on physical interfaces and Loopback 0 of the CSG1.
description To csg2
undo shutdown
interface. A 30-bit subnet mask is used to save IP address resources.
isis enable 1//Enable IS-IS on the interface.
isis cost 10//Set the link cost on the access ring to 10.
#
description To ASG3
undo shutdown
ip address 10.1.3.1 255.255.255.252
isis enable 1
isis cost 10
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.255
isis enable 1
isis cost 10
Configuring ASGs
Configure IS-IS 1 and IS-IS 100 on the master and backup ASGs respectively. Configuring the
master ASG is similar to configuring the backup ASG. Use the configuration on ASG3 as an
example. The configuration procedure is as follows:
isis 1//Configure an IS-IS process on the access ring.
graceful-restart
is-level level-2
cost-style wide
timer lsp-generation 1 50 50
flash-flood level-2
network-entity 49.0001.0030.0300.3003.00
timer spf 1 50 50
traffic-eng level-2
log-peer-change
isis 100//Configure an IS-IS process on the aggregation ring.
graceful-restart
is-level level-2
cost-style wide
flash-flood level-2
network-entity 49.0002.0030.0300.3003.00
timer spf 1 50 50
traffic-eng level-2
log-peer-change

VPN) Solution
Configure IS-IS on the interfaces on the access ring.

description To csg1
undo shutdown
ip address 10.1.3.2 255.255.255.252
isis enable 1
isis cost 10
#
description To ASG4
undo shutdown
ip address 10.3.4.1 255.255.255.252
isis enable 1
isis cost 100//Set the cost of the link between ASGs to 100.
Configure IS-IS on the interfaces on the aggregation ring.

description To ASG4
undo shutdown
ip address 10.3.4.5 255.255.255.252
isis enable 100
isis cost 100//Set the link cost on the aggregation ring to 100.
#
description To rsg5
undo shutdown
ip address 10.3.5.1 255.255.255.252
isis enable 100
isis cost 100
#
interface LoopBack0//Advertise the Loopback 0 routes on ASGs on the aggregation
ring.
ip address 3.3.3.3 255.255.255.255
isis enable 100
isis cost 100
Configuring RSGs
Configure IS-IS 100 on the master and backup RSGs respectively. The configurations on the
master and backup RSGs are similar. Use the configuration on RSG5 as an example. The
configuration procedure is as follows:

isis 100
graceful-restart
is-level level-2
cost-style wide
flash-flood level-2
network-entity 49.0002.0050.0500.5005.00
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 cost 100
#
interface GigabitEthernetEth-Trunk 1.1
description To rsg6
undo shutdown
ip address 10.5.6.1 255.255.255.252

VPN) Solution
isis enable 100

isis cost 1000//Set the cost of the link between RSGs to 1000.
#
interface LoopBack0
ip address 5.5.5.5 255.255.255.255
isis enable 100
isis cost 100
3.4 Controlling Route Advertisement and Import

A routing policy needs to be configured to control the route advertisement and import on the
access and aggregation rings.
Configuring the Master ASG

1. Configure a routing policy to select the Loopback 0 routes on the aggregation ring.
route-policy LoopBack0 permit node 1
if-match ip-prefix LoopBack0
apply isis level-2
#
ip ip-prefix LoopBack0 index 1 permit 3.3.3.3 32
2. Import the Loopback 0 routes that are advertised to the aggregation ring to the access ring.
isis 1
import-route isis 100 route-policy LoopBack0 cost 100//Import the loopback0
routes with the cost of 100 in IS-IS 100 to IS-IS 1.
Configuring the Backup ASG

1. Configure a routing policy to select the Loopback 0 routes on the aggregation ring.
route-policy LoopBack0 permit node 1
if-match ip-prefix LoopBack0
apply isis level-2
#
ip ip-prefix LoopBack0 index 1 permit 4.4.4.4 32
2. Import the Loopback 0 routes that are advertised to the aggregation ring to the access ring.
isis 1
import-route isis 100 route-policy LoopBack0 cost 200

l Run the ping command to check network connectivity.
l Run the display isis peer command on a router to check information about its IS-IS
neighbors.
If the IS-IS neighbor relationships are established, you can view the router's IS-IS
neighbors.
[CSG1]display isis peer
Peer information for ISIS(1)
System Id Interface Circuit Id State HoldTime Type

PRI
------------------------------------------------------------------------------
-
0020.0200.2002 GE0/1/0 0030.0300.3003.00 Up 24s L2 64
0030.0300.3003 GE0/1/1 0030.0300.3003.00 Up 24s L2 64
Total Peer(s): 2
l Run the display isis interface command on a router to check information about IS-IS-
enabled interfaces.

VPN) Solution
If the IS-IS neighbor relationships are established, you can see that the router's IPv4
neighbors are Up.
[CSG1]display isis interface
Interface information for ISIS(1)

---------------------------------
Interface Id IPV4.State IPV6.State MTU Type DIS
Loop0 001 Up Down 1500 L1/L2 --
GE0/1/0 001 Up Down 1497 L1/L2 No/No
GE0/1/1 002 Up Down 1497 L1/L2 No/No
[CSG1]
l Run the display isis lsdb command to check the IS-IS Link State Database (LSDB) on each
router.
You can see that the LSDB on CSG1 contains only link state information on the access
ring.
l Run the display isis route command to check IS-IS routes on each router.
You can see that the IS-IS routes on CSG1 contain only the Loopback 0 routes on the
aggregation ring.

VPN) Solution
Configuration Guide(CLI) 4 Deploying MPLS
4 Deploying MPLS
About This Chapter
MPLS TE needs to be configured for links between CSGs and RSGs to transmit MPLS VPN
services.
This section describes the roadmap for deploying MPLS.
4.2 Data Planning
To deploy MPLS, plan the following data.
4.3 Configuring MPLS TE and Hot Standby
MPLS TE is enabled to establish a primary tunnel and hot standby is enabled to establish a hot-
standby tunnel to protect traffic on the primary tunnel.These tunnels are used to transmit VPN
services.
4.4 Configuring Static BFD for TE
This section describes how to configure static BFD for TE to monitor primary tunnels. Static
BFD for TE speeds up L3VPN FRR traffic switchovers.
4.5 Configuring Static BFD for TE-LSP
This section describes how to Configure static BFD for TE-LSP to monitor primary CR-LSPs.
Static BFD for TE-LSP speeds up traffic switchovers.

VPN) Solution

This section describes the roadmap for deploying MPLS.
As shown in Figure 4-1, an MPLS TE tunnel (MPLS VPN) is established between the CSG and
RSG to transmit wireless services.
Figure 4-1 MPLS TE tunnel topology
1. Configure LSR-IDs and enable MPLS and MPLS TE globally on each device and interfaces
along the TE tunnel. In addition, enable OSPF on the ingress.
2. Create the tunnel for the Ethernet service.
(1) Create master VPN tunnels.
l Establish the master VPN tunnel TE1 between CSG1 and ASG3. Enable hot-
standby protection for TE1, with the primary explicit path and secondary explicit
path established.
l Establish the master VPN tunnel TE2 between ASG3 and RSG5. Enable hot-
path established.
(2) Create the slave VPN tunnel.
l Establish the slave VPN tunnels TE3 and TE4 for TE1.
l Establish the slave VPN tunnel TE5 for TE2.
l Create a tunnel policy to bind the tunnel to the destination IP address. This allows
this tunnel only to transmit VPN services.
(3) Configure BFD for TE-LSP.

VPN) Solution
Configure BFD for TE-LSP on the master VPN tunnels TE1 and TE2, which speeds
up the switchover between the primary LSP and the hot-standby LSP.
(4) Configuring BFD for TE.
Configure BFD for TE on the master VPN tunnels TE1 and TE2, which speeds up the
switchover between the master tunnel and the slave tunnel in L3VPN FRR.
3. Create the ATM/TDM service tunnel.
(1) Enable MPLS L2VPN on each node along the TE tunnel, and configure LDP remote
peers on these nodes.
(2) Create the master VPN tunnel.
l Establish the master VPN tunnel TE1 between CSG1 and ASG3. Enable hot-
path established.
l Establish the master VPN tunnel TE2 between ASG3 and RSG5. Enable hot-
path established.
(3) Create the slave VPN tunnel.
l Establish the slave VPN tunnels TE3 and TE6 for TE1 or TE2.
l Establish TE7 between RSGs to facilitate the traffic to be diverted to the spoke
PW when a link fault occurs on the RSG side.
NOTE
If the Ethernet service shares the same tunnel with the ATM/TDM service, the same tunnel policy
can be configured for these services. Otherwise, different tunnel policies need to be configured.
4. Create a tunnel policy.
Bind the IP address of the remote peer to the tunnel policy, ensuring that VPN data from
the local end to the destination address is transmitted along the bound tunnel.
4.2 Data Planning

To deploy MPLS, plan the following data.
NOTE
Parameter values need to be set based on the network conditions such as network scale and network
Table 4-1 MPLS parameters
mpls lsr-id The IP address of loopback 0 Configuring LSR IDs for

is specified as the LSR ID. devices is the prerequisite for
running other MPLS
commands.
mpls — MPLS, MPLS TE, and

mpls te RSVP-TE are enabled
globally on the device or on
mpls rsvp-te interfaces, and the hello
mpls rsvp-te hello mechanism is enabled.

VPN) Solution
label advertise non-null By default, the egress of an

ATN device allocates labels
to the penultimate hop.
Therefore, the egress of the
corresponding CX device
also needs to be configured to
allocate labels to the
penultimate hop so that the
communication between the
ATN device and the CX
device can be implemented.
lsp-trigger all LSPs are established on the

basis of all static routes and
IGP routes.
mpls rsvp-te hello full-gr — RSV-TE GR is enabled

mpls rsvp-te hello basic- between devices. In addition,
restart-time the basic restart time of
RSVP GR is specified, for
example, as 900s.
explicit-path The name of an explicit path An explicit path is

is specified in the format of configured.
A_XtoY.
l A: If A is specified as
main, it indicates the
primary LSP; if A is
specified as standby, it
specifies the hot-standby
LSP.
l XY: X specifies the router
ID of the source node and
Y indicates the router ID
of the destination node.
interface Tunnel Tunnel number: 0/0/XY A tunnel interface is created.

XY: X specifies the router ID
of the source node and Y
specifies the router ID of the
destination node.
ip address unnumbered interface LoopBack 0 The IP address of loopback 0

is used by the tunnel
interface.
tunnel-protocol mpls te The CR-LSP tunnel mode is

specified for the tunnel
interface.
destination IP address of Loopback 0 on The destination IP address is

the remote device specified.

VPN) Solution
mpls te tunnel-id Tunnel ID format: XY A tunnel ID is configured.

XY: X specifies the router ID
of the source node and Y
specifies the router ID of the
destination node.
mpls te record-route label — Route recording and label

recording are configured for
the tunnel.
mpls te path explicit-path hot-standby wtr 60 The primary and secondary

[ secondary ] explicit paths are specified
mpls te backup for the tunnel.
If the hot-standby mode is
configured for the tunnel, the
switching time is determined
based on the real world
situation.
mpls te commit — MPLS TE tunnel

configurations are
committed.
bfd bind mpls-te interface discriminator local BFD is bound to the primary
Tunnel te-lsp discriminator remote LSP of the master VPN
tunnel.
process-pst
The local discriminator is the
same as the remote
discriminator.The local
discriminator value of ATN
ranges from 1 to 255, and that
of CX600 ranges from 1 to
8191.
The minimum sending and
receiving intervals for BFD
packets need to be configured
according to configurations
of the live network. Detection
period = Detection multiple *
Sending/Receiving interval
(3*10 ms)
To speed up the switchover,
BFD is allowed to modify the
port state table.

VPN) Solution
bfd bind mpls-te interface discriminator local The master VPN tunnel to be
Tunnel discriminator remote monitored by BFD is
configured.
process-pst
The local discriminator is the
same as the remote
discriminator.The local
discriminator value of ATN
ranges from 1 to 255, and that
of CX600 ranges from 1 to
8191.
of the live network. Detection
period=detection
multiple*sending/receiving
interval (3*100 ms)
To speed up the switchover,
BFD sessions are allowed to
modify the port state table.
tunnel-policy Name of a tunnel Configure a tunnel

policy:IPRAN policy,and CR-LSP is
tunnel select-seq cr-lsp preferred.
load-balance-number 1
Table 4-2 MPLS TE tunnel list

Tunnel Tunnel Tunnel ID Primary Path Host-standby
Interface Path
TE1 CSG1: 13 main_1to3: standby_1to3:

Tunnel0/0/13 31 CSG1–ASG3 CSG1–CSG2–
ASG3: main_3to1: ASG4–ASG3
Tunnel0/0/31 ASG3–CSG1 standby_3to1:
ASG3–ASG4–
CSG2–CSG1
TE2 ASG3: 35 main_3to5: standby_3to5:

Tunnel0/0/35 53 ASG3–RSG5 ASG3–ASG4–
RSG5: main_5to3: RSG6–RSG5
Tunnel0/0/53 RSG5–ASG3 standby_5to3:
RSG5–RSG6–
ASG4–ASG3

VPN) Solution
Tunnel Tunnel Tunnel ID Primary Path Host-standby

Interface Path
TE3 CSG1: 14 main_1to4: —

Tunnel0/0/14 41 CSG1–CSG2–
ASG4: ASG4
Tunnel0/0/41 main_4to1:
ASG4–CSG2–
CSG1
TE4 ASG4: 45 main_4to5: —

Tunnel0/0/45 54 ASG4–RSG6–
RSG5: RSG5
RSG5–RSG6–
ASG4

Tunnel0/0/36 63 ASG3–ASG4–
RSG6: RSG6
RSG6–ASG4–
ASG3

Tunnel0/0/46 64 ASG4–RSG6
RSG6: main_6to4:
Tunnel0/0/64 RSG6–ASG4
TE7 RSG5: 56 main_5to6: —

Tunnel0/0/56 65 RSG5–RSG6
RSG6: main_6to5:
Tunnel0/0/65 RSG6–RSG5
4.3 Configuring MPLS TE and Hot Standby

MPLS TE is enabled to establish a primary tunnel and hot standby is enabled to establish a hot-
standby tunnel to protect traffic on the primary tunnel.These tunnels are used to transmit VPN
services.
NOTE
IGP TE has been enabled.
Configuring CSGs
Configure MPLS TE tunnels on each CSG on the access network:
l Establish an RSVP-TE tunnel with hot-standby CR-LSP between CSG1 and ASG3.
l Establish an RSVP-TE tunnel between CSG1 and ASG4.
Configure CSGs on the access ring. Use CSG1 (master) as an example.

VPN) Solution
1. Enable MPLS TE globally and on interfaces.

mpls lsr-id 1.1.1.1//Configure an MPLS LSR ID. Using a loopback interface
address is recommended.
mpls//Enable MPLS globally.
mpls te//Enable MPLS TE globally.
mpls rsvp-te//Enable RSVP-TE.
mpls rsvp-te hello//Enable the RSVP-TE Hello mechanism globally.
mpls rsvp-te hello full-gr//Enable RSVP-TE GR.
mpls te cspf//Enable CSPF.
#
mpls//Enable MPLS on the interface.
mpls te//Enable MPLS TE on the interface.
mpls rsvp-te//Enable RSVP-TE on the interface.
mpls rsvp-te hello//Enable the RSVP-TE Hello mechanism on the interface.
mpls rsvp-te srefresh//Enable RSVP Srefresh on the interface.
#
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls rsvp-te srefresh
2. Configure explicit paths.

explicit-path main_1to3//Configure an explicit path for the primary CR-LSP
between CSG1 and ASG3 and apply the explicit path to the tunnel interface.
next hop 4.4.4.4 exclude//Prevent the primary CR-LSP from passing through the
backup ASG. Using a loose explicit path is recommended. A loose explicit path
allows the future operation of adding nodes to the ring.
#
explicit-path standby_1to3//Specify an explicit path for a hot-standby CR-LSP
betweenCSG1 and ASG3.
next hop 4.4.4.4 include loose //Ensure that the hot-standby CR-LSP in the
primary tunnel passes through the backup ASG. Using a loose explicit path and
loopback0 address are recommended.
#
explicit-path main_1to4//Specify an explicit path for the primary CR-LSP
betweenCSG1 and ASG4.
next hop 3.3.3.3 exclude//Prevent the primary CR-LSP in the hot-standby tunnel
from passing through the backup ASG.
3. Configure tunnel interfaces.

interface Tunnel0/0/13//Configure a tunnel interface for the primary tunnel
between CSG1 and ASG3.
ip address unnumbered interface LoopBack0//Configure the tunnel interface to
borrow the IP address of loopback0.
tunnel-protocol mpls te//Configure MPLS TE as a tunnel protocol.
destination 3.3.3.3//Configure the destination IP address of the tunnel. The
value is the IP address of ASG3.
mpls te tunnel-id 13//Set a tunnel ID. The tunnel ID takes effect locally and
must be unique on the local node.
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 an explicit path for the primary
CR-LSP between CSG1 and ASG3.
mpls te path explicit-path standby_1to3 secondary//Configure a hot-standby CR-
LSP between CSG1 and ASG3.
mpls te backup hot-standby wtr 60//Set the WTR time to 60s. The default WTR
time for a switchback is 10s. The value can be set as needed.
mpls te commit//Commit all MPLS TE configurations on the tunnel interface. The

configurations can take effect only after this command is run.
#
interface Tunnel0/0/14//Specify the tunnel between CSG1 and ASG4, which is used
to switch traffic to the backup TE tunnel.
ip address unnumbered interface LoopBack0
tunnel-protocol mpls te
destination 4.4.4.4

VPN) Solution
mpls te tunnel-id 14
mpls te record-route label
mpls te path explicit-path main_1to4
mpls te commit
4. Configure a tunnel policy.

tunnel-policy IPRAN//Configure a tunnel policy.
tunnel select-seq cr-lsp load-balance-number 1 //CR-LSP is preferred.
Configuring ASGs
Configure MPLS TE tunnels on each ASG:
l Establish RSVP-TE tunnels with Hot-standby CR-LSP between ASG3 and CSG1 and
between ASG3 and RSG5.
l Establish RSVP-TE tunnels between ASG4 and CSG1 and between ASG4 and RSG5.
l Establish an RSVP-TE tunnel between ASG3 and RSG6.
l Establish an RSVP-TE tunnel between ASG4 and RSG6.
The configuration on the master ASG is similar to that on the backup ASG. Use ASG3 (master)
as an example.
mpls lsr-id 3.3.3.3
mpls
mpls te
label advertise non-null//Allocate non-null labels to the penultimate hop.
Allocating non-null labels from the egress to the penultimate hop is a default
setting on ATNs. To communicate with ATNs, CX600s are configured to allocate
non-null labels to the penultimate hops.
mpls rsvp-te
mpls rsvp-te hello
mpls rsvp-te hello full-gr
mpls te cspf
#
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//Configure the primary CR-LSP between ASG3 and CSG1,
and apply the explicit path to the tunnel interface.

VPN) Solution
next hop 4.4.4.4 exclude//Prevent the primary CR-LSP from passing through the
backup ASG. Using a loose explicit path is recommended. A loose explicit path
#
between ASG3 and CSG1.
next hop 4.4.4.4 include loose
#
next hop 6.6.6.6 exclude//Prevent the TE tunnel from passing through the
backup RSG. Using a loose explicit path is recommended. A loose explicit path
#
#
explicit-path main_3to6//Specify an explicit path for a CR-LSP between ASG3 and
RSG6.
next hop 5.5.5.5 exclude//Prevent the primary CR-LSP in the primary TE tunnel
from passing through the master RSG.

interface Tunnel0/0/31//Configure a tunnel interface for the tunnel between
ASG3 and CSG1.
ip address unnumbered interface LoopBack0//Configure the tunnel interface to
borrow the IP address of loopback0.
tunnel-protocol mpls te//Configure MPLS TE as a tunnel protocol.
destination 1.1.1.1//Configure the destination IP address of the tunnel. The
value is the IP address of CSG1.
mpls te tunnel-id 31//Set a tunnel ID. The tunnel ID takes effect locally and
must be unique on the local node.
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_3to1//Specify an explicit path for the primary
CR-LSP between ASG3 and CSG1.
mpls te path explicit-path standby_3to1 secondary//Configure a hot-standby CR-
LSP between ASG3 and CSG1.
mpls te backup hot-standby wtr 60//Set the WTR time to 60s. The default WTR
time for a switchback is 10s. The value can be set as needed.
mpls te commit//Commit all MPLS TE configurations on the tunnel interface. The

configurations can take effect only after this command is run.
#
ASG3 and RSG5.
destination 5.5.5.5
mpls te path explicit-path standby_3to5 secondary
mpls te backup hot-standby wtr 60
mpls te commit
#
ASG3 and RSG6.
destination 6.6.6.6
mpls te commit
#

VPN) Solution

Configuring RSGs
Configure MPLS TE tunnels on each RSG:
l Establish an RSVP-TE tunnel with Hot-standby CR-LSP between RSG5 and ASG3.
l Establish an RSVP-TE tunnel between RSG6 and ASG3.
l Establish an RSVP-TE tunnel for bypass PW between RSG5 and RSG6.
The configuration on the master RSG is similar to that on the backup RSG. Use RSG5 (master)
as an example.
mpls lsr-id 5.5.5.5
mpls
mpls te
label advertise non-null//Allocate non-null labels to the penultimate hop.
Allocating non-null labels from the egress to the penultimate hop is a default
setting on ATNs. To communicate with ATNs, CX600s are configured to allocate
non-null labels to the penultimate hops.
mpls rsvp-te
mpls rsvp-te hello
mpls rsvp-te hello full-gr
mpls te cspf
#
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
#
interface Eth-Trunk 1.1
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello

between RSG5 and ASG3.
next hop 6.6.6.6 exclude
#
between RSG5 and ASG3.
#
explicit-path main_5to4//Specify an explicit path for a CR-LSP between RSG5
and ASG4.
next hop 3.3.3.3 exclude
#
explicit-path main_5to6//Specify an explicit path for a CR-LSP between RSG5
and RSG6.

RSG5 and ASG3.

VPN) Solution
destination 3.3.3.3
mpls te path explicit-path standby_5to3 secondary
mpls te backup hot-standby wtr 60
mpls te commit
#
RSG5 and ASG4.
destination 4.4.4.4
mpls te commit
#
RSG5 and RSG6.
destination 6.6.6.6
mpls te commit


l Run the ping lsp te tunnel command to check CR-LSP connectivity and the forwarding
status of CR-LSPs.
# Run the following commands to check TE tunnel connectivity on the ingress and egress.
<HUAWEI> ping lsp te tunnel 0/0/13//The VPN tunnel can be pinged.
<HUAWEI> ping lsp te tunnel 0/0/13 hot-standby//The hot-standby VPN tunnel can
be pinged.
l Run the tracert lsp te tunnel command to check the forwarding paths of CR-LSPs.
This command is used to verify that the links of the primary and hot-standby tunnels do
not overlap.
[ASG3]tracert lsp te Tunnel 0/0/31
LSP Trace Route FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel0/0/31 , press CTRL_C
to break.
TTL Replier Time Type Downstream
0 Ingress 10.1.3.1/[3 ]
1 1.1.1.1 70 ms Egress
[ASG3]tracert lsp te Tunnel 0/0/31 hot-standby
LSP Trace Route FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel0/0/31 , press CTRL_C
to break.
0 Ingress 10.3.4.2/[1026 ]
1 10.3.4.2 40 ms Transit 10.2.4.1/[1026 ]
2 10.2.4.1 40 ms Transit 10.1.2.1/[3 ]
3 1.1.1.1 40 ms Egress
l Run the display mpls te tunnel-interface to view information about tunnel interfaces on
CSG1.
# Display tunnel interface information. The command output shows that the primary and
hot-standby CR-LSPs have been established successfully.
<CSG1> display mpls te tunnel-interface tunnel 0/0/13
================================================================

VPN) Solution
Tunnel0/0/13
================================================================
Tunnel State Desc : UP
Active LSP : Primary LSP
Session ID : 13
Ingress LSR ID : 1.1.1.1 Egress LSR ID: 3.3.3.3
Admin State : UP Oper State : UP
Primary LSP State : UP
Main LSP State : READY LSP ID : 1
Hot-Standby LSP State : UP
================================================================
Tunnel0/0/14
================================================================
Tunnel State Desc : UP
Active LSP : Primary LSP
Session ID : 14
Ingress LSR ID : 1.1.1.1 Egress LSR ID: 4.4.4.4
Admin State : UP Oper State : UP
Primary LSP State : UP
4.4 Configuring Static BFD for TE

This section describes how to configure static BFD for TE to monitor primary tunnels. Static
BFD for TE speeds up L3VPN FRR traffic switchovers.
Configure static BFD for TE to monitor all primary tunnels.
Configuring CSGs
Configure static BFD for TE to monitor the primary tunnel between CSG1 and ASG3.
1. Enable BFD.
bfd
2. Configure static BFD for TE.

# Configure static BFD for TE on Tunnel0/0/13 for the primary tunnel between CSG1 and
ASG3.
bfd TE13 bind mpls-te interface Tunnel0/0/13//Configure static BFD to monitor
the primary CR-LSP on Tunnel0/0/13.
discriminator local 13//Specify the local discriminator. The local
discriminator on one end is the same as the remote discriminator on the other
end of a BFD session.
discriminator remote 31//Specify the remote discriminator.
min-tx-interval 100//Set the local minimum interval at which BFD packets are
sent to 100 ms.
min-rx-interval 100//Set the local minimum interval at which BFD packets are
received to 100 ms.
process-pst//Enable the BFD session to modify the PST, speeding up a traffic
switchover.
commit//Commit the BFD session configurations.

Configure static BFD for TE to monitor the primary tunnel between ASG3 (master) and
CSG1 and that between ASG3 and RSG5 (master).
1. Enable BFD.

VPN) Solution
bfd

# Configure static BFD for TE on Tunnel0/0/31 for the primary tunnel between ASG3 and
CSG1.
discriminator local 31
discriminator remote 13
min-tx-interval 100
min-rx-interval 100
process-pst
commit
# Configure static BFD for TE on Tunnel0/0/35 for the primary tunnel between ASG3 and
RSG5.
sent to 100 ms.
received to 100 ms.
switchover.
Configuring the Master RSG

Configure static BFD for TE to monitor the primary tunnel between RSG5 (master) and
ASG3 (master).
1. Enable BFD.
bfd

# Configure static BFD for TE on Tunnel0/0/53 for the primary tunnel between RSG5 and
ASG3.
min-tx-interval 100
min-rx-interval 100
process-pst
commit

Run the display bfd session all for-te command on each node to view the BFD status.
The BFD session of the S_TE_TNL type is in the Up state. The BFD session has been established
successfully.
<CSG1> display bfd session all for-te
--------------------------------------------------------------------------------
Local Remote PeerIpAddr State Type InterfaceName
--------------------------------------------------------------------------------
13 31 3.3.3.3 Up S_TE_TNL Tunnel0/0/13
--------------------------------------------------------------------------------
Total UP/DOWN Session Number : 1/0

VPN) Solution
<ASG3> display bfd session all for-te

--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
31 13 1.1.1.1 Up S_TE_TNL Tunnel0/0/31
35 53 5.5.5.5 Up S_TE_TNL Tunnel0/0/35
--------------------------------------------------------------------------------
<RSG5> display bfd session all for-te
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
53 35 3.3.3.3 Up S_TE_TNL Tunnel0/0/53
--------------------------------------------------------------------------------
4.5 Configuring Static BFD for TE-LSP

This section describes how to Configure static BFD for TE-LSP to monitor primary CR-LSPs.
Static BFD for TE-LSP speeds up traffic switchovers.
Configure static BFD for TE-LSP to monitor all primary CR-LSPs.
Configuring the CSG

Configure static BFD for TE-LSP to monitor the primary CR-LSP between CSG1 and ASG3.
1. Enable BFD.
bfd
2. Configure static BFD for TE-LSP.

# Configure static BFD for TE-LSP on Tunnel0/0/13 for the primary CR-LSP between
CSG1 and ASG3.
bfd LSP13 bind mpls-te interface Tunnel0/0/13 te-lsp//Configure static BFD to
monitor the primary CR-LSP on Tunnel0/0/13.
sent to 10 ms.
received to 10 ms.
switchover.

Configure static BFD for TE-LSP for the primary CR-LSP between ASG3 (master) and
CSG1 and that between ASG3 (master) and RSG5 (master).
1. Enable BFD.
bfd

ASG3 and CSG1.

VPN) Solution

min-tx-interval 10
min-rx-interval 10
process-pst
commit
ASG3 and RSG5.
min-tx-interval 10
min-rx-interval 10
process-pst
commit

Configure static BFD for TE-LSP to monitor the primary tunnel between RSG5 (master) and
ASG3 (master).
1. Enable BFD.
bfd

RSG5 and ASG3.
min-tx-interval 10
min-rx-interval 10
process-pst
commit

Run the display bfd session all for-lsp command on each node to view the BFD status.
The BFD session of the S_TE_LSP type is in the Up state. The BFD session has been established
successfully.
<CSG1> display bfd session all for-lsp
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
103 301 3.3.3.3 Up S_TE_LSP Tunnel0/0/13
--------------------------------------------------------------------------------
<ASG3> display bfd session all for-lsp
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
301 103 1.1.1.1 Up S_TE_LSP Tunnel0/0/31
305 503 5.5.5.5 Up S_TE_LSP Tunnel0/0/35
--------------------------------------------------------------------------------
<RSG5> display bfd session all for-lsp
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
503 305 3.3.3.3 Up S_TE_LSP Tunnel0/0/53

VPN) Solution
--------------------------------------------------------------------------------

VPN) Solution
Configuration Guide(CLI) 5 Configuring Ethernet Service Bearer and Protection
5 Configuring Ethernet Service Bearer and

Protection
About This Chapter
Hierarchical BGP and MPLS VPN need to be configured between CSGs and RSGs to bear ETH
services.
This section describes the roadmap for configuring hierarchical BGP/MPLS VPN and service
protection.
5.2 Data Planning
To deploy L3VPN, plan the following data.
5.3 Configuring MP-BGP
To transmit 3G and LTE Ethernet services, MP-BGP needs to be configured between CSGs and
RSGs to implement hierarchical BGP/MPLS VPN.
5.4 Configuring a VPN
VPN instances need to be configured to advertise VPNv4 routes and forward data to achieve
communication over a L3VPN.
5.5 Configuring Protection Switching
To protect services from CSGs to RSGs, BGP GR and VPN FRR need to be configured.
5.6 Configuring VRRP
To protect links between RSGs and the MBB Core, VRRP needs to be configured between the
master and backup RSGs.

VPN) Solution

This section describes the roadmap for configuring hierarchical BGP/MPLS VPN and service
protection.
l Communications between NodeBs and RNCs need to be enabled to transmit 3G (Ethernet)
services.
l Communications (S1 services) between eNodeBs and Mobility Management Entities
(MMEs) and communications (X2 services) between eNodeBs need to be enabled to
transmit LTE services.
As shown in Figure 5-1, hierarchical BGP/MPLS VPN is configured between CSGs and RSGs.
Figure 5-1 Hierarchical L3VPN
The hierarchical BGP/MPLS VPN configuration roadmap is as follows:

1. Deploy MP-IBGP.
l Establish MP-IBGP peer relationships between CSGs and the master ASG, and between
the master ASG and the master RSG.
l To protect the master ASG, establish MP-IBGP peer relationships between CSGs and
the backup ASG, and between the backup ASG and the master RSG.
l To protect the master RSG, establish an MP-IBGP peer relationship between the master
ASG and the backup RSG.
2. Deploy VPN services.
Use either of the following modes to deploy VPN services from CSGs to RSGs:
l H-VPN
For end-to-end services from CSGs to RSGs, create VPN instances on CSGs and RSGs.
Configure ASGs as VPN RRs, and CSGs and RSGs as VPN RR clients. Configure
ASGs to advertise specific routes to CSGs.

VPN) Solution
For local switching services between CSGs, create VPN instances on each CSG and on
the ASG and RSG to which the CSG belongs. (This is applicable in the case where
CSGs belong to different ASGs.) Configure ASGs to advertise default routes to only
the corresponding CSGs.
l HoVPN
For all services, configure hierarchical L3VPN on ASGs by specifying CSGs as UPEs.
Configure ASGs to advertise only default routes to CSGs.
NOTE
The H-VPN solution is used as an example.
3. Configure service protection switching.
l Enable BGP GR and BGP tracking on the entire network. This is to ensure that BGP
peer relationships are not interrupted during a master/backup device switchover and
speed up IBGP route convergence.
l Increase the ConnectRetry interval for re-establishing the BGP peer relationship
between a CSG and the master ASG.
This configuration allows the BGP peer relationship to be established between the CSG
and the master ASG after the BGP peer relationship has been established between the
recovered master ASG and the master RSG during LTE X2 service deployment.
l Configure VPN FRR or BFD for BGP.
VPN FRR is recommended. If no VPN instance is created on the deployed devices,
configure BFD for BGP to speed up the master/backup device switchover.
4. Configure VRRP.
To protect the links between RSGs and the MBB core, configure VRRP over VLANIF
between the master and backup RSGs.
(1) Configure the interfaces that connect the master and backup RSGs and the interfaces
that connect the master and backup RSGs to the RNC to be Layer 2 switch interfaces,
and add these interfaces to a VLAN.
(2) Create a VLANIF interface on the master and backup RSGs and configure VRRP over
VLANIF.
(3) Configure BFD between the master and backup RSGs to check Layer 2 links and
remote private network addresses. This is to speed up the master/backup device
switchover.
(4) Configure VRRP switchback delay on the master RSG. If VRRP switchback delay is
not configured, both NEs may be in the master state during VRRP switchback. This
will result in packet loss.
5.2 Data Planning

To deploy L3VPN, plan the following data.
NOTE
The data provided in this section is used as an example, which may be different from that in real world
situations because the network scale and topology may differ.

VPN) Solution
Table 5-1 BGP/MPLS VPN parameters

Parameter Value Appendix
bgp 100 Enables BGP.
router-id IP address of Loopback 0 Indicates a router ID. Each

router ID uniquely identifies
a router in an AS.
graceful-restart 600 Enables BGP GR to ensure

non-stop services during a
master/backup device
switchover.
peer tracking delay 30 Sets the delay to a value

greater than GR convergence
time if a local device and its
BGP peer have successfully
performed GR negotiation,
and the master/slave MPU
switchover have occurred on
the BGP peer. If the delay is
set to be smaller than the GR
convergence time, the
connection between the local
device and the BGP peer will
be torn down, which leads to
a GR failure.
peer as-number 100 Sets an AS number for a peer

or a peer group.
peer connect-interface LoopBack0 Configure the source

interface that sends BGP
packets to be Loopback 0.
peer timer connect-retry 300 Sets a ConnectRetry interval

for a specified peer or peer
group. This configuration
allows the BGP peer
relationship to be established
between the CSG and the
master ASG after the BGP
peer relationship has been
established between the
recovered master ASG and
the master RSG.
ipv4-family vpnv4 - Enters the BGP-VPNv4

address family view.

VPN) Solution
undo policy vpn-target - Disables VPN target-based

filtering to allow all VPNv4
routes to be added to a routing
table.
peer enable - Enables specified peers or

peer groups to exchange
routing information in the
address family view.
peer route-policy { import | - Applies a routing policy to

export } the route sent from a peer or
peer group.
reflector cluster-id 1 Cluster ID of an RR Normally, a cluster has only

one RR. The router ID of an
RR identifies the cluster to
which the RR belongs.
peer reflect-client - Configures a device as an RR

and the specified peer or peer
group as the client of the RR.
tunnel-selector - Applies a tunnel selector to

labeled routes.
peer next-hop-local - Configures a device to set its

IP address as the next hop
when the device advertises
routes to an IBGP peer or an
IBGP peer group.
ipv4-family vpn-instance IPRAN Associates a specified VPN

instance with the IPv4
address family. This
parameter displays the BGP-
VPN instance IPv4 address
family view.
ip vpn-instance IPRAN Creates a VPN instance and

enters the VPN instance
view.
route-distinguisher - Sets a Route Distinguisher

(RD) for the VPN instance
IPv4 address family.

VPN) Solution
vpn-target - Associates the current VPN

instance IPv4 address family
with one or more VPN
targets. When a PE sends a
VPN route to other PEs, this
PE adds an export VPN target
to the VPN route. When a PE
receives a VPN route from
other PEs, this PE checks
whether the export VPN
target in the received VPN
route matches the local
import VPN target. If the two
VPN targets match, the PE
adds the VPN route to the
VPN instance IPv4 address
family.
vpn frr route-policy - Enables VPN FRR.
5.3 Configuring MP-BGP

To transmit 3G and LTE Ethernet services, MP-BGP needs to be configured between CSGs and
RSGs to implement hierarchical BGP/MPLS VPN.
Configuring CSGs
Configure CSGs on the access ring. Use CSG1 as an example.
1. Configure a route-policy and set a lower priority for the routes to the backup ASG.
route-policy pref permit node 10
apply local-preference 50//Set the local preference of BGP routes to 50.
2. Configure MP-IBGP peers.

bgp 100
router-id 1.1.1.1
peer 3.3.3.3 as-number 100//Establish a peer relationship between the CSG and
the master ASG.
peer 3.3.3.3 connect-interface LoopBack0//Configure the source interface that
sends BGP packets to be Loopback 0 and IP address of the source interface to
be the IP address of Loopback 0.
peer 4.4.4.4 as-number 100//Establish a peer relationship between the CSG and
the backup ASG.
peer 4.4.4.4 connect-interface LoopBack0
#
ipv4-family vpnv4
peer 3.3.3.3 enable
peer 4.4.4.4 enable
peer 4.4.4.4 route-policy pref import//Configure the VPN routes to the
backup ASG not to be preferentially selected.
NOTE
To allow LTE X2 services to be transmitted between eNodeBs, configure CSG2. The configuration of
CSG2 is similar to that of CSG1, and is not provided here.

VPN) Solution
Configuring ASGs
For LTE X2 services, ASGs advertise only default routes to CSGs. For other services, ASGs
advertise specific routes to CSGs.
# Configure the master and backup ASGs. Use the configuration of ASG3 as an example.
1. Configure an IP prefix list to match the default route for LTE X2 services.
ip ip-prefix default index 10 permit 0.0.0.0 0//Permit the default route
0.0.0.0 0.
ip ip-prefix default index 20 permit 192.168.2.0 24 greater-equal 24 less-
equal 32//Permit the core route 192.168.2.0.
ip ip-prefix nodefault index 10 deny 0.0.0.0 0//Deny the default route 0.0.0.0
0.
ip ip-prefix nodefault index 20 permit 0.0.0.0 0 less-equal 32//Permit all
routes except the default route.
2. Configure a tunnel selector and bind a VPN to a TE tunnel.

tunnel-selector IPRAN permit node 10
apply tunnel-policy IPRAN
NOTE
For details on tunnel policy configurations, see the section "Deploying MPLS."
3. Configure MP-IBGP peers.
bgp 100
router-id 3.3.3.3
group CSG internal//Create an IBGP peer group named CSG.
peer CSG connect-interface LoopBack0
peer 1.1.1.1 group CSG//Add CSGs to the CSG peer group.
peer 2.2.2.2 group CSG
group RSG internal//Create an IBGP peer group named RSG.
peer RSG connect-interface LoopBack0
peer 5.5.5.5 group RSG//Add RSGs to the RSG peer group.
peer 6.6.6.6 group RSG
#
ipv4-family vpnv4
reflector cluster-id 1//Configure ASGs as RRs.
undo policy vpn-target//Cancel VPN target-based filtering for VPNv4 routes
to allow all VPN routes to be received.
tunnel-selector IPRAN//Configure a tunnel selector and bind a VPN to a TE
tunnel.
peer CSG enable
peer CSG ip-prefix default export//Permit the default VPN route 0.0.0.0 0
sent to the CSGs. (This configuration is for LTE X2 services.)
peer CSG reflect-client//Configure CSGs as clients of ASGs (RRs).
peer CSG next-hop-local//Configure the ASG to set its IP address as the next
hop of routes when the ASG advertises routes to a CSG.
peer RSG enable
peer RSG ip-prefix nodefault export//Deny the default VPN route 0.0.0.0 0
sent to the RSGs. (This configuration is for LTE X2 services.)
peer RSG reflect-client//Configure RSGs as clients of ASGs (RRs).
peer RSG next-hop-local//Configure the ASG to set its IP address as the next
hop of routes when the ASG advertises routes to an RSG.
NOTE
Configure ASG4 as a different RR. The configuration is similar to that of ASG3 and is not provided here.
Configuring RSGs
# Configure the master and backup RSGs. Use the configuration of RSG5 as an example.
Configure MP-IBGP peers.

VPN) Solution
bgp 100
router-id 5.5.5.5
peer 3.3.3.3 as-number 100
peer 4.4.4.4 as-number 100
#
ipv4-family vpnv4
peer 3.3.3.3 enable
peer 4.4.4.4 enable
NOTE
The configuration of RSG6 is similar to that of RSG5, and is not provided here.

l Run the display bgp vpnv4 all peer command. The command output shows that the status
of the BGP peer relationship is Established, indicating that the BGP peer relationship has
been established.
# Run the following commands on the ingress and egress of a TE tunnel to check TE tunnel
connectivity.
[CSG1]display bgp vpnv4 all peer
BGP local router ID : 1.1.1.1
Local AS number : 100
Total number of peers : 2 Peers in established state : 2
Peer V AS MsgRcvd MsgSent OutQ Up/Down State
PrefRcv
3.3.3.3 4 100 12 18 0 00:09:38 Established 0
4.4.4.4 4 100 1 1 0 00:00:07 Established 0
[ASG3]display bgp vpnv4 all peer
BGP local router ID : 3.3.3.3

Local AS number : 100
Total number of peers : 4 Peers in established state : 4
Peer V AS MsgRcvd MsgSent OutQ Up/Down State

PrefRcv
1.1.1.1 4 100 98 98 0 01:36:18

Established 0
2.2.2.2 4 100 98 99 0 01:36:17
Established 0
5.5.5.5 4 100 98 98 0 01:36:18
Established 0
6.6.6.6 4 100 98 98 0 01:36:18
Established 0
5.4 Configuring a VPN

VPN instances need to be configured to advertise VPNv4 routes and forward data to achieve
communication over a L3VPN.
Configuring CSGs
# Configure CSGs. Use the configuration of CSG1 as an example.
1. Configure VPN instances.

# Create VPN instances based on service types.
ip vpn-instance LTE_S1//Create a VPN instance for LTE S1 services. (The
configuration is the same as that for 3G ETH services.)
ipv4-family

VPN) Solution
route-distinguisher 100:1//The VPN instance IPv4 address family takes effect

only after an RD is configured for it.
tnl-policy IPRAN//Configure a TE tunnel as the tunnel for the VPN instance.
vpn-target 1:1 export-extcommunity//Specify a VPN target for LTE S1 servies.
vpn-target 1:1 import-extcommunity
ip vpn-instance LTE_X2//Create a VPN instance for LTE X2 services.
ipv4-family
route-distinguisher 200:2//Set different RDs for different VPN instances on
the same device.
tnl-policy IPRAN
vpn-target 100:1 export-extcommunity//Specify a VPN target for LTE X2
services.
# Bind VPN instances to specific service interfaces.

interface Ethernet0/3/0
ip binding vpn-instance LTE_S1//Bind the LTE S1 VPN instance to a specific
service interface.
interface Ethernet0/3/1
ip binding vpn-instance LTE_X2//Bind the LTE X2 VPN instance to a specific
service interface.
2. Configure VPN route exchange at the CSG side.

Configure VPN route import as required. For example, direct route import, static route
import, and dynamic route import. Configuring direct route import is used as an example.
bgp 100
#
ipv4-family vpn-instance LTE_S1
import-route direct//Import direct routes to the VPN.
#
ipv4-family vpn-instance LTE_X2
import-route direct
NOTE
The configuration of CSG2 is similar to that of CSG1, and is not provided here.
Configuring ASGs
For LTE X2 services, ASGs advertise only default routes to CSGs. For other services, ASGs
advertise specific routes to CSGs. On ASGs, VPN instances are created only for LTE X2
services.

ip vpn-instance LTE_X2//Set the same VPN instance for LTE X2 services on the
entire VPN.
ipv4-family
route-distinguisher 200:2
tnl-policy IPRAN
vpn-target 100:1 export-extcommunity
2. Configure VPN route exchange at the ASG side.

# Configure a default route for a VPN instance.
ip route-static vpn-instance LTE_X2 0.0.0.0 0.0.0.0 NULL0//Configure a default
route for a VPN instance.
# Configure VPN routes.

bgp 100
ipv4-family vpn-instance LTE_X2

VPN) Solution
network 0.0.0.0//Advertise the default route in the VPN instance of LTE X2

services.
NOTE
The configuration of ASG4 is similar to that of ASG3, and is not provided here.
Configuring RSGs
ipv4-family ip vpn-instance LTE_S1//Specify a VPN target for LTE S1 services.
route-distinguisher 100:1
tnl-policy IPRAN
vpn-target 1:1 2:2 export-extcommunity//Configure the RSG to send routing
information of CSG1 and CSG2.
vpn-target 1:1 2:2 import-extcommunity//Configure the RSG to receive routing
information of CSG1 and CSG2.
# Bind VPN instances to specific service interfaces.

interface Vlanif100
ip binding vpn-instance LTE_S1///Bind the LTE S1 VPN instance to a VLANIF
interface.
2. Configure VPN route exchange at the RSG side.

Configure VPN route import as required. For example, direct route import, static route
import, and dynamic route import. Configuring direct route import is used as an example.
bgp 100
#
ipv4-family vpn-instance LTE_S1
import-route direct
NOTE
The configuration of RSG6 is similar to that of RSG5, and is not provided here.

l Run the ping -vpn-instance command on a PE to ping the remote PE.
ping -vpn-instance LTE_S1 192.168.1.1
NOTE
When a PE has multiple interfaces bound to the same VPN instance, specify the source address in
the ping -vpn-instance command to ping the remote PE. Otherwise, the ping may fail.
l Run the display ip vpn-instance verbose command to check VPN instance configurations.
[CSG1] display ip vpn-instance verbose
Total VPN-Instances configured : 2
VPN-Instance Name and ID : LTE_S1, 1

Interfaces : Ethernet0/3/0
Address family ipv4
Create date : 2011/07/07 12:09:15 UTC-08:00
Up time : 0 days, 00 hours, 10 minutes and 18 seconds
Route Distinguisher : 100:1
Export VPN Targets : 1:1
Import VPN Targets : 1:1
Label Policy : label per route
The diffserv-mode Information is : uniform
The ttl-mode Information is : pipe
Tunnel Policy : IPRAN
Log Interval : 5
VPN-Instance Name and ID : LTE_X2, 2

VPN) Solution
Interfaces : Ethernet0/3/1
Address family ipv4
Create date : 2011/07/07 12:09:15 UTC-08:00
Up time : 0 days, 00 hours, 10 minutes and 18 seconds
Route Distinguisher : 200:2
Export VPN Targets : 100:1
Import VPN Targets : 100:1
Label Policy : label per route
The diffserv-mode Information is : uniform
The ttl-mode Information is : pipe
Tunnel Policy : IPRAN
Log Interval : 5
l Run the display ip routing-table vpn-instance command to view the routing table of the
VPN instance.
[ASG3]dis ip routing-table vpn-instance LTE_X2
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Routing Tables: LTE_X2
Destinations : 2 Routes : 2
Destination/Mask Proto Pre Cost Flags NextHop Interface
0.0.0.0/0 Static 60 0 D 0.0.0.0 NULL0

192.168.101.0/24 IBGP 255 0 RD 1.1.1.1 Tunnel0/0/31
[RSG5]dis ip routing-table vpn-instance LTE_S1
------------------------------------------------------------------------------
Routing Tables: LTE_S1
192.168.2.0/24 Direct 0 0 D 192.168.2.2 Vlanif100

192.168.2.2/32 Direct 0 0 D 127.0.0.1 InLoopBack0
192.168.100.0/24 IBGP 255 0 RD 3.3.3.3 Tunnel0/0/53
[CSG1]display ip routing-table vpn-instance LTE_S1
------------------------------------------------------------------------------
Routing Tables: LTE_S1
192.168.2.0/24 IBGP 255 0 RD 3.3.3.3 Tunnel0/0/13

192.168.100.0/24 Direct 0 0 D 192.168.100.1
Ethernet0/0/2.1
[CSG1]display ip routing-table vpn-instance LTE_X2
------------------------------------------------------------------------------
Routing Tables: LTE_X2
0.0.0.0/0 IBGP 255 0 RD 3.3.3.3 Tunnel0/0/13

192.168.101.0/24 Direct 0 0 D 192.168.101.1
Ethernet0/0/2.2
5.5 Configuring Protection Switching

To protect services from CSGs to RSGs, BGP GR and VPN FRR need to be configured.

VPN) Solution
Configuring CSGs
Configure CSGs on the access ring. Use CSG1 as an example.
1. Configure BGP GR and BGP tracking.

bgp 100
graceful-restart//Enable BGP GR to ensure non-stop services during a master/
backup device switchover.
peer 3.3.3.3 tracking delay 30//Enable BGP tracking to speed up IBGP route
convergence.
peer 4.4.4.4 tracking delay 30
2. Set a ConnectRetry interval for re-establishing the BGP relationship.

bgp 100
peer 3.3.3.3 timer connect-retry 300//Allow the BGP peer relationship to be
established between the CSG and the master ASG after the BGP peer relationship
has been established between the recovered master ASG and the master RSG.
3. Configure VPN FRR.

# Configure a route-policy for VPN FRR.
ip ip-prefix frr index 10 permit 3.3.3.3 32//Match the destination address of
a packet with the IP address of the master ASG.
#
route-policy frr permit node 10//Configure a route-policy for VPN FRR.
if-match ip next-hop ip-prefix frr//Match the destination address of a packet
with the IP address of the master ASG.
apply backup-nexthop auto//Set the next hop of the VPN to auto.
# Configure VPN FRR for LTE S1 services.

ip vpn-instance LTE_S1
vpn frr route-policy frr//Configure VPN FRR for LTE S1 services.
# Configure VPN FRR for LTE X2 services.

ip vpn-instance LTE_X2
vpn frr route-policy frr//Configure VPN FRR for LTE X2 services.
NOTE
Configure BFD for TE on the working VPN tunnel to speed up a VPN FRR switchover. For details
on how to configure BFD for TE, see the section "Deploying MPLS."
Configuring ASGs
1. Configure BGP GR and BGP Tracking.

bgp 100
graceful-restart
2. Set a ConnectRetry interval between BGP peers.

bgp 100
peer 1.1.1.1 timer connect-retry 300//Allow the BGP peer relationship to be
established between the CSG and the master ASG after the BGP peer relationship
has been established between the recovered master ASG and the master RSG.
3. If no VPN instance is created on ASGs, configure BFD for BGP on ASGs and RSGs to
speed up master/backup RSG switchover in the case of an RSG failure. Only the ASG
configurations are provided here. For RSG configurations, see related sections.
bgp 100
peer 5.5.5.5 bfd min-tx-interval 100 min-rx-interval 100//Speed up the master/
backup RSG switchover.
peer 5.5.5.5 bfd enable

VPN) Solution
Configuring RSGs
1. Configure BGP GR.
bgp 100
graceful-restart
2. Configure VPN FRR.

# Configure a route-policy for VPN FRR.
ip ip-prefix frr index 10 permit 3.3.3.3 32//Match the destination address of
a packet with the IP address of the master ASG.
#
route-policy frr permit node 10//Configure a route-policy for VPN FRR.
if-match ip next-hop ip-prefix frr//Match the destination address of a packet
with the IP address of the master ASG.
apply backup-nexthop auto//Set the backup next hop of the VPN to auto.
# Configure VPN FRR for LTE S1 services.

ip vpn-instance LTE_S1
vpn frr route-policy frr//Configure VPN FRR for LTE S1 services.
NOTE
Configure BFD for TE on the working VPN tunnel to speed up a VPN FRR switchover. For details
on how to configure BFD for TE, see the section "Deploying MPLS."
3. If BFD for BGP is configured on ASGs, BFD sessions need to be configured on RSGs.
bgp 100
peer 3.3.3.3 bfd min-tx-interval 100 min-rx-interval 100//Configure BFD for
BGP process on an ASG.
peer 3.3.3.3 bfd enable

l Run the display bgp vpnv4 all peer command to check the backup next hop, backup label,
and backup tunnel ID.
<HUAWEI> display ip routing-table vpn-instance LTE_S1 10.1.3.0 verbose
------------------------------------------------------------------------------
Routing Table : LTE_S1
Summary Count : 1
Destination: 10.3.1.0/24
Protocol: BGP Process ID: 0
Preference: 255 Cost: 0
NextHop: 3.3.3.3 Neighbour: 3.3.3.3
State: Active Adv Relied Age: 00h15m06s
Tag: 0 Priority: low
Label: 15361 QoSInfo: 0x0
IndirectID: 0x13
RelayNextHop: 0.0.0.0 Interface: GE2/0/0
TunnelID: 0x6002002 Flags: RD
BkNextHop: 4.4.4.4 BkInterface:Unknown
BkLabel: 15362
SecTunnelID: 0x0
BkPETunnelID: 0x6002000 BkPESecTunnelID: 0x0
BkIndirectID: 0x15
5.6 Configuring VRRP

To protect links between RSGs and the MBB Core, VRRP needs to be configured between the
master and backup RSGs.

VPN) Solution
Configure VRRP over VLANIF between RSG5 and RSG6.

# Configure VRRP on RSG5.
1. Create a VLAN.
vlan batch 100 //Create VLAN 100.
2. Configure a VLAN trunk between the master and backup RSGs.

interface Eth-Trunk 1 portswitch//Configure the interfaces connecting the
master and backup RSGs to be switched interfaces.
undo shutdown
port link-type trunk//Configure the interfaces connecting the master and
backup RSGs to be trunk interfaces.
port trunk allow-pass vlan 100//Configure the trunk interfaces to allow
packets that carry VLAN 100 to pass.
3. Configure a VLAN trunk between the master RSG and the Core.
portswitch
negotiation auto
undo shutdown
port link-type trunk//Configure the same link type on the master RSG and the
MBB core.
4. Configure a VRRP backup group on a VLANIF interface.

interface Vlanif100//Create a VLANIF interface.
ip binding vpn-instance LTE_S1
ip address 192.168.2.1 255.255.255.0//Configure an IP address for the VLANIF
interface.
vrrp vrid 100 virtual-ip 192.168.2.100//Create a VRRP backup group and
configure a virtual IP address as the MBB core-to-NodeB/eNodeB gateway IP
address.
vrrp vrid 100 priority 120//Set the priority of RSG5 to 120 in the VRRP backup
group to allow RSG5 to become the master device.
vrrp vrid 100 preempt-mode timer delay 180//Set the preemption delay to 180s
for RSG5 in the VRRP backup group.
direct-route track vrrp vrid 100 degrade-cost 100//Associate the interface
cost with the VRRP backup group to ensure that the routes to the master
device's interface are preferred.
5. Configure BFD.
l # Configure BFD for VRRP.
bfd vrrp bind peer-ip 192.168.2.2 vpn-instance LTE_S1 interface Vlanif100

source-ip 192.168.2.1
min-tx-interval 50
min-rx-interval 50
commit
l # Configure BFD to detect the status of the remote RSG.

If there are multiple links between RSGs, bundle these links into an Eth-Trunk, and then
run the bfd bind peer-ip default-ip command to detect the status of the physical
interfaces connecting the RSGs. This is to allow a member interface to go Down when
a single fiber fails, preventing packet loss (including VRRP packet loss).
bfd link_01 bind peer-ip default-ip interface gigabitethernet 1/0/1
min-tx-interval 10

VPN) Solution
min-rx-interval 10
commit
6. Set the VRRP recovery delay.

vrrp recover-delay 60//Set the delay for restoring the status of a VRRP backup
group to 60 seconds.
Configuring the Backup RSG

# Configure VRRP on RSG6.
1. Create VLANs.
vlan batch 100
2. Configure a VLAN trunk between the master and backup RSGs.

interface Eth-Trunk 1
portswitch
undo shutdown
port link-type trunk
3. Configure a VLAN trunk between the master RSG and the MBB Core.
portswitch
negotiation auto
undo shutdown
port link-type trunk
4. Configure a VRRP backup group on a VLANIF interface.

interface Vlanif100//Create a VLANIF interface.
ip binding vpn-instance LTE_S1
ip address 192.168.2.2 255.255.255.0
vrrp vrid 100 virtual-ip 192.168.2.100
vrrp vrid 100 track bfd-session VRRP increased 40//Configure a VRRP backup
group to track the BFD session status, achieving a master/backup VRRP
switchover.
direct-route track vrrp vrid 100 degrade-cost 100//Associate the interface
cost with the VRRP backup group to ensure that the routes to the master
device's interface are preferred.
5. Configure BFD.
l # Configure BFD for VRRP.
bfd vrrp bind peer-ip 192.168.2.1 vpn-instance LTE_S1 interface Vlanif100

source-ip 192.168.2.2
min-tx-interval 50
min-rx-interval 50
commit
l # Configure BFD to detect the status of the remote RSG.

If there are multiple links between RSGs, bundle these links into an Eth-Trunk, and then
run the bfd bind peer-ip default-ip command to detect the status of the physical
interfaces connecting the RSGs. This is to allow a member interface to go Down when
a single fiber fails, preventing packet loss (including VRRP packet loss).
bfd link_01 bind peer-ip default-ip interface gigabitethernet 1/0/1
min-tx-interval 10
min-rx-interval 10
commit
6. Set the VRRP recovery delay.

VPN) Solution
vrrp recover-delay 60//Set the delay for restoring the status of a VRRP backup
group to 60 seconds.

VPN) Solution
Configuration Guide(CLI) 6 Deploying TDM Service Bearer and Protection
6 Deploying TDM Service Bearer and

Protection
About This Chapter
Multi-segment PWs need to be created between CSGs and RSGs to bear TDM services.

This section describes the roadmap for configuring multi-segment PWs and PW protection for
TDM services.
6.2 Data Planning
To configure multi-segment PWs and PW protection, you need to know the following data.
6.3 Configuring Multi-segment PWs
This section describes how to create multi-segment PWs and configure the PWs to bear different
TDM services for service isolation.
6.4 Configuring BFD for PW
BFD for PW can speed up the traffic switchover between the primary and secondary PWs.
6.5 Configuring E-APS
Configuring E-APS on service interfaces allows APS switching between RSGs.

VPN) Solution

TDM services.
As shown in Figure 6-1, a multi-hop PW is established between the CSG and the RSG.
Figure 6-1 Multi-hop PW redundancy in the networking of CSG dual-homing to RSGs

1. Configuring service interfaces on the CSG and RSGs.
2. Configuring remote LDP sessions between the CSG and ASGs, between ASGs and RSGs,
and between RSGs
l Configuring remote LDP peer relationships between CSG1 and ASG3
l Configuring a remote LDP peer relationship between CSG1 and ASG4
l Configuring a remote LDP peer relationship between ASG3 and RSG5
l Configuring a remote LDP peer relationship between RSG5 and RSG6
3. Configuring multi-hop PW services
l Configuring service PWs on CSGs and RSGs, and PW switching on ASGs
l Configuring a bypass PW between RSGs
4. Configuring BFD for PW
l Configuring static BFD for PW between the CSG and the RSGs to speed up the
switchover between the primary PW and the backup PW.

VPN) Solution
CAUTION
If the ATM/TDM service and Ethernet service share the same hot-standby protection
tunnel, the detection period of BFD for PW must be longer than the switching delay for the
hot-standby LSP, preventing repeated switchover.
5. Configuring E-APS
Configuring E-APS between RSGs.
NOTE
In addition to configuring E-APS on RSGs, configuring E-APS on the core side (Base Station
Controllers) adjacent to the RSGs. For details on configurations of Base Station Controllers, refer to
the relevant product manual.
6.2 Data Planning

# Configure TDM service interfaces.
l Configure the TDM-encapsulated E1 channel at the CSG side. You can use either the E1
channel in clear channel mode or the E1 channel in channelized mode based on service and
bandwidth requirements.
Channel Type Description PW Encapsulation Type
Clear channel mode Unframed mode: All 32 satop-e1: is a protocol of

(structure-agnostic) timeslots can be used to TDM PWE3. This mode is
transmit valid data. not sensitive to TDM signal
(E1, E3, or other signals)
structures. It regards data as
bit streams at a fixed rate.
These bit streams are
encapsulated into data
packets to be transmitted
over PWs.
Channelized mode l Multiframed mode: cesopsn-basic: is a

(structure-aware) Timeslot 0 and timeslot protocol of TDM PWE3.
16 are used to transmit The Circuit Emulation
signaling. Timeslots 1 Service (CES) protocol is
to 15 and timeslots 17 to sensitive to E1 frame
31 are used to transmit structures. TDM signals
valid data. (E1, E3, or other signals)
l Framed mode: Timeslot can be encapsulated into
0 is used to transmit packets based on timeslots.
frame alignment data,

VPN) Solution
l Configure the TDM-encapsulated E1 channel on a CPOS interface at the RSG side based
on the channel type at the CSG side.
# Configure TDM PW services.
Table 6-1 TDM PW parameter description

Parameter Description
tdm-encapsulation-number 8 Indicates the number of TDM frames

encapsulated in a packet.
You can determine the number of TDM
frames encapsulated into each PW packet.
The smaller the number of frames
encapsulated into a packet, the shorter the
encapsulation and transmission delay but the
more the encapsulation overhead. The larger
the number of frames encapsulated into a
packet, the higher the bandwidth utilization
but the longer the encapsulation delay.
jitter-buffer depth 8 Indicates the depth of the jitter buffer,

namely, the allowed maximum jitter.
The shallower the jitter buffer is, the weaker
the anti-jitter capabilities are. The deeper the
jitter buffer is, the stronger the anti-jitter
capabilities are, but a long transmission delay
will be introduced when data flows are
reconstructed. Therefore, a too large or too
small jitter buffer is not conducive to high-
quality transmission of services.
NOTE
Table 6-2 Multi-hop PW parameters

mpls l2vpn — —

VPN) Solution
mpls ldp Remote LDP peer sessions LDP is enabled globally and
mpls ldp remote-peer are established between the remote LDP peer sessions are
ASG and the CSG, and created.
between the ASG and the In this example, TE tunnels
RSG. are configured between the
CSG and RSG. PWE3 uses
extended LDP signaling to
distribute VPN labels.
Therefore, a remote MPLS
LDP session has to be
configured between the CSG
and RSG.
mpls l2vc control-word PWs are configured between The primary/secondary PW

[ secondary| bypass] CSGs, ASGs and RSGs. or bypass PW is created with
the control word specified.
mpls l2vpn redundancy independent The negotiation mode of PW

redundancy is set to
independent .
mpls switch-l2vc PW switching is configured PW switching is configured.

on ASGs.
bfd bind pw pw-ttl auto- discriminator local BFD sessions are configured
calculate discriminator remote to monitor PWs in TTL mode
and the number of hops in a
min-tx-interval PW is calculated
min-rx-interval automatically.
of the live network.
Detection period=detection
multiple * sending/receiving
interval
If the tunnel is shared by
Ethernet services, the
detection period becomes
3*100 ms because TE hot-
standby is used. If the tunnel
is in independent mode, the
3*10 ms.
aps group APS group number An APS group is created and

an interface is added to the
APS group.

VPN) Solution
aps working 5.5.5.5 6.6.6.6 The interface added to the

Addresses of master and APS group is specified as the
slave RSGs as IP addresses of working interface.
local and remote interfaces in
the protection group.
aps protect 5.5.5.5 6.6.6.6 The interface added to the

slave RSGs as IP addresses of protection interface.
aps mode one2one APS is configured to work in

bidirection 1:1 mode, that is, only the
working link transmits
traffic, whereas the
protection link only transmits
traffic when the working link
is faulty.
APS is configured to work in
bidirectional mode, that is,
both the sender and the
receiver switch their traffic to
the protection link.
aps revert 1 The link switch-back time of

the APS group is set to 1
minute.

TDM services for service isolation.
Configuring the CSG

Configure the CSG on the access network. The following uses CSG1 as an example.
1. Enable MPLS L2VPN globally.

mpls l2vpn
2. Set up remote LDP sessions.

mpls ldp//Enable MPLS LDP before setting up MPLS LDP sessions.
graceful-restart
#
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
#

VPN) Solution
mpls ldp remote-peer 4.4.4.4

remote-ip 4.4.4.4
3. Configure a PW profile.
pw-template tdm//Create a PW profile for TDM services.
control-word//Enable the control word for TDM services to help transmit alarm
and clock information.
tnl-policy IPRAN//Configure the tunnel policy for PWs.
jitter-buffer depth 8//Set the depth of the jitter buffer to 8.
tdm-encapsulation-number 8//Set the number of TDM frames to be encapsulated
into a PW packet to 8, and the number must be the same on both ends of a PW.
4. Configure PWs.
controller E1 0/2/0
using e1//Configure the clear channel mode.
# interface Serial0/2/0:0 //Enter the view of the serial interface
corresponding to the E1 channel, and the serial interface number should
correspond to the E1 interface.
link-protocol tdm //Configure the link protocol as TDM.
mpls l2vc 3.3.3.3 pw-template tdm 100//Specify the PW between CSG1 and the
master ASG as the primary PW.
mpls l2vc 4.4.4.4 pw-template tdm 101 secondary//Specify the PW between CSG1
and the backup ASG as the secondary PW.
mpls l2vpn redundancy independent//Configure PW redundancy. The combined use
of PW redundancy and the bypass PW can prevent network-side faults from
affecting the AC side .
mpls l2vpn stream-dual-receiving//Allow both the primary and secondary PWs to
receive packets. This prevents packet loss during traffic switchback to the
primary PW.
mpls l2vpn oam-mapping//Enable the mapping between the AC status and the
network side status

# Configure the primary PW on ASG3.
mpls l2vpn

mpls ldp
graceful-restart
#
remote-ip 1.1.1.1
#
remote-ip 5.5.5.5
3. Configure PW switching.
mpls switch-l2vc 5.5.5.5 200 tunnel-policy IPRAN between 1.1.1.1 100 tunnel-
policy IPRAN encapsulation satop-e1 control-word-transparent//Configure PW
switching for the primary PW of which the encapsulation mode is satop-e1.

# Configure the secondary PW on ASG4.
mpls l2vpn

mpls ldp
graceful-restart

VPN) Solution
#
remote-ip 1.1.1.1
#
remote-ip 6.6.6.6
policy IPRAN encapsulation satop-e1 control-word-transparent//Configure PW
switching for the secondary PW.

# Configure the primary PW on RSG5.
mpls l2vpn

mpls ldp
graceful-restart
#
remote-ip 3.3.3.3
#
remote-ip 6.6.6.6
pw-template tdm
control-word
tnl-policy IPRAN
jitter-buffer depth 8
tdm-encapsulation-number 8
4. Configure PWs.
link-protocol tdm
mpls l2vc 3.3.3.3 pw-template tdm 200//Configure the primary PW.
mpls l2vc 6.6.6.6 pw-template tdm 1000 bypass//Configure the bypass PW.
mpls l2vpn oam-mapping
#

# Configure the secondary PW on RSG6.
mpls l2vpn

mpls ldp
graceful-restart
#
remote-ip 4.4.4.4
#
remote-ip 5.5.5.5
pw-template tdm
control-word

VPN) Solution
tnl-policy IPRAN
jitter-buffer depth 8
tdm-encapsulation-number 8
4. Configure a serial interface on the CPOS interface.

undo shutdown
cpos-trunk 0//Configure a CPOS-Trunk interface.
interface Cpos-Trunk0
e1 1 unframed//Configure the TDM interface on the RSG to use the same channel
type as the interface on the CSG.
5. Configure PWs.
link-protocol tdm
mpls l2vc 4.4.4.4 pw-template tdm 201
mpls l2vc 5.5.5.5 pw-template tdm 1000 bypass
mpls l2vpn oam-mapping
#

Check PW connectivity.
l Run the ping vc command on CSG1 and RSGs to check PW connectivity.
<CSG1> ping vc satop-e1 100 control-word remote 5.5.5.5 200
Reply from 5.5.5.5: bytes=100 Sequence=1 time=1 ms

Reply from 5.5.5.5: bytes=100 Sequence=4 time=1 ms Reply from 5.5.5.5:
bytes=100 Sequence=5 time=1 ms
--- FEC: FEC 128 PSEUDOWIRE (NEW). Type = satop-e1, ID = 100 ping statistics
- --
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 1/1/1 ms
<RSG5> ping vc satop-e1 200 control-word remote 1.1.1.1 100

--- FEC: FEC 128 PSEUDOWIRE (NEW). Type = satop-e1, ID = 200 ping statistics
- --
0.00% packet loss
l Run the tracert vc command on CSG1 and RSGs to know information about the tunnels
that the PWs pass through and about outbound interfaces.
<CSG1> tracert vc satop-e1 100 control-word
tracert vc satop-e1 100 control-word
0 Ingress 10.1.3.2/[4113 4096 ]
1 10.1.3.2 1 ms Egress
<RSG5> tracert vc satop-e1 200 control-word

0 Ingress 10.3.5.1/[4112 4111 ]
1 10.3.5.1 3 ms Egress
Checking the PW status.

VPN) Solution
l Check L2VPN connections on CSG1 and RSGs. The result shows that an L2VC is set up
and is in the Up state between CSG1 and each RSG. The following lists the check results
on CSG1 and RSG5 as an example.
<CSG1> display mpls l2vc brief
*Client Interface : Serial0/2/0:0
Administrator PW : no
AC status : up
VC State : up
Label state : 0
Token state : 0
VC ID : 100
VC Type : SAT E1 over Packet
session state : up
Destination : 3.3.3.3
link state : up
TDM encapsulation number : 8
jitter-buffer : 8
idle-code : ff
rtp-header : disable
*Client Interface : Serial0/2/0:0

AC status : up
VC State : up
Label state : 0
Token state : 0
VC ID : 101
session state : up
link state : up
jitter-buffer : 8
idle-code :
ff rtp-header : disable
<RSG5> display mpls l2vc brief
*Client Interface : Trunk-Serial0/1:0
AC status : up
VC State : up
Label state : 0
Token state : 0
VC ID : 200
session state : up
link state : up
jitter-buffer : 8
idle-code : ff
*Client Interface : Trunk-Serial0/1:0

AC status : up
VC State : up
Label state : 0
Token state : 0
VC ID : 1000
session state : up
link state : up
jitter-buffer : 8
idle-code : ff

VPN) Solution

BFD for PW can speed up the traffic switchover between the primary and secondary PWs.
Configuring the CSG

# Configure BFD for the primary PW on CSG1.
bfd tdm_primary_pw bind pw interface Serial0/2/0:0 remote-peer 5.5.5.5 pw-ttl auto-
calculate//Configure BFD for the primary PW.
min-tx-interval 100
min-rx-interval 100
commit
# Configure BFD for the secondary PW on CSG1.

bfd tdm_secondary_pw bind pw interface Serial0/2/0:0 remote-peer 6.6.6.6 pw-ttl
auto-calculate//Configure BFD for the secondary PW.
min-tx-interval 100
min-rx-interval 100
commit

# Configure BFD for the primary PW on RSG5.
#
bfd
#
bfd tdm_primary_pw bind pw interface Trunk-Seria0/1:0 remote-peer 1.1.1.1 pw-ttl
auto-calculate
min-tx-interval 100
min-rx-interval 100
commit
#

# Configure BFD for the secondary PW on RSG6.
#
bfd
#
bfd tdm_secondary_pw bind pw interface Trunk-Seria0/1:0 remote-peer 1.1.1.1 pw-ttl
auto-calculate
min-tx-interval 100
min-rx-interval 100
commit
#

Run the display bfd session all for-pw command to view the BFD status.

VPN) Solution
successfully.
<CSG1> display bfd session all for-pw
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
150 150 --.--.--.-- Up S_PW(M) Serial0/2/0:0
200 200 --.--.--.-- Up S_PW(M) Serial0/2/0:0
--------------------------------------------------------------------------------
<RSG5> display bfd session all for-pw
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
150 150 --.--.--.-- Up S_PW(M) Trunk-Seria1/1:0
--------------------------------------------------------------------------------


Configure a service interface on RSG5 as the working interface.
undo shutdown
aps group 1//Create an APS group.
aps working 6.6.6.6 5.5.5.5//Specify the interface as the working interface in APS
group 1. The peer IP address is 6.6.6.6, and the local IP address is 5.5.5.5.
cpos-trunk 0

Configure a service interface on RSG6 as the protection interface.
undo shutdown
aps group 1
aps protect 5.5.5.5 6.6.6.6//Specify the interface as the protection interface in
APS group 1. The peer IP address is 5.5.5.5, and the local IP address is 6.6.6.6.
aps mode one2one bidirection//Set the APS switching mode to bidirectional 1:1.
aps revert 1//Set the delay time for switchback in the APS group to 1 minute.
cpos-trunk 0//The working interface and protection interface must be added to the
same trunk interface.
NOTE
E-APS needs to be configured on both RSGs and the Base Station Controller (BSC) connected to the RSGs.
For details on how to configure E-APS on the BSC, see the BSC manuals.

Run the display aps group 1 command to check APS group configurations.
[RSG5]display aps group 1
APS Group 1: Cpos1/3/0 working channel 1(Active)
APS protection channel is 6.6.6.6
--------------------------------------------------------------------------------
Group Work-Channel Protect-Channel Wtr W-State P-State Switch-Cmd Switch-Result
--------------------------------------------------------------------------------
1 Cpos1/3/0 6.6.6.6 NA ok ok NA idle

VPN) Solution
--------------------------------------------------------------------------------
total entry: 1
APS Group 1: APS working channel is 5.5.5.5
Cpos1/0/0 protection channel 0(Inactive)
Bidirection, 1:1 mode, Revert time(1 minutes)
KeepAlive Timer: 1(seconds), Hold Timer: 180(seconds)
No Request on Both Working and Protection Side
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
1 5.5.5.5 Cpos1/0/0 1 ok ok NA idle
--------------------------------------------------------------------------------
total entry: 1

VPN) Solution
Configuration Guide(CLI) 7 Deploying ATM Service Bearer and Protection
7 Deploying ATM Service Bearer and

Protection
About This Chapter
Multi-segment PWs need to be created between CSGs and RSGs to bear ATM services.

ATM services.
7.2 Data Planning
ATM services for service isolation.
If the primary PW fails, BFD for PW can detect the fault and implement a PW switchover within
milliseconds.

VPN) Solution

ATM services.
As shown in Figure 7-1, a multi-hop PW is established between the CSG and the RSG.
Figure 7-1 Multi-hop PW redundancy in the networking of CSG dual-homing to RSGs

1. Configuring service interfaces on the CSG and RSGs.
2. Configuring remote LDP sessions between the CSG and ASGs, between ASGs and RSGs,
and between RSGs
l Configuring remote LDP peer relationships between CSG1 and ASG3
l Configuring a remote LDP peer relationship between CSG1 and ASG4
l Configuring a remote LDP peer relationship between RSG5 and RSG6
3. Configuring multi-hop PW services
l Configuring service PWs on CSGs and RSGs, and PW switching on ASGs
l Configuring a bypass PW between RSGs
4. Configuring BFD for PW
l Configuring static BFD for PW between the CSG and the RSGs to speed up the
switchover between the primary PW and the backup PW.

VPN) Solution
CAUTION
If the ATM/TDM service and Ethernet service share the same hot-standby protection
tunnel, the detection period of BFD for PW must be longer than the switching delay for the
hot-standby LSP, preventing repeated switchover.
5. Configuring E-APS
Configuring E-APS between RSGs.
NOTE
In addition to configuring E-APS on RSGs, configuring E-APS on the core side (Base Station
Controllers) adjacent to the RSGs. For details on configurations of Base Station Controllers, refer to
the relevant product manual.
7.2 Data Planning

# Configure ATM service interfaces.
l Configure the ATM-encapsulated E1 channel at the CSG side. You can use only the E1
channel in channelized mode based on service and bandwidth requirements.
Channel Type Description PW Encapsulation Type
Channelized mode l Multiframed mode: l atm-1to1-vcc

(structure-aware) Timeslot 0 and timeslot l atm-1to1-vpc
16 are used to transmit
signaling. Timeslots 1 l atm-nto1-vcc
to 15 and timeslots 17 to l atm-nto1-vpc
31 are used to transmit
valid data.
l Framed mode: Timeslot
0 is used to transmit
frame alignment data,
l Add ATM-encapsulated synchronous serial interfaces to an Inverse Multiplexing over

ATM (IMA) group and create a PVC to an RSG on a sub-interface in the IMA group.
L2VPN provides four emulation services for ATM cell relay on serial interfaces or sub-
interfaces in an IMA group.

Mode interface in an Connection
IMA Group
1-to-1 VCC A PW transmits P2P PVC: vpi/vci

cells of one ATM
VCC.

VPN) Solution

Mode interface in an Connection
IMA Group
1-to-1 VPC A PW transmits P2P PVP: vpi

cells of one ATM
VPC.
N-to-1 VCC A PW transmits P2MP PVC: vpi/vci

cells of multiple
ATM VCCs.
N-to-1 VPC A PW transmits P2MP PVP: vpi

cells of multiple
ATM VPCs.
l Configure ATM interfaces at the RSG side based on the PVC created at the CSG side.
# Configure ATM PW services.
Table 7-1 ATM parameter description

Parameter Description
max-atm-cells 1 Maximum number of cells that are

encapsulated into a packet
NOTE
Table 7-2 Multi-hop PW parameters

mpls l2vpn — —
mpls ldp Remote LDP peer sessions LDP is enabled globally and
mpls ldp remote-peer are established between the remote LDP peer sessions are
ASG and the CSG, and created.
between the ASG and the In this example, TE tunnels
RSG. are configured between the
CSG and RSG. PWE3 uses
extended LDP signaling to
distribute VPN labels.
Therefore, a remote MPLS
LDP session has to be
configured between the CSG
and RSG.

VPN) Solution
mpls l2vc control-word PWs are configured between The primary/secondary PW

[ secondary| bypass] CSGs, ASGs and RSGs. or bypass PW is created with
the control word specified.
mpls l2vpn redundancy independent The negotiation mode of PW

redundancy is set to
independent .
mpls switch-l2vc PW switching is configured PW switching is configured.

on ASGs.
bfd bind pw pw-ttl auto- discriminator local BFD sessions are configured
calculate discriminator remote to monitor PWs in TTL mode
and the number of hops in a
min-tx-interval PW is calculated
min-rx-interval automatically.
of the live network.
Detection period=detection
multiple * sending/receiving
interval
If the tunnel is shared by
Ethernet services, the
3*100 ms because TE hot-
standby is used. If the tunnel
is in independent mode, the
3*10 ms.
aps group APS group number An APS group is created and

an interface is added to the
APS group.
aps working 5.5.5.5 6.6.6.6 The interface added to the

slave RSGs as IP addresses of working interface.
aps protect 5.5.5.5 6.6.6.6 The interface added to the

slave RSGs as IP addresses of protection interface.

VPN) Solution
aps mode one2one APS is configured to work in

bidirection 1:1 mode, that is, only the
working link transmits
traffic, whereas the
protection link only transmits
traffic when the working link
is faulty.
APS is configured to work in
bidirectional mode, that is,
both the sender and the
receiver switch their traffic to
the protection link.
aps revert 1 The link switch-back time of

the APS group is set to 1
minute.

ATM services for service isolation.
Configuring the CSG

Configure the CSG on the access network. The following uses CSG1 as an example.
mpls l2vpn

mpls ldp//Enable MPLS LDP before setting up MPLS LDP sessions.
graceful-restart
#
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
#
remote-ip 4.4.4.4
pw-template atm
max-atm-cells 1 //Set the maximum number of cells to be encapsulated into a
packet to 1.
control-word//Enable the control word for ATM services to transmit alarm and
clock information.
tnl-policy IPRAN
4. Configure PWs.
interface Ima-group0/2/1.2 p2p//Configure ATM cell relay in 1-to-1 VCC mode on
a sub-interface in an IMA group.
pvc 1/100
map pvc 1/100 bidirectional//Configure the mapping between the local VPI/VCI

VPN) Solution
and its peer VPI/VCI.

mpls l2vc 3.3.3.3 pw-template atm 300 //Specify the PW between CSG1 and the
master ASG as the primary PW.
mpls l2vc 4.4.4.4 pw-template atm 301 secondary//Specify the PW between CSG1
and the backup ASG as the secondary PW.
mpls l2vpn redundancy independent//Configure PW redundancy. The combined use
of PW redundancy and the bypass PW can prevent network-side faults from
affecting the AC side.
mpls l2vpn stream-dual-receiving//Allow both the primary and secondary PWs to
receive packets. This prevents packet loss during traffic switchback to the
primary PW.

# Configure the primary PW on ASG3.

mpls l2vpn

mpls ldp
graceful-restart
# mpls ldp remote-peer 1.1.1.1
remote-ip 1.1.1.1
#
remote-ip 5.5.5.5
policy IPRAN encapsulation atm-1to1-vcc control-word-transparent//Configure PW
switching for the primary PW of which the encapsulation mode is atm-1to1-vcc.

# Configure the secondary PW on ASG4.

mpls l2vpn

mpls ldp
graceful-restart
#
remote-ip 1.1.1.1
#
remote-ip 6.6.6.6
policy IPRAN encapsulation atm-1to1-vcc control-word-transparent//Configure PW
switching for the secondary PW. #

# Configure the primary PW on RSG5.

mpls l2vpn

VPN) Solution
mpls ldp
graceful-restart
#
remote-ip 3.3.3.3
#
remote-ip 6.6.6.6
pw-template atm
max-atm-cells 1
control-word
tnl-policy IPRAN
4. Configure PWs.
#
interface Atm-Trunk1.1 p2p
pvc 1/100//Configure the mapping between the local VPI/VCI and the VPI/VCI on
CSG1.
mpls l2vc 3.3.3.3 pw-template atm 500 //Configure the primary PW.
mpls l2vc 6.6.6.6 pw-template atm 2000 bypass//Configure the bypass PW.
#

# Configure the secondary PW on RSG6.
mpls l2vpn

mpls ldp
graceful-restart
#
remote-ip 4.4.4.4
#
remote-ip 5.5.5.5
pw-template atm
max-atm-cells 1
control-word
tnl-policy IPRAN
4. Configure PWs.
interface Atm-Trunk1.1 p2p
pvc 1/100
mpls l2vc 4.4.4.4 pw-template atm 501
mpls l2vc 5.5.5.5 pw-template atm 2000 bypass
#

Check PW connectivity.
l Run the ping vc command on CSG1 and RSGs to check PW connectivity.
<CSG1> ping vc atm-1to1-vcc 300 control-word remote 5.5.5.5 500

VPN) Solution

--- FEC: FEC 128 PSEUDOWIRE (NEW). Type = atm-1to1-vcc, ID = 300 ping
statisti cs ---
0.00% packet loss
<RSG5> ping vc atm-1to1-vcc 500 control-word remote 1.1.1.1 300
--- FEC: FEC 128 PSEUDOWIRE (NEW). Type = atm-1to1-vcc, ID = 500 ping
statisti cs ---
0.00% packet loss
l Run the tracert vc command on CSG1 and RSGs to know information about the tunnels
that the PWs pass through and about outbound interfaces.
<CSG1> tracert vc atm-1to1-vcc 300 control-word
0 Ingress 10.1.3.2/[4115 4096 ]
1 10.1.3.2 1 ms Egress
<RSG5> tracert vc atm-1to1-vcc 500 control-word
0 Ingress 10.3.5.1/[4114 4111 ]
1 10.3.5.1 12 ms Egress
Check the PW status.
l Check L2VPN connections on CSG1 and RSGs. The result shows that an L2VC is set up
and is in the Up state between CSG1 and each RSG. The following lists the check results
on CSG1 and RSG5 as an example.
<CSG1> display mpls l2vc brief
*Client Interface : Ima-group0/2/1.1
AC status : up
VC State : up
Label state : 0
Token state : 0
VC ID : 300
VC Type : ATM 1to1 VCC
session state : up
link state : up
max ATM cells : 1
ATM pack overtime : 1000
seq-number : disable
*Client Interface : Ima-group0/2/1.1

AC status : up
VC State : up
Label state : 0
Token state : 0
VC ID : 301
session state : up
link state : up

VPN) Solution
max ATM cells : 1

<RSG5> display mpls l2vc brief
*Client Interface : Atm-Trunk1.1
AC status : up
VC State : up
Label state : 0
Token state : 0
VC ID : 500
session state : up
link state : up
max ATM cells : 1
*Client Interface : Atm-Trunk1.1

AC status : up
VC State : up
Label state : 0
Token state : 0
VC ID : 2000
session state : up
link state : up
max ATM cells : 1

If the primary PW fails, BFD for PW can detect the fault and implement a PW switchover within
milliseconds.
Configuring the CSG

# Configure BFD for the primary PW on CSG1.
bfd atm_primary_pw bind pw interface Ima-group0/2/1.1 remote-peer 5.5.5.5 pw-ttl
auto-calculate//Configure BFD for the primary PW.
min-tx-interval 100
min-rx-interval 100
commit
# Configure BFD for the secondary PW on CSG1.

bfd tdm_secondary_pw bind pw interface Ima-group0/2/1.1 remote-peer 6.6.6.6 pw-ttl
auto-calculate//Configure BFD for the secondary PW.
min-tx-interval 100
min-rx-interval 100
commit

# Configure BFD for the primary PW on RSG5.

VPN) Solution
bfd atm_primary_pw bind pw interface Atm-Trunk1.1 remote-peer 1.1.1.1 pw-ttl auto-

calculate
min-tx-interval 100
min-rx-interval 100
commit

# Configure BFD for the secondary PW on RSG6.
#
bfd
#
bfd tdm_secondary_pw bind pw interface Atm-Trunk1.1 remote-peer 1.1.1.1 pw-ttl auto-
calculate
min-tx-interval 100
min-rx-interval 100
commit
#

Run the display bfd session all for-pw command to view the BFD status.
successfully.
<CSG1> display bfd session all for-pw
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
100 100 --.--.--.-- Up S_PW(M) Ima-group0/2/1.1
200 200 --.--.--.-- Up S_PW(M) Ima-group0/2/1.1
--------------------------------------------------------------------------------
<RSG5> display bfd session all for-pw
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
100 100 --.--.- -.-- Up S_PW(M) Atm-Trunk1.1
--------------------------------------------------------------------------------


Configure a service interface on RSG5 as the working interface.
interface Atm3/0/0
undo shutdown
aps group 2//Create an APS group and add the interface to the group.
aps working 6.6.6.6 5.5.5.5//Specify the interface as the working interface in APS
group 2. The peer IP address is 6.6.6.6, and the local IP address is 5.5.5.5.
atm-trunk 1//The working interface and protection interface must be added to the
same trunk interface.

VPN) Solution

Configure a service interface on RSG6 as the protection interface.
interface Atm3/0/0
undo shutdown
aps group 2
aps protect 5.5.5.5 6.6.6.6//Specify the interface as the protection interface in
APS group 2. The peer IP address is 5.5.5.5, and the local IP address is 6.6.6.6.
aps mode one2one bidirection//Set the APS switching mode to bidirectional 1:1.
aps revert 1//Set the delay time for switchback in the APS group to 1 minute.
atm-trunk 1
NOTE
E-APS needs to be configured on both RSGs and the Base Station Controller (BSC) connected to the RSGs.
For details on how to configure E-APS on the BSC, see the BSC manuals.

Run the display aps group 2 command to check APS group configurations.
APS Group 2: Atm1/0/0 working channel 1(Active)
APS protection channel is 6.6.6.6
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
2 Atm1/0/0 6.6.6.6 NA ok ok NA idle
--------------------------------------------------------------------------------
APS Group 2: APS working channel is 5.5.5.5
Atm1/1/0 protection channel 0(Inactive)
Bidirection, 1:1 mode, Revert time(1 minutes)
KeepAlive Timer: 1(seconds), Hold Timer: 180(seconds)
No Request on Both Working and Protection Side
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
2 5.5.5.5 Atm1/1/0 1 ok ok NA idle
--------------------------------------------------------------------------------
total entry: 1

VPN) Solution
Configuration Guide(CLI) 8 Deploying QoS
8 Deploying QoS
About This Chapter
This chapter describes the roadmap, data planning, and procedure for configuring QoS in the
DiffServ model.
8.1 Deploying QoS for Ethernet Services

This section describes the roadmap, data planning, and procedure for configuring QoS for
Ethernet services using the DiffServ model.
8.2 Deploying QoS for ATM Services
This section describes the roadmap, data planning, and procedure for configuring QoS for ATM
services using the DiffServ model.

VPN) Solution
8.1 Deploying QoS for Ethernet Services

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

This section describes the QoS configuration roadmap for Ethernet services.
l Configure priority mapping in the DiffServ domain.
– Map the IP DSCP value or VLAN 802.1p priority of each wireless service packet into
the Class of Service (CoS) on the AC-side interfaces of the ATN device and CX600.
– Map the MPLS EXP value of each packet into the CoS on the interfaces of the ATN
device and CX600 in the MPLS domain.
l Limit the traffic rate on the AC-side interfaces.
– Use a QoS profile to define CAR parameters and apply the profile to the AC-side
interfaces.
8.1.2 Data Planning

To configure QoS, plan the following data.
NOTE
The data provided in this section is used as an example and for reference, which may be different from that
in real world situations because the network scale and topology may differ.
Table 8-1 Mappings in the DiffServ domain

Device Name Direction Priority Priority CoS Color
Type Value
CSG1 ds-uni Inbound DSCP 62 CS6 Green

RSG5
Inbound DSCP 14 AF1 Green
RSG6
Table 8-2 QoS profile and flow queues on the ATN device
Device Name Normal Queue Scheduli Rate of Weight
Role Conditio Priority ng Mode Traffic
n Shaping
(kbit/s)
CSG1 csg-uni CIR: 4000 CS6 PQ 500 -

PIR: 4000
EF PQ 2000 -
Direction:
inbound AF4 WFQ - 15

VPN) Solution
Device Name Normal Queue Scheduli Rate of Weight

Role Conditio Priority ng Mode Traffic
n Shaping
(kbit/s)
BE WFQ - 10
Table 8-3 QoS profile and flow queues on the CX600

Device Name Queue Scheduli Rate of PIR Weight
Role Priority ng Mode Traffic (Byte)
Shaping
(kbit/s)
RSG5 rsg-uni CS6 PQ 50 - -

RSG6
EF PQ 200 - -
AF1 WFQ 200 400 10
AF2 WFQ 200 400 10
AF3 WFQ 200 400 15
AF4 WFQ 200 400 15
BE WFQ 200 400 10
8.1.3 Configuring Priority Mapping

Priority mapping is configured to allow packets from the wireless side to enter correct queues
on the bearer network.
To use default priority mappings, run the trust upstream default command on each interface.
Configuring the CSG

1. Configure a DiffServ domain.
#
diffserv domain ds-uni//Create a DiffServ domain. The default mapping will be
used if the mapping is not modified in the domain. Run the display diffserv
domain command to view default priority mappings.
ip-dscp-inbound 14 phb af1 green//Configure a CoS for incoming IP packets with
a specified DSCP value in the domain and color the packets.
ip-dscp-inbound 62 phb cs6 green
#
2. Bind the DiffServ domain to interfaces.

#
interface Ethernet0/3/0//Enter the view of the AC-side interface.
trust upstream ds-uni//Bind the DiffServ domain to the interface. Priority
mapping will be performed for the packets that enter the interface based on the
mappings of the domain.
#

VPN) Solution
trust upstream default

#
trust upstream default
#
ip vpn-instance ipran
ipv4-family
egress priority-mapping pipe//Specifies the MPLS Diff-Serv mode in the
downstream direction as pipe. That is, when labels are stripped off from the
packets, the equipment does not write the internal scheduling priorities back
to user packets.
#
Configuring the ASG

Run the trust upstream default command on each interface. You only need to configure
mappings between MPLS EXP values and CoSs.
Configuring the RSG

The RSG configuration is similar to the CSG configuration.
l Run the trust upstream ds-uni command on the AC-side interface.
l Run the trust upstream default command on the MPLS-aware interface.
8.1.4 Configuring Queue Scheduling and Bandwidth

Different scheduling modes and bandwidth assurance can be configured for different queues to
ensure the good quality of high-priority services.
Configuring the CSG

1. Configure a flow queue profile and a QoS profile.
#
flow-queue csg-uni//Create 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//Change the scheduling mode for the flow queues. 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 csg-uni//Configure a QoS profile.
user-queue cir 10000 pir 20000 flow-queue csg-uni//Configure the queue
bandwidth and apply the bandwidth to flow queues.
#
2. # Apply the QoS profile to an interface.

#
interface Ethernet0/3/0.1//Enter the view of the AC-side interface.
qos-profile csg-uni inbound
#
Configuring the ASG

The ASG configuration is not required.
Configuring the RSG

1. Configure queue scheduling parameters on the AC-side interface.

VPN) Solution
#
interface GigabitEthernet1/0/2//Enter the view of the AC-side interface. port-
queue be wfq weight 10 shaping 200 outbound//Configure queue scheduling
parameters. In this example, weighted fair queuing (WFQ) is used for EF queues.
The weight is set to 10, and the traffic shaping rate is set to 10 Mbit/s.
port-queue af1 wfq weight 10 shaping 200 outbound
port-queue ef pq shaping 200 outbound
port-queue cs6 pq shaping 50 outbound
#
8.2 Deploying QoS for ATM Services

This section describes the roadmap, data planning, and procedure for configuring QoS for ATM
services using the DiffServ model.
8.2.1 Configuration Roadmap

This section describes the QoS configuration roadmap for ATM services.
Configure different Constant Bit Rate (CBR), Variable Bit Rate non-real-time (VBR-nrt), and
Variable Bit Rate real-time (VBR-rt) values for different types of services on the ATN device
and CX600.
8.2.2 Data Planning

To configure QoS, plan the following data.
NOTE
The data provided in this section is used as an example and for reference, which may be different from that
in real world situations because the network scale and topology may differ.
Table 8-4 ATM QoS data planning

Interfaces Parameter Value Remarks
Ima-group 0/2/0.1 on Service name/ cbr -

CSG1 Service type
PIR (kbit/s) 1000 -
Cell delay (us) 500 -
ATM 3/0/0 on RSG5 Service name/ cbr -

Service type
PIR (kbit/s) 100000 -
Cell delay (us) 50000 -

VPN) Solution
8.2.3 Configuring Traffic Shaping

Traffic shaping can be configured to provide different bandwidth assurance for different
services.
Configuring the CSG

1. Specify a service type and configure relevant parameters.
#
atm service csg cbr 1000 500//Set the service type to CBR, the PIR to 1000
kbit/s, and the cell delay to 500 us.
#
2. Specify a PVC.
#
interface Ima-group0/2/0.1
pvc 20/60
service output csg
#
Configuring the ASG

The ASG configuration is not required.
Configuring the RSG

1. Specify a service type and configure relevant parameters.
#
atm service rsg cbr 100000 50000
#
2. Specify a PVC.
#
interface Atm3/0/0
undo shutdown
pvc 20/60
service output rsg
#

VPN) Solution
Configuration Guide(CLI) 9 Deploying the Clock
9 Deploying the Clock
About This Chapter
This chapter describes the roadmap, data planning, and procedure for configuring 1588v2 and
synchronization Ethernet to achieve time and frequency synchronization.

This section describes the roadmap for configuring 1588v2 and synchronization Ethernet.
9.2 Data Planning
You need to plan the data before configuring the clock.
9.3 Selecting the Clock Source
Devices on the entire network need to be configured to trace the same clock source.
9.4 Configuring Synchronization Ethernet to Achieve Frequency Synchronization
Synchronization Ethernet can be used to achieve frequency synchronization on a network.
9.5 Configuring 1588v2 to Achieve Time Synchronization
1588v2 can be used to achieve time synchronization on a network.

VPN) Solution

This section describes the roadmap for configuring 1588v2 and synchronization Ethernet.
Multiple technologies can be used to transparently transmit clock information. Using 1588v2 to
achieve time synchronization and using synchronization Ethernet to achieve frequency
synchronization are recommended.
Figure 9-1 Networking diagram for clock deployment

M a s te r
B IT S
C lo c k p ri 1
C S G 1 C lo c k p ri 1 C lo c k p ri 3 A S G 3 C lo c k p ri 1 C lo c k p ri 3 RSG5
G E 0 /1 /1 G E 1 /1 /2 G E 1 /1 /0 G E 1 /0 /0
G E 0 /1 /0 G E 1 /1 /1 G E 1 /0 /1
C lo c k p ri 2 C lo c k p ri 2 C lo c k p ri 2
C lo c k p ri 2 C lo c k p ri 2 C lo c k p ri 1
G E 0 /1 /0 G E 1 /1 /1 G E 1 /0 /1
G E 0 /1 /1 G E 1 /1 /2 G E 1 /1 /0 G E 1 /0 /0
C S G 2 C lo c k p ri 1 C lo c k p ri 3 A S G 4 C lo c k p ri 1 C lo c k p ri 2 RSG6
C lo c k p ri 3
Im p o rt th e c lo c k
C lo c k p ri n P rio rity o f th e c lo c k s o u rc e o n th e in te rfa c e
S la v e
B IT S
The networking is shown in Figure 9-1. The configuration roadmap is as follows:
l Configure master and slave BITS devices to prevent single point failures from interrupting
clock transmission and configure RSG5 and RSG6 to select the normal clock source.
l Configure the BITS connected to RSG5 as the master clock to provide a reference clock
for the entire network.
– Configure synchronization Ethernet to achieve frequency synchronization.
– Configure 1588v2 to achieve time synchronization.
l Configure the ATN device to transmit the clock information to the base transceiver station
(BTS). The common scenarios are described below:
– The clock interface on the ATN device is directly connected to the BTS.
– Synchronization Ethernet or 1588v2 is used on the Ethernet interface to transmit clock
information to the BTS. The BTS is required to support synchronization Ethernet or
1588v2. The configuration on the BTS 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.
9.2 Data Planning

You need to plan the data before configuring the clock.

VPN) Solution
Assign a high priority to the interface that connects to the master clock. Note that the smaller
the value, the higher the priority.
9.3 Selecting the Clock Source

Devices on the entire network need to be configured to trace the same clock source.
The BITS connected to RSG5 is the master BITS.
Configuring RSG5
1. Select a clock source.
#
clock bits-type bits0 2mhz//Specify the type of the clock signal from the
external reference clock source. 2 MHz signals are used in this example.
clock bits-type bits1 1pps input nmea//Specify the type of the clock signal
from the external reference clock source. ASCII signals (1PPS+RS422) are used
in this example.
clock source bits0 priority 1//Assign the highest clock priority to interface
bits0 that connects to the master BITS. The smaller the value, the higher the
priority. If multiple clock sources exist on the network, assigning different
priorities to the interfaces connected to the clock sources is recommended.
clock source bits0 ssm prc//Configure the SSM level for the reference clock
source. prc is the highest level.
clock source ptp ssm unk//This command does not need to be configured if
1588v2 will not be deployed.
clock source bits0 synchronization enable//Enable clock synchronization. The
device will trace a clock source only after clock synchronization is enabled.
clock source ptp synchronization enable//This command does not need to be
configured if 1588v2 will not be deployed.
clock ssm-control on//Enable SSM control in clock source selection so that the
clock source is selected based on SSM levels. By default, SSM control is
enabled.
clock bits output-threshold dnu//Set the lower threshold, namely, the lowest
quality level, of the clock signals output by the BITS. dnu is the default
setting.
#
Configuring RSG6
#
clock bits-type bits0 2mhz
clock bits-type bits1 1pps input nmea
clock source bits0 priority 3//Assign a low clock priority to the interface
connected to the slave BITS on RSG6. The priority should be lower than that of
other interfaces that receive clock information from other devices using 1588v2
or synchronization Ethernet. This ensures that all devices on the network trace
the same clock source.
clock source bits0 ssm prc
clock source ptp ssm unk
clock source bits0 synchronization enable
clock source ptp synchronization enable
clock ssm-control on
clock bits output-threshold dnu
#
Configuring the CSG and ASG


VPN) Solution
#
clock source ptp synchronization enable
#

Verify that the correct clock source is configured on all devices. The following uses the
verification on RSG5 as an example:
<HUAWEI> display clock source
9.4 Configuring Synchronization Ethernet to Achieve

Frequency Synchronization
Synchronization Ethernet can be used to achieve frequency synchronization on a network.
Configuring the CSG

The following uses the configuration on CSG1 as an example:
1. Configure synchronization Ethernet in the system view and interface view.
#
clock ethernet-synchronization enable//Enable synchronization Ethernet in the
system view.
#
undo shutdown
clock priority 2//Assign a clock priority to the interface. This will affect
clock selection in the inbound direction on the local end. The smaller the
value, the higher the priority. Assigning the highest priority to each
interface on the shortest path for clock signal transmission is recommended.
clock synchronization enable//Enable synchronization Ethernet in the
interface view.
#
undo shutdown
clock priority 1//The path from the interface is the shortest one to the BITS.
Setting the highest priority is recommended.
clock synchronization enable
#
Configuring the ASG and RSG

The ASG and RSG configurations are similar to the CSG configuration:
l Enable synchronization Ethernet in the system view and interface view.
l Configure clock priorities on interfaces.
9.5 Configuring 1588v2 to Achieve Time Synchronization

1588v2 can be used to achieve time synchronization on a network.
Configuring the CSG

1. Configure 1588v2 in the system view.
#
ptp enable//Enable 1588v2 in the system view.

VPN) Solution
ptp domain 1//Configure the 1588v2 clock domain. All devices must be added to
the same 1588v2 clock domain.
ptp device-type bc//Configure the device type as BC. Configuring all devices
on the network as BCs is recommended in this solution.
ptp clock-source local priority1 80
#
2. Configure 1588v2 in the interface view.

#
ptp delay-mechanism pdelay//Configure the delay measurement mechanism as
Pdelay. Pdelay calculates the time difference based on the link delay of the
master and slave clocks.
ptp enable//Enable 1588v2 in the interface view.
#
ptp delay-mechanism pdelay
ptp enable
#
Configuring the ASG

The ASG configuration is similar to the CSG configuration.
l Enable 1588v2 in the system view and interface view.

l Add all ASGs to the same 1588v2 domain.
l Configure the device type of all ASGs as BC.
l Configure the same delay measurement mechanism on all ASGs.
Configuring RSG5
#
ptp enable
ptp domain 1
ptp device-type bc
ptp clock-source bits1 priority1 1//Increase the first priority (priority1) of the
time source. The smaller the value, the higher the priority. The default value is
128. When the BMC algorithm is used by a 1588v2-enabled device for master clock
selection, priority1 of each candidate time source is compared first, then the
clock class, clock accuracy, and priority2. If priority1 of candidate time sources
is the same, the clock class is compared, and so on. The time source with the
highest priority is selected as the master clock. For details on how to configure
other parameters, see the relevant ATN and CX product manuals.
#
Configuring RSG6
#
ptp enable
ptp domain 1
ptp device-type bc
ptp clock-source bits1 priority1 2//Increase the first priority (priority1) of the
time source. The smaller the value, the higher the priority. The default value is
128. When the BMC algorithm is used by a 1588v2-enabled device for master clock
selection, priority1 of each candidate time source is compared first, then the
clock class, clock accuracy, and priority2. If priority1 of candidate time sources
is the same, the clock class is compared, and so on. The time source with the
highest priority is selected as the master clock. For details on how to configure
other parameters, see the relevant ATN and CX product manuals.
#

VPN) Solution

Verify that 1588v2 runs properly on all devices. The following uses the verification on RSG5
as an example:
<HUAWEI> display ptp all
Device config info
------------------------------------------------------------------
PTP state :enabled Domain value :0
Slave only :no Device type :BC
Set port state :no Local clock ID :286ed4fffeedfd31
Acl :no Virtual clock ID :no
Acr :no Time lock success :yes
BMC run info

------------------------------------------------------------------
Source port :bits1
Leap :None
UTC Offset :34
UTC Offset Valid :True
Port info
Name State Delay-mech Ann-timeout Type Domain
------------------------------------------------------------------------
GigabitEthernet1/0/0 master pdelay 9 BC 0
GigabitEthernet1/0/1 master pdelay 9 BC 0
Clock source info

Clock Pri1 Pri2 Accuracy Class TimeSrc Signal Switch Direction In-Status
------------------------------------------------------------------------
local 128 128 0x31 187 0xa0 - - - -
bits0 128 128 0x20 6 0x20 none off -/- abnormal
bits1 128 1 0x20 6 0x20 1pps on in/- normal
bits2 128 128 0x20 6 0x20 1pps off -/out abnormal


(For Customer) IPTime MBB Backhaul ATN+CX (Hierarchy VPN) Solution Configuration Guide (0 - 01, CLI)

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

(For Customer) IPTime MBB Backhaul ATN+CX (Hierarchy VPN) Solution Configuration Guide (0 - 01, CLI)

Hochgeladen von

Copyright:

Verfügbare Formate

HUAWEI IPTime MBB Backhaul ATN+CX (Hierarchy

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2011-09-20) Huawei Proprietary and Confidential i

About This Document

Issue 01 (2011-09-20) Huawei Proprietary and Confidential ii

About This Document.....................................................................................................................ii

5 Configuring Ethernet Service Bearer and Protection...........................................................44

6 Deploying TDM Service Bearer and Protection....................................................................60

Issue 01 (2011-09-20) Huawei Proprietary and Confidential iii

6.3 Configuring Multi-segment PWs......................................................................................................................65

7 Deploying ATM Service Bearer and Protection....................................................................73

9 Deploying the Clock...................................................................................................................91

Issue 01 (2011-09-20) Huawei Proprietary and Confidential iv

About This Chapter

1.1 Service Requirements and Networking

Issue 01 (2011-09-20) Huawei Proprietary and Confidential 1

1.1 Service Requirements and Networking

Table 1-1 Hierarchy VPN deployment

Solution H-VPN MS-PW

Service l LTE S1/X2 l 3G ATM

IGP Hierarchical IGP needs to be deployed between CSGs and

MPLS tunnel MPLS tunnels need to be established from CSGs to ASGs,

VPN Hierarchical L3VPN needs to Multi-hop PW needs to be

Protection switching Protection switching needs to be configured for nodes and

Issue 01 (2011-09-20) Huawei Proprietary and Confidential 2

Solution H-VPN MS-PW

Recommended protection Recommended protection

QoS End-to-end QoS needs to be configured between CSGs and

Clock synchronization End-to-end clock synchronization needs to be configured

Figure 1-1 Network topology

Issue 01 (2011-09-20) Huawei Proprietary and Confidential 3

Figure 1-2 IP network interface topology

Table 1-2 NE IP interface list

NE Role Local Interface IP Address Interface

CSG1 (ATN910- Loopback 0 1.1.1.1/32

GigabitEthernet 10.1.3.1/30 Interface description:

CSG2 (ATN950- Loopback 0 2.2.2.2/32

GigabitEthernet 10.2.4.1/30 Interface description:

ASG3 (CX600- Loopback 0 3.3.3.3/32

GigabitEthernet1/1/ 10.3.4.1/30 Interface description:

Issue 01 (2011-09-20) Huawei Proprietary and Confidential 4

NE Role Local Interface IP Address Interface

GigabitEthernet 10.3.4.5/30 Interface description:

GigabitEthernet 10.3.5.1/30 Interface description:

ASG4 (CX600- Loopback 0 4.4.4.4/32

GigabitEthernet1/1/ 10.3.4.2/30 Interface description:

GigabitEthernet 10.3.4.6/30 Interface description:

GigabitEthernet 10.4.6.1/30 Interface description:

RSG5 (CX600- Loopback 0 5.5.5.5/32

GigabitEthernet Eth-Trunk 1.1 Interface description:

GigabitEthernet vlan-type dot1q 1

RSG6 (CX600- Loopback 0 6.6.6.6/32

GigabitEthernet Eth-Trunk 1.1 Interface description:

GigabitEthernet vlan-type dot1q 1

Table 1-3 NE service interface list

CSG1 (ATN910- Ethernet0/3/0 192.168.100.1/24 Interface description:

Ethernet0/3/1 192.168.101.1/24 Interface description:

Issue 01 (2011-09-20) Huawei Proprietary and Confidential 5

NE Role Service Interface Logical Interface Interface

E1 0/2/0 Serial0/2/0:0 Interface description:

E1 0/2/1 Serial0/2/1:0 Interface description: