Sie sind auf Seite 1von 81

BSC6910 GSM

V100R015C00

Commissioning Guide
Issue

02

Date

2013-06-25

HUAWEI TECHNOLOGIES CO., LTD.

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


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

Trademarks and Permissions


and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.

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

Huawei Technologies Co., Ltd.


Address:

Huawei Industrial Base


Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website:

http://www.huawei.com

Email:

support@huawei.com

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

BSC6910 GSM
Commissioning Guide

About This Document

About This Document


Overview
BSC6910 commissioning is performed after hardware is installed and before services are
provided. It aims to ensure that the BSC6910 can work properly by performing verification tasks
related to equipment, board software and data file loading, interfaces, and services.

Product Version
The following table lists the product version related to this document.
Product Name

Product Version

BSC6910

V100R015C00

Intended Audience
This document is intended for field engineers.

Organization
1 Changes in the BSC6910 GSM Commissioning Guide
This chapter describes the changes in the BSC6910 GSM Commissioning Guide.
2 Commissioning Prerequisites
Before the BSC6910 commissioning, the status of the equipment and the network to be
commissioned must meet the conditions required. The software installation packages, licenses,
and MML command scripts required for commissioning must be ready.
3 Commissioning Process
The BSC6910 commissioning can be performed remotely, locally, or remotely with local
assistance.
4 Checking Operating Status of Hardware
Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

ii

BSC6910 GSM
Commissioning Guide

About This Document

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

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

iii

BSC6910 GSM
Commissioning Guide

About This Document

This chapter describes how to troubleshoot common problems during the commissioning.
17 Appendix
This chapter provides communication ports on and the commissioning checklist of the
BSC6910.

Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol

Description
Indicates a hazard with a high level or medium level of risk
which, if not avoided, could result in death or serious injury.
Indicates a hazard with a low level of risk which, if not
avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation that, if not
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
Indicates a tip that may help you solve a problem or save
time.
Provides additional information to emphasize or supplement
important points of the main text.

General Conventions
The general conventions that may be found in this document are defined as follows.
Convention

Description

Times New Roman

Normal paragraphs are in Times New Roman.

Boldface

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


boldface. For example, log in as user root.

Italic

Book titles are in italics.

Courier New

Examples of information displayed on the screen are in


Courier New.

Command Conventions
The command conventions that may be found in this document are defined as follows.
Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

iv

BSC6910 GSM
Commissioning Guide

About This Document

Convention

Description

Boldface

The keywords of a command line are in boldface.

Italic

Command arguments are in italics.

[]

Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... }

Optional items are grouped in braces and separated by


vertical bars. One item is selected.

[ x | y | ... ]

Optional items are grouped in brackets and separated by


vertical bars. One item is selected or no item is selected.

{ x | y | ... }*

Optional items are grouped in braces and separated by


vertical bars. A minimum of one item or a maximum of all
items can be selected.

[ x | y | ... ]*

Optional items are grouped in brackets and separated by


vertical bars. Several items or no item can be selected.

GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention

Description

Boldface

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


are in boldface. For example, click OK.

>

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


signs. For example, choose File > Create > Folder.

Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format

Description

Key

Press the key. For example, press Enter and press Tab.

Key 1+Key 2

Press the keys concurrently. For example, pressing Ctrl+Alt


+A means the three keys should be pressed concurrently.

Key 1, Key 2

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


the two keys should be pressed in turn.

Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

BSC6910 GSM
Commissioning Guide

Issue 02 (2013-06-25)

About This Document

Action

Description

Click

Select and release the primary mouse button without moving


the pointer.

Double-click

Press the primary mouse button twice continuously and


quickly without moving the pointer.

Drag

Press and hold the primary mouse button and move the
pointer to a certain position.

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

vi

BSC6910 GSM
Commissioning Guide

Contents

Contents
About This Document.....................................................................................................................ii
1 Changes in the BSC6910 GSM Commissioning Guide.........................................................1
2 Commissioning Prerequisites.....................................................................................................3
3 Commissioning Process...............................................................................................................6
4 Checking Operating Status of Hardware..................................................................................8
5 Commissioning the OMU..........................................................................................................10
5.1 Commissioning the OMU Locally...............................................................................................................................11
5.2 Commissioning the OMU Using a USB Flash Drive...................................................................................................16

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


7 Updating the OMU Database....................................................................................................26
8 Activating and Verifying the License......................................................................................30
9 Loading BSC6910 Board Software and Data Files................................................................32
9.1 Generating Data Files for the Loading.........................................................................................................................33
9.2 Setting the Loading Mode............................................................................................................................................33
9.3 Resetting BSC6910 Boards..........................................................................................................................................33
9.4 Checking the Consistency of the Data and the Version...............................................................................................34

10 Connecting to the M2000..........................................................................................................36


11 Setting the Connection Mode Between the M2000 and BSC6910 to SSL.......................38
12 Verifying Interfaces..................................................................................................................40
12.1 Verifying Interfaces on the M2000............................................................................................................................41
12.1.1 Setting the NE Engineering Mode to TESTING.....................................................................................................41
12.1.2 Verifying Interfaces Automatically.........................................................................................................................42
12.1.3 Setting the NE Engineering Mode to NORMAL...................................................................................................44
12.2 Verifying Interfaces on the LMT................................................................................................................................45
12.2.1 Verifying Fiber Optic Cable Connections...............................................................................................................45
12.2.2 Verifying Internal Interfaces....................................................................................................................................47
12.2.3 Verifying the Abis Interface....................................................................................................................................48
12.2.4 Verifying the A Interface.........................................................................................................................................51
Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

vii

BSC6910 GSM
Commissioning Guide

Contents

12.2.5 Verifying the Gb Interface.......................................................................................................................................53


12.2.6 Verifying the Lb Interface.......................................................................................................................................54
12.2.7 Verifying the CB Interface......................................................................................................................................55
12.2.8 Verifying the Iur-g Interface....................................................................................................................................55

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


14 Verifying GSM Services..........................................................................................................58
15 Verifying Network Reliability................................................................................................60
16 Troubleshooting........................................................................................................................62
16.1 Checking Transmission Links....................................................................................................................................63
16.2 Unavailable E1/T1 Port..............................................................................................................................................65
16.3 Unavailable FE/GE Port.............................................................................................................................................65
16.4 IP Connection Setup Failure.......................................................................................................................................66
16.5 Data Loading Failures on the Board...........................................................................................................................67
16.6 Performing a Loopback Test on an Optical Port........................................................................................................69

17 Appendix.....................................................................................................................................71
17.1 Communication Ports on the BSC6910......................................................................................................................72
17.2 BSC6910 Commissioning Checklist..........................................................................................................................72

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

viii

BSC6910 GSM
Commissioning Guide

1 Changes in the BSC6910 GSM Commissioning Guide

Changes in the BSC6910 GSM


Commissioning Guide

This chapter describes the changes in the BSC6910 GSM Commissioning Guide.

02 (2013-06-25)
This is the second commercial release of V100R015C00.
Compared with issue 01 (2013-05-04), this issue does not include any new topics.
Compared with issue 01 (2013-05-04), this issue incorporates the following changes:
Content

Change Description

16.1 Checking Transmission


Links

l Added procedure of checking PPP/MLPPP


transmission link.
l Added procedure of checking TDM transmission.

Compared with issue 01 (2013-05-04), this issue does not exclude any topics.

01 (2013-05-04)
This is the first commercial release of V100R015C00.
Compared with issue Draft A (2013-02-27) of V100R015C00, this issue does not include any
new topics.
Compared with issue Draft A (2013-02-27) of V100R015C00, this issue incorporates the
following changes:

Issue 02 (2013-06-25)

Content

Change Description

8 Activating and Verifying the


License

Added procedure of verifying the license information.

12.2.4 Verifying the A Interface

Added procedure of transmission resource pool.

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

BSC6910 GSM
Commissioning Guide

1 Changes in the BSC6910 GSM Commissioning Guide

Compared with issue Draft A (2013-02-27) of V100R015C00, this issue does not exclude any
topics.

Draft A (2013-02-27)
This is the Draft A release of V100R015C00.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

BSC6910 GSM
Commissioning Guide

2 Commissioning Prerequisites

Commissioning Prerequisites

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

Requirements for Equipment Status


Before commissioning, ensure that the equipment meets the conditions listed in Table 2-1.
Table 2-1 Requirements for equipment status before commissioning
Item

Requirement

BSC6910 hardware

The hardware is installed and has passed the hardware


installation check and power-on check.

OMU

The OMU is configured before delivery. For details, see


Checklist for the OMU Software Factory Settings in the
BSC6910 GSM OMU Administration Guide.

LMT PC

The LMT PC meets the configuration requirements. For details,


see Configuration Requirements of the LMT PC in the BSC6910
GSM LMT User Guide.

Requirements for the Network to Be Commissioned


To ensure the smooth commissioning of the Abis, A, and Gb interfaces on the network, the
network equipment in the network to be commissioned must meet the following requirements:
l

At least one BTS is connected to the BSC6910. The BTS must have passed commissioning
and can provide basic functions.

At least one set of core network (CN) equipment is connected to the BSC6910. The CN
equipment must have passed commissioning and can provide basic functions.

Three single-mode MSs and one dual-mode MS for testing are functional and are registered
with the home location register (HLR).

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


Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

BSC6910 GSM
Commissioning Guide

2 Commissioning Prerequisites

Figure 2-1 Typical network to be commissioned

The figure shows only the connections. The quantity and type of cables are not specified.

Figure 2-1 illustrates an example. There are other commissioning scenarios, as listed in
Table 2-2.

Table 2-2 Other commissioning scenarios


Scenario

Description

In BM/TC combined
mode

The BM and TC are configured in the same subrack.

A over IP

The TCS is not configured in the BSC6910. The TC function is


performed by the media gateway (MGW).

BSC6910 interconnected
with the MGW/BTS

Two NEs in the same equipment room are connected directly.

Alarm box configured on


the BSC6910 side

The alarm box is connected to the BSC6910 LMT that serves as


the alarm management system.

Requirements for the Software and Data Files


l
Issue 02 (2013-06-25)

Software installation package


Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.

BSC6910 GSM
Commissioning Guide

2 Commissioning Prerequisites

The installation package of the OMU application that is compatible 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 from the Huawei
technical support engineer.

MML command script file


Before commissioning, complete the initial configuration according to the BSC6910
GSM Initial Configuration Guide to obtain the MML command script file. In addition,
check and ensure the correctness of the data configuration based on the MML command
script examples and the on-site negotiated data defined in the BSC6910 GSM Initial
Configuration Guide.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

BSC6910 GSM
Commissioning Guide

3 Commissioning Process

Commissioning Process

The BSC6910 commissioning can be performed remotely, locally, or remotely with local
assistance.
l

Local commissioning is performed by a field engineer (engineer responsible for onsite


commissioning in the BSC equipment room) who connects a PC to the BSC and performs
the commissioning on the LMT.

Remote commissioning is remotely performed by an engineer (technical engineer


responsible for the BSC) and multiple BSCs can be commissioned simultaneously in the
central equipment room.

Remote commissioning with local assistance is performed remotely by an engineer with


the assistance of a field engineer.

Figure 3-1 shows the commissioning process if all commissioning prerequisites are met.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

BSC6910 GSM
Commissioning Guide

3 Commissioning Process

Figure 3-1 Commissioning flowchart

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

BSC6910 GSM
Commissioning Guide

