BSC6900 GSM Commissioning Guide(V900R012C01_05)

BSC6900 GSM V900R012C01

Commissioning Guide Issue

05

Date

2011-03-07

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. 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 mentioned in this document are the property of of their respective respective holders. 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 document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, 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 recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address:

Huawei Industrial Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website:

http://www.huawei.com

Email:

[email protected]

Issue 05 (2011-03-07)

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

i

BSC6900 GSM Commissioning Guide

About This Document

About This Document Overview BSC6900 commissioning is performed after the hardware is installed and before the services are provided. It aims to ensure that the BSC6900 can work properly by performing verification tasks related to equipment, BSC6900 board software and data file loading, interfaces, and services. This document provides guidelines for commissioning the BSC6900. It includes the following contents: Verifying the Operation and Maintenance Unit (OMU), Activating and Verifying the License, Loading the BSC6900 Board Software and Data Files, Connecting the BSC6900 to the M2000, and Verifying the Interfaces and Services.

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

Product Name

Product Version

BSC6900

V900R012C01

Intended Audience This document is intended for field engineers.

Organization 1 Changes in the BSC6900 GSM Commissioning Guide

This chapter describes the changes in the BSC6900 GSM Commissioning Guide. 2 Prerequisites for Commissioning

Before the BSC6900 commissioning, the status of the equipment and the network to be commissioned must meet the conditions required. The software installation package, license, and MML command scripts required for commissioning must be ready. 3 Commissioning Process Issue 05 (2011-03-07)


iii


About This Document

The BSC6900 commissioning can be performed remotely or locally. Remote commissioning is performed by the remote engineer (technical owner of the BSC) and multiple BSCs can be commissioned simultaneously in the central equipment room. Local commissioning is performed by the site engineer (commissioning owner in the BSC equipment room) who connects a PC to the BSC and performs the commissioning through the LMT. There is also another commissioning mode: remote commissioning through local assistance, which is performed by both the remote engineer and the site engineer. 4 Checking Operating Status of Hardware

Before verifying the equipment, ensure that the cabinet is powered on and operates normally. 5 Verifying the OMU

This section describes how to verify the OMU to enable the normal communication between the LMT and the BSC6900. The OMU verification involves installing the OMU operating system and OMU ap plication, checking the OMU operation status, and changing the external fixed IP address and external virtual IP address of the OMU on site. 6 Logging in to the BSC6900 Through the LMT

This section describes how to log in to the BSC6900 through the LMT and enable the normal communication. LMT verification ensures the BSC6900 commissioning through the LMT. 7 Updating the OMU Database

This describes how to update configuration data in the OMU database by running MML commands. 8 Activating and Verifying the License

This chapter describes how to activate the license and verify the licensed configuration information to enable service checking. 9 Loading BSC6900 Board Software and Data Files

This chapter describes how to load the BSC6900 board software and data files to enable the normal operation of the BSC6900. 10 Connecting the BSC6900 to the M2000

This chapter describes how to connect the BSC6900 to the M2000 for the centralized management. 11 Verifying Interfaces

This section describes how to verify interfaces. The interfaces to be verified are Abis, A, Gb, Ater, Pb, and Lb interfaces. The Ater interface verification is mandatory in BM/TC separated mode; the Pb interface verification is mandatory when the external PCU is used on the BSC6900; the Lb interface verification is mandatory when the external SMLC is used on the BSC6900. 12 Handling the Alarms Generated During the Commissioning

This chapter describes how to handle the alarms generated during the commissioning, thus preventing the alarms from affecting the verification of services. 13 Verifying the GSM Services

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


Issue 05 (2011-03-07)


About This Document

14 Verifying Network Reliability

The network reliability is verified by alarm checks and dialing tests after the active/standby switchover of boards. 15 FAQ

This chapter describes how to handle the common problems encountered during the commissioning. 16 Appendix

This chapter details the communication ports and the commissioning checklist of the BSC6900.

Conventions Symbol Conventions

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

Symbol

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

General Conventions

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

Convention

Description

Times New Roman

Normal paragraphs are in Times New Roman.

Boldface

Names of files, directories, folders, and users are in boldface. For example, log in as user root.

Italic

Book titles are in italics.

Courier New

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

Issue 05 (2011-03-07)


v


About This Document

Command Conventions

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

Convention

Description

Boldface

The keywords of a command line are in boldface.

Italic

Command arguments are in italics.

[]

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

{ x | y | ... }

Optional items are grouped in braces and separated by vertical bars. One item is selected.

[ x | y | ... ]

Optional items are grouped in brackets and separated by vertical bars. One item is selected or no i tem is selected.

{ x | y | ... } *

Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected.

[ x | y | ... ] *

Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.

GUI Conventions

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

Convention

Description

Boldface

Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK .

>

Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.

Keyboard Operations

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

Format

Description

Key

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

Key 1+Key 2

Press the keys concurrently. For example, pressing Ctrl+Alt +A means the three keys should be pressed concurrently.

Key 1, Key 2

Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.

Mouse Operations vi


Issue 05 (2011-03-07)


About This Document

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

Issue 05 (2011-03-07)

Action

Description

Click

Select and release the primary mouse button without moving the pointer.

Double-click

Press the primary mouse button twice continuously and quickly without moving the pointer.

Drag

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


vii


Contents

Contents About This Document...................................................................................................................iii 1 Changes in the BSC6900 GSM Commissioning Guide......................................................1-1 2 Prerequisites for Commissioning...........................................................................................2-1 3 Commissioning Process............................................................................................................3-1 4 Checking Operating Status of Hardware..............................................................................4-1 5 Verifying the OMU....................................................................................................................5-1 5.1 Verifying the OMU Locally............................................................................................................................5-2 5.2 Verifying the OMU Through USB Disk.........................................................................................................5-6

6 Logging in to the BSC6900 Through the LMT......................................................................6-1 7 Updating the OMU Database..................................................................................................7-1 8 Activating and Verifying the License....................................................................................8-1 9 Loading BSC6900 Board Software and Data Files...............................................................9-1 9.1 Generating the Data File for the Loading........................................................................................................9-2 9.2 Setting the Loading Mode...............................................................................................................................9-2 9.3 Resetting the BSC6900 Boards.......................................................................................................................9-3 9.4 Checking the Consistency of the Data and the Version..................................................................................9-4

10 Connecting the BSC6900 to the M2000...............................................................................10-1 11 Verifying Interfaces...............................................................................................................11-1 11.1 Verifying Interfaces Through M2000.........................................................................................................11-2 11.1.1 Setting Maintenance Mode of NE to Install.......................................................................................11-2 11.1.2 Verifying Interfaces Automatically....................................................................................................11-2 11.1.3 Setting the Maintenance Mode of the NE to Normal.........................................................................11-4 11.2 Verifying Interfaces Through LMT............................................................................................................11-5 11.2.1 Verifying the Abis Interface...............................................................................................................11-6 11.2.2 Verifying the A Interface...................................................................................................................11-8 11.2.3 Verifying the Gb Interface...............................................................................................................11-10 11.2.4 Verifying the Ater Interface.............................................................................................................11-12 11.2.5 Verifying the Pb Interface................................................................................................................11-13 11.2.6 Verifying Lb Interface......................................................................................................................11-13 Issue 05 (2011-03-07)


ix


Contents

11.2.7 Verifying the Internal Interfaces......................................................................................................11-14

12 Handling the Alarms Generated During the Commissioning......................................12-1 13 Verifying the GSM Services................................................................................................13-1 14 Verifying Network Reliability............................................................................................14-1 15 FAQ...........................................................................................................................................15-1 15.1 Checking the Transmission Link.................................................................................................................15-2 15.2 Unavailable E1/T1 Port...............................................................................................................................15-4 15.3 Unavailable FE/GE Port..............................................................................................................................15-4 15.4 IP Connection Setup Failure.......................................................................................................................15-5 15.5 Board Data Loading Failure........................................................................................................................15-5 15.6 Performing the Loopback Test on the E1/T1 Port......................................................................................15-7 15.7 Performing the Loopback Test on the Optical Port.....................................................................................15-9 15.8 Setting Maintenance Mode f or NE............................................................................................................15-11

16 Appendix..................................................................................................................................16-1 16.1 Communication Ports Used by the BSC6900.............................................................................................16-2 16.2 BSC6900 Commissioning Checklist...........................................................................................................16-4

x


Issue 05 (2011-03-07)


Figures

Figures Figure 2-1 Typical commissioning network........................................................................................................ 2-2 Figure 3-1 Commissioning process......................................................................................................................3-2 Figure 5-1 U_creator_eng window.......................................................................................................................5-7 Figure 5-2 Add NE dialog box.............................................................................................................................5-7 Figure 5-3 Configuring information.....................................................................................................................5-8 Figure 6-1 BSC6900 log-in dialog box................................................................................................................6-2 Figure 7-1 Batch commands pane........................................................................................................................7-3 Figure 7-2 Setting the batch commands...............................................................................................................7-3 Figure 15-1 Setting Maintenance Mode for NE...............................................................................................15-12

Issue 05 (2011-03-07)


xi


Tables

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

Issue 05 (2011-03-07)


xiii


1 Changes in the BSC6900 GSM Commissioning Guide

1

Changes in the BSC6900 GSM Commissioning Guide

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

05 (2011-03-07) This is the fifth commercial release of V900R012C01. Compared with issue 04 (2010-11-30), this issue does not include any new topics. Compared with issue 04 (2010-11-30), this issue incorporates the following changes:

Content

Description

5.1 Verifying the OMU Locally

The procedure for verifying the OMU locally is changed.

6 Logging in to the BSC6900 Through the LMT

The description of performing subsequent local commissioning tasks with the debugging IP address is added.

Compared with issue 04 (2010-11-30), this issue does not exclude any topics.

04 (2010-11-30) This is the fourth commercial release of V900R012C01. Compared with issue 03 (2010-09-20), this issue does not include any new topics. Compared with issue 03 (2010-09-20), this issue incorporates the following changes:

Issue 05 (2011-03-07)

Content

Description


The description of debugging IP address is changed.

