Bsc6910 GSM Omu Administration Guide (v100r015c00 - 05) (PDF) - en

BSC6910 GSM
V100R015C00
OMU Administration Guide

Issue
05
Date
2014-03-28
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 05 (2014-03-28)
Huawei Proprietary and Confidential

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

Overview
This document describes software structure, working principles, application installation, general
tasks of OMU boards.
NOTE
In this document, OMU board (hardware) indicates the combination of the EOMUa board and its operating
system; OMU (logical concept) indicates the OMU board with product software.
Product Version
The following table lists the product versions related to this document.
Product Name
Product Version
BSC6910
V100R015C00
Intended Audience
This document is intended for:
l
Field engineers
Shift operators
Organization
1 Changes in BSC6910 GSM OMU Administration Guide
This document describes the changes in BSC6910 GSM OMU Administration Guide.
2 Introduction to OMU
This chapter describes the following information about the OMU: position in the network,
software structure, working mode, OM methods, and safety instructions.
3 Working Principles of the OMU
Issue 05 (2014-03-28)

ii
BSC6910 GSM
About This Document
This section has the following topics:

4 Initially Commissioning the OMU
This section describes the procedure for initially commissioning the OMU after delivery.
5 Installing OMU Software
If an OMU board is damaged onsite, replace it. If the operating system fails, reinstall it along
with the product software.
6 Operating and Maintaining the OMU
This section describes how to perform operation and maintenance on the OMU after product
software are installed. To perform this task, log in to the OMU remotely or run MML commands.
7 Appendix: OMU-Related Operations
This section describes basic OMU-related operations, including logging into the OMU, logging
out of the OMU, and starting OMU tools.
8 Appendix: OMU-Related Software
This section describes how to obtain and use the OMU-related software, including the psftp
software and PuTTY software. The OMU-related software is used to install the product software
and perform operation and maintenance on the OMU.
9 Appendix: OMU-Related Information Tables
This section describes the tables in which the OMU information is recorded during routine
operation and maintenance on the OMU.
10 Appendix: Troubleshooting
This chapter describes OMU faults and troubleshooting methods.
11 Appendix: Security FAQ
This section describes how to improve the security of the BSC6910.
12 Appendix: Special OMU Networking Scenarios
This section describes special scenarios associated with connecting the OMU to peripheral
equipment.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
Indicates an imminently hazardous situation which, if not
avoided, will result in death or serious injury.
Issue 05 (2014-03-28)

iii
BSC6910 GSM
About This Document
Symbol
Description
Indicates a potentially hazardous situation which, if not
avoided, could result in death or serious injury.
avoided, may result in minor or moderate injury.
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Calls attention to important information, best practices and
tips.
NOTE is used to address information not related to personal
injury, equipment damage, and environment deterioration.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention
Description
Times New Roman
Normal paragraphs are in Times New Roman.
Boldface
Names of files, directories, folders, and users are in

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

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

vertical bars. One item is selected.
iv
BSC6910 GSM
About This Document
Convention
Description
[ x | y | ... ]
Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }*
Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]*
Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
Buttons, menus, parameters, tabs, window, and dialog titles

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

signs. For example, choose File > Create > Folder.
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format
Description
Key
Press the key. For example, press Enter and press Tab.
Key 1+Key 2
Press the keys concurrently. For example, pressing Ctrl+Alt

+A means the three keys should be pressed concurrently.
Key 1, Key 2
Press the keys in turn. For example, pressing Alt, A means

the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Issue 05 (2014-03-28)
Action
Description
Click
Select and release the primary mouse button without moving

the pointer.

BSC6910 GSM
Issue 05 (2014-03-28)
About This Document
Action
Description
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.

vi
BSC6910 GSM
Contents
Contents
About This Document.....................................................................................................................ii
1 Changes in BSC6910 GSM OMU Administration Guide......................................................1
2 Introduction to OMU....................................................................................................................4
2.1 Position of the OMU in the BSC6910............................................................................................................................5
2.2 OMU Components..........................................................................................................................................................5
2.3 OMU Working Mode.....................................................................................................................................................9
2.4 OMU Installation and Maintenance Methods................................................................................................................9
2.5 OMU Safety Information..............................................................................................................................................10
3 Working Principles of the OMU..............................................................................................11

3.1 OMU Ethernet Adapter Configuration.........................................................................................................................12
3.2 OMU IP Address Plan..................................................................................................................................................13
3.3 OMU Networking Principle.........................................................................................................................................21
3.4 Heartbeat Detection on Active and Standby OMUs.....................................................................................................26
3.5 Synchronization Between Active and Standby OMUs.................................................................................................26
3.6 Switchover Between Active and Standby OMUs.........................................................................................................27
4 Initially Commissioning the OMU..........................................................................................29

4.1 Setting the Link Mode for External OMU Ethernet Adapters......................................................................................31
4.2 Commissioning the OMU.............................................................................................................................................32
5 Installing OMU Software..........................................................................................................38

5.1 Preparations..................................................................................................................................................................39
5.2 Optional: Installing Product Software by Using a USB Storage Device.....................................................................40
5.3 Optional: Manually Installing the Product Software....................................................................................................43
5.3.1 Obtaining Information About OMU Software Installation.......................................................................................43
5.3.2 Uploading the OMU Application Installation Package to the OMU.........................................................................43
5.3.3 Installing the Product Software in the Active Workspace.........................................................................................46
5.3.4 Checking the Installation Directory of Product Software..........................................................................................49
6 Operating and Maintaining the OMU....................................................................................55

6.1 Querying the Mapping Between Ethernet Adapters.....................................................................................................57
6.2 Querying the Configuration of the OMU Ethernet Adapters.......................................................................................57
6.3 Querying Occupied OMU Ports...................................................................................................................................59
Issue 05 (2014-03-28)

vii
BSC6910 GSM
Contents
6.4 Querying the Link Mode of the External OMU Network Adapters.............................................................................59
6.5 Checking the Version of the Operating System...........................................................................................................60
6.6 Changing the Administrator Password of the Operating System.................................................................................60
6.7 Setting RAID 1 on OMU Hard Disks...........................................................................................................................61
6.8 Adjusting OMU Slots...................................................................................................................................................64
6.9 Transferring OMU Files to a Local PC........................................................................................................................66
6.10 Managing the Operating Status of the OMU..............................................................................................................69
6.10.1 Querying the OMU Operating Status......................................................................................................................69
6.10.2 Querying the Information About an OMU Board...................................................................................................69
6.10.3 Querying the Version of the Active/Standby OMU Workspaces............................................................................70
6.10.4 Querying the Status of Data Synchronization Between the Active and Standby OMUs........................................71
6.10.5 Checking the Data Consistency Between the Active OMU and the Standby OMU...............................................71
6.10.6 Changing the Time Zone and OMU Time ..............................................................................................................72
6.10.7 Configuring Data Rates of Accessing the OMU Hard Disks..................................................................................72
6.10.8 Forcibly Switching Over the Active and Standby OMUs.......................................................................................73
6.10.9 Resetting the OMU..................................................................................................................................................74
6.11 Managing the Product Software.................................................................................................................................75
6.11.1 Querying Operating Status of the omud..................................................................................................................75
6.11.2 Starting the omud.....................................................................................................................................................75
6.11.3 Stop the omud..........................................................................................................................................................76
6.11.4 Uninstalling the Product Software...........................................................................................................................76
6.12 Backing Up and Restoring Data.................................................................................................................................77
6.12.1 Backing Up System Data.........................................................................................................................................78
6.12.2 Restoring System Data............................................................................................................................................79
6.13 Setting OMU System Parameters...............................................................................................................................81
6.13.1 Setting the OMU Working Mode............................................................................................................................81
6.13.2 Changing IP Addresses and Subnet Masks of OMU Ethernet Adapters.................................................................85
6.13.3 Changing Users' Passwords.....................................................................................................................................88
6.13.4 Changing the Computer Name................................................................................................................................90
7 Appendix: OMU-Related Operations......................................................................................91

7.1 Starting the omu_backup_linker Tool..........................................................................................................................92
7.2 Starting the omutool.....................................................................................................................................................92
7.3 Logging In to the OMU................................................................................................................................................93
7.4 Logging Out of the OMU.............................................................................................................................................94
8 Appendix: OMU-Related Software..........................................................................................95

8.1 psftp Software...............................................................................................................................................................96
8.2 PuTTY Software...........................................................................................................................................................97
8.3 Dopra_Linux_USB Disk Tool......................................................................................................................................99
9 Appendix: OMU-Related Information Tables.....................................................................119

9.1 Information Records of OMU Software Installation..................................................................................................120
Issue 05 (2014-03-28)

viii
BSC6910 GSM
Contents
9.2 Checklist for the OMU Software Factory Settings.....................................................................................................121

9.3 OMU Directory Operation Rights List.......................................................................................................................123
9.4 OMU Folder Size List................................................................................................................................................124
9.5 Enabled Ports on the OMU.........................................................................................................................................127
10 Appendix: Troubleshooting..................................................................................................128
10.1 Restoring OS by the Using USB Storage Device.....................................................................................................129
11 Appendix: Security FAQ........................................................................................................131

11.1 Disabling root user login with SSH..........................................................................................................................132
11.2 Disabling OMU route forwarding............................................................................................................................135
11.3 Configuring the Function of Recording OMU OS Accessing Information in Real Time........................................137
11.4 Enabling Function of Checking OS File Integrity....................................................................................................138
11.5 Enhancing Security of Time Synchronization with NTP.........................................................................................139
12 Appendix: Special OMU Networking Scenarios.............................................................. 141

12.1 Scenario of Connecting the OMU and VNP............................................................................................................142
Issue 05 (2014-03-28)

ix
BSC6910 GSM
Changes in BSC6910 GSM OMU

Administration Guide
This document describes the changes in BSC6910 GSM OMU Administration Guide.
05 (2014-03-28)
This is the fifth commercial release for V100R015C00.
Compared with 04 (2014-01-20), this issue does not include any new information.
Compared with 04 (2014-01-20), this issue does not incorporate any changes.
Compared with 04 (2014-01-20), this issue excludes the following topics:
Content
Description
Active/Standby Workspaces of the OMU
Deleted this content because this function has

been incorporated into the upgrade tool and
is no longer independently used.
Switching Over the Active/Standby OMU

Workspaces
04 (2014-01-20)
This is the fourth commercial release for V100R015C00.
Compared with 03 (2013-11-15), this issue incorporates the following changes.
Issue 05 (2014-03-28)
Content
Description
6.13.3 Changing Users' Passwords
Changed the background information.

Updated description of changing users'
passwords on both the active and standby
OMUs.

BSC6910 GSM
Compared with 03 (2013-11-15), this issue does not exclude any topics.
03 (2013-11-15)
This is the third commercial release for V100R015C00.
Content
Description
7.2 Starting the omutool
The use right of the omutool is changed.
9.4 OMU Folder Size List
The storage specifications of some logs are

changed.
02 (2013-06-25)
This is the second commercial release for V100R015C00.
Content
Description
5.3.3 Installing the Product Software in the

Active Workspace
Changed the password information of User

admin and FtpUsr user. The special character
of the password is modified.
01 (2013-05-04)
This is the first commercial release for V100R015C00.
Compared with Draft A (2013-02-27), this issue does not include any new information.
Compared with Draft A (2013-02-27), this issue incorporates the following changes.
Issue 05 (2014-03-28)
Content
Description
11.5 Enhancing Security of Time

Synchronization with NTP
Changed the background information. When

the OMU works as an NTP server, NTP
packets are transmitted in plaintext on the
intranet.

BSC6910 GSM
Content
Description
3.2 OMU IP Address Plan
Added description of changing the fixed and

virtual internal IP addresses.
Changed the OMU folder size list.
Added a flowchart for commissioning the

OMU.
4.2 Commissioning the OMU
Classified procedures for commissioning the

OMU.
Compared with Draft A (2013-02-27), this issue does not exclude any topics.
Draft A (2013-02-27)
This is the Draft A release of V100R015C00.
Issue 05 (2014-03-28)

BSC6910 GSM
Introduction to OMU
About This Chapter

This chapter describes the following information about the OMU: position in the network,
software structure, working mode, OM methods, and safety instructions.
2.1 Position of the OMU in the BSC6910
This section describes the components of the BSC6910 operation and maintenance (O&M)
network and the position of the OMU in the OM network.
2.2 OMU Components
This section describes the OMU components and dependencies of those components on each
other.
2.3 OMU Working Mode
The OMU works in independent or active/standby mode.
2.4 OMU Installation and Maintenance Methods
This section describes how to perform installation and maintenance on the OMU in different
scenarios.
2.5 OMU Safety Information
This section describes the safety information related to the OMU operation.
Issue 05 (2014-03-28)

BSC6910 GSM
2.1 Position of the OMU in the BSC6910

This section describes the components of the BSC6910 operation and maintenance (O&M)
network and the position of the OMU in the OM network.
The BSC6910 O&M network is composed of the O&M terminal (LMT or M2000), OMU, SCU,
and O&M modules on the host boards. The O&M terminal communicates with the BSC6910
host boards by using the OMU.
Figure 2-1 shows the position of the OMU in the BSC6910 O&M network.
Figure 2-1 Position of the OMU in the BSC6910 O&M Network
As shown in Figure 2-1, the external network is the logical network between the OMU and the
O&M terminal (LMT/M2000), and the internal network is the logical network between the OMU
and the BSC6910 host boards.
2.2 OMU Components

This section describes the OMU components and dependencies of those components on each
other.
The OMU consists of the OMU Hardware, OMU operating system and product software, as
shown in Figure 2-2.
l
OMU Hardware
The OMU hardware is monitoring its software in real time to avoid suspension of product
software.
Issue 05 (2014-03-28)

BSC6910 GSM
OMU Operating System

The OMU operating system, installed on the boards, can be the Dopra Linux.
OMU Application Software

The OMU application software runs on the bottom-level operating system and provides
various service processes.
Figure 2-2 OMU Components
NOTE
l The yellow blocks in Figure 2-2 indicate OMU service monitoring entities, the blue blocks indicate
OMU service processes, the white blocks indicate OMU peripheral devices.
l The arrows shown in Figure 2-2 indicate communication between modules.
OMU Service Processes

The OMU is managed by OMU services processes. OMU service processes are logically
independent of one another. When one process fails, other processes continue to run properly.
The OMU can detect a process that stops abnormally and restart it quickly.
Table 2-1 shows the OMU service processes and the functions.
Issue 05 (2014-03-28)

BSC6910 GSM
Table 2-1 OMU Service Processes

Service Processes
Functions
Communication Module
(ems_gate)
The communication module receives messages from the

Element Management System (EMS) or Local Maintenance
Terminal (LMT), converts the messages into frames for
internal communication in the OMU, and then sends the
messages to the authentication module. Receives messages
from the OMU modules, interprets the messages, and then
sends the messages to the EMS or LMT.
The communication module receives, interprets, and sends
messages between the VNP and maintenance module.
Issue 05 (2014-03-28)
Authentication Module
(authority)
The authentication module performs functions such as

authority management, log management, and command
resolution.
Network Management Agent

Module (ems_agent)
The network management agent module performs functions

such as batch command processing, and scheduled task
management.
Configuration Module
(configure)
The configuration module performs the functions of data

configuration and management for the BSC6910 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 BSC6910 host
hardware, physical/logical links, and channels. It also
enables the BAM to test and maintain objects.
Alarm Module (alarm)
The alarm module handles alarms. It controls the output

mode and classification of alarms, and shields alarms.
Performance Module (stat)
The performance module collects, stores, and computes the

performance measurement data of the host, and then reports
the data to the M2000.
Software Management
Module (software)
The software management module performs functions such

as BOOTP service for the OMU board, OMU software
management, OMU active/standby workspace management,
file synchronization between the active OMU and the
standby OMU, and version upgrade management.
OMU Management Module

(omu_manager)
The OMU management module monitors the OMU hardware

and software.

BSC6910 GSM
Service Processes
Functions
Time Server Module (sntp)
The server module performs the functions as follows:

l The time server provides time synchronization for
BSC6900 boards and the base station.
l The time client synchronizes with the upper-level time
server and provides the reference time.
FTP Module (ftp_server)
The FTP module serves as an FTP server and provides the

file transfer function for the host boards, LMT, and EMS.
Exchange Module
(host_gate)
The exchange module enables the communication between

the OMU processes and the host.
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 Diagnosis Module (cfa)
The fault diagnosis module collects end-to-end link fault

information, periodically diagnoses faulty nodes, and
performs self-healing.
OMU Log Management

Module (debug_log)
The OMU log management module records and regularly

cleans up OMU logs.
LMT Module (weblmt)
The LMT module performs message tracing, performance

monitoring, and device maintenance. It also provides an
interface for issuing MML commands.
Data Exportation Module

(cfg_mirror)
The data exportation module exports the configuration data.
OMU Service Monitoring Entities

The product software perform monitoring at three levels:
l
Level 1 is the hardware-level monitoring in which the watchdog monitors the omud.
A watchdog is a timer used to monitor the omud. Once the omud is abnormal and cause
the watchdog timer to overflow, the OMU will be reset automatically.
Level 2 is the system-level monitoring in which the omud monitors the monitor.
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.
Level 3 is the application-level monitoring in which the monitor monitors service processes.
The monitor monitors the service processes in real time.
When a service process, the monitor, or the omud is faulty, three-level monitoring mechanism
ensures that the faulty service process, monitor, or omud can be restarted.
Issue 05 (2014-03-28)

BSC6910 GSM
2.3 OMU Working Mode

The OMU works in independent or active/standby mode.
Independent Mode
When the BSC6910 is configured with one OMU board or one GBAM server, the OMU works
in independent mode.
In this mode, if the OMU is faulty, operation and maintenance (OM) cannot be performed on
the BSC6910. This reduces system reliability.
Active/Standby Mode
When the BSC6910 is configured with two OMU boards, the OMU works in active/standby
mode.
In this mode, the OMU board working in active mode is called the active OMU board, and the
OMU board working in standby mode is called the standby OMU board. The active and standby
OMU boards must be of the same type. Installing different types of OMU boards is prohibited.
When the BSC6910 is configured in active/standby OMU mode, the OMU can operate properly
with high reliability. Specifically, if a hardware or software fault occurs on the active OMU, the
standby OMU is automatically switched over to the active state and provides services.
NOTE
l The OMU working mode is set during the OMU application installation.
l After the product software are installed, run the MML command DSP OMU to query the OMU working
mode, and check the value for the Operational state parameter in the command output to check the OMU
working mode. If the value is Active normal or Standby normal, the OMU works in active/standby mode.
If the value is Normal, the OMU works in independent mode.
2.4 OMU Installation and Maintenance Methods

This section describes how to perform installation and maintenance on the OMU in different
scenarios.
Scenario: Installing Product Software Before Onsite Commissioning

After installing the BSC6910 hardware, install product software before commissioning the
OMU. For details about this scenario, see 4 Initially Commissioning the OMU.
Scenario: Reinstalling the OMU Operating System Onsite

If the operating system crashes onsite, reinstall the OMU operating system as well as product
software, and reconfigure the OMU. For details, see 5.2 Optional: Installing Product Software
by Using a USB Storage Device.
When product software are abnormal and you do not want to change the OMU operating system
configurations, you must manually reinstall the product software. For details about this scenario,
see 5.3 Optional: Manually Installing the Product Software.
Issue 05 (2014-03-28)

BSC6910 GSM
Scenario: Performing Routine OM on the OMU

Query and set some OMU information by using MML commands or operating system command
lines. For details about this scenario, see 6 Operating and Maintaining the OMU.
2.5 OMU Safety Information

This section describes the safety information related to the OMU operation.
l
To ensure normal operation of the OMU, do not create or delete directories, change
directory attributes, delete backup files, modify system files, change system file attributes,
disable Ethernet adapters, modify configuration files for Ethernet adapters, or configure
routes.
Install and run only the operating system software (including necessary drivers and
components) and product software on the OMU.
The operation information and faults of the BSC6910 are recorded on the OMU. Therefore,
to timely and accurately locate and rectify faults, do not delete any log file from the OMU.
Issue 05 (2014-03-28)

10
BSC6910 GSM
Working Principles of the OMU
About This Chapter

This section has the following topics:
3.1 OMU Ethernet Adapter Configuration
This section describes the configuration of OMU Ethernet adapters.
The OMU Ethernet adapters must follow the IP address planning principles to meet the
communication requirements of the operation and maintenance (O&M) network.
3.3 OMU Networking Principle
The internal Ethernet adapters of the OMU are connected to the SCUs in the MPS, and the
external Ethernet adapters of the OMU are connected to the operation and maintenance (O&M)
terminals. In this way, the OMU fulfills the communication between the BSC6910 and the O&M
terminals.
3.4 Heartbeat Detection on Active and Standby OMUs
In active/standby OMU mode, heartbeat detection is performed on active and standby OMUs to
check whether the active and standby OMUs are working properly.
3.5 Synchronization Between Active and Standby OMUs
In active/standby mode, the synchronization between the active and standby OMUs consists of
data synchronization, file synchronization, and time synchronization.
3.6 Switchover Between Active and Standby OMUs
For OMUs working in active/standby mode, there are four types of switchover: manual
switchover, fault-triggered switchover, failover, and self-healing switchover.
Issue 05 (2014-03-28)

11
BSC6910 GSM
3.1 OMU Ethernet Adapter Configuration

This section describes the configuration of OMU Ethernet adapters.
The six Ethernet adapters on an EOMUa board are:
l
F_ETH0 and F_ETH1: These two Ethernet adapters are bound as an external Ethernet
adapter team. This Ethernet adapter team is used for communication in the external network.
That is, the communication between the OMU and the LMT/M2000. This external Ethernet
adapter team is also called bond1/bond1:0.
F_DBG: bond2, a debugging Ethernet adapter, is connected to a portable PC for OMU

debugging if required.
B_UPDATE: This is a backup channel Ethernet adapter used for the dedicated backup
channel between the active and standby OMUs when the BSC6910 is configured with two
EOMUa boards. This backup Ethernet adapter is also called bond3.
B_ETH0 and B_ETH1: The two Ethernet adapters are bound as an internal Ethernet adapter
team. This Ethernet adapter team is used for communication in the internal network. That
is, the communication between the OMU and BSC6910 host boards. This Ethernet adapter
team is also called bond0 (vlan1/vlan1:0).
Figure 3-1 shows the binding relationship between Ethernet adapters on the EOMUa board.
Figure 3-1 Binding relationship between Ethernet adapters on the EOMUa board
Issue 05 (2014-03-28)

12
BSC6910 GSM
NOTE
l F_ETH0, F_ETH1, and F_DBG are connected to the external network by using the Ethernet ports on
the panel of the EOMUa board. B_ETH0, B_ETH1, and B_UPDATE are connected to the the external
network by using the Ethernet ports which are on the backplane of the Main Processing Subrack (MPS)
and are invisible on the panel of the EOMUa board.
l One of bond1 and bond1:0 is reserved for the fixed external IP address, and the other is reserved for
the virtual external IP address.
l B_ETH0 and B_ETH1 are bound as an internal adapter team. This internal adapter team is also called
bond0. To enable communication between the OMU and the SCU, a VLAN whose ID is 1 needs to be
established on bond0. vlan1 and vlan1:0 are reserved for the internal fixed IP address and the internal
virtual IP address, respectively.

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

