BSC6900 UMTS Commissioning Guide (V900R018C10 Draft A) (PDF) - EN PDF

BSC6900 UMTS
V900R018C10
Commissioning Guide
Issue
Draft A
Date
2015-12-31
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.

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

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

Address:
Huawei Industrial Base

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

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

Overview
BSC6900 commissioning is performed after hardware is installed and before services are
provided. It aims to ensure that the BSC6900 can work properly by performing verification
tasks related to equipment, board software and data file loading, interfaces, and services.
Product Versions
The following table lists the product version and solution version related to this document.
Product Name
Product Version
Solution Version
BSC6900
V900R018C10
RAN18.1
Intended Audience
This document is intended for:
l
Field engineers
Organization
1 Change History
This section provides information about the changes in different document versions. There are
two types of changes, including function changes and editorial changes. Function changes
refer to changes in functions of a specific product version. Editorial changes refer to changes
in wording or addition of information that was not described in the earlier version.
2 Commissioning Prerequisites
Before BSC6900 commissioning, the status of the equipment and the network to be
commissioned must meet the conditions required. The software installation packages,
licenses, and MML scripts required for commissioning must be ready.
3 Commissioning Process

ii
BSC6900 UMTS
Commissioning Guide
About This Document
The BSC6900 commissioning can be performed remotely, locally, or remotely with local
assistance.
4 Checking Operating Status of Hardware
Before commissioning the equipment, ensure that the BSC6900 cabinet is powered on and is
operating properly.
5 Commissioning the OMU
Before using the OMU for the first time, commission the OMU onsite to check the installation
of product software and the version of the product software, and configure the IP address,
mask, and computer name to ensure the normal communication between the BSC6900 and the
LMT or U2000.
6 Logging In to the BSC6900 Using the LMT
This chapter describes how to log in to the BSC6900 using the LMT and how to establish
communication between the LMT and BSC6900 to ensure successful BSC6900
commissioning using the LMT.
7 Updating the OMU Database
This chapter describes how to update configuration data in the OMU database by running
MML scripts.
8 Activating and Verifying the License
This section describes how to activate the license and verify the license configuration
information to enable service commissioning.
9 Loading BSC6900 Board Software and Data Files
This chapter describes how to load the BSC6900 board software and data files.
10 Connecting to the U2000
This section describes how to connect the BSC6900 to the U2000 for centralized
management.
11 Connecting to Operator's PKI System
This section describes how to connect the BSC6900 to operator's CA server so that the
BSC6900 can automatically manage its own digital certificates.
12 Setting the Connection Mode Between the U2000 and BSC6900 to SSL
The connection mode between the U2000 and BSC6900 must be set to Secure Socket Layer
(SSL) on the U2000 to ensure operation and maintenance (O&M) safety.
13 Verifying Interfaces
This section describes how to verify interfaces on the BSC6900 side using the LMT or
U2000. Select a verification method based on the onsite situation.
14 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.
15 Verifying UMTS Services

iii
BSC6900 UMTS
Commissioning Guide
About This Document
This section describes how to verify that the basic UMTS services and the feature services are
normal. The basic UMTS services are speech services and data services. Feature services
include inter-RAT handovers, HSDPA, HSUPA, 64QAM, MIMO, CBS, and DC-HSDPA.
16 Verifying Network Reliability
The network reliability can be verified by checking generated alarms and making dialing tests
after a switchover between the active/standby boards.
17 Troubleshooting
This chapter describes how to troubleshoot common problems during the commissioning.
18 Appendix
This chapter provides communication ports on and the commissioning checklist of the
BSC6900.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
Indicates an imminently hazardous situation which, if not
avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not
avoided, could result in death or serious injury.
avoided, may result in minor or moderate injury.
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Calls attention to important information, best practices and
tips.
NOTE is used to address information not related to
personal injury, equipment damage, and environment
deterioration.
General Conventions
The general conventions that may be found in this document are defined as follows.

iv
BSC6900 UMTS
Commissioning Guide
About This Document
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.
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.

BSC6900 UMTS
Commissioning Guide
About This Document
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.
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
BSC6900 UMTS
Commissioning Guide
Contents
Contents
About This Document.....................................................................................................................ii
1 Change History.............................................................................................................................. 1
2 Commissioning Prerequisites..................................................................................................... 2
3 Commissioning Process............................................................................................................... 4
4 Checking Operating Status of Hardware..................................................................................6
5 Commissioning the OMU............................................................................................................8
5.1 Commissioning an OMU Locally...................................................................................................................................9
5.2 Commissioning the OMU Using a USB Flash Drive...................................................................................................15
6 Logging In to the BSC6900 Using the LMT............................................................................ 26

7 Updating the OMU Database....................................................................................................28
8 Activating and Verifying the License......................................................................................33
9 Loading BSC6900 Board Software and Data Files................................................................ 35
9.1 Generating Data Files for the Loading......................................................................................................................... 36
9.2 Setting the Board Loading Mode..................................................................................................................................36
9.3 Resetting BSC6900 Boards.......................................................................................................................................... 36
9.4 Checking the Consistency of the Data and the Version................................................................................................37
10 Connecting to the U2000...........................................................................................................39

11 Connecting to Operator's PKI System...................................................................................42
12 Setting the Connection Mode Between the U2000 and BSC6900 to SSL........................ 45
13 Verifying Interfaces.................................................................................................................. 47
13.1 Verifying Interfaces on the U2000..............................................................................................................................48
13.1.1 Setting the NE Engineering Mode to TESTING..................................................................................................... 48
13.1.2 Verifying Interfaces Automatically..........................................................................................................................49
13.1.3 Setting the NE Engineering Mode to NORMAL................................................................................................... 51
13.2 Verifying Interfaces on the LMT................................................................................................................................ 52
13.2.1 Verifying Fiber Optic Cable Connections............................................................................................................... 53
13.2.2 Verifying Internal Interfaces.................................................................................................................................... 54
13.2.3 Verifying the Iub Interface.......................................................................................................................................55

vii
BSC6900 UMTS
Commissioning Guide
Contents
13.2.4 Verifying the Iu-CS Interface.................................................................................................................................. 58

13.2.5 Verifying the Iu-PS Interface................................................................................................................................... 62
13.2.6 Verifying the Iur Interface....................................................................................................................................... 65
13.2.7 Verifying the Iu-BC Interface.................................................................................................................................. 69
13.2.8 Verifying the Iur-g Interface.................................................................................................................................... 69
13.2.9 Verifying the Iur-p Interface.................................................................................................................................... 70
13.2.10 Verifying the Sr Interface...................................................................................................................................... 72
14 Handling the Alarms Generated During the Commissioning......................................... 73

15 Verifying UMTS Services........................................................................................................ 74
16 Verifying Network Reliability................................................................................................77
17 Troubleshooting........................................................................................................................ 79
17.1 Checking Transmission Links.................................................................................................................................... 81
17.2 Performing a VCL Continuity Check......................................................................................................................... 84
17.3 Verifying the PVC Delay Detection Function............................................................................................................ 86
17.4 Unavailable E1/T1 Port.............................................................................................................................................. 88
17.5 Unavailable FE/GE Port............................................................................................................................................. 89
17.6 Cell Setup Failure....................................................................................................................................................... 89
17.7 Signaling Link Failure on the Iub Interface................................................................................................................95
17.8 AAL2/IP Connection Setup Failure......................................................................................................................... 100
17.9 Data Loading Failures on the Board.........................................................................................................................104
17.10 Performing a Loopback Test on the Local E1/T1 Port........................................................................................... 106
17.11 Performing a Loopback Test on an Optical Port.....................................................................................................109
17.12 Checking the QCIs of the IP Transmission Link.................................................................................................... 110
18 Appendix................................................................................................................................... 113
18.1 Communication Ports on the BSC6900.................................................................................................................... 114
18.2 BSC6900 Commissioning Checklist........................................................................................................................ 114

viii
BSC6900 UMTS
Commissioning Guide
1 Change History
Change History
This section provides information about the changes in different document versions. There are
two types of changes, including function changes and editorial changes. Function changes
refer to changes in functions of a specific product version. Editorial changes refer to changes
in wording or addition of information that was not described in the earlier version.
Draft A (20151231)
Compared with Issue 01 (2015-03-25) of V900R017C10, this issue includes the following
changes.
Change Type
Change Description
Technical
change
New
None
Modified
For details about the processes required when the

OMU is running, see Commissioning an OMU Locally.
Deleted
None
Editorial change
None

BSC6900 UMTS
Commissioning Guide
Commissioning Prerequisites
Before BSC6900 commissioning, the status of the equipment and the network to be
commissioned must meet the conditions required. The software installation packages,
licenses, and MML 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
BSC6900 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 BSC6900
UMTS OMU Administration Guide.
LMT PC
The LMT PC meets the configuration requirements. For

details, see Configuration Requirements of the LMT PC in
BSC6900 UMTS LMT User Guide.
Requirements for the Network

To ensure the smooth commissioning of the Iub, Iu, Iur, Iur-g, Iur-p, and Iu-BC interfaces, the
network to be commissioned must meet the following requirements:
l
At least one NodeB is connected to the BSC6900. The NodeB must have passed
commissioning and can provide basic functions.
At least one set of CN equipment is connected to the BSC6900. 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 BSC6900, the RNC,
BSC, or CBC must have passed commissioning and can provide basic functions.

BSC6900 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 Software and Data Files

l
Software installation package

The installation package that is compatible with the version used in the local office must
be ready before commissioning.
License
The license that is applicable to configurations used in the local office is obtained from
the Huawei technical support engineers.
MML script file

The initial configuration is complete before commissioning according to BSC6900
UMTS Initial Configuration Guide to obtain the MML script file. In addition, the
correctness of the data configuration is checked and ensured based on the MML script
examples and the onsite negotiated data defined in BSC6900 UMTS Initial Configuration
Guide.
NOTE
If the CME method is used to configure the data, the MML script file is not necessary.

BSC6900 UMTS
Commissioning Guide
Commissioning Process
The BSC6900 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 BSC6900 equipment room) who connects a PC to the BSC6900
and performs the commissioning on the LMT.
Remote commissioning is remotely performed by an engineer (technical engineer

responsible for the BSC6900) and multiple BSC6900s 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.

BSC6900 UMTS
Commissioning Guide
Figure 3-1 Commissioning Flowchart

BSC6900 UMTS
Commissioning Guide
Checking Operating Status of Hardware
Before commissioning the equipment, ensure that the BSC6900 cabinet is powered on and is
operating properly.
Prerequisites
The BSC6900 cabinet has passed the power-on check.
Procedure
Step 1 Check whether the cabinet is powered on.
If...
Then...
The cabinet is not powered on
Go to Step 2.
The cabinet is powered on
Go to Step 4.
Step 2 Turn on the power switches that control cabinet power supply on the power distribution frame
(PDF).
Step 3 Turn on the power switches on the power distribution box after the RUN indicator on the front
panel of the power distribution box blinks 0.25s on and 0.25s off.
If...
Then...
The cabinet is an MPR
Set the corresponding power switches on the power

distribution box to ON.
If the cabinet is an
EPR/TCR
Set the power switches that correspond to the subracks

configured in the same cabinet to ON.
Step 4 Check the power supply to the cabinet components, as listed in Table 4-1. Ensure that the
hardware operates properly.

BSC6900 UMTS
Commissioning Guide
Table 4-1 Checklist of the power supply to the cabinet components

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 1s on and 1s off in green after the
subrack or independent fan subrack is
powered on.
Power distribution monitor board
The RUN indicator on the board panel

