IP eRAN Engineering Guide (eRAN18.1 - 02)

eRAN
IP eRAN Engineering Guide Feature

Parameter Description
Issue 02
Date 2022-04-27
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://www.huawei.com
Email: support@huawei.com
Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. i

eRAN
IP eRAN Engineering Guide Feature Parameter
Description Contents
Contents
1 Change History.........................................................................................................................1
1.1 eRAN18.1 02 (2022-04-27)..................................................................................................................................................1
1.2 eRAN18.1 01 (2022-03-08)..................................................................................................................................................1
1.3 eRAN18.1 Draft A (2021-12-30)........................................................................................................................................ 1
2 About This Document.............................................................................................................4

2.1 General Statements................................................................................................................................................................ 4
2.2 Applicable RAT......................................................................................................................................................................... 4
2.3 Features in This Document.................................................................................................................................................. 4
2.4 Feature Differences Between NB-IoT and FDD............................................................................................................ 6
2.5 Differences Between Base Station Types........................................................................................................................ 6
3 Interface Engineering Guidelines........................................................................................ 8

3.1 Deployment of Common Transmission Data.................................................................................................................8
3.1.1 Principles................................................................................................................................................................................. 8
3.1.2 Network Analysis................................................................................................................................................................. 9
3.1.2.1 Benefits................................................................................................................................................................................ 9
3.1.2.2 Impacts................................................................................................................................................................................. 9
3.1.3 Requirements...................................................................................................................................................................... 10
3.1.3.1 Licenses.............................................................................................................................................................................. 10
3.1.3.2 Software............................................................................................................................................................................ 10
3.1.3.3 Hardware.......................................................................................................................................................................... 11
3.1.3.4 Networking...................................................................................................................................................................... 11
3.1.3.5 Others................................................................................................................................................................................ 14
3.1.4 Operation and Maintenance (IPv4 Transmission)..................................................................................................14
3.1.4.1 Data Configuration........................................................................................................................................................ 14
3.1.4.1.1 Data Preparation (Old Model)...............................................................................................................................15
3.1.4.1.2 Data Preparation (New Model)............................................................................................................................. 23
3.1.4.1.3 Using MML Commands (Old Model).................................................................................................................. 34
3.1.4.1.4 Using MML Commands (New Model)................................................................................................................ 36
3.1.4.1.5 Using the MAE-Deployment................................................................................................................................... 37
3.1.4.2 Activation Verification.................................................................................................................................................. 38
3.1.4.3 Network Monitoring..................................................................................................................................................... 38
Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. ii

eRAN

3.1.6 Operation and Maintenance (IPv4/IPv6 Dual-Stack Transmission).................................................................48
3.1.6.1.1 Data Preparation.........................................................................................................................................................48
3.1.6.1.2 Using MML Commands............................................................................................................................................ 48
3.2 Deployment of an S1 Interface........................................................................................................................................ 48
3.2.1 Principles.............................................................................................................................................................................. 49
3.2.2 Network Analysis............................................................................................................................................................... 49
3.2.2.1 Benefits.............................................................................................................................................................................. 49
3.2.2.2 Impacts.............................................................................................................................................................................. 49
3.2.3 Requirements...................................................................................................................................................................... 51
3.2.3.1 Licenses.............................................................................................................................................................................. 51
3.2.3.2 Software............................................................................................................................................................................ 52
3.2.3.3 Hardware.......................................................................................................................................................................... 52
3.2.3.4 Networking...................................................................................................................................................................... 52
3.2.3.5 Others................................................................................................................................................................................ 55
3.2.4 Operation and Maintenance......................................................................................................................................... 55
3.2.4.1.1 Data Preparation (Old Model)............................................................................................................................... 55
3.3 Deployment of an X2 Interface........................................................................................................................................ 70
3.3.1 Principles.............................................................................................................................................................................. 70
3.3.2.1 Benefits.............................................................................................................................................................................. 71
3.3.2.2 Impacts.............................................................................................................................................................................. 71
3.3.3 Requirements...................................................................................................................................................................... 71
3.3.3.1 Licenses.............................................................................................................................................................................. 71
3.3.3.2 Software............................................................................................................................................................................ 72
3.3.3.3 Hardware.......................................................................................................................................................................... 72
Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. iii

eRAN
3.3.3.4 Networking...................................................................................................................................................................... 72
3.3.3.5 Others................................................................................................................................................................................ 73
3.4 Deployment of an eX2 Interface..................................................................................................................................... 76
3.5 Deployment of O&M Channels........................................................................................................................................ 76
3.5.1 Principles.............................................................................................................................................................................. 76
3.5.2.1 Benefits.............................................................................................................................................................................. 77
3.5.2.2 Impacts.............................................................................................................................................................................. 77
3.5.3 Requirements...................................................................................................................................................................... 78
3.5.3.1 Licenses.............................................................................................................................................................................. 78
3.5.3.2 Software............................................................................................................................................................................ 78
3.5.3.3 Hardware.......................................................................................................................................................................... 78
3.5.3.4 Networking...................................................................................................................................................................... 78
3.5.3.5 Others................................................................................................................................................................................ 79
3.6 IP Transmission over eCoordinator Interfaces.............................................................................................................84
3.6.1 Principles.............................................................................................................................................................................. 84
3.6.2.1 Benefits.............................................................................................................................................................................. 85
3.6.2.2 Impacts.............................................................................................................................................................................. 85
Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. iv

eRAN
3.6.3 Requirements...................................................................................................................................................................... 85
3.6.3.1 Licenses.............................................................................................................................................................................. 85
3.6.3.2 Software............................................................................................................................................................................ 86
3.6.3.3 Hardware.......................................................................................................................................................................... 86
3.6.3.4 Networking...................................................................................................................................................................... 86
3.6.3.5 Others................................................................................................................................................................................ 86
4 Engineering Guidelines for Transmission Reliability.................................................... 89

4.1 Ethernet Route Backup for the Base Station...............................................................................................................89
4.1.1 Principles.............................................................................................................................................................................. 89
4.1.2.1 Benefits.............................................................................................................................................................................. 89
4.1.2.2 Impacts.............................................................................................................................................................................. 89
4.1.3 Requirements...................................................................................................................................................................... 90
4.1.3.1 Licenses.............................................................................................................................................................................. 90
4.1.3.2 Software............................................................................................................................................................................ 90
4.1.3.3 Hardware.......................................................................................................................................................................... 90
4.1.3.4 Networking...................................................................................................................................................................... 90
4.1.3.5 Others................................................................................................................................................................................ 91
4.1.4.1 Data Configuration (IPv4).......................................................................................................................................... 91
4.1.4.2 Data Configuration (IPv6).......................................................................................................................................... 94
4.1.4.3 Activation Verification (IPv4)..................................................................................................................................... 96
4.1.4.4 Activation Verification (IPv6)..................................................................................................................................... 97
4.1.4.5 Network Monitoring (IPv4)........................................................................................................................................ 98
4.1.4.6 Network Monitoring (IPv6)........................................................................................................................................ 98
4.2 Link Aggregation (Layer 2 or Layer 3 Networking Between the Base Station and Transmission
Equipment)..................................................................................................................................................................................... 98
4.2.1 Principles.............................................................................................................................................................................. 98
Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. v

eRAN

4.2.2.1 Benefits.............................................................................................................................................................................. 98
4.2.2.2 Impacts.............................................................................................................................................................................. 98
4.2.3 Requirements...................................................................................................................................................................... 99
4.2.3.1 Licenses.............................................................................................................................................................................. 99
4.2.3.2 Software............................................................................................................................................................................ 99
4.2.3.3 Hardware.......................................................................................................................................................................... 99
4.2.3.4 Networking.................................................................................................................................................................... 100
4.2.3.5 Others.............................................................................................................................................................................. 100
4.2.4 Operation and Maintenance....................................................................................................................................... 100
4.2.4.1 Data Configuration..................................................................................................................................................... 100
4.2.4.1.1 Data Preparation (Old Model)............................................................................................................................ 100
4.2.4.1.2 Data Preparation (New Model).......................................................................................................................... 100
4.2.4.1.3 Using MML Commands (Old Model)................................................................................................................101
4.2.4.1.4 Using MML Commands (New Model)..............................................................................................................101
4.2.4.1.5 Using the MAE-Deployment.................................................................................................................................101
4.2.4.2 Activation Verification (Old Model)...................................................................................................................... 102
4.2.4.3 Activation Verification (New Model).................................................................................................................... 102
4.2.4.4 Network Monitoring................................................................................................................................................... 102
4.3 O&M Channel Backup...................................................................................................................................................... 103
4.3.1 Principles............................................................................................................................................................................ 103
4.3.2 Network Analysis............................................................................................................................................................ 103
4.3.2.1 Benefits............................................................................................................................................................................103
4.3.2.2 Impacts............................................................................................................................................................................ 103
4.3.3 Requirements.................................................................................................................................................................... 103
4.3.3.1 Licenses........................................................................................................................................................................... 103
4.3.3.2 Software.......................................................................................................................................................................... 104
4.3.3.3 Hardware........................................................................................................................................................................ 104
4.3.3.4 Networking.................................................................................................................................................................... 104
4.3.3.5 Others.............................................................................................................................................................................. 105
4.3.4.1 Data Configuration (IPv4)........................................................................................................................................ 105
4.3.4.1.1 Data Preparation...................................................................................................................................................... 105
4.3.4.2 Data Configuration (IPv6)........................................................................................................................................ 110
4.3.4.2.1 Data Preparation...................................................................................................................................................... 110
4.3.4.2.2 Using MML Commands......................................................................................................................................... 114
4.3.4.3 Activation Verification................................................................................................................................................116
Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. vi

eRAN
5 Engineering Guidelines for Transmission Maintenance and Detection................. 119

5.1 BFD.......................................................................................................................................................................................... 119
5.1.1 Principles............................................................................................................................................................................ 119
5.1.2.1 Benefits............................................................................................................................................................................120
5.1.2.2 Impacts............................................................................................................................................................................ 120
5.1.3 Requirements.................................................................................................................................................................... 120
5.1.3.1 Licenses........................................................................................................................................................................... 120
5.1.3.2 Software.......................................................................................................................................................................... 120
5.1.3.3 Hardware........................................................................................................................................................................ 120
5.1.3.4 Networking.................................................................................................................................................................... 121
5.1.3.5 Others.............................................................................................................................................................................. 121
5.1.4.1.3 MML Command Examples (Old Model).......................................................................................................... 129
5.1.4.1.4 MML Command Examples (New Model)........................................................................................................ 129
5.2 GTP-U Echo........................................................................................................................................................................... 131
5.2.1 Principles............................................................................................................................................................................ 131
5.2.2.1 Benefits............................................................................................................................................................................131
5.2.2.2 Impacts............................................................................................................................................................................ 131
5.2.3 Requirements.................................................................................................................................................................... 131
5.2.3.1 Licenses........................................................................................................................................................................... 131
5.2.3.2 Software.......................................................................................................................................................................... 131
5.2.3.3 Hardware........................................................................................................................................................................ 132
5.2.3.4 Networking.................................................................................................................................................................... 132
5.2.3.5 Others.............................................................................................................................................................................. 132
5.3 LLDP........................................................................................................................................................................................ 135
Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. vii

eRAN
5.3.1 Principles............................................................................................................................................................................ 135

5.3.2.1 Benefits............................................................................................................................................................................136
5.3.2.2 Impacts............................................................................................................................................................................ 136
5.3.3 Requirements.................................................................................................................................................................... 136
5.3.3.1 Licenses........................................................................................................................................................................... 136
5.3.3.2 Software.......................................................................................................................................................................... 136
5.3.3.3 Hardware........................................................................................................................................................................ 136
5.3.3.4 Networking.................................................................................................................................................................... 137
5.3.3.5 Others.............................................................................................................................................................................. 137
6 Engineering Guidelines for Quick Transmission Congestion Detection.................141

6.1 Principles............................................................................................................................................................................... 141
6.2 Network Analysis................................................................................................................................................................ 141
6.2.1 Benefits............................................................................................................................................................................... 141
6.2.2 Impacts............................................................................................................................................................................... 141
6.3 Requirements....................................................................................................................................................................... 141
6.3.1 Licenses............................................................................................................................................................................... 141
6.3.2 Software............................................................................................................................................................................. 142
6.3.3 Hardware........................................................................................................................................................................... 142
6.3.4 Networking....................................................................................................................................................................... 142
6.3.5 Others................................................................................................................................................................................. 143
6.4 Operation and Maintenance.......................................................................................................................................... 143
6.4.1 Data Configuration......................................................................................................................................................... 143
6.4.1.1 Data Preparation..........................................................................................................................................................143
6.4.1.2 Using MML Commands............................................................................................................................................. 143
6.4.1.3 Using the MAE-Deployment.................................................................................................................................... 143
6.4.2 Activation Verification................................................................................................................................................... 143
6.4.3 Network Monitoring...................................................................................................................................................... 145
7 Parameters............................................................................................................................146
8 Counters................................................................................................................................ 147
9 Glossary................................................................................................................................. 148
Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. viii

eRAN
10 Reference Documents...................................................................................................... 149
Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. ix

eRAN
Description 1 Change History
1 Change History
This chapter describes changes not included in the "Parameters", "Counters",

"Glossary", and "Reference Documents" chapters. These changes include:
● Technical changes
Changes in functions and their corresponding parameters
● Editorial changes
Improvements or revisions to the documentation
1.1 eRAN18.1 02 (2022-04-27)

This issue includes the following changes.
Technical Changes
None
Editorial Changes
Revised descriptions in this document.
1.2 eRAN18.1 01 (2022-03-08)

This issue includes the following changes.
Technical Changes
None
Editorial Changes
1.3 eRAN18.1 Draft A (2021-12-30)

This issue introduces the following changes to eRAN17.1 02 (2021-04-30).
Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. 1

eRAN
Technical Changes
Change Description Parameter Change RAT Base Station
Model
Added support for the Added the FDD ● 3900 and

TEID-based load TRANSFUNCTIONS 5900 series
sharing trunk function W.ETHTRKLBMODE base stations
by the main control parameter. ● DBS3900
board. For details, see: LampSite
● Network Impacts and DBS5900
in 4.2.2.2 Impacts LampSite
● 4.2.4.1.1 Data
Preparation (Old
Model)
● 4.2.4.1.2 Data
Preparation (New
Model)
● Activation
Command
Examples in
4.2.4.1.3 Using
MML Commands
(Old Model)
● Activation
Command
Examples in
4.2.4.1.4 Using
MML Commands
(New Model)
Added support for OM Added parameters: FDD ● 3900 and

channel switchback in ● GTRANSPARA.OM 5900 series
IPv6. For details, see: CHSWITCHBACK base stations
● 4.3.4.2.1 Data ● GTRANSPARA.OM ● DBS3900
Preparation CHSBWAITTIME LampSite
● 4.3.4.2.2 Using and DBS5900
● OMCH.CHECKTYP LampSite
MML Commands E
● 4.3.4.3 Activation
Verification
Deleted the UCCU None FDD ● 3900 and

board. 5900 series
base stations
● DBS3900
LampSite
and DBS5900
LampSite

eRAN
Editorial Changes

eRAN
Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
This document is intended to acquaint readers with:
● The technical principles of features and their related parameters

● The scenarios where these features are used, the benefits they provide, and
the impact they have on networks and functions
● Requirements of the operating environment that must be met before feature
activation
● Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance
NOTE
This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve optimal gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this
document apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.
2.2 Applicable RAT

This document applies to FDD/NB-IoT.
2.3 Features in This Document

This document describes the following FDD features.

eRAN
Feature ID Feature Name Chapter/Section
LBFD-003001 Transmission Networking 3.2.3 Requirements
LBFD-00300101 Star Topology 3.2.3 Requirements
LBFD-00300102 Chain Topology 3.2.3 Requirements
LBFD-00300103 Tree Topology 3.2.3 Requirements
LBFD-003006 IPv4/IPv6 Dual Stack 3.1.3 Requirements
LBFD-003007 IP Route Backup 4.1 Ethernet Route

Backup for the Base
Station
LOFD-003005 OM Channel Backup 4.3 O&M Channel

Backup
LOFD-003007 Bidirectional Forwarding 5.1 BFD

Detection
LOFD-003008 Ethernet Link 4.2 Link Aggregation

Aggregation (IEEE (Layer 2 or Layer 3
802.3ad) Networking Between
the Base Station and
Transmission
Equipment)
LOFD-003017 S1 and X2 over IPv6 3.2 Deployment of an

S1 Interface
3.3 Deployment of an
X2 Interface
This document describes the following NB-IoT features.
MLBFD-12000307 IPv4/IPv6 Dual Stack 3.1.3 Requirements
MLBFD-12000308 IP Route Backup 3.2.3 Requirements
MLOFD-003005 OM Channel Backup 4.3 O&M Channel

Backup
MLOFD-003007 Bidirectional Forwarding 5.1 BFD

Detection
MLOFD-003008 Ethernet Link 4.2 Link Aggregation

Aggregation (IEEE (Layer 2 or Layer 3
802.3ad) Networking Between
the Base Station and
Transmission
Equipment)

eRAN
MLOFD-003017 S1 over IPv6 3.2 Deployment of an

S1 Interface
3.3 Deployment of an
X2 Interface
2.4 Feature Differences Between NB-IoT and FDD

NB-IoT Feature FDD Feature Difference Chapter/Section
MLBFD-12000307 LBFD-003006 None 3.1.3

IPv4/IPv6 Dual IPv4/IPv6 Dual Requirements
Stack Stack
MLBFD-12000308 LBFD-003007 IP None 4.1 Ethernet

IP Route Backup Route Backup Route Backup for
the Base Station
MLOFD-003005 LOFD-003005 OM None 4.3 O&M

OM Channel Channel Backup Channel Backup
Backup
MLOFD-003007 LOFD-003007 None 5.1 BFD

Bidirectional Bidirectional
Forwarding Forwarding
Detection Detection
MLOFD-003008 LOFD-003008 None 4.2 Link

Ethernet Link Ethernet Link Aggregation
Aggregation (IEEE Aggregation (IEEE (Layer 2 or Layer
802.3ad) 802.3ad) 3 Networking
Between the
Base Station and
Transmission
Equipment)
MLOFD-003017 LOFD-003017 S1 NB-IoT supports 3.2 Deployment

S1 over IPv6 and X2 over IPv6 only S1 and X2-C of an S1
(control plane) Interface
interfaces, and 3.3 Deployment
does not support of an X2
X2-U (user plane). Interface
2.5 Differences Between Base Station Types

For details about IPv4 transmission, see IPv4 Transmission. For details about IPv6
transmission, see IPv6 Transmission.

eRAN
IPv4 Transmission Implementation in Macro, Micro, and LampSite Base

Stations
Base Difference
Station
Model
Macro Supported
Micro The eX2 interface does not support this function.

Link aggregation does not support this function.
E1/T1 scenarios do not support this function.
LampSite Supported
IPv6 Transmission Implementation in Macro, Micro, and LampSite Base

Stations
Base Difference
Station
Model
Macro Supported
Micro Not supported
LampSite Supported

eRAN
Description 3 Interface Engineering Guidelines
3 Interface Engineering Guidelines
3.1 Deployment of Common Transmission Data
3.1.1 Principles
IPv4 Transmission
Deploying common transmission data is to set up the transmission path of the
bottom layers. Common transmission data includes data at the physical layer, data
link layer, and network layer.
● Physical layer data
Information about the cabinet, subrack, and slot housing transmission ports,
optical/electrical port attribute, transmission rate, and duplex mode, which are
determined based on the operator's network plan
● Data link layer data
– Information about the MAC layer of the Ethernet, which includes flow
control frames and ARP proxies of ports
– VLAN ID and VLAN priority of each service flow of an eNodeB, which are
determined based on the operator's network plan
● Network layer data
– IP address information about the local eNodeB, including interface IP
addresses and logical IP addresses
– IP addresses for the O&M channel, IPsec tunnel, S1-C, S1-U, X2-C, X2-U,
eX2-C (LTE FDD), eX2-U (LTE FDD), and IP clock links, which are
configured based on the operator's network plan
– Information about routes from the local eNodeB to the destination IP
addresses of the peer NEs (such as the MME, S-GW, neighboring eNodeB,
MAE-Access, and IP clock), which is required when there are routers
between the eNodeB and peer NEs

eRAN
IPv6 Transmission
The differences between IPv6 transmission and IPv4 transmission lie in the data at
the data link layer and network layer.
● Data link layer data

– In IPv6 networking, the information about the MAC layer of the Ethernet
contains the flow control frames over the ports. The ARP protocol is not
used. The ARP function is replaced by the neighbor discovery function.
– You are advised to plan an independent VLAN ID for the O&M channel
and isolate it from VLANs of other services.
● Network layer data
– Similar to IPv4 transmission, IPv6 transmission requires the local IPv6
addresses of IPv6 services on the eNodeB, including the interface IP
addresses and logical IP addresses, and also requires the IPv6 addresses
and IPv6 routes of the peer devices used for IPv6 transmission.
– In IPv6 transmission, the MTU of the backhaul network must be
collected. It is recommended that the interface MTU of the base station
be set to the minimum MTU on all backhaul networks of the interface.
Ensure that all the routers support the sending of ICMPv6 Packet Too Big
messages and the network firewall allows the packets to pass through.
IPv4/IPv6 Dual-Stack Transmission

Information about IPv4 and IPv6 transmission is required for this type of
transmission.
VLAN configurations for IPv4 and IPv6 transmission are correlated and must be set
as follows:
● IPv6 and dual-stack transmission support only the new model. In dual-stack
transmission, the VLANs for both IPv4 and IPv6 transmission must be
configured in the interface VLAN configuration mode. IPv4 transmission
cannot use the single VLAN or VLAN group configuration mode.
3.1.2 Network Analysis
3.1.2.1 Benefits
None
3.1.2.2 Impacts
Network Impacts
None

eRAN
Function Impacts
Function Name Function Reference Description
Switch
IP-based multi-mode None Common Source-based IPv6

co-transmission on Transmission routing does not
BS side support backplane
tunnels in main-
control-board-based co-
transmission through
backplane
interconnection on the
separate-MPT MBTS
side.
3.1.3 Requirements
3.1.3.1 Licenses
None
3.1.3.2 Software
Prerequisite Functions
None
Mutually Exclusive Functions

Function Function Switch Reference Description
Name
Direct IPv6 USERPLANEHOST.IP S1 and X2 Self- Direct IPv6 IPsec does

IPsec SECSWITCH and Management not support source-
SCTPHOST.SIGIP1SE based IPv6 routing.
CSWITCH
O&M None IPv6 The O&M channel in
channel in Transmission route-binding mode
route- does not support
binding source-based routing.
mode

eRAN
3.1.3.3 Hardware
Base Station Models

The following base station models support IPv4 transmission:
● 3900 and 5900 series base stations
● DBS3900 LampSite and DBS5900 LampSite
● BTS3912E
● BTS3911E
Boards
The following boards of the eNodeB support IPv4 transmission:
● UMPT
● UMDU
The following boards of the eNodeB support IPv6 transmission:
● UMPT
● UMDU
Source-based routing on the base station has the following requirements for
boards:
● The following boards of the 3900 and 5900 series base stations support
source-based routing: UMPT/UMDU/UTRPa/UTRPc/USU.
● A base station supports source-based routing only when all of the configured
boards support source-based routing.
RF Modules
None
3.1.3.4 Networking
IPv4 Transmission
The eNodeB side has different service interfaces, including the S1-C, S1-U, X2-C,
X2-U, eX2-C (LTE FDD), eX2-U (LTE FDD), IP clock links, and the O&M channel.
These service interfaces can have identical or different IP addresses. eNodeB IP
addresses need to be planned based on the use of IP addresses for service
interfaces.
The eNodeB uses route forwarding in panel cascading scenarios. An interface IP
address must be configured for the cascading interface, which serves as the next-
hop IP address of the next-hop leaf node.

eRAN
Transmission reliability needs to be considered during network planning. Planning

multiple physical links or more IP addresses and routes for the eNodeB can
improve transmission reliability. Before using a specific transmission maintenance
and detection feature, ensure that devices on the transport network support this
feature.
In addition to routes of the MME, S-GW, MAE-Access, and neighboring eNodeB,

consider the following during IP route planning:
● If an IP clock server is used, a corresponding route must be planned.

● If the SeGW, PKI, FTP server, or NTP server is used, a corresponding route
must be planned. If multiple devices are in the same network segment, the
route can be a network segment route. This means that an independent route
is not required for each device.
● If an IPsec tunnel is enabled, the interface IP address functions as the external
IP address of the IPsec tunnel and the loopback IP address functions as the
internal IP address of the IPsec tunnel.
● Source-based IPv6 routing must be deployed on the same board.
● If the X2 interface uses layer 2 networking and does not support source-based
routing on the base station but the S1 interface uses layer 3 networking and
requires source-based routing on the base station, two IP addresses must be
configured for the X2 and S1 interfaces, respectively, on the base station.
● Whether to use source-based or destination-based IP routing must be
planned.
– For details about the application scenarios of source-based IP routing, see
IPv4 Transmission. Destination-based IP routing is used by default.
– A maximum of 32 source IP routes can be configured.
If an eNodeB requires more than 32 IP routes, you are advised to
configure only destination-based IP routes for the eNodeB.
– Destination-based IP routing and source-based IP routing are mutually
exclusive.
The user plane and control plane of the base station must adopt the
same routing policy.
The active and standby routes must adopt the same routing policy. The
priority of destination-based IP routing is lower than that of source-based
IP routing.
IPv6 Transmission
● The IP addresses and routes in IPv4 Transmission are changed to IPv6
addresses and IPv6 routes, respectively. IPv6 routes support source-based and
destination-based IP routing.
● Whether to use source-based or destination-based IP routing on the base
station side must be planned.
– For details about the application scenarios of source-based IP routing, see
IPv6 Transmission. Destination-based IP routing is used by default.
– A maximum of 32 source IP routes can be configured.
If an eNodeB requires more than 32 IP routes, you are advised to
configure only destination-based IP routes for the eNodeB.

eRAN
– Destination-based IP routing and source-based IP routing are mutually

exclusive.
The routing policies must be consistent between the user plane and
control plane
The active and standby routes must adopt the same routing policy.
● In IPv6 transmission, the main control board of the local BBU can provide a
port for connecting to the IPv6 transport network, and co-transmission
through panel interconnection and cascading networking are supported.
However, IPv6 co-transmission through backplane interconnection is not
supported.
● IPv6 transmission and dual-stack transmission support only the new
transmission model.
● IPv6 transmission has been deployed on the transport network, and IPv6
transmission routes have been configured between the base station and the
peer device.
● In layer 2 or layer 2+layer 3 networking, the layer 2 switch must support the
transmission of all multicast packets or support MLD snooping, support
addition of IPv6 solicited-node multicast addresses, perform IPv6 address
conflict detection, and transmit IPv6 address resolution multicast packets.
● The IPv6 extension header is optional and used for specific functions. The
eNodeB can only receive or send the following IPv6 extension headers. The
IPv6 packets sent by the peer device (router, core network, base station, or
clock server) must not carry extension headers except for the following ones.
Otherwise, the packets will be discarded by the base station.
– Fragment header: This header is used for packet fragmentation.
– AH and ESP: supporting encryption
– HOP by HOP: This header can be carried only in packets compliant with
the MLD snooping discovery protocol.
● The MTUs of IPv6 transmission links must be centrally planned.
– During IPv6 transmission, the router discards the packets whose MTU size
is larger than its MTU. E2E MTU planning is required.
– For the transmission link of the O&M channel, the MTU of the bearer
network device must be greater than or equal to 1500 bytes. The default
MTU on the MAE-Access side is 1500 bytes. It is recommended that an
independent VLAN interface be planned for the O&M channel on the
base station side and the MTU be set to 1500 bytes. This ensures that
packets less than or equal to 1500 bytes can be transmitted in the E2E
O&M link.
– For the transmission links of other service interfaces, a unified MTU value
is planned based on the capability of the devices on the E2E transmission
link, including the base station, router, and peer device. The MTU value
can equal the minimum among the maximum MTU values of these
devices to improve the transmission efficiency of service packets.
– In secure networking, the MTUs of the SeGW and the routers between
the SeGW and base station are the above MTU value plus the length of
the IPsec encryption header.
● An X2 interface cannot be set up between an IPv4 single-stack transmission
base station and an IPv6 transmission base station. X2 dual-stack must be

