BSC6900 GSM Commissioning Guide(V900R011C00_01)

BSC6900 GSM

V900R011C00

Commissioning Guide

Issue 01

Date 2009-07-30

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For anyassistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but the statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

http://www.huawei.com

mailto:[email protected]

Contents

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

1 Changes in BSC6900 GSM Commissioning Guide.............................................................1-1

2 Prerequisites for Commissioning...........................................................................................2-1

3 Commissioning Process............................................................................................................3-1

4 Verifying the Equipment..........................................................................................................4-14.1 Checking the Operating Status of the Hardware.............................................................................................4-24.2 Verifying the OMU.........................................................................................................................................4-24.3 Logging In to the BSC6900 Through the LMT..............................................................................................4-4

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

6 Activating and Verifying the License....................................................................................6-1

7 Loading BSC6900 Board Software and Data Files...............................................................7-17.1 Generating the Data File for the Loading........................................................................................................7-37.2 Setting the Loading Mode...............................................................................................................................7-37.3 Resetting the BSC6900 Boards.......................................................................................................................7-47.4 Checking the Consistency of the Data and the Version..................................................................................7-5

8 Verifying GSM Interfaces........................................................................................................8-18.1 Verifying the Abis Interface............................................................................................................................8-28.2 Verifying the A Interface................................................................................................................................8-38.3 Verifying the Gb Interface..............................................................................................................................8-58.4 Verifying the Ater Interface............................................................................................................................8-78.5 Verifying the Pb Interface...............................................................................................................................8-7

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

10 Verifying the GSM Services................................................................................................10-1

11 Connecting the BSC6900 to the M2000...............................................................................11-1

12 Creating Scheduled Tasks....................................................................................................12-1

13 FAQ...........................................................................................................................................13-113.1 Checking the Transmission Link.................................................................................................................13-213.2 Unavailable E1/T1 Port...............................................................................................................................13-3

BSC6900 GSMCommissioning Guide Contents

Issue 01 (2009-07-30) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

13.3 Unavailable FE/GE Port..............................................................................................................................13-413.4 IP Connection Setup Failure.......................................................................................................................13-413.5 Data Loading Failure on the Board.............................................................................................................13-513.6 Performing the Loopback Test on the E1/T1 Port......................................................................................13-713.7 Performing the Loopback Test on the Optical Port...................................................................................13-10

14 Appendix..................................................................................................................................14-114.1 Communication Ports Used by the BSC6900.............................................................................................14-214.2 BSC6900 Commissioning Checklist...........................................................................................................14-4

ContentsBSC6900 GSM

Commissioning Guide

ii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2009-07-30)

Figures

Figure 2-1 Typical commissioning network........................................................................................................2-2Figure 4-1 BSC6900 log-in dialog box................................................................................................................4-5Figure 5-1 Batch tab page....................................................................................................................................5-2Figure 5-2 Setting the batch commands...............................................................................................................5-3

BSC6900 GSMCommissioning Guide Figures


iii

Tables

Table 2-1 Requirements for equipment status before commissioning.................................................................2-1Table 2-2 Other commissioning scenarios...........................................................................................................2-2Table 4-1 Checklist of the power supply to the cabinet components...................................................................4-2Table 7-1 Name of the loading file.......................................................................................................................7-3Table 7-2 Time for system resetting in different scenarios..................................................................................7-4Table 10-1 Performing dialing tests on the basic services.................................................................................10-1Table 10-2 Performing dialing tests on the feature services...............................................................................10-2Table 11-1 Configuring the route from the BSC6900 to the M2000.................................................................11-2Table 12-1 Log type and file name.....................................................................................................................12-1Table 13-1 Methods for checking the status of transmission link in different transmission modes..................13-2Table 13-2 Operation index................................................................................................................................13-5Table 13-3 Procedure for performing the loopback test on the local E1/T1 port...............................................13-8Table 13-4 Procedure for performing the loopback test on the local E1/T1 cable.............................................13-8Table 13-5 Procedure for checking the peer equipment or the transport network.............................................13-9Table 13-6 Procedure for performing the loopback test on the SDH port........................................................13-10Table 13-7 Procedure for performing the loopback test on the local fiber.......................................................13-10Table 13-8 Procedure for performing the loopback test on the peer optical port.............................................13-11Table 14-1 Communication ports used by the services of the BSC6900...........................................................14-2

BSC6900 GSMCommissioning Guide Tables


v

About This Document

OverviewThis provides guidelines for commissioning the BSC6900. It includes the following contents:verifying the Operation and Maintenance Unit (OMU), activating and verifying the license,loading the BSC6900 board software and data files, verifying the interfaces and services, andconnecting the BSC6900 to the M2000.

Product VersionThe following table lists the product version related to this document.

Product Name Product Version

BSC6900 V900R011C00

Intended AudienceThis document is intended for field engineers.

Organization1 Changes in BSC6900 GSM Commissioning Guide

This describes the changes made in the BSC6900 GSM Commissioning Guide.

2 Prerequisites for Commissioning

To perform the BSC6900 commissioning, the status of the equipment and the network to becommissioned must meet the conditions described in this part, and the installation software,license, and MML command scripts required for commissioning must be ready.

3 Commissioning Process

The BSC6900 commissioning involves verifying the equipment, updating the OMU database,activating and verifying the license, loading the BSC6900 board software and data files,verifying the interfaces, handling the alarms generated during commissioning, verifying theservices, and connecting the BSC6900 to the M2000.

4 Verifying the Equipment

The verifying of the equipment is the basis for commissioning the BSC6900. The verifying ofthe interfaces and services can be performed only after the equipment is verified. Equipment

BSC6900 GSMCommissioning Guide About This Document


1

verifying involves checking the hardware operating status, verifying the OMU and logging into the BSC6900 through the LMT.

5 Updating the OMU Database

This describes how to update the BSC6900 configuration data in the OMU database by runningMML commands.

6 Activating and Verifying the License

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

7 Loading BSC6900 Board Software and Data Files

This describes how to load the BSC6900 board software and data files to enable the normaloperation of the BSC6900.

8 Verifying GSM Interfaces

This describes how to verify the GSM interfaces on the BSC6900 side during the BSC6900commissioning. The GSM interfaces are the Abis interface, A interface, Gb interface, Ater, andPb interface. The Ater interface verification is mandatory only in BM/TC separated mode. ThePb interface verification is mandatory only if the BSC6900 is configured with an external PCU.

9 Handling the Alarms Generated During the Commissioning

This describes how to handle the alarms generated during the commissioning, thus preventingthe alarms from affecting the verification of services.

10 Verifying the GSM Services

This describes how to verify that the GSM basic services and the feature services that are enabledare normal. The basic services consist of speech service and data service. The feature servicesconsist of the inter-RAT handover, location service, and AMR service.

11 Connecting the BSC6900 to the M2000

This describes how to connect the BSC6900 to the M2000 for the centralized management.

12 Creating Scheduled Tasks

This describes how to create the scheduled tasks for the automatical backup of the system dataand logs after commissioning; thus, the data and logs can be used for the BSC6900 equipmentfault recovery.

13 FAQ

This describes how to handle the common problems during the commissioning.

14 Appendix

This provides the communication ports and the commissioning checklist of the BSC6900.

ConventionsSymbol Conventions

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

About This DocumentBSC6900 GSM

Commissioning Guide

2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2009-07-30)

Symbol Description

Indicates a hazard with a high level of risk, which if notavoided, will result in death or serious injury.

Indicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation, which if notavoided, could result in equipment damage, data loss,performance degradation, or unexpected results.

Indicates a tip that may help you solve a problem or savetime.

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 inboldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are inCourier New.

Command Conventions

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


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

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

{ x | y | ... } Optional items are grouped in braces and separated byvertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.

BSC6900 GSMCommissioning Guide About This Document


3


{ x | y | ... }* Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of allitems 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 titlesare 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 meansthe two keys should be pressed in turn.

Mouse Operations

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

Action Description

Click Select and release the primary mouse button without movingthe 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 thepointer to a certain position.

About This DocumentBSC6900 GSM

Commissioning Guide

4 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2009-07-30)

1 Changes in BSC6900 GSM CommissioningGuide

This describes the changes made in the BSC6900 GSM Commissioning Guide.

01 (2009-07-30)This is the first commercial release.

BSC6900 GSMCommissioning Guide 1 Changes in BSC6900 GSM Commissioning Guide


1-1

2 Prerequisites for Commissioning

To perform the BSC6900 commissioning, the status of the equipment and the network to becommissioned must meet the conditions described in this part, and the installation software,license, and MML command scripts required for commissioning must be ready.

Requirements for the Status of the Equipment

Before commissioning, ensure that the equipment meets the conditions listed in Table 2-1.

Table 2-1 Requirements for equipment status before commissioning

Item Requirement

BSC6900 hardware The hardware is installed and passes the hardware installationcheck and powering-on check.

OMU Configured before delivery. For details, see Checklist for theFactory Settings of the OMU Software.

LMT PC The LMT PC meets the configuration requirements. For details,see Configuration Requirements of the LMT PC.

Requirements for the Commissioning the Network