blinks 1s on and 1s off in green. The ALM
indicator is steady off.
NOTE
If a power failure occurs, resolve the problem following the operations provided in step 5 in section Powering
On the Cabinet in BSC6900 UMTS Site Maintenance Guide.
----End

BSC6900 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 product software and the version of the product software, and configure the IP address,
mask, and computer name to ensure the normal communication between the BSC6900 and the
LMT or U2000.
Context
The OMU can be commissioned locally or by using a USB flash drive. In new network
deployment, the OMU board has been preinstalled with the operating system and applications
before delivery. Therefore, it is recommended that the OMU board be commissioned locally.
NOTE
For the definitions of "fixed external IP address", "virtual external IP address", "fixed internal IP address",
"virtual internal IP address", "IP address of the backup channel between the active and standby OMU
boards", and "commissioning IP address", refer to OMU IP Address Plan of "Working Principles" in
BSC6900 OMU Administration Guide.
5.1 Commissioning an OMU Locally

This section describes how to commission an OMU locally. The commissioning is performed
by a field engineer by connecting a PC to the OMU over a commissioning Ethernet port. If
the BSC6900 has been configured with active and standby OMUs, commission both the
active OMU and the standby OMU.
5.2 Commissioning the OMU Using a USB Flash Drive
This section describes how to commission an OMU using a USB flash drive. You can locally
insert the prepared USB flash drive to the OMU and then perform OMU commissioning with
cooperation of a remote engineer.

BSC6900 UMTS
Commissioning Guide
5.1 Commissioning an OMU Locally

This section describes how to commission an OMU locally. The commissioning is performed
by a field engineer by connecting a PC to the OMU over a commissioning Ethernet port. If
the BSC6900 has been configured with active and standby OMUs, commission both the
active OMU and the standby OMU.
Prerequisites
l
The OMU is connected to a local PC using a commissioning Ethernet port.
The version installation package or patch installation package that you have obtained is
the same as the customer version.
You have obtained the psftp software and the PuTTY software. For details, see Obtaining
and Using the psftp Software and Obtaining and Using the PuTTY Software.
If the product software has been installed before delivery, the active workspace of the
OMU is version_a.
If the product software is not installed before delivery, plan items in Information Records
of OMU Software Installation before installing the product software.
For details about the OMU software factory settings, see Checklist for the OMU
Software Factory Settings.
Context
For details about how to commission the OMU locally, see Figure 5-1.

BSC6900 UMTS
Commissioning Guide
Figure 5-1 Flowchart for commissioning the OMU locally
Procedure
Step 1 Connect a PC to the OMU board.
1.
Connect the PC to the ETH2 commissioning port on the OMU board using a network
cable.
2.
Set the IP addresses of the PC and ETH2 port so that they are in the same network
segment.
The initial IP address of the ETH2 port is 192.168.6.50 or 192.168.6.60, and the subnet
mask is 255.255.255.0. The initial IP address of the ETH2 port is the commissioning IP
address. For details about the commissioning IP address, see OMU IP Address Plan.
Step 2 Set the link mode of the external OMU Ethernet adapters.
1.
Log in to the OMU by referring to the procedures described in Logging In to the OMU.
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
Querying the Link Mode of the External OMU Network Adapters.

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

Ethernet adapters is consistent with that
of LAN switches
Go to Step 3.
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.
Step 3 Install the product software.

1.
Enter /etc/rc.d/omud status to check the running status of the OMU process.
If...
Then...
running is displayed
1. Enter /etc/rc.d/omud stop to stop the

omud process.
2. Go to Step 3.2.
unused is displayed
Go to Step 3.2.
No such file or directory is displayed
1. Install the product software to the

active workspace by referring to
operations in Procedure of Installing
the Product Software in the Active
Workspace.
2. Go to Step 7, Step 8 and Step 9.
2.
Enter cd /mbsc/upgrade to go to the OMU installation directory, and then enter ls to

query the current version of the product software.
If...
Then...
The product software version is the same

as that required by the operator
Go to Step 4.

11
BSC6900 UMTS
Commissioning Guide
If...
Then...
The product software version is different

from that required by the operator
1. Uninstall the product software by

referring to operations in Procedure of
Uninstalling the Product Software.
2. Upload the product software
installation package to the OMU by
referring to operations in Procedure of
Uploading the OMU Application
Installation Package to the OMU.
3. Install the product software to the
active workspace by referring to
operations in Procedure of Installing
the Product Software in the Active
Workspace.
4. Go to Step 7, Step 8 and Step 9.
Step 4 Modify the OMU IP addresses.

Perform either of the following operations to change IP addresses of the OMU:
l Method 1: Run the MOD OMUIP command. This operation can be performed only if the
Ethernet adapter is connected to the OMU over a local commissioning port. For details,
see the description of the MOD OMUIP command in the MML command reference.
l Method 2: Use the omutool to change IP addresses of the OMU. For details, see the
following substeps.
1.
Enter cd /mbsc/bam/version_a/bin/bam to go to the directory where the omutool

program is located.
NOTE
You can execute ./omutool -h to view the help information of the omutool.
2.
Change the external fixed IP address and subnet mask according to the operator's plan.
Enter ./omutool extercard The external fixed IP address The subnet mask The gateway
IP address (Optional) to change the external fixed IP address and the subnet mask. For
example, you can enter the following command:
./omutool extercard 10.161.10.100 255.255.255.0
NOTE
l Perform either of the following operations if a gateway IP address needs to be changed while
you are changing an external fixed IP address:
l Method 1: Enter ./omutool extercard The external fixed IP address The subnet mask (The
gateway IP address) to change the external fixed 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: Enter ./omutool gateway The gateway IP address to change the gateway IP
address separately. The following is an example:
./omutool gateway 10.161.10.1
l After the external fixed IP address is changed, the OMU can be connected to the operation and
maintenance (OM) network of the operator over the ETH0 or ETH1 port. In this case,
subsequent commissioning tasks can be performed remotely.

12
BSC6900 UMTS
Commissioning Guide
3.
Change the external virtual IP address and subnet mask of the active and standby OMUs
according to the plan. Ensure that the external virtual IP address is on the same network
segment as the external fixed IP address.
Enter ./omutool extervip The external virtual IP address The subnet mask to change the
external virtual IP address and subnet mask. For example, you can enter the following
command:
./omutool extervip 10.161.10.102 255.255.255.0
NOTE
The external virtual, external fixed and gateway IP addresses must all be in the same network
segment. If you change either of the first two of these, you will be prompted to check whether the
other two addresses need to be changed to comply with this rule.
4.
Check whether the internal fixed IP address, internal virtual IP address, backup channel
IP address, and commissioning IP address of active and standby OMUs are in the same
network segment as the operator's network.
If...
Then...
All the preceding IP addresses

are in the same network
segment as the operator's
network
Change the IP address in conflict.

l Change the internal network segment by
referring to Follow-up Procedure in 7 Updating
the OMU Database.
l Change the backup channel IP address and
subnet mask of the active and standby OMUs:
If OMUa boards are used, enter ./omutool
backupcard The IP address. For example,
you can enter the following command:
./omutool backupcard 192.168.3.60
If OMUc boards are used, enter ./omutool

backupcard_for_omuc The IP address
and ./omutool backupcard_for_omua The
IP address. For example, you can enter the
following commands:
./omutool backupcard_for_omuc
192.168.9.60
./omutool backupcard_for_omua
192.168.3.60
l Enter ./omutool debugcard The debugging IP

address to change the commissioning IP address
and subnet mask. For example, you can enter the
following command:
./omutool debugcard 192.168.6.60

13
BSC6900 UMTS
Commissioning Guide
If...
Then...
The preceding IP addresses are

not in the same network
segment as the operator's
network
Change the backup channel IP address of the

standby OMU.
l If OMUa boards are used, enter ./omutool
backupcard The IP address. For example, you
can enter the following command:
./omutool backupcard 192.168.3.60
l If OMUc boards are used, enter ./omutool

backupcard_for_omuc The IP address and ./
omutool backupcard_for_omua The IP
address. For example, you can enter the
following commands:
./omutool backupcard_for_omuc 192.168.9.60
./omutool backupcard_for_omua 192.168.3.60
Step 5 Enter ./omutool dispipinfo to check whether the modified OMU IP address and subnet mask
are correct based on the query result.
Step 6 Change the OMU name.
1.
Enter ./omutool computername OMU name to change the name of the OMU.
For example, you can enter ./omutool computername omu_123.
NOTE
The OMU name cannot contain control characters, spaces, or any of the following special characters: / \
[ ] ( ) ' : | < > + = ; , ?, and the length of the OMU name must range from 1 to 62 characters.
Step 7 Set the working mode of the OMU.

1.
Set the OMU backup mode.

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

a.
Enter /etc/rc.d/omud start to start the product software.
b.
Run the SET OFFICENAME command to set the office name.
Step 8 Check the OMU running status.

1.
Enter ps -afx 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, and
debug_log

14
BSC6900 UMTS
Commissioning Guide
OMU State
OMU Processes That Must Exist
Standby OMU
software, ftp_server, sntp,

omu_manager, cfg_mirror, and
debug_log
NOTE
If some of the preceding processes do not exist, enter /etc/rc.d/omud restart to restart the OMU
server, and then check whether the processes exist. If some of them still do not exist, uninstall the
product software and then reinstall it in the active workspace by referring to operations in
Procedure of Uninstalling the Product Software and Installing the Product Software in the Active
Workspace.
Step 9 Enter exit to stop the PuTTY and then remove the cable to disconnect the PC from the OMU.
----End
5.2 Commissioning the OMU Using a USB Flash Drive

This section describes how to commission an OMU using a USB flash drive. You can locally
insert the prepared USB flash drive to the OMU and then perform OMU commissioning with
cooperation of a remote engineer.
Prerequisites
l
The preparations for installing software on site are completed. For details, see Onsite
Software Installation Preparations.
You have obtained the planned OMU information and recorded them in Configuration
Information for Preparing the USB Flash Drive.
The capacity of the USB flash drive is at least 4 GB. If the BSC6900 is configured with
active and standby OMUs, two USB flash drives are required.
A USB flash drive has been inserted into an available and uncontrolled (for example,
CPM control) USB port on a portable computer
Check whether the USB flash drive is usable by referring to the USB Flash Drive
Verification Guide under the USB Disk 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 (4 GB), Kingston and Sandisk USB storage devices are recommended.
Context
NOTICE
Back up the OMU data before you install the OMU operating system and product software.
This is because the OMU hard disk will be formatted during the installation of the OMU
operating system and product software using the USB flash drive, and all data will be deleted.

15
BSC6900 UMTS
Commissioning Guide
This section uses the commissioning of active and standby OMUs as an example. The
commissioning operation differences between the OMU in independent mode and the
OMUs in active/standby mode are described separately.
Commissioning an OMU using a USB flash drive involves two steps: preparing the USB
flash drive and commissioning the OMU after inserting the USB flash drive into the
OMU.
Figure 5-2 Flowchart for commissioning the OMU using a USB flash drive
Procedure
Step 1 Prepare a USB flash drive.
1.
Double-click U_creator_eng.exe to begin installing a Dopra Linux operating system on

the USB flash drive, as shown in Figure 5-3.