eRAN
configured for base stations in the border area. The bearer network must
support dual-stack transmission, as shown in Figure 1 X2 dual-stack.
Figure 3-1 X2 dual-stack
IPv4/IPv6 Dual-Stack Transmission

● IPv4 and IPv6 transmission use independent IP addresses and routes at the IP
layer. To implement IPv4/IPv6 dual-stack transmission, the IP layer must
include IPv4 addresses and IPv6 routes. For detailed configuration
requirements, see IPv6 Transmission.
● IPv4/IPv6 dual-stack transmission has been deployed on the transport bearer
network, and IPv4/IPv6 transmission routes have been configured for the
transmission link between the base station and the peer device.
● For details about the requirements for IPv6 transmission, see IPv6
Transmission. For details about the requirements for IPv4 transmission, see
IPv4 Transmission.
3.1.3.5 Others
If dual-stack networking is required for core network devices, all base stations
connected to the core network must be upgraded to SRAN15.1, and then dual-
stack data can be configured on the core network. Base stations earlier than
SRAN15.1 do not support the processing of signaling that carries dual-stack IP
addresses.
3.1.4 Operation and Maintenance (IPv4 Transmission)
3.1.4.1 Data Configuration

eRAN
3.1.4.1.1 Data Preparation (Old Model)

If the GTRANSPARA.TRANSCFGMODE parameter is set to OLD, the old model is
used for data preparation.
NOTE
The new and old models in this document are selected based on the value of the
GTRANSPARA.TRANSCFGMODE parameter. If the GTRANSPARA.TRANSCFGMODE
parameter is set to OLD, the old model is used. If the GTRANSPARA.TRANSCFGMODE
parameter is set to NEW, the new model is used.
Ethernet Port
The following table describes the parameters that must be set in an ETHPORT
MO to configure an Ethernet port.
Paramete Parameter ID Setting Notes

r Name
Subboard ETHPORT.SB This parameter specifies the type of the sub-board

Type T providing an Ethernet port.
Port ETHPORT.PA This parameter specifies whether an Ethernet port

Attribute is an electrical port or optical port. The port
attributea must be the same as that of the peer
port.
For a macro base station, when a UMPT or UMDU
board is configured, automatic port attribute
detection is not supported. Set this parameter
based on the port attribute (optical or electrical).
For micro base stations, automatic port attribute
detection is supported. Set this parameter based on
the port attribute.
Maximum ETHPORT.MT This parameter specifies the maximum size of an IP

Transmiss U packet (including the IP header) transmitted over
ion Unit the port. Set this parameter based on the network
plan.
Speed ETHPORT.SPE This parameter specifies the speed mode of an

ED Ethernet port. The speed mode of an Ethernet port
must be consistent with that of its interconnected
port. Set this parameter based on the network
plan.

eRAN

r Name
Duplex ETHPORT.DU This parameter specifies the duplex mode of an

PLEX Ethernet port.
● For a 10 Mbit/s or 100 Mbit/s electrical port, set
the Speed parameter to 10M or 100M and this
parameter to FULL.
● For a 1000 Mbit/s electrical port, set both the
Speed parameter and this parameter to AUTO.
● For a 100 Mbit/s optical port, set the Speed
parameter to 100M and this parameter to FULL.
parameter to 1000M and this parameter to
FULL, or set both the Speed parameter and this
parameter to AUTO.
● For a 10 Gbit/s optical port, set the Speed
parameter to 10G and this parameter to FULL.
● When the Port Attribute parameter is set to
AUTO for the Ethernet port, set both the Speed
parameter and this parameter to AUTO.
a: If this parameter is set to AUTO, port activation may take about one minute.
If the port attribute is reconfigured as optical on the peer device, the
reconfiguration takes effect only after this optical port on the peer device is
reset or the Ethernet port on the local eNodeB is reset by running the RST
ETHPORT command.
VLAN Mapping
The following table describes the parameters that must be set in a VLANMAP MO
to configure VLAN mapping.

r Name
VRF Index VLANMAP.VR Set this parameter to the default value 0. Micro
FIDX base stations do not support the VRF function.
Next Hop VLANMAP.NE This parameter specifies the next-hop IP address

IP XTHOPIP for VLAN mapping. This IP address must be in the
same network segment as the interface IP address
and the IP address of the gateway on the transport
network connecting to the eNodeB.

eRAN

r Name
Mask VLANMAP.M This parameter specifies the subnet mask of the

ASK next-hop IP address for VLAN mapping. The
interface IP address of the eNodeB must be in the
network segment determined by the next-hop IP
address and subnet mask.
A 31-bit mask can be configured for the IP address
of an Ethernet interface. During transport network
planning, only the directly connected 31-bit
network segment can be set to all 0s or all 1s.
VLAN VLANMAP.VL This parameter specifies the VLAN mode. Set this
Mode ANMODE parameter based on operators' requirements and
peer device configurations:
● If the operator plans one-to-one mapping
relationships between eNodeBs and VLANs, set
this parameter to SINGLEVLAN.
● If the operator plans one-to-multiple mapping
relationships between eNodeBs and VLANs
based on traffic types, set this parameter to
VLANGROUP.
VLAN VLANMAP.VL This parameter specifies the VLAN group number.

Group ANGROUPN ● This parameter is valid only when the
No. O VLANMAP.VLANMODE parameter is set to
VLANGROUP. It is recommended that VLAN
groups be numbered from 0. Generally, each
eNodeB has only one VLAN group number.
● Set this parameter if the value of the
VLANMAP.VLANMODE parameter is changed
from SINGLEVLAN to VLANGROUP during
modification of this MO.
● Ensure that the value of this parameter is the
same as the VLAN group number in the
VLANCLASS MO.
VLAN ID VLANMAP.VL This parameter specifies the VLAN ID in the VLAN

ANID tag.
● Set this parameter based on the network plan.
This parameter is valid only when the
VLANMAP.VLANMODE parameter is set to
SINGLEVLAN.
● VLAN tags contain VLAN IDs.

eRAN

r Name
Set VLAN VLANMAP.SE This parameter specifies whether to set the priority
Priority TPRIO of a single VLAN.
● Set this parameter only when the
SINGLEVLAN and a VLAN has only one priority.
● To use default mapping relationships between
user data types and VLAN priorities, set this
parameter to DISABLE.
● To use specific mapping relationships between
parameter to ENABLE.
● You are advised to set VLANMAP.SETPRIO to
DISABLE to use the default mapping
relationships. In addition, configure the
DSCPMAP MO to specify the mapping
relationships between differentiated services
code point (DSCP) values and VLAN priorities in
single VLAN mode.
VLAN Priority Mapping

If a single VLAN is used, it is recommended that the DSCPMAP MO be set to
configure mapping relationships between service types and VLAN priorities.

r Name
VRF Index DSCPMAP.VR Set this parameter to the default value 0. Micro
Differenti DSCPMAP.DS This parameter specifies the DSCP value.

ated CP Set this parameter for each data type, such as
Service service flow, signaling flow, and data flow in the
Codepoint O&M channel, based on the network plan.
VLAN DSCPMAP.VL This parameter specifies the priority of a VLAN.

Priority ANPRIO Set this parameter to the VLAN priority that maps
to the DSCP value based on the network plan.
To configure a VLAN group mapping relationship, both the VLANMAP and

VLANCLASS MOs are required.
The following table describes the parameters that must be set in a VLANCLASS
MO to configure the VLAN priority mapping.
Micro base stations do not support VLAN configuration in VLAN group mode.

eRAN

r Name
VLAN VLANCLASS. This parameter specifies the number of the VLAN

Group VLANGROUP group that the added VLAN mapping relationship
No. NO belongs to. There are no setting notes for this
parameter.
Traffic VLANCLASS.T This parameter specifies a service type for data

Type RAFFIC transmission. Different types of service data have
different VLANs.
Set this parameter based on the network plan. The
following traffic types are available: USERDATA,
SIG, OM, OM_LOW, OM_HIGH, and OTHER. A
VLAN ID must be specified for each traffic type to
prevent abnormal services.
User Data VLANCLASS.S This parameter specifies the service priority of user
Service RVPRIO data.
Priority ● This parameter is valid only when the
VLANCLASS.TRAFFIC parameter is set to
USERDATA.
● It is recommended that the setting of this
parameter be consistent with configurations in
the DSCPMAP MO.
VLAN ID VLANCLASS. This parameter specifies the ID of the VLAN for

VLANID service data. Set this parameter based on the
network plan.
VLAN VLANCLASS. This parameter specifies the VLAN priority. A larger

Priority VLANPRIO value indicates a higher priority. Set this parameter
based on the network plan.
Device IP Address
The following table describes the parameters that must be set in a DEVIP MO to
configure a device IP address.

r Name
Subboard DEVIP.SBT This parameter specifies the type of the sub-board

Type providing the port. Set this parameter to
BASE_BOARD.
IP DEVIP.IP This parameter specifies an IP address configured

Address on a port. The control plane and the user plane of
the S1/X2/eX2 (FDD) interface use this IP address.
If NR and LTE share the main control board, plan
different local IP addresses for NR and LTE.

eRAN

r Name
Mask DEVIP.MASK This parameter specifies the subnet mask for the
device IP address. Set this parameter based on the
network plan.
Port Type DEVIP.PT This parameter specifies the type of a physical port.
● For macro base stations in an E1/T1 scenario,
configure a device IP address with this
parameter set to PPP or MPGRP.
● For micro base stations in a PPPoE scenario,
configure a device IP address with this
parameter set to PPPOE.
● In an Ethernet scenario, configure a device IP
address with this parameter set to ETH.
● In a secure networking scenario, a logical IP
address is required in addition to the interface IP
address. A device IP address with this parameter
set to LOOPINT is a logical IP address.
● When the eNodeB uses an interface IP address
to set up an IPsec tunnel with the SeGW, the
eNodeB uses the logical IP address to
communicate with the MAE-Access, S-GW,
MME, or neighboring eNodeBs.
● For FDD macro base stations, if a device IP
address needs to function as the UMPT CI port
address, set this parameter to ETHCI.
IP Route
The following table describes the parameters that must be set in an IPRT MO to
configure a destination-based IP route. In layer 2 networking, these parameters
are not required.

r Name
Route IPRT.RTIDX This parameter specifies the index of an IP route.

Index Set this parameter based on the network plan.

eRAN

r Name
Destinatio IPRT.DSTIP This parameter specifies the destination IP address

n IP of a route.
● The default route, with the destination IP
address and subnet mask being 0.0.0.0, is not
recommended.
● If peer NEs, such as the S-GW, MME, and
eNodeB, are in the same network segment, an
IP route to this network segment is
recommended. That is, set the destination IP
address to the IP address of this segment and
the subnet mask to that of this segment.
Mask IPRT.DSTMAS This parameter specifies the subnet mask for the
K destination IP address of a route.
recommended.
Subboard IPRT.SBT This parameter specifies the type of the sub-board

BASE_BOARD.
Route IPRT.RTTYPE This parameter specifies the route type.

Type ● Set this parameter to NEXTHOP in Ethernet
scenarios.
● For macro base stations, set this parameter to IF
in E1 networking scenarios.
● For micro base stations, set this parameter to IF
in PPPoE networking scenarios.
Port Type IPRT.IFT This parameter specifies the port type.

For macro base stations, set this parameter to PPP
or MPGRP in E1 networking scenarios.
For micro base stations, set this parameter to
PPPoE in PPPoE networking scenarios.

eRAN

r Name
Next Hop IPRT.NEXTH This parameter specifies the next-hop IP address.

IP OP ● This parameter is valid only when the
IPRT.RTTYPE parameter is set to NEXTHOP.
● Generally, set this parameter to the IP address
of the gateway on the transport network
connecting to the eNodeB based on the network
plan.
Preferenc IPRT.PREF This parameter specifies the priority of a routing

e entry.
This parameter is required for IP route backup. A
higher parameter value indicates a lower priority.
The route with a higher priority is activated.
The eNodeB does not support route load sharing.
Routes to the same destination network segment
must have different priorities.
The following table describes the parameters that must be set in an SRCIPRT MO
to configure a source-based IP route. In layer 2 networking, these parameters are
not required.

r Name
Source SRCIPRT.SRC This parameter specifies the index of an IP route.

Route RTIDX Set this parameter based on the network plan.
Index
Source IP SRCIPRT.SRCI This parameter specifies the local IP address of the

Address P eNodeB. This IP address is used as the device IP
address on the user plane, control plane, and O&M
plane.
Subboard SRCIPRT.SBT This parameter specifies the type of the sub-board

BASE_BOARD.
Route SRCIPRT.RTT This parameter specifies the route type.

Type YPE ● Set this parameter to NEXTHOP in Ethernet
networking scenarios.
● Set this parameter to IF in E1 networking
scenarios.
Interface SRCIPRT.IFT This parameter specifies the port type.

Type Set this parameter to PPP or MPGRP in E1

eRAN

r Name
Next Hop SRCIPRT.NEX This parameter specifies the next-hop IP address.

IP THOP ● This parameter is valid only when the
plan.
Priority SRCIPRT.PRE This parameter specifies the priority of a routing

F entry.
3.1.4.1.2 Data Preparation (New Model)

If the GTRANSPARA.TRANSCFGMODE parameter is set to NEW, the new model
is used for data preparation.
Ethernet Port

r Name
Port ID ETHPORT.PO This parameter uniquely identifies an Ethernet

RTID port. For an automatically created Ethernet port,
the port ID includes the cabinet No., subrack No.,
and slot No. from the most significant bit to the
least significant bit. In the old model, this
parameter is optional, and the default value is
4294967295. In the new model, this parameter is
mandatory, and the value must be unique.
In later versions, the value 4294967295 of this
parameter will be deleted. Therefore, you are
advised not to use this value.


eRAN

r Name

attribute must be the same as that of the peer
port.
For macro base stations, when a UMPT or UMDU
For micro base stations, automatic port attribute
detection is supported. Set this parameter based on
the port attribute.
NOTE
If this parameter is set to AUTO, port activation may take
about one minute. If the port attribute is reconfigured as
optical on the peer device, the reconfiguration takes
effect only after this optical port on the peer device is
reset or the Ethernet port on the local eNodeB is reset by
running the RST ETHPORT command.
Maximum ETHPORT.MT This parameter specifies the maximum size of an IP

Transmiss U packet (including the IP header) transmitted over
ion Unit the port. Set this parameter based on the network
plan.
Speed ETHPORT.SPE This parameter specifies the speed mode of an

ED Ethernet port, which must be consistent with that
of its interconnected port. Set this parameter based
on the network plan.

eRAN

r Name

PLEX Ethernet port.
parameter to FULL.
● For a 1000 Mbit/s electrical port, set both the
Speed parameter and this parameter to AUTO.
parameter to AUTO.

The following table describes the parameters that must be set in a
DSCP2PCPMAP MO to configure mapping relationships between traffic types and
VLAN priorities.

r Name
DSCP-to- DSCP2PCPM This parameter specifies the ID of the mapping

PCP AP.DSCP2PCP table between DSCPs and VLAN priorities.
Mapping MAPID
ID
Default DSCP2PCPM This parameter specifies the default VLAN priority

PCP AP.DEFAULTP used for non-mapped DSCPs.
CP
Differenti DSCP2PCPM This parameter specifies the DSCP. A larger value
ated AP.DSCP indicates a higher priority.
Service
Code
Point

eRAN

r Name
Priority DSCP2PCPM This parameter specifies the VLAN priority. A larger

Code AP.PCP value indicates a higher priority.
Point
Interface-based VLAN Setting

The following table describes the parameters that must be set in an INTERFACE
MO to configure VLAN interfaces and associated VLANs.

r Name
Interface INTERFACE.IT This parameter specifies the ID of an interface.

ID FID
Interface INTERFACE.IT This parameter specifies the type of an interface,
Type FTYPE which can be set to NORMAL or VLAN. For a
VLAN interface, set this parameter to VLAN.
Port Type INTERFACE.P This parameter specifies the type of the port to
T which an interface belongs.
Port ID INTERFACE.P This parameter specifies the ID of the port to which

ORTID an interface belongs.
VLAN ID INTERFACE.V This parameter specifies the VLAN ID of an

LANID interface.
DSCP-to- INTERFACE.D This parameter specifies the ID of a mapping

PCP SCP2PCPMAP between DSCP values and VLAN priorities for an
Mapping ID interface.
ID
VRF Index INTERFACE.V This parameter specifies the VRF index of an

RFIDX interface.
IPv4 INTERFACE.M This parameter specifies the maximum IPv4

Maximum TU4 transmission unit supported by an interface.
Transmiss
ion Unit
ARP Proxy INTERFACE.A This parameter specifies whether to enable the

RPPROXY ARP proxy function.
VLAN Mapping-based VLAN Setting

NOTE
Setting a VLAN based on the interface is mutually exclusive with setting a VLAN based on
the VLAN mapping. Only one method can be used at a time.

eRAN
The following table describes the parameters that must be set in a VLANMAP MO
to configure VLAN mapping.

r Name
VRF Index VLANMAP.VR Set this parameter to the default value 0. Micro
Next Hop VLANMAP.NE This parameter specifies the next-hop IP address

IP XTHOPIP for VLAN mapping. This IP address must be in the
same network segment as the interface IP address
and the IP address of the gateway on the transport
network connecting to the eNodeB.
Mask VLANMAP.M This parameter specifies the subnet mask of the

ASK next-hop IP address for VLAN mapping. The
interface IP address of the eNodeB must be in the
network segment determined by the next-hop IP
address and subnet mask.
VLAN VLANMAP.VL This parameter specifies the VLAN mode. Set this
Mode ANMODE parameter based on operators' requirements and
peer device configurations:
● If the operator plans one-to-one mapping
relationships between eNodeBs and VLANs, set
this parameter to SINGLEVLAN.
● If the operator plans one-to-multiple mapping
relationships between eNodeBs and VLANs
based on traffic types, set this parameter to
VLANGROUP.
VLAN VLANMAP.VL This parameter specifies the VLAN group number.

Group ANGROUPN ● This parameter is valid only when the
No. O VLANMAP.VLANMODE parameter is set to
VLANGROUP. It is recommended that VLAN
groups be numbered from 0. Generally, each
eNodeB has only one VLAN group number.
● This parameter must be configured if the value
of the VLANMAP.VLANMODE parameter is
changed from SINGLEVLAN to VLANGROUP
during the change of the mapping from a next-
hop IP address to a single VLAN or VLAN group.
● Ensure that the value of this parameter is the
same as the VLAN group number in the
VLANCLASS MO.

eRAN

r Name
VLAN ID VLANMAP.VL This parameter specifies the VLAN ID in the VLAN

ANID tag.
● Set this parameter based on the network plan.
This parameter is valid only when the
SINGLEVLAN.
● VLAN tags contain VLAN IDs.
Set VLAN VLANMAP.SE This parameter specifies whether to set the priority
Priority TPRIO of a single VLAN.
● Set this parameter only when the
SINGLEVLAN and a VLAN has only one priority.
● To use default mapping relationships between
parameter to DISABLE.
● To use specific mapping relationships between
parameter to ENABLE.
● You are advised to set VLANMAP.SETPRIO to
DISABLE to use the default mapping
relationships. In addition, configure the
DSCPMAP MO to specify the mapping
relationships between DSCP values and VLAN
priorities in single VLAN mode.
To configure a VLAN group mapping relationship, both the VLANMAP and

VLANCLASS MOs are required.
Micro base stations do not support VLAN configuration in VLAN group mode.

r Name
VLAN VLANCLASS. This parameter specifies the number of the VLAN

Group VLANGROUP group that the added VLAN mapping relationship
No. NO belongs to. There are no setting notes for this
parameter.

eRAN

r Name
Traffic VLANCLASS.T This parameter specifies a service type for data

Type RAFFIC transmission. Different types of service data have
different VLANs.
Set this parameter based on the network plan. The
following traffic types are available: USERDATA,
SIG, OM, OM_LOW, OM_HIGH, and OTHER. A
VLAN ID must be specified for each traffic type to
prevent abnormal services.
User Data VLANCLASS.S This parameter specifies the service priority of user
Service RVPRIO data.
Priority ● This parameter is valid only when the
VLANCLASS.TRAFFIC parameter is set to
USERDATA.
● It is recommended that the setting of this
parameter be consistent with configurations in
the DSCPMAP MO.
VLAN ID VLANCLASS. This parameter specifies the ID of the VLAN for

VLANID service data. Set this parameter based on the
network plan.
VLAN VLANCLASS. This parameter specifies the VLAN priority. A larger

Priority VLANPRIO value indicates a higher priority. Set this parameter
The following table describes the parameters that must be set in an INTERFACE
MO to configure common interfaces.

r Name

ID FID
Type FTYPE which can be set to NORMAL or VLAN.
For a normal interface, set this parameter to
NORMAL.


eRAN

r Name
VLAN INTERFACE.T This parameter specifies whether the interface

Tagged AGGED processes tagged packets.
Switch

ID

RFIDX interface.

Transmiss
ion Unit
ARP Proxy INTERFACE.A This parameter specifies whether to enable the

RPPROXY ARP proxy function.
Loopback Interface Configuration

The following table lists the parameters that must be set in the LOOPBACK MO to
configure loopback interfaces.

r Name
Port ID LOOPBACK.P This parameter specifies the ID of a loopback

ORTID interface and is unique in the system.
Cabinet LOOPBACK.C This parameter specifies the cabinet number of the

No. N board to which the loopback interface belongs.
Subrack LOOPBACK.S This parameter specifies the subrack number of the

No. RN board to which the loopback interface belongs.
Slot No. LOOPBACK.S This parameter specifies the slot number of the
N board to which the loopback interface belongs.
The following table lists the parameters that must be set in the INTERFACE MO to
configure interfaces for loopback interfaces.

r Name

ID FID

eRAN

r Name

For a loopback interface, set this parameter to
NORMAL.
LOOPINT.

For a loopback interface, set this parameter to the
same value as that of the LOOPBACK.PORTID
parameter.

RFIDX interface.
IP Address Configuration
Set an IP address for a VLAN or common interface.
The following table describes the parameters that must be set in an IPADDR4 MO
to set an IP address.

r Name
Interface IPADDR4.ITFI This parameter specifies the ID of an interface.

ID D ● If the PT parameter in the INTERFACE MO
corresponding to the interface ID is set to ETH,
ETHTRK, PPP, MPGRP, ETHCI, or PPPOE, the IP
address is configured as an interface IP address.
● If the PT parameter in the INTERFACE MO
corresponding to the interface ID is set to
LOOPINT, the IP address is configured as a
logical IP address.
IP IPADDR4.IP This parameter specifies an IP address configured

Address on a port. If NR and LTE share the main control
board, plan different local IP addresses for NR and
LTE.

eRAN

r Name
Mask IPADDR4.MA This parameter specifies the subnet mask for the
SK device IP address.
VRF Index IPADDR4.VRF This parameter specifies the ID of a virtual routing

IDX instance.
IP Route
The following table lists the parameters that must be set in the IPROUTE4 MO to
configure IP routes. In layer 2 networking, these parameters are not required.

r Name
Route IPROUTE4.RT This parameter specifies the index of an IPv4 route.

Index IDX Set this parameter based on the network plan.
VRF Index IPROUTE4.VR This parameter specifies the ID of a virtual routing

FIDX instance.
Destinatio IPROUTE4.DS This parameter specifies the destination IP address

n IP TIP of a route.
recommended.
Mask IPROUTE4.DS This parameter specifies the subnet mask for the
TMASK destination IP address of a route.
recommended.

eRAN

r Name
Route IPROUTE4.RT This parameter specifies the route type.

Type TYPE ● Set this parameter to NEXTHOP in Ethernet
● For macro base stations, set this parameter to IF
in E1 networking scenarios.
● For micro base stations, set this parameter to IF
in PPPoE networking scenarios.
Port Type IPROUTE4.PT This parameter specifies the port type.

For macro base stations, set this parameter to PPP
or MPGRP in E1 networking scenarios.
For micro base stations, set this parameter to
PPPoE in PPPoE networking scenarios.
Port ID IPROUTE4.PO This parameter specifies the port ID.

RTID
Next Hop IPROUTE4.NE This parameter specifies the next-hop IP address.
IP XTHOP ● This parameter is valid only when the
plan.
Preferenc IPROUTE4.PR This parameter specifies the priority of a routing

e EF entry.
The following table describes the parameters that must be set in an

SRCIPROUTE4 MO to configure IP routes. In layer 2 networking, these parameters
are not required.

r Name
Source SRCIPROUTE This parameter specifies the index of a source IPv4

Route 4.SRCRTIDX route. Set this parameter based on the network
Index plan.

eRAN

r Name
Source IP SRCIPROUTE This parameter specifies the source IPv4 address of

Address 4.SRCIP a source IPv4 route. This IP address is used as the
device IP address on the user plane, control plane,
and O&M plane.
Route SRCIPROUTE This parameter specifies the type of a source IPv4

Type 4.RTTYPE route.
● Set this parameter to NEXTHOP in Ethernet
● Set this parameter to IF in E1 networking
scenarios.
Port Type SRCIPROUTE This parameter specifies the port type of a source
4.PT IPv4 route.
Set this parameter to PPP or MPGRP in E1
Port ID SRCIPROUTE This parameter specifies the port ID of a source

4.PORTID IPv4 route.
Next Hop SRCIPROUTE This parameter specifies the next hop IP address of
IP 4.NEXTHOP a source IPv4 route.
● This parameter is valid only when the
plan.
Priority SRCIPROUTE This parameter specifies the priority of the source

4.PREF IPv4 routing entry. A smaller value indicates a
higher priority.
3.1.4.1.3 Using MML Commands (Old Model)

//Setting Ethernet port attributes for the eNodeB
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PA=FIBER, MTU=1500, SPEED=1000M,
DUPLEX=FULL, ARPPROXY=ENABLE, FC=OPEN, FERAT=10,
FERDT=10,RXBCPKTALMOCRTHD=322,RXBCPKTALMCLRTHD=290;
//Adding an eNodeB device IP address
ADD DEVIP: CN=0,SRN=0,SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="10.1.1.1", MASK="255.255.255.0",
VRFIDX=0;
//(Optional 1) Adding a destination IP route from the eNodeB to the peer device
ADD IPRT: RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="10.2.1.1", DSTMASK="255.255.255.0",

eRAN
RTTYPE=NEXTHOP, NEXTHOP="10.1.1.2", PREF=60;

