RNC Commissioning Guide-(V200R011_03)

8/10/2019 RNC Commissioning Guide-(V200R011_03)

http://slidepdf.com/reader/full/rnc-commissioning-guide-v200r01103 1/118

RNC

V200R011

Commissioning Guide

Issue 03

Date 2010-03-25

Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.



Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any

assistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Copyright © Huawei Technologies Co., Ltd. 2010. 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 the property of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and the

customer. All or part of the products, services and features described in this document may not be within the

purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,

and recommendations in this document are provided "AS IS" without warranties, guarantees or representations

of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Proprietary and Confidential


http://www.huawei.com/



Contents

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

1 Changes in RNC Commissioning Guide..............................................................................1-1

2 Safety Information.....................................................................................................................2-1

2.1 Safety Precautions...........................................................................................................................................2-1

2.2 Electricity Saf ety.............................................................................................................................................2-3

2.3 Flammable Atmosphere..................................................................................................................................2-5

2.4 Battery.............................................................................................................................................................2-6

2.5 Radiation.........................................................................................................................................................2-8

2.6 Working at Heights.........................................................................................................................................2-9

2.7 Mechanical Safety.........................................................................................................................................2-12

2.8 Others............................................................................................................................................................2-13

3 Introduction to RNC Commissioning....................................................................................3-1

3.1 Definition of RNC Commissioning.................................................................................................................3-2

3.2 Prerequisites for RNC Commissioning...........................................................................................................3-2

3.3 Preparations for RNC Commissioning............................................................................................................3-4

4 Commissioning the RNC..........................................................................................................4-1

5 Commissioning the RNC Equipment....................................................................................5-1

5.1 Commissioning BAMs....................................................................................................................................5-2

5.1.1 Obtain the Installation Information on the BAM Software....................................................................5-3

5.1.2 Remotely Logging In to the BAM.........................................................................................................5-3

5.1.3 Checking BAM Software.......................................................................................................................5-55.1.4 Checklist for BAM Software Settings Performed Before Delivery.......................................................5-5

5.1.5 Installing the BAM Application in the Active Workspace....................................................................5-6

5.1.6 Checking the Operation Status of the BAM Application.......................................................................5-8

5.1.7 Installation Directory of the BAM Application.....................................................................................5-9

5.2 Connecting the LMT.....................................................................................................................................5-11

5.2.1 Checking Computer Configuration of the RNC LMT.........................................................................5-12

5.2.2 Installing the RNC LMT Application..................................................................................................5-12

5.2.3 Connecting the RNC LMT to the BAM...............................................................................................5-15

5.2.4 Starting the Local Maintenance Terminal of the RNC.........................................................................5-16

5.3 Loading RNC Software and Data Files.........................................................................................................5-19

RNC

Commissioning Guide Contents

Issue 03 (2010-03-25) Huawei Proprietary and Confidential


i



5.3.1 Generating the RNC Data File.............................................................................................................5-20

5.3.2 Setting RNC Loading Modes (Commissioning)..................................................................................5-22

5.3.3 Loading the RSS Subrack....................................................................................................................5-23

5.3.4 Loading the RBS Subrack....................................................................................................................5-24

5.4 Activating and Verifying the RNC License..................................................................................................5-26

6 Handling Alarms During RNC Commissioning................................................................. 6-1

7 Verifying Interfaces...................................................................................................................7-1

7.1 Verifying the Iub Interface..............................................................................................................................7-2

7.1.1 Verifying the Iub Interface (over ATM)................................................................................................7-2

7.1.2 Verifying the Iub Interface (over IP)......................................................................................................7-4

7.1.3 Verifying the Iub Interface (over ATM and IP).....................................................................................7-5

7.2 Verifying the Iu-CS Interface..........................................................................................................................7-5

7.2.1 Verifying the Iu-CS Interface (over ATM)............................................................................................7-67.2.2 Verifying the Iu-CS Interface (over IP).................................................................................................7-7

7.3 Verifying the Iu-PS Interface..........................................................................................................................7-8

7.3.1 Verifying the Iu-PS Interface (over ATM).............................................................................................7-8

7.3.2 Verifying the Iu-PS Interface (over IP)................................................................................................7-10

7.4 Verifying the Iur Interface.............................................................................................................................7-11

7.4.1 Verifying the Iur Interface (over ATM)...............................................................................................7-11

7.4.2 Verifying the Iur Interface (over IP)....................................................................................................7-13

7.5 Verifying the Iu-BC Interface.......................................................................................................................7-14

8 Verifying RNC Services............................................................................................................8-1

9 Integrating the RNC into the M2000...................................................................................... 9-1

10 Creating RNC Scheduled Tasks..........................................................................................10-1

11 FAQ...........................................................................................................................................11-1

11.1 Verifying Physical Links on the Terrestrial Interface at the RNC (over ATM).........................................11-2

11.2 Verifying Physical Links on the Terrestrial Interface at the RNC (over IP)...............................................11-3

11.3 Conducting BFD/ARP Connectivity Check on the Gateway of the FE/GE Port........................................11-4

11.4 Troubleshooting: Unavailable E1/T1 Physical Links.................................................................................11-5

11.5 Troubleshooting: Unavailable FE/GE Physical Links..............................................................................11-1011.6 Troubleshooting: Inconsistent Interface Data...........................................................................................11-11

11.7 Troubleshooting: Cell Setup Failures........................................................................................................11-11

11.8 Troubleshooting: Signaling Link Failures on the Iub Interface................................................................11-18

11.9 Troubleshooting: AAL2/IP Connection Setup Failures............................................................................11-22

11.10 Troubleshooting: RNC Boards Loading Failures....................................................................................11-24

12 Communication Ports Used by the BSC6810....................................................................12-1

Contents

RNC

Commissioning Guide

ii Huawei Proprietary and Confidential


Issue 03 (2010-03-25)



Figures

Figure 2-1 Wearing an ESD wrist strap...............................................................................................................2-5

Figure 2-2 Lifting a weight................................................................................................................................2-10

Figure 2-3 Slant angle........................................................................................................................................2-11

Figure 2-4 One meter higher than the eave........................................................................................................2-11

Figure 3-1 Ty pical RNC commissioning network......................................................................................... ......3-3

Figure 5-1 Remote Desktop Connection dialog box............................................................................................5-4

Figure 5-2 Directory structure of BAM application on the active workarea.......................................................5-9

Figure 5-3 Directory structure of BAM application on the active and standby workareas................................5-10

Figure 5-4 Selecting a setup language................................................................................................................5-12

Figure 5-5 Co pyright notice................................................................................................................... ............5-13

Figure 5-6 Selecting software components........................................................................................................5-14

Figure 5-7 Confirming installation.....................................................................................................................5-15

Figure 5-8 User Login dialog box......................................................................................................................5-17

Figure 5-9 Of fice Management dialog box before adding an office..................................................................5-17Figure 5-10 To add an office, perform the following steps:...............................................................................5-18

Figure 5-11 Office Management dialog box after adding an office...................................................................5-18

Figure 5-12 User Login dialog box....................................................................................................................5-19

Figure 5-13 R unning commands in batches.......................................................................................................5-21

Figure 5-14 Setting the batch commands...........................................................................................................5-21

Figure 5-15 Setting the execution type...............................................................................................................5-22

Figure 5-16 R unning result of immediate batch commands..............................................................................5-22

Figure 5-17 Device panel...................................................................................................................................5-24

Figure 5-18 Device panel...................................................................................................................................5-26

Figure 6-1 Alarm browser....................................................................................................................................6-2

Figure 6-2 Detailed alarm information.................................................................................................................6-3

Figure 11-1 Locating cell setup failures (1).....................................................................................................11-13

Figure 11-2 Locating cell setup failures (2).....................................................................................................11-15

Figure 11-3 Procedure for handling signaling link failures on the ATM-based Iub interface.........................11-19

Figure 11-4 Procedure for handling signaling link failures on the IP-based Iub interface..............................11-21

Figure 11-5 Procedure for handling AAL2 connection setup failures.............................................................11-22

RNC

Commissioning Guide Figures



iii



Tables

Table 3-1 Equipment status before commissioning.............................................................................................3-2

Table 3-2 Other commissioning scenarios...........................................................................................................3-3

Table 5-1 Checklist for BAM software settings performed before delivery........................................................5-5

Table 5-2 Description...........................................................................................................................................5-8

Table 5-3 File folders of the BAM application..................................................................................................5-10

Table 5-4 Name of the loading file.....................................................................................................................5-20

Table 7-1 Per forming continuity check on AAL2 paths......................................................................................7-3

Table 7-2 Per forming continuity check on the IPoA PVC...................................................................................7-3

Table 7-3 Per forming continuity check on AAL2 paths......................................................................................7-7

Table 7-4 Per forming continuity check on the IPoA PVC...................................................................................7-9

Table 7-5 Per forming continuity check on AAL2 paths....................................................................................7-12

Table 9-1 Configuring the route from the RNC to the M2000.............................................................................9-2

Table 11-1 Physical link failure alarms..............................................................................................................11-6

Table 11-2 Pr ocedure for conducting the loopback test on the local E1/T1 port...............................................11-7Table 11-3 Pr ocedure for conducting the loopback test on the local trunk cable...............................................11-7

Table 11-4 Pr ocedure for checking the peer equipment or the transport network.............................................11-8

Table 11-5 Pr ocedure for conducting the loopback test on the SDH port..........................................................11-9

Table 11-6 Pr ocedure for conducting the loopback test on local fibers.............................................................11-9

Table 11-7 Pr ocedure for conducting the loopback test on the peer optical port.............................................11-10

Table 11-8 O peration index (1)........................................................................................................... .............11-14

Table 11-9 O peration index (2)........................................................................................................... .............11-15

Table 11-10 Common Transport Channel of the Cell......................................................................................11-17

Table 11-11 Common Transport Channel of the Cell......................................................................................11-17

Table 11-12 Operation index (1)......................................................................................................................11-19



Table 11-15 Checking and modifying the data configuration..........................................................................11-23


Table 12-1 Communication ports used by the services of the BSC6810...........................................................12-1

RNC

Commissioning Guide Tables



v



About This Document

Purpose

The commissioning of the RNC is performed after the hardware and software are installed. Thecommissioning ensures that the RNC works properly as designed.

This document describes how to commission the RNC from the aspects such as BAM, LMT,

loaded data and data files, basic information, standard interfaces, integration of the RNC into

the M2000, and services.

Product Version

The following table lists the product version related to this document

Product Name Product Model Product Version

RNC BSC6810 V200R011

Intended Audience

This document is intended for field engineers.

Organization

1 Changes in RNC Commissioning Guide

This describes the changes in the RNC Commissioning Guide.

2 Safety Information

3 Introduction to RNC Commissioning

This provides the definition of RNC commissioning. It also provides the prerequisites and preparations to be made for RNC commissioning.

RNC

Commissioning Guide About This Document



1



4 Commissioning the RNC

This describes the RNC commissioning, including commissioning RNC hardware,

commissioning software loading, verifying all interfaces, verifying RNC services, and

integrating the RNC into the M2000.

5 Commissioning the RNC Equipment

This describes how to commission the RNC equipment, including commissioning the BAM,

commissioning the RNC LMT, loading the RNC software and data files, verifying the RNC

license configuration, and verifying the switchover between active and standby RNC boards.

6 Handling Alarms During RNC Commissioning

This describes how to handle alarms reported during RNC commissioning.

7 Verifying Interfaces

This describes how to verify at the RNC that the Iub, Iu-CS, Iu-PS, and Iur interfaces areoperational.

8 Verifying RNC Services

This describes how to verify that the RNC can provide basic services or certain feature services.

9 Integrating the RNC into the M2000

This describes how to integrate the RNC into the M2000 for centralized management.

10 Creating RNC Scheduled Tasks

This describes how to create the scheduled task of automatically backing up RNC system dataand logs after RNC commissioning, so that the data and logs can be used for recovery of the

RNC equipment failure.

11 FAQ

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

12 Communication Ports Used by the BSC6810

Lists the number of the communication ports used by the services of the BSC6810.

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

About This Document

RNC

Commissioning Guide

2 Huawei Proprietary and Confidential


Issue 03 (2010-03-25)



Symbol Description

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.

Command Conventions

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


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

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

{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated by

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

{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all

items can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated by

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

RNC

Commissioning Guide About This Document



3



GUI Conventions

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


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

are in boldface. For example, click OK .

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

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

Keyboard Operations

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

Format Description

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

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

+A means the three keys should be pressed concurrently.

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

the two keys should be pressed in turn.

Mouse Operations

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

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.

About This Document

RNC

Commissioning Guide

4 Huawei Proprietary and Confidential


Issue 03 (2010-03-25)




This describes the changes in the RNC Commissioning Guide.

03(2010-03-25)

This is the commercial release.

Compared with issue 02(2009-10-31) of V200R011, this issue does not include any new topic.

Compared with issue 02(2009-10-31) of V200R011, this issue incorporates the following

changes:

Topic Change

7.2.1 Verifying the Iu-CS Interface (overATM)

7.3.1 Verifying the Iu-PS Interface (over

ATM)

l

Add the DSP ADJNODE command tocheck the adjacent node state.

l Add the LST CNNODE command to

check if the CN node is configured.

7.2.2 Verifying the Iu-CS Interface (over

IP)


IP)

Add the expected result of LST CNNODE

command.

Compared with issue 02(2009-10-31) of V200R011, this issue does not exclude any topic.

02(2009-10-31)

This is the commercial release.

Compared with issue 01 (2009-02-10) of V200R011, no information is added or deleted.

This issue incorporates the changes described in the following table:

RNC

Commissioning Guide 1 Changes in RNC Commissioning Guide



1-1



Topic Change

7.2.2 Verifying the Iu-CS Interface (over

IP)

l Add the LST CNNODE command to

check the CN node state.

l Change QAAL2 state of expected resultof the DSP ADJNODE command to

Operation state.


IP)

Add the LST CNNODE command to check

the CN node state.

01(2009-02-10)

This is the field trial release.

Compared with issue 04 (2008-08-30) of V200R010, this issue includes the following new

topics:

7.5 Verifying the Iu-BC Interface

Compared with issue 04 (2008-08-30) of V200R010, this issue excludes the following topics:

l Verifying the Switchover Between Active and Standby Boards

l Checking the RNC LMT

l Starting the RNC Message Tracing

– Tracing Iub Interface Messages

– Tracing QAAL2 Messages

– Tracing SAAL Messages

– Tracing SCTP Messages

l Monitoring the Loading Progress Window

l Verifying the Control Plane on the Iub Interface (over ATM)

l Verify the Management Plane on the Iub Interface

l Verifying the Cell Setup

l Verifying the Control Plane on the Iub Interface (over IP)

l

Verifying the Control Plane on the Iu-CS Interface (over ATM)l Verifying the Control Plane on the Iu-CS Interface (over IP)

l Verifying the Control Plane on the Iu-PS Interface (over ATM)

l Verifying the Control Plane on the Iu-PS Interface (over IP)

l Verifying the Control Plane on the Iur Interface (over ATM)

l Verifying the Control Plane on the Iur Interface (over IP)

l Checking RNC Commissioning Results

l Checklists for RNC Commissioning

l Conducting Loopback Test on E1/T1 Links at Electr ical Ports

l Conducting Loopback Test on E1/T1 Links at Optical Ports


RNC

Commissioning Guide

1-2 Huawei Proprietary and Confidential


Issue 03 (2010-03-25)



l Checking DSP Resources

l Performing Continuity Checks on Links over Interfaces

Compared with issue 04 (30.08.08) of V200R010, this issue incorporates the following changes:

Topic Change Description

4 Commissioning the RNC Steps are modified.

l 11.1 Verifying Physical Links on the

Terrestrial Interface at the RNC (over

ATM)

l 11.2 Verifying Physical Links on the

Terrestrial Interface at the RNC (over

IP)

l 11.3 Conducting BFD/ARP

Connectivity Check on the Gateway of the FE/GE Port

They are moved to the FAQ part.

l 7.1.1 Verifying the Iub Interface (over

ATM)

l 7.2.1 Verifying the Iu-CS Interface

(over ATM)

l 7.4.1 Verifying the Iur Interface (over

ATM)

l A description is added on how to handle

the result of Unavailable after the DSP

AAL2PATH command is run.

l How to conduct continuity check on

