RAN17.1 Reconfiguration Guide for BSC6900(03)(PDF)-En

8/18/2019 RAN17.1 Reconfiguration Guide for BSC6900(03)(PDF)-En

1/381


2/381

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written

consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

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

Notice

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

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

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

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

of any kind, either express or implied.

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

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 03 (2015-06-30) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com/


3/381

About This Document

Overview

This document describes how to reconfigure a RAN after it starts operating, including how to

expand the network capacity and adjust equipment configurations. For details about the

configurations before the system is put into operation, see BSC6900 UMTS Initial ConfigurationGuide. For details about how to enable and adjust a feature, see RAN Feature Parameter

Description.

Product Versions

The following table lists the product versions and solution version related to this document.

Product Name Product Version Solution Version

BSC6900 V900R017C10 RAN17.1

BTS3900 V100R010C10. The

mapping single-mode base

station version is:

NodeB: V200R017C10

BTS3900A

BTS3900L

BTS3900C

BTS3900AL

DBS3900

CME V200R015C10

Intended Audience

This document is intended for:

l Technical support engineers

l Maintenance engineers

l Field engineers

RAN17.1

Reconfiguration Guide for BSC6900 About This Document



ii


4/381

l Network optimization engineers

Organization1 Change Description

This section provides information about the changes in different document versions. There are

two types of changes, including function changes and editorial changes. Function changes refer

to changes in functions of a specific product version. Editorial changes refer to changes in

wording or addition of information that was not described in the earlier version.

2 Introduction to Reconfiguration

This chapter defines reconfiguration and introduces reconfiguration tools.

3 Checking a License

This section describes how to check a newly granted license of the base station controller.

4 Backing Up and Restoring Data

During network optimization, some parameters are reconfigured, but the network performance

is not as good as expected. When this occurs, you can restore to the original network conditions

by backing up and restoring data.

5 Backing Up and Restoring Data by CME

This section describes how to back up and restore data. Users can use the function to restore thenetwork to the state before parameters were reconfigured during network performance

optimization, if the network performance does not meet users' expectations.

6 Reconfiguring the BSC6900

This chapter describes how to reconfigure a running BSC6900 or expand its capacity.

7 Reconfiguring the NodeB

This chapter describes how to reconfigure a running NodeB or expand its capacity.

8 Reconfiguring the UMTS Network

This chapter describes how to reconfigure a UMTS network on a running RNC.

9 Reconfiguring the Interfaces

This chapter describes how to reconfigure interfaces in the case of capacity expansion,

reconfiguration, and network cutover.

Conventions

Symbol Conventions

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

RAN17.1




iii


5/381

Symbol Description

Indicates an imminently hazardous situation which, if not

avoided, will result in death or serious injury.

Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.


avoided, may result in minor or moderate injury.


avoided, could result in equipment damage, data loss,

performance deterioration, or unanticipated results.

NOTICE is used to address practices not related to personalinjury.

Calls attention to important information, best practices and

tips.

NOTE is used to address information not related to personal

injury, equipment damage, and environment deterioration.

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.

RAN17.1




iv


6/381


[ ] 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.

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.

RAN17.1




v


7/381

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.

RAN17.1




vi


8/381

Contents

About This Document.....................................................................................................................ii

1 Change Description.......................................................................................................................1

2 Introduction to Reconfiguration.................................................................................................4

2.1 Definition........................................................................................................................................................................5

2.2 Tools...............................................................................................................................................................................5

3 Checking a License......................................................................................................................10

4 Backing Up and Restoring Data...............................................................................................12

4.1 Backing U p and Restoring Data (Dopra Linux)...........................................................................................................14

4.1.1 Starting the omu_backup_linker tool........................................................................................................................14

4.1.2 Backing Up the System Data.....................................................................................................................................14

4.1.3 Restoring the System Data........................................................................................................................................16

4.2 Backing U p and Restoring Data (Windows)................................................................................................................18

4.2.1 Starting the omu_backup_linker tool........................................................................................................................18

4.2.2 Backing Up the System Data.....................................................................................................................................19

4.2.3 Restoring the System Data........................................................................................................................................23

5 Backing Up and Restoring Data by CME...............................................................................28

6 Reconfig uring the BSC6900.......................................................................................................29

6.1 Changing Signaling Points...........................................................................................................................................30

6.2 Changing the Board Backup Mode from Independent to Active/Standby...................................................................32

6.3 Adjusting OMU Slots...................................................................................................................................................35

6.4 Changing Optical Fibers from Direct Connection to Y-Shaped Connection...............................................................37

6.5 Install a Built-in NE......................................................................................................................................................41

6.6 Uninstall a Built-in NE.................................................................................................................................................46

6.7 Adding a Board or a Subrack.......................................................................................................................................52

6.7.1 Adding a Subrack......................................................................................................................................................52

6.7.2 Adding an SPUa, SPUb, or SPUc Board...................................................................................................................55

6.7.3 Adding a DPUb/DPUe/DEUa Board.........................................................................................................................58

6.7.4 Adding an ASUa Board.............................................................................................................................................61

6.7.5 Adding an Interface Board........................................................................................................................................65

6.7.6 Adding an NIU Board................................................................................................................................................67

RAN17.1

Reconfiguration Guide for BSC6900 Contents



vii


9/381

6.8 Removing a Board or a Subrack...................................................................................................................................70

6.8.1 Removing a Subrack..................................................................................................................................................70

6.8.2 Removing an SPUa/SPUb/SPUc Board (UCP/RUCP).............................................................................................72

6.8.3 Removing a DPUb/DPUe/DEUa Board....................................................................................................................79

6.8.4 Removing an ASUa Board........................................................................................................................................81

6.8.5 Removing an Interface Board....................................................................................................................................84

6.8.6 Removing an NIU Board...........................................................................................................................................86

7 Reconfig uring the NodeB..........................................................................................................89

7.1 Changing the Maintenance Mode of the NodeB..........................................................................................................90

7.2 Device Data Reconfiguration.......................................................................................................................................93

7.2.1 Reconfiguring the NE Information of a NodeB........................................................................................................93

7.2.2 Reconfiguring the NodeB Clock Source or the Clock Working Mode.....................................................................95

7.2.3 Reconfiguring the IP Address of a NodeB Clock Server..........................................................................................99

7.2.4 Adding a WBBP or UBBP to a 3900 Series Base Station.......................................................................................103

