OMU Administration Guide

BSC6900 GSM
V900R012C01
OMU Administration Guide
Issue 01
Date 2010-04-10
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any
assistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com

Copyright Huawei Technologies Co., Ltd. 2010. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions
and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Proprietary and Confidential
Contents
About This Document.....................................................................................................................1
1 Changes in the BSC6900 GSM OMU Administration Guide...........................................1-1
2 Introduction to OMU.................................................................................................................2-1
2.1 Position of the OMU in the BSC6900.............................................................................................................2-2
2.2 OMUa/OMUb Board.......................................................................................................................................2-2
2.2.1 Functions of the OMUa/OMUb Board...................................................................................................2-3
2.2.2 Panel of the OMUa/OMUb Board.........................................................................................................2-3
2.2.3 Ports on the OMUa/OMUb Board.........................................................................................................2-5
2.2.4 LEDs on the OMUa/OMUb Board........................................................................................................2-5
2.2.5 Technical Specifications of the OMUa/OMUb Board...........................................................................2-6
2.2.6 Replacing an OMU Board......................................................................................................................2-7
2.3 GBAM...........................................................................................................................................................2-13
2.3.1 Functions of GBAM.............................................................................................................................2-13
2.3.2 Physical Appearance of the GBAM (IBM X3650T)...........................................................................2-13
2.3.3 Physical Appearance of the GBAM (HUAWEI C5210)......................................................................2-16
2.3.4 Physical Appearance of the GBAM (HP CC3310)..............................................................................2-19
2.3.5 Technical Specifications and Counters of the GBAM.........................................................................2-22
2.3.6 Replacing the GBAM...........................................................................................................................2-24
2.4 OMU Software..............................................................................................................................................2-29
2.4.1 OMU Application Structure.................................................................................................................2-29
2.4.2 OMU Service Monitoring Entities.......................................................................................................2-30
2.4.3 OMU Service Processes.......................................................................................................................2-31
2.5 OMU Working Mode....................................................................................................................................2-33
2.6 OMU OM Methods.......................................................................................................................................2-33
2.7 OMU Safety Information..............................................................................................................................2-35
3 Working Principles of the OMU.............................................................................................3-1
3.1 OMU Ethernet Adapter Configuration............................................................................................................3-2
3.2 Planning of the OMU IP Addresses................................................................................................................3-6
3.3 OMU Networking Principle..........................................................................................................................3-13
3.4 Heartbeat Test on Active/Standby OMUs.....................................................................................................3-17
3.5 Synchronization Between the Active OMU and the Standby OMU.............................................................3-17
3.6 Switchover Between the Active and Standby OMUs...................................................................................3-17
BSC6900 GSM
OMU Administration Guide Contents
Issue 01 (2010-04-10) Huawei Proprietary and Confidential
i
4 Scenario: Creating a BSC6900 NE........................................................................................... 4-1
4.1 Installing the OMU Applications in Field Commissioning............................................................................4-3
4.1.1 Setting the Link Mode of the External OMU Ethernet Adapter............................................................4-3
4.1.2 Debugging OMU on Site........................................................................................................................4-5
4.2 Reinstalling Software on Site..........................................................................................................................4-8
4.2.1 Preparations for Installing Software on Site..........................................................................................4-9
4.2.2 Preparing the USB Installation Disk....................................................................................................4-10
4.2.3 Installing the Operating System Through the USB Installation Disk..................................................4-15
4.2.4 Optional: Installing the OMU Applications.........................................................................................4-17
4.3 Operating and Maintaining the OMU...........................................................................................................4-25
4.3.1 Querying the Configuration of the OMU Ethernet Adapters...............................................................4-26
4.3.2 Querying the Network Configuration of the OMU Ethernet Adapters................................................4-26
4.3.3 Checking the version of the Operating System....................................................................................4-27
4.3.4 Changing the IP Address of the OMU Ethernet Adapter Team...........................................................4-27
4.3.5 Changing the Administrator Password of the Operating System.........................................................4-29
4.3.6 Setting the 1st Boot Device of the OMU to USB................................................................................4-29
4.3.7 Maintaining the OMU Routinely.........................................................................................................4-31
4.3.8 Managing the Operating Status of the OMU.......................................................................................4-33
4.3.9 Managing the OMU Applications........................................................................................................4-39
4.3.10 Backing Up and Restoring Data.........................................................................................................4-42
4.3.11 Using the omutool..............................................................................................................................4-45
4.4 Appendix: OMU-Related Software...............................................................................................................4-51
4.4.1 psftp Software......................................................................................................................................4-51
4.4.2 PuTTY Software..................................................................................................................................4-53
4.5 Appendix: OMU-Related Information Tables..............................................................................................4-55
4.5.1 Records of OMU Software Installation Information............................................................................4-55
4.5.2 Checklist for the Factory Settings of the OMU Software....................................................................4-57
4.5.3 Enabled Ports on the OMU..................................................................................................................4-58
5 Scenario: Upgrade from the BSC6000 to the BSC6900........................................................5-1
5.1 Software Installation After the Upgrade.........................................................................................................5-3
5.1.1 Installing the Operating System.............................................................................................................5-3
5.1.2 Installing the OMU Applications...........................................................................................................5-3
5.2 Routine OMU Maintenance After the Upgrade..............................................................................................5-4
5.2.1 Regularly Checking and Cleaning Up the OMU Hard Disk..................................................................5-5
5.2.2 Transferring and Backing Up Files........................................................................................................5-5
5.3 OMU Operation and Maintenance After the Upgrade....................................................................................5-7
5.3.1 Querying the Operating Status of the OMU...........................................................................................5-9
5.3.2 Querying the Information About the OMUa Board.............................................................................5-10
5.3.3 Querying the Version of the Active/Standby OMU Workspaces........................................................5-11
5.3.4 Querying the Status of the Data Synchronization Between the Active OMU and the Standby OMU
.......................................................................................................................................................................5-11
5.3.5 Checking the Data Consistency Between the Active OMU and the Standby OMU............................5-12
Contents
BSC6900 GSM
ii Huawei Proprietary and Confidential
Issue 01 (2010-04-10)
5.3.6 Changing the OMU Time and Time Zone...........................................................................................5-12
5.3.7 Changing the Administrator Password of the Operating System.........................................................5-13
5.3.8 Switching Over the Active/Standby OMU Workspaces......................................................................5-13
5.3.9 Forcibly Switching Over the Active and Standby OMUs....................................................................5-14
5.3.10 Replacing the Public and Private Key Certificate Files.....................................................................5-15
5.3.11 Checking the Version of the Operating System.................................................................................5-15
5.3.12 Checking the OMU Hard Disk Partitions..........................................................................................5-16
5.3.13 Checking the OMU Memory Capacity..............................................................................................5-16
5.3.14 Checking the OMU Ethernet Adapter Teams....................................................................................5-17
5.3.15 Changing the Connection Mode of the OMU Ethernet Adapters......................................................5-19
5.3.16 Prohibiting Dark Screen and Startup Animation................................................................................5-21
5.3.17 Resetting the OMU.............................................................................................................................5-22
5.3.18 Shutting Down the OMU...................................................................................................................5-23
5.3.19 Managing the OMU Applications......................................................................................................5-24
5.3.20 Backing Up and Restoring Data.........................................................................................................5-26
5.3.21 Using the omutool..............................................................................................................................5-30
5.4 Appendix: the SEK SetSuse Software..........................................................................................................5-37
5.4.1 Installing the SEK SetSuse Software ..................................................................................................5-37
5.4.2 Rolling Back Security Enhancement Policies During the Use of the SEK SetSuse Software.............5-40
5.4.3 Uninstalling the SEK SetSuse Software...............................................................................................5-41
5.5 Appendix: Anti-Virus Software....................................................................................................................5-42
5.6 Appendix: Ethernet Adapter Binding Tool...................................................................................................5-43
5.7 Appendix: OMU-Related Information Tables..............................................................................................5-46
5.7.1 Record Sheet of OMU Software Installation Information...................................................................5-46
5.7.2 Checklist for the Factory Settings of the OMU Software....................................................................5-47
5.7.3 List of the Factory Configuration of the OMU Software and Hardware.............................................5-48
BSC6900 GSM
OMU Administration Guide Contents
iii
Figures
Figure 2-1 Position of the OMU in the BSC6900 OM Subsystem......................................................................2-2
Figure 2-2 Panel of the OMUa/OMUb board......................................................................................................2-4
Figure 2-3 Removing the OMU board...............................................................................................................2-10
Figure 2-4 Installing the OMU board.................................................................................................................2-11
Figure 2-5 GBAM (IBM X3650T).....................................................................................................................2-13
Figure 2-6 Front panel of the GBAM (IBM X3650T).......................................................................................2-14
Figure 2-7 Rear panel of the GBAM..................................................................................................................2-15
Figure 2-8 GBAM (HUAWEI C5210)...............................................................................................................2-16
Figure 2-9 Front panel of the GBAM (HUAWEI C5210).................................................................................2-17
Figure 2-10 Rear panel of the GBAM (HUAWEI C5210)................................................................................2-18
Figure 2-11 GBAM (HP CC3310).....................................................................................................................2-19
Figure 2-12 Front panel of the GBAM (HP CC3310)........................................................................................2-20
Figure 2-13 Rear panel of the GBAM (HP CC3310).........................................................................................2-21
Figure 2-14 Front panel of the power distribution box......................................................................................2-25
Figure 2-15 OMU Application Structure...........................................................................................................2-30
Figure 3-1 Mapping between the ETHxxx and the bondxxx on the OMUa Board.............................................3-2
Figure 3-2 Mapping between the ETHxxx and the bondxxx on the OMUb Board.............................................3-3
Figure 3-3 Location of Ethernet adapters on HUAWEI C5210 GBAM..............................................................3-4
Figure 3-4 Location of Ethernet adapters on IBM X3650T GBAM....................................................................3-4
Figure 3-5 Location of Ethernet adapters on HP CC3310 GBAM......................................................................3-5
Figure 3-6 IP addresses for three Ethernet adapters on the GBAM.....................................................................3-6
Figure 3-7 IP addresses for four Ethernet adapters on the GBAM......................................................................3-6
Figure 3-8 Onsite network....................................................................................................................................3-9
Figure 3-9 Single-OMUa/OMUb networking topology.....................................................................................3-14
Figure 3-10 Dual-OMUa/OMUb networking topology.....................................................................................3-15
Figure 3-11 GBAM networking topology..........................................................................................................3-16
Figure 4-1 OMU software structure.....................................................................................................................4-1
Figure 4-2 Querying the link mode of the Ethernet adapter (example)...............................................................4-4
Figure 4-3 U_creator_eng window.....................................................................................................................4-11
Figure 4-4 Add NE dialog box...........................................................................................................................4-12
Figure 4-5 Configuring information...................................................................................................................4-13
Figure 4-6 Add NE dialog box...........................................................................................................................4-14
Figure 4-7 Configuring information...................................................................................................................4-15
BSC6900 GSM
OMU Administration Guide Figures
v
Figure 4-8 Setting the run mode of product.......................................................................................................4-19
Figure 4-9 Setting the office name.....................................................................................................................4-20
Figure 4-10 Setting the language........................................................................................................................4-20
Figure 4-11 Setting the admin password............................................................................................................4-20
Figure 4-12 Setting the FTP password...............................................................................................................4-20
Figure 4-13 Setting the external virtual IP address............................................................................................4-20
Figure 4-14 Setting the OMU system type.........................................................................................................4-20
Figure 4-15 Confirming the installation.............................................................................................................4-21
Figure 4-16 Directory structure of OMU applications on the active workspace...............................................4-22
Figure 4-17 Directory structure of OMU applications on the active and standby workspaces..........................4-23
Figure 4-18 Factory settings of the OMU Ethernet adapters (example)............................................................4-26
Figure 4-19 Network configuration of the OMU Ethernet adapters (example).................................................4-27
Figure 4-20 Changing the password...................................................................................................................4-29
Figure 4-21 BIOS Setup.....................................................................................................................................4-29
Figure 4-22 Boot tab page..................................................................................................................................4-30
Figure 4-23 Selecting the 1st boot device..........................................................................................................4-31
Figure 4-24 Operation example..........................................................................................................................4-33
Figure 4-25 Starting the omu_backup_linker Tool............................................................................................4-42
Figure 4-26 Example..........................................................................................................................................4-43
Figure 4-27 Example..........................................................................................................................................4-45
Figure 4-28 Logging in to the OMU through the psftp software.......................................................................4-52
Figure 4-29 Entering the user name password...................................................................................................4-52
Figure 4-30 PuTTY Configuration dialog box...................................................................................................4-54
Figure 4-31 Logging in to the OMUa board through PuTTY software.............................................................4-55
Figure 5-1 OMU software structure.....................................................................................................................5-1
Figure 5-2 Operation example..............................................................................................................................5-7
Figure 5-3 Changing the password.....................................................................................................................5-13
Figure 5-4 Message (example)...........................................................................................................................5-15
Figure 5-5 Checking the OMU hard disk partitions...........................................................................................5-16
Figure 5-6 Checking the OMU memory capacity and usage (example)............................................................5-17
Figure 5-7 Configuration of the OMU Ethernet adapters (example).................................................................5-17
Figure 5-8 Mapping between the physical and logical Ethernet adapters..........................................................5-19
Figure 5-9 Connection setting of OMU Ethernet adapters.................................................................................5-20
Figure 5-10 Checking the connection setting of OMU Ethernet adapters.........................................................5-20
Figure 5-11 Starting the omu_backup_linker Tool............................................................................................5-27
Figure 5-12 Example..........................................................................................................................................5-28
Figure 5-13 Example..........................................................................................................................................5-30
Figure 5-14 Query result (an example)..............................................................................................................5-34
Figure 5-15 PuTTY software configuration.......................................................................................................5-38
Figure 5-16 Information about successful installation.......................................................................................5-39
Figure 5-17 Rollback of a specific policy (an example)....................................................................................5-40
Figure 5-18 Confirming the uninstallation of the SEK SetSuse software .........................................................5-41
Figures
BSC6900 GSM
vi Huawei Proprietary and Confidential
Issue 01 (2010-04-10)
Figure 5-19 Successful uninstallation of the SEK SetSuse software.................................................................5-42
Figure 5-20 Anti-Virus Software Networking...................................................................................................5-42
Figure 5-21 Changing the IP address of the external Ethernet adapter..............................................................5-45
BSC6900 GSM
OMU Administration Guide Figures
vii
Tables
Table 2-1 Ports on the OMUa/OMUb board........................................................................................................2-5
Table 2-2 LEDs on the OMUa/OMUb board.......................................................................................................2-5
Table 2-3 Hardware configuration indexes of the OMUa/OMUb board............................................................. 2-6
Table 2-4 Performance counters of the OMUa/OMUb board..............................................................................2-7
Table 2-5 Silkscreen labels on the front panel of the GBAM (IBM X3650T)...................................................2-14
Table 2-6 Silkscreen labels on the rear panel of the GBAM (IBM X3650T)....................................................2-16
Table 2-7 Silkscreen labels on the front panel of the GBAM (HUAWEI C5210).............................................2-17
Table 2-8 Silkscreen labels on the rear panel of the GBAM (HUAWEI C5210)..............................................2-19
Table 2-9 Silkscreen labels on the front panel of the GBAM (HP CC3310).....................................................2-20
Table 2-10 Silkscreen labels on the rear panel of the GBAM (HP CC3310).....................................................2-22
Table 2-11 Hardware configuration specifications of the GBAM (IBM X3650T)............................................2-22
Table 2-12 Hardware configuration specifications of the GBAM (C5210).......................................................2-23
Table 2-13 Hardware configuration specifications of the GBAM (HP CC3310)..............................................2-23
Table 2-14 Performance counters of the GBAM................................................................................................2-24
Table 2-15 Checklist for GBAM replacement...................................................................................................2-26
Table 3-1 Definitions of IP addresses of the OMU..............................................................................................3-7
Table 3-2 Onsite planning of OMU IP addresses...............................................................................................3-10
Table 3-3 Onsite checking of OMU IP addresses..............................................................................................3-11
Table 3-4 Impact of Changes of OMU IP Addresses.........................................................................................3-12
Table 4-1 Configuration requirements of the portable computer.........................................................................4-9
Table 4-2 Description.........................................................................................................................................4-21
Table 4-3 File folders of the OMU application directory...................................................................................4-23
Table 4-4 Commands frequently used on the FTP.............................................................................................4-32
Table 4-5 Commands frequently used on the psftp software.............................................................................4-51
Table 5-1 Commands frequently used on the FTP...............................................................................................5-6
Table 5-2 Combinations of Ethernet adapters on the GBAM ...........................................................................5-44
BSC6900 GSM
OMU Administration Guide Tables
ix
About This Document
Purpose
This document describes the software and hardware structure, software installation, GUI, and
operations concerning the OMUa board.
Product Version
The following table lists the product version related to this document.
Product Name Product Version
BSC6900 V900R012C01

Intended Audience
This document is intended for:
l Field engineers
l Shift operators
Organization
1 Changes in the BSC6900 GSM OMU Administration Guide
This describes the changes in the BSC6900 GSM OMU Administration Guide.
2 Introduction to OMU
The physical entity of the OMU is the OMUa board. The OMUa board 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 describes the operating principles of Ethernet adapters, related IP addresses, active and
standby workspaces, and active and standby OMUs.
BSC6900 GSM
OMU Administration Guide About This Document
1
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.
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.
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in
boldface. For example, log in as user root.
Italic Book titles are in italics.
Courier New Examples of information displayed on the screen are in
Courier New.

Command Conventions
The command conventions that may be found in this document are defined as follows.
About This Document
BSC6900 GSM
2 Huawei Proprietary and Confidential
Issue 01 (2010-04-10)
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[ ] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by
vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by
vertical bars. One item is selected or no item is selected.
{ x | y | ... }
*
Optional items are grouped in braces and separated by
vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]
*
Optional items are grouped in brackets and separated by
vertical bars. Several items or no item can be selected.

GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Boldface Buttons, menus, parameters, tabs, window, and dialog titles
are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"
signs. For example, choose File > Create > Folder.

Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.

Mouse Operations
The mouse operations that may be found in this document are defined as follows.
BSC6900 GSM
OMU Administration Guide About This Document
3
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Double-click Press the primary mouse button twice continuously and
quickly without moving the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
About This Document
BSC6900 GSM
4 Huawei Proprietary and Confidential
Issue 01 (2010-04-10)
1 Changes in the BSC6900 GSM OMU
Administration Guide
This describes the changes in the BSC6900 GSM OMU Administration Guide.
01(2010-04-10)
This is the first commercial release.
Compared with issue 04 (2010-01-30) of V900R011C00, this issue includes the following new
topics:
The new scenario:
l 4 Scenario: Creating a BSC6900 NE
l 5 Scenario: Upgrade from the BSC6000 to the BSC6900
Compared with issue 04 (2010-01-30) of V900R011C00, this issue incorporates the following
changes:
Topic Change Description
3.1 OMU Ethernet Adapter
Configuration, 3.3 OMU Networking
Principle
The description of configuration of Ethernet
adapters on the OMUb board and GBAM is
added.

