BSC6900 UMTS OMU Administration Guide (V900R014C00 - 08) (PDF) - EN PDF

BSC6900 UMTS
V900R014C00
OMU Administration Guide
Issue 08
Date 2013-06-25
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior 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: support@huawei.com
Issue 08 (2013-06-25) Huawei Proprietary and Confidential i

Copyright Huawei Technologies Co., Ltd.
BSC6900 UMTS
OMU Administration Guide About This Document
About This Document
Purpose
This document describes the software and hardware structure, software installation, GUI, and
operations for the OMUa/OMUc board.
Product Version
The following table lists the product version related to this document.
Product Name Product Version
BSC6900 V900R014C00
Intended Audience
This document is intended for:
l Field engineers
l Shift operators
Organization
1 Changes in the BSC6900 UMTS OMU Administration Guide
This document describes the changes in the BSC6900 UMTS OMU Administration Guide.
2 Introduction to OMU
The physical entity of the OMU is the OMUa/OMUc board. The OMU collects and processes
information about operation and maintenance (OM), and reports this information to the OM
terminal: either the LMT or M2000.
3 Working Principles of the OMU
This section has the following topics:
4 Scenario: Deploying a BSC6900
Issue 08 (2013-06-25) Huawei Proprietary and Confidential ii

BSC6900 UMTS
This section describes how to install software and perform operation and maintenance for the
OMU when a BSC6900 is deployed.
5 Scenario: Upgrading from the BSC6810 to the BSC6900
This chapter describes how to install software and perform operation and maintenance for the
OMU when the BSC6810 is upgraded to the BSC6900.
6 Appendix: Security FAQ
This section describes how to improve the security of the BSC6900.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level or medium level of risk

which, if not avoided, could result in death or serious injury.
Indicates a hazard with a low level of risk which, if not

avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation that, if not

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated 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
Issue 08 (2013-06-25) Huawei Proprietary and Confidential iii

BSC6900 UMTS
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.
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.
Issue 08 (2013-06-25) Huawei Proprietary and Confidential iv

BSC6900 UMTS
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.
Issue 08 (2013-06-25) Huawei Proprietary and Confidential v

BSC6900 UMTS
OMU Administration Guide Contents
Contents
About This Document.....................................................................................................................ii

1 Changes in the BSC6900 UMTS OMU Administration Guide............................................1
2 Introduction to OMU..................................................................................................................10
2.1 Position of the OMU in the BSC6900..........................................................................................................................11
2.2 OMUa Board................................................................................................................................................................11
2.2.1 Functions of the OMUa Board..................................................................................................................................12
2.2.2 Panel of the OMUa Board.........................................................................................................................................12
2.2.3 Ports on the OMUa Board.........................................................................................................................................14
2.2.4 LEDs on the OMUa Board........................................................................................................................................14
2.2.5 Technical Specifications of the OMUa Board...........................................................................................................15
2.3 OMUc Board................................................................................................................................................................17
2.3.1 Functions of the OMUc Board..................................................................................................................................17
2.3.2 Panel of the OMUc Board.........................................................................................................................................17
2.3.3 Ports on the OMUc Board.........................................................................................................................................19
2.3.4 LEDs on the OMUc Board........................................................................................................................................19
2.3.5 Technical Specifications of the OMUc Board...........................................................................................................20
2.4 OMU Software.............................................................................................................................................................22
2.4.1 OMU Software Monitoring.......................................................................................................................................22
2.4.2 OMU Application Structure......................................................................................................................................23
2.4.3 OMU Service Monitoring Entities............................................................................................................................24
2.4.4 OMU Service Processes............................................................................................................................................25
2.5 OMU Working Mode...................................................................................................................................................27
2.6 OMU OM Methods......................................................................................................................................................27
2.7 OMU Safety Information..............................................................................................................................................28
3 Working Principles of the OMU..............................................................................................30

3.1 OMU Ethernet Adapter Configuration.........................................................................................................................31
3.2 OMU IP Address Plan..................................................................................................................................................33
3.3 OMU Networking Principle.........................................................................................................................................43
3.4 Active/Standby Workspaces of the OMU....................................................................................................................54
3.5 Heartbeat Detection on Active and Standby OMUs.....................................................................................................55
3.6 Synchronization Between Active and Standby OMUs.................................................................................................55
3.7 Switchover Between Active and Standby OMUs.........................................................................................................56
Issue 08 (2013-06-25) Huawei Proprietary and Confidential vi

BSC6900 UMTS
4 Scenario: Deploying a BSC6900................................................................................................58

4.1 Installing the OMU Applications in Field Commissioning..........................................................................................61
4.1.1 Setting the Link Mode of the External OMU Ethernet Adapter................................................................................61
4.1.2 Commissioning OMU Onsite....................................................................................................................................62
4.2 Reinstalling Software Onsite........................................................................................................................................68
4.2.1 Preparations for Installing Software Onsite...............................................................................................................68
4.2.2 Optional: Installing the Operating System and OMU Applications..........................................................................69
4.2.3 Optional: Installing the OMU Applications..............................................................................................................82
4.3 Operating and Maintaining the OMU...........................................................................................................................94
4.3.1 Querying the Mapping Between Ethernet Adapters..................................................................................................94
4.3.2 Querying the Configuration of the OMU Ethernet Adapters....................................................................................95
4.3.3 Querying Occupied OMU Ports................................................................................................................................97
4.3.4 Querying the Link Mode of the External OMU Network Adapters..........................................................................97
4.3.5 Checking the Version of the Operating System........................................................................................................99
4.3.6 Changing the Administrator Password of the Operating System..............................................................................99
4.3.7 Setting RAID 1 on OMU Hard Disks......................................................................................................................100
4.3.8 Maintaining the OMU Routinely.............................................................................................................................106
4.3.9 Managing the Operating Status of the OMU...........................................................................................................109
4.3.10 Managing OMU Applications...............................................................................................................................115
4.3.11 Backing Up and Restoring Data............................................................................................................................117
4.3.12 Using the omutool.................................................................................................................................................121
4.3.13 Adjusting OMU Slots............................................................................................................................................130
4.4 Appendix: OMU-Related Software............................................................................................................................132
4.4.1 psftp Software..........................................................................................................................................................132
4.4.2 PuTTY Software......................................................................................................................................................133
4.5 Appendix: OMU-Related Information Tables............................................................................................................135
4.5.1 Information Record Sheet of OMU Software Installation.......................................................................................135
4.5.2 Checklist for the OMU Software Factory Settings..................................................................................................137
4.5.3 OMU Directory Operation Rights List....................................................................................................................140
4.5.4 OMU Folder Size List.............................................................................................................................................141
4.5.5 List of Enabled Ports on the OMU..........................................................................................................................144
5 Scenario: Upgrading from the BSC6810 to the BSC6900....................................................147

5.1 Reinstalling Software Onsite......................................................................................................................................149
5.1.1 Reinstalling the Windows OS..................................................................................................................................149
5.1.2 Switching the OMU Operating System...................................................................................................................163
5.1.3 Optional: Installing OMU Applications..................................................................................................................177
5.2 OMU Operation and Maintenance After the Upgrade...............................................................................................180
5.2.1 Querying the Configuration of the OMU Ethernet Adapters..................................................................................180
5.2.2 Querying the OMU Operating Status......................................................................................................................182
5.2.3 Querying the Information About an OMU Board...................................................................................................182
5.2.4 Querying the Version of the Active/Standby OMU Workspaces............................................................................183
5.2.5 Querying the Status of Data Synchronization Between the Active and Standby OMUs........................................184
Issue 08 (2013-06-25) Huawei Proprietary and Confidential vii

BSC6900 UMTS
5.2.6 Querying Occupied OMU Ports..............................................................................................................................184

5.2.7 Checking the Data Consistency Between the Active OMU and the Standby OMU...............................................185
5.2.8 Changing the Administrator Password for the Operating System...........................................................................185
5.2.9 Forcibly Switching Over the Active and Standby OMUs.......................................................................................187
5.2.10 Setting RAID 1 on OMU Hard Disks....................................................................................................................188
5.2.11 Switching Over the Active/Standby OMU Workspaces.......................................................................................195
5.2.12 Checking the Version of the Operating System....................................................................................................196
5.2.13 Manually Synchronizing the Data of the Active and Standby OMUs...................................................................197
5.2.14 Stopping the Synchronization of the Data of the Active and Standby OMUs......................................................197
5.2.15 Renaming Local Area Connections on the OMU..................................................................................................198
5.2.16 Setting the Link Mode for External OMU Ethernet Adapters...............................................................................200
5.2.17 Setting the First Boot Device of the OMU to USB...............................................................................................204
5.2.18 Uninstalling the SQL Server 2000.........................................................................................................................212
5.2.19 Uploading Files to the OMU.................................................................................................................................213
5.2.20 Logging In to the OMU.........................................................................................................................................214
5.2.21 Logging Out of the OMU......................................................................................................................................215
5.2.22 Resetting the OMU................................................................................................................................................217
5.2.23 Maintaining the OMU Routinely...........................................................................................................................217
5.2.24 Managing OMU Applications...............................................................................................................................218
5.2.25 Backing Up and Restoring Data............................................................................................................................224
5.2.26 Using the omutool.................................................................................................................................................231
5.2.27 Adjusting OMU Slots............................................................................................................................................240
5.3 Appendix: Antivirus Software....................................................................................................................................242
5.4 Appendix: Installing the iPSI SEK SetWin Software................................................................................................243
5.4.1 Running the iPSI SEK SetWin Software.................................................................................................................243
5.4.2 Rolling Back Security Enhancement Policies During the Use of the SEK SetWin Software.................................248
5.5 Appendix: OMU-Related Information Tables............................................................................................................248
5.5.1 Record Sheet of OMU Software Installation Information.......................................................................................248
5.5.2 Checklist for Factory Settings of the OMU Software.............................................................................................250
5.5.3 List of Enabled Ports on the OMU..........................................................................................................................251
5.5.4 List of Disabled Ports on the OMU.........................................................................................................................252
6 Appendix: Security FAQ..........................................................................................................254

6.1 Disabling root user login with SSH............................................................................................................................255
6.2 Disabling OMU route forwarding..............................................................................................................................258
6.3 Enhancing Security of Time Synchronization with NTP...........................................................................................260
6.4 Configuring the Function of Recording OMU OS Accessing Information in Real Time..........................................261
6.5 Enabling Function of Checking OS File Integrity......................................................................................................262
Issue 08 (2013-06-25) Huawei Proprietary and Confidential viii

BSC6900 UMTS 1 Changes in the BSC6900 UMTS OMU Administration
OMU Administration Guide Guide
1 Changes in the BSC6900 UMTS OMU

Administration Guide
This document describes the changes in the BSC6900 UMTS OMU Administration Guide.
08 (2013-06-28)
This is the eighth commercial release of V900R014C00.
Compared with issue 07 (2013-04-15), this issue includes the following new topics:
l 6.3 Enhancing Security of Time Synchronization with NTP
Compared with issue 07 (2013-04-15), this issue incorporates the following changes:
Content Description
Changing Users' Passwords The password complicacy is modified.
Preparing a USB Storage Device Add note: After the OMU operating system
is installed, user security settings (including
user passwords and security policies) are
restored to the factory settings.
Compared with issue 07 (2013-04-15), this issue does not exclude any topics.
07 (2013-04-15)
This is the seventh commercial release of V900R014C00.
l 4.3.4 Querying the Link Mode of the External OMU Network Adapters
Issue 08 (2013-06-25) Huawei Proprietary and Confidential 1

Content Description
Restoring System Data Described different scenarios where MML

commands and backup restoration tools are
Restoring System Data used to restore system data.
Installing the OMU Operating System Updated the status of indicators during the
Using a USB Flash Drive operating system installation, operating
system restoration, and operating system and
OMU applications installation.
4.5.4 OMU Folder Size List The OMU folder size list is updated.
06 (2013-03-25)
This is the sixth commercial release of V900R014C00.
Compared with issue 05 (2012-12-31), this issue does not exclude any new topics.
Content Description
Logging In to the OMU Added the description: It is recommended

that you change the root user password upon
your first login and change the password
every three months.
4.5.2 Checklist for the OMU Software Changed the default root user passwords of
Factory Settings the active and standby OMUs to
Installing the OMU Operating System osadmin@123.
Using a USB Flash Drive
Preparing a USB Storage Device Kingston and Sandisk USB storage devices
are added.
5.1.2 Switching the OMU Operating
System
Logging In to the OMU Description about login to the OMU by the

4.5.2 Checklist for the OMU Software lgnusr user is added.
Factory Settings
4.4.1 psftp Software
4.4.2 PuTTY Software
Uploading the OMU Application
Installation Package to the OMU
6.1 Disabling root user login with SSH

05 (2012-12-31)
This is the fifth commercial release of V900R014C00.
l 4.5.4 OMU Folder Size List
Content Description
3.1 OMU Ethernet Adapter Configuration Notes on the bond1 and bond1:0 of the OMUa
board are added.
l Scenario: Creating a BSC6900 NE Changed the chapter name to Changing the

Changing the Computer Name Computer Name.
l Scenario: Upgrade from the BSC6810 to
the BSC6900
Changing the Computer Name
Checking the Installation Directory of The file folder version_a/ftp/trace is

OMU Applications deleted.
04 (2012-11-07)
This is the fourth commercial release of V900R014C00.
l 4.2.2 Optional: Installing the Operating System and OMU Applications
Content Description
l 4 Scenario: Deploying a BSC6900 Scenario descriptions are added.

l 5 Scenario: Upgrading from the
BSC6810 to the BSC6900
5.1.2 Switching the OMU Operating Procedures of configuring the ACL for the
System PortTrunking service on the M2000 are
added.
3.2 OMU IP Address Plan The descriptions about the restriction on IP

addresses of the backup channel between the
active and standby OMUs on OMUc board is
modified.

Content Description
4.2.3 Optional: Installing the OMU Background information is added.

Applications
Logging In to the OMU Notes on the password of the user root are
added.
4.3.6 Changing the Administrator Notes on admin password complexity are

Password of the Operating System added.
Creating the Installation Source of the Notes on obtaining the SetWin software are
SetWin Software and OS Patches added.
5.2.1 Querying the Configuration of the The chapter title is changed to Querying the
OMU Ethernet Adapters Configuration of the OMU Ethernet
Adapters.
Installing the OMU Operating System The status of indicators on the OMU during
Using a USB Flash Drive installation is modified.
The description that the password for logging
in to the operating system automatically
changes to the default value after the
operating system is recovered using a USB
flash drive is added.
l Scenario: Creating a BSC6900 NE Descriptions on starting and stoping the omud

Changing IP Addresses of OMU process are added into the Context.
Ethernet Adapters and Their Subnet
Masks
the BSC6900
Changing IP Addresses of OMU
Ethernet Adapters and Their Subnet
Masks
03 (2012-08-30)
This is the third commercial release of V900R014C00.
Compared with issue 02 (2012-06-30), this issue does not exclude any new topics.
Content Description
4 Scenario: Deploying a BSC6900 The procedure descriptions for the scenario

of new deployment are added.

Content Description
6.4 Configuring the Function of Recording The procedures are modified.

OMU OS Accessing Information in Real
Time
l Scenario: Creating a BSC6900 NE The procedure descriptions for restoring the

Restoring System Data system data by running MML commands are
added.
the BSC6900
Restoring System Data
5.1.2 Switching the OMU Operating The description about how to start the
System Dopra_Linux_U tool by using EMS Proxy
IP Address is added.
02 (2012-06-30)
This is the second commercial release of V900R014C00.
l 4.5.3 OMU Directory Operation Rights List
l 6.4 Configuring the Function of Recording OMU OS Accessing Information in Real
Time
l 6.5 Enabling Function of Checking OS File Integrity
Content Description
Checking the Installation Directory of Notes about some OMU application

OMU Applications directories are changed.
Preparing a USB Storage Device Descriptions of data encryption are added in

Context.
Switching Over the Active/Standby OMU The scenarios of OMU active and standby
Workspaces workspace switch is changed.
l Logging In to the OMU The initial password of the OMU OS is

l 4.5.2 Checklist for the OMU Software changed to mbsc@com.
Factory Settings

Content Description
l Scenario: Upgrade from the BSC6000 to Added the description that you need to
the BSC6900 contact Huawei engineers regarding
4.2.1 Preparations for Installing information or tools that you need to
Software Onsite download from Software Center.
the BSC6900
System
Creating the Installation Source of
the SetWin Software and OS
Patches
Preparations for Reinstalling the
OMU Operating System
01 (2012-04-26)
This is the first commercial release of V900R014C00.
Compared with issue Draft B (2012-03-26), this issue includes the following new topics:
l 2.4.1 OMU Software Monitoring

l Scenario: Creating a BSC6900 NE
4.3.3 Querying Occupied OMU Ports
l Scenario: Upgrade from the BSC6810 to the BSC6900
Compared with issue Draft B (2012-03-26), this issue incorporates the following changes:
Content Description
2.4 OMU Software The OMU architecture description is added.
2.4.3 OMU Service Monitoring Entities The OMU monitoring mechanism is changed
from two-level to three-level.
3.7 Switchover Between Active and A condition triggering the self-healing

Standby OMUs switchover is added.
Transferring OMU Files to a Local PC The initial password for the FtpUsr user is
changed.
6.1 Disabling root user login with SSH Explanations for password change policy are
added.
5.5.3 List of Enabled Ports on the OMU The port 3306 is deleted.

Content Description
5.1.2 Switching the OMU Operating The Add NE interface is modified and the
System explanation for the Admin Password
parameter is added.
l Scenario: Creating a BSC6900 NE The restrictions on changing the active and

Changing the Computer Name standby OMU names are added in the
background information.
the BSC6900
l Scenario: Creating a BSC6900 NE Explanations for password change policy are

4.3.6 Changing the Administrator added.
Password of the Operating System
Changing Users' Passwords
Logging In to the OMU
the BSC6900
5.2.8 Changing the Administrator
Password for the Operating System
Compared with issue Draft B (2012-03-26), this issue does not exclude any topics.
Draft B (2012-03-26)
This is the Draft B release of V900R014C00.
Compared with issue Draft A (2012-02-15), this issue does not include any new topics.
Compared with issue Draft A (2012-02-15), this issue incorporates the following changes:
Content Description
4.3.7 Setting RAID 1 on OMU Hard Disks Descriptions about using the external
keyboard and monitor to configure the OMU
hard disk RAID 1 are added.
6.1 Disabling root user login with SSH The method of modifying a non-root user's
password is added.
5.1.2 Switching the OMU Operating Description about selecting secure

System transmission type is modified.

Content Description
l Scenario: Creating a BSC6900 NE The method of modifying passwords of root,

Changing Users' Passwords db_user and FtpUsr are added.
the BSC6900
l Scenario: Creating a BSC6900 NE Descriptions about checking whether the

Installing the OMU Applications in the OMU application is pre-installed are added.
Active Workspace
the BSC6900
5.1.3 Optional: Installing OMU
Applications
l Scenario: Creating a BSC6900 NE Notes on ports 6099, 8099, 16002 and 18002
4.5.5 List of Enabled Ports on the OMU are modified.
the BSC6900
5.5.3 List of Enabled Ports on the OMU
Compared with issue Draft A (2012-02-15), this issue does not exclude any topics.
Draft A (2012-02-15)
This is the Draft A release of V900R014C00.
Compared with issue 05 (2012-01-05) of V900R013C00, this issue includes the following new
topics:
l 5.2.18 Uninstalling the SQL Server 2000
Compared with issue 05 (2012-01-05) of V900R013C00, this issue incorporates the following
changes:
Content Description
3.2 OMU IP Address Plan The description of restrictions on setting the

internal fixed IP address, internal virtual IP
address, and IP address of the backup channel
between the active and standby OMUs have
been modified.
3.7 Switchover Between Active and A condition for triggering the OMU self-
Standby OMUs healing switchover has been added.
4.1.1 Setting the Link Mode of the External The method for setting the mode of the OMU
OMU Ethernet Adapter external network Ethernet adapter has been
modified.

Content Description
Preparing a USB Storage Device The login interface of the USB storage device
has been modified. And the relevant interface
descriptions have been added.
4.3.2 Querying the Configuration of the The method for querying the Ethernet adapter
OMU Ethernet Adapters configuration by using the omutool has been
added.
l Scenario: Upgrade from the BSC6810 to The procedure for switching the OMU
the BSC6900 operating system to Dopra Linux is modified.
System
l Scenario: Creating a BSC6900 NE The operations of changing the password of

Changing Users' Passwords the db_user has been added.
the BSC6900
Compared with issue 05 (2012-01-05) of V900R013C00, this issue does not exclude any topics.

BSC6900 UMTS
OMU Administration Guide 2 Introduction to OMU
2 Introduction to OMU
About This Chapter
The physical entity of the OMU is the OMUa/OMUc board. The OMU collects and processes
information about operation and maintenance (OM), and reports this information to the OM
terminal: either the LMT or M2000.
2.1 Position of the OMU in the BSC6900

This section describes the components of the BSC6900 operation and maintenance (OM)
subsystem and the position of the OMU in the OM subsystem.
2.2 OMUa Board
OMUa is short for Operation and Maintenance Unit REV: a.
2.3 OMUc Board
OMUc is short for Operation and Maintenance Unit REV: c.
2.4 OMU Software
The OMU software, running on the OMUa board and OMUc board, is responsible for the
operation and maintenance of the BSC6900.
2.5 OMU Working Mode
The OMU works in independent or active/standby mode.
2.6 OMU OM Methods
This section describes how to perform operation and maintenance (OM) on the OMU in different
scenarios.
2.7 OMU Safety Information
This section describes the safety information related to the OMU operation.

BSC6900 UMTS
2.1 Position of the OMU in the BSC6900

This section describes the components of the BSC6900 operation and maintenance (OM)
subsystem and the position of the OMU in the OM subsystem.
The BSC6900 OM subsystem is composed of the OM terminal (LMT/M2000), OMU, SCU, and
OM modules on other boards. In the BSC6900 OM subsystem, the LMT/M2000 communicates
with BSC6900 boards through the OMU.
Figure 2-1 shows the position of the OMU in the BSC6900 OM subsystem.
Figure 2-1 Position of the OMU in the BSC6900 OM Subsystem
As shown in Figure 2-1, the external network is the logical network between the OMU and the
LMT/M2000, and the internal network is the logical network between the OMU and the
BSC6900.
2.2 OMUa Board

OMUa is short for Operation and Maintenance Unit REV: a.
Two OMUa boards must be configured in the BSC6900. One OMUa board occupies two slots.
The board can be installed in slots 0 to 3, slots 20 to 23, or slots 24 to 27 in the MPS at the bottom
of the MPR. It is recommended that the OMUa board be installed in slots 20 to 23 for inventory
sites and in slots 24 to 27 for new sites.

BSC6900 UMTS
NOTE
l This document describes the installation of other boards based on the OMUa boards being installed in slots
24 to 27.
l Different types of OMU boards can be configured in active and standby slots only for a short period. When
an OMUc board is used to replace an OMUa board, the OMUc board and the OMUa board can be inserted
into the slots and co-exist for a short period (less than one hour), so that data can be synchronized from the
OMUa board to the OMUc board.
l Different types of OMU boards cannot be configured in active and standby slots for a long period. In
scenarios of long-term operation, the active and standby OMU boards must be of the same type. For example,
both active and standby OMU boards must be OMUa boards or OMUc boards.
2.2.1 Functions of the OMUa Board

The OMUa board connects the LMT/M2000 and the other boards in the BSC6900.
The functions of the OMUa board are as follows:
l Performs the configuration management, performance management, fault management,
security management, and loading management functions for the system
l Enables LMT or M2000 users to perform operation and maintenance on the BSC6900
system to control the communication between the LMT or M2000 and the SCUa board of
the BSC6900
2.2.2 Panel of the OMUa Board

There are LEDs, ports, and buttons on the panel of the OMUa board. In addition, there are hard
disks installed on the OMUa board.
Figure 2-2 shows the panel of the OMUa board.

BSC6900 UMTS
Figure 2-2 Panel of the OMUa board
(1) Captive screw (2) Ejector lever (3) Self-locking latch (4) RUN LED
(5) ALM LED (6) ACT LED (7) RESET button (8) SHUTDOWN button
(9) USB port (10) ETH0 Ethernet port (11) ETH1 Ethernet port (12) ETH2 Ethernet port
(13) COM port (14) VGA port (15) HD LEDs (16) OFFLINE LED
(17) Hard disks (18) Screws for securing the hard disk
NOTE
l To power off the OMUa board, simultaneously pivot the top and bottom ejector levers away from the
front panel of the OMUa board. After the OFFLINE LED is on, turn off the power switch.
l The SHUTDOWN button is used only for powering off the board in an emergency.
l The RESET button is used to reset the system. It works the same way as the reset button on a PC.
l Pressing the SHUTDOWN or RESET button has the risk of scratching the surface of OMUa hard disks.
Avoid pressing these two buttons whenever possible.

BSC6900 UMTS
2.2.3 Ports on the OMUa Board

There are four USB ports, three GE ports, one serial port COM0-ALM/COM1-BMC, and one
VGA port on the OMUa board.
Table 2-1 describes the ports on the OMUa board.
Table 2-1 Ports on the OMUa board
Port Function Connector Type
USB0-1 and USB2-3 Operators can use the USB ports USB
only after logging in to the
operating system (OS) running on
the board. The ports does not
require a signal cable or connection
to other devices when the system
runs properly. Therefore,
equipment security is not affected.
ETH0 to ETH1 The hardware ports are used for the RJ45
communication between the OMU
and the LMT/M2000.
ETH2 The port does not require a signal RJ45

cable or connection to other
devices when the system runs
properly. Therefore, equipment
security is not affected.
COM0-ALM/COM1-BMC The port does not require a signal DB9

cable or connection to other
devices when the system runs
properly. Therefore, equipment
security is not affected.
VGA Video port DB15
2.2.4 LEDs on the OMUa Board

There are five types of LEDs on the OMUa board: RUN, ALM, ACT, OFFLINE, and HD.
Table 2-2 describes the LEDs on the OMUa board.
Table 2-2 LEDs on the OMUa board
LED Color Status Description
RUN Green ON for 1s and OFF for 1s The board is functional.
ON for 0.125s and OFF The board is being started.

for 0.125s

BSC6900 UMTS
ON There is power supply, but the board

is faulty.
OFF There is no power supply, or the

board is faulty.
ALM Red OFF There is no alarm.
ON or blinking There is a fault alarm.
ACT Green ON The board is in active mode.
OFF The board is in standby mode, or the

board is disconnected.
OFFLINE Blue ON The board can be removed.
OFF The board cannot be removed.
ON for 0.125s and OFF The board is being switched over to

for 0.125s the other working mode.
HD Green OFF There is no read or write operation

on the hard disk.
Blinking The hard disk is being read or

written to.
2.2.5 Technical Specifications of the OMUa Board

This section describes the hardware configuration indexes and performance counters of the
OMUa board, including dimensions, power supply, number of CPUs, power consumption,
weight, hard disk capacity, memory capacity, working temperature, and working humidity.
Hardware Configuration Indexes

Table 2-3 lists the hardware configuration indexes of the OMUa board.
Table 2-3 Hardware configuration indexes
Item Index of the OMUa board
Dimensions 248 mm x 64.6 mm x 395.4 mm
Power supply Two -48 V DC working in active/standby mode. The

backplane of the subrack is responsible for the power supply.
Number of CPUs 4
Power consumption 120 W
Weight 4.0 kg

BSC6900 UMTS
Item Index of the OMUa board
Hard disk capacity 73 GB or above x 2 (RAID 1)*
Memory capacity 2G
Temperature required when 5C to 40C

working for an extended
period of time

working for a short period of
time
Relative humidity required 5% to 85%

when working for an
extended period of time

when working for a short
period of time
*The hard disk capacity can be 73 GB, 146 GB, or 300 GB. Hard disks will be delivered according
to the production plan of our hard disk providers.
Performance Counters
Table 2-4 lists the performance counters of the OMUa board.
Table 2-4 Performance counters
Counter Index of the OMUa Board
Number of recorded The maximum number of recorded alarms is 150,000.

alarms
Time when the standby The standby OMU synchronizes its data with that of the active
OMU data is OMU board every second.
synchronized with the
active OMU data
Duration of the Five minutes. The time needed for the synchronization varies
synchronization between according to the size and quantity of the files to be synchronized.
the active OMU files and
standby OMU files
Duration of the Refers to the time from the request for OMU switchover being
switchover between the accepted to the switchover being finished. The switchover
active and standby OMUs finishes in four minutes.
Duration of the OMU Duration of the OMU restart caused by an OMU fault. This
restart duration lasts for about three minutes.

BSC6900 UMTS
The OMUa board contains mechanical hard disk. Adverse environments, such as high
temperature and high altitude, shorten board lifespan.
To extend the lifespan of the OMUa board, protect it from vibration, shock, and abnormal
shutdowns.
2.3 OMUc Board

OMUc is short for Operation and Maintenance Unit REV: c.
Two boards must be configured in the BSC6900. The boards can be installed in slots 0 to 3, slots
20 to 23, or slots 24 to 27 in the MPS at the bottom of the MPR. Slots 24 to 25 are recommended.
NOTE
l This document describes the installation of other boards on the basis that the OMUc boards are installed in
slots 24 and 25.
l Different types of OMU boards can be configured in active and standby slots only for a short period. When
an OMUc board is used to replace an OMUa board, the OMUc board and the OMUa board can be inserted
into the slots and co-exist for a short period (less than one hour), so that data can be synchronized from the
OMUa board to the OMUc board.
l Different types of OMU boards cannot be configured in active and standby slots for a long period. In
scenarios of long-term operation, the active and standby OMU boards must be of the same type. For example,
both active and standby OMU boards must be OMUa boards or OMUc boards.
2.3.1 Functions of the OMUc Board

The OMUc board works as a bridge for the communication between the Local Maintenance
Terminal (LMT) and the other boards in the BSC6900.
The OMUc board performs the following functions:
l Performs the configuration management, performance management, fault management,
security management, and loading management functions for the system
l Enables LMT or M2000 users to perform operation and maintenance on the BSC6900
system to control the communication between the LMT or M2000 and the SCUb board of
the BSC6900
2.3.2 Panel of the OMUc Board

There are LEDs, ports, and buttons on the panel of the OMUc board.
Figure 2-3 shows the panel of the OMUc board.

BSC6900 UMTS
Figure 2-3 Panel of the OMUc board
(1) Captive screw (2) Ejector lever (3) Self-locking latch (4) RUN LED
(5) ALM LED (6) ACT LED (7) POWER Button (8) HDD LED
(9) OFL LED (10) COM port (11) ETH0 Ethernet port (12) ETH1 Ethernet port
(13) VGA port (14) USB port (15) ETH2 Ethernet port
NOTE
To power off the OMUc board, you need to simultaneously pivot the top and bottom ejector levers away
from the front panel of the OMUc board. After the OFL (OFFLINE) LED is on, turn off the power switch.

BSC6900 UMTS
2.3.3 Ports on the OMUc Board

There are four USB ports, three GE ports, one serial port COM0, and one VGA port on the
OMUc board.
Table 2-5 describes the ports on the OMUc board.
Table 2-5 Ports on the OMUc board
Port Function Connector Type
USB0-1 and USB2-3 Operators can use the USB ports USB
only after logging in to the
operating system (OS) running on
the board. The hardware ports need
no cables or connecting to other
equipment and therefore do not
affect the equipment safety.
ETH0 to ETH1 The hardware ports are used for the RJ45
communication between the OMU
and the LMT/M2000.
ETH2 The hardware ports need no cables RJ45

or connecting to other equipment
and therefore do not affect the
equipment safety.
COM The hardware ports need no cables DB9

or connecting to other equipment
and therefore do not affect the
equipment safety.
VGA Port for the video. DB15
2.3.4 LEDs on the OMUc Board

There are five types of LEDs on the OMUc board: RUN, ALM, ACT, OFL, and HDD.
Table 2-6 describes the LEDs on the OMUc board.
Table 2-6 LEDs on the OMUc board
RUN Green ON for 1s and OFF for 1s The board is functional.
ON for 0.125s and OFF The board is being started.

for 0.125s
ON There is power supply, but the board

is faulty.

BSC6900 UMTS
OFF There is no power supply, or the

board is faulty.
ALM Red OFF There is no alarm.
ON or blinking There is a fault alarm.
ACT Green ON The board is in active mode.
OFF The board is in standby mode, or the

board is disconnected.
OFL Blue ON The board can be removed.
OFF The board cannot be removed.
ON for 0.125s and OFF The board is being switched over to

for 0.125s the other working mode.
HDD Green OFF There is no read or write operation

on the hard disk.
Blinking The hard disk is being read or

written to.
2.3.5 Technical Specifications of the OMUc Board

The technical specifications of the OMUc board include hardware configuration indexes and
performance counters. The hardware configuration indexes refer to the dimensions, power
supply, number of CPUs, power consumption, weight, operating temperature, and relative
humidity.
Hardware Configuration Indexes

Table 2-7 lists the hardware configuration indexes of the OMUc board.
Table 2-7 Hardware configuration indexes of the OMUc board
Item Index of the OMUc board
Dimensions 248 mm x 32.3mm x 395.4 mm
Power supply Two -48 V DC working in active/standby mode. The

backplane of the subrack is responsible for the power supply.
Number of CPUs 6
Power consumption 90 W
Weight 2.5 kg
Hard disk capacity 500 GB

BSC6900 UMTS
Memory capacity 8 GB

working for an extended
period of time

working for a short period of
time

when working for an
extended period of time

when working for a short
period of time
Performance Counters
Table 2-8 describes the performance counters of the OMUc board.
Table 2-8 Performance counters of the OMUc board
Number of recorded The maximum number of recorded alarms is 150,000.

alarms
Time when the standby The standby OMU synchronizes its data with that of the active
OMU data is OMU board every second.
synchronized with the
active OMU data
Duration of the Five minutes. The time needed for the synchronization varies
synchronization between according to the size and quantity of the files to be synchronized.
the active OMU files and
standby OMU files
Duration of the Refers to the time from the request for OMU switchover being
switchover between the accepted to the switchover being finished. The switchover
active and standby OMUs finishes in four minutes.
Duration of the OMU Duration of the OMU restart caused by an OMU fault. This
restart duration lasts for about three minutes.
The OMUc board contains a mechanical hard disk. Due to the short lifespan of the mechanical
hard disk, the lifespan of the OMUc board is about 5 years. Adverse environments, such as high
temperature and high altitude, shorten board lifespan.

BSC6900 UMTS
To ensure the lifespan of the OMUc board, the OMUc board must be protected against vibration,
shock and abnormal shutdown.
2.4 OMU Software

The OMU software, running on the OMUa board and OMUc board, is responsible for the
operation and maintenance of the BSC6900.
The OMU software consists of the operating system and OMU applications, as shown in Figure
2-4.
Figure 2-4 OMU structure
l OMU operating system

The OMU operating system, installed on the boards, can be the Dopra Linux, SUSE Linux,
or Windows Server 2003.
l OMU Application Software
The OMU application software runs on the bottom-level operating system and provides
various service processes.
2.4.1 OMU Software Monitoring

The OMU hardware is monitoring its software in real time to avoid suspension of OMU
applications.
Figure 2-5 shows how OMU hardware monitors OMU software.

BSC6900 UMTS
Figure 2-5 Monitoring of the OMU hardware on its software
The omud process periodically clears the watchdog timer. If the omud process is abnormal and
causes the watchdog timer to overflow, the OMU will be reset automatically.
2.4.2 OMU Application Structure

The OMU applications used for operation and maintenance consist of multi-level service
monitoring entities and service processes.
Figure 2-6 shows the structure of the OMU applications.

BSC6900 UMTS
Figure 2-6 OMU Application Structure
NOTE
The arrows shown in Figure 2-6 indicate communication between modules.
For details about the OMU service processes, see 2.4.4 OMU Service Processes. For details
about the service monitoring entities, see 2.4.3 OMU Service Monitoring Entities.
2.4.3 OMU Service Monitoring Entities

The OMU applications perform monitoring at three levels: Level 1 is the hardware-level
monitoring in which the watchdog monitors the omud. Level 2 is the system-level monitoring
in which the omud monitors the monitor. Level 3 is the application-level monitoring in which
the monitor monitors service processes. When a service process, the monitor, or the omud is
faulty, three-level monitoring mechanism ensures that the faulty service process, monitor, or
omud can be restarted.

BSC6900 UMTS
Watchdog
A watchdog is a timer used to monitor the omud. Once the omud is abnormal, the watchdog
timer will enable the OMU to be reset.
omud
As a service entity, the omud is registered in the operating system and automatically starts when
the operating system starts. The monitor is started when the omud starts and the omud monitors
the monitor.
Monitor
The monitor monitors the service processes in real time.
2.4.4 OMU Service Processes

The OMU is managed by OMU services processes.
The OMU service processes are as follows: communication module (ems_gate), authentication
module (authority), network management agent module (ems_agent), configuration module
(configure), maintenance module (maintain), alarm module (alarm), performance module (stat),
software management module (software), OMU management module (omu_manager), time
server module (sntp), FTP module (ftp_server), exchange module (host_gate), fault diagnosis
module (cfa), OMU log management module (debug_log), LMT module (weblmt), and data
exportation module.
Communication Module (ems_gate)

The communication module performs the following functions:
Receives messages from the Element Management System (EMS) or Local Maintenance
Terminal (LMT), converts the messages into frames for internal communication in the OMU,
and then sends the messages to the authentication module. Receives messages from the OMU
modules, interprets the messages, and then sends the messages to the EMS or LMT.
Receives, interprets, and sends messages between the VNP and maintenance module.
Authentication Module (authority)

The authentication module performs functions such as authority management, log management,
and command resolution.
Network Management Agent Module (ems_agent)

The network management agent module performs the following functions:
l Batch command processing
l Scheduled task management
Configuration Module (configure)

The configuration module performs the functions of data configuration and management for the
BSC6900 host, such as configuring data effective and ineffective modes, formatting the data
files loaded by the host, and checking data consistency.

BSC6900 UMTS
Maintenance Module (maintain)

The maintenance module enables the OMU to query the operating status of objects such as the
BSC6900 host hardware, physical/logical links, and channels. It also enables the BAM to test
and maintain objects.
Alarm Module (alarm)

The alarm module handles alarms. It controls the output mode and classification of alarms, and
shields alarms.
Performance Module (stat)

The performance module collects, stores, and computes the performance measurement data of
the host, and then reports the data to the M2000.
Software Management Module (software)

The software management module performs functions such as BOOTP service for the OMUa
board, OMU software management, OMU active/standby workspace management, file
synchronization between the active OMU and the standby OMU, and version upgrade
management.
OMU Management Module (omu_manager)

The OMU management module monitors the OMU hardware and software.
Time Server Module (sntp)

The time server module performs the following functions:
l The time server provides time synchronization for BSC6900 boards and the base station.
l The time client synchronizes with the upper-level time server and provides the reference
time.
FTP Module (ftp_server)

The FTP module serves as an FTP server and provides the file transfer function for the host
boards, LMT, and EMS.
Exchange Module (host_gate)

The exchange module enables the communication between the OMU processes and the host.
Fault Diagnosis Module (cfa)

The fault diagnosis module collects end-to-end link fault information, periodically diagnoses
faulty nodes, and performs self-healing.
OMU Log Management Module (debug_log)

The OMU log management module records and regularly cleans up OMU logs.

BSC6900 UMTS
LMT Module (weblmt)

The LMT module performs message tracing, performance monitoring, and device maintenance.
It also provides an interface for issuing MML commands.
Data Exportation Module (cfg_mirror)

The data exportation module exports the configuration data.
OMU service processes are logically independent of one another. When one process fails, other
processes continue to run properly. The OMU can detect a process that stops abnormally and
restart it quickly.
2.5 OMU Working Mode

The OMU works in independent or active/standby mode.
Independent Mode
When the BSC6900 is configured with one OMUa/OMUc board, the OMU works in independent
mode.
In this mode, if the OMU is faulty, operation and maintenance (OM) cannot be performed on
the BSC6900. This reduces system reliability.
Active/Standby Mode
When the BSC6900 is configured with two OMUa/OMUc boards, the OMU works in active/
standby mode.
In this mode, the OMUa/OMUc board working in active mode is called the active OMU board,
and the OMUa/OMUc board working in standby mode is called the standby OMU board. The
active and standby OMU boards must be of the same type. Mixed installation of the OMUc
board and the OMUa board is prohibited.
When the BSC6900 is configured in active/standby OMU mode, the OMU can operate properly
with high reliability. Specifically, if a hardware or software fault occurs on the active OMU, the
standby OMU is automatically switched over to the active state and provides services.
NOTE
l Check the OMU working mode before installing the OMU applications.
l After the OMU applications are installed, run the MML command DSP OMU and check the value for the
Operational state parameter in the command output to check the OMU working mode.
2.6 OMU OM Methods

This section describes how to perform operation and maintenance (OM) on the OMU in different
scenarios.
Scenario 1: Installing OMU Applications Before Onsite Commissioning

After installing the BSC6900 hardware, install OMU applications before commissioning the
OMU.

BSC6900 UMTS
In this scenario, log in to the OMU and install the OMU applications. For details, see 4.1
Installing the OMU Applications in Field Commissioning.
Scenario 2: Reinstalling the OMU Operating System Onsite

If the operating system crashes onsite, reinstall the OMU operating system and OMU
applications, and reconfigure the OMU.
In this scenario, use the USB storage device to reinstall the OMU operating system. For details,
see 4.2 Reinstalling Software Onsite.
Scenario 3: Operating OMU Applications and Tools

In this scenario, manage the OMU applications and use the omu_backup_linker and omutool.
In this scenario, log in to the OMU and perform OM on the OMU. For details, see 4.3 Operating
and Maintaining the OMU.
Scenario 4: Performing Routine OM on the OMU

In this scenario, periodically check the OMU hard disk space, clean up the OMU hard disk, and
perform routine OM on the OMU.
In this scenario:
l If you want to periodically check the OMU hard disk space and clean up the OMU hard
disk, log in to the OMU and perform the operations by referring to 4.3.8 Maintaining the
OMU Routinely.
l If you perform routine OM on the OMU, log in to the LMT to connect to the OMU, and
then run MML commands to perform the operations by referring to BSC6900 UMTS LMT
User Guide.
Scenario 5: Upgrading BSC6810 to BSC6900

The operating system of the BSC6810 is Windows Server 2003, and the operating system of the
BSC6900 is Dopra Linux. After the BSC6810 is upgraded to the BSC6900, Windows Server
2003 can be retained or switched to Dopra Linux.
In this scenario:
l Install the OMU operating system and OMU applications by referring to 5.1 Reinstalling
Software Onsite.
l Perform routine OM on the OMU by referring to 5.2 OMU Operation and Maintenance
After the Upgrade.
2.7 OMU Safety Information

This section describes the safety information related to the OMU operation.
l To ensure proper operation of the OMU, do not create or delete directories, change directory
attributes, backup files, modify system files, change system file attributes, disable Ethernet
adapters, modify configuration files for Ethernet adapters, or configure routes.
l To ensure proper operation of the OMU, install and run only the operating system software
(including necessary drivers and components) and OMU applications on the OMU.

BSC6900 UMTS
l The operation information and faults of the BSC6900 are recorded on the OMU. Therefore,
to timely and accurately locate and rectify BSC6900 faults, do not delete any log file from
the OMU.

BSC6900 UMTS
OMU Administration Guide 3 Working Principles of the OMU
3 Working Principles of the OMU
About This Chapter
This section has the following topics:
3.1 OMU Ethernet Adapter Configuration

This section describes the configuration of OMU Ethernet adapters.
3.2 OMU IP Address Plan
The OMU Ethernet adapters must follow the IP address planning principles to meet the
communication requirements of the operation and maintenance (O&M) network.
3.3 OMU Networking Principle
The internal Ethernet adapters of the OMU are connected to the SCUs in the MPS, and the
external Ethernet adapters of the OMU are connected to the OM terminals. In this way, the OMU
fulfills the communication between the BSC6900 and the OM terminals.
3.4 Active/Standby Workspaces of the OMU
The active/standby workspaces of the OMU are used for the upgrade and rollback of the
BSC6900 versions, therefore enabling quick switching between versions.
3.5 Heartbeat Detection on Active and Standby OMUs
In active/standby OMU mode, heartbeat detection is performed on active and standby OMUs to
check whether the active and standby OMUs are working properly.
3.6 Synchronization Between Active and Standby OMUs
In dual-OMU mode, the synchronization between the active OMU and the standby OMU
consists of data synchronization, file synchronization, and time synchronization.
3.7 Switchover Between Active and Standby OMUs
For OMUs working in active/standby mode, there are four types of switchover: manual
switchover, fault-triggered switchover, failover, and self-healing switchover.

BSC6900 UMTS
3.1 OMU Ethernet Adapter Configuration

This section describes the configuration of OMU Ethernet adapters.
Configuration of Ethernet Adapters on an OMUa Board

The six Ethernet adapters on an OMUa board are:
l ETH0 and ETH1: These two Ethernet adapters are bound as an external Ethernet adapter
team, that is, bond1/bond1:0. This Ethernet adapter team is used for communication in the
external network. That is, the communication between the OMU and the LMT/M2000.
l ETH2: This Ethernet adapter is used to commission the OMU. It is connected to a portable
PC, if required. This Ethernet adapter is also called bond2.
l ETH3-UPDATE: This is an backup Ethernet adapter used for the dedicated backup channel
between the active and standby OMUs when the BSC6900 is configured with two OMUa
boards. This backup Ethernet adapter is also called bond3.
l ETH4-SCU7 and ETH5-SCU6: The two Ethernet adapters are bound as an internal Ethernet
adapter team, that is, bond0 (vlan1/vlan1:0). This Ethernet adapter team is used for
communication in the internal network. That is, the communication between the OMU and
BSC6900 host boards.
Figure 3-1 shows the binding relationship between Ethernet adapters on the OMUa board.
Figure 3-1 Binding relationship between Ethernet adapters on the OMUa board

BSC6900 UMTS
NOTE
l ETH0, ETH1, and ETH2 are connected to the external network through the Ethernet ports on the panel
of the OMUa board. ETH4-SCU7, ETH5-SCU6, and ETH3-UPDATE are connected to the backplane
of the MPS and invisible on the panel of the OMUa board.
l Either bond1 or bond1:0 is reserved for the fixed external IP address, and the other is reserved for the
virtual external IP address.
l When no external fixed IP address is configured, bond1 corresponds to the external virtual IP
address, but bond1:0 does not exist.
l When an external fixed IP address is configured, bond1 corresponds to the external fixed IP address,
and bond1:0 corresponds to the external virtual IP address.
l ETH4-SCU7 and ETH5-SCU6 are bound as an internal Ethernet adapter team, that is, bond0. To enable
communication between the OMU and the SCU, a VLAN whose ID is 1 needs to be established on
bond0. vlan1 and vlan1:0 are used for the fixed internal IP address and the virtual internal IP address,
respectively.
Configuration of Ethernet Adapters on an OMUc Board

The seven Ethernet adapters on the OMUc board are described as follows:
l F_ETH0 and F_ETH1: These two Ethernet adapters are bound as an external Ethernet
adapter team, that is, bond1/bond1:0. This Ethernet adapter team is used for communication
in the external network. That is, the communication between the OMU and the LMT/
M2000.
l F_DBG: This Ethernet adapter team is used to commission the OMU. It is connected to a
portable PC, if required. This Ethernet adapter is also called bond2.
l B_UPDATE0: This backup Ethernet adapter is used for the dedicated backup channel
between the active and standby OMUs when the BSC6900 is configured with two OMUc
boards.
l B_UPDATE1: This backup Ethernet adapter between the OMUc board and the OMUa
board is used for the dedicated backup channel between the OMUc board and the OMUa
board when the BSC6900 is configured with one OMUc board and one OMUa board.
l B_ETH0 and B_ETH1: The two Ethernet adapters are bound as an internal Ethernet adapter
team, that is, bond0 (vlan1/vlan1:0). This Ethernet adapter team is used for the
communication in the internal network. That is, the communication between the OMU and
BSC6900 host boards.
Figure 3-2 shows the binding relationship between Ethernet adapters on the OMUc board.
Figure 3-2 Binding relationship between Ethernet adapters on the OMUc board

BSC6900 UMTS
NOTE
l F_ETH0, F_ETH1, and F_DBG are connected to the external network through the Ethernet ports on
the panel of the OMUc board. B_ETH0, B_ETH1, B_UPDATE0, and B_UPDATE1 are connected to
the backplane of the MPS, and you cannot see them on the panel of the OMUc board.
l Either bond1 or bond1:0 is reserved for the fixed external IP address, and the other is reserved for the
virtual external IP address.
l B_ETH0 and B_ETH1 are bound as an internal Ethernet adapter team, that is, bond0. To enable the
communication between the OMU and the SCU, a VLAN whose ID is 1 needs to be established on
bond0.vlan1 and vlan1:0 are used for the fixed internal IP address and the virtual internal IP address,
respectively.
3.2 OMU IP Address Plan

The OMU Ethernet adapters must follow the IP address planning principles to meet the
communication requirements of the operation and maintenance (O&M) network.
Definitions of OMU IP Addresses

The OMU IP addresses include fixed internal IP address, fixed external IP address, virtual
internal IP address, virtual external IP address, and commissioning IP address. If the
BSC6900 is configured with two OMUa or OMUc boards, the OMU IP addresses also include
the IP address of the backup channel between the active and standby OMUa or OMUc boards.
Table 3-1 provides definitions of different OMU IP addresses.
Table 3-1 Definitions of OMU IP addresses

IP Definition Function Correspo Correspo
Addre nding nding
ss Ethernet Ethernet
Adapters Adapters
on the on the
OMUa OMUc
Board Board
Fixed IP address for the Used for the l ETH0 l F_ET

external communication between communication l ETH1 H0
IP peripheral devices (for example, between peripheral l F_ET
address a PC) and the OMU. devices (for H1
The fixed external IP address is example, a PC) and
automatically configured on the the OMU.
OMU external Ethernet adapter A user can log in to
team when the OMU operating the LMT by using
system is being installed. the fixed external IP
address on a PC.

BSC6900 UMTS

Addre nding nding
Adapters Adapters
on the on the
OMUa OMUc
Board Board
Virtual IP address for the Used for the l ETH0 l F_ET

external communication between communication l ETH1 H0
IP peripheral devices (for example, between peripheral l F_ET
address LMT or M2000) and the OMU. devices (for H1
The virtual external IP address example, LMT or
is configured on the Ethernet M2000) and the
adapter team of the active OMU active OMU.
when the OMU applications are If active and standby
installed. It takes effect after the OMUs are switched
OMU applications are started. over when a
peripheral device
communicates with
the OMUs using the
virtual external IP
address, the
communication
between the
peripheral device
and the OMU will be
interrupted for a
while and then be
recovered. During
this process, the
virtual external IP
address of the
original standby
OMU becomes
effective, and the
virtual external IP
address of the
original active OMU
becomes ineffective.
A user can log in to
the LMT by using
the fixed external IP
address on a PC.

BSC6900 UMTS

Addre nding nding
Adapters Adapters
on the on the
OMUa OMUc
Board Board
Fixed IP address for the Used for the l ETH4- l B_ET

internal communication between the communication SCU7 H0
IP active and standby OMUs on the between the active l ETH5- l B_ET
address internal network segment and standby OMUs SCU6 H1
(network on which information in the internal
is exchanged by using the SCUa network segment.
or SCUb board). The fixed internal IP
The fixed internal IP address is address is not used
automatically configured on the for the
OMU internal Ethernet adapter communication
team when the OMU operating between the OMU
system is installed. and the BSC6900
host boards.
Virtual IP address for the Used for the l ETH4- l B_ET

internal communication between the communication SCU7 H0
IP active OMU and the BSC6900 between the active l ETH5- l B_ET
address host boards. OMU and the SCU6 H1
The virtual internal IP address is BSC6900 host
configured on the internal boards.
Ethernet adapter team of the The communication
active OMU. It takes effect after between the
the OMU applications are BSC6900 host
started. boards and the OMU
are not interrupted
even during the
switchover of the
active and standby
OMUs.

BSC6900 UMTS

Addre nding nding
Adapters Adapters
on the on the
OMUa OMUc
Board Board
IP IP address for the Used for the ETH3- l B_UP

address communication between the communication UPDATE DATE
of the active and standby OMUs on the between the active 0 (used
backup backup channel network and standby OMUs for the
channel segment (network on which on the backup comm
betwee information is exchanged using channel network unicati
n the an Ethernet cable). segment. on
active The IP address of the backup betwee
and channel between the active and n the
standby standby OMUs is automatically active
OMUs configured on the standby OMU and
Ethernet adapter when the OMU standb
operating system is being y
installed. OMUc
boards
)
l B_UP
DATE
1 (used
for the
comm
unicati
on
betwee
n the
OMUc
board
and the
OMUa
board)
Debugg IP address for operating and IP address used for ETH2 F_DBG
ing IP maintaining the OMU when a connecting to the
address PC is connected to the OMU
commissioning Ethernet port of commissioning
the OMU using an Ethernet Ethernet port.
cable at the local end. A user can perform
O&M on the OMU
by using the
commissioning IP
address through a PC
or by logging in to
the LMT.

BSC6900 UMTS
Definition of Onsite Network

The network connecting the OMU external Ethernet adapters and the LMT or M2000 is defined
as an external network or an onsite network. If the OMU external Ethernet adapters are connected
to the LMT or M2000 routers, then the network connecting the OMU external Ethernet adapters
and the first router (gateway) is defined as an onsite network. Figure 3-3 shows an onsite
network.
l The network between the OMU internal Ethernet adapters and host boards is defined as an
internal network. The OMU communicates with the base station through the host boards.
l The network between the OMU external Ethernet adapters and the LMT or M2000 is
defined as an external network. The OMU is connected to the LMT or M2000 either directly
or through multiple routers (gateways).
Figure 3-3 Onsite network
Consider the following principles when configuring IP addresses on site:
l When configuring a NodeB, ensure that none of the IP addresses (set by running the ADD
UNODEBIP command) that are used for O&M on the NodeB under the BSC6900 are
located in the same network segment as the virtual external IP addresses, fixed external IP
address, IP address of the backup channel between the active and standby OMU, or
commissioning IP address.
l Assume that IP routes are configured for the OMU by running the ADD OMUIPRT
command. If IP routes to the NodeB are configured, ensure that Route Address and
Destination Network Address are not located in the same network segment as the virtual
external IP address, fixed external IP address, IP address of the backup channel between
the active and standby OMUs, or commissioning IP address. If IP routes to the LMT/M2000
are configured, ensure that Forward Route Address and Destination Network
Address are not located in the same network segment as the virtual internal IP address,
fixed internal IP address, IP address of the backup channel between the active and standby
OMUs, or commissioning IP address.
IP Addresses to Be Changed on Site

IP addresses are configured before an OMU is delivered. For more information, see 4.5.2
Checklist for the OMU Software Factory Settings. The default IP addresses may fail to meet
the requirements of onsite network planning. Therefore, you are required to reconfigure some
of the OMU IP addresses.
Generally, the fixed and virtual external IP addresses need to be reconfigured according to the
customer network planning.

BSC6900 UMTS
l If one OMU is configured, fixed and virtual external IP addresses of the OMU must be in
the same network segment.
l If active and standby OMUs are configured, the fixed external IP addresses of the active
and standby OMUs, the virtual external IP address of the active and standby OMUs (the
virtual external IP address of the active OMU and that of the standby OMU are the same)
must be configured in the same network segment.
Table 3-2 describes the planning principles of OMU IP addresses.
Table 3-2 Onsite planning of OMU IP addresses

IP Address Planning Principle
Fixed external IP The default fixed external IP address of the active OMU is
address 172.121.139.201 (255.255.255.0).
The default fixed external IP address of the standby OMU is
172.121.139.202 (255.255.255.0).
Planning principle:
1. The fixed external IP address should be changed so that it is located in
the same network segment as the onsite network IP address. In
addition, the fixed external IP address cannot conflict with the onsite
network IP address. Configure the IP address of the external gateway
so that it is on the same network segment as the fixed external IP
address. In addition, the IP address of the external gateway cannot
conflict with the fixed external IP address.
2. If active and standby OMUs are configured, the fixed external IP
addresses of the active and standby OMUs must be different from each
other and located in the same network segment as the onsite network
IP address.
Virtual external 1. Change the virtual external IP address as required. Ensure that the
IP address virtual external IP address and the fixed external IP address are in the
same network segment (This network segment is called the OMU
external network segment). In addition, the virtual external IP address
cannot conflict with other IP addresses in the network segment.
For example, if active and standby OMUs are configured, the fixed
external IP address of the active OMU is 172.121.139.201, and that of
the standby OMU is 172.121.139.202, the virtual external IP address
can be configured as 172.121.139.200.
2. For example, if an independent OMU is configured and the fixed
external IP address of the OMU is 172.121.139.201, the virtual
external IP address can be configured as 172.121.139.200.
IP Addresses to Be Checked on Site

Review OMU IP addresses on site. If the IP addresses are located in the same network segment
as the onsite network IP address, they should be reconfigured. Table 3-3 describes the principles
of configuring the IP addresses.

BSC6900 UMTS
Table 3-3 Onsite checking of OMU IP addresses

IP Address Checking Principle
Fixed internal IP The default fixed internal IP address of the active OMU is 80.168.3.50
address (255.0.0.0).
The default fixed internal IP address of the active OMU is 80.168.3.50
(255.0.0.0).
Checking principle:
1. The network segment in which the fixed internal IP address is located
cannot conflict with the onsite network segment. If they conflict, you
must change the fixed internal IP address.
2. Only the network segment where the fixed internal IP address is
located can be changed. For example, 80.168.3.50 can be changed to
90.168.3.50.
3. If active and standby OMUs are configured, the fixed internal IP
addresses of the active and standby OMUs must be different and in the
same network segment.
4. If an independent OMU is configured and the network segment where
the fixed internal IP address is located does not conflict with the onsite
network segment, reserve the default fixed internal IP address.
5. The subnet mask of the fixed internal IP address must be 255.0.0.0.
Virtual internal 1. The virtual internal IP address must be located in the same subnet as
IP address the fixed internal IP addresses of the active and standby OMUs. This
subnet is called the OMU internal network segment. In addition, the
virtual internal IP address cannot be identical with other IP addresses
in the subnet and it should be configured as X.168.3.40 in which X
must be the same as the network segment where the fixed internal IP
address is located.
For example, if active and standby OMUs are configured, the fixed
internal IP address of the active OMU is 80.168.3.50, and that of the
standby OMU is 80.168.3.60, the virtual internal IP address can be
configured as 80.168.3.40.
2. For example, if an independent OMU is configured and the fixed
internal IP address of the OMU is 80.168.3.50, the virtual internal IP
address can be configured as 80.168.3.40.
3. The subnet mask of the virtual internal IP address must be 255.0.0.0.

BSC6900 UMTS
Debugging IP The default commissioning IP address of the active OMU is 192.168.6.50

address (255.255.255.0).
The default commissioning IP address of the standby OMU is
192.168.6.60 (255.255.255.0).
Checking principle:
1. The commissioning IP addresses of the active and standby OMUs
cannot be identical with other IP addresses on the live network. If they
are identical, you must change the commissioning IP address.
2. If active and standby OMUs are configured, the commissioning IP
addresses of the active and standby OMUs must be different and in the
same network segment.
For example, the commissioning IP address of the active OMU is
192.168.6.50 (255.255.255.0) and the commissioning IP address of the
standby OMU can be 192.168.6.60 (255.255.255.0).
the IP addresses of the backup channel between the active and standby
OMUs is located is different from the live network segment, retain the
IP addresses of the backup channel between the active and standby
OMUs.

BSC6900 UMTS
IP address of the For an active OMUa board, the IP address of the backup channel between
backup channel the active and standby OMUs must be set to X. X. X. 50. The default IP
between the address is 192.168.3.50 (255.255.255.0).
active and For a standby OMUa board, the IP address of the backup channel between
standby OMUs the active and standby OMUs must be set to X. X. X. 60. The default IP
address is 192.168.3.60 (255.255.255.0).
For an active OMUc board, the IP address of the backup channel between
the active and standby OMUs must be set to X. X. X. 50. The default IP
address of Ethernet adapter B-UPDATE0 is 192.168.9.50(255.255.255.0)
and that of Ethernet adapter B-UPDATE1 is 192.168.3.50
(255.255.255.0).
For an active OMUc board, the IP address of the backup channel between
the active and standby OMUs must be set to X. X. X. 60. The default IP
address of Ethernet adapter B-UPDATE0 is 192.168.9.60(255.255.255.0)
and that of Ethernet adapter B-UPDATE1 is 192.168.3.60
(255.255.255.0).
Planning principle:
1. The network segment where the IP addresses of the channel between
the active and standby OMUs are located cannot conflict with the live
network segment. If they conflict, the IP addresses of the channel
between the active and standby OMUs must be changed.
2. If active and standby OMUs are configured, the IP addresses of the
channel between the active and standby OMUs on the active and
standby OMUs must be different and in the same network segment.
the IP addresses of the backup channel between the active and standby
OMUs is located is different from the live network segment, retain the
IP addresses of the backup channel between the active and standby
OMUs.
4. The subnet mask of the IP address of the channel between the active
and standby OMUs must be 255.255.255.0.
5. The IP address of the backup channel between the active and standby
OMUs on Ethernet adapter B-UPDATE0 and that on Ethernet adapter
B-UPDATE1 must be on different network segments.
Impact of OMU IP Address Changes

Changing IP addresses for the OMU routine maintenance impacts the working of the
BSC6900, as described in Table 3-4.

BSC6900 UMTS
Table 3-4 Impact of OMU IP address changes

IP Address Change Impact
Fixed external IP After the fixed external IP address is changed, the device connected to the
address external Ethernet port can access the OMU only by using the new fixed
external IP address.
The fixed external IP address can be changed remotely and takes effect
immediately after it is changed.
Virtual external After the virtual external IP address is changed, the device connected to
IP address the OMU by using the original IP address can access the OMU only by
using the new virtual external IP address.
The virtual external IP address can be changed remotely and takes effect
immediately after it is changed.
Fixed internal IP The internal fixed IP address and the IP addresses of the BSC6900 host
address boards have been planned. Therefore, only the network segment on which
the internal fixed IP address is located can be changed so that the internal
fixed IP address is not identical with the IP addresses of the BSC6900 host
boards.
If the network segment where the fixed internal IP address is located is
changed, the BSC6900 subnet number must be changed as well.
Otherwise, the communication between the OMU and the BSC6900 host
boards will be interrupted.
The fixed internal IP address is usually changed when the OMU is
debugged on site to avoid negative effects caused by frequent resets of the
BSC6900 during daily maintenance.
The fixed internal IP address can be changed remotely. After it is changed,
you must reset the BSC6900 host at the local end.
Virtual internal The virtual and fixed internal IP addresses must be changed at the same
IP address time.
After the virtual internal IP address is changed, reset the BSC6900 host
boards so that the communication between the OMU and the BSC6900
host boards can be reestablished.
The virtual internal IP address is usually changed when the OMU is
debugged on site to avoid negative effects caused by frequent resets of the
BSC6900 during daily maintenance.
The virtual internal IP address can be changed remotely. After it is
changed, you must reset the BSC6900 host boards at the local end.
IP address of the After the IP address of the backup channel between the active and standby
backup channel OMUs is changed, reset the OMUs so that the communication between
between the the active and standby OMUs can be re-established.
active and The IP address of the backup channel between the active and standby
standby OMUs OMUs can be changed remotely and takes effect immediately after it is
changed.

BSC6900 UMTS
IP Address Change Impact
Debugging IP After the commissioning IP address is changed, the device connected to

address the commissioning Ethernet port cannot access the OMU. The OMU can
be accessed only by using the new commissioning IP address.
The commissioning IP address must be changed by connecting the
commissioning Ethernet port. The new IP address takes effect
immediately after the change.
NOTE
l The fixed internal and external IP addresses are bound to the active and standby OMUs, and the virtual
internal and external IP addresses are bound to the active OMU. For example, after the switchover of the
active and standby OMUs, the fixed internal and external IP addresses of the original active and standby
OMUs remain the same while the virtual internal and external IP addresses of the original active OMU
become the virtual internal and external IP addresses of the original standby OMU. There is no virtual internal
or external IP addresses for the original active OMU.
l Each pair of the following IP addresses must be in the same network segment: fixed and virtual internal IP
addresses, fixed and virtual external IP addresses, IP addresses of the channel between the active and standby
OMUs on the active OMU and standby OMU, commissioning IP address of the active and standby OMU.
The network segments of these pairs of IP addresses cannot conflict with each other. Additionally, the IP
addresses on a network segment cannot conflict, either.
l Record the IP addresses in 4.5.1 Information Record Sheet of OMU Software Installation.
l The next hop IP address of the M2000 route must be the virtual external IP address of the OMU.
3.3 OMU Networking Principle

The internal Ethernet adapters of the OMU are connected to the SCUs in the MPS, and the
external Ethernet adapters of the OMU are connected to the OM terminals. In this way, the OMU
fulfills the communication between the BSC6900 and the OM terminals.
Single-OMUa/OMUc Networking Principle

Figure 3-4, Figure 3-5, Figure 3-6, and Figure 3-7 show the networking topology in single-
OMUa/OMUc mode.

BSC6900 UMTS
Figure 3-4 Single-OMUa networking topology (with a single LAN switch)

BSC6900 UMTS
Figure 3-5 Single-OMUc networking topology (with a single LAN switch)

BSC6900 UMTS
Figure 3-6 Single-OMUa networking topology (with two LAN switches)
The two internal Ethernet adapters ETH4-SCU7 and ETH5-SCU6 of the OMUa board are
connected to the SCUs in slots 7 and 6 of the MPS through the backplane, respectively.
The two external Ethernet adapters ETH0 and ETH 1 of the OMUa board are connected to the
OM terminals through network equipment such as a hub, LAN switch, or router. In this way,
the OMU fulfills the communication between the BSC6900 and the OM terminals.
As shown in Figure 3-6, the two external Ethernet ports of the OMUa board are connected to
the two LAN switches, respectively, which improves network reliability. In this network
topology, the Ethernet ports connecting the ETH0, ETH1, and LAN switches must be in the
same intranet as the two Ethernet ports on the LAN switches connecting ETH0 and ETH1.
Moreover, the Ethernet adapter marked in blue in Figure 3-6 must be enabled with the Spanning
Tree Protocol (STP) function to prevent network storms.

BSC6900 UMTS
Figure 3-7 Single-OMUc networking topology (with two LAN switches)
The two internal Ethernet adapters B_ETH1 and B_ETH0 are connected to the SCUs in slots 6
and 7 in the MPS respectively through the backplane.
The two external Ethernet adapters F_ETH1 and F_ETH0 of the OMUc board are connected to
the OM terminals through network equipment such as a hub, LAN switch, or router. In this way,
As shown in Figure 3-7, the two external Ethernet ports of the OMUc board are connected to
the two LAN switches respectively, which improves network reliability. In this network
topology, the Ethernet ports connecting F_EH0, F_ETH1, and LAN switches must be in the
same Intranet as the two Ethernet ports on the LAN switches connecting F_ETH0 and F_ETH1.
Moreover, the Ethernet adapter marked in blue in Figure 3-7 must be enabled with the Spanning
Tree Protocol (STP) function to prevent network storms.

BSC6900 UMTS
Dual-OMUa/OMUc Networking Principle

Figure 3-8, Figure 3-9, Figure 3-10, Figure 3-11, Figure 3-12, and Figure 3-13 show the
networking topology in dual-OMUa/OMUc mode.
Figure 3-8 Dual-OMUa networking topology (with a single LAN switch)

BSC6900 UMTS
Figure 3-9 Dual-OMUc networking topology (with a single LAN switch)

BSC6900 UMTS
Figure 3-10 Dual-OMUa/OMUc networking topology (with a single LAN switch)

BSC6900 UMTS
Figure 3-11 Dual-OMUa networking topology (with two LAN switches)
The two internal Ethernet adapters ETH4-SCU7 and ETH5-SCU6 of the OMUa board are
connected to the SCUs in slots 7 and 6 of the MPS respectively through the backplane.
The two external Ethernet adapters ETH0 and ETH 1 of the OMUa board are connected to the
OM terminals through network equipment such as a hub, LAN switch, or router. In this way,
The ETH3-UPDATE of the active OMUa board is connected to the ETH3-UPDATE of the
standby OMUa board through the backplane to fulfill the data synchronization and the update
of OMU software between the active and standby OMUs.
As shown in Figure 3-11, the two external Ethernet ports of the active and standby OMUs are
connected to the two LAN switches respectively, which improves network reliability. In this
network topology, the Ethernet ports connecting the ETH0, ETH1, and LAN switches must be
in the same Intranet as the two Ethernet ports on the LAN switches connecting ETH0 and ETH1.

BSC6900 UMTS
Moreover, the Ethernet adapter marked in blue in Figure 3-11 must be enabled with the STP
function to prevent network storms.
Figure 3-12 Dual-OMUc networking topology (with two LAN switches)
The two internal Ethernet adapters B_ETH0 and B_ETH1 of the OMUc board are connected to
the SCUs in slots 7 and 6 in the MPS respectively through the backplane.
The two external Ethernet adapters F_ETH0 and F_ETH1 of the OMUc board are connected to
the OM terminals through network equipment such as a hub, LAN switch, or router. In this way,
The B_UPDATE0 of the active OMUc board is connected to the B_UPDATE0 of the standby
OMUc board through the backplane. This fulfills data synchronization and update of OMU
software between the active and standby OMUs.

BSC6900 UMTS
network topology, the Ethernet ports connecting F_EH0, F_ETH1, and LAN switches must be
in the same Intranet as the two Ethernet ports on the LAN switches connecting F_ETH0 and
F_ETH1. Moreover, the Ethernet adapter marked in blue in Figure 3-12 must be enabled with
the STP function to prevent network storms.
Figure 3-13 Single-OMUc/OMUa networking topology (with two LAN switches)
The two internal Ethernet adapters of the OMU are connected to the SCUs in slots 7 and 6 in
the MPS respectively through the backplane.
The two external Ethernet adapters of the OMU are connected to the OM terminals through
network equipment such as a hub, LAN switch, or router. In this way, the OMU fulfills the
communication between the BSC6900 and the OM terminals.

BSC6900 UMTS
The B_UPDATE1 of the active OMUc board is connected to the ETH3-UPDATE of the standby
OMUa board through the backplane. This fulfills data synchronization and update of OMU
software between the active and standby OMUs.
network topology, the Ethernet ports connecting external Ethernet adapters and LAN switches
must be in the same Intranet as the two Ethernet ports on the LAN switches connecting external
Ethernet adapters. Moreover, the Ethernet adapter marked in blue in Figure 3-12 must be enabled
with the STP function to prevent network storms.
3.4 Active/Standby Workspaces of the OMU

The active/standby workspaces of the OMU are used for the upgrade and rollback of the
BSC6900 versions, therefore enabling quick switching between versions.
Concept of the Active/Standby Workspaces of the OMU

The active/standby workspaces of the OMU refer to the active/standby workspaces for storing
the version files on the OMU. Each workspace is used to store files of different versions.
The relationship between the active/standby workspaces is relative. The active/standby

relationship depends on the storage location of the running version. The workspace that stores
the running OMU version files is the active workspace, and the other is the standby workspace.
Working Principles of the Active/Standby Workspaces of the OMU

The working principles of the OMU active/standby workspaces in the case of the OMU version
upgrade are as follows:
1. The standby workspace of the active OMU is upgraded to a new version.
2. The standby workspace of the standby OMU is upgraded to a new version.
3. A switchover is performed between the active and standby workspaces of the active OMU.
The standby workspace that stores the new version of files becomes active, and the other
workspace becomes standby.
4. The active OMU runs the upgraded version.
5. A switchover is performed between the active and standby workspaces of the standby OMU
to ensure that the versions of the workspaces are consistent with those of the active OMU.
6. The OMU version upgrade is complete.
After the OMU version upgrade, the standby workspaces of the active and standby OMUs store
the files of the old version. In this case, version rollback can be performed as required.
The working principles of the OMU active/standby workspaces in the case of version rollback
are as follows:
1. A switchover is performed between the active and standby workspaces of the active OMU.
The running version of the active OMU is rolled back to the source version.
2. The active OMU runs the source version.

BSC6900 UMTS
3. A switchover is performed between the active and standby workspaces of the standby OMU
to ensure that the versions of the workspaces are consistent with those of the active OMU.
4. The OMU version rollback is complete.
Relationship Between Intra-OMU Active and Standby Workspaces

The active and standby workspaces of the OMU are independent of each other. The operation
of the active workspace does not change any information in the standby workspace.
Relationship Between Inter-OMU Active and Standby Workspaces

The active and standby workspaces of the active OMU correspond to the active and standby
workspaces of the standby OMU respectively. Between the active and standby OMUs, the files
in the active workspaces are automatically synchronized in real time, but those in the standby
workspaces need to be synchronized manually.
Relationship Between the Active/Standby Workspaces of Host Boards and the

Active/Standby Workspaces of the OMU
On the active workspaces of the host boards, files can be loaded only from the active workspace
of the OMU. On the standby workspaces of the host boards, files can be loaded only from the
standby workspace of the OMU.
3.5 Heartbeat Detection on Active and Standby OMUs

In active/standby OMU mode, heartbeat detection is performed on active and standby OMUs to
check whether the active and standby OMUs are working properly.
Heartbeat refers to response messages between active and standby OMUs. In active/standby
OMU mode, active and standby OMUs send heartbeat messages to each other to ensure that they
work properly and the network connection is normal.
The principle of heartbeat detection is: The active and standby OMUs send status messages to
each other and check the messages. Based on the active/standby policy, they determine whether
they are operating as the active or standby OMU. In addition, they decide whether to perform a
switchover after negotiation. If an OMU cannot receive any messages from the other for a period
of time, the uncommunicative OMU is considered faulty. If the active OMU is faulty, a
switchover is triggered.
3.6 Synchronization Between Active and Standby OMUs

In dual-OMU mode, the synchronization between the active OMU and the standby OMU
consists of data synchronization, file synchronization, and time synchronization.
Data Synchronization
The OMU data is dynamic, which changes when the BSC6900 is working. After the standby
OMU starts, the active OMU data is fully synchronized, and the increments are synchronized.
This ensures that the OMU can work normally after a switchover.

BSC6900 UMTS
File Synchronization
The synchronization between active OMU files and standby OMU files is mainly applicable to
dynamic files. The dynamic files include the license file, board program, BOOTROM file, DSP
file, patch file, and performance measurement file. The software management module on the
standby OMU regularly checks the active OMU files and synchronizes the dynamic files on the
active OMU with those on the standby OMU. This ensures that the files on the active and standby
OMUs are the same.
Time Synchronization
Time synchronization means that the sntp module on the standby OMU regularly synchronizes
the time with the sntp module on the active OMU. This ensures that the time on the active and
standby OMUs is the same.
3.7 Switchover Between Active and Standby OMUs

For OMUs working in active/standby mode, there are four types of switchover: manual
switchover, fault-triggered switchover, failover, and self-healing switchover.
NOTE
Operation and maintenance can be performed on the LMT only after a switchover is successfully completed.
Manual Switchover
If OMUs work in active/standby mode and the data synchronization between the active and
standby OMUs is normal, you can manually switch over the OMUs as required. For example,
you need to manually switch over OMUs for software and hardware upgrade or fault
rectification. To manually switch over the OMUs, run the SWP OMU command or use the
LMT. For detailed operations, see Switching Over the BSC Boards in the BSC6900 UMTS LMT
User Guide. After the manual switchover, the original standby OMU becomes the active OMU,
and the original active OMU becomes the standby OMU.
Manual switchover can only be performed when the active and standby OMUs work properly.
In addition, at least one of the following conditions must be met:
l The DSP OMU command output shows that the value for Data-sync state is Data
synchronization is successful.
l The DSP OMU command output shows that the version of the active OMU applications
is different from that of the standby OMU applications.
l The ALM-20701 OMU Failure Switchover persists after a fault-triggered OMU switchover
is performed.
CAUTION
Before performing the manual switchover, do not perform an operation that may change the data
in the database. For example, do not modify configuration data or user information.

BSC6900 UMTS
Fault-Triggered Switchover
When the active and standby OMUs operate properly, the active OMU maintains the
BSC6900 and the standby OMU monitors the active OMU. If a fault occurs on the active OMU
and persists for more than 5 minutes, the standby OMU automatically becomes active. After the
fault is rectified, the original active OMU becomes standby. If the fault is rectified within 5
minutes, the switchover does not occur.
After the fault-triggered switchover, the OMU automatically reports the alarm ALM-20701
OMU Failure Switchover and initiates a CRC. If the host data is consistent with the OMU data,
the alarm is automatically cleared. If the host data is inconsistent with the OMU data, the alarm
persists.
NOTE
If the DSP OMU command output shows that the values for Internal network link state, External network
state, and Backup network link state are all Breakdown, then the active OMU is faulty.
Failover
When the active OMU runs longer than the failover interval, a failover occurs. To reduce the
impact on the services, the failover usually occurs between 03: 00 and 05: 00.
You can run the SET ASWPARA command to set whether the failover between the active and
standby OMUs is allowed. You can also run this command to set the failover interval.
NOTE
l The failover is only functional on an OMU running Windows.

l You should not set parameters during the failover. You can query the time when the failover occurred by
running the LST ASWPARA command.
Self-Healing Switchover
Self-healing switchover is a method of self-healing for the OMUs.
The active OMU performs a self-healing switchover when any of the following conditions
occurs:
l The hard disk capacity of the active OMU overflows if the remaining space is smaller than
200 MB.
l An abnormality occurred on the active OMU for 10 times within 30 minutes.
l No Ethernet cable is connected to the external Ethernet ports on the active OMU.
l The virtual internal or external IP address of the active OMU is lost for more than 3 minutes.
l The standby OMU detects that the active OMU is restarted abnormally three times within
24 hours.
l The connection between the active OMU and SCU is interrupted and the connection
between the standby OMU and SCU is normal.

BSC6900 UMTS
OMU Administration Guide 4 Scenario: Deploying a BSC6900
4 Scenario: Deploying a BSC6900
About This Chapter
This section describes how to install software and perform operation and maintenance for the
OMU when a BSC6900 is deployed.
NOTE
In the scenario of deploying the BSC6900, the physical entity to carry the OMU is the OMUa or OMUc board
(recommended). For the policy of replacing a faulty OMUa or OMUc board, see Replacing an OMU Board in
the BSC6900 UMTSSite Maintenance Guide.
OMU Software Structure

The OMU software consists of the operating system and the OMU applications. Figure 4-1
shows the OMU software structure.
Figure 4-1 OMU software structure
l Operating System
The DOPRA Linux operating system is used.
l OMU Applications
The OMU applications run on the bottom-level operating system and provide various
service processes.
Scenario Overview
Figure 4-2 shows how to install OMU applications when deploying a BSC6900.

BSC6900 UMTS
Figure 4-2 OMU applications installation scenarios
l Commissioning phase
Determine whether to reinstall OMU applications based on the status and version of the
current OMU applications and configure the correct OMU IP address for communication
between the LMT and BSC6900 operation and maintenance network.
l Maintenance phase
If OMU applications cannot work properly during the maintenance phase, select one of the
following ways to reinstall the OMU applications:
1. Use the USB flash drive. With this method, the OMU operating system and
applications will be reinstalled. For details, see 4.2.2 Optional: Installing the
Operating System and OMU Applications.
2. Use the OMU applications installation file in the version package. If this way is used,
only the OMU applications will be reinstalled. For details, see 4.2.3 Optional:
Installing the OMU Applications.
4.1 Installing the OMU Applications in Field Commissioning
The OMU operating system is installed before the OMU is delivered. However, it is uncertain
whether the OMU applications are installed and whether the versions of the OMU applications
are correct. Before you use the OMU for the first time, you need to check whether the OMU
applications are installed as well as their version information and configure the IP addresses,
subnet mask, and OMU name onsite according to the IP address planning principle.
4.2 Reinstalling Software Onsite
If an OMUa/OMUc board is damaged onsite, replace it. If the operating system fails, reinstall
it along with the OMU applications.
4.3 Operating and Maintaining the OMU

BSC6900 UMTS
This section describes how to perform operation and maintenance on the OMU after OMU
applications are installed. To perform this task, log in to the OMU remotely or run MML
commands.
4.4 Appendix: OMU-Related Software
The OMU-related software, including the psftp software and PuTTY software, is used to install
the OMU applications and perform operation and maintenance on the OMU.
4.5 Appendix: OMU-Related Information Tables
This section describes the tables in which the OMU information is recorded during routine
operation and maintenance on the OMU.

BSC6900 UMTS
4.1 Installing the OMU Applications in Field

Commissioning
The OMU operating system is installed before the OMU is delivered. However, it is uncertain
whether the OMU applications are installed and whether the versions of the OMU applications
are correct. Before you use the OMU for the first time, you need to check whether the OMU
applications are installed as well as their version information and configure the IP addresses,
subnet mask, and OMU name onsite according to the IP address planning principle.
4.1.1 Setting the Link Mode of the External OMU Ethernet Adapter
This section describes how to set the link mode of the external OMU Ethernet adapters so that
it is the same as that of the LAN switch.
Prerequisites
The link mode, duplex mode, and rate of the LAN switch have been acquired.
Context
There are two link modes of the LAN switch: force mode and auto-negotiation mode. The link
mode of the OMU external Ethernet adapter must be consistent with that of the LAN switch.
If the link mode of the external Ethernet adapters of the OMU is inconsistent with that of the
LAN switch, the network may be interrupted. If the link mode of the LAN switch is specified,
the link mode of the external Ethernet adapter of the OMU should also be specified.
If active and standby OMUs are configured, perform the following steps on both the active and
standby OMUs:
NOTE
l The following procedure assumes that the link mode of the external Ethernet adapter is force mode and
the adapter works at 100 Mbit/s in full duplex mode.
l The following procedure assumes that version_a is the active workspace of the OMU. To query the
active workspace of the current OMU, run the LST OMUAREA command.
Procedure
Step 1 Log in to the target OMU by referring to Logging In to the OMU.
Step 2 Enter the /etc/rc.d/omud stop command and press Enter to stop the omud.
Step 3 Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the directory
where the omutool program is saved.
Step 4 Run the ./omutool duplexmode 100 full off command.

BSC6900 UMTS
NOTE
Querying the link mode of the external OMU network adapters, see 4.3.4 Querying the Link Mode of
the External OMU Network Adapters.
The fields in the ./omutool duplexmode 100 full off command are described as follows:
l 100 indicates that the rate of the Ethernet adapter is 100 Mbit/s. The value of this field can be 10, 100,
or 1000.
l full indicates that the Ethernet adapter works in full duplex mode. The value of this field can be full
or half.
l off indicates that the link mode of the Ethernet adapter is force mode. The value of this field can be off
or on. When the value of this field is on, the link mode is auto-negotiation mode.
Step 5 Enter the /etc/rc.d/omud start command and press Enter to start the omud.
----End
4.1.2 Commissioning OMU Onsite

Before using the OMU for the first time, commission the OMU onsite to check whether OMU
applications have been installed and the version of the OMU applications.
Prerequisites
The OMU is connected to the local PC by using the commissioning Ethernet port.
Context
NOTE
In a newly deployed site, the active workspace of the delivered OMU is version_a.
Procedure
Step 1 Connect the PC to the ETH2 debugging port on the OMU board by using an Ethernet cable.
Step 2 Set the IP address of the PC to be on the same network segment with the ETH2 port. The initial
IP address of the ETH2 port is 192.168.6.50 or 192.168.6.60, the subnet mask is 255.255.255.0.
Step 3 Log in to the OMU by referring to Logging In to the OMU in theBSC6900 UMTS OMU
Administration Guide.
Step 4 Check whether the link mode of the external OMU Ethernet Adapter is consistent with that of
LAN Switch by referring to theBSC6900 UMTS OMU Administration Guide for Setting the
Link Mode of the External OMU Ethernet Adapters about Procedure.
Step 5 Run the /etc/rc.d/omud status command to check the running status of the OMU process.
If... Then...
The information displayed is running Change the IP address. The detailed

operations are as follows:
1. Run the /etc/rc.d/omud stop command to
stop the omud process.
2. Go to Step 6.
The information displayed is unused Go to Step 6.

BSC6900 UMTS
If... Then...
The information displayed is No such file or 1. Install the OMU application in the active
directory workspace by referring to the BSC6900
UMTS OMU Administration Guide for
Installing the OMU Applications in the
Active Workspace about Procedure.
2. Perform steps Step 7 through Step 10.
Step 6 Run the cd /mbsc/upgrade command to switch to the OMU installation directory, and then run
the ls command to query the current version of the OMU application.
If... Then...
The version of the OMU application is the Perform steps Step 7 through Step 16.
same as required by the operator
The version of the OMU application is 1. Uninstall the OMU application by

different from what is required by the referring to theBSC6900 UMTS OMU
operator Administration Guide for Uninstalling
the OMU Applications about
Procedure.
2. Upload the OMU application installation
package to OUM by referring to
theBSC6900 UMTS OMU Administration
Guide for Uploading the OMU
Application Installation Package to the
OMU about Procedure.
3. Install the OMU application in the active
workspace by referring to theBSC6900
UMTS OMU Administration Guide for
Installing the OMU Applications in the
Active Workspace about Procedure.
Step 7 Run the cd /mbsc/bam/version_a/bin/bam command to switch to the directory where the
omutool program locates.
NOTE
To view the help information of the omutool, run the ./omutool -h command.
Step 8 Change the external fixed IP address and the subnet mask according to the plan of the operator.
Run the ./omutool extercard The external fixed IP address The subnet mask The gateway IP
address (Optional) command to change the external fixed IP address and the subnet mask. For
example, you can type the following command and then press Enter.
./omutool extercard 10.161.10.100 255.255.255.0

BSC6900 UMTS
NOTE
l The following two ways show how to change an external fixed IP address if changing a gateway IP
address is required at the same time.
l Method 1: Run the ./omutool extercard The external fixed IP address The subnet mask (The
gateway IP address) command and then click the Enter to change the external fixed IP address
and the gateway IP address at the same time. For example:
./omutool extercard 10.161.10.100 255.255.255.0 10.161.10.1
l Method 2: Run the ./omutool gateway The external IP address command and then press Enter to
change the gateway IP address separately. For example:
./omutool gateway 10.161.10.1
l After the external fixed IP address is changed, the OMU can be connected to the OM network of the
operator by the ETH0 or ETH1 port. In this case, the commissioning task can be performed in a
centralized manner.
Step 9 Change the external virtual IP address and the subnet mask of the active and standby OMUs
according to the plan. Ensure that the external virtual IP address is on the same network segment
as the external fixed IP address.
Run the ./omutool extervip The external virtual IP address The subnet mask command to change
the external virtual IP address and the subnet mask. For example, you can type the following
command and then press Enter.
./omutool extervip 10.161.10.102 255.255.255.0
NOTE
When the external fixed or virtual IP address is being changed, a window is displayed to remind users to
check whether the external virtual or fixed IP address and the gateway IP address need to be changed. In
this way, users can make necessary changes to ensure the three IP addresses are in the same segment.
Step 10 Check whether the internal fixed IP address, internal virtual IP address, backup channel IP
address, and debugging IP address of active and standby OMUs are on the same network segment
as the network of the operator.

BSC6900 UMTS
If... Then...
Any IP address is on the same Change the IP address in conflict.

network segment as the network of l Run the ./omutool innercard The internal fixed IP
the operator address command to change the internal fixed IP
address and the subnet mask. For example, you can
type the following command and then press Enter.
./omutool innercard 80.168.3.60
l Run the ./omutool innervip The internal virtual IP

address command to change the internal virtual IP
./omutool innervip 80.168.3.40
NOTE
l When the internal fixed or virtual IP address is being
changed, a window is displayed to remind users to
check whether the internal virtual or fixed IP address
need to be changed. In this way, users can make
necessary changes to ensure the two IP addresses are in
the same segment.
l If the network segment of the internal fixed IP address
or that of the internal virtual IP address is changed, the
Subnet No. must be changed when updating the OMU
database. For details, see "Follow-up Procedure" in
Updating the OMU Database.
l Change the backup channel IP address and subnet
mask of the active and standby OMUs:
If OMUa boards are used, run the ./omutool
backupcard The IP address command. For
example, you can type the following command
and then press Enter.
./omutool backupcard 192.168.3.60
If OMUc boards are used, run the ./omutool

backupcard_for_omuc The IP address and ./
omutool backupcard_for_omua The IP
address command. For example, you can type the
following command and then press Enter.
./omutool backupcard_for_omuc 192.168.9.60
./omutool backupcard_for_omua 192.168.3.60
l Run the ./omutool debugcard The debugging IP

address command to change the debugging IP
./omutool debugcard 192.168.6.60

BSC6900 UMTS
If... Then...
All IP addresses are not on the Change the backup channel IP addresses of the standby
same network segment as the OMU.
network of the operator l If OMUa boards are used, run the ./omutool
backupcard The IP address command. For example,
you can type the following command and then press
Enter.
./omutool backupcard 192.168.3.60
l If OMUc boards are used, run the ./omutool

backupcard_for_omuc The IP address and ./
omutool backupcard_for_omua The IP address
command. For example, you can type the following
command and then press Enter.
./omutool backupcard_for_omuc 192.168.9.60
./omutool backupcard_for_omua 192.168.3.60
Step 11 Run the ./omutool hostname OMU name command to change the name of the OMU.
For example, you can type the following command and then press Enter to change the OMU
name to omu_123: ./omutool hostname omu_123.
NOTE
The OMU name cannot contain control characters, spaces, or any of the following characters: / \ [ ] ( ) ' : | < >
+ = ; , ? , and the length of the OMU name rangs from 1 to 62 characters.
Step 12 Set the working mode of the OMU based on the number of configured OMU boards.
l If only one OMU board is configured, run the ./omutool dualmode single command to set
the working mode to the single-server mode.
l If two OMU boards (active and standby OMU boards) are configured, run the ./omutool
dualmode dual command to set the working mode to the dual-server mode.
Step 13 Run the cd /mbsc/bam/common command to switch to the directory where the reg.ini file
locates.
1. Run the vi reg.ini command to open the reg.ini file.
2. Move the cursor with arrow keys and then set mlangflag to CHS or ENG to change the
language used in the OMU.
3. Move the cursor with arrow keys and then set runmode to UO to change the service mode
of the OMU.
4. Move the cursor with arrow keys and then set officename to change the office name.
5. Press Esc, input : and then wq, and press Enter. The reg.ini file is changed.

BSC6900 UMTS
NOTE
l To set the preceding information, move the cursor to the beginning character of the information
to be modified, press X to delete the existing information, then press A, and you can input the
new information. After you modify an information item, press Esc and then move the cursor to
modify another information item.
l To quit without saving your modification, perform either of the following operations:
l Operation 1: Press Esc, type : and then q!. Press Enter.
l Operation 2: Directly close the PuTTY window. If you perform this operation, a prompt is
displayed when you edit the reg.ini file using the vi command next time. In this case, type
D and then press Enter to open the reg.ini file.
NOTE
You can also copy the reg.ini file to the local PC to change the previous information by using the psftp
software.
1. Obtain the psftp software and open it locally by double-clicking the application icon.
2. Input cd /mbsc/bam/common in the psftp command line window to switch to the directory where the
reg.ini file locates.
3. Input get reg.ini in the psftp command line window to transfer the reg.ini file from the OMU to the
directory where the psftp software locates.
4. Open the reg.ini file with Notepad, set mlangflag to CHS or ENG, set runmode to UO, and then set
officename.
5. Input put reg.ini in the psftp command line window to upload the modified reg.ini file from the local
PC to the OMU.
Step 14 Run the /etc/rc.d/omud start command to start the OMU application.
Step 15 Run the ps -afx command to check the operating status of the OMU.
The OMU is operating properly if all OMU processes exist in the OMU active workspace
directory/mbsc/bam/version_a/bin/bam/monitor.
OMU State OMU Processes that Must Exist
Active OMU host_gate, ems_gate, authority, configure,

maintain, stat, alarm, software,
ftp_server, sntp, ems_agent,
omu_manager, cfa, weblmt, debug_log,
cfg_mirror
Standby OMU software, ftp_server, sntp, omu_manager,

debug_log
NOTE
If some of the processes do not exist, run the /etc/rc.d/omud restart command to restart the OMU server,
and then check again whether the processes exist. If some of them still do not exist, uninstall the OMU
application and then install the OMU application in the active workspace by referring to theBSC6900
UMTS OMU Administration Guide for Uninstalling the OMU Applications and Installing the OMU
Applications in the Active Workspace about Procedure.
Step 16 Run the exit command to terminate the PuTTY software to log out of the OMU.
----End

BSC6900 UMTS

If an OMUa/OMUc board is damaged onsite, replace it. If the operating system fails, reinstall
it along with the OMU applications.
4.2.1 Preparations for Installing Software Onsite

Before reinstalling the OMU software onsite, ensure that the following items are available: the
OMUa/OMUc board, portable computer, BSC6900 version installation package or patch
installation package, and the Dopra_Linux_USB Disks.
Configuration of the OMUa and OMUc Boards

See the hardware configuration indexes of the OMUa and OMUc boards described in Technical
Specifications of the OMUa Board and Technical Specifications of the OMUc Board.
Configuration Requirements for the Portable Computer

Table 4-1 lists the configuration requirements of the portable computer.
Table 4-1 Configuration requirements for the portable computer
Item Quantity Recommended Minimum Configuration

Configuration
CPU 1 1.66 GHz or faster 866 MHz
RAM 1 512 MB 256 MB
Hard disk 1 80 GB 10 GB
Display - 1024x768 pixels or higher 800600

adapter
resolutio
n
CD drive 1 - -
USB 1 - -
installati
on drive
Operatin - l Microsoft Windows XP -

g system Professional
l Microsoft Windows
Server 2003
l Microsoft Windows 7
Check that Microsoft .NET Framework 2.0 or later has been installed on the portable computer.

BSC6900 UMTS
NOTE
To check whether Microsoft .NET Framework 2.0 or later has been installed, choose Start > Settings >
Control Panel > Add or Remove Programs to view the components installed on the portable computer.
If Microsoft .NET Framework 2.0 or later has not been installed on the portable computer,
rundotnetfx2.0.exe under software package for preparing a USB storage device used for switching
the OMU operating system to Dopra Linux\tools.
Software Required for the Installation

Ensure that the following software package is available:
l BSC6900 version installation package or patch installation package
l Dopra_Linux_USB Disks
NOTE
Contact Huawei engineers who can obtain the installation package and tool by performing the following
operation:
l Log in to http://support.huawei.com/support/ and choose Software Center > Version Software >
Wireless Product Line > SingleRAN > MBSC > BSC6900 > BSC6900 Product Version > BSC6900
Software Version.
l Click Software Version VER to obtain the BSC6900 version installation package.
l Log in to http://support.huawei.com/support/ and choose Software Center > Version Software >
Wireless Product Line > SingleRAN > SRAN O&M tools to obtain the Dopra_Linux_USB Disks.
4.2.2 Optional: Installing the Operating System and OMU

Applications
If the OMU applications cannot work properly during the maintenance, reinstall the OMU
Operating System and applications by using the USB flash drive.
Context
l When reinstalling the OMU applications, re-import the OMU configuration data. You must
back up the OMU data before reinstalling the OMU applications and restore the OMU data
after the installation. For details, see Backing Up the System Data and Restoring System
Data.
l If the OMU data cannot be backed up because the OMU applications cannot work properly,
obtain the latest backup data for restoration.
Preparing a USB Storage Device

This section describes how to prepare a USB storage device to quickly install and restore the
OMU operating system.
Prerequisites
l The capacity of the USB storage device is at least 2 GB. If the BSC6900 is configured with
active and standby OMUs, two USB storage devices are required.
l The USB storage device is inserted in a functional USB port on the portable PC.
l The portable PC has read and write rights on the USB port.
l You have obtained the planned OMU IP addresses and the OMU name and have recorded
them in Configuration Information for Preparing USB Storage Device.

BSC6900 UMTS
Context
CAUTION
This function is for quickly restoring data and rectifying faults. During the process, data is
encrypted against the risk of information leakage.
The USB storage device can be used to install the OMU operating system or install both the
OMU operating system and the OMU applications. The installation made depends on whether
the OMU version installation package or patch installation package has been installed when the
USB storage device is prepared.
The USB storage device is used in the following scenarios:
l Initially installing the OMU operating system and applications
l Restoring the corrupted OMU operating system
When the USB storage device is used to perform operations on the OMU, the OMU data is
affected as follows:
l If the Operate Type of the USB storage device is Install, the hard disk drive is formatted
and the OMU data is erased. Therefore, back up the OMU data before installing the OMU
operating system by using the USB storage device.
After the OMU operating system is installed, user security settings (including user
passwords and security policies) are restored to the factory settings.
For details about the password for the root user, see section Checklist for the OMU
Board Software Factory Settings.
For details about security policies for the root user password, see section Dopra Linux
OS Security in the Dopra_Linux_USB Disks software package.
l If the Operate Type of the USB storage device is Recover, then only the OMU operating
system is restored. The OMU applications and data are lost.
NOTE
The modified and deleted system files cannot be restored using the USB storage device. The USB storage device
applies only to the following scenarios:
1. The OMU operating system cannot start.
2. When the OMU operating system starts, a message is displayed that prompts you to restore the file system.
3. After the OMU operating system starts, a Kernel panic error is displayed that indicates a failure in loading
rootfs.
If the OMU operating system cannot be restored using the USB storage device, you are advised to reinstall the
OMU operating system using the USB storage device.
Before preparing a USB storage device, verify the device by referring to DOPRA Linux USB
Disk Certificate Guide in the directory where the Dopra Linux USB storage device is saved. If
the USB storage device is not usable, replace it. The Netac U208 (2 GB), Kingston and Sandisk
USB storage devices are recommended.
The duration for preparing a USB storage device varies based the bandwidth of the network
from the PC to the equipment room, the USB protocol, and the PC performance. The duration
listed in Table 4-2 refers to the duration for preparing a USB storage device in compliance with
the USB2.0 protocol. The duration for preparing a USB storage device in compliance with the

BSC6900 UMTS
USB1.1 protocol takes about twice as long as preparing a USB storage device in compliance
with the USB2.0 protocol. If the duration for preparing the device requires much longer than the
listed duration, the performance of the PC in use is poor. If this occurs, restart the PC or use a
PC with a higher level of performance.
Table 4-2 Operation and duration

Operation Duration
Prepare a USB storage device. The duration varies based on the bandwidth
of the network from the PC to the equipment
room.
l If the network bandwidth is 1 Mbit/s or
higher:
and an independent OMU is
configured, the duration is 15 to 30
minutes.
and active and standby OMUs are
minutes.
l If the network bandwidth is 512 kbit/s:
minutes.
minutes.
Install, restore, or switch the OMU operating 20 to 40 minutes

system using a USB storage device.
NOTE
The following operations assume that you are preparing a USB storage device for active and standby OMUs.
Differences are specified for preparing USB storage devices for active and standby OMUs and for an independent
OMU.
Procedure
l Preparing the USB storage device for initially installing the OMU operating system and
applications
1. Double-click U_creator_eng.exe to begin installing a Dopra Linux operating system
on the USB storage device, as shown in Figure 4-3.

BSC6900 UMTS
Figure 4-3 U_creator_eng window
2. Right-click NE List in the left pane of the window shown in Figure 4-3 and choose
Add NE from the shortcut menu. A dialog box is displayed, as shown in Figure
4-4.

BSC6900 UMTS
Figure 4-4 Add NE dialog box
3. Specify NE Name, set Operate type to Install, and select Install OMU Then click
OK. An NE is added.
NOTE
l To initially install OMU applications, select Install OMU and specify External Virtual IP
Address of the NE to be added.
l The NE name, used to identify an NE, can include only letters, numerals, dashes ("-"), and
underscores ("_").
l The NE name and the virtual external IP address can be changed only after you delete the NE
and then add it again.
l To prepare multiple USB storage devices, you are advised to prepare and label the USB storage
devices one by one.
4. Double-click the added NE in the left pane. The window is refreshed, as shown in
Figure 4-5.

BSC6900 UMTS
Figure 4-5 Configuring information
NOTE
l The IP addresses shown in Figure 4-5 are default IP addresses of the Dopra Linux tool. Change
the IP addresses as required. For details about the principles of changing the IP addresses, see
3.2 OMU IP Address Plan.
l Select the link mode for external Ethernet adapters listed in Figure 4-5 as required. Ensure that
the link mode for external Ethernet adapters is consistent with that for the onsite LAN switch.
Table 4-3 lists the mapping between the queried link mode for external Ethernet adapters and
that selected in Figure 4-5.
l If Install OMU is not selected in Step 3, only the names of the active and standby OMUs and
IP addresses are displayed in Figure 4-5.
l In independent OMU mode, only the active OMU configuration is effective, whereas the standby
OMU configuration is ineffective.
Table 4-3 Mapping between link modes of external Ethernet adapters
Queried Link Mode of External Link Mode of External Ethernet

Ethernet Adapter Adapter to Be Selected
l Auto-negotiation is on. Auto
l Auto-negotiation is off. 10Mb Full

l Speed is 10Mb/s.
l Duplex is Full.

BSC6900 UMTS

l Auto-negotiation is off. 10Mb Half

l Speed is 10Mb/s.
l Duplex is Half.

l Speed is 100Mb/s.
l Duplex is Full.

l Speed is 100Mb/s.
l Duplex is Half.
5. After all the information is automatically obtained, check whether the information is
correct and enter any missing information.
NOTE
l If a version or baseline patch is to be installed, select the V**R**C** directory for the version
installation package or the V**R**C**SPCX00 directory for the baseline patch installation
package.
l If a non-baseline patch is to be installed, select the V**R**C**SPCXYZ or
V**R**C**SPHXYZ directory for the patch installation package.
6. Check that all the information is correct and click OK. In the displayed dialog box,
check the directory where the USB storage device is located and start preparing a USB
storage device.
7. Perform operations by following the instructions until the system displays a message
that reads Succeed to create USB drive of OMU installation. Click Finish to finish
preparing the USB storage device.
NOTE
l If the system asks for your confirmation during preparation of the USB storage device, insert or
remove the USB storage device.
l If an independent OMU is configured, skip the steps for preparing the standby OMU USB storage
device.
l Preparing the USB storage device for restoring the OMU operating system
1. Double-click U_creator_eng.exe to begin installing a Dopra Linux operating system
on the USB storage device, as shown in Figure 4-3.
2. Right-click NE List in the left pane of the window shown in Figure 4-3 and choose
Add NE. A dialog box is displayed, as shown in Figure 4-6.

BSC6900 UMTS
3. Specify NE Name, and set Operate type to Restore. Then click OK. An NE is added.
NOTE
l The NE name, used to identify an NE, can include only letters, numerals, dashes ("-"), and
underscores ("_").
l An NE name can be changed only after you delete the NE and then add it again.
l To prepare multiple USB storage devices, you are advised to prepare and label the USB storage
devices one by one.
4. Double-click the added NE in the left pane. The window is refreshed, as shown in
Figure 4-7.

BSC6900 UMTS
Figure 4-7 Configuration information
NOTE
l The IP addresses shown in Figure 4-7 are default IP addresses of the Dopra Linux tool. Change
the IP addresses as required. For details about the principles of changing the IP addresses, see
3.2 OMU IP Address Plan.
l Select the link mode for external Ethernet adapters listed in Figure 4-7 as required. Ensure that
the link mode for external Ethernet adapters is consistent with that for the onsite LAN switch.
l In independent OMU mode, only the active OMU configuration is effective, whereas the standby
OMU configuration is ineffective.
5. After all the information is automatically obtained, check whether the information is
correct and type the required information.
6. Check that all the information is correct and click OK. In the displayed dialog box,
check that the directory where the USB storage device is located and start preparing
a USB storage device.
7. Perform operations by following the instructions till the system displays a message
that reads Succeed to create USB drive of OMU installation. Click Finish to finish
preparing the USB storage device.
NOTE
l If the system asks for your confirmation during preparation of the USB storage device, insert or
remove the USB storage device.
l If an independent OMU is configured, skip the steps for preparing the standby OMU USB storage
device.
----End
Installing the OMU Operating System Using a USB Flash Drive

This section describes how to use a USB flash drive to install or restore the OMU operating
system.

BSC6900 UMTS
Prerequisites
l The USB flash drive is prepared. For details, see Preparing a USB Storage Device.
l There are USB ports available on the OMU board panel.
NOTE
The USB flash drive with an indicator is inserted into the USB port. If the indicator is on, then the USB
port is available.
Procedure
Step 1 Insert the USB flash drive into any of the USB ports on the OMUa or OMUc board panel.
Step 2 Remove and then reinstall the OMUa or OMUc board to reset the OMU.
NOTE
Press and hold the two locking buttons, flip the ejector levers out on the OMU board panel to unlock them,
and rotate them outward. The OMU board is separated from the backplane. Remove the OMU board after
the OFFLINE LED flashes fast and then is steady blue.
Step 3 Wait 1 to 2 minutes and then use the USB flash drive to install the OMU operating system. Check
the status of indicators on the OMU board panel to determine whether the OMU operating system
is installed successfully.
l If only the operating system is to be installed on the OMU, check the indicator status. See
Table 4-4.
l If the OMU operating system is to be restored, check the indicator status. See Table 4-5.
l If the operating system and applications are to be installed on the OMU, check the indicator
status. See Table 4-6.
NOTE
If the status of the indicators differs from this, the OMU cannot identify the USB flash drive. When this occurs,
prepare another USB flash drive. Alternatively, copy the data in the original USB flash drive to a new USB flash
drive, and then reinstall the OMU operating system.
For information about how much time will be consumed during the OMU operating system installation, see
Table 4-2 in Preparing a USB Storage Device.

BSC6900 UMTS
Table 4-4 Status of the indicators on the OMUa or OMUc board panel during the OMU operating
system installation
Board Installation Procedure Successful Failed Installation
Installation
OMUa At the beginning: l The RUN indicator l The RUN indicator is

l The RUN indicator blinks. off.
blinks. l The ALM indicator is l The ALM indicator
l The ALM indicator off or blinks. blinks.
blinks. l The ACT indicator is l The ACT indicator is
l The ACT indicator off. off.
blinks. l The OFFLINE l The OFFLINE
l The OFFLINE indicator is off. indicator blinks.
indicator is off.
After a certain period:
l The RUN indicator
blinks.
l The ALM indicator is
off.
l The ACT indicator is
off.
l The OFFLINE
indicator blinks.
OMUc l The RUN indicator l The RUN indicator l The RUN indicator is
blinks. blinks. off.
l The ALM indicator l The ALM indicator is l The ALM indicator
blinks. off. blinks.
l The ACT indicator l The ACT indicator is l The ACT indicator is
blinks. off. off.
l The OFFLINE l The OFFLINE l The OFFLINE
indicator is off. indicator blinks. indicator blinks.

BSC6900 UMTS
Table 4-5 Status of the indicators on the OMUa or OMUc board panel during the OMU operating
system restore
Installation
OMUa At the beginning: l The RUN indicator l The RUN indicator

l The RUN indicator blinks. blinks.
l The ALM indicator steady on or off. blinks.
l The ACT indicator steady on or off. off.
l The OFFLINE indicator is off. indicator is off.
indicator blinks.
l The RUN indicator
blinks.
l The ALM indicator
blinks.
off.
l The OFFLINE
indicator is off.
OMUc l The RUN indicator l The RUN indicator l The RUN indicator
blinks. blinks. blinks.
blinks. steady on or off. blinks.
blinks. steady on or off. off.
indicator blinks. indicator is off. indicator is off.

BSC6900 UMTS
Table 4-6 Status of indicators on the OMUa or OMUc board panel during the OMU operating
system and OMU applications installation
Installation
OMUa At the beginning: l The RUN indicator l The RUN indicator

l The RUN indicator blinks. blinks.
l The ALM indicator steady on or off. blinks.
l The ACT indicator steady on or off. off.
l The OFFLINE indicator is off. indicator is off.
indicator is off.
l The RUN indicator
blinks.
l The ALM indicator is
off.
off.
l The OFFLINE
indicator blinks.
OMUc l The RUN indicator l The RUN indicator l The RUN indicator
blinks. blinks. blinks.
blinks. steady on or off. blinks.
blinks. steady on or off. off.
indicator is off. indicator is off. indicator is off.

BSC6900 UMTS
CAUTION
l After the OMU operating system is installed successfully, remove the USB flash drive from
the OMU board panel in a timely manner.
l After the OMU operating system is restored using a USB flash drive, the password changes
to the default value.
l If the version of the OMU operating system is V200R003C02SPC090 or later, log in to
the active OMU as the lgnusr user, for whom the initial password is osnormal@123. Do
not log in to the OMU as the root user. After the login succeeds, you can run the su
command to switch to the root user, for whom the initial password is osadmin@123.
l If the version of the OMU operating system is earlier than V200R003C02SPC090, log in
to the active OMU as the root user, for whom the initial password is mbsc@com.
l If you do not know the version of the OMU operating system, try to log in to the active
OMU first as the lgnusr user and then the root user.
----End
Follow-up Procedure
If the OMU operating system fails to be installed, perform the following operations:
1. Prepare a new USB flash drive. For details, see Preparing a USB Storage Device. Then,
reinstall the OMU operating system again.
l If the OMU operating system is installed successfully, no further action is required.
l If the OMU operating system fails to be installed, Contact Huawei Customer Service
Center.
If you use the USB flash drive to restore the OMU operating system, check whether you should
implement the following operations:
l After the OMU operating system is restored, the setting on the original operating system
will become ineffective for the functions of disabling root user remote login. Enable the
function by referring to 6.1 Disabling root user login with SSH.
4.2.3 Optional: Installing the OMU Applications

If OMU applications cannot work properly during maintenance, use the OMU applications
installation file in the version package.
Context
l When reinstalling the OMU applications, re-import the OMU configuration data. You must
back up the OMU data before reinstalling the OMU applications and restore the OMU data
after the installation. For details, see Backing Up the System Data and Restoring System
Data.
l If the OMU data cannot be backed up because the OMU applications cannot work properly,
obtain the latest backup data for restoration.
l When installing the OMU applications for the first time, the OMU applications can be
installed only on the active workspace of the OMU, and the OMU data does not need to be
backed up.

BSC6900 UMTS
NOTE
This section uses the version installation package named V900R014C00 as an example to illustrate how to install
the OMU applications.
Obtaining Information About OMU Software Installation

Before installing the OMU applications, you should obtain the password for the administrator
of the OMU operating system and the IP address of the Ethernet adapter teams.
Procedure
Step 1 Before you install the OMU applications, obtain the following information. For details, see 4.5.1
Information Record Sheet of OMU Software Installation.
l Password of the operating system administrator
l Fixed IP address of the external network, virtual IP address of the external network, and
commissioning IP address of the OMU.
----End
Logging In to the OMU

You can run the Secure Shell (SSH) terminal, for example, the PuTTY software, to log in to the
OMU and perform operation and maintenance (OM) on the OMU.
Prerequisites
The PC to be used to log in to the OMU is properly connected.
Procedure
Step 1 Run the SSH terminal, for example, PuTTY, on the PC, and type the IP address of the OMU.
NOTE
l Before starting OMU applications, type the fixed external IP address of the OMU.
l After the OMU applications start, type the fixed or virtual external IP address. The former is preferred.
l If you are performing local commissioning, type the commissioning IP address of the OMU.
l If the PC cannot be connected to the OMU by using either the fixed or virtual external IP address,
connect the PC to the commissioning Ethernet port on the OMU and type the commissioning IP address
of the OMU.
l You are advised to log in to the OMU using the external fixed IP address, external virtual IP
address, and commissioning IP address in sequence.
Step 2 Log in to the OMU as the root user, lgnusr user, or common user.

BSC6900 UMTS
NOTE
l If the login fails, check whether the Disabling user root remote login function is enabled. If the function
is enabled, log in to the OMU as a common user. For details, see 6.1 Disabling root user login with
SSH.
l Run the LST VER command to query the OMU operating system version and log in to the OMU by using
the corresponding password. For details, see 4.5.2 Checklist for the OMU Software Factory Settings.
l It is recommended that you change the root user password upon your first login and change the password
every three months. If the version of the OMU operating system is
Doprax86DopraLinuxV200R003C02SPC080, change the root user password every 30 days. To query the
OMU operating system version, run the LST VER command.
l If you enter the password incorrectly for three times when logging in to the OMU, the operating system will
be automatically locked for 5 minutes and then unlocked. When the operating system is locked, do not log
in to the OMU.
Step 3 For a common user or lgnusr user, enter su and press Enter. Then, enter the root user password
to switch to a root user account.
----End
Example
The following shows an example of logging in to the OMU as the root user.
login as: root

You are trying to access a restricted zone. Only Authorized Users allowed.
Using keyboard-interactive authentication.
Password:
Last login: Fri Jul 13 12:14:11 2012 from 10.142.36.219
Hello! Welcome to DOPRALINUX!
omud215 ~ #
The following shows an example of logging in to the OMU as the lgnusr user. The same is for
a common user.
login as: lgnusr

Using keyboard-interactive authentication.
Password:
Last login: Mon Feb 4 09:58:11 2013 from 10.142.36.219
Hello! Welcome to DOPRALINUX!
omu ~ $ su
Password:
omu /home/lgnusr #
Uploading the OMU Application Installation Package to the OMU

Before installing the OMU applications, upload the OMU application package to the specified
directory of the OMU.
Prerequisites
l Contact Huawei engineers who can obtain the tool by performing the following operation:
You have obtained the OMU application installation package including the patch
installation package by accessing http://support.huawei.com/support/ and choosing

BSC6900 UMTS
Software Center > Version Software > Wireless Product Line > Single RAN >
MBSC > BSC6900.
l The psftp has been obtained. For details about the psftp, see 4.4.1 psftp Software.
Context
l The OMU application installation package must be uploaded to the \mbsc\upgrade
directory of the OMU.
l The OMU application installation package must be named after the version number. That
is, after the OMU application installation package is uploaded to the OMU, the directory
of the installation package on OMU is "\mbsc\upgrade\V900R014C00."
l If patches also need to be installed, you must check whether the original patch files exist
in the patch folder in the OMU application installation package before installing the OMU
application. If yes, you must delete the original patch files in the patch folder in the OMU
application installation package and copy the patch installation package (for example, the
V900R01XC0XSPCXXX folder) saved on the local computer.
NOTE
If you need to delete the patch files V900R01XC0XSPCXXX in the patch directory, navigate to the
\mbsc\upgrade\V900R015C00\patch directory and then run rm -r \V900R01XC0XSPCXXX.
l During the uploading process, if the root user cannot log in to the OMU, check with the
equipment room operators to determine whether the 6.1 Disabling root user login with
SSH function has been enabled on the BSC6900. If so, you must log in to the OMU as a
common user, and then continue with the uploading task.
NOTE
As an example, this task uploads the V900R014C00 version installation package to the \mbsc\upgrade directory
of the OMU and downloads version files from http://support.huawei.com/support/ to local drive D.
Procedure
l Logging in to the OMU as a root user and uploading the OMU application installation
package to the OMU
1. Decompress the BSC6900 version installation package to the local D drive.
2. Log in to the OMU as the root user by using the psftp. For details, see 4.4.1 psftp
Software.
3. Run the lcd D:\ command to go to the directory on the local PC where the version
files are saved.
4. Run the ls /mbsc/upgrade command to query whether there is an installation directory
on the OMU.
If the /mbsc/upgrade directory does not exist, go to Step 5.
If the /mbsc/upgrade directory exists, go to Step 6.
5. Run the mkdir /mbsc/upgrade command to create the installation directory on the
OMU.
NOTE
Run the commands mkdir /mbsc and mkdir /mbsc/upgrade in sequence to create the /mbsc/
upgrade directory hierarchically.
6. Run the cd /mbsc/upgrade command to go to the OMU installation directory.
7. Run the put -r V900R014C00 command to upload the OMU application installation
package to the OMU.

BSC6900 UMTS
NOTE
If the package fails to be uploaded, check whether any file with the same name as the package name
is in use. If there is such a file, release it.
8. After the upload is complete, type the exit command to exist the psftp software.
l Logging in to the OMU as a non-root user and uploading the OMU application installation
package to the OMU
1. Log in to the OMU as a common user and switch to the root user account. For details,
see Logging In to the OMU.
2. Enter the path=`grep xxx /etc/passwd | cut -d:-f 6`; if [ !-d $path ] ; then mkdir -
p $path; chown xxx $path; fi command and press Enter to establish a non-root user
information file directory.
NOTE
In the command above, xxx indicates the name of a non-root user.

3. Enter the cat /etc/passwd command and press Enter to query all the non-root user
file directories.
NOTE
If the queried result is omcuser:x:1001:100::/home/omcuser:/bin/bash, then the user files

directory for omcuser is /home/omcuser. In later operations, the /home/omcuser directory of the
non-root user omcuser is used as an example.
4. Enter the exit command and press Enter to log out of PuTTY.
5. Decompress the BSC6900 version installation package to the local drive D.
6. Log in to the OMU as a non-root user by using the psftp software.
7. Enter the lcd D:\ command and press Enter to log in to the local directory for version
files.
8. Enter the cd /home/omcuser command and press Enter to go to the user file directory
of the non-root user omcuser.
9. Enter the put -r V900R014C00 command and press Enter to upload the OMU
application installation package to the OMU.
10. After the uploading is complete, type the exit command and press Enter to exit the
psftp software.
11. Repeat Step 1 to log in to the OMU as a non-root user and switch the account from
non-root user to root user.
12. Enter the ls /mbsc/upgrade command and press Enter to query whether there is an
installation directory on the OMU.
13. Enter the mkdir /mbsc/upgrade command and press Enter to create an installation
directory on the OMU.
NOTE
14. Enter the cp /home/omcuser/V900R014C00 -r /mbsc/upgrade/ command and copy
the version installation package under the /home/omcuser directory to the OMU
installation directory.
15. Enter the exit command and press Enter to log out of PuTTY.

BSC6900 UMTS
l Log in to the OMU as the lgnusr user and upload the OMU application package to the
OMU.
1. Decompress the BSC6900 version installation package to a local drive D.
2. Log in to the OMU as the lgnusr user by using psftp.
3. Type the lcd D:\ command and press Enter to navigate to the local directory where
version files are saved.
4. Type the cd /home/lgnusr command and press Enter to switch to the directory of the
lgnusr user.
NOTE
The default direcotry of the lgnusr user is /home/lgnusr. The lgnusr user has the read/write
permissions to this directory.
5. Type the put -r commandV900R014C00 and press Enter to upload files.
6. After files are uploaded, enter exit and press Enter to exit psftp.
7. Log in to the OMU as the lgnusr user and switch to the root user account. For details,
see Logging In to the OMU.
8. Type ls /mbsc/upgrade command and press Enter to query whether there is the /
mbsc/upgrade directory on the OMU.
9. Type the mkdir /mbsc/upgrade command and press Enter to set up an installation
directory on the OMU.
NOTE
10. Run the cp /home/lgnusr/V900R014C00-r /mbsc/upgrade/ command to copy the
intallation package under the /home/lgnusr directory to the OMU installation
directory.
11. Enter exit and press Enter to exit PuTTY.
----End
Installing the OMU Applications in the Active Workspace

This section describes how to install the OMU applications in the active workspace. If the
BSC6900 is configured with two OMU boards, install the OMU applications in the active
workspace of each individual board.
Prerequisites
l Obtained information about OMU software installation.
l Uploaded the OMU application installation package to the OMU.
Context
Run a command to install the install_bam program contained in the BSC6900 version installation
package. Enter the related parameters during the process.

BSC6900 UMTS
If OMU applications have been pre-installed on active and standby OMU boards, unintall them
before installing the OMU applications of a correct version. To check whether OMU applications
have been pre-installed, do as follows:
1. Log in to the OMU by using the fixed external IP address or commissioning IP address.
For details, see Logging In to the OMU.
2. Enter the cd /etc/rc.d/ command and press Enter to go to the current directory.
3. Enter the ls command and press Enter to check files in the current directory.
l If the omud file is in the directory, OMU applications have been pre-installed. Uninstall
them by following operation steps in Uninstalling the OMU Applications.
l If the omud is not in the directory, OMU applications have not been pre-installed. Install
the OMU applications following the installation procedures.
4. Enter the exit command to close PuTTY.
Procedure
Step 1 Log in to the OMU by using the external fixed IP address or commissioning IP address by
referring to Logging In to the OMU, then navigate to the directory where the OMU application
installation package is saved.
Assume that the OMU application installation package install_bam.sh is saved in /mbsc/
upgrade/V***R***C**/install/setup. Run the following command and press Enter:
cd /mbsc/upgrade/V***R***C**/install/setup
Step 2 Run the chmod +x ./install_bam.sh command to acquire the authority to run the ./
install_bam.sh command.
Step 3 Enter the ./install_bam.sh command and press Enter. The system prompts you to type the
product mode, as shown:
[2011-05-03 10:12:32] software integrality verify begin...
[2011-05-03 10:12:42] software integrality verify end...
# The run mode of the product

# GO:GSM only
# UO:UMTS only
# GU:GSM and UMTS
# Please select one mode to install.
Please input a valid run_mode :
NOTE
The software integrity of the OMU applications is checked before they are automatically installed. The OMU
applications can be installed only if the check passes.
Step 4 Enter the product running mode and press Enter. The system prompts you to type the office
name, as shown:
# The name of office
# The name suggest range from 5 to 32 characters.
# The characters suggest be letters, digits, "-"or "_".
Please input a valid office_name :
Step 5 Enter the office name and press Enter. The system prompts you to type the language, as shown:
# The OMU language version. eg: eng/chs
Please input a valid version :
Step 6 Enter the language and press Enter. The system prompts you to type the admin password, as
shown:
# The "admin" user's password of OMU service.
# The password must range from 6 to 32 characters and consist of only letters and

BSC6900 UMTS
figures.
# Do not forget the password.
# You can change the password later, but this password should be provided first.
Please input a valid admin_password :
NOTE
The admin password is the initial password for the administrator to log in to the LMT.
Step 7 Enter the admin password and press Enter. The system prompts you to type the FTP password,
as shown:
# The ftp user's password of OMU service
# The password must range from 6 to 32(characters) and consist of only letters and
figures.
# You can change it later, but this password should be provided first.
Please input a valid ftp_password :
NOTE
The FTP password is customized. After the OMU applications are installed, you can access the FTP service
with the FTP password.
Step 8 Enter the FTP password and press Enter. The system prompts you to type the external virtual
IP address, as shown:
# The extranet IP address, subnet mask, and default gateway.

# example: 192.168.1.9/255.255.255.0;192.168.1.1
Please input a valid virtual_extranet_config :
NOTE
The external virtual IP address must be located on the same network segment as the external fixed IP
address. The factory setting of the external fixed IP address is 172.121.139.201 (255.255.255.0). After the
OMU applications are installed, you can change the IP addresses and subnet masks of the OMU Ethernet
adapters
Step 9 Enter the external virtual IP address and press Enter. The system prompts you to type the OMU
system type, as shown:
# The OMU system type. eg: Single/Dual
# Single:Install stand-alone system
# Dual:Install dual-OMU system.
The dual-OMU system can effeciently increase the reliability of the OMU system.
Please input a valid install_type :
Step 10 Enter the OMU installation type based on the field configuration and press Enter. Table 4-7
describes the OMU installation types.
Table 4-7 Description
Parameter Description
Single When the BSC6900 is configured with one

OMU board, install the OMU applications on
the board in single-OMU mode.
Dual When the BSC6900 is configured with two

OMU boards, install OMU applications on
the board in dual-OMU mode.
Step 11 The system asks you whether to continue with the installation, as shown:
Please affirm input information. input Y to continue; input E to exit. ->

BSC6900 UMTS
Step 12 Enter Y to install the OMU applications. When the messageInstall OMU succeed! is
displayed, the OMU applications are successfully installed.
Step 13 Record the information about the OMU applications installation in 4.5.1 Information Record
Sheet of OMU Software Installation.
----End
Checking the Installation Directory of OMU Applications

By default, the installation directory for OMU applications is /mbsc/bam. The OMU application
components, BSC6900 host software, and data used or generated by the BSC6900 are stored in
this directory.
Background
The default installation directory for the OMU applications is /mbsc/bam/. You are not allowed
to change the directory.
Procedure
1. Log in to the OMU by referring to Logging In to the OMU.
2. Type the cd /mbsc/bam command and press Enter to go to the OMU installation directory.
3. Check whether the OMU installation directory is in the same structure as what is shown in
Figure 4-8 and Figure 4-9.
Directory Structure
l Figure 4-8 shows the directory structure of the OMU applications when they are installed
in the active OMU workspace for the first time.
l If the OMU applications are installed on both the active workspace and the standby
workspace, the directory structure is the same as that shown in Figure 4-9. The structures
of the version_a and version_b folders are the same.
NOTE
l Active and standby OMU workspace files are segregated by type into version_a and version_b folders.
l Run the LST OMUAREA command to query the OMU workspaces. If the Workarea flag is
version_a, the version_a folder saves active workspace files.
l Figure 4-8 and Figure 4-9 show the directory structure of the OMU applications.

BSC6900 UMTS
Figure 4-8 Directory structure of OMU applications on the active workspace
Figure 4-9 Directory structure of OMU applications on the active and standby workspaces
CAUTION
To prevent a critical impact to the BSC6900, do not delete any files in the installation directory
of the OMU applications.

BSC6900 UMTS
File Folders
Table 4-8 lists the file folders in the OMU application directory.
Table 4-8 File folders in the OMU application directory
File Folder Description
common/bts Stores BTS board software (including patches), BTS

inventory information, BTS logs, and BTS RET antenna
software
common/ems Stores the M2000-related data
common/fam Stores host log files and host files for performance statistics
common/fam/fad Stores the last word of the host
common/fam/famlog Stores host log files which record platform-related

information. Users can open the files to view the
information.
common/fam/famlogfmt Stores binary logs of the host
common/fam/famlogfmt/ Stores files that record basic information about the BTS
btsinfo
common/fam/famlogfmt/ Stores basic information and logs about abnormal calls

gchr
common/fam/famlogfmt/ Stores the call history record (CHR) for the packet switched
gphr (PS) domain.
common/fam/famlogfmt/ Stores files recording detailed information about each call

pchr for KPI analysis. The information includes service access,
call release, handover, and signal qualities.
common/fam/famlogfmt/ Stores information about severe hardware and software

sysfault faults, such as system fault contents, resource leakage, and
equipment failure. This information is used for network
health check.
common/fam/famlogfmt/ Stores tracing files of VIP subscribers

viptrace
common/fam/mr Stores AMR measurement files
common/fam/pfm Stores traffic statistics reported by an NE to the M2000
common/fam/smlc Stores files about the location function
common/fam/ibst_file Stores tracing files recording the TC management

information in the GSM network
common/fam/trace Stores message tracing files
common/log Stores logs of the omud, common logs of the base station,
frequency scanning logs, and site commissioning logs

BSC6900 UMTS
common/services Stores the common programs of the active and standby

OMU workspaces
common/weblmt_cfg Stores the configuration files for LMT
common/MeasResult Stores performance measurement result files
common/reg.ini Stores register files
version_a/bin/bam Stores the program files, configuration files, and patch files
for the OMU. Do not perform any operations on this
directory.
version_a/bin/fam Stores the program files and data files for the host. Do not
perform any operations on this directory.
version_a/data/backup Stores backup files of the OMU database
version_a/data/backup/ Stores configuration data in MML format backed up by the

data_backup/mml host
version_a/data/backup/ Stores the configuration data downloaded from the M2000

data_restore/db_data in DB format for restoration
version_a/data/backup/ Stores the configuration data downloaded from the M2000

data_restore/mml in MML format for restoration
version_a/ftp/bts_upgrade Stores BTS upgrade files
version_a/ftp/cert Stores digital certificates the BSC received from the

network management system
version_a/ftp/ Stores log collection results

COLLOGINFO
version_a/ftp/crashfile Stores OMU breakdown logs and dump files generated

when OMU modules are faulty
version_a/ftp/DefaultMeas Stores the performance measurement task file in use
version_a/ftp/ Stores files about performance synchronization tasks

DefaultMeasSync
version_a/ftp/device_file Stores the hardware archives exported from the host
version_a/ftp/e_label Stores electrical label files exported from the host
version_a/ftp/ExportBCPFile Stores exported BCP files
version_a/ftp/ Stores files about the "configure" process. These files are
ExportCMESyncView used for the synchronization between the NE and the CME
or M2000
version_a/ftp/export_cfgmml Stores exported MML scripts
version_a/ftp/license Stores the license files that have not been activated

BSC6900 UMTS
version_a/ftp/MeasDefinition Stores the performance measurement task files and

measurement definition files in multi-mode
version_a/ftp/licusage Stores files about license usage recorded within 24 hours.

These files are used for analyzing reports reported by the
M2000
version_a/ftp/oprator_log Stores operation log files and security log files of the
standby OMU
version_a/license Stores the activated license files
version_a/log Stores the operation logs of the OMU
version_a/security_file Stores the configuration file of the antivirus software and

the backup configuration file for system recovery
weblmt Stores host files and files recording LMT online help
associated with the LMT
upgrade Stores the software package of the version to be upgraded
upgrade/log Stores upgrade log files
upgrade/os_patch Stores operating system patch files
Logging Out of the OMU

This section describes how to log out of the OMU after you have finished operating and
maintaining the OMU through PuTTY.
Prerequisites
You have logged in to the OMU by referring to Logging In to the OMU.
Procedure
Step 1 Run the exit command to terminate the PuTTY software.
----End
4.3 Operating and Maintaining the OMU

commands.
4.3.1 Querying the Mapping Between Ethernet Adapters

This section describes the mapping between the physical and logical Ethernet adapters.

BSC6900 UMTS
Prerequisites
The OMU applications are installed. For details, see Installing the OMU Applications in the
Active Workspace.
Procedure
Step 1 Log in to the OMU by referring to Logging In to the OMU.
Step 2 Optional: To query the factory settings of the Ethernet adapters of the OMUa board, type the /
root/eth_alias_omu.sh command and press Enter. The following shows the factory settings of
the Ethernet adapters of the OMUa board.
eth0 06,0,0 ETH4-SCU7

eth1 06,0,1 ETH5-SCU6
eth2 04,4,0 ETH2
eth3 04,4,1 ETH3-UPDATE
eth4 08,4,0 ETH0
eth5 08,4,1 ETH1
Step 3 Optional: To query the factory settings of the Ethernet adapters of the OMUc board, type
the ./eth_alias_names.sh command and press Enter. The following shows the factory settings
of the Ethernet adapters of the OMUc board.
eth0 02,0,0 F_ETH0

eth1 01,0,0 F_ETH1
eth2 07,0,0 F_DBG
eth3 05,0,0 B_UPDATE0
eth4 06,0,0 B_UPDATE1
eth5 03,0,0 B_ETH0
eth6 03,0,1 B_ETH1
NOTE
The three columns in the figure for the configuration of OMU Ethernet adapters contain the following
information:
l The first column lists the logical OMU Ethernet adapters for software identification.
l The second column lists the Peripheral Component Identity (PCI) of the Ethernet adapters for hardware
identification.
l The third column lists the physical OMU Ethernet adapters for human identification.
The mapping between the second and third columns cannot be changed. The mapping between the first
and second columns and the mapping between the first and third columns depend on the configuration of
the OMU.
----End
4.3.2 Querying the Configuration of the OMU Ethernet Adapters

This section describes how to query the configuration information of the OMU Ethernet adapters.
The information includes IP addresses, their subnet masks, and broadcast IP addresses.
Procedure
l Method 1
1. Log in to the target OMU by referring to Logging In to the OMU.
2. Enter the /etc/rc.d/omud stop command and press Enter to stop the omud..
3. Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the
directory where the omutool program is saved..

BSC6900 UMTS
NOTE
version_a as the main workspace of the OMU is used as an example.

4. Enter the ./omutool dispipinfo command and press Enter. The following shows an
example of the returned information.
[Virtual IP Information]
External virtual ip / mask : 10.141.149.15 / 255.255.254.0
Internal virtual ip / mask : 80.168.3.40 / 255.0.0.0
[Fixed IP Information]
External fixed ip / mask : 10.141.149.14 / 255.255.254.0
Internal fixed ip / mask : 80.168.3.60 / 255.0.0.0
Backup channel ip / mask : 192.168.3.60 / 255.255.255.0
Debugging ip / mask : 192.168.6.60 / 255.255.255.0
[Gateway Information]
Gateway : 10.141.148.1
l Method 2
2. Optional: To query the fixed internal IP address, broadcast IP address, and subnet
mask of the OMUa board, type the ifconfig vlan1 command and press Enter. The
following shows an example of the returned information.
vlan1 Link encap:Ethernet HWaddr 00:18:82:68:4D:0E

inet addr:80.168.3.60 Bcast:80.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::218:82ff:fe68:4d0e/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:638957 errors:0 dropped:0 overruns:0 frame:0
TX packets:256271 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:705095569 (672.4 Mb) TX bytes:16423247 (15.6 Mb)
NOTE
To query the OMU IP addresses and subnet masks, do as follows:

l Run the ifconfig bond1 command to query the fixed external IP address, its subnet mask, and
broadcast IP address. If the fixed external IP address is not configured, the virtual external IP
address, its subnet mask, and broadcast IP address are queried.
l Run the ifconfig bond1:0 command to query the virtual external IP address, its subnet mask,
and broadcast IP address. If the fixed external IP address is not configured, the query result does
not contain IP addresses.
l Run the ifconfig vlan1 command to query the fixed internal IP address, its subnet mask, and
broadcast IP address.
l Run the ifconfig vlan1:0 command to query the internal virtual IP address, its subnet mask, and
l Run the ifconfig bond2 command to query the commissioning IP address, its subnet mask, and
l Run the ifconfig bond3 command to query the IP address of the backup channel between the
active and standby OMUa boards, the subnet mask of that IP address, and broadcast IP address.
3. Optional: To query the fixed internal IP address, its subnet mask, and broadcast IP
address of the OMUc board, type the ifconfig vlan1 command and press Enter. The
vlan1 Link encap:Ethernet HWaddr 00:18:82:68:4D:0E

inet addr:80.168.3.60 Bcast:80.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::218:82ff:fe68:4d0e/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:638957 errors:0 dropped:0 overruns:0 frame:0
TX packets:256271 errors:0 dropped:0 overruns:0 carrier:0

BSC6900 UMTS
collisions:0 txqueuelen:0
RX bytes:705095569 (672.4 Mb) TX bytes:16423247 (15.6 Mb)
NOTE
To query the OMU IP addresses and subnet masks, do as follows:

l Run the ifconfig bond1 command to query the fixed external IP address, its subnet mask, and
broadcast IP address. If the fixed external IP address is not configured, the virtual external IP
address, its subnet mask, and broadcast IP address are queried.
l Run the ifconfig bond1:0 command to query the virtual external IP address, its subnet mask,
and broadcast IP address. If the fixed external IP address is not configured, the query result does
not contain IP addresses.
l Run the ifconfig vlan1 command to query the fixed internal IP address, its subnet mask, and
l Run the ifconfig vlan1:0 command to query the internal virtual IP address, its subnet mask, and
l Run the ifconfig bond2 command to query the commissioning IP address, its subnet mask, and
l Run the ifconfig bond3 command to query the IP address of the channel between the active and
standby OMUc boards, its subnet mask, and broadcast IP address.
l Run the ifconfig bond4 command to query the IP address of the channel between the OMUc
board and OMUa board, its subnet mask, and broadcast IP address.
----End

This section describes how to query occupied OMU ports.
Procedure
Step 2 Enter the netstat -tuan command and press Enter to query the occupied OMU ports. The
omu_136 ~ # netstat -tuan

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 10.0.0.1:8000 0.0.0.0:* LISTEN
tcp 0 0 10.0.0.1:8001 0.0.0.0:* LISTEN
tcp 0 0 10.0.0.1:16002 0.0.0.0:* LISTEN
tcp 0 0 10.0.0.1:16002 0.0.0.0:* LISTEN
tcp 0 0 10.0.0.1:8099 0.0.0.0:* LISTEN
tcp 0 0 10.0.0.1:8100 0.0.0.0:* LISTEN
tcp 0 0 10.0.0.1:8006 0.0.0.0:* LISTEN
tcp 0 0 10.0.0.1:8200 0.0.0.0:* LISTEN
Information to the right of colon in the Local Address column indicates the occupied OMU port
numbers.
----End
4.3.4 Querying the Link Mode of the External OMU Network

Adapters
This section describes how to query the link mode of the external OMU network adapters: duplex
mode and adaptive mode.

BSC6900 UMTS
Procedure
Step 1 Logging In to the OMU.
Step 2 Query the logical network adapters corresponding to the external OMU network adapters, as
listed in Table 4-9.
Table 4-9 Querying the logical network adapters corresponding to the external OMU network
adapters
Item Description
OMUa/OMUb Board Type /root/eth_alias_omu.sh and press

Enter.
OMUc Board Run the chmod +x ./eth_alias_names.sh

command to obtain the permission to run the ./
eth_alias_names.sh command. Type ./
eth_alias_names.sh and press Enter.
NOTE
l The OMUa or OMUb external network adapters are ETH0 and ETH1, respectively. The OMUc external
network adapters are F_ETH0 and F_ETH1, respectively. The objects of this task are the logical
network adapters corresponding to the external OMU network adapters.
l Mapping between physical OMU network adapters and logical network adapters can change. In normal
cases, the logical network adapters corresponding to the external OMUa or OMUb network adapters
are eth4 and eth5, respectively; the logical network adapters corresponding to the external OMUc
network adapters are eth0 and eth1, respectively.
Step 3 Query the effective link mode of the external OMU network adapters. Run the ethtool eth0
command to query the link mode of eth0. Run the ethtool eth1 command to query eth1.
NOTE
l Check Speed, Duplex, and Auto-negotiation. Speed, Duplex, and Auto-negotiation indicate the rate,
duplex mode, and auto-negotiation mode, respectively.
l The following example assumes that the logical network adapters corresponding to the external OMU
network adapters are eth0 and eth1, respectively. The command output is as follows:
Settings for eth0:

Supported ports: [ FIBRE ]
Supported link modes: 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: external
Auto-negotiation: on
Supports Wake-on: pumbag
Wake-on: g
Current message level: 0x00000001 (1)
Link detected: yes
----End

BSC6900 UMTS
4.3.5 Checking the Version of the Operating System

This section describes how to check whether the version of the operating system on the OMUa
board is correct.
Prerequisites
You have logged in to the LMT. For details, see Logging In to and Logging Out of the LMT.
Procedure
Step 1 Run the MML command LST VER to check whether OS type and OS service pack version
are correct.
----End
4.3.6 Changing the Administrator Password of the Operating

System
This section describes how to change the password of the operating system administrator to
ensure that the administrator account is secure.
Context
l It is recommended that you change the root user password upon your first login and change
the password every three months. If the version of the OMU operating system is
Doprax86DopraLinuxV200R003C02SPC080, change the root user password every 30
days. To query the OMU operating system version, run the LST VER command.
l A root user password must contain the combination of the following:
At least one lower-case letter
At least one upper-case letter
At least one digit
At least one special character `~!@#$%^&*()-_=+\|[{}];:'",<.>/? or a space
The root user password must have a minimum length of 8 characters and maximum length
of 127 characters.
Procedure
Step 2 Run the passwd root command (for example, use root as an example). A message is displayed,
prompting you to type the password, as shown in the:
Changing password for root.
New password:
Step 3 Enter a password and press Enter. The message Retype password: is displayed.
Step 4 Retype the password and press Enter. The message Password changed is displayed, indicating
that the Linux administrator password is successfully changed.

BSC6900 UMTS
Step 5 Record the new password in the 4.5.1 Information Record Sheet of OMU Software
Installation.
----End
4.3.7 Setting RAID 1 on OMU Hard Disks

This section describes how to set RAID 1 on OMU hard disks to ensure data synchronization
between the source and target OMU hard disks.
Prerequisites
l The OMU is started normally.
l OMU serial cables are available. For details about the cable information, see OMU serial
cable in BSC6900 UMTS Hardware Description.
l The source and target hard disks are available.
Context
One OMU hard disk serves as the source hard disk, and the other serves as the target hard disk.
Setting RAID 1 on the hard disks synchronizes the data on the source and target hard disks,
improving data security.
l The source hard disk saves backup data and files.
l The target hard disk mirrors the source hard disk.
NOTE
RAID 1 cannot be set on an OMUc board because it is configured with one hard disk.
Procedure
Step 1 Connect the PC to the OMU serial port using the OMU serial port cable.
NOTE
If the OMU serial port cable is not available, the USB and VGA ports of the active OMU can be connected
to an external keyboard and monitor, respectively. Then starts from Step 6 to complete the configuration.
Step 2 On the PC, choose Start > All Programs > Accessories > Communications >
HyperTerminal. The dialog box shown in Figure 4-10 is displayed.

BSC6900 UMTS
Figure 4-10 Connection description
Step 3 Enter the connection name and click OK. The dialog box shown in Figure 4-11 is displayed.
Figure 4-11 Confirming the connection
Step 4 Check the connection port and click OK. The dialog box shown in Figure 4-12 is displayed.

BSC6900 UMTS
Figure 4-12 Setting attributes for the connection port
NOTE
The parameters for the connection port must be set as shown in Figure 4-12.
Step 5 Check that the parameters for the connection port are set correctly and click OK. The window
shown in Figure 4-13 is displayed.

BSC6900 UMTS
Figure 4-13 Connection established
Step 6 Restart the OMU.
Option Description
Windows Server 2003 operating system 1. Log in to the target OMU by referring to 5.2.20
Logging In to the OMU.
2. Choose Start > Shutdown, click Restart, and
click OK.
Step 7 After the OMU restarts, press F4 repeatedly until the message "Press Ctrl-C to start
LSI Logic Configuration Utility" is displayed. Then press Ctrl+C. The following
shows examples of the messages displayed.
Adapter PCI PCI PCI PCI FW Revision Status Boot

Bus Dev Fnc Slot Order
SAS1064 05 01 00 00 0.11.01-IR Enabled 0
Step 8 Press Enter. The following shows examples of the messages displayed.
Adapter SAS1064
PCI Slot 00
PCI Address(Bus/Dev/Func) 05:01:00
MPT Firmware Revision 0.11.01.00-IR
SAS Address 500E0FC1:23456775
NVDATA Version 25.09

BSC6900 UMTS
Status Enabled
Boot Order 0
Boot Support [Enabled Bios & OS]
RAID Properties
SAS Topology
Advanced Adapter Properties
Press the arrow keys to select RAID Properties and press Enter. Check the value of Status to
determine whether the RAID is correct.
l If Status is Optimal, the RAID is working properly.
l If Status is Resyncing, the RAID is synchronizing data.
NOTE
l If this is the first time that the RAID is being set on the OMU, go to Step 13.
l If this is not the first time that the RAID is being set on the OMU, go to Step 9.
Step 9 Select RAID Properties and press Enter. The following shows examples of the results that are
displayed.
Array 1 of 1
Identifier LSILOGICLogical Volume 3000
Type IM
Scan Order 2
Size(MB) 69618
Status Optimal
Manage Array
Slot Device Identifier RAID Hot Drive Pred Size
Num Disk Spr Status Fail (MB)
0 FUJITSU MAY2073rc D109 [Yes] [No] Primary --- 69618
1 FUJITSU MAY2073rc D109 [Yes] [No] Secondary --- 69618
Step 10 Select Manage Array and press Enter. The following shows examples of the results that are
displayed.

Type IM
Scan Order 2
Size(MB) 69618
Status Optimal
Manage Hot Spare
Synchronize Array
Activate Array
Delete Array
Step 11 Select Delete Array and press Enter. The following shows examples of the results that are
displayed.
Y Delete array and exit to Adapter Properties

N Abandon array detetion and exit this menu
Step 12 Select Y. The following shows examples of the results that are displayed.
Adapter SAS1064
PCI Slot 00
Status Enabled
Boot Order 0
RAID Properties

BSC6900 UMTS
SAS Topology
displayed.
Creat IM Volume Create Integrated Mirror Array of 2

disks plus an optional hot spare,Data
on the primary disk may be migrated.
Create IME Volume Create Integrated Mirrored Enhanced

Array of 3 to 8 disks including an
optional hot spare.
All DATA on array disks will be DELETED!
Create IS Volume Create Integrated Striping array of
2 to 8 disks.
ALL DATA on array disks will be DELETED!
Step 14 Select Create IM Volume and press Enter. The following shows examples of the results that
are displayed.
Array Type:IM
Array Size(MB): -------

0 FUJITSU MAY2073rc D109 [No] [No] ------ --- 70003
CAUTION
Select the source and target hard disks with caution because the data on the source hard disk can
be lost.
Step 15 Set RAID Disk to No, move the cursor to the value for RAID Disk of the source hard disk, and
press Space. The following show examples of the results that are displayed.
M - Keep existing data, migrate to an IM array.

Synchronization of disk will occur.
D - Overwrite existing data, create a new IM array
ALL DATA on ALL disks in the array will be DELETED!!
NO Synchronization performed.
l If you press M, the data on the source hard disk is saved. The target hard disk copies the data
from the source disk.
l If you press D, the data is deleted from the source hard disk and a new RAID is created.
Step 16 Press M or D to return to the messages shown in Step 14.
The value for RAID Disk is Yes, and the value for Drive Status is Primary.
Step 17 Select the target hard disk and press Space. An alarm is generated, as shown in the following:
WARNING! Data was found on the selected disk,this data will be lost when the array
is created!
Choose Discard configuration or Cancel Exit on the next screen to abort.
Step 18 Press C to return to the messages shown in Step 14.
The value for RAID Disk is Yes, and the value for Drive Status is Secondary.

BSC6900 UMTS
Step 19 Press C. The following shows the results that are displayed.
Create and save new array?

Cancel Exit
Save changes then exit this menu
Discard changes then exit this menu
Exit the Configuration Utility and Reboot
Step 20 Select Save changes then exit this menu and press Enter. The screen is refreshed, as shown
in Step 12.
Step 21 Select RAID Properties shown in Step 12 and press Enter. The following shows examples of
the results that are displayed.
Array 1 of 1
Type 1M
Scan Order 0
Size(MB) 69618
Status 2% Syncd
Manager Array
Step 22 Check that the RAID 1 is set correctly, and then press Esc repeatedly until the following
messages are displayed:
Are you sure you want to exit?

Cancel Exit.
Save changes and reboot.
Discard changes and reboot.
Exit the Configuration Utility and Reboot.
Step 23 Select Exit the Configuration Utility and Reboot and press Enter. RAID 1 is successfully set
on the OMU hard disks and the OMU restarts.
----End
4.3.8 Maintaining the OMU Routinely

This section describes how to remotely check and clean up the OMU hard disk and transfer files
from the OMU to the LMT PC on a regular basis to ensure that the OMU is working normally.
Regularly Checking and Cleaning Up the OMU Hard Disk

This section describes how to regularly check and clean up the OMU hard disk to ensure that at
least 20% space is available in each partition on the OMU hard disk.
Prerequisites
Procedure
Step 1 Run the MML command DSP OMUSRV to query the available space of the partitions on the
OMU hard disk.

BSC6900 UMTS
l If the available space of any partition on the OMU hard disk is less than 20%, perform the
following operations to clean up the disk:
1. Back up the files on the partition that need to be saved to a hard disk by referring to
Transferring OMU Files to a Local PC.
3. Run the cd target directory command to navigate to the directory where the files to be
deleted are saved.
4. Run the rm file name or rm -r folder name command to delete the unnecessary files.
l If the available space of each partition is at least 20%, no further action is required.
----End
Transferring OMU Files to a Local PC

Transferring files between a local PC and the OMU using the FTP protocol is an important
method for saving files during operation and maintenance.
Prerequisites
l The firewall on the portable PC is disabled.
l OMU applications are started.
Context
There are two methods for transferring files on the OMU:
l Using the file management function on the LMT
l Running commands
Table 4-10 describes the commands used for downloading files.
Table 4-10 Commands commonly used on the FTP
Command Description Example
cd Change the current directory. cd /mbsc/upgrade
dir Query the structure of the dir

current directory.
get Upload files from the OMU get x (x indicates the file
to a local PC. name)
put Download files from a local put x (x indicates the file

PC to the OMU. name)
NOTE
The following steps use downloading the 123.xml file from the OMU to the local D drive as an example.

BSC6900 UMTS
Procedure
l Downloading the 123.xml file on the OMU to the local D drive using the file management
function on the LMT
1. Enable the file management function on the LMT. For details, see File Manager in
BSC6900 UMTS LMT User Guide.
2. Select the 123.xml file in the target directory and click Download.
l Downloading the 123.xml file on the OMU to the local D drive using commands
1. On the local PC, choose Start > Run, enter cmd, and click OK.
2. Type the d: command and press Enter to go to drive D.
3. Enter the ftp IP address command to connect the local PC to the OMU, where IP
address indicates the virtual external or commissioning IP address of the OMU.
4. Enter the user name and password of the FTP. The connection between the local PC
and the OMU is established after the certification passes.
NOTE
The FTP user name is fixed to be FtpUsr. Its password is mbsc@com or will be set during the OMU
application installation. For details, see Records of the OMU Application Installation
Information.
5. Go to the directory where the 123.xml file is saved by referring to commonly used
FTP commands.
6. Transfer the 123.xml file.
Command Description
Run the get 123.xml command. Upload the 123.xml file from the OMU
to the local D drive.
Run the put 123.xml command. Download the 123.xml file from the
local D drive to the OMU.
7. After the file transfer is complete, run the quit command to disconnect the FTP.
----End
Example
The following is an example for downloading the 123.xml file from the local D drive to the /
mbsc/bam/version_a/bin/bam directory of the OMU:
C:\Documents and Settings>d:
D:\>ftp 10.161.21.3
Connected to 10.161.21.3.
220 ftp server ready.
User (10.161.21.3:(none)): FtpUsr
331 Password required for FtpUsr.
Password:
230 User logged in.
ftp> cd /mbsc/bam/version_a/bin/bam
250 CWD successful.
ftp> put 123.xml
200 PORT command OK.
150 Opening BINARY mode data connection for '/123.xml' (104 bytes)
226 Transfer complete.
ftp> quit

BSC6900 UMTS
D:\>
4.3.9 Managing the Operating Status of the OMU

This section describes how to manage the operating status of the OMU by running MML
commands.
Querying the OMU Operating Status

This section describes how to query the operating status of the OMU subsystem, the service
processes, and the status of the OMU board.
Prerequisites
Procedure
l Querying the status of the OMU subsystem
1. Run the MML command DSP OMU. The operating status of the OMU subsystem is
displayed, including the OMU operating status, fixed IP address configuration, virtual
IP address configuration, status of data synchronization, status of the internal and
external networks, and status of the backup channel.
l Querying the status of the service processes when the OMU is operational
1. Run the MML command DSP OMUMODULE. The names and status of the service
processes are displayed.
If the status of the service processes is Started, the OMU service processes are
normal.
If the status of the service processes is Stopped, the OMU service processes are
normal and not started.
If the status of the service processes is Exception, the OMU service processes are
abnormal. When active and standby OMUs are configured, the self-healing
switchover is triggered if the abnormal state persists. When an independent OMU
is configured, the OMU reports the ALM-20707 OMU Process Abort alarm.
l Querying the status of the OMU board
1. Run the MML command DSP OMUSRV. The OMU board information is displayed,
including the CPU usage, memory usage, number of logical CPUs, memory capacity,
total space of logical disks, current available space, and percentage of the available
space.
----End
Querying the Information About an OMU Board

This section describes how to query the working environment, hardware status, and version
information about an OMU board.
Prerequisites

BSC6900 UMTS
Context
If an OMU board becomes faulty, query the information about the OMU board for fault location.
Procedure
l Querying the OMU working environment
1. Run the MML command DSP OMUENV. The CPU inlet temperature, memory inlet
temperature, hard disk temperature, and voltage of chips are displayed.
l Querying the OMU hardware status
1. Run the MML command DSP OMUHW. The subrack number, slot number, operating
status of the hard disk, status of Ethernet adapters and Ethernet adapter teams, and
RAID of the OMU are displayed.
The OMU hardware is normal if the following conditions are met:
The status of Primer harddisk and Standby harddisk is Online.

The status of the Raid is Normal, and the Raid rebulid scale is 0.
ETH0 netcard, ETH1 netcard, or both are Normal.
In active/standby OMU mode, the value for Backup channel netcard is
Normal. In independent OMU mode, the value for Backup channel netcard does
not impact the OMU hardware status.
Inner0 netcard, Inner1 netcard , or both are Normal.
Both Inner netcard group and Extra netcard group are Normal.
l Querying the version information about the OMU board
1. Run the MML command DSP OMUVER. The subrack number, slot number, and
version information about the PCB, BIOS, BMC, CPLD, and SDR are displayed.
----End
Querying the Version of the Active/Standby OMU Workspaces

This section describes how to query the version of the active and standby OMU workspaces,
such as the workspace flag and version of the OMU applications.
Prerequisites
Procedure
Step 1 Run the LST OMUAREA command to query the version of the active and standby OMU
workspaces.
----End
Querying the Status of Data Synchronization Between the Active and Standby
OMUs
This section describes how to query the status of data synchronization between the active and
standby OMUs.

BSC6900 UMTS
Prerequisites
l You have logged in to the LMT. For details, see Logging In to and Logging Out of the
LMT.
l Active and standby OMUs are configured.
Context
Due to network or database problems, an exception may occur during data synchronization.
When this occurs, the OMUs automatically rectify the faults.
Procedure
Step 1 Run the MML command DSP OMU on the active or standby OMU. The status of data
synchronization between the active and standby OMUs is displayed.
If data synchronization is abnormal, the ALM-20704 OMU Data Synchronization Failure alarm
is reported. Clear the alarm by referring to the alarm handling suggestions.
CAUTION
When Data-sync state is Data synchronization is successful, Data synchronization not built
due to version inconsistency, or Data synchronization cannot built due to OMU failure
switchover, you are allowed to switch over the active and standby OMUs.
----End
Checking the Data Consistency Between the Active OMU and the Standby OMU
This section describes how to check the data consistency between the active OMU and the
standby OMU after a fault-triggered switchover occurs.
Prerequisites
LMT.
l The OMUs work in active/standby mode.
Procedure
Step 1 Run the CMP OMUDATA command to check the consistency of alarm data, performance data,
and configuration data between the active and standby OMUs.

BSC6900 UMTS
CAUTION
l If the active OMU data is inconsistent with the standby OMU data, run the STR
DATASYNC command to start the data synchronization between the active OMU and the
standby OMU. Wait 5 minutes then run the CMP OMUDATA command.
l If the active OMU is synchronizing the initial data with the standby OMU, the LMT displays
failure information.
Step 2 Run the CMP OMUFILE command to check the consistency of the license file, patch file, and
performance file between the active and standby OMUs.
----End
Changing the OMU Time and Time Zone

The OMU time stops after the battery on the OMUa/OMUc board is exhausted. To correct it,
you will need to replace the battery, reset the OMU time, and change the OMU time zone.
Prerequisites
LMT.
l You have obtained the time and the time zone.
Context
The OMU time and time zone are set by default before the OMUa/OMUc board is delivered.
The OMU time indicates the time on the OMU operating system, and the OMU time zone
indicates the time zone on the OMU operating system.
Procedure
l Change the OMU time
1. Run the SET TIME command to change the OMU date and time.
l Change the OMU time zone
1. Run the SET TZ command to change the OMU time zone.
----End
Switching Over the Active/Standby OMU Workspaces

This section describes how to switch over the active and standby OMU workspaces for OMU
version upgrade.
Prerequisites
LMT.
l When the OMU works in active/standby mode, the active and standby OMUs work
normally. In addition, no MML commands are executed and no scheduled tasks are

BSC6900 UMTS
triggered. (You can query the data consistency using the CMP OMUDATA and CMP
OMUFILE commands to ensure that the data on the active OMU is synchronized to the
standby OMU.)
Context
Do not use this command for other scenarios.
Procedure
l Switching over the active/standby OMU workspaces in single-OMU mode
1. Run the SWP OMUAREA command and set Target OMU to ACTIVE (Active
OMU) to switch over the active and standby workspaces on the OMU.
2. Run the RST BSC command to reset the BSC so that the OMU data is consistent with
the host data.
l Switching over the active/standby OMU workspaces in dual-OMU mode
1. Run the SWP OMUAREA command and set Target OMU to STANDBY (Standby
OMU) to switch over the active and standby workspaces on the active OMU.
the host data.
NOTE
Switchover of the active and standby OMU workspaces will interrupt the BSC6900 O&M for
3 minutes.
----End
Forcibly Switching Over the Active and Standby OMUs

This section describes how to forcibly switch over the active and standby OMUs when the active
OMU needs to be manually shut down for a software/hardware upgrade or fault rectification.
By performing this task, the OMU services will not be interrupted.
Prerequisites
LMT.
l The OMU works in active/standby mode and the active and standby OMUs work normally
for more than 5 minutes (You can run the CMP OMUDATA and CMP OMUFILE
commands to query whether the active OMU data is consistent with the standby OMU data.
Ensure that the data on the active OMU is synchronized to the standby OMU to avoid data
loss after the switchover.)
Procedure
Step 1 Run the DSP OMU command to query the operating status of the active/standby OMUs.

BSC6900 UMTS
If... Then...
The active and standby OMUs work properly and the data Go to Step 2.
synchronization is normal,
The active and standby OMUs do not work properly or the data End this task.
synchronization is abnormal,
Step 2 Run the SWP OMU command to manually switch over the OMUs.
Step 3 Run the DSP OMU command to query the operating status of the active OMU after the
switchover. If the active OMU works properly, the switchover is successful.
----End
Resetting the OMU

This section describes how to reset the OMUa board, OMU applications, and OMU service
processes.
Prerequisites
Context
l The OMU operating system is restarted after the OMUa board is reset. If the OMUa board
is reset successfully, the faults of the OMU operating system or applications can be rectified.
l All the service processes are disrupted after the OMU applications are reset. If the OMUa
board is reset successfully, the faults of the OMU applications can be rectified.
l Resetting a specified OMU service process interrupts the service of the process for a while.
Procedure
l Reset the OMUa board/OMU applications
1. Run the RST OMU command.
If Reset Type is set to SOFT, only the OMU applications are reset. The OMU
operating system is not restarted.
If Reset Type is set to HARD, the OMU operating system is restarted.
NOTE
l When the OMU works in single-OMU mode, set the Reset Target to ACTIVE.
l When the OMUs work in dual-OMU mode, the active OMU is reset if you set the Reset
Target to ACTIVE.
l When the OMUs work in dual-OMU mode, the standby OMU is reset if you set the Reset
Target to STANDBY.
l Reset a specified service process
1. Run the RST OMUMODULE command and specify Reset Target and Module
Name to reset the specified OMU service process.
----End

BSC6900 UMTS
4.3.10 Managing OMU Applications

This section describes how to manage OMU applications.
Querying Operating Status of the omud

This section describes how to query the operating status of the omud to determine whether the
OMU can provide services normally.
Procedure
Step 1 Log in to the OMU by using the external fixed IP address by referring to Logging In to the
OMU.
Step 2 Run the /etc/rc.d/omud status command to query the operating status of the omud.
Option Description
If the operating status of the omud is running, The OMU is working.
If the operating status of the omud is unused, The OMU stops working.
----End
Starting the omud

This section describes how to start the omud so that the OMU can provide normal services.
Procedure
OMU.
Step 2 Enter the /etc/rc.d/omud start command and press Enter to start the omud.
----End
Stopping the omud

This section describes how to stop the omud so that the OMU stops providing services.
Context
You need to stop the omud before uninstalling the OMU applications, upgrading the OMU
applications, or restoring the BSC6900 data.

BSC6900 UMTS
CAUTION
l When the omud is stopped, all the OMU service processes will also stop. In turn, the OMU
stops providing services for the BSC6900. Therefore, perform this task with caution.
l If a fixed external IP address is configured for the OMU, stopping the omud will make the
virtual external IP address ineffective. In this situation, a user can log in to the OMU by using
the fixed external IP address if an independent OMU is configured. If the OMUs work in
active/standby mode, the virtual external IP address of the original standby OMU becomes
effective after the active OMU is stopped.
l If no fixed external IP address is configured for the OMU, the virtual external IP address is
still effective after you stop the omud.
Procedure
OMU.
Step 2 Enter the /etc/rc.d/omud stop command and press Enter to stop the omud.
----End
Uninstalling the OMU Applications

This section describes how to uninstall the OMU applications.
Prerequisites
l The OMU applications are installed. For details, see Installing the OMU Applications in
the Active Workspace.
Context
l If OMU applications are installed on both the active and standby OMU workspaces,
uninstall the OMU applications on the standby workspace before uninstalling them on the
active workspace.
l When the BSC6900 is configured with active and standby OMUs, uninstall the OMU
applications on both the active and standby OMUs.
l If there is only the active workspace on the OMU, the system will prompt you to uninstall
only the OMU applications on the active workspace.
NOTE
l Uninstalling the OMU applications from an OMU will cause all the data in the OMU to be lost. You are
advised to back up system data on the OMU before the uninstalling by referring to Backing Up the System
Data.
Procedure
Step 1 Log in to the standby OMU by using the fixed external IP address or the commissioning IP
address. For details, see Logging In to the OMU.
Step 2 Enter the /etc/rc.d/omud stop command and press Enter to stop the omud..

BSC6900 UMTS
Step 3 Enter uninstall_bam in any directory of the OMU and press Enter.
Step 4 The message Uninstall standby area. input Y to continue; input E to exit. is displayed. Enter
Y to uninstall the OMU applications on the standby workspace of the standby OMU.
Step 5 Enter the uninstall_bam command and press Enter.
Step 6 The message Uninstall main area. input Y to continue; input E to exit. is displayed. Enter
Y to uninstall the OMU applications on the active workspace of the standby OMU.
Step 7 Enter the exit command to log out of the OMU.
Option Description
If the OMU is in dual-OMU mode, Go to Step 8.
If the OMU is in single-OMU mode, End this task.
Step 8 Log in to the active OMU using the fixed external IP address or commissioning IP address. Then
perform Step 2 through Step 7 again.
----End
4.3.11 Backing Up and Restoring Data

This section describes how to use the omu_backup_linker tool to back up or restore the OMU
configuration data, alarm data, and performance data. When the OMU works in active/standby
mode, the omu_backup_linker tool can be used on only the active OMU. Otherwise, the OMU
data may be lost.
Context
The omu_backup_linker tool is used in the following scenarios:
l When an OMUa/OMUc board is damaged, it needs to be replaced with a new one. The data
on the damaged OMUa/OMUc board needs to be backed up and restored on the new OMUa/
OMUc board.
l The OMU data needs to be backed up during routine maintenance.
l The latest OMU data needs to be restored after the OMU database collapses or the OMU
upgrade fails.
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.

BSC6900 UMTS
Procedure
Step 2 Enter the cd /mbsc/bam/common/services command and press Enter to go to the directory
where the program of the omu_backup_linker tool is saved.
Step 3 Enter the ./omu_backup_linker command and press Enter to start the omu_backup_linker
tool, as shown in the following figure.
# 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
Backing Up the System Data

This section describes how to back up the BSC6900 configuration data, performance data, and
alarm data by using MML commands or the omu_backup_linker tool.
Prerequisites
l Prerequisites for performing this task using MML commands:
You have logged in to the LMT. For details, see Logging In to and Logging Out of the
LMT.
l Prerequisites for performing this task using the omu_backup_restore_tool are as follows:
You have logged in to the OMU by referring to Logging In to the OMU.
Context
CAUTION
l When the OMU works in active/standby mode, the system data must be backed up on the
active OMU.
l You must back up the OMU data manually to avoid a system data backup failure before
capacity expansion, upgrade, or a software loading.
Procedure
l Backing up the system data through an MML command
1. Run the BKP DB command to set Path of Backup File and Backup File Name to
back up the data in the specified directory on the OMU hard disk.
2. Obtain the backup data file from the specified directory by referring to Transferring
OMU Files to a Local PC.
l Backing up the data by using the omu_backup_restore_tool
1. Enter the cd /mbsc/bam/common/services command and press Enter to go to the
directory where the program of the omu_backup_linker tool is saved.

BSC6900 UMTS
2. Enter the ./omu_backup_linker command and press Enter to start the

3. Enter backup and press Enter after the Please input a valid
bkp_res_type : message is displayed.
4. Enter the save path and names of the backup files and press Enter. The system data
starts the backup. If the message Backup OMU database succeed! is
displayed, the system data is successfully backed up on the OMU hard disk.
----End
Example
Back up the OMU data to /mbsc/bam using the omu_backup_restore_tool and the name the file
as omu.bak. The following shows an example of the results.
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, 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
Backup omu database [100%]
Backup OMU database succeed!
omd_test_name /mbsc/bam/common/services #

This section describes how to restore system data by using a data backup file.
Context
Restoring the BSC6900 system data will interrupt services on the BSC6900. After the system
data is restored, the data on the host will be inconsistent with the data on the OMU. As a result,
services will be greatly impacted. Therefore, you are advised to restore the system data in the
early morning hours when traffic volume is low.
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.
l If the backup restoration tool is used to restore data, all BSC6900 data is restored, including
configuration data, alarm data, performance data, operating logs, administrator account,
authority information, and product information.
NOTE
This document uses the OMU in active/standby mode as an example. If an OMU is in independent mode, skip
operations on the standby OMU.
Procedure
l Restoring the system data through an MML command

BSC6900 UMTS
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.
l Restoring the system data by using the omu_backup_restore_tool
1. Log in to the active and standby OMUs by referring to Logging In to the OMU.
2. Enter the /etc/rc.d/omud stop command and press Enter to stop the omud. on the
active and standby OMUs.
3. Restore data in the original active OMU using the omu_backup_linker tool.
a. Enter the cd /mbsc/bam/common/services command and press Enter 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 the ./omu_backup_linker command
and press Enter to start the omu_backup_linker tool.
c. Enter backup and press Enter after the Please input a valid
bkp_res_type : message is displayed.
d. Enter the save path and name of the backup file and press Enter when the
Please input a valid backup file pathname : message is
displayed. If the restoration is successful, the Restore OMU database
succeed! message is displayed.
4. Copy and save the backup file to be restored in the standby OMU using the psftp
software. For details, see 4.4.1 psftp Software.
5. Repeat Step 3 to restore data in the original standby OMU using the
6. Enter the /etc/rc.d/omud start command and press Enter to start the omud. on the
7. Log in to the LMT by referring to Logging In to and Logging Out of the LMT in the
8. Run the REQ CMCTRL command to obtain the data configuration rights.
9. 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 no, load the restored data to the BSC6900 host boards.
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 9.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 with Subrack No. specified to reset this subrack. If data inconsistency
occurs in multiple subracks, run the RST BSC command to reset the BSC.
----End
Example
Restore the OMU data by using the omu.bak file under /mbsc/bam. The following shows an
example of the results:

BSC6900 UMTS
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, 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
Restore omu database [100%]
Restore OMU database succeed!
omd_test_name /mbsc/bam/common/services # /etc/rc.d/omud start
Starting mbsc daemon
4.3.12 Using the omutool

This section describes how to use the omutool to modify the configuration data of the active and
standby OMUs, including the OMU working mode, IP addresses and subnet masks of the internal
and external networks, and admin password.
Starting the omutool

This section describes how to start the omutool on the OMU. When the OMU works in active/
standby mode, you should log in to the active or standby OMU, and start the omu_backup_linker
tool.
Prerequisites
The OMU applications are installed. For details, see Installing the OMU Applications in the
Active Workspace.
Context
You can perform tasks by running omutool commands with specified parameters.
NOTE
l You can run the LST OMUAREA command to query the active OMU workspace.
l Assume that the active OMU workspace is installed in /mbsc/bam/version_a.
Procedure
Step 3 Run the ./omutool -h command. The parameter information on the omutool is displayed.
----End

BSC6900 UMTS
Setting the OMU Working Mode

This section describes how to set the OMU working mode by using the omutool. The OMU can
work either in independent or active/standby mode.
Prerequisites
l You have logged in to the LMT, and queried the slot No. for the OMU by running the LST
BRD command.
l You have logged in to the LMT, and queried whether the OMU is in single-OMU or dual-
OMU mode by running the DSP OMU command.
l You have logged in to the LMT, and queried the OMU version and workspace information
by running the LST OMUAREA command.
l You have logged in to the LMT and queried the OMU service mode by running the LST
MBSCMODE command.
Context
l If the working mode is changed from independent mode to active/standby mode, apply the
settings to both the active and standby OMUs. If the working mode is changed from active/
standby mode to independent mode, apply the settings to only the new active OMU.
l If the working mode of the OMU is changed from independent mode to active/standby
mode, ensure that the operating system, software version, and board type of the active
OMU are the same as those of the standby OMU. In addition, the slot number of the active
OMU and that of the standby OMU have an active/standby relationship.
l If the working mode of the OMU is changed from active/standby mode to independent
mode, you should run the MML command DSP OMU to ensure that the Data-sync
state is Data synchronization is successful and run the MML command
CMP OMUFILE to ensure that Compare result is consistent.
Procedure
l Switching the OMU from the independent mode to the active/standby mode (OMU
applications are not installed on the OMU to be added).
1. Insert an OMUa/OMUc board into the standby slot by referring to Installing the
OMUa/OMUc/SAUa/SAUc Boards or Installing the OMUc Boards in BSC6900
UMTS Installation Guide
2. Connect the PC to the commissioning Ethernet port of the OMU, and log in to the
standby OMU by using the commissioning IP address. For details, see Logging In to
the OMU.
3. Install OMU applications on the standby OMU. For details, see Uploading the OMU
Application Installation Package to the OMU and Installing the OMU
Applications in the Active Workspace.
NOTE
You must select active/standby mode during the process of installing the OMU applications for the
standby OMU.
4. Change the IP addresses and subnet masks of the standby OMU to ensure that the
fixed internal IP addresses, fixed external IP addresses, and IP address of the backup
channel between active and standby of OMUs comply with the planning principle for
the IP addresses and do not conflict with each other. For details about changing IP

BSC6900 UMTS
addresses, see Changing IP Addresses of OMU Ethernet Adapters and Their

Subnet Masks.
original active OMU.
directory where the omutool program is saved. on the original active OMU.
7. Run the ./omutool dualmode dual command on the original active OMU to set the
working mode of the OMU to active/standby mode.
9. Five minutes after the original active OMU has been started, start the omud on the
standby OMU.
WARNING
You should start the standby OMU 5 minutes after the active OMU is started to keep
the two OMUs from competing for the active state. This helps avoid data loss.
10. Change the operating system password on the standby OMU to that of the original
active OMU by referring to 4.3.6 Changing the Administrator Password of the
Operating System.
11. Run the ADD BRD command on the LMT to add an OMU.
12. Run the MML command DSP OMU on the LMT and check whether the value for
Data-sync state is Data synchronization is successful.
13. Connect an Ethernet cable to the Ethernet port on the added OMU.
l Switching the OMU from the independent mode to the active/standby mode. (OMU
applications are installed on the OMU to be added.)
1. Connect the PC to the commissioning Ethernet port of the OMU and log in to the
original active OMU by using the commissioning IP address. For details, see Logging
In to the OMU.
directory where the omutool program is saved. on the original active OMU.
4. Run the ./omutool dualmode dual command on the original active OMU to set the
6. Insert an OMUa/OMUc board in the standby slot 5 minutes after the original active
OMU starts.

BSC6900 UMTS
WARNING
Start the standby OMU 5 minutes after the active OMU is started to avoid the two
OMUs from competing for active state, which will avoid data loss.
7. Set the working mode of the standby OMU to active/standby mode by repeating Step
1 through Step 4.
fixed internal IP addresses, fixed external IP addresses, and the IP address of the
backup channel between active and standby of OMUs comply with the planning
principle for the IP addresses and do not conflict with each other. For details about
changing IP addresses, see Changing IP Addresses of OMU Ethernet Adapters
and Their Subnet Masks.
standby OMU.
active OMU by referring to 4.3.6 Changing the Administrator Password of the
Operating System.
11. Run the ADD BRD command on the LMT to add an OMU.
l Change the working mode of the OMU from active/standby mode to independent mode.
1. Run the RMV BRD command on the LMT to remove an OMU.
2. Log in to the active and standby OMUs by using the fixed external IP address by
referring to Logging In to the OMU.
4. Run the poweroff command on the OMU to be removed to power off the OMU.
5. Remove the OMU to be removed by referring to step 2 to step 5 inScenario: Old and
New OMU Boards Running the Same OS.
directory where the omutool program is saved. on the active OMU.
7. Run the ./omutool dualmode single command on the active OMU to set the working
mode of the OMU to independent mode.
active OMU.
----End
Changing IP Addresses of OMU Ethernet Adapters and Their Subnet Masks

This section describes how to change IP addresses and subnet masks of the OMU Ethernet
adapters using omutool.
Context
If the OMU is in active/standby mode, change the IP addresses and subnet masks of the Ethernet
adapters on both the active and standby OMUs. You are advised to first change the IP addresses

BSC6900 UMTS
and subnet masks of the Ethernet adapters for the standby OMU before changing those for the
active OMU.
NOTE
This task describes how to change all the IP addresses and subnet masks for the OMU. You can perform required
steps to fit onsite needs.
l Single-OMU mode: Stop the omud before the change and start the omud after the change.
l Dual-OMU mode: Stop the standby omud and then the active omud before the change. Start the active omud
and then the standby omud after the change.
For details about the Ethernet adapter binding relationship, see 3.1 OMU Ethernet Adapter
Configuration.
Procedure
where the omutool program is saved..
Step 4 The command for querying the OMU IP address and subnet mask is ./omutool dispipinfo.
For example, type the following command and press Enter to query the OMU IP address and
subnet mask:
./omutool dispipinfo
Step 5 The ./omutool innercard IP address command is used to change the fixed internal IP address.
For example, type the following command and press Enter to change the fixed internal IP
address:
./omutool innercard 80.168.3.60
Step 6 The ./omutool innervip IP address command is used to change the virtual internal IP address.
For example, type the following command and press Enter to change the virtual internal IP
address:
./omutool innervip 80.168.3.40
NOTE
l The fixed and virtual internal IP addresses must be in the same network segment. If the network segment
of the fixed internal IP address is changed to be different from that of the virtual internal IP address, you are
prompted to change the virtual internal IP address. If the network segment of the internal IP address is
changed to be different from that of the fixed internal IP address, you are prompted to change the fixed
internal IP address.
l When you change the fixed and virtual internal IP addresses, the corresponding subnet masks are created
automatically.
l If you change the fixed and virtual internal IP addresses for the first time, perform the following additional
steps:
1. Run the SET SUBNET command to set the BSC6900 subnet number so that it is consistent with the
number of the network segments on which the fixed internal IP address and virtual internal IP address
are located.
2. Remove the SCUa board and reinstall it in the MPS. Then, reset the MPS to validate the new fixed and
virtual internal IP addresses.
l After these two steps are performed, the OMU can communicate with the BSC6900 host boards normally.
Step 7 The ./omutool extercard IP address mask (gateway) command is used to change the fixed
external IP address and mask.

BSC6900 UMTS
For example, type the following command and press Enter to change the fixed external IP
address and mask:
./omutool extercard 10.161.10.100 255.255.255.0
CAUTION
Before changing the fixed external IP address, virtual external IP address, and external gateway
IP address, log in to the OMU using the debugging IP address at the local end. Otherwise, remote
login in to the OMU to change the IP addresses may disconnect the OMU from its peer.
Step 8 The ./omutool extervip IP address subnet mask (gateway) command is used to change the virtual
external IP address and subnet mask.
For example, type the following command and press Enter to change the virtual external IP
address and subnet mask:
./omutool extervip 10.161.10.102 255.255.255.0
NOTE
l After the virtual external IP address and mask are changed, run the RMV EMSIP command and then the
ADD EMSIP command to update the virtual external IP address and mask that are recorded in the OMU
database.
of the fixed external IP address is changed to be different from that of the virtual internal IP address, you
are prompted to change the virtual external IP address. If the network segment of the virtual external IP
address is changed to be different from that of the fixed external IP address, you are prompted to change the
fixed external IP address.
l After the fixed external IP address, virtual external IP address, and gateway IP address are changed, the
communication between the OMU and peripheral equipment is interrupted. You need to use the new fixed
or virtual external IP address to reconnect the OMU and peripheral equipment.
Step 9 The ./omutool gateway gateway IP address is used to change the gateway IP address.
For example, type the following command and press Enter to change the gateway IP address:
./omutool gateway 10.161.10.1
NOTE
You can change the fixed or virtual external IP address simultaneously with changing the gateway IP address.
The following are the related commands:
l ./omutool extercard IP address Subnet mask Gateway IP address for changing the fixed external IP address
and gateway IP address simultaneously
l ./omutool extervip IP address Subnet mask Gateway IP address for changing the virtual external IP address
Step 10 Change the backup channel IP address of the active and standby OMUs by using commands
listed in the following table.
Option Description
Backup channel IP address of the ./omutool backupcard IP address.

active and standby OMUs on the
Example: Enter the following command and press
Ethernet adapter ETH3-UPDATE of
Enter to delete the fixed external IP address:
the OMUa board ./omutool backupcard 192.168.3.60

BSC6900 UMTS
Option Description
Backup channel IP address of the ./omutool backupcard_for_omuc IP address.

Ethernet adapter B_UPDATE0 of the
OMUc board ./omutool backupcard_for_omuc 192.168.9.60
Backup channel IP address of the ./omutool backupcard_for_omua IP address.

OMUc board ./omutool backupcard_for_omua 192.168.3.60
Step 11 The ./omutool debugcard IP address is used to change the commissioning IP address.
For example, type the following command and press Enter to change the commissioning IP
address:
./omutool debugcard 192.168.6.60
NOTE
l After you change the backup channel IP address and commissioning IP address of the active and standby
OMUs, the corresponding subnet mask will be created automatically.
l To change the IP addresses of the OMU, you must follow the principle of IP address planning. For
details, see 3.2 OMU IP Address Plan. When entering the command, ensure that there is a space
between the IP address and the subnet mask.
l Record the new IP addresses in 4.5.1 Information Record Sheet of OMU Software Installation.
Step 12 The ./omutool delextercard command is used to delete the fixed external IP address.
For example, type the following command and press Enter to delete the fixed external IP
address:
./omutool delextercard
NOTE
l If the virtual and fixed external IP addresses have been configured and the fixed external IP address is planned
to be deleted, use this command to delete the configured fixed external IP address.
l If ALM-20702 Active and Standby OMU Communication Link Failure is reported before you delete the
fixed external IP address and the alarm cause is the external network, delete the alarm after you delete the
Step 13 Enter the /etc/rc.d/omud start command and press Enter to start the omud..
----End

This section describes how to change the passwords for users admin, root, and db_user by using
the omutool and how to change the password for user FtpUsr by using the MML command.
Context
l admin is the account for logging in to the LMT.
l db_user and root are the accounts for accessing the OMU database.
l FtpUsr is the account for uploading and downloading files to and from the OMU.
If active and standby OMUs are configured on the BSC6900, you must change the passwords
used by the admin, db_user, and root user on both the active and standby OMUs.

BSC6900 UMTS
It is assumed that version_a is the OMU active workspace in this operation.
NOTE
l It is recommended that you change the password at your first login and then change the password every
three months.
l Users root and db_usr must both contain the combination of the following:
l At least one lower-case letter
l At least one upper-case letter
l At least one digit
l At least one special character -?[]_+{}
The user password must have a minimum length of 8 characters and maximum length of 32 characters.
l The admin and FtpUsr user password must have a minimum length of 6 characters and maximum length
of 32 characters.
Procedure
l Changing the password used by admin
4. Run the ./omutool adminpwd command to change the admin password.
5. Enter the /etc/rc.d/omud start command and press Enter to start the omud..
l Changing the password used by root
4. Run the ./omutool dbrootpwd command to change the root password.
l Changing the password used by db_user user
1. Log in to the target OMU.
4. Run the ./omutool dbpwd command to change the password of the db_user user.
l Changing the password used by FtpUsr user
2. Run the MML command MOD FTPPWD to change the password used by FtpUsr
user.
----End

BSC6900 UMTS
Example
The following shows an example for changing the password used by admin:
Dopra_136 /mbsc/bam/version_a/bin/bam # ./omutool adminpwd

Enter a password or press Ctrl+C to quit:
Re-enter password or press Ctrl+C to quit:
Successfully set the admin user's password!
The following shows an example for changing the password used by root:
Dopra_136 /mbsc/bam/version_a/bin/bam # ./omutool dbrootpwd

Successfully set the root's password of the database!
The following shows an example for changing the password used by db_user user:
Dopra_136 /mbsc/bam/version_a/bin/bam # ./omutool dbpwd

Successfully set the db_user's password of the database!

This section describes how to change the computer name by using omutool.
Context
l After installing the OMU applications onsite, you need to change the computer name and
IP addresses according to the plan. For information about how to change the OMU IP
addresses, see Changing IP Addresses of OMU Ethernet Adapters and Their Subnet
Masks.
l If the BSC6900 is configured with active and standby OMUs, name them differently.
Procedure
where the omutool program is saved..
Step 4 Run the ./omutool hostname Computer name command to change the computer name.
For example, to change the computer name to omu_123, type the ./omutool hostname
omu_123 command and press Enter.
Step 5 Enter the /etc/rc.d/omud start command and press Enter to start the omud..
----End
Follow-up Procedure

BSC6900 UMTS
2. Run the DSP OMU command to query the new computer name.
Modifying the NE Type

This section describes how to modify the NE type by using the omutool.
Context
To manage BSCs uniformly on the M2000, you need to modify the NE type of upgraded BSCs.
The following procedure is for active and standby OMUs whose active workspace is
version_a. For a single OMU, ignore the steps for the standby OMU.
Procedure
Step 1 Log in to the standby OMU and stop the omud process on it. Then, log in to the active OMU
and stop the omud process on it. For details, see Logging In to the OMU and Stopping the
omud.
Step 2 Type the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the directory
Step 3 Type the ./omutool netype command followed by the new value of the NE type parameter on
the active OMU. Press Enter to modify the NE type.
The prompt set ne type success! indicates that the NE type has been successfully modified.
NOTE
To query the NE type, type the omutool netype command and press Enter.
Step 4 Start the omud process on the active OMU first and then the omud process on the standby OMU.
For details, see Starting the omud.
----End
Example
dopra_linux_up /mbsc/bam/version_a/bin/bam # ./omutool netype
Current ne type is :BSC6***
dopra_linux_up /mbsc/bam/version_a/bin/bam # ./omutool netype BSC6900
set ne type success!
4.3.13 Adjusting OMU Slots

This section describes how to move the active and standby OMUs that are originally installed
in slots 20 to 27 to other slots to reserve slots 20 to 27 for interface boards with high throughput.
Prerequisites
l The target slots for OMUs are idle and can hold OMUs. Such slots can be slots 0 to 3, slots
20 to 23, or slots 24 to 27.
l The target slots for OMUs are idle and can hold OMUs. Such slots refer to OMUa Board
or OMUc Board.
l The value of Data-sync state is Data synchronization is successful. You can run the DSP
OMU command to view the setting of Data-sync state.

BSC6900 UMTS
Procedure
Step 1 Perform different operations to shut down the OMUs based on the operating system.
If... Then...
The Suse Linux operating system or Dopra 1. Log in to the active and standby OMUs
Linux operating system is used respectively by referring to Logging In to
the OMU.
2. Run the etc/rc.d/omud stop command to
3. Run the poweroff command to shut down
the OMUs.
The Windows operating system is used 1. Log in to the active and standby OMUs
respectively by referring to 5.2.20
2. Choose Start > Run. Type cmd in the
Open text box and then press Enter. The
OMU command interface is displayed.
3. Run the net stop omud command to stop
the omud process.
4. Choose Start > Shutdown. Select
Shutdown from the drop-down list box to
shut down the OMU.
Step 2 When the OFFLINE LED on the OMU board panel is on, pull the active and standby OMUs
and insert them into the target slots.
NOTE
Insert active and standby OMUs into the target slots one by one after pulling both of them.
Step 3 Wait about five minutes, log in to the LMT. and then run the DSP OMU command to check
whether the active and standby OMUs operate properly.
Step 4 Run the LST BRD command to query the subrack number and slot numbers of the active and
standby OMUs before the switchover.
Step 5 Run the RMV BRD command to remove the original active and standby OMUs.
Step 6 Run the ADD BRD command to add new active and standby OMUs. In this step, set slot numbers
of the OMUs to the target OMU slot numbers.
Assume that the target OMU slot numbers are 21 and 23. Run the following commands:
ADD BRD: SRN=0, BRDCLASS=OMU, BRDTYPE=OMUa, SN=21;
Step 7 Check whether the OMUs are properly displayed on the device panel and whether they are in
normal state.
Step 8 Click Alarm in the home page of the LMT and view current active alarms of the BSC6900 in
the Browse Alarm tab page.

BSC6900 UMTS
Step 9 Optional: If there is an alarm related to the original OMUs in the list of active alarms, select
the alarm, right-click it, and choose Clear Alarm from the shortcut menu to manually clear the
alarm.
----End
4.4 Appendix: OMU-Related Software

The OMU-related software, including the psftp software and PuTTY software, is used to install
the OMU applications and perform operation and maintenance on the OMU.
4.4.1 psftp Software

This section describes how to obtain and use the psftp software to upload the OMU application
installation package to the OMU.
Context
l The psftp software is used to upload files to the OMU hard disk. The OMU applications
can be used only after the psftp software is installed.
l The psftp software is also used to download files from the OMU hard disk to a local PC.
Table 4-11 lists the commands commonly used on the psftp software.
Table 4-11 Commands commonly used on the psftp software
Command Description Example
cd Change the OMU directory. cd /mbsc/upgrade
ls Query the structure of the ls

current directory.
lcd Go to the local folder. lcd D:\BSC6900V900R014C00

\Software\setup\linux
get Transfer files from the To transfer a file, run the get
OMU to the local PC. V900R014C00 command.
To transfer a folder, run the get -r
V900R014C00 command.
put Transfer files from the local To transfer a file, run the put
PC to the OMU. V900R014C00 command.
To transfer a folder, run the put -r
V900R014C00 command.
mkdir Create a directory on the mkdir /mbsc/upgrade

OMU.
rmdir Remove a directory from rmdir /mbsc/upgrade

the OMU.

BSC6900 UMTS
Procedure
Step 1 Contact Huawei engineers who can obtain the psftp software by performing the following
operation:
Log in to http://support.huawei.com/support/. Choose Software Center > Controlled Tool
> Core Network Product Line > Genex CN Nastar TOOL > Tools for remote login linux
to download the psftp software.
Step 2 Double-click psftp.exe. A window is displayed, as shown in Figure 4-14.
Figure 4-14 Logging in to the OMU using the psftp software
Step 3 Type the open IP address command and press Enter (using 10.161.21.203 as an example).
Step 4 Log in to the OMU as user root user, lgnusr user, or common user to connect to the OMU. The
displayed interface is as follows:
psftp: no hostname specified; use "open host.name" to connect

psftp> open 10.161.21.203
login as: root
root@10.161.21.203's password:
----End
4.4.2 PuTTY Software

This section describes how to obtain and use the PuTTY software to log in to the OMU.
Prerequisites
l The PC is connected to the Internet.

BSC6900 UMTS
l An operating system has been installed on the OMU board.
Context
PuTTY is an SSH client program that supports SSH and can be used for remotely logging in to
the Dopra Linux operating system.
NOTE
Other client programs that support SSH can also be used.
Procedure
Step 1 Contact Huawei engineers who can obtain the tool by performing the following operation:
Log in to http://support.huawei.com/support/. Choose Software Center > Controlled Tool
> Core Network Product Line > Genex CN Nastar TOOL > Tools for remote login linux
to download the PuTTY software.
Step 2 Double-click putty.exe. The PuTTY Configuration dialog box is displayed, as shown in
Figure 4-15.
Figure 4-15 PuTTY Configuration dialog box
Step 3 In the Specify your connection by host name or IP address area, specify the Host Name (or
IP address) by entering the IP address of the OMU board, and set Protocol to SSH.

BSC6900 UMTS
The IP address is determined based on the following rules:
If... Then...
The PC is connected to ETH2 on the OMU The IP address is the commissioning IP

board panel through an Ethernet cable, address of the OMU board.
The PC is connected to ETH0 or ETH1 on the The IP address is the fixed external IP address
OMU board panel through a network device, or virtual external IP address of the OMU.
Step 4 Click Open. The window shown in Figure 4-16 is displayed.
Figure 4-16 Logging in to the OMUa board through PuTTY software
Step 5 Log in to the OMU as the root user, lgnusr user, or common user.
----End

4.5.1 Information Record Sheet of OMU Software Installation

The information record sheet of OMU software installation records information regarding the
parameter configurations during the OMU software installation.

BSC6900 UMTS
Information Record Sheet of OMU Operating System Installation

Item Setting Installer
Computer name (active

OMU)
Administrator password
(active OMU)
Computer name (standby

OMU)
(standby OMU)
See Information Record Sheet of OMU Operating System Installation.
OMU Ethernet Adapter Team IP Address Installation Information

Internal IP address (subnet

mask) of the active OMU
External IP address (subnet


mask) of the standby OMU

Backup channel IP address

(subnet mask) of the active
OMU

(subnet mask) of the standby
OMU
Debugging IP address (mask)

of the active OMU
Debugging IP address
OMU
BSC local IP address (subnet

mask)

BSC6900 UMTS
Virtual Local Area Network

(VLAN) ID for
communication with the
VNP
Virtual Local Area Network

(VLAN) ID for
communication with the
EMS/LMT
Default gateway
See OMU Ethernet Adapter Team IP Address Installation Information.
OMU Applications Installation Information

Administrator (admin)
password
Password of the FTP user

(FtpUsr)
Internal virtual IP address
External virtual IP address
Local office name
See OMU Applications Installation Information.
4.5.2 Checklist for the OMU Software Factory Settings

This section provides a checklist for the OMU software factory settings. The checklist records
the OMU software installation and configuration information before delivery.
Checklist for the OMUa Board Software Factory Settings

Item Remarks
Setting the RAID 1 between the two SAS -

hard disks on the OMUa boards
Setting OMU BIOS Set the first boot device of the OMU to USB

BSC6900 UMTS
Item Remarks
Installing the Dopra Linux operating l If the version of the OMU operating system is
system V200R003C02SPC090 or later,
The default root user passwords of the
active and standby OMUs are
osadmin@123.
The default lgnusr user passwords of the
osnormal@123.
l If the version of the OMU operating system is
earlier than V200R003C02SPC090,
The default root user password of active
and standby OMUs are mbsc@com,
11111111, or huawei.
Installing the IPMI driver -
Teaming the internal Ethernet adapter The default IP address of the internal Ethernet
team adapter team of the active OMU is 80.168.3.50
(255.0.0.0).
The default IP address of the internal Ethernet
adapter team of the standby OMU is 80.168.3.60
(255.0.0.0).
Teaming the external Ethernet adapter The default IP address of the external Ethernet
team adapter team of the active OMU is
172.121.139.201 (255.255.255.0).
The default IP address of the external Ethernet
adapter team of the standby OMU is
172.121.139.202 (255.255.255.0).
Configuring backup channel IP address The default backup channel IP addresses of the
of the active and standby OMUs (for the active OMU is 192.168.3.50 (255.255.255.0).
OMUa board) The default backup channel IP addresses of the
standby OMU is 192.168.3.60 (255.255.255.0).
Configuring commissioning IP The factory setting of the commissioning IP

addresses of the active and standby addresses of the active OMU is 192.168.6.50
OMUs (255.255.255.0).
The factory setting of the commissioning IP
addresses of the standby OMU is 192.168.6.60
(255.255.255.0).
Checklist for the OMUc Board Software Factory Settings

Item Remarks
Setting OMU BIOS Set the first boot device of the OMU to USB

BSC6900 UMTS
Item Remarks
Installing the Dopra Linux operating l If the version of the OMU operating system is
system V200R003C02SPC090 or later,
The default root user passwords of the
osadmin@123.
The default lgnusr user passwords of the
osnormal@123.
l If the version of the OMU operating system is
earlier than V200R003C02SPC090,
The default root user password of active
and standby OMUs are mbsc@com,
11111111, or huawei.
Installing the IPMI driver -
Teaming the internal Ethernet adapter The default IP address of the internal Ethernet
team adapter team of the active OMU is 80.168.3.50
(255.0.0.0).
The default IP address of the internal Ethernet
adapter team of the standby OMU is 80.168.3.60
(255.0.0.0).
Teaming the external Ethernet adapter The default IP address of the external Ethernet
team adapter team of the active OMU is
172.121.139.201 (255.255.255.0).
The default IP address of the external Ethernet
adapter team of the standby OMU is
172.121.139.202 (255.255.255.0).
Configuring backup channel IP address l For the active OMU:

of the active and standby OMUs (for the
OMUc board) The default backup channel IP address of
B_UPDATE0 is 192.168.9.50
(255.255.255.0).
The default backup channel IP address of
B_UPDATE1 is 192.168.3.50
(255.255.255.0).
l For the standby OMU:

B_UPDATE0 is 192.168.9.60
(255.255.255.0).
B_UPDATE1 is 192.168.3.60
(255.255.255.0).

BSC6900 UMTS
Item Remarks
Configuring commissioning IP The factory setting of the commissioning IP

addresses of the active and standby addresses of the active OMU is 192.168.6.50
OMUs (255.255.255.0).
The factory setting of the commissioning IP
addresses of the standby OMU is 192.168.6.60
(255.255.255.0).
For details, see Checklist for the Factory Settings of the OMU Software (Creating
BSC6900).
4.5.3 OMU Directory Operation Rights List

This section describes the OMU directory operation rights list. The list records the operation
rights of all OMU directories.
After OMU applications have been installed, all the generated directories have operation rights.
For details about the OMU directory operation rights list, see the OMU Directory Operation
Rights List.
NOTE
In the OMU directory operation rights list, all files indicates all the files in a specific directory. all other
files indicates all the files that are not listed in a specific directory.
OMU Directory Operation Rights Explanation

Figure 4-17 explains the OMU directory operation rights.
Figure 4-17 OMU Directory Operation Rights Explanation
l (1) indicates the object type corresponding to the operation rights: - represents a file while
d represents a folder.
l (2) indicates the operation rights the current user has over the object: r represents that the
user has the right to read the object, w represents that the user has the right to write into the
object, x represents that the user has the right to execute the object, and- represents that the
user does not have the corresponding right.
l (3) indicates the operation rights users in the current user's group have over the object: r
represents that they have the rights to read the object, w represents that they have the rights
to write into the object, x represents that they have the rights to execute the object, and-
represents that they do not have the corresponding rights.
l (4) indicates the operation rights users who are not in the current user's group have over
the object: r represents that they have the rights to read the object, w represents that they

BSC6900 UMTS
have the rights to write into the object, x represents that they have the rights to execute the
object, and- represents that they do not have the corresponding rights.
l (5) does not indicate anything.
l (6) indicates the current user.
l (7) indicates the user group the current user belongs to.
l (8) indicates the object.
OMU Directory Operation Rights Explanation Examples

The following are two examples of directory operation rights explanation:
/mbsc:
drwxrwxrwx 8 root mysql mysql
-rw-r-xr-- 1 root root upsrvcfg.ini
l drwxrwxrwx 8 root mysql mysql indicates that the current user root, the users in the mysql
user group that the user root belongs to, and the users who do not belong to the mysql user
group have the rights to read and write into the /mbsc/mysql folder as well as the rights to
search for files in the folder.
l -rw-r-xr-- 1 root root upsrvcfg.ini indicates that the current user root has the rights to
read and write into the upsrvcfg.ini file in the /mbsc folder; the users in the root user group
that the user root belongs to have the rights to read and execute the upsrvcfg.ini file in
the /mbsc folder, and users who are not in the root use group that the user root belongs to
have the rights to read the upsrvcfg.ini file in the /mbsc folder.
4.5.4 OMU Folder Size List

The OMU folder size list records the size of storage space of the OMU common directories.
OMU Folder Size List

Contents Specifications
Storage Saving Path Classification Maximum Size (MB) Maxim

File Type um
GSM UMT GU Files
Only S Only
Only

BSC6900 UMTS
Host /mbsc/bam/common/ Files in the Larg Large Larg 30000

binary log fam/famlogfmt current e- - e-
directory capac capaci capa
ity ty city
hard hard hard
disk: disk: disk:
7392 16493 5344
Smal .6 Smal
l- Small l-
capac - capa
ity capaci city
hard ty hard
disk: hard disk:
3296 disk: 2272
4308
Files and Large-capacity hard N/A

subdirectories disk: 27000
in the current Small-capacity hard
directory disk: 9000
3G PCHR /mbsc/bam/common/ Files in the N/A Large Larg 12000

log fam/famlogfmt/pchr current - e-
directory capaci capa
ty city
hard hard
disk: disk:
9016 5944
Small Smal
- l-
capaci capa
ty city
hard hard
disk: disk:
4408 2872
VIP user /mbsc/bam/common/ Files in the 0 200 12000

tracing log fam/famlogfmt/ current
viptrace directory
MR log /mbsc/bam/common/ Files in the 1898 12000

fam/mr current
directory
Files and 2000 N/A

subdirectories
in the current
directory

BSC6900 UMTS
Tracing /mbsc/bam/common/ Files in the Large-capacity hard 12000

file fam/trace current disk: 2048
directory Small-capacity hard
disk: 512
Files and Large-capacity hard N/A

subdirectories disk: 3000
in the current Small-capacity hard
directory disk: 1000
File /mbsc/bam/version_x/ Files in the 50 1000

exported ftp/ExportBCPfile current
by running directory
the EXP
CFGBCP
command
Exported /mbsc/bam/version_x/ Files in the 100 1000

M2000 ftp/ExportCMESync- current
and CME View directory
BCP file
File /mbsc/bam/version_x/ Files in the N/A 30000

exported ftp/kpi_file current
the
EXP UKPI Files and 100 N/A
command subdirectories
in the current
directory
Exported /mbsc/bam/version_x/ Files and N/A 10000

device file ftp/device_file subdirectories
in the current
directory
Files in the 100 N/A

current
directory
Exported /mbsc/bam/version_x/ Files in the N/A 20000

electronic ftp/e_label current
label file directory
Files and 100 N/A

subdirectories
in the current
directory

BSC6900 UMTS
File /mbsc/bam/version_x/ Files and 100 N/A

exported ftp/export_almlog subdirectories
by running in the current
the directory
EXP ALM
LOG
command
File /mbsc/bam/version_x/ Files in the 200 5000

exported ftp/export_cfgmml current
the EXP
CFGMML
command
Directory /mbsc/bam/version_x/ Files and 50 N/A

exported ftp/export_logfile subdirectories
from board in the current
replaceme directory
nt logs and
board
temperatur
e logs
File server /mbsc/bam/common/ Files and 1500 N/A

directory ems subdirectories
in the current
directory
Database /mbsc/bam/version_x/ Files in the N/A 50

file backup data/backup current
directory directory
Files and 300 N/A

subdirectories
in the current
directory
Remark:
Large-capacity hard disk: OMU hard disk space > 73 GB
Small-capacity hard disk: OMU hard disk space = 73 GB
version_x indicates the active workspace of the OMU, which is either version_a or
version_b.
For details about storage space of the OMU common directories, see OMU Folder Size List.

This section provides the list of enabled ports on the OMU. The list describes the mapping
between enabled ports on the OMU and services provided by the OMU applications.

BSC6900 UMTS
Enabled Ports on the OMU

NOTE
Port 22 can be enabled regardless of whether the OMU applications are installed. Other ports can be enabled
only after the OMU applications are installed.
Port No. Service Process Description Network

Protocol Type
TCP UDP
20 FTP Server data Port for host loading, and uploading Y -

and downloading software and logs
(in active mode)
21 FTP Server Port for host loading, and uploading Y -

control and downloading software and logs
22 SSHD (operating SSH port for remotely logging in to Y -

system service) the OMUa board
1024-6553 FTP Server data Port for host loading, and uploading Y -
5 and downloading software and logs
(in passive mode)
80 Web LMT Port for local maintenance on the Y -

LMT
123 sntp Port that synchronizes the time of the - Y

OMU with that of the server and
provides local interception
443 Web LMT Port used to establish an encryption Y -

connection between a browser and
the LMT, therefore achieving NE
maintenance
843 Web LMT Port used for communication Y -

between the LMT and an NE,
therefore achieving NE maintenance
6000 ems_gate Port for maintenance Y -
6001 ems_gate Port for the alarm console Y -
6006 ems_gate Port for maintenance Y -
6088 Remote upgrade Remote upgrade tool Y -

tool
6099 ems_gate Port for configuration change Y -

informing message. This port is
connected only to the M2000.
6100 ems_gate Port for the alarm box Y -
6200 ems_gate Port for the Vendor Network Probe Y -

(VNP)

BSC6900 UMTS
Port No. Service Process Description Network

Protocol Type
TCP UDP
8000 ems_gate Port for maintenance (SSL Y -

encryption)
8001 ems_gate Port for alarm console (SSL Y -

encryption)
8006 ems_gate Port for maintenance (SSL Y -

encryption)
8099 ems_gate Port for configuration change Y -

informing message. This port is
connected only to the M2000. (SSL
encryption)
8100 ems_gate Port for alarm box (SSL encryption) Y -
8200 ems_gate Port for the VNP (SSL encryption) Y -
11775 monitor Port for monitoring the external - Y

network heartbeat between the
active/standby OMU and peripheral
equipment
16002 ems_gate Port through which the performance Y -

module reports notification
messages. This port is connected only
to the M2000.
18002 ems_gate Port through which the performance Y -

module reports notification
messages. This port is connected only
to the M2000. (SSL encryption)
For details, see Enabled Ports on the OMU (Creating BSC690).

BSC6900 UMTS
OMU Administration Guide 5 Scenario: Upgrading from the BSC6810 to the BSC6900
5 Scenario: Upgrading from the BSC6810 to the

BSC6900
About This Chapter
This chapter describes how to install software and perform operation and maintenance for the
OMU when the BSC6810 is upgraded to the BSC6900.
In this scenario, the physical entity to carry the OMU is the OMUa or OMUc board. For the
policy of replacing a faulty OMUb board, see Replacing an OMU Board in the BSC6900
UMTSSite Maintenance Guide.
OMU Software Structure

The OMU software consists of the operating system and the OMU applications. Figure 5-1
shows the OMU software structure.
Figure 5-1 OMU software structure
l Operating System
Windows Server 2003 is used.
l OMU Applications
The OMU applications run on the bottom-level operating system and provide various
service processes.
NOTE
Antivirus software such as Norton, Macfee, and Officescan can be installed on the OMU.

BSC6900 UMTS
Scenario Overview
When the BSC6810 is upgraded to the BSC6900, the OMU applications are upgraded while the
Windows Server 2003 operating system is retained.
This section describes the software installation policies after the BSC6810 is upgraded to the
BSC6900.
5.2 OMU Operation and Maintenance After the Upgrade
commands.
5.3 Appendix: Antivirus Software
The OMU supports an integrated antivirus solution that uses the OfficeScan software provided
by TrendMicro. For the method of installing the antivirus software, see the antivirus software
installation guide provided by Huawei.
5.4 Appendix: Installing the iPSI SEK SetWin Software
This section describes how to install the iPSI SEK SetWin software and how to roll back the
security enhancement policies.

BSC6900 UMTS

This section describes the software installation policies after the BSC6810 is upgraded to the
BSC6900.
Context
If Windows Server 2003 needs to be retained, Go to 5.1.3 Optional: Installing OMU Applications.
If Windows Server 2003 needs to be reinstalled, Go to 5.1.1 Reinstalling the Windows OS.
If Windows Server 2003 needs to be switched to Dopra Go to 5.1.2 Switching the OMU Operating System.
Linux,
5.1.1 Reinstalling the Windows OS

This section describes how to reinstall the Windows operating system (OS).
Context
After the BSC6810 is upgraded to the BSC6900, reinstall the Windows Server 2003 OS if it is
retained.
NOTE
The OMUc board supports only the Dopra Linux OS. Therefore, the Windows OS can only be reinstalled on
the OMUa board. Later in the document, the OMU board indicates the OMUa board.
Preparations for Reinstalling the OMU Operating System

An OMU board, PC, EasyInstall software, and other installation source programs must be
prepared before the OMU operating system is reinstalled.
Configuration Requirements for the OMU Board

l The memory is greater than 1 GB.
l Two SAS hard disks with more than 70 GB each are configured.
l RAID 1 is set up for the two hard disks.
Configuration Requirements for the Portable Computer

Table 5-1 lists the configuration requirements for the portable computer.

Configuration

BSC6900 UMTS

Configuration
RAM 1 512 MB 256 MB
Hard disk 1 80 GB 10 GB
Display - 1024x768 pixels or higher 800x600

adapter
resolutio
n
CD drive 1 - -
Ethernet 1 10&100 Mbit/s 10&100 Mbit/s

adapter
Operatin - Microsoft Windows XP -

g system Professional or Microsoft
Windows Server 2003
If the operating system of the PC is Microsoft Windows XP Professional, the Windows firewall
and simple file sharing must be disabled. Otherwise, the EasyInstall software and the installation
of the OMU operating system may be affected.
To disable the Windows firewall, perform the following procedures:
1. Right-click My Network Places and choose Properties from the shortcut menu. The
Network Connections window is displayed.
2. Right-click the Local Area Connection and choose Properties from the shortcut menu.
The Local Area Connection Properties dialog box is displayed.
3. Click the Advanced tab.
4. Click Settings. A dialog box is displayed. Click the General tab and click Off. Click
OK. The firewall is disabled.
To disable the simple file sharing, perform the following steps:
1. Double-click My Computer. The My Computer window is displayed.

2. Choose Tools > Folder options. The Folder options dialog box is displayed.
3. Click the View tab. In the Advanced settings area, clear the Use simple file sharing
(Recommended) check box.
To configure the IP address of the Ethernet adapter of the portable computer to 192.168.0.215,
perform the following steps:
1. Right-click My Network Places and choose Properties from the shortcut menu. The
Network Connections window is displayed.
2. Right-click Local Area Connection and choose Properties from the shortcut menu. The
Local Area Connection Properties dialog box is displayed.
3. Select Internet Protocol (TCP/IP) then click Properties. The Internet Protocol (TCP/
IP) Properties dialog box is displayed.

BSC6900 UMTS
4. Click Use the following IP address. Configure the IP address to 192.168.0.215 and the
subnet mask to 255.255.255.0.
Disks and Programs to Be Prepared

Ensure that the following installation disks and programs are available:
l EasyInstall software
l Microsoft Windows Server 2003 R2 standard edition installation disk
l SP2 patch programs: WindowsServer2003-KB914961-SP2-x86-CHS.exe and
WindowsServer2003-KB914961-SP2-x86-ENU.exe
l Windows 2007 basic patches: win2k3_CN 2007Basic Patches.exe and win2k3_EN
2007Basic Patches.exe
l iPSI SEK SetWin software
NOTE
Contact Huawei engineers who can obtain the software by performing the following operation:
To obtain the latest EasyInstall software, log in to http://support.huawei.com/support and choose Software
Center > Version Software > Wireless Product Line > WCDMA-RAN > WRAN OM Tools to download
the autoinst software.
The EasyInstall installation source cannot be prepared on a PC running the Windows XP SP3 operating system.
Creating the Operating System Installation Source

This section describes how to use the EasyInstall software to create the installation source of the
operating system to be installed on the OMU board.
Context
An installation source server, a portable computer, saves programs such as the operating system.
The EasyInstall software is used to install the OMU operating system.
Procedure
Step 1 Decompress the EasyInstall software package to a portable computer.
NOTE
Unless otherwise specified, the software package is decompressed in the D:\autoinst directory.
Step 2 Go to the D:\autoinst\cdcopy directory.

Step 3 Double-click ISM.EXE. The dialog box shown in Figure 5-2 is displayed.

BSC6900 UMTS
Figure 5-2 Installation Source Manager dialog box
Step 4 Select the installation source directory and click OK. The window shown in Figure 5-3 is
displayed. You are advised to select the default installation source directory. If the default
installation source directory does not exist, create one.
Figure 5-3 Installation Source Manager window
Step 5 Click New on the toolbar or choose Source > New. The dialog box shown in Figure 5-4 is
displayed.

BSC6900 UMTS
Figure 5-4 Creating operating system installation source 1
Step 6 Select an installation source type and click Next.
If... Then...
Windows Server 2003 R2... is selected, The dialog box shown in Figure 5-5 is displayed.

BSC6900 UMTS
Step 7 Click Next. The dialog box shown in Figure 5-6 is displayed.

BSC6900 UMTS
Step 8 Insert CD1 into the CD drive on the portable computer. Click Next. A dialog box is displayed.
Step 9 Click Execute. Files in CD1 start to be copied and the progress is displayed.
Step 10 After all the files in CD1 are copied, a dialog box is displayed, prompting you to insert CD2.
Click OK. Follow the wizard to copy the remaining CDs.
Step 11 After all the CDs of the OMU operating system are copied, click Finish. The installation source
is displayed in the Installation Source Manager window shown in Figure 5-3.
----End
Creating the Installation Source of the SetWin Software and OS Patches

This section describes how to use the EasyInstall software to create the installation source of the
operating system (OS) to be installed on the OMU board.
Context
l Contact Huawei engineers to obtain the SetWin software by logging in to http://
support.huawei.com/support and choosing Software Center > Controlled Tool >
Wireless Product Line > Security Tools > public.
NOTE
The version of the SetWin software must be consistant with that described in the Deployment Guide to
WRAN Windows Device Security Policy. To obtain the Deployment Guide to WRAN Windows Device
Security Policy, log in to http://support.huawei.com/support and choose Wireless > WCDMA-RAN
> WCDMA-RNC > Reconstruction Guide.
l Contact Huawei engineers to obtain patches for the Windows SP2 and basic patches for
the Windows 2007 by logging in to http://support.huawei.com/support and choosing
Software Center > Controlled Tool > Wireless Product Line > Universal OS
Patches > public.
Procedure
Step 1 Decompress the SetWin software package.
Step 2 Copy the pack folder under autoinst\template\pomu_mode to D:\OMU\SRC.
Step 3 Save the 2700 basic patches and the iPSI SEK Setwin.exe and License.Dat files decompressed
from the SetWin software package to D:\OMU\SRC\pack\ENU\.
Step 4 Save SP2 into D:\OMU\SRC\ and rename it ws2k3sp2.enu.exe.
The creation of the installation source for the SetWin software and OS patches is complete.
----End
Installing the OMU Operating System Using the EasyInstall Software

This section describes how to run the EasyInstall software on a portable computer to install the
Windows operating system, SP2, and SetWin software on the OMU.

BSC6900 UMTS
Prerequisites
l The OMU board is powered on and works normally.
l The OMU is connected to the local PC through the commissioning Ethernet port.
l The operating system installation source is created. For details, see Creating the
Operating System Installation Source.
Context
l Other Ethernet adapters are bound before you use the EasyInstall software to install the
OMU operating system. Therefore, you can install the software in network installation
mode by using only the commissioning Ethernet port. Otherwise, the installation fails.
l The time required for the installation depends on the portable computer configuration and
the Ethernet adapter performance. Generally, installing the Windows operating system,
SP2, and SetWin software takes 60 minutes if a 100 Mbit/s Ethernet adapter is used.
Procedure
Step 1 Go to the D:\autoinst path, open the autoinst.conf file using a text processing program, and
configure parameters by changing the default values to the recommended values, as shown in
Table 5-2.
Table 5-2 Configuration item
Item Default Value Recommended Description

Value
SRC_PATH d:\OMU\SRC Path for saving the Save path of the installation
installation source file source file
as needed (you can use
the default path)
DHCPD_INT Local area Eth2 Name of the Ethernet port

ERFACE connection connecting the portable
computer to the OMU
board
IPADDR 192.168.0.1 192.168.0.215 IP address of the portable

computer enabled with
DHCPD services
NETMASK 255.255.255.0 255.255.255.0 Subnet mask of the portable

computer enabled with
DHCPD services
RANGE 192.168.0.2-192.16 192.168.0.2-192.168. Range of the IP addresses

8.0.254 0.254 that can be assigned to the
portable computer by the
DHCPD server
Step 2 Choose Start > Run, and run the cmd command. The cmd window is displayed.
Type the following command and press Enter:
C:\Documents and Settings>cd /d D:\autoinst

BSC6900 UMTS
Step 3 Type checkout.bat and press Enter. The POMU Easy-Install Check Result dialog box is
displayed. Check whether the ports displayed in the dialog box are used, as shown in Figure
5-7.
Figure 5-7 Port status
NOTE
If the port status is Fail as shown in Figure 5-7, the port is not used. If the port status is OK, the port is
used. To release the port, quit other running programs.
1. Run the netstat -a -n -o command to query the PID of the port.
2. Open the task manager. Click the Processes tab. Choose View > Select Columns. Select PID and click
OK.
3. Query the process mapping the PID and terminate the process.
Step 4 Type install.bat and press Enter. After the DHCP and TFCP services are successfully started,
the command line returns to D:\autoinst, as shown in Figure 5-8.

BSC6900 UMTS
Figure 5-8 Starting services

BSC6900 UMTS
CAUTION
l Before running the script, ensure that ETH2 is in Link state, that the DHCP Ethernet port on
the installation source server and ETH2 (commissioning Ethernet port) on the OMU board
panel are connected, and that the installation source server is powered on. The DHCP service
cannot be started if ETH2 is in Down state.
l If the system provides a prompt indicating that a service failed to start, run the install.bat
program again until services are successfully started.
Step 5 Enter checkout.bat. If the four Ethernet ports are in OK state, all the services are started
properly.
Step 6 Go to the D:\autoinst\template\pomu_mode\RNC_02237123_LEFT path to check the

configuration files such as config.ini, deploy-ipconfig.ini, and third-party.ini, as shown in
Figure 5-9, Figure 5-10, and Figure 5-11.
Figure 5-9 config.ini
NOTE
The configuration items in the config.ini file are described as follows:
l ostype: type of the OMU operating system (unchangeable).
l cdkey: serial No. for installing the OMU operating system (unchangeable).
l partitions: partitions of the OMU hard disk. The OMU hard disk is divided into two partitions. For
example, change c:ntfs:15000|d:ntfs:5000|e:fat32:1 to c:ntfs:15000|d:ntfs:1, in which 1 indicates
the remaining capacity of the OMU hard disk. Only the last partition can be set to 1.
l Other configuration items can be changed as required.
Figure 5-10 deploy-ipconfig.ini

BSC6900 UMTS
NOTE
The configuration items in the deploy-ipconfig.ini file are described as follows:
l The change of the internal and external IP addresses must be based on the live network conditions.
l You should end each line with a semi-colon.
Figure 5-11 third-party.ini
NOTE
l If third-party software is to be installed, add the software name, save path, and commands to be executed
to the third-party.ini file.
l Delete the information about SQL2000 which is marked in red. Otherwise, the installation of the OMU
operating system may fail.
Step 7 Open the relevant file in D:\autoinst\site. Enter only the MAC address of ETH2 and the name
of the configuration file, as shown in Figure 5-12.

BSC6900 UMTS
Figure 5-12 Edited file
NOTE
l By default, there is a # symbol preceding the value of each MAC. This symbol is used to comment out
this statement. Delete # before the installation.
l To learn the MAC address of the ETH2 port, view the bar code of the MAC address on the OMU board,
for example, 0018821D0FE0-E5(6), which indicates that the MAC addresses of the six Ethernet
adapters on the OMU board are 0018821D0FE0, 0018821D0FE1, 0018821D0FE2, 0018821D0FE3,
0018821D0FE4, and 0018821D0FE5. You can write all these addresses in the file named site.
Step 8 Enter config.bat. When the script is successfully executed, all configurations on the server are
complete, as shown in Figure 5-13.
Figure 5-13 Configuring services

BSC6900 UMTS
CAUTION
l If the system provides a prompt indicating that a service failed to start, run the config.bat
program again until services are successfully configured.
l After the config.bat program is executed, a symbol # is automatically added in front of the
value of MAC. Delete the symbol # before running the install.bat program again.
Step 9 Turn the ejector levers on the OMU board outwards. After the OFFLINE LED on the OMUa
board is ON, turn the ejector levers inwards until they are in the proper position. The OMU board
automatically restarts on the DHCP server, and the installation of the operating system starts.
CAUTION
l During the installation process, do not connect the keyboard and mouse to the portable
computer to avoid any interruption to the installation.
l The OMU board may automatically restart several times during the installation process.
l During the installation process, do not run the install.bat script. If you run the install.bat
script, the DHCP server and TFTP server will be reconfigured and the network will be
interrupted temporarily, and the installation fails.
l During the installation process, if a message reading PXE-E32:TFTP open timeout
is displayed, disable the DHCP server, TFTP server, and firewall. If the DHCP server is
enabled after you run the install.bat script repeatedly, run the install.bat stop command to
disable the DHCP service, as shown in Figure 5-14. Then, run the install.bat script again
to start the EasyInstall software.
Figure 5-14 Disabling services
Step 10 Enter checkout.bat to query the status of the OMU board installation.
If STATUS of MAC in the displayed window is OK, the installation of the operating system is
complete. Ten seconds after the installation, the board restarts automatically. You can now
remotely log in to the OMU board.

BSC6900 UMTS
NOTE
Run the checkout.bat program. The STATUS of MAC in the displayed window indicates the installation
status of the OMU operating system.
l OK: the installation is complete.
l Installing: the installation is in progress.
l Waiting : the client has not sent messages to the server and that the installation is not started. If the
OMUa board is in Waiting state after the board is on for ten minutes, check that the network is connected
and that the client PC is powered on.
l Failed: the installation fails. For details, view the LOG.
----End
5.1.2 Switching the OMU Operating System

This section describes how to switch the OMU operating system after the BSC6810 is upgraded
to the BSC6900.
Prerequisites
l Before a USB storage device to switch the OMU operating system is prepared, the
communication between the local PC and the OMU must be normal. This ensures that the
Dopra Linux tool can obtain the configuration information of the target OMU.
l The virtual external IP address and external subnet gateway IP address have been obtained.
Context
After the OMU operating system is switched using the USB storage device, all the OMU data
is moved to the new operating system, including the OMU database that stores the configuration,
alarm, and platform data; performance configuration files; SSL certificate files; license files. All
the OMU applications are retained. The performance result files and log files need to be backed
up to a local PC before the OMU operating system is switched. For details about the directory
where these files are to be backed up, see table 1 in Checking the Installation Directory of
OMU Applications. You can use a file manager to back up the files. For details about the file
manager, see File Manager.
The OMU is reset when the operating system is switched. In active/standby mode, the OMU
reset interrupts Operation and Maintenance (OM) for 5 minutes. In independent mode, the OMU
reset interrupts OM for 20 minutes. The OMU reset does not affect ongoing services.
The communication between the M2000 and BSC6900 is interrupted when the OMU is reset.
The periodical traffic statistics that are to be reported to the M2000 when the OMU is being
restarted are lost. You are advised to finish preparing a USB storage device for this operation
before 24:00. If the OMU is in active/standby mode, insert the prepared USB storage device to
the standby OMU and restart the standby OMU. Then switch over the active and standby OMUs
between 24:00 and 01:00 when performance counters are not being reported to the M2000. This
prevents the loss of traffic statistics. If the OMU is in independent mode, insert the prepared
USB storage device and restart the OMU between 24:00 and 01:00 for the same purpose.
Before preparing a USB storage device, verify the device by referring to DOPRA Linux USB
Disk Certificate Guide in the directory where the Dopra Linux USB storage device is saved. If

BSC6900 UMTS
the USB storage device is not usable, replace it. The Netac U208 (2 GB), Kingston and Sandisk
USB storage devices are recommended.
The duration for preparing a USB storage device varies based the bandwidth of the network
from the PC to the equipment room, the USB protocol, and the PC performance. The duration
listed in Table 4-2 refers to the duration for preparing a USB storage device in compliance with
the USB2.0 protocol. The duration for preparing a USB storage device in compliance with the
USB1.1 protocol takes about twice as long as preparing a USB storage device in compliance
with the USB2.0 protocol. If the duration for preparing the device requires much longer than the
listed duration, the performance of the PC in use is poor. If this occurs, restart the PC or use a
PC with a higher level of performance.
Table 5-3 Operation and duration
Operation Duration
Prepare a USB storage device. The duration varies based on the bandwidth
of the network from the PC to the equipment
room.
l If the network bandwidth is 1 Mbit/s or
higher:
minutes.
minutes.
l If the network bandwidth is 512 kbit/s:
minutes.
minutes.
Install, restore, or switch the OMU operating 20 to 40 minutes

system using a USB storage device.
CAUTION
l The BSC software version cannot be rolled back after the OMU operating system is switched.
l After the USB storage device is prepared, do not modify the OMU data before switching the
OMU operating system. Otherwise, the OMU data will be inconsistent with the host data.
l To ensure data synchronization between the two hard disks of the OMU, the Redundant Array
of Independent Disks (RAID) between them must be normal. If the RAID is abnormal, do
not switch the OMU operating system. To query whether the RAID is normal, run the DSP
OMUHW command.

BSC6900 UMTS
Procedure
Step 1 Prepare a USB storage device, portable computer, and program files.
1. Prepare a USB storage device.
l The memory of the USB disk is at least 2 GB. If the BSC6900 is configured with active
and standby OMUs, two USB storage devices are required.
l The USB storage device will be formatted when it is prepared. Therefore, before using
the USB storage device, back up the data on it.
2. Prepare a portable computer.
l Check that the portable computer has the permission to read and write the USB storage
device. In addition, check that Microsoft .NET Framework 2.0 or later has been installed
on the portable computer.
NOTE
To check whether Microsoft .NET Framework 2.0 or later has been installed, choose Start >
Settings > Control Panel > Add or Remove Programs to view the components installed on
the portable computer. If Microsoft .NET Framework 2.0 or later has not been installed on the
portable computer, run dotnetfx2.0.exe under software package for preparing a USB storage
device used for switching the OMU operating system to Dopra Linux\tools.
l Table-2 lists the configuration requirements for the portable computer.

Configuration
RAM 1 512 MB 256 MB
Hard 1 80 GB 10 GB
disk
Display - 1024x768 pixels or higher 800600

adapter
resoluti
on
CD 1 - -
drive
USB 1 - -
installat
ion
drive
Operati - l Microsoft Windows -

ng XP Professional
system l Microsoft Windows
Server 2003
l Microsoft Windows 7
3. Obtain the tool for preparing the USB storage device.

BSC6900 UMTS
Contact Huawei engineers who can obtain the installation package or patch installation
package by performing the following operation:
Log in to http://support.huawei.com/support/ and choose Software Center > Version
Software > Wireless > SingleRAN > SRAN O&M tools to download the tool.
4. Download OMU-related software.
The OMU-related software, including the psftp and PuTTY software, is used to install the
OMU applications and perform O&M on the OMU.
Log in to http://support.huawei.com/support/. Choose Software Center > Controlled
Tool > Core Network Product Line > Genex CN Nastar TOOL > Tools for remote
login linux to download the psftp and PuTTY software.
5. Download the BSC6900 version installation package or patch installation package.
Log in to http://support.huawei.com/support/ and choose Software Center > Version
Software > Wireless > SingleRAN > MBSC > BSC6900 > BSC6900 Product Version
> BSC6900 Software Version. Choose Software VersionVER to download the
BSC6900 version installation package.
6. Prepare the OMU.
l Log in to the LMT using the OMU virtual external IP address by referring to Logging
In to and Logging Out of the LMT. On the LMT, run the BSC6900 MML command
DSP OMUVER to query the currently running OMU BIOS version.
NOTE
If the OMU BIOS version is V013 or V031, prepare a serial cable, monitor, and USB keyboard so that
the OMU can be started from the USB storage device. For details, see Setting the First Boot Device
of the OMU to USB.
7. Check that the host data is consistent with the OMU data.
Before switching the OMU operating system, ensure that the host data is consistent with
the OMU data.
Log in to the LMT using the OMU virtual external IP address and run the BSC6900 MML
command ACT CRC to check whether the host data is consistent with the OMU data. If
they are inconsistent, the alarm ALM-20736 Data Inconsistency Between OMU and Host
is reported. Clear the alarm by referring to ALM-20736 Data Inconsistency Between OMU
and Host.
Step 2 Prepare the USB storage device for switching the OMU operating system.
1. Double-click U_creator_eng.exe to begin installing a Dopra Linux operating system on
the USB storage device, as shown in Figure 5-15.

BSC6900 UMTS
Figure 5-15 U_creator_eng window
2. Select NE List in the left pane of the window, right-click the NE list, and choose Add
NE from the shortcut menu. The dialog box shown in Figure 5-16 is displayed.

BSC6900 UMTS
3. Enter the NE Name, select Switch from the Operate type drop-down list box, specify the
Virtual External IP and Password of Admin, and click OK. An NE is added.

BSC6900 UMTS
NOTE
l The NE name is used to identify different NEs and only can include letter, numerals, "-", and "_."
l Password of Admin is the password the admin user uses to log in to the LMT. It is configured during
the installation of the OMU applications.
l If you select EMS Proxy IP Address and type the IP address of the EMS proxy server (for example,
M2000), the EMS proxy server will forward messages between the PC and the OMU. The port 31035
of the EMS proxy server must be opened to the PC without being shielded by network devices such
as firewalls.
l If the upgrade is implemented by using the M2000 whose software version is iManager M2000
V200R012C00SPC220 or its later patch versions, the Access Control List (ACL) needs to be
configured for the PortTrunking service on the M2000 as follows:
a. Log in to the LMT and run the MML command DSP OMU to obtain the fixed and virtual external
IP addresses of the active and standby OMUs.
b. Run the MML command LST FTPSSRV to obtain the FTP command port number, the FTP active
mode data port number, and the numerical range of the FTP passive mode data port.
c. Run the ipconfig command on a PC running the M2000 client to obtain the IP address of the M2000
client.
d. Add the M2000 client IP address to the configuration file for source IP address rules and add the
following to the configuration file for destination IP address and port rules: OMU virtual external
IP address, fixed external IP addresses of the active and standby OMUs and the port numbers 6000,
8000, 6088, and 8088 that correspond to those IP addresses as well as the numbers of ports on the
FTP server. For details, see How Do I Configure the ACL for the PortTrunking Service? in
the FAQ part of the M2000 Administrator Guide (Sun, S10). If the software version of the M2000
is iManager M2000 V200R012C00SPC230 or later, click Online Help on the M2000, and choose
Security Management > User Management > Configuration and Management of User
Security > Security Policy Management > Setting the Proxy Service ACL for more information
about adding the M2000 client IP address to the configuration file for source IP address rules.
Log in to http://support.huawei.com/support/ by using the account of a Huawei engineer. Then,
go to Core Network Product Line > Wireless-OSS > iManager M2000-II to obtain the M2000
Administrator Guide (Sun, S10).
l The NE name, external virtual IP address, and the EMS proxy IP address can be changed only after
you delete the NE and then add the NE.
l Run the MML command LST SSLCONF to query the SSL configuration information of the OMU
whose operating system is to be switched.
l In the command output, if Certificate File Name and Private Key File Name are NULL, then
select None-SSL connection in Figure 5-16.
l If Connection Type is ALL Type in the command output, determine whether the SSL connection
is required when preparing the USB flash drive for installing a DOPRA Linux operating system
based on the security requirement. If the SSL connection is not required, select None-SSL
connection as the secure transmission type in Figure 5-16. If the SSL connection is required,
determine whether the certificate file and private key file are required based on the value of
Authentication Mode.
l If Connection Type is Only SSL Connection, determine whether the certificate file and private
key file are required based on the value of Authentication Mode.
l If Authentication Mode is Verify None, select SSL connection without the certificate file and
private key file as the secure transmission type in Figure 5-16. If Authentication Mode is Verify
Peer Certificate, select SSL connection with the certificate file and private key file as the
secure transmission type in Figure 5-16.
l If SSL connection with the certificate file and private key file is selected as the secure
transmission type in Figure 5-16, you need to load the certificate file and private key file. If the
OMU whose operating system is to be switched does not use its own pre-set certificates, download
the certificate file and private key file from the OMU to the local PC by using the FtpUsr user
account. For details, see MML commands in Transferring OMU Files to a Local PC. If the
OMU uses its own pre-set certificates, you do not need to download the certificate file or private
key file. The save path for the certificate file and private key file on the OMU is \bam\version_a

BSC6900 UMTS
\ftp\cert if the active workspace is version_a. You can run the LST OMUAREA command to
query the active workspace information.
l If you want to prepare multiple USB flash drives, it is recommended that you prepare the USB flash
drives one by one, and make a mark for each one.
4. Double-click the added NE in the left pane of the window. The window is updated, as
shown in Figure 5-17.
5. After all the information is obtained automatically, check the result and select the directory
for the version package. If there is a patch, also select the directory for the patch. Then click
OK to start the preparation for the USB storage device.
NOTE
l If a version or baseline patch is to be installed, select the V**R**C** directory of the version
installation package or the V**R**C**SPCX00 directory of the baseline patch installation
package.
l If a non-baseline patch is to be installed, select the V**R**C**SPCXYZ or
V**R**C**SPHXYZ directory of the patch installation package.
l If the link mode of OMU external Ethernet adapters fails to be obtained, query and set it by
referring to 4.1.1 Setting the Link Mode of the External OMU Ethernet Adapter and 5.2.16
Setting the Link Mode for External OMU Ethernet Adapters. Table 3 lists the mapping
between the queried link mode of OMU external Ethernet adapters and the mode of OMU external
Ethernet adapters selected in Figure 5-17.

BSC6900 UMTS
Table 5-5 Mapping between link modes of external Ethernet adapters

l Auto-negotiation is on. Auto

l Speed is 10Mb/s.
l Duplex is Full.

l Speed is 10Mb/s.
l Duplex is Half.

l Speed is 100Mb/s.
l Duplex is Full.

l Speed is 100Mb/s.
l Duplex is Half.

BSC6900 UMTS
CAUTION
l All the IP addresses shown in Figure 5-17 are obtained from the target OMU by the
Dopra Linux tool.
l If any information shown in Figure 5-17 is incorrect, suspend the operations, correct
the information on the working OMU, and continue with the operation. The information
cannot be corrected in online mode on the tool.
l The IP addresses listed in Figure 5-17 must follow the principle of planning OMU IP
addresses. For details, see 3.2 OMU IP Address Plan. Change the commissioning IP
address and commissioning subnet mask according to the real condition.
l The software version and data of only the active OMU workspace are switched when
the OMU operating system is switched. Therefore, the BSC version cannot be rolled
back if the OMU is not upgraded after the OMU operating system is switched. The host
log files, OMU log files, and traffic statistics are not retained after the OMU operating
system is switched.
l In independent mode, focus on configurations for only the active OMU. Configurations
for the standby OMU do not take effect.
l The data to be backed up includes the OMU database (which contains configuration,
alarm, and platform data), performance configuration files, SSL certificate files, and
license files.
l A directory where the tool is saved will be generated when an NE is created. The
directory name is the same as the NE name.
l If NE Name for a newly created NE is a duplicate of an already existing NE, the data
backup file directory of the existing NE will be replaced. Therefore, give each NE a
unique name. Ensure that all the files have been backed up or that the files are no longer
needed if an NE is given a duplicate name.
6. After the data backup is completed, the The data backup is completed. Continue with
preparing the USB device? message is displayed, as shown in Figure 5-18.

BSC6900 UMTS
Figure 5-18 Operational Interface
l Click Continue with preparing USB device to start preparing the USB storage device.
Then go to Step 2.12.
l Click Save the NE backup data, select the save path for the backup file, and click
Finish. Then go to Step 2.7.
NOTE
l If you just want to back up data or you cannot continue with preparing the USB storage device
because it cannot be identified by the PC, click Save the NE backup data to save the NE backup
data to the PC for future use. Before you click Save the NE backup data, ensure that the relevant
backup file exists in the Dopra Linux\NE Name\bk_pkg directory.
l The backup file created after you click Save the NE backup data is saved in a file folder named
after the OMU virtual external IP address of the NE.
l The backup file created after you click Save the NE backup data can be saved for preparing the
USB storage device before going to the site where the USB storage device cannot be prepared.
CAUTION
l The backup file cannot be modified after being saved on the PC. Otherwise, you cannot
prepare the USB storage device by using the local backup data of the NE.
l The saved NE data backup file does not contain information of the version or patch
installation package.

BSC6900 UMTS
7. To prepare the USB storage device by using the local backup data, double-click
U_creator_eng.exe to start the USB storage device for installation of the Dopra Linux
operating system.
8. Select NE List in the left pane of the window, right-click the NE list, and choose Add
NE from the shortcut menu. The dialog box shown in Figure 5-19 is displayed.
9. In the dialog box shown in Figure 5-19, type the NE name and set Operate type to Use
the local backup data to create the USB device. Then click OK.
10. Double-click the added NE in the NE list on the left pane of the window, as shown in
Figure 5-20.

BSC6900 UMTS
11. Select please select the local backup data. Then the USB storage device will automatically
obtain the backup data. After all the data is obtained, select the version package directory
and the patch directory. Then click OK to start the preparation of the USB storage device.
12. Check that the USB storage device is correct. If there is no USB storage device installed,
insert a USB storage device.
NOTE
l If multiple USB storage devices are required for multiple NEs, the USB storage devices are written
to one NE at a time. Remove the USB storage device and click Retry to start the preparation of another
USB storage device.
l After the USB storage device is prepared, remove it from the PC in secure mode to prevent the data
on it from being lost or corrupted.
13. After the preparation of the USB storage device used for switching the operating system
of the active OMU, the tool prompts you to insert another USB storage device for switching
the operating system of the standby OMU.
NOTE
l If only one OMU is configured, the standby OMU USB storage device does not need to be prepared.
l If each NE is configured with a pair of active and standby OMUs and the OMU operating system for
multiple NEs needs to be switched, label USB storage devices with the NE name and OMU slot number
to differentiate them.
14. After the preparation of the USB storage device used for switching the operating system
of the standby OMU, click Finish. The preparation for the USB storage devices is complete.
Step 3 Switch the OMU operating system by using the USB storage device.

BSC6900 UMTS
NOTE
l Switching the operating system of active and standby OMUs is used as an example. To switch the operating
system of an OMU in independent mode, perform Step 3.1, Step 3.2, Step 3.3, Step 3.4, Step 3.5, Step
3.9 in order. In Step 3.4, you only need to check that the OMU works properly.
l In active/standby mode, the original active OMU becomes a standby OMU and the original standby OMU
becomes an active OMU after the operating systems of the OMUs are switched. This does not affect the
system.
l Check that the USB storage device can be written to before inserting it to a USB port on the OMU panel.
1. Insert the USB storage device into any of the USB ports on the panel of the standby OMU
board.
NOTE
Differentiate the active OMU from the standby OMU by checking the status of the ACT indicator on their
panels. The OMU with the ACT indicator steady on is active, and the OMU with the ACT indicator steady
off is standby.
2. Restart the OMU.
a. Log in to the OMU by using the OMU fixed external IP address. For details, see 5.2.20
b. Choose Start > Shutdown > Restart.
3. Log in to the OMU 5 minutes later to determine whether the OMU operating system has
started installing from the USB storage device.
l If you fail to log in to the OMU, the OMU operating system has started to install from
the USB storage device.
l If you log in to the OMU successfully, the OMU operating system has not started
installing from the USB storage device. Prepare another USB storage device.
4. Wait 15 to 25 minutes, check the status of indicators on the OMU board to determine
whether the OMU operating system has been installed successfully (for details about the
indicator status, see step 3 in the Installing the OMU Operating System Using a USB
Flash Drive). After the operating system has been installed, use the virtual external IP
address of the OMU to log in to the LMT. After the OMU works properly (indicated on
the device panel), run the BSC6900 MML command DSP OMU to query Data-sync
state.
Expected result: Data-sync state is Data synchronization is successful.
5. Remove the USB storage device. Then restart the OMU by referring to Step 3.2.
6. Wait about 5 minutes and log in to the LMT using the OMU external virtual IP address.
After the OMU returns to normal (indicated on the device panel), run the BSC6900 MML
command DSP OMU to query Data-sync state.
Expected result: Data-sync state is Data synchronization is successful.
7. Run the BSC6900 MML command SWP OMU to switch over the active and standby
OMUs.
8. Wait about 5 minutes and log in to the LMT using the OMU external virtual IP address.
Check the status of the active and standby OMUs on the device panel.
Expected result: The active and standby OMUs are normal.
9. Run the BSC6900 MML command DSP TIME to check whether the OMU system time
is correct.
Expected result: The OMU system time is correct.

BSC6900 UMTS
If the OMU system time is incorrect, run the MML command SET TIME to change it.
10. Insert the USB storage device into any of the USB ports on the panel of the original active
OMU board.
11. Repeat Step 3.2, Step 3.3, Step 3.4, Step 3.8 to switch the operating system of the original
active OMU.
Expected result: The active and standby OMUs are normal.
----End
Follow-up Procedure
1. Log in to the LMT. On the LMT, type the user name and password that are used before the
OMU operating system is switched and check that they can still be used for the login.
2. Run the BSC6900 MML command ACT CRC to check whether the host data is consistent
with the OMU data. If they are inconsistent, the alarm ALM-20736 Data Inconsistency
Between OMU and Host is reported. For details about how to clear the alarm, see
ALM-20736 Data Inconsistency Between OMU and Host.
3. Optional: You are advised to change the password for user root of the Dopra Linux
operating system to ensure system security after the OMU operating system is switched.
4. Optional: After the operating system is switched, the setting on the original operating
system for disabling root user remote login and OMU route forwarding will be ineffective.
You need to re-configure those functions on the new operating system by referring to 6.1
Disabling root user login with SSH and 6.2 Disabling OMU route forwarding.
5.1.3 Optional: Installing OMU Applications

This section describes the policies for installing OMU applications after the BSC6810 is
upgraded to the BSC6900.
Prerequisites
l The administrator password of the OMU operating system and the external fixed IP
addresses that is planned on site are available.
l You have logged in to the OMU by referring to 5.2.20 Logging In to the OMU.
l You have obtained the OMU version installation package and copied it to the OMU hard
disk through directory sharing of the hard disk by referring to 5.2.19 Uploading Files to
the OMU.
Context
l If the operating system is Dopra Linux after the BSC6810 is upgraded to the BSC6900, see
4.2.3 Optional: Installing the OMU Applications for the method of installing OMU
applications.
l If the operating system is still Windows after the upgrade from the BSC6810> to the
BSC6900, see this section for the installation method of the OMU applications.

BSC6900 UMTS
WARNING
l After the upgrade and before OMU applications are reinstalled, record the IP addresses of
the live network. After OMU applications are reinstalled, change the IP addresses or restore
them to the historical IP addresses according to onsite requirements.
l If patches have been installed, before installing OMU applications, replace the original patch
files in the patch folder of the OMU application installation package with the patch
installation package (for example, the V900R01XC0XSPCXXX folder) saved on the local
PC.
If OMU applications have been pre-installed on active and standby OMU boards, unintall them
before installing the OMU applications of a correct version. To check whether OMU applications
have been pre-installed, do as follows:
1. Log in to the OMU by using the fixed external IP address or commissioning IP address.
For details, see 5.2.20 Logging In to the OMU.
2. Choose Start > Control Panel > Administrative Tools > Services to check whether the
omud service is available.
l If the omud service is available, OMU applications have been pre-installed. Uninstall
them by following operation steps in Uninstalling the OMU Applications.
l If the omud is service is not available, OMU applications have not been pre-installed.
Install the OMU applications following the installation procedures.
3. Log out of the OMU. For details, see 5.2.21 Logging Out of the OMU.
Procedure
Step 1 Go to the V***R***C**\install\setup directory of the version installation package and double-
click install_bam.bat. The system prompts you to type the product running mode, as shown in
the following:
NOTE
V***R***C** is an example of the version installation package. During installation, see the actual version.
[2011-05-03 10:12:32] software integrality verify begin...
[2011-05-03 10:12:42] software integrality verify end...
# The run mode of the product

# GO:GSM only
# UO:UMTS only
# GU:GSM and UMTS
# Please select one mode to install.
Please input a valid run_mode :
NOTE
The software integrity of the OMU applications is checked before they are automatically installed. The OMU
applications can be installed only if the check passes.
Step 2 Enter the product running mode and press Enter. The system prompts you to type the office
name, as shown:
# The name of office
# The name must range from 5 to 32 characters.
# The first character must be a letter and the subsequent characters can be lett
ers, digits, "-"or "_".
Please input a valid office_name :

BSC6900 UMTS
Step 3 Enter the office name and press Enter. The system prompts you to type the language, as shown:
# The OMU language version. eg: eng/chs
Please input a valid version :
Step 4 Enter the language and press Enter. The system prompts you to type the admin password, as
shown:
# The "admin" user's password of OMU service.
# The password must range from 6 to 32 characters and consist of only letters an
d figures.
# You can change the password later, but this password should be provided first.
Please input a valid admin_password :
Please input a valid Confirm password :
Step 5 Enter the admin password and press Enter. The system prompts you to type the FTP password,
as shown:
# The ftp user's password of OMU service
# The password must range from 6 to 32(characters) and consist of only letters a
nd figures.
# 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 6 Enter the ftp password and press Enter. The system prompts you to type the external virtual
IP address, as shown:
# The virtual extranet ip.
Please input a valid virtual_extranet_ip :
NOTE
The external virtual IP address must be located on the same network segment as the external fixed IP
address. The factory setting of the external fixed IP address is 172.121.139.201 (255.255.255.0). After the
OMU applications are installed, you can change the IP addresses and subnet masks of the OMU Ethernet
adapters
Step 7 Enter the external virtual IP address and press Enter. The system prompts you to type the
OMU system type, as shown:
# The OMU system type. eg: Single/Dual
# Single : Install stand-alone system
# Dual : Install dual system. The dual-OMU system can effeciently increase the
reliability of the OMU system
Please input a valid install_type :
Step 8 Enter the OMU installation type based on the field configuration and press Enter. Table 5-6
describes the OMU installation types.
Table 5-6 Description
Parameter Description
Single When the BSC6900 is configured with one

OMU board, install the OMU applications on
the board in single-OMU mode.
Dual When the BSC6900 is configured with two

OMU boards, install OMU applications on
the board in dual-OMU mode.
Step 9 The system asks you whether to continue with the installation, as shown:

BSC6900 UMTS
Please affirm input information. input Y to continue; input E to exit. ->
Step 10 Enter Y to install OMU applications. When the messageInstall OMU succeed! is
displayed, OMU applications are successfully installed.
Step 11 Record the information about the OMU applications installation in 5.5.1 Record Sheet of OMU
Software Installation Information.
----End
5.2 OMU Operation and Maintenance After the Upgrade

commands.
Context
After the BSC6810 is upgraded to the BSC6900, the OMU operation and maintenance is
depending on the type of the OMU operating system.
l If the OMU operating system is switched to Dopra Linux, perform maintenance and
operation for the OMU by referring to 4.3 Operating and Maintaining the OMU.
l If the OMU operating system is still Windows Server 2003, perform the steps in this section
for the OMU maintenance and operation.
5.2.1 Querying the Configuration of the OMU Ethernet Adapters

This section describes how to query the configuration information of the OMU Ethernet adapters.
The information includes IP addresses, their subnet masks, and broadcast IP addresses.
Procedure
l Method 1
1. Log in to the target OMU by referring to 5.2.20 Logging In to the OMU.
2. Choose Start > Run. Then type the cmd command and press Enter to type the
command mode of the OMU.
3. Type the net stop omud command and press Enter to stop the omud.
4. Type the cd /d d:\mbsc\bam\common\services command and press Enter to
navigate to the directory where the program of the omu_backup_linker tool is saved.
5. Type the omutool dispipinfo command and press Enter. The following shows an
example of the returned information.
[Virtual IP Information]
External virtual ip / mask : 10.141.149.15 / 255.255.254.0
Internal virtual ip / mask : 80.168.3.40 / 255.0.0.0
[Fixed IP Information]
External fixed ip / mask : 10.141.149.14 / 255.255.254.0
Internal fixed ip / mask : 80.168.3.60 / 255.0.0.0
Backup channel ip / mask : 192.168.3.60 / 255.255.255.0
Debugging ip / mask : 192.168.6.60 / 255.255.255.0
[Gateway Information]
Gateway : 10.141.148.1

BSC6900 UMTS
l Method 2
1. Log in to the active OMU by referring to 5.2.20 Logging In to the OMU.
3. Enter the ipconfig /all command and press Enter. The following shows an example
of the returned information.
Windows IP Configuration
Host Name . . . . . . . . . . . . : rnc-sq8diettruq

Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
Ethernet adapter Internal Network Team:
Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : TEAM : Internal Network Team
Physical Address. . . . . . . . . : 78-1D-BA-CB-15-D2
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 80.168.3.40
Subnet Mask . . . . . . . . . . . : 255.0.0.0
IP Address. . . . . . . . . . . . : 80.168.3.50
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . :
Ethernet adapter FE(Spare):

Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
#4
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.3.50
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Ethernet adapter External Network Team:

Description . . . . . . . . . . . : BASP Virtual Adapter
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.141.149.18
Subnet Mask . . . . . . . . . . . : 255.255.254.0
IP Address. . . . . . . . . . . . : 10.141.149.16
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 10.141.148.1
Ethernet adapter Eth2(LocalMaintain):

Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
#3
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.6.50
Subnet Mask . . . . . . . . . . . : 255.255.255.0
4. Log in to the LMT by referring to Logging In to and Logging Out of the LMT.
5. Run the DSP OMU command to query the fixed internal IP address, fixed external
IP address, IP address of the backup channel between active and standby OMU boards,
virtual internal IP address, and virtual external IP address.

BSC6900 UMTS
NOTE
The results from Step 3 and Step 5 show the information of all the IP addresses and subnet
masks of the OMU.
----End
5.2.2 Querying the OMU Operating Status

This section describes how to query the operating status of the OMU subsystem, the service
processes, and the status of the OMU board.
Prerequisites
Procedure
l Querying the status of the OMU subsystem
1. Run the MML command DSP OMU. The operating status of the OMU subsystem is
displayed, including the OMU operating status, fixed IP address configuration, virtual
IP address configuration, status of data synchronization, status of the internal and
external networks, and status of the backup channel.
l Querying the status of the service processes when the OMU is operational
1. Run the MML command DSP OMUMODULE. The names and status of the service
processes are displayed.
If the status of the service processes is Started, the OMU service processes are
normal.
If the status of the service processes is Stopped, the OMU service processes are
normal and not started.
If the status of the service processes is Exception, the OMU service processes are
abnormal. When active and standby OMUs are configured, the self-healing
switchover is triggered if the abnormal state persists. When an independent OMU
is configured, the OMU reports the ALM-20707 OMU Process Abort alarm.
l Querying the status of the OMU board
1. Run the MML command DSP OMUSRV. The OMU board information is displayed,
including the CPU usage, memory usage, number of logical CPUs, memory capacity,
total space of logical disks, current available space, and percentage of the available
space.
----End
5.2.3 Querying the Information About an OMU Board

This section describes how to query the working environment, hardware status, and version
information about an OMU board.
Prerequisites

BSC6900 UMTS
Context
If an OMU board becomes faulty, query the information about the OMU board for fault location.
Procedure
l Querying the OMU working environment
1. Run the MML command DSP OMUENV. The CPU inlet temperature, memory inlet
temperature, hard disk temperature, and voltage of chips are displayed.
l Querying the OMU hardware status
1. Run the MML command DSP OMUHW. The subrack number, slot number, operating
status of the hard disk, status of Ethernet adapters and Ethernet adapter teams, and
RAID of the OMU are displayed.
The OMU hardware is normal if the following conditions are met:
The status of Primer harddisk and Standby harddisk is Online.

The status of the Raid is Normal, and the Raid rebulid scale is 0.
ETH0 netcard, ETH1 netcard, or both are Normal.
In active/standby OMU mode, the value for Backup channel netcard is
Normal. In independent OMU mode, the value for Backup channel netcard does
not impact the OMU hardware status.
Inner0 netcard, Inner1 netcard , or both are Normal.
Both Inner netcard group and Extra netcard group are Normal.
l Querying the version information about the OMU board
1. Run the MML command DSP OMUVER. The subrack number, slot number, and
version information about the PCB, BIOS, BMC, CPLD, and SDR are displayed.
----End
5.2.4 Querying the Version of the Active/Standby OMU

Workspaces
This section describes how to query the version of the active and standby OMU workspaces,
such as the workspace flag and version of the OMU applications.
Prerequisites
Procedure
Step 1 Run the LST OMUAREA command to query the version of the active and standby OMU
workspaces.
----End

BSC6900 UMTS
5.2.5 Querying the Status of Data Synchronization Between the

Active and Standby OMUs
This section describes how to query the status of data synchronization between the active and
standby OMUs.
Prerequisites
LMT.
l Active and standby OMUs are configured.
Context
Due to network or database problems, an exception may occur during data synchronization.
When this occurs, the OMUs automatically rectify the faults.
Procedure
Step 1 Run the MML command DSP OMU on the active or standby OMU. The status of data
synchronization between the active and standby OMUs is displayed.
If data synchronization is abnormal, the ALM-20704 OMU Data Synchronization Failure alarm
is reported. Clear the alarm by referring to the alarm handling suggestions.
CAUTION
When Data-sync state is Data synchronization is successful, Data synchronization not built
due to version inconsistency, or Data synchronization cannot built due to OMU failure
switchover, you are allowed to switch over the active and standby OMUs.
----End

This section describes how to query occupied OMU ports.
Procedure
Step 1 Log in to the target OMU by referring to 5.2.20 Logging In to the OMU.
Step 2 Choose Start > Run. Then type the cmd command and press Enter to type the command mode
of the OMU.
Step 3 Enter the netstat -ano command and press Enter to query the occupied OMU ports. The
C:\Documents and Settings\Administrator>netstat -ano
Active Connections
Proto Local Address Foreign Address State PID

TCP 10.0.0.1:20 0.0.0.0:0 LISTENING 1712

BSC6900 UMTS
TCP 10.0.0.1:21 0.0.0.0:0 LISTENING 1512

TCP 10.0.0.1:80 0.0.0.0:0 LISTENING 3792
TCP 10.0.0.1:6099 0.0.0.0:0 LISTENING 672
TCP 10.0.0.1:6100 0.0.0.0:0 LISTENING 3792
TCP 10.0.0.1:16002 0.0.0.0:0 LISTENING 4
TCP 10.0.0.1:8006 0.0.0.0:0 LISTENING 1200
TCP 10.0.0.1:8088 0.0.0.0:0 LISTENING 436
TCP 10.0.0.1:8099 0.0.0.0:0 LISTENING 4
Information to the right of colon in the Local Address column indicates the occupied OMU port
numbers.
----End
5.2.7 Checking the Data Consistency Between the Active OMU and
the Standby OMU
This section describes how to check the data consistency between the active OMU and the
standby OMU after a fault-triggered switchover occurs.
Prerequisites
LMT.
Procedure
Step 1 Run the CMP OMUDATA command to check the consistency of alarm data, performance data,
and configuration data between the active and standby OMUs.
CAUTION
l If the active OMU data is inconsistent with the standby OMU data, run the STR
DATASYNC command to start the data synchronization between the active OMU and the
standby OMU. Wait 5 minutes then run the CMP OMUDATA command.
l If the active OMU is synchronizing the initial data with the standby OMU, the LMT displays
failure information.
Step 2 Run the CMP OMUFILE command to check the consistency of the license file, patch file, and
performance file between the active and standby OMUs.
----End
5.2.8 Changing the Administrator Password for the Operating

System
This section describes how to change the administrator password for Windows Server 2003 to
ensure security of the administrator account.
Prerequisites
You have logged in to the OMU by referring to 5.2.20 Logging In to the OMU.

BSC6900 UMTS
Context
For the factory setting of the administrator password for Windows Server 2003, see Checklist
for the Factory Settings of the OMU Software.
NOTE
three months.
of 32 characters.
Procedure
Step 1 Right-click My Computer and choose Manage from the shortcut menu.
Step 2 On the left pane of the window, choose System Tools > Local Users and Groups > Users.
Figure 5-21 shows the interface.
Figure 5-21 Computer Management Window
Step 3 On the right pane of Figure 5-21, right-click Administrator and choose Set Password from
the shortcut menu. Figure 5-22 shows the prompted dialog box.

BSC6900 UMTS
Figure 5-22 Setting the password for administrator
Step 4 Click Proceed in Figure 5-22. Figure 5-23 shows the prompted dialog box.
Figure 5-23 Setting password for administrator window
Step 5 Type the new password and confirm it. Record the password in the Record Sheet of OMU
Software Installation Information.
Step 6 Click OK to finish the operation.
----End
5.2.9 Forcibly Switching Over the Active and Standby OMUs

This section describes how to forcibly switch over the active and standby OMUs when the active
OMU needs to be manually shut down for a software/hardware upgrade or fault rectification.
By performing this task, the OMU services will not be interrupted.

BSC6900 UMTS
Prerequisites
LMT.
l The OMU works in active/standby mode and the active and standby OMUs work normally
for more than 5 minutes (You can run the CMP OMUDATA and CMP OMUFILE
commands to query whether the active OMU data is consistent with the standby OMU data.
Ensure that the data on the active OMU is synchronized to the standby OMU to avoid data
loss after the switchover.)
Procedure
Step 1 Run the DSP OMU command to query the operating status of the active/standby OMUs.
If... Then...
The active and standby OMUs work properly and the data Go to Step 2.
synchronization is normal,
The active and standby OMUs do not work properly or the data End this task.
synchronization is abnormal,
Step 2 Run the SWP OMU command to manually switch over the OMUs.
Step 3 Run the DSP OMU command to query the operating status of the active OMU after the
switchover. If the active OMU works properly, the switchover is successful.
----End
5.2.10 Setting RAID 1 on OMU Hard Disks

This section describes how to set RAID 1 on OMU hard disks to ensure data synchronization
between the source and target OMU hard disks.
Prerequisites
l OMU serial cables are available. For details about the cable information, see OMU serial
cable in BSC6900 UMTS Hardware Description.
l The source and target hard disks are available.
Context
One OMU hard disk serves as the source hard disk, and the other serves as the target hard disk.
Setting RAID 1 on the hard disks synchronizes the data on the source and target hard disks,
improving data security.
l The source hard disk saves backup data and files.

l The target hard disk mirrors the source hard disk.
NOTE
RAID 1 cannot be set on an OMUc board because it is configured with one hard disk.

BSC6900 UMTS
Procedure
Step 1 Connect the PC to the OMU serial port using the OMU serial port cable.
NOTE
If the OMU serial port cable is not available, the USB and VGA ports of the active OMU can be connected
to an external keyboard and monitor, respectively. Then starts from Step 6 to complete the configuration.
Step 2 On the PC, choose Start > All Programs > Accessories > Communications >
Step 3 Enter the connection name and click OK. The dialog box shown in Figure 5-25 is displayed.

BSC6900 UMTS
Step 4 Check the connection port and click OK. The dialog box shown in Figure 5-26 is displayed.

BSC6900 UMTS
Figure 5-26 Setting attributes for the connection port
NOTE
Step 5 Check that the parameters for the connection port are set correctly and click OK. The window
shown in Figure 5-27 is displayed.

BSC6900 UMTS
Step 6 Restart the OMU.
Option Description
Windows Server 2003 operating system 1. Log in to the target OMU by referring to 5.2.20
2. Choose Start > Shutdown, click Restart, and
click OK.
Step 7 After the OMU restarts, press F4 repeatedly until the message "Press Ctrl-C to start
LSI Logic Configuration Utility" is displayed. Then press Ctrl+C. The following
shows examples of the messages displayed.
Adapter PCI PCI PCI PCI FW Revision Status Boot

Bus Dev Fnc Slot Order
SAS1064 05 01 00 00 0.11.01-IR Enabled 0
Step 8 Press Enter. The following shows examples of the messages displayed.
Adapter SAS1064
PCI Slot 00

BSC6900 UMTS
Status Enabled
Boot Order 0
RAID Properties
SAS Topology
Press the arrow keys to select RAID Properties and press Enter. Check the value of Status to
determine whether the RAID is correct.
l If Status is Optimal, the RAID is working properly.
l If Status is Resyncing, the RAID is synchronizing data.
NOTE
l If this is the first time that the RAID is being set on the OMU, go to Step 13.
l If this is not the first time that the RAID is being set on the OMU, go to Step 9.
displayed.
Array 1 of 1
Type IM
Scan Order 2
Size(MB) 69618
Status Optimal
Manage Array
Step 10 Select Manage Array and press Enter. The following shows examples of the results that are
displayed.

Type IM
Scan Order 2
Size(MB) 69618
Status Optimal
Manage Hot Spare
Synchronize Array
Activate Array
Delete Array
Step 11 Select Delete Array and press Enter. The following shows examples of the results that are
displayed.
Y Delete array and exit to Adapter Properties

N Abandon array detetion and exit this menu
Step 12 Select Y. The following shows examples of the results that are displayed.
Adapter SAS1064
PCI Slot 00
Status Enabled
Boot Order 0
RAID Properties

BSC6900 UMTS
SAS Topology
displayed.
Creat IM Volume Create Integrated Mirror Array of 2

disks plus an optional hot spare,Data
on the primary disk may be migrated.
Create IME Volume Create Integrated Mirrored Enhanced

Array of 3 to 8 disks including an
optional hot spare.
All DATA on array disks will be DELETED!
Create IS Volume Create Integrated Striping array of
2 to 8 disks.
ALL DATA on array disks will be DELETED!
Step 14 Select Create IM Volume and press Enter. The following shows examples of the results that
are displayed.
Array Type:IM
Array Size(MB): -------

CAUTION
Select the source and target hard disks with caution because the data on the source hard disk can
be lost.
Step 15 Set RAID Disk to No, move the cursor to the value for RAID Disk of the source hard disk, and
press Space. The following show examples of the results that are displayed.
M - Keep existing data, migrate to an IM array.

Synchronization of disk will occur.
D - Overwrite existing data, create a new IM array
ALL DATA on ALL disks in the array will be DELETED!!
NO Synchronization performed.
l If you press M, the data on the source hard disk is saved. The target hard disk copies the data
from the source disk.
l If you press D, the data is deleted from the source hard disk and a new RAID is created.
Step 16 Press M or D to return to the messages shown in Step 14.
The value for RAID Disk is Yes, and the value for Drive Status is Primary.
Step 17 Select the target hard disk and press Space. An alarm is generated, as shown in the following:
WARNING! Data was found on the selected disk,this data will be lost when the array
is created!
Choose Discard configuration or Cancel Exit on the next screen to abort.
Step 18 Press C to return to the messages shown in Step 14.
The value for RAID Disk is Yes, and the value for Drive Status is Secondary.

BSC6900 UMTS
Step 19 Press C. The following shows the results that are displayed.
Create and save new array?

Cancel Exit
Save changes then exit this menu
Discard changes then exit this menu
Exit the Configuration Utility and Reboot
Step 20 Select Save changes then exit this menu and press Enter. The screen is refreshed, as shown
in Step 12.
Step 21 Select RAID Properties shown in Step 12 and press Enter. The following shows examples of
the results that are displayed.
Array 1 of 1
Type 1M
Scan Order 0
Size(MB) 69618
Status 2% Syncd
Manager Array
Step 22 Check that the RAID 1 is set correctly, and then press Esc repeatedly until the following
messages are displayed:
Are you sure you want to exit?

Cancel Exit.
Save changes and reboot.
Discard changes and reboot.
Exit the Configuration Utility and Reboot.
Step 23 Select Exit the Configuration Utility and Reboot and press Enter. RAID 1 is successfully set
on the OMU hard disks and the OMU restarts.
----End
5.2.11 Switching Over the Active/Standby OMU Workspaces

This section describes how to switch over the active and standby OMU workspaces for OMU
version upgrade.
Prerequisites
LMT.
l When the OMU works in active/standby mode, the active and standby OMUs work
normally. In addition, no MML commands are executed and no scheduled tasks are
triggered. (You can query the data consistency using the CMP OMUDATA and CMP
OMUFILE commands to ensure that the data on the active OMU is synchronized to the
standby OMU.)
Context
Do not use this command for other scenarios.

BSC6900 UMTS
Procedure
l Switching over the active/standby OMU workspaces in single-OMU mode
OMU) to switch over the active and standby workspaces on the OMU.
the host data.
l Switching over the active/standby OMU workspaces in dual-OMU mode
1. Run the SWP OMUAREA command and set Target OMU to STANDBY (Standby
the host data.
NOTE
Switchover of the active and standby OMU workspaces will interrupt the BSC6900 O&M for
3 minutes.
----End
5.2.12 Checking the Version of the Operating System

This section describes how to check whether the version of the operating system on the OMUa
board is correct.
Prerequisites
Procedure
Step 1 Choose Start > Settings > Control Panel on the OMU.
Step 2 Double-click System on the pop-up interface.
Step 3 Click the General tab on the pop-up interface.
Step 4 Check whether Microsoft Windows Server 2003, Standard Edition, and Service Pack 2 are
displayed in the System list on the interface.
Option Description
The displayed content is Microsoft Shows that Windows Server 2003 is installed
Windows Server 2003, Standard Edition, successfully and the patch is Windows Server
and Service Pack 2. 2003 Service Pack 2.
The displayed content is not Microsoft Shows that Windows Server 2003 is not
Windows Server 2003, Standard Edition, installed successfully. You need to reinstall the
and Service Pack 2. operating system. For details, see 5.1.2
Switching the OMU Operating System.
----End

BSC6900 UMTS
5.2.13 Manually Synchronizing the Data of the Active and Standby

OMUs
This section describes how to manually synchronize the data of the standby OMU with that of
the active OMU.
Prerequisites
LMT.
Context
After running the CMP OMUDATA command, you can manually synchronize the data of the
standby OMU with that of the active OMU if the data is inconsistent.
Procedure
Step 1 Run the STR DATASYNC command to start synchronizing the data of the standby OMU with
that of the active OMU.
NOTE
Successful running of the command only indicates a successful start to the data synchronization procedure
between the active and standby OMUs. To check whether the data synchronization succeeds, run the DSP
OMU command and query Data-sync state.
----End
5.2.14 Stopping the Synchronization of the Data of the Active and

Standby OMUs
This section describes how to manually stop synchronizing the data of the standby OMU with
the active OMU.
Prerequisites
LMT.
l The data of the standby OMU is being synchronized with that of the active OMU.
Procedure
Step 1 Run the STP DATASYNC command to stop the data synchronization between the active and
standby OMUs.
NOTE
Running this command leads to asynchronous data between the active and standby OMUs. The data between
the active and standby OMUs can be still asynchronous even after an OMU switchover. You can restart data
synchronization only by running the STR DATASYNC command.
----End

BSC6900 UMTS
5.2.15 Renaming Local Area Connections on the OMU

This section describes how to rename the local area connections on the OMU by using a portable
computer to remotely log in to the OMU after installing the OMU operating system and binding
the Ethernet adapters. Renaming the local area connections facilitates later configuration of the
IP addresses of the Ethernet adapters and Ethernet adapter teams and facilitates queries of the
Ethernet adapters.
Prerequisites
Context
You can use the portable computer to remotely log in to the OMU by connecting the computer
to the ETH2 port on the panel of the OMUa board. The default IP address of the ETH2 port is
192.168.6.50.
Procedure
Step 1 Right-click My Network Places and choose Properties from the shortcut menu. The Network
Connections window is displayed, as shown in Figure 5-28 .
Figure 5-28 Network Connections window
NOTE
The name of the external Ethernet adapter team has been displayed as External Network Team; therefore, it
does not need to be renamed.
Step 2 In the Network Connections window, rename the local area connections with the Device
Name of TEAM: Internal Network Team to Internal Network Team.
Step 3 Double-click the network_identify.js tool for identifying Ethernet adapters in the C:
\DRIVERS path. An Ethernet adapter can also be called a Network Interface Card, or NIC. The
interface shown in Figure 5-29 is displayed.

BSC6900 UMTS
Figure 5-29 Interface for identifying the Ethernet adapters (example)
NOTE
NIC Name in Figure 5-29 indicates the name of each local area connection in the Network
Connections window.
Step 4 Rename the local area connections according to the rules shown in Table 5-7.
Table 5-7 Renaming rule table
NIC Type New Name
ETH1 Eth1(External)
ETH0 Eth0(External)
ETH5-SCU6 Intel0(Internal)
ETH4-SCU7 Intel1(Internal)
ETH3-UPDATE FE(Spare)

BSC6900 UMTS
NIC Type New Name
ETH2 Eth2(LocalMaintain)
Step 5 Click Close to close the interface of the tool.
Figure 5-30 shows the Network Connections window after the renaming is complete.
Figure 5-30 Network Connections window after the renaming
----End
5.2.16 Setting the Link Mode for External OMU Ethernet Adapters
This section describes how to set the link mode of the external OMU Ethernet adapters so that
it is the same as that of the LAN switch.
Prerequisites
The link mode, duplex mode, and rate of the LAN switch have been acquired.
Context
There are two link modes of the LAN switch: force mode and auto-negotiation mode. The link
mode of the OMU external Ethernet adapter must be consistent with that of the LAN switch.
If the link mode of the external Ethernet adapters of the OMU is inconsistent with that of the
LAN switch, the network may be interrupted. If the link mode of the LAN switch is specified,
the link mode of the external Ethernet adapter of the OMU should also be specified.
If active and standby OMUs are configured, perform the following steps on both the active and
standby OMUs:

BSC6900 UMTS
NOTE
l The following procedure assumes that the link mode of the external Ethernet adapter is force mode and
the adapter works at 100 Mbit/s in full duplex mode.
l The following procedure assumes that version_a is the active workspace of the OMU. To query the
active workspace of the current OMU, run the LST OMUAREA command.
Procedure
Step 1 Connect the PC to the commissioning Ethernet port of the OMU and log in to the OMU by using
the commissioning IP address. For details how to log in to the OMU, see5.2.20 Logging In to
the OMU.
Step 2 Click Start > Settings > Control Panel > Network Connections. The Network
Connections window is displayed.
Step 3 Double-click Eth1(External). The interface shown in Figure 5-31 is displayed.
Figure 5-31 Eth1(External) status
Step 4 Click Properties. The interface shown in Figure 5-32 is displayed.

BSC6900 UMTS
Figure 5-32 Eth1(External) properties
Step 5 Click Configure in the General tab. The Broadcom NetXtreme Gigabit Ethernet #2
Properties interface is displayed.
Step 6 Click the Advanced tab and choose Property > Speed & Duplex on the left side, as shown in
Figure 5-33.

BSC6900 UMTS
Figure 5-33 Broadcom NetXtreme Gigabit Ethernet #2 properties
Step 7 Select the same link mode as that of the LAN switch from the Value list box and click
Confirm to end the setting.
CAUTION
The link mode of a Gigabit Ethernet adapter must be auto-negotiation and it is invalid to set the
link mode to 1000BASE-TX.
Step 8 Perform Step 2 to Step 7 again to configure the link mode of Eth0(External).
NOTE
The value is the link mode for external Ethernet adapters of the OMU, which can be set to Auto, 10 Mb
Full, 10 Mb Half, 100 Mb Full, and 100 Mb Half.
NOTE
The link mode of Eth0(External) and that of Eth1(External) must be the same.
Step 9 Choose Start > Run. Type cmd in the displayed dialog box and press Enter. The Command
Prompt window is displayed.

BSC6900 UMTS
Step 10 Type shutdown -r and press Enter to restart the OMU.

----End
5.2.17 Setting the First Boot Device of the OMU to USB

Before installing the Dopra Linux operating system using a USB storage device, ensure that the
first boot device of the OMU is USB.
Prerequisites
l The OMU starts normally.
l The OMU is locally configured with a keyboard and a monitor.
l The OMU serial cable has been obtained. For details about the OMU serial cable, see OMU
serial cable.
l The USB storage device has been inserted to the USB port on the OMUa board.
Context
There are two methods for starting the OMU:
1. Connecting the OMU to a PC by using the HyperTerminal program on the PC.
2. Directly connecting the OMU to the keyboard and monitor.
NOTE
This section is designed for OMUa board and uses the OMUa board as an example. An OMUc board is started
from a USB port by default.
Procedure
l Connecting the OMU to a PC by using the HyperTerminal program on the PC
(recommended)
1. Connect the PC to the OMU serial port by using the OMU serial cable.
2. On the PC, choose Start > All Programs > Accessories > Communications >

BSC6900 UMTS
3. Enter the connection name and click OK. The dialog box shown in Figure 5-35 is
displayed.
4. Check the connection port and click OK. The dialog box shown in Figure 5-36 is
displayed.

BSC6900 UMTS
Figure 5-36 Setting the attributes of the connection port
NOTE
5. Check that the parameters of the connection port are correct and click OK. The
window shown in Figure 5-37 is displayed.

BSC6900 UMTS
6. Restart the OMU.

If the OMU is installed with Windows Server 2003 operating system,
a. Log in to the OMU by referring to 5.2.20 Logging In to the OMU.
b. Choose Start > Shutdown, click Restart, and click OK.
7. After the OMU is restarted, switch to the window shown in Figure 5-37. Press F4 or
S repeatedly until the window is updated, as shown in Figure 5-38.

BSC6900 UMTS
Figure 5-38 BIOS information
8. Press the arrow keys to select Boot. The window is updated, as shown in Figure
5-39.
Figure 5-39 Boot setting

BSC6900 UMTS
9. Press the arrow keys to select Boot Device Priority and press Enter. The window is
updated, as shown in Figure 5-40.
Figure 5-40 Setting the boot device priority
10. Press the arrow keys to select 1st Boot Device and press Enter. The window is
updated, as shown in Figure 5-41.

BSC6900 UMTS
Figure 5-41 Setting the 1st boot device
11. Press Esc, select Exit, and press Enter. The window is updated, as shown in Figure
5-42.
Figure 5-42 Saving changes and exit

BSC6900 UMTS
12. Press the arrow keys to select Save Changes and Exit and press Enter. The changes
are saved. Exit the setting.
l Connecting the OMU to the keyboard and monitor directly
1. Directly connect the keyboard to the USB port and the monitor to the VGA port on
the OMU.
2. Log in to the LMT. Run the RST OMU command with Reset Type set to HARD.
Then reset the target OMU. The BIOS Setup screen is displayed on the monitor, as
Figure 5-43 BIOS Setup
3. Press DEL to type the BIOS Setup screen.

4. Press the arrow keys to select Boot, as shown in Figure 5-44.
Figure 5-44 Boot tab page
5. Use the arrow keys on the keyboard to select Boot Device Priority and press Enter.
6. Use the arrow keys on the keyboard to select 1st Boot Device and press Enter. Set
the first boot device of the OMU operating system to USB, as shown in Figure
5-45.

BSC6900 UMTS
Figure 5-45 Selecting the 1st boot device
7. Press F10 to save the settings and exit.
----End
5.2.18 Uninstalling the SQL Server 2000

After the BSC6810 is upgraded to the BSC6900, the SQL Server 2000 will not be used; however,
it still occupies operating system resources and is a potential safety hazard. Therefore, you are
required to uninstall the SQL Server 2000 after the version is stable.
Context
If active and standby OMUs are configured, uninstall the SQL Server 2000 on both active and
standby OMUs.
Exit all the applications including Windows NT event viewer and register editor before
uninstalling the SQL Server 2000. You are advised to perform the operation during off-peak
traffic hours.
Procedure
Step 2 On the OMU, choose Start > Control Panel > Add or Remove Programs, the Add or Remove
Programs window is displayed.
Step 3 Select Microsoft SQL Server 2000 and click Change/Remove to finish the installation, as

BSC6900 UMTS
Figure 5-46 Add or Remove Programs window
----End
5.2.19 Uploading Files to the OMU

This section describes how to upload files on a local PC to the OMU by using file sharing. This
task applies only to the OMU running the Windows operating system.
Prerequisites
l The fixed IP address of the external network, virtual IP address of the external network, or
commissioning IP address of the OMU are available. For the IP addresses of the OMU, see
the Record Sheet of OMU Software Installation Information.
Context
This task uploads the version installation package from a local PC to the OMU.
Procedure
Step 1 5.2.20 Logging In to the OMU.
Step 2 Set up a new folder on the OMU. Right-click the folder and choose Sharing and Security. The
Program Files Properties dialog box is displayed.
Step 3 In the Program Files Properties dialog box, select Share this folder and click OK.

BSC6900 UMTS
Step 4 Choose StartRun on the local PC. Enter \\IP address of the OMU, input the user name and
password in the displayed dialog box, and click OK.
Step 5 Copy the files to be uploaded to the target OMU directory that holds the files.
----End
5.2.20 Logging In to the OMU

This section describes how to log in to the OMU for the operation and maintenance by running
the mstsc.exe program on a computer.
Prerequisites
l The computer for remote login to the OMU is installed with an operating system of
Windows XP or later versions.
l The computer for remote login to the OMU works normally and is connected to the OMU
external network properly.
l The fixed IP address of the external network, virtual IP address of the external network, or
commissioning IP address of the OMU is obtained. For the IP addresses of the OMU, see
the Record Sheet of OMU Software Installation Information.
l The computer for remote login to the OMU and the IP addresses of OMU external network
are on the same network segment.
Context
l The OMU can be connected to only one computer by using the mstsc.exe program.
l The mstsc.exe program by running which you log in to the OMU should have the console
parameter. Otherwise, you cannot log in to the OMU.
NOTE
If the operating system of the computer for remote login to the OMU is Windows XP SP3, run the mstsc.exe
program with the admin parameter. That is, type mstsc /admin instead of mstsc /console.
Procedure
Step 1 Choose Start > Run on the computer used for remote login to the OMU. The Run dialog box
is displayed.
Step 2 Type mstsc /console and click Confirm. The Remote Desktop Connection dialog box shown
in Figure 5-47 is displayed.
CAUTION
When typing mstsc /console, include a space between mstsc and /console.

BSC6900 UMTS
Figure 5-47 Remote desktop connection dialog box
Step 3 Type the IP address of the OMU and click Connect.

NOTE
l Before starting OMU applications, type the fixed external IP address of the OMU.
l After the OMU applications start, type the fixed or virtual external IP address. The former is preferred.
l If you are performing local commissioning, type the commissioning IP address of the OMU.
l If the PC cannot be connected to the OMU by using either the fixed or virtual external IP address,
connect the PC to the commissioning Ethernet port on the OMU and type the commissioning IP address
of the OMU.
l You are advised to log in to the OMU using the external fixed IP address, external virtual IP
address, and commissioning IP address in sequence.
Step 4 Type the administrator user name and password and click Confirm based on the interface
message. The login is complete.
NOTE
It is recommended that you change the password at your first login and then change the password every three
months.
----End
5.2.21 Logging Out of the OMU

This section describes how to log out of the OMU after logging in to the OMU by running the
mstsc.exe program on a computer and performing operation and maintenance on the OMU.
Prerequisites

BSC6900 UMTS
Context
CAUTION
l Do not log out of the OMU by directly closing the desktop used for the remote login to the
OMU. Otherwise, the OMU operating system resources may not be fully released, and the
use of the OMU can be affected.
l Do not log off from the OMU directly. Otherwise, OMU processes will be abnormal.
l Shutting down the OMU will stop all the OMU services. If this occurs, you must restart the
OMU at the local end.
Procedure
Step 1 Choose Start > Close. The dialog box shown in Figure 5-48 is displayed.
Figure 5-48 Shut Down Windows dialog box
Step 2 Select Disconnect and click OK to log out of the OMU.
----End

BSC6900 UMTS
5.2.22 Resetting the OMU

This section describes how to reset the OMUa board, OMU applications, and OMU service
processes.
Prerequisites
Context
l The OMU operating system is restarted after the OMUa board is reset. If the OMUa board
is reset successfully, the faults of the OMU operating system or applications can be rectified.
l All the service processes are disrupted after the OMU applications are reset. If the OMUa
board is reset successfully, the faults of the OMU applications can be rectified.
l Resetting a specified OMU service process interrupts the service of the process for a while.
Procedure
l Reset the OMUa board/OMU applications
1. Run the RST OMU command.
If Reset Type is set to SOFT, only the OMU applications are reset. The OMU
operating system is not restarted.
If Reset Type is set to HARD, the OMU operating system is restarted.
NOTE
l When the OMU works in single-OMU mode, set the Reset Target to ACTIVE.
l When the OMUs work in dual-OMU mode, the active OMU is reset if you set the Reset
Target to ACTIVE.
l When the OMUs work in dual-OMU mode, the standby OMU is reset if you set the Reset
Target to STANDBY.
l Reset a specified service process
1. Run the RST OMUMODULE command and specify Reset Target and Module
Name to reset the specified OMU service process.
----End
5.2.23 Maintaining the OMU Routinely

This section describes how to remotely check and clean up the OMU hard disk and transfer files
from the OMU to the LMT PC on a regular basis to ensure that the OMU is working normally.
Regularly Checking and Cleaning Up the OMU Hard Disk

This section describes how to regularly check and clean up the OMU hard disk to ensure that at
least 20% space is available in each partition on the OMU hard disk.
Prerequisites

BSC6900 UMTS
Procedure
Step 1 Run the MML command DSP OMUSRV to query the available space of the partitions on the
OMU hard disk.
l If the available space of any partition on the OMU hard disk is less than 20%, perform the
following steps:
1. Back up the files on the partition that need to the saved to a hard disk of a computer by
referring to Transfer OMU Files to a Local Computer.
3. On the local computer, choose Start > Run, enter cmd, and click OK.
4. Run the cd /d Disk:\Target Directory command to navigate to the directory where the
files to be deleted are saved.
5. Run the del File name or rmdir Folder name command to delete the useless files.
l If the available space of each partition is greater than or equal to 20%, this task is complete.
----End
Transfer OMU Files to a Local Computer

This section describes how to transfer files between the local computer and the OMU through
the FTP protocol, which is an important method of backing up files in the operation and
maintenance process.
Prerequisites
l The firewall on the portable computer has been disabled.
l The OMU applications are started.
Procedure
Step 1 Start the file manager on the LMT by referring to File Manager in the BSC6900 UMTS LMT
User Guide.
Step 2 Right-click the target file and choose Download.
----End
5.2.24 Managing OMU Applications

This section describes how to manage OMU applications.
Querying the Operating Status of the omud

This section describes how to query the operating status of the omud to determine whether the
OMU can provide services normally.
Prerequisites

BSC6900 UMTS
Procedure
Step 1 Click Start > Settings > Control Panel to type the Control Panel interface.
Step 2 Double-click Administrative Tools > Services to type the Services interface.
Figure 5-49 Services interface
Step 3 Check the Status of omud to see whether the OMU is providing services.
Option Description
If the Status of omud is Started, the OMU is working.
If the Status of omud is blank, the OMU stops working.
----End
Starting the omud

This section describes how to start the omud so that the OMU can provide normal services.
Prerequisites
l OMU applications are installed. For details, see 5.1.3 Optional: Installing OMU
Applications.

BSC6900 UMTS
Procedure
l To start the omud using commands, perform the following steps:
2. Run the net start omud command to start the omud.
l To start the omud using menus, perform the following steps:
1. Choose Start > Settings > Control Panel to type the control panel interface.
2. Double-click Administrative Tools > Services to type the Services interface, as
Figure 5-50 Services interface (for starting the omud)
3. Select omud.
4. Click the icon on the toolbar to start the omud.

5. When the Status of omud is Started, close the Services interface.
----End
Stopping the omud

This section describes how to stop the omud so that the OMU stops providing services.
Prerequisites

BSC6900 UMTS
Applications.
Context
CAUTION
l When the omud is stopped, all the OMU service processes will also stop. In turn, the OMU
stops providing services for the BSC6900. Therefore, perform this task with caution.
l If a fixed external IP address is configured for the OMU, stopping the omud will make the
virtual external IP address ineffective. In this situation, a user can log in to the OMU by using
the fixed external IP address if an independent OMU is configured. If the OMUs work in
active/standby mode, the virtual external IP address of the original standby OMU becomes
effective after the active OMU is stopped.
l If no fixed external IP address is configured for the OMU, the virtual external IP address is
still effective after you stop the omud.
Procedure
l To stop the omud through commands, do as follows:
2. Type the net stop omud command and press Enter to stop the omud.
l To stop the omud through menus, do as follows:
1. Choose Start > Settings > Control Panel to type the control panel interface.
2. Double-click Administrative Tools > Services to type the Services interface, as

BSC6900 UMTS
Figure 5-51 Services window (for stopping the omud)
3. Select omud.
4. Click the icon on the toolbar to stop the omud.

5. When the Status of omud is blank, close the Services interface.
----End
Uninstalling the OMU Applications

This section describes how to uninstall the OMU applications.
Prerequisites
Applications.
Context
l If OMU applications are installed on both the active and standby OMU workspaces,
uninstall the OMU applications on the standby workspace before uninstalling them on the
active workspace.
l When the BSC6900 is configured with active and standby OMUs, uninstall the OMU
applications on both the active and standby OMUs.
l If there is only the active workspace on the OMU, the system will prompt you to uninstall
only the OMU applications on the active workspace.

BSC6900 UMTS
NOTE
Uninstalling the OMU applications from an OMU will cause all the data in the OMU to be lost. You are advised
to back up system data on the OMU before the uninstalling by referring to Backing Up the System Data.
Procedure
Step 1 Log in to the standby OMU by using the fixed external IP address or the commissioning IP
address. For details, see Logging In to the OMU.
of the OMU..
Step 3 Type the net stop omud command and press Enter to stop the omud..
Step 4 Click Start > Run and the Run interface is displayed.
Step 5 In the Run interface, run the uninstall_bam command and click OK.
If... Then...
The OMU applications are installed in only An interface is displayed, as Figure 5-52
the active workspace shows.
The OMU applications are installed in both An interface is displayed, as Figure 5-53
the active and standby workspaces shows.
Figure 5-52 cmd interface for uninstallation 1

BSC6900 UMTS
Figure 5-53 cmd interface for uninstallation 2
Step 6 Type Y, and press Enter until the Uninstall OMU succeed! message is displayed.
If... Then...
The OMU applications are installed only OMU applications are uninstalled. This task is
in the active workspace completed.
The OMU applications are installed in 1. Go to Step 5 after uninstalling the OMU
both the active and standby workspaces applications in the standby workspace.
2. Perform Step 6 to uninstall the OMU
applications in the active workspace. This
task is completed.
Step 7 Log in to the active OMU using the fixed external IP address or commissioning IP address. Then
perform Step 2 through Step 6 again.
----End
5.2.25 Backing Up and Restoring Data

This section describes how to use the omu_backup_linker tool to back up and restore the data
related to the OMU configuration, alarms, and performance. When the OMUs work in active/
standby mode, the omu_backup_linker tool can be used only on the active OMU. Otherwise,
the data may be lost.
Context
The omu_backup_linker tool is used in the following scenarios:

BSC6900 UMTS
l When an OMUa board is damaged, it needs to be replaced with a new one. The data on the
damaged OMUa board needs to be backed up and restored on the new OMUa board.
l The OMU data needs to be backed up in routine maintenance.
l When the OMU database collapses or an OMU upgrade fails, the latest OMU data is
restored by using the omu_backup_linker tool.
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
of the OMU.
Step 3 Type the cd /d d:\mbsc\bam\common\services command and press Enter to navigate to the
directory where the program of the omu_backup_linker tool is saved.
Step 4 Type the omu_backup_linker.exe command and press Enter. An interface is displayed, as
Figure 5-54 Starting the omu_backup_linker Tool

BSC6900 UMTS
----End
Backing Up the System Data

This section describes how to back up the BSC6900 configuration data, performance data, and
alarm data by using MML commands or the omu_backup_linker tool.
Prerequisites
l Prerequisites for the backup by using MML commands:
You have logged in to the LMT. For details, see Logging In to and Logging Out of the
LMT.
l Prerequisites for the backup by using the omu_backup_linker tool:
Context
CAUTION
l When the OMU works in active/standby mode, the system data must be backed up on the
active OMU.
l You must back up the OMU data manually to avoid a system data backup failure before
capacity expansion, upgrade, or a software loading.
Procedure
l Backing up the system data through an MML command
1. Run the BKP DB command with Path of Backup File and Backup File Name set to
appropriate values to back up the data in the specified directory on the OMU hard
disk.
2. Obtain the backup data file from the specified directory by referring to Transferring
OMU Files to a Local PC.
l Backing up the data by using the omu_backup_restore_tool
2. Type the cd /d d:\mbsc\bam\common\services command and press Enter to
navigate to the directory where the program of the omu_backup_linker tool is
saved..
3. Type the backup command and press Enter in the interface, as shown in Figure
5-55.

BSC6900 UMTS
Figure 5-55 Backing up the system data
4. Type the save path and names of the backup files, and then press Enter. The system
data starts to be backed up. After the backup is complete, a message is displayed,
indicating whether the backup is successful. If the backup is successful, the message
"Backup OMU database succeed!" is displayed on the interface, as shown
in Figure 5-56.
Figure 5-56 Backup result

BSC6900 UMTS
5. Press any key to exit.
----End

This section describes how to restore system data by using a data backup file.
Context
Restoring the BSC6900 system data will interrupt services on the BSC6900. After the system
data is restored, the data on the host will be inconsistent with the data on the OMU. As a result,
services will be greatly impacted. Therefore, you are advised to restore the system data in the
early morning hours when traffic volume is low.
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.
l If the backup restoration tool is used to restore data, all BSC6900 data is restored, including
configuration data, alarm data, performance data, operating logs, administrator account,
authority information, and product information.
NOTE
This document uses the OMU in active/standby mode as an example. If an OMU is in independent mode, skip
operations on the standby OMU.
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.
l Restoring the system data by using the omu_backup_restore_tool
1. (Optional) If the OMUs work in active/standby mode, stop the data synchronization
between the active and standby OMUs by referring to 5.2.14 Stopping the
Synchronization of the Data of the Active and Standby OMUs
2. Log in to the active and standby OMUs by referring to 5.2.20 Logging In to the
OMU.
command mode of the OMU. on the active and standby OMUs.
4. Type the net stop omud command and press Enter 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 type the cmd command and press Enter to type the
b. Type the cd /d d:\mbsc\bam\common\services command and press Enter to
navigate to the directory where the program of the omu_backup_linker tool is
saved..

BSC6900 UMTS
c. Type the omu_backup_linker.exe command and press Enter to start the

d. Type the restore command on the interface and press Enter, as shown in Figure
5-57.
Figure 5-57 Restoring system data
e. Enter the save path and names of the backup files and press Enter. The system
data starts to be restored. The interface informs you of the result. If the system
data is restored successfully, the message Restore OMU database
succeed! is displayed on the interface, as shown in Figure 5-58.

BSC6900 UMTS
Figure 5-58 Result indication of restoring the system data
f. 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 5.2.19 Uploading Files to the OMU.
7. Repeat Step 5 to restore data in the original backup OMU using the
8. Starting the omud on the active and standby OMUs.
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 no, load the restored data to the BSC6900 host boards.
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.
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 with Subrack No. specified to reset this subrack. If data inconsistency
occurs in multiple subracks, run the RST BSC command to reset the BSC.
11. (Optional, required only for Step 1) Run the MML command STR DATASYNC to
start data synchronization between the active and standby OMUs.
----End

BSC6900 UMTS
5.2.26 Using the omutool

This section describes how to use the omutool to modify the configuration data of the active and
standby OMUs, including the OMU working mode, IP addresses and subnet masks of the internal
and external networks, and admin password.
Starting the omutool

This section describes how to start the omutool on the OMU. When the OMU works in active/
standby mode, you should log in to the active or standby OMU, and start the omu_backup_linker
tool.
Prerequisites
Applications.
Procedure
of the OMU.
Step 3 Enter the cd /d d:\mbsc\bam\version_a\bin\bam command and press Enter to navigate to the
directory where the program of the omutool is saved.
Step 4 Type the omutool.exe command and press Enter to start the omutool.
Step 5 Enter the omutool -h command and press Enter to view the help information.
----End
Setting the OMU Working Mode

This section describes how to set the OMU working mode by using the omutool. The OMU can
work either in independent or active/standby mode.
Prerequisites
l You have logged in to the LMT, and queried the slot No. for the OMU by running the LST
BRD command.
l You have logged in to the LMT, and queried whether the OMU is in single-OMU or dual-
OMU mode by running the DSP OMU command.
l You have logged in to the LMT, and queried the OMU version and workspace information
by running the LST OMUAREA command.
l You have logged in to the LMT and queried the OMU service mode by running the LST
MBSCMODE command.

BSC6900 UMTS
Context
l If the working mode is changed from independent mode to active/standby mode, apply the
settings to both the active and standby OMUs. If the working mode is changed from active/
standby mode to independent mode, apply the settings to only the new active OMU.
l If the working mode of the OMU is changed from independent mode to active/standby
mode, ensure that the operating system, software version, and board type of the active
OMU are the same as those of the standby OMU. In addition, the slot number of the active
OMU and that of the standby OMU have an active/standby relationship.
l If the working mode of the OMU is changed from active/standby mode to independent
mode, you should run the MML command DSP OMU to ensure that the Data-sync
state is Data synchronization is successful and run the MML command
CMP OMUFILE to ensure that Compare result is consistent.
Procedure
applications are not installed on the OMU to be added).
1. Insert an OMUa/OMUc board into the standby slot by referring to Installing the
OMUa/OMUc/SAUa/SAUc Boards or Installing the OMUc Boards in the BSC6900
UMTS Installation Guide.
2. Log in to the standby OMU using the fixed external IP address by referring to 5.2.20
3. Install OMU applications on the standby OMU. For details, see 5.1.3 Optional:
Installing OMU Applications.
NOTE
You must select active/standby mode in the process of installing the OMU applications for the
standby OMU.
fixed internal IP addresses, fixed external IP addresses, IP address of the backup
Subnet Masks.
command mode of the OMU. on the original active OMU.
6. Type the net stop omud command and press Enter to stop the omud. on the original
active OMU.
7. Enter the cd /d d:\mbsc\bam\version_a\bin\bam command and press Enter to
navigate to the directory where the program of the omutool is saved on the original
active OMU.
8. Run the omutool dualmode dual command on the original active OMU to set the
9. Run the net start omud command to start the omud on the original active OMU.
10. Five minutes after the original active OMU has been started, start the omud on the
standby OMU.

BSC6900 UMTS
WARNING
active OMU by referring to 5.2.8 Changing the Administrator Password for the
Operating System.
12. Run the ADD BRD command on the LMT to add an OMUa or OMUc board.
applications are installed on the OMU to be added).
1. Log in to the original active OMU by using the fixed external IP address by referring
to 5.2.20 Logging In to the OMU.
command mode of the OMU. on the original active OMU.
3. Type the net stop omud command and press Enter to stop the omud. on the original
active OMU.
navigate to the directory where the program of the omutool is saved on the original
active OMU.
5. Run the omutool dualmode dual command on the original active OMU to set the
6. Run the net start omud command to start the omud on the original active OMU.
7. Insert an OMUa/OMUc board in the standby slot 5 minutes after the original active
OMU is started.
WARNING
8. Set the working mode of the standby OMU to active/standby mode by repeating Step
1 through Step 5.
fixed internal IP addresses, fixed external IP addresses, IP address of the backup
Subnet Masks.
10. Start the omud on the standby OMU.

BSC6900 UMTS
active OMU by referring to 5.2.8 Changing the Administrator Password for the
Operating System.
12. Run the ADD BRD command on the LMT to add an OMUa or OMUc board.
l Change the working mode of the OMU from active/standby mode to independent mode.
1. Run the RMV BRD command on the LMT to remove an OMUa or OMUc board.
2. Log in to the active and standby OMUs by using the fixed external IP address by
referring to 5.2.20 Logging In to the OMU.
command mode of the OMU. on the active and standby OMUs.
4. Type the net stop omud command and press Enter to stop the omud. on the active
and standby OMUs.
5. Run the poweroff command on the OMU to be removed to power off the OMU.
6. Remove the OMUa/OMUc board to be removed by referring to step 2 to step 5
inScenario: Old and New OMU Boards Running the Same OS.
navigate to the directory where the program of the omutool is saved on the active
OMU.
8. Run the omutool dualmode single command on the working OMU to set the working
mode of the OMU to single-OMU mode.
9. Run the net start omud command to start the omud on the active OMU.
----End
Changing IP Addresses of OMU Ethernet Adapters and Their Subnet Masks

This section describes how to change IP addresses and subnet masks of the OMU Ethernet
adapters using omutool.
Context
If the OMU is in active/standby mode, change the IP addresses and subnet masks of the Ethernet
adapters on both the active and standby OMUs. You are advised to first change the IP addresses
and subnet masks of the Ethernet adapters for the standby OMU before changing those for the
active OMU.
NOTE
This task describes how to change all the IP addresses and subnet masks for the OMU. You can perform required
steps to fit onsite needs.
l Single-OMU mode: Stop the omud before the change and start the omud after the change.
l Dual-OMU mode: Stop the standby omud and then the active omud before the change. Start the active omud
and then the standby omud after the change.
For details about the Ethernet adapter binding relationship, see 3.1 OMU Ethernet Adapter
Configuration.

BSC6900 UMTS
Procedure
Step 1 Log in to the OMU by referring to 5.2.20 Logging In to the OMU.
of the OMU..
Step 5 The omutool dispipinfo command is used to query the IP address and subnet mask of the OMU.
For example, type the following command and press Enter to query the IP address and subnet
mask of the OMU:
omutool dispipinfo
Step 6 The omutool innercard IP address command is used to change the fixed internal IP address.
For example, type the following command and press Enter to change the fixed internal IP
address:
omutool innercard 80.168.3.60
Step 7 The omutool innervip IP address is used to change the virtual internal IP address.
For example, type the following command and press Enter to change the virtual internal IP
address:
omutool innervip 80.168.3.40
NOTE
of the fixed internal IP address is changed to be different from that of the virtual internal IP address, you are
prompted to change the virtual internal IP address. If the network segment of the internal IP address is
changed to be different from that of the fixed internal IP address, you are prompted to change the fixed
internal IP address.
l When you change the fixed and virtual internal IP addresses, the corresponding subnet masks are created
automatically.
l If you change the fixed and virtual internal IP addresses for the first time, perform the following additional
steps:
1. Run the SET SUBNET command to set the BSC6900 subnet number so that it is consistent with the
number of the network segments on which the fixed internal IP address and virtual internal IP address
are located.
2. Remove the SCUa board and reinstall it in the MPS. Then, reset the MPS to validate the new fixed and
virtual internal IP addresses.
l After these two steps are performed, the OMU can communicate with the BSC6900 host boards normally.
Step 8 The omutool extercard IP address subnet mask (gateway IP address) command is used to
change the fixed external IP address and subnet mask.
For example, type the following command and press Enter to change the fixed external IP
omutool extercard 10.161.10.100 255.255.255.0

BSC6900 UMTS
CAUTION
Before changing the fixed external IP address, virtual external IP address, and external gateway
IP address, log in to the OMU using the commissioning IP address.
Step 9 The ./omutool extervip IP address subnet mask (gateway IP address) command is used to
change the virtual external IP address and subnet mask.
For example, type the following command and press Enter to change the virtual external IP
omutool extervip 10.161.10.102 255.255.255.0
NOTE
l After the virtual external IP address and mask are changed, run the RMV EMSIP command and then the
ADD EMSIP command to update the virtual external IP address and mask that are recorded in the OMU
database.
of the fixed external IP address is changed to be different from that of the virtual internal IP address, you
are prompted to change the virtual external IP address. If the network segment of the virtual external IP
address is changed to be different from that of the fixed external IP address, you are prompted to change the
l After the fixed external IP address, virtual external IP address, and gateway IP address are changed, the
communication between the OMU and peripheral equipment is interrupted. You need to use the new fixed
or virtual external IP address to reconnect the OMU and peripheral equipment.
Step 10 The omutool gateway gateway IP address command is used to change the gateway IP address.
For example, type the following command and press Enter to change the gateway IP address:
omutool gateway 10.161.10.1
NOTE
You can change the fixed or virtual external IP address simultaneously with changing the gateway IP address.
The following are the related commands:
l omutool extercard IP address Subnet mask Gateway IP address for changing the fixed external IP address
l omutool extervip IP address Subnet mask Gateway IP address for changing the virtual external IP address
Step 11 Change the backup channel IP address of the active and standby OMUs by using the commands
listed in the following table:
Option Description
Backup channel IP address of the omutool backupcard IP address.

Example: type the following command and press
Ethernet adapter ETH3-UPDATE of
the OMUa board omutool backupcard 192.168.3.60
Backup channel IP address of the omutool backupcard IP address.

OMUc board omutool backupcard_for_omuc 192.168.9.60

BSC6900 UMTS
Option Description
Backup channel IP address of the omutool backupcard_for_omua IP address.

OMUc board omutool backupcard_for_omua 192.168.3.60
Step 12 The omutool debugcard IP address command is used to change the commissioning IP
address.
For example, type the following command and press Enter to change the commissioning IP
address:
omutool debugcard 192.168.6.60
NOTE
l After you change backup channel IP address and commissioning IP address of the active and standby
OMUs, the corresponding subnet mask will be created automatically.
l To change the IP addresses of the OMU, you must follow the principle of IP address planning. For
details, see 3.2 OMU IP Address Plan. When entering the command, leave a space between the IP
address and the subnet mask.
l Record the new IP addresses in 5.5.1 Record Sheet of OMU Software Installation Information.
Step 13 Run the net start omud command to start the omud.
----End

This section describes how to change the passwords for users admin, root, and db_user by using
the omutool and how to change the password for user FtpUsr by using the MML command.
Context
l admin is the account for logging in to the LMT.
l db_user and root are the accounts for accessing the OMU database.
l FtpUsr is the account for uploading and downloading files to and from the OMU.
If active and standby OMUs are configured on the BSC6900, you must change the passwords
used by the admin, db_user, and root user on both the active and standby OMUs.
It is assumed that version_a is the OMU active workspace in this operation.
NOTE
three months.
of 32 characters.

BSC6900 UMTS
Procedure
l Changing the password used by admin
command mode of the OMU..
3. Type the net stop omud command and press Enter to stop the omud..
navigate to the directory where the program of the omutool is saved.
5. Run the omutool adminpwd command to change the admin password.
l Changing the password used by root
5. Run the omutool dbrootpwd command to change the root password.
l Changing the password used by db_user user
5. Run the omutool dbpwd command to change the password of the db_user user.
l Changing the password used by FtpUsr user
2. Run the MML command MOD FTPPWD to change the password used by FtpUsr
user.
----End
Example
The following shows an example for changing the password used by admin:
D:\mbsc\bam\version_a\bin\bam>omutool adminpwd
Enter a password or press Ctrl+Break to quit:
Re-enter password or press Ctrl+Break to quit:
Successfully set the admin user's password!
The following shows an example for changing the password used by root:

BSC6900 UMTS
D:\mbsc\bam\version_a\bin\bam>omutool dbrootpwd
Successfully set the root's password of the database!
The following shows an example for changing the password used by db_user user:
D:\mbsc\bam\version_a\bin\bam>omutool dbpwd
Successfully set the db_user's password of the database!

This section describes how to change the computer name by using omutool.
Context
l Generally, the computer name and IP addresses are planned by the operator. You need to
change the computer name and IP addresses by using the omutool after installing the OMU
applications onsite. For information about how to change the OMU IP addresses, see
Changing IP Addresses of OMU Ethernet Adapters and Their Subnet Masks.
l If the BSC6900 is configured with active and standby OMUs, name them differently.
Procedure
of the OMU..
Step 5 Run the omutool hostname Computer name command to change the computer name.
For example, to change the computer name to omu_123, type the omutool hostname
omu_123 command and press Enter.
Step 6 Run the net start omud command to start the omud.
----End
Follow-up Procedure
2. Run the DSP OMU command to query the new computer name.
Modifying the NE Type

This section describes how to modify the NE type by using the omutool.

BSC6900 UMTS
Context
To manage BSCs uniformly on the M2000, you need to modify the NE type of upgraded BSCs.
The following procedure is for active and standby OMUs whose active workspace is
version_a. For a single OMU, ignore the steps for the standby OMU.
Procedure
Step 1 Log in to the standby OMU first and stop the omud process on it. Then, log in to the active OMU
and stop the omud process on it. For details, see 5.2.20 Logging In to the OMU and Stopping
the omud.
Step 2 Choose Start> > Run on the active OMU. Type the cmd command and press Enter to type the
Step 3 Type the cd /d d:\mbsc\bam\version_a\bin\bam command and press Enter to navigate to the
directory where the omutool program is saved.
Step 4 Type the omutool netype command followed by the new value of the NE type parameter on
the active OMU. Press Enter to modify the NE type.
The prompt set ne type success! indicates that the NE type has been successfully modified.
NOTE
Type the omutool netype command and press Enter to query the NE type.
Step 5 Start the omud process on the active and standby OMUs separately. For details, see Starting
the omud.
----End
Example
D:\mbsc\bam\version_b\bin\bam>omutool netype
Current ne type is : BSC6***
D:\mbsc\bam\version_b\bin\bam>omutool netype BSC6900
set ne type success!
5.2.27 Adjusting OMU Slots

This section describes how to move the active and standby OMUs that are originally installed
in slots 20 to 27 to other slots to reserve slots 20 to 27 for interface boards with high throughput.
Prerequisites
l The target slots for OMUs are idle and can hold OMUs. Such slots can be slots 0 to 3, slots
20 to 23, or slots 24 to 27.
l The target slots for OMUs are idle and can hold OMUs. Such slots refer to OMUa Board
or OMUc Board.
l The value of Data-sync state is Data synchronization is successful. You can run the DSP
OMU command to view the setting of Data-sync state.

BSC6900 UMTS
Procedure
Step 1 Perform different operations to shut down the OMUs based on the operating system.
If... Then...
The Suse Linux operating system or Dopra 1. Log in to the active and standby OMUs
Linux operating system is used respectively by referring to Logging In to
the OMU.
2. Run the etc/rc.d/omud stop command to
3. Run the poweroff command to shut down
the OMUs.
The Windows operating system is used 1. Log in to the active and standby OMUs
respectively by referring to 5.2.20
2. Choose Start > Run. Type cmd in the
Open text box and then press Enter. The
OMU command interface is displayed.
3. Run the net stop omud command to stop
the omud process.
4. Choose Start > Shutdown. Select
Shutdown from the drop-down list box to
shut down the OMU.
Step 2 When the OFFLINE LED on the OMU board panel is on, pull the active and standby OMUs
and insert them into the target slots.
NOTE
Insert active and standby OMUs into the target slots one by one after pulling both of them.
Step 3 Wait about five minutes, log in to the LMT. and then run the DSP OMU command to check
whether the active and standby OMUs operate properly.
Step 4 Run the LST BRD command to query the subrack number and slot numbers of the active and
standby OMUs before the switchover.
Step 5 Run the RMV BRD command to remove the original active and standby OMUs.
Step 6 Run the ADD BRD command to add new active and standby OMUs. In this step, set slot numbers
of the OMUs to the target OMU slot numbers.
Assume that the target OMU slot numbers are 21 and 23. Run the following commands:
Step 7 Check whether the OMUs are properly displayed on the device panel and whether they are in
normal state.
Step 8 Click Alarm in the home page of the LMT and view current active alarms of the BSC6900 in
the Browse Alarm tab page.

BSC6900 UMTS
Step 9 Optional: If there is an alarm related to the original OMUs in the list of active alarms, select
the alarm, right-click it, and choose Clear Alarm from the shortcut menu to manually clear the
alarm.
----End
5.3 Appendix: Antivirus Software

The OMU supports an integrated antivirus solution that uses the OfficeScan software provided
by TrendMicro. For the method of installing the antivirus software, see the antivirus software
installation guide provided by Huawei.
Installation of Antivirus Software

The Huawei antivirus solution protects the entire operation and maintenance (O&M) network.
The solution contains the antivirus software integration and antivirus policies for the OMU.
Figure 5-59 shows policies for deploying the antivirus software.
Figure 5-59 Deployment policies of antivirus software
An antivirus server is deployed independently in the Demilitary Zone (DMZ) of the OM network.
The server obtains the latest virus code or upgrade package from the Internet. The antivirus
server (for example, OfficeScan Server) on the current network is upgraded by an antivirus
upgrade server in the DMZ instead of being directly connected to the Internet. After the antivirus
server is upgraded, the virus code and upgrade package of the equipment on the entire network
are upgraded automatically.

BSC6900 UMTS
OfficeScan
OfficeScan is a web-based integrated product and it provides comprehensive security protection
for the corporate desktops. It has passed strict compatibility tests of Huawei and is compatible
with OMUs provided by Huawei.
NOTE
Log in to http://support.huawei.com/support/ using the account of a Huawei engineer, and choose

Documentation > Wireless > WCDMA-RAN > WCDMA-RNC > Technical Guides > Deployment
Guide to download the Deployment Guide to the Installation and Upgrade of OfficeScan 10.0 Server and
Client.
5.4 Appendix: Installing the iPSI SEK SetWin Software

This section describes how to install the iPSI SEK SetWin software and how to roll back the
security enhancement policies.
Context
The iPSI SEK SetWin software is a security enhancement tool for a server's operating system
(OS). This software applies to Windows Server 2003.
NOTE
The software cannot be used if the OS is switched to Dopra Linux after the BSC6810 is upgraded to the
BSC6900.
5.4.1 Running the iPSI SEK SetWin Software

This section describes how to use the iPSI SEK SetWin software to customize security policies
for the Windows operating system (OS) on the OMU.
Prerequisites
l The OMU applications have been installed.
l The Deployment Guide to WRAN Windows Device Security Policy has been obtained from
http://support.huawei.com/support/ by choosing Wireless > WCDMA-RAN > WCDMA-
RNC > Reconstruction Guide.
Context
In command line mode, the iPSI SEK SetWin software is executed using the SetWinCmd
command. The SetWinCmd command can be executed in the following ways:
l If a parameters is attached to the SetWinCmd command, perform a specified task by loading
the parameter.
l If no parameter is attached to the SetWinCmd command, select a specified task by using
the menu.

BSC6900 UMTS
CAUTION
When you run a customized policy, ensure that the imported policy is the tested customized files
and versions of the policy files, the OMU, and SetWin are compatible. If an incorrect policy or
the default system policy is imported, security problems may occur on the OMU or the OMU
becomes inaccessible.
Procedure
l If a parameter is attached to the SetWinCmd command
4. Go to the directory for the SetWin program.
Assume that the SetWin program is installed in the default path, C:\Program Files
\SetWin. Type the following command and press Enter.
cd /d C:\Program Files\SetWin
5. Import the configuration file.

Assume that the configuration file is saved in C:\Program Files\SetWin. Type the
following command and press Enter.
SetWinCmd /I=D:\setwin2003.inf
6. Type the SetWinCmd /B=C:\backup.bak command and press Enter to back up the
system policies.
CAUTION
If there is no special requirement, the backup file is saved in the default directory. The
backup file is used for rollback if the operation fails. Reserve the backup file with
caution.
7. Type the SetWinCmd /X command and press Enter to execute all the policies.
NOTE
The SetWinCmd command handles the parameter items in the sequence of command input.
For details about the parameters of the SetWinCmd command, see Table 5-8.
8. When the customization is completed, restart the operating system.
l If no parameter is attached to the SetWinCmd command
4. Go to the directory for the SetWin program.
Assume that the SetWin program is installed in the default path, C:\Program Files
\SetWin. Type the following command and press Enter.
cd /d C:\Program Files\SetWin

BSC6900 UMTS
5. Type the SetWinCmd command and press Enter. The system backup window is
displayed. Enter y in the window.
6. The system indicates a message asking you whether to enter a name for the backup
file. Enter y.
7. Type the name of the backup file and press Enter. The system starts the initial backup,
as shown in Figure 5-60. After the initial system backup is completed, an interface is
displayed, as shown in Figure 5-61. Table 5-8 shows task descriptions of the
command lines.
Figure 5-60 System backup

BSC6900 UMTS
Figure 5-61 SetWin command lines
Table 5-8 Tasks supported by the SetWin command lines

Operat Task Menu Description Parameter
ion
Seque
nce
1 Generate License Used to generate a license request /G

Request file in the SetWin installation
folder to obtain the license.
2 Import License Used to import a specified license /

file. L=<filename>
3 Show Version Used to export version /V

information to the console.
4 Import Used to import a specified /I=<filename>

Configuration configuration file.
5 Export Used to export a specified /

Configuration configuration file. E=<filename>
6 Execute Used to execute all the policies /X

according to the current
configuration.

BSC6900 UMTS
Operat Task Menu Description Parameter

ion
Seque
nce
7 Rollback Used to roll back all the policies /

according to the current R=<filename>
configuration and the provided
rollback files.
8 Backup Used to generate the backup file /

for the system policies. B=<filename>
9 Exit Used to exit from the SetWin -

program.
8. Type 1 and press Enter to generate the license registration file.

NOTE
Only the user with a formal license can use the SetWin software. The license in the installation
package is valid for 30 days. If the trial expires, a user must apply for a formal license to continue
the usage.
9. Send the license registration file and the license application form to Huawei. Huawei
engineers will provide a formal license according to the registration file.
10. Type 2 (importing the license). Then type the valid license file name and press
Enter to import the formal license file provided by Huawei engineers. The file type
is *.zip.
11. Type 4 (importing the configuration file). Then type the configuration file name and
press Enter. The file type is *.inf. The system displays the message, Are you sure(y/
n)?
CAUTION
The configuration file must pass the product test. The name of the configuration file
is in the form of setwin plus operating system type, for example, setwin2003.inf.
12. Type y. The system automatically imports the configuration file.

13. After the configuration file is successfully imported, type 8 (backing up the policies).
Then type the backup file name and press Enter.
14. After the backup is completed, type 6 (executing the policies). The system displays
the message again, Are you sure(y/n)?
15. Type y. After the customization is completed, restart the operating system.
NOTE
If the OMU cannot work normally after the operating system is customized by using the iPSI
SEK SetWin software, refer to 5.4.2 Rolling Back Security Enhancement Policies During
the Use of the SEK SetWin Software for troubleshooting.
----End

BSC6900 UMTS
5.4.2 Rolling Back Security Enhancement Policies During the Use

of the SEK SetWin Software
When a PC cannot work normally after the operating system is customized by using the iPSI
SEK SetWin software, you can roll back the security enhancement policies for the operating
system.
Procedure
Step 1 Log in to the OMU by referring to 5.2.20 Logging In to the OMU. Click Start > Run and the
Run interface is displayed.
Step 2 Type cmd in the Open area and click Confirm. The cmd command line interface (CLI) is
displayed.
Step 3 Go to the directory for the SetWin program.

Assume that the SetWin program is installed in the default path, C:\Program Files\SetWin.
Type the cd /d C:\Program Files\SetWin command and press Enter.
Step 4 Run the rollback command. Assume that the backup file is saved in the C:\SetWin\config
directory and its file name is 1.bak. Type the SetWinCmd /R=C:\SetWin\config\1.bak
command and press Enter.
Step 5 When the rollback is completed, restart the operating system.
----End

5.5.1 Record Sheet of OMU Software Installation Information

The information record sheet of OMU software installation records information regarding the
parameter configurations during the OMU software installation.
Record Sheet of OMU Operating System Installation Information

Item Setting Information Installation Personnel
Computer name (active

OMU)
(active OMU)
Computer name (standby

OMU)
(standby OMU)

BSC6900 UMTS
For details, see Record Sheet of OMU Operating System Installation Information (Upgrade
from BSC6810 to BSC6900).
Records of IP Addresses of the OMU Ethernet Adapter Teams






OMU

OMU
OMU
OMU
Default gateway
For details, see Records of IP Addresses of the OMU Ethernet Adapter Teams (Upgrade
from BSC6810 to BSC6900).
Records of the OMU Application Installation Information

Administrator (admin)
password
Password of the FTP user

(FtpUsr)
Internal virtual IP address
External virtual IP address

BSC6900 UMTS
Local office name
For details, see Records of the OMU Application Installation Information (Upgrade from
BSC6810 to BSC6900).
5.5.2 Checklist for Factory Settings of the OMU Software

This section provides a checklist for the OMU software factory settings. The checklist records
the OMU software installation and configuration information before delivery.
Checklist for factory settings of the OMU software

Item Status
RAID 1 between the two SAS hard disks on Set

the OMUa board
Windows Server 2003 Installed with the administrator passwords of

the active and standby OMUs set to 11111111
License for Windows Server 2003 Activated
IPMI driver Installed
Memory diagnosis driver based on Windows Installed
Routing and Remote Access service Started with Start Type set to Automatic.
The processes DHCP Relay Agent and
NAT/Basic Firewall are removed by default
before the OMU is delivered. If the processes
are started during the OMU maintenance,
they must be removed after choosing Start >
All Programs > Administrative tools >
Routing and Remote Access.
Windows Time service Disabled
Computer Browser service Disabled
Terminal Services Started with Start Type set to Automatic.
Remote login property Enabled
Intel 82571 Ethernet adapter binding driver Installed
BACS Ethernet adapter binding driver Installed

BSC6900 UMTS
Item Status
Debugging IP addresses of the active and Set

standby OMUs The default commissioning IP addresses of
the active OMU is 192.168.6.50
(255.255.255.0).
The default commissioning IP addresses of
the standby OMU is 192.168.6.60
(255.255.255.0).
iPSI SEK SetWin software Installed
For details, see Checklist for Factory Settings of the OMU Software (Upgrade from
BSC6810 to BSC6900).

This section provides the list of enabled ports on the OMU. The list describes the mapping
between enabled ports on the OMU and services provided by the OMU applications.
List of enabled ports on the OMU

Port No. Service Process Description
20 FTP server data Port for host loading, and uploading and
downloading software and logs (in active mode)
21 FTP server control Port for host loading, and uploading and
downloading software and logs
1024-65535 FTP server data Port for host loading, and uploading and
downloading software and logs (in passive
mode)
80 Web LMT Port connected to the LMT for BSC6900 local

maintenance
123 sntp Port for synchronizing the time of the OMU

with that of the server and provides local
interception
443 Web LMT Port for establishing an encryption connection

between a browser and the LMT to enable
BSC6900 maintenance
3389 - Port for Windows remote desktop
6000 ems_gate Port for maintenance
6001 ems_gate Port for the alarm console
6006 ems_gate Port for maintenance

BSC6900 UMTS
Port No. Service Process Description
6088 Remote upgrade tool Port for the remote upgrade tool
6099 ems_gate Port for configuration change informing

message. This port is connected only to the
M2000.
6100 ems_gate Port for the alarm box
6200 ems_gate Port for the VNP
8000 ems_gate Port for maintenance (SSL encryption)
8001 ems_gate Port for alarm console (SSL encryption)
8006 ems_gate Port for maintenance (SSL encryption)
8088 Remote upgrade tool Port for the remote upgrade tool (SSL
encryption)
8099 ems_gate Port for configuration change informing

message. This port is connected only to the
M2000. (SSL encryption)
8100 ems_gate Port for the alarm box (SSL encryption)
8200 ems_gate Port for the Vendor Network Probe (VNP) (SSL
encryption)
11775 monitor Port for monitoring the external network

heartbeat between the active/standby OMU and
peripherals.
16002 ems_gate Port through which the performance module

reports notification messages. This port is
connected only to the M2000.
18002 ems_gate Port through which the performance module

reports notification messages. This port is
connected only to the M2000. (SSL encryption)
For details, see Enabled Ports on the OMU (Upgrade from BSC6810 to BSC6900).
5.5.4 List of Disabled Ports on the OMU

For the sake of OMU security, the OMU automatically closes the ports that are not used.
Protocol Port No. Service Description
TCP 135 Port 135 is used for services that comply with the
Remote Procedure Call (RPC) protocol and for
the Distributed Components Object Mode
(DCOM) services.

BSC6900 UMTS
Protocol Port No. Service Description
UDP 138 Port 138 is used for the NetBIOS browsing. It is

used to display all the PCs in the network.
UDP 139 Port 139 is used for the NetBIOS Session

Service, enabling the sharing of files in PCs
running Windows and printer and providing the
Samba service in the Unix system. To share files
on PCs running Windows in the LAN, the
service must be used.
UDP 445 Port 445 is used for the NetBIOS Session

Service, enabling the sharing of files in PCs
running Windows and printer and providing the
Samba service in the Unix system. To share files
on PCs running Windows in the LAN, the
service must be used.
For details, see Disabled Ports on the OMU.

BSC6900 UMTS
OMU Administration Guide 6 Appendix: Security FAQ
6 Appendix: Security FAQ
About This Chapter
This section describes how to improve the security of the BSC6900.

This section describes how to disable root user login with SSH to security-harden the
BSC6900.
6.2 Disabling OMU route forwarding
This section describes how to disable OMU route forwarding to security-harden the BSC6900.
6.3 Enhancing Security of Time Synchronization with NTP
The security of time synchronization with Network Time Protocol (NTP) is enhanced for the
BSC6900 after NTP messages are authenticated.
6.4 Configuring the Function of Recording OMU OS Accessing Information in Real Time
This section describes how to configure the function of recording OMU operating system (OS)
accessing information in real time when users log in to or out of the OMU OS. This function
helps monitor the OMU OS security.
6.5 Enabling Function of Checking OS File Integrity
This section describes how to enable the function of checking the operating system (OS) file
integrity. This function is for monitoring the security of the OMU OS.

BSC6900 UMTS

This section describes how to disable root user login with SSH to security-harden the
BSC6900.
Prerequisites
l The currently-running software version is BSC6900V900R013C00SPH529 or later.
l The OMU is running properly.
Context
This operation only applies to Dopra Linux V2.
version_a as the OMU active workspace is used as an example in this operation. To query the
current OMU active workspace, run the LST OMUAREA command.
Procedure
l Disabling root user login with SSH
NOTE
l Ensure that a new non-root user account has been created before disabling root userlogin with SSH.
Otherwise, the operation fails.
l After root user login with SSH is disabled, the current user will not be logged off automatically. A
new login will be disabled.
l If the OMU operating system version is V200R003C02SPC090 or later, the root user is forbidden by
default while the lgnusr user is added as the default account. To query the OMU operating system
version, run the LST VER command.
1. Log in to the OMU as a root user. For details, see Logging In to the OMU.
directory where the root_login.sh script is saved.
3. Enter the chmod +x root_login.sh command and press Enter to make the
root_login.sh script executable.
4. Enter the ./root_login.sh disable command and press Enter. The message Disable
root user login, are you sure? [y/n]: is displayed. Enter y and press Enter to disable
root user login.
l Adding a common user account
1. Log in to the OMU as a root user.
2. Enter the useradd -m User Name command and press Enter to add a non-root user
account.
3. Enter the passwd Password command and press Enter to set the password.
4. Confirm the password. The non-root user account is added.

BSC6900 UMTS
WARNING
Save information about the added non-root user account promptly for future use. If
this information is lost and the root user login with SSH has been disabled, you cannot
log in to the OMU remotely. In this situation, you must connect a keyboard with a
USB port to the USB port of the OMU and log in to the OMU as the root user to add
a common user, or use a USB flash drive to reinstall the operating system.
l Changing password for common user or lgnusr user

1. Log in to the OMU as a common user or lgnusr user.
2. Enter the command passwd and press Enter. You are prompted to type the password.
3. Enter the common user password. The user password is changed.
It is recommended that you change the password at your first login and then change
the password every three months.
The users password must both contain the combination of the following:
At least one lower-case letter
At least one upper-case letter
At least one digit
At least one special character -?[]_+{}
The user password must have a minimum length of 8 characters and maximum
length of 32 characters.
l Switching from a common user account or a lgnusr user account to a root user account
2. Enter the command su and press Enter. You are prompted to type the password.
3. Enter the root user password and press Enter to switch the user account from common
user or lgnusr user to root user.
l Querying user information on the OMU
1. Log in to the OMU as a common user, lgnusr user or root user.
2. Enter the cat /etc/passwd command and press Enter to query the information of all
users.
l Deleting a non-root user account
NOTE
l To delete a non-root user account, you must have a root user account.
l A non-root user account cannot be deleted while in use.
l If there is not any common user who is allowed for login with SSH, the lgnusr user is not allowed to
be deleted.
1. Log in to the OMU as a common, lgnusr user or root user.
NOTE
If you have logged in as a non-root user, re-log in as a root user before deleting a non-root user
account.
2. Enter the userdel -r User Name command and press Enter to delete the account.
l Enabling root user login with SSH

BSC6900 UMTS
2. Switch the account of a common user or lgnusr user to that of a root user.
directory where the root_login.sh script is saved.
5. Enter the ./root_login.sh enable command and press Enter. The message Enable
root user login, are you sure? [y/n]: is displayed. Enter y and press Enter to enable
root user login.
l Querying the status of the root user login
1. Log in to the OMU as a root user.
2. Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to switch the
current directory to the directory where the root_login.sh script is saved.
4. Enter the ./root_login.sh status command and press Enter to query the status of the
root user login with SSH.
NOTE
Parameter description
l Configuration status indicates the root user status to be configured.
l Actual status indicates the current root user status.
l enabled indicates that the root user login with SSH is enabled. disabled indicates that the root
user login with SSH is disabled.
----End
Example
The following is used as an example for disabling root user login with SSH to the OMU.
omucc_68 / # cd /mbsc/bam/version_a/bin/bam
omucc_68 /mbsc/bam/version_a/bin/bam # chmod +x root_login.sh
omucc_68 /mbsc/bam/version_a/bin/bam # ./root_login.sh disable
Disable root user login, are you sure? [y/n]:y
Disabling root user login done
The following is used as an example for creating a non-root user omu123 account.
omucc_68 / # useradd -m omu123

omucc_68 / # passwd omu123
Changing password for omu123.
New UNIX password: Retype new UNIX password:
The following is used as an example for changing password for common user or lgnusr user.
omucc_68 / # passwd
Changing password for eric.
Old Password:
New Password:
Reenter New Password:
Password changed.
The following is used as an example for switching an account from common user or lgnusr user
to root user.

BSC6900 UMTS
omucc_68 / $ su
Password:
omucc_68 / #
The following is used as an example for querying user information on the OMU.
omucc_68 / # cat /etc/passwd

root:x:0:0:root:/root:/bin/bash
omu123:x:1001:100::/home/omu123:/bin/bash
The following is used as an example for deleting a non-root user account.
omucc_68 / # userdel -r omu123
The following is used as an example for enabling root user login with SSH to the OMU.
omucc_68 / $ su
Password:
omucc_68 /mbsc/bam/version_a/bin/bam # ./root_login.sh enable
Enable root user login, are you sure? [y/n]:y
Enabling root user login done
omucc_68 /mbsc/bam/version_a/bin/bam #
The following is used as an example for querying the status of the root user login with SSH.
omucc_68 /mbsc/bam/version_a/bin/bam # ./root_login.sh status
Configuration status: enabled Actual status: enabled
Follow-up Procedure
1. Record the information of the new non-root user and the status of the root user login with
SSH.
6.2 Disabling OMU route forwarding

This section describes how to disable OMU route forwarding to security-harden the BSC6900.
Prerequisites
l The currently-running software version is BSC6900V900R013C00SPH529 or later.
l The OMU is running properly.
Context
This operation only applies to Dopra Linux V2.
version_a as the OMU active workspace is used as an example in this operation. To query the
current OMU active workspace, run the LST OMUAREA command.
Procedure
l Disabling OMU route forwarding

BSC6900 UMTS
NOTE
l If NodeBs are maintained by using the M2000 remotely in the live network, do not disable the OMU
route forwarding. Otherwise, the remote operation and maintenance (O&M) channels for NodeBs fail.
l The OMU route forwarding is enabled by default.
1. Log in to the OMU. For details, see Logging In to the OMU.
directory where the ip_forward.sh script is saved.
ip_forward.sh script executable.
4. Enter the ./ip_forward.sh disable command and press Enter to disable the OMU
route forwarding.
l Enable OMU route forwarding.
1. Log in to the OMU.
4. Enter the ./ip_forward.sh enable command and press Enter to enable the OMU route
forwarding.
l Querying the status of OMU route forwarding
1. Log in to the OMU.
4. Enter the ./ip_forward.sh status command and press Enter to query the status of
OMU route forwarding.
NOTE
Parameter description
l Configuration status indicates the status of OMU route forwarding to be configured.
l Actual status indicates the current status of OMU route forwarding.
l enabled indicates that OMU route forwarding is enabled. disabled indicates that OMU route
forwarding is disabled.
----End
Example
The following is used as an example for disabling OMU route forwarding.
omucc_68 ~ # cd /mbsc/bam/version_a/bin/bam
omucc_68 /mbsc/bam/version_a/bin/bam # chmod +x ip_forward.sh
omucc_68 /mbsc/bam/version_a/bin/bam # ./ip_forward.sh disable
Disabling ip forward done
The following is used as an example for enabling OMU route forwarding.

BSC6900 UMTS
omucc_68 /mbsc/bam/version_a/bin/bam # ./ip_forward.sh enable

Enabling ip forward done
The following is used as an example for querying the status of OMU route forwarding.
omucc_68 /mbsc/bam/version_a/bin/bam # ./ip_forward.sh status
Configuration status: enabled Actual status: enabled
Follow-up Procedure
1. Record the status of OMU route forwarding.
6.3 Enhancing Security of Time Synchronization with NTP

The security of time synchronization with Network Time Protocol (NTP) is enhanced for the
BSC6900 after NTP messages are authenticated.
Prerequisites
l The peer equipment supports NTP and NTP message authentication.
l The IP address, NTP server port number, and key index of the peer equipment have been
obtained.
Context
Before sending a synchronization request to an NTP server, the OMU, as an NTP client, encrypts
the request and attaches a key index and encryption information to the request. The NTP server
decrypts the request and sends a synchronization response to the NTP client. After receiving the
response, the NTP client checks whether the encryption information in the response is consistent
with that calculated locally. If yes, the time synchronization between the NTP client and server
starts.
If multiple NTP servers are configured for the time synchronization with the OMU (NTP client),
the OMU automatically selects the best NTP server as the clock source.
When OMU of the BSC6900 is used as an NTP client, the OMU supports the NTP-based time
synchronization in plaintext or in cipher.
When OMU of the BSC6900 is used as an NTP server, the OMU only provides NTP plaintext
in internal network.
Procedure
Step 1 Log in to the LMT by referring to Logging In to and Logging Out of the LMT.
Step 2 To add the information of an NTP server connected to the OMU, run the ADD
SNTPSRVINFO command and set the following parameters as required: IP Address, Port,
NTP Authentication Mode, Key ID, Encryption Algorithm, Key, Confirmation Key.
NOTE
Repeat Step 2 to configure multiple NTP servers available for the time synchronization with the OMU.
----End

BSC6900 UMTS
6.4 Configuring the Function of Recording OMU OS

Accessing Information in Real Time
This section describes how to configure the function of recording OMU operating system (OS)
accessing information in real time when users log in to or out of the OMU OS. This function
helps monitor the OMU OS security.
Prerequisites
l The OMU OS is Dopra Linux.
l The peer equipment OS is Linux or Unix.
Context
With this function, the OMU automatically records a user's information and reports the
information to the peer equipment by using the syslog service when the user logs in to or out of
the OMU OS. The reported user information includes the user name, user IP address, and the
number of the port through which the user accesses the OMU.
Multiple OMUs can be enabled with this function. Once enabled, they report their users'
information to the peer equipment simultaneously.
NOTE
For example, the version information for the active OMU workspace is version_a. You can run the LST
OMUAREA command to query the version information for the current active OMU workspace.
Procedure
l Enabling the function of recording OMU OS accessing information in real time
1. Log in to the target OMU. For details, see Logging In to the OMU.
2. Run the cd /mbsc/bam/version_a/bin/bam command to switch the directory where
the syslog_config.sh script is saved.
3. Run the ./syslog_config.sh IP address PORT command to enable the function of
recording OMU OS accessing information in real time.
NOTE
l IP address represents the IP address of the third-party server.

l PORT represents the number of port through which the third-party server receives OMU OS
accessing information. The recommended value for this parameter is 514.
For example, you can run the ./syslog_config.sh 10.142.38.157 514 to enable this function.
l Disabling the function of recording OMU OS accessing information in real time
3. Run the ./syslog_config.sh disable command to disable the function of recording
OMU OS accessing information in real time.
l Checking whether the function of recording OMU OS accessing information in real time
is enabled

BSC6900 UMTS

3. Run the ./syslog_config.sh l command to query whether the function of recording
OMU OS accessing information in real time is enabled.
----End
6.5 Enabling Function of Checking OS File Integrity

This section describes how to enable the function of checking the operating system (OS) file
integrity. This function is for monitoring the security of the OMU OS.
Prerequisites
The OMU OS File Integrity Checklist is available.
Context
l The OMU OS File Integrity Checklist is used to specify the OS files to be checked. This
list must be in .txt format and file path information for a maximum of 5000 files can be
provided in the list. File path information for each file occupies one line and must include
the file name. The following are two examples of file path information corresponding to
Linux and Window, respectively: /etc/sysctl.conf and C:\WINDOWS\explorer.exe.
l After the function is enabled, the OMU checks the integrity of specified files every 12
hours. If the check fails, the ALM-20723 File Loss or Damage is reported. In the scenarios
of version upgrade, driver upgrade, and OS upgrade, if the ALM-20723 File Loss or
Damage is reported after a monitored file is changed, clear the alarm by following the alarm
handling procedures.
l After an OS switch, this function will be automatically disabled and the OMU OS File
Integrity Checklist will be deleted. To enable this function, the OMU OS File Integrity
Checklist must be created and loaded again.
l It is recommended that the files to be checked must be important and will not be changed
by the NE automatically. If the OMU is using Linux, files in the following directories are
recommended to be checked: /bin, /boot, /etc, /sbin, and /sys
NOTE
If the OMU is in active/standby mode, enable or disable this function on both active and standby OMUs.
Procedure
l Enabling this function
1. Upload the OMU OS File Integrity Checklist into the ftp/integrity_cfg directory in
the OMU active workspace. For details, see 4.4.1 psftp Software.
2. Run the ACT FILEINTEGRITYPRO command to enable this function.
l Disabling this function
1. Run the DEA FILEINTEGRITYPRO command to disable this function.
l Querying the function status

BSC6900 UMTS
1. Run the LST FILEINTEGRITYPRO command to query the status of this function.
----End


BSC6900 UMTS OMU Administration Guide (V900R014C00 - 08) (PDF) - EN PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BSC6900 UMTS OMU Administration Guide (V900R014C00 - 08) (PDF) - EN PDF

Hochgeladen von

Copyright:

Verfügbare Formate

BSC6900 UMTS

OMU Administration Guide

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 08 (2013-06-25) Huawei Proprietary and Confidential i

About This Document

Product Name Product Version

Issue 08 (2013-06-25) Huawei Proprietary and Confidential ii

Indicates a hazard with a high level or medium level of risk

Indicates a hazard with a low level of risk which, if not

Indicates a potentially hazardous situation that, if not

Indicates a tip that may help you solve a problem or save

Provides additional information to emphasize or supplement

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

Italic Book titles are in italics.

Issue 08 (2013-06-25) Huawei Proprietary and Confidential iii

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

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

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

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

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

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

Issue 08 (2013-06-25) Huawei Proprietary and Confidential iv

Double-click Press the primary mouse button twice continuously and

Issue 08 (2013-06-25) Huawei Proprietary and Confidential v

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

3 Working Principles of the OMU..............................................................................................30

Issue 08 (2013-06-25) Huawei Proprietary and Confidential vi

4 Scenario: Deploying a BSC6900................................................................................................58

5 Scenario: Upgrading from the BSC6810 to the BSC6900....................................................147

Issue 08 (2013-06-25) Huawei Proprietary and Confidential vii

5.2.6 Querying Occupied OMU Ports..............................................................................................................................184

6 Appendix: Security FAQ..........................................................................................................254

Issue 08 (2013-06-25) Huawei Proprietary and Confidential viii

1 Changes in the BSC6900 UMTS OMU

l 6.3 Enhancing Security of Time Synchronization with NTP

Changing Users' Passwords The password complicacy is modified.

Issue 08 (2013-06-25) Huawei Proprietary and Confidential 1

Restoring System Data Described different scenarios where MML

Logging In to the OMU Added the description: It is recommended

Logging In to the OMU Description about login to the OMU by the

Issue 08 (2013-06-25) Huawei Proprietary and Confidential 2

l 4.5.4 OMU Folder Size List

l Scenario: Creating a BSC6900 NE Changed the chapter name to Changing the

Checking the Installation Directory of The file folder version_a/ftp/trace is

l 4.2.2 Optional: Installing the Operating System and OMU Applications

l 4 Scenario: Deploying a BSC6900 Scenario descriptions are added.

3.2 OMU IP Address Plan The descriptions about the restriction on IP

Issue 08 (2013-06-25) Huawei Proprietary and Confidential 3

4.2.3 Optional: Installing the OMU Background information is added.

4.3.6 Changing the Administrator Notes on admin password complexity are

l Scenario: Creating a BSC6900 NE Descriptions on starting and stoping the omud

4 Scenario: Deploying a BSC6900 The procedure descriptions for the scenario

Issue 08 (2013-06-25) Huawei Proprietary and Confidential 4

6.4 Configuring the Function of Recording The procedures are modified.

l Scenario: Creating a BSC6900 NE The procedure descriptions for restoring the

Checking the Installation Directory of Notes about some OMU application

Preparing a USB Storage Device Descriptions of data encryption are added in