7.2.5 Adding an RF Module.............................................................................................................................................108

7.2.6 Changing CPRI Ports for RF Modules....................................................................................................................116

7.2.7 Replacing a Baseband Processing Board.................................................................................................................122

7.2.8 Replacing a Main Control Board.............................................................................................................................127

7.2.9 Changing the Local Maintenance IP address of a NodeB.......................................................................................134

7.3 Radio Data Reconfiguration.......................................................................................................................................137

7.3.1 Reconfiguring the Number of Carriers for a NodeB...............................................................................................137

7.3.2 Adding a Set of Baseband Equipment.....................................................................................................................140

7.3.3 Modifying a Set of Baseband Equipment................................................................................................................144

7.3.4 Removing a Set of Baseband Equipment................................................................................................................147

7.3.5 Adjusting the Networking of RF Units (Between Chain and Ring Topologies).....................................................150

7.3.6 Adjusting the Networking of RF Units (From Chain to Star Topologies)..............................................................157

7.4 Transport Data Reconfiguration.................................................................................................................................163

7.4.1 Replacing the U2000...............................................................................................................................................163

7.4.2 Adjusting the VLAN Priority..................................................................................................................................168

7.4.3 Changing the VLAN Configuration Mode..............................................................................................................172

7.5 Reconfigurations Dedicated to the LampSite Solution..............................................................................................180

7.5.1 Adding a pRRU.......................................................................................................................................................180

7.5.2 Adding an RHUB....................................................................................................................................................185

7.5.3 Adding a pRRU-Aggregation Cell..........................................................................................................................189

7.5.4 Combining pRRU-Aggregation Cells.....................................................................................................................194

7.5.5 Splitting a pRRU-Aggregation Cell........................................................................................................................198

8 Reconfig uring the UMTS Network.......................................................................................203

8.1 Reconfiguring a Cell...................................................................................................................................................204

8.1.1 Changing Cell Power...............................................................................................................................................204

8.1.2 Changing Cell Frequencies......................................................................................................................................210

8.1.3 Changing the Scrambling Code of a Cell................................................................................................................212

RAN17.1




viii


10/381

8.1.4 Reconfiguring Cell System Information Parameters...............................................................................................214

8.1.5 Reconfiguring Cell Radio Link Power Parameters.................................................................................................218

8.1.6 Reconfiguring Cell Synchronization Parameters....................................................................................................220

8.1.7 Modifying the Area Information of a Cell...............................................................................................................223

8.1.8 Modifying the UTRAN Registration Area of a Cell...............................................................................................226

8.1.9 Modifying a Cell Name...........................................................................................................................................228

8.1.10 Modify the ID of a Cell.........................................................................................................................................231

8.1.11 Adding an SCCPCH..............................................................................................................................................233

8.1.12 Removing a UMTS Cell........................................................................................................................................237

8.2 Modifying an SCCPCH..............................................................................................................................................241

8.3 Reconfiguring Neighboring Cells...............................................................................................................................249

8.3.1 Adding an Intra-Frequency Neighboring Cell.........................................................................................................249

8.3.2 Adding an Inter-Frequency Neighboring Cell.........................................................................................................253

8.3.3 Adding a Neighboring GSM Cell............................................................................................................................258

8.3.4 Adding a Neighboring LTE Cell.............................................................................................................................262

8.3.5 Modifying a Neighboring Cell................................................................................................................................265

8.3.6 Removing a Neighboring Cell.................................................................................................................................266

8.4 Reconfiguring NodeB Management Distribution.......................................................................................................270

8.4.1 Regularly Reconfiguring NodeB Distribution Using MML Commands................................................................270

8.4.2 Manually Reconfiguring NodeB Distribution.........................................................................................................272

9 Reconfig uring the Interfaces...................................................................................................277

9.1 Interface Capacity Expansion.....................................................................................................................................2789.1.1 Iu-CS Interface Capacity Expansion.......................................................................................................................278

9.1.1.1 Iu-CS Interface Capacity Expansion (in ATM Transmission Mode)...................................................................278

9.1.1.2 Iu-CS Interface Capacity Expansion (in IP Transmission Mode)........................................................................282

9.1.1.3 Iu-CS Interface Capacity Expansion (IP Pool).....................................................................................................287

9.1.2 Iu-PS Interface Capacity Expansion........................................................................................................................291

9.1.2.1 Iu-PS Interface Capacity Expansion (in ATM Transmission Mode)...................................................................291

9.1.2.2 Iu-PS Interface Capacity Expansion (in IP Transmission Mode).........................................................................294

9.1.2.3 Iu-PS Interface Capacity Expansion (IP Pool).....................................................................................................299

9.1.3 Iur Inter face Capacity Expansion............................................................................................................................303

9.1.3.1 Iur Interface Capacity Expansion (in ATM Transmission Mode)........................................................................304

9.1.3.2 Iur Interface Capacity Expansion (in IP Transmission Mode).............................................................................307

9.1.3.3 Iur Interface Capacity Expansion (IP Pool)..........................................................................................................312

9.1.4 Iub Inter face Capacity Expansion............................................................................................................................317

9.1.4.1 Iub Interface Capacity Expansion (in ATM Transmission Mode).......................................................................317

9.1.4.2 Iub Interface Capacity Expansion (in IP Transmission Mode)............................................................................320

9.1.4.3 Iub Interface Capacity Expansion (IP Pool).........................................................................................................325

9.2 Reconfiguring the Transmission Mode and the Networking Mode...........................................................................329

9.2.1 Reconfiguring the Transmission Mode...................................................................................................................329

9.2.1.1 Changing the Transmission Mode over the Iub Interface from ATM to IP.........................................................329

RAN17.1




ix


11/381

9.2.1.2 Changing the Transmission Mode over the Iub Interface from ATM to IP Pool.................................................333

9.2.1.3 Changing the Transmission Mode over the Iub Interface from ATM/IP Dual Stack to IP Pool.........................339

9.2.1.4 Changing Networking Mode over the Iub Interface from IP to Transmission Resource Pool.............................345

9.2.1.5 Changing Networking Mode over the Iu-CS Interface from IP to Transmission Resource Pool........................349

9.2.1.6 Changing Networking Mode over the Iu-PS Interface from IP to Transmission Resource Pool.........................354

9.2.1.7 Changing Networking Mode over the Iur Interface from IP to Transmission Resource Pool.............................356

9.2.2 Reconfiguring Timeslot Cross Connection.............................................................................................................359