To ensure smooth verifying of the Abis, Ater, A, and Gb interfaces, the network equipment inthe commissioning network must meet the following requirements:

l At least one BTS is connected to the local BSC6900. The BTS should have passed thecommissioning and can provide basic functions.

l At least one set of Core Network (CN) equipment is connected to the local BSC6900. TheCN equipment should have passed the commissioning and can provide basic functions.

l Three single-mode MSs and one dual-mode MS for testing are functional and are registeredin the HLR.

Figure 2-1 shows a typical commissioning network.

BSC6900 GSMCommissioning Guide 2 Prerequisites for Commissioning


2-1

Figure 2-1 Typical commissioning network

l The figure shows only the connection. The quantity and type of cables are not specified.l Figure 2-1 illustrates the typical commissioning network. Other commissioning scenarios

may be possible, as described in Table 2-2.

Table 2-2 Other commissioning scenarios

Scenario Description

In BM/TC separated mode,with the TCS configuredremotely

The TCS is configured on the MSC side.

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

The external PCU It communicates with the BSC6900 over the Pb interface, andprovides PS service.

The BSC6900 is connectedto the MGW or BTS

Two NEs in the same equipment room are connected directly.

Alarm box configured onBSC6900 side

The alarm box is connected to the BSC6900 LMT that servesas the alarm management system.

2 Prerequisites for CommissioningBSC6900 GSM

Commissioning Guide

2-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2009-07-30)

Requirements for the Software and Data Filesl Software installation package

The installation package of the OMU application that is consistent with the local officeversion must be ready before commissioning.

l LicenseThe license that is applicable to configuration in the local office is obtained through theHuawei technical support engineer.

l MML command script fileBefore commissioning, complete the initial configuration according to the BSC6900GSM Initial Configuration Guide to obtain the MML command script file. In addition,check and ensure the correctness of the data configuration according to the MML commandscript examples and the on-site negotiated data defined in the BSC6900 GSM InitialConfiguration Guide.

BSC6900 GSMCommissioning Guide 2 Prerequisites for Commissioning


2-3

3 Commissioning Process

The BSC6900 commissioning involves verifying the equipment, updating the OMU database,activating and verifying the license, loading the BSC6900 board software and data files,verifying the interfaces, handling the alarms generated during commissioning, verifying theservices, and connecting the BSC6900 to the M2000.

Procedure

Step 1 Verify the equipment by referring to 4 Verifying the Equipment.1. Check the operating status of the hardware by referring to 4.1 Checking the Operating

Status of the Hardware.2. Verify the OMU by referring to 4.2 Verifying the OMU.3. Logging in to the BSC6900 through the LMT by referring to 4.3 Logging In to the

BSC6900 Through the LMT.

Step 2 Update the OMU data by referring to 5 Updating the OMU Database.

Step 3 Activate and verify the license by referring to 6 Activating and Verifying the License.

Step 4 Load the BSC6900 board software and data files by referring to 7 Loading BSC6900 BoardSoftware and Data Files.1. Generate the data file for loading by referring to 7.1 Generating the Data File for the

Loading.2. Set the loading mode by referring to 7.2 Setting the Loading Mode.3. Reset the BSC6900 boards by referring to 7.3 Resetting the BSC6900 Boards.4. Check the consistency of the version and the data by referring to 7.4 Checking the

Consistency of the Data and the Version.

Step 5 Verify GSM interfaces by referring to 8 Verifying GSM Interfaces.1. Verify the Abis interface by referring to 8.1 Verifying the Abis Interface.2. Verify the A interface by referring to 8.2 Verifying the A Interface.3. Verify the Gb interface by referring to 8.3 Verifying the Gb Interface.4. Optional: Verify the Ater interface by referring to 8.4 Verifying the Ater Interface

(required in BM/TC separated mode).5. Optional: Verify the Pb interface by referring to 8.5 Verifying the Pb Interface (required

if the BSC6900 is configured with an external PCU).

BSC6900 GSMCommissioning Guide 3 Commissioning Process


3-1

Step 6 Handle the alarms generated during commissioning by referring to 9 Handling the AlarmsGenerated During the Commissioning.

Step 7 Verify GSM services by referring to 10 Verifying the GSM Services.

Step 8 Connect the BSC6900 to the M2000 by referring to 11 Connecting the BSC6900 to theM2000.

----End

PostrequisiteAfter the commissioning, create scheduled tasks by referring to 12 Creating ScheduledTasks, so that the data backed up can be used for BSC6900 data restoration.

3 Commissioning ProcessBSC6900 GSM

Commissioning Guide


Issue 01 (2009-07-30)

4 Verifying the Equipment

About This Chapter

The verifying of the equipment is the basis for commissioning the BSC6900. The verifying ofthe interfaces and services can be performed only after the equipment is verified. Equipmentverifying involves checking the hardware operating status, verifying the OMU and logging into the BSC6900 through the LMT.

1. 4.1 Checking the Operating Status of the HardwareBefore verifying the equipment, ensure that the cabinet is powered on and operatesnormally.

2. 4.2 Verifying the OMUThis describes how to verify the OMU to enable the normal communication between theLMT and the BSC6900. The OMU verifying involves installing the OMU application onsite, checking the operation status of the OMU and changing the external physical IPaddress.

3. 4.3 Logging In to the BSC6900 Through the LMTLog in to the BSC6900 through the LMT, and enabling the normal communication betweenthe LMT and the BSC6900. LMT verifying ensures the BSC6900 commissioning throughthe LMT.

BSC6900 GSMCommissioning Guide 4 Verifying the Equipment


4-1

4.1 Checking the Operating Status of the HardwareBefore verifying the equipment, ensure that the cabinet is powered on and operates normally.

PrerequisiteThe BSC6900 cabinet has passed the power-on check.

Procedure

Step 1 Check whether the cabinet is powered on.

If... Then...

The cabinet is not powered on, Go to Step 2.

The cabinet is powered on, Go to Step 3.

Step 2 Power on the cabinet by referring to Powering On the Cabinet.

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

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

Component Normal LED Status

Board The green RUN LED on the board panel flashes every othersecond.

Fan box The green STATUS LED on the panel of the fan box flashesevery other second after the subrack and independent fansubrack are powered on.

Power monitoringcommunication board

The green RUN LED on the board panel flashes every othersecond and the ALM LED is also OFF.

----End

4.2 Verifying the OMUThis describes how to verify the OMU to enable the normal communication between the LMTand the BSC6900. The OMU verifying involves installing the OMU application on site, checkingthe operation status of the OMU and changing the external physical IP address.

PrerequisiteThe software installation package of OMU application that is consistent with the version usedin the local office and the Records of OMU Software Installation Information are obtained.

4 Verifying the EquipmentBSC6900 GSM

Commissioning Guide


Issue 01 (2009-07-30)

Context

The external physical IP address described here refers to the physical IP address of the externalEthernet adapter team. This IP address is planned and set before the delivery of the OMU. Itmay be different from the IP address plan in the existing network. In this case, the externalphysical IP address needs to be changed according to the actual networking. Generally, thegateway IP address should be changed with the external physical IP address.

The OMU application is installed in the active workspace of the OMU. If the BSC6900 worksin active/standby OMU mode, then the OMU application must be installed in the activeworkspaces of both the active and standby OMUs. This part takes the condition that only oneOMU is configured on the BSC6900 as an example.

Procedure

Step 1 Connect the PC to the ETH2 debugging port on the OMUa by using an Ethernet cable.

Step 2 Set the IP address of the PC to be in the same network segment with the ETH2 port. The IPaddress of the ETH2 port before changing is 192.168.6.50, the subnet mask is 255.255.255.0.

Step 3 Remotely log in to the Linux operating system by referring to Logging In to the OMU.

Step 4 Check the OMU software environment by referring to Checking the OMU SoftwareEnvironment.

Step 5 Check that the OMU application is normally installed.

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

If... Then...

The returned information is running, Go to Step 5.2.

The returned information is unused, a. Run the /etc/rc.d/omud startcommand to start the omud.

b. Go to Step 5.2.

The returned information is neitherrunning nor unused,

Go to Step 6.

2. Log in to the BSC6900 through the LMT by referring to 4.3 Logging In to the BSC6900Through the LMT. Run the MML command LST VER to view the application version ofthe OMU.

If... Then...

The OMU application version is same as thatrequired by the customer,

End this task.

The OMU application version is differentfrom that required by the customer,

a. Uninstall the OMU application byreferring to Uninstalling the OMUApplications.

b. Go to Step 6.



4-3

Step 6 Install the OMU application in the active workspace by referring to Installing the OMUApplications in the Active Workspace.

Step 7 Run the /etc/rc.d/omud start command to start the OMU application.

Step 8 Run the ps -afx command to check the operating status of the OMU.You can infer that the OMU is in normal state if the following OMU service processes exist inthe OMU active workspace directory\bin\bam\monitor: host_gate, ems_gate, authority,configure, maintain, stat, alarm, software, ftp_server, sntp, btsom, ems_agent,omu_manager, cfa and weblmt.

NOTEYou can infer that the standby OMU is in normal state if the following processes exist: software, ftp_server,sntp, and omu_manager.