Compared with issue 04 (2010-01-30) of V900R011C00, this issue does not exclude any topic.
BSC6900 GSM
OMU Administration Guide 1 Changes in the BSC6900 GSM OMU Administration Guide
1-1
About This Chapter
The physical entity of the OMU is the OMUa board. The OMUa board 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 describes the components of the BSC6900 OM subsystem and the position of the OMU in
the OM subsystem.
2.2 OMUa/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. Slots 24 to 27 are recommended.
2.3 GBAM
The BSC6900 uses three models of GBAM: IBM X3650T, HUAWEI C5210, and HP CC3310.
The GBAM is installed in the MPR.
2.4 OMU Software
OMU software refers to all the software running on the OMU.
2.5 OMU Working Mode
The OMU works in single-OMU or dual-OMU mode.
2.6 OMU OM Methods
This describes several scenarios and methods of the OMU OM.
2.7 OMU Safety Information
This describes the safety information related to OMU operation.
BSC6900 GSM
OMU Administration Guide 2 Introduction to OMU
2-1
2.1 Position of the OMU in the BSC6900
This 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/M2000, OMUa/OMUb board or
GBAM (OMU), SCUa board, and OM modules on 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
Figure 2-1 takes the OMUa board as an example. Both the OMUb board and GBAM can replace the OMUa
board.
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/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. Slots 24 to 27 are recommended.
BSC6900 GSM
2-2 Huawei Proprietary and Confidential
Issue 01 (2010-04-10)
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.
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.
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.
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.
2.2.5 Technical Specifications of the OMUa/OMUb Board
This section describes the hardware configuration indexes and performance counters of the
OMUa/OMUb board, including size, power supply, power consumption, weight, hard disk
capacity, memory capacity, working temperature, and working humidity.
2.2.6 Replacing an OMU Board
This section describes how to replace a faulty OMU board. The OMU board is hot-swappable.
It takes about 16 minutes to replace an OMU board.
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 board performs the following functions:
l Performs the configuration management, performance management, fault management,
security management, and loading management functions for the system
l 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.
BSC6900 GSM
2-3
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 (16) OFFLINE LED
(17) Hard disks (18) Screws for fixing the hard disk

BSC6900 GSM
Issue 01 (2010-04-10)
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 -

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
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.
BSC6900 GSM
2-5
LED Color Status Description
ALM Red OFF There is no alarm.
ON or blinking There is a fault alarm.
ACT Green ON The board is in active mode.
OFF The board is in standby mode, or the
board is disconnected.
OFFLINE Blue ON The board can be removed.
OFF The board cannot be removed.
ON for 0.125s and OFF
for 0.125s
The board is being switched over to
the other working mode.
HD Green OFF There is no read or write operation
on the hard disk.
Blinking The hard disk is being read or
written.

2.2.5 Technical Specifications of the OMUa/OMUb Board
This section describes the hardware configuration indexes and performance counters of the
OMUa/OMUb 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 of the OMUa/OMUb board.
Table 2-3 Hardware configuration indexes of the OMUa/OMUb board
Index Index of the OMUa Board Index of the OMUb Board
Size 366.7 mm x 220 mm 366.7 mm x 220 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)
Power consumption 120 W 90 W
Weight 4.0 kg 3.5 kg
Hard disk capacity 146 GB x 2 (RAID 1) 146 GB x 2 (RAID 1)
Memory capacity 2 GB 2 GB
Temperature required when
working for a long time
0C - +45C 0C - +45C
BSC6900 GSM
Issue 01 (2010-04-10)
Index Index of the OMUa Board Index of the OMUb Board
Temperature required when
working for a short time
-5C - +55C -5C - +55C
Relative humidity required
when working for a long time
5%-85% 5%-85%
Relative humidity required
when working for a short
time
5%-95% 5%-95%

Performance Counters
Table 2-4 describes the performance counters of the OMUa/OMUb board.
Table 2-4 Performance counters of the OMUa/OMUb board
Counter Index of the OMUa/OMUb Board
Number of recorded
alarms
The maximum number of recorded alarms is 150,000.
Time when the standby
OMU data is
synchronized with the
active OMU data
The standby OMU synchronizes its data with that of the active
OMU board every second.
Duration of the
synchronization between
the active OMU files and
standby OMU files
Five minutes. The time needed for the synchronization varies
according to the size and quantity of the files to be synchronized.
Duration of the
switchover between the
active and standby OMUs
Duration from when the request for OMU switchover is accepted
to when the switchover is finished. This duration lasts for two to
three minutes.
Duration of the OMU
restart
Duration of the OMU restart due to OMU fault. This duration
lasts for about three minutes.

2.2.6 Replacing an OMU Board
This section describes how to replace a faulty OMU board. The OMU board is hot-swappable.
It takes about 16 minutes to replace an OMU board.
Prerequisite
l The tools are ready. The tools are the ESD wrist strap, Phillips screwdriver, and ESD box
or bag.
BSC6900 GSM
2-7
l The LMT is started and communicates with the OMU properly. If the OMU board is faulty
and cannot communicate with other boards or the LMT, ensure that the version of the LMT
application program is consistent with the software version of the new OMU board.
l The USB installation disk with software and applications for the new OMU board is
prepared. For details, see 4.2.2 Preparing the USB Installation Disk. When configuring
the new OMU board, the following configurations are consistent with those of the OMU
board to be replaced:
Password for the administrator user of the Linux operating system
FTP server password
Administrator password
Internal and external network virtual IP addresses of the OMU board
Computer name of the OMU board
Operating system of the OMU board
Context
CAUTION
To protect the components from electrostatic discharge, wear an ESD wrist strap properly.
Ensure that the ESD wrist strap is properly connected to the ESD connector on the cabinet. If
no ESD wrist strap or no proper grounding point is available, wear ESD gloves.
CAUTION
Replacing the standby OMU board has no adverse impact on the system operation. Replacing
an OMU board that works independently, however, disrupts the communication between the
OMU and the host boards. In addition, the system operation data will be lost.
Procedure
Step 1 Display the subrack that houses the OMU board in the Device Panel on the LMT. Check the
configuration of the OMU board.
If... Then...
Two OMU boards are configured in the MPS, Go to Step 2.
Only one OMU board is configured in the MPS, Go to Step 4.
Step 2 Run the DSP OMU command to query the status of the OMU board to be replaced.
BSC6900 GSM
Issue 01 (2010-04-10)
If... Then...
The board status is Standby, Go to Step 4.
The board status is Active, Go to Step 3.
Step 3 Run the DSP OMU command to query the data synchronization status of the active and standby
OMU boards.
If... Then...
The board status is Data synchronization
normal,
Run the SWP OMU command to
manually switch over the active and
standby OMU boards. After five minutes,
run the DSP OMU command to check that
the OMU board to be replaced is in
standby state. Go to Step 4.
The board status is not Data
synchronization normal,
Run the STR DATASYNC command to
manually synchronize the standby
workspaces of the active and standby
OMU boards. Then, run the SWP OMU
command to manually switch over the
active and standby OMU boards. After
five minutes, run the DSP OMU
command to check that the OMU board to
be replaced is in standby state. Go to Step
4.
Step 4 Shut down the operating system of the OMU board.
Step 5 Loosen the captive screws on the OMU board, as shown in part A of Figure 2-3.
BSC6900 GSM
2-9
Figure 2-3 Removing the OMU board

Step 6 Flip open the ejector levers of the OMU board, as shown in part B of Figure 2-3.
NOTE
After you flip open the upper and lower ejector levers, OMU board automatically shuts down the operating
system and hard disks. The OFFLINE LED on the board is on, which indicates that the board is powered
off.
Step 7 Remove the Ethernet cable, mouse cable, keyboard cable, and monitor cable (if configured) from
the OMU board.
Step 8 Pull out the OMU board along the guide rails, as shown in part C of Figure 2-3.
Step 9 Flip open the ejector levers of the OMU board, as shown in part A of Figure 2-4.
Step 10 Push the new board along the guide rails into the subrack, as shown in part B of Figure 2-4.
BSC6900 GSM
Issue 01 (2010-04-10)
Figure 2-4 Installing the OMU board

Step 11 Flip inwards the ejector levers of the OMU board until they are in position, as shown in part C
of Figure 2-4.
Step 12 Secure the screws on the OMU board, as shown in part D of Figure 2-4.
The new board automatically loads program and configuration data, and the RUN LED blinks
every alternate 0.125s.
Step 13 Install the cables by referring to the labels.
Step 14 Use the USB installation disk to install the software and applications on the new OMU board.
For details, see section 4.2.3 Installing the Operating System Through the USB Installation
Disk.
Step 15 Run the DSP OMU command to query the status of the new OMU board again.
If... Then...
Only one OMU board is configured and the Operation status is Active
normal,
Go to Step 17.
BSC6900 GSM
2-11
If... Then...
Two OMU boards are configured and the Operation status is Standby
normal,
Go to Step 17.
In other cases, Go to Step 16.
Step 16 Check whether a board failure alarm is reported on the LMT.
If... Then...
Alarms caused by a faulty board are
reported,
1. Identify and rectify the fault according to the
alarm information.
2. Go to Step 15.
No alarms caused by the faulty board are
reported,
Go to Step 17.
Step 17 Run the DSP OMUMODULE command to view the status of the OMU service. For details,
see Querying the Operating Status of the OMU.
If... Then...
Status is Active, The replacement is complete.
Status is Stopped, Restart the faulty processes. If the fault persists, contact Huawei for
technical support.
Status is Faulty, Contact Huawei for technical support.
NOTE
When only one OMU board is configured, you should restore the system data. For details, see Restoring the
System Data.
----End
Postrequisite
Record the name and the PCB version of the replaced board. Check whether there are obvious
physical damages, such as the distorted pin, broken pin, or burnt board. If there is any damage,
fill in the BSC6900 site maintenance record and pack the replaced board. When packing a
board, pay attention to the following points:
l Wear an ESD wrist strap or a pair of ESD gloves.
l Ensure that each ESD bag or case holds only one board.
l When packing multiple boards, isolate them with ESD materials.
Contact the local Huawei office to dispose of the replaced board.
BSC6900 GSM
Issue 01 (2010-04-10)
NOTE
You may obtain the name and the PCB version from the panel or bottom of the faulty board.
2.3 GBAM
The BSC6900 uses three models of GBAM: IBM X3650T, HUAWEI C5210, and HP CC3310.
The GBAM is installed in the MPR.
2.3.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.
2.3.2 Physical Appearance of the GBAM (IBM X3650T)
This section describes the physical appearance of the GBAM (IBM X3650T).
2.3.3 Physical Appearance of the GBAM (HUAWEI C5210)
This section describes the physical appearance of the GBAM (HUAWEI C5210).
2.3.4 Physical Appearance of the GBAM (HP CC3310)
This section describes the physical appearance of the GBAM (HP CC3310).
2.3.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.
2.3.6 Replacing the GBAM
This section describes how to replace a faulty GBAM. It takes about 40 minutes to replace a
GBAM. There are three models of GBAM, namely, IBM X3650T, C5210, and HP CC3310.
2.3.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 Performs the configuration management, performance management, fault management,
security management, and loading management functions for the system
l 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.3.2 Physical Appearance of the GBAM (IBM X3650T)
This section describes the physical appearance of the GBAM (IBM X3650T).
Figure 2-5 shows the GBAM (IBM X3650T).
Figure 2-5 GBAM (IBM X3650T)
BSC6900 GSM
2-13

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-6 shows the front panel of the GBAM server (IBM X3650T).
Figure 2-6 Front panel of the GBAM (IBM X3650T)

Table 2-5 describes the silkscreen labels on the front panel of the GBAM (IBM X3650T).
Table 2-5 Silkscreen labels on the front panel of the GBAM (IBM X3650T)
No. Silkscreen Label Description
1 None CD-ROM drive
2 Power switch
3 Reset switch
4 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.
5 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.
6 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.
BSC6900 GSM
Issue 01 (2010-04-10)
7 PWR The PWR (Power) LED is used for alarm
indicates that the power supply for the system is
faulty.
8 Serial port for an 8-pin RJ45 connector
9 USB port
10
0
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
1
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 Main power LED
13 NIC0/NIC1 activity LED
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-7 shows the rear panel of the GBAM (IBM X3650T).
Figure 2-7 Rear panel of the GBAM

Table 2-6 describes the silkscreen labels on the rear panel of the GBAM (IBM X3650T).
BSC6900 GSM
2-15
Table 2-6 Silkscreen labels on the rear panel of the GBAM (IBM X3650T)
No. Silkscreen
Label
Description
1 Alarms DB15 port (for exporting alarm information from the
GBAM)
2 None PCI card bracket (with no card inserted)
3 None PCI card bracket (with a card inserted)
4 None 10M/100M adaptive port for Ethernet adapter
5 None Power module
6 PS/2 mouse/keyboard ports. The upper port is for the
mouse, and the lower one is for the keyboard.
8
1
RJ45 NIC port 1
9
2
RJ45 NIC port 2
10 Port for the video
11
1
USB port 1
12
0
USB port 0
13 Server management port
14 Ultra320 SCSI port
15 Grounding post for the PGND cable

2.3.3 Physical Appearance of the GBAM (HUAWEI C5210)
This section describes the physical appearance of the GBAM (HUAWEI C5210).
Figure 2-8 shows the GBAM (HUAWEI C5210).
Figure 2-8 GBAM (HUAWEI C5210)

BSC6900 GSM
Issue 01 (2010-04-10)
Front Panel of the GBAM (HUAWEI C5210)
The components on the front panel of the GBAM (C5210) are LEDs, ports, switches, and a CD-
ROM drive.
Figure 2-9 shows the front panel of the GBAM (HUAWEI C5210).
Figure 2-9 Front panel of the GBAM (HUAWEI C5210)

Table 2-7 describes the silkscreen labels on the front panel of the GBAM (HUAWEI C5210).
Table 2-7 Silkscreen labels on the front panel of the GBAM (HUAWEI C5210)
No.
Silkscreen
Label Description
1 None CD-ROM drive
2 Power switch
3 Reset switch
4 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.
5 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.
6 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.
7 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.
9 USB port
BSC6900 GSM
2-17
No.
Silkscreen
Label Description
10
11
2
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
1
disk 1 is faulty.
15 System ID LED
17 None 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-10 shows the rear panel of the GBAM (HUAWEI C5210).
Figure 2-10 Rear panel of the GBAM (HUAWEI C5210)

Table 2-8 describes the silkscreen labels on the rear panel of the GBAM (HUAWEI C5210).
BSC6900 GSM
Issue 01 (2010-04-10)
Table 2-8 Silkscreen labels on the rear panel of the GBAM (HUAWEI C5210)
No. Silkscreen
Label
Description
1
1
USB port 1
4
1
RJ45 NIC port 1
5 Integrated port for mouse and keyboard. You can use a Y-
shaped cable to connect the mouse and keyboard to the
GBAM (C5210).
7
2
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.)
GBAM)
12
0
RJ45 NIC port 0

2.3.4 Physical Appearance of the GBAM (HP CC3310)
This section describes the physical appearance of the GBAM (HP CC3310).
Figure 2-11 shows the GBAM (HP CC3310).
Figure 2-11 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.
BSC6900 GSM
2-19
Figure 2-12 shows the front panel of the GBAM (HP CC3310).
Figure 2-12 Front panel of the GBAM (HP CC3310)

Table 2-9 describes the silkscreen labels on the front panel of the GBAM (HP CC3310).
Table 2-9 Silkscreen labels on the front panel of the GBAM (HP CC3310)
No.
Silkscreen
Label Description
1 None CD-ROM drive
2 Power switch
3 Reset switch
4 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.
5 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.
6 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.
7 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.
9 USB port
10
BSC6900 GSM
Issue 01 (2010-04-10)
No.
Silkscreen
Label Description
11
2
disk 2 is faulty.
12
1
disk 1 is faulty.
15 System ID LED
17 None NMI switch. The NMI switch is used to stop the system for
fault diagnosis.

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-13 shows the rear panel of the GBAM (HP CC3310).
Figure 2-13 Rear panel of the GBAM (HP CC3310)

Table 2-10 describes the silkscreen labels on the rear panel of the GBAM (HP CC3310).
BSC6900 GSM
2-21
Table 2-10 Silkscreen labels on the rear panel of the GBAM (HP CC3310)
1
1
USB port 1
4
1
RJ45 NIC port 1
5 Integrated port for mouse and keyboard. You can use a
Y-shaped cable to connect the mouse and keyboard to
the GBAM (HP CC3310).
7
2
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.)
GBAM)
12
0
RJ45 NIC port 0

2.3.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-11, Table 2-12, and Table 2-13 respectively.
Table 2-11 Hardware configuration specifications of the GBAM (IBM X3650T)
Hardware Name Hardware Specifications
CPU Double CPU; primary frequency: 3.2 GHz
Memory 2 GB
BSC6900 GSM
Issue 01 (2010-04-10)
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-12 Hardware configuration specifications of the GBAM (C5210)
Memory 2 GB
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.

Table 2-13 Hardware configuration specifications of the GBAM (HP CC3310)
Memory 2 GB
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-14 shows, performance counters of the three types of GBAM are the same.
BSC6900 GSM
2-23
Table 2-14 Performance counters of the GBAM
Counter Name Counter Value
Number of recorded
alarms
The maximum number of recorded alarms is 300,000.
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
caused to pause by its upgrade.
l Restarting the GBAM takes about five minutes if the GBAM is
caused to stop working by its fault

2.3.6 Replacing the GBAM
This section describes how to replace a faulty GBAM. It takes about 40 minutes to replace a
GBAM. There are three models of GBAM, namely, IBM X3650T, C5210, and HP CC3310.
Prerequisite
l The tools are ready. They are the ESD wrist strap, Phillips screwdriver, straight screwdriver,
and ESD boxes or bags.
l A new GBAM is ready.
CAUTION
l When configuring the new GBAM or OMU board, ensure that the following parameter
settings are consistent with those of the GBAM to be replaced: server name or computer
name, OS administrator password, admin password, and IP address.
l If you change the IP address of the GBAM, you need to reset the alarm box manually.
Context
CAUTION
To avoid damage to the boards, ASIC chips, or other electronic components, wear an ESD wrist
strap properly. Ensure that the ESD wrist strap is properly connected to the ESD connector on
the cabinet. If no ESD wrist strap or no proper grounding point is available, wear ESD gloves.
BSC6900 GSM
Issue 01 (2010-04-10)
CAUTION
l Replacing the GBAM disrupts the communication between the GBAM and the host boards.
l Replacing the GBAM disrupts the communication between the LMT/M2000 and the
BSC6900. In this case, you cannot maintain the BSC6900 or collect the alarm information.
The BSC6900 host boards, however, work normally during the replacement of the GBAM.
Procedure
l Replace the GBAM with a new GBAM.
1. Log in to the GBAM as user root, and then run the Linux OS command /etc/rc.d/
omud stop to stop all applications on the GBAM to be replaced.
2. Run the Linux OS command poweroff to shut down the GBAM to be replaced.
3. Turn off SW3 and SW6 on the power distribution box that control the power supply
to the GBAM to be replaced. Figure 2-14 shows the labels for the power switches on
the front panel of the power distribution box.
Figure 2-14 Front panel of the power distribution box
1 Panel of the MDMC 2 RUN LED 3 ALM LED 4 Mute switch
5 Labels of power switches 6 Power switches 7 Panel of the WOPB board