The OMU IP addresses include fixed internal IP address, fixed external IP address, virtual
internal IP address, virtual external IP address, and commissioning IP address. If the
BSC6910 is configured with two OMU boards, the OMU IP addresses also include the IP address
of the backup channel between the active and standby OMU boards.
Table 3-1 provides definitions of different OMU IP addresses.
Table 3-1 Definitions of OMU IP addresses
IP Address
Definition and Function
Corresponding
Ethernet
Adapters on the
EOMUa Board
Fixed external
IP address
IP address for the communication between peripheral

devices (for example, LMT/M2000) and the OMU. A
user can log in to the LMT and OMU by using the
fixed external IP address.
l F_ETH0
l F_ETH1
The fixed external IP address is automatically

configured on the OMU external Ethernet adapter
team when the OMU operating system is being
installed.
If active and standby OMUs are switched over when
a peripheral device communicates with the active
OMU by using the fixed external IP address, the
communication between the peripheral device and the
active OMU will be interrupted.
Issue 05 (2014-03-28)

13
BSC6910 GSM
IP Address
Corresponding
Ethernet
Adapters on the
EOMUa Board
Virtual
external IP
address
IP address for the communication between peripheral

devices (for example, LMT/M2000) and the OMU. A
user can log in to the LMT and OMU by using the
l F_ETH0
l F_ETH1
The virtual external IP address is configured on the

Ethernet adapter team of the active OMU when the
product software are installed. It takes effect after the
product software are started.
If active and standby OMUs are switched over when
a peripheral device communicates with the OMUs by
using the virtual external IP address, the
communication between the peripheral device and the
OMU will be interrupted for a while and then be
recovered. During this process, the virtual external IP
address of the original standby OMU becomes
effective, and the virtual external IP address of the
original active OMU becomes ineffective.
Fixed internal
IP address
IP address for the communication between the active

and standby OMUs on the internal network segment
(network on which information is exchanged by using
the SCU board).
l B_ETH0
l B_ETH1
The fixed internal IP address is automatically

configured on the OMU internal Ethernet adapter team
when the OMU operating system is installed.
The fixed internal IP address is not used for the
communication between the OMU and the BSC6910
host boards.
Virtual
internal IP
address

OMU and the BSC6910 host boards.
l B_ETH0
l B_ETH1
The virtual internal IP address is configured on the

internal Ethernet adapter team of the active OMU. It
takes effect after the product software are started.
The communication between the BSC6910 host
boards and the OMU are not interrupted even during
the switchover of the active and standby OMUs.
Issue 05 (2014-03-28)

14
BSC6910 GSM
IP Address
Corresponding
Ethernet
Adapters on the
EOMUa Board
IP address of
the backup
channel
between active
and standby
OMU boards

and standby OMUs on the backup channel network
segment (network on which information is exchanged
by using an Ethernet cable).
l B_UPDATE
The IP address of the backup channel between the

active and standby OMUs is automatically configured
on the standby OMU Ethernet adapter when the OMU
operating system is being installed.
The active and standby OMUs communicates by using
the backup channel IP address between the active and
standby OMUs. Any fault on a host board does not
affect the communication between the active and
standby OMUs.
Commissionin
g IP address
IP address for operating and maintaining the OMU

when a PC is connected to the commissioning Ethernet
port of the OMU by using an Ethernet cable at the local
end.
l F_DBG
The commissioning Ethernet port and the ETH0 or

ETH1 port cannot be simultaneously connected to the
external network. Otherwise, the OMU IP Address
Conflict alarm is generated.
Definition of Onsite Network

The network connecting the OMU external Ethernet adapters and the LMT or M2000 is defined
as an external network or an onsite network. If the OMU external Ethernet adapters are connected
to the LMT or M2000 routers, then the network connecting the OMU external Ethernet adapters
and the first router (gateway) is defined as an onsite network. Figure 3-2 shows an onsite
network.
l
The network between the OMU internal Ethernet adapters and host boards is defined as an
internal network. The OMU communicates with the base station by using the host boards.
The network between the OMU external Ethernet adapters and the LMT or M2000 is
defined as an external network. The OMU is connected to the LMT or M2000 either directly
or by using multiple routers (gateways).
Issue 05 (2014-03-28)

15
BSC6910 GSM
Figure 3-2 Onsite network
Consider the following principles when configuring IP addresses onsite:

l
If IP routes configured for the OMU are configured (by running the ADD OMUIPRT
command), ensure that the Forward Route Address and Destination Network Address
to the LMT/M2000 are not located in the same network segment as the virtual internal IP
address, fixed internal IP address, backup channel IP address, and debugging IP address.
IP Addresses to Be Changed Onsite

IP addresses are configured before an OMU is delivered. For more information, see 9.2 Checklist
for the OMU Software Factory Settings. The default IP addresses may fail to meet the
requirements of onsite network planning. Therefore, you are required to reconfigure some of the
OMU IP addresses.
Generally, the fixed and virtual external IP addresses need to be reconfigured according to the
customer network planning. To reconfigure the IP addresses, do as follows:
l
If single OMU is configured, one fixed and one virtual external IP addresses of the OMU
must be on the same network segment.
If active and standby OMUs are configured, the fixed external IP addresses of the active
and standby OMUs, the virtual external IP address of the active and standby OMUs (the
virtual external IP address of the active OMU and that of the standby OMU are the same)
must be configured on the same network segment.
If the fixed and virtual internal IP addresses need to be changed, do as follows:

l
If single OMU is configured, one fixed and one virtual internal IP addresses of the OMU
must be on the same network segment. And their subnet masks are fixed to 255.0.0.0.
If active and standby OMUs are configured, the fixed internal IP addresses of the active
and standby OMUs, the virtual internal IP address of the active and standby OMUs (the
virtual internal IP address of the active OMU and that of the standby OMU are the same)
must be configured on the same network segment. The subnet masks of the IP addresses
are fixed to 255.0.0.0.
Table 3-2 describes the planning principles of OMU IP addresses.
Issue 05 (2014-03-28)

16
BSC6910 GSM
Table 3-2 Onsite planning of OMU IP addresses

IP Address
Planning Principle
Fixed external IP
address
The default fixed external IP address of the active OMU is

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

Review OMU IP addresses onsite. If the IP addresses are located on the same network segment
as the onsite network IP address, they should be reconfigured. Table 3-3 describes the principles
of configuring the IP addresses.
Issue 05 (2014-03-28)

17
BSC6910 GSM
Table 3-3 Onsite check of OMU IP addresses

IP Address
Check Principle
Fixed internal IP
address
The fixed internal IP address of the active OMU must be set to X.168.3.50.
The default IP address is 80.168.3.50 (255.0.0.0).
The fixed internal IP address of the standby OMU must be set to X.
168.3.60. The default IP address is 80.168.3.60 (255.0.0.0).
Check principle:
1. The network segment in which the fixed internal IP address is located
cannot conflict with the onsite network segment. If they conflict, you
must change the fixed internal IP address.
2. Only the network segment where the fixed internal IP address is
located can be changed. For example, 80.168.3.50 can be changed to
90.168.3.50.
3. If active and standby OMUs are configured, the fixed internal IP
addresses of the active and standby OMUs must be different and on
the same network segment.
4. If an independent OMU is configured and the network segment where
the fixed internal IP address is located does not conflict with the onsite
network segment, reserve the default fixed internal IP address.
5. The subnet mask of the fixed internal IP address must be 255.0.0.0.
Virtual internal
IP address
1. The virtual internal IP address must be located in the same subnet as

the fixed internal IP addresses of the active and standby OMUs. This
subnet is called the OMU internal network segment. In addition, the
virtual internal IP address cannot be identical with other IP addresses
in the subnet and it should be configured as X.168.3.40 in which X
must be the same as the network segment where the fixed internal IP
address is located.
For example, if active and standby OMUs are configured, the fixed
internal IP address of the active OMU is 80.168.3.50, and that of the
standby OMU is 80.168.3.60, the virtual internal IP address can be
configured as 80.168.3.40.
2. For example, if an independent OMU is configured and the fixed
internal IP address of the OMU is 80.168.3.50, the virtual internal IP
address can be configured as 80.168.3.40.
3. The subnet mask of the virtual internal IP address must be 255.0.0.0
Issue 05 (2014-03-28)

18
BSC6910 GSM
IP Address
Check Principle
Commissioning
IP address
The default commissioning IP address of the active OMU is 192.168.6.50

(255.255.255.0).
The default commissioning IP address of the standby OMU is
192.168.6.60 (255.255.255.0).
Check principle:
1. The commissioning IP addresses of the active and standby OMUs
cannot be identical with other IP addresses on the onsite network. If
they are identical, you must change the commissioning IP address.
2. If active and standby OMUs are configured, the commissioning IP
addresses of the active and standby OMUs must be different and on
For example, the commissioning IP address of the active OMU is
192.168.6.50 (255.255.255.0) and the commissioning IP address of the
standby OMU can be 192.168.6.60 (255.255.255.0).
the commissioning IP addresses is located is different from the onsite
network segment, retain the commissioning IP address.
IP address of the
backup channel
between active
and standby
OMU boards
For an active OMU, the default IP address of the backup channel between
the active and standby OMUs must be set to X. X. X.50. The default IP
address is 192.168.3.50 (255.255.255.0).
For a standby OMU, the default IP address of the backup channel between
the active and standby OMUs must be set to X. X. X.60. The default IP
address is 192.168.3.60 (255.255.255.0).
Planning principle:
1. The network segment where the IP addresses of the channel between
the active and standby OMUs are located cannot conflict with the
onsite network segment. If they conflict, the IP addresses of the
channel between the active and standby OMUs must be changed.
2. If active and standby OMUs are configured, the IP addresses of the
channel between the active and standby OMUs on the active and
standby OMUs must be different and on the same network segment.
the IP addresses of the backup channel between the active and standby
OMUs is located is different from the onsite network segment, retain
the IP addresses of the backup channel between the active and standby
OMUs.
4. The subnet mask of the IP address of the channel between the active
and standby OMUs must be 255.255.255.0.
Impact of OMU IP Address Changes

Changing IP addresses for the OMU routine maintenance impacts the working of the
BSC6910, as described in Table 3-4.
Issue 05 (2014-03-28)

19
BSC6910 GSM
Table 3-4 Impact of OMU IP address changes

IP Address
Change Impact
Fixed external IP
address
After the fixed external IP address is changed, the device connected to the
external Ethernet port can access the OMU only by using the new fixed
external IP address.
The fixed external IP address can be changed remotely and takes effect
immediately after it is changed.
Virtual external
IP address
After the virtual external IP address is changed, the device connected to

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

20
BSC6910 GSM
IP Address
Change Impact
Commissioning
IP address
After the commissioning IP address is changed, the device connected to

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

The internal Ethernet adapters of the OMU are connected to the SCUs in the MPS, and the
external Ethernet adapters of the OMU are connected to the operation and maintenance (O&M)
terminals. In this way, the OMU fulfills the communication between the BSC6910 and the O&M
terminals.
Independent EOMUa Networking Principle

Figure 3-3, and Figure 3-4 show the networking topology in single-EOMUa mode.
Issue 05 (2014-03-28)

21
BSC6910 GSM
Figure 3-3 Independent-EOMUa (with a single LAN switch)
Issue 05 (2014-03-28)

22
BSC6910 GSM
Figure 3-4 Independent EOMUa networking topology (with two LAN switches)
The two internal Ethernet adapters B_ETH0 and B_ETH1 of the EOMUa board are connected
to the active and standby SCUs in the MPS by using the backplane, respectively.
The two external Ethernet adapters F_ETH0 and F_ETH1 of the EOMUa board are connected
to the O&M terminals by using network equipment such as a hub, LAN switch, or router. In this
way, the OMU fulfills the communication between the BSC6910 and the O&M terminals.
As shown in Figure 3-4, the two external Ethernet ports of the EOMUa board are connected to
the two LAN switches, respectively, which improves network reliability. In this network
topology, external Ethernet ports on the OMU, ports on the LAN switches for the connection
with the OMU, and the ports on the LAN switches for the connection between LAN switches
must be in the same local area network (LAN).
Issue 05 (2014-03-28)

23
BSC6910 GSM
The Ethernet port marked in blue in Figure 3-3 and Figure 3-4 must be enabled with the
Spanning Tree Protocol (STP) function to prevent network storms.
Active/standby EOMUa Networking Principle

Figure 3-5, and Figure 3-6 show the network topology in dual-EOMUa mode.
Figure 3-5 Active/standby EOMUa (with a single LAN switch)
Issue 05 (2014-03-28)

24
BSC6910 GSM
Figure 3-6 Active/standby EOMUa (with two LAN switches)
The two internal Ethernet adapters B_ETH0 and B_ETH1 of the EOMUa board are connected
to the active and standby SCUs in the MPS by using the backplane, respectively.
The two external Ethernet adapters F_ETH0 and F_ETH1 of the EOMUa board are connected
to the O&M terminals by using network equipment such as a hub, LAN switch, or router. In this
way, the OMU fulfills the communication between the BSC6910 and the O&M terminals.
The B_UPDATE Ethernet adapters of the active and standby EOMUa boards are connected by
using the backplane to fulfill the data synchronization and software update between the active
and standby OMUs.
As shown in Figure 3-6, the two external Ethernet ports of the active and standby OMUs are
connected to the two LAN switches, respectively, which improves network reliability. In this
Issue 05 (2014-03-28)

25
BSC6910 GSM
network topology, external Ethernet ports on the OMU, ports on the LAN switches for the
connection with the OMU, and the ports on the LAN switches for the connection between LAN
switches must be in the same local area network (LAN).
The Ethernet port marked in blue in Figure 3-5 and Figure 3-6 must be enabled with the
Spanning Tree Protocol (STP) function to prevent network storms.
3.4 Heartbeat Detection on Active and Standby OMUs

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

In active/standby mode, the synchronization between the active and standby OMUs consists of
data synchronization, file synchronization, and time synchronization.
data synchronization
The OMU data is dynamic, which changes when the BSC6910 is working. After the standby
OMU starts, the active OMU data is fully synchronized, and the increments are synchronized.
This ensures that the OMU can work normally after a switchover.
File Synchronization
The synchronization between active and standby OMU files is mainly applicable to dynamic
files. The dynamic files include the license file, board program, BOOTROM file, DSP file, patch
file, and performance statistics file. The software management module on the standby OMU
regularly checks the active OMU files and synchronizes the dynamic files on the standby OMU
with those on the active OMU. This ensures that the files on the active and standby OMUs are
the same.
Time Synchronization
Time synchronization means that the sntp module on the standby OMU regularly synchronizes
the time with the sntp module on the active OMU. This ensures that the time on the active and
standby OMUs is the same.
Issue 05 (2014-03-28)

26
BSC6910 GSM
3.6 Switchover Between Active and Standby OMUs

For OMUs working in active/standby mode, there are four types of switchover: manual
switchover, fault-triggered switchover, failover, and self-healing switchover.
NOTE
Operation and maintenance (O&M) can be performed on the LMT only after a switchover is successfully
completed.
Manual Switchover
If OMUs work in active/standby mode and data synchronization between the active and standby
OMUs is normal, you can manually switch over the OMUs as required. For example, you need
to manually switch over OMUs for software and hardware upgrade or fault rectification. To
manually switch over the OMUs, run the SWP OMU command or use the LMT. For detailed
operations, see the BSC6910 GSMLMT User Guide. After the manual switchover, the original
standby OMU becomes the active OMU, and the original active OMU becomes the standby
OMU.
Manual switchover can be performed only when the active and standby OMUs work properly.
In addition, at least one of the following conditions must be met:
l
The DSP OMU command output shows that the value for Data-sync state is Data
synchronization is successful.
The DSP OMU command output shows that the version of the active product software is
different from that of the standby product software.
The ALM-20701 OMU Failure Switchover persists after a fault-triggered OMU switchover
is performed.
NOTICE
Before performing the manual switchover, do not perform an operation that may change the data
in the database. For example, do not modify configuration data or user information.
Fault-Triggered Switchover
When the active and standby OMUs operate properly, the active OMU maintains the
BSC6910 and the standby OMU monitors the active OMU. If a fault occurs on the active OMU
and persists for more than 5 minutes, the standby OMU automatically becomes active. After the
fault is rectified, the original active OMU becomes standby. If the fault is rectified within 5
minutes, the switchover does not occur.
After the fault-triggered switchover, the OMU automatically reports the ALM-20701 OMU
Failure Switchover and initiates a Cyclic Redundancy Check (CRC). If the host data is consistent
with the OMU data, the alarm is automatically cleared. If the host data is inconsistent with the
OMU data, the alarm persists.
Issue 05 (2014-03-28)

27
BSC6910 GSM
NOTE
If the DSP OMU command output shows that the values for Internal network link state, External network
state, and Backup network link state are all Breakdown, then the active OMU is faulty.
Self-Healing Switchover
Self-healing switchover is a method of self-healing for OMUs.
The active OMU performs a self-healing switchover when any of the following conditions
occurs:
l
The hard disk capacity of the active OMU overflows if the remaining space is smaller than
200 MB.
An abnormality occurred on the active OMU for 10 times within 30 minutes.
No Ethernet cable is connected to any external Ethernet port on the active OMU.
The virtual internal or external IP address of the active OMU is lost for more than 3 minutes.
The standby OMU detects that the active OMU is restarted abnormally three times within
24 hours.
The connection between the active OMU and SCU is interrupted and the connection
between the standby OMU and SCU is normal.
A fault occurs in one or both of the internal and external networks of the active OMU while
the internal and external networks of the standby OMU are normal.
Issue 05 (2014-03-28)

28
BSC6910 GSM
Initially Commissioning the OMU
About This Chapter

This section describes the procedure for initially commissioning the OMU after delivery.
NOTE
Install product software if the version number is not specified in the BSC6910 order.
For the commissioning procedure in the OM phase, see 6.13 Setting OMU System
Parameters.
In the initial commissioning phase, check the installation of product software, and configure the
IP addresses, subnet masks, and OMU name of OMU Ethernet adapters based on the onsite IP
address plan. For IP addresses and masks to be changed in the initial commissioning phase, see
3.2 OMU IP Address Plan.
Figure 4-1 shows the procedure in the initial commissioning phase.
Issue 05 (2014-03-28)

29
BSC6910 GSM
Figure 4-1 Initial commissioning procedure
4.1 Setting the Link Mode for External OMU Ethernet Adapters
This section describes how to set the link mode of the external OMU Ethernet adapters so that
it is the same as that of the LAN switch.
Before using the OMU for the first time, commission the OMU onsite to check the installation
status and version of the product software, and configure IP addresses of the OMU.
Issue 05 (2014-03-28)

30
BSC6910 GSM
4.1 Setting the Link Mode for External OMU Ethernet

Adapters
This section describes how to set the link mode of the external OMU Ethernet adapters so that
it is the same as that of the LAN switch.
Prerequisites
The link mode, duplex mode, and rate of the LAN switch have been acquired.
Context
If the link mode of the external Ethernet adapters of the OMU is inconsistent with that of the
LAN switch, the network may be interrupted. If the link mode of the LAN switch is specified,
the link mode of the external Ethernet adapter of the OMU should also be specified.
There are two link modes of the LAN switch: forced mode and auto-negotiation mode. The link
mode of the OMU external Ethernet adapter must be consistent with that of the LAN switch.
If active and standby OMUs are configured, perform the following steps on both the active and
standby OMUs:
NOTE
l The following procedure assumes that the link mode of the external Ethernet adapter is forced mode
and the adapter works at 100 Mbit/s in full duplex mode.
l The following procedure assumes that version_a is the active workspace of the OMU.
Procedure
Step 1 Log in to the target OMU by referring to 7.3 Logging In to the OMU.
Step 2 Type the /etc/rc.d/omud stop command and click Enter to stop the omud process
Step 3 Type the cd /mbsc/bam/version_a/bin/bam command and click Enter to navigate to the
directory that contains omutool
Step 4 Run the ./omutool duplexmode 100 full off command.
NOTE
For details about how to query the link mode of the external OMU Ethernet adapters, see 6.4 Querying
the Link Mode of the External OMU Network Adapters.
The fields in the ./omutool duplexmode 100 full off command are described as follows:
l 100 indicates that the rate of the Ethernet adapter is 100 Mbit/s. The value of this field can be 10, 100,
or 1000. If the Ethernet adapter of the peer switch cannot work at 1000 Mbit/s, the external network
connection of the OMU is interrupted when the rate of the OMU Ethernet adapter is set to 1000 Mbit/
s.
l full indicates that the Ethernet adapter works in full duplex mode. The value of this field can be full
or half.
l off indicates that the link mode of the Ethernet adapter is forced mode. The value of this field can be
off or on. When the value of this field is on, the link mode is auto-negotiation mode.
Issue 05 (2014-03-28)

31
BSC6910 GSM
Step 5 Enter the /etc/rc.d/omud start command and press Enter to start the omud
----End

Before using the OMU for the first time, commission the OMU onsite to check the installation
status and version of the product software, and configure IP addresses of the OMU.
Prerequisites
The OMU is connected to the local PC using the commissioning Ethernet port.
Context
NOTE
If the product software have been installed before delivery, the active workspace of the OMU is version_a.
If the product software have been installed before delivery, refer to 9.2 Checklist for the OMU Software
Factory Settings for the initial parameters of the OMU.
If the product software are not installed before delivery, plan items in 9.1 Information Records of OMU
Software Installation, and then install the product software.
Procedure
Step 1 Connect the PC to the OMU board.
1.
Connect the PC to the ETH2 commissioning port on the OMU board by using a network
cable.
2.
Set the IP addresses of the PC and ETH2 port to be on the same network segment.
The initial IP address of the ETH2 port is 192.168.6.50 (active OMU) or 192.168.6.60
(standby OMU), and the subnet mask is 255.255.255.0.
Step 2 Set the link mode of the external OMU Ethernet adapters.
1.
Log in to the OMU by referring to 7.3 Logging In to the OMU in the BSC6910 GSMOMU
Administration Guide.
2.
Check whether the link mode of the external OMU Ethernet adapters is consistent with that
of LAN switches.
For details about how to query the link mode of the external OMU Ethernet adapters, see
Follow-up Procedure of 4.1 Setting the Link Mode for External OMU Ethernet
Adapters in the BSC6910 GSMOMU Administration Guide.
Issue 05 (2014-03-28)
If...
Then...
The link mode of the external OMU

Ethernet adapters is consistent with that of
LAN switches
Go to Step 3.

32
BSC6910 GSM
If...
Then...
The link mode of the external OMU

Ethernet adapters is inconsistent with that
of LAN switches
Set the link mode of the external OMU

network adapters to be consistent with that
of LAN switch by referring to operations
in Procedure of 4.1 Setting the Link Mode
for External OMU Ethernet Adapters in
BSC6910 GSMOMU Administration
Guide.
Step 3 Install the product software.

1.
Run the /etc/rc.d/omud status command to check the running status of the OMU process.
If...
Then...
The information displayed is running
1. Run the /etc/rc.d/omud stop command

to stop the omud process.
2. Go to Step 3.2.
The information displayed is unused
Go to Step 3.2.
The information displayed is No such file

or directory
1. Install the product software in the active

workspace by referring to operations in
Procedure of 5.3.3 Installing the
Product Software in the Active
Workspace in the BSC6910
GSMOMU Administration Guide.
2. Go to Step 6.
3. Go to Step 7. The task is complete.
2.
Issue 05 (2014-03-28)
Run the cd /mbsc/upgrade command to switch to the OMU installation directory, and then
run the ls command to query the current versions of the product software.
If...
Then...
The versions of the product software are

the same as those required by the operator
Go to Step 4.