Step 9 Run the ifconfig command to check whether the external physical IP address of the OMU issame as that planed in the existing network.

If... Then...

The external physical IP address is same as that planed in the existingnetwork,

End this task.

The external physical IP address is different from that planed in theexisting network,

Go to Step 10.

Step 10 Run the /etc/rc.d/omud stop command to stop the omud.

Step 11 Switch to the directory where the omutool program locates.You can run the ./omutool -h command to view the help information of the omutool.

Step 12 Run the ./omutool extercard The external physical IP address The mask The gateway IPaddress command to change the external physical IP address and the gateway IP address.

For example, you can run the following command and then press Enter.

./omutool extercard 10.161.10.100 255.255.255.0 10.161.10.1

NOTEAfter the external physical IP address is changed, the BSC6900 can be connected to the OM network of thecustomer through the ETH0 or ETH1 port. In this case, the commissioning can be performed in a centralizedmanner.

Step 13 Run the /etc/rc.d/omud start command to start the OMU application so that the modificationtakes effect.

Step 14 Remotely log out of the Linux operating system by referring to Logging Out of the OMU.

----End

4.3 Logging In to the BSC6900 Through the LMTLog in to the BSC6900 through the LMT, and enabling the normal communication between theLMT and the BSC6900. LMT verifying ensures the BSC6900 commissioning through the LMT.


Commissioning Guide


Issue 01 (2009-07-30)

Prerequisitel The OMU has passed the commissioning.l The network connection between the LMT and the OMU is established.

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

WARNINGWhen 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 LMTapplications first.

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

1. Check the hardware configuration of the BSC6900 LMT PC to ensure that the requirementsdescribed in Configuration Requirements of the LMT PC are satisfied.

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

Step 2 Start the Internet Explorer, and then log in to the BSC6900 through the LMT.1. Start the Internet Explorer. and then enter the external virtual IP address of the OMU of

the BSC6900 on the address bar. The log-in dialog box is displayed, as shown in Figure4-1.

Figure 4-1 BSC6900 log-in dialog box



4-5

NOTETo log in to the BSC6900 by using the Domain user account, the connection between the BSC6900 andthe M2000 server should be established.

2. Enter the User Name, Password, and Verify Code, and then click Login to enter the LMTmaintain interface.

----End


Commissioning Guide


Issue 01 (2009-07-30)

5 Updating the OMU Database

This describes how to update the BSC6900 configuration data in the OMU database by runningMML commands.

Prerequisitel You have logged in to the BSC6900 through the LMT.

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

ContextThere are two ways to run the MML command script: through GUI or through MML commands.The MML command script can be executed through GUI only when the script is smaller than 4MB. It is recommended that you run the MML script through MML commands, because thisway is more efficient.

Procedurel Run the MML command script through MML commands

1. Run the MML command SET CFGDATAINEFFECTIVE and do not specify anyparameter to set all the subracks to the ineffective mode.

2. Run the MML command RST DATA. A dialog box is displayed. Click OK toinitialize the BSC6900 configuration data in the OMU database. The Executionsucceeded message is displayed.

3. Copy the MML command script to the ftp folder in the OMU active workspacedirectory.

NOTEThe directory of the OMU active workspace can be queried through the MML command LSTOMUAREA.

4. Run the MML command RUN BATCHFILE to run the MML command script. It isrecommended that you set Finish Type to ALL_END_RETURN(Stop at end),Result Recording Type to REC_ERR(Record errors), and Result File Name toRUN_BATCHFILE_RESULT.txt.

BSC6900 GSMCommissioning Guide 5 Updating the OMU Database


5-1

NOTE

l The result file RUN_BATCHFILE_RESULT.txt is saved in the ftp folder in the OMU activeworkspace directory.

l After the MML command script is executed, open the RUN_BATCHFILE_RESULT.txt file tocheck whether there is any command fails to be executed. If yes, extract the commands that failto be executed to generate a new MML command script, correct the new script according to theprompts, and then go to Step 4 to run the new script.

l Run the MML command script through GUI1. Run the MML command SET CFGDATAINEFFECTIVE and do not specify any

parameter to set all the subracks to the ineffective mode.2. Run the MML command RST DATA. A dialog box is displayed. Click OK to

initialize the BSC6900 configuration data in the OMU database. The Executionsucceeded message is displayed.

NOTEIf an Error dialog box showing Execution failed. Do you want to continue? is displayed duringthe execution of the MML command script, you can infer that the MML command script is incorrect.In this case, select Yes to all to ignore the error prompt. After the script is executed, extract thecommands that are fail to be executed to generate a new MML command script, correct the newscript, and then go to Step 4 to run the new script.

3. Click Batch on the LMT main page. The Batch tab page is displayed, as shown inFigure 5-1.

Figure 5-1 Batch tab page

4. Click Open.... The Open dialog box is displayed.5. Select the prepared MML command data script. Click Open. The selected script is

displayed in the Batch tab page.6. Click Set.... The dialog box for setting batch commands is displayed.7. Set Sending Commands interval(s) to 0. Select Save Failed Commands, and then

set the save path of the unsuccessful commands. Click OK to complete the setting ofthe batch commands, as shown in Figure 5-2.

5 Updating the OMU DatabaseBSC6900 GSM

Commissioning Guide


Issue 01 (2009-07-30)

Figure 5-2 Setting the batch commands

8. In the Batch tab page, set Execution Type to All.9. Click Go. The system runs the MML commands one by one.

NOTE

Click OK when the system prompts that the current configuration is in ineffective mode after youclick Go. The execution of MML commands may take a long time. A total of 50,000 commands canbe run in an hour.

10. Click OK when the message dialog box is displayed, indicating that the running ofall the MML commands is complete.

----End

BSC6900 GSMCommissioning Guide 5 Updating the OMU Database


5-3

6 Activating and Verifying the License

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


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

Procedure

Step 1 Run the MML command DLD LICENSE to download the License to the OMU activeworkspace directory\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 applyfor,

Go to Step 3.

The license is inconsistent with what youapply for,

Contact the Huawei Customer ServiceCenter by referring to Contact the HuaweiCustomer Service Center.

Step 3 Run the MML command ACT LICENSE to activate the license file.

----End

PostrequisiteIf the license activation fails, you can infer that the configuration data of the license isinconsistent 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 of the license is incorrect, apply for a new license.

BSC6900 GSMCommissioning Guide 6 Activating and Verifying the License


6-1

l If the configuration data in the OMU database is incorrect, correct the configuration data,and then activate the license again.

6 Activating and Verifying the LicenseBSC6900 GSM

Commissioning Guide


Issue 01 (2009-07-30)

7 Loading BSC6900 Board Software and DataFiles

About This Chapter

This describes how to load the BSC6900 board software and data files to enable the normaloperation of the BSC6900.

Prerequisitel The equipment verifying is complete.

l The OMU database is updated.

ContextThe software of BSC6900 boards is generated automatically in the OMU active workspacedirectory\bin\fam when installing OMU applications. The software can be loaded directly.

To make the configuration take effect, format the configuration data in the OMU database togenerate a .DAT data file, and then reset the BSC6900.

Procedure

----End

1. 7.1 Generating the Data File for the LoadingThis describes how to generate the BSC6900 data file, which can be loaded, by using theMML command data scripts.

2. 7.2 Setting the Loading ModeThis describes how to set the loading modes of all the board subsystems before resettingBSC6900 boards.

3. 7.3 Resetting the BSC6900 BoardsThis describes how to load the BSC6900 board software and data files from the OMUinstallation directory to the boards and make them take effect.

4. 7.4 Checking the Consistency of the Data and the Version

BSC6900 GSMCommissioning Guide 7 Loading BSC6900 Board Software and Data Files


7-1

This describes how to check whether the board configuration and the software version ofthe BSC6900 are consistent with the information in the OMU.

7 Loading BSC6900 Board Software and Data FilesBSC6900 GSM

Commissioning Guide


Issue 01 (2009-07-30)

7.1 Generating the Data File for the LoadingThis describes how to generate the BSC6900 data file, which can be loaded, by using the MMLcommand data scripts.


ContextThe generated loading file is saved in OMU active workspace directory\bin\fam. The file nameis in ABCXXYYZZ.DAT format, such as XPUa000200.DAT. Table 7-1 lists the detailedinformation.

Table 7-1 Name of the loading file

Parameter Indication

ABC Board name

XX Subrack number

YY Slot number

ZZ Subsystem number

Procedure

Step 1 Run the MML command SET CFGDATAEFFECTIVE and do not specify any parameter toset all the subracks to effective mode.

Step 2 Run the MML command FMT DATA and set Work Area Flag to Active(Format activearea) (do not specify the subrack number) to format the configuration data in the OMU database.If the Execution succeeded message is displayed, then the .DAT data files are generatedand saved in OMU active workspace directory\bin\fam.

----End

7.2 Setting the Loading ModeThis describes how to set the loading modes of all the board subsystems before resettingBSC6900 boards.

PrerequisiteYou have logged in to the BSC6900 through the LMT.

ContextFor details about the loading modes, see Loading Management.



7-3

Procedure