//(Optional 2) Adding a source IP route with the local IP address of the eNodeB as the source IP address
ADD SRCIPRT: SRCRTIDX=0, SN=7, SBT=BASE_BOARD, SRCIP="10.1.1.1", RTTYPE=NEXTHOP,
NEXTHOP="10.1.1.2", PREF=60;
//Setting DSCP values for signaling data, O&M data, and IP clock data
SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMHIGHPRI=46, OMLOWPRI=18, IPCLKPRI=46;
//Setting DSCP values for user data
ADD UDT: UDTNO=9,UDTPARAGRPID=48;
ADD UDTPARAGRP:
UDTPARAGRPID=40,PRIRULE=DSCP,PRI=46,PRIMTRANRSCTYPE=HQ,PRIMPTLOADTH=100,PRIM2SECPTLOAD
RATH=0;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
UDTPARAGRPID=48,PRIRULE=DSCP,PRI=0,PRIMTRANRSCTYPE=HQ,PRIMPTLOADTH=100,PRIM2SECPTLOADR
ATH=1000;
//Modifying the DSCP for GTP-U echo packets
MOD GTPU: TIMEOUTTH=5000, TIMEOUTCNT=3, DSCP=0, STATICCHK=ENABLE;
//Setting the DSCP for IP PM packets when adding the IP PM session
ADD IPPMSESSION: IPPMSN=0, IPPMTYPE=FOUR_TUPLE, BINDPATH=NO, LOCALIP="10.1.1.1",
PEERIP="10.2.1.1", IPPMDSCP=18, DIR=UP;
//Setting the DSCP for BFD packets when adding the BFD session
ADD BFDSESSION: SN=7, CN=0, SRN=0, BFDSN=0, SRCIP="10.1.1.1", DSTIP="10.1.1.2", HT=SINGLE_HOP,
CATLOG=RELIABILITY, DSCP=46, VER=STANDARD, BFDAUTHSW=OFF;
//Setting the DSCP value for IKE packets
SET IKECFG:IKELNM="IKE", IKEKLI=20, IKEKLT=60, DSCP=46;
//Setting the DSCP value for ping packets when running the PING command
PING: SN=7, SRCIP="10.1.1.1", DSTIP="10.2.1.1", PKTSIZE=32, CONTPING=DISABLE, NUM=4, PRIRULE=DSCP,
DSCP=46, PKTINT=1000, APPTIF=NO;
//Setting the DSCP value for TRACERT packets when running the TRACERT command
TRACERT: SN=7, SRCIP="10.1.1.1", DSTIP="10.2.1.1", TTLFST=1, TTLMAX=30, UDPPORT=52889, PRBNUM=3,
TIMEOUT=5000, DF=OFF, DSCP=46;
//Setting VLAN information in single VLAN mode
//Adding mapping relationships between next-hop IP addresses and VLANs
ADD VLANMAP: NEXTHOPIP="10.1.1.2", MASK="255.255.255.0", VLANMODE=SINGLEVLAN, VLANID=1,
SETPRIO=DISABLE, VRFIDX=0;
//Setting mapping relationships between DSCP values and VLAN priorities
SET DSCPMAP: DSCP=48, VLANPRIO=6, VRFIDX=0;

eRAN

//Setting VLAN information in VLAN group mode
//Adding mapping relationships between next-hop IP addresses and VLAN groups
ADD VLANMAP:NEXTHOPIP="10.1.1.2", MASK="255.255.255.0", VLANMODE=VLANGROUP,
VLANGROUPNO=0, VRFIDX=0;
//Adding mapping relationships among traffic types, DSCP values, and VLANs
ADD VLANCLASS: VLANGROUPNO=0, TRAFFIC=SIG, VLANID=1, VLANPRIO=6;
ADD VLANCLASS: VLANGROUPNO=0, TRAFFIC=OM_HIGH, VLANID=1, VLANPRIO=5;
ADD VLANCLASS: VLANGROUPNO=0, TRAFFIC=OM_LOW, VLANID=1, VLANPRIO=2;
ADD VLANCLASS: VLANGROUPNO=0, TRAFFIC=USERDATA, SRVPRIO=46, VLANID=1, VLANPRIO=5;
ADD VLANCLASS: VLANGROUPNO=0, TRAFFIC=OTHER, VLANID=1, VLANPRIO=5;
3.1.4.1.4 Using MML Commands (New Model)

//Setting Ethernet port attributes
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PORTID=1, PA=FIBER, SPEED=1000M,
DUPLEX=FULL, FC=OPEN, FERAT=10, FERDT=10, RXBCPKTALMOCRTHD=322, RXBCPKTALMCLRTHD=290;
//Configuring a VLAN (based on the interface)
ADD INTERFACE: ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=1, VLANID=100, VRFIDX=0, MTU4=1500,
ARPPROXY=ENABLE;
//(Optional) Configuring a VLAN priority mapping
ADD DSCP2PCPMAP: DSCP2PCPMAPID=0, DEFAULTPCP=0;
ADD DSCP2PCPREF: DSCP2PCPMAPID=0, DSCP=48, PCP=6;
//Configuring a VLAN (based on the VLAN map) and adding the mapping between the VLAN ID and the
next hop
//Adding mapping relationships among traffic types, DSCP values, and VLANs
ADD VLANCLASS: VLANGROUPNO=0, TRAFFIC=SIG, VLANID=1, VLANPRIO=6;
ADD VLANCLASS: VLANGROUPNO=0, TRAFFIC=OM_HIGH, VLANID=1, VLANPRIO=5;
ADD VLANCLASS: VLANGROUPNO=0, TRAFFIC=OM_LOW, VLANID=1, VLANPRIO=2;
ADD VLANCLASS: VLANGROUPNO=0, TRAFFIC=OTHER, VLANID=1, VLANPRIO=5;
ADD INTERFACE: ITFID=0, ITFTYPE=NORMAL, PT=ETH, PORTID=1, VRFIDX=0, MTU4=1500,
ARPPROXY=ENABLE;
//Adding an interface IP address for the eNodeB
ADD IPADDR4: ITFID=0, IP="10.1.1.1", MASK="255.255.255.0", VRFIDX=0;
//(Optional) Adding a loopback IP address for the eNodeB
ADD LOOPBACK: PORTID=0, CN=0, SRN=0, SN=7;
ADD INTERFACE: ITFID=1, ITFTYPE=NORMAL, PT=LOOPINT, PORTID=0, VRFIDX=0;
//(Optional 1) Adding a destination IP route from the eNodeB to the peer device
ADD IPROUTE4: RTIDX=0, DSTIP="10.2.1.1", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP,
NEXTHOP="10.1.1.2", PREF=60;
//(Optional 2) Adding a source IP route with the local IP address of the eNodeB as the source IP address
//When an interface IP address is configured
ADD SRCIPROUTE4: SRCRTIDX=0, SRCIP="10.1.1.1", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.2", PREF=60;
//When a loopback IP address is configured
ADD SRCIPROUTE4: SRCRTIDX=0, SRCIP="10.2.1.1", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.2", PREF=60;
//Setting DSCP values for signaling data, O&M data, and IP clock data
//Setting DSCP values for user data

eRAN

ADD UDTPARAGRP:
RATH=0;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
ATH=1000;
//Setting the DSCP for IP PM packets when adding the IP PM session
//Setting the DSCP for BFD packets when adding the BFD session
ADD BFD: BFDSN=100, SRCIP="10.1.1.1", DSTIP="10.1.1.2", MYDISCREAMINATOR=1, HT=SINGLE_HOP,
//Setting the DSCP value for ping packets when running the PING command
//Setting the DSCP value for TRACERT packets when running the TRACERT command
3.1.4.1.5 Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.

eRAN
3.1.4.2 Activation Verification

The verification procedure is as follows:
Step 1 Run the DSP ETHPORT command to query the status of an Ethernet port.
Expected result:
● The values of Port Status and Physical Layer Status are UP, indicating that
the physical port is successfully activated.
● The values of Local Speed and Peer Speed are the same.
● The values of Local Duplex and Peer Duplex are the same.
Step 2 Run the DSP DEVIP (in the old model)/DSP IPADDR4 (in the new model)
command to check whether DEVIP (old model)/IPADDR4 (new model) takes
effect.
Expected result: The configured IP address takes effect.
Step 3 (Optional) Run the DSP IPRT (in the old model)/DSP IPROUTE4 (in the new
model) command to check the route status.
Expected result: The value of Valid State of IP Route is Valid, indicating that the
route takes effect.
Step 4 (Optional) Run the DSP SRCIPRT (in the old model)/DSP SRCIPROUTE4 (in the
new model) command to check the route status.
Expected result: The value of Valid State of IP Route is Valid, indicating that the
route takes effect.
Step 5 Run the PING command to ping the peer IP address, with the local IP address set
to the corresponding IP address specified in the DEVIP (in the old model)/
IPADDR4 (in the new model) MO.
Expected result: The peer IP address is pinged successfully, indicating that the
route and IP address specified in the DEVIP (in the old model)/IPADDR4 (in the
new model) MO have taken effect.
----End
3.1.4.3 Network Monitoring

For details about troubleshooting, see eRAN Troubleshooting Guide in 3900 &
5900 Series Base Station Product Documentation.

IPv6 transmission requires the new transmission model. Set the
GTRANSPARA.TRANSCFGMODE parameter to NEW.

eRAN
Ethernet Port

r Name
Port ID ETHPORT.PO This parameter uniquely identifies an Ethernet

RTID port. For an automatically created Ethernet port,
the port ID includes the cabinet No., subrack No.,
and slot No. from the most significant bit to the
least significant bit. In the new model, this
parameter is mandatory, and the value must be
unique.


attributea must be the same as that of the peer
port.
For a macro base station, when a UMPT or UMDU
Speed ETHPORT.SPE Set the speed mode to the same as that of the
ED peer port. Set this parameter based on the network
plan.

eRAN

r Name

PLEX Ethernet port.
parameter to FULL.
● For a 1000 Mbit/s electrical port, set the Speed
AUTO.
parameter to AUTO.
a: If this parameter is set to AUTO, port activation may take about one minute.
If the port attribute is reconfigured as optical on the peer device, the
reconfiguration takes effect only after this optical port on the peer device is
reset or the Ethernet port on the local eNodeB is reset by running the RST
ETHPORT command.
Loopback Interface
The following table lists the parameters that must be set in the LOOPBACK MO to

r Name
Port ID LOOPBACK.P This parameter specifies the ID of a loopback

ORTID interface and is unique in the system.
Cabinet LOOPBACK.C This parameter specifies the cabinet number of the

No. N board to which the loopback interface belongs.
Subrack LOOPBACK.S This parameter specifies the subrack number of the

No. RN board to which the loopback interface belongs.
Slot No. LOOPBACK.S This parameter specifies the slot number of the
N board to which the loopback interface belongs.

eRAN

The following table describes the key parameters that must be set in a
DSCP2PCPMAP MO to configure mapping relationships between traffic types and
VLAN priorities.

r Name
DSCP-to- DSCP2PCPM This parameter specifies the ID of the mapping

PCP AP.DSCP2PCP table between DSCPs and VLAN priorities.
Mapping MAPID
ID
Default DSCP2PCPM This parameter specifies the default VLAN priority

PCP AP.DEFAULTP used for non-mapped DSCPs.
CP
Differenti DSCP2PCPM This parameter specifies the DSCP. A larger value
ated AP.DSCP indicates a higher priority.
Services
Code
Point
Priority DSCP2PCPM This parameter specifies the VLAN priority. A larger

Code AP.PCP value indicates a higher priority.
Point
VLAN Interface
The following table describes the key parameters that must be set in an
INTERFACE MO to configure a VLAN interface and VLAN.

r Name

ID FID
Type FTYPE which can be set to NORMAL or VLAN. For a
VLAN interface, set this parameter to VLAN.
For VLAN interfaces used to implement IPv6
transmission, this parameter can only be set to
ETH.

eRAN

r Name

VLAN ID INTERFACE.V This parameter specifies the VLAN ID of an

LANID interface.
This parameter must be set to configure a VLAN
interface.

ID

Transmiss ● The minimum E2E MTU of the transmission link
ion Unit is the MTU of the interface on the base station
side.
● If the PMTUCFG.MODE parameter is set to
ACTIVE, set this parameter to the maximum
value among multiple links over the interface to
improve transmission efficiency. If the
PMTUCFG.MODE parameter is set to PASSIVE,
set this parameter to the minimum value
among multiple links over the interface.
IPv6 INTERFACE.IP This parameter specifies whether to enable the

Switch V6SW IPv6 function on an interface. Set this parameter to
ENABLE for an interface on which IPv6
transmission or dual-stack transmission is used.
Common Interfaces
The following table describes the parameters that must be set in the INTERFACE
MO to configure common interfaces.

r Name

ID FID
Type FTYPE which can be set to NORMAL or VLAN. For
common interfaces, set this parameter to
NORMAL.

eRAN

r Name
For a common IPv6 interface, set this parameter to
ETH or LOOPINT.
If packets that do not carry VLAN tags need to be
received or sent, a common interface with the port
type set to ETH is required.
If the service IP address is a logical IP address (for
example, in security networking), a common
interface with the port type set to LOOPIF is
required.

VLAN INTERFACE.T This parameter specifies whether the interface

Tagged AGGED processes tagged packets.
Switch

ID

Transmiss ● The minimum E2E MTU of the transmission link
ion Unit is the MTU of the interface on the base station
side.
IPv6 INTERFACE.IP This parameter specifies whether to enable the

Switch V6SW IPv6 function on an interface. Set this parameter to
ENABLE for an interface on which IPv6
transmission or dual-stack transmission is used.
The following table lists the parameters that must be set in the INTERFACE MO to

r Name

ID FID
NORMAL.

eRAN

r Name
LOOPINT.

For a loopback interface, set this parameter to the
same value as that of the LOOPBACK.PORTID
parameter.
IPv6 Address Configuration

An IPv6 address can be configured for a VLAN or common interface.
The following table lists the parameters that must be set in an IPADDR6 MO to
configure an IPv6 address.

r Name
IPv6 IPADDR6.IPA Set this parameter based on the network plan.

Address DDR6ID
ID
Interface IPADDR6.ITFI This parameter specifies the ID of an interface.

ID D
IPv6 IPADDR6.IPV This parameter specifies the IPv6 address. If NR
Address 6 and LTE share the main control board, plan
different local IPv6 addresses for NR and LTE.
Prefix IPADDR6.PFX This parameter specifies the prefix length of an

Length LEN IPv6 address.
A 127-bit mask can be configured for the IP
address of an Ethernet interface. During transport
network planning, only the directly connected 127-
bit network segment can be set to all 0s or all 1s.
IPv6 Route Configuration

The following table lists the parameters that must be set in the IPROUTE6 MO to
configure IPv6 routes. IPv6 routes do not need to be configured for layer 2
networking.

eRAN

r Name
Route IPROUTE6.RT This parameter specifies the ID of a static IPv6

Index IDX route.
Destinatio IPROUTE6.DS This parameter specifies the destination IPv6

n IPv6 TIP address of a static IPv6 route.
Address ● The default route is not recommended. In the
default route, the destination IPv6 address is
0::0 and the prefix length is 0.
recommended. That is, set the destination IPv6
address to the IP address of this segment. The
prefix length is less than 128.
Prefix IPROUTE6.PF This parameter specifies the prefix length of the

Length XLEN destination IPv6 address of a static IPv6 route.
Route IPROUTE6.RT This parameter specifies the type of a static IPv6

Type TYPE route. Set this parameter to NEXTHOP.
Next-Hop IPROUTE6.NE This parameter specifies the next-hop IPv6 address

IPv6 XTHOP of a static IPv6 route.
Address
Preferenc IPROUTE6.PR This parameter specifies the priority of a static IPv6

e EF route. A smaller parameter value indicates a higher
priority.
(Optional) The following table lists the parameters that must be set in an
SRCIPROUTE6 MO to configure source-based IPv6 routing. Source-based IPv6
routing does not need to be configured for layer 2 networking.

r Name
IPv6 SRCIPROUTE This parameter specifies the ID of a source IPv6

Source 6.SRCRTIDX route.
Route
Index
Source SRCIPROUTE This parameter specifies the source IPv6 address,

IPv6 6.SRCIP which is the IP address configured in the IPADDR6
Address MO.

Type 6.RTTYPE route. You can set this parameter to
NEXTHOP(Next Hop) or IF(Exit Interface).

eRAN

r Name
Next-Hop SRCIPROUTE This parameter specifies the next-hop IPv6 address

IPv6 6.NEXTHOP of a source IPv6 route. The address must be a
Address global unicast address.
Preferenc SRCIPROUTE This parameter specifies the priority of the source

e 6.PREF IPv6 routing entry. A smaller value indicates a
higher priority.
//Setting the Ethernet port attributes

//(Optional) Configuring a VLAN priority mapping
ADD DSCP2PCPMAP: DSCP2PCPMAPID=0, DEFAULTPCP=0;
//Configuring a VLAN interface with the VLAN ID, IPv6 Maximum Transmission Unit, and IPv6 Switch
parameters set
ADD INTERFACE: ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=1, VLANID=100, DSCP2PCPMAPID=0,
MTU6=1500, IPV6SW=ENABLE;
//Configuring a common interface with the IPv6 Maximum Transmission Unit and IPv6 Switch parameters
set
ADD INTERFACE: ITFID=0, ITFTYPE=NORMAL, PT=ETH, PORTID=1, VRFIDX=0, MTU6=1500,
IPV6SW=ENABLE;
//Adding an eNodeB loopback IP address
ADD INTERFACE: ITFID=10, ITFTYPE=NORMAL, PT=LOOPINT, PORTID=8, VRFIDX=0, IPV6SW=ENABLE;
ADD IPADDR6: IPADDR6ID="LTELOOPBACK", ITFID=10, IPV6="2001:db8:100:ad1:200:100:200:100",
PFXLEN=128;
//Adding an eNodeB IPv6 address
ADD IPADDR6: IPADDR6ID="LTE", ITFID=0, IPV6="2001:db8:100:ad1:200:100:100:2", PFXLEN=126;
//(Optional) Adding a destination IP route from the eNodeB to the peer device
ADD IPROUTE6: RTIDX=0, DSTIP="2001:db8:100:ad1:200:100:3001:0", PFXLEN=112, RTTYPE=NEXTHOP,
NEXTHOP="2001:db8:100:ad1:200:100:100:1", PREF=60;
//(Optional) Adding a source IP route from the eNodeB to the peer device
ADD SRCIPROUTE6: SRCRTIDX=0, SRCIP="2001:db8:100:ad1:200:100:200:100",RTTYPE=NEXTHOP,
//Setting DSCP values for signaling, O&M data, and IP clock data
//Setting DSCP values for service data
ADD UDTPARAGRP:
RATH=0;
ADD UDTPARAGRP:

eRAN
RATH=1000;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
RATH=1000;
ADD UDTPARAGRP:
ATH=1000;


Step 1 Run the DSP ETHPORT command to query the status of an Ethernet port.
Expected result:
● The values of Port Status and Physical Layer Status are UP, indicating that
the physical port is successfully activated.
● The values of Local Speed and Peer Speed are the same.
● The values of Local Duplex and Peer Duplex are the same.
Step 2 Run the DSP IPADDR6 command to check whether the IPv6 address takes effect.
Expected result: The configured IP address takes effect.
Step 3 (Optional) Run the DSP IPROUTE6 or DSP SRCIPROUTE6 command to check the
route status.
Expected result: The value of Valid State is Valid, indicating that the route has
taken effect.
Step 4 Run the PING6 command to ping the peer IP address, with the local IP address set
to the corresponding IPv6 address (in the IPADDR6 MO).
Expected result: The peer IP address is successfully pinged, indicating that the IPv6
route and IPv6 address (in the IPADDR6 MO) have taken effect.
----End

eRAN

3.1.6 Operation and Maintenance (IPv4/IPv6 Dual-Stack

Transmission)
3.1.6.1.1 Data Preparation

For details about how to prepare IPv4 transmission data, see 3.1.4.1.2 Data
Preparation (New Model).
For details about how to prepare IPv6 transmission data, see 3.1.5.1.1 Data
NOTE
IPv6 transmission and dual-stack transmission support only the new transmission model. If
IPv6 configuration is added to IPv4 configuration on the live network to form dual-stack
transmission, the IPv4 configuration must be first converted into the new model, then the
single VLAN or VLAN group configuration mode of IPv4 must be converted to the interface
VLAN configuration mode, and at last the IPv6 configuration is added.
3.1.6.1.2 Using MML Commands

For details about how to configure IPv4 transmission data using MML commands,
see 3.1.4.1.4 Using MML Commands (New Model).
For details about how to configure the IPv6 transmission data using MML
commands, see 3.1.5.1.2 Using MML Commands (New Model).


For how to perform activation verification for IPv4 transmission, see 3.1.4.2
Activation Verification.
For how to perform activation verification for IPv6 transmission, see 3.1.5.2
Activation Verification.

3.2 Deployment of an S1 Interface

eRAN
3.2.1 Principles
IPv4 Transmission
For IPv4 transmission, an S1 interface can be set up in either of the following
modes:
● Link configuration mode: The IPPATH, ENODEBPATH, SCTPLNK, CPBEARER,

and S1INTERFACE MOs are to be configured.
● Endpoint configuration mode: An S1 interface is automatically set up after the
following data is configured: S1, EPGROUP, SCTPTEMPLATE, SCTPHOST,
SCTPPEER, USERPLANEHOST, and USERPLANEPEER. Endpoint configuration
mode is recommended.
When configuring the S1 interface in link configuration mode, collect the

following information according to operators' network plan: local IP addresses of
the S1-C and S1-U interfaces of the eNodeB, local port number, peer IP address,
and peer port number. Information, including settings of SCTP negotiation- and
detection-related parameters in SCTPLNK MOs, the operators owning the S1
interfaces, and the versions of connected MMEs, must be collected.
For IPv4 transmission, this document describes only S1 interface setup in link
configuration mode. For details about S1 interface setup in endpoint configuration
mode, see S1 and X2 Self-Management.
IPv6 Transmission or IPv4/IPv6 Dual-Stack Transmission

For IPv6 transmission, an S1 interface can be set up only in endpoint mode. To
automatically set up an S1 interface, the following MOs must be configured: S1,
EPGROUP, SCTPTEMPLATE, SCTPHOST, SCTPPEER, USERPLANEHOST, and
USERPLANEPEER.
For how to configure S1 interfaces in endpoint mode for IPv6 transmission or IPv4/
IPv6 dual-stack transmission, see S1 and X2 Self-Management.
3.2.2.1 Benefits
None
3.2.2.2 Impacts
Network Impacts
The length of a basic IPv6 packet header is 40 bytes, which is longer than that of
a basic IPv4 packet header (20 bytes). Therefore, the transmission efficiency of an
IPv6 network is slightly lower than that of an IPv4 network. For example, the
length of an IPv4 packet is 800 bytes and the length of an IPv6 packet is 820
bytes. The IPv6 transmission efficiency is 2.5% lower than IPv4 transmission
efficiency.

eRAN
Function Impacts
RAT Function Function Switch Reference Description
Name
FDD Transport RSCGRPALG.TXSSW, Transmissi Transport

Dynamic Flow RSCGRPALG.TXBWAS on Dynamic Flow
Control W, and Resource Control does not
RSCGRPALG.RXBWAS Managem apply to IPv6
W ent scenarios.
FDD Transport TACALG.PORTULCAC Transmissi Transport

Overbooking SW and on Overbooking
TACALG.PORTDLCAC Resource does not apply to
SW Managem IPv6 scenarios.
ent
FDD Transport TOLCALG.TRMULOLC Transmissi Transport
Resource SWITCH and on Resource
Overload TOLCALG.TRMDLOLC Resource Overload Control
Control SWITCH Managem does not apply to
ent IPv6 scenarios.
FDD Different None Transmissi Different

Transport on Transport Paths
Paths based Resource based on QoS
on QoS Grade Managem Grade does not
ent apply to IPv6
scenarios.
FDD Compression In PPP networking IP Compression &

& scenarios: PFC Switch Transmissi Multiplexing over
Multiplexing (PPPLNK.PFC), ACFC on E1/T1 does not
over E1/T1 Switch Efficiency apply to IPv6
(PPPLNK.ACFC) Improvem scenarios.
In MP networking ent
scenarios: PFC Switch
(MPLNK.PFC), ACFC
Switch
(MPLNK.ACFC)
FDD IP Header In PPP networking IP IP Header

Compression scenarios: Transmissi Compression
PPPLNK.IPHC on does not apply to
Efficiency IPv6 scenarios.
In MP networking Improvem
scenarios: ent
MPGRP.IPHC

eRAN
RAT Function Function Switch Reference Description

Name
FDD PPP MUX None IP PPP MUX does

Transmissi not apply to IPv6
on scenarios.
Efficiency
Improvem
ent
FDD MLPPP/MC- MPGRP.MCPPP IP MLPPP/MC-PPP
PPP Transmissi does not apply to
on IPv6 scenarios.
Efficiency
Improvem
ent
FDD 2G/3G and None 2G, 3G 2G/3G and LTE
LTE Co- and LTE Co-transmission
transmission Co- does not apply to
transmissi IPv6 scenarios.
on
FDD IP None IP IP Performance
Performance Performan Monitor does not
Monitor ce Monitor apply to IPv6
scenarios.
FDD IP Active None IP Active IP Active

Performance Performan Performance
Measurement ce Measurement
Measurem does not apply to
ent IPv6 scenarios.
FDD Ethernet None Ethernet Ethernet OAM

OAM OAM does not apply to
IPv6 scenarios.
3.2.3 Requirements
3.2.3.1 Licenses
RAT Feature ID Feature Model Sales Unit
Name
FDD LOFD-003017 S1 and X2 LT1SSXIPV600 per eNodeB

over IPv6
FDD MLOFD-0030 S1 over IPv6 ML1SS1IPV60 per eNodeB

17 0

eRAN
3.2.3.2 Software
None

None
3.2.3.3 Hardware
Base Station Models

● BTS3912E
● BTS3911E
Boards
The UMDU and UMPT of the eNodeB support this function.
For FDD, the BBU3910C does not support the tree topology.
RF Modules
This feature does not depend on RF modules.
3.2.3.4 Networking
Table 3-1 describes the requirements of the S1 interface for transmission
networking.
Table 3-1 Requirements of the S1 interface for transmission networking
Application Delay (ms) Jitter (ms) Packet Loss Rate

Scenario
Best 5 2 0.0001%
Recommended 10 4 0.001%
Tolerable 20 8 0.5%

eRAN
NOTE
The Delay (ms) values presented in Table 3-1 are one-way delays meeting basic
transmission requirements. If a feature has special delay requirements, the special delay
must be shorter than the one-way delay. For details about any special delay requirements,
see the corresponding feature parameter description.
In Table 3-1, the Best scenario ensures the QoS of all services and the Recommended
scenario ensures the QoS of services with a QCI of 1, 2, 3, or 7. The Tolerable scenario
ensures establishment of services, but does not ensure the QoS of QCI-specific services
whose QoS requirements are beyond the QoS specifications for the corresponding QCI.
● Transmission networking planning
eNodeBs support star, chain, and tree topologies on IP networks, as shown in
Figure 3-2, Figure 3-3, and Figure 3-4.
NOTE
The BTS3912E does not support the chain topology.
Figure 3-2 eNodeBs deployed using the star topology
Figure 3-3 eNodeBs deployed using the chain topology

eRAN
Figure 3-4 eNodeBs deployed using the tree topology
Table 3-2 describes application scenarios of these topologies.
Table 3-2 Three topologies and their application scenarios
Topology Application Scenario
Star Commonly used and applicable to densely populated areas

topology
Chain Applicable to sparsely populated belt-shaped areas, such as

topology areas along expressways and railways
Tree Applicable to areas with complicated network architecture,

topology site distribution, and UE distribution, for example, hotspots
where UEs are widely distributed
An eNodeB communicates with an MME or S-GW through an S1 interface

and with another eNodeB through an X2 or eX2 interface. For interface
specifications, see S1 and X2 Self-Management and eX2 Self-Management.
● IP address planning
During the planning of IP addresses for an eNodeB, O&M, S1-C, and S1-U IP
addresses can be identical or different. The following principles are used for
determining whether IP addresses are identically configured:
– If O&M channels, S1-C interfaces, and S1-U interfaces need to be isolated
by IP addresses, plan different IP addresses.
– If O&M channels, S1-C interfaces, and S1-U interfaces do not need to be
isolated by IP addresses, plan identical IP addresses.
The IP address of an IP clock must be a port IP address (Ethernet port IP
address or Ethernet trunk IP address) if the IP clock link complies with the
Huawei proprietary protocol, and can be a port IP address or a logical IP
address (loopback interface IP address) if the IP clock link complies with the
IEEE 1588V2 protocol.