33
BSC6910 GSM
If...
Then...
The versions of the product software are

different from those required by the
operator
1. Uninstall the product software by

referring to operations in Procedure of
6.11.4 Uninstalling the Product
Software in the BSC6910 GSMOMU
2. Upload the OMU application
installation package to the OMU by
referring to operations in Procedure of
Uploading the OMU Application
Installation Package to the OMU in
the BSC6910 GSMOMU
3. Install the product software in the active
workspace by referring to operations in
Procedure of 5.3.3 Installing the
Product Software in the Active
Workspace in the BSC6910
GSMOMU Administration Guide.
4. Go to Step 6.
5. Go to Step 7. The task is complete.
Step 4 Modify the OMU IP addresses.

1.
Run the cd /mbsc/bam/version_a/bin/bam command to switch to the directory where the

omutool program is located.
NOTE
You can run the ./omutool -h command to view the help information of the omutool.
2.
Change the fixed external IP address and subnet mask according to the plan of the operator.
Run the ./omutool extercard The external fixed IP address The subnet mask The gateway
IP address (Optional) command to change the fix external IP address and the subnet mask.
For example, you can type the following command and then press Enter.
./omutool extercard 10.161.10.100 255.255.255.0
NOTE
l The following two methods show how to change the fixed external IP address if changing the
gateway IP address is required at the same time.
l Method 1: Type ./omutool extercard The external fixed IP address The subnet mask (The
gateway IP address) and then press Enter to change the fixed external IP address and gateway
IP address at the same time. The following is an example:
./omutool extercard 10.161.10.100 255.255.255.0 10.161.10.1
l Method 2: Type ./omutool gateway The gateway IP address and then press Enter to change
the gateway IP address separately. The following is an example:
./omutool gateway 10.161.10.1
l After the fixed external IP address is changed, the OMU can be connected to the operation and
maintenance (OM) network of the operator by using the ETH0 or ETH1 port. In this case, the
commissioning task can continue remotely.
Issue 05 (2014-03-28)

34
BSC6910 GSM
3.
Change the virtual external IP address and the subnet mask of the active and standby OMUs
according to the plan. Ensure that the virtual external IP address is on the same network
segment as the fixed external IP address.
Run the ./omutool extervip The external virtual IP address The subnet mask command to
change the virtual external IP address and the subnet mask. For example, you can type the
following command and then press Enter.
./omutool extervip 10.161.10.102 255.255.255.0
NOTE
When the fixed or virtual external IP address is being changed, a window is displayed to remind users
to check whether the virtual or fixed external IP address and the gateway IP address need to be
changed. In this way, users can make necessary changes to ensure that the three IP addresses are on
4.
Issue 05 (2014-03-28)
Check whether the fixed internal IP address, virtual internal IP address, backup channel IP
address, and debugging IP address of active and standby OMUs are on the same network
segment as the operator's network.

35
BSC6910 GSM
If...
Then...
All of the preceding IP addresses

are on the same network
segment as the network of the
operator
Change the IP address in conflict.

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

IP address command to change the virtual internal
IP address and the subnet mask. For example, you
Enter.
./omutool innervip 80.168.3.40
NOTE
l When the fixed or virtual internal IP address is being
changed, a window is displayed to remind users to
check whether the virtual or fixed internal IP
address needs to be changed. In this way, users can
make necessary changes to ensure that the two IP
addresses are on the same network segment.
l If the network segment of the virtual or fixed
internal IP address is changed, the Subnet No. must
be changed when updating the OMU database. For
details, see Follow-up Procedure in Updating the
OMU Database to ensure that the OMU
communicates properly with the BSC6910 host.
l Change the backup channel IP address and subnet

mask of the active and standby OMUs:
Run the ./omutool backupcard The IP address
command. For example, you can type the
following command and then press Enter.
./omutool backupcard 192.168.3.60
l Run the ./omutool debugcard The debugging IP

address command to change the debugging IP
address and the subnet mask. For example, you
Enter.
./omutool debugcard 192.168.6.60
The preceding IP addresses are

not on the same network
segment as the network of the
operator
Change the backup channel IP address of the standby

OMU.
Run the ./omutool backupcard The IP address
command. For example, you can type the following
command and then press Enter.
Step 5 Change the OMU name.

1.
Issue 05 (2014-03-28)
Run the ./omutool hostname OMU name command to change the name of the OMU.
36
BSC6910 GSM
For example, you can type ./omutool hostname omu_123 and then press Enter.
NOTE
The OMU name cannot contain control characters, spaces, or any of the following characters: / \ [ ] ( ) ' :
| < > + = ; , ?, and the length of the OMU name ranges from 1 to 62 characters.
Step 6 Set the working mode of the OMU.

1.
Set the OMU backup attribute.

l If only one OMU board is configured, run the ./omutool dualmode single command
to set the OMU to work in independent mode.
l If two OMU boards (active and standby OMU boards) are configured, run the ./omutool
dualmode dual command to set the OMU to work in active/standby mode.
2.
Set the product mode.

a.
Run the /etc/rc.d/omud start command to start the product software.
b.
Run the MML command SET OFFICENAME to set the product mode.
Step 7 Check the OMU running status.

1.
Run the ps -afx command to check the running status of the OMU.
The OMU is operating properly if all OMU processes exist in the OMU active workspace
directory /mbsc/bam/version_a/bin/bam/monitor.
OMU State
OMU Processes that Must Exist
Active OMU
host_gate, ems_gate, authority,

configure, maintain, stat, alarm,
software, ftp_server, sntp, btsom,
ems_agent, omu_manager, cfa, weblmt,
debug_log, and cfg_mirror
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 product software and then reinstall the product software in the active workspace by referring to
operations in Procedure of 6.11.4 Uninstalling the Product Software and 5.3.3 Installing the
Product Software in the Active Workspace in the BSC6910 GSMOMU Administration Guide.
2.
Run the exit command to stop the PuTTY and then remove the cable to the OMU.
----End
Issue 05 (2014-03-28)

37
BSC6910 GSM
Installing OMU Software
About This Chapter

If an OMU board is damaged onsite, replace it. If the operating system fails, reinstall it along
with the product software.
For details about the OMU software structure, see 2.2 OMU Components.
1.
5.1 Preparations
Before reinstalling the OMU software onsite, gather the following items: the OMU board,
a portable PC, theBSC6910 version installation package or patch installation package, and
the Dopra_Linux_U tool.
2.
5.2 Optional: Installing Product Software by Using a USB Storage Device

This section describes how to install the Dopra Linux operating system (OS) and
applications on the OMU by using a prepared USB storage device.
3.
5.3 Optional: Manually Installing the Product Software

If the product software are not installed during the process of preparing the USB flash drive,
then the product software must be installed manually after the OMU operating system is
installed.
Issue 05 (2014-03-28)

38
BSC6910 GSM
5.1 Preparations
Before reinstalling the OMU software onsite, gather the following items: the OMU board, a
portable PC, theBSC6910 version installation package or patch installation package, and the
Dopra_Linux_U tool.
Configuration of the OMU Board

See the hardware configuration indexes of the OMU boards described in Technical
Specifications of the EOMUa Board.
Configuration Requirements for the Portable PC

Table 5-1 lists the configuration requirements for the portable PC.
Table 5-1 Description
Configu
ration
Item
Quantity
Recommended Setting
Minimum Configuration
CPU
1.66GHz or higher
866 MHz
RAM
512 MB
256 MB
Hard disk
80 GB
10 GB
Display
resolutio
n
1024 x 768 or higher
800 x 600
CDROM
drive
USB
flash
drive
Operatin
g system
l Microsoft Windows XP
Professional
l Microsoft Windows
Server 2003
l Microsoft Windows 7
Check that Microsoft .NET Framework 2.0 or later has been installed on the portable PC.
Issue 05 (2014-03-28)

39
BSC6910 GSM
NOTE
To check whether Microsoft .NET Framework 2.0 or later has been installed, choose Start > Settings >
Control Panel > Add or Remove Programs to view the components installed on the portable PC. If
Microsoft .NET Framework 2.0 or later has not been installed on the portable PC, run dotnetfx2.0.exe
under the \tools directory of the Dopra_Linux_U tool software package.
Required Software
Ensure that the following software package is available:
l
BSC6910 version installation package or patch installation package
Dopra_Linux_U tool software package

NOTE
Contact Huawei engineers who can obtain the installation package and tool by performing the following
operation:
l Log in to http://support.huawei.com/support/ and choose Software Center > Version Software >
Wireless Product Line > SingleRAN > MBSC > BSC6910 > BSC6910 Product Version > BSC6910
Software Version.
l Click Software Version VER to obtain the BSC6910 version installation package.
l Log in to http://support.huawei.com/support/ and choose Software Center > Version Software >
Wireless Product Line > SingleRAN > SRAN O&M tools to obtain the Dopra_Linux_U tool.
5.2 Optional: Installing Product Software by Using a USB

Storage Device
This section describes how to install the Dopra Linux operating system (OS) and applications
on the OMU by using a prepared USB storage device.
Prerequisites
l
There are USB ports available on the OMU board panel.

NOTE
The USB flash device with an indicator is inserted into the USB port. If the indicator is on, then the USB
port is available.
Context
This operation applies to establishing a newly deployed BSC6910 because all the data in the
OMU hard disks will be lost after the disks are formatted during the operation.
Procedure
Step 1 Prepare a USB storage device. For details, see Preparing the USB storage device for initially
installing the OMU operating system and applications in 8.3 Dopra_Linux_USB Disk
Tool.
Step 2 Insert the USB flash device into any of the USB ports on the OMU board panel.
Step 3 Remove and then reinstall the OMU board to reset the OMU.
Issue 05 (2014-03-28)

40
BSC6910 GSM
NOTE
Press and hold the two locking buttons, flip the ejector levers out on the OMU board panel to unlock them,
and rotate them outward. The OMU board is separated from the backplane. Remove the OMU board after
the OFFLINE LED flashes fast and then is steady blue.
Step 4 Wait 1 to 2 minutes and then use the USB flash device to install the OMU operating system.
Check the status of indicators on the OMU board panel to determine whether the OMU operating
system is installed successfully.
l If only the operating system is to be installed on the OMU, check the indicator status. See
Table 5-2.
l If the operating system and applications are to be installed on the OMU, check the indicator
status. See Table 5-3.
l If the OMU operating system is to be restored, check the indicator status. See Table 5-2.
NOTE
If the status of the indicators differs from this, the OMU cannot identify the USB flash device. When this occurs,
prepare another USB flash device. Alternatively, copy the data in the original USB flash device to a new USB
flash device, and then reinstall the OMU operating system.
For information about how much time will be consumed during the OMU operating system installation, see
Table 1 in 8.3 Dopra_Linux_USB Disk Tool.
Table 5-2 Status of the indicators on the OMU board panel during the OMU operating system
installation
Issue 05 (2014-03-28)
Board
Installation Procedure
Successful
Installation
Failed Installation
EOMUa
l The RUN indicator

blinks.
l The RUN indicator

blinks.
l The RUN indicator is

off.
l The ALM indicator

blinks.
l The ALM indicator is

off or blinks.
l The ALM indicator

blinks.
l The ACT indicator

blinks.
l The ACT indicator is

off.

off.
l The OFFLINE
indicator is off.
l The OFFLINE
indicator blinks.
l The OFFLINE
indicator blinks.

41
BSC6910 GSM
Table 5-3 Status of indicators on the OMU board panel during the OMU operating system and
product software installation
Board
Installation Procedure
Successful
Installation
Failed Installation
EOMUa
At the beginning:
l The RUN indicator

blinks.
l The RUN indicator

blinks.

steady on or off.
l The ALM indicator

blinks.

steady on or off.

off.
l The OFFLINE
indicator is off.
l The OFFLINE
indicator is off.
l The RUN indicator

blinks.
l The ALM indicator
blinks.
l The ACT indicator
blinks.
l The OFFLINE
indicator is off.
After a certain period:
l The RUN indicator
blinks.
off.
off.
l The OFFLINE
indicator blinks.
NOTICE
l After the OMU operating system is installed successfully, remove the USB flash device from
the OMU board panel in a timely manner.
l After the OMU operating system is restored using a USB flash drive, the password changes
to the default value.
l If the version of the OMU operating system is V200R003C02SPC090 or later, log in to
the active OMU as the lgnusr user, for whom the initial password is osnormal@123. Do
not log in to the OMU as the root user. After the login succeeds, you can run the su
command to switch to the root user, for whom the initial password is osadmin@123.
l If the version of the OMU operating system is earlier than V200R003C02SPC090, log in
to the active OMU as the root user, for whom the initial password is mbsc@com.
l If you do not know the version of the OMU operating system, try to log in to the active
OMU first as the lgnusr user and then the root user.
----End
Follow-up Procedure
If the OS fails to be installed, do as follows:
Issue 05 (2014-03-28)

42
BSC6910 GSM
1.
Prepare a new USB storage device. For details, see Step 1.

l If the OS is installed successfully, no further action is required.
l If the OMU operating system fails to be installed, contact Huawei for technical support.
5.3 Optional: Manually Installing the Product Software

If the product software are not installed during the process of preparing the USB flash drive,
then the product software must be installed manually after the OMU operating system is installed.
Context
l
When reinstalling the product software, re-import the OMU configuration data. You must
back up the OMU data before reinstalling the product software and restore the OMU data
after the installation. For details, see 6.12.1 Backing Up System Data and 6.12.2 Restoring
System Data.
When installing the product software for the first time, the product software can be installed
only on the active workspace of the OMU, and the OMU data does not need to be backed
up.
NOTE
This section uses the version installation package named V100R015C00 as an example to illustrate how to install
the product software.
5.3.1 Obtaining Information About OMU Software Installation

Before installing the product software, 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 product software, obtain the following information. For details, see 9.1
Information Records of OMU Software Installation.
l Password of the operating system administrator
l Fixed IP address of the external network, virtual IP address of the external network, and
debugging IP address of the OMU.
----End
5.3.2 Uploading the OMU Application Installation Package to the

OMU
Before installing the product software, upload the OMU application package to the specified
directory of the OMU.
Prerequisites
l
Contact Huawei engineers who can obtain the OMU application installation package
including the patch installation package by performing the following operation:
You have obtained the OMU application installation package including the patch
installation package by accessing http://support.huawei.com/support/ and choosing
Issue 05 (2014-03-28)

43
BSC6910 GSM
Software Center > Version Software > Wireless Product Line > Single RAN >
MBSC > BSC6910.
l
The psftp has been obtained. For details about the psftp, see 8.1 psftp Software.
The OMU application installation package must be uploaded to the /mbsc/upgrade

directory of the OMU.
The OMU application installation package must be named after the version number. That
is, after the OMU application installation package is uploaded to the OMU, the directory
of the installation package on OMU is "/mbsc/upgrade/V100R015C00."
If patches also need to be installed, you must check whether the original patch files exist
in the patch folder in the OMU application installation package before installing the OMU
application. If yes, you must delete the original patch files in the patch folder in the OMU
application installation package and copy the patch installation package (for example, the
V100R01XC0XSPCXXX folder) saved on the local computer.
Context
NOTE
If you need to delete the patch files V100R01XC0XSPCXXX in the patch directory, navigate to
the /mbsc/upgrade/V100R015C00/patch directory and then run rm -r
\V100R01XC0XSPCXXX.
During the uploading process, if the root user cannot log in to the OMU, check with the
equipment room operators to determine whether the 11.1 Disabling root user login with
SSH function has been enabled on the BSC6910. If so, you must log in to the OMU as a
lgnusr user or common user, and then continue with the uploading task.
NOTE
As an example, this task uploads the V100R015C00 version installation package to the /mbsc/upgrade directory
of the OMU and downloads version files from http://support.huawei.com/support/ to local drive D.
The default IP address of the external Ethernet adapter team of the active OMU is 172.121.139.201
(255.255.255.0).
The default IP address of the external Ethernet adapter team of the standby OMU is 172.121.139.202
(255.255.255.0).
Procedure
l
Log in to the OMU as the lgnusr user and upload the OMU application package to the
OMU.
1.
Decompress the BSC6910 version installation package to a local drive D.
2.
Log in to the OMU as the lgnusr user by using psftp. For details, see 8.1 psftp
Software.
3.
Type the lcd D:\ command and press Enter to navigate to the local directory where
version files are saved.
4.
Type the cd /home/lgnusr command and press Enter to switch to the directory of the
lgnusr user.
NOTE
The default direcotry of the lgnusr user is /home/lgnusr. The lgnusr user has the read/write
permissions to this directory.
5.
Issue 05 (2014-03-28)
Type the put -r commandV100R015C00 and press Enter to upload files.

44
BSC6910 GSM
6.
After files are uploaded, enter exit and press Enter to exit psftp.
7.
Log in to the OMU as the lgnusr user by using PuTTY and switch to the root user
account. For details, see 7.3 Logging In to the OMU.
8.
Type ls /mbsc/upgrade command and press Enter to query whether there is the /
mbsc/upgrade directory on the OMU.
If the /mbsc/upgrade directory does not exist, go to Step 9.
If the /mbsc/upgrade directory exists, go to Step 10.
9.
Type the mkdir /mbsc/upgrade command and press Enter to set up an installation
directory on the OMU.
NOTE
Run the commands mkdir /mbsc and mkdir /mbsc/upgrade in sequence to create the /mbsc/
upgrade directory hierarchically.
10. Run the cp /home/lgnusr/V100R015C00 -r /mbsc/upgrade/ command to copy the

intallation package under the /home/lgnusr directory to the OMU installation
directory.
11. Enter exit and press Enter to exit PuTTY.
l
Logging in to the OMU as a common user and uploading the OMU application installation
package to the OMU
1.
Log in to the OMU as a common user by using PuTTY and switch to the root user
account. For details, see 7.3 Logging In to the OMU.
2.
Type the path=`grep xxx /etc/passwd | cut -d:-f 6`; if [ !-d $path ] ; then mkdir p $path; chown xxx $path; fi command and press Enter to establish a common user
information file directory.
NOTE
In the command above, xxx indicates the name of a common user.
3.
Type the cat /etc/passwd command and press Enter to query all the common user
file directories.
NOTE
If the queried result is omcuser:x:1001:100::/home/omcuser:/bin/bash, then the user files

directory for omcuser is /home/omcuser. In later operations, the /home/omcuser directory of the
common user omcuser is used as an example.
4.
Type the exit command and press Enter to log out of PuTTY.
5.
Decompress the BSC6910 version installation package to the local drive D.
6.
Log in to the OMU as a common user by using the psftp software.
7.
Type the lcd D:\ command and press Enter to log in to the local directory for version
files.
8.
Type the cd /home/omcuser command and press Enter to go to the user file directory
of the common user omcuser.
9.
Type the put -r V100R015C00 command and press Enter to upload the OMU
application installation package to the OMU.
10. After the uploading is complete, enter the exit command and press Enter to exit the
psftp software.
11. Repeat Step 1 to log in to the OMU as a common user and switch the account from
common user to root user.
Issue 05 (2014-03-28)

45
BSC6910 GSM
12. Type the ls /mbsc/upgrade commandand press Enter to query whether there is an
installation directory on the OMU.
13. Type the mkdir /mbsc/upgrade command and press Enter to create an installation
directory on the OMU.
NOTE
14. Type the cp /home/omcuser/V100R015C00 -r /mbsc/upgrade/ command and copy

the version installation package under the /home/omcuser directory to the OMU
installation directory.
15. Type the exit command and press Enter to log out of PuTTY.
l
Logging in to the OMU as a root user and uploading the OMU application installation
package to the OMU
NOTE
If failing to log in to the OMU as a lgnusr user or a common user, log in to the OMU as a root user.
1.
Decompress the BSC6910 version installation package to the local drive D.
2.
Log in to the OMU as the root user by using the psftp. For details, see 8.1 psftp
Software.
3.
Run the lcd D:\ command to go to the directory on the local PC where the version
files are saved.
4.
Run the ls /mbsc/upgrade command to query whether there is an installation directory

on the OMU.
5.
Run the mkdir /mbsc/upgrade command to create the installation directory on the
OMU.
NOTE
6.
Run the cd /mbsc/upgrade command to go to the OMU installation directory.
7.
Run the put -r V100R015C00 command to upload the OMU application installation
package to the OMU.
NOTE
If the package fails to be uploaded, check whether any file with the same name as the package name
is in use. If there is such a file, release it.
8.
After the upload is complete, enter the exit command to exist the psftp software.
----End
5.3.3 Installing the Product Software in the Active Workspace

This section describes how to install the product software in the active workspace. If the
BSC6910 is configured with active and standby OMU boards, install the product software in the
active workspace of each individual board.
Issue 05 (2014-03-28)

46
BSC6910 GSM
Prerequisites
l
Obtained information about OMU software installation.
Uploaded the OMU application installation package to the OMU.
Context
Run a command to install the install_bam program contained in the BSC6910 version installation
package. Type the related parameters during the process.
If product software have been pre-installed on active and standby OMU boards, unintall them
before installing the product software of a correct version. To check whether product software
have been pre-installed, do as follows:
1.
Log in to the OMU by using the fixed external IP address or commissioning IP address.
For details, see 7.3 Logging In to the OMU.
2.
Input the cd /etc/ssh/ command and press Enter to go to the target directory.
3.
Type the ls command and press Enter to navigate to the current directory.
l If the omud file is in the directory, product software have been pre-installed. Uninstall
them by following operation steps in 6.11.4 Uninstalling the Product Software.
l If the omud file is not in the directory, product software have not been pre-installed.
Install the product software following the installation procedures.
4.
Type the exit command to close PuTTY.
Procedure
Step 1 Use the fixed external IP address or commissioning IP address to log in to the OMU by referring
to 7.3 Logging In to the OMU and navigate to the directory where the OMU application
installation package is saved.
Assume that the OMU application installation package install_bam.sh is saved in /mbsc/
upgrade/V***R***C**/install/setup. Run the following command and press Enter:
cd /mbsc/upgrade/V***R***C**/install/setup
Step 2 Type the chmod +x ./install_bam.sh command and press Enter to obtain the permission to run
the ./install_bam.sh command.
Step 3 Type the ./install_bam.sh command and press Enter.
Step 4 The system prompts you to type the product running mode. Type the product running mode and
press Enter.
[2011-05-03 10:12:32] software integrality verify begin...
[2011-05-03 10:12:42] software integrality verify end...
# The run mode of the product
# GO:GSM only
# UO:UMTS only
# GU:GSM and UMTS
# Please select one mode to install.
Please input a valid run_mode :
NOTE
The software integrity of the product software is checked before they are installed. The product software can be
installed only if the check passes.
Issue 05 (2014-03-28)

