BSC6900 GU Commissioning Guide - (V900R011C00 - 03)

BSC6900 GU
V900R011C00
Commissioning Guide
Issue 03
Date 2009-12-05
Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any
assistance, please contact our local office or company headquarters.
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
Copyright © Huawei Technologies Co., Ltd. 2009. 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 the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Proprietary and Confidential

BSC6900 GU
Commissioning Guide Contents
Contents
About This Document.....................................................................................................................1

1 Changes in BSC6900 GU Commissioning Guide................................................................1-1
2 Prerequisites for Commissioning...........................................................................................2-1
3 Commissioning Process............................................................................................................3-1
4 Verifying the Equipment..........................................................................................................4-1
4.1 Checking the Operating Status of the Hardware.............................................................................................4-2
4.2 Verifying the OMU.........................................................................................................................................4-2
4.3 Logging In to the BSC6900 Through the LMT..............................................................................................4-5
5 Updating the OMU Database..................................................................................................5-1

6 Activating and Verifying the License....................................................................................6-1
7 Loading BSC6900 Board Software and Data Files...............................................................7-1
7.1 Generating the Data File for the Loading........................................................................................................7-3
7.2 Setting the Loading Mode...............................................................................................................................7-3
7.3 Resetting the BSC6900 Boards.......................................................................................................................7-4
7.4 Checking the Consistency of the Data and the Version..................................................................................7-5
8 Verifying Interfaces Automatically........................................................................................8-1

9 Verifying Interfaces Manually................................................................................................9-1
9.1 Verifying the Abis Interface............................................................................................................................9-3
9.2 Verifying the A Interface................................................................................................................................9-5
9.3 Verifying the Gb Interface..............................................................................................................................9-7
9.4 Verifying the Ater Interface............................................................................................................................9-9
9.5 Verifying the Pb Interface.............................................................................................................................9-10
9.6 Verifying the Iub Interface............................................................................................................................9-11
9.7 Verifying the Iu-CS Interface........................................................................................................................9-13
9.8 Verifying the Iu-PS Interface........................................................................................................................9-15
9.9 Verifying the Iur Interface.............................................................................................................................9-17
9.10 Verifying the Iu-BC Interface.....................................................................................................................9-19
10 Handling the Alarms Generated During the Commissioning......................................10-1

11 Verifying the GSM Services................................................................................................11-1
Issue 03 (2009-12-05) Huawei Proprietary and Confidential i

BSC6900 GU
Contents Commissioning Guide
12 Verifying the UMTS Services..............................................................................................12-1

13 Connecting the BSC6900 to the M2000...............................................................................13-1
14 Creating Scheduled Tasks....................................................................................................14-1
15 FAQ...........................................................................................................................................15-1
15.1 Checking the Transmission Link.................................................................................................................15-2
15.2 Performing VCL Continuity Check............................................................................................................15-4
15.3 Unavailable E1/T1 Port...............................................................................................................................15-6
15.4 Unavailable FE/GE Port..............................................................................................................................15-6
15.5 Cell Setup Failure........................................................................................................................................15-7
15.6 Signaling Link Failure on the Iub Interface..............................................................................................15-12
15.7 AAL2/IP Connection Setup Failure..........................................................................................................15-16
15.8 Data Loading Failure on the Board...........................................................................................................15-18
15.9 Performing the Loopback Test on the E1/T1 Port....................................................................................15-20
15.10 Performing the Loopback Test on the Optical Port.................................................................................15-23
16 Appendix..................................................................................................................................16-1
16.1 Communication Ports Used by the BSC6900.............................................................................................16-2
16.2 BSC6900 Commissioning Checklist...........................................................................................................16-4
ii Huawei Proprietary and Confidential Issue 03 (2009-12-05)

BSC6900 GU
Commissioning Guide Figures
Figures
Figure 2-1 Typical commissioning network........................................................................................................2-2

Figure 4-1 BSC6900 log-in dialog box................................................................................................................4-6
Figure 5-1 Batch tab page....................................................................................................................................5-3
Figure 5-2 Setting the batch commands...............................................................................................................5-3
Figure 15-1 Locating cell setup failures (1).......................................................................................................15-8
Figure 15-2 Locating cell setup failures (2).......................................................................................................15-9
Figure 15-3 Handling of signaling link failures on the Iub interface over ATM transmission........................15-13
Figure 15-4 Handling of signaling link failures on the Iub interface over IP transmission.............................15-15
Figure 15-5 Procedure for handling AAL2 connection setup failure...............................................................15-16
Issue 03 (2009-12-05) Huawei Proprietary and Confidential iii

BSC6900 GU
Commissioning Guide Tables
Tables
Table 2-1 Requirements for equipment status before commissioning.................................................................2-1

Table 2-2 Other commissioning scenarios...........................................................................................................2-2
Table 4-1 Checklist of the power supply to the cabinet components...................................................................4-2
Table 7-1 Name of the loading file.......................................................................................................................7-3
Table 7-2 Time for system resetting in different scenarios..................................................................................7-4
Table 11-1 Performing dialing tests on the basic services.................................................................................11-1
Table 11-2 Performing dialing tests on the feature services...............................................................................11-2
Table 12-1 Performing dialing tests on the basic services.................................................................................12-1
Table 12-2 Performing dialing tests on the feature services...............................................................................12-2
Table 13-1 Configuring the route from the BSC6900 to the M2000.................................................................13-2
Table 14-1 Log type and file name.....................................................................................................................14-1
Table 15-1 Methods for checking the status of the transmission link in different transmission modes.............15-2
Table 15-2 Operation index (1)..........................................................................................................................15-8
Table 15-3 Operation index (2)........................................................................................................................15-10
Table 15-7 Checking and modifying the data configuration............................................................................15-17
Table 15-9 Procedure for performing the loopback test on the local E1/T1 port.............................................15-21
Table 15-10 Procedure for performing the loopback test on the local E1/T1 cable.........................................15-21
Table 15-11 Procedure for checking the peer equipment or the transport network.........................................15-22
Table 15-12 Procedure for performing the loopback test on the SDH port......................................................15-23
Table 15-13 Procedure for performing the loopback test on the local fiber.....................................................15-23
Table 15-14 Procedure for performing the loopback test on the peer optical port...........................................15-24
Table 16-1 Communication ports used by the services of the BSC6900...........................................................16-2
Issue 03 (2009-12-05) Huawei Proprietary and Confidential v

BSC6900 GU
Commissioning Guide About This Document
About This Document
Overview
BSC6900 commissioning is performed after the hardware is installed and before the services
are provided. It aims to ensure that the BSC6900 can work normally through tasks such as
equipment verification, BSC6900 board software and data file loading, interface verification,
and service verification.
This document provides guidelines for commissioning the BSC6900. It includes the following
contents: Verifying the Operation and Maintenance Unit (OMU), Activating and Verifying the
License, Loading the BSC6900 Board Software and Data Files, Verifying the Interfaces and
Services, and Connecting the BSC6900 to the M2000.
Product Version
The following table lists the product version related to this document.
Product Name Product Version
BSC6900 V900R011C00
Intended Audience
This document is intended for field engineers.
Organization
1 Changes in BSC6900 GU Commissioning Guide
This chapter provides the changes in the BSC6900 GU Commissioning Guide.
2 Prerequisites for Commissioning
To perform the BSC6900 commissioning, the status of the equipment and the network to be
commissioned must meet the conditions required. The installation software, license, and MML
command scripts required for commissioning must be ready.
3 Commissioning Process
Issue 03 (2009-12-05) Huawei Proprietary and Confidential 1

BSC6900 GU
Organization Commissioning Guide
The BSC6900 commissioning involves verifying the equipment, updating the OMU database,
activating and verifying the license, loading the BSC6900 board software and data files,
verifying the interfaces, handling the alarms generated during commissioning, verifying the
services, and connecting the BSC6900 to the M2000.
4 Verifying the Equipment
Verifying the equipment is the basis for commissioning the BSC6900. The verifying of the
interfaces and services can be performed only after the equipment is verified. Equipment
verifying involves checking the hardware operating status, verifying the OMU and logging in
to the BSC6900 through the LMT.
5 Updating the OMU Database
This chapter describes how to update the BSC6900 data configuration in the OMU database by
running MML commands.
6 Activating and Verifying the License
This chapter describes how to activate the license and verify the license configuration
information to enable service checking.
7 Loading BSC6900 Board Software and Data Files
This chapter describes how to load the BSC6900 board software and data files to enable the
normal operation of the BSC6900.
8 Verifying Interfaces Automatically
This chapter describes how to verify the BSC6900 interfaces automatically through NE health
check on the M2000.
9 Verifying Interfaces Manually
This chapter describes how to verify interfaces at the BSC6900 through MML commands or
GUI on the LMT. The interfaces to be verified are Abis, A, Gb, Ater, Pb, Iub, Iu-CS, Iu-PS, Iur,
and Iu-BC interfaces. The Ater interface verification is mandatory in BM/TC separated mode;
the Pb interface verification is mandatory when the external PCU is used on the BSC6900; the
Iur interface verification is mandatory when the BSC6900 is connected to another RNC.
10 Handling the Alarms Generated During the Commissioning
This chapter describes how to handle the alarms generated during the commissioning, thus
preventing the alarms from affecting the verification of services.
11 Verifying the GSM Services
This chapter describes how to verify that the GSM basic services and the feature services that
are enabled are normal. The basic services consist of speech service and data service. The feature
services consist of the inter-RAT handover, location service, and AMR service.
12 Verifying the UMTS Services
This chapter describes how to verify that the UMTS basic services and the feature services that
are enabled are normal. The basic services consist of voice service, CS streaming service, PS
service, and mobility management service. Feature services consist of inter-RAT handover,
HSDPA service, HSUPA service, 64QAM service, and MIMO service.
13 Connecting the BSC6900 to the M2000
2 Huawei Proprietary and Confidential Issue 03 (2009-12-05)

BSC6900 GU
Commissioning Guide Organization
This chapter describes how to connect the BSC6900 to the M2000 for the centralized
management.
14 Creating Scheduled Tasks
This chapter describes how to create the scheduled tasks for the automatic backup of the system
data and logs after commissioning; thus, the data and logs can be used for the BSC6900
equipment fault recovery.
15 FAQ
This chapter describes how to handle the common problems during the commissioning.
16 Appendix
This chapter provides the communication ports 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 a hazard with a high level of risk, which if not

avoided,will result in death or serious injury.
Indicates a hazard with a medium or low level of risk, which

if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation, which if not

avoided,could result in equipment damage, data loss,
performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save

time.
Provides additional information to emphasize or supplement

important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic Book titles are in italics.

BSC6900 GU
Organization Commissioning Guide
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.
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.
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

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

signs. For example, choose File > Create > Folder.
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
4 Huawei Proprietary and Confidential Issue 03 (2009-12-05)

BSC6900 GU
Commissioning Guide Organization
Format Description
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.

BSC6900 GU
Commissioning Guide 1 Changes in BSC6900 GU Commissioning Guide
1 Changes in BSC6900 GU Commissioning

Guide
This chapter provides the changes in the BSC6900 GU Commissioning Guide.
03(2009-12-05)
This is the third commercial release.
Compared with issue 02 (2009-10-30) of V900R011C00, this issue includes no new topics.
Compared with issue 02 (2009-10-30) of V900R011C00, this issue excludes no topics.
Compared with issue 02 (2009-10-30) of V900R011C00, this issue incorporates the following
changes:
Content Change Description
5 Updating the OMU Database Add the method for uploading the MML script to the
OMU and the script execution time in MML and GUI
modes.
8 Verifying Interfaces Add the method for checking whether the M2000 license
Automatically supports the NE health check.
9.1 Verifying the Abis Interface Add the troubleshooting method when the Abis interface
verification fails in MML and GUI modes.
9.2 Verifying the A Interface Add the troubleshooting method when the A interface
9.3 Verifying the Gb Interface Add the troubleshooting method when the Gb interface
verification fails in MML mode.
9.4 Verifying the Ater Interface Add the troubleshooting method when the Ater interface
9.5 Verifying the Pb Interface Add the troubleshooting method when the Pb interface
Issue 03 (2009-12-05) Huawei Proprietary and Confidential 1-1

BSC6900 GU
1 Changes in BSC6900 GU Commissioning Guide Commissioning Guide
9.6 Verifying the Iub Interface Add the troubleshooting method when the Iub interface
9.7 Verifying the Iu-CS Add the troubleshooting method when the Iu-CS interface
Interface verification fails in MML mode.
9.8 Verifying the Iu-PS Add the troubleshooting method when the Iu-PS interface
Interface verification fails in MML mode.
9.9 Verifying the Iur Interface Add the troubleshooting method when the Iur interface
15.1 Checking the Add the troubleshooting method when the status of the
Transmission Link optical port is abnormal.
15.2 Performing VCL Add the troubleshooting method when the continuity
Continuity Check check of links over interfaces fails.
02(2009-10-30)
This is the second commercial release.
Compared with issue 01 (2009-07-30) of V900R011C00, this issue includes the following new
topics:
l 8 Verifying Interfaces Automatically
l 9 Verifying Interfaces Manually
Compared with issue 01 (2009-07-30) of V900R011C00, this issue excludes the following
topics:
l Verifying GSM Interfaces
l Verifying UMTS Interfaces
Compared with issue 01 (2009-07-30) of V900R011C00, this issue incorporates the following
changes:
3 Commissioning Process The step of automatically verifying interfaces is added in

the commissioning process.
01(2009-07-30)
This is the first commercial release.
1-2 Huawei Proprietary and Confidential Issue 03 (2009-12-05)

