Bsc6900 GSM Omu Administration Guide v900r013c00 08 PDF en

BSC6900 GSM
V900R013C00
OMU Administration Guide

Issue
08
Date
2012-02-27
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2012. 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 the 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 (2012-02-27)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
BSC6900 GSM
About This Document
About This Document

Purpose
This document describes the software and hardware structure, software installation, GUI, and
operations concerning the OMUa/OMUb/OMUc board.
Product Version
The following table lists the product version related to this document.
Product Name
Product Version
BSC6900
V900R013C00
Intended Audience
This document is intended for:
l
Field engineers
Shift operators
Organization
1 Changes in the BSC6900 GSM OMU Administration Guide
This document describes the changes in the BSC6900 GSM OMU Administration Guide.
2 Introduction to OMU
The physical entity of the OMU is the OMUa/OMUb/OMUc board. The OMU collects and
processes the information about operation and maintenance (OM), and then reports the
information to the OM terminal: LMT or M2000.
3 Working Principles of the OMU
This chapter describes the operating principles of Ethernet adapters, related IP addresses, active
and standby workspaces, and active and standby OMUs.
Issue 08 (2012-02-27)

ii
BSC6900 GSM
About This Document
4 Scenario: Creating a BSC6900 NE

This chapter describes how to install software and perform operation and maintenance for the
OMU when a BSC6900 NE is created.
5 Scenario: Upgrade from the BSC6000 to the BSC6900
OMU when the BSC6000 is upgraded to the BSC6900.
6 Appendix: Troubleshooting
This chapter describes OMU faults and troubleshooting methods.
7 Appendix: Security FAQ
This section describes how to improve the security of the BSC6900.
8 Appendix: Special OMU Networking Scenarios
This section describes the special scenarios of connecting the OMU to peripheral equipment.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
Indicates a hazard with a high level of risk, which if not
avoided, will result in death or serious injury.
Indicates a hazard with a medium or low level of risk, which
if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation, which if not
avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save
time.
Provides additional information to emphasize or supplement
important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows.
Issue 08 (2012-02-27)
Convention
Description
Times New Roman
Normal paragraphs are in Times New Roman.

iii
BSC6900 GSM
About This Document
Convention
Description
Boldface
Names of files, directories, folders, and users are in

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

Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
The keywords of a command line are in boldface.
Italic
Command arguments are in italics.
[]
Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... }
Optional items are grouped in braces and separated by

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

vertical bars. One item is selected or no 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.
Convention
Description
Boldface
Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
>
Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Issue 08 (2012-02-27)

iv
BSC6900 GSM
About This Document
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 (2012-02-27)
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.

BSC6900 GSM
Contents
Contents
About This Document.....................................................................................................................ii
1 Changes in the BSC6900 GSM OMU Administration Guide...............................................1
2 Introduction to OMU....................................................................................................................8
2.1 Position of the OMU in the BSC6900................................................................................................................9
2.2 OMUa and OMUb Board...................................................................................................................................9
2.2.1 Functions of the OMUa/OMUb Board....................................................................................................10
2.2.2 Panel of the OMUa/OMUb Board...........................................................................................................10
2.2.3 Ports on the OMUa/OMUb Board...........................................................................................................12
2.2.4 LEDs on the OMUa/OMUb Board..........................................................................................................12
2.2.5 Technical Index for the OMUa/OMUb/OMUc Board............................................................................13
2.3 OMUc Board....................................................................................................................................................15
2.3.1 Functions of the OMUc Board................................................................................................................15
2.3.2 Panel of the OMUc Board.......................................................................................................................15
2.3.3 LEDs on the OMUc Board......................................................................................................................17
2.3.4 Ports on the OMUc Board.......................................................................................................................17
2.3.5 Technical Index for the OMUa/OMUb/OMUc Board............................................................................18
2.4 GBAM..............................................................................................................................................................20
2.4.1 Functions of GBAM................................................................................................................................20
2.4.2 Physical Appearance of the GBAM (IBM X3650T)...............................................................................20
2.4.3 Physical Appearance of the GBAM (HUAWEI C5210).........................................................................23
2.4.4 Physical Appearance of the GBAM (HP CC3310).................................................................................26
2.4.5 Technical Specifications and Counters of the GBAM............................................................................29
2.5 OMU Software.................................................................................................................................................30
2.5.1 OMU Application Structure....................................................................................................................30
2.5.2 OMU Service Monitoring Entities..........................................................................................................31
2.5.3 OMU Service Processes..........................................................................................................................32
2.6 OMU Working Mode.......................................................................................................................................34
2.7 OMU OM Methods..........................................................................................................................................34
2.8 OMU Safety Information..................................................................................................................................36
3 Working Principles of the OMU..............................................................................................37

3.1 OMU Ethernet Adapter Configuration.............................................................................................................38
3.2 Planning of the OMU IP Addresses.................................................................................................................43
Issue 08 (2012-02-27)

vi
BSC6900 GSM
Contents
3.3 OMU Networking Principle.............................................................................................................................54

3.4 Active/Standby Workspaces of the OMU........................................................................................................67
3.5 Heartbeat Test on Active/Standby OMUs........................................................................................................68
3.6 Synchronization Between the Active OMU and the Standby OMU................................................................68
3.7 Switchover Between Active and Standby OMUs.............................................................................................69
4 Scenario: Creating a BSC6900 NE.............................................................................................71

4.1 Installing the OMU Applications in Field Commissioning..............................................................................73
4.1.1 Setting the Link Mode of the External OMU Ethernet Adapters............................................................73
4.1.2 Debugging OMU on Site.........................................................................................................................75
4.2 Reinstalling Software Onsite............................................................................................................................80
4.2.1 Preparations for Installing Software Onsite.............................................................................................80
4.2.2 Preparing the USB Storage Device.........................................................................................................82
4.2.3 Installing the OMU Operating System from a USB Storage Device......................................................89
4.2.4 Optional: Installing the OMU Applications............................................................................................91
4.3 Operating and Maintaining the OMU.............................................................................................................102
4.3.1 Querying the Configuration of the OMU Ethernet Adapters................................................................102
4.3.2 Querying the Network Configuration of the OMU Ethernet Adapters.................................................103
4.3.3 Checking the Version of the Operating System....................................................................................104
4.3.4 Changing the IP Address of the OMU Ethernet Adapter Team............................................................104
4.3.5 Changing the Administrator Password of the Operating System..........................................................105
4.3.6 Setting RAID 1 on the OMU Hard Disks..............................................................................................106
4.3.7 Maintaining the OMU Routinely...........................................................................................................112
4.3.8 Managing the Operating Status of the OMU.........................................................................................115
4.3.9 Managing the OMU Applications.........................................................................................................120
4.3.10 Backing Up and Restoring Data..........................................................................................................123
4.3.11 Using the omutool...............................................................................................................................126
4.3.12 Adjusting OMU Slots..........................................................................................................................135
4.4 Appendix: OMU-Related Software................................................................................................................136
4.4.1 psftp Software........................................................................................................................................136
4.4.2 PuTTY Software....................................................................................................................................138
4.5 Appendix: OMU-Related Information Tables................................................................................................140
4.5.1 Records of OMU Software Installation Information.............................................................................140
4.5.2 Checklist for the Factory Settings of the OMU Software.....................................................................142
4.5.3 Enabled Ports on the OMU....................................................................................................................144
5 Scenario: Upgrade from the BSC6000 to the BSC6900........................................................147

5.1 Reinstalling Software Onsite..........................................................................................................................149
5.1.1 Re-Installing the Suse Linux Operating System....................................................................................149
5.1.2 Switching the OMU Operating System.................................................................................................159
5.1.3 Optional: Installing the OMU Applications..........................................................................................171
5.2 OMU Operation and Maintenance After the Upgrade...................................................................................173
5.2.1 Querying the Operating Status of the OMU..........................................................................................173
5.2.2 Querying the Information About the OMU...........................................................................................174
Issue 08 (2012-02-27)

vii
BSC6900 GSM
Contents
5.2.3 Querying the Version of the Active/Standby OMU Workspaces..........................................................175

5.2.4 Querying the Status of the Data Synchronization Between the Active OMU and the Standby OMU
........................................................................................................................................................................175
5.2.5 Checking the Data Consistency Between the Active OMU and the Standby OMU.............................176
5.2.6 Changing the OMU Time and Time Zone.............................................................................................176
5.2.7 Changing the Administrator Password of the Operating System..........................................................177
5.2.8 Switching Over the Active/Standby OMU Workspaces.......................................................................177
5.2.9 Forcibly Switching Over the Active and Standby OMUs.....................................................................178
5.2.10 Setting the FTP User Password...........................................................................................................179
5.2.11 Setting RAID 1 on the OMU Hard Disks............................................................................................179
5.2.12 Replacing the Public and Private Key Certificate Files.......................................................................186
5.2.13 Checking the Version of the Operating System..................................................................................187
5.2.14 Checking the OMU Hard Disk Partitions............................................................................................187
5.2.15 Checking the OMU Memory Capacity-Size.......................................................................................188
5.2.16 Checking the OMU Ethernet Adapter Teams......................................................................................188
5.2.17 Changing the Connection Mode of the OMU Ethernet Adapters........................................................190
5.2.18 Setting the Link Mode of the External OMU Ethernet Adapter..........................................................192
5.2.19 Setting the 1st Boot Device of the OMU to USB................................................................................195
5.2.20 Resetting the OMU..............................................................................................................................203
5.2.21 Shutting Down the OMU.....................................................................................................................204
5.2.22 Routine OMU Maintenance After the Upgrade...................................................................................205
5.2.23 Managing the OMU Applications.......................................................................................................207
5.2.24 Backing Up and Restoring Data..........................................................................................................210
5.2.25 Using the omutool...............................................................................................................................213
5.2.26 Adjusting OMU Slots..........................................................................................................................226
5.3 Appendix: the SEK SetSuse Software............................................................................................................227
5.3.1 Installing the SEK SetSuse Software.....................................................................................................227
5.3.2 Rolling Back Security Enhancement Policies During the Use of the SEK SetSuse Software..............230
5.3.3 Uninstalling the SEK SetSuse Software................................................................................................231
5.4 Appendix: Antivirus Software........................................................................................................................232
5.5 Appendix: Ethernet Adapter Binding Tool....................................................................................................233
5.6 Appendix: OMU-Related Information Tables................................................................................................236
5.6.1 Record Sheet of OMU Software Installation Information.....................................................................236
5.6.2 Checklist for the Factory Settings of the OMU Software.....................................................................237
5.6.3 List of the Factory Configuration of the OMU Software and Hardware...............................................238
5.6.4 Enabled Ports on the OMU....................................................................................................................238
6 Appendix: Troubleshooting....................................................................................................241
6.1 Prohibiting Dark Screen and Startup Animation............................................................................................242
6.2 Restoring the Server Through the OMU Troubleshooting Tool....................................................................243
7 Appendix: Security FAQ..........................................................................................................248

7.1 Disabling root user remote login....................................................................................................................249
7.2 Disabling OMU route forwarding..................................................................................................................252
Issue 08 (2012-02-27)

viii
BSC6900 GSM
Contents
8 Appendix: Special OMU Networking Scenarios................................................................ 254

8.1 Scenario of Connecting the OMU and VNP..................................................................................................255
Issue 08 (2012-02-27)

ix
BSC6900 GSM
Changes in the BSC6900 GSM OMU

Administration Guide
This document describes the changes in the BSC6900 GSM OMU Administration Guide.
08 (2012-02-27)
This is the eighth commercial release of V900R013C00.
Compared with issue 07 (2012-01-05), this issue does not include any new topics.
Compared with issue 07 (2012-01-05), this issue incorporates the following changes:
Content
Description
4.3.6 Setting RAID 1 on the OMU Hard

Disks
Descriptions about using the external

keyboard and monitor to configure the OMU
hard disk RAID 1 are added.
7.1 Disabling root user remote login
The method of modifying a non-root user's

password is added.
l Scenario: Creating a BSC6900 NE
The method of modifying passwords of root,

db_user and FtpUsr are added.
Changing the admin password

l Scenario: Upgrade from the BSC6000 to
the BSC6900
Changing the Admin Password
Installing the OMU Applications in the
Active Workspace
Descriptions about checking whether the

OMU application is pre-installed are added.

the BSC6900
5.1.3 Optional: Installing the OMU
Applications
Issue 08 (2012-02-27)

BSC6900 GSM
Content
Description
Notes on ports 6099, 8099, 16002 and 18002

are modified.
4.5.3 Enabled Ports on the OMU

the BSC6900
Compared with issue 07 (2012-01-05), this issue does not exclude any topics.
07 (2012-01-05)
This is the seventh commercial release of V900R013C00.
Compared with issue 06 (2011-11-30), this issue includes the following new topics:
l
7.2 Disabling OMU route forwarding
Content
Description
Uploading the OMU Application

Installation Package to the OMU
The method for uploading the OMU

application installation package to the OMU
is added.
4.2.3 Installing the OMU Operating

System from a USB Storage Device
The follow-up procedure for enabling the

disabling the root-user remote login function
is added.
Logging In to the OMU
The notes for the operation after the failure of

the root-user login are added.
2.2.5 Technical Index for the OMUa/

OMUb/OMUc Board
The time taken to synchronize the standby

OMU files with the active OMU files is
modified.
The procedure for configuring the OMU

working mode is modified.
Setting the Working Mode of the OMU

the BSC6900
Restoring the System Data
The procedure for restoring the system data

is modified.

the BSC6900
Issue 08 (2012-02-27)

BSC6900 GSM
Content
Description
The procedure for configuring the OMU IP

address is modified.
Changing IP Addresses and Masks of

the OMU Ethernet Adapters
the BSC6900
Changing IP Addresses and Masks of
Port 8088 is deleted.

the BSC6900
the BSC6900
The procedure for switching the OMU

operating system to Dopra Linux is modified.
5.1.2 Switching the OMU Operating

System
06 (2011-11-30)
This is the sixth commercial release of V900R013C00.
l
8.1 Scenario of Connecting the OMU and VNP
Content
Description
4.5.1 Records of OMU Software

Installation Information
The OMU Ethernet adapter team IP address

information is added.

The follow-up procedures are added.
Uninstalling the OMU Applications
Precautions for uninstalling OMU

applications are added.

the BSC6900


System
Issue 08 (2012-02-27)

BSC6900 GSM
05 (2011-08-31)
This is the fifth commercial release of V900R013C00.
Content
Description
3.7 Switchover Between Active and

Standby OMUs
The description of four types of OMU

switchovers is modified.
Checking the Installation Directory of

OMU Applications
The directory structure of OMU applications

is modified.
4.2.2 Preparing the USB Storage Device
The basis for determining the link mode of the

OMU external Ethernet adapter in the process
of preparing the USB storage device is added.

the BSC6900


System
04 (2011-07-11)
This is the fourth commercial release of V900R013C00.
Content
Description
4.2.1 Preparations for Installing Software

Onsite
The description of supporting operating

system of Microsoft Windows 7 is added.
4.1.1 Setting the Link Mode of the External

OMU Ethernet Adapters
The method of setting the link mode of the

OMU external Ethernet adapters is modified.
The description of referring to the DOPRA

Linux USB Disk Certificate Guide is added.

the BSC6900


System
Issue 08 (2012-02-27)

BSC6900 GSM
03 (2011-05-30)
This is the third commercial release of V900R013C00.
l
Upgrade from the BSC6000 to the BSC6900, 5.2.18 Setting the Link Mode of the
External OMU Ethernet Adapter.
Content
Description

OMUb/OMUc Board
The Counter that time required for switchover

between the active and standby OMUs is
modified.


The description of how to set the link mode

of OMU external Ethernet adapters is added
and the interface of the U-creator tool is
updated.

the BSC6900


System
02 (2011-04-25)
This is the second commercial release of V900R013C00.
Issue 08 (2012-02-27)
Content
Description
4.5.2 Checklist for the Factory Settings of

the OMU Software
The default password of the OMUc board is

changed to 11111111.
2.6 OMU Working Mode
The description that mixed insertion of OMU

boards of different types is prohibited.
5.2.19 Setting the 1st Boot Device of the

OMU to USB
The description that the task is applicable to

only OMUa and OMUb boards is added.



BSC6900 GSM
Content
Description
The description that time of install the OMU

operating system is added.

The two methods how to estimate the

operating system finished is deleted.
Installing the OMU Applications in the

Active Workspace
The procedure for installing a patch on the

BSC is deleted.
5.1 Reinstalling Software Onsite
The description that the task procedures vary

with the OMU operating system is added.

System

operating system to Dopra Linux is added.
Compared with issue 01 (2011-03-30), this issue excludes the following topics:
l
The description of how to replace an OMUa or OMUb board is deleted from this manual
and moved to the Replacing an OMU Board.
The description of how to replace an GBAM is deleted from this manual and moved to the
Replacing the GBAM.
01 (2011-03-30)
This is the first commercial release of V900R013C00.
Compared with issue Draft B (2011-03-21), editorial changes are applied.
Draft B (2011-03-21)
This is the Draft B release of V900R013C00.
Compared with issue Draft A (2011-01-31), this issue does not include any new topics.
Compared with issue Draft A (2011-01-31), this issue incorporates the following changes:
Content
Description
4.2.1 Preparations for Installing Software

Onsite
The USB installation disk used for installing

OMU operating system and applications is
renamed.
Checking the Installation Directory of

OMU Applications
The directory where the OMU applications

are saved is updated.

OMUb/OMUc Board
The OMU hardware specifications are

updated.
Compared with issue Draft A (2011-01-31), this issue does not exclude any topics.
Issue 08 (2012-02-27)

BSC6900 GSM
Draft A (2011-01-31)
This is the Draft A release of V900R013C00.
Compared with issue 03 (2010-09-20) of V900R012C01, this issue includes the following new
topics:
l
6 Appendix: Troubleshooting.
4.3.12 Adjusting OMU Slots
Compared with issue 03 (2010-09-20) of V900R012C01, this issue incorporates the following
changes:
Content
Description

The procedure for setting the link mode of the

The window of the Dopra Linux tool is

updated.

The three methods of determining whether

the OMU operating system and OMU
applications are installed successfully are
updated.
3.1 OMU Ethernet Adapter Configuration
The description of principles of Ethernet

adapter configuration of the OMUc board is
added.
3.2 Planning of the OMU IP Addresses
The description of principles of IP address

planning of the OMUc board is added.
3.3 OMU Networking Principle
The description of networking principles of

the OMUc board is added.
l Changing IP Addresses and Masks of

The description of procedure for changing the

backup channel IP address and subnet mask
of the OMUc board is added.
l Changing IP Addresses and Masks of

Compared with issue 03 (2010-09-20) of V900R012C01, this issue does not exclude any topics.
Issue 08 (2012-02-27)

BSC6900 GSM
Introduction to OMU
About This Chapter

The physical entity of the OMU is the OMUa/OMUb/OMUc board. The OMU collects and
processes the information about operation and maintenance (OM), and then reports the
information to the OM terminal: LMT or M2000.
2.1 Position of the OMU in the BSC6900
This section describes the components of the BSC6900 OM subsystem and the position of the
OMU in the OM subsystem.
2.2 OMUa and OMUb Board
OMUa refers to Operation and Maintenance Unit REV:a. OMUb refers to Operation and
Maintenance Unit REV:b. One or two OMUa/OMUb boards must be configured in the
BSC6900. The width of the OMUa/OMUb board is twice the width of other boards. Therefore,
one OMUa/OMUb 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. The OMUa/OMUb board can be
installed in slots 20 to 23 in inventory sites and in slots 24 to 27 in new sites.
2.3 OMUc Board
OMUc refers to Operation and Maintenance Unit REV:c. A pair of active/standby OMUc boards
must be configured. The OMUc 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.
2.4 GBAM
The BSC6900 uses three models of GBAM: IBM X3650T, HUAWEI C5210, and HP CC3310.
The GBAM is installed in the MPR.
2.5 OMU Software
OMU software refers to all the software running on the OMU.
The OMU works in single-OMU or dual-OMU mode.
2.7 OMU OM Methods
This section describes several scenarios and methods of the OMU OM.
2.8 OMU Safety Information
This section describes the safety information related to OMU operation.
Issue 08 (2012-02-27)

BSC6900 GSM
2.1 Position of the OMU in the BSC6900

This section describes the components of the BSC6900 OM subsystem and the position of the
OMU in the OM subsystem.
The BSC6900 OM subsystem is composed of the LMT or M2000, OMU, SCU, and OM modules
of other boards. In the BSC6900 OM subsystem, the OM terminal (LMT or M2000)
communicates with the BSC6900 host 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
NOTE
Either the OMUa, OMUb, or OMUc board, or GBAM can serve as an OMU. This chapter uses the OMUa board
as an example for your reference.
Either the SCUa or SCUb board can serve as an SCU. This chapter takes the SCUa board as an example for
your reference.
As shown in Figure 2-1, the external network is the logical network between the OMU and the
OM terminal (LMT/M2000), and the internal network is the logical network between the OMU
and the BSC6900 host.
2.2 OMUa and OMUb Board

OMUa refers to Operation and Maintenance Unit REV:a. OMUb refers to Operation and
Maintenance Unit REV:b. One or two OMUa/OMUb boards must be configured in the
BSC6900. The width of the OMUa/OMUb board is twice the width of other boards. Therefore,
one OMUa/OMUb board occupies two slots. The board can be installed in slots 0 to 3, slots 20
Issue 08 (2012-02-27)

BSC6900 GSM
to 23, or slots 24 to 27 in the MPS at the bottom of the MPR. The OMUa/OMUb board can be
installed in slots 20 to 23 in inventory sites and in slots 24 to 27 in new sites.
NOTE
This document describes the installation of other boards on the basis that the OMUa/OMUb boards are installed
in slots 24 to 27.
2.2.1 Functions of the OMUa/OMUb Board

The OMUa/OMUb board works as a bridge for the communication between the Local
Maintenance Terminal (LMT) and the other boards in the BSC6900.
The OMUa/OMUb board performs the following functions:
l
Performs the configuration management, performance management, fault management,

security management, and loading management functions for the system
Provides the LMT or M2000 users with the operation and maintenance port of 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/OMUb Board

There are LEDs, ports, and buttons on the panel of the OMUa/OMUb board. In addition, there
are hard disks installed on the OMUa/OMUb board.
Figure 2-2 shows the panel of the OMUa/OMUb board.
Issue 08 (2012-02-27)

10
BSC6900 GSM
Figure 2-2 Panel of the OMUa/OMUb 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
(17) Hard disks
(18) Screws for fixing the hard disk
Issue 08 (2012-02-27)

(16) OFFLINE LED
11
BSC6900 GSM
NOTE
l To power off the OMUa/OMUb board, you need to simultaneously pivot the top and bottom ejector
levers away from the front panel of the OMUa/OMUb 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 emergency.
l The RESET button is used to reset the system. It works in the same way as the reset button on the PC.
l Powering off the board by pressing the SHUTDOWN button or resetting the system by pressing the
RESET button may scratch the surface of the hard disks of the OMUa board. Thus, avoid operating
the two buttons whenever possible.
2.2.3 Ports on the OMUa/OMUb Board

There are four USB ports, three GE ports, one serial port COM0-ALM/COM1-BMC, and one
VGA port on the OMUa/OMUb board.
Table 2-1 describes the ports on the OMUa/OMUb board.
Table 2-1 Ports on the OMUa/OMUb board
Port
Function
Connector Type
USB0-1 and USB2-3
USB ports. These ports are used to

connect USB devices.
ETH0 to ETH2
GE ports
RJ45
COM0-ALM/COM1-BMC
Serial port. This port is used for

system commissioning or for
common serial port usage.
DB9
VGA
Port for the video
DB15
2.2.4 LEDs on the OMUa/OMUb Board

There are five types of LEDs on the OMUa/OMUb board: RUN, ALM, ACT, OFFLINE, and
HD.
Table 2-2 describes the LEDs on the OMUa/OMUb board.
Table 2-2 LEDs on the OMUa/OMUb board
Issue 08 (2012-02-27)
LED
Color
Status
Description
RUN
Green
ON for 1s and OFF for 1s
The board is functional.
ON for 0.125s and OFF

for 0.125s
The board is being started.
ON
There is power supply, but the board

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

board is faulty.

12
BSC6900 GSM
LED
Color
Status
Description
ALM
Red
OFF
There is no alarm.
ON or blinking
There is a fault alarm.
ON
The board is in active mode.
OFF
The board is in standby mode, or the

board is disconnected.
ON
The board can be removed.
OFF
The board cannot be removed.

for 0.125s
The board is being switched over to

the other working mode.
OFF
There is no read or write operation

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

written.
ACT
Green
OFFLINE
Blue
HD
Green
2.2.5 Technical Index for the OMUa/OMUb/OMUc Board

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

Table 2-3 lists the hardware configuration indexes for the OMUa/OMUb/OMUc board.
Table 2-3 Hardware configuration indexes
Issue 08 (2012-02-27)
Counter Name
Index of the
OMUa Board
Index of the
OMUb Board
Index of the
OMUc Board
Size
248 mm x 64.6mm x
395.4 mm
248 mm x 64.6mm x
395.4 mm
248 mm x 32.3mm x
395.4 mm
Power supply
Two routes of -48 V

DC in redundancy
backup mode
(provided by the
backplane of the
subrack)
Two routes of -48 V

DC in redundancy
backup mode
(provided by the
backplane of the
subrack)
Two routes of -48 V

DC in redundancy
backup mode
(provided by the
backplane of the
subrack)
Number of logical
CPUs
Power consumption
120 W
90 W
90 W

13
BSC6900 GSM
Counter Name
Index of the
OMUa Board
Index of the
OMUb Board
Index of the
OMUc Board
Weight
4.0 kg
3.5 kg
2.5 kg
Hard disk capacity
146 GB x 2 (RAID 1)
146 GB x 2 (RAID 1)
500 GB x 1
Memory capacity
2 GB
2 GB
8 GB
Long-term ambient
temperature range
5C to 40C
5C to 40C
5C to 40C
Short-term ambient
temperature range
0C to 50C
0C to 50C
0C to 50C
Long-term ambient
relative humidity
range
5%-85%
5%-85%
5%-85%
Short-term ambient
relative humidity
range
5%-95%
5%-95%
5%-95%
Performance Counters
Table 2-4 lists the performance counters of the OMUa/OMUb/OMUc board.
Table 2-4 Performance counters
Counter Name
Value of the performance counters of the OMUa/OMUb/

OMUc Board
Number of recorded
alarms
The maximum number of recorded alarms is 150,000.
Interval between data

synchronization between
active and standby OMUs
The standby OMU synchronizes its data with that of the active
OMU board every second.
Time taken to
synchronize the standby
OMU files with the active
OMU files
Seven minutes. The time required for the synchronization varies

depending on the size and quantity of the files to be synchronized.
Time required for

switchover between the
Less than 4 minutes for the time elapsed between the request for
OMU switchover is accepted and the switchover is finished.
Time required for the

OMU restart
Time required for the OMU restart due to OMU fault: about three
minutes.
The OMUa/OMUb/OMUc board contains mechanical hard disk. Adverse environments, such
as high temperature and high altitude, shorten board lifespan.
Issue 08 (2012-02-27)

14
BSC6900 GSM
To ensure the lifespan of the OMUa/OMUb/OMUc board, the OMUa/OMUb/OMUc board must
be protected against vibration, shock, and abnormal shutdown.
2.3 OMUc Board

OMUc refers to Operation and Maintenance Unit REV:c. A pair of active/standby OMUc boards
must be configured. The OMUc 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 to 25.
l The OMUc and OMUa/OMUb boards cannot be installed in the same subrack.
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

BSC6900 system, to control the communication between the LMT or M2000 and the SCUb
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.
Issue 08 (2012-02-27)

15
BSC6900 GSM
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
(13) VGA port
(14) USB 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.
Issue 08 (2012-02-27)

16
BSC6900 GSM
2.3.3 LEDs on the OMUc Board

There are five types of LEDs on the OMUc board: RUN, ALM, ACT, OFL, and HDD.
Table 2-5 describes the LEDs on the OMUc board.
Table 2-5 LEDs on the OMUc board
LED
Color
Status
Description
RUN
Green
ON for 1s and OFF for 1s
The board is functional.

for 0.125s
The board is being started.
ON
There is power supply, but the board

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

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

board is disconnected.
ON
The board can be removed.
OFF
The board cannot be removed.

for 0.125s
The board is being switched over to

the other working mode.
OFF
There is no read or write operation

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

written.
ALM
ACT
OFL
HDD
Red
Green
Blue
Green
2.3.4 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-6 describes the ports on the OMUc board.
Issue 08 (2012-02-27)

17
BSC6900 GSM
Table 2-6 Ports on the OMUc board

Port
Function
Connector Type
USB0-1 and USB2-3
USB ports. These ports are used to

connect USB devices.
TYPE-A
ETH0 to ETH2
GE ports.
RJ45
COM
Serial port. This port is used for

system commissioning or for
common serial port usage.
DB9
VGA
Port for the video.
DB15
2.3.5 Technical Index for the OMUa/OMUb/OMUc Board

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

Table 2-7 lists the hardware configuration indexes for the OMUa/OMUb/OMUc board.
Table 2-7 Hardware configuration indexes
Issue 08 (2012-02-27)
Counter Name
Index of the
OMUa Board
Index of the
OMUb Board
Index of the
OMUc Board
Size
248 mm x 64.6mm x
395.4 mm
248 mm x 64.6mm x
395.4 mm
248 mm x 32.3mm x
395.4 mm
Power supply
Two routes of -48 V

DC in redundancy
backup mode
(provided by the
backplane of the
subrack)
Two routes of -48 V

DC in redundancy
backup mode
(provided by the
backplane of the
subrack)
Two routes of -48 V

DC in redundancy
backup mode
(provided by the
backplane of the
subrack)
Number of logical
CPUs
Power consumption
120 W
90 W
90 W
Weight
4.0 kg
3.5 kg
2.5 kg
Hard disk capacity
146 GB x 2 (RAID 1)
146 GB x 2 (RAID 1)
500 GB x 1
Memory capacity
2 GB
2 GB
8 GB
Long-term ambient
temperature range
5C to 40C
5C to 40C
5C to 40C

18
BSC6900 GSM
Counter Name
Index of the
OMUa Board
Index of the
OMUb Board
Index of the
OMUc Board
Short-term ambient
temperature range
0C to 50C
0C to 50C
0C to 50C
Long-term ambient
relative humidity
range
5%-85%
5%-85%
5%-85%
Short-term ambient
relative humidity
range
5%-95%
5%-95%
5%-95%
Performance Counters
Table 2-8 lists the performance counters of the OMUa/OMUb/OMUc board.
Table 2-8 Performance counters
Counter Name
Value of the performance counters of the OMUa/OMUb/

OMUc Board
Number of recorded
alarms
Interval between data

synchronization between
The standby OMU synchronizes its data with that of the active
OMU board every second.
Time taken to
synchronize the standby
OMU files with the active
OMU files
Seven minutes. The time required for the synchronization varies

depending on the size and quantity of the files to be synchronized.
Time required for

switchover between the
Less than 4 minutes for the time elapsed between the request for
OMU switchover is accepted and the switchover is finished.
Time required for the

OMU restart
Time required for the OMU restart due to OMU fault: about three
minutes.
The OMUa/OMUb/OMUc board contains mechanical hard disk. Adverse environments, such
as high temperature and high altitude, shorten board lifespan.
To ensure the lifespan of the OMUa/OMUb/OMUc board, the OMUa/OMUb/OMUc board must
be protected against vibration, shock, and abnormal shutdown.
Issue 08 (2012-02-27)

19
BSC6900 GSM
2.4 GBAM
The BSC6900 uses three models of GBAM: IBM X3650T, HUAWEI C5210, and HP CC3310.
The GBAM is installed in the MPR.
2.4.1 Functions of GBAM

The GBAM works as a bridge for the communication between the Local Maintenance Terminal
(LMT) and the other boards in the BSC6900.
The GBAM performs the following functions:
l

BSC6900 system to control the communication between the LMT or M2000 and the SCUa
2.4.2 Physical Appearance of the GBAM (IBM X3650T)

This section describes the physical appearance of the GBAM (IBM X3650T).
Figure 2-4 shows the GBAM (IBM X3650T).
Figure 2-4 GBAM (IBM X3650T)
Front Panel of the GBAM (IBM X3650T)

The components on the front panel of the GBAM (IBM X3650T) are LEDs, ports, switches, and
a CD-ROM drive.
Figure 2-5 shows the front panel of the GBAM server (IBM X3650T).
Figure 2-5 Front panel of the GBAM (IBM X3650T)
Issue 08 (2012-02-27)

20
BSC6900 GSM
Table 2-9 describes the silkscreen labels on the front panel of the GBAM (IBM X3650T).
Table 2-9 Silkscreen labels on the front panel of the GBAM (IBM X3650T)
No.
Silkscreen Label
Description
None
CD-ROM drive
Power switch
Reset switch
CRT
The CRT (Critical) LED is used for alarm

indication. When this LED is on (yellow), it
indicates that a critical fault occurs in the system
and the system cannot work properly.
MJR
The MJR (Major) LED is used for alarm indication.

When this LED is on (yellow), it indicates that a
major fault occurs in the system. Under this
circumstance, the system can still work properly;
however, the performance deteriorates
significantly.
MNR
The MNR (Minor) LED is used for alarm

indicates that a minor fault occurs in the system.
Under this circumstance, the system can still work
properly.
PWR
The PWR (Power) LED is used for alarm

indicates that the power supply for the system is
faulty.
Serial port for an 8-pin RJ45 connector
USB port
10
Hard disk 0 activity LED. When this LED is on

(green), it indicates that the data on hard disk 0 can
be normally read or written. When this LED is on
(yellow), it indicates that hard disk 0 is faulty.
11
Hard disk 1 activity LED. When this LED is on

(green), it indicates that the data on hard disk 1 can
be normally read or written. When this LED is on
(yellow), it indicates that hard disk 1 is faulty.
12
ON
13
Issue 08 (2012-02-27)
Main power LED

NIC0/NIC1 activity LED

21
BSC6900 GSM
No.
Silkscreen Label
Description
14
System ID LED
15
ID switch, used to switch system IDs
16
None
NMI switch. The NMI switch is used to stop the

system for fault diagnosis.
Rear Panel of the GBAM (IBM X3650T)

The components on the rear panel of the GBAM (IBM X3650T) are power port, grounding post,
and other ports.
Figure 2-6 shows the rear panel of the GBAM (IBM X3650T).
Figure 2-6 Rear panel of the GBAM
Table 2-10 describes the silkscreen labels on the rear panel of the GBAM (IBM X3650T).
Table 2-10 Silkscreen labels on the rear panel of the GBAM (IBM X3650T)
Issue 08 (2012-02-27)
No.
Silkscreen
Label
Description
Alarms
DB15 port (for exporting alarm information from the

GBAM)
None
PCI card bracket (with no card inserted)
None
PCI card bracket (with a card inserted)
None
10M/100M adaptive port for Ethernet adapter
None
Power module
PS/2 mouse/keyboard ports. The upper port is for the

mouse, and the lower one is for the keyboard.

22
BSC6900 GSM
No.
Silkscreen
Label
Description
RJ45 NIC port 1
RJ45 NIC port 2
10
Port for the video
11
USB port 1
12
USB port 0
13
Server management port
14
Ultra320 SCSI port
15
Grounding post for the PGND cable
2.4.3 Physical Appearance of the GBAM (HUAWEI C5210)

This section describes the physical appearance of the GBAM (HUAWEI C5210).
Figure 2-7 shows the GBAM (HUAWEI C5210).
Figure 2-7 GBAM (HUAWEI C5210)
Front Panel of the GBAM (HUAWEI C5210)

The components on the front panel of the GBAM (C5210) are LEDs, ports, switches, and a CDROM drive.
Figure 2-8 shows the front panel of the GBAM (HUAWEI C5210).
Figure 2-8 Front panel of the GBAM (HUAWEI C5210)
Issue 08 (2012-02-27)

23
BSC6900 GSM
Table 2-11 describes the silkscreen labels on the front panel of the GBAM (HUAWEI C5210).
Table 2-11 Silkscreen labels on the front panel of the GBAM (HUAWEI C5210)
No.
Silkscreen
Label
Description
None
CD-ROM drive
Power switch
Reset switch
CRT
The CRT (Critical) LED is used for alarm indication. When the
LED is on (yellow), it indicates that a critical fault occurs in
the system and the system cannot work properly.
MJR
The MJR (Major) LED is used for alarm indication. When this
LED is on (yellow), it indicates that a major fault occurs in the
system. Under this circumstance, the system can still work
properly; however, the performance deteriorates significantly.
MNR
The MNR (Minor) LED is used for alarm indication. When this
LED is on (yellow), it indicates that a minor fault occurs in the
properly.
PWR
The PWR (Power) LED is used for alarm indication. When this
LED is on (yellow), it indicates that the power supply for the
system is faulty.
USB port
10
Issue 08 (2012-02-27)
11
Hard disk 2 activity LED. When this LED is on (green), it