7 Updating the OMU Database

The procedure for running the MML script fileis is changed.


1-1



Content

Description

9.3 Resetting the BSC6900 Boards

The procedure for loading and activating the patch version is added.

9.4 Checking the Consistency of the Data and the Version

The procedure for checking the consistency of the data and the version is changed.


03 (2010-09-20) This is the third commercial release of V900R012C01. Compared with issue 02 (2010-06-21), this issue includes the following new topics: l

11.2.6 Verifying Lb Interface

l


Compared with issue 02 (2010-06-21), this issue incorporates the following changes:

Content

Description

3 Commissioning Process

The figure of commissioning process is optimized.


The procedure for verifying the OMU locally is changed.

5.2 Verifying the OMU Through USB Disk

The procedure for verifying the OMU through USB disk is changed.


The procedure for updating the OMU database is changed.

11.1.2 Verifying Interfaces Automatically

The procedure for verifying interfaces automatically is changed.

15.8 Setting Maintenance Mode for NE

The procedure for setting the maintenance mode for the NE is changed.


02 (2010-06-21) This is the second commercial release of V900R012C01. Compared with issue 01 (2010-04-10), this issue includes the following new topics: l

11.2.7 Verifying the Internal Interfaces

Compared with issue 01 (2010-04-10), this issue incorporates the following changes:

1-2


Issue 05 (2011-03-07)



Content

Description

16.1 Communication Ports Used by the BSC6900

The description of communication ports used by the BSC6900 is changed.


01 (2010-04-10) This is the first commercial release of V900R012C01. Compared with issue 04 (2010-01-30) of V900R011C00, this issue does not include any new topics. Compared with issue 04 (2010-01-30) of V900R011C00, this issue incorporates the following changes:

Content

Description

Creating Scheduled Tasks

The procedure for creating scheduled tasks is changed.

Compared with issue 04 (2010-01-30) of V900R011C00, this issue does not exclude any topics.

Issue 05 (2011-03-07)


1-3


2 Prerequisites for Commissioning

2

Prerequisites for Commissioning

Before the BSC6900 commissioning, the status of the equipment and the network to be commissioned must meet the conditions required. The software installation package, license, 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

BSC6900 hardware

The hardware is installed and passes the hardware installation inspection and power-on check.

OMU

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

LMT PC

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

Requirements for Commissioning the Network To ensure smooth verification of the Abis, Ater, A, and Gb interfaces, the network equipment in the commissioning network must meet the following requirements: l

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

l

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

l

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

Figure 2-1 shows a typical commissioning network.

Issue 05 (2011-03-07)


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

2-2

Scenario

Description

In BM/TC separated mode, with the TCS configured remotely

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, and provides PS service.

The BSC6900 is connected to the MGW or BTS

Two NEs in the same equipment room are connected directly.

Alarm box configured on BSC6900 side

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


Issue 05 (2011-03-07)



Requirements for Software and Data Files l

Software installation package 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 through the Huawei technical support engineer.

l

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

Issue 05 (2011-03-07)


2-3



3

Commissioning Process

The BSC6900 commissioning can be performed remotely or locally. Remote commissioning is performed by the remote engineer (technical owner of the BSC) and multiple BSCs can be commissioned simultaneously in the central equipment room. Local commissioning is performed by the site engineer (commissioning owner in the BSC equipment room) who connects a PC to the BSC and performs the commissioning through the LMT. There is also another commissioning mode: remote commissioning through local assistance, which is performed by both the remote engineer and the site engineer. Figure 3-1 shows the commissioning process.

Issue 05 (2011-03-07)


3-1



Figure 3-1 Commissioning process

NOTE

The remote engineer performs operations remotely, while the site engineer performs operations locally.

3-2


Issue 05 (2011-03-07)


4 Checking Operating Status of Hardware

4

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

Prerequisite The BSC6900 cabinet has passed the power-on check.

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

Then...

The cabinet is not powered on,

Go to step Step 2.

The cabinet is powered on,

Go to step Step 3.

Step 2 Power on the cabinet by referring to Powering On the Cabinet. Step 3 Check the power supply to the cabinet components, as listed in Table 4-1. Ensure that the hardware operates normally. Table 4-1 Checklist of the power supply to the cabinet components

Component

Normal LED Status

Board

The green RUN LED on the board panel flashes every other second.

Fan box

The green STATUS LED on the panel of the fan box flashes every other second after the subrack and independent fan subrack are powered on.

Power distribution monitoring board

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

Issue 05 (2011-03-07)


4-1

4 Checking Operating Status of Hardware


NOTE

If power failure occurs, handle the problem by referring to Handling power failures of internal cabinet components in Powering On the Cabinet.

----End

4-2


Issue 05 (2011-03-07)


5 Verifying the OMU

5

Verifying the OMU

About This Chapter This section descri bes how to verify the OMU to enable the normal communication between the LMT and the BSC6900. The OMU verification involves installing the OMU operating system and OMU application, checking the OMU operation status, and changing the external fixed IP address and external virtual IP address of the OMU on site.

Context 5.1 Verifying the OMU Locally applies to the scenario that the site engineer performs the commissioning without the involvement of a USB drive. 5.2 Verifying the OMU Through USB Disk applies to the scenario that a USB drive for commissioning is prepared by the remote engineer. In this mode, the site engineer plugs the USB drive for commissioning into the OMU to complete the installation of the operating system. The commission is performed through the collaboration between the remote engineer and site engineers.

Select a verification method according to the actual scenario. 1.

5.1 Verifying the OMU Locally This section describes how to verify the OMU locally to enable the normal communication between the LMT and the BSC6900. The OMU verifying involves checking the operation status of the OMU, checking the version of the OMU application, changing the external fixed IP address, and changing the external virtual IP address. If the BSC6900 is configured with the active and standby OMUs, verify the active OMU and the standby OMU respectively based on the procedure given in this section.

2.

5.2 Verifying the OMU Through USB Disk This section describes how to verify the OMU through a USB disk. In this scenario, the USB disk that is prepared in advance is plugged into the OMU at the site. Then, the OMU verification is performed through cooperation of the remote engineer.

Issue 05 (2011-03-07)


5-1


5 Verifying the OMU

5.1 Verifying the OMU Locally This section describes how to verify the OMU locally to enable the normal communication between the LMT and the BSC6900. The OMU verifying involves checking the operation status of the OMU, checking the version of the OMU application, changing the external fixed IP address, and changing the external virtual IP address. If the BSC6900 is configured with the active and standby OMUs, verify the active OMU and the standby OMU respectively based on the procedure given in this section.

Prerequisite l

The OMU application installation package that is consistent with the version used in the local office and the Records of OMU Software Installation Information are obtained.

l

The information designated by the operator, such as the IP add ress and OMU name, is obtained and recorded in the Configuration Information for Verifying OMU Locally.

l

The active workspace of the OMU is version_a by default.

l

For details about the IP address planning, see Planning of the OMU IP Addresses.

Context

Procedure Step 1 Set the link mode of the external OMU Ethernet adapter by referring to Setting the Link Mode of the External OMU Ethernet Adapter.

Step 2 Connect the PC to the ETH2 debugging port on the OMUa board by using an Ethernet cable. Step 3 Set the IP address of the PC to be on the same network segment with the ETH2 port. The initial IP address of the ETH2 port is 192.168.6.50 or 192.168.6.60, the subnet mask is 255.255.255.0.

Step 4 Log in to the OMU by referring to Logging In to the OMU. Step 5 Run the /etc/rc.d/omud status command to check the running status of the OMU process. If...

Then...

The information returned is running ,

1. Run the /etc/rc.d/omud stop command to stop the omud process. 2. Go to Step 6.

The information returned is unused,

Go to Step 6.

The information returned is No such file or directory,

Install the OMU application in the active workspace by referring to Installing the OMU Applications in the Active Workspace.

Step 6 Run the cd /mbsc/upgrade command to switch to the OMU installation directory, and then run the ls command to query the current version of the OMU application.

5-2


Issue 05 (2011-03-07)


5 Verifying the OMU

If...

Then...

The version of the OMU application is the same as that required by the operator,

Perform operations in Step 7 through Step 16. Then this task is complete.

The version of the OMU application is different from that required by the operator,

1. Uninstall the OMU application by referring to Uninstalling the OMU Applications. 2. Upload the OMU application installation package to the OMU by referring to Uploading the OMU Application Installation Package to the OMU. 3. Install the OMU application in the active workspace by referring to Installing the OMU Applications in the Active Workspace. 4. Perform operations in Step 7 through Step 10. 5. Perform operations in Step 14 through Step 16. Then this task is complete.

Step 7 Run the cd /mbsc/bam/version_a/bin/bam command to switch to the directory where the omutool program locates. NOTE

To view the help information of the omutool, run the ./omutool -h command.

Step 8 Change the external fixed IP address, subnet mask, and the gateway IP address according to the plan of the operator. Run the ./omutool extercard The external fixed IP address The subnet mask The gateway IP address command to change the external fixed IP address and the subnet mask. 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 NOTE

After the external fixed IP address is changed, the BSC6900 can be connected to the OM netw ork of the operator through the ETH0 or ETH1 port. In this case, the commissioning need not n ecessarily be performed in the BSC6900 equipment room and can be performed in a centralized manner.

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

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

Issue 05 (2011-03-07)


5-3


5 Verifying the OMU

If...

Then...

Any IP address is in the same network segment as the network of the operator, change the IP address.

l

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

l

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

NOTE If the network segment of the internal fixed IP address or that of the internal virtual IP address is changed, the Subnet No. must be changed when updating the OMU database. For details, see the "Follow-up procedure" in the 7 Updating the OMU Database. l

Run the ./omutool backupcard The IP address The subnet mask command to change the backup channel IP addresses of the active and standby OMUs and the subnet mask. For example, you can run the following command and then press Enter. ./omutool backupcard 192.168.3.60 255.255.255.0

l

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

All IP addresses are not in the same network segment as the network of the operator, change only the backup channel IP address of the backup OMU.