BSC6900 GU
Commissioning Guide 2 Prerequisites for Commissioning
2 Prerequisites for Commissioning
To perform the BSC6900 commissioning, the status of the equipment and the network to be
commissioned must meet the conditions required. The installation software, license, and MML
command scripts required for commissioning must be ready.
Requirements for the Status of the Equipment

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 passes the hardware installation
check and powering-on check.
OMU Configured before delivery. For details, see Checklist for the
Factory Settings of the OMU Software.
LMT PC The LMT PC meets the configuration requirements. For details,

see Configuration Requirements of the LMT PC.
Requirements for the Commissioning Network

To ensure the smooth verifying of the Abis, Ater (optional), and A interfaces on the GSM
network and the Iub, Iu, and Iur (optional) interfaces on the UMTS network, the network
equipment in the commissioning network must meet the following requirements:
l At least one BTS and one NodeB are connected to the local BSC6900. The BTS and the
NodeB should have passed commissioning and can provide basic functions.
l At least one set of Core Network (CN) equipment is connected to the local BSC6900. The
CN equipment should have passed the commissioning and can provide basic functions.
l If the BSC6900 is connected to the RNC, then that RNC must have passed the
commissioning.
l Three single-mode UEs, three single-mode MSs and one dual-mode UE are ready for test
and are registered in the HLR.
Figure 2-1 shows a typical commissioning network.

BSC6900 GU
2 Prerequisites for Commissioning Commissioning Guide
Figure 2-1 Typical commissioning network
l The figure shows only the connection. The quantity and type of cables are not specified.
l Figure 2-1 illustrates an example. There may be other commissioning scenarios, as listed
in Table 2-2.
Table 2-2 Other commissioning scenarios
Scenario Description
In BM/TC separated mode, The TCS is configured on the MSC side.

with the TCS configured
remotely
A over IP The TCS is not configured in the BSC6900.
In BM/TC combined mode The BM and TC are configured in the same subrack.
The BSC6900 is connected to Two NEs in the same equipment room are connected directly.
the MGW, base station, or
RNC
The external PCU It communicates with the BSC6900 over the Pb interface, and
provides PS service.

BSC6900 GU
Commissioning Guide 2 Prerequisites for Commissioning
Scenario Description
Alarm box configured on The alarm box is connected to the BSC6900 LMT that serves
BSC6900 side as the alarm management system.
Requirements for the Software and Data Files

l Software installation package
The installation package of the OMU application that is consistent with the local office
version must be ready before commissioning.
l License
The license that is applicable to configuration in the local office is obtained through the
Huawei technical support engineer.
l MML command script file
Before commissioning, complete the initial configuration according to the BSC6900 GU
Initial Configuration Guide to obtain the MML command script file. In addition, check and
ensure the correctness of the data configuration according to the MML command script
examples and the on-site negotiated data defined in the BSC6900 GU Initial Configuration
Guide.

BSC6900 GU
Commissioning Guide 3 Commissioning Process
3 Commissioning Process
The BSC6900 commissioning involves verifying the equipment, updating the OMU database,
activating and verifying the license, loading the BSC6900 board software and data files,
verifying the interfaces, handling the alarms generated during commissioning, verifying the
services, and connecting the BSC6900 to the M2000.
Procedure
Step 1 Verify the equipment by referring to 4 Verifying the Equipment.
1. Check the operating status of the hardware by referring to 4.1 Checking the Operating
Status of the Hardware.
2. Verify the OMU by referring to 4.2 Verifying the OMU.
3. Logging in to the BSC6900 through the LMT by referring to 4.3 Logging In to the
BSC6900 Through the LMT.
Step 2 Update the OMU data by referring to 5 Updating the OMU Database.
Step 3 Activate and verify the license by referring to 6 Activating and Verifying the License.
Step 4 Load the BSC6900 board software and data files by referring to 7 Loading BSC6900 Board
Software and Data Files.
1. Generate the data file for loading by referring to 7.1 Generating the Data File for the
Loading.
2. Set the loading mode by referring to 7.2 Setting the Loading Mode.
3. Reset the BSC6900 boards by referring to 7.3 Resetting the BSC6900 Boards.
4. Check the consistency of the version and the data by referring to 7.4 Checking the
Consistency of the Data and the Version.
Step 5 Verify interfaces.

1. To automatically verify interfaces on the M2000, refer to 8 Verifying Interfaces
Automatically.
2. To manually verify interfaces through LMT, refer to 9 Verifying Interfaces Manually.
Step 6 Handle the alarms generated during commissioning by referring to 10 Handling the Alarms
Generated During the Commissioning.
Step 7 Verify GSM services by referring to 11 Verifying the GSM Services.

BSC6900 GU
3 Commissioning Process Commissioning Guide
Step 8 Verify UMTS services by referring to 12 Verifying the UMTS Services.

Step 9 Connect the BSC6900 to the M2000 by referring to 13 Connecting the BSC6900 to the
M2000.
----End
Postrequisite
After the commissioning, create scheduled tasks by referring to 14 Creating Scheduled
Tasks, so that the data backed up can be used for BSC6900 data restoration.

BSC6900 GU
Commissioning Guide 4 Verifying the Equipment
4 Verifying the Equipment
About This Chapter
Verifying the equipment is the basis for commissioning the BSC6900. The verifying of the
interfaces and services can be performed only after the equipment is verified. Equipment
verifying involves checking the hardware operating status, verifying the OMU and logging in
to the BSC6900 through the LMT.
1. 4.1 Checking the Operating Status of the Hardware

Before verifying the equipment, ensure that the cabinet is powered on and operates
normally.
2. 4.2 Verifying the OMU
This section describes how to verify the OMU to enable the normal communication between
the LMT and the BSC6900. The OMU verification involves installing the OMU application
on site, checking the operation status of the OMU and changing the external physical IP
address.
3. 4.3 Logging In to the BSC6900 Through the LMT
Log in to the BSC6900 through the LMT, and enabling the normal communication between
the LMT and the BSC6900. LMT verification ensures the BSC6900 commissioning
through the LMT.

BSC6900 GU
4 Verifying the Equipment Commissioning Guide
4.1 Checking the Operating Status of the Hardware

Before verifying the equipment, ensure that the cabinet is powered on and operates normally.
Prerequisite
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 Step 2.
The cabinet is powered on, Go to step Step 3.
Step 2 Power on the cabinet by referring to Powering On the Cabinet.
Step 3 Check the power supply to the cabinet components, as listed in Table 4-1. Ensure that the
hardware operates normally.
Table 4-1 Checklist of the power supply to the cabinet components
Component Normal LED Status
Board The green RUN LED on the board panel flashes every other
second.
Fan box The green STATUS LED on the panel of the fan box flashes
every other second after the subrack and independent fan
subrack are powered on.
Power monitoring The green RUN LED on the board panel flashes every other
communication board second and the ALM LED is also OFF.
NOTE
If power failure occurs, handle the problem by referring to Handling power failures of internal cabinet
components in Powering On the Cabinet.
----End
4.2 Verifying the OMU

This section describes how to verify the OMU to enable the normal communication between the
LMT and the BSC6900. The OMU verification involves installing the OMU application on site,
checking the operation status of the OMU and changing the external physical IP address.

BSC6900 GU
Prerequisite
The software installation package of OMU application that is consistent with the version used
in the local office and the Records of OMU Software Installation Information are obtained.
Context
The external physical IP address mentioned refers to the physical IP address of the external
Ethernet adapter team. This IP address is planned and set before the delivery of the OMU. It
may be different from the IP address plan in the existing network. In this case, the external
physical IP address needs to be changed according to the actual networking. Generally, the
gateway IP address should be changed with the external physical IP address.
The OMU application is installed in the active workspace of the OMU. If the BSC6900 works
in active/standby OMU mode, then the OMU application must be installed in the active
workspaces of both the active and standby OMUs. This part takes the condition that only one
OMU is configured on the BSC6900 as an example.
The active workspace of the OMU can be queried through the MML command LST
OMUAREA. To view the directory structure of the OMU workspace, see Checking the
Installation Directory of the OMU Applications. The following procedure assumes that the active
workspace is version_a.
Procedure
Step 1 Connect the PC to the ETH2 debugging port on the OMUa by using an Ethernet cable.
Step 2 Set the IP address of the PC to be in the same network segment with the ETH2 port. The initial
IP address of the ETH2 port is 192.168.6.50, the subnet mask is 255.255.255.0.
Step 3 Remotely log in to the Linux operating system by referring to Logging In to the OMU.
Step 4 Check that the OMU application is normally installed.

1. Run the /etc/rc.d/omud status command to check the running status of the OMU process.
If... Then...
The returned information is running, Go to step Step 4.2.
The returned information is unused, a. Run the /etc/rc.d/omud start

command to start the omud.
b. Go to step Step 4.2.
The returned information is neither Go to step Step 5.

running nor unused,
2. Log in to the BSC6900 through the LMT by referring to 4.3 Logging In to the BSC6900
Through the LMT. Run the MML command LST VER to view the application version of
the OMU.
If... Then...
The OMU application version is same as that End this task.

required by the customer,

BSC6900 GU
If... Then...
The OMU application version is different a. Uninstall the OMU application by

from that required by the customer, referring to Uninstalling the OMU
Applications.
b. Go to step Step 5.
Step 5 Install the OMU application in the active workspace by referring to Installing the OMU
Applications in the Active Workspace.
NOTE
l After the OMU application is installed, the OMU application installation directory is /mbsc/bam and the
active workspace is version_a. That is, the default OMU active workspace directory is /mbsc/bam/
version_a.
Step 6 Run the /etc/rc.d/omud start command to start the OMU application.
Step 7 Run the ps -afx command to check the operating status of the OMU.
You can infer that the OMU is in normal state if the following OMU service processes exist in
the OMU active workspace directory /bin/bam/monitor (/mbsc/bam/version_a/bin/bam/
monitor) in the result: host_gate, ems_gate, authority, configure, maintain, stat, alarm,
software, ftp_server, sntp, btsom, ems_agent, omu_manager, cfa, weblmt, and
debug_log.
NOTE
l You can infer that the standby OMU is in normal state if the following processes exist: software,
ftp_server, sntp, omu_manager and debug_log.
l If some of the processes do not exist, run the /etc/rc.d/omud restart command to restart the OMU server,
and then check again whether the processes exist. If some of them still do not exist, uninstall the OMU
application by referring to Uninstalling the OMU Applications and then install the OMU application in the
active workspace again by referring to Installing the OMU Applications in the Active Workspace.
Step 8 Run the ifconfig command to check whether the external physical IP address of the OMU is
same as that planned in the existing network.
If... Then...
The external physical IP address is same as that planned in the existing End this task.
network,
The external physical IP address is different from that planned in the Go to step Step 9.
existing network,
Step 9 Run the /etc/rc.d/omud stop command to stop the omud.

Step 10 Run the cd /mbsc/bam/version_a/bin/bam command to switch to the directory where the
omutool program is located.
You can run the ./omutool -h command to view the help information of the omutool.
Step 11 Run the ./omutool extercard The external physical IP address The mask The gateway IP
address command to change the external physical IP address and the gateway IP address.
For example, you can run the following command and then press Enter.

BSC6900 GU
./omutool extercard 10.161.10.100 255.255.255.0 10.161.10.1
NOTE
After the external physical IP address is changed, the BSC6900 can be connected to the OM network of the
customer through the ETH0 or ETH1 port. In this case, the commissioning can be performed in a centralized
manner.
Step 12 Run the /etc/rc.d/omud start command to start the OMU application so that the modification
takes effect.
Step 13 Remotely log out of the Linux operating system by referring to Logging Out of the OMU.
----End
4.3 Logging In to the BSC6900 Through the LMT

Log in to the BSC6900 through the LMT, and enabling the normal communication between the
LMT and the BSC6900. LMT verification ensures the BSC6900 commissioning through the
LMT.
Prerequisite
l The OMU has passed the commissioning.
l The network connection between the LMT and the OMU is established.
Context
JRE is a standard plug-in in Java operating environment. If JRE is not installed, a message is
displayed when the LMT is started. In this case, install JRE according to the prompt message
on the screen. If the JRE installed in the LMT PC is not of the latest version, a message is
displayed when the LMT is started, prompting you to update the JRE. In this case, it is
recommended that you uninstall the old version and then install the latest version.
WARNING
When the LMT application is running, do not change the LMT PC system time. Otherwise,
severe errors may occur on the system. If you have to change the system time, stop all the LMT
applications first.
Procedure
Step 1 Check the configuration of the LMT PC and ensure that it meets the requirements.
1. Check the hardware configuration of the BSC6900 LMT PC to ensure that the requirements
described in Configuration Requirements of the LMT PC are satisfied.
2. Check the security settings of the Internet Explorer, ensure that the Java script is supported.
Step 2 Start the Internet Explorer, and then log in to the BSC6900 through the LMT.
1. Start the Internet Explorer. and then enter the external virtual IP address of the OMU of
the BSC6900 on the address bar. The log-in dialog box is displayed, as shown in Figure
4-1.

BSC6900 GU
Figure 4-1 BSC6900 log-in dialog box
NOTE
To log in to the BSC6900 by using the Domain user account, the connection between the BSC6900 and
the M2000 server should be established.
2. Enter the User Name, Password, and Verify Code, and then click Login to enter the LMT
maintain interface.
----End

BSC6900 GU
Commissioning Guide 5 Updating the OMU Database
5 Updating the OMU Database
This chapter describes how to update the BSC6900 data configuration in the OMU database by
running MML commands.
Prerequisite
l You have logged in to the BSC6900 through the LMT.
l The MML command data scripts applicable to the local office are verified and the contents
are precise and complete.
Context
There are two ways to run the MML command script: through GUI or through MML commands.
The MML command script can be executed through GUI only when the script is smaller than 4
MB. It is recommended that you run the MML script through MML commands, because this
way is more efficient.
Procedure
l Run the MML command script through MML commands
1. Repeat the MML command SET CFGDATAINEFFECTIVE to set all the subracks
to the ineffective mode.
2. Run the MML command RST DATA. A dialog box is displayed. Click Yes to
initialize the BSC6900 configuration data in the OMU database.
3. Upload the MML command script to the /ftp folder in the OMU active workspace
directory.
NOTE
Two methods are available: through File Manager on the LMT or through command lines.
The following procedure takes uploading the MML script BATCHFILE.txt saved in disk D to
the OMU active workspace /mbsc/bam/version_a/ftp as an example to introduce the two
methods.
– Through File Manager on the LMT