indicates that the data on hard disk 2 can be normally read or
written. When this LED is on (yellow), it indicates that hard
disk 2 is faulty.
12

disk 1 is faulty.
13
ON
Main power LED
14
15
System ID LED
16

24
BSC6900 GSM
No.
Silkscreen
Label
17
None
Description
NMI switch. The NMI switch is used to stop the system for
fault diagnosis.
Rear Panel of the GBAM (HUAWEI C5210)

The components on the rear panel of the GBAM (HUAWEI C5210) are power port, grounding
post, and other ports.
Figure 2-9 shows the rear panel of the GBAM (HUAWEI C5210).
Figure 2-9 Rear panel of the GBAM (HUAWEI C5210)
Table 2-12 describes the silkscreen labels on the rear panel of the GBAM (HUAWEI C5210).
Table 2-12 Silkscreen labels on the rear panel of the GBAM (HUAWEI C5210)
No.
1
Description
USB port 1
Port for the video
Ultra320 SCSI port
RJ45 NIC port 1
Integrated port for mouse and keyboard. You can use a Yshaped cable to connect the mouse and keyboard to the
GBAM (C5210).
None
Issue 08 (2012-02-27)
Silkscreen
Label
USB port 2

25
BSC6900 GSM
No.
Silkscreen
Label
Description
10
None
DC input power socket (wiring terminal "-" is for the -48 V

power cable, and wiring terminal "+" is for the RTN cable.)
11
Alarms

GBAM)
12
RJ45 NIC port 0
2.4.4 Physical Appearance of the GBAM (HP CC3310)

This section describes the physical appearance of the GBAM (HP CC3310).
Figure 2-10 shows the GBAM (HP CC3310).
Figure 2-10 GBAM (HP CC3310)
Front Panel of the GBAM (HP CC3310)

The components on the front panel of the GBAM (HP CC3310) are LEDs, ports, switches, and
a CD-ROM drive.
Figure 2-11 shows the front panel of the GBAM (HP CC3310).
Figure 2-11 Front panel of the GBAM (HP CC3310)
Table 2-13 describes the silkscreen labels on the front panel of the GBAM (HP CC3310).
Issue 08 (2012-02-27)

26
BSC6900 GSM
Table 2-13 Silkscreen labels on the front panel of the GBAM (HP CC3310)
No.
Silkscreen
Label
Description
None
CD-ROM drive
Power switch
Reset switch
CRT
The CRT (Critical) LED is used for alarm indication. When the
LED is on (yellow), it indicates that a critical fault occurs in the
system and the system cannot work properly.
MJR
The MJR (Major) LED is used for alarm indication. When this
LED is on (yellow), it indicates that a major fault occurs in the
properly; however, the performance deteriorates significantly.
MNR
The MNR (Minor) LED is used for alarm indication. When this
LED is on (yellow), it indicates that a minor fault occurs in the
properly.
PWR
The PWR (Power) LED is used for alarm indication. When this
LED is on (yellow), it indicates that the power supply for the
system is faulty.
USB port
10
11

disk 2 is faulty.
12

disk 1 is faulty.
13
ON
14
15
System ID LED
16
17
Issue 08 (2012-02-27)
Main power LED
None
NMI switch. The NMI switch is used to stop the system for
fault diagnosis.

27
BSC6900 GSM
Rear Panel of the GBAM (HP CC3310)

The components on the rear panel of the GBAM (HP CC3310) are power port, grounding post,
and other ports.
Figure 2-12 shows the rear panel of the GBAM (HP CC3310).
Figure 2-12 Rear panel of the GBAM (HP CC3310)
Table 2-14 describes the silkscreen labels on the rear panel of the GBAM (HP CC3310).
Table 2-14 Silkscreen labels on the rear panel of the GBAM (HP CC3310)
No.
1
Silkscreen Label
1
USB port 1
Port for the video
Ultra320 SCSI port
RJ45 NIC port 1
Integrated port for mouse and keyboard. You can use a

Y-shaped cable to connect the mouse and keyboard to
the GBAM (HP CC3310).
None
Issue 08 (2012-02-27)
Description
USB port 2
10
None
DC input power socket (wiring terminal "-" is for the -48

V power cable, and wiring terminal "+" is for the RTN
cable.)
11
Alarms

GBAM)

28
BSC6900 GSM
No.
12
Silkscreen Label
Description
RJ45 NIC port 0
2.4.5 Technical Specifications and Counters of the GBAM

The technical specifications and counters of the GBAM include hardware configuration
specifications and performance counters of the GBAM.
The BSC can be configured with different types of GBAM, including IBM X3650T, C5210, and
HP CC3310.
Hardware Configuration Specifications of the GBAM

The hardware configuration specifications of different types of GBAM are shown in Table
2-15, Table 2-16, and Table 2-17 respectively.
Table 2-15 Hardware configuration specifications of the GBAM (IBM X3650T)
Hardware Name
Hardware Specifications
CPU
Double CPU; primary frequency: 3.2 GHz
Memory
2 GB
Hard disk capacity
2146 GB RAID1
Ethernet adapter
Four Ethernet adapters are configured.

l Two Ethernet adapters are integrated on the main board, bound
as a team, and work in active/standby mode.
l The other two are installed in the PCI slot, bound as a team, and
work in active/standby mode.
Table 2-16 Hardware configuration specifications of the GBAM (C5210)

Hardware Name
CPU
Memory
2 GB
Hard disk capacity
2146 GB RAID1
Ethernet adapter
Three or four Ethernet adapters are configured.

l The other one works on its own. Or the other two are installed in
the PCI slot, bound as a team, and work in active/standby mode.
Issue 08 (2012-02-27)

29
BSC6900 GSM
Table 2-17 Hardware configuration specifications of the GBAM (HP CC3310)

Hardware Name
CPU
Memory
2 GB
Hard disk capacity
2146 GB RAID1
Ethernet adapter
Three Ethernet adapters are configured.

l The other one is installed in the PCI slot and works on its own.
Performance Counters of the GBAM

As Table 2-18 shows, performance counters of the three types of GBAM are the same.
Table 2-18 Performance counters of the GBAM
Counter Name
Counter Value
Number of recorded
alarms
Number of days for

storing files of
performance
measurement results
The maximum number of days for storing files of performance

measurement results is 15 days.
Time taken for starting

the GBAM
l Restarting the GBAM takes about two minutes if the GBAM is

paused due to its upgrade.
l Restarting the GBAM takes about five minutes if the GBAM
stops working due to its fault
2.5 OMU Software

OMU software refers to all the software running on the OMU.
2.5.1 OMU Application Structure

The OMU applications, used for operation and maintenance, consist of multi-level service
monitoring entities and service processes.
Figure 2-13 shows the structure of the OMU applications.
Issue 08 (2012-02-27)

30
BSC6900 GSM
Figure 2-13 OMU Application Structure
NOTE
The bidirectional arrows shown in Figure 2-13 denote communication between modules.
For details about the OMU service processes, see 2.5.3 OMU Service Processes. For details
about the service monitoring entities, see 2.5.2 OMU Service Monitoring Entities.
2.5.2 OMU Service Monitoring Entities

The OMU applications perform monitoring at two levels: level 1 and level 2. Level 1 is the
system-level monitoring, that is, the omud monitors the monitor. Level 2 is the application-level
monitoring, that is, the monitor monitors the service processes. When a service process or the
monitor is faulty, the two-level monitoring ensures that the faulty service process or monitor
can be restarted.
Issue 08 (2012-02-27)

31
BSC6900 GSM
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 manages the OMU boards and monitors the service processes in real time.
2.5.3 OMU Service Processes

The OMU provides the back administration function with the help of OMU service processes.
The service processes of the OMU 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 (sntp), FTP module (ftp_server), exchange module
(host_gate), fault diagnose module (cfa), base station maintenance module (btsom), OMU log
management module (debug_log), and LMT module (weblmt).
Communication Module (ems_gate)

The communication module performs the following functions:
Receiving messages from the Element Management System (EMS)/Local Maintenance
Terminal (LMT), converting the messages into frames for internal communication in the OMU,
and then sending the messages to the authentication module. Receiving messages from the OMU
modules, interpreting the messages, and then sending the messages to the EMS or LMT.
Authentication Module (authority)

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

The network agent module performs the following functions:
l
Batch command processing
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.
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.
Issue 08 (2012-02-27)

32
BSC6900 GSM
Alarm Module (alarm)

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

The performance module collects, stores, 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, 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 for BSC6900 boards and the BTS.
The time client synchronizes with the upper-level time server, and provides the standard
time on the upper-level time server for the OMU.
FTP Module (ftp_server)

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

The exchange module supports the communication between the OMU service processes and the
host.
Base Station Maintenance Module (btsom)

The base station maintenance module performs the functions of alarm management, performance
management, software management, and routine maintenance for the base station.
Fault Diagnose Module (cfa)

The fault diagnose module performs the end-to-end functions of collecting link fault information,
periodically diagnosing faulty nodes, and performing self-healing on faults.
OMU Log Management Module (debug_log)

The OMU log management module performs the functions of regularly collecting and cleaning
up OMU logs.
Issue 08 (2012-02-27)

33
BSC6900 GSM
LMT Module (weblmt)

The LMT module traces messages, monitors performances, and maintains devices. It also
provides an interface for issuing MML commands.
Each process is logically independent, that is, when one process fails, other processes continue
to run normally. When a process stops unexpectedly, the OMU detects it in time and restarts the
process quickly.

The OMU works in single-OMU or dual-OMU mode.
Single-OMU Mode
When the BSC6900 is configured with one OMUa/OMUb/OMUc board, it works in singleOMU mode.
If the OMU is faulty, you cannot perform OM on the BSC6900. Therefore, the system is
unreliable when the OMU works in single-OMU mode.
NOTE
The GBAM works in only single-GBAM mode. That is, a BSC is configured with only one GBAM.
Dual-OMU Mode
When the BSC6900 is configured with two OMUa/OMUb/OMUc boards, it works in dual-OMU
mode.
In dual-OMU mode, the OMUa/OMUb/OMUc board working in active mode is called the active
OMUa board, that is, the active OMU; the OMUa/OMUb/OMUc board working in standby
mode is called the standby OMUa board, that is, the standby OMU. The active and standby OMU
boards must be of the same type. Mixed insertion of OMUc board and OMUa/OMUb board is
prohibited.
When the BSC6900 is in dual-OMU mode, the OMU can operate properly with high reliability.
When a hardware or software fault occurs on the active OMU, the standby OMU is automatically
switched over and works in active mode. It continues to provide services for users and the host.
NOTE
l Check the OMU working mode before you install the OMU applications.
l After the OMU applications are installed, run the DSP OMU command to query the OMU working mode.
2.7 OMU OM Methods

This section describes several scenarios and methods of the OMU OM.
Scenario 1: Installing the OMU Applications Before Field Commissioning

After the BSC6900 hardware is installed, the OMU applications should be installed before the
OMU commissioning.
Issue 08 (2012-02-27)

34
BSC6900 GSM
In this scenario, you need to log in to the OMU before performing the operations. For how to
log in to the OMU, see Logging In to the OMU. For detailed methods of setting up the operating
environment, see 4.1 Installing the OMU Applications in Field Commissioning.
Scenario 2: Setting and Reinstalling the OMU Operating System on Site

If the operating system crashes on site, reinstall the OMU operating system and OMU
applications, and reconfigure the OMU. For the software to be installed on the OMU, see 4.5.2
Checklist for the Factory Settings of the OMU Software.
In this scenario, you need to use the USB installation CD-ROM to reinstall the OMU operating
system. For detailed methods of setting up the operating environment, see 4.2 Reinstalling
Software Onsite.
Scenario 3: Operating the OMU Applications and Tools

In this scenario, you manage the components of the OMU applications and use the
omu_backup_linker and omutool.
In this scenario, you need to log in to the OMU before performing the operations. For how to
log in to the OMU, see Logging In to the OMU. For detailed methods of setting up the operating
environment, see 4.3 Operating and Maintaining the OMU.
Scenario 4: Performing Routine OM on the OMU

In this scenario, you periodically check the OMU hard disk space, clean up the OMU hard disk,
and perform routine OM on the operational state of the OMU.
In this scenario:
l
If you want to periodically check the OMU hard disk space and clean up the OMU hard
disk, you need to log in to the OMU and perform the operations. For details on how to log
in to the OMU, see Logging In to the OMU. For detailed methods of setting up the
operating environment, see 4.3.7 Maintaining the OMU Routinely.
If you perform routine OM on the operational state of the OMU, you need to log in to the
OMU through the LMT, and then perform the operations by running MML commands on
the MML client. For detailed methods of setting up the operating environment, see
BSC6900 GSM LMT User Guide.
Scenario 5: Upgrading the BSC6000 to the BSC6900

The operating system of the BSC6000 is SUSE Linux, and the operating system of the
BSC6900 is Dopra Linux. After the BSC6000 is upgraded to the BSC6900, SUSE Linux can
still be used 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.
Perform routine operation and maintenance on the OMU by referring to 5.2.22 Routine
OMU Maintenance After the Upgrade and 5.2 OMU Operation and Maintenance
After the Upgrade.
Issue 08 (2012-02-27)

35
BSC6900 GSM
2.8 OMU Safety Information

This section describes the safety information related to OMU operation.
l
To ensure proper operation of the OMU, do not create or delete directories, change directory
attributes, backup files, modify system file, change system file attributes, restart the
network, disable Ethernet adapters, modify configuration file for Ethernet adapters, or
configure routing.
To ensure proper operation of the OMU, you can install and run only the operating system
software (including necessary drivers and components) and OMU applications on the
OMU.
The operation 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 on the OMU.
Issue 08 (2012-02-27)

36
BSC6900 GSM
Working Principles of the OMU
About This Chapter

This chapter describes the operating principles of Ethernet adapters, related IP addresses, active
and standby workspaces, and active and standby OMUs.
This section describes the configuration of OMU Ethernet adapters.
The OMU Ethernet adapters must follow the IP address planning principles to meet the
requirements of the communication in the operation and maintenance network.
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
helps in 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, thus enabling quick switching between versions.
3.5 Heartbeat Test on Active/Standby OMUs
The dual-OMU system monitors the heartbeat to ensure that the active and the standby OMUs
work properly.
3.6 Synchronization Between the Active OMU and the Standby OMU
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 dual-OMU mode, there are four types of switchover: manual switchover,
fault-triggered switchover, failover, and self-healing switchover.
Issue 08 (2012-02-27)

37
BSC6900 GSM

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

An OMUa board is configured with six Ethernet adapters. To enhance the network reliability,
two Ethernet adapters are teamed for the communication in the external network, that is, the
communication between the OMU and the LMT/M2000, and another two adapters are teamed
for the communication in the internal network, that is, the communication between the OMU
and the BSC6900 boards.
The six Ethernet adapters on the OMUa board are as follows:
l
ETH0 and ETH1: The two Ethernet adapters are teamed as the external Ethernet adapter
team, that is, bond1/bond1:0, which is used for the communication between the OMU and
the LMT/M2000.
ETH2: ETH2 (bond2), a debugging Ethernet adapter, is connected to a portable PC for

OMU debugging if required.
ETH3-UPDATE: ETH3-UPDATE (bond3), a backup Ethernet adapter, is used for the

backup channel between the active OMU and the standby OMU when the BSC6900 is
configured with two OMUa boards.
ETH4-SCU7 and ETH5-SCU6: The two Ethernet adapters are teamed as the internal
Ethernet adapter team, that is, bond0 (vlan1/vlan1:0), which is used for the communication
between the OMU and the BSC6900 host boards.
Figure 3-1 shows the mapping between the ETHxxx and the bondxxx on the OMUa board.
Figure 3-1 Mapping between the ETHxxx and the bondxxx on the OMUa board
Issue 08 (2012-02-27)

38
BSC6900 GSM
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 you cannot see them on the panel of the OMUa board.
l bond1 and bond1:0: one is reserved for the external fixed IP address, and the other is reserved for the
external virtual IP address.
l ETH4-SCU7 and ETH5-SCU6 are teamed as the 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 is for the internal fixed IP address, and vlan1:0 is for the internal virtual IP address.
Configuration of Ethernet Adapters on the OMUb Board

An OMUb board is configured with six Ethernet adapters. To enhance the network reliability,
The six Ethernet adapters on the OMUb board are as follows:
l
ETH0 and ETH1 are teamed as external Ethernet adapter team, that is, bond1 which is used
for the communications between the OMU and the LMT/M2000.
ETH2: a debugging Ethernet adapter, is connected to a portable PC for OMU debugging

if required. The default IP address for ETH2 is 192.168.1.1 and subnet mask 255.255.255.0.
ETH3-UPDATE serves as a backup Ethernet adapter of the OMU. When the BSC6900 is
configured with two OMUb boards, this Ethernet adapter works as a dedicated backup
channel between the active OMU and the standby OMU.
ETH4-SCU7 and ETH5-SCU6 are teamed as the internal Ethernet adapter team, that is,
bond0, which is used for the communication between the OMU and the BSC6900 boards.
Figure 3-2 shows the mapping between the ETHxxx and the bondxxx on the OMUb board.
Figure 3-2 Mapping between the ETHxxx and the bondxxx on the OMUb board
NOTE
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 you cannot see them on the panel of the OMUa board.
Issue 08 (2012-02-27)

39
BSC6900 GSM
Configuration of Ethernet Adapters on the OMUc Board

An OMUc board is configured with seven Ethernet adapters. To enhance the network reliability,
The seven Ethernet adapters on the OMUc board are as follows:
l
F_ETH0 and F_ETH1: The two Ethernet adapters are teamed as the external Ethernet
adapter team, that is, bond1/bond1:0, which is used for the communication between the
OMU and the LMT/M2000.
F_DBG: a debugging Ethernet adapter, is connected to a portable PC for OMU debugging

if required.
B_UPDATE0 serves as a backup Ethernet adapter between the OMUc boards. When the
BSC6900 is configured with two OMUc boards, this Ethernet adapter works as a dedicated
backup channel between the active OMU and the standby OMU.
B_UPDATE1 serves as a backup Ethernet adapter between the OMUc board and the
OMUa/OMUb board. When the BSC6900 is configured with one OMUc board and one
OMUa/OMUb board, this Ethernet adapter works as a dedicated backup channel between
the active OMU and the standby OMU.
B_ETH0 and B_ETH1: The two Ethernet adapters are teamed as the internal Ethernet
adapter team, that is, bond0 (vlan1/vlan1:0), which is used for the communication between
the OMU and the BSC6900 host boards.
Figure 3-3 shows the mapping between the ETHxxx and the bondxxx on the OMUc board.
Figure 3-3 Mapping between the ETHxxx and the bondxxx on the OMUc board
Issue 08 (2012-02-27)

40
BSC6900 GSM
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 OMUa board.
l bond1 and bond1:0: one is reserved for the external fixed IP address, and the other is reserved for the
external virtual IP address.
l B_ETH0 and B_ETH1 are teamed as the 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 is used for the internal fixed IP address, and vlan1:0 is used for the internal virtual IP address.
Configuration of Ethernet Adapters on the GBAM

HUAWEI C5210 GBAM has three or four Ethernet adapters: two internal Ethernet adapters and
one or two external Ethernet adapters. Figure 3-4 shows the location of the Ethernet adapters
on the HUAWEI C5210 GBAM.
Figure 3-4 Location of Ethernet adapters on HUAWEI C5210 GBAM
1 Ethernet adapter integrated on the host
3 Ethernet adapter integrated on the PCI slot
NOTE
When three Ethernet adapters are configured on HUAWEI C5210 GBAM, Ethernet adapters indicated by 3 or
4 in Figure 3-4 are mutually exclusive.
IBM X3650T GBAM has four Ethernet adapters: two internal Ethernet adapters and two external
Ethernet adapters. Figure 3-5 shows the location of the Ethernet adapters on the IBM X3650T
GBAM.
Figure 3-5 Location of Ethernet adapters on IBM X3650T GBAM
Issue 08 (2012-02-27)

41
BSC6900 GSM
HP CC3310 GBAM has three Ethernet adapters: two internal Ethernet adapters and one external
Ethernet adapter. Figure 3-6 shows the location of the Ethernet adapters on the HP CC3310
GBAM.
Figure 3-6 Location of Ethernet adapters on HP CC3310 GBAM
3 Ethernet adapter port 1 integrated on the PCI slot
4 Ethernet adapter port 2 integrated on the PCI slot
Ethernet adapter teams on the GBAM are divided into internal Ethernet adapter team and external
Ethernet adapter team.
To bind the Ethernet adapters on the GBAM through an Ethernet adapter binding tool, do as
follows:
l
Bind eth0 and eth1 integrated on the host as Ethernet adapter team bond0 in which eth0
and eth1 work in active/standby mode.
Bind eth2 and eth3 installed in the PCI slot as Ethernet adapter team bond1 in which eth2
and eth3 work in active/standby mode. If only eth2 is installed on the PCI slot, then eth2
is bound as Ethernet adapter team bond1.
bond0 is the internal Ethernet adapter team in which eth0 and eth1 are internal Ethernet adapters
used for the communication between the GBAM and the BSC. eth0 and eth1 are automatically
configured with IP addresses 80.0.102.65 and 80.1.102.65 when they are bound as internal
Ethernet adapter team bond0. These two IP addresses are calculated based on the slot number
and subnet number. Currently, the slot number is 25 and subnet number is 80.
bond1 is the external Ethernet adapter team in which eth2 and/or eth3 are/is external Ethernet
adapter(s) used for the communication between the GBAM and the LMT/M2000. Only one IP
address 192.168.1.1 is configured for the external Ethernet adapters when they are bound as
external Ethernet adapter team bond1 before delivery.
Both the GBAM local process and GBAM core process use bond0. The GBAM local process,
which uses IP address 80.0.102.65, is used for the configuration and maintenance on the GBAM.
The GBAM core process, which uses the IP address 80.1.102.65, performs operation and
maintenance on the BSC with the joint effort of the GBAM core process and BSC boards.
Figure 3-7 and Figure 3-8 show the IP addresses for Ethernet adapters on the GBAM.
Issue 08 (2012-02-27)

42
BSC6900 GSM
Figure 3-7 IP addresses for three Ethernet adapters on the GBAM
Figure 3-8 IP addresses for four Ethernet adapters on the GBAM

The OMU Ethernet adapters must follow the IP address planning principles to meet the
requirements of the communication in the operation and maintenance network.
Issue 08 (2012-02-27)

43
BSC6900 GSM
NOTE
l The OMU in the existing network involves OMUa board, OMUb board, OMUc board, and GBAM. OMUb
board and GBAM are inventory materials, and therefore their IP addresses do not need to be planned for
site deployment. The original IP addresses of the OMUb and GBAM can be reserved in the case of upgrade.
l For details on the Ethernet adapter configuration of the OMUb board and GBAM, see 3.1 OMU Ethernet
Adapter Configuration.
l The following describes the IP address planning when OMUa and OMUc boards are used.
Description of IP addresses of the OMU

The OMU IP addresses include fixed internal/external IP addresses, virtual internal/external IP
addresses, and debugging IP address. If the BSC6900 is configured with two OMUa/OMUc
boards, the OMU IP addresses also include the backup channel IP address of the active and
standby OMUs.
Table 3-1 describes the IP addresses of the OMU.
Table 3-1 Description of IP addresses of the OMU
Issue 08 (2012-02-27)
IP
Addre
ss
Definition
Fixed
Externa
l IP
address
IP address for communication

between peripheral devices (for
example, a PC)and the OMU.
Function
Used for the

communication
between peripheral
The fixed external IP address is devices (for
automatically configured on the example, a PC) and
OMU external Ethernet adapter the OMU.
team when the OMU operating A PC can access the
system is installed.
LMT process of the
OMU, that is, log in
to the LMT, using
the fixed external IP
address.

Correspo
nding
Ethernet
Adapters
on the
OMUa
Board
Correspo
nding
Ethernet
Adapters
on the
OMUc
Board
l ETH0
l F_ET
H0
l ETH1
l F_ET
H1
44
BSC6900 GSM
IP
Addre
ss
Definition
Function
Correspo
nding
Ethernet
Adapters
on the
OMUa
Board
Correspo
nding
Ethernet
Adapters
on the
OMUc
Board
Externa
l virtual
IP
address
IP address for the

communication between
peripheral devices (for example,
LMT and M2000) and the
OMU.
Used for the

communication
between peripheral
devices (for
example, LMT and
M2000) and the
active OMU.
l ETH0
l F_ET
H0
The virtual external IP address

is configured on the Ethernet
adapter team of the active OMU
when the OMU applications are
installed, and it takes effect after
the OMU applications are
started.
l ETH1
l F_ET
H1
If active and standby

OMUs are switched
over when a
peripheral device
communicates with
the OMUs using the
fixed 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 starts to take
effect, and the virtual
external IP address
of the original active
OMU stops taking
effect.
A PC can access the
LMT process of the
OMU, that is, log in
to the LMT, using
the virtual external
IP address.
Issue 08 (2012-02-27)

45
BSC6900 GSM
IP
Addre
ss
Definition
Internal
fixed IP
address
IP address for the

communication between the
active OMU and the standby
OMU in the internal network
segment (network on which
information is exchanged using
the SCUa/SCUb board).
Internal
virtual
IP
address
Correspo
nding
Ethernet
Adapters
on the
OMUa
Board
Correspo
nding
Ethernet
Adapters
on the
OMUc
Board
Used for the

communication
between the active
and standby OMUs
in the internal
network segment
(network on which
The fixed internal IP address is information is
automatically configured on the exchanged using the
OMU internal Ethernet adapter SCUa/SCUb board).
team when the OMU operating The fixed IP address
is not used for the
communication
between the OMU
and the BSC6900
host boards.
l ETH4SCU7
l B_ET
H0
l ETH5SCU6
l B_ET
H1
IP address for the

active OMU and the BSC6900
host boards.
l ETH4SCU7
l B_ET
H0
l ETH5SCU6
l B_ET
H1
The virtual internal IP address is

configured on the internal
Ethernet adapter team of the
active OMU. It takes effect after
the OMU applications are
started.
Issue 08 (2012-02-27)
Function
Used for the

communication
between the active
OMU and the
BSC6900 host
boards.
The communication
between the
BSC6900 host
boards and the
OMUs are not
interrupted even if
the active and
standby OMUs are
switched over.

46
BSC6900 GSM
Issue 08 (2012-02-27)
IP
Addre
ss
Definition
Backup
channel
IP
address
of the
active
and
standby
OMUs
IP address for the

active OMU and the standby
OMU in the backup channel
network segment (network on
which information is exchanged
using an Ethernet cable).
Function
IP address for the

communication
between the active
OMU and the
standby OMU in the
backup channel
network segment
The backup channel IP address (network on which
of the active and standby OMUs information is
are configured automatically on exchanged using an
Ethernet cable).
the standby OMU Ethernet
adapter when the OMU
applications are installed.

Correspo
nding
Ethernet
Adapters
on the
OMUa
Board
Correspo
nding
Ethernet
Adapters
on the
OMUc
Board
ETH3UPDATE
l B_UP
DATE
0 (used
for the
comm
unicati
on
betwee
n two
OMUc
boards
)
l B_UP
DATE
1 (used
for the
comm
unicati
on
betwee
n the
OMUc
board
and the
OMUa
/
OMUb
board)
47
BSC6900 GSM
IP
Addre
ss
Definition
Function
Correspo
nding
Ethernet
Adapters
on the
OMUa
Board
Correspo
nding
Ethernet
Adapters
on the
OMUc
Board
Debugg
ing IP
address
IP address for performing

operation and maintenance on
the OMU when a PC is
connected to the debugging
Ethernet port of the OMU using
an Ethernet cable at the local
end.
IP address used for

connecting to the
OMU debugging
Ethernet port.
ETH2
F_DBG
Operation and
maintenance on the
OMU can be
performed on the PC
using the debugging
IP address. A PC can
access the LMT
process of the OMU,
that is, log in to the
LMT, using the
debugging IP
address.
Definition of Onsite Network

The network between the OMU external Ethernet adapters and the LMT/M2000 is defined as
external network, or onsite network. If the OMU external Ethernet adapters are connected to the
LMT/M2000 by routers, then the network between the OMU external Ethernet adapters and the
first router (gateway) is defined as onsite network. Figure 3-9 shows the onsite network.
l
The network between the OMU internal Ethernet adapters and the host boards is defined
as internal network. The OMU communicates with the base station through the host boards.
The network between the OMU external Ethernet adapters and the LMT/M2000 is defined
as external network. The OMU is connected to the LMT/M2000 either directly or through
multiple routers (gateway).
Figure 3-9 Onsite network
Issue 08 (2012-02-27)

48
BSC6900 GSM
Follow the following principles of configuring IP addresses on site:

l
If IP routes to the OMU are configured (by running the ADD OMUIPRT command),
ensure that the Forware Route Address and Destination Network Address to the LMT/
M2000 are not located in the same network segment as the internal virtual IP address,
internal fixed IP address, backup channel IP address, and debugging 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 Factory Settings of the OMU Software. The default IP addresses may fail
to meet the requirements of onsite network planning. Therefore, you must reconfigure some of
the OMU IP addresses.
Generally, the fixed external IP address and virtual external IP address need to be reconfigured
according to the network planning of the customer.
l
If one OMU is configured, the fixed external IP address and virtual external IP address
need to be planned and configured in the same network segment.
When active and standby OMUs are configured, the fixed external IP address of the active
OMU, the fixed external IP address of the standby OMU, and 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 address
The default fixed external IP address of the active OMU is

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 the fixed
external IP address and the onsite network are located in the same
network segment. In addition, the fixed external IP address cannot
conflict with the IP address of the live network.
2. If active and standby OMUs are configured, the fixed external IP
addresses of the active and standby OMUs must be different from and
located in the same network segment as the onsite network IP address.
Issue 08 (2012-02-27)

49
BSC6900 GSM
IP Address
Planning Principle
External virtual
IP address
1. Change the virtual external IP address as required. Ensure that the

virtual external IP address and the fixed external IP address are in the
same network segment (This network segment is named external
network segment). In addition, the virtual external IP address cannot
conflict with other IP addresses in the network segment.
For example, in dual-OMU mode, if 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. In single-OMU mode, for example, if 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.
Table 3-3 Onsite configuration of OMU IP addresses
IP Address
Checking Principle
Internal fixed IP
address
The default fixed internal IP address of the active OMU is 80.168.3.50

(255.0.0.0).
The default fixed internal IP address of the standby OMU is 80.168.3.60
(255.0.0.0).
Configuration 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. In dual-OMU mode, the fixed internal IP addresses of the active and
standby OMUs must be different and in the same network segment.
4. In single-OMU mode, if the network segment where the fixed internal
IP address is located does not conflict with the onsite network segment,
reserve the default setting of the fixed internal IP address.
Issue 08 (2012-02-27)

50
BSC6900 GSM
IP Address
Checking Principle
Internal virtual
IP address
1. The virtual internal IP address must be located in the same subnet as

the fixed internal IP addresses of the active and standby OMUs. This
subnet is named the OMU internal network segment. In addition, the
virtual internal IP address cannot be identical with other IP addresses
in the subnet.
For example, in dual-OMU mode, if 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. In single-OMU mode, for example, if 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.
Debugging IP
address
The default setting of the debugging IP address of the active OMU is

192.168.6.50 (255.255.255.0).
The default setting of the debugging IP address of the standby OMU is
192.168.6.60 (255.255.255.0).
Configuration principle:
1. The debugging 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 debugging IP address.
2. In dual-OMU mode, the debugging IP addresses of the active and
standby OMUs must be different and configured in the same network
segment.
For example, in dual-OMU mode, the debugging IP address of the
active OMU is 192.168.6.50 (255.255.255.0), and the debugging IP
address of the standby OMU is 192.168.6.60 (255.255.255.0).
3. In single-OMU mode, if the network segment where the debugging IP
address is located is different from the onsite network segment, retain
the default setting of the fixed internal IP address.
Issue 08 (2012-02-27)

51
BSC6900 GSM
IP Address
Checking Principle
Backup channel
IP address of the
active and
standby OMUs
For the active OMUa board, the default backup channel IP address of the
active and standby OMUs is 192.168.3.50 (255.255.255.0).
For the standby OMUa board, the default backup channel IP address of
the active and standby OMUs is 192.168.3.60 (255.255.255.0).
The default backup channel IP address of B-UPDATE0 of the active
OMUc board is 192.168.9.50 (255.255.255.0), and that of B-UPDATE1
of the active OMUc board is 192.168.3.50 (255.255.255.0).
The default backup channel IP address of B-UPDATE0 of the standby
OMUc board is 192.168.9.60 (255.255.255.0), and that of B-UPDATE1
of the standby OMUc board is 192.168.3.60 (255.255.255.0).
Planning principle:
1. The network segment where the backup IP addresses of the active and
standby OMUs are located cannot conflict with the onsite network
segment. If they conflict, the backup channel IP addresses of the active
and standby OMUs must be changed.
2. In dual-OMU mode, the backup channel IP addresses of the active and
standby OMUs must be different and configured in the same network
segment.
3. In single-OMU mode, if the network segment where the fixed internal
IP address is located is different from the onsite network segment,
retain the default setting of the fixed internal IP address.
Impact of Changes of OMU IP Addresses

Changing IP addresses impact the working of the BSC6900, as described in Table 3-4.
Table 3-4 Impact of Changes of OMU IP Addresses
IP Address
Change Impact
Fixed External
IP address
After the fixed external IP address is changed, the device that is connected
to the external Ethernet port can access the OMU only using the new fixed
external IP address.
The fixed external IP address can be changed remotely, and takes effect
immediately after it is changed.
External virtual
IP address
After the virtual external IP address is changed, the device that is

connected to the OMU through the IP address cannot access the OMU
unless through the new virtual external IP address.
The virtual external IP address can be changed remotely, and takes effect
immediately after it is changed.
Issue 08 (2012-02-27)

52
BSC6900 GSM
IP Address
Change Impact
Internal fixed IP
address
The internal fixed IP address and the IP addresses of theBSC6900 host

boards have been planned. Therefore, only the network segment on which
the internal fixed IP address is located can be changed so that it is not
identical with the IP addresses of the BSC6900 host boards.
The internal fixed 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 internal fixed IP address can be changed remotely. After it is changed,
you must reset the BSC6900 host at the local end.
Internal virtual
IP address
The virtual internal IP address and fixed internal IP address must be

changed at the same time.
After the internal virtual IP address is changed, reset the BSC6900 host
so that the communication between the OMU and the BSC6900 host can
be re-established.
The internal virtual IP address is usually changed when the OMU is
debugged on site to avoid negative effects caused by frequency resets of
the BSC6900 during daily maintenance.
The internal virtual IP address can be changed remotely. After it is
changed, you must reset the BSC6900 host at the local end.
Backup channel
IP address of the
active and
standby OMUs
After the backup channel IP addresses of the active/standby OMUs are

changed, reset the OMUs so that the communication between the active
OMU and the standby OMU can be re-established.
l In dual-OMU mode, the backup channel IP addresses of the active and
standby OMUs must be in the same network segment. Otherwise, the
communication between the active and standby OMUs fails.
l In single-OMU mode, the backup channel IP address of the active and
standby OMUs needs to be changed only if it conflicts with the onsite
network segment.
The backup channel IP address of the active and standby OMUs can be
changed remotely, and takes effect immediately after it is changed.
Debugging IP
address
After the debugging IP address is changed, the device that is connected to

the debugging Ethernet port cannot access the OMU unless through the
new debugging IP address.
The debugging IP address must be changed by connecting the debugging
Ethernet port, and takes effect immediately after it is changed.
Issue 08 (2012-02-27)

