bsc6910 gsm commissioning guide(v100r015c00_02)(pdf)-en

8/19/2019 BSC6910 GSM Commissioning Guide(V100R015C00_02)(PDF)-En

1/81

BSC6910 GSM

V100R015C00

Commissioning Guide

Issue 02

Date 2013-06-25

HUAWEI TECHNOLOGIES CO., LTD.


2/81

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: [email protected]

Issue 02 (2013-06-25) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com/


3/81

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

BSC6910 GSM

Commissioning Guide About This Document



ii


4/81

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 installationof 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 MMLcommand scripts.

8 Activating and Verifying the License

This section describes how to activate the license and verify the license configur ation

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

BSC6910 GSM




iii


5/81

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

BSC6910 GSM




iv


6/81


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 byvertical bars. Several items or no item can be selected.

GUI Conventions

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


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

are in boldface. For example, click OK .

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

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

Keyboard Operations

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

Format Description

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

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.

BSC6910 GSM




v


7/81

Action Description

Click Select and release the primary mouse button without moving

the pointer.

Double-click Press the primary mouse button twice continuously andquickly without moving the pointer.

Drag Press and hold the primary mouse button and move the

pointer to a certain position.

BSC6910 GSM




vi


8/81

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

BSC6910 GSM

Commissioning Guide Contents



vii


9/81

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

BSC6910 GSM

Commissioning Guide Contents



viii


10/81

1 Changes in the BSC6910 GSMCommissioning 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:

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.

BSC6910 GSM

Commissioning Guide 1 Changes in the BSC6910 GSM Commissioning Guide



1


11/81

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.

BSC6910 GSM

Commissioning Guide 1 Changes in the BSC6910 GSM Commissioning Guide



2


12/81

2 Commissioning PrerequisitesBefore 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.

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

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

BSC6910 GSM

Commissioning Guide 2 Commissioning Prerequisites



3


13/81

Figure 2-1 Typical network to be commissioned

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

l 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 Software installation package

BSC6910 GSM




4


14/81

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.

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

BSC6910 GSM




5


15/81

3 Commissioning ProcessThe 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.

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

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

BSC6910 GSM

Commissioning Guide 3 Commissioning Process



6


16/81

Figure 3-1 Commissioning flowchart

BSC6910 GSM

Commissioning Guide 3 Commissioning Process



7


17/81

4 Checking Operating Status of HardwareBefore 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) toON.

Step 4 Check the power supply to the subrack components, as listed in Table 4-1. Ensure that thehardware operates correctly.

Table 4-1 Checklist of the power supply to the cabinet components

Component Normal Power Supply Status

Board The RUN indicator on the board panel is

neither steady on nor steady off.

Fan box The RUN indicator on the fan box panel

blinks one second on and one second off in

green after the subrack is powered on.

BSC6910 GSM

Commissioning Guide 4 Checking Operating Status of Hardware



8


18/81

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

BSC6910 GSM

Commissioning Guide 4 Checking Operating Status of Hardware



9


19/81

5 Commissioning the OMUAbout 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.

BSC6910 GSM

Commissioning Guide 5 Commissioning the OMU



10


20/81

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.

l You have obtained the planned OMU IP addresses and the OMU name and recorded them

in Configuration Information for Commissioning the OMU Locally.

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

If... Then...

The link mode of the external OMU

Ethernet adapters is consistent with that of

LAN switches

Go to Step 3.

BSC6910 GSM




11


21/81

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

BSC6910 GSM




12


22/81

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


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


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.

BSC6910 GSM




13


23/81

3. Change the virtual external IP address and the subnet mask of the active and standby OMUs

according to the plan. Ensure that the virtual external IP address is on the same network

segment as the fixed external IP address.

Run the ./omutool extervip The external virtual IP address The subnet mask command to

change the virtual external IP address and the subnet mask. For example, you can type thefollowing 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. 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.

BSC6910 GSM




14


24/81

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 internalIP address and the subnet mask. For example, you

can type the following command and then press

Enter../omutool innercard 80.168.3.60

l Run the ./omutool innervip The internal virtual

IP address command to change the virtual internal

IP address and the subnet mask. For example, you


Enter../omutool innervip 80.168.3.40

NOTE

l When the fixed or virtual internal IP address is being

changed, a window is displayed to remind users to

check whether the virtual or fixed internal IP

address needs to be changed. In this way, users can

make necessary changes to ensure that the two IP

addresses are on the same network segment.

l If the network segment of the virtual or fixed

internal IP address is changed, the Subnet No. must

be changed when updating the OMU database. For

details, see Follow-up Procedure in 7 Updating the

OMU Database to ensure that the OMU

communicates normally with the BSC6910 host.

l Change the backup channel IP address and subnet

mask of the active and standby OMUs:

Run the ./omutool backupcard The IP address

command. For example, you can type the

following command and then press Enter../omutool backupcard 192.168.3.60

l Run the ./omutool debugcard The debugging IP

address command to change the debugging IP

address and the subnet mask. For example, you


Enter../omutool debugcard 192.168.6.60

The preceding IP addresses are

not on the same network

segment as the network of the

operator

Change the backup channel IP address of the standby

OMU.

Run the ./omutool backupcard The IP address

command. For example, you can type the following

command and then press Enter../omutool backupcard 192.168.3.60

Step 5 Change the OMU name.

1. Run the ./omutool hostname OMU name command to change the name of the OMU.

For example, you can type ./omutool hostname omu_123 and then press Enter.

BSC6910 GSM




15


25/81

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.

BSC6910 GSM




16


26/81

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.

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

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

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

is no CPM restriction.

Context

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

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