Run the ./omutool backupcard The IP address The subnet mask command to change the backup channel IP addresses of the active and standby OMUs and the subnet mask. For example, you can run the following command and then press Enter. ./omutool backupcard 192.168.3.60 255.255.255.0

Step 11 Run the ./omutool hostname OMU name command to change the name of the OMU. For example, you can run the following command and then press Enter to change the OMU name to omu_123: ./omutool hostname omu_123.

Step 12 Set the work mode of the OMU according to the number of OMUa boards that are configured. l

If only one OMUa board is configured, run the ./omutool dualmode single command to set the work mode to the single-server mode.

l

If two OMUa boards (active and standby OMUa boards) are configured, run the ./omutool dualmode dual command to set the work mode to the dual-server mode.

Step 13 Run the cd /mbsc/bam/common command to switch to the directory where the reg.ini file locates. 5-4


Issue 05 (2011-03-07)


5 Verifying the OMU

1.

Run the vi reg.ini command to open the reg.ini file. Press Insert.

2.

Set mlangflag to CHS or ENG by moving the cursor with arrow keys to change the language used in the OMU.

3.

Set runmode to or by moving the cursor with arrow keys to change the service mode of the OMU.

4.

Set officename by moving the cursor with arrow keys to change the name of the OMU.

5.

Press Esc, input :, and then input wq. Press Enter to change the reg.ini file. NOTE l

To set the preceding information, move the cursor to the beginning character of the information to be modified, press X to delete the existing information, then press A, and you can input the new information. After you modify an information item, press Esc and then move the cursor to modify another information item.

l

To quit without saving your modification, perform either of the following operations: l

Operation 1: Press Esc, type : and then q!. Press Enter.

l

Operation 2: Directly close the PuTTY window. If you perform this operation, a prompt is displayed when you edit the reg.ini file using the vi command next time. In this case, type D and then press Enter to open the reg.ini file.

NOTE

You can also copy the reg.ini to the local PC to change the previ ous information by using the psftp software. 1. Obtain the psftp Software and open it locally by double-clicking the application icon. 2. Input cd /mbsc/bam/common in the psftp command line window to switch to the directory where the reg.ini file locates. 3. Input get reg.ini in the psftp command line window to transfer the reg.ini file from the OMU to the directory where the psftp software locates. 4. Open the reg.ini file with notepadm, set mlangflag to CHS or ENG, set runmode to GO, and then set officename. 5. Input put reg.ini in the psftp command line window to upload the modified reg.ini file from the local PC to the OMU.

Step 14 Run the /etc/rc.d/omud start command to start the OMU application. Step 15 Run the ps -afx command to check the operating status of the OMU. You can infer that the OMU is in normal state if all OMU processes exist in the OMU active workspace directory/mbsc/bam/version_a/bin/bam/monitor.

Issue 05 (2011-03-07)

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, and debug_log

Standby OMU

software, ftp_server , sntp, omu_manager, and debug_log


5-5


5 Verifying the OMU

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 application by referring to Uninstalling the OMU Applications, and then install the OMU application in the active workspace again by referring to Installing the OMU Applications in the Active Workspace.

Step 16 Exit the OMU by referring to Logging Out of the OMU. ----End

5.2 Verifying the OMU Through USB Disk This section describes how to verify the OMU through a USB disk. In this scenario, the USB disk that is prepared in advance is plugged into the OMU at the site. Then, the OMU verification is performed through cooperation of t he remote engineer.

Prerequisite l

The preparations for installing software on site are complete. For details, see Preparations for Installing Software on Site.

l

The information planned by the operator, such as IP address and OMU name, is obtained and recorded in the Configuration Information for Preparing USB Disk for Installation.

l

The capacity of the USB disk is greater than or equal to 2G. If the BSC6900 works in the active/standby OMU mode, two USB disks are required.

l

A USB port is available on the PC, and the USB port is not restricted (such as CPM restriction).

l

A USB port is available on the OMUa board.

l

The OMU verification through a USB disk involves two st eps: preparing the USB disk and verifying the OMU after plugging the USB disk into the OMU .

l

The USB disk applies to only the Dopra Linux operating system.

l

This task takes preparing the USB disk in active/standby OMU mode as an example. Differences between the task in dual-OMU mode and that in single-OMU mode are specified.

Context

CAUTION

In the process of installing the OMU operating system through a USB disk, the OMU hard disk will be formatted and all the data on the OMU will get lost. Make sure you have backed up the OMU data before proceeding with the installation of the OMU operating system.

Procedure Step 1 Set the link mode of the external OMU Ethernet adapter by referring to Setting the Link Mode of the External OMU Ethernet Adapter. 5-6


Issue 05 (2011-03-07)


5 Verifying the OMU

Step 2 Preparing the USB disk 1.

Plug the USB disk into the USB port on the portable computer.

2.

Double-click U_creator_eng.exe to open the BSC6900 Dopra Linux tool package, as shown in Figure 5-1.

Figure 5-1 U_creator_eng window

3.

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

Issue 05 (2011-03-07)


5-7


5 Verifying the OMU

4.

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

5.

l

The NE name is used to identify NEs, and it is composed of only letters, 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 disks, it is recommended that you prepare the USB disks one by one, and make marks for the disks.

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.

Figure 5-3 Configuring information

5-8


Issue 05 (2011-03-07)


5 Verifying the OMU

NOTE l

All the manually configured items need to be entered.

l

If Install OMU? is not selected in Step 2.4, only the names of the active and standby OMUs and IP addresses are displayed in the Figure 5-3.

l

If a patch needs to be installed, select the patch package.

l

The downloaded patch package must be saved in the patch folder of the installation package.

l

Select the patch folder when selecting the patch package.

6.

Check that all the information is correct and click OK to start preparing the USB disk for the active OMU.

7.

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

If only one OMU is configured, the USB disk for the standby OMU need not be prepared.

Step 3 Verifying the OMU after plugging the USB disk into the OMU 1.

Insert the USB disk into any of the USB ports on the OMUa board panel.

2.

Remove and then install the OMUa board to reset it. For details, see Removing a Board and Inserting a Board.

3.

Check whether the OMU operating system is successfully installed through either of the following methods. l

Method 1: Wait for 5 to 10 minutes to view the status of the LEDs on t he OMUa board panel. NOTE

The state of the LEDs on the OMUa board panel can be: RUN LED flashes, ALM LED flashes, ACT LED flashes, and OFFLINE LED is off.

If...

Then...

All the following conditions are met:

The OMU operating system is installed successfully.

l

The RUN LED flashes.

l

The ALM LED is off.

The RUN LED is off or the ALM LED flashes,

l

If the OMU operating system fails to be installed, perform Step 3.4.

Method 2: Connect the display to the VGA port on the OMUa board panel. The OMU operating system is successfully installed if the following message is displayed: Please login from TTY2(Press ALT-F2).

l

Issue 05 (2011-03-07)

Method 3: Wait for 5 to 10 minutes. If you Logging In t o the OMU successfully, the OMU operating system is installed successfully.


5-9


5 Verifying the OMU

CAUTION

After the operating system installation is complete, the OMU verification is complete. Remove the USB disk from the OMU board panel. 4.

Check whether the configuration files and operating system installation script prepared during the step Preparing the USB disk are correct. l

If the configuration files or operating system installation script are not correct, prepare the USB disk again by referring to Preparing the USB disk .

l

If the configuration files and operating system installation script are correct, contact Huawei technical support by referring to Contact Huawei Customer Service Center. NOTE l

After the operating system installation is complete, the OMU verification is complete. Remove the USB disk from the OMU board panel.

l

After the OMU operating system is instal led successfully, you can log in to the OMU by referring to Logging In to the OMU.

----End

5-10


Issue 05 (2011-03-07)



6

Logging in to the BSC6900 Through the LMT This section describes how to log in to the BSC6900 through the LMT and enable the normal communication. LMT verification ensures the BSC6900 commissioning through the LMT.

Prerequisite l

The OMU has passed the commissioning.

l

The network connection between the LMT and the OMU is established. NOTE

In the case of the local OMU verification, field engineers can perform subsequent local commissioning tasks and then log in to the BSC6900 through the LMT to verify the connection between the OMU and the external network. In this case, field engineers need to type the IP address for OMU verification in the address bar of Internet Explorer (IE) to log in to the LMT for local commissioning.

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

WARNING

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

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

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

2.

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

Issue 05 (2011-03-07)


6-1



Step 2 Start the Internet Explorer, and then log in to the BSC6900 through the LMT. 1.

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

Figure 6-1 BSC6900 log-in dialog box

NOTE

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

2.

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

----End

6-2


Issue 05 (2011-03-07)



7

Updating the OMU Database

This describes how to update configuration data in the OMU database by running MML commands.

Prerequisite l

You have logged in to the BSC6900 through the LMT.

l

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

l

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

l

The active workspace of the OMU can be queried through the MML command LST OMUAREA. To view the directory structure of the OMU workspace, see Checking the Installation Directory of the OMU Applications. The following procedure assumes that the active workspace is version_a.

l

Run the MML command script through MML commands

Context

Procedure 1.

Run the MML command SET CFGDATAINEFFECTIVE repeatedly to set all the subracks to the ineffective mode.

2.

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

3.

Upload the MML command script to the /ftp folder in the OMU active workspace directory. The following procedure takes uploading the MML script BATCHFILE.txt saved in disk D to the OMU active workspace /mbsc/bam/version_a/ftp as an example to introduce the two methods. NOTE

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

– Through File Manager on the LMT (1) Start the File Manager by referring to File Manager. Issue 05 (2011-03-07)


7-1



(2) Choose Root > bam > version_a > ftp on the left pane. Click Upload on the right. A dialog box is displayed. Select BATCHFILE.txt saved in disk D, and then click Open to upload the file.

– Through Command Lines (1) On the local PC, choose Start > Run. Type cmd, and then click OK . (2) Input d:, and then press Enter to switch to disk D. (3) Input ftp IP address to try to connect to the OMU. Here, IP address is the IP address of the OMU. (4) Input the FTP user name and password. The connection between the OMU and the local FTP is set up after the authentication succeeds. NOTE