eRAN
3.2.3.5 Others
None
3.2.4 Operation and Maintenance

This section describes data preparation when the GTRANSPARA.TRANSCFGMODE
parameter is set to OLD.
The RSCGRP MO is required for precise management of transmission resources. If
this MO is not configured, user plane data is transmitted by the default
transmission resource group. For details about transmission resource group
management, see Transmission Resource Management.
(Optional) The following table describes the parameters that must be set in an
RSCGRP MO to configure a base station transmission resource group for
bandwidth management.

r Name
Transmiss RSCGRP.RSC Set this parameter based on the network plan.

ion GRPID It is recommended that different transmission
Resource resource groups be configured for different
Group ID operators to manage their user plane resources.
You do not need to add a transmission resource
group if the default transmission resource group is
used. If statistics of performance counters for this
group are required, add a transmission resource
group.
Subboard RSCGRP.SBT This parameter specifies the sub-board type of the

Type board to which a transmission resource group
belongs.
Set this parameter to BASE_BOARD.
Bearing RSCGRP.PT This parameter specifies the type of the port

Port Type carrying the transmission resource group.
Set this parameter to ETH or ETHTRK.
Tx RSCGRP.TXB This parameter specifies the restricted transmit

Bandwidt W bandwidth for the transmission resource group. Set
h this parameter based on the network plan. This
parameter is required in single-rate mode for
admission control and traffic shaping.

eRAN

r Name
Rx RSCGRP.RXB This parameter specifies the restricted receive

Bandwidt W bandwidth for the transmission resource group. Set
admission control.
TX RSCGRP.TXCB This parameter specifies the transmit committed

Committe S burst size.
d Burst Set this parameter based on the network plan.
Size Ensure that the value of RSCGRP.TXCBS is greater
than or equal to the value of the RSCGRP.TXBW
parameter for traffic shaping.
TX RSCGRP.TXEB This parameter specifies the transmit excessive

Excessive S burst size.
Burst Size Set this parameter to a value twice the transmit
bandwidth of the transmission resource group.
Schedulin RSCGRP.WEI This parameter specifies the scheduling weight for

g Weight GHT a transmission resource group. It is used for
calculating the bandwidth scheduled to a resource
group, which helps implement user admission
control.
If the bandwidth for physical ports is restricted, the
default value is recommended based on the
network plan.
TX RSCGRP.TXCI This parameter specifies the committed

Committe R information rate (CIR) for transmission over the
d transmission resource group.
Informati Set this parameter based on the network plan. This
on Rate parameter specifies the TX CIR bandwidth of the
transmission resource group. The value indicates a
TX rate committed to the operator. Set this
parameter based on the network plan. This
parameter is used for uplink admission control and
scheduling in dual-rate mode.
RX RSCGRP.RXCI This parameter specifies the receive CIR over the

Committe R transmission resource group.
d Set this parameter based on the network plan. This
Informati parameter is required in double-rate mode for
on Rate downlink admission control.

eRAN

r Name
TX Peak RSCGRP.TXPI This parameter specifies the transmit PIR for the
Informati R transmission resource group.
on Rate Set this parameter based on the network plan. This
parameter is required in double-rate mode for
uplink admission control, scheduling, and traffic
shaping.
RX Peak RSCGRP.RXPI This parameter specifies the receive PIR for the
Informati R transmission resource group. This parameter value
on Rate is used as the downlink transmission admission
bandwidth.
Set this parameter based on the network plan. This
downlink admission control.
TX Peak RSCGRP.TXPB This parameter specifies the transmit peak burst

Burst Size S size for the transmission resource group.
Set this parameter based on the network plan.
Ensure that the value of RSCGRP.TXPBS is greater
than or equal to the values of RSCGRP.TXCBS and
RSCGRP.TXPIR.
On the S1-U interface, it is recommended that GTP-U detection be enabled to

check the connectivity of the S1-U interface by using GTP-U echo messages. GTP-
U detection can be enabled by configuring the GTPU MO. For details about how
to configure this MO, see the GTPU MO in 5.2.4.1.1 Data Preparation (Old
Model).
S1 Interface Created in Link Configuration Mode
The following table details the parameters to be set in the IPPATH MO to
configure an IP path for user-plane data transmission between the eNodeB and
the S-GW. (Note that the local IP address specified in the IPPATH MO must be
configured on the board that provides transmission interfaces for the eNodeB.)
The transmission ports include PPP, MPGRP, ETH, ETHTRUNK, and TUNNEL.

r Name
Path ID IPPATH.PATH Set this parameter based on the network plan. For
ID an S1 interface, a value within the range of 0 to
65535 is recommended.
Port Type IPPATH.PT This parameter specifies the type of physical port
to which the IP path belongs. Set this parameter

eRAN

r Name
Join IPPATH.JNRS This parameter specifies whether the IP path is

Transmiss CGRP added to a transmission resource group.
ion If this parameter is set to ENABLE, the IP path is
Resource added to the dedicated transmission resource
Group group.
If this parameter is set to DISABLE, the IP path is
added to the default transmission resource group.
Set this parameter based on the network plan. It is
recommended that this parameter be set to
ENABLE to facilitate transmission resource
management.
Transmiss IPPATH.RSCG Set this parameter based on the network plan.

ion RPID Ensure that the transmission resource group ID has
Resource been configured in the associated RSCGRP MO.
Group ID This parameter is valid only when the
IPPATH.JNRSCGRP parameter is set to ENABLE.
Local IP IPPATH.LOCA This parameter specifies the local IP address of an

Address LIP IP path, that is, the local IP address of the S1 user
plane. Set this parameter based on the network
plan. Ensure that the IP address has been
configured in the associated DEVIP MO.
Peer IP IPPATH.PEERI This parameter specifies the peer IP address of a

Address P peer path, that is, the IP address of the peer S-GW
for an S1 interface. Set this parameter based on
the network plan.
Path Type IPPATH.PATH This parameter specifies the type of an IP path. Set
TYPE this parameter to ANY.
DSCP IPPATH.DSCP This parameter specifies the DSCP value of an IP

path.
Set this parameter based on the type of services to
be carried on the IP path.
This parameter is valid only when
IPPATH.PATHTYPE is set to FIXED.
Descriptio IPPATH.DESC This parameter specifies IP path information.

n RI
The following table describes the parameters that must be set in an eNodeBPath
MO to specify whether the IP path is established over an S1 or X2 interface.

eRAN

r Name
IP Path ID eNodeBPath.I This parameter specifies the ID of an IP path. In co-

pPathId MPT scenarios, LTE cannot use the same IP path ID
as other RATs. Set this parameter based on the
network plan.
Applicatio eNodeBPath. This parameter specifies the application type of an

n Type AppType IP path.
● If the IP path is established over an S1 interface,
set this parameter to S1.
● If the IP path is established over an X2 interface,
set this parameter to X2.
X2 eNodeBPath. This parameter specifies the X2 interface ID of the

Interface X2InterfaceId IP path.
ID This parameter indicates the X2 interface ID
corresponding to the eNodeBPath.IpPathId
parameter and the mapping between the X2 user
plane and X2 control plane.
The following table describes the parameters that must be set in an SCTPLNK MO
to specify a link for transmitting S1 control-plane data.

r Name
Link No. SCTPLNK.SCT This parameter specifies the number of the SCTP
PNO link. Set this parameter based on the network plan.
First Local SCTPLNK.LO This parameter specifies the first local IP address
IP CIP for the SCTP link.
Address Set this parameter based on the network plan.
Ensure that the IP address has been configured in
the associated DEVIP MO.
Second SCTPLNK.SEC This parameter specifies the second local IP

Local IP LOCIP address for the SCTP link.
Address Set this parameter based on the network plan only
when SCTP multihoming is used. Ensure that the IP
address has been configured in the associated
DEVIP MO.
Local SCTPLNK.LO This parameter specifies the local port number of

SCTP Port CPORT the SCTP link. Set this parameter based on the
No. network plan.

eRAN

r Name
First Peer SCTPLNK.PEE This parameter specifies the first peer IP address of
IP RIP the SCTP link. Set this parameter based on the
Address network plan.
● For an S1 interface, set this parameter to the IP
address of the MME.
● For an X2 interface, set this parameter to the
control-plane IP address of the peer eNodeB.
Second SCTPLNK.SEC This parameter specifies the second peer IP

Peer IP PEERIP address.
Address Set this parameter based on the network plan
when SCTP multihoming is used.
Peer SCTP SCTPLNK.PEE This parameter specifies the peer port number of
Port No. RPORT the SCTP link. Set this parameter based on the
network plan.
● For an S1 interface, set this parameter to the
SCTP port number of the peer MME.
SCTP port number of the peer eNodeB.
Switch SCTPLNK.AU This parameter specifies whether to switch back to

Back Flag TOSWITCH the primary path when it is restored. The default
value is recommended.
Heart- SCTPLNK.SW This parameter specifies the number of heartbeats

beat ITCHBACKHB to be detected before the transmission switches
Times NUM back to the primary path. The default value is
When recommended.
Switch
Back
DSCP SCTPLNK.DS Set this parameter based on the network plan if

Switch CPSW RAT-specific signaling priorities need to be
differentiated in co-MPT scenarios.
DSCP SCTPLNK.DS Set this parameter based on the network plan if

CP RAT-specific signaling priorities need to be
The following table describes the parameters that must be set in a CPBEARER MO
to specify transport bearers.

eRAN

r Name
CP Bear CPBEARER.CP This parameter specifies the number of a CP

No. BEARID bearer. Set this parameter based on the network
plan.
Bear Type CPBEARER.BE This parameter specifies the type of a CP bearer.

ARTYPE ● When the lower layer uses SCTP over IPv4, set
this parameter to SCTP.
● When the lower layer uses SCTP over IPv6, set
this parameter to SCTP6.
Link No. CPBEARER.LI This parameter specifies the number of a link

NKNO carried on the CP bearer. Set this parameter based
The following table describes the parameters that must be set in an S1Interface
MO to configure an S1 interface between an eNodeB and an MME.

r Name
S1 S1Interface.S This parameter specifies the S1 interface ID.

Interface 1InterfaceId Set this parameter based on the network plan. The
ID value of this parameter must be different from that
of the X2Interface.X2InterfaceId parameter.
S1 S1Interface.S This parameter specifies the ID of the CP bearer for

Interface 1CpBearerId the S1 interface. Set this parameter based on the
CP Bearer network plan.
ID
CN S1Interface.C This parameter specifies the ID of the operator to

Operator nOperatorId which the S1 interface belongs.
ID Set this parameter based on the network plan.
Ensure that the operator ID has been configured in
the associated CnOperator MO.
MME S1Interface. This parameter specifies the MME version for the
Release MmeRelease S1 interface. Set this parameter based on the
actual MME version.

parameter is set to NEW.
The IPRSCGRP MO is required for precise management of transmission resources.
If this MO is not configured, user plane data is transmitted by the default

eRAN
transmission resource group. For details about transmission resource group

management, see Transmission Resource Management.
(Optional) The following table describes the parameters that must be set in an
IPRSCGRP MO to configure an eNodeB IP transmission resource group for
bandwidth management.

r Name
IP IPRSCGRP.IPR Set this parameter based on the network plan.

Transmiss SCGRPID It is recommended that different transmission
ion resource groups be configured for different
Resource operators to manage their user plane resources.
Group ID
group.
Bearing IPRSCGRP.PT This parameter specifies the type of the port

Port Type carrying an IP transmission resource group.
Set this parameter to ETH or ETHTRK.
Bearing IPRSCGRP.PO This parameter specifies the ID of the port carrying

Port ID RTID an IP transmission resource group.
Resource IPRSCGRP.RS Set this parameter based on the network plan.

Group CGRPNO It is recommended that different transmission
Number resource groups be configured for different
operators to manage their user plane resources.
group.
TX IPRSCGRP.TX This parameter specifies the restricted transmit

Bandwidt BW bandwidth for the transmission resource group. Set
admission control and traffic shaping.
RX IPRSCGRP.RX This parameter specifies the restricted receive

Bandwidt BW bandwidth for the IP transmission resource group.
h Set this parameter based on the network plan. This
admission control.

eRAN

r Name
TX IPRSCGRP.TX This parameter specifies the transmit committed

Committe CBS burst size for an IP transmission resource group.
d Burst This parameter is required for traffic shaping. Set
Size this parameter based on the network plan. Ensure
that the value of IPRSCGRP.TXCBS is greater than
or equal to that of IPRSCGRP.TXBW.
TX IPRSCGRP.TX This parameter specifies the transmit excessive

Excessive EBS burst size for an IP transmission resource group.
Burst Size Set this parameter to a value twice the transmit
bandwidth of the IP transmission resource group.
Schedulin IPRSCGRP.W This parameter specifies the scheduling weight for

g Weight EIGHT an IP transmission resource group. It is used for
calculating the bandwidth scheduled to a resource
group, which helps implement user admission
control.
If the bandwidth for physical ports is restricted, the
default value is recommended based on the
network plan.
TX IPRSCGRP.TX This parameter specifies the transmit CIR for an IP

Committe CIR transmission resource group.
d Set this parameter based on the network plan. This
Informati parameter specifies the TX CIR bandwidth of the
on Rate transmission resource group. The value indicates a
TX rate committed to the operator. Set this
parameter based on the network plan. This
parameter is used for uplink admission control and
scheduling in dual-rate mode.
RX IPRSCGRP.RX This parameter specifies the receive CIR for an IP

Committe CIR transmission resource group. This parameter value
d is used as the downlink transmission admission
Informati bandwidth for non-flow-control services.
on Rate Set this parameter based on the network plan. This
TX Peak IPRSCGRP.TX This parameter specifies the transmit peak

Informati PIR information rate (PIR) for an IP transmission
on Rate resource group.
uplink admission control, scheduling, and traffic
shaping.

eRAN

r Name
RX Peak IPRSCGRP.RX This parameter specifies the receive PIR for an IP

Informati PIR transmission resource group. This parameter value
on Rate is used as the downlink transmission admission
bandwidth.
TX Peak IPRSCGRP.TX This parameter specifies the transmit peak burst

Burst Size PBS size for an IP transmission resource group.
Ensure that the value of IPRSCGRP.TXPBS is
greater than or equal to the values of
IPRSCGRP.TXCBS and IPRSCGRP.TXPIR.
On the S1-U interface, it is recommended that GTP-U detection be enabled to

check the connectivity of the S1-U interface by using GTP-U echo messages. GTP-
U detection can be enabled by configuring the GTPU MO. For details about how
to configure this MO, see the GTPU MO in 5.2.4.1.1 Data Preparation (Old
Model).
S1 Interface Created in Link Configuration Mode
The following table details the parameters to be set in the IPPATH MO to
configure an IP path for user-plane data transmission between the eNodeB and
the S-GW. (Note that the local IP address specified in the IPPATH MO must be
configured on the board that provides transmission interfaces for the eNodeB.)
The transmission ports include PPP, MPGRP, ETH, ETHTRUNK, and TUNNEL.

r Name
Path ID IPPATH.PATH Set this parameter based on the network plan. For
ID an S1 interface, a value within the range of 0 to
65535 is recommended.
Transmiss IPPATH.TRAN This parameter specifies the configuration mode of

ion SCFGMODE the transmission mode. The configuration mode
Configura can be new or old.
tion Set this parameter to NEW.
Mode
Bearing IPPATH.BPT This parameter specifies the type of physical port

Port Type to which the IP path belongs. Set this parameter
Port ID IPPATH.PORT This parameter specifies the interface ID of the IP

ID path.

eRAN

r Name
Join IP IPPATH.JNIPR This parameter specifies whether the IP path is

Transmiss SCGRP added to an IP transmission resource group.
ion If this parameter is set to ENABLE, the IP path is
Resource added to the dedicated transmission resource
Group group.
If this parameter is set to DISABLE, the IP path is
added to the default transmission resource group.
Set this parameter based on the network plan. It is
recommended that this parameter be set to
ENABLE to facilitate transmission resource
management.
IP IPPATH.IPRSC This parameter specifies the ID of the IP

Transmiss GRPID transmission resource group to which the IP path
ion belongs.
Resource Ensure that the IP transmission resource group ID
Group ID has been configured in the associated IPRSCGRP
MO. This parameter is valid only when
IPPATH.JNIPRSCGRP is set to ENABLE.
Local IP IPPATH.LOCA This parameter specifies the local IP address of an

Address LIP IP path, that is, the local IP address of the S1 user
plane. Set this parameter based on the network
plan. Ensure that the IP address has been
configured in the associated DEVIP MO.
Peer IP IPPATH.PEERI This parameter specifies the peer IP address of a

Address P peer path, that is, the IP address of the peer S-GW
for an S1 interface. Set this parameter based on
the network plan.
Path Type IPPATH.PATH This parameter specifies the type of an IP path. Set
TYPE this parameter to ANY.
DSCP IPPATH.DSCP This parameter specifies the DSCP value of an IP

path.
Set this parameter based on the type of services to
be carried on the IP path.
This parameter is valid only when
IPPATH.PATHTYPE is set to FIXED.
Descriptio IPPATH.DESC This parameter specifies IP path information.

n RI
The following table describes the parameters that must be set in an eNodeBPath
MO to specify whether the IP path is established over an S1 or X2 interface.

eRAN

r Name
IP Path ID eNodeBPath.I This parameter specifies the ID of an IP path. In co-

pPathId MPT scenarios, LTE cannot use the same IP path ID
as other RATs. Set this parameter based on the
network plan.
Applicatio eNodeBPath. This parameter specifies the application type of an

n Type AppType IP path.
● If the IP path is established over an S1 interface,
set this parameter to S1.
● If the IP path is established over an X2 interface,
set this parameter to X2.
X2 eNodeBPath. This parameter specifies the X2 interface ID of the

Interface X2InterfaceId IP path.
ID This parameter indicates the X2 interface ID
corresponding to the eNodeBPath.IpPathId
parameter and the mapping between the X2 user
plane and X2 control plane.
The following table describes the parameters that must be set in an SCTPLNK MO
to specify a link for transmitting S1 control-plane data.

r Name
Link No. SCTPLNK.SCT This parameter specifies the number of the SCTP
PNO link. Set this parameter based on the network plan.
IP Version SCTPLNK.IPV This parameter specifies the IP protocol version.

ERSION
First Local SCTPLNK.LOC This parameter specifies the first local IP address
IP IP for the SCTP link.
Address Set this parameter based on the network plan.
Ensure that the IP address has been configured in
the associated DEVIP MO.
Second SCTPLNK.SEC This parameter specifies the second local IP

Local IP LOCIP address for the SCTP link.
Address Set this parameter based on the network plan only
when SCTP multihoming is used. Ensure that the IP
address has been configured in the associated
DEVIP MO.
Local SCTPLNK.LOC This parameter specifies the local port number of

SCTP Port PORT the SCTP link. Set this parameter based on the
No. network plan.

eRAN

r Name
First Peer SCTPLNK.PEE This parameter specifies the first peer IP address of
IP RIP the SCTP link. Set this parameter based on the
● For an S1 interface, set this parameter to the IP
address of the MME.
control-plane IP address of the peer eNodeB.
Second SCTPLNK.SEC This parameter specifies the second peer IP

Peer IP PEERIP address.
Address Set this parameter based on the network plan
when SCTP multihoming is used.
Peer SCTP SCTPLNK.PEE This parameter specifies the peer port number of
Port No. RPORT the SCTP link. Set this parameter based on the
network plan.
● For an S1 interface, set this parameter to the
SCTP port number of the peer MME.
SCTP port number of the peer eNodeB.
Switch SCTPLNK.AU This parameter specifies whether to switch back to

Back Flag TOSWITCH the primary path when it is restored. The default
value is recommended.
Heart- SCTPLNK.SWI This parameter specifies the number of heartbeats

beat TCHBACKHB to be detected before the transmission switches
Times NUM back to the primary path. The default value is
When recommended.
Switch
Back
DSCP SCTPLNK.DSC Set this parameter based on the network plan if

Switch PSW RAT-specific signaling priorities need to be
DSCP SCTPLNK.DSC Set this parameter based on the network plan if

P RAT-specific signaling priorities need to be
The following table describes the parameters that must be set in a CPBEARER MO
to specify transport bearers.

eRAN

r Name
CP Bear CPBEARER.CP This parameter specifies the number of a CP

No. BEARID bearer. Set this parameter based on the network
plan.
Bear Type CPBEARER.BE This parameter specifies the type of a CP bearer.

ARTYPE The SCTPLNK MO supports both IPv4 and IPv6.
Therefore, set this parameter to SCTP.
Link No. CPBEARER.LI This parameter specifies the number of a link

NKNO carried on the CP bearer. Set this parameter based
The following table describes the parameters that must be set in an S1Interface
MO to configure an S1 interface between an eNodeB and an MME.

r Name
S1 S1Interface.S This parameter specifies the S1 interface ID.

Interface 1InterfaceId Set this parameter based on the network plan. The
ID value of this parameter must be different from that
of the X2Interface.X2InterfaceId parameter.
S1 S1Interface.S This parameter specifies the ID of the CP bearer for

Interface 1CpBearerId the S1 interface. Set this parameter based on the
ID
CN S1Interface.C This parameter specifies the ID of the operator to

Operator nOperatorId which the S1 interface belongs.
the associated CnOperator MO.
MME S1Interface. This parameter specifies the MME version for the
Release MmeRelease S1 interface. Set this parameter based on the
actual MME version.
Activation Command Examples

Before using MML commands, refer to 3.2.2.2 Impacts and 3.2.3.2 Software and
complete the parameter configurations for related functions based on the impact
relationships between the functions, as well as the actual network scenario.
//Adding an IP path for the S1 interface
ADD IPPATH: PATHID=0, CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, JNRSCGRP=ENABLE,

eRAN
RSCGRPID=0, VRFIDX=0, LOCALIP="192.168.3.37", PEERIP="192.168.2.20", PATHTYPE=ANY;

//Adding an SCTP link for the S1 interface
ADD SCTPLNK: SCTPNO=0, CN=0, SRN=0, SN=7, LOCIP="192.168.3.37", LOCPORT=36412,
PEERIP="192.168.1.20", PEERPORT=1024, AUTOSWITCH=ENABLE;
//Adding a control-plane bearer for the S1 interface
ADD CPBEARER: CPBEARID=0, BEARTYPE=SCTP, LINKNO=0, FLAG=MASTER;
//Adding an S1 interface
ADD S1INTERFACE: S1InterfaceId=0, S1CpBearerId=0, CnOperatorId=0;
//Specifying that the added IP path is used for the S1 interface
ADD ENODEBPATH: IpPathId=0, AppType=S1;
Deactivation Command Examples

The following provides only deactivation command examples. You can determine
whether to restore the settings of other parameters based on actual network
conditions.
//Removing the application type of an IP path
RMV ENODEBPATH: IpPathId=0;
//Remove an S1 interface
RMV S1INTERFACE: S1InterfaceId=0;
//Removing the control-plane bearer for the S1 interface
RMV CPBEARER: CPBEARID=0, FLAG=MASTER;
//Removing the SCTP link for the S1 interface
RMV SCTPLNK: SCTPNO=0;
//Removing the IP path for the S1 interface
RMV IPPATH: PATHID=0;

complete the parameter configurations for related functions based on the impact
relationships between the functions, as well as the actual network scenario.
//Adding an IP path for the S1 interface
ADD IPPATH: PATHID=0, TRANSCFGMODE=NEW, JNIPRSCGRP=ENABLE, IPRSCGRPID=0, VRFIDX=0,
LOCALIP="192.168.3.37", PEERIP="192.168.2.20", PATHTYPE=ANY;
//Adding an SCTP link for the S1 interface
ADD SCTPLNK: SCTPNO=0, IPVERSION=IPv4, LOCIP="192.168.3.37", LOCPORT=36412,
//Adding a control-plane bearer for the S1 interface
//Adding an S1 interface
ADD S1INTERFACE: S1InterfaceId=0, S1CpBearerId=0, CnOperatorId=0;
//Specifying that the added IP path is used for the S1 interface
ADD ENODEBPATH: IpPathId=0, AppType=S1;

conditions.
//Remove an S1 interface
RMV S1INTERFACE: S1InterfaceId=0;
//Removing the control-plane bearer for the S1 interface
//Removing the SCTP link for the S1 interface

eRAN
//Removing the IP path for the S1 interface



Step 1 Run the DSP S1INTERFACE command to check the S1 interface status.
Expected result:
● If S1Interface state is Normal, the S1 interface status is normal.
● If S1 CP Bearer State is Normal, the SCTP link status is normal.
Step 2 Enable a UE to access a cell to start a service.
Expected result: The service runs properly.
----End

For details about troubleshooting of IP transmission over S1 interfaces, see eRAN
Troubleshooting Guide in 3900 & 5900 Series Base Station Product
Documentation.
There are four S1 reconfiguration scenarios: adding a connection to an MME,
adding a connection to an S-GW, changing an MME IP address, and changing an
S-GW IP address. For details, see eRAN Troubleshooting Guide in 3900 & 5900
Series Base Station Product Documentation.
3.3 Deployment of an X2 Interface
3.3.1 Principles
IPv4 Transmission
For IPv4 transmission, an X2 interface can be set up in either of the following
modes:
● Link configuration mode: The IPPATH, ENODEBPATH, SCTPLNK, CPBEARER,
and X2INTERFACE MOs must be configured.
● Endpoint configuration mode: An X2 interface is automatically set up after the
following data is configured: X2, EPGROUP, SCTPTEMPLATE, SCTPHOST,
SCTPPEER, USERPLANEHOST, and USPERPLANEPEER. Endpoint
configuration mode is recommended.
If an eNodeB is configured with X2 interfaces in link configuration mode, local IP
addresses, local port numbers, peer IP addresses, and peer port numbers of X2-C
and X2-U interfaces must be collected based on operators' network plan.

eRAN
Information, including settings of SCTP negotiation- and detection-related

parameters in SCTPLNK MOs, the homing operators of the X2 interfaces, and the
versions of connected neighboring eNodeBs, must be collected.
For IPv4 transmission, this document describes only X2 interface setup in link
configuration mode. For details about X2 interface setup in endpoint configuration
mode, see S1 and X2 Self-Management.
IPv6 Transmission or IPv4/IPv6 Dual-Stack Transmission

For IPv6 transmission, an X2 interface can be set up only in endpoint mode. To
automatically set up an X2 interface, the following MOs must be configured: X2,
EPGROUP, SCTPTEMPLATE, SCTPHOST, SCTPPEER, USERPLANEHOST, and
USERPLANEPEER.
For how to configure X2 interfaces in endpoint mode for IPv6 transmission, see S1
and X2 Self-Management.
3.3.2.1 Benefits
None
3.3.2.2 Impacts
Network Impacts
The length of a basic IPv6 packet header is 40 bytes, which is longer than that of
a basic IPv4 packet header (20 bytes). Therefore, the transmission efficiency of an
IPv6 network is slightly lower than that of an IPv4 network. For example, the
length of an IPv4 packet is 800 bytes and the length of an IPv6 packet is 820
bytes. The IPv6 transmission efficiency is 2.5% lower than IPv4 transmission
efficiency.
Function Impacts
For details about the impacted features of S1 and X2 over IPv6, see 3.2.2.2
Impacts.
3.3.3 Requirements
3.3.3.1 Licenses
Name
FDD LOFD-003017 S1 and X2 LT1SSXIPV600 per eNodeB