9.2.2.1 Configuring a Timeslot Cross Connection on the RNC.......................................................................................359

9.2.2.2 Configuring a Timeslot Cross Connection on a NodeB.......................................................................................361

9.3 Network Cutover........................................................................................................................................................362

9.3.1 Changing the Connection Between the BSC and the MSC.....................................................................................362

9.3.1.1 Changing the Connection Between the BSC and the MSC (IP Transmission Mode Retained on the Iu-CS Interface)

..........................................................................................................................................................................................363

9.3.1.2 Changing the Connection Between the RNC and MSC (ATM Transmission Mode Retained on the Iu-CS Interface)

..........................................................................................................................................................................................366

9.3.1.3 Changing the Connection Between the RNC and the MSC (Transmission Mode on the Iu-CS Interface Changed

from ATM to IP)...............................................................................................................................................................367

RAN17.1




x


12/381

1 Change DescriptionThis section provides information about the changes in different document versions. There are

two types of changes, including function changes and editorial changes. Function changes refer

to changes in functions of a specific product version. Editorial changes refer to changes in

wording or addition of information that was not described in the earlier version.

03 (2015-06-30)

This issue includes the following changes.

Change Type Change Description

Functional

change

New l Added descriptions about NIU reconfiguration. For

details, see 6.7.6 Adding an NIU Board and 6.8.6Removing an NIU Board.

l Added Removing an SPUb/SPUc Board (NASP),

because removing the SPUb/SPUc board (NASP) is

supported in UMTS mode.

RAN17.1

Reconfiguration Guide for BSC6900 1 Change Description



1


13/381


Modified l Deleted operations of modifying board content and

OMU configurations. For details, see 6.2 Changing

the Board Backup Mode from Independent toActive/Standby.

l Optimized the operation of adding a subrack. For

details, see 6.7.1 Adding a Subrack .

l Added the board normalization principle and

optimized operation procedures accordingly. For

details, see 6.7.2 Adding an SPUa, SPUb, or SPUc

Board, 6.7.3 Adding a DPUb/DPUe/DEUa Board,

6.7.4 Adding an ASUa Board, and 6.7.5 Adding an

Interface Board.

l Optimized the operation of removing a subrack. For

details, see 6.8.1 Removing a Subrack .

l Modified operation procedures and added

descriptions about the RUCP mode. For details, see

6.8.2 Removing an SPUa/SPUb/SPUc Board

(UCP/RUCP).

l Modified background information. For details, see

6.8.4 Removing an ASUa Board.

Deleted None

Editorial change None

02 (2015-05-08)

This issue includes the following changes.


Function change Added None.

Modified The description of the procedure is modified, and the

corresponding notes are added. For details, see6.7.1Adding a Subrack .

Deleted None.

Editorial change None.

01 (2015-03-25)

This issue does not include any changes.

RAN17.1




2


14/381

Draft A (2015-01-15)

This is the Draft A release of the RAN17.1.

Compared with issue 03 (2014-09-10) of RAN16.0, this issue includes the following changes.


Feature change New l Added the built-in ECO6910. Added sections 6.5

Install a Built-in NE, 6.6 Uninstall a Built-in NE,

6.7.4 Adding an ASUa Board, and 6.8.4 Removing

an ASUa Board.

Modified None.

Deleted None.

Editorial change None.

RAN17.1




3


15/381

2 Introduction to ReconfigurationAbout This Chapter

This chapter defines reconfiguration and introduces reconfiguration tools.

RAN17.1

Reconfiguration Guide for BSC6900 2 Introduction to Reconfiguration



4


16/381

2.1 Definition

Reconfiguration refers to the process of adding, deleting, or modifying the data of the RAN

system (consisting of at least one base station controller and one base station) after it starts

operating.

This document focuses on associated data preparation and reconfiguration procedures. The

detailed data analysis process for network optimization and the number of boards and links for

capacity expansion are determined according to actual network conditions.

This document involves the following scenarios:

l Network optimization

Network optimization is the process of adjusting and optimizing network performance

based on the data obtained from performance measurements or drive tests when the network

is in service.

l System capacity expansion

System capacity ex pansion enables the system to serve more users with hardware addition

or reconfiguration in the existing network.

l Transmission reconstruction

Transmission reconstruction is the process of changing the transmission mode of the

existing transport network.

l Network cutover

Network cutover is the process of physically or logically changing the cables or devices in

use.NOTE

This document describes only the data configuration procedure. The data planning is described in

professional service documentation.

2.2 Tools

The local maintenance terminal (LMT) and the Configuration Management Express (CME) can

be used to configure the BSC6900.

Table 2-1 describes the reconfiguration tools.

Table 2-1 Reconfiguration tools

Data Configuration Tool Function

LMT The LMT provides graphic user interfaces (GUIs) for users to

configure a single network element (NE) using MML

commands.

CME The CME provides GUIs for users to configure a single base

station controller, base station, or cell. In addition, the CME

supports batch configuration of multiple base stations and

cells by importing or exporting a configuration file.

RAN17.1




5


17/381

Process of Reconfiguring Data Using the CME

When reconfiguring data by using the CME, the operation process is the same in eachreconfiguration scenario but data reconfiguration steps are different. Figure 2-1 shows the

process of reconfiguring data. Table 2-2 describes the process.

Figure 2-1 Reconfiguration process

NOTE

You can press F1 to view the CME Help for the function description and related operations.

Table 2-2 Reconfiguration process

Procedure Description

Ensure thatthe NE is

connected to

the U2000

You can use the CME to configure NE data only after the NE is successfullyconnected to the U2000.

Collect

configuration

data

Before configuring data, you have to collect the data to be configured.

RAN17.1




6


18/381


Start the CME CME functions can be started in the following modes: CME client mode and

U2000 client mode. The methods of starting the CME are as follows:

l CME client mode

– Start CME functions on the U2000 client in application mode.

1. On the Windows desktop, choose Start > All Programs >

iManager U2000 MBB Client > U2000version Client. The login

dialog box is displayed.

2. Enter the user name and password, and click Login.

NOTE

You can click to add, modify, or delete server information.

3. Log in to the U2000 client and click in the upper left part

of the U2000 main window. The application window is displayed.

4. On the Application Center tab page, double-click the CME icon

to start the CME.

– Start the CME client directly.

1. On the Windows desktop, choose Start > All Programs >