16
BSC6900 UMTS
Commissioning Guide
Figure 5-3 U_creator_eng window
2.
Right-click NE List in the left pane of the window shown in Figure 5-3 and choose Add
NE from the shortcut menu. A dialog box is displayed, as shown in Figure 5-4.

17
BSC6900 UMTS
Commissioning Guide
Figure 5-4 Add NE dialog box
3.
Specify NE Name, set Operating System Type to DopraLinux, set Operate type to
Install. Then click OK. An NE is added.

18
BSC6900 UMTS
Commissioning Guide

NOTE
l If only the operating system is to be installed on the OMU, do not select Install product software?.
If the operating system and product software are to be installed on the OMU, select Install product
software? and specify External Virtual IP Address of the NE to be added.
l If only the product software is to be installed on the OMU, set Operate type to Only install
product software, and specify External Virtual IP Address of the NE to be added.
l The NE name, used to identify an NE, can include only letters, numerals, dashes ("-"), and
underscores ("_").
l The NE name and the virtual external IP address can be changed only after you delete the NE and
then add it again.
l If you want to prepare multiple USB flash drives, you are advised to prepare and label the USB
flash drives one by one.
4.
Double-click the added NE in the left pane. The window is refreshed, as shown in
Figure 5-5.
Figure 5-5 Configuring information

19
BSC6900 UMTS
Commissioning Guide

NOTE
l The IP addresses shown in Figure 5-5 are required by the U_creator tool by default. Change the IP
addresses as required. For details about the principles of changing the IP addresses, see OMU IP
Address Plan.
l Select the link mode for external Ethernet adapters listed in Figure 5-5 as required. Ensure that the
link mode for external Ethernet adapters is consistent with that for the onsite LAN switch. Table
5-1 lists the mapping between the queried link mode for external Ethernet adapters and that selected
in Figure 5-5.
l In independent OMU mode, only the active OMU configuration is effective, whereas the standby
OMU configuration is ineffective.
l The new password policy is as follows:
l Passwords of admin must contain 8 to 32 characters.
l The characters must be uppercase letters, lowercase letters, digits, or special characters, or the
combination of two among these types.
l Special characters include spaces and the following characters ~!@#$^*()_+-{}|[]:./
l Modify Debug network IP and Debug network mask based on actual conditions.
l On the interface described in Figure 5-5, under Please select the initial configuration data file,
import an initial configuration data file exported using a non-encryption method, and ensure that the
file data is consistent with that on Figure 5-5. The data includes the product type, version, patch
version, run mode of OMU, and language of OMU.
l On the interface described in Figure 5-5, if Data encryption is selected, fill in the E-Label of the
target OMU. To obtain the E-Label of an OMU, you can manually query the OMU board bar code
label. Alternatively, you can run the DSP OMU command to view the current OMU active/standby
status and then query the value of the BarCode parameter in the DSP ELABEL command.
Table 5-1 Mapping between link modes of external Ethernet adapters

Queried Link Mode of External
Ethernet Adapter
Link Mode of External Ethernet

Adapter to Be Selected
l Auto-negotiation is on.
Auto
l Auto-negotiation is off.
10Mb Full
l Speed is 10Mb/s.
l Duplex is Full.
10Mb Half
l Speed is 10Mb/s.
l Duplex is Half.
100Mb Full
l Speed is 100Mb/s.
l Duplex is Full.
100Mb Half
l Speed is 100Mb/s.
l Duplex is Half.

20
BSC6900 UMTS
Commissioning Guide
Queried Link Mode of External

Ethernet Adapter
Link Mode of External Ethernet

Adapter to Be Selected
l Auto-negotiation is off
1000Mb Full
l Speed is 1000 Mbit/s

l Duplex is Full
l Auto-negotiation is off
1000Mb Half
l Speed is 1000 Mbit/s

l Duplex is Half
5.
After all the information is automatically obtained, check whether the information is
correct and enter other required information.
NOTE
l If a version or baseline patch is to be installed, select the V**R**C** directory of the version
installation package or the V**R**C**SPCX00 directory for the baseline patch installation
package.
l If a non-baseline patch is to be installed, select the V**R**C**SPCXYZ or V**R**C**SPHXYZ
directory for the patch installation package.
6.
Check that all the information is correct and click OK. In the displayed dialog box,
check the directory where the USB flash drive is located and start preparing a USB flash
drive.
7.
Perform operations by following the instructions until the system displays a message that
reads Succeed to create USB drive of OMU installation. Click Finish to finish
preparing the USB flash drive.
NOTE
l If the system asks for your confirmation during preparation of the USB flash drive, insert or remove
the USB flash drive.
l If an independent OMU is configured, skip the steps for preparing the standby OMU USB flash
drive.
Step 2 Commission the OMU after inserting the USB flash drive to the OMU.
1.
Insert the USB flash drive into any USB port 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 BSC6900 UMTS Site Maintenance Guide.
3.
Observe the status of the indicators on the OMU board panel and determine whether the
installation is complete.
If...
Check the indicator status
Only the operating system is to be

installed on the OMU
Table 5-2
The operating system and product

software are to be installed on the OMU
Table 5-3
Only the product software is to be

installed
Table 5-4

21
BSC6900 UMTS
Commissioning Guide

NOTE
l If the status of the indicators differs from this, the OMU cannot identify the USB flash device.
In this case, prepare another USB flash device. Alternatively, copy the data in the original
USB flash device to a new one, and then reinstall the OMU operating system.
l After the OMU operating system and the product software are installed successfully, remove
the USB flash drive from the OMU board panel. The OMU commissioning is complete. If the
value of operation type is Only install product software, you need to remove and reinsert
the OMU to restart the OMU operating system after removing the USB flash drive.
Table 5-2 Status of the indicators on the OMUa or OMUc board panel during the OMU
operating system installation
Board
Installation
Procedure
Successful
Installation
Failed Installation
OMUa
At the beginning:
l The RUN indicator

blinks.
l The RUN indicator

is off.
l The ALM indicator

is off or blinks.
l The ALM indicator

blinks.
l The ACT indicator

is off.
l The ACT indicator

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

blinks.
l The RUN indicator

blinks.
l The RUN indicator

is off.
l The ALM indicator

blinks.
l The ALM indicator

is off.
l The ALM indicator

blinks.
l The ACT indicator

blinks.
l The ACT indicator

is off.
l The ACT indicator

is off.
l The OFFLINE
indicator is off.
l The OFFLINE
indicator blinks.
l The OFFLINE
indicator blinks.
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.
OMUc

22
BSC6900 UMTS
Commissioning Guide
Table 5-3 Status of indicators on the OMUa or OMUc board panel during the OMU
operating system and product software installation
Board
Installation
Procedure
Successful
Installation
Failed Installation
OMUa
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

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 RUN indicator

blinks.
l The RUN indicator

blinks.
l The ALM indicator

blinks.
l The ALM indicator

l The ALM indicator

blinks.
l The ACT indicator

blinks.
l The ACT indicator

l The ACT indicator

is off.
l The OFFLINE
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.
l The RUN indicator
blinks.
l The ALM indicator
is off.
l The ACT indicator
is off.
l The OFFLINE
indicator blinks.
OMUc

23
BSC6900 UMTS
Commissioning Guide
Table 5-4 Status of indicators on the OMUa or OMUc board panel during only the
product software installation
Board
Installation
Procedure
Successful
Installation
Failed Installation
OMUa
At the beginning:
l The RUN indicator

blinks.
l The RUN indicator

blinks.
l The ALM indicator

l The ALM indicator

blinks.
l The ACT indicator

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 RUN indicator

blinks.
l The RUN indicator

blinks.
l The ALM indicator

is off.
l The ALM indicator

l The ALM indicator

blinks.
l The ACT indicator

is off.
l The ACT indicator

l The ACT indicator

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

blinks.
l The ALM indicator
is off.
l The ACT indicator
blinks.
l The OFFLINE
indicator is off.
l The RUN indicator
blinks.
l The ALM indicator
blinks.
l The ACT indicator
is off.
l The OFFLINE
indicator is off.
OMUc
----End
Follow-up Procedure
Troubleshooting upon Installation Failures
Check whether the configuration files prepared in 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.
l
If the configuration files are not correct, prepare the USB flash drive again by referring
to the step Prepare the USB flash drive.
If the configuration files are correct, contact Huawei technical support by referring to
Contact the Technical Support for Assistance.
Querying the Operating System Version Using the PuTTY


24
BSC6900 UMTS
Commissioning Guide
1.
Double-click putty.exe. Enter the physical IP address of the OMU where an operating
system has been installed. An interface for logging in to the Linux operating system is
displayed. Enter an administrator-level user name and its password to log in to the OMU.
2.
Execute /cat /etc/DL-Release to query the operating system version, as shown in Figure
5-6.
Figure 5-6 Querying the operating system version using the Putty

25
BSC6900 UMTS
Commissioning Guide
Logging In to the BSC6900 Using the LMT
This chapter describes how to log in to the BSC6900 using the LMT and how to establish
communication between the LMT and BSC6900 to ensure successful BSC6900
commissioning using the LMT.
Prerequisites
l
The OMU commissioning has been complete.
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 BSC6900 using the LMT to verify the connection between the OMU and
the external network. In this case, the field engineer needs to enter the IP address for OMU
commissioning in the address bar of Internet Explorer (IE) to log in to the LMT.
Context
JRE is a standard Java plug-in. If JRE is not installed, a message is displayed when you
attempt to log in to the LMT. In this case, install JRE by following the instructions in the
displayed prompt message. If the JRE installed in the PC is not of the latest version, a
message is displayed when you attempt to log in to the LMT, prompting you to update the
JRE. In this case, it is recommended that you uninstall the JRE and then install the JRE of the
latest version
CAUTION
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.
Check the hardware configuration of the BSC6900 LMT PC to ensure that the
requirements described in Configuration Requirements of the LMT PC are met.

26
BSC6900 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 BSC6900 using the LMT.
1.
Start the IE and enter the external virtual IP address of the OMU of the BSC6900 on the
address bar. The login dialog box is displayed, as shown in Figure 6-1.
Figure 6-1 BSC6900 login dialog box
NOTE
To log in to the BSC6900 by using the Domain user account, establish the connection between the
BSC6900 and the U2000 server.
2.
Enter User Name, Password, and Verify Code, and click Login to log in to the LMT.
----End

27
BSC6900 UMTS
Commissioning Guide
Updating the OMU Database
This chapter describes how to update configuration data in the OMU database by running
MML scripts.
Prerequisites
l
You have completed the operations provided in section 6 Logging In to the BSC6900
Using the LMT.
The MML command data scripts applicable to the local office are verified and the
contents are precise and complete.
There are two methods to run MML scripts: by running MML commands or using the
GUI. The MML 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 script by running MML commands.
Context
Procedure
1.
Run the MML command SET CFGDATAINEFFECTIVE to set the MPS to work
in ineffective mode.
NOTICE
If the database has been updated, run the MML command SET
CFGDATAINEFFECTIVE to set each configured subrack to work in ineffective
mode.
2.
Run the MML command RST DATA. Click Yes in the displayed dialog box to
initialize the BSC6900 configuration data in the OMU database.
3.
Run the MML command UPD KEYMATERIAL to update the key material used
for local data encryption.

28
BSC6900 UMTS
Commissioning Guide
4.
Upload the MML 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.
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
5.
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 LMT user name and password. The connection between the OMU
and the local FTP is set up after the authentication succeeds.
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 to Step 5
to run the new script.
Run the MML script by using the GUI.