Step 1 Run the MML command SET LODCTRL, and then set Board Start Load Control to LFB(Load from OMU and write flash). If the Execution succeeded message is displayed, the settingof the BSC6900 loading modes is complete.

----End

7.3 Resetting the BSC6900 BoardsThis describes how to load the BSC6900 board software and data files from the OMU installationdirectory to the boards and make them take effect.

Prerequisitel The data file for the Loading is generated.

l You have logged in to the BSC6900 through the LMT.

l All the subracks are powered on.

Context

The time for system resetting is different in different scenarios, as listed in Table 7-2.

Table 7-2 Time for system resetting in different scenarios

Work Mode Resetting Time Sequence for ResettingSubracks

BM/TC combined, orA over IP

The resetting time is less thannine minutes in the maximumconfiguration.

The subracks should be reset inthe following sequence: EPS ->MPS.

BM/TC separate The resetting time is less thanfifteen minutes in the maximumconfiguration.

The subracks should be reset inthe following sequence: remoteextension TCS-> remote mainTCS -> EPS -> MPS.

You can run the MML command LST SUBRACK and then check the parameters SubrackType and Remote TC Central to determine the resetting sequence.

Procedure

Step 1 Run the MML command RST SUBRACK, and then set Subrack No. to the number of thesubrack to be reset. A dialog is displayed, asking you whether to proceed. Click OK. The boardsin the subrack automatically load the BSC6900 board software and data files from the OMU.Run this command repeatedly to reset all the subracks of the BSC6900.

NOTEYou can observe the loading process at the Progress tab page on the LMT main page. If this tab page is hidden,click Progress in the toolbar on the LMT main page.

7 Loading BSC6900 Board Software and Data FilesBSC6900 GSM

Commissioning Guide


Issue 01 (2009-07-30)

Step 2 After all the subracks are reset, click the Device Maintenance on the LMT main page. TheDevice Maintenance tab page is displayed.

Step 3 Click the BSC6900 to be queried in the Device Navigation Tree to start the device panel.

If... Then...

The device panel shows that all the boardsare in normal state,

End this task.

The device panel shows that some boardsare in normal state,

Rectify the faults according to the prompt. Fordetails, see 13.5 Data Loading Failure on theBoard.

----End

7.4 Checking the Consistency of the Data and the VersionThis describes how to check whether the board configuration and the software version of theBSC6900 are consistent with the information in the OMU.

Prerequisitel All the subracks and boards are running normally.


Procedure

Step 1 Run the MML command ACT CRC and do not specify any parameter to check whether theboard configuration is consistent with the data in the OMU.Expected result: The All table data consistent. message is displayed.

Step 2 Run the MML command CMP BRDVER and do not specify any parameter to check whetherthe version run by the BSC6900 is consistent with the version information in the OMU.Expected result: The Compare consistent message is displayed.

If... Then...

The board configuration or software versionof the BSC6900 is inconsistent with theinformation in the OMU,

Run the MML command RST SUBRACK toreset the subrack with incorrect data orversion.

The board configuration or software versionof the BSC6900 is consistent with theinformation in the OMU,

The BSC6900 board software and data filesare loaded successfully, end this task.

----End



7-5

8 Verifying GSM Interfaces

About This Chapter

This describes how to verify the GSM interfaces on the BSC6900 side during the BSC6900commissioning. The GSM interfaces are the Abis interface, A interface, Gb interface, Ater, andPb interface. The Ater interface verification is mandatory only in BM/TC separated mode. ThePb interface verification is mandatory only if the BSC6900 is configured with an external PCU.

ContextDuring the interface verification, you can run the LST command to query the configurationinformation. For example, before running the MML command DSP ADJNODE, you can runthe MML command LST ADJNODE to query the parameter Adjacent Node ID.

8.1 Verifying the Abis InterfaceThis describes how to verify the control plane and the user plane of the Abis interface. The Abisinterface verification varies according to the transmission mode over the Abis interface.

8.2 Verifying the A InterfaceThis describes how to verify the control plane and the user plane of the A interface. The Ainterface verification varies according to the transmission mode of the A interface.

8.3 Verifying the Gb InterfaceThis describes how to verify the Gb interface. The Gb interface verification varies according tothe transmission mode over the Gb interface.

8.4 Verifying the Ater InterfaceThis describes how to verify the Ater interface when the BSC6900 is in BM/TC separated mode.

8.5 Verifying the Pb InterfaceIf the BSC6900 is configured with an external PCU, Pb interface verification is needed.

BSC6900 GSMCommissioning Guide 8 Verifying GSM Interfaces


8-1

8.1 Verifying the Abis InterfaceThis describes how to verify the control plane and the user plane of the Abis interface. The Abisinterface verification varies according to the transmission mode over the Abis interface.

Prerequisitel The BSC6900 has passed the commissioning.

l The BSC6900 and the base stations are physically connected, and the hardware installationacceptance is passed.

l The base stations used to verify the Abis interface are commissioned and the cellconfiguration is complete.

l All the subracks of the BSC6900 are running normally.


ContextFor 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 onthe Abis interface. If multiple base stations are connected, repeat the operations.

Procedurel Verifying the Abis interface (Abis over TDM)

1. Run the MML command DSP LAPDLNK to check whether the Link Access Protocolon the D channel (LAPD) link on the Abis interface is normal.

Expected result: The value of UsageStatus is Normal.2. Run the MML command DSP ABISTS to query the timeslot status of the Abis

interface.

Expected result: The State of many timeslots is Idle, and there is no timeslot with theState of Failure.

If the LAPD link or timeslot status on the Abis interface is abnormal, checking thetransmission link by referring to 13.1 Checking the Transmission Link.

3. Run the MML command DSP BTSATTR to query the status of the carrier of the basestation.Expected result: The value of Cell Initialized is Yes and the value of ChannelFault is No.

l Verifying the Abis interface (Abis over IP)1. Run the MML command DSP LAPDLNK to check whether the LAPD link on the

Abis interface is normal.

Expected result: The value of UsageStatus is Normal.2. Run the MML command DSP ADJNODE to query the status of the adjacent node.

Expected result: The value of Operation state is Available and the availablebandwidth cannot be all 0.

8 Verifying GSM InterfacesBSC6900 GSM

Commissioning Guide


Issue 01 (2009-07-30)

3. Run the MML command DSP IPPATH to query the status of the IP path on the Abisinterface.

Expected result: The value of Operation state is Available.

If the value of Operation state is Unavailable, see 13.4 IP Connection SetupFailure for troubleshooting.

4. Run the MML command DSP BTSSTAT to query the status of the cells and channels.Expected result: The value of Cell Initialized is Yes and the value of ChannelFault is No.

l Verifying the Abis interface (Abis over HDLC)1. Run the MML command DSP LAPDLNK to check whether the LAPD link on the

Abis interface is normal.

Expected result: The value of UsageStatus is Normal.2. Optional: Run the MML command LST BTSABISHDLCPATH to query the HDLC

link number.3. Run the MML command DSP HDLCLNK to query the status of the HDLC link.

Expected result: The value of operation state is Available and the value of AvailableTx Bandwidth or Available Rx Bandwidth is not 0.

4. Run the MML command DSP BTSSTAT to query the status of the cells and channels.Expected result: The value of Cell Initialized is Yes and the value of ChannelFault is No.

----End

8.2 Verifying the A InterfaceThis describes how to verify the control plane and the user plane of the A interface. The Ainterface verification varies according to the transmission mode of the A interface.


l The BSC6900 and the MSC are physically connected.

l The MSC used to verify the A interface operates normally.

l The Ater interface has been verified when the BSC6900 is in BM/TC separated mode.



Procedurel Verifying the A interface (A over TDM)

1. Run the MML command DSP MTP2LNK to query the status of the Message TransferPart Level 2 (MTP2) signaling link.

Expected result: The value of Link State is IN SERVICE.

If the value of Link State is OUT OF SERVICE, check the transmission links byreferring to 13.1 Checking the Transmission Link.



8-3

2. Run the MML command DSP MTP3LNK to query the status of the Message TransferPart Level 3 (MTP3) signaling link.Expected result: The value of Operation state is Available.

3. Run the MML command DSP SSN to query the status of the SCCP SSN.Expected result: The value of SSN state is Allowed.

4. Run the MML command DSP N7DPC to query the status of the SS7 destinationsignaling point.

Expected result: The value of SCCP DSP state is Accessible.

5. Optional: Run the MML command LST AE1T1 to query the configurationinformation such as OPC Index and DPC Group Index.

6. Run the MML command DSP ACIC to query the status of A interface circuits.Expected result: The CIC State of many CICs is Idle, and there is no CIC with theCIC State of Failure.

l Verifying the A interface (A over IP)

1. Run the MML command DSP SCTPLNK to query the status of the Stream ControlTransmission 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 byreferring to 13.1 Checking the Transmission Link.

NOTE

Run the MML command DSP SCTPLNK for two or three times, if the value of Operation stateis always Normal and the value of State Changed Time does not change, you can infer that theSCTP link is normal without intermittent disconnection.