4. Check whether the labels on the cables that are connected to the GBAM to be replaced
are legible. If the labels are not legible, attach a new label to the cables to avoid
improper connection after replacing the GBAM.
5. Remove the power cable, PGND cable, and Ethernet cables from the GBAM to be
replaced.
6. Remove the screws fixing the GBAM to the rack.
7. Remove the hangers from the GBAM to be replaced, and then install the hangers on
the new GBAM.
8. Remove the GBAM from the cabinet along the guide rails.
9. Place the new GBAM in the original position. Then, secure the screws.
10. Connect the power cable, PGND cable, and Ethernet cables to the new GBAM.
11. Turn on the power switch controlling the power supply to the GBAM on the power
distribution box. For distribution of the power switches, see labels on the front panel
of the power distribution box, as shown in Figure 2-14.
BSC6900 GSM
2-25
12. Turn on the power switch on the front panel of the new GBAM.
13. Check the items in Table 2-15.
Table 2-15 Checklist for GBAM replacement
Item Result Action
Whether the LEDs on the
panel show that the GBAM is
in normal state. For details on
the LEDs, see Front Panel of
the GBAM (IBM X3650T),
Front Panel of the GBAM
(HUAWEI C5210), and
Front Panel of the GBAM
(HP CC3310).
Yes Check the next item.
No Rectify the fault by
referring to the user
manual of the GBAM.
Alarms related to the failure of
the GBAM are cleared.
No 1. Clear the alarms by
referring to the alarm
online help on the
LMT.
2. If the alarms persist,
contact Huawei for
technical support.
Run the Ping command to
check whether the
communication between the
GBAM and other computers
on the same network segment
is normal.
No 1. Check whether the
route setting is
correct. If the route
setting is incorrect,
modify the route
setting.
2. If the route setting is
correct, check the
connection of the
Ethernet cables.
Check whether the processes
are normal.
Yes End the check.
No Restart the abnormal
processes. If the
problem persists,
contact Huawei for
technical support.

l Replace the GBAM with an OMUa board.
BSC6900 GSM
Issue 01 (2010-04-10)
CAUTION
l Do not perform any operations that will modify the configuration data or the attributes
when replacing the GBAM.
l Get a PC ready for file backup during the GBAM replacement.
1. The OMU board can be installed in slots 0 to 3, 20 to 23, or 24 to 27 in the MPS. When
replacing the GBAM with the OMU board, first run the LST BRD command to check
whether there is an idle slot for the OMU board. If there is no idle slot for the OMU
board, first modify the configuration data.
2. Collect the required information.
(1) Run the DSP OMU command to obtain the computer name and external fixed
IP address of the GBAM.
NOTE
If the external fixed IP address is not configured, its value is displayed as null. In this case,
one must apply for an IP address that is in the same network segment as the external virtual
IP address and use it as the external fixed IP address.
(2) Run the LST VER command to obtain the version information about the GBAM.
(3) Run the Linux OS command route to obtain the external mask and gateway IP
address of the GBAM.
(4) Run the Linux OS command ps -afx to obtain the common directory and active
workspace directory of the OMU.
3. Obtain the version software based on the version information obtained in step 2.2.
4. Back up the data on the GBAM.
(1) Create a backup directory on the hard disk that has at least 1 GB free space on
the PC. The backup directory is used to back up the data on the GBAM. Then,
create subdirectories common, data, license, DefaultMeas, cert, and bin under
the backup directory.
(2) Back up the reg.ini file in the common directory of the OMU to the backup/
common directory of the PC.
(3) Run the BKP DB command to back up the OMU databases. The backup
databases are stored in /data/backup of the OMU active workspace directory.
Then, back up the files in /data/backup of the OMU active workspace directory
to the backup/data directory of the PC.
(4) Back up the license files in the license of the OMU active workspace directory
to the backup/license directory of the PC.
(5) Back up the performance task files in /ftp/DefaultMeas of the OMU active
workspace directory to the backup/DefaultMeas directory of the PC.
(6) Back up the certificate files in /ftp/cert of the OMU active workspace directory
to the backup/cert directory of the PC.
(7) Back up the bin directory. To back up the bin directory, first run the Linux OS
command tar czvf bin.tgz bin/ in the OMU active workspace directory to
compress the bin directory. Then, back up the compressed bin.tgz file to the
backup/bin directory of the PC.
5. Shut down the GBAM to be replaced.
BSC6900 GSM
2-27
(1) Log in to the GBAM as user root, and then run the Linux OS command /etc/rc.d/
omud stop to stop all applications on the GBAM to be replaced.
(2) Run the Linux OS command poweroff to shut down the GBAM to be replaced.
(3) Turn off SW3 and SW6 on the power distribution box that control the power
supply to the GBAM to be replaced. Figure 2-14 shows the labels for the power
switches on the front panel of the power distribution box.
6. Remove the GBAM.
(1) Remove the power cable, PGND cable, and Ethernet cables from the GBAM to
be replaced.
(2) Remove the screws fixing the GBAM to the rack. Then, remove the hangers from
the GBAM to be replaced.
(3) Remove the GBAM from the cabinet along the guide rails.
7. Installing the OMUa Boards
8. Installing the OMU Applications in the Active Workspace
9. Modify the external fixed IP address, mask, gateway IP address, and computer name
of the OMU by using the omutool. For details, see Changing the IP Addresses and
Masks of the OMU Ethernet Adapters and Changing the OMU Name.
10. Recover the data.
(1) Recover the reg.ini file by first deleting the reg.ini file in the /mbsc/bam/
common/ directory of the OMU and then uploading the reg.ini file in the backup/
common directory of the PC to the /mbsc/bam/common/ directory of the OMU.
(2) Recover the license files by uploading the license files in the backup/license
directory of the PC to the /mbsc/bam/version_a/license directory of the OMU.
(3) Recover the performance task files by uploading the files in the backup/
DefaultMeas directory of the PC to the /mbsc/bam/version_a/ftp/
DefaultMeas directory of the OMU.
(4) Recover the license files by uploading the files in the backup/cert directory of
the PC to the /mbsc/bam/version_a/ftp/cert directory of the OMU.
(5) Recover the bin directory.
Run the Linux OS command mv /mbsc/bam/version_a/bin /mbsc/bam/
version_a/binbak to change the name of the bin directory in the /mbsc/bam/
version_a directory to binbak.
Upload the bin.tgz file in the backup/bin directory of the PC to the /mbsc/
bam/version_a directory of the OMU.
Run the Linux OS command tar xzvf bin.tgz to decompress the bin directory.
Run the Linux OS command rm -fr /mbsc/bam/version_a/binbak to delete
the binbak directory.
(6) Recover the OMU databases.
Upload the files in the backup/data directory of the PC to the OMU.
Recover the OMU data by using the omu_backup_linker tool. For details, see
Restoring the System Data.
11. Run the Linux OS command /etc/rc.d/omud start to start the OMU services.
12. Run the DSP OMU command to check the status and IP addresses of the new board.
13. Run the DSP OMUMODULE command to check the status of OMU services.
BSC6900 GSM
Issue 01 (2010-04-10)
14. Run the DSP BRD command to query the status of the OMU board.
15. After the OMU board works normally, run the ADD BRD command to add the
configuration data of the OMU board.
16. Run the SET SCUPORT command to disable ports 10 and 11 on the SCUa board in
subrack 0.
----End
2.4 OMU Software
OMU software refers to all the software running on the OMU.
2.4.1 OMU Application Structure
The OMU applications, used for operation and maintenance, consist of multi-level service
monitoring entities and service processes.
2.4.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.
2.4.3 OMU Service Processes
The OMU provides the back administration function with the help of OMU service processes.
2.4.1 OMU Application Structure
The OMU applications, used for operation and maintenance, consist of multi-level service
monitoring entities and service processes.
Figure 2-15 shows the structure of the OMU applications.
BSC6900 GSM
2-29
Figure 2-15 OMU Application Structure

NOTE
The bidirectional arrows shown in Figure 2-15 denote communication between modules.
For details about the OMU service processes, see 2.4.3 OMU Service Processes. For details
about the service monitoring entities, see 2.4.2 OMU Service Monitoring Entities.
2.4.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.
BSC6900 GSM
Issue 01 (2010-04-10)
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.4.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
l Scheduled task management
Configuration Module (configure)
The configuration module performs the functions of data configuration and management for the
BSC6900 host, such as configuring data effective and ineffective modes, formatting the data
files loaded by the host, and checking data consistency.
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.
BSC6900 GSM
2-31
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.
l 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.
BSC6900 GSM
Issue 01 (2010-04-10)
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.
2.5 OMU Working Mode
The OMU works in single-OMU or dual-OMU mode.
Single-OMU Mode
When the BSC6900 is configured with one OMUa/OMUb board, the OMU works in single-
OMU mode.
If the OMU is faulty, you cannot perform OM on the BSC6900. The system reliability is low
when the OMU is 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 boards, the OMUs work in active/
standby mode, that is, dual-OMU mode.
In dual-OMU mode, the OMUa/OMUb board working in active mode is called the active OMUa/
OMUb board, that is, the active OMU; the OMUa/OMUb board working in standby mode is
called the standby OMUa/OMUb board, that is, the standby OMU.
When the BSC6900 is in dual-OMU mode, the OMU can operate normally 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 and 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.
l Use two OMUa or OMUb boards.
2.6 OMU OM Methods
This 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.
BSC6900 GSM
2-33
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 on Site.
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.
l 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 that of the BSC6900 is Dopra Linux.
After the BSC6000 is upgraded to the BSC6900, Suse Linux can keep functioning or be switched
to Dopra Linux.
In this scenario:
l Install the OMU operating system and OMU applications by referring to 5.1 Software
Installation After the Upgrade.
l Perform routine operation and maintenance on the OMU by referring to 5.2 Routine OMU
Maintenance After the Upgrade and 5.3 OMU Operation and Maintenance After the
Upgrade.
BSC6900 GSM
Issue 01 (2010-04-10)
2.7 OMU Safety Information
This 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.
l 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.
l 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.
BSC6900 GSM
2-35
About This Chapter
This describes the operating principles of Ethernet adapters, related IP addresses, active and
standby workspaces, and active and standby OMUs.
3.1 OMU Ethernet Adapter Configuration
This section describes the configuration of Ethernet adapters on the OMUa board, OMUb board,
and GBAM.
3.2 Planning of the OMU IP Addresses
The six OMU Ethernet adapters must follow the IP address planning principles to meet the
requirements of the communication in the operation and maintenance network.
3.3 OMU Networking Principle
The internal Ethernet adapters of the OMU are connected to the SCUa boards in the MPS, and
the external Ethernet adapters of the OMU are connected to the OM terminals. In this way, the
OMU helps the communication between the BSC6900 and the OM terminals.
3.4 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.5 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.6 Switchover Between the Active and Standby OMUs
When the OMU works in dual-OMU mode, there are four types of switchover, namely, manual
switchover, fault-triggered switchover, failover, and self-healing switchover.
BSC6900 GSM
OMU Administration Guide 3 Working Principles of the OMU
3-1
3.1 OMU Ethernet Adapter Configuration
This section describes the configuration of Ethernet adapters on the OMUa board, OMUb board,
and GBAM.
Configuration of Ethernet Adapters on the OMUa Board
An OMUa board is configured with six Ethernet adapters in total. To enhance the network
reliability, two Ethernet adapters are teamed for 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 OMU 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.
l ETH2: ETH2 (bond2), a debugging Ethernet adapter, is connected to a portable PC for
OMU debugging if required.
l 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.
l 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.
Figure 3-1 Mapping between the ETHxxx and the bondxxx on the OMUa Board

BSC6900 GSM
Issue 01 (2010-04-10)
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 for the external fixed IP address, and the other 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 SCUa board, 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 in total. To enhance the network
reliability, two Ethernet adapters are teamed for 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 OMU 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.
l 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.
l 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.
l 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.
Figure 3-2 Mapping between the ETHxxx and the bondxxx on the OMUb Board

BSC6900 GSM
3-3
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.
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-3 shows the location of the Ethernet adapters
on the HUAWEI C5210 GBAM.
Figure 3-3 Location of Ethernet adapters on HUAWEI C5210 GBAM
1 Ethernet adapter integrated on the host 2 Ethernet adapter integrated on the host
3 Ethernet adapter integrated on the PCI slot 4 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-3 are exclusive.

IBM X3650T GBAM has four Ethernet adapters: two internal Ethernet adapters and two external
Ethernet adapters. Figure 3-4 shows the location of the Ethernet adapters on the IBM X3650T
GBAM.
Figure 3-4 Location of Ethernet adapters on IBM X3650T GBAM
3 Ethernet adapter integrated on the PCI slot 4 Ethernet adapter integrated on the PCI slot

HP CC3310 GBAM has three Ethernet adapters: two internal Ethernet adapters and one external
Ethernet adapter. Figure 3-5 shows the location of the Ethernet adapters on the HP CC3310
GBAM.
BSC6900 GSM
Issue 01 (2010-04-10)
Figure 3-5 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.
l 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 adapter(s) 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-6 and Figure 3-7 show the IP addresses for Ethernet adapters on the GBAM.
BSC6900 GSM
3-5
Figure 3-6 IP addresses for three Ethernet adapters on the GBAM

Figure 3-7 IP addresses for four Ethernet adapters on the GBAM

3.2 Planning of the OMU IP Addresses
The six OMU Ethernet adapters must follow the IP address planning principles to meet the
requirements of the communication in the operation and maintenance network.
BSC6900 GSM
Issue 01 (2010-04-10)
NOTE
l The OMU in the existing network involves OMUa board, OMUb board, and GBAM. OMUb board and
GBAM are legacy material, and thus do not require IP address planning in a 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 in the case of OMUa board.
Definitions of IP addresses of the OMU
The OMU IP addresses include external/internal fixed IP addresses, external/internal virtual IP
addresses, and debugging IP address. If the BSC6900 is configured with two OMUa boards, the
OMU IP addresses also include the backup channel IP address of the active and standby OMUs.
Table 3-1 describes the definitions of the IP addresses of the OMU.
Table 3-1 Definitions of IP addresses of the OMU
IP
Address
Definition Function Ethernet
Adapter
External
fixed IP
address
This IP address is configured for the
external Ethernet adapter team when the
OMU operating system is installed.
used for the
communication
between the
peripheral devices and
the OMU.
When the switchover
between the active
OMU and the standby
OMU occurs, the
communication
through the IP address
between the devices
and the OMU is
disrupted.
l ETH0
l ETH1
BSC6900 GSM
3-7
IP
Address
Adapter
External
virtual IP
address
IP address used for the communication
between the OMU and the LMT or
M2000 The external virtual IP address is
configured during the installation of the
OMU applications.
The external virtual IP address is
configured for the external Ethernet
adapter team of the active OMU and takes
effect automatically when the OMU
applications are started.
Used for the
communication
between the active
OMU and the LMT/
M2000.
When the switchover
between the active
OMU and the standby
OMU occurs, the
communication
through the IP address
between the LMT or
M2000 and the OMU
is disrupted for a while
and then recovered
automatically.
NOTE
The LMT can access
the OMU only through
the external virtual IP
address.
l ETH0
l ETH1
Internal
fixed IP
address
internal Ethernet adapter team when the
Used for the
communication
between the active
OMU and the standby
OMU in the internal
network segment.
l ETH4-
SCU7
l ETH5-
SCU6
Internal
virtual IP
address
between the OMU and the BSC6900 host
internal Ethernet adapter team of the
active OMU and is configured
automatically when the OMU
applications are started.
Used for the
communication
between the active
OMU and the
BSC6900 host boards.
When the switchover
between the active
OMU and the standby
OMU occurs, the
communication
between the OMU and
the BSC6900 host
boards is not
disrupted.
l ETH4-
SCU7
l ETH5-
SCU6
BSC6900 GSM
Issue 01 (2010-04-10)
IP
Address
Adapter
Backup
channel
IP
address
of the
active
and
standby
OMUs
between the active OMU and the standby
OMU This IP address is configured for
the backup Ethernet adapter when the
Used for the
communication
between the active
OMU and the standby
OMU in the backup
channel network
segment.
ETH3-
UPDATE
Debuggi
ng IP
address
IP address used for performing operation
and maintenance on the OMU locally
This IP address is used
for debugging the
OMU locally. LMT
processes cannot be
accessed through this
IP address.
ETH2

Definition of Onsite Network
The network between the OMU external Ethernet adapters and the LMT/M2000 is defined as
external network, that is, onsite network. If the OMU external Ethernet adapters are connected
to the LMT/M2000 routers, then the network between the OMU external Ethernet adapters and
the first router (gateway) is defined as onsite network. Figure 3-8 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.
l 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-8 Onsite network

Follow the following principles for 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/
BSC6900 GSM
3-9
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
Before an OMU is delivered, six IP addresses are configured. For details, see 4.5.2 Checklist
for the Factory Settings of the OMU Software. The default IP addresses may not meet the
requirement of onsite planning. All the OMU IP addresses need to be planned on site, and some
of the IP addresses need to be re-set.
Generally, the external fixed IP address and external virtual IP address need to be re-set according
to the network planning of the customer. The backup channel IP addresses of OMUs are the
same before delivery. Therefore, the backup channel IP addresses of the active and standby
OMUs need to be planned on site to avoid conflict.
l If one OMU is configured, the external fixed IP address and external virtual IP address
need to be planned in the way that they are located in the same network segment.
l If active and standby OMUs are configured, two external fixed IP addresses and one
external virtual IP address need to be planned in the way that they are located in the same
network segment. In addition, the backup IP addresses of the active and standby OMUs
need to be planned in the way that they are located in the same network segment and do
not conflict with each other.
Table 3-2 describes the planning principles of OMU IP addresses.
Table 3-2 Onsite planning of OMU IP addresses
IP Address Planning Principle
External fixed IP
address
The default external fixed IP address is 172.121.139.201 (255.255.255.0).
Planning principle:
1. The external fixed IP address should be changed on site so that the
external fixed IP address and the onsite network are located in the same
network segment. In addition, the external fixed IP address cannot
conflict with the onsite network.
2. If active and standby OMUs are configured, the external fixed IP
addresses of the active and standby OMUs must be different from and
located in the same network segment as the onsite network.
External virtual
IP address
You can change the external virtual IP address as required on site. Ensure
that the external virtual IP address and the external fixed IP address are in
the same network segment (This network segment is named external
network segment). In addition, the external virtual IP address cannot
conflict with other IP addresses in the network segment.
For example, in dual-OMU mode, if the external fixed IP address of the
active OMU is 172.121.139.201 and that of the standby OMU is
172.121.139.202, the external virtual IP address can be configured as
172.121.139.200.
In single-OMU mode, the external virtual IP address is set according to
the one of the active OMU in dual-OMU mode.
BSC6900 GSM
Issue 01 (2010-04-10)
IP Address Planning Principle
Backup channel
IP address of the
active and
standby OMUs
The default backup channel IP addresses of the active and standby OMUs
is 192.168.3.50 (255.255.255.0).
Planning principle:
1. The network segment in which the backup IP addresses of the active
and standby OMUs cannot conflict with the onsite network segment.
If so, 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 in the same network segment.
3. In single-OMU mode, reserve the default setting of the backup channel
IP address.