1.
Run the MML command SET CFGDATAINEFFECTIVE to set the MPS to work
in ineffective mode.
NOTICE
If the database has been updated, run the MML command SET
CFGDATAINEFFECTIVE to set each configured subrack to work in ineffective
mode.

29
BSC6900 UMTS
Commissioning Guide
2.
Run the MML command RST DATA. Click Yes in the displayed dialog box to
initialize the BSC6900 configuration data in the OMU database.
3.
Run the MML command UPD KEYMATERIAL to update the key material used
for local data encryption.
4.
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
5.
Click Open....The Open dialog box is displayed. Select the prepared MML script,
and then click Open. The commands in the script are displayed on the Batch tab
page.
6.
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.

30
BSC6900 UMTS
Commissioning Guide
Figure 7-2 Setting the batch commands
7.
On the Batch tab page, select All in the Execution Type area.
8.
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 script, the MML 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 5 to run the script again.
9.
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 operations to ensure the normal
communication between the OMU and BSC6900.
1.
Run the MML command LST SUBNET to query the Subnet No. of the BSC6900.
2.
Check whether the Subnet No. of the BSC6900 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
Commissioning the OMU Locally.

31
BSC6900 UMTS
Commissioning Guide
l If they are consistent, run the DSP OMU command to query the OMU internal
network segment and check whether the OMU internal network segment is consistent
with the network segment of the internal IP address of the OMU.
a.
If they are consistent, perform 3.
b.
If they are inconsistent, run the RST OMU command with Reset Type set to
SOFT(Soft Reset) to reset the active and standby OMU boards.
l If they are inconsistent, perform the following operations:

a.
Run the MML command SET SUBNET to change the Subnet No. of the
BSC6900 so that it is consistent with the network segment of the planned
internal IP address of the OMU.
b.
Run the RST OMU command with Reset Type set to SOFT(Soft Reset) to
reset the active and standby OMU boards.
3.
Run the MML command SET CFGDATAEFFECTIVE to set the MPS to work in
effective mode.
4.
Locally remove the SCU board and then reinsert it into the MPS. Then, reset the MPS so
that the new IP address of the BSC6900 host takes effect.

32
BSC6900 UMTS
Commissioning Guide
Activating and Verifying the License
This section describes how to activate the license and verify the license configuration
information to enable service commissioning.
Prerequisites
l
Using the LMT.
The FTP server is started. For details on how to start the FTP server, see the operations
in Startup in BSC6900 UMTS LMT User Guide for FTP Server. For the default user
name and password of the FTP server, see FTP Server in BSC6900 UMTS LMT User
Guide. Note that the user name or password may be modified.
The license file 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/software/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 for
Go to Step 3.
The license is inconsistent with what you apply for
Contact Huawei technical support.
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.

33
BSC6900 UMTS
Commissioning Guide
If...
Then...
The license information is consistent with the

OMU information
Go to Step 4.
The license information is inconsistent with the Modify the inconsistent data and then
OMU information
repeat this 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 command for each
operator.
----End
Follow-up Procedure
If the license activation fails, 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 a license activation failure. For details, see the online
help of the MML command ACT LICENSE.

34
BSC6900 UMTS
Commissioning Guide
Loading BSC6900 Board Software and Data

Files
About This Chapter

This chapter describes how to load the BSC6900 board software and data files.
Prerequisites
l
The device has been commissioned.
The OMU database has been updated.
Context
The software of the BSC6900 is generated automatically in the OMU active workspace
directory /bin/fam during the installation of the product software. 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 BSC6900 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 Board Loading Mode
This section describes how to set the loading modes of all the board subsystems before
resetting BSC6900 boards.
9.3 Resetting BSC6900 Boards
This section describes how to load the BSC6900 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 BSC6900 are consistent with those on the OMU.

35
BSC6900 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
Using the LMT.
Procedure
Step 1 Run the MML command SET CFGDATAEFFECTIVE without specifying any parameter to
set the subracks configured 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 Board Loading Mode

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

This section describes how to load the BSC6900 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.

36
BSC6900 UMTS
Commissioning Guide
Using the LMT.
All the subracks have been powered on.
Context
The resetting time is less than or equal to six minutes in the maximum configuration. There is
no requirement for the sequence. All the subracks can be reset at the same time.
Procedure
Step 1 Run the MML command RST SUBRACK, and then set Subrack No. to the number of the
subrack to be reset. A dialog box is displayed, asking you whether to proceed. Click OK. The
boards in the subrack automatically load the BSC6900 board software and data files from the
OMU.
Step 2 Repeat Step 1 to reset all the BSC6900 subracks.
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 3 Click the Device Maintenance tab on the LMT home page after all the subracks are reset.
The Device Maintenance tab page is displayed.
Step 4 Check whether all the boards on the device panel are in the normal state.
If...
Then...
The device panel shows that all the boards No further action is required.
are in the normal state
The device panel shows that some boards
are not in the normal state
Check the faulty boards and clear the alarms

according to operations in 17.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 BSC6900 are consistent with those on the OMU.
Prerequisites
l
All the subracks and boards are running properly.
Using the LMT.
Procedure
Step 1 Run the MML command ACT CRC without specifying any parameter to check whether the
BSC6900 board configuration is consistent with the data on the OMU.

37
BSC6900 UMTS
Commissioning Guide
Expected result: The All table data consistent. message is displayed.

Step 2 Run the MML command CMP BRDVER without specifying any parameter to check whether
the version run by the BSC6900 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
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).

38
BSC6900 UMTS
Commissioning Guide
10
Connecting to the U2000
This section describes how to connect the BSC6900 to the U2000 for centralized
management.
Prerequisites
l
The operation and maintenance (O&M) network has passed the commissioning. The
U2000 is operating properly.
The version of the U2000 is compatible with that of the BSC6900.
The mediation version of the U2000 is compatible with the NE version.
If the BSC6900 and the U2000 are in the same network segment, you do not need to
configure an IP route to the BSC6900 to the U2000.
If the BSC6900 and the U2000 are not in the same network segment, you must configure
an IP route from the BSC6900 to the U2000.
Context
Procedure
Step 1 Connect the BSC6900 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 BSC6900 to the U2000.

1.
Run the MML command LST OMUIPRT to check whether the IP route to the U2000 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 BSC6900
has an IP route to the U2000. 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 BSC6900 does not
have a route to the U2000. Go to Step 2.2.
2.
Run the MML command ADD OMUIPRT to configure a route from the BSC6900 to
the U2000.

39
BSC6900 UMTS
Commissioning Guide
3.
Verify the configuration of the route from the BSC6900 to the router.
Log in to the OMU according to the instructions in BSC6900 UMTS OMU
Administration Guide for Logging In to the OMU, and then run the ping command to
check whether the network connectivity between the BSC6900 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 BSC6900 to the U2000.
Log in to the OMU and run the ping command to check whether the network
connectivity between the BSC6900 and the U2000 is available. If the OMU can receive a
response packet from the U2000, go to Step 3. Otherwise, check whether the router and
the U2000 are properly connected.
Step 3 Create the BSC6900 on the U2000. For details, see the information about how to create an NE
in the U2000 documentation.
NOTICE
l If a firewall exists between the BSC6900 and U2000, enable the communication ports
connecting the BSC6900 and U2000 to ensure proper communication between the
BSC6900 and U2000.
l For details on the ports connecting the BSC6900 and U2000, see 18.1 Communication
Ports on the BSC6900.
l The MTU value configured for the transmission equipment between the BSC6900 and the
U2000 must be no less than that configured for the OMU board of the BSC6900.
Otherwise, the communication between the BSC6900 and the U2000 may be abnormal.
The default MTU value for the OMU board is 1500.
l You are advised to run the SET CONNTYPE command with Connection Type set to
ONLY_SSL(Only SSL Connection) to enhance network transmission security.
----End
Example
Table 10-1 describes how to configure a route between the BSC6900 and the U2000.
Table 10-1 Configuring a route from the BSC6900 to the U2000
Scenar
io
The IP address of the U2000 server is 10.11.100.23. The mask is

255.255.255.255. The OMU is connected to the U2000 network segment through
the router. The IP address of the router is 192.168.139.10.

40
BSC6900 UMTS
Commissioning Guide
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 192.168.139.10.
2. Run the Secure Shell (SSH) terminal, such as PuTTY, to log in to the OMU.
3. Run the ping 192.168.139.10 command to check whether the network
connectivity between the BSC6900 and router is available.
4. Run the ping 10.11.100.23 command to check whether the network
connectivity between the BSC6900 and U2000 is available.
Follow-up Procedure
If the CME method is used to configure the data, it is necessary to complete the configuration
through the U2000.

41
BSC6900 UMTS
Commissioning Guide
11
Connecting to Operator's PKI System
This section describes how to connect the BSC6900 to operator's CA server so that the
BSC6900 can automatically manage its own digital certificates.
Prerequisites
l
The operator has the public key infrastructure (PKI) system.
The route from the operator's PKI system to the external IP address is available.
You have completed the operations provided in section 10 Connecting to the U2000.
The OMU board must be configured with an identification-capable device certificate so

that the base station controller can connect to the operator's PKI system for automatic
digital certificate management.
Operators have purchased licenses for feature WRFD-160276 RNC Supporting PKI.
Procedure
Step 1 Configure Huawei root certificate as the trust certificate on the operator's CA server. If the
operator's CA server works in the active/standby mode, configure Huawei root certificate as
the trust certificate on both the active and standby CA servers.
Step 2 Check whether the base station controller has the identification-capable device certificate.
1.
Run the MML command LST APPCERT to query information about the device
certificate of the base station controller.
l If Certificate File Name is usercert.pem in the command output, the device
certificate is pre-installed by Huawei.
l If Certificate File Name is hwusercert.pem in the command output, the device
certificate is pre-installed by Huawei and bound to the ESN of the OMU board. Go to
Step 4.
l If Certificate File Name is any other value in the command output, go to Step 2.2.
l If the command output displays no information about the device certificate, go to
Step 3.
2.
Run the MML command DSP APPCERT to check whether the device certificate is
issued by the operator's CA server.
l If the device certificate is issued by the operator's CA server, the device certificate is
unique. Go to Step 5.

42
BSC6900 UMTS
Commissioning Guide
l If the device certificate is not issued by the operator's CA server, the device
certificate is issued by other CA server. Go to Step 4.
Step 3 Apply for the certificate issued by the operator's CA server on the U2000.
1.
Run the following MML commands to install the certificate files required by the
BSC6900:
l Run the MML command MOD CERTREQ to configure the certificate request
template.
l Run the MML command CRE CERTREQFILE to generate a certificate request file.
l To apply for a digital certificate, run the MML command ULD CERTFILE to
download the local digital certificate from the CA center according to the local
certificate quest file that is sent to the CA center. You can also copy the digital
certificate from the CA center using a USB flash drive.
2.
Apply for the device certificate from the operator's CA server on the U2000. In this step,
the U2000 manually submits a certificate update request file to the operator's CA server
to apply for the operator's device certificate and the operator's CA server manually sends
the operator's device certificate to the U2000.
3.
Run the MML command DLD CERTFILE to download the operator-issued trust
certificate from the U2000.
4.
Run the MML command ADD TRUSTCERT to add the trust certificate issued by the
operator's CA server.
5.
Run the MML command DLD CERTFILE to download the device certificate from the
U2000.
6.
Run the MML command ADD CERTMK to add the device certificate to the base
station controller.
7.
On the U2000, choose Security > Certificate Authentication Management >