interface links is described in details.

7.1.3 Verifying the Iub Interface (over

ATM and IP)

The steps for the following operations are

deleted: verifying physical links on the Iub

interface, verifying the control panel on the

Iub interface, and verifying the management

panel on the Iub interface.


ATM)

How to conduct continuity check on interface

links is described in details.

7.1.2 Verifying the Iub Interface (over IP) l A description on how to handle the result

of Unavailable after the DSP IPPATH

command is run is added.

l Parameters related to the DSP RSCGRP

command are updated.

l 7.1.2 Verifying the Iub Interface (over

IP)

l 7.2.2 Verifying the Iu-CS Interface

(over IP)

l 7.3.2 Verifying the Iu-PS Interface (over

IP)

l 7.4.2 Verifying the Iur Interface (over

IP)

l A description on how to handle the result

of Unavailable after the DSP IPPATH

command is run is added.

l Parameters related to the DSP IPRT

command are updated.

l Verifying control plane is added.

8 Verifying RNC Services How to verify 64QAM service and MIMO

service is added.

RNC

Commissioning Guide 1 Changes in RNC Commissioning Guide



1-3



Topic Change Description

11.4 Troubleshooting: Unavailable E1/T1

Physical Links

l How to conduct loopback test on E1/T1

links on electrical ports is described in

details.

l How to conduct loopback test on E1/T1

links on optical ports is described in

details.

11.7 Troubleshooting: Cell Setup Failures How to check the DSP resources is described

in details.

11.3 Conducting BFD/ARP Connectivity

Check on the Gateway of the FE/GE Port

l The LST GATEWAYCHK command is

changed to LST IPCHK command.

l The STR GATEWAYCHK command is

changed to STR IPCHK command.

l The STP GATEWAYCHK command ischanged to STP IPCHK command.

11.9 Troubleshooting: AAL2/IP

Connection Setup Failures

MTP3BLNK is changed to MTP3.


RNC

Commissioning Guide



Issue 03 (2010-03-25)




2.1 Safety PrecautionsThis section will help you to choose measurement and testing devices to ensure safe working

conditions. Read and follow these safety precautions before installing, operating, and

maintaining the device.

Following All Safety Precautions

Before any operation, read the instructions and precautions in this document carefully to

minimize the possibility of accidents.

The Danger, Caution, and Note items in the package of documents do not cover all the safety

precautions that must be followed. They only provide the generic safety precautions for

operations.

Symbols

DANGER

Indicates a hazard with a high level of risk which, if not avoided, will result in death or serious

injury.

CAUTION

Indicates a potentially hazardous situation that, if not avoided, could cause equipment damage,

data loss, and performance degradation, or unexpected results.

NOTE

This symbol indicates that the operation may be easier if you pay attention to the safety instruction.

RNC

Commissioning Guide 2 Safety Information



2-1



Complying with the Local Safety Regulations

When operating the device, comply with local safety regulations. The safety precautions

provided in this document are supplementary to local safety regulations.

General Installation Requirements

The personnel in charge of installation and maintenance must be trained and master the correct

operating methods and safety precautions before beginning work.

The rules for installing and maintaining the device are as follows:

l Only the trained and qualified personnel can install, operate and maintain the device.

l Only the qualified specialists are allowed to remove the safety facilities, and repair the

device.

l Any replacement of the device or part of the device (including the software) or any change

made to the device must be performed by qualified or authorized personnel.

l Any fault or error that might cause safety problems must be reported immediately to the

personnel in charge.

Grounding Requirements

The following requirements are applicable to the device to be grounded:

l Ground the device before installation and remove the ground cable after uninstallation.

l Do not operate the device in the absence of a ground conductor. Do not damage the ground

conductor.

l The unit (or system) must be permanently connected to the protection ground before

operation. Check the electrical connection of the device before operation and ensure that

the device is reliably grounded.

Safety of Personnel

Ensure the following:

l When the device has been struck by lightning, do not operate the device and cables.

l When the device has been struck by lightning, unplug the AC power connector. Do not use

the fixed terminal or touch the terminal or antenna connector.

NOTE

The previous two requirements apply to the wireless fixed terminal.

l To prevent electric shock, do not connect safety extra-low voltage (SELV) circuits to

telecommunication network voltage (TNV) circuits.

l To prevent laser radiation from injuring your eyes, never look into the optical fiber outlet

with unprotected eyes.

l To prevent electric shock and burns, wear the electrostatic discharge (ESD) clothing, gloves

and wrist strap, and remove conductors such as jewelry and watch before operation.

l In case of fire, you must keep away from the buildings or device areas. You must ring the

fire alarm bell or dial the fire-alarm telephone. In any cases, you must not enter the burning buildings.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



Device Safety

l Before operation, the device must be secured on the floor or other fixed objects, such as a

wall or a mounting rack.

l Do not block ventilation openings while the system is running.

l When installing the panel, tighten the screw with the tool.

l After installing the device, properly dispose of the packing materials that are not required

in the device area.

2.2 Electricity Safety

High Voltage

DANGER

l The system requires a high voltage power supply. Direct contact with the high voltage power

supply, or contact through damp objects, may be fatal.

l Non-standard and improper high voltage operations may result in fire and electric shock.

l The personnel who install the AC facility must be qualified to perform operations on high

voltage and AC power supply facilities.

l When installing the AC power supply facility, follow the local safety regulations.

l

When operating the AC power supply facility, follow the local safety regulations.l When operating the high voltage and AC power supply facilities, use the specific tools

instead of common tools.

l When the operation is performed in a damp environment, ensure that water is kept off the

device. If the cabinet is damp or wet, shut down the power supply immediately.

Thunderstorm

The following requirements are suitable only for the wireless base station or the device with an

antenna or GPS antenna.

DANGER

In a thunderstorm, do not perform operations on high voltage and AC power supply facilities or

on a metal tower or mast.

RNC




2-3



High Electrical Leakage

DANGER

Ground the device before powering on the device. Otherwise, the personnel and device are in

danger.

If the "high electrical leakage" flag is stuck to the power terminal of the device, you must ground

the device before powering it on.

Power Cable

CAUTION

Do not install and remove the power cable with a live line. Transient contact between the core

of the power cable and the conductor may generate electric arc or spark, which may cause fire

or eye injury.

l Before installing or removing the power cable, turn off the power switch.

l Before connecting the power cable, ensure that the power cable and label comply with the

requirements of the actual installation.

Fuse

CAUTION

To ensure that the system runs safely, when a fuse blows, replace it with a fuse of the same type

and specifications.

Electrostatic Discharge

CAUTION

The static electricity generated by the human body may damage the electrostatic sensitive

components on the circuit board, such as the large-scale integrated circuit (LSI).

In the following situations, the human body generates a static electromagnetic field:

l Movement of body parts

l Clothes friction

l Friction between shoes and the ground


RNC

Commissioning Guide



Issue 03 (2010-03-25)



l Holding plastic in hand

The static electromagnetic field will remain within the human body for a long time.

Before contacting the device, plug boards, circuit boards, and application specific integrated

circuits (ASICs), wear a grounded ESD wrist strap. It can prevent the sensitive components from being damaged by the static electricity in the human body. If neither the ESD wrist strap nor an

appropriate PGND point is provided, wear the ESD gloves.

Figure 2-1 shows how to wear an ESD wrist strap.

Figure 2-1 Wearing an ESD wrist strap

2.3 Flammable Atmosphere

DANGER

Do not install the device in an atmosphere that contains flammable or explosive gas or vapour.

Do not perform any operation in this environment.

Any operation of the electrical device in the inflammable environment causes danger.

RNC




2-5



2.4 Battery

Precautions

DANGER

Before handling the battery, read the safety precautions for the handling and connection of the

battery.

Incorrect operation of batteries may cause danger. During operation, ensure the following:

l Prevent any short-circuit.

l Prevent the electrolyte from overflowing and leakage.

Electrolyte overflow may damage the device. It will corrode the metal parts and the circuit

boards, and ultimately damage the device.

General Operations

Before installing and maintaining the battery, ensure the following:

l Use special insulation tools.

l Use eye protection devices and operate with care.

l Wear rubber gloves and an apron in case of an electrolyte overflow.

l Always keep the battery upright when moving. Do not place the battery upside down or tilt

it.

l During the installation or maintenance, keep the charge power supply disconnected.

Short-Circuit

DANGER

Short-circuit of the battery may cause injury. Although the voltage of a battery is low, high

transient current generated by short-circuit will release a surge of power.

Keep metal objects away from the battery to prevent short circuit. If they have to be used,

disconnect the battery in use before performing any other operation.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



Harmful Gas

CAUTION

l Do not use unsealed lead-acid batteries, because the gas emitted from them may result in fire

or device corrosion.

l Install the battery on a horizontal surface and fix it properly.

Lead-acid batteries emit flammable gas. Therefore, store it in a place with good ventilation and

take precautions against fire.

High Temperature

CAUTION

High temperature may result in distortion, damage, and electrolyte overflow of the battery.

When the temperature of the battery exceeds 60oC, check whether there is acid overflow. If acid

overflow occurs, remove the acid immediately.

Acid

CAUTION

If the acid overflows, it should be absorbed and neutralized immediately.

When handling a leaky battery, protect against the possible damage caused by the acid. Use the

following materials to absorb and neutralize acid spills:

l Sodium bicarbonate (baking soda): NaHCO3

l Sodium carbonate (soda): Na2CO3

Antacids must be used according to the instructions provided by the battery manufacturer.

If your body touches the acid accidentally, you must immediately flush your body with clean

water. In serious cases, you must be immediately delivered to hospital for proper treatment.

Lithium Battery

DANGER

There is danger of explosion if the battery is incorrectly replaced.

RNC




2-7



l Replace the lithium battery with the same or equivalent type recommended by the

manufacturer.

l Dispose of the used battery according to the instructions provided by the manufacturer.

l Do not toss the lithium battery in fire.

2.5 Radiation

Electromagnetic Field Exposure

CAUTION

High power radio-frequency signals are harmful to the human body.

Before installing or maintaining an antenna on a metal tower or mast with a large number of

transmitter antennas, the operator should coordinate with all parties to ensure that the transmitter

antennas are shut down.

The base transceiver station (BTS) emits RF radiation, causing radiation hazard. Suggestions

for the installation and operation of BTSs are given in the following section. Operators are also

required to comply with the related local regulations on erecting BTSs.

l The antenna should be located in an area that is inaccessible to the public where the RF

radiation exceeds the stipulated value.

l If the areas where RF radiation exceeds the stipulated value are accessible to workers,

ensure that workers know where these areas are. They can shut down the transmitters before

entering these areas. If it is necessary to create areas in which RF radiation exceeds the

stipulated value, the perimeter of each area must never be more than 10 m from the antenna.

l Each forbidden zone should be indicated by a physical barrier and striking sign to warn the

public or workers.

Laser

CAUTION

When handling optical fibers, do not stand close to, or look into the optical fiber outlet with

unprotected eyes.

Laser transceivers or transmitters are used in the optical transmission system and associated test

tools. Because the laser that is transmitted through the optical fiber produces a small beam of

light, it has a very high power density and is invisible to human eyes. If a beam of light enters

the eye, the retina may be damaged.

Normally, looking into the end of an unterminated optical fiber or broken optical fiber with the

unprotected eyes from a distance of more than 150 mm [5.91 in.] will not cause eye injury. Eyes

may, however, be damaged if an optical tool such as a microscope, magnifying glass or eyeloupe is used to look into the bare optical fiber end.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



Read the following guidelines to prevent laser radiation:

l Only the trained and authorized personnel can perform the operation.

l Wear a pair of eye-protective glasses when you are handling lasers or optical fibers.

l Ensure that the optical source is switched off before disconnecting optical fiber connectors.

l Never look into the end of an exposed optical fiber or an open connector if you cannot

ensure that the optical source is switched off.

l To ensure that the optical source is switched off, use an optical power meter.

l Before opening the front door of an optical transmission system, ensure that you are not

exposed to laser radiation.

l Never use an optical tool such as a microscope, a magnifying glass, or an eye loupe to look

into the optical fiber connector or end.

Read the following instructions before handling optical fibers:

l Only the trained personnel can cut and splice optical fibers.

l Before cutting or splicing an optical fiber, ensure that the optical fiber is disconnected from

the optical source. After disconnecting the optical fiber, place protective caps on all the

optical connectors.

2.6 Working at Heights

CAUTION

When working at heights, be careful to prevent objects from falling

When working at heights, ensure that the following requirements are met:

l The personnel who work at heights must be trained.

l The operating machines and tools should be carried and handled safely to prevent them

from falling.

l Safety measures, such as wearing a helmet and a safety belt, should be taken.

l In cold conditions, warm clothes should be worn before working at heights.

l Ensure that the lifting appliances are well prepared for working at heights.

Lifting Weights

CAUTION

Do not access the areas under the arm of the crane and the goods in suspension when lifting

weights.

l Ensure that the operators have been trained and qualified.

RNC




2-9



l Check the weight lifting tools and ensure that they are intact and in good working order.

l Lift the weight only when the weight lifting tools are firmly mounted onto the weight-

bearing object or the wall.

l Use a concise instruction to prevent incorrect operation.

l The angle between the two cables should be less than or equal to 90o in the lifting of weights

(See Figure 2-2).

Figure 2-2 Lifting a weight

Safety Guide on Ladder Use

Checking the Ladder

l Check the ladder before using it. Check the maximum weight that the ladder can support.

l Never overload the ladder.

Placing the Ladder

The slant angle is preferred to be 75o. The slant can be measured with the angle square or with

arms, as shown in Figure 2-3. When using a ladder, place the wider end of the ladder on the

ground and take protective measures on the base of the ladder against slippage. Place the ladder

on stable ground.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



Figure 2-3 Slant angle

When climbing the ladder, ensure the following:

l The centre of gravity of the body does not shift outside the edge of the ladder.

l Keep balance on the ladder before performing any operation.

l Do not climb higher than the fourth rung from the top of the ladder.

If you tend to climb to the roof, the top of the ladder should be at least one meter higher than

the eave, as shown in Figure 2-4.

Figure 2-4 One meter higher than the eave

RNC




2-11



2.7 Mechanical Safety

Drilling

CAUTION

Do not drill on the cabinet without permission. Inappropriate drilling on the cabinet may damage

the electromagnetic shielding and internal cables. Metal shavings from the drilling may result

in a short-circuit of the circuit board if they get into the cabinet.

l Before drilling a hole on the cabinet, remove the cables from the cabinet.

l During the drilling, wear a visor to protect your eyes.

l During the drilling, wear the protective gloves.

l Prevent the metal shavings from getting into the cabinet. After drilling, remove the metal

shavings immediately.

Handling Sharp Objects

CAUTION

When carrying the device by hand, wear the protective gloves to prevent injury by sharp objects.

Handling Fans

l When replacing a component, place the component, screw, and tool at a safe place to prevent

them from falling into the running fan.

l When replacing the ambient equipment around the fan, do not place the finger or board

into the running fan until the fan is switched off and stops running.

Moving Heavy Objects

Wear the protective gloves when moving heavy objects.

CAUTION

l Be careful when moving heavy objects.

l When moving a chassis, ensure that there are no unattached objects resting on it, as these

may fall and cause injury.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



l Two persons should be available to move a chassis; one person must not move a heavy

chassis. When moving a chassis, keep your back straight and move carefully to prevent a

sprain.

l When moving or lifting a chassis, hold the handle or bottom of the chassis. Do not hold the

handle of the installed modules in the chassis, such as the power module, fan module, or board.

2.8 Others

Inserting and Removing a Board

CAUTION

When inserting a board, wear the ESD wrist strap or gloves. Insert the board gently to prevent

any bent pins on the backplane.

l Insert the board along the guide rail.

l Avoid contact of one board with another to prevent short-circuit or damage.

l Do not remove the active board before powering off.

l When holding a board in hand, do not touch the board circuit, components, connectors, or

connection slots.

Bundling Signal Cables

CAUTION

Bundle the signal cables separately from high current or high voltage cables.

Cabling Requirements

At a very low temperature, movement of the cable may damage the plastic skin of the cable. To

ensure the safety during installation, comply with the following requirements:

l When installing cables, ensure that the ambient temperature is above 0oC.

l If cables are stored in the place below 0oC, move the cables into a place at a room

temperature and store the cables for more than 24 hours before installation.