BSC6900 GU
5 Updating the OMU Database Commissioning Guide
(1) Start the File Manager by referring to File Manager.

(2) Choose Root > bam > version_a > ftp on the left pane. 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
(1) On the local PC, choose Start > Run. Type cmd, and then click OK.
(2) Input d:, and then press Enter to switch to disk D.
(3) Input ftp IP address to try to be connected to the OMU. Here, IP address is
the IP address of the OMU.
(4) Input the FTP user name and password. The connection between the OMU
and the local FTP is set up after the authentication succeeds.
NOTE
The FTP user name is always FtpUsr. The FTP password is set during the OMU
application installation. For details, see Records of the OMU Application Installation
Information.
(5) Input cd /mbsc/bam/version_a/ftp to switch to the OMU active workspace.
(6) Input put BATCHFILE.txt to upload the file.
(7) After the file is uploaded successfully, input quit to disconnect the FTP.
4. Run the MML command RUN BATCHFILE to run the MML command script. It is
recommended that you set Finish Type to ALL_END_RETURN(Stop at end),
Result Recording Type to REC_ERR(Record errors), 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 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 may needed
for executing a script with 100,000 commands.
l After the MML command script is executed, open the RUN_BATCHFILE_RESULT.txt file to
check whether there is any command that fails to be executed. If yes, extract the commands that
fail to execute to generate a new MML command script, correct the new script according to the
prompts, and then go to step Step 4 to run the new script.
l Run the MML command script through GUI
1. Repeat the MML command SET CFGDATAINEFFECTIVE to set all the subracks
to the ineffective mode.
2. Run the MML command RST DATA. A dialog box is displayed. Click Yes to
initialize the BSC6900 configuration data in the OMU database.
NOTE
If an Error dialog box showing Execution failed. Do you want to continue? is displayed during
the execution of the MML command script, you can infer that the MML command script is incorrect.
In this case, select Yes to all to ignore the error prompt. After the script is executed, extract the
commands that fail to execute to generate a new MML command script, correct the new script, and
then go to step Step 4 to run the new script.
3. Click Batch on the LMT main page. The Batch tab page is displayed, as shown in
Figure 5-1.

BSC6900 GU
Commissioning Guide 5 Updating the OMU Database
Figure 5-1 Batch tab page
4. Click Open.... The Open dialog box is displayed.

5. Select the prepared MML command data script. Click Open. The selected script is
displayed in the Batch tab page.
6. Click Set.... The Set dialog box is displayed.
7. Set Sending Commands interval(s) to 0. Select Save Failed Commands, and then
set the save path of the unsuccessful commands. Click OK to complete the setting of
the batch commands, as shown in Figure 5-2.
Figure 5-2 Setting the batch commands

BSC6900 GU
5 Updating the OMU Database Commissioning Guide
8. In the Batch tab page, set Execution Type to All.

9. Click Go. The system runs the MML commands one by one.
NOTE
Click OK when the system prompts that the current configuration is in ineffective mode after you
click Go. The execution of the script may take a long time (2-3 hours) in GUI mode.
10. Click OK when the message dialog box is displayed, indicating that the running of
all the MML commands is complete.
----End

BSC6900 GU
Commissioning Guide 6 Activating and Verifying the License
6 Activating and Verifying the License
This chapter describes how to activate the license and verify the license configuration
information to enable service checking.
Prerequisite
l The license is ready and the license check is passed.
Context
Procedure
Step 1 Run the MML command DLD LICENSE to download the License to the OMU active
workspace directory/ftp/license, that is, /mbsc/bam/version_a/ftp/license.
Step 2 Run the MML command LST LICENSE and then set File Name to the name of the license file
to be activated to query the detailed configuration information of the license file.
If... Then...
The license is consistent with what you apply Go to step Step 3.

for,
The license is inconsistent with what you Contact the Huawei Customer Service
apply for, Center by referring to Contact the Huawei
Customer Service Center.
Step 3 Run the MML command ACT LICENSE to activate the license file.
Step 4 Optional: If there are the primary operator and secondary operators, run the MML command
SET LICENSE to re-allocate the resources and functions in sequence from the primary operator

BSC6900 GU
6 Activating and Verifying the License Commissioning Guide
to the secondary operator. If there are multiple secondary operators, run the commands several
times.
----End
Postrequisite
If the license activation fails, you can infer that the configuration data of the license is
inconsistent with that in the OMU database. Check the configuration data of the license and the
configuration data in the OMU database.
l If the configuration data of the license is incorrect, apply for a new license.
l If the configuration data in the OMU database is incorrect, correct the configuration data,
and then activate the license again.

BSC6900 GU
Commissioning Guide 7 Loading BSC6900 Board Software and Data Files
7 Loading BSC6900 Board Software and Data

Files
About This Chapter
This chapter describes how to load the BSC6900 board software and data files to enable the
normal operation of the BSC6900.
Prerequisite
l The equipment verifying is complete.
l The OMU database is updated.
Context
The software of BSC6900 boards is generated automatically in the OMU active workspace
directory/bin/fam when installing OMU applications. Assume that the active workspace is
version_a, then 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.
Procedure
----End
1. 7.1 Generating the Data File for the Loading
This section describes how to generate the BSC6900 data file, which can be loaded, by
using the MML command data scripts.
2. 7.2 Setting the Loading Mode
This section describes how to set the loading modes of all the board subsystems before
resetting BSC6900 boards.
3. 7.3 Resetting the BSC6900 Boards

BSC6900 GU
7 Loading BSC6900 Board Software and Data Files Commissioning Guide
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.
4. 7.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 the information in the OMU.

BSC6900 GU
7.1 Generating the Data File for the Loading

This section describes how to generate the BSC6900 data file, which can be loaded, by using
the MML command data scripts.
Prerequisite
Context
The data file is generated in the OMU active workspace directory/bin/fam. Assume that the
active workspace is version_a, then the data file is in /mbsc/bam/version_a/bin/fam. The file
name is in ABCXXYYZZ.DAT format, such as XPUa000200.DAT. Table 7-1 lists the detailed
information.
Table 7-1 Name of the loading file
Parameter Indication
ABC Board name
XX Subrack number
YY Slot number
ZZ Subsystem number
Procedure
Step 1 Run the MML command SET CFGDATAEFFECTIVE and do not specify any parameter to
set all the subracks to effective mode.
Step 2 Run the MML command FMT DATA and set Work Area Flag to Active(Format active
area) (do not specify the subrack number) to format the configuration data in the OMU database.
After the command is executed successfully, the .DAT file is generated in the OMU active
workspace directory/bin/fam, that is, /mbsc/bam/version_a/bin/fam.
----End
7.2 Setting the Loading Mode

This section describes how to set the loading modes of all the board subsystems before resetting
BSC6900 boards.

BSC6900 GU
7 Loading BSC6900 Board Software and Data Files Commissioning Guide
Prerequisite
You have logged in to the BSC6900 through the LMT.
Context
For details about the loading modes, see Loading Management.
Procedure
Step 1 Run the MML command SET LODCTRL, and set Board Start Load Control to LFB(Load
from OMU and write flash). The BSC6900 loading mode is set.
----End
7.3 Resetting the 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.
Prerequisite
l The data file for the Loading is generated.
l All the subracks are powered on.
Context
The time for system resetting is different in different scenarios, as listed in Table 7-2.
Table 7-2 Time for system resetting in different scenarios

Work Mode Resetting Time Sequence for Resetting
Subracks
BM/TC combined, or The resetting time is less than The subracks should be reset in
A over IP nine minutes in the maximum the following sequence: EPS ->
configuration. MPS.
BM/TC separate The resetting time is less than The subracks should be reset in
fifteen minutes in the the following sequence: remote
maximum configuration. extension TCS-> remote main
TCS -> EPS -> MPS.
You can run the MML command LST SUBRACK to check the configuration information of
Subrack Type and Is Remote TC Central to determine the resetting sequence.
Procedure
Step 1 Run the MML command RST SUBRACK, and then set Subrack No. to the number of the
subrack to be reset. A confirmation dialog box is displayed, asking you whether to proceed.

BSC6900 GU
Click OK. The boards in the subrack automatically load the BSC6900 board software and data
files from the OMU.
Step 2 Repeat step Step 1 to reset all the subracks of the BSC6900.
NOTE
You can observe the loading process at the Progress tab page on the LMT main page. If this tab page is hidden,
click Progress in the toolbar on the LMT main page.
Step 3 After all the subracks are reset, click the Device Maintenance on the LMT main page. The
Device Maintenance tab page is displayed.
Step 4 Observe the device panel to check whether all the boards are in normal state.
If... Then...
The device panel shows that all the boards End this task.
are in normal state,
The device panel shows that some boards Rectify the faults according to the prompt. For
are in normal state, details, see 15.8 Data Loading Failure on the
Board.
----End
7.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 the information in the OMU.
Prerequisite
l All the subracks and boards are running normally.
Procedure
Step 1 Run the MML command ACT CRC and do not specify any parameter to check whether the
board configuration is consistent with the data in the OMU.
Expected result: The All table data consistent. message is displayed.
Step 2 Run the MML command CMP BRDVER and do not specify any parameter to check whether
the software version run by the BSC6900 is consistent with the version information in the OMU.
Expected result: The Compare consistent message is displayed.
NOTE
If the board configuration or software version of the BSC6900 is inconsistent with the information in the OMU,
run the MML command RST SUBRACK to reset the subrack with incorrect data or version.
----End

BSC6900 GU
Commissioning Guide 8 Verifying Interfaces Automatically
8 Verifying Interfaces Automatically
This chapter describes how to verify the BSC6900 interfaces automatically through NE health
check on the M2000.
Prerequisite
l The BSC6900 and the peer equipment are physically connected, and the hardware
installation acceptance is passed.
l All the subracks of the BSC6900 are running normally.
l The BSC6900 is connected to the M2000 (for details, see 13 Connecting the BSC6900 to
the M2000). The M2000 license supports the NE health check.
Context
To check whether the M2000 license supports the NE health check, do as follows: On the M2000
client, choose Help > License Information. The License Information dialog box is displayed.
Click the Resource control item tab, check whether the license item NE Health Checking-
GBSS or NE Health Checking-WRAN exists.
l If the license item NE Health Checking-GBSS or NE Health Checking-WRAN exists
and the value of License capacity is greater than zero, the M2000 license supports the NE
health check. In this case, the NE Health Check item is available in the Maintenance
menu.
l If the license item NE Health Checking-GBSS and NE Health Checking-WRAN do not
exist, or the value of License capacity is zero, the M2000 license does not support the NE
health check. In this case, verify interfaces manually by referring to 9 Verifying Interfaces
Manually.
NOTE
The license item NE Health Checking-GBSS is for GSM services, and the license item NE Health
Checking-WRAN is for UMTS services.
Procedure
Step 1 Set the scenario for NE health check.
1. On the M2000 client, choose Maintenance > NE Health Check.
2. Click Configure Scenario... in the displayed tab page.
3. Click New in the displayed dialog box.

BSC6900 GU
8 Verifying Interfaces Automatically Commissioning Guide
4. Enter the scenario name in the Name text box at the right of the dialog box.
NOTE
The scenario name must be different from existing scenario names.

5. Click the type of the NE for health check in the NE Types area.Click BSC6900 GU.
6. Select the NEs for health check (deselect those not for health check) in the Interface State
Check under the Check Items area.
7. Click OK. A dialog box is displayed, prompting that the NE health check scenario is set
successfully. Click OK to complete the set of the NE health check scenario.
Step 2 Create the NE health check task.
1. On the NE Health Check tab page, click New.... The Create Task dialog box is displayed.
2. Enter the task name in the Name text box, and then click the corresponding scenario in the
Scenario drop-down list.
3. Select the NE for health check in the Select NE area.
4. Select the way to run the task in the Time setting area. The operations for different ways
are as follows:
Operation Mode Description
Instant Click Next. The Collection period dialog

box is displayed. Click Finish.
NOTE
The setting of Collection period not necessary
during commissioning.
Scheduled Set the time for running the task in the

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

Run Times, and then click Finish.
NOTE
The executed health check tasks are listed under the Finished Tasks node in the navigation tree at the left
of the NE Health Check tab page.
Step 3 View the result of the NE health check.

1. Under the Finished Tasks node of the navigation tree, click the executed task. Right-click
the corresponding task at the right and then click View Report... from the shortcut menu.
2. In the displayed Health Check Report dialog box, click the HTML Format tab or DOC
Format tab to view the report.

BSC6900 GU
Commissioning Guide 8 Verifying Interfaces Automatically
If... Then...
You selected the HTML Select the report from the report list, and then view
Format, the report in one of the following ways:
l Click Open to directly open the report in 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 selected 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 Word format.
NOTE
The health check report is saved in .zip format. To view the report, double-click the .zip file, and
then double-click the report in the zip file browser.
If some items in the health check report are in red, the corresponding interface is faulty. Rectify the
fault by referring to the health check report.
----End