Certificate Management. On the displayed Certificate Management tab page, select
the obtained operator certificate and click Tset to check whether an SSL connection to
the U2000 can be successfully set up using the certificate.
8.
Run the MML command MOD APPCERT to configure the certificate.
9.
Go to Step 5.
Step 4 The base station controller applies for the device certificate from the operator's CA server.
1.
Run the MML command MOD CERTREQ to configure the certificate request template.
2.
Run the MML command ADD CA to add configurations of the operator's CA server. If
the operator's CA server works in the active/standby mode, add configurations of both
the active and standby CA servers to CA information to guarantee reliability in
certificate application and update.
3.
Run the MML command REQ DEVCERT to apply for the certificate issued by the
operator's CA server.
4.
On the U2000, choose Security > Certificate Authentication Management >

Certificate Management. On the displayed Certificate Management tab page, select
the obtained operator certificate and click Tsetto check whether an SSL connection to the
U2000 can be successfully set up using the certificate.
5.
Run the MML command MOD APPCERT to configure the certificate.
6.
Go to Step 5.
Step 5 Start the base station controller device certificate automatic check task to automatically
update the certificate.

43
BSC6900 UMTS
Commissioning Guide
1.
Run the MML command SET CERTCHKTSK to set a periodic certificate validity
checking task.
2.
Optional: Run the MML command DLD CERTFILE to download the operator's CRL
certificate from the certificate and CRL storage device of the operator.
3.
Optional: Run the MML command ADD CRL to set CRL information.
4.
Optional: Run the MML command SET CRLPOLICY to set the CRL policy.
5.
Optional: Run the MML command ADD CRLTSK to set a periodic CRL downloading
task.
NOTE
The current base station controller supports only the LDAPv3 protocol. Therefore, if the CRL is
updated using the LDAP, ensure that the CRL server supports the LDAPv3 protocol.
----End

44
12 Setting the Connection Mode Between the U2000 and

BSC6900 to SSL
BSC6900 UMTS
Commissioning Guide
12
Setting the Connection Mode Between

the U2000 and BSC6900 to SSL
The connection mode between the U2000 and BSC6900 must be set to Secure Socket Layer
(SSL) on the U2000 to ensure operation and maintenance (O&M) safety.
Prerequisites
l
The BSC6900 and peer equipment are physically connected and both have passed the
hardware installation acceptance.
All the subracks of the BSC6900 are running normally.
Using the LMT.
One of the following conditions must be met:

You have applied for an SSL safety certificate from the Certificate Authority (CA).
You have accessed the operator's PKI system.
You directly use Huawei pre-installed digital certificate.
Procedure
Step 1 If you have applied for an SSL safety certificate from the CA but do not access the operator's
PKI system or use Huawei pre-installed digital certificate, import and activate the obtained
certificate on the U2000.
1.
Import a CA certificate to the BSC6900. For details about how to import a CA

certificate, see section "Importing CA Certificates" in U2000 Data Management User
Guide under U2000 Product Documentation.
2.
Install a device certificate on the BSC6900. For details about how to install a device
certificate, see section "Manually Installing a Device Certificate" in U2000 Data
Management User Guide under U2000 Product Documentation.
Step 2 Set the connection mode between the U2000 and BSC6900 to SSL.
1.
On the U2000 client, choose Security Management > NE Security > Certificate
Authentication Management > SSL Connection Management (application style) or
Security > Certificate Authentication Management > SSL Connection Management
(traditional style).

45
12 Setting the Connection Mode Between the U2000 and

BSC6900 to SSL
BSC6900 UMTS
Commissioning Guide
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.
NOTE
When the SSL configuration is modified on the U2000, the U2000 sends a command to the BSC6900 to
synchronize its SSL configuration.
----End

46
BSC6900 UMTS
Commissioning Guide
13
Verifying Interfaces
About This Chapter

This section describes how to verify interfaces on the BSC6900 side using the LMT or
U2000. Select a verification method based on the onsite situation.
13.1 Verifying Interfaces on the U2000
This section describes how to verify interfaces by setting engineering modes and performing
an NE health check on the U2000.
13.2 Verifying Interfaces on the LMT
This chapter describes how to verify interfaces on the BSC6900 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, Iur-p, Sr interfaces. The Iur interface
verification is mandatory when the BSC6900 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. The Sr interface verifications is mandatory when the RNC
connects to the eCoordinator in the coordinating features.

47
BSC6900 UMTS
Commissioning Guide
13.1 Verifying Interfaces on the U2000

This section describes how to verify interfaces by setting engineering modes and performing
an NE health check on the U2000.
13.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 U2000
client or by running MML commands on the U2000 or LMT.
Prerequisites
l
Using the LMT.
An NE can work in the following engineering modes: NORMAL, INSTALL,

EXPAND, UPGRADE, and TESTING. The NE mode of the BSC6900 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 U2000 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 U2000.
Setting the NE engineering mode by using the GUI on the U2000 client
Procedure
1.
On the U2000 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 BSC6900 NE that needs to be set, and
then set NE Mode to TESTING. A window is displayed, as shown in Figure 13-1.

48
BSC6900 UMTS
Commissioning Guide
Figure 13-1 Setting the NE engineering mode to TESTING
Setting the NE engineering mode by running MML commands on the U2000 or LMT
1.
On the U2000 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 U2000 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 U2000 Operator Guide.
13.1.2 Verifying Interfaces Automatically

This section describes how to use an NE health check on the U2000 to automatically verify
the BSC6900 interfaces.
Prerequisites
l
You have completed the operations provided in chapter 10 Connecting to the U2000.

49
BSC6900 UMTS
Commissioning Guide
Context
The internal interface must be verified by using MML commands on the LMT. For details, see
13.2.2 Verifying Internal Interfaces.
Procedure
Step 1 Specify a scenario for an NE health check.
1.
On the U2000 client, choose Trace and Maintenance > Monitor > NE Health Check
(application styles) or Maintenance > Network Health Check > NE Health Check
(traditional styles).
2.
on the displayed tab page. The Scenario Management dialog box is

Click
displayed.
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.
NOTE
The scenario name must be different from existing scenario names.
5.
Select an NE type for health check from NE Types, that is, BSC6900 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.

1.
On the NE Health Check tab page, click the

displayed.
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, select the task execution mode. The following table lists the
options. Click Finish to select the instant execution mode.
. The Create Task dialog box is
Option
Description
Instant execution
Click Next. The Time Setting dialog box

is displayed. Click Finish.
NOTE
The setting of Time Setting is not required
during commissioning.
Scheduled execution
Set the time for executing the task in the

Scheduled spin box. Click Next. Set
Health Check Period in the displayed
dialog box, and then click Finish.
Periodic execution
Click Next. Set Start Time, Period, and

Run Times, and then click Finish.

50
BSC6900 UMTS
Commissioning Guide
NOTE
The executed health check tasks are listed under the Finished Tasks node in the navigation tree on the
left side.
Step 3 View 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.
If...
Then...
You select the HTML format
Select the report from the report list, and then view
the report in one of the following ways:
l Click the report to directly open the report in
HTML format. Click Open to open the report in
the HTML format.
l Click Save As, and then select the path for
saving the report in the displayed Save dialog
box to save the report in HTML format.
You select the DOC format
Click Save As, and then select the path for saving
the report in the displayed Save dialog box to save
the report in DOC format.
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
13.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 U2000 client or by running MML
commands on the U2000 or LMT. Alarms are reported when the NE works in NORMAL
mode.
Prerequisites
l
You have completed the operations provided in section 13.1.1 Setting the NE
Engineering Mode to TESTING before interface verification.
The BSC6900 has passed the commissioning.

51
BSC6900 UMTS
Commissioning Guide
Procedure
l
Setting the NE engineering mode by using the GUI on the U2000 client
1.
On the U2000 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 BSC6900 NE to be set, and set NE
Mode to NORMAL, the window shown in Figure 13-2 is displayed.
Figure 13-2 Setting the NE engineering mode to NORMAL
Setting the NE engineering mode by running MML commands on the U2000 or LMT
1.
On the U2000 or the LMT client, run the MML command SET MNTMODE, and
set Maintenance Mode to NORMAL(NORMAL).
----End
13.2 Verifying Interfaces on the LMT

This chapter describes how to verify interfaces on the BSC6900 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, Iur-p, Sr interfaces. The Iur interface
verification is mandatory when the BSC6900 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. The Sr interface verifications is mandatory when the RNC
connects to the eCoordinator in the coordinating features.

52
BSC6900 UMTS
Commissioning Guide
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 query the value of the Adjacent Node ID parameter.
13.2.1 Verifying Fiber Optic Cable Connections

This section describes how to verify whether fiber optic cables are connected properly. 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 BSC6900 is operating properly and has
been connected to the transmission equipment with fiber optic cables.
Using the LMT.
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 13-3 shows the fiber optic cable connections.

53
BSC6900 UMTS
Commissioning Guide
Figure 13-3 Fiber optic cable connections
----End
13.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 SCUa/SCUb boards.
Prerequisites
l
The BSC6900 Inter-SCUa/Inter-SCUb network cables have been installed.
Using the LMT.

54
BSC6900 UMTS
Commissioning Guide
Procedure
Step 1 Run the MML command DSP PANELPORT to query the link status of the ports on the
SCUa/SCUb boards.
Expected result: The command output shows the actual status of links to the ports on the
SCUa/SCUb boards.
If the status in the command output does not meet the installation requirements, reinstall the
inter-SCUa/SCUb network cables by referring to Installing the Inter-SCUb SFP+ High-Speed
Cables Between Different Subracks and . Reinstalling Inter-SCUa/SCUb Network Cables in
the BSC6900 UMTS Installation Guide.
----End
13.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 BSC6900 and base station are physically connected and both have passed the
The cell under the base station for the Iub interface verification has been configured.
Using the LMT.
Context
The following takes one base station as an example to describe the verification process on the
Iub interface during the commissioning of the BSC6900. 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 17.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 17.7 Signaling Link Failure
on the Iub Interface for troubleshooting.

55
BSC6900 UMTS
Commissioning Guide
3.
Run the MML command DSP ADJNODE to query the status of the adjacent node.
Available and the values of available bandwidths 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 bandwidths are all 0, see EVT-22918 Change of Transport Resource State
for Adjacent Node User Plane 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 17.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 17.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 17.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 17.6 Cell Setup Failure for
troubleshooting.
Verifying the Iub Interface (over IP)

1.
Run the MML command DSP SCTPLNK to query the status of a Stream Control
Transmission Protocol (SCTP) link.
Normal.
If the value of Operation state is not Normal, see 17.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.
interface.
Available.
3.
Expected result: The command output shows that the values of available
bandwidths cannot be all 0.

56
BSC6900 UMTS
Commissioning Guide
If the values of available bandwidths are all 0, see EVT-22918 Change of Transport
Resource State for Adjacent Node User Plane for troubleshooting.
4.
Run the MML command DSP IPPATH to query the status of the IP path on the Iub
interface.
Available.
5.
troubleshooting.
Verifying the Iub Interface (over Transmission Resource Pool)

1.
Optional: Run the LST UIUBCP command to query the SCTP link ID that
corresponds to the NCP and CCP to a NodeB of which the control-plane parameters
are self-planned.
2.
Run the MML command DSP SCTPLNK to query the status of an SCTP link.
Normal.
NOTE
3.
interface.
Available.
4.
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.
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.
5.
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.