53
BSC6900 GSM
NOTE
l The internal and external fixed IP addresses are bound to the active and standby OMU boards, and the virtual
internal and external IP addresses are bound to the active OMU. For example, after the switchover of the
active/standby OMUs, the internal/external fixed IP addresses of the original active/standby OMUs remain
the same, the internal/external virtual IP addresses of the original active OMU become the internal/external
virtual IP addresses of the original standby OMU. There is no internal/external virtual IP addresses for the
original active OMU.
l The following IP addresses must be in the same network segments: fixed internal IP address and virtual
internal IP address, fixed external IP address and virtual external IP address, backup channel IP address of
the active OMU and backup channel IP address of the standby OMU, debugging IP address of the active
OMU and debugging IP address of the standby OMU. The network segments cannot conflict with each
other, nor can the IP addresses in a network segment conflict.
l Record the IP addresses in 4.5.1 Records of OMU Software Installation Information.
l The next hop IP address of the route to the M2000 must be the virtual external IP address of the OMU.
l For principles of configuring the BSC local IP address, see 8.1 Scenario of Connecting the OMU and
VNP.

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
helps in the communication between the BSC6900 and the OM terminals.
Single-OMUa/OMUb/OMUc Networking Principle

Figure 3-10, Figure 3-11, Figure 3-12, and Figure 3-13 show the networking in single-OMUa/
OMUb/OMUc mode.
Issue 08 (2012-02-27)

54
BSC6900 GSM
Figure 3-10 Single-OMUa/OMUb Networking Principle (with a single LAN switch)
Issue 08 (2012-02-27)

55
BSC6900 GSM
Figure 3-11 Single-OMUc Networking Principle (with a single LAN switch)
Issue 08 (2012-02-27)

56
BSC6900 GSM
Figure 3-12 Single-OMUa/OMUb Networking Principle (with dual LAN switches)
The two internal Ethernet adapters ETH4-SCU7 and ETH5-SCU6 of the OMUa/OMUb 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/OMUb board are connected
to the OM terminals through network equipment such as hub, LAN switch, and router. In this
way, the OMU fulfills the communication between the BSC6900 and the OM terminals.
As shown in Figure 3-12, the two external Ethernet ports of the OMUa/OMUb board are
connected to the two LAN switches respectively, improving the 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-12 must be enabled with the Spanning
Tree Protocol (STP) function to prevent network storms.
Issue 08 (2012-02-27)