IP Addresses to Be Checked on Site
Other OMU IP addresses except the ones that needs to be changed on site need to be checked
on site. If they are located in the same network segment as the onsite network, they need to be
replanned and reconfigured. Table 3-3 describes the principles of checking the IP addresses.
Table 3-3 Onsite checking of OMU IP addresses
IP Address Checking Principle
Internal fixed IP
address
The default internal fixed IP address is 80.168.3.50 (255.0.0.0).
Checking principle:
1. The internal fixed IP address cannot conflict with the onsite network.
If so, it must be changed.
2. Only the network segment where the internal fixed IP address can be
changed. For example, 80.168.3.50 is changed to 90.168.3.50.
3. In dual-OMU mode, the internal fixed IP addresses of the active and
4. In single-OMU mode, if the network segment where the internal fixed
IP address is located does not conflict with the onsite network segment,
reserve the default setting of the internal fixed IP address.
Internal virtual
IP address
The internal virtual IP address must be located in the same subnet with
the internal fixed IP addresses of the active and standby OMUs. This
subnet is named as the OMU internal network segment. In addition, the
internal virtual IP address cannot be identical with other IP addresses in
the subnet.
For example, in dual-OMU mode, if the internal fixed IP address of the
active OMU is 80.168.3.50 and that of the standby OMU is 80.168.3.60,
the internal virtual IP address can be configured as 80.168.3.40.
In single-OMU mode, the external virtual IP address is set according to
the one of the active OMU in dual-OMU mode.
BSC6900 GSM
3-11
IP Address Checking Principle
Debugging IP
address
The factory setting of the debugging IP address is 192.168.6.50
(255.255.255.0).
Checking principle:
1. The debugging IP addresses of the active and standby OMUs cannot
conflict with other IP addresses in the onsite network. If so, the
debugging IP addresses must be changed.
2. In dual-OMU mode, the debugging IP addresses of the active and
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 internal fixed
IP address is located does not conflict with the onsite network segment,
reserve the default setting of the internal fixed 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
External fixed IP
address
After the external fixed IP address is changed, the device that is connected
to the external Ethernet port cannot access the OMU unless through the
new external fixed IP address.
External virtual
IP address
After the external virtual IP address is changed, the device that is
connected to the OMU through the IP address cannot access the OMU
unless through the new external virtual IP address.
Internal fixed IP
address
The planning of the internal fixed IP address must be consistent with that
of the IP address for the BSC6900 host boards. After the internal fixed 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 fixed IP address is changed usually when the OMU is
debugged on site to avoid negative effects caused by frequency resets of
the BSC6900 during daily maintenance.
Internal virtual
IP address
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 changed usually when the OMU is
debugged on site to avoid negative effects caused by frequency resets of
the BSC6900 during daily maintenance.
BSC6900 GSM
Issue 01 (2010-04-10)
IP Address Change Impact
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, you need not change the backup channel IP
address.
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.

NOTE
l The internal and external fixed IP addresses are bound to the OMUa board, and the internal and external
virtual 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, and 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: internal fixed IP address and internal
virtual IP address, external fixed IP address and external virtual 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, and the IP addresses in a network segment cannot conflict with each other neither.
l Record the IP addresses in 4.5.1 Records of OMU Software Installation Information.
3.3 OMU Networking Principle
The internal Ethernet adapters of the OMU are connected to the SCUa boards in the MPS, and
the external Ethernet adapters of the OMU are connected to the OM terminals. In this way, the
OMU helps the communication between the BSC6900 and the OM terminals.
Single-OMUa/OMUb Networking Principle
Figure 3-9 shows the networking in single-OMUa/OMUb mode.
BSC6900 GSM
3-13
Figure 3-9 Single-OMUa/OMUb networking topology

The two internal Ethernet adapters ETH4-SCU7 and ETH5-SCU6 of the OMU are connected
to the SCUa boards in slot 7 and slot 6 of the MPS respectively through the backplane.
The two external Ethernet adapters of the OMUa board ETH0 and ETH 1 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.
Dual-OMUa/OMUb Networking Principle
Figure 3-10 shows the networking in dual-OMUa/OMUb mode.
BSC6900 GSM
Issue 01 (2010-04-10)
Figure 3-10 Dual-OMUa/OMUb networking topology

The two internal Ethernet adapters ETH4-SCU7 and ETH5-SCU6 of the OMU are connected
to the SCUa boards in slot 7 and slot 6 of the MPS respectively through the backplane.
The two external Ethernet adapters of the OMUa board ETH0 and ETH 1 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.
The working principle of the standby OMU is similar to that of the active OMU.
The ETH3-UPDATE of the active OMU is connected to the ETH3-UPDATE of the standby
OMU through the backplane to fulfill the data synchronization and the OMU software update
between the active and standby OMUs.
BSC6900 GSM
3-15
GBAM Networking Principle
Figure 3-11 shows the networking principle concerning the GBAM and LAN switch.
Figure 3-11 GBAM networking topology

As shown in Figure 3-11, 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 he 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 balance of traffic volume is achieved between multiple links.
BSC6900 GSM
Issue 01 (2010-04-10)
3.4 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.5 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.
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.6 Switchover Between the Active and Standby OMUs
When the OMU works in dual-OMU mode, there are four types of switchover, namely, manual
switchover, fault-triggered switchover, failover, and self-healing switchover.
BSC6900 GSM
3-17
NOTE
During the switchover process, the communication between the OM terminals and the OMU is interrupted
for about one to two minutes. In addition, operation and maintenance cannot be performed on the LMT
until the switchover is complete successfully.
Manual Switchover
If the OMU works in dual-OMU mode and the data synchronization between the active OMU
and the standby OMU is normal, you can manually switch over the OMUs as required, for
example, in the case that the active OMU needs to be manually shut down for software/hardware
upgrade or fault rectification. To manually switch over the OMUs, you can run the SWP
OMU command on the MML client or refer to Switching Over the BSC Boards. After the manual
switchover, the standby OMU is in active mode, and the active OMU is in standby mode.
The manual switchover can be performed only when the active and standby OMUs work
properly. In addition, at least one of the following prerequisites must be met:
l The message in response to the execution of the DSP OMU command indicates that the
Data-sync state is Data synchronization is successful.
l The data synchronization between the active OMU and the standby OMU is stopped
through the STP DATASYNC command.
l The message in response to the execution of the DSP OMU command shows that the
version of the active OMU applications is different from that of the standby OMU
applications.
CAUTION
Before performing the manual switchover, do not perform any operation that may change the
data in the database, such as configuring data and changing the user information.
Fault-Triggered Switchover
When the active/standby OMUs run normally, 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 five minutes, the standby OMU automatically switches over to be in active mode.
Once the fault is rectified, the original active OMU works in standby mode. If the fault is rectified
within five minutes, the switchover does not occur.
The fault-triggered switchover caused by loss of heartbeat is classified as follows:
l If a heartbeat message is not received through any one of the heartbeat channels within one
minute, you can infer that the heartbeat is interrupted. In this case, the active OMU generates
an alarm.
l You can query the Internal network link state, External network link state, and Backup
network link state through the execution of the DSP OMU command. If the three channels
between the active OMU and the standby OMU is disrupted for five minutes but the internal
and external networks of the standby OMU works normally, then the standby OMU is
automatically switched over to the active OMU.
BSC6900 GSM
Issue 01 (2010-04-10)
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 a.m. and 5 a.m..
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
Note that you should not set parameters during the failover. However, you can query when the failover occurs
through the LST ASWPARA command.
Self-Healing Switchover
Self-healing switchover is a method of self-healing for the OMU.
When the hard disk capacity overflows, processes are abnormal, and the internal or external
Ethernet adapter team does not receive or send any message in 10 minutes, the standby OMU
triggers self-healing switchover automatically and reports the alarm ALM-20701 OMU Failure
Switchover.
BSC6900 GSM
3-19
About This Chapter
OMU when a BSC6900 NE is created.
Context
In this scenario, the physical entity to carry the OMU is the OMUa board. For the procedure for
replacing a faulty OMUa board, see 2.2.6 Replacing an OMU Board in the BSC6900 GSMSite
Maintenance Guide.
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

l Operating system
The Dopra Linux operating system is used.
l OMU applications
Based on the operating system, the OMU applications provide all types of service progress.
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, mask, and OMU name on site according
to the IP address planning principle.
4.2 Reinstalling Software on Site
BSC6900 GSM
OMU Administration Guide 4 Scenario: Creating a BSC6900 NE
4-1
When the OMUa board is damaged or the operating system collapses, you need to replace the
OMUa board or reinstall the operating system and OMU applications.
4.3 Operating and Maintaining the OMU
This describes how to perform operation and maintenance 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 provides the tables in which the OMU information is recorded during the routine
operation and maintenance on the OMU.
BSC6900 GSM
Issue 01 (2010-04-10)
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, mask, and OMU name on site according
to the IP address planning principle.
1. 4.1.1 Setting the Link Mode of the External OMU Ethernet Adapter
This describes how to set the link mode of the external Ethernet adapter on the OMU so
that it is consistent with that of the LAN switch.
2. 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.
4.1.1 Setting the Link Mode of the External OMU Ethernet Adapter
This describes how to set the link mode of the external Ethernet adapter on the OMU so that it
is consistent with that of the LAN switch.
Prerequisite
You have obtained the link mode of the LAN switch.
Context
If the link mode of the external Ethernet adapter on the OMUa board panel is inconsistent with
that of the LAN switch, the network may be interrupted. If the link mode of the LAN switch is
specified, the link mode of the external Ethernet adapter on the OMUa board panel should also
be specified.
There are two link modes of the LAN switch: force mode and auto-negotiation mode. The link
mode of the OMUa external Ethernet adapter must be consistent with the link mode of the LAN
switch.
NOTE
If the link mode of the LAN switch is auto-negotiation, you do not need to set the link mode of the external
Ethernet adapter on the OMUa board. End this task.
Procedure
Step 1 Log in to the OMU remotely by referring to Logging In to the OMU.
Step 2 Run the /root/eth_alias_omu.sh command to query the names of the external Ethernet adapters
that are identified by the operating system corresponding to ETH0 and ETH1.
BSC6900 GSM
4-3
NOTE
Assume that:
l The names of the external Ethernet adapters that are identified by the operating system corresponding
to ETH0 and ETH1 are eth0 and eth1.
l The force link mode is half-duplex with a rate of 10 Mbit/s.
Step 3 Run the ethtool eth0 command to query the eth0 link mode. The screen is displayed, as shown
in Figure 4-2. Check whether the fields Speed, Duplex, and Auto-negotiation are set consistent
with the link mode of the LAN switch.
Figure 4-2 Querying the link mode of the Ethernet adapter (example)
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: 10Mb/s
Duplex: Half
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
consistent with that of the LAN
switch.
End this task.
The link mode of eth0 is not
consistent with that of the LAN
switch.
Go to Step 4.
Step 4 Set the link mode of the OMUa external Ethernet adapter according to the link mode of the LAN
switch.
Option Description
The link mode of the LAN
switch is force mode,
Enter the ethtool -s eth0 speed 10duplex half autoneg off
command.
The link mode of the LAN
switch is auto-negotiation
mode,
Enter the ethtool -s eth0 speed 10 duplex half autoneg on
command.
BSC6900 GSM
Issue 01 (2010-04-10)
CAUTION
If the link mode of the LAN switch is not auto-negotiation and you are not sure whether it is
duplex, you must assume that the link mode of the LAN switch is half-duplex, and you must set
the link mode of the external Ethernet adapter on the OMUa board panel to half-duplex.
Step 5 Repeat Step 3 and Step 4 to set the eth1 link mode.
NOTE
The link modes of eth0 and eth1 must be consistent.
----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.
Prerequisite
The OMU is connected to the local PC through the debugging Ethernet port.
Procedure
Step 1 Connect the PC to the ETH2 debugging port on the OMUa board by using an Ethernet cable.
Step 2 Set the IP address of the PC to be on the same network segment with the ETH2 port. The initial
IP address of the ETH2 port is 192.168.6.50, the subnet mask is 255.255.255.0.
Step 3 Log in to the OMU by referring to Logging In to the OMU.
Step 4 Run the /etc/rc.d/omud status command to check the running status of the OMU process.
If... Then...
The information returned is running, 1. Run the /etc/rc.d/omud stop command to
stop the omud process.
2. Go to Step 5.
The information returned is unused, Go to Step 5.
The information returned is neither running
nor unused,
Install the OMU application in the active
workspace by referring to Installing the
OMU Applications in the Active
Workspace.

Step 5 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 that required by the operator,
Perform operations in Step 6 through Step
15.
BSC6900 GSM
4-5
If... Then...
The version of the OMU application is
different from that required by the operator,
1. Uninstalling the OMU application by
referring to Uninstalling the OMU
Applications.
2. Install the OMU application in the active
workspace by referring to Installing the
OMU Applications in the Active
Workspace.
3. Perform operations in Step 6 through Step
9.
4. Perform operations in Step 13 through
Step 15.

Step 6 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 7 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 run the following command and then press Enter.
./omutool extercard 10.161.10.100 255.255.255.0 10.161.10.1
NOTE
After the external fixed IP address is changed, the BSC6900 can be connected to the OM network of the operator
through the ETH0 or ETH1 port. In this case, the commissioning need not necessarily be performed in the
BSC6900 equipment room and can be performed in a centralized manner.
Step 8 Change the external virtual IP address and the subnet mask of the active and standby OMUs
according to the plan.
Run the ./omutool extervip The external virtual IP address The subnet mask command to
change the external virtual IP address and the subnet mask. For example, you can run the
following command and then press Enter.
./omutool extervip 10.161.10.102 255.255.255.0
Step 9 Check whether the internal fixed IP address, internal virtual IP address, backup channel IP
address, and debugging IP address of active and standby OMUs are in the same network segment
as the network of the operator.
BSC6900 GSM
Issue 01 (2010-04-10)
If... Then...
Any IP address is in the same
network segment as the network of
the operator, change the IP
address.
l Run the ./omutool innercard The internal fixed IP
address The subnet mask command to change the
internal fixed IP address and the subnet mask. For
example, you can run the following command and
then press Enter.
./omutool innercard 80.168.3.60 255.0.0.0
l Run the ./omutool innervip The internal virtual IP
internal virtual IP address and the subnet mask. For
then press Enter.
./omutool innervip 80.168.3.40 255.0.0.0
l Run the ./omutool backupcard The IP address The
subnet mask command to change the backup channel
IP addresses of the active and standby OMUs and the
subnet mask. For example, you can run the following
command and then press Enter.
./omutool backupcard 192.168.3.60
255.255.255.0
l Run the ./omutool debugcard The debugging IP
debugging IP address and the subnet mask. For
then press Enter.
./omutool debugcard 192.168.6.60 255.255.255.0
All IP addresses are not in the
same network segment as the
network of the operator, change
only the backup channel IP
address of the backup OMU.
Run the ./omutool backupcard The IP address The
subnet mask command to change the backup channel IP
addresses of the active and standby OMUs and the subnet
mask. For example, you can run the following command
and then press Enter.
./omutool backupcard 192.168.3.60 255.255.255.0

Step 10 Run the ./omutool hostname OMU name command to change the name of the OMU.
For example, you can run the following command and then press Enter to change the OMU
name to omu_123: ./omutool hostname omu_123.
Step 11 Set the work mode of the OMU according to the number of OMUa boards that are configured.
l If only one OMUa board is configured, run the ./omutool dualmode single command to set
the work mode to the single-server mode.
l If two OMUa boards (active and standby OMUa boards) are configured, run the ./omutool
dualmode dual command to set the work mode to the dual-server mode.
Step 12 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. Press Insert.
2. Set mlangflag to CHS or ENG by moving the cursor with arrow keys to change the
language used in the OMU.
BSC6900 GSM
4-7
3. Set runmode to or by moving the cursor with arrow keys to change the service mode of
the OMU.
4. Set officename by moving the cursor with arrow keys to change the name of the OMU.
5. Press Esc, input ;, and then input wq. Press Enter to change the reg.ini file.
NOTE
You can also copy the reg.ini 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 notepadm, 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 13 Run the /etc/rc.d/omud start command to start the OMU application.
Step 14 Run the ps -afx command to check the operating status of the OMU.
You can infer that the OMU is in normal state 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, and debug_log
Standby OMU software, ftp_server, sntp, omu_manager,
and debug_log

NOTE
If some of the processes do not exist, run the /etc/rc.d/omud restart command to restart the 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 15 Exit the OMU by referring to Logging Out of the OMU.
----End
4.2 Reinstalling Software on Site
When the OMUa board is damaged or the operating system collapses, you need to replace the
OMUa board or reinstall the operating system and OMU applications.
1. 4.2.2 Preparing the USB Installation Disk
This describes how to prepare the USB installation disk to quickly install, recover, and
switch the OMU operating system.
BSC6900 GSM
Issue 01 (2010-04-10)
2. 4.2.3 Installing the Operating System Through the USB Installation Disk
This describes how to install the operating system on the OMU with the USB installation
disk.
3. 4.2.4 Optional: Installing the OMU Applications
If the OMU applications are not installed in the process of preparing the USB installation
CD-ROM, then the OMU applications must be installed manually after the OMU operating
system is installed.
4.2.1 Preparations for Installing Software on Site
Before you reinstall the OMU software on site, you should make ready the OMUa board, portable
computer, BSC6900 version installation package or patch installation package, and Dopra Linux
tool package.
Configurations of the OMUa Board
See the hardware configuration indexes of the OMUa board described in 2.2.5 Technical
Specifications of the OMUa/OMUb Board.
Configuration Requirements of the Portable Computer
Table 4-1 lists the configuration requirements of the portable computer.
Table 4-1 Configuration requirements of the portable computer
Item Quantity Recommended
Configuration
Minimum Configuration
CPU 1 1.66 GHz or faster 866 MHz
RAM 1 512 MB 256 MB
Hard disk 1 80 GB 10 GB
Display
adapter
resolutio
n
- 1024x768 pixels or higher 800600
CD drive 1 - -
USB
installati
on disk
1 - -
Operatin
g system
- Microsoft Windows XP
Professional or Microsoft
Windows Server 2003
-

Software to Be Made Ready
Ensure that the following software is available:
BSC6900 GSM
4-9
l BSC6900 version installation package or patch installation package
l Dopra Linux tool package
NOTE
l Log in to http://support.huawei.com/support/ and choose Software Center > Version Software >
Wireless > Single RAN > MBSC > BSC6900 > BSC6900 Product Version > BSC6900 Software
Version.
l Choose Software Version linux or Software Version windows to obtain the BSC6900 version
installation package.
l Choose Software Version Offline Tools to obtain the Dopra Linux tool package.
4.2.2 Preparing the USB Installation Disk
This describes how to prepare the USB installation disk to quickly install, recover, and switch
the OMU operating system.
Prerequisite
l The capacity of the USB disk is 2 GB at least. If the BSC6900 is configured with active/
standby OMUs, two USB disks are needed.
l The USB disk is inserted in an available USB port on the portable computer.
l The USB port on the portable computer can be read and written.
l The planned IP addresses and OMU name are obtained.
Context
The USB installation disk can be used to install the OMU operating system or 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 the USB
installation disk is prepared.
The USB installation disk is used in the following scenarios:
l Initial installation of the OMU operating system and applications
l Recovery of the collapsed OMU operating system
l Switch the current OMU operating system to the target operating system.
NOTE
The operating system of the BSC6000 is Suse Linux and that of the BSC6900 is Dopra Linux. After the
BSC6000 is upgraded to the BSC6900, the OMU operating system needs to be switched.
When the USB installation disk is used to perform operations on the OMU, the data on the OMU
is impacted:
l If the OMU operating system is installed through the USB installation disk, the OMU hard
disk is formatted, and thus the OMU data is lost. Make sure you have backed up the OMU
data before you install the OMU operating system through the USB installation disk.
l If the operation mode of the USB installation disk is Recover, then only the OMU operating
system is recovered, and the OMU applications and configuration data are reserved.
l If the operation mode of the USB installation disk is Switch, then all the OMU data is re-
moved to the new operating system smoothly, and the OMU application data is reserved.
BSC6900 GSM
Issue 01 (2010-04-10)
NOTE
This task takes preparing the USB installation disk in active/standby mode as an example. Differences of the
task between in dual-OMU mode and in single-OMU mode are specified.
Procedure
l Preparing the USB installation disk for the initial installation of the OMU operating system
and applications
1. Double-click U_creator_eng.exe to open the Dopra Linux tool package, as shown in
Figure 4-3.
Figure 4-3 U_creator_eng window

2. Select NE List in the area on the left pane of the window shown in Figure 4-3, right-
click the NE list, and choose Add NE. A dialog box is displayed, as shown in Figure
4-4.
BSC6900 GSM
4-11
Figure 4-4 Add NE dialog box