iManager U2000 MBB Client > CM Express. The login dialog

box is displayed.


NOTE


l U2000 client mode

Start CME functions on the U2000 client in traditional mode.

1. On the Windows desktop, choose Start >All Programs > iManager

U2000 MBB Client > U2000 version Client. The login dialog box

is displayed.


NOTE


3. After logging in to the U2000 client, choose CME on the menu bar

of the U2000 main window and then choose a submenu item to start

the related CME function.

RAN17.1




7


19/381


Create a

planned data

area.

You have to create a planned data area before configuring data.

1. On the menu bar, choose Area Management > Planned Area > Create

Planned Area (CME client mode) or CME > Planned Area > CreatePlanned Area (U2000 client mode). A dialog box is displayed for you

to create a planned data area.

2. Add the NEs that you want to reconfigure to the planned data area that

you want to create. Enter the information about the planned data area and

click OK . The CME starts to create the planned data area. After the

planned data area is created, the CME automatically opens it.

For details about how to create a planned data area, press F1 to obtain

the online help.

Reconfigure

data.

Data is reconfigured using different CME functions based on scenarios. You

need to check the reconfiguration operations in each scenario.

Verify data. After data reconfiguration is complete, verify the data to ensure data

accuracy.

l Check accuracy and integrity of configuration data.

1. On the menu bar of the planned data area, choose Advanced > Check

Data (CME client mode) or CME > Advanced > Check Data

(U2000 client mode) to start verification.

2. Select the NEs that you want to verify from the navigation tree in the

left pane, add them to the right pane, and click OK . The CME starts

the verification. You can verify the configuration data for a maximum

of 50 NEs at a time.l Check configuration data consistency.

On the menu bar of the current or planned data area, choose Advanced

> Consistency Check (CME client mode) or CME > Advanced >

Consistency Check (U2000 client mode) to start the data consistency

check.

For detailed operations, see section Manually Checking NE Data

Consistency in the U2000 Help.

l Check for any conflicts between configuration data and data on the live

network. Before activating configuration data, you can compare

configuration data in the planned data area with the live network

configuration data in the current data area to locate data conflicts. Then,

you can reconfigure the data in the planned data area based on the check

results to ensure successful data activation.

On the menu bar of the planned data area, choose Area Management >

Planned Area > Check Conflict (CME client mode) or CME > Planned

Area > Check Conflict (U2000 client mode) to start the conflict check.

For detailed operations, see section Checking for Data Conflicts in the

U2000 Help.

When verifying configuration data, modify configuration data as prompted

until the verification succeeds.

RAN17.1




8


20/381


Export

configuration

and rollback scripts.

Export configuration data from the CME as a script. When exporting the

script, the CME automatically generates a rollback script.

On the menu bar of the planned data area, choose Area Management >Planned Area > Export Incremental Scripts (CME client mode) or

CME > Planned Area > Export Incremental Scripts (U2000 client

mode). Then, export configuration scripts.

NOTE

l If the OMCH is disconnected in the reconstruction scenario, you are advised to

export the full base station script during the script export.

The operation portal is as follows: Choose Advanced > Export NE Files (CME

client mode) or CME > Advanced > Export NE Files (U2000 client mode) on

the current or planned data area.

l When you export incremental scripts:

l If you need to check or edit scripts in the script executor window beforeactivating the scripts, select Launch script executor only during the export.

The CME then automatically uploads the scripts to the U2000 server.

l If you need to immediately activate scripts after they are exported, select

Launch script executor and activate exported project during the export.

l If you do not need to activate scripts or check scripts in the script executor

window, select Do not launch script executor during the export.

For detailed operations, see section Exporting Incremental Scripts from

a Planned Data Area in the U2000 Help.

Activate

scripts.

Activate the scripts exported the CME for them to take effect on NEs. If

Launch script executor and activate exported project is not selected

when you export scripts, you have to manually activate the scripts.

1. On the menu bar of the CME main window, choose System > Script

Executor (CME client mode) or CME > Script Executor (U2000 client

mode). The script executor window is displayed.

2. (Optional and required when Do not launch script executor is selected

during the script export) Choose Project > Load Project on the menu

bar of the script executor. In the displayed dialog box, select the folder

that stores the scripts to be activated (the folder must contain the

scriptcfg.xml file), and click Select. The script executor window is

displayed again. Right-click one or more projects to be uploaded and

choose Upload Project from the shortcut menu. Enter the project

description and click OK .

3. Right-click a project to be activated in the right pane and chooseActivate

Project from the shortcut menu.

Before activating a project, you are advised to preactivate the project to

check script correctness by performing the following operation: Right-

click the project and choose Preactivate Project from the shortcut menu.

For detailed operations, see section Activating Data Using the Script

Executor in the U2000 Help.

RAN17.1




9


21/381

3 Checking a LicenseThis section describes how to check a newly granted license of the base station controller.

Prerequisites

l A new license has been granted.

l The license file has been imported to the \ftp\license directory in the installation directory

of the OMU active workspace. For details about how to import the license file, see FTP

Server.

Context

A new license is required in the following situations:

l A network is deployed.

l New license control items are introduced to the customization (C) version to be upgraded.

These license control items, however, are not defined in the license file of the earlier version.

l New license control items are introduced to the C version to be upgraded. These license

control items are defined in the license file of the earlier version, but their values are

incorrect.

l The release (R) version is upgraded.

l The equipment serial number (ESN) changes.

l The functions controlled by a license need to be enabled.

l The license in use is about to expire.

l BTSs are redistributed among BSCs, and the original licensed value cannot meet the license

requirement after the BTS redistribution. Therefore, new licenses are required.

Procedure

Step 1 Run the CHK DATA2LIC command to check a license file. In this step, set File Name to anappropriate value.

----End

RAN17.1

Reconfiguration Guide for BSC6900 3 Checking a License



10


22/381

Example

/*Checking the license file named ON1020691_GU2.dat*/

CHK DATA2LIC: FN="ON1020691_GU2.dat";

Follow-up Procedure

After the verification succeeds, run the ACT LICENSE command to activate the license.

RAN17.1

Reconfiguration Guide for BSC6900 3 Checking a License



11


23/381

4 Backing Up and Restoring DataAbout This Chapter

During network optimization, some parameters are reconfigured, but the network performance

is not as good as expected. When this occurs, you can restore to the original network conditions

by backing up and restoring data.

Context

Table 4-1 Data restoration