57
BSC6900 UMTS
Commissioning Guide
If the value of Detection Status is not Normal, see 17.8 AAL2/IP Connection
6.
troubleshooting.
Verifying the Iub interface (over ATM/IP Dual Stack)

Verify the Iub interface over ATM and over IP, respectively.
----End
13.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 Iu-CS interface.
Prerequisites
l
For R99 networking on the Iu-CS interface: the BSC6900 and MSC are been physically
connected, and the MSC is running properly.
For R4 networking on the Iu-CS interface: the BSC6900, 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 properly.
Using the LMT.
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.
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.

58
BSC6900 UMTS
Commissioning Guide
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 Inaccessible, see ALM-21521 SCCP Subsystem
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 bandwidths are all 0, see EVT-22918 Change of
Transport Resource State for Adjacent Node User Plane 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 17.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 17.3 Verifying the PVC Delay
Detection Function.
Verifying the Iu-CS Interface (over IP)

1.
Normal.

59
BSC6900 UMTS
Commissioning Guide
NOTE
2.
Run the MML command DSP M3LNK to query the status of an MTP3-User
Adaptation Layer (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.
6.
CS_DOMAIN.
not CS_DOMAIN, Run the MML command ADD UCNNODE to configure the
7.
Run the MML command DSP IPPATH to query the status of the IP path on the IuCS interface.
Available.
Verifying the Iu-CS Interface (over Transmission Resource Pool)

1.
Normal.

60
BSC6900 UMTS
Commissioning Guide
NOTE
2.
Run the MML command DSP M3LNK to query the status of an M3UA link.
Active.
3.
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.
CS_DOMAIN.
not CS_DOMAIN, run the MML command ADD UCNNODE to configure the
----End

61
BSC6900 UMTS
Commissioning Guide
13.2.5 Verifying the Iu-PS Interface

This section describes how to verify the control plane and user plane on the Iu-PS interface.
The method for verifying the Iu-PS interface varies depending on the transmission mode on
the Iu-PS interface.
Prerequisites
l
The BSC6900 and SGSN are physically connected and both have passed the hardware
installation acceptance.
The SGSN used to verify the Iu-PS interface is operating properly.
Using the LMT.
Verifying the Iu-PS Interface (over ATM)
Procedure
1.
Available.
2.
Available.
3.
Allowed.
4.
signaling point.
Accessible.
5.

62
BSC6900 UMTS
Commissioning Guide

6.
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
7.
Run the MML command PING IP to check whether the connection to the SGSN is
normal.
Expected result: The IP address can be pinged.
If the IP address cannot be pinged, check whether a firewall is configured at the
peer end. If a firewall does not exist, perform virtual channel link (VCL) continuity
check on all the IP over ATM (IPoA) permanent virtual connections (PVCs) on the
Iu-PS interface. For details, see 17.2 Performing a VCL Continuity Check and
17.3 Verifying the PVC Delay Detection Function.
Verifying the Iu-PS Interface (over IP)

1.
Normal.
NOTE
2.
Active.
3.
Allowed.
4.
signaling point.
63
BSC6900 UMTS
Commissioning Guide
Accessible.
5.
6.
PS_DOMAIN.
not PS_DOMAIN, run the MML command ADD UCNNODE to configure the
7.
Run the MML command DSP IPPATH to query the status of the IP path on the IuPS interface.
Available.
Verifying the Iu-PS Interface (over Transmission Resource Pool)

1.
Normal.
NOTE
2.
Active.
3.
Allowed.

64
BSC6900 UMTS
Commissioning Guide

4.
signaling point.
Accessible.
5.
Run the MML command DSP ADJNODEDIP to query the destination IP address
information of an adjacent node.
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.
PS_DOMAIN.
not PS_DOMAIN, Run the MML command ADD UCNNODE to configure the
----End
13.2.6 Verifying the Iur Interface

This section describes how to verify the control plane and user plane on the Iur interface when
the BSC6900 is connected to the RNC. The method for verifying the Iur interface varies
depending on the transmission mode.
Prerequisites
l
The BSC6900 and RNC are physically connected and both have passed the hardware
installation acceptance.
The RNC used to verify the Iur interface is operating properly.
Using the LMT.

65
BSC6900 UMTS
Commissioning Guide
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.
Links.
2.
Available.
3.
Allowed.
4.
signaling point.
Accessible.
5.
6.
the Iur interface.
Available.

66
BSC6900 UMTS
Commissioning Guide
7.
Optional: If the BSC6900 is configured with an IP path to the RNC, run the MML
command PING IP to check whether the connection to the RNC is correct.
Expected result: The IP address can be pinged.
If the IP address cannot be pinged, check whether a firewall is configured at the
peer end. If a firewall does not exist, perform virtual channel link (VCL) continuity
check on all the IP over ATM (IPoA) permanent virtual connections (PVCs) on the
Iur interface. For details, see 17.2 Performing a VCL Continuity Check and 17.3
Verifying the PVC Delay Detection Function.
Verifying the Iur Interface (over IP)

1.
Normal.
Links.
NOTE
is always Normal and the value of State Changed Time does not change, the Stream Control
Transmission Protocol (SCTP) link does not disconnect intermittently.
2.
Active.
3.
Allowed.
4.
signaling point.
Accessible.
5.
6.
Run the MML command DSP IPPATH to query the status of the IP path on the Iur
interface.
67
BSC6900 UMTS
Commissioning Guide
Available.
l
Verifying the Iur Interface (over Transmission Resource Pool)

1.
Normal.
Links.
NOTE
2.
Run the MML command DSP M3LNK to query the status of an M3UA link.
Active.
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.
Normal.

68
BSC6900 UMTS
Commissioning Guide
----End
13.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.
Prerequisites
l
The BSC6900 and CBC have been physically connected, and both have passed the
Using the LMT.
Procedure
Step 1 Run the PING IP command to query the connectivity between the BSC and CBC. 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 BSC6900 and CBC
are correctly configured.
----End
13.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 RNC used to verify the Iur-g interface is operating properly.
Using the LMT.
Verifying the Iur-g interface (intra-RNC)
Procedure
1.
Run the DSP BRD command to query the status of a board.

69
BSC6900 UMTS
Commissioning Guide
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.
l
Verifying the Iur-g interface (inter-RNC)

1.
Run the MML command DSP SCTPLNK to query the status of the Stream Control
Expected result: The value of Operation state is Normal.
If the value of Operation state is not Normal, see operations in 17.1 Checking
Transmission Links.
NOTE
2.
Expected result: The value of Operation state is Active.
3.
Allowed.
4.
Run the MML command DSP N7DPC to query the status of the SS7 destination
signaling point.
Accessible.
----End
13.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
The BSC6910 and BSC6900 are physically connected and both have passed the
The BSC6900 or BSC6910 used to verify the Iur-p interface is operating properly.

70
BSC6900 UMTS
Commissioning Guide
Using the LMT.
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 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 SPU board depends on its logical function type. The SPUa
board supports three Iur-p links when its logical function type is RUCP and supports four Iur-p links
when its logical function type is UCP. The SPUb/SPUc board supports seven Iur-p links when its logical
function type is RUCP and supports eight Iur-p links when its logical function type is UCP.
If the value of Number of Fault IURP Link is not 0, see ALM-21606 IURP Link Fault for
troubleshooting.
Step 2 Run the MML command DSP ADJNODEDIP to query the destination address of an adjacent
node.
Expected result: If the command output shows the destination IP address information of an
adjacent node of the peer end.
If there is no destination IP address information, the peer end does not configure an adjacent
node, the verification is complete.
Step 3 Run the MML command DSP ADJNODEPING to query the status of the adjacent node.
Expected result: If the command output shows that the value of Detection Status is Normal.
If Detection Status is Fault, see 17.8 AAL2/IP Connection Setup Failure for
troubleshooting.
----End

71
BSC6900 UMTS
Commissioning Guide
13.2.10 Verifying the Sr Interface

This section describes how to verify the Sr interface when the RNC connects to the
eCoordinator. The Sr interface is dedicated for the coordinating features.
Prerequisites
l
The BSC6900 and eCoordinator are physically connected and both have passed the
The Sr interface has been configured.
Using the LMT.
Procedure
Step 1 Run the MML command DSP SCTPLNK to query the status of a Stream Control
Expected result: The value of Operation state is Normal.
If the value of Operation state is not Normal
l If the coordination service is not configured within the RNC, see operations in 17.1
Checking Transmission Links.
l If the coordination service is configured within the RNC, check whether the data
configuration on the interface is correct.
Step 2 Run the MML command DSP UECOCONN to query the status of the communication link.
Expected result: The value of Operation state is Available.
If the value of Operation state is Unavailable, check whether the data configuration on the
interface is correct.
----End

72
14 Handling the Alarms Generated During the

Commissioning
BSC6900 UMTS
Commissioning Guide
14
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 BSC6900 and OMU is normal.
Using the LMT.
Procedure
Step 1 Click Alarm/Event on the LMT home page. The BSC6900 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
No further action is required.
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 Step 3 through Step 5 to handle other alarms.
----End

73
BSC6900 UMTS
Commissioning Guide
15
Verifying UMTS Services
This section describes how to verify that the basic UMTS services and the feature services are
normal. The basic UMTS services are speech services and data services. Feature services
include inter-RAT handovers, HSDPA, HSUPA, 64QAM, MIMO, CBS, and DC-HSDPA.
Prerequisites
l
The BSC6900 has passed the commissioning.
The commissioning over the Iub, Iu-CS, Iu-PS, Iur, Iu-BC, Iur-g, and Iur-p interfaces is
successful.
Test UEs are functional and have registered with the HLR.
Using the LMT.
Procedure
Step 1 Verify basic UMTS services with test UEs in NodeB cells by following operations listed in
Table 15-1.
Table 15-1 Operations for verifying basic UMTS services with test UEs in NodeB cells
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 properly after the
call is terminated.
Make 20 calls from a fixedline phone to a test UE and

hold on each call for 60
seconds.

call is terminated.

74
BSC6900 UMTS
Commissioning Guide
Service Type
Data service
Operation
Expected Result

UE to another test UE and
seconds.

call is 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
properly.

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, UE Trace, and Cell Trace.
Step 2 Verify feature services with the test UEs in NodeB cells by following operations listed in
Table 15-2.
Table 15-2 Operations for verifying feature services with test UEs in NodeB cells
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.

75
BSC6900 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.

is 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

76
BSC6900 UMTS
Commissioning Guide
16
Verifying Network Reliability
The network reliability can be verified by checking generated alarms and making dialing tests
after a switchover between the active/standby boards.
Prerequisites
l
The standby board to be switched over is operating properly.
Using the LMT.
The alarms generated before the switchover have been cleared.
Procedure
Step 1 Switch over the OMU boards. For details, see Switching Over BSC Boards in the BSC6900
UMTS LMT User Guide.
Step 2 Check and handle the alarms generated during the switchover. For details, see 14 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 16-1.
Table 16-1 Operations for verifying basic UMTS services with test UEs in NodeB cells
Service Type
Operation
Expected Result
Speech service

UE to a fixed-line phone
and hold on each call for 60
seconds.

call is terminated.

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

seconds.

call is terminated.

UE to another test UE and
seconds.

call is 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.

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

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

higher than 95%.
----End

78
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
17
Troubleshooting
About This Chapter

This chapter describes how to troubleshoot common problems during the commissioning.
17.1 Checking Transmission Links
This section describes how to verify that terrestrial transmission links of the BSC6900 are
functional. The verification covers E1/T1 ports, FE/GE ports, optical ports, upper-layer links,
and the QCIs of the IP transmission link.
17.2 Performing a VCL Continuity Check
This section describes how to perform a virtual channel link (VCL) continuity check on links
over interfaces.
17.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.
17.4 Unavailable E1/T1 Port
This section describes how to troubleshoot an unavailable E1/T1 port. The
17.5 Unavailable FE/GE Port
This section describes how to troubleshoot an unavailable FE/GE port.
17.6 Cell Setup Failure
This section describes how to handle cell setup failures.
17.7 Signaling Link Failure on the Iub Interface
This section describes how to troubleshoot a signaling link failure on the Iub interface.
17.8 AAL2/IP Connection Setup Failure
This section describes how to troubleshoot an AAL2/IP connection setup failure based on the
actual transmission mode.
17.9 Data Loading Failures on the Board
This section describes how to troubleshoot failures that occur during data loading to a
BSC6900 board.
17.10 Performing a Loopback Test on the Local E1/T1 Port

79
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
This section describes how to check whether E1/T1 ports are functional by performing
loopback tests on the E1/T1 links carried by the electrical port.
17.11 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.
17.12 Checking the QCIs of the IP Transmission Link
This section describes how to perform the active test to check whether the QoS class
identifiers (QCIs) of the interface-based IP transmission meet the requirements. QoS is short
for quality of service.

80
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
17.1 Checking Transmission Links

This section describes how to verify that terrestrial transmission links of the BSC6900 are
functional. The verification covers E1/T1 ports, FE/GE ports, optical ports, upper-layer links,
and the QCIs of the IP transmission link.
Prerequisites
l
Using the LMT.
Check the status of physical transmission links based on the transmission scheme.
Procedure

81
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
Table 17-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. Optional: If the channelized

STM-1 transmission is used on
the interface, 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 upperlayer 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
mode, run the MML
command DSP UNILNK to
check the status of a UNI
link.
l For the FRA transmission
mode, run the MML
command 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
Check the status of an optical

port.

82
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
If the transmission scheme on the

interface is...
Then...
IP
1. Optional: If the channelized

STM-1 transmission is used on
the interface, check the status of
an optical port.
PPP/MLPPP
2. Check the status of an E1/T1

port.
3. Check the status of an upperlayer link.
l For the PPP transmission
mode, run the MML
command DSP PPPLNK to
check the status of a PPP
link.
l For the MLPPP transmission
mode, run the MML
command DSP MPGRP to
check the status of an MLPPP
group.
NOTE
If the upper-layer link is not
functional, run the MML
command LST PPPLNK or
LST MPGRP to check whether
the data configuration on the
interface is correct.
IP over Ethernet
Check the status of an FE/GE

port.
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 17.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 17.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

three-layer networking applies).
83
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
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
17.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
Using the LMT.
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, andCC
activated failure alarm are all Normal.