over IPv6

eRAN

Name
FDD MLOFD-0030 S1 over IPv6 ML1SS1IPV60 per eNodeB

17 0
3.3.3.2 Software
None

None
3.3.3.3 Hardware
Base Station Models

No requirements
Boards
The UMDU and UMPT of the eNodeB support this feature.
RF Modules
No requirements
3.3.3.4 Networking
Table 3-3 describes the requirements of the X2 interface for transmission
networking.
Table 3-3 Requirements of the X2 interface for transmission networking
Application Delay Jitter Packet Rerouting (Tolerance) (s)

Scenario (ms) (ms) Loss
Rate
Best 10 4 0.0001% Suggested: 1; maximum: 2
Recommende 20 7 0.001% Suggested: 1; maximum: 2

d
Tolerable 40 10 0.5% Suggested: 1; maximum: 2

eRAN
NOTE
The Delay (ms) values presented in Table 3-3 are one-way delays meeting basic
transmission requirements. If a feature has special delay requirements, the special delay
must be shorter than the one-way delay. For details about any special delay requirements,
see the corresponding feature parameter description.
In Table 3-3, the Best scenario ensures the QoS of all services and the Recommended
scenario ensures the QoS of services with a QCI of 1, 2, 3, or 7. The Tolerable scenario
ensures establishment of services, but does not ensure the QoS of QCI-specific services
whose QoS requirements are beyond the QoS specifications for the corresponding QCI.
During IP address planning for an eNodeB, the O&M channel, X2-C interface, and
X2-U interface can have identical or different IP addresses. The following principles
are used for determining whether IP addresses are identically configured:
1. If the O&M channel, X2-C interface, and X2-U interface are to be isolated by
IP addresses, plan different IP addresses.
2. If the O&M channel, X2-C interface, and X2-U interface are not to be isolated
by IP addresses, use identical IP addresses.
The IP address of an IP clock must be a port IP address (Ethernet port IP address
or Ethernet trunk IP address) if the IP clock link complies with the Huawei
proprietary protocol, and can be a port IP address or a logical IP address
(loopback interface IP address) if the IP clock link complies with the IEEE 1588V2
protocol.
3.3.3.5 Others
None

After deploying the common data, deploy the X2 interface.
Prepare the parameters in an RSCGRP MO used to configure a transmission
resource group for bandwidth management. The transmission resource group
contains IP paths for transmitting X2 user-plane data. For details about
configurations of an RSCGRP MO, see 3.2.4.1.1 Data Preparation (Old Model).
How to configure X2 interfaces in link configuration mode is described as follows:
Prepare the parameters in an IPPATH MO used to configure an IP path for
transmitting X2 user-plane data between eNodeBs. For details about
configurations of an IPPATH MO, see 3.2.4.1.1 Data Preparation (Old Model).
Prepare the parameters in an eNodeBPath MO used to specify that the IP path is
established over an X2 interface. For details about configurations of an
eNodeBPath MO, see 3.2.4.1.1 Data Preparation (Old Model).

eRAN
Prepare the parameters in an SCTPLNK MO used to configure an SCTP link for

transmitting X2 control-plane data between eNodeBs. For details about
configurations of an SCTPLNK MO, see 3.2.4.1.1 Data Preparation (Old Model).
Prepare the parameters in a CPBEARER MO used to configure transport bearers.
For details about configurations of a CPBEARER MO, see 3.2.4.1.1 Data
Preparation (Old Model).
Prepare the parameters in an X2Interface MO used to configure an X2 interface
between base stations.

r Name
X2Interfac X2Interface.X This parameter specifies the X2 interface ID.

e ID 2InterfaceId Set this parameter based on the network plan. The
value of this parameter must be different from that
of the S1Interface.S1InterfaceId parameter.
X2 X2Interface.X This parameter specifies the ID of the CP bearer for

Interface 2CpBearerId the X2 interface. Set this parameter based on the
ID
CN X2Interface.C This parameter specifies the ID of the operator

Operator nOperatorId owning the X2 interface.
the associated CnOperator MO. For details, see
RAN Sharing.
Peer Base X2Interface.T This parameter specifies the 3GPP release which
Station argetENodeB the peer eNodeB connected to the X2 interface
Release Release complies with. Set this parameter based on the
network plan.

After deploying the common data, deploy the X2 interface.
Prepare the parameters in an IPRSCGRP MO used to configure a transport
resource group for bandwidth management. The transport resource group
contains IP paths for transmitting X2 user-plane data. For details about
configurations of an IPRSCGRP MO, see 3.2.4.1.2 Data Preparation (New
Model).
How to configure X2 interfaces in link configuration mode is described as follows:
Prepare the parameters in an IPPATH MO used to configure an IP path for
transmitting X2 user-plane data between eNodeBs. For details about
configurations of an IPPATH MO, see 3.2.4.1.2 Data Preparation (New Model).

eRAN
Prepare the parameters in an eNodeBPath MO used to specify that the IP path is

established over an X2 interface. For details about configurations of an
eNodeBPath MO, see 3.2.4.1.2 Data Preparation (New Model).
Prepare the parameters in an SCTPLNK MO used to configure an SCTP link for

transmitting X2 control-plane data between eNodeBs. For details about
configurations of an SCTPLNK MO, see 3.2.4.1.2 Data Preparation (New Model).
Prepare the parameters in a CPBEARER MO used to configure transport bearers.

For details about configurations of a CPBEARER MO, see 3.2.4.1.2 Data
Prepare the parameters in an X2Interface MO to configure an X2 interface

between eNodeBs. For details, see 3.2.4.1.2 Data Preparation (New Model).

//Adding an IP path for the X2 interface
ADD IPPATH: PATHID=0, CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, JNRSCGRP=ENABLE,
RSCGRPID=0, VRFIDX=0, LOCALIP="192.168.3.37", PEERIP="192.168.2.20", PATHTYPE=ANY;
//Adding an SCTP link for the X2 interface
ADD SCTPLNK: SCTPNO=0, CN=0, SRN=0, SN=6, LOCIP="192.168.3.37", LOCPORT=36412,
//Adding a CP bearer for the X2 interface
//Adding an X2 interface
ADD X2INTERFACE: X2InterfaceId=16, X2CpBearerId=0, CnOperatorId=0;
//Specifying that the added IP path is used for the X2 interface
ADD ENODEBPATH: IpPathId=0, AppType=X2, X2InterfaceId=16;

//Removing an X2 interface
RMV X2INTERFACE: X2InterfaceId=16;
//Removing the control-plane bearer for the X2 interface
//Removing the SCTP link for the X2 interface
//Removing the IP path for the X2 interface

//Adding an IP path for the X2 interface
ADD IPPATH: PATHID=0, TRANSCFGMODE=NEW, JNIPRSCGRP=ENABLE, IPRSCGRPID=0, VRFIDX=0,
LOCALIP="192.168.3.37", PEERIP="192.168.2.20", PATHTYPE=ANY;
//Adding an SCTP link for the X2 interface
ADD SCTPLNK: SCTPNO=0, IPVERSION=IPv4, LOCIP="192.168.3.37", LOCPORT=36412,
//Adding a CP bearer for the X2 interface
//Adding an X2 interface
ADD X2INTERFACE: X2InterfaceId=16, X2CpBearerId=0, CnOperatorId=0;
//Specifying that the added IP path is used for the X2 interface
ADD ENODEBPATH: IpPathId=0, AppType=X2, X2InterfaceId=16;

eRAN

//Removing an X2 interface
RMV X2INTERFACE: X2InterfaceId=16;
//Removing the control-plane bearer for the X2 interface
//Removing the SCTP link for the X2 interface
//Removing the IP path for the X2 interface


Step 1 Run the DSP X2INTERFACE command to check the X2 interface status.
Expected result: If the value of X2Interface state is Normal, the X2 interface
status is normal.
Step 2 Create an X2 interface signaling trace task on the MAE-Access and trigger a
handover for a UE.
Expected result: Signaling messages traced in the handover process are observed.
----End

For details about the reconfiguration of an X2 channel, see eRAN Reconfiguration
Guide in 3900 & 5900 Series Base Station Product Documentation.
3.4 Deployment of an eX2 Interface

The eX2 interface can be set up only using the endpoint configuration mode.
For details about eX2 interface deployment, see eX2 Self-Management.
3.5 Deployment of O&M Channels
3.5.1 Principles
Operators can remotely maintain an eNodeB using the O&M channel. The OMCH
MO must be configured because it defines routine O&M information for operators
to maintain an eNodeB using the O&M channel.
IPv4 Transmission
Operators can configure the OMCH MO in route-binding mode or route-
unbinding mode.

eRAN
● In route-binding mode, users need to bind a route specified by the IPRT (old
model)/IPROUTE4 (new model) MO to an O&M channel. In the OMCH MO,
set OMCH.BRT to YES and set OMCH.RTIDX to the index of the route to be
bound.
● In route-unbinding mode, a route for the O&M channel is specified by adding
an IPRT (old model)/IPROUTE4 (new model) MO and the route does not
need to be bound to the O&M channel.
If there is only one O&M channel, a route can be configured by adding an IPRT
(old model)/IPROUTE4 (new model) MO. Alternatively, the route can be
configured by performing the following operations: adding an IPRT (old model)/
IPROUTE4 (new model) MO, binding the route in the OMCH MO, and entering
the index of the route. In route-binding mode, the route bound to an invalid O&M
channel does not take effect. Therefore, ensure that the route bound to the O&M
channel forwards only the service flows in the O&M channel. Otherwise, when the
O&M channel does not take effect, the route bound to the O&M channel does not
take effect, affecting forwarding of other service flows.
If there are active and standby O&M channels, only one IP address of the MAE-
Access is available for the eNodeB and the routes of the two O&M channels can
be added in route-binding mode. Different routes must be bound to the two
channels. When the active O&M channel takes effect, only the route bound to the
active O&M channel takes effect. When the standby O&M channel takes effect,
only the route bound to the standby O&M channel takes effect.
IPv6 Transmission
In IPv6 transmission scenarios, the OMCH.BEAR parameter in the OMCH MO
must be set to IPV6.
You are advised to plan an independent local IPv6 address (specified by the
OMCH.IP6 parameter) and an IPv6 route for the O&M channel.
The information of the O&M channel, including the O&M channel IP addresses of
the eNodeB and MAE-Access, and the route corresponding to the O&M channel
must be collected based on the operator's network plan.
3.5.2.1 Benefits
None
3.5.2.2 Impacts
Network Impacts
None
Function Impacts
None

eRAN
3.5.3 Requirements
3.5.3.1 Licenses
None
3.5.3.2 Software
None

None
3.5.3.3 Hardware
Base Station Models

● BTS3912E
● BTS3911E
Boards
IPv4 transmission:
IPv6 transmission:
RF Modules
No requirements
3.5.3.4 Networking
The O&M channel can share an IP address with another interface or use a
separate IP address. The routes from the base station to the MAE-Access must be
planned.

eRAN
For IPv6 transmission:

● The transmission bearer network must support IPv6. IPv6 routes must be
planned between the base station and the MAE-Access.
● IPv6 addresses need to be planned on the MAE-Access for IPv6-based
communication between the base station and the MAE-Access. These IPv6
addresses include the IPv6 address of the O&M channel, and IPv6 addresses
of the upper-layer application services, such as IPv6 addresses of the FTP
server and NTP server.
● If some O&M channels of the base station connected to the MAE-Access are
used for both IPv4 and IPv6 transmission, both IPv4 and IPv6 addresses must
be planned on the MAE-Access to manage both IPv4 and IPv6 transmission.
3.5.3.5 Others
For IPv6 transmission, an O&M channel can be set up only if the base station IP
address on the MAE-Access is the same as the local IPv6 address in the OMCH
MO.

O&M channels can be deployed after the common data is configured.
If the MAE-Access serves as an NTP server, a separate route to the NTP server is
not required. If a standalone NTP server is deployed but no route (neither the
default route nor network segment routes) reaches this NTP server, a route to this
NTP server must be configured. The configuration of the route to an FTP server
and an NTP server is the same.
The following table describes the parameters that must be set in an OMCH MO to
configure an O&M channel.

r Name
Standby OMCH.FLAG This parameter specifies whether the O&M channel

Status is an active or standby O&M channel. Set this
parameter to MASTER. If an O&M channel needs
to be configured as a standby channel, the O&M
channel backup feature must be enabled.

eRAN

r Name
Local IP OMCH.IP This parameter specifies the local IP address of the

O&M channel. Set this parameter based on the
network plan.
The local IP address (specified by the IP parameter
in the OMCH MO) of the O&M channel can be
configured using either of the following methods:
1. Set the IP parameter in the OMCH MO. A
DEVIP (old model)/IPADDR4 (new model) MO
does not need to be configured.
2. Set the DEVIP (old model)/IPADDR4 (new
model) MO. Then, associate this parameter with
the IP parameter in the DEVIP (old model)/
IPADDR4 (new model) MO. This method can be
used when the IP address of the O&M channel
must be an interface IP address.
In both configuration methods, ensure that the
route between the local IP address (specified by
the IP parameter in the OMCH MO) of the O&M
channel and the MAE-Access is reachable.
In non-IPsec scenarios, the port where the local IP
address is configured is an Ethernet port. In IPsec
scenarios, the port where the local IP address is
configured is a loopback interface and this IP
address is used for communication inside the IPsec
tunnel.
Local OMCH.MASK This parameter specifies the local subnet mask of

Mask an O&M channel. Set this parameter based on the
network plan.
Peer IP OMCH.PEERI This parameter specifies the peer IP address of the

P O&M channel, that is, the IP address of the MAE-
Access. Set this parameter based on the network
plan.
Peer OMCH.PEER This parameter specifies the subnet mask of the

Mask MASK peer IP address of the O&M channel. Set this
parameter based on the network plan.

eRAN

r Name
Binding OMCH.BRT This parameter specifies whether a route is bound

Route to the O&M channel. Set this parameter based on
the network plan.
● If this parameter is set to YES, the eNodeB
automatically adds a route for the O&M
channel based on the configuration of the O&M
channel.
● If this parameter is set to NO, a route must be
manually added for the O&M channel when the
network segment of the IP address, which is
specified in the DEVIP (old model)/IPADDR4
(new model) MO, is different from and does not
cover that of the peer IP address of the O&M
channel.
Route OMCH.RTIDX This parameter specifies the index of the master

Index route bound to the O&M channel, that is, the index
of the route to the master MAE-Access. Set this
Binding OMCH.BINDS This parameter specifies whether to bind a slave

Secondar ECONDARYR route to the O&M channel. This route is the one to
y Route T the slave MAE-Access. Set this parameter based on
the network plan.
Secondar OMCH.SECO This parameter specifies the index of the slave

y Route NDARYRTIDX route bound to the O&M channel, that is, the index
Index of the route to the slave MAE-Access. Set this
NOTICE
The IP addresses of the local maintenance port and the MAE-Access cannot be in
the same network segment. If they are in the same network segment and the
local maintenance port and the MAE-Access are connected to the same transport
network, the base station deployment will fail.

//Adding an O&M channel from the base station to the MAE-Access
//Configuration mode 1: Setting the IP parameter in the OMCH MO
ADD OMCH: FLAG=MASTER, IP="10.10.25.8", MASK="255.255.255.0", PEERIP="10.25.36.9",
PEERMASK="255.255.255.0", BEAR=IPV4, BRT=YES, RTIDX=0, BINDSECONDARYRT=NO, CHECKTYPE=NONE;
//Configuration mode 2 (old model): Configuring the DEVIP MO and associating the IP parameter in the
OMCH MO with the IP parameter in the DEVIP MO
ADD ETHPORT: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PN=0;
ADD DEVIP: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, IP="10.10.25.8",
MASK="255.255.255.0", VRFIDX=0;

eRAN
//Configuration mode 2 (new model): Configuring the IPADDR4 MO and associating the IP parameter in
the OMCH MO with the IP parameter in the DEVIP MO
ADD ETHPORT: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PN=0, PORTID=0;
ADD INTERFACE: ITFID=0, ITFTYPE=NORMAL, PT=ETH, PORTID=0;
ADD IPADDR4: ITFID=0, IP="10.10.25.8", MASK="255.255.255.0";


Step 1 Run the DSP OMCH command to query the O&M channel status.
Expected result: If the value of OM Channel Status is Normal, the O&M channel
status is normal.
Step 2 Log in to the MAE-Access. Choose Topology > Main Topology to check the
eNodeB topology.
Expected result: The eNodeB topology is normal.
----End

For details about the reconfiguration of an O&M channel, see eRAN
Reconfiguration Guide in 3900 & 5900 Series Base Station Product Documentation.
For details about troubleshooting of IP transmission over O&M channels, see
eRAN Troubleshooting Guide in 3900 & 5900 Series Base Station Product
Documentation.

O&M channels can be deployed after the common data is configured.
Ensure that the IPv6 route of the upper-layer application over the O&M channel is
reachable. For example, if the MAE-Access IP address is used as the NTP server IP
address, separate routes are not required for the NTP server. If a standalone NTP
server is deployed but no route (neither the default route nor network segment
routes) reaches this NTP server, a route to this NTP server must be configured. The
method of configuring a route to applications, such as an FTP server, is the same
as that to an NTP server.
The following table describes the parameters that must be set in an OMCH MO to
configure an O&M channel.

eRAN

r Name
Standby OMCH.FLAG This parameter specifies whether the O&M channel

Status is an active or standby O&M channel. Set this
parameter to MASTER. To set this parameter to
SLAVE, you need to enable O&M channel backup.
Bearer OMCH.BEAR This parameter specifies the bearer type of an

Type O&M channel. If IPv6 transmission is used for the
O&M channel, set this parameter to IPV6.
Local IPv6 OMCH.IP6 This parameter specifies the local IPv6 address of
Address an O&M channel. Set this parameter based on the
network plan.
There are two configuration methods:
1. Set the OMCH.IP6 parameter directly without
the need of configuring the IPADDR6 MO. The
IP address takes effect on the loopback interface
directly. This configuration method must be
used when the main control board backup
function is enabled.
2. Configure an IPADDR6 MO before setting this
parameter. This method can be used when the
IPv6 address of the O&M channel must be an
interface IP address.
In non-IPsec scenarios, the port for which the IPv6
address is configured can be an Ethernet port. In
IPsec scenarios, the port for which the IP address is
configured is a loopback interface and this IPv6
address is used for communication within the IPsec
tunnel.
Peer IPv6 OMCH.PEERI This parameter specifies the peer IPv6 address of
Address P6 an O&M channel. Set this parameter based on the
network plan.
This address can be an MAE-Access address or an
MAE-Access network segment address.
Peer IPv6 OMCH.PEERI This parameter specifies the prefix length of the
Address P6PFXLEN peer IPv6 address of an O&M channel.
Prefix
Length
NOTICE
The IP addresses of the local maintenance port and the MAE-Access cannot be in
the same network segment. If they are in the same network segment and the
local maintenance port and the MAE-Access are connected to the same transport
network, the base station deployment will fail.

eRAN

//Adding an O&M channel from the base station to the MAE-Access
//Configuration mode 1: Setting the IP6 parameter in the OMCH MO

ADD OMCH: FLAG=MASTER, BEAR=IPV6,IP6="2001:db8:100:ad1:200:100:100:10",
PEERIP6="2001:db8:100:ad1:200:100:211:2", PEERIP6PFXLEN=124;
//Configuration method 2: Configuring an IPADDR6 MO and setting the OMCH.IP6 parameter to the same
value as the IP address specified in the IPADDR6 MO (assuming that the interface with ITFID being 0 has
been configured)
//Adding an eNodeB IPv6 address

ADD IPADDR6: IPADDR6ID="LTE", ITFID=0, IPV6="2001:db8:100:ad1:200:100:100:10", PFXLEN=126;
PEERIP6="2001:db8:100:ad1:200:100:211:2", PEERIP6PFXLEN=124;


Step 1 Run the DSP OMCH command to query the O&M channel status.
Expected result: If the value of OM Channel Status is Normal, the O&M channel
status is normal.
Step 2 Log in to the MAE-Access. Choose Topology > Main Topology to check the
eNodeB topology.
Expected result: The eNodeB topology is normal.
----End

For details about the reconfiguration of an O&M channel, see eRAN
Reconfiguration Guide in 3900 & 5900 Series Base Station Product Documentation.
For details about troubleshooting of IP transmission over O&M channels, see
eRAN Troubleshooting Guide in 3900 & 5900 Series Base Station Product
Documentation.
3.6 IP Transmission over eCoordinator Interfaces
3.6.1 Principles
Se, Sg, Sr, Sw (LTE FDD), Su (LTE FDD), M2, and M3 interfaces are eCoordinator
interfaces.
● For details about engineering guidelines for IP transmission over the Sg
interface, see IP BSS Engineering Guide in GBSS Feature Documentation.
● For details about engineering guidelines for IP transmission over the Sr
interface, see IP RAN Engineering Guide in RAN Feature Documentation.

eRAN
● For details about engineering guidelines for IP transmission over the Se and
M2 interfaces, see Interface Self-planning.
● For details about engineering guidelines for IP transmission over the Sw and
Su interfaces for FDD, see Intelligent Wi-Fi Selection based on eCoordinator.
● For details about engineering guidelines for IP transmission over the M3
interface, see eCoordinator Product Documentation.
Enable IP transmission over the eCoordinator interfaces when the eCoordinator is

involved in coordination among GSM, UMTS, and LTE networks or coordination on
LTE networks.
Collect the following information:
● Physical layer data

Configurations, including port and VLAN configurations, of the peer
equipment at the physical layer
● Link layer data
SCTP configurations of the peer equipment
● Transport layer data
IP addresses of peer equipment and next-hop equipment, maximum
transmission unit (MTU), and differentiated services code point (DSCP)
IP transmission over eCoordinator interfaces is supported only in IPv4 transmission

scenarios.
3.6.2.1 Benefits
None
3.6.2.2 Impacts
Network Impacts
None
Function Impacts
None
3.6.3 Requirements
3.6.3.1 Licenses
None

eRAN
3.6.3.2 Software
None

None
3.6.3.3 Hardware
Base Station Models

No requirements
Boards
No requirements
RF Modules
This function does not depend on RF modules.
3.6.3.4 Networking
It is recommended that layer 3 networking with IP over Ethernet be used between
the eCoordinator and eNodeBs.
Bearer network QoS requirements for Se, M2, and M3 interfaces are the same as
those for the S1 interface.
3.6.3.5 Others
The peer eNodeB supports the Se and M2 interfaces. The peer MME supports the
M3 interface.

For details, see ECO6910 Initial Configuration Guide in ECO6910 Product
Documentation.

For details about how to activate this feature, see ECO6910 Initial Configuration
Guide.

eRAN
On the eCoordinator Side

Step 1 Run the DSP SCTPLNK command to check the value of Operation state in the
command output.
Expected result: The value of Operation state is Available.
Step 2 (Optional) Trace the corresponding interface on the eCoordinator LMT.
For LTE:
● Set Trace Type to SCTP and M2AP to enable M2 Interface Trace.

● Set Trace Type to SCTP and M3AP to enable M3 Interface Trace.
● Set Trace Type to SCTP and SCTPAP to enable Se Interface Trace.
For details, see ECO6910 LMT User Guide in ECO6910 Product Documentation.
Expected result: The corresponding interface tracing results show that an ACK
message is returned for SCTP trace and SCTPAP trace.
The following table lists eCoordinator counters related to IP transmission.
Counter ID Counter Name Counter Description
67191612 VS.SCTP.RX.PKGNUM Number of IP packets

received on the SCTP link
67191613 VS.SCTP.TX.PKGNUM Number of IP packets

transmitted on the SCTP
link
----End
On the eNodeB Side

Step 1 Run the DSP ETHPORT command to check the status of the Ethernet port in the
command output.
Step 2 (Optional) Enable Se Interface Trace and M2 Interface Trace on the LMT. If
messages are traced, services are carried over SCTP links. For details, see 3900 &
5900 Series Base Station LMT User Guide in 3900 & 5900 Series Base Station
Product Documentation.
The following table lists eNodeB counters related to IP transmission over the Se
and M2 interfaces.
1542455874 VS.IPPath.TxPkts Number of packets

successfully transmitted
on the IP path

eRAN
1542455877 VS.IPPath.RxPkts Number of packets

successfully received on
the IP path
----End

For details about how to handle alarms, see ECO6910 Alarm Reference in
ECO6910 Product Documentation.

eRAN
Description 4 Engineering Guidelines for Transmission Reliability
4 Engineering Guidelines for Transmission

Reliability
4.1 Ethernet Route Backup for the Base Station
4.1.1 Principles
This function is recommended when a base station is connected to layer 3 routers
that provide active/standby gateways.
If active and standby IPv4 routes are configured, BFD is enabled to detect the link
status between the base station and active and standby gateway routers, and the
BFD status is associated with the base station's route status. In this way, route
switchovers can be triggered when needed. For details about the license
controlling the BFD function, see 5.1.3.1 Licenses.
IPv6 active and standby routes can be switched based on the status of the bound
IPv6 BFD session or the physical port.
4.1.2.1 Benefits
None
4.1.2.2 Impacts
Network Impacts
None
Function Impacts
None

eRAN
4.1.3 Requirements
4.1.3.1 Licenses
None
4.1.3.2 Software
None

None
4.1.3.3 Hardware
Base Station Models

No requirements
Boards
In IPv4 transmission, the UMPT board supports this function.
In IPv6 transmission, the UMPT board supports this function.
RF Modules
4.1.3.4 Networking
One physical port of the base station or two physical ports on the same board
connect, through a layer 2 network, to the router that supports active/standby
gateways.
The base station supports source-based and destination-based routing. For details
about the route policy and application scenarios, see IPv4 Transmission and IPv6
Transmission.
If active and standby IPv4 routes are configured, BFD is enabled to detect the link
status between the base station and active and standby gateway routers, and the
BFD status is associated with the base station's route status. In this way, route
switchovers can be triggered when needed.
IPv6 active and standby routes can be switched based on the status of the bound
IPv6 BFD session or the physical port.
The active and standby IP routes can be configured only on the same board.

eRAN
4.1.3.5 Others
A standby route to the base station is configured on both the active and standby
gateways. Even if the active route is faulty, the gateway router can send packets to
the base station through the standby route.
4.1.4.1 Data Configuration (IPv4)

Table 4-1 Data to be prepared for Ethernet route backup for the eNodeB and co-
MPT base station
r Name
Next Hop IPROUTE4.NE Set this parameter to the IP address of the active/
IP XTHOP standby gateway.
Preferenc IPROUTE4.PR The active gateway takes precedence over the

e EF standby gatewaya.
a: A smaller value of this parameter indicates a higher route priority.
For the data to be prepared for the BFD function, see 5.1.4.1.2 Data Preparation
(New Model).

When the GTRANSPARA.TRANSCFGMODE parameter is set to OLD, run the
following commands:
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PA=FIBER, MTU=1500, SPEED=1000M,
DUPLEX=FULL, ARPPROXY=ENABLE, FC=OPEN, FERAT=10,
FERDT=10,RXBCPKTALMOCRTHD=322,RXBCPKTALMCLRTHD=290;
//Adding interface IP addresses
VRFIDX=0;
VRFIDX=0;
//Adding loopback IP addresses
ADD DEVIP: CN=0,SRN=0,SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=0, IP="192.168.126.1",
MASK="255.255.255.0", VRFIDX=0;
ADD DEVIP: CN=0,SRN=0,SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=1, IP="192.168.127.1",
MASK="255.255.255.0", VRFIDX=0;
//Adding mapping relationships between next-hop IP addresses and VLAN IDs