The FTP user name is always FtpUsr. The FTP password is set during the OMU application installation. For details, see Records of the OMU Application Installation Information.

(5) Input cd /mbsc/bam/version_a/ftp to switch to the OMU active workspace. (6) Input put BATCHFILE.txt to upload the file. (7) After the file is uploaded successfully, input quit to disconnect the FTP. 4.

Run the MML command RUN BATCHFILE to run the MML script file. It is recommended that you set Finish type to ALL_END_RETURN(Stop at end) , Result recording type to REC_ERR(Record errors), Source File Name to BATCHFILE.txt , and Result file name to RUN_BATCHFILE_RESULT.txt . NOTE

l

7-2

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 may be needed for executing a script with 100,000 commands.

l

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

Run the MML script through GUI 1.

Run the MML command SET CFGDATAINEFFECTIVE repeatedly to set all the subracks to the ineffective mode.

2.

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

3.

On the LMT, click the Batch tab to enter the Batch pane, as shown in Figure 7-1.


Issue 05 (2011-03-07)



Figure 7-1 Batch commands pane

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 in the Batch pane.

5.

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

Issue 05 (2011-03-07)


7-3



6.

In the Batch area, select All under the Execution Type area.

7.

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

8.

l

Click OK when the system prompts that the current configuration is in ineffective mode after you click Go. The execution of the script may take a long time in GUI mode. For example, 2-3 hours may be needed for executing a script with 4 MB.

l

If an Error dialog box showing Execution failed. Continue? is displayed during the execution of 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 according to the prompts, and then go to Step 4 to run the script again.

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, do as follows to ensure the normal communication between the OMU and the BSC6900. 1.

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

2.

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

For details about the planned internal IP address of the OMU, see Configuration Information for Verifying OMU Locally.

3.

7-4

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 BSC6900 so that it is consistent with the network segment of the planned internal IP address of the OMU.

Pull out and then reinsert the SCUa board in the MPS, and then reset the MPS. The new IP address of the BSC6900 host takes effect.


Issue 05 (2011-03-07)


8 Activating and Verifying the License

8

Activating and Verifying the License

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

Prerequisite l


l

The license is ready and the license check is passed.

Context The active workspace of the OMU can be queried through the MML command LST OMUAREA. To view the directory structure of the OMU workspace, see Checking the Installation Directory of the OMU Applications. The following procedure assumes that the active workspace is version_a.

Procedure Step 1 Run the MML command DLD LICENSE to download the License to the OMU active workspace directory/ftp/license, that is, /mbsc/bam/version_a/ftp/license.

Step 2 Run the MML command LST LICENSE and then set File Name to the name of the license file to be activated to query the detailed configuration information of the license file.

If...

Then...

The license is consistent with what you apply Go to step Step 3. for, The license is inconsistent with what you apply for,

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

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

Issue 05 (2011-03-07)


8-1

8 Activating and Verifying the License


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

8-2

l

If the configuration data of the license is incorrect, apply for a new license.

l

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


Issue 05 (2011-03-07)


9 Loading BSC6900 Board Software and Data Files

9

Loading BSC6900 BSC6900 Board Software and Data Files

About This Chapter This chapter describes how to load the BSC6900 board software and data files to enable the normal operation of the BSC6900.

Prerequisite l

The equipment verifying is complete.

l

The OMU database is updated .

Context The software of BSC6900 boards is generated automatically in the OMU active workspace directory/bin/fam when installing OMU applications. Assume that the active workspace is version_a, then the software is in /mbsc/bam/version_a/bin/fam. The software can be loaded directly. To make the configuration take effect, format the configuration data in the OMU database to generate a .DAT data file, and then reset the BSC6900. 1.

9.1 Generating the Data File for the Loading This section describes how to generate the BSC6900 data file, which can be loaded, by using the MML command data scripts.

2.

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

3.

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

4.

9.4 Checking the Consistency of the Data and the Version This section describes how to check whether the board configuration and the software version of the BSC6900 are consistent with the information in the OMU.

Issue 05 (2011-03-07)


9-1



9.1 Generating the Data File for the Loading This section describes how to generate the BSC6900 data file, which can be loaded, by using the MML command data scripts.

Prerequisite l


Context The data file is generated in the OMU active workspace directory/bin/fam. Assume that the active workspace is version_a, then the data file is in /mbsc/bam/version_a/bin/fam. The file name is in ABCXXYYZZ .DAT format, such as XPUa000200.DAT. Table 9-1 lists the detailed ABCXXYYZZ .DAT information. Table 9-1 Name of the loading file

Parameter

Indication

ABC

Board name

XX

Subrack number

YY

Slot number

ZZ

Subsystem number

The active workspace of the OMU can be queried through the MML command LST OMUAREA. To view the directory structure of the OMU workspace, see Checking the Installation Directory of the OMU Applications. The following procedure assumes that the active workspace is version_a.

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

After the command is executed successfully, the .DAT file is generated in the OM U active workspace directory /bin/fam, that is, /mbsc/bam/version_a/bin/fam. ----End

9.2 Setting the Loading Mode M ode This section describes how to set the loading modes of all the board subsystems before resetting BSC6900 boards. 9-2


Issue 05 (2011-03-07)



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

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

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

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

Prerequisite l

The data file for the Loading is generated.

l


l

All the subracks are powered on.

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

Work Mode

Resetting Time

Sequence for Resetting Subracks

BM/TC combined, or A over IP

The resetting time is less than nine minutes in the maximum configuration.

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

BM/TC separate

The resetting time is less than fifteen minutes in the maximum configuration.

The subracks should be reset in the following sequence: remote extension TCS-> remote main TCS -> EPS -> MPS.

You can run the MML command LST SUBRACK and then check the parameters Subrack Type 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 the subrack to be reset. A confirmation dialog box is displayed, asking you whether to proceed. Issue 05 (2011-03-07)


9-3



Click OK . The boards in the subrack automatically load the BSC6900 board software and data files from the OMU.

Step 2 Repeat step Step 1 to reset all the subracks of the BSC6900. NOTE

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

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

Step 4 Observe the device panel to check whether all the boards are in normal state. If...

Then...

The device panel shows that all the boards End this task. are in normal state, The device panel shows that some boards are in normal state,

Rectify the faults according to the prompt. For details, see 15.5 Board Data Loading Failure.

Step 5 Optional: If a patch version is installed, run the MML command INS PATCH to load and activate the patch version. NOTE

Loading and activating the patch version is needed only when a patch version is installed on a newly deployed site for the first time.

----End

9.4 Checking the Consistency of the Data and the Version This section describes how to check whether the board configuration and the software version of the BSC6900 are consistent with the i nformation in the OMU.

Prerequisite l

All the subracks and boards are running normally.

l


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

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

9-4


Issue 05 (2011-03-07)



NOTE

If the board configuration or software version of the BSC6900 is inconsistent with the information in the OMU, run the MML command RST SUBRACK to reset the subrack with incorrect data or version.

----End

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

Issue 05 (2011-03-07)


9-5


10 Connecting the BSC6900 to the M2000

10

Connecting the BSC6900 to the M2000

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

Prerequisite l

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

l

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

l

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

l

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

Context

Procedure Step 1 Connect the BSC6900 to the OM network. 1.

Connect one end of a straight-through Ethernet cable to the ETHO port on the OMU board, and connect one end of another straight-through Ethernet cable to the ETH1 port on the OMU board.

2.

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

Step 2 Configure the IP route from the BSC6900 to the M2000. 1.

Issue 05 (2011-03-07)

Run the MML command LST OMUIPRT to check whether the route to the M2000 is configured on the OMU. l

If the values of Destination Network Address, Destination Address Mask , and Forward Route Address in the result are consistent with the planned addresses, you can infer that the BSC6900 already has a route to the M2000. Go to step Step 2.3.

l

If the Destination Network Address, Destination Address Mask , and Forward Route Address in the result are not consistent with the planned addresses, you can infer that the BSC6900 does not have a route to the M2000. Go to step Step 2.2.


10-1

10 Connecting the BSC6900 to the M2000


2.

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

3.

Verify the configuration of the route from the BSC6900 to the router. Logging in to the OMU remotely, run the ping command to check whether the network connectivity between the BSC6900 and the router is available. If the OMU can receive a response packet from the router, go to step Step 2.4. Otherwise, check whether the OMU and the router are properly connected.

4.

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

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

CAUTION l

If a firewall exists between BSC6900 and M2000, ensure that the communication ports connecting the BSC6900 and M2000.

l

For details on the ports connecting the BSC6900 and M2000, see 16.1 Communication Ports Used by the BSC6900.

----End

Example Table 10-1 describes how to configure the route between the BSC6900 and the M2000. Table 10-1 Configuring the route from the BSC6900 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.

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

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 to check whether the network between the BSC6900 and the router is operational. 4. Run the ping 10.11.100.23 command to check whether the network between the BSC6900 and the M2000 is operational.

10-2


Issue 05 (2011-03-07)


11 Verifying Interfaces

11

Verifying Interfaces

About This Chapter This section describes how to verify interfaces. The interfaces to be verified are Abis, A, Gb, Ater, Pb, and Lb interfaces. The Ater interface verification is mandatory in BM/TC separated mode; the Pb interface verification is mandatory when the external PCU is used on the BSC6900; the Lb interface verification is mandatory when the external SMLC is used on the BSC6900.

Context Select a verif ication method according to the actual scenario. 11.1 Verifying Interfaces Through M2000 This section describes how to verify interfaces through the maintenance mode and the NE health check function of the M2000. 11.2 Verifying Interfaces Through LMT This chapter describes how to verify interfaces on the BSC6900 through MML commands or GUI on the LMT. The interfaces to be verified are Abis, A, Gb, Ater, Pb, and Lb interfaces. The Ater interface verification is mandatory in BM/TC separated mode; the Pb interface verification is mandatory when the external PCU is used on the BSC6900; the Lb interface verification is mandatory when the external SMLC is used on the B SC6900.

Issue 05 (2011-03-07)


11-1