4 Checking Operating Status of Hardware

Checking Operating Status of Hardware


Before commissioning the equipment, ensure that the BSC6910 subrack is powered on and is
operating normally.

Prerequisites
The BSC6910 subrack has passed the power-on check.

Procedure
Step 1 Check whether the subrack is powered on.
If...

Then...

The subrack is not powered on

Go to Step 2.

The subrack is powered on

Go to Step 4.

Step 2 Set the power switches that control the subrack power supply on the power distribution frame
(PDF) to ON.
Step 3 Set the air switches that control the subrack power supply on the power entry module (PEM) to
ON.
Step 4 Check the power supply to the subrack components, as listed in Table 4-1. Ensure that the
hardware operates correctly.
Table 4-1 Checklist of the power supply to the cabinet components

Issue 02 (2013-06-25)

Component

Normal Power Supply Status

Board

The RUN indicator on the board panel is


neither steady on nor steady off.

Fan box

The RUN indicator on the fan box panel


blinks one second on and one second off in
green after the subrack is powered on.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.

BSC6910 GSM
Commissioning Guide

4 Checking Operating Status of Hardware

Component

Normal Power Supply Status

PEM

The STATUS indicator on the panel is green


and steady on.

NOTE

If power failure occurs, handle the problem by referring to step 5 in section Powering on the Subrack in the
BSC6910 GSM Site Maintenance Guide.

----End

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

BSC6910 GSM
Commissioning Guide

5 Commissioning the OMU

Commissioning the OMU

About This Chapter


Before using the OMU for the first time, commission the OMU onsite to check the installation
of OMU applications and the version of the OMU applications, and configure the IP address,
mask, and name of the OMU to ensure the normal communication between the BSC6910 and
the LMT or M2000.

Context
The OMU can be commissioned locally or through a USB flash drive. Select a commissioning
method based on the onsite scenario.
5.1 Commissioning the OMU Locally
The OMU is locally commissioned by a field engineer who connects a PC to the OMU. If the
BSC6910 is configured with active and standby OMUs, commission the active OMU and the
standby OMU based on the procedure given in this section.
5.2 Commissioning the OMU Using a USB Flash Drive
This section describes how to commission the OMU using a USB flash drive. You can locally
insert the prepared USB flash drive to the OMU at the site and then perform OMU commissioning
with cooperation of a remote engineer.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

10

BSC6910 GSM
Commissioning Guide

5 Commissioning the OMU

5.1 Commissioning the OMU Locally


The OMU is locally commissioned by a field engineer who connects a PC to the OMU. If the
BSC6910 is configured with active and standby OMUs, commission the active OMU and the
standby OMU based on the procedure given in this section.

Prerequisites
l

You have obtained the OMU application installation package consistent with the OMU
version used in the local office and the Records of OMU Software Installation
Information.

You have obtained the planned OMU IP addresses and the OMU name and recorded them
in Configuration Information for Commissioning the OMU Locally.

You have obtained the psftp software and the PuTTY software. For details, see psftp
Software and PuTTY Software in the BSC6910 GSMOMU Administration Guide.

Context
In new deployment scenarios, the active workspace of the OMU is version_a by default. In the
following descriptions, the active workspace of the OMU uses version_a.
For details about the definitions of OMU IP addresses mentioned in the following descriptions,
see section OMU IP Address Plan in BSC6910 GSMOMU Administration Guide. You can run
the ./omutool dispipinfo command to query these IP addresses or check modification results.

Procedure
Step 1 Connect the PC to the OMU board.
1.

Connect the PC to the ETH2 commissioning port on the OMU board by using a network
cable.

2.

Set the IP addresses of the PC and ETH2 port to be on the same network segment.
The initial IP address of the ETH2 port is 192.168.6.50 (active OMU) or 192.168.6.60
(standby OMU), and the subnet mask is 255.255.255.0.

Step 2 Set the link mode of the external OMU Ethernet adapters.
1.

Log in to the OMU by referring to Logging In to the OMU in the BSC6910 GSMOMU
Administration Guide.

2.

Check whether the link mode of the external OMU Ethernet adapters is consistent with that
of LAN switches.
For details about how to query the link mode of the external OMU Ethernet adapters, see
Follow-up Procedure of Setting the Link Mode for External OMU Ethernet Adapters in the
BSC6910 GSMOMU Administration Guide.

Issue 02 (2013-06-25)

If...

Then...

The link mode of the external OMU


Ethernet adapters is consistent with that of
LAN switches

Go to Step 3.

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

11

BSC6910 GSM
Commissioning Guide

5 Commissioning the OMU

If...

Then...

The link mode of the external OMU


Ethernet adapters is inconsistent with that
of LAN switches

Set the link mode of the external OMU


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

Step 3 Install the OMU applications.


1.

Run the /etc/rc.d/omud status command to check the running status of the OMU process.
If...

Then...

The information displayed is running

a. Run the /etc/rc.d/omud stop command


to stop the omud process.
b. Go to Step 3.2.

The information displayed is unused

Go to Step 3.2.

The information displayed is No such file


or directory

a. Install the OMU applications in the


active workspace by referring to
operations in Procedure of Installing
the OMU Applications in the Active
Workspace in the BSC6910 GSMOMU
Administration Guide.
b. Go to Step 6.
c. Go to Step 7. The task is completed.

2.

Issue 02 (2013-06-25)

Run the cd /mbsc/upgrade command to switch to the OMU installation directory, and then
run the ls command to query the current versions of the OMU applications.
If...

Then...

The versions of the OMU applications are


the same as those required by the operator

Go to Step 4.

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

12

BSC6910 GSM
Commissioning Guide

5 Commissioning the OMU

If...

Then...

The versions of the OMU applications are


different from those required by the
operator

a. Uninstall the OMU applications by


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

Step 4 Modify the OMU IP addresses.


1.

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


omutool program is located.
NOTE

You can run the ./omutool -h command to view the help information of the omutool.

2.

Change the fixed external IP address and subnet mask according to the plan of the operator.
Run the ./omutool extercard The external fixed IP address The subnet mask The gateway
IP address (Optional) command to change the fix external IP address and the subnet mask.
For example, you can type the following command and then press Enter.
./omutool extercard 10.161.10.100 255.255.255.0
NOTE

l The following two methods show how to change the fixed external IP address if changing the
gateway IP address is required at the same time.
l Method 1: Type ./omutool extercard The external fixed IP address The subnet mask (The
gateway IP address) and then press Enter to change the fixed external IP address and gateway
IP address at the same time. The following is an example:
./omutool extercard 10.161.10.100 255.255.255.0 10.161.10.1

l Method 2: Type ./omutool gateway The gateway IP address and then press Enter to change
the gateway IP address separately. The following is an example:
./omutool gateway 10.161.10.1

l After the fixed external IP address is changed, the OMU can be connected to the operation and
maintenance (OM) network of the operator by using the ETH0 or ETH1 port. In this case, the
commissioning task can continue remotely.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

13

BSC6910 GSM
Commissioning Guide

3.

5 Commissioning the OMU

Change the virtual external IP address and the subnet mask of the active and standby OMUs
according to the plan. Ensure that the virtual external IP address is on the same network
segment as the fixed external IP address.
Run the ./omutool extervip The external virtual IP address The subnet mask command to
change the virtual external IP address and the subnet mask. For example, you can type the
following command and then press Enter.
./omutool extervip 10.161.10.102 255.255.255.0
NOTE

When the fixed or virtual external IP address is being changed, a window is displayed to remind users
to check whether the virtual or fixed external IP address and the gateway IP address need to be
changed. In this way, users can make necessary changes to ensure that the three IP addresses are on
the same network segment.

4.

Issue 02 (2013-06-25)

Check whether the fixed internal IP address, virtual internal IP address, backup channel IP
address, and debugging IP address of active and standby OMUs are on the same network
segment as the operator's network.

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

14

BSC6910 GSM
Commissioning Guide

5 Commissioning the OMU

If...

Then...

All IP addresses are on the same


network segment as the network
of the operator

Change the IP address in conflict.


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

l Run the ./omutool innervip The internal virtual


IP address command to change the virtual internal
IP address and the subnet mask. For example, you
can type the following command and then press
Enter.
./omutool innervip 80.168.3.40

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

l Change the backup channel IP address and subnet


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

l Run the ./omutool debugcard The debugging IP


address command to change the debugging IP
address and the subnet mask. For example, you
can type the following command and then press
Enter.
./omutool debugcard 192.168.6.60

The preceding IP addresses are


not on the same network
segment as the network of the
operator

Change the backup channel IP address of the standby


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

Step 5 Change the OMU name.


1.

Run the ./omutool hostname OMU name command to change the name of the OMU.
For example, you can type ./omutool hostname omu_123 and then press Enter.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

15

BSC6910 GSM
Commissioning Guide

5 Commissioning the OMU


NOTE

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

Step 6 Set the working mode of the OMU.


1.

Set the OMU backup attribute.


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

2.

Set the product mode.


a.

Run the /etc/rc.d/omud start command to start the OMU applications.

b.

Run the MML command SET OFFICENAME to set the product mode.

Step 7 Check the OMU running status.


1.

Run the ps -afx command to check the running status of the OMU.
The OMU is operating properly if all OMU processes exist in the OMU active workspace
directory /mbsc/bam/version_a/bin/bam/monitor.
OMU State

OMU Processes that Must Exist

Active OMU

host_gate, ems_gate, authority,


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

Standby OMU

software, ftp_server, sntp,


omu_manager, and debug_log

NOTE

If some of the processes do not exist, run the /etc/rc.d/omud restart command to restart the OMU
server, and then check again whether the processes exist. If some of them still do not exist, uninstall
the OMU applications and then reinstall the OMU applications in the active workspace by referring
to operations in Procedure of Uninstalling the OMU Applications and Installing the OMU
Applications in the Active Workspace in the BSC6910 GSMOMU Administration Guide.

2.

Run the exit command to stop the PuTTY and then remove the cable to the OMU.

----End

5.2 Commissioning the OMU Using a USB Flash Drive


This section describes how to commission the OMU using a USB flash drive. You can locally
insert the prepared USB flash drive to the OMU at the site and then perform OMU commissioning
with cooperation of a remote engineer.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

16

BSC6910 GSM
Commissioning Guide

5 Commissioning the OMU

Prerequisites
l

The preparations for installing software on site are completed. For details, see Onsite
Software Installation Preparations in the BSC6910 GSM OMU Administration Guide.

You have obtained the planned OMU IP addresses and the OMU name, and have recorded
them in Configuration Information for Preparing the USB Flash Drive.

The capacity of the USB flash drive is at least 2 GB. If the BSC6910 is configured with
active and standby OMUs, two USB flash drives are required.

A USB port is available on the PC, and the USB port is not restricted. For example, there
is no CPM restriction.

Using a USB flash drive to commission an OMU involves two steps: preparing the USB
flash drive and commissioning the OMU after inserting the USB flash drive into the OMU.

The prepared USB flash drive applies only to the DOPRA Linux operating system.

This section takes the commissioning OMU in active/standby mode as an example.


Differences between operations for the OMU in independent mode and that in active/
standby mode are specified.

Check whether the USB flash drive is usable by referring to the DOPRA Linux USB Flash
Drive Certificate Guide under the Dopra_Linux_U tool (a tool used for preparing the USB
flash drive) directory. If the USB flash drive cannot be used, replace it with another one.
The Netac U208 (2 GB), Kingston and Sandisk USB storage devices are recommended.