NE Data Restoring Description

Strength Weakness

Base

station

controll

er

Restore the configuration

database stored on the

OMU board.

This operation is simple.

The data can be definitely

restored to the original

status.

The base station

controller is restarted

during a rollback, and

services are interrupted.

Execute rollback scripts. You do not need to restart

the base station controller

during the rollback.

Services are notinterrupted.

The procedure for making

rollback scripts is

complex.

Use the CME to back up

and restore data.

This operation is simple. The rollback succeeds

only in some scenarios.

Base

station

Execute rollback scripts. None The procedure for making

rollback scripts is

complex.

Use the CME to back up

and restore data.

This operation is simple. The rollback succeeds

only in some scenarios.

RAN17.1

Reconfiguration Guide for BSC6900 4 Backing Up and Restoring Data



12


24/381

For the procedure of restoring data by executing rollback scripts, see sections "Follow-up

Procedure" and "Rollback" in each reconfiguration scenario.

For the procedure of backing up and restoring data using the Configuration Management Express

(CME), see Backing Up and Restoring Data (CME-Based).

This chapter describes how to back up and restore the configuration database stored on the OMU

board of the base station controller.

RAN17.1




13


25/381

4.1 Backing Up and Restoring Data (Dopra Linux)

This section describes how to back up and restore data when the OMU runs the Dopra Linuxoperating system.

4.1.1 Starting the omu_backup_linker tool

This section describes how to start the omu_backup_linker tool.

Context

l If an independent OMU is configured, log in to the OMU to start the omu_backup_linker

tool.

l If active and standby OMUs are configured, log in to the active OMU to start the

omu_backup_linker tool.

Procedure

Step 1 Log in to the target OMU by referring to Logging In to the OMU.

Step 2 Enter cd /mbsc/bam/common/services to go to the directory where the program of theomu_backup_linker tool is saved.

Step 3 Enter ./omu_backup_linker to start the omu_backup_linker tool. The following information is

displayed:

# The backup/restore option

# backup :Backup OMU database

# restore :Restore OMU database

# Please select one option to backup or restore OMU database, if you don't know it,

consult the administrator.

Please input a valid bkp_res_type :

----End

4.1.2 Backing Up the System Data

This section describes how to back up the BSC6900 configuration data, performance data, alarmdata, operation logs, operator account, rights information, and product information using an

MML command or the omu_backup_linker_tool. The backup data can be encrypted to ensure

the security in data storage and transmission.

Prerequisites

l Using an MML command:

You have logged in to the LMT by referring to Logging In to and Logging Out of the LMT.

l Using the omu_backup_linker_tool:

The Logging In to the OMU is connected.

RAN17.1




14


26/381

Context

NOTICEl When the OMUs work in active/standby mode, the system data must be backed up on the

active OMU.

l Before capacity expansion, upgrade, or software loading, you must back up the OMU data

manually to avoid a system data backup failure.

Procedure

l Using an MML command

1. Run the BKP DB command to back up the data to the specified directory on the OMU

hard disk. In this step, set Path of Backup File and Backup File Name to appropriate

values. If the backup file needs to be encrypted, set Encrypted Mode to Password

Encrypted and specify File Encryption Password.

2. Obtain the backup file from the specified directory by referring to the procedures

described in Transferring OMU Files to a Local PC.

l Using the omu_backup_linker_tool

1. Log in to the target OMU.

2. Enter cd /mbsc/bam/common/services to go to the directory where the program of

the omu_backup_linker tool is saved.

3. Enter ./omu_backup_linker to start the omu_backup_linker tool.

4. Enter backup after the Please input a valid bkp_res_type : message

is displayed.

5. Enter the save path and names of the backup files.

6. Enter the encryption mode when the Please input a valid encrypt

mode : message is displayed. If the backup file does not need to be encrypted, enter

unencrypt. If the backup file needs to be encrypted, enter encrypt.

7. If you have entered encrypt in the previous step, enter File Encryption Password.

The system starts to back up data. If the data is successfully backed up to the OMU

hard disk, the Backup OMU database succeed! message is displayed.

8. Obtain the backup file from the specified directory by referring to the proceduresdescribed in Transferring OMU Files to a Local PC.

----End

Example

Backing up the OMU data to /mbsc/bam using the omu_backup_linker_tool and naming the

file as omu.bak with the file encrypted

omd_test_name /mbsc/bam/common/services # ./omu_backup_linker


# backup : Backup OMU database# restore : Restore OMU database

RAN17.1




15


27/381

# Please select one option to backup or restore OMU database, if you don't know

it, please consult the administrator.

Please input a valid bkp_res_type : backup

# The backup file pathname.

# eg: d:/mbsc/bam/omu.bak, in windows;

# eg: /mbsc/bam/omu.bak, in linux.

Please input a valid backup file pathname : /mbsc/bam/omu.bak# The backup file encrypted mode.

# unencrypt: The backup file is unencrypted.

# encrypt: The backup file is encrypted.

Please input a valid encrypt mode : encrypt

# The backup file password.

Please input a valid file password :

Backup omu database [100%]

Backup OMU database succeed!

omd_test_name /mbsc/bam/common/services #

4.1.3 Restoring the System Data

This section describes how to restore the system data using the data backup file and using the

encrypted backup file.

Prerequisites

The system data has been backed up.

Context

Restoring the BSC6900 system data will interrupt services on the BSC6900. The data on the

host will be inconsistent with the data on the OMU after the system data is restored. As a result,

the services will be greatly impacted. Therefore, you are advised to restore the system data inthe early morning hours when traffic volume is low.

As an example, the OMU in active/standby mode is used in this document. If an OMU is in

independent mode, skip operations on the standby OMU.

This chapter describes how to restore data by using the following methods:

l If an MML command is used to restore data, only the BSC6900 configuration data is

restored while other data, such as alarm data or performance data, cannot be restored.

l If the omu_backup_linker tool is used to restore data, all BSC6900 data is restored,

including configuration data, alarm data, performance data, operating logs, administrator

account, authority information, SSL configuration information, certificate information and product information.

Procedure

l Restoring the system data through an MML command

1. Run the LST BKPFILE command to query data backup files saved in the OMU

active workspace installation directory\data\backup directory.

2. Run the RTR DB command to restore configuration data on the OMU. If the backup

file is encrypted, specify Encrypted Mode and File Encryption Password.

3. Run the LST SUBNET and DSP OMU commands to query the internal network