BSC6900 GU
Commissioning Guide 9 Verifying Interfaces Manually
9 Verifying Interfaces Manually
About This Chapter
This chapter describes how to verify interfaces at the BSC6900 through MML commands or
GUI on the LMT. The interfaces to be verified are Abis, A, Gb, Ater, Pb, Iub, Iu-CS, Iu-PS, Iur,
and Iu-BC interfaces. The Ater interface verification is mandatory in BM/TC separated mode;
the Pb interface verification is mandatory when the external PCU is used on the BSC6900; the
Iur interface verification is mandatory when the BSC6900 is connected to another RNC.
Context
During the interface verification, you can run the LST command to query the configuration
information. For example, before running the MML command DSP ADJNODE, you can run
the MML command LST ADJNODE to query the parameter Adjacent Node ID.
9.1 Verifying the Abis Interface
This section describes how to verify the control plane and the user plane of the Abis interface.
The Abis interface verification varies according to the transmission mode over the Abis interface.
9.2 Verifying the A Interface
This section describes how to verify the control plane and the user plane of the A interface. The
A interface verification varies according to the transmission mode of the A interface.
9.3 Verifying the Gb Interface
This section describes how to verify the Gb interface. The Gb interface verification varies
according to the transmission mode over the Gb interface.
9.4 Verifying the Ater Interface
This section describes how to verify the Ater interface when the BSC6900 is in BM/TC separated
mode.
9.5 Verifying the Pb Interface
If the BSC6900 is configured with an external PCU, Pb interface verification is needed.
9.6 Verifying the Iub Interface
This section describes how to verify the control plane and the user plane of Iub interface. The
Iub interface verification varies according to the transmission mode over the Iub interface.
9.7 Verifying the Iu-CS Interface

BSC6900 GU
9 Verifying Interfaces Manually Commissioning Guide
This section describes how to verify the control plane and the user plane of the Iu-CS interface.
The Iu-CS interface verification varies according to the transmission mode over the Iu-CS
interface.
9.8 Verifying the Iu-PS Interface
This section describes how to verify the control plane and the user plane of the Iu-PS interface.
The Iu-PS interface verification varies according to the transmission mode over the Iu-PS
interface.
9.9 Verifying the Iur Interface
This section describes how to verify the control plane and the user plane of the Iur interface
when the BSC6900 is connected to the RNC. The Iur interface verification varies according to
the transmission mode over the Iur interface.
9.10 Verifying the Iu-BC Interface
This section describes how to verify that the user plane of the Iu-BC interface is operational.

BSC6900 GU
9.1 Verifying the Abis Interface

This section describes how to verify the control plane and the user plane of the Abis interface.
The Abis interface verification varies according to the transmission mode over the Abis interface.
Prerequisite
l The BSC6900 and the base stations are physically connected, and the hardware installation
acceptance is passed.
l The base stations used to verify the Abis interface are commissioned and the cell
configuration is complete.
Context
For the commissioning of the base station, see the commissioning guide of the base station.
The following takes one base station as an example to describe the commissioning process on
the Abis interface. If multiple base stations are connected, repeat the operations.
There are two ways to verify the Abis interface (Abis over TDM): through GUI or through MML.
You can choose either way according to your convenience.
Procedure
l To verify the Abis interface (Abis over TDM) through GUI, see Verifying the Abis Interface
(Abis over TDM) Through GUI.
l Verifying the Abis interface (Abis over TDM) through MML
1. Run the MML command DSP LAPDLNK to check whether the Link Access Protocol
on the D channel (LAPD) link on the Abis interface is normal.
Expected result: The value of UsageStatus is Normal.
If the status of LAPD links on the Abis interface is abnormal, check the transmission
link by referring to 15.1 Checking the Transmission Link.
2. Run the MML command DSP ABISTS to query the timeslot status of the Abis
interface.
Expected result: The State of many timeslots is Idle, and there is no timeslot with the
State of Failure.
If the status of timeslots on the Abis interface is abnormal, check the transmission link
by referring to 15.1 Checking the Transmission Link.
NOTE
To query the Subrack No., Slot No., and Port No. of the timeslots to be verified, run the MML
command LST BTSCONNECT.
3. Run the MML command DSP BTSSTAT to query the status of cells and channels.
Expected result: The value of Cell Initialized is Yes and the value of Channel
Fault is No.

BSC6900 GU
If the value of Cell Initialized is No, see ALM-21801 GSM Cell out of Service for
troubleshooting; if the value of Cell Initialized is Yes but the value of Channel
Fault is Yes, check the alarms related to the TRX and rectify the fault according to
the alarm handling suggestion.
l Verifying the Abis interface (Abis over IP)
1. Run the MML command DSP LAPDLNK to check whether the LAPD link on the
Abis interface is normal.
2. Run the MML command DSP ADJNODE to query the status of the adjacent node.
Expected result: The values of available bandwidth are not all 0.
If the values of available bandwidth are all 0, see ALM-21585 No Resource for
Adjacent Node for troubleshooting.
3. Run the MML command DSP IPPATH to query the status of the IP path on the Abis
interface.
Expected result: The value of Operation state is Available.
If the value of Operation state is Unavailable, see IP Connection Setup Failure for
troubleshooting.
4. Run the MML command DSP BTSSTAT to query the status of the cells and channels.
Fault is No.
l Verifying the Abis interface (Abis over HDLC)
1. Run the MML command DSP LAPDLNK to check whether the LAPD link on the
Abis interface is normal.
2. Run the MML command DSP HDLCLNK to query the status of the HDLC link.
Expected result: The value of operation state is Available and the value of Available
Tx Bandwidth or Available Rx Bandwidth is not 0.
NOTE
To query the number of the HDLC link to be verified, run the MML command LST
BTSABISHDLCPATH.
3. Run the MML command DSP BTSSTAT to query the status of the cells and channels.

BSC6900 GU
Fault is No.
----End
9.2 Verifying the A Interface

This section describes how to verify the control plane and the user plane of the A interface. The
A interface verification varies according to the transmission mode of the A interface.
Prerequisite
l The BSC6900 and the MSC are physically connected.
l The MSC used to verify the A interface operates normally.
l The Ater interface has been verified when the BSC6900 is in BM/TC separated mode.
Context
There are two ways to verify the A interface (A over TDM): through GUI or through MML.
You can choose either way according to your convenience.
Procedure
l To verify the A interface (A over TDM) through GUI, see Verifying the A Interface (A
over TDM) Through GUI.
l Verifying the A interface (A over TDM) through MML
1. Run the MML command DSP MTP2LNK to query the status of the Message Transfer
Part Level 2 (MTP2) signaling link.
Expected result: The value of Link State is IN SERVICE.
If the value of Link State is OUT OF SERVICE, check the transmission links by
referring to 15.1 Checking the Transmission Link.
2. Run the MML command DSP MTP3LNK to query the status of the Message Transfer
Part Level 3 (MTP3) signaling link.
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 the SCCP SSN.
Expected result: The value of SSN state is Allowed.

BSC6900 GU
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 the SS7 destination
signaling point.
Expected result: The value of SCCP DSP state is Accessible.
If the value of SCCP DSP state is not normal, see ALM-21521 SCCP Subsystem
Prohibited for troubleshooting.
5. Run the MML command DSP ACIC to query the status of A interface circuits.
Expected result: The CIC State of many CICs is Idle, and there is no CIC with the
CIC State of Failure.
If the value of CIC State is Failure, check the transmission links by referring to 15.1
Checking the Transmission Link.
NOTE
To query the OPC Index and DPC Group Index of the E1/T1 to be verified on the A interface, run
the MML command LST AE1T1.
l Verifying the A interface (A over IP)
1. Run the MML command DSP SCTPLNK to query the status of the Stream Control
Transmission Protocol (SCTP) link.
Expected result: The value of SCTP link Operation state is Normal.
If the value of Operation state is Unavailable, check the transmission links by
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, you can infer that the
SCTP link is normal without intermittent disconnection.
2. Run the MML command DSP M3LNK to query the status of the MTP3 User Adaption
Layer (M3UA) signaling link.
Expected result: The value of Operation state is Activated state.
If the value of Operation state is not normal, see ALM-21506 MTP3 Signaling Link
Faulty for troubleshooting.
signaling point.

BSC6900 GU
6. Run the MML command DSP IPPATH to query the status of the IP path.
If the value of Operation state is Unavailable, see IP Connection Setup Failure for
troubleshooting.
----End
9.3 Verifying the Gb Interface

This section describes how to verify the Gb interface. The Gb interface verification varies
according to the transmission mode over the Gb interface.
Prerequisite
l The BSC6900 and the SGSN are physically connected, and the hardware installation
l The SGSN equipment used to verify the Gb interface operates normally.
Procedure
l Verifying the Gb interface links (Gb over FR)
1. Run the MML command DSP BC to query the status of the Bearer Channel (BC) to
be verified.
Expected result: The value of BC Service State is available.
If the value of BC Administration State is Blocked, run the MML command UBL
BC to unblock the BC, and then run the MML command DSP BC to check whether
the BC status is normal. If the status remains abnormal, check the transmission links
by referring to 15.1 Checking the Transmission Link.
2. Run the MML command DSP NSVC to query the status of the Network Service
Virtual Connection (NSVC) to be verified.
Expected result: The value of NSVC Service State is Active Unblock.
If the value of Service State is not normal, see the Postrequisites below for
troubleshooting.
3. Run the MML command DSP SIGBVC to query the SIG BSSGP Virtual Connection
(SIGBVC) status of the Network Service Entity (NSE) to be verified.
Expected result: The value of SIG BVC State is Normal.
If the value of SIG BVC State is Fault, the SGSN may be configured with an NSE
that has a different NSE ID.
NOTE
To query the configuration of the NSE to be verified, run the MML command LST NSE.

BSC6900 GU
4. Run the MML command DSP PTPBVC to query the status of the PTP BSSGP Virtual
Connection (PTPBVC) of the NSE to be verified.
Expected result: The value of Service State is Normal.
troubleshooting.
l Verifying the Gb interface links (Gb over IP)
1. Run the MML command DSP NSVL to query the status of the Network Service
Virtual Link (NSVL) to be verified.
Expected result: The value of NSVL State is Normal .
If the value of NSVL State is Fault, check the transmission links by referring to 15.1
NOTE
To query the configuration of the local or remote NSVL to be verified, run the MML command
LST NSVLLOCAL or LST NSVLREMOTE.
2. Run the MML command DSP GBIPROUTE to query the status of the IP connection
to be verified on the Gb interface.
Expected result: The value of State is Normal .
If the value of State is Faulty, run the MML command DSP IPRT to check whether
the route configuration on the Gb interface is correct.
3. Run the MML command DSP SIGBVC to query the SIGBVC status of the NSE to
be verified.
Expected result: The value of SIG BVC State is Normal.
If the value of SIG BVC State is Fault, the SGSN may be configured with an NSE
that has a different NSE ID.
NOTE
To query the configuration of the NSE to be verified, run the MML command LST NSE.
4. Run the MML command DSP PTPBVC to query the PTPBVC status of the NSE to
be verified.
Expected result: The value of Service State is Normal.
troubleshooting.
----End
Postrequisite
Handling Suggestions to Exceptional NSVC Status
l If the value of NSVC Manage State is Unblock and the NSVC Service State is Active
Block, you can infer that the FR link that bears the NSVC is functional and that the NSVC
is blocked by the SGSN.
l If the value of NSVC Manage State is Block and the NSVC Service State is Active
Block, you can infer that the FR link that bears the NSVC is functional and that the NSVC
is blocked by the BSC6900 or by both the BSC6900 and the SGSN.

BSC6900 GU
1. Run the MML command UBL NSVC to unblock the BSC6900.

2. Run the MML command DSP NSVC to query the status of the NSVC. If the value of
NSVC Service State is still Active Block, you can infer that the NSVC is blocked by
the SGSN.
l If the value of NSVC Service State is Deactive Block, the possible causes are as follows:
– The NSVC ID and NSE ID of the NSVC on the BSC6900 are inconsistent with that on
the SGSN.
– The NSVC configured on the same BC at the SGSN is not the required one.
Handling Suggestions to Exceptional PTPBVC Service Status
1. If the value of PTPBVC Manage State is Block, run the MML command UBL
PTPBVC to unblock the PTPBVC, and then run the MML command DSP PTPBVC to
query the status of the PTPBVC. If the status remains abnormal, go to step 2.
2. Run the MML command RST PTPBVC to reset the PTPBVC, and then run the MML
command DSP PTPBVC to query the status of the PTPBVC. If the status remains
abnormal, go to step 3.
3. Run the MML command RST PSCELL to reset the cell corresponding to the exceptional
PTPBVC, and then run the MML command DSP PTPBVC to query the status of the
PTPBVC. If the status remains abnormal, go to step 4.
4. Run the MML command RST SIGBVC to reset the SIGBVC corresponding to the
exceptional PTPBVC, and then run the MML command DSP PTPBVC to query the status
of the PTPBVC. If the status remains abnormal, contact the Huawei Customer Service
Center by referring to Contact the Huawei Customer Service Center.
9.4 Verifying the Ater Interface

This section describes how to verify the Ater interface when the BSC6900 is in BM/TC separated
mode.
Prerequisite
l The MPS/EPS and the TCS are physically connected.
l The data configuration on the Ater interface is complete.
l The TCS is loaded and started.
Context
There are two ways to verify the Ater interface: through GUI or through MML. You can choose
either way according to your convenience.
Procedure
l To verify the Ater interface through GUI, see Verifying the Ater Interface Through GUI.
l Verifying the Ater Interface through MML
1. Run the MML command DSP ATERTS to query the status of timeslots on the Ater
interface.

BSC6900 GU
Expected result: The State of many timeslots is Idle, and there is no timeslot with the
State of Failure.
If the State of a timeslot is Failure, check the transmission links by referring to 15.1
NOTE
To query the Ater connection path index and ID of BSC in TC Pool of the E1/T1 to be verified
on the Ater interface, run the MML command LST ATERE1T1.
2. Optional: If the TCS is configured remotely, run the MML command DSP
ATERSL to query whether the Ater signaling link is normal.
If the value of UsageStatus is Faulty, check the transmission links by referring to