Context

CAUTION
Back up the OMU data before you install the OMU operating system and OMU applications.
The OMU hard disk will be formatted during the installation of the OMU operating system and
OMU applications using the USB flash drive and all data will be deleted.

Procedure
Step 1 Prepare a USB flash drive.
1.

Insert a USB flash drive into the USB port on a portable computer.

2.

Double-click U_creator_chs.exe to open the Dopra_Linux_U tool, as shown in Figure


5-1.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

17

BSC6910 GSM
Commissioning Guide

5 Commissioning the OMU

Figure 5-1 Dopra_Linux_U tool window

3.

Issue 02 (2013-06-25)

Select NE List in the left panel of the window shown in Figure 5-1 and right-click the list
to choose Add NE. A dialog box is displayed, as shown in Figure 5-2.

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

18

BSC6910 GSM
Commissioning Guide

5 Commissioning the OMU

Figure 5-2 Add NE dialog box

4.

Enter the NE Name, set Operate type to Install, select Install OMU?, enter the external
virtual IP address of the NE to be added and then click OK. An NE is added.
NOTE

l The NE name is used to identify different NEs and only can include letter, numerals, "-", and "_".
l After an NE is added, the NE name and the external virtual IP address can be changed only after you
delete the NE and then add the NE.
l If you want to prepare multiple USB flash drives, it is recommended that you prepare the USB flash
drives one by one and make a mark on each USB flash drive to specify which NE this USB flash drive
is to be used for.

5.

Issue 02 (2013-06-25)

Double-click the newly added NE on the left pane. After all the information is automatically
obtained, check whether the information is correct and enter the information that needs to
be typed, as shown in Figure 5-3.

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

19

BSC6910 GSM
Commissioning Guide

5 Commissioning the OMU

Figure 5-3 Configuring information

The description of the parameter is as the following:


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

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

20

BSC6910 GSM
Commissioning Guide

5 Commissioning the OMU

Table 5-1 Mapping between the queried link mode of OMU external Ethernet adapters and
the selected external network netcard mode
Queried Link Mode of OMU External
Ethernet Adapters

Selected External Network Netcard


Mode

l Auto-negotiation is on

Auto

l Auto-negotiation is off

10Mb Full

l Speed is 10 Mbit/s
l Duplex is Full
l Auto-negotiation is off

10Mb Half

l Speed is 10 Mbit/s
l Duplex is Half
l Auto-negotiation is off

100Mb Full

l Speed is 100 Mbit/s


l Duplex is Full
l Auto-negotiation is off

100Mb Half

l Speed is 100 Mbit/s


l Duplex is Half
l Auto-negotiation is off

1000Mb Full

l Speed is 1000 Mbit/s


l Duplex is Full
l Auto-negotiation is off

1000Mb Half

l Speed is 1000 Mbit/s


l Duplex is Half
6.

Check that all information is correct. Click OK. Check the local directory of the USB flash
drive in the displayed dialog box, and then start the process for preparing the USB flash
drive for the active OMU.

7.

After the USB flash drive for the active OMU is prepared, check the prompted information,
and then insert the USB flash drive for the standby OMU to prepare the USB flash drive
for the standby OMU. After the message Succeed to create USB flash drive of OMU
installation displays, click Finish. The USB flash drives are prepared.
NOTE

l After the USB flash drive is prepared, remove it from the PC in safe mode to avoid data loss or data
corruption.
l If only one OMU is configured, the USB flash drive for the standby OMU is not required.

Step 2 Commissioning the OMU after inserting the USB flash drive to the OMU
1.

Insert the USB flash drive into any USB ports on the OMU board panel.

2.

Remove and then install the OMU board to reset it. For details, see sections Removing a
Board and Installing a board in the BSC6910 GSM Site Maintenance Guide.

3.

Observe the status of the indicator on the OMU panel. Determine whether the installation
is complete by referring to the following table.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

21

BSC6910 GSM
Commissioning Guide

5 Commissioning the OMU


NOTE

If the status of the indicators differs from this, the OMU cannot identify the USB flash device. When this
occurs, prepare another USB flash device. Alternatively, copy the data in the original USB flash device
to a new USB flash device, and then reinstall the OMU operating system.
For information about how much time will be consumed during the OMU operating system installation,
see Table 1 in Dopra_Linux_USB Disk Tool.

Table 5-2 Status of indicators on the OMU board panel during the OMU operating system
and OMU applications installation
Board

Installation
Procedure

Successful
Installation

Failed Installation

EOMU
a

At the beginning:

l The RUN indicator


blinks.

l The RUN indicator


blinks.

l The ALM indicator


is steady on or off.

l The ALM indicator


blinks.

l The ACT indicator


is steady on or off.

l The ACT indicator


is off.

l The OFFLINE
indicator is off.

l The OFFLINE
indicator is off.

l The RUN indicator


blinks.
l The ALM indicator
blinks.
l The ACT indicator
blinks.
l The OFFLINE
indicator is off.
After a certain period:
l The RUN indicator
blinks.
l The ALM indicator
is off.
l The ACT indicator is
off.
l The OFFLINE
indicator blinks.

CAUTION
After the OMU operating system and the OMU applications are installed successfully,
remove the USB flash drive from the OMU panel. The OMU commissioning by using the
USB flash drive is complete.
----End

Follow-up Procedure
Check whether the configuration files prepared during the step Prepare the USB flash drive
are correct according to the Configuration Information for Preparing the USB flash drive
for Installation recorded during the preparations.
Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

22

BSC6910 GSM
Commissioning Guide

5 Commissioning the OMU

If the configuration files are not correct, prepare the USB flash drive again by referring to
Prepare the USB flash drive.

If the configuration files are correct, contact Huawei technical support by referring to
Contact Huawei Customer Service Center.
NOTE

After the OMU operating system and the OMU applications are installed successfully, remove the USB
flash drive from the OMU panel. The OMU commissioning by using the USB flash drive is complete.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

23

BSC6910 GSM
Commissioning Guide

6 Logging In to the BSC6910 Through the LMT

Logging In to the BSC6910 Through the LMT


This section describes how to log in to the BSC6910 through the LMT and enable communication
between the LMT and the BSC6910 to ensure smooth BSC6910 commissioning through the
LMT.

Prerequisites
l

The OMU commissioning has been completed.

The network connection between the LMT and the OMU has been established.
NOTE

In the case of the local OMU commissioning, a field engineer performs local commissioning tasks
and then Log in to the BSC6910 through the LMT to verify the connection between the OMU and
the external network. In this case, the field engineer needs to type the IP address for OMU
commissioning in the address bar of Internet Explorer (IE) to log in to the LMT for local
commissioning.

Context
JRE is a standard plug-in in Java operating environment. If JRE is not installed, a message is
displayed when you start the LMT. In this case, install JRE according to the prompt message on
the screen. If the JRE installed in the PC is not of the latest version, a message is displayed when
you start the LMT, prompting you to update the JRE. In this case, it is recommended that you
uninstall the old version and then install the latest version.

WARNING
When the LMT application is running, do not change the LMT PC system time. Otherwise,
severe errors may occur on the system. If you have to change the system time, stop all the LMT
applications first.

Procedure
Step 1 Check the configuration of the LMT PC and ensure that it meets the requirements.
1.

Issue 02 (2013-06-25)

Check the hardware configuration of the BSC6910 LMT PC to ensure that the requirements
described in Configuration Requirements of the LMT PC are met.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.

24

BSC6910 GSM
Commissioning Guide

2.

6 Logging In to the BSC6910 Through the LMT

Check the security settings of the Internet Explorer and ensure that the Java script is
supported.

Step 2 Start the IE, and then log in to the BSC6910 through the LMT.
1.

Start the IE and enter the external virtual IP address of the OMU of the BSC6910 on the
address bar. The log-in dialog box is displayed, as shown in Figure 6-1.

Figure 6-1 BSC6910 log-in dialog box

NOTE

To log in to the BSC6910 by using the Domain user account, establish the connection between the
BSC6910 and the M2000 server.

2.

Enter User Name, Password, and Verify Code, and click Login to log in to the LMT.

----End

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

25

BSC6910 GSM
Commissioning Guide

7 Updating the OMU Database

Updating the OMU Database

This chapter describes how to update configuration data in the OMU database by running MML
command scripts.

Prerequisites
l

You have completed the section You have 6 Logging In to the BSC6910 Through the
LMT..

The MML command data scripts applicable to the local office are verified and the contents
are precise and complete.

There are two ways to run MML command scripts: by running MML commands or using
the GUI. The MML command script can be executed by using the GUI only when a script
is smaller than 4 MB. It is recommended that you run the MML script by running MML
commands, because it is more efficient.

You can query the active workspace of the OMU through the MML command LST
OMUAREA. The following procedure assumes that the active workspace is version_a.

Run the MML command script by running MML commands

Context

Procedure
1.

Run the MML command SET CFGDATAINEFFECTIVE to set the system to work
in ineffective mode.

CAUTION
If the database has been updated, run the MML command SET
CFGDATAINEFFECTIVE to set the system to work in ineffective mode.

Issue 02 (2013-06-25)

2.

Run the MML command RST DATA. Click Yes in the displayed dialog box to
initialize the BSC6910 configuration data in the OMU database.

3.

Upload the MML command script to the /ftp folder in the OMU active workspace
directory. The following assumes that the MML script BATCHFILE.txt saved in
disk D is uploaded to the OMU active workspace /mbsc/bam/version_a/ftp to
introduce the two methods.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.

26

BSC6910 GSM
Commissioning Guide

7 Updating the OMU Database


NOTE

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

Through File Manager on the LMT


a.

Click File Manager on the toolbar of the LMT to start the file manager.

b.

In the displayed window, choose Root > bam > version_a > ftp on the left
and click Upload on the right. A dialog box is displayed. Select
BATCHFILE.txt saved in disk D, and then click Open to upload the file.

Through command lines


a.

On the local PC, choose Start > Run. Type cmd and click OK.

b.

Input d: and press Enter to switch to disk D.

c.

Input ftp IP address to connect to the OMU. Here, IP address is the IP address
of the OMU.

d.

Input the FTP user name and password. The connection between the OMU
and the local FTP is set up after the authentication succeeds.
NOTE

The FTP user name is always FtpUsr. The FTP password is set during the OMU
application installation. Both the FTP username and password are already recorded in the
Information Records of OMU Software Installation.

4.

e.

Input cd /mbsc/bam/version_a/ftp to switch to the OMU active workspace.

f.

Input put BATCHFILE.txt to upload the file.

g.

After the file is uploaded successfully, input quit to disconnect the FTP.

Run the MML command RUN BATCHFILE to run the batch command file. It is
recommended that you set Finish Type to ANY_ERR_RETURN(Stop at Error),
Result Recording Type to REC_ERR(Record errors), Source File Name to
BATCHFILE.txt, and Result File Name to RUN_BATCHFILE_RESULT.txt.
NOTE

l The result file RUN_BATCHFILE_RESULT.txt is saved in the /ftp folder in the OMU
active workspace installation directory, that is, /mbsc/bam/version_a/ftp.
l The execution of the script takes a certain period of time. For example, 1-1.5 hours will be
needed for executing a script with 100,000 commands.
l If the MML script fails to be executed, open the RUN_BATCHFILE_RESULT.txt file
to check the commands that fail to be executed. Then, extract the commands that fail to be
executed and the commands that have not been executed to generate a new MML script.
Correct the MML script based on the displayed messages, and then go toStep 4 to run the
new script.

