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

BSC6910 UMTSV100R015C00

Commissioning Guide

Issue 02Date 2013-07-30

HUAWEI TECHNOLOGIES CO., LTD.

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

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied. Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.comEmail: [email protected]

Issue 02 (2013-07-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

i

About This Document

OverviewBSC6910 commissioning is performed after hardware is installed and before services areprovided. It aims to ensure that the BSC6910 can work properly by performing verification tasksrelated to equipment, board software and data file loading, interfaces, and services.

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

Product Name Product VersionBSC6910 V100R015C00

Intended AudienceThis document is intended for field engineers.

Organization1 Changes in the BSC6910 UMTS Commissioning GuideThis chapter describes the changes in the BSC6910 UMTS Commissioning Guide.2 Commissioning PrerequisitesBefore the BSC6910 commissioning, the status of the equipment and the network to becommissioned must meet the conditions required. The software installation packages, licenses,and MML command scripts required for commissioning must be ready.3 Commissioning ProcessThe BSC6910 commissioning can be performed remotely, locally, or remotely with localassistance.4 Checking Operating Status of Hardware

BSC6910 UMTSCommissioning Guide About This Document


ii

Before commissioning the equipment, ensure that the BSC6910 subrack is powered on and isoperating normally.5 Commissioning the OMUBefore using the OMU for the first time, commission the OMU onsite to check the installationof OMU applications and the version of the OMU applications, and configure the IP address,mask, and name of the OMU to ensure the normal communication between the BSC6910 andthe LMT or M2000.6 Logging In to the BSC6910 Through the LMTThis section describes how to log in to the BSC6910 through the LMT and enable communicationbetween the LMT and the BSC6910 to ensure smooth BSC6910 commissioning through theLMT.7 Updating the OMU DatabaseThis chapter describes how to update configuration data in the OMU database by running MMLcommand scripts.8 Activating and Verifying the LicenseThis section describes how to activate the license and verify the license configurationinformation to enable the service checking.9 Loading BSC6910 Board Software and Data FilesThis chapter describes how to load the BSC6910 board software and data files.10 Connecting to the M2000This section describes how to connect the BSC6910 to the M2000 for centralized management.11 Setting the Connection Mode Between the M2000 and BSC6910 to SSLThe connection mode between the M2000 and BSC6910 must be set to Secure Socket Layer(SSL) on the M2000 to ensure operation and maintenance (O&M) safety.12 Verifying InterfacesThis section describes how to verify interfaces on the BSC6910 side. Select a verification methodbased on the onsite situation.13 Handling the Alarms Generated During the CommissioningThis section describes how to handle the alarms generated during the commissioning to preventthe alarms from affecting service verifications.14 Verifying UMTS ServicesThis section describes how to verify that the UMTS basic services and the feature services thatare enabled are normal. The basic UMTS services are voice service, CS streaming service, PSservice, and mobility management service. The feature services include inter-RAT handovers,HSDPA, HSUPA, 64QAM, MIMO, and DC-HSDPA.15 Verifying Network ReliabilityThe network reliability can be verified after you switch over active and standby boards, checkgenerated alarms, and making dialing tests.16 Troubleshooting



iii

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

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

Symbol DescriptionIndicates a hazard with a high level or medium level of riskwhich, if not avoided, could result in death or serious injury.

Indicates a hazard with a low level of risk which, if notavoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation that, if notavoided, could result in equipment damage, data loss,performance deterioration, or unanticipated results.Indicates a tip that may help you solve a problem or savetime.Provides additional information to emphasize or supplementimportant points of the main text.

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

Convention DescriptionTimes New Roman Normal paragraphs are in Times New Roman.Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.Italic Book titles are in italics.Courier New Examples of information displayed on the screen are in

Courier New.

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



iv

Convention DescriptionBoldface The keywords of a command line are in boldface.Italic Command arguments are in italics.[ ] Items (keywords or arguments) in brackets [ ] are optional.{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.{ x | y | ... }* Optional items are grouped in braces and separated by

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

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

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

Convention DescriptionBoldface 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 OperationsThe keyboard operations that may be found in this document are defined as follows.

Format DescriptionKey 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 OperationsThe mouse operations that may be found in this document are defined as follows.



v

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



vi

Contents

About This Document.....................................................................................................................ii1 Changes in the BSC6910 UMTS Commissioning Guide.......................................................12 Commissioning Prerequisites.....................................................................................................33 Commissioning Process...............................................................................................................54 Checking Operating Status of Hardware..................................................................................75 Commissioning the OMU............................................................................................................95.1 Commissioning the OMU Locally...............................................................................................................................105.2 Commissioning the OMU Using a USB Flash Drive...................................................................................................156 Logging In to the BSC6910 Through the LMT.......................................................................237 Updating the OMU Database....................................................................................................258 Activating and Verifying the License......................................................................................299 Loading BSC6910 Board Software and Data Files................................................................319.1 Generating Data Files for the Loading.........................................................................................................................329.2 Setting the Loading Mode............................................................................................................................................329.3 Resetting BSC6910 Boards..........................................................................................................................................329.4 Checking the Consistency of the Data and the Version...............................................................................................3310 Connecting to the M2000..........................................................................................................3511 Setting the Connection Mode Between the M2000 and BSC6910 to SSL.......................3712 Verifying Interfaces..................................................................................................................3912.1 Verifying Interfaces on the M2000............................................................................................................................4012.1.1 Setting the NE Engineering Mode to TESTING.....................................................................................................4012.1.2 Verifying Interfaces Automatically.........................................................................................................................4112.1.3 Setting the NE Engineering Mode to NORMAL...................................................................................................4312.2 Verifying Interfaces on the LMT................................................................................................................................4412.2.1 Verifying Fiber Optic Cable Connections...............................................................................................................4512.2.2 Verifying Internal Interfaces....................................................................................................................................4612.2.3 Verifying the Iub Interface......................................................................................................................................4712.2.4 Verifying the Iu-CS Interface..................................................................................................................................49

BSC6910 UMTSCommissioning Guide Contents


vii

12.2.5 Verifying the Iu-PS Interface..................................................................................................................................5212.2.6 Verifying the Iur Interface.......................................................................................................................................5312.2.7 Verifying the Iu-BC Interface..................................................................................................................................5512.2.8 Verifying the Iur-g Interface....................................................................................................................................5612.2.9 Verifying the Iur-p Interface....................................................................................................................................5713 Handling the Alarms Generated During the Commissioning.........................................5914 Verifying UMTS Services........................................................................................................6015 Verifying Network Reliability................................................................................................6316 Troubleshooting........................................................................................................................6516.1 Checking Transmission Links....................................................................................................................................6716.2 Performing a VCL Continuity Check.........................................................................................................................6916.3 Verifying the PVC Delay Detection Function............................................................................................................7016.4 Unavailable E1/T1 Port..............................................................................................................................................7216.5 Unavailable FE/GE Port.............................................................................................................................................7316.6 Cell Setup Failure.......................................................................................................................................................7316.7 Signaling Link Failure on the Iub Interface................................................................................................................7916.8 AAL2/IP Connection Setup Failure...........................................................................................................................8316.9 Data Loading Failures on the Board...........................................................................................................................8516.10 Performing a Loopback Test on an Optical Port......................................................................................................8717 Appendix.....................................................................................................................................9017.1 Communication Ports on the BSC6910......................................................................................................................9117.2 BSC6910 Commissioning Checklist..........................................................................................................................91

BSC6910 UMTSCommissioning Guide Contents


viii

1 Changes in the BSC6910 UMTSCommissioning Guide

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

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

Content Change Description16.1 Checking TransmissionLinks

Added procedure of checking FRA transmission link.

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

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

Content Change Description8 Activating and Verifying theLicense

Added procedure of verifying the license information.

Compared with issue Draft A (2013-01-30), this issue does not exclude any topics.

BSC6910 UMTSCommissioning Guide 1 Changes in the BSC6910 UMTS Commissioning Guide


1

Draft A (2013-01-30)This is the Draft A release of V100R015C00.

BSC6910 UMTSCommissioning Guide 1 Changes in the BSC6910 UMTS Commissioning Guide


2

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

Requirements for Equipment StatusBefore commissioning, ensure that the equipment meets the conditions listed in Table 2-1.

Table 2-1 Requirements for equipment status before commissioningItem RequirementBSC6910 hardware The hardware is installed and has passed the hardware

installation check and power-on check.OMU The OMU is configured before delivery. For details, see

Checklist for the OMU Software Factory Settings in theBSC6910 UMTS OMU Administration Guide.

LMT PC The LMT PC meets the configuration requirements. For details,see Configuration Requirements of the LMT PC in the BSC6910UMTS LMT User Guide.

Requirements for the Network to Be CommissionedTo ensure the smooth commissioning of the Iub, Iu, Iur, Iur-g, Iur-p, and Iu-BC interfaces, thenetwork equipment in the network to be commissioned must meet the following requirements:l At least one NodeB is connected to the BSC6910. The NodeB must have passed

commissioning and can provide basic functions.l At least one set of CN equipment is connected to the BSC6910. The CN equipment must

have passed commissioning and can provide basic functions.l Other network equipment that is connected to the network equipment to be commissioned,

if any, must have passed commissioning and can provide basic functions. If an RNC, BSC,or call broadcast center (CBC) is connected to the BSC6910, the RNC, BSC, or CBC musthave passed commissioning and can provide basic functions.

BSC6910 UMTSCommissioning Guide 2 Commissioning Prerequisites


3

l Three single-mode UEs and one dual-mode UE are ready for test and are registered withthe home location register (HLR).

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

Figure 2-1 Typical network to be commissioned

Requirements for the Software and Data Filesl Software installation package

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

l LicenseThe license that is applicable to configuration in the local office is obtained from the Huaweitechnical support engineer.

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

BSC6910 UMTSCommissioning Guide 2 Commissioning Prerequisites


4

3 Commissioning ProcessThe BSC6910 commissioning can be performed remotely, locally, or remotely with localassistance.l Local commissioning is performed by a field engineer (engineer responsible for onsite

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

l Remote commissioning is remotely performed by an engineer (technical engineerresponsible for the BSC) and multiple BSCs can be commissioned simultaneously in thecentral equipment room.

l Remote commissioning with local assistance is performed remotely by an engineer withthe assistance of a field engineer.

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

BSC6910 UMTSCommissioning Guide 3 Commissioning Process


5

Figure 3-1 Commissioning flowchart

BSC6910 UMTSCommissioning Guide 3 Commissioning Process


6

4 Checking Operating Status of HardwareBefore commissioning the equipment, ensure that the BSC6910 subrack is powered on and isoperating normally.

PrerequisitesThe BSC6910 subrack has passed the power-on check.

ProcedureStep 1 Check whether the subrack is powered on.

If... Then...

The subrack is not powered on Go to Step 2.

The subrack is powered on Go to Step 4.

Step 2 Set the power switches that control the subrack power supply on the power distribution frame(PDF) to ON.

Step 3 Set the air switches that control the subrack power supply on the power entry module (PEM) toON.

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

Table 4-1 Checklist of the power supply to the cabinet componentsComponent Normal Power Supply StatusBoard The RUN indicator on the board panel is

neither steady on nor steady off.Fan box The RUN indicator on the fan box panel

blinks one second on and one second off ingreen after the subrack is powered on.

BSC6910 UMTSCommissioning Guide 4 Checking Operating Status of Hardware


7

Component Normal Power Supply StatusPEM The STATUS indicator on the panel is green

and steady on.

NOTEIf power failure occurs, handle the problem by referring to step 5 in section Powering on the Subrack in theBSC6910 UMTS Site Maintenance Guide.

----End

BSC6910 UMTSCommissioning Guide 4 Checking Operating Status of Hardware


8

5 Commissioning the OMUAbout This Chapter

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

ContextThe OMU can be commissioned locally or through a USB flash drive. Select a commissioningmethod based on the onsite scenario.5.1 Commissioning the OMU LocallyThe OMU is locally commissioned by a field engineer who connects a PC to the OMU. If theBSC6910 is configured with active and standby OMUs, commission the active OMU and thestandby OMU based on the procedure given in this section.5.2 Commissioning the OMU Using a USB Flash DriveThis section describes how to commission the OMU using a USB flash drive. You can locallyinsert the prepared USB flash drive to the OMU at the site and then perform OMU commissioningwith cooperation of a remote engineer.

BSC6910 UMTSCommissioning Guide 5 Commissioning the OMU


9

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

Prerequisitesl You have obtained the OMU application installation package consistent with the OMU

version used in the local office and the Records of OMU Software InstallationInformation.

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

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

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

ProcedureStep 1 Connect the PC to the OMU board.

1. Connect the PC to the ETH2 commissioning port on the OMU board by using a networkcable.

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

Step 2 Set the link mode of the external OMU Ethernet adapters.1. Log in to the OMU by referring to Logging In to the OMU in the BSC6910 UMTSOMU

Administration Guide.2. Check whether the link mode of the external OMU Ethernet adapters is consistent with that

of LAN switches.For details about how to query the link mode of the external OMU Ethernet adapters, seeFollow-up Procedure of Setting the Link Mode for External OMU Ethernet Adapters in theBSC6910 UMTSOMU Administration Guide.

If... Then...The link mode of the external OMUEthernet adapters is consistent with that ofLAN switches

Go to Step 3.



10

If... Then...The link mode of the external OMUEthernet adapters is inconsistent with thatof LAN switches

Set the link mode of the external OMUnetwork adapters to be consistent with thatof LAN switch by referring to operationsin Procedure of Setting the Link Mode forExternal OMU Ethernet Adapters inBSC6910 UMTSOMU AdministrationGuide.

Step 3 Install the OMU applications.

1. Run the /etc/rc.d/omud status command to check the running status of the OMU process.If... Then...The information displayed is running a. Run the /etc/rc.d/omud stop command

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

The information displayed is unused Go to Step 3.2.The information displayed is No such fileor directory

a. Install the OMU applications in theactive workspace by referring tooperations in Procedure of Installingthe OMU Applications in the ActiveWorkspace in the BSC6910UMTSOMU Administration Guide.

b. Go to Step 6.c. Go to Step 7. The task is completed.

2. Run the cd /mbsc/upgrade command to switch to the OMU installation directory, and then

run the ls command to query the current versions of the OMU applications.If... Then...The versions of the OMU applications arethe same as those required by the operator

Go to Step 4.



11

If... Then...The versions of the OMU applications aredifferent from those required by theoperator

a. Uninstall the OMU applications byreferring to operations in Procedure ofUninstalling the OMU Applications inthe BSC6910 UMTSOMUAdministration Guide.

b. Upload the OMU applicationinstallation package to the OMU byreferring to operations in Procedure ofUploading the OMU ApplicationInstallation Package to the OMU in theBSC6910 UMTSOMU AdministrationGuide.

c. Install the OMU applications in theactive workspace by referring tooperations in Procedure of Installingthe OMU Applications in the ActiveWorkspace in the BSC6910UMTSOMU Administration Guide.

d. Go to Step 6.e. Go to Step 7. The task is completed.

Step 4 Modify the OMU IP addresses.

1. Run the cd /mbsc/bam/version_a/bin/bam command to switch to the directory where theomutool program is located.

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

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

NOTE

l The following two methods show how to change the fixed external IP address if changing thegateway IP address is required at the same time.l Method 1: Type ./omutool extercard The external fixed IP address The subnet mask (The

gateway IP address) and then press Enter to change the fixed external IP address and gatewayIP address at the same time. The following is an example: ./omutool extercard 10.161.10.100 255.255.255.0 10.161.10.1

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

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



12

3. Change the virtual external IP address and the subnet mask of the active and standby OMUsaccording to the plan. Ensure that the virtual external IP address is on the same networksegment as the fixed external IP address.Run the ./omutool extervip The external virtual IP address The subnet mask command tochange the virtual external IP address and the subnet mask. For example, you can type thefollowing command and then press Enter../omutool extervip 10.161.10.102 255.255.255.0

NOTE

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

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



13

If... Then...All IP addresses are on the samenetwork segment as the networkof the operator

Change the IP address in conflict.l Run the ./omutool innercard The internal fixed

IP address command to change the fixed internalIP address and the subnet mask. For example, youcan type the following command and then pressEnter../omutool innercard 80.168.3.60

l Run the ./omutool innervip The internal virtualIP address command to change the virtual internalIP address and the subnet mask. For example, youcan type the following command and then pressEnter../omutool innervip 80.168.3.40NOTEl When the fixed or virtual internal IP address is being

changed, a window is displayed to remind users tocheck whether the virtual or fixed internal IPaddress needs to be changed. In this way, users canmake necessary changes to ensure that the two IPaddresses are on the same network segment.

l If the network segment of the virtual or fixedinternal IP address is changed, the Subnet No. mustbe changed when updating the OMU database. Fordetails, see Follow-up Procedure in 7 Updating theOMU Database to ensure that the OMUcommunicates normally with the BSC6910 host.

l Change the backup channel IP address and subnetmask of the active and standby OMUs:Run the ./omutool backupcard The IP addresscommand. For example, you can type thefollowing command and then press Enter../omutool backupcard 192.168.3.60

l Run the ./omutool debugcard The debugging IPaddress command to change the debugging IPaddress and the subnet mask. For example, youcan type the following command and then pressEnter../omutool debugcard 192.168.6.60

The preceding IP addresses arenot on the same networksegment as the network of theoperator

Change the backup channel IP address of the standbyOMU.Run the ./omutool backupcard The IP addresscommand. For example, you can type the followingcommand and then press Enter../omutool backupcard 192.168.3.60

Step 5 Change the OMU name.

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



14

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

Step 6 Set the working mode of the OMU.1. Set the OMU backup attribute.

l If only one OMU board is configured, run the ./omutool dualmode single commandto set the OMU to work in independent mode.

l If two OMU boards (active and standby OMU boards) are configured, run the ./omutooldualmode dual command to set the OMU to work in active/standby mode.

2. Set the product mode.a. Run the /etc/rc.d/omud start command to start the OMU applications.b. Run the MML command SET OFFICENAME to set the product mode.

Step 7 Check the OMU running status.1. Run the ps -afx command to check the running status of the OMU.

The OMU is operating properly if all OMU processes exist in the OMU active workspacedirectory /mbsc/bam/version_a/bin/bam/monitor.

OMU State OMU Processes that Must ExistActive OMU host_gate, ems_gate, authority,

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

Standby OMU software, ftp_server, sntp,omu_manager, and debug_log

NOTE

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

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

5.2 Commissioning the OMU Using a USB Flash DriveThis section describes how to commission the OMU using a USB flash drive. You can locallyinsert the prepared USB flash drive to the OMU at the site and then perform OMU commissioningwith cooperation of a remote engineer.



15

Prerequisitesl The preparations for installing software on site are completed. For details, see Onsite

Software Installation Preparations in the BSC6910 UMTS OMU Administration Guide.l You have obtained the planned OMU IP addresses and the OMU name, and have recorded

them in Configuration Information for Preparing the USB Flash Drive.l The capacity of the USB flash drive is at least 2 GB. If the BSC6910 is configured with

active and standby OMUs, two USB flash drives are required.l A USB port is available on the PC, and the USB port is not restricted. For example, there

is no CPM restriction.

Contextl Using a USB flash drive to commission an OMU involves two steps: preparing the USB

flash drive and commissioning the OMU after inserting the USB flash drive into the OMU.l The prepared USB flash drive applies only to the DOPRA Linux operating system.l This section takes the commissioning OMU in active/standby mode as an example.

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

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

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

ProcedureStep 1 Prepare a USB flash drive.

1. Insert a USB flash drive into the USB port on a portable computer.2. Double-click U_creator_chs.exe to open the Dopra_Linux_U tool, as shown in Figure

5-1.



16

Figure 5-1 Dopra_Linux_U tool window

3. Select NE List in the left panel of the window shown in Figure 5-1 and right-click the list

to choose Add NE. A dialog box is displayed, as shown in Figure 5-2.



17

Figure 5-2 Add NE dialog box

4. Enter the NE Name, set Operate type to Install, select Install OMU?, enter the external

virtual IP address of the NE to be added and then click OK. An NE is added.NOTE

l The NE name is used to identify different NEs and only can include letter, numerals, "-", and "_".l After an NE is added, the NE name and the external virtual IP address can be changed only after you

delete the NE and then add the NE.l If you want to prepare multiple USB flash drives, it is recommended that you prepare the USB flash

drives one by one and make a mark on each USB flash drive to specify which NE this USB flash driveis to be used for.

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



18

Figure 5-3 Configuring information

The description of the parameter is as the following:l All the manually configured items need to be entered.l If Install OMU? is not selected in Step 1.4, only the names of the active and standby

OMUs and IP addresses are displayed in the Figure 5-3.l In the configuration information interface, the values of the Backup network IP and

Backup network mask parameters must be specified. If the active and standby OMUboard is installed, the backup channels are respectively configured on the networkadapters of the backup channels corresponding to the OMUs.

l To install the software version, select the V**R**C** directory in the versioninstallation package. To install the baseline software patch, selectV**R**C**SPCX00 folder in the baseline patch installation package.

l To install a non-baseline software patch, select the V**R**C**SPCXYZ orV**R**C**SPHXYZ directory in the patch installation package.

l Select the link mode of external network adapters listed in Figure 5-3 as required. Notethat the link mode of external network adapters must be consistent with that of the onsiteLAN switch. Table 5-1 lists the mapping between the queried link mode of OMUexternal Ethernet adapters and the external network netcard mode of OMU selected inFigure 5-3.



19

Table 5-1 Mapping between the queried link mode of OMU external Ethernet adapters andthe selected external network netcard mode

Queried Link Mode of OMU ExternalEthernet Adapters

Selected External Network NetcardMode

l Auto-negotiation is on Autol Auto-negotiation is offl Speed is 10 Mbit/sl Duplex is Full

10Mb Full

l Auto-negotiation is offl Speed is 10 Mbit/sl Duplex is Half

10Mb Half

l Auto-negotiation is offl Speed is 100 Mbit/sl Duplex is Full

100Mb Full


100Mb Half

l Auto-negotiation is offl Speed is 1000 Mbit/sl Duplex is Full

1000Mb Full


1000Mb Half

6. Check that all information is correct. Click OK. Check the local directory of the USB flash

drive in the displayed dialog box, and then start the process for preparing the USB flashdrive for the active OMU.

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

NOTEl After the USB flash drive is prepared, remove it from the PC in safe mode to avoid data loss or data

corruption.l If only one OMU is configured, the USB flash drive for the standby OMU is not required.

Step 2 Commissioning the OMU after inserting the USB flash drive to the OMU1. Insert the USB flash drive into any USB ports on the OMU board panel.2. Remove and then install the OMU board to reset it. For details, see sections Removing a

Board and Installing a board in the BSC6910 UMTS Site Maintenance Guide.3. Observe the status of the indicator on the OMU panel. Determine whether the installation

is complete by referring to the following table.



20

NOTE

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

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

Board InstallationProcedure

SuccessfulInstallation

Failed Installation

EOMUa

At the beginning:l The RUN indicator

blinks.l The ALM indicator

blinks.l The ACT indicator

blinks.l The OFFLINE

indicator is off.After a certain period:l The RUN indicator

blinks.l The ALM indicator

is off.l The ACT indicator is

off.l The OFFLINE

indicator blinks.

l The RUN indicatorblinks.

l The ALM indicatoris steady on or off.

l The ACT indicatoris steady on or off.

l The OFFLINEindicator is off.

l The RUN indicatorblinks.

l The ALM indicatorblinks.

l The ACT indicatoris off.

l The OFFLINEindicator is off.

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

----End

Follow-up ProcedureCheck whether the configuration files prepared during the step Prepare the USB flash driveare correct according to the Configuration Information for Preparing the USB flash drivefor Installation recorded during the preparations.



21

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

l If the configuration files are correct, contact Huawei technical support by referring toContact Huawei Customer Service Center.

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



22

6 Logging In to the BSC6910 Through the LMTThis section describes how to log in to the BSC6910 through the LMT and enable communicationbetween the LMT and the BSC6910 to ensure smooth BSC6910 commissioning through theLMT.

Prerequisitesl The OMU commissioning has been completed.l The network connection between the LMT and the OMU has been established.

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

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

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

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

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

BSC6910 UMTSCommissioning Guide 6 Logging In to the BSC6910 Through the LMT


23

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

Step 2 Start the IE, and then log in to the BSC6910 through the LMT.1. Start the IE and enter the external virtual IP address of the OMU of the BSC6910 on the

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

Figure 6-1 BSC6910 log-in dialog box

NOTE

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

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

BSC6910 UMTSCommissioning Guide 6 Logging In to the BSC6910 Through the LMT


24

7 Updating the OMU DatabaseThis chapter describes how to update configuration data in the OMU database by running MMLcommand scripts.

Prerequisitesl You have completed the section You have 6 Logging In to the BSC6910 Through the

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

are precise and complete.

Contextl There are two ways to run MML command scripts: by running MML commands or using

the GUI. The MML command script can be executed by using the GUI only when a scriptis smaller than 4 MB. It is recommended that you run the MML script by running MMLcommands, because it is more efficient.

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

Procedurel Run the MML command script by running MML commands

1. Run the MML command SET CFGDATAINEFFECTIVE to set the system to workin ineffective mode.

CAUTIONIf the database has been updated, run the MML command SETCFGDATAINEFFECTIVE to set the system to work in ineffective mode.

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

3. Upload the MML command script to the /ftp folder in the OMU active workspacedirectory. The following assumes that the MML script BATCHFILE.txt saved indisk D is uploaded to the OMU active workspace /mbsc/bam/version_a/ftp tointroduce the two methods.

BSC6910 UMTSCommissioning Guide 7 Updating the OMU Database


25

NOTE

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

a. Click File Manager on the toolbar of the LMT to start the file manager.b. In the displayed window, choose Root > bam > version_a > ftp on the left

and click Upload on the right. A dialog box is displayed. SelectBATCHFILE.txt saved in disk D, and then click Open to upload the file. Through command lines

a. On the local PC, choose Start > Run. Type cmd and click OK.b. Input d: and press Enter to switch to disk D.c. Input ftp IP address to connect to the OMU. Here, IP address is the IP address

of the OMU.d. Input the FTP user name and password. The connection between the OMU

and the local FTP is set up after the authentication succeeds.NOTE

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

e. Input cd /mbsc/bam/version_a/ftp to switch to the OMU active workspace.f. Input put BATCHFILE.txt to upload the file.g. After the file is uploaded successfully, input quit to disconnect the FTP.

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

NOTE

l The result file RUN_BATCHFILE_RESULT.txt is saved in the /ftp folder in the OMUactive workspace installation directory, that is, /mbsc/bam/version_a/ftp.

l The execution of the script takes a certain period of time. For example, 1-1.5 hours will beneeded for executing a script with 100,000 commands.

l If the MML script fails to be executed, open the RUN_BATCHFILE_RESULT.txt fileto check the commands that fail to be executed. Then, extract the commands that fail to beexecuted and the commands that have not been executed to generate a new MML script.Correct the MML script based on the displayed messages, and then go toStep 4 to run thenew script.

l Run the MML script by using the GUI1. Run the MML command SET CFGDATAINEFFECTIVE to set the system to work

in ineffective mode.

CAUTIONIf the database has been updated, run the MML command SETCFGDATAINEFFECTIVE to set the system to work in ineffective mode.

2. Run the MML command RST DATA. Click Yes in the displayed dialog box toinitialize theBSC6910 configuration data in the OMU database.



26

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

Figure 7-1 Batch tab page

4. Click Open....The Open dialog box is displayed. Select the prepared MML command

script, and then click Open. The commands in the script are displayed on the Batchtab page.

5. Click Set.... The Set dialog box is displayed. Set Sending Commands Interval(s) to0, 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



27

6. On the Batch tab page, select All in the Execution Type area.7. Click Go. The system runs the MML commands one by one.

NOTE

l Click OK when the system displays that the current configuration is in ineffective modeafter you click Go. The execution of the script will take a long time in GUI mode. Forexample, 2-3 hours will be needed for executing a 4-MB script.

l If an Error dialog box showing Execution failed. Continue? is displayed during theexecution of the MML command script, you can infer that the MML command script isincorrect. In this case, select Yes to All to ignore the error prompt. After the MML scriptfile is executed, extract the commands that fail to be executed to generate a new MMLscript, correct the commands based on the prompts, and then go to Step 4 to run the scriptagain.

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

----End

Follow-up ProcedureAfter the OMU database is upgraded, perform the following to ensure the normal communicationbetween the OMU and BSC6910.1. Run the MML command LST SUBNET to query the Subnet No. of the BSC6910.2. Check whether the Subnet No. of the BSC6910 is consistent with the network segment of

the planned internal IP address of the OMU.NOTEThe planned internal IP address of the OMU is recorded in Configuration Information for VerifyingOMU Locally.

l If they are consistent, end this task.l If they are inconsistent, run the MML command SET SUBNET to change the Subnet

No. of the BSC6910 so that it is consistent with the network segment of the plannedinternal IP address of the OMU.

3. Run the MML command SET CFGDATAEFFECTIVE to set the system to work ineffective mode.

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



28

8 Activating and Verifying the LicenseThis section describes how to activate the license and verify the license configurationinformation to enable the service checking.

Prerequisitesl You have 6 Logging In to the BSC6910 Through the LMT..l The FTP server is started. For details on how to start the FTP server, see the operations in

Startup in the BSC6910 UMTS LMT User Guide for FTP Server. For the username andpassword of the FTP server, see FTP Server in the BSC6910 UMTS LMT User Guide. Notethat the user name or password may be modified.

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

ContextThe active workspace of the OMU can be queried through the MML command LSTOMUAREA. The following operations assume that the active workspace is version_a.

ProcedureStep 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 applyfor

Go to Step 3.

The license is inconsistent with what youapply for

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

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

BSC6910 UMTSCommissioning Guide 8 Activating and Verifying the License


29

If... Then...

The license information is consistent withthe OMU information

Go to Step 4.

The license information is inconsistent withthe OMU information

Modify the inconsistent data and repeat thisstep.

Step 4 Run the MML command ACT LICENSE to activate the license file.Step 5 Optional: If there are the primary and secondary operators, run the MML command SET

LICENSE to reallocate the resources and functions in sequence from the primary operator tothe secondary operator. If there are multiple secondary operators, run the commands severaltimes.----End

Follow-up ProcedureIf the license activation fails, you can infer that the configuration data of the license isinconsistent with that in the OMU database. Check the configuration data of the license and theconfiguration data in the OMU database.l If the configuration data such as the product name, ESN, and version number of the license

is incorrect, apply for a new license.l If the configuration data in the OMU database is incorrect, correct the configuration data,

and then reactivate the license.NOTEAn invalid or expired license file can also lead to license activation failure. For details, see the help of theMML command ACT LICENSE.

BSC6910 UMTSCommissioning Guide 8 Activating and Verifying the License


30

9 Loading BSC6910 Board Software and DataFiles

About This Chapter

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

Prerequisitesl The OMU has been commissioned.l The OMU database has been updated.

ContextThe software of the BSC6910 is generated automatically in the OMU active workspacedirectory /bin/fam during the installation of the OMU applications. For example, if the activeworkspace is version_a, the software is in /mbsc/bam/version_a/bin/fam. The software canbe loaded directly.To make the configuration take effect, format the configuration data in the OMU database togenerate a .DAT data file, and then reset the BSC6910 boards.9.1 Generating Data Files for the LoadingThis section describes how to generate data files, which can be loaded, using the MML datascripts.9.2 Setting the Loading ModeThis section describes how to set the loading modes of all the board subsystems before resettingBSC6910 boards.9.3 Resetting BSC6910 BoardsThis section describes how to load the BSC6910 board software and data files from the OMUinstallation directory to the boards and make them take effect.9.4 Checking the Consistency of the Data and the VersionThis section describes how to check whether the board configuration and the software versionof the BSC6910 are consistent with those on the OMU.

BSC6910 UMTSCommissioning Guide 9 Loading BSC6910 Board Software and Data Files


31

9.1 Generating Data Files for the LoadingThis section describes how to generate data files, which can be loaded, using the MML datascripts.

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

ProcedureStep 1 Run the MML command SET CFGDATAEFFECTIVE and do not specify any parameter to

set the system to work in effective mode.Step 2 Run the MML command FMT DATA and set Work Area Flag to Active(Format active

area) to format the configuration data in the OMU database. Do not specify the subrack numberwhen running the MML command.----End

9.2 Setting the Loading ModeThis section describes how to set the loading modes of all the board subsystems before resettingBSC6910 boards.

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

ContextFor details about the loading modes, see BSC6910 Loading Management.

ProcedureStep 1 Run the MML command SET LODCTRL to set the loading mode. In this command, set Board

Start Load Control to LFB(Load from OMU and write flash).----End

9.3 Resetting BSC6910 BoardsThis section describes how to load the BSC6910 board software and data files from the OMUinstallation directory to the boards and make them take effect.

Prerequisitesl The data file for the loading has been generated.l You have 6 Logging In to the BSC6910 Through the LMT.l All the subracks have been powered on.



32

ContextThe resetting time is less than or equals to 10 minutes.

ProcedureStep 1 Run the MML command RST BSC to reset all the BSC6910 service processing boards.

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

Step 2 Click the Device Maintenance tab on the LMT home page. The Device Maintenance tab pageis displayed.

Step 3 Check whether all the boards on the device panel are in normal state.

If... Then...

The device panel shows that all the boardsare in normal state

End this task.

The device panel shows that some boardsare not in normal state

Check the faulty boards and clear the alarmsaccording to operations in 16.9 Data LoadingFailures on the Board.

----End

9.4 Checking the Consistency of the Data and the VersionThis section describes how to check whether the board configuration and the software versionof the BSC6910 are consistent with those on the OMU.

Prerequisitesl All the subracks and boards are running normally.l You have 6 Logging In to the BSC6910 Through the LMT.

ProcedureStep 1 Run the MML command ACT CRC and do not specify a parameter and check whether the

BSC6910 board configuration is consistent with the data on the OMU.Expected result: The All table data consistent. message is displayed.

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

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

----End



33

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



34

10 Connecting to the M2000This section describes how to connect the BSC6910 to the M2000 for centralized management.

Prerequisitesl The operation and maintenance (O&M) network has passed commissioning. The M2000

is operating properly.l The version of the M2000 is compatible with that of the BSC6910.l The mediation version of the M2000 is compatible with the NE version.

Contextl If the BSC6910 and the M2000 are in the same network segment, you do not need to

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

an IP route from the BSC6910 to the M2000.

ProcedureStep 1 Connect the BSC6910 to the O&M network.

1. Connect one end of a straight-through cable to the ETH0 or ETH1 port on the OMU board.2. Connect the other end of the straight-through cable to the peer network device, such as a

hub or a router, to access the O&M network.Step 2 Configure an IP route from the BSC6910 to the M2000.

1. Run the MML command LST OMUIPRT to check whether the IP route to the M2000 isconfigured on the OMU.l If the values of Destination Network Address, Destination Address Mask, and

Forward Route Address are consistent with the planned addresses, the BSC6910 hasan IP route to the M2000. Go to Step 2.3.

l If the Destination Network Address, Destination Address Mask, and ForwardRoute Address are not consistent with the planned addresses, the BSC6910 does nothave a route to the M2000. Go to Step 2.2.

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

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

BSC6910 UMTSCommissioning Guide 10 Connecting to the M2000


35

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

4. Verify the configuration of the route from the BSC6910 to the M2000.Log in to the OMU and run the ping command to check whether the network connectivitybetween the BSC6910 and the M2000 is available. If the OMU can receive a responsepacket from the M2000, go to Step 3. Otherwise, check whether the OMU and the M2000are properly connected.

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

CAUTIONl If a firewall exists between the BSC6910 and M2000, enable the communication ports

connecting the BSC6910 and M2000 to ensure proper communication between theBSC6910 and M2000.

l For details on the ports connecting the BSC6910 and M2000, see 17.1 CommunicationPorts on the BSC6910.

l The MTU value configured for the transmission equipment between the BSC6910 and theM2000 must be no less than that configured for the OMU board of the BSC6910. Otherwise,the communication between the BSC6910 and the M2000 may be abnormal. The defaultMTU value for the OMU board is 1500.

----End

ExampleTable 10-1 describes how to configure a route between the BSC6910 and the M2000.

Table 10-1 Configuring a route from the BSC6910 to the M2000Scenario

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 IPaddress of the router is 172.121.139.10.

Operation

1. Run the MML ADD OMUIPRT command.l Set Destination network address to 10.11.100.23.l Set Destination address mask to 255.255.255.255.l Set Forward route address to 172.121.139.10.

2. Run the Secure Shell (SSH) terminal, such as PuTTY to log in to the OMU.3. Run the ping 172.121.139.10 command to check whether the network

connectivity between the BSC6910 and router is available.4. Run the ping 10.11.100.23 command to check whether the network connectivity

between the BSC6910 and M2000 is available.

BSC6910 UMTSCommissioning Guide 10 Connecting to the M2000


36

11 Setting the Connection Mode Betweenthe M2000 and BSC6910 to SSL

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

Prerequisitesl The BSC6910 and peer equipment are physically connected and both have passed the

hardware installation acceptance.l All the subracks of the BSC6910 are running normally.l You have 6 Logging In to the BSC6910 Through the LMT.l You have completed section 10 Connecting to the M2000.l You have applied for an SSL safety certificate from the Certificate Authority (CA).

ProcedureStep 1 Import and activate the certificate.

l Importing and activating the certificate on the M2000.1. On the M2000 client, choose Security Management > NE Security > Certificate

Authentication Management > Certificate Management(application style) orSecurity > Certificate Authentication Management > Certificate Management(traditional style).

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

3. In the displayed Certificate Management window, click the Device Certificate taband click Add.

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

l Importing and activating the certificate on the LMT1. On FTP Server, upload the certificate into the directory where the OMU is installed.2. Run the MML command SET CERTFILE to set the SSL certificate file of an NE.

BSC6910 UMTSCommissioning Guide

11 Setting the Connection Mode Between the M2000 andBSC6910 to SSL


37

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

3. Run the MML command SET SSLAUTHMODE. In this step, set AuthenticationMode to NONE(Verify None) or PEER(Verify Peer Certificate) as required by thesite.

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

Step 2 Set the connection method between the M2000 and BSC6910 to SSL.1. On the M2000 client, choose Security Management > NE Security > Certificate

Authentication Management > SSL Connection Management(application style) orSecurity > Certificate Authentication Management > SSL Connection Management(traditional style).

2. In the displayed SSL-Connection Policy Management window, set Connection Type ofthe relevant NE to SSL Connection. Set SSL Authentication to CryptonymAuthentication, OMC Authentication NE, NE Authentication OMC, or BidirectionalAuthentication as required on site.

NOTEWhen the SSL configuration is modified on the M2000, the M2000 sends a command to the BSC6910 tosynchronize its SSL configuration.

----End

BSC6910 UMTSCommissioning Guide

11 Setting the Connection Mode Between the M2000 andBSC6910 to SSL


38

12 Verifying InterfacesAbout This Chapter

This section describes how to verify interfaces on the BSC6910 side. Select a verification methodbased on the onsite situation.

12.1 Verifying Interfaces on the M2000This section describes how to verify interfaces by setting engineering modes and performing anNE health check on the M2000.12.2 Verifying Interfaces on the LMTThis chapter describes how to verify interfaces on the BSC6910 by using MML commands onthe LMT or the GUI. The items to be verified include fiber optic cable connections, internalinterfaces, Iub, Iu-CS, Iu-PS, Iur, Iu-BC, Iur-g, and Iur-p interfaces. The Iur interface verificationis mandatory when the BSC6910 connects to another RNC. The Iu-BC interface is mandatorywhen RNC cell broadcast services (CBSs). The Iur-g interface verification is mandatory whenthe RNC connects to the BSC. The Iur-p interface verification is mandatory when RNC in POOLis applied.

BSC6910 UMTSCommissioning Guide 12 Verifying Interfaces


39

12.1 Verifying Interfaces on the M2000This section describes how to verify interfaces by setting engineering modes and performing anNE health check on the M2000.

12.1.1 Setting the NE Engineering Mode to TESTINGDuring commissioning, the NE reports many alarms that require no care. You can mask thesealarms by setting the NE mode to TESTING by using GUL-based functions on the M2000 clientor by running MML commands on the M2000 or LMT.


hardware installation acceptance.l All the subracks of the BSC6910 are running normally.l You have completed M2000.l You have 6 Logging In to the BSC6910 Through the LMT.

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

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

NOTEFor details about engineering modes, see section Introduction to the Maintenance ModeManagement Feature in the M2000 Product Documentation.

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

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

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

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

2. In the displayed window, click .3. In the Set NE Mode dialog box, select the BSC6910 NE that needs to be set, and then

set NE Mode to TESTING. A window is displayed, as shown in Figure 12-1.NOTESelect the performance methods Instant or Time based on requirements. If Time is selected,set the Start Time and End Time of testing for the NE.



40

Figure 12-1 Setting the NE engineering mode to TESTING

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

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

----End

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

12.1.2 Verifying Interfaces AutomaticallyThis section describes how to use an NE health check on the M2000 to automatically verify theBSC6910 interfaces.


hardware installation acceptance.



41

l All the subracks of the BSC6910 are running normally.l You have completed section 10 Connecting to the M2000.

ContextThe internal interface must be verified by using MML commands or GUI on the LMT. Fordetails, see 12.2.2 Verifying Internal Interfaces.

ProcedureStep 1 Set the scenario for NE health check.

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

2. Click on the displayed tab page. The Scenario Management dialog box is displayed.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. Select an NE type for health check in NE Types, that is BSC6910 UMTS.6. Select the check items for health check (deselect those not for health check) in the Interface

Check under Check Items.7. Click OK A dialog box is displayed, prompting that the NE health check scenario is set up

successfully. Click OK to set up the NE health check scenario.Step 2 Create an NE health check task.

1. On the NE Health Check tab page, click the . The Create Task dialog box is displayed.2. Select an application scenario from the Scenario drop-down list. The application scenario

must be suitable for the newly created task. The application scenario and the specific time(the time is accurate to the second) on which the task is created are automatically displayedin the Task Name text box.

3. Select the NE for health check in the Select NE. area.4. In the Time Setting area, Click Finish to select the instant execution mode.

NOTE

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

Step 3 Check the NE health check result.1. Expand the Finished Tasks node in the navigation tree on the left side. Right-click a

finished task and choose View Report from the shortcut menu.2. In the Health Check Report dialog box, select a format to view the NE health check report.



42

NOTEThe 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 thefault according to the health check report.

----End

12.1.3 Setting the NE Engineering Mode to NORMALWhen the end time specified by End Time is reached, the NE finishes its engineering modeautomatically. If the engineering process finishes in advance, you can set the NE engineeringmode to NORMAL by using GUL functions on the M2000 client or by running MML commandson the M2000 or LMT. Alarms are reported when the NE works in NORMAL mode.

Prerequisitesl You have completed section 10 Connecting to the M2000.l Before interface verification, complete section 12.1.1 Setting the NE Engineering Mode

to TESTING.l BSC6910 has passed commissioning.

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

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

2. In the displayed window, click .3. In the Set NE Mode dialog box, select the BSC6910 NE to be set, and set NE

Mode to NORMAL, the window shown in Figure 12-2 is displayed.NOTEIf the NE engineering mode is set to NORMAL, Instant is selected by default.



43

Figure 12-2 Setting the NE engineering mode to NORMAL

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

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

----End

12.2 Verifying Interfaces on the LMTThis chapter describes how to verify interfaces on the BSC6910 by using MML commands onthe LMT or the GUI. The items to be verified include fiber optic cable connections, internalinterfaces, Iub, Iu-CS, Iu-PS, Iur, Iu-BC, Iur-g, and Iur-p interfaces. The Iur interface verificationis mandatory when the BSC6910 connects to another RNC. The Iu-BC interface is mandatorywhen RNC cell broadcast services (CBSs). The Iur-g interface verification is mandatory whenthe RNC connects to the BSC. The Iur-p interface verification is mandatory when RNC in POOLis applied.

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



44

12.2.1 Verifying Fiber Optic Cable ConnectionsThis section describes how to verify whether fiber optic cables are connected correctly. Thissection applies to the fiber optic cable connections for the working channel and protectionchannel between local and peer ends when ports on the local interface boards are working inmultiplex section protection (MSP) mode.

Prerequisitesl The optical interface board configured on the BSC6910 is operating properly and has been

connected to the transmission equipment with fiber optic cables.l You have 6 Logging In to the BSC6910 Through the LMT.

ContextWorking channel: board in an even-numbered slot in active/standby modeProtection channel: board in an odd-numbered slot in active/standby modeThe following operation assumes that the board in an even-numbered slot is the active boardand that the board in an odd-numbered slot is the standby board.

ProcedureStep 1 Run the MML command CHK OPTCRS to check the status of fiber optic cable connections

for an optical interface board.Expected result: The command output shows that the value for Check Result is Correctconnection.l If the command output shows that the value of Check Result is The check fails, check fiber

optic cable connections or the peer optical port.l If the command output shows that the value of Check Result is Incorrect connections,

exchange the RX branches of the optic fiber cables for the local working channel andprotection channel and then exchange the TX branches in the same way.

l If the command output shows that the value of Check Result is Incorrect TX connection,correct RX connection, exchange the TX branches of the optic fiber cables for the localworking channel and protection channel.

l If the command output shows that the value of Check Result is Correct TX connection,incorrect RX connection, exchange the RX branches of the optic fiber cables for the localworking channel and protection channel.

l If the command output shows that the value of Check Result is not of any of the precedingones, the conditions for checking fiber optic cable connections are not met. In this case,troubleshoot according to the command output and run this command again.

Figure 12-3 shows the fiber optic cable connections.



45

Figure 12-3 Fiber optic cable connections

----End

12.2.2 Verifying Internal InterfacesThis section describes how to verify whether the internal interfaces are working properly bychecking the status of links to the ports on the SCUb boards.

Prerequisitesl BSC6910Inter-SCUb network cables have been installed.l All the subracks of the BSC6910 are running normally.l You have 6 Logging In to the BSC6910 Through the LMT.



46

ProcedureStep 1 Run the MML command DSP PANELPORT to query the link status of the ports on the

SCUb boards.Expected result: The command output shows the actual status of links to the ports on theSCUb boards.If the status in the command output does not meet the installation requirements, reinstall theinter-SCUb network cables by referring to Installing the Inter-SCUb SFP+ High-Speed CablesBetween Different SubracksReinstalling Inter-SCUb Network Cables in the BSC6910 UMTSInstallation Guide.----End

12.2.3 Verifying the Iub InterfaceThis section describes how to verify the control plane and user plane on the Iub interface. Themethod for verifying the Iub interface varies depending on the transmission mode on the Iubinterface.

Prerequisitesl The BSC6910 and base station are physically connected and both have passed the hardware

installation acceptance.l The cell under the base station for the Iub interface verification has been configured.l All the subracks of the BSC6910 are running normally.l You have 6 Logging In to the BSC6910 Through the LMT.

ContextThe following takes one base station as an example to describe the verification process on theIub interface during the commissioning of the BSC6910. If multiple base stations are connected,repeat the operations.

Procedurel Verifying the Iub Interface (over ATM)

1. Run the MML

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

Documents

huawei trademarks

huawei proprietary

bsc6910 subrack

bsc6910 throu

huawei industrial basebantian

bsc6910 andthe lmt

product versionthe

organization1 changes