2. Run the MML command DSP M3LNK to query the status of the MTP3 User AdaptionLayer (M3UA) signaling link.Expected result: The value of Operation state is Activated state.

3. Run the MML command DSP SSN to query the status of the SCCP SSN.Expected result: The value of SSN state is Allowed.

4. Run the MML command DSP N7DPC to query the status of the SS7 destinationsignaling point.Expected result: The value of SCCP DSP state is Accessible.

5. Run the MML command DSP ADJNODE to query the status of the adjacent node.Expected result: The value of Operation state is Available and the availablebandwidth cannot be all 0.

6. Run the MML command DSP IPPATH to query the status of the IP path.

Expected result: The value of Operation state is Available.

If the value of Operation state is Unavailable, see 13.4 IP Connection SetupFailure for troubleshooting.

----End


Commissioning Guide


Issue 01 (2009-07-30)

8.3 Verifying the Gb InterfaceThis describes how to verify the Gb interface. The Gb interface verification varies according tothe transmission mode over the Gb interface.


l The BSC6900 and the SGSN are physically connected, and the hardware installationacceptance is passed.

l The SGSN equipment used to verify the Gb interface operates normally.



Procedurel Verifying the Gb interface links (Gb over FR)

1. Run the MML command DSP BC to query the status of the Bearer Channel (BC) tobe verified.

Expected result: The value of BC Service State is available.

NOTEIf the value of BC Administration State is Blocked, run the MML command UBL BC to unblockthe BC, and then run the MML command DSP BC to check whether the BC status is normal. If thestatus remains abnormal, check the transmission links by referring to 13.1 Checking theTransmission Link.

2. Run the MML command DSP NSVC to query the status of the Network ServiceVirtual Connection (NSVC) to be verified.Expected result: The value of NSVC Service State is Active Unblock.

3. Optional: Run the MML command LST NSE to query the NSE configurationinformation.

4. Run the MML command DSP SIGBVC to query the SIG BSSGP Virtual Connection(SIGBVC) status of the Network Service Entity (NSE) to be verified.Expected result: The value of SIG BVC State is Normal.

NOTEIf the value of SIG BVC State is Fault, the SGSN may be configured with an NSE that has a differentNSE ID.

5. Run the MML command DSP PTPBVC to query the status of the PTP BSSGP VirtualConnection (PTPBVC) of the NSE to be verified.Expected result: The value of Service State is Normal.

l Verifying the Gb interface links (Gb over IP)1. Optional: Run the MML command LST NSVLLOCAL or LST NSVLREMOTE

to query the configuration information of the local or remote Network Service VirtualLink (NSVL).

2. Run the MML command DSP NSVL to query the status of the Network ServiceVirtual Link (NSVL) to be verified.

Expected result: The value of NSVL State is Normal .



8-5

If the value of NSVL State is Fault, check the transmission links by referring to 13.1Checking the Transmission Link.

3. Run the MML command DSP GBIPROUTE to query the status of the IP connectionto be verified on the Gb interface.

Expected result: The value of State is Normal .

If the value of State is Faulty, run the MML command DSP IPRT to check whetherthe route configuration on the Gb interface is correct.

4. Optional: Run the MML command LST NSE to query the NSE configurationinformation.

5. Run the MML command DSP SIGBVC to query the SIGBVC status of the NSE tobe verified.Expected result: The value of SIG BVC State is Normal.

NOTEIf the value of SIG BVC State is Fault, the SGSN may be configured with an NSE that has a differentNSE ID.

6. Run the MML command DSP PTPBVC to query the PTPBVC status of the NSE tobe verified.Expected result: The value of Service State is Normal.

----End

Postrequisite

Handling Suggestions to Exceptional NSVC Status

l If the value of NSVC Manage State is Unblock and the NSVC Service State is ActiveBlock, you can infer that the FR link that bears the NSVC is functional and that the NSVCis blocked by the SGSN.

l If the value of NSVC Manage State is Block and the NSVC Service State is ActiveBlock, you can infer that the FR link that bears the NSVC is functional and that the NSVCis blocked by the BSC6900 or by both the BSC6900 and the SGSN.

1. Run the MML command UBL NSVC to unblock the BSC6900.2. Run the MML command DSP NSVC to query the status of the NSVC. If the value of

NSVC Service State is still Active Block, you can infer that the NSVC is blocked bythe SGSN.

l If the value of NSVC Service State is Deactive Block, the possible causes are as follows:– The NSVC ID and NSE ID of the NSVC on the BSC6900 are inconsistent with that on

the SGSN.– The NSVC configured on the same BC at the SGSN is not the required one.

Handling Suggestions to Exceptional PTPBVC Service Status

1. If the value of PTPBVC Manage State is Block, run the MML command UBLPTPBVC to unblock the PTPBVC, and then run the MML command DSP PTPBVC toquery the status of the PTPBVC. If the status remains abnormal, go to the next step.

2. Run the MML command RST PTPBVC to reset the PTPBVC, and then run the MMLcommand DSP PTPBVC to query the status of the PTPBVC. If the status remainsabnormal, go to the next step.


Commissioning Guide


Issue 01 (2009-07-30)

3. Run the MML command RST PSCELL to reset the cell corresponding to the exceptionalPTPBVC, and then run the MML command DSP PTPBVC to query the status of thePTPBVC. If the status remains abnormal, go to the next step.

4. Run the MML command RST SIGBVC to reset the SIGBVC corresponding to theexceptional PTPBVC, and then run the MML command DSP PTPBVC to query the statusof the PTPBVC. If the status remains abnormal, contact the Huawei Customer ServiceCenter by referring to Contact the Huawei Customer Service Center.

8.4 Verifying the Ater InterfaceThis describes how to verify the Ater interface when the BSC6900 is in BM/TC separated mode.


l The MPS/EPS and the TCS are physically connected.

l The data configuration on the Ater interface is complete.

l The TCS is loaded and started.


Procedure

Step 1 Optional: Run the MML command LST ATERE1T1 to query the configuration informationsuch as Ater connection path index and ID of BSC in TC Pool.

Step 2 Run the MML command DSP ATERTS to query whether the service paths on the Aterconnection channels are normal.

Expected result: The State of many timeslots is Idle, and there is no timeslot with the State ofFailure.

If the State of a timeslot is Failure, check the transmission links by referring to 13.1 Checkingthe Transmission Link.

Step 3 Optional: If the TCS is configured remotely, run the MML command DSP ATERSL to querywhether the data configuration of the Ater signaling link is normal.

Expected result: The value of UsageStatus is Normal.

If the value of UsageStatus is Faulty, check the transmission links by referring to 13.1 Checkingthe Transmission Link.

Step 4 Repeat Step 2 through Step 3 to verify whether the service channels on other Ater connectionpaths are normal.

----End

8.5 Verifying the Pb InterfaceIf the BSC6900 is configured with an external PCU, Pb interface verification is needed.



8-7

Prerequisitel The PCU used to verify the Pb interface operates normally.

l The BSC6900 and the PCU are physically connected, and the hardware installationacceptance is passed.



Procedure

Step 1 Run the MML command DSP LAPDLNK to check whether the LAPD link on the Pb interfaceis normal.

Expected result: The value of UsageStatus is Normal.

Step 2 Optional: Run the MML command LST PBE1T1 to query the E1/T1 configuration informationon the Pb interface.

Step 3 Run the MML command DSP PBCIC to query the status of the circuit on the Pb interface.Expected result: The status of many circuit identity codes (CICs) is Idle, and there is no CICwith the status of Failure.

----End


Commissioning Guide


Issue 01 (2009-07-30)

9 Handling the Alarms Generated During theCommissioning

This describes how to handle the alarms generated during the commissioning, thus preventingthe alarms from affecting the verification of services.

Prerequisitel The communication between the BSC6900 and the OMU is normal.


Procedure

Step 1 Click the Alarm on the LMT main page. The Alarm tab page is displayed.

Step 2 Check whether any alarm is listed on the Fault tab page.

If... Then...

No alarm is listed, End this task.

One or more alarms are listed, Go to Step 3.

Step 3 Double-click the alarm to be handled in the fault tab page. The Alarm Detailed Informationdialog box is displayed.

Step 4 Click Solution.... The LMT Online Help interface is displayed.

Step 5 Follow the suggestions to handle the alarm.

NOTEIf the alarm persists, contact the Huawei Customer Service Center by referring to Contact the HuaweiCustomer Service Center.

Step 6 Repeat Step 3 to Step 5 to handle other alarms.

----End

BSC6900 GSMCommissioning Guide 9 Handling the Alarms Generated During the Commissioning


9-1

10 Verifying the GSM Services

This describes how to verify that the GSM basic services and the feature services that are enabledare normal. The basic services consist of speech service and data service. The feature servicesconsist of the inter-RAT handover, location service, and AMR service.


l The commissioning over the Abis, A, Gb, Ater and Pb interfaces is successful. Thecommissioning over Ater interface is mandatory only in BM/TC separated mode. Thecommissioning over Pb interface is mandatory only if the BSC6900 is configured with anexternal PCU.

l The MSs used for test are functional and are registered in the HLR.


Procedure

Step 1 Table 10-1 lists the procedure for verifying the basic services by testing the MS in the BTS cells.