11.1 Verifying Interfaces Through M2000 This section describes how to verify interfaces through the maintenance mode and the NE health check function of the M2000. 11.1.1 Setting Maintenance Mode of NE to Install During the commissioning, the NE may report many alarms that require no attention. You can shield these alarms by setting the maintenance mode of the NE to be in Install mode. 11.1.2 Verifying Interfaces Automatically This section describes how to verify the BSC6900 interfaces automatically through NE health check on the M2000. 11.1.3 Setting the Maintenance Mode of the NE to Normal After the End Time of the maintenance mode, the NE enters the normal mode automatically. In addition, you can set the UE mode to Normal manually.

11.1.1 Setting Maintenance Mode of NE to Install During the commissioning, the NE may report many alarms that require no attention. You can shield these alarms by setting the maintenance mode of the NE to be in Install mode.

Prerequisite l

The BSC6900 and the peer equipment are physically connected, and the hardware installation acceptance is passed.

l

All the subracks of the BSC6900 are running normally.

l

The BSC6900 is connected to the M2000 (for details, see 10 Connecting the BSC6900 to the M2000).

l

Currently, four maintenance modes are provided on the M2000: Install, Expand , Upgrade, and Testing. In the BSC6900 commissioning scenario, set the maintenance mode to Install.

l

The maintenance modes are effective for the UE during Start Time and End Time. Before Start Time and after End Time, NEs are in the Normal mode. When NEs are in the Normal mode, alarms are reported normally.

l

When the NE is restored to the Normal mode, the alarms that are not cleared when the NE is in the Install mode are reported to the M2000 as common alarms.

Context

Procedure Step 1 Set the maintenance mode of the NE to Install on the M2000 client. For details, see 15.8 Setting Maintenance Mode for NE. ----End

11.1.2 Verifying Interfaces Automatically This section describes how to verify the BSC6900 interfaces automatically through NE health check on the M2000. 11-2


Issue 05 (2011-03-07)



Prerequisite l


l


l

The BSC6900 is connected to the M2000 (see 10 Connecting the BSC6900 to the M2000 for details).

Context The Lb interface and the internal interface should be verified through MML commands or GUI on the LMT, see 11.2.6 Verifying Lb Interface and 11.2.7 Verifying the Internal Interfaces for details.

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

On the M2000 client, choose Maintenance > NE Health Check .

2.

Click Scenario Management on the displayed tab page.

3.

Click New in the displayed dialog box.

4.

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

The scenario name must be different from existing scenario names.

5.

Click the type of the NE for health check in NE Types, that is BSC6900 GSM.

6.

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

7.

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

Step 2 Create the NE health check task. 1.

On the NE Health Check tab page, click New. The Create Task dialog box is displayed.

2.

Select the application scenario corresponding to the task that is currently created from the Scenario drop-down list. The Name text box is automatically filled in with the text consisting of the application scenario and the specific time (the time is accurate to the second) on which the task is created.

3.

Select the NE for health check in under Select NE.

4.

Select the option to kick off the task in under Time Setting. The options are as follows:

Operation Mode

Description

Instant

Click Next. The Time Setting dialog box is displayed. Click Finish. NOTE The setting of Time Setting is not required during commissioning.

Issue 05 (2011-03-07)


11-3



Operation Mode

Description

Scheduled

Set the time for kicking off the task in the Scheduled spin box. Click Next. Set Health Check Period in the displayed dialog box, and then click Finish.

Periodic

Click Next. Set Start Time, Period, and Run Times, and then click Finish.

NOTE

The executed health check tasks are listed under the Finished Tasks node on the navigation tree on the left of the NE Health Check tab page.

Step 3 View the result of the NE health check. 1.

Under the Finished Tasks node of the navigation tree, click the executed task. Right-click the corresponding task on the right and then click View Report from the shortcut menu.

2.

In the displayed Health Check Report dialog box, click the HTML Format tab or DOC Format tab to view the report.

If...

Then...

You selected the HTML Format,

Select the report from the report list, and then view the report in one of the following ways:

You selected DOC Format,

l

Click Open to directly open the report in HTML format.

l

Click Save As, and then select the path for saving the report in the displayed Save dialog box to save the report in HTML format.

Click Save As, and then select the path for saving the report in the displayed Save dialog box to save the report in Word format.

NOTE

The health check report is 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 by referring to the health check report.

----End

11.1.3 Setting the Maintenance Mode of the NE to Normal After the End Time of the maintenance mode, the NE enters the normal mode automatically. In addition, you can set the UE mode to Normal manually.

11-4


Issue 05 (2011-03-07)



Prerequisite l

The BSC6900 is connected to the M2000 (see 10 Connecting the BSC6900 to the M2000 for details).

l

Before verifying interfaces, set the maintenance mode for the NE by referring to 11.1.1 Setting Maintenance Mode of NE to Install.

l

The BSC6900 has passed the commissioning.

Procedure Step 1 Set the maintenance mode of the NE to Normal on the M2000 client. For details, see 15.8 Setting Maintenance Mode for NE. ----End

11.2 Verifying Interfaces Through LMT This chapter describes how to verify interfaces o n the BSC6900 through MML commands or GUI on the LMT. The interfaces to be verified are Abis, A, Gb, Ater, Pb, and Lb interfaces. The Ater interface verification is mandatory in BM/TC separated mode; the Pb interface verification is mandatory when the external PCU is used on the BSC6900; the Lb interface verification is mandatory when the external SMLC is used on the BSC6900.

Context During the interface verification, you can run the LST command to view the configuration information. For example, before running the MML command DSP ADJNODE, you can run the MML command LST ADJNODE to check the parameter Adjacent Node ID. 11.2.1 Verifying the Abis Interface This section describes how to verify the control plane and the user plane of the Abis interface. The Abis interface verification varies according to the transmission mode over the Abis interface. 11.2.2 Verifying the A Interface This section describes how to verify the control plane and the user plane of the A interface. The A interface verification varies according to the transmission mode of the A interface. 11.2.3 Verifying the Gb Interface This section describes how to verify the Gb interface. The Gb interface verification varies according to the transmission mode over the Gb interface. 11.2.4 Verifying the Ater Interface This section describes how to verify the Ater interface when the BSC6900 is in BM/TC separated mode. 11.2.5 Verifying the Pb Interface If the BSC6900 is configured with an external PCU, Pb interface verification is needed. 11.2.6 Verifying Lb Interface This section describes how to verify the L b interface. Both E1/T1 transmission and FE/GE transmission can be applied on the Lb interface. When E1/T1 transmission is applied, the data link layer adopts TDM transmission. When FE/GE transmission is applied, the data link layer adopts IP transmission. 11.2.7 Verifying the Internal Interfaces Issue 05 (2011-03-07)


11-5



This describes how to verify the link status of the ports on the TNUa and SCUa boards.

11.2.1 Verifying the Abis Interface This section describes how to verify the control plane and the user plane of the Abis interface. The Abis interface verification varies according to the transmission mode over the Abis interface.

Prerequisite l

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

l

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

l


l


Context For the commissioning of the base station, see the commissioning guide of the base station. The following takes one base station as an example to describe the commissioning process on the Abis interface. If multiple base stations are connected, repeat the operations. There are two ways to verify the Abis interface (Abis over TDM): through GUI or through MML. You can choose either way according to your convenience.

Procedure l

To verify the Abis interface (Abis over TDM) through GUI, see Verifying the Abis Interface (Abis over TDM) Through GUI.

l

Verifying the Abis interface (Abis over TDM) through MML 1.

Run the MML command DSP LAPDLNK to check whether the Link Access Protocol on the D channel (LAPD) link on the Abis interface is normal. Expected result: The value of UsageStatus is Normal. If the status of LAPD links on the Abis interface is abnormal, check the transmission link by referring to 15.1 Checking the Transmission Link .

2.

Run the MML command DSP ABISTS to query the timeslot status of the Abis interface. Expected result: The State of many timeslots is Idle, and there is no timeslot with the State of Failure. If the status of timeslots on the Abis interface is abnormal, check the transmission link by referring to 15.1 Checking the Transmission Link . NOTE

To query the Subrack No., Slot No., and Port No. of the timeslots to be verified, run the MML command LST BTSCONNECT.

3.

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

11-6


Issue 05 (2011-03-07)



If the value of Cell Initialized is No, see ALM-21801 GSM Cell out of Service for troubleshooting; if the value of Cell Initialized is Yes but the value of Channel Fault is Yes, check the alarms related to the TRX and rectify the fault according to the alarm handling suggestion. l

Verifying the Abis interface (Abis over IP) 1.

Run the MML command DSP LAPDLNK to check whether the LAPD link on the Abis interface is normal. Expected result: The value of UsageStatus is Normal. If the status of LAPD links on the Abis interface is abnormal, check the transmission link by referring to 15.1 Checking the Transmission Link .

2.

Run the MML command DSP ADJNODE to query the status of the adjacent node. Expected result: The values of available bandwidth are not all 0. If the values of available bandwidth are all 0, see EVT-22918 Change of Transport Resource State for Adjacent Node User Plane for troubleshooting.

3.

Run the MML command DSP IPPATH to query the status of the IP path on the Abis interface. Expected result: The value of Operation state is Available. If the value of Operation state is Unavailable, see 15.4 IP Connection Setup Failure 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 Channel Fault is No. If the value of Cell Initialized is No, see ALM-21801 GSM Cell out of Service for troubleshooting; if the value of Cell Initialized is Yes but the value of Channel Fault is Yes, check the alarms related to the TRX and rectify the fault according to the alarm handling suggestion.

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. If the status of LAPD links on the Abis interface is abnormal, check the transmission link by referring to 15.1 Checking the Transmission Link .

2.

Run the MML command DSP HDLCLNK to query the status of the HDLC link. Expected result: The value of operation state is Available and the value of Available Tx Bandwidth or Available Rx Bandwidth is not 0. If the status of LAPD links on the Abis interface is abnormal, check the transmission link by referring to 15.1 Checking the Transmission Link . NOTE