15.1 Checking the Transmission Link.
----End
9.5 Verifying the Pb Interface

If the BSC6900 is configured with an external PCU, Pb interface verification is needed.
Prerequisite
l The PCU used to verify the Pb interface operates normally.
l The BSC6900 and the PCU are physically connected, and the hardware installation
Procedure
Step 1 Run the MML command DSP LAPDLNK to check whether the LAPD link on the Pb interface
is normal.
If the status of LAPD links on the Pb interface is abnormal, check the transmission link by
Step 2 Run the MML command DSP PBCIC to query the status of the circuit on the Pb interface.
Expected result: The status of many circuit identity codes (CICs) is Idle, and there is no CIC
with the status of Failure.
If the status of a CIC is Failure, check the transmission links by referring to 15.1 Checking the
Transmission Link.
NOTE
To query the E1/T1 configuration information to be verified on the Pb interface, run the MML command LST
PBE1T1.
----End

BSC6900 GU
9.6 Verifying the Iub Interface

This section describes how to verify the control plane and the user plane of Iub interface. The
Iub interface verification varies according to the transmission mode over the Iub interface.
Prerequisite
l The BSC6900 and the base stations are physically connected, and the hardware installation
l The cell configuration on the base station for verifying is complete.
Context
The following takes one base station as an example to describe the commissioning process on
the Iub interface. If multiple base stations are connected, repeat the operations.
Procedure
l Verifying the Iub Interface (Iub over ATM)
1. Run the MML command DSP SAALLNK to query the status of the Signaling ATM
Adaptation Layer (SAAL) link.

2. Run the MML command DSP UIUBCP to query the status of the links on the Iub
interface.
If the value of Operation state is Unavailable, see 15.6 Signaling Link Failure on
the Iub Interface for troubleshooting.
Expected result: The value of Operation state is Available and the available
bandwidth cannot be all 0.
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 available bandwidths are all 0, see ALM-21585 No Resource for Adjacent
Node for troubleshooting.
4. Run the MML command DSP AAL2PATH to query the status of the AAL2 path on
the Iub interface.
If the value of Operation state is Unavailable, see 15.7 AAL2/IP Connection Setup
Failure for troubleshooting.

BSC6900 GU
5. Optional: Perform Virtual Connect Link (VCL) continuity check on all the AAL2
paths on the Iub interface. For details, see 15.2 Performing VCL Continuity
Check.
6. Run the MML command DSP UCELL to query the status of cells.
Expected result: For all the cells, the value of OperStat is Available.
If the value of OperStat is Unavailable, see 15.5 Cell Setup Failure for
troubleshooting.
l Verifying the Iub Interface (Iub over IP)
1. Run the MML command DSP SCTPLNK to query the status of the SCTP link.
Expected result: The value of Operation state is Normal.

NOTE
2. Run the MML command DSP UIUBCP to query the status of the links on the Iub
interface.
If the value of Operation state is Unavailable, see 15.6 Signaling Link Failure on
the Iub Interface for troubleshooting.
4. Run the MML command DSP IPPATH to query the status of the IP path on the Iub
interface.
5. Run the MML command DSP UCELL to query the status of the cells.
Expected result: For all the cells, the value of OperStat is Available.
If the value of OperStat is Unavailable, see 15.5 Cell Setup Failure for
troubleshooting.
l Verifying the Iub Interface (over ATM/IP dual-stack transmission) over ATM and over IP
respectively
When the transmission resources are being used, whether ATM transmission or IP
transmission is used to carry the current service is determined according to transmission
resource mapping. To verify the Iub Interface over ATM/IP dual-stack transmission is to
verify the Iub interface over ATM and the Iub interface over IP respectively.
----End

BSC6900 GU
9.7 Verifying the Iu-CS Interface

This section describes how to verify the control plane and the user plane of the Iu-CS interface.
The Iu-CS interface verification varies according to the transmission mode over the Iu-CS
interface.
Prerequisite
l For R99 networking on the Iu-CS interface: the BSC6900 and the MSC are physically
connected, and the MSC is running normally.
l 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 normal; the MSC Server and the MGW are running normally.
Procedure
l Verifying the Iu-CS Interface (Iu-CS over ATM)
1. Run the MML command DSP SAALLNK to query the status of the SAAL link.

2. Run the MML command DSP MTP3LNK to query the status of the MTP3 link.

signaling point.


BSC6900 GU
6. Run the MML command LST GCNNODE or LST UCNNODE to check whether
the CN node in the CS domain is configured.
Expected result: 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 GCNNODE or ADD UCNNODE to
configure the corresponding CN node.
the Iu-CS interface.
8. Optional: Perform VCL continuity check on all the AAL2 paths over the Iu-CS
interface. For details, see 15.2 Performing VCL Continuity Check.
l Verifying the Iu-CS Interface (Iu-CS over IP)

NOTE
2. Run the MML command DSP M3LNK to query the status of the M3UA link.
signaling point.

BSC6900 GU
the CN node in the CS domain is configured.
Expected result: The value of CN domain ID is CS_DOMAIN.

CS_DOMAIN, run the MML command ADD GCNNODE or ADD UCNNODE to
7. Run the MML command DSP IPPATH to query the status of the IP path on the Iu-
CS interface.
----End
9.8 Verifying the Iu-PS Interface

This section describes how to verify the control plane and the user plane of the Iu-PS interface.
The Iu-PS interface verification varies according to the transmission mode over the Iu-PS
interface.
Prerequisite
l The BSC6900 and the SGSN are physically connected, and the hardware installation
l The SGSN used to verify the Iu-PS interface operates normally.
Procedure
l Verifying the Iu-PS Interface (Iu-PS over ATM)


3. Run the MML command DSP SSN to query the status of the Signaling Connection
Control Part Sub-System Number (SCCP SSN).

BSC6900 GU
signaling point.

the CN node in the PS domain is configured.
Expected result: The value of CN domain ID is PS_DOMAIN.

PS_DOMAIN, run the MML command ADD GCNNODE or ADD UCNNODE to
7. Run the MML command PING IP to check whether the connection to the SGSN is
normal.
Expected result: the SGSN can be pinged.
If the SGSN cannot be pinged, check whether a firewall is configured at the SGSN.
If a firewall does not exist, perform VCL continuity check on all the IPoa PVCs on
the Iu-PS interface. For details, see 15.2 Performing VCL Continuity Check.
l Verifying the Iu-PS Interface (Iu-PS over IP)

NOTE
Expectation: The value of Operation state is Activated state.

BSC6900 GU
signaling point.
the CN node in the PS domain is configured.
Expected result: The value of CN domain ID is PS_DOMAIN.

PS_DOMAIN, run the MML command ADD GCNNODE or ADD UCNNODE to
7. Run the MML command DSP IPPATH to query the status of the IP path on the Iu-
PS interface.
----End
9.9 Verifying the Iur Interface

This section describes how to verify the control plane and the user plane of the Iur interface
when the BSC6900 is connected to the RNC. The Iur interface verification varies according to
the transmission mode over the Iur interface.
Prerequisite
l The BSC6900 and the RNC is physically connected, and the hardware installation
l The RNC used to verify the Iur interface operates normally.
Context
To perform this task, ensure that the RNC at the other end of the Iur interface is commissioned.

BSC6900 GU
Procedure
l Verifying the Iur Interface (Iur over ATM)
signaling point.
the Iur interface.
7. Optional: If the BSC6900 is configured with the IP path to the RNC, run the MML
command PING IP to check whether the connection to the RNC 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 VCL continuity check on all the IPoa PVCs
on the Iur interface. For details, see 15.2 Performing VCL Continuity Check.
l Verifying the Iur Interface (Iur over IP)

BSC6900 GU

NOTE
signaling point.
6. Run the MML command DSP IPPATH to query the status of the IP path on the Iur
interface.
----End
9.10 Verifying the Iu-BC Interface

This section describes how to verify that the user plane of the Iu-BC interface is operational.
Prerequisite
Procedure
Step 1 Run the PING IP command. Set Source IP address to the IP address of the Iu-BC interface
board at the local end and set Destination IP address to the IP address of the Cell Broadcast

BSC6900 GU
Center (CBC) server at the peer end to query the connectivity between the BSC6900 and the
CBC.
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 on the BSC6900 and on the CBC are
correctly configured.
----End

BSC6900 GU 10 Handling the Alarms Generated During the
Commissioning Guide Commissioning
10 Handling the Alarms Generated During

the Commissioning
This chapter describes how to handle the alarms generated during the commissioning, thus
preventing the alarms from affecting the verification of services.
Prerequisite
l The communication between the BSC6900 and the OMU is normal.
Procedure
Step 1 Click the Alarm on the LMT main page. The Alarm tab page is displayed.
Step 2 Check whether any alarm is listed on the Fault tab page.
If... Then...
No alarm is listed, End this task.
One or more alarms are listed, Go to step Step 3.
Step 3 Double-click the alarm to be handled in the fault tab page. The Alarm Detailed Information
dialog box is displayed.
Step 4 Click Solution.... The LMT Online Help interface is displayed.
Step 5 Follow the suggestions to handle the alarm.
Step 6 Repeat step Step 3 to Step 5 to handle other alarms.
----End

BSC6900 GU
Commissioning Guide 11 Verifying the GSM Services
11 Verifying the GSM Services
This chapter describes how to verify that the GSM basic services and the feature services that
are enabled are normal. The basic services consist of speech service and data service. The feature
services consist of the inter-RAT handover, location service, and AMR service.
Prerequisite
l The verification over the Abis, A, Gb, Ater and Pb interfaces is successful. The verification
over Ater interface is mandatory only in BM/TC separated mode. The verification over Pb
interface is mandatory only if the BSC6900 is configured with an external PCU.
l The MSs used for test are functional and are registered in the HLR.
Procedure
Step 1 Table 11-1 lists the procedure for verifying the basic services by testing the MS in the BTS cells.
Table 11-1 Performing dialing tests on the basic services

Basic Services Procedure for Conducting Expected Result
the Dialing Test
Speech service Make 20 calls from an MS to a The connection success rate is

fixed-line phone and hold on each higher than 90%. The voice is
call for 60 seconds. clear and without loud noise. No
call drop occurs and the system
resources are released normally
after the call is terminated.
Make 20 calls from a fixed-line The connection success rate is

phone to an MS and hold on each higher than 90%. The voice is
call for 60 seconds. clear and without loud noise. No

BSC6900 GU
11 Verifying the GSM Services Commissioning Guide

the Dialing Test
Make 20 calls from an MS to The connection success rate is

another MS and hold on each call higher than 90%. The voice is
for 60 seconds. clear and without loud noise. No
Data service Send a fax from an MS to an Faxes are sent and received
electrograph. Send a fax from an normally.
electrograph to an MS.
Test the General Packet Radio The test data rate is similar to the
Service (GPRS) or Enhanced data rate tested in a lab.
Data Rate for GSM Evolution
(EDGE) function on the MS.
NOTE
If the result of service verification cannot meet the expected results, start message tracing on the LMT over the
Um, Abis, A, Gb, Pb, and Ater interfaces. Where the message tracing over the Pb interface is mandatory only
when the BSC6900 is configured with an external PCU, and the message tracing over the Ater interface is
mandatory only in BM/TC separated mode.
Step 2 Table 11-2 lists the procedure for verifying the feature services by testing the MS in the BTS
cells.
Table 11-2 Performing dialing tests on the feature services

Feature Services Procedure for Conducting Expected Result
the Dialing Test
Inter-RAT handover Hand over a dual-mode MS from The connection success rate is
the GSM to the UMTS for 20 higher than 90%. The voice is
times. Hand over a dual-mode clear and without loud noise.
MS from the UMTS to the GSM
for 20 times.
Location service Make a call from the MS and hold The location of the MS conforms
on the call. Then, locate the MS. to the precision requirements.
Adaptive Multi Rate Make 50 calls from an MS to a The connection success rate is
(AMR) service fixed-line phone and select voice higher than 90%. The voice is
version to AMR. clear and without loud noise.
----End

BSC6900 GU
Commissioning Guide 12 Verifying the UMTS Services
12 Verifying the UMTS Services
This chapter describes how to verify that the UMTS basic services and the feature services that
are enabled are normal. The basic services consist of voice service, CS streaming service, PS
service, and mobility management service. Feature services consist of inter-RAT handover,
HSDPA service, HSUPA service, 64QAM service, and MIMO service.
Prerequisite
l The verification over the Iub, Iu-CS, Iu-PS, and Iur interfaces is successful. The verification
over the Iur interface is mandatory only when the BSC6900 is connected to the RNC.
l The UEs used for test are operational and are registered in the HLR.
Procedure
Step 1 Table 12-1 lists the procedure for verifying the basic services by testing the UE in the NodeB
cells.
Table 12-1 Performing dialing tests on the basic services

the Dialing Test
Speech service Make 20 calls from a UE to a The connection success rate is

fixed-line phone and hold on higher than 95%. The voice is
each call for 60 seconds. clear without loud noise. No call
drop occurs and the system
Make 20 calls from a fixed-line The connection success rate is

phone to a UE and hold on each higher than 95%. The voice is
call for 60 seconds. clear without loud noise. No call

BSC6900 GU
12 Verifying the UMTS Services Commissioning Guide

the Dialing Test
Make 20 calls from a UE to The connection success rate is

another UE and hold on each higher than 95%. The voice is
call for 60 seconds. clear without loud noise. No call
CS streaming service Make two video calls from a UE The sound is clear, the video is
to another UE. continuous, and the voice is
synchronous with the video.
PS service Activate the 384 kbit/s services. The activation success rate is
Access the Web server and higher than 95% and the web
browse web pages on a UE. page can be browsed normally.
Perform the verification for 20
times.
Mobility management Perform 20 soft handovers on The handover success rate is

service the CS voice service. higher than 95%.
Perform 20 soft handovers on The handover success rate is