l Move the cables with care, especially at a low temperature. Do not drop the cables directly

from the vehicle.

RNC




2-13




About This Chapter

This provides the definition of RNC commissioning. It also provides the prerequisites and

preparations to be made for RNC commissioning.

3.1 Definition of RNC Commissioning

The RNC commissioning refers to the commissioning of equipment, RNC loading, interfaces,

and services after the RNC hardware installation. This ensures that the RNC works as designed.

3.2 Prerequisites for RNC Commissioning

This describes the prerequisites for RNC commissioning: RNC equipment status and

commissioning network.

3.3 Preparations for RNC Commissioning

This describes how to obtain the installation software, license, and MML command scripts

required for RNC commissioning.

RNC

Commissioning Guide 3 Introduction to RNC Commissioning



3-1



3.1 Definition of RNC Commissioning

The RNC commissioning refers to the commissioning of equipment, RNC loading, interfaces,

and services after the RNC hardware installation. This ensures that the RNC works as designed.

3.2 Prerequisites for RNC Commissioning

This describes the prerequisites for RNC commissioning: RNC equipment status and

commissioning network.

Requirements for the State of the RNC Equipment

Before commissioning, ensure that the RNC meets the conditions listed in Table 3-1.

Table 3-1 Equipment status before commissioning

Item State

RNC hardware The hardware is installed and passes the hardware installation acceptance

and powering-on test.

BAM Configured before delivery. For details, refer to 5.1.4 Checklist for BAM

Software Settings Performed Before Delivery.

LMT The LMT computer meets the configuration requirements. For details, refer

to Computer Requirements of the LMT.

Requirements for the Commissioning Network

The network equipment in the commissioning network should meet the following requirements

to ensure smooth commissioning of the Iub, Iu, and Iur interfaces:

l At least one NodeB that has passed commissioning and that can provide basic functions is

connected to the local RNC.

l At least one set of CN equipment that has passed commissioning and that can provide basic

functions is connected to the local RNC.

l If the Iur interface is configured, another RNC that has passed commissioning is connected

to the local RNC.

l Three single-mode UEs and one dual-mode UE are ready for test and are registered in the

HLR.

Figure 3-1 shows a typical RNC commissioning network.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



Figure 3-1 Typical RNC commissioning network

l The figure shows only the connection. The quantity and type of cables are not involved.

l Figure 3-1 illustrates an example. There may be other commissioning scenarios, as listed

in Table 3-2.

Table 3-2 Other commissioning scenarios

Scenario Description

The RNC is connected to

the MGW, NodeB, or

another RNC.

When two NEs are in the same equipment room, connect them

directly.

The RNC is configured

with an alarm box.

Connect the alarm box to the RNC LMT that serves as the alarm

management system.

RNC

Commissioning Guide 3 Introduction to RNC Commissioning



3-3



3.3 Preparations for RNC Commissioning

This describes how to obtain the installation software, license, and MML command scripts

required for RNC commissioning.

Required Software

The required software is as follows:

l Setup disk of the BAM application that is consistent with the local office version

l Setup disk of the LMT application that is consistent with the local office version

Required License

Huawei technical support engineers apply for the license that is applicable to configuration in

the local office.

Required MML Command Scripts

Before RNC commissioning, complete the initial configuration according to the RNC Initial

Configuration Guide and obtain the MML command scripts. In addition, check the data

configuration according to the MML command script demonstration and the on-site negotiated

data defined in the RNC Initial Configuration Guide.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



4 Commissioning the RNC

This describes the RNC commissioning, including commissioning RNC hardware,

commissioning software loading, verifying all interfaces, verifying RNC services, and

integrating the RNC into the M2000.

Procedure

Step 1 Perform 5 Commissioning the RNC Equipment.

1. Perform 5.1 Commissioning BAMs.

2. Perform 5.2 Connecting the LMT.

3. Perform 5.3 Loading RNC Software and Data Files.

4. Perform 5.4 Activating and Verifying the RNC License.

Step 2 Perform 6 Handling Alarms During RNC Commissioning.

Step 3 Perform 7 Verifying Interfaces.

l Perform 7.1 Verifying the Iub Interface.

l Perform 7.2 Verifying the Iu-CS Interface.

l Perform 7.3 Verifying the Iu-PS Interface.

l Perform 7.4 Verifying the Iur Interface.

l Perform 7.5 Verifying the Iu-BC Interface.

Step 4 Perform 8 Verifying RNC Services.

Step 5 Perform 9 Integrating the RNC into the M2000.

----End

RNC

Commissioning Guide 4 Commissioning the RNC



4-1




About This Chapter

This describes how to commission the RNC equipment, including commissioning the BAM,

commissioning the RNC LMT, loading the RNC software and data files, verifying the RNC

license configuration, and verifying the switchover between active and standby RNC boards.

5.1 Commissioning BAMs

This task describes how to commission the BAMs, including verifying the BAM settings before

commissioning and installing the BAM software on site.

5.2 Connecting the LMT

This describes how to connect the RNC LMT, including checking the configuration of the RNC

LMT PC, installing the RNC LMT applications, connecting the RNC LMT to the BAM, and

starting the R NC LMT.

5.3 Loading RNC Software and Data Files

This describes how to load the host software and data during RNC commissioning.

5.4 Activating and Verifying the RNC License

This describes how to activate the RNC license and verify the license configuration information.

RNC

Commissioning Guide 5 Commissioning the RNC Equipment



5-1



5.1 Commissioning BAMs

This task describes how to commission the BAMs, including verifying the BAM settings before

commissioning and installing the BAM software on site.

Prerequisite

The setup disk of BAM application that is consistent with the local office version is obtained.

Procedure

Step 1 5.1.1 Obtain the Installation Information on the BAM Software

Before commissioning the BAM, obtain the Data Sheet of BAM Software Installation with

information already filled in.

Step 2 5.1.2 Remotely Logging In to the BAM

Before commissioning the BAM, remotely log in to the BAM on an operating terminal that can

run the mstsc.exe program.

Step 3 5.1.3 Checking BAM Software

Before commissioning the BAM, check the operating system and software setting of the BAM

to ensure that the BAM application is successfully installed and operational.

Step 4 5.1.4 Checklist for BAM Software Settings Performed Before Delivery

Before installing the BAM application, check the software installation and setting before

delivery of the BAM.

Step 5 5.1.5 Installing the BAM Application in the Active Workspace

Install the BAM application in the active workspace of the BAM. Install the BAM application

on all the BAMs of the RNC.

Step 6 5.1.6 Checking the Operation Status of the BAM Application

After installing the BAM application, check the operation of the BAM application including the

operation of the BAMService and SecurityManager.

Step 7 5.1.7 Installation Directory of the BAM Application

After installing the BAM software, check the data stored in the BAM installation directory. This

data includes the data related to the BAM application components, data related to the RNC host

software, and various data used or generated by the RNC.

----End

5.1.1 Obtain the Installation Information on the BAM Software

This describes how to obtain information about the operating system and the IP address of the

Ethernet adapter queue on the BAM software before installing the BAM application.

5.1.2 Remotely Logging In to the BAM

This describes how to remotely log in to the BAM by running a mstsc /parameter command

on a computer so that operation and maintenance can be performed on the BAM.

5.1.3 Checking BAM Software

This describes how to check the software on the BAM to ensure that the BAM application can be installed and executed properly.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



5.1.4 Checklist for BAM Software Settings Performed Before Delivery

This provides a checklist for BAM software settings before delivery. The checklist records the

BAM software installation and settings that are performed before delivery.

5.1.5 Installing the BAM Application in the Active Workspace

This describes how to install the BAM application in the active workspace. If the RNC isconfigured with two OMUa boards, the BAM application must be installed in the active

workspaces of both the boards.

5.1.6 Checking the Operation Status of the BAM Application

This describes how to check the operation status of the BAM application including the operation

status of the omud and the BAM service processes.

5.1.7 Installation Directory of the BAM Application

After the BAM application is installed, the BAM programs and data are stored in the installation

directory of the BAM application. The default installation path is ..\bam. The following items

are stored in the installation directory of the BAM application: the BAM application components,

the RNC host software, and various data used or generated by the RNC.

5.1.1 Obtain the Installation Information on the BAM Software

This describes how to obtain information about the operating system and the IP address of the

Ethernet adapter queue on the BAM software before installing the BAM application.

Procedure

Step 1 Before the installation, obtain the following information from Data Sheet of BAM Software

Installation.

l Administrator password of Windows Server 2003

l Fixed IP addresses of the internal and external networks

----End

5.1.2 Remotely Logging In to the BAM

This describes how to remotely log in to the BAM by running a mstsc /parameter command

on a computer so that operation and maintenance can be performed on the BAM.

Prerequisitel The BAM is started normally and enters the operating system.

l The com puter for remote login to the BAM is installed with Windows XP or a later version.

l The com puter for remote login to the BAM works and connects to the BAM external

network properly.

l The fixed IP address or the virtual IP address of the external network is obtained. For details

about the external IP addresses of the BAM, see Data Sheet of BAM Software Installation.

l When the computer used for remote login to the BAM is connected to the BAM through a

LAN, the IP address of this computer must be in the same network segment as one of the

BAM external IP addresses.

RNC




5-3



Context

You can log in to the BAM remotely only by running the mstsc /parameter command. The

parameter is determined by the version of the operating system of the computer through which

the BAM is remotely logged in to.

l If the operating system of the computer through which the BAM is remotely logged in to

is Windows Server 2000, Windows NT, Windows XP Service Pack 2 or earlier, run the

mstsc /console command.

l If the operating system of the computer through which the BAM is remotely logged in to

is Windows Server 2008, Windows Server 2003, Windows Vista Service Pack 1, or

Windows XP Service Pack 3, run the mstsc /admin command.

NOTE

If the version of the operating system of the computer through which the BAM is remotely logged in to is

unknown, choose Start > Run. Enter mstsc /? in the Run dialog box to check the parameter for logging

in to the BAM.

Assume that the operating system of the computer through which the BAM is logged in to

remotely is Windows XP Service Pack 2. Perform the following steps to log in to the BAM

remotely.

Procedure

Step 1 On the computer for remote login to the BAM, choose Start > Run. The Run dialog box is

displayed.

Step 2 Enter mstsc /console and click OK . The Remote Desktop Connection dialog box is displayed,

as shown in Figure 5-1.

CAUTION

When entering mstsc /console, leave a space between mstsc and /console.

Figure 5-1 Remote Desktop Connection dialog box

Step 3 Enter the external fixed IP address of the BAM for remote login, and then click Connect.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



NOTE

l If you remotely log in to the BAM before installing the BAM application, enter the fixed IP address

of the external network.

l If you remotely log in to the BAM after installing the BAM application, enter the virtual IP address of

the external network.

Step 4 Enter the name and password of an administrator-level user of the BAM, and then click OK to

remotely log in to the BAM.

CAUTION

By running the mstsc /console command, you can connect the BAM to only one computer. In

other words, another computer connected to the BAM in this way will be disconnected from the

BAM after you click OK on the computer.

----End

5.1.3 Checking BAM Software

This describes how to check the software on the BAM to ensure that the BAM application can

be installed and executed properly.

Procedure

Step 1 Check the version of Windows Server 2003 installed on the BAM. For details, see Checking theVersion of Windows Server 2003 on the BAM.

Step 2 Check and ensure that the system time and time zone of the BAM is consistent with the local

time.

----End

5.1.4 Checklist for BAM Software Settings Performed BeforeDelivery

This provides a checklist for BAM software settings before delivery. The checklist records the

BAM software installation and settings that are performed before delivery.

Table 5-1 Checklist for BAM software settings performed before delivery

Item Remarks

Setting the RAID 1

relationship between two

SAS hard disks on the

OMUa board

-

Installing Windows Server

2003

The default password of the administrator of the active and

standby BAMs is 11111111.

RNC




5-5



Item Remarks

Activating the License of

Windows Server 2003

-

Installing the IPMI driver -

Installing Windows memory

diagnosis driver

-

Starting the Routing and

Remote Access service

The Routing and Remote Access service is started and Startup

Type is set to Automatic.

Disabling the Windows

Time service

-

Disabling the Computer

Browser service

-

Starting the Terminal

Services service

The Terminal Services service is started and Startup Type is

set to Automatic.

Enabling remote login -

Installing the teaming driver

of Intel 82571 Ethernet

adapters

-

Installing the Teaming

Driver of BACS Ethernet

adapters

-

Configuring commissioning

IP addresses of the active

and standby BAMs

The preset commissioning IP address is: 192.168.6.50

(255.255.255.0)

Installing the iPSI SEK

SetWin Software

-

5.1.5 Installing the BAM Application in the Active Workspace

This describes how to install the BAM application in the active workspace. If the RNC isconfigured with two OMUa boards, the BAM application must be installed in the active

workspaces of both the boards.

Prerequisite

l You have logged in to the BAM in remote mode. For details, see 5.1.2 Remotely Logging

In to the BAM.

l 5.1.3 Checking BAM Software is complete.

l 5.1.1 Obtain the Installation Information on the BAM Software is complete.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



l The installation CD-ROM of the BAM application is obtained, and the files on the setup

disk are copied to the BAM hard disk in directory sharing mode. The BSC6810V200R011

installation CD-ROM is shipped with the OMUa board.

ContextYou can install the BAM application in the following ways:

1. Run the install_bam.exe program in the BAM installation package, and then set the

parameters during the installation process.

2. Configure the parameters in the install_info.ini file in the BAM installation package, and

then run the install_bam.exe program to install the BAM application.

NOTE

Huawei recommends the first way to install the BAM application.

Procedure

Step 1 Double-click the install_bam.exe program in the BAM installation package. The following

information is displayed.

# The name of office

# The name must range from 8 to 32(characters);

# The first character must be a letter and the subsequent characters must beletters, digits, "-", "_".

# If you don't know it, please consult the administrator.

Please input a valid office_name :

Step 2 Type the office_name and press Enter.

Step 3 Choose the language version and press Enter.

# The BAM language version. eg: eng/chs

Please input a valid version :

Step 4 Enter the admin password and press Enter.

# The admin's password of bam service

# The password must range from 6 to 32(characters) and can only consist of lettersand figures.

# The password should be remembered.

# You can change it later, but this password should be provided first.

Please input a valid admin_password :

Step 5 Type the admin password again to confirm the validity of the password and press Enter.

# The admin's password of bam service

# The password must range from 6 to 32(characters) and can only consist of letters

and figures.

# The password should be remembered.# You can change it later, but this password should be provided first.

Please input a valid admin_password :

Please input a valid Confirm password :

Step 6 Type the ftp password and press Enter.

# The ftp user's password of bam service

# The password must range from 6 to 32(characters) and can only consist of letters

and figures.

# The password should be remembered.# You can change it later, but this password should be provided first.

Please input a valid ftp_password :

Step 7 Type the ftp password again to confirm the validity of the password and press Enter.

# The ftp user's password of bam service

# The password must range from 6 to 32(characters) and can only consist of lettersand figures.

RNC




5-7



# The password should be remembered.

# You can change it later, but this password should be provided first.

Please input a valid ftp_password :Please input a valid Confirm password :

Step 8 Type the virtual extra net ip and press Enter.

# The virtual extra net ip.Please input a valid virtual_extranet_ip :

Step 9 Choose the install_type accordingly. For details, see Table 5-2.

# The BAM system type. eg: Single/Dual# Single : Install stand-alone system

# Dual : Install dual system

# The dual-BAM system can efficiently increase the reliability of the BAM system.

Please select the type to install.Please input a valid install_type :

Table 5-2 Description

Parameter Meaning Remarks

Single The RNC is configured with

one OMU, which works in

single mode.

When the RNC is configured

with one OMUa board, select

this option.

Dual The RNC is configured with

two OMUs, which work in

dual mode.

When the RNC is configured

with two OMUa boards,

select this option.

Step 10 The BAM application is being installed. When the Install bam succeed! message is

displayed, the installation is complete.

----End

5.1.6 Checking the Operation Status of the BAM Application

This describes how to check the operation status of the BAM application including the operation

status of the omud and the BAM service processes.

Procedure

Step 1 Check the omud status1. Choose Start > All programs > Administrative Tools > Services, and then check the

omud status in the displayed window.

l If State is started, you can infer that the installation is successful and the omud is

running properly.