3. Enter the NE Name, set the Operate type to Install, select Install OMU?, and click
OK. An NE is added.
NOTE
l If the OMU applications are 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.
l If you want to prepare multiple USB disks, it is recommended that you prepare the USB disks
one by one, and make marks for the disks.
4. Double-click the added NE on the left pane of the window. The window is updated,
as shown in Figure 4-5.
BSC6900 GSM
Issue 01 (2010-04-10)
Figure 4-5 Configuring information

NOTE
If Install OMU ? is not selected in Step 3, only the names of the active and standby OMUs and IP
addresses are displayed in the Figure 4-5.
5. After all the information are automatically obtained, check whether the information
is correct and enter the information that needs to be typed.
NOTE
l If a patch needs to be installed, select a patch installation package.
l The downloaded patch installation package must be saved in the patch folder of the version
installation package.
l Choose the patch folder when selecting a patch installation package.
6. Check that all the information is correct and click OK to start preparing the USB
installation disk.
BSC6900 GSM
4-13
7. Perform operations by following the instructions till the system prompts that Succeed
to create USB drive of OMU installation.. Click Finish to finish preparing the USB
installation disk.
NOTE
l When the system prompts a message, asking you to check the preparing of the USB installation
disk, you can insert or remove the USB disk.
l If only one OMU is configured, the standby OMU USB installation disk need not be prepared.
l Preparing the USB installation disk for restoring the OMU operating system
1. Double-click U_creator_eng.exe to open the Dopra Linux tool package, as shown in
Figure 4-3.
2. Select NE List in the area on the left pane of the window shown in Figure 4-3, right-
click the NE list, and choose Add NE. A dialog box is displayed, as shown in Figure
4-6.
Figure 4-6 Add NE dialog box

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 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.
l If you want to prepare multiple USB disks, it is recommended that you prepare the USB disks
one by one, and make marks for the disks.
4. Double-click the added NE on the left pane of the window. The window is updated,
BSC6900 GSM
Issue 01 (2010-04-10)
Figure 4-7 Configuring information

5. After all the information are 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 to start preparing the USB
installation disk.
7. Perform operations by following the instructions till the system prompts that Succeed
to create USB drive of OMU installation.. Click Finish to finish preparing the USB
installation disk.
NOTE
l When the system prompts a message, asking you to check the preparing of the USB installation
disk, you can insert or remove the USB disk.
l If only one OMU is configured, the standby OMU USB installation disk need not be prepared.
l Preparing the USB installation disk for switching the OMU operating system
The procedure of creating a USB installation disk for switching the OMU operating system
is almost the same as the procedure of creating a USB installation disk for restoring the
OMU operating system except that you should set the Operate type to Switch in Step 3.
----End
4.2.3 Installing the Operating System Through the USB Installation
Disk
This describes how to install the operating system on the OMU with the USB installation disk.
BSC6900 GSM
4-15
Prerequisite
l The USB installation disk is prepared. For details, see 4.2.2 Preparing the USB
Installation Disk.
l There are USB ports available on the OMUa board panel.
NOTE
The USB disk with LED is inserted into the USB port. If the LED is on, then the USB port is available.
Procedure
Step 1 Insert the USB installation disk into any of the USB ports on the OMUa board panel.
Step 2 Press the SHUTDOWN button on the OMUa board panel to reset the OMUa board.
Step 3 Check whether the OMU operating system is successfully installed through either of the
following methods.
l Method 1: Wait for 5-10 minutes to view the state of the LEDs on the OMUa board panel.
NOTE
The state of the LEDs on the OMUa board panel can be: RUN LED flashes, ALM LED flashes, ACT LED
flashes, and OFFLINE LED is off.
Option Description
All the following conditions are met:
l RUN LED flashes.
l ALM LED is off.
The OMU operating system is installed
successfully.
The RUN LED is off or the ALM LED
flashes
The installation of the OMU operating system
fails.
l Method 2: Connect the display to the VGA port on the OMU board panel. The OMU
operating system is successfully installed if the following message is displayed:
Please login from TTY2(Press ALT-F2).
l Method 3: Wait for 5 to 10 minutes. If you log in to the OMU successfully, the OMU
operating system is installed successfully.
CAUTION
Remove the USB installation disk from the panel of the OMUa board/OMUb board/GBAM
immediately after the OMU operating system is installed successfully.
----End
Postrequisite
If the OMU operating system fails to be installed, perform the following operations:
1. Prepare a new USB installation disk. For details, see 4.2.2 Preparing the USB Installation
Disk.
BSC6900 GSM
Issue 01 (2010-04-10)
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.
4.2.4 Optional: Installing the OMU Applications
If the OMU applications are not installed in the process of preparing the USB installation CD-
ROM, 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.
l 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 V900R011C00 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, or
debugging IP address of the OMU.
----End
Logging In to the OMU
After you log in to the OMU by running the SSH (Secure Shell) terminal (through the PuTTY
software, for example) on a computer, you can perform OM on the OMU.
Prerequisite
The computer for logging in to the OMU is connected to the OMU properly.
Procedure
Step 1 Run the SSH terminal, PuTTY, for example, on the computer, and then enter the IP address of
the OMU.
BSC6900 GSM
4-17
NOTE
l Before the OMU applications are started, 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 preferential.
l In local commissioning scenario, you should enter the debugging IP address of the OMU.
Step 2 Log in to the OMU as user root.
NOTE
The user name is root and the default password is huawei.
----End
Uploading the OMU Application Installation Package to the OMU
Before installing the OMU applications, you must upload the OMU application package to the
specified directory of the OMU.
Prerequisite
l Log in to http://support.huawei.com/support/. Choose Software Center > Version Software
> Wireless Product Line > Single RAN > MBSC > BSC6900, to download the OMU
application installation package.
l The psftp software is obtained. For details about the psftp software, see 4.4.1 psftp
Software.
Context
l The OMU application installation package must be uploaded to the \mbsc\upgrade
directory of the OMU.
l The OMU application installation package must be named after the version number. That
is, after the OMU application installation package is uploaded to the OMU, the structure
of the directory of the OMU is "mbsc\upgrade\V900R011C**."
NOTE
This task takes uploading the V900R011C00 version installation package to the \mbsc\upgrade directory of
the OMU and downloading version files from http://support.huawei.com/support/ to local drive D as an example.
Procedure
Step 1 Decompress the BSC6900 version installation package to the local drive D.
Step 2 Log in to the OMU through the psftp software. For details about the psftp software, see 4.4.1
psftp Software.
Step 3 Run the lcd D:\ command to go to the directory on the local PC where the version files are saved.
Step 4 Run the ls /mbsc/upgrade command to query whether there is an installation directory on the
OMU.
Option Description
If the /mbsc/upgrade directory does not exist, Go to Step 5.
BSC6900 GSM
Issue 01 (2010-04-10)
Option Description
If the /mbsc/upgrade directory exists, Go to Step 6.
Step 5 Run the mkdir /mbsc/upgrade command to create installation directory on the OMU.
Step 6 Run the cd /mbsc/upgrade command to go to the OMU installation directory.
Step 7 Run the put -r V900R011C00 command to upload the OMU application installation package
to the OMU.
Step 8 After the loading is complete, enter the exit command to exist the psftp software.
----End
Installing the OMU Applications in the Active Workspace
This describes how to install the OMU applications in the active workspace. If the BSC6900 is
configured with two OMUa boards, you need to install the OMU applications in the active
workspaces of both the boards.
Prerequisite
You have logged in to the OMU remotely. For details, see Obtaining the Information About
OMU Software Installation.
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.
Procedure
Step 1 Log in to the OMU through the external fixed 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/V900R011C00/install/setup. Run the following command and press Enter:
cd /mbsc/upgrade/V900R011C00/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 Figure 4-8.
Figure 4-8 Setting the run mode of product
# 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 :
Step 4 Type the product running mode and press Enter. The system prompts you to enter the office
name, as shown in Figure 4-9.
BSC6900 GSM
4-19
Figure 4-9 Setting the office name
# 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 Figure 4-10.
Figure 4-10 Setting the language
# 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 Figure 4-11.
Figure 4-11 Setting the admin password
# The "admin" user's password of OMU service.
# The password must range from 6to 32characters 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,
Figure 4-12 Setting the FTP password
# The ftp user's password of OMU service
# The password must range from 6to 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 client
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 Figure 4-13.
Figure 4-13 Setting the external virtual IP address
# The virtual extranet ip.
Please input a valid virtual_extranet_ip :
Step 9 Type the external virtual IP address and press Enter. The system prompts you to enter the OMU
system type, as shown in Figure 4-14.
Figure 4-14 Setting the OMU system type
# The OMU system type. eg: Single/Dual
# Single:Install stand-alone system
# Dual:Install dual-OMU system.
BSC6900 GSM
Issue 01 (2010-04-10)
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 according to the actual conditions and press Enter. Table 4-2
describes the OMU installation types.
Table 4-2 Description
Parameter Meaning
Single When the BSC6900 is configured with one
OMUa board, install the OMU applications
on the board in single-OMU mode.
Dual When the BSC6900 is configured with two
OMUa 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 Figure 4-15.
Figure 4-15 Confirming the installation
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, you can infer that the OMU applications are successfully installed.
Step 13 Record the information about the installation of the OMU applications in 4.5.1 Records of OMU
Software Installation Information.
----End
Postrequisite
1. After the OMU applications are installed, change the IP addresses and name of the OMU
as required by the operator planning. For details, see Changing the IP Addresses and
Masks of the OMU Ethernet Adapters and Changing the OMU Name.
2. Remotely log in to the Linux operating system by referring to Starting the omud.
3. Update the OMU database by referring to Updating the OMU Database.
4. Activate and verify the license by referring to Activating and Verifying the License.
5. Load the BSC6900 board software and data files by referring to Loading BSC6900 Board
Software and Data Files.
Checking the Installation Directory of the OMU Applications
The installation directory of the OMU applications is under /mbsc/bam by default after the
OMU applications are installed. The following items are stored in the installation directory of
the OMU applications: the OMU application components, the BSC6900 host software, and data
used or generated by the BSC6900.
Background Information
The default installation directory for the OMU applications is /mbsc/bam/. You are not allowed
to change the directory.
BSC6900 GSM
4-21
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 the same as that shown in Figure 4-16
and Figure 4-17.
Directory Structure
l Figure 4-16 shows the directory structure of the OMU applications when they are installed
only in the active OMU workspace for the first time.
l If the OMU applications are installed on both the active workspace and the standby
workspace, the directory structure is as shown in Figure 4-17. The structures of the
version_a and version_b folders are the same.
NOTE
l The version_a and version_b folders save active/standby OMU workspace files.
l You can run the LST OMUAREA command to query the OMU workspaces. If the Workarea flag is
version_a, you can infer that the version_a folder saves active workspace files.
l Figure 4-16 and Figure 4-17 show the directory structure of the OMU applications.
Figure 4-16 Directory structure of OMU applications on the active workspace

BSC6900 GSM
Issue 01 (2010-04-10)
Figure 4-17 Directory structure of OMU applications on the active and standby workspaces

CAUTION
Do not delete any file in the installation directory of the OMU applications to avoid any severe
impact on the BSC6900 system.
File Folders
Table 4-3 lists the file folders of the OMU application directory.
Table 4-3 File folders of the OMU application directory
File folder Description
common/ems Stores the M2000-related data
common/fam Stores log files and performance measurement file of the
host
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
version_a/bin/bam Stores the program files, configuration files, and patch files
for the OMU
version_a/bin/fam Stores the program files and data files of the host
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.
BSC6900 GSM
4-23
File folder Description
data_restore/mml
Stores the configuration data downloaded from the M2000
in MML format for restoration.
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/pcu_file Stores data files reported by the host
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/export_logfile Stores exported OMU operation log files
version_a/ftp/license Stores the inactivated license files
version_a/ftp/MeasDefinition Stores the performance measurement task files and
measurement definition files in multi-mode
version_a/ftp/MeasResult Stores performance measurement result files
version_a/ftp/n3gcs Stores temporary measurement task files
version_a/ftp/oprator_log Stores operation log files and security log files of the
standby OMU
version_a/ftp/trace Stores traced message files
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 help file associated with the LMT
upgrade Stores the software package of the version to be upgraded

Logging Out of the OMU
This describes how to log out of the OMU after you have finished operating and maintaining
the OMU through PuTTY.
Prerequisite
You have logged in to the OMU by referring to Logging In to the OMU.
BSC6900 GSM
Issue 01 (2010-04-10)
Procedure
Step 1 Run the exit command to terminate the PuTTY software.
----End
4.3 Operating and Maintaining the OMU
4.3.1 Querying the Configuration of the OMU Ethernet Adapters
This section describes how to query the configuration of OMU Ethernet adapters to learn the
mapping between physical OMU Ethernet adapters and logical Ethernet adapters.
4.3.2 Querying the Network Configuration of the OMU Ethernet Adapters
This section describes how to query the network configuration of the OMU Ethernet adapters
to obtain the IP addresses, broadcast IP addresses, and masks of the six OMU Ethernet adapters.
4.3.3 Checking the version of the Operating System
This describes how to check that the version of the operating system on the OMUa board is
correct.
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. Such an 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.
4.3.5 Changing the Administrator Password of the Operating System
This describes how to change the password of the Dopra Linux operating system administrator
to ensure the security of the administrator account.
4.3.6 Setting the 1st Boot Device of the OMU to USB
You should check that the 1st boot device of the OMUa board is USB before installing the Dopra
Linux operating system through the USB installation disk.
4.3.7 Maintaining the OMU Routinely
This 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.
4.3.8 Managing the Operating Status of the OMU
This describes how to manage the operating status of the OMU by running MML commands.
4.3.9 Managing the OMU Applications
This section describes how to manage the OMU applications.
4.3.10 Backing Up and Restoring Data
This 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.
4.3.11 Using the omutool
BSC6900 GSM
4-25
This 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 masks of the internal and external
networks, and admin password.
4.3.1 Querying the Configuration of the OMU Ethernet Adapters
This section describes how to query the configuration of OMU Ethernet adapters to learn the
mapping between physical OMU Ethernet adapters and logical Ethernet adapters.
Prerequisite
The OMU applications are installed. For details, see Installing the OMU Applications in the
Active Workspace.
Procedure
Step 1 You have logged in to the OMU. For details, see Logging In to the OMU.
Step 2 Type the /root/eth_alias_omu.sh command and press Enter to query the configuration
information of the Ethernet adapters before delivery. Figure 4-18 shows the factory settings of
the OMU Ethernet adapters.
Figure 4-18 Factory settings of the OMU Ethernet adapters (example)
eth0 06,0,0 ETH4-SCU7
eth2 04,4,0 ETH2
eth3 04,4,1 ETH3-Update
eth4 08,4,0 ETH0
eth5 08,4,1 ETH1
NOTE
The three columns of the configuration of OMU Ethernet adapters are detailed 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 of the OMU Ethernet adapters
to obtain the IP addresses, broadcast IP addresses, and masks of the six OMU Ethernet adapters.
Prerequisite
Active Workspace.
BSC6900 GSM
Issue 01 (2010-04-10)
Procedure
Step 1 You have logged in to the OMU. For details, see Logging In to the OMU.
Step 2 Type the ifconfig bond1 command and press Enter to query the external fixed IP address,
broadcast IP address, and mask. Figure 4-19 shows the network configuration of the OMU
Ethernet adapters.
Figure 4-19 Network configuration of the OMU Ethernet adapters (example)
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 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 for the backup channel between the active OMU
and the standby OMU, broadcast IP address, and mask.
----End
4.3.3 Checking the version of the Operating System
This describes how to check that the version of the operating system on the OMUa board is
correct.
Prerequisite
You have logged in to the LMT.
Procedure
Step 1 Run the MML command LST VER to check whether the OS type is 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. Such an 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.
BSC6900 GSM
4-27
Prerequisite
You have logged in to the OMU by referring to Logging In to the OMU through the external
fixed IP address.
Context
CAUTION
l Improperly changing the IP addresses of the Ethernet adapter team leads to network failure.
You must follow the instructions.
l 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.
l 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.
Procedure
l Change the external fixed IP address after the OMU applications are operating normally.
1. Stop the omud by referring to Stopping the omud.
2. Change the external fixed IP address by referring to Changing the 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 the
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.
l Replace the OMUa board and reconfigure the IP addresses of the internal and external
Ethernet adapter team.
1. Replace the OMUa board by referring to 2.2.6 Replacing an OMU Board.
NOTE
Replace the OMUa board and reconfigure the IP address of the internal Ethernet adapter team.
Ensure that you know the active/standby state of the OMUa board to be replaced and the new
OMUa board, to avoid the 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.
2. Change the IP addresses of the external Ethernet adapter team, internal Ethernet
adapter team, and backup channel by referring to Changing the 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
BSC6900 GSM
Issue 01 (2010-04-10)
4.3.5 Changing the Administrator Password of the Operating
System
Prerequisite
The OMUa board works normally, which is displayed on the device panel of the LMT.
Procedure
Step 2 Run the passwd root command (take user root as an example). A message is displayed, asking
you to enter the password, as shown in Figure 4-20.
Figure 4-20 Changing the password
Changing password for root. New password:
Step 3 Type 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 the 1st Boot Device of the OMU to USB
You should check that the 1st boot device of the OMUa board is USB before installing the Dopra
Linux operating system through the USB installation disk.
Prerequisite
l A keyboard and a monitor are ready.
l The USB disk is inserted in the USB port on the OMUa board.
Procedure
Step 1 Connect the keyboard and monitor to the OMUa board.
Step 2 Press the RESET button on the panel of the OMUa board to reset the OMU locally. The BIOS
Setup window is displayed on the monitor, as shown in Figure 4-21.
Figure 4-21 BIOS Setup
BSC6900 GSM
4-29

Step 3 Press the DEL button to enter BIOS setup.
Step 4 Select the Boot tab, as shown in Figure 4-22.
Figure 4-22 Boot tab page

Step 5 Use the direction arrows on the keyboard to select Boot Device Priority and press Enter.
Step 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 4-23.
BSC6900 GSM
Issue 01 (2010-04-10)
Figure 4-23 Selecting the 1st boot device

Step 7 Press F10 to save the setting and exit.
----End
4.3.7 Maintaining the OMU Routinely
normally.
Regularly Checking and Cleaning Up the OMU Hard Disk
This 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%.
Prerequisite
You have logged in to the LMT. For details, see LMT Login and Exit.
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.
BSC6900 GSM
4-31
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 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.
Prerequisite
l The firewall on the portable computer is disabled.
l The user password for FTP is obtained. For details, see 4.5.1 Records of OMU Software
Installation Information.
l 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
l Running commands
Table 4-4 describes the commands that are used for downloading files.
Table 4-4 Commands frequently used on the FTP
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)
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.
BSC6900 GSM
Issue 01 (2010-04-10)
2. Right-click 123.xml and choose Download.
l 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 the 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 previous table.
6. Transfer the file.
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.