84
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
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
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
suggestions.
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
suggestions.

85
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
3.

Link type set to IPOAPVC.
----End
17.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
Using the LMT.
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.
Verify the PVC delay detection function on the SAAL link.
Context
Procedure
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.
86
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
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.
Enable the function of monitoring the real-time performance of the PVC link using
the LMT.
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.

87
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
Max Time Delay[ms]

Min Time Delay[ms]
4.
Enable the function of monitoring the real-time performance of the PVC link using
the LMT.
a.
b.

c.

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

This section describes how to troubleshoot an unavailable E1/T1 port. The
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 for an E1/T1 port, handle the problem as follows:
l When electrical ports serve as the bearers, perform the E1/T1 loopback test on all the
faulty E1/T1 ports. For details, see 17.10 Performing a Loopback Test on the Local
E1/T1 Port.
l When optical ports serve as the bearers, perform the group loopback test on all the
faulty E1/T1 ports. For details, see 17.11 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-21201 E1/T1 Loss of Signal
l ALM-21294 SDH/SONET TU Signal Loss
l ALM-21261 SDH/SONET LP Remote Defect Indication
l ALM-21202 E1/T1 Loss of Frame Alignment
l ALM-21275 SDH/SONET Tributary Loss of Frame
l ALM-21241 Loss of Fractional IMA Frame
l ALM-21203 E1/T1 Remote Alarm Indication Signal
l ALM-21286 SDH/SONET Tributary Remote Alarm Indication Signal
l ALM-21205 E1/T1 Loss of Multiframe Alignment

88
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
l ALM-21288 SDH/SONET Tributary Loss of Multiframe

l ALM-21204 E1/T1 Alarm Indication Signal
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.
17.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:
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
17.6 Cell Setup Failure

This section describes how to handle cell setup failures.
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.

89
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
Fault Locating Policy
NOTICE
l If Iub over ATM is applied, check whether the alarms related to the DPUb/DPUe, DSP,
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 DPUb/DPUe, DSP, 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 them as follows:
l If Iub over ATM/IP dual-stack is applied, check whether the alarms related to the DPUb/
DPUe, DSP, 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 them as follows:
To narrow down the fault location, determine whether the NodeB or the BSC6900 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 17-1 and Figure 17-2 show the procedures for locating cell setup failures.

90
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
Figure 17-1 Locating cell setup failures (1)
Table 17-2 Operation index (1)

Index
Operation
Step
*1-1
Check whether the Iub link

works properly.
See 17.1 Checking Transmission

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

interface.
See 17.7 Signaling Link Failure on

the Iub Interface.

91
BSC6900 UMTS
Commissioning Guide
17 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 DSP

resources are available.
l Run the MML command DSP DSP

to query the number of available
DSPs on a DPUb board. Perform
this action on all the DPU boards.
The sum of the results is the number
of available DSPs.
l The number of cells that can be set
up is 15 times the number of DSPs.
If the calculated cell number is
smaller than the number of cells that
are currently set up, the DSP
resources are insufficient.
*1-7
Check whether the TNL

resources are available.
See Solution 6: Checking TNL

Resources.
Figure 17-2 Locating cell setup failures (2)

92
BSC6900 UMTS
Commissioning Guide
17 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 17.1 Checking Transmission

Links.
*2-3
Handle link failures on the

Iub interface.
See 17.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 17.2 Performing a
VCL Continuity Check.
l For IP transmission, check whether
the IP link setup is successful.
1. Run the MML command DSP
IPPATH to query the status of
the IP path.
2. Optional: If the transmission
resource group is configured, run
the MML command DSP
RSCGRP to query the status of
the transmission resource groups.
*2-5
Handle the AAL2/IP link

setup failures.
See 17.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.

93
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
Solution 2: Unblocking Cells

l
If the cell is blocked by the BSC6900, 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.
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.
Run the MML command LST IPPATH 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.
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.

94
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
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.
Run the MML command LST IPPATH 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.
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 (non-IP Pool) transmission mode, run the MML command LST IPPATH to check
the configuration of the IPPATH of the adjacent node.
4.
In IP Pool mode, run the MML command DSP IPPOOLPM to check the IP status of the
adjacent node.
5.
Run the MML command LST TRMMAP to check whether the AAL2 path and IPPATH
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 and
IPPATH do not exist, add the associated AAL2 path and IPPATH. If the bandwidth does
not meet the requirements of the common channel, add an AAL2 path and IPPATH or
modify the configuration of the AAL2 path and IPPATH.
17.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 DPUb/DSP board are
not reported.
Solution
1.
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 17-3.

95
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
Figure 17-3 Troubleshooting signaling link failures on the Iub interface over ATM
transmission
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 17.4 Unavailable E1/T1 Port.

96
BSC6900 UMTS
Commissioning Guide
17 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 17-3.
2. Run the MML command LST E1T1 to check the
coding schemes are consistent between the two
ends.
3. Run the MML command LST IMAGRP to
check the IMA protocol version configurations
are consistent between the two ends.
*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.
For Iub over IP transmission, check whether alarms related to the E1/T1 port, 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 17-4.

97
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
Figure 17-4 Handling of signaling link failures on the Iub interface over IP transmission

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 17.1 Checking Transmission Links.
*2-4
Handle the
transmission link
failure.
1. If the data is transmitted over Ethernet, for

example, through the FE port, see 17.5
Unavailable FE/GE Port.
2. If the data is transmitted over a private line, for
example, over E1/T1 links, see 17.4
Unavailable E1/T1 Port.
3.
*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 17-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.
If the control-plane parameters are self-planned in Iub over IP scenarios, troubleshoot

signaling link faults according to Figure 17-5.

98
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
Figure 17-5 Handling of signaling link failures on a NodeB for which the control-plane
parameters are self-planned in Iub over IP scenarios

Index
Operation
Step
*3-1
Handle alarms.
Check for ALM-22244 Configuration Between

Related NE Dismatch and ALM22245: NodeB
Signal Interface Create fail.
If the alarm exists, handle it by referring to the
Alarm Reference. Otherwise, go to *3-2.
*3-2
Query the upperlayer applications.
Run the LST UIUBCP command to check

whether the NCP and CCP are configured for the
NodeB.
If yes, handle the signaling link failure by referring
to Figure 17-4.
Otherwise, go to *3-3.
*3-3
Delete redundancy
configurations.
Run the LST UIUBCP command to check

whether the NodeB CCP configuration exceeds the
processing capability.
If yes, run the RMV UCCP command to remove
the faulty CCP.
Otherwise, go to *3-4.

99
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
Index
Operation
Step
*3-4
Modify the data

configuration.
The following describes the operation procedure.

1. Check whether the NCP and CCP are
configured on the NodeB.
l If the NCP and CCP are not configured, run
the ADD UNCP command and the ADD
UCCP command to add upper-layer
configurations to the SCTP link.
l If the NCP and CCP are configured, go to
the next step.
2. Run the LST SCTPLNK command on the
NodeB side, and the LST SCTPSRV command
on the RNC side to check whether the IP
address and port number on the NodeB side is
consistent with these on the RNC side.
l If they are not consistent, run the MOD
SCTPLNK command on the NodeB side
and the MOD SCTPSRV command on the
RNC side to change the data configurations
according to the data planning.
l If they are consistent, go to the next step.
*3-5
Handle the
transmission link
failure.
On the Web LMT, perform SCTP trace based on

the IP address pair to check whether the NodeB
can successfully send a signaling message to the
RNC.
If the NodeB cannot send a signaling message to
the RNC, the transmission link is faulty.
1. If the data is transmitted over Ethernet, for
example, through the FE port, see 17.5
example, over E1/T1 links, see 17.4
Unavailable E1/T1 Port.
4.
For Iub over ATM/IP dual-stack transmission, troubleshoot the failures according to the
suggestions in the ATM transmission and IP transmission as required.
17.8 AAL2/IP Connection Setup Failure

This section describes how to troubleshoot an AAL2/IP connection setup failure based on the
actual transmission mode.
Fault Description
During an AAL2 or IP connection setup or cell setup, the AAL2 or IP link fails to be
established.

100
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
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 17-6.
Figure 17-6 Procedure for handling AAL2 connection setup failure
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 17-8.
*1-2
Handle link failures on

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

Interface.

101
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
Table 17-8 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
AAL2PATH
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.
When the user plane is over transmission resource pool, troubleshoot the setup failure on
the UMTS user plane according to Table 17-9.
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.

102
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
Index
Check Item
Operation
*2-3
Check whether
the peer IP
address is
normal.
Run the MML command DSP ADJNODEPING to