47
BSC6910 GSM
Step 5 The system prompts you to type the office name. Type the office name and press Enter.
# 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 6 The system prompts you to type the language version. Type the language version and press
Enter.
# The OMU language version. eg: eng/chs
Please input a valid version :
Step 7 The system prompts you to type the admin password. Type the admin password, confirm it, and
press Enter.
# The "admin" user's password of OMU service.
# The password must range from 8 to 32(characters).The characters must be uppercase
letters, lowercase letters, digits, or special characters.
Special characters include spaces and the following characters:~!@#$%^&*()_+-{}|
[]:<>?./
The password must consist of 2 types of uppercase letter,lowercase letter,digit or
special character at least.
# Do not forget the password.
# You can change the password later, but this password should be provided first.
Please input a valid admin_password :
Please input a valid Confirm password :
NOTE
The admin password is the initial password for the administrator to log in to the LMT.
Step 8 The system prompts you to type the FTP password. Type the FTP password, confirm it, and
press Enter.
# The ftp user's password of OMU service
# The password must range from 8 to 32(characters).The characters must be uppercase
letters, lowercase letters, digits, or special characters.
Special characters include spaces and the following characters:~!@#$%^&*()_+-{}|
[]:<>?./
The password must consist of 2 types of uppercase letter,lowercase letter,digit or
special character at least.
# Do not forget the password.
# You can change it later, but this password should be provided first.
Please input a valid ftp_password :
Please input a valid Confirm password :
NOTE
The FTP password is customized. After the product software are installed, you can access the FTP service
with the FTP password.
Step 9 The system prompts you to type the virtual external IP address. Type the virtual external IP
address and press Enter.
# The extranet IP address, subnet mask, and default gateway.
# example: 192.168.1.9/255.255.255.0;192.168.1.1
Please input a valid virtual_extranet_config :
Issue 05 (2014-03-28)

48
BSC6910 GSM
NOTE
The virtual external IP address must be located on the same network segment as the fixed external IP
address.
The default IP address of the external Ethernet adapter team of the active OMU is 172.121.139.201
(255.255.255.0).
The default IP address of the external Ethernet adapter team of the standby OMU is 172.121.139.202
(255.255.255.0).
After the product software are installed, you can refer to 6.13.2 Changing IP Addresses and Subnet
Masks of OMU Ethernet Adapters change the IP addresses and subnet masks of the OMU Ethernet
adapters.
Step 10 The system prompts you to type the OMU system type. Type the OMU installation type based
on the field configuration and press Enter. Table 5-4 describes the OMU system types.
# The OMU system type. eg: Single/Dual
# Single:Install stand-alone system
# Dual:Install dual-OMU system.
The dual-OMU system can effeciently increase the reliability of the OMU system.
Please input a valid install_type :
Table 5-4 Installation types

Parameters
Description
Single
When the BSC6910 is configured with one

OMU board, install the product software on
the board in single mode.
Dual
When the BSC6910 is configured with two

OMU boards, install the product software on
the boards in dual mode.
Step 11 The system asks you whether to continue with the installation, as shown:
Please affirm input information. input Y to continue; input E to exit. ->
Step 12 Type Y to install the product software. When the message Install OMU succeed! is
displayed, the product software are successfully installed.
Step 13 Record the information about the product software installation in 9.1 Information Records of
OMU Software Installation.
----End
5.3.4 Checking the Installation Directory of Product Software

By default, the installation directory for product software is /mbsc/bam. The OMU application
components, BSC6910 host software, and data used or generated by the BSC6910 are stored in
this directory.
Background Information
The default installation directory for the product software is /mbsc/bam/, which cannot be
changed.
Issue 05 (2014-03-28)

49
BSC6910 GSM
Steps
1.
Log in to the target OMU by referring to 7.3 Logging In to the OMU.
2.
Type the cd /mbsc/bam command and press Enter to navigate to the OMU installation
directory.
3.
Check whether the OMU installation directory has the same structure as is shown in Figure
5-1 or Figure 5-2.
Determining Directory Structure

l
Figure 5-1 shows the directory structure of the product software when they are installed
on the active OMU workspace for the first time.
Figure 5-2 shows the directory structure of product software when they are installed on
both the active and standby workspaces. The structures of the version_b and version_a
folders are the same.
NOTE
l Active and standby OMU workspace files are segregated by type into version_a and version_b folders.
l Run the LST OMUAREA command to query the OMU workspace information. If the Workarea
flag is version_a, the version_a folder saves active workspace files.
l Figure 5-1 and Figure 5-2 show the directory structure of the product software in different conditions.
Figure 5-1 Directory structure of product software on the active workspace
Issue 05 (2014-03-28)

50
BSC6910 GSM
Figure 5-2 Directory structure of product software on the active and standby workspaces
NOTICE
Deleting any file from the installation directory of the product software will cause an
unpredictable impact to the BSC6910.
File Folders
Table 5-5 describes the file folders in the installation directory of the OMU application.
Table 5-5 File folders in the OMU application directory
Issue 05 (2014-03-28)
Contents
Description
common/bts
Stores base station board software (including patches), base

station inventory information, base station logs, and base
station RET antenna software
common/ems
Stores the M2000-related data
common/fam
Stores host log files and performance statistics files
common/fam/fad
Stores the last word of the host
common/fam/fad/linuxinf
Stores the dump and ftrace logs of the Linux operating

system
common/fam/fad/linuxinf/
linuxproc
Stores the process statistics logs of the Linux operating

system
common/fam/famlog
Stores host log files, which record platform-related log

information. Users can open the files to view the
information

51
BSC6910 GSM
Issue 05 (2014-03-28)
Contents
Description
common/fam/famlogfmt
Stores binary logs of the host
common/fam/famlogfmt/
btsinfo
Stores files that record basic information about the base

station
gchr
Stores basic information and logs about abnormal calls
gphr
Stores the call history record (CHR) for the packet switched
(PS) domain
pchr
Stores files recording detailed information about each call

for KPI analysis. The information includes service access,
call release, handover, and signal qualities
pchr/special
Stores special PCHR logs, including PCHR exception logs,

PCHR logs for all VIP users, and PCHR logs for all cells
sysfault
Stores information about severe hardware and software

faults, such as resource leakage, and equipment failure.
This information is used for network health check
viptrace
Stores tracing files of VIP subscribers
common/fam/mr
Stores AMR measurement files
common/fam/pfm
Stores the original performance statistics files that are

reported by the host to the OMU
common/fam/smlc
Stores files about the locating function
common/fam/ibst_file
Stores tracing files recording the TC management

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

frequency scanning logs, and site commissioning logs
common/services
Stores the common programs of the active and standby

OMU workspaces
common/weblmt_cfg
Stores the configuration files for the LMT
common/MeasResult
Stores the performance statistics files that are aggregated

and generated by the OMU
common/reg.ini
Stores registry files
version_a/bin/bam
Stores the program files, configuration files, and patch files

for the OMU. Do not perform any operations on this
directory

52
BSC6910 GSM
Issue 05 (2014-03-28)
Contents
Description
version_a/bin/fam
Stores the program files and data files for the host. Do not
perform any operations on this directory.
version_a/data/backup
Stores backup files of the OMU database
version_a/data/backup/
data_backup/mml
Stores MML-format configuration data backed up by the

host
data_restore/db_data
Stores the DB-format configuration data downloaded from

the M2000 in DB format for restoration
data_restore/mml
Stores the MML-format configuration data downloaded

from the M2000 for restoration
version_a/ftp/bts_upgrade
Stores base station upgrade files
version_a/ftp/cert
Stores the digital certificates sent from the network

management element
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 the performance measurement task files in use
version_a/ftp/
DefaultMeasSync
Stores the performance synchronization task files
version_a/ftp/device_file
Stores the hardware archives exported from the host
version_a/ftp/e_label
Stores electronic label files exported from the host
version_a/ftp/ExportBCPFile
Stores exported BCP files
version_a/ftp/
ExportCMESyncView
Stores files about the "configure" process. These files are

used for the synchronization between the NE and the CME
or M2000
version_a/ftp/export_cfgmml
Stores exported MML scripts
version_a/ftp/license
Stores the license files that have not been activated
version_a/ftp/MeasDefinition
Stores the multi-mode performance measurement task files

and measurement definition files
version_a/ftp/licusage
Stores files about license usage recorded within 24 hours.

These files are used for analyzing reports from the M2000
version_a/ftp/operator_log
Stores operation log files and security log files of the

standby OMU
version_a/license
Stores the activated license files
version_a/log
Stores the operation logs of the OMU

53
BSC6910 GSM
Issue 05 (2014-03-28)
Contents
Description
version_a/omu_shm
Part of the OMU memory space is used as the hardware

space. The file containing the mapping between the OMU
memory and the hardware space is saved in this directory.
version_a/security_file
Stores the configuration file of the antivirus software and

the backup configuration file for system recovery
/mbsc/weblmt
Stores LMT online help files
/mbsc/upgrade
Stores the software package of the version to be upgraded
/mbsc/upgrade/log
Stores upgrade log files
/mbsc/upgrade/os_patch
Stores operating system patch files
/mbsc/bam/common/fam/fad/
linuxinf/linuxproc
Saves the logs related to the Linux operating system in the

host boards
/mbsc/bam/common/fam/fad/
linuxinf
Saves the logs related to process scheduling and scheduling

stack of the Linux operating system in the host boards

54
BSC6910 GSM
Operating and Maintaining the OMU
About This Chapter

This section describes how to perform operation and maintenance on the OMU after product
software are installed. To perform this task, log in to the OMU remotely or run MML commands.
6.1 Querying the Mapping Between Ethernet Adapters
This section describes the mapping between the physical and logical Ethernet adapters.
6.2 Querying the Configuration of the OMU Ethernet Adapters
This section describes how to query the configuration information of the OMU Ethernet adapters.
The information includes IP addresses, their subnet masks, and broadcast IP addresses.
6.3 Querying Occupied OMU Ports
This section describes how to query occupied OMU ports.
6.4 Querying the Link Mode of the External OMU Network Adapters
This section describes how to query the link mode of the external OMU network adapters: duplex
mode and adaptive mode.
6.5 Checking the Version of the Operating System
This section describes how to check that the version of the operating system on the OMU is
correct.
6.6 Changing the Administrator Password of the Operating System
This section describes how to change the password of the operating system administrator to
ensure that the administrator account is secure.
6.7 Setting RAID 1 on OMU Hard Disks
This section describes how to set RAID 1 on OMU hard disks to ensure data synchronization
between the source and target OMU hard disks.
6.8 Adjusting OMU Slots
This section describes how to adjust the slots where the operation and maintenance unit (OMU)
is installed.
6.9 Transferring OMU Files to a Local PC
Transferring files between a local PC and the OMU by using the FTP protocol is an important
method for saving files during operation and maintenance.
Issue 05 (2014-03-28)

55
BSC6910 GSM
6.10 Managing the Operating Status of the OMU

This section describes how to manage the operating status of the OMU by running MML
commands.
6.11 Managing the Product Software
This section describes how to manage the product software.
6.12 Backing Up and Restoring Data
This section describes how to use the omu_backup_linker tool to back up or restore the OMU
configuration data, alarm data, and performance data. When the OMU works in active/standby
mode, the omu_backup_linker tool can be used only on the active OMU. Otherwise, the OMU
data may be lost. For details, see 7.1 Starting the omu_backup_linker Tool.
6.13 Setting OMU System Parameters
This section describes how to use the omutool to modify the configuration data of the active and
standby OMUs, including the OMU working mode, IP addresses and subnet masks of the internal
and external networks, and admin password. This section describes how to adjust OMU system
parameters only during the maintenance process. For the procedure for setting OMU system
parameters during initial OMU commissioning (that is, new deployment), see 4 Initially
Commissioning the OMU.
Issue 05 (2014-03-28)

56
BSC6910 GSM
6.1 Querying the Mapping Between Ethernet Adapters

This section describes the mapping between the physical and logical Ethernet adapters.
Prerequisites
The product software are installed.
Procedure
Step 1 Log in to the OMU by referring to 7.3 Logging In to the OMU.
Step 2 To query the factory settings of the Ethernet adapters of the EOMUa board, type the ./
eth_alias_names.sh command and press Enter. The following shows the factory settings of the
Ethernet adapters of the EOMUa board.
eth0
eth1
eth2
eth3
eth4
eth5
05,0,0
05,0,1
06,0,0
06,0,1
01,0,0
01,0,1
F_ETH0
F_ETH1
F_DBG
B_UPDATE
B_ETH0
B_ETH1
NOTE
The three columns in the figure for the configuration of OMU Ethernet adapters contain the following
information:
l The first column lists the logical OMU Ethernet adapters for software identification.
l The second column lists the Peripheral Component Identity (PCI) of the Ethernet adapters for hardware
identification.
l The third column lists the physical OMU Ethernet adapters for human identification.
The mapping between the second and third columns cannot be changed. The mapping between the first and
second columns and the mapping between the first and third columns depend on the configuration of the OMU.
----End
6.2 Querying the Configuration of the OMU Ethernet

Adapters
This section describes how to query the configuration information of the OMU Ethernet adapters.
The information includes IP addresses, their subnet masks, and broadcast IP addresses.
Procedure
l
Issue 05 (2014-03-28)
Method 1
1.
2.
Type the /etc/rc.d/omud stop command and click Enter to stop the omud process.
3.
Type the cd /mbsc/bam/version_a/bin/bam command and click Enter to navigate

to the directory that contains omutool.
57
BSC6910 GSM

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

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

l Run the ifconfig bond1 command to query the fixed external IP address, its subnet mask,
and broadcast IP address. If the fixed external IP address is not configured, the virtual
external IP address, its subnet mask, and broadcast IP address are queried.
l Run the ifconfig bond1:0 command to query the virtual external IP address, its subnet
mask, and broadcast IP address. If the fixed external IP address is not configured, the query
result does not contain IP addresses.
l Run the ifconfig vlan1 command to query the fixed internal IP address, its subnet mask,
and broadcast IP address.
l Run the ifconfig vlan1:0 command to query the internal virtual IP address, its subnet mask,
l Run the ifconfig bond2 command to query the commissioning IP address, its subnet mask,
l Run the ifconfig bond3 command to query the IP address of the backup channel between
the active and standby EOMUa boards, the subnet mask of that IP address, and broadcast
IP address.
If the OMU is connected to the VNP in the live network and the local BSC IP address has been
configured, refer to Scenario of Connecting the OMU and VNP for the mapping between
Ethernet adapters and IP addresses.
----End
Issue 05 (2014-03-28)

58
BSC6910 GSM
6.3 Querying Occupied OMU Ports

This section describes how to query occupied OMU ports.
Procedure
Step 2 Enter the netstat -tuan command and press Enter to query the occupied OMU ports. The
following shows an example of the returned information.
omu_136 ~ # netstat -tuan
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address
Foreign Address
tcp
0
0 10.0.0.1:8000
0.0.0.0:*
tcp
0
0 10.0.0.1:8001
0.0.0.0:*
tcp
0
0 10.0.0.1:16002
0.0.0.0:*
tcp
0
0 10.0.0.1:16002
0.0.0.0:*
tcp
0
0 10.0.0.1:8099
0.0.0.0:*
tcp
0
0 10.0.0.1:8100
0.0.0.0:*
tcp
0
0 10.0.0.1:8006
0.0.0.0:*
tcp
0
0 10.0.0.1:8200
0.0.0.0:*
State
LISTEN
LISTEN
LISTEN
LISTEN
LISTEN
LISTEN
LISTEN
LISTEN
Information following : in the Local Address column indicates the occupied OMU port
numbers.
----End
6.4 Querying the Link Mode of the External OMU Network

Adapters
This section describes how to query the link mode of the external OMU network adapters: duplex
mode and adaptive mode.
Procedure
Step 1 7.3 Logging In to the OMU.
Step 2 Query the logical network adapters corresponding to the external OMU network adapters, as
listed in Table 6-1.
Table 6-1 Querying the logical network adapters corresponding to the external OMU network
adapters
Item
Description
EOMUa Board
Type /root/eth_alias_omu.sh and press

Enter.
Step 3 Query the effective link mode of the external OMU network adapters. Run the ethtool eth0
command to query the link mode of eth0. Run the ethtool eth1 command to query eth1.
Issue 05 (2014-03-28)

59
BSC6910 GSM
NOTE
l Check Speed, Duplex, and Auto-negotiation. Speed, Duplex, and Auto-negotiation indicate the rate,
duplex mode, and auto-negotiation mode, respectively.
l The following example assumes that the logical network adapters corresponding to the external OMU
network adapters are eth0 and eth1, respectively. The command output is as follows:
Settings for eth0:
Supported ports: [ FIBRE ]
Supported link modes:
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: external
Auto-negotiation: on
Supports Wake-on: pumbag
Wake-on: g
Current message level: 0x00000001 (1)
Link detected: yes
----End
6.5 Checking the Version of the Operating System

This section describes how to check that the version of the operating system on the OMU is
correct.
Prerequisites
You have logged in to the LMT by referring to Logging In to and Logging Out of the LMT.
Procedure
Step 1 Run the MML command LST VER to check whether OS type and OS service pack version
are correct.
----End
6.6 Changing the Administrator Password of the Operating

System
This section describes how to change the password of the operating system administrator to
ensure that the administrator account is secure.
Context
l
It is recommended that you change the root user password upon your first login and change
the password every three months.
A root user password must contain the combination of the following:

At least one lower-case letter
Issue 05 (2014-03-28)

60
BSC6910 GSM
At least one upper-case letter