l If State is not started, you can infer that the omud is not started after the installation

of the BAM application. In this case, right-click omud, and then choose Start from the

shortcut menu.

Step 2 Check the status of the BAM service processes

1. Press Ctrl+Alt+Del. The Windows Security dialog box is displayed.

2. Click Task Manager. The Windows Task Manager dialog box is displayed.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



3. Click the Processes tab. If the processes are displayed in the Image Name pane, you can

infer that the processes are started.

----End

5.1.7 Installation Directory of the BAM ApplicationAfter the BAM application is installed, the BAM programs and data are stored in the installation

directory of the BAM application. The default installation path is ..\bam. The following items

are stored in the installation directory of the BAM application: the BAM application components,

the RNC host software, and various data used or generated by the RNC.

Directory Structure

l If the BAM application is installed only on the active workspace, the directory structure is

similar to that shown in Figure 5-2.

l

If the BAM application is installed on both the active workarea and the standby workspace,the directory structure is similar to that shown in Figure 5-3. The structure of the

version_a and version_b folders must be the same.

Figure 5-2 Directory structure of BAM application on the active workarea

RNC




5-9



Figure 5-3 Directory structure of BAM application on the active and standby workareas

CAUTION

Do not delete any file in the installation directory of the BAM application, because it may have

a severe impact on the system performance.

File Folders

Table 5-3 lists the file folders.

Table 5-3 File folders of the BAM application

Folder Name Description

common\fam\famlogfmt Stores the trace files of the host.

common\fam\famlog Stores FAM operation logs to be loaded to the BAM server.

common\ems Stores the M2000-related data.

common\fam\fad Stores diagnostic results to be loaded to the BAM server.

common\services Stores the common programs of the active and standby

workspaces.

patch Stores the patch programs for remote upgrade.

bin\bam Stores the configuration files and patches for the BAM.

bin\fam Stores the BIN files.

data\backup\data_backup

\db_data

Stores configuration data in DB format for RNC backup.

data\backup\data_backup

\mml

Stores configuration data in MML format for RNC backup.

data\backup\data_restore

\db_data

Stores the configuration data in DB format for restoration.

The data is downloaded from the M2000.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



Folder Name Description

data\backup\data_restore

\mml

Stores the configuration data in MML format for

restoration. The data is downloaded from the M2000.

version_a\ems\eqparch Stores equipment documents.

version_a\ems\pm

\default_meas

Stores default performance measurement counters.

version_a\ems\pm

\default_meas_sync

Stores default measurement counters for synchronization.

version_a\ems\pm

\meas_definition

Stores performance definition.

version_a\ems\pm

\meas_result

Stores performance measurement results.

version_a\ems\pm

\meas_result_list

Stores performance measurement result lists.

version_a\ems\pm

\nastart_result

Stores the measurement results obtained by Nastar.

ftp\cert Stores the certificate for ftp security strategy.

ftp\device_file Stores the device files exported from the RNC.

ftp\export_cfgxml Stores exported data configuration files.

ftp\export_xmlfile Stores files exported from the database.ftp\license Stores the inactivated license file.

version_a\license Stores the activated license file.

version_a\log Stores the operation logs of the BAM.

common\fam\smlc Stores the single-point positioning information generated

after the single-point positioning.

5.2 Connecting the LMTThis describes how to connect the RNC LMT, including checking the configuration of the RNC

LMT PC, installing the RNC LMT applications, connecting the RNC LMT to the BAM, and

starting the RNC LMT.

Prerequisite

The RNC BAM has passed the commissioning.

1. 5.2.1 Checking Computer Configuration of the RNC LMT

This describes how to check computer configuration of the RNC LMT to ensure that the

requirements are satisfied.

RNC




5-11



2. 5.2.2 Installing the RNC LMT Application

This describes how to install the RNC LMT application. This task takes

V200R011C00SPC100 as an example.

3. 5.2.3 Connecting the RNC LMT to the BAM

This describes how to connect the LMT to the OM network by providing an example of connecting the LMT to the BAM through the LAN. This task is only performed before the

LMT is used for the first time.

4. 5.2.4 Starting the Local Maintenance Terminal of the RNC

This describes how to start the LMT and connect it to the specified RNC. This task takes

the Local user account as an example to describe how to log in to the RNC on the LMT.

5.2.1 Checking Computer Configuration of the RNC LMT

This describes how to check computer configuration of the RNC LMT to ensure that the

requirements are satisfied.

Procedure

Step 1 Check the hardware configuration of the RNC LMT to ensure that the requirements in Computer

Requirements of the LMT are satisfied.

----End

5.2.2 Installing the RNC LMT Application

This describes how to install the RNC LMT application. This task takes V200R011C00SPC100

as an example.

Prerequisitel The setup disk and the instructions on the LMT application installation are available.

Huawei provides both the disk and the instructions.

l The valid CD-KEY of the LMT application is available.

l The PC on which the LMT application will be installed meets all the requirements listed

in Computer Requirements of the LMT.

Procedure

Step 1 Use the administrator account to log in to the Windows XP operating system.

Step 2 Insert the setup disk into the CD-ROM drive.

l The setup program runs automatically. A dialog box is displayed, as shown in Figure 5-4.

l If the setup program fails to run automatically, double-click setup.bat or setup.vbs in the

directory of the setup disk. A dialog box is displayed, as shown in Figure 5-4.

Figure 5-4 Selecting a setup language


RNC

Commissioning Guide



Issue 03 (2010-03-25)



CAUTION

If the setup languages of the LMT and BAM applications are different, some functions are

unavailable, for example, managing the RNC LMT operator accounts. It is recommended to

keep the two languages consistent.

Step 3 Select a language for the installation, and then click OK to start up.

Step 4 Click Next. A dialog box is displayed, as shown in Figure 5-5.

Figure 5-5 Copyright notice

Step 5 Read the copyright notice. If you accept the agreement terms, select I accept these terms, andthen click Next. The installation directory is displayed, as shown in Step 6. If you do not accept

the agreement terms, click Cancel to quit the installation.

Step 6 Use the default directory or set up a new directory, and then click Next.

l If the installation directory does not exist, a dialog box is displayed, prompting whether to

create the directory. Click Yes. A dialog box is displayed, as shown in Figure 5-6.

l If the installation directory exists, A dialog box is displayed, as shown in Figure 5-6.

RNC




5-13



Figure 5-6 Selecting software components

NOTE

The default installation path is D:\HW LMT. If the LMT application of other versions or of other Network

Elements (NEs) has already been installed, the default installation path is the path of the previousinstallation and cannot be changed. To change the installation path, you must uninstall the existing LMT

application.

If an LMT application is running, the Warning dialog box is displayed. If you click Yes, the LMT

application is automatically stopped. If you click No, you need to manually stop the LMT application.

Step 7 Select the software components and then click Next. It is recommended that you select all

components. A dialog box is displayed for entering the CD-KEY.

Step 8 Enter the CD-KEY correctly, and then click Next. A dialog box is displayed for confirming the

installation, as shown in Figure 5-7.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



Figure 5-7 Confirming installation

Step 9 Confirm the installation parameters and click Next. A dialog box is displayed for copying files.

When the task of copying files is complete, a dialog box is displayed for initializing components.

When all programs are installed, the dialog box for completing the installation is displayed.

Step 10 Click Finish.

NOTE

The installation is complete. When the installation is complete, the LMT Service Manager automatically

starts.

----End

5.2.3 Connecting the RNC LMT to the BAM

This describes how to connect the LMT to the OM network by providing an example of

connecting the LMT to the BAM through the LAN. This task is only performed before the LMT

is used for the first time.

Prerequisite

l The BAM communicates with the RNC host properly.

l The physical connection between the LMT and the BAM is established and functional.

Context

You can connect the LMT to the BAM through a LAN or a router.

RNC




5-15



Procedure

Step 1 To set the IP address of the LMT PC, refer to Setting the IP Address of the RNC LMT PC.

Step 2 On the LMT PC, choose Start > Run, enter the cmd command in the Run dialog box, and then

press Enter. The cmd.exe window is displayed.

Step 3 Enter ping BAM external virtual IP address in the cmd.exe window.

If the window displays similar information as follows, the communication between the LMT

and the BAM is functional. The task is complete. In this example, the external virtual IP address

of the BAM is 10.161.197.206.

Pinging 10.161.197.206 with 32 bytes of data:Reply from 10.161.197.206: bytes=32 time<1ms TTL=125

Reply from 10.161.197.206: bytes=32 time<1ms TTL=125

Reply from 10.161.197.206: bytes=32 time<1ms TTL=125

Reply from 10.161.197.206: bytes=32 time<1ms TTL=125Ping statistics for 10.161.197.206:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

----End

5.2.4 Starting the Local Maintenance Terminal of the RNC

This describes how to start the LMT and connect it to the specified RNC. This task takes the

Local user account as an example to describe how to log in to the RNC on the LMT.

Prerequisite

l The physical link connecting the LMT to the BAM is established.

l The LMT application is installed correctly.

Context

WARNING

When the LMT application is running, do not modify the system time. Otherwise, serious errors

may occur on the system. If you have to modify the system time, stop all the LMT applicationfirst.

Procedure

Step 1 Choose Start >All Programs >Huawei Local Maintenance Terminal >Local Maintenance

Terminal. The User Login dialog box is displayed, as shown in Figure 5-8.

If this is the first time to start the LMT? Then...

Yes Go to Step 2.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



If this is the first time to start the LMT? Then...

No Select the office to be connected in the Office

drop-down list, and then go to Step 6.

Figure 5-8 User Login dialog box

NOTE

l Click Offline to log in to the LMT offline. In this way, you do not log in to the BAM, but still can

perform part of the functions of the LMT. For example, you can browse the online help.

l Click Exit to exit the LMT.

Step 2 Click . The Office Management dialog box is displayed, as shown in Figure 5-9.

Figure 5-9 Office Management dialog box before adding an office

RNC




5-17



Step 3 Click Add. The Add dialog box is displayed, as shown in Figure 5-10.

Figure 5-10 To add an office, perform the following steps:

Step 4 Set the office name and enter the external virtual IP address of the BAM. Click OK . The system

returns to the Office Management dialog box shown in Figure 5-11.

NOTE

If the LMT PC is installed with the LMTs of other Network Elements (NEs) such as SGSN, you can selectone NE from the NE Type drop-down list, and then set the office for the NE.

Figure 5-11 Office Management dialog box after adding an office

Step 5 In the Office Management dialog box, click Close. The system returns to the User Login dialog box, as shown in Figure 5-12.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



Figure 5-12 User Login dialog box

Step 6 Enter the user name and password, and then click Login. The main interface of the Local

Maintenance Terminal is displayed.

NOTE

l Before logging in to an NE as an EMS user on the LMT, you need to set up the connection between

the NE and the M2000 server.

l If the LMT communicates with the BAM through the M2000 Proxy Server, select the Proxy Server

in the User Login dialog box and then enter the IP address of the proxy server.

l Log in with the account of admin for the first login. The password is set during the installation of theBAM application.

l If you log in to the LMT in Offline mode, you can use only a part of functions, such as viewing MML

command help.

----End

5.3 Loading RNC Software and Data Files

This describes how to load the host software and data during RNC commissioning.

Prerequisite

l The commissioning of the BAM and the RNC LMT is complete.

l The MML command scripts applicable to the local office are available.

5.3.1 Generating the RNC Data File

This describes how to generate the RNC data file, which can be loaded, by using the MML

command data scripts.

5.3.2 Setting RNC Loading Modes (Commissioning)

This task describes how to set the loading mode of subsystems of all the boards before resetting

RNC boards.

5.3.3 Loading the RSS Subrack

RNC




5-19



This task describes how to load the RSS host software and data files in BAM Installation

Directory to the RSS subrack.

5.3.4 Loading the RBS Subrack

This describes how to load the host software and data files in BAM Active Workspace Installation

Directory to the RBS subrack.

5.3.1 Generating the RNC Data File

This describes how to generate the RNC data file, which can be loaded, by using the MML

command data scripts.

Prerequisite

l The RNC LMT is started and properly communicates with the BAM.

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

are precise and complete.

Context

The generated subrack loading file is saved in BAM Active Workspace Installation Directory

\bam\version_a\bin\fam. The file name is in ABCXXYYZZ .DAT format, such as

XPU000200.DAT. Table 5-4 lists the detailed information.

Table 5-4 Name of the loading file

Parameter Indication

ABC Board name, such as XPUa.

XX Subrack number.

YY Slot number.

ZZ Subsystem number

Procedure

Step 1 On the RNC LMT, run the SET OFFLINE command and set all the subracks to the offline

mode.

Step 2 Run the RST DATA command. A dialog box is displayed. Click Yes to initialize the RNC

configuration data in the BAM database. The Execution succeeded message is displayed.

Step 3 On the main menu of the Local Maintenance Terminal, choose System > Batch

Commands. The running commands in batches window is displayed, as shown in Figure

5-13.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



Figure 5-13 Running commands in batches

Step 4 In the Immediate Batch Command tab page, click Open. The Open dialog box is displayed.

Select the prepared MML command data script. Click Open. The selected script is displayed in

the Immediate Batch Command window.

Step 5 Click Set. The setting batch commands dialog box is displayed. Set Sending Commands

Interval (s) to 0. Select Save Failed Results, and then set the save path of the unsuccessful

commands. Click OK to complete the setting of the batch commands, as shown in Figure

5-14.

Figure 5-14 Setting the batch commands

Step 6 In the window of the batch commands, set Execution Type to Execute All, as shown in Figure

5-15.

RNC




5-21



Figure 5-15 Setting the execution type

Step 7 Click Go. The system runs the MML commands one by one.

NOTE

Click OK when the system prompts that the current configuration is in offline mode. The execution of MML

commands may take a long time.

Step 8 Click OK when the system prompts that the running of all the MML commands is complete.

The running result is shown in Figure 5-16.

Figure 5-16 Running result of immediate batch commands

NOTE

If the number of Failure in Total Results is not 0, modify the MML command script and go to Step 1 to run

the commands again.

Step 9 Run the FMT DATA command to set Format type to ALL_SUBRACK (Format all

subracks) for formatting all the subracks.

The Execution succeeded message is displayed. The generated data file can be obtained

in the loading path of the BAM.

Step 10 Run the SET ONLINE command to set all the subracks to the online mode.

----End

5.3.2 Setting RNC Loading Modes (Commissioning)

This task describes how to set the loading mode of subsystems of all the boards before resetting

RNC boards.

Prerequisite

The RNC LMT is started and properly communicates with the BAM.

Context

For details about how to set the RNC loading mode, refer to RNC Loading Management.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



Procedure

Step 1 On the MML client, run the SET LODCTRL command to set Board start load control. to

LFB (Load from BAM and write flash). The setting of the RNC loading modes is complete

when the Execution succeeded message is displayed.

----End

5.3.3 Loading the RSS Subrack

This task describes how to load the RSS host software and data files in BAM Installation

Directory to the RSS subrack.

Prerequisite

l The RSS host software and data files in BAM Active Workspace Installation Directory

\bam\version_a\bin\fam are ready.


l The loading progress window is started. For details, refer to Monitoring the Loading

Progress Window.

Context

The process of loading the RSS subrack lasts three to five minutes.

Procedure

Step 1 Check whether the RSS subrack is powered on.

If... Then...

The RSS subrack is not powered on. Go to Step 2.

The RSS subrack is powered on. Go to Step 3.

Step 2 Switch on the power distribution boxes to power on the RSS. Find the relationship between the

switches and subracks on the front panel of the power distribution box. The boards in the RSS

subrack automatically load the host software and data file from the BAM. Go to Step 4.

Step 3 On the MML client, run the RST SUBRACK command to set Subrack No. to 0. A dialog is

displayed, asking you whether to proceed. Click Yes. The boards in the RSS subrack

automatically load the host software and data file from the BAM.

Step 4 Observe the loading progress of the associated RSS subrack in Progress Management.

Step 5 After the loading of the RSS subrack, click the Device Panel tab in the navigation tree and then

double-click the shelf node to be queried. The device panel is displayed, as shown in Figure

5-17.

RNC




5-23



Figure 5-17 Device panel

If... Then...

The device panel displays the valid

status of the boards,

The loading of the RSS subrack is complete.

The device panel displays the invalid


Troubleshoot according to the prompt. For details,