eRAN
//Activating Ethernet route backup for the eNodeB and co-MPT base station
//For a single-hop BFD session, when the destination IP address is the next-hop IP address, source and
destination IP addresses are in different network segments if the source port is of the LOOPINT type, but
must be in the same network segment if the source port is of the ETH or ETHTRK type.
ADD BFDSESSION: SN=7, CN=0, SRN=0, BFDSN=0, SRCIP="192.168.126.1", DSTIP="10.10.12.2",
HT=SINGLE_HOP, CATLOG=RELIABILITY, DSCP=48, VER=STANDARD, BFDAUTHSW=OFF;
ADD BFDSESSION: SN=7, CN=0, SRN=0, BFDSN=1, SRCIP="192.168.127.1", DSTIP="10.10.13.2",
HT=SINGLE_HOP, CATLOG=RELIABILITY, DSCP=48, VER=STANDARD, BFDAUTHSW=OFF;
//Changing the route switchback time to 300s
SET GTRANSPARA: SBTIME=300;
NOTE
Set Protocol Version to the BFD session protocol version supported by the peer device.
If this function involves the S1/X2/eX2 interface of the service type, you need to change the
local and peer IP addresses of the corresponding interface. For details, see S1 and X2 Self-
Management and eX2 Self-Management.

When the GTRANSPARA.TRANSCFGMODE parameter is set to OLD, run the
following commands:
//Deactivating Ethernet route backup for the base station
RMV BFDSESSION: CN=0, SRN=0, SN=7, BFDSN=0;
RMV IPRT: RTIDX=0;
RMV IPRT: RTIDX=1;
RMV DEVIP: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=0, IP="192.168.126.1", VRFIDX=0;
RMV DEVIP: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=1, IP="192.168.127.1", VRFIDX=0;
RMV DEVIP: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="10.10.12.1", VRFIDX=0;
RMV DEVIP: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="10.10.13.1", VRFIDX=0;
RMV VLANMAP: NEXTHOPIP="10.10.12.2", MASK="255.255.255.0", VRFIDX=0;
RMV VLANMAP: NEXTHOPIP="10.10.13.2", MASK="255.255.255.0", VRFIDX=0;
RMV ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0;

When the GTRANSPARA.TRANSCFGMODE parameter is set to NEW, run the
following commands:
//Configuring VLANs
ARPPROXY=ENABLE;
ARPPROXY=ENABLE;
//(Optional) Adding loopback IP addresses
ADD INTERFACE: ITFID=3, ITFTYPE=NORMAL, PT=LOOPINT, PORTID=0, VRFIDX=0;

eRAN

//Activating Ethernet route backup for the eNodeB and co-MPT base station
NEXTHOP="10.10.12.2", PREF=60;
NEXTHOP="10.10.13.2", PREF=80;
//For a single-hop BFD session, when the destination IP address is the next-hop IP address, the source and
destination IP addresses are in different network segments if the source port is of the LOOPINT type, but
must be in the same network segment if the source port is of the ETH or ETHTRK type.
ADD BFD: BFDSN=100, IPVERSION=IPV4, SRCIP="192.168.126.1", DSTIP="10.10.12.2",
MYDISCREAMINATOR=1, HT=SINGLE_HOP, CATLOG=RELIABILITY, DSCP=48, VER=STANDARD,
BFDAUTHSW=OFF;
BFDAUTHSW=OFF;
//Changing the route switchover time to 300s
NOTE
Set Protocol Version to the BFD session protocol version supported by the peer device.
If this function involves the S1/X2/eX2 interface of the service type, the local and peer IP
addresses of the corresponding interface need to be changed. For details, see S1 and X2
Self-Management and eX2 Self-Management.

When the GTRANSPARA.TRANSCFGMODE parameter is set to NEW, run the
following commands:
//Deactivating Ethernet route backup for the base station
RMV BFD: BFDSN=100;
RMV BFD: BFDSN=101;
RMV IPROUTE4: RTIDX=0;
RMV IPADDR4: ITFID=3, IP="192.168.126.1";
RMV IPADDR4: ITFID=1, IP="10.10.13.1"";
RMV INTERFACE: ITFID=3;
RMV LOOPBACK: PORTID=0;


Table 4-2 Data to be prepared for Ethernet route backup for the eNodeB and co-
MPT base station

r Name
Next Hop IPRT.NEXTH Set this parameter to the IP address of the active/
IP OP standby gateway.

eRAN

r Name
Preferenc IPRT.PREF The active gateway takes precedence over the

e standby gatewaya.
For the data to be prepared for the BFD function, see 5.1.4.1.1 Data Preparation
(Old Model).

The following table lists the data to be prepared for the Ethernet route backup for
the base station.
● If the active and standby IP routes adopt destination-based IP routing,

configure destination-based IPv6 routing.
The following table describes the parameters that must be set in an IPROUTE6
MO to configure a destination IPv6 route.

r Name
Route IPROUTE6.RT Set this parameter based on the network plan.

Index IDX
Destinatio IPROUTE6.DS The default route is not recommended. In the
n IPv6 TIP default route, the destination IPv6 address is 0::0
Address and the prefix length is 0.
If the local eNodeB resides in the same network
segment as the core network equipment or peer
eNodeB/gNodeB, a network segment route is
recommended, with the destination IPv6 address
being the network segment address and the prefix
length being less than 128.
Prefix IPROUTE6.PF Set this parameter based on the network plan.

Length XLEN
Route IPROUTE6.RT Set this parameter to NEXTHOP.
Type TYPE
Next-Hop IPROUTE6.NE Set this parameter to the IP address of the active
IPv6 XTHOP or standby gateway connected to the base station.
Address
Preferenc IPROUTE6.PR The active gateway takes precedence over the

e EF standby gatewaya.

eRAN

r Name
● If the active and standby IP routes adopt source-based IP routing, configure

source-based IPv6 routing.
The following table describes the parameters that must be set in an
SRCIPROUTE6 MO to configure source-based IPv6 routing.

r Name
IPv6 SRCIPROUTE Set this parameter based on the network plan.

Source 6.SRCRTIDX
Route
Index
Source SRCIPROUTE Set this parameter based on the network plan.

IPv6 6.SRCIP
Address
Route SRCIPROUTE Set this parameter to NEXTHOP.

Type 6.RTTYPE
Next-Hop SRCIPROUTE Set this parameter to the IP address of the active

IPv6 6.NEXTHOP or standby gateway connected to the base station.
Address
Preferenc SRCIPROUTE The active gateway takes precedence over the

e 6.PREF standby gatewaya.

SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=1, PA=FIBER, SPEED=1000M,
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=1, PORTID=2, PA=FIBER, SPEED=1000M,
//Configuring VLANs
ADD INTERFACE: ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=1, VLANID=10, VRFIDX=0, MTU6=1500;
ADD INTERFACE: ITFID=1, ITFTYPE=VLAN, PT=ETH, PORTID=2, VLANID=20, VRFIDX=0, MTU6=1500;
ADD IPADDR6: IPADDR6ID="RT1", ITFID=0, IPV6="2001:db8:100:ad1:200:100:100:10", PFXLEN=126;
ADD IPADDR6: IPADDR6ID="RT2", ITFID=1, IPV6="2001:db8:100:ad1:200:100:200:10", PFXLEN=126;
//(Optional) Adding a loopback IP address
ADD INTERFACE: ITFID=10, ITFTYPE=NORMAL, PT=LOOPINT, PORTID=8, VRFIDX=0, IPV6SW=ENABLE;
ADD IPADDR6: IPADDR6ID="LOOPBACK", ITFID=10, IPV6="2001:db8:100:ad1:200:100:200:100",
PFXLEN=128;

eRAN
//Activating Ethernet route backup for the base station

//Operations when the active and standby IP routes adopt destination-based IP routing
//On the base station, if BFD hop type is single-hop and the source IP address is the IP address of an
Ethernet port or Ethernet trunk, the source and destination IP addresses must be on the same network
segment.
ADD BFD: BFDSN=100, IPVERSION=IPV6, SRCIPV6="2001:db8:100:ad1:200:100:100:12",
DSTIPV6="2001:db8:100:ad1:200:100:100:1", MYDISCREAMINATOR=1, HT=SINGLE_HOP,
DSTIPV6="2001:db8:100:ad1:200:100:200:1", MYDISCREAMINATOR=1, HT=SINGLE_HOP,
//Operations when the active and standby IP routes adopt source-based IP routing
ADD SRCIPROUTE6: SRCRTIDX=0, SRCIP="2001:db8:100:ad1:200:100:200:100", RTTYPE=NEXTHOP,
NOTE
If this function involves the S1/X2/eX2 interface of the service type, the local and peer IP
addresses of the corresponding interface need to be changed. For details, see S1 and X2
Self-Management and eX2 Self-Management.

//Removing the active and standby routes as well as the BFD session for the base station
//Operations when the active and standby IP routes adopt destination-based IP routing
RMV BFD: BFDSN=100;
RMV BFD: BFDSN=100;
//Operations when the active and standby IP routes adopt source-based IP routing
RMV SRCIPROUTE6: SRCRTIDX=0;
RMV SRCIPROUTE6: SRCRTIDX=1;
RMV IPADDR6: IPADDR6ID="RT1";
RMV IPADDR6: IPADDR6ID="RT2";
RMV IPADDR6: IPADDR6ID="LOOPBACK";
RMV LOOPBACK: PORTID=8;

4.1.4.3 Activation Verification (IPv4)

This section describes activation verification of Ethernet route backup for the
eNodeB and co-MPT base station.
IP route backup is flexible to implement and verify. For two IP routes with the
same destination IP address but different priorities and next-hop IP addresses,
data is transmitted on the IP route with a higher priority if both of the IP routes

eRAN
are functional. When the IP route with a higher priority becomes faulty, the other
IP route takes over to perform data transmission.
Before the verification, ensure that both the active and standby IP routes are
functional. You can run the DSP IPRT (old model)/IPROUTE4 (new model)
command to check whether both the active and standby IP routes are in the
routing table. If both are in the routing table, perform the following steps:
Step 1 Run the TRACERT command to check the active route. In the command output,
the route with the first-hop IP address being the next-hop IP address is the active
route.
Step 2 Trigger a fault in the active route, and run the DSP IPRT (old model)/DSP
IPROUTE4 (new model) command to check that the value of Valid State of IP
Route of the active route is Invalid.
Step 3 Ensure that route switchover is completed. Specifically, run the TRACERT
command. The switchover is successful if the first hop IP address is the next hop IP
address of the standby IP route.
Step 4 Restore the higher-priority link in the IPRT (old model)/IPROUTE4 (new model)
MO.
----End
4.1.4.4 Activation Verification (IPv6)

This section describes activation observation of Ethernet route backup for the base
station.
The verification method is to trigger a route fault and check whether services can
be switched to the other route. If the two IP routes are both functional, data is
transmitted on the IP route with the higher priority.
Ensure that the active and standby IP routes are normal before verifying the IP
route backup function. You can run the DSP IPROUTE6 command (when active
and standby IP routes adopt destination-based IP routing) or the SRCIPROUTE6
command (when active and standby IP routes adopt source-based IP routing) to
check whether both the active and standby IP routes are in the current routing
and forwarding table. If both are in the table, perform the following steps:
Step 1 Check the active route. Run the TRACERT6 command to check the active route. In
the command output, the route with the first-hop IP address being the next-hop
IP address is the active route.
Step 2 Trigger a fault in the active route, Run the DSP IPROUTE6 command (when active
and standby IP routes adopt destination-based IP routing) or the DSP
SRCIPROUTE6 command (when active and standby IP routes adopt source-based
IP routing) to check the route status. In the command output, Route Status of the
active route is Invalid.
Step 3 Verify the switchover. Run the TRACERT6 command. The switchover is successful if
the first hop IP address is the next hop IP address of the standby IP route.
Step 4 Restore the transmission link with a higher priority specified in the IPROUTE6
(when active and standby IP routes adopt destination-based IP routing)/

eRAN
SRCIPROUTE6 (when active and standby IP routes adopt source-based IP routing)

MO on the base station.
----End
4.1.4.5 Network Monitoring (IPv4)

Run the DSP IPRT (old model)/DSP IPROUTE4 (new model) command to check
whether the routes take effect.
Run the MOD IPRT (old model)/MOD IPROUTE4 (new model) command.
4.1.4.6 Network Monitoring (IPv6)

Run the DSP IPROUTE6 (when the active and standby IP routes adopt
destination-based IP routing)/DSP SRCIPROUTE6 (when the active and standby IP
routes adopt source-based IP routing) command to check whether the routes take
effect.
Run the MOD IPROUTE6 (when the active and standby IP routes adopt
destination-based IP routing)/MOD SRCIPROUTE6 (when the active and standby
IP routes adopt source-based IP routing) command to modify the route.
4.2 Link Aggregation (Layer 2 or Layer 3 Networking

Between the Base Station and Transmission
Equipment)
4.2.1 Principles
Enable link aggregation when layer 2 or layer 3 networking is used between the
base station and transmission equipment that supports link aggregation group.
Link aggregation is supported in IPv4 and IPv6 transmission scenarios.
4.2.2.1 Benefits
None
4.2.2.2 Impacts
Network Impacts
Under different TRANSFUNCTIONSW.ETHTRKLBMODE parameter settings, the
volume of traffic transmitted to the bearer network varies between each member
port in an Ethernet trunk.

eRAN
Function Impacts
None
4.2.3 Requirements
4.2.3.1 Licenses
No license is required for the eGBTS and NodeB.
The operator must have purchased and activated the licenses for the features
listed in the following table if the features are to be deployed for the eNodeB.
Feature ID Feature Model License NE Sales Unit

Name Control Item
LOFD-00300 Ethernet LT1S000E Ethernet Link eNodeB per eNodeB

8 Link LA00 Aggregation
Aggregat (IEEE 802.3ad)
ion (IEEE
802.3ad)
MLOFD-003 Ethernet ML1S000E Ethernet Link eNodeB per eNodeB

008 Link LA00 Aggregation
Aggregat (IEEE 802.3ad)
ion (IEEE (NB-IoT)
802.3ad)
4.2.3.2 Software
None

None
4.2.3.3 Hardware
Base Station Models

3900 and 5900 series base stations
Boards
Only the UMPT boards of the 3900 and 5900 series base stations support this
function.

eRAN
RF Modules
4.2.3.4 Networking
The base station provides multiple FE/GE/10GE/25GE ports. These ports are all FE
ports or all GE/10GE/25GE ports, and all electrical ports or all optical ports.
The ports on a board of the base station can form a static link aggregation group
and work in load sharing mode.
4.2.3.5 Others
The base station must be directly connected to layer-2 or layer-3 transmission
equipment that supports link aggregation.
Table 4-3 Data to be prepared for link aggregation

r Name
ETH TRANSFUNC Set this parameter to LB_MODE_1(Load Balancing

Trunk TIONSW.ETH Mode 1).
Load TRKLBMODE
Balancing
Mode
Trunk ETHTRK.LAC Set this parameter to ENABLE.

Type P
Table 4-4 Data required for activating link aggregation

r Name
ETH TRANSFUNC Set this parameter to LB_MODE_1(Load Balancing

Trunk TIONSW.ETH Mode 1).
Load TRKLBMODE
Balancing
Mode

eRAN

r Name
Trunk ETHTRUNK.L Set this parameter to ENABLE.

Type ACP

//Adding a link aggregation group
SET TRANSFUNCTIONSW: ETHTRKLBMODE=LB_MODE_1;
ADD ETHTRK: CN=0, SRN=0, SN=5, SBT=ETH_COVERBOARD, TN=0, LACP=ENABLE;
ADD ETHTRKLNK: CN=0, SRN=0, SN=5, SBT=ETH_COVERBOARD, TN=0, PN=0, FLAG=YES;
ADD ETHTRKLNK: CN=0, SRN=0, SN=5, SBT=ETH_COVERBOARD, TN=0, PN=1, FLAG=NO;
ADD DEVIP: CN=0, SRN=0, SN=5, SBT=ETH_COVERBOARD, PT=ETHTRK, PN=0, IP="192.168.126.1",
MASK="255.255.255.0", VRFIDX=0;

//Removing a link aggregation group
RMV DEVIP: CN=0, SRN=0, SN=5, SBT=ETH_COVERBOARD, PT=ETHTRK, PN=0, IP="192.168.126.1",
VRFIDX=0;
RMV ETHTRKLNK: CN=0, SRN=0, SN=5, SBT=ETH_COVERBOARD, TN=0, PN=1;
RMV ETHTRKLNK: CN=0, SRN=0, SN=5, SBT=ETH_COVERBOARD, TN=0, PN=0;
RMV ETHTRK: CN=0, SRN=0, SN=5, SBT=ETH_COVERBOARD, TN=0;

//Adding a link aggregation group
SET TRANSFUNCTIONSW: ETHTRKLBMODE=LB_MODE_1;
ADD ETHTRUNK: PORTID=0, LACP=ENABLE;
ADD ETHTRUNKLNK: ETHTRKPORTID=0, ETHTRUNKLNKID=0, ETHPORTID=0, FLAG=YES;
ADD ETHTRUNKLNK: ETHTRKPORTID=0, ETHTRUNKLNKID=1, ETHPORTID=1, FLAG=NO;
//Adding an interface (IPv4)
ADD INTERFACE: ITFID=0, ITFTYPE=VLAN, PT=ETHTRK, PORTID=0, VLANID=100, VRFIDX=0, MTU4=1500,
ARPPROXY=ENABLE;
ADD IPADDR4: ITFID=0, IP="192.168.126.1", MASK="255.255.255.0";
//Adding an interface (IPv6)
ADD INTERFACE: ITFID=1, ITFTYPE=VLAN, PT=ETHTRK, PORTID=0, VLANID=200, VRFIDX=0, MTU6=1500,
IPV6SW=ENABLE;
ADD IPADDR6: IPADDR6ID="0", ITFID=1, IPV6="2001:DB8::1", PFXLEN=32;

//Removing a link aggregation group
//IPv4 scenario
//IPv6 scenario
RMV IPADDR6: IPADDR6ID="0";
RMV ETHTRUNKLNK: ETHTRKPORTID=0, ETHTRUNKLNKID=1;
RMV ETHTRUNKLNK: ETHTRKPORTID=0, ETHTRUNKLNKID=0;
RMV ETHTRUNK: PORTID=0;


eRAN
4.2.4.2 Activation Verification (Old Model)

Step 1 Run the DSP ETHTRK command to query the status of an Ethernet trunk. If
Ethernet Trunk Status is Up and Number of Active Trunk Ports is not 0, the
Ethernet link aggregation function is normal and there are active ports in the
trunk.
Step 2 Remove the fiber or Ethernet cable from the active ports and run the DSP
ETHTRK command again. The ports from which the fiber or Ethernet cable is
removed are not displayed after Active Trunk Port No. in the result. The S1
interface configured on the Ethernet link is functional. Run the DSP ETHTRKLNK
command to query the status of this port. Port Status is Down.
Step 3 Reconnect the optical fiber or Ethernet cable to the port.
Step 4 Run the DSP ETHTRK and DSP ETHTRKLNK commands. The command outputs
show that the port to which the optical fiber or Ethernet cable is reconnected
becomes active.
----End
4.2.4.3 Activation Verification (New Model)

Step 1 Run the DSP ETHTRUNK command to query the status of an Ethernet trunk. If
Ethernet Trunk Status is Up and Number of Active Trunk Ports is not 0, the
Ethernet link aggregation function is normal and there are active ports in the
trunk.
Step 2 Remove the fiber or Ethernet cable from the active ports and run the DSP
ETHTRUNK command again. The ports from which the fiber or Ethernet cable is
removed are not displayed after Active Trunk Port No. in the result. The S1
interface configured on the Ethernet link is functional. Run the DSP
ETHTRUNKLNK command to check the status of the port from which the cable
has been removed. The command output shows that the value of Port Status is
Down.
Step 3 Reconnect the optical fiber or Ethernet cable to the port.
Step 4 Run the DSP ETHTRUNK and DSP ETHTRUNKLNK commands. The command
outputs show that the port to which the optical fiber or Ethernet cable is
reconnected becomes active.
----End

Old model:
Run the DSP ETHTRK command to check whether the link aggregation group is
functional.
Run the DSP ETHTRKLNK command to check whether links in the link
aggregation group are functional.
New model:
Run the DSP ETHTRUNK command to check whether the Ethernet aggregation
group is functional.

eRAN
Run the DSP ETHTRUNKLNK command to check the statuses of ports in the
Ethernet aggregation group.
If the following alarms are reported, clear them by referring to the alarm handling
suggestions:
● ALM-25895 Ethernet Trunk Group Fault

● ALM-25887 Ethernet Trunk Link Fault
If the attributes of a port in a link aggregation group become different from those
of other ports in the link aggregation group, remove the port from the link
aggregation group.
4.3 O&M Channel Backup
4.3.1 Principles
The eNodeB and co-MPT base station support O&M channel backup.
Enable O&M channel backup on the base station side when hybrid transmission is
used for high-QoS and low-QoS links, secure and non-secure links, and multi-RAT
services of a co-MPT multimode base station.
4.3.2.1 Benefits
None
4.3.2.2 Impacts
Network Impacts
None
Function Impacts
None
4.3.3 Requirements
4.3.3.1 Licenses
No license is required for the eGBTS and NodeB.

eRAN
Feature ID Feature Model License Sales Unit

Name Control Item
LOFD-003005 OM Channel LT1S00OMCB OM Channel per eNodeB

Backup 00 Backup
MLOFD-0030 OM Channel ML1S00OMC OM Channel per eNodeB

05 Backup B00 Backup
4.3.3.2 Software
None

Function Function Switch Reference Description
Name
Source- None IPv6 The O&M channel in

based IP Transmission route-binding mode
routing does not support
source-based routing.
4.3.3.3 Hardware
Base Station Models

Boards
In IPv4 transmission mode, only the UMPT boards of the 3900 and 5900 series
base stations support O&M channel backup.
In IPv6 transmission mode, only the UMPT boards of the 3900 and 5900 series
base stations support O&M channel backup.
RF Modules
4.3.3.4 Networking
Two IP addresses for the two O&M channels must be planned on the base station
side for different transmission links.

eRAN
The O&M channel in IPv6 route-binding mode does not support IPv6-over-IPv4
IPsec. In IPv6-over-IPv4 IPsec, IPv6 is in the inner IP header and IPv4 is in the outer
IP header. For details about IPv6-over-IPv4 IPsec, see IPsec.
4.3.3.5 Others
The MAE-Access must be configured with the IP addresses of the active and
standby O&M channels and the bound routes.

Table 4-5 lists the parameters that need to be set if O&M channel switchback is
not required.
Table 4-5 Data to prepare for O&M channel backup

r Name
Standby OMCH.FLAG Set this parameter to MASTER for the active O&M
Status channel and to SLAVE for the standby O&M
channel.
Local IP OMCH.IP Set this parameter to the local IP address of the

active O&M channel for the active O&M channel
and to the local IP address of the standby O&M
channel for the standby O&M channel.
Local OMCH.MASK Set this parameter to the local subnet mask.

Mask
Peer IP OMCH.PEERI Set this parameter to the MAE-Access address.

P
Peer OMCH.PEER Set this parameter to the peer subnet mask.
Mask MASK
Binding OMCH.BRT Set this parameter to YES.
Route
Route OMCH.RTIDX Set this parameter to the index of the route bound
Index to the active MAE-Access.
Binding OMCH.BINDS Set this parameter to YES if the MAE-Access uses

Secondar ECONDARYR the remote HA system and the IP address of the
y Route T standby MAE-Access is beyond the network
segment range of the route bound to the O&M
channel. Otherwise, set this parameter to NO.

eRAN

r Name
Secondar OMCH.SECO Set this parameter to the index of the route to the
y Route NDARYRTIDX standby MAE-Access. This parameter is valid only
Index when Binding Secondary Route is set to YES.
The following tables list the parameters that need to be set if O&M channel
switchback is required.
Data preparation for O&M channel switchback is required. The following table lists
the parameters that must be set in a GTRANSPARA MO to set NE global
transmission parameters.

r Name
OMCH GTRANSPAR If O&M channel switchback is required, set this

Switch A.OMCHSWI parameter to ENABLE.
Back TCHBACK
OMCH GTRANSPAR This parameter specifies the wait time for
Switch A.OMCHSBW switching from the standby remote maintenance
Back Wait AITTIME channel to the active remote maintenance channel.
Time Set this parameter to the default value (60s).
Data preparation for O&M channel backup is required. The following table lists
the parameters that must be set in an OMCH MO to configure an O&M channel.

r Name
Standby OMCH.FLAG Set this parameter to MASTER for the active O&M
Status channel and to SLAVE for the standby O&M
channel.
Local IP OMCH.IP Set this parameter to the local IP address of the


Mask
Peer IP OMCH.PEERI Set this parameter to the MAE-Access address.

P
Peer OMCH.PEER Set this parameter to the peer subnet mask.
Mask MASK

eRAN

r Name
Check OMCH.CHEC This parameter can be set to AUTO_UDPSESSION

Type KTYPE for only the active O&M channel.
If this parameter is set to AUTO_UDPSESSION for
the active O&M channel, this parameter must be
set to NONE for the standby O&M channel.
The following table lists the data to prepare if the

GTRANSPARA.TRANSCFGMODE parameter is set to OLD.
Data preparation of source IP routes is required for O&M channel backup. The
following table lists the parameters that must be set in an SRCIPRT MO to
configure a source IP route.

r Name
Source SRCIPRT.SRC This parameter specifies the index of an IP route.

Route RTIDX Set this parameter based on the network plan.
Index
Source IP SRCIPRT.SRCI This parameter specifies the source IP address of a

Address P source IP route.
If O&M channel backup is used, set this parameter
to the local IP address of the O&M channel.
Subboard SRCIPRT.SBT This parameter specifies the type of the sub-board

BASE_BOARD.
Route SRCIPRT.RTT This parameter specifies the route type. In Ethernet

Type YPE networking scenarios, set this parameter to
NEXTHOP.
Next Hop SRCIPRT.NEX This parameter specifies the next-hop IP address.

IP THOP ● This parameter is valid when the IPRT.RTTYPE
parameter is set to NEXTHOP.
plan.
The following table lists the data to prepare if the

GTRANSPARA.TRANSCFGMODE parameter is set to NEW.
Data preparation of source IP routes is required for O&M channel backup. The
following table lists the parameters that must be set in an SRCIPROUTE4 MO to
configure a source IP route.

eRAN

r Name
Source SRCIPROUTE This parameter specifies the index of a source IPv4

Route 4.SRCRTIDX route. Set this parameter based on the network
Index plan.
Source IP SRCIPROUTE This parameter specifies the source IPv4 address of

Address 4.SRCIP a source IPv4 route.
If O&M channel backup is used, set this parameter
to the local IP address of the O&M channel.

Type 4.RTTYPE route. In Ethernet networking scenarios, set this
parameter to NEXTHOP.
Next Hop SRCIPROUTE This parameter specifies the next hop IP address of
IP 4.NEXTHOP a source IPv4 route.
● This parameter is valid when the IPRT.RTTYPE
parameter is set to NEXTHOP.
plan.

//If O&M channel switchback is not required
//Configuring active and standby O&M channels when the MAE-Access does not use the remote HA system
RTTYPE=NEXTHOP, NEXTHOP="10.10.12.2";
ADD OMCH: FLAG=SLAVE, IP="10.10.11.1", MASK="255.255.255.255", PEERIP="100.100.100.1",
//Configuring active and standby O&M channels when the MAE-Access uses the remote HA system
PEERMASK="255.255.255.0", BEAR=IPV4, BRT=YES, RTIDX=0, BINDSECONDARYRT=YES,
SECONDARYRTIDX=2, CHECKTYPE=NONE;
//If O&M channel switchback is required


eRAN
SET GTRANSPARA: OMCHSWITCHBACK=ENABLE, OMCHSBWAITTIME=60;