At least one digit
At least one special character `~!@#$%^&*()-_=+\|[{}];:'",<.>/? or a space
The root user password must have a minimum length of 8 characters and maximum length
of 127 characters.
Procedure
Step 2 Run the passwd root command (for example, use root as an example). A message is displayed,
prompting you to enter the password, as shown in the:
Changing password for root.
New password:
Step 3 Enter a password and press Enter. The message Retype password: is displayed.
Step 4 Retype the password and press Enter. The message Password changed is displayed, indicating
that the Linux administrator password is successfully changed.
Step 5 Record the new password in the 9.1 Information Records of OMU Software Installation.
----End
6.7 Setting RAID 1 on OMU Hard Disks

This section describes how to set RAID 1 on OMU hard disks to ensure data synchronization
between the source and target OMU hard disks.
Prerequisites
l
The OMU is started properly.
The source and target hard disks are available.
Context
One OMU hard disk serves as the source hard disk, and the other serves as the target hard disk.
Setting RAID 1 on the hard disks synchronizes the data on the source and target hard disks,
improving data security.
l
The source hard disk saves backup data and files.
The target hard disk mirrors the source hard disk.
Procedure
Step 1 Connect the USB and VGA ports of the OMU to an external keyboard and monitor, respectively.
Step 2 Restart the OMU.
Issue 05 (2014-03-28)

61
BSC6910 GSM
Option
Description
Dopra Linux operating system 1. Log in to the target OMU by referring to Step 2 and Step
3 in 7.3 Logging In to the OMU.
2. Type the reboot command and press Enter to restart the
OMU.
Step 3 After the OMU restarts, press Ctrl+C when the message Press Ctrl-C to start LSI
Logic Configuration Utility is displayed. The following shows an example of
returned information:
Adapter
Eval Board
PCI
PCI
PCI
PCI
FW Revision
BUS
Dev
Fnc
Slot
0A
00
00
00
13.00.01.00-IR
status
Boot
Enabled
Step 4 Press Enter. Results are displayed, as shown in the following figure (an example).
Adapter
PCI Slot
PCI Address(Bus/Dev)
MPT Firmware Revision
SAS Address
NVDATA Version
Status
Boot Order
Boot Support
Eval Board
00
0A:00
13.00.01.00-IR
54CB16C0:00066004
0C.00
Enabled
0
[Enabled Bios & OS]
RAID Properties
SAS Topology
Advanced Adapter Properties
Press the arrow keys to select RAID Properties and press Enter. Check the value for Status to
determine whether the RAID is correct.
l If Status is Optimal, the RAID is working properly.
l If Status is Resyncing, the RAID is synchronizing data.
NOTE
l If the RAID is set for the first time on the OMU, go to Step 9.
l If the RAID is set for the second time on the OMU, go to Step 5.
Step 5 Select RAID Properties and press Enter. Results are displayed, as shown in the following figure
(an example).
Volume
1 of 1
Identifier
LSI Logical Volume
Type
RAID 1
Size(GB)
557
Status
Optimal
Task
0% Initialized
Manage Volume
Slot Device Identifier
Num
0
SEAGATE ST9600205SS
B002
1
SEAGATE ST9600205SS
B002
3000
RAID
Hot Drive
Pred
Size
Disk Spr Status
Fail
(GB)
Yes
No
Primary
NO
557
Yes
No
Secondary NO
557
Step 6 Select Manage Volume and press Enter. The following shows an example of returned
information:
Identifier
Issue 05 (2014-03-28)
LSI Logical Volume 3000

62
BSC6910 GSM
Type
RAID 1
Size(GB)
69618
Status
Optimal
Manage Hot Spare
Synchronize
Array
Activate Array
Delete
Array
Step 7 Select Delete Array and press Enter. Results are displayed, as shown in the following figure
(an example).
Y
N
Delete array and exit to Adapter Properties

Abandon array detetion and exit this menu
Step 8 Select Y. Messages are displayed, as shown in the following figure (an example).
Adapter
PCI Slot
PCI Address(Bus/Dev)
MPT Firmware Revision
SAS Address
NVDATA Version
Status
Boot Order
Boot Support
Eval Board
00
0A:00
13.00.01.00-IR
54CB16C0:00066004
0C.00
Enabled
0
[Enabled Bios & OS]
RAID Properties
SAS Topology
Advanced Adapter Properties
Step 9 Select RAID Properties and press Enter. Results are displayed, as shown in the following
figure.
Create RAID 1 Volume
volume disks will be DELETED!

10 volume
Create a RAID 1 volume

consisting of 2 disks plus up to 2
optional hot spares. ALL DATA on
Create RAID 1E/10 Volume Create a RAID 1E or RAID
consisting of 3 to disks including up

to 2 optional hot spares. ALL DATA on
volume disks will be DELETED! Create RAID 0 Volume
Create a RAID 0 volume
consisting of
2 to 10 disks. ALL DATA on
volume disks will be DELETED!
Step 10 Select Creat RAID 1 Volume and press Enter. The following shows an example of returned
information:
Type:
Volume Size(GB):
RAID 1

Num
0
SEAGATE ST9600205SS
1
SEAGATE ST9600205SS
RAID
Drive
Pred
Size
Status
Fail
(GB)
NO
557
NO
557
Disk
B002
B002
No
No
NOTICE
Select the source and target hard disks with caution. If the selection is wrong, data on the source
hard disk will be lost.
Issue 05 (2014-03-28)

63
BSC6910 GSM
Step 11 Set RAID Disk, move the cursor to the value for RAID Disk of the source hard disk, and press
+. The following shows an example of returned information:
Type:
Volume Size(GB):
RAID 1

Num
0
SEAGATE ST9600205SS
1
SEAGATE ST9600205SS
RAID
Drive
Pred
Size
Status
Fail
(GB)
Primary
NO
557
NO
557
Disk
B002
B002
Yes
No
Step 12 Press C. Results are displayed, as shown in the following figure.

Processingmay take up to 1 minute
Creating RAID Volume
Step 13 Select Save changes then exit this menu and press Enter. The screen is refreshed, as shown
in Step 8.
Step 14 Select RAID Properties shown in Step 8 and press Enter. Results are displayed, as shown in
the following figure (an example).
Volume
1 of 1
Identifier
LSI Logical Volume
Type
RAID 1
Size(GB)
557
Status
Optimal
Task
0% Initialized
Manage Volume
Num
0
SEAGATE ST9600205SS
B002
1
SEAGATE ST9600205SS
B002
3000
RAID
Hot Drive
Pred
Size
Disk Spr Status
Fail
(GB)
Yes
No
Primary
NO
557
Yes
No
Secondary NO
557
Step 15 Check that the RAID 1 is correctly set and press Esc repeatedly until messages are displayed,
as shown in the following figure:
Are you sure you want to exit?
Cancel Exit.
Save changes and reboot.
Discard changes and reboot.
Exit the Configuration Utility and Reboot.
Step 16 Select Exit the Configuration Utility and Reboot and press Enter. RAID 1 is successfully set
on the OMU hard disks and the OMU restarts.
----End
6.8 Adjusting OMU Slots

This section describes how to adjust the slots where the operation and maintenance unit (OMU)
is installed.
Prerequisites
l
Issue 05 (2014-03-28)
Before adjusting the OMU slots, collect information listed in Table 6-2.

64
BSC6910 GSM
Table 6-2 Required information
Information
Description
OMU Slots
Query and record the slots where the

OMUs are installed.
Hardware requirement
The target slots are idle. For details about the OMU slot information, see EOMUa Board.
Software requirement
None
License requirement
None
Context
Prepare the data listed in the following table.
Table 6-3 Data preparation
MO
Configuration Suggestion
Data
Source
MML
Reference
BRD
Set Slot No. to an appropriate value.
Internal
planning
ADD BRD
Procedure
Step 1 Run the DSP OMU command to query the numbers of the slots where the active and standby
OMUs reside before the adjustment.
Step 2 Log in to the active and standby OMUs separately.
Step 3 Run the /etc/rc.d/omud stop command to stop the omud process.
Step 4 Run the poweroff command to power off the OMU.
Step 5 When the OFFLINE indicator on the OMU board panel is on, pull out the active and standby
OMUs.
Step 6 Insert the active and standby OMUs into the target slots.
Step 7 Wait for about five minutes, and run the DSP OMU command to check whether the active and
standby OMUs operate properly. If not, please check whether the OMU is installed correctly.
Step 8 Run the RMV BRD command to remove the OMU boards that have been configured.
Step 9 Run the ADD BRD command to add an active and standby OMU boards separately. In this step,
set Slot No. to an appropriate value.
Step 10 Log in to the LMT to check whether the OMUs are properly displayed on the device panel.
Issue 05 (2014-03-28)

65
BSC6910 GSM
Step 11 On the main page of the LMT, click Alarm, and select Browse Alarm to view current active
alarms.
Step 12 Optional: If there is an OMU-related alarm in the list of active alarms and the OMU slot number
is the original slot number, right-click the alarm, and choose Clear Alarm to manually clear the
alarm.
----End
Example
/*Information Recording Procedure*/
//Querying the numbers of the subracks and slots where the active and standby OMUs
reside before the slot adjustment
DSP OMU:;
/*Reconfiguration Procedure*/
//Removing a board
RMV BRD: SRN=0, SN=16;
RMV BRD: SRN=0, SN=18;
//Add boards
ADD BRD: SRN=0, BRDCLASS=OMU, BRDTYPE=EOMUa, SN=24;
ADD BRD: SRN=0, BRDCLASS=OMU, BRDTYPE=EOMUa, SN=26;
Follow-up Procedure
l
Verification
Run the DSP OMU command to check whether the active and standby OMUs operate
properly.
Expected result: The active and standby OMUs operate properly.
Rollback
The rollback procedure is similar to the reconfiguration procedure, except that parameters
in the rollback procedure are set to values used before the reconfiguration.
6.9 Transferring OMU Files to a Local PC

Transferring files between a local PC and the OMU by using the FTP protocol is an important
method for saving files during operation and maintenance.
Prerequisites
l
The firewall on the portable PC is disabled.
product software are started.
Context
There are two methods for transferring files on the OMU:
l
Using the file management function on the LMT
Running commands
Application Scenarios
Issue 05 (2014-03-28)

66
BSC6910 GSM
If the OMU FTP server is set to Secure Sockets Layer (SSL) connection mode, only the
file management function on the LMT can be used to transfer files. For detailed operations,
see File Manager.
If the OMU FTP server is not set to Secure Sockets Layer (SSL) connection mode, both
the file management function on the LMT and commands can be used to transfer files.
Table 6-4 lists the commands used for downloading files.

Table 6-4 Commands commonly used on the FTP
Command
Description
Example
cd
Change the current directory.
cd /mbsc/upgrade
dir
Query the structure of the

current directory.
dir
get
Upload files from the OMU

to a local PC.
get x (x indicates the file

name)
put
Download files from a local

PC to the OMU.
put x (x indicates the file

name)
Table 6-5 lists the specifications of the FTP file transmission.

Table 6-5 Specifications of the FTP file transmission
Item
Description
Maximum number of concurrent connections

for guest users
10
Maximum number of concurrent connections

for the FtpUsr user
10
Timeout interval for control connections
15 minutes
Timeout interval for data connections
5 minutes
NOTE
The following steps use downloading the 123.xml file from the OMU to the local drive D as an example.
Procedure
l
Downloading the 123.xml file on the OMU to local drive D by using the file management
function on the LMT
1.
Issue 05 (2014-03-28)
Enable the file management function on the LMT. For details, see File Manager in
BSC6910 GSM LMT User Guide.
67
BSC6910 GSM
2.
l
Select the files to be downloaded in the corresponding directories and click

Download.
Downloading the 123.xml file on the OMU to local drive D by running commands
1.
On the local PC, choose Start > Run, enter cmd, and click OK.
2.
Type the d: command and press Enter to go to drive D.
3.
Type the ftp IP address command to connect the local PC to the OMU, where IP
address indicates the virtual external or debugging IP address of the OMU.
4.
Type the user name and password of the FTP. The connection between the local PC
and the OMU is established after the certification passes.
NOTE
The FTP user name has a fixed value FtpUsr. Its password is mbsc@com or set during the OMU
application installation. For details, see 9.1 Information Records of OMU Software
Installation.
5.
Navigate to the directory where the 123.xml file is saved by referring to commonly
used FTP commands.
6.
Transfer the 123.xml file.
7.
Command
Description
Run the get 123.xml command.
Upload the 123.xml file from the OMU

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

local drive D to the OMU.
After the file transfer is complete, run the quit command to disconnect the FTP.
----End
Example
The following is an example for downloading the 123.xml file from the local drive D to the /
mbsc/bam/version_a/bin/bam directory of the OMU:
C:\Documents and Settings>d:
D:\>ftp 10.161.21.3
Connected to 10.161.21.3.
220 ftp server ready.
User (10.161.21.3:(none)): FtpUsr
331 Password required for FtpUsr.
Password:
230 User logged in.
ftp> cd /mbsc/bam/version_a/bin/bam
250 CWD successful.
ftp> put 123.xml
200 PORT command OK.
150 Opening BINARY mode data connection for '/123.xml' (104 bytes)
226 Transfer complete.
ftp> quit
D:\>
Issue 05 (2014-03-28)

68
BSC6910 GSM
6.10 Managing the Operating Status of the OMU

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

This section describes how to query the OMU operating information, the status of OMU service
processes when the OMU is operating properly, and the OMU board information.
Prerequisites
Procedure
l
Querying the OMU operating information

1.
Run the DSP OMU command. The OMU operating information is displayed,
including the OMU operating status, fixed IP address configuration, virtual IP address
configuration, status of data synchronization, status of the internal and external
networks, and status of the backup channel.
Querying the status of OMU service processes when the OMU is operating properly
1.
Run the DSP OMUMODULE command. The names and status of the OMU service
processes are displayed.
If the status of service processes is Started, the OMU service processes are normal.
If the status of service processes is Stopped, the OMU service processes are normal
and not started.
If the status of the service processes is Exception, the OMU service processes are
abnormal. When active and standby OMUs are configured, the self-healing
switchover is triggered if the abnormal status persists. When an independent OMU
is configured, the OMU reports the ALM-20707 OMU Process Abort alarm.
Querying the OMU board information

1.
Run the DSP OMUSRV command. The OMU board status is displayed, including
the CPU usage, memory usage, number of logical CPUs, memory capacity, total space
of logical disks, current available space, percentage of the available space, and the
time cost by input/output (I/O) operation on the OMU hard disks.
----End
6.10.2 Querying the Information About an OMU Board

This section describes how to query the working environment, hardware status, and version
information about an OMU board.
Prerequisites
Issue 05 (2014-03-28)

69
BSC6910 GSM
Context
If an OMU board becomes faulty, query the information about the OMU board for fault location.
Procedure
l
Querying the OMU working environment

1.
Run the MML command DSP OMUENV. The CPU inlet temperature, memory inlet
temperature, hard disk temperature, and voltage of chips are displayed.
Querying the OMU hardware status

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

1.
Run the MML command DSP OMUVER. The subrack number, slot number, OMU
type, and version information about the PCB, BIOS, BMC, CPLD, and SDR are
displayed.
----End
6.10.3 Querying the Version of the Active/Standby OMU

Workspaces
This section describes how to query the version of the active and standby OMU workspaces,
such as the workspace flag and version of the product software.
Prerequisites
Procedure
Step 1 Run the LST OMUAREA command to query the version of the active and standby OMU
workspaces.
----End
Issue 05 (2014-03-28)

70
BSC6910 GSM
6.10.4 Querying the Status of Data Synchronization Between the

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

71
BSC6910 GSM
NOTICE
l If the active OMU data is inconsistent with the standby OMU data, run the STR
DATASYNC command to start the data synchronization between the active OMU and the
standby OMU. Wait 5 minutes then run the CMP OMUDATA command.
l If the active OMU is synchronizing the initial data with the standby OMU, the LMT displays
failure information.
Step 2 Run the CMP OMUFILE command to check the consistency of the license file, certificate file,
host patch file and other files between the active and standby OMUs.
----End
6.10.6 Changing the Time Zone and OMU Time

The OMU time stops after the battery on the OMU board is exhausted. To correct it, you will
need to replace the battery, reset the OMU time, and change the OMU time zone.
Prerequisites
l
You have obtained the time and the time zone.
Context
The OMU time and time zone are set by default before the OMU 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 zone

1.
Run the SET TZ command to change the OMU time zone.
Change the OMU time

1.
Run the SET TIME command to change the OMU date and time.
----End
6.10.7 Configuring Data Rates of Accessing the OMU Hard Disks

This section describes how to configure the data rates of accessing the OMU hard disk to prevent
a single I/O operation from consuming too many OMU hard disk resources.
Prerequisites
Context
The functions of uploading and downloading files through FTP, writing log files, writing traced
messages into files lead to many I/O operations. To prevent a single I/O operation from
Issue 05 (2014-03-28)

72
BSC6910 GSM
consuming too much OMU hard disk resources, the data rates of the previous functions must be
limited.
Procedure
l
Configuring the maximum data rate for an external FTP user

1.
Querying the maximum data rate for an external FTP user

1.
Run the SET TRCLOGSPD command to configure the maximum data rate of writing
traced messages into files.
Querying the maximum data rate of writing traced messages into files
1.
Run the DSP HOSTLOGSPD command to query the average data rate of writing log
files.
Configuring the maximum data rate of writing traced messages into files
1.
Run the LST HOSTLOGSPD command to configure the maximum data rate of
writing log files.
Querying the average data rate of writing log files

1.
Run the SET HOSTLOGSPD command to configure the maximum data rate of
writing log files.
Querying the maximum data rate of writing log files

1.
Run the DSP FTPSRVSPD command to query the average data rate of an external
FTP user.
Configuring the maximum data rate of writing log files

1.
Run the LST FTPSRVSPD command to query the maximum data rate for an external
FTP user.
Querying the average data rate of an external FTP user

1.
Run the SET FTPSRVSPD command to configure the maximum data rate for an
external FTP user.
Run the LST TRCLOGSPD command to query the maximum data rate of writing
Querying the average data rate of writing traced messages into files
1.
Run the DSP TRCLOGSPD command to query the maximum data rate of writing
----End
6.10.8 Forcibly Switching Over the Active and Standby OMUs

This section describes how to forcibly switch over the active and standby OMUs when the active
OMU needs to be manually shut down for a software/hardware upgrade or fault rectification.
By performing this task, the OMU services will not be interrupted.
Prerequisites
l
The OMU works in active/standby mode and the active and standby OMUs work normally
for more than 5 minutes (You can run the CMP OMUDATA and CMP OMUFILE
commands to query whether the active OMU data is consistent with the standby OMU data.
Issue 05 (2014-03-28)

73
BSC6910 GSM
Ensure that the data on the active OMU is synchronized to the standby OMU to avoid data
loss after the switchover.)
Procedure
Step 1 Run the DSP OMU command to query the operating status of the active/standby OMUs.
If...
Then...
The active and standby OMUs work properly and the data
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, the switchover is successful.
----End
6.10.9 Resetting the OMU

This section describes how to reset the OMU, product software, and OMU service processes.
Prerequisites
Context
l
The OMU operating system is restarted after the OMU is reset. If the OMU is reset
successfully, the faults of the OMU operating system or applications can be rectified.
All the service processes are disrupted after the product software are reset. If the OMU is
reset successfully, the faults of the product software can be rectified.
Resetting a specified OMU service process interrupts the service of the process for a while.
Reset the OMU or product software
Procedure
1.
Run the RST OMU command.

If Reset Type is set to SOFT, only the product software are reset. The OMU
operating system is not restarted.
If Reset Type is set to HARD, the OMU operating system is restarted.
Issue 05 (2014-03-28)

74
BSC6910 GSM

NOTE
l When the OMU works in single-OMU mode, set the Reset Target to ACTIVE.
l When the OMUs work in dual-OMU mode, the active OMU is reset if you set the Reset
Target to ACTIVE.
l When the OMUs work in dual-OMU mode, the standby OMU is reset if you set the Reset
Target to STANDBY.
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
6.11 Managing the Product Software

This section describes how to manage the product software.
6.11.1 Querying Operating Status of the omud

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

This section describes how to start the omud so that the OMU can provide normal services.
Procedure
Step 1 Log in to the OMU by using the external fixed IP address by referring to 7.3 Logging In to the
OMU.
Step 2 Enter the /etc/rc.d/omud start command and press Enter to start the omud.
----End
Issue 05 (2014-03-28)

75
BSC6910 GSM
6.11.3 Stop the omud

This section describes how to stop the omud process so that the OMU stops providing services.
Context
The omud process must be stopped before performing the following operations: uninstalling the
product software, upgrading product software, or restoring the BSC6910 data.
NOTICE
l When the omud process is stopped, all the OMU service processes will also stop. In turn, the
OMU stops providing services for the BSC6910. Therefore, perform this task with caution.
l If the virtual external IP address is used to log in to the OMU, stopping the omud process
will disconnects the OMU from the peripheral devices.
l If a fixed external IP address is configured for the OMU, stopping the omud will make
the virtual external IP address ineffective. In this situation, a user can log in to the OMU
by using the fixed external IP address if an independent OMU is configured. If the OMUs
work in active/standby mode, the virtual external IP address of the original standby OMU
becomes effective after the active OMU is stopped.
l If no fixed external IP address is configured for the OMU, the virtual external IP address
is still effective after you stop the omud.
Procedure
Step 1 You have logged in to the OMU through the external fixed IP address by referring to 7.3 Logging
In to the OMU.
Step 2 Type the /etc/rc.d/omud stop command and click Enter to stop the omud process.
----End
6.11.4 Uninstalling the Product Software

This section describes how to uninstall the product software.
Prerequisites
l
If product software are installed on both the active and standby OMU workspaces, uninstall
the product software on the standby workspace before uninstalling them on the active
workspace.
When the BSC6910 is configured with active and standby OMUs, uninstall the product
software on both the active and standby OMUs.
Context
Issue 05 (2014-03-28)

76
BSC6910 GSM
If there is only the active workspace on the OMU, the system will prompt you to uninstall
only the product software on the active workspace.
NOTE
l Uninstalling the product software from an OMU will cause all the data in the OMU to be lost. You are
advised to back up system data on the OMU before the uninstalling by referring to 6.12.1 Backing Up
System Data.
l If the BSC6910 is configured with the feature Radio Measurement Data Interface for Navigation and
the BSC local IP address is used to connect the OMU and the VNP, you must deactivate the feature before
the uninstalling by referring to Radio Measurement Data Interface for Navigation in GBSS Feature
Documentation.
Procedure
Step 1 Log in to the standby OMU by using the fixed external IP address or the debugging IP address.
For details, see 7.3 Logging In to the OMU.
Step 3 Enter uninstall_bam in any directory of the OMU and press Enter.
Step 4 The message Uninstall standby area. input Y to continue; input E to exit. is displayed. Enter
Y to uninstall the product software on the standby workspace of the standby OMU.
Step 5 Type the uninstall_bam command and press Enter.
Step 6 The message Uninstall main area. input Y to continue; input E to exit. is displayed. Enter
Y to uninstall the product software on the active workspace of the standby OMU.
Step 7 Type the exit command to log out of the OMU.
Option
Description
If the OMU is in dual-OMU mode,
Go to Step 8.
If the OMU is in single-OMU mode,
End this task.
Step 8 Log in to the active OMU using the fixed external IP address or debugging IP address. Then
perform Step 2 through Step 7 again.
----End
6.12 Backing Up and Restoring Data

This section describes how to use the omu_backup_linker tool to back up or restore the OMU
configuration data, alarm data, and performance data. When the OMU works in active/standby
mode, the omu_backup_linker tool can be used only on the active OMU. Otherwise, the OMU
data may be lost. For details, see 7.1 Starting the omu_backup_linker Tool.
Context
The omu_backup_linker tool is used in the following scenarios:
Issue 05 (2014-03-28)

77
BSC6910 GSM
When an EOMUa board is damaged, it needs to be replaced with a new one. The data on
the damaged EOMUa board needs to be backed up and restored on the new EOMUa board.
The OMU data needs to be backed up during routine maintenance.
The latest OMU data needs to be restored after the OMU database collapses or the OMU
upgrade fails.
6.12.1 Backing Up System Data

This section describes how to back up the BSC6910 configuration data, performance data, and
alarm data using MML commands or the omu_backup_restore_tool.
Prerequisites
l
Using MML commands:

Using the omu_backup_restore_tool:

The 7.3 Logging In to the OMU is connected.
Context
NOTICE
l When the OMU works in active/standby mode, back up the system data on the active OMU.
l Back up the OMU data manually to avoid a system data backup failure before capacity
expansion, upgrade, or software loading.
Procedure
l
Issue 05 (2014-03-28)
Using an MML command

1.
Run the BKP DB command to set Path of Backup File and Backup File Name to
back up the data in the specified directory on the OMU hard disk.
2.
Obtain the backup data file from the specified directory by referring to 6.9
Transferring OMU Files to a Local PC.
Using the omu_backup_restore_tool

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.
2.
Type the ./omu_backup_linker command and press Enter to start the

omu_backup_linker tool.
3.
Enter backup and press Enter after the Please input a valid
bkp_res_type : message is displayed.
4.
Type the save path and names of the backup files and press Enter. The system data
starts to back up the data. If the message Backup OMU database succeed! is
displayed, the system data is successfully backed up on the OMU hard disk.
78
BSC6910 GSM
5.
Obtain the backup data file from the specified directory by referring to 6.9
Transferring OMU Files to a Local PC.
----End
Example
Backing up the OMU data to /mbsc/bam using the omu_backup_restore_tool and name the file
as omu.bak
omd_test_name /mbsc/bam/common/services # ./omu_backup_linker
# The backup/restore option
# backup :Backup OMU database
# restore :Restore OMU database
# Please select one option to backup or restore OMU database, if you don't know it,
consult the administrator.
Please input a valid bkp_res_type :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 #
6.12.2 Restoring System Data

This section describes how to restore the system data using the data backup file.
Prerequisites
The system data has been backed up.
Context
Restoring the BSC6910 system data will interrupt services on theBSC6910. The data on the host
will be inconsistent with the data on the OMU after the system data is restored. As a result, the
services will be greatly impacted. Therefore, you are advised to restore the system data in the
early morning hours when traffic volume is low.
This chapter describes how to restore data by using the following methods:
l
If an MML command is used to restore data, only the BSC6910 configuration data is
restored.
If the backup restoration tool is used to restore data, all BSC6910 data is restored, including
configuration data, alarm data, performance data, operating logs, administrator account,
authority information, and product information.
NOTE
As an example, the OMU in active/standby mode is used in this document. If an OMU is in independent mode,
skip operations on the standby OMU.
Procedure
l
Issue 05 (2014-03-28)
Restoring the system data through an MML command

79
BSC6910 GSM
1.
Run the LST BKPFILE command to query data backup files saved in the OMU
active workspace installation directory\data\backup directory.
2.
Run the RTR DB command to restore configuration data on the OMU.
Restoring the system data by using the omu_backup_restore_tool

1.
Log in to the active and standby OMUs by referring to 7.3 Logging In to the
OMU.
2.
Type the /etc/rc.d/omud stop command and click Enter to stop the omud process on
the active and standby OMUs.
3.
Restore data in the original active OMU using the omu_backup_linker tool.
a.
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
b.
Log in to the OMU by referring to Type the ./omu_backup_linker command

and press Enter to start the omu_backup_linker tool.
c.
Enter restore and press Enter after the Please input a valid
bkp_res_type : message is displayed.
d.
Type the save path and name of the backup file and press Enter when the
Please input a valid backup file pathname : message is
displayed. If the restoration is successful, the Restore OMU database
succeed! message is displayed.
4.
Copy and save the backup file to be restored in the standby OMU using the psftp
software. For details, see 8.1 psftp Software.
5.
Repeat Step 3 to restore data in the original standby OMU using the
6.
Enter the /etc/rc.d/omud start command and press Enter to start the omud on the
active and standby OMUs.
7.
Log in to the LMT by referring to Logging In to and Logging Out of the LMT in
theBSC6910 GSM LMT User Guide.
8.
Run the LCK CMCTRL command to lock the data configuration right.
9.
Run the LST CFGMODE command to query whether the System Configuration
Mode parameter is set to Effective Mode for all subracks. If this parameter is set to
Ineffective Mode for any subrack, run the SET CFGDATAEFFECTIVE command
to change the value to Effective Mode.
10. Check the consistency between the BSC6910 host data and the OMU data.
NOTE
After data restoration, check whether the BSC6910 host data is consistent with the OMU data.
If not, load the restored data to the BSC6910 host.
a.
Run the ACT CRC command to check whether the host data is consistent with
the OMU data.
If the data is consistent, end this task.
If the data is inconsistent, go to 10.2.
Issue 05 (2014-03-28)
b.
Run the FMT DATA command to format the data in the OMU database so that
the data can be loaded into the host.
c.
If data inconsistency occurs in only one subrack, run the RST SUBRACK
command to reset this subrack. Before running the command, set Subrack
80
BSC6910 GSM
No.. If data inconsistency occurs in multiple subracks, run the RST BSC
command to reset the BSC.
----End
Example
Restore the OMU data by using the omu.bak file under /mbsc/bam. The following shows an
example of the results:
omd_test_name
Shutting down
omd_test_name
omd_test_name
~ # /etc/rc.d/omud stop
mbsc daemon..........
~ # cd /mbsc/bam/common/services
/mbsc/bam/common/services # ./omu_backup_linker

# backup : Backup OMU database
# restore : Restore OMU database
Please input a valid bkp_res_type : restore
# The backup file pathname.
# eg: d:/mbsc/bam/omu.bak, in windows;
# eg: /mbsc/bam/omu.bak, in linux.
Please input a valid backup file pathname : /mbsc/bam/omu.bak
Restore omu database
[100%]
Restore OMU database succeed!
omd_test_name /mbsc/bam/common/services # /etc/rc.d/omud start
Starting mbsc daemon
6.13 Setting OMU System Parameters

This section describes how to use the omutool to modify the configuration data of the active and
standby OMUs, including the OMU working mode, IP addresses and subnet masks of the internal
and external networks, and admin password. This section describes how to adjust OMU system
parameters only during the maintenance process. For the procedure for setting OMU system
parameters during initial OMU commissioning (that is, new deployment), see 4 Initially
Commissioning the OMU.
6.13.1 Setting the OMU Working Mode

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

81
BSC6910 GSM
Context
l
If the working mode of the OMU is changed from independent mode to active/standby
mode, apply the settings to both the active and standby OMUs. If the working mode is
changed from active/standby mode to independent mode, apply the settings to only the new
active OMU.
If the working mode of the OMU is changed from independent mode to active/standby
mode, ensure that the operating system, software version, and board type of the active OMU
are the same as those of the standby OMU. In addition, the slot number of the active OMU
and that of the standby OMU have an active/standby relationship.
If the working mode of the OMU is changed from active/standby mode to independent
mode, you should run the MML command DSP OMU to ensure that the Data-sync state
is Data synchronization is successful and run the MML command CMP
OMUFILE to ensure that Compare result is consistent.
The following procedure assumes that version_a is the OMU active workspace. Run the
LST OMUAREA command to query the OMU active workspace.
Switching the OMU from the independent mode to the active/standby mode (product
software are not installed on the OMU to be added).
Procedure
1.
Insert an EOMUa board into the standby slot by referring to Installing the EOMUa
Board in the BSC6910 GSM Installation Guide
2.
Connect the PC to the commissioning Ethernet port of the OMU, and log in to the
standby OMU by using the commissioning IP address. For details, see 7.3 Logging
In to the OMU.
3.
Install product software on the standby OMU. For details, see 5.3.2 Uploading the
OMU Application Installation Package to the OMU and 5.3.3 Installing the
Product Software in the Active Workspace.
NOTE
You must select active/standby mode during the process of installing the product software for the
standby OMU.
Issue 05 (2014-03-28)
4.
Change the IP addresses and subnet masks of the standby OMU to ensure that the
fixed internal IP addresses, fixed external IP addresses, and IP address of the backup
channel between active and standby of OMUs comply with the planning principle for
the IP addresses and do not conflict with each other. For details about changing IP
addresses, see 6.13.2 Changing IP Addresses and Subnet Masks of OMU Ethernet
Adapters.
5.
the original active OMU.
6.

to the directory that contains omutool on the original active OMU.
7.
Run the ./omutool dualmode dual command on the original active OMU to set the
working mode of the OMU to active/standby mode.
8.
original active OMU.
9.
Five minutes after the original active OMU has been started, start the omud on the
standby OMU.
82
BSC6910 GSM
CAUTION
You should start the standby OMU 5 minutes after the active OMU is started to keep
the two OMUs from competing for the active state. This helps avoid data loss.
10. Change the operating system password on the standby OMU to that of the original
active OMU by referring to 6.6 Changing the Administrator Password of the
Operating System.
11. Run the ADD BRD command on the LMT to add an OMU.
12. Run the MML command DSP OMU on the LMT and check whether the value for
Data-sync state is Data synchronization is successful.
13. Connect an Ethernet cable to the Ethernet port on the added OMU.
l
Switching the OMU from the independent mode to the active/standby mode. (product
software are installed on the OMU to be added.)
1.
Connect the PC to the commissioning Ethernet port of the OMU and log in to the
original active OMU by using the commissioning IP address. For details, see 7.3
Logging In to the OMU.
2.
the original active OMU.
3.

to the directory that contains omutool on the original active OMU.
4.
Run the ./omutool dualmode dual command on the original active OMU to set the
working mode of the OMU to active/standby mode.
5.
original active OMU.
6.
Insert an EOMUa board in the standby slot 5 minutes after the original active OMU
starts.
CAUTION
Start the standby OMU 5 minutes after the active OMU is started to avoid the two
OMUs from competing for active state, which will avoid data loss.
Issue 05 (2014-03-28)
7.
Set the working mode of the standby OMU to active/standby mode by repeating Step
1 through Step 4.
8.
Change the IP addresses and subnet masks of the standby OMU to ensure that the
fixed internal IP addresses, fixed external IP addresses, and IP address of the backup
channel between active and standby of OMUs comply with the planning principle for
the IP addresses and do not conflict with each other. For details about changing IP
addresses, see 6.13.2 Changing IP Addresses and Subnet Masks of OMU Ethernet
Adapters.
9.
standby OMU.
83
BSC6910 GSM
10. Change the operating system password on the standby OMU to that of the original
active OMU by referring to 6.6 Changing the Administrator Password of the
Operating System.
11. Run the ADD BRD command on the LMT to add an OMU.
12. Run the MML command DSP OMU on the LMT and check whether the value for
Data-sync state is Data synchronization is successful.
If...
Then...
Data-sync state is Data

synchronization not built due to
version inconsistency
Reinstall product software on the

standby OMU by performing the
following steps:
1. Uninstall product software from the
standby OMU by referring to steps in
6.11.4 Uninstalling the Product
Software.
2. Install product software of the
correct version on the standby OMU.
For details, see 5.3.2 Uploading the
OMU Application Installation
Package to the OMU and 5.3.3
Installing the Product Software in
the Active Workspace.
3. Perform Step 12.
Data-sync state is Data

synchronization is successful
Go to Step 13.
13. Connect an Ethernet cable to the Ethernet port on the added OMU.
l
Change the working mode of the OMU from active/standby mode to independent mode.
1.
Run the RMV BRD command on the LMT to remove an OMU.
2.
Log in to the active and standby OMUs by using the fixed external IP address by
referring to 7.3 Logging In to the OMU.
3.
the active and standby OMUs.
4.
Run the poweroff command on the OMU to be removed to power off the OMU.
5.
Remove the OMU.
6.

to the directory that contains omutool on the active OMU.
7.
Run the ./omutool dualmode single command on the active OMU to set the working
mode of the OMU to independent mode.
8.
active OMU.
----End
Issue 05 (2014-03-28)

84
BSC6910 GSM
6.13.2 Changing IP Addresses and Subnet Masks of OMU Ethernet

Adapters
This section describes how to change IP addresses and subnet masks of the OMU Ethernet
adapters using omutool.
Prerequisites
The product software have been started.
For the default values of OMU system parameters, see 9.2 Checklist for the OMU Software
Factory Settings.
For the IP address introduction and planning principles, see 3.2 OMU IP Address Plan.
Context
l
This task describes how to change all the IP addresses and subnet masks for the OMU. You
can perform these steps based on the onsite IP address plan.
NOTE
l Single-OMU mode: Stop the omud before the change and start the omud after the change.
l Dual-OMU mode: Stop the standby omud and then the active omud before the change. Start the active omud
and then the standby omud after the change.
Procedure
Step 2 Type the /etc/rc.d/omud stop command and click Enter to stop the omud process
directory that contains omutool
Step 4 The command for querying the OMU IP address and subnet mask is ./omutool dispipinfo.
./omutool dispipinfo
Step 5 The ./omutool innercard IP address command is used to change the fixed internal IP address.
./omutool innercard 80.168.3.60
Step 6 The ./omutool innervip IP address command is used to change the virtual internal IP address.
./omutool innervip 80.168.3.40
Issue 05 (2014-03-28)

85
BSC6910 GSM
NOTE
l The network segments of the fixed and virtual internal IP addresses must be the same. If the network segment
of the fixed internal IP address is changed to be different from that of the virtual internal IP address, you are
prompted to change the virtual internal IP address. If the network segment of the virtual internal IP address
is changed to be different from that of the fixed internal IP address, you are prompted to change the fixed
internal IP address.
l When you change the fixed and virtual internal IP addresses, the corresponding subnet masks are created
automatically.
l If you are changing the fixed and virtual internal IP addresses for the first time, perform the following
additional steps:
1. Run the SET SUBNET command and set the BSC6910 subnet number to be consistent with the network
segment on which the fixed internal IP address and virtual internal IP address are located.
2. Remove the SCUb board from the MPS and reinstall it in the MPS. Then, reset the MPS to validate the
new fixed and virtual internal IP addresses.
After the preceding steps are performed, the OMU can communicate with the BSC6910 host normally.
Step 7 The ./omutool extercard IP address mask (gateway) command is used to change the fixed
external IP address and subnet mask.
./omutool extercard 10.161.10.100 255.255.255.0
NOTICE
Before changing the fixed external IP address, virtual external IP address, and external gateway
IP address, log in to the OMU using the debugging IP address at the local end. Otherwise, remote
login in to the OMU to change the IP addresses may disconnect the OMU from its peer.
Step 8 The ./omutool extervip IP address subnet mask (gateway) command is used to change the virtual
external IP address and subnet mask.
./omutool extervip 10.161.10.102 255.255.255.0
NOTE
l After the virtual external IP address and subnet mask are changed, start the omud, run the RMV EMSIP
command and then run the ADD EMSIP command to update the virtual external IP address and subnet
mask that are recorded in the OMU database.
l The network segments of the fixed and virtual external IP addresses must be the same. If the network segment
of the fixed external IP address is changed to be different from that of the virtual external IP address, you
are prompted to change the virtual external IP address. If the network segment of the virtual external IP
address is changed to be different from that of the fixed external IP address, you are prompted to change the
l After the fixed external IP address, virtual external IP address, and gateway IP address are changed,
communication between the OMU and peripheral equipment is interrupted. You need to use the new fixed
or virtual external IP address to reconnect the OMU and peripheral equipment.
Step 9 The ./omutool gateway gateway IP address command is used to change the gateway IP address.
./omutool gateway 10.161.10.1
Issue 05 (2014-03-28)

86
BSC6910 GSM
NOTE
You can change the fixed or virtual external IP address simultaneously with changing the gateway IP address.
The following are the related commands:
l ./omutool extercard IP address Subnet mask Gateway IP address for changing the fixed external IP address
and gateway IP address simultaneously
l ./omutool extervip IP address Subnet mask Gateway IP address for changing the virtual external IP address
and gateway IP address simultaneously
Step 10 Change the backup channel IP address and subnet mask of the active and standby OMUs by
using the commands listed in the following table.
Option
Description
Backup channel IP address of the active

and standby OMUs on the Ethernet
adapter B_UPDATE of the OMU board
./omutool backupcard IP address.

For example, you can type the following
command and then press Enter.
Step 11 The ./omutool debugcard IP address command is used to change the debugging IP address.
./omutool debugcard 192.168.6.60
NOTE
l After you change the backup channel IP address and debugging IP address of the active and standby
OMUs, the corresponding subnet mask will be created automatically.
l To change the OMU IP addresses, you must follow the principles of IP address planning. For details,
see 3.2 OMU IP Address Plan. When entering the command, ensure that there is a space between the
IP address and the subnet mask.
l Record the new IP addresses in 9.1 Information Records of OMU Software Installation.
Step 12 The ./omutool delextercard command is used to delete the fixed external IP address.
./omutool delextercard
NOTE
l If the virtual and fixed external IP addresses have been configured and the fixed external IP address is planned
for deletion, use this command to delete the configured fixed external IP address.
l If ALM-20702 Active and Standby OMU Communication Link Failure is reported before you delete the
fixed external IP address and the alarm is caused by the external network, delete the alarm after you delete
the fixed external IP address.
Step 13 For how to configure the BSC local IP address, see "Radio Measurement Data Interface for
Navigation" in GBSS Feature Documentation.
NOTE
The BSC local IP address is used for communication between the OMU and VNP. For details, see Scenario of
Connecting the OMU and VNP.
Step 14 Enter the /etc/rc.d/omud start command and press Enter to start the omud
----End
Issue 05 (2014-03-28)

87
BSC6910 GSM
6.13.3 Changing Users' Passwords

This section describes how to change the passwords for users admin, root, and db_user by using
the omutool, how to change the password for user FtpUsr by using the MML command, and
how to log in to the M2000 to change its FTP user's password.
Context
l
admin is the account for logging in to the LMT.
db_user and root are the accounts for accessing the OMU database.
FtpUsr is the account for uploading and downloading files to and from the OMU.
The M2000's FTP user is used for the M2000 to access BSC6910 for file loading and
downloading.
If active and standby OMUs are configured on the BSC6910, you must change the
passwords of the admin, db_user, and root user on both the active and standby OMUs.
NOTE
l Single-OMU mode: Stop the omud before the change and start the omud after the change.
l Dual-OMU mode: Stop the standby omud and then the active omud before the change. Start the
active omud and then the standby omud after the change.
NOTE
l It is recommended that you change the password at your first login and then change the password
every three months.
l Users root and db_usr must both contain the combination of the following:
l At least one lower-case letter
l At least one upper-case letter
l At least one digit
l At least one special character -?[]_+{}
The user password must have a minimum length of 8 characters and maximum length of 32
characters.
l User admin and FtpUsr must both contain the combination of the following:
l At least one special character ~!@#$%^&*()_+-{}|[]:<>?./
The user password must have a minimum length of 8 characters and maximum length of 32
characters.
DANGER
Keep the password safe. You need to reinstall the OMU operating system if the password
is lost.
Issue 05 (2014-03-28)

88
BSC6910 GSM
Procedure
l
Changing the admin password

1.
2.
3.

4.
Run the ./omutool adminpwd command to change the admin password.
5.
Enter the /etc/rc.d/omud start command and press Enter to start the omud.
Changing the root password

1.
2.
3.

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

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

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

1.
Log in to the LMT by referring to Logging In to and Logging Out of the LMT in the
2.
Run the MML command MOD FTPPWD to change the password of the FtpUsr user.
Changing the password of the M2000's FTP user

1.
Log in to the M2000.
2.
Change the password of the M2000's FTP user. For details, see Setting an NE as a
Transfer Server in the M2000 version documentation.
----End
Example
The following shows an example for changing the admin password:
Dopra_136 /mbsc/bam/version_a/bin/bam # ./omutool adminpwd
Enter a password or press Ctrl+C to quit:
Re-enter password or press Ctrl+C to quit:
Successfully set the admin user's password!
The following shows an example for changing the root password:

Dopra_136 /mbsc/bam/version_a/bin/bam # ./omutool dbrootpwd
Issue 05 (2014-03-28)

89
BSC6910 GSM

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

This section describes how to change the computer name through omutool.
Context
l
If the BSC6910 is configured with active and standby OMUs, name them differently.
Procedure
directory that contains omutool.
Step 4 Run the ./omutool hostname Computer name command to change the computer name.
For example, to change the computer name to omu_123, type the ./omutool hostname
omu_123 command and press Enter.
Step 5 Enter the /etc/rc.d/omud start command and press Enter to start the omud.
----End
Follow-up Procedure
1.
Log in to the LMT by referring to Logging In to and Logging Out of the LMT in the
2.
Run the DSP OMU command to query the new computer name.
Issue 05 (2014-03-28)

90
BSC6910 GSM
Appendix: OMU-Related Operations
About This Chapter

This section describes basic OMU-related operations, including logging into the OMU, logging
out of the OMU, and starting OMU tools.
7.1 Starting the omu_backup_linker Tool
This section describes how to start the omu_backup_linker tool.
This section describes how to start the omutool on the OMU to set OMU system parameters.
7.3 Logging In to the OMU
You can run the Secure Shell (SSH) terminal, for example, the PuTTY software, to log in to the
OMU and perform operation and maintenance (OM) on the OMU.
7.4 Logging Out of the OMU
This section describes how to log out of the OMU after you have finished operating and
maintaining the OMU by using PuTTY.
Issue 05 (2014-03-28)

91
BSC6910 GSM
7.1 Starting the omu_backup_linker Tool

This section describes how to start the omu_backup_linker tool.
Context
l
If an independent OMU is configured, log in to the OMU to start the omu_backup_linker

tool.
If active and standby OMUs are configured, log in to the active OMU to start the
Procedure
Step 1 Log in to the target OMU by referring to the procedure in 7.3 Logging In to the OMU.
Step 2 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 3 Type the ./omu_backup_linker command and press Enter to start the omu_backup_linker
tool. The following information is displayed:
# backup :Backup OMU database
# restore :Restore OMU database
Please input a valid bkp_res_type :
----End

This section describes how to start the omutool on the OMU to set OMU system parameters.
Prerequisites
Context
l
The omutool can be used by only one type of users in the following operating systems:
Only the administrator user is allowed to use the omutool in the Windows operating system.
The created users with the same user rights as the administrator user cannot use this tool.
Only the root user is allowed to use the omutool in the Linux operating system.
When the BSC6900 is configured with active and standby OMUs and system parameters
need to be set on two OMUs, log in to the active and standby OMUs and start the omutool
on two OMUs, respectively.
Issue 05 (2014-03-28)

92
BSC6910 GSM
Procedure
directory that contains omutool.
Step 3 Type the ./omutool -h command and press Enter. The parameter information on the omutool
is displayed.
----End
7.3 Logging In to the OMU

You can run the Secure Shell (SSH) terminal, for example, the PuTTY software, to log in to the
OMU and perform operation and maintenance (OM) on the OMU.
Prerequisites
The PC to be used to log in to the OMU is properly connected.
Procedure
Step 1 Run the SSH terminal, for example, PuTTY, on the PC, and then enter the IP address of the
OMU.
NOTE
l Before starting product software, enter the fixed external IP address of the OMU.
l After the product software start, enter the fixed or virtual external IP address. The former is preferred.
l If you are performing local commissioning, enter the debugging IP address of the OMU.
l If the PC cannot be connected to the OMU by using either the fixed or virtual external IP address,
connect the PC to the debugging Ethernet port on the OMU and enter the debugging IP address of the
OMU.
l You are advised to log in to the OMU using the external fixed IP address, external virtual IP
address, and debugging IP address in a preference sequence.
Step 2 Log in to the OMU as the lgnusr user, common user, or root user.
NOTE
l If the login fails, check whether the Disabling user root remote login function is enabled. If the function
is enabled, log in to the OMU as a common user.
For details about the Disabling user root remote login function, see 11.1 Disabling root user login with
SSH.
l Run the LST VER command to query the OMU operating system version and log in to the OMU by using
the corresponding password. For details, see 9.2 Checklist for the OMU Software Factory Settings.
l It is recommended that you change the root user password upon your first login and change the password
every three months.
l If you enter the password incorrectly for three times when logging in to the OMU, the operating system will
be automatically locked for 5 minutes and then unlocked. When the operating system is locked, do not log
in to the OMU.
Issue 05 (2014-03-28)

93
BSC6910 GSM
Step 3 For a common user or lgnusr user, enter su and press Enter. Then, enter the root user password
to switch to a root user account.
----End
Example
The following shows an example of logging in to the OMU as the root user.
login as: root
You are trying to access a restricted zone. Only Authorized Users allowed.
Using keyboard-interactive authentication.
Password:
Last login: Fri Jul 13 12:14:11 2012 from 10.142.36.219
Hello! Welcome to RTOS!
omud215 ~ #
The following shows an example of logging in to the OMU as the lgnusr user. The same is for
a common user.
login as: lgnusr
Password:
Hello! Welcome to RTOS!
omu / $ su
Password:
omu /home/lgnusr #
7.4 Logging Out of the OMU

This section describes how to log out of the OMU after you have finished operating and
maintaining the OMU by using PuTTY.
Prerequisites
The 7.3 Logging In to the OMU is connected.
Procedure
Step 1 Type the exit command and press Enter to close PuTTY.
----End
Issue 05 (2014-03-28)

94
BSC6910 GSM
Appendix: OMU-Related Software
About This Chapter

This section describes how to obtain and use the OMU-related software, including the psftp
software and PuTTY software. The OMU-related software is used to install the product software
and perform operation and maintenance on the OMU.
8.1 psftp Software
This section describes how to obtain and use the psftp software to upload the OMU application
installation package to the OMU.
8.2 PuTTY Software
This section describes how to obtain and use the PuTTY software to log in to the OMU.
8.3 Dopra_Linux_USB Disk Tool
This section describes how to use the Dopra_Linux_USB disk tool to prepare the USB storage
device for quickly installing, restoring, or switching the OMU operating system (OS).
Issue 05 (2014-03-28)

95
BSC6910 GSM
8.1 psftp Software

This section describes how to obtain and use the psftp software to upload the OMU application
installation package to the OMU.
Context
l
The psftp software is used to upload files to the OMU hard disk. The product software can
be used only after the psftp software is installed.
The psftp software is also used to download files from the OMU hard disk to a local PC.
Table 8-1 lists the commands commonly used on the psftp software.
Table 8-1 Commands commonly used on the psftp software
Command
Description
Example
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:\V100R015C00\Software\setup
\linux
get
Transfer files from the

OMU to the local PC.
To transfer a file, run the get

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

PC 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 Contact Huawei engineers who can obtain the psftp software by performing the following
operation: Log in to http://support.huawei.com/support/. Choose Software Center >
Controlled Tool(Mini-tool Software) > Wireless Product Line > Wireless Performance &
RNP & RNO > iManager Nastar > Nastar Tools to download the psftp software.
Step 2 Double-click psftp.exe. A window is displayed, as shown in Figure 8-1.
Issue 05 (2014-03-28)

96
BSC6910 GSM
Figure 8-1 Logging in to the OMU using the psftp software
Step 3 Type the open IP address command and press Enter.

Step 4 Log in to the OMU as the root user, lgnusr user, or common user. The displayed interface is as
follows:
psftp: no hostname specified; use "open host.name" to connect
psftp> open 10.161.21.203
login as: root
Password:
----End
8.2 PuTTY Software

This section describes how to obtain and use the PuTTY software to log in to the OMU.
Context
PuTTY is an SSH client program that supports SSH and can be used for remotely logging in to
the Dopra Linux operating system.
NOTE
Other client programs that support SSH can also be used.
Issue 05 (2014-03-28)

97
BSC6910 GSM
Procedure
Step 1 Contact Huawei engineers who can obtain the PuTTY software by performing the following
operation: Log in to http://support.huawei.com/support/. Choose Software Center >
Controlled Tool(Mini-tool Software) > Wireless Product Line > Wireless Performance &
RNP & RNO > iManager Nastar > Nastar Tools to download the PuTTY software.
Step 2 Double-click putty.exe. The PuTTY Configuration dialog box is displayed, as shown in
Figure 8-2.
Figure 8-2 PuTTY Configuration dialog box
Step 3 In the Specify your connection by host name or IP address area, specify the Host Name (or
IP address) by entering the IP address of the OMU board, and set Protocol to SSH.
The IP address is determined based on the following rules:
Issue 05 (2014-03-28)
If...
Then...
The PC is connected to ETH2 on the OMU

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

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

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

or virtual external IP address of the OMU.

98
BSC6910 GSM
Step 4 Click Open. The window shown in Figure 8-3 is displayed.

Figure 8-3 Logging in to the OMU board through PuTTY software
Step 5 Log in to the OMU as the root user, lgnusr user, or common user.
----End
8.3 Dopra_Linux_USB Disk Tool

This section describes how to use the Dopra_Linux_USB disk tool to prepare the USB storage
device for quickly installing, restoring, or switching the OMU operating system (OS).
Prerequisites
l
The capacity of the USB storage device is at least 2 GB. If the BSC6910 is configured with
active and standby OMUs, two USB storage devices are required.
The USB storage device is inserted in a functional USB port on the portable PC.
The portable PC has read and write rights on the USB port.
You have obtained the following OMU information: the OMU name, fixed external IP
address, subnet mask of the fixed external IP address, subnet gateway of the fixed external
IP address, IP address of the backup channel between the active and standby OMUs,
debugging IP address, and subnet mask of the debugging IP address.
Contact Huawei engineers who can obtain the tool by performing the following operation:
Issue 05 (2014-03-28)

99
BSC6910 GSM
Log in to http://support.huawei.com/support/ and choose Software Center > Version

Software > Wireless Product Line > SingleRAN > SRAN O&M tools to obtain the
Dopra_Linux_U tool.
Context
NOTICE
This function is for quickly restoring data and rectifying faults. During the process, data is
encrypted against the risk of information leakage.
The USB storage device can be used to install the OMU operating system or install both the
OMU operating system and the product software. The installation made depends on whether the
OMU version installation package or patch installation package has been installed when the
USB storage device is prepared.
The USB storage device is used in the following scenarios:
l
Initially installing the OMU operating system and applications
Restoring the corrupted OMU operating system
Switching the OMU OS to Dopra Linux
When the USB storage device is used to perform operations on the OMU, the OMU data is
affected as follows:
l
If the working mode of the USB storage device is Install, the hard disk drive is formatted
and the OMU data is erased. Therefore, back up the OMU data before installing the OMU
operating system by using the USB storage device.
After the OMU operating system is installed, user security settings (including user
passwords and security policies) are restored to the factory settings.
For details about the password for the root user, see section Checklist for the OMU
Board Software Factory Settings.
For details about security policies for the root user password, see section Dopra Linux
OS Security in the Dopra_Linux_USB Disks software package.
If the working mode of the USB storage device is Recover, the OMU operating system is
restored and the product software and data are retained.
NOTE
The modified and deleted system files cannot be restored using the USB storage device. The USB storage
device applies only to the following scenarios:
1. The OMU operating system cannot start.
2. When the OMU operating system starts, a message is displayed that prompts you to restore the file
system.
3. After the OMU operating system starts, a Kernel panic error is displayed that indicates a failure in
loading rootfs.
If the OMU operating system cannot be restored using the USB storage device, you are advised to reinstall
the OMU operating system using the USB storage device.
Issue 05 (2014-03-28)
If the operation type of the USB storage device is Switch, the OMU OS is to be switched
to Dopra Linux with all the product software and data retained.
100
BSC6910 GSM
After the OMU operating system is switched by using the USB flash drive, all the OMU
data is smoothly moved to the new operating system, including the OMU database that
stores the configuration, alarm, and platform data; performance configuration files; SSL
certificate files; license files and the SingleRAN base station data upgrade files
generated when a non-SingleRAN base station is upgraded to a SingleRAN base
station. All the product software are retained. The performance result files and log files
need to be backed up to a local PC before the OMU operating system is switched. For
details about the directory where these files are to be backed up, see Table 1 in 5.3.4
Checking the Installation Directory of Product Software. You can use a file manager
to back up the files. For details about the file manager, see File Manager.
The OMU is reset when the operating system is switched. In active/standby mode, the
OMU reset interrupts Operation and Maintenance (O&M) for about 5 minutes. In
independent mode, the OMU reset interrupts O&M for about 20 minutes. The OMU
reset does not affect ongoing services.
The communication between the M2000 and BSC6910 is interrupted when the OMU
is reset. The periodical performance counters that are to be reported to the M2000 when
the OMU is being restarted are lost. You are advised to finish preparing a USB flash
drive for this operation before 24:00. If the OMU is in active/standby mode, insert the
prepared USB flash drive to the standby OMU and restart the standby OMU. Then
switch over the active and standby OMUs between 24:00 and 01:00 when performance
counters are not being reported to the M2000. This prevents the loss of performance
counters. If the OMU is in independent mode, insert the prepared USB storage device
and restart the OMU between 24:00 and 01:00 for the same purpose.
NOTICE
l The BSC software version cannot be rolled back after the OMU operating system is
switched by using the USB flash drive.
l After the USB flash drive is prepared, do not modify the OMU data before switching
the OMU operating system. Otherwise, the OMU data will be inconsistent with the
host data.
l To ensure data synchronization between the two hard disks of the OMU, the
Redundant Array of Independent Disks (RAID) between them must be normal. If
the RAID is abnormal, do not switch the OMU operating system. To query whether
the RAID is normal, run the DSP OMUHW command.
Before preparing a USB storage device, verify the device by referring to DOPRA Linux USB
Disk Certificate Guide in the directory where the Dopra Linux USB storage device is saved. If
the USB storage device is not usable, replace it. The Netac U208 (2 GB), Kingston and Sandisk
USB storage devices are recommended.
The duration for preparing a USB storage device varies based the bandwidth of the network
from the PC to the equipment room, the USB protocol, and the PC performance. The duration
listed in Table 1 refers to the duration for preparing a USB storage device in compliance with
the USB2.0 protocol. The duration for preparing a USB storage device in compliance with the
USB1.1 protocol takes about twice as long as preparing a USB storage device in compliance
with the USB2.0 protocol. If the duration for preparing the device requires much longer than the
listed duration, the performance of the PC in use is poor. If this occurs, restart the PC or use a
PC with a higher level of performance.
Issue 05 (2014-03-28)

101
BSC6910 GSM
Table 8-2 Operation and duration

Operation
Duration
Prepare a USB storage device.
The duration varies based on the bandwidth

of the network from the PC to the equipment
room.
l If the network bandwidth is 1 Mbit/s or
higher:
When an independent OMU is
configured, the duration is 15 to 30
minutes.
When active and standby OMUs are
minutes.
l If the network bandwidth is 512 kbit/s:
When an independent OMU is
minutes.
When active and standby OMUs are
minutes.
Install, restore, or switch the OMU operating

system using a USB storage device.
20 to 40 minutes
Procedure
l
Preparing the USB storage device for initially installing the OMU operating system and
applications
1.
Issue 05 (2014-03-28)
Double-click U_creator_eng.exe to begin installing a Dopra Linux operating system

on the USB storage device, as shown in Figure 8-4.

102
BSC6910 GSM
Figure 8-4 U_creator_eng window
2.
Issue 05 (2014-03-28)
Right-click NE List in the left pane of the window shown in Figure 8-4 and choose
Add NE from the shortcut menu. A dialog box is displayed, as shown in Figure
8-5.

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

104
BSC6910 GSM
Figure 8-6 Configuring information
NOTE
l The IP addresses shown in Figure 8-6 are default IP addresses of the Dopra Linux tool. Change
the IP addresses as required. For details about the principles of changing the IP addresses, see
l Select the link mode for external Ethernet adapters listed in Figure 8-6 as required. Ensure that
the link mode for external Ethernet adapters is consistent with that for the onsite LAN switch.
Table 8-3 lists the mapping between the queried link mode for external Ethernet adapters and
that selected in Figure 8-6.
l If Install OMU is not selected in Step 3, only the names of the active and standby OMUs and
IP addresses are displayed in Figure 8-6.
l In independent OMU mode, only the active OMU configuration is effective, whereas the standby
OMU configuration is ineffective.
l The new password policy is as follows:
l Passwords of admin and ftp must contain 8 to 32 characters.
l The characters must be uppercase letters, lowercase letters, digits, or special characters, or
the combination of two among these types.
l Special characters include spaces and the following characters: ~!@#$%^&*()_+-{}|
[]:<>?./
Table 8-3 Mapping between link modes of external Ethernet adapters
Issue 05 (2014-03-28)
Queried Link Mode of External

Ethernet Adapter
Link Mode of External Ethernet

Adapter to Be Selected
l Auto-negotiation is on.
Auto

105
BSC6910 GSM

Ethernet Adapter

l Auto-negotiation is off.
10Mb Full
l Speed is 10Mb/s.
l Duplex is Full.
10Mb Half
l Speed is 10Mb/s.
l Duplex is Half.
100Mb Full
l Speed is 100Mb/s.
l Duplex is Full.
100Mb Half
l Speed is 100Mb/s.
l Duplex is Half.
l Auto-negotiation is off
1000Mb Full
l Speed is 1000 Mbit/s

l Duplex is Full
1000Mb Half

l Duplex is Half
5.
After all the information is automatically obtained, check whether the information is
correct and enter any missing information.
NOTE
l If a version or baseline patch is to be installed, select the V**R**C** directory of the version
installation package or the V**R**C**SPCX00 directory for the baseline patch installation
package.
l If a non-baseline patch is to be installed, select the V**R**C**SPCXYZ or
V**R**C**SPHXYZ directory for the patch installation package.
6.
Check that all the information is correct and click OK. In the displayed dialog box,
check the directory where the USB storage device is located and start preparing a USB
storage device.
7.
Perform operations by following the instructions until the system displays a message
that reads Succeed to create USB drive of OMU installation. Click Finish to finish
preparing the USB storage device.
NOTE
l If the system asks for your confirmation during preparation of the USB storage device, insert or
remove the USB storage device.
l If an independent OMU is configured, skip the steps for preparing the standby OMU USB storage
device.
Issue 05 (2014-03-28)

106
BSC6910 GSM
Preparing the USB storage device for restoring the OMU operating system
1.

on the USB storage device, as shown in Figure 1.
2.
Right-click NE List in the left pane of the window shown in Figure 1 and choose Add
NE. A dialog box is displayed, as shown in Figure 8-7.
3.
Specify NE Name, and set Operate type to Restore. Then click OK. An NE is added.
NOTE
l The NE name, used to identify an NE, can include only letters, numerals, dashes ("-"), and
underscores ("_").
l An NE name can be changed only after you delete the NE and then add it again.
l To prepare multiple USB storage devices, you are advised to prepare and label the USB storage
devices one by one.
4.
Issue 05 (2014-03-28)
Double-click the added NE in the left pane. The window is refreshed, as shown in
Figure 8-8.

107
BSC6910 GSM
Figure 8-8 Configuration information
NOTE
l The IP addresses shown in Figure 8-8 are default IP addresses of the Dopra Linux tool. Change
the IP addresses as required. For details about the principles of changing the IP addresses, see
l Select the link mode for external Ethernet adapters listed in Figure 8-8 as required. Ensure that
the link mode for external Ethernet adapters is consistent with that for the onsite LAN switch.
l In independent OMU mode, only the active OMU configuration is effective, whereas the standby
OMU configuration is ineffective.
5.
After all the information is automatically obtained, check whether the information is
correct and enter the required information.
6.
Check that all the information is correct and click OK. In the displayed dialog box,
check the directory where the USB storage device is located and start preparing a USB
storage device.
7.
Perform operations by following the instructions until the system displays a message
that reads Succeed to create USB drive of OMU installation. Click Finish to finish
preparing the USB storage device.
NOTE
l If the system asks for your confirmation during preparation of the USB storage device, insert or
remove the USB storage device.
l If an independent OMU is configured, skip the steps for preparing the standby OMU USB storage
device.
Prepare the USB flash drive for switching the OMU operating system.
1.
Issue 05 (2014-03-28)

on the USB storage device, as shown in Figure 8-9.

108
BSC6910 GSM
Figure 8-9 U_creator_eng window
2.
Issue 05 (2014-03-28)
Select NE List in the left pane of the window, right-click the NE list, and choose Add
NE from the shortcut menu. The dialog box shown in Figure 8-10 is displayed.

109
BSC6910 GSM
3.
Issue 05 (2014-03-28)
Type the NE Name, select Switch from the Operate type drop-down list box, specify
the Virtual External IP and Password of Admin parameters, and click OK. An NE
is added.

110
BSC6910 GSM

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

111
BSC6910 GSM

If the OMU whose operating system is to be switched does not use its own pre-set certificates,
apply for the corresponding certificate file or private key file from Certificate Authority
(CA). If the OMU uses its own pre-set certificates, you do not need to download the
certificate file or private key file. Table 8-4 lists formats of certificates supported by NEs.
Table 8-4 Formats of certificates supported by NEs
4.
Certificate Type
Format
File Extensions
Certificate
PEM, DER
*.cer, *.crt, *.pem, *.der
Private key
PEM, DER
*.cer, *.crt, *.pem, *.der
Double-click the added NE in the left pane of the window. The window is updated,
as shown in Figure 8-11.
5.
Issue 05 (2014-03-28)
After all the information is obtained automatically, check the result and select the
directory for the version package. If there is a patch, also select the directory for the
patch. Then click OK to start the preparation of the USB flash drive.

112
BSC6910 GSM

NOTE
l To install the software version, select the V**R**C** directory in the version installation
package. To install the baseline software patch, select V**R**C**SPCX00 directory in
the baseline patch installation package.
l To install a non-baseline software patch, select the V**R**C**SPCXYZ or
V**R**C**SPHXYZ directory in the patch installation package.
l If the link mode of OMU external Ethernet adapters fails to be obtained, query and set it
by referring to 4.1 Setting the Link Mode for External OMU Ethernet Adapters. Table
3 lists the mapping between the queried link mode of OMU external Ethernet adapters and
the mode of OMU external Ethernet adapters selected in Figure 8-11.
Table 8-5 Mapping between link modes of external Ethernet adapters

Ethernet Adapter

l Auto-negotiation is on.
Auto
10Mb Full
l Speed is 10Mb/s.
l Duplex is Full.
10Mb Half
l Speed is 10Mb/s.
l Duplex is Half.
100Mb Full
l Speed is 100Mb/s.
l Duplex is Full.
100Mb Half
l Speed is 100Mb/s.
l Duplex is Half.
1000Mb Full

l Duplex is Full
1000Mb Half

l Duplex is Half
Issue 05 (2014-03-28)

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

114
BSC6910 GSM
Figure 8-12 Operational interface
Click Continue with preparing USB device to start preparing the USB flash
drive. Then go to Step 12.
Click Save the NE backup data, select the save path for the backup file, and click
Finish. Then go to Step 7.
NOTE
l If you just want to back up data or you cannot continue with preparing the USB flash drive
because it cannot be identified by the PC, click Save the NE backup data to save the NE
backup data to the PC for future use. Before you click Save the NE backup data, ensure
that the relevant backup file exists in the Dopra Linux\NE Name\bk_pkg directory.
l The backup file created after you click Save the NE backup data is saved in a file folder
named after the OMU virtual external IP address of the NE.
l The backup file created after you click Save the NE backup data can be saved for
preparing the USB flash drive before going to the site where the USB flash drive cannot
be prepared.
Issue 05 (2014-03-28)

115
BSC6910 GSM
NOTICE
l The backup file cannot be modified after being saved on the PC. Otherwise, you
cannot prepare the USB flash drive by using the local backup data of the NE.
l The saved NE data backup file does not contain information of the version or patch
installation package.
7.
To prepare the USB flash drive by using the local backup data, double-click
U_creator_eng.exe to start the USB flash drive for installation of the DOPRA Linux
operating system.
8.
Select NE List in the left pane of the window, right-click the NE list, and choose Add
NE from the shortcut menu. The dialog box shown in Figure 8-13 is displayed.
9.
In the dialog box shown in Figure 8-13, type the NE name and set Operate type to
Use the local backup data to create the USB device. Then click OK
10. Double-click the added NE in the NE list on the left pane of the window, as shown in
Figure 8-14.
Issue 05 (2014-03-28)

116
BSC6910 GSM
11. Select please select the local backup data. Then the USB flash drive will
automatically obtain the backup data. After all the data is obtained, select the version
package directory and the patch directory. Then click OK to start the preparation of
the USB flash drive.
12. Check that the USB flash drive for the active OMU is inserted. If there is no USB
flash drive inserted, insert one.
NOTE
l If multiple USB flash drives are required for multiple NEs, one USB flash drive for one NE is
prepared at a time. After one USB flash drive is prepared, remove it, insert a new one, and click
Retry to start the preparation of another USB flash drive.
l After the USB flash drive is prepared, remove it from the PC in secure mode to prevent the data
on it from being lost or corrupted.
13. After the preparation of the USB flash drive for the active OMU, the tool prompts you
to insert another USB flash drive for the standby OMU.
NOTE
l If only one OMU is configured, the standby OMU USB flash drive does not need to be prepared.
l If multiple USB flash drives are required for active and standby OMUs or for multiple NEs,
label USB flash drives with the NE name and OMU slot number to differentiate them.
Issue 05 (2014-03-28)

117
BSC6910 GSM
14. After the preparation of the USB flash drive for the standby OMU, click Finish. The
preparation for the USB flash drives is complete.
----End
Issue 05 (2014-03-28)

118
BSC6910 GSM
Appendix: OMU-Related Information

Tables
About This Chapter

This section describes the tables in which the OMU information is recorded during routine
operation and maintenance on the OMU.
9.1 Information Records of OMU Software Installation
During OMU installation, the software records information regarding the parameter
configurations.
9.2 Checklist for the OMU Software Factory Settings
This section provides a checklist for the OMU software factory settings. The checklist records
the OMU software and the software configurations installed before delivery.
9.3 OMU Directory Operation Rights List
This section describes the OMU directory operation rights list. The list records the operation
rights of all OMU directories.
The OMU folder size list records the size of storage space of the OMU common directories.
9.5 Enabled Ports on the OMU
This section lists the mapping between the enabled ports on the OMU and the services provided
by the product software.
Issue 05 (2014-03-28)

119
BSC6910 GSM
9.1 Information Records of OMU Software Installation

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

Item
Setting
Installation Engineer
Computer name (active

OMU)
Administrator password
(active OMU)
Computer name (standby
OMU)
Administrator password
(standby OMU)
OMU Ethernet Adapter Team IP Address Installation Information

Item
Setting
Internal IP address (subnet

mask) of the active OMU
External IP address (subnet
mask) of the active OMU
Internal IP address (subnet
mask) of the standby OMU
External IP address (subnet
mask) of the standby OMU
Backup channel IP address
(subnet mask) of the active
OMU
Backup channel IP address
(subnet mask) of the standby
OMU
Commissioning IP address
(mask) of the active OMU
Commissioning IP address
(subnet mask) of the standby
OMU
Issue 05 (2014-03-28)

120
BSC6910 GSM
Item
Setting
BSC local IP address (subnet

mask)
Virtual Local Area Network
(VLAN) ID for
communication with the
VNP
Virtual Local Area Network
(VLAN) ID for
communication with the
EMS/LMT
Default gateway
Product Software Installation Information

Item
Setting
Installer
Administrator (admin)
password
Password of the FTP user
(FtpUsr)
Virtual internal IP address
Virtual external IP address
Local office name
For details, see Information Records of OMU Software Installation.
9.2 Checklist for the OMU Software Factory Settings

This section provides a checklist for the OMU software factory settings. The checklist records
the OMU software and the software configurations installed before delivery.
Checklist for the EOMUa Board Software Factory Settings
Issue 05 (2014-03-28)
Item
Remarks
Setting the RAID 1 between the two SAS

hard disks on the EOMUa boards
Setting OMU BIOS
l Set the first boot device of the OMU to USB.

121
BSC6910 GSM
Item
Remarks
Installing the Dopra Linux operating

system
l If the version of the OMU operating system is

RTOS-V100R001C00SPC070 or later,
The default root user passwords of the
active and standby OMUs are
osadmin@123.
The default lgnusr user passwords of the
osnormal@123.
l If the version of the OMU operating system is
earlier than RTOS-V100R001C00SPC070,
The default root user passwords of the
mbsc@com.
Installing the IPMI driver
Teaming the internal Ethernet adapter

team
The default IP address of the internal Ethernet

adapter team of the active OMU is 80.168.3.50
(255.0.0.0).
The default IP address of the internal Ethernet
adapter team of the standby OMU is 80.168.3.60
(255.0.0.0).
Teaming the external Ethernet adapter

team
The default IP address of the external Ethernet

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

of the active and standby OMUs
The default backup channel IP addresses of the

active OMU is 192.168.3.50 (255.255.255.0).
The default backup channel IP addresses of the
standby OMU is 192.168.3.60 (255.255.255.0).
Configuring debugging IP addresses of

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

of the active OMU is 192.168.6.50
(255.255.255.0).
The factory setting of the debugging IP addresses
of the standby OMU is 192.168.6.60
(255.255.255.0).
For details, see Checklist for the OMU Software Factory Settings.
Issue 05 (2014-03-28)

122
BSC6910 GSM
9.3 OMU Directory Operation Rights List

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

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

The following are two examples of directory operation rights explanation:
Issue 05 (2014-03-28)

123
BSC6910 GSM
/mbsc:
drwxrwxrwx 8 root mysql
-rw-r-xr-- 1 root root
mysql
upsrvcfg.ini
drwxrwxrwx 8 root mysql mysql indicates that the current user root, the users in the mysql
user group that the user root belongs to, and the users who do not belong to the mysql user
group have the rights to read and write into the /mbsc/mysql folder as well as the rights to
search for files in the folder.
-rw-r-xr-- 1 root root upsrvcfg.ini indicates that the current user root has the rights to
read and write into the upsrvcfg.ini file in the /mbsc folder; the users in the root user group
that the user root belongs to have the rights to read and execute the upsrvcfg.ini file in
the /mbsc folder, and users who are not in the root use group that the user root belongs to
have the rights to read the upsrvcfg.ini file in the /mbsc folder.

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

Content
Storage
File Type
Host
binary log
Saving Path
/mbsc/bam/common/
fam/famlogfmt
Specifications
Classification
Files in the
current
directory
Maximum Size (MB)

GSM
Only
UMT
S
Only
GU
Only
3029
0
67768
2187
2
Files and
subdirectories
in the current
directory
Issue 05 (2014-03-28)
106967
Maxim
um
Files
120000
N/A
TC DSP
lastword
log
/mbsc/bam/common/
fam/famlogfmt/
dspinfo
Files in the
current
directory
2088
N/A
2088
30000
System
fault log
/mbsc/bam/common/
fam/famlogfmt/
sysfault
Files in the
current
directory
1228
1228
1228
1200
2G PCHR
log
/mbsc/bam/common/
fam/famlogfmt/gphr
Files in the
current
directory
2525
1
N/A
1683
4
120000
2G CHR
log
/mbsc/bam/common/
fam/famlogfmt/gchr
Files in the
current
directory
1683
4
N/A
8417
30000

124
BSC6910 GSM
Content
Host crash
log
/mbsc/bam/common/
fam/fad
Specifications
Files in the
current
directory
3379
Files and
subdirectories
in the current
directory
Host log
/mbsc/bam/common/
fam/famlog
Files in the
current
directory
3379
6328
2088
Files and
subdirectories
in the current
directory
2088
30000
N/A
2088
3010
120000
N/A
3G PCHR
log
/mbsc/bam/common/
fam/famlogfmt/pchr
Files in the
current
directory
N/A
37049
2439
2
120000
VIP user
tracing log
/mbsc/bam/common/
fam/famlogfmt/
viptrace
Files in the
current
directory
N/A
861
861
12000
MR log
/mbsc/bam/common/
fam/mr
Files in the
current
directory
7803
120000
Files and
subdirectories
in the current
directory
7802
N/A
Files in the
current
directory
8417
48000
Files and
subdirectories
in the current
directory
8417
N/A
Files in the
current
directory
246
1000
Tracing
file
File
exported
by running
the EXP
CFGBCP
command
Issue 05 (2014-03-28)
3379
/mbsc/bam/common/
fam/trace
/mbsc/bam/version_x/
ftp/ExportBCPfile

125
BSC6910 GSM
Content
Issue 05 (2014-03-28)
Specifications
Exported
M2000
and CME
BCP file
ftp/ExportCMESyncView
Files in the
current
directory
430
N/A
File
exported
by running
the
EXP UKPI
command
ftp/kpi_file
Files and
subdirectories
in the current
directory
430
N/A
Exported
device file
ftp/device_file
Files and
subdirectories
in the current
directory
430
N/A
Exported
electronic
label file
ftp/e_label
Files and
subdirectories
in the current
directory
430
N/A
File
exported
by running
the
EXP ALM
LOG
command
ftp/export_almlog
Files and
subdirectories
in the current
directory
430
N/A
File
exported
by running
the EXP
CFGMML
command
ftp/export_cfgmml
Files in the
current
directory
860
N/A
Directory
exported
from board
replaceme
nt logs and
board
temperatur
e logs
ftp/export_logfile
Files and
subdirectories
in the current
directory
184
N/A
Cell
relocation
log
ftp/OptMml
Files in the
current
directory
184
300

126
BSC6910 GSM
Content
Specifications
File server
directory
/mbsc/bam/common/
ems
Files and
subdirectories
in the current
directory
6328
N/A
Database
file backup
directory
data/backup
Files and
subdirectories
in the current
directory
1290
N/A
Remark:
Remark:
version_x indicates the active workspace of the OMU, which is either version_a or
version_b.
If the FREEDISKSW parameter is set to ON by running the SET OMUPARA command,
the storage specifications of the following logs are dynamically adjusted when the disk
space on the OMU is small or insufficient: host binary log, 3G PCHR, 2G PCHR, 2G
CHR, and MR. If this parameter is disabled, each log in the preceding table takes up a
fixed disk space on the OMU. When the space is insufficient for any of these logs that
are newly generated, the corresponding type of logs will be deleted from the earliest one
until sufficient space is released for the new one.
For details about storage space of the OMU common directories, see OMU Folder Size List.
9.5 Enabled Ports on the OMU

This section lists the mapping between the enabled ports on the OMU and the services provided
by the product software.
For details about the communication ports on the OMU, see BSC6910 Communication Matrix.
Issue 05 (2014-03-28)

127
BSC6910 GSM
10
Appendix: Troubleshooting
About This Chapter

This chapter describes OMU faults and troubleshooting methods.
10.1 Restoring OS by the Using USB Storage Device
This section describes how to restore the OMU operating system (OS) by using a prepared USB
storage device.
Issue 05 (2014-03-28)

128
BSC6910 GSM
10.1 Restoring OS by the Using USB Storage Device

This section describes how to restore the OMU operating system (OS) by using a prepared USB
storage device.
Prerequisites
l
There are USB ports available on the OMU board panel.

NOTE
The USB flash device with an indicator is inserted into the USB port. If the indicator is on, then the USB
port is available.
Context
This operation applies only to the scenario of restoring a crashed OMU OS in which case OMU
data does not require to be retained since product software and data are lost after this operation.
Procedure
Step 1 Prepare a USB storage device. For details, see Preparing the USB storage device for restoring
the OMU operating system in 8.3 Dopra_Linux_USB Disk Tool.
Step 2 Insert the USB flash device into any of the USB ports on the OMU board panel.
Step 3 Remove and then reinstall the OMU board to reset the OMU.
NOTE
Press and hold the two locking buttons, flip the ejector levers out on the OMU board panel to unlock them,
and rotate them outward. The OMU board is separated from the backplane. Remove the OMU board after
the OFFLINE LED flashes fast and then is steady blue.
Step 4 Wait 1 to 2 minutes and then use the USB flash device to restore the OMU operating system.
Check the status of indicators on the OMU board panel to determine whether the OMU operating
system is restored successfully.
If the OMU operating system is to be restored, check the indicator status. See Table 10-1.
Table 10-1 Status of the indicators on the OMU board panel during the OMU operating system
restoration
Board
Running Status
Successful
Restoration
Failed Restoration
EOMUa
l The RUN
indicator blinks.
l The RUN
indicator blinks.
l The RUN
indicator blinks.
l The ALM
indicator blinks.
l The ALM
indicator is
steady on or off.
l The ALM
indicator blinks.
l The ACT
indicator blinks.
l The OFFLINE
indicator is off.
l The ACT
indicator is
steady on or off.
l The ACT
indicator is off.
l The OFFLINE
indicator is off.
l The OFFLINE
indicator blinks.
Issue 05 (2014-03-28)

129
BSC6910 GSM
NOTE
l If the status of the indicators differs from this, the OMU cannot identify the USB flash device. When this
occurs, prepare another USB flash device. Alternatively, copy the data in the original USB flash device to
a new USB flash device, and then restore the OMU operating system.
l For information about how much time will be consumed during the OMU operating system restoration, see
Table 1 in 8.3 Dopra_Linux_USB Disk Tool.
NOTICE
l After the OMU operating system is restored successfully, remove the USB flash device from
the OMU board panel in a timely manner.
l After the OMU operating system is restored using a USB flash drive, the password changes
to the default value.
l If the version of the OMU operating system is V200R003C02SPC090 or later, log in to
the active OMU as the lgnusr user, for whom the initial password is osnormal@123. Do
not log in to the OMU as the root user. After the login succeeds, you can run the su
command to switch to the root user, for whom the initial password is osadmin@123.
l If the version of the OMU operating system is earlier than V200R003C02SPC090, log in
to the active OMU as the root user, for whom the initial password is mbsc@com.
l If you do not know the version of the OMU operating system, try to log in to the active
OMU first as the lgnusr user and then the root user.
----End
Follow-up Procedure
If the OS fails to be restored, do as follows:
1.
Prepare a new USB storage device. For details, see Step 1.

l If the OS is restored successfully, check whether the following procedures require to
be implemented:
After the OS is restored, the setting on the original OS for the function of disabling
root user remote login will become ineffective. To enable this function on the new
OS, implement operations in 11.1 Disabling root user login with SSH.
Only when BSC is enabled with the Radio Measurement Data Interface for
Navigation feature and the BSC local IP address is used for communication between
the OMU and VNP, do you need to reconfigure the BSC local IP address, VLAN
IDs for communication between the OMU and VNP, and VLAN IDs for
communication between the OMU and EMS/LMT based on "OMU Ethernet
Adapter Team IP Address Installation Information." For details, see Radio
Measurement Data Interface for Navigation in GBSS Feature Documentation.
l If the OS fails to be restored, contact Huawei Customer Service Center.
Issue 05 (2014-03-28)

130
BSC6910 GSM
11
Appendix: Security FAQ
About This Chapter

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

131
BSC6910 GSM
11.1 Disabling root user login with SSH

This section describes how to disable root user login with SSH to security-harden the
BSC6910.
Prerequisites
l
The OMU is running properly.
Context
This operation only applies to Dopra Linux V2.
version_a as the OMU active workspace is used as an example in this operation. To query the
current OMU active workspace, run the LST OMUAREA command.
Procedure
l
Disabling root user login with SSH

NOTE
l Ensure that a new common user account has been created before disabling root user login with SSH.
Otherwise, the operation fails.
l After root user login with SSH is disabled, the current user will not be logged off automatically. A
new login will be disabled.
l If the OMU operating system version is RTOS-V100R001C00SPC070 or later, the root user is
forbidden by default while the lgnusr user is added as the default account. To query the OMU operating
system version, run the LST VER command.
Issue 05 (2014-03-28)
1.
Log in to the OMU as a root user. For details, see 7.3 Logging In to the OMU.
2.
Type the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the

directory where the root_login.sh script is saved.
3.
Type the chmod +x root_login.sh command and press Enter to make the
root_login.sh script executable.
4.
Type the ./root_login.sh disable command and press Enter. The message Disable
root user login, are you sure? [y/n]: is displayed. Enter y and press Enter to disable
root user login.
Adding a common user account

1.
Log in to the OMU as a root user.
2.
Type the useradd -m User Name command and press Enter to add a common user
account.
3.
Type the passwd Password command and press Enter to set the password.
4.
Confirm the password. The common user account is added.

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

1.
Log in to the OMU as a common user or lgnusr user.
2.
Type the command passwd and press Enter. You are prompted to type the password.
3.
Type the common user password. The user password is changed.

NOTE
l It is recommended that you change the root user password upon your first login and change the
password every three months.
l A root user password must contain the combination of the following:
l At least one special character `~!@#$%^&*()-_=+\|[{}];:'",<.>/? or a space
The root user password must have a minimum length of 8 characters and maximum length of
127 characters.
Switching from a common user account or a lgnusr user account to a root user account
1.
2.
Type the command su and press Enter. You are prompted to type the password.
3.
Type the root user password and press Enter to switch the user account from common
user or lgnusr user to root user.
Querying user information on the OMU