refer to 11.10 Troubleshooting: RNC Boards

Loading Failures.

Step 6 Observe the signaling connection setup on the Iub interface and cell setup in the message tracing

window.

If... Then...

The setup process is correct, End this task.

The setup process is incorrect, Troubleshoot according to the prompt. For details, refer to

11.8 Troubleshooting: Signaling Link Failures on the

Iub Interface or 11.7 Troubleshooting: Cell SetupFailures.

----End

5.3.4 Loading the RBS Subrack

This describes how to load the host software and data files in BAM Active Workspace Installation

Directory to the RBS subrack.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



Prerequisite

l The RBS host software and data files in BAM Active Workspace Installation Directory

\bam\version_a\bin\fam are ready.


l The message tracing window is started. For details, refer to Starting the RNC Message

Tracing (Commissioning).

l The loading progress window is started. For details, refer to Monitoring the Loading

Progress Window.

l The RSS subrack is loaded and operational.

Context

The process of loading one RBS subrack lasts three to five minutes.

ProcedureStep 1 Check whether the RBS subrack is powered on.

If... Then...

The RBS subrack is not powered on, Go to Step 2.

The RBS subrack is powered on, Go to Step 3.

Step 2 Switch on the power distribution box to power on the RBS subrack. Find the relationship between

the switches and subracks on the front panel of the power distribution box. The boards in theRBS subrack automatically load the host software and data file from the BAM. Go to Step 4.

Step 3 On the MML client, run the RST SUBRACK command to set Subrack No. to Number of the

RBS to be loaded . A dialog box is displayed, asking whether to proceed. Click Yes. The boards

in the RBS subrack automatically load the host software and data file from the BAM.

Step 4 Observe the loading progress of the associated RBS subrack in the Progress Management

window.

Step 5 After the current RBS subrack is loaded, go to Step 3 to load other RBS subracks until all the

RBS subracks of the RNC are loaded.

Step 6 After all the RBS subracks are loaded, click the Device Panel tab in the navigation tree, andthen double-click the shelf node to be queried. The device panel is displayed, as shown in Figure

5-18.

RNC




5-25



Figure 5-18 Device panel

If... Then...

The device panel displays the valid


The loading of the RBS subrack is complete.

The device panel displays the invalid


Troubleshoot according to the prompt. For details,

refer to 11.10 Troubleshooting: RNC Boards

Loading Failures.

Step 7 Observe the signaling connection setup on the Iub interface and cell setup in the message tracing

window.

If... Then...

The setup process is correct, End this task.

The setup process is incorrect, Troubleshoot according to the prompt. For details, refer to

11.8 Troubleshooting: Signaling Link Failures on the

Iub Interface or 11.7 Troubleshooting: Cell SetupFailures.

----End

5.4 Activating and Verifying the RNC License

This describes how to activate the RNC license and verify the license configuration information.

Prerequisite

l The LMT is started and properly communicates with the BAM.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



l The communication between the RNC FAM and the BAM is operational.

l The license of the local office is in BAM Active Workspace Installation Directory\FTP

\License and the file name is license.dat.

Procedure

Step 1 On the RNC LMT, run the LST LICENSE command and enter 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 that applied, Go to Step 2.

The license is inconsistent with that applied, Contact Huawei for confirmation.

Step 2 Run the LST CFGMODE to query the data configuration of all the subracks. If the subrack is

in offline mode, run the SET ONLINE command to set the subrack to the online mode.

Step 3 Run the ACT LICENSE command to activate the licenses of all telecom operators. The

activation is performed in sequence from the primary telecom operator to the secondary telecom

operator. If there are multiple telecom operators, run the command repeatedly.

Step 4 Run the CMP LICENSE command to check whether the license of the host and that of the

BAM are consistent.

If... Then...

The two licenses are consistent, End this task.

The two licenses are inconsistent, Go to Step 5.

Step 5 Run the DSP LICENSE command to check whether the license data of the host is consistent

with that applied.

If... Then...

The query result is consistent with the actual

configuration,

End this task.

The query result is inconsistent with the actual

configuration,

Contact Huawei for confirmation.

----End

RNC




5-27



6 Handling Alarms During RNC

Commissioning

This describes how to handle alarms reported during RNC commissioning.

Prerequisite



Procedure

Step 1 On the main menu of the LMT, choose Fault Management > Browse Alarm. A window is

displayed, as shown in Figure 6-1.

RNC

Commissioning Guide 6 Handling Alarms During RNC Commissioning



6-1



Figure 6-1 Alarm browser

Step 2 Check whether there are any alarms in the alarm browser window.

If... Then...

There is no alarm in the alarm browser window, End this task.

There are alarms in the alarm browser window, Go to Step 3.

Step 3 Double-click the alarm to be handled in the alarm browse window. A dialog box is displayed,

as shown in Figure 6-2.

6 Handling Alarms During RNC Commissioning

RNC

Commissioning Guide



Issue 03 (2010-03-25)



Figure 6-2 Detailed alarm information

Step 4 Click Solution. The LMT Help System window is displayed.

Step 5 Follow the suggestions to handle the alarm in the Alarm Handling part.

NOTE

If the alarm cannot be cleared, contact Huawei for technical support.

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

----End

RNC

Commissioning Guide 6 Handling Alarms During RNC Commissioning



6-3




About This Chapter

This describes how to verify at the RNC that the Iub, Iu-CS, Iu-PS, and Iur interfaces are

operational.

7.1 Verifying the Iub Interface

This task describes how to verify that the Iu b interface is operational. The verification is

performed at the RNC. The Iub interface verification varies according to the transport mode over

the Iub interf ace.

7.2 Verifying the Iu-CS Interface

This task describes how to verify that the Iu-CS interface is operational. The verification is

performed at the RNC.

7.3 Verifying the Iu-PS Interface

This describes how to verify that the Iu-PS interface is operational. The verification is performed

at the RNC.

7.4 Verifying the Iur Interface

This describes how to verify that the Iur interface is operational. The verification is performed

at the RNC.

7.5 Verifying the Iu-BC Interface

This describes how to verify that the Iu-PS interface is operational. The verification is performed

at the RNC. Irrespective of whether the ATM transmission or IP transmission is used, the

verification is the same.

RNC

Commissioning Guide 7 Verifying Interfaces



7-1



7.1 Verifying the Iub Interface

This task describes how to verify that the Iub interface is operational. The verification is

performed at the RNC. The Iub interface verification varies according to the transport mode over

the Iub interface.

7.1.1 Verifying the Iub Interface (over ATM)

This describes how to verify that the control plane and user plane on the ATM-based Iub interface

is operational.

7.1.2 Verifying the Iub Interface (over IP)

This describes how to verify that the control plane and user plane on the IP-based Iub interface

are operational.

7.1.3 Verifying the Iub Interface (over ATM and IP)

This task describes how to verify that the Iub interface is operational when ATM/IP dual stack- based transport is applied. The verification is performed at the RNC. This task takes one NodeB

as an example to describe the verification of the Iub interface (over ATM and IP). To verify the

ATM/IP dual stack-based Iub interface between the RNC and another NodeB, repeat this

procedure.

7.1.1 Verifying the Iub Interface (over ATM)

This describes how to verify that the control plane and user plane on the ATM-based Iub interface

is operational.

Prerequisitel The communication between the RNC FAM and the BAM is operational.

l The RSS subrack and all the RBS subracks are operational.


Procedure

Step 1 Run the DSP SAALLNK command.

Expected result: Operation state is Available.

Step 2 Run the DSP IUBCP command.


Step 3 Run the DSP ADJNODE command.

Expected result: QAAL2 state is Available.

Step 4 On the MML client, run the DSP AAL2PATH command to query the state of the AAL2 path.

Expected result:

The Operation state is Available.

If The Operation state is Unavailable, Check whether the Iub interface data configuration is

correct.

l If it is incorrect, reconfigure the Iu-CS interface data.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



l If it is correct, go to 11.1 Verifying Physical Links on the Terrestrial Interface at the

RNC (over ATM).

Step 5 Optional: If service setup over one AAL2 path fails, perform Virtual Connect Link (VCL)

continuity check on the AAL2 path.

NOTE

l The peer end (NodeB, MGW, MSC, SGSN, or RNC) must support the F5 OAM protocol.

l Only the VCL that carries the SAAL link, IPoA PVC, and AAL2 path supports the continuity check.

Table 7-1 Performing continuity check on AAL2 paths

Step Action

b-1 Run the ACT VCLCC command to activate the continuity check on the AAL2

path.

b-2 Run the DSP VCLCC command, and set Link type to AAL2PATH.Expected result: all the following items are Normal.

If the result of any following items is Alarm, go to 11.1 Verifying Physical Links

on the Terrestrial Interface at the RNC (over ATM).

l LOC alarm

l AIS alarm

l RDI alarm

l CC activated failure alarm

l CC deactivated failure alarm

l LB failure alarm

b-3

(option

al)

To keep the VCL continuity check, end this task. Otherwise, run the DEA

VCLCC command.

1. Perform continuity check on the IPoA PVC.

Step 6 Optional: If Operation and Maintenance channel of one IPoA PVC set failed, Perform continuity

check on the IPoA PVC.

Table 7-2 Performing continuity check on the IPoA PVC

Step Action

c-1 Run the ACT VCLCC command to activate the continuity check on the IPoA PVC.

RNC




7-3



Step Action

c-2 Run the DSP VCLCC command, and set Link type to IPOA PVC.

Expected result: all the following items are Normal.

If the result of any following items is Alarm, go to 11.1 Verifying Physical Linkson the Terrestrial Interface at the RNC (over ATM).

l LOC alarm

l AIS alarm

l RDI alarm



l LB failure alarm

c-3

(option

al)


VCLCC command.

----End

7.1.2 Verifying the Iub Interface (over IP)

This describes how to verify that the control plane and user plane on the IP-based Iub interface

are operational.

Prerequisite




Procedure

Step 1 For each SPU subsystem where the SCTP is terminated on the Iub interface, run the DSP

SCTPLNK command.


Step 2 Run the DSP IUBCP command.


Step 3 On the MML client, run the DSP IPPATH command to query the state of all the IP paths over

the Iub interface.


If the Operation state is Unavailable, check whether the Iub interface data configuration is

correct and then go to 11.2 Verifying Physical Links on the Terrestrial Interface at the RNC

(over IP)


RNC

Commissioning Guide



Issue 03 (2010-03-25)



NOTE

If FG2a or GOUa serves as the interface board, go to 11.3 Conducting BFD/ARP Connectivity Check

on the Gateway of the FE/GE Port. If the Iub interface data configuration is correct, end this task; if the

Iub interface data configuration is incorrect, go to 11.2 Verifying Physical Links on the Terrestrial

Interface at the RNC (over IP).

Step 4 Optional: If the Iub interface is configured with the transmission resource group, run the DSP

RSCGRP command to query the states of all the transmission resource groups.

l Set Subrack No. to the number of the subrack where the resource group to be queried is

located.

l Set Slot No. to the number of the slot to which the Iub interface to be queried is connected.

l Set Resource Group No. to the number of the transmission resource group to be queried.

Expected result: Number of Paths in Resource Group is not 0.

----End

7.1.3 Verifying the Iub Interface (over ATM and IP)

This task describes how to verify that the Iub interface is operational when ATM/IP dual stack-

based transport is applied. The verification is performed at the RNC. This task takes one NodeB

as an example to describe the verification of the Iub interface (over ATM and IP). To verify the

ATM/IP dual stack-based Iub interface between the RNC and another NodeB, repeat this

procedure.

Prerequisite

l The RNC hardware has passed the commissioning.

l

The RNC and the NodeB are physically connected, that is, the connection has passed thehardware installation acceptance.

l All the cells are set up on the NodeB.

Context

When applying for transmission resources, the RNC can determine whether ATM transport or

IP transport is used to carry the current services according to the TRM mapping. To verify the

ATM/IP dual stack-based Iub interface is to verify the ATM-based Iub interface and the IP-

based Iub interface respectively.

Procedure

Step 1 Verify the control plane and user plane on the Iub interface.

l When the ATM transport is applied, refer to 7.1.1 Verifying the Iub Interface (over

ATM).

l When the IP transport is applied, refer to 7.1.2 Verifying the Iub Interface (over IP).

----End

7.2 Verifying the Iu-CS Interface

This task describes how to verify that the Iu-CS interface is operational. The verification is performed at the RNC.

RNC




7-5



7.2.1 Verifying the Iu-CS Interface (over ATM)

This describes how to verify that the control plane and user plane on the ATM-based Iu-CS

interface are operational.

7.2.2 Verifying the Iu-CS Interface (over IP)This describes how to verify that the control plane and user plane on the IP-based Iu-CS interface

are operational.

7.2.1 Verifying the Iu-CS Interface (over ATM)

This describes how to verify that the control plane and user plane on the ATM-based Iu-CS


Prerequisite




Procedure

Step 1 On the MML client, run the DSP SAALLNK command.


Step 2 Run the DSP MTP3LNK command.


Step 3 Run the DSP SSN command.

Expected result: SSN state is Allowed.

Step 4 Run the DSP N7DPC command.

Expected result:SCCP DSP state is Accessible.


Expected result: The value of Operation state is Available and the available bandwidth cannot

be all 0.

Step 6 Run the LST CNNODE command.

Expected result: The value of CN domain ID is CS_DOMAIN.

Step 7 On the MML client, run the DSP AAL2PATH command.


If Operation state is Unavailable, Check whether the Iu-CS interface data configuration is

correct.



RNC (over ATM).

Step 8 Optional: If service setup over one AAL2 path fails, perform VCL continuity check on theAAL2 path.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



NOTE




Step Action


path.

b-2 Run the DSP VCLCC command, and set Link type to AAL2PATH. Expected

result: all the following items are Normal.

l LOC alarm

l AIS alarm

l RDI alarm



l LB failure alarm

NOTEIf the result of any previous items is Alarm, go to 11.1 Verifying Physical Links on the

Terrestrial Interface at the RNC (over ATM).

b-3

(option

al)


VCLCC command.

----End

7.2.2 Verifying the Iu-CS Interface (over IP)

This describes how to verify that the control plane and user plane on the IP-based Iu-CS interface

are operational.

Prerequisite




Procedure

Step 1 On the MML client, run the DSP N7DPC command.



Expected result: The value of available bandwidth are not all 0.


RNC




7-7



Expected result: The value of CN domain ID is CS_DOMAIN.

Step 4 For each SPU subsystem where the SCTP is terminated on the Iu-CS interface, run the DSP

SCTPLNK command.

Expected result: Operation state is Normal.

Step 5 Run the DSP M3LKS command.


Step 6 On the MML client, run the DSP IPPATH command to query the state of the IP path.


If the Operation state is Unavailable,check whether the Iu-CS interface data configuration is

correct, and then go to 11.2 Verifying Physical Links on the Terrestrial Interface at the RNC

(over IP).

NOTE


on the Gateway of the FE/GE Port . If the Iu-CS interface data configuration is correct, end this task; if

the Iu-CS interface data configuration is incorrect, go to 11.2 Verifying Physical Links on the Terrestrial


Step 7 Run the DSP IPRT command.

Expected result: the associated route information is in place.

----End

7.3 Verifying the Iu-PS InterfaceThis describes how to verify that the Iu-PS interface is operational. The verification is performed

at the RNC.

7.3.1 Verifying the Iu-PS Interface (over ATM)

This describes how to verify that the control plane and user plane on the ATM-based Iu-PS


7.3.2 Verifying the Iu-PS Interface (over IP)

This describes how to verify that the control plane and user plane on the IP-based Iu-PS interface

are operational.

7.3.1 Verifying the Iu-PS Interface (over ATM)

This describes how to verify that the control plane and user plane on the ATM-based Iu-PS


Prerequisite



l

The RNC LMT is started and properly communicates with the BAM.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



Procedure

Step 1 Run the DSP SAALLNK command.







Expected result: SCCP DSP state is Accessible.


Expected result: The value of Operation state is Available and the available bandwidth cannot

be all 0.


Expected result: The value of CN domain ID is PS_DOMAIN.

Step 7 Run the PING IP command.

If... Then...

The IP address can be pinged, End this task.

Others Go to Step 8.

NOTE

If a firewall exists at the peer end, a failure message is displayed.

Step 8 Optional: If the setup of the service corresponding to one IPoA PVC fails, perform VCL