7. 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 Figure 4-24.
Figure 4-24 Operation example
C:\Documents and Settings>d:
D:\>ftp 10.161.21.3
Connected to 10.161.21.3.
220ftp server ready.
User (10.161.21.3:(none)): FtpUsr
331Password required for FtpUsr.
Password:
230User logged in.
ftp> cd /mbsc/bam/version_a/bin/bam
250CWD successful.
ftp> put 123.xml
200PORT command OK.
150Opening BINARY mode data connection for '/123.xml' (104bytes)
226Transfer complete.
ftp> quit
D:\>
4.3.8 Managing the Operating Status of the OMU
This describes how to manage the operating status of the OMU by running MML commands.
BSC6900 GSM
4-33
Querying the Operating Status of the OMU
This describes how to query the operating status of the OMU subsystem and the service
processes, and the status of the board.
Prerequisite
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.
l 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.
l Query the status of the OMUa board.
1. Run the DSP OMUSRV command. The information related to the OMUa board 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 OMUa Board
This section describes how to query the working environment, hardware state, and version of
the OMUa board.
Prerequisite
Context
When a fault occurs on the OMUa board, you can query the information about the OMUa board
for fault location.
Procedure
l Query the working environment of the OMUa board.
BSC6900 GSM
Issue 01 (2010-04-10)
1. Run the DSP OMUENV command. The voltage and temperature of the CPU, hard
disk, and chips are displayed.
l Query the hardware information about the OMUa board.
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
OMUa board are displayed.
The hardware of the OMUa board 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 OMUa
board.
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 OMUa board.
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 describes how to query the version of the active and standby OMU workspaces, such as
the workspace flag and version of the OMU applications.
Prerequisite
Procedure
Step 1 Run the LST OMUAREA command to query the version of the active and standby OMU
workspaces.
----End
Querying the Status of the Data Synchronization Between the Active OMU and the
Standby OMU
This describes how to query the status of the data synchronization between the active OMU and
the standby OMU.
Prerequisite
l You have logged in to the LMT.
l The OMUs work in active/standby mode.
BSC6900 GSM
4-35
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 initial or Data
synchronization fault, the active and standby OMUs cannot be switched over.
----End
Checking the Data Consistency Between the Active OMU and the Standby OMU
This describes how to check the data consistency between the active OMU and the standby OMU
after a fault-triggered switchover occurs.
Prerequisite
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.
l If the active OMU data is consistent with the standby OMU data, run the STR
DATASYNC command to start the data synchronization between the active OMU and the
standby OMU.
l If the active OMU data is consistent with the standby OMU data, run the CMP
OMUDATA command five minutes later.
CAUTION
If the active OMU is synchronizing the initial data with the standby OMU, the LMT displays
failure information.
BSC6900 GSM
Issue 01 (2010-04-10)
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 board is exhausted. In this situation, you
need to replace the battery and then re-set the OMU time and change the OMU time zone.
Prerequisite
l You have obtained the time and time zone.
Context
The OMU time and time zone are set by default before the OMUa board is delivered.
The OMU time indicates the time on the OMU operating system, and the OMU time zone
indicates the time zone on the OMU operating system.
Procedure
l Change the OMU time
1. Run the SET TIME command to change the OMU date and time.
l Change the OMU time zone
1. Run the SET TZ command to change the OMU time zone.
----End
Switching Over the Active/Standby OMU Workspaces
This describes how to switch over the active and standby OMU workspaces for OMU version
upgrade and rollback.
Prerequisite
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
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.
BSC6900 GSM
4-37
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.
l 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.
3. Run the RST BSC command to reset the BSC so that the OMU data is consistent with
the host data.
----End
Forcibly Switching Over the Active and Standby OMUs
This 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.
Prerequisite
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.
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 describes how to reset the OMUa board, OMU applications, and OMU service processes.
BSC6900 GSM
Issue 01 (2010-04-10)
Prerequisite
Context
l The OMU operating system is restarted after the OMUa board is reset. If the OMUa board
is reset successfully, the faults of the OMU operating system or applications can be rectified.
l All the service processes are disrupted after the OMU applications are reset. If the OMUa
board is reset successfully, the faults of the OMU applications can be rectified.
l Resetting a specified OMU service process interrupts the service of the process for a while.
Procedure
l Reset the OMUa board/OMU applications
1. Run the RST OMU command.
If Reset Type is set to SOFT, only the OMU applications are reset. The OMU
operating system is not restarted.
If Reset Type is set to HARD, the OMU operating system is restarted.
NOTE
l When the OMU works in single-OMU mode, 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.
l Reset a specified service process
1. Run the RST OMUMODULE command and specify Reset Target and Module
Name to reset the specified OMU service process.
----End
Querying the Operating Status of the omud
This section describes how to query the operating status of the omud to determine whether the
OMU can provide services normally.
Prerequisite
Procedure
Step 1 Run the /etc/rc.d/omud status command to query the operating status of the omud.
BSC6900 GSM
4-39
Option Description
If the operating status of the omud is
running,
Then it shows that the OMU is working.
unused,
Then it shows that the OMU stops working.
----End
Starting the omud
This section describes how to start the omud so that the OMU provides services normally.
Prerequisite
l The OMU applications are installed. For details, see Installing the OMU Applications in
the Active Workspace.
l The omud is not running. For details on how to query the omud status, see Querying the
Operating Status of the omud.
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.
Prerequisite
Active Workspace.
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
disrupted if you have logged in to the OMU through the external virtual IP address.
BSC6900 GSM
Issue 01 (2010-04-10)
Procedure
In to the OMU.
Step 2 Type the /etc/rc.d/omud stop command and press Enter to stop the omud.
----End
Uninstalling the OMU Applications
The OMU applications must be uninstalled when the OMU applications are incorrectly installed.
Prerequisite
l The OMU applications are installed.
l The data is backed up. For details, see Backing Up the System Data.
Context
l 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 the OMU
applications on the active workspace.
l When the BSC6900 is configured with active and standby OMUs, uninstall the OMU
applications on both the active and standby OMUs.
Procedure
Step 1 Log in to the standby OMU through the external fixed IP address by referring to Logging In to
the OMU.
Step 2 Stop the omud by referring to Stopping the omud.
Step 3 Type uninstall_bam on any directory of the OMU, and press Enter.
Step 4 The system prompts a message that Uninstall standby area. input Y to continue; input E to
exit.. Enter Y to uninstall the OMU applications on the standby workspace of the OMU.
Step 5 Enter the uninstall_bam command and press Enter.
Step 6 The system prompts a message that Uninstall main area. input Y to continue; input E to
exit.. Enter Y to uninstall the OMU applications on the active workspace of the OMU.
Step 7 Enter the exit command to log out of the OMU.
Option Description
If the OMU is in dual-OMU mode, Go to Step 8.
If the OMU is in single-OMU mode, End this task.
Step 8 Log in to the active OMU through the external fixed IP address by referring to Logging In to
the OMU. Then repeat Step 2 through Step 7 to uninstall the OMU applications on the active
OMU.
----End
BSC6900 GSM
4-41
data may be lost.
Context
The omu_backup_linker tool is used in the following scenarios:
l A damaged OMUa board is replaced with a new one, and the data on the damaged OMUa
board is backed up and restored on the new OMUa board.
l The OMU data is backed up in routine maintenance.
l The OMU database collapses or the OMU upgrade fails, and the latest OMU data is restored.
Starting the omu_backup_linker Tool
This 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.
Prerequisite
fixed IP address.
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,
Figure 4-25 Starting 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
Postrequisite
l Back up the system data through the omu_backup_linker by referring to Backing Up the
System Data.
l Restore the system data through the omu_backup_linker by referring to Restoring the
System Data.
Backing Up the System Data
This describes how to back up the BSC6900 configuration data, performance data, and alarm
data through MML commands or the omu_backup_restore_tool.
BSC6900 GSM
Issue 01 (2010-04-10)
Prerequisite
l If you perform this task by running the MML command, you need to log in to the LMT
first.
l Prerequisites for performing this task by omu_backup_restore_tool are as follows: You
have logged in to the OMU through the external fixed IP address by referring to Logging
In to the OMU.
Context
CAUTION
l When the OMU works in active/standby mode, the system data must be backed up on the
active OMU.
l You must back up the OMU data manually before expansion, upgrade or loading to avoid
the failure of system data backup.
Procedure
l Backing up the system data through an MML command
1. Run the BKP DB command, and then 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.
l Backing up the data by using the omu_backup_linker tool
1. Start the omu_backup_restore_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. A message "Backup OMU database
succeed!" is displayed, indicating that the system data is 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 Figure 4-26.
Figure 4-26 Example
omd_test_name /mbsc/bam/common/services # ./omu_backup_linker
BSC6900 GSM
4-43
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 #
Restoring the System Data
This describes how to restore the system data through the data backup file. The system data
consists of configuration data, performance data, and alarm data.
Prerequisite
l You have logged in to the OMU through the external fixed IP address by referring to
Logging In to the OMU.
Context
Restoring the BSC6900 system data will disrupt the services on the BSC6900 operation and
maintenance system. The data on the host may be inconsistent with the data on the BAM after
the system data is restored. Thus, the services will be greatly impacted. Therefore, you are
advised to restore the system data when the traffic volume is low.
Procedure
Step 1 Load the BSC6900 board software and data files by referring to Stopping the omud.
Step 2 Restore the system data through the omu_backup_linker.
1. Load the BSC6900 board software and data files by referring to Starting the
omu_backup_linker Tool.
2. Type restore and press Enter after the message "Please input a valid
3. Type 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 Load the BSC6900 board software and data files by referring to Starting the omud.
Step 4 Run the REQ CMCTRL command to obtain the data configuration rights.
Step 5 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.
BSC6900 GSM
Issue 01 (2010-04-10)
l If the data is consistent, end this task.
l If the data is inconsistent, go to Step 5.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 and
specify the Subrack No. to reset the subrack. 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 Figure 4-27:
Figure 4-27 Example
omd_test_name ~
# /etc/rc.d/omud stop
Shutting down mbsc daemon..........
omd_test_name ~ # cd /mbsc/bam/common/services
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
Starting the omutool
This 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 omu_backup_linker
tool.
Prerequisite
Active Workspace.
BSC6900 GSM
4-45
Context
You can perform tasks by running omutool commands attached with 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 command. The parameter information about the omutool is displayed.
----End
Setting the Working Mode of the OMU
This 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.
Prerequisite
l You have logged in to the OMU by referring to Logging In to the OMU through the
external fixed IP address.
l You have logged in to the LMT, and queried the slot No. for the OMUa board through the
LST BRD command.
l You have logged in to the LMT, and run the DSP OMU command to query whether the
OMU is in single or dual mode.
Context
l 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 dual-
OMU mode to single-OMU mode, apply the settings to only the working OMU.
l If the working mode of the OMU is changed from single-OMU mode to dual-OMU
mode, ensure that the version of the active OMUa board is the same as that of the standby
OMUa board. In addition, the slot number of the active OMUa board and the slot number
of the standby OMUa board are in active/standby mode, for example, slot 21 and slot 23.
l 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
synchronization is successful.
Procedure
l Switch the OMU from the single-OMU mode to dual-OMU mode (The OMU to be added
is installed with the OMU applications).
1. Insert an OMUa board into the standby slot by referring to Inserting a Board.
BSC6900 GSM
Issue 01 (2010-04-10)
2. Log in to the standby OMU through the external fixed IP address by referring to
Logging In to the OMU, and then install the OMU applications on the active
workspace of the standby OMU by referring to Installing the OMU Applications in
NOTE
l You must select dualmode in the process of installing the OMU applications.
l If the OMU is installed with a patch, you need to copy the bin file to the active workspace of
the standby OMU through 4.4.1 psftp Software.
3. Change the IP addresses and masks of the OMU Ethernet adapters by referring to
Changing the 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 in
case that the two OMUs compete for active state. Thus, data loss can be avoided.
9. Run the ADD BRD command on the LMT to add an OMUa board.
is not installed with the OMU applications).
1. Log in to the original working OMU through the external fixed IP address by referring
to Logging In to the OMU, and then stop the omud on the original working OMU
by referring to Stopping the omud.
omutool.
5. After the original working OMU is started for five minuets, add an OMUa board to
the slot for the standby OMUa board by referring to Inserting a Board, and then start
the omud on the standby OMU by referring to Starting the omud.
BSC6900 GSM
4-47
WARNING
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 OMUa board.
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 OMUa board by referring to Replacing the OMUa Board.
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 the IP Addresses and Masks of the OMU Ethernet Adapters
This describes how to change the IP addresses and masks of the OMU Ethernet adapters.
Prerequisite
l The omutool is started. For details, see Starting the omutool.
Context
In dual-OMU mode, change the IP addresses and masks of the Ethernet adapters on both the
active and standby OMUs.
NOTE
This task describes the method of changing all the IP addresses and masks of the OMU. You can perform certain
steps according to the planning of the IP addresses on site.
Procedure
Step 1 Stop the omud on the target OMU by referring to Stopping the omud.
BSC6900 GSM
Issue 01 (2010-04-10)
Step 2 ETH4-SCU7 and ETH5-SCU6 are teamed as the internal Ethernet adapter team. The ./omutool
innercard IP address mask command is used to change the internal fixed IP address and mask.
For example, type the following command and press Enter:
Step 3 The ./omutool innervip IP address mask command is used to change the internal virtual IP
address and mask.
Step 4 ETH0 and ETH1 are teamed as the external Ethernet adapter team. The ./omutool extercard
IP address mask (gateway) command is used to change the external fixed IP address and mask.
./omutool extercard 10.161.10.100 255.255.255.0
NOTE
To change the external fixed IP address and the gateway, you can 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.100255.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.
Step 6 ETH3-UPDATE serves as the backup Ethernet adapter of the OMU. The ./omutool backupcard
IP address mask command is used to change the IP address and mask of the backup channel
Step 7 ETH2 serves as the debugging Ethernet adapter of the OMU. The ./omutool debugcard IP
address mask command is used to change the debugging IP address and mask.
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 mask.
l Record the new IP addresses in 4.5.1 Records of OMU Software Installation Information.
Step 8 Start the omud by referring to Starting the omud to validate the new admin password.
----End
Changing the admin Password
This describes how to change the admin password by using the omutool.
BSC6900 GSM
4-49
Prerequisite
l You have started the omutool by referring to Starting the omutool.
Context
admin is the account for the administrator to log in to the LMT.
Procedure
Step 1 Stop the omud on the OMU by referring to Stopping the omud.
Step 2 Run the ./omutool adminpwd Password command to change the admin password.
For example, to change the admin password to 111111, type the ./omutool adminpwd
111111 command and press Enter.
----End
Changing the OMU Name
This section describes how to change the OMU name through omutool.
Prerequisite
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 the IP Addresses and Masks of the
OMU Ethernet Adapters.
Procedure
Step 1 Load the BSC6900 board software and data files by referring to 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
BSC6900 GSM
Issue 01 (2010-04-10)
Postrequisite
1. Run the DSP OMU command to query the new name.
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 describes how to obtain and use the psftp software to upload the OMU application
installation package to the OMU.
4.4.2 PuTTY Software
This describes how to obtain and use the PuTTY software to log in to the OMU.
4.4.1 psftp Software
This describes how to obtain and use the psftp software to upload the OMU application
installation package to the OMU.
Prerequisite
l The PC is connected to the Internet.
l The OMUa board is installed with operating system.
Context
l The psftp software can be used to upload files to the OMU hard disk.
l The psftp software can also be used to download files from the OMU hard disk to a local
computer.
Table 4-5 lists the commands frequently used on the psftp software.
Table 4-5 Commands frequently used on the psftp software
cd Change the OMU directory cd /mbsc/upgrade
ls Query the structure of the
current directory
ls
lcd Go to the local folder lcd D:\BSC6900V900R011C00
\Software\setup\linux
get Transfer files from the
OMU to the local computer
To transfer a file, run the get
V900R011C00 command.
To transfer a folder, run the get -r
BSC6900 GSM
4-51
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 > Mini-tool software >
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-28.
Figure 4-28 Logging in to the OMU through the psftp software

Step 3 Type the open IP address command (10.161.21.203, for example) and press Enter. The system
prompts you to enter the user password, as shown in Figure 4-29.
Figure 4-29 Entering the user name password
psftp: no hostname specified; use "open host.name" to connect
BSC6900 GSM
Issue 01 (2010-04-10)
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:
Step 4 Enter the user name root and the user password to connect the psftp software to the OMU.
----End
4.4.2 PuTTY Software
This describes how to obtain and use the PuTTY software to log in to the OMU.
Prerequisite
l The PC is connected to the Internet.
l The OMUa board is installed with operating system.
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.
Procedure
Step 1 Log in to http://support.huawei.com/support/. Choose Software Center > Mini-tool software >
Core Network Product Line > Genex CN Nastar TOOL > Tools for remote login linux, to
download the PuTTY files.
Step 2 Double-click putty.exe. A dialog box PuTTY Configuration is displayed, as shown in Figure
4-30.
BSC6900 GSM
4-53
Figure 4-30 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) with the IP address of the OMUa board, and set Protocol to SSH.
NOTE
Specify the IP address based on the following table.
If... Then...
The PC is connected to ETH2 on the OMUa board
panel through an Ethernet cable,
The IP address is the debugging IP address of the
OMUa board.
The PC is connected to ETH0 or ETH1 on the
OMUa board panel through a network device,
The IP address is the external fixed IP address or
external virtual IP address of the OMU.

Step 4 Click Open. A window is displayed, as shown in Figure 4-31.
BSC6900 GSM
Issue 01 (2010-04-10)
Figure 4-31 Logging in to the OMUa board through PuTTY software

Step 5 Log in to the OMU as user root.
----End
4.5.1 Records of OMU Software Installation Information
The records of the OMU software installation information include the parameter configurations
during the installation of the OMU software.
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.
4.5.3 Enabled Ports on the OMU
This section lists the mapping between the enabled ports on the OMU and the services provided
by the OMU applications.
4.5.1 Records of OMU Software Installation Information
BSC6900 GSM
4-55
Records of OMU Operating System Installation Information
Item Configuration
Information
Installer
Computer name (active
OMU)

(active OMU)

Computer name (standby
OMU)

(standby OMU)

For details, see Record Sheet of OMU Operating System Installation Information.
Records of the IP Addresses of the OMU Ethernet Adapter Teams
Item Configuration
Information
Installer
Internal IP address (mask) of
the active OMU

External IP address (mask) of
the active OMU

Internal IP address (mask) of
the standby OMU

External IP address (mask) of
the standby OMU

Backup channel IP address
(mask) of the active OMU

Backup channel IP address
(mask) of the standby OMU

Debugging IP address (mask)
of the active OMU

Debugging IP address (mask)
of the standby OMU

Default gateway

For details, see Records of the IP Addresses of the OMU Ethernet Adapter Teams.
BSC6900 GSM
Issue 01 (2010-04-10)
Records of the OMU Application Installation Information
Item Configuration
Information
Installer
Administrator (admin)
password

Password of the FTP user
(FtpUsr)

Internal virtual IP address
External virtual IP address
Local office name

For details, see Records of the OMU Application Installation Information.
Checklist for the Factory Settings of the OMU Software
Item Remarks
Setting the RAID 1 between the two SAS hard
disks on the OMUa board
-
Setting OMU BIOS Set the first boot device of the OMU to USB
Installing the Dopra Linux operating system Set the password of the administrator of the
active and standby OMUs to "huawei"
Installing the IPMI driver -
Teaming the internal Ethernet adapter team The default IP address of the internal Ethernet
adapter team is 80.168.3.50 (255.0.0.0).
Teaming the external Ethernet adapter team The default IP address of the external
Ethernet adapter team is 172.121.139.201
(255.255.255.0).
Configuring backup channel IP address of the
The default backup channel IP address is
192.168.3.50 (255.255.255.0).
Configuring debugging IP addresses of the
The factory settings of the debugging IP
addresses of the active and standby OMUs are
both 192.168.6.50 (255.255.255.0).