1.
Log in to the OMU as a common user, lgnusr user or root user.
2.
Type the cat /etc/passwd command and press Enter to query the information of all
users.
Deleting a common user account

NOTE
l To delete a common user account, you must have a root user account.
l A common user account cannot be deleted while in use.
l If there is not any common user who is allowed for login with SSH, the lgnusr user is not allowed to
be deleted.
1.
Log in to the OMU as a common, lgnusr user or root user.

NOTE
If you have logged in as a common user or lgnusr user, re-log in as a root user before deleting a
common user account.
2.
l
Issue 05 (2014-03-28)
Type the userdel -r User Name command and press Enter to delete the account.
Enabling root user login with SSH

133
BSC6910 GSM
1.
2.
Switch the account of a common user or lgnusr user to that of a root user.
3.

directory where the root_login.sh script is saved.
4.
5.
Type the ./root_login.sh enable command and press Enter. The message Enable
root user login, are you sure? [y/n]: is displayed. Enter y and press Enter to enable
root user login.
Querying the status of the root user login

1.
Log in to the OMU as a root user.
2.
Type the cd /mbsc/bam/version_a/bin/bam command and press Enter to switch the

current directory to the directory where the root_login.sh script is saved.
3.
4.
Type the ./root_login.sh status command and press Enter to query the status of the
root user login with SSH.
NOTE
Parameter description
l Configuration status indicates the root user status to be configured.
l Actual status indicates the current root user status.
l enabled indicates that the root user login with SSH is enabled. disabled indicates that the root
user login with SSH is disabled.
----End
Example
The following is used as an example for disabling root user login with SSHn to the OMU.
omucc_68 / # cd /mbsc/bam/version_a/bin/bam
omucc_68 /mbsc/bam/version_a/bin/bam # chmod +x root_login.sh
omucc_68 /mbsc/bam/version_a/bin/bam # ./root_login.sh disable
Disable root user login, are you sure? [y/n]:y
Disabling root user login
done
The following is used as an example for creating a common user omu123 account.
omucc_68
omucc_68
Changing
New UNIX
/ # useradd -m omu123
/ # passwd omu123
password for omu123.
password: Retype new UNIX password:
The following is used as an example for changing password for common user or lgnusr user.
omucc_68 / # passwd
Changing password for eric.
Old Password:
New Password:
Reenter New Password:
Password changed.
Issue 05 (2014-03-28)