continuity check on all the IPoA PVCs over the Iu-PS interface.

NOTE



Table 7-4 Performing continuity check on the IPoA PVC

Step Action

c-1 Run the ACT VCLCC command to activate the continuity check on the IPoA PVC.

RNC




7-9



Step Action

c-2 Run the DSP VCLCC command. Set Link type to IPoA PVC. Expected result:

all the following items are Normal.

l LOC alarml AIS alarm

l RDI alarm



l LB failure alarm

NOTEIf the result of any previous items is Alarm, go to 11.1 Verifying Physical Links on the


c-3(option

al)

To keep the VCL continuity check, end this task. Otherwise, run the DEAVCLCC command.

----End

7.3.2 Verifying the Iu-PS Interface (over IP)

This describes how to verify that the control plane and user plane on the IP-based Iu-PS interface

are operational.

Prerequisite




Procedure




Expected result: The value of available bandwidth are not all 0.


Expected result: The value of CN domain ID is PS_DOMAIN.

Step 4 For each SPU subsystem where the SCTP on the Iu-PS interface is terminated, run the DSP

SCTPLNK command.





RNC

Commissioning Guide



Issue 03 (2010-03-25)





If the Operation state is Unavailable,check whether the Iu-PS interface data configuration is


(over IP).

NOTE


on the Gateway of the FE/GE Port . If the Iu-PS interface data configuration is correct, end this task; if

the Iu-PS interface data configuration is incorrect, go to 11.2 Verifying Physical Links on the Terrestrial


Step 7 Run the DSP IPRT command and set the Destination address to the IP address of the connected

SGSN.


----End

7.4 Verifying the Iur Interface

This describes how to verify that the Iur interface is operational. The verification is performed

at the RNC.

7.4.1 Verifying the Iur Interface (over ATM)

This describes how to verify that the control plane and user plane on the ATM-based Iur interface

are operational.

7.4.2 Verifying the Iur Interface (over IP)This describes how to verify that the control plane and user plane on the IP-based Iur interface

are operational.

7.4.1 Verifying the Iur Interface (over ATM)

This describes how to verify that the control plane and user plane on the ATM-based Iur interface

are operational.

Prerequisite




Procedure

Step 1 On the MML client, run the DSP SAALLNK command.





RNC




7-11






Step 5 Run the DSP ADJNODE command.Expected result: QAAL2 state is Available.

Step 6 On the MML client, run the DSP AAL2PATH command.


If Operation state is Unavailable,check whether the Iur interface data configuration is correct.



RNC (over ATM).

Step 7 If the RNC is configured with the IP path to another RNC, run the PING IP command and setthe parameters as follows:

l Set Subrack No. to the number of the subrack carrying the Iur interface.

l Set Slot No. to the number of the slot where the board of the user plane to be queried is held.

l Set Source IP address to the IP address of the board carrying the Iur interface.

l Set Destination address to the IP address of peer RNC.

If... Then...

The IP address can be pinged, End this task.

Others Go to Step 8.

NOTE


Step 8 Optional: If service setup over one AAL2 path fails, perform VCL continuity check on all the

AAL2 paths over the Iur interface.

NOTE




Step Action


path.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



Step Action

b-2 Run the DSP VCLCC command. Set Link type as AAL2 paths. Expected result:

all the following items are Normal.

l LOC alarml AIS alarm

l RDI alarm



l LB failure alarm

NOTEIf the result of any previous items is alarm, go to 11.1 Verifying Physical Links on the


b-3(option

al)

To keep the VCL continuity check, end this task. Otherwise, run the DEAVCLCC command.

----End

7.4.2 Verifying the Iur Interface (over IP)

This describes how to verify that the control plane and user plane on the IP-based Iur interface

are operational.

Prerequisite




Procedure




Expected result: QAAL2 state is Available.

Step 3 Run the DSP SCTPLNK command.






RNC




7-13



If the Operation state is Unavailable,check whether the Iur interface data configuration is


(over IP).

NOTE


on the Gateway of the FE/GE Port. If the Iur interface data configuration is correct, end this task; if the

Iur interface data configuration is incorrect, go to 11.2 Verifying Physical Links on the Terrestrial


Step 6 Run the DSP IPRT command and set the Objective IP address to the IP address of the

connected IPC.


----End

7.5 Verifying the Iu-BC InterfaceThis describes how to verify that the Iu-PS interface is operational. The verification is performed

at the RNC. Irrespective of whether the ATM transmission or IP transmission is used, the

verification is the same.

Prerequisite




Procedure

Step 1 On the MML client, run the PING IP command and set the parameters as follows:

l Set Subrack No. to the number of the subrack carrying the Iu-BC interface.

l Set Slot No. to the number of the slot carrying the Iu-BC interface.

l Set Source IP address to the IP address of the board carrying the Iu-BC interface.

l Set Destination address to the IP address of the connected CBC.

If pinging the IP address succeeds, end this task. Otherwise, check that the IP addresses for the

RNC and CBC are correct.

NOTE


----End


RNC

Commissioning Guide



Issue 03 (2010-03-25)



Expected result: The activation success rate is higher than 95%. Page browsing is operational.

Step 5 Verify the mobility management. Perform 20 soft handovers on the CS and PS voice services

respectively.

Expected result: The handover success rate is higher than 95%.

Step 6 Verify the OM management. Switch over the SPUa, DPUb, and OMUa boards one time

respectively during service operation.

Expected result: The switchover succeeds, and the service is not interrupted during switchover.

Step 7 Verify inter-system handover. Hand over a dual-mode UE from UMTS to GSM 20 times. Hand

over a dual-mode UE from GSM to UMTS 50 times.

Expected result: The connection success rate is higher than 90%. The CS service is clear and

does not have any loud noise. The PS service is free from call drop.

Step 8 Verify the HSDPA. Activate the high-speed PS service, access the FTP server, and download

large files. The assigned downlink rate of services is recommended to be over 384 kbit/s.To

ensure stability of rate. Perform the verification 10 times.Expected result: The activation success rate is above 90%. Downloading is operational.

Step 9 Verify the HSUPA. Activate the high-speed PS service, access the FTP server, and upload large

files. The assigned downlink rate of services is recommended to be over 384 kbit/s. To ensure

stability of rate. Perform the verification 10 times.

Expected result: The activation success rate is above 90%. Uploading is operational.

Step 10 Verify the 64QAM service. Activate the high-speed PS service, access the FTP server, and

download large files. The assigned downlink rate of services is recommended to be over 384

kbit/s. To ensure stability of rate. Perform the verification 10 times.

Expected result: The activation success rate is above 90%. Downloading is operational.

Step 11 Verify the MIMO service. Activate the high-speed PS service, access the FTP server, and

download large files. The assigned downlink rate of services is recommended to be over 384

kbit/s.To ensure stability of rate. Perform the verification 10 times.

Expected result: The activation success rate is above 90%. Downloading is operational.

----End

8 Verifying RNC Services

RNC

Commissioning Guide



Issue 03 (2010-03-25)




This describes how to integrate the RNC into the M2000 for centralized management.

Prerequisite

l The RNC local office has passed commissioning.

l The OM network has passed commissioning. The M2000 is operational.

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

Context

l If the RNC and the M2000 are in the same network segment, you do not need to configure

the IP route to the M2000 before connection.

l If the RNC and the M2000 are not in the same network segment, you need to configure the

IP route to the M2000 before connection.

Procedure

Step 1 Connect the RNC to the OM network.

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

RNC.

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

hub or a route.

Step 2 Configure the IP route from the RNC to the M2000.

1. Check whether the route to the M2000 is configured on the BAM.

On the MML client, run the LST BAMIPRT command. Set Destination network

address to the subnet network segment address of the M2000.

l If the data of the route to the M2000 is displayed, end this task.

l If the data of the route to the M2000 is not displayed, go to Step 2.2.

2. Configure the IP route from the RNC to the M2000.

Run the ADD BAMIPRT command to set the parameters as follows:

l

Set Destination network address to the IP address of the network segment where theM2000 server is located.

RNC

Commissioning Guide 9 Integrating the RNC into the M2000



9-1



l Set Destination address mask to the mask of the IP address of the M2000 server.

l Set Forward route address to the IP address of the router.

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

Run the ping command at the RNC to check whether the network between the RNC and

the router is operational. If the BAM can receive a response packet from the router, go to

Step 2.4. Otherwise, check that the BAM and the router are properly connected.

4. Verify the configuration of the route from the RNC to the M2000.

Run the ping command at the RNC to check whether the network between the RNC and

the M2000 is operational. If the M2000 can receive a response packet from the router, go

to Step 3. Otherwise, check that the M2000 and the router are properly connected.

Step 3 Create the RNC on the M2000. For details, refer to the M2000 documents.

CAUTION

l If a firewall exists between RNC and M2000, ensure the communication ports connecting

the RNC and M2000.

l For details on the ports connecting the RNC and M2000, see 12 Communication Ports Used

by the BSC6810.

----End

Example

Table 9-1 describes how to configure the route between the RNC and the M2000.

Table 9-1 Configuring the route from the RNC to the M2000

Scenar

io

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

The BAM is connected to M2000 network segment through the route. The IP

address of the route is 172.121.139.10.

Action 1. Run the ADD BAMIPRT command

l Set Destination network address to 10.11.100.0.

l Set Destination address mask to 255.255.255.0.

l Set Forward route address to 172.121.139.10.

2. Run the ping 172.121.139.10 command.

3. Run the ping 10.11.100.23 command.


RNC

Commissioning Guide



Issue 03 (2010-03-25)



10 Creating RNC Scheduled Tasks

This describes how to create the scheduled task of automatically backing up RNC system data

and logs after RNC commissioning, so that the data and logs can be used for recovery of the

RNC equipment failure.

Prerequisite

The RNC has passed commissioning.

Context

You are required to set the period for the scheduled task. The period for the scheduled task is of

the following types: fixed time, day-based scheduling, day-based duration, week-based

scheduling, week-based duration, month-based scheduling, and month-based duration.

Procedure

Step 1 Perform Automatically Backing Up RNC System Data.

This describes how to automatically back up the RNC system data on the LMT. The system data

consists of the RNC configuration data, performance data, and alarm data.

Step 2 Perform Automatically Backing Up RNC Logs.

This describes how to set automatic backup of RNC logs on the LMT. RNC logs can be used

for fault location and analysis. They are the following items: host logs, BAM logs, database logs,

system event logs, operation logs, and alarm logs.

----End

RNC

Commissioning Guide 10 Creating RNC Scheduled Tasks



10-1



11 FAQ

About This Chapter

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

11.1 Verifying Physical Links on the Terrestrial Interface at the RNC (over ATM)

This describes how to verify that physical links on the ATM-based terrestrial interface are

operational.

11.2 Verifying Physical Links on the Terrestrial Interface at the RNC (over IP)

This describes how to verify that physical links on the IP-based terrestrial interface are

operational.

11.3 Conducting BFD/ARP Connectivity Check on the Gateway of the FE/GE Port

This describes how to conduct BFD/ARP connectivity check on the gateway of the FE/GE port.

11.4 Troubleshooting: Unavailable E1/T1 Physical Links

This describes how to handle the unavailability of E1/T1 links on standard interfaces.

11.5 Troubleshooting: Unavailable FE/GE Physical Links

This task describes how to handle unavailability of physical links on the FE and GE ports.

11.6 Troubleshooting: Inconsistent Interface Data

This describes how to handle the inconsistency of interface data. When RNC standard interfaces

are commissioned, the interface data may be inconsistent.

11.7 Troubleshooting: Cell Setup Failures

This describes how to handle cell setup failures.

11.8 Troubleshooting: Signaling Link Failures on the Iub Interface

This describes how to handle signaling link failures on the Iub interface.

11.9 Troubleshooting: AAL2/IP Connection Setup Failures

This describes how to handle the failures in AAL2/IP connection setup.

11.10 Troubleshooting: RNC Boards Loading Failures

This describes how to handle the failures when RNC boards are loaded.

RNC

Commissioning Guide 11 FAQ



11-1



11.1 Verifying Physical Links on the Terrestrial Interface atthe RNC (over ATM)

This describes how to verify that physical links on the ATM-based terrestrial interface are

operational.

Prerequisite


l The RSS and all the RBSs are operational.


Contextl When the E1/T1 ports on the AEUa and AOUa boards serve as the bearer ports of the RNC,

check that the E1/T1 physical links are operational.

l When the optical ports on the AOUa/UOIa (UOIa_ATM) boards serve the interconnection

between the RNC and the peer end, check that the optical ports are operational.

l It is recommended that the UOIa (UOIa_ATM) serves as the interface board when the Iu-

PS interface uses ATM transmission mode. Check that the optical ports are operational.

NOTE

The UOIa_ATM is the UOIa board used in ATM transport. The UOIa_IP is the UOIa board used in IP

transport.

Procedure

l Verifying E1/T1 links

1. On the RNC LMT, run the DSP E1T1 command and set the parameters as follows:

– Set Subrack No. to the number of the subrack where the interface board carrying

the E1/T1 links to be queried is located.

– Set Slot No. to the number of the slot where the interface board carrying the E1/

T1 links to be queried is housed.

– Set Board type to the type of the interface board carrying E1/T1 links to be queried.

– Set Link No. to the number of the E1/T1 links to be queried.

Expected result: The Link running state of the associated T1/E1 links is Available.

2. If Link running state displays one of the following alarms, refer to 11.4

Troubleshooting: Unavailable E1/T1 Physical Links for troubleshooting:

– Loss of Signal

– Alarm Indication Signal

– Loss of Frame

– Remote Alarm

– Loss of Multiple Frame

– Fault

l Verifying optical ports

11 FAQ

RNC

Commissioning Guide



Issue 03 (2010-03-25)



1. On the RNC LMT, run the DSP OPTI command and set the parameters as follows:

– Set Subrack No. to the number of the subrack where the optical ports to be verified

are located.

– Set Slot No. to the number of the slot where the optical ports to be verified are

held.

– Set Board type to the type of the board where the optical ports are located.

– Set Port No. to the number of the port of the board where the optical ports to be

verified are located.

Expected result: For the associated optical ports, Optical port state is Normal.

----End

11.2 Verifying Physical Links on the Terrestrial Interface at

the RNC (over IP)This describes how to verify that physical links on the IP-based terrestrial interface are

operational.

Prerequisite


l The RSS and all the RBSs are operational.


Contextl When the E1/T1 port on the PEUa/POUa serves as the bearer port of the RNC, verify that

the physical links on the E1/T1 port, PPP links, and MLPPP group are operational.

l When the FE/GE port on the FG2a and GOUa boards serve as the bearer port of the RNC,

verify that the physical links on the FE/GE port are operational.

Procedure

l Verifying E1/T1 links

1. On the RNC LMT, run the DSP E1T1 command and set the parameters as follows:


the E1/T1 links to be queried is located.

– Set Slot No. to the number of the slot where the interface board carrying the E1/

T1 links to be queried is housed.

– Set Board type to the type of the interface board carrying E1/T1 links to be queried.

– Set Link No. to the number of the E1/T1 links to be queried.

Expected result: For the associated E1 links, Link running state is Available.

If Link running state displays one of the following alarms, refer to 11.4

Troubleshooting: Unavailable E1/T1 Physical Links for troubleshooting:

– Loss of Signal

– Alarm Indication Signal

RNC




11-3



– Loss of Frame

– Remote Alarm

– Loss of Multiple Frame

–Fault

2. Run the DSP PPPLNK command and set the parameters as follows:

– Set Subrack No. to the number of the subrack where the PPP link to be queried

is housed.

– Set Slot No. to the number of the slot where the interface board carrying the PPP

link to be queried is housed.

– Set PPP link No. to the number of the PPP link to be queried.

Expected result: For the associated PPP link, Link state is UP.

3. Run the DSP MPGRP command and set the parameters as follows:

– Set Subrack No. to the number of the subrack where the MLPPP link to be queriedis carried.

– SetSlot No. to the number of the slot where the interface board carrying the MLPPP

link to be queried is housed.

– Set MLPPP Group No. to the number of the MLPPP link group to be queried.

Expected result: For the associated E1 link, Link state is Normal.

l Verifying physical links on the FE/GE Port

1. On the RNC LMT, run the DSP ETHPORT command and set the parameters as

follows:


the FE/GE links to be queried is located.