To query the number of the HDLC link to be verified, run the MML command LST BTSABISHDLCPATH.

3. Issue 05 (2011-03-07)

Run the MML command DSP BTSSTAT to query the status of the cells and channels. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

11-7



Expected result: The value of Cell Initialized is Yes and the value of Channel Fault is No. If the value of Cell Initialized is No, see ALM-21801 GSM Cell out of Service for troubleshooting; if the value of Cell Initialized is Yes but the value of Channel Fault is Yes, check the alarms related to the TRX and rectify the fault according to the alarm handling suggestion. ----End

11.2.2 Verifying the A Interface This section describes how to verify the control plane and the user plane of the A interface. The A interface verification varies according to the transmission mode of the A interface.

Prerequisite l

The BSC6900 and the MSC are physically connected.

l

The MSC used to verify the A interface operates normally.

l

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

l


l


Context There are two ways to verify the A interface (A over TDM): through GUI or through MML. You can choose either way according to your convenience.

Procedure l

To verify the A interface (A over TDM) through GUI, see Verifying the A Interface (A over TDM) Through GUI.

l

Verifying the A interface (A over TDM) through MML 1.

Run the MML command DSP MTP2LNK to query the status of the Message Transfer Part Level 2 (MTP2) signaling link. Expected result: The value of Link State is IN SERVICE. If the value of Link State is OUT OF SERVICE, check the transmission links by referring to 15.1 Checking the Transmission Link .

2.

Run the MML command DSP MTP3LNK to query the status of the Message Transfer Part Level 3 (MTP3) signaling link. Expected result: The value of Operation state is Available. If the value of Operation state is Unavailable, see ALM-21506 MTP3 Signaling Link Faulty for troubleshooting.

3.

Run the MML command DSP SSN to query the status of the SCCP SSN. Expected result: The value of SSN state is Allowed. If the value of SSN state is Prohibited, see ALM-21521 SCCP Subsystem Prohibited for troubleshooting.

11-8


Issue 05 (2011-03-07)



4.

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

5.

Run the MML command DSP ACIC to query the status of A interface circuits. Expected result: The CIC State of many CICs is Idle, and there is no CIC with the CIC State of Failure. If the value of CIC State is Failure, check the transmission links by referring to 15.1 Checking the Transmission Link . NOTE

To query the OPC Index and DPC Group Index of the E1/T1 to be verified on the A interface, run the MML command LST AE1T1. l

Verifying the A interface (A over IP) 1.

Run the MML command DSP SCTPLNK to query the status of the Stream Control Transmission Protocol (SCTP) link. Expected result: The value of SCTP link Operation state is Normal. If the value of Operation state is Unavailable, check the transmission links by referring to 15.1 Checking the Transmission Link . NOTE

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

2.

Run the MML command DSP M3LNK to query the status of the MTP3 User Adaption Layer (M3UA) signaling link. Expected result: The value of Operation state is Activated state. If the value of Operation state is not normal, see ALM-21506 MTP3 Signaling Link Faulty for troubleshooting.

3.

Run the MML command DSP SSN to query the status of the SCCP SSN. Expected result: The value of SSN state is Allowed. If the value of SSN state is Prohibited, see ALM-21521 SCCP Subsystem Prohibited for troubleshooting.

4.

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

5.

Run the MML command DSP ADJNODE to query the status of the adjacent node. Expected result: The values of available bandwidth are not all 0.

Issue 05 (2011-03-07)


11-9



If the values of available bandwidth are all 0, see EVT-22918 Change of Transport Resource State for Adjacent Node User Plane for troubleshooting. 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 15.4 IP Connection Setup Failure for troubleshooting.

----End

11.2.3 Verifying the Gb Interface This section describes how to verify the Gb interface. The Gb interface verification varies according to the transmission mode over the Gb interface.

Prerequisite l

The BSC6900 and the SGSN are physically connected, and the hardware installation acceptance is passed.

l

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

l


l


l

Verifying the Gb interface links (Gb over FR)

Procedure 1.

Run the MML command DSP BC to query the status of the Bearer Channel (BC) to be verified. Expected result: The value of BC Service State is available. If the value of BC Administration State is Blocked, run the MML command UBL BC to unblock the BC, and then run the MML command DSP BC to check whether the BC status is normal. If the status remains abnormal, check the transmission links by referring to 15.1 Checking the Transmission Link .

2.

Run the MML command DSP NSVC to query the status of the Network Service Virtual Connection (NSVC) to be verified. Expected result: The value of NSVC Service State is Active Unblock . If the value of Service State is not normal, see the "Follow-up procedure" for troubleshooting.

3.

Run the MML command DSP SIGBVC to query the SIG BSSGP Virtual Connection (SIGBVC) status of the Network Service Entity (NSE) to be verified. Expected result: The value of SIG BVC State is Normal . If the value of SIG BVC State is Fault, the SGSN may be configured with an NSE that has a different NSE ID. NOTE

To query the configuration of the NSE to be verified, run the MML command LST NSE.

4.

11-10

Run the MML command DSP PTPBVC to query the status of the PTP BSSGP Virtual Connection (PTPBVC) of the NSE to be verified. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 05 (2011-03-07)



Expected result: The value of Service State is Normal. If the value of Service State is not normal, see the Postrequisites below for troubleshooting. l

Verifying the Gb interface links (Gb over IP) 1.

Run the MML command DSP NSVL to query the status of the Network Service Virtual Link (NSVL) to be verified. Expected result: The value of NSVL State is Normal. If the value of NSVL State is Fault, check the transmission links by referring to 15.1 Checking the Transmission Link . NOTE

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

2.

Run the MML command DSP GBIPROUTE to query the status of the IP connection to be verified on the Gb interface. Expected result: The value of State is Normal . If the value of State is Faulty, run the MML command DSP IPRT to check whether the route configuration on the Gb interface is correct.

3.

Run the MML command DSP SIGBVC to query the SIGBVC status of the NSE to be verified. Expected result: The value of SIG BVC State is Normal . If the value of SIG BVC State is Fault, the SGSN may be configured with an NSE that has a different NSE ID. NOTE

To query the configuration of the NSE to be verified, run the MML command LST NSE.

4.

Run the MML command DSP PTPBVC to query the PTPBVC status of the NSE to be verified. Expected result: The value of Service State is Normal. If the value of Service State is not normal, see the Postrequisites below for troubleshooting.

----End

Follow-up Procedure Handling Suggestions to Exceptional NSVC Status l

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

l

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

Issue 05 (2011-03-07)

Run the MML command UBL NSVC to unblock the BSC6900. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

11-11



2.

l

Run the MML command DSP NSVC to query the status of the NSVC. If the value of NSVC Service State is still Active Block , you can infer that the NSVC is blocked by the SGSN.

If the value of NSVC Service State is Deactive Block , the possible causes are as follows:

– The NSVC ID and NSE ID of the NSVC on the BSC6900 are inconsistent with that on the SGSN.

– The NSVC configured on the same BC at the SGSN is not the required one. Handling Suggestions to Exceptional PTPBVC Service Status

1.

If the value of PTPBVC Manage State is Block , run the MML command UBL PTPBVC to unblock the PTPBVC, and then run the MML command DSP PTPBVC to query the status of the PTPBVC. If the status remains abnormal, go to step 2.

2.

Run the MML command RST PTPBVC to reset the PTPBVC, and then run the MML command DSP PTPBVC to query the status of the PTPBVC. If the status remains abnormal, go to step 3.

3.

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

4.

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

11.2.4 Verifying the Ater Interface This section describes how to verify the Ater interface when the BSC6900 is in BM/TC separated mode.

Prerequisite l

The MPS/EPS and the TCS are physically connected.

l

The data configuration on the Ater interface is complete.

l

The TCS is loaded and started.

l


Context There are two ways to verify the Ater interface: through GUI or through MML. You can choose either way according to your convenience.

Procedure l

To verify the Ater interface through GUI, see Verifying the Ater Interface Through GUI.

l

Verifying the Ater Interface through MML 1.

Run the MML command DSP ATERTS to query the status of timeslots on the Ater interface. Expected result: The State of many timeslots is Idle, and there is no timeslot with the State of Failure.

11-12


Issue 05 (2011-03-07)



If the State of a timeslot is Failure, check the transmission links by referring to 15.1 Checking the Transmission Link . NOTE

To query the Ater connection path index and ID of BSC in TC Pool of the E1/T1 to be verified on the Ater interface, run the MML command LST ATERE1T1 .

2.

Optional: If the TCS is configured remotely, run the MML command DSP ATERSL to query whether the Ater signaling link is normal.

Expected result: The value of UsageStatus is Normal. If the value of UsageStatus is Faulty, check the transmission links by referring to 15.1 Checking the Transmission Link . ----End

11.2.5 Verifying the Pb Interface If the BSC6900 is configured with an external PCU, Pb interface verification is needed.

Prerequisite l

The PCU used to verify the Pb interface operates normally.

l

The BSC6900 and the PCU are physically connected, and the hardware installation acceptance is passed.

l


l


Procedure Step 1 Run the MML command DSP LAPDLNK to check whether the LAPD link on the Pb interface is normal. Expected result: The value of UsageStatus is Normal. If the status of LAPD links on the Pb interface is abnormal, check the transmission link by referring to 15.1 Checking the Transmission Link .

Step 2 Run the MML command DSP PBCIC to query the status of the circuit on the Pb interface. Expected result: The status of many circuit identity codes (CICs) is Idle, and there is no CIC with the status of Failure. If the status of a CIC is Failure, check the transmission links by referring to 15.1 Checking the Transmission Link . NOTE

To query the E1/T1 configuration information to be verified on the Pb interface, run the MML command LST PBE1T1.

----End

11.2.6 Verifying Lb Interface This section describes how to verify the Lb interface. Both E1/T1 transmission and FE/GE transmission can be applied on the Lb interface. When E1/T1 transmission is applied, the data Issue 05 (2011-03-07)


11-13



link layer adopts TDM transmission. When FE/GE transmission is applied, the data link layer adopts IP transmission.

Prerequisite l