134
BSC6910 GSM
The following is used as an example for switching an account from common user or lgnusr user
to root user.
omucc_68 / $ su
Password:
omucc_68 / #
The following is used as an example for querying user information on the OMU.
omucc_68 / # cat /etc/passwd
root:x:0:0:root:/root:/bin/bash
omu123:x:1001:100::/home/omu123:/bin/bash
The following is used as an example for deleting a common user account.

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

This section describes how to disable OMU route forwarding to security-harden the BSC6910.
Prerequisites
l
The OMU is running properly.
Context
This operation only applies to Dopra Linux V2.
version_a as the OMU active workspace is used as an example in this operation. To query the
current OMU active workspace, run the LST OMUAREA command.
Issue 05 (2014-03-28)

135
BSC6910 GSM
Procedure
l
Disabling OMU route forwarding

NOTE
l If NodeBs are maintained by using the M2000 remotely in the live network, do not disable the OMU
route forwarding. Otherwise, the remote operation and maintenance (O&M) channels for NodeBs fail.
l The OMU route forwarding is enabled by default.
1.
Log in to the OMU. For details, see 7.3 Logging In to the OMU.
2.

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

1.
Log in to the OMU.
2.

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

1.
Log in to the OMU.
2.

3.
4.
Type the ./ip_forward.sh status command and press Enter to query the status of
OMU route forwarding.
NOTE
Parameter description
l Configuration status indicates the status of OMU route forwarding to be configured.
l Actual status indicates the current status of OMU route forwarding.
l enabled indicates that OMU route forwarding is enabled. disabled indicates that OMU route
forwarding is disabled.
----End
Example
The following is used as an example for disabling OMU route forwarding.
omucc_68 ~ # cd /mbsc/bam/version_a/bin/bam
omucc_68 /mbsc/bam/version_a/bin/bam # chmod +x ip_forward.sh
omucc_68 /mbsc/bam/version_a/bin/bam # ./ip_forward.sh disable
Disabling ip forward
Issue 05 (2014-03-28)