NEXTHOP="10.10.12.2";
NEXTHOP="10.10.13.2";
PEERMASK="255.255.255.0", BEAR=IPV4, CHECKTYPE=AUTO_UDPSESSION;
PEERMASK="255.255.255.0", BEAR=IPV4, CHECKTYPE=NONE;
Optimization Command Examples

//Changing the O&M channel binding mode to O&M channel switchback
//This adjustment may interrupt the O&M channel. You are advised to run the CFM CB command to enable
automatic configuration data rollback before data reconstruction.
CFM CB:MODE=UNFORCED,NAME="CB1",COMMENT="omch back
",AUTORBKSW=ENABLE,RBKTIME=60,RBKCONDITION=OMCH_FAULT;
//Turning on the O&M channel switchback switch

//Adding source IP routes used by the active and standby O&M channels
NEXTHOP="10.10.12.2";
NEXTHOP="10.10.13.2";
//Setting Check Type of the active O&M channel to AUTO_UDPSESSION, Check Type of the standby O&M
channel to NONE, and Binding Route to NO
MOD OMCH: FLAG=MASTER, IP="10.10.10.1", MASK="255.255.255.255", PEERIP="100.100.100.1",
PEERMASK="255.255.255.0", BEAR=IPV4, BRT=NO, CHECKTYPE=AUTO_UDPSESSION;
MOD OMCH: FLAG=SLAVE, IP="10.10.11.1", MASK="255.255.255.255", PEERIP="100.100.100.1",
PEERMASK="255.255.255.0", BEAR=IPV4, BRT=NO, CHECKTYPE=NONE;
//Disabling automatic data configuration rollback

MOD CB: NAME="CB1", AUTORBKSW=DISABLE;

//Removing the standby O&M channel
RMV OMCH: FLAG=SLAVE;
//Disabling O&M channel switchback (if configured)

SET GTRANSPARA: OMCHSWITCHBACK=DISABLE;

//If O&M channel switchback is not required
NEXTHOP="10.10.12.2";
NEXTHOP="10.10.13.2";
//Configuring active and standby O&M channels when the MAE-Access uses the remote HA system
NEXTHOP="10.10.12.2";
NEXTHOP="10.10.13.2";
NEXTHOP="10.10.12.2";

eRAN

NEXTHOP="10.10.13.2";
//If O&M channel switchback is required

//Activating O&M channel backup if the MAE-Access does not use the remote HA system
ADD SRCIPROUTE4: SRCRTIDX=0, SRCIP="10.10.10.1", RTTYPE=NEXTHOP, NEXTHOP="10.10.12.2";
PEERMASK="255.255.255.0", BEAR=IPV4, CHECKTYPE= AUTO_UDPSESSION;
PEERMASK="255.255.255.0", BEAR=IPV4, CHECKTYPE=NONE;

//Changing the O&M channel binding mode to O&M channel switchback
//This adjustment may interrupt the O&M channel. You are advised to run the CFM CB command to enable
automatic configuration data rollback before data reconstruction.
CFM CB:MODE=UNFORCED,NAME="CB1",COMMENT="omch back
",AUTORBKSW=ENABLE,RBKTIME=60,RBKCONDITION=OMCH_FAULT;
//Turning on the O&M channel switchback switch

//Adding source IP routes used by the active and standby O&M channels
//Setting Check Type of the active O&M channel to AUTO_UDPSESSION, Check Type of the standby O&M
channel to NONE, and Binding Route to NO
MOD OMCH: FLAG=MASTER, IP="10.10.10.1", MASK="255.255.255.255", PEERIP="100.100.100.1",
PEERMASK="255.255.255.0", BEAR=IPV4, BRT=NO, CHECKTYPE=AUTO_UDPSESSION;
MOD OMCH: FLAG=SLAVE, IP="10.10.11.1", MASK="255.255.255.255", PEERIP="100.100.100.1",
PEERMASK="255.255.255.0", BEAR=IPV4, BRT=NO, CHECKTYPE=NONE;
//Disabling the automatic data configuration rollback function

MOD CB: NAME="CB1", AUTORBKSW=DISABLE;

//Removing the standby O&M channel
//Disabling O&M channel switchback (if configured)

SET GTRANSPARA: OMCHSWITCHBACK=DISABLE;


Table 4-6 describes the parameter configurations when O&M channel switchback
is not required.

eRAN
Table 4-6 Data to prepare for O&M channel backup

r Name
Standby OMCH.FLAG Set this parameter to MASTER for an active O&M

Status channel and to SLAVE for a standby O&M channel.
Bearer OMCH.BEAR If two IPv6 O&M channels work in active/standby

Type mode, set this parameter to IPV6 for both the
active and standby O&M channels.
If a single IPv4 O&M channel and a single IPv6
O&M channel work in active/standby mode, set
this parameter to IPV6 and IPV4 for the active and
standby O&M channels, respectively.
Local IPv6 OMCH.IP6 When the BEAR parameter is set to IPV6, the IP6
Address parameter must be configured.
Set this parameter to the local IP address of the
The base station O&M IPv6 address configured on
the MAE-Access topology view must be the same
as this local IPv6 address.
Peer IPv6 OMCH.PEERI When the BEAR parameter is set to IPV6, the
Address P6 PEERIP6 parameter must be configured.
This address can be an MAE-Access address or an
MAE-Access network segment address.
Peer IPv6 OMCH.PEERI When the BEAR parameter is set to IPV6, the
Address P6PFXLEN PEERIP6PFXLEN parameter must be configured.
Prefix Set this parameter based on the network plan.
Length
Local IP OMCH.IP When the BEAR parameter is set to IPV4, the IP

parameter must be configured.
Set this parameter to the local IP address of the
Local OMCH.MASK When the BEAR parameter is set to IPV4, the

Mask MASK parameter must be configured.
Peer IP OMCH.PEERI When the BEAR parameter is set to IPV4, the

P PEERIP parameter must be configured. Set this
parameter to the MAE-Access address.
Peer OMCH.PEER When the BEAR parameter is set to IPV4, the

Mask MASK PEERMASK parameter must be configured. Set this

eRAN

r Name
Binding OMCH.BRT You are advised to set this parameter to YES if the
Route O&M channels use destination-based routes.
Set this parameter to NO if the O&M channels use
source-based routes.
Route OMCH.RTIDX Set this parameter to the index of the route bound
Index to the active MAE-Access.
Binding OMCH.BINDS Set this parameter to YES if the MAE-Access uses

Secondar ECONDARYR the remote HA system, BRT is set to YES, and the
y Route T standby MAE-Access address is beyond the
network segment range of the indicated route.
Otherwise, set this parameter to NO.
Secondar OMCH.SECO Set this parameter to the index of the route to the
y Route NDARYRTIDX standby MAE-Access if BINDSECONDARYRT is set
Index to YES.
The following tables describe the parameter configurations when O&M channel
switchback is required.
Data preparation for O&M channel switchback is required. The following table lists
the parameters that must be set in a GTRANSPARA MO to set NE global
transmission parameters.

r Name
OMCH GTRANSPAR If O&M channel switchback is required, set this

Switch A.OMCHSWI parameter to ENABLE.
Back TCHBACK
OMCH GTRANSPAR This parameter specifies the wait time for
Switch A.OMCHSBW switching from the standby O&M channel back to
Back Wait AITTIME the active O&M channel. Use the default value 60
Time (in the unit of second).
Data preparation for O&M channel backup is required. The following table lists
the parameters that must be set in an OMCH MO to configure an O&M channel.
Param Parameter ID Setting Notes

eter
Name
Standb OMCH.FLAG Set this parameter to MASTER for an active

y O&M channel and to SLAVE for a standby O&M
Status channel.

eRAN

eter
Name
Bearer OMCH.BEAR If two IPv6 O&M channels work in active/

Type standby mode, set this parameter to IPV6 for
both the active and standby O&M channels.
If a single IPv4 O&M channel and a single IPv6
O&M channel work in active/standby mode, set
this parameter to IPV6 and IPV4 for the active
and standby O&M channels, respectively.
Local OMCH.IP6 When the BEAR parameter is set to IPV6, the

IPv6 IP6 parameter must be configured.
Addres Set this parameter to the local IP address of the
s active O&M channel for the active O&M channel
The base station O&M IPv6 address configured
on the MAE-Access topology view must be the
same as the parameter value.
Peer OMCH.PEERIP6 When the BEAR parameter is set to IPV6, the

IPv6 PEERIP6 parameter must be configured.
Addres The parameter value can be an MAE-Access
s address or an MAE-Access network segment
address.
Peer OMCH.PEERIP6PF When the BEAR parameter is set to IPV6, the

IPv6 XLEN PEERIP6PFXLEN parameter must be configured.
Addres Set this parameter based on the network plan.
s
Prefix
Length
Local OMCH.IP Set this parameter to the local IP address of the

IP active O&M channel for the active O&M channel
Addres and to the local IP address of the standby O&M
s channel for the standby O&M channel.

Mask
Peer IP OMCH.PEERIP Set this parameter to the MAE-Access address.
Peer OMCH.PEERMASK Set this parameter to the peer subnet mask.

Mask

eRAN

eter
Name
Check OMCH.CHECKTYPE The CHECKTYPE parameter can be set to

Type AUTO_UDPSESSION only for the active O&M
channel.
If CHECKTYPE is set to AUTO_UDPSESSION for
the active OM channel, CHECKTYPE must be set
to NONE for the standby O&M channel.

complete the parameter configurations for related functions based on the
mutually exclusive relationships between the functions, as well as the actual
network scenario.
//Activating O&M channel backup if the MAE-Access does not use the remote HA system
//Operations required when two IPv6 O&M channels are configured to work in active/standby mode and
destination-based routes are used
NEXTHOP="2001:db8:100:ad1:200:100:100:1",PREF=60;
//When O&M channel switchback is not required
ADD OMCH: FLAG=MASTER, BEAR=IPV6, IP6="2001:db8:100:ad1:200:100:100:10",
PEERIP6="2001:db8:100:ad1:200:100:211:2", PEERIP6PFXLEN=124, BRT=YES, RTIDX=0,
BINDSECONDARYRT=NO;
//When O&M channel switchback is required
BINDSECONDARYRT=NO, CHECKTYPE=AUTO_UDPSESSION;
ADD OMCH: FLAG=SLAVE, BEAR=IPV6,IP6="2001:db8:100:ad1:200:100:200:10",

BINDSECONDARYRT=NO;
source-based routes are used
NEXTHOP="2001:db8:100:ad1:200:100:100:1";
NEXTHOP="2001:db8:100:ad1:200:100:200:1";
PEERIP6="2001:db8:100:ad1:200:100:211:2", PEERIP6PFXLEN=124, BRT=NO;
PEERIP6="2001:db8:100:ad1:200:100:211:2", PEERIP6PFXLEN=124, BRT=NO,
CHECKTYPE=AUTO_UDPSESSION;
ADD OMCH: FLAG=SLAVE, BEAR=IPV6, IP6="2001:db8:100:ad1:200:100:200:10",

//Operations required when a single IPv4 O&M channel and a single IPv6 O&M channel are configured to
work in active/standby mode and destination-based routes are used
NEXTHOP="2001:db8:100:ad1:200:100:100:1";

eRAN

NEXTHOP="10.10.13.2";

BINDSECONDARYRT=NO;
BINDSECONDARYRT=NO, CHECKTYPE=AUTO_UDPSESSION;
PEERMASK="255.255.255.0", BEAR=IPV4, BRT=YES, RTIDX=1, BINDSECONDARYRT=NO;
work in active/standby mode and source-based routes are used
NEXTHOP="2001:db8:100:ad1:200:100:100:1";
PEERIP6="2001:db8:100:ad1:200:100:211:2", PEERIP6PFXLEN=124, BRT=NO,
CHECKTYPE=AUTO_UDPSESSION;

//Activating O&M channel backup if the MAE-Access uses the remote HA system
destination-based routes are used
//Adding a route from the active O&M channel to the active MAE-Access
//Adding a route from the standby O&M channel to the active MAE-Access
//Adding a route from the active O&M channel to the standby MAE-Access
//Adding a route from the standby O&M channel to the standby MAE-Access
//Adding active and standby channels
BINDSECONDARYRT=YES, SECONDARYRTIDX=2;
source-based routes are used
NEXTHOP="2001:db8:100:ad1:200:100:100:1";
NEXTHOP="2001:db8:100:ad1:200:100:200:1";
work in active/standby mode and destination-based routes are used
//Adding a route from the active O&M channel to the active MAE-Access
NEXTHOP="2001:db8:100:ad1:200:100:100:1";

eRAN
//Adding a route from the standby O&M channel to the active MAE-Access
NEXTHOP="10.10.13.2";
//Adding a route from the active O&M channel to the standby MAE-Access
NEXTHOP="2001:db8:100:ad1:200:100:100:1";
//Adding a route from the standby O&M channel to the standby MAE-Access
NEXTHOP="10.10.13.2";
//Adding active and standby channels
SECONDARYRTIDX=3;
work in active/standby mode and source-based routes are used
NEXTHOP="2001:db8:100:ad1:200:100:100:1";

//Modifying the O&M channel
MOD OMCH: FLAG=MASTER, BEAR=IPV6, BRT=NO;

conditions.
//Removing the standby O&M channel of the base station


This section is based on the following assumptions:
● Local IP addresses of the active and standby O&M channels are in different
network segments.
● In IPv4 transmission mode, the next-hop IP addresses in the IPRT MO (old
model)/IPROUTE4 (new model) MO bound to active and standby O&M
channels are different.
● In IPv6 transmission mode, the next-hop IP addresses in the IPROUTE6 or
SRCIPROUTE6 MO bound to active and standby O&M channels are different.
If the actual networking is different from the assumed networking, perform the
verification based on the actual networking. That is, an O&M channel switchover
can be triggered when the O&M channel in use is faulty and the transmission link
of the other O&M channel is normal.

eRAN
To check whether O&M channel backup has taken effect, perform the following
steps:
Step 1 Run the DSP OMCH command to query the status of the active and standby O&M
channels and check which channel is in use. An O&M channel is active if the value
of OM Channel Status is Normal and the value of Used State is In Use.
Step 2 Trigger an O&M channel switchover.
Generate a transmission link fault on the O&M channel in use and verify that the
normal O&M channel can take over for the faulty O&M channel.
● If the O&M channel in use is the active one, generate a route fault on the
active O&M channel. Wait approximately 10 minutes and run the DSP OMCH
command to check the status of the standby O&M channel. The switchover is
successful if the value of OM Channel Status is Normal and the value of
Used State is In Use.
● If the O&M channel in use is the standby channel, generate a route fault on
the standby O&M channel. Wait approximately 10 minutes and run the DSP
OMCH command to check the status of the active O&M channel. The
switchover is successful if the value of OM Channel Status is Normal and the
value of Used State is In Use.
Step 3 Restore the faulty link in Step 2.
Step 4 Trigger the O&M channel switchback.
This example aims to verify that the O&M channel can be switched back to the
active channel after the fault in the active channel is rectified in Step 3.
If GTRANSPARA.OMCHSBWAITTIME is set to 60 (in the unit of second), wait

about 5 minutes and run the DSP OMCH command to check the status of the
active O&M channel.
● The switchback is successful if the value of OM Channel Status is Normal

and the value of Used State is In Use.
● Otherwise, check the value of Automatic UDP Session Detection Status. If
the value is DETECTING or SWITCHING, the detection or switchback is being
performed for the active O&M channel.
----End

Run the DSP OMCH command on the base station side to query statuses of active
and standby O&M channels.
During a switchover or switchback of the active and standby O&M channels, the
MAE reports ALM-301 NE Is Disconnected. This alarm is cleared after the
switchover or switchback is successfully completed. The base station reports
EVT-25893 Remote Maintenance Link Switchover to help determine whether the
O&M channel switchover is successful.
If the active and standby O&M channels need to be reconfigured, run the MOD
OMCH command on the base station side.

eRAN
When the O&M channel switchback function is configured, you can run the DSP
OMCH command to query the value of Automatic UDP Session Detection
Status for the active O&M channel.

eRAN
IP eRAN Engineering Guide Feature Parameter 5 Engineering Guidelines for Transmission
Description Maintenance and Detection
5 Engineering Guidelines for Transmission

Maintenance and Detection
5.1 BFD
5.1.1 Principles
Enable BFD only when BFD is required for quick fault locating in IP transmission
scenarios. BFD consumes CPU resources and transmission bandwidth, which will
affect network performance.
For regions and operators with high security requirements, enable the single-hop
BFD authentication function. The peer gateway must support BFD authentication.
Run the MOD BFDSESSION (in the old model)/MOD BFD (in the new model)
command to reconfigure the MINTI, MINRI, and DM parameters, if required.
● If BFD packets are sent at a too high frequency, excessive bandwidth is
required, which will affect the performance of the peer equipment. In this
case, increase the value of the MINTI parameter (negotiation with the
operator is required).
● If BFD packets are sent at a too low frequency, detection results are less
accurate. In this case, decrease the value of the MINTI parameter
(negotiation with the operator is required).
● If the fault detection sensitivity is too high on the peer end, ping-pong effects
occur. In this case, increase the value of the MINRI and DM parameters
(negotiation with the operator is required).
● If the fault detection sensitivity is too low on the peer end, it will take too
much time to detect a fault. In this case, decrease the value of the MINRI and
DM parameters (negotiation with the operator is required).
BFD is supported in IPv4 and IPv6 transmission scenarios.

eRAN
5.1.2.1 Benefits
None
5.1.2.2 Impacts
Network Impacts
None
Function Impacts
None
5.1.3 Requirements
5.1.3.1 Licenses
Feature ID Feature Model License Sales Unit

Name Control Item
LOFD-003007 Bidirectional LT1S000BFD0 Bidirectional per eNodeB

Forwarding 0 Forwarding
Detection Detection
MLOFD-0030 Bidirectional ML1S000BFD Bidirectional per eNodeB

07 Forwarding 00 Forwarding
Detection Detection
5.1.3.2 Software
None

None
5.1.3.3 Hardware
Base Station Models

No requirements

eRAN
Boards
● The UMPT/UMDU boards of the 3900 and 5900 series base stations support
BFD.
● The UMPT/UMDU boards of the 3900 and 5900 series base stations support
BFD authentication.
● The eNodeB needs to be configured with the UMPT, and the Ethernet port is
required.
RF Modules
5.1.3.4 Networking
None
5.1.3.5 Others
The peer device supports BFD.

r Name
Hop Type BFDSESSION. ● A single-hop BFD session is used to perform

HT point-to-point detection, generally in layer 2
networking mode.
● A multi-hop BFD session is used to perform
end-to-end connectivity check, generally in layer
3 networking mode.

eRAN

r Name
Source IP BFDSESSION. This parameter specifies the source IP address of a

SRCIP BFD session. Set this parameter based on the
network plan.
● A BFD session cannot be configured as a single-
hop session if its source IP address is a logical IP
address.
● Ensure that the DEVIP MO corresponding to this
IP address has been configured.
● This parameter must not be set to 0 and must
be set to a valid IP address. It must be set to a
device IP address (for example, the IP address of
an Ethernet port) or a logical IP address (for
example, the IP address of a loopback interface)
of a specified board, but cannot be set to the IP
address of an O&M channel. A BFD session
cannot be configured as a single-hop one if this
parameter is set to a logical IP address.
This parameter must be set to a value different
from that of the BFDSESSION.DSTIP parameter.
Destinatio BFDSESSION. This parameter specifies the destination IP address

n IP DSTIP of a BFD session. Set this parameter based on the
network plan.
If single-hop BFD is used and the source IP address
is configured on an Ethernet port, the source and
destination IP addresses must be in the same
network segment. If a BFD session with Hop Type
set to SINGLE_HOP and Session Catalog set to
RELIABILITY is inactive, routes with the next-hop
IP address being the destination IP address of this
BFD session will be disabled. If the BFD session is
active, the routes will be enabled.
The destination IP address of each BFD session
must be unique.
Min TX BFDSESSION. Set this parameter to 100.

Interval MINTI
Min RX BFDSESSION. Set this parameter to 100.
Interval MINRI
Detection BFDSESSION. Set this parameter to 3.
Multiplier DM

eRAN

r Name
Session BFDSESSION. Set this parameter based on the network plan.

Catalog CATLOG ● If this parameter is set to MAINTENANCE, a
BFD session is used only for continuity checks.
● If this parameter is set to RELIABILITY, a BFD
session is used to trigger route interlock. Route
interlock enables the standby route to take over
once the active route becomes faulty, and
therefore prevents service interruption caused
by route failures.
DSCP BFDSESSION. Set this parameter based on the network plan.

DSCP
BFD BFDSESSION. Set this parameter based on the network plan.
Authentic BFDAUTHSW ● You are advised to turn on this switch if there
ation are high security requirements for BFD control
Switch packets.
● Otherwise, you are advised to turn off this
switch.
BFD BFDSESSION. Set this parameter based on the network plan. The
Authentic BFDAUTHTYP following algorithms are supported:
ation E ● MD5 (indicated by value MD5)
Algorithm
● Meticulous MD5 (indicated by value MeMD5)
● SHA1 (indicated by value SHA1)
● Meticulous SHA1 (indicated by value MeSHA1)
The algorithm must be consistent between the
base station and the peer equipment.
BFD BFDSESSION. Set this parameter to the same value as that of the
Authentic KEYCHAINID BFDKEYCHAIN.KEYCHAINID parameter.
ation Key
Chain ID
BFD BFDKEYCHAI Negotiation with the peer end is not required.

Authentic N.KEYCHAINI Currently, only one key chain can be configured.
ation Key D
Chain ID
Key Chain BFDKEYCHAI Negotiation with the peer end is not required.
Descriptio N.KEYCHAIN Currently, only one key chain can be configured.
n DESC
BFD BFDKEY.KEYC Set this parameter to the same value as that of the
Authentic HAINID BFDKEYCHAIN.KEYCHAINID parameter.
ation Key
Chain ID

eRAN

r Name
KEY BFDKEY.KEYI Set this parameter based on the network plan. The
Identity D algorithm must be consistent between the base
station and the peer equipment.
KEY BFDKEY.KEY Set this parameter based on the network plan. The
String algorithm must be consistent between the base
NOTE
The MD5 and SHA1 algorithms are considered insufficiently secure in the industry. If these
algorithms of low security levels are used, the transmitted data may be forged by attackers.
It is recommended that the MeMD5 or MeSHA1 algorithm for authentication be used to
ensure security in data transmission.
IPv4 Scenario
r Name
Hop Type BFD.HT ● A single-hop BFD session is used to perform

point-to-point detection, generally in layer 2
networking mode.
● A multi-hop BFD session is used to perform
end-to-end connectivity check, generally in layer
3 networking mode.
IP Version BFD.IPVERSI Set this parameter to IPV4.

ON

eRAN

r Name
Source IP BFD.SRCIP This parameter specifies the source IP address of a

BFD session. Set this parameter based on the
network plan.
hop session if its source IP address is a logical IP
address.
● Ensure that the DEVIP MO corresponding to this
IP address has been configured.
● This parameter must be set to a valid IP address
and cannot be set to 0.0.0.0. It must be set to a
device IP address (for example, the IP address of
an Ethernet port) or a logical IP address (for
from that of the BFDSESSION.DSTIP parameter.
Destinatio BFD.DSTIP This parameter specifies the destination IP address

n IP of a BFD session. Set this parameter based on the
network plan.
If single-hop BFD is used and the source IP address
is configured on an Ethernet port, the source and
destination IP addresses must be in the same
network segment. If a BFD session with Hop Type
set to SINGLE_HOP and Session Catalog set to
RELIABILITY is inactive, routes with the next-hop
IP address being the destination IP address of this
BFD session will be disabled. If the BFD session is
active, the routes will be enabled.
The destination IP address of each BFD session
must be unique.
My BFD.MYDISC This parameter specifies the local discriminator of

Discrimin REAMINATO the BFD session. The local discriminator must be
ator R the same as the peer discriminator.
Min TX BFD.MINTI Set this parameter to 100.

Interval
Min RX BFD.MINRI Set this parameter to 100.

Interval
Detection BFD.DM Set this parameter to 3.

Multiplier

eRAN

r Name
Session BFD.CATLOG Set this parameter based on the network plan.

Catalog ● If this parameter is set to MAINTENANCE, a
by route failures.
DSCP BFD.DSCP Set this parameter based on the network plan.
BFD BFD.BFDAUT Set this parameter based on the network plan.

Authentic HSW ● Enable BFD authentication if there are high
ation security requirements for BFD control packets.
Switch
● Otherwise, disable BFD authentication.
BFD BFD.BFDAUT Set this parameter based on the network plan. The
Authentic HTYPE following algorithms are supported:
ation ● MD5 (indicated by value MD5)
Algorithm
● Meticulous MD5 (indicated by value MeMD5)
● SHA1 (indicated by value SHA1)
BFD BFD.KEYCHAI Set this parameter to the same value as that of the
Authentic NID BFDKEYCHAIN.KEYCHAINID parameter.
ation Key
Chain ID

ation Key D
Chain ID
n DESC
ation Key
Chain ID

eRAN

r Name
IPv6 Scenario
r Name
Hop Type BFD.HT ● A single-hop BFD session is used to perform

point-to-point detection, generally in layer 2
networking mode.
● The MBFD session is used to perform end-to-
end connectivity check (generally in Layer 3
networking).
IP Version BFD.IPVERSI Set this parameter to IPV6.

ON
Source BFD.SRCIPV6 This parameter specifies the source IPv6 address of
IPv6 a BFD session. Set this parameter based on the
hop session if its source IP address is a logical
IPv6 address.
● The source IPv6 address must have been
configured in the IPADDR6 MO.
● This parameter must be set to a global unicast
address and cannot be set to 0. It must be set to
a device IP address (for example, the IP address
of an Ethernet port) or a logical IP address (for
from that of the BFD.DSTIPv6 parameter.
Destinatio BFD.DSTIPV6 This parameter specifies the destination IPv6

n IPv6 address of a BFD session. Set this parameter based
Address on the network plan.
If single-hop BFD is used and the source IPv6
address is configured on an Ethernet port, the
source and destination IPv6 addresses must be in
the same network segment.

eRAN

r Name
My BFD.MYDISC This parameter specifies the local discriminator of

Discrimin REAMINATO the BFD session. The local discriminator must be
ator R the same as the peer discriminator.
Min TX BFD.MINTI Set this parameter to 100.

Interval
Min RX BFD.MINRI Set this parameter to 100.

Interval
Detection BFD.DM Set this parameter to 3.

Multiplier
Session BFD.CATLOG Set this parameter based on the network plan.

Catalog ● If this parameter is set to MAINTENANCE, a
by route failures.
DSCP BFD.DSCP Set this parameter based on the network plan.
BFD BFD.BFDAUT Set this parameter based on the network plan.

Authentic HSW ● Enable BFD authentication if there are high
ation security requirements for BFD control packets.
Switch
● Otherwise, disable BFD authentication.
BFD BFD.BFDAUT Set this parameter based on the network plan. The
Authentic HTYPE following algorithms are supported:
ation ● SHA1 (indicated by value SHA1)
Algorithm
BFD BFD.KEYCHAI Set this parameter to the same value as that of the
Authentic NID BFDKEYCHAIN.KEYCHAINID parameter. Only one
ation Key key chain is currently supported.
Chain ID

ation Key D
Chain ID
n DESC

eRAN

r Name
ation Key
Chain ID
NOTE
The MD5 and SHA1 algorithms are considered insufficiently secure in the industry. If these
algorithms of low security levels are used, the transmitted data may be forged by attackers.
It is recommended that the MeMD5 or MeSHA1 algorithm for authentication be used to
ensure security in data transmission.
5.1.4.1.3 MML Command Examples (Old Model)

//Adding a BFD authentication key chain (BFD Authentication Key Chain ID = 0; Key Chain Description =
bfdkeychain)
ADD BFDKEYCHAIN: KEYCHAINID=0, KEYCHAINDESC="bfdkeychain";
//Adding a key to the BFD key chain (BFD Authentication Key Chain ID = 0; KEY Identity = 0; KEY String =
123)
ADD BFDKEY: KEYCHAINID=0, KEYID=0, KEY="*****";
//Adding a BFD session (Cabinet No. = 0; Subrack No. = 0; Slot No. = 6; Session ID = 0; Source IP =
192.168.5.5; Destination IP = 192.168.5.6; Hop Type = SINGLE_HOP; Session Catalog = RELIABILITY; DSCP =
0; Protocol Version = STANDARD; BFD Authentication Switch = ON; BFD Authentication Algorithm = SHA1;
BFD Authentication Key Chain ID = 0)
ADD BFDSESSION: CN=0, SRN=0, SN=6, BFDSN=0, SRCIP="192.168.5.5", DSTIP="192.168.5.6",
HT=SINGLE_HOP, CATLOG=RELIABILITY, DSCP=0,
VER=STANDARD,BFDAUTHSW=ON,BFDAUTHTYPE=SHA1,KEYCHAINID=0;