Run the MML script by using the GUI


1.

Run the MML command SET CFGDATAINEFFECTIVE to set the system to work
in ineffective mode.

CAUTION
If the database has been updated, run the MML command SET
CFGDATAINEFFECTIVE to set the system to work in ineffective mode.
2.

Issue 02 (2013-06-25)

Run the MML command RST DATA. Click Yes in the displayed dialog box to
initialize theBSC6910 configuration data in the OMU database.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.

27

BSC6910 GSM
Commissioning Guide

7 Updating the OMU Database

3.

On the LMT, click the Batch tab. The Batch tab page is displayed, as shown in Figure
7-1.

Figure 7-1 Batch tab page

4.

Click Open....The Open dialog box is displayed. Select the prepared MML command
script, and then click Open. The commands in the script are displayed on the Batch
tab page.

5.

Click Set.... The Set dialog box is displayed. Set Sending Commands Interval(s) to
0, select Save Failed Commands and set the path for saving the failed commands,
and then click OK, as shown in Figure 7-2.
Figure 7-2 Setting the batch commands

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

28

BSC6910 GSM
Commissioning Guide

7 Updating the OMU Database

6.

On the Batch tab page, select All in the Execution Type area.

7.

Click Go. The system runs the MML commands one by one.
NOTE

l Click OK when the system displays that the current configuration is in ineffective mode
after you click Go. The execution of the script will take a long time in GUI mode. For
example, 2-3 hours will be needed for executing a 4-MB script.
l If an Error dialog box showing Execution failed. Continue? is displayed during the
execution of the MML command script, you can infer that the MML command script is
incorrect. In this case, select Yes to All to ignore the error prompt. After the MML script
file is executed, extract the commands that fail to be executed to generate a new MML
script, correct the commands based on the prompts, and then go to Step 4 to run the script
again.

8.

Click OK when a dialog box is displayed, indicating that the running of all the MML
commands is complete.

----End

Follow-up Procedure
After the OMU database is upgraded, perform the following to ensure the normal communication
between the OMU and BSC6910.
1.

Run the MML command LST SUBNET to query the Subnet No. of the BSC6910.

2.

Check whether the Subnet No. of the BSC6910 is consistent with the network segment of
the planned internal IP address of the OMU.
NOTE

The planned internal IP address of the OMU is recorded in Configuration Information for Verifying
OMU Locally.

l If they are consistent, end this task.


l If they are inconsistent, run the MML command SET SUBNET to change the Subnet
No. of the BSC6910 so that it is consistent with the network segment of the planned
internal IP address of the OMU.
3.

Run the MML command SET CFGDATAEFFECTIVE to set the system to work in
effective mode.

4.

Run the MML command RST BSC to reset the entire system. The new IP address of the
BSC6910 host takes effect.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

29

BSC6910 GSM
Commissioning Guide

8 Activating and Verifying the License

Activating and Verifying the License

This section describes how to activate the license and verify the license configuration
information to enable the service checking.

Prerequisites
l

You have 6 Logging In to the BSC6910 Through the LMT..

The FTP server is started. For details on how to start the FTP server, see the operations in
Startup in the BSC6910 GSM LMT User Guide for FTP Server. For the username and
password of the FTP server, see FTP Server in the BSC6910 GSM LMT User Guide. Note
that the user name or password may be modified.

The license is ready and the license check is passed.

Context
The active workspace of the OMU can be queried through the MML command LST
OMUAREA. The following operations assume that the active workspace is version_a.

Procedure
Step 1 Run the MML command DLD LICENSE to download the license to the OMU active workspace
directory /ftp/license, that is /mbsc/bam/version_a/ftp/license.
Step 2 Run the MML command LST LICENSE and then set File Name to the name of the license file
to be activated to query the detailed configuration information of the license file.
If...

Then...

The license is consistent with what you apply Go to Step 3.


for
The license is inconsistent with what you
apply for

Contact the Huawei Customer Service


Center by referring to Contact Huawei
Customer Service Center.

Step 3 Run the MML command CHK DATA2LIC, and then set File Name to the name of the license
file to be activated to verify the license information including the equipment serial number
(ESN), version, working mode, and configuration.
Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

30

BSC6910 GSM
Commissioning Guide

8 Activating and Verifying the License

If...

Then...

The license information is consistent with


the OMU information

Go to Step 4.

The license information is inconsistent with Modify the inconsistent data and repeat this
the OMU information
step.
Step 4 Run the MML command ACT LICENSE to activate the license file.
----End

Follow-up Procedure
If the license activation fails, you can infer that the configuration data of the license is
inconsistent with that in the OMU database. Check the configuration data of the license and the
configuration data in the OMU database.
l

If the configuration data such as the product name, ESN, and version number of the license
is incorrect, apply for a new license.

If the configuration data in the OMU database is incorrect, correct the configuration data,
and then reactivate the license.
NOTE

An invalid or expired license file can also lead to license activation failure. For details, see the help of the
MML command ACT LICENSE.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

31

BSC6910 GSM
Commissioning Guide

9 Loading BSC6910 Board Software and Data Files

Loading BSC6910 Board Software and Data


Files

About This Chapter


This chapter describes how to load the BSC6910 board software and data files.

Prerequisites
l

The OMU has been commissioned.

The OMU database has been updated.

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

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

32

BSC6910 GSM
Commissioning Guide

9 Loading BSC6910 Board Software and Data Files

9.1 Generating Data Files for the Loading


This section describes how to generate data files, which can be loaded, using the MML data
scripts.

Prerequisites
l

You have 6 Logging In to the BSC6910 Through the LMT.

Procedure
Step 1 Run the MML command SET CFGDATAEFFECTIVE and do not specify any parameter to
set the system to work in effective mode.
Step 2 Run the MML command FMT DATA and set Work Area Flag to Active(Format active
area) to format the configuration data in the OMU database. Do not specify the subrack number
when running the MML command.
----End

9.2 Setting the Loading Mode


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

Prerequisites
You have 6 Logging In to the BSC6910 Through the LMT.

Context
For details about the loading modes, see BSC6910 Loading Management.

Procedure
Step 1 Run the MML command SET LODCTRL to set the loading mode. In this command, set Board
Start Load Control to LFB(Load from OMU and write flash).
----End

9.3 Resetting BSC6910 Boards


This section describes how to load the BSC6910 board software and data files from the OMU
installation directory to the boards and make them take effect.

Prerequisites
l

The data file for the loading has been generated.

You have 6 Logging In to the BSC6910 Through the LMT.

All the subracks have been powered on.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

33

BSC6910 GSM
Commissioning Guide

9 Loading BSC6910 Board Software and Data Files

Context
The resetting time is less than or equals to 10 minutes.

Procedure
Step 1 Run the MML command RST BSC to reset all the BSC6910 service processing boards.
NOTE

You can observe the loading process on the Progress tab page on the LMT home page. If this tab page is hidden,
click Progress in the toolbar on the LMT home page.

Step 2 Click the Device Maintenance tab on the LMT home page. The Device Maintenance tab page
is displayed.
Step 3 Check whether all the boards on the device panel are in normal state.
If...

Then...

The device panel shows that all the boards End this task.
are in normal state
The device panel shows that some boards Check the faulty boards and clear the alarms
are not in normal state
according to operations in 16.5 Data Loading
Failures on the Board.
----End

9.4 Checking the Consistency of the Data and the Version


This section describes how to check whether the board configuration and the software version
of the BSC6910 are consistent with those on the OMU.

Prerequisites
l

All the subracks and boards are running normally.

You have 6 Logging In to the BSC6910 Through the LMT.

Procedure
Step 1 Run the MML command ACT CRC and do not specify a parameter and check whether the
BSC6910 board configuration is consistent with the data on the OMU.
Expected result: The All table data consistent. message is displayed.
Step 2 Run the MML command CMP BRDVER and do not specify a parameter to check whether the
version run by the BSC6910 is consistent with the version information on the OMU.
Expected result: The Compare consistent message is displayed.
NOTE

If the board configuration or software version is inconsistent with the information on the OMU, run the MML
command RST SUBRACK reset the subrack where the board with incorrect data or version is located.

----End
Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

34

BSC6910 GSM
Commissioning Guide

9 Loading BSC6910 Board Software and Data Files

Follow-up Procedure
After the consistency check, restore the loading method of the board: Run the MML command
SET LODCTRL to set Board Start Load Control to CL(Consult Load).

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

35

BSC6910 GSM
Commissioning Guide

10 Connecting to the M2000

10

Connecting to the M2000

This section describes how to connect the BSC6910 to the M2000 for centralized management.

Prerequisites
l

The operation and maintenance (O&M) network has passed commissioning. The M2000
is operating properly.

The version of the M2000 is compatible with that of the BSC6910.

The mediation version of the M2000 is compatible with the NE version.

If the BSC6910 and the M2000 are in the same network segment, you do not need to
configure an IP route to the BSC6910 to the M2000.

If the BSC6910 and the M2000 are not in the same network segment, you must configure
an IP route from the BSC6910 to the M2000.

Context

Procedure
Step 1 Connect the BSC6910 to the O&M network.
1.

Connect one end of a straight-through cable to the ETH0 or ETH1 port on the OMU board.

2.

Connect the other end of the straight-through cable to the peer network device, such as a
hub or a router, to access the O&M network.

Step 2 Configure an IP route from the BSC6910 to the M2000.


1.

Run the MML command LST OMUIPRT to check whether the IP route to the M2000 is
configured on the OMU.
l If the values of Destination Network Address, Destination Address Mask, and
Forward Route Address are consistent with the planned addresses, the BSC6910 has
an IP route to the M2000. Go to Step 2.3.
l If the Destination Network Address, Destination Address Mask, and Forward
Route Address are not consistent with the planned addresses, the BSC6910 does not
have a route to the M2000. Go to Step 2.2.

2.

Run the MML command ADD OMUIPRT to configure a route from the BSC6910 to the
M2000.

3.

Verify the configuration of the route from the BSC6910 to the router.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

36

BSC6910 GSM
Commissioning Guide

10 Connecting to the M2000

Log in to the OMU according to the instructions in the BSC6910 GSM OMU Administration
Guide for Logging In to the OMU, and then run the ping command to check whether the
network connectivity between the BSC6910 and the router is available. If the OMU can
receive an acknowledge packet from the router, go to Step 2.4. Otherwise, check whether
the OMU and the router are properly connected.
4.

Verify the configuration of the route from the BSC6910 to the M2000.
Log in to the OMU and run the ping command to check whether the network connectivity
between the BSC6910 and the M2000 is available. If the OMU can receive a response
packet from the M2000, go to Step 3. Otherwise, check whether the OMU and the M2000
are properly connected.

Step 3 Create the BSC6910 on the M2000. For details, see the information about how to create an NE
in the M000 documentation.

CAUTION
l If a firewall exists between the BSC6910 and M2000, enable the communication ports
connecting the BSC6910 and M2000 to ensure proper communication between the
BSC6910 and M2000.
l For details on the ports connecting the BSC6910 and M2000, see 17.1 Communication
Ports on the BSC6910.
l The MTU value configured for the transmission equipment between the BSC6910 and the
M2000 must be no less than that configured for the OMU board of the BSC6910. Otherwise,
the communication between the BSC6910 and the M2000 may be abnormal. The default
MTU value for the OMU board is 1500.
----End