– Set Slot No. to the number of the slot where the interface board carrying the FE/

GE links to be queried is held.

– Set Port No. to the number of the FE/GE port to be queried.

Expected result: For the physical links on the FE/GE port, Link Availability Status

is Available.

If the verification fails and one of the following is displayed, refer to 11.5

Troubleshooting: Unavailable FE/GE Physical Links.

– Link Availability Status is Unavailable.

– Port state is Deactivated .

2. If layer 3 networking mode is used, perform continuity check on the gateway. For

details, refer to 11.3 Conducting BFD/ARP Connectivity Check on the Gateway

of the FE/GE Port.

----End

11.3 Conducting BFD/ARP Connectivity Check on theGateway of the FE/GE Port

This describes how to conduct BFD/ARP connectivity check on the gateway of the FE/GE port.

11 FAQ

RNC

Commissioning Guide



Issue 03 (2010-03-25)



Prerequisite


l Before conducting the gateway connectivity check, check whether the peer router supports

BFD function.

Context

l Only FG2 and GOU boards support gateway connectivity check.

l If the peer router supports BFD function, and also is enabled with it, enable the BFD check

function; if the peer router does not support BFD function, start ARP check.

Procedure

Step 1 Run the LST IPCHK command to query the configuration of the gateway connectivity check.

Set the parameters as follows:l Set Subrack No. to the number of the port to be checked.

l Set Slot No. to the number of the port to be checked.

Step 2 Run the STR IPCHK command and set the parameters as follows:

l Set Subrack No. to the number of the port to be checked.

l Set Slot No. to the number of the port to be checked.

l Set Port No. to the number of the port to be checked.

l If the peer router supports and is enabled with the BFD function, set Check type toSBFD.

Otherwise, set it to ARP.

l Set Check mode to the work mode of the port to be checked.

l Set Gateway IP address to the IP address of the gateway to be checked.

Step 3 On the RNC LMT, check whether the 2624 L3 detect fail alarm is generated. If yes, clear the

alarm as suggested.

Step 4 Optional: To keep the gateway connectivity check, end this task; Otherwise, run the STP

IPCHK command and set the parameters as follows:

l Set Subrack No. to the number of the port whose gateway connectivity check is to be stopped.

l Set Slot No. to the number of the port whose gateway connectivity check is to be stopped.

l Set Check index to the index of the port whose gateway connectivity check is to be stopped.

----End

11.4 Troubleshooting: Unavailable E1/T1 Physical Links

This describes how to handle the unavailability of E1/T1 links on standard interfaces.

Symptoms

When the DSP E1T1 command is run on the MML client to check the E1/T1 link status, and

Link running state is Link is down.

RNC




11-5



NOTE

When you run the DSP E1T1 command to check the E1/T1 link status, the value of the E1T1 is

used parameter may be set to NO. In such a case, if the link running state isLoss of Signal orAlarm

Indication Signal, the link is still operational.

Solutions

1. If Link running state of the E1/T1 link is Fault, and we can see one of the

following alarms from the alarm console:

l Loss of Signal

l Alarm Indication Signal

l Loss of Frame

l Remote Alarm

l Loss of Multiple Frame

Then troubleshoot according to the suggestions in the Alarm Handling part in the RNCOnline Help. The alarms are listed in Table 11-1.

Table 11-1 Physical link failure alarms

E1/T1 Link Status Alarm

Loss of Signal ALM_1101 (E1/T1 Signal Loss)

Alarm Indication

Signal

ALM_959 (Lower Order Path Remote Defect Indication)

Loss of Frame l ALM_1102 (E1/T1 Loss of Frame Alignment)

l ALM_1015 (Fractional IMA Link Loss of Frame)

Remote Alarm ALM_1103 (E1/T1 Remote Alarm Indication)

Loss of Multiple

Frame

ALM_1105 (E1/T1 Loss of Multiframe Alignment)

2. If Link running state of the E1/T1 link is Fault and electrical ports on the AEUa/

PEUa serve as bearers, perform the loopback test on all the faulty E1/T1 links carried on

the electrical ports.

NOTE

The background information for the loopback test is listed as follows:

l The loopback test and the Bit Error Rate (BER) test cannot be conducted simultaneously.

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

l The loopback test can be performed on the E1/T1 link at the electrical ports when the E1/T1

physical links on the standard interfaces are unavailable.

l Conduct the loopback test on the local E1/T1 port.

11 FAQ

RNC

Commissioning Guide



Issue 03 (2010-03-25)



Table 11-2 Procedure for conducting the loopback test on the local E1/T1 port

Step Action

*1 Run the SET E1T1LOP command and set the Loop type to

LOCAL_LOOP (local loopback).

*2 Run the LOP E1T1 command.

*3 Run the DSP E1T1LOP command to check the loopback test result.

*4 Run the SET E1T1LOP command and set the Loop type to NO_LOOP

(No loopback).

If... Then...

If the loopback test result is

Succeeded,

It indicates that the E1/T1 port is

operational. Continue with the loopback test

on the local trunk cable.

If the loopback test result is Not

succeeded,

It indicates that the E1/T1 port is faulty.

Replace the interface board carrying the

faulty E1/T1 port.

l Conduct the loopback test on the local trunk cable.

Table 11-3 Procedure for conducting the loopback test on the local trunk cableStep Action

*1 Connect the TX end to the RX end of the E1/T1 cable at the local end.



*4 Stop the loopback at the local end.

If... Then...


Succeeded,

It indicates that the local trunk cable is operational.

Continue with the loopback test on the peer E1/T1

port.

RNC




11-7



If... Then...


Not succeeded,

l Use a multimeter to measure the continuity

between the connector pin and the inner conductor

of the coaxial cable and that between the outer shell

of the connector and the shielding layer of the

coaxial cable. If a continuity failure occurs, make

a new connector and assemble the cable again.

l Use a multimeter to check whether the internal and

external conductors are short-circuited. If so, make

a new connector and assemble the cable again.

If the fault persists, replace the trunk cable with a new

one.

l Conduct the loopback test on the peer E1/T1 port.

Table 11-4 Procedure for checking the peer equipment or the transport network

Step Action

*1 Run the SET E1T1LOP command and set the Loop type to

REMOTE_LOOP (Remote loop).



*4 Run the SET E1T1LOP command and set the Loop type to NO_LOOP

(No loop).

If... Then...


Succeeded,

If the E1/T1 belongs to a certain IMA group,

run the RST IMAGRP command. In the

displayed confirmation dialog box, click

Yes.


succeeded,

Contact the maintenance personnel for the

peer equipment to rectify faults in the peer

equipment or the transport network.

l If the E1/T1 belongs to a certain IMA group, run the RST IMAGRP command. In the

displayed confirmation dialog box, click Yes.

If... Then...


Succeeded,

End this task.

11 FAQ

RNC

Commissioning Guide



Issue 03 (2010-03-25)



If... Then...


succeeded,

Contact the local Huawei office for

technical support.

3. If Link running state of the E1/T1 link is Fault and optical ports on the AEUa/

PEUa serve as bearers, perform the loopback test on all the faulty E1/T1 links carried on

the electrical ports.

NOTE

The loopback test can be conducted on E1/T1 links at the optical ports when the E1/T1 physical links

on the standard interfaces are unavailable.

l Conduct the loopback test on the SDH port.

Table 11-5 Procedure for conducting the loopback test on the SDH port

Step Action

*1 Run the SET OPTLOP command and set the Loop type to

LOCAL_LOOP.

*2 Run the DSP OPT command.

*3 Run the SET OPTLOP command and set the Loop type to NO_LOOP.

If... Then...

The Optical port state in the

returned result is Normal.

It indicates that the SDH port is operational.

Continue with the loopback test on local

fibers.


returned result is Fault.

It indicates that the SDH port is faulty.

Replace the interface board carrying the

faulty SDH port.

l Conduct the loopback test on local fibers.

Table 11-6 Procedure for conducting the loopback test on local fibers

Step Action

*1 Connect the TX end to the RX end of the fiber at the local end.


*3 Stop the loopback at the local end.

RNC




11-9



If... Then...


returned result is Normal.

It indicates that the local fiber is operational.

Continue with the loopback test on the peer

optical port.



It indicates that the local cable is faulty.

Replace the faulty cable.

l Conduct the loopback test on the peer optical port.

Table 11-7 Procedure for conducting the loopback test on the peer optical port

Step Action


REMOTE_LOOP.



NO_LOOP.

If... Then...


returned result is Normal, but thefault persists.

Contact local Huawei office for technical

support.



Contact the maintenance personnel for the

peer equipment to rectify faults in the peer

equipment or the transport network.

11.5 Troubleshooting: Unavailable FE/GE Physical Links

This task describes how to handle unavailability of physical links on the FE and GE ports.

Symptoms

When the DSP ETHPORT command is run on the MML client to check the physical link status

on the FE and GE ports, the system displays the following information:

l Link Availability Status is Unavailable.

l Port State is Deactivated.

11 FAQ

RNC

Commissioning Guide



Issue 03 (2010-03-25)



Solutions

1. If the system shows that Link Availability Status is Unavailable, check the connection

of the Ethernet cable and check whether the peer Ethernet port is enabled. Then refer to the

suggestions in the Alarm Handling part in the RNC Online Help for troubleshooting.

2. If the system shows that Port state is Deactivated, activate the FE port.

(1) Run the ACT ETHPORT command to set the parameters as follows:

l Set Subrack No. to the number of the subrack where the interface board of the FE

links is housed.

l Set Slot No. to the logic number of the slot housing the interface board.

l Set Port No. to the number of the FE/GE port.

(2) Run the DSP ETHPORT command to set the parameters as follows:

l Set Subrack No. to the number of the subrack where the interface board of the FE

links is housed.l Set Slot No. to the logic number of the slot housing the interface board.

l Set Port No. to the number of the FE/GE port.

Expected results:

l Link Availability Status is Activated.

l Port State is Activated.

11.6 Troubleshooting: Inconsistent Interface Data

This describes how to handle the inconsistency of interface data. When RNC standard interfaces

are commissioned, the interface data may be inconsistent.

Symptoms

During the verification of the Iub, Iu-CS, Iu-PS, and Iur interfaces, the final results are not as

expected. The comparison between the negotiated data and the configured data proves that the

problem is caused by the inconsistent interface data.

Solutions

Modify the inconsistent interface data. For details, refer to the RNC Initial Configuration

Guide.

11.7 Troubleshooting: Cell Setup Failures

This describes how to handle cell setup failures.

Symptoms

During the verification of cell setup, the final result is not as expected. Operational state of the

cell is Unavailable and the complete cell setup procedure over the Iub interface cannot be traced.

RNC




11-11



Fault-Locating Policies

CAUTION

l In ATM transport mode over Iub, if cell setup failure occurs, check whether the alarms related

to the DPUb, optical ports and links such as DSP, SAAL, IMA, and AAL2 exist in the alarm

management system. If such alarms exist, handle the alarms according to the suggestions in

the Alarm Handling part. If the alarms persist, handle them according to the later mentioned

methods.

l In IP transport mode over Iub, if cell setup failure occurs, check whether the alarms related

to the DPUb, DSP, and SCTP link exist in the alarm management system. If such alarms

exist, handle the alarms according to the suggestions in the Alarm Handling part. If the alarms

persist, handle them according to the later mentioned methods.

l In dual stack of ATM/IP transport mode over Iub, if cell setup failure occurs, check whether

the alarms related to the DPUb, optical ports and links such as the DSP, SAAL, SCTP, IMA,

and AAL2 exist in the alarm management system. If such alarms exist, handle the alarms

according to the suggestions in the Alarm Handling part. If the alarms persist, handle them

according to the later mentioned methods.

The policy of fault location is to get the faulty NodeB or RNC by comparing the results of the

Iub interface message tracing with that in normal situation. Then further locate the faults by

other methods. For details about the interface message tracing, refer to Starting the RNC Message

Tracing (Commissioning).

Figure 11-1 and Figure 11-2 show how to locate cell setup failures.

11 FAQ

RNC

Commissioning Guide



Issue 03 (2010-03-25)



Figure 11-1 Locating cell setup failures (1)

RNC




11-13



Table 11-8 Operation index (1)

Index Action Step

*1-1 Check that the Iub link

works properly.

l In ATM transport, refer to 11.1 Verifying Physical

Links on the Terrestrial Interface at the RNC(over ATM).

l In IP transport, refer to 11.2 Verifying Physical

Links on the Terrestrial Interface at the RNC

(over IP).

l In ATM/IP dual stack transport, refer to 7.1.3

Verifying the Iub Interface (over ATM and IP).

*1-2 Handle signaling link

failures on the Iub

interface.

Refer to 11.8 Troubleshooting: Signaling Link

Failures on the Iub Interface.

*1-3 Check whether theaudit response

message is correct.

Refer to Solution 1: Checking the Audit ResponseMessage.

*1-4 Unblock the cell. Refer to Solution 2: Unblocking Cells.

*1-5 Match the configured

maximum downlink

transmit power with

the reporting ability of

the NodeB.

Refer to Solution 3: Matching the Configured

Maximum Downlink Transmit Power with

Reporting Ability of the NodeB.

*1-6 Check that DSP

resources are

available.

l On the RNC LMT, run the DSP DSP command to

query how many DSPs are available to a DPUb.

Calculate all the DPUbs. The final result is the number

of DSPs available to all DPUbs.

l The number of cells that can be setup is 15 times the

number of DSPs. If the number of DSPs is smaller

than that of the cells that can be set up, it indicates that

the DSP resources are insufficient.

*1-7 Check that there are

available TNL

resources.

Refer to Solution 6: Checking TNL Resources.

11 FAQ

RNC

Commissioning Guide



Issue 03 (2010-03-25)



Figure 11-2 Locating cell setup failures (2)


Index Action Step

*2-1 Check that the RACH

setup response message is

correct.

Refer to Solution 4: Checking the RACH Setup

Response Message.

*2-2 Check that the Iub link

works properly.

l In ATM transport, refer to 11.1 Verifying Physical


(over ATM).

l In IP transport, refer to 11.2 Verifying Physical


(over IP).l In ATM/IP dual stack transport, refer to 7.1.3

Verifying the Iub Interface (over ATM and

IP).

*2-3 Handle signaling link

failures on the Iub

interface.



RNC




11-15



Index Action Step

*2-4 Check that AAL2/IP link

setup succeeds.

l In ATM transport, check that AAL2 link setup

succeeds. Refer to 7.1.1 Verifying the Iub

Interface (over ATM).

l In IP transport, check that IP link setup succeeds.

Refer to 7.1.2 Verifying the Iub Interface (over

IP).

*2-5 Handle AAL2/IP link

setup failures.

Refer to 11.9 Troubleshooting: AAL2/IP

Connection Setup Failures.

*2-6 Check that the PCH/

FACH setup response

message is correct.

Refer to Solution 5: Checking the PCH/FACH

Setup Response Message.

Solution 1: Checking the Audit Response Message

Start the Iub interface tracing to check the audit response message of the NodeB. The

requirements for correct audit response messages of the NodeB are as follows:

l Each cell has the associated LocalCell.

l If LocalCell is configured to belong to LocalCellGroup, then LocalCell has the associated

LocalCellGroup.

Solution 2: Unblocking Cells

l If the RNC initiates the unblocking, run the UBL CELL command to unblock cells.

l If the NodeB initiates the unblocking, contact the maintenance personnel of the NodeB for

troubleshooting.

Solution 3: Matching the Configured Maximum Downlink Transmit Power withReporting Ability of the NodeB

Run the LST CELL command to query the cell maximum downlink transmit power

(MAXTXPOWER) configured in the database. The value should not be greater than that of

Maximum DL Power Capability (MAXTXPOWER) in the audit response message.

If the previously mentioned requirements cannot be met, run the MOD CELL command to

modify the cell maximum downlink transmit power or request the NodeB to modify the reported

maximum downlink transmit power.

Solution 4: Checking the RACH Setup Response Message

RACH Setup Response Message is included in the Common Transport Channel Setup Response

(NBAP_COMM_TRANSP_CH_SETUP_RSP) Message. The requirements for the correct

RACH Setup Response Message are as follows:

l The information such asCommon Transport Channel ID

,TransportLayerAddr

, and

Binding Id exists.

11 FAQ

RNC

Commissioning Guide



Issue 03 (2010-03-25)