The BSC and the Serving Mobile Location Center (SMLC) are physically connected.

l

The SMLC that is used to verify the Lb interface operates normally.

l


l


Context There is no dedicated interface board for the Lb interface. The data link layer of the Lb interface can be carried on the Abis interface board, A interface board, or Ater interface board.

Procedure l

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

l

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

l

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

----End

11.2.7 Verifying the Internal Interfaces This describes how to verify the link status of the ports on the TNUa and SCUa boards.

Prerequisite l

The inter-TNUa cables and inter-SCUa cables of the BSC6900 are installed.

l


l


Procedure Step 1 Run the MML command DSP LINKBTNUTNU to query the link status of the ports on the TNUa boards. Expected result: The value of Link Status is Normal. If the value of Link Status is Failure, re-install the inter-TNUa cables as required in the returned result by referring to Installing the Inter-TNUa Cables.

Step 2 Run the MML command DSP PANELPORT to query the link status of the ports on the SCUa boards. Expected result: The actual link status of the ports on the SCUa boards are displayed in the returned result. 11-14


Issue 05 (2011-03-07)



If the link status in the returned result does not meet the installation requirements, re-install the inter-SCUa cables by referring to Installing the Inter-SCUa Cables Between Different Subracks. ----End

Issue 05 (2011-03-07)


11-15


12 Handling the Alarms Generated During the Commissioning

12

Handling the Alarms Generated During the Commissioning This chapter describes how to handle the alarms generated during the commissioning, thus preventing the alarms from from affecting the verification verification of services. services.

Prerequisite l

The communication between the BSC6900 and the OMU is normal.

l


Procedure Step 1 Click the Alarm on the LMT main page. The Alarm tab page is displayed. Step 2 Check whether alarms are listed on the Fault tab page. If...

Then...

No alarm is listed,

End this task.

One or more alarms are listed,

Go to step Step 3.

Step 3 Double-click the alarm to be handled in the fault tab page. The Detail dialog box is displayed. Step 4 Click Solution.... The LMT Online Help interface is displayed. Step 5 Follow the suggestions to handle the alarm. Step 6 Repeat Step 3 to Step 5 to handle other alarms. ----End

Issue 05 (2011-03-07)


12-1


13 Verifying the GSM Services

13

Verifying the GSM Services

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

Prerequisite l

The verification over the Abis, A, Gb, Ater, Pb, and Lb interfaces is successful. The verification over Ater interface is mandatory only in BM/TC separated mode. The verification over Pb interface is mandatory only if the BSC6900 is configured with an external PCU. The verification over Lb interface is mandatory only if the BSC6900 is configur ed ed with an external SMLC.

l

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

l


Procedure Step 1 Table 13-1 lists the procedure for verifying the basic services by testing the MS in the BTS cells. Table 13-1 Performing dialing tests on the basic services

Issue 05 (2011-03-07)

Basic Services

Procedure for Conducting the Dialing Test

Expected Result

Speech service

Make 20 calls from an MS to a fixed-line phone and hold on each call for 60 seconds.

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

Make 20 calls from a fixed-line phone to an MS and hold on each each call for 60 seconds.



13-1


13 Verifying the GSM Services

Basic Services

Data service


Expected Result

Make 20 calls from an MS to another MS and hold on each call for 60 seconds.


Send a fax from an MS to an electrograph. Send a fax from an electrograph to an MS.

Faxes are sent and received normally.

Test the General Packet Radio Service (GPRS) or Enhanced Data Rate for GSM Evolution (EDGE) function on the MS.

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

NOTE

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

Step 2 Table 13-2 lists the procedure for verifying the feature services by testing the MS in the BTS cells. Table 13-2 Performing dialing tests on the feature services

Feature Services


Expected Result

Inter-RAT handover

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

The connection success rate is higher than 90%. The voice is clear and without loud noise.

Location service

Make a call from the MS and hold on the call. Then, locate the MS.

The location of the MS conforms to the precision requirements.

Adaptive Multi Rate (AMR) service

Make 50 calls from an MS to a fixed-line phone and select voice version to AMR.

The connection success rate is higher than 90%. The voice is clear and without loud noise.

----End

13-2


Issue 05 (2011-03-07)



14

Verifying Network Reliability

The network reliability is verified by alarm checks and dialing tests after the active/standby switchover of boards.

Prerequisite l

The standby board for the switchover operates normally.

l


l


l

The alarms generated before the switchover have been cleared.

Procedure Step 1 Switch over the active/standby boards. For details, see Switching Over the BSC Boards. Step 2 Check and handle the alarms generated during the active/standby switchover. For details, see 12 Handling the Alarms Generated During the Commissioning.

Step 3 Use an MS in a cell under the BTS to perform basic services and verify the services. For details, see Table 14-1. Table 14-1 Performing dialing tests on the basic services

Issue 05 (2011-03-07)

Basic Services


Expected Result

Speech service

Make 20 calls from an MS to a fixed-line phone and hold on each call for 60 seconds.



14-1



Basic Services

Data service


Expected Result

Make 20 calls from a fixed-line phone to an MS and hold on each call for 60 seconds.


Make 20 calls from an MS to another MS and hold on each call for 60 seconds.


Send a fax from an MS to an electrograph. Send a fax from an electrograph to an MS.

Faxes are sent and received normally.

Test the General Packet Radio Service (GPRS) or Enhanced Data Rate for GSM Evolution (EDGE) function on the MS.

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

----End

14-2


Issue 05 (2011-03-07)


15 FAQ

15

FAQ

About This Chapter This chapter describes how to handle the common problems encountered during the commissioning. 15.1 Checking the Transmission Link This section describes how to verify that the terrestrial transmission links of the BSC6900 are functional. The verification covers E1/T1 port, FE/GE port, optical port, and upper-layer link. 15.2 Unavailable E1/T1 Port This section describes how to handle the problem that the E1/T1 port is unavailable. 15.3 Unavailable FE/GE Port This section describes how to handle the pr oblem that the FE/GE port is unavailable. 15.4 IP Connection Setup Failure This section describes how to handle the f ailures during IP connection setup. 15.5 Board Data Loading Failure This section describes how to handle the failures that occur during data loading to the BSC6900 board. 15.6 Performing the Loopback Test on the E1/T1 Port This section describes how to perform the loopback test to check whether the E1/T1 port is functional. 15.7 Performing the Loopback Test on the Optical Port This section describes how to perform the group loopback test to check whether the optical port is functional. 15.8 Setting Maintenance Mode for NE

Issue 05 (2011-03-07)


15-1


15 FAQ

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

Prerequisite l


l


l

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

Procedure

Table 15-1 Methods for checking the status of transmission link in different transmission modes

If the transmission on the interface is over...

Then...

IP

1. If the channelized STM-1 transmission is used on the interface, check the status of the optical port.

PPP/MLPPP transmission mode

2. Check the status of the E1/T1 port. 3. Check the status of the upperlayer link. l

For the PPP transmission mode, run the MML command DSP PPPLNK to check the status of the PPP link.

l

For the MLPPP transmission mode, run the MML command DSP MPGRP to check the status of the MLPPP group. NOTE If the upper-layer link is not functional, run the MML command LST PPPLNK /LST MPGRP accordingly to check whether the data configuration on the interface is correct.

TD M

15-2

IP over Ethernet transmission mode

Check the status of the FE/GE port.

E1/T1 transmission mode

Check the status of the E1/T1 port.


Issue 05 (2011-03-07)


15 FAQ

If the transmission on the interface is over... Channelized STM-1 transmission mode

l

Then... Check the status of the optical port.

HDLC


FR


Checking the status of the E1/T1 port 1.

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

l

Checking the status of the FE/GE port 1.

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

– The value of Link Availability Status is Unavailable. – The value of Port state is Deactivated. 2.

Optional: Check the connectivity of the gateway (mandatory in three-layer networking).

(1) Run the MML command LST IPCHK to query the configuration of the gateway connectivity check. (2) Run the MML command STR IPCHK to start the gateway connectivity check. NOTE

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

(3) In the alarm tab page of the LMT, check whether the ALM-21346 IP Connectivity Check Failure alarm is reported. If yes, clear the alarm as suggested. (4) To keep the gateway connectivity check, end this task; otherwise, run the MML command STP IPCHK to stop the gateway connectivity check. l

Checking the status of the optical port 1.

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

----End Issue 05 (2011-03-07)


15-3


15 FAQ

15.2 Unavailable E1/T1 Port This section describes how to handle the problem that the E1/T1 port is unavailable.

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

Solution 1.

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

l

2.

When electrical ports serve as the bearers, perform loopback test on the faulty E1/T1 ports. For details, see 15.6 Performing the Loopback Test on the E1/T1 Port . When optical ports serve as the bearers, perform group loopback test on the faulty E1/ T1 ports. For details, see 15.7 Performing the Loopback Test on the Optical Port .

Check whether the following alarms are listed on the alarm tab page of the LMT. If any of the alarms exists, handle them based on the suggestions from the online help. l

ALM-21201 E1/T1 Loss of Signal

l

ALM-21202 E1/T1 Loss of Frame Alignment

l

ALM-21203 E1/T1 Remote Alarm Indication Signal

l

ALM-21205 E1/T1 Loss of Multiframe Alignment NOTE

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

15.3 Unavailable FE/GE Port This section describes how to handle the problem that the FE/GE port is unavailable.

Symptom When you run the MML command DSP ETHPORT to check the status of the FE/GE port, one of the following conditions exists: l

The value of Link Availability Status is Unavailable.

l

The value of Port state is Deactivated.

1.

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

2.

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

Solution

15-4


Issue 05 (2011-03-07)


15 FAQ

15.4 IP Connection Setup Failure This section describes how to handle the failures during IP connection setup.

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

Solutions When the user plane is over IP transmission, handle the failure according to Table 15-2. Table 15-2 Operation index

Index

Action

Remarks

*1-1

Determine the IP path that carries the common channel.

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

*1-2

Check whether the IP path is available.