Example
Table 10-1 describes how to configure a route between the BSC6910 and the M2000.
Table 10-1 Configuring a route from the BSC6910 to the M2000
Scenar
io

The IP address of the M2000 server is 10.11.100.23. The mask is 255.255.255.255.


The OMU is connected to the M2000 network segment through the router. The IP
address of the router is 172.121.139.10.

Opera
tion

1. Run the MML ADD OMUIPRT command.


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

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

37

BSC6910 GSM
Commissioning Guide

11

11 Setting the Connection Mode Between the M2000 and


BSC6910 to SSL

Setting the Connection Mode Between


the M2000 and BSC6910 to SSL

The connection mode between the M2000 and BSC6910 must be set to Secure Socket Layer
(SSL) on the M2000 to ensure operation and maintenance (O&M) safety.

Prerequisites
l

The BSC6910 and peer equipment are physically connected and both have passed the
hardware installation acceptance.

All the subracks of the BSC6910 are running normally.

You have 6 Logging In to the BSC6910 Through the LMT.

You have completed section 10 Connecting to the M2000.

You have applied for an SSL safety certificate from the Certificate Authority (CA).

Procedure
Step 1 Import and activate the certificate.
l Importing and activating the certificate on the M2000.
1.

On the M2000 client, choose Security Management > NE Security > Certificate
Authentication Management > Certificate Management(application style) or
Security > Certificate Authentication Management > Certificate Management
(traditional style).

2.

In the displayed Certificate Management window, click the CA Certificate tab and
click Add to add a root certificate.

3.

In the displayed Certificate Management window, click the Device Certificate tab
and click Add.

4.

In the displayed Device Certificate Batch Import window, choose the relevant NE on
the left. Click Import Certificate on the lower right and import the prepared certificate.
Select Activate the Certificate on the bottom and click OK to import and activate the
certificate.

l Importing and activating the certificate on the LMT

Issue 02 (2013-06-25)

1.

On FTP Server, upload the certificate into the directory where the OMU is installed.

2.

Run the MML command SET CERTFILE to set the SSL certificate file of an NE.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.

38

BSC6910 GSM
Commissioning Guide

11 Setting the Connection Mode Between the M2000 and


BSC6910 to SSL
NOTE

Private Key Password, Certificate Revocation List File Name, and Certificate Chain File
Name must be set if the three parameters exist.

3.

Run the MML command SET SSLAUTHMODE. In this step, set Authentication
Mode to NONE(Verify None) or PEER(Verify Peer Certificate) as required by the
site.
NOTE

If Authentication Mode is set to NONE(Verify None), that is, if SSL Authentication is set to
Cryptonym Authentication, the BSC6910 and the M2000 do not authenticate each other's certificate.
If Authentication Mode is set to PPEER(Verify Peer Certificate), that is, if SSL Authentication
is set to NE Authentication OMC, or Bidirectional Authentication, the BSC6910 authenticates the
certificate of the M2000; if SSL Authentication is set to OMC Authentication NE, the BSC6910
does not authenticate the peer certificate.

Step 2 Set the connection method between the M2000 and BSC6910 to SSL.
1.

On the M2000 client, choose Security Management > NE Security > Certificate
Authentication Management > SSL Connection Management(application style) or
Security > Certificate Authentication Management > SSL Connection Management
(traditional style).

2.

In the displayed SSL-Connection Policy Management window, set Connection Type of


the relevant NE to SSL Connection. Set SSL Authentication to Cryptonym
Authentication, OMC Authentication NE, NE Authentication OMC, or Bidirectional
Authentication as required on site.
NOTE

When the SSL configuration is modified on the M2000, the M2000 sends a command to the BSC6910 to
synchronize its SSL configuration.

----End

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

39

BSC6910 GSM
Commissioning Guide

12 Verifying Interfaces

12

Verifying Interfaces

About This Chapter


This section describes how to verify interfaces on the BSC6910 side. Select a verification method
based on the onsite situation.
12.1 Verifying Interfaces on the M2000
This section describes how to verify interfaces by setting engineering modes and performing an
NE health check on the M2000.
12.2 Verifying Interfaces on the LMT
This chapter describes how to verify interfaces on the BSC6910 by using MML commands on
the LMT or the GUI. The items to be verified include fiber optic cable connections, internal
interfaces, Abis, A, Gb, and Lb interfaces. The Lb interface verification is mandatory when an
external serving mobile location center (SMLC) is configured.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

40

BSC6910 GSM
Commissioning Guide

12 Verifying Interfaces

12.1 Verifying Interfaces on the M2000


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

12.1.1 Setting the NE Engineering Mode to TESTING


During commissioning, the NE reports many alarms that require no care. You can mask these
alarms by setting the NE mode to TESTING by using GUL-based functions on the M2000 client
or by running MML commands on the M2000 or LMT.

Prerequisites
l

The BSC6910 and peer equipment are physically connected and both have passed the
hardware installation acceptance.

All the subracks of the BSC6910 are running normally.

You have completed M2000.

You have 6 Logging In to the BSC6910 Through the LMT.

An NE can work in the following engineering modes: NORMAL, INSTALL,


EXPAND, UPGRADE, and TESTING. The NE mode of the BSC6910 must be set to
TESTING in commissioning scenarios.

Context

NOTE

For details about engineering modes, see section Introduction to the Maintenance Mode
Management Feature in the M2000 Product Documentation.

The NE engineering mode is valid only during the time specified by Start Time and End
Time. Before Start Time and after End Time, the NE mode changes to NORMAL. Alarms
are reported when the NE works in NORMAL mode.

When the NE engineering mode changes to the NORMAL mode, the alarms that are not
cleared in TESTING mode are reported as common alarms to the M2000.

Setting the NE engineering mode by using the GUI on the M2000 client

Procedure
1.

On the M2000 client, choose System Settings > Task Schedule > Maintenance
Mode(Application Styles) or Maintenance > Maintenance Mode(Traditional
Styles).

2.

In the displayed window, click

3.

In the Set NE Mode dialog box, select the BSC6910 NE that needs to be set, and then
set NE Mode to TESTING. A window is displayed, as shown in Figure 12-1.

NOTE

Select the performance methods Instant or Time based on requirements. If Time is selected,
set the Start Time and End Time of testing for the NE.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

41

BSC6910 GSM
Commissioning Guide

12 Verifying Interfaces

Figure 12-1 Setting the NE engineering mode to TESTING

Setting the NE engineering mode by running MLL commands on the M2000 or LMT
1.

On the M2000 client or LMT, run the MML command SET MNTMODE. In this
command, set Maintenance Mode to TESTING(TESTING), Start Time and End
Time to values based on onsite requirements.

----End

Follow-up Procedure
After the preceding operations, all the alarms and events reported during Start Time and End
Time will not be shown in the M2000 Alarm and Event Log for the NE by default. You can
check the alarms and events reported when the NE works in TESTING mode by setting the
filtering conditions. For details, see the M2000 Operator Guide.

12.1.2 Verifying Interfaces Automatically


This section describes how to use an NE health check on the M2000 to automatically verify the
BSC6910 interfaces.

Prerequisites
l

Issue 02 (2013-06-25)

The BSC6910 and peer equipment are physically connected and both have passed the
hardware installation acceptance.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.

42

BSC6910 GSM
Commissioning Guide

12 Verifying Interfaces

All the subracks of the BSC6910 are running normally.

You have completed section 10 Connecting to the M2000.

Context
The Lb interface and the internal interface must be verified through MML commands or the GUI
on the LMT. For details, see 12.2.6 Verifying the Lb Interface and 12.2.2 Verifying Internal
Interfaces.

Procedure
Step 1 Set the scenario for NE health check.
1.

On the M2000 client, choose Trace and Maintenance > Monitor > NE Health Check
(Application Styles) or Maintenance > Network Health Check > NE Health Check
(Traditional Styles).

2.

Click

3.

Click New in the displayed dialog box.

4.

Enter the scenario name in the Scenario Name text box on the right of the dialog box.

on the displayed tab page. The Scenario Management dialog box is displayed.

NOTE

The scenario name must be different from existing scenario names.

5.

Select an NE type for health check in NE Types, that is BSC6910 GSM.

6.

Select the check items for health check (deselect those not for health check) in the Interface
Check under Check Items.

7.

Click OK A dialog box is displayed, prompting that the NE health check scenario is set up
successfully. Click OK to set up the NE health check scenario.

Step 2 Create an NE health check task.


. The Create Task dialog box is displayed.

1.

On the NE Health Check tab page, click the

2.

Select an application scenario from the Scenario drop-down list. The application scenario
must be suitable for the newly created task. The application scenario and the specific time
(the time is accurate to the second) on which the task is created are automatically displayed
in the Task Name text box.

3.

Select the NE for health check in the Select NE. area.

4.

In the Time Setting area, Click Finish to select the instant execution mode.
NOTE

The executed health check tasks are listed under the Finished Tasks node in the navigation tree on the left
side.

Step 3 Check the NE health check result.


1.

Expand the Finished Tasks node in the navigation tree on the left side. Right-click a
finished task and choose View Report from the shortcut menu.

2.

In the Health Check Report dialog box, select a format to view the NE health check report.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

43

BSC6910 GSM
Commissioning Guide

12 Verifying Interfaces
NOTE

The health check report is compressed to a .zip file. To view the report, double-click the .zip file,
and then double-click the report file index.html in the .zip file browser.
If some items in the health check report are in red, the corresponding interface is faulty. Rectify the
fault according to the health check report.

----End

12.1.3 Setting the NE Engineering Mode to NORMAL


When the end time specified by End Time is reached, the NE finishes its engineering mode
automatically. If the engineering process finishes in advance, you can set the NE engineering
mode to NORMAL by using GUL functions on the M2000 client or by running MML commands
on the M2000 or LMT. Alarms are reported when the NE works in NORMAL mode.

Prerequisites
l

You have completed section 10 Connecting to the M2000.

Before interface verification, complete section 12.1.1 Setting the NE Engineering Mode
to TESTING.

BSC6910 has passed commissioning.

Setting the NE engineering mode by using the GUI on the M2000 client

Procedure
1.

On the M2000 client, choose Configuration > Settings > Maintenance Mode
(application style) or Maintenance > Maintenance Mode(traditional style).

2.

In the displayed window, click

3.

In the Set NE Mode dialog box, select the BSC6910 NE to be set, and set NE
Mode to NORMAL, the window shown in Figure 12-2 is displayed.

NOTE

If the NE engineering mode is set to NORMAL, Instant is selected by default.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

44

BSC6910 GSM
Commissioning Guide

12 Verifying Interfaces

Figure 12-2 Setting the NE engineering mode to NORMAL

Setting the NE engineering mode by running MLL commands on the M2000 or LMT
1.

On the M2000 or the LMT client, run the MML command SET MNTMODE, and
set Maintenance Mode to NORMAL(NORMAL).

----End

12.2 Verifying Interfaces on the LMT


This chapter describes how to verify interfaces on the BSC6910 by using MML commands on
the LMT or the GUI. The items to be verified include fiber optic cable connections, internal
interfaces, Abis, A, Gb, and Lb interfaces. The Lb interface verification is mandatory when an
external serving mobile location center (SMLC) is configured.

Context
During interface verification, you can run an LST command to view the configuration
information. For example, before running the MML command DSP ADJNODE, you can run
the MML command LST ADJNODE to check the value of the Adjacent Node ID parameter.

12.2.1 Verifying Fiber Optic Cable Connections