query the Detection Status of the adjacent node.
*2-4
*2-5
*2-6
*2-7
Check whether
the transmission
link is available.
l If the Detection Status is Normal, go to *2-4.

l If the Detection Status is not Normal, go to 17.5
See 17.1 Checking Transmission Links.
l If the transmission link is unavailable, go to *2-5.
l If the transmission link is available, go to 17.5
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 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.
When the user plane is over IP transmission, troubleshoot the setup failure on the user
plane according to Table 17-10.
Index
Check Item
Operation
*3-1
Determine the IP
path that carries
the common
channel.
Run the MML commands LST IPPATH and LST

TRMMAP to obtain the ID of the IP path that carries
the common channel.

103
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
Index
Check Item
Operation
*3-2
Check whether
the IP path is
available.
1. Run the MML command DSP IPPATH to query the

status of the IP path.
2. Optional: If any transmission resource group is
configured over the Iub interface, run the MML
command DSP RSCGRP to query the status of the
transmission resource group.
3. If all the IP paths are unavailable, go to *3-3.
*3-3
*3-4
Check whether
the transmission
link is available.
1. See 17.1 Checking Transmission Links.

2. If the transmission link is unavailable, go to *3-4.
3. If the transmission link is available, go to *3-5.
Handle the
transmission
link failure.
1. If the data is transmitted over Ethernet, for example,

through FE ports, see 17.5 Unavailable FE/GE Port.
*3-5
Check the
configuration of
the IP path.
Run the MML command LST IPPATH to check

whether the negotiated data is consistent. If
inconsistency exists, modify the negotiated data.
*3-6
Check the realtime IP route

information.
Run the MML command DSP IPRT to check the realtime IP route information.

example, over E1/T1 links, see 17.4 Unavailable
E1/T1 Port.
17.9 Data Loading Failures on the Board

This section describes how to troubleshoot failures that occur during data loading to a
BSC6900 board.
Fault Description
The status of a board on the device panel is abnormal when host software and data files are
being loaded to the BSC6900 board.
Solution
1.
Check the loading status of other boards in this subrack.
If...
Then...
Board status of other boards is

Normal
Replace the faulty board and then reload data to the

new board.
Board status of all the other

boards is Faulty
Go to 2.

104
BSC6900 UMTS
Commissioning Guide
2.
3.
4.
5.
6.
17 Troubleshooting
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 power cycle

the subrack to reset it for reloading.
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 *.*.3.50 and *.*.3.60. The internal IP address is related to
the configure of the MML command LST SUBNET.
If...
Then...
No
Correct the OMU internal subnet mask, internal IP

address, or the host SUBNET internal IP address,
and then power cycle all subracks to reset them for
reloading.
Yes
Go to 4.
If data loading on all boards in the EPS fails, check whether the 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.
If data loading on all boards in the EPS fails, run the LST SCUPORT command to
check whether configurations of panel ports between the EPS subrack and its upper-level
subrack are correct.
If...
Then...
Configurations of panel ports

are incorrect.
Correctly configure panel ports and load the

software to all boards in the EPS subrack.
Configurations of panel ports

are correct.
Go to 6.
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.

105
BSC6900 UMTS
Commissioning Guide
7.
8.
9.
17 Troubleshooting
If...
Then...
The type of the board is

correctly set
Go to 7.
If data loading on the SPUa/SPUb/SPUc board fails, run the MML command LST
URNCBASIC to check whether the BSC6900 basic data is properly set.
If...
Then...
The setting is incorrect
Correct the BSC6900 basic information and reload

data to the board.
The setting is correct
Go to 8.
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 9.
17.10 Performing a Loopback Test on the Local E1/T1 Port

This section describes how to check whether E1/T1 ports are functional by performing
loopback tests on the E1/T1 links carried by the electrical port.
Prerequisites
the LMT.
Context
l
The loopback test and the Bit Error Rate (BER) test cannot be performed simultaneously.
During a loopback test, services carried on the tested link will be interrupted.
The loopback test can be performed when an E1/T1 unavailable alarm is reported on an
E1/T1 port.
Procedure
Step 1 Perform the loopback test on the local E1/T1 port.

106
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
Table 17-11 Procedure for performing the loopback test on the local E1/T1 port
Step
Operation
1-1
Run the MML command SET E1T1LOP to set a loopback test on an E1/T1 port.
In this step, set Loop type to LOCAL_LOOP.
1-2
Run the MML command LOP E1T1 to start the loopback test on the E1/T1 port.
1-3
Run the MML command DSP E1T1LOP to query the result of the loopback test.
1-4
Run the MML command SET E1T1LOP to stop the loopback test on the E1/T1
port. In this step, set Loop type to NO_LOOP.
If...
Then...
The loopback test result is

Succeeded
The E1/T1 port is operational. Go to Step 2.
The loopback test result is Not

succeeded
The E1/T1 port is faulty. Replace the interface board

carrying the faulty E1/T1 port.
Step 2 Perform the loopback test on the local E1/T1 cable.

Table 17-12 Procedure for performing a loopback test on the local E1/T1 cable
Step
Operation
2-1
Perform E1/T1 physical loopback at the local end, that is, connect the TX end of
the E1/T1 cable to the RX end of the E1/T1 cable.
2-2
Run the MML command LOP E1T1 to start the loopback test on the E1/T1 port.
2-3
Run the MML command DSP E1T1LOP to query the result of the loopback test.
2-4
Stop the E1/T1 physical loopback at the local end.
If...
Then...

Succeeded
The E1/T1 cable is properly connected. Go to Step 3.

107
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
If...
Then...
The loopback test result is Not

succeeded
l Use a multimeter to measure the connectivity between

the connector pin of the E1/T1 cable and the inner
conductor of the coaxial cable and the connectivity
between the outer shell of the connector and the shield
layer of the coaxial cable. If a connectivity failure
occurs, make a new connector and assemble the cable
again.
l Use a multimeter to check whether the internal and
external conductors of the E1/T1 cable are shortcircuited. If so, make a new connector and assemble
the cable again.
If the fault persists, replace the E1/T1 cable with a new
E1/T1 cable.
Step 3 Perform the loopback test on the peer E1/T1 port.

Table 17-13 Procedure for checking the peer equipment or the transport network
Step
Operation
3-1
Run the MML command SET E1T1LOP at the local end to set a loopback test on
the remote E1/T1 port. In this command, set Loop type to
REMOTE_LOOP(REMOTE LOOP).
3-2
l If the peer equipment is the BSC6900, run the MML command LOP E1T1 at
the peer end to start the loopback test on the E1/T1 port, then run the MML
command DSP E1T1LOP at the peer end to query the result of the loopback
test.
l If the peer equipment is not the BSC6900, contact the maintenance personnel
for the peer equipment to query the result of the loopback test.
3-3
Run the MML command SET E1T1LOP at the local end to stop the loopback test
on the E1/T1 link. In this step, set Loop type to NO_LOOP(No loop).
If...
Then...

successful
Contact the Technical Support for Assistance.

unsuccessful
Contact the maintenance personnel for the peer equipment

to rectify faults in the peer equipment or the transport
network.
----End

108
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
17.11 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
the LMT.
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 17-14 Procedure for performing the loopback test on the SDH port
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).
If...
Then...
The command output shows that the

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

value 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 17-15 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.

109
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
Step
Operation
2-3
Stop the fiber optic cable physical loopback at the local end.
If...
Then...

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

Step 3.

value 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 17-16 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 BSC6900, 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 BSC6900, contact the maintenance personnel
for the peer equipment to query the state of the optical port.
3-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).
If...
Then...

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
17.12 Checking the QCIs of the IP Transmission Link

This section describes how to perform the active test to check whether the QoS class
identifiers (QCIs) of the interface-based IP transmission meet the requirements. QoS is short
for quality of service.

110
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
Prerequisites
l
Using the LMT.
The peer end (NodeB, MGW, MSC, or SGSN) supports the Two-Way Active
Measurement Protocol (TWAMP).
You have purchased the license of the TWAMP.
Procedure
Step 1 Enable the TWAMP and start the active test.
1.
Run the ADD TWAMPCLIENT command to add a client and configure the IP
addresses of the local and peer ends.
2.
Run the ADD TWAMPSENDER command to set the parameters for the active test.
After the command is successfully executed, the test is started.
Step 2 Run the DSP TWAMPSENDER command to query the test results.
Table 17-17 shows QCIs recommended on interfaces. Check whether the test results meet the
QCIs recommended on interfaces.
Table 17-17 QCIs recommended on interfaces
QCI
Delay
Jitter
Packet Loss Rate
Recommended value
on the Iub interface
10
0.01%
Maximum value on
the Iub interface
40
15
0.1%
Recommended value
on the Iu-CS
interface
10
0.01%
Maximum value on
the Iu-CS interface
15
0.1%
Recommended value
on the Iu-PS
interface
10
0.0001%
Maximum value on
the Iu-PS interface
15
0.1%
Recommended value
on the Iur interface
10
0.01%
Maximum value on
the Iur interface
15
0.1%
Recommended value
of satellite
transmission
300
20
0.05%

111
BSC6900 UMTS
Commissioning Guide
17 Troubleshooting
QCI
Delay
Jitter
Packet Loss Rate
Maximum value of
satellite transmission
350
40
0.05%
l If yes, no further action is required.

l If no, contact Huawei technical support.
----End

112
BSC6900 UMTS
Commissioning Guide
18 Appendix
18
Appendix
About This Chapter

This chapter provides communication ports on and the commissioning checklist of the
BSC6900.
18.1 Communication Ports on the BSC6900
This section describes communication ports on the BSC6900.
18.2 BSC6900 Commissioning Checklist
This section describes the BSC6900 commissioning checklist used to record and check the
BSC6900 commissioning results.

113
BSC6900 UMTS
Commissioning Guide
18 Appendix
18.1 Communication Ports on the BSC6900

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

This section describes the BSC6900 commissioning checklist used to record and check the
BSC6900 commissioning results.
For details, see BSC6900 Commissioning Checklist.

114

BSC6900 UMTS Commissioning Guide (V900R018C10 Draft A) (PDF) - EN PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSC6900 UMTS Commissioning Guide (V900R018C10 Draft A) (PDF) - EN PDF

Uploaded by

Copyright:

Available Formats

BSC6900 UMTS

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Issue Draft A (2015-12-31)

Huawei Proprietary and Confidential

About This Document

About This Document

Huawei Proprietary and Confidential

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

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 ">"

Huawei Proprietary and Confidential

About This Document

Press the keys concurrently. For example, pressing Ctrl

Press the keys in turn. For example, pressing Alt, A means

Select and release the primary mouse button without

Press the primary mouse button twice continuously and

Issue Draft A (2015-12-31)

Huawei Proprietary and Confidential

6 Logging In to the BSC6900 Using the LMT............................................................................ 26

10 Connecting to the U2000...........................................................................................................39

Huawei Proprietary and Confidential

13.2.4 Verifying the Iu-CS Interface.................................................................................................................................. 58

14 Handling the Alarms Generated During the Commissioning......................................... 73

Issue Draft A (2015-12-31)

Huawei Proprietary and Confidential

For details about the processes required when the

Issue Draft A (2015-12-31)

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

Requirements for the Network

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

Issue Draft A (2015-12-31)

Huawei Proprietary and Confidential

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

Requirements for Software and Data Files

Software installation package

MML script file

Issue Draft A (2015-12-31)

Huawei Proprietary and Confidential