the PS service. higher than 95%.
NOTE
If the result of service verification cannot meet the expected result, start the following message tracing tasks:
tracing over the UE, cell, and interfaces including Uu, Iu, Iub, and Iur (mandatory only in inter-RNC handover).
Step 2 Table 12-2 lists the procedure for verifying the feature services by testing the UE in the NodeB
cells.
Table 12-2 Performing dialing tests on the feature services

the Dialing Test
Inter-RAT handover Hand over a dual-mode UE The connection success rate is

from UMTS to GSM for 20 higher than 90%. For CS
times on CS and PS services services, the voice is clear
respectively. Hand over a dual- without loud noise; For PS
mode UE from GSM to UMTS service, no call drop occurs.
for 20 times on CS and PS
services respectively.
High Speed Downlink Activate the high-speed PS The activation success rate is
Packet Access service, access the FTP server, higher than 90% and the
(HSDPA) service and download large files for 10 downloading is normal.
times. The assigned downlink
rate of services is required to be
over 384 kbit/s.

BSC6900 GU
Commissioning Guide 12 Verifying the UMTS Services

the Dialing Test
High Speed Uplink Activate the high-speed PS The activation success rate is
Packet Access service, access the FTP server, higher than 90% and the
(HSUPA) service and upload large files for 10 uploading is normal.
times. The assigned uplink rate
of services is required to be over
384 kbit/s.
64QAM service Activate the high-speed PS The activation success rate is

service, access the FTP server, higher than 90% and the
and download large files for 10 downloading is normal.
over 384 kbit/s.
Multiple Input Activate the high-speed PS The activation success rate is

Multiple Output service, access the FTP server, higher than 90% and the
(MIMO) service and download large files for 10 downloading is normal.
over 384 kbit/s.
----End

BSC6900 GU
Commissioning Guide 13 Connecting the BSC6900 to the M2000
13 Connecting the BSC6900 to the M2000
This chapter describes how to connect the BSC6900 to the M2000 for the centralized
management.
Prerequisite
l The Operation and Maintenance (OM) network has passed commissioning. The M2000 is
operational.
l The version of the M2000 is compatible with that of the BSC6900.
Context
l If the BSC6900 and the M2000 are in the same network segment, you need not configure
the IP route to the M2000.
l If the BSC6900 and the M2000 are not in the same network segment, you need to configure
the IP route to the M2000.
Procedure
Step 1 Connect the BSC6900 to the OM network.
1. Connect one end of the straight-through cable to the LAN Switch that is connected to the
BSC6900.
2. Connect the other end of the straight-through cable to the network device, for example, a
hub or a router.
Step 2 Configure the IP route from the BSC6900 to the M2000.

1. Run the MML command LST OMUIPRT to check whether the route to the M2000 is
configured on the OMU.
l If the values of Destination Network Address, Destination Address Mask, and
Forward Route Address in the result are consistent with the planned addresses, then
you can infer that the BSC6900 already has a route to the M2000. Go to step Step
2.3.
l If the Destination Network Address, Destination Address Mask, and Forward
Route Address in the result are not consistent with the planned addresses, then you can
infer that the BSC6900 does not have a route to the M2000. Go to step Step 2.2.

BSC6900 GU
13 Connecting the BSC6900 to the M2000 Commissioning Guide
2. Run the MML command ADD OMUIPRT to configure the route from the BSC6900 to
the M2000.
3. Verify the configuration of the route from the BSC6900 to the router.
Logging in to the OMU remotely, run the ping command to check whether the network
between the BSC6900 and the router is operational. If the OMU can receive a response
packet from the router, go to step Step 2.4. Otherwise, check that the OMU and the router
are properly connected.
4. Verify the configuration of the route from the BSC6900 to the M2000.
Logging in to the OMU remotely, run the ping command to check whether the network
between the BSC6900 and the M2000 is operational. If the BSC6900 can receive a response
packet from the router, go to step Step 3. Otherwise, check that the M2000 and the router
are properly connected.
Step 3 Create the BSC6900 on the M2000. For details, see the NE creating-related parts in M2000
documents.
CAUTION
l If a firewall exists between BSC6900 and M2000, ensure the communication ports
connecting the BSC6900 and M2000.
l For details on the ports connecting the BSC6900 and M2000, see 16.1 Communication
Ports Used by the BSC6900.
----End
Example
Table 13-1 describes how to configure the route between the BSC6900 and the M2000.
Table 13-1 Configuring the route from the BSC6900 to the M2000
Scenar The IP address of the M2000 server is 10.11.100.23. The mask is 255.255.255.0.
io The OMU is connected to the M2000 network segment through the router. The IP
address of the router is 172.121.139.10.
Action 1. Run the MML command ADD OMUIPRT.

l Set Destination Network Address to 10.11.100.23.
l Set Destination Address Mask to 255.255.255.0.
l Set Forward Route Address to 172.121.139.10.
2. Run the Telnet client, such as PuTTY, to log in to the OMU.
3. Run the ping 172.121.139.10 command.
4. Run the ping 10.11.100.23 command.

BSC6900 GU
Commissioning Guide 14 Creating Scheduled Tasks
14 Creating Scheduled Tasks
This chapter describes how to create the scheduled tasks for the automatic backup of the system
data and logs after commissioning; thus, the data and logs can be used for the BSC6900
equipment fault recovery.
Prerequisite
l The BSC6900 has passed the commissioning.
l To create scheduled tasks, you must be an administrator.
Context
You can set the period for the scheduled task according to the actual situation. The period for
the scheduled task is of the following types: fixed time, day based scheduling, day based duration,
week based scheduling, week based duration, month based scheduling, and month based
duration.
l Scheduled tasks for backing up system data
After the scheduled task is executed, you can obtain the latest backup file from the backup
directory on the OMU. For the backup directory and the file name, see the Help
Information of the MML command BKP DB.
l Scheduled tasks for backing up logs
The logs are backed up in the OMU active workspace directory/ftp directory as compressed
files at the specified time. Assume that the active workspace is version_a, then the logs
are backed up in /mbsc/bam/version_a/bin/fam. Table 14-1 lists the name of the
compressed files.
Table 14-1 Log type and file name
Type File Name
ALL FixInfo_All.zip
OMU FixInfo_OMU.zip
HOST FixInfo_HOST.zip

BSC6900 GU
14 Creating Scheduled Tasks Commissioning Guide
To check the information of the logs, download the logs through the FTP client. For details,
see the help information of the FTP client.
NOTE
l The files that are automatically backed up do not overwrite the files backed up earlier.
l For the directory structure of the OMU workspace, see Checking the Installation Directory of the OMU
Applications.
Procedure
Step 1 Run the MML command ADD SCHTSK. Specify the Task Name and Task ID to add a
scheduled task.
Step 2 Run the MML command ADD SUBTSK. Set Command String to BKP DB to create a
scheduled task for backing up the system data.
Step 3 Run the MML command ADD SUBTSK. Set Command String to COL LOG to create a
scheduled task for backing up logs.
l To view the created tasks, run the MML command LST SUBTSK.
l To change the time and period for backing up tasks, run the MML command MOD
SUBTSK.
----End
Example
l To set the system data to be backed up at 2010-4-12-12:00:00, run the following command:
ADD SUBTSK: ID=1, SUBID=8, SCMD="BKP DB:", FREQ=ONTIME,
SD=2010&04&12, TM=12&00;
l To set the BSC6900 logs to be automatically backed up from 2010-4-10-11:01:52 to
2010-4-12-11:01:52 (log type: ALL, time mode: fixed time), run the following command:
ADD SUBTSK: ID=1, SUBID=44, SCMD="COL LOG: TP=ALL,
ST=2010&04&10&11&01&52, ET=2010&04&12&11&01&52", FREQ=ONTIME,
SD=2010&04&13, TM=12&00;

BSC6900 GU
Commissioning Guide 15 FAQ
15 FAQ
About This Chapter
This chapter describes how to handle the common problems during the commissioning.
15.1 Checking the Transmission Link

This section describes how to verify that the terrestrial transmission links of the BSC6900 are
functional. The verification covers E1/T1 port, FE/GE port, optical port, and upper-layer link.
15.2 Performing VCL Continuity Check
This section describes how to perform VCL continuity check on links over interfaces.
15.3 Unavailable E1/T1 Port
This section describes how to handle the problem that the E1/T1 port is unavailable.
15.4 Unavailable FE/GE Port
This section describes how to handle the problem that the FE/GE port is unavailable.
15.5 Cell Setup Failure
This section describes how to handle cell setup failures.
15.6 Signaling Link Failure on the Iub Interface
This section describes how to handle signaling link failures on the Iub interface.
15.7 AAL2/IP Connection Setup Failure
This section describes how to handle the failures during AAL2/IP connection setup.
15.8 Data Loading Failure on the Board
This section describes how to handle the failures that occur during data loading to the
BSC6900 board.
15.9 Performing the Loopback Test on the E1/T1 Port
This section describes how to perform the loopback test to check whether the E1/T1 port is
functional.
15.10 Performing the Loopback Test on the Optical Port
This section describes how to perform the group loopback test to check whether the optical port
is functional.

BSC6900 GU
15 FAQ Commissioning Guide
15.1 Checking the Transmission Link

This section describes how to verify that the terrestrial transmission links of the BSC6900 are
functional. The verification covers E1/T1 port, FE/GE port, optical port, and upper-layer link.
Prerequisite
Procedure
l Check the status of the transmission link based on the transmission mode.
Table 15-1 Methods for checking the status of the transmission link in different
transmission modes
If the transmission on the interface is Then...
over...
A IMA/UNI/FRA transmission mode 1. In the case of channelized STM-1

T transmission over interface, check
M the status of the optical port.
2. Check the status of the E1/T1
port.
3. Check the status of the upper-layer
link.
l For the IMA transmission mode,
run the MML command DSP
IMAGRP to check the status of
the IMA group.
l For the UNI transmission mode,
UNILNK to check the status of
the UNI link.
l For the FRA transmission mode,
FRALNK to check the status of
the fractional IMA/ATM link.
NOTE
If the upper-layer link is not
functional, run the MML command
LST IMAGRP/LST UNILNK/
LST FRALNK accordingly to
check whether the data configuration
on the interface is correct.
NCOPT transmission mode Check the status of the optical port.

BSC6900 GU
If the transmission on the interface is Then...

over...
I PPP/MLPPP transmission mode 1. In the case of channelized STM-1

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

D
M Channelized STM-1 transmission mode Check the status of the optical port.
HDLC Check the status of the E1/T1 port.
FR Check the status of the E1/T1 port.
l Checking the status of the E1/T1 port

1. Run the MML command DSP E1T1 to query the status of the E1/T1 ports.
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 the 15.3 Unavailable E1/
T1 Port for troubleshooting.
l Checking the status of the 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 occur, see 15.4 Unavailable FE/GE Port for
troubleshooting.
– The value of Link Availability Status is Unavailable.

BSC6900 GU
– The value of Port state is Deactivated.

2. Optional: Check the connectivity of the gateway (mandatory in three-layer
networking).
(1) Run the MML command LST IPCHK to query the configuration of the gateway
connectivity check.
(2) Run the MML command STR IPCHK to start the gateway connectivity 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.
(3) In the alarm tab page of the LMT, check whether the ALM-21346 IP Connectivity
Check Failure alarm is reported. If yes, clear the alarm as suggested.
(4) To keep the gateway connectivity check, end this task; otherwise, run the MML
command STP IPCHK to stop the gateway connectivity check.
l Checking the status of the optical port
1. Run the MML command DSP OPT to query the status of the optical port.
Expected result: The value of Optical port state is Available.
If the value of Optical port state is not normal, check the alarms related to the optical
port and rectify the fault according to the alarm handling suggestion.
----End
15.2 Performing VCL Continuity Check

This section describes how to perform VCL continuity check on links over interfaces.
Prerequisite
l The peer end (NodeB, MGW, MSC, or SGSN) supports the F5 protocol.
Context
Only the VCL that carries the SAAL link, IPoA PVC, or AAL2 path supports the continuity
check.
Procedure
l Perform continuity check on the SAAL link.
1. Run the MML command ACT VCLCC, and then set Link type to SAALLNK, 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 SAALLNK to
query the result of the continuity check on the VCL.
Expected result: The values of LOC alarm, AIS alarm, RDI alarm, CC activated
failure alarm, and LB failure alarm are all Normal.
If any of the preceding parameters is of an abnormal value, check whether the
following alarms are reported. If yes, rectify the fault according to the alarm handling
suggestion.

BSC6900 GU
– ALM-21321 VCL CC Detection Failure

– ALM-21322 VCL Alarm Indication Signal
– ALM-21323 VCL Remote Alarm Indication
– ALM-21324 VCL CC Activation Failure
– ALM-21326 VCL LB Detection Failure
3. Optional: To keep the VCL continuity check, end this task; otherwise, run the MML
command DEA VCLCC, and then set Link type to SAALLNK to deactivate the
continuity check on the VCL.
l Perform continuity check on the AAL2 path.
1. Run the MML command ACT VCLCC, and then set Link type to AAL2PATH,
VCL act type to CC, and Activation direction to BOTH to activate the continuity
check on the VCL.
2. Run the MML command DSP VCLCC, and then set Link type to AAL2PATH to
query the result of the continuity check on the VCL.

suggestion.
command DEA VCLCC, and then set Link type to AAL2PATH to deactivate the
l Perform continuity check on the IPoA PVC.
1. Run the MML command ACT VCLCC, and then set Link type to IPOAPVC, VCL
act type to CC, and Activation direction to BOTH to activate the continuity check
on the VCL.
2. Run the MML command DSP VCLCC, and then set Link type to IPOAPVC to query
the result of the continuity check on the VCL.

suggestion.

BSC6900 GU