Table 10-1 Performing dialing tests on the basic services

Basic Services Procedure for Conductingthe Dialing Test

Expected Result

Speech service Make 20 calls from an MS to afixed-line phone and hold on eachcall for 60 seconds.

The connection success rate ishigher than 90%. The voice isclear and without loud noise. Nocall drop occurs and the systemresources are released normallyafter the call is terminated.

Make 20 calls from a fixed-linephone to an MS and hold on eachcall for 60 seconds.


BSC6900 GSMCommissioning Guide 10 Verifying the GSM Services


10-1

Basic Services Procedure for Conductingthe Dialing Test

Expected Result

Make 20 calls from an MS toanother MS and hold on each callfor 60 seconds.


Data service Send a fax from an MS to anelectrograph. Send a fax from anelectrograph to an MS.

Faxes are sent and receivednormally.

Test the General Packet RadioService (GPRS) or EnhancedData Rate for GSM Evolution(EDGE) function on the MS.

The test data rate is similar to thedata rate tested in a lab.

NOTEIf the result of service verification cannot meet the expected results, start message tracing on the LMT over theUm, Abis, A, Gb, Pb, and Ater interfaces. Where the message tracing over the Pb interface is mandatory onlywhen the BSC6900 is configured with an external PCU, and the message tracing over the Ater interface ismandatory only in BM/TC separated mode.

Step 2 Table 10-2 lists the procedure for verifying the feature services by testing the MS in the BTScells.

Table 10-2 Performing dialing tests on the feature services

Feature Services Procedure for Conductingthe Dialing Test

Expected Result

Inter-RAT handover Hand over a dual-mode MS fromthe GSM to the UMTS for 20times. Hand over a dual-modeMS from the UMTS to the GSMfor 20 times.

The connection success rate ishigher than 90%. The voice isclear and without loud noise.

Location service Make a call from the MS and holdon the call. Then, locate the MS.

The location of the MS conformsto the precision requirements.

Adaptive Multi Rate(AMR) service

Make 50 calls from an MS to afixed-line phone and select voiceversion to AMR.

The connection success rate ishigher than 90%. The voice isclear and without loud noise.

----End

10 Verifying the GSM ServicesBSC6900 GSM

Commissioning Guide


Issue 01 (2009-07-30)

11 Connecting the BSC6900 to the M2000

This describes how to connect the BSC6900 to the M2000 for the centralized management.

Prerequisitel The Operation and Maintenance (OM) network has passed commissioning. The M2000 is

operational.l The version of the M2000 is compatible with that of the BSC6900.

Contextl If the BSC6900 and the M2000 are in the same network segment, you need not configure

the IP route to the M2000.l If the BSC6900 and the M2000 are not in the same network segment, you need to configure

the IP route to the M2000.

Procedure

Step 1 Connect the BSC6900 to the OM network.1. Connect one end of the straight-through cable to the LAN Switch that is connected to the

BSC6900.2. Connect the other end of the straight-through cable to the network device, for example, a

hub or a router.

Step 2 Configure the IP route from the BSC6900 to the M2000.1. Run the MML command LST OMUIPRT to check whether the route to the M2000 is

configured on the OMU.l If the values of Destination Network Address, Destination Address Mask, and

Forward Route Address in the result are consistent with the planed addresses, thenyou can infer that the BSC6900 already has a route to the M2000. Go to Step 2.3.

l If the Destination Network Address, Destination Address Mask, and ForwardRoute Address in the result are not consistent with the planed addresses, then you caninfer that the BSC6900 does not have a route to the M2000. Go to Step 2.2.

2. Run the MML command ADD OMUIPRT to configure the route from the BSC6900 tothe M2000.

3. Verify the configuration of the route from the BSC6900 to the router.

BSC6900 GSMCommissioning Guide 11 Connecting the BSC6900 to the M2000


11-1

Logging in to the OMU remotely, run the ping command to check whether the networkbetween the BSC6900 and the router is operational. If the OMU can receive a responsepacket from the router, go to Step 2.4. Otherwise, check that the OMU and the router areproperly connected.

4. Verify the configuration of the route from the BSC6900 to the M2000.Logging in to the OMU remotely, run the ping command to check whether the networkbetween the BSC6900 and the M2000 is operational. If the BSC6900 can receive a responsepacket from the router, go to Step 3. Otherwise, check that the M2000 and the router areproperly connected.

Step 3 Create the BSC6900 on the M2000. For details, see the NE creating-related parts in M2000documents.

CAUTIONl If a firewall exists between BSC6900 and M2000, ensure the communication ports

connecting the BSC6900 and M2000.l For details on the ports connecting the BSC6900 and M2000, see 14.1 Communication

Ports Used by the BSC6900.

----End

ExampleTable 11-1 describes how to configure the route between the BSC6900 and the M2000.

Table 11-1 Configuring the route from the BSC6900 to the M2000

Scenario

The IP address of the M2000 server is 10.11.100.23. The mask is 255.255.255.0.The OMU is connected to the M2000 network segment through the router. The IPaddress of the router is 172.121.139.10.

Action 1. Run the MML command ADD OMUIPRT.l Set Destination Network Address to 10.11.100.23.

l Set Destination Address Mask to 255.255.255.0.

l Set Forward Route Address to 172.121.139.10.

2. Run the Telnet client, such as PuTTY, to log in to the OMU.3. Run the ping 172.121.139.10 command.4. Run the ping 10.11.100.23 command.

11 Connecting the BSC6900 to the M2000BSC6900 GSM

Commissioning Guide


Issue 01 (2009-07-30)

12 Creating Scheduled Tasks

This describes how to create the scheduled tasks for the automatical backup of the system dataand logs after commissioning; thus, the data and logs can be used for the BSC6900 equipmentfault recovery.



l To create scheduled tasks, you must be an administrator.

ContextYou can set the period for the scheduled task according to the actual situation. The period forthe scheduled task is of the following types: fixed time, day based scheduling, day based duration,week based scheduling, week based duration, month based scheduling, and month basedduration.

l Scheduled tasks for backing up system data

After the scheduled task is executed, you can obtain the latest backup file from the backupdirectory on the OMU. For the backup directory and the file name, see the HelpInformation of the MML command BKP DB.

l Scheduled tasks for backing up logs

The logs are backed up in the OMU active workspace directory\ftp directory as compressedfiles at the specified time. Table 12-1 lists the name of the compressed files.

Table 12-1 Log type and file name

Type File Name

ALL FixInfo_All.zip

OMU FixInfo_OMU.zip

HOST FixInfo_HOST.zip

BSC6900 GSMCommissioning Guide 12 Creating Scheduled Tasks


12-1

To check the information of the logs, download the logs through the FTP client. For details,see the help information of the FTP client.

NOTE

l The files that are automatically backed up do not overwrite the files backed up earlier.

l For the directory structure of the OMU workspace, see Checking the Installation Directory of the OMUApplications.

Procedure

Step 1 Run the MML command ADD SCHTSK. Specify the Task Name and Task ID to add ascheduled task.

Step 2 Run the MML command ADD SUBTSK. Set Command String to BKP DB to create ascheduled task for backing up the system data.

Step 3 Run the MML command ADD SUBTSK. Set Command String to COL LOG to create ascheduled task for backing up logs.l To view the created tasks, run the MML command LST SUBTSK.

l To change the time and period for backing up tasks, run the MML command MODSUBTSK.

----End

Examplel To set the system data to be backed up at 2010-4-12-12:00:00, run the following command:

ADD SUBTSK: ID=1, SUBID=8, SCMD="BKP DB:", FREQ=ONTIME,SD=2010&04&12, TM=12&00;

l To set the BSC6900 logs to be automatically backed up from 2010-4-10-11:01:52 to2010-4-12-11:01:52 (log type: ALL, time mode: fixed time), run the following command:ADD SUBTSK: ID=1, SUBID=44, SCMD="COL LOG: TP=ALL,ST=2010&04&10&11&01&52, ET=2010&04&12&11&01&52", FREQ=ONTIME,SD=2010&04&13, TM=12&00;

12 Creating Scheduled TasksBSC6900 GSM

Commissioning Guide


Issue 01 (2009-07-30)

13 FAQ

About This Chapter

This describes how to handle the common problems during the commissioning.

13.1 Checking the Transmission LinkThis describes how to verify that the terrestrial transmission links of the BSC6900 are functional.The verification covers E1/T1 port, FE/GE port, optical port, and upper-layer link.

13.2 Unavailable E1/T1 PortThis describes how to handle the problem that the E1/T1 port is unavailable.

13.3 Unavailable FE/GE PortThis describes how to handle the problem that the FE/GE port is unavailable.

13.4 IP Connection Setup FailureThis describes how to handle the failures during IP connection setup.

13.5 Data Loading Failure on the BoardThis describes how to handle the failures that occur during data loading to the BSC6900 board.

13.6 Performing the Loopback Test on the E1/T1 PortThis describes how to perform the loopback test to check whether the E1/T1 port is functional.

13.7 Performing the Loopback Test on the Optical PortThis describes how to perform the group loopback test to check whether the optical port isfunctional.

