Bsc6910 Umts Commissioning Guide (v100r015c00 - 02) (PDF) - en

BSC6910 UMTS
V100R015C00
Commissioning Guide
Issue
02
Date
2013-07-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2013. 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 02 (2013-07-30)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
BSC6910 UMTS
Commissioning Guide
About This Document
About This Document

Overview
BSC6910 commissioning is performed after hardware is installed and before services are
provided. It aims to ensure that the BSC6910 can work properly by performing verification tasks
related to equipment, board software and data file loading, interfaces, and services.
Product Version
The following table lists the product version related to this document.
Product Name
Product Version
BSC6910
V100R015C00
Intended Audience
This document is intended for field engineers.
Organization
1 Changes in the BSC6910 UMTS Commissioning Guide
This chapter describes the changes in the BSC6910 UMTS Commissioning Guide.
2 Commissioning Prerequisites
Before the BSC6910 commissioning, the status of the equipment and the network to be
commissioned must meet the conditions required. The software installation packages, licenses,
and MML command scripts required for commissioning must be ready.
3 Commissioning Process
The BSC6910 commissioning can be performed remotely, locally, or remotely with local
assistance.
4 Checking Operating Status of Hardware
Issue 02 (2013-07-30)

ii
BSC6910 UMTS
Commissioning Guide
About This Document
Before commissioning the equipment, ensure that the BSC6910 subrack is powered on and is
operating normally.
5 Commissioning the OMU
Before using the OMU for the first time, commission the OMU onsite to check the installation
of OMU applications and the version of the OMU applications, and configure the IP address,
mask, and name of the OMU to ensure the normal communication between the BSC6910 and
the LMT or M2000.
6 Logging In to the BSC6910 Through the LMT
This section describes how to log in to the BSC6910 through the LMT and enable communication
between the LMT and the BSC6910 to ensure smooth BSC6910 commissioning through the
LMT.
7 Updating the OMU Database
This chapter describes how to update configuration data in the OMU database by running MML
command scripts.
8 Activating and Verifying the License
This section describes how to activate the license and verify the license configuration
information to enable the service checking.
9 Loading BSC6910 Board Software and Data Files
This chapter describes how to load the BSC6910 board software and data files.
10 Connecting to the M2000
This section describes how to connect the BSC6910 to the M2000 for centralized management.
11 Setting the Connection Mode Between the M2000 and BSC6910 to SSL
The connection mode between the M2000 and BSC6910 must be set to Secure Socket Layer
(SSL) on the M2000 to ensure operation and maintenance (O&M) safety.
12 Verifying Interfaces
This section describes how to verify interfaces on the BSC6910 side. Select a verification method
based on the onsite situation.
13 Handling the Alarms Generated During the Commissioning
This section describes how to handle the alarms generated during the commissioning to prevent
the alarms from affecting service verifications.
14 Verifying UMTS Services
This section describes how to verify that the UMTS basic services and the feature services that
are enabled are normal. The basic UMTS services are voice service, CS streaming service, PS
service, and mobility management service. The feature services include inter-RAT handovers,
HSDPA, HSUPA, 64QAM, MIMO, and DC-HSDPA.
15 Verifying Network Reliability
The network reliability can be verified after you switch over active and standby boards, check
generated alarms, and making dialing tests.
16 Troubleshooting
Issue 02 (2013-07-30)

iii
BSC6910 UMTS
Commissioning Guide
About This Document
This chapter describes how to troubleshoot common problems during the commissioning.
17 Appendix
This chapter provides communication ports on and the commissioning checklist of the
BSC6910.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
Indicates a hazard with a high level or medium level of risk
which, if not avoided, could result in death or serious injury.
Indicates a hazard with a low level of risk which, if not
avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation that, if not
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
Indicates a tip that may help you solve a problem or save
time.
Provides additional information to emphasize or supplement
important points of the main text.
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 02 (2013-07-30)

iv
BSC6910 UMTS
Commissioning Guide
About This Document
Convention
Description
Boldface
The keywords of a command line are in boldface.
Italic
Command arguments are in italics.
[]
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 02 (2013-07-30)