command DEA VCLCC, and then set Link type to IPOAPVC to deactivate the
----End
15.3 Unavailable E1/T1 Port

This section describes how to handle the problem that the E1/T1 port is unavailable.
Symptom
When you run the MML command DSP E1T1 to check the status of E1/T1 ports, the Port
running state on the returned result shows Port is down.
Solution
1. If the value of Port running state is Port is down, handle the problem as follows:
l When electrical ports serve as the bearers, perform loopback test on the faulty E1/T1
ports. For details, see 15.9 Performing the Loopback Test on the E1/T1 Port.
l When optical ports serve as the bearers, perform group loopback test on the faulty optical
ports. For details, see 15.10 Performing the Loopback Test on the Optical Port.
2. Check whether the following alarms are listed in the alarm tab page of the LMT. If any of
the alarms exist, handle them according to the suggestions in the online help.
l ALM-21201 E1/T1 Loss of Signal
l ALM-21261 SDH/SONET LP Remote Defect Indication
l ALM-21202 E1/T1 Loss of Frame Alignment
l ALM-21241 Loss of Fractional IMA Frame
l ALM-21203 E1/T1 Remote Alarm Indication Signal
l ALM-21205 E1/T1 Loss of Multiframe Alignment
NOTE
When you run the MML command DSP E1T1 to check the E1/T1 port status, the value of Is this
E1/T1 occupied may be set to NO. In such a case, if the ALM-21201 E1/T1 Loss of Signal or
ALM-21261 SDH/SONET LP Remote Defect Indication exists, the link is still operational.
15.4 Unavailable FE/GE Port

This section describes how to handle the problem that the FE/GE port is unavailable.
Symptom
When you run the MML command DSP ETHPORT to check the status of the FE/GE port, any
of the following situation exists:
l The value of Link Availability Status is Unavailable.
l The value of Port state is Deactivated.

BSC6900 GU
Solution
1. If the value of Link Availability Status is Unavailable, check the connection of the
Ethernet cable and check whether the peer Ethernet port is enabled. See the online help for
the handling suggestions of the alarm.
2. If the value of Port state is Deactivated, run the MML command ACT ETHPORT to
activate the FE/GE port.
15.5 Cell Setup Failure

This section describes how to handle cell setup failures.
Symptom
During the verification of cell setups, the final result is not as expected. The operational state of
the cell is Unavailable and the Iub interface tracing function cannot trace the complete cell setup
procedure on the Iub interface.
Fault Locating Policy
CAUTION
l If the Iub interface is over ATM transmission, check whether the alarms related to the DPUb
or DPUe board, 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 according to the methods provided here.
l If the Iub interface is over IP transmission, check whether the alarms related to the DPUb or
DPUe board, DSP, and SCTP link exist in the alarm management system when cell setup
failure occurs. If such alarms exist, handle the alarms according to the suggestions in the
Alarm Handling part. If the alarms persist, handle them according to the methods provided
here.
l If the Iub interface is over ATM/IP dual-stack transmission, check whether the alarms related
to the DPUb or DPUe board, DSP, SAAL link, SCTP link, IMA, optical ports, and AAL2
exist in the alarm management system when cell setup failure occurs. If such alarms exist,
handle the alarms according to the suggestions in the Alarm Handling part. If the alarms
persist, handle them according to the methods provided here.
To locate the fault, determine whether the NodeB or the BSC6900 is faulty by comparing the
results of the Iub interface message tracing with that in normal situation. Then, further locate
the fault using other methods.
Figure 15-1 and Figure 15-2 show how to locate cell setup failures.

BSC6900 GU
Figure 15-1 Locating cell setup failures (1)
Table 15-2 Operation index (1)

Index Action Step
*1-1 Check whether the Iub link See 15.1 Checking the Transmission
works properly. Link.
*1-2 Handle link failures on the Iub See 15.6 Signaling Link Failure on the
interface. Iub Interface.

BSC6900 GU
Index Action Step
*1-3 Check whether the audit See Solution 1: Checking the Audit
response message is correct. Response Message.
*1-4 Unblock the cell. See Solution 2: Unblocking Cells.
*1-5 Change the configured See Solution 3: Changing the

maximum downlink transmit Configured Maximum Downlink
power according to the Transmit Power According to the
reporting ability of the NodeB. Reporting Ability of the NodeB.
*1-6 Check whether the DSP l Run the MML command DSP DSP to
resources are available. 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 setup
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 See Solution 6: Checking TNL

resources are available. Resources.
Figure 15-2 Locating cell setup failures (2)

BSC6900 GU
Index Action Step
*2-1 Check whether the PRACH See Solution 4: Checking the PRACH
setup response message is Setup Response Message.
correct.
*2-2 Check whether the Iub link See 15.1 Checking the Transmission
works properly. Link.
*2-3 Handle link failures on the Iub See 15.6 Signaling Link Failure on the
interface. Iub Interface.
*2-4 Check whether the AAL2/IP l For ATM transmission, check whether
link setup is successful. 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 15.2 Performing 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. If the transmission resource group
is configured, run the MML
command DSP RSCGRP to query
the states of the transmission
resource groups.
*2-5 Handle the AAL2/IP link setup See 15.7 AAL2/IP Connection Setup
failures. Failure.
*2-6 Check whether the SCCPCH See Solution 5: Checking the SCCPCH
setup response massage is Setup Response Message.
correct.
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.
l If LocalCell is configured to belong to a LocalCellGroup, then the associated
LocalCellGroup exists.

BSC6900 GU
Solution 2: Unblocking Cells

l If the cell is blocked by the BSC6900, run the MML command UBL UCELLto unblock
the cell.
l If the cell is blocked by the NodeB, contact the NodeB maintenance personnel for
troubleshooting.
Solution 3: Changing the Configured Maximum Downlink Transmit Power

According to the Reporting Ability of the NodeB
Run the MML command to query the cell maximum downlink transmit power
(MAXTXPOWER) 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 previously mentioned requirement cannot be met, run the MML command MOD
UCELL to change the cell maximum transmit power or request the NodeB to change the reported
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 information of RachInfo, TranspLayerAddr, and BindingId exist.
l The transport channel ID of RACH displayed in the messages should be the same as that
configured in the database.
l The value of TranspLayerAddr in the message is consistent with that in the database.
NOTE
When the user plane is over ATM transmission, the value of TranspLayerAddr is the ATM address. Run the
MML command LST UNODEB to check whether the ATM address configured is consistent with that in the
PRACH setup response message.
When the user plane is over IP transmission, the value of TranspLayerAddr 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 correct SCCPCH setup response message are as follows:
l The information of FachInfo, PchInfo, TranspLayerAddr, and BindingId exist.
l The transport channel ID of the FACH or PCH displayed in the messages should be the
same as that configured in the database.
l The value of TranspLayerAddr in the message is consistent with that in the database.
NOTE
When the user plane is over ATM transmission, the value of TranspLayerAddr 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 TranspLayerAddr 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.

BSC6900 GU
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. Run the MML command LST AAL2PATH to check the configuration of the AAL2 path
of the adjacent node.
3. Run the MML command LST TRMMAP to check whether the AAL2 path mapped by the
R99 RT service (service type of the common channel) exists, and check whether the
bandwidth meets the requirements of the common channel. If the AAL2 path does not exist,
add the associated AAL2 path. If the bandwidth does not meet the requirements of the
common channel, add an AAL2 path or modify the configuration of the AAL2 path.
4. Run the MML command LST AAL2RT to check whether the AAL2 route to the adjacent
node is configured. If it is not configured, add the route.
15.6 Signaling Link Failure on the Iub Interface

This section describes how to handle signaling link failures on the Iub interface.
Symptom
During the cell setup, the signaling link on the Iub interface is faulty. The
NBAP_AUDIT_REQ message cannot be traced through the Iub interface tracing. The alarms
related to the DPUb board or DSP are not reported.
Solution
1. For Iub over ATM transmission, check whether the alarms related to E1/T1 ports, FE/GE
ports, SAAL links, IMA, UNI, NCP, or CCP are reported. If such alarms exist, handle them
as suggested. If the alarms persist, handle them according to Figure 15-3.

BSC6900 GU
Figure 15-3 Handling of signaling link failures on the Iub interface over ATM transmission

Index Action Step
*1-1 Add the upper-layer Run the MML commands ADD UNCP, ADD
application of the UCCP, and ADD ADJNODE to add NCP, CCP, and
SAAL link. ALCAP respectively.
*1-2 Check and handle See 15.3 Unavailable E1/T1 Port.

physical connection
failures.

BSC6900 GU
Index Action Step
*1-3 Check the data Perform the following steps:

configuration. 1. Run the MML command LST SAALLNK to
check the consistency of the negotiated data
configuration 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 15-3.
2. Run the MML command LST E1T1 to check the
consistency of coding modes at the two ends.
in Figure 15-3.
3. Run the MML command LST IMAGRP to check
the consistency of the IMA protocol version
configuration at the two ends.
in Figure 15-3.
*1-4 Modify data 1. Modify the SAAL link configuration as follows:

configuration. a. Run the MML command RMV UNCP, RMV
UCCP, or RMV ADJNODE to delete the
upper-layer application.
b. Run the MML command RMV SAALLNK to
delete the SAAL link.
c. Run the MML command ADD SAALLNK to
add the SAAL link as negotiated.
d. Run the MML command ADD UNCP, ADD
UCCP, or ADD ADJNODE to add the upper-
layer application.
2. Run the MML command SET E1T1 to change the
E1/T1 coding mode as negotiated.
3. Run the MML command MOD IMAGRP to
change the configuration of the IMA protocol
version.
2. For Iub over IP transmission, check whether the alarms related to E1/T1, FE/GE ports,
SCTP links, NCP, or CCP are reported. If such alarms exist, handle them according to the
suggestions in the Alarm Handling part. If the alarms persist, handle them according to
Figure 15-4.

BSC6900 GU
Figure 15-4 Handling of signaling link failures on the Iub interface over IP transmission
Index Action Step
*2-1 Check whether the Run the MML command DSP SCTPLNK to check
SCTP link works whether the SCTP link works properly.
properly.
*2-2 Add the upper-layer Run the MML commands ADD UNCP and ADD
application to the UCCP to add the upper-layer application to the
SCTP link. SCTP link.
*2-3 Check whether the See 15.1 Checking the Transmission Link.
transmission link
works properly.
*2-4 Handle the 1. If the data is transmitted over Ethernet, for

transmission link example, through FE ports, see 15.4 Unavailable
failure. FE/GE Port.
2. If the data is transmitted over a private line, for
example, over E1/T1 cable, see 15.3 Unavailable
E1/T1 Port.
*2-5 Check the data Run the LST SCTPLNK command to check the
configuration. 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
15-4.
*2-6 Modify data Modify the configuration on the SCTP link. Run the
configuration. MOD SCTPLNK command to modify the
configuration on the SCTP link.
3. For Iub over ATM/IP dual-stack transmission, handle the failures according to the
suggestions in the ATM transmission and IP transmission as required.

BSC6900 GU
15.7 AAL2/IP Connection Setup Failure

This section describes how to handle the failures during AAL2/IP connection setup.
Symptom
During AAL2 or IP connection setup or during cell setup, the AAL2 or IP link fails to be
established.
Solution
1. 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 any of the preceding alarms is
reported, clear the alarm as suggested. If the alarm cannot be cleared, handle it according
to Figure 15-5.
Figure 15-5 Procedure for handling AAL2 connection setup failure

BSC6900 GU

Index Action Remarks
*1-1 Check and modify the Check the data configuration. If the data
local data configuration. configuration is inconsistent with the negotiated
data, modify the data configuration according to
the negotiated data, as described in Table 15-7.
*1-2 Handle Iub interface See 15.6 Signaling Link Failure on the Iub
link failures. Interface.
Table 15-7 Checking and modifying the data configuration

Command Item If No
LST Whether the adjacent node Run the MML command ADD
ADJNODE is configured. ADJNODE to configure adjacent node.
LST Whether the AAL2 path to Run the MML command ADD
AAL2PAT the adjacent node is AAL2PATH to add an AAL2 path.
H configured.
Whether the path ID is 1. Run the MML command RMV

consistent with the AAL2PATH to delete this AAL2
negotiated data. path.
2. Run the MML command ADD
AAL2PATH to add an AAL2 path.
Whether the bandwidth is 1. Run the MML command RMV

consistent with the AAL2PATH to delete this AAL2
negotiated data. path.
AAL2PATH to add an AAL2 path.
LST Whether the IP route to a Run the MML command ADD

AAL2RT specified adjacent node is AAL2RT to add an IP route to the
configured. specified adjacent node.
Whether the ATM address 1. Run the MML command RMV

(NSAP) is correct. AAL2RT to delete the IP route.
AAL2RT to add an IP route.
2. When the user plane is over IP transmission, handle the failure according to Table 15-8.

BSC6900 GU

Index Action Remarks
*2-1 Determine the IP Run the MML commands LST IPPATH and LST
path that carries TRMMAP to obtain the ID of the IP path that carries the
the common common channel.
channel.
*2-2 Check whether 1. Run the MML command DSP IPPATH to query the
the IP path is status of the IP path.
operational. 2. 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 *2-3.
*2-3 Check whether 1. See 15.1 Checking the Transmission Link.

the transmission 2. If the transmission link is unavailable, go to *2-4.
link is
operational. 3. If the transmission link is available, go to *2-5.
*2-4 Handle the 1. If the data is transmitted over Ethernet, for example,
transmission link through FE ports, see 15.4 Unavailable FE/GE Port.
failure. 2. If the data is transmitted over a private line, for example,
over E1/T1 cable, see 15.3 Unavailable E1/T1 Port.
*2-5 Check the Run the MML command LST IPPATH to check whether
configuration of the negotiated data is consistent. If inconsistency exists,
the IP path. modify the negotiated data.
*2-6 Check the real- Run the MML command DSP IPRT to check the real-time
time IP route IP route information.
information.
15.8 Data Loading Failure on the Board