done
136
BSC6910 GSM
The following is used as an example for enabling OMU route forwarding.

omucc_68
omucc_68
omucc_68
Enabling
~ # cd /mbsc/bam/version_a/bin/bam
/mbsc/bam/version_a/bin/bam # chmod +x ip_forward.sh
/mbsc/bam/version_a/bin/bam # ./ip_forward.sh enable
ip forward
done
The following is used as an example for querying the status of OMU route forwarding.
omucc_68 ~ # cd /mbsc/bam/version_a/bin/bam
omucc_68 /mbsc/bam/version_a/bin/bam # chmod +x ip_forward.sh
omucc_68 /mbsc/bam/version_a/bin/bam # ./ip_forward.sh status
Configuration status: enabled
Actual status: enabled
Follow-up Procedure
1.
Record the status of OMU route forwarding.
11.3 Configuring the Function of Recording OMU OS

Accessing Information in Real Time
This section describes how to configure the function of recording OMU operating system (OS)
accessing information in real time when users log in to or out of the OMU OS. This function
helps monitor the OMU OS security.
Prerequisites
l
The OMU OS is Dopra Linux.
The peer equipment OS is Linux or Unix.
Context
With this function, the OMU automatically records a user's information and reports the
information to the peer equipment by using the syslog service when the user logs in to or out of
the OMU OS. The reported user information includes the user name, user IP address, and the
number of the port through which the user accesses the OMU.
Multiple OMUs can be enabled with this function. Once enabled, they report their users'
information to the peer equipment simultaneously.
NOTE
For example, the version information for the active OMU workspace is version_a. You can run the LST
OMUAREA command to query the version information for the current active OMU workspace.
Procedure
l
Issue 05 (2014-03-28)
Enabling the function of recording OMU OS accessing information in real time

1.
Log in to the target OMU. For details, see 7.3 Logging In to the OMU.
2.
Run the cd /mbsc/bam/version_a/bin/bam command to switch the directory where

the syslog_config.sh script is saved.
3.
Run the ./syslog_config.sh IP address PORT command to enable the function of

recording OMU OS accessing information in real time.
137
BSC6910 GSM

NOTE
l IP address represents the IP address of the third-party server.

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

1.
2.

3.
Run the ./syslog_config.sh disable command to disable the function of recording

OMU OS accessing information in real time.
Checking whether the function of recording OMU OS accessing information in real time
is enabled
1.
2.

3.
Run the ./syslog_config.sh l command to query whether the function of recording

OMU OS accessing information in real time is enabled.
----End
11.4 Enabling Function of Checking OS File Integrity

This section describes how to enable the function of checking the operating system (OS) file
integrity. This function is for monitoring the security of the OMU OS.
Prerequisites
The OMU OS File Integrity Checklist is available.
Context
l
The OMU OS File Integrity Checklist is used to specify the OS files to be checked. This
list must be in .txt format and file path information for a maximum of 5000 files can be
provided in the list. File path information for each file occupies one line and must include
the file name. The following is the example of file path information corresponding to Linux,
respectively: /etc/sysctl.conf.
After the function is enabled, the OMU checks the integrity of specified files every 12
hours. If the check fails, the ALM-20723 File Loss or Damage is reported. In the scenarios
of version upgrade, driver upgrade, and OS upgrade, if the ALM-20723 File Loss or
Damage is reported after a monitored file is changed, clear the alarm by following the alarm
handling procedures.
After an OS switch, this function will be automatically disabled and the OMU OS File
Integrity Checklist will be deleted. To enable this function, the OMU OS File Integrity
Checklist must be created and loaded again.
Issue 05 (2014-03-28)

138
BSC6910 GSM
It is recommended that the files to be checked must be important and will not be changed
by the NE automatically. If the OMU is using Linux, files in the following directories are
recommended to be checked: /bin, /boot, /etc, /sbin, and /sys
NOTE
If the OMU is in active/standby mode, enable or disable this function on both active and standby OMUs.
Procedure
l
Enabling this function

1.
Upload the OMU OS File Integrity Checklist into the ftp/integrity_cfg directory in
the OMU active workspace. For details, see File Manager.
2.
Run the ACT FILEINTEGRITYPRO command to enable this function.
Disabling this function

1.
Run the DEA FILEINTEGRITYPRO command to disable this function.
Querying the function status

1.
Run the LST FILEINTEGRITYPRO command to query the status of this function.
----End
11.5 Enhancing Security of Time Synchronization with NTP

The security of time synchronization with Network Time Protocol (NTP) is enhanced for the
BSC6910 after NTP messages are authenticated.
Prerequisites
l
The peer equipment supports NTP and NTP message authentication.
The IP address, NTP server port number, and key index of the peer equipment have been
obtained.
Context
Before sending a synchronization request to an NTP server, the OMU, as an NTP client, encrypts
the request and attaches a key index and encryption information to the request. The NTP server
decrypts the request and sends a synchronization response to the NTP client. After receiving the
response, the NTP client checks whether the encryption information in the response is consistent
with that calculated locally. If yes, the time synchronization between the NTP client and server
starts.
If multiple NTP servers are configured for the time synchronization with the OMU (NTP client),
the OMU automatically selects the best NTP server as the clock source.
When OMU of the BSC6910 is used as an NTP client, the OMU supports the NTP-based time
synchronization in plaintext or in cipher.
When OMU of the BSC6910 is used as an NTP server, the OMU only provides NTP plaintext
in internal network.
Issue 05 (2014-03-28)

139
BSC6910 GSM
Procedure
Step 1 Log in to the LMT by referring to Logging In to and Logging Out of the LMT.
Step 2 To add the information of an NTP server connected to the OMU, run the ADD
SNTPSRVINFO command and set the following parameters as required: IP Address, Port,
NTP Authentication Mode, Key ID, Encryption Algorithm, Key, Confirmation Key.
NOTE
Repeat Step 2 to configure multiple NTP servers available for the time synchronization with the OMU.
----End
Issue 05 (2014-03-28)

140
BSC6910 GSM
12
Appendix: Special OMU Networking

Scenarios
About This Chapter

This section describes special scenarios associated with connecting the OMU to peripheral
equipment.
12.1 Scenario of Connecting the OMU and VNP
This section describes how to modify the connection between the OMU and Vendor Network
Probe (VNP) if the BSC6910 supports the Radio Measurement Data Interface for
Navigation feature.
Issue 05 (2014-03-28)

141
BSC6910 GSM
12.1 Scenario of Connecting the OMU and VNP

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

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

In this scenario, the BSC local IP address is used for communication between the BSC and VNP.
l
The M2000 and VNP can be configured in different LANs.
The BSC local IP address for communication between the BSC6910 and VNP must be
configured on the OMU.
Issue 05 (2014-03-28)

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

The BSC local IP address for communication between the BSC6910 and VNP is configured on
the external Ethernet adapter team of the OMU.
Figure 12-2 show the binding relationship between Ethernet adapters of the OMU board.
NOTE
VLANs vlan2 and vlan3 in Figure 12-2 are used as examples. The VLAN IDs depend on the actual configuration.
Figure 12-2 Binding relationship between Ethernet adapters on the EOMUa board
Description of the binding relationship between Ethernet adapters on the EOMUa board
l
B_ETH0 and B_ETH1 are bound as an internal Ethernet adapter team, bond0. Vlan1 is
established on bond0 for communication between the OMU and SCU. Vlan1 and vlan1:0
are corresponding to the fixed and virtual internal IP addresses of the OMU, respectively.
F_ETH0 and F_ETH1 are bound as an external Ethernet adapter team, bond1. Vlan2 and
vlan3 are established on bond1 for communication between the OMU and the M2000 and
VNP. Vlan2 and vlan2:0 are corresponding to the fixed and virtual external IP addresses
of the OMU respectively while vlan3 is corresponding to the BSC local IP address.
F_DBG (bond2), a commissioning Ethernet adapter, is connected to a portable PC for OMU

commissioning if required.
B_UPDATE (bond3), a backup Ethernet adapter, is used as the backup channel between
the active and standby OMUs when the BSC6910 is configured with two EOMUa boards.
BSC local IP address:

l
The BSC local IP address is null by default. The BSC local IP address requires to be
configured only if the feature Radio Measurement Data Interface for Navigation is
enabled on the BSC6910 and the prerequisites in scenario 2 are met.
If active and standby OMUs are switched over when a VNP communicates with the OMU
using the BSC local IP address, the communication will be interrupted for a while and then
be recovered automatically. During this process, the BSC local IP address of the original
Issue 05 (2014-03-28)

143
BSC6910 GSM
standby OMU starts to take effect, and the BSC local IP address of the original active OMU
becomes ineffective.
Restrictions on configuring the BSC local IP address:
l
The network segment of the BSC local IP address must be different from that of the
following IP addresses: fixed and virtual internal IP addresses of the OMU, commissioning
IP address, and backup channel IP address of the active and standby OMUs.
Impact of deleting or changing the BSC local IP address:

l
After the BSC local IP address is deleted or changed, the VNP connected to the OMU
through the original IP address cannot access the OMU unless through a new BSC local IP
address.
The BSC local IP address can be changed remotely, and the new IP address takes effect
immediately.
For details about configuring the BSC local IP address, see Radio Measurement Data Interface
for Navigation in GBSS Feature Documentation.
Issue 05 (2014-03-28)

144

Bsc6910 GSM Omu Administration Guide (v100r015c00 - 05) (PDF) - en

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Bsc6910 GSM Omu Administration Guide (v100r015c00 - 05) (PDF) - en

Загружено:

Авторское право:

Доступные форматы

BSC6910 GSM

OMU Administration Guide

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

Huawei Proprietary and Confidential

About This Document

This section has the following topics:

Huawei Proprietary and Confidential

About This Document

Times New Roman

Normal paragraphs are in Times New Roman.

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

Book titles are in italics.

Examples of information displayed on the screen are in

The keywords of a command line are in boldface.

Command arguments are in italics.

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

Optional items are grouped in braces and separated by

About This Document

Optional items are grouped in brackets and separated by

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

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

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

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

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

Select and release the primary mouse button without moving

Huawei Proprietary and Confidential

About This Document

Press the primary mouse button twice continuously and

Huawei Proprietary and Confidential

3 Working Principles of the OMU..............................................................................................11

4 Initially Commissioning the OMU..........................................................................................29

5 Installing OMU Software..........................................................................................................38

6 Operating and Maintaining the OMU....................................................................................55

Huawei Proprietary and Confidential

7 Appendix: OMU-Related Operations......................................................................................91

8 Appendix: OMU-Related Software..........................................................................................95

9 Appendix: OMU-Related Information Tables.....................................................................119

Huawei Proprietary and Confidential

9.2 Checklist for the OMU Software Factory Settings.....................................................................................................121

11 Appendix: Security FAQ........................................................................................................131

12 Appendix: Special OMU Networking Scenarios.............................................................. 141

Huawei Proprietary and Confidential

1 Changes in BSC6910 GSM OMU Administration Guide

Changes in BSC6910 GSM OMU

Active/Standby Workspaces of the OMU

Deleted this content because this function has

Switching Over the Active/Standby OMU

6.13.3 Changing Users' Passwords

Changed the background information.

Huawei Proprietary and Confidential

1 Changes in BSC6910 GSM OMU Administration Guide

7.2 Starting the omutool

The use right of the omutool is changed.

9.4 OMU Folder Size List

The storage specifications of some logs are