BSC6910 UMTS
Commissioning Guide
Issue 02 (2013-07-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
BSC6910 UMTS
Commissioning Guide
Contents
Contents
About This Document.....................................................................................................................ii
1 Changes in the BSC6910 UMTS Commissioning Guide.......................................................1
2 Commissioning Prerequisites.....................................................................................................3
3 Commissioning Process...............................................................................................................5
4 Checking Operating Status of Hardware..................................................................................7
5 Commissioning the OMU............................................................................................................9
5.1 Commissioning the OMU Locally...............................................................................................................................10
5.2 Commissioning the OMU Using a USB Flash Drive...................................................................................................15
6 Logging In to the BSC6910 Through the LMT.......................................................................23

7 Updating the OMU Database....................................................................................................25
8 Activating and Verifying the License......................................................................................29
9 Loading BSC6910 Board Software and Data Files................................................................31
9.1 Generating Data Files for the Loading.........................................................................................................................32
9.2 Setting the Loading Mode............................................................................................................................................32
9.3 Resetting BSC6910 Boards..........................................................................................................................................32
9.4 Checking the Consistency of the Data and the Version...............................................................................................33
10 Connecting to the M2000..........................................................................................................35

11 Setting the Connection Mode Between the M2000 and BSC6910 to SSL.......................37
12 Verifying Interfaces..................................................................................................................39
12.1 Verifying Interfaces on the M2000............................................................................................................................40
12.1.1 Setting the NE Engineering Mode to TESTING.....................................................................................................40
12.1.2 Verifying Interfaces Automatically.........................................................................................................................41
12.1.3 Setting the NE Engineering Mode to NORMAL...................................................................................................43
12.2 Verifying Interfaces on the LMT................................................................................................................................44
12.2.1 Verifying Fiber Optic Cable Connections...............................................................................................................45
12.2.2 Verifying Internal Interfaces....................................................................................................................................46
12.2.3 Verifying the Iub Interface......................................................................................................................................47
12.2.4 Verifying the Iu-CS Interface..................................................................................................................................49
Issue 02 (2013-07-30)

vii
BSC6910 UMTS
Commissioning Guide
Contents
12.2.5 Verifying the Iu-PS Interface..................................................................................................................................52

12.2.6 Verifying the Iur Interface.......................................................................................................................................53
12.2.7 Verifying the Iu-BC Interface..................................................................................................................................55
12.2.8 Verifying the Iur-g Interface....................................................................................................................................56
12.2.9 Verifying the Iur-p Interface....................................................................................................................................57
13 Handling the Alarms Generated During the Commissioning.........................................59

14 Verifying UMTS Services........................................................................................................60
15 Verifying Network Reliability................................................................................................63
16 Troubleshooting........................................................................................................................65
16.1 Checking Transmission Links....................................................................................................................................67
16.2 Performing a VCL Continuity Check.........................................................................................................................69
16.3 Verifying the PVC Delay Detection Function............................................................................................................70
16.4 Unavailable E1/T1 Port..............................................................................................................................................72
16.5 Unavailable FE/GE Port.............................................................................................................................................73
16.6 Cell Setup Failure.......................................................................................................................................................73
16.7 Signaling Link Failure on the Iub Interface................................................................................................................79
16.8 AAL2/IP Connection Setup Failure...........................................................................................................................83
16.9 Data Loading Failures on the Board...........................................................................................................................85
16.10 Performing a Loopback Test on an Optical Port......................................................................................................87
17 Appendix.....................................................................................................................................90
17.1 Communication Ports on the BSC6910......................................................................................................................91
17.2 BSC6910 Commissioning Checklist..........................................................................................................................91
Issue 02 (2013-07-30)

viii
BSC6910 UMTS
Commissioning Guide
Changes in the BSC6910 UMTS

Commissioning Guide
This chapter describes the changes in the BSC6910 UMTS Commissioning Guide.
02 (2013-07-30)
This is the second commercial release of V100R015C00.
Compared with issue 01 (2013-05-04), this issue does not include any new topics.
Compared with issue 01 (2013-05-04), this issue incorporates the following changes:
Content
Change Description
16.1 Checking Transmission

Links
Added procedure of checking FRA transmission link.
Compared with issue 01 (2013-05-04), this issue does not exclude any topics.
01 (2013-05-04)
This is the first commercial release of V100R015C00.
Compared with issue Draft A (2013-01-30), this issue does not include any new topics.
Compared with issue Draft A (2013-01-30), this issue incorporates the following changes:
Content
Change Description
8 Activating and Verifying the

License
Added procedure of verifying the license information.
Compared with issue Draft A (2013-01-30), this issue does not exclude any topics.
Issue 02 (2013-07-30)

BSC6910 UMTS
Commissioning Guide
Draft A (2013-01-30)
This is the Draft A release of V100R015C00.
Issue 02 (2013-07-30)

BSC6910 UMTS
Commissioning Guide
Commissioning Prerequisites
Before the BSC6910 commissioning, the status of the equipment and the network to be
commissioned must meet the conditions required. The software installation packages, licenses,
and MML command scripts required for commissioning must be ready.
Requirements for Equipment Status

Before commissioning, ensure that the equipment meets the conditions listed in Table 2-1.
Table 2-1 Requirements for equipment status before commissioning
Item
Requirement
BSC6910 hardware
The hardware is installed and has passed the hardware

installation check and power-on check.
OMU
The OMU is configured before delivery. For details, see

Checklist for the OMU Software Factory Settings in the
BSC6910 UMTS OMU Administration Guide.
LMT PC
The LMT PC meets the configuration requirements. For details,

see Configuration Requirements of the LMT PC in the BSC6910
UMTS LMT User Guide.
Requirements for the Network to Be Commissioned

To ensure the smooth commissioning of the Iub, Iu, Iur, Iur-g, Iur-p, and Iu-BC interfaces, the
network equipment in the network to be commissioned must meet the following requirements:
l
At least one NodeB is connected to the BSC6910. The NodeB must have passed
commissioning and can provide basic functions.
At least one set of CN equipment is connected to the BSC6910. The CN equipment must
have passed commissioning and can provide basic functions.
Other network equipment that is connected to the network equipment to be commissioned,

if any, must have passed commissioning and can provide basic functions. If an RNC, BSC,
or call broadcast center (CBC) is connected to the BSC6910, the RNC, BSC, or CBC must
have passed commissioning and can provide basic functions.
Issue 02 (2013-07-30)

BSC6910 UMTS
Commissioning Guide
Three single-mode UEs and one dual-mode UE are ready for test and are registered with
the home location register (HLR).
Figure 2-1 shows a typical network to be commissioned.

Figure 2-1 Typical network to be commissioned
Requirements for the Software and Data Files

l
Software installation package

The installation package of the OMU application that is compatible with the local office
version must be ready before commissioning.
License
The license that is applicable to configuration in the local office is obtained from the Huawei
technical support engineer.
MML command script file

Before commissioning, complete the initial configuration according to the BSC6910
UMTS Initial Configuration Guide to obtain the MML command script file. In addition,
check and ensure the correctness of the data configuration based on the MML command
script examples and the on-site negotiated data defined in the BSC6910 UMTS Initial
Configuration Guide.
Issue 02 (2013-07-30)

BSC6910 UMTS
Commissioning Guide
Commissioning Process
The BSC6910 commissioning can be performed remotely, locally, or remotely with local
assistance.
l
Local commissioning is performed by a field engineer (engineer responsible for onsite

commissioning in the BSC equipment room) who connects a PC to the BSC and performs
the commissioning on the LMT.
Remote commissioning is remotely performed by an engineer (technical engineer

responsible for the BSC) and multiple BSCs can be commissioned simultaneously in the
central equipment room.
Remote commissioning with local assistance is performed remotely by an engineer with

the assistance of a field engineer.
Figure 3-1 shows the commissioning process if all commissioning prerequisites are met.
Issue 02 (2013-07-30)

BSC6910 UMTS
Commissioning Guide
Figure 3-1 Commissioning flowchart
Issue 02 (2013-07-30)

BSC6910 UMTS
Commissioning Guide
Checking Operating Status of Hardware

Before commissioning the equipment, ensure that the BSC6910 subrack is powered on and is
operating normally.
Prerequisites
The BSC6910 subrack has passed the power-on check.
Procedure
Step 1 Check whether the subrack is powered on.
If...
Then...
The subrack is not powered on
Go to Step 2.
The subrack is powered on
Go to Step 4.
Step 2 Set the power switches that control the subrack power supply on the power distribution frame
(PDF) to ON.
Step 3 Set the air switches that control the subrack power supply on the power entry module (PEM) to
ON.
Step 4 Check the power supply to the subrack components, as listed in Table 4-1. Ensure that the
hardware operates correctly.
Table 4-1 Checklist of the power supply to the cabinet components
Issue 02 (2013-07-30)
Component
Normal Power Supply Status
Board
The RUN indicator on the board panel is

neither steady on nor steady off.
Fan box
The RUN indicator on the fan box panel

blinks one second on and one second off in
green after the subrack is powered on.
BSC6910 UMTS
Commissioning Guide
Component
Normal Power Supply Status
PEM
The STATUS indicator on the panel is green

and steady on.
NOTE
If power failure occurs, handle the problem by referring to step 5 in section Powering on the Subrack in the
BSC6910 UMTS Site Maintenance Guide.
----End
Issue 02 (2013-07-30)

BSC6910 UMTS
Commissioning Guide
Commissioning the OMU
About This Chapter

Before using the OMU for the first time, commission the OMU onsite to check the installation
of OMU applications and the version of the OMU applications, and configure the IP address,
mask, and name of the OMU to ensure the normal communication between the BSC6910 and
the LMT or M2000.
Context
The OMU can be commissioned locally or through a USB flash drive. Select a commissioning
method based on the onsite scenario.
5.1 Commissioning the OMU Locally
The OMU is locally commissioned by a field engineer who connects a PC to the OMU. If the
BSC6910 is configured with active and standby OMUs, commission the active OMU and the
standby OMU based on the procedure given in this section.
5.2 Commissioning the OMU Using a USB Flash Drive
This section describes how to commission the OMU using a USB flash drive. You can locally
insert the prepared USB flash drive to the OMU at the site and then perform OMU commissioning
with cooperation of a remote engineer.
Issue 02 (2013-07-30)

BSC6910 UMTS
Commissioning Guide
5.1 Commissioning the OMU Locally

The OMU is locally commissioned by a field engineer who connects a PC to the OMU. If the
BSC6910 is configured with active and standby OMUs, commission the active OMU and the
standby OMU based on the procedure given in this section.
Prerequisites
l
You have obtained the OMU application installation package consistent with the OMU
version used in the local office and the Records of OMU Software Installation
Information.
You have obtained the planned OMU IP addresses and the OMU name and recorded them
in Configuration Information for Commissioning the OMU Locally.
You have obtained the psftp software and the PuTTY software. For details, see psftp
Software and PuTTY Software in the BSC6910 UMTSOMU Administration Guide.
Context
In new deployment scenarios, the active workspace of the OMU is version_a by default. In the
following descriptions, the active workspace of the OMU uses version_a.
For details about the definitions of OMU IP addresses mentioned in the following descriptions,
see section OMU IP Address Plan in BSC6910 UMTSOMU Administration Guide. You can run
the ./omutool dispipinfo command to query these IP addresses or check modification results.
Procedure
Step 1 Connect the PC to the OMU board.
1.
Connect the PC to the ETH2 commissioning port on the OMU board by using a network
cable.
2.
Set the IP addresses of the PC and ETH2 port to be on the same network segment.
The initial IP address of the ETH2 port is 192.168.6.50 (active OMU) or 192.168.6.60
(standby OMU), and the subnet mask is 255.255.255.0.
Step 2 Set the link mode of the external OMU Ethernet adapters.
1.
Log in to the OMU by referring to Logging In to the OMU in the BSC6910 UMTSOMU
Administration Guide.
2.
Check whether the link mode of the external OMU Ethernet adapters is consistent with that
of LAN switches.
For details about how to query the link mode of the external OMU Ethernet adapters, see
Follow-up Procedure of Setting the Link Mode for External OMU Ethernet Adapters in the
BSC6910 UMTSOMU Administration Guide.
Issue 02 (2013-07-30)
If...
Then...
The link mode of the external OMU

Ethernet adapters is consistent with that of
LAN switches
Go to Step 3.

10
BSC6910 UMTS
Commissioning Guide
If...
Then...
The link mode of the external OMU

Ethernet adapters is inconsistent with that
of LAN switches
Set the link mode of the external OMU

network adapters to be consistent with that
of LAN switch by referring to operations
in Procedure of Setting the Link Mode for
External OMU Ethernet Adapters in
BSC6910 UMTSOMU Administration
Guide.
Step 3 Install the OMU applications.

1.
Run the /etc/rc.d/omud status command to check the running status of the OMU process.
If...
Then...
The information displayed is running
a. Run the /etc/rc.d/omud stop command

to stop the omud process.
b. Go to Step 3.2.
The information displayed is unused
Go to Step 3.2.
The information displayed is No such file

or directory
a. Install the OMU applications in the

active workspace by referring to
operations in Procedure of Installing
the OMU Applications in the Active
Workspace in the BSC6910
UMTSOMU Administration Guide.
b. Go to Step 6.
c. Go to Step 7. The task is completed.
2.
Issue 02 (2013-07-30)
Run the cd /mbsc/upgrade command to switch to the OMU installation directory, and then
run the ls command to query the current versions of the OMU applications.
If...
Then...
The versions of the OMU applications are

the same as those required by the operator
Go to Step 4.

11
BSC6910 UMTS
Commissioning Guide
If...
Then...
The versions of the OMU applications are

different from those required by the
operator
a. Uninstall the OMU applications by

referring to operations in Procedure of
Uninstalling the OMU Applications in
the BSC6910 UMTSOMU
Administration Guide.
b. Upload the OMU application
installation package to the OMU by
referring to operations in Procedure of
Uploading the OMU Application
Installation Package to the OMU in the
BSC6910 UMTSOMU Administration
Guide.
c. Install the OMU applications in the
active workspace by referring to
operations in Procedure of Installing
the OMU Applications in the Active
Workspace in the BSC6910
UMTSOMU Administration Guide.
d. Go to Step 6.
e. Go to Step 7. The task is completed.
Step 4 Modify the OMU IP addresses.

1.
Run the cd /mbsc/bam/version_a/bin/bam command to switch to the directory where the

omutool program is located.
NOTE
You can run the ./omutool -h command to view the help information of the omutool.
2.
Change the fixed external IP address and subnet mask according to the plan of the operator.
Run the ./omutool extercard The external fixed IP address The subnet mask The gateway
IP address (Optional) command to change the fix external IP address and the subnet mask.
For example, you can type the following command and then press Enter.
./omutool extercard 10.161.10.100 255.255.255.0
NOTE
l The following two methods show how to change the fixed external IP address if changing the
gateway IP address is required at the same time.
l Method 1: Type ./omutool extercard The external fixed IP address The subnet mask (The
gateway IP address) and then press Enter to change the fixed external IP address and gateway
IP address at the same time. The following is an example:
./omutool extercard 10.161.10.100 255.255.255.0 10.161.10.1
l Method 2: Type ./omutool gateway The gateway IP address and then press Enter to change
the gateway IP address separately. The following is an example:
./omutool gateway 10.161.10.1
l After the fixed external IP address is changed, the OMU can be connected to the operation and
maintenance (OM) network of the operator by using the ETH0 or ETH1 port. In this case, the
commissioning task can continue remotely.
Issue 02 (2013-07-30)

12
BSC6910 UMTS
Commissioning Guide
3.
Change the virtual external IP address and the subnet mask of the active and standby OMUs
according to the plan. Ensure that the virtual external IP address is on the same network
segment as the fixed external IP address.
Run the ./omutool extervip The external virtual IP address The subnet mask command to
change the virtual external IP address and the subnet mask. For example, you can type the
following command and then press Enter.
./omutool extervip 10.161.10.102 255.255.255.0
NOTE
When the fixed or virtual external IP address is being changed, a window is displayed to remind users
to check whether the virtual or fixed external IP address and the gateway IP address need to be
changed. In this way, users can make necessary changes to ensure that the three IP addresses are on
the same network segment.
4.
Issue 02 (2013-07-30)
Check whether the fixed internal IP address, virtual internal IP address, backup channel IP
address, and debugging IP address of active and standby OMUs are on the same network
segment as the operator's network.

13
BSC6910 UMTS
Commissioning Guide
If...
Then...
All IP addresses are on the same

network segment as the network
of the operator
Change the IP address in conflict.

l Run the ./omutool innercard The internal fixed
IP address command to change the fixed internal
IP address and the subnet mask. For example, you
can type the following command and then press
Enter.
./omutool innercard 80.168.3.60
l Run the ./omutool innervip The internal virtual

IP address command to change the virtual internal
IP address and the subnet mask. For example, you
Enter.
./omutool innervip 80.168.3.40
NOTE
l When the fixed or virtual internal IP address is being
changed, a window is displayed to remind users to
check whether the virtual or fixed internal IP
address needs to be changed. In this way, users can
make necessary changes to ensure that the two IP
addresses are on the same network segment.
l If the network segment of the virtual or fixed
internal IP address is changed, the Subnet No. must
be changed when updating the OMU database. For
details, see Follow-up Procedure in 7 Updating the
OMU Database to ensure that the OMU
communicates normally with the BSC6910 host.
l Change the backup channel IP address and subnet

mask of the active and standby OMUs:
Run the ./omutool backupcard The IP address
command. For example, you can type the
following command and then press Enter.
./omutool backupcard 192.168.3.60
l Run the ./omutool debugcard The debugging IP

address command to change the debugging IP
address and the subnet mask. For example, you
Enter.
./omutool debugcard 192.168.6.60
The preceding IP addresses are

not on the same network
segment as the network of the
operator
Change the backup channel IP address of the standby

OMU.
Run the ./omutool backupcard The IP address
command. For example, you can type the following
command and then press Enter.
./omutool backupcard 192.168.3.60
Step 5 Change the OMU name.

1.
Run the ./omutool hostname OMU name command to change the name of the OMU.
For example, you can type ./omutool hostname omu_123 and then press Enter.
Issue 02 (2013-07-30)

14
BSC6910 UMTS
Commissioning Guide

NOTE
The OMU name cannot contain control characters, spaces, or any of the following characters: / \ [ ] ( ) ' :
| < > + = ; , ?, and the length of the OMU name ranges from 1 to 62 characters.
Step 6 Set the working mode of the OMU.

1.
Set the OMU backup attribute.

l If only one OMU board is configured, run the ./omutool dualmode single command
to set the OMU to work in independent mode.
l If two OMU boards (active and standby OMU boards) are configured, run the ./omutool
dualmode dual command to set the OMU to work in active/standby mode.
2.
Set the product mode.

a.
Run the /etc/rc.d/omud start command to start the OMU applications.
b.
Run the MML command SET OFFICENAME to set the product mode.
Step 7 Check the OMU running status.

1.
Run the ps -afx command to check the running status of the OMU.
The OMU is operating properly if all OMU processes exist in the OMU active workspace
directory /mbsc/bam/version_a/bin/bam/monitor.
OMU State
OMU Processes that Must Exist
Active OMU
host_gate, ems_gate, authority,

configure, maintain, stat, alarm,
software, ftp_server, sntp, ems_agent,
omu_manager, cfa, weblmt, debug_log,
and cfg_mirror
Standby OMU
software, ftp_server, sntp,

omu_manager, and debug_log
NOTE
If some of the processes do not exist, run the /etc/rc.d/omud restart command to restart the OMU
server, and then check again whether the processes exist. If some of them still do not exist, uninstall
the OMU applications and then reinstall the OMU applications in the active workspace by referring
to operations in Procedure of Uninstalling the OMU Applications and Installing the OMU
Applications in the Active Workspace in the BSC6910 UMTSOMU Administration Guide.
2.
Run the exit command to stop the PuTTY and then remove the cable to the OMU.
----End
5.2 Commissioning the OMU Using a USB Flash Drive

This section describes how to commission the OMU using a USB flash drive. You can locally
insert the prepared USB flash drive to the OMU at the site and then perform OMU commissioning
with cooperation of a remote engineer.
Issue 02 (2013-07-30)

15
BSC6910 UMTS
Commissioning Guide
Prerequisites
l
The preparations for installing software on site are completed. For details, see Onsite
Software Installation Preparations in the BSC6910 UMTS OMU Administration Guide.
You have obtained the planned OMU IP addresses and the OMU name, and have recorded
them in Configuration Information for Preparing the USB Flash Drive.
The capacity of the USB flash drive is at least 2 GB. If the BSC6910 is configured with
active and standby OMUs, two USB flash drives are required.
A USB port is available on the PC, and the USB port is not restricted. For example, there
is no CPM restriction.
Using a USB flash drive to commission an OMU involves two steps: preparing the USB
flash drive and commissioning the OMU after inserting the USB flash drive into the OMU.
The prepared USB flash drive applies only to the DOPRA Linux operating system.
This section takes the commissioning OMU in active/standby mode as an example.

Differences between operations for the OMU in independent mode and that in active/
standby mode are specified.
Check whether the USB flash drive is usable by referring to the DOPRA Linux USB Flash
Drive Certificate Guide under the Dopra_Linux_U tool (a tool used for preparing the USB
flash drive) directory. If the USB flash drive cannot be used, replace it with another one.
The Netac U208 (2 GB), Kingston and Sandisk USB storage devices are recommended.
Context
CAUTION
Back up the OMU data before you install the OMU operating system and OMU applications.
The OMU hard disk will be formatted during the installation of the OMU operating system and
OMU applications using the USB flash drive and all data will be deleted.
Procedure
Step 1 Prepare a USB flash drive.
1.
Insert a USB flash drive into the USB port on a portable computer.
2.
Double-click U_creator_chs.exe to open the Dopra_Linux_U tool, as shown in Figure

5-1.
Issue 02 (2013-07-30)

16
BSC6910 UMTS
Commissioning Guide
Figure 5-1 Dopra_Linux_U tool window
3.
Issue 02 (2013-07-30)
Select NE List in the left panel of the window shown in Figure 5-1 and right-click the list
to choose Add NE. A dialog box is displayed, as shown in Figure 5-2.

17
BSC6910 UMTS
Commissioning Guide
Figure 5-2 Add NE dialog box
4.
Enter the NE Name, set Operate type to Install, select Install OMU?, enter the external
virtual IP address of the NE to be added and then click OK. An NE is added.
NOTE
l The NE name is used to identify different NEs and only can include letter, numerals, "-", and "_".
l After an NE is added, the NE name and the external virtual IP address can be changed only after you
delete the NE and then add the NE.
l If you want to prepare multiple USB flash drives, it is recommended that you prepare the USB flash
drives one by one and make a mark on each USB flash drive to specify which NE this USB flash drive
is to be used for.
5.
Issue 02 (2013-07-30)
Double-click the newly added NE on the left pane. After all the information is automatically
obtained, check whether the information is correct and enter the information that needs to
be typed, as shown in Figure 5-3.

18
BSC6910 UMTS
Commissioning Guide
Figure 5-3 Configuring information
The description of the parameter is as the following:

l All the manually configured items need to be entered.
l If Install OMU? is not selected in Step 1.4, only the names of the active and standby
OMUs and IP addresses are displayed in the Figure 5-3.
l In the configuration information interface, the values of the Backup network IP and
Backup network mask parameters must be specified. If the active and standby OMU
board is installed, the backup channels are respectively configured on the network
adapters of the backup channels corresponding to the OMUs.
l To install the software version, select the V**R**C** directory in the version
installation package. To install the baseline software patch, select
V**R**C**SPCX00 folder in the baseline patch installation package.
l To install a non-baseline software patch, select the V**R**C**SPCXYZ or
V**R**C**SPHXYZ directory in the patch installation package.
l Select the link mode of external network adapters listed in Figure 5-3 as required. Note
that the link mode of external network adapters must be consistent with that of the onsite
LAN switch. Table 5-1 lists the mapping between the queried link mode of OMU
external Ethernet adapters and the external network netcard mode of OMU selected in
Figure 5-3.
Issue 02 (2013-07-30)

19
BSC6910 UMTS
Commissioning Guide
Table 5-1 Mapping between the queried link mode of OMU external Ethernet adapters and
the selected external network netcard mode
Queried Link Mode of OMU External
Ethernet Adapters
Selected External Network Netcard

Mode
l Auto-negotiation is on
Auto
l Auto-negotiation is off
10Mb Full
l Speed is 10 Mbit/s
l Duplex is Full
10Mb Half
l Duplex is Half
100Mb Full

l Duplex is Full
100Mb Half

l Duplex is Half
1000Mb Full

l Duplex is Full
1000Mb Half

l Duplex is Half
6.
Check that all information is correct. Click OK. Check the local directory of the USB flash
drive in the displayed dialog box, and then start the process for preparing the USB flash
drive for the active OMU.
7.
After the USB flash drive for the active OMU is prepared, check the prompted information,
and then insert the USB flash drive for the standby OMU to prepare the USB flash drive
for the standby OMU. After the message Succeed to create USB flash drive of OMU
installation displays, click Finish. The USB flash drives are prepared.
NOTE
l After the USB flash drive is prepared, remove it from the PC in safe mode to avoid data loss or data
corruption.
l If only one OMU is configured, the USB flash drive for the standby OMU is not required.
Step 2 Commissioning the OMU after inserting the USB flash drive to the OMU
1.
Insert the USB flash drive into any USB ports on the OMU board panel.
2.
Remove and then install the OMU board to reset it. For details, see sections Removing a
Board and Installing a board in the BSC6910 UMTS Site Maintenance Guide.
3.
Observe the status of the indicator on the OMU panel. Determine whether the installation
is complete by referring to the following table.
Issue 02 (2013-07-30)

20
BSC6910 UMTS
Commissioning Guide

NOTE
If the status of the indicators differs from this, the OMU cannot identify the USB flash device. When this
occurs, prepare another USB flash device. Alternatively, copy the data in the original USB flash device
to a new USB flash device, and then reinstall the OMU operating system.
For information about how much time will be consumed during the OMU operating system installation,
see Table 1 in Dopra_Linux_USB Disk Tool.
Table 5-2 Status of indicators on the OMU board panel during the OMU operating system
and OMU applications installation
Board
Installation
Procedure
Successful
Installation
Failed Installation
EOMU
a
At the beginning:
l The RUN indicator

blinks.
l The RUN indicator

blinks.
l The ALM indicator

is steady on or off.
l The ALM indicator

blinks.
l The ACT indicator

is steady on or off.
l The ACT indicator

is off.
l The OFFLINE
indicator is off.
l The OFFLINE
indicator is off.
l The RUN indicator

blinks.
l The ALM indicator
blinks.
l The ACT indicator
blinks.
l The OFFLINE
indicator is off.
After a certain period:
l The RUN indicator
blinks.
l The ALM indicator
is off.
l The ACT indicator is
off.
l The OFFLINE
indicator blinks.
CAUTION
After the OMU operating system and the OMU applications are installed successfully,
remove the USB flash drive from the OMU panel. The OMU commissioning by using the
USB flash drive is complete.
----End
Follow-up Procedure
Check whether the configuration files prepared during the step Prepare the USB flash drive
are correct according to the Configuration Information for Preparing the USB flash drive
for Installation recorded during the preparations.
Issue 02 (2013-07-30)

21
BSC6910 UMTS
Commissioning Guide
If the configuration files are not correct, prepare the USB flash drive again by referring to
Prepare the USB flash drive.
If the configuration files are correct, contact Huawei technical support by referring to
Contact Huawei Customer Service Center.
NOTE
After the OMU operating system and the OMU applications are installed successfully, remove the USB
flash drive from the OMU panel. The OMU commissioning by using the USB flash drive is complete.
Issue 02 (2013-07-30)

22
BSC6910 UMTS
Commissioning Guide
Logging In to the BSC6910 Through the LMT

This section describes how to log in to the BSC6910 through the LMT and enable communication
between the LMT and the BSC6910 to ensure smooth BSC6910 commissioning through the
LMT.
Prerequisites
l
The OMU commissioning has been completed.
The network connection between the LMT and the OMU has been established.
NOTE
In the case of the local OMU commissioning, a field engineer performs local commissioning tasks
and then Log in to the BSC6910 through the LMT to verify the connection between the OMU and
the external network. In this case, the field engineer needs to type the IP address for OMU
commissioning in the address bar of Internet Explorer (IE) to log in to the LMT for local
commissioning.
Context
JRE is a standard plug-in in Java operating environment. If JRE is not installed, a message is
displayed when you start the LMT. In this case, install JRE according to the prompt message on
the screen. If the JRE installed in the PC is not of the latest version, a message is displayed when
you start the LMT, prompting you to update the JRE. In this case, it is recommended that you
uninstall the old version and then install the latest version.
WARNING
When the LMT application is running, do not change the LMT PC system time. Otherwise,
severe errors may occur on the system. If you have to change the system time, stop all the LMT
applications first.
Procedure
Step 1 Check the configuration of the LMT PC and ensure that it meets the requirements.
1.
Issue 02 (2013-07-30)
Check the hardware configuration of the BSC6910 LMT PC to ensure that the requirements
described in Configuration Requirements of the LMT PC are met.
23
BSC6910 UMTS
Commissioning Guide
2.
Check the security settings of the Internet Explorer and ensure that the Java script is
supported.
Step 2 Start the IE, and then log in to the BSC6910 through the LMT.
1.
Start the IE and enter the external virtual IP address of the OMU of the BSC6910 on the
address bar. The log-in dialog box is displayed, as shown in Figure 6-1.
Figure 6-1 BSC6910 log-in dialog box
NOTE
To log in to the BSC6910 by using the Domain user account, establish the connection between the
BSC6910 and the M2000 server.
2.
Enter User Name, Password, and Verify Code, and click Login to log in to the LMT.
----End
Issue 02 (2013-07-30)

24
BSC6910 UMTS
Commissioning Guide
Updating the OMU Database
This chapter describes how to update configuration data in the OMU database by running MML
command scripts.
Prerequisites
l
You have completed the section You have 6 Logging In to the BSC6910 Through the
LMT..
The MML command data scripts applicable to the local office are verified and the contents
are precise and complete.
There are two ways to run MML command scripts: by running MML commands or using
the GUI. The MML command script can be executed by using the GUI only when a script
is smaller than 4 MB. It is recommended that you run the MML script by running MML
commands, because it is more efficient.
You can query the active workspace of the OMU through the MML command LST
OMUAREA. The following procedure assumes that the active workspace is version_a.
Run the MML command script by running MML commands
Context
Procedure
1.
Run the MML command SET CFGDATAINEFFECTIVE to set the system to work
in ineffective mode.
CAUTION
If the database has been updated, run the MML command SET
CFGDATAINEFFECTIVE to set the system to work in ineffective mode.
Issue 02 (2013-07-30)
2.
Run the MML command RST DATA. Click Yes in the displayed dialog box to
initialize the BSC6910 configuration data in the OMU database.
3.
Upload the MML command script to the /ftp folder in the OMU active workspace
directory. The following assumes that the MML script BATCHFILE.txt saved in
disk D is uploaded to the OMU active workspace /mbsc/bam/version_a/ftp to
introduce the two methods.
25
BSC6910 UMTS
Commissioning Guide

NOTE
Two methods are available: through File Manager on the LMT or through command lines.
Through File Manager on the LMT

a.
Click File Manager on the toolbar of the LMT to start the file manager.
b.
In the displayed window, choose Root > bam > version_a > ftp on the left
and click Upload on the right. A dialog box is displayed. Select
BATCHFILE.txt saved in disk D, and then click Open to upload the file.
Through command lines

a.
On the local PC, choose Start > Run. Type cmd and click OK.
b.
Input d: and press Enter to switch to disk D.
c.
Input ftp IP address to connect to the OMU. Here, IP address is the IP address
of the OMU.
d.
Input the FTP user name and password. The connection between the OMU
and the local FTP is set up after the authentication succeeds.
NOTE
The FTP user name is always FtpUsr. The FTP password is set during the OMU
application installation. Both the FTP username and password are already recorded in the
Information Records of OMU Software Installation.
4.
e.
Input cd /mbsc/bam/version_a/ftp to switch to the OMU active workspace.
f.
Input put BATCHFILE.txt to upload the file.
g.
After the file is uploaded successfully, input quit to disconnect the FTP.
Run the MML command RUN BATCHFILE to run the batch command file. It is
recommended that you set Finish Type to ANY_ERR_RETURN(Stop at Error),
Result Recording Type to REC_ERR(Record errors), Source File Name to
BATCHFILE.txt, and Result File Name to RUN_BATCHFILE_RESULT.txt.
NOTE
l The result file RUN_BATCHFILE_RESULT.txt is saved in the /ftp folder in the OMU
active workspace installation directory, that is, /mbsc/bam/version_a/ftp.
l The execution of the script takes a certain period of time. For example, 1-1.5 hours will be
needed for executing a script with 100,000 commands.
l If the MML script fails to be executed, open the RUN_BATCHFILE_RESULT.txt file
to check the commands that fail to be executed. Then, extract the commands that fail to be
executed and the commands that have not been executed to generate a new MML script.
Correct the MML script based on the displayed messages, and then go toStep 4 to run the
new script.
Run the MML script by using the GUI

1.
Run the MML command SET CFGDATAINEFFECTIVE to set the system to work
in ineffective mode.
CAUTION
If the database has been updated, run the MML command SET
CFGDATAINEFFECTIVE to set the system to work in ineffective mode.
2.
Issue 02 (2013-07-30)
Run the MML command RST DATA. Click Yes in the displayed dialog box to
initialize theBSC6910 configuration data in the OMU database.
26
BSC6910 UMTS
Commissioning Guide
3.
On the LMT, click the Batch tab. The Batch tab page is displayed, as shown in Figure
7-1.
Figure 7-1 Batch tab page
4.
Click Open....The Open dialog box is displayed. Select the prepared MML command
script, and then click Open. The commands in the script are displayed on the Batch
tab page.
5.
Click Set.... The Set dialog box is displayed. Set Sending Commands Interval(s) to
0, select Save Failed Commands and set the path for saving the failed commands,
and then click OK, as shown in Figure 7-2.
Figure 7-2 Setting the batch commands
Issue 02 (2013-07-30)

27
BSC6910 UMTS
Commissioning Guide
6.
On the Batch tab page, select All in the Execution Type area.
7.
Click Go. The system runs the MML commands one by one.
NOTE
l Click OK when the system displays that the current configuration is in ineffective mode
after you click Go. The execution of the script will take a long time in GUI mode. For
example, 2-3 hours will be needed for executing a 4-MB script.
l If an Error dialog box showing Execution failed. Continue? is displayed during the
execution of the MML command script, you can infer that the MML command script is
incorrect. In this case, select Yes to All to ignore the error prompt. After the MML script
file is executed, extract the commands that fail to be executed to generate a new MML
script, correct the commands based on the prompts, and then go to Step 4 to run the script
again.
8.
Click OK when a dialog box is displayed, indicating that the running of all the MML
commands is complete.
----End
Follow-up Procedure
After the OMU database is upgraded, perform the following to ensure the normal communication
between the OMU and BSC6910.
1.
Run the MML command LST SUBNET to query the Subnet No. of the BSC6910.
2.
Check whether the Subnet No. of the BSC6910 is consistent with the network segment of
the planned internal IP address of the OMU.
NOTE
The planned internal IP address of the OMU is recorded in Configuration Information for Verifying
OMU Locally.
l If they are consistent, end this task.

l If they are inconsistent, run the MML command SET SUBNET to change the Subnet
No. of the BSC6910 so that it is consistent with the network segment of the planned
internal IP address of the OMU.
3.
Run the MML command SET CFGDATAEFFECTIVE to set the system to work in
effective mode.
4.
Run the MML command RST BSC to reset the entire system. The new IP address of the
BSC6910 host takes effect.
Issue 02 (2013-07-30)

28
BSC6910 UMTS
Commissioning Guide
Activating and Verifying the License
This section describes how to activate the license and verify the license configuration
information to enable the service checking.
Prerequisites
l
You have 6 Logging In to the BSC6910 Through the LMT..
The FTP server is started. For details on how to start the FTP server, see the operations in
Startup in the BSC6910 UMTS LMT User Guide for FTP Server. For the username and
password of the FTP server, see FTP Server in the BSC6910 UMTS LMT User Guide. Note
that the user name or password may be modified.
The license is ready and the license check is passed.
Context
The active workspace of the OMU can be queried through the MML command LST
OMUAREA. The following operations assume that the active workspace is version_a.
Procedure
Step 1 Run the MML command DLD LICENSE to download the license to the OMU active workspace
directory /ftp/license, that is /mbsc/bam/version_a/ftp/license.
Step 2 Run the MML command LST LICENSE and then set File Name to the name of the license file
to be activated to query the detailed configuration information of the license file.
If...
Then...
The license is consistent with what you apply Go to Step 3.

for
The license is inconsistent with what you
apply for
Contact the Huawei Customer Service

Center by referring to Contact Huawei
Customer Service Center.
Step 3 Run the MML command CHK DATA2LIC, and then set File Name to the name of the license
file to be activated to verify the license information including the equipment serial number
(ESN), version, working mode, and configuration.
Issue 02 (2013-07-30)

29
BSC6910 UMTS
Commissioning Guide
If...
Then...
The license information is consistent with

the OMU information
Go to Step 4.
The license information is inconsistent with Modify the inconsistent data and repeat this
the OMU information
step.
Step 4 Run the MML command ACT LICENSE to activate the license file.
Step 5 Optional: If there are the primary and secondary operators, run the MML command SET
LICENSE to reallocate the resources and functions in sequence from the primary operator to
the secondary operator. If there are multiple secondary operators, run the commands several
times.
----End
Follow-up Procedure
If the license activation fails, you can infer that the configuration data of the license is
inconsistent with that in the OMU database. Check the configuration data of the license and the
configuration data in the OMU database.
l
If the configuration data such as the product name, ESN, and version number of the license
is incorrect, apply for a new license.
If the configuration data in the OMU database is incorrect, correct the configuration data,
and then reactivate the license.
NOTE
An invalid or expired license file can also lead to license activation failure. For details, see the help of the
MML command ACT LICENSE.
Issue 02 (2013-07-30)

30
BSC6910 UMTS
Commissioning Guide
Loading BSC6910 Board Software and Data

Files
About This Chapter

This chapter describes how to load the BSC6910 board software and data files.
Prerequisites
l
The OMU has been commissioned.
The OMU database has been updated.
Context
The software of the BSC6910 is generated automatically in the OMU active workspace
directory /bin/fam during the installation of the OMU applications. For example, if the active
workspace is version_a, the software is in /mbsc/bam/version_a/bin/fam. The software can
be loaded directly.
To make the configuration take effect, format the configuration data in the OMU database to
generate a .DAT data file, and then reset the BSC6910 boards.
9.1 Generating Data Files for the Loading
This section describes how to generate data files, which can be loaded, using the MML data
scripts.
9.2 Setting the Loading Mode
This section describes how to set the loading modes of all the board subsystems before resetting
BSC6910 boards.
9.3 Resetting BSC6910 Boards
This section describes how to load the BSC6910 board software and data files from the OMU
installation directory to the boards and make them take effect.
9.4 Checking the Consistency of the Data and the Version
This section describes how to check whether the board configuration and the software version
of the BSC6910 are consistent with those on the OMU.
Issue 02 (2013-07-30)

31
BSC6910 UMTS
Commissioning Guide
9.1 Generating Data Files for the Loading

This section describes how to generate data files, which can be loaded, using the MML data
scripts.
Prerequisites
l
You have 6 Logging In to the BSC6910 Through the LMT.
Procedure
Step 1 Run the MML command SET CFGDATAEFFECTIVE and do not specify any parameter to
set the system to work in effective mode.
Step 2 Run the MML command FMT DATA and set Work Area Flag to Active(Format active
area) to format the configuration data in the OMU database. Do not specify the subrack number
when running the MML command.
----End
9.2 Setting the Loading Mode

This section describes how to set the loading modes of all the board subsystems before resetting
BSC6910 boards.
Prerequisites
Context
For details about the loading modes, see BSC6910 Loading Management.
Procedure
Step 1 Run the MML command SET LODCTRL to set the loading mode. In this command, set Board
Start Load Control to LFB(Load from OMU and write flash).
----End
9.3 Resetting BSC6910 Boards

This section describes how to load the BSC6910 board software and data files from the OMU
installation directory to the boards and make them take effect.
Prerequisites
l
The data file for the loading has been generated.
All the subracks have been powered on.
Issue 02 (2013-07-30)

32
BSC6910 UMTS
Commissioning Guide
Context
The resetting time is less than or equals to 10 minutes.
Procedure
Step 1 Run the MML command RST BSC to reset all the BSC6910 service processing boards.
NOTE
You can observe the loading process on the Progress tab page on the LMT home page. If this tab page is hidden,
click Progress in the toolbar on the LMT home page.
Step 2 Click the Device Maintenance tab on the LMT home page. The Device Maintenance tab page
is displayed.
Step 3 Check whether all the boards on the device panel are in normal state.
If...
Then...
The device panel shows that all the boards End this task.
are in normal state
The device panel shows that some boards Check the faulty boards and clear the alarms
are not in normal state
according to operations in 16.9 Data Loading
Failures on the Board.
----End
9.4 Checking the Consistency of the Data and the Version

This section describes how to check whether the board configuration and the software version
of the BSC6910 are consistent with those on the OMU.
Prerequisites
l
All the subracks and boards are running normally.
Procedure
Step 1 Run the MML command ACT CRC and do not specify a parameter and check whether the
BSC6910 board configuration is consistent with the data on the OMU.
Expected result: The All table data consistent. message is displayed.
Step 2 Run the MML command CMP BRDVER and do not specify a parameter to check whether the
version run by the BSC6910 is consistent with the version information on the OMU.
Expected result: The Compare consistent message is displayed.
NOTE
If the board configuration or software version is inconsistent with the information on the OMU, run the MML
command RST SUBRACK reset the subrack where the board with incorrect data or version is located.
----End
Issue 02 (2013-07-30)

33
BSC6910 UMTS
Commissioning Guide
Follow-up Procedure
After the consistency check, restore the loading method of the board: Run the MML command
SET LODCTRL to set Board Start Load Control to CL(Consult Load).
Issue 02 (2013-07-30)

34
BSC6910 UMTS
Commissioning Guide
10
Connecting to the M2000
This section describes how to connect the BSC6910 to the M2000 for centralized management.
Prerequisites
l
The operation and maintenance (O&M) network has passed commissioning. The M2000
is operating properly.
The version of the M2000 is compatible with that of the BSC6910.
The mediation version of the M2000 is compatible with the NE version.
If the BSC6910 and the M2000 are in the same network segment, you do not need to
configure an IP route to the BSC6910 to the M2000.
If the BSC6910 and the M2000 are not in the same network segment, you must configure
an IP route from the BSC6910 to the M2000.
Context
Procedure
Step 1 Connect the BSC6910 to the O&M network.
1.
Connect one end of a straight-through cable to the ETH0 or ETH1 port on the OMU board.
2.
Connect the other end of the straight-through cable to the peer network device, such as a
hub or a router, to access the O&M network.
Step 2 Configure an IP route from the BSC6910 to the M2000.

1.
Run the MML command LST OMUIPRT to check whether the IP route to the M2000 is
configured on the OMU.
l If the values of Destination Network Address, Destination Address Mask, and
Forward Route Address are consistent with the planned addresses, the BSC6910 has
an IP route to the M2000. Go to Step 2.3.
l If the Destination Network Address, Destination Address Mask, and Forward
Route Address are not consistent with the planned addresses, the BSC6910 does not
have a route to the M2000. Go to Step 2.2.
2.
Run the MML command ADD OMUIPRT to configure a route from the BSC6910 to the
M2000.
3.
Verify the configuration of the route from the BSC6910 to the router.
Issue 02 (2013-07-30)

35
BSC6910 UMTS
Commissioning Guide
Log in to the OMU according to the instructions in the BSC6910 UMTS OMU
Administration Guide for Logging In to the OMU, and then run the ping command to check
whether the network connectivity between the BSC6910 and the router is available. If the
OMU can receive an acknowledge packet from the router, go to Step 2.4. Otherwise, check
whether the OMU and the router are properly connected.
4.
Verify the configuration of the route from the BSC6910 to the M2000.
Log in to the OMU and run the ping command to check whether the network connectivity
between the BSC6910 and the M2000 is available. If the OMU can receive a response
packet from the M2000, go to Step 3. Otherwise, check whether the OMU and the M2000
are properly connected.
Step 3 Create the BSC6910 on the M2000. For details, see the information about how to create an NE
in the M000 documentation.
CAUTION
l If a firewall exists between the BSC6910 and M2000, enable the communication ports
connecting the BSC6910 and M2000 to ensure proper communication between the
BSC6910 and M2000.
l For details on the ports connecting the BSC6910 and M2000, see 17.1 Communication
Ports on the BSC6910.
l The MTU value configured for the transmission equipment between the BSC6910 and the
M2000 must be no less than that configured for the OMU board of the BSC6910. Otherwise,
the communication between the BSC6910 and the M2000 may be abnormal. The default
MTU value for the OMU board is 1500.
----End
Example
Table 10-1 describes how to configure a route between the BSC6910 and the M2000.
Table 10-1 Configuring a route from the BSC6910 to the M2000
Scenar
io
The IP address of the M2000 server is 10.11.100.23. The mask is 255.255.255.255.

The OMU is connected to the M2000 network segment through the router. The IP
address of the router is 172.121.139.10.
Opera
tion
1. Run the MML ADD OMUIPRT command.

l Set Destination network address to 10.11.100.23.
l Set Destination address mask to 255.255.255.255.
l Set Forward route address to 172.121.139.10.
2. Run the Secure Shell (SSH) terminal, such as PuTTY to log in to the OMU.
3. Run the ping 172.121.139.10 command to check whether the network
connectivity between the BSC6910 and router is available.
4. Run the ping 10.11.100.23 command to check whether the network connectivity
between the BSC6910 and M2000 is available.
Issue 02 (2013-07-30)

36
BSC6910 UMTS
Commissioning Guide
11
11 Setting the Connection Mode Between the M2000 and

BSC6910 to SSL
Setting the Connection Mode Between

the M2000 and BSC6910 to SSL
The connection mode between the M2000 and BSC6910 must be set to Secure Socket Layer
(SSL) on the M2000 to ensure operation and maintenance (O&M) safety.
Prerequisites
l
The BSC6910 and peer equipment are physically connected and both have passed the
hardware installation acceptance.
All the subracks of the BSC6910 are running normally.
You have completed section 10 Connecting to the M2000.
You have applied for an SSL safety certificate from the Certificate Authority (CA).
Procedure
Step 1 Import and activate the certificate.
l Importing and activating the certificate on the M2000.
1.
On the M2000 client, choose Security Management > NE Security > Certificate
Authentication Management > Certificate Management(application style) or
Security > Certificate Authentication Management > Certificate Management
(traditional style).
2.
In the displayed Certificate Management window, click the CA Certificate tab and
click Add to add a root certificate.
3.
In the displayed Certificate Management window, click the Device Certificate tab
and click Add.
4.
In the displayed Device Certificate Batch Import window, choose the relevant NE on
the left. Click Import Certificate on the lower right and import the prepared certificate.
Select Activate the Certificate on the bottom and click OK to import and activate the
certificate.
l Importing and activating the certificate on the LMT
Issue 02 (2013-07-30)
1.
On FTP Server, upload the certificate into the directory where the OMU is installed.
2.
Run the MML command SET CERTFILE to set the SSL certificate file of an NE.
37
BSC6910 UMTS
Commissioning Guide
11 Setting the Connection Mode Between the M2000 and

BSC6910 to SSL
NOTE
Private Key Password, Certificate Revocation List File Name, and Certificate Chain File
Name must be set if the three parameters exist.
3.
Run the MML command SET SSLAUTHMODE. In this step, set Authentication
Mode to NONE(Verify None) or PEER(Verify Peer Certificate) as required by the
site.
NOTE
If Authentication Mode is set to NONE(Verify None), that is, if SSL Authentication is set to
Cryptonym Authentication, the BSC6910 and the M2000 do not authenticate each other's certificate.
If Authentication Mode is set to PPEER(Verify Peer Certificate), that is, if SSL Authentication
is set to NE Authentication OMC, or Bidirectional Authentication, the BSC6910 authenticates the
certificate of the M2000; if SSL Authentication is set to OMC Authentication NE, the BSC6910
does not authenticate the peer certificate.
Step 2 Set the connection method between the M2000 and BSC6910 to SSL.
1.
On the M2000 client, choose Security Management > NE Security > Certificate
Authentication Management > SSL Connection Management(application style) or
Security > Certificate Authentication Management > SSL Connection Management
(traditional style).
2.
In the displayed SSL-Connection Policy Management window, set Connection Type of

the relevant NE to SSL Connection. Set SSL Authentication to Cryptonym
Authentication, OMC Authentication NE, NE Authentication OMC, or Bidirectional
Authentication as required on site.
NOTE
When the SSL configuration is modified on the M2000, the M2000 sends a command to the BSC6910 to
synchronize its SSL configuration.
----End
Issue 02 (2013-07-30)

38
BSC6910 UMTS
Commissioning Guide
12
Verifying Interfaces
About This Chapter

This section describes how to verify interfaces on the BSC6910 side. Select a verification method
based on the onsite situation.
12.1 Verifying Interfaces on the M2000
This section describes how to verify interfaces by setting engineering modes and performing an
NE health check on the M2000.
12.2 Verifying Interfaces on the LMT
This chapter describes how to verify interfaces on the BSC6910 by using MML commands on
the LMT or the GUI. The items to be verified include fiber optic cable connections, internal
interfaces, Iub, Iu-CS, Iu-PS, Iur, Iu-BC, Iur-g, and Iur-p interfaces. The Iur interface verification
is mandatory when the BSC6910 connects to another RNC. The Iu-BC interface is mandatory
when RNC cell broadcast services (CBSs). The Iur-g interface verification is mandatory when
the RNC connects to the BSC. The Iur-p interface verification is mandatory when RNC in POOL
is applied.
Issue 02 (2013-07-30)

39
BSC6910 UMTS
Commissioning Guide
12.1 Verifying Interfaces on the M2000

This section describes how to verify interfaces by setting engineering modes and performing an
NE health check on the M2000.
12.1.1 Setting the NE Engineering Mode to TESTING

During commissioning, the NE reports many alarms that require no care. You can mask these
alarms by setting the NE mode to TESTING by using GUL-based functions on the M2000 client
or by running MML commands on the M2000 or LMT.
Prerequisites
l
You have completed M2000.
An NE can work in the following engineering modes: NORMAL, INSTALL,

EXPAND, UPGRADE, and TESTING. The NE mode of the BSC6910 must be set to
TESTING in commissioning scenarios.
Context
NOTE
For details about engineering modes, see section Introduction to the Maintenance Mode
Management Feature in the M2000 Product Documentation.
The NE engineering mode is valid only during the time specified by Start Time and End
Time. Before Start Time and after End Time, the NE mode changes to NORMAL. Alarms
are reported when the NE works in NORMAL mode.
When the NE engineering mode changes to the NORMAL mode, the alarms that are not
cleared in TESTING mode are reported as common alarms to the M2000.
Setting the NE engineering mode by using the GUI on the M2000 client
Procedure
1.
On the M2000 client, choose System Settings > Task Schedule > Maintenance
Mode(Application Styles) or Maintenance > Maintenance Mode(Traditional
Styles).
2.
In the displayed window, click
3.
In the Set NE Mode dialog box, select the BSC6910 NE that needs to be set, and then
set NE Mode to TESTING. A window is displayed, as shown in Figure 12-1.
NOTE
Select the performance methods Instant or Time based on requirements. If Time is selected,
set the Start Time and End Time of testing for the NE.
Issue 02 (2013-07-30)

40
BSC6910 UMTS
Commissioning Guide
Figure 12-1 Setting the NE engineering mode to TESTING
Setting the NE engineering mode by running MLL commands on the M2000 or LMT
1.
On the M2000 client or LMT, run the MML command SET MNTMODE. In this
command, set Maintenance Mode to TESTING(TESTING), Start Time and End
Time to values based on onsite requirements.
----End
Follow-up Procedure
After the preceding operations, all the alarms and events reported during Start Time and End
Time will not be shown in the M2000 Alarm and Event Log for the NE by default. You can
check the alarms and events reported when the NE works in TESTING mode by setting the
filtering conditions. For details, see the M2000 Operator Guide.
12.1.2 Verifying Interfaces Automatically

This section describes how to use an NE health check on the M2000 to automatically verify the
BSC6910 interfaces.
Prerequisites
l
Issue 02 (2013-07-30)
41
BSC6910 UMTS
Commissioning Guide
Context
The internal interface must be verified by using MML commands or GUI on the LMT. For
details, see 12.2.2 Verifying Internal Interfaces.
Procedure
Step 1 Set the scenario for NE health check.
1.
On the M2000 client, choose Trace and Maintenance > Monitor > NE Health Check
(Application Styles) or Maintenance > Network Health Check > NE Health Check
(Traditional Styles).
2.
Click
3.
Click New in the displayed dialog box.
4.
Enter the scenario name in the Scenario Name text box on the right of the dialog box.
on the displayed tab page. The Scenario Management dialog box is displayed.
NOTE
The scenario name must be different from existing scenario names.
5.
Select an NE type for health check in NE Types, that is BSC6910 UMTS.
6.
Select the check items for health check (deselect those not for health check) in the Interface
Check under Check Items.
7.
Click OK A dialog box is displayed, prompting that the NE health check scenario is set up
successfully. Click OK to set up the NE health check scenario.
Step 2 Create an NE health check task.

. The Create Task dialog box is displayed.
1.
On the NE Health Check tab page, click the
2.
Select an application scenario from the Scenario drop-down list. The application scenario
must be suitable for the newly created task. The application scenario and the specific time
(the time is accurate to the second) on which the task is created are automatically displayed
in the Task Name text box.
3.
Select the NE for health check in the Select NE. area.
4.
In the Time Setting area, Click Finish to select the instant execution mode.
NOTE
The executed health check tasks are listed under the Finished Tasks node in the navigation tree on the left
side.
Step 3 Check the NE health check result.

1.
Expand the Finished Tasks node in the navigation tree on the left side. Right-click a
finished task and choose View Report from the shortcut menu.
2.
In the Health Check Report dialog box, select a format to view the NE health check report.
Issue 02 (2013-07-30)

42
BSC6910 UMTS
Commissioning Guide
NOTE
The health check report is compressed to a .zip file. To view the report, double-click the .zip file,
and then double-click the report file index.html in the .zip file browser.
If some items in the health check report are in red, the corresponding interface is faulty. Rectify the
fault according to the health check report.
----End
12.1.3 Setting the NE Engineering Mode to NORMAL

When the end time specified by End Time is reached, the NE finishes its engineering mode
automatically. If the engineering process finishes in advance, you can set the NE engineering
mode to NORMAL by using GUL functions on the M2000 client or by running MML commands
on the M2000 or LMT. Alarms are reported when the NE works in NORMAL mode.
Prerequisites
l
Before interface verification, complete section 12.1.1 Setting the NE Engineering Mode
to TESTING.
BSC6910 has passed commissioning.
Setting the NE engineering mode by using the GUI on the M2000 client
Procedure
1.
On the M2000 client, choose Configuration > Settings > Maintenance Mode
(application style) or Maintenance > Maintenance Mode(traditional style).
2.
In the displayed window, click
3.
In the Set NE Mode dialog box, select the BSC6910 NE to be set, and set NE
Mode to NORMAL, the window shown in Figure 12-2 is displayed.
NOTE
If the NE engineering mode is set to NORMAL, Instant is selected by default.
Issue 02 (2013-07-30)

43
BSC6910 UMTS
Commissioning Guide
Figure 12-2 Setting the NE engineering mode to NORMAL
Setting the NE engineering mode by running MLL commands on the M2000 or LMT
1.
On the M2000 or the LMT client, run the MML command SET MNTMODE, and
set Maintenance Mode to NORMAL(NORMAL).
----End
12.2 Verifying Interfaces on the LMT

This chapter describes how to verify interfaces on the BSC6910 by using MML commands on
the LMT or the GUI. The items to be verified include fiber optic cable connections, internal
interfaces, Iub, Iu-CS, Iu-PS, Iur, Iu-BC, Iur-g, and Iur-p interfaces. The Iur interface verification
is mandatory when the BSC6910 connects to another RNC. The Iu-BC interface is mandatory
when RNC cell broadcast services (CBSs). The Iur-g interface verification is mandatory when
the RNC connects to the BSC. The Iur-p interface verification is mandatory when RNC in POOL
is applied.
Context
During interface verification, you can run an LST command to view the configuration
information. For example, before running the MML command DSP ADJNODE, you can run
the MML command LST ADJNODE to check the value of the Adjacent Node ID parameter.
Issue 02 (2013-07-30)

44
BSC6910 UMTS
Commissioning Guide
12.2.1 Verifying Fiber Optic Cable Connections

This section describes how to verify whether fiber optic cables are connected correctly. This
section applies to the fiber optic cable connections for the working channel and protection
channel between local and peer ends when ports on the local interface boards are working in
multiplex section protection (MSP) mode.
Prerequisites
l
The optical interface board configured on the BSC6910 is operating properly and has been
connected to the transmission equipment with fiber optic cables.
Context
Working channel: board in an even-numbered slot in active/standby mode
Protection channel: board in an odd-numbered slot in active/standby mode
The following operation assumes that the board in an even-numbered slot is the active board
and that the board in an odd-numbered slot is the standby board.
Procedure
Step 1 Run the MML command CHK OPTCRS to check the status of fiber optic cable connections
for an optical interface board.
Expected result: The command output shows that the value for Check Result is Correct
connection.
l If the command output shows that the value of Check Result is The check fails, check fiber
optic cable connections or the peer optical port.
l If the command output shows that the value of Check Result is Incorrect connections,
exchange the RX branches of the optic fiber cables for the local working channel and
protection channel and then exchange the TX branches in the same way.
l If the command output shows that the value of Check Result is Incorrect TX connection,
correct RX connection, exchange the TX branches of the optic fiber cables for the local
working channel and protection channel.
l If the command output shows that the value of Check Result is Correct TX connection,
incorrect RX connection, exchange the RX branches of the optic fiber cables for the local
working channel and protection channel.
l If the command output shows that the value of Check Result is not of any of the preceding
ones, the conditions for checking fiber optic cable connections are not met. In this case,
troubleshoot according to the command output and run this command again.
Figure 12-3 shows the fiber optic cable connections.
Issue 02 (2013-07-30)

45
BSC6910 UMTS
Commissioning Guide
Figure 12-3 Fiber optic cable connections
----End
12.2.2 Verifying Internal Interfaces

This section describes how to verify whether the internal interfaces are working properly by
checking the status of links to the ports on the SCUb boards.
Prerequisites
l
BSC6910Inter-SCUb network cables have been installed.
Issue 02 (2013-07-30)

46
BSC6910 UMTS
Commissioning Guide
Procedure
Step 1 Run the MML command DSP PANELPORT to query the link status of the ports on the
SCUb boards.
Expected result: The command output shows the actual status of links to the ports on the
SCUb boards.
If the status in the command output does not meet the installation requirements, reinstall the
inter-SCUb network cables by referring to Installing the Inter-SCUb SFP+ High-Speed Cables
Between Different SubracksReinstalling Inter-SCUb Network Cables in the BSC6910 UMTS
Installation Guide.
----End
12.2.3 Verifying the Iub Interface

This section describes how to verify the control plane and user plane on the Iub interface. The
method for verifying the Iub interface varies depending on the transmission mode on the Iub
interface.
Prerequisites
l
The BSC6910 and base station are physically connected and both have passed the hardware
installation acceptance.
The cell under the base station for the Iub interface verification has been configured.
Context
The following takes one base station as an example to describe the verification process on the
Iub interface during the commissioning of the BSC6910. If multiple base stations are connected,
repeat the operations.
Procedure
l
Verifying the Iub Interface (over ATM)

1.
Run the MML command DSP SAALLNK to query the status of a Signaling ATM
Adaptation Layer (SAAL) link.
Expected result: The command output shows that the value of Operation state is
Available.
If the value of Operation state is Unavailable, see 16.1 Checking Transmission
Links for troubleshooting.
2.
Run the MML command DSP UIUBCP to query the status of a link on the Iub
interface.
Available.
If the value of Operation state is Unavailable, see 16.7 Signaling Link Failure on
the Iub Interface for troubleshooting.
Issue 02 (2013-07-30)

47
BSC6910 UMTS
Commissioning Guide
3.
Run the MML command DSP ADJNODE to query the status of an adjacent node.
Available and the values of available bandwidth cannot be all 0.
If the value of Operation state is Unavailable, see ALM-21531 SAAL Link Fault
for troubleshooting. If the value of Operation state is Available and the values of
available bandwidth are all 0, see ALM-21581 Path Fault and ALM-21561 AAL2
Path Blocked for troubleshooting.
4.
Run the MML command DSP AAL2PATH to query the status of an AAL2 path on
the Iub interface.
Available.
If the value of Operation state is not Available, see 16.8 AAL2/IP Connection Setup
Failure for troubleshooting.
5.
Optional: Perform Virtual Connect Link (VCL) continuity check on all the AAL2
paths on the Iub interface. For details, see 16.2 Performing a VCL Continuity
Check.
6.
Optional: Perform permanent virtual channel (PVC) delay test on all the AAL2 paths
on the Iub interface. For details, see 16.3 Verifying the PVC Delay Detection
Function.
7.
Run the MML command DSP UCELL to query the status of a cell.
Expected result: For all the cells, the value of Operational state is Available.
If the value of Operational state is not Available, see 16.6 Cell Setup Failure for
troubleshooting.
Verifying the Iub Interface (over Transmission Resource Pool)

1.
Run the MML command DSP SCTPLNK to query the status of an SCTP link.
Normal.
If the value of Operation state is not Normal, see 16.1 Checking Transmission
NOTE
Run the MML command DSP SCTPLNK for two or three times. If the value of Operation state
is always Normal and the value of State Changed Time does not change, the SCTP link does not
disconnect intermittently.
2.
Run the MML command DSP UIUBCP to query the status of a link on the Iub
interface.
Available.
If the value of Operation state is Unavailable, see 16.7 Signaling Link Failure on
the Iub Interface for troubleshooting.
3.
Run the MML command DSP ADJNODEDIP to query the destination address of an
adjacent node.
Expected result: The command output shows the destination IP address information
of an adjacent node.
Issue 02 (2013-07-30)

48
BSC6910 UMTS
Commissioning Guide
If there is no destination IP address information, the system has not initiated a call.
The verification is complete. You can proceed to query adjacent node Ping detection
status when the cell is set up.
4.
Run the MML command DSP ADJNODEPING to query adjacent node Ping
detection status.
Expected result: The command output shows that the value of Detection Status is
Normal.
If the value of Detection Status is not Normal, see 16.8 AAL2/IP Connection Setup
5.
Run the MML command DSP UCELL to query the status of a cell.
Expected result: For all the cells, the value of Operational state is Available.
If the value of Operational state is not Available, see 16.6 Cell Setup Failure for
troubleshooting.
Verifying the Iub interface (over ATM/IP Dual Stack)

Verify the Iub interface over ATM and over IP, respectively.
----End
12.2.4 Verifying the Iu-CS Interface

This section describes how to verify the control plane and user plane on the Iu-CS interface. The
method for verifying the Iu-CS interface varies depending on the transmission mode on the IuCS interface.
Prerequisites
l
For R99 networking on the Iu-CS interface: the BSC6910 and MSC are been physically
connected, and the MSC is running correctly.
For R4 networking on the Iu-CS interface: the BSC6910, MSC server, and MGW are
physically connected; the transmission links on the interface between the MSC server and
the MGW are correct; the MSC server and the MGW are running correctly.
Verifying the Iu-CS Interface (over ATM)
Procedure
1.
Available.
2.
Run the MML command DSP MTP3LNK to query the status of a Message Transfer
Part Level 3 (MTP3) signaling link.
Available.
Issue 02 (2013-07-30)

49
BSC6910 UMTS
Commissioning Guide
If the value of Operation state is Unavailable, see ALM-21506 MTP3 Signaling

Link Faulty for troubleshooting.
3.
Run the MML command DSP SSN to query the status of a Signaling Connection
Control Part (SCCP) subsystem number (SSN).
Expected result: The command output shows that the value of SSN state is
Allowed.
If the value of SSN state is Prohibited, see ALM-21521 SCCP Subsystem Prohibited
for troubleshooting.
4.
Run the MML command DSP N7DPC to query the status of an SS7 destination
signaling point.
Expected result: The command output shows that the value of SCCP DSP state is
Accessible.
If the value of SCCP DSP state is not Accessible, see ALM-21521 SCCP Subsystem
Prohibited for troubleshooting.
5.
If the value of Operation state is Unavailable, see ALM-21562 QAAL2 Adjacent
Node Inaccessible for troubleshooting. If the value of Operation state is Available
and the values of available bandwidth are all 0, see ALM-21581 Path Fault and
ALM-21561 AAL2 Path Blocked for troubleshooting.
6.
Run the MML command LST UCNNODE to check whether the CN node in the CS
domain is configured.
Expected result: The command output shows that the value of CN Domain ID is
CS_DOMAIN.
If Corresponding results not found is returned or the value of CN Domain ID is
not CS_DOMAIN, Run the MML command ADD UCNNODE to configure the
corresponding CN node.
7.
the Iu-CS interface.
Available.
8.
Optional: Perform virtual channel link (VCL) continuity check on all the AAL2 paths
on the Iu-CS interface. For details, see 16.2 Performing a VCL Continuity Check.
9.
Optional: Perform permanent virtual channel (PVC) delay test on all the AAL2 paths
on the Iu-CS interface. For details, see 16.3 Verifying the PVC Delay Detection
Function.
Verifying the Iu-CS Interface (over Transmission Resource Pool)

1.
Normal.
Issue 02 (2013-07-30)

50
BSC6910 UMTS
Commissioning Guide
NOTE
2.
Run the MML command DSP M3LNK to query the status of an M3UA link.
Active.
If the value of Operation state is not Active, see ALM-21551 M3UA Link Fault for
troubleshooting.
3.
Run the MML command DSP SSN to query the status of an SCCP SSN.
Allowed.
4.
signaling point.
Accessible.
5.
Run the MML command DSP ADJNODEDIP to query the destination IP address
information of an adjacent node.
If there is no destination IP address information, the system has not initiated a call.
The verification is complete. You can proceed to query adjacent node Ping detection
status when the call is initiated.
6.
detection status.
Normal.
7.
Run the MML command LST UCNNODE to check whether the CN node in the CS
domain is configured.
CS_DOMAIN.
not CS_DOMAIN, Run the MML command ADD UCNNODE to configure the
----End
Issue 02 (2013-07-30)

51
BSC6910 UMTS
Commissioning Guide
12.2.5 Verifying the Iu-PS Interface

This section describes how to verify the control plane and user plane on the Iu-PS interface.
Prerequisites
l
The BSC6910 and SGSN are physically connected and both have passed the hardware
The SGSN used to verify the Iu-PS interface is operating correctly.
Verifying the Iu-PS Interface (over Transmission Resource Pool)
Procedure
1.
Run the MML command DSP SCTPLNK to query the status of a Stream Control
Transmission Protocol (SCTP) link.
Normal.
NOTE
2.
Run the MML command DSP M3LNK to query the status of an MTP3-User
Adaptation Layer (M3UA) link.
Active.
troubleshooting.
3.
Allowed.
4.
signaling point.
Accessible.
5.
Issue 02 (2013-07-30)
Run the MML command DSP ADJNODEDIP to query the destination IP address
information of an adjacent node.
52
BSC6910 UMTS
Commissioning Guide
Expected result: The command output shows that the destination IP address
information of an adjacent node is returned.
If there is no destination IP address information, the system has not started a data
service. The verification is complete. You can proceed to query adjacent node Ping
detection status when the data service is started.
6.
detection status.
Normal.
7.
Run the MML command LST UCNNODE to check whether the CN node is
configured in the PS domain.
PS_DOMAIN.
not PS_DOMAIN, Run the MML command ADD UCNNODE to configure the
----End
12.2.6 Verifying the Iur Interface

This section describes how to verify the control plane and user plane on the Iur interface when
the BSC6910 is connected to the RNC. The method for verifying the Iur interface varies
depending on the transmission mode.
Prerequisites
l
The BSC6910 and RNC are physically connected and both have passed the hardware
The RNC used to verify the Iur interface is operating correctly.
Context
Before performing this task, ensure that the RNC at the other end on the Iur interface is
commissioned.
Procedure
l
Verifying the Iur Interface (over ATM)

1.
Available.
Issue 02 (2013-07-30)

53
BSC6910 UMTS
Commissioning Guide

Links.
2.
Run the MML command DSP MTP3LNK to query the status of a Message Transfer
Part Level 3 (MTP3) signaling link.
Available.
If the value of Operation state is Unavailable, see ALM-21506 MTP3 Signaling
Link Faulty for troubleshooting.
3.
Allowed.
4.
signaling point.
Accessible.
5.
If the value of Operation state is Unavailable, see ALM-21562 QAAL2 Adjacent
Node Inaccessible for troubleshooting. If the value of Operation state is Available
and the values of available bandwidth are all 0, see ALM-21581 Path Fault and
ALM-21561 AAL2 Path Blocked for troubleshooting.
6.
the Iur interface.
Available.
Verifying the Iur Interface (over Transmission Resource Pool)

1.
Normal.
Links.
Issue 02 (2013-07-30)

54
BSC6910 UMTS
Commissioning Guide
NOTE
2.
Run the MML command DSP M3LNK to query the status of an M3UA link.
Active.
troubleshooting.
3.
Allowed.
4.
signaling point.
Accessible.
5.
Run the MML command DSP ADJNODEDIP to query the destination address of an
adjacent node.
If there is no destination IP address information, the system has not started an Iur
handover. The verification is complete. You can proceed to query adjacent node Ping
detection status when the Iur handover is started.
6.
detection status.
Available.
If the value of Detection Status is Unavailable, see 16.8 AAL2/IP Connection Setup
----End
12.2.7 Verifying the Iu-BC Interface

This section describes how to verify that the user plane of the Iu-BC interface is operational.
The Iu-BC interface verification is mandatory when UMTS cell broadcast services (CBSs) are
supported.
Issue 02 (2013-07-30)

55
BSC6910 UMTS
Commissioning Guide
Prerequisites
l
The BSC6910 and CBC have been physically connected, and both have passed the hardware
Procedure
Step 1 Query the connectivity between the BSC and CBC, run the PING IP command. In this command,
set Source IP Address to the IP address of the Iu-BC interface board at the local end and set
Target IP Address to the IP address of the CBC server at the peer end.
Expected result: The CBC server can be pinged.
If the CBC server cannot be pinged, check whether a firewall is configured at the peer end. If a
firewall does not exist, check whether the IP addresses and route on the BSC6910 and CBC are
correctly configured.
----End
12.2.8 Verifying the Iur-g Interface

This section describes how to verify the Iur-g interface when the BSC connects to the RNC or
when BSCs connect to each other. The method for verifying the Iur-g interface varies depending
on the Iur-g configuration.
Prerequisites
l
The BSC6910 and peer NE are physically connected and both have passed the hardware
The RNC used to verify the Iur-g interface is operating correctly.
Verifying the Iur-g interface (intra-RNC)
Procedure
1.
Run the DSP BRD command to query the status of a board.

Expected result: The command output shows that the value of CPU status is Active
normal.
If the value of CPU status is not Active normal, see ALM-20242 Board Subsystem
Unavailable for troubleshooting.
Verifying the Iur-g interface (inter-RNC)

1.
Run the MML command DSP SCTPLNK to query the status of a Stream Control
Transmission Protocol (SCTP) link.
Expected result: The value of Operation state is Normal.
If the value of Operation state is not Normal, see operations in 16.1 Checking
Transmission Links.
Issue 02 (2013-07-30)

56
BSC6910 UMTS
Commissioning Guide
NOTE
2.
Run the MML command DSP M3LNK to query the status of an MTP3-User
Adaptation Layer (M3UA) link.
Expected result: The value of Operation state is Active.
troubleshooting.
3.
Allowed.
4.
signaling point.
Accessible.
----End
12.2.9 Verifying the Iur-p Interface

This section describes how to verify the Iur-p interface when RNC in Pool is applied.
Prerequisites
l
BSC6910 and BSC6900 are physically connected and both have passed the hardware
The BSC6900 or BSC6910 used to verify the Iur-p interface is operating correctly.
Procedure
Step 1 Run the MML command DSP IURPLKS and specify External Node Id. to query the status of
an Iur-p link set of the external node.
Expected result: Values of Number of IURP Link on Fault Subsystem, Number of IURP
Link on Invalid Subsystem, and Number of Fault IURP Link are all 0s.
If the value of Number of IURP Link on Fault Subsystem is not 0, run the MML command
RMV IURPLKS to remove the Iur-p link set of the external node and then run the MML
command ADD IURPLKS to add a new Iur-p link set to the external node.
If the value of Number of IURP Link on Invalid Subsystem is not 0, the number of Iur-p links
exceeds the RNC capability. In this case, run the MML command MOD IURPLKS to modify
Issue 02 (2013-07-30)

57
BSC6910 UMTS
Commissioning Guide
the number of Iur-p links in the link set. Alternatively, run the MML command RMV
IURPLKS to remove a link set so that the number of Iur-p links can be decreased to be within
RNC capability.
NOTE
l The RNC's capability for supporting Iur-p links depends on the capabilities of configured boards on the
control plane (CP) and their numbers. When RNC in Pool is applied with two RNCs pooled, the maximum
number of Iur-p links supported in an RNC pool depends on the pooled RNC whose capability for supporting
Iur-p links is lower.
For example, in an RNC pool with two RNCs pooled, if RNC 1 supports four Iur-p links and RNC 2 supports
six Iur-p links, the RNC pool can support a maximum of four Iur-p links and the excessive two Iur-p links
on RNC 2 become faulty.
l The number of Iur-p links supported by the EGPUa board (logical function type: UCUP) and an external
node depends on the board's CP processing capability. You can run the MML command LST
UCPUPFLEXCFG to obtain CP processing capability of a board. If CP PROPORTION IN TOTAL is
100%, the EGPUa board (logical function type: UCUP) supports 56 Iur-p links. The number of Iur-p links
supported by the RNC can be calculated in the following formula: Number of Iur-p links supported by an
external node = Number of EGPUa boards (logical function type: UCUP) 56 CP proportion in total.
If the value of Number of Fault IURP Link is not 0, see ALM-21606 IURP Link Fault for
troubleshooting.
----End
Issue 02 (2013-07-30)

58
BSC6910 UMTS
Commissioning Guide
13
13 Handling the Alarms Generated During the

Commissioning
Handling the Alarms Generated During

the Commissioning
This section describes how to handle the alarms generated during the commissioning to prevent
the alarms from affecting service verifications.
Prerequisites
l
The communication between the BSC6910 and OMU is normal.
Procedure
Step 1 Click Alarm/Event on the LMT home page. The BSC6910 Alarm/Event tab page is displayed.
Step 2 Check whether any active alarm exists on the Normal Alarm tab page.
If...
Then...
No active alarm is listed
End this task.
One or more active alarms are listed
Go to Step 3.
Step 3 Double-click the active alarm to be handled on the Normal Alarm tab page. The Detailed
Information dialog box is displayed.
Step 4 Click Solution. The Online Help page is displayed.
Step 5 Follow the suggestions to handle the alarm.
Step 6 Repeat steps Step 3 through Step 5 to handle other alarms.
----End
Issue 02 (2013-07-30)

59
BSC6910 UMTS
Commissioning Guide
14
Verifying UMTS Services
This section describes how to verify that the UMTS basic services and the feature services that
are enabled are normal. The basic UMTS services are voice service, CS streaming service, PS
service, and mobility management service. The feature services include inter-RAT handovers,
HSDPA, HSUPA, 64QAM, MIMO, and DC-HSDPA.
Prerequisites
l
The BSC6910 has passed the commissioning.
The commissioning over the Iub, Iu-CS, Iu-PS, Iur, Iu-BC, Iur-g, and Iur-pinterfaces is
successful. The commissioning over the Iur interface is mandatory only when the
BSC6910 is connected to the RNC.
The test UEs are functional and have registered with the HLR.
Procedure
Step 1 Table 14-1 lists the operations for verifying basic UMTS services with test UEs in NodeB cells.
Table 14-1 Operations for verifying basic UMTS services with test UEs in NodeB cells
Issue 02 (2013-07-30)
Service Type
Operation
Expected Result
Speech service
Make 20 calls from a test UE

to a fixed-line phone and hold
on each call for 60 seconds.
The connection success rate

is higher than 95%. The voice
is clear without loud noise.
No call drop occurs and the
system resources are released
normally after the call is
terminated.
Make 20 calls from a fixedline phone to a test UE and

hold on each call for 60
seconds.

terminated.

60
BSC6910 UMTS
Commissioning Guide
Service Type
Data Service
Operation
Expected Result

to another test UE and hold

terminated.
Use a test UE to make two

video calls to another test UE.
The sound is clear, the video

is continuous, and the voice
is synchronous with the
video.
Perform a soft handover on

the CS voice service of 20 test
UEs.
The handover success rate is

higher than 95%.
Activate the 384 kbit/s

service. Use a test UE to
browse web pages through
the web browser 20 times.
The activation success rate is

higher than 95% and you can
browse the web page
normally.

the web browser. Perform 20
soft handovers for the PS
service.

higher than 95%.
NOTE
If service verification results cannot meet expected results, start the following tracing tasks: Uu Interface
Trace, Iu Interface Trace, Iub Interface Trace, Iur Interface Trace (mandatory only in inter-RNC handover),
UE Trace, and Cell Trace.
Step 2 Table 14-2 lists the operations for verifying feature services with the test UEs in NodeB cells.
Table 14-2 Operations for verifying feature services with test UEs in NodeB cells
Issue 02 (2013-07-30)
Service Type
Operation
Expected Result
Inter-RAT handover
Hand over a dual-mode test

UE from UMTS to GSM for
20 times on CS and PS
services respectively. Hand
over a dual-mode test UE
from GSM to UMTS for 20
times on CS and PS services,
respectively.

higher than 90%. For CS
services, the voice is clear
without loud noise; For PS
service, no call drop occurs.

61
BSC6910 UMTS
Commissioning Guide
Service Type
Operation
Expected Result
High Speed Downlink Packet

Access (HSDPA)
Activate the high-speed PS

access the FTP server and
download large files for 10
times. The assigned
downlink data rate of
services must be higher than
384 kbit/s.

higher than 90% and the
downloading is normal.
High Speed Uplink Packet

Access (HSUPA)

upload large files for 10
times. The assigned uplink
rate of services is required to
be over 384 kbit/s.

uploading is normal.
64QAM

times. The assigned
384 kbit/s.

Multiple Input Multiple

Output (MIMO) service

times. The assigned
384 kbit/s.

DC-HSDPA (Dual-Carrier
High Speed Downlink Packet
Access) service

times. The assigned
384 kbit/s.

Cell broadcast service (CBS)
Use the cell broadcast center

(CBC) to send CBS short
messages. Enable the UE to
receive these messages.
Repeat this operation 10
times.
The UE successfully receives

correct CBS short messages.
----End
Issue 02 (2013-07-30)

62
BSC6910 UMTS
Commissioning Guide
15
Verifying Network Reliability
The network reliability can be verified after you switch over active and standby boards, check
generated alarms, and making dialing tests.
Prerequisites
l
The standby board to be switched over is operating correctly.
The alarms generated before the switchover have been cleared.
Procedure
Step 1 Run the MML command SWP BRD to switch over the BSC boards.
Step 2 Check and handle the alarms generated during the switchover. For details, see 13 Handling the
Alarms Generated During the Commissioning.
Step 3 Use a UE in a cell under the NodeB to perform basic services and check whether services are
going on properly. For details, see Table 15-1.
Table 15-1 Operations for verifying basic UMTS services with test UEs in NodeB cells
Issue 02 (2013-07-30)
Service Type
Operation
Expected Result
Speech service

to a fixed-line phone and hold

terminated.

63
BSC6910 UMTS
Commissioning Guide
Service Type
Data Service
Operation
Expected Result
Make 20 calls from a fixedline phone to a test UE and

hold on each call for 60
seconds.

terminated.

to another test UE and hold

terminated.
Use a test UE to make two

video calls to another test UE.
The sound is clear, the video

is continuous, and the voice
is synchronous with the
video.
Perform a soft handover on

the CS voice service of 20 test
UEs.

higher than 95%.

the web browser 20 times.

higher than 95% and you can
browse the web page
normally.

the web browser. Perform 20
soft handovers for the PS
service.

higher than 95%.
----End
Issue 02 (2013-07-30)

64
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
16
Troubleshooting
About This Chapter

This chapter describes how to troubleshoot common problems during the commissioning.
16.1 Checking Transmission Links
This section describes how to verify that terrestrial transmission links of the BSC6910 are
functional. The verification covers E1/T1 ports, FE/GE ports, optical ports, and upper-layer
links.
16.2 Performing a VCL Continuity Check
This section describes how to perform a virtual channel link (VCL) continuity check on links
over interfaces.
16.3 Verifying the PVC Delay Detection Function
This section describes how to check whether the permanent virtual connection (PVC) delay
detection function is operational in ATM transmission mode.
16.4 Unavailable E1/T1 Port
This section describes how to troubleshoot an unavailable E1/T1 port.BSC6910 only support
the E1/T1 over SDH mode.
16.5 Unavailable FE/GE Port
This section describes how to troubleshoot an unavailable FE/GE port.
16.6 Cell Setup Failure
This section describes how to handle cell setup failures.
16.7 Signaling Link Failure on the Iub Interface
This section describes how to troubleshoot a signaling link failure on the Iub interface.
16.8 AAL2/IP Connection Setup Failure
This section describes how to troubleshoot an AAL2/IP connection setup failure.
16.9 Data Loading Failures on the Board
This section describes how to troubleshoot failures that occur during data loading to a
BSC6910 board.
16.10 Performing a Loopback Test on an Optical Port
Issue 02 (2013-07-30)

65
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
This section describes how to perform the group loopback test to check whether an optical port
is functional.
Issue 02 (2013-07-30)

66
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
16.1 Checking Transmission Links

This section describes how to verify that terrestrial transmission links of the BSC6910 are
functional. The verification covers E1/T1 ports, FE/GE ports, optical ports, and upper-layer
links.
Prerequisites
l
Check the status of physical transmission links based on the transmission scheme.
Procedure
Table 16-1 Methods for checking the status of transmission links based on the transmission
scheme
If the transmission scheme on the
interface is...
Then...
AT
M
1. Check the status of an optical

port.
IMA/UNI/FRA
2. Check the status of an E1/T1

port.
3. Check the status of an upper-layer
link.
l For the IMA transmission
mode, run the MML command
DSP IMAGRP to check the
status of an IMA group.
l For the UNI transmission
DSP UNILNK to check the
status of a UNI link.
l For the FRA transmission
DSP FRALNK to check the
status of a fractional IMA/
ATM link.
NOTE
If the upper-layer link is not
functional, run the MML
command LST IMAGRP, LST
UNILNK, or LST FRALNK to
check whether the data
configuration on the interface is
correct.
NCOPT
Issue 02 (2013-07-30)
Check the status of an optical

port.

67
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
If the transmission scheme on the

interface is...
Then...
IP
Check the status of an FE/GE

port.
IP over Ethernet
If the port is operating properly, run

the MML commands PING IP and
TRC IPADDR to check the status of
the link connecting the local end to
the peer end.
l
Check the status of an E1/T1 port.

1.
Run the MML command DSP E1T1 to query the status of an E1/T1 port.
Expected result: The Port running state of the associated E1/T1 port is Port
available.
If the value of the Port running state is Port is down, see 16.4 Unavailable E1/T1
Port for troubleshooting.
Check the status of an FE/GE port.

1.
Run the MML command DSP ETHPORT to query the status of the Ethernet port.
Expected result: The value of Link Availability Status is Available.
If either of the following cases occurs, see 16.5 Unavailable FE/GE Port for
troubleshooting.
The value of Link Availability Status is Unavailable.
The value of Port state is Deactivated.
2.
Optional: Check the connectivity of the gateway (this operation is mandatory if threelayer networking applies).
a.
Run the MML command LST IPCHK to query the configuration of the gateway
continuity check.
b.
Run the MML command STR IPCHK to start the gateway continuity check.
NOTE
If the BFD function is supported by and enabled at the peer router, set Check type to SBFD.
Otherwise, set it to ARP.
c.
On the alarm tab page of the LMT, check whether ALM-21346 IP Connectivity
Check Failure is reported. If yes, clear the alarm according to the alarm handling
suggestions.
d.
Optional: To keep the gateway continuity check, end the check task; otherwise,
run the MML command STP IPCHK to stop the gateway continuity check.
Checking the status of an optical port

1.
Run the MML command DSP OPT to query the status of an optical port.
Expected result: The value of Optical port state is Available.
If the value of Optical port state is not Available, check the alarms related to the
optical port and rectify the fault according to the handling suggestions in the online
alarm reference.
----End
Issue 02 (2013-07-30)

68
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
16.2 Performing a VCL Continuity Check

This section describes how to perform a virtual channel link (VCL) continuity check on links
over interfaces.
Prerequisites
l
The peer end (NodeB, MGW, MSC, or SGSN) supports the F5 protocol.
Context
Only the VCLs that carry the SAAL link, IPoA PVC, or AAL2 path supports the continuity
check.
Procedure
l
Perform a continuity check on the SAAL link.

1.
Run the MML command ACT VCLCC to activate the continuity check on the VCL.
In this step, set Link type to SAALLNK, VCL act type to CC, and Activation
direction to BOTH.
2.
Run the MML command DSP VCLCC, and then set Link type to SAALLNK to
query the result of the continuity check on the VCL.
Expected result: The values of LOC alarm, AIS alarm, RDI alarm, CC activated
failure alarm, and LB failure alarm are all Normal.
If the value of any of these parameters is not Normal, check whether the following
alarms are reported. If yes, rectify the fault following the alarm handling suggestions.
ALM-21321 VCL CC Detection Failure
ALM-21322 VCL Alarm Indication Signal
ALM-21323 VCL Remote Alarm Indication
ALM-21324 VCL CC Activation Failure
ALM-21326 VCL LB Detection Failure
3.
Optional: To keep the VCL continuity check running, no action is required. To

terminate the VCL continuity check, run the MML command DEA VCLCC with
Link type set to SAALLNK.
Perform a continuity check on the AAL2 path.

1.
Run the MML command ACT VCLCC, and then set Link type to AAL2PATH,
VCL act type to CC, and Activation direction to BOTH to activate the continuity
check on the VCL.
2.
Run the MML command DSP VCLCC, and then set Link type to AAL2PATH to
query the result of the continuity check on the VCL.
Issue 02 (2013-07-30)

69
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting

3.

Link type set to AAL2PATH.
Perform a continuity check on the IPoA PVC.

1.
Run the MML command ACT VCLCC, and then set Link type to IPOAPVC, VCL
act type to CC, and Activation direction to BOTH to activate the continuity check
on the VCL.
2.
Run the MML command DSP VCLCC, and then set Link type to IPOAPVC to query
the result of the continuity check on the VCL.
3.

Link type set to IPOAPVC.
----End
16.3 Verifying the PVC Delay Detection Function

This section describes how to check whether the permanent virtual connection (PVC) delay
detection function is operational in ATM transmission mode.
Prerequisites
l
The peer end (NodeB, MGW, MSC, or SGSN) supports the F5 protocol.
Only VCLs that carry the SAAL link, IPoA PVC, or AAL2 path supports the PVC delay
test.
The PVC delay for a maximum of six links can be detected on the LMT because only six
link performance monitoring tasks can be started simultaneously.
Context
Issue 02 (2013-07-30)

70
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
Procedure
l
Verify the PVC delay detection function on the SAAL link.

1.
Run the MML command LOP VCL to perform a single PVC loopback test. In this
step, set Link type to SAALLNK.
Expected result: The PVC loopback delay is displayed.
2.
Run the MML command ACT VCLCC to activate the VCL loopback test.
Set Link type to SAALLNK.
Set VCL act type to LOOPBACK.
3.
Run the MML command DSP VCLCC to query the Average Time Delay, Max Time
Delay, and Min Time Delay in the VCL loopback test results. In this step, set Link
type to SAALLNK
Expected result: The following information is displayed:
Average Time Delay[ms]
Max Time Delay[ms]
Min Time Delay[ms]
4.
Enable the PVC link performance monitoring function on the LMT.

a.
Click Monitor on the LMT main page. The Monitor tab page is displayed.
b.
In the Monitor Navigation Tree, expand Monitor > Common Monitoring and
double-click Link Performance Monitoring.
c.
In the displayed Link Performance Monitoring dialog box, set Monitor

Item to SAAL Link, and click Start.
Expected result: The delay of the link being monitored is dynamically displayed in
the Link Performance Monitoring dialog box.
5.
Optional: To keep the PVC delay test running, no action is required. To terminate
the PVC delay test, run the MML command DEA VCLCC with Link type set to
SAALLNK.
Perform the PVC delay test on the AAL2 path.

1.
Run the MML command LOP VCL and then set Link type to AAL2PATH to
perform a single PVC loopback test.
2.
Run the MML command ACT VCLCC and then set Link type to AAL2PATH,
VCL act type to LOOPBACK, Activation direction to BOTH to activate the VCL
loopback test.
3.
Run the MML command DSP VCLCC and then set Link type to AAL2PATH to
query the Average Time Delay, Max Time Delay, and Min Time Delay in the VCL
loopback test results.
Max Time Delay[ms]
Min Time Delay[ms]
4.
Issue 02 (2013-07-30)
Enable the function of monitoring the real-time performance of the PVC link through
the LMT.
71
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
a.
b.
c.

Item to AAL2 PATH and click Start.
5.
AAL2PATH.
Perform the PVC delay test on the IPoA PVC.

1.
Run the MML command LOP VCL and then set Link type to IPOAPVC to perform
a single PVC loopback test.
2.
Run the MML command ACT VCLCC and then set Link type to IPOAPVC, VCL
act type to LOOPBACK, and Activation direction to BOTH to activate the VCL
loopback test.
3.
Run the MML command DSP VCLCC and then set Link type to IPOAPVC to query
the Average Time Delay, Max Time Delay, and Min Time Delay in the VCL loopback
test results.
Max Time Delay[ms]
Min Time Delay[ms]
4.
Enable the function of monitoring the real-time performance of the PVC link through
the LMT.
a.
b.
c.

Item to IPOA PVC and click Start.
5.
IPOAPVC.
----End
16.4 Unavailable E1/T1 Port

This section describes how to troubleshoot an unavailable E1/T1 port.BSC6910 only support
the E1/T1 over SDH mode.
Issue 02 (2013-07-30)

72
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
Fault Description
When you run the MML command DSP E1T1 to check the status of E1/T1 ports, Port running
state in the returned result is Port is down.
Solution
1.
If Port running state is Port is down, perform the group loopback test on all the faulty
E1/T1 ports because only optical ports serve as the bearers on the BSC6910. For details,
see 16.10 Performing a Loopback Test on an Optical Port.
2.
Check whether the following alarms are listed on the alarm tab page on the LMT. If any
of the alarms exists, handle them according to the suggestions in online alarm reference.
l ALM-21294 SDH/SONET TU Signal Loss
l ALM-21261 SDH/SONET LP Remote Defect Indication
l ALM-21275 SDH/SONET Tributary Loss of Frame
l ALM-21286 SDH/SONET Tributary Remote Alarm Indication Signal
l ALM-21288 SDH/SONET Tributary Loss of Multiframe
l ALM-21287 SDH/SONET Tributary Alarm Indication Signal
NOTE
When you run the MML command DSP E1T1 to check the E1/T1 port status, if Is this E1/T1
occupied is set to NO, the link is still available even though the ALM-21261 SDH/SONET LP
Remote Defect Indication exists.
16.5 Unavailable FE/GE Port

This section describes how to troubleshoot an unavailable FE/GE port.
Fault Description
When you run the MML command DSP ETHPORT to check the status of the FE/GE port, one
of the following events occurs exists:
l
The value of Link Availability Status is Unavailable.
The value of Port state is Deactivated.
1.
If the value of Link Availability Status is Unavailable, check the connection of the
network cable and check whether the peer network interface is enabled. See the online
alarm reference for the alarm handling suggestions.
2.
If the value of Port state is Deactivated, run the MML command ACT ETHPORT to
activate the FE/GE port.
Solution
16.6 Cell Setup Failure

This section describes how to handle cell setup failures.
Issue 02 (2013-07-30)

73
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
Fault Description
During the verification of cell setups, the final result is not as expected. The operation state of
the cell is Unavailable and the Iub interface tracing fails to trace the complete cell setup
procedure on the Iub interface.
Fault Locating Policy
CAUTION
l If Iub over ATM is applied, check whether the alarms related to the EGPUa, UUP, SAAL
link, IMA, optical port, or AAL2 exist in the alarm management system when cell setup
failure occurs. If such alarms exist, handle the alarms as suggested. If the alarms persist,
handle them as follows:
l If Iub over IP is applied, check whether the alarms related to the EGPUa, UUP, or SCTP link
exist in the alarm management system when cell setup failure occurs. If such alarms exist,
handle the alarms as suggested. If the alarms persist, handle as follows:
l If Iub over ATM/IP dual-stack is applied, check whether the alarms related to the EGPUa,
UUP, SAAL link, SCTP link, IMA, optical port, or AAL2 exist in the alarm management
system when cell setup failure occurs. If such alarms exist, handle the alarms as suggested.
If the alarms persist, handle as follows:
To narrow down the fault location, determine whether the NodeB or the BSC6910 is faulty by
comparing the results of the Iub interface message tracing results with those expected in normal
working condition. Then, further locate the fault using other methods.
Figure 16-1 and Figure 16-2 show the procedures for locating cell setup failures.
Issue 02 (2013-07-30)

74
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
Figure 16-1 Locating cell setup failures (1)
Table 16-2 Operation index (1)
Issue 02 (2013-07-30)
Index
Operation
Step
*1-1
Check whether the Iub link

works properly.
See 16.1 Checking Transmission

Links.
*1-2
Handle link failures on the Iub

interface.
See 16.7 Signaling Link Failure on the

Iub Interface.

75
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
Index
Operation
Step
*1-3
Check whether the audit

response message is correct.
See Solution 1: Checking the Audit

Response Message.
*1-4
Unblock the cell.
See Solution 2: Unblocking Cells.
*1-5
Change the configured

maximum downlink transmit
power based on the reporting
ability of the NodeB.
See Solution 3: Changing the

Configured Maximum Downlink
Transmit Power Based on the
Reporting Ability of the NodeB.
*1-6
Check whether the UUP

resources are available.
On the ALM tab on the LMT, check

whether the active alarm ALM-22208
UMTS Cell Common Channel Setup
Failed exists and that Alarm Cause is L2
resource allocate failure. If both are
correct, the UUP resources are
insufficient in the cell.
*1-7
Check whether the TNL

resources are available.
See Solution 6: Checking TNL

Resources.
Figure 16-2 Locating cell setup failures (2)
Issue 02 (2013-07-30)

76
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting

Index
Operation
Step
*2-1
Check whether the PRACH

setup response message is
correct.
See Solution 4: Checking the PRACH

Setup Response Message.
*2-2
Check whether the Iub link

works properly.
See 16.1 Checking Transmission

Links.
*2-3
Handle link failures on the Iub

interface.
See 16.7 Signaling Link Failure on the

Iub Interface.
*2-4
Check whether the AAL2/IP

link setup is successful.
l For ATM transmission, check

whether the AAL2 link setup is
successful.
1. Run the MML command DSP
AAL2PATH to query the status of
the AAL2 path.
2. Perform the VCL continuity check
on all the AAL2 paths. For details,
see 16.2 Performing a VCL
Continuity Check.
l For IP transmission, check whether
the IP link setup is successful.
Run the MML command DSP
ADJNODE to query the status of an
adjacent node.
*2-5
Handle the AAL2/IP link setup

failures.
See 16.8 AAL2/IP Connection Setup

Failure.
*2-6
Check whether the SCCPCH

setup response message is
correct.
See Solution 5: Checking the SCCPCH

Setup Response Message.
Solution 1: Checking the Audit Response Message

Start the Iub interface tracing to check the audit response message of the NodeB. The
requirements for correct audit response messages of the NodeB are as follows:
l
Each cell has the associated LocalCell.
If LocalCell is configured to belong to a LocalCellGroup, the associated LocalCellGroup

exists.
Solution 2: Unblocking Cells

l
If the cell is blocked by the BSC6910, run the MML command UBL UCELL to unblock
the cell.
If the cell is blocked by the NodeB, contact the NodeB maintenance personnel for
troubleshooting.
Issue 02 (2013-07-30)

77
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
Solution 3: Changing the Configured Maximum Downlink Transmit Power Based

on the Reporting Ability of the NodeB
Run the MML command LST UCELL to query Maximum Downlink Transmit Power
(MAXTXPOWER) of the cell configured in the database. The value should not be greater than
the value of Maximum DL Power Capability (MAXTXPOWER) in the audit response
message.
If the value is greater than the value of Maximum DL Power Capability (MAXTXPOWER), run
the MML command MOD UCELL to change the cell maximum transmit power or request that
the NodeB change the maximum downlink transmit power.
Solution 4: Checking the PRACH Setup Response Message

The requirements for the correct PRACH setup response message are as follows:
l
The RachInfo, TranspLayerAddr, and BindingId parameters have been assigned values.
The transport channel ID of the RACH displayed in the messages should be the same as
that configured in the database.
The value of the TranspLayerAddr parameter in the message is the same as that in the
database.
NOTE
When the user plane is over ATM transmission, the value of the TranspLayerAddr parameter is the ATM
address. Run the MML command LST UNODEB to check whether the configured ATM address is consistent
with that in the PRACH setup response message.
When the user plane is over IP transmission, the value of the TranspLayerAddr parameter is the IP address.
You do not need to check whether the peer IP address (that is, the IP address of the NodeB user plane) configured
is consistent with that in the PRACH setup response message because it does not need to be configured on the
BSC6910.
Solution 5: Checking the SCCPCH Setup Response Message

The requirements for the correct SCCPCH setup response message are as follows:
l
The FachInfo, PchInfo, TranspLayerAddr, and BindingId parameters have been

assigned values.
The transport channel ID of the FACH or PCH displayed in the messages should be the
same as that configured in the database.
The value of the TranspLayerAddr parameter in the message is the same as that in the
database.
NOTE
When the user plane is over ATM transmission, the value of the TranspLayerAddr parameter is the ATM
address. Run the MML command LST UNODEB to check whether the ATM address configured is consistent
with that in the SCCPCH setup response message.
When the user plane is over IP transmission, the value of the TranspLayerAddr parameter is the IP address.
You do not need to check whether the peer IP address (that is, the IP address of the NodeB user plane) configured
is consistent with that in the SCCPCH setup response message because it does not need to be configured on the
BSC6910.
Issue 02 (2013-07-30)

78
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
Solution 6: Checking TNL Resources

1.
Run the MML command LST ADJNODE to check whether the adjacent node is
configured. If the adjacent node is not configured, run the MML command ADD
ADJNODE to configure the adjacent node.
2.
In ATM transmission mode, run the MML command LST AAL2PATH to check the
configuration of the AAL2 path of the adjacent node.
3.
In IP Pool mode, run the MML command DSP IPPOOLPM to check the IP status of the
adjacent node.
4.
Run the MML command LST TRMMAP to check whether the AAL2 path mapped by the
R99 RT service (service type of the common channel) exists and whether the bandwidth
meets the requirements of the common channel. If the AAL2 path does not exist, add the
associated AAL2 path. If the bandwidth does not meet the requirements of the common
channel, add an AAL2 path or modify the configuration of the AAL2 path.
16.7 Signaling Link Failure on the Iub Interface

This section describes how to troubleshoot a signaling link failure on the Iub interface.
Fault Description
During cell setup, a signaling link on the Iub interface is faulty. The NBAP_AUDIT_REQ
message cannot be traced on the Iub interface. The alarms related to the EGPUa/UUP board are
not reported.
Solution
1.
Issue 02 (2013-07-30)
For Iub over ATM transmission, check whether alarms related to the E1/T1 port, FE/GE
port, SAAL link, IMA, UNI, NCP, or CCP are reported. If the alarms are reported, handle
them according to the suggestions in the online alarm reference. If the alarms persist, handle
them according to Figure 16-3.

79
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
Figure 16-3 Troubleshooting signaling link failures on the Iub interface over ATM transmission
Issue 02 (2013-07-30)
Index
Operation
Step
*1-1
Add upper-layer
applications to the
SAAL link.
Run the MML commands ADD UNCP, ADD

UCCP, and ADD ADJNODE to add NCP, CCP, and
ALCAP, respectively.
*1-2
Troubleshoot
physical connection
failures.
See 16.4 Unavailable E1/T1 Port.

80
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
Index
Operation
Step
*1-3
Check the data

configuration.
Perform the following steps:

1. Run the MML command LST SAALLNK to
check whether negotiated data configurations are
consistent between the two ends of the SAAL link.
l If they are inconsistent, go to *1-4.
l If they are consistent, go to the next step shown
in Figure 16-3.
2. Run the MML command LST E1T1 to check the
coding schemes are consistent between the two
ends.
in Figure 16-3.
3. Run the MML command LST IMAGRP to check
the IMA protocol version configurations are
consistent between the two ends.
in Figure 16-3.
*1-4
Modify data
configuration.
1. Run the MML command MOD SAALLNK to

modify the configuration on the SAAL link.
2. Run the MML command SET E1T1 to change the
E1/T1 coding scheme as negotiated.
3. Run the MML command MOD IMAGRP to
change the IMA protocol version as negotiated.
2.
Issue 02 (2013-07-30)
For Iub over IP transmission, check whether alarms related to the FE/GE port, SCTP link,
NCP, CCP are reported. If the alarms are reported, handle them according to the suggestions
in the online alarm reference. If the alarms persist, handle them according to Figure
16-4.

81
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
Figure 16-4 Handling of signaling link failures on the Iub interface over IP transmission
3.
Issue 02 (2013-07-30)
Index
Operation
Step
*2-1
Check whether the

SCTP link works
properly.
Run the MML command DSP SCTPLNK to check

whether the SCTP link works properly.
*2-2
Add upper-layer
applications to the
SCTP link.
Run the MML commands ADD UNCP and ADD

UCCP to add upper-layer applications to the SCTP
link.
*2-3
Check whether the

transmission link is
available.
See 16.1 Checking Transmission Links.
*2-4
Handle the
transmission link
failure.
See 16.5 Unavailable FE/GE Port.
*2-5
Check the data

configuration.
Run the MML LST SCTPLNK command to check

the consistency of the negotiated data on the SCTP
link. If they are inconsistent, go to *2-6. If they are
consistent, go to the next step shown in Figure
16-4.
*2-6
Modify data
configuration.
Modify the configuration on the SCTP link. Run the

MML command MOD SCTPLNK to modify the
configuration on the SCTP link.
For Iub over ATM/IP dual-stack transmission, troubleshoot the failures according to the
suggestions in the ATM transmission and IP transmission as required.

82
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
16.8 AAL2/IP Connection Setup Failure

This section describes how to troubleshoot an AAL2/IP connection setup failure.
Fault Description
During an AAL2 or IP connection setup or cell setup, the AAL2 or IP link fails to be established.
Solution
l
When the user plane is over ATM transmission, check whether the alarms related to the
IMA, optical ports, RSS, AAL2, or MTP3B are reported. If the alarms are reported, handle
them according to the suggestions in the online alarm reference. If the alarms persist, handle
them according to Figure 16-5.
Figure 16-5 Procedure for handling AAL2 connection setup failure
Issue 02 (2013-07-30)

83
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting

Index
Operation
Remarks
*1-1
Check and modify the

local data configuration.
If the configuration data is inconsistent with the

negotiated data, modify the configuration data
based on the negotiated data as described in
Table 16-7.
*1-2
Handle link failures on

the Iub interface.
See 16.7 Signaling Link Failure on the Iub

Interface.
Table 16-7 Checking and modifying the data configuration

Command
Check Item
If Not
LST
ADJNODE
Whether the adjacent node

is configured.
Run the MML command ADD

ADJNODE to add an adjacent node.
LST
AAL2PAT
H
Whether the AAL2 path to

the adjacent node is
configured.

AAL2PATH to add an AAL2 path.
Whether the path ID is

consistent with the
negotiated data.
1. Run the MML command RMV

AAL2PATH to delete this AAL2
path.
2. Run the MML command ADD
Whether the bandwidth is

consistent with the
negotiated data.

AAL2PATH to delete this AAL2
path.
LST
AAL2RT
Whether the IP route to a

specified adjacent node is
configured.

AAL2RT to add an IP route to the
specified adjacent node.
Whether the ATM address

(NSAP) is correct.

AAL2RT to delete the IP route.
AAL2RT to add an IP route.
Issue 02 (2013-07-30)
When the user plane is over transmission resource pool, troubleshoot the setup failure on
the user plane according to Table 16-8.

84
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting

Index
Check Item
Operation
*2-1
Determine the
SIP that carries
the common
channel.
Run the MML command DSP ADJNODESIP to query

the SIP that carries the common channel.
*2-2
Check whether
the SIP is
normal.
Run the MML command DSP IPPOOL to query the SIP

status.
l If the value of SIP operation state is Normal, go to
*2-3.
l If the value of SIP operation state is Fault, go to *2-4.
*2-3
*2-4
*2-5
*2-6
*2-7
Check whether
the peer IP
address is
normal.
Run the MML command DSP ADJNODEPING to query

the Detection Status of the adjacent node.
Check whether
the transmission
link is available.
See 16.1 Checking Transmission Links.
Check the status

of the route based
on the source IP
address.
Run the MML command DSP SRCIPRT to query the

status of the route based on the source IP address.
Check whether
the configuration
of the route based
on the source IP
address is
correct.
Run the MML command LST SRCIPRT to query the

configuration of the route based on the source IP address.
Check the
configuration of
the IP route from
the local end to
the destination
end.
Run the MML command TRC IPADDR to check the

transmission and request transmission engineers to handle
problems.
l If the Detection Status is Normal, go to *2-4.

l If the Detection Status is not Normal, go to 16.5
Unavailable FE/GE Port.
l If the transmission link is unavailable, go to *2-5.

l If the transmission link is available, go to 16.5
Unavailable FE/GE Port.
l If the value of Route Status is UP, go to *2-7.

l If the value of Route Status is DOWN, go to *2-6.
l If the configuration is incorrect, modify the

configuration accordingly.
l If the configuration is correct, go to *2-7.
16.9 Data Loading Failures on the Board

This section describes how to troubleshoot failures that occur during data loading to a
BSC6910 board.
Issue 02 (2013-07-30)

85
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
Fault Description
The status of a board on the device panel is abnormal when host software and data files are being
loaded to the BSC6910 board.
Solution
1.
2.
3.
4.
5.
Issue 02 (2013-07-30)
Check the loading status of other boards of the same type in this subrack.
If...
Then...
Board status of other boards of

the same type is Normal
Replace the faulty board and then reload data to the

new board.
Board status of other boards of

the same type is Faulty
Go to 2.
Check whether the DIP switch on the subrack is set as configured.

If...
Then...
The DIP switch on the subrack

is not set as configured
Correct the DIP switch setting and then reload data to

the board.
The DIP switch on the subrack

is set as configured
Go to 3.
Check whether the internal subnet mask of the OMU board is 255.0.0.0 and whether the
two internal IP addresses are *.168.3.50 and *.168.3.40.
If...
Then...
No
Correct the internal subnet mask and internal IP

address and then reload data to the board.
Yes
Go to 4.
If data loading on the boards in the EPS fails, check whether the SCUb board in the MPS
is properly connected to that in the EPS.
If...
Then...
The connection is improper
Correct the connection and reload data to the board.
The connection is proper
Go to 5.
Run the MML command LST SUBRACK to check whether the type of the faulty board
is properly set.
If...
Then...
The type of the board is

incorrectly set
Correct the board type and then reload data to the

board.

86
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
6.
7.
If...
Then...
The type of the board is correctly

set
Go to 6.
Check whether any alarm related to board fault is present in the Alarm Browser window.
If...
Then...
Alarms related to board fault

exist
Analyze the alarm information and clear the alarm.
No alarm related to board fault

exists
Go to 7.
16.10 Performing a Loopback Test on an Optical Port

This section describes how to perform the group loopback test to check whether an optical port
is functional.
Prerequisites
Context
The loopback test can be performed on an optical port when the E1/T1 transmission link on a
standard interface is unavailable.
Procedure
Step 1 Perform the loopback test on the local optical port.
Table 16-9 Procedure for performing the loopback test on the SDH port
Issue 02 (2013-07-30)
Step
Operation
1-1
Run the MML command SET OPTLOP to set a loopback test on a local optical
port. In this command, set Loop type to LOCAL_LOOP(LOCAL_LOOP).
1-2
Run the MML command DSP E1T1 to query Port State.
1-3
Run the MML command SET OPTLOP to stop the loopback test on the optical
port. In this command, set Loop type to NO_LOOP(NO_LOOP).

87
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
If...
Then...
The command output shows that the value

of Port State is AVAILABLE
The SDH port is available. Go to Step 2.

of Port State is LINK_DOWN
The SDH port is faulty. Replace the interface

board carrying the faulty SDH port.
Step 2 Perform the loopback test on the local fiber optical cable.
Table 16-10 Procedure for performing the loopback test on the local fiber
Step
Operation
2-1
Perform fiber physical loopback at the local end, that is, connect the TX end of the
fiber optic cable to the RX end of the fiber optic cable.
2-2
Run the MML command DSP E1T1 to query Port State.
2-3
Stop the fiber optic cable physical loopback at the local end.
If...
Then...

of Port State is AVAILABLE
The local fiber optic cable is available. Go to

Step 3.

of Port State is LINK_DOWN
The local fiber optic cable is faulty. Replace the

faulty fiber optic cable.
Step 3 Perform the loopback test on the peer optical port.

Table 16-11 Procedure for performing the loopback test on the peer optical port
Step
Operation
3-1
Run the MML command SET OPTLOP at the local end, set Loop type to
REMOTE_LOOP(REMOTE_LOOP).
3-2
l If the peer equipment is the BSC6910, run the MML command DSP OPT at the
peer end to query the state of the optical port.
l If the peer equipment is not the BSC6910, contact the maintenance personnel for
the peer equipment to query the state of the optical port.
3-3
Issue 02 (2013-07-30)
Run the MML command SET OPTLOP to stop the loopback test on the optical
port. In this command, set Loop type to NO_LOOP(NO_LOOP).

88
BSC6910 UMTS
Commissioning Guide
16 Troubleshooting
If...
Then...
The command output shows that the

optical port state is available
The command output shows that the port

state is faulty
Contact the maintenance personnel for the peer

equipment to rectify faults in the peer equipment
or the transport network.
----End
Issue 02 (2013-07-30)

89
BSC6910 UMTS
Commissioning Guide
17 Appendix
17
Appendix
About This Chapter

This chapter provides communication ports on and the commissioning checklist of the
BSC6910.
17.1 Communication Ports on the BSC6910
This section describes communication ports on the BSC6910.
17.2 BSC6910 Commissioning Checklist
This section describes the BSC6910 commissioning checklist used to record and check the
BSC6910 commissioning results.
Issue 02 (2013-07-30)

90
BSC6910 UMTS
Commissioning Guide
17 Appendix
17.1 Communication Ports on the BSC6910

This section describes communication ports on the BSC6910.
For details, see BSC6910 Communication Matrix.
17.2 BSC6910 Commissioning Checklist

This section describes the BSC6910 commissioning checklist used to record and check the
BSC6910 commissioning results.
For details, see BSC6910 Commissioning Checklist.
Issue 02 (2013-07-30)

91

Bsc6910 Umts Commissioning Guide (v100r015c00 - 02) (PDF) - en

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Bsc6910 Umts Commissioning Guide (v100r015c00 - 02) (PDF) - en

Enviado por

Direitos autorais:

Formatos disponíveis

BSC6910 UMTS

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

Huawei Proprietary and Confidential

About This Document

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

Huawei Proprietary and Confidential

About This Document

The keywords of a command line are in boldface.

Command arguments are in italics.

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

6 Logging In to the BSC6910 Through the LMT.......................................................................23

10 Connecting to the M2000..........................................................................................................35

Huawei Proprietary and Confidential

12.2.5 Verifying the Iu-PS Interface..................................................................................................................................52

13 Handling the Alarms Generated During the Commissioning.........................................59

Huawei Proprietary and Confidential

1 Changes in the BSC6910 UMTS Commissioning Guide

Changes in the BSC6910 UMTS

16.1 Checking Transmission

Added procedure of checking FRA transmission link.

8 Activating and Verifying the

Added procedure of verifying the license information.

Huawei Proprietary and Confidential

1 Changes in the BSC6910 UMTS Commissioning Guide

Huawei Proprietary and Confidential

Requirements for Equipment Status

The hardware is installed and has passed the hardware

The OMU is configured before delivery. For details, see

The LMT PC meets the configuration requirements. For details,

Requirements for the Network to Be Commissioned

Other network equipment that is connected to the network equipment to be commissioned,

Huawei Proprietary and Confidential

Figure 2-1 shows a typical network to be commissioned.

Requirements for the Software and Data Files

Software installation package

MML command script file

Huawei Proprietary and Confidential