This section describes how to handle the failures that occur during data loading to the
BSC6900 board.
Symptom
The status of the board on the device panel is abnormal when the BSC6900 board software and
data files are being loaded to the BSC6900 boards.
Solution
1. Check the board status of other boards of the same type in this subrack.

BSC6900 GU
If... Then...
Board status of other boards of Replace the faulty board and then reload the data to
the same type is Normal, the new board.
Board status of other boards of Go to step 2.

the same type is Faulty,
2. Check whether the DIP switch on the subrack is set as configured.
If... Then...
The DIP switch on the subrack Correct the DIP switch setting and then reload the
is not set as configured, data to the board.
The DIP switch on the subrack Go to step 3.

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

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

set,
6. If the data loading on the SPUa or SPUb board fails, run the MML commands LST
URNCBASIC to check whether the BSC6900 basic information is properly set.

BSC6900 GU
If... Then...
The setting is incorrect, Correct the BSC6900 basic information, and then
reload the data to the board.
The setting is correct, Go to step 7.
7. If the data loading on the DPUb or DPUc board in the remote TCS fails, run the MML
command DSP ATEROML to check whether the OML on the Ater interface is functional,
and then run the MML command DSP E1T1 to check whether the physical links between
the Ater interface boards is functional.
If... Then...
The OML is faulty, and the 1. Check whether the configuration is consistent with
physical link is functional, the physical OML connection. If they are
inconsistent, modify the configuration according
to the physical OML connection.
2. Check whether the cross connection exists in the
physical OML. If yes, correct the physical
connection of the OML, and then reload the data
to the board.
The OML is faulty, and the Correct the connection, and then reload the data to the
physical link is also faulty, board.
The OML is functional, Go to step 8.
8. Check whether any alarm related to board fault is present in the Alarm tab page.
If... Then...
Alarms related to board fault Analyze the alarm information and accordingly clear
exist, the alarm.
No alarm related to board fault Go to step 9.

exists,
9. Contact the Huawei Customer Service Center.
15.9 Performing the Loopback Test on the E1/T1 Port

This section describes how to perform the loopback test to check whether the E1/T1 port is
functional.
Prerequisite
Context
l The loopback test and the Bit Error Rate (BER) test cannot be performed simultaneously.

BSC6900 GU
l The loopback test leads to temporary interruption of services carried over this link.
l The loopback test can be performed when the E1/T1 port is unavailable.
Procedure
Step 1 Perform the loopback test on the local E1/T1 port.
Table 15-9 Procedure for performing the loopback test on the local E1/T1 port
Step Action
1-1 Run the MML command SET E1T1LOP. Set Loop type to LOCAL_LOOP(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, and then set Loop type to NO_LOOP
(No loop) to stop the loopback test on the E1/T1 port.
If... Then...
If the loopback test result is The E1/T1 port is operational. Go to step Step 2.
Succeeded,
If the loopback test result is Not The E1/T1 port is faulty. Replace the interface board
succeeded, carrying the faulty E1/T1 port.
Step 2 Perform the loopback test on the local E1/T1 cable.
Table 15-10 Procedure for performing the loopback test on the local E1/T1 cable
Step Action
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...
If the loopback test result is The local E1/T1 cable is operational. Go to step Step 3.
Succeeded,

BSC6900 GU
If... Then...
If the loopback test result is Not l Use a multimeter to measure the connectivity between
succeeded, the connector pin of the E1/T1 cable and the inner
conductor of the coaxial cable and that between the outer
shell of the connector and the shielding 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 short-
circuited. If so, make a new connector and assemble the
cable again.
If the fault persists, replace the E1/T1 cable with a new one.
Step 3 Perform the loopback test on the peer E1/T1 port.
Table 15-11 Procedure for checking the peer equipment or the transport network
Step Action
3-1 Run the MML command SET E1T1LOP. Set Loop type to REMOTE_LOOP
(Remote loop).
3-2 Run the MML command LOP E1T1 at the peer end to start the loopback test on the
E1/T1 port.
3-3 Run the MML command DSP E1T1LOP at the peer end to query the result of the
loopback test.
3-4 Run the MML command SET E1T1LOP at the peer end, and then set Loop type
to NO_LOOP(No loop) to stop the loopback test on the E1/T1 port.
If... Then...
If the loopback test result is Go to step Step 4.

Succeeded,
If the loopback test result is Not Contact the maintenance personnel for the peer equipment
succeeded, to rectify faults in the peer equipment or the transport
network.
Step 4 If the E1/T1 for loopback belongs to an IMA group, then run the MML command RST
IMAGRP. Click OK on the displayed dialog box to reset that IMA group.
----End

BSC6900 GU
15.10 Performing the Loopback Test on the Optical Port

This section describes how to perform the group loopback test to check whether the optical port
is functional.
Prerequisite
Context
The loopback test can be performed on optical port when the E1/T1 transmission link on the
standard interface is unavailable.
Procedure
Step 1 Perform the loopback test on the local optical port.
Table 15-12 Procedure for performing the loopback test on the SDH port
Step Action
1-1 Run the MML command SET OPTLOP, and then set Loop type to
LOCAL_LOOP(LOCAL_LOOP).
1-2 Run the MML command DSP OPT to query the result of the loopback.
1-3 Run the MML command SET E1T1LOP, and then set Loop type to NO_LOOP
(NO_LOOP) to stop the loopback test on the optical port.
If... Then...
The values of Optical port state in the The SDH port is operational. Go to step Step 2.
result are Available,
The values of Optical port state in the The SDH port is faulty. Replace the interface
result are Fault, board carrying the faulty SDH port.
Step 2 Perform the loopback test on the local fiber.
Table 15-13 Procedure for performing the loopback test on the local fiber
Step Action
2-1 Perform fiber physical loopback at the local end, that is, connect the TX end of the
fiber to the RX end of the fiber.
2-2 Run the MML command DSP OPT to query the result of the loopback.
2-3 Stop the fiber physical loopback at the local end.

BSC6900 GU
If... Then...
The values of Optical port state in the The local fiber is operational. Go to step Step
result are Available, 3.
The values of Optical port state in the The local fiber is faulty. Replace the faulty fiber.
result are Fault,
Step 3 Perform the loopback test on the peer optical port.
Table 15-14 Procedure for performing the loopback test on the peer optical port
Step Action
3-1 Run the MML command SET OPTLOP, and then set Loop type to
REMOTE_LOOP(REMOTE_LOOP).
3-2 Run the MML command DSP OPT at the peer end to query the result of the
loopback.
3-3 Run the MML command SET E1T1LOP at the peer end, and then set Loop type
to NO_LOOP(NO_LOOP) to stop the loopback test on the optical port.
If... Then...
The values of Optical port state in the Contact the Huawei Customer Service Center.
result are Available,
The values of Optical port state in the Contact the maintenance personnel for the peer
result are Fault, equipment to rectify faults in the peer equipment
or the transport network.
----End

BSC6900 GU
Commissioning Guide 16 Appendix
16 Appendix
About This Chapter
This chapter provides the communication ports and the commissioning checklist of the
BSC6900.
16.1 Communication Ports Used by the BSC6900

This section provides communication ports used by the BSC6900.
16.2 BSC6900 Commissioning Checklist
BSC6900 commissioning checklist is for recording and checking the result of BSC6900
commissioning.

BSC6900 GU
16 Appendix Commissioning Guide
16.1 Communication Ports Used by the BSC6900

This section provides communication ports used by the BSC6900.
Table 16-1 lists the number of the communication ports used by the services of the BSC6900.
Table 16-1 Communication ports used by the services of the BSC6900

Protoc Side Side Side B Side Service Authenti
ol A A B cation
Ports Ports
(Liste (Lau
ning) nch)
TCP OMU 20 BSC6900 1024- For FTP data. FAM Load, username/
Host, 6553 software and log upload/ password
LMT, 5 download (active mode)
M2000
Server
TCP OMU 21 BSC6900 1024- For FTP control. FAM username/

Host, 6553 Load, software and log password
LMT, 5 upload/download
M2000
Server
TCP LMT 21 OMU 1024- For FTP control, this port username/
6553 for OMU password
5
TCP OMU 1500 BSC6900 1024- Exchange, communication IP Address

Host 6553 with FAM
5
TCP OMU 3389 Remote 1024- the port is used by MSTSC, username/
Desktop 6553 to maintain OMU password
5
TCP/ OMU 6000/8 LMT, 1024- MML, For Maintenance username/

SSL 000 M2000 6553 password
Server 5
TCP/ OMU 6001/8 LMT, 1024- MML, For Alarm username/

Server 5
TCP/ OMU 6006/8 LMT, 1024- LMT, For Maintenance username/

Server 5
TCP LMT 80 LMT 80 For LMT Web browsing username/

computer password

BSC6900 GU
Commissioning Guide 16 Appendix

ol A A B cation
Ports Ports
(Liste (Lau
ning) nch)
TCP/ OMU 6022/8 Equipmen 1024- MML, for equipment None

SSL 022 t debug 6553 debug console
console 5
TCP OMU 6088 Upgrade 1024- For Upgrade tool None

tool 6553
5
TCP/ OMU 6093/8 Test 1024- MML, Emulator operate None

SSL 093 validation 6553
5
TCP/ OMU 6099/8 M2000 1024- MML, data None

SSL 099 Server 6553 synchronization with
5 M2000
TCP/ OMU 6100/8 LMT 1024- MML, Alarm Box None

SSL 100 6553
5
TCP/ OMU 16002/ M2000 1024- MML, notification None

SSL 18002 Server 6553 message from performance
5 and M2000
TCP MySQ 3306 Peer OMU 1024- MySQL username/

L 6553 password
5
TCP BTS 700 SMT 1024- For local maintenance, None

6553 SMT(Station
5 Management), it will be
used before GBTS connect
in the network
TCP OMU 22 SSH 1024- Putty terminal tool port username/

Client 6553 (SSH) password
5
TCP OMU 139/44 Samba 1024- Samba service port username/

5 Client 6553 password
5
UDP OMU 67 BSC6900 1024- Load, Bootp Listen None

Host 6553
5
UDP OMU 123 NodeB/ 1024- NTP Server, slow time None
OMU 6553 synchronization, local
5 listening port

BSC6900 GU
16 Appendix Commissioning Guide

ol A A B cation
Ports Ports
(Liste (Lau
ning) nch)
UDP OMU 1234 BSC6900 1024- NTP, time synchronization None

Host 6553 with FAM, local listening
5 port
UDP OMU 11774 Peer OMU 1024- SecurityManager, for dual None
6553 OMU
5
UDP OMU 11775 Peer OMU 1024- SecurityManager, for dual None
6553 OMU
5
UDP OMU 11776 Peer OMU 1024- SecurityManager, backup None

6553 tunnel between dual OMU
5
UDP M200 123 OMU 123 NTPClient, time None

0 synchronization with
Server time's server, local
listening port
16.2 BSC6900 Commissioning Checklist

BSC6900 commissioning checklist is for recording and checking the result of BSC6900
commissioning.
BSC6900 Commissioning Checklist.


BSC6900 GU Commissioning Guide - (V900R011C00 - 03)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSC6900 GU Commissioning Guide - (V900R011C00 - 03)

Uploaded by

Copyright:

Available Formats

BSC6900 GU

Huawei Proprietary and Confidential

Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.

Trademarks and Permissions

Huawei Proprietary and Confidential

About This Document.....................................................................................................................1

5 Updating the OMU Database..................................................................................................5-1

8 Verifying Interfaces Automatically........................................................................................8-1

10 Handling the Alarms Generated During the Commissioning......................................10-1

Issue 03 (2009-12-05) Huawei Proprietary and Confidential i

12 Verifying the UMTS Services..............................................................................................12-1

ii Huawei Proprietary and Confidential Issue 03 (2009-12-05)

Figure 2-1 Typical commissioning network........................................................................................................2-2

Issue 03 (2009-12-05) Huawei Proprietary and Confidential iii

Table 2-1 Requirements for equipment status before commissioning.................................................................2-1

Issue 03 (2009-12-05) Huawei Proprietary and Confidential v

About This Document

Product Name Product Version

Issue 03 (2009-12-05) Huawei Proprietary and Confidential 1

4 Verifying the Equipment

5 Updating the OMU Database

6 Activating and Verifying the License

7 Loading BSC6900 Board Software and Data Files

8 Verifying Interfaces Automatically

9 Verifying Interfaces Manually

10 Handling the Alarms Generated During the Commissioning

11 Verifying the GSM Services

12 Verifying the UMTS Services

13 Connecting the BSC6900 to the M2000

2 Huawei Proprietary and Confidential Issue 03 (2009-12-05)

14 Creating Scheduled Tasks

Indicates a hazard with a high level of risk, which if not

Indicates a hazard with a medium or low level of risk, which

Indicates a potentially hazardous situation, which if not

Indicates a tip that may help you solve a problem or save

Provides additional information to emphasize or supplement

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

Italic Book titles are in italics.

Issue 03 (2009-12-05) Huawei Proprietary and Confidential 3

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

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

4 Huawei Proprietary and Confidential Issue 03 (2009-12-05)

Double-click Press the primary mouse button twice continuously and

Issue 03 (2009-12-05) Huawei Proprietary and Confidential 5

1 Changes in BSC6900 GU Commissioning

This chapter provides the changes in the BSC6900 GU Commissioning Guide.

Content Change Description

Issue 03 (2009-12-05) Huawei Proprietary and Confidential 1-1

Content Change Description

Content Change Description

3 Commissioning Process The step of automatically verifying interfaces is added in

1-2 Huawei Proprietary and Confidential Issue 03 (2009-12-05)

2 Prerequisites for Commissioning

Requirements for the Status of the Equipment