l 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 ar e specified.

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

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.

BSC6910 GSM




17


27/81

Figure 5-1 Dopra_Linux_U tool window

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

BSC6910 GSM




18


28/81

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 driveis to be used for.

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

BSC6910 GSM




19


29/81

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.

BSC6910 GSM




20


30/81

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 ExternalEthernet Adapters

Selected External Network NetcardMode

l Auto-negotiation is on Auto

l Auto-negotiation is off

l Speed is 10 Mbit/s

l Duplex is Full

10Mb Full



l Duplex is Half

10Mb Half



l Duplex is Full

100Mb Full



l Duplex is Half

100Mb Half



l Duplex is Full

1000Mb Full



l Duplex is Half

1000Mb 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 OMUinstallation 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 installationis complete by referring to the following table.

BSC6910 GSM




21


31/81

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 InstallationProcedure

SuccessfulInstallation

Failed Installation

EOMU

a

At the beginning:

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.

l The RUN indicator

blinks.

l The ALM indicator

is steady on or off.

l The ACT indicator

is steady on or off.

l The OFFLINE

indicator is off.

l The RUN indicator

blinks.

l The ALM indicator

blinks.

l The ACT indicator

is off.

l The OFFLINE

indicator is off.

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.

BSC6910 GSM




22


32/81

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

Prepare the USB flash drive.

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

BSC6910 GSM




23


33/81


34/81

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

supported.

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

1. Start the IE and enter the external virtual IP address of the OMU of the BSC6910 on the

address bar. The log-in dialog box is displayed, as shown in Figure 6-1.

Figure 6-1 BSC6910 log-in dialog box

NOTE

To log in to the BSC6910 by using the Domain user account, establish the connection between the

BSC6910 and the M2000 server.

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

----End

BSC6910 GSM

Commissioning Guide 6 Logging In to the BSC6910 Through the LMT



25


35/81

7 Updating the OMU DatabaseThis 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..

l The MML command data scripts applicable to the local office are verified and the contents

are precise and complete.

Context

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

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

Procedure

l Run the MML command script by running MML commands

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. 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 tointroduce the two methods.

BSC6910 GSM

Commissioning Guide 7 Updating the OMU Database



26


36/81

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.

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.

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

l Run the MML script by using the GUI

1. Run the MML commandSET 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. Run the MML command RST DATA. Click Yes in the displayed dialog box toinitialize theBSC6910 configuration data in the OMU database.

BSC6910 GSM




27


37/81

3. On the LMT, click theBatch 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

BSC6910 GSM




28


38/81

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.

BSC6910 GSM




29


39/81

8 Activating and Verifying the LicenseThis 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..

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

l The license is ready and the license check is passed.

ContextThe 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 workspacedirectory /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 fileto be activated to query the detailed configuration information of the license file.

If... Then...

The license is consistent with what you apply

for

Go to Step 3.

The license is inconsistent with what you

apply for

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

BSC6910 GSM

Commissioning Guide 8 Activating and Verifying the License



30


40/81

If... Then...

The license information is consistent with

the OMU information

Go to Step 4.

The license information is inconsistent with

the OMU information

Modify the inconsistent data and repeat this

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

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

BSC6910 GSM

Commissioning Guide 8 Activating and Verifying the License



31


41/81

9 Loading BSC6910 Board Software and DataFiles

About This Chapter

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

Prerequisites

l The OMU has been commissioned.

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

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.

BSC6910 GSM

Commissioning Guide 9 Loading BSC6910 Board Software and Data Files



32


42/81

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 toset the system to work in effective mode.

Step 2 Run the MML command FMT DATA and set Work Area Flag to Active(Format activearea) 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.

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


l All the subracks have been powered on.

BSC6910 GSM




33


43/81

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

are in normal state

End this task.

The device panel shows that some boards

are not in normal state

Check the faulty boards and clear the alarms

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.


Procedure

Step 1 Run the MML command ACT CRC and do not specify a parameter and check whether theBSC6910 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 theversion 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

BSC6910 GSM




34


44/81

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

BSC6910 GSM




35


45/81

10 Connecting to the M2000This 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.

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

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

Context

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

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.

BSC6910 GSM

Commissioning Guide 10 Connecting to the M2000



36


46/81

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

BSC6910 GSM

Commissioning Guide 10 Connecting to the M2000



37


47/81

11 Setting the Connection Mode Betweenthe 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.

l All the subracks of the BSC6910 are running normally.


l You have completed section 10 Connecting to the M2000.

l 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

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.

BSC6910 GSM

Commissioning Guide

11 Setting the Connection Mode Between the M2000 and

BSC6910 to SSL



38


48/81

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

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

BSC6910 GSM

Commissioning Guide

11 Setting the Connection Mode Between the M2000 and

BSC6910 to SSL



39


49/81

12 Verifying InterfacesAbout 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, A bis, A, Gb, and Lb interfaces. The Lb interface verification is mandatory when an

external serving mobile location center (SMLC) is configured.

BSC6910 GSM

Commissioning Guide 12 Verifying Interfaces



40


50/81

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 thehardware installation acceptance.

l All the subracks of the BSC6910 are running normally.

l You have completed M2000.


Context

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

NOTE

For details about engineering modes, see section Introduction to the Maintenance Mode

Management Feature in the M2000 Product Documentation.

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

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

Procedure

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

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.

BSC6910 GSM




41


51/81

Figure 12-1 Setting the NE engineering mode to TESTING

l 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 cancheck 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

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

BSC6910 GSM




42


52/81


53/81

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 i

bsc6910 gsm commissioning guide(v100r015c00_02)(pdf)-en

Documents