This section describes how to verify whether fiber optic cables are connected correctly. This
section applies to the fiber optic cable connections for the working channel and protection
Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

45

BSC6910 GSM
Commissioning Guide

12 Verifying Interfaces

channel between local and peer ends when ports on the local interface boards are working in
multiplex section protection (MSP) mode.

Prerequisites
l

The optical interface board configured on the BSC6910 is operating properly and has been
connected to the transmission equipment with fiber optic cables.

You have 6 Logging In to the BSC6910 Through the LMT.

Context
Working channel: board in an even-numbered slot in active/standby mode
Protection channel: board in an odd-numbered slot in active/standby mode
The following operation assumes that the board in an even-numbered slot is the active board
and that the board in an odd-numbered slot is the standby board.

Procedure
Step 1 Run the MML command CHK OPTCRS to check the status of fiber optic cable connections
for an optical interface board.
Expected result: The command output shows that the value for Check Result is Correct
connection.
l If the command output shows that the value of Check Result is The check fails, check fiber
optic cable connections or the peer optical port.
l If the command output shows that the value of Check Result is Incorrect connections,
exchange the RX branches of the optic fiber cables for the local working channel and
protection channel and then exchange the TX branches in the same way.
l If the command output shows that the value of Check Result is Incorrect TX connection,
correct RX connection, exchange the TX branches of the optic fiber cables for the local
working channel and protection channel.
l If the command output shows that the value of Check Result is Correct TX connection,
incorrect RX connection, exchange the RX branches of the optic fiber cables for the local
working channel and protection channel.
l If the command output shows that the value of Check Result is not of any of the preceding
ones, the conditions for checking fiber optic cable connections are not met. In this case,
troubleshoot according to the command output and run this command again.
Figure 12-3 shows the fiber optic cable connections.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

46

BSC6910 GSM
Commissioning Guide

12 Verifying Interfaces

Figure 12-3 Fiber optic cable connections

----End

12.2.2 Verifying Internal Interfaces


This section describes how to verify whether the internal interfaces are working properly by
checking the status of links to the ports on the SCUb boards.

Prerequisites
l

BSC6910Inter-SCUb network cables have been installed.

All the subracks of the BSC6910 are running normally.

You have 6 Logging In to the BSC6910 Through the LMT.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

47

BSC6910 GSM
Commissioning Guide

12 Verifying Interfaces

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

12.2.3 Verifying the Abis Interface


This section describes how to verify the control plane and user plane of the Abis interface. The
Abis interface verification varies with the transmission mode used over the Abis interface.

Prerequisites
l

The BSC6910 and the base stations are physically connected, and the hardware installation
acceptance is passed.

The base stations used to verify the Abis interface are commissioned and the cell
configuration is complete.

All the subracks of the BSC6910 are running normally.

You have 6 Logging In to the BSC6910 Through the LMT.

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 using MML
commands. You can choose either way according to your convenience.
This version does not support the Abis over HDLC mode.

Procedure
l

Issue 02 (2013-06-25)

Verifying the Abis interface (Abis over TDM) through GUI


1.

On the LMT, click the Device Maintenance tab to enter the Device Maintenance tab
page.

2.

Query the status of the Link Access Protocol on the D channel (LAPD) link on the
Abis interface.
a.

On the BSC Maintenance tab page, choose BSC Maintenance > Maintain
Transmission and Signaling, and then double-click Maintain LAPD link. The
Maintain LAPD link tab page is displayed.

b.

In the LAPD Link Type area, choose OML and RSL (deselect EML and
ESL). In the BTS Type area, click the BTS type to be queried (all candidate
BTSs will be listed in the Candidate BTS area). Select the BTS to be queried in
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.

48

BSC6910 GSM
Commissioning Guide

12 Verifying Interfaces

the Candidate BTS area and click the


and then click Query.

to add it to the Selected BTS area,

Expected result: In the Query Result area, the value of State is Normal.
If the status of LAPD links on the Abis interface is abnormal, check the
transmission link by referring to 16.1 Checking Transmission Links.
c.
3.

Click the in the Maintain LAPD link tab to close the Maintain LAPD
link tab page.

Query the status of the timeslots on the Abis interface.


a.

On the BSC Maintenance tab page, choose BSC Maintenance > Maintain
User Resources, and then double-click Query Abis Interface Timeslot
Status. The Query Abis Interface Timeslot Status dialog box is displayed.

b.

Set the parameters in the Location area, and then click Query.
Expected result: In the Query Result area, the State of many timeslots is
Normal, 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 16.1 Checking Transmission Links.

c.

4.

Click Cancel or the icon on the upper-right of the Query Abis Interface
Timeslot Status dialog box to close the Query Abis Interface Timeslot
Status dialog box.

Query the status of cells and channels.


a.

On the BTS Maintenance tab page, choose BTS Maintenance, and then doubleclick Query BTS Running Status. The Query BTS Running Status tab page
is displayed.

b.

In the Select Status area, select Site in the Object Type drop-down list. In the
BTS Type area, click the BTS type to be queried (all candidate BTSs will be
listed in the Candidate BTS area). Select the BTS to be queried in the Candidate
to add it to the Selected BTS area, and then click
BTS area and click the
Start. The Query Complete dialog box is displayed. Click OK.
Expected result: In the Operation Result area, the value of Cell Initialized is
Yes and the value of Channel Fault is No.
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.

c.
l

Click the in the Query BTS Running Status tab to close the Query BTS
Running Status tab page.

Verifying the Abis interface (Abis over TDM) using MML commands
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 16.1 Checking Transmission Links.

2.

Issue 02 (2013-06-25)

Run the MML command DSP ABISTS to query the timeslot status of the Abis
interface.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.

49

BSC6910 GSM
Commissioning Guide

12 Verifying Interfaces

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 16.1 Checking Transmission Links.
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.
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.

Verifying the Abis interface (Abis over IP, Transmission Resource Pool,GBTS)
1.

Run the MML command DSP LAPDLNK to check whether the 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 16.1 Checking Transmission Links.

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.

3.

Run the MML command DSP ADJNODEDIP to check whether the queried IP
address is the IP address of the Abis interface user plane.
Expected result: The queried IP address is the IP address of the Abis interface user
plane.
If the queried IP address is not the IP address of the Abis interface use plane, the MS
has not initiated a call. When this occurs, the verification on the A interface in IP pool
networking is complete. Perform next step to verify the status of the Abis interface
user plane after the MS initiates a call.

4.

Run the MML command DSP ADJNODEPING to query the Ping detection status
of the Abis interface user plane.
Expected result: The value of Detection Status is Available.
If the value of Detection Status is Unavailable, see 16.4 IP Connection Setup
Failure for troubleshooting.

5.

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

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

50

BSC6910 GSM
Commissioning Guide

12 Verifying Interfaces

Verifying the Abis interface (Abis over IP, Transmission Resource Pool,eGBTS)
1.

Run the MML command DSP SCTPLNK to query the status of an SCTP link.
Expected result: The value of Operation state is Normal.
If the value of Operation state is Unavailable, see 16.1 Checking Transmission
Links for troubleshooting
NOTE

Run the MML command DSP SCTPLNK to query the status of the SCTP link for two or three
times. If the value of Operation state remains Normal and State Changed Time remains
unchanged, the SCTP link operates properly.

2.

Run the MML command DSP ADJNODEDIP to check whether the queried IP
address is the IP address of the Abis interface user plane.
Expected result: The queried IP address is the IP address of the Abis interface user
plane.
If the queried IP address is not the IP address of the Abis interface use plane, the MS
has not initiated a call. When this occurs, the verification on the A interface in IP pool
networking is complete. Perform next step to verify the status of the Abis interface
user plane after the MS initiates a call.

3.

Run the MML command DSP ADJNODEPING to query the Ping detection status
of the Abis interface user plane.
Expected result: The value of Detection Status is Normal.
If the value of Detection Status is Unavailable, see 16.4 IP Connection Setup
Failure for troubleshooting.

4.

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.

5.

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

----End

12.2.4 Verifying the A Interface


This section describes how to verify the control plane and user plane of the A interface.

Prerequisites
l

The BSC6910 and the MSC are physically connected.

The MSC used to verify the A interface are operating properly.

All the subracks of the BSC6910 are running normally.

You have 6 Logging In to the BSC6910 Through the LMT.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

51

BSC6910 GSM
Commissioning Guide

12 Verifying Interfaces

Context
This version does not support the A over TDM mode.

Procedure
l

Verifying the A interface (A over IPTransmission Resource Pool)


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
referring to 16.1 Checking Transmission Links.
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 disconnections.

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-21551 M3UA Link Fault 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.
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 ADJNODEDIP to check whether the queried IP
address is the IP address of the Abis interface user plane.
Expected result: The queried IP address is the IP address of the Abis interface user
plane.
If the queried IP address is not the IP address of the Abis interface use plane, the MS
has not initiated a call. When this occurs, the verification on the A interface in IP pool
networking is complete. Perform next step to verify the status of the Abis interface
user plane after the MS initiates a call.

6.

Run the MML command DSP ADJNODEPING to query the Ping detection status
of the Abis interface user plane.
Expected result: The value of Detection Status is Available.
If the value of Detection Status is Unavailable, see 16.4 IP Connection Setup
Failure for troubleshooting.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

52

BSC6910 GSM
Commissioning Guide

12 Verifying Interfaces

7.

Run the MML command LST GCNNODE to query the configuration of a CN node.
Expected result: The configuration information about the CN node is displayed in the
command output.
If Corresponding results not found is displayed in the command output, run the
MML command ADD GCNNODE to configure a CN node.

----End

12.2.5 Verifying the Gb Interface


This section describes how to verify the Gb interface. .

Prerequisites
l

The BSC6910 and SGSN are physically connected and both have passed the hardware
installation acceptance.

The SGSN used to verify the Gb interface is operating correctly.

All the subracks of the BSC6910 are running normally.

You have 6 Logging In to the BSC6910 Through the LMT.

Verifying Gb interface links (Gb over IP)

Procedure
1.

Run the MML command DSP NSVL to query the status of the Network Service
Virtual Link (NSVL) to be verified.
Expected result: The command output shows that the value of State of the NSVL is
Normal.
If the value of State of the NSVL is Fault, see 16.1 Checking Transmission Links
for troubleshooting.
NOTE

You can run the MML command LST NSVLLOCAL or LST NSVLREMOTE to query the
configuration of the local or remote NSVL to be verified.

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 command output shows that 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 command output shows that the value of SIG BVC State is
Normal.
If the value of SIG BVC State is Fault, the SGSN is configured with an NSE that
has a different NSE ID.
NOTE

You can run the MML command LST NSE to query the configuration of the NSE to be verified.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

53

BSC6910 GSM
Commissioning Guide

12 Verifying Interfaces

4.

Run the MML command DSP PTPBVC to query the PTPBVC status of the NSE to
be verified.
Expected result: The command output shows that the value of Service State is
Normal.
If the value of Service State is not Normal, see handling suggestions in the following
"Follow-up Procedure" for troubleshooting.

----End

Follow-up Procedure
Handling Suggestions to Abnormal 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 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 abnormal
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
abnormal 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 Huawei Customer Service Center.

12.2.6 Verifying the Lb Interface


This section describes how to verify the Lb interface.

Prerequisites
l

The BSC and serving mobile location center (SMLC) are physically connected.

The SMLC used to verify the Iub interface is operating correctly.

All the subracks of the BSC6910 are running normally.