BSC6900 GSMCommissioning Guide 13 FAQ


13-1

13.1 Checking the Transmission LinkThis describes how to verify that the terrestrial transmission links of the BSC6900 are functional.The verification covers E1/T1 port, FE/GE port, optical port, and upper-layer link.

Prerequisitel All the subracks of the BSC6900 are running normally.


Procedurel Check the status of the transmission link based on the transmission mode.

Table 13-1 Methods for checking the status of transmission link in different transmissionmodes

If the transmission on the interface isover...

Then...

IP PPP/MLPPP transmission mode 1. If the channelized STM-1transmission is used on theinterface, check the status of theoptical port.

2. Check the status of the E1/T1port.

3. Check the status of the upper-layerlink.l For the PPP transmission mode,

run the MML command DSPPPPLNK to check the status ofthe PPP link.

l For the MLPPP transmissionmode, run the MML commandDSP MPGRP to check thestatus of the MLPPP group.NOTE

If the upper-layer link is notfunctional, run the MMLcommand LST PPPLNK/LSTMPGRP accordingly to checkwhether the data configuration onthe interface is correct.

IP over Ethernet transmission mode Check the status of the FE/GEport.

TDM

E1/T1 transmission mode Check the status of the E1/T1port.

13 FAQBSC6900 GSM

Commissioning Guide


Issue 01 (2009-07-30)

If the transmission on the interface isover...

Then...

Channelized STM-1 transmission mode Checkg the status of the opticalport.

HDLC Check the status of the E1/T1port.

FR Check the status of the E1/T1port.

l Checking the status of the E1/T1 port

1. Run the MML command DSP E1T1 to query the status of the E1/T1 ports.

Expected result: The Port running state of the associated E1/T1 port is Portavailable.

If the value of the Port running state is Port is down, see the 13.2 Unavailable E1/T1 Port for troubleshooting.

l Checking the status of the FE/GE port1. Run the MML command DSP ETHPORT to query the status of the Ethernet port.

Expected result: The value of Link Availablility Status is Available.

If either of the following cases occurs, see 13.3 Unavailable FE/GE Port fortroubleshooting.– The value of Link Availablility Status is Unavailable.– The value of Port state is Deactivated.

2. Optional: Check the connectivity of the gateway (mandatory in three-layernetworking).

(1) Run the MML command LST IPCHK to query the configuration of the gatewayconnectivity check.

(2) Run the MML command STR IPCHK to start the gateway connectivity check.NOTE

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

(3) In the alarm tab page of the LMT, check whether the ALM-21346 IP ConnectivityCheck Failure alarm is reported. If yes, clear the alarm as suggested.

(4) To keep the gateway connectivity check, end this task; otherwise, run the MMLcommand STP IPCHK to stop the gateway connectivity check.

l Checking the status of the optical port1. Run the MML command DSP OPT to query the status of the optical port.

Expected result: The value of Optical port state is Available.

----End

13.2 Unavailable E1/T1 PortThis describes how to handle the problem that the E1/T1 port is unavailable.



13-3

SymptomsWhen you run the MML command DSP E1T1 to check the status of E1/T1 ports, the Portrunning state on the returned result shows Port is down.

Solutions1. If the value of Port running state is Port is down, handle the problem as follows:

l When electrical ports serve as the bearers, perform loopback test on the faulty E1/T1ports. For details, see 13.6 Performing the Loopback Test on the E1/T1 Port.

l When optical ports serve as the bearers, perform group loopback test on the faulty opticalports. For details, see 13.7 Performing the Loopback Test on the Optical Port.

2. Check whether the following alarms are listed in the alarm tab page of the LMT. If any ofthe alarms exist, handle them according to the suggestions in the online help.l ALM-21201 E1/T1 Signal Lossl ALM-21202 E1/T1 Frame out of Synchronizationl ALM-21203 E1/T1 Remote Alarm Indicationl ALM-21205 E1/T1 Multiframe out of Synchronization

NOTE

When you run the MML command DSP E1T1 to check the E1/T1 port status, the value of Is thisE1/T1 occupied may be set to NO. In such a case, if the ALM-21201 E1/T1 Signal Loss exists, thelink is still operational.

13.3 Unavailable FE/GE PortThis describes how to handle the problem that the FE/GE port is unavailable.

SymptomsWhen you run the MML command DSP ETHPORT to check the status of the FE/GE port, anyof the following situation exists:l The value of Link Availablility Status is Unavailable.l The value of Port state is Deactivated.

Solutions1. If the value of Link Availablility Status is Unavailable, check the connection of the

Ethernet cable and check whether the peer Ethernet port is enabled. See the online help forthe handling suggestions of the alarm.

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

13.4 IP Connection Setup FailureThis describes how to handle the failures during IP connection setup.

SymptomsDuring IP connection setup, the IP link fails to be established.

13 FAQBSC6900 GSM

Commissioning Guide


Issue 01 (2009-07-30)

Solutions

When the user plane is over IP transmission, handle the failure according to Table 13-2.

Table 13-2 Operation index

Index Action Remarks

*1-1 Determine the IPpath that carriesthe commonchannel.

Run the MML commands LST IPPATH and LSTTRMMAP to obtain the ID of the IP path that carries thecommon channel.

*1-2 Check whetherthe IP path isoperational.

1. Run the MML command DSP IPPATH to query the statusof the IP path.

2. If any transmission resource group is configured over theIub interface, run the MML command DSP RSCGRP toquery the status of the transmission resource group.

3. If all the IP paths are unavailable, go to *1-3.

*1-3 Check whetherthe transmissionlink is operational.

1. See 13.1 Checking the Transmission Link.2. If the transmission link is unavailable, go to *1-4.3. If the transmission link is available, go to *1-5.

*1-4 Handle thetransmission linkfailure.

1. If the data is transmitted over Ethernet, for example,through FE ports, see 13.3 Unavailable FE/GE Port.

2. If the data is transmitted over a private line, for example,over E1/T1 cable, see 13.2 Unavailable E1/T1 Port.

*1-5 Check theconfiguration ofthe IP path.

Run the MML command LST IPPATH to check whether thenegotiated data is consistent. If inconsistency exists, modifythe negotiated data.

*1-6 Check the real-time IP routeinformation.

Run the MML command DSP IPRT to check the real-time IProute information.

13.5 Data Loading Failure on the BoardThis describes how to handle the failures that occur during data loading to the BSC6900 board.

SymptomsThe status of the board on the device panel is abnormal when the BSC6900 board software anddata files are being loaded to the BSC6900 boards.

Solutions1. Check the board status of other boards of the same type in this subrack.



13-5

If... Then...

Board status of other boards ofthe same type is Normal,

Replace the faulty board and then reload the data tothe new board.

Board status of other boards ofthe same type is Faulty,

Go to 2.

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

If... Then...

The DIP switch on the subrackis not set as configured,

Correct the DIP switch setting and then reload thedata to the board.

The DIP switch on the subrackis set as configured,

Go to 3.

3. Check whether the internal subnet mask of the OMUa board is 255.0.0.0 and whether the

two internal IP addresses are *.168.3.50 and *.168.3.40.

If... Then...

No Correct the internal subnet mask and internal IPaddress and then reload the data to the board.

Yes Go to 4.

4. If data loading on the DPU boards in the EPS fails, check whether the SCUa boards in the

MPS and that in the EPS are properly connected.

If... Then...

The connection is improper, Correct the connection, and then reload the data to theboard.

The connection is proper, Go to 5.

5. Run the MML command LST SUBRACK to check whether the type of the faulty board

is properly set.

If... Then...

The type of the board isincorrectly set,

Correct the board type and then reload the data to theboard.

The type of the board is correctlyset,

Go to 6.

6. If the data loading on the DPUc board in the remote TCS fails, run the MML command

DSP ATEROML to check whether the OML on the Ater interface is functional, and thenrun the MML command DSP E1T1 to check whether the physical link between the Aterinterface boards is functional.

13 FAQBSC6900 GSM

Commissioning Guide


Issue 01 (2009-07-30)

If... Then...

The OML is faulty, and thephysical link is functional,

1. Check whether the configuration is consistent withthe physical OML connection. If they areinconsistent, modify the configuration accordingto the physical OML connection.

2. Check whether the cross connection exists in thephysical OML. If yes, correct the physicalconnection of the OML, and then reload the datato the board.

The OML is faulty, and thephysical link is also faulty,

Correct the connection, and then reload the data to theboard.

The OML is functional, Go to 7.

7. Check whether any alarm related to board fault is present in the Alarm tab page.

If... Then...

Alarms related to board faultexist,

Analyze the alarm information and accordingly clearthe alarm.

No alarm related to board faultexists,

Go to 8.

8. Contact the Huawei Customer Service Center.

13.6 Performing the Loopback Test on the E1/T1 PortThis describes how to perform the loopback test to check whether the E1/T1 port is functional.


Contextl The loopback test and the Bit Error Rate (BER) test cannot be performed simultaneously.

l The loopback test leads to temporary interruption of services carried over this link.

l The loopback test can be performed when the E1/T1 port is unavailable.

Procedure

Step 1 Perform the loopback test on the local E1/T1 port.