57
BSC6900 GSM
Figure 3-13 Single-OMUc Networking Principle (with dual 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 hub, LAN switch, and router. In this way,
the OMU fulfills the communication between the BSC6900 and the OM terminals.
As shown in Figure 3-13, the two external Ethernet ports of the OMUc board are connected to
the two LAN switches respectively, improving the 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-13 must be enabled with the Spanning Tree
Protocol (STP) function to prevent network storms.
Issue 08 (2012-02-27)

58
BSC6900 GSM
Dual-OMUa/OMUb/OMUc Networking Principle

Figure 3-14, Figure 3-15, Figure 3-16, Figure 3-17, Figure 3-18, and Figure 3-19 show the
networking in dual-OMUa/OMUb/OMUc mode.
Figure 3-14 Dual-OMUa/OMUb Networking Principle (with a single LAN switch)
Issue 08 (2012-02-27)

59
BSC6900 GSM
Figure 3-15 Dual-OMUc Networking Principle (with a single LAN switch)
Issue 08 (2012-02-27)

60
BSC6900 GSM
Figure 3-16 Dual-OMUa/OMUc Networking Principle (with a single LAN switch)
Issue 08 (2012-02-27)

61
BSC6900 GSM
Figure 3-17 Dual-OMUa/OMUb Networking Principle (with dual LAN switches)
The two internal Ethernet adapters ETH4-SCU7 and ETH5-SCU6 of the OMUa/OMUb 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/OMUb board are connected
to the OM terminals through network equipment such as hub, LAN switch, and router. In this
way, the OMU fulfills the communication between the BSC6900 and the OM terminals.
The ETH3-UPDATE of the active OMUa/OMUb board is connected to the ETH3-UPDATE of
the standby OMUa/OMUb 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-17, the two external Ethernet ports of the active and standby OMUs are
connected to the two LAN switches respectively, thereby improving the 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
Issue 08 (2012-02-27)

62
BSC6900 GSM
ETH1. Moreover, the Ethernet adapter marked in blue in Figure 3-17 must be enabled with the
STP function to prevent network storms.
Figure 3-18 Dual-OMUc Networking Principle (with dual 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 hub, LAN switch, and router. In this way,
the OMU fulfills the communication between the BSC6900 and the OM terminals.
The B_UPDATE0 of the active OMUc board is connected to the B_UPDATE0 of the standby
OMUc board through the backplane. This permits data synchronization and update of OMU
software between the active and standby OMUs.
Issue 08 (2012-02-27)

63
BSC6900 GSM
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-18 must be enabled with
the STP function to prevent network storms.
Figure 3-19 Single-OMUc/OMUa Networking Principle (with dual 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 hub, LAN switch, and router. In this way, the OMU fulfills the
communication between the BSC6900 and the OM terminals.
Issue 08 (2012-02-27)

64
BSC6900 GSM
The B_UPDATE1 of the active OMUc board is connected to the ETH3UPDATE of the standby
OMUa board through the backplane. This permits data synchronization and update of OMU
software between the active and standby OMUs.
this 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-18 must
be enabled with the STP function to prevent network storms.
GBAM Networking Principle

Figure 3-20 and Figure 3-21 show the networking principle concerning the GBAM and LAN
switch.
Figure 3-20 GBAM networking topology (with a single LAN switch)
Issue 08 (2012-02-27)

65
BSC6900 GSM
Figure 3-21 GBAM networking topology (with dual LAN switches)
As shown in Figure 3-20 and Figure 3-21, eth0 and eth1 are internal Ethernet adapters, and
eth2 and eth3 are external Ethernet adapters. The HUAWEI C5210 GBAM has only one external
Ethernet adapter, that is, the HUAWEI C5210 GBAM does not have eth3. This figure takes two
external Ethernet adapters of the GBAM as an example.
The two internal Ethernet adapters of the GBAM are respectively connected to ports 10 on the
active and standby SCUa boards in the MPS. Ports 10 on the active and standby SCUa boards
in the MPS form a trunk group. This ensures that the communication between the GBAM and
the SCUa board is normal even if the Ethernet port on the GBAM or SCUa board fails. There
are twelve 10/100/1000 Mbit/s Ethernet ports on the panel of each SCUa board. Port 10 is used
to connect the SCUa board to the GBAM, and other ports are used to connect the SCUa board
to other boards in the MPS in star network topology.
NOTE
Trunk group is a function based on which multiple physical ports are bound to serve as a logical port, so that
multiple links are backed up and there is a balance of traffic volume between multiple links.
As shown in Figure 3-21, the two external Ethernet ports of the GBAM are connected to the
two LAN switches respectively, thereby improving the network reliability. In this network
Issue 08 (2012-02-27)

66
BSC6900 GSM
topology, the Ethernet ports connecting the eth2, eth3, and LAN switches must be in the same
Intranet as the two Ethernet ports on the LAN switches connecting eth2 and eth3. Moreover, the
Ethernet adapter marked in blue in Figure 3-21 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, thus 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 relation between the active/standby workspaces is relative. The active/standby relation
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 pre-upgrade version.
2.
The active OMU runs the pre-upgrade version.
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.
Relation 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.
Issue 08 (2012-02-27)

67
BSC6900 GSM
Relation 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.
Relation 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 Test on Active/Standby OMUs

The dual-OMU system monitors the heartbeat to ensure that the active and the standby OMUs
work properly.
The heartbeat refers to messages with responses. Both the active and the standby OMUs send
the heartbeat. The dual-OMU system monitors the heartbeat to ensure that the active and the
standby OMUs work properly and the network connection is normal.
The principle of heartbeat test is: The active/standby OMUs send a message about its status to
each other and simultaneously check the message from each other, and then determine the active/
standby state according to the active/standby policy, and finally switchover is performed through
negotiation. If an OMU cannot receive the message from the other for a period, the latter is
considered faulty and the switchover is triggered.
3.6 Synchronization Between the Active OMU and the

Standby OMU
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 then the increments are
synchronized. This ensures that the OMU can work normally after the switchover.
File Synchronization
The synchronization between active OMU files and standby OMU files is mainly applicable to
the dynamically changing files. The dynamic changing files include license file, board program,
BOOTROM file, DSP file, patch file, and performance measurement file, and so on. The
software 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, so that the files on the
active and standby OMUs are the same.
Issue 08 (2012-02-27)

68
BSC6900 GSM
Time Synchronization
Time synchronization means that the sntp module on the standby OMU regularly synchronizes
the time with that of the sntp module on the active OMU so that the time on the active and
standby OMUs is the same.
3.7 Switchover Between Active and Standby OMUs

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

69
BSC6900 GSM
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 for a longer time than the failover interval, a failover occurs. The
failover may interrupt OMU services for a short period. To reduce the impact on the services,
the failover usually occurs between 3 and 5 o'clock in the morning.
You can run the SET ASWPARA command to set whether the failover between the active OMU
and the standby OMU is allowed. You can also run this command to set the failover interval.
NOTE
l The failover is only functional on the OMU running Windows.

l Note that you should not set parameters during the failover. You can query when the failover occurs 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 under any of the following conditions:
l
The hard disk capacity of the active OMU overflows with the remaining space being smaller
than 200 megabytes.
The active OMU has abnormal processes.
No Ethernet cable is connected to the external Ethernet ports on the active OMU.
The internal or external virtual IP address of the active OMU is lost for more than 3 minutes.
Issue 08 (2012-02-27)

70
BSC6900 GSM
Scenario: Creating a BSC6900 NE
About This Chapter

OMU when a BSC6900 NE is created.
Context
NOTE
You are advised to use an OMUc board when creating a BSC6900 NE.
In this scenario, the OMUa/OMUc board serves as an OMU. For instructions on how to replace
a faulty OMUa/OMUc board, see Replacing an OMU Board in theBSC6900 GSM.
The OMU software consists of the operating system and the OMU applications. It performs
operation and maintenance for the BSC6900. Figure 4-1 shows the OMU software structure.
Figure 4-1 OMU software structure
Operating system
The Dopra Linux operating system is used.
OMU applications
Based on the operating system, the OMU applications provide all types of service progress.
NOTE
After OMU applications are installed, confirm that the gateway IP address has been configured.
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 version of the OMU application is
Issue 08 (2012-02-27)

71
BSC6900 GSM
correct. Before you use the OMU for the first time, you need to check the installation status of
the OMU applications and configure the IP addresses, subnet mask, and OMU name on site
according to the IP address planning principle.
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
This section describes how to perform operation and maintenance on the OMU after OMU
applications are installed. To perform this task, you can 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 OM on the OMU.
4.5 Appendix: OMU-Related Information Tables
This section describes the tables in which the OMU information is recorded during the routine
operation and maintenance on the OMU.
Issue 08 (2012-02-27)

72
BSC6900 GSM
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 version of the OMU application is
correct. Before you use the OMU for the first time, you need to check the installation status of
the OMU applications and configure the IP addresses, subnet mask, and OMU name on site
according to the IP address planning principle.
4.1.1 Setting the Link Mode of the 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 of the LAN switch has been set to full-duplex.
Context
The link mode of the OMUa/OMUc external Ethernet adapters must be the same as that of the
LAN switch. If they are different, the network may be interrupted. If the link mode of the LAN
switch is specified, the link mode of the external Ethernet adapter on the OMUa/OMUC board
panel must be specified.
There are two link modes of the LAN switch: force mode and auto-negotiation mode.
Procedure
Step 1 Log in to the OMU by referring to Logging In to the OMU.
Step 2 Query the logic names of external OMU Ethernet adapters.
Option
Description
OMUa board 1. Type the /root/eth_alias_omu.sh command and press Enter.

OMUc board 1. Run the chmod +x ./eth_alias_names.sh command to acquire the
permission for running the ./install_bam.sh command.
2. Type the ./eth_alias_names.sh command and press Enter.
NOTE
External Ethernet adapters of the OMUa board are ETH0 and ETH1, and those of the OMUc board are
F_ETH0 and F_ETH1. This task is performed on the logical OMU external Ethernet adapters.
The mapping between the OMU physical Ethernet adapters and the OMU logical Ethernet adapters is
variable. Assume that:
l The logic names of OMU external Ethernet adapters are eth0 and eth1.
l The force mode is full-duplex with a rate of 100 Mbit/s.
Issue 08 (2012-02-27)

73
BSC6900 GSM
Step 3 Run the ethtool eth0 command to query the eth0 link mode. The following information (an
example) is displayed. Verify that the fields Speed, Duplex, and Auto-negotiation are
consistent with those of the link mode of the LAN switch.
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: 100Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: umbg
Wake-on: g
Current message level: 0x00000007 (7)
Link detected: yes
Option
Description
The link mode of eth0 is the

End this task.
same as that of the LAN switch.
The link mode of eth0 is
Go to Step 4.
different from that of the LAN
switch.
Step 4 Set the link mode of the OMUa external Ethernet adapters according to the link mode of the
LAN switch.
Option
Description
The link mode of the LAN

switch is force,
Enter the ethtool -s eth0 speed 100 duplex full autoneg

off command.

switch is auto-negotiation.
Enter the ethtool -s eth0 speed 100 duplex full autoneg on

command.
NOTE
The fields in the command are described as follows:

l speed *** indicates Ethernet adapter rate: speed 10, speed 100, or speed 1000.
l duplex ***indicates duplex mode of the Ethernet adapters: full duplex mode (duplex full) or half duplex
mode (duplex half).
l autoneg *** indicates link mode of the Ethernet adapters: force (autoneg off) or auto-negotiation mode
(autoneg on).
Step 5 Repeat Step 3 through Step 4 to set the eth1 link mode.
NOTE
The link modes of eth0 and eth1 must be the same.

Do not reset the OMU before performing Step 6. Otherwise, the setting of the eth1 link mode becomes invalid.
Step 6 Create an Ethernet adapter attribute file.

Issue 08 (2012-02-27)

74
BSC6900 GSM
1.
Enter the cd /etc/rc.d command to go to the target directory.
2.
Enter the touch rc.local command to add the Ethernet adapter attribute file.
3.
Enter the vi rc.local command to open the Ethernet adapter attribute file.
4.
Enter a (lower-case) to switch to the editing mode. Enter the command provided in Step
4 to set the link mode of the OMUa external Ethernet adapter according to the link mode
of the LAN switch.
l If the link mode of the LAN switch is force, type ethtool -s eth0 speed 100 duplex full
autoneg off and press Enter. Then, enter ethtool -s eth1 speed 100 duplex full autoneg
off.
l If the link mode of the LAN switch is auto-negotiation, type ethtool -s eth0 speed 100
duplex full autoneg on and press Enter. Then, enter ethtool -s eth1 speed 100 duplex
full autoneg on.
5.
Press ESC to switch to the command line mode. Type the :wq command and press
Enter to save and exit the rc.local file.
6.
Enter the cat rc.local command to check the contents of the rc.local file to determine
whether the file is created successfully.
If it fails to be created, repeat 6.3 through 6.5 to re-create it.
If the contents of the rc.local file are consistent with the settings, the Ethernet adapter
attribute file is created successfully. Otherwise, the Ethernet adapter attribute file fails to
be created.
7.
Run the chmod +x rc.local command to add permissions for executing the scripts.
8.
Run the exit command to end this task.
----End
4.1.2 Debugging OMU on Site

Before you use the OMU for the first time, you need to debug the OMU on site to check the
installation status and version of the OMU applications.
Prerequisites
The OMU is connected to the local PC through the debugging Ethernet port.
Context
NOTE
This chapter uses the OMUa board as an example for your reference.
Procedure
Step 1 Set the link mode of the external OMU Ethernet adapter by referring to 4.1.1 Setting the Link
Mode of the External OMU Ethernet Adapters.
Step 2 Connect the PC to the ETH2 debugging port on the OMU board by using an Ethernet cable.
Step 3 Set the IP address of the PC to be on the same network segment with the ETH2 port. The initial
IP address of the ETH2 port is 192.168.6.50 or 192.168.6.60, the subnet mask is 255.255.255.0.
Issue 08 (2012-02-27)

75
BSC6900 GSM
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.
The information displayed is No such file or

directory
Install the OMU application in the active

workspace by referring to Installing the
OMU Applications in the Active
Workspace.
Step 6 Run the cd /mbsc/upgrade command to switch to the OMU installation directory, and then run
the ls command to query the current version of the OMU application.
If...
Then...
The version of the OMU application is the

same as required by the operator
Perform steps Step 7 through Step 16.
The version of the OMU application is

different from what is required by the
operator
1. Uninstall the OMU application by

referring to Uninstalling the OMU
Applications.
2. Upload the OMU application installation
package to the OMU by referring to
Uploading the OMU Application
Installation Package to the OMU.
3. Install the OMU application in the active
workspace by referring to Installing the
OMU Applications in the Active
Workspace.
4. Perform steps Step 7 through Step 10.
5. Perform steps Step 14 through Step 16.
Step 7 Run the cd /mbsc/bam/version_a/bin/bam command to switch to the directory where the
omutool program locates.
NOTE
To view the help information of the omutool, run the ./omutool -h command.
Step 8 Change the external fixed IP address, subnet mask, and the gateway IP address according to the
plan of the operator.
Run the ./omutool extercard The external fixed IP address The subnet mask (The gateway IP
address) command to change the external fixed IP address and the subnet mask. For example,
you can type the following command and then press Enter.
./omutool extercard 10.161.10.100 255.255.255.0
Issue 08 (2012-02-27)

76
BSC6900 GSM
NOTE
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 OMU 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 (The gateway IP
address) 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
l The network segments of the fixed and virtual external IP addresses must be the same. If the network
segment 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 connection between the OMU and peripheral
equipment.
Step 10 Check whether the internal fixed IP address, internal virtual IP address, backup channel IP
address, and debugging IP address of OMU are on the same network segment as the network of
the operator.
Issue 08 (2012-02-27)

77
BSC6900 GSM
If...
Then...
Any IP address is on the same

network segment as the network of
the operator
l Change the IP address. Run the ./omutool innercard

The internal fixed IP 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
address and the subnet mask. For example, you can
type the following command and then press Enter.
./omutool innervip 80.168.3.40
NOTE
l When you change the fixed and virtual internal IP
addresses, the corresponding subnet masks are created
automatically.
l The network segments of the fixed and virtual internal
IP addresses must be the same. 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 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 OMU:
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
command. For example, you can type the
following command and then press Enter.
./omutool backupcard_for_omuc 192.168.9.60
l Run the ./omutool debugcard The debugging IP

address command to change the debugging IP
address and the subnet mask. For example, you can
type the following command and then press Enter.
./omutool debugcard 192.168.6.60
Issue 08 (2012-02-27)

78
BSC6900 GSM
If...
Then...
All IP addresses are not on the

same network segment as the
network of the operator
Change the backup channel IP address and subnet mask

of the OMU:
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.
l If OMUc boards are used, run the ./omutool

backupcard_for_omuc The IP address command.
For example, you can type the following command
and then press Enter.
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.
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 GO 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.
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.
Issue 08 (2012-02-27)

79
BSC6900 GSM
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 4.4.1 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 GO, and then set
officename.
5. Input put reg.ini in the psftp command line window to upload the modified reg.ini file from the local
PC to the OMU.
Step 14 Run the /etc/rc.d/omud start command to start the OMU application.
Step 15 Run the ps -afx command to check the operating status of the OMU.
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, btsom, ems_agent,
omu_manager, cfa, weblmt, debug_log
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 by referring to Uninstalling the OMU Applications, and then install the OMU application in
the active workspace again by referring to Installing the OMU Applications in the Active Workspace.
Step 16 Exit the OMU by referring to Logging Out of the OMU.

----End

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.
Issue 08 (2012-02-27)

80
BSC6900 GSM
Configuration of the OMUa and OMUc Boards

See the hardware configuration indexes of the OMUa and OMUc boards described in 2.2.5
Technical Index for the OMUa/OMUb/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
Configuration
Minimum Configuration
CPU
1.66 GHz or faster
866 MHz
RAM
512 MB
256 MB
Hard disk
80 GB
10 GB
Display
adapter
resolutio
n
1024x768 pixels or higher
800600
CD drive
USB
installati
on drive
Operatin
g system
l Microsoft Windows XP
Professional
l Microsoft Windows
Server 2003
l Microsoft Windows 7
Software Required for the Installation

Ensure that the following software package is available:
l
BSC6900 version installation package or patch installation package
Dopra_Linux_USB Disks
NOTE
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.
Issue 08 (2012-02-27)

81
BSC6900 GSM

This section describes how to prepare a USB storage device to install and restore the OMU
operating system quickly.
Prerequisites
l
The memory 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.
The USB storage device is inserted into an available USB port on the portable computer.
The USB port on the portable computer can be read and written.
You have obtained the planned OMU IP addresses and the OMU name and recorded them
in the Configuraion Information for Preparing USB Disk for Installation.
Context
The USB storage device can be used to install the OMU operating system or install both the
OMU operating system and the OMU applications. This depends on whether the OMU version
installation package or patch installation package is installed during the process of preparing the
USB storage device.
The USB storage device is used in the following scenarios:
l
Initial installation of the OMU operating system and applications
Restoring of the collapsed OMU operating system
When the USB storage disk is used to perform operations on the OMU, the data on the OMU is
impacted:
l
If the operation mode of the USB storage device is Install, OMU data is erased as the hard
disk drive is re-formatted in the process of installing the OMU operating system by using
the USB storage device. Make sure you have backed up the OMU data before installing
the OMU operating system by using the USB storage device.
If the operation mode of the USB storage device is Recover, then only the OMU operating
system is recovered. The OMU applications and data are retained.
NOTE
The modified and deleted system files cannot be restored by using the USB storage device. The USB storage
device is applicable to only the following scenarios:
1. The OMU operating system cannot be started properly.
2. A message is displayed when the OMU operating system is started, prompting you to restore the file system.
3. After the OMU operating system is started, a message is displayed, indicating a error of Kernel panic or
failure of loading rootfs.
If the OMU operating system cannot be restored by using the USB storage device, you are advised to reinstall
the OMU operating system by using the USB storage device.
Before preparing the USB storage device, verify it by referring to the DOPRA Linux USB Disk
Certificate Guide under the directory where the Dopra Linux USB disk is saved. If the USB
storage device is not usable, replace it. The Netac U208 (2G) is recommended.
The duration of preparing the USB storage device varies according to the bandwidth of the
network from the LMT PC to the equipment room, USB protocol, and LMT PC performance.
The duration listed in Table 1 refers to the duration of preparing a USB storage device in
compliance with the USB2.0 protocol. The duration of preparing a USB storage device in
Issue 08 (2012-02-27)

82
BSC6900 GSM
compliance with the USB1.1 protocol is twice that of preparing a USB storage device in
compliance with the USB2.0 protocol. A much longer duration may result from a poor LMT PC
performance. In this case, restart the LMT PC or use a LMT PC of higher performance.
Table 4-2 Operation and Duration
Operation
Duration
Preparing a USB storage device.
The duration varies according to the

bandwidth of the network from the LMT PC
to the equipment room.
l If the network is 1 Mbit/s or faster:
It takes 15 to 30 minutes when a single
OMU is configured.
It takes 30 to 50 minutes when dual
OMUs are configured.
l If the bandwidth is 512 kbit/s:
OMU is configured.
Install, restore, or switch the OMU operating

system from a USB storage device.
20 to 40 minutes
NOTE
This task assumes that you are preparing the USB storage device for dual OMU. Differences in preparing the
USB storage device between in dual-OMU mode and in single-OMU mode are specified.
Procedure
l
Prepare the USB storage device for the initial installation of the OMU operating system
and applications.
1.
Issue 08 (2012-02-27)
Double-click U_creator_eng.exe to open the USB storage device for installing a

Dopra Linux operating system, as shown in Figure 4-2.

83
BSC6900 GSM
Figure 4-2 U_creator_eng window
2.
Select NE List in the area in the left pane of the window shown in Figure 4-2, rightclick the NE list, and choose Add NE. A dialog box is displayed, as shown in Figure
4-3.
Figure 4-3 Add NE dialog box
3.
Issue 08 (2012-02-27)
Enter the NE Name, set the Operate type to Install, select Install OMU?, and click
OK. An NE is added.
84
BSC6900 GSM

NOTE
l If the OMU applications are to be installed initially, select Install OMU? and enter the External
Virtual IP Address of the NE to be added.
l The NE name is used to identify NEs, and it is composed of only letters, numerals, "-", and "_".
l After an NE is added, the NE name and the external virtual IP address can be changed only after
you delete the NE and then add the NE again.
l If you want to prepare multiple USB disks, it is recommended that you prepare the USB disks
one by one and mark the USB disks.
4.
Double-click the added NE in the left pane of the window. The window is updated,
as shown in Figure 4-4.
Figure 4-4 Configuring information
NOTE
l The IP addresses shown in Figure 4-4 are default IP addresses of the Dopra Linux tool. Change
the IP addresses as required. For details on the principle of changing the IP addresses, see 3.2
Planning of the OMU IP Addresses.
l Select the link mode of external Ethernet adapters listed in Figure 4-4 as required. Note that the
link mode of external Ethernet adapters must be consistent with that of the onsite LAN switch.
Table 4-3 lists the mapping between the queried link mode of OMU external Ethernet adapters
and that selected in Figure 4-4.
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-4.
l If only one OMU is configured, the active OMU configuration is effective while the standby
OMU configuration is not.
Issue 08 (2012-02-27)

85
BSC6900 GSM
Table 4-3 Mapping Between the Queried and Selected Link Mode of the OMU
External Ethernet Adapter
Queried Link Mode of the OMU
Link Mode of the OMU External

Ethernet Adapter to Be Selected
l Auto-negotiation is on.
Link mode of the OMU external

Ethernet adapter to be selected is Auto.
l Auto-negotiation is off.

Ethernet adapter to be selected is 10Mb
Full.
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.
5.

Half.
Full.
Half.
After all the information is automatically obtained, check whether the information is
correct and enter the information that needs to be typed.
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.
6.
Check that all the information is correct and click OK. A dialog box is displayed.
Check that the directory where the USB storage device is located to 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 When the system prompts a message, asking you to check the preparing of the USB storage
device, you can insert or remove the USB storage device.
l If only one OMU is configured, the standby OMU USB storage device does not need to be
prepared.
Prepare the USB storage device for restoring the OMU operating system.
1.
Issue 08 (2012-02-27)
Double-click U_creator_eng.exe to open the USB storage device for installing a

Dopra Linux operating system, as shown in Figure 4-2.

86
BSC6900 GSM
2.
Select NE List in the area in the left pane of the window shown in Figure 4-2, rightclick the NE list, and choose Add NE. A dialog box is displayed, as shown in Figure
4-5.
3.
Enter the NE Name, set the Operate type to Install, select Install OMU?, and click
OK. An NE is added.
NOTE
l The NE name can only be changed after you delete the NE and then add the NE.
l If you want to prepare multiple USB disks, it is recommended that you prepare the USB disks
one by one and mark the USB disks.
4.
Issue 08 (2012-02-27)
Double-click the added NE in the left pane of the window. The window is updated,
as shown in Figure 4-6.

87
BSC6900 GSM
NOTE
l The IP addresses shown in Figure 4-6 are default IP addresses of the Dopra Linux tool. Change
the IP addresses as required. For details on the principle of changing the IP addresses, see 3.2
Planning of the OMU IP Addresses.
l Select the link mode of external Ethernet adapters listed in Figure 4-6 as required. Note that the
link mode of external Ethernet adapters must be consistent with that of the onsite LAN switch.
l For the single-OMU mode, the active OMU configuration is effective while the standby OMU
configuration is not.
5.
After all the information is automatically obtained, check whether the information is
correct and enter the information that needs to be typed.
6.
Check that all the information is correct and click OK. A dialog box is displayed.
Check that the directory where the USB storage device is located to 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 When the system prompts a message, asking you to check the preparing of the USB storage
device, you can insert or remove the USB storage device.
l If only one OMU is configured, the standby OMU USB storage device does not need to be
prepared.
----End
Issue 08 (2012-02-27)

88
BSC6900 GSM
4.2.3 Installing the OMU Operating System from a USB Storage

Device
This section describes how to install or restore the OMU operating system from a USB storage
device.
Prerequisites
l
The USB storage device has been prepared. For details, see 4.2.2 Preparing the USB
Storage Device.
There are USB ports available on the OMU board panel.

NOTE
The USB storage device with an LED is inserted into the USB port. If the LED is on, then the USB port
is available.
Procedure
Step 1 Insert the USB storage device into any of the USB ports on the OMUa/OMUc board panel.
Step 2 Remove and then install the OMUa/OMUc board to reset the OMU. For details, see Removing
a Board and Inserting a Board.
Step 3 Wait 1 to 2 minutes and install the OMU operating system from the USB storage device. Check
the status of LED on the OMU board panel to determine whether the installation of the OMU
operating system is complete.
l If only the operating system is to be installed on the OMU, check the LED status. See Table
4-4.
l If the operating system and applications are to be installed on the OMU, check the LED
status. See Table 4-5.
l If the OMU operating system is to be recovered, check the LED status. See Table 4-5.
NOTE
The status of the LEDs on the OMU board panel can be: RUN LED blinks, ALM LED blinks, ACT LED blinks,
or OFFLINE LED is off.
If the status of the LEDs differs from the preceding status, the OMU cannot identify the USB storage device.
Use another USB storage device and prepare it. Alternatively, copy the data in the original USB storage device
to a new USB storage device, and then reinstall the OMU operating system.
See the duration of the OMU operating system installation, see Table 4-2 in 4.2.2 Preparing the USB Storage
Device.
Table 4-4 Status of the LEDs on the OMUa/OMUc board panel when the OMU operating system
is installed
Board
Successful Installation
Failed Installation
OMUa
l The RUN LED blinks.
l RUN LED is off.
l ALM LED is off or

blinks.
l The ALM LED blinks.
l ACT LED is off.
l OFFLINE LED blinks.
l ACT LED is off.
l The OFFLINE LED is

off.
Issue 08 (2012-02-27)

89
BSC6900 GSM
Board
Failed Installation
OMUc
l RUN LED is off.
l ALM LED is off.
l ACT LED is off.
l ACT LED is off.
Table 4-5 Status of the LEDs on the OMUa/OMUc board panel when the OMU operating system
and OMU applications are installed
Board
Failed Installation
OMUa
l ALM LED is steady on or

off.
l ALM LED is steady on or

off.
l ACT LED is off.

l ACT LED is steady on or l The OFFLINE LED is
off.
off.
off.
OMUc
l ACT LED is off.

l ACT LED is steady on or l The OFFLINE LED is
off.
off.
off.
CAUTION
Remove the USB storage device from the OMU board panel in time after the OMU operating
system is installed successfully.
----End
Follow-up Procedure
If the OMU operating system fails to be installed, perform the following operations:
1.
Prepare a new USB storage device. For details, see 4.2.2 Preparing the USB Storage
Device. Then, install the OMU operating system again.
l If the OMU operating system is installed successfully, end this task.
l If the OMU operating system fails to be installed, contact Huawei for technical support.
For details, see Contact Huawei Customer Service Center.
Issue 08 (2012-02-27)

90
BSC6900 GSM
If you use the USB storage device to restore the OMU operating system, check whether you
should implement the following operations:
l
After the restoring, the setting on the original operating system for disabling root user
remote login will be ineffective. You need to reset on the restored operating system by
referring to 7.1 Disabling root user remote login.
Only when BSC6900 is configured with the GBFD-511701 Radio Measurement Data
Interface for Navigation feature and the BSC local IP address is used for communication
between the OMU and VNP, you need to reconfigure the BSC local IP address, VLAN IDs
for communication between the OMU and VNP, and VLAN IDs for communication
between the OMU and EMS/LMT based on "OMU Ethernet Adapter Team IP Address
Installation Information." For details, see Configuring Radio Measurement Data Interface
for Navigation in GBSS Feature Activation Guide.
4.2.4 Optional: Installing the OMU Applications

If the OMU applications are not installed in the process of preparing the USB installation CDROM, then the OMU applications must be installed manually after the OMU operating system
is installed.
Context
l
In the case of reinstalling the OMU applications, you need to re-import the OMU
configuration data. Therefore, you need to back up the OMU data before reinstalling the
OMU applications and recover the OMU data after the installation. For details, see Backing
Up the System Data and Restoring the System Data.
In the case of 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 need not be backed
up.
NOTE
This section takes the version installation package named V900R013C00 as an example to illustrate how to
install the OMU applications.
Obtaining the 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
Records of OMU Software Installation Information.
l Password of the operating system administrator
l Fixed IP address of the external network, virtual IP address of the external network, and
debugging IP address of the OMU.
----End
Logging In to the OMU

You can perform OM after logging on to the OMU by running the SSH (Secure Shell) terminal.
For example, you can log on through the PuTTY software.
Issue 08 (2012-02-27)

91
BSC6900 GSM
Prerequisites
The computer to be used to log in to the OMU is properly connected.
Procedure
Step 1 Run the SSH terminal, PuTTY, for example, on the computer, and then enter the IP address of
the OMU.
NOTE
l Before starting the OMU applications, you should enter the fixed IP address of the external network.
l After the OMU applications are started, you should enter the fixed or virtual IP address of the external
network. The latter is preferred.
l In the case of local commissioning, you should enter the debugging IP address of the OMU.
l If the OMU cannot be connected by using either the external fixed IP address or external virtual IP
address, the debugging Ethernet port of the OMU must be debugged. You should enter the debugging
IP address of the OMU.
l You are advised to log in to the OMU using the fixed external IP address, virtual externalIP
address, or debugging IP address in a preference sequence.
Step 2 Log in to the OMU as user root.

NOTE
l If the login fails, check whether the Disabling root user remote login function is enabled. If so, log in to
the OMU as a non-root user. For details, see 7.1 Disabling root user remote login.
l The user name of the root user account is root and the password is 11111111 by default.
l If you cannot log in to the OMU as a root user by entering the password 11111111, try huawei.
----End
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
You have obtained the OMU application installation package including the patch
installation package by logging in to http://support.huawei.com/support/ and choosing
Software Center > Version Software > Wireless Product Line > Single RAN >
MBSC > BSC6900.
The psftp has been obtained. For details about the psftp, see 4.4.1 psftp Software.
The OMU application installation package must be uploaded to the \mbsc\upgrade

directory of the OMU.
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 package on OMU is "\mbsc\upgrade\V900R013C00."
If patches are also to be installed, before you install the OMU application, you must replace
the original patch files in the patch folder in the OMU application installation package with
Context
Issue 08 (2012-02-27)

92
BSC6900 GSM
the patch installation package (for example, the V900R01XC0XSPCXXX folder) saved
on the local computer.
l
During the uploading process, if the root user cannot log in to the OMU, check with the
equipment room operators whether the 7.1 Disabling root user remote login function has
been enabled on the BSC6900. If so, you must log in to the OMU as a non-root user, and
then continue with the uploading task.
NOTE
As an example, this task uploads the V900R013C00 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 drive D.
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 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 V900R013C00 command to upload the OMU application installation
package to the OMU.
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 an file, release the file.
8.
l
After the uploading is complete, enter the exit command to exist the psftp software.
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 non-root user. For details, see Logging In to the OMU.
2.
Enter the su command and press Enter. You are prompted to enter the password.
3.
Enter the root user password and press Enter to switch the user account from a nonroot to root user.
4.
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
xxx in the command is the name of a non-root user.
Issue 08 (2012-02-27)

93
BSC6900 GSM
5.
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.
6.
Enter the exit command and press Enter to log out of PuTTY.
7.
Decompress the BSC6900 version installation package to the local drive D.
8.
Log in to the OMU as a non-root user by using the psftp software.
9.
Enter the lcd D:\ command and press Enter to log in to the local directory for version
files.
10. Enter the cd /home/omcuser command and press Enter to go to the user file directory
of the non-root user omcuser.
11. Enter the put -r V900R013C00 command and press Enter to upload the OMU
application installation package to the OMU.
12. After the uploading is complete, enter the exit command and press Enter to exit the
psftp software.
13. Repeat Step 1 to Step 3 to log in to the OMU as a non-root user and switch the account
from non-root user to root user.
14. Enter the ls /mbsc/upgrade command and press Enter to query whether there is an
installation directory on the OMU.
If the /mbsc/upgrade directory does not exist, go to Step 15.
If the /mbsc/upgrade directory exists, go to Step 16.
15. Enter the mkdir /mbsc/upgrade command and press Enter to create an installation
directory on the OMU.
NOTE
Run the commands mkdir /mbsc and mkdir /mbsc/upgrade in sequence to create the /mbsc/
upgrade directory hierarchically.
16. 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.
17. Enter the exit command and press Enter to log out of 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 OMUa/OMUc boards, you need to install the OMU
applications in the active workspace of each individual board.
Prerequisites
You have logged in to the OMU by referring to Obtaining the Information About OMU
Software Installation.
Issue 08 (2012-02-27)

94
BSC6900 GSM
Context
Run a command to install the install_bam program contained in the BSC6900 version installation
package. You need to enter the related parameters during the process.
If an OMU application is pre-installed on the OMU, uninstall it and then install the OMU
application. To check whether an OMU application has been pre-installed on the OMU, do as
follows:
1.
Log in to the OMU by using the fixed external IP address or the debugging IP address. For
details, seeLogging 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 there is an omud file, it indicates that an OMU application has been pre-installed on
the OMU. Then, uninstall the application. For details about how to uninstall the
application, see operation procedures in
l If there is no omud file, it indicates that no OMU application has been pre-installed on
the OMU. Then, continue with installation of the OMU application.
4.
Run the exit command to terminate the PuTTY software.
Procedure
Step 1 Log in to the OMU using the external fixed IP address or debugging IP address by referring to
Logging In to the OMU, and then go 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 Type the ./install_bam.sh command and press Enter. The system prompts you to enter the
product mode, as shown in the following figure.
[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 installed automatically, because they
can be installed only if the check passes.
Step 4 Type the product running mode and press Enter. The system prompts you to enter the office
name, as shown in the following figure.
# 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 Type the office name and press Enter. The system prompts you to enter the language, as shown
in the following figure.
Issue 08 (2012-02-27)

95
BSC6900 GSM
# The OMU language version. eg: eng/chs

Please input a valid version :
Step 6 Type the language and press Enter. The system prompts you to enter the admin password, as
shown in the following figure.
# The "admin" user's password of OMU service.
# The password must range from 6 to 32 characters and consist of only letters and
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 Type the admin password and press Enter. The system prompts you to enter the FTP password,
as shown in the following figure.
# The ftp user's password of OMU service
# The password must range from 6 to 32(characters) and consist of only letters and
figures.
# Do not forget the password.
# 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 Type the FTP password and press Enter. The system prompts you to enter the external virtual
IP address, as shown in the following figure.
# 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 Type the external virtual IP address and press Enter. The system prompts you to enter the OMU
system type, as shown in the following figure.
# 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 Type the OMU system type based on the field configuration and press Enter. Table 4-6 describes
the OMU installation types.
Table 4-6 Description
Issue 08 (2012-02-27)
Parameter
Description
Single
When the BSC6900 is configured with one

OMU board, install the OMU applications on
the board in single-OMU mode.

96
BSC6900 GSM
Parameter
Description
Dual
When the BSC6900 is configured with two

OMU boards, install the OMU applications
on the boards in dual-OMU mode.
Step 11 The system asks you whether to continue with the installation, as shown in the following figure.
Please affirm input information. input Y to continue; input E to exit. ->
Step 12 Enter Y to install the OMU applications. When the message"Install OMU succeed!" is
displayed, the OMU applications are successfully installed.
Step 13 Record the information on the installation of the OMU applications in 4.5.1 Records of OMU
Software Installation Information.
----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-7 and Figure 4-8.
Directory Structure
l
Figure 4-7 shows the directory structure of the OMU applications when they are installed
only in the active OMU workspace for the first time.
If the OMU applications are installed on both the active workspace and the standby
workspace, the directory structure is shown in Figure 4-8. The structures of the
version_a and version_b folders are the same.
NOTE
l The version_a and version_b folders save active and standby OMU workspace files, respectively, or
in reverse order.
l You can 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-7 and Figure 4-8 show the directory structure of the OMU applications.
Issue 08 (2012-02-27)

97
BSC6900 GSM
Figure 4-7 Directory structure of OMU applications on the active workspace
Figure 4-8 Directory structure of OMU applications on the active and standby workspaces
CAUTION
To prevent critical impact on the BSC6900, do not delete any files in the installation directory
of the OMU applications.
Issue 08 (2012-02-27)

98
BSC6900 GSM
File Folders
Table 4-7 lists the file folders in the OMU application directory.
Table 4-7 File folders in the OMU application directory
Issue 08 (2012-02-27)
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/
btsinfo
Stores files that record basic information about the BTS
gchr
Stores basic information and logs about abnormal calls
gphr
Stores basic information about a subscriber, such as cell

index, CGI, and IMSI, and information about interfaces and
call messages during a call. The information is used to
analyze the abnormalities during PS service admission and
data transmission in the GSM network, which facilitates
fault location in a PS call.
pchr
Stores information about each call in the UMTS network,

including service admission and release, handover, and
signal quality. These information is used to analyze
network KPIs.
sysfault
Stores information about severe hardware and software

faults, such as system fault contents, resource leakage, and
equipment failure. These information is used for network
health check.
viptrace
Stores tracing files of VIP subscribers
common/fam/mr
Stores AMR measurement files
common/fam/pcu_file
Stores data files reported by the host
common/fam/pfm
Stores traffic statistics reported by an NE to the M2000
common/fam/smlc
Stores files about the location function

99
BSC6900 GSM
Issue 08 (2012-02-27)
File Folder
Description
common/fam/tc_file
Stores TC speech files 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
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/
data_backup/mml
Stores configuration data in MML format backed up by the

host
data_restore/db_data
Stores the configuration data downloaded from the M2000

in DB format for restoration.
data_restore/mml
Stores the configuration data downloaded from the M2000

in MML format for restoration.
version_a/ftp/bts_upgrade
Stores BTS upgrade files
version_a/ftp/cert
Stores the certificates for ftp security strategy
version_a/ftp/
COLLOGINFO
Stores log collection results
version_a/ftp/crashfile
Stores OMU breakdown logs and dump files generated

when OMU modules are faulty
version_a/ftp/DefaultMeas
Stores performance measurement task file in use
version_a/ftp/
DefaultMeasSync
Stores files about performance synchronization tasks
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

100
BSC6900 GSM
File Folder
Description
version_a/ftp/
ExportCMESyncView
Stores files about the "configure" process. These files are

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
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/ftp/trace
Stores files recording traced message
version_a/license
Stores the activated license files
version_a/log
Stores the operation logs of the OMU
version_a/security_file
Stores configuration file of the anti-virus 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
Issue 08 (2012-02-27)

101
BSC6900 GSM
4.3 Operating and Maintaining the OMU

commands.
4.3.1 Querying the Configuration of the OMU Ethernet Adapters

This section describes how to query the configuration of OMU Ethernet adapters to obtain the
information about the mapping between physical OMU Ethernet adapters and logical Ethernet
adapters.
Prerequisites
The OMU applications are installed. For details, see Installing the OMU Applications in the
Active Workspace.
Procedure
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 figure shows the factory
settings of the Ethernet adapters of the OMUa board.
eth0
eth1
eth2
eth3
eth4
eth5
06,0,0
06,0,1
04,4,0
04,4,1
08,4,0
08,4,1
ETH4-SCU7
ETH5-SCU6
ETH2
ETH3-UPDATE
ETH0
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 figure shows the factory
settings of the Ethernet adapters of the OMUc board.
eth0
eth1
eth2
eth3
eth4
eth5
eth6
Issue 08 (2012-02-27)
02,0,0
01,0,0
07,0,0
05,0,0
06,0,0
03,0,0
03,0,1
F_ETH0
F_ETH1
F_DBG
B_UPDATE0
B_UPDATE1
B_ETH0
B_ETH1

102
BSC6900 GSM
NOTE
The details about the three columns in the figure for the configuration of OMU Ethernet adapters are as
follows:
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 Network Configuration of the OMU Ethernet

Adapters
This section describes how to query the network configuration such as the IP addresses, broadcast
IP addresses, and subnet masks of the OMU Ethernet adapters.
Prerequisites
Active Workspace.
Procedure
Step 2 Optional: To query the external fixed IP address, broadcast IP address, and mask of the OMUa
board, type the ifconfig bond1 command and press Enter. The following figure shows the
network configuration of the OMUa Ethernet adapters.
bond1
Link encap:Ethernet HWaddr 00:18:82:5B:0C:26

inet addr:10.161.21.203 Bcast:10.161.21.255 Mask:255.255.254.0
inet6 addr: fe80::218:82ff:fe5b:c26/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:439779 errors:0 dropped:0 overruns:0 frame:0
TX packets:130258 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:57319799 (54.6 Mb) TX bytes:13458423 (12.8 Mb)
NOTE
To query the OMU IP addresses and subnet masks, do as follows:

l Run the ifconfig bond1:0 command to query the external virtual IP address, broadcast IP address, and mask.
l Run the ifconfig vlan1 command to query the internal fixed IP address, broadcast IP address, and mask.
l Run the ifconfig vlan1:0 command to query the internal virtual IP address, broadcast IP address, and mask.
l Run the ifconfig bond2 command to query the debugging IP address, broadcast IP address, and mask.
l Run the ifconfig bond3 command to query the IP address of the backup channel between the active OMUa
board and the standby OMUa board, broadcast IP address, and mask.
Step 3 Optional: To query the external fixed IP address, broadcast IP address, and mask of the OMUc
board, type the ifconfig bond1 command and press Enter. The following figure shows the
network configuration of the OMUc Ethernet adapters.
bond1
Issue 08 (2012-02-27)
Link encap:Ethernet
HWaddr 00:18:82:9F:14:11

103
BSC6900 GSM

inet6 addr: fe80::218:82ff:fe9f:1411/64 Scope:Link
NOTE
To query the OMU IP addresses and subnet masks, do as follows:

l Run the ifconfig bond1:0 command to query the external virtual IP address, broadcast IP address, and mask.
l Run the ifconfig vlan1 command to query the internal fixed IP address, broadcast IP address, and mask.
l Run the ifconfig vlan1:0 command to query the internal virtual IP address, broadcast IP address, and mask.
l Run the ifconfig bond2 command to query the debugging IP address, broadcast IP address, and mask.
l Enter the ifconfig bond3 command to query the backup channel IP address, broadcast IP address, and subnet
mask of the Ethernet adapter on the OMUc board for communication with the peer OMUc board.
l Enter the ifconfig bond4 command to query the backup channel IP address, broadcast IP address, and subnet
mask of the Ethernet adapter on the OMUc board for communication with the OMUa board.
----End
4.3.3 Checking the Version of the Operating System

This section describes how to check that the version of the operating system on the OMUa board
is correct.
Prerequisites
You have logged in to the LMT by referring to 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.4 Changing the IP Address of the OMU Ethernet Adapter Team

The IP address of the OMU Ethernet adapter team is set before delivery. This IP address,
therefore, is not obtained from the network and may be inconsistent with the actual network
planning. You can change the IP address of the OMU Ethernet adapter team according to the
actual requirements.
Prerequisites
Issue 08 (2012-02-27)

104
BSC6900 GSM
Context
CAUTION
l
Improperly changing the IP addresses of the Ethernet adapter team leads to network failure.
Therefore, you must follow the instructions.
In dual-OMU mode, if you change the network segment where the external fixed IP address
is located, ensure that the modification is applied to both the active OMU and the standby
OMU. Note that the new IP address of the active OMU is in the same network segment as
that of the standby OMU.
In dual-OMU mode, if you change the external virtual IP address, ensure that the external
virtual IP address of the active OMU is the same as that of the standby OMU.
Change the external fixed IP address when the OMU applications are operating normally.
Procedure
1.
Stop the omud by referring to Stopping the omud.
2.
Change the external fixed IP address by referring to Changing IP Addresses and

Masks of the OMU Ethernet Adapters, and then record the new virtual IP address
in 4.5.1 Records of OMU Software Installation Information.
3.
Change the virtual IP address of the external network by referring to Changing IP

Addresses and Masks of the OMU Ethernet Adapters, and then record the new
virtual IP address in 4.5.1 Records of OMU Software Installation Information.
4.
Start the omud by referring to Starting the omud.
Replace the OMUa/OMUc board and reconfigure the IP addresses of the internal and
external Ethernet adapter team.
1.
Replace the OMUa/OMUc board by referring to Replacing an OMU Board.

NOTE
Replace the OMUa/OMUc board and reconfigure the IP address of the internal Ethernet adapter
team. To avoid conflicts among the IP addresses of the internal Ethernet adapter team, the
external Ethernet adapter team, and the backup channel of the active and standby BAMs, ensure
that you know the active/standby state of the OMUa/OMUc board to be replaced and of the
new OMUa/OMUc board.
2.
Change the IP addresses of the external Ethernet adapter team, internal Ethernet
adapter team, and backup channel by referring to Changing IP Addresses and Masks
of the OMU Ethernet Adapters, and then record the new IP addresses in 4.5.1
Records of OMU Software Installation Information.
----End
4.3.5 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.
Issue 08 (2012-02-27)

105
BSC6900 GSM
Procedure
Step 2 Run the passwd root command (using user root as an example). A message is displayed,
prompting you to enter the password, as shown in the following figure.
Changing password for root.
New password:
Step 3 Enter a password and press Enter. The message Re-enter new 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.
Step 5 Record the new password in the 4.5.1 Records of OMU Software Installation Information.
----End
4.3.6 Setting RAID 1 on the OMU Hard Disks

This section describes how to set RAID 1 on the OMU hard disks to ensure that the data on the
target OMU hard disk is synchronized with that on the source OMU hard disk.
Prerequisites
l
The OMU is started normally.
The OMU serial cable is obtained. For details about the OMU serial cable, see OMU serial
port cable.
The source hard disk and target hard disk 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 target hard disk with that on the
source hard disk, thus improving data security.
l
The source hard disk saves the backup data and files.
The target hard disk mirrors the source hard disk.

NOTE
This task cannot be performed on an OMUc board because it is configured with one hard disk.
Procedure
Step 1 Connect the PC to the serial port of the OMU through the OMU serial 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. A dialog box is displayed, as shown in Figure 4-9.
Issue 08 (2012-02-27)

106
BSC6900 GSM
Figure 4-9 Connection description
Step 3 Enter the connection name and click OK. A dialog box is displayed, as shown in Figure 4-10.
Figure 4-10 Confirming the connection
Step 4 Check the connection port and click OK. A dialog box is displayed, as shown in Figure 4-11.
Issue 08 (2012-02-27)

107
BSC6900 GSM
Figure 4-11 Setting the attributes of the connection port
NOTE
The parameters of the connection port must be set as shown in Figure 4-11.
Step 5 Check that the parameters of the connection port are correct and click OK. A window is
displayed, as shown in Figure 4-12.
Issue 08 (2012-02-27)

108
BSC6900 GSM
Figure 4-12 Connection established
Step 6 Restart the OMU.

Option
Description
Suse Linux/Dopra Linux Operating

system
Log in to the target OMU by the PuTTY

software. Type the reboot command and press
Enter to restart the OMU. For details about the
PuTTY software, see 4.4.2 PuTTY Software.
Windows Server 2003 Operating system
1. Logging In to the OMU.

2. Choose Start > Close, Select Restart and
click OK.
Step 7 After the OMU is restarted, until the message "Press Ctrl-C to start LSI Logic
Configuration Utility" is displayed. Press Ctrl+C. Messages are displayed, as shown
in the following figure (an example).
Adapter PCI
Bus
SAS1064 05
PCI
Dev
01
PCI
Fnc
00
PCI
Slot
00
FW Revision
0.11.01-IR
Status
Boot
Order
Enabled 0
Step 8 Press Enter. Messages are displayed, as shown in the following figure (an example).
Issue 08 (2012-02-27)

109
BSC6900 GSM
Adapter
PCI Slot
PCI Address(Bus/Dev/Func)
MPT Firmware Revision
SAS Address
NVDATA Version
Status
Boot Order
Boot Support
SAS1064
00
05:01:00
0.11.01.00-IR
500E0FC1:23456775
25.09
Enabled
0
[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 normally.
l If Status is Resyncing, the RAID is synchronizing data.
NOTE
l If the RAID of the OMU is set for the first time, go to Step 13.
l If the RAID of the OMU is set for the second time, go to Step 9.
Step 9 Select RAID Properties and press Enter. Results are displayed, as shown in the following figure
(an example).
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
Num
Disk Spr Status
Fail
0 FUJITSU MAY2073rc
D109 [Yes] [No] Primary
--1 FUJITSU MAY2073rc
D109 [Yes] [No] Secondary ---
Size
(MB)
69618
69618
Step 10 Select Manage Array and press Enter. Results are displayed, as shown in the following figure
(an example).
Identifier
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. Results are displayed, as shown in the following figure
(an example).
Y
N
Delete array and exit to Adapter Properties

Abandon array detetion and exit this menu
Step 12 Select Y. Messages are displayed, as shown in the following figure (an example).
Adapter
PCI Slot
Issue 08 (2012-02-27)
SAS1064
00
05:01:00
0.11.01.00-IR

110
BSC6900 GSM
SAS Address
NVDATA Version
Status
Boot Order
Boot Support
500E0FC1:23456775
25.09
Enabled
0
[Enabled Bios & OS]
RAID Properties
SAS Topology
Step 13 Select RAID Properties and press Enter. Results are displayed, as shown in the following
figure.
Creat IM Volume
Create IME Volume
Create IS Volume
Create Integrated Mirror Array of 2

disks plus an optional hot spare,Data
on the primary disk may be migrated.
Create Integrated Mirrored Enhanced
Array of 3 to 8 disks including an
optional hot spare.
All DATA on array disks will be DELETED!
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. Results are displayed, as shown in the following
figure (an example).
Array Type:
Array Size(MB):
Num
0 FUJITSU MAY2073rc
1 FUJITSU MAY2073rc
IM
------RAID
Disk
D109 [No]
D109 [No]
Hot Drive
Spr Status
[No] -----[No] ------
Pred
Fail
-----
Size
(MB)
70003
70003
CAUTION
Use caution when selecting the source and target hard disks. Otherwise, the data on the source
hard disk may be lost.
Step 15 Set RAID Disk to No, move the cursor to the value of RAID Disk of the source hard disk, and
press Space. Results are displayed, as shown in the following figure.
M
D
- Keep existing data, migrate to an IM array.

Synchronization of disk will occur.
- 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
on the source disk.
l If you press D, the data on the source hard disk is deleted and a new RAID is created.
Step 16 Press M or D to return to the messages shown in Step 14.
The value of RAID Disk is Yes, and the value of Drive Status is Primary.
Step 17 Select the target hard disk and press Space. An alarm is generated, as shown in the following
figure.
WARNING! Data was found on the selected disk,this data will be lost when the array
Issue 08 (2012-02-27)

111
BSC6900 GSM
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 of RAID Disk is Yes, and the value of Drive Status is Secondary.
Step 19 Press C. Results are displayed, as shown in the following figure.
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 updated, as shown in
Step 12.
Step 21 Select RAID Properties shown in Step 12 and press Enter. Results are displayed, as shown in
the following figure (an example).
Array
Identifier
Type
Scan Order
Size(MB)
Status
1 of 1
1M
0
69618
2% Syncd
Manager Array
Num
0 FUJITSU MAY2073rc
1 FUJITSU MAY2073rc
RAID
Disk
D109 [Yes]
D109 [Yes]
Hot
Spr
[No]
[No]
Drive
Status
Primary
Secondary
Pred
Fail
-----
Size
(MB)
69618
69618
Step 22 Check that the RAID 1 is set correctly, and then press Esc repeatedly until messages are
prompted, as shown in the following figure.
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. Setting the RAID 1 on the
OMU hard disks is complete and the OMU is restarted.
----End
4.3.7 Maintaining the OMU Routinely

This section describes how to log in to the OMU remotely to regularly check and clean up the
OMU hard disk and transfer files from the OMU to the LMT PC 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
the available space of any partition on the OMU hard disk is equal to or more than 20%.
Issue 08 (2012-02-27)

112
BSC6900 GSM
Prerequisites
Procedure
Step 1 Run the DSP OMUSRV command 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 operations:
1.
Back up the files on the partition that needs to the saved to a hard disk by referring to
Transferring and Backing Up Files.
2.
3.
Run the cd target directory to go to the directory where the files to be deleted are saved.
4.
Run the rm file name or rm -rfolder name command to delete the unneeded files.
l If the available space of each directory is equal to or more than 20%, end this task.
----End
Transferring and Backing Up Files

This section describes how to transfer files between the local computer and the OMU through
the FTP protocol, which is an important method of saving files in the OM process.
Prerequisites
l
The firewall on the portable computer is disabled.
The user password for FTP is obtained. For details, see 4.5.1 Records of OMU Software
Installation Information.
The OMU applications are started.
Context
There are two methods of transferring the files on the OMU:
l
Using the function of file management on the LMT
Running commands
Table 4-8 describes the commands that are used for downloading files.
Table 4-8 Commands frequently used on the FTP
Issue 08 (2012-02-27)
Command
Description
Example
cd
Change directory
cd /mbsc/upgrade
dir
Query the structure of the

current directory
dir
get
Upload files from the OMU

to the local computer
get x (x indicates the file

name)

113
BSC6900 GSM
Command
Description
Example
put
Download files from the

local computer to the OMU
put x (x indicates the file

name)
NOTE
This task takes how to download the 123.xml file from the OMU to local disk D as an example.
Procedure
l
Download the files on the OMU by using the file management function on the LMT
1.
Start the file manager by referring to File Manager.
2.
Right-click the 123.xml file and choose Download.
Download the files on the OMU to local drive D by running commands

1.
On the local computer, 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 computer to the OMU. The
IP address indicates the IP address of the OMU.
4.
Enter the user name and password of the FTP. The connection between the local
computer and the OMU is established after the certification passes.
NOTE
The user name of the FTP is FtpUsr. The FTP password is set when the OMU applications are
installed. For details, see Records of the OMU Application Installation Information.
5.
Go to the directory where the file to be transferred is saved by referring to the command
listed in the preceding table.
6.
Transfer the file.
7.
Run the get 123.xml command.
Upload the 123.xml file from the OMU

to the local drive D.
Run the put 123.xml command.
Download the 123.xml file from the

local drive D to the OMU.
After the file transfer is complete, run the quit command to disconnect the FTP.
----End
Example
The following takes downloading the 123.xml file from local drive D to the /mbsc/bam/
version_a/bin/bam directory of the OMU as an example, as shown in the following figure.
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.
Issue 08 (2012-02-27)

114
BSC6900 GSM
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
D:\>
4.3.8 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 Operating Status of the OMU

This section describes how to query the operating status of the OMU subsystem and the service
processes, and the status of the board.
Prerequisites
Procedure
l
Query the status of the OMU subsystem.

1.
Run the DSP OMU command. The operating status of the OMU subsystem is
displayed, including the OMU operating status, fixed IP address configuration, virtual
IP address configuration, data synchronization status, status of the internal/external
networks, and status of the backup channel.
Query the status of the service processes when the OMU is operational.
1.
Run the DSP OMUMODULE command. The names and status of the service
processes are displayed.
If the state of the service processes is Started, the OMU service processes are
normal.
If the state of the service processes is Stopped, the OMU service processes are
normal and not started.
If the state of the service processes is Exception, the OMU service processes are
abnormal. In dual-OMU mode, the self-healing switchover is triggered if the
abnormal state persists. In single-OMU mode, the OMU reports the alarm
ALM-20707 OMU Process Abort.
Query the status of the OMU.

1.
Run the DSP OMUSRV command. The information related to the OMU is displayed,
including the CPU usage, memory usage, total space of each logical disk, current free
space, and percentage of the free space of the OMUa board.
----End
Querying the Information About the OMU

This section describes how to query the working environment, hardware state, and version of
the OMU.
Issue 08 (2012-02-27)

115
BSC6900 GSM
Prerequisites
Context
When a fault occurs on the OMU, you can query the information about the OMU for fault
location.
Procedure
l
Query the working environment of the OMU.

1.
Run the DSP OMUENV command. The voltage and temperature of the CPU, hard
disk, and chips are displayed.
Query the hardware information about the OMU.

1.
Run the DSP OMUHW command. The subrack number, slot number, and operating
status of the hard disk, Ethernet adapters, Ethernet adapter teams, and RAID of the
OMU are displayed.
The hardware of the OMU is normal if the following conditions are met:
The state of the Primer harddisk and Standby harddisk is Online.
The state of the Raid is Normal, and the Raid rebulid scale is 0.
The ETH0 netcard or ETH1 netcard is Normal.
In dual-OMU mode, the Backup channel netcard is Normal; in single-OMU
mode, the Backup channel netcard does not have impact on the state of the OMU.
The Inner0 netcard or Inner1 netcard is Normal.
Inner netcard group and Extra netcard group are both Normal.
Query the version information about the OMU.

1.
Run the DSP OMUVER command. 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
Issue 08 (2012-02-27)

116
BSC6900 GSM
Querying the Status of the Data Synchronization Between the Active OMU and the
Standby OMU
This section describes how to query the status of the data synchronization between the active
OMU and the standby OMU.
Prerequisites
l
The OMUs work in active/standby mode.
Context
The data synchronization may be faulty due to network or database problems. The OMU will
rectify the fault automatically. In such situation, the Data-sync state is Data
synchronization fault.
Procedure
Step 1 Run the DSP OMU command on the active OMU or standby OMU. The status of the data
synchronization between the active OMU and the standby OMU is displayed.
If the data synchronization is normal, the alarm ALM-20704 OMU Data Synchronization Failure
is reported. Clear the alarm by referring to the suggestions.
CAUTION
When the Data-sync state is Data synchronization is successful, Data synchronization not
built due to version inconsistency or Data synchronization can not built due to OMU failure
switchover, the active and standby OMUs can be switched over.
----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
l
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.
Issue 08 (2012-02-27)

117
BSC6900 GSM
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, and run the CMP OMUDATA command five minutes later.
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 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, re-set the OMU time, and change the OMU time zone.
Prerequisites
l
You have obtained the time and 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.
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 and rollback.
Prerequisites
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 through the CMP OMUDATA and CMP
Issue 08 (2012-02-27)

118
BSC6900 GSM
OMUFILE commands to ensure that the data on the active OMU is totally synchronized
to the standby OMU.)
Context
Do not use this command in other cases.
Procedure
l
Switch 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.
Switch 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.
2.
3.
the host data.
----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 software/hardware upgrade or fault rectification. By
performing this task, the OMU services are not interrupted.
Prerequisites
l
The OMU works in active/standby mode and the active and standby OMUs work normally
for more than five 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 totally 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
synchronization is normal,
Go to Step 2.
The active and standby OMUs do not work properly or the data
synchronization is abnormal,
End this task.
Issue 08 (2012-02-27)

119
BSC6900 GSM
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, you can infer that 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.
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.
Resetting a specified OMU service process interrupts the service of the process for a while.
Reset the OMUa board/OMU applications
Procedure
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, you need to 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.
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
4.3.9 Managing the OMU Applications

This section describes how to manage the 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.
Issue 08 (2012-02-27)

120
BSC6900 GSM
Prerequisites
Procedure
Step 1 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 begins to provide normal services.
Procedure
Step 1 You have logged in to the OMU through the external fixed IP address by referring to Logging
In to the OMU.
Step 2 Type 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.
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 When the omud is stopped, the connection between the OMU and the peripheral devices is
terminated if you have logged in to the OMU through the external virtual IP address.
Procedure
In to the OMU.
Issue 08 (2012-02-27)

121
BSC6900 GSM
Step 2 Type the /etc/rc.d/omud stop command and press Enter to stop the omud.
----End

This section describes how to uninstall the OMU applications when they are not installed
properly.
Prerequisites
l
The OMU applications are installed. For details, see Installing the OMU Applications in
the Active Workspace.
The system data is backed up. For details, see Backing Up the System Data.
If both the active and standby workspaces of the OMU are installed with OMU applications,
uninstall the OMU applications on the standby workspace before uninstalling them on the
active workspace.
When the BSC6900 is configured with active and standby OMUs, uninstall the OMU
applications on both the active and standby OMUs.
If there is only the active workspace on the OMU, the system will prompt you to uninstall
the OMU applications on only the active workspace.
Context
NOTE
l Uninstalling the OMU applications from an OMU will cause all the data in the OMU to be lost. It is advised
to back up system data on the OMU before the unintalling by referring to Backing Up the System Data.
l If the BSC6900 is configured with the GBFD-511701 Radio Measurement Data Interface for
Navigation feature and the BSC local IP address is used to connect the OMU and the VNP, you must
deactivate the feature before the uninstalling by referring to Configuring Radio Measurement Data Interface
for Navigation in the GBSS Feature Actication Guide.
Procedure
Step 1 Log in to the standby OMU by using the fixed external IP address or the debugging IP address
by referring to Logging In to the OMU.
Step 2 Stop the omud by referring to Stopping the omud.
Step 3 Enter uninstall_bam under 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.
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.
Issue 08 (2012-02-27)

122
BSC6900 GSM
Option
Description
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 debugging IP address. Then
perform Step 2 through Step 7 again.
----End
4.3.10 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.
The OMU data needs to be backed up during routine maintenance.
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. When the OMU works in active/
standby mode, you should log in to the OMU to start the omu_backup_linker.
Prerequisites
Procedure
Step 1 Type 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 2 Type the ./omu_backup_linker command and press Enter to start the omu_backup_linker tool,
# 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,
please consult the administrator.
Please input a valid bkp_res_type :
----End
Issue 08 (2012-02-27)

123
BSC6900 GSM
Follow-up Procedure
l
Back up the system data through the omu_backup_linker by referring to Backing Up the
System Data.
Restore the system data through the omu_backup_linker by referring to Restoring the
System Data.
Backing Up the System Data

This section describes how to back up the BSC6900 configuration data, performance data, and
alarm data through MML commands or the omu_backup_restore_tool.
Prerequisites
l
Prerequisites for performing this task using MML commands are as follows:
Prerequisites for performing this task using the omu_backup_restore_tool are as follows:
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 the failure of system data backup before
capacity expansion, upgrade, or 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
and Backing Up Files.
Backing up the data by using the omu_backup_linker tool

1.
Start the omu_backup_linker tool by referring to Starting the omu_backup_linker

Tool.
2.
Type backup and press Enter after the message "Please input a valid
bkp_res_type:" is displayed.
3.
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 message "Backup OMU
database succeed!" is displayed, it indicates that the system data is
successfully backed up on the OMU hard disk.
----End
Issue 08 (2012-02-27)

124
BSC6900 GSM
Example
Back up the OMU data to /mbsc/bam through the omu_backup_restore_tool and the name the
file as omu.bak. An example is given, as shown in the following figure.
omd_test_name /mbsc/bam/common/services # ./omu_backup_linker
# Please select one option to backup or restore OMU database, if you don't know
it, please consult the administrator.
Please input a valid bkp_res_type : backup
# The backup file pathname.
# eg: d:/mbsc/bam/omu.bak, in windows;
# eg: /mbsc/bam/omu.bak, in linux.
Please input a valid backup file pathname : /mbsc/bam/omu.bak
Backup omu database
[100%]
Backup OMU database succeed!
omd_test_name /mbsc/bam/common/services #

This section describes how to restore the system data through the data backup file. The system
data consists of configuration data, performance data, and alarm data.
Prerequisites
l
Context
Restoring the BSC6900 system data will interrupt the services on the BSC6900 operation and
maintenance system. The data on the host will be inconsistent with the data on the OMU after
the system data is restored. As a result, the services will be greatly impacted. Therefore, you are
advised to restore the system data when the traffic volume is low.
NOTE
The OMU in dual-OMU mode is used as an example in this document. If an OMU is in single-OMU mode, skip
operations on the standby OMU.
Procedure
Step 1 Stop the omud on the active and standby OMUs by referring to Stopping the omud.
Step 2 Restore data in the original active OMU using the omu_backup_linker tool.
1.
Type the cd /mbsc/bam/common/services command and press Enter to go to the directory

2.
Enter the ./omu_backup_linker.exe command and press Enter to start the

omu_backup_linker tool.
3.
Type restore and press Enter after the message "Please input a valid
4.
Enter the directory and names of the backup files and press Enter after the message
Please input backup file pathname : is displayed. The system data starts
to be restored. A message is displayed to indicate whether the restore is successful. If the
Issue 08 (2012-02-27)

125
BSC6900 GSM
restore is successful, the message "Restore OMU database succeed!" is

displayed.
Step 3 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.
Step 4 Repeat Step 2 to restore data in the original active OMU using the omu_backup_linker tool.
Step 5 Stop the omud on the active and standby OMUs by referring to Starting the omud.
Step 6 Log in to the LMT by referring to Logging In to and Logging Out of the LMT. Run the REQ
CMCTRL.
Step 7 Check the consistency between the BSC6900 host data and the OMU data.
NOTE
After data restoration, check whether the BSC6900 host data is consistent with the OMU data. If not, load
the restored data to the BSC6900 host.
1.
Run the ACT CRC command to check whether the host data is consistent with the OMU
data.
l If the data is consistent, end this task.
l If the data is inconsistent, go to Step 7.2.
2.
Run the FMT DATA command to format the data in the OMU database so that the data
can be loaded into the host.
3.
If data inconsistency occurs in only one subrack, run the RST SUBRACK command to
reset this subrack. Before running the command, set Subrack No.. If data inconsistency
occurs in multiple subracks, run the RST BSC command to reset the BSC.
----End
Example
Restore the OMU data through the omu.bak file under /mbsc/bam. An example is given, as
shown in the following figure:
omd_test_name
Shutting down
omd_test_name
omd_test_name
~ # /etc/rc.d/omud stop
mbsc daemon..........
~ # cd /mbsc/bam/common/services
/mbsc/bam/common/services # ./omu_backup_linker

Please input a valid bkp_res_type : restore
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.11 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.
Issue 08 (2012-02-27)

126
BSC6900 GSM
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 then start the
Prerequisites
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 1 You have logged in to the OMU by referring to Logging In to the OMU through the external
fixed IP address.
Step 2 Type the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the directory
where the omutool program is saved.
Step 3 Run the ./omutool -h command. The parameter information on the omutool is displayed.
----End

This section describes how to set the working mode of the OMU through the omutool. The OMU
can work either in single-OMU mode or dual-OMU mode.
Prerequisites
l
You have logged in to the LMT, and queried the slot No. for the OMU by running the LST
BRD command.
You have logged in to the LMT, and queried whether the OMU is in single-OMU or dualOMU mode by running the DSP OMU command.
You have logged in to the LMT, and queried OMU version and workspace information by
running the LST OMUAREA command.
You have logged in to the LMT and queried OMU service mode by running the LST
MBSCMODE command.
If the working mode is changed from single-OMU mode to dual-OMU mode, apply the
settings to both the active and standby OMUs. If the working mode is changed from dualOMU mode to single-OMU mode, apply the settings to only the working OMU.
Context
Issue 08 (2012-02-27)

127
BSC6900 GSM
If the working mode of the OMU is changed from single-OMU mode to dual-OMU
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 a active/standby relation.
If the working mode of the OMU is changed from dual-OMU mode to single-OMU
mode, you should run the DSP OMU command to ensure that the Data-sync state is Data
Switch the OMU from the single-OMU mode to dual-OMU mode (OMU applications are
not installed on the OMU to be added).
Procedure
1.
Insert an OMUa or OMUc board into the standby slot by referring to Installing the
OMUa Boards or Installing the OMUc Boards.
2.
Connect the PC to the debugging Ethernet port of the OMU, log in to the standby
OMU through the debugging IP address, upload the OMU application installation
package to the stanbdy OMU, and then install the OMU applications on the active
workspace of the standby OMU. For instructions to the operations, see Logging In
to the OMU, Uploading the OMU Application Installation Package to the
OMU, and Installing the OMU Applications in the Active Workspace.
NOTE
You must select dualmode in the process of installing the OMU applications.
3.
Change the IP addresses and masks of the OMU Ethernet adapters by referring to
Changing IP Addresses and Masks of the OMU Ethernet Adapters to ensure that
the internal fixed IP addresses, external fixed IP addresses, backup channel IP address
of the active and standby OMUs comply with the planning principle for the IP
addresses and do not conflict with each other.
4.
Stop the omud on the original working OMU by referring to Stopping the omud.
5.
Start the omutool on the original working OMU by referring to Starting the
omutool.
6.
Run the ./omutool dualmode dual command on the original working OMU to set the
working mode of the OMU to active/standby mode.
7.
Start the omud on the original working OMU by referring to Starting the omud.
8.
After the original working OMU is started for five minutes, start the omu on the
standby OMU by referring to Starting the omud.
WARNING
You should start the standby OMU five minutes after the active OMU is started to
avoid the problem that the two OMUs compete for active state. As a result, data loss
can be avoided.
9.
Change the operating system password on the standby OMU to that of the original
working OMU by referring to 4.3.5 Changing the Administrator Password of the
Operating System.
10. Run the ADD BRD command on the LMT to add an OMU.
Issue 08 (2012-02-27)

128
BSC6900 GSM
11. Run the DSP OMU on the LMT and check whether the value for Data-sync state is
Data synchronization is successful.
12. Connect an Ethernet cable to the Ethernet port on the added OMU by referring to the
cable connection of the original working OMU.
l
installed on the OMU to be added.).
1.
Connect the PC to the debugging Ethernet port of the OMU, log in to the original
working OMU, and then stop the omud on the original working OMU. For instruction
to log in to the OMU and stop the omud, see Logging In to the OMU and Stopping
the omud.
2.
omutool.
3.
4.
5.
Five minutes after the orginal OMU is started, insert an OMUa or OMUc board to the
standby slot by referring to Installing the OMUa Boards or Installing the OMUc
Boards.
WARNING
can be avoided.
6.
Set the working mode of the standby OMU to dual-OMU mode by performing Step
1 to Step 3.
7.
8.
Start the omud on the standby OMU by referring to Starting the omud.
9.
Operating System.
l
Issue 08 (2012-02-27)
Change the working mode of the OMU from dual-OMU mode to single-OMU mode
1.
Run the RMV BRD command on the LMT to remove an OMU.
2.
Log in to the active and standby OMUs through the external fixed IP address by
referring to Logging In to the OMU, and then stop the omud on the active and standby
OMUs by referring to Stopping the omud.
129
BSC6900 GSM
3.
Run the poweroff command on the OMU which is to be removed to power off the
OMU.
4.
Remove the OMU to be removed by referring to Scenario: Old and New OMU Boards
Running the Same OS.
5.
Start the omutool on the working OMU by referring to Starting the omutool.
6.
Run the ./omutool dualmode single command on the working OMU to set the
working mode of the OMU to single mode.
7.
Start the omud on the working OMU by referring to Starting the omud.
----End
Changing IP Addresses and Masks of the OMU Ethernet Adapters

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 change the IP addresses and
subnet masks of the Ethernet adapters of the standby OMU and then of the active OMU.
NOTE
This task describes how to change all the IP addresses and subnet masks of the OMU. You can perform steps
following the planning of the IP addresses on site.
For details about the Ethernet adapter binding relation, see 3.1 OMU Ethernet Adapter
Configuration.
Procedure
Step 3 Type 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 The command for querying the OMU IP address and subnet mask is ./omutool dispipinfo.
For example, enter the following command and press Enter to delete the fixed external IP
address:
./omutool dispipinfo
Step 5 The ./omutool innercard IP address command is used to change the fixed internal IP address.
address:
Step 6 The ./omutool innervip IP address command is used to change the virtual internal IP address.
address:
Issue 08 (2012-02-27)

130
BSC6900 GSM
NOTE
l The network segments of the fixed and virtual internal IP addresses must be the same. 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 are changing 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
network segments on which the internal fixed IP address and internal virtual IP address are located.
2. Remove the SCUa board from the MPS and reinstall it in the MPS. Then, reset the MPS to validate the
new fixed and virtual internal IP addresses.
l After the two steps are performed, the OMU can communicate with the BSC6900 host normally.
Step 7 The ./omutool extercard IP address mask (gateway) command is used to change the fixed
external IP address and mask.
address:
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.
Step 8 The ./omutool extervip IP address subnet mask (gateway) command is used to change the virtual
external IP address and subnet mask.
address:
NOTE
l After the external virtual IP address and mask are changed, run the RMV EMSIP command and then the
ADD EMSIP command to update the external virtual IP address and mask that are recorded in the OMU
database.
l The network segments of the fixed and virtual external IP addresses must be the same. If the network segment
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 connection between the OMU and peripheral equipment.
Step 9 The ./omutool gateway gateway IP address is used to change the IP address of the gateway.
address:
./omutool gateway 10.161.10.1
Issue 08 (2012-02-27)

131
BSC6900 GSM
NOTE
You can change the fixed or virtual external IP address simutaneously 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
and gateway IP address simultaneously
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

active and standby OMUs on the
Ethernet adapter ETH3-UPDATE of
the OMUa board
./omutool backupcard IP address.

For example, enter the following command and
press Enter to delete the fixed external IP address:
./omutool backupcard_for_omuc IP address.

Ethernet adapter B_UPDATE0 of the
OMUc board
./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 debugging IP address.
address:
NOTE
l After you change the backup channel IP address and debugging 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 Planning of the OMU IP Addresses. 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 Records of OMU Software Installation Information.
Step 12 The ./omutool delextercard command is used to delete the fixed external IP address.
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
fixed external IP address.
Issue 08 (2012-02-27)

132
BSC6900 GSM
Step 13 For how to configure the BSC local IP address, see Configuring Radio Measurement Data
Interface for Navigation.
NOTE
The BSC local IP address is for communication between the OMU and VNP, for details, see 8.1 Scenario of
Connecting the OMU and VNP.
----End

This section describes how to change the admin, root, and account db_user passwords by using
the omutool, and how to change the FtpUsr password by using the MML.
Context
l
Admin is the account for the administrator to log in to the LMT.
The du_user and root are the account used by the OMU applications to access the OMU
database.
FtpUsr is the account for uploading and downloading files to and from the OMU.
Procedure
l
Issue 08 (2012-02-27)
1.
Log in to the target OMU by referring to Logging In to the OMU.
2.
Type the /etc/rc.d/omud stop command and press Enter to stop the omud..
3.
Type the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the

directory where the omutool program is saved..
4.
Run the ./omutool adminpwd command to change the admin password.
5.
Type the /etc/rc.d/omud start command and press Enter to start the omud..
Changing the root password

1.
2.
3.

4.
Run the ./omutool dbrootpwd command to change the root password.
5.
Changing the password of the db_user user

1.
Log in to the target OMU.
2.
3.

4.
Run the ./omutool dbpwd command to change the password of the db_user user.
5.
Changing the password of the FtpUsr user

133
BSC6900 GSM
1.
Log in to the LMT by referring to Logging In to and Logging Out of the LMT in the
2.
Run the MML command MOD FTPPWD to change the password of the FtpUsr user.
----End
Example
The following is an example for the operation of changing the admin password:
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 is an example for the operation of changing the root password:
Dopra_136 /mbsc/bam/version_a/bin/bam # ./omutool dbrootpwd
Successfully set the root's password of the database!
The following is an example for the operation of changing the db_user user password:
Dopra_136 /mbsc/bam/version_a/bin/bam # ./omutool dbpwd
Successfully set the db_user's password of the database!
Changing the OMU Name

This section describes how to change the OMU name through omutool.
Prerequisites
l
You have started the omutool by referring to Starting the omutool.
Context
The OMU name and IP addresses have been planned by the customer. You need to change the
OMU name and IP addresses through the omutool after you have installed the OMU applications.
For how to change the OMU IP addresses, see Changing IP Addresses and Masks of the OMU
Ethernet Adapters.
Procedure
Step 2 Run the ./omutool hostname OMU name command to change the OMU name.
For example, to change the OMU name to omu_123, type the ./omutool hostname omu_123
command and press Enter.
Step 3 Start the omud by referring to Starting the omud to validate the new name.
----End
Issue 08 (2012-02-27)

134
BSC6900 GSM
Follow-up Procedure
1.
Log in the LMT.
2.
Run the DSP OMU command to query the new name.

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.
The target slots for OMUs are idle and can hold OMUs. Such slots refer to OMUa/
OMUb Board or OMUc Board.
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.
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

Linux operating system is used
1. Log in to the active and standby OMUs

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

the OMU.
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.
Issue 08 (2012-02-27)

135
BSC6900 GSM
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.
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 OM 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.
Prerequisites
l
The PC is connected to the Internet.
The OMUa board is installed with an operating system.
The psftp software can be used to upload files to the OMU hard disk.
The psftp software can also be used to download files from the OMU hard disk to a local
computer.
Context
Table 4-9 lists the commands frequently used on the psftp software.
Issue 08 (2012-02-27)

136
BSC6900 GSM
Table 4-9 Commands frequently used on the psftp software

Command
Description
Example
cd
Change the OMU directory cd /mbsc/upgrade
ls

current directory
ls
lcd
Go to the local folder
lcd D:\BSC6900V900R013C00
\Software\setup\linux
get
Transfer files from the

OMU to the local computer
To transfer a file, run the get

V900R013C00 command.
To transfer a folder, run the get -r
put
Transfer files from the local

computer to the OMU
To transfer a file, run the put

To transfer a folder, run the put -r
mkdir
Create a directory on the

OMU
mkdir /mbsc/upgrade
rmdir
Remove a directory from

the OMU
rmdir /mbsc/upgrade
Procedure
Step 1 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 files.
Step 2 Double-click psftp.exe. A window is displayed, as shown in Figure 4-13.
Issue 08 (2012-02-27)

137
BSC6900 GSM
Figure 4-13 Logging in to the OMU through the psftp software
Step 3 Type the open IP address and press Enter (using 10.161.21.203 as an example).
Step 4 Log in to the OMU as a non-root or root user. The following information is displayed. (The root
user login is used as an example.)
psftp: no hostname specified; use "open host.name" to connect
psftp> open 10.161.21.203
login as: root
You are trying to access a restricted zone. Only Authorized Users allowed.
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.
An operating system has been installed on the OMU board.
Context
PuTTY is a Telnet client software that supports multiple network protocols, including SSH and
Telnet. PuTTY can be used for remotely logging in to the Dopra Linux operating system.
Issue 08 (2012-02-27)

138
BSC6900 GSM
Procedure
Step 1 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. A dialog box PuTTY Configuration is displayed, as shown in Figure
4-14.
Figure 4-14 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.
The IP address is determined based on the following rules:
Issue 08 (2012-02-27)
If...
Then...
The PC is connected to ETH2 on the OMU

board panel through an Ethernet cable,
The IP address is the debugging IP address of

the OMU board.
The PC is connected to ETH0 or ETH1 on the

OMU board panel through a network device,
The IP address is the fixed external IP address

or virtual external IP address of the OMU.

139
BSC6900 GSM
Step 4 Click Open. A window is displayed, as shown in Figure 4-15.

Figure 4-15 Logging in to the OMUa board through PuTTY software
Step 5 Log in to the OMU as a non-root or root user.

----End

4.5.1 Records of OMU Software Installation Information

During OMU installation, the software records information regarding the parameter
configurations.
Record Sheet of OMU Operating System Installation Information

Item
Setting
Installer
Computer name (active

OMU)
Administrator password
(active OMU)
Issue 08 (2012-02-27)

140
BSC6900 GSM
Item
Setting
Installer
Computer name (standby

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

Item
Setting
Installer
Internal IP address (subnet

mask) of the active OMU
External IP address (subnet
mask) of the active OMU
Internal IP address (subnet
mask) of the standby OMU
External IP address (subnet
mask) of the standby OMU
Backup channel IP address
(subnet mask) of the active
OMU
Backup channel IP address
(subnet mask) of the standby
OMU
Debugging IP address (mask)
of the active OMU
Debugging IP address
(subnet mask) of the standby
OMU
BSC local IP address (subnet
mask)
Virtual Local Area Network
(VLAN) ID for
communication with the
VNP
Virtual Local Area Network
(VLAN) ID for
communication with the
EMS/LMT
Issue 08 (2012-02-27)

141
BSC6900 GSM
Item
Setting
Installer
Default gateway
See OMU Ethernet Adapter Team IP Address Installation Information.
OMU Applications Installation Information

Item
Setting
Installer
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 Factory Settings of the OMU Software

This section provides a checklist for the factory settings of the OMU software. The checklist
records the installed OMU software and the software configurations before delivery.
Checklist for the Factory Settings of the OMUa Board Software

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
Installing the Dopra Linux operating

system
The administrator passwords of the active and

standby OMUs are both set to 11111111.
If you fail to log in to the OMU by entering
11111111, try huawei.
Installing the IPMI driver
Issue 08 (2012-02-27)

142
BSC6900 GSM
Item
Remarks
Teaming the internal Ethernet adapter

team
The default IP address of the internal Ethernet

adapter team of the active OMU is 80.168.3.50
(255.0.0.0).
adapter team of the standby OMU is 80.168.3.60
(255.0.0.0).
Teaming the external Ethernet adapter

team
The default IP address of the external Ethernet

adapter team of the active OMU is
172.121.139.201 (255.255.255.0).
adapter team of the standby OMU is
172.121.139.202 (255.255.255.0).
Configuring backup channel IP address

of the active and standby OMUs (for the
OMUa board)
The default backup channel IP addresses of the

active OMU is 192.168.3.50 (255.255.255.0).
Configuring debugging IP addresses of

the active and standby OMUs
The factory setting of the debugging IP addresses

of the active OMU is 192.168.6.50
(255.255.255.0).
The default backup channel IP addresses of the

standby OMU is 192.168.3.60 (255.255.255.0).

of the standby OMU is 192.168.6.60
(255.255.255.0).
Checklist for the Factory Settings of the OMUc Board Software

Item
Remarks
Setting OMU BIOS
Set the first boot device of the OMU to USB
Installing the Dopra Linux operating

system
The administrator passwords of the active and

standby OMUs are both set to 11111111.
Installing the IPMI driver
Teaming the internal Ethernet adapter

team

adapter team of the active OMU is 80.168.3.50
(255.0.0.0).
adapter team of the standby OMU is 80.168.3.60
(255.0.0.0).
Issue 08 (2012-02-27)

143
BSC6900 GSM
Item
Remarks
Teaming the external Ethernet adapter

team

adapter team of the active OMU is
172.121.139.201 (255.255.255.0).
adapter team of the standby OMU is
172.121.139.202 (255.255.255.0).
Configuring backup channel IP address

of the active and standby OMUs (for the
OMUc board)
l For the active OMU:

The default backup channel IP address of
B_UPDATE0 is 192.168.9.50
(255.255.255.0).
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).
Configuring debugging IP addresses of

the active and standby OMUs

of the active OMU is 192.168.6.50
(255.255.255.0).
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).

This section lists the mapping between the enabled ports on the OMU and the services provided
by the OMU applications.
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.
Issue 08 (2012-02-27)

144
BSC6900 GSM
Port No.
Issue 08 (2012-02-27)
Service Process
Description
Network
Protocol Type
TCP
UDP
20
FTP Server data
Port for host loading, and uploading

and downloading of software and
logs (in active mode)
21
FTP Server
control

logs
22
SSHD (operating
system service)
SSH port for remotely logging in to

the OMUa board
1024-6553
5
FTP Server data

logs (in passive mode)
80
Web LMT
Port for local maintenance on the

LMT
123
sntp
Port that synchronizes the time of the

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

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

between the LMT and an NE,
therefore achieving NE maintenance
6000
ems_gate
Port for maintenance
6001
ems_gate
Port for the alarm console
6006
ems_gate
6088
Remote upgrade
tool
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 Vendor Network Probe

(VNP)
8000
ems_gate
Port for maintenance (SSL

encryption)

145
BSC6900 GSM
Port No.
Service Process
Description
Network
Protocol Type
TCP
UDP
8001
ems_gate
Port for alarm console (SSL

encryption)
8006
ems_gate
Port for maintenance (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 alarm box (SSL encryption)
8200
ems_gate
Port for the VNP (SSL encryption)

(Reserved port, which is not
supported in the current version)
11775
monitor
Port for monitoring the external

network heartbeat between the
active/standby OMU and peripheral
equipment
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 (Creating BSC690).
Issue 08 (2012-02-27)

146
BSC6900 GSM
Scenario: Upgrade from the BSC6000 to the

BSC6900
About This Chapter

OMU when the BSC6000 is upgraded to the BSC6900.
Context
In this scenario, the physical entity to carry the OMU is the OMUb board. For the strategy for
replacing a faulty OMUb board, see Strategy on Replacing Legacy Components in an Upgrade
Scenario in the BSC6900 GSM Site Maintenance Guide.
The OMU software consists of the operating system and the OMU applications. It performs
operation and maintenance for the BSC6900. Figure 5-1 shows the OMU software structure.
Figure 5-1 OMU software structure
Operating system
The Suse Linux operating system is used.
OMU applications
Based on the operating system, the OMU applications provide all types of service progress.

This section describes the software installation policies after the BSC6000 is upgraded to the
BSC6900.
5.2 OMU Operation and Maintenance After the Upgrade
Issue 08 (2012-02-27)

147
BSC6900 GSM
commands.
5.3 Appendix: the SEK SetSuse Software
This section describes how to install, use, and uninstall the SEK SetSuse software.
5.4 Appendix: Antivirus Software
Before installing the antivirus software, refer to the Antivirus Software Installation Guide
provided by Huawei. Now the BSC6000 supports the antivirus software installation: TrendMicro
Control Manager (TMCM) + ServerProtect for Linux 2.5. After the BSC6000 is upgraded to the
BSC6900, the antivirus software installation is still supported.
5.5 Appendix: Ethernet Adapter Binding Tool
The Ethernet adapter binding tool is used only for the GBAM. It provides independent IP
configuration scripts, binds Ethernet adapters, and changes the IP address of the external
network.
Issue 08 (2012-02-27)

148
BSC6900 GSM

This section describes the software installation policies after the BSC6000 is upgraded to the
BSC6900.
Context
BSC6900 is Dopra Linux. After the BSC6000 is upgraded to the BSC6900, Suse Linux can be
retained or switched to Dopra Linux.
If Suse Linux needs to be retained,
Go to 5.1.3 Optional: Installing the OMU

Applications.
If Suse Linux needs to be reinstalled,
Go to 5.1.1 Re-Installing the Suse Linux

Operating System.
If Suse Linux needs to be switched to Dopra Go to 5.1.2 Switching the OMU Operating
Linux,
System.
5.1.1 Re-Installing the Suse Linux Operating System

This section describes how to reinstall the Suse Linux operating system.
Context
After the BSC6000 is upgraded to the BSC6900, re-install the Suse Linux operating system if
it is retained.
NOTE
The OMUc board supports only the Dopra Linux operating system. Therefore, the Suse Linux operating system
can only be reinstalled on the OMUa or OMUb board.
Procedure
----End
Preparations for Reinstalling the OMU Operating System

Before reinstalling the OMU operating system on site, you must install and configure the
EasyInstall software.
Installing the EasyInstall Software

NOTE
The EasyInstall installation source cannot be prepared on a PC running the Windows XP SP3 operating system.
1.
Issue 08 (2012-02-27)
Insert the EasyInstall software installation CD-ROM into the installation source server CD
drive and disable all the firewalls on the installation source server.
149
BSC6900 GSM
2.
Log in to the installation source server, double-click the autoinst.zip file in the \tools
\EasyInstall directory to decompress the software package to the installation source server.
The EasyInstall software is installed.
NOTE
l Unless otherwise specified, the software package is decompressed in the D:\autoinst path.
l An installation source server, physically a portable computer, saves installation programs such as
operating system.
Configuring the EasyInstall Software

1.
Go to the D:\autoinst directory, open the autoinst.conf file using a text processing program
and set parameters by changing the default values to recommended values, as shown in
Table 5-1.
Table 5-1 Configuration item
Item
Default Value
Recom
mended
Value
Description
SRC_PATH
D:\OMU\SRC
D:\OMU
\SRC
Save path of the installation source

file
THIRD_PA
RTY_PATH
D:\OMU\SRC
D:\OMU
\SRC
Path for saving the third-party

software
DHCPD_IN
TERFACE
Local area
connection 1
Ethernet port enabled with DHCPD

services on the installation source
server. The name of the Ethernet port
is consistent with the network
connection of the installation source
server. You can query the name of the
Ethernet port on the device panel or by
using commands.
IPADDR
192.168.0.1
IP address of the Ethernet port enabled

with DHCPD services on the
installation source server. This IP
address is set to the IP address of the
installation source server.
NETMASK
255.255.255.0
Subnet mask of the Ethernet port

enabled with DHCPD services on the
installation source server.
RANGE
192.168.0.128
192.168.0.254
Range of the IP addresses that can be

assigned to the client by the DHCPD
server
Creating 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.
Issue 08 (2012-02-27)

150
BSC6900 GSM
Context
An installation source server, physically a portable computer, saves programs such as operating
system.
The EasyInstall software is used to install the OMU operating system.
Procedure
Step 1 Go to the D:\autoinst\cdcopy path.
Step 2 Double-click ISM.EXE. A window is displayed, as shown in Figure 5-2.
Figure 5-2 Installation Source Manager window
Step 3 Select the installation source directory and click OK. The window is updated, as shown in Figure
5-3. You are advised to select the default installation source directory. If the default installation
source directory does not exist, create one.
Issue 08 (2012-02-27)

151
BSC6900 GSM
Figure 5-3 Installation Source Manager window
Step 4 Click New on the toolbar or choose Source > New. A dialog box is displayed, as shown in
Figure 5-4.
Figure 5-4 Creating operating system installation source 1
Issue 08 (2012-02-27)

152
BSC6900 GSM
Step 5 Select an installation source type and click Next.

If...
Then...
SuSE Linux Enterprise Server 9 Service

Pack 3 is selected,
A dialog box is displayed, as shown in Figure

5-5.
Figure 5-5 Creating operating system installation source 2
Step 6 Click Next. A dialog box is displayed, as shown in Figure 5-6.
Issue 08 (2012-02-27)

153
BSC6900 GSM
Figure 5-6 Creating operating system installation source (3)
Step 7 Insert CD1 into the CD drive on the portable comuputer. Click Next. A dialog box is displayed.
Step 8 Click Execute. Files in CD1 start to be copied, showing the progress.
Step 9 After all the files in CD1 are copied, a dialog box is displayed, prompting you to insert CD2.
Click OK. Follow the wizard to proceed to copy the remaining CDs.
Step 10 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 2.
----End
Installing the OMU Operating System by Using the EasyInstall Software

This section describes how to run the EasyInstall software on a portable computer to install an
Suse Linux Enterprise Server 9.0 SP3 operating system on the OMU.
Prerequisites
l
The OMU board is powered on and works normally.
The OMU is connected to the local PC through the debugging Ethernet port.
The MAC address of ETH2 of the OMU has been obtained.
The operating system installation source is created. For details, see Creating Operating
System Installation Source.
Issue 08 (2012-02-27)

154
BSC6900 GSM
CAUTION
Disable the firewalls of the installation source server before installing the Linux operating
system. The firewalls include sysgate and windows firewalls. You can run the smc -stop
command to disable the sysgate firewall.
Context
Check that the Ethernet cable is connected to ETH2. Otherwise, the Linux operating system will
fail to be installed.
You can obtain the MAC address of the ETH2 Ethernet adapter of the OMU in the following
three ways:
l
There is a short label on the upper right corner of the OMU board. The label specifies the
MAC addresses of the six Ethernet adapters of the OMU board, for example,
001822230568~6D(6). The third one is the MAC address of ETH2, for example,
00182223056A.
For BIOS V010 or later, the OMU board is started through the ETH2 Ethernet port by
default as the first boot device. When the ETH2 Ethernet port is connected, the OMU board
requests DHCP services after it is started. The MAC address of ETH2 is displayed on the
monitor through the VGA port.
Connect the OMU board to the LMT PC by using the serial cable of the OMU and choose
Start > Programs > Accessories > Communications > HyperTerminal on the LMT PC.
Restore the HyperTerminal to the default setting (9600-8-None-1-None), and then restart
the OMU board. The BIOS startup information is displayed on the HyperTerminal. After
the OMUb board sends the DHCP request, the MAC address of the ETH2 Ethernet adapter
can be obtained on the HyperTerminal.
Procedure
Step 1 In the directory autoinst\site, open the site file by using the text processing program. The
following information is displayed:
#MAC TYPE OS/FILE NAME SP/IP KEY PASSWD OWNER ORG
##00e0fc8f5e03 inst ws2k3std.enu test10 nosp F23FM-6928R-6XQ42-MBBRC-84QGW huawei
huawei Huawei\ Technologies\ Co.,\ Ltd.
#00E0FC8f5e04 win
NOTE
l # indicates shielding this statement. You need to delete # during installation.

l TYPE indicates the template name under the autoinst\template\pomu_mode directory. You can change
the template name as required. This section takes the template name bsc6000 as an example.
Step 2 Modify the third line displayed in Step 1: Delete #, change MAC to the MAC address of the
OMU that is to be installed with the Linux operating system, and change the value of TYPE to
bsc6000.
NOTE
You can modify several lines and install the Linux operating system on several OMU boards. The computer
name must be unique when installing the operating system on several OMU boards.
If you add the MAC address line for the standby OMU board, you can install the Linux operating system on the
OMU board in dual mode.
Issue 08 (2012-02-27)

155
BSC6900 GSM
Step 3 Press CTRL+S to save the settings.

Step 4 Create a folder under the autoinst\template\pomu_mode directory and name it bsc6000, which
is the template name set in <Step 2.
Step 5 Copy the files in the autoinst\template\pomu_mode\linux directory to the bsc6000 folder.
Step 6 Open the bsc6000 folder, and then double-click the config.ini file. The following information
is displayed.
<
<
<
<
<
deployitem >
ostype >sles9sp3< /ostype >
password >huawei< /password >
hostname >omu-test< /hostname >
/deployitem >
sles9sp3 is the name of the operating system to be installed. You can set the password and host
name. The password is used for logging in to the system as the user root after the operating
Step 7 Check whether the setsuse directory exists under the src directory. If not, create a folder and
name it setsuse under the src directory. The following files are under the src/setsuse directory:
(SEK SetSuse installation package).tar.gz, (SEK SetSuse Strategy file package).tar,
setsusesetup.sh, and third-party.ini. For details on where to obtain the files, see 5.3.1 Installing
the SEK SetSuse Software.
Step 8 Open the bsc6000 folder, and then double-click the third-party.ini file. The following
information is displayed.
;Example for third-party software to deploy.
;[third-party software title]
;Path=perl
;Command="msiexec /i ActivePerl-5.8.8.822-MSWin32-x86-280952.msi /quiet /passive"
;[xxxx] //the third-party software name or description.
;Path=xxx/xxx //software path under the third-party path.
;Command="xxxx /i xxx /s yyy" //want to run command or file.
Step 9 Add the information about setting the SEK SetSuse software to the third-party software
configuration file.
;Example for third-party software to deploy.
;[third-party software title]
;Path=perl
;Command="msiexec /i ActivePerl-5.8.8.822-MSWin32-x86-280952.msi /quiet /passive"
;[xxxx] //the third-party software name or description.
;Path=xxx/xxx //software path under the third-party path.
;Command="xxxx /i xxx /s yyy" //want to run command or file.
[Setsuse]
Path=setsuse
Command=setsusesetup.sh
NOTE
l ; indicates comment. If the SEK SetSuse software is not required, add ; in front of the added information.
l setsuse indicates the name of the directory where the SEK SetSuse software files are saved under the src
directory.
l setsusesetup.sh indicates the command script for installing the SEK SetSuse software.
Step 10 Double-click the deploy-ipconfig.ini file. The following information is displayed.

eth2;192.168.1.1;255.255.255.0;
The default IP address of ETH2 is 192.168.1.1. Set the IP address of ETH2.

Step 11 Run the checkout.bat program in the autoinst directory, and then check whether the ports to
be used by the EasyInstall software are occupied by other programs.
Issue 08 (2012-02-27)

156
BSC6900 GSM
NOTE
If the port status is Fail, the port is not used. If the port status is OK, the port is used. Quit other running
programs to release the port.
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.
You can log out the installation source server to quickly release all ports.
Step 12 On the installation source server, choose Start > Run. Enter cmd. The cmd prompt command
window is displayed.
Step 13 Run the cd /d D:\autoinst command to enter the autoinst folder where the installation directory
of the EasyInstall software is located. D: is the symbol of hard disk D. This step assumes that
the EasyInstall software is installed in the root directory of hard disk D.
Step 14 Enter install.bat, and then run the script until the command line automatically returns to the D:
\autoinst path.
NOTE
l Before running the script, ensure that ETH2 is in Link state, that the DHCP Ethernet port on the installation
source server and ETH2 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 a series of messages are displayed, modify the autoinst.conf file or system environment defined in the
autoinst.conf file as required, and then run the install.bat program until the execution is successful.
Step 15 Run the checkout.bat program. If the four Ethernet ports are in OK state, you can infer that all
the services are started properly.
Step 16 In the cmd prompt command window, run the config.bat command to finish all the
configurations related to the server.
NOTE
l Before running config.bat, ensure that the installation source files are copied; otherwise, the installation
fails.
l The config.bat file is in the autoinst folder.
l If the system prompts that a service fails to be started, run the config.bat program again till services are
configured successfully.
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 17 Turn outwards the two ejector levers of the OMU board until the OFFLINE LED is on steadily,
and then turn inwards the two ejector levers. The OMU board automatically restarts on the DHCP
server. The installation of the Linux operating system starts.
Issue 08 (2012-02-27)

157
BSC6900 GSM
NOTE
l The OMU board may automatically restart several times during the installation process.
l In the early stage of the installation, the HyperTerminal shows that the board is restarted several times. Do
not perform any operation by using the mouse or keyboard until the initrd.ini file of the Linux operating
system is automatically loaded.
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. Thus, 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 firewalls. If the DHCP server is started because the install.bat file is
executed multiple times, run the install.bat stop command to terminate DHCP services. Then, run the
install.bat file to start the Easyinstall software.
l During the installation process, do not connect the keyboard and mouse to the portable computer in case of
any interruption.
Step 18 Query the status of OMU operating system installation.

l You can view the autoinst\log\task\mac file. If Success is displayed, it indicates that the
installation is complete.
l Double-click checkout.bat under the autoinst directory to view the status of OMU operating
system installation.
After the operating system is installed, though the OMU board will still choose the network for
startup, the software of the installation source server has automatically canceled the network
service provided to the OMU board; therefore, the OMU board will start from the hard disk.
Step 19 In the cmd prompt command window, run the install.bat stop command to stop the EasyInstall
service.
NOTE
After the EasyInstall service is finished, the shared folder set by the EasyInstall software is closed automatically.
----End
Result
l
The SEK SetSuSe software is installed.
The GOMU hard disk is partitioned.
l
Issue 08 (2012-02-27)
Partition
Capacity
Type
Directory
/dev/sda
67.9 GB
/dev/sda1
133.3 MB
EXT3
/boot
/dev/sda2
67.8 GB
Extended
/dev/sda5
2.0 GB
Swap
swap
/dev/sda6
10.0 GB
EXT3
/dev/sda7
5.0 GB
EXT3
/BSC6000
/dev/sda8
Remaining capacity
EXT3
/BSC6000/data
The password for user root is 11111111.

158
BSC6900 GSM
The common user bsc6000 is created and the password of bsc6000 is set to 11111111.
The Samba service of the folder \BSC6000 is started. The sharing name of the folder
\BSC6000 is bsc6000, which is described as bsc6000 omu. The user name and password
of the folder \BSC6000 are bsc6000 and 11111111 respectively.
The folder \BSC6000\install is created. The authority of the \BSC6000 is changed to 777,
and the \BSC6000 is grouped to bsc6000.
The ETH4-SCU7 and ETH5-SCU6 are bounded as bond0, and the ETH0 and ETH1 are
bounded as bond1. The binding mode of bond0 is balance-rr, and that of bond1 is balancerr.
The IP address of the ETH2 Ethernet adapter on the panel of the OMU board is 192.168.1.1,
and the subnet mask 255.255.255.0.
The ECC and IPMI drives are installed.
The tool for identifying Ethernet adapters eth_alias_omu. sh is saved in the root directory.
The following table lists the drives and versions of the Linux operating system.
Drive
Version
LSI SAS1064
3.12.19.0
Intel82571
7.3.35
BCM5715C
3.58
ECC
1.0
IPMI
N/A
Network_Identify
N/A
5.1.2 Switching the OMU Operating System

This section describes how to switch the OMU operating system after the BSC6000 is upgraded
to the BSC6900.
Prerequisites
l
Before preparing a USB storage device to switch the OMU operating system, check that
the communication between the local PC and the OMU is normal. This ensures that the
tool for preparing the USB storage device obtains the configuration information of the target
OMU.
The virtual external IP address and external subnet gateway have been obtained.
Context
BSC6900 is Dopra Linux. After the BSC6000 is upgraded to the BSC6900, SUSE Linux can
still be used or switched to Dopra Linux.
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 configuration,
alarm, and platform data, performance configuration files, SSL certificate files, license files, and
SingleRAN BTS data upgrade files generated when a non-SingleRAN BTS is upgraded to a
Issue 08 (2012-02-27)

159
BSC6900 GSM
SingleRAN BTS. Meanwhile, all the OMU applications will be 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 on 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 on the file manager, see File Manager.
In the process of switching the operating system, the OMU is reset. In dual-OMU mode, the
OMU reset interrupts Operation and Maintenance (OM) for 5 minutes. In single-OMU mode,
the OMU reset interrupts OM for 20 minutes. The OMU reset does not affect the ongoing
services.
The communication between the M2000 and BSC6900 is interrupted when the OMU is reset.
The periodical traffic statistics 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 12
o'clock at night. 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 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 the USB storage device, verify it by referring to the DOPRA Linux USB Disk
Certificate Guide under the directory where the Dopra Linux USB disk is saved. If the USB
storage device is not usable, replace it. The Netac U208 (2G) is recommended.
The duration of preparing the USB storage device varies according to the bandwidth of the
network from the LMT PC to the equipment room, USB protocol, and LMT PC performance.
The duration listed in Table 1 refers to the duration of preparing a USB storage device in
compliance with the USB2.0 protocol. The duration of preparing a USB storage device in
compliance with the USB1.1 protocol is twice that of preparing a USB storage device in
compliance with the USB2.0 protocol. A much longer duration may result from a poor LMT PC
performance. In this case, restart the LMT PC or use a LMT PC of higher performance.
Table 5-2 Operation and Duration
Operation
Duration
Preparing a USB storage device.
The duration varies according to the

bandwidth of the network from the LMT PC
to the equipment room.
l If the network is 1 Mbit/s or faster:
OMU is configured.
l If the bandwidth is 512 kbit/s:
OMU is configured.
Install, restore, or switch the OMU operating

system from a USB storage device.
Issue 08 (2012-02-27)
20 to 40 minutes

160
BSC6900 GSM
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.
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.

Table 5-3 Configuration requirements for the portable computer
Issue 08 (2012-02-27)
Item
Quantity
Recommended
Configuration
CPU
1.66 GHz or faster
866 MHz
RAM
512 MB
256 MB
Hard
disk
80 GB
10 GB
Display
adapter
resoluti
on
1024x768 pixels or higher
800600

161
BSC6900 GSM
Item
Quantity
Recommended
Configuration
CD
drive
USB
installat
ion
drive
Operati
ng
system
l Microsoft Windows
XP Professional
l Microsoft Windows
Server 2003
l Microsoft Windows 7
3.
Obtain the tool for preparing the USB storage device.

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.

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 5.2.19 Setting the 1st 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
Issue 08 (2012-02-27)

162
BSC6900 GSM
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 open the USB storage device for installing a Dopra
Linux operating system, as shown in Figure 5-7.
Figure 5-7 U_creator_eng window
2.
Issue 08 (2012-02-27)
Select NE List in the area in the left pane of the window, right-click the NE list, and choose
Add NE from the shortcut menu. A dialog box is displayed, as shown in Figure 5-8.

163
BSC6900 GSM
3.
Enter the NE Name, select Switch from the Operate type drop-down list box, specify the
Virtual External IP, and click OK. An NE is added.
NOTE
l If you select EMS Proxy IP Address and enter 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 open to the PC without being shielded by network devices such as
firewalls.
l The NE name, external virtual IP address, and the EMS proxy IP address can only be changed after
you delete the NE and then add the NE.
l If you want to prepare multiple USB disks, it is recommended that you prepare the USB disks one by
one and mark the disks.
4.
Issue 08 (2012-02-27)
Double-click the added NE in the left pane of the window. The window is updated, as
shown in Figure 5-9.

164
BSC6900 GSM
5.
After all the information is obtained automatically, check the result and select the directory
for the version package. If there is a patch, select the directory for the patch also. Then,
click OK to start preparing 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 to4.1.1 Setting the Link Mode of the External OMU Ethernet Adapters. Table 3
lists the mapping between the queried link mode of OMU external Ethernet adapters and the
external network netcard mode of OMU selected in Figure 5-9.
Table 5-4 Mapping Between the Queried and Selected Link Mode of the OMU External
Ethernet Adapter
Issue 08 (2012-02-27)


l Auto-negotiation is on.
Link mode of the OMU external Ethernet

adapter to be selected is Auto.

165
BSC6900 GSM



adapter to be selected is 10Mb Full.
l Speed is 10Mb/s.
l Duplex is Full.
l Speed is 10Mb/s.

adapter to be selected is 10Mb Half.
l Duplex is Half.
l Speed is 100Mb/s.

adapter to be selected is 100Mb Full.
l Duplex is Full.
l Speed is 100Mb/s.

adapter to be selected is 100Mb Half.
l Duplex is Half.
CAUTION
l All the IP addresses shown in Figure 5-9 are obtained from the target OMU by the
Dopra Linux tool.
l If any information shown in Figure 5-9 is incorrect, suspend the operations, correct the
information on the working OMU, and then continue with the operation. The
information cannot be corrected in online mode on the tool.
l The IP addresses listed in Figure 5-9 must follow the principle of planning OMU IP
addresses. For details, see 3.2 Planning of the OMU IP Addresses. Change the
debugging IP address and debugging subnet mask.
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 single-OMU mode, pay attention to configurations for only the active OMU.
Configurations for the standby OMU do not take effect.
l The data to be backed up include 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 is generated when an NE is created. The directory
name is the same as the NE name.
l If NE Name of a new created NE is duplicate with an existing NE, the data backup file
directory of the existing NE will be replaced. Therefore, name the NEs differently.
Ensure that all the files have been backed up or that the files are no longer needed if any
NE names are duplicate.
Issue 08 (2012-02-27)

166
BSC6900 GSM
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-10.
Figure 5-10 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 there is the
relevant backup file under the Dopra Linux\NE Name\bk_pkg directory.
l The created backup file 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 created backup file after you click Save the NE backup data
Issue 08 (2012-02-27)

167
BSC6900 GSM
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.
7.
For preparing the USB storage device by using the local backup data, double-click
U_creator_eng.exe to start the USB storage device for installing a Dopra Linux operating
system, as shown in Figure 1.
8.
Select NE List in the area in the left pane of the window, right-click the NE list, and choose
Add NE from the shortcut menu. A dialog box is displayed, as shown in Figure 5-11.
9.
On the dialog box shown in Figure 5-11, enter 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-12.
Issue 08 (2012-02-27)

168
BSC6900 GSM
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 to prepare 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
NE by NE. Remove a USB storage device, and click Retry to start to prepare another USB storage
device.
l After the USB storage device is prepared, remove it from the PC in secure mode to protect the data
on it from being lost or corrupted.
13. After the USB storage device used for switching the operating system of the active OMU
is prepared, 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 of
multiple NEs needs to be switched, label USB storage devices with NE name and OMU slot number
to differentiate them.
14. After the USB storage device used for switching the operating system of the standby OMU
is prepared, click Finish. The preparation for the USB storage devices is complete.
Issue 08 (2012-02-27)

169
BSC6900 GSM
Step 3 Switch the OMU operating system by using the USB storage device.
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 single-OMU mode, perform Step 3.1, Step 3.2, Step 3.3, Step 3.4, Step 3.5, Step
3.7, and Step 3.10 in turn. In Step 3.4, you only need to check that the OMU works properly.
l In dual-OMU 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 is writable 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 LED on their
panels. The OMU with the ACT LED steady on is active, and the other with the ACT LED steady off is
standby.
2.
3.
Restart the OMU.

a.
Log in to the OMU by using the OMU fixed external IP address. For details, see
Logging In to the OMU.
b.
Run the reboot command.
Log in to the OMU 5 minutes later to determine whether the OMU operating system has
started to be installed from the USB storage device.
l If you fail to log in to the OMU, the OMU operating system has started to be installed
from the USB storage device.
l If you log in to the OMU successfully, the OMU operating system has not started to be
installed from the USB storage device. Prepare another USB storage device.
4.
Wait for 15 to 25 minutes until the OFFLINE indicator on the OMU panel stops blinking.
Then use the OMU virtual external IP address to log in to the LMT. After the OMU works
properly, as shown 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 for about 5 minutes and log in to the LMT using the OMU external virtual IP address.
After the OMU returns to normal, as shown 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.
l If the GBFD-511701 Radio Measurement Data Interface for Navigation feature is
configured, turn to Step 3.7.
l If the GBFD-511701 Radio Measurement Data Interface for Navigation feature is
not configured, turn to Step 3.8.
7.
Issue 08 (2012-02-27)
Optional: Only when BSC6900 is configured with the GBFD-511701 Radio

Measurement Data Interface for Navigation feature and the BSC local IP address is used
for communication between the OMU and VNP, you need to reconfigure the BSC local IP
address, VLAN IDs for communication between the OMU and VNP, and VLAN IDs for
communication between the OMU and EMS/LMT based on "OMU Ethernet Adapter Team
IP Address Installation Information." For details, see Configuring Radio Measurement Data
170
BSC6900 GSM
Interface for Navigation in GBSS Feature Activation Guide. And repeat Step 3.6 until
Data-sync state is Data synchronization is successful. Then, go to Step 3.8.
NOTE
In Step 3.6, if the queried value of External network link state is Breakdown, External network
link state will be Normal after performing Step 3.7.
8.
Run the BSC6900 MML command SWP OMU to switch over the active and standby
OMUs.
9.
Wait for 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.
10. Run the BSC6900 MML command DSP TIME to check whether the OMU system time
is correct.
Expected result: The OMU system time is correct.
If the OMU system time is incorrect, run the MML command SET TIME to change it.
11. Insert the USB storage device into any of the USB ports on the panel of the original active
OMU board.
12. Repeat Step 3.2, Step 3.3, Step 3.4, Step 3.7, and Step 3.9 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, enter the user name and password that are used before
the OMU operating system is switched and check whether 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 on 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 switch, the setting on the original operating system for disabling root
user remote login and OMU route forwarding will be ineffective. You need to reset on the
switched operating system by referring to 7.1 Disabling root user remote login and 7.2
Disabling OMU route forwarding.
5.1.3 Optional: Installing the OMU Applications

This section describes the installation policy for the OMU applications after the BSC6000 is
upgraded to the BSC6900.
Prerequisites
Software > Wireless > SingleRAN > SRAN O&M tools > OMU Driver Upgrade V1.1 to
download the OMU Suse Linux 9.3 Operating System Driver Upgrade Guide.
Issue 08 (2012-02-27)

171
BSC6900 GSM
Context
l
If the operating system is Dopra Linux after the upgrade from the BSC6000 to the
BSC6900, see 4.2.4 Optional: Installing the OMU Applications for the installation
method of the OMU applications.
If the operating system is still Suse Linux after the upgrade from the BSC6000 to the
BSC6900, see the section for the installation method of the OMU applications.
WARNING
l After the upgrade and before the OMU applications are reinstalled, record the IP addresses
of the existing network. After the OMU applications are reinstalled, the IP addresses need
to be set again, or restored from the history IP addresses on site.
l If patches are installed in the existing network, the patch installation package needs to delete
the original patch files saved in the patch folder for OMU applications, copy the patches (for
example, the V900R01XC0XSPCXXX folder) saved on the local computer to the patch
folder for OMU applications.
If an OMU application is pre-installed on the OMU, uninstall it and then install the OMU
application. To check whether an OMU application has been pre-installed on the OMU, do as
follows:
1.
Log in to the OMU by using the fixed external IP address or the debugging IP address. For
details, seeLogging In to the OMU.
2.
Enter the cd /BSC6000/data/mbsc/bam command and press Enter to go to the current

directory.
3.
Enter the ls command and press Enter to check whether the BSC6900 OMU application
has been pre-installed on the OMU.
l If there is a version_a or version_b file, it indicates that an OMU application has been
pre-installed on the OMU. Then, uninstall the application. For details about how to
uninstall the application, see operation procedures in Uninstalling the OMU
Applications.
l If there is neither version_a or version_b file, it indicates that no OMU application has
been pre-installed on the OMU.
4.
4. Enter the omuctrl stop command and press Enter to check whether the BSC6000 OMU
application has been pre-installed on the OMU.
l If the execution is successful, it indicates that the BSC6000 OMU application has been
pre-installed on the OMU. Then, uninstall the application. For details about how to
uninstall the OMU application, refer to relevant BSC6000 guides.
l If the -bash: omuctrl: command not found message is displayed, it indicates that no
BSC6000 OMU application has been pre-installed on the OMU. Then, continue with
installation of the OMU application.
5.
Run the exit command to terminate the PuTTY software.
Procedure
Step 1 Install the OMU driver by referring to the OMU Suse Linux 9.3 Operating System Driver
Upgrade Guide.
Issue 08 (2012-02-27)

172
BSC6900 GSM
NOTE
The OMU operating system may restart and therefore operation and maintenance is interrupted if there is a very
earlier version of Ethernet adapter driver and hard disk driver in use.
Step 2 Log in to the OMU using the debugging IP address by referring to Logging In to the OMU.
Step 3 Upload the OMU application installation package to /BSC6000/data/mbsc/upgrade of the
OMU by referring to Uploading the OMU Application Installation Package to the OMU.
Step 4 Install the OMU operating system from a USB storage device by referring to Installing the
OMU Applications in the Active Workspace.
Step 5 Reconfigure all the IP addresses of the OMU by referring to Changing IP Addresses and Masks
of the OMU Ethernet Adapters according to the principle of planning OMU IP addresses
describes in 3.2 Planning of the OMU IP Addresses.
NOTE
In the previous BSC6000 network, the default backup channel IP address of the post-positioned OMU is
192.168.10.121 or 192.168.10.123, and the default backup channel IP address of the pre-positioned OMU is
192.168.10.100 or 192.168.10.102. If these IP addresses are used in the existing network, the backup channel
IP address must be changed.
The post-positioned OMU is located in slot 14-27, and the pre-positioned OMU is located in slot 0-13.
----End
5.2 OMU Operation and Maintenance After the Upgrade

commands.
Context
After the BSC6000 is upgraded to the BSC6900, the OMU operation and maintenance are related
to 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.
If the OMU operating system is still Suse Linux, perform the steps in this section for the
OMU maintenance and operation.
Procedure
----End
5.2.1 Querying the Operating Status of the OMU

This section describes how to query the operating status of the OMU subsystem and the service
processes, and the status of the board.
Prerequisites
Issue 08 (2012-02-27)

173
BSC6900 GSM
Procedure
l
Query the status of the OMU subsystem.

1.
Run the DSP OMU command. The operating status of the OMU subsystem is
displayed, including the OMU operating status, fixed IP address configuration, virtual
IP address configuration, data synchronization status, status of the internal/external
networks, and status of the backup channel.
Query the status of the service processes when the OMU is operational.
1.
Run the DSP OMUMODULE command. The names and status of the service
processes are displayed.
If the state of the service processes is Started, the OMU service processes are
normal.
If the state of the service processes is Stopped, the OMU service processes are
normal and not started.
If the state of the service processes is Exception, the OMU service processes are
abnormal. In dual-OMU mode, the self-healing switchover is triggered if the
abnormal state persists. In single-OMU mode, the OMU reports the alarm
ALM-20707 OMU Process Abort.
Query the status of the OMU.

1.
Run the DSP OMUSRV command. The information related to the OMU is displayed,
including the CPU usage, memory usage, total space of each logical disk, current free
space, and percentage of the free space of the OMUa board.
----End
5.2.2 Querying the Information About the OMU

This section describes how to query the working environment, hardware state, and version of
the OMU.
Prerequisites
Context
When a fault occurs on the OMU, you can query the information about the OMU for fault
location.
Procedure
l
Query the working environment of the OMU.

1.
Run the DSP OMUENV command. The voltage and temperature of the CPU, hard
disk, and chips are displayed.
Query the hardware information about the OMU.

1.
Run the DSP OMUHW command. The subrack number, slot number, and operating
status of the hard disk, Ethernet adapters, Ethernet adapter teams, and RAID of the
OMU are displayed.
The hardware of the OMU is normal if the following conditions are met:
Issue 08 (2012-02-27)

174
BSC6900 GSM
The state of the Primer harddisk and Standby harddisk is Online.

The state of the Raid is Normal, and the Raid rebulid scale is 0.
The ETH0 netcard or ETH1 netcard is Normal.
In dual-OMU mode, the Backup channel netcard is Normal; in single-OMU
mode, the Backup channel netcard does not have impact on the state of the OMU.
The Inner0 netcard or Inner1 netcard is Normal.
Inner netcard group and Extra netcard group are both Normal.
l
Query the version information about the OMU.

1.
Run the DSP OMUVER command. The subrack number, slot number, and version
information about the PCB, BIOS, BMC, CPLD, and SDR are displayed.
----End
5.2.3 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
5.2.4 Querying the Status of the Data Synchronization Between the

Active OMU and the Standby OMU
This section describes how to query the status of the data synchronization between the active
OMU and the standby OMU.
Prerequisites
l
Context
The data synchronization may be faulty due to network or database problems. The OMU will
rectify the fault automatically. In such situation, the Data-sync state is Data
synchronization fault.
Procedure
Step 1 Run the DSP OMU command on the active OMU or standby OMU. The status of the data
synchronization between the active OMU and the standby OMU is displayed.
Issue 08 (2012-02-27)

175
BSC6900 GSM
If the data synchronization is normal, the alarm ALM-20704 OMU Data Synchronization Failure
is reported. Clear the alarm by referring to the suggestions.
CAUTION
When the Data-sync state is Data synchronization is successful, Data synchronization not
built due to version inconsistency or Data synchronization can not built due to OMU failure
switchover, the active and standby OMUs can be switched over.
----End
5.2.5 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
l
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, and run the CMP OMUDATA command five minutes later.
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 license file, patch file, and
performance file between the active and standby OMUs.
----End
5.2.6 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, re-set the OMU time, and change the OMU time zone.
Prerequisites
l
Issue 08 (2012-02-27)
176
BSC6900 GSM
You have obtained the time and 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.
Change the OMU time zone

1.
Run the SET TZ command to change the OMU time zone.
----End
5.2.7 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.
Procedure
Step 2 Run the passwd root command (using user root as an example). A message is displayed,
prompting you to enter the password, as shown in the following figure.
Changing password for root.
New password:
Step 3 Enter a password and press Enter. The message Re-enter new 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.
Step 5 Record the new password in the 4.5.1 Records of OMU Software Installation Information.
----End
5.2.8 Switching Over the Active/Standby OMU Workspaces

This section describes how to switch over the active and standby OMU workspaces for OMU
version upgrade and rollback.
Prerequisites
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 through the CMP OMUDATA and CMP
Issue 08 (2012-02-27)

177
BSC6900 GSM
OMUFILE commands to ensure that the data on the active OMU is totally synchronized
to the standby OMU.)
Context
Do not use this command in other cases.
Procedure
l
Switch over the active/standby OMU workspaces in single-OMU mode.

1.
OMU) to switch over the active and standby workspaces on the OMU.
2.
the host data.
Switch over the active/standby OMU workspaces in dual-OMU mode.

1.
Run the SWP OMUAREA command and set Target OMU to STANDBY (Standby
2.
3.
the host data.
----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 software/hardware upgrade or fault rectification. By
performing this task, the OMU services are not interrupted.
Prerequisites
l
The OMU works in active/standby mode and the active and standby OMUs work normally
for more than five 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 totally 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
synchronization is normal,
Go to Step 2.
The active and standby OMUs do not work properly or the data
synchronization is abnormal,
End this task.
Issue 08 (2012-02-27)

178
BSC6900 GSM
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, you can infer that the switchover is successful.
----End
5.2.10 Setting the FTP User Password

This section describes how to set the FTP user password so that it suits the user.
Prerequisites
Context
After the BSC6000 is upgraded to the BSC6900, the default FTP user password remains valid.
Alternatively, the password can be re-set so that it suits the user.
Procedure
Step 1 Run the MOD FTPPWD command to set the New Password and Confirm Password
parameters.
Step 2 Record the new FTP user password in the Records of OMU Operating System Installation
Information.
----End
5.2.11 Setting RAID 1 on the OMU Hard Disks

This section describes how to set RAID 1 on the OMU hard disks to ensure that the data on the
target OMU hard disk is synchronized with that on the source OMU hard disk.
Prerequisites
l
The OMU is started normally.
The OMU serial cable is obtained. For details about the OMU serial cable, see OMU serial
port cable.
The source hard disk and target hard disk 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 target hard disk with that on the
source hard disk, thus improving data security.
l
The source hard disk saves the backup data and files.
The target hard disk mirrors the source hard disk.

NOTE
This task cannot be performed on an OMUc board because it is configured with one hard disk.
Issue 08 (2012-02-27)

179
BSC6900 GSM
Procedure
Step 1 Connect the PC to the serial port of the OMU through the OMU serial 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. A dialog box is displayed, as shown in Figure 5-14.
Issue 08 (2012-02-27)

180
BSC6900 GSM
Step 4 Check the connection port and click OK. A dialog box is displayed, as shown in Figure 5-15.
Issue 08 (2012-02-27)

181
BSC6900 GSM
NOTE
Step 5 Check that the parameters of the connection port are correct and click OK. A window is
displayed, as shown in Figure 5-16.
Issue 08 (2012-02-27)

182
BSC6900 GSM
Step 6 Restart the OMU.

Option
Description
Suse Linux/Dopra Linux Operating

system
Log in to the target OMU by the PuTTY

software. Type the reboot command and press
Enter to restart the OMU. For details about the
PuTTY software, see 4.4.2 PuTTY Software.
Windows Server 2003 Operating system
1. Logging In to the OMU.

2. Choose Start > Close, Select Restart and
click OK.
Step 7 After the OMU is restarted, until the message "Press Ctrl-C to start LSI Logic
Configuration Utility" is displayed. Press Ctrl+C. Messages are displayed, as shown
in the following figure (an example).
Adapter PCI
Bus
SAS1064 05
PCI
Dev
01
PCI
Fnc
00
PCI
Slot
00
FW Revision
0.11.01-IR
Status
Boot
Order
Enabled 0
Step 8 Press Enter. Messages are displayed, as shown in the following figure (an example).
Issue 08 (2012-02-27)

183
BSC6900 GSM
Adapter
PCI Slot
SAS Address
NVDATA Version
Status
Boot Order
Boot Support
SAS1064
00
05:01:00
0.11.01.00-IR
500E0FC1:23456775
25.09
Enabled
0
[Enabled Bios & OS]
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 normally.
l If Status is Resyncing, the RAID is synchronizing data.
NOTE
l If the RAID of the OMU is set for the first time, go to Step 13.
l If the RAID of the OMU is set for the second time, go to Step 9.
Step 9 Select RAID Properties and press Enter. Results are displayed, as shown in the following figure
(an example).
Array
1 of 1
Identifier
Type
IM
Scan Order
2
Size(MB)
69618
Status
Optimal
Manage Array
RAID Hot Drive
Pred
Num
Disk Spr Status
Fail
0 FUJITSU MAY2073rc
D109 [Yes] [No] Primary
--1 FUJITSU MAY2073rc
D109 [Yes] [No] Secondary ---
Size
(MB)
69618
69618
Step 10 Select Manage Array and press Enter. Results are displayed, as shown in the following figure
(an example).
Identifier
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. Results are displayed, as shown in the following figure
(an example).
Y
N
Delete array and exit to Adapter Properties

Abandon array detetion and exit this menu
Step 12 Select Y. Messages are displayed, as shown in the following figure (an example).
Adapter
PCI Slot
Issue 08 (2012-02-27)
SAS1064
00
05:01:00
0.11.01.00-IR

184
BSC6900 GSM
SAS Address
NVDATA Version
Status
Boot Order
Boot Support
500E0FC1:23456775
25.09
Enabled
0
[Enabled Bios & OS]
RAID Properties
SAS Topology
Step 13 Select RAID Properties and press Enter. Results are displayed, as shown in the following
figure.
Creat IM Volume
Create IME Volume
Create IS Volume
Create Integrated Mirror Array of 2

disks plus an optional hot spare,Data
on the primary disk may be migrated.
Create Integrated Mirrored Enhanced
Array of 3 to 8 disks including an
optional hot spare.
All DATA on array disks will be DELETED!
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. Results are displayed, as shown in the following
Array Type:
Array Size(MB):
Num
0 FUJITSU MAY2073rc
1 FUJITSU MAY2073rc
IM
------RAID
Disk
D109 [No]
D109 [No]
Hot Drive
Spr Status
[No] -----[No] ------
Pred
Fail
-----
Size
(MB)
70003
70003
CAUTION
Use caution when selecting the source and target hard disks. Otherwise, the data on the source
hard disk may be lost.
Step 15 Set RAID Disk to No, move the cursor to the value of RAID Disk of the source hard disk, and
press Space. Results are displayed, as shown in the following figure.
M
D
- Keep existing data, migrate to an IM array.

Synchronization of disk will occur.
- 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
on the source disk.
l If you press D, the data on the source hard disk is deleted and a new RAID is created.
Step 16 Press M or D to return to the messages shown in Step 14.
The value of RAID Disk is Yes, and the value of Drive Status is Primary.
Step 17 Select the target hard disk and press Space. An alarm is generated, as shown in the following
figure.
WARNING! Data was found on the selected disk,this data will be lost when the array
Issue 08 (2012-02-27)

185
BSC6900 GSM
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 of RAID Disk is Yes, and the value of Drive Status is Secondary.
Step 19 Press C. Results are displayed, as shown in the following figure.
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 updated, as shown in
Step 12.
Step 21 Select RAID Properties shown in Step 12 and press Enter. Results are displayed, as shown in
the following figure (an example).
Array
Identifier
Type
Scan Order
Size(MB)
Status
1 of 1
1M
0
69618
2% Syncd
Manager Array
Num
0 FUJITSU MAY2073rc
1 FUJITSU MAY2073rc
RAID
Disk
D109 [Yes]
D109 [Yes]
Hot
Spr
[No]
[No]
Drive
Status
Primary
Secondary
Pred
Fail
-----
Size
(MB)
69618
69618
Step 22 Check that the RAID 1 is set correctly, and then press Esc repeatedly until messages are
prompted, as shown in the following figure.
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. Setting the RAID 1 on the
OMU hard disks is complete and the OMU is restarted.
----End
5.2.12 Replacing the Public and Private Key Certificate Files

The public and private key certificate files match the OMU operating system. When the OMU
operating system changes, the public and private key certificate files of the active and standby
OMUs need to be synchronized so that you can log in to the OMU successfully.
Prerequisites
The IP addresses of the active and standby OMUs are obtained.
Context
This task is optional. Perform this task in the following scenarios:
Issue 08 (2012-02-27)

186
BSC6900 GSM
A single OMU is replaced by active and standby OMUs.
The faulty standby OMU is replaced by a backup standby OMU.
The standby OMU is reinstalled with operating system.
Procedure
Step 1 Log in to the standby OMU by referring to Logging In to the OMU.
Step 2 Run the cd /etc/ssh command to go to the directory where the public and private key certificate
files are saved.
Step 3 Run the rm *key* command to remove the public and private key certificate files of the standby
OMU.
Step 4 Run the scp IP address of the active OMU:/etc/ssh/*key* . command to copy the public and
private key certificate files of the active OMU to the standby OMU. You are prompted to enter
the admin password of the active OMU, as shown in the following figure (an example).
You are trying to access a restricted zone. Only Authorized Users allowed.
root@10.161.21.207's password:
Step 5 Type the password for user administrator of the active OMU and press Enter. The result is
displayed.
----End
5.2.13 Checking the Version of the Operating System

This section describes how to check the version of the OMU operating system.
Context
This task only checks the version of the OMU operating system. For details on further handling
of incorrect version of the OMU operating system, contact Huawei for technical support. For
details, see Contact Huawei Customer Service Center.
Procedure
Step 2 Run the uname -r command to view the version of the OMU operating system kernel.
l If 2.6.5-7.244-smp is displayed, you can infer that the version of the OMU operating system
is correct.
l If information other than 2.6.5-7.244-smp is displayed, you can infer that the version of the
OMU operating system is incorrect.
----End
5.2.14 Checking the OMU Hard Disk Partitions

This section describes how to check the OMU hard disk partitions and the capacity of each
partition.
Issue 08 (2012-02-27)

187
BSC6900 GSM
Procedure
Step 2 Run the df -h command to check the OMU hard disk partitions, as shown in the following figure
(an example).
Linux:~ # df -h
Filesystem
/dev/sda6
tmpfs
/dev/sda7
/dev/sda8
/dev/sda1
Size
9.9G
1013M
5.0G
51G
130M
Used Avail Use% Mounted on

1.8G 7.6G 20% /
4.0K 1013M
1% /dev/shm
904M 3.8G 19% /BSC6000
1.4G
47G
3% /BSC6000/data
11M 113M
9% /boot
NOTE
l In the Mounted on column, /BSC6000 indicates the OMU software partition that stores the BSC6000 OMU
applications. Ensure that this partition is equal to or greater than 3 GB. After the BSC6000 is upgraded to
the BSC6900, the data in this partition is retained but used for version rollback.
l In the Mounted on column, /BSC6000/data indicates the OMU software partition that stores the
BSC6000 OMU applications. Ensure that this partition is equal to or greater than 40 GB. After the
BSC6000 is upgraded to the BSC6900, the data in this partition is retained but used for version rollback.
The data in this partition will be automatically deleted in the further BSC6900 upgrade. The BSC6900 OMU
applications are stored in this partition.
l In the Mounted on column, / and /boot indicate the OMU operating system partition which stores the data
about the operation of the OMU operating system.
----End
5.2.15 Checking the OMU Memory Capacity-Size

This section describes how to check the OMU memory capacity and usage.
Procedure
Step 2 Run the free -m command to check the OMU memory capacity and usage, as shown in the
following figure (an example).
Linux:~ # free -m
total
used
free
Mem:
20251848177075
-/+ buffers/cache:
609
Swap:
20550
2055
shared
1162
1416
buffers
cached
NOTE
Data about the OMU memory is displayed in the "Mem" row.
----End
5.2.16 Checking the OMU Ethernet Adapter Teams

This section describes how to check the OMU Ethernet adapter teams and IP addresses of the
OMU Ethernet adapters.
Prerequisites
Active Workspace.
Issue 08 (2012-02-27)

188
BSC6900 GSM
Procedure
Step 2 Run the ifconfig command to view the OMU Ethernet adapter teams, as shown in the following
linux:~ # ifconfig
bond0
Link encap:Ethernet HWaddr 00:18:82:1B:5E:EE
inet6 addr: fe80::218:82ff:fe1b:5eee/64 Scope:Link
bond0.1

bond0.1:1 Link encap:Ethernet HWaddr 00:18:82:1B:5E:EE

bond1
Link encap:Ethernet HWaddr 00:18:82:1B:5E:F0

inet6 addr: fe80::218:82ff:fe1b:5ef0/64 Scope:Link
eth0

UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
Base address:0xcf80 Memory:fdce0000-fdd00000
eth1

Base address:0xcf00 Memory:fdc80000-fdca0000
eth2

UP BROADCAST MULTICAST MTU:1500 Metric:1
RX bytes:982582 (959.5 Kb) TX bytes:1377729 (1.3 Mb)
Interrupt:16
eth3

Issue 08 (2012-02-27)

189
BSC6900 GSM

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:17
eth4

Interrupt:16
eth5

UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17
lo
Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
linux:~ #
NOTE
l For details on the mapping between the logical and physical OMU Ethernet adapters, see 5.2.17 Changing
the Connection Mode of the OMU Ethernet Adapters.
l Run the ifconfig logical Ethernet adapter command to query the IP address, broadcast IP address, and mask
of the logical OMU Ethernet adapter.
----End
5.2.17 Changing the Connection Mode of the OMU Ethernet

Adapters
This section describes how to change the link mode of the external Ethernet adapters of the active
and standby OMUs to match the link mode of the switch to ensure that the network connection
is normal.
Prerequisites
The setting of the link mode of the switch is complete.
Context
The link mode information of the switch is obtained. You can obtain the information in the
following ways:
l
Running the command associated with the link mode of the switch
Contacting the maintenance personnel on the switch side from the customer
The principles for setting the link mode of the Ethernet adapters are as follows:
Issue 08 (2012-02-27)

190
BSC6900 GSM
If the link mode of the switch is forced mode, the link mode of the external Ethernet adapters
of the OMU must be set to forced mode.
If the link mode of the switch is adaptive mode, the link mode of the external Ethernet
adapters of the OMU must be set to adaptive mode.
Query the configuration of the OMU external Ethernet adapters
Procedure
1.
2.
Type the /root/eth_alias_omu.sh command and press Enter to query the mapping
between the physical and logical Ethernet adapters, as shown in the following figure
(an example).
eth0
eth1
eth2
eth3
eth4
eth5
06,0,0
06,0,1
04,4,0
04,4,1
08,4,0
08,4,1
ETH4-SCU7
ETH5-SCU6
ETH2
ETH3-UPDATE
ETH0
ETH1
NOTE
The details about the three columns in the figure for the configuration of OMU Ethernet
adapters are as follows:
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.
As indicated by the prompt in Step 2, the Ethernet adapters of the OMU, eth4 and
eth5, are external Ethernet adapters. These two Ethernet adapters are connected to the
switch, and thus their connection mode must be the same as that of the switch.
l
Change the configuration of the OMU external Ethernet adapters

NOTE
The following takes the example of changing the connection mode of eth4 from adaptive mode to forced
full-duplex mode when the connection mode of the switch is forced full-duplex mode.
1.
2.
Run the ethtool eth4 command to query theeth4 link mode. The screen is displayed,
as shown in the following figure (an example).
Linux:~ # ethtool eth4
Settings for eth4:
Supported ports: [ MII ]
10baseT/Half 10baseT/Full
Advertised link modes: 10baseT/Half 10baseT/Full
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Issue 08 (2012-02-27)

191
BSC6900 GSM

Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Current message level: 0x000000ff (255)
Link detected: yes
3.
Run the ethtool -s eth4 autoneg off command to switch off the adaptive connection
mode of eth4.
4.
Enter the ethtool -s eth4 speed 100 duplex full command to switch on the forced fullduplex connection mode of eth4.
5.
Run the ethtool eth4 command to query the connection mode of eth4. Check the
values of Auto-negotiation, Speed, and Duplex, as shown in the following figure (an
example).
Linux:~ # ethtool eth4
Settings for eth4:
Supported ports: [ MII ]
Advertised link modes: 10baseT/Half 10baseT/Full
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Supports Wake-on: g
Wake-on: d
Current message level: 0x000000ff (255)
Link detected: yes
NOTE
To set the connection mode of OMU Ethernet adapters to adaptive mode, run the ethtool -s logical
Ethernet adapter autoneg on command.
----End
5.2.18 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 of the LAN switch has been set to full-duplex.
Context
The link mode of the OMUa/OMUc external Ethernet adapters must be the same as that of the
LAN switch. If they are different, the network may be interrupted. If the link mode of the LAN
switch is specified, the link mode of the external Ethernet adapter on the OMUa/OMUC board
panel must be specified.
There are two link modes of the LAN switch: force mode and auto-negotiation mode.
Issue 08 (2012-02-27)

192
BSC6900 GSM
Procedure
Step 2 Query the logic names of external OMU Ethernet adapters.
Option
Description
OMUa/OMUb board 1. Type the /root/eth_alias_omu.sh command and press Enter.

OMUc board
1. Run the chmod +x ./eth_alias_names.sh command to acquire the

permission for running the ./install_bam.sh command.
2. Type the ./eth_alias_names.sh command and press Enter.
NOTE
External Ethernet adapters of the OMUa/OMUb board are ETH0 and ETH1, and those of the OMUc board
are F_ETH0 and F_ETH1. This task is performed on the logical OMU external Ethernet adapters.
The mapping between the OMU physical Ethernet adapters and the OMU logical Ethernet adapters is
variable. Assume that:
l The logic names of OMU external Ethernet adapters are eth0 and eth1.
l The force mode is full-duplex with a rate of 100 Mbit/s.
Step 3 Run the ethtool eth0 command to query the eth0 link mode. The following information (an
example) is displayed. Verify that the fields Speed, Duplex, and Auto-negotiation are
consistent with those of the link mode of the LAN switch.
Settings for eth0:
Supported ports: [ FIBRE ]
1000baseT/Full
Advertised link modes: 1000baseT/Full
Speed: 100Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Supports Wake-on: umbg
Wake-on: g
Current message level: 0x00000007 (7)
Link detected: yes
Option
Description
The link mode of eth0 is the

End this task.
same as that of the LAN switch.
The link mode of eth0 is
Go to Step 4.
different from that of the LAN
switch.
Step 4 Set the link mode of the OMUa external Ethernet adapters according to the link mode of the
LAN switch.
Issue 08 (2012-02-27)

193
BSC6900 GSM
Option
Description

switch is force,
Enter the ethtool -s eth0 speed 100 duplex full autoneg

off command.

switch is auto-negotiation.
Enter the ethtool -s eth0 speed 100 duplex full autoneg on

command.
NOTE
The fields in the command are described as follows:

l speed *** indicates Ethernet adapter rate: speed 10, speed 100, or speed 1000.
l duplex ***indicates duplex mode of the Ethernet adapters: full duplex mode (duplex full) or half duplex
mode (duplex half).
l autoneg *** indicates link mode of the Ethernet adapters: force (autoneg off) or auto-negotiation mode
(autoneg on).
Step 5 Repeat Step 3 through Step 4 to set the eth1 link mode.
NOTE
The link modes of eth0 and eth1 must be the same.

Do not reset the OMU before performing Step 6. Otherwise, the setting of the eth1 link mode becomes invalid.
Step 6 Create an Ethernet adapter attribute file.

1.
Enter the cd /etc/rc.d command to go to the target directory.
2.
Enter the touch rc.local command to add the Ethernet adapter attribute file.
3.
Enter the vi rc.local command to open the Ethernet adapter attribute file.
4.
Enter a (lower-case) to switch to the editing mode. Enter the command provided in Step
4 to set the link mode of the OMUa external Ethernet adapter according to the link mode
of the LAN switch.
l If the link mode of the LAN switch is force, type ethtool -s eth0 speed 100 duplex full
autoneg off and press Enter. Then, enter ethtool -s eth1 speed 100 duplex full autoneg
off.
l If the link mode of the LAN switch is auto-negotiation, type ethtool -s eth0 speed 100
duplex full autoneg on and press Enter. Then, enter ethtool -s eth1 speed 100 duplex
full autoneg on.
5.
Press ESC to switch to the command line mode. Type the :wq command and press
Enter to save and exit the rc.local file.
6.
Enter the cat rc.local command to check the contents of the rc.local file to determine
whether the file is created successfully.
If it fails to be created, repeat 6.3 through 6.5 to re-create it.
If the contents of the rc.local file are consistent with the settings, the Ethernet adapter
attribute file is created successfully. Otherwise, the Ethernet adapter attribute file fails to
be created.
7.
Run the chmod +x rc.local command to add execution rights to scripts.
8.
Run the cd /etc/rc.d/rc3.d command to switch to the target directory.
9.
Run the ln -s ../rc.local S07rc.local command to establish links to files.
----End
Issue 08 (2012-02-27)

194
BSC6900 GSM
5.2.19 Setting the 1st Boot Device of the OMU to USB

Before installing the Dopra Linux operating system using a USB storage device, ensure that the
1st boot device of the OMU is USB.
Prerequisites
l
The OMU starts normally.
The OMU is configured with a keyboard and monitor locally.
The OMU serial cable has been obtained. For details about the OMU serial cable, see OMU
serial port cable.
The USB storage device has been inserted to the USB port on the OMUb board.
Context
There are two methods of starting the OMU:
1.
Connecting the OMU to a PC through the HyperTerminal program on the PC.
2.
Connecting the OMU to the keyboard and monitor directly.

NOTE
This section is designed for OMUa and OMUb boards and uses OMUa board as an example. An OMUc board
is started from a USB port by default.
Procedure
l
Connect the OMU to a PC through the HyperTerminal program on the PC (recommended).

1.
Connect the PC to the OMU serial port through the OMU serial cable.
2.
On the PC, choose Start > All Programs > Accessories > Communications >
Issue 08 (2012-02-27)

195
BSC6900 GSM
3.
Enter the connection name and click OK. A dialog box is displayed, as shown in
Figure 5-18.
4.
Issue 08 (2012-02-27)
Check the connection port and click OK. A dialog box is displayed, as shown in
Figure 5-19.

196
BSC6900 GSM
NOTE
5.
Issue 08 (2012-02-27)
Check that the parameters of the connection port are correct and click OK. A window
is displayed, as shown in Figure 5-20.

197
BSC6900 GSM
6.
Restart the OMU.

If the OMU is installed with Suse Linux or Dopra Linux operating system,
a.
Log in to the target OMU by using the PuTTY software. Type the reboot
command and press Enter to restart the OMU. For details about the PuTTY
software, see 4.4.2 PuTTY Software.
If the OMU is installed with Windows Server 2003 operating system,
7.
Issue 08 (2012-02-27)
a.
Install the OMU operating system from a USB storage device by referring to
Logging In to the OMU.
b.
Choose Start > Shutdown, click Restart, and click OK.
After the OMU is restarted, switch to the window shown in Figure 5-20. Press F4 or
S repeatedly until the window is updated, as shown in Figure 5-21.

198
BSC6900 GSM
Figure 5-21 BIOS information
8.
Press the arrow keys to select Boot. The window is updated, as shown in Figure
5-22.
Figure 5-22 Boot setting
Issue 08 (2012-02-27)

199
BSC6900 GSM
9.
Press the arrow keys to select Boot Device Priority and press Enter. The window is
updated, as shown in Figure 5-23.
Figure 5-23 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-24.
Issue 08 (2012-02-27)

200
BSC6900 GSM
Figure 5-24 Setting the 1st boot device
11. Press Esc, select Exit, and press Enter. The window is updated, as shown in Figure
5-25.
Figure 5-25 Saving changes and exit
Issue 08 (2012-02-27)

201
BSC6900 GSM
12. Press the arrow keys to select Save Changes and Exit and press Enter. The changes
are saved. Exit the setting.
l
Connect the OMU to the keyboard and monitor directly.

1.
Connect the keyboard to the USB port and the monitor to the VGA port on the OMU
directly.
2.
Log in to the LMT. Run the RST OMU command to set Reset Type to HARD. Then
reset the target OMU. The BIOS Setup screen is displayed on the monitor, as shown
in Figure 5-26.
Figure 5-26 BIOS Setup
3.
PressDEL to enter BIOS Setup screen.
4.
Press the arrow keys to select Boot, as shown in Figure 5-27.
Figure 5-27 Boot tab page
Issue 08 (2012-02-27)
5.
Use the direction arrows on the keyboard to select Boot Device Priority and press
Enter.
6.
Use the direction arrows on the keyboard to select 1st Boot Device and press Enter.
Set the 1st boot device of the OMU operating system to USB, as shown in Figure
5-28.
202
BSC6900 GSM
Figure 5-28 Selecting the 1st boot device
7.
Press F10 to save the settings and exit.
----End
5.2.20 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.
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.
Resetting a specified OMU service process interrupts the service of the process for a while.
Reset the OMUa board/OMU applications
Procedure
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.
Issue 08 (2012-02-27)

203
BSC6900 GSM

NOTE
l When the OMU works in single-OMU mode, you need to 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.
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.21 Shutting Down the OMU

This section describes how to shut down the OMU by running a command or shutting down the
OMU hardware.
Prerequisites
l
The OMU is powered on and functional.
An ESD wrist strap and ESD gloves are ready.
Context
WARNING
The BSC6900 operation and maintenance network is disrupted if the OMU is shut down. Perform
this task with caution.
The OMU software must be shut down before the OMU hardware is shut down.
l
Stop the OMU processes before shutting down the OMU by running a command. For
details, see Stopping the omud.
The OMU can be shut down only manually if it fails to be shut down by running a command.
In dual-OMU mode, the BSC6900 operation and maintenance network is not disrupted
when the active OMU is shut down, for the standby OMU switches to active OMU.
Shut down the OMU by running a command.
Procedure
1.
2.
Type the poweroff command and press Enter.

The message The system is going down for system halt NOW! is displayed on the
screen, and the OMU starts the shutdown process. No operation on PuTTY is
available. The OFFLINE LED on the OMU flashes. The shutdown of the OMU is
complete when the LED is on steady in blue.
l
Issue 08 (2012-02-27)
Shut down the OMU by turning outwards the ejector levers.

204
BSC6900 GSM
1.
Turn outwards the ejector levers of the OMU.

The OMU starts the shutdown process. The OFFLINE LED on the OMU flashes. The
shutdown of the OMU is complete when the LED is on steady in blue.
NOTE
The OMU can be removed only when the OFFLINE LED is on steady in case that the data on the
OMU is lost or that the OMU is damaged.
----End
5.2.22 Routine OMU Maintenance After the Upgrade

This section describes how to log in to the OMU remotely to regularly check and clean up the
OMU hard disk and transfer files from the OMU to the LMT PC 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
the available space of any partition on the OMU hard disk is equal to or more than 20%.
Prerequisites
Procedure
l
Method 1
1.
Run the DSP OMUSRV command to query the available space of the partitions on
the OMU hard disk.
If the available space of any partition on the OMU hard disk is less than 20%,
perform the following operations:
a.
Back up the files on the partition that needs to the saved to a hard disk by
referring to Transferring and Backing Up Files.
b.
c.
Run the cd target directory to go to the directory where the files to be deleted
are saved.
d.
Run the rm file name or rm -rfolder name command to delete the unneeded
files.
If the available space of each directory is equal to or more than 20%, end this task.
l
Method 2
1.
2.
Run the df -h command to query the hard disk partitioning and usage.
If the usage of any hard disk partition exceeds 80%, save the files in the partition
to another hard disk if needed by referring to Transferring and Backing Up
Files.
If the usage of no hard disk partition exceeds 80%, go to Step 3.
Issue 08 (2012-02-27)

205
BSC6900 GSM
3.
Exit the OMU by referring to Logging Out of the OMU.
----End
Transferring and Backing Up Files

This section describes how to transfer files between the local computer and the OMU through
the FTP protocol, which is an important method of saving files in the OM process.
Prerequisites
l
The firewall on the portable computer is disabled.
The user password for FTP is obtained. For details, see 4.5.1 Records of OMU Software
Installation Information.
The OMU applications are started.
Context
There are two methods of transferring the files on the OMU:
l
Using the function of file management on the LMT
Running commands
Table 5-5 describes the commands that are used for downloading files.
Table 5-5 Commands frequently used on the FTP
Command
Description
Example
cd
Change directory
cd /mbsc/upgrade
dir

current directory
dir
get
Upload files from the OMU

to the local computer
get x (x indicates the file

name)
put
Download files from the

local computer to the OMU
put x (x indicates the file

name)
NOTE
This task takes how to download the 123.xml file from the OMU to local disk D as an example.
Procedure
l
Issue 08 (2012-02-27)
Download the files on the OMU by using the file management function on the LMT
1.
Start the file manager by referring to File Manager.
2.
Right-click the 123.xml file and choose Download.
Download the files on the OMU to local drive D by running commands

1.
On the local computer, choose Start > Run, enter cmd, and click OK.
2.
Type the d: command and press Enter to go to drive D.

206
BSC6900 GSM
3.
Enter the ftp IP address command to connect the local computer to the OMU. The
IP address indicates the IP address of the OMU.
4.
Enter the user name and password of the FTP. The connection between the local
computer and the OMU is established after the certification passes.
NOTE
The user name of the FTP is FtpUsr. The FTP password is set when the OMU applications are
installed. For details, see Records of the OMU Application Installation Information.
5.
Go to the directory where the file to be transferred is saved by referring to the command
listed in the preceding table.
6.
Transfer the file.
7.
Run the get 123.xml command.
Upload the 123.xml file from the OMU

to the local drive D.
Run the put 123.xml command.
Download the 123.xml file from the

local drive D to the OMU.
After the file transfer is complete, run the quit command to disconnect the FTP.
----End
Example
The following takes downloading the 123.xml file from local drive D to the /mbsc/bam/
version_a/bin/bam directory of the OMU as an example, as shown in the following figure.
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
D:\>
5.2.23 Managing the OMU Applications

This section describes how to manage the 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.
Prerequisites
Issue 08 (2012-02-27)

207
BSC6900 GSM
Procedure
Step 1 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 begins to provide normal services.
Procedure
In to the OMU.
----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.
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 When the omud is stopped, the connection between the OMU and the peripheral devices is
terminated if you have logged in to the OMU through the external virtual IP address.
Procedure
In to the OMU.
----End
Issue 08 (2012-02-27)

208
BSC6900 GSM

This section describes how to uninstall the OMU applications when they are not installed
properly.
Prerequisites
l
The OMU applications are installed. For details, see Installing the OMU Applications in
the Active Workspace.
The system data is backed up. For details, see Backing Up the System Data.
If both the active and standby workspaces of the OMU are installed with OMU applications,
uninstall the OMU applications on the standby workspace before uninstalling them on the
active workspace.
When the BSC6900 is configured with active and standby OMUs, uninstall the OMU
applications on both the active and standby OMUs.
If there is only the active workspace on the OMU, the system will prompt you to uninstall
the OMU applications on only the active workspace.
Context
NOTE
l Uninstalling the OMU applications from an OMU will cause all the data in the OMU to be lost. It is advised
to back up system data on the OMU before the unintalling by referring to Backing Up the System Data.
l If the BSC6900 is configured with the GBFD-511701 Radio Measurement Data Interface for
Navigation feature and the BSC local IP address is used to connect the OMU and the VNP, you must
deactivate the feature before the uninstalling by referring to Configuring Radio Measurement Data Interface
for Navigation in the GBSS Feature Actication Guide.
Procedure
Step 1 Log in to the standby OMU by using the fixed external IP address or the debugging IP address
by referring to Logging In to the OMU.
Step 3 Enter uninstall_bam under any directory of the OMU and press 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.
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.
Issue 08 (2012-02-27)

209
BSC6900 GSM
Step 8 Log in to the active OMU using the fixed external IP address or debugging IP address. Then
perform Step 2 through Step 7 again.
----End
5.2.24 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 OMUb board is damaged, it needs to be replaced with a new OMUa board. For
details, see Board Replacing Policies. The data on the damaged OMUb board needs to be
backed up and restored on the new OMUa board.
The OMU data needs to be backed up during routine maintenance.
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. When the OMU works in active/
standby mode, you should log in to the OMU to start the omu_backup_linker.
Prerequisites
Procedure
Step 1 Type the cd /BSC6000/data/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 2 Type the ./omu_backup_linker command and press Enter to start the omu_backup_linker tool,
# Please select one option to backup or restore OMU database, if you don't know it,
please consult the administrator.
Please input a valid bkp_res_type :
----End
Follow-up Procedure
l
Back up the system data through the omu_backup_linker by referring to Backing Up the
System Data.
Restore the system data through the omu_backup_linker by referring to Restoring the
System Data.
Issue 08 (2012-02-27)

210
BSC6900 GSM
Backing Up the System Data

This section describes how to back up the BSC6900 configuration data, performance data, and
alarm data through MML commands or the omu_backup_restore_tool.
Prerequisites
l
Prerequisites for performing this task using MML commands are as follows:
Prerequisites for performing this task using the omu_backup_restore_tool are as follows:
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 the failure of system data backup before
capacity expansion, upgrade, or 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
and Backing Up Files.
Backing up the data by using the omu_backup_linker tool

1.
Start the omu_backup_linker tool by referring to Starting the omu_backup_linker

Tool.
2.
Type backup and press Enter after the message "Please input a valid
3.
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 message "Backup OMU
database succeed!" is displayed, it indicates that the system data is
successfully backed up on the OMU hard disk.
----End
Example
Back up the OMU data to /mbsc/bam through the omu_backup_restore_tool and the name the
file as omu.bak. An example is given, as shown in the following figure.
omd_test_name /mbsc/bam/common/services # ./omu_backup_linker
Issue 08 (2012-02-27)

211
BSC6900 GSM

Please input a valid bkp_res_type : backup
Backup omu database
[100%]
Backup OMU database succeed!
omd_test_name /mbsc/bam/common/services #

This section describes how to restore the system data through the data backup file. The system
data consists of configuration data, performance data, and alarm data.
Prerequisites
l
Context
Restoring the BSC6900 system data will interrupt the services on the BSC6900 operation and
maintenance system. The data on the host will be inconsistent with the data on the OMU after
the system data is restored. As a result, the services will be greatly impacted. Therefore, you are
advised to restore the system data when the traffic volume is low.
NOTE
The OMU in dual-OMU mode is used as an example in this document. If an OMU is in single-OMU mode, skip
operations on the standby OMU.
Procedure
Step 1 Stop the omud on the active and standby OMUs by referring to Stopping the omud.
Step 2 Restore data in the original active OMU using the omu_backup_linker tool.
1.
Type the cd /mbsc/bam/common/services command and press Enter to go to the directory

2.
Enter the ./omu_backup_linker.exe command and press Enter to start the

3.
Type restore and press Enter after the message "Please input a valid
4.
Enter the directory and names of the backup files and press Enter after the message
Please input backup file pathname : is displayed. The system data starts
to be restored. A message is displayed to indicate whether the restore is successful. If the
restore is successful, the message "Restore OMU database succeed!" is
displayed.
Step 3 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.
Step 4 Repeat Step 2 to restore data in the original active OMU using the omu_backup_linker tool.
Issue 08 (2012-02-27)

212
BSC6900 GSM
Step 5 Stop the omud on the active and standby OMUs by referring to Starting the omud.
Step 6 Log in to the LMT by referring to Logging In to and Logging Out of the LMT. Run the REQ
CMCTRL.
Step 7 Check the consistency between the BSC6900 host data and the OMU data.
NOTE
After data restoration, check whether the BSC6900 host data is consistent with the OMU data. If not, load
the restored data to the BSC6900 host.
1.
Run the ACT CRC command to check whether the host data is consistent with the OMU
data.
l If the data is consistent, end this task.
l If the data is inconsistent, go to Step 7.2.
2.
Run the FMT DATA command to format the data in the OMU database so that the data
can be loaded into the host.
3.
If data inconsistency occurs in only one subrack, run the RST SUBRACK command to
reset this subrack. Before running the command, set Subrack No.. If data inconsistency
occurs in multiple subracks, run the RST BSC command to reset the BSC.
----End
Example
Restore the OMU data through the omu.bak file under /mbsc/bam. An example is given, as
shown in the following figure:
omd_test_name
Shutting down
omd_test_name
omd_test_name
~ # /etc/rc.d/omud stop
mbsc daemon..........
~ # cd /mbsc/bam/common/services
/mbsc/bam/common/services # ./omu_backup_linker

Please input a valid bkp_res_type : restore
Restore omu database
[100%]
Restore OMU database succeed!
omd_test_name /mbsc/bam/common/services # /etc/rc.d/omud start
Starting mbsc daemon
5.2.25 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 then start the
Issue 08 (2012-02-27)

213
BSC6900 GSM
Prerequisites
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 /BSC6000/data/mbsc/bam/version_a.
Procedure
Step 1 You have logged in to the OMU by referring to Logging In to the OMU through the external
fixed IP address.
Step 2 Type the cd /BSC6000/data/mbsc/bam/version_a/bin/bam command and press Enter to go
to the directory where the omutool program is saved.
Step 3 Run the ./omutool -h command. The parameter information on the omutool is displayed.
----End

This section describes how to set the working mode of the OMU through the omutool. The OMU
can work either in single-OMU mode or dual-OMU mode.
Prerequisites
l
You have logged in to the LMT, and queried the slot No. for the OMU by running the LST
BRD command.
You have logged in to the LMT, and queried whether the OMU is in single-OMU or dualOMU mode by running the DSP OMU command.
You have logged in to the LMT, and queried OMU version and workspace information by
running the LST OMUAREA command.
You have logged in to the LMT and queried OMU service mode by running the LST
MBSCMODE command.
If the working mode is changed from single-OMU mode to dual-OMU mode, apply the
settings to both the active and standby OMUs. If the working mode is changed from dualOMU mode to single-OMU mode, apply the settings to only the working OMU.
If the working mode of the OMU is changed from single-OMU mode to dual-OMU
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 a active/standby relation.
Context
Issue 08 (2012-02-27)

214
BSC6900 GSM
If the working mode of the OMU is changed from dual-OMU mode to single-OMU
mode, you should run the DSP OMU command to ensure that the Data-sync state is Data
not installed on the OMU to be added.).
Procedure
Issue 08 (2012-02-27)
1.
Insert an OMUa/OMUb/OMUc board into the standby slot by referring to Installing

the OMUa Boards or Installing the OMUc Boards.
2.
Check the operating system of the standby OMU by referring to the instructions
describes in Table 5-6.

215
BSC6900 GSM
Table 5-6 Checking the operating system of the standby OMU

If...
Then...
The operating system of

the original working
OMU and that of the
standby OMU are both
Dopra Linux.
Method 1: downloading the software installation

package and install OMU applications
1. Connect the PC to the debugging Ethernet port of the
standby OMU, log in to the standby OMU through
the debugging IP address, upload the OMU
application installation package to the stanbdy
OMU, and then install the OMU applications on the
active workspace of the standby OMU. For
instructions for the operations, see Logging In to the
OMU, Uploading the OMU Application
Installation Package to the OMU, and Installing
the OMU Applications in the Active Workspace.
NOTE
You must select dualmode in the process of installing the
OMU applications.
2. Change the IP addresses and masks of the OMU

Ethernet adapters by referring to Changing IP
Addresses and Masks of the OMU Ethernet
Adapters to ensure that the internal fixed IP
addresses, external fixed IP addresses, backup
channel IP address of the active and standby OMUs
comply with the planning principle for the IP
Method 2: installing OMU applications using the USB
storage device
1. Prepare the USB installation disk for the standby
OMU. For instructions to prepare the USB
installation disk, see section "Preparing the USB
installation disk for the initial installation of the
OMU operating system and applications" in 4.2.2
Preparing the USB Storage Device. IP addresses
must be configured, and OMU software installation
package and patch installation package must be
loaded during the preparation of the USB installation
disk.
2. Install OMU applications using the USB installation
disk by referring to 4.2.3 Installing the OMU
Operating System from a USB Storage Device.
Issue 08 (2012-02-27)

216
BSC6900 GSM
If...
Then...

OMU and that of the
standby OMU are both
SUSE Linux.
NOTE
The directory structure of the OMU with SUSE Linux is
different from that of the OMU with Dopra Linux. The OMU
application installation package must be uploaded to the /
BSC6000/data/mbsc/upgrade directory.

NOTE
OMU applications.

OMU is Dopra Linux,
and that of the standby
OMU is SUSE Linux.
1. Prepare the USB installation disk for the standby

OMU. For instructions to prepare the USB
installation disk, see section "Preparing the USB
installation disk for the initial installation of the
OMU operating system and applications" in 4.2.2
Preparing the USB Storage Device. IP addresses
must be configured, and OMU software installation
package and patch installation package must be
loaded during the preparation of the USB installation
disk.
2. Install OMU applications using the USB installation
disk by referring to 4.2.3 Installing the OMU
Operating System from a USB Storage Device.
Issue 08 (2012-02-27)

217
BSC6900 GSM
If...
Then...

OMU is SUSE Linux,
and that of the standby
OMU is Dopra Linux.
Method 1: switching the operating system of the original

working OMU from SUSE Linux to Dopra Linux
1. Record the IP addresses of the original working
OMU.
2. Prepare a USB installation disk. For instructions to
prepare a USB installation disk, see section
"Preparing the USB installation disk for the initial
installation of the OMU operating system and
applications" in 4.2.2 Preparing the USB Storage
Device. Ensure that the configured IP addresses are
the same as the original ones.
3. Switch the oprating system of the original working
OMU to Dopra Linux using the USB installation disk
by referring to 4.2.3 Installing the OMU Operating
System from a USB Storage Device.
NOTE
OMU applications.

Method 2: switching the operating system of the standby
OMU from Dopra Linux to SUSE Linux
1. Install SUSE Linux on the standby OMU by referring
to 5.1.1 Re-Installing the Suse Linux Operating
System.
2. Install OMU applications on the stanbdy OMU by
referring to 5.1.3 Optional: Installing the OMU
Applications.
3.
Issue 08 (2012-02-27)
Log in to the original working OMU and stop omud on it. For detailed instructions,
see Logging In to the OMU and Stopping the omud.

218
BSC6900 GSM
4.
omutool.
5.
6.
7.
After the original working OMU is started for five minutes, start the omu on the
standby OMU by referring to Starting the omud.
WARNING
can be avoided.
8.
Operating System.
9.
Run the ADD BRD command on the LMT to add an OMU.
l
installed on the OMU to be added.).
1.
Connect the PC to the debugging Ethernet port of the OMU, log in to the original
working OMU, and then stop the omud on the original working OMU. For instruction
to log in to the OMU and stop the omud, see Logging In to the OMU and Stopping
the omud.
2.
omutool.
3.
4.
5.
Five minutes after the origianl working OMU is started, insert an OMUa/OMUb board
to the slot for the standby OMU by referring to Installing the OMUa Boards or
Installing the OMUc Boards.
WARNING
can be avoided.
6.
Issue 08 (2012-02-27)
Set the working mode of the standby OMU to dual-OMU mode by performing Step
1 to Step 3.
219
BSC6900 GSM
7.
8.
Start the omud on the standby OMU by referring to Starting the omud.
9.
Operating System.
l
Change the working mode of the OMU from dual-OMU mode to single-OMU mode
1.
Run the RMV BRD command on the LMT to remove an OMU.
2.
Log in to the active and standby OMUs through the external fixed IP address by
referring to Logging In to the OMU, and then stop the omud on the active and standby
OMUs by referring to Stopping the omud.
3.
Run the poweroff command on the OMU which is to be removed to power off the
OMU.
4.
Remove the OMU to be removed by referring to Scenario: Old and New OMU Boards
Running the Same OS.
5.
Start the omutool on the working OMU by referring to Starting the omutool.
6.
Run the ./omutool dualmode single command on the working OMU to set the
working mode of the OMU to single mode.
7.
Start the omud on the working OMU by referring to Starting the omud.
----End
Changing IP Addresses and Masks of the OMU Ethernet Adapters

This section describes how to change IP addresses and subnet masks of the OMU Ethernet
adapters using omutool.
Prerequisites
l
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 change the IP addresses and
subnet masks of the Ethernet adapters of the standby OMU and then of the active OMU.
NOTE
This task describes how to change all the IP addresses and subnet masks of the OMU. You can perform steps
following the planning of the IP addresses on site.
Issue 08 (2012-02-27)

220
BSC6900 GSM
For details about the Ethernet adapter binding relation, see 3.1 OMU Ethernet Adapter
Configuration.
Procedure
Step 1 Stop the omud on the target OMU by referring to Stopping the omud.
Step 2 The ./omutool innercard IP address command is used to change the internal fixed IP address.
For example, type the following command and press Enter:
Step 3 The ./omutool innervip IP address command is used to change the internal virtual IP address.
NOTE
If you are changing the fixed internal IP address and internal virtual IP address 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 network
segments on which the internal fixed IP address and internal virtual IP address are located.
2. Remove the SCUa board from the MPS and then install the SCUa board in the MPS to reset the MPS and
validate the new internal fixed IP address and internal virtual IP address.
After the two steps are performed, the OMU can communicate with the BSC6900 host normally.
Step 4 The ./omutool extercard IP address mask (gateway) command is used to change the external
fixed IP address and mask.
CAUTION
Before changing the fixed external IP address, virtual external IP address, and external gateway
IP address, you must log in to the OMU using the debugging IP address.
NOTE
To change both the fixed external IP address and the gateway IP address, do as follows:
l Type the ./omutool extercard IP address mask gateway command and press Enter to change the
external fixed IP address and gateway at the same time. For example,
./omutool extercard 10.161.10.100 255.255.255.0 10.161.10.1
l Type the ./omutool gateway gateway command and press Enter to change the gateway separately.
For example,
./omutool gateway 10.161.10.1
Step 5 The ./omutool extervip IP address mask command is used to change the external virtual IP
address and mask.
NOTE
After the external virtual IP address and mask are changed, run the RMV EMSIP command and then the ADD
EMSIP command to update the external virtual IP address and mask that are recorded in the OMU database.
Step 6 Change the backup channel IP address of the active and standby OMUs by using commands
listed in the following table.
Issue 08 (2012-02-27)

221
BSC6900 GSM
Option
Description

Ethernet adapter ETH3-UPDATE of
the OMUa board
./omutool backupcard IP address.

For example, type the following command and
press Enter:

./omutool backupcard_for_omuc IP address.
Ethernet adapter B_UPDATE0 of the For example, type the following command and
press Enter:
OMUc board
255.255.255.0
./omutool backupcard_for_omua IP address.

For example, type the following command and
press Enter:
OMUc board
./omutool backupcard_for_omua 192.168.3.60
Step 7 The ./omutool debugcard IP address command is used to change the debugging IP address.
NOTE
l To change the IP addresses of the OMU, you must follow the principle of IP address planning. For
details, see 3.2 Planning of the OMU IP Addresses. 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 Records of OMU Software Installation Information.
Step 8 For methods of configuring the BSC local IP address, see Configuring Radio Measurement Data
Interface for Navigation.
NOTE
The BSC local IP address is for communication between the OMU and VNP, for details, see 8.1 Scenario of
Connecting the OMU and VNP.
Step 9 Start the omud to validate the new admin password by referring to Starting the omud.
NOTE
If the external virtual IP address of the BSC6900 in single-OMU mode is changed, you must type the reboot
command and press Enter to restart the OMU.
----End
Follow-up Procedure
If the router settings also need to be changed on site when the virtual IP address and subnet mask
of the external network are changed, perform the following steps to change the settings.
1.
Log in to the LMT by referring to Logging In to and Logging Out of the LMT.
2.
Run the DSP OMU command to query the backup channel IP address of the standby OMU
and the virtual external IP address. The query result (an example) is as follows:
Subrack No.
Slot No.
Issue 08 (2012-02-27)
=
=
0
23

222
BSC6900 GSM
Computer name = bamupup

Internal network fixed IP = 80.168.3.60
External network fixed IP = NULL
Backup network IP = 192.168.10.123
Operational state = Standby normal
Other state
----------Internal network virtual IP = 80.168.3.40
External network virtual IP = 10.161.95.187
Internal network virtual IP state = Normal
External network virtual IP state = Normal
Data-sync state = Data synchronization is successful
Internal network link state = Normal
External network link state = NULL
Backup network link state = Normal
NOTE
As specified in the preceding query result, the backup channel IP address of the standby OMU is
192.168.10.123 and the virtual external IP address is 10.161.95.187.
3.
Log in to the target OMU using the virtual external IP address by referring to Logging In
to the OMU.
4.
Type the cd /BSC6000/data/mbsc/bam/common/ command and press Enter to go to the /

BSC6000/data/mbsc/bam/common/ directory.
5.
Type the vi reg.ini command and press Enter to open the vi reg.ini file.
6.
Search for the configuration items extranetaddr, extranetmask, and gateway and
reconfigure them.
WARNING
Ensure that the reconfiguration is correct. Incorrect configuration will make the OMU
inaccessible.
7.
Type the ssh backup channel IP address of the standby OMU command and press Enter
to log in to the standby OMU.
8.
Repeat 5 through 6 on the standby OMU.
9.
On the standby OMU, type the /etc/init.d/omud restart command and press Enter to
restart the standby OMU and validate the new settings.
10. After the standby OMU is restarted successfully, log out of the standby OMU by referring
to Logging Out of the OMU.
11. On the active OMU, type the /etc/init.d/omud restart command and press Enter to restart
the active OMU and validate the new settings.
12. After the active OMU is restarted successfully, log out of it.
WARNING
After the OMU is restarted and before the router configuration is changed, the OMU will
be inaccessible.
Issue 08 (2012-02-27)

223
BSC6900 GSM
13. Change the router configuration to make the OMU accessible by using the new virtual
external IP address.
14. Log in to the OMU using the new virtual external IP address.
15. Run the DSP OMU command to check whether the new virtual external IP address takes
effect.

This section describes how to change the admin, root, and account db_user passwords by using
the omutool, and how to change the FtpUsr password by using the MML.
Context
l
Admin is the account for the administrator to log in to the LMT.
The du_user and root are the account used by the OMU applications to access the OMU
database.
FtpUsr is the account for uploading and downloading files to and from the OMU.
Procedure
1.
2.
3.

4.
Run the ./omutool adminpwd command to change the admin password.
5.
Changing the root password

1.
2.
3.

4.
Run the ./omutool dbrootpwd command to change the root password.
5.
Changing the password of the db_user user

1.
Log in to the target OMU.
2.
3.

4.
Run the ./omutool dbpwd command to change the password of the db_user user.
5.
Changing the password of the FtpUsr user

1.
Log in to the LMT by referring to Logging In to and Logging Out of the LMT in the
2.
Run the MML command MOD FTPPWD to change the password of the FtpUsr user.
----End
Issue 08 (2012-02-27)

224
BSC6900 GSM
Example
The following is an example for the operation of changing the admin password:
Dopra_136 /mbsc/bam/version_a/bin/bam # ./omutool adminpwd
Successfully set the admin user's password!
The following is an example for the operation of changing the root password:
Dopra_136 /mbsc/bam/version_a/bin/bam # ./omutool dbrootpwd
Successfully set the root's password of the database!
The following is an example for the operation of changing the db_user user password:
Dopra_136 /mbsc/bam/version_a/bin/bam # ./omutool dbpwd
Successfully set the db_user's password of the database!
Changing the OMU Name

This section describes how to change the OMU name through omutool.
Prerequisites
l
Context
The OMU name and IP addresses have been planned by the customer. You need to change the
OMU name and IP addresses through the omutool after you have installed the OMU applications.
For how to change the OMU IP addresses, see Changing IP Addresses and Masks of the OMU
Ethernet Adapters.
Procedure
Step 1 Starting the omutool.
Step 3 Run the ./omutool hostname OMU name command to change the OMU name.
For example, to change the OMU name to omu_123, type the ./omutool hostname omu_123
command and press Enter.
Step 4 Start the omud by referring to Starting the omud to validate the new name.
----End
Follow-up Procedure
1.
Issue 08 (2012-02-27)
Log in the LMT.

225
BSC6900 GSM
2.
Run the DSP OMU command to query the new name.

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.
The target slots for OMUs are idle and can hold OMUs. Such slots refer to OMUa/
OMUb Board or OMUc Board.
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.
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

Linux operating system is used

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

the OMU.
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.
Issue 08 (2012-02-27)

226
BSC6900 GSM
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.
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: the SEK SetSuse Software

This section describes how to install, use, and uninstall the SEK SetSuse software.
Context
The SEK SetSuse software is a security enhancement tool for a server's operating system. It is
suitable for Suse Linux Enterprise Server 9.0 and Suse Linux in versions later than Suse Linux
Enterprise Server 9.0.
The SEK SetSuse software performs the following functions:
l
Closing unnecessary services
Enhancing the SSH service
Controlling the authority to access files and directories
Limiting the authority to access the system
Managing the user password
Recording operation logs
Checking whether the system operates normally

NOTE
If the operating system is switched to Dopra Linux after the upgrade from the BSC6000 to the BSC6900, the
software cannot be used.
5.3.1 Installing the SEK SetSuse Software

If the SEK SetSuse software is not integrated in the EasyInstall installation files during the
installation of the OMU operating system, the SEK SetSuse software needs to be installed
separately to customize the OMU operating system policies.
Issue 08 (2012-02-27)

227
BSC6900 GSM
Prerequisites
l
The OMU operating system is Suse Linux Enterprise Server 9.0 SP3 or later.
The reserved space for installing the SEK SetSuse software is 100 MB or larger.

Software > Wireless > SingleRAN > SRAN O&M tools to obtain the SetSuse
(forBSC6000)_VER.zip file. Extract the iPSISEKSetSUSEV100R002C01B509.tar.gz
file. Where, the policy file is SEKConf_V009R008C12.tar.
As Figure 5-29 shows, when logging in to the OMU through PuTTY, do not select Enable
X11 forwarding.
Context
Figure 5-29 PuTTY Configuration dialog box
Issue 08 (2012-02-27)
If the system displays SEK is already running after the SEK command is run, perform
the following operations:
1.
Type the ipcs -s|grep 14|awk '{print $2}' command and press Enter.
2.
Type the ipcrm -s "the value obtained through the previous command" command
and press Enter.

228
BSC6900 GSM
Procedure
Step 1 On the LMT computer, choose Start > Run. Type the IP address of the OMU and click
Confirm to log in to the OMU.
Step 2 Double-click the bsc6000 folder shared by the OMU on the LMT PC, and enter the right user
name and password in the logging prompt window to log in.
NOTE
The default user name is bsc6000 and the default password is 11111111.
Step 3 Copy the compressed installation package of the SEK SetSuse software, namely,
iPSISEKSetSUSEV100R002C01B509.tar.gz to the \BSC6000\install directory.
Step 4 Install the OMU operating system from a USB storage device by referring to Logging In to the
OMU.
Step 5 Type the cd /BSC6000/install command and press Enter to go to the path where the SEK
SetSuse software is saved.
Step 6 Type the tar -zxf iPSISEKSetSUSEV100R002C01B509.tar.gz command and press Enter to
decompress the compressed SEK SetSuse installation package.
Step 7 Type the cd iPSISEKSetSUSEV100R002C01B509 command and press Enter to change the
current directory to the directory for the SEK SetSuse software installation procedure (install.sh).
Step 8 Type the ./install.sh -p /opt -i /opt/seklog/ -if /BSC6000/install/
iPSISEKSetSUSEV100R002C01B509/<SEK SetSuse policy file>.tar -x command and press
Enter. In this way, start installing the SEK SetSuse software, importing the policy file, and
implementing the file.
NOTE
l -p is used to determine the SetSuse installation path.

l -i is used to determine the path for saving log files.
l -if is used to determine the policy file to be imported.
l -x is used to indicate immediate implementation of all policies after the installation.
If importing and implementing policy files need to be customized, refer to the SetSuse User Guide.
Step 9 The installation ends. The system indicates that the installation succeeds and that the SEK
SetSuse software is operational. The system also displays the installation log file path and the
installation path, as shown in the following figure.
Installation completed successfully
Note:
SEK installation log file path :
< /opt/seklog/SEKInstall.log >
SEK installation path :
< /opt >
SEK tool was run after installation, please refer the application log for details
SEK version :
iPSI SEK SetSuSE
Version V100R002 (B509)
----End
Follow-up Procedure
1.
Issue 08 (2012-02-27)
Type the cd .. command and press Enter.

229
BSC6900 GSM
2.
Type the rm -rf iPSISEKSetSUSEV100R002C01B509 command and press Enter to

delete the SEK SetSuse installation package.
3.
Type the omuctrl status command and press Enter to check that the OMU software is
running normally.
In dual-OMU mode, install the SEK SetSuse software for the standby OMU.
1.
Type the ssh bsc6000@*.*.*.* command and press Enter to log in to the standby OMU.
*.*.*.* indicates the backup channel IP address of the standby OMU.
2.
Type the scp bsc6000@*.*.*.*:/BSC6000/

iPSISEKSetSUSEV100R002C01B509.tar.gz /BSC6000 command and press Enter to
copy the compressed SEK SetSuse installation package of the active OMU to the BSC6000
directory of the standby OMU.
3.
Repeat Step 4 through Step 9 to finish installing the SEK SetSuse software on the standby
OMU.
5.3.2 Rolling Back Security Enhancement Policies During the Use

of the SEK SetSuse Software
When a PC cannot work normally after the operating system is customized through the SEK
SetSuse software, rollback of security hardening policies for the operating system can be
performed.
Context
l
When performing rollback, select the latest configuration data of the operating system that
works normally.
If the operating system cannot work normally after the rollback of security hardening
policies to the previous state, roll back the policies to the initial state.
Rollback of a specific policy
Procedure
1.
2.
Type the sekcli -p 11 command and press Enter to roll back policy 11 to the previous
state, as shown in the following figure (an example).
Linux:~ # sekcli -p 11
***********************************************************************
Policy Name : Secure SSH authentication (SEC.LNX.SRV.207)
Result
: Successful
***********************************************************************
NOTE
The sekcli -b 11 command is used to roll back a policy to the initial state.
Rollback of all policies in the policy file

1.
2.
Run the sekcli -p all command and press Enter to roll back all policies in the policy
file to the previous state.
The rollback result for each policy in the policy file is displayed on the screen.
Issue 08 (2012-02-27)

230
BSC6900 GSM

NOTE
The sekcli -b all command is used to roll back all policies in the policy file to the initial state.
----End
5.3.3 Uninstalling the SEK SetSuse Software

This section describes how to uninstall the SEK SetSuse software when it is not used any more
or it needs to be reinstalled.
Prerequisites
l
The SEK SetSuse software is installed successfully on the OMU.
The compressed SEK SetSuse installation package is decompressed and saved in the /
BSC6000/install directory on the OMU.
Procedure
Step 2 Type the cd /BSC6000/install/<SEK SetSuse installation package> command and press
Enter to change the current directory to the directory for the SEK SetSuse software uninstall
procedure (uninstall.sh).
NOTE
By entering the ls command, you can find the files such as such as Readme.txt, ActiveTcl-8.4,
Resource_install.txt, SEXInstall.log, install.sh, install.tcl, lib, uninstall.tcl, uninstall.sh, SEK.tar,
SEKResourseHandler.tcl, and User Manual.tar, in the directory of the SEK setSuse software installation
files.
Step 3 Type the sekuni command and press Enter to start uninstalling the SEK SetSuse software.
NOTE
l When uninstalling the SEK SetSuse software, the c filename option, for example, sekuni c /home/
SEKconfig can be used to export the configuration file. In the option, filename indicates the path for
the configuration file to be exported to.
l The path for saving the configuration file can be any valid path.
Step 4 As the following figure shows, the screen displays a message indicating that the uninstall will
remove the SEK SetSuse software directory including the check report. Press y to uninstall the
SEK SetSuse software.
Uninstallation will remove the SEK installation including
checkreport placed in the path<opt> </opt>
Are you sure you want to uninstall SEK?
Press "y" to proceed or "n" to abort
NOTE
Press n to cancel the uninstall and the operation ends.
Step 5 The interface prompts you to export the configuration data. Press Enter to export the
configuration data.
NOTE
The default destination path for exporting the configuration data is /opt/SEKexport.sek.
Issue 08 (2012-02-27)

231
BSC6900 GSM
Step 6 The interface prompts you to roll back the security policies of the operating system to the initial
state of policy applications. Press y or n as required.
Step 7 As shown in the following figure, the screen displays a message, indicating that the software
uninstall succeeds and displays the path for saving the uninstall log file.
SEK uninstallation completed successfully
Note:
SEK uninstallation log path : < /var/log/SEKUninstall.log >
----End
5.4 Appendix: Antivirus Software

Before installing the antivirus software, refer to the Antivirus Software Installation Guide
provided by Huawei. Now the BSC6000 supports the antivirus software installation: TrendMicro
Control Manager (TMCM) + ServerProtect for Linux 2.5. After the BSC6000 is upgraded to the
BSC6900, the antivirus software installation is still supported.
OMU Antivirus Software Networking

The OMU antivirus software consists of the server software, TrendMicro Control Manager
(TMCM) and the client software, ServerProtect for Linux 2.5.
Figure 5-30 Antivirus Software Networking
TrendMicro Control Manager

As a web-based management control console in the center of control management, TMCM
provides centralized monitoring of antivirus products and service in the entire network. It
manages the gateway, mail server, file server, TrendMicro products and service, and third-party
antivirus security products.
The TMCM server can connect to the Internet, download the latest virus feature codes, and
upgrade the equipment that is based on Suse Linux and monitored by the TMCM server.
Issue 08 (2012-02-27)

232
BSC6900 GSM
ServerProtect for Linux

TrendMicro ServerProtect for Linux 2.5 (TMSP) provides centralized scanning of viruses,
update on virus feature codes, reporting of events, and system configuration. By providing
comprehensive and real-time protection for enterprise servers, TMSP can protect the servers
against internal or external virus propagation, spy software, and other threats.
Huawei BSC6000 supports TMSP, which monitors the BSC6000 and protects it against viruses.
Installation of Antivirus Software

The operator needs to install antivirus software. Huawei provides a complete antivirus solution
for Suse Linux that is based on TMCM + ServerProtect for Linux 2.5.
Hardware
Server
Server software
TrendMicro Control Manager

(TMCM)
Client software
ServerProtect for Linux 2.5
Purchased by the operator/

Provided by Huawei
Purchased by the operator/
Provided by Huawei
5.5 Appendix: Ethernet Adapter Binding Tool

The Ethernet adapter binding tool is used only for the GBAM. It provides independent IP
configuration scripts, binds Ethernet adapters, and changes the IP address of the external
network.
Context
The script file, netcfg and the configuration file, server.cfg must be saved in the same directory
of the GBAM. Commands are run in the directory to bind Ethernet adapters and change the IP
address of the external network. The Ethernet adapter binding tool must be used on the standard
GBAM.
The standard GBAM must meet the following requirements:
l
The GBAM requires two internal Ethernet adapters and one or two external Ethernet
adapters. The model of the Ethernet adapters can only be one of the following combinations
listed in Table 5-7.
Table 5-7 Combinations of Ethernet adapters on the GBAM
Issue 08 (2012-02-27)
Combina
tion
Internal Ethernet Adapter

Model

Model
Intel Corporation 82546 GB

Gigabit Ethernet Controller (rev 03)
Intel Corporation 82545GM

Intel Corporation 82546 EB Gigabit

Ethernet Controller (Copper) (rev
01)
Intel Corporation 82545GM


233
BSC6900 GSM
Combina
tion
Internal Ethernet Adapter

Model

Model

01)
VIA Technologies, Inc. VT6105

01)
Intel Corporation 82546EB Gigabit

Ethernet Controller (rev 01)
The kernel version of the GBAM operating system is 2.6.5-7.244-smp.

NOTE
To view the Ethernet adapter model of the GBAM, run the lspci | grep "Ethernet Controller"
command.
To view the kernel version of the GBAM operating system, run the uname -r command.
Procedure
l
Obtain the Ethernet adapter binding tool and save it to the /BSC6000/install directory of
the GBAM.
1.
Visit http://support.huawei.com/support/. Choose Software Center > Controlled

Tool > Wireless Product Line > GSM BSS Tool > Ethernet Adapter Binding Tool
of the GBAM to download the compressed package file, Ethernet Adapter Binding
Tool of the GBAM.rar, save the file to the local disk, and decompress it for the script
file, netcfg and the configuration file, server.cfg.
NOTE
Assume the script file, netcfg and the configuration file, server.cfg are saved in the root directory
of local disk D. The operation is as follows:
Issue 08 (2012-02-27)
2.
Log in to the OMU through the psftp software. For details about the psftp software,
see 4.4.1 psftp Software.
3.
Run the lcd D:\ command to go to the directory on the local PC where Netcfg.rar is
saved.
4.
Run the cd /BSC6000/install command to go to the OMU installation directory.
5.
Run the put netcfg to upload netcfg to the BSC6000/install path of the GBAM.
6.
Run the put server.cfg to upload server.cfg to the BSC6000/install path of the
GBAM.
7.
After the uploading is complete, enter the exit command to exist the psftp software.
8.
Log in to the GBAM by referring to Logging In to the GBAM. Run the ls /BSC6000/
install command to check that the script file, netcfg and the configuration file,
server.cfg are both in the /BSC6000/install path.
Bind the Ethernet adapters with the Ethernet adapter binding tool of the GBAM
1.
Log in to the GBAM by referring to Logging In to the GBAM.
2.
3.
Run the cd /BSC6000/install command to change the current directory to /BSC6000/

install.
4.
Run the ./netcfg bond command to bind the Ethernet adapters.

234
BSC6900 GSM
5.
After the Ethernet adapters are bound, the system prompts you to set the IP address
of the external network. You may enter y or n to select operations.
If you enter y, you need to set the IP address, subnet mask, and gateway of the
external network.
If you enter n, the IP address of the external network is the default IP address,
192.168.1.1 (255.255.255.0).
CAUTION
The IP address of the external network is set according to the on-site planning. The
IP address of the external network, however, cannot be located in the network segment,
80.*.*.*, for the network segment is assigned to the internal network of the GBAM.
l
Change the IP address of the external network.

1.
Log in to the GBAM by referring to Logging In to the GBAM.
2.
3.
Run the cd /BSC6000/install command to change the current directory to /BSC6000/

install.
4.
Run the ./netcfg command to change the IP address of the external network.
5.
As Figure 5-31 shows, enter the IP address, subnet mask, and default gateway of the
external network.
6.
As Figure 5-31 shows, after checking the input, type y, and press Enter. Then the
network restarts.
Figure 5-31 Changing the IP address of the external Ethernet adapter
----End
Issue 08 (2012-02-27)

235
BSC6900 GSM

5.6.1 Record Sheet of OMU Software Installation Information

During OMU installation, the software records information regarding the parameter
configurations.
Record Sheet of OMU Operating System Installation Information

Item
Factory Settings
Common user name
bsc6000
Common user
password
11111111
Root user password
11111111
FtpUsr user
password
8anYwhERe8
Version of the iPSI

SEK SetSuse
software
V100R002C01B509
System enhancement
policies of iPSI SEK
SetSuse
Default policies
Setting
Information
Installation
Personnel
For details, see Record Sheet of OMU Operating System Installation Information (Upgrade
from BSC6000 to BSC6900).
Record Sheet of OMU Ethernet Adapter Teaming Information
Issue 08 (2012-02-27)
Item
Factory Settings
Internal Ethernet
adapter teaming
(ETH4-SCU7 and
ETH5-SCU6)
Teamed as bond0 in
the "balance-rr"
mode
ETH2
192.168.1.1
(255.255.255.0)
Setting
Information

Installation
Personnel
236
BSC6900 GSM
Item
Factory Settings
External Ethernet
adapter teaming
(ETH0 and ETH1)
Teamed as bond1 in
the "balance-rr"
mode
Setting
Information
Installation
Personnel
For details, see Record Sheet of OMU Ethernet Adapter Teaming Information (Upgrade
from BSC6000 to BSC6900).
Record Sheet of Samba Service Installation Information

Item
Factory Settings
Samba user name
bsc6000
Samba user
password
11111111
Samba file directory
/BSC6000
Setting
Information
Installation
Personnel
For details, see Record Sheet of Samba Service Installation Information (Upgrade from
BSC6000 to BSC6900).
5.6.2 Checklist for the Factory Settings of the OMU Software

This section provides a checklist for the factory settings of the OMU software. The checklist
records the installed OMU software and the software configurations before delivery.
Checklist for the Factory Settings of the OMU Software

Item
Whether Installed or Set
Remarks
Setting BIOS for the OMUb

board
Y; N
Set the OMUb board to be

started through the network.
Installing Suse Linux

Enterprise Server 9.0 SP3
Y; N
Root user password:

11111111
Setting the Ethernet adapters
Y; N
l ETH4-SCU7 and ETH5SCU6 are Teamed as

bond0 in the "balance-rr"
mode.
l ETH2: 192.168.1.1
(255.255.255.0)
l ETH0 and ETH1 are
teamed as bond1 in the
"balance-rr" mode.
Issue 08 (2012-02-27)

237
BSC6900 GSM
Item
Whether Installed or Set
Remarks
Setting time for the OMUb

board
Y; N
Current time
Setting the Samba service
Y; N
User name/password:
bsc6000/11111111
For details, see Checklist for the Factory Settings of the OMU Software (Upgrade from
BSC6000 to BSC6900).
5.6.3 List of the Factory Configuration of the OMU Software and

Hardware
This list records the factory configuration of the OMU software and hardware.
List of the Factory Configuration of the OMU Software and Hardware

Hardware/Software
Quantity
Remarks
OMUb board
One (standard configuration) Delivery-attached
EasyInstall and drive

software CD
One
Delivery-attached or
obtained from http://
support.huawei.com/
support/.
Suse Linux Enterprise Server

9.0 CD (32 bits)
Six
Delivery-attached
Suse Linux Enterprise Server

9.0 SP3 CD
Three
Delivery-attached
OMUb serial cable
One
Delivery-attached
For details, see List of the Factory Configuration of the OMU Software and Hardware
(Upgrade from BSC6000 to BSC6900).

This section lists the mapping between the enabled ports on the OMU and the services provided
by the OMU applications.
Issue 08 (2012-02-27)

238
BSC6900 GSM
Enabled Ports on the OMU
Issue 08 (2012-02-27)
Port No.
Service Process
Description
20
FTP Server data
Port for host loading, and uploading and

downloading of software and logs (in active
mode)
21
FTP Server control

downloading of software and logs
22
SSHD (operating
system service)
SSH port for remotely logging in to the OMU
1024-65535
FTP Server data

downloading of software and logs (in passive
mode)
80
Web LMT
Port connected to the LMT for local

maintenance of the BSC6900
123
sntp
Port that synchronizes the time of the OMU with

that of the server and provides local interception
443
Web LMT
Port used to establish an encryption connection

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

and an NE, therefore achieving NE maintenance
3306
Port for the database
6000
ems_gate
6001
ems_gate
Port for the alarm console
6006
ems_gate
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)
8099
ems_gate
Port for configuration change informing

message. This port is connected only to the
M2000. (SSL encryption)

239
BSC6900 GSM
Port No.
Service Process
Description
8100
ems_gate
Port for the alarm box (SSL encryption)
8200
ems_gate
Port for the VNP (SSL encryption)(Reserved

port, which is not supported in the current
version)
11775
monitor
Port for monitoring the external network

heartbeat between the active/standby OMU and
peripheral equipment
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 BSC6000 to BSC6900).
Issue 08 (2012-02-27)

240
BSC6900 GSM
Appendix: Troubleshooting
About This Chapter

This chapter describes OMU faults and troubleshooting methods.
6.1 Prohibiting Dark Screen and Startup Animation
This section describes how to prohibit dark screen and startup animation of the OMU so that the
fault of the OMU can be located quickly if any.
6.2 Restoring the Server Through the OMU Troubleshooting Tool
This describes how to back up and restore the operating system of the server and the configuration
data, and modify the password for user root through the OMU troubleshooting tool.
Issue 08 (2012-02-27)

241
BSC6900 GSM
6.1 Prohibiting Dark Screen and Startup Animation

This section describes how to prohibit dark screen and startup animation of the OMU so that the
fault of the OMU can be located quickly if any.
Context
l
This operation needs to be performed only once after the Suse Linux operating system is
installed.
When the keyboard and mouse are not in use for a long time, the system automatically
starts dark screen to save power and protect the screen. When the kernel breaks down, the
information about the kernel is displayed on the screen. The information, however, cannot
be seen when the screen is dark. Therefore, you cannot locate the fault.
When the Suse Linux operating system is started, the logo of the Suse Linux operating
system is displayed by default, and the loading information is shielded. You can press F2
to cancel the startup animation and view the loading information. If the Suse Linux
operating system breaks down, however, you cannot view the loading information.
Prohibit dark screen
Procedure
1.
2.
Run the cd /etc/init.d/ command to go to the directory where the boot.local file is
saved.
3.
Run the vi boot.local command to open the file.
4.
Press to move the cursor to the last line of the file.
5.
Type the :a command and then press Enter to edit the file.
6.
Type the printf "\033[9;0]" > /dev/console command and press Enter.
7.
Type the printf "\033[13]" > /dev/console command and press Enter.
8.
Press Esc to quit editing the file.
9.
Type the :w command and press Enter to save the settings.
10. Type the :q command and press Enter to quite editing the boot.local file. The dark
screen is prohibited.
11. Log out of the OMU by referring to Logging Out of the OMU.
l
Prohibit startup animation

1.
2.
Run the cd /boot/grub/ command to go to the directory where the menu.lst file is
saved.
3.
Run the vi menu.lst command to open the file.
4.
Type the /splash command and press Enter to view the value of splash.
If the value of splash is 0, you can infer that the startup animation is prohibited.
Go to Step 9.
If the value of splash is not 0, you can infer that the startup animation is not
prohibited. Go to Step 5.
5.
Issue 08 (2012-02-27)
Press Insert to edit the file.

242
BSC6900 GSM
6.
Press to move the cursor to the position behind splash=. Delete the existing value,
type 0, and then press Enter.
7.
Press Esc to quit editing the file.
8.
Type the :w command and press Enter to save the settings.
9.
Type the :q command and press Enter to quite editing the menu.lst file. The startup
animation is prohibited.
10. Log out of the OMU by referring to Logging Out of the OMU.
----End
6.2 Restoring the Server Through the OMU

Troubleshooting Tool
This describes how to back up and restore the operating system of the server and the configuration
data, and modify the password for user root through the OMU troubleshooting tool.
Prerequisites
l
The user has basic knowledge of the Linux operating system and the server hardware.
The LMT PC supports the DVD drive and is started by the CD drive.
The DVD of the OMU troubleshooting tool is available.
The Ethernet cable is long enough to connect the LMT PC and the server.
The free space in the hard disk (in NTFS or FAT format) of the LMT PC should not be
smaller than 3 GB when data backup is required.
The first Ethernet adapter is determined among multiple Ethernet adapters of the LMT PC.
Download the source files of the OMU troubleshooting tool to make the DVD:
Context
Issue 08 (2012-02-27)
1.
Visit the website http://support.huawei.com/support/.
2.
Choose Front Page > Software > Version Software > Wireless Product Line >
GSM-BSS > GBSS O&M tools, and download GSM BSC6000 fixomu-3.1beta4.part1 to GSM BSC6000 fixomu-3.1-beta4.part4 (total four files) and save
them in one folder.
3.
After the downloading is complete, double-click GSM BSC6000 fixomu-3.1beta4.part1 to decompress the file whose name is GSM BSC6000 fixomu-3.1beta4.iso.
4.
Use the CD recorder supporting DVD recording to make CD of the OMU

troubleshooting tool.
To determine the first Ethernet adapter among multiple Ethernet adapters of the LMT PC,
do as follows:
1.
Right-click My Computer and choose Properties from the shortcut menu.
2.
In the displayed Properties dialog box, click the Hardware tab. Then, click Device
Manager in the Device Manager area.
3.
In the Device Manager window, double-click Network adapters to expand the

network adapters available for use. Then, record the name of the first Ethernet adapter.
243
BSC6900 GSM
4.
Right-click My Network Places and choose Properties from the shortcut menu.
Then, the Network Connections window is displayed.
5.
Choose View > Details from the menu bar to display the specific information about
all the network connections.
6.
Determine the position of the first Ethernet adapter by pulling out and inserting the
Ethernet cable.
During the operation, the IP address of the LMT PC is 192.168.1.100, and the IP address
of the OMU/GBAM server is 192.168.1.110. The debugging IP address of the OMU/
GBAM server is 192.168.1.1, which takes effect after the operating system of the OMU/
GBAM server is restarted.
NOTE
l When an error occurs in the hard disk partitions of the OMU, run the gomu-part-setup command to
recreate the information about the hard disk partitions of the OMU.
l When an error occurs in the hard disk partitions of the GBAM, run the gbam-part-setup command to
recreate the information about the hard disk partitions of the GBAM.
Procedure
Step 1 Start the LMT PC.
1.
Set the LMT PC to be started by the CD driver in the BIOS.
2.
Place the CD of the OMU troubleshooting tool in the CD driver of the LMT PC to start the
LMT PC.
After the LMT PC is started, the IP address of the LMT PC is 192.168.1.100.
3.
The LMT PC loads the system integrated in the CD. When the message waiting is
displayed, the LMT is started successfully after five minutes.
NOTE
You can press Alt+F1 and Alt+F2 to switch between operation objects during the waiting time.
Do not press Ctrl+C to stop the running of the program when waiting for starting the LMT.
4.
Pull all the Ethernet cables out of the OMU/GBAM server.
5.
Use an Ethernet cable to connect the LMT PC to the server.

l The Ethernet cable is connected to the first Ethernet adapter of the LMT PC.
l If the server is GBAM, the Ethernet cable is connected to the first Ethernet adapter of
the GBAM.
l If the server is OMU, the Ethernet cable is connected to the ETH2 Ethernet adapter of
the OMU.
Step 2 Start the server.

1.
Reset the OMU by pulling the ejector lever or reset the GBAM server by pressing the reset
button.
NOTE
l To reset the OMU, do as follows: Turn outwards the ejector levers of the OMU until the OFFLINE
LED is ON steadily. Then, turn inwards the ejector levers to start the OMU automatically.
l Do not press the RESET or SHUTDOWN button on the panel of the OMU to reset or power off the
OMU.
2.
Issue 08 (2012-02-27)
The server starts in PXE mode by default. The LMT PC displays how the system integrated
in the CD of the OMU troubleshooting tool starts the server. When Figure 6-1 is displayed,
it indicates that the server starts successfully.
244
BSC6900 GSM
Figure 6-1 Successful startup of the server
NOTE
If the message I'M READY, as shown in Figure 6-1, is not displayed within five minutes, reset the
server.
Step 3 Log in to the server.

1.
Run the ssh root@192.168.1.110 command under the command prompt root@fixomu /
root %, and then press Enter to log in to the OMU/GBAM server.
2.
When the message Are you sure you want to continue connecting (yes/no)? is displayed,
as shown in Figure 6-2, enter yes.
3.
When the system prompts you to enter the password, as shown in Figure 6-2, enter the
password 11111111. When the command prompt fixomu~# is displayed, it indicates that
you have logged in to the server successfully.
Figure 6-2 Successful login of the server
NOTE
l If the command prompt is root@fixomu /root %, it indicates that the operation on the LMT is
performed currently.
l If the command prompt is fixomu~#, it indicates that the operation on the OMU/GBAM server
is performed currently.
l You can press Alt+Fn (n is 1, 2, 312) to switch between operation objects.
Step 4 Back up data.

NOTE
You need to back up the data in the BSC6000 folder and restore it in the new server only when the server
or operating system is corrupted or when the GBAM/OMU server should be replaced. The data backup is
not required when the BSC6000 of the new version is installed. The following substeps describe how to
backup data.
Issue 08 (2012-02-27)

245
BSC6900 GSM
1.
Run fdisk -l under the command prompt root@fixomu /root % to check the hard disk
partitions of the LMT PC.
2.
Select a hard disk partition (take /dev/hda6 as an example) of the LMT PC under the
command prompt root@fixomu /root % as a space for mounting backup data.
l If /dev/hda6 is partitioned in NTFS format, run the ntfs-3g /dev/sda6 /mnt/windows
command to mount data and use the mount directory as a backup directory at the same
time.
l If /dev/hda6 is partitioned in FAT or LINUX format, run the mount /dev/hda6 /mnt/
windows command to mount data and use the mount directory as a backup directory at
the same time.
3.
Run the ssh root@192.168.1.110 command, and then press Enter to log in to the OMU/
GBAM server.
4.
Run the image-backup data/mnt/windows command to back up data.

NOTE
Run the image-backup -h command under the command prompt fixomu~# to query the command
format.
5.
After the data backup, run the exit command under the command prompt fixomu~# to exit
from the OMU/GBAM server.
6.
Run the ls /mnt/windows command under the command prompt root@fixomu /root %
to query the backup data.
Step 5 Back up data, operating system, and software.

NOTE
If data is not backed up, you should not run the restore command to restore data of the system. That is, you
can skip Substep Step 5.1 through Substep Step 5.3. Only the system and software need to be restored. If
the version of the OMU software is a latest one, you are not advised to restore the software.
1.
Under the command prompt root@fixomu /root %, mount the space for backing up data.
Take /dev/hda6 as an example.
l If the hard disk is partitioned in NTFS format, run the ntfs-3g /dev/sda6 /mnt/
windows command to mount the space for backing up data.
l If the hard disk is partitioned in FAT or LINUX format, run the mount /dev/hda6 /mnt/
windows command to mount the space for backing up data.
2.
Run the cd /mnt/windows command under the command prompt root@fixomu /root %
to open the backup directory.
3.
Run the mv sda8.000 sda8 command under the command prompt root@fixomu /root
% to modify the name of the backup file. Modify the names of other backup files
accordingly.
4.
Run the ssh root@192.168.1.110 command, and then press Enter to log in to the OMU/
GBAM server.
5.
Run the image-restore <server type> <backup data type> <backup directory>
command under the command prompt fixomu~# to restore the backup data of the server.
Issue 08 (2012-02-27)

246
BSC6900 GSM
NOTE
l If the server is OMU, the server type is omu.

l If the server is GBAM, the server type is bam.
l The backup data involves the following types:
l data specifies the configuration data of the OMU.
l software specifies the application software.
l system specifies the operating system.
l If the backup directory is not specified, use the default file restoration system on the CD of
the OMU troubleshooting tool and then set the debugging IP address of the OMU/GBAM
server to 192.168.1.1 and the password for user root to 11111111.
Step 6 Reset the password for user root (optional).

1.
Run the passwd-setup command under the command prompt fixomu~# to modify the
password of the OMU/GBAM server.
2.
Run the reboot command under the command prompt fixomu~# to reset the OMU/GBAM
server.
3.
Disconnect the OMU/GBAM server from the LMT PC and then connect the OMU/GBAM
server to the network. The server restoration by the OMU troubleshooting tool is complete.
----End
Follow-up Procedure
l
Log in to the server through the PuTTY to check whether all the directories are restored.
If the directories are incorrect, run the fdisk command to modify the hard disk partitions.
Restart the OMU software progress to check whether the OMU software starts successfully.
If the OMU software fails to start, reinstall the OMU software.
Log in to the LMT to check whether the server data is consistent with the LMT data. If the
data is inconsistent, reconfigure data on the BSC.
Issue 08 (2012-02-27)

247
BSC6900 GSM
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 remote login to security-harden the BSC6900.
This section describes how to disable OMU route forwarding to security-harden the BSC6900.
Issue 08 (2012-02-27)

248
BSC6900 GSM

This section describes how to disable root user remote login to security-harden the BSC6900.
Prerequisites
l
The currently-running software version is BSC6900V900R013C00SPH529 or later.
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 remote login

NOTE
l Ensure that a new non-root user account has been created before disabling root user remote login.
Otherwise, the operation fails.
l After root user remote login is disabled, the current user will not be logged off automatically. A new
login will be disabled.
Issue 08 (2012-02-27)
1.
Log in to the OMU as a root user. For details, see Logging In to the OMU.
2.
Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the

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 excutable.
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.
Adding a non-root user account

1.
Log in to the OMU as a root user.
2.
Enter the useradd 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.

249
BSC6900 GSM
WARNING
The information of the added non-root user account must be kept. If this information
is lost and the root user remote login is disabled, you cannot log in to the OMU
remotely. In this situation, you must connect a PC to the debugging port of the OMU
and log in to the OMU as the root user to add a non-root user or use a USB storage
device to reinstall the operating .
l
Changing password for non-root user

1.
Log in to the OMU as a non-root user.
2.
Enter the command passwd and press Enter. You are prompted to enter the password.
3.
Enter the non-root user password. The non-root user password is changed.
Switching from a non-root user account to a root user account

1.
2.
Enter the command su and press Enter. You are prompted to enter the password.
3.
Enter the root user password and press Enter to switch the user account from a nonroot to root user.
Querying user information on the OMU

1.
Log in to the OMU as a non-root or root user.
2.
Enter the cat /etc/passwd command and press Enter to query the information of all
users.
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.
1.
Log in to the OMU as a non-root 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.
l
Enabling root user remote login

1.
2.
Switch the account of a non-root user to that of a root user.
3.

directory where the root_login.sh script is saved.
4.
root_login.sh script excutable.
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.
Querying the status of the root user login

1.
Issue 08 (2012-02-27)
Enter the userdel command and User Name. Then, press Enter to delete the account.

250
BSC6900 GSM
2.
Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to swith the

current directory to the directory where the root_login.sh script is saved.
3.
root_login.sh script executable.
4.
Enter the ./root_login.sh status command and press Enter to query the status of the
root user remote login.
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 remote login is enabled. disabled indicates that the root user
remote login is disabled.
----End
Example
The following is used as an example for disabling root user remote login 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
omucc_68
Changing
New UNIX
/ # useradd omu123
/ # passwd omu123
password for omu123.
password: Retype new UNIX password:
The following is used as an example for changing password for non-root 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 a non-root to root user.
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 omu123
Issue 08 (2012-02-27)

251
BSC6900 GSM
The following is used as an example for enabling root user remote login 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
omucc_68 /mbsc/bam/version_a/bin/bam #
done
The following is used as an example for querying the status of the root user remote login.
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 remote login.

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

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.
l
Issue 08 (2012-02-27)
1.
Log in to the OMU as a root user. For details, see Logging In to the OMU.
2.

directory where the ip_forward.sh script is saved.
3.
ip_forward.sh script excutable.
4.
Enter the ./ip_forward.sh disable command and press Enter to disable the OMU
route forwarding.
Enable OMU route forwarding.

252
BSC6900 GSM
1.
2.

3.
4.
Enter the ./ip_forward.sh enable command and press Enter to enable the OMU route
forwarding.
Querying the status of OMU route forwarding

1.
2.

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

omucc_68
omucc_68
omucc_68
Enabling
~ # cd /mbsc/bam/version_a/bin/bam
/mbsc/bam/version_a/bin/bam # chmod +x ip_forward.sh
/mbsc/bam/version_a/bin/bam # ./ip_forward.sh enable
ip forward
done
The following is used as an example for querying the status of 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 status
Configuration status: enabled
Actual status: enabled
Follow-up Procedure
1.
Issue 08 (2012-02-27)
Record the status of OMU route forwarding.

253
BSC6900 GSM
Appendix: Special OMU Networking

Scenarios
About This Chapter

This section describes the special scenarios of connecting the OMU to peripheral equipment.
This section describes how to modify the connection between the OMU and Vendor Network
Probe (VNP) if the BSC6900 supports the GBFD-511701 Radio Measurement Data Interface
for Navigation feature.
Issue 08 (2012-02-27)

254
BSC6900 GSM

This section describes how to modify the connection between the OMU and Vendor Network
Probe (VNP) if the BSC6900 supports the GBFD-511701 Radio Measurement Data Interface
for Navigation feature.
Figure 8-1 shows the connection between the OMU and VNP.
Figure 8-1 Connection Between the OMU and VNP
Scenario 1: using the virtual external IP address of the OMU

In this scenario, the virtual external IP address of the OMU is used for communication between
the OMU and VNP. The following are detailed descriptions.
l
The VLAN that the M2000 belongs to and the VLAN that the VNP belong to can be
accessed by using the same VLAN ID.
BSC6900 is communicating with the M2000 and VNP by using the virtual IP address of
the OMU external network.
For configuration restrictions on the virtual external IP address of the OMU, see 3.2 Planning
of the OMU IP Addresses. For how to configure that IP address, see Changing IP Addresses
and Masks of the OMU Ethernet Adapters.
Scenario 2: using the BSC local IP address

In this scenario, the BSC local IP address is used for communication between the BSC and VNP.
l
The M2000 and VNP can be configured in different LANs.
The BSC local IP address for communication between the BSC6900 and VNP must be
configured on the OMU.
Issue 08 (2012-02-27)

255
BSC6900 GSM
BSC6900 communicates with the M2000 by using the virtual IP address of the OMU
external network and with the VNP by using the BSC local IP address.
BSC local IP address

The BSC local IP address for communication between the BSC6900 and VNP is configured on
the external Ethernet adapter team of the OMU.
Figure 8-2 and Figure 8-3 show the binding relationship between Ethernet adapters of the OMU
board.
NOTE
VLANs vlan2 and vlan3 in Figure 8-2 and Figure 8-3 are used as examples. The VLAN IDs depend on the
actual configuration.
Figure 8-2 Binding relationship between Ethernet adapters of the OMUa board
Description of the binding relationship between Ethernet adapters of the OMUa board
l
ETH4-SCU7 and ETH5-SCU6 are bound as an internal Ethernet adapter team, bond0.
Vlan1 is established on bond0 for communication between the OMU and SCU. Vlan1 and
vlan1:0 are corresponding to the fixed and virtual internal IP addresses of the OMU
respectively.
ETH0 and ETH1 are bound as an external Ethernet adapter team, bond1. Vlan3 and vlan4
are established on bond1 for communication between the OMU and the M2000 and VNP.
Vlan2 and vlan2:0 are corresponding to the fixed and virtual external IP addresses of the
OMU respectively while vlan3 is corresponding to the BSC local IP address.
ETH2 (bond2), a debugging Ethernet adapter, is connected to a portable PC for OMU

debugging if required.
ETH3-UPDATE (bond3), a backup Ethernet adapter, is used as the backup channel between
the active and standby OMUs when the BSC6900 is configured with two OMUa boards.
Issue 08 (2012-02-27)

256
BSC6900 GSM
Figure 8-3 Binding relationship between Ethernet adapters of the OMUc board
Description of the binding relationship between Ethernet adapters of the OMUc board
l
B_ETH0 and B_ETH1 are bound as an internal Ethernet adapter team, bond0. Vlan1 is
established on bond0 for communication between the OMU and SCU. Vlan1 and vlan1:0
are corresponding to the fixed and virtual internal IP addresses of the OMU respectively.
F_ETH0 and F_ETH1 are bound as an external Ethernet adapter team, bond1. Vlan3 and
vlan4 are established on bond1 for communication between the OMU and the M2000 and
VNP. Vlan2 and vlan2:0 are corresponding to the fixed and virtual external IP addresses
of the OMU respectively while vlan3 is corresponding to the BSC local IP address.
F_DBG (bond2), a debugging Ethernet adapter, is connected to a portable PC for OMU

debugging if required.
B_UPDATE0 serves as a backup Ethernet adapter between the OMUc boards. When the
BSC6900 is configured with two OMUc boards, this Ethernet adapter works as a dedicated
backup channel between the active OMU and the standby OMU.
B_UPDATE1 serves as a backup Ethernet adapter between the OMUc board and the
OMUa/OMUb board. When the BSC6900 is configured with one OMUc board and one
OMUa/OMUb board, this Ethernet adapter works as a dedicated backup channel between
the active OMU and the standby OMU.
BSC local IP address:

l
The BSC local IP address is null by default. The BSC local IP address requires to be
configured only if the feature GBFD-511701 Radio Measurement Data Interface for
Navigation is enabled on the BSC6900 and the prerequisites in scenario 2 are met.
If active and standby OMUs are switched over when a VNP communicates with the OMU
using the BSC local IP address, the communication will be interrupted for a while and then
be recovered automatically. During this process, the BSC local IP address of the original
standby OMU starts to take effect, and the BSC local IP address of the original active OMU
becomes ineffective.
Restrictions on configuring the BSC local IP address:

l
Issue 08 (2012-02-27)
The network segment of the BSC local IP address must be different from that of the
following IP addresses: fixed and virtual internal IP addresses of the OMU, debugging IP
address, and backup channel IP address of the active and standby OMUs.
257
BSC6900 GSM
Impact of deleting or changing the BSC local IP address:

l
After the BSC local IP address is deleted or changed, the VNP connected to the OMU
through the original IP address cannot access the OMU unless through a new BSC local IP
address.
The BSC local IP address can be changed remotely, and the new IP address takes effect
immediately.
For details about configuring the BSC local IP address, see Configuring Radio Measurement
Data Interface for Navigation in GBSS Feature Activation Guide.
Issue 08 (2012-02-27)

258

Bsc6900 GSM Omu Administration Guide v900r013c00 08 PDF en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Bsc6900 GSM Omu Administration Guide v900r013c00 08 PDF en

Uploaded by

Copyright:

Available Formats

BSC6900 GSM

OMU Administration Guide

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2012. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

Huawei Proprietary and Confidential

About This Document

4 Scenario: Creating a BSC6900 NE

Times New Roman

Normal paragraphs are in Times New Roman.

Huawei Proprietary and Confidential

About This Document

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

Book titles are in italics.

Examples of information displayed on the screen are in

The keywords of a command line are in boldface.

Command arguments are in italics.

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

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

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

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

Huawei Proprietary and Confidential

About This Document

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

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

Select and release the primary mouse button without moving

Press the primary mouse button twice continuously and

Huawei Proprietary and Confidential

3 Working Principles of the OMU..............................................................................................37

Huawei Proprietary and Confidential

3.3 OMU Networking Principle.............................................................................................................................54

4 Scenario: Creating a BSC6900 NE.............................................................................................71

5 Scenario: Upgrade from the BSC6000 to the BSC6900........................................................147

Huawei Proprietary and Confidential

5.2.3 Querying the Version of the Active/Standby OMU Workspaces..........................................................175

7 Appendix: Security FAQ..........................................................................................................248

Huawei Proprietary and Confidential

8 Appendix: Special OMU Networking Scenarios................................................................ 254

Huawei Proprietary and Confidential

1 Changes in the BSC6900 GSM OMU Administration Guide

Changes in the BSC6900 GSM OMU

4.3.6 Setting RAID 1 on the OMU Hard

Descriptions about using the external

7.1 Disabling root user remote login

The method of modifying a non-root user's

l Scenario: Creating a BSC6900 NE

The method of modifying passwords of root,

Changing the admin password

Descriptions about checking whether the

l Scenario: Upgrade from the BSC6000 to

Huawei Proprietary and Confidential

1 Changes in the BSC6900 GSM OMU Administration Guide

l Scenario: Creating a BSC6900 NE

Notes on ports 6099, 8099, 16002 and 18002

4.5.3 Enabled Ports on the OMU