1. Run the MML command DSP IPPATH to query the status of the IP path. 2. If any transmission resource group is configured over the Iub interface, run the MML command DSP RSCGRP to query the status of the transmission resource group. 3. If all the IP paths are unavailable, go to *1-3.

*1-3

Check whether the transmission link is available.

1. See 15.1 Checking the Transmission Link .

Handle the transmission link failure.

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

*1-5

Check the configuration of the IP path.

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

*1-6

Check the realtime IP route information.

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

*1-4

2. If the transmission link is unavailable, go to *1-4. 3. If the transmission link is available, go to *1-5.

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

15.5 Board Data Loading Failure This section describes how to handle the failures that occur during data loading to the BSC6900 board. Issue 05 (2011-03-07)


15-5


15 FAQ

Symptom The status of the boards on the device panel is abnormal when the BSC6900 board software and data files are being loaded to the BSC6900 boards.

Solution 1.

2.

3.

4.

5.

15-6

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

If...

Then...

Board status of other boards of the same type is Normal,

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

Board status of other boards of the same type is Faulty,

Go to step 2.

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

If...

Then...

The DIP switch on the subrack is not set as configured,

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

The DIP switch on the subrack is set as configured,

Go to step 3.

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

If...

Then...

No,

Correct the internal subnet mask and internal IP address and then reload the data to the board.

Yes,

Go to step 4.

If data loading on the DPU boards in the EPS fails, check whether the SCUa boards in the MPS and the EPS are properly connected.

If...

Then...

The connection is improper,

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

The connection is proper,

Go to step 5.

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

If...

Then...

The type of the board is incorrectly set,

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


Issue 05 (2011-03-07)


6.

15 FAQ

If...

Then...

The type of the board is correctly set,

Go to step 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 then run the MML command DSP E1T1 to check whether the physical link between the Ater interface boards is functional.

If...

Then...

The OML is faulty, and the physical link is functional,

1. Check whether the configuration is consistent with the physical OML connection. If they are inconsistent, modify the configuration according to the physical OML connection. 2. Check whether the cross connection exists in the physical OML. If yes, correct the physical connection of the OML, and then reload the data to the board.

7.

8.

The OML is faulty, and the physical link is also faulty,

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

The OML is functional,

Go to step 7.

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

If...

Then...

Board related fault alarms exist,

Analyze the alarm information and rectify the fault accordingly.

No board related fault alarm exists,

Go to step 8.

Contact the Huawei Customer Service Center.

15.6 Performing the Loopback Test on the E1/T1 Port This section describes how to perform the loopback test to check whether the E1/T1 port is functional.


Context l

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.

Issue 05 (2011-03-07)


15-7


15 FAQ l

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

Procedure Step 1 Perform the loopback test on the local E1/T1 port. Table 15-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(Local loop).

1-2

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

1-3

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

1-4

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

If...

Then...

If the loopback test result is Succeeded ,

The E1/T1 port is available. Go to step Step 2.

If the loopback test result is Not succeeded ,

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

Step 2 Perform the loopback test on the local E1/T1 cable. Table 15-4 Procedure for performing the loopback test on the local E1/T1 cable

15-8

Step

Action

2-1

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

2-2

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

2-3

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

2-4

Stop the E1/T1 physical loopback at the local end.

If...

Then...


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


Issue 05 (2011-03-07)


15 FAQ

If...

Then...


l

Use a multimeter to measure the connectivity between the connector pin of the E1/T1 cable and the inner conductor of the coaxial cable and the connectivity between the outer shell of the connector and the shielding layer of the coaxial cable. If a connectivity failure occurs, make a new connector and assemble the cable again.

l

Use a multimeter to check whether the internal and external conductors of the E1/T1 cable are shortcircuited. If so, make a new connector and assemble the cable again.

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

Step 3 Perform the loopback test on the peer E1/T1 port. Table 15-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 the E1/T1 port.

3-3

Run the MML command DSP E1T1LOP at the peer end to query the result of the loopback test.

3-4

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

If...

Then...




Contact the maintenance personnel for the peer equipment to rectify faults in the peer equipment or the transport network.

----End

15.7 Performing the Loopback Test on the Optical Port This section describes how to perform the group loopback test to check whether the optical port is functional. Issue 05 (2011-03-07)


15-9


15 FAQ


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

Procedure Step 1 Perform the loopback test on the local optical port. Table 15-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 to LOCAL_LOOP(LOCAL_LOOP) .

1-2

Run the MML command DSP E1T1 to query the state of the port.

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 Port State. in the result are AVAILABLE ,

The SDH port is available. Go to step Step 2.

The values of Port State. in the result are The SDH port is faulty. Replace the interface LINK_DOWN, board carrying the faulty SDH port.

Step 2 Perform the loopback test on the local fiber. Table 15-7 Procedure for performing the loopback test on the local fiber

15-10

Step

Action

2-1

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

2-2

Run the MML command DSP E1T1 to query the state of the port.

2-3

Stop the fiber physical loopback at the local end.

If...

Then...

The values of Port State. in the result are AVAILABLE ,

The local fiber is available. Go to step Step 3.

The values of Port State. in the result are LINK_DOWN,

The local fiber is faulty. Replace the faulty fiber.


Issue 05 (2011-03-07)


15 FAQ

Step 3 Perform the loopback test on the peer optical port. Table 15-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 to REMOTE_LOOP(REMOTE_LOOP) .

3-2

Run the MML command DSP OPT at the peer end to query the result of the loopback.

3-3

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

If...

Then...

The values of Optical port state in the result are Available,


The values of Optical port state in the result are Fault,

Contact the maintenance personnel for the peer equipment to rectify faults in the peer equipment or the transport network.

----End

15.8 Setting Maintenance Mode for NE Prerequisite l


l


l

The BSC6900 is connected to the M2000 (for details, see 10 Connecting the BSC6900 to the M2000).

Procedure Step 1 On the M2000, choose Monitor > Alarm Setting > Maintenance Mode Alarm Filter. Step 2 In the Maintenance Mode Alarm Filter window, click Setting. Step 3 In the Set Maintenance Mode Alarm Filter dialog box, select the NE to be set, as shown in Figure 15-1. l

Issue 05 (2011-03-07)

Set Start Time and End Time as required. The Start Time and End Time take effect based on the time displayed on the NE. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

15-11


15 FAQ l

To set the maintenance mode of the NE to Install, select Install from the Device Status drop-down list box.

l

To set the maintenance mode of the NE to Normal, select Normal from the Device Status drop-down list box.

Figure 15-1 Setting Maintenance Mode for NE

Step 4 Click OK . The Set Data Comparison dialog box is displayed, providing the current device status and the parameters that you set. This helps determine whether the current status of the NE should be changed. ----End

Follow-up Procedure After the setting is complete, the NE alarms and events that are generated during Start Time and End Time are not displayed in the alarm list and event log list of the M2000. You can query the alarms and events that are generated when the NE is in a specific status by setting advanced filtering conditions. For details, see the M2000 Operator Guide.

15-12


Issue 05 (2011-03-07)


16 Appendix

16

Appendix

About This Chapter This chapter details the communication ports and the commissioning checklist of the BSC6900. 16.1 Communication Ports Used by the BSC6900 This section provides communication ports used by the BSC6900. 16.2 BSC6900 Commissioning Checklist BSC6900 commissioning checklist is for recording and checking the result of BSC6900 commissioning.

Issue 05 (2011-03-07)


16-1


16 Appendix

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

16-2

Protoc ol

Side A

Side A Ports (Liste ning)

Side B

Side B Ports (Lau nch)

Service

Authenti cation

TCP

OMU

20

BSC6900 Host, LMT, M2000 Server

10246553 5

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

username/ password

TCP

OMU

21

BSC6900 Host, LMT, M2000 Server

10246553 5

For FTP control. FAM Load, software and log upload/download

username/ password

TCP

LMT

21

OMU

10246553 5

For FTP control, this port for OMU

username/ password

TCP

OMU

1500

BSC6900 Host

10246553 5

Exchange, communication with FAM

IP Address

TCP

OMU

3389

Remote Desktop

10246553 5

the port is used by MSTSC, username/ to maintain OMU password

TCP/ SSL

OMU

6000/8 000

LMT, M2000 Server

10246553 5

MML, For Maintenance

username/ password

TCP/ SSL

OMU

6001/8 001

LMT, M2000 Server

10246553 5

MML, For Alarm

username/ password

TCP/ SSL

OMU

6006/8 006

LMT, M2000 Server

10246553 5

LMT, For Maintenance

username/ password

TCP

LMT

80

LMT computer

80

For LMT Web browsing

username/ password


Issue 05 (2011-03-07)


Issue 05 (2011-03-07)

16 Appendix

Protoc ol

Side A

Side A Ports (Liste ning)

Side B

Side B Ports (Lau nch)

Service

Authenti cation

TCP

OMU

6088

Upgrade tool

10246553 5

For Upgrade tool

None

TCP/ SSL

OMU

6099/8 099

M2000 Server

10246553 5

MML, data synchronization with M2000

None

TCP/ SSL

OMU

6100/8 100

LMT

10246553 5

MML, Alarm Box

None

TCP/ SSL

OMU

16002/ 18002

M2000 Server

10246553 5

MML, notification None message from performance and M2000

TCP

MySQ L

3306

Peer OMU

10246553 5

MySQL

username/ password

TCP

OMU

22

SSH Client

10246553 5

Putty terminal tool port (SSH)

username/ password

UDP

OMU

67

BSC6900 Host

10246553 5

Load, Bootp Listen

None

UDP

OMU

123

OMU

1024- NTP Server, slow time 6553 synchronization, local 5 listening port

None

UDP

OMU

11774

Peer OMU

10246553 5

SecurityManager, for dual OMU

None

UDP

OMU

11775

Peer OMU

10246553 5

SecurityManager, for dual OMU

None

UDP

OMU

11776

Peer OMU

10246553 5

SecurityManager, backup tunnel between dual OMU

None

UDP

M200 0 Server

123

OMU

123

NTPClient, time synchronization with time's server, local listening port

None


16-3

BSC6900 GSM Commissioning Guide(V900R012C01_05)

Recommend Documents