For details, see Checklist for the Factory Settings of the OMU Software.
BSC6900 GSM
4-57
4.5.3 Enabled Ports on the OMU
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
Port
No.
Service
Process
Description Network
Protocol
Type
Network Segment
TCP UD
P
Int
ern
al
Ne
tw
ork
Ext
ern
al
Net
wo
rk
Local
Netwo
rk
20 FTP Server
data
Port for host loading, and
uploading and
downloading of software
and logs (in active mode)
Y - Y Y -
21 FTP Server
control
uploading and
and logs
Y - Y Y -
22 SSHD
(operating
system
service)
SSH port for remotely
logging in to the OMUa
board
Y - Y Y Y
1024-6
5535
FTP Server
data
uploading and
and logs (in passive mode)
Y - Y Y -
67 software Bootp Listen - Y Y - -
80 Web LMT Port for local maintenance
on the LMT
Y - - Y -
123 sntp Port for local interception
providing standard clock
synchronization
- Y Y - -
123 sntp Port for local interception
which synchronizes the
time of the OMU with that
of the server
- Y - Y -
1234 sntp Port for clock
synchronization of the host
and local interception
- Y Y - -
BSC6900 GSM
Issue 01 (2010-04-10)
Port
No.
Service
Process
Description Network
Protocol
Type
Network Segment
TCP UD
P
Int
ern
al
Ne
tw
ork
Ext
ern
al
Net
wo
rk
Local
Netwo
rk
1500 host_gate Port for communication
with the host
Y - Y - -
6000 ems_gate Port for maintenance Y - - Y -
6001 ems_gate Port for alarm console Y - - Y -
6006 ems_gate Port for maintenance Y - - Y -
6007 ems_gate Port for debugging console Y - - Y -
6022 ems_gate Port for equipment console Y - - Y -
6088 Remote
upgrade tool
Port for remote upgrade
tool
Y - - Y -
6093 Service
simulation
Port for service simulation Y - - Y -
6099 ems_gate Port for synchronizing the
OMU data with the M2000
data
Y - - Y -
6100 ems_gate Port for alarm box Y - - Y -
8000 ems_gate Port for maintenance (SSL
encryption)
Y - - Y -
8001 ems_gate Port for alarm console
(SSL encryption)
Y - - Y -
8006 ems_gate Port for maintenance (SSL
encryption)
Y - - Y -
8007 ems_gate Port for debugging console
(SSL encryption)
Y - - Y -
8022 ems_gate Port for equipment console
(SSL encryption)
Y - - Y -
8088 Remote
upgrade tool
Port for remote upgrade
tool (SSL encryption)
Y - - Y -
8093 Service
simulation
Port for service emulation
(SSL encryption)
Y - - Y -
BSC6900 GSM
4-59
Port
No.
Service
Process
Description Network
Protocol
Type
Network Segment
TCP UD
P
Int
ern
al
Ne
tw
ork
Ext
ern
al
Net
wo
rk
Local
Netwo
rk
8099 ems_gate Port for synchronizing the
OMU data with the M2000
data (SSL encryption)
Y - - Y -
8100 ems_gate Port for alarm box (SSL
encryption)
Y - - Y -
11774 monitor Port for dual-OMU - Y Y - -
11775 monitor Port for dual-OMU - Y - Y -
11776 monitor Port for backup channel of
the active and standby
OMUs
- Y - - Y
16002 ems_gate Port through which the
performance module
reports notification
messages
Y - - Y -
18002 ems_gate Port through which the
performance module
reports notification
messages (SSL
encryption)
Y - - Y -
Others
(reserve
d)
Third-party
software
Port for configuring tools - - - - -

For details, see Enabled Ports on the OMU.
NOTE
The local network segment refers to the network between the OMUs.
BSC6900 GSM
Issue 01 (2010-04-10)
5 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 GSMSite 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

l Operating system
The Suse Linux operating system is used.
l OMU applications
Based on the operating system, the OMU applications provide all types of service progress.
5.1 Software Installation After the Upgrade
This section describes the software installation policies after the BSC6000 is upgraded to the
BSC6900.
5.2 Routine OMU Maintenance After the Upgrade
BSC6900 GSM
OMU Administration Guide 5 Scenario: Upgrade from the BSC6000 to the BSC6900
5-1
normally.
5.3 OMU Operation and Maintenance After the Upgrade
5.4 Appendix: the SEK SetSuse Software
This describes how to install, use, and uninstall the SEK SetSuse software.
5.5 Appendix: Anti-Virus Software
Before installing the anti-virus software, refer to the Anti-Virus Software Installation Guide
provided by Huawei. Now the BSC6000 supports the anti-virus software installation:
TrendMicro Control Manager (TMCM) + ServerProtect for Linux 2.5. After the BSC6000 is
upgraded to the BSC6900, the anti-virus software installation is still supported.
5.6 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.
BSC6900 GSM
Issue 01 (2010-04-10)
5.1 Software Installation After the Upgrade
This section describes the software installation policies after the BSC6000 is upgraded to the
BSC6900.
5.1.1 Installing the Operating System
This section describes the installation policy for the OMU operating system after the
BSC6000 is upgraded to the BSC6900.
5.1.2 Installing the OMU Applications
This section describes the installation policy for the OMU applications after the BSC6000 is
upgraded to the BSC6900.
5.1.1 Installing the Operating System
This section describes the installation policy for the OMU operating system after the
BSC6000 is upgraded to the BSC6900.
Context
The operating system of the BSC6000 is Suse Linux and that of the BSC6900 is Dopra Linux.
After the BSC6000 is upgraded to the BSC6900, Suse Linux can keep functioning or be switched
to Dopra Linux.
Procedure
Step 1 Determine whether the operating system is to be switched.
Option Description
If Suse Linux is still used, Then skip the task.
If Windows Server 2003 is switched to
Dopra Linux,
Then prepare a USB disk for switching the OMU
operating system. For details, see 4.2.2
Preparing the USB Installation Disk.
Step 2 Install the OMU operating system through the USB installation disk by referring to 4.2.3
Installing the Operating System Through the USB Installation Disk.
----End
5.1.2 Installing the OMU Applications
This section describes the installation policy for the OMU applications after the BSC6000 is
upgraded to the BSC6900.
Prerequisite
The OMU Driver Upgrade Guide is obtained.
BSC6900 GSM
5-3
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.
l 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 anew or restored to history IP addresses as required on site.
l If patches are installed in the existing network, the patch installation package needs to be
copied to the patch folder of the version installation package before the reinstallation of the
OMU applications. In this way, when the OMU applications are reinstalled, patches are
reinstalled at the same time.
Procedure
Step 1 Install the OMU driver by referring to the OMU Driver Upgrade Guide.
NOTE
The OMU operating system may restart and thus operation and maintenance is disrupted if the version of the
Ethernet adapter driver and hard disk driver is too early.
Step 3 Upload the OMU application installation package to \mbsc\upgrade\BSC6000\data\mbsc
\upgrade of the OMU by referring to Uploading the OMU Application Installation Package
to the OMU.
Step 4 Install the OMU applications to the active workspace of the OMU 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 the 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 Routine OMU Maintenance After the Upgrade
normally.
BSC6900 GSM
Issue 01 (2010-04-10)
5.2.1 Regularly Checking and Cleaning Up the OMU Hard Disk
5.2.2 Transferring and Backing Up Files
5.2.1 Regularly Checking and Cleaning Up the OMU Hard Disk
Prerequisite
You have logged in to the LMT. For details, see LMT Login and Exit.
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:
(1) Back up the files on the partition that needs to the saved to a hard disk by
referring to 5.2.2 Transferring and Backing Up Files.
(2) Log in to the OMU by referring to Logging In to the OMU.
(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.
If the available space of each directory is equal to or more than 20%, end this task.
l Method 2
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 5.2.2 Transferring and Backing Up
Files.
If the usage of no hard disk partition exceeds 80%, go to Step 3.
3. Exit the OMU by referring to Logging Out of the OMU.
----End
5.2.2 Transferring and Backing Up Files
BSC6900 GSM
5-5
Prerequisite
l The firewall on the portable computer is disabled.
l The user password for FTP is obtained. For details, see 4.5.1 Records of OMU Software
Installation Information.
l 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
l Running commands
Table 5-1 describes the commands that are used for downloading files.
Table 5-1 Commands frequently used on the FTP
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)
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 123.xml and choose Download.
l 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 the Records of the OMU Application Installation Information.
BSC6900 GSM
Issue 01 (2010-04-10)
5. Go to the directory where the file to be transferred is saved by referring to the command
listed in the previous table.
6. Transfer the file.
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.