l The Common Transport Channel ID of RACH carried in the message should be the same

as that configured in the database.

l The TransportLayerAddr carried in the message should be the same as that configured

in the database.

Table 11-10 Common Transport Channel of the Cell

Coding of the CommonTransport Channel

Channel Type and ID of CommonTransport Channel

1 RACH PRACH

NOTE

When the user plane is carried over the ATM transport, TransportLayerAddr is the ATM address. Run the

LST NODEB command to check that the configured ATM address is consistent with that in the RACH SetupResponse Message.

When the user plane is carried over the IP transport, TransportLayerAddr is the IP address. Run the LST

IPPATH command to check that the configured peer IP address, or the IP address of the NodeB user plane, is

consistent with that in the RACH Setup Response Message.

Solution 5: Checking the PCH/FACH Setup Response Message

FACH Setup Response Message is included in Common Transport Channel Setup Response

（ NBAP_COMM_TRANSP_CH_SETUP_RSP) Message. The requirements for correct FACH

Setup Response Messages are as follows:

l The messages of Common Transport Channel ID, TransportLayerAddr , and

BindingId exist.

l The transport channel ID of FACH or PCH displayed in the messages should be the same

as that configured in the database.

l TransportLayerAddr in the message is consistent with that in the database.

Table 11-11 Common Transport Channel of the Cell

Coding of the CommonTransport Channel

Channel Type and ID of CommonTransport Channel

3 PCH SCCPCH

4 FACH (signaling)

5 FACH (service)

NOTE

When the user plane is carried over the ATM transport, TransportLayerAddr is the ATM address. Run the

LST NODEB command to check that the configured ATM address is consistent with that in the PCH/FACH

Setup Response Message.

When the user plane is carried over the IP transport, TransportLayerAddr is the IP address. Run the LST

IPPATH command to check whether the configured peer IP address, or the IP address of the NodeB user plane,is consistent with that in the PCH/FACH Setup Response Message.

RNC




11-17



Solution 6: Checking TNL Resources

1. Run the LST ADJNODE command to check that the adjacent node is configured. If not,

run the ADD ADJNODE command to configure the adjacent node.

2. Run the LST AAL2PATH command to check the configuration of the AAL2 path of theadjacent node.

3. Run the LST TRMMAP command to check that the AAL2 path mapped by the R99 RT

service (service type of the common channel) exists, and check that the bandwidth meets

the requirements of the common channel. If the AAL2 path does not exist, add the

associated AAL2 path. If the bandwidth does not meet the requirement of the common

channel, add an AAL2 path or modify the configuration of the AAL2 path.

4. Run the LST AAL2RT command to check that the AAL2 route to the adjacent node is

configured. If it is not configured, add the route.

11.8 Troubleshooting: Signaling Link Failures on the IubInterface

This describes how to handle signaling link failures on the Iub interface.

Symptoms

During the verification of physical links on the Iub interface or during the cell setup, the signaling

link on the Iub interface is faulty. The NBAP_AUDIT_REQ message cannot be traced through

the Iub interface tracing. The alarms related to the DPUb or DSP are not reported.

Solutions1. In ATM transport over Iub, check whether the alarms related to optical ports and links such

as E1/T1, IMA, UNI, SAAL, NCP, and CCP are reported. If such alarms exist, handle them

according to the suggestions in the Alarm Handling part. If the alarm persists, handle it

according to Figure 11-3.

11 FAQ

RNC

Commissioning Guide



Issue 03 (2010-03-25)



Figure 11-3 Procedure for handling signaling link failures on the ATM-based Iub interface


Index Action Step

*1-1 Add the upper-layer

application to the

SAAL link.

For the Iub interface, run the ADD NCP, ADD

CCP, and ADD ADJNODE commands to add NCP,

CCP, and ALCAP to the SAAL link respectively.

*1-2 Check and handle

physical channel

failures.

Refer to 11.4 Troubleshooting: Unavailable E1/T1

Physical Links.

RNC




11-19



Index Action Step

*1-3 Check the data

configuration.

Perform the following steps:

1. Run the LST SAALLNK command to check the

consistency of the negotiated data configurationin the SAAL link.

l If they are inconsistent, go to *1-4.

l If they are consistent, go to next step shown in

Figure 11-3.

2. Run the LST E1T1 command to check the

consistency of coding modes at the two ends.



Figure 11-3.

3. Run the LST IMAGRP command to check theconsistency of the IMA protocol version

configuration at the two ends.



Figure 11-3.

*1-4 Modify data

configuration.

1. Modify the SAAL link configuration as follows:

a. Run the RMV NCP, RMV CCP, or RMV

ADJNODE command to delete upper-layer

applications.

b. Run the RMV SAALLNK command to delete

the SAAL link.

c. Run the ADD SAALLNK command to add the

SAAL link as negotiated.

d. Run the ADD NCP, ADD CCP, or ADD

ADJNODE command to add upper-layer

applications.

2. Run the SET E1T1 command to modify the E1/

T1 coding mode according to the negotiated

conclusion.

3. Run the MOD IMAGRP command to modify theconfiguration of the IMA protocol version.

2. In IP transport over Iub, check whether the alarms related to FE ports and links such as E1/

T1, SCTP, NCP, and CCP are reported. If such alarms exist, handle them according to the

suggestions in the Alarm Handling part. If the alarm persists, handle it according to Figure

11-4.

11 FAQ

RNC

Commissioning Guide



Issue 03 (2010-03-25)



Figure 11-4 Procedure for handling signaling link failures on the IP-based Iub interface


Index Action Step

*2-1 Check whether the

SCTP link works

properly.

Run theLST NODEB, DSP SCTPLNK , and DSP

IUBCP commands to check that the SCTP link is

operational.

*2-2 Add the upper-layer

application to the

SCTP link.

Run the ADD NCP and ADD CCP commands to

add the upper-layer application to the SCTP link.

*2-3 Check whether the

physical link works

properly.

Refer to 11.2 Verifying Physical Links on the

Terrestrial Interface at the RNC (over IP).

*2-4 Handle the physical

link failure.

1. If the data is transmitted over Ethernet, for

example, through FE ports, refer to 11.5

Troubleshooting: Unavailable FE/GE

Physical Links.

2. If the data is transmitted over a private line, for

example, over E1/T1, refer to 11.4

Troubleshooting: Unavailable E1/T1 PhysicalLinks.

*2-5 Check the data

configuration.

Run the LST SCTPLNK command to check the

consistency of the negotiated data on the SCTP link.

If they are inconsistent, go to *2-6. If they are

consistent, go to next step shown in Figure 11-4.

*2-6 Modify data

configuration.

Modify the configuration on the SCTP link. Run the

MOD SCTPLNK command to modify the

configuration on the SCTP link.

RNC




11-21



3. If the transmission on the Iub interface is based on the ATM/IP dual stack, handle the

failures according to the suggestions in the ATM transport and IP transport as required.

11.9 Troubleshooting: AAL2/IP Connection Setup FailuresThis describes how to handle the failures in AAL2/IP connection setup.

Symptoms

During cell setup or AAL2 connection, failures in setup of the AAL2 or the IP link occur.

Solutions

1. When the user plane is carried over ATM, check whether the alarms related to the IMA,

optical ports, RSS, AAL2, and MTP3 are reported. If such alarms exist, handle them

according to the suggestions in the Alarm Handling part. If the fault persists, handle it

according to Figure 11-5.

Figure 11-5 Procedure for handling AAL2 connection setup failures

11 FAQ

RNC

Commissioning Guide



Issue 03 (2010-03-25)




Index Action Remarks

*1-1 Check and modify the

local data configuration.

Check the configured data. If the configured data

is inconsistent with the negotiated data, modifythe configured data according to the negotiated

data, as shown in Table 11-15.

*1-2 Handle Iub interface

link failures.



Table 11-15 Checking and modifying the data configuration

Command Item If No

LST

ADJNODE

Whether the adjacent node

is configured

Run the ADD ADJNODE command to

configure adjacent nodes.

LST

AAL2PATH

Whether the AAL2 path to

the adjacent node is

configured

Run the ADD AAL2PATH command to

configure the AAL2 path.

Whether the path ID is

consistent with the

negotiated data

1. Run the RMV AAL2PATH

command to delete this AAL2 path.

2. Run the ADD AAL2PATH command

to add the AAL2 path again.

Whether the bandwidth isconsistent with the

negotiated data

1. Run the RMV AAL2PATHcommand to delete this AAL2 path.

2. Run the ADD AAL2PATH command

to add the AAL2 path again.

LST

AAL2RT

Whether the IP route to the

specified adjacent node is

configured

Run the ADD AAL2RT command to add

the IP route to the specified adjacent

node.

Whether the ATM address

(NSAP) is correct

1. Run the RMV AAL2RT command to

delete the IP route.

2. Run the ADD AAL2RT command to

add the IP route again.

2. When the user plane is carried over IP transport, handle the failure according to Table

11-16.

RNC




11-23




Index Action Remarks

*2-1 Determine the IP

path that carriesthe common

channel.

Run the LST IPPATH and LST TRMMAP commands

to get the ID of the IP path that carries the commonchannel.

*2-2 Check whether

the IP path is

operational.

1. Refer to 7.1.2 Verifying the Iub Interface (over IP).

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

*2-3 Check whether

the physical link

works properly.

1. Refer to 11.2 Verifying Physical Links on the

Terrestrial Interface at the RNC (over IP).

2. If all the physical links are unavailable, go to *2-4.

3. If all the physical links are available, go to *2-5.

*2-4 Handle the

physical link

failure.

1. If the data is transmitted over Ethernet, for example,

through FE ports, refer to 11.5 Troubleshooting:

Unavailable FE/GE Physical Links.

2. If the data is transmitted over a private line, for example,

over E1/T1, refer to 11.4 Troubleshooting:

Unavailable E1/T1 Physical Links.

*2-5 Check the

configuration of

the IP path.

Run the LST IPPATH command to check whether the

negotiated data is consistent. If they are inconsistent,

modify the negotiated data.

11.10 Troubleshooting: RNC Boards Loading Failures

This describes how to handle the failures when RNC boards are loaded.

Symptoms

When the subrack is loaded to the RNC, the device panel shows that the board status is invalid.

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

If... Then...

Loading other boards of the same type

succeeds,

Replace the faulty board and then reload

the new board.

Loading other boards of the same type

fails,

Go to 2.

2. Check whether the DIP switches of the subrack are properly set.

11 FAQ

RNC

Commissioning Guide



Issue 03 (2010-03-25)



If... Then...

The DIP switches are incorrectly set, Set the correct DIP switches and then

reload the board.

The DIP switches are correctly set, Go to 3.

3. Check whether the internal address mask of the OMUa is 255.0.0.0 and whether the two

internal IP addresses are 80.168.*.*.

If... Then...

No Set the correct internal IP address mask and

internal IP address and then reload the

board.

Yes Go to 4.

4. If loading the DPUb in the RBS fails, check whether the SCUa in the RBS and that in the

RSS are properly connected.

If... Then...

The connection is improper, Correct the connection, and then reload the

boards.

The connection is proper, Go to 5.

5. On the RNC LMT, run the LST SUBRACK command to check whether the type of the

faulty board is properly set.

If... Then...

The type of the board is incorrectly set, Set the correct board type and then reload

the board.

The type of the board is correctly set, Go to 6.

6. If loading the SPUa fails, run the LST RNCBASIC command to check whether RNC basic

information is properly set.

If... Then...

The setting is incorrect, Set the RNC basic information correctly,

and then reload the SPUa.

The setting is correct, Go to 7.

7. Check whether the alarms related to faulty boards are reported in the Alarm Browser

window.

RNC




11-25



If... Then...

Alarms of faulty boards exist, Analyze the alarm information and

accordingly clear the alarm.

Alarms of faulty boards do not exist, Go to 8.

8. Contact the local Huawei office for technical support.

11 FAQ

RNC

Commissioning Guide



Issue 03 (2010-03-25)



12 Communication Ports Used by the

BSC6810

Lists the number of the communication ports used by the services of the BSC6810.

Table 12-1 lists the number of the communication ports used by the services of the BSC6810.

Table 12-1 Communication ports used by the services of the BSC6810

Protocol

Side A Side APort

(Listening)

Side B Side BPort

(Launch)

Service Authentication

TCP RNCBAM

21 RNCHost,

LMT,

M2000

Server

1024-65535

For loading to thehost/uploading

and downloading

of software and

logs

user name, password

TCP RNC

BAM

20 RNC

Host,

LMT,

M2000

Server

1024-65

535

For loading to the

host/uploading

and downloading

of software and

logs (in active

mode)

user name,

password

TCP RNC

BAM

1024-65

535

RNC

Host,

LMT,

M2000

Server

1024-65

535

For loading to the

host/uploading

and downloading

of software and

logs (in passive

mode)

user name,

password

UDP RNC

BAM

67 RNC

Host

1024-65

535

Bootp Listen None

RNC

Commissioning Guide 12 Communication Ports Used by the BSC6810



12-1



Protocol

Side A Side APort

(Listening)

Side B Side BPort

(Launch)


UDP RNC

BAM

123 NODE

B/RNC

BAM

1024-65

535

For standard

clock

synchronization

with SNTP

Server and local

interception

None

UDP M2000

Server

123 RNC

BAM

123 For clock

synchronization

with the server

and local

interception

None

UDP RNC

BAM

1234 RNC

Host

1024-65

535

For clock

synchronization

of the FAM and

local interception

None

TCP RNC

BAM

1500 RNC

Host

1024-65

535

For

communication

with the host

IP Address

TCP RNC

BAM

6000 LMT,

M2000

Server

1024-65

535

For transmitting

MML commands

user name,

password

SSL RNC

BAM

8000 LMT,

M2000

Server

1024-65

535

user name,

password

TCP RNC

BAM

6001 LMT,

M2000

Server

1024-65

535

For alarm

console

user name,

password

SSL RNC

BAM

8001 LMT,

M2000

Server

1024-65

535

user name,

password

TCP RNC

BAM

6006 LMT,

M2000

Server

1024-65

535

For maintenance user name,

password

SSL RNC

BAM

8006 LMT,

M2000

Server

1024-65

535

user name,

password

TCP RNC

BAM

6022 equipm

ent

debug

console

1024-65

535

For equipment

console

None


RNC

Commissioning Guide



Issue 03 (2010-03-25)



Protocol

Side A Side APort

(Listening)

Side B Side BPort

(Launch)


SSL RNC

BAM

8022 equipm

ent

debug

console

1024-65

535

None

TCP RNC

BAM

6088 Upgrad

e tool

1024-65

535

For remote

update tools

None

TCP RNC

BAM

6093 Test

validati

on

1024-65

535

For service

simulation

None

SSL RNCBAM

8093 Testvalidati

on

1024-65535

None

TCP RNC

BAM

6099 M2000

Server

1024-65

535

For data

synchronization

with the M2000

None

SSL RNC

BAM

8099 M2000

Server

1024-65

535

None

TCP RNC

BAM

6100 LMT 1024-65

535

For alarm box None

SSL RNCBAM

8100 LMT 1024-65535

None

UDP RNC

BAM

11774 Peer

RNC

BAM

1024-65

535

For dual-BAM-

server

None

UDP RNC

BAM

11775 Peer

RNC

BAM

1024-65

535

For dual-BAM-

server

None

UDP RNC

BAM

11776 Peer

RNC

BAM

1024-65

535

For dual-BAM-

server backup

None

TCP RNC

BAM

16002 M2000

Server

1024-65

535

For

MML,notificatio

n messages

reports from stat

and M2000

None

SSL RNC

BAM

18002 M2000

Server

1024-65

535

None

RNC

Commissioning Guide 12 Communication Ports Used by the BSC6810



12-3



Protocol

Side A Side APort

(Listening)

Side B Side BPort

(Launch)


TCP CHR 16005 RNC

BAM

1024-65

535

For connection

with the

host_gate on the

BAM. The 16005

port is located on

the CHR server

and added by the

MML server.

None

TCP RNC

BAM

3389 Remote

Desktop

1024-65

535

For users

accessing the

remote PC ininteractive mode

None

TCP Databas

e

3306 Peer

RNC

BAM

1024-65

535

For database user name,

password


RNC

Commissioning Guide

RNC Commissioning Guide-(V200R011_03)

Documents

Transcript of RNC Commissioning Guide-(V200R011_03)