segments. If the queried internal network segments in the two command outputs are

RAN17.1




16


28/381

different, run the RST OMU command to perform soft resets on the active and standby

OMU boards.

l Restoring the system data by using the omu_backup_linker tool

1. Log in to the active and standby OMUs by referring to Logging In to the OMU.

2. Enter /etc/rc.d/omud stop to stop the omud process on the active and standby OMUs.

3. Restore data in the original active OMU using the omu_backup_linker tool.

a. Enter cd /mbsc/bam/common/services to go to the directory where the program

of the omu_backup_linker tool is saved

b. Log in to the OMU by referring to Enter ./omu_backup_linker to start the


c. Enter restore and press Enter after the Please input a valid

bkp_res_type : message is displayed.

d. Type the save path and name of the backup file and press Enter when the

Please input a valid backup file pathname : message isdisplayed.

e. Enter the encryption mode when the Please input a valid encrypt

mode : message is displayed. If the backup file has not been encrypted, enter

unencrypt. If the backup file has been encrypted, enter encrypt. Then, press

Enter.

f. If you enter encrypt in the previous step, specify File Encryption Password

and press Enter. The system data starts to be restored. After the restoration is

complete, a message is displayed, indicating whether the restoration is

successful. If the restoration is successful, the Restore OMU database

succeed! message is displayed on the interface.

4. Copy and save the backup file to be restored in the standby OMU using the psftp

software. For details, see Obtaining and Using the psftp Software.

5. Repeat Step 3 to restore data in the original standby OMU using the


6. Enter /etc/rc.d/omud start to start the omud on the active and standby OMUs.

7. Log in to the LMT by referring to Logging In to and Logging Out of the LMT in the

BSC6900 UMTS LMT User Guide.

8. Run the LCK CMCTRL command to lock the data configuration right.

9. Run the LST CFGMODE command to query whether the System Configuration

Mode parameter is set to Effective Mode for all subracks. If this parameter is set toIneffective Mode for any subrack, run the SET CFGDATAEFFECTIVE command

to change the value to Effective Mode.

10. Check the consistency between the BSC6900 host data and the OMU data.

NOTE

After data restoration, check whether the BSC6900 host data is consistent with the OMU data.

If not, load the restored data to the BSC6900 host.

a. Run the ACT CRC command to check whether the host data is consistent with

the OMU data.

– If the data is consistent, end this task.

– If the data is inconsistent, go to 10.2.

RAN17.1




17


29/381

b. Run the FMT DATA command to format the data in the OMU database so that

the data can be loaded into the host.

c. If data inconsistency occurs in only one subrack, run the RST SUBRACK

command to reset this subrack. Before running the command, set Subrack No.

----End

Example

Restore the OMU data by using the omu.bak.ecf file (the file name extension after encryption

is .ecf) under /mbsc/bam. The following shows an example of the results:omd_test_name ~ # /etc/rc.d/omud stop

Shutting down mbsc daemon..........

omd_test_name ~ # cd /mbsc/bam/common/services

omd_test_name /mbsc/bam/common/services # ./omu_backup_linker


# backup : Backup OMU database

# restore : Restore OMU database

# Please select one option to backup or restore OMU database, if you don't know

it, please consult the administrator.

Please input a valid bkp_res_type : restore

# The backup file pathname.

# eg: d:/mbsc/bam/omu.bak, in windows;

# eg: /mbsc/bam/omu.bak, in linux.

Please input a valid backup file pathname : /mbsc/bam/omu.bak.ecf

# The backup file encrypted mode.

# unencrypt: The backup file is unencrypted.

# encrypt: The backup file is encrypted.

Please input a valid encrypt mode : encrypt

# The backup file password.

Please input a valid file password :

Restore omu database [100%]

Restore OMU database succeed!

omd_test_name /mbsc/bam/common/services # /etc/rc.d/omud start

Starting mbsc daemon

4.2 Backing Up and Restoring Data (Windows)

This section describes how to back up and restore data when the OMU uses the Windows

operating system.

4.2.1 Starting the omu_backup_linker tool

This section describes how to start the omu_backup_linker tool.

Context

l If an independent OMU is configured, log in to the OMU to start the omu_backup_linker

tool.

l If active and standby OMUs are configured, log in to the active OMU to start the


Procedure

Step 1 Log in to the target OMU by referring to Logging In to the OMU.

RAN17.1




18


30/381

Step 2 Choose Start > Run. Then enter the cmd command and press Enter to enter the command modeof the OMU.

Step 3 Enter the cd /d d:\mbsc\bam\common\services command and press Enter to go to the directorywhere the program of the omu_backup_linker tool is saved.

Step 4 Type the omu_backup_linker.exe command and press Enter. As Figure 4-1 shows, aninterface is displayed.

Figure 4-1 Starting the omu_backup_linker Tool

----End

4.2.2 Backing Up the System Data

This section describes how to back up the BSC6900 configuration data, performance data, alarm

data, operation logs, operator account, rights information, and product information using an

MML command or the omu_backup_linker_tool. The backup data can be encrypted to ensure

the security in data storage and transmission.

Prerequisites

l Using an MML command:

You have logged in to the LMT by referring to Logging In to and Logging Out of the LMT.

l Using the omu_backup_linker_tool:

You have logged in to the OMU by referring to Logging In to the OMU.

RAN17.1




19


31/381


32/381

4. Enter the save path and names of the backup files.

Figure 4-3 Entering the save path and names of backup files

5. If the backup file does not need to be encrypted, enter unencrypt. If the backup file

needs to be encrypted, enter encrypt, as shown in Figure 4-4.

Figure 4-4 Specifying encryption mode of the backup file

6. If you have entered encrypt in the previous step, enter File Encryption Password,

as shown in Figure 4-5.

RAN17.1




21


33/381

Figure 4-5 Entering the file encryption password

7. The system starts to back up data. If the data is successfully backed up to the OMU

hard disk, the "Backup OMU database succeed!" message is displayed, as

shown in Figure 4-6.

Figure 4-6 Backup result indication

8. Press any key to exit.

----End

RAN17.1




22


34/381

4.2.3 Restoring the System Data

This section describes how to restore the system data using the data backup file and using the

encrypted backup file.

Context

Restoring the BSC6900 system data will interrupt services on the BSC6900. The data on the

host will be inconsistent with the data on the OMU after the system data is restored. As a result,