//Removing a BFD session (cabinet No.: 0; subrack No.: 0; slot No.: 0; BFD session No.: 0)
5.1.4.1.4 MML Command Examples (New Model)

//Adding a BFD authentication key chain (BFD Authentication Key Chain ID = 0; Key Chain Description =
bfdkeychain)
ADD BFDKEYCHAIN: KEYCHAINID=0, KEYCHAINDESC="bfdkeychain";
//Adding a key to the BFD key chain (BFD Authentication Key Chain ID = 0; KEY Identity = 0; KEY String =
123)
ADD BFDKEY: KEYCHAINID=0, KEYID=0, KEY="*****";
//Adding a BFD session (Session ID = 0; Source IP = 192.168.5.5; Destination IP = 192.168.5.6; My
Discriminator = 1; Hop Type = SINGLE_HOP; Session Catalog = RELIABILITY; DSCP = 0; Protocol Version =

eRAN
STANDARD; BFD Authentication Switch = ON; BFD Authentication Algorithm = SHA1; BFD Authentication
Key Chain ID = 0)
//IPv4 transmission
BFDAUTHSW=ON, BFDAUTHTYPE=SHA1, KEYCHAINID=0;
//IPv6 transmission
DSTIPV6="2001:db8:100:ad1:200:100:200:1", MYDISCREAMINATOR=1, HT=SINGLE_HOP, BFDAUTHSW=OFF;

//Removing BFD session 0
RMV BFD: BFDSN=100;


The procedure of verifying single-hop BFD and multi-hop BFD is the same.
Step 1 Enable BFD-based IP fault detection. If BFD fails, ALM-25899 BFD Session Fault is
reported.
Step 2 On the eNodeB, run the DSP BFDSESSION (in the old model)/DSP BFD (in the
new model) command to check the BFD status.
If the value of Session State is Up, the feature has been activated.
----End

Step 1 Run the DSP BFDSESSION (in the old model)/DSP BFD (in the new model)
command to check the BFD status.
----End
If a running single-hop BFD session fails, the base station automatically disables
the routes whose next-hop IP address is the peer IP address of the failed single-
hop BFD session.
The BFD on the base station cannot determine whether a BFD interruption is
caused by link disconnection or incorrect BFD configuration.
● If the BFD is bound with a route, a BFD link fault may result in a route
switchover.
● If BFD authentication is enabled, a link fault due to authentication failure
may result in a route switchover.
If a BFD session on an eNodeB is faulty, check whether an alarm listed in Table

5-1 is generated on the eNodeB. If an alarm is generated, clear the alarm by
referring to the related alarm reference.

eRAN
Table 5-1 Alarm related to BFD sessions

Alarm ID Alarm Name Severity
25899 BFD Session Fault Minor
5.2 GTP-U Echo
5.2.1 Principles
You are advised to enable GTP-U echo if the eNodeB needs to check the time
required for detecting a GTP-U path disconnection or failure as well as the number
of detected GTP-U path disconnections or failures.
5.2.2.1 Benefits
None
5.2.2.2 Impacts
Network Impacts
After static GTP-U echo is enabled, if the detection result shows that a user-plane
link is faulty, no bearer will be set up on the link. As a result, the bearer access
success rate may decrease and the rate of bearer access failures with the cause of
transport layer faults may increase.
Function Impacts
None
5.2.3 Requirements
5.2.3.1 Licenses
None
5.2.3.2 Software
None

None

eRAN
5.2.3.3 Hardware
Base Station Models

No requirements
Boards
No requirements
RF Modules
5.2.3.4 Networking
To use link-level static GTP-U echo for a link, the link must have been created.
5.2.3.5 Others
None

The following table describes the key parameters that must be set in a GTPU MO
to configure global GTP-U parameters, including the global GTP-U echo switch
and the duration and number of timeouts for detecting a disconnection or failure
in the GTP-U path.
Parameter Parameter Setting Notes

Name ID
ECHO GTPU.TIMEO Set this parameter based on the network plan. If

Frame UTTH no echo response is received during the period
Timeout specified by this parameter, echo response times
out.
ECHO GTPU.TIMEO This parameter specifies the maximum number of

Frame UTCNT echo response timeouts. Set this parameter based
Timeout on the network plan. If the number of consecutive
Count echo response timeouts reaches the parameter
value, the GTP-U path fails.
DSCP GTPU.DSCP Set this parameter based on the network plan.
Static GTPU.STATI Set this parameter based on the network plan. The
Check CCHK value ENABLE is recommended.
Switch

eRAN
The following table describes the key parameter in a USERPLANEPEER MO to

configure the link-level static GTP-U echo switch in endpoint configuration mode.

Name ID
Static USERPLANE Set this parameter based on the network plan. By

Check PEER.STATIC default, this parameter is set to FOLLOW_GLOBAL.
Switch CHK
The following table describes the key parameter that must be set in an IPPATH
MO to set the link-level GTP-U static detection switch in link configuration mode.

Name ID
Static IPPATH.STAT Set this parameter based on the network plan. By

Check ICCHK default, this parameter is set to FOLLOW_GLOBAL.
Switch This parameter applies when IPv4 is used.

The following table describes the key parameters that must be set in a GTPU MO
to configure global GTP-U parameters.

Name ID
ECHO GTPU.TIMEO Set this parameter based on the network plan. If

Frame UTTH no echo response is received during the period
Timeout specified by this parameter, echo response times
out.
ECHO GTPU.TIMEO This parameter specifies the maximum number of

Frame UTCNT echo response timeouts. Set this parameter based
Timeout on the network plan. If the number of consecutive
Count echo response timeouts reaches the parameter
value, the GTP-U path fails.
DSCP GTPU.DSCP Set this parameter based on the network plan.
Static GTPU.STATI Set this parameter based on the network plan. The
Check CCHK value ENABLE is recommended.
Switch
The following table describes the key parameter in a USERPLANEPEER MO to

configure the link-level static GTP-U echo switch in endpoint configuration mode.

eRAN

Name ID
Static USERPLANE Set this parameter based on the network plan. By

Check PEER.STATIC default, this parameter is set to FOLLOW_GLOBAL.
Switch CHK
The following table describes the key parameter that must be set in an IPPATH
MO to set the link-level GTP-U static detection switch in link configuration mode.

Name ID
Static IPPATH.STAT Set this parameter based on the network plan. By

Check ICCHK default, this parameter is set to FOLLOW_GLOBAL.
Switch This parameter applies when IPv4 is used.

//Turning on the global static GTP-U echo switch on the eNodeB side
MOD GTPU: STATICCHK=ENABLE;
//Turning on the link-level static GTP-U echo switch on the eNodeB side
MOD USERPLANEPEER: UPPEERID=0, STATICCHK=ENABLE;
MOD IPPATH: PATHID=0, SN=0, STATICCHK=ENABLE;

//Turning off the global static GTP-U echo switch on the eNodeB side
MOD GTPU: STATICCHK=DISABLE;
//Turning off the link-level static GTP-U echo switch on the eNodeB side
MOD USERPLANEPEER: UPPEERID=0, STATICCHK=DISABLE;
MOD IPPATH: PATHID=0, SN=0, STATICCHK=DISABLE;

//Enabling static GTP-U echo globally on the eNodeB side
MOD GTPU: STATICCHK=ENABLE;
//Enabling static GTP-U echo for a link on the eNodeB side
MOD USERPLANEPEER: UPPEERID=0, STATICCHK=ENABLE;
MOD IPPATH: PATHID=0, STATICCHK=ENABLE;

//Disabling static GTP-U echo globally on the eNodeB side
MOD GTPU: STATICCHK=DISABLE;
//Disabling static GTP-U echo for a link on the eNodeB side
MOD USERPLANEPEER: UPPEERID=0, STATICCHK=DISABLE;
MOD IPPATH: PATHID=0, STATICCHK=DISABLE;

eRAN


For details about GTP-U echo monitoring, see the MAE-Access online help.
The activation observation procedure is as follows:
Step 1 Before starting GTP-U echo monitoring, check the following items.
If... Then...
GTP-U static detection is Ensure that the user-plane link is set up

enabled in the initial data successfully.
configuration
GTP-U static detection is Ensure that bearers are set up for UEs in the cell.
disabled in the initial data This can be achieved using UEs to access the cell
configuration and injecting packets in the uplink or downlink for
the UEs.
The eNodeB can send GTP-U echo control messages in either of the preceding
scenarios.
Step 2 Log in to the MAE-Access. Press F1 while the MAE-Access window is active to see
the MAE-Access online help.
Step 3 Create a GTP-U echo monitoring task as follows:
1. On the MAE-Access, choose Monitor > Signaling Trace > Signaling Trace
Management.
2. On the navigation tree of the Signaling Trace Management window, choose
Base Station Device and Transport > Transport Trace > GTPU Trace.
3. On the displayed GTPU Trace window, set parameters of the GTP-U echo
monitoring task to create a task.
Step 4 Run the monitoring task, and check the results. GTP-U echo monitoring is
successfully activated if echo request and response messages can be viewed in real
time.
----End

None
5.3 LLDP
5.3.1 Principles
Link Layer Discovery Protocol (LLDP) allows network devices to advertise local
information in the local subnet, including the system name, system description,

eRAN
port ID, and MAC address. In IP transmission mode, you are advised to enable this
function if network topology information is required.
5.3.2.1 Benefits
None
5.3.2.2 Impacts
Network Impacts
None
Function Impacts
None
5.3.3 Requirements
5.3.3.1 Licenses
None
5.3.3.2 Software
None

None
5.3.3.3 Hardware
Base Station Models

No requirements
Boards
No requirements
RF Modules

eRAN
5.3.3.4 Networking
LLDP has been enabled on the interconnected equipment.
5.3.3.5 Others
None

Adding LLDP global configuration:
The following table lists the parameters that must be set in an LLDPGLOBALINFO
MO to configure LLDP global parameters.
Parameter Name Parameter ID Setting Notes
LLDPDU Tx Interval LLDPGLOBAL.TXINTVAL Set this parameter to 30

(in the unit of second).
LLDP Hold Multiplier LLDPGLOBAL.HOLDMU Set this parameter to 4.

LTI
Reinit Delay LLDPGLOBAL.REINITDE Set this parameter to 2
LAY (in the unit of second).
Transmission Delay LLDPGLOBAL.DELAY Set this parameter to 2

LLDP Notify Switch LLDPGLOBAL.NOTIFYS If the NE topology

W drawing function is
enabled on the FMA, set
this parameter to
ENABLE.
Notify Interval LLDPGLOBAL.NOTIFYIN Set this parameter to 5

TERVAL (in the unit of second).
LLDP Port Configuration LLDPGLOBAL.PORTCFG The value

Mode MODE MANUAL(Manual) is
recommended.
Adding an LLDP local entity:
The following table describes the parameters that must be set in an LLDPPORT
MO to configure LLDP parameters.

eRAN
Binding VLAN LLDPLOCAL.BNDVLAN Set this parameter to

YES.
VLAN ID LLDPLOCAL.VLANID Set this parameter based

VLAN Priority LLDPLOCAL.VLANPRI Set this parameter based


Adding LLDP global configuration:
The following table lists the parameters that must be set in an LLDPGLOBALINFO
MO to configure LLDP global parameters.
LLDPDU Tx Interval LLDPGLOBAL.TXINTVAL Set this parameter to 30

LLDP Hold Multiplier LLDPGLOBAL.HOLDMU Set this parameter to 4.

LTI
Reinit Delay LLDPGLOBAL.REINITDE Set this parameter to 2
LAY (in the unit of second).
Transmission Delay LLDPGLOBAL.DELAY Set this parameter to 2

LLDP Notify Switch LLDPGLOBAL.NOTIFYS If the NE topology

W drawing function is
enabled on the FMA, set
this parameter to
ENABLE.
Notify Interval LLDPGLOBAL.NOTIFYIN Set this parameter to 5

TERVAL (in the unit of second).
LLDP Port Configuration LLDPGLOBAL.PORTCFG The value

Mode MODE MANUAL(Manual) is
recommended.
Adding an LLDP local entity:

The following table describes the parameters that must be set in an LLDP MO to
configure local LLDP parameters.

eRAN
LLDP ID LLDP.LLDPID Set this parameter based

Ethernet Port ID LLDP.ETHPORTID Set this parameter based

Binding VLAN LLDP.BNDVLAN Set this parameter based

VLAN ID LLDP.VLANID Set this parameter based

VLAN Priority LLDP.VLANPRI Set this parameter based


//Manually configuring LLDP local port information
//Setting LLDP Port Configuration Mode to MANUAL
SET LLDPGLOBALINFO: NOTIFYSW=ENABLE, PORTCFGMODE=MANUAL;
//Adding LLDP port configuration information to port 0 in slot 6, subrack 0, and cabinet 0 without binding
the port to a VLAN
ADD LLDPPORT: CN=0, SRN=0, SN=6, SBT=ETH_COVERBOARD, PN=0, BNDVLAN=NO;
//Automatically configuring LLDP port information for all ports
SET LLDPGLOBALINFO: NOTIFYSW=ENABLE, PORTCFGMODE=AUTO;

//Manually removing LLDP local port information from the port
//Removing the LLDP port information from port 0 in slot 6, subrack 0, and cabinet 0
RMV LLDPPORT: CN=0, SRN=0, SN=6, SBT=ETH_COVERBOARD, PN=0;
//Automatically removing LLDP port information from all ports
SET LLDPGLOBALINFO: PORTCFGMODE=MANUAL;

//Manually configuring LLDP local port information
//Setting LLDP Port Configuration Mode to MANUAL
SET LLDPGLOBALINFO: NOTIFYSW=ENABLE, PORTCFGMODE=MANUAL;
//Adding LLDP port configuration information to port 0 in slot 6, subrack 0, and cabinet 0 without binding
the port to a VLAN
ADD ETHPORT: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PN=0, PORTID=0, PA=FIBER;
ADD LLDP: LLDPID=0, ETHPORTID=0, BNDVLAN=NO;
//Automatically configuring LLDP port information for all ports
SET LLDPGLOBALINFO: NOTIFYSW=ENABLE, PORTCFGMODE=AUTO;

//Manually removing LLDP local port information from the port
//Removing the LLDP port information from port 0 in slot 6, subrack 0, and cabinet 0
RMV LLDP: LLDPID=0;
//Automatically removing LLDP port information from all ports
SET LLDPGLOBALINFO: PORTCFGMODE=MANUAL;

eRAN


Step 1 Run the DSP LLDPPORT (in the old model)/DSP LLDP (in the new model)
command to query information about the LLDP local port.
Step 2 Run the DSP LLDPNEIGHBOR command to query LLDP remote information.
Expected result: If the LLDP local port information and LLDP remote information
can be queried successfully, the LLDP function has been successfully enabled.
----End

None

eRAN
IP eRAN Engineering Guide Feature Parameter 6 Engineering Guidelines for Quick Transmission
Description Congestion Detection
6 Engineering Guidelines for Quick

Transmission Congestion Detection
6.1 Principles
Enable quick transmission congestion detection when eX2/X2 interfaces carry
coordination-based services such as CA in relaxed backhaul mode in coordinated
networking scenarios and the transmission bandwidth is insufficient.
Quick transmission congestion detection is supported only in IPv4 transmission
scenarios.
6.2 Network Analysis
6.2.1 Benefits
None
6.2.2 Impacts
Network Impacts
None
Function Impacts
None
6.3 Requirements
6.3.1 Licenses
None

eRAN
6.3.2 Software
None

None
6.3.3 Hardware
Base Station Models
● Macro base station
● LampSite base station
The DBS3900 LampSite and DBS5900 LampSite working in LO/UL mode
support quick transmission congestion detection.
● Micro base station
– The following FDD micro base station models support quick transmission
congestion detection when working in LO/UL mode:
▪ BTS3202E
▪ BTS3203E
▪ BTS3911E
▪ BTS3912E
Boards
Only the UMPTb, UMPTe, UMPTg, UMPTga, and UMDU of 3900 and 5900 series
base stations support quick transmission congestion detection.
RF Modules
6.3.4 Networking
eX2/X2 interfaces work in relaxed backhaul mode in coordinated networking
scenarios.
The transmission bandwidth setting meets the following requirements:
● Traffic shaping is configured on the egress port and the committed access
rate (CAR) is configured for traffic policing on the ingress port.
● If the CAR is configured for traffic policing on the ingress port, traffic shaping
must be configured on the egress port of the upstream device, thereby
ensuring consistency between the transmit bandwidth of the upstream device

eRAN
and that corresponding to the CAR of the ingress port. This avoids packet loss
caused by transmission bandwidth mismatch.
6.3.5 Others
1. IP PM has been activated for the eX2/X2 link but not backward activated.
2. Base stations are synchronized over the eX2/X2 interface.
6.4 Operation and Maintenance
6.4.1 Data Configuration
6.4.1.1 Data Preparation

The following table lists the parameter that must be set in an
ENODEBALGOSWITCH MO to enable quick transmission congestion detection.
Parameter Name Parameter ID Option Setting Notes
OverBBUsSwitch ENodeBAlgoSwit TransportCongDe- Set this parameter

ch.OverBBUsSwit tectSw based on the
ch network plan.
6.4.1.2 Using MML Commands

//Activating quick transmission congestion detection
MOD ENODEBALGOSWITCH: OverBBUsSwitch= TransportCongDetectSw-1;

//Deactivating quick transmission congestion detection
MOD ENODEBALGOSWITCH: OverBBUsSwitch= TransportCongDetectSw-0;
6.4.1.3 Using the MAE-Deployment

6.4.2 Activation Verification

Using MML Commands
On the eNodeB side, query quick transmission congestion detection results.
Step 1 Run the LST GLOBALPROCSWITCH command to query the value of the
GlobalProcSwitch.ItfTypeForNonIdealModeServ parameter, which indicates the
interface type to support coordination features in no-ideal backhaul mode. If the
GlobalProcSwitch.ItfTypeForNonIdealModeServ parameter value is EX2, an eX2

eRAN
interface is used for carrying coordination services in non-ideal backhaul mode. If

the GlobalProcSwitch.ItfTypeForNonIdealModeServ parameter value is X2, an
X2 interface is used for carrying coordination services in non-ideal backhaul mode.
Step 2 Query the quick transmission congestion detection result of each eX2 link. If an
eX2 interface is used for carrying coordination-based services in relaxed backhaul
mode, run the DSP EX2UPINFO command. If an X2 interface is used for carrying
coordination-based services in relaxed backhaul mode, run the DSP X2UPINFO
command. In the command outputs, if the values of Transmit Congestion Delay
and Transmit Available Bandwidth are not NULL, quick transmission congestion
detection works normally. If the values are NULL, quick transmission congestion
detection fails.
----End
Real-Time Monitoring Mode

If eX2/X2 interfaces are configured in endpoint mode, perform the following steps
on the LMT to monitor quick transmission congestion detection for eX2/X2
interfaces in real time:
1. In the navigation tree, click Monitor to open the Monitor tab page.
2. In the Monitor Navigation Tree pane, choose Monitor > Common
Monitoring > Transport Auto Setup User Plane Monitoring.
3. In the displayed dialog box, set IPPM Flag to User Plane Link+IPPM
+Transport Congestion Detect, fill in the VRF instances, source IPs,
destination IPs, and DSCPs, and click Submit.
4. Double-click the corresponding task to view results of quick transmission
congestion detection, including the average uplink transmission congestion
delay and average uplink available transmission bandwidth.
If X2 interfaces are configured in link mode, perform the following steps on the
LMT to monitor quick transmission congestion detection for X2 interfaces in real
time:
1. In the navigation tree, click Monitor to open the Monitor tab page.
2. In the Monitor Navigation Tree pane, choose Monitor > Common
Monitoring > Transport Link Traffic Monitoring.
3. In the displayed dialog box, select Include IPPM Statistic, Include Transport
Congestion Detect, and IP paths for detection, fill in the IP path IDs, and click
Submit.
If eX2/X2 interfaces are configured in endpoint mode, perform the following steps
on the MAE-Access to monitor quick transmission congestion detection for eX2/X2
interfaces in real time:
1. Choose Monitor > Signaling Trace > Signaling Trace Management.
2. Choose Base Station Device and Transport > Transport Performance
Monitoring > Transport Auto Setup User Plane Monitoring.
3. In the displayed dialog box, set IPPM Flag to Include IPPM+Transport
Congestion Detect, set parameters of user-plane links, and click Finish.

eRAN

If X2 interfaces are configured in link mode, perform the following steps on the
MAE-Access to monitor quick transmission congestion detection for X2 interfaces
in real time:
1. Choose Monitor > Signaling Trace > Signaling Trace Management.
2. Choose Base Station Device and Transport > Transport Performance
Monitoring > Transport Link Traffic Monitoring.
3. In the displayed dialog box, set Extend Option to Include IPPM+Transport
Congestion Detect, select the bound IP path IDs, and click Finish.
6.4.3 Network Monitoring

None

eRAN
Description 7 Parameters
7 Parameters
The following hyperlinked EXCEL files of parameter documents match the

software version with which this document is released.
● Node Parameter Reference: contains device and transport parameters.

● eNodeBFunction Parameter Reference: contains all parameters related to
radio access functions, including air interface management, access control,
mobility control, and radio resource management.
● eNodeBFunction Used Reserved Parameter List: contains the reserved
parameters that are in use and those that have been disused.
NOTE
You can find the EXCEL files of parameter reference and used reserved parameter list for
the software version used on the live network from the product documentation delivered
with that version.
FAQ 1: How do I find the parameters related to a certain feature from

parameter reference?
Step 1 Open the EXCEL file of parameter reference.
Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, LOFD-001016 or
TDLOFD-001016.
Step 3 Click OK. All parameters related to the feature are displayed.
----End
FAQ 2: How do I find the information about a certain reserved parameter

from the used reserved parameter list?
Step 1 Open the EXCEL file of the used reserved parameter list.
Step 2 On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT
columns to locate the reserved parameter, which may be only a bit of a parameter.
View its information, including the meaning, values, impacts, and product version
in which it is activated for use.
----End

eRAN
Description 8 Counters
8 Counters
The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● eNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from

performance counter reference?
Step 1 Open the EXCEL file of performance counter reference.

Step 2 On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID, for example, LOFD-001016 or
TDLOFD-001016.
Step 3 Click OK. All counters related to the feature are displayed.
----End

eRAN
Description 9 Glossary
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
Description 10 Reference Documents
10 Reference Documents
● Common Transmission
● IPv4 Transmission
● IPv6 Transmission
● IP Transmission Efficiency Improvement
● 2G, 3G and LTE Co-transmission
● IP Performance Monitor
● IP Active Performance Measurement
● Ethernet OAM
● Transmission Resource Management
● S1 and X2 Self-Management
● RAN Sharing
● IPsec
● eX2 Self-Management
● Interface Self-planning
● VRF
● Intelligent Wi-Fi Selection based on eCoordinator
● Document in GBSS Feature Documentation:
– IP BSS Engineering Guide
● Document in RAN Feature Documentation:
– IP RAN Engineering Guide
● Documents in 3900 & 5900 Series Base Station Product Documentation:
– eRAN Reconfiguration Guide
– eRAN Troubleshooting Guide
– 3900 & 5900 Series Base Station Initial Configuration Guide
– 3900 & 5900 Series Base Station LMT User Guide
● Documents in ECO6910 Product Documentation:
– ECO6910 Initial Configuration Guide
– ECO6910 LMT User Guide

eRAN
Description 10 Reference Documents
– ECO6910 Reconfiguration Guide

– ECO6910 Alarm Reference

IP eRAN Engineering Guide (eRAN18.1 - 02)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IP eRAN Engineering Guide (eRAN18.1 - 02)

Uploaded by

Copyright:

Available Formats

eRAN

IP eRAN Engineering Guide Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.............................................................................................................4

3 Interface Engineering Guidelines........................................................................................ 8

Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. ii

3.1.5.1 Data Configuration........................................................................................................................................................ 38

Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. iii

Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. iv

4 Engineering Guidelines for Transmission Reliability.................................................... 89

Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. v

4.2.2 Network Analysis............................................................................................................................................................... 98

Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. vi

5 Engineering Guidelines for Transmission Maintenance and Detection................. 119

Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. vii

5.3.1 Principles............................................................................................................................................................................ 135

6 Engineering Guidelines for Quick Transmission Congestion Detection.................141

Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. viii

10 Reference Documents...................................................................................................... 149

Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. ix

This chapter describes changes not included in the "Parameters", "Counters",

1.1 eRAN18.1 02 (2022-04-27)

1.2 eRAN18.1 01 (2022-03-08)

1.3 eRAN18.1 Draft A (2021-12-30)

Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. 1

Added support for the Added the FDD ● 3900 and

Added support for OM Added parameters: FDD ● 3900 and

Deleted the UCCU None FDD ● 3900 and

Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. 2

Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. 3

2 About This Document

2.1 General Statements

● The technical principles of features and their related parameters

2.2 Applicable RAT

2.3 Features in This Document

Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. 4

Feature ID Feature Name Chapter/Section

LBFD-003001 Transmission Networking 3.2.3 Requirements

LBFD-00300101 Star Topology 3.2.3 Requirements

LBFD-00300102 Chain Topology 3.2.3 Requirements

LBFD-00300103 Tree Topology 3.2.3 Requirements

LBFD-003006 IPv4/IPv6 Dual Stack 3.1.3 Requirements

LBFD-003007 IP Route Backup 4.1 Ethernet Route

LOFD-003005 OM Channel Backup 4.3 O&M Channel

LOFD-003007 Bidirectional Forwarding 5.1 BFD

LOFD-003008 Ethernet Link 4.2 Link Aggregation

LOFD-003017 S1 and X2 over IPv6 3.2 Deployment of an

This document describes the following NB-IoT features.

Feature ID Feature Name Chapter/Section

MLBFD-12000307 IPv4/IPv6 Dual Stack 3.1.3 Requirements

MLBFD-12000308 IP Route Backup 3.2.3 Requirements

MLOFD-003005 OM Channel Backup 4.3 O&M Channel

MLOFD-003007 Bidirectional Forwarding 5.1 BFD

MLOFD-003008 Ethernet Link 4.2 Link Aggregation

Issue 02 (2022-04-27) Copyright © Huawei Technologies Co., Ltd. 5

Feature ID Feature Name Chapter/Section

MLOFD-003017 S1 over IPv6 3.2 Deployment of an

2.4 Feature Differences Between NB-IoT and FDD

MLBFD-12000307 LBFD-003006 None 3.1.3

MLBFD-12000308 LBFD-003007 IP None 4.1 Ethernet