You have 6 Logging In to the BSC6910 Through the LMT.

Context
There is no dedicated interface board for the Lb interface. The data link layer of the Lb interface
can be carried on the Abis interface board and A interface board.
This version does not support Lb over TDM.

Procedure
l

Issue 02 (2013-06-25)

When the data link layer of the Lb interface is carried on the Abis interface board, verify
the Lb interface in the same way as that for the Abis interface. For details, see 12.2.3
Verifying the Abis Interface.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.

54

BSC6910 GSM
Commissioning Guide

12 Verifying Interfaces

When the data link layer of the Lb interface is carried on the A interface board, verify the
Lb interface in the same way as that for the A interface. For details, see 12.2.4 Verifying
the A Interface.

----End

12.2.7 Verifying the CB Interface


This section describes how to verify the CB interface. The CB interface applies only in FE/GE
transmission provided by the interface boardsGE transmission provided by the EXPUa/
EGPUa board.

Prerequisites
l

The BSC and CBC are physically connected.

The CBC used to verify the CB interface is operating properly.

All the subracks of the BSC6910 are running properly.

You have 6 Logging In to the BSC6910 Through the LMT.

Procedure
Step 1 Run the MML command PING IP. In this step, set Source IP address to the IP address of the
CB interface board on the local end and Destination IP address to the IP address of the CBC
server on the peer end.
Step 2 Check whether the BSC communicates with the CBC properly.
Expected result: The BSC communicates with the CBC properly.
If the IP address of the CBC server fails to be pinged through, check whether the firewall is
enabled on the CBC side. If the firewall is disabled on the CBC side, check whether the IP
address of the CBC on the BSC6910 have been configured correctly.
----End

12.2.8 Verifying the Iur-g Interface


This section describes how to verify the Iur-g interface when the BSC connects to the RNC or
when BSCs connect to each other. The method for verifying the Iur-g interface varies depending
on the Iur-g configuration.

Prerequisites
l

The BSC6910 and peer NE are physically connected and both have passed the hardware
installation acceptance.

The RNC used to verify the Iur-g interface is operating correctly.

All the subracks of the BSC6910 are running normally.

You have 6 Logging In to the BSC6910 Through the LMT.

Verifying the Iur-g interface (intra-RNC)

Procedure
1.
Issue 02 (2013-06-25)

Run the DSP BRD command to query the status of a board.


Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.

55

BSC6910 GSM
Commissioning Guide

12 Verifying Interfaces

Expected result: The command output shows that the value of CPU status is Active
normal.
If the value of CPU status is not Active normal, see ALM-20242 Board Subsystem
Unavailable for troubleshooting.
l

Verifying the Iur-g interface (inter-RNC)


1.

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

Run the MML command DSP SCTPLNK for two or three times. If the value of Operation state
is always Normal and the value of State Changed Time does not change, the SCTP link does not
disconnect intermittently.

2.

Run the MML command DSP M3LNK to query the status of an MTP3-User
Adaptation Layer (M3UA) link.
Expected result: The value of Operation state is Active.
If the value of Operation state is not Active, see ALM-21551 M3UA Link Fault for
troubleshooting.

3.

Run the MML command DSP SSN to query the status of a Signaling Connection
Control Part (SCCP) subsystem number (SSN).
Expected result: The command output shows that the value of SSN state is
Allowed.
If the value of SSN state is Prohibited, see ALM-21521 SCCP Subsystem Prohibited
for troubleshooting.

4.

Run the MML command DSP N7DPC to query the status of an SS7 destination
signaling point.
Expected result: The command output shows that the value of SCCP DSP state is
Accessible.
If the value of SCCP DSP state is not Accessible, see ALM-21521 SCCP Subsystem
Prohibited for troubleshooting.

----End

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

56

BSC6910 GSM
Commissioning Guide

13

13 Handling the Alarms Generated During the


Commissioning

Handling the Alarms Generated During


the Commissioning
This section describes how to handle the alarms generated during the commissioning to prevent
the alarms from affecting service verifications.

Prerequisites
l

The communication between the BSC6910 and OMU is normal.

You have 6 Logging In to the BSC6910 Through the LMT.

Procedure
Step 1 Click Alarm/Event on the LMT home page. The BSC6910 Alarm/Event tab page is displayed.
Step 2 Check whether any active alarm exists on the Normal Alarm tab page.
If...

Then...

No active alarm is listed

End this task.

One or more active alarms are listed

Go to Step 3.

Step 3 Double-click the active alarm to be handled on the Normal Alarm tab page. The Detailed
Information dialog box is displayed.
Step 4 Click Solution. The Online Help page is displayed.
Step 5 Follow the suggestions to handle the alarm.
Step 6 Repeat steps Step 3 through Step 5 to handle other alarms.
----End

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

57

BSC6910 GSM
Commissioning Guide

14 Verifying GSM Services

14

Verifying GSM Services

This section describes how to verify that the GSM basic services and the feature services that
are enabled are normal. GSM basic services are speech service and data service. Feature services
include intra-RAT handover, location service, and AMR service.

Prerequisites
l

Verification on the Abis, A, and Gb interface is successful. Verification on the Lb interface


is mandatory only when a serving mobile location center (SMLC) is configured on the
BSC6910. Verification on the Iur-g interface is mandatory only when two BSCs
(BSC6910) or between BSC and RNC connect to each other. Verification on the CB
interface is mandatory only when the cell broadcast services are supported in GSM cells.

The MSs used for test are functional and have registered with the HLR.

You have 6 Logging In to the BSC6910 Through the LMT.

Procedure
Step 1 Table 14-1 lists the operations for verifying basic GSM services with test MSs in BTS cells.
Table 14-1 Operations for verifying basic GSM services with test MSs in BTS cells

Issue 02 (2013-06-25)

Service Type

Operation

Expected Result

Speech service

Make 20 calls from a test MS to


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

The connection success rate is


higher than 90%. The voice is
clear without loud noise. No call
drop occurs and the system
resources are released normally
after the call is terminated.

Make 20 calls from a fixed-line


phone to a test MS and hold on
each call for 60 seconds.

The connection success rate is


higher than 90%. The voice is
clear without loud noise. No call
drop occurs and the system
resources are released normally
after the call is terminated.

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

58

BSC6910 GSM
Commissioning Guide

14 Verifying GSM Services

Service Type

Data Service

Operation

Expected Result

Make 20 calls from a test MS to


another test MS and hold on each
call for 60 seconds.

The connection success rate is


higher than 90%. The voice is
clear without loud noise. No call
drop occurs and the system
resources are released normally
after the call is terminated.

Send a fax from a test MS to a fax


machine. Send a fax from a fax
machine to a test MS.

Faxes are sent and received


correctly.

Test the General Packet Radio


Service (GPRS) or Enhanced
Data Rate for GSM Evolution
(EDGE) function on the test MS.

The test data rate is same to the


data rate tested in a lab.

NOTE

If the result of service verification cannot meet the expected results, start message tracing on the LMT over the
Um, Abis, A, Gb .

Step 2 Table 14-2 lists the procedure for verifying feature services by testing test MSs in the BTS cells.
Table 14-2 Operations for verifying feature services with test MSs in BTS cells
Service Type

Operation

Expected Result

Inter-RAT handover

Hand over a dual-mode test MS


from GSM to UMTS for 20
times. Hand over a dual-mode
test MS from UMTS to GSM for
20 times.

The connection success rate is


higher than 90%. The voice is
clear without loud noise.

Location service

Make a call from the test MS and


hold on the call. Then, locate the
test MS.

The location of the MS conforms


to the precision requirements.

Adaptive multirate
(AMR) service

Make 50 calls from a test MS to


a fixed-line phone and select
voice version to AMR.

The connection success rate is


higher than 90%. The voice is
clear without loud noise.

----End

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

59

BSC6910 GSM
Commissioning Guide

15 Verifying Network Reliability

15

Verifying Network Reliability

The network reliability can be verified after you switch over active and standby boards, check
generated alarms, and making dialing tests.

Prerequisites
l

The standby board to be switched over is operating correctly.

All the subracks of the BSC6910 are running normally.

You have 6 Logging In to the BSC6910 Through the LMT.

The alarms generated before the switchover have been cleared.

Procedure
Step 1 Run the MML command SWP BRD to switch over the BSC boards.
Step 2 Check and handle the alarms generated during the switchover. For details, see 13 Handling the
Alarms Generated During the Commissioning.
Step 3 Use an MS in a cell under the BTS to perform basic services and check whether services are
going on properly. For details, see Table 15-1.
Table 15-1 Operations for verifying basic GSM services with test MSs in BTS cells

Issue 02 (2013-06-25)

Service Type

Operation

Expected Result

Speech service

Make 20 calls from a test MS to


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

The connection success rate is


higher than 90%. The voice is
clear without loud noise. No call
drop occurs and the system
resources are released normally
after the call is terminated.

Make 20 calls from a fixed-line


phone to a test MS and hold on
each call for 60 seconds.

The connection success rate is


higher than 90%. The voice is
clear without loud noise. No call
drop occurs and the system
resources are released normally
after the call is terminated.

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

60

BSC6910 GSM
Commissioning Guide

15 Verifying Network Reliability

Service Type

Data Service

Operation

Expected Result

Make 20 calls from a test MS to


another test MS and hold on each
call for 60 seconds.

The connection success rate is


higher than 90%. The voice is
clear without loud noise. No call
drop occurs and the system
resources are released normally
after the call is terminated.

Send a fax from a test MS to a fax


machine. Send a fax from a fax
machine to a test MS.

Faxes are sent and received


correctly.

Test the General Packet Radio


Service (GPRS) or Enhanced
Data Rate for GSM Evolution
(EDGE) function on the test MS.

The test data rate is same to the


data rate tested in a lab.

----End

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

61

BSC6910 GSM
Commissioning Guide

16 Troubleshooting

16

Troubleshooting

About This Chapter


This chapter describes how to troubleshoot common problems during the commissioning.
16.1 Checking Transmission Links
This section describes how to verify that terrestrial transmission links of the BSC6910 are
functional. The verification covers E1/T1 ports, FE/GE ports, optical ports, and upper-layer
links.
16.2 Unavailable E1/T1 Port
This section describes how to troubleshoot an unavailable E1/T1 port.BSC6910 only support
the E1/T1 over SDH mode.
16.3 Unavailable FE/GE Port
This section describes how to troubleshoot an unavailable FE/GE port.
16.4 IP Connection Setup Failure
This section describes how to troubleshoot an IP connection setup failure.
16.5 Data Loading Failures on the Board
This section describes how to troubleshoot failures that occur during data loading to a
BSC6910 board.
16.6 Performing a Loopback Test on an Optical Port
This section describes how to perform the group loopback test to check whether an optical port
is functional.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

62

BSC6910 GSM
Commissioning Guide

16 Troubleshooting

16.1 Checking Transmission Links


This section describes how to verify that terrestrial transmission links of the BSC6910 are
functional. The verification covers E1/T1 ports, FE/GE ports, optical ports, and upper-layer
links.

Prerequisites
l

All the subracks of the BSC6910 are running normally.

You have 6 Logging In to the BSC6910 Through the LMT.

Check the status of physical transmission links based on the transmission scheme.

Procedure

Table 16-1 Methods for checking the status of transmission links based on the transmission
scheme
If the transmission scheme on the
interface is...

Then...

IP

Check the status of an FE/GE


port.

IP over Ethernet

If the port is operating properly, run