the services will be greatly impacted. Therefore, you are advised to restore the system data in

the early morning hours when traffic volume is low.

As an example, the OMU in active/standby mode is used in this document. If an OMU is in

independent mode, skip operations on the standby OMU.

This chapter describes how to restore data by using the following methods:

l If an MML command is used to restore data, only the BSC6900 configuration data is

restored while other data, such as alarm data or performance data, cannot be restored.

l If the omu_backup_linker tool is used to restore data, all BSC6900 data is restored,

including configuration data, alarm data, performance data, operating logs, administrator

account, authority information, SSL configuration information, certificate information and

product information.

Procedure

l Restoring the system data through an MML command

1. Run the LST BKPFILE command to query data backup files saved in the OMUactive workspace installation directory\data\backup directory.

2. Run the RTR DB command to restore configuration data on the OMU. If the backup

file is encrypted, specify Encrypted Mode and File Encryption Password.

3. Run the LST SUBNET and DSP OMU commands to query the internal network

segments. If the queried internal network segments in the two command outputs are

different, run the RST OMU command to perform soft resets on the active and standby

OMU boards.

l Restoring the system data by using the omu_backup_linker tool

1. (Optional) If the OMUs work in active/standby mode, stop the data synchronization

between the active and standby OMUs by referring to Stopping the Synchronizationof the Data of the Active and Standby OMUs

2. Log in to the active and standby OMUs by referring to Logging In to the OMU.

3. Choose Start > Run. Enter the cmd command to enter the command mode of the

OMU on the active and standby OMUs.

4. Run the net stop omud command to stop the omud on the active and standby OMUs.

5. Restore data in the original active OMU using the omu_backup_linker tool.

a. Choose Start > Run. Then enter the cmd command and press Enter to enter the

command mode of the OMU.

b. Enter the cd /d d:\mbsc\bam\common\services command and press Enter to

go to the directory where the program of the omu_backup_linker tool is saved.

RAN17.1




23


35/381

c. Enter the omu_backup_linker.exe command and press Enter to start the


d. Enter the restore command and press Enter on the interface, as shown in Figure

4-7.

Figure 4-7 Restoring the system data

e. Enter the save path and names of the backup files, and then press Enter.

Figure 4-8 Entering the save path and names of backup files

f. If the backup file is not encrypted, enter unencrypt. If the backup file is

encrypted, enter encrypt. Then, press Enter, as shown in Figure 4-9.

RAN17.1




24


36/381

Figure 4-9 Entering the mode of the backup files to be restored

g. If you enter encrypt in the previous step, specify File Encryption Password

and press Enter, as shown in Figure 4-10.

Figure 4-10 Entering the file encryption password

h. The system data starts to be restored. After the restoration is complete, a message

is displayed, indicating whether the restoration is successful. If the restoration is

successful, the Restore OMU database succeed! message is displayed

on the interface, as shown in Figure 4-11.

RAN17.1




25


37/381

Figure 4-11 Result indication of restoring the system data

i. Press any key to exit.

6. Copy and save the backup file to be restored in the standby OMU using file sharing.

For details, see Uploading Files to the OMU.

7. Repeat Step 5 to restore data in the original active OMU using the omu_backup_linker

tool.

8. Managing the omud on the active and standby OMUs.

9. Log in to the LMT by referring to Logging In to and Logging Out of the LMT in the

BSC6900 UMTS LMT User Guide.

10. Run the LCK CMCTRL command to lock the data configuration right.

11. Run the LST CFGMODE command to query whether the System Configuration

Mode parameter is set to Effective Mode for all subracks. If this parameter is set to

Ineffective Mode for any subrack, run the SET CFGDATAEFFECTIVE command

to change the value to Effective Mode.

12. Check the consistency between the BSC6900 host data and the OMU data.

NOTE

After data restoration, check whether the BSC6900 host data is consistent with the OMU data.

If not, load the restored data to the BSC6900 host.

a. Run the ACT CRC command to check whether the host data is consistent with

the OMU data.

– If the data is consistent, end this task.

– If the data is inconsistent, go to 12.2.

b. Run the FMT DATA command to format the data in the OMU database so that

the data can be loaded into the host.

c. If data inconsistency occurs in only one subrack, run the RST SUBRACK

command to reset this subrack. Before running the command, set Subrack No.

RAN17.1




26


38/381

13. (Optional, required only for Step 1) Run the MML command STR DATASYNC to

start data synchronization between the active and standby OMUs.

----End

RAN17.1




27


39/381

5 Backing Up and Restoring Data by CMEThis section describes how to back up and restore data. Users can use the function to restore the

network to the state before parameters were reconfigured during network performance

optimization, if the network performance does not meet users' expectations.

Context

The CME provides the following methods for you to back up and restore data:

You create a planned data area to reconfigure network data. All the operations performed in the

planned data area are recorded and then exported as a script. This script takes effect on the live

network after it is activated by the script executor. When exporting the script, the CME generates

a fallback script. If unsatisfied with the reconfiguration, you can activate the fallback script to

restore the network to a state before the reconfiguration.

Procedure

Step 1 After you perform operations based on the process for reconfiguring data using the CME, theCME automatically generates a data fallback script. For details about the process, see Process

for Reconfiguring Data Using the CME.

Step 2 Perform steps based on Fallback in each scenario.

1. On the menu bar of the CME main window, chooseSystem > Script Executor (CME client

mode) or CME > Script Executor (U2000 client mode). The script executor window is

displayed.

2. In the Script Executor window, click the Summary tab.

3. Right-click the project whose data you want to roll back and choose Activate Fallback

Project from the shortcut menu.

You can press F1 on the CME to view section Fallback Based on Configuration Steps in the

U2000 Help for the detailed function operations and introduction.

----End

RAN17.1

Reconfiguration Guide for BSC6900 5 Backing Up and Restoring Data by CME



28


40/381

6 Reconfiguring the BSC6900About This Chapter

This chapter describes how to reconfigure a running BSC6900 or expand its capacity.

RAN17.1

Reconfiguration Guide for BSC6900 6 Reconfiguring the BSC6900



29


41/381

6.1 Changing Signaling Points

When a BSC is relocated or a network is optimized, originating signaling points (OSPs) and

destination signaling points (DSPs) change. In this case, you need to change related settings.

Prerequisites

l Before changing signaling points, collect information listed in Table 6-1.

Table 6-1 Required information

Information Description

OSP information Query and record the name and code of a