13-7

Table 13-3 Procedure for performing the loopback test on the local E1/T1 port

Step Action

1-1 Run the MML command SET E1T1LOP. Set Loop type to LOCAL_LOOP(Localloop).

1-2 Run the MML command LOP E1T1 to start the loopback test on the E1/T1 port.

1-3 Run the MML command DSP E1T1LOP to query the result of the loopback test.

1-4 Run the MML command SET E1T1LOP, and then set Loop type to NO_LOOP(No loop) to stop the loopback test on the E1/T1 port.

If... Then...

If the loopback test result isSucceeded,

The E1/T1 port is operational. Go to Step 2.

If the loopback test result is Notsucceeded,

The E1/T1 port is faulty. Replace the interface boardcarrying the faulty E1/T1 port.

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

Table 13-4 Procedure for performing the loopback test on the local E1/T1 cable

Step Action

2-1 Perform E1/T1 physical loopback at the local end, that is, connect the TX end of theE1/T1 cable to the RX end of the E1/T1 cable.

2-2 Run the MML command LOP E1T1 to start the loopback test on the E1/T1 port.

2-3 Run the MML command DSP E1T1LOP to query the result of the loopback test.

2-4 Stop the E1/T1 physical loopback at the local end.

If... Then...


The local E1/T1 cable is operational. Go to Step 3.

13 FAQBSC6900 GSM

Commissioning Guide


Issue 01 (2009-07-30)

If... Then...


l Use a multimeter to measure the connectivity betweenthe connector pin of the E1/T1 cable and the innerconductor of the coaxial cable and that between the outershell of the connector and the shielding layer of thecoaxial cable. If a connectivity failure occurs, make anew connector and assemble the cable again.

l Use a multimeter to check whether the internal andexternal conductors of the E1/T1 cable are short-circuited. If so, make a new connector and assemble thecable again.

If the fault persists, replace the E1/T1 cable with a new one.

Step 3 Perform the loopback test on the peer E1/T1 port.

Table 13-5 Procedure for checking the peer equipment or the transport network

Step Action

3-1 Run the MML command SET E1T1LOP. Set Loop type to REMOTE_LOOP(Remote loop).

3-2 Run the MML command LOP E1T1 at the peer end to start the loopback test on theE1/T1 port.

3-3 Run the MML command DSP E1T1LOP at the peer end to query the result of theloopback test.

3-4 Run the MML command SET E1T1LOP at the peer end, and then set Loop typeto NO_LOOP(No loop) to stop the loopback test on the E1/T1 port.

If... Then...


Go to Step 4.


Contact the maintenance personnel for the peer equipmentto rectify faults in the peer equipment or the transportnetwork.

Step 4 If the E1/T1 for loopback belongs to an IMA group, then run the MML command RSTIMAGRP. Click OK on the displayed dialog box to reset that IMA group.

----End



13-9

13.7 Performing the Loopback Test on the Optical PortThis describes how to perform the group loopback test to check whether the optical port isfunctional.


ContextThe loopback test can be performed on optical port when the E1/T1 transmission link on thestandard interface is unavailable.

Procedure

Step 1 Perform the loopback test on the local optical port.

Table 13-6 Procedure for performing the loopback test on the SDH port

Step Action

1-1 Run the MML command SET OPTLOP, and then set Loop type toLOCAL_LOOP(LOCAL_LOOP).

1-2 Run the MML command DSP OPT to query the result of the loopback.

1-3 Run the MML command SET E1T1LOP, and then set Loop type to NO_LOOP(NO_LOOP) to stop the loopback test on the optical port.

If... Then...

The values of Optical port state in theresult are Available,

The SDH port is operational. Go to Step 2.

The values of Optical port state in theresult are Fault,

The SDH port is faulty. Replace the interfaceboard carrying the faulty SDH port.

Step 2 Perform the loopback test on the local fiber.

Table 13-7 Procedure for performing the loopback test on the local fiber

Step Action

2-1 Perform fiber physical loopback at the local end, that is, connect the TX end of thefiber to the RX end of the fiber.

2-2 Run the MML command DSP OPT to query the result of the loopback.

2-3 Stop the fiber physical loopback at the local end.

13 FAQBSC6900 GSM

Commissioning Guide


Issue 01 (2009-07-30)

If... Then...


The local fiber is operational. Go to Step 3.


The local fiber is faulty. Replace the faulty fiber.

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

Table 13-8 Procedure for performing the loopback test on the peer optical port

Step Action

3-1 Run the MML command SET OPTLOP, and then set Loop type toREMOTE_LOOP(REMOTE_LOOP).

3-2 Run the MML command DSP OPT at the peer end to query the result of theloopback.

3-3 Run the MML command SET E1T1LOP at the peer end, and then set Loop typeto NO_LOOP(NO_LOOP) to stop the loopback test on the optical port.

If... Then...


Contact the Huawei Customer Service Center.


Contact the maintenance personnel for the peerequipment to rectify faults in the peer equipmentor the transport network.

----End



13-11

14 Appendix

About This Chapter

This provides the communication ports and the commissioning checklist of the BSC6900.

14.1 Communication Ports Used by the BSC6900This provides communication ports used by the BSC6900.

14.2 BSC6900 Commissioning ChecklistBSC6900 commissioning checklist is for recording and checking the result of BSC6900commissioning.

BSC6900 GSMCommissioning Guide 14 Appendix


14-1

14.1 Communication Ports Used by the BSC6900This provides communication ports used by the BSC6900.

Table 14-1 lists the number of the communication ports used by the services of the BSC6900.

Table 14-1 Communication ports used by the services of the BSC6900

Protocol

SideA

SideAPorts(Listening)

Side B SideBPorts(Launch)

Service Authentication

TCP OMU 20 BSC6900Host,LMT,M2000Server

1024-65535

For FTP data. FAM Load,software and log upload/download (active mode)

username/password

TCP OMU 21 BSC6900Host,LMT,M2000Server

1024-65535

For FTP control. FAMLoad, software and logupload/download

username/password

TCP LMT 21 OMU 1024-65535

For FTP control, this portfor OMU

username/password

TCP OMU 1500 BSC6900Host

1024-65535

Exchange, communicationwith FAM

IP Address

TCP OMU 3389 RemoteDesktop

1024-65535

the port is used by MSTSC,to maintain OMU

username/password

TCP/SSL

OMU 6000/8000

LMT,M2000Server

1024-65535

MML, For Maintain username/password

TCP/SSL

OMU 6001/8001

LMT,M2000Server

1024-65535

MML, For Alarm username/password

TCP/SSL

OMU 6006/8006

LMT,M2000Server

1024-65535

LMT, For Maintain username/password

TCP LMT 80 LMTcomputer

80 For LMT Web browsing username/password

14 AppendixBSC6900 GSM

Commissioning Guide


Issue 01 (2009-07-30)

Protocol

SideA




TCP/SSL

OMU 6022/8022

Equipment debugconsole

1024-65535

MML, for equipmentdebug console

None

TCP OMU 6088 Upgradetool

1024-65535

For Upgrade tool None

TCP/SSL

OMU 6093/8093

Testvalidation

1024-65535

MML, Emluator operate None

TCP/SSL

OMU 6099/8099

M2000Server

1024-65535

MML, datasynchronization withM2000

None

TCP/SSL

OMU 6100/8100

LMT 1024-65535

MML, Alarm Box None

TCP/SSL

OMU 16002/18002

M2000Server

1024-65535

MML, notificationmessage from performanceand M2000

None

TCP MySQL

3306 Peer OMU 1024-65535

MySQL username/password

TCP BTS 700 SMT 1024-65535

For local maintenance,SMT(StationManagement), it will beused before GBTS connectin the network

None

TCP OMU 22 SSHClient

1024-65535

Putty terminal tool port(SSH)

username/password

TCP OMU 139/445

SambaClient

1024-65535

Samba service port username/password

UDP OMU 67 BSC6900Host

1024-65535

Load, Bootp Listen None

UDP OMU 123 OMU 1024-65535

NTP Server,slow timesynchronization, locallistening port

None

BSC6900 GSMCommissioning Guide 14 Appendix


14-3

Protocol

SideA




UDP OMU 1234 BSC6900Host

1024-65535

NTP, time synchronizationwith FAM, local listeningport

None

UDP OMU 11774 Peer OMU 1024-65535

SecurityManager, for dualOMU

None

UDP OMU 11775 Peer OMU 1024-65535

SecurityManager, for dualOMU

None

UDP OMU 11776 Peer OMU 1024-65535

SecurityManager, backuptunnel between dual OMU

None

UDP M2000Server

123 OMU 123 NTPClient, timesynchronization withtime's server, locallistening port

None

14.2 BSC6900 Commissioning ChecklistBSC6900 commissioning checklist is for recording and checking the result of BSC6900commissioning.

BSC6900 Commissioning Checklist.

14 AppendixBSC6900 GSM

Commissioning Guide


Issue 01 (2009-07-30)

BSC6900 GSM Commissioning Guide(V900R011C00_01)

Documents

Transcript of BSC6900 GSM Commissioning Guide(V900R011C00_01)