the MML commands PING IP and
TRC IPADDR to check the status of
the link connecting the local end to
the peer end.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

63

BSC6910 GSM
Commissioning Guide

16 Troubleshooting

If the transmission scheme on the


interface is...
PPP/MLPPP

Then...
1. Optional: If the channelized
STM-1 transmission is used on
the interface, check the status of
an optical port.
2. Check the status of an E1/T1
port.
3. Check the status of an upper-layer
link.
l For the PPP transmission
mode, run the MML command
DSP PPPLNK to check the
status of a PPP link.
l For the MLPPP transmission
mode, run the MML command
DSP MPGRP to check the
status of an MLPPP group.
NOTE
If the upper-layer link is not
functional, run the MML
command LST PPPLNK or
LST MPGRP to check whether
the data configuration on the
interface is correct.

TD
M
l

Channelized STM-1

check the status of an optical port.

Check the status of an E1/T1 port.


1.

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

Check the status of an FE/GE port.


1.

Run the MML command DSP ETHPORT to query the status of the Ethernet port.
Expected result: The value of Link Availability Status is Available.
If either of the following cases occurs, see 16.3 Unavailable FE/GE Port for
troubleshooting.
The value of Link Availability Status is Unavailable.
The value of Port state is Deactivated.

2.

Optional: Check the connectivity of the gateway (this operation is mandatory if threelayer networking applies).
a.

Issue 02 (2013-06-25)

Run the MML command LST IPCHK to query the configuration of the gateway
continuity check.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.

64

BSC6910 GSM
Commissioning Guide

16 Troubleshooting

b.

Run the MML command STR IPCHK to start the gateway continuity check.
NOTE

If the BFD function is supported by and enabled at the peer router, set Check type to SBFD.
Otherwise, set it to ARP.

c.

On the alarm tab page of the LMT, check whether ALM-21346 IP Connectivity
Check Failure is reported. If yes, clear the alarm according to the alarm handling
suggestions.

d.

Optional: To keep the gateway continuity check, end the check task; otherwise,
run the MML command STP IPCHK to stop the gateway continuity check.

Checking the status of an optical port


1.

Run the MML command DSP OPT to query the status of an optical port.
Expected result: The value of Optical port state is Available.
If the value of Optical port state is not Available, check the alarms related to the
optical port and rectify the fault according to the handling suggestions in the online
alarm reference.

----End

16.2 Unavailable E1/T1 Port


This section describes how to troubleshoot an unavailable E1/T1 port.BSC6910 only support
the E1/T1 over SDH mode.

Fault Description
When you run the MML command DSP E1T1 to check the status of E1/T1 ports, Port running
state in the returned result is Port is down.

Solution
1.

If Port running state is Port is down, perform the group loopback test on all the faulty
E1/T1 ports because only optical ports serve as the bearers on the BSC6910. For details,
see 16.6 Performing a Loopback Test on an Optical Port.

2.

Check whether the following alarms are listed on the alarm tab page on the LMT. If any
of the alarms exists, handle them according to the suggestions in online alarm reference.
l ALM-21294 SDH/SONET TU Signal Loss
l ALM-21275 SDH/SONET Tributary Loss of Frame
l ALM-21286 SDH/SONET Tributary Remote Alarm Indication Signal
l ALM-21288 SDH/SONET Tributary Loss of Multiframe
l ALM-21287 SDH/SONET Tributary Alarm Indication Signal

16.3 Unavailable FE/GE Port


This section describes how to troubleshoot an unavailable FE/GE port.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

65

BSC6910 GSM
Commissioning Guide

16 Troubleshooting

Fault Description
When you run the MML command DSP ETHPORT to check the status of the FE/GE port, one
of the following events occurs exists:
l

The value of Link Availability Status is Unavailable.

The value of Port state is Deactivated.

1.

If the value of Link Availability Status is Unavailable, check the connection of the
network cable and check whether the peer network interface is enabled. See the online
alarm reference for the alarm handling suggestions.

2.

If the value of Port state is Deactivated, run the MML command ACT ETHPORT to
activate the FE/GE port.

Solution

16.4 IP Connection Setup Failure


This section describes how to troubleshoot an IP connection setup failure.

Fault Description
During IP connection setup, the IP link fails to be established.

Solution
If the user plane uses a transmission resource pool, troubleshoot the problem according to Table
16-2.
Table 16-2 Procedure for troubleshooting the IP connection setup failure if the user plane uses
a transmission resource pool
Index

Operation

Remarks

*1-1

Determine the SIP


addresses of the
common
channels.

Run the MML command DSP ADJNODESIP to query the


value of SIP address for all common channels.

*1-2

Check whether
the SIP status is
normal.

Run the MML command DSP IPPOOL to query the value of


SIP operation state.
l If SIP operation state is Normal, go to *1-3.
l If SIP operation state is Fault, go to *1-4.

*1-3

Check whether
the peer IP address
is normal.

Run the MML command DSP ADJNODEPING to query the


values of Peer IP address and Detection status.
l If Detection status is Normal, go to *1-4.
l If Detection status is Abnormal, troubleshoot the
transmission link fault by following instructions in
Unavailable FE/GE Port.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

66

BSC6910 GSM
Commissioning Guide

16 Troubleshooting

Index

Operation

Remarks

*1-4

Check whether
the transmission
link is normal.

Check whether the transmission link is normal by following


instructions in Checking Transmission Links.
l If the transmission link is normal, go to *1-5.
l If the transmission link is abnormal, troubleshoot the
transmission link fault by following instructions in
Unavailable FE/GE Port.

Check the status


of the source IP
route.

*1-5

Run the MML command DSP SRCIPRT to check the value


of Route Status.
l If Route Status is UP, go to *1-7.
l If Route Status is DOWN, go to *1-6.

*1-6

Check whether
the source IP route
is correctly
configured.

Run the MML command LST SRCIPRT to query the


configuration of the policy-based route using the source IP
address.
l If the configuration is incorrect, correct the configuration.
l If , go to *1-7.

*1-7

Check the
transmission route
conditions.

Run the MML command TRC IPADDR to check the


transmission route conditions and ask the transmission
equipment engineer for further processing.

16.5 Data Loading Failures on the Board


This section describes how to troubleshoot failures that occur during data loading to a
BSC6910 board.

Fault Description
The status of a board on the device panel is abnormal when host software and data files are being
loaded to the BSC6910 board.

Solution
1.

2.

Issue 02 (2013-06-25)

Check the loading status of other boards of the same type in this subrack.
If...

Then...

Board status of other boards of


the same type is Normal

Replace the faulty board and then reload data to the


new board.

Board status of other boards of


the same type is Faulty

Go to 2.

Check whether the DIP switch on the subrack is set as configured.

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

67

BSC6910 GSM
Commissioning Guide

3.

4.

5.

6.

7.

Issue 02 (2013-06-25)

16 Troubleshooting

If...

Then...

The DIP switch on the subrack


is not set as configured

Correct the DIP switch setting and then reload data to


the board.

The DIP switch on the subrack


is set as configured

Go to 3.

Check whether the internal subnet mask of the OMU board is 255.0.0.0 and whether the
two internal IP addresses are *.168.3.50 and *.168.3.40.
If...

Then...

No

Correct the internal subnet mask and internal IP


address and then reload data to the board.

Yes

Go to 4.

If data loading on the boards in the EPS fails, check whether the SCUb board in the MPS
is properly connected to that in the EPS.
If...

Then...

The connection is improper

Correct the connection and reload data to the board.

The connection is proper

Go to 5.

Run the MML command LST SUBRACK to check whether the type of the faulty board
is properly set.
If...

Then...

The type of the board is


incorrectly set

Correct the board type and then reload data to the


board.

The type of the board is correctly


set

Go to 6.

Check whether any alarm related to board fault is present in the Alarm Browser window.
If...

Then...

Alarms related to board fault


exist

Analyze the alarm information and clear the alarm.

No alarm related to board fault


exists

Go to 7.

Contact Huawei Customer Service Center.

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

68

BSC6910 GSM
Commissioning Guide

16 Troubleshooting

16.6 Performing a Loopback Test on an Optical Port


This section describes how to perform the group loopback test to check whether an optical port
is functional.

Prerequisites
You have 6 Logging In to the BSC6910 Through the LMT.

Context
The loopback test can be performed on an optical port when the E1/T1 transmission link on a
standard interface is unavailable.

Procedure
Step 1 Perform the loopback test on the local optical port.
Table 16-3 Procedure for performing the loopback test on the SDH port
Step

Operation

1-1

Run the MML command SET OPTLOP to set a loopback test on a local optical
port. In this command, set Loop type to LOCAL_LOOP(LOCAL_LOOP).

1-2

Run the MML command DSP E1T1 to query Port State.

1-3

Run the MML command SET OPTLOP to stop the loopback test on the optical
port. In this command, set Loop type to NO_LOOP(NO_LOOP).

If...

Then...

The command output shows that the value


of Port State is AVAILABLE

The SDH port is available. Go to Step 2.

The command output shows that the value


of Port State is LINK_DOWN

The SDH port is faulty. Replace the interface


board carrying the faulty SDH port.

Step 2 Perform the loopback test on the local fiber optical cable.
Table 16-4 Procedure for performing the loopback test on the local fiber

Issue 02 (2013-06-25)

Step

Operation

2-1

Perform fiber physical loopback at the local end, that is, connect the TX end of the
fiber optic cable to the RX end of the fiber optic cable.

2-2

Run the MML command DSP E1T1 to query Port State.

2-3

Stop the fiber optic cable physical loopback at the local end.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.

69

BSC6910 GSM
Commissioning Guide

16 Troubleshooting

If...

Then...

The command output shows that the value


of Port State is AVAILABLE

The local fiber optic cable is available. Go to


Step 3.

The command output shows that the value


of Port State is LINK_DOWN

The local fiber optic cable is faulty. Replace the


faulty fiber optic cable.

Step 3 Perform the loopback test on the peer optical port.


Table 16-5 Procedure for performing the loopback test on the peer optical port
Step

Operation

3-1

Run the MML command SET OPTLOP at the local end, set Loop type to
REMOTE_LOOP(REMOTE_LOOP).

3-2

l If the peer equipment is the BSC6910, run the MML command DSP OPT at the
peer end to query the state of the optical port.
l If the peer equipment is not the BSC6910, contact the maintenance personnel for
the peer equipment to query the state of the optical port.

3-3

Run the MML command SET OPTLOP to stop the loopback test on the optical
port. In this command, set Loop type to NO_LOOP(NO_LOOP).

If...

Then...

The command output shows that the


optical port state is available

Contact Huawei Customer Service Center.

The command output shows that the port


state is faulty

Contact the maintenance personnel for the peer


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

----End

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

70

BSC6910 GSM
Commissioning Guide

17 Appendix

17

Appendix

About This Chapter


This chapter provides communication ports on and the commissioning checklist of the
BSC6910.
17.1 Communication Ports on the BSC6910
This section describes communication ports on the BSC6910.
17.2 BSC6910 Commissioning Checklist
This section describes the BSC6910 commissioning checklist used to record and check the
BSC6910 commissioning results.

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

71

BSC6910 GSM
Commissioning Guide

17 Appendix

17.1 Communication Ports on the BSC6910


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

17.2 BSC6910 Commissioning Checklist


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

Issue 02 (2013-06-25)

Huawei Proprietary and Confidential


Copyright Huawei Technologies Co., Ltd.

72