RAN17.1 Reconfiguration Guide For BSC6900 (03) (PDF) - en

RAN17.
Reconfiguration Guide for BSC6900

Issue
03
Date
2015-06-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 03 (2015-06-30)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
RAN17.1
About This Document
About This Document

Overview
This document describes how to reconfigure a RAN after it starts operating, including how to
expand the network capacity and adjust equipment configurations. For details about the
configurations before the system is put into operation, see BSC6900 UMTS Initial Configuration
Guide. For details about how to enable and adjust a feature, see RAN Feature Parameter
Description.
Product Versions
The following table lists the product versions and solution version related to this document.
Product Name
Product Version
Solution Version
BSC6900
V900R017C10
RAN17.1
BTS3900
BTS3900A
V100R010C10. The
mapping single-mode base
station version is:
BTS3900L
NodeB: V200R017C10
BTS3900C
BTS3900AL
DBS3900
CME
V200R015C10
Intended Audience
This document is intended for:
l
Technical support engineers
Maintenance engineers
Field engineers
Issue 03 (2015-06-30)

ii
RAN17.1
About This Document
Network optimization engineers
Organization
1 Change Description
This section provides information about the changes in different document versions. There are
two types of changes, including function changes and editorial changes. Function changes refer
to changes in functions of a specific product version. Editorial changes refer to changes in
wording or addition of information that was not described in the earlier version.
2 Introduction to Reconfiguration
This chapter defines reconfiguration and introduces reconfiguration tools.
3 Checking a License
This section describes how to check a newly granted license of the base station controller.
4 Backing Up and Restoring Data
During network optimization, some parameters are reconfigured, but the network performance
is not as good as expected. When this occurs, you can restore to the original network conditions
by backing up and restoring data.
5 Backing Up and Restoring Data by CME
This section describes how to back up and restore data. Users can use the function to restore the
network to the state before parameters were reconfigured during network performance
optimization, if the network performance does not meet users' expectations.
6 Reconfiguring the BSC6900
This chapter describes how to reconfigure a running BSC6900 or expand its capacity.
7 Reconfiguring the NodeB
This chapter describes how to reconfigure a running NodeB or expand its capacity.
8 Reconfiguring the UMTS Network
This chapter describes how to reconfigure a UMTS network on a running RNC.
9 Reconfiguring the Interfaces
This chapter describes how to reconfigure interfaces in the case of capacity expansion,
reconfiguration, and network cutover.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Issue 03 (2015-06-30)

iii
RAN17.1
About This Document
Symbol
Description
Indicates an imminently hazardous situation which, if not
avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not
avoided, could result in death or serious injury.
avoided, may result in minor or moderate injury.
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Calls attention to important information, best practices and
tips.
NOTE is used to address information not related to personal
injury, equipment damage, and environment deterioration.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention
Description
Times New Roman
Normal paragraphs are in Times New Roman.
Boldface
Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic
Book titles are in italics.
Courier New
Examples of information displayed on the screen are in

Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Issue 03 (2015-06-30)
Convention
Description
Boldface
The keywords of a command line are in boldface.
Italic
Command arguments are in italics.

iv
RAN17.1
About This Document
Convention
Description
[]
Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... }
Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ]
Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }*
Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]*
Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
>
Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format
Description
Key
Press the key. For example, press Enter and press Tab.
Key 1+Key 2
Press the keys concurrently. For example, pressing Ctrl+Alt

+A means the three keys should be pressed concurrently.
Key 1, Key 2
Press the keys in turn. For example, pressing Alt, A means

the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Issue 03 (2015-06-30)

RAN17.1
Issue 03 (2015-06-30)
About This Document
Action
Description
Click
Select and release the primary mouse button without moving

the pointer.
Double-click
Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag
Press and hold the primary mouse button and move the
pointer to a certain position.

vi
RAN17.1
Contents
Contents
About This Document.....................................................................................................................ii
1 Change Description.......................................................................................................................1
2 Introduction to Reconfiguration.................................................................................................4
2.1 Definition........................................................................................................................................................................5
2.2 Tools...............................................................................................................................................................................5
3 Checking a License......................................................................................................................10
4 Backing Up and Restoring Data...............................................................................................12
4.1 Backing Up and Restoring Data (Dopra Linux)...........................................................................................................14
4.1.1 Starting the omu_backup_linker tool........................................................................................................................14
4.1.2 Backing Up the System Data.....................................................................................................................................14
4.1.3 Restoring the System Data........................................................................................................................................16
4.2 Backing Up and Restoring Data (Windows)................................................................................................................18
4.2.1 Starting the omu_backup_linker tool........................................................................................................................18
4.2.2 Backing Up the System Data.....................................................................................................................................19
4.2.3 Restoring the System Data........................................................................................................................................23
5 Backing Up and Restoring Data by CME...............................................................................28

6 Reconfiguring the BSC6900.......................................................................................................29
6.1 Changing Signaling Points...........................................................................................................................................30
6.2 Changing the Board Backup Mode from Independent to Active/Standby...................................................................32
6.3 Adjusting OMU Slots...................................................................................................................................................35
6.4 Changing Optical Fibers from Direct Connection to Y-Shaped Connection...............................................................37
6.5 Install a Built-in NE......................................................................................................................................................41
6.6 Uninstall a Built-in NE.................................................................................................................................................46
6.7 Adding a Board or a Subrack.......................................................................................................................................52
6.7.1 Adding a Subrack......................................................................................................................................................52
6.7.2 Adding an SPUa, SPUb, or SPUc Board...................................................................................................................55
6.7.3 Adding a DPUb/DPUe/DEUa Board.........................................................................................................................58
6.7.4 Adding an ASUa Board.............................................................................................................................................61
6.7.5 Adding an Interface Board........................................................................................................................................65
6.7.6 Adding an NIU Board................................................................................................................................................67
Issue 03 (2015-06-30)

vii
RAN17.1
Contents
6.8 Removing a Board or a Subrack...................................................................................................................................70

6.8.1 Removing a Subrack..................................................................................................................................................70
6.8.2 Removing an SPUa/SPUb/SPUc Board (UCP/RUCP).............................................................................................72
6.8.3 Removing a DPUb/DPUe/DEUa Board....................................................................................................................79
6.8.4 Removing an ASUa Board........................................................................................................................................81
6.8.5 Removing an Interface Board....................................................................................................................................84
6.8.6 Removing an NIU Board...........................................................................................................................................86
7 Reconfiguring the NodeB..........................................................................................................89

7.1 Changing the Maintenance Mode of the NodeB..........................................................................................................90
7.2 Device Data Reconfiguration.......................................................................................................................................93
7.2.1 Reconfiguring the NE Information of a NodeB........................................................................................................93
7.2.2 Reconfiguring the NodeB Clock Source or the Clock Working Mode.....................................................................95
7.2.3 Reconfiguring the IP Address of a NodeB Clock Server..........................................................................................99
7.2.4 Adding a WBBP or UBBP to a 3900 Series Base Station.......................................................................................103
7.2.5 Adding an RF Module.............................................................................................................................................108
7.2.6 Changing CPRI Ports for RF Modules....................................................................................................................116
7.2.7 Replacing a Baseband Processing Board.................................................................................................................122
7.2.8 Replacing a Main Control Board.............................................................................................................................127
7.2.9 Changing the Local Maintenance IP address of a NodeB.......................................................................................134
7.3 Radio Data Reconfiguration.......................................................................................................................................137
7.3.1 Reconfiguring the Number of Carriers for a NodeB...............................................................................................137
7.3.2 Adding a Set of Baseband Equipment.....................................................................................................................140
7.3.3 Modifying a Set of Baseband Equipment................................................................................................................144
7.3.4 Removing a Set of Baseband Equipment................................................................................................................147
7.3.5 Adjusting the Networking of RF Units (Between Chain and Ring Topologies).....................................................150
7.3.6 Adjusting the Networking of RF Units (From Chain to Star Topologies)..............................................................157
7.4 Transport Data Reconfiguration.................................................................................................................................163
7.4.1 Replacing the U2000...............................................................................................................................................163
7.4.2 Adjusting the VLAN Priority..................................................................................................................................168
7.4.3 Changing the VLAN Configuration Mode..............................................................................................................172
7.5 Reconfigurations Dedicated to the LampSite Solution..............................................................................................180
7.5.1 Adding a pRRU.......................................................................................................................................................180
7.5.2 Adding an RHUB....................................................................................................................................................185
7.5.3 Adding a pRRU-Aggregation Cell..........................................................................................................................189
7.5.4 Combining pRRU-Aggregation Cells.....................................................................................................................194
7.5.5 Splitting a pRRU-Aggregation Cell........................................................................................................................198
8 Reconfiguring the UMTS Network.......................................................................................203

8.1 Reconfiguring a Cell...................................................................................................................................................204
8.1.1 Changing Cell Power...............................................................................................................................................204
8.1.2 Changing Cell Frequencies......................................................................................................................................210
8.1.3 Changing the Scrambling Code of a Cell................................................................................................................212
Issue 03 (2015-06-30)

viii
RAN17.1
Contents
8.1.4 Reconfiguring Cell System Information Parameters...............................................................................................214

8.1.5 Reconfiguring Cell Radio Link Power Parameters.................................................................................................218
8.1.6 Reconfiguring Cell Synchronization Parameters....................................................................................................220
8.1.7 Modifying the Area Information of a Cell...............................................................................................................223
8.1.8 Modifying the UTRAN Registration Area of a Cell...............................................................................................226
8.1.9 Modifying a Cell Name...........................................................................................................................................228
8.1.10 Modify the ID of a Cell.........................................................................................................................................231
8.1.11 Adding an SCCPCH..............................................................................................................................................233
8.1.12 Removing a UMTS Cell........................................................................................................................................237
8.2 Modifying an SCCPCH..............................................................................................................................................241
8.3 Reconfiguring Neighboring Cells...............................................................................................................................249
8.3.1 Adding an Intra-Frequency Neighboring Cell.........................................................................................................249
8.3.2 Adding an Inter-Frequency Neighboring Cell.........................................................................................................253
8.3.3 Adding a Neighboring GSM Cell............................................................................................................................258
8.3.4 Adding a Neighboring LTE Cell.............................................................................................................................262
8.3.5 Modifying a Neighboring Cell................................................................................................................................265
8.3.6 Removing a Neighboring Cell.................................................................................................................................266
8.4 Reconfiguring NodeB Management Distribution.......................................................................................................270
8.4.1 Regularly Reconfiguring NodeB Distribution Using MML Commands................................................................270
8.4.2 Manually Reconfiguring NodeB Distribution.........................................................................................................272
9 Reconfiguring the Interfaces...................................................................................................277

9.1 Interface Capacity Expansion.....................................................................................................................................278
9.1.1 Iu-CS Interface Capacity Expansion.......................................................................................................................278
9.1.1.1 Iu-CS Interface Capacity Expansion (in ATM Transmission Mode)...................................................................278
9.1.1.2 Iu-CS Interface Capacity Expansion (in IP Transmission Mode)........................................................................282
9.1.1.3 Iu-CS Interface Capacity Expansion (IP Pool).....................................................................................................287
9.1.2 Iu-PS Interface Capacity Expansion........................................................................................................................291
9.1.2.1 Iu-PS Interface Capacity Expansion (in ATM Transmission Mode)...................................................................291
9.1.2.2 Iu-PS Interface Capacity Expansion (in IP Transmission Mode).........................................................................294
9.1.2.3 Iu-PS Interface Capacity Expansion (IP Pool).....................................................................................................299
9.1.3 Iur Interface Capacity Expansion............................................................................................................................303
9.1.3.1 Iur Interface Capacity Expansion (in ATM Transmission Mode)........................................................................304
9.1.3.2 Iur Interface Capacity Expansion (in IP Transmission Mode).............................................................................307
9.1.3.3 Iur Interface Capacity Expansion (IP Pool)..........................................................................................................312
9.1.4 Iub Interface Capacity Expansion............................................................................................................................317
9.1.4.1 Iub Interface Capacity Expansion (in ATM Transmission Mode).......................................................................317
9.1.4.2 Iub Interface Capacity Expansion (in IP Transmission Mode)............................................................................320
9.1.4.3 Iub Interface Capacity Expansion (IP Pool).........................................................................................................325
9.2 Reconfiguring the Transmission Mode and the Networking Mode...........................................................................329
9.2.1 Reconfiguring the Transmission Mode...................................................................................................................329
9.2.1.1 Changing the Transmission Mode over the Iub Interface from ATM to IP.........................................................329
Issue 03 (2015-06-30)

ix
RAN17.1
Contents
9.2.1.2 Changing the Transmission Mode over the Iub Interface from ATM to IP Pool.................................................333
9.2.1.3 Changing the Transmission Mode over the Iub Interface from ATM/IP Dual Stack to IP Pool.........................339
9.2.1.4 Changing Networking Mode over the Iub Interface from IP to Transmission Resource Pool.............................345
9.2.1.5 Changing Networking Mode over the Iu-CS Interface from IP to Transmission Resource Pool........................349
9.2.1.6 Changing Networking Mode over the Iu-PS Interface from IP to Transmission Resource Pool.........................354
9.2.1.7 Changing Networking Mode over the Iur Interface from IP to Transmission Resource Pool.............................356
9.2.2 Reconfiguring Timeslot Cross Connection.............................................................................................................359
9.2.2.1 Configuring a Timeslot Cross Connection on the RNC.......................................................................................359
9.2.2.2 Configuring a Timeslot Cross Connection on a NodeB.......................................................................................361
9.3 Network Cutover........................................................................................................................................................362
9.3.1 Changing the Connection Between the BSC and the MSC.....................................................................................362
9.3.1.1 Changing the Connection Between the BSC and the MSC (IP Transmission Mode Retained on the Iu-CS Interface)
..........................................................................................................................................................................................363
9.3.1.2 Changing the Connection Between the RNC and MSC (ATM Transmission Mode Retained on the Iu-CS Interface)
..........................................................................................................................................................................................366
9.3.1.3 Changing the Connection Between the RNC and the MSC (Transmission Mode on the Iu-CS Interface Changed
from ATM to IP)...............................................................................................................................................................367
Issue 03 (2015-06-30)

RAN17.1
Change Description
This section provides information about the changes in different document versions. There are
two types of changes, including function changes and editorial changes. Function changes refer
to changes in functions of a specific product version. Editorial changes refer to changes in
wording or addition of information that was not described in the earlier version.
03 (2015-06-30)
This issue includes the following changes.
Change Type
Change Description
Functional
change
New
l Added descriptions about NIU reconfiguration. For

details, see 6.7.6 Adding an NIU Board and 6.8.6
Removing an NIU Board.
l Added Removing an SPUb/SPUc Board (NASP),
because removing the SPUb/SPUc board (NASP) is
supported in UMTS mode.
Issue 03 (2015-06-30)

RAN17.1
Change Type
Change Description
Modified
l Deleted operations of modifying board content and

OMU configurations. For details, see 6.2 Changing
the Board Backup Mode from Independent to
Active/Standby.
l Optimized the operation of adding a subrack. For
details, see 6.7.1 Adding a Subrack.
l Added the board normalization principle and
optimized operation procedures accordingly. For
details, see 6.7.2 Adding an SPUa, SPUb, or SPUc
Board, 6.7.3 Adding a DPUb/DPUe/DEUa Board,
6.7.4 Adding an ASUa Board, and 6.7.5 Adding an
Interface Board.
l Optimized the operation of removing a subrack. For
details, see 6.8.1 Removing a Subrack.
l Modified operation procedures and added
descriptions about the RUCP mode. For details, see
6.8.2 Removing an SPUa/SPUb/SPUc Board
(UCP/RUCP).
l Modified background information. For details, see
6.8.4 Removing an ASUa Board.
Deleted
Editorial change
None
None
02 (2015-05-08)
This issue includes the following changes.
Change Type
Change Description
Function change
Added
None.
Modified
The description of the procedure is modified, and the

corresponding notes are added. For details, see6.7.1
Adding a Subrack.
Deleted
None.
Editorial change
None.
01 (2015-03-25)
This issue does not include any changes.
Issue 03 (2015-06-30)

RAN17.1
Draft A (2015-01-15)
This is the Draft A release of the RAN17.1.
Compared with issue 03 (2014-09-10) of RAN16.0, this issue includes the following changes.
Change Type
Change Description
Feature change
New
l Added the built-in ECO6910. Added sections 6.5

Install a Built-in NE, 6.6 Uninstall a Built-in NE,
6.7.4 Adding an ASUa Board, and 6.8.4 Removing
an ASUa Board.
Modified
None.
Deleted
None.
Editorial change
Issue 03 (2015-06-30)
None.

RAN17.1
Introduction to Reconfiguration
About This Chapter

This chapter defines reconfiguration and introduces reconfiguration tools.
Issue 03 (2015-06-30)

RAN17.1
2.1 Definition
Reconfiguration refers to the process of adding, deleting, or modifying the data of the RAN
system (consisting of at least one base station controller and one base station) after it starts
operating.
This document focuses on associated data preparation and reconfiguration procedures. The
detailed data analysis process for network optimization and the number of boards and links for
capacity expansion are determined according to actual network conditions.
This document involves the following scenarios:
l
Network optimization
Network optimization is the process of adjusting and optimizing network performance
based on the data obtained from performance measurements or drive tests when the network
is in service.
System capacity expansion

System capacity expansion enables the system to serve more users with hardware addition
or reconfiguration in the existing network.
Transmission reconstruction
Transmission reconstruction is the process of changing the transmission mode of the
existing transport network.
Network cutover
Network cutover is the process of physically or logically changing the cables or devices in
use.
NOTE
This document describes only the data configuration procedure. The data planning is described in
professional service documentation.
2.2 Tools
The local maintenance terminal (LMT) and the Configuration Management Express (CME) can
be used to configure the BSC6900.
Table 2-1 describes the reconfiguration tools.
Table 2-1 Reconfiguration tools
Issue 03 (2015-06-30)
Data Configuration Tool
Function
LMT
The LMT provides graphic user interfaces (GUIs) for users to

configure a single network element (NE) using MML
commands.
CME
The CME provides GUIs for users to configure a single base

station controller, base station, or cell. In addition, the CME
supports batch configuration of multiple base stations and
cells by importing or exporting a configuration file.
RAN17.1
Process of Reconfiguring Data Using the CME

When reconfiguring data by using the CME, the operation process is the same in each
reconfiguration scenario but data reconfiguration steps are different. Figure 2-1 shows the
process of reconfiguring data. Table 2-2 describes the process.
Figure 2-1 Reconfiguration process
NOTE
You can press F1 to view the CME Help for the function description and related operations.
Table 2-2 Reconfiguration process
Issue 03 (2015-06-30)
Procedure
Description
Ensure that
the NE is
connected to
the U2000
You can use the CME to configure NE data only after the NE is successfully
connected to the U2000.
Collect
configuration
data
Before configuring data, you have to collect the data to be configured.

RAN17.1
Procedure
Description
Start the CME
CME functions can be started in the following modes: CME client mode and
U2000 client mode. The methods of starting the CME are as follows:
l CME client mode
Start CME functions on the U2000 client in application mode.
1. On the Windows desktop, choose Start > All Programs >
iManager U2000 MBB Client > U2000 version Client. The login
dialog box is displayed.
2. Enter the user name and password, and click Login.
NOTE
You can click
to add, modify, or delete server information.
in the upper left part

3. Log in to the U2000 client and click
of the U2000 main window. The application window is displayed.
4. On the Application Center tab page, double-click the CME icon
to start the CME.
Start the CME client directly.
1. On the Windows desktop, choose Start > All Programs >
iManager U2000 MBB Client > CM Express. The login dialog
box is displayed.
NOTE
You can click
l U2000 client mode

Start CME functions on the U2000 client in traditional mode.
1. On the Windows desktop, choose Start > All Programs > iManager
U2000 MBB Client > U2000 version Client. The login dialog box
is displayed.
NOTE
You can click
3. After logging in to the U2000 client, choose CME on the menu bar
of the U2000 main window and then choose a submenu item to start
the related CME function.
Issue 03 (2015-06-30)

RAN17.1
Procedure
Description
Create a
planned data
area.
You have to create a planned data area before configuring data.

1. On the menu bar, choose Area Management > Planned Area > Create
Planned Area (CME client mode) or CME > Planned Area > Create
Planned Area (U2000 client mode). A dialog box is displayed for you
to create a planned data area.
2. Add the NEs that you want to reconfigure to the planned data area that
you want to create. Enter the information about the planned data area and
click OK. The CME starts to create the planned data area. After the
planned data area is created, the CME automatically opens it.
For details about how to create a planned data area, press F1 to obtain
the online help.
Reconfigure
data.
Data is reconfigured using different CME functions based on scenarios. You

need to check the reconfiguration operations in each scenario.
Verify data.
After data reconfiguration is complete, verify the data to ensure data

accuracy.
l Check accuracy and integrity of configuration data.
1. On the menu bar of the planned data area, choose Advanced > Check
Data (CME client mode) or CME > Advanced > Check Data
(U2000 client mode) to start verification.
2. Select the NEs that you want to verify from the navigation tree in the
left pane, add them to the right pane, and click OK. The CME starts
the verification. You can verify the configuration data for a maximum
of 50 NEs at a time.
l Check configuration data consistency.
On the menu bar of the current or planned data area, choose Advanced
> Consistency Check (CME client mode) or CME > Advanced >
Consistency Check (U2000 client mode) to start the data consistency
check.
For detailed operations, see section Manually Checking NE Data
Consistency in the U2000 Help.
l Check for any conflicts between configuration data and data on the live
network. Before activating configuration data, you can compare
configuration data in the planned data area with the live network
configuration data in the current data area to locate data conflicts. Then,
you can reconfigure the data in the planned data area based on the check
results to ensure successful data activation.
On the menu bar of the planned data area, choose Area Management >
Planned Area > Check Conflict (CME client mode) or CME > Planned
Area > Check Conflict (U2000 client mode) to start the conflict check.
For detailed operations, see section Checking for Data Conflicts in the
U2000 Help.
When verifying configuration data, modify configuration data as prompted
until the verification succeeds.
Issue 03 (2015-06-30)

RAN17.1
Procedure
Description
Export
configuration
and rollback
scripts.
Export configuration data from the CME as a script. When exporting the
script, the CME automatically generates a rollback script.
Planned Area > Export Incremental Scripts (CME client mode) or
CME > Planned Area > Export Incremental Scripts (U2000 client
mode). Then, export configuration scripts.
NOTE
l If the OMCH is disconnected in the reconstruction scenario, you are advised to
export the full base station script during the script export.
The operation portal is as follows: Choose Advanced > Export NE Files (CME
client mode) or CME > Advanced > Export NE Files (U2000 client mode) on
the current or planned data area.
l When you export incremental scripts:
l If you need to check or edit scripts in the script executor window before
activating the scripts, select Launch script executor only during the export.
The CME then automatically uploads the scripts to the U2000 server.
l If you need to immediately activate scripts after they are exported, select
Launch script executor and activate exported project during the export.
l If you do not need to activate scripts or check scripts in the script executor
window, select Do not launch script executor during the export.
For detailed operations, see section Exporting Incremental Scripts from

a Planned Data Area in the U2000 Help.
Activate
scripts.
Activate the scripts exported the CME for them to take effect on NEs. If
Launch script executor and activate exported project is not selected
when you export scripts, you have to manually activate the scripts.
1. On the menu bar of the CME main window, choose System > Script
Executor (CME client mode) or CME > Script Executor (U2000 client
mode). The script executor window is displayed.
2. (Optional and required when Do not launch script executor is selected
during the script export) Choose Project > Load Project on the menu
bar of the script executor. In the displayed dialog box, select the folder
that stores the scripts to be activated (the folder must contain the
scriptcfg.xml file), and click Select. The script executor window is
displayed again. Right-click one or more projects to be uploaded and
choose Upload Project from the shortcut menu. Enter the project
description and click OK.
3. Right-click a project to be activated in the right pane and choose Activate
Project from the shortcut menu.
Before activating a project, you are advised to preactivate the project to
check script correctness by performing the following operation: Rightclick the project and choose Preactivate Project from the shortcut menu.
For detailed operations, see section Activating Data Using the Script
Executor in the U2000 Help.
Issue 03 (2015-06-30)

RAN17.1
Checking a License
This section describes how to check a newly granted license of the base station controller.
Prerequisites
l
A new license has been granted.
The license file has been imported to the \ftp\license directory in the installation directory
of the OMU active workspace. For details about how to import the license file, see FTP
Server.
Context
A new license is required in the following situations:
l
A network is deployed.
New license control items are introduced to the customization (C) version to be upgraded.
These license control items, however, are not defined in the license file of the earlier version.
New license control items are introduced to the C version to be upgraded. These license
control items are defined in the license file of the earlier version, but their values are
incorrect.
The release (R) version is upgraded.
The equipment serial number (ESN) changes.
The functions controlled by a license need to be enabled.
The license in use is about to expire.
BTSs are redistributed among BSCs, and the original licensed value cannot meet the license
requirement after the BTS redistribution. Therefore, new licenses are required.
Procedure
Step 1 Run the CHK DATA2LIC command to check a license file. In this step, set File Name to an
appropriate value.
----End
Issue 03 (2015-06-30)

10
RAN17.1
Example
/*Checking the license file named ON1020691_GU2.dat*/
CHK DATA2LIC: FN="ON1020691_GU2.dat";
Follow-up Procedure
After the verification succeeds, run the ACT LICENSE command to activate the license.
Issue 03 (2015-06-30)

11
RAN17.1
Backing Up and Restoring Data
About This Chapter

During network optimization, some parameters are reconfigured, but the network performance
is not as good as expected. When this occurs, you can restore to the original network conditions
by backing up and restoring data.
Context
Table 4-1 Data restoration
NE
Data Restoring
Description
Strength
Weakness
Base
station
controll
er
Restore the configuration

database stored on the
OMU board.
This operation is simple.
The base station

controller is restarted
during a rollback, and
services are interrupted.
Execute rollback scripts.
You do not need to restart

the base station controller
during the rollback.
Services are not
interrupted.
The procedure for making

rollback scripts is
complex.
Use the CME to back up

and restore data.
The rollback succeeds

only in some scenarios.
Execute rollback scripts.
None
The procedure for making

rollback scripts is
complex.
Use the CME to back up

and restore data.
The rollback succeeds

only in some scenarios.
Base
station
Issue 03 (2015-06-30)
The data can be definitely

restored to the original
status.

12
RAN17.1
For the procedure of restoring data by executing rollback scripts, see sections "Follow-up
Procedure" and "Rollback" in each reconfiguration scenario.
For the procedure of backing up and restoring data using the Configuration Management Express
(CME), see Backing Up and Restoring Data (CME-Based).
This chapter describes how to back up and restore the configuration database stored on the OMU
board of the base station controller.
Issue 03 (2015-06-30)

13
RAN17.1
4.1 Backing Up and Restoring Data (Dopra Linux)

This section describes how to back up and restore data when the OMU runs the Dopra Linux
operating system.
4.1.1 Starting the omu_backup_linker tool

This section describes how to start the omu_backup_linker tool.
Context
l
If an independent OMU is configured, log in to the OMU to start the omu_backup_linker

tool.
If active and standby OMUs are configured, log in to the active OMU to start the
omu_backup_linker tool.
Procedure
Step 1 Log in to the target OMU by referring to Logging In to the OMU.
Step 2 Enter cd /mbsc/bam/common/services to go to the directory where the program of the
omu_backup_linker tool is saved.
Step 3 Enter ./omu_backup_linker to start the omu_backup_linker tool. The following information is
displayed:
# The backup/restore option
# backup :Backup OMU database
# restore :Restore OMU database
# Please select one option to backup or restore OMU database, if you don't know it,
consult the administrator.
Please input a valid bkp_res_type :
----End
4.1.2 Backing Up the System Data

This section describes how to back up the BSC6900 configuration data, performance data, alarm
data, operation logs, operator account, rights information, and product information using an
MML command or the omu_backup_linker_tool. The backup data can be encrypted to ensure
the security in data storage and transmission.
Prerequisites
l
Using an MML command:

You have logged in to the LMT by referring to Logging In to and Logging Out of the LMT.
Using the omu_backup_linker_tool:

The Logging In to the OMU is connected.
Issue 03 (2015-06-30)

14
RAN17.1
Context
NOTICE
l When the OMUs work in active/standby mode, the system data must be backed up on the
active OMU.
l Before capacity expansion, upgrade, or software loading, you must back up the OMU data
manually to avoid a system data backup failure.
Procedure
l
Using an MML command

1.
Run the BKP DB command to back up the data to the specified directory on the OMU
hard disk. In this step, set Path of Backup File and Backup File Name to appropriate
values. If the backup file needs to be encrypted, set Encrypted Mode to Password
Encrypted and specify File Encryption Password.
2.
Obtain the backup file from the specified directory by referring to the procedures
described in Transferring OMU Files to a Local PC.
Using the omu_backup_linker_tool

1.
Log in to the target OMU.
2.
Enter cd /mbsc/bam/common/services to go to the directory where the program of

the omu_backup_linker tool is saved.
3.
Enter ./omu_backup_linker to start the omu_backup_linker tool.
4.
Enter backup after the Please input a valid bkp_res_type : message

is displayed.
5.
Enter the save path and names of the backup files.
6.
Enter the encryption mode when the Please input a valid encrypt
mode : message is displayed. If the backup file does not need to be encrypted, enter
unencrypt. If the backup file needs to be encrypted, enter encrypt.
7.
If you have entered encrypt in the previous step, enter File Encryption Password.
The system starts to back up data. If the data is successfully backed up to the OMU
hard disk, the Backup OMU database succeed! message is displayed.
8.
described in Transferring OMU Files to a Local PC.
----End
Example
Backing up the OMU data to /mbsc/bam using the omu_backup_linker_tool and naming the
file as omu.bak with the file encrypted
omd_test_name /mbsc/bam/common/services # ./omu_backup_linker
# backup : Backup OMU database
# restore : Restore OMU database
Issue 03 (2015-06-30)

15
RAN17.1
# Please select one option to backup or restore OMU database, if you don't know
it, please consult the administrator.
Please input a valid bkp_res_type : backup
# The backup file pathname.
# eg: d:/mbsc/bam/omu.bak, in windows;
# eg: /mbsc/bam/omu.bak, in linux.
Please input a valid backup file pathname : /mbsc/bam/omu.bak
# The backup file encrypted mode.
# unencrypt: The backup file is unencrypted.
# encrypt: The backup file is encrypted.
Please input a valid encrypt mode : encrypt
# The backup file password.
Please input a valid file password :
Backup omu database
[100%]
Backup OMU database succeed!
omd_test_name /mbsc/bam/common/services #
4.1.3 Restoring the System Data

This section describes how to restore the system data using the data backup file and using the
encrypted backup file.
Prerequisites
The system data has been backed up.
Context
Restoring the BSC6900 system data will interrupt services on the BSC6900. The data on the
host will be inconsistent with the data on the OMU after the system data is restored. As a result,
the services will be greatly impacted. Therefore, you are advised to restore the system data in
the early morning hours when traffic volume is low.
As an example, the OMU in active/standby mode is used in this document. If an OMU is in
independent mode, skip operations on the standby OMU.
This chapter describes how to restore data by using the following methods:
l
If an MML command is used to restore data, only the BSC6900 configuration data is
restored while other data, such as alarm data or performance data, cannot be restored.
If the omu_backup_linker tool is used to restore data, all BSC6900 data is restored,
including configuration data, alarm data, performance data, operating logs, administrator
account, authority information, SSL configuration information, certificate information and
product information.
Restoring the system data through an MML command
Procedure
Issue 03 (2015-06-30)
1.
Run the LST BKPFILE command to query data backup files saved in the OMU
active workspace installation directory\data\backup directory.
2.
Run the RTR DB command to restore configuration data on the OMU. If the backup
file is encrypted, specify Encrypted Mode and File Encryption Password.
3.
Run the LST SUBNET and DSP OMU commands to query the internal network
segments. If the queried internal network segments in the two command outputs are
16
RAN17.1
different, run the RST OMU command to perform soft resets on the active and standby
OMU boards.
l
Restoring the system data by using the omu_backup_linker tool

1.
Log in to the active and standby OMUs by referring to Logging In to the OMU.
2.
Enter /etc/rc.d/omud stop to stop the omud process on the active and standby OMUs.
3.
Restore data in the original active OMU using the omu_backup_linker tool.
a.
Enter cd /mbsc/bam/common/services to go to the directory where the program

of the omu_backup_linker tool is saved
b.
Log in to the OMU by referring to Enter ./omu_backup_linker to start the

c.
Enter restore and press Enter after the Please input a valid
bkp_res_type : message is displayed.
d.
Type the save path and name of the backup file and press Enter when the
Please input a valid backup file pathname : message is
displayed.
e.
Enter the encryption mode when the Please input a valid encrypt
mode : message is displayed. If the backup file has not been encrypted, enter
unencrypt. If the backup file has been encrypted, enter encrypt. Then, press
Enter.
f.
If you enter encrypt in the previous step, specify File Encryption Password
and press Enter. The system data starts to be restored. After the restoration is
complete, a message is displayed, indicating whether the restoration is
successful. If the restoration is successful, the Restore OMU database
succeed! message is displayed on the interface.
4.
Copy and save the backup file to be restored in the standby OMU using the psftp
software. For details, see Obtaining and Using the psftp Software.
5.
Repeat Step 3 to restore data in the original standby OMU using the
6.
Enter /etc/rc.d/omud start to start the omud on the active and standby OMUs.
7.
Log in to the LMT by referring to Logging In to and Logging Out of the LMT in the
BSC6900 UMTS LMT User Guide.
8.
Run the LCK CMCTRL command to lock the data configuration right.
9.
Run the LST CFGMODE command to query whether the System Configuration
Mode parameter is set to Effective Mode for all subracks. If this parameter is set to
Ineffective Mode for any subrack, run the SET CFGDATAEFFECTIVE command
to change the value to Effective Mode.
10. Check the consistency between the BSC6900 host data and the OMU data.
NOTE
After data restoration, check whether the BSC6900 host data is consistent with the OMU data.
If not, load the restored data to the BSC6900 host.
a.
Run the ACT CRC command to check whether the host data is consistent with
the OMU data.
If the data is consistent, end this task.
If the data is inconsistent, go to 10.2.
Issue 03 (2015-06-30)

17
RAN17.1
b.
Run the FMT DATA command to format the data in the OMU database so that
the data can be loaded into the host.
c.
If data inconsistency occurs in only one subrack, run the RST SUBRACK
command to reset this subrack. Before running the command, set Subrack No.
----End
Example
Restore the OMU data by using the omu.bak.ecf file (the file name extension after encryption
is .ecf) under /mbsc/bam. The following shows an example of the results:
omd_test_name
Shutting down
omd_test_name
omd_test_name
~ # /etc/rc.d/omud stop
mbsc daemon..........
~ # cd /mbsc/bam/common/services
/mbsc/bam/common/services # ./omu_backup_linker

# backup : Backup OMU database
# restore : Restore OMU database
# Please select one option to backup or restore OMU database, if you don't know
it, please consult the administrator.
Please input a valid bkp_res_type : restore
# The backup file pathname.
# eg: d:/mbsc/bam/omu.bak, in windows;
# eg: /mbsc/bam/omu.bak, in linux.
Please input a valid backup file pathname : /mbsc/bam/omu.bak.ecf
# The backup file encrypted mode.
# unencrypt: The backup file is unencrypted.
# encrypt: The backup file is encrypted.
Please input a valid encrypt mode : encrypt
# The backup file password.
Please input a valid file password :
Restore omu database
[100%]
Restore OMU database succeed!
omd_test_name /mbsc/bam/common/services # /etc/rc.d/omud start
Starting mbsc daemon
4.2 Backing Up and Restoring Data (Windows)

This section describes how to back up and restore data when the OMU uses the Windows
operating system.
4.2.1 Starting the omu_backup_linker tool

This section describes how to start the omu_backup_linker tool.
Context
l
If an independent OMU is configured, log in to the OMU to start the omu_backup_linker

tool.
If active and standby OMUs are configured, log in to the active OMU to start the
Procedure
Step 1 Log in to the target OMU by referring to Logging In to the OMU.
Issue 03 (2015-06-30)

18
RAN17.1
Step 2 Choose Start > Run. Then enter the cmd command and press Enter to enter the command mode
of the OMU.
Step 3 Enter the cd /d d:\mbsc\bam\common\services command and press Enter to go to the directory
where the program of the omu_backup_linker tool is saved.
Step 4 Type the omu_backup_linker.exe command and press Enter. As Figure 4-1 shows, an
interface is displayed.
Figure 4-1 Starting the omu_backup_linker Tool
----End
4.2.2 Backing Up the System Data

This section describes how to back up the BSC6900 configuration data, performance data, alarm
data, operation logs, operator account, rights information, and product information using an
MML command or the omu_backup_linker_tool. The backup data can be encrypted to ensure
the security in data storage and transmission.
Prerequisites
l
Using an MML command:

You have logged in to the LMT by referring to Logging In to and Logging Out of the LMT.
Using the omu_backup_linker_tool:

You have logged in to the OMU by referring to Logging In to the OMU.
Issue 03 (2015-06-30)

19
RAN17.1
Context
NOTICE
l When the OMUs work in active/standby mode, the system data must be backed up on the
active OMU.
l Before capacity expansion, upgrade, or software loading, you must back up the OMU data
manually to avoid a system data backup failure.
Procedure
l
Using an MML command

1.
Run the BKP DB command to back up the data to the specified directory on the OMU
hard disk. In this step, set Path of Backup File and Backup File Name to appropriate
values. If the backup file needs to be encrypted, set Encrypted Mode to Password
Encrypted and specify File Encryption Password.
2.
described in Transfer OMU Files to the Local Computer.
Using the omu_backup_linker_tool

1.
Choose Start > Run. Then enter the cmd command and press Enter to enter the
command mode of the OMU.
2.
Enter the cd /d d:\mbsc\bam\common\services command and press Enter to go to

the directory where the program of the omu_backup_linker tool is saved.
3.
Enter backup in the interface, as shown in Figure 4-2.

Figure 4-2 Backing up the system data
Issue 03 (2015-06-30)

20
RAN17.1
4.
Enter the save path and names of the backup files.

Figure 4-3 Entering the save path and names of backup files
5.
If the backup file does not need to be encrypted, enter unencrypt. If the backup file
needs to be encrypted, enter encrypt, as shown in Figure 4-4.
Figure 4-4 Specifying encryption mode of the backup file
6.
Issue 03 (2015-06-30)
If you have entered encrypt in the previous step, enter File Encryption Password,
as shown in Figure 4-5.
21
RAN17.1
Figure 4-5 Entering the file encryption password
7.
The system starts to back up data. If the data is successfully backed up to the OMU
hard disk, the "Backup OMU database succeed!" message is displayed, as
shown in Figure 4-6.
Figure 4-6 Backup result indication
8.
Press any key to exit.
----End
Issue 03 (2015-06-30)

22
RAN17.1
4.2.3 Restoring the System Data

This section describes how to restore the system data using the data backup file and using the
encrypted backup file.
Context
Restoring the BSC6900 system data will interrupt services on the BSC6900. The data on the
host will be inconsistent with the data on the OMU after the system data is restored. As a result,
the services will be greatly impacted. Therefore, you are advised to restore the system data in
the early morning hours when traffic volume is low.
As an example, the OMU in active/standby mode is used in this document. If an OMU is in
independent mode, skip operations on the standby OMU.
This chapter describes how to restore data by using the following methods:
l
If an MML command is used to restore data, only the BSC6900 configuration data is
restored while other data, such as alarm data or performance data, cannot be restored.
If the omu_backup_linker tool is used to restore data, all BSC6900 data is restored,
including configuration data, alarm data, performance data, operating logs, administrator
account, authority information, SSL configuration information, certificate information and
product information.
Restoring the system data through an MML command
Procedure
Issue 03 (2015-06-30)
1.
Run the LST BKPFILE command to query data backup files saved in the OMU
active workspace installation directory\data\backup directory.
2.
Run the RTR DB command to restore configuration data on the OMU. If the backup
file is encrypted, specify Encrypted Mode and File Encryption Password.
3.
Run the LST SUBNET and DSP OMU commands to query the internal network
segments. If the queried internal network segments in the two command outputs are
different, run the RST OMU command to perform soft resets on the active and standby
OMU boards.
Restoring the system data by using the omu_backup_linker tool

1.
(Optional) If the OMUs work in active/standby mode, stop the data synchronization
between the active and standby OMUs by referring to Stopping the Synchronization
of the Data of the Active and Standby OMUs
2.
Log in to the active and standby OMUs by referring to Logging In to the OMU.
3.
Choose Start > Run. Enter the cmd command to enter the command mode of the
OMU on the active and standby OMUs.
4.
Run the net stop omud command to stop the omud on the active and standby OMUs.
5.
Restore data in the original active OMU using the omu_backup_linker tool.
a.
Choose Start > Run. Then enter the cmd command and press Enter to enter the
command mode of the OMU.
b.
Enter the cd /d d:\mbsc\bam\common\services command and press Enter to

go to the directory where the program of the omu_backup_linker tool is saved.
23
RAN17.1
c.
Enter the omu_backup_linker.exe command and press Enter to start the

d.
Enter the restore command and press Enter on the interface, as shown in Figure
4-7.
Figure 4-7 Restoring the system data
e.
Enter the save path and names of the backup files, and then press Enter.
Figure 4-8 Entering the save path and names of backup files
f.
Issue 03 (2015-06-30)
If the backup file is not encrypted, enter unencrypt. If the backup file is
encrypted, enter encrypt. Then, press Enter, as shown in Figure 4-9.
24
RAN17.1
Figure 4-9 Entering the mode of the backup files to be restored
g.
If you enter encrypt in the previous step, specify File Encryption Password
and press Enter, as shown in Figure 4-10.
Figure 4-10 Entering the file encryption password
h.
Issue 03 (2015-06-30)
The system data starts to be restored. After the restoration is complete, a message
is displayed, indicating whether the restoration is successful. If the restoration is
successful, the Restore OMU database succeed! message is displayed
on the interface, as shown in Figure 4-11.

25
RAN17.1
Figure 4-11 Result indication of restoring the system data
i.
Press any key to exit.
6.
Copy and save the backup file to be restored in the standby OMU using file sharing.
For details, see Uploading Files to the OMU.
7.
Repeat Step 5 to restore data in the original active OMU using the omu_backup_linker
tool.
8.
Managing the omud on the active and standby OMUs.
9.
Log in to the LMT by referring to Logging In to and Logging Out of the LMT in the
BSC6900 UMTS LMT User Guide.
10. Run the LCK CMCTRL command to lock the data configuration right.
11. Run the LST CFGMODE command to query whether the System Configuration
Mode parameter is set to Effective Mode for all subracks. If this parameter is set to
Ineffective Mode for any subrack, run the SET CFGDATAEFFECTIVE command
to change the value to Effective Mode.
12. Check the consistency between the BSC6900 host data and the OMU data.
NOTE
After data restoration, check whether the BSC6900 host data is consistent with the OMU data.
If not, load the restored data to the BSC6900 host.
a.
Run the ACT CRC command to check whether the host data is consistent with
the OMU data.
If the data is consistent, end this task.
If the data is inconsistent, go to 12.2.
Issue 03 (2015-06-30)
b.
Run the FMT DATA command to format the data in the OMU database so that
the data can be loaded into the host.
c.
If data inconsistency occurs in only one subrack, run the RST SUBRACK
command to reset this subrack. Before running the command, set Subrack No.
26
RAN17.1
13. (Optional, required only for Step 1) Run the MML command STR DATASYNC to
start data synchronization between the active and standby OMUs.
----End
Issue 03 (2015-06-30)

27
RAN17.1
5 Backing Up and Restoring Data by CME
Backing Up and Restoring Data by CME

This section describes how to back up and restore data. Users can use the function to restore the
network to the state before parameters were reconfigured during network performance
optimization, if the network performance does not meet users' expectations.
Context
The CME provides the following methods for you to back up and restore data:
You create a planned data area to reconfigure network data. All the operations performed in the
planned data area are recorded and then exported as a script. This script takes effect on the live
network after it is activated by the script executor. When exporting the script, the CME generates
a fallback script. If unsatisfied with the reconfiguration, you can activate the fallback script to
restore the network to a state before the reconfiguration.
Procedure
Step 1 After you perform operations based on the process for reconfiguring data using the CME, the
CME automatically generates a data fallback script. For details about the process, see Process
for Reconfiguring Data Using the CME.
Step 2 Perform steps based on Fallback in each scenario.
1.
On the menu bar of the CME main window, choose System > Script Executor (CME client
mode) or CME > Script Executor (U2000 client mode). The script executor window is
displayed.
2.
In the Script Executor window, click the Summary tab.
3.
Right-click the project whose data you want to roll back and choose Activate Fallback
Project from the shortcut menu.
You can press F1 on the CME to view section Fallback Based on Configuration Steps in the
U2000 Help for the detailed function operations and introduction.
----End
Issue 03 (2015-06-30)

28
RAN17.1
Reconfiguring the BSC6900
About This Chapter

This chapter describes how to reconfigure a running BSC6900 or expand its capacity.
Issue 03 (2015-06-30)

29
RAN17.1
6.1 Changing Signaling Points

When a BSC is relocated or a network is optimized, originating signaling points (OSPs) and
destination signaling points (DSPs) change. In this case, you need to change related settings.
Prerequisites
l
Before changing signaling points, collect information listed in Table 6-1.

Table 6-1 Required information
Information
Description
OSP information
Query and record the name and code of a

new OSP.
DSP information
Query and record the name and code of a

new DSP.
Hardware requirement
None
Software requirement
None
License requirement
None
Context
NOTICE
Changing signaling points will interrupt BSC services. Therefore, perform this operation when
the traffic is light, for example, during early morning hours.
Prepare the data listed in the following table.
Table 6-2 Data preparation
Issue 03 (2015-06-30)
Data
Type
MO
Setting Notes
Data
Source
MML
Command
OSP
OPC
Set OSP name and OSP code to the

target values.
Network
plan
MOD OPC
DSP
N7DPC
Set DSP name and DSP code to the

target values.
Network
plan
MOD
N7DPC

30
RAN17.1
Procedure
l
Using MML commands

Record the information before reconfiguration
1.
Run the LST OPC command to query the values of all OSP-related parameters.
2.
Run the LST N7DPC command to query the values of all DSP-related parameters.
Change information about an OSP.

1.
Run the MOD OPC command to modify the values of OSP name and OSP
code.
Change information about a DSP.
1.
Run the MOD N7DPC command to modify the values of DSP name and DSP
code.
2.
Run the MOD UCNNODE command to modify the CN node.
The CME-based procedure is as follows:

1.
Select a base station controller in the left pane of the planned data area. The NE object
tree is displayed in the lower part of the left pane, as shown in the following figure:
Figure 6-1 Configuration window
2.
In area 1, select or search for the MO you want to configure based on the following
list and double-click the MO. In area 2, set parameters for the MO and click
save configured data.
to
----End
Issue 03 (2015-06-30)

31
RAN17.1
Example
/*Information Recording Procedure*/
//Recording the OSP information
LST OPC: SPX=1, SPDF=WNF;
//Recording the DSP information
LST N7DPC: DPX=1, SPDF=WNF;
/*Reconfiguration Procedure*/
//Changing information about an OSP
MOD OPC: SPX=1, SPCBITS=BIT14, SPDF=WNF, SPC=10001, NAME="OPCName2";
//Changing information about a DSP
MOD N7DPC: DPX=1, SPDF=WNF, DPC=1002, NAME="DPCName2";
//Modifying the CN node
MOD UCNNODE: CnOpIndex=0, CNId=0, CNDomainId=PS_DOMAIN;
Follow-up Procedure
l
Verification
Run the LST OPC command to check that the values of OSP-related parameters are
consistent with the data plan.
Run the LST N7DPC command to check that the values of DSP-related parameters are
consistent with the data plan.
Rollback
Using MML commands
The rollback procedure is similar to the reconfiguration procedure, except that
parameters in the rollback procedure are set to values used before the reconfiguration.
1.
On the menu bar of the CME main window, choose System > Script Executor
(CME client mode) or CME > Script Executor (U2000 client mode). The script
executor window is displayed.
2.
3.
Right-click the project whose data you want to roll back and choose Activate
Fallback Project from the shortcut menu.
You can press F1 on the CME to view section Fallback Based on Configuration
Steps in the U2000 Help for the detailed function operations and introduction.
6.2 Changing the Board Backup Mode from Independent to

Active/Standby
To improve the reliability of BSC6900 boards, change the backup mode of boards from
independent to active/standby. This section describes how to change the backup mode of
interface boards and .
Issue 03 (2015-06-30)

32
RAN17.1
Prerequisites
l
Before changing the board backup mode, collect information listed in Table 6-3.
Information
Description
Board information
Query and record the number, model,

backup mode, and slots that accommodate
the boards.
The interface board and cables have been installed.
None
License requirement
None
Context
NOTICE
l Skip the following operations for DPU boards that work in resource pool mode.
l Reset the BSC6900 after changing the board backup mode.
l Verify the network reliability after changing the board backup mode.
For details about how to change the backup mode of the OMU board from independent to active/
standby, see Setting the OMU Working Mode.
After changing the backup mode of an IP interface board to active/standby, manually configure
port IP addresses for the standby board or configure ports in active/standby mode.
If ports that do not work in active/standby mode are used to transmit data, run the
ADDETHIP command to configure port IP addresses for the standby board.
If ports in active/standby mode are used to transmit data, the port IP address of the standby board
is the same as that of the active board. In this case, run the ADD ETHREDPORT command to
configure ports in active/standby mode.
Issue 03 (2015-06-30)
MO
Setting Notes
Data Source
MML Command
BRD
Set Backup to YES(YES).
Internal plan
MOD BRD

33
RAN17.1
Procedure
l
Information Recording Procedure

1.
Run the LST BRD command to query the board information before the
reconfiguration.
Reconfiguration Procedure
1.
Run the SET CFGDATAINEFFECTIVE command to set the configuration mode

of all subracks to ineffective mode.
2.
Run the MOD BRD command to change the board backup mode to active/standby.
3.
Run the SET CFGDATAEFFECTIVE command to set the configuration mode of

all subracks to effective mode.
4.
Run the FMT DATA command to generate a data configuration file.
5.
Run the RST BSC command to reset the BSC6900.
----End
Example
//Recording board information before the reconfiguration
LST BRD:;
//Setting the configuration mode of subrack 1 to ineffective mode
SET CFGDATAINEFFECTIVE: SRN=1;
//Changing the backup mode of the board in slot 14 of subrack 1
MOD BRD: BRDCLASS=INT, SRN=1, SN=14, RED=YES;
//Adding two Ethernet ports working in active/standby mode
ADD ETHREDPORT: SRN=1, SN=14, PN=1;
//Setting the configuration mode of all subracks to effective mode
SET CFGDATAEFFECTIVE:;
//Generating a data configuration file
FMT DATA: SRN=1, WORKAREA=Active;
//Resetting the BSC
RST BSC: OT=BYBSCID, BSCID=1;
Follow-up Procedure
l
Verification
For the detailed verification procedure, see Verifying Network Reliability.
Rollback
The board backup mode rollback from active/standby to independent is not supported.
Issue 03 (2015-06-30)

34
RAN17.1
6.3 Adjusting OMU Slots

This section describes how to adjust the slots that accommodate the operation and maintenance
units (OMUs).
Prerequisites
l
Before adjusting the OMU slots that accommodate the OMUs, collect information listed
in Table 6-5.
Information
Description
OMU Slots
Query and record the slots that

accommodate the OMUs.
The target slots are idle. For details about the OMU slot information, see OMUa Board.
None
License requirement
None
Context
MO
Setting Notes
Data
Source
MML
Command
BRD
Set Slot No. to an appropriate value.
Internal plan
ADD BRD
Procedure
Step 1 Run the DSP OMU command to query the numbers of the slots that accommodate the active
and standby OMUs before the reconfiguration.
Step 2 Perform the operations listed in the following table based on the operating system of the OMU.
Issue 03 (2015-06-30)

35
RAN17.1
If...
Then...
The Dopra Linux operating system is used
1. Log in to the active and standby OMUs

separately.
2. Run the /etc/rc.d/omud stop command to
stop the omud process.
3. Run the poweroff command to power off
the OMU.
The Windows operating system is used
1. Log in to the active and standby OMUs

separately.
2. Choose Start > Run. In the Run dialog
box, type cmd, and press Enter. The
OMU command input dialog box is
displayed.
3. In the command line, type the net stop
omud command to stop the omud process.
4. Choose Start > Shutdown. In the
displayed dialog box, select Shutdown to
shut down the OMU.
Step 3 When the OFFLINE indicator on the OMU board panel is on, remove the active and standby
OMUs.
Step 4 Insert the active and standby OMUs into the target slots.
Step 5 After five minutes, run the DSP OMU command to check whether the active and standby OMUs
operate properly. If not, check whether the OMUs are installed correctly.
Step 6 Run the RMV BRD command to remove the OMU boards that have been configured.
Step 7 Run the ADD BRD command to add active and standby OMU boards separately. In this step,
set Slot No. to an appropriate value.
Step 8 Log in to the LMT to check whether the OMU status displayed on the device panel is correct.
Step 9 On the LMT, click Alarm, and select Browse Alarm to view current active alarms.
Step 10 Optional: If an OMU-related alarm is displayed in the list of active alarms and the OMU slot
number is the original one, right-click the alarm, and choose Clear Alarm from the shortcut
menu to manually clear the alarm.
----End
Example
//Querying the numbers of the subracks and slots where the active and standby OMUs
reside before the slot adjustment
DSP OMU:;
Issue 03 (2015-06-30)

36
RAN17.1
//Removing a board
RMV BRD: SRN=0, SN=16;
//Adding boards
ADD BRD: SRN=0, BRDCLASS=OMU, BRDTYPE=OMUa, SN=24;
ADD BRD: SRN=0, BRDCLASS=OMU, BRDTYPE=OMUa, SN=26;
Follow-up Procedure
l
Verification
Run the DSP OMU command to check whether the active and standby OMUs operate
properly.
Expected result: The active and standby OMUs operate properly.
Rollback
The rollback procedure is similar to the reconfiguration procedure, except that parameters
in the rollback procedure are set to values used before the reconfiguration.
6.4 Changing Optical Fibers from Direct Connection to YShaped Connection

To improve transmission reliability of optical interface boards, you can install optical splitters/
combiners. This section describes how to change optical fibers of optical interface boards from
direct connection to Y-shaped connection.
Prerequisites
l
Before changing the connection, collect information listed in Table 6-7.

Information
Description
Board information
Query and record the model and

installation position of interface boards,
and the number of the optical interface.
The optical splitters/combiners are ready.
If an optical interface board works in independent mode, another optical interface board
of the same type must be installed so that the two optical interface boards can work in
active/standby mode.
None
License requirement
None
Issue 03 (2015-06-30)

37
RAN17.1
Context
Before the reconnection, the BSC6900 interface boards and peer optical transmission equipment
work in independent mode. Figure 6-2 illustrates the optical fiber connections between an
interface board and the peer equipment.
Figure 6-2 Connections of optical fibers for optical interface boards working in independent
mode
After the reconnection, the BSC6900 interface boards work in active/standby mode, but the peer
optical transmission equipment still works in independent mode. Figure 6-3 illustrates the
connections between an interface board and the peer equipment through optical splitters/
combiners.
Figure 6-3 Installation positions of optical splitters/combiners
Issue 03 (2015-06-30)

38
RAN17.1
NOTICE
Installing an optical splitter/combiner interrupts ongoing services on the relevant interface board.
Therefore, perform this operation when the traffic is light, for example, during early morning
hours.
Only the AOUa, UOIa, AOUc, POUc, and UOIc boards can be connected to an optical splitter/
combiner.
An automatic switchover between active and standby optical ports cannot be triggered even if
an optical splitter/combiner is used in the following scenarios:
l The active and standby optical ports on a BSC6900 interface board are operating properly.
When the transmission on the TX optical fiber for the active optical port is interrupted, the
BSC6900 reports ALM-21253 SDH/SONET MS Remote Defect Indication for the active
and standby optical ports.
When the transmission is interrupted on the optical fiber between the optical splitter/
combiner and the TX port on the peer equipment, the BSC6900 reports ALM-21253 SDH/
SONET MS Remote Defect Indication for the active and standby optical ports.
When the transmission is interrupted on the optical fiber between the optical splitter/
combiner and the RX port on the peer equipment, the BSC6900 reports ALM-21252 SDH/
SONET Loss of Signal for the active and standby optical ports.
MO
Setting Notes
Data Source
MML Command
MSP
Set Backup mode to MODE4(Y

Line).
Internal plan
SET MSP
Procedure
Step 1 Run the LST BRD command to query and record the board backup mode.
If...
Then...
Backup is Yes Go to Step 2.

Backup is No 1. Configure the interface board to work in active/standby mode by referring
to 6.2 Changing the Board Backup Mode from Independent to Active/
Standby.
2. Go to Step 2.
Step 2 Run the LST MSP command to query and record the MSP backup mode.
Issue 03 (2015-06-30)

39
RAN17.1
If...
Then...
Backup mode is MODE4(Y Line)
Go to Step 3.
Backup mode is a value other than

MODE4(Y Line)
1. Run the SET MSP command with Backup

mode to MODE4(Y Line).
2. Go to Step 3.
Step 3 Install the optical splitter/combiner by referring to the procedure in Installing the Optical Splitter/
Combiner.
NOTICE
Connect the TX and RX ends of each optical splitter/combiner correctly. Otherwise, the optical
signals cannot be received or sent.
Step 4 Replace the temporary labels on the new optical splitter/combiner with engineering labels. For
details, see Attaching the Engineering Labels to the Signal Cables.
Step 5 Bind the optical splitters/combiners.
Step 6 Check the items listed in Table 6-9 one by one.
Table 6-9 Checklist for replacing an optical splitter/combiner
Item
Result
Action
Connection of the
optical fiber is
correct.
Yes
Check the next item.
No
Disconnect the optical fiber and reconnect it.
Optical connectors
are firmly
connected.
Yes
Check the next item.
No
Secure the optical connectors.
Yes
No further action is required.
No
Clear the alarms by referring to the alarm online

help on the LMT. If the alarms persist, contact
Huawei for technical support.
Alarms related to the

transmission cable
are cleared.
----End
Example
//Checking the backup mode of a board
LST BRD: SRN=0, SN=24;
Issue 03 (2015-06-30)

40
RAN17.1
//Checking the backup mode of an MSP

LST MSP: SRN=0, SN=24, PN=0;
//Setting the backup mode of an MSP to mode 4.
SET MSP: SRN=0, SN=24, PN=0, MODE=MODE4;
/*Rollback Procedure*/
//Setting the backup mode of an MSP to mode 2.
SET MSP: SRN=0, SN=24, PN=0, MODE=MODE2;
Follow-up Procedure
l
Verification
For the detailed verification procedure, see Verifying Network Reliability.
Rollback
1.
Run the SET MSP command with Backup mode set based on the network plan.
2.
Remove the optical splitters/combiners.
3.
Install optical fibers.
6.5 Install a Built-in NE

This section describes how to install a built-in NE.
Procedure
l
Issue 03 (2015-06-30)
U2000 Based
1.
Choose Software > Software Browser on the U2000. A window is displayed. Expand
the Server node on the OSS Server tab page in the left navigation tree. Then, select
the host NE node.
2.
On the Built-in NE Software tab page, click "Transfer", and choose "From OSS Client
to OSS Server" to uploading the installation package to the U2000 server.

41
RAN17.1
Issue 03 (2015-06-30)
3.
On the Built-in NE Software tab page, click "Transfer", and choose "From OSS
Server to NE" to upload the installation package to the host NEs.
4.
Click "Install" to install the built-in NE software. Download the upgrade tool to the
local computer. If the upgrade tool is already locally available, skip the download
operation.
5.
Click "OK", and the Select NE is displayed. Click "OK", and the following dialog
box is displayed.
6.
Click "OK" and double-click the NE in the NE List.

42
RAN17.1
Issue 03 (2015-06-30)
7.
Enter the account and the password of Admin User, and select the secure transmission
type. Click "Next".
8.
Confirm the version information, and select the "Direct Install" mode. Click "Next".
9.
Enter the built-in NE information, and click "Install".

43
RAN17.1
10. Finish the install.
Remote-Client Based
NOTE
The remote client of the ECO6910 is used in the following operations.

The following operations for installing built-in NEs are implemented on the BSC6900.
Issue 03 (2015-06-30)
1.
Add the BSC6900 NE, and double-click the NE in the NE List.
2.
Enter the account and the password of BSC6900 Admin User, and then select the
"uninstall a built-in NE" operation and the secure transmission type. Click "Next".

44
RAN17.1
Issue 03 (2015-06-30)
3.
Confirm the version information, and select the "New Installation" mode. Click
"Next".
4.
Enter the built-in NE information and upload the installation package files. Click
"Install".

45
RAN17.1
5.
Finish the install.
----End
Follow-up Procedure
The password of built-in ECO6910 admin is software@com by default.
6.6 Uninstall a Built-in NE

This section describes how to remove a built-in ECO6910.
Procedure
l
U2000 Based
1.
Issue 03 (2015-06-30)
Choose Software > Software Browser on the U2000. A window is displayed. Expand
the Server node on the OSS Server tab page in the left navigation tree. Then, select
the host NE node.
46
RAN17.1
Issue 03 (2015-06-30)
2.
Click the NE in the Install, and select the "Uninstall".
3.
Click "OK", and the following dialog box is displayed.

47
RAN17.1
Issue 03 (2015-06-30)
4.
Click "OK" and double-click the NE in the NE List.
5.
Enter the account and the password of Admin User, and select the secure transmission
type. Click "Next".
6.
Select the target built-in NE which will be uninstalled, and click "Uninstall".

48
RAN17.1
7.
Issue 03 (2015-06-30)
Finish the uninstall.

49
RAN17.1
Remote-Client Based
NOTE
The remote client of the ECO6910 is used in the following operations.

The following operations for removing built-in NEs are implemented on the BSC6900.
Issue 03 (2015-06-30)
1.
Add the BSC6900 NE.
2.
Double-click the NE in the NE List. Enter the account and the password of
BSC6900 Admin User, and then select the "uninstall a built-in NE" operation and the
secure transmission type. Click "Next".

50
RAN17.1
Issue 03 (2015-06-30)
3.
Select the target built-in NE which will be uninstalled, and click "Uninstall".
4.
Finish the uninstall.

51
RAN17.1
----End
6.7 Adding a Board or a Subrack

As the traffic volume increases, the existing boards and subracks may not meet the increasing
service requirements. In this case, you can add boards or subracks to expand system capacity.
6.7.1 Adding a Subrack

This section describes how to add a subrack.
Prerequisites
l
Before adding a subrack, collect information listed in Table 6-10.

Information
Description
Cabinet and Subracks
Query and record the numbers of cabinet

and subracks that have been installed.
Query and record the number of the
subrack to be added.
The new subrack has been installed in the target cabinet. For details about the installation
procedure, see Installing a Subrack.
None
Issue 03 (2015-06-30)

52
RAN17.1
License requirement
None
Context
NOTE
The BSC6900 supports only PARC subrack. The PARCb subrack cannot be installed in the BSC6900.
Before adding a subrack, ensure that clock cables have been connected properly. Otherwise, services allocated
to the added subrack will become abnormal if the subrack cannot obtain clock signals.

MO
Setting Notes
Data
Source
MML
Command
SUBRACK
Set Subrack No. and Subrack name to

the target values.
Internal plan
ADD
SUBRACK
Procedure
Step 1 Run the LST SUBRACK command to query the number of a subrack.
Step 2 Run the ADD SUBRACK command to add a subrack.
Step 3 Configure boards.
Choose either of the following two methods to add boards. The second method takes less time
than the first one but requires a configuration script.
l Single command mode
1.
Run the ADD BRD command to add a board.
l Batch processing mode

1.
On the LMT, click Batch. The Batch tab page is displayed.
2.
Click New and enter the batch commands in the editing area, or click Open... to select
the pre-edited batch file.
3.
Click Set... to set the parameters for running the MML commands.
4.
Click Go to enable the system to start executing the commands one by one.
NOTE
You can select Execution Type and use Prompt when Error Occurs (which is selected by
default).
Step 4 Run the SET SCUPORT command to simultaneously enable the ports for inter-subrack
interconnection on the SCU panels in the new subrack and the subrack that is directly connected
to the new subrack.
NOTE
Disable the ports not used on the SCU board and ensure inter-subrack cables are not connected to these ports.
Issue 03 (2015-06-30)

53
RAN17.1
Step 5 Run the SET CFGDATAEFFECTIVE command to set the configuration mode of the new
subrack to effective mode.
Step 6 Run the SET LODCTRL command with Board Start Load Control set to LFB(Load from
OMU and write flash).
Step 7 Run the FMT DATA command to generate configuration data files for all subracks.
Step 8 If the newly added subrack is not powered on, turn on the power switch of the subrack.
Step 9 On the LMT, choose Device Maintenance to check the board status. Ten minutes later, all the
boards in the subrack are loaded, and the subrack begins to work properly. Observe the status
of each board in the Device Maintenance window.
Step 10 On the Browse Alarm tab page on the LMT, check whether alarms related to board faults are
reported.
If...
Then...
Alarms related to board faults are

reported
1. Analyze and clear the alarms according to the

alarm help information.
2. Go to Step 10.
No alarms related to board faults are

reported
Go to Step 11.
NOTE
For a newly added subrack that is not configured with any BTSs, the BSC allocates some services to the
subrack based on the load sharing algorithm. Therefore, if an alarm is reported by any board in the subrack,
you must clear the alarm in a timely manner. Otherwise, services will be negatively affected.
Step 11 Run the CMP BRDVERCheck whether the software version of the board in the newly added
subrack is consistent with the host software.
If...
Then...
The values are consistent.
Go to Step 12.
The values are inconsistent.
1. Run the RST BRD command to reset the board.

2. Go to Step 11.
NOTE
You can obtain the correct board version mapping table from Release Notes.
Step 12 Run the SET LODCTRL command with Board Start Load Control set to CL(Consult
Load).
----End
Example
Issue 03 (2015-06-30)

54
RAN17.1
//Querying the numbers of configured subracks

LST SUBRACK:;
//Adding a subrack
ADD SUBRACK: SRN=2, SRName="2";
//Enabling a port on the SCU board in the new subrack
SET SCUPORT: SRN=2, SN=6, PN=8, Switch=OPEN;
//Setting the configuration mode of a subrack to effective mode
SET CFGDATAEFFECTIVE: SRN=21;
//Configuring the Board Start Load Control parameter
SET LODCTRL: LODCTRL=LFB;
//Generating a data configuration file
FMT DATA:;
//Configuring the Board Start Load Control parameter
SET LODCTRL: LODCTRL=CL;
Follow-up Procedure
l
Verification
Log in to the LMT to check the subrack status on the device panel.
Expected result: The subrack status is normal.
Rollback
For the detailed rollback procedure, see 6.8.1 Removing a Subrack.
6.7.2 Adding an SPUa, SPUb, or SPUc Board

This section describes how to add an SPUa, SPUb, or SPUc board.
Prerequisites
l
Network design has been complete.

Network design involves planning of the following items: traffic carried by each subrack,
quantity of BTSs carried by an SPUa, SPUb, or SPUc board, and slots housing the boards
Contact Huawei to obtain the detailed network design scheme.
Before adding a board, collect information listed in Table 6-12.

Information
Description
Board information
Query and record the quantity, logical

functions, and installation positions of
SPUa, SPUb, or SPUc boards.
The SPUa, SPUb, or SPUc board has been installed in the target slot. For details about
the installation procedure, see Installing a board.
None
l
Issue 03 (2015-06-30)
License requirement
55
RAN17.1
None
Context
For details about how to bind the MPU subsystem to each type of board, see ADD BRD.
NOTICE
When the board types bound to the MPU subsystem are not complete or when the proportion of
the boards is inappropriate, the number of exchange messages between MPU subsystems surges,
which adversely affects system stability.
MO
Setting Notes
Data Source
MML Command
BRD
Configure the board

based on the plan.
Internal plan
ADD BRD
Procedure
l
Using MML commands

1.
Run the ADD BRD command to add an SPUa, SPUb, or SPUc board.
NOTE
When the subrack is in the effective state, the board added by running this command immediately
starts software loading and internal configuration. During internal configuration of the board, you
cannot run any other configuration-type command. To query the value of Executing inner
configuration or not, run the DSP BRD command.
2.
3.
Issue 03 (2015-06-30)
On the LMT, choose Device Maintenance to check the board status. If the board
status is Normal (the board is green), run the DSP BRD command to query the CPU
status of the added board.
If...
Then...
The value of CPU status is Active

normal
Go to Step 4.
Others
Go to Step 3.
On the Browse Alarm tab page on the LMT, check whether alarms related to board
faults are reported.

56
RAN17.1
If...
Then...

reported
1. Analyze and clear the alarm

according to the alarm help
information.
2. Go to Step 3.

reported
4.
5.
Go to Step 4.
Run the CMP BRDVER command to check whether the software version of the new
board is consistent with the host software version.
If...
Then...
The software version of the new board

is not consistent with the host software
version
1. Run the RST BRD command to reset

the board.

is consistent with the host software
version
The board is successfully added.
2. Go to Step 4.
Configure the new board by referring to the procedure in Configuring the Cell Data.
If a NodeB needs to be reparented from an SPUa, SPUb, or SPUc board to the new
board, perform the reparenting by referring to section "Reparenting UMTS NodeBs"
in WRAN Reconfiguration Guide (CME-Based).
Visit http://support.huawei.com to download the WRAN Reconfiguration Guide
(CME-Based).

1.
In the navigation tree in the left pane of the planned data area, right-click a BSC and
choose Device Panel from the shortcut menu. The device panel of the BSC is displayed
in the right pane.
2.
Based on the planned data, right-click the required slot and choose XPU > Add
XXX from the shortcut menu. A dialog box is displayed for you to configure attributes.
3.
In the dialog box, type the planned board information and click OK. The board
configuration is complete.
----End
Example
No information needs to be recorded before a board is added.
Issue 03 (2015-06-30)

57
RAN17.1
//Adding a board
ADD BRD: SRN=0, BRDCLASS=XPU, BRDTYPE=SPUb, LGCAPPTYPE=UCP, SN=4, MPUSUBRACK=0,
MPUSLOT=0;
//Checking whether the software version of the new board is consistent with the
host software version
CMP BRDVER: SRN=0;
//Querying board status
DSP BRD: SRN=0, SN=4;
Follow-up Procedure
l
Verification
None
Rollback
Using MML commands
For the detailed rollback procedure, see 6.8.2 Removing an SPUa/SPUb/SPUc Board
(UCP/RUCP).
1.
2.
3.
6.7.3 Adding a DPUb/DPUe/DEUa Board

This section describes how to add a DPUb/DPUe/DEUa board.
Prerequisites
l
Before adding a DPUb/DPUe/DEUa board, collect information listed in Table 6-14.

Information
Description
Board information
Query and record the quantity and

installation positions of the boards.
The DPUb/DPUe/DEUa is installed by referring to the procedure in Installing a board.
None
License requirement
None
Issue 03 (2015-06-30)

58
RAN17.1
Context
NOTICE
l To avoid damage to the boards, ASIC chips, or other electronic components, wear an ESD
wrist strap properly. Ensure that the ESD wrist strap is properly connected to the ESD
connector on the cabinet. If no ESD wrist strap or no proper grounding point is available,
wear ESD gloves.
l It is recommended that you need to use the same board type to replace the old board. To use
a board of the different version to replace the board (for example, use a board of version a
to replace a board of version b), contact Huawei for technical support.
NOTICE
l Configure the DPU boards one by one.
l The type of the configured board must be the same as that of the installed board. For example,
if you configure a DPUe in a slot, you must install a DPUe in this slot.
MO
Setting Notes
Data Source
MML Command
BRD
Configure the board

based on the plan.
Internal plan
ADD BRD
Procedure
l
Using MML commands

1.

NOTE
Issue 03 (2015-06-30)
2.
Run the INH BRD command to logically inhibit a board
3.
Install the board by referring to the procedure in Installing a board.
4.
After five minutes, run the DSP DSP command to query the status of a DSP chip on
the board.
5.
When all DSP chips on the DPUb/DPUe/DEUa board enter the Disable state, run the
UIN BRD command to uninhibit the board.
59
RAN17.1
6.
7.
If...
Then...
Status is NORMAL
Go to Step 8.
Status is a value other than NORMAL
Go to Step 7.
If...
Then...

reported
Go to Step 8.

reported
1. Analyze and clear the alarms

information.
2. Go to Step 6.
8.
9.
If...
Then...
DSP patch state is Normal
Go to Step 9.
DSP patch state is a value other than

Normal
Go to Step 7.
If...
Then...

version

the board.

version
2. Go to Step 7.

1.
Issue 03 (2015-06-30)
Run the DSP DSP command to query the status of a DSP chip on the DPU board.
in the right pane.

60
RAN17.1
2.
Based on the planned data, right-click the required slot and choose DPU > Add
3.
----End
Example
//Adding a board
ADD BRD: SRN=0, BRDCLASS=DPU, BRDTYPE=DPUe, SN=10, MPUSUBRACK=0, MPUSLOT=0;
//Logically inhibiting a board

INH BRD: INHT=LOGIC, SRN=0, SN=10;
//Querying the status of a DSP chip
DSP DSP: SRN=0, SN=10;
//Uninhibiting a board
UIN BRD: UINT=LOGIC, SRN=0, SN=10;
//Querying the status of a DSP chip
DSP DSP: SRN=0, SN=10;
CMP BRDVER: SRN=0;
Follow-up Procedure
l
Verification
None
Rollback
Using MML commands
For the detailed rollback procedure, see 6.8.3 Removing a DPUb/DPUe/DEUa
Board.
1.
2.
3.
6.7.4 Adding an ASUa Board

This section describes how to add an ASUa board.
Issue 03 (2015-06-30)

61
RAN17.1
Prerequisites
l
Before adding an ASUa board, collect information listed in Table 6-16.

Information
Description
Board information
Query and record the quantity, logical

functions, and installation positions of
boards.
The ASUa board has been installed in the target slot. For details about the installation
procedure, see Installing a board.
None
License requirement
None
Context
NOTICE
l To avoid damage to the boards, ASIC chips, or other electronic components, wear an ESD
wrist strap properly. Ensure that the ESD wrist strap is properly connected to the ESD
connector on the cabinet. If no ESD wrist strap or no proper grounding point is available,
wear ESD gloves.
l It is recommended that you need to use the same board type to replace the old board. To use
a board of the different version to replace the board (for example, use a board of version a
to replace a board of version b), contact Huawei for technical support.
NOTICE
l Configure the ASUa boards one by one.
l The type of the configured board must be the same as that of the installed board. For example,
if you configure an ASUa in a slot, you must install an ASUa in this slot.
Issue 03 (2015-06-30)

62
RAN17.1

MO
Setting Notes
Data Source
MML Command
BRD
Configure the board

based on the plan.
Internal plan
ADD BRD
Procedure
l
Using MML commands

1.

NOTE
2.
Install the board by referring to the procedure in Installing a board.
3.
4.
If...
Then...
Status is NORMAL
Go to Step 5.
Status is a value other than NORMAL
Go to Step 4.
If...
Then...

reported
Go to Step 5.

reported

information.
2. Go to Step 3.
5.
Issue 03 (2015-06-30)
If...
Then...

version

the board.
2. Go to Step 3.

63
RAN17.1
If...
Then...

version

1.
in the right pane.
2.
Based on the planned data, right-click the required slot and choose ASU > Add
3.
----End
Example
//Adding a board
ADD BRD: BRDCLASS=ASU, BRDTYPE=ASUa, LGCAPPTYPE=GASP, SN=20;
//Querying the status of the board
Follow-up Procedure
l
Verification
None
Rollback
Using MML commands
For the detailed rollback procedure, see 6.8.4 Removing an ASUa Board.
1.
2.
3.
Issue 03 (2015-06-30)

64
RAN17.1
6.7.5 Adding an Interface Board

This section describes how to add an interface board.
Prerequisites
l
Before adding an interface board, collect information listed in Table 6-18.

Information
Description
Board information
Query and record the model, quantity,

installation position, and backup mode of
interface boards.
The interface board and cables have been installed.
None
License requirement
None
Context
If a new interface board uses E1/T1 transmission or channelized STM-1 transmission over
optical ports, the dual in-line package (DIP) switches on the board must be configured. For
details about how to configure the DIP switches, see DIP Switches on Components.
Run the LST CFGMODE command to query the configuration mode of the subrack.
l
If configuration mode of a subrack is set to effective mode, adding an interface board

does not affect ongoing services.
If configuration mode of a subrack is set to ineffective mode, adding a board requires

resetting the base station controller.

MO
Setting Notes
Data Source
MML Command
BRD
Configure the board

based on the plan.
Internal plan
ADD BRD
Procedure
l
Using MML commands

1.
Issue 03 (2015-06-30)
Run the ADD BRD command to add an interface board.

65
RAN17.1
Configure the transmission data by referring to the procedure in Configuring the

Interfaces.
NOTE
2.
3.
If...
Then...
CPU status is Normal
Go to Step 6.
CPU status is a value other than

Normal
Go to Step 3.
If...
Then...

reported
Go to Step 6.

reported

information.
2. Go to Step 2.
4.
Check the status of ports on an interface board by board type. For example, if the
added board is an FG2c board, run DSP ETHPORT to check the port status.
5.
Check the status of the transmission link based on the board type and configured
transmission mode.
For example, if the added board is an AOUc board using ATM IMA transmission, run
the DSP IMAGRP and DSP SAALLNK commands to check the IMA group status
and SAALLNK status.
6.
Issue 03 (2015-06-30)
If...
Then...

version

the board.

version
2. Go to Step 2.

66
RAN17.1

1.
in the right pane.
2.
Based on the planned data, right-click the required slot and choose INT > Add
Interface Board Type from the shortcut menu. A dialog box is displayed for you to
configure attributes.
3.
----End
Example
//Adding an interface board
ADD BRD: SRN=1, BRDCLASS=INT, BRDTYPE=FG2c, SN=26, RED=YES, MPUSUBRACK=1,
MPUSLOT=0;
CMP BRDVER: SRN=1;
Follow-up Procedure
l
Verification
None
Rollback
Using MML commands
For the detailed rollback procedure, see 6.8.5 Removing an Interface Board.
1.
2.
3.
6.7.6 Adding an NIU Board

This section describes how to add an NIU board and related precautions.
Issue 03 (2015-06-30)

67
RAN17.1
Prerequisites
l
Before adding an NIU board, collect the information described in Table 6-20.
Required Information
Description
Board information
Board quantity, logical function types,

installation slots
The NIU board has been installed in the target slot. For details about how to install an
NIU board, see Installing a board.
None
License requirement
None
Context
Prepare data according to the following table.
Table 6-21 Data Preparation
MO
Setting Notes
Data Source
MML Command
BRD
Configure this MO
based on the data plan.
Internal plan
ADD BRD
Procedure
l
Using MML commands

1.
Run the ADD BRD command to add an NIU board.

NOTE
2.
Issue 03 (2015-06-30)
On the Device Maintenance tab page on the LMT, check the board status. When the
board status changes to Normal (board becomes green), run the DSP BRD command
to check the status of the board you have added.
If...
Then...
The value of CPU status is Active

normal
Go to Step 4.

68
RAN17.1
3.
If...
Then...
Others
Go to Step 3.
If...
Then...

reported
Go to Step 4.

reported
1. Analyze and clear the alarms based

on the alarm help information.
2. Go to Step 2.
4.
Run the CMP BRDVER command to check whether the software version of the newly
added board is consistent with the host software.
If...
Then...
The values are inconsistent.

the board.
2. Go to Step 2.
The values are consistent.
Adding an NIU board is complete.

1.
in the right pane.
2.
Based on the planned data, right-click the required slot and choose NIU > Add
NIUa from the shortcut menu. The attribute dialog box is displayed.
3.
----End
Example
/*Information Recording*/
You do not need to record any information before adding a board.
//Adding a board
ADD BRD: SRN=0, BRDCLASS=NIU, BRDTYPE=NIUa, SN=10, MPUSUBRACK=0,
MPUSLOT=0;
//Checking whether the software version of the new board matches the board
Issue 03 (2015-06-30)

69
RAN17.1
version mapping
CMP BRDVER: SRN=0;
//Checking board status
Follow-up Procedure
l
Verification
None
Rollback
Using MML commands
See 6.8.6 Removing an NIU Board.
1.
2.
3.
6.8 Removing a Board or a Subrack

Removing a board interrupts services on the board. Therefore, remove the board when the traffic
is light, for example, during early morning hours.
6.8.1 Removing a Subrack

This section describes how to remove a subrack.
Prerequisites
l
Before removing a subrack, collect information listed in Table 6-22.

Information
Description
Cabinet and subrack information
Query and record the No. of the installed

subrack and cabinet and the subrack to be
removed.
None
l
Issue 03 (2015-06-30)
70
RAN17.1
None
l
License requirement
None
Context
MO
Setting Notes
Data Source
MML Command
SUBRACK
Remove the target

subrack.
BSC internal
plan
RMV SUBRACK
NOTICE
Removing a subrack interrupts services on the subrack. To remove a subrack, perform the
following steps. You must remove all boards (except SCU boards) in a subrack before removing
the subrack. Otherwise, services in other subracks will also be negatively affected.
Procedure
Step 1 Based on the network design, reparent the BTS carried on the subrack to be removed to the target
subrack by referring to the procedure in WRAN Reconfiguration Guide (CME-Based).
Visit http://support.huawei.com to download WRAN Reconfiguration Guide (CME-Based).
Step 2 Run the RMV BRD command to remove the SPUa/SPUb/SPUc board whose logical function
is UCP. For the detailed procedure, see 6.8.2 Removing an SPUa/SPUb/SPUc Board (UCP/
RUCP).
Step 3 Remove the interface board.
Step 4 Remove the DPU.
Step 5 Run the RMV BRD command to remove the SPUa/SPUb/SPUc board whose logical function
is RUCP.
Step 6 Run the RMV SUBRACK command to remove the subrack.
Step 7 Run the SET SCUPORT to disable the port on the SCU in the subrack whose connection is
removed.
----End
Example
Issue 03 (2015-06-30)

71
RAN17.1
//Querying a board
LST BRD: SRN=1;
//Querying a subrack
LST SUBRACK: SRN=1;
//Removing a subrack
RMV SUBRACK: SRN=1;
//Disabling the port on the SCU
SET SCUPORT: SRN=1, SN=6, PN=8, Switch=CLOSE;
Follow-up Procedure
For details about how to remove the subrack hardware connection and subracks, see Site
Maintenance Guide. If the subrack to remove is connected to other subracks, you need to
reconnect these subracks to subracks that are not to be removed.
l
Verification
None
Rollback
For the detailed rollback procedure, see 6.7.1 Adding a Subrack.
6.8.2 Removing an SPUa/SPUb/SPUc Board (UCP/RUCP)

This section describes how to remove an SPUa, SPUb, or SPUc board whose logical function
type is UCP or RUCP. It also describes related precautions.
Prerequisites
l
Before removing an SPUa/SPUb/SPUc board (UCP/RUCP), collect information listed in

Table 6-24.
Information
Description
Board information

installation positions (slot No.) of boards.
None
None
License requirement
None
Context
The logical function type of an SPUa, SPUb, or SPUc board can be RUCP or UCP. RUCP
represents Resource Management and UMTS RNC Control plane Process, and UCP represents
UMTS RNC Control plane Process.
Issue 03 (2015-06-30)

72
RAN17.1
NOTE
l Subsystem 0 of an SPUa, SPUb, or SPUc board whose logical function type is RUCP is the main processing
unit (MPU). The MPU manages other boards (XPU, DPU, interface boards) in the subrack.
l An SPUa, SPUb, or SPUc board whose logical function type is UCP does not have an MPU. All its
subsystems are CPUS subsystems. The board whose logical function type is UCP carries only the BTS and
transmission links.
l To remove an SPUa, SPUb, or SPUc board and then add a new SPUa, SPUb, or SPUc board, use MML
commands.
To check the logical function type of a board, run the LST BRD command. The command output
displays the board logical function type.
In terms of logical functions, SPUa/SPUb/SPUc boards can be categorized as Resource
Management and UMTS RNC Control plane Process (RUCP) boards and UMTS RNC Control
plane Process (UCP) boards.
NOTICE
l Removing the SPUa/SPUb/SPUc board interrupts cell services and transmission links. Do
not remove the SPUa/SPUb/SPUc board unless otherwise specified.
l If you need to remove an SPUa, SPUb, or SPUc board in special scenarios, remove only the
board whose logical function type is UCP.
l You are not allowed to remove any SPUa, SPUb, or SPUc board whose logical function type
is RUCP.
MO
Setting Notes
Data Source
MML Command
BRD
Remove the board.
Internal plan
RMV BRD
Table 6-26 Impact and handling suggestions
Issue 03 (2015-06-30)
Configuration Objects of
the Board to Be Removed
Impact on Services
Operations
NodeB
Services on the NodeB are

interrupted.
Reparent the NodeB to other

boards using the CME.

73
RAN17.1
Impact on Services
Operations
MTP3 link, SAAL link,

M3UA link, and SCTP link
l If all links in the

transmission link set are
configured on the board to
be removed, the
transmission links are
interrupted.
1. Check and remove the

transmission links on the
board to be removed.
l If all links in the

transmission link set are
configured not only on the
board to be removed but
also on other boards, the
transmission links can
still work but their
capacities decrease.
IUR common SCCP
connection
None
2. Establish new
transmission links on
other SPUa/SPUb/SPUc
boards.
1. Run the LST

UIURCOMMSCCP
command to check
whether the board to be
removed is configured
with IUR Common
SCCP Connection.
2. If the board to be removed
has been configured with
IUR Common SCCP
Connection, run the
MOD
UIURCOMMSCCP
command to configure
IUR Common SCCP
Connection to other
SPUa/SPUb/SPUc
boards.
If the board to be removed
is not configured with
IUR Common SCCP
Connection, no further
operation is required.
Issue 03 (2015-06-30)

74
RAN17.1
Impact on Services
Operations
CBS RNC IP address
None
1. Run the LST

UCBSADDR command
to check whether the
board to be removed is
configured with CBS
RNC IP Address.
CBS RNC IP Address,
run the MOD
UCBSADDR command
to configure CBS RNC
IP Address to other
SPUa/SPUb/SPUc
boards.
CBS RNC IP Address,
no further operation is
required.
Iur-g connection
None
1. Run the LST

UIURGCONN
command to check
whether the board to be
removed is configured
with Iur-g connection.
Iur-g connection, run the
MOD UIURGCONN
command to configure
Iur-g connection to other
SPUa/SPUb/SPUc
boards.
Iur-g connection, no
further operation is
required.
NOTE
The board that accommodates the MPU subsystem can be removed only if no other board that is bound to the
subsystem exists.
Issue 03 (2015-06-30)

75
RAN17.1
Procedure
l
Using MML commands

1.
Step 1 Back up the system data by referring to the procedure in Backing Up the System
Data.
2.
Record the No. of the single-core slot to be removed to facilitate subsequent check.
3.
Reparent the NodeB carried on the board to be removed to another board according
to the network plan. For details about the procedure, see section "Reparenting
NodeBs" in Reparenting Base Stations.
Visit http://support.huawei.com to download Reparenting NodeBs.
4.
Migrate the MTP3LNK, SAALLNK, and M3LNK on the board to be removed to other
SPUa/SPUb/SPUc boards.
Table 6-27 Migrating transmission links to other SPUa/SPUb/SPUc boards
Transmission
Links on the
Board to Be
Removed
Analysis
Operations
Migrating
Transmission
Links to Other
SPUa/SPUb/
SPUc Boards
MTP3LNK
Search for the

ADD MTP3LNK
command in the
script to obtain the
configuration of
MTP3 links and
SAAL links
carried by the
board to be
removed.
Run the RMV

MTP3LNK
command to
remove an MTP3
link.
Run the ADD

MTP3LNK
command to
migrate the MTP3
link to another
SPUa/SPUb/
SPUc board.
The SCTP link can

be online
migrated, that is, it
does not need to be
removed before
being migrated.
Run the MOD

SAALLNK
command to
migrate the SAAL
link to another
SPUa/SPUb/
SPUc board.
Run the RMV

M3LNK
command to
remove the M3UA
link.
Run the ADD

M3LNK
command to
migrate the M3UA
link to another
SPUa/SPUb/
SPUc board.
SAALLNK
For example, if the

SPUa board to be
removed is located
in slot 2 of subrack
0, search for
SRN=0, SN=2,.
The configuration
of MTP3 links and
SAAL links can be
analyzes based on
the search results.
M3LNK
Issue 03 (2015-06-30)
Search for the

ADD M3LNK
command in the
script to obtain the
configuration of
M3UA links and
SCTP links carried

76
RAN17.1
Transmission
Links on the
Board to Be
Removed
Analysis
Operations
Migrating
Transmission
Links to Other
SPUa/SPUb/
SPUc Boards
SCTPLNK
by the board to be
removed.
The SCTP link can

be on-line
migrated, that is, it
does not need to be
removed before
being migrated.
Run the MOD

SCTPLNK
command to
migrate the SCTP
link to another
SPUa/SPUb/
SPUc board.
For example, if the

SPUa board to be
removed is located
in slot 2 of subrack
0, search for
SRN=0, SN=2,.
The configuration
of M3UA and
SCTP links can be
analyzed based on
search results.
5.
Remove other configuration objects of the board.

Table 6-28 Removing other configuration objects of the board
Configuration Objects
of the Board to Be
Removed
Impact
on
Services
Operations
Iur SCCP connection
None
1. Run the LST UIURCOMMSCCP

command to check whether the board
to be removed is configured with IUR
Common SCCP Connection.
2. If the board to be removed has been
configured with IUR Common SCCP
Connection, run the MOD
UIURCOMMSCCP command to
configure IUR Common SCCP
Connection to other SPUa/SPUb/
SPUc boards.
If the board to be removed is not
configured with IUR Common SCCP
Connection, no further operation is
required.
Issue 03 (2015-06-30)

77
RAN17.1
Configuration Objects
of the Board to Be
Removed
Impact
on
Services
Operations
CBS RNC IP Address
None
1. Run the LST UCBSADDR command

to check whether the board to be
removed is configured with CBS RNC
IP Address.
configured with CBS RNC IP
Address, run the MOD
UCBSADDR command to configure
CBS RNC IP Address to other SPUa/
SPUb/SPUc boards.
configured with CBS RNC IP
Address, no further operation is
required.
Iur-g interface connection
None
1. Run the LST UIURGCONN

command to check whether the board
to be removed is configured with Iurg connection.
configured with Iur-g connection, run
the MOD UIURGCONN command
to configure Iur-g connection to other
SPUa/SPUb/SPUc boards.
configured with Iur-g connection, no
further operation is required.
6.
Run the RMV BRD command to remove the board.
7.
Uninstall the board by referring to the procedure in Removing a Board.
8.
Perform a dialing test to check whether services on the NodeB and transmission links
are recovered.

1.
in the right pane.
2.
Right-click a board you want to delete and choose Delete from the shortcut menu. The
confirmation dialog box is displayed.
3.
Click OK to delete the board.
----End
Example
Issue 03 (2015-06-30)

78
RAN17.1
//Removing a board
Follow-up Procedure
l
Verification
None
Rollback
Using MML commands
For the detailed rollback procedure, see 6.7.2 Adding an SPUa, SPUb, or SPUc
Board.
1.
2.
3.
6.8.3 Removing a DPUb/DPUe/DEUa Board

This section describes how to remove a DPUb/DPUe/DEUa board.
Prerequisites
l
Before removing a DPUb/DPUe/DEUa board, collect information listed in Table 6-29.

Information
Description
Board information

None
None
License requirement
None
Issue 03 (2015-06-30)

79
RAN17.1
Context
NOTICE
Do not remove all DPUb/DPUe boards in a subrack. Reserve at least one DPUb or DPUe board
for service processing.
MO
Setting Notes
Data Source
MML Command
BRD
Remove the board

according to the
network plan.
Internal plan
RMV BRD
Procedure
l
Using MML commands

1.
Run the INH BRD command to logically inhibit the board.
2.
3.
4.
After five minutes, repeat Step 1 to Step 3 for each board to remove multiple boards,

1.
in the right pane.
2.
3.
----End
Example
//Inhibiting a board logically
INH BRD: INHT=LOGIC, SRN=0, SN=10;
//Removing a board
Issue 03 (2015-06-30)

80
RAN17.1
Follow-up Procedure
l
Verification
None
Rollback
Using MML commands
For the detailed rollback procedure, see 6.7.3 Adding a DPUb/DPUe/DEUa Board.
1.
2.
3.
6.8.4 Removing an ASUa Board

This section describes how to remove an ASUa board.
Prerequisites
l
Risk assessment is complete.

Risk assessment: The impact of removing an ASUa board on the built-in network element
(NE) has been assessed. Services provided by the built-in NE on an ASUa board will be
interrupted after you remove the board. Management entities (MEs) deployed on the board
need to be moved to other boards.
Before removing an ASUa board, collect information listed in Table 6-31.

Information
Description
Board information

None
None
License requirement
None
Context
Issue 03 (2015-06-30)

81
RAN17.1

MO
Setting Notes
Data Source
MML Command
BRD
Remove the board

according to the
network plan.
Internal plan
RMV BRD
Assess the impact of removing an ASUa board on the built-in NE before performing this
operation. Table 6-33 describes the detailed impact and handling suggestions.
Table 6-33 Impact of removing an ASUa board on the built-in NE and handling suggestions
Impacted Item
Service Impact
Setting Notes
MML Command
Services provided by
the built-in NE on the
board
All services provided

by the built-in NE on
the board are
interrupted.
Before removing a
board, run the LST
BRDBIND2ME
command to query
the binding between
the ME and the
board. If the board is
bound to the built-in
NE, removing the
board will interrupt
all services provided
by the built-in NE on
the board.
LST
BRDBIND2ME
MEs deployed on the

board
The MEs of the builtin NE need to be

moved to other
boards.
Before removing a
board, run the DSP
ME command to
check whether the
board carries running
MEs. If yes, run the
MOV ME command
to move the MEs to
other boards.
DSP ME
MOV ME
NOTICE
Removing an ASUa board will interrupt services provided by the built-in NE. Therefore, do not
remove an ASUa board unless required.
Procedure
l
Issue 03 (2015-06-30)
Using MML commands

82
RAN17.1
1.
2.
Run the DSP ME command to check whether the board to be removed carries running
MEs.
If...
Then...
The board carries running MEs.
Run the BKP ME command to backup

the MEs. Then, go to Step 2.
The board carries no running MEs.
Go to Step 5.
Log in to the OMU of the built-in NE and check the OMU status of the board to be
removed.
If...
Then...
The OMU works in independent mode.
Go to Step 3.
The OMU is the active OMU in active/

standby mode.
Switch over the active and standby

OMUs. For details, see section
"Forcibly Switching Over the Active
and Standby OMUs" in Built-in
ECO6910 OMU Administration Guide.
Go to Step 5.
The OMU is the standby OMU in active/

standby mode.
Go to Step 5.
3.
Run the MOV ME command and move the MEs to other ASUa boards.
4.
Optional: You do not need to perform this operation if the ME works in dual OMU
server mode and the standby OMU of the ME needs to be moved. Run the RTR
ME command to restore MEs.
5.
On the Web LMT of the built-in NE, check whether the OMU status of the ME is
normal. When the OMU status is normal, go to Step 6.
6.
On the HNE, run the RMV BRD command to remove the boards.
7.
For details about how to remove a board, see Removing a Board.

1.
in the right pane.
2.
3.
----End
Example
//Removing the Management Entity
MOV ME: MEID=1, SRN=0, SN=11, FORCESWAP=NO, DSTSRN=0, DSTSN=15;
Issue 03 (2015-06-30)

83
RAN17.1
//Restoring data and files of the Management Entity

RTR ME: MEID=1;
//Removing a board
Follow-up Procedure
l
Verification
None
Rollback
Using MML commands
For the detailed rollback procedure, see 6.7.4 Adding an ASUa Board.
1.
2.
3.
6.8.5 Removing an Interface Board

This section describes how to remove an interface board.
Prerequisites
l
Before removing an interface board, collect information listed in Table 6-34.

Information
Description
Board information
Query and record the model, quantity, and

installation positions of interface boards.
None
None
License requirement
None
Issue 03 (2015-06-30)

84
RAN17.1
Context
MO
Setting Notes
Data Source
MML Command
BRD
Remove the board from the target

slot.
Internal plan
RMV BRD
NOTICE
Removing an interface board that carries NodeBs to be reparented interrupts services on the
NodeBs.
Procedure
l
Using MML commands

1.
Reparent the NodeB configured on the interface board to be removed and

corresponding transmission cables to the target interface board according to the
network design. For details, see WRAN Reconfiguration Guide (CME-Based).
Visit http://support.huawei.com to download WRAN Reconfiguration Guide (CMEBased).
2.
Remove the configuration objects of the board.

Configuration objects of the board are as follows: AAL2PATH, ABISE1T1, AE1T1,
ATERE1T1, ATMLOGICPORT, BRDE1CON1, BRDE1CON2, CBSADDR,
DEVIP, ETHIP, ETHMD, ETHREDPORT, ETHTRK, FRALNK, ICMPGUARD,
IMAGRP, IPLOGICPORT, IPLOPTST, IPOAPVC, IPPATH, MPGRP, MTP3LNK,
NODEBIP_ATM, NODEBIP_IP, NSE PBE1T1, PPPLNK, RNCCBCPUID,
RSCGRP, RSVRES_BM, RSVRES_TC, SAALLNK SCTPLNK, TSCROSS,
VPCLCX_H, and VPCLCX_L GBE1T1, UNILNK, and VLANID.
3.
4.
5.
Perform a dialing test to check whether services on the NodeB and transmission links
are recovered.

1.
in the right pane.
2.
3.
----End
Issue 03 (2015-06-30)

85
RAN17.1
Example
//Querying a board
//Removing a board
Follow-up Procedure
l
Verification
None
Rollback
Using MML commands
For the detailed rollback procedure, see 6.7.5 Adding an Interface Board.
1.
2.
3.
6.8.6 Removing an NIU Board

This section describes how to remove an NIU board and related precautions.
Prerequisites
l
Before removing an NIU board, collect the information described in Table 6-36.
Required Information
Description
Board information
Board quantity, installation slots
None
None
License requirement
None
Issue 03 (2015-06-30)

86
RAN17.1
Context
NOTICE
To remove an NIU board and then add a new NIU board, use MML commands.
Removing an NIU board may affect the Web Browsing Acceleration, P2P Downloading Rate
Control during Busy Hour, Video Service Rate Adaption, and Radio Awared Video Shaping
features.
Prepare data according to the following table.
Table 6-37 Data Preparation
MO
Setting Notes
Data Source
MML Command
BRD
Configure this MO
Internal plan of
the base station
controller
RMV BRD
Procedure
l
Using MML commands

1.
Uninstall the board by following the procedure described in Removing a Board.
2.
Run the RMV BRD command to remove a board.
3.
Repeat steps 1 and 2 to remove multiple boards.

1.
in the right pane.
2.
3.
----End
Example
//Removing a board
Follow-up Procedure
l
Verification
None
Issue 03 (2015-06-30)

87
RAN17.1
Rollback
Using MML commands
See 6.7.6 Adding an NIU Board.
1.
2.
3.
Issue 03 (2015-06-30)

88
RAN17.1
Reconfiguring the NodeB
About This Chapter

This chapter describes how to reconfigure a running NodeB or expand its capacity.
Issue 03 (2015-06-30)

89
RAN17.1
7.1 Changing the Maintenance Mode of the NodeB

To avoid reporting unnecessary alarms during the reconfiguration, set the maintenance mode of
the NodeB to TESTING. When the reconfiguration is complete, set the maintenance mode of
the NodeB to NORMAL.
Prerequisites
l
Required information
None
The NodeB communicates properly with the U2000.
None
License requirement
None
Context
l
An NE can work in such maintenance modes as NORMAL, INSTALL, EXPAND,

UPGRADE, and TESTING. The maintenance mode of the NodeB is NORMAL when
the NodeB operates properly.
NOTE
For details about maintenance modes, see section "U2000 Feature Description About Maintenance Mode
Management" in U2000 Product Documentation.
The NE maintenance mode is valid only during the period specified by Start Time and
End Time. Before Start Time and after End Time, the NE mode changes to
NORMAL. Alarms are reported normally when the NE works in NORMAL.
When the NE maintenance mode changes to NORMAL, the alarms that are not cleared in
TESTING mode are reported as common alarms to the U2000.
Issue 03 (2015-06-30)

90
RAN17.1
Data Type
MO
Setting Notes
Data Source
MML
Command
Maintenance
mode
Maintenance
Mode of the
BTS
(MNTMODE)
l Before the
reconfigurati
on, set NE
Maintenanc
e Mode to
TESTING
(TESTING)
.
Internal plan
SET
MNTMODE
l When the
reconfigurati
on is
complete, set
NE
Maintenanc
e Mode to
NORMAL
(NORMAL
).
NOTE
l For a co-MPT base station, the maintenance mode can be set only on the entire base station. The maintenance
mode takes effect on the entire base station after being set.
l For a separate-MPT base station, the maintenance mode is set separately for each mode of this base station
and affects only the mode for which it is set.
Procedure
l
The U2000-based procedure is as follows:

1.
On the U2000 client, choose Application Center > Configuration > Settings >
Maintenance Mode (application style) or Maintenance > Maintenance Mode
(traditional style). The Maintenance Mode window is displayed.
2.
Click
at the upper left corner of the Maintenance Mode window. The Set
Maintenance Mode dialog box is displayed.
3.
Select the NEs to be configured in the Set Maintenance Mode dialog box.
Before the reconfiguration, set NE Maintenance Mode to TESTING.
NOTE
Select the performance methods Instant or Time based on requirements. If Time is selected,
set the Start Time and End Time for the NE.
When the reconfiguration is complete, set NE Maintenance Mode to

NORMAL.
4.
l
Using MML commands

1.
Issue 03 (2015-06-30)
Click OK.
Run the NodeB MML command SET MNTMODE.
91
RAN17.1
Before the reconfiguration, run the NodeB MML command SET MNTMODE to
set Maintenance Mode to TESTING(TESTING), and set the Start Time of
Status Setting and End Time of Status Setting for the NE based on requirements.
When the reconfiguration is complete, run the NodeB MML command SET
MNTMODE with Maintenance Mode set to NORMAL(NORMAL).
l

1.
Select a base station in the left pane of the planned data area. The NE object tree is
displayed in the lower part of the left pane, as shown in the following figure:
2.
to
----End
Example
//Setting the maintenance mode to testing
SET MNTMODE: MNTMode=TESTING, ST=2012&10&24&23&05&33,
ET=2012&10&25&23&05&34;
//Setting the maintenance mode to normal
SET MNTMODE: MNTMode=NORMAL;
Issue 03 (2015-06-30)

92
RAN17.1
7.2 Device Data Reconfiguration

This chapter describes how to reconfigure NodeB device data in typical scenarios.
7.2.1 Reconfiguring the NE Information of a NodeB

This section describes how to change the NE name, site location, deployment identifier, and site
name.
Prerequisites
l
Before the reconfiguration, collect information listed in Table 7-1.
Information
Description
NE information
NE information of the NodeB to be

reconfigured, including its NE name, site
location, deployment identifier, and site
name.
Hardware Preparation
N/A
Software Preparation
N/A
License File Preparation

N/A
Application Scenario
The current NE information about a NodeB needs replanning.
Context
Issue 03 (2015-06-30)
Data Type
MO
Setting Notes
Data Source
MML
Command
NE information
NE
Configure the
NE information
according to the
network plan.
Network plan
SET NE

93
RAN17.1
Procedure
l
Using MML commands

1.
Run the NodeB MML command SET NEto set Network Element Name, Site
Location, Deployment Identifier, and Site Name.

Single configuration
1.
Select a base station in the left pane of the planned data area. The NE object tree
is displayed in the lower part of the left pane, as shown in the following figure:
2.
to save configured data.
Batch configuration
1.
On the menu bar of the planned data area, choose UMTS Application > Export
Data > Export Base Station Bulk Configuration Data (CME client mode) or
CME > UMTS Application > Export Data > Export Base Station Bulk
Configuration Data (U2000 client mode). Then, export data from the CME to a
file.
NOTE
On the export wizard, set Export By to Custom MOC.
2.
Issue 03 (2015-06-30)
Open the exported file saved on the local PC and reconfigure data in the file based
on the planned data. After the reconfiguration, save and close the file.
94
RAN17.1
3.
On the menu bar of the planned data area, choose UMTS Application > Import
Data > Import Base Station Bulk Configuration Data (CME client mode) or
CME > UMTS Application > Import Data > Import Base Station Bulk
Configuration Data (U2000 client mode). Then, import the edited file into the
CME.
NOTE
For detailed function operations and introduction, press F1 on the CME to view section
Importing and Exporting NodeB Data for Batch Configuration in the U2000 Help.
----End
Example
//Setting the NE information/
SET NE: NENAME="HUAWEI", LOCATION="HANGZHOU-JIANGUOLU-3-3",
DID="DID_NODEB12345", SITENAME="LTE_1526", USERLABEL="hangzhou",
CLOUDBBID=0;
Follow-up Procedure
l
Verification
1.
Run the NodeB MML command LST NE to query the NE configuration information.
Expected result: The NE name, site location, deployment identifier, and site name are
the same as planned.
Rollback
Using MML commands
1.
Run the NodeB MML command SET NE to restore the NE configurations to the
original value.

1.
2.
3.
7.2.2 Reconfiguring the NodeB Clock Source or the Clock Working

Mode
This section describes how to reconfigure the NodeB clock source and the working mode of the
clock when the transport network is replanned.
Prerequisites
l
Issue 03 (2015-06-30)
Before reconfiguring the NodeB clock source or the clock working mode, collect
information listed in Table 7-2.
95
RAN17.1

Information
Description
Synchronization mode based on network

plan
Clock synchronization modes, such as

Clock over IP synchronization,
synchronous Ethernet clock
synchronization, and IEEE1588 V2
synchronization
Network interworking information for the
previous clock synchronization modes
If the IP clock synchronization mode is used, ensure that the IP clock server compatible
with Huawei devices is deployed.
If the GPS synchronization mode is used, ensure that the GPS satellite receiver and
antennas are installed and the GPS device works properly.
None
License requirement
A license is required for some clock synchronization features. A license file required for
reconfiguring the clock synchronization mode has been sent from the U2000 to the NodeB.
For the detailed operation procedure, see Managing NodeB Licenses in U2000 Online
Help.
Context
NOTICE
Without synchronization sources, the NodeB clock can maintain its accuracy for about 90 days.
However, if the NodeB cannot synchronize time with the new clock source 90 days after the
new clock source is configured, services on the NodeB will be affected.
During transport network restructuring, the clock synchronization mode may be reconfigured.
For example, when an ATM network is restructured into an IP network, the E1 clock
synchronization mode may be replaced with the IEEE1588 V2 synchronization mode.
Issue 03 (2015-06-30)
MO
Setting Notes
Data Source
Tasm
Set this MO as planned. For

details, see IP Network
Clock.
Engineering design

96
RAN17.1
MO
Setting Notes
Data Source
BITS
Set this MO as planned.
Engineering design
LineClk
Engineering design
GPS
Engineering design
IPCLKLNK

Clock.
Engineering design
SyncEth

Clock.
Engineering design
Procedure
l
Using MML commands

1.
Run the NodeB MML command DSP CLKSTAT to query the current settings of the
clock source and clock working mode.
2.
Run the NodeB MML commands listed in Table 7-4 to configure corresponding clock
sources.
Table 7-4 NodeB MML commands for configuring clock sources
3.
l
NodeB MML Commands
IP clock
ADD IPCLKLINK
Synchronous Ethernet clock
ADD SYNCETH
E1/T1 line clock
ADD LINECLK
GPS clock
ADD GPS
BITS clock
ADD BITS
After configuring the new clock source, run the NodeB MML command SET
CLKMODE to set the working mode of the reference clock source.

1.
Issue 03 (2015-06-30)
Clock Source

97
RAN17.1
2.
to
----End
Example
Reconfiguring the clock source from the E1 clock source to the Ethernet clock source
ADD SYNCETH: LN=0, SN=7, PN=0;
SET CLKMODE: MODE=MANUAL, CLKSRC=SYNCETH;
RMV LINECLK: LN=0;
Follow-up Procedure
l
Verification
1.
Run the NodeB MML command DSP CLKSTAT to check that the line clock source
and clock working mode are correctly reconfigured.
Expected result: Current Clock Source State is Normal.
Rollback
Using MML commands
Issue 03 (2015-06-30)
1.
Restore the reconfigured hardware devices and connections between them.
2.
Run the NodeB MML commands listed in Table 7-4 to reconfigure the removed
clock links.
98
RAN17.1
3.
Run the NodeB MML command SET CLKMODE to restore the clock source to
the original one.
4.
Run the NodeB MML commands listed in Table 7-5 to remove the new clock
links.
Table 7-5 NodeB MML commands for deleting clock links
Clock Source
NodeB MML Command
IP clock
RMV IPCLKLINK
Synchronous Ethernet clock
RMV SYNCETH
E1/T1 line clock
RMV LINECLK
GPS clock
RMV GPS
BITS clock
RMV BITS

1.
2.
3.
l
Troubleshooting
Issue 1: ALM-26262 External Clock Reference Problem is reported on the NodeB.
Solution: Clear the alarm based on the related alarm reference.
7.2.3 Reconfiguring the IP Address of a NodeB Clock Server

This section describes how to change the IP address of a NodeB clock server.
Prerequisites
l
Before data preparation, collect information listed in Table 7-6.
l
Issue 03 (2015-06-30)
Information
Description
IP address of the new clock server
IP address and subnet mask
99
RAN17.1
N/A
l
N/A

N/A
l
The current NodeB clock server is unavailable.
A network replanning requires changing the IP address of a NodeB clock server.
Context
During the IP address reconfiguration of the NodeB clock server, the NodeB fails time
synchronization, which may cause UE handover failures.
The reconfiguration requirements are as follows:
l
If no route has been configured between the NodeB and the NodeB clock server, a route
between them needs to be added.
If the NodeB clock server to be replaced works in manual clock working mode and uses
IP clock source, change the clock working mode to AUTO(Auto) so that the original IP
clock route can be removed and a new IP clock route can be added.
If the clock working mode is changed to AUTO(Auto) during the reconfiguration, change
it back to MANUAL(Manual) after the reconfiguration is complete.

Data Type
MO
Setting Notes
Data Source
MML
Command
IP route
IPRT
Query the route

between the
NodeB and its
clock server.
Device plan
LST IPRT
Clock Working
Mode
CLKMODE
Set the clock

working mode.
Device plan
LST
CLKMODE
Procedure
l
Issue 03 (2015-06-30)
Using MML commands

1.
Run the NodeB MML command SET CLKMODE to set Clock Working Mode to
AUTO(Auto).
2.
Run the NodeB MML command RMV IPCLKLINK to remove the original IP clock
link.
3.
Run the NodeB MML command ADD IPCLKLINK to add an IP clock link, with the
server IP address set to the IP address of the new NodeB clock server.
100
RAN17.1
4.
Run the NodeB MML command ADD IPRT to add an IP route bound to the new
clock server.
5.
Run the NodeB MML command SET CLKMODE to set Clock Working Mode to
MANUAL(Manual), Selected Clock Source to IPCLK(IP Clock).

1.
2.
Batch configuration
1.
file.
NOTE
Issue 03 (2015-06-30)
2.
3.
101
RAN17.1
CME.
NOTE
----End
Example
/*Setting the clock working mode*/
SET CLKMODE: MODE=AUTO;
/*Removing the original IP clock route*/
RMV IPCLKLINK:;
/*Add an IP clock link*/
ADD IPCLKLINK: ICPT=PTP, SN=7, CNM=UNICAST, IPMODE=IPV4,
CIP="172.31.13.241", SIP="192.168.0.128", PROFILETYPE=1588V2;
/*Adding an IP route between the NodeB and the NodeB clock server*/
ADD IPRT: RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="192.168.0.128",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="172.31.13.1";
/*Configuring the clock working mode and the clock source*/
SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK;
Follow-up Procedure
l
Verification
1.
Run the NodeB MML command LST IPCLKLINK to query the configuration of the
IP clock link.
Expected result: The server IP address of the new clock server is the same as planned.
2.
Run the NodeB MML command DSP IPCLKLINK to query the status of the IP clock
link.
Expected result: Link Available State is Available.
3.
Run the NodeB MML command DSP CLKSTAT to query the status of the NodeB
clock.
Expected result: PLL Status is Locked in 10 minutes later.
Rollback
Using MML commands
Follow Stepsto change the IP address of the clock server to the original IP address.
Issue 03 (2015-06-30)
1.
2.
3.
102
RAN17.1
l
Troubleshooting
Issue 1: The following alarms are reported on the NodeB.
ALM-26260 System Clock Failure
ALM-26262 External Clock Reference Problem
ALM-26263 IP Clock Link Failure
ALM-26264 System Clock Unlocked
Solution: Clear the alarm according to 3900 Series Base Station Alarm Reference.
7.2.4 Adding a WBBP or UBBP to a 3900 Series Base Station

This section describes how to add a WBBP or UBBP to expand the capacity of a 3900 series
base station.
Prerequisites
l
Before adding a WBBP or UBBP, collect information listed in Table 7-7.

Information
Description
Baseband processing board
l Slot information about the baseband

processing board
l Configuration information about the
current baseband processing board.
The WBBP or UBBP is installed and runs normally. For the detailed installation procedure,
see the following sections in DBS3900 Site Maintenance Guide: Replacing or Adding
Common Components > Adding Boards to the BBU.
Before the board for capacity expansion is installed, the NodeB is upgraded to a version
that matches the board. For the detailed operation procedure, see Upgrade Guide of the
target version.
License requirement
A license allowing a larger capacity has been obtained from Huawei engineers and sent
from the U2000 to the NodeB. For the detailed operation procedure, see Managing NodeB
Licenses in U2000 Online Help.
When adding a UBBP, prepare the license shown in the following table.
Issue 03 (2015-06-30)
Control Item ID
Control Item Name
Abbreviation
1008
UBBP Multi-Mode license

for UMTS (per UBBP)
LQW9UBPDM01

103
RAN17.1
Context
When the baseband resources on a NodeB are insufficient, a WBBP or UBBP is needed to expand
the capacity of the NodeB.
Data
Type
MO
Setting Notes
Data
Source
MML
Comm
and
Baseba
nd
processi
ng
board
RU
Set Cabinet No., Subrack No., and Slot No.

based on the planned installation position. Set
Board Type to WBBP or UBBP, and set and
Work Mode to FDD(Frequency Division
Duplex). Set Hardware Capacity Enhance
based on the capability of purchased hardware.
Normal indicates basic hardware capabilities,
and Full indicates full hardware capabilities.
Enginee
ring
design
ADD
BRD
Baseba
nd
equipm
ent
BASEB
ANDE
QM
Modify resource composition of the baseband

equipment.
Radio
plan
(Interna
l plan)
MOD
BASEB
ANDE
QM
NodeB
resourc
e
allocate
rule
NODE
BRESA
LLOCR
ULE
l Set the base station resource allocation mode Radio

plan
with Resource Allocate Rule set to
(Interna
CAPAFIRST(Capacity First Rule)
l plan)
l Optional: Set the automatic cell
SET
NODE
BRESA
LLOC
RULE
reestablishment switch.
Set Auto Rebuild Cell Switch to ON(ON),
and set Cs User Number Threshold and Ps
User Number Threshold. If the number of
CS users or the number of PS CELL_DCH
users in the downlink resource group is
smaller than the corresponding threshold, the
local cells are reestablished automatically.
NOTICE
Services in all cells will be interrupted while setting the
base station resource allocation mode and automatic
cell reestablishment switch.
Issue 03 (2015-06-30)

104
RAN17.1
NOTE
For a co-MPT base station, configure the baseband processing board only once and configure the
baseband equipment separately for each mode of the base station. For a separate-MPT base station,
configure the baseband processing board for each mode separately because different modes of the
base station cannot share the same baseband board.
The UBBP board supports multimode concurrence. When a UBBP board is added, the proportions
of resources on the board for different RATs must be specified. When the UBBP is used in multimode
concurrence scenarios, configure the UBBP for other modes. For details, see the corresponding
reconfiguration guides:
l GSM: GBSS Reconfiguration Guide for BSC6900
l LTE FDD: eRAN (FDD) Reconfiguration Guide
Run the NodeB MML command ADD BRD to set Hardware Capacity Enhance for the UBBP
board.
For the detailed configuration principle for WBBPs or UBBPs, see NodeB Baseband Resource
Management Feature Parameter Description.
It is not necessary to set the base station resource allocation mode and automatic cell reestablishment
switch if the uplink CE resources are added or the downlink CE resources are added for the WBBPb1
or WBBPb2 board.
Procedure
l
Using MML commands

1.
Run the NodeB MML command ADD BRD to add a WBBP or UBBP for a NodeB.
When a UBBP board is added, specify the UMTS mode for which the UBBP provides
baseband processing resources.
2.
Run the NodeB MML command MOD BASEBANDEQM to add baseband

equipment. After the new board is added to the corresponding baseband equipment,
the NodeB records the information about the baseband equipment and related uplink
and downlink baseband resources.
3.
Optional: When the downlink CE resources are expanded by adding boards to the
downlink resource group, configure the resource allocation mode for the NodeB and
reestablish local cells.
NOTICE
Services in all cells will be interrupted during the operation.
NOTE
The following operations are not required if the uplink CE resources are expanded or the
downlink CE resources are expanded for the WBBPb1 or WBBPb2 board.
a.
Run the BSC6900 MML command DEA UCELL to deactivate all logical cells.
b.
Run the NodeB MML command SET NODEBRESALLOCRULE to set

Resource Allocate Rule to CAPAFIRST(Capacity First Rule).
c.
Reestablish local cells.

Method 1: Run the NodeB MML command STR REALLOCLOCELL to
reallocate baseband resources for all the local cells.
Issue 03 (2015-06-30)

105
RAN17.1
Method 2: Run the NodeB MML command SET

NODEBRESALLOCRULE with Auto Rebuild Cell Switch set to ON
(ON), and Cs User Number Threshold and Ps User Number Threshold
set to appropriate values. If the number of CS users or the number of PS
CELL_DCH users in the downlink resource group is smaller than the
corresponding threshold, the local cells are reestablished automatically.
d.
l
Run the BSC6900 MML command ACT UCELL to activate all logical cells.

1.
In the left pane of the planned data area, right-click a NodeB and choose Device
Panel from the shortcut menu. A window is displayed in the right pane for you to
configure device data.
Figure 7-5 NodeB device panel
Area 1
Device navigation tree. The cabinet navigation tree is in the upper part
and the RF unit navigation tree is in the lower part.
After you select the cabinet, subrack, or RF unit in the device navigation
tree, area 2 displays the device panel of the selected device.
Area 2
2.
3.
Issue 03 (2015-06-30)
Cabinet, subrack, and board configuration area.
Add boards on the device panel.

a.
In area 2, select the slot for installing a board.
b.
Right-click the slot and choose to add a required board.
c.
Set board parameters and click OK.
Configure MO BASEBANDEQM and NODEBRESALLOCRULE.

106
RAN17.1
----End
Example
Adding a WBBPf board in slot 0
ADD BRD: SN=0, BT=WBBP;
MOD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=UL, OPMODE=ADD, SN=0;
MOD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=DL, OPMODE=ADD, SN=0;
Adding a UBBP board in slot 0

ADD BRD: SN=0, BT=UBBP, BBWS=GSM-0&UMTS-1&LTE FDD-0&LTE TDD-0;
MOD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=UL, OPMODE=ADD, SN=0;
MOD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=DL, OPMODE=ADD, SN=0;
Follow-up Procedure
l
Verification
1.
Issue 03 (2015-06-30)
Run the NodeB MML command DSP BRD to check whether the baseband processing
board works properly.
107
RAN17.1
Expected result: Availability Status of the baseband processing board is Normal.

2.
Optional: If the queried baseband processing board is UBBP, run the NodeB MML
command DSP NODEBBBRES to check whether the NODEBBBRES MO is
normal.
Expected result: Operational State of the UBBPd is Enabled.
Rollback
Using MML commands
1.
Run the NodeB MML command RMV BRD to remove the added board.

1.
2.
3.
l
Troubleshooting
Issue 1: ALM-26205 BBU Board Maintenance Link Failure and ALM-26200 Board
Hardware Fault are reported on the NodeB.
Solution: Clear the alarms based on the related alarm reference.
7.2.5 Adding an RF Module

This section describes how to add a radio frequency (RF) module for service adjustment or
capacity expansion.
Prerequisites
l
Before adding an RF module, collect information listed in Table 7-9.

Information
Description
RF unit type
Types of RF modules, such as WRFU,

MRFU, and RRU
Connections of the RFU units and BBUs
Optic cable connections between RF

modules and WBBP
RF modules are installed.
None
Issue 03 (2015-06-30)

108
RAN17.1
License requirement
None
Context
An RF module can be added for service adjustment or capacity expansion. For example, a
frequency band is added or a sector is expanded. After an RF module is added, its service
capability can be locked if required.
NOTE
The following RF modules do not allow users to lock their service capabilities: RRU3801C,
RRU3801E, RRU3804, RRU3805, RRU3806, RRU3808, RRU3821E, MTRU, MRFU V1, and
WRFU.
After adding an RF module, configure the carriers according to configuration principles in NodeB
Carrier Management Feature Parameter Description.
Prepare the data listed in Table 7-10.

Data
Type
MO
Setting Notes
Data
Sourc
e
MML
Comm
and
RRU/
RFU
RRU/
RFU
(RRU)
Add an RF module.
Networ
k plan
ADD
RRU
Breakp
oint
RRU
Chain/
Ring
(RRUC
HAIN)
During expansion of cascading levels for the RRU

chain or ring, if you need to add RF modules in the
middle of the chain or on the ring, then set a
breakpoint and clear the breakpoint.
Networ
k plan
MOD
RRUC
HAIN
During expansion of cascading levels for the RRU

chain or ring, if you need to add RF modules in the
middle of the chain or on the ring, add new RF
modules.
l Setting a breakpoint:
For the RRU chain, set BreakPoint
Position1 according to the actual position of
breakpoints.
For the RRU ring, set BreakPoint
Position1 and BreakPoint Position2
according to the actual position of
breakpoints.
l Clearing the breakpoint:
For the RRU chain, set BreakPoint
Position1 to 255.
For the RRU ring, set BreakPoint
Position1 and BreakPoint Position2 to
255.
Issue 03 (2015-06-30)

109
RAN17.1
NOTE
If newly added RF modules are managed by multiple modes, the configurations vary as follows:
l
For a co-MPT base station, RF module data is configured only once because the data can be shared in the
base station.
For a separate-MPT base station, RF module data is configured for each mode of the base station and
common parameters must be consistent for different modes.
Using MML commands
Procedure
Information Recording Procedure
1.
Run the NodeB MML command LST RRU to record the configuration
information about the RF module to be adjusted.
2.
Optional: If the service capability of the RF module is locked, run the NodeB
MML command DSP TXBRANCH to record the maximum output power of the
TX channel of the current RF module.
Reconfiguration Procedure
1.
Set the maintenance mode of the NodeB to TESTING.
2.
Run the NodeB MML command ADD RRU to add an RF module.
3.
Optional: During expansion of cascading levels for the RRU chain or ring, if you
need do add RF modules in the middle of the chain or on the ring, perform the
following steps:
a.
Run the NodeB MML command MOD RRUCHAIN to set breakpoints for
the RRU chain or ring.
NOTE
l Set Chain No. to the number of the RRU chain or ring to be expanded.
l For the RRU chain, set BreakPoint Position1 according to the actual position of
breakpoints.
l For the RRU ring, set BreakPoint Position1 and BreakPoint Position2 according to
the actual position of breakpoints.
4.
l
Run the NodeB MML command ADD RRU to add an RF module.
c.
Run the NodeB MML command MOD RRUCHAIN to clear the breakpoints.
In this step, set BreakPoint Position1 and BreakPoint Position2 in 3.1 to
255.
Set the maintenance mode of the NodeB to NORMAL.

1.
Issue 03 (2015-06-30)
b.

110
RAN17.1
Area 1
Area 2
2.
3.
Issue 03 (2015-06-30)
Add an RXU chain/ring.

a.
In the lower left part of the device panel, right-click TOPO and choose Add
Chain from the shortcut menu.
b.
Based on the planned data, set the related information such as the number and
networking mode of the RXU chain/ring and the port on the board to which the
RXU chain/ring head is connected.
c.
Click OK. The configured RXU chain/ring is displayed under the TOPO node.
Perform the following operations based on planned data.

111
RAN17.1
If you
need to...
Then...
Add an
RF unit
1. In the lower left part of the device panel, right-click a configured

RXU chain/ring, and choose Add Board > Board Type from the
shortcut menu. A dialog box is displayed for you to add an RF
board.
2. Set the working mode and other related attributes for the RF board.
NOTE
If the working mode of the RF module is UO, LO, or UL, when you set the
number of RF channels, you need to manually enter the RF specifications.
Selecting RF specifications from the RF specification list is not supported.
3. Click OK.
Add an
active
antenna
system
(AAS)
1. In the lower left part of the device panel, right-click a configured

RXU chain/ring, and choose Add Board > AAS from the shortcut
menu. A dialog box is displayed for you to add an AAS.
2. Set the topology position and other related attributes for the AAS.
3. Click OK.
4. Right-click a configured AAS and choose Internal Module from
the shortcut menu.
5. In the Internal Module dialog box, right-click a slot based on
planned data and choose Add ARRU from the shortcut menu.
6. In the displayed dialog box, click corresponding tabs and configure
antenna data.
7. When the configuration is complete, click OK.
8. Click Close. The Internal Module dialog box is closed.
4.
(Optional and required when you need to add RF units on the RXU ring or in the
middle of the RXU chain during RXU chain/ring capacity expansion) Add RF units
to the RXU ring or in the middle of the RXU chain.
Add an RF unit in the middle of the RXU chain.
Issue 03 (2015-06-30)
a.
On the RXU Topology tab page, select the board connected to the RXU chain
from the Interface board drop-down list.
b.
On the RXU Topology tab page, right-click the RXU chain for which you
want to set breakpoints, and choose Set Break Point from the shortcut menu.
c.

112
RAN17.1
If you
need
to...
Then...
Add an
RF unit
1. Right-click a position after the breakpoint where you want

to add a board and choose Add Board > Board Type from
the shortcut menu. A dialog box is displayed for you to add
an RF board.
2. Set the working mode and other related attributes for the RF
board.
3. Click OK.
Add an
AAS
1. Right-click a position after the breakpoint where you want

to add a board and choose Add Board > AAS from the
shortcut menu. A dialog box is displayed for you to add an
AAS.
2. Set AAS attributes.
3. Click OK.
4. Right-click a configured AAS and choose Internal
Module from the shortcut menu.
5. In the Internal Module dialog box, right-click a slot based
on planned data and choose Add ARRU from the shortcut
menu.
6. In the displayed dialog box, click corresponding tabs and
configure antenna data.
d.
Export the incremental scripts for adding RF boards.

Planned Area > Export Incremental Scripts (CME client mode) or CME
> Planned Area > Export Incremental Scripts (U2000 client mode). Then,
export configuration scripts.
For detailed function operations and introduction, press F1 on the CME to
view section Exporting Incremental Scripts from a Planned Data Area in
the U2000 Help.
e.
On the RXU Topology tab page, right-click a configured breakpoint and

choose Cancel Break Point from the shortcut menu.
f.
Export the incremental scripts for deleting breakpoints.

the U2000 Help.
Issue 03 (2015-06-30)

113
RAN17.1

NOTE
During script activation, you are advised to activate the incremental scripts for adding RF
boards, and then activate the incremental scripts for deleting breakpoints after hardware
reconfiguration.
Add an RF unit on the RXU ring.

a.
On the device panel, right-click the board where the RXU ring is located and
choose Properties from the shortcut menu. A dialog box is displayed for you
to set properties.
b.
On the CPRI Port tab page, set Administrative Status for ports at the RXU
ring head and tail to Blocked and click OK.
c.
On the RXU Topology tab page, select the board connected to the RXU ring
d.
On the RXU Topology tab page, right-click the RXU ring for which you want
to set breakpoints, and choose Set Break Point from the shortcut menu.
e.
Set start and end positions of two breakpoints and click OK.
f.

If you
need
to...
Then...
Add an
RF unit
1. Right-click a position between two breakpoints where you

want to add a board and choose Add Board > Board Type
from the shortcut menu. A dialog box is displayed for you to
add an RF board.
2. Set the working mode and other related attributes for the RF
board.
3. Click OK.
Add an
AAS
1. Right-click a position where you want to add a board on the

ring between two breakpoints and choose Add Board >
AAS from the shortcut menu. A dialog box is displayed for
you to add an AAS.
2. Set AAS attributes.
3. Click OK.
4. Right-click a configured AAS and choose Internal
Module from the shortcut menu.
5. In the Internal Module dialog box, right-click a slot based
on planned data and choose Add ARRU from the shortcut
menu.
6. In the displayed dialog box, click corresponding tabs and
configure antenna data.
Issue 03 (2015-06-30)

114
RAN17.1
g.

h.
Export the incremental scripts for adding RF boards.

the U2000 Help.
i.
On the device panel, right-click the board where the RXU ring is located and
choose Properties from the shortcut menu. A dialog box is displayed for you
to set properties.
j.
On the CPRI Port tab page, set Administrative Status for ports at the RXU
ring head and tail to Unblocked and click OK.
k.
Export the incremental scripts for unblocking the management status of CPRI
ports.
the U2000 Help.
NOTE
During script activation, you are advised to activate the incremental scripts for adding RF
boards, and then activate the incremental scripts for unblocking the management status of
CPRI ports after hardware reconfiguration.
----End
Example
//Recording the configuration information about the current RF module
LST RRU:;
//Adding an RF module on the RRU ring
//Setting the breakpoints
MOD RRUCHAIN:RCN=0, BRKPOS1=3, BRKPOS2=3;
//Adding an RF module
ADD RRU: CN=0, SRN=78, SN=0, TP=TRUNK, RCN=0, PS=4, RT=MRRU, RS=GO,
RXNUM=2, TXNUM=2, RUSPEC="RRU3908_V1";
//Clearing the breakpoints
//Setting the breakpoints
//Deleting the RF module
RMV RRU: CN=0, SRN=78, SN=0;
Issue 03 (2015-06-30)

115
RAN17.1
//Clearing the breakpoints

Follow-up Procedure
l
Verification
1.
Run the NodeB MML command LST RRU to query the reconfigured RF module. If
the configuration of this RF module is the same as the specified value, the
reconfiguration is successful.
2.
Run the NodeB MML command DSP BRD to query the state of the RF module.
Expected result: Availability Status of the RF module is Normal.
Rollback
Using MML commands
1.
Optional: If the service capability of the RF module is locked, run the MML
command LOC RRUTC to unlock the service capability. In this step, set
Maximum Output Power Support Setting of the TX Channel to 0.
2.
Optional: If the RRU chain or ring is cascaded:

a.
Run the NodeB MML command MOD RRUCHAIN to set breakpoints for
the RRU chain.
b.
Run the NodeB MML command RMV RRU to delete the RF module added
after the reconfiguration.
c.
Run the NodeB MML command MOD RRUCHAIN to delete the

breakpoints set after the reconfiguration.

1.
2.
3.
l
Troubleshooting
Issue 1: ALM-26235 RF Unit Maintenance Link Failure and ALM-26532 RF Unit
Hardware Fault are reported on the NodeB.
7.2.6 Changing CPRI Ports for RF Modules

This section describes how to change CPRI ports for RF modules.
Prerequisites
l
Issue 03 (2015-06-30)

116
RAN17.1
Information
Description
RF module topology over the CPRI ports
Ring or chain topology supported in the

UMTS network
New CPRI port numbers
Slot number of the baseband processing

board and the CPRI port number
CPRI port numbers before the topology

change

board and the CPRI port number, which are
required for engineering rollback
N/A
N/A
License requirement
N/A
Context
NOTICE
Before changing CPRI ports for RF modules, the CPRI line rate must be checked. You can run
the NodeB MML command LST RRUCHAIN to query the configuration of the RRU chain/
ring.
Issue 03 (2015-06-30)

117
RAN17.1

Data
Type
MO
Setting Notes
Data
Source
MML
Comma
nd
RRU
Chain/
Ring
RRUCH
AIN
1. Set breakpoints on the RRU chain or ring:
Network
plan
MOD
RRUCH
AIN
l Set only one breakpoint for a chain

with the BreakPoint Position1
parameter set to 0.
l Set two breakpoints for a ring with the
BreakPoint Position1 and
BreakPoint Position2 parameters set
to 0 and a value equaling the number
of RRU cascading levels, respectively.
2. Determine the parameters to be modified
based on the CPRI networking mode and
slot for the board providing the CPRI ports
after reconfiguration. For details, see
Table 7-13 and Table 7-14.
3. Set the BreakPoint Position1 and
BreakPoint Position2 parameters to 255
to remove breakpoints from the RRU
chain or ring.
Determine the parameters to be modified based on the CPRI networking mode and slot for the
board providing the CPRI ports after reconfiguration.
l
For BBU3900 or BBU3910, see the following table.

Table 7-13 Parameters should be modified for BBU3900 or BBU3910
New CPRI
Port Position
Issue 03 (2015-06-30)
CPRI
Networking
Mode
Parameters to Be Modified
Another CPRI
Chain
port on the same
Ring
baseband
processing
board
Set Head Port No. to the target value.
A CPRI port on
another
baseband
processing
board
Chain
Set Head Slot No. and Head Port No. to the

target values.
Ring
Set Head Slot No., Tail Slot No., Head Port

No., and Tail Port No. to the target values based
on whether the new CPRI port number is the ring
head or tail port number.
Set Head Port No. and Tail Port No. to the target
values based on whether the new CPRI port
number is the ring head or tail port number.

118
RAN17.1
For BBU3910A, see the following table.

Table 7-14 Parameters should be modified for BBU3910A
New CPRI
Port Position
CPRI
Networking
Mode
Another CPRI
Chain
port on the same
Ring
BBU

Procedure
l
Using MML commands

1.
Run the NodeB MML command MOD RRUCHAIN to set break points for the RRU
chain or ring.
For the RRU chain, set BreakPoint Position1 according to the actual position of
breakpoints.
For the RRU ring, set BreakPoint Position1 and BreakPoint Position2 according
to the actual position of breakpoints.
2.
Perform the following operations onsite:

If the RF modules need to be connected to another CPRI port with the baseband
processing board position unchanged, remove the CPRI cable from the original
port and connect it to the new port.
For BBU3900 or BBU3910, if the RF modules need to be connected to another
CPRI port with the baseband processing board position changed, remove the
baseband processing board from the original slot and install it in the new slot.
3.
Run the NodeB MML command MOD RRUCHAIN to set the CPRI ports connecting
RF modules to the target ones.
4.
Run the NodeB MML command MOD RRUCHAIN to clear the break points. Set
BreakPoint Position1 and BreakPoint Position2 in Step 1 to 255.

1.
Issue 03 (2015-06-30)

119
RAN17.1
2.
to
----End
Example
For BBU3900 or BBU3910, in the following example, the topology of the CPRI ports is a ring,
the head CPRI port with the ring number 0 is changed from port 0 of the WBBP in slot 2 to port
0 of the WBBP in slot 3, the tail CPRI port is changed from port 1 of the WBBP in slot 2 to port
1 of the WBBP in slot 3, and the number of remote radio unit (RRU) cascading levels is 2.
/*Set the first and second breakpoints of the RRU ring to 0 and 2,
respectively.*/
MOD RRUCHAIN: RCN=0, BRKPOS1=0, BRKPOS2=2;
/*Modify the numbers of the CPRI ports connecting the RRUs.*/
MOD RRUCHAIN: RCN=0, TT=RING, BM=COLD, HSN=3, HPN=0, TSN=3, TPN=1;
/*Remove the breakpoints of the RRU ring.*/
For BBU3910A, in the following example, the topology of the CPRI ports is a ring, the head
CPRI port with the ring number 0 is changed from port 0 of the WBBP to port 1 of the WBBP,
the tail CPRI port is changed from port 3 of the WBBP to port 4 of the WBBP, and the number
of remote radio unit (RRU) cascading levels is 2.
/*Set the first and second breakpoints of the RRU ring to 0 and 2,
respectively.*/
Issue 03 (2015-06-30)

120
RAN17.1

/*Modify the numbers of the CPRI ports connecting the RRUs.*/
MOD RRUCHAIN: RCN=0, TT=RING, BM=COLD, HSN=6, HPN=1, TSN=6, TPN=4;
/*Remove the breakpoints of the RRU ring.*/
Follow-up Procedure
l
Verification
1.
Run the NodeB MML command DSP ULOCELL to query the status of the local cell.
Expected result: Local Cell Status is Local Cell Available.
Rollback
Using MML commands
1.
Run the NodeB MML command MOD RRUCHAIN to set break points for the
RRU chain or ring.
2.

If the RF modules need to be connected to another CPRI port with the baseband
processing board position unchanged, remove the CPRI cable from the new
port and connect it to the original port.
For BBU3900 or BBU3910, if the RF modules need to be connected to another
CPRI port with the baseband processing board position changed, remove the
baseband processing board from the new slot and install it in the original slot.
3.
Run the NodeB MML command MOD RRUCHAIN to set the CPRI ports
connecting RF modules to the original ones.
4.
Run the NodeB MML command MOD RRUCHAIN to clear the break points.

1.
2.
3.
l
Troubleshooting
Issue 1: ALM-26246 BBU CPRI Line Rate Negotiation Abnormal is reported on the
NodeB.
Issue 2: ALM-28203 Local Cell Unusable or ALM-28206 Local Cell Capability
Decline is reported on the NodeB.
Issue 03 (2015-06-30)

121
RAN17.1
7.2.7 Replacing a Baseband Processing Board

This section describes how to replace a WBBP board with a UBBP board.
Prerequisites
l
Before replacing a WBBP board with a UBBP board, collect information listed in Table
7-15.
Information
Description
NodeB baseband resource
NodeB baseband resources for a new

UBBP board
Board
The WBBP board and UBBP board are of

different types. Therefore, change the
board type to UBBP.
The physical connection of the new UBBP board is complete.
None
License requirement
The license UBBP Multi-Mode license for UMTS (per UBBP) has been obtained
from Huawei engineers and sent from the U2000 to the NodeB. For the detailed
operation procedure, see Managing NodeB Licenses in U2000 Online Help.
The license control item value must be greater than or equal to the number of UBBP
boards, or alarms about the license will be reported.
Context
Issue 03 (2015-06-30)

122
RAN17.1
Issue 03 (2015-06-30)
Data
Type
MO
Setting Notes
Data Source
MML Command
Baseband
Processing
Board
BBP
Set Board Type for

the board in the
target slot to
UBBP, and set
Base Band Work
Standard to
specify the UMTS
mode for which the
UBBP provides
baseband
processing
resources.
Network plan
MOD BBP

123
RAN17.1
Data
Type
MO
Setting Notes
Data Source
MML Command
NodeB
resource
allocate
rule
NODEBR
ESALLO
CRULE
l Set the base

station resource
allocation mode
with Resource
Allocate Rule
set to
CAPAFIRST
(Capacity First
Rule)
Radio plan
(Internal plan)
SET
NODEBRESALLO
CRULE
l Optional: Set
the automatic
cell
reestablishment
switch.
Set Auto
Rebuild Cell
Switch to ON
(ON), and set
Cs User
Number
Threshold and
Ps User
Number
Threshold. If
the number of
CS users or the
number of PS
CELL_DCH
users in the
downlink
resource group
is smaller than
the
corresponding
threshold, the
local cells are
reestablished
automatically.
NOTICE
Services in all cells
will be interrupted
while setting the
base station
resource allocation
mode and automatic
cell reestablishment
switch.
Issue 03 (2015-06-30)

124
RAN17.1
NOTE
l When the UBBP is used in multimode concurrence scenarios, configure the UBBP for other modes. For
details, see the corresponding reconfiguration guides:
l GSM: GBSS Reconfiguration Guide for BSC6900
l LTE FDD: eRAN (FDD) Reconfiguration Guide
l It is not necessary to set the base station resource allocation mode and automatic cell reestablishment switch
if the uplink CE resources are added.
Procedure
l
Using MML commands

1.
Run the NodeB MML command BLK BRD to block the WBBP board.
2.
Remove the WBBP board and install a UBBP board in the target slot. If the RF
modules are connected to the WBBP board, connect the optical modules or the
electrical ports to the corresponding ports on the UBBP board.
3.
Run the NodeB MML command MOD BBP to set Board Type for the board in the
target slot to UBBP, and set Base Band Work Standard to GSM-0&UMTS-1&LTE
FDD-0&LTE TDD-0 to specify the UMTS mode for which the UBBP provides
baseband processing resources.
4.
Run the NodeB MML command UBL BRD to unblock the UBBP board.
5.
Reestablish local cells.

Method 1: Run the NodeB MML command STR REALLOCLOCELL to
reallocate baseband resources for all the local cells.
Method 2: Run the NodeB MML command SET NODEBRESALLOCRULE
with Auto Rebuild Cell Switch set to ON(ON), and Cs User Number
Threshold and Ps User Number Threshold set to appropriate values. If the
number of CS users or the number of PS CELL_DCH users in the downlink
resource group is smaller than the corresponding threshold, the local cells are
reestablished automatically.

1.
Issue 03 (2015-06-30)

125
RAN17.1
2.
to
----End
Example
BLK BRD: CN=0, SRN=0, SN=3, BLKTP=IMMEDIATE;
MOD BBP: CN=0, SRN=0, SN=3, TYPE=UBBP, BBWS=GSM-0&UMTS-1&LTE FDD-0&LTE
TDD-0;
UBL BRD: CN=0, SRN=0, SN=3;
Follow-up Procedure
l
Verification
1.
Expected result: Local Cell Status is Local Cell Available and Cell Operation
Status is Enabled.
2.
Ensure that no alarms related to the baseband processing board are reported.
3.
Observe the board-level performance counters, such as VS.CE.DLMean.Board and

VS.CE.ULMean.Board. Check that the actual service is normal.
Rollback
Using MML commands
1.
Issue 03 (2015-06-30)
Run the NodeB MML command BLK BRD to block the specified board.
126
RAN17.1
2.
Run the NodeB MML command MOD BBP to set Board Type for the board in
the target slot to WBBP.
3.
Run the NodeB MML command UBL BRD to unblock the specified board.

1.
2.
3.
l
Troubleshooting
Issue 1: ALM-28203 Local Cell Unusable or ALM-28206 Local Cell Capability Decline
is reported on the NodeB.
Issue 2: ALM-26811 Configured Capacity Limit Exceeding Licensed Limit is reported
on the NodeB. The license UBBP Multi-Mode license for UMTS (per UBBP) has not
been sent to the NodeB.
Solution: Obtain the UBBP Multi-Mode license for UMTS (per UBBP) license and
send it from U2000 to NodeB.
7.2.8 Replacing a Main Control Board

When the WMPT can no longer meet service requirements, for example, it cannot provide
sufficient CNBAP capacity, replace the WMPT with the UMPT. For details about how to replace
the software, see Replacing the WMPT in DBS3900 Site Maintenance Guide. This section
mainly describes the configuration adjustment related to the replacement.
Prerequisites
l

Information
Description
Local maintenance IP address
Record the local maintenance IP address of

the WMPT before replacement. This IP
address is necessary for a rollback in the
event of a replacement failure.
The UMPT is prepared.
If the USB flash drive is used to restore the software and configurations, ensure that the
USB port on the UMPT is enabled.
Issue 03 (2015-06-30)

127
RAN17.1
You have obtained the software package from Huawei engineers and decompressed the
software package on a local PC.
License requirement
N/A
Context
Replacing the WMPT has the following impacts on the base station:
l
If no standby WMPT is configured, replacing the WMPT interrupts all the services carried
by the base station. Therefore, the WMPT must be replaced within 10 minutes.
If a multimode base station supports co-transmission and the shared ports for cotransmission are on the WMPT, replacing the WMPT will interrupt the services of the peer
mode. Typical scenario: The GU dual-mode base station supports co-transmission over IP
through the Ethernet link on the WMPT. The GSM data is transmitted through the FE ports
interconnecting the WMPT and GTMU panels.
For a multimode base station in dual-star topology, replacing the WMPT may decrease the
rate of GSM or LTE data services. However, voice services will not be affected.
When the WMPT can no longer meet service requirements, for example, it cannot provide
sufficient CNBAP capacity, replace the WMPT with the UMPT by following the process
illustrated in Figure 7-10.
NOTICE
l
Do not use a USB flash drive but the LMT or U2000 to restore the software and
configurations when any certificate or authentication related data is being used, because
the CME cannot export such data. Such data includes the data related to a PPP certificate,
multi-link PPP certificate, or pre-shared key used for authentication.
If the NodeB is configured with VLAN group mode, change the VLAN group mode to
single VLAN mode. For instructions on how to adjust the configuration, see 7.4.3
Changing the VLAN Configuration Mode.
Issue 03 (2015-06-30)

128
RAN17.1
Figure 7-10 Process for replacing the WMPT

Issue 03 (2015-06-30)
Data Type
MO
Setting Notes
Data Source
MML
Command
IP Address
LOCALIP
Change the local

maintenance IP
address after the
main control
board is
replaced.
Equipment
planning
SET
LOCALIP

129
RAN17.1
Procedure
Step 1 Run the NodeB MML command BLK ULOCELL to block all cells under the NodeB.
NOTE
If this command cannot be executed or services of this cell are interrupted, go to the next step.
Step 2 Optional: If the NodeB is configured with VLAN group mode, change the VLAN group mode
to single VLAN mode. For instructions on how to adjust the configuration, see 7.4.3 Changing
the VLAN Configuration Mode.
Step 3 On the CME, change the local maintenance IP address.
1.
Select a base station in the left pane of the planned data area. The NE object tree is displayed
in the lower part of the left pane, as shown in the following figure.
2.
In area 1, select or search for the MO: LOCALIP and double-click the MO. In area 2, set
IP Address to 192.168.0.49 and click
Step 4 Export data configuration files and deployment lists from the CME. For details, see CME
Management > CME Guidelines > Enhanced Feature Management > Exporting AutoDeployment Data Files in U2000 Online Help.
NOTE
The deployment lists are required if configuration data is to be activated using the U2000 or USB flash drive.
The deployment lists must be exported using the CME.
Step 5 Make preparations based on the method used to restore the software and configurations.
Issue 03 (2015-06-30)

130
RAN17.1
NOTICE
If the BBU is configured with a UTRPc, the software and configurations can only be reset locally.
Procedure
Prerequisite
If...
Then...
Restore software
and
configurations
remotely.
l The transport
network
supports the
automatic
establishment
of OM
channels.
You need to
restore software
and
configurations by
means of a selfdeployment task
on the U2000
1. Upload the software

package to the U2000
server.
For details, see RAN
Management > SON
Management > NE
Automatic Deployment
Management >
Uploading Data Files in
U2000 Online Help.
l The time for

restoring
software and
configurations
remotely is
longer than
that for
restoring
software and
configurations
locally.
2. Upload the data

configuration files and
deployment list to the
U2000 server.
Management > SON
Management > NE
Management >
Uploading Data Files in
U2000 Online Help.
3. Create the NE
commissioning task.
Management > SON
Management > NE
Management > Creating
NE Commissioning
Tasks in U2000 Online
Help.
Issue 03 (2015-06-30)

131
RAN17.1
Procedure
Prerequisite
If...
Then...
Restore software
and
configurations
locally.
l The device
required by
local
commissionin
g is available:
a PC (restoring
using the
LMT) or USB
flash drive
(restoring
using a USB
flash drive).
You need to
restore software
and
configurations
using a USB flash
drive.
Prepare the USB flash drive

directory for upgrading the
software and updating
configuration files.
You need to
restore software
and
configurations
using LMT.
Configuring the FTP Server.
l Ensure that the

USB port on
the main
control board
has been
enabled.
For details, see

Commissioning a Newly
Deployed Base Station >
USB+U2000-based
Commissioning >
Preparation > Preparing a
USB Flash Drive (for
NodeB, eNodeB, and
BTS3900) in 3900 Series
Base Station Commissioning
Guide.
For details, see Maintaining

the Base Station > Common
Maintenance Tasks >
Configuring the FTP
Server in LMT Online Help.
Step 6 Perform the following operations onsite:

1.
Record cable connections of the WMPT and then remove the cables.
2.
Remove the WMPT and insert the UMPT.
3.
Connect cables to the UMPT according to cable connections recorded in Step 6.1. Then,
power on the base station.
Step 7 Restore the software and configurations according to the following table.
If...
Then...
You need to restore software

and configurations using
U2000.
1. Start the NE commissioning task.

For details, see RAN Management > SON
Management > NE Automatic Deployment
Management > Starting NE Commissioning Tasks in
U2000 Online Help.
2. Monitor the task status. If the NE commissioning task
enters the auto-configuration phase, the base station has
finished restoring the software and configurations.
For details, see RAN Management > SON
Management > NE Automatic Deployment
Management > NE Commissioning Monitoring in
U2000 Online Help.
Issue 03 (2015-06-30)

132
RAN17.1
If...
Then...

and configurations using
LMT.
1. Download and activate the software and configuration

file.
For details, see Maintaining the Base Station >
Common Maintenance Tasks > Downloading and
Activating the Software and Data Configuration File
in LMT Online Help.
2. After the base station restarts, run the LST VER
command to check whether all modes have been loaded
with the software of the target version. If not, run the DLD
SOFTWARE command to redownload the software and
then run the ACT SOFTWARE command to activate the
software.

and configurations using a
USB flash drive.
1. Connect the USB flash drive to the USB port on the main
control board, and the board automatically loads the
software package and data configuration files from the
USB flash drive.
For details, see Commissioning a Newly Deployed Base
Station > USB+U2000-based Commissioning > Local
Operations > Loading a Software Package or Data
Configuration Files from a USB Flash Drive in 3900
Series Base Station Commissioning Guide.
2. After the base station restarts, run the LST VER
command to check whether all modes have been loaded
with the software of the target version. If not, run the DLD
SOFTWARE command to redownload the software and
then run the ACT SOFTWARE command to activate the
software.
Step 8 Run the NodeB MML command UBL ULOCELL to unblock all cells under the NodeB.
----End
Follow-up Procedure
l
Verification
1.
Expected result: Local Cell Status is Local Cell Available and Cell Operation
Status is Enabled.
Rollback
1.
Run the NodeB MML command BLK ULOCELL to block all cells under the NodeB.
2.
On the CME, roll back the configurations of VLANs and the local maintenance IP
address.
3.

Remove the UMPT and insert the WMPT.
Issue 03 (2015-06-30)

133
RAN17.1
Connect cables to the WMPT according to cable connections recorded in Step

6.1. Then, power on the base station.
4.
l
Run the NodeB MML command UBL ULOCELL to unblock all cells under the
NodeB.
Troubleshooting
Issue 1: ALM-25880 Ethernet Link Fault is reported on the NodeB.
7.2.9 Changing the Local Maintenance IP address of a NodeB

This section describes how to change the local maintenance IP address of a NodeB.
Prerequisites
l
Information
Description
Local maintenance IP address
Local maintenance IP address of the

WMPT used before the reconfiguration.
This IP address is necessary for a rollback
in the event of a reconfiguration failure.
Includes the new local maintenance IP
address and subnet mask.
N/A
N/A
License requirement
N/A
The previous local maintenance IP address plan is inappropriate and a new plan is required.
Context
l
During the reconfiguration of the local maintenance IP address of a NodeB, the LMT cannot
connect to the NodeB. After the reconfiguration is complete, use the new local maintenance
IP address to log in to the LMT.
To change the local maintenance IP address, modify the MO LOCALIP to change the
values of IP Address and Mask to the target values.

Issue 03 (2015-06-30)

134
RAN17.1
Data Type
MO
Setting Notes
Data Source
MML
Command
IP address and
subnet mask
LOCALIP
Set the IP
Address and
Mask to the
target values.
Device plan
SET
LOCALIP
Procedure
l
Using MML commands

1.
Run the NodeB MML command SET LOCALIP to set the IP Address and Mask.

1.
2.
Batch configuration
1.
Issue 03 (2015-06-30)
135
RAN17.1
file.
NOTE
2.
3.
CME.
NOTE
----End
Example
/*Changing the IP address for the NodeB local maintenance*/
SET LOCALIP: IP="192.168.0.49", MASK="255.255.255.0";
Follow-up Procedure
l
Verification
1.
Run the NodeB MML command LST LOCALIP to query the information about the
local maintenance IP address of the NodeB.
Expected result: IP Address and Mask is the same as planned.
Rollback
Using MML commands
1.
Run the NodeB MML command SET LOCALIP to set the local maintenance IP
address of the NodeB to the original value.
2.
Run the NodeB MML command LST LOCALIP to check that the local
maintenance IP address of the NodeB is the same as the one used before the
reconfiguration.

1.
2.
3.
Issue 03 (2015-06-30)

136
RAN17.1
7.3 Radio Data Reconfiguration

This chapter describes how to reconfigure NodeB radio data in typical scenarios.
7.3.1 Reconfiguring the Number of Carriers for a NodeB

This section describes how to reconfigure the number of carriers for a NodeB.
Prerequisites
l
Before reconfiguring the number of carriers for a NodeB, collect information listed in Table
7-20.
Information
Description
Logical cell
Configuration of the logical cell for which

the carrier to be added
Local cell
Configuration of the local cell for which

the carrier to be added
The physical connection of the new RF module is complete.
None
License requirement
None
Context
Issue 03 (2015-06-30)
Data
Type
MO
Setting Notes
Data Source
MML Command
Location
LOCATI
ON
Set this MO as
planned.
Network plan
ADD LOCATION
Sector
SECTOR
Set this MO as
planned.
Network plan
ADD SECTOR
Sector
equipment
SECTOR
EQM
Set this MO as
planned.
Network plan
ADD
SECTOREQM

137
RAN17.1
Data
Type
MO
Setting Notes
Data Source
MML Command
UL or DL
baseband
equipment
BASEBA
NDEQM
Set this MO as
planned.
Network plan
ADD
BASEBANDEQM
Cell
ULOCEL
L
Set this MO as
planned.
Network plan
ADD ULOCELL
NOTE
If different modes of a co-MPT base station share a SECTOR MO, the data shared by all modes can be configured
only once. Before removing the configured SECTOR MO, ensure that the SECTOR MO is disabled on all
modes of the base station.
Procedure
l
The MML-based procedure is as follows:

1.
Optional: Run the NodeB MML command ADD LOCATION to set location-related
parameters.
NOTE
If new RF modules are added, see 7.2.5 Adding an RF Module.
2.
Optional: Run the NodeB MML command ADD SECTOR to set parameters related
to the sector and sector antenna.
3.
Optional: Run the NodeB MML command ADD SECTOREQM to set parameters
related to the sector equipment and sector equipment antenna.
4.
Optional: Run the NodeB MML command ADD BASEBANDEQM to set

parameters related to the uplink or downlink baseband equipment.
5.
Run the NodeB MML command ADD ULOCELL to set parameters related to the
local cell and local cell sector equipment.
If you need to add a logical cell, perform the following steps:
a.
Run the BSC MML command ADD ULOCELL to add a local cell belonging
to a specified NodeB.
b.
Run the BSC MML command ADD UCELLQUICKSETUP to quickly set up

a cell.
c.
Run the BSC MML command ACT UCELL to activate the new logical cell.
NOTE
If the LOCATION, SECTOR, SECTOREQM, or BASEBANDEQM MO has been configured,

ignore the related operation.

Adjust the number of carriers for a single base station.
1.
Issue 03 (2015-06-30)
138
RAN17.1
2.
Adjust the numbers of carriers for base stations in batches.

1.
file.
NOTE
2.
3.
CME.
NOTE
----End
Issue 03 (2015-06-30)

139
RAN17.1
Example
ADD LOCATION: LOCATIONNAME="mall", MODE=MANUAL, GCDF=Degree,
LATITUDEDEGFORMAT=22222222, LONGITUDEDEGFORMAT=33333333;
ADD SECTOR: SECTORID=0, ANTNUM=2, ANT1CN=0, ANT1SRN=60, ANT1SN=0,
ANT1N=R0A, ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0B,
CREATESECTOREQM=FALSE;
ADD SECTOREQM: SECTOREQMID=0, SECTORID=0, ANTNUM=2, ANT1CN=0, ANT1SRN=60,
ANT1SN=0, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=60, ANT2SN=0,
ANT2N=R0B, ANTTYPE2=RX_MODE;
ADD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=ULDL,
UMTSDEMMODE=DEM_2_CHAN, SN1=3;
ADD ULOCELL: ULOCELLID=1001, LOCELLTYPE=NORMAL_CELL, SECTOREQMNUM=1,
SECTOREQMID1=0, TTW=FALSE, ULFREQ=9612, DLFREQ=10562, MAXPWR=430,
HISPM=FALSE, RMTCM=FALSE, VAM=FALSE;
Follow-up Procedure
l
Verification
Rollback
1.
Run the NodeB MML command RMV ULOCELL to remove the added local cell.
2.
Run the NodeB MML command RMV SECTOREQM to remove the added sector
equipment.
3.
Run the NodeB MML command RMV SECTOR to remove the added sector.
4.
Run the NodeB MML command RMV LOCATION to remove the added location
information.

1.
2.
3.
l
Troubleshooting
Issue 1: ALM-28203 Local Cell Unusable or ALM-28206 Local Cell Capability Decline
is reported on the NodeB.
7.3.2 Adding a Set of Baseband Equipment

This section describes how to add a set of uplink baseband equipment and a set of downlink
baseband equipment.
Issue 03 (2015-06-30)

140
RAN17.1
Prerequisites
l
Information
Description
NodeB baseband resources
Whether the baseband processing unit to be

added to a set of baseband equipment has
been installed.
Baseband processing unit
Different types of baseband processing

units support different baseband
equipments.
NodeB baseband equipment

been added to other sets of baseband
equipment.
The WBBP or UBBP board is installed and running properly. For details, see Replacing
or Adding Common Components > Adding BBU3900 or BBU3910 Components in
DBS3900 Site Maintenance Guide.
NOTE
The WBBPf4 board can be added to two sets of UL baseband equipment. Before adding a WBBPf4
board to a set of second UL baseband equipment, run the BLK BRD command to block the board.
N/A
License requirement
N/A
The current baseband resources are insufficient.
Context
Issue 03 (2015-06-30)

141
RAN17.1
Data Type
MO
Setting Notes
Data Source
MML
Command
NodeB
baseband
resources
RU
Query the
information
about all
baseband
processing
units.
Engineering
design
DSP BRD
Baseband
processing unit
BRDMFRINFO
Query the
information of a
specified
baseband
processing unit.
Engineering
design
DSP
BRDMFRINF
O
Baseband
equipment
BASEBANDE
QM
List the
configuration of
the baseband
equipment.
Network plan
LST
BASEBANDE
QM
NOTE
l A set of baseband equipment that is capable of processing uplink services can be a set of uplink baseband
equipment or a set of uplink and downlink baseband equipment. A set of baseband equipment that is capable
of processing downlink services can be a set of downlink baseband equipment or a set of uplink and downlink
baseband equipment.
l A maximum of 24 sets of baseband equipment that are capable of processing uplink services can be
configured. A maximum of 12 sets of baseband equipment that are capable of processing downlink services
can be configured. A base station supports a maximum of 36 baseband processing units.
l The baseband processing units in a set of baseband equipment capable of processing uplink services (or
uplink and downlink services) must be configured in the same subrack. The baseband processing units in a
set of baseband equipment capable of processing downlink services can be configured in different subracks.
l The ID of a set of uplink and downlink baseband equipment capable must differ from the ID of a set of
uplink or downlink baseband equipment.
Procedure
l
Using MML commands

1.
Optional: When the WBBPf4 board is used, run the command BLK BRD to block
the board before adding it to the second set of UL baseband equipment.
2.
Run the NodeB MML command ADD BASEBANDEQM to add a set of baseband
equipment.
3.
Optional: Run the NodeB MML command UBL BRD to unblock the board that has
been blocked in Step 1.

Single reconfiguration
1.
Issue 03 (2015-06-30)
142
RAN17.1
2.
Based on the planned data, select or search for the MO to be configured in area 1,
and then double-click the MO.
3.
Add the baseband equipment in the upper part of area 2 and add the baseband board
for the baseband equipment in the lower part.
4.
Click
to save the configured data.
Batch reconfiguration
1.
file.
NOTE
2.
3.
CME.
NOTE
----End
Issue 03 (2015-06-30)

143
RAN17.1
Example
/*Adding a set of baseband equipment*/
ADD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=DL, SN1=2, SN2=1;
Follow-up Procedure
l
Verification
1.
Run the NodeB MML command LST BASEBANDEQM to query the configuration
of the set of baseband equipment.
Expected result: The newly added baseband equipment is displayed in the command
output.
Rollback
Using MML commands
1.
Run the NodeB MML command RMV BASEBANDEQM to remove the newly
added baseband equipment.

1.
2.
3.
7.3.3 Modifying a Set of Baseband Equipment

This section describes how to modify a set of baseband equipment, including to remove a
baseband processing unit and to add a baseband processing unit.
Prerequisites
l
Information
Description

been added to other sets of baseband
equipment.
N/A
Issue 03 (2015-06-30)

144
RAN17.1
N/A
License requirement
N/A
The processing capabilities of a set of baseband equipment need adjustment.
Context
This is a high-risk MML command, and therefore exercise caution when you are modifying a
set of baseband equipment:
l
Removing a baseband processing unit that carries services from a set of baseband
equipment affects the ongoing services.
At least one baseband processing unit must be reserved in a set of baseband equipment.

Data Type
MO
Setting Notes
Data Source
MML
Command
Baseband
equipment
BASEBANDE
QM
List and modify

the
configuration of
a set of
baseband
equipment.
Network plan
LST
BASEBANDE
QM
MOD
BASEBANDE
QM
Procedure
l
Using MML commands

1.
Optional: When the WBBPf4 board is used, run the command BLK BRD to block
the board before adding it to the second set of UL baseband equipment.
2.
Run the NodeB MML command MOD BASEBANDEQM to remove the baseband
processing unit from the set of baseband equipment.
3.
Run the NodeB MML command MOD BASEBANDEQM to add a baseband

processing unit to the planned set of baseband equipment.
4.
Optional: Run the NodeB MML command UBL BRD to unblock the board that has
been blocked in Step 1.

1.
Issue 03 (2015-06-30)
145
RAN17.1
2.
3.
Select baseband equipment to be modified in the upper part of area 2 and add or
delete the baseband board for the baseband equipment in the lower part.
4.
Click
1.
file.
NOTE
2.
3.
CME.
NOTE
----End
Issue 03 (2015-06-30)

146
RAN17.1
Example
/*Modifying a set of baseband equipment:*/
MOD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=ULDL, OPMODE=ADD, SN=0;
Follow-up Procedure
l
Verification
1.
Expected result: The configuration of the set of baseband equipment is the same as
planned.
Rollback
Using MML commands
1.
Run the NodeB MML command MOD BASEBANDEQM to remove the newly
added baseband processing unit from the set of baseband equipment.
2.
Run the NodeB MML command MOD BASEBANDEQM to restore the original
configurations for the set of baseband equipment.

1.
2.
3.
7.3.4 Removing a Set of Baseband Equipment

This section describes how to remove a set of uplink baseband equipment and a set of downlink
baseband equipment.
Prerequisites
l
Issue 03 (2015-06-30)
Information
Description

deleted has been used in a local cell.
Local cell
Baseband equipment to which the local cell

belongs.

147
RAN17.1
N/A
N/A
License requirement
N/A
The resources of a baseband processing unit need to be released.
Context
The baseband equipment cannot be removed when being used by a cell.
Data Type
MO
Setting Notes
Data Source
MML
Command
Baseband
equipment
BASEBANDE
QM
List the
configuration of
a set of
baseband
equipment.
Network plan
LST
BASEBANDE
QM
Cell
ULOCELL
Add a local cell

according to the
network plan.
Network plan
ADD
ULOCELL
Procedure
l
Using MML commands

1.
Run the NodeB MML command RMV BASEBANDEQM to remove the specific set
of baseband equipment.

1.
Issue 03 (2015-06-30)

148
RAN17.1
2.
3.
Select the baseband equipment to be deleted in the upper part of area 2 and click
.
1.
file.
NOTE
2.
3.
CME.
NOTE
----End
Issue 03 (2015-06-30)

149
RAN17.1
Example
/*Removing a set of baseband equipment*/
RMV BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=ULDL;
Follow-up Procedure
l
Verification
1.
Expected result: The newly removed set of baseband equipment is not displayed in
the command output.
Rollback
Using MML commands
1.
Run the NodeB MML command ADD BASEBANDEQM to add the removed set
of baseband equipment.

1.
2.
3.
7.3.5 Adjusting the Networking of RF Units (Between Chain and

Ring Topologies)
This section describes how to adjust the networking of RF units between chain and ring
topologies.
Prerequisites
l
Issue 03 (2015-06-30)
Information
Description
RF module topology over the CPRI ports
Chain or ring topology used in the network.
New CPRI port numbers

unit and the CPRI port number.

150
RAN17.1
Information
Description

change

unit and the CPRI port number. The slot
No. and CPRI port No. are required for
rollback in the event of an adjustment
failure.
N/A
N/A
License requirement
N/A
The CPRI-based topology of RF units needs adjustment.
Context
NOTICE
Before changing CPRI ports used by RF units, ensure that the CPRI physical connection be
consistent with the data configuration. You can run the command LST RRUCHAIN to query
the configuration of the RRU/RFU chain or ring.
This is a high-risk MML command, and therefore exercise caution when you are adjusting the
CPRI networking mode:
l
To modify the configuration of a chain, a breakpoint must be set at the chain head. To
modify the configuration of a ring, ensure that a breakpoint is set at both the ring head and
tail.
Do not specify the parameter Topo Type when setting a breakpoint.
If a breakpoint is set on an RRU chain, the services carried by the RF modules between the
optical port at the chain head and the breakpoint are not interrupted. The services carried
on the RF modules behind the breakpoint are interrupted.
If two breakpoints are set on an RRU ring, the services carried by the RF modules between
the two breakpoints are interrupted. The services carried by the RF modules between the
optical port at the ring head/tail and the breakpoint may be interrupted.
Issue 03 (2015-06-30)

151
RAN17.1

Data
Type
MO
Setting Notes
Data
Source
MML
Comma
nd
RRU
Chain/
Ring
RRUCH
AIN
1. Set breakpoints on the RRU chain or ring:
Network
plan
MOD
RRUCH
AIN
l Set only one breakpoint for a chain

with the BreakPoint Position1
parameter set to 0.
l Set two breakpoints for a ring with the
BreakPoint Position1 and
BreakPoint Position2 parameters set
to 0 and a value equaling the number
of RRU cascading levels, respectively.
2. Determine the parameters to be modified
based on the CPRI networking mode and
slot for the board providing the CPRI ports
after reconfiguration. For details, see
Table 7-27 and Table 7-28.
3. Set the BreakPoint Position1 and
BreakPoint Position2 parameters to 255
to remove breakpoints from the RRU
chain or ring.
l

New CPRI
Port Position
Issue 03 (2015-06-30)
CPRI
Networking
Mode
Another CPRI
Chain
port on the same
Ring
baseband
processing
board
A CPRI port on
another
baseband
processing
board
Chain

target values.
Ring
Set Head Slot No., Tail Slot No., Head Port

No., and Tail Port No. to the target values based
on whether the new CPRI port number is the ring
head or tail port number.

152
RAN17.1

New CPRI
Port Position
CPRI
Networking
Mode
Another CPRI
Chain
port on the same
Ring
BBU

Procedure
l
Using MML commands

Ring-to-chain topology reconfiguration:
1.
Run the NodeB MML command MOD RRUCHAIN to set BreakPoint

Position1 and BreakPoint Position2 at the chain head and tail according to the
actual position of breakpoints.
2.
Perform the following operation onsite: Remove the CPRI cable of the RF unit
positioned at the ring tail.
3.
Run the NodeB MML command MOD RRUCHAIN to set Topo Type to
CHAIN.
4.
Run the NodeB MML command MOD RRUCHAIN to clear the breakpoint
configured in 1.
Chain-to-ring topology reconfiguration:
1.
Run the NodeB MML command MOD RRUCHAIN to set BreakPoint

Position1 at the chain head according to the actual position of breakpoints.
2.
Perform the following operation onsite: Insert the RF unit positioned at the chain
tail to the target optical port.
3.
Run the NodeB MML command MOD RRUCHAIN to set Topo Type to
RING.
4.
configured in 1.

Reconfiguring the ring topology into the chain topology:
1.
Issue 03 (2015-06-30)
Panel from the shortcut menu. A window is displayed in the right pane for you
to configure device data.

153
RAN17.1
Area 1
Device navigation tree. The cabinet navigation tree is in the upper

part and the RF unit navigation tree is in the lower part.
After you select the cabinet, subrack, or RF unit in the device
navigation tree, area 2 displays the device panel of the selected
device.
Area 2
2.
On the RXU Topology tab page, select the board connected to the RXU ring
3.
On the RXU Topology tab page, right-click the RXU ring for which you want
4.
In the topology node in the lower part of area 1, right-click the RXU chain to
be modified and choose Chain Properties from the shortcut menu to change
the networking mode.
5.
Click OK.
6.
Export the incremental script for data reconfiguration.

Planned Area > Export Incremental Scripts (CME client mode) or CME >
Planned Area > Export Incremental Scripts (U2000 client mode). Then,
For detailed function operations and introduction, press F1 on the CME to view
section Exporting Incremental Scripts from a Planned Data Area in the
U2000 Help.
7.
Issue 03 (2015-06-30)

154
RAN17.1
8.

U2000 Help.
NOTE
During script activation, you need to activate the incremental script for data reconfiguration
and incremental script for canceling breakpoints in sequence.
Reconfiguring the chain topology into the ring topology:

1.
Panel from the shortcut menu. A window is displayed in the right pane for you
to configure device data.
Area 1
Device navigation tree. The cabinet navigation tree is in the upper

part and the RF unit navigation tree is in the lower part.
navigation tree, area 2 displays the device panel of the selected
device.
Area 2
2.
Issue 03 (2015-06-30)
155
RAN17.1
3.
On the RXU Topology tab page, right-click the RXU chain for which you want
4.
In the topology node in the lower part of area 1, right-click the RXU chain to
be modified and choose Chain Properties from the shortcut menu to change
the networking mode.
5.
Click OK.
6.

U2000 Help.
7.

8.

U2000 Help.
NOTE
During script activation, you need to activate the incremental script for data reconfiguration
and incremental script for canceling breakpoints in sequence.
Batch configuration
1.
file.
NOTE
2.
3.
CME.
NOTE
----End
Issue 03 (2015-06-30)

156
RAN17.1
Example
/*Setting the breakpoints of the RRU ring*/
MOD RRUCHAIN: RCN=0, BRKPOS1=0;
/*Modifying the configurations*/
MOD RRUCHAIN: RCN=0, TT=RING, BM=COLD, HCN=0, HSRN=0, HSN=3, HPN=0, TCN=0,
TSRN=0, TSN=3, TPN=1;
/*Removing the breakpoints of the RRU ring*/
Follow-up Procedure
l
Verification
1.
Run the NodeB MML command LST RRUCHAIN to query the configuration of the
RRU chain or ring.
Expected result: The configuration of the RRU chain or ring is the same as planned.
Rollback
Using MML commands
Following the steps in Procedure to restore the initial configuration.
1.
2.
3.
7.3.6 Adjusting the Networking of RF Units (From Chain to Star

Topologies)
This section describes how to change the networking of RF units from the chain topology to star
topology.
Prerequisites
l
Issue 03 (2015-06-30)
Information
Description
CPRI topology
Configuration of the chain topology.
CPRI port number after adjustment

unit and the CPRI port number.

157
RAN17.1
Information
Description

change

unit and the CPRI port number. The slot
No. and CPRI port No. are required for
rollback in the event of an adjustment
failure.
N/A
N/A
License requirement
N/A
The CPRI-based topology of RF units needs adjustment.
Context
NOTICE
Before changing CPRI ports used by RF units, ensure that the CPRI physical connection be
consistent with the data configuration. You can run the command LST RRUCHAIN to query
the configuration of the RRU/RFU chain or ring.
This is a high-risk MML command, and therefore exercise caution when you are adjusting the
CPRI networking mode:
l
To modify the configuration of a chain, a breakpoint must be set at the chain head.
Do not specify the parameter Topo Type when setting a breakpoint.
If a breakpoint is set on an RRU chain, the services carried by the RF modules between the
optical port at the chain head and the breakpoint are not interrupted. The services carried
on the RF modules behind the breakpoint are interrupted.
Issue 03 (2015-06-30)
Data Type
MO
Setting Notes
Data
Source
MML
Command
RF unit
RRU
Required when an RF unit

needs to be added to an RRU/
RFU chain that requires
capacity expansion.
Network
plan
ADD RRU

158
RAN17.1
Data Type
MO
Setting Notes
Data
Source
MML
Command
RRU chain/
ring
RRUCHAIN
1. Set only one breakpoint

for an RRU chain with
BreakPoint Position1
parameter set to 0.
Network
plan
MOD
RRUCHAI
N
2. Determine the parameters

to be modified based on
the CPRI networking
mode and slot for the
board providing the CPRI
ports after
reconfiguration. For
details, see Table 7-30
and Table 7-31.
3. Clearing the breakpoint:
Set BreakPoint
Position1 to 255 to
remove the breakpoint.
l

New CPRI
Port Position
Issue 03 (2015-06-30)
CPRI
Networking
Mode
Another CPRI
Chain
port on the same
baseband
processing
board
A CPRI port on
another
baseband
processing
board

target values.
Chain

159
RAN17.1

New CPRI
Port Position
CPRI
Networking
Mode
Another CPRI
Chain
port on the same
BBU
Procedure
l
Using MML commands

1.
Run the NodeB MML command MOD RRUCHAIN to set a breakpoint on the RRU
chain according to the onsite configuration.
2.
Run the NodeB MML command RMV RRU to remove the RF unit that needs to be
configured to another CPRI chain.
3.
configured in Step 1.
4.
Run the NodeB MML command ADD RRUCHAIN to add a CPRI chain.
5.
Run the NodeB MML command ADD RRU to add the RF unit removed in Step 2 to
the CPRI chain added in Step 4.

1.
Issue 03 (2015-06-30)

160
RAN17.1
Area 1
navigation tree, area 2 displays the device panel of the selected device.
Area 2
2.
3.
On the RXU Topology tab page, right-click the RXU chain for which you want
4.
On the chain after the breakpoint, right-click the RF module to be configured on

another CPRI chain and choose Delete Board from the shortcut menu.
5.
Add an RXU chain.
6.
Issue 03 (2015-06-30)
a.
b.
Set the number and networking mode of the RXU chain based on the planned
data.
c.
Click OK.
Configure the RF module in 4 on the new CPRI chain in 5.

a.
In the lower left part of the device panel, right-click a configured RXU chain/
ring, and choose Add Board > Board Type from the shortcut menu. A dialog
box is displayed for you to add an RF board.
b.
Set the working mode and other related attributes for the RF board.
161
RAN17.1

NOTE
If the working mode of the RF module is UO, LO, or UL, when you set the number of RF
channels, you need to manually enter the RF specifications. Selecting RF specifications
from the RF specification list is not supported.
c.
7.
Click OK.

On the menu bar of the planned data area, choose Area Management > Planned
Area > Export Incremental Scripts (CME client mode) or CME > Planned
Area > Export Incremental Scripts (U2000 client mode). Then, export
configuration scripts.
U2000 Help.
8.
On the RXU Topology tab page, right-click a configured breakpoint and choose
Cancel Break Point from the shortcut menu.
9.

On the menu bar of the planned data area, choose Area Management > Planned
Area > Export Incremental Scripts (CME client mode) or CME > Planned
Area > Export Incremental Scripts (U2000 client mode). Then, export
configuration scripts.
U2000 Help.
NOTE
During script activation, you need to activate the incremental script for data reconfiguration and
incremental script for canceling breakpoints in sequence.
Batch configuration
1.
file.
NOTE
2.
3.
CME.
NOTE
----End
Issue 03 (2015-06-30)

162
RAN17.1
Example
/*Set the breakpoint on the RRU chain*/
/*Removing the breakpoint of the RRU chain*/
/*Adding an RRU chain*/
ADD RRUCHAIN: RCN=1, TT=CHAIN, BM=COLD, HCN=0, HSRN=0, HSN=3, HPN=1;
/*Removing an RRU with the parameter settings as follows*/
RMV RRU: CN=0, SRN=60, SN=0
/*Adding an RF unit with the parameter settings as follows*/
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=0, PS=0, RT=MRRU, RS=UO,
RXNUM=2, TXNUM=2, ALMPROCSW=ON, ALMPROCTHRHLD=30, IFOFFSET=0, RFDS=0,
SCR=6.1;
Follow-up Procedure
l
Verification
1.
Run the NodeB MML command LST RRUCHAIN to query the configuration of the
RRU chain.
Expected result: The configuration of the RRU chain is the same as planned.
2.
Run the NodeB MML command LST RRU to query the RRU/RFU configuration.
Expected result: The RRU/RFU configuration is the same as planned.
Rollback
Using MML commands
Following the steps in Procedure to restore the initial configuration.
1.
2.
3.
7.4 Transport Data Reconfiguration

This chapter describes how to reconfigure NodeB transport data in typical scenarios.
7.4.1 Replacing the U2000

This section describes the application scenario, procedure, verification, and rollback for
replacing a U2000.
Prerequisites
l
Issue 03 (2015-06-30)

163
RAN17.1

Information
Description
Route from the NodeB to the new U2000
Includes the next-hop IP address,

destination IP address, subnet mask, and
route priority.
IP address and subnet mask for the new

U2000
l If the new U2000 uses multi-server

load-sharing (SLS), you need to obtain
the IP address segment and subnet mask
of the network segment where the
master server is located. The master,
slave, and standby servers of the U2000
are in the same network segment.
l If the new U2000 does not use SLS, you
need to obtain the IP address and
network segment of the new U2000.
NodeB version
Includes the NodeB version and mediation

software version.
U2000 Server: If no U2000 has been deployed, prepare the server for deploying the
U2000.
U2000 software: If no U2000 has been deployed, prepare the U2000 software for the
target NodeB version for deploying the U2000.
NE mediation software: NE mediation software is used by the U2000 to adapt to
different NEs of different versions. With NE mediation software, the U2000 can obtain
and recognize data reported by NEs through their interfaces.
License requirement
N/A
When the U2000 or NodeB deployment is modified, the U2000 may need to be replaced.
Context
Determine the reconfiguration scheme according to Table 7-32.
Table 7-33 Scheme options
Issue 03 (2015-06-30)
If...
Then...
The device IP addresses of the existing

NodeBs cannot meet requirements when both
old and new U2000s exist
New device IP addresses need to be

configured on the NodeB.

164
RAN17.1
If...
Then...
No route is available between the NodeB and

the added U2000
Add a route between the NodeB and the added

U2000.
NOTE
The network segment on which the NodeB is
located can be obtained based on the values of
Mask and IP Address of the corresponding
Ethernet port.
An IP route has been added
Remove the route between the NodeB and the

old U2000.
New device IP addresses have been added
Remove the original device IP address.

NOTE
This document does not describe how to configure the new U2000. For details, see related U2000 documents.

Data Type
MO
Setting Notes
Data
Source
MML
Command
IP address
DEVIP
l Configure the device IP

address for
communicating with the
new U2000.
Network
plan
ADD
DEVIP
Network
plan
ADD IPRT
Network
plan
MOD
OMCH
l Delete the IP address for

old U2000.
IP route
IPRT
l If the new U2000 uses

SLS, set Destination IP
to the IP address segment
of the network segment
where the new U2000
master server is located.
l If the new U2000 does not
use SLS, set Destination
IP to the address of the
new U2000.
l Remove the IP route for
old U2000.
Remote
maintenance
channel
Issue 03 (2015-06-30)
OMCH
Set Peer IP to the IP address

of the new U2000.

165
RAN17.1
Procedure
l

1.
Run the NodeB MML command ADD DEVIP to add a device IP address for the
NodeB.
2.
Run the NodeB MML command ADD IPRT to add a route from the NodeB to the
new U2000.
3.
Run the NodeB MML command MOD OMCH to change the remote maintenance
channel.
4.
Run the NodeB MML command RMV IPRT to remove the IP route from the NodeB
to the old U2000.
5.
Run the NodeB MML command RMV DEVIP to remove the old device IP address.

1.
2.
Batch configuration
1.
Issue 03 (2015-06-30)
166
RAN17.1
file.
NOTE
2.
3.
CME.
NOTE
----End
Example
/*Configuring a new device IP address*/
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="172.31.13.18",
MASK="255.255.255.0";
/*Adding an IP route from the NodeB to the U2000*/
ADD IPRT: RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="10.148.36.103",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="172.31.13.1";
/*Changing the remote maintenance channel of the NodeB*/
MOD OMCH: FLAG=MASTER, IP="172.31.13.18", MASK="255.255.255.0",
PEERIP="10.148.36.103", PEERMASK="255.255.255.0", BEAR=IPV4, BRT=NO;
/*Removing the IP route between the NodeB and the old U2000*/
RMV IPRT: RTIDX=1;
/*Removing the old device IP address of the NodeB*/
RMV DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="172.31.13.15";
Follow-up Procedure
l
Verification
1.
Check whether ALM-25901 Remote Maintenance Link Failure is reported.

If this alarm is reported, clear the alarm according to 3900 Series Base Station Alarm
Reference.
Rollback
If the reconfiguration fails, the OM channel will be interrupted. In this case, engineering
rollback can be performed only using the LMT. Before a rollback, upload the original
configuration file to the FTP server.
1.
On the NodeB LMT, download and activate the original configuration file.
a.
Run the NodeB MML command DLD CFGFILE to download the

configuration file to the NodeB.
For example:
DLD CFGFILE: MODE=IPV4, IP="192.169.2.16", USR="admin",
PWD="*****";
Issue 03 (2015-06-30)

167
RAN17.1
b.
Run the NodeB MML command ACT CFGFILE to active the configuration
file.
For example:
ACT CFGFILE: EFT=IMMEDIATELY;
2.
Restore the physical connections.
3.
Verify the engineering rollback according to instructions inVerification.

1.
2.
3.
l
Troubleshooting
Issue 1: ALM-25901 Remote Maintenance Link Failure is reported on the NodeB.
7.4.2 Adjusting the VLAN Priority

This section describes the application scenario, procedure, verification, and rollback for
adjusting the priority of a VLAN.
Prerequisites
l
Information
Description
VLAN mode
VLAN Mode of the live network, which

can be single VLAN or VLAN group.
Differentiated services code point (DSCP)
DSCP of a VLAN when the VLAN works

in VLAN group mode.
Set VLAN priority
Set VLAN Priority of a VLAN when the

VLAN works in single VLAN mode.
N/A
N/A
Issue 03 (2015-06-30)

168
RAN17.1

N/A
Changes in transmission equipment and network scale in the operation and maintenance stage
require an optimization of transmission network QoS management and adjustment in the
mapping between different types of services and VLAN priorities.
Context
Prepare the following data according to Table 7-35.
l
Single VLAN mode: mapping between the DSCP and VLAN priority.
VLAN group mode: mapping between the DSCP and VLAN priorities for user data,
mapping between DSCPs and VLAN priorities for signaling data, high-priority OM data,
low-priority OM data, and other types of data.
NOTICE
Ensure that the number of VLAN priorities is no more than that of the VLAN priorities supported
by the customer's network equipment. To query VLAN priority mapping, perform the following
steps:
l
For single VLAN mode, the number of VLAN priorities must be smaller than that supported
by the customer's network equipment.
For VLAN group mode, the total number of VLAN priorities for all types of services must
be smaller than that supported by the customer's network equipment.
Procedure
1.
2.
3.
Issue 03 (2015-06-30)
Collect required information before adjusting the VLAN priority.

a.
Run the NodeB MML command LST VLANMAP to query the next-hop VLAN
mapping configuration.
b.
Run the NodeB MML command LST VLANCLASS to query the user data
service priority configured in the VLANCLASS MO.
If the current VLAN mode is single VLAN, Set VLAN Priority is set to ENABLE
(Enable), and multiple VLAN priorities are required after the reconfiguration:
a.
Run the NodeB MML command MOD VLANMAP to set Set VLAN
Priority to DISABLE(Disable).
b.
Run the NodeB MML command SET DSCPMAP to set Differentiated Service
Codepoint and VLAN Priority according to the planned mapping between the
DSCP and VLAN priority.
If the current VLAN mode is single VLAN and Set VLAN Priority is set to DISABLE
(Disable):
169
RAN17.1
a.
4.
Run the NodeB MML command SET DSCPMAP to set Differentiated Service
Codepoint and VLAN Priority according to the planned mapping between the
DSCP and VLAN priority.
If the current VLAN mode is VLAN group:

a.
Run the NodeB MML command MOD VLANCLASS to configure the mapping
between User Data Service Priority and VLAN Priority according to the
planned mapping between the DSCP and VLAN priorities for user data and to
set the VLAN priorities for different types of services according to the planned
mapping between DSCPs and VLAN priorities for signaling data, high-priority
OM data, low-priority OM data, and other types of data.

1.
2.
Batch configuration
1.
Issue 03 (2015-06-30)
file.
170
RAN17.1

NOTE
2.
3.
CME.
NOTE
----End
Example
//If the VLAN mode is single VLAN and VLAN priority is set before
reconfiguration
ADD VLANMAP: NEXTHOPIP="192.168.1.10", MASK="255.255.255.255",
VLANMODE=SINGLEVLAN, VLANID=1024, SETPRIO=ENABLE, VLANPRIO=0;
//If VLAN priority is not used in the VLANMAP MO and the mapping between
a DSCP and a VLAN priority is configured
MOD VLANMAP: NEXTHOPIP="192.168.1.10", MASK="255.255.255.255",
VLANMODE=SINGLEVLAN, VLANID=1024, SETPRIO=DISABLE;
SET DSCPMAP: VRFIDX=0, DSCP=0, VLANPRIO=0;
Follow-up Procedure
l
Verification
1.
Run the NodeB MML command LST DSCPMAP to query the mapping configuration
between the DSCPs and VLAN priorities.
Expected result: The mapping between the DSCPs and VLAN priorities is the same
as planned.
2.
Run the NodeB MML command LST VLANCLASS to query the mapping between
DSCPs of different types of services and VLAN priorities.
Expected result: The mapping between DSCPs of different types of services and
VLAN priorities is the same as planned.
Rollback
Issue 03 (2015-06-30)
1.
Run the NodeB MML command MOD VLANMAP to set Set VLAN Priority to
the original value.
2.
Run the NodeB MML command MOD VLANCLASS to set VLAN Priority to
the original value for different types of services.
171
RAN17.1
3.
Run the NodeB MML command SET DSCPMAP to restore the original mapping
between Differentiated Service Codepoint and VLAN Priority.

1.
2.
3.
7.4.3 Changing the VLAN Configuration Mode

This section describes how to change the VLAN configuration mode from VLAN group to single
VLAN.
Prerequisites
Before changing the VLAN configuration mode from VLAN group to single VLAN, check
whether the current VLAN group configuration meets the following conditions:
l
The VLANs in a VLAN group are not isolated.
The Differentiated Service Codepoint (DSCP) value varies with service types in a VLAN
group. Service types of the same DSCP value must have the same VLAN priority.
After the VLAN configuration mode is changed to the single VLAN mode, the number of
VLAN priorities is no more than that of the VLAN priorities supported by the customer's
network equipment.
NOTE
l Generally, the customer's equipment supports eight VLAN priorities. In this case, this condition check
can be ignored.
l In single VLAN mode, different VLAN priorities are recommended for service flows. This section
does not describe how to modify the single VLAN mode.
Before changing the VLAN configuration mode, collect information listed in Table 7-36.
Issue 03 (2015-06-30)
Information
Description
VLAN ID
VLAN ID in the VLAN group
DSCP
DSCP values for user data, signaling data,

high-priority OM data, low-priority OM
data, and other data in the VLAN group
VLAN priority
VLAN priorities of user data, signaling

data, high-priority OM data, low-priority
OM data, and other data in the VLAN
group

172
RAN17.1

Data Type
Data
Data Source
User data in the VLAN

group
VLAN ID
Value of VLAN ID in the

VLANCLASS MO
DSCP
Value of User Data

Service Priority in the
VLANCLASS MO
VLAN priority
Value of VLAN Priority in

the VLANCLASS MO
VLAN ID

VLANCLASS MO
DSCP
Value of Signaling
Priority in the DIFPRI
MO
VLAN priority

the VLANCLASS MO
VLAN ID

VLANCLASS MO
DSCP
Value of OM High
MO
VLAN priority

the VLANCLASS MO
VLAN ID

VLANCLASS MO
DSCP
Value of OM Low
MO
VLAN priority

the VLANCLASS MO
VLAN ID

VLANCLASS MO
Signaling data information

in the VLAN group
High-priority OM data
configuration in the VLAN
group
Low-priority OM data
configuration in the VLAN
group
Configuration of other data

(including BFD packets,
IKE packets, clock packets,
ARP packets, and ICMP
packets) in the VLAN
group
Issue 03 (2015-06-30)

173
RAN17.1
Data Type
Data
Data Source
DSCP
l Value of DSCP in the

BFDSESSION MO
(BFD packets)
l Value of DSCP in the
IKECFG MO (IKE
packets)
l Value of IP Clock
Priority in the
DIFPRI MO (clock
packets)
l No DSCP value is set
for ARP packets.
l The DSCP value
obtained by running the
ping command is used
for the ICMP packets.
VLAN priority
The VLAN priority for

other data is not required.
When the VLAN
configuration mode is
changed from the VLAN
group mode to the single
VLAN mode, the VLAN
priority for other data is
directly mapped to the
DSCP value in the single
VLAN specified by the
value of VLAN Priority in
the DSCPMAP MO.
NOTE
No DSCP value is set for ARP
packets. In single VLAN
mode, the VLAN priority for
ARP packets is automatically
set to 7.
Table 7-38 lists the information collected based on the preceding table. You need to check
whether the collected information meets the modification requirements.
The VLANs in a VLAN group are not isolated. Check whether the VLAN IDs of all
service types in a VLAN group are the same. If yes, VLANs in the VLAN group are
not isolated. If no, VLANs in the VLAN group are isolated.
The DSCP value varies with service types in a VLAN group. Service types of the same
DSCP value must have the same VLAN priority. Check whether the data of different
VLAN priorities has the same DSCP value based on the values of the DSCP and VLAN
Priority columns in Table 7-38.
Issue 03 (2015-06-30)

174
RAN17.1
Table 7-38 Information collected

VLANM
AP
VLANCL
ASS
Service
Type
VLANID
DSCP
VLAN
Priority
IP1/
MASK1
VLAN
group 1
User data
20
30
38
48
...
...
...
...
...
Signaling
data
48
OMH
46
OML
18
OTHER
DSCP
value of
BFD
packets
...
...
DSCP
value of
IKE
packets
...
...
DSCP
value of
clock
packets
...
...
DSCP
value of
ICMP
packets
...
...
ARP
In single
VLAN
mode, the
VLAN
priority is
automatical
ly set to 7.
...
...
...
...
...
...
...
...
...
...
...
...
IP2/
MASK2
Issue 03 (2015-06-30)
VLAN
group 2

175
RAN17.1
VLANM
AP
...
VLANCL
ASS
...
Service
Type
VLANID
DSCP
VLAN
Priority
...
...
...
...
...
...
...
...
...
...
...
...
None
None
License requirement
None
Context
Data
Type
MO
Setting Notes
Data Source
MML Command
Differenti
ated
Service
Codepoin
t and
VLAN
Priority
DSCPMA
P
Based on
Information
Collection, change
the values of
DSCP and VLAN
Priority to the
target values.
User plan
SET DSCPMAP
VLAN
Mode,
VLAN ID,
and Set
VLAN
Priority
VLANM
AP
1. Set VLAN
Mode to
SINGLEVLA
N(Single
VLAN).
User plan
MOD VLANMAP
2. Set VLAN ID
based on
Information
Collection.
3. Set Set VLAN
Priority to
DISABLE
(Disable).
Issue 03 (2015-06-30)

176
RAN17.1
After the single VLAN mode is used, check whether the number of VLAN priorities is no more
than that of the VLAN priorities supported by the customer's network equipment by performing
the following steps:
1.
After configuring DSCPMAP, check the data preparation table to confirm the number of
VLAN priorities to be configured.
2.
Based on the DSCPMAP configuration to be modified, check VLAN Priority for other
data in VLAN group mode.
3.
Check whether the total number of VLAN priorities obtained in steps 1 and 2 is less than
or equal to that of the VLAN priorities supported by the customer's network equipment.
Using MML commands
Procedure
1.
Collect required information.

a.
Run the NodeB MML command LST VLANMAP to query the mapping
between next-hop IP addresses and VLANs.
b.
Run the NodeB MML command LST VLANCLASS to query the mapping
between DSCP values and VLAN priorities for user data in VLANCLASS and
the VLAN priorities for signaling data, high-priority OM data, and low-priority
OM data.
c.
Run the NodeB MML command LST DIFPRI to query the configured signaling
priority, high-priority OM data priority, and low-priority OM data priority.
2.
Run the NodeB MML command SET DSCPMAP to modify the DSCP value and
VLAN priority in DSCPMAP based on DSCPMAP in Data preparation.
3.
Run the NodeB MML command MOD VLANMAP to change the values of VLAN
Mode, VLAN ID, and Set VLAN Priority to SINGLEVLAN(Single VLAN),
VLANID in VLANCLASS, and DISABLE(Disable), respectively, based on
VLANMAP in Data preparation.
4.
After the modification is complete, remove the VLAN group configuration.

a.
Run the NodeB MML command LST VLANCLASS to query all configured
mappings between VLAN priorities and DSCP values.
b.
Run the NodeB MML command RMV VLANCLASS to remove all mappings
between VLAN priorities and DSCP values.

1.
Issue 03 (2015-06-30)

177
RAN17.1
2.
Batch configuration
1.
file.
NOTE
2.
3.
CME.
NOTE
----End
Issue 03 (2015-06-30)

178
RAN17.1
Example
//Setting the mapping between DSCP values and VLAN priorities based on the
DSCPMAP MO configuration in data preparation
SET DSCPMAP: DSCP=10, VLANPRIO=1;
//Modifying the values of VLAN Mode, VLAN ID, and Set VLAN Priority based
on the VLANMAP MO configuration in data preparation
MOD VLANMAP: NEXTHOPIP="10.10.10.10", MASK="255.255.255.255",
VLANMODE=SINGLEVLAN, VLANID=1024, SETPRIO=DISABLE;
//Removing the
complete
RMV VLANCLASS:
RMV VLANCLASS:
RMV VLANCLASS:
RMV VLANCLASS:
RMV VLANCLASS:
RMV VLANCLASS:
RMV VLANCLASS:
RMV VLANCLASS:
RMV VLANCLASS:
RMV VLANCLASS:
RMV VLANCLASS:
RMV VLANCLASS:
RMV VLANCLASS:
RMV VLANCLASS:
RMV VLANCLASS:
VLAN group configuration after the modification is

TRAFFIC=SIG;
TRAFFIC=OM_HIGH;
TRAFFIC=OM_LOW;
TRAFFIC=OTHER;
TRAFFIC=USERDATA,
TRAFFIC=USERDATA,
TRAFFIC=USERDATA,
TRAFFIC=USERDATA,
TRAFFIC=USERDATA,
TRAFFIC=USERDATA,
TRAFFIC=USERDATA,
TRAFFIC=USERDATA,
TRAFFIC=USERDATA,
TRAFFIC=USERDATA,
TRAFFIC=USERDATA,
SRVPRIO=20;
SRVPRIO=30;
SRVPRIO=40;
SRVPRIO=50;
SRVPRIO=51;
SRVPRIO=52;
SRVPRIO=53;
SRVPRIO=54;
SRVPRIO=55;
SRVPRIO=56;
SRVPRIO=57;
Follow-up Procedure
l
Verification
1.
Run the NodeB MML command LST DSCPMAP to query the mapping configuration
between DSCP values and VLAN priorities.
Expected result: The mapping configuration between DSCP values and VLAN
priorities is consistent with the network plan.
2.
Run the NodeB MML command LST VLANMAP to query the mapping between
next-hop IP addresses and VLANs.
Expected result: The mapping between next-hop IP addresses and VLANs is
consistent with the network plan.
Rollback
Using MML commands
Issue 03 (2015-06-30)

179
RAN17.1
1.
Run the NodeB MML command MOD VLANMAP to change the value of VLAN
Mode to VLANGROUP(VLAN Group) and restore VLAN Group No. to the
original configuration.

1.
2.
3.
7.5 Reconfigurations Dedicated to the LampSite Solution

This section provides guidelines for typical reconfigurations dedicated to the LampSite solution.
7.5.1 Adding a pRRU

This section describes how to add a pRRU for service adjustment or capacity expansion.
Prerequisites
l
Before the reconfiguration, collect information listed inTable 7-40.
Information
Description
RF unit type
The RF unit is a pRRU.
Connection between pRRU and RHUB
Electrical port connection between the

pRRU and RHUB
The pRRUs and RHUB are installed and running properly. For details, seeInstalling
an RHUB and Installing a pRRU in DBS3900 LampSite Installation Guide.
N/A
License requirement
N/A
l
Issue 03 (2015-06-30)
The RF resources are insufficient.

180
RAN17.1
The coverage planning requires adjustment in the target area.
Context
A pRRU can be added for service adjustment or capacity expansion. For example, a frequency
band is added or a sector is expanded. After a pRRU is added, its maximum transmit power can
be locked if required.
NOTE
The pRRU does not support the following parameter settings: VSWR alarm post-processing switch,
VSWR alarm post-processing threshold, VSWR alarm threshold, IfOffset, RF Desensitivity, Low
Current Protect Switch, ALD Reuse Flag, RU Specification, and PA Efficiency Improvement
Switch.
After a pRRU is added, carrier resources can be configured according to the configuration principles in
Independent Demodulation of Signals from Multiple Small Cell RRUs in One Cell Feature Parameter
Description.
To add a pRRU, RRU Topo Position can be set only to BRANCH(Branch) and the position of the pRRU
must be the same as the RHUB to which it connects in a chain or ring.

Data Type
MO
Setting Notes
Data Source
MML
Command
RRU chain/ring
RRUCHAIN
Add a pRRU
chain.
Network plan
ADD
RRUCHAIN
RF unit
RRU
Add a pRRU.
Network plan
ADD RRU
Sector
equipment
SECTOREQM
Add a sector
equipment.
Network plan
ADD
SECTOREQM
Sector
equipment
group
ULOCELLSEC
TOREQMGRP
Add a sector
equipment
group.
Network plan
ADD
ULOCELLSE
CTOREQMG
RP
Sector
equipment used
by sector
equipment
group
ULOCELLSEC
TOREQMGRPI
TEM
Add a sector
equipment to a
specified sector
equipment
group.
Network plan
ADD
ULOCELLSE
CTOREQMG
RPITEM
NOTE
l
base station.
Issue 03 (2015-06-30)

181
RAN17.1
Procedure
l

1.
Run the NodeB MML command ADD RRUCHAIN to add a pRRU chain connecting
to the RHUB.
2.
Run the NodeB MML command ADD RRU to add a pRRU to the pRRU chain created
in Step 1.
3.
Run the NodeB MML command ADD SECTOR to add a sector.
4.
Run the NodeB MML command ADD SECTOREQM to add a sector equipment.
5.
Optional: Run the NodeB MML command ADD ULOCELLSECTOREQMGRP

to add the sector equipment added in Step 4 to a local cell.
6.
Optional: Run the NodeB MML command ADD

ULOCELLSECTOREQMGRPITEM to add the sector equipment added in Step
4 to the specified existed sector equipment group.

1.
Area 1
Issue 03 (2015-06-30)

182
RAN17.1
Area 2
2.
Add a chain/ring and an RF module.

.a
BUHR kcilc-thgir ,lenap ecived eht fo trap tfel rewol eht ni weiv ygolopot eht nI
esoohc dnaOPOT BUHR nepO.unem tuctrohs eht morf
.b
weiv ygolopot BUHR eht ni ecafretni na kcilc-thgir ,atad dennalp eht no desaB
esoohc dnaniahC ddAtes ,xob golaid deyalpsid eht nI .unem tuctrohs eht morf
eht hcihw ot draob eht no trop eht dna ,edom gnikrowten ,rebmun knil UXR eht
.detcennoc si knil UXR
.c
kcilCKO.
.d
ni nwohs aera eht ni kcilc-thgiR32-7 erugiF esoohc dna draoB ddA<

UMPM.unem tuctrohs eht morf
32-7 erugiFygolopot BUHR
.e
3.
Add sectors and sector equipment.

a.
Issue 03 (2015-06-30)
kcilc dna setubirtta UMPM tes ,xob golaid deyalpsid eht nIKO.

183
RAN17.1
b.
In area 1, select or search for the MO you want to configure based on the
following list and double-click the MO. In area 2, set parameters for the MO and
click
----End
Example
/*Adding a pRRU chain*/
ADD RRUCHAIN: RCN=1, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=60, HSN=0,
HPN=0;
/*Adding a pRRU*/
ADD RRU: CN=0, SRN=61, SN=0, TP=BRANCH, RCN=1, PS=0, RT=MPMU, RS=UO,
RXNUM=0, TXNUM=0;
/*Adding the pRRU to a sector*/
ANT1N=R0A, CREATESECTOREQM=FALSE;
/*Adding the pRRU to a sector equipment*/
ANT1SN=1, ANT1N=R0A, ANTTYPE1=RXTX_MODE;
/*Optional: Adding the sector equipment to a local cell*/
ADD ULOCELLSECTOREQMGRP: ULOCELLID=0, SECTOREQMGRPID=0, SECTOREQMID=0;
/*Optional: Adding the sector equipment to the specified existed sector
equipment group*/
ADD ULOCELLSECTOREQMGRPITEM: ULOCELLID=0, SECTOREQMGRPID=0,
SECTOREQMID=0;
Follow-up Procedure
l
Issue 03 (2015-06-30)
Verification
184
RAN17.1
1.
Run the NodeB MML command LST RRU to query the reconfigured pRRU.
Expected result: The configuration of this pRRU is the same as configured.
2.
Run the NodeB MML command DSP BRD to query the state of the pRRU.
Expected result: Availability Status is Normal.
3.
Run the NodeB MML command LST ULOCELL to query the information about the
local cell.
Expected result: The sector equipment is added for the local cell.
Rollback
1.
Optional: Run the NodeB MML command RMV

ULOCELLSECTOREQMGRP to remove the newly added sector equipment
group from the local cell.
2.

ULOCELLSECTOREQMGRPITEM to remove the newly added sector
equipment from the sector equipment group.
3.
Run the NodeB MML command RMV SECTOREQM to remove the newly
added sector equipment.
4.
Run the NodeB MML command RMV SECTOR to remove the newly added
sector.
5.
Optional: If the maximum transmit power of the pRRU is locked, run the NodeB
MML command LOC RRUTC to unlock the maximum transmit power. In this
step, set Maximum Output Power Support Setting of the TX Channel to 0.
6.
Run the NodeB MML command MOD RRUCHAIN to set the breakpoint on the
pRRU chain.
7.
Run the NodeB MML command RMV RRU to remove the newly added pRRU.
8.
Run the NodeB MML command MOD RRUCHAIN to clear the breakpoint.

1.
2.
3.
l
Troubleshooting
Hardware Fault are reported.
7.5.2 Adding an RHUB

This section describes how to add a RF unit for service adjustment or capacity expansion.
Issue 03 (2015-06-30)

185
RAN17.1
Prerequisites
l
Information
Description
RF unit type
The RF unit is an RHUB.
Connection between RHUB and BBU
Optical port connection between the

RHUB and interface board.
The RHUB is installed and running properly. For details, see Installing an RHUB in
DBS3900 LampSite Installation Guide.
N/A
License requirement
N/A
l
The RF resources are insufficient.
The coverage planning requires adjustment in the target area.
Context
A pRRU can be added for service adjustment or capacity expansion. For example, a frequency
band is added or a sector is expanded. After a pRRU is added, its maximum transmit power can
be locked if required.
NOTE
After a pRRU is added, carrier resources can be configured according to the configuration principles in
Independent Demodulation of Signals from Multiple Small Cell RRUs in One Cell Feature Parameter
Description.
Issue 03 (2015-06-30)
Data Type
MO
Setting Notes
Data
Source
MML
Command
RRU chain/
ring
RRUCHAIN
Add a pRRU chain.
Network
plan
ADD
RRUCHAI
N

186
RAN17.1
Data Type
MO
Setting Notes
Data
Source
MML
Command
Breakpoint
RRUCHAIN
During expansion of
cascading levels for the RRU
chain, if you need to add RF
modules in the middle of the
chain, then set a breakpoint
and clear the breakpoint.
Network
plan
MOD
RRUCHAI
N
Network
plan
ADD RHUB
l Setting a breakpoint: Set

BreakPoint Position1
according to the actual
position of breakpoints.
l Clearing the breakpoint:
Set BreakPoint
Position1 to 255.
RF unit
RHUB
Add an RHUB.
NOTE
l
base station.
Using MML commands
Procedure
1.
Optional: Run the NodeB MML command ADD RRUCHAIN to add an RHUB chain
for connecting to the BBU.
2.
Optional: Run the NodeB MML command MOD RRUCHAIN to set a breakpoint
on the RHUB chain added in Step 1.
3.
Run the NodeB MML command ADD RHUB to add an RHUB.
4.
Optional: Run the NodeB MML command MOD RRUCHAIN to clear the
breakpoint configured in Step 2.

1.
Issue 03 (2015-06-30)

187
RAN17.1
Area 1
Area 2
2.
3.
Add an RXU chain.

a.
b.
Based on the planned data, set the related information such as the number and
networking mode of the RXU chain and the port on the board to which the RXU
chain is connected.
c.
Click OK. The configured RXU chain is displayed under the TOPO node.
Add an RHUB.
a.
Right-click the new RXU chain/ring and choose Add Board > RHUB from the
shortcut menu.
b.
Configure RHUB attributes based on the planned data and click OK.
----End
Issue 03 (2015-06-30)

188
RAN17.1
Example
/*Adding a pRRU chain*/
ADD RRUCHAIN: RCN=1, TT=CHAIN, BM=COLD, HCN=0, HSRN=0, HSN=3, HPN=1;
/*Setting a breakpoint on the pRRU chain*/
/*Adding an RHUB*/
ADD RHUB: SRN=60, RCN=1, PS=0;
/*Clearing the breakpoint*/
Follow-up Procedure
l
Verification
1.
Run the NodeB MML command LST RHUB to check the RHUB configuration.
Expected result: The RHUB configuration is the same as planned.
2.
Run the NodeB MML command DSP BRD to query the state of the RHUB.
Expected result: Availability Status is Normal.
Rollback
Using MML commands
1.
Run the NodeB MML command MOD RRUCHAIN to set the breakpoint on the
RHUB chain.
2.
Run the NodeB MML command RMV RHUB to remove the newly added RHUB.
3.
configured in 1.

1.
2.
3.
l
Troubleshooting
Hardware Fault are reported.
7.5.3 Adding a pRRU-Aggregation Cell

This section describes the application scenario, reconfiguration procedure, engineering
verification, and engineering rollback for adding a pRRU-aggregation cell.
Prerequisites
l
Issue 03 (2015-06-30)

189
RAN17.1

Information
Description
Cell information
l Basic information about the cell to be added.

l TX and RX mode. pRRU-aggregation cells support 1T1R
or 2T2R mode.
Baseband processing
board type
The type of the Baseband Processing Units. For example, the

WBBPf3, WBBPf4, or UBBPd.
Main control board

type
LampSite supports only UMPTb1 and UMPTb2.
RF unit
l Types of newly added RF units. pRRU-aggregation cells

support only the MPMU.
l Connections between pRRUs and RHUBs.
Network topology
Network topology of pRRU-aggregation cells.

NOTE
pRRU-aggregation cells support only the chain topology. Set RRU
Topo Position to BRANCH(BRANCH).
Sector equipment
group
Values of the Sector Equipment Group ID and Sector

equipment ID parameters in the EuSectorEqmGroup MO.
Reference signal power
pRRU reference signal power.
New pRRUs and the cables and optical modules for these pRRUs.
If baseband processing units are insufficient, new baseband processing units are
required.
If the RHUB resources are insufficient, new RHUBs and cables and optical modules
for these RHUBs are required.
N/A
License requirement
Table 7-43 lists the license control items to be prepared.
Table 7-43 License control items to be prepared
Issue 03 (2015-06-30)
License Control Item
Description
WCDMA Multi-Carrier License for

LampSite pRRU (Per Carrier)
WCDMA Multi-Carrier License for

LampSite pRRU
Independent Demodulation of Signals

from Multiple Small Cell RRUs in One
Cell (per Cell*pRRU Group)
Independent Demodulation of Signals

from Multiple Small Cell RRUs in One
Cell

190
RAN17.1
In office buildings, subways, residential areas, shopping malls, and other subscriberconcentrated areas, pRRU-aggregation cells need to be added to satisfy the service quality
requirements of indoor subscribers in these areas.
Context
Local operations refer to the operations that must be performed onsite, such as board installation
or operations on the LMT.
Remote operations refer to the operations that must be performed on the operation and
maintenance center, such as reconfiguring parameters using the U2000.
Data Type
MO
Setting Notes
Data Source
MML
Command
Sector
SECTOR
Set this MO as
planned.
Network plan
ADD SECTOR
Sector
equipment
SECTOREQM
One pRRU
forms a set of
sector
equipment.
Network plan
ADD
SECTOREQM
Cell
ULOCELL
Add a cell with

multiple
pRRUs. To add
a pRRUaggregation cell,
configure only
one set of sector
equipment for
each sector
equipment
group.
Network plan
ADD
ULOCELL
Sector
equipment in a
sector
equipment
group
ULOCELLSEC
TOREQMGRPI
TEM
If a sector
equipment
group has more
than one set of
sector
equipment, you
need to add the
sector
equipment.
Network plan
ADD
ULOCELLSE
CTOREQMG
RPITEM
Procedure
l
Issue 03 (2015-06-30)
Local operations:
191
RAN17.1
1.
Install the baseband processing units in the BBU subrack.
2.
Install the RHUB. For details, see DBS3900 LampSite Installation Guide.
3.
Install a pRRU. For details, see DBS3900 LampSite Installation Guide.
4.
Install the CPRI optical fibers and cables. For details, see DBS3900 LampSite
Installation Guide.
Remote operations:
1.
Run the NodeB MML command ADD SECTOR to add a sector. In this step,
ensure that the number of sector is equal to that the number of pRRUs.
2.
Run the NodeB MML command ADD SECTOREQM to add a set of sector
equipment. In this step, ensure that the number of sector equipment is equal to that
the number of pRRUs.
3.
Run the NodeB MML command ADD BASEBANDEQM to add a set of baseband
equipment.
4.
Run the NodeB MML command ADD ULOCELL to add a LampSite cell.
5.
Run the NodeB MML command ADD ULOCELLSECTOREQMGRPITEM

to add the sector equipment to the sector equipment group.

1.
Select a base station in the left pane of the planned data area. The NE object
tree is displayed in the lower part of the left pane, as shown in the following
figure:
Issue 03 (2015-06-30)

192
RAN17.1
2.
following list and double-click the MO. In area 2, set parameters for the MO
and click
Batch configuration
1.
Data > Export Base Station Bulk Configuration Data (CME client mode)
or CME > UMTS Application > Export Data > Export Base Station Bulk
Configuration Data (U2000 client mode). Then, export data from the CME
to a file.
NOTE
2.
Open the exported file saved on the local PC and reconfigure data in the file
based on the planned data. After the reconfiguration, save and close the file.
3.
Data > Import Base Station Bulk Configuration Data (CME client mode)
or CME > UMTS Application > Import Data > Import Base Station Bulk
CME.
NOTE
----End
Example
/*Adding a sector*/
ANT1N=R0A, CREATESECTOREQM=FALSE;
/*Adding a set of sector equipment*/
ANT1SN=0, ANT1N=R0A, ANTTYPE1=RXTX_MODE;
/*Adding a set of baseband equipment*/
ADD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=ULDL,
UMTSDEMMODE=DEM_2_CHAN, SN1=0;
/*Adding a LampSite cell*/
ADD ULOCELL: ULOCELLID=0, LOCELLTYPE=MIXED_MULTIRRU_CELL,
SECTOREQMGROUPNUM=1, SECTOREQMGROUPID1=0, SECTOREQMID1=0, ULFREQ=9650,
DLFREQ=10600, MAXPWR=430;
/*Adding other sets of sector equipment to the sector equipment group*/
SECTOREQMID=1;
Follow-up Procedure
l
Verification
1.
2.
Issue 03 (2015-06-30)
local cell.
193
RAN17.1
Expected result: The values of Multiple RRUs in one cell flag, Multiple RRUs in
one cell mode, and Cell transmission and reception mode are the same as planned.
l
Rollback
1.
Run the NodeB MML command RMV ULOCELL to remove the added local cell.
2.
Run the NodeB MML command RMV BASEBANDEQM to remove the added
baseband equipment.
3.
Run the NodeB MML command RMV SECTOREQM to remove the added sector
equipment.
4.
Run the NodeB MML command RMV SECTOR to remove the added sector.

1.
2.
3.
l
Troubleshooting
7.5.4 Combining pRRU-Aggregation Cells

This section describes the application scenarios, reconfiguration procedure, engineering
verification, and engineering rollback for combining pRRU-aggregation cells.
Prerequisites
l
Information
Description
Network topology
If RF units are added, pRRUs support only chain topologies.
Sector equipment
group
Values of the Sector Equipment Group ID and Sector

N/A
Issue 03 (2015-06-30)

194
RAN17.1
N/A

If pRRUs are configured for existing pRRU-aggregation cells, a new license is not
required.
Deploying pRRUs can help eliminate coverage holes and enhance coverage in weak coverage
areas. At the initial stage, one pRRU-aggregation cell that is served by multiple pRRUs can be
deployed, reducing inter-cell interference and the number of baseband processing units.
A pRRU-aggregation cell can be connected to one or multiple RHUBs on an RHUB chain or
ring. A maximum of four RHUBs can be cascaded.
An RHUB can be connected to a maximum of eight pRRUs, and a maximum of 96 pRRUs can
be aggregated to one pRRU-aggregation cell. If more than 96 pRRUs are aggregated, another
pRRU-aggregation cell is required.
Context
Data Type
MO
Setting Notes
Data
Source
MML
Command
Cell
ULOCELL
Remove the LampSite cells

to be combined.
Network
plan
RMV
ULOCELL
Sector
equipment
group
ULOCELLS
ECTOREQ
MGRP
If pRRUs of which the data is

converged at different optical
port, ensure that pRRUs of
which data is converged at
the same optical port are
included in the same sector
equipment group.
Network
plan
ADD
ULOCELL
SECTORE
QMGRP
Sector
equipment
used by a
sector
equipment
group
ULOCELLS
ECTOREQ
MGRPITE
M
If a sector equipment group

has more than one set of
sector equipment, you need
to add the sector equipment.
Network
plan
ADD
ULOCELL
SECTORE
QMGRPIT
EM
Procedure
l
Using MML commands

1.
Issue 03 (2015-06-30)
Run the NodeB MML command RMV ULOCELL to remove the LampSite cell to
be combined.
195
RAN17.1
2.
Run the NodeB MML command ADD ULOCELLSECTOREQMGRP to add a

sector equipment group for a LampSite cell. In this step, ensure that pRRUs of which
data is converged at the same optical port belong to the same sector equipment group.
3.
Run the NodeB MML command ADD ULOCELLSECTOREQMGRPITEM to

add the sector equipment of which the cells are to be combined to the sector equipment
group.

1.
2.
Batch configuration
1.
file.
NOTE
Issue 03 (2015-06-30)

196
RAN17.1
2.
3.
CME.
NOTE
----End
Example
/*Removing a LampSite cell*/
RMV ULOCELL: ULOCELLID=1;
/*Adding a set of sector equipment group in a LampSite cell*/
ADD ULOCELLSECTOREQMGRP: ULOCELLID=0, SECTOREQMGRPID=1, SECTOREQMID=1;
/*Adding the sector equipment of which the cells are to be combined to a
sector equipment group */
SECTOREQMID=2;
Follow-up Procedure
l
Verification
1.
2.
Run the NodeB MML command LST ULOCELLSECTOREQMGRP to query the

configuration of a sector equipment group.
Expected result: Number of Sector Equipment Groups is the same as planned.
3.
Run the NodeB MML command LST ULOCELLSECTOREQMGRPITEM to

query the configuration of the sector equipment in the sector equipment group of a
LampSite cell.
Expected result: The sector equipment used in the sector equipment group is the same
as planned.
Rollback
Using MML commands
Roll back to the source configuration, for details, see the procedure in Splitting a
pRRU-Aggregation Cell.
Issue 03 (2015-06-30)
1.
2.
3.
197
RAN17.1
l
Troubleshooting
7.5.5 Splitting a pRRU-Aggregation Cell

This section describes the application scenarios, reconfiguration procedure, engineering
verification, and engineering rollback for splitting a pRRU-aggregation cell.
Prerequisites
l
Information
Description
Cell information
l Basic information about the cell to be added, including

mode, Flag of Multi-RRU Cell, and Mode of Multi-RRU
Cell.
l TX and RX mode: pRRU-aggregation cells support 1T1R
or 2T2R mode.
BBP type
The type of the baseband processing units. For example, the

WBBPf3, WBBPf4, or UBBPd.
Sector equipment
group
Value of the Sector Equipment Group ID and Sector

Baseband equipment
Processes baseband unit information of each sector equipment

group.
Reference signal power
pRRU reference signal power.
If baseband processing units are insufficient, new baseband processing units are
required.
N/A

N/A
Issue 03 (2015-06-30)

198
RAN17.1
Splitting pRRU-aggregation cells and adding carriers are required to increase network capacity
in office buildings, subways, residential areas, shopping malls, and many other places where
traffic volumes grow rapidly along with the increasing subscriber amount.
Context
NOTICE
A cell must be deactivated during cell splitting, which causes service interruption for the cell.
Local operations refer to the operations that must be performed onsite, such as board installation
or operations on the LMT.
Remote operations refer to the operations that must be performed on the operation and
maintenance center, such as reconfiguring parameters using the U2000.
Data Type
MO
Setting Notes
Data
Source
MML
Command
Sector
equipment
group
ULOCELLS
ECTOREQ
MGRP
Remove the sector

equipment group of which a
pRRU-aggregation cell
needs to be split. If the cell
has only one sector
equipment group, do not
remove sector equipment
group.
Network
plan
RMV
ULOCELL
SECTORE
QMGRP
Sector
equipment
used by a
sector
equipment
group
ULOCELLS
ECTOREQ
MGRPITE
M
l Remove the sector

equipment of which a
pRRU-aggregation cell
needs to be split. If the
sector equipment group
has only one set of sector
equipment, remove the
sector equipment group,
rather than the sector
equipment.
Network
plan
RMV
ULOCELL
SECTORE
QMGRPIT
EM, ADD
ULOCELL
SECTORE
QMGRPIT
EM
l If a sector equipment
group has more than one
set of sector equipment,
you need to add the sector
equipment.
Issue 03 (2015-06-30)

199
RAN17.1
Data Type
MO
Setting Notes
Data
Source
MML
Command
Cell
ULOCELL
Add a mixed multi-RRU cell.

To add a pRRU-aggregation
cell, configure only one set of
sector equipment for each
sector equipment group.
Network
plan
ADD
ULOCELL
Procedure
l
Local operations: Install the baseband processing units in the BBU subrack.
Remote operations:
Using MML commands
1.
Run the NodeB MML command RMV ULOCELLSECTOREQMGRPITEM

to remove the sector equipment of which the cell needs to be split from the local
cell.
2.
Run the NodeB MML command RMV ULOCELLSECTOREQMGRP to

remove the sector equipment of which the cell needs to be split from the sector
equipment group.
3.
Run the NodeB MML command ADD ULOCELL to add a LampSite cell.
4.
Run the NodeB MML command ADD ADD

ULOCELLSECTOREQMGRPITEM to add the sector equipment of which the
cell needs to be split to the sector equipment group of the new cell.

1.
Issue 03 (2015-06-30)
Select a base station in the left pane of the planned data area. The NE object
tree is displayed in the lower part of the left pane, as shown in the following
figure:

200
RAN17.1
2.
following list and double-click the MO. In area 2, set parameters for the MO
and click
Batch configuration
1.
Data > Export Base Station Bulk Configuration Data (CME client mode)
or CME > UMTS Application > Export Data > Export Base Station Bulk
Configuration Data (U2000 client mode). Then, export data from the CME
to a file.
NOTE
2.
Open the exported file saved on the local PC and reconfigure data in the file
based on the planned data. After the reconfiguration, save and close the file.
3.
Data > Import Base Station Bulk Configuration Data (CME client mode)
or CME > UMTS Application > Import Data > Import Base Station Bulk
CME.
NOTE
----End
Issue 03 (2015-06-30)

201
RAN17.1
Example
/*Removing sector equipment of which the cell needs to be split from
sector equipment group of a local cell*/
RMV ULOCELLSECTOREQMGRPITEM: ULOCELLID=0, SECTOREQMGRPID=0,
SECTOREQMID=0;
/*If a sector equipment group has only one set of sector equipment, remove
the sector equipment group*/
RMV ULOCELLSECTOREQMGRP: ULOCELLID=0, SECTOREQMGRPID=0;
/*Adding a new LampSite cell*/
ADD ULOCELL: ULOCELLID=1, LOCELLTYPE=MIXED_MULTIRRU_CELL,
SECTOREQMGROUPNUM=1, SECTOREQMGROUPID1=0, SECTOREQMID1=0, ULFREQ=9650,
DLFREQ=10600, MAXPWR=430;
/*Adding other sets of sector equipment to the cell*/
SECTOREQMID=1;
Follow-up Procedure
l
Verification
1.
2.
local cell.
Expected result: The values of Multiple RRUs in one cell flag, Multiple RRUs in
one cell mode, and Cell transmission and reception mode are the same as planned.
Rollback
Using MML commands
Roll back to the source configuration, for details, see the procedure in Combining
pRRU-Aggregation Cells.
1.
2.
3.
l
Troubleshooting
Issue 03 (2015-06-30)

202
RAN17.1
Reconfiguring the UMTS Network
About This Chapter

This chapter describes how to reconfigure a UMTS network on a running RNC.
Issue 03 (2015-06-30)

203
RAN17.1
8.1 Reconfiguring a Cell

This section describes how to reconfigure a cell and cell parameters.
8.1.1 Changing Cell Power

This section describes how to change the maximum transmit power of a serving cell or power
of different channels in a cell during network optimization.
Prerequisites
l
Before changing cell power, collect information listed in Table 8-1.
Information
Description
Cell information
Query and record planned cell ID and cell

power.
None
None
License requirement
None
Context
Issue 03 (2015-06-30)
Data
Type
MO
Setting Notes
Data Source
MML Command
Power of a
cell
UCELL
Reconfigure Max
Transmit Power of
Cell, PCPICH
Transmit Power,
PSCH Transmit
Power, SSCH
Transmit Power,
and BCH Transmit
Power based on the
data plan.
Network plan
MOD UCELL

204
RAN17.1
Data
Type
MO
Setting Notes
Data Source
MML Command
UPCPICHP
WR
Reconfigure Max
Transmit Power of
PCPICH and Min
Transmit Power of
PCPICH based on
the data plan.
Network plan
MOD
UPCPICHPWR
UAICHPW
ROFFSET
Reconfigure AICH
Power Offset based
on the data plan.
Network plan
MOD
UAICHPWROFFSE
T
UPICHPW
ROFFSET
Reconfigure PICH
Power Offset based
on the data plan.
Network plan
MOD
UPICHPWROFFSE
T
USCCPCH
Reconfigure Max
Transmit Power of
FACH1 and Max
Transmit Power of
FACH2 based on the
data plan.
Network plan
MOD USCCPCH
NOTE
Among these parameters, the PCPICH power, maximum and minimum transmit powers of the
PCPICH, and the maximum transmit power of the cell are absolute values. The rest of the parameters
are power offsets relative to the PCPICH power.
If the SCCPCH or PRACH is in service, changing the maximum transmit power of the FACH or the
power of the PCH, PICH, or AICH can trigger the COMMON TRANSPORT CHANNEL
RECONFIGURATION procedure over the Iub interface.
If the cell is in service, changing the maximum transmit power of the cell or the power of PCPICH,
PSCH, SSCH, or BCH has the following impacts:
l If the maximum transmit power of the cell is changed to a value within the range specified by
the maximum and minimum transmit powers for cells under a NodeB, the change will take effect
and trigger the CELL RECONFIGURATION procedure over the Iub interface.
l If the maximum transmit power of the cell is changed to a value greater than the maximum
transmit power or less than the minimum transmit power for cells under a NodeB, the change
will not take effect nor trigger the CELL RECONFIGURATION procedure over the Iub interface.
When this occurs, the RNC will automatically report ALM-22215 UMTS Cell Max DL Power
Mismatch.
Procedure
l
Using MML commands

Modify the maximum transmit power of a cell.
1.
Issue 03 (2015-06-30)
On the BSC, run the LST UCELL command to query the maximum transmit
power of a logical cell.
205
RAN17.1
NOTICE
l If the maximum transmit power of a cell on the RNC is greater than that on the
NodeB, the logical cell cannot be set or cell reconfiguration fails.
l Setting the maximum transmit power of a cell to a too small value on the RNC
causes cell reconfiguration failures.
l The maximum transmit power of a cell on the RNC must be the same as that
on the NodeB.
2.
On the BSC, run the MOD UCELL command to modify the maximum transmit
power of a logical cell.
3.
On the NodeB, run the LST ULOCELL command to query the maximum transmit
power of a local cell corresponding to the logical cell.
4.
On the NodeB, run the MOD ULOCELL command to modify the maximum
transmit power of a local cell corresponding to the logical cell.
5.
On the BSC, run the LST UCELL command, and on the NodeB, run the LST
ULOCELL command to check whether the transmit power is successfully
modified.
Modify the transmit power of the PCPICH.

1.
Run the LST UPCPICH command to query the transmit power of the PCPICH.
2.
Run the MOD UCELL to modify the transmit power of the PCPICH.
3.
Run the LST UPCPICH command to check whether the transmit power is
successfully modified.
Modify the maximum transmit power of the PCPICH.

1.
Run the LST UPCPICH to query the maximum transmit power of the PCPICH.
2.
Run the MOD UPCPICHPWR command to modify the maximum transmit power
of the PCPICH.
3.
Modify the minimum transmit power of the PCPICH.

1.
Run the LST UPCPICH command to query the minimum transmit power of the
PCPICH.
2.
Run the MOD UPCPICHPWR command to modify the minimum transmit power
of the PCPICH.
3.
Modify the power of the PSCH.

1.
Run the LST UPSCH command to query the power of the PSCH.
2.
Run the MOD UCELL command to modify the power of the PSCH.
3.
Run the LST UPSCH command to check whether the transmit power is
Modify the power of the SSCH.

Issue 03 (2015-06-30)

206
RAN17.1
1.
Run the LST USSCH command to query the power of the SSCH.
2.
Run the MOD UCELL command to modify the power of the SSCH.
3.
Run the LST USSCH command to check whether the transmit power is
Modify the power offset of the AICH.

1.
Run the LST UCHPWROFFSET command to query the power offset of the
AICH.
2.
Run the MOD UAICHPWROFFSET command to modify the power offset of

the AICH.
3.
Run the LST UCHPWROFFSET command to check whether the transmit power
is successfully modified.
Modify the power offset of the PICH.

1.
Run the LST UCHPWROFFSET command to query the power offset of the
PICH.
2.
Run the MOD UPICHPWROFFSET command to modify the power offset of

the PICH.
3.
Run the LST UCHPWROFFSET command to check whether the transmit power
Modify the power of the BCH.

1.
Run the LST UBCH command to query the power of the BCH.
2.
Run the MOD UCELL command to modify the power of the BCH.
3.
Run the LST UBCH command to check whether the transmit power is successfully
modified.
Modify the power of the PCH.

1.
Run the LST UPCH command to query the power of the PCH.
2.
Run the MOD USCCPCH command to modify the power of the PCH.
3.
Run the LST UPCH to check whether the transmit power is successfully modified.
Modify the maximum transmit power of the FACH.
1.
Run the LST UFACH command to query the maximum transmit power of the
FACH.
2.
Run the MOD USCCPCH to modify the maximum transmit power of the FACH.
3.
Run the LST UFACH to check whether the transmit power is successfully
modified.

Configure a single cell.
1.
Issue 03 (2015-06-30)
Select a base station controller in the left pane of the planned data area. The NE
object tree is displayed in the lower part of the left pane, as shown in the following
figure:

207
RAN17.1
2.
Configure cells in batches.

You can modify cell data in batches by exporting data from the live network to a file,
modifying the cell data in the file, and importing the file into the CME.
1.
Data > Export Cell Parameter Data (CME client mode) or CME > UMTS
Application > Export Data > Export Cell Parameter Data (U2000 client
mode). Then, export the parameters you want to reconfigure to a file.
2.
Edit the planned data in the file, and save and close the file.
3.
Data > Import Cell Parameter Data (CME client mode) or CME > UMTS
Application > Import Data > Import Cell Parameter Data (U2000 client
mode). Then, import the file into the CME.
section Importing and Exporting a Cell File in the U2000 Help.
----End
Example
//Querying the maximum transmit power of a logical cell
LST UCELL: LstType=ByCellId, CellId=1;
//Modifying the maximum transmit power of a logical cell
MOD UCELL: CellId=1, MaxTxPower=430;
Issue 03 (2015-06-30)

208
RAN17.1
//Querying the transmit power, the maximum transmit power, and minimum transmit
power of the PCPICH.
LST UPCPICH: CellId=1;
//Modifying the transmit power of the PCPICH
MOD ULOCELL: CellId=1, PCPICHPower=330;
//Modifying the maximum and minimum transmit powers of the PCPICH
MOD UPCPICHPWR: CellId=1, MaxPCPICHPower=346, MinPCPICHPower=313;
//Querying the power of the PSCH
LST UPSCH: CellId=1;
//Modifying the power of the PSCH
MOD UCELL: CellId=1, PSCHPower=-50;
//Querying the power of the SSCH
LST USSCH: CellId=1;
//Modifying the power of the SSCH
MOD UCELL: CellId=1, SSCHPower=-50;
//Querying the power offset of the AICH
LST UCHPWROFFSET: CellId=1;
//Modifying the power offset of the AICH
MOD UAICHPWROFFSET: CellId=1, AICHPowerOffset=-6;
//Querying the power offset of the PICH
LST UCHPWROFFSET: CellId=1;
//Modifying the power offset of the PICH
MOD UPICHPWROFFSET: CellId=1, PICHPowerOffset=-7;
//Querying the power of the BCH
LST UBCH: CellId=1;
//Modifying the power of the BCH
MOD ULOCELL: CellId=1, BCHPower=-20;
//Querying the power of the PCH
LST UPCH: CellId=1;
//Modifying the power of the PCH
MOD USCCPCH: CellId=1, PCHPower=-20;
//Querying the maximum transmit power of the FACH
LST UFACH: CellId=1;
//Modifying the maximum transmit power of the FACH
MOD USCCPCH: CellId=1, FACH1MaxPower=5;
Follow-up Procedure
l
Verification
None
Rollback
Using MML commands
Issue 03 (2015-06-30)

209
RAN17.1
1.
2.
3.
8.1.2 Changing Cell Frequencies

This section describes how to change cell frequencies (including uplink and downlink
frequencies) when the cell frequencies are replanned for capacity expansion of a TRX.
Prerequisites
l
Before changing cell frequencies, collect information listed in Table 8-3.

Information
Description
Cell information

frequencies.
None
None
License requirement
None
Context
MO
Setting Notes
Data Source
MML Command
UCELLSET
UP
Reconfigure Uplink
UARFCN and
Downlink UARFCN
Network plan
MOD UCELLSETUP
After the cell frequency is changed, the neighboring relationships in the cell are deleted. Replan
and add the neighboring cells by referring to the procedure in 8.3 Reconfiguring Neighboring
Cells.
Issue 03 (2015-06-30)

210
RAN17.1
Procedure
l
Using MML commands

1.
On the RNC LMT:

a.
Run the LST UCELL command to query the cell frequencies before the
reconfiguration.
b.
Run the HO UCELL command to forcibly hand over UEs in a cell to a

neighboring cell.
c.
Run the DEA UCELL to deactivate the cell.
d.
Run the RMV UNRELATION command to remove the bidirectional neighbor

relationships of the cell.
NOTE
Running the RMV UNRELATION command can only remove the bidirectional
neighbor relationships of the cell in only one RNC. To remove the relationship between
the cell and the neighboring cells in another RNC, run this command on that RNC.
e.
Run the MOD UCELLSETUP command to modify the cell frequencies.
f.
Run the LST UCELL command to check whether the cell frequencies are
correctly modified.
2.
On the NodeB LMT, run the MOD ULOCELL command to modify the cell
frequencies.
3.
On the RNC LMT, run the ACT UCELL command to activate the cell.
4.
After the cell frequencies are modified, reconfigure the neighboring cell data by
referring to the procedure in 8.3 Reconfiguring Neighboring Cells.

On the menu bar of the planned data area, choose UMTS Application > Modify Cell
Frequencies in Batches (CME client mode) or CME > UMTS Application > Modify
Cell Frequencies in Batches (U2000 client mode), and reconfigure cell frequencies and
scrambling codes.
Changing UMTS Cell Frequencies in the U2000 Help.
----End
Example
//Querying the cell frequencies before the reconfiguration
//Forcibly handing over UEs in a cell to a neighboring cell
HO UCELL: CellId=1, CellChoice=ALLCELL;
//Deactivating a cell
DEA UCELL: CellId=1;
//Removing neighbor relationships of the cell
RMV UNRELATION: CellId=1, NCellType=IntraFreqNCell
//Modifying cell frequencies
MOD UCELLSETUP: CellId=1, BandInd=Band2, UARFCNUplinkInd=TRUE, UARFCNUplink=37,
UARFCNDownlink=437;
Issue 03 (2015-06-30)

211
RAN17.1
//Activating the cell

ACT UCELL: CellId=1;
Follow-up Procedure
l
Verification
Run the DSP UCELL command to check whether the cell status is normal.
Expected result: State explanation is Cell is setup and enabled.
Rollback
Using MML commands
1.
2.
3.
8.1.3 Changing the Scrambling Code of a Cell

This section describes how to change the downlink primary scrambling code of a cell when cell
scrambling codes are replanned after capacity expansion.
Prerequisites
l
Before changing the scrambling code of a cell, collect information listed in Table 8-5.
Information
Description
Cell information

scrambling code.
None
None
License requirement
None
Context
Issue 03 (2015-06-30)

212
RAN17.1

MO
Setting Notes
Data Source
MML Command
UCELLSET
UP
Reconfigure DL
Primary Scrambling
Code based on the data
plan.
Network plan
MOD UCELLSETUP
Procedure
l
Using MML commands

1.
Run the LST UCELL command to query the downlink primary scrambling code of
a cell before the reconfiguration.
2.
Run the HO UCELL command to forcibly hand over UEs in a cell to a neighboring
cell.
3.
Run the DEA UCELL command to deactivate the cell.
4.
Run the LST UCELL command to query the basic information of the cell.
5.
Run the MOD UCELLSETUP command to modify the downlink primary scrambling
code of the cell.
6.
Run the ACT UCELL command to activate the cell.
7.
8.
Run the LST UCELL command to check whether the scrambling code is successfully
modified.

On the menu bar of the planned data area, choose UMTS Application > Modify Cell
Frequencies in Batches (CME client mode) or CME > UMTS Application > Modify
Cell Frequencies in Batches (U2000 client mode), and reconfigure cell frequencies and
scrambling codes.
Changing UMTS Cell Frequencies in the U2000 Help.
----End
Example
//Querying the downlink primary scrambling code of a cell before the
reconfiguration
//Modifying the scrambling code of the cell
MOD UCELLSETUP: CellId=1, PScrambCode=5;
Issue 03 (2015-06-30)

213
RAN17.1
//Activating the cell

Follow-up Procedure
l
Verification
Rollback
Using MML commands
1.
2.
3.
8.1.4 Reconfiguring Cell System Information Parameters

This section describes how to reconfigure cell system information-related parameters during
network optimization. The parameters are cell system information switch, cell access restriction
information, cell selection or reselection information, and cell measurement control system
information.
Prerequisites
l
Before reconfiguring cell system information parameters, collect information listed in

Table 8-7.
Information
Description
Cell information
Query and record the cell ID, cell system

information parameters, cell access
restriction parameters, cell selection or
reselection parameters, and cell
measurement control parameters.
None
l
Issue 03 (2015-06-30)
214
RAN17.1
None
l
License requirement
None
Context
Data
Type
MO
Setting Notes
Data Source
MML Command
Cell
informati
on
UCELLSI
BSWITC
H
Configure data
based on the plan.
Network plan
MOD
UCELLSIBSWITC
H
UCELLA
CCESSST
RICT
Configure data
based on the plan.
Network plan
MOD
UCELLACCESSSTRICT
UCELLSE
LRESEL
Configure data
based on the plan.
Network plan
MOD
UCELLSELRESEL
UCELLM
EAS
Configure data
based on the plan.
Network plan
MOD UCELLMEAS
Procedure
l
Using MML commands

Modify the cell system information switch.
1.
Run the LST UCELLSIBSWITCH command to query the cell system

information switch.
2.
Run the MOD UCELLSIBSWITCH command to modify the cell system

information switch.
3.
Run the LST UCELLSIBSWITCH command to check whether the cell system
information switch is successfully modified.
Modify the cell access restriction information.

1.
Run the LST UCELLACCESSSTRICT command to query the cell access

restriction information.
2.
Run the MOD UCELLACCESSSTRICT command to modify the cell access

restriction information.
3.
Run the LST UCELLACCESSSTRICT command to check whether the cell

access restriction information is successfully modified.
Modify the cell selection or reselection information.

1.
Issue 03 (2015-06-30)
Run the LST UCELLSELRESEL command to query the cell selection or

reselection information.
215
RAN17.1
2.
Run the MOD UCELLSELRESEL command to modify the cell selection or

reselection information.
3.
Run the LST UCELLSELRESEL command to check whether the cell selection
or reselection information is successfully modified.
Modify the cell measurement control system information.
1.
Run the LST UCELLMEAS command to query the cell measurement control
system information.
2.
Run the MOD UCELLMEAS command to modify the cell measurement control
system information.
3.
Run the LST UCELLMEAS command to check whether the cell measurement
control system information is successfully modified.

1.
figure:
2.

Issue 03 (2015-06-30)

216
RAN17.1
1.
2.
3.
----End
Example
//Querying the cell system information switch before the reconfiguration
LST UCELLSIBSWITCH: CellId=1;
//Modifying the cell system information switch
MOD UCELLSIBSWITCH: CellId=1, SibCfgBitMap=SIB19-1;
//Query the cell access restriction information
LST UCELLACCESSSTRICT: CellId=1;
//Modifying the cell access restriction information
MOD UCELLACCESSSTRICT: CELLID=1, ISACCESSCLASS10BARRED=BARRED;
//Querying the cell selection or reselection information
LST UCELLSELRESEL: CellId=1;
//Modifying the cell selection or reselection information
MOD UCELLSELRESEL: CELLID=1, QQUALMIN=-22;
//Querying the cell measurement control system information
LST UCELLMEAS: CellId=1;
//Modifying the cell measurement control system information
MOD UCELLMEAS: CELLID=1, INTERFREQINTERRATMEASIND=INTER_FREQ, FACHMEASIND=REQUIRE;
Follow-up Procedure
l
Verification
None
Rollback
Using MML commands
1.
2.
3.
Issue 03 (2015-06-30)

217
RAN17.1
8.1.5 Reconfiguring Cell Radio Link Power Parameters

This section describes how to reconfigure cell radio link parameters during network optimization
to resolve specific call drop problems. The modifiable parameter is the radio link power.
Prerequisites
l
Before reconfiguring cell radio link power parameters, collect information listed in Table
8-9.
Information
Description
Cell information
Query and record the cell ID and cell radio

link power.
None
None
License requirement
None
Context
After a logical cell is activated, you can query, modify, remove, or add the cell radio link power
information for CS and PS services. The new settings are sent to the NodeB in the NBAP RADIO
LINK SETUP REQUEST message over the Iub interface. The settings are used to control the
power. If no information in the database can math the service rate requested by the UE, the
system uses the power data with the closest rate.
MO
Setting Notes
Data Source
MML Command
UCELLRLP
WR
Configure data based

on the plan.
Network plan
MOD UCELLRLPWR
Procedure
l
Using MML commands

Modify the cell radio link power.
Issue 03 (2015-06-30)
1.
Run the LST UCELLRLPWR command to query the cell radio link power.
2.
Configure the cell radio link power.

218
RAN17.1
Run the MOD UCELLRLPWR command to modify the downlink transmit

power of a cell.
Run the ADD UCELLRLPWR command to add downlink transmit powerrelated parameters for the cell.
Run the RMV UCELLRLPWR command to remove the downlink transmit
power of the cell.
l

1.
figure:
2.

Issue 03 (2015-06-30)
1.
2.
219
RAN17.1
3.
----End
Example
//Querying the cell radio link power configurations before the reconfiguration
LST UCELLRLPWR: CellId=1;
//Modifying the cell radio link power configurations
MOD UCELLRLPWR: CELLID=1, CNDOMAINID=CS_DOMAIN, MAXBITRATE=12200, RLMAXDLPWR=-30,
RLMINDLPWR=-180;
Follow-up Procedure
l
Verification
Run the LST UCELLRLPWR command to check whether the cell radio link power is
Rollback
Using MML commands
1.
2.
3.
8.1.6 Reconfiguring Cell Synchronization Parameters

This section describes how to reconfigure cell synchronization parameters during network
optimization to resolve access and call drop problems.
Prerequisites
l
Issue 03 (2015-06-30)
Before reconfiguring cell synchronization parameters, collect information listed in Table

8-11.
220
RAN17.1
Information
Description
Cell information
Query and record the cell ID and cell

synchronization parameters.
None
None
License requirement
None
Context
MO
Setting Notes
Data Source
MML Command
UCELL
Reconfigure Num of
Continuous in Sync
Ind, Num of
Continuous Out of
Sync Ind, and Radio
Link Failure Timer
Length based on the
data plan.
Network plan
MOD UCELL
NOTICE
Reconfiguring the cell synchronization parameters triggers the CELL RECONFIGURATION
procedure over the Iub interface.
Procedure
l
Using MML commands

1.
Run the LST UCELL command to query the cell information.
2.
Run the MOD UCELL command to modify the cell synchronization parameters.

Issue 03 (2015-06-30)

221
RAN17.1
1.
figure:
2.

1.
2.
3.
----End
Issue 03 (2015-06-30)

222
RAN17.1
Example
//Querying the cell synchronization parameters before the reconfiguration
LST UCELL: CellId=1;
//Modifying the cell synchronization parameters
MOD UCELL: CellId=1, NInsyncInd=5, NOutsyncInd=50, TRlFailure=50;
Follow-up Procedure
l
Verification
Run the LST UCELL command to check whether the cell synchronization parameters are
Rollback
Using MML commands
1.
2.
3.
8.1.7 Modifying the Area Information of a Cell

This section describes how to modify the area information of a cell when some areas are
replanned or a NodeB is cut over. These areas are location areas, service areas, and routing areas.
Prerequisites
l
Before modifying the area information of a cell, collect information listed in Table 8-13.
Information
Description
Cell information
Query and record the cell ID, location area

code (LAC), routing area code (RAC) and
service area code (SAC).
None
Issue 03 (2015-06-30)

223
RAN17.1
None
License requirement
None
Context
MO
Setting Notes
Data Source
MML Command
UCELLACI
NFO
Modify the LAC, RAC,

or SAC for a cell.
Network plan
MOD UCELLACINFO
Procedure
l
Using MML commands

1.
Run the LST UCELL command to query the basic information of a cell.
2.
Run the MOD UCELLACINFO command to modify the LAC, RAC, or SAC for a
cell.

1.
figure:
Issue 03 (2015-06-30)

224
RAN17.1
2.

1.
2.
3.
----End
Example
//Querying the area information of a cell
//Modifying the area information of a cell
MOD UCELLACINFO: CELLID=1, LAC=H'2501, SAC=H'0000, CFGRACIND=REQUIRE, RAC=H'00;
Follow-up Procedure
l
Verification
Run the LST UCELL command to check whether the area information is successfully
modified.
Rollback
Using MML commands
Issue 03 (2015-06-30)
1.
2.

225
RAN17.1
3.
8.1.8 Modifying the UTRAN Registration Area of a Cell

This section describes how to modify the UTRAN registration area (URA) of a cell when URAs
are replanned.
Prerequisites
l
Before modifying the URA of a cell, collect information listed in Table 8-15.
Information
Description
Cell information
Query and record the cell ID and the URA

of a cell.
None
None
License requirement
None
Context
MO
Setting Notes
Data Source
MML Command
UCELLUR
A
Reconfigure URA ID
Network plan
ADD UCELLURA
One cell can belong to 1 to 8 URAs. After the cell is activated, URAs can be dynamically added
as required.
Procedure
l
Issue 03 (2015-06-30)
Using MML commands

1.
Run the LST UCELLURA command to query the URAs of the cell.
2.
Configure URAs of a cell

226
RAN17.1
If...
Then...
You need to remove a URA of a cell
Run the RMV UCELLURA command.
You need to add a URA of a cell
Run the ADD UCELLURA command.
You need to change the URA of a cell

from A to B
1. Run the ADD UCELLURA

command to add the cell to a new
URA (URA B)
2. Run the RMV UCELLURA
command to remove the cell from the
old URA (URA A).

1.
figure:
2.

Issue 03 (2015-06-30)

227
RAN17.1
1.
2.
3.
----End
Example
//Querying URA information of a cell
LST UCELLURA: CellId=1;
//Adding a cell to a new URA (URA A)
ADD UCELLURA: CELLID=1, URAID=2;
//Removing a cell from the old URA (URA B)
RMV UCELLURA: CELLID=1, URAID=1;
Follow-up Procedure
l
Verification
Run the LST UCELLURA command to check whether the URA is successfully modified.
Rollback
Using MML commands
1.
2.
3.
8.1.9 Modifying a Cell Name

This section describes how to modify a cell name during network optimization, for example,
when cell information is replanned.
Issue 03 (2015-06-30)

228
RAN17.1
Prerequisites
l
Before modifying a cell name, collect information listed in Table 8-17.

Information
Description
Cell information
Query and record the cell ID and cell name.
None
None
License requirement
None
Context
MO
Setting Notes
Data Source
MML Command
UCELLNA
ME
Configure Cell Name

based on the plan.
Network plan
MOD UCELLNAME
Procedure
l
Using MML commands

1.
Run the LST UCELL command to query the cell name.
2.
Run the MOD UCELLNAME command to modify the cell name.

1.
Issue 03 (2015-06-30)
figure:

229
RAN17.1
2.

1.
2.
3.
----End
Example
//Querying the cell name
Issue 03 (2015-06-30)

230
RAN17.1
//Modifying the cell name
MOD UCELLNAME: RNCID=1,CELLID=1, CELLNAME="Cell1";
Follow-up Procedure
l
Verification
Run the LST UCELL command to check whether the cell name is successfully modified.
Rollback
Using MML commands
1.
2.
3.
8.1.10 Modify the ID of a Cell

This section describes how to modify the ID of a cell during network optimization, for example,
when cell information is replanned.
Prerequisites
l
Before modifying the ID of a cell, collect information listed in Table 8-19.

Information
Description
Cell information
Query and record the ID of a cell.
None
None
License requirement
None
Context
Issue 03 (2015-06-30)

231
RAN17.1

MO
Setting Notes
Data Source
MML Command
UCELLID

on the plan.
Network plan
MOD UCELLID
Procedure
Step 1 Run the DSP UCELL command to query the cell status.
If...
Then...
The cell is activated
Go to Step 2.
The cell is inactive
Go to Step 4.
Step 2 Run the HO UCELL command to forcibly hand over UEs in a cell to a neighboring cell.
Step 3 Run the DEA UCELL command to deactivate the cell.
Step 4 Run the MOD UCELLID command to modify the ID of the cell.
Step 5 Run the LST UCELL command to check whether the ID of the cell is correct after the
modification.
Step 6 To restore the serving state of the cell, run the ACT UCELL command to reactivate the cell.
----End
Example
//Querying the ID of a cell
LST UCELL: LstType=ByCellName, CellName="cell1";
//Forcibly handing over UEs in the cell to a neighboring cell
//Modifying the ID of the cell
MOD UCELLID: RNCID=1,SrcCellID =1, DesCellID=2;
//Reactivating the cell
Follow-up Procedure
l
Verification
Issue 03 (2015-06-30)

232
RAN17.1
Rollback
8.1.11 Adding an SCCPCH

This section describes how to add a secondary common control physical channel (SCCPCH) in
a cell where FACH congestion occurs.
Prerequisites
l
The cell has been successfully set up and is configured with only one SCCPCH.
Before adjusting the SCCPCH, collect information listed in Table 8-21.

Information
Description
Cell information
Query and record the cell ID and SCCPCH

parameters.
None
None
License requirement
None
Context
Issue 03 (2015-06-30)
MO
Setting Notes
Data Source
MML Command
USCCPCHB
ASIC

on the plan.
Network plan
ADD USCCPCHBASIC
USCCPCHT
FC

on the plan.
Network plan
ADD USCCPCHTFC
UFACH

on the plan.
Network plan
ADD UFACH
UFACHDY
NTFS

on the plan.
Network plan
ADD UFACHDYNTFS
UFACHLO
CH

on the plan.
Network plan
ADD UFACHLOCH

233
RAN17.1
MO
Setting Notes
Data Source
MML Command
UPCH

on the plan.
Network plan
ADD UPCH
UPCHDYN
TFS

on the plan.
Network plan
RMV UPCHDYNTFS
UPICH

on the plan.
Network plan
ADD UPICH
NOTICE
The number of SCCPCHs must be the same for all cells in the network, that is, all cells are
configured with one SCCPCH or two SCCPCHs. This prevents UEs with poor compatibility
from failing to set up services.
Procedure
l
Using MML commands

Remove the configured SCCPCH.
1.
Run the HO UCELL command to forcibly hand over UEs in a cell to a neighboring
cell.
2.
Run the DEA UCELL command to deactivate the cell.
3.
Run the RMV USCCPCH command to remove the configured SCCPCH.
Add an SCCPCH with the channel ID of 8 to carry the PCH.

1.
Run the ADD USCCPCHBASIC command to add an SCCPCH. In this step, set
SCCPCH ID to 8.
2.
Run the ADD USCCPCHTFC command to add the calculated transport format
combination (CTFC) of the SCCPCH.
3.
Run the ADD UPICH command to add a PICH.
4.
Run the ADD UPCH command to add a PCH.
5.
Run the ADD UPCHDYNTFS command to add the transport format set (TFS) of
the PCH.
6.
Run the ACT USCCPCH command to activate the SCCPCH.
Add an SCCPCH with the channel ID of 9 to carry the FACH.
Issue 03 (2015-06-30)
1.
Run the ADD USCCPCHBASIC command to add an SCCPCH. In this step, set
SCCPCH ID to 9.
2.
Run the ADD USCCPCHTFC command to add the CTFC of the SCCPCH.
3.
Run the ADD UFACH command to add an FACH that carries data services. In
this step, set FACH ID to 5.
4.
Run the ADD UFACHDYNTFS command to add the TFS of the FACH.
234
RAN17.1
5.
Run the ADD UFACHLOCH command to add a logical channel mapped to the
FACH with the channel ID of 4.
6.
Run the ACT UCELL command to activate the cell.

l

1.
figure:
2.

Issue 03 (2015-06-30)
1.
2.
3.
235
RAN17.1
----End
Example
//Querying the SCCPCH configurations of a cell before the reconfiguration
//Deactivating the cell
//Deactivating the SCCPCH of the cell
DEA USCCPCH: CellId=1, PhyChId=8;
//Removing the existing SCCPCH
RMV USCCPCH: CellId=1, PhyChId=8;
//Adding an SCCPCH with the channel ID of 8 to carry the PCH
ADD USCCPCHBASIC:CELLID=1, PHYCHID=8, SCCPCHOFFSET=50, SCRAMBCODE=0,
STTDIND=FALSE, PO1=8, PO3=12, CTFCSIZE=BIT2, PILOTSYMBOLEXIST=NOT_EXISTS,
SLOTFORMAT=D4, MBMSCHIND=COMMON;
//Adding the CTFC of the SCCPCH
ADD USCCPCHTFC:CELLID=1, PHYCHID=8, CTFC=0;
//Adding a PICH
ADD UPICH:CELLID=1, PICHID=10, PHYCHID=8, PICHMODE=V36, STTDIND=FALSE;
//Adding a PCH
ADD UPCH:CELLID=1, TRCHID=3, PHYCHID=8, RATEMATCHINGATTR=230, TOAWS=35,
TOAWE=10, PCHPOWER=-20;
//Adding the TFS of the PCH
ADD UPCHDYNTFS:CELLID=1, RLCSIZE=240, TRCHID=3, TFSNUMBER=D2,
TBNUMBER1=0, TBNUMBER2=1;
//Activating the SCCPCH
ACT USCCPCH:CELLID=1, PHYCHID=8;
//Adding an SCCPCH with the channel ID of 9 to carry the FACH
ADD USCCPCHBASIC:CELLID=1, PHYCHID=9, TFCIPRESENCE=EXISTS,
SCCPCHOFFSET=100, SCRAMBCODE=0, STTDIND=FALSE, CTFCSIZE=BIT4,
SLOTFORMAT=D8, MBMSCHIND=COMMON;
//Adding the CTFC of the SCCPCH
Issue 03 (2015-06-30)

236
RAN17.1
//Adding an FACH with the channel ID of 4 to transmit signaling

ADD UFACH:CELLID=1, TRCHID=4, PHYCHID=9, RATEMATCHINGATTR=220,
MAXCMCHPI=D15, MINCMCHPI=D14, SIGRBIND=TRUE, CHCODINGTYPE=CONVOLUTIONAL,
CODINGRATE=D1/2, TOAWS=35, TOAWE=10, MAXFACHPOWER=10;
//Adding an FACH with the channel ID of 5 to transmit data
ADD UFACH:CELLID=1, TRCHID=5, PHYCHID=9, RATEMATCHINGATTR=130,
MAXCMCHPI=D13, MINCMCHPI=D0, SIGRBIND=FALSE, CHCODINGTYPE=TURBO,
TOAWS=35, TOAWE=10, MAXFACHPOWER=10;
//Adding the TFS of the FACH whose channel ID is 4
ADD UFACHDYNTFS:CELLID=1, TRCHID=4, RLCSIZE=168, TFSNUMBER=D3,
TBNUMBER1=0, TBNUMBER2=1, TBNUMBER3=2;
//Adding the TFS of the FACH whose channel ID is 5
ADD UFACHDYNTFS:CELLID=1, TRCHID=5, RLCSIZE=360, TFSNUMBER=D2,
TBNUMBER1=0, TBNUMBER2=1;
//Adding a logical channel mapped to the FACH with the channel ID of 4
ADD UFACHLOCH:TRCHID=4, CELLID=1, SDUDISCARDTIMER=T10, MAXPDUSIZE=20;
//Activating the SCCPCH
ACT USCCPCH:CELLID=1, PHYCHID=9;
//Activate the cell
Follow-up Procedure
l
Verification
Run the DSP UCELL command to query the status of the cell.
Rollback
Using MML commands
1.
2.
3.
8.1.12 Removing a UMTS Cell

In refarming scenarios, resources used by a UMTS cell needs to be allocated to a GSM or LTE
cell.
Issue 03 (2015-06-30)

237
RAN17.1
Prerequisites
l
The cell to be removed is not configured in the power sharing group or in multicarrier cell
group.
Before removing a UMTS cell, collect information listed in Table 8-23.

Information
Description
Cell
Local cell ID and logical cell ID.
Uplink and downlink baseband equipment

serving a cell.
NodeB sector equipment
Sector equipment serving a cell.
N/A
N/A
License requirement
N/A
Context
MO
Setting Notes
Data Source
MML Command
ULOCELL
Configure the
parameters in the
MO as planned.
Network plan
RMV ULOCELL
BASEBANDEQM
Configure the
parameters in the
MO as planned.
Network plan
RMV
BASEBANDEQM
SECTOREQM
Configure the
parameters in the
MO as planned.
Network plan
RMV
SECTOREQM
SECTOR
Configure the
parameters in the
MO as planned.
Network plan
RMV SECTOR
Procedure
l
Issue 03 (2015-06-30)
Using MML commands

238
RAN17.1
1.
Run the RNC MML command DEA UCELL to deactivate the cell to be moved.
2.
Optional: Run the NodeB MML command RMV NODEBPAGRP to remove the
power sharing group of the cell.
3.

NODEBMULTICELLGRPITEM to remove the cell from the multicarrier cell
group.
4.
Run the NodeB MML command RMV ULOCELL to remove the local cell.
5.
Optional: Run the NodeB MML command RMV BASEBANDEQM to remove the
baseband equipment of the cell.
6.
Optional: Run the NodeB MML command RMV SECTOREQM to remove the
sector equipment of the cell.
7.
Optional: Run the NodeB MML command RMV SECTOR to remove the sector of
the cell.

1.
2.
Select or search for the MO to be configured based on the planned data, and then
double-clock the MO. Delete the related MO configuration records in area 2, and
click
Batch configuration
Issue 03 (2015-06-30)

239
RAN17.1
1.
file.
NOTE
2.
3.
CME.
NOTE
----End
Example
//Deactivating the cell to be removed
//If the local cell is in the power sharing group, removing the power
sharing group
RMV NODEBPAGRP: DLOCELL=0;
//If the local cell is in a multicarrier cell group, removing the cell
from the multicarrier cell group
RMV NODEBMULTICELLGRPITEM: MULTICELLGRPID=0, ULOCELLID=0;
//Removing the local cell
RMV ULOCELL: ULOCELLID=0;
//If the baseband equipment serving the local cell is not used by other
local cells, remove the baseband equipment
RMV BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=ULDL;
//If the sector equipment serving the local cell is not used by other
local cells, removing the sector equipment
RMV SECTOREQM: SECTOREQMID=0;
//If no other cells are in the sector of the local cell, remove the
sector
RMV SECTOR: SECTORID=0;
Follow-up Procedure
l
Verification
Run the NodeB MML command LST ULOCELL to list the information of the local
cell.
Expected results: The information about this local cell is not listed in the command
output.
Rollback
Using MML commands
Issue 03 (2015-06-30)

240
RAN17.1
Reconfiguring the number of carriers for a NodeB. For detail, see the procedure in 7.3.1
Reconfiguring the Number of Carriers for a NodeB.
1.
2.
3.
8.2 Modifying an SCCPCH

This section describes how to modify a secondary common control physical channel (SCCPCH)
in a cell during network optimization. The modifiable data includes the time window and power
of the PCH, time window and power of the FACH, calculated transport format combination
(CTFC) information of the SCCPCH, basic information of the FACH, dynamic transport format
set (TFS) of the FACH, logical channels mapped onto the FACH, basic information of the PCH,
dynamic TFS of the PCH, and PICH information.
Prerequisites
l
Before modifying an SCCPCH, collect information listed in Table 8-24.

Information
Description
Cell information
Query and record the cell ID and SCCPCH

parameters.
None
None
License requirement
None
Context
Issue 03 (2015-06-30)

241
RAN17.1

MO
Setting Notes
Data Source
MML Command
USCCPCH

on the plan.
Network plan
MOD USCCPCH
USCCPCHT
FC

on the plan.
Network plan
ADD USCCPCHTFC
UFACH

on the plan.
Network plan
ADD UFACH
UFACHDY
NTFS

on the plan.
Network plan
ADD UFACHDYNTFS
UFACHLO
CH

on the plan.
Network plan
ADD UFACHLOCH
UPCH

on the plan.
Network plan
ADD UPCH
UPCHDYN
TFS

on the plan.
Network plan
RMV UPCHDYNTFS
UPICH

on the plan.
Network plan
ADD UPICH
NOTICE
If the number of FACHs or PCHs carried on the SCCPCH changes, or TFS of the FACH or PCH
changes, recalculate the CTFC of the SCCPCH before modifying the SCCPCH.
Procedure
l
Using MML commands

Modify the time window and power of the PCH and FACH.
1.
Run the LST UFACH or LST UPCH command to query SCCPCH information
to be modified.
2.
Run the MOD USCCPCH command to reconfigure the SCCPCH.
3.
Run the LST UFACH or LST UPCH command to check whether SCCPCH
information is successfully modified.
Modify the CTFC of the SCCPCH.
Issue 03 (2015-06-30)

242
RAN17.1
NOTE
If the cell in service has only one SCCPCH or has two SCCPCHs but the one with the smaller
channel ID needs to be modified, do as follows:
1. Run the HO UCELL command to forcibly hand over UEs in a cell to a neighboring cell.
2. Run the DEA UCELL command to deactivate the cell.
3. After the modification, run the ACT UCELL command to activate the cell for providing
services.
1.
Run the DEA USCCPCH command to deactivate the SCCPCH.
2.
Run the LST USCCPCH command to query the CTFC of the SCCPCH.
3.
Modify the CTFC of the SCCPCH.

If...
Then...
You need to
remove the
transport format
combination
(TFC) of the
SCCPCH
Run the RMV USCCPCHTFC command.
You need to add

the TFC of the
SCCPCH
Run the ADD USCCPCHTFC command.
4.
Run the LST USCCPCH command to check whether the TFC of the SCCPCH is
5.
Modify the basic information of the FACH

NOTE
2. Run the DEA UCELL to deactivate the cell.
services.
1.
Run the DEA USCCPCH to deactivate the SCCPCH.
2.
Run the LST UFACH command to query the basic information of the FACH.
3.
Modify the basic information of the FACH.

Before removing the basic information of the FACH, ensure that the FACH
dynamic transport format, FACH logical channel, and carried CTCH are
removed.
You can restore the removed basic information of the FACH if required after
the modification. The information includes the FACH dynamic transport
format, FACH logical channel, and carried CTCH.
Issue 03 (2015-06-30)

243
RAN17.1
If...
Then...
You need to
remove the basic
information of
the FACH
Run the RMV UFACH command.
You need to add

the basic
information of
the FACH
Run the ADD UFACH command.
4.
Run the LST UFACH command to check whether the basic information of the
FACH is successfully modified.
5.
Modify the dynamic TFS of the FACH.

NOTE
services.
1.
2.
Run the LST UFACH command to check whether the dynamic TFS of the FACH
3.
Modify the dynamic TFS of the FACH.

If...
Then...
You need to
remove the
dynamic TFS of
the FACH
Run the RMV UFACHDYNTFS command.
You need to add

the dynamic TFS
of the FACH
Run the ADD UFACHDYNTFS command.
4.
Run the LST UFACH command to check whether the dynamic TFS of the FACH
5.
Modify the logical channels mapped onto the FACH
Issue 03 (2015-06-30)

244
RAN17.1
NOTE
services.
1.
2.
Run the LST UFACH command to query the logical channels mapped onto the
FACH.
3.
Modify the logical channels mapped onto the FACH.

Before removing the logical channels mapped to the FACH, ensure that the
CTCH carried on the FACH is removed.
You can restore the removed logical channels mapped to the FACH if required
after the modification, such as the CTCH carried on the FACH.
If...
Then...
You need to
remove the
logical channels
mapped onto the
FACH
Run the RMV UFACHLOCH command.
You need to add

the logical
channels mapped
onto the FACH
Run the ADD UFACHLOCH command.
4.
Run the LST UFACH command to check whether the logical channels mapped
onto the FACH are correct.
5.
Modify the basic information of the PCH

NOTE
services.
1.
2.
Run the LST UPCH command to query the basic information of the PCH.
3.
Modify the basic information of the PCH.

Before removing the basic information of the PCH, ensure that the dynamic
TFS of the PCH is removed.
Issue 03 (2015-06-30)

245
RAN17.1
You can restore the removed basic information of the PCH if required after the
modification, such as the dynamic TFS of the PCH.
If...
Then...
You need to
remove the basic
information of
the PCH
Run the RMV UPCH command.
You need to add

the basic
information of
the PCH
Run the ADD UPCH command.
4.
Run the LST UPCH command to check whether the basic information of the PCH
is correctly modified.
5.
Modify the dynamic TFS of the PCH.

NOTE
services.
1.
2.
Run the LST UPCH command to check the dynamic TFS of the PCH.
3.
Modify the dynamic TFS of the PCH.

If...
Then...
You need to
remove the
dynamic TFS of
the PCH
Run the RMV UPCHDYNTFS command.
You need to add

the dynamic TFS
of the PCH
Run the ADD UPCHDYNTFS command.
4.
Run the LST UPCH command to check whether the dynamic TFS of the PCH is
correctly modified.
5.
Modify the information of the PICH.
Issue 03 (2015-06-30)

246
RAN17.1
NOTE
services.
1.
2.
Run the LST UPICH command to query the information of the PICH.
3.
Modify the information of the PICH.

If...
Then...
You need to
remove the
information of
the PICH
Run the RMV UPICH command.
You need to add

the information
of the PICH
Run the ADD UPICH command.
4.
Run the LST UPICH command to check whether the information of the PICH is
correctly modified.
5.

1.
Issue 03 (2015-06-30)
figure:

247
RAN17.1
2.

1.
2.
3.
----End
Follow-up Procedure
l
Verification
None
Issue 03 (2015-06-30)

248
RAN17.1
Rollback
Using MML commands
1.
2.
3.
8.3 Reconfiguring Neighboring Cells

This section describes how to reconfigure neighboring cells, including intra-frequency cells,
inter-frequency cells, and neighboring GSM cells.
8.3.1 Adding an Intra-Frequency Neighboring Cell

This section describes how to add an intra-frequency neighboring cell to a specified cell during
capacity expansion, for example, when NodeBs are added.
Prerequisites
l
Before adding an intra-frequency neighboring cell, collect information listed in Table

8-26.
Information
Description
Cell information
Query and record the cell ID and intrafrequency neighboring cell parameters.
None
None
License requirement
None
Context
Issue 03 (2015-06-30)

249
RAN17.1

MO
Setting Notes
Data Source
MML Command
UINTRAFR
EQNCELL

on the plan.
Network plan
ADD
UINTRAFREQNCELL
NOTICE
The primary scrambling codes of intra-frequency neighboring cells of a cell should be different
from each other.
Procedure
l
Using MML commands

1.
2.
Run the LST UINTRAFREQNCELL command to query the intra-frequency

neighboring cell.
If...
Then...
There are cells that belong to a

neighboring RNC
Go to Step 2.
There is no cell that belongs to a

neighboring RNC
Go to Step 4.
Run the LST UEXT3GCELL command to check whether the basic parameters of
neighboring cells that belong to other RNCs are configured on the local RNC.
If...
Then...
There are cells that are not configured at

the local RNC
1. Run the ADD UEXT3GCELL

command to add the parameters of a
neighboring cell under another RNC.
To add the parameters of multiple
neighboring cells under other RNCs,
run this command for each cell.
2. Go to Step 3.
All cells have been configured on the

local RNC
3.
Issue 03 (2015-06-30)
Go to Step 3.
Run the LST UNRNCURA command and specify Neighboring RNC ID to query
whether all the URA IDs are configured on the local RNC.

250
RAN17.1
If...
Then...
There are URA IDs that are not

configured
1. Run the ADD UNRNCURA

command to add a URA ID of the
neighboring RNC. To add more
URA IDs, run this command for each
URA ID.
2. Go to Step 4.
All URA IDs are configured
4.
Go to Step 4.
Run the ADD UINTRAFREQNCELL command to add an intra-frequency

neighboring cell.
To add multiple intra-frequency neighboring cells, run this command for each intrafrequency neighboring cell.

1.
In the left pane of the planned data area, right-click a UMTS cell and choose
Neighboring Cell Configuration Express from the shortcut menu. The
neighboring cell configuration express is displayed, as shown in Figure 8-11.
Figure 8-11 Neighboring cell configuration express
Issue 03 (2015-06-30)
Area 1
Area for selecting cells
Area 2
Area for selecting neighboring cell types
Area 3
Area for selecting neighboring NEs in intra or inter-OSS

systems.
Area 4
Area for the neighboring cell resource pool
Area 5
Area for the options and the neighboring cell templates
Area 6
Area for configuring neighboring cells

251
RAN17.1
2.
Add and modify neighbor relationships.

If you need
to...
Then...
Add an intrafrequency
neighboring cell
1. Click Intra-frequency Neighboring Cell in area 2.

2. In area 3, select the base station controller to which the
target cells belong. In area 4, information about cells that
can be configured as neighboring cells is displayed.
3. In area 4, select a target cell.
NOTE
You can right-click in area 4 and choose Load from the shortcut
menu to select the target cell by loading a file.
4. In area 5, select a neighboring cell template, and select

Bidirectional based on site requirements to configure
bidirectional neighbor relationships.
NOTE
If Bidirectional is cleared, only the unidirectional neighbor
relationship between the source cell and the target cell is
configured.
5. Click Add to add a neighboring relationship.

Modify
neighboring cell
configuration
data
1. In area 6, right-click a neighboring cell record whose

configuration data you want to modify and choose
Modify Ncell Relationship from the shortcut menu. A
dialog box is displayed for you to modify data.
2. Modify the data, and close the dialog box.

You can modify neighboring cell data in batches by exporting data from the live network
to a file, modifying the neighboring cell information in the file, and importing the file
into the CME.
1.
Data > Export Radio Network Planning Data (CME client mode) or CME >
UMTS Application > Export Data > Export Radio Network Planning Data
(U2000 client mode). Then, export the parameters you want to reconfigure to a
file.
2.
3.
Data > Import Radio Network Planning Data (CME client mode) or CME >
UMTS Application > Import Data > Import Radio Network Planning Data
(U2000 client mode). Then, import the file into the CME.
section Importing and Exporting a Radio Data Planning File in UMTS
Application Management in the U2000 Help.
----End
Issue 03 (2015-06-30)

252
RAN17.1
Example
//Querying intra-frequency neighboring cells
LST UINTRAFREQNCELL: RncId=1819, CellId=51058, NCellRncId=250,NCellId=4700,
LstFormat=VERTICAL;
//Adding a neighboring cell under another RNC
ADD UEXT3GCELL: NRncId=250, CellId=4700, CellHostType=SINGLE_HOST,
CellName="CELL65537", CnOpGrpIndex=0, PScrambCode=256, BandInd=Band1,
UARFCNUplinkInd=TRUE, UARFCNUplink=9750, UARFCNDownlink=10700,
TxDiversityInd=FALSE, LAC=H'2506, CfgRacInd=NOT_REQUIRE, QqualminInd=FALSE,
QrxlevminInd=FALSE, MaxAllowedUlTxPowerInd=FALSE,
CellCapContainerFdd=EDCH_SUPPORT-1, EFachSupInd=FALSE;
//Adding an intra-frequency neighboring cell
ADD UINTRAFREQNCELL: RNCId=1819, CellId=51058, NCellRncId=250, NCellId=4700,
SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, NPrioFlag=FALSE;
Follow-up Procedure
l
Verification
Run the LST UINTRAFREQNCELL command to check whether the intra-frequency
neighboring cell is correctly added.
Rollback
Using MML commands
For the detailed rollback procedure, see 8.3.6 Removing a Neighboring Cell.
1.
2.
3.
8.3.2 Adding an Inter-Frequency Neighboring Cell

This section describes how to add an inter-frequency neighboring cell to a specified cell during
capacity expansion, for example, when NodeBs are added.
Prerequisites
l
Before adding an inter-frequency neighboring cell, collect information listed in Table

8-28.
Issue 03 (2015-06-30)
Information
Description
Cell information
Query and record the cell ID and interfrequency neighboring cell parameters.

253
RAN17.1
None
None
License requirement
None
Context
MO
Setting Notes
Data Source
MML Command
UINTERFR
EQNCELL

on the plan.
Network plan
ADD
UINTERFREQNCELL
NOTICE
l Any two inter-frequency neighboring cells of a cell must have different uplink frequencies,
downlink frequencies, or scrambling codes.
l A maximum of two pairs can be formed by an uplink frequency and a downlink frequency
of the inter-frequency neighboring cell.
Procedure
l
Using MML commands

1.
Run the LST UINTERFREQNCELL command to query and record inter-frequency

neighboring cells before the reconfiguration.
2.
Check the planned inter-frequency neighboring cells.
3.
Issue 03 (2015-06-30)
If...
Then...
There are cells that belong to a

neighboring RNC
Go to Step 3.
There is no cell that belongs to a

neighboring RNC
Go to Step 5.
Run the LST UEXT3GCELL command to check whether the basic parameters of
neighboring cells that belong to other RNCs are configured on the local RNC.
254
RAN17.1
If...
Then...
There are neighboring RNC cells that

are not configured on the local RNC
1. Run the ADD UEXT3GCELL to

add a neighboring cell under another
RNC. To add multiple neighboring
cells under other RNCs, run this
command for each neighboring cell
under other RNCs.
2. Go to Step 4.
All neighboring RNC cells are

configured on the local RNC
4.
Go to Step 4.
Run the LST UNRNCURA command and specify Neighboring RNC ID to check
whether all URA IDs of neighboring cells are configured on the local RNC.
If...
Then...
There are URA IDs that are not

configured on the local RNC
1. Run the ADD UNRNCURA

command to add a URA ID of a
neighboring RNC. To add multiple
URA IDs, run this command for each
URA ID.
2. Go to Step 5.
All URA IDs are configured on the local

RNC
5.
Go to Step 5.
Run the ADD UINTERFREQNCELL command to add an inter-frequency

neighboring cell.
To add multiple inter-frequency neighboring cells, run this command for each interfrequency neighboring cell.

1.
Issue 03 (2015-06-30)

255
RAN17.1
2.
Area 1
Area 2
Area 3

systems.
Area 4
Area 5
Area 6

If you need
to...
Then...
Add an interfrequency
neighboring cell
1. Click Inter-frequency Neighboring Cell in area 2.

NOTE

NOTE
configured.
Issue 03 (2015-06-30)

256
RAN17.1
If you need
to...
Then...
Modify
neighboring cell
configuration
data


into the CME.
1.
file.
2.
3.
----End
Example
//Querying inter-frequency neighboring cells
LST UINTERFREQNCELL: RNCId=1819, CellId=51058, NCellRncId=250;
//Adding a neighboring cell under another RNC
ADD UEXT3GCELL: NRncId=250, CellId=4700, CellHostType=SINGLE_HOST,
CellName="CELL65537", CnOpGrpIndex=0, PScrambCode=256, BandInd=Band1,
UARFCNUplinkInd=TRUE, UARFCNUplink=9750, UARFCNDownlink=10700,
TxDiversityInd=FALSE, LAC=H'2506, CfgRacInd=NOT_REQUIRE, QqualminInd=FALSE,
QrxlevminInd=FALSE, MaxAllowedUlTxPowerInd=FALSE,
CellCapContainerFdd=EDCH_SUPPORT-1, EFachSupInd=FALSE;
//Adding an inter-frequency neighboring cell
ADD UINTERFREQNCELL: RNCId=1819, CellId=51058, NCellRncId=250, NCellId=4700,
SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=FALSE,
NPrioFlag=FALSE, InterNCellQualReqFlag=FALSE, CLBFlag=FALSE;
Follow-up Procedure
l
Issue 03 (2015-06-30)
Verification
257
RAN17.1
Run the LST UINTERFREQNCELL command to check whether the inter-frequency

neighboring cell is correctly added.
l
Rollback
Using MML commands
1.
2.
3.
8.3.3 Adding a Neighboring GSM Cell

This section describes how to add a neighboring GSM cell at the coverage edge of a WCDMA
cell when the neighbor relationship between WCDMA and GSM cells changes after capacity
expansion.
Prerequisites
l
Before adding a neighboring GSM cell, collect information listed in Table 8-30.
Information
Description
Cell information
Query and record the UMTS cell ID and

neighboring GSM cell parameters.
None
None
License requirement
None
Context
Issue 03 (2015-06-30)

258
RAN17.1

MO
Setting Notes
Data Source
MML Command
UEXT2GCE
LL

on the plan.
Network plan
ADD UEXT2GCELL
U2GNCELL

on the plan.
Network plan
ADD U2GNCELL
NOTICE
l
Any two neighboring GSM cells of a cell must have different BTS color codes, network
color codes, frequencies, or band indicators.
A maximum of 32 neighboring GSM cells can be added.
Using MML commands
Procedure
1.
Run the LST U2GNCELL command to check whether the basic information of
neighboring GSM cells is configured on the local RNC.
If...
Then...
The basic information of the

neighboring GSM cells are not
configured
1. Run the ADD UEXT2GCELL

command to add neighboring GSM
cells.
2. Go to Step 2.
The basic information of the

neighboring GSM cells are configured
2.
l
Go to Step 2.
Run the ADD U2GNCELL command to add a neighboring GSM cell.

1.
Issue 03 (2015-06-30)

259
RAN17.1
2.
Area 1
Area 2
Area 3

systems.
Area 4
Area 5
Area 6

If you need
to...
Then...
Add a
neighboring
GSM cell
1. Click GSM Neighboring Cell in area 2.

NOTE

NOTE
configured.
Issue 03 (2015-06-30)

260
RAN17.1
If you need
to...
Then...
Modify
neighboring cell
configuration
data


into the CME.
1.
file.
2.
3.
----End
Example
//Querying the basic information of a neighboring GSM cell
LST U2GNCELL: RNCId=1819, CellId=51058;
//Adding the basic information of a neighboring GSM cell
ADD UEXT2GCELL: GSMCellIndex=0, GSMCellName="GSMCell1", NBscIndex="1",
LdPrdRprtSwitch="ON", MCC="460", MNC="01", CnOpGrpIndex=1, LAC=H'1234,
CfgRacInd=REQUIRE, RAC=0, CID=1, NCC=1, BCC=1, BcchArfcn=512,
BandInd=GSM900_DCS1800_BAND_USED, RatCellType=GPRS;
//Adding a neighboring GSM cell
ADD U2GNCELL: RNCId=1819, CellId=51058, GSMCellIndex=0, BlindHoFlag=FALSE,
NPrioFlag=FALSE;
Follow-up Procedure
l
Verification
Run the LST U2GNCELL command to check whether the neighboring GSM cell is
correctly added.
Issue 03 (2015-06-30)

261
RAN17.1
Rollback
Using MML commands
1.
2.
3.
8.3.4 Adding a Neighboring LTE Cell

This section describes how to add a neighboring LTE cell when the UMTS and LTE coverage
areas overlap after capacity expansion.
Prerequisites
l
Before adding a neighboring LTE cell, collect information listed in Table 8-32.
Information
Description
Configuration information
Query and record the ID of the UMTS cell

and configuration parameters of the
neighboring LTE cell.
None
None
License requirement
None
Context
Issue 03 (2015-06-30)
MO
Setting Notes
Data Source
MML Command
ULTECELL
Add an LTE cell based

on the plan.
Network plan
ADD ULTECELL

262
RAN17.1
MO
Setting Notes
Data Source
MML Command
ULTENCEL
L
Add a neighboring LTE

cell based on the plan.
Network plan
ADD ULTENCELL
Procedure
l
Using MML commands

1.
Run the LST ULTECELL command to query whether the neighboring LTE cell has
been configured on the local RNC.
If...
Then...
The neighboring LTE cell has not been

configured on the RNC
1. Run the ADD ULTECELL

command to add a neighboring LTE
cell.
2. Go to Step 2.
The neighboring LTE cell has been

configured on the RNC
2.
l
Go to Step 2.
Run the ADD ULTENCELL to add a neighboring LTE cell for the UMTS cell.

1.
Issue 03 (2015-06-30)
Area 1
Area 2

263
RAN17.1
Area 3

systems.
Area 4
Area 5
Area 6
2.
Click Neighboring LTE Cell in area 2.
3.
In area 3, select the eNodeB to which the target cells belong. In area 4, information
about cells that can be configured as neighboring cells is displayed.
4.
In area 4, select a target cell.

NOTE
You can right-click in area 4 and choose Load from the shortcut menu to select the target
cell by loading a file.
5.
In area 5, select a neighboring cell template, and select Bidirectional based on site
requirements to configure bidirectional neighbor relationships.
NOTE
If Bidirectional is cleared, only the unidirectional neighbor relationship between the source
cell and the target cell is configured.
6.
Click Add to add a neighboring relationship.

into the CME.
1.
file.
2.
3.
----End
Example
//Querying whether the neighboring LTE cell has been configured on the local RNC
LST ULTECELL: LstType=ByLTECellId, MCC="460", MNC="01", TAC=10;
Issue 03 (2015-06-30)

264
RAN17.1
//Adding an LTE cell
ADD ULTECELL: LTECellIndex=0, LTECellName="LTECELL1", EUTRANCELLID=1, MCC="460",
MNC="01", TAC=10, CnOpGrpIndex=1, CellPHYID=100, LTEBand=10, LTEArfcn=4150,
SuppPSHOFlag=Support;
//Adding a neighboring LTE cell for the UMTS cell
ADD ULTENCELL: RNCId=1819, CellId=51058, LTECellIndex=0;
Follow-up Procedure
l
Verification
Run the LST ULTENCELL to check whether the neighboring LTE cell is correctly
configured.
Rollback
Using MML commands
1.
2.
3.
8.3.5 Modifying a Neighboring Cell

This section describes how to modify the neighboring cell of a specified cell when the neighbor
relationship changes after capacity expansion or network optimization. For example, you can
change the neighboring cell of cell A from cell B to cell C.
Prerequisites
None
Procedure
Step 1 Add a neighboring cell based on the neighboring cell type.
l 8.3.1 Adding an Intra-Frequency Neighboring Cell
l 8.3.2 Adding an Inter-Frequency Neighboring Cell
l 8.3.3 Adding a Neighboring GSM Cell
l 8.3.4 Adding a Neighboring LTE Cell
Step 2 Remove a neighboring cell by referring to the procedure in 8.3.6 Removing a Neighboring
Cell.
----End
Issue 03 (2015-06-30)

265
RAN17.1
8.3.6 Removing a Neighboring Cell

This section describes how to remove a neighboring cell when the neighbor relationship changes
after capacity expansion or network optimization. This includes unidirectional neighbor
relationship removal and bidirectional neighbor relationship removal.
Prerequisites
l
Before removing a neighboring cell, collect information listed in Table 8-34.

Information
Description
Cell information
Query and record the cell ID, and basic

information and parameters of neighboring
GSM cells.
None
None
License requirement
None
Context
Issue 03 (2015-06-30)
MO
Setting Notes
Data Source
MML Command
UINTERFR
EQNCELL

on the plan.
Network plan
RMV
UINTRAFREQNCELL
UINTERFR
EQNCELL

on the plan.
Network plan
RMV
UINTERFREQNCELL
U2GNCELL

on the plan.
Network plan
RMV U2GNCELL
ULTENCEL
L

on the plan.
Network plan
RMV ULTENCELL
UNRELATI
ON

on the plan.
Network plan
RMV UNRELATION

266
RAN17.1
NOTE
Assume that cell A and cell B reside under an RNC, and they are neighboring cells of each other. Removing
the neighboring cell of cell A unidirectionally means that cell B is removed from the neighboring cell list
of cell A, but cell A is not removed from the neighboring cell list of cell B. Removing the neighboring cell
of A bidirectionally means that cell B is removed from the neighboring cell list of cell A and meanwhile
cell A is removed from the neighboring cell list of cell B.
Procedure
l
Using MML commands

Unidirectional removal of an intra-frequency neighboring cell
1.
Run the LST UINTRAFREQNCELL command to query an intra-frequency

neighboring cell.
2.
Run the RMV UINTRAFREQNCELL command to remove the intra-frequency

neighboring cell.
3.
Run the LST UINTRAFREQNCELL command to check whether the

neighboring cell is successfully removed.
Unidirectional removal of an inter-frequency neighboring cell

1.
Run the LST UINTERFREQNCELL command to query an inter-frequency

neighboring cell.
2.
Run the RMV UINTERFREQNCELL command to remove the inter-frequency

neighboring cell.
3.
Run the LST UINTERFREQNCELL command to check whether the

neighboring cell is successfully removed.
Unidirectional removal of a neighboring GSM cell

1.
Run the LST U2GNCELL command to query a neighboring GSM cell.
2.
Run the RMV U2GNCELL command to remove the neighboring GSM cell.
3.
Run the LST U2GNCELL command to check whether the neighboring GSM cell
is successfully removed.
Unidirectional removal of a neighboring LTE cell

1.
Run the LST ULTENCELL command to query a neighboring LTE cell.
2.
Run the RMV ULTENCELL command to remove the neighboring LTE cell.
3.
Run the LST ULTENCELL command to check whether the neighboring LTE
cell is successfully removed.
Bidirectional removal of a neighboring cell
Issue 03 (2015-06-30)
1.
If the current cell is in serving state, run the HO UCELL command to forcibly
hand over UEs in a cell to a neighboring cell.
2.
If the current cell is activated, run the DEA UCELL command to deactivate the
cell.
3.
Run the RMV UNRELATION command and specify one or several types of
neighboring cells in Neighboring Cell Type, and then bidirectionally remove the
neighboring cells of the current cell within the RNC.

267
RAN17.1

NOTE
l Running the RMV UNRELATION command can bidirectionally remove a

neighboring cell of a cell within one RNC.
l To remove the neighboring cells under another RNC, perform the operation on that
RNC.
4.
Run the ACT UCELL command to reactivate the cell for providing services.
5.

1.
Area 1
Area 2
Area 3

systems.
Area 4
Area 5
Area 6
2.
Select a source cell in area 1.
3.
Select a neighboring cell type in area 2.
4.
In area 6, select a neighbor relationship record you want to delete and click
Delete.

into the CME.
Issue 03 (2015-06-30)

268
RAN17.1
1.
file.
2.
3.
----End
Example
//Querying an intra-frequency neighboring cell
LST UINTRAFREQNCELL: RNCId=1819, CellId=51058;
//Querying an inter-frequency neighboring cell
LST UINTERFREQNCELL: RNCId=1819, CellId=51058;
//Querying a neighboring GSM cell
LST U2GNCELL: RNCId=1819, CellId=51058;
//Querying a neighboring LTE cell
LST ULTENCELL: RNCId=1819, CellId=51058;
//Removing an intra-frequency neighboring cell
RMV UINTRAFREQNCELL: RNCId=1819, CellId=51058, NCellRncId=250, NCellId=4700;
//Removing an inter-frequency neighboring cell
RMV UINTERFREQNCELL: RNCId=1819, CellId=51058, NCellRncId=250, NCellId=4700;
//Removing a neighboring GSM cell
RMV U2GNCELL: RNCId=1819, CellId=51058, GSMCellIndex=450;
//Removing a neighboring LTE cell
RMV ULTENCELL: RNCId=1819, CellId=51058, LTECellIndex=0;
//Forcibly handing over UEs in a cell to other cells
//Deactivating the current cell
//Bidirectionally removing neighboring cells of the current cell within the local
RNC
RMV UNRELATION: RNCId=1819, CellId=51058, NCellType=IntraFreqNCell//Reactivating a
cell
Follow-up Procedure
l
Verification
Run the LST U2GNCELL command to check whether the neighboring GSM cell is
correctly added.
Rollback
Using MML commands
Issue 03 (2015-06-30)

269
RAN17.1
For the detailed rollback procedure, see 8.3.1 Adding an Intra-Frequency

Neighboring Cell, 8.3.2 Adding an Inter-Frequency Neighboring Cell, and 8.3.3
Adding a Neighboring GSM Cell.
1.
2.
3.
8.4 Reconfiguring NodeB Management Distribution

When an SPU subsystem serves multiple NodeBs and the CPU usage of the SPU subsystem
exceeds 60%, you need to distribute these NodeBs to multiple SPU subsystems. When the NodeB
Application Part (NBAP) signaling message processing capability of a NodeB is larger than 300
times per second, you need to distribute the cells under this NodeB to multiple SPU subsystems
to improve system stability.
8.4.1 Regularly Reconfiguring NodeB Distribution Using MML

Commands
This section describes how to regularly reconfigure NodeB distribution using MML commands.
Prerequisites
l
Before reconfiguring NodeB distribution, collect information listed in Table 8-36.

Information
Description
Load of the SPU board
Query and record the CPU usage of the

SPU board and the number of NodeBs
carried on the SPU board.
None
None
License requirement
None
Issue 03 (2015-06-30)

270
RAN17.1
Context
An SPUa/SPUb/SPUc board has several logical subsystems, which are called SPU subsystems.
The NodeB whose NodeB Application Part (NBAP) signaling message processing capability is
larger than 300 times per second is called a super NodeB.
Generally, all the cells under a NodeB are managed by one SPU subsystem. The load of an
SPU subsystem increases when the number of users increases and the traffic model changes.
With the reconfiguration, the BSC6900 can distribute cells under a NodeB to several SPU
subsystems, avoiding overload of a single SPU subsystem. This enables the BSC6900 to support
a single NodeB with high traffic volume.
Users can distribute NodeBs, cells, NCPs/CCPs or ADJNODE (when the Iub interface works
in ATM or ATM/IP dual stack mode) to different SPU subsystems.
NOTICE
Reconfiguring the NodeB, NCP, CCP, or ADJNODE will interrupt services. Perform the
reconfiguration when the traffic is light, for example, during early morning hours.
The reconfiguration principles are as follows:
l
When the CPU usage of an SPU subsystem is larger than the value of CPU Threshold for
Schedule Assign Out, perform the reconfiguration as follows:
1.
If a single SPU subsystem is configured with several NodeBs, transfer some NodeBs
served by this SPU subsystem to other SPU subsystems.
2.
Do not transfer part of cells under a NodeB to other SPU subsystems unless the
SPU subsystem serves only one NodeB and the CPU usage of that SPU subsystem is
higher than the value of CPU Threshold for Schedule Assign Out.
Procedure
Step 1 Run the SET UCELLAUTOHOMING command to start the scheduled task. In this step, set
Schedule Homing Switch to ON and Schedule Homing Mode to MANUAL.
Step 2 If the loads of SPU subsystems in the BSC6900 are unbalanced, the BSC6900 reports
ALM-22240 Inappropriate NodeB Deployment and exports NodeB migration suggestion
scripts to the \ftp\OptMml directory in the active workspace of the OMU.
Step 3 If NodeB distribution needs to be reconfigured, run the RUN BATCHFILE command to
execute the NodeB reparenting scripts.
NOTE
If you need to update the NodeB reparenting scripts are updated based on the actual network condition,
obtain the migration file from the \ftp\OptMml directory in the active workspace of the OMU and then
modify the file as required.
----End
Issue 03 (2015-06-30)

271
RAN17.1
Example
//Starting a scheduled task
SET UCELLAUTOHOMING: SchedHomingSwitch=ON, SchedHomingMode=MANUAL;
Follow-up Procedure
l
Verification
Monitor the CPU usage of the SPU subsystem. The CPU usage decreases to the planned
value.
Rollback
8.4.2 Manually Reconfiguring NodeB Distribution

This section describes how to manually reconfigure NodeB distribution when you need to
determine the migrated objects and target migrated subsystems based on the CPU load of each
subsystem and NodeB deployment.
Prerequisites
l
Before reconfiguring NodeB distribution, collect information listed in Table 8-37.

Information
Description
Load of the SPU board
Query and record the CPU usage of the

SPU board and the number of NodeBs
carried on the SPU board.
None
None
License requirement
None
Context
An SPUa/SPUb/SPUc board has several logical subsystems, which are called SPU subsystems.
The NodeB whose NodeB Application Part (NBAP) signaling message processing capability is
larger than 300 times per second is called a super NodeB.
Generally, all the cells under a NodeB are managed by one SPU subsystem. The load of an
SPU subsystem increases when the number of users increases and the traffic model changes.
With the reconfiguration, the BSC6900 can distribute cells under a NodeB to several SPU
subsystems, avoiding overload of a single SPU subsystem. This enables the BSC6900 to support
a single NodeB with high traffic volume.
Issue 03 (2015-06-30)

272
RAN17.1
Users can distribute NodeBs, cells, NCPs/CCPs, or ADJNODE (when the Iub interface works
in ATM or ATM/IP dual stack mode) to different SPU subsystems.
NOTICE
Reconfiguring theNodeB, NCP, CCP, or ADJNODE will interrupt services. Perform the
reconfiguration when the traffic is light, for example, during early morning hours.
The reconfiguration principles are as follows:
l
When the CPU usage of an SPU subsystem is larger than 60%, perform the reconfiguration
as follows:
1.
If a single SPU subsystem is configured with several NodeBs, transfer some NodeBs
served by this SPU subsystem to other SPU subsystems.
2.
Do not transfer part of cells under a NodeB to other SPU subsystems unless the
SPU subsystem serves only one NodeB and the CPU usage of that SPU subsystem is
higher than 60%.
For a super NodeB, perform the reconfiguration as follows:

1.
Configure several SPU subsystems for a super NodeB. Use one of them to process
NodeB management services and the NCP or CCP and use other SPU subsystems to
process part of its cell management services.
2.
These SPU subsystems process services only on the planned super NodeB instead of
services of any other super NodeBs.
3.
Those SPU subsystems should belong to the same SPUa/SPUb/SPUc board. Those
SPU subsystems cannot belong to different boards in the same subrack unless all the
subsystems of the SPUa/SPUb/SPUc board are fully loaded. The SPU subsystems can
never belong to different subracks. This prevents traffic surge of inter-subrack
switching data.
For details about how to monitor the CPU usage of an SPU subsystem, see Monitoring Board
CPU/DSP Usage. After the reconfiguration, the CPU usage of the original SPU subsystem
decreases and that of the target SPU subsystem increases. That is, the CPU usage of SPU
subsystems approaches the average CPU usage.
Procedure
l
Using MML commands

1.
Collect information before the reconfiguration.

Collect information about the migrated objects listed in Table 8-38:
Issue 03 (2015-06-30)

273
RAN17.1
2.
Migrate
dObject
Informa
tion
Description
NodeB
NodeB
deploym
ent
informati
on
Run the LST UNODEB command to query Subsystem

No. of the NodeB. If the NodeB and its sub-objects are
migrated, run the LST UCELL command to query
Subsystem No. of all cells served by the NodeB and run
the LST UIUBCP command to query Subsystem No. of
the NCP and CCP.
Cell
Cell
informati
on
Run the LST UCELL command to query Subsystem

No. of all cells served by a NodeB.
NCP
NCP
informati
on
Run the LST UIUBCP command to query Subsystem

No. of the NCP.
CCP
CCP
informati
on
Run the LST UIUBCP command to query Subsystem

No. of the CCP.
If migration occurs in one of the scenarios listed in Table 8-39, run the MOV
UNODEB command to distribute NodeBs served by an SPU subsystem to multiple
SPU subsystems.
Table 8-39 Scenario
Migration Type
Description
Only NodeBs are migrated
Only NodeBs are migrated to the target

subsystem. Cells, NCPs, CCPs, and
ADJNODE (when the Iub interface
works in ATM or ATM/IP dual stack
mode) of the migrated NodeBs are
retained in the original subsystem.
All NodeBs served by a subsystem and

their sub-objects are migrated
All objects (including NodeBs and the

cells, NCPs, CCPs, and ADJNODE of
the NodeBs) under the current
subsystem are migrated to the target
subsystem.
In this scenario, the objects of the
migrated NodeBs on other subsystems
are not migrated.
Issue 03 (2015-06-30)

274
RAN17.1
3.
Migration Type
Description
NodeBs and all sub-objects are migrated
The NodeB and all its sub-objects

(including the NodeB and the cells,
NCPs, CCPs, and ADJNODE of the
NodeB) are migrated to the target
subsystem. The original sub-objects and
NodeBs can be served by the same or
different subsystems.
If the migration occurs in other scenarios excluded in Table 8-39, perform the
following steps:
Reconfiguring resource management based on NodeBs
a.
Run the MOV UNODEB to move the NodeBs which were originally
processed by a single SPU subsystem to several SPU subsystems. In this step,
set SRN, SN, and SSN to appropriate values.
Reconfiguring resource management based on cells

a.
Run the MOV UCELL to move the cells which were originally processed
by a single SPU subsystem to several SPU subsystems. In this step, set
SRN, SN, and SSN to appropriate values.
Reconfiguring resource management based on NCPs

a.
Run the MOV UNCP to move the NCPs to the target SPU system. In this
step, set SRN, SN, and SSN to appropriate values.
Reconfiguring resource management based on CCPs

a.
Run the MOV UCCP to move the CCPs to the target SPU system. In this
step, set SRN, SN, and SSN to appropriate values.
Reconfiguring resource management based on ADJNODE (only when the Iub

interface works in ATM or ATM/IP dual stack mode)
a.
l
Run the MOV ADJNODE to move the ADJNODE to the target SPU system.
In this step, set SRN, SN, and SSN to appropriate values.

You can use the Export Iub Bulk Configuration Data and Import Iub Bulk
Configuration Data functions provided by the CME to adjust data among SPU subsystems.
You can press F1 on the CME to view section Reparenting NodeBs Within an RNC in
the U2000 Help for the detailed function operations and introduction.
----End
Example
//Scenarios where migration cannot be implemented using only one command
//Migrating NodeBs
MOV UNODEB: IDTYPE=BYID, NodeBId=100, SRN=1, SN=2, SSN=3;
//Migrating cells
MOV UCELL: IDTYPE=ByCellId, CellId=101, SRN=1, SN=2, SSN=3;
Issue 03 (2015-06-30)

275
RAN17.1
//Migrating NCPs
MOV UNCP: IDTYPE=BYID, NodeBId=100, SRN=1, SN=2, SSN=3;
//Migrating CCPs
MOV UCCP: IDTYPE=BYID, NodeBId=100, PN=0, SRN=1, SN=2, SSN=3;
//Migrating ADJNODE
MOV ADJNODE: ANI=10, SRN=1, SN=2, SSN=3;
//Scenario where migration can be implemented using only one command
//Migrating only NodeB 1 to subsystem 3 of subrack 2 in cabinet 1
MOV UNODEB: IDTYPE=BYNAME, NodeBName="NodeB 1", SRN=1, SN=2, SSN=3,
MoveType=OnlyThisNodeBObj;
//Migrating NodeB2 to subsystem 3 of subrack 2 in cabinet 1 and cells,
NCPs, and CCPs of NodeB 2 to subsystem 4 of subrack 2 in cabinet 1
MoveType= ObjsOfThisNBOnNBSSN;
//Migrating NodeB 3 and all its sub-objects (including cells, NCPs, and
CCPs) to subsystem 5 of subrack 2 in cabinet 1
MoveType= AllObjsOfThisNodeB;
Follow-up Procedure
l
Verification
Monitor the CPU usage of the SPU subsystem. The CPU usage decreases to the planned
value.
Rollback
Using MML commands
1.
2.
3.
Issue 03 (2015-06-30)

276
RAN17.1
Reconfiguring the Interfaces
About This Chapter

This chapter describes how to reconfigure interfaces in the case of capacity expansion,
reconfiguration, and network cutover.
Context
In IP networking mode, it is recommended that two or more physical ports be configured on the
Iu interface (Iu-CS interface, Iu-PS interface, and Iur interface) to enhance reliability.
l
If signaling messages and service messages are transmitted on different physical ports, it
is recommended that signaling messages and service messages be respectively transmitted
on two or more physical ports. (The active and standby ports are considered as one port.)
If two or more subracks are configured on a BSC, it is recommended that physical ports
on the Iu interface (Iu-CS interface, Iu-PS interface, and Iur interface) be configured in
different subracks.
If only one subrack is configured on a BSC, it is recommended that physical ports on the
Iu interface (Iu-CS interface, Iu-PS interface, and Iur interface) be configured on different
boards. (The active and standby boards are considered as one board.)
Issue 03 (2015-06-30)

277
RAN17.1
9.1 Interface Capacity Expansion

This section describes how to expand the capacity of configured interfaces, excluding the
procedure for configuring newly added interfaces. For details about how to configure the newly
added interfaces, see BSC6900 UMTS Initial Configuration Guide.
Context
Transmission capacity expansion consists of three phases: evaluating transmission load,
designing the capacity expansion scheme, and implementing the capacity expansion scheme.
The first two phases are described in Huawei professional service documentation. This section
describes only how to implement the capacity expansion scheme.
In addition, transmission capacity expansion can refer to the expansion of the physical layer,
data link layer, control plane, user plane. Users can expand the capacity of a single layer or all
layers as required. Detailed information is described in Huawei professional service
documentation.
9.1.1 Iu-CS Interface Capacity Expansion

When the in-use transmission resources over the Iu-CS interface are insufficient due to an
increasing traffic volume, capacity expansion over the Iu-CS interface is required.
9.1.1.1 Iu-CS Interface Capacity Expansion (in ATM Transmission Mode)

This section describes how to expand the capacity over the Iu-CS interface in ATM transmission
mode.
Prerequisites
l
Before expanding the capacity, collect information listed in Table 9-1.

Information
Description
Interface
board physical
information
Query and record the board model, quantity of boards, board

installation position (slot No.), backup modes of the board and
interface, and port parameters.
Data link layer

information
Negotiation of information about the E1/T1 link, IMA link, IMA group
with the peer end.
NOTE
If only IMA and E1/T1 links are added, all attributes of the newly added E1/T1
links must be consistent with those of the E1/T1 links corresponding to the
existing IMA links in the IMA group.
Issue 03 (2015-06-30)

278
RAN17.1
Information
Description
Control plane
information
SAAL link data planning, including the bearing IMA group No.,
bearing VPI, bearing VCI, bearing type, TX traffic record index, RX
traffic record index, and interface type, must be complete.
MTP3 signaling link data planning, including signaling link code,
signaling link priority, signaling link name, test code length, and test
code, must be complete.
User plane
information
AAL2 path data planning, including the bearing subrack No., bearing
slot No., bearing VPI, bearing VCI, TX traffic record index, RX traffic
record index, and AAL2 path type, must be complete.
The interface board has been installed.
None
License requirement
None
Context
Data Type
MO
Setting Notes
Data
Source
MML
Command
Physical layer
configuration
BRD
Add a board.
Network
plan
ADD BRD
Data link layer

configuration
E1T1
Modify attributes
of the E1/T1 link.
Network
plan
SET E1T1
IMALNK
Add an IMA link.
Network
plan
ADD IMALNK
SAALLNK
Add an SAAL
link.
Network
plan
ADD
SAALLNK
MTP3LNK
Add an MTP3
link.
Network
plan
ADD
MTP3LNK
AAL2PATH
Add an AAL2
path.
Network
plan
ADD
AAL2PATH
Control plane
configuration
User plane
configuration
Issue 03 (2015-06-30)

279
RAN17.1
Procedure
l
Back up configuration data before capacity expansion.

1.
Run the BKP DB command to back up the database.
2.
Run the EXP CFGMML command to back up the configuration scripts.
Expand capacity of the physical layer and data link layer for the newly added AEUa, AOUa,
and AOUc boards.
1.
2.
Run the SET E1T1 command to add an E1/T1 transmission link. To add more E1/T1
links, run this command for each E1/T1 link.
3.
Optional: If the interface board is an optical interface board, such as AOUa and
AOUc, run the SET OPT command to set the attributes of the optical interface.
4.
Run the ADD IMAGRP command to add an IMA group.
5.
Run the ADD IMALNK command to add an IMA link, which is carried on the E1/
T1 link. To add more IMA links, run this command for each IMA link.
Expand capacity of the physical layer and data link layer for the existing AEUa, AOUa,
and AOUc boards.
1.
Run the LST E1T1 command to query the attributes of configured E1/T1 links.
If the attributes of the configured E1/T1 links are consistent with those of the E1/
T1 links corresponding to other IMA links in the IMA group, go to Step 2.
If the attributes of the configured E1/T1 links are inconsistent with those of the
E1/T1 links corresponding to other IMA links in the IMA group, run the SET
E1T1 to modify the attributes of the configured E1/T1 links.
2.
3.
Expand capacity of the physical layer and data link layer for the newly added UOIa and
UOIc boards.
1.
2.
Run the SET OPT command to set the attributes of the optical interface.
Expand the capacity of the control plane.

1.
Run the ADD SAALLNK command to add an SAAL link. In this step, set Interface
type to NNI. To add more SAAL links, run this command for each SAAL link.
2.
Run the ADD MTP3LNK command to add an MTP3 signaling link. To add more
MTP3 signaling links, run this command for each MTP3 signaling link.
Expand the capacity of the user plane.

1.
Run the ADD AAL2PATH command to add an AAL2 path. To add more AAL2
paths, run this command for each AAL2 path.
----End
Example
/*Data Backup Procedure*/
Issue 03 (2015-06-30)

280
RAN17.1
//Backing up the database

BKP DB:;
//Backing up the configuration scripts
EXP CFGMML:;
//Querying the MSP backup mode
//Querying the attributes of an E1/T1 link
LST E1/T1: SRN=0, SN=14, BT=AOUc;
//Setting the attributes of an E1/T1 link
SET E1T1: SRN=0, SN=14, BT=AOUc, PS=SINGLE, PN=5,
PTTYPE=E1_CRC4_MULTI_FRAME, SCRAMBLESW=OFF, LOOPSW=OFF;
//Adding an IMA link
ADD IMALNK: SRN=0, SN=14, IMALNKN=5, IMAGRPSN=14, IMAGRPN=0;
//Adding an SAAL link
ADD SAALLNK: SAALLNKN=0, CARRYT=IMA, CARRYSRN=0, CARRYSN=14,
CARRYIMAGRPN=0, CARRYVPI=9, CARRYVCI=34, TXTRFX=100, RXTRFX=100,
SAALLNKT=NNI;
//Adding an MTP3 link
ADD MTP3LNK: SIGLKSX=0, SIGSLC=0, BEARTYPE=SAAL, SAALLNKN=0, NAME="for
MTP3";
//Adding an AAL2 path
ADD AAL2PATH: ANI=0, PATHID=1, CARRYT=IMA, CARRYF=0, CARRYSN=14,
CARRYIMAGRPN=9, RSCGRPFLAG=NO, VPI=9, VCI=36, TXTRFX=100, RXTRFX=100,
AAL2PATHT=R99;
//Removing an AAL2 path
RMV AAL2PATH: ANI=0, PATHID=1;
//Removing an MTP3 link
RMV MTP3LNK: SIGLKSX=0, SIGSLC=0;
//Removing an SAAL link
RMV SAALLNK: SAALLNKN=0;
//Removing an IMA link
RMV IMALNK: SRN=0, SN=14, IMALNKN=5;
//(Optional) Setting the E1/T1 attributes to their original
configurations
SET E1T1: SRN=0, SN=14, BT=AOUc, PS=SINGLE, PN=5, PTTYPE=E1_DOUBLE_FRAME,
SCRAMBLESW=OFF, LOOPSW=OFF;
Follow-up Procedure
l
Verification
1.
Run the DSP IMALNK command to query the IMA link status.
Expected result: The IMA link status is normal.
2.
Run the DSP IMAGRP command to query the IMA group status.
Expected result: The IMA group status is normal.
3.
Issue 03 (2015-06-30)
Run the DSP SAALLNK command to query the SAAL link status.
281
RAN17.1
Expected result: The SAAL link status is normal.

4.
Run the DSP MTP3LNK command to query the MTP3 link status.
Expected result: The MTP3 link status is normal.
5.
Run the DSP MTP3LKS command to query the MTP3 link set status.
Expected result: The MTP3 link set status is normal.
6.
Run the DSP AAL2PATH command to query the AAL2 path status.
Expected result: The AAL2 path status is normal.
7.
l
Verify network reliability.
Rollback
1.
Run the RMV AAL2PATH command to remove an AAL2 path.
2.
Run the RMV MTP3LNK command to remove an MTP3 link.
3.
Run the RMV SAALLNK command to remove an SAAL link.
4.
Run the RMV IMALNK command to remove an IMA link.
5.
Run the SET E1T1 to restore the E1/T1 attribute configurations.
6.
Restore the hardware connection.
9.1.1.2 Iu-CS Interface Capacity Expansion (in IP Transmission Mode)

This section describes how to expand the capacity over the Iu-CS interface in IP transmission
mode.
Prerequisites
l

Issue 03 (2015-06-30)
Informatio
n
Description
Interface
board
physical
information
Query and record the board model, quantity of boards, board installation
position (slot No.), backup modes of the board and interface, and port
parameters.
Data link
layer
information
(IP over E1/
T1)
Negotiation of information about an E1/T1 link, MLPPP link, MLPPP

group with the peer end.
Data link
layer
information
(IP over FE/
GE)
Plan of information about the Ethernet port.
If only MLPPP links are added to the existing MLPPP group, all
attributes of the newly added E1/T1 links must be consistent with those
of the existing E1/T1 links in the MLPPP group.
If Ethernet ports are added to the existing Ethernet trunk group, all
attributes of the added Ethernet ports must be the same as those of the
existing Ethernet ports in the Ethernet trunk group. If they are not the
same, run the SET ETHPORT command to set the attributes of the
added Ethernet ports.

282
RAN17.1
Informatio
n
Description
Control plane
information
SCTP link data planning, including the application type, work mode,
local IP address, and peer IP address, must be complete.
M3UA signaling link data planning, including subrack No., slot No.,
SCTP link ID, SCTP link No., and M3UA link name, must be complete.
User plane
information
IP path data planning, including the interface type, transmission type,

local IP address, peer IP address, transmit bandwidth, and receive
bandwidth, must be complete.
None
License requirement
None
Context
Data Type
MO
Setting Notes
Data
Source
MML Command
Physical layer
BRD
Add a board.
Network
plan
ADD BRD
Data link layer (IP

over E1/T1)
E1T1
Modify E1/T1
attributes.
Network
plan
SET E1TI
MPLNK
Add an MLPPP
link.
Network
plan
ADD MPLNK
ETHPORT
Modify
attributes of the
Ethernet port.
Network
plan
SET ETHPORT
ETHTRKL
NK
Add a link to the

Ethernet trunk.
Network
plan
ADD
ETHTRKLNK
SCTPLNK
Add an SCTP
link.
Network
plan
ADD SCTPLNK
M3LNK
Add an M3UA
link.
Network
plan
ADD M3LNK
Data link layer (IP

over FE/GE)
Control plane
Issue 03 (2015-06-30)

283
RAN17.1
Data Type
MO
Setting Notes
Data
Source
MML Command
User plane
IPPATH
Add an IP path.
Network
plan
ADD IPPATH
Procedure
l
Back up data before capacity expansion.

1.
Run the BKPDB command to back up the database.
2.
Expand capacity of the physical layer and data link layer for the newly added PEUa, POUa,
and POUc boards.
1.
Run the ADDBRD command to add an interface board.
2.
Run the SETE1TI command to add an E1/T1 transmission link. To add more E1/T1
3.
Optional: If the interface board is an optical interface board, such as POUa and POUc,
run the SET OPT command to set the attributes of the optical interface.
4.
Run the ADD MPLNK command to add an MLPPP link, which is carried on the E1/
T1 link. To add more MLPPP links, run this command for each MLPPP link.
Expand capacity of the physical layer and data link layer for the existing PEUa, POUa, and
POUc boards.
1.
Run the LSTE1TI command to query the attributes of configured E1/T1 links.
T1 links corresponding to other MLPPP links in the MLPPP group, go to Step 2.
E1/T1 links corresponding to other MLPPP links in the MLPPP group, run the
SET E1TI command to modify the attributes of the configured E1/T1 links.
Issue 03 (2015-06-30)
2.
3.
Expand capacity of the physical layer and data link layer for the newly added FG2a, FG2c,
GOUa, GOUc, and GOUe boards.
1.
2.
Run the SET ETHPORT command to set the attributes of the Ethernet port.
3.
Run the ADD ETHTRKLNK command to add a link to the Ethernet trunk, which is
carried on the Ethernet port. To add more links, run this command for each link.

1.
Run the ADD SCTPLNK command to add an SCTP link. In this step, set Application
type to M3UA. To add more SCTP links, run this command for each SCTP link.
2.
Run the ADD M3LNK command to add an M3UA signaling link. To add more M3UA
signaling links, run this command for each M3UA signaling link.
284
RAN17.1

1.
Run the ADD IPPATH command to add an IP path. To add more IP paths, run this
command for each IP path.
----End
Example
BKP DB:;
EXP CFGMML:;
//(IP over E1/T1) Querying the attributes of an E1/T1 link
LST E1T1: SRN=0, SN=14;
//(IP over E1/T1) Modifying the attributes of an E1/T1 link
SET E1T1: SRN=0, SN=14, BT=POUc, PS=SINGLE, PN=5,
PTTXT=E1_CRC4_MULTI_FRAME;
//(IP over E1/T1) Adding the attributes of an MLPPP link
ADD MPLNK: SRN=0, SN=14, BRDTYPE=POUc, MPGRPN=0, PPPLNKN=4, DS1=5,
TSBITMAP=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS1
1-1TS12-1&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&
TS22-1&TS23-1&TS24-1&TS25-1&TS26-1&TS27-1TS28-1&TS29-1&TS30-1&TS31-1;
//(IP over FE/GE) Querying the attributes of an Ethernet port
LST ETHPORT: SRN=0, SN=14;
//(IP over FE/GE) Modifying the attributes of an Ethernet port
SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2c, PTYPE=GE, PN=0, SPEED=1000M,
MTU=1500;
//(IP over FE/GE) Adding a link in the Ethernet trunk
ADD ETHTRKLNK: SRN=0, SN=14, TRKN=0, TRKLNKSN=14, TRKLNKPN=4,
WORKMODE=LOAD_SHARING;
//Adding an SCTP link
ADD SCTPLNK: APP=M3UA, SCTPLNKID=0, MODE=CLIENT, LOCIP1="172.23.1.32",
PEERIP1="172.23.1.100", PEERPN=1024, LOGPORTFLAG=NO, VLANFLAG1=DISABLE,
VLANFLAG2=DISABLE, SWITCHBACKFLAG=YES;
//Adding an M3UA link
ADD M3LNK: SIGLKSX=0, SIGLNKID=4, SRN=0, SN=0, NAME="for M3UA";
//Adding an IP path
ADD IPPATH: ANI=0, PATHID=2, ITFT=IUCS, PATHT=QoS, IPADDR="172.23.1.32",
PEERIPADDR="172.23.1.100", TXBW=10000, RXBW=10000, CARRYFLAG=NULL,
VLANFlAG=DISABLE, PATHCHK=DISABLED;
//Removing an IP path
RMV IPPATH: ANI=0, PATHID=2;
//Removing an M3UA link
Issue 03 (2015-06-30)

285
RAN17.1
RMV M3LNK: SIGLKSX=0, SIGLNKID=4;

//Removing an SCTP link
RMV SCTPLNK: SCTPLNKID=0;
//Adding a link in the trunk
RMV ETHTRKLNK: SRN=0, TRKLNKSN=14, TRKLNKPN=4;
//(Optional) Setting the attributes of an Ethernet port to their original
configurations
SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2c, PTYPE=GE, PN=0, SPEED=AUTO,
MTU=1500;
configurations
SET E1T1: SRN=0, SN=14, BT=POUc, PS=SINGLE, PN=5, PTTXT=E1_DOUBLE_FRAME;
Follow-up Procedure
l
Verification
1.
Run the DSP MPLNK command to query the MLPPP link status.
Expected result: The MLPPP link status is normal.
2.
Run the DSP MPGRP command to query the MLPPP group status.
Expected result: The MLPPP group status is normal.
3.
Run the DSP ETHTRKLNK command to remove a link in the Ethernet trunk.
Expected result: The trunk link status is normal.
4.
Run the DSP ETHTRK command to query the trunk status.

Expected result: The trunk status is normal.
5.
Run the DSP SCTPLNK command to query the SCTP link status.
Expected result: The SCTP link status is normal.
6.
Run the DSP M3LNK command to query the M3UA link status.
Expected result: The M3UA link status is normal.
7.
Run the DSP M3LKS command to query the M3UA link set status.
Expected result: The status of the M3UA link set is normal.
8.
Run the DSP IPPATH command to query the IP path status.

Expected result: The IP path status is normal.
9.
l
Issue 03 (2015-06-30)
Rollback
1.
Run the RMV IPPATH command to remove an IP path.
2.
Run the RMV M3LNK command to remove an M3UA link.
3.
Run the RMV SCTPLNK command to remove an SCTP link.
4.
Run the RMV ETHTRKLNK command to remove an Ethernet trunk link.
5.
Run the SET ETHPORT command to restore the Ethernet port attribute
configurations.
6.
Run the RMV MPLNK command to remove an MLPPP link.
7.
Run the SET E1T1 command to restore the E1/T1 attribute configurations.
286
RAN17.1
8.
9.1.1.3 Iu-CS Interface Capacity Expansion (IP Pool)

This section describes how to expand the capacity over the Iu-CS interface in IP pool
transmission mode.
Prerequisites
l

Information
Description
Interface
board physical
information
Model, quantity, installation position (slot No.), backup mode,

interface backup mode, and port parameters of the interface board
Data link layer

information
Plan information about the Ethernet port.
Control plane
information
User plane
information
Plan the SIP information (IP Address in Transmission Resource

Pool in the ADD IPPOOLIP command).
If the local IP address of the transmission resource pool in the original
IP pool is DEVIP, the capacity expansion can be performed only by
adding a device IP.
IP pool is ETHIP or ETHTRKIP, the capacity expansion can be
implemented only by adding an ETHIP or ETHTRKIP.
None
License requirement
None
Context
Issue 03 (2015-06-30)

287
RAN17.1

Data Type
MO
Setting Notes
Data
Source
MML Command
Physical layer
BRD
Add a board.
Network
plan
ADD BRD
Data link layer
ETHPORT
Modify the
attributes of the
Ethernet port.
Network
plan
SET ETHPORT
ETHTRKL
NK
Add a trunk link.
Network
plan
ADD ETHTRKLNK
DEVIP
Add a device IP
address.
Network
plan
ADD DEVIP
Policybased route
based on
the source
IP address
(SRCIPRT
)
Add a policy-based
route based on the
source IP address.
Network
plan
ADD SRCIPRT
SCTPLNK
Add an SCTP link.
Network
plan
ADD SCTPLNK
M3LNK
Add an M3UA link.
Network
plan
ADD M3LNK
IPPOOLIP
Add the local IP

address in
transmission
resource pool.
Network
plan
ADD IPPOOLIP
Control plane
User plane
Procedure
l

1.
2.
Expand capacity of the physical layer and data link layer for the newly added boards.
1.
2.
3.
Run the ADD ETHTRKLNK command to add an Ethernet trunk link, which is
4.
Run the ADD DEVIP command to add the device IP address of the board.
Expand capacity of the physical layer and data link layer for existing boards.
1.
Issue 03 (2015-06-30)
Run the LST ETHPORT command to query the attributes of the Ethernet port.
288
RAN17.1
If the attributes of the Ethernet port are consistent with those of other Ethernet
ports in the trunk link, go to Step 2.
If the attributes of the Ethernet port are inconsistent with those of other Ethernet
ports in the trunk link, run the SET ETHPORT command to modify the attributes
of an Ethernet port.
2.
l
carried on the Ethernet port. To add more trunk links, run this command for each link.

1.
2.

1.
2.
Run the ADD SRCIPRT command to add a policy-based IP route based on the source
IP address. Policy-based IP routes based on the source IP address consist of the policybased IP route based on the IP address of an Ethernet port or link aggregation group,
and the policy-based IP route based on the device IP address. To add more IP routes,
run this command for each IP route.
a.
To add the policy-based IP route based on the IP address of an Ethernet port or

IP address of a link aggregation group, set IP TYPE to ETHIP(ETHIP) or
ETHTRKIP(ETHTRKIP), set Source IP address to the value of Local IP
address in the ADD ETHIP or ADD ETHTRKIP, and set Next Hop
Address to the IP address of the switch or router connected to the in-use port.
b.
To add the policy-based IP route based on the device IP address, set IP TYPE
to DEVIP(DEVIP), set Source IP address to the value of IP address in the
ADD DEVIP. And set Forward route address to an IP address in the same
network segment as Local IP address specified in ADD ETHIP or ADD
ETHTRKIP. When Standby Next hop switch is set to YES(YES), set Standby
Forward route address to the other IP address in the same network segment as
Local IP address specified in ADD ETHIP or ADD ETHTRKIP.
Run the ADD IPPOOLIP command to add an IP address to the transmission resource
pool. In this step, set IP Address in Transmission Resource Pool to the following
value based on network planning.
IP address in the ADD DEVIP.
Local IP address in the ADD ETHTRKIP.
Local IP address in the ADD ETHIP.
----End
Example
BKP DB:;
EXP CFGMML:;
Issue 03 (2015-06-30)

289
RAN17.1
//Querying the attributes of an Ethernet port
//Modifying the attributes of an Ethernet port
MTU=1500;
//Adding an Ethernet trunk link
//Adding a device IP address for the board
ADD DEVIP: SRN=0, SN=14, DEVTYPE=LOGIC_IP, IPADDR="172.173.1.32";
//Add a policy-based route based on the source IP address
ADD SRCIPRT: SRN=0, SN=14, IPTYPE=DEVIP, SRCIPADDR="172.173.1.32",
NEXTHOP="10.10.111.32", STANDBYNEXTHOPSWITCH=NO;
//Adding the local IP address in transmission resource pool
ADD IPPOOLIP: IPPOOLINDEX=0, SRN=0, SN=14, IPADDR="172.173.1.32";
//Removing the IP address of the transmission resource pool
RMV IPPOOLIP: IPPOOLINDEX=0, IPADDR="172.173.1.32";
//Removing the transmission resource pool
RMV IPPOOL: IPPOOLINDEX=0;
//Removing the policy-based route based on the source IP address
RMV SRCIPRT: SRN=0, SN=14, SRCIPADDR="172.173.1.32";
//Removing the device IP address of the board
RMV DEVIP: IPADDR="172.173.1.32";
Follow-up Procedure
l
Verification
1.
2.

3.
Issue 03 (2015-06-30)
290
RAN17.1

4.
5.
6.
Run the DSP ADJNODE command to query the adjacent node status.
Expected result: The adjacent node status is normal.
7.
l
Rollback
1.
Run the RMV IPPOOLIP command to remove the local IP address of the
transmission resource pool added during the capacity expansion.
2.
Run the RMV SRCIPRT command to remove the policy-based route based on the
source IP address.
3.
Run the RMV DEVIP command to remove the device IP address added during the
capacity expansion.
4.
Run the RMV M3LNK command to remove the M3UA link added during the capacity
expansion.
5.
Run the RMV SCTPLNK command to remove the SCTP link added during the
capacity expansion.
6.
Run the RMV ETHTRKLNK command to remove the trunk link added during the
capacity expansion.
7.
configurations.
8.
9.1.2 Iu-PS Interface Capacity Expansion

When the in-use transmission resources over the Iu-PS interface are insufficient due to an
increasing traffic volume, capacity expansion over the Iu-PS interface is required.
9.1.2.1 Iu-PS Interface Capacity Expansion (in ATM Transmission Mode)

This section describes how to expand the capacity over the Iu-PS interface in ATM transmission
mode.
Prerequisites
l
Before the capacity expansion, collect information listed in.

Issue 03 (2015-06-30)
Information
Description
Interface
board physical
information


291
RAN17.1
Information
Description
Data link layer

information
IPOAPVC data planning, including local IP address, peer IP address,

VPI/VCI, and traffic record index, must be complete.
Control plane
information
User plane
information
AAL2 path data planning, including the subrack No., slot No., VPI,
VCI, TX traffic record index, RX traffic record index, and AAL2 path
type, must be complete.
None
License requirement
None
Context
Data Type
MO
Setting Notes
Data Source
MML Command
Physical layer
BRD
Add a board.
Network plan
ADD BRD
Data link layer
OPT
Modify the
attributes of the
optical port.
Network plan
SET OPT
IPOAPVC
Add an
IPOAPVC.
Network plan
ADD IPOAPVC
SAALLNK
Add an SAAL
link.
Network plan
ADD SAALLNK
MTP3LNK
Add an MTP3
link.
Network plan
ADD MTP3LNK
AAL2PATH
Add an AAL2
path.
Network plan
ADD AAL2PATH
Control plane
User plane
Issue 03 (2015-06-30)

292
RAN17.1
Procedure
l

1.
2.
Expand capacity of the physical layer and data link layer.

1.
Run the ADD DEVIP command to add a device IP for IPOAPVC.
2.
Run the ADD IPOAPVC command to add an IPOAPVC. To add more IPOAPVC
links, run this command for each link.

1.
2.

1.
----End
Example
BKP DB:;
EXP CFGMML:;
//Querying the attributes of an optical port
LST OPT: SRN=0, SN=14;
//Setting the attributes of an optical port
SET OPT: SRN=0, SN=14, BT=UOIc, PS=SINGLE, PN=3, SCRAMBLESW=OFF,
WORKTYPE=NNI;
//Adding a device IP for the IPOAPVC
ADD DEVIP: SRN=0, SN=14, DEVTYPE=IPOA_CLIENT_IP, IPADDR="172.23.1.32",
MASK="255.255.255.0";
//Adding an IPOAPVC
ADD IPOAPVC: IPADDR="172.23.1.32", PEERIPADDR="172.23.1.100",
CARRYT=NCOPT, CARRYNCOPTN=3, CARRYVPI=10, CARRYVCI=32, TXTRFX=100,
RXTRFX=100, PEERT=IUPS;
SAALLNKT=NNI;
MTP3";
//Adding an IP path
ADD IPPATH: ANI=0, PATHID=2, ITFT=IUPS, PATHT=QoS, IPADDR="172.23.1.32",
Issue 03 (2015-06-30)

293
RAN17.1

Follow-up Procedure
l
Verification
1.
Run the DSP OPT command to query the optical port status.
Expected result: The optical port status is normal.
2.
3.
4.
5.
6.
l
Rollback
1.
2.
3.
4.
Run the RMV IPOAPVC command to remove an IPOAPVC.
5.
Run the RMV DEVIP command to remove the device IP address of an interface board.
6.
Run the SET OPT to restore the optical port attribute configurations.
7.
9.1.2.2 Iu-PS Interface Capacity Expansion (in IP Transmission Mode)

This section describes how to expand the capacity over the Iu-PS interface in IP transmission
mode.
Prerequisites
l

Issue 03 (2015-06-30)
Informatio
n
Description
Interface
board
physical
information
parameters.

294
RAN17.1
Informatio
n
Description
Data link
layer
information
(IP over E1/
T1)

Data link
layer
information
(IP over FE/
GE)
Control plane
information
User plane
information

None
License requirement
None
Context
Issue 03 (2015-06-30)
Data Type
MO
Setting Notes
Data
Source
MML Command
Physical layer
BRD
Add a board.
Network
plan
ADD BRD
Data link layer (IP

over E1/T1)
E1T1
Modify E1/T1
attributes.
Network
plan
SET E1TI
MPLNK
Add an MLPPP
link.
Network
plan
ADD MPLNK

295
RAN17.1
Data Type
MO
Setting Notes
Data
Source
MML Command
Data link layer (IP

over FE/GE)
ETHPORT
Modify
attributes of the
Ethernet port.
Network
plan
SET ETHPORT
ETHTRKL
NK
Add a link to the

Ethernet trunk.
Network
plan
ADD
ETHTRKLNK
SCTPLNK
Add an SCTP
link.
Network
plan
ADD SCTPLNK
M3LNK
Add an M3UA
link.
Network
plan
ADD M3LNK
IPPATH
Add an IP path.
Network
plan
ADD IPPATH
Control plane
User plane
Procedure
l

1.
2.
and POUc boards.
1.
2.
3.
4.
POUc boards.
1.
Issue 03 (2015-06-30)
2.
3.
296
RAN17.1
1.
2.
3.

1.
2.

1.
----End
Example
BKP DB:;
EXP CFGMML:;
MTU=1500;
Issue 03 (2015-06-30)

297
RAN17.1

//Adding an IP path
ADD IPPATH: ANI=0, PATHID=2, ITFT=IUPS, PATHT=QoS, IPADDR="172.23.1.32",
configurations
MTU=1500;
configurations
Follow-up Procedure
l
Verification
1.
2.
3.
4.

5.
6.
7.
8.

9.
l
Issue 03 (2015-06-30)
Rollback
298
RAN17.1
1.
2.
3.
4.
5.
configurations.
6.
7.
8.
9.1.2.3 Iu-PS Interface Capacity Expansion (IP Pool)

This section describes how to expand the capacity over the Iu-PS interface in IP pool
transmission mode.
Prerequisites
l

Information
Description
Interface
board physical
information

Data link layer

information
Control plane
information
User plane
information

adding a device IP.
Issue 03 (2015-06-30)

299
RAN17.1
None
License requirement
None
Context
Data Type
MO
Setting Notes
Data
Source
MML Command
Physical layer
BRD
Add a board.
Network
plan
ADD BRD
Data link layer
ETHPORT
Modify the
attributes of the
Ethernet port.
Network
plan
SET ETHPORT
ETHTRKL
NK
Add a trunk link.
Network
plan
ADD ETHTRKLNK
DEVIP
Add a device IP
address.
Network
plan
ADD DEVIP
Policybased route
based on
the source
IP address
(SRCIPRT
)
Add a policy-based
route based on the
source IP address.
Network
plan
ADD SRCIPRT
SCTPLNK
Add an SCTP link.
Network
plan
ADD SCTPLNK
M3LNK
Add an M3UA link.
Network
plan
ADD M3LNK
IPPOOLIP
Add the local IP

address in
transmission
resource pool.
Network
plan
ADD IPPOOLIP
Control plane
User plane
Issue 03 (2015-06-30)

300
RAN17.1
Procedure
l

1.
2.
1.
2.
3.
4.
1.
2.
l

1.
2.

1.
2.
Issue 03 (2015-06-30)
a.

b.
301
RAN17.1

----End
Example
BKP DB:;
EXP CFGMML:;
MTU=1500;
Issue 03 (2015-06-30)

302
RAN17.1

Follow-up Procedure
l
Verification
1.
2.

3.
4.
5.
6.
7.
l
Rollback
1.
2.
source IP address.
3.
capacity expansion.
4.
expansion.
5.
capacity expansion.
6.
capacity expansion.
7.
configurations.
8.
9.1.3 Iur Interface Capacity Expansion

When the in-use transmission resources over the Iur interface are insufficient due to an increasing
traffic volume, capacity expansion over the Iur interface is required.
Issue 03 (2015-06-30)

303
RAN17.1
9.1.3.1 Iur Interface Capacity Expansion (in ATM Transmission Mode)

This section describes how to expand the capacity over the Iur interface in ATM transmission
mode.
Prerequisites
l

Information
Description
Interface
board physical
information

Data link layer

information
Negotiation of information about the E1/T1 link, IMA link, IMA group
with the peer end.
NOTE
If only IMA and E1/T1 links are added, all attributes of the newly added E1/T1
links must be consistent with those of the E1/T1 links corresponding to the
Control plane
information
User plane
information
AAL2 path data planning, including the bearing subrack No., bearing
slot No., bearing VPI, bearing VCI, TX traffic record index, RX traffic
record index, and AAL2 path type, must be complete.
None
License requirement
None
Context
Issue 03 (2015-06-30)

304
RAN17.1

Data Type
MO
Setting Notes
Data
Source
MML
Command
Physical layer
configuration
BRD
Add a board.
Network
plan
ADD BRD
Data link layer

configuration
E1T1
Modify attributes
of the E1/T1 link.
Network
plan
SET E1T1
IMALNK
Add an IMA link.
Network
plan
ADD IMALNK
SAALLNK
Add an SAAL
link.
Network
plan
ADD
SAALLNK
MTP3LNK
Add an MTP3
link.
Network
plan
ADD
MTP3LNK
AAL2PATH
Add an AAL2
path.
Network
plan
ADD
AAL2PATH
Control plane
configuration
User plane
configuration
Procedure
l

1.
2.
Expand capacity of the physical layer and data link layer for the newly added AEUa, AOUa,
and AOUc boards.
1.
2.
Run the SET E1T1 command to add an E1/T1 transmission link. To add more E1/T1
3.
4.
5.
Expand capacity of the physical layer and data link layer for the existing AEUa, AOUa,
and AOUc boards.
1.
2.
Issue 03 (2015-06-30)
305
RAN17.1
3.
l
UOIc boards.
1.
2.

1.
2.

1.
----End
Example
BKP DB:;
EXP CFGMML:;
LST E1/T1: SRN=0, SN=14, BT=AOUc;
SAALLNKT=NNI;
MTP3";
CARRYIMAGRPN=9, RSCGRPFLAG=NO, VPI=9, VCI=36, TXTRFX=100, RXTRFX=100,
AAL2PATHT=R99;
Issue 03 (2015-06-30)

306
RAN17.1
//Removing an MTP3 link

RMV MTP3LNK: SIGLKSX=0, SIGSLC=0;
configurations
SET E1T1: SRN=0, SN=14, BT=AOUc, PS=SINGLE, PN=5, PTTYPE=E1_DOUBLE_FRAME,
SCRAMBLESW=OFF, LOOPSW=OFF;
Follow-up Procedure
l
Verification
1.
2.
3.
4.
5.
6.
7.
l
Rollback
1.
2.
3.
4.
5.
6.
9.1.3.2 Iur Interface Capacity Expansion (in IP Transmission Mode)

This section describes how to expand the capacity over the Iur interface in IP transmission mode.
Prerequisites
l
Issue 03 (2015-06-30)

307
RAN17.1

Informatio
n
Description
Interface
board
physical
information
parameters.
Data link
layer
information
(IP over E1/
T1)

Data link
layer
information
(IP over FE/
GE)
Control plane
information
User plane
information

None
License requirement
None
Context
Issue 03 (2015-06-30)
Data Type
MO
Setting Notes
Data
Source
MML Command
Physical layer
BRD
Add a board.
Network
plan
ADD BRD

308
RAN17.1
Data Type
MO
Setting Notes
Data
Source
MML Command
Data link layer (IP

over E1/T1)
E1T1
Modify E1/T1
attributes.
Network
plan
SET E1TI
MPLNK
Add an MLPPP
link.
Network
plan
ADD MPLNK
ETHPORT
Modify
attributes of the
Ethernet port.
Network
plan
SET ETHPORT
ETHTRKL
NK
Add a link to the

Ethernet trunk.
Network
plan
ADD
ETHTRKLNK
SCTPLNK
Add an SCTP
link.
Network
plan
ADD SCTPLNK
M3LNK
Add an M3UA
link.
Network
plan
ADD M3LNK
IPPATH
Add an IP path.
Network
plan
ADD IPPATH
Data link layer (IP

over FE/GE)
Control plane
User plane
Procedure
l

1.
2.
and POUc boards.
1.
2.
3.
4.
POUc boards.
1.
Issue 03 (2015-06-30)

309
RAN17.1
2.
3.
1.
2.
3.

1.
2.

1.
----End
Example
BKP DB:;
EXP CFGMML:;
MTU=1500;
Issue 03 (2015-06-30)

310
RAN17.1

//Adding an IP path
ADD IPPATH: ANI=0, PATHID=2, ITFT=IUR, PATHT=QoS, IPADDR="172.23.1.32",
configurations
MTU=1500;
configurations
Follow-up Procedure
l
Verification
1.
2.
3.
4.

5.
6.
7.
Issue 03 (2015-06-30)
311
RAN17.1

8.

9.
l
Rollback
1.
2.
3.
4.
5.
configurations.
6.
7.
8.
9.1.3.3 Iur Interface Capacity Expansion (IP Pool)

This section describes how to expand the capacity over the Iur interface in IP pool transmission
mode.
Prerequisites
l

Information
Description
Interface
board physical
information

Data link layer

information
Control plane
information
Issue 03 (2015-06-30)

312
RAN17.1
Information
Description
User plane
information

adding a device IP.
None
License requirement
None
Context
Data Type
MO
Setting Notes
Data
Source
MML Command
Physical layer
BRD
Add a board.
Network
plan
ADD BRD
Data link layer
ETHPORT
Modify the
attributes of the
Ethernet port.
Network
plan
SET ETHPORT
ETHTRKL
NK
Add a trunk link.
Network
plan
ADD ETHTRKLNK
DEVIP
Add a device IP
address.
Network
plan
ADD DEVIP
Policybased route
based on
the source
IP address
(SRCIPRT
)
Add a policy-based
route based on the
source IP address.
Network
plan
ADD SRCIPRT
SCTPLNK
Add an SCTP link.
Network
plan
ADD SCTPLNK
Control plane
Issue 03 (2015-06-30)

313
RAN17.1
Data Type
User plane
MO
Setting Notes
Data
Source
MML Command
M3LNK
Add an M3UA link.
Network
plan
ADD M3LNK
IPPOOLIP
Add the local IP

address in
transmission
resource pool.
Network
plan
ADD IPPOOLIP
Procedure
l

1.
2.
1.
2.
3.
4.
1.
2.
l

1.
2.

1.
a.
Issue 03 (2015-06-30)

314
RAN17.1
b.
2.
----End
Example
BKP DB:;
EXP CFGMML:;
MTU=1500;
Issue 03 (2015-06-30)

315
RAN17.1

Follow-up Procedure
l
Verification
1.
2.

3.
4.
5.
6.
7.
l
Issue 03 (2015-06-30)
Rollback
1.
2.
source IP address.
3.
capacity expansion.
4.
expansion.
5.
capacity expansion.
316
RAN17.1
6.
capacity expansion.
7.
configurations.
8.
9.1.4 Iub Interface Capacity Expansion

When the in-use transmission resources over the Iub interface are insufficient due to an
increasing traffic volume, capacity expansion over the Iub interface is required.
9.1.4.1 Iub Interface Capacity Expansion (in ATM Transmission Mode)

This section describes how to expand the capacity over the Iub interface in ATM transmission
mode.
Prerequisites
l

Information
Description
Interface board
physical
information

Data link layer

information
Negotiation of information about the E1/T1 link, IMA link, IMA

NOTE
If only IMA and E1/T1 links are added, all attributes of the newly added E1/
T1 links must be consistent with those of the E1/T1 links corresponding to the
Control plane
information
User plane
information
AAL2 path data planning, including the subrack No., slot No., VPI,
VCI, TX traffic record index, RX traffic record index, and AAL2 path
type, must be complete.
None
License requirement
None
Issue 03 (2015-06-30)

317
RAN17.1
Context
Data Type
MO
Setting Notes
Data
Source
MML
Command
Physical layer
BRD
Add a board.
Network
plan
ADD BRD
Data link layer
E1T1
Modify attributes
of an E1/T1 link.
Network
plan
SET E1T1
IMALNK
Add an IMA link.
Network
plan
ADD IMALNK
Control plane
SAALLNK
Add an SAAL
link.
Network
plan
ADD
SAALLNK
User plane
AAL2PATH
Add an AAL2
path.
Network
plan
ADD
AAL2PATH
Procedure
l

1.
2.
Expand capacity of the physical layer and data link layer for the newly added AEUa, AOUa
and AOUc boards.
1.
2.
Run the SET E1T1 command to add an E1/T1 link. To add more E1/T1 links, run
this command for each E1/T1 link.
3.
4.
5.
Expand capacity of the physical layer and data link layer for the existing AEUa, AOUa and
AOUc boards.
1.
Issue 03 (2015-06-30)

318
RAN17.1
2.
3.
UOIc boards.
1.
2.

1.
type to UNI. To add more SAAL links, run this command for each SAAL link.
2.
Run the ADD UCCP command to add an CCP link. In this step, set Bearing Link
Type to SAAL. To add more CCP links, run this command for each CCP link.

1.
----End
Example
BKP DB:;
EXP CFGMML:;
LST E1T1: SRN=0, SN=14, BT=AOUc;
SAALLNKT=UNI;
//Adding a CCP link
ADD UCCP: IDTYPE=BYNAME, NODEBNAME="NodeB1", PN=1, CARRYLNKT=SAAL,
SAALLNKN=1;
CARRYIMAGRPN=0, VPI=9, VCI=36, TXTRFX=100, RXTRFX=100, AAL2PATHT=R99;;
Issue 03 (2015-06-30)

319
RAN17.1
//Removing a CCP link
RMV UCCP: IDTYPE=BYNAME, NodeBName="NodeB1", PN=1;
configurations
SET E1T1: SRN=0, SN=14, BT=AOUc, PS=SINGLE, PN=5, SCRAMBLESW=OFF,
LOOPSW=OFF, PTTYPE=E1_DOUBLE_FRAME;
Follow-up Procedure
l
Verification
1.
2.
3.
4.
5.
l
Rollback
1.
2.
Run the RMV UCCP command to remove a CCP link.
3.
4.
5.
6.
9.1.4.2 Iub Interface Capacity Expansion (in IP Transmission Mode)

This section describes how to expand the capacity over the Iub interface in IP transmission mode.
Prerequisites
l
Issue 03 (2015-06-30)

320
RAN17.1
Informatio
n
Description
Interface
board
physical
information
parameters.
Data link
layer
information
(IP over E1/
T1)

Data link
layer
information
(IP over FE/
GE)
Control plane
information
User plane
information

None
License requirement
None
Context
Issue 03 (2015-06-30)
Data Type
MO
Setting Notes
Data
Source
MML Command
Physical layer
BRD
Add a board.
Network
plan
ADD BRD

321
RAN17.1
Data Type
MO
Setting Notes
Data
Source
MML Command
Data link layer

information (IP
over E1/T1)
E1T1
Modify
attributes of an
E1/T1 link.
Network
plan
SET E1TI
MPLNK
Add an MLPPP
link.
Network
plan
ADD MPLNK
ETHPORT
Modify the
attributes of an
Ethernet port.
Network
plan
SET ETHPORT
ETHTRKL
NK
Add a trunk link. Network

plan
ADD
ETHTRKLNK
Control plane
SCTPLNK
Add an SCTP
link.
Network
plan
ADD SCTPLNK
User plane
IPPATH
Add an IP path.
Network
plan
ADD IPPATH
Data link layer

information (IP
over FE/GE)
Procedure
l

1.
2.
and POUc boards.
1.
2.
Run the SET E1TI command to add an E1/T1 transmission link. To add more E1/T1
3.
Optional: If the interface board is an optical interface board, such as POUa or POUc,
4.
POUc boards.
1.
Run the LST E1TI command to query the attributes of configured E1/T1 links.
2.
Issue 03 (2015-06-30)
322
RAN17.1
3.
l
1.
2.
3.

1.
type to NBAP. To add more SCTP links, run this command for each SCTP link.
2.
Run the ADD UCCP command to add a CCP link. In this step, set Bearing Link
Type to SCTP. To add more CCP links, run this command for each CCP link.

1.
----End
Example
BKP DB:;
EXP CFGMML:;
//(IP over E1/T1) Adding an MLPPP link
1-1&TS12-1&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1
&TS22-1&TS23-1&TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1;
MTU=1500;
//(IP over FE/GE) Adding an Ethernet trunk link
Issue 03 (2015-06-30)

323
RAN17.1

ADD SCTPLNK: APP=NBAP, SCTPLNKID=0, MODE=SERVER, LOCIP1="172.23.1.32",
//Adding a CCP link
ADD UCCP: IDTYPE=BYNAME, NodeBName="NodeB1", PN=1, CARRYLNKT=SCTP,
SCTPLNKID=1;
ADD M3LNK: SIGLKSX=0, SIGLNKID=4, SRN=0, SN=16, SCTPLNKID=0, NAME="for
M3UA";
//Adding an IP path
ADD IPPATH: ANI=0, PATHID=2, ITFT=IUB, TRANST=IP, PATHT=AF11,
IPADDR="172.23.1.32", PEERIPADDR="172.23.1.100", TXBW=10000, RXBW=10000,
CARRYFLAG=NULL, VLANFlAG=DISABLE, PATHCHK=DISABLED;
//Removing a CCP link
RMV UCCP: IDTYPE=BYNAME, NodeBName="NodeB1", PN=1;
//Removing an Ethernet trunk link
configurations
MTU=1500;
configurations
Follow-up Procedure
l
Verification
1.
2.
3.
4.

5.
6.

Issue 03 (2015-06-30)

324
RAN17.1
7.
l
Rollback
1.
2.
3.
4.
5.
configurations.
6.
7.
8.
9.1.4.3 Iub Interface Capacity Expansion (IP Pool)

This section describes how to expand the capacity over the Iub interface in IP pool transmission
mode.
Prerequisites
l

Information
Description
Interface board
physical
information

Data link layer

information
Control plane
information
User plane
information


adding a device IP.
Issue 03 (2015-06-30)

325
RAN17.1
None
License requirement
None
Context
Data Type
MO
Setting Notes
Data Source
MML
Command
Physical layer
BRD
Add a board.
Network plan
ADD BRD
Data link layer
ETHPORT
Modify the attributes of

an Ethernet port.
Network plan
SET
ETHPORT
ETHTRK
LNK
Add an Ethernet trunk

link.
Network plan
ADD
ETHTRKLN
K
DEVIP
Add a device IP address.
Network plan
ADD DEVIP
SRCIPRT
Add a policy-based
route based on the
source IP address.
Network plan
ADD
SRCIPRT
Control plane
SCTPLNK
Add an SCTP link.
Network plan
ADD
SCTPLNK
User plane
IPPOOLIP
Add the local IP address

in transmission resource
pool.
Network plan
ADD
IPPOOLIP
Procedure
l
Issue 03 (2015-06-30)

1.
2.
1.
2.
3.
326
RAN17.1
4.
l
1.
2.
l

1.
2.
Run the ADD UCCP command to add a CCP link. In this step, set Bearing Link
Type to SCTP. To add more CCP links, run this command for each CCP link.

1.
2.
a.

b.
----End
Example
BKP DB:;
Issue 03 (2015-06-30)

327
RAN17.1

EXP CFGMML:;
MTU=1500;
Follow-up Procedure
l
Verification
1.
Run the DSP ETHTRKLNK command to query the status of the Ethernet trunk link.
Issue 03 (2015-06-30)

328
RAN17.1
2.

3.
4.
5.
l
Rollback
1.
2.
Run the RMV IPPOOLIP command to remove the policy-based route based on the
source IP address.
3.
capacity expansion.
4.
5.
capacity expansion.
6.
capacity expansion.
7.
configurations.
8.
9.2 Reconfiguring the Transmission Mode and the

Networking Mode
This section describes how to reconfigure the transmission mode and networking mode.
9.2.1 Reconfiguring the Transmission Mode

This chapter describes how to reconfigure the transmission mode on the Iu-CS, Iu-PS, Iub, and
Iur interfaces to optimize network performance.
Context
Information described in this section will be included in the subsequent professional service for
project delivery.
9.2.1.1 Changing the Transmission Mode over the Iub Interface from ATM to IP
This section describes how to change the transmission mode over the Iub interface from ATM
to IP by running an MML command.
Issue 03 (2015-06-30)

329
RAN17.1
Prerequisites
l
Network planning has been complete.

Network planning is performed to plan the type, quantity, and backup mode of an interface
board, as well as the interface IP (ETHIP and TRUNKIP), user plane IP, and control plane
IP. To obtain the detailed network planning scheme, contact Huawei technical support.
The IP-based network is available.
The IP interface board has been configured and properly connected to the transmission
equipment.
The license controlling Iub over IP transmission has been activated.
Context
NOTICE
Changing the transmission mode over the Iub interface interrupts BSC6900 services. Therefore,
perform this operation when the traffic is light, for example, during early morning hours.
The transmission mode over the Iub interface can be changed from ATM to IP in batches on the
CME. Therefore, you are advised to perform this operation using the CME.
Procedure
l
On the RNC side

1.
Remove the configuration data in Iub over ATM mode.

a.
b.
Issue 03 (2015-06-30)
Remove configuration data related to the user plane and transport resource
management (TRM) over the Iub interface.
a.
Run the RMV AAL2PATH command to remove an AAL2 path. To remove

more AAL2 paths, run this command for each AAL2 path.
b.
Optional: (Optional) If an adjacent node mapping has been configured, run

the RMV ADJMAP command to remove the TRM mapping corresponding
to the adjacent node.
c.
If all NodeBs in Iub over ATM mode have been converted to Iub over IP
mode, run the RMV TRMMAP command to remove the TRMMAP items
in Iub over ATM mode.
d.
Run the RMV ADJNODE command to remove the adjacent node over the
Iub interface.
Remove the control plane data over the Iub interface.

a.
Run the RMV UCCP command to remove a communication control port

(CCP) link. To remove more CCP links, run this command for each CCP
link.
b.
Run the RMV UNCP command to remove a NodeB control port (NCP)
link.

330
RAN17.1
c.
c.
Run the RMV SAALLNK command to remove an SAAL link over the Iub
interface. To remove all SAAL links used by the adjacent node, UCCP, and
UNCP, run this command for each SAAL link.
Remove the configuration data of the operation and maintenance channel over
the Iub interface.
a.
Run the RMV IPRT command to remove the IP route configuration data
of the operation and maintenance channel over the Iub interface.
b.
Run the RMV UNODEBIP command to remove the configuration data

related to the IP address of the operation and maintenance channel for the
NodeB.
c.
Run the RMV IPOAPVC command to remove an IPoA PVC for the
operation and maintenance of the NodeB.
d.
After the last NodeB connected to the ATM interface board is removed, run
the RMV DEVIP command to remove the device IP address of this board.
d.
Optional: If an ATM logical port is configured, run the RMV

ATMLOGICPORT command to remove this port.
e.
Run the RMV ATMTRF command to remove an ATM traffic record.
f.
Optional: If the interface board is not a UOIa or UOIc, remove the configuration
data on the ATM link layer.
For a UNI link, run the RMV UNILNK command to remove the UNI link.
For an IMA group:
a.
Run the RMV IMALNK command to remove an IMA link. To remove

more IMA links, run this command for each IMA link.
b.
Run the RMV IMAGRP command to remove an IMA group.
For a fractional ATM link, run the RMV FRALNK command to remove the
fractional ATM link.
For a fractional IMA group:
2.
Run the RMV FRALNK command to remove a fractional IMA link.

To remove more fractional IMA links, run this command for each
fractional IMA link.
b.
g.
Optional: If a timeslot cross connection is configured, run the RMV

TSCROSS command to remove it.
h.
Run the RMV BRD command to remove an ATM interface board.
Configure IP transmission data over the Iub interface as follows:

a.
Configure the physical layer and data link layer.
b.
Configure the control plane over the Iub interface.
c.
Configure the user plane over the Iub interface.
d.
Configure the mapping between service types and transmission resources.
e.
Configure the OM channel over the Iub interface.
On the NodeB side

1.
Issue 03 (2015-06-30)
a.
Remove the ATM configuration data on the Iub interface.

331
RAN17.1
a.
b.
c.
Remove the configuration data related to the user plane and transmission resource
management on the Iub interface.
a.
Run the MML command RMV AAL2PATH to remove an ATM Adaption

Layer Type 2 (AAL2) path. To remove more AAL2 paths, run this command
for each AAL2 path you want to remove.
b.
Run the MML command RMV AAL2NODE to remove an Iub-interface

node.
Remove the Iub-interface control-plane configuration data.

a.
Run the MML command RMV IUBCP, set Port Type to CCP(CCP
Port) to remove a communication control port (CCP) link. To remove more
CCP links, run this command for each CCP link you want to remove.
b.
Run the MML command RMV IUBCP, set Port Type to NCP(NCP
Port) to remove a network control protocol (NCP) link.
c.
Run the MML command RMV CPBEARER to remove the used control
port bearer.
d.
Run the MML command RMV SAALLNK to remove a Signaling ATM

Adaptation Layer (SAAL) link on the Iub interface. Run this command
repeatedly to remove all the SAAL links used for the adjacent node, CCP,
and NCP.
Optional: Remove the configuration data of the ATM links.

For the user-to-network interface (UNI) link, run the MML command RMV
UNILNK to remove an UNI link.
For the inverse multiplexing over ATM (IMA) group, run the MML command
RMV IMAGRP to remove an IMA group.
For the Fractional ATM link, run the MML command RMV FRALNK to
remove a Fractional ATM link.
2.
Configure the Physical Layer and Data Link Layer.

a.
Optional: For the FE/GE port, run the MML command SET ETHPORT to
configure the Ethernet port.
b.
Optional: Run the MML command ADD PPPLNK to add a Point-to-Point

Protocol (PPP) link.
c.
Optional: Configure an MP group.
d.
Issue 03 (2015-06-30)
a.
Run the MML command ADD MPGRP to add a Multilink Protocol (MP)
group.
b.
Run the MML command ADD MPLNK to add an MP link. Run this
command for each MP link to be added.
Optional: Configure the Ethernet link aggregation group only on the UTRP2,
UTRP9, or UTRPc.
a.
Run the MML command ADD ETHTRK to add an Ethernet link

aggregation group.
b.
Run the MML command ADD ETHTRKLNK to add a member port for
an Ethernet link aggregation group. Run this command for each member
port to be added.

332
RAN17.1
e.
Run the MML command ADD DEVIP to add a device IP address. Run this
command for each device IP address to be added.
f.
Optional: If VLAN networking is used, configure VLAN data based on the

VLAN plan.
a.
Run the MML command ADD VLANMAP to add a mapping from a nexthop IP address to a VLAN.
b.
Optional: If Set VLAN Priority in the ADD VLANMAP command is set

to DISABLE(Disable) and the default mapping relationship is not used,
run the SET DSCPMAP command to set the mapping between DSCPs and
VLAN priorities.
3.
Run the MML command MOD OMCH to modify the configuration data of the
operation and maintenance channel (OMCH) on the Iub interface. This operation
interrupts the OMCH. Therefore, during the operation, ensure that the IP channels are
physically connected and OMCH data is correctly configured.
4.
Configure Iub-interface control-plane data.
5.
a.
Run the MML command ADD SCTPLNK to add an SCTP link. To add more
SCTP links, run this command for each SCTP link to be added.
b.
Run the MML command ADD CPBEARER to set Bear Type to SCTP, set
Link No. to the value configured in 4.1.
c.
Run the MML command ADD IUBCP to add an NCP link. Set Port Type to
NCP(NCP Port) and set CP Bear No. to the value configured in 4.2.
d.
Run the MML command ADD IUBCP to add a CCP link. Set Port Type to
CCP(CCP Port) and set CP Bear No. to the value configured in 4.2. To add
more CCP links, run this command for each CCP link to be added.
Configure Iub-interface user-plane data.

a.
Run the MML command ADD IPPATH to add an IP path. The settings of
DSCP must be consistent with those on the RNC. To add more IP paths, run this
command for each IP path to be added.
b.
Optional: When the NodeB and RNC/U2000 are deployed on a layer 3 network,
configure IP routes based on the planned routing policy:
If the destination IP address-based routing policy will be used according to
the networking plan, run the MML command ADD IPRT to respectively
configure a route from the NodeB to the RNC and a route from the NodeB to
the U2000. Run this command for each IP route to be added.
If the source IP address-based routing policy will be used according to the
networking plan, run the MML command ADD SRCIPRT to configure
routes for the OM IP address and UMTS service (signaling) source IP address.
Run this command for each IP route to be added.
----End
9.2.1.2 Changing the Transmission Mode over the Iub Interface from ATM to IP
Pool
This section describes how to change the transmission mode over the Iub interface from ATM
to IP pool by running an MML command on the RNC side.
Issue 03 (2015-06-30)

333
RAN17.1
Prerequisites
l

Network planning is performed to plan the type, quantity, and backup mode of an interface
board, as well as the interface IP (ETHIP and TRUNKIP), user plane IP, and control plane
IP. To obtain the detailed network planning scheme, contact Huawei technical support.
The IP-based network is available.
The IP interface board has been configured and properly connected to the transmission
equipment.
None
License requirement
The license controlling Iub over IP pool transmission has been activated.
Context
NOTICE
Changing the transmission mode over the Iub interface interrupts BSC6900 services. Therefore,
perform this operation when the traffic is light, for example, during early morning hours.
Procedure
l
On the RNC side

1.
Remove the configuration data in Iub over ATM mode.

a.
b.
Issue 03 (2015-06-30)
Remove configuration data related to the user plane and transport resource
management (TRM) over the Iub interface.
a.
Run the RMV AAL2PATH command to remove an AAL2 path. To remove

more AAL2 paths, run this command for each AAL2 path.
b.
Optional: If an adjacent node mapping has been configured, run the RMV
ADJMAP command to remove the TRM mapping corresponding to the
adjacent node.
c.
If all NodeBs in Iub over ATM mode have been converted to Iub over IP
mode, run the RMV TRMMAP command to remove the TRMMAP items
in Iub over ATM mode.
d.
Run the RMV ADJNODE command to remove the adjacent node over the
Iub interface.

a.
Run the RMV UCCP command to remove a communication control port

(CCP) link. To remove more CCP links, run this command for each CCP
link.
b.
Run the RMV UNCP to remove a NodeB control port (NCP) link.

334
RAN17.1
c.
c.
Run the RMV SAALLNK command to remove an SAAL link over the Iub
interface. To remove all SAAL links used by the adjacent node, UCCP, and
UNCP, run this command for each SAAL link.
Remove the configuration data of the operation and maintenance channel over
the Iub interface.
a.
Run the RMV IPRT command to remove the IP route configuration data
of the operation and maintenance channel over the Iub interface.
b.
Run the RMV UNODEBIP command to remove the configuration data

related to the IP address of the operation and maintenance channel for the
NodeB.
c.
Run the RMV IPOAPVC command to remove an IPoA PVC for the
operation and maintenance of the NodeB.
d.
After the last NodeB connected to the ATM interface board is removed, run
the RMV DEVIP command to remove the device IP address of this board.
d.
Optional: If an ATM logical port is configured, run the RMV

ATMLOGICPORT command to remove this port.
e.
Run the RMV ATMTRF command to remove an ATM traffic record.
f.
Optional: If the interface board is not a UOIa or UOIc, remove the data on the
ATM link layer.
For a UNI link, run the RMV UNILNK command to remove the UNI link.
For an IMA group:
a.
Run the RMV IMALNK command to remove an IMA link. To remove

more IMA links, run this command for each IMA link.
b.
Run the RMV FRALNK to command remove a fractional ATM link.
2.
g.
Optional: If a timeslot cross connection is configured, run the RMV

TSCROSS command to remove it.
h.
Run the RMV BRD command to remove an ATM interface board.
Configure IP pool transmission data over the Iub interface as follows:

a.
Configure physical layer and data link layer for FG2c/GOUc/GOUe.
b.
Configure the transmission resource pool.
c.
Configure the control plane over the Iub interface.
d.
Configure the user plane over the Iub interface.
e.
Configure the mapping between service types and transmission resources.
f.
Configure the OM channel over the Iub interface.
On the NodeB side

1.
Remove the ATM configuration data on the Iub interface.

a.
management on the Iub interface.
a.
Issue 03 (2015-06-30)


335
RAN17.1
b.
b.
c.

node.
Remove the Iub-interface control-plane configuration data.

a.
Run the MML command RMV IUBCP, set Port Type to CCP(CCP
Port) to remove a communication control port (CCP) link. To remove more
CCP links, run this command for each CCP link you want to remove.
b.
Run the MML command RMV IUBCP, set Port Type to NCP(NCP
Port) to remove a network control protocol (NCP) link.
c.
Run the MML command RMV CPBEARER to remove the used control
port bearer.
d.

repeatedly to remove all the SAAL links used for the adjacent node, CCP,
and NCP.
Optional: Remove the configuration data of the ATM links.

For the Fractional ATM link, run the MML command RMV FRALNK to
remove a Fractional ATM link.
2.
Configure the Physical Layer: run the MML command ADD ETHPORT to add an
Ethernet port and set its parameters, such as the speed, duplex mode, and port attribute.
3.
Optional: Configure the Data link layer: If VLAN networking is used, configure
VLAN data based on the VLAN plan.
If VLAN networking is based on the next-hop IP address, perform the following
steps:
a.
Run the MML command ADD VLANMAP to add an entry of mapping from
the next-hop IP address to a single VLAN. In this step, set VLAN Mode to
SINGLEVLAN(Single VLAN) (recommended), and set Set VLAN
Priority to DISABLE(Disable) (recommended) to use the default mapping
relationship or run the MML command SET DSCPMAP to set the mapping
between DSCPs and VLAN priorities. If Set VLAN Priority is set to
ENABLE(Enable), you need to set the VLAN Priority parameter.
b.
Optional: If Set VLAN Priority in the MML command ADD

VLANMAP is set to DISABLE(Disable) and the default mapping
relationship is not used, run the MML command SET DSCPMAP to set the
mapping between DSCPs and VLAN priorities.
If VLAN networking is based on the source IP address, run the MML command
ADD SUBNETVLAN to add an entry of mapping between a source IP address
and a VLAN.
4.
Configure the Transmission layer:

a.
Run the MML command ADD DEVIP to add a device IP address.

If the device IP address is set to a logical IP address, the device IP address must
be on a different network segment from the port IP address. In addition, a route
Issue 03 (2015-06-30)

336
RAN17.1
must be configured from the logical IP address to an external device (such as the
router connected to the base station).
b.
Configure IP routes based on the planned routing policy:

the networking plan, run the MML command ADD IPRT commands to
respectively configure a route from the NodeB to the RNC and a route from
the NodeB to the U2000.
routes to source IP addresses of the OM channel, signaling link, and service
link.
c.
Issue 03 (2015-06-30)
Optional: If RAN Sharing, common transmission, or base station cascading is

used, you are advised to perform the following steps:
a.
Run the MML command ADD RSCGRP to add a transmission resource

group.
b.
Run the MML command SET RSCGRPALG to set algorithm parameters

for a transmission resource group.
d.
Run the MML command ADD SCTPLNK to add an SCTP link.
e.
Run the MML command ADD CPBEARER to add a CP bearer. In this step, set
Bear Type to SCTP(SCTPLNK).
f.
Run the MML command ADD USERPLANEHOST to add a user-plane host.
g.
Optional: Run the MML command ADD USERPLANEPEER to add a userplane peer. If you do not run this command to manually add a user-plane peer,
such a user-plane peer will be automatically created.
h.
Run the MML command ADD EPGROUP to add an end point group. In
addition, you need to perform the following steps:
a.
Run the MML command ADD UPHOST2EPGRP to add user-plane hosts

to the end point group.
b.
Optional: If a user-plane peer has been configured, run the MML command
ADD UPPEER2EPGRP to add user-plane peer to an end point group.
i.
Optional: After transmission resource groups are configured, run the MML
command ADD EP2RSCGRP to add the mapping between an end point and a
transmission resource group.
j.
Optional: Run the MML command SET DIFPRI to set the mapping from traffic
types to priorities.
5.
Configure the Maintenance channel: run the MML command ADD OMCH to add a
remote maintenance channel. In this step, set Bearer Type to IPV4. The peer IP
address specified in this step must be different from the IP address added by using the
ADD DEVIP command.
6.
Optional: Configure the DHCP: if base stations are cascaded, perform the following
steps:
a.
Run the MML command ADD DHCPSVRIP to add the IP address of a DHCP
server.
b.
Run the MML command SET DHCPRELAYSWITCH to set a Dynamic Host

Configuration Protocol (DHCP) relay switch.
337
RAN17.1
7.
Configure the Interface data:

a.
Run the MML command ADD IUB to add transmission resources over the Iub
interface.
b.
Run the MML command ADD IUBCP to respectively add a NodeB control port
(NCP) and a communication control port (CCP).
----End
Follow-up Procedure
l
Verification
1.
Rollback
1.
Remove the IP pool networking mode on the Iub interface.

a.
Remove the mapping between service types and transmission resources for the
adjacent node.
Run the RMV ADJMAP command to remove a transport resource
management (TRM) mapping from an adjacent node.
Run the RMV TRMFACTOR command to remove an activity factor table.
Run the RMV TRMMAP command to remove the mapping between
transmission resources and services.
b.
Remove the user plane configuration data on the Iub interface (IP Pool).
Run the RMV ADJNODE command to remove a transport adjacent node.
c.
Remove the control-plane configuration data on the Iub interface.

Run the RMV UNCP command to remove an NCP link.
Run the MML command RMV SCTPLNK to remove an SCTP link.
d.
e.
Remove a transmission resource pool.

a.
Run the RMV IPPOOLIP command to remove an IP address from a

transmission resource pool.
b.
Run the RMV IPPOOL command to remove a transmission resource pool.
c.
Run the RMV SRCIPRT command to remove a policy-based route based

on the source IP address.
Remove data from the physical layer and data link layer.
a.
If the logical IP networking is used, run the RMV DEVIP command to

remove a device IP address.
b.
Optional: If VLANs are configured, run the RMV VLANID command to

remove the IP-to-VLAN ID mapping table.
c.
If link aggregation is used, perform the following operations:

Run the RMV ETHTRKIP command to remove the IP address of the
trunk group.
Run the RMV ETHTRKLNK command to remove a link from the
trunk group.
Issue 03 (2015-06-30)

338
RAN17.1
Run the RMV ETHTRK command to remove a trunk group.

d.
If non-link aggregation is used, perform the following operations:

Run the RMV ETHIP command to remove the IP address of an Ethernet
port.
Optional: If active and standby Ethernet ports are used, run the RMV
ETHREDPORT command to remove the active and standby Ethernet
ports.
2.
Configure the ATM networking mode on the Iub interface by referring to the following
operations:
a.
Configure physical layer data (in ATM mode) by referring to the procedure in
Configuring Physical-Layer Data (in ATM Mode) in Initial Configuration
Guide.
b.
Configure ATM traffic resources by referring to the procedure in Configuring

ATM Traffic Resources in Initial Configuration Guide.
c.
Configure control-plane data over the Iub interface (in ATM mode) by referring
to the procedure in Configuring Control-Plane Data over the Iub Interface (in
ATM Mode) in Initial Configuration Guide.
d.
Configure the user plane over the Iub interface (in ATM mode) by referring to
the procedure in Configuring the User Plane of the Iub Interface (over ATM) in
Initial Configuration Guide.
e.
Configure the mapping between service types and transmission resources for an
adjacent node by referring to the procedure in Configuring the Mapping Between
Service Types and Transmission Resources for an Adjacent Node in Initial
Configuration Guide.
f.
Configure the OM channel over the Iub interface (in ATM mode) by referring
to the procedure in Configuring the O&M Channel over the Iub Interface (in
ATM Mode) in Initial Configuration Guide.
9.2.1.3 Changing the Transmission Mode over the Iub Interface from ATM/IP Dual
Stack to IP Pool
To improve the reliability over the Iub interface, you can change the transmission mode over
the Iub interface from ATM/IP dual stack to IP pool.
Prerequisites
l

Network planning is performed to plan the data throughput in IP pool transmission mode,
the interface board type, quantity, and backup mode, the Ethernet IP or trunk IP, and
whether the interface board is configured with active/standby gateway and VLAN.
Contact Huawei technical support to obtain the detailed network design scheme.
The FG2c/GOUc/GOUe board has been configured.
The license controlling transmission resource pool over the Iub interface has been activated.
Issue 03 (2015-06-30)

339
RAN17.1
Context
NOTICE
1. Changing the transmission mode over the Iub interface to IP pool interrupts BSC6900
services. Therefore, perform this operation when the traffic is light, for example, during early
morning hours.
2. You are advised to make configuration scripts in advance before reconfiguration and use the
batch configuration to shorten the service interruption duration.
The BSC transmission resource pool is also called IP pool.
Only the FG2c/GOUc/GOUe board supports IP pool transmission mode.
The IP pool transmission mode over the Iub interface means that multiple interface boards form
a resource pool and this pool is connected to NodeBs, as shown in Figure 9-1. The IP pool
transmission mode has the following advantages
l
Increases board and port utilization.
Simplifies the transmission capacity expansion for the BSC6900. When adding
transmission ports and boards, you do not need to reparent NodeBs.
Implements automatic load balancing. You do not need to reparent NodeBs to balance the
load among Iub interface boards.
Figure 9-1 IP pool transmission
This figure provides only the information about the IP transport network.
This task only reconfigures the IP transmission data on the user plane over the Iub interface.
Procedure
l
On the RNC side

1.
Remove the Iub configuration data.

If the user plane over the Iub interface uses IP transmission, remove the IP transmission
data on the user plane.
Issue 03 (2015-06-30)

340
RAN17.1
a.
Run the DEA UCELL to deactivate all cells.
b.
Optional: If the layer 3 networking is used between the BSC6900 and NodeB,
run the RMV IPRT command to remove the IP route on the Iub user plane.
c.
If the Iub control plane uses ATM transmission, you do not need to reconfigure the
transmission data on the Iub control plane, and the Iub interface still uses ATM
transmission.
If the control plane over the Iub interface uses IP transmission, remove the IP
transmission data on the Iub control plane.
a.
b.
Run the RMV UNCP command to remove a NodeB control port (NCP) link.
c.
Run the RMV ADJNODE command to remove basic information about the
adjacent node.
d.
Optional: If the layer 3 networking is used between the BSC6900 and NodeB,
run the RMV IPRT command to remove the IP route on the Iub control plane.
e.
Run the RMV SCTPLNK command to remove an SCTP link over the Iub
interface.
a.
Remove the physical layer and data link layer.

a.
2.
1)
Run the RMV ETHTRKIP command to remove the trunk IP address.
2)
Run the RMV ETHTRKLNK command to remove a link in the trunk.
3)
Run the RMV ETHTRK command to remove a trunk.
b.
Optional: If VLANs are configured for the BSC6900, run the RMV
VLANID to delete the mapping between IP addresses and VLAN IDs.
c.
If non-link aggregation is used, run the RMV ETHIP command to remove

the IP address of the Ethernet port.
d.
Optional: Run the RMV DEVIP command to remove the device IP address
of a board.
e.
Optional: Run the RMV ETHREDPORT command to remove the active

and standby Ethernet ports.
Configure ATM/IP dual stack over the Iub interface (IP pool).
a.
b.
Configure physical layer and data link layer by referring to the procedure in
Configuring Physical-Layer and Data-Link-Layer Data for the FG2c/GOUc/
GOUe in Initial Configuration Guide.
c.
Configure the transmission resource pool by referring to the procedure in

Configuring the Route in Initial Configuration Guide.
d.
Configure the Iub control plane (IP pool).

a.
Issue 03 (2015-06-30)
Run the ADD SCTPLNK command to add an SCTP link. To add more
SCTP links, perform this step for each SCTP link. In this step, set the
parameters as follows:

341
RAN17.1
The SCTP link must be configured to work in dual-homed mode on the

BSC6900. That is, configure two local IP addresses and two peer IP
addresses for the SCTP link.
b.
Run the ADD UNCP command to add a NodeB control port (NCP).
c.
Run the ADD UCCP command to add a NodeB communication control

port (CCP) link. To add more CCP links, perform this step for a CCP link.
e.
Configure the user plane over the Iub interface (in transmission resource pool)
by referring to the procedure in Configuring the User Plane of the Iub Interface
(in Transmission Resource Pool Mode) in Initial Configuration Guide.
f.
On the NodeB side

1.
Remove the Iub-interface configuration data.

Remove the configuration data related to IP transmission in the user plane on the
Iub interface.
a.
Optional: When the NodeB and RNC are deployed on a layer 3 network, run
the MML command RMV IPRT to remove the IP route in the user plane on
the Iub interface.
b.
Run the MML command RMV IPPATH to remove an IP path.
Remove the configuration data related to ATM transmission in the user plane on
the Iub interface.
2.
3.
a.

b.

node.
If ATM transmission is used in the control plane on the Iub interface, remove the
configuration data related to ATM transmission in the control plane on the Iub
interface.
a.
Run the MML command RMV IUBCP, set Port Type to CCP(CCP Port) to
remove a communication control port (CCP) link. To remove more CCP links,
run this command for each CCP link you want to remove.
b.
Run the MML command RMV IUBCP, set Port Type to NCP(NCP Port) to
remove a network control protocol (NCP) link.
c.
Run the MML command RMV CPBEARER to remove the used control port
bearer.
d.

repeatedly to remove all the SAAL links used for the adjacent node, CCP, and
NCP.
Remove the configuration data of the ATM links.

Issue 03 (2015-06-30)

342
RAN17.1
For the Fractional ATM link, run the MML command RMV FRALNK to remove
a Fractional ATM link.
4.
Configure the Physical Layer: run the MML command ADD ETHPORT to add an
Ethernet port and set its parameters, such as the speed, duplex mode, and port attribute.
5.
Optional: Configure the Data link layer: If VLAN networking is used, configure
VLAN data based on the VLAN plan.
If VLAN networking is based on the next-hop IP address, perform the following
steps:
a.
Run the MML command ADD VLANMAP to add an entry of mapping from
the next-hop IP address to a single VLAN. In this step, set VLAN Mode to
SINGLEVLAN(Single VLAN) (recommended), and set Set VLAN
Priority to DISABLE(Disable) (recommended) to use the default mapping
relationship or run the MML command SET DSCPMAP to set the mapping
between DSCPs and VLAN priorities. If Set VLAN Priority is set to
ENABLE(Enable), you need to set the VLAN Priority parameter.
b.
Optional: If Set VLAN Priority in the MML command ADD

VLANMAP is set to DISABLE(Disable) and the default mapping
relationship is not used, run the MML command SET DSCPMAP to set the
mapping between DSCPs and VLAN priorities.
If VLAN networking is based on the source IP address, run the MML command
ADD SUBNETVLAN to add an entry of mapping between a source IP address
and a VLAN.
6.
Configure the Transmission layer:

a.
Run the MML command ADD DEVIP to add a device IP address.

If the device IP address is set to a logical IP address, the device IP address must
be on a different network segment from the port IP address. In addition, a route
must be configured from the logical IP address to an external device (such as the
router connected to the base station).
b.
Configure IP routes based on the planned routing policy:

the networking plan, run the MML command ADD IPRT commands to
respectively configure a route from the NodeB to the RNC and a route from
the NodeB to the U2000.
routes to source IP addresses of the OM channel, signaling link, and service
link.
c.
Issue 03 (2015-06-30)
Optional: If RAN Sharing, common transmission, or base station cascading is

used, you are advised to perform the following steps:
a.
Run the MML command ADD RSCGRP to add a transmission resource

group.
b.
Run the MML command SET RSCGRPALG to set algorithm parameters

for a transmission resource group.

343
RAN17.1
d.
Run the MML command ADD SCTPLNK to add an SCTP link.
e.
Run the MML command ADD CPBEARER to add a CP bearer. In this step, set
Bear Type to SCTP(SCTPLNK).
f.
g.
Optional: Run the MML command ADD USERPLANEPEER to add a userplane peer. If you do not run this command to manually add a user-plane peer,
such a user-plane peer will be automatically created.
h.
Run the MML command ADD EPGROUP to add an end point group. In
addition, you need to perform the following steps:
a.
Run the MML command ADD UPHOST2EPGRP to add user-plane hosts

to the end point group.
b.
Optional: If a user-plane peer has been configured, run the MML command
ADD UPPEER2EPGRP to add user-plane peer to an end point group.
i.
Optional: After transmission resource groups are configured, run the MML
command ADD EP2RSCGRP to add the mapping between an end point and a
transmission resource group.
j.
Optional: Run the MML command SET DIFPRI to set the mapping from traffic
types to priorities.
7.
Configure the Maintenance channel: run the MML command ADD OMCH to add a
remote maintenance channel. In this step, set Bearer Type to IPV4. The peer IP
address specified in this step must be different from the IP address added by using the
ADD DEVIP command.
8.
Optional: Configure the DHCP: if base stations are cascaded, perform the following
steps:
9.
a.
Run the MML command ADD DHCPSVRIP to add the IP address of a DHCP
server.
b.
Run the MML command SET DHCPRELAYSWITCH to set a Dynamic Host

Configuration Protocol (DHCP) relay switch.
Configure the Interface data:

a.
Run the MML command ADD IUB to add transmission resources over the Iub
interface.
b.
Run the MML command ADD IUBCP to respectively add a NodeB control port
(NCP) and a communication control port (CCP).
----End
Follow-up Procedure
1.
Configure IP transmission equipment and peer equipment based on the network plan. For
details, see the documents delivered with the equipment.
You need to reconfigure the IP addresses and VLANs.
NOTE
Only IP transmission equipment needs to be reconfigured.
2.
Issue 03 (2015-06-30)

344
RAN17.1
9.2.1.4 Changing Networking Mode over the Iub Interface from IP to Transmission
Resource Pool
To improve the reliability over the Iub interface, change the transmission mode over the Iub
interface to IP pool as required.
Prerequisites
l

The transmission equipment has been enabled with dynamic routing protocols.
Alternatively, a static route has been configured from the transmission equipment to the
IP address of the transmission resource pool for the base station controller.
The IP route from the peer NE to the base station controller has been configured.
License requirement
The license controlling transmission resource pool over the Iub interface has been
activated.
Context
NOTICE
morning hours.
The IP pool transmission mode over the Iub interface means that multiple interface boards form
a resource pool and this pool is connected to NodeBs, as shown in Figure 9-2. The IP pool
transmission mode has the following advantages
l
Simplifies the transmission capacity expansion for the BSC6900. When adding
transmission ports and boards, you do not need to reparent NodeBs.
Issue 03 (2015-06-30)

345
RAN17.1
Implements automatic load balancing. You do not need to reparent NodeBs to balance the
load among Iub interface boards.
Figure 9-2 IP pool transmission
Procedure
l
On the RNC side

1.
Remove the Iub configuration data.

a.
b.
c.
Remove the user plane data over the Iub interface.

a.
Run the DEA UCELL to deactivate all cells.
b.
Optional: If the layer 3 networking is used between the BSC6900 and

NodeB, run the RMV IPRT command to remove the IP route on the Iub
user plane.
c.

a.
b.
Run the RMV UNCP command to remove a NodeB control port (NCP)
link.
c.
Run the RMV ADJNODE command to remove basic information about

the adjacent node.
d.
Optional: If the layer 3 networking is used between the BSC6900 and

NodeB, run the RMV IPRT command to remove the IP route on the Iub
control plane.
e.
Run the RMV SCTPLNK command to remove an SCTP link over the Iub
interface.

a.
b.
Issue 03 (2015-06-30)

1)
2)
3)
Optional: If VLANs are configured for the BSC6900, run the RMV
VLANID to delete the mapping between IP addresses and VLAN IDs.

346
RAN17.1
2.
c.
If non-link aggregation is used, run the RMV ETHIP command to remove

the IP address of the Ethernet port.
d.
Optional: Run the RMV DEVIP command to remove the device IP address
of a board.
e.
Optional: Run the RMV ETHREDPORT command to remove the active

Configure the IP pool transmission mode over the Iub interface.

a.
Configure the physical layer and data link layer by referring to the procedure in
Configuring Physical-Layer and Data-Link-Layer Data for the FG2c/GOUc/
GOUe in Initial Configuration Guide.
b.
Configure the transmission resource pool by referring to the procedure in

Configuring the Route in Initial Configuration Guide.
c.
Configure the control plane over the Iub interface in IP pool transmission mode.
a.
Run the ADD SCTPLNK command to add an SCTP link. To add more
SCTP links, perform this step for each SCTP link. In this step, set the
parameters as follows:
The SCTP link must be configured to work in dual-homed mode on the
BSC6900. That is, configure two local IP addresses and two peer IP
addresses for the SCTP link.
Run the ADD UNCP command to add a NodeB control port (NCP).
c.
Run the ADD UCCP command to add a NodeB communication control

port (CCP) link. To add more CCP links, perform this step for a CCP link.
d.
Configure the user plane over the Iub interface (in transmission resource pool)
by referring to the procedure in Configuring the User Plane of the Iub Interface
(in Transmission Resource Pool Mode) in Initial Configuration Guide.
e.
adjacent node by referring to Configuring the Mapping Between Service Types
and Transmission Resources for an Adjacent Node in Initial Configuration
Guide.
On the NodeB side

1.
2.
Issue 03 (2015-06-30)
b.
Remove the configuration data related to IP transmission in the user plane on the Iub
interface.
a.
Optional: When the NodeB and BSC6900/U2000 are deployed on a layer 3

network, run the MML command RMV IPRT to remove the IP route in the user
plane on the Iub interface.
b.
c.
Optional: When NODEBPATH MO are configured, run the MML command

RMV NODEBPATH to cancel NodeB IP PATH.
Configure Iub-interface user-plane data.

a.
Run the MML command ADD EPGROUP to add an end point group.
b.

Run this command for each user-plane IP address to be added.
c.
Run the MML command ADD UPHOST2EPGRP to add a user-plane host to

an end point group. Run this command for each user-plane host to be added.
347
RAN17.1
d.
3.
Run the MML command ADD IUB to add a transmission object on the Iub
interface.
Optional: Modify Iub-interface control-plane data.

a.
Run the MML command MOD SCTPLNK to modify the peer IP address and
the peer SCTP port number of the SCTP link on the Iub interface. Run this
command for each SCTP link to be modified.
b.
Optional: When the NodeB and RNC/U2000 are deployed on a layer 3 network,
configure IP routes based on the planned routing policy:
the networking plan, run the MML command ADD IPRT to respectively
configure a route from the NodeB to the RNC and a route from the NodeB to
the U2000. Run this command for each IP route to be added.
routes for the OM IP address and UMTS service (signaling) source IP address.
Run this command for each IP route to be added.
----End
Follow-up Procedure
l
Verification
1.
Configure transmission equipment and peer equipment based on the network plan.
For details, see the documents delivered with the equipment.
2.
l
Rollback
1.
Remove the IP pool networking mode on the Iub interface.

a.
adjacent node.
Run the RMV TRMFACTOR command to remove an activity factor table.
Run the RMV TRMMAP command to remove the mapping between
transmission resources and services.
b.
Remove the user plane configuration data on the Iub interface (IP Pool).
Run the RMV ADJNODE command to remove an adjacent node.
c.
Remove the control-plane configuration data on the Iub interface.

Run the RMV UNCP command to remove an NCP link.
d.

a.
Issue 03 (2015-06-30)


348
RAN17.1
e.
b.
c.

a.

b.

c.

trunk group.
trunk group.
d.

port.
ports.
2.
Configure the IP networking mode on the Iub interface.

a.
Configure physical layer and data link layer (in IP mode) by referring to the
procedure in Configuring Physical-Layer and Data Link-Layer Data (in IP Mode)
in Initial Configuration Guide.
b.
Configure control plane over the Iub interface (in IP mode) by referring to the
procedure in Configuring Control-Plane Data over the Iub Interface (in IP Mode)
c.
Configure the user plane over the Iub interface (over IP) by referring to the
procedure in Configuring the User Plane of the Iub Interface (over IP) in Initial
d.
e.
Configure the OM channel over the Iub interface (over IP) by referring to the
procedure in Configuring the OM Channel over the Iub Interface (over IP) in
9.2.1.5 Changing Networking Mode over the Iu-CS Interface from IP to

Transmission Resource Pool
This section describes how to configure the IP pool networking mode on the Iu-CS interface to
improve the reliability of the interface.
Issue 03 (2015-06-30)

349
RAN17.1
Prerequisites
l

License requirement
The license controlling the transmission resource pool for the RNC's Iu-CS interface
has been activated.
Context
NOTICE
morning hours.
When the BSC6900 has been connected to the core network (CN) devices of multiple operators
in ATM or IP transmission mode and you want to configure the IP pool networking mode on
the Iu-CS interface, the networking modes of the BSC6900 and the CN devices of the same
operator must be configured to the IP pool networking mode. The BSC6900 can only be
connected to all the CN devices of the same operator in either ATM or IP transmission mode.
When the IP pool networking mode is configured on the Iu-CS Interface, multiple interface
boards form a resource pool that connects to the circuit service (CS) domain, as shown in Figure
9-3. The IP pool networking mode has the following advantages:
l
Simplifies transmission capacity expansion for the BSC6900.
Implements capacity expansion or reconfiguration of a peer NE such as NRNC, MGW,

SGSN, and GGSN without modifying the transmission data configured on the BSC6900
side.
Issue 03 (2015-06-30)

350
RAN17.1
Figure 9-3 IP pool networking
Procedure
Step 1 Remove Iu-CS configuration data.
1.
2.
3.
Remove the user plane configuration data on the Iu-CS interface.

a.
Optional: If the layer 3 networking is used between the BSC6900 and CS domain,
run the MML command RMV IPRT to remove an IP route on the user plane of the
Iu-CS interface.
b.
Remove the control-plane configuration data on the Iu-CS interface.

a.
Run the MML command RMV UCNNODE to remove a CN node.
b.
Run the MML command RMV UCNDOMAIN to remove a CN domain.
c.
Run the MML command RMV ADJNODE command to remove an adjacent

transmission node.
d.
Optional: If the layer 3 networking is used between the BSC6900 and CS domain,
run the MML command RMV IPRT to remove an IP route on the control plane of
the Iu-CS interface.
e.
Run the MML command RMV M3LNK to remove an M3UA link.
f.
Run the MML command RMV M3RT to remove an M3UA route.
g.
Run the MML command RMV M3LKS to remove an M3UA link set.
h.

a.
Issue 03 (2015-06-30)

1)
2)
3)
b.
Optional: If VLANs are configured for the BSC6900, run the RMV VLANID to
delete the mapping between IP addresses and VLAN IDs.
c.
If non-link aggregation is used, run the RMV ETHIP command to remove the IP
address of the Ethernet port.
351
RAN17.1
d.
Optional: Run the RMV DEVIP command to remove the device IP address of a
board.
e.
Optional: Run the RMV ETHREDPORT command to remove the active and
standby Ethernet ports.
Step 2 Configure the IP pool networking mode on the Iu-CS interface.

1.
Configure physical layer and data link layer by referring to the procedure in Configuring
Physical-Layer and Data-Link-Layer Data for the FG2c/GOUc/GOUe in Initial
2.
Configure the transmission resource pool by referring to the procedure in Configuring the
Route in Initial Configuration Guide.
3.
Configure control plane over the Iu-CS interface by referring to the procedure in
Configuring Control-Plane Data over the Iu-CS Interface in Initial Configuration Guide.
4.
Configure user plane over the Iu-CS interface (in transmission resource pool) by referring
to the procedure in Configuring User-Plane Data over the Iu-CS Interface (in Transmission
Resource Pool Mode) in Initial Configuration Guide.
5.
Configure the mapping between service types and transmission resources for an adjacent
node by referring to the procedure in Configuring the Mapping Between Service Types and
Transmission Resources for an Adjacent Node in Initial Configuration Guide.
----End
Follow-up Procedure
l
Verification
1.
Configure transmission equipment and peer equipment based on the network plan.
For details, see the documents delivered with the equipment.
2.
l
Rollback
1.
Remove the IP pool networking mode on the Iu-CS interface.

a.
b.
adjacent node.
a.

b.
Run the RMV TRMMAP command to remove the transport resource

mapping.
Remove the user plane configuration data on the Iu-CS interface (IP Pool).
Run the RMV ADJNODE command to remove an adjacent node.
c.
Issue 03 (2015-06-30)

a.
b.
c.
Optional: If the layer 3 networking is used between the BSC6900 and CS

domain, run the MML command RMV IPRT to remove an IP route on the
control plane of the Iu-CS interface.

352
RAN17.1
d.
e.
d.
e.
f.
g.

a.

b.
c.

a.

b.

c.

trunk group.
trunk group.
d.

port.
ports.
2.
Issue 03 (2015-06-30)
Configure the IP networking mode on the Iu-CS interface.

a.
Configure physical layer and data link layer (in IP mode) by referring to the
procedure in Configuring Physical-Layer and Data Link-Layer Data (in IP Mode)
b.
Configure control plane over the Iu-CS interface (over IP) by referring to the
procedure in Configuring the Control Plane of the Iu-CS Interface (over IP) in
c.
Configure the user plane over the Iu-CS interface (over IP) by referring to the
procedure in Configuring the User Plane of the Iu-CS Interface (over IP) in Initial
d.

353
RAN17.1
9.2.1.6 Changing Networking Mode over the Iu-PS Interface from IP to

Transmission Resource Pool
This section describes how to configure the IP pool networking mode on the Iu-PS interface to
Prerequisites
l

License requirement
The license controlling transmission resource pool for the RNC's Iu-PS interface has
been activated.
Context
NOTICE
morning hours.
When the BSC6900 has been connected to the core network (CN) devices of multiple operators
in ATM or IP transmission mode and you want to configure the IP pool networking mode on
the Iu-PS interface, the networking modes of the BSC6900 and the CN devices of the same
operator must be configured to the IP pool networking mode. The BSC6900 can only be
connected to all the CN devices of the same operator in either ATM or IP transmission mode.
When the IP pool networking mode is configured on the Iu-PS Interface, multiple interface
boards form a resource pool that connects to the packet service (PS) domain, as shown in Figure
9-4. The IP pool networking mode has the following advantages:
Issue 03 (2015-06-30)

354
RAN17.1
Simplifies the transmission capacity expansion for the BSC6900.

side.
Procedure
Step 1 Remove Iu-PS configuration data.
1.
2.
3.
Remove the user plane configuration data on the Iu-PS interface.

a.
Optional: If the layer 3 networking is used between the BSC6900 and PS domain,
run the MML command RMV IPRT to remove an IP route on the user plane of the
Iu-PS interface.
b.
Remove the control-plane configuration data on the Iu-PS interface.

a.
b.
c.
Run the MML command RMV ADJNODE command to remove an adjacent node.
d.
Optional: If the layer 3 networking is used between the BSC6900 and NodeB, run
the MML command RMV IPRT to remove an IP route on the control plane of the IuPS interface.
e.
f.
g.
h.

a.
Issue 03 (2015-06-30)

1)
2)
3)

355
RAN17.1
b.
c.
d.
board.
e.
Step 2 Configure the IP pool networking mode on the Iu-PS interface.

1.
2.
3.
Configure control plane over the Iu-PS interface by referring to the procedure in
Configuring Control-Plane Data over the Iu-PS Interface in Initial Configuration Guide.
4.
Configure the user plane over the IU-PS interface by referring to the procedure in
Configuring User-Plane Data over the Iu-PS Interface (in Transmission Resource Pool
Mode) in Initial Configuration Guide.
5.
----End
Follow-up Procedure
1.
Configure transmission equipment and peer equipment based on the network plan. For
2.
9.2.1.7 Changing Networking Mode over the Iur Interface from IP to Transmission
Resource Pool
This section describes how to configure the IP pool networking mode on the Iur interface to
Prerequisites
l

l
Issue 03 (2015-06-30)
356
RAN17.1

l
License requirement
The license controlling transmission resource pool for the RNC's Iu/Iur interface has
been activated.
Context
NOTICE
morning hours.
When the IP pool networking mode is configured on the Iur Interface, multiple interface boards
form a resource pool that connects to adjacent RNCs, as shown in Figure 9-5. The IP pool
networking mode has the following advantages:
l
Simplifies the transmission capacity expansion for the BSC6900.

side.
Issue 03 (2015-06-30)

357
RAN17.1
Procedure
Step 1 Remove Iub configuration data.
1.
2.
3.
4.
Remove the configuration data about the SRNC relocation IP path on the Iur interface.
a.
Run the MML command RMV IPPATH to remove an IP path for SRNC relocation.
b.
Run the MML command RMV IPRT to remove an IP route that connects to an
adjacent RNC.
Remove the user plane configuration data on the Iur interface.

a.
Optional: If the layer 3 networking is used between the BSC6900 and adjacent RNC,
run the MML command RMV IPRT to remove an IP route.
b.
Remove the control-plane configuration data on the Iur interface.

a.
Run the MML command RMV ADJNODE command to remove an adjacent node.
b.
Optional: If the layer 3 networking is used between the BSC6900 and NodeB, run
the MML command RMV IPRT to remove an IP route on the control plane of the Iur
interface.
c.
d.
e.
f.
Run the MML command RMV UNRNC to remove an adjacent RNC.
g.

a.

1)
2)
3)
b.
c.
d.
board.
e.
Step 2 Configure the IP pool networking mode on the Iur interface.

1.
2.
Issue 03 (2015-06-30)

358
RAN17.1
3.
Configure control plane over the Iur interface by referring to the procedure in Configuring
Control-Plane Data over the Iur Interface in Initial Configuration Guide.
4.
Configure user plane over the Iur interface (in transmission resource pool) by referring to
the procedure in Configuring User-Plane Data over the Iur Interface (in Transmission
Resource Pool Mode) in Initial Configuration Guide.
5.
----End
Follow-up Procedure
1.
Configure transmission equipment and peer equipment based on the network plan. For
2.
9.2.2 Reconfiguring Timeslot Cross Connection

This section describes how to reconfigure timeslot cross connection on an RNC and on a NodeB.
9.2.2.1 Configuring a Timeslot Cross Connection on the RNC

This describes how to configure a timeslot cross connection on the RNC, providing channels
between narrow-band transmission equipment.
Prerequisites
l
Before configuring a timeslot cross connection, collect information listed in Table 9-25.
Information
Description
E1/T1 timeslot information
Query and record timeslots reserved on the

E1/T1 link for services.
None
None
License requirement
None
Issue 03 (2015-06-30)

359
RAN17.1
Context
MO
Setting Notes
Data Source
MML Command
TSCROSS
Configure the timeslot

cross connection
based on the plan.
Internal plan
ADD TSCROSS
Procedure
l
Using MML commands

1.
Run the ADD TSCROSS to add a timeslot cross connection on the AEUa, PEUa, or
PEUc board. To add more timeslot cross connections, run this command for each
timeslot cross connection.

1.
2.
to
----End
Issue 03 (2015-06-30)

360
RAN17.1
Example
//Adding a timeslot cross connection
ADD TSCROSS: SRN=2, SN=15, SRCPORTNO=6, SRCTSMASK=TS1-1, DSTPORTNO=8,
DSTTSMASK=TS1-0&TS2-0&TS3-0&TS4-0&TS5-0&TS6-0&TS7-0&TS8-0&TS9-0&TS10-0&TS
11-0&TS12-0&TS13-0&TS14-0&TS15-0&TS16-0&TS17-0&TS18-0&TS19-0&TS20-0&TS210&TS22-0&TS23-0&TS24-0&TS25-0&TS26-0&TS27-0&TS28-0&TS29-0&TS30-0&TS31-0;
//Querying the timeslot cross connection
LST TSCROSS: SRN=2, SN=15, SRCPORTNO=6;
Follow-up Procedure
l
Verification
Run the LST TSCROSS command to check whether the timeslot cross connection is
correctly configured.
Rollback
Using MML commands
1.
2.
3.
9.2.2.2 Configuring a Timeslot Cross Connection on a NodeB

This section describes how to configure a timeslot cross connection on a running NodeB,
providing channels between narrow-band transmission equipment.
Prerequisites
l
The E1/T1 link is configured as a fractional ATM or PPP link. The link has idle timeslots.
The NodeB works properly.
Using MML commands
Procedure
l
Issue 03 (2015-06-30)
1.
On the NodeB LMT, run the ADD TSCROSS command to add a timeslot cross
connection to the NodeB.
2.
On the NodeB LMT, run the LST TSCROSS command to check whether the
configuration is correct.

361
RAN17.1
1.
2.
to
----End
9.3 Network Cutover

This section describes network cutover of configured interfaces, excluding the procedure for
configuring newly added interfaces. For details about how to configure the newly added
interfaces, see BSC6900 UMTS Initial Configuration Guide.
Context
Network cutover consists of three phases: designing a network cutover scheme, preparing the
configuration data, and implementing the network cutover scheme. The first two phases are
described in Huawei professional service documentation. This section describes only how to
implement the network cutover scheme.
9.3.1 Changing the Connection Between the BSC and the MSC
This section describes how to relocate the BSC from one MSC (MSC A) to another MSC (MSC
B) to optimize the network architecture.
Issue 03 (2015-06-30)

362
RAN17.1
Context
Information described in this section will be included in the subsequent professional service for
project delivery.
When an originating signaling point code (OPC) or destination signaling point code (DPC)
changes, the Equipment Serial Number (ESN) of the BSC changes. The ESN of the BSC is
bound to a license. Therefore, apply for a new BSC license and activate it upon any changes of
the ESN.
Changing the connection between the BSC and the MSC is categorized into three types by the
transmission mode over the Iu-CS interface, as listed in Table 9-27.
Table 9-27 Changing the connection between the BSC and the MSC
Before the Reconfiguration
After the Reconfiguration
IP
IP
ATM
ATM
ATM
IP
9.3.1.1 Changing the Connection Between the BSC and the MSC (IP Transmission
Mode Retained on the Iu-CS Interface)
The IP transmission mode over the Iu-CS interface remains after an RNC is relocated from one
MSC (MSC A) to another MSC (MSC B).
Prerequisites
l
Network planning is complete.

Network planning is performed to plan the data throughput, the type, number, and backup
mode of interface boards, to set the IP addresses for Ethernet ports and trunk groups, and
to determine whether to configure active and standby gateways and virtual local area
network (VLAN) for the interface boards. Contact Huawei to obtain the detailed network
planning scheme.
The IP interface boards are in position and the IP transport network is ready.
The new MSC is ready and the interconnection parameters have been negotiated with
the RNC.
License requirement
The license controlling IP transmission over the Iu-CS interface has been activated.
Issue 03 (2015-06-30)

363
RAN17.1
Context
NOTICE
Changing the connection between the RNC and the MSC will interrupt RNC services. Perform
this operation when the traffic is light, for example, during early morning hours.
To configure IP networking on the Iu-CS interface, the networking modes of the RNC and the
CN equipment run by the same operator must be set to IP.
During the configuration process, configure a new MSC and then remove the original MSC.
l
If the RNC has idle slots, configure data for the new MSC first to ensure that the
communication between the RNC and the control plane and user plane of the new MSC is
normal. Then, remove the configuration data of the original MSC.
If the RNC has no idle slots, remove the configuration data of the original MSC first to
release the interface boards connected to it. Then, configure data for the new MSC and
connect the new MSC to the released interface boards.
This document takes the first method as an example to explain the reconfiguration procedure.
Procedure
Step 1 Configure Iu-CS configuration data for the new MSC (IP).
1.
Run the MML command ADD BRD to add an IP interface board.
2.
Run the MML command ADD N7DPC to add a destination signaling point (DSP) to the
new MSC.
3.
Optional: Run the MML command ADD M3LE to add an MTP3-User Adaptation Layer
(M3UA) local entity.
NOTE
If the IU-PS or Iur interface has used IP transmission and shares the same originating signaling point
(OSP) with the Iu-CS interface, you do not need to add the M3UA local entity.
4.
Run the MML command ADD M3DE to add an M3UA destination entity to a new MSC.
5.
Configure the Physical Layer and Data Link Layer.
6.
Configure Iu-CS control-plane data.
7.
Configure Iu-CS user-plane data.
8.
Remove the mapping between service types and transmission resources for the adjacent
node.
Step 2 Switch the Iu-CS interface to a new MSC.

1.
Run the MML command RMV UCNNODE to remove the original CN node.
2.
Run the MML command ADD UCNNODE to add a CN node. In this step, set CN domain
ID to CS_DOMAIN and Iu transfers bearer type to IP_TRANS.
Step 3 Remove the Iu-CS configuration data of the original MSC.

1.
Issue 03 (2015-06-30)
management on the Iu-CS interface.
364
RAN17.1
2.
3.
a.
Optional: If the layer 3 networking is used between the RNC and the CS domain, run
the MML command RMV IPRT to remove an IP route on the user plane on the IuCS interface.
b.
c.
Optional: If a transmission resource mapping for an adjacent node is configured, run

the MML command RMV ADJMAP to remove the mapping.
d.
Run the MML command RMV TRMMAP to remove transport resource mapping
(TRMMAP) items for IP transmission on the Iu-CS interface.
e.
f.
g.
Run the MML command RMV ADJNODE to remove an adjacent node on the Iu-CS
interface.

a.
Run the MML command RMV MTP3LNK to remove a Message Transfer Part Layer
3 (MTP3b) link.
b.
Run the MML command RMV MTP3RT to remove an MTP3b route.
c.
Run the MML command RMV MTP3LKS to remove an MTP3b signaling link set.
d.
Run the MML command RMV SCTPLNK to remove a Signaling Control

Transmission Protocol (SCTP) link.
e.
Run the MML command RMV N7DPC to remove a DSP.
Remove the configuration data at the physical layer and the data link layer.
l If link aggregation is used, perform the following operations:
a.
Run the MML command RMV ETHTRKIP to remove the IP address of a trunk
group.
b.
Run the MML command RMV ETHTRKLNK to remove a link from an LAG.
c.
Run the MML command RMV ETHTRK to remove an LAG.
d.
Optional: If VLANs are configured, run the MML command RMV VLANID to
remove the mapping between IP addresses and VLAN IDs.
l If link aggregation is not used, run the MML command RMV ETHIP to remove the
IP address of an Ethernet port.
4.
a.
Run the MML command RMV DEVIP to remove the device IP address of a board.
b.
Run the MML command RMV ETHREDPORT to remove the active and standby
Ethernet ports.
Run the MML command RMV BRD to remove an IP interface board on the Iu-CS interface.
----End
Follow-up Procedure
l
Verification
Verify network reliability as follows:
1.
Issue 03 (2015-06-30)
Run the MML command DSP N7DPC to query the state of an SS7 DSP and ensure
that SCCP DSP state is set to Accessible. If the value of SCCP DSP state is not
Accessible, troubleshoot the fault by referring to the relevant alarm help.
365
RAN17.1
2.
l
Run the MML command PING IP to check whether the IP address of the MGW is
reachable. If not, troubleshoot the fault first.
Rollback
Relocate the RNC from MSC B to MSC A by performing operations in Reconfiguration
Procedure.
9.3.1.2 Changing the Connection Between the RNC and MSC (ATM Transmission
Mode Retained on the Iu-CS Interface)
This section describes how to relocate the RNC from one MSC (MSC A) to another MSC (MSC
B) with the ATM transmission mode retained on the Iu-CS interface.
Prerequisites
l

Network planning is performed to plan the type, number, and backup mode of the interface
boards, and the interconnection parameters to be negotiated with the MSC. Contact Huawei
to obtain the detailed network planning scheme.
The transmission equipment between the RNC and the new MSC is ready.
The new MSC is ready.
Context
NOTICE
l
If the RNC has idle interface boards or interface boards have idle ports, configure data for
the new MSC first to ensure that the new MSC can provide services. Then, remove the
configuration data of the original MSC.
If the RNC has no idle interface boards or interface boards have no idle ports, remove the
configuration data of the original MSC first to release the interface boards connected to it.
Then, configure data for the new MSC and connect the new MSC to the released interface
boards.
Procedure
Step 1 Configure Iu-CS configuration data for the new MSC (ATM).
1.
Run the MML command ADD BRD to add an ATM interface board.
2.
new MSC.
Issue 03 (2015-06-30)

366
RAN17.1
3.
Configure the physical layer.
4.
Configure the ATM transmission resources.
5.
6.
7.
node.

1.
2.
ID to CS_DOMAIN and Iu transfers bearer type to ATM_TRANS.

1.
2.
3.
a.
Run the MML command RMV AAL2PATH to remove an ATM Adaption Layer
Type 2 (AAL2) path. To remove more AAL2 paths, run this command for each AAL2
path.
b.

c.
(TRMMAP) items for ATM transmission on the Iu-CS interface.
d.
interface.

a.
3 (MTP3b) link.
b.
Run the MML command RMV SAALLNK to remove a Signaling ATM Adaptation
Layer (SAAL) link.
c.
d.
e.
Run the MML command RMV N7DPC to remove a destination signaling point
(DSP).
Run the MML command RMV BRD to remove an ATM interface board on the Iu-CS
interface.
----End
9.3.1.3 Changing the Connection Between the RNC and the MSC (Transmission
Mode on the Iu-CS Interface Changed from ATM to IP)
The transmission mode over the Iu-CS interface changes from ATM to IP when the RNC is
relocated from MSC A to MSC B.
Issue 03 (2015-06-30)

367
RAN17.1
Prerequisites
l

Network planning is performed to plan the data throughput, the type, number, and backup
mode of interface boards, to set the IP addresses for Ethernet ports and trunk groups, and
to determine whether to configure active and standby gateways and virtual local area
network (VLAN) for the interface boards. Contact Huawei to obtain the detailed network
planning scheme.
The FG2c/GOUc/GOUe board is in position and the IP transport network is ready.
The new MSC is ready.
None
License requirement
The license controlling IP transmission over the Iu-CS interface has been activated.
Context
NOTICE
To configure IP networking on the Iu-CS interface, the networking modes of the RNC and the
CN equipment run by the same operator must be set to IP.
l
If the RNC has idle slots, configure data for the new MSC first to ensure that the
communication between the RNC and the control plane and user plane of the new MSC is
normal. Then, remove the configuration data of the original MSC.
If the RNC has no idle slots, remove the configuration data of the original MSC first to
release the interface boards connected to it. Then configure data to the new MSC.
Procedure
Step 1 Configure Iu-CS configuration data for the new MSC (IP).
1.
Run the MML command ADD BRD to add an IP interface board.
2.
new MSC.
3.
Optional: Run the MML command ADD M3LE to add an MTP3-User Adaptation Layer
(M3UA) local entity.
Issue 03 (2015-06-30)

368
RAN17.1
NOTE
If the IU-PS or Iur interface has used IP transmission and shares the same originating signaling point
(OSP) with the Iu-CS interface, you do not need to add the M3UA local entity.
4.
Run the MML command ADD M3DE to add an M3UA destination entity to a new MSC.
5.
Configure the physical layer and data link layer.
6.
7.
8.
node.

1.
2.
ID to CS_DOMAIN and Iu transfers bearer type to IP_TRANS.

1.
2.
3.
a.
Run the MML command RMV AAL2PATH to remove an ATM Adaption Layer
Type 2 (AAL2) path. To remove more AAL2 paths, run this command for each AAL2
path.
b.

c.
(TRMMAP) items for ATM transmission on the Iu-CS interface.
d.
interface.

a.
3 (MTP3b) link.
b.
Run the MML command RMV SAALLNK to remove a Signaling ATM Adaptation
Layer (SAAL) link.
c.
d.
e.
Run the MML command RMV BRD to remove an ATM interface board on the Iu-CS
interface.
----End
Follow-up Procedure
l
Verification
Verify network reliability as follows:
Issue 03 (2015-06-30)

369
RAN17.1
1.
Run the MML command DSP N7DPC to query the state of an SS7 DSP and ensure
that SCCP DSP state is set to Accessible. If the value of SCCP DSP state is not
Accessible, troubleshoot the fault by referring to the relevant alarm help.
2.
Run the MML command PING IP to check whether the IP address of the MGW is
reachable. If not, troubleshoot the fault first.
Rollback
1.
2.
3.
Configure Iu-CS configuration data for the original MSC (ATM).

a.
Run the MML command ADD BRD to add an ATM interface board.
b.
Run the MML command ADD N7DPC to add a destination signaling point
(DSP) to the new MSC.
c.
Configure the physical layer.
d.
Configure the ATM transmission resources.
e.
f.
g.
adjacent node.
Switch the Iu-CS interface to the original MSC.

a.
b.
Run the MML command ADD UCNNODE to add a CN node. In this step, set
CN domain ID to CS_DOMAIN and Iu transfers bearer type to
ATM_TRANS.
Remove the Iu-CS configuration data of the new MSC.

a.
b.
Issue 03 (2015-06-30)
a.
Optional: If the layer 3 networking is used between the RNC and the CS
domain, run the MML command RMV IPRT to remove an IP route on the
user plane on the Iu-CS interface.
b.
c.
Optional: If a transmission resource mapping for an adjacent node is

configured, run the MML command RMV ADJMAP to remove the
mapping.
d.
Run the MML command RMV TRMMAP to remove transport resource

mapping (TRMMAP) items for IP transmission on the Iu-CS interface.
e.
f.
g.
Run the MML command RMV ADJNODE to remove an adjacent node on

the Iu-CS interface.

a.
Run the MML command RMV MTP3LNK to remove a Message Transfer

Part Layer 3 (MTP3b) link.
b.

370
RAN17.1
c.
c.
Run the MML command RMV MTP3LKS to remove an MTP3b signaling

link set.
d.
Run the MML command RMV SCTPLNK to remove a Signaling Control

Transmission Protocol (SCTP) link.
e.
Remove the configuration data at the physical layer and the data link layer.
a.
Run the MML command RMV ETHTRKIP to remove the IP address

of a trunk group.
b.
Run the MML command RMV ETHTRKLNK to remove a link from

an LAG.
c.
Run the MML command RMV ETHTRK to remove an LAG.
d.
Optional: If VLANs are configured, run the MML command RMV

VLANID to remove the mapping between IP addresses and VLAN IDs.
If link aggregation is not used, run the MML command RMV ETHIP to
remove the IP address of an Ethernet port.
d.
Issue 03 (2015-06-30)
a.
Run the MML command RMV DEVIP to remove the device IP address
of a board.
b.
Run the MML command RMV ETHREDPORT to remove the active

Run the MML command RMV BRD to remove an IP interface board on the IuCS interface.

371

RAN17.1 Reconfiguration Guide For BSC6900 (03) (PDF) - en

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

RAN17.1 Reconfiguration Guide For BSC6900 (03) (PDF) - en

Загружено:

Авторское право:

Доступные форматы

RAN17.

Reconfiguration Guide for BSC6900

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

Technical support engineers

Huawei Proprietary and Confidential

About This Document

Network optimization engineers

Huawei Proprietary and Confidential

About This Document

Times New Roman

Normal paragraphs are in Times New Roman.

Names of files, directories, folders, and users are in

Book titles are in italics.

Examples of information displayed on the screen are in

The keywords of a command line are in boldface.

Command arguments are in italics.

About This Document

Items (keywords or arguments) in brackets [ ] are optional.

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Buttons, menus, parameters, tabs, window, and dialog titles

Multi-level menus are in boldface and separated by the ">"

Press the keys concurrently. For example, pressing Ctrl+Alt

Press the keys in turn. For example, pressing Alt, A means

Huawei Proprietary and Confidential

About This Document

Select and release the primary mouse button without moving

Press the primary mouse button twice continuously and

Huawei Proprietary and Confidential

5 Backing Up and Restoring Data by CME...............................................................................28

Huawei Proprietary and Confidential

6.8 Removing a Board or a Subrack...................................................................................................................................70

7 Reconfiguring the NodeB..........................................................................................................89

8 Reconfiguring the UMTS Network.......................................................................................203

Huawei Proprietary and Confidential

8.1.4 Reconfiguring Cell System Information Parameters...............................................................................................214

9 Reconfiguring the Interfaces...................................................................................................277

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

l Added descriptions about NIU reconfiguration. For

Huawei Proprietary and Confidential

l Deleted operations of modifying board content and

The description of the procedure is modified, and the

Huawei Proprietary and Confidential

l Added the built-in ECO6910. Added sections 6.5

Huawei Proprietary and Confidential

About This Chapter

Huawei Proprietary and Confidential

System capacity expansion

Data Configuration Tool

The LMT provides graphic user interfaces (GUIs) for users to

The CME provides GUIs for users to configure a single base

Process of Reconfiguring Data Using the CME

Table 2-2 Reconfiguration process