new OSP.

DSP information Query and record the name and code of a

new DSP.

l Hardware requirement

– None

l Software requirement

– None

l License requirement

– None

Context

NOTICE

Changing signaling points will interrupt BSC services. Therefore, perform this operation when

the traffic is light, for example, during early morning hours.

Prepare the data listed in the following table.

Table 6-2 Data preparation

DataType

MO Setting Notes DataSource

MMLCommand

OSP OPC Set OSP name and OSP code to the

target values.

Network

plan

MOD OPC

DSP N7DPC Set DSP name and DSP code to the

target values.

Network

plan

MOD

N7DPC

RAN17.1




30


42/381

Procedure

l Using MML commands

– Record the information before reconfiguration

1. Run the LST OPC command to query the values of all OSP-related parameters.

2. Run the LST N7DPC command to query the values of all DSP-related parameters.

– Change information about an OSP.

1. Run the MOD OPC command to modify the values of OSP name and OSP

code.

– Change information about a DSP.

1. Run the MOD N7DPC command to modify the values of DSP name and DSP

code.

2. Run the MOD UCNNODE command to modify the CN node.l The CME-based procedure is as follows:

1. Select a base station controller in the left pane of the planned data area. The NE object

tree is displayed in the lower part of the left pane, as shown in the following figure:

Figure 6-1 Configuration window

2. In area 1, select or search for the MO you want to configure based on the following

list and double-click the MO. In area 2, set parameters for the MO and click to

save configured data.

----End

RAN17.1




31


43/381

Example

/*Information Recording Procedure*/

//Recording the OSP information

LST OPC: SPX=1, SPDF=WNF;//Recording the DSP information

LST N7DPC: DPX=1, SPDF=WNF;

/*Reconfiguration Procedure*/

//Changing information about an OSP

MOD OPC: SPX=1, SPCBITS=BIT14, SPDF=WNF, SPC=10001, NAME="OPCName2";

//Changing information about a DSP

MOD N7DPC: DPX=1, SPDF=WNF, DPC=1002, NAME="DPCName2";

//Modifying the CN node

MOD UCNNODE: CnOpIndex=0, CNId=0, CNDomainId=PS_DOMAIN;

Follow-up Procedure

l Verification

Run the LST OPC command to check that the values of OSP-related parameters are

consistent with the data plan.

Run the LST N7DPC command to check that the values of DSP-related parameters are

consistent with the data plan.

l Rollback

–

Using MML commandsThe rollback procedure is similar to the reconfiguration procedure, except that

parameters in the rollback procedure are set to values used before the reconfiguration.

– The CME-based procedure is as follows:

1. On the menu bar of the CME main window, choose System > Script Executor

(CME client mode) or CME > Script Executor (U2000 client mode). The script

executor window is displayed.

2. In the Script Executor window, click the Summary tab.

3. Right-click the project whose data you want to roll back and choose Activate

Fallback Project from the shortcut menu.

You can press F1 on the CME to view section Fallback Based on Configuration

Steps in the U2000 Help for the detailed function operations and introduction.

6.2 Changing the Board Backup Mode from Independent toActive/Standby

To improve the reliability of BSC6900 boards, change the backup mode of boards from

independent to active/standby. This section describes how to change the backup mode of

interface boards and .

RAN17.1




32


44/381

Prerequisites

l Before changing the board backup mode, collect information listed in Table 6-3.



Board information Query and record the number, model,

backup mode, and slots that accommodate

the boards.


– The interface board and cables have been installed.

l Software requirement

– None

l License requirement

– None

Context

NOTICE

lSkip the following operations for DPU boards that work in resource pool mode.

l Reset the BSC6900 after changing the board backup mode.

l Verify the network reliability after changing the board backup mode.

For details about how to change the backup mode of the OMU board from independent to active/

standby, see Setting the OMU Working Mode.

After changing the backup mode of an IP interface board to active/standby, manually configure

port IP addresses for the standby board or configure ports in active/standby mode.

If ports that do not work in active/standby mode are used to transmit data, run the

ADDETHIP command to configure port IP addresses for the standby board.

If ports in active/standby mode are used to transmit data, the port IP address of the standby board

is the same as that of the active board. In this case, run the ADD ETHREDPORT command to

configure ports in active/standby mode.

Prepare the data listed in the following table.

Table 6-4 Data preparation

MO Setting Notes Data Source MML Command

BRD Set Backup to YES(YES). Internal plan MOD BRD

RAN17.1




33


45/381

Procedure

l Information Recording Procedure

1. Run the LST BRD command to query the board information before the

reconfiguration.

l Reconfiguration Procedure

1. Run the SET CFGDATAINEFFECTIVE command to set the configuration mode

of all subracks to ineffective mode.

2. Run the MOD BRD command to change the board backup mode to active/standby.

3. Run the SET CFGDATAEFFECTIVE command to set the configuration mode of

all subracks to effective mode.

4. Run the FMT DATA command to generate a data configuration file.

5. Run the RST BSC command to reset the BSC6900.

----End

Example

/*Information Recording Procedure*/

//Recording board information before the reconfiguration

LST BRD:;

/*Reconfiguration Procedure*/

//Setting the configuration mode of subrack 1 to ineffective mode

SET CFGDATAINEFFECTIVE: SRN=1;

//Changing the backup mode of the board in slot 14 of subrack 1MOD BRD: BRDCLASS=INT, SRN=1, SN=14, RED=YES;

//Adding two Ethernet ports working in active/standby mode

ADD ETHREDPORT: SRN=1, SN=14, PN=1;

//Setting the configuration mode of all subracks to effective mode

SET CFGDATAEFFECTIVE:;

//Generating a data configuration file

FMT DATA: SRN=1, WORKAREA=Active;

//Resetting the BSC

RST BSC: OT=BYBSCID, BSCID=1;

Follow-up Procedure

l Verification

For the detailed verification procedure, see Verifying Network Reliability.

l Rollback

The board backup mode rollback from active/standby to independent is not supported.

RAN17.1




34


46/381

6.3 Adjusting OMU Slots

This section describes how to adjust the slots that accommodate the operation and maintenance

units (OMUs).

Prerequisites

l Before adjusting the OMU slots that accommodate the OMUs, collect information listed

in Table 6-5.



OMU Slots Query and record the slots that

accommodate the OMUs.


RAN17.1 Reconfiguration Guide for BSC6900(03)(PDF)-En

Documents