7. 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 Figure 5-2.
Figure 5-2 Operation example
C:\Documents and Settings>d:
D:\>ftp 10.161.21.3
Connected to 10.161.21.3.
220ftp server ready.
User (10.161.21.3:(none)): FtpUsr
331Password required for FtpUsr.
Password:
230User logged in.
ftp> cd /mbsc/bam/version_a/bin/bam
250CWD successful.
ftp> put 123.xml
200PORT command OK.
150Opening BINARY mode data connection for '/123.xml' (104bytes)
226Transfer complete.
ftp> quit
D:\>
5.3 OMU Operation and Maintenance After the Upgrade
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.
l If the OMU operating system is still Suse Linux, perform the steps in this section for the
OMU maintenance and operation.
BSC6900 GSM
5-7
Procedure
----End
5.3.1 Querying the Operating Status of the OMU
5.3.2 Querying the Information About the OMUa Board
the OMUa board.
5.3.3 Querying the Version of the Active/Standby OMU Workspaces
5.3.4 Querying the Status of the Data Synchronization Between the Active OMU and the Standby
OMU
the standby OMU.
5.3.5 Checking the Data Consistency Between the Active OMU and the Standby OMU
5.3.6 Changing the OMU Time and Time Zone
5.3.7 Changing the Administrator Password of the Operating System
5.3.8 Switching Over the Active/Standby OMU Workspaces
5.3.9 Forcibly Switching Over the Active and Standby OMUs
5.3.10 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.
5.3.11 Checking the Version of the Operating System
This section describes how to check the version of the OMU operating system.
5.3.12 Checking the OMU Hard Disk Partitions
This section describes how to check the OMU hard disk partitions and the capacity of each
partition.
5.3.13 Checking the OMU Memory Capacity
This section describes how to check the OMU memory capacity and usage.
5.3.14 Checking the OMU Ethernet Adapter Teams
BSC6900 GSM
Issue 01 (2010-04-10)
This section describes how to check the OMU Ethernet adapter teams and IP addresses of the
OMU Ethernet adapters.
5.3.15 Changing the Connection Mode of the OMU Ethernet Adapters
This section describes how to change the connection mode of the external Ethernet adapters of
the active/standby OMUs to match the connection mode of the switch in order to keep the normal
connection of the network.
5.3.16 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.
5.3.17 Resetting the OMU
5.3.18 Shutting Down the OMU
This section describes how to shut down the OMU by running a command or shutting down the
OMU hardware.
data may be lost.
5.3.1 Querying the Operating Status of the OMU
Prerequisite
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.
l 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.
BSC6900 GSM
5-9
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.
l Query the status of the OMUa board.
1. Run the DSP OMUSRV command. The information related to the OMUa board 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.3.2 Querying the Information About the OMUa Board
the OMUa board.
Prerequisite
Context
When a fault occurs on the OMUa board, you can query the information about the OMUa board
for fault location.
Procedure
l Query the working environment of the OMUa board.
1. Run the DSP OMUENV command. The voltage and temperature of the CPU, hard
disk, and chips are displayed.
l Query the hardware information about the OMUa board.
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
OMUa board are displayed.
The hardware of the OMUa board 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 OMUa
board.
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 OMUa board.
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
BSC6900 GSM
Issue 01 (2010-04-10)
5.3.3 Querying the Version of the Active/Standby OMU
Workspaces
Prerequisite
Procedure
Step 1 Run the LST OMUAREA command to query the version of the active and standby OMU
workspaces.
----End
5.3.4 Querying the Status of the Data Synchronization Between the
Active OMU and the Standby OMU
the standby OMU.
Prerequisite
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 initial or Data
synchronization fault, the active and standby OMUs cannot be switched over.
----End
BSC6900 GSM
5-11
5.3.5 Checking the Data Consistency Between the Active OMU and
the Standby OMU
Prerequisite
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.
l If the active OMU data is consistent with the standby OMU data, run the STR
DATASYNC command to start the data synchronization between the active OMU and the
standby OMU.
l If the active OMU data is consistent with the standby OMU data, run the CMP
OMUDATA command five minutes later.
CAUTION
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.3.6 Changing the OMU Time and Time Zone
Prerequisite
l You have obtained the time and time zone.
Context
The OMU time and time zone are set by default before the OMUa 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.
BSC6900 GSM
Issue 01 (2010-04-10)
Procedure
l Change the OMU time
1. Run the SET TIME command to change the OMU date and time.
l Change the OMU time zone
1. Run the SET TZ command to change the OMU time zone.
----End
5.3.7 Changing the Administrator Password of the Operating
System
Prerequisite
The OMUa board works normally, which is displayed on the device panel of the LMT.
Procedure
Step 2 Run the passwd root command (take user root as an example). A message is displayed, asking
you to enter the password, as shown in Figure 5-3.
Figure 5-3 Changing the password
Changing password for root. New password:
Step 3 Type 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.3.8 Switching Over the Active/Standby OMU Workspaces
Prerequisite
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
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.
BSC6900 GSM
5-13
Procedure
l Switch over the active/standby OMU workspaces in single-OMU mode.
OMU) to switch over the active and standby workspaces on the OMU.
l Switch over the active/standby OMU workspaces in dual-OMU mode.
1. Run the SWP OMUAREA command and set Target OMU to STANDBY (Standby
3. Run the RST BSC command to reset the BSC so that the OMU data is consistent with
the host data.
----End
5.3.9 Forcibly Switching Over the Active and Standby OMUs
Prerequisite
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.
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
BSC6900 GSM
Issue 01 (2010-04-10)
5.3.10 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.
Prerequisite
The IP addresses of the active and standby OMUs are obtained.
Context
This task is optional. Perform this task in the following scenarios:
l A single OMU is replaced by active and standby OMUs.
l The faulty standby OMU is replaced by a backup standby OMU.
l 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. A message is promoted, as
shown in Figure 5-4.
Figure 5-4 Message (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.3.11 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
on incorrect version of the OMU operating system, contact Huawei for technical support. For
details, see Contact Huawei Customer Service Center.
BSC6900 GSM
5-15
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.3.12 Checking the OMU Hard Disk Partitions
This section describes how to check the OMU hard disk partitions and the capacity of each
partition.
Procedure
Step 2 Run the df -h command to check the OMU hard disk partitions, as shown in Figure 5-5.
Figure 5-5 Checking the OMU hard disk partitions
Linux:~ # df -h
Filesystem Size Used Avail Use% Mounted on /dev/sda6 9.9G
1.8G 7.6G 20% / tmpfs 1013M 4.0K 1013M 1% /dev/shm /dev/
sda7 5.0G 904M 3.8G 19% /BSC6000
/dev/sda8 51G 1.4G 47G 3% /BSC6000/data
/dev/sda1 130M 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, data in this partition is reserved but used for version rollback.
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, data in this partition is reserved but used for version rollback. 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.3.13 Checking the OMU Memory Capacity
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 Figure
5-6.
BSC6900 GSM
Issue 01 (2010-04-10)
Figure 5-6 Checking the OMU memory capacity and usage (example)
Linux:~ # free -m
total used free shared buffers cached Mem: 2025
1848 177 0 75 1162
-/+ buffers/cache: 609
Swap: 2055 0 2055
NOTE
Data about the OMU memory is displayed in the "Mem" row.
----End
5.3.14 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.
Prerequisite
Active Workspace.
Procedure
Step 2 Run the ifconfig command to view the OMU Ethernet adapter teams, as shown in Figure 5-7.
Figure 5-7 Configuration of the OMU Ethernet adapters (example)
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 Link encap:Ethernet HWaddr 00:18:82:1B:5E:EE

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 Link encap:Ethernet HWaddr 00:18:82:1B:5E:EE
BSC6900 GSM
5-17
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
Base address:0xcf80 Memory:fdce0000-fdd00000

eth1 Link encap:Ethernet HWaddr 00:18:82:1B:5E:EE
Base address:0xcf00 Memory:fdc80000-fdca0000

eth2 Link encap:Ethernet HWaddr 00:18:82:1B:5E:F2
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX bytes:982582 (959.5 Kb) TX bytes:1377729 (1.3 Mb)
Interrupt:16

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

Interrupt:16

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:~ #
BSC6900 GSM
Issue 01 (2010-04-10)
NOTE
l For details on the mapping between the logical and physical OMU Ethernet adapters, see 5.3.15 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.3.15 Changing the Connection Mode of the OMU Ethernet
Adapters
This section describes how to change the connection mode of the external Ethernet adapters of
the active/standby OMUs to match the connection mode of the switch in order to keep the normal
connection of the network.
Prerequisite
The setting of the connection mode of the switch is complete.
Context
The connection mode information of the switch is obtained. You can obtain the information in
the following ways:
l Running the command associated with the connection mode of the switch
l Contacting the maintenance personnel on the switch side from the customer
The principles for setting the connection mode of the Ethernet adapters are as follows:
l If the connection mode of the switch is forced mode, the connection mode of the external
Ethernet adapters of the OMU must be set to forced mode.
l If the connection mode of the switch is adaptive mode, the connection mode of the external
Ethernet adapters of the OMU must be set to adaptive mode.
Procedure
l Query the configuration of the OMU external Ethernet adapters
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 Figure 5-8.
Figure 5-8 Mapping between the physical and logical Ethernet adapters
eth2 04,4,0 ETH2
eth3 04,4,1 ETH3-UPDATE
eth4 08,4,0 ETH0
eth5 08,4,1 ETH1
BSC6900 GSM
5-19
NOTE
The three columns of the configuration of OMU Ethernet adapters are detailed 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 in Figure 5-8, 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.
2. Run the ethtool eth4 command to query the connection mode of eth4, as shown in
Figure 5-9.
Figure 5-9 Connection setting of OMU Ethernet adapters
Linux:~ # ethtool eth4
Settings for eth4:
Supported ports: [ MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised link modes: 10baseT/Half 10baseT/Full
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
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. Run the ethtool -s eth4 speed 100 duplex full command to switch on the forced full-
duplex 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 Figure 5-10.
Figure 5-10 Checking the connection setting of OMU Ethernet adapters
Linux:~ # ethtool eth4
Settings for eth4:
BSC6900 GSM
Issue 01 (2010-04-10)
Supported ports: [ MII ]
Supported link modes: 10baseT/Half 10baseT/Full
Advertised link modes: 10baseT/Half 10baseT/Full
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Auto-negotiation: off
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.
----End
5.3.16 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.
l 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. Thus, you cannot locate the fault.
l 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.
Procedure
l Prohibit dark screen
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.
BSC6900 GSM
5-21
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
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. Press Insert to edit the file.
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
5.3.17 Resetting the OMU
Prerequisite
Context
l The OMU operating system is restarted after the OMUa board is reset. If the OMUa board
is reset successfully, the faults of the OMU operating system or applications can be rectified.
l All the service processes are disrupted after the OMU applications are reset. If the OMUa
board is reset successfully, the faults of the OMU applications can be rectified.
l Resetting a specified OMU service process interrupts the service of the process for a while.
Procedure
l Reset the OMUa board/OMU applications
1. Run the RST OMU command.
BSC6900 GSM
Issue 01 (2010-04-10)
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.
l Reset a specified service process
1. Run the RST OMUMODULE command and specify Reset Target and Module
Name to reset the specified OMU service process.
----End
5.3.18 Shutting Down the OMU
This section describes how to shut down the OMU by running a command or shutting down the
OMU hardware.
Prerequisite
l The OMU is powered on and functional.
l 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.
l The OMU can be shut down only manually if it fails to be shut down by running a command.
l 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.
Procedure
l Shut down the OMU by running a command.
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
BSC6900 GSM
5-23
available. The OFFLINE LED on the OMU flashes. The shutdown of the OMU is
complete when the LED is on steady in blue.
l Shut down the OMU by turning outwards the ejector levers.
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
Querying the Operating Status of the omud
This section describes how to query the operating status of the omud to determine whether the
OMU can provide services normally.
Prerequisite
Procedure
Step 1 Run the /etc/rc.d/omud status command to query the operating status of the omud.
Option Description
running,
Then it shows that the OMU is working.
unused,
Then it shows that the OMU stops working.
----End
Starting the omud
This section describes how to start the omud so that the OMU provides services normally.
Prerequisite
l The OMU applications are installed. For details, see Installing the OMU Applications in
l The omud is not running. For details on how to query the omud status, see Querying the
Operating Status of the omud.
BSC6900 GSM
Issue 01 (2010-04-10)
Procedure
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.
Prerequisite
Active Workspace.
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
disrupted if you have logged in to the OMU through the external virtual IP address.
Procedure
In to the OMU.
Step 2 Type the /etc/rc.d/omud stop command and press Enter to stop the omud.
----End
Uninstalling the OMU Applications
The OMU applications must be uninstalled when the OMU applications are incorrectly installed.
Prerequisite
l The data is backed up. For details, see Backing Up the System Data.
BSC6900 GSM
5-25
Context
l 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 the OMU
applications on the active workspace.
l When the BSC6900 is configured with active and standby OMUs, uninstall the OMU
applications on both the active and standby OMUs.
Procedure
Step 1 Log in to the standby OMU through the external fixed IP address by referring to Logging In to
the OMU.
Step 3 Type uninstall_bam on any directory of the OMU, and press Enter.
Step 4 The system prompts a message that Uninstall standby area. input Y to continue; input E to
exit.. Enter Y to uninstall the OMU applications on the standby workspace of the OMU.
Step 5 Enter the uninstall_bam command and press Enter.
Step 6 The system prompts a message that Uninstall main area. input Y to continue; input E to
exit.. Enter Y to uninstall the OMU applications on the active workspace of the OMU.
Step 7 Enter the exit command to log out of the OMU.
Option Description
If the OMU is in dual-OMU mode, Go to Step 8.
If the OMU is in single-OMU mode, End this task.
Step 8 Log in to the active OMU through the external fixed IP address by referring to Logging In to
the OMU. Then repeat Step 2 through Step 7 to uninstall the OMU applications on the active
OMU.
----End
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.
l The OMU data is backed up in routine maintenance.
BSC6900 GSM
Issue 01 (2010-04-10)
l The OMU database collapses or the OMU upgrade fails, and the latest OMU data is restored.
Starting the omu_backup_linker tool
This 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.
Prerequisite
fixed IP address.
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,
Figure 5-11 Starting the omu_backup_linker Tool
Please input a valid bkp_res_type :
----End
Postrequisite
l Back up the system data through the omu_backup_linker by referring to Backing Up the
System Data.
l Restore the system data through the omu_backup_linker by referring to Restoring the
System Data.
Backing Up the System Data
This describes how to back up the BSC6900 configuration data, performance data, and alarm
data through MML commands or the omu_backup_restore_tool.
Prerequisite
l If you perform this task by running the MML command, you need to log in to the LMT
first.
l Prerequisites for performing this task by omu_backup_restore_tool are as follows: You
have logged in to the OMU through the external fixed IP address by referring to Logging
In to the OMU.
BSC6900 GSM
5-27
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 before expansion, upgrade or loading to avoid
the failure of system data backup.
Procedure
l Backing up the system data through an MML command
1. Run the BKP DB command, and then 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 5.2.2
Transferring and Backing Up Files.
l Backing up the data by using the omu_backup_linker tool
1. Start the omu_backup_restore_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. A message "Backup OMU database
succeed!" is displayed, indicating that the system data is 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 Figure 5-12.
Figure 5-12 Example
Please input a valid bkp_res_type : backup
Backup omu database [100%]
Backup OMU database succeed!
omd_test_name /mbsc/bam/common/services #
BSC6900 GSM
Issue 01 (2010-04-10)
Restoring the System Data
This describes how to restore the system data through the data backup file. The system data
consists of configuration data, performance data, and alarm data.
Prerequisite
Context
Restoring the BSC6900 system data will disrupt the services on the BSC6900 operation and
maintenance system. The data on the host may be inconsistent with the data on the BAM after
the system data is restored. Thus, the services will be greatly impacted. Therefore, you are
advised to restore the system data when the traffic volume is low.
Procedure
Step 1 Load the BSC6900 board software and data files by referring to Stopping the omud.
Step 2 Restore the system data through the omu_backup_linker.
1. Load the BSC6900 board software and data files by referring to Starting the
omu_backup_linker Tool.
2. Type restore and press Enter after the message "Please input a valid
3. Type 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 Load the BSC6900 board software and data files by referring to Starting the omud.
Step 4 Run the REQ CMCTRL command to obtain the data configuration rights.
Step 5 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 5.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 and
specify the Subrack No. to reset the subrack. If data inconsistency occurs in multiple
subracks, run the RST BSC command to reset the BSC.
----End
BSC6900 GSM
5-29
Example
Restore the OMU data through the omu.bak file under /mbsc/bam. An example is given, as
shown in Figure 5-13:
Figure 5-13 Example
omd_test_name ~
# /etc/rc.d/omud stop
Shutting down mbsc daemon..........
omd_test_name ~ # cd /mbsc/bam/common/services
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
Starting the omutool
This 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 omu_backup_linker
tool.
Prerequisite
Active Workspace.
Context
You can perform tasks by running omutool commands attached with 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.
BSC6900 GSM
Issue 01 (2010-04-10)
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 command. The parameter information about the omutool is displayed.
----End
Setting the Working Mode of the OMU
This 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.
Prerequisite
l You have logged in to the LMT, and queried the slot No. for the OMUa board through the
LST BRD command.
l You have logged in to the LMT, and run the DSP OMU command to query whether the
OMU is in single or dual mode.
Context
l 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 dual-
OMU mode to single-OMU mode, apply the settings to only the working OMU.
l If the working mode of the OMU is changed from single-OMU mode to dual-OMU
mode, ensure that the version of the active OMUa board is the same as that of the standby
OMUa board. In addition, the slot number of the active OMUa board and the slot number
of the standby OMUa board are in active/standby mode, for example, slot 21 and slot 23.
l 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
synchronization is successful.
Procedure
is installed with the OMU applications).
1. Insert an OMUa board into the standby slot by referring to Inserting a Board.
2. Log in to the standby OMU through the external fixed IP address by referring to
Logging In to the OMU, and then install the OMU applications on the active
workspace of the standby OMU by referring to Installing the OMU Applications in
NOTE
l You must select dualmode in the process of installing the OMU applications.
l If the OMU is installed with a patch, you need to copy the bin file to the active workspace of
the standby OMU through 4.4.1 psftp Software.
BSC6900 GSM
5-31
4. Stop the omud on the original working OMU by referring to Stopping the omud.
omutool.
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
is not installed with the OMU applications).
1. Log in to the original working OMU through the external fixed IP address by referring
to Logging In to the OMU, and then stop the omud on the original working OMU
by referring to Stopping the omud.
omutool.
5. After the original working OMU is started for five minuets, add an OMUa board to
the slot for the standby OMUa board by referring to Inserting a Board, and then start
the omud on the standby OMU by referring to Starting the omud.
WARNING
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 OMUa board.
BSC6900 GSM
Issue 01 (2010-04-10)
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 OMUa board by referring to Replacing the OMUa Board.
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 the IP Addresses and Masks of the OMU Ethernet Adapters
This describes how to change the IP addresses and masks of the OMU Ethernet adapters.
Prerequisite
l The omutool is started. For details, see Starting the omutool.
Context
In dual-OMU mode, change the IP addresses and masks of the Ethernet adapters on both the
active and standby OMUs.
NOTE
This task describes the method of changing all the IP addresses and masks of the OMU. You can perform certain
steps according to the planning of the IP addresses on site.
Procedure
Step 1 Stop the omud on the target OMU by referring to Stopping the omud.
Step 2 ETH4-SCU7 and ETH5-SCU6 are teamed as the internal Ethernet adapter team. The ./omutool
innercard IP address mask command is used to change the internal fixed IP address and mask.
Step 3 The ./omutool innervip IP address mask command is used to change the internal virtual IP
address and mask.
Step 4 ETH0 and ETH1 are teamed as the external Ethernet adapter team. The ./omutool extercard
IP address mask (gateway) command is used to change the external fixed IP address and mask.
./omutool extercard 10.161.10.100 255.255.255.0
BSC6900 GSM
5-33
NOTE
To change the external fixed IP address and the gateway, you can 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.100255.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.
Step 6 ETH3-UPDATE serves as the backup Ethernet adapter of the OMU. The ./omutool backupcard
IP address mask command is used to change the IP address and mask of the backup channel
Step 7 ETH2 serves as the debugging Ethernet adapter of the OMU. The ./omutool debugcard IP
address mask command is used to change the debugging IP address and mask.
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 mask.
l Record the new IP addresses in 4.5.1 Records of OMU Software Installation Information.
----End
Postrequisite
If the router settings also need to be changed on site when the virtual IP address and mask of the
external network are changed, perform the following steps to change the settings.
1. LMT Login and Exit
.
2. Run the DSP OMU command to query the backup channel IP address of the standby OMU
and the virtual IP address of the external network. Figure 5-14 shows the query result.
Figure 5-14 Query result (an example)
Subrack No. = 0
Slot No. = 23
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
-----------
BSC6900 GSM
Issue 01 (2010-04-10)
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 the query result above tells, the backup channel IP address of the standby OMU is 192.168.10.123 and
the virtual IP address of the external network is 10.161.95.187.
3. Log in to the OMU through the virtual IP address of the external network by referring to
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 configuration information is reconfigured correctly, for incorrect
configuration may 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 the active OMU by referring to
Logging out of the OMU.
WARNING
After the OMU is restarted and before the router configuration is changed, the OMU may
be inaccessible.
13. Change the router configuration to make the OMU accessible through the new virtual IP
address of the external network.
14. Log in to and out of the OMU through the new virtual IP address of the external network
by referring to LMT Login and Exit.
BSC6900 GSM
5-35
15. Run the DSP OMU command to check whether the new virtual IP address of the external
network takes effect.
Changing the admin Password
This describes how to change the admin password by using the omutool.
Prerequisite
l You have started the omutool by referring to Starting the omutool.
Context
admin is the account for the administrator to log in to the LMT.
Procedure
Step 1 Stop the omud on the OMU by referring to Stopping the omud.
Step 2 Run the ./omutool adminpwd Password command to change the admin password.
For example, to change the admin password to 111111, type the ./omutool adminpwd
111111 command and press Enter.
----End
Changing the OMU Name
This section describes how to change the OMU name through omutool.
Prerequisite
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 the IP Addresses and Masks of the
OMU Ethernet Adapters.
Procedure
Step 1 Load the BSC6900 board software and data files by referring to Starting the omutool.
Step 3 Run the ./omutool hostname OMU name command to change the OMU name.
BSC6900 GSM
Issue 01 (2010-04-10)
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
Postrequisite
1. Run the DSP OMU command to query the new name.
5.4 Appendix: the SEK SetSuse Software
This 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
l Enhancing the SSH service
l Controlling the authority to access files and directories
l Limiting the authority to access the system
l Managing the user password
l Recording operation logs
l 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.4.1 Installing the SEK SetSuse Software
If the SEK SetSuse software is not integrated in the EasyInstall installation files during the
installation of the operating system for the server, the SEK SetSuse software needs to be installed
separately to customize the operating system policies.
5.4.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 enhancement policies for the operating system can be
performed.
5.4.3 Uninstalling the SEK SetSuse Software
The SEK SetSuse software is uninstalled when it is not used any more or it needs to be reinstalled.
5.4.1 Installing the SEK SetSuse Software
If the SEK SetSuse software is not integrated in the EasyInstall installation files during the
installation of the operating system for the server, the SEK SetSuse software needs to be installed
separately to customize the operating system policies.
BSC6900 GSM
5-37
Prerequisite
l The OMU operating system is Suse Linux Enterprise Server 9.0 SP3 or Suse Linux in later
versions.
l The reserved space for installing the SEK SetSuse software is or larger.
Context
l To obtain the compressed SEK SetSuse installation package, visit http://
support.huawei.com/support/ and choose Home Page > Software Center > Version
Software > Wireless Product Line > GSMBSS > GBSS OM tools > SetSuse(for
BSC6000)_VER. Then download SetSuse(for BSC6000)_VER.zip and decompress it for
iPSISEKSetSUSEV100R002C01B509.tar.gz.
l As Figure 5-15 shows, when logging in to the OMU through PuTTY, do not select Enable
X11 forwarding.
Figure 5-15 PuTTY software configuration

l 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.
BSC6900 GSM
Issue 01 (2010-04-10)
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 of the OMU on the LMT computer, 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 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, and implementing the
policy 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. As Figure 5-16 shows, 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.
Figure 5-16 Information about successful installation
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
BSC6900 GSM
5-39
Postrequisite
1. Type the cd .. command and press Enter.
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-server mode, install the SEK SetSuse software for the standby OMU.
1. Type the ssh bsc6000@*.*.*.* command and press Enter. In this command, bsc6000 is
the user name for logging in to the standby OMU and *.*.*.* 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.4.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 enhancement 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.
l If the operating system cannot work normally after the rollback of security enhancement
policies to the previous state, perform the rollback of the policies to the initial state.
Procedure
l Rollback of a specific policy
2. As Figure 5-17 shows, type the sekcli -p 11 command and press Enter to roll back
the policy, 11 to the previous state.
Figure 5-17 Rollback of a specific policy (an example)
Linux:~ # sekcli -p 11
***********************************************************************
Policy Name : Secure SSH authentication (SEC.LNX.SRV.207)
Result : Successful
***********************************************************************
BSC6900 GSM
Issue 01 (2010-04-10)
NOTE
The sekcli -b 11 command is used to roll back a policy to the initial state.
l Rollback of all policies in the policy file
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 interface.
NOTE
The sekcli -b all command is used to roll back all policies in the policy file to the initial state.
----End
5.4.3 Uninstalling the SEK SetSuse Software
The SEK SetSuse software is uninstalled when it is not used any more or it needs to be reinstalled.
Prerequisite
l The SEK SetSuse software is installed successfully on the OMU.
l The compressed SEK SetSuse installation package is decompressed and saved in the /
BSC6000/install directory.
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 uninstallation
procedure (uninstall.sh).
NOTE
By typing the ls command, you can find in the directory of the SEK SetSuse software installation files the
files 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.
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 specified at will but it must be valid.
Step 4 As Figure 5-18 shows, an interface displays a message indicating that the uninstallation will
remove the SEK SetSuse software directory including the check report. Press y to uninstall.
Figure 5-18 Confirming the uninstallation of the SEK SetSuse software
Uninstallation will remove the SEK installation including
checkreport placed in the path
Are you sure you want to uninstall SEK?
Press "y" to proceed or "n" to abort
BSC6900 GSM
5-41
NOTE
Press n to cancel uninstallation 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.
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 Figure 5-19 shows, the interface displays a message indicating that the software
uninstallation succeeds and displays the path for storing the uninstallation log file.
Figure 5-19 Successful uninstallation of the SEK SetSuse software
SEK uninstallation completed successfully
Note:
SEK uninstallation log path : < /var/log/SEKUninstall.log >
----End
5.5 Appendix: Anti-Virus Software
Before installing the anti-virus software, refer to the Anti-Virus Software Installation Guide
provided by Huawei. Now the BSC6000 supports the anti-virus software installation:
TrendMicro Control Manager (TMCM) + ServerProtect for Linux 2.5. After the BSC6000 is
upgraded to the BSC6900, the anti-virus software installation is still supported.
OMU Anti-Virus Software Networking
The OMU anti-virus software consists of the server software, TrendMicro Control Manager
(TMCM) and the client software, ServerProtect for Linux 2.5.
Figure 5-20 Anti-Virus Software Networking

BSC6900 GSM
Issue 01 (2010-04-10)
TrendMicro Control Manager
As a web-based management control console in the center of control management, TMCM
provides centralized monitoring of anti-virus products and service in the entire network. It
manages the gateway, mail server, file server, TrendMicro products and service, and third-party
anti-virus 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.
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 Anti-Virus Software
The operator needs to install anti-virus software. Huawei provides a complete anti-virus solution
for Suse Linux that is based on TMCM + ServerProtect for Linux 2.5.
Hardware Server
Purchased by the operator/
Provided by Huawei
Server software
TrendMicro Control Manager
(TMCM)
Purchased by the operator/
Provided by Huawei
Client software ServerProtect for Linux 2.5

5.6 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-2.
BSC6900 GSM
5-43
Table 5-2 Combinations of Ethernet adapters on the GBAM
Combina
tion
Internal Ethernet Adapter
Model
External Ethernet Adapter
Model
1 Intel Corporation 82546GB Gigabit
Ethernet Controller (rev 03)
Intel Corporation 82545GM
Gigabit Ethernet Controller (rev 04)
2 Intel Corporation 82546EB Gigabit
Ethernet Controller (Copper) (rev
01)
Intel Corporation 82545GM
Gigabit Ethernet Controller (rev 04)
01)
VIA Technologies, Inc. VT6105
01)
Intel Corporation 82546EB Gigabit
Ethernet Controller (rev 01)

l The kernel version of the GBAM operating system is 2.6.5-7.244-smp.
NOTE
l To view the Ethernet adapter model of the GBAM, run the lspci | grep "Ethernet Controller"
command.
l 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 > Mini-tool
software > 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:
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.
BSC6900 GSM
Issue 01 (2010-04-10)
l 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.
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.
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.
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-21 shows, enter the IP address, subnet mask, and default gateway of the
external network.
6. As Figure 5-21 shows, after checking the input, type y, and press Enter. Then the
network restarts.
Figure 5-21 Changing the IP address of the external Ethernet adapter
BSC6900 GSM
5-45

----End
5.7.1 Record Sheet of OMU Software Installation Information
5.7.3 List of the Factory Configuration of the OMU Software and Hardware
This list records the factory configuration of the OMU software and hardware.
5.7.1 Record Sheet of OMU Software Installation Information
Record Sheet of OMU Operating System Installation Information
Item Factory Settings Setting
Information
Installer
Common user name bsc6000
Common user
password
11111111
Root user password 11111111
Version of the iPSI
SEK SetSuse
software
V100R002C01B509
System enhancement
policies of iPSI SEK
SetSuse
Default policies

For details, see Record Sheet of OMU Operating System Installation Information.
BSC6900 GSM
Issue 01 (2010-04-10)
Record Sheet of OMU Ethernet Adapter Teaming Information
Information
Installer
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)
External Ethernet
adapter teaming
(ETH0 and ETH1)
Teamed as bond1 in
the "balance-rr"
mode

For details, see Record Sheet of OMU Ethernet Adapter Teaming Information.
Record Sheet of Samba Service Installation Information
Information
Installer
Samba user name bsc6000
Samba user
password
11111111
Samba file directory /BSC6000

For details, see Record Sheet of Samba Service Installation Information.
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
BSC6900 GSM
5-47
Item Whether Installed or Set Remarks
Setting the Ethernet adapters Y; N l ETH4-SCU7 and ETH5-
SCU6 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.
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.
5.7.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.
BSC6900 GSM
Issue 01 (2010-04-10)

OMU Administration Guide

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

OMU Administration Guide

Caricato da

Copyright:

Formati disponibili

BSC6900 GSM

Potrebbero piacerti anche