V900R014C00
Issue 08
Date 2013-06-25
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.
Website: http://www.huawei.com
Email: support@huawei.com
Purpose
This document describes the software and hardware structure, software installation, GUI, and
operations for the OMUa/OMUc board.
Product Version
The following table lists the product version related to this document.
BSC6900 V900R014C00
Intended Audience
This document is intended for:
l Field engineers
l Shift operators
Organization
1 Changes in the BSC6900 UMTS OMU Administration Guide
This document describes the changes in the BSC6900 UMTS OMU Administration Guide.
2 Introduction to OMU
The physical entity of the OMU is the OMUa/OMUc board. The OMU collects and processes
information about operation and maintenance (OM), and reports this information to the OM
terminal: either the LMT or M2000.
3 Working Principles of the OMU
This section has the following topics:
4 Scenario: Deploying a BSC6900
This section describes how to install software and perform operation and maintenance for the
OMU when a BSC6900 is deployed.
5 Scenario: Upgrading from the BSC6810 to the BSC6900
This chapter describes how to install software and perform operation and maintenance for the
OMU when the BSC6810 is upgraded to the BSC6900.
6 Appendix: Security FAQ
This section describes how to improve the security of the BSC6900.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
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.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Contents
This document describes the changes in the BSC6900 UMTS OMU Administration Guide.
08 (2013-06-28)
This is the eighth commercial release of V900R014C00.
Compared with issue 07 (2013-04-15), this issue includes the following new topics:
Compared with issue 07 (2013-04-15), this issue incorporates the following changes:
Content Description
Preparing a USB Storage Device Add note: After the OMU operating system
is installed, user security settings (including
user passwords and security policies) are
restored to the factory settings.
Compared with issue 07 (2013-04-15), this issue does not exclude any topics.
07 (2013-04-15)
This is the seventh commercial release of V900R014C00.
Compared with issue 06 (2013-03-25), this issue includes the following new topics:
l 4.3.4 Querying the Link Mode of the External OMU Network Adapters
Compared with issue 06 (2013-03-25), this issue incorporates the following changes:
Content Description
Installing the OMU Operating System Updated the status of indicators during the
Using a USB Flash Drive operating system installation, operating
system restoration, and operating system and
OMU applications installation.
4.5.4 OMU Folder Size List The OMU folder size list is updated.
Compared with issue 06 (2013-03-25), this issue does not exclude any topics.
06 (2013-03-25)
This is the sixth commercial release of V900R014C00.
Compared with issue 05 (2012-12-31), this issue does not exclude any new topics.
Compared with issue 05 (2012-12-31), this issue incorporates the following changes:
Content Description
4.5.2 Checklist for the OMU Software Changed the default root user passwords of
Factory Settings the active and standby OMUs to
Installing the OMU Operating System osadmin@123.
Using a USB Flash Drive
Preparing a USB Storage Device Kingston and Sandisk USB storage devices
are added.
5.1.2 Switching the OMU Operating
System
Compared with issue 05 (2012-12-31), this issue does not exclude any topics.
05 (2012-12-31)
This is the fifth commercial release of V900R014C00.
Compared with issue 04 (2012-11-07), this issue includes the following new topics:
Compared with issue 04 (2012-11-07), this issue incorporates the following changes:
Content Description
3.1 OMU Ethernet Adapter Configuration Notes on the bond1 and bond1:0 of the OMUa
board are added.
Compared with issue 04 (2012-11-07), this issue does not exclude any topics.
04 (2012-11-07)
This is the fourth commercial release of V900R014C00.
Compared with issue 03 (2012-08-30), this issue includes the following new topics:
Compared with issue 03 (2012-08-30), this issue incorporates the following changes:
Content Description
5.1.2 Switching the OMU Operating Procedures of configuring the ACL for the
System PortTrunking service on the M2000 are
added.
Content Description
Logging In to the OMU Notes on the password of the user root are
added.
Creating the Installation Source of the Notes on obtaining the SetWin software are
SetWin Software and OS Patches added.
5.2.1 Querying the Configuration of the The chapter title is changed to Querying the
OMU Ethernet Adapters Configuration of the OMU Ethernet
Adapters.
Installing the OMU Operating System The status of indicators on the OMU during
Using a USB Flash Drive installation is modified.
The description that the password for logging
in to the operating system automatically
changes to the default value after the
operating system is recovered using a USB
flash drive is added.
Compared with issue 03 (2012-08-30), this issue does not exclude any topics.
03 (2012-08-30)
This is the third commercial release of V900R014C00.
Compared with issue 02 (2012-06-30), this issue does not exclude any new topics.
Compared with issue 02 (2012-06-30), this issue incorporates the following changes:
Content Description
Content Description
5.1.2 Switching the OMU Operating The description about how to start the
System Dopra_Linux_U tool by using EMS Proxy
IP Address is added.
Compared with issue 02 (2012-06-30), this issue does not exclude any topics.
02 (2012-06-30)
This is the second commercial release of V900R014C00.
Compared with issue 01 (2012-04-26), this issue includes the following new topics:
l 4.5.3 OMU Directory Operation Rights List
l 6.4 Configuring the Function of Recording OMU OS Accessing Information in Real
Time
l 6.5 Enabling Function of Checking OS File Integrity
Compared with issue 01 (2012-04-26), this issue incorporates the following changes:
Content Description
Switching Over the Active/Standby OMU The scenarios of OMU active and standby
Workspaces workspace switch is changed.
Content Description
l Scenario: Upgrade from the BSC6000 to Added the description that you need to
the BSC6900 contact Huawei engineers regarding
4.2.1 Preparations for Installing information or tools that you need to
Software Onsite download from Software Center.
l Scenario: Upgrade from the BSC6810 to
the BSC6900
5.1.2 Switching the OMU Operating
System
Creating the Installation Source of
the SetWin Software and OS
Patches
Preparations for Reinstalling the
OMU Operating System
Compared with issue 01 (2012-04-26), this issue does not exclude any topics.
01 (2012-04-26)
This is the first commercial release of V900R014C00.
Compared with issue Draft B (2012-03-26), this issue includes the following new topics:
Compared with issue Draft B (2012-03-26), this issue incorporates the following changes:
Content Description
2.4.3 OMU Service Monitoring Entities The OMU monitoring mechanism is changed
from two-level to three-level.
Transferring OMU Files to a Local PC The initial password for the FtpUsr user is
changed.
6.1 Disabling root user login with SSH Explanations for password change policy are
added.
5.5.3 List of Enabled Ports on the OMU The port 3306 is deleted.
Content Description
5.1.2 Switching the OMU Operating The Add NE interface is modified and the
System explanation for the Admin Password
parameter is added.
Compared with issue Draft B (2012-03-26), this issue does not exclude any topics.
Draft B (2012-03-26)
This is the Draft B release of V900R014C00.
Compared with issue Draft A (2012-02-15), this issue does not include any new topics.
Compared with issue Draft A (2012-02-15), this issue incorporates the following changes:
Content Description
4.3.7 Setting RAID 1 on OMU Hard Disks Descriptions about using the external
keyboard and monitor to configure the OMU
hard disk RAID 1 are added.
6.1 Disabling root user login with SSH The method of modifying a non-root user's
password is added.
Content Description
l Scenario: Creating a BSC6900 NE Notes on ports 6099, 8099, 16002 and 18002
4.5.5 List of Enabled Ports on the OMU are modified.
l Scenario: Upgrade from the BSC6810 to
the BSC6900
5.5.3 List of Enabled Ports on the OMU
Compared with issue Draft A (2012-02-15), this issue does not exclude any topics.
Draft A (2012-02-15)
This is the Draft A release of V900R014C00.
Compared with issue 05 (2012-01-05) of V900R013C00, this issue includes the following new
topics:
Compared with issue 05 (2012-01-05) of V900R013C00, this issue incorporates the following
changes:
Content Description
3.7 Switchover Between Active and A condition for triggering the OMU self-
Standby OMUs healing switchover has been added.
4.1.1 Setting the Link Mode of the External The method for setting the mode of the OMU
OMU Ethernet Adapter external network Ethernet adapter has been
modified.
Content Description
Preparing a USB Storage Device The login interface of the USB storage device
has been modified. And the relevant interface
descriptions have been added.
4.3.2 Querying the Configuration of the The method for querying the Ethernet adapter
OMU Ethernet Adapters configuration by using the omutool has been
added.
l Scenario: Upgrade from the BSC6810 to The procedure for switching the OMU
the BSC6900 operating system to Dopra Linux is modified.
5.1.2 Switching the OMU Operating
System
Compared with issue 05 (2012-01-05) of V900R013C00, this issue does not exclude any topics.
2 Introduction to OMU
The physical entity of the OMU is the OMUa/OMUc board. The OMU collects and processes
information about operation and maintenance (OM), and reports this information to the OM
terminal: either the LMT or M2000.
As shown in Figure 2-1, the external network is the logical network between the OMU and the
LMT/M2000, and the internal network is the logical network between the OMU and the
BSC6900.
NOTE
l This document describes the installation of other boards based on the OMUa boards being installed in slots
24 to 27.
l Different types of OMU boards can be configured in active and standby slots only for a short period. When
an OMUc board is used to replace an OMUa board, the OMUc board and the OMUa board can be inserted
into the slots and co-exist for a short period (less than one hour), so that data can be synchronized from the
OMUa board to the OMUc board.
l Different types of OMU boards cannot be configured in active and standby slots for a long period. In
scenarios of long-term operation, the active and standby OMU boards must be of the same type. For example,
both active and standby OMU boards must be OMUa boards or OMUc boards.
(1) Captive screw (2) Ejector lever (3) Self-locking latch (4) RUN LED
(5) ALM LED (6) ACT LED (7) RESET button (8) SHUTDOWN button
(9) USB port (10) ETH0 Ethernet port (11) ETH1 Ethernet port (12) ETH2 Ethernet port
(13) COM port (14) VGA port (15) HD LEDs (16) OFFLINE LED
(17) Hard disks (18) Screws for securing the hard disk
NOTE
l To power off the OMUa board, simultaneously pivot the top and bottom ejector levers away from the
front panel of the OMUa board. After the OFFLINE LED is on, turn off the power switch.
l The SHUTDOWN button is used only for powering off the board in an emergency.
l The RESET button is used to reset the system. It works the same way as the reset button on a PC.
l Pressing the SHUTDOWN or RESET button has the risk of scratching the surface of OMUa hard disks.
Avoid pressing these two buttons whenever possible.
USB0-1 and USB2-3 Operators can use the USB ports USB
only after logging in to the
operating system (OS) running on
the board. The ports does not
require a signal cable or connection
to other devices when the system
runs properly. Therefore,
equipment security is not affected.
ETH0 to ETH1 The hardware ports are used for the RJ45
communication between the OMU
and the LMT/M2000.
Number of CPUs 4
Weight 4.0 kg
Memory capacity 2G
*The hard disk capacity can be 73 GB, 146 GB, or 300 GB. Hard disks will be delivered according
Performance Counters
Table 2-4 lists the performance counters of the OMUa board.
Time when the standby The standby OMU synchronizes its data with that of the active
OMU data is OMU board every second.
synchronized with the
active OMU data
Duration of the Five minutes. The time needed for the synchronization varies
synchronization between according to the size and quantity of the files to be synchronized.
the active OMU files and
standby OMU files
Duration of the Refers to the time from the request for OMU switchover being
switchover between the accepted to the switchover being finished. The switchover
active and standby OMUs finishes in four minutes.
Duration of the OMU Duration of the OMU restart caused by an OMU fault. This
restart duration lasts for about three minutes.
The OMUa board contains mechanical hard disk. Adverse environments, such as high
temperature and high altitude, shorten board lifespan.
To extend the lifespan of the OMUa board, protect it from vibration, shock, and abnormal
shutdowns.
NOTE
l This document describes the installation of other boards on the basis that the OMUc boards are installed in
slots 24 and 25.
l Different types of OMU boards can be configured in active and standby slots only for a short period. When
an OMUc board is used to replace an OMUa board, the OMUc board and the OMUa board can be inserted
into the slots and co-exist for a short period (less than one hour), so that data can be synchronized from the
OMUa board to the OMUc board.
l Different types of OMU boards cannot be configured in active and standby slots for a long period. In
scenarios of long-term operation, the active and standby OMU boards must be of the same type. For example,
both active and standby OMU boards must be OMUa boards or OMUc boards.
(1) Captive screw (2) Ejector lever (3) Self-locking latch (4) RUN LED
(5) ALM LED (6) ACT LED (7) POWER Button (8) HDD LED
(9) OFL LED (10) COM port (11) ETH0 Ethernet port (12) ETH1 Ethernet port
(13) VGA port (14) USB port (15) ETH2 Ethernet port
NOTE
To power off the OMUc board, you need to simultaneously pivot the top and bottom ejector levers away
from the front panel of the OMUc board. After the OFL (OFFLINE) LED is on, turn off the power switch.
USB0-1 and USB2-3 Operators can use the USB ports USB
only after logging in to the
operating system (OS) running on
the board. The hardware ports need
no cables or connecting to other
equipment and therefore do not
affect the equipment safety.
ETH0 to ETH1 The hardware ports are used for the RJ45
communication between the OMU
and the LMT/M2000.
Number of CPUs 6
Power consumption 90 W
Weight 2.5 kg
Memory capacity 8 GB
Performance Counters
Table 2-8 describes the performance counters of the OMUc board.
Time when the standby The standby OMU synchronizes its data with that of the active
OMU data is OMU board every second.
synchronized with the
active OMU data
Duration of the Five minutes. The time needed for the synchronization varies
synchronization between according to the size and quantity of the files to be synchronized.
the active OMU files and
standby OMU files
Duration of the Refers to the time from the request for OMU switchover being
switchover between the accepted to the switchover being finished. The switchover
active and standby OMUs finishes in four minutes.
Duration of the OMU Duration of the OMU restart caused by an OMU fault. This
restart duration lasts for about three minutes.
The OMUc board contains a mechanical hard disk. Due to the short lifespan of the mechanical
hard disk, the lifespan of the OMUc board is about 5 years. Adverse environments, such as high
temperature and high altitude, shorten board lifespan.
To ensure the lifespan of the OMUc board, the OMUc board must be protected against vibration,
shock and abnormal shutdown.
The omud process periodically clears the watchdog timer. If the omud process is abnormal and
causes the watchdog timer to overflow, the OMU will be reset automatically.
NOTE
The arrows shown in Figure 2-6 indicate communication between modules.
For details about the OMU service processes, see 2.4.4 OMU Service Processes. For details
about the service monitoring entities, see 2.4.3 OMU Service Monitoring Entities.
Watchdog
A watchdog is a timer used to monitor the omud. Once the omud is abnormal, the watchdog
timer will enable the OMU to be reset.
omud
As a service entity, the omud is registered in the operating system and automatically starts when
the operating system starts. The monitor is started when the omud starts and the omud monitors
the monitor.
Monitor
The monitor monitors the service processes in real time.
Independent Mode
When the BSC6900 is configured with one OMUa/OMUc board, the OMU works in independent
mode.
In this mode, if the OMU is faulty, operation and maintenance (OM) cannot be performed on
the BSC6900. This reduces system reliability.
Active/Standby Mode
When the BSC6900 is configured with two OMUa/OMUc boards, the OMU works in active/
standby mode.
In this mode, the OMUa/OMUc board working in active mode is called the active OMU board,
and the OMUa/OMUc board working in standby mode is called the standby OMU board. The
active and standby OMU boards must be of the same type. Mixed installation of the OMUc
board and the OMUa board is prohibited.
When the BSC6900 is configured in active/standby OMU mode, the OMU can operate properly
with high reliability. Specifically, if a hardware or software fault occurs on the active OMU, the
standby OMU is automatically switched over to the active state and provides services.
NOTE
l Check the OMU working mode before installing the OMU applications.
l After the OMU applications are installed, run the MML command DSP OMU and check the value for the
Operational state parameter in the command output to check the OMU working mode.
In this scenario, log in to the OMU and install the OMU applications. For details, see 4.1
Installing the OMU Applications in Field Commissioning.
l The operation information and faults of the BSC6900 are recorded on the OMU. Therefore,
to timely and accurately locate and rectify BSC6900 faults, do not delete any log file from
the OMU.
Figure 3-1 Binding relationship between Ethernet adapters on the OMUa board
NOTE
l ETH0, ETH1, and ETH2 are connected to the external network through the Ethernet ports on the panel
of the OMUa board. ETH4-SCU7, ETH5-SCU6, and ETH3-UPDATE are connected to the backplane
of the MPS and invisible on the panel of the OMUa board.
l Either bond1 or bond1:0 is reserved for the fixed external IP address, and the other is reserved for the
virtual external IP address.
l When no external fixed IP address is configured, bond1 corresponds to the external virtual IP
address, but bond1:0 does not exist.
l When an external fixed IP address is configured, bond1 corresponds to the external fixed IP address,
and bond1:0 corresponds to the external virtual IP address.
l ETH4-SCU7 and ETH5-SCU6 are bound as an internal Ethernet adapter team, that is, bond0. To enable
communication between the OMU and the SCU, a VLAN whose ID is 1 needs to be established on
bond0. vlan1 and vlan1:0 are used for the fixed internal IP address and the virtual internal IP address,
respectively.
Figure 3-2 Binding relationship between Ethernet adapters on the OMUc board
NOTE
l F_ETH0, F_ETH1, and F_DBG are connected to the external network through the Ethernet ports on
the panel of the OMUc board. B_ETH0, B_ETH1, B_UPDATE0, and B_UPDATE1 are connected to
the backplane of the MPS, and you cannot see them on the panel of the OMUc board.
l Either bond1 or bond1:0 is reserved for the fixed external IP address, and the other is reserved for the
virtual external IP address.
l B_ETH0 and B_ETH1 are bound as an internal Ethernet adapter team, that is, bond0. To enable the
communication between the OMU and the SCU, a VLAN whose ID is 1 needs to be established on
bond0.vlan1 and vlan1:0 are used for the fixed internal IP address and the virtual internal IP address,
respectively.
Debugg IP address for operating and IP address used for ETH2 F_DBG
ing IP maintaining the OMU when a connecting to the
address PC is connected to the OMU
commissioning Ethernet port of commissioning
the OMU using an Ethernet Ethernet port.
cable at the local end. A user can perform
O&M on the OMU
by using the
commissioning IP
address through a PC
or by logging in to
the LMT.
l The network between the OMU internal Ethernet adapters and host boards is defined as an
internal network. The OMU communicates with the base station through the host boards.
l The network between the OMU external Ethernet adapters and the LMT or M2000 is
defined as an external network. The OMU is connected to the LMT or M2000 either directly
or through multiple routers (gateways).
l When configuring a NodeB, ensure that none of the IP addresses (set by running the ADD
UNODEBIP command) that are used for O&M on the NodeB under the BSC6900 are
located in the same network segment as the virtual external IP addresses, fixed external IP
address, IP address of the backup channel between the active and standby OMU, or
commissioning IP address.
l Assume that IP routes are configured for the OMU by running the ADD OMUIPRT
command. If IP routes to the NodeB are configured, ensure that Route Address and
Destination Network Address are not located in the same network segment as the virtual
external IP address, fixed external IP address, IP address of the backup channel between
the active and standby OMUs, or commissioning IP address. If IP routes to the LMT/M2000
are configured, ensure that Forward Route Address and Destination Network
Address are not located in the same network segment as the virtual internal IP address,
fixed internal IP address, IP address of the backup channel between the active and standby
OMUs, or commissioning IP address.
l If one OMU is configured, fixed and virtual external IP addresses of the OMU must be in
the same network segment.
l If active and standby OMUs are configured, the fixed external IP addresses of the active
and standby OMUs, the virtual external IP address of the active and standby OMUs (the
virtual external IP address of the active OMU and that of the standby OMU are the same)
must be configured in the same network segment.
Table 3-2 describes the planning principles of OMU IP addresses.
Fixed external IP The default fixed external IP address of the active OMU is
address 172.121.139.201 (255.255.255.0).
The default fixed external IP address of the standby OMU is
172.121.139.202 (255.255.255.0).
Planning principle:
1. The fixed external IP address should be changed so that it is located in
the same network segment as the onsite network IP address. In
addition, the fixed external IP address cannot conflict with the onsite
network IP address. Configure the IP address of the external gateway
so that it is on the same network segment as the fixed external IP
address. In addition, the IP address of the external gateway cannot
conflict with the fixed external IP address.
2. If active and standby OMUs are configured, the fixed external IP
addresses of the active and standby OMUs must be different from each
other and located in the same network segment as the onsite network
IP address.
Virtual external 1. Change the virtual external IP address as required. Ensure that the
IP address virtual external IP address and the fixed external IP address are in the
same network segment (This network segment is called the OMU
external network segment). In addition, the virtual external IP address
cannot conflict with other IP addresses in the network segment.
For example, if active and standby OMUs are configured, the fixed
external IP address of the active OMU is 172.121.139.201, and that of
the standby OMU is 172.121.139.202, the virtual external IP address
can be configured as 172.121.139.200.
2. For example, if an independent OMU is configured and the fixed
external IP address of the OMU is 172.121.139.201, the virtual
external IP address can be configured as 172.121.139.200.
Fixed internal IP The default fixed internal IP address of the active OMU is 80.168.3.50
address (255.0.0.0).
The default fixed internal IP address of the active OMU is 80.168.3.50
(255.0.0.0).
Checking principle:
1. The network segment in which the fixed internal IP address is located
cannot conflict with the onsite network segment. If they conflict, you
must change the fixed internal IP address.
2. Only the network segment where the fixed internal IP address is
located can be changed. For example, 80.168.3.50 can be changed to
90.168.3.50.
3. If active and standby OMUs are configured, the fixed internal IP
addresses of the active and standby OMUs must be different and in the
same network segment.
4. If an independent OMU is configured and the network segment where
the fixed internal IP address is located does not conflict with the onsite
network segment, reserve the default fixed internal IP address.
5. The subnet mask of the fixed internal IP address must be 255.0.0.0.
Virtual internal 1. The virtual internal IP address must be located in the same subnet as
IP address the fixed internal IP addresses of the active and standby OMUs. This
subnet is called the OMU internal network segment. In addition, the
virtual internal IP address cannot be identical with other IP addresses
in the subnet and it should be configured as X.168.3.40 in which X
must be the same as the network segment where the fixed internal IP
address is located.
For example, if active and standby OMUs are configured, the fixed
internal IP address of the active OMU is 80.168.3.50, and that of the
standby OMU is 80.168.3.60, the virtual internal IP address can be
configured as 80.168.3.40.
2. For example, if an independent OMU is configured and the fixed
internal IP address of the OMU is 80.168.3.50, the virtual internal IP
address can be configured as 80.168.3.40.
3. The subnet mask of the virtual internal IP address must be 255.0.0.0.
IP address of the For an active OMUa board, the IP address of the backup channel between
backup channel the active and standby OMUs must be set to X. X. X. 50. The default IP
between the address is 192.168.3.50 (255.255.255.0).
active and For a standby OMUa board, the IP address of the backup channel between
standby OMUs the active and standby OMUs must be set to X. X. X. 60. The default IP
address is 192.168.3.60 (255.255.255.0).
For an active OMUc board, the IP address of the backup channel between
the active and standby OMUs must be set to X. X. X. 50. The default IP
address of Ethernet adapter B-UPDATE0 is 192.168.9.50(255.255.255.0)
and that of Ethernet adapter B-UPDATE1 is 192.168.3.50
(255.255.255.0).
For an active OMUc board, the IP address of the backup channel between
the active and standby OMUs must be set to X. X. X. 60. The default IP
address of Ethernet adapter B-UPDATE0 is 192.168.9.60(255.255.255.0)
and that of Ethernet adapter B-UPDATE1 is 192.168.3.60
(255.255.255.0).
Planning principle:
1. The network segment where the IP addresses of the channel between
the active and standby OMUs are located cannot conflict with the live
network segment. If they conflict, the IP addresses of the channel
between the active and standby OMUs must be changed.
2. If active and standby OMUs are configured, the IP addresses of the
channel between the active and standby OMUs on the active and
standby OMUs must be different and in the same network segment.
3. If an independent OMU is configured and the network segment where
the IP addresses of the backup channel between the active and standby
OMUs is located is different from the live network segment, retain the
IP addresses of the backup channel between the active and standby
OMUs.
4. The subnet mask of the IP address of the channel between the active
and standby OMUs must be 255.255.255.0.
5. The IP address of the backup channel between the active and standby
OMUs on Ethernet adapter B-UPDATE0 and that on Ethernet adapter
B-UPDATE1 must be on different network segments.
Fixed external IP After the fixed external IP address is changed, the device connected to the
address external Ethernet port can access the OMU only by using the new fixed
external IP address.
The fixed external IP address can be changed remotely and takes effect
immediately after it is changed.
Virtual external After the virtual external IP address is changed, the device connected to
IP address the OMU by using the original IP address can access the OMU only by
using the new virtual external IP address.
The virtual external IP address can be changed remotely and takes effect
immediately after it is changed.
Fixed internal IP The internal fixed IP address and the IP addresses of the BSC6900 host
address boards have been planned. Therefore, only the network segment on which
the internal fixed IP address is located can be changed so that the internal
fixed IP address is not identical with the IP addresses of the BSC6900 host
boards.
If the network segment where the fixed internal IP address is located is
changed, the BSC6900 subnet number must be changed as well.
Otherwise, the communication between the OMU and the BSC6900 host
boards will be interrupted.
The fixed internal IP address is usually changed when the OMU is
debugged on site to avoid negative effects caused by frequent resets of the
BSC6900 during daily maintenance.
The fixed internal IP address can be changed remotely. After it is changed,
you must reset the BSC6900 host at the local end.
Virtual internal The virtual and fixed internal IP addresses must be changed at the same
IP address time.
After the virtual internal IP address is changed, reset the BSC6900 host
boards so that the communication between the OMU and the BSC6900
host boards can be reestablished.
The virtual internal IP address is usually changed when the OMU is
debugged on site to avoid negative effects caused by frequent resets of the
BSC6900 during daily maintenance.
The virtual internal IP address can be changed remotely. After it is
changed, you must reset the BSC6900 host boards at the local end.
IP address of the After the IP address of the backup channel between the active and standby
backup channel OMUs is changed, reset the OMUs so that the communication between
between the the active and standby OMUs can be re-established.
active and The IP address of the backup channel between the active and standby
standby OMUs OMUs can be changed remotely and takes effect immediately after it is
changed.
NOTE
l The fixed internal and external IP addresses are bound to the active and standby OMUs, and the virtual
internal and external IP addresses are bound to the active OMU. For example, after the switchover of the
active and standby OMUs, the fixed internal and external IP addresses of the original active and standby
OMUs remain the same while the virtual internal and external IP addresses of the original active OMU
become the virtual internal and external IP addresses of the original standby OMU. There is no virtual internal
or external IP addresses for the original active OMU.
l Each pair of the following IP addresses must be in the same network segment: fixed and virtual internal IP
addresses, fixed and virtual external IP addresses, IP addresses of the channel between the active and standby
OMUs on the active OMU and standby OMU, commissioning IP address of the active and standby OMU.
The network segments of these pairs of IP addresses cannot conflict with each other. Additionally, the IP
addresses on a network segment cannot conflict, either.
l Record the IP addresses in 4.5.1 Information Record Sheet of OMU Software Installation.
l The next hop IP address of the M2000 route must be the virtual external IP address of the OMU.
The two internal Ethernet adapters ETH4-SCU7 and ETH5-SCU6 of the OMUa board are
connected to the SCUs in slots 7 and 6 of the MPS through the backplane, respectively.
The two external Ethernet adapters ETH0 and ETH 1 of the OMUa board are connected to the
OM terminals through network equipment such as a hub, LAN switch, or router. In this way,
the OMU fulfills the communication between the BSC6900 and the OM terminals.
As shown in Figure 3-6, the two external Ethernet ports of the OMUa board are connected to
the two LAN switches, respectively, which improves network reliability. In this network
topology, the Ethernet ports connecting the ETH0, ETH1, and LAN switches must be in the
same intranet as the two Ethernet ports on the LAN switches connecting ETH0 and ETH1.
Moreover, the Ethernet adapter marked in blue in Figure 3-6 must be enabled with the Spanning
Tree Protocol (STP) function to prevent network storms.
The two internal Ethernet adapters B_ETH1 and B_ETH0 are connected to the SCUs in slots 6
and 7 in the MPS respectively through the backplane.
The two external Ethernet adapters F_ETH1 and F_ETH0 of the OMUc board are connected to
the OM terminals through network equipment such as a hub, LAN switch, or router. In this way,
the OMU fulfills the communication between the BSC6900 and the OM terminals.
As shown in Figure 3-7, the two external Ethernet ports of the OMUc board are connected to
the two LAN switches respectively, which improves network reliability. In this network
topology, the Ethernet ports connecting F_EH0, F_ETH1, and LAN switches must be in the
same Intranet as the two Ethernet ports on the LAN switches connecting F_ETH0 and F_ETH1.
Moreover, the Ethernet adapter marked in blue in Figure 3-7 must be enabled with the Spanning
Tree Protocol (STP) function to prevent network storms.
The two internal Ethernet adapters ETH4-SCU7 and ETH5-SCU6 of the OMUa board are
connected to the SCUs in slots 7 and 6 of the MPS respectively through the backplane.
The two external Ethernet adapters ETH0 and ETH 1 of the OMUa board are connected to the
OM terminals through network equipment such as a hub, LAN switch, or router. In this way,
the OMU fulfills the communication between the BSC6900 and the OM terminals.
The ETH3-UPDATE of the active OMUa board is connected to the ETH3-UPDATE of the
standby OMUa board through the backplane to fulfill the data synchronization and the update
of OMU software between the active and standby OMUs.
As shown in Figure 3-11, the two external Ethernet ports of the active and standby OMUs are
connected to the two LAN switches respectively, which improves network reliability. In this
network topology, the Ethernet ports connecting the ETH0, ETH1, and LAN switches must be
in the same Intranet as the two Ethernet ports on the LAN switches connecting ETH0 and ETH1.
Moreover, the Ethernet adapter marked in blue in Figure 3-11 must be enabled with the STP
function to prevent network storms.
The two internal Ethernet adapters B_ETH0 and B_ETH1 of the OMUc board are connected to
the SCUs in slots 7 and 6 in the MPS respectively through the backplane.
The two external Ethernet adapters F_ETH0 and F_ETH1 of the OMUc board are connected to
the OM terminals through network equipment such as a hub, LAN switch, or router. In this way,
the OMU fulfills the communication between the BSC6900 and the OM terminals.
The B_UPDATE0 of the active OMUc board is connected to the B_UPDATE0 of the standby
OMUc board through the backplane. This fulfills data synchronization and update of OMU
software between the active and standby OMUs.
As shown in Figure 3-12, the two external Ethernet ports of the active and standby OMUs are
connected to the two LAN switches respectively, which improves network reliability. In this
network topology, the Ethernet ports connecting F_EH0, F_ETH1, and LAN switches must be
in the same Intranet as the two Ethernet ports on the LAN switches connecting F_ETH0 and
F_ETH1. Moreover, the Ethernet adapter marked in blue in Figure 3-12 must be enabled with
the STP function to prevent network storms.
The two internal Ethernet adapters of the OMU are connected to the SCUs in slots 7 and 6 in
the MPS respectively through the backplane.
The two external Ethernet adapters of the OMU are connected to the OM terminals through
network equipment such as a hub, LAN switch, or router. In this way, the OMU fulfills the
communication between the BSC6900 and the OM terminals.
The B_UPDATE1 of the active OMUc board is connected to the ETH3-UPDATE of the standby
OMUa board through the backplane. This fulfills data synchronization and update of OMU
software between the active and standby OMUs.
As shown in Figure 3-13, the two external Ethernet ports of the active and standby OMUs are
connected to the two LAN switches respectively, which improves network reliability. In this
network topology, the Ethernet ports connecting external Ethernet adapters and LAN switches
must be in the same Intranet as the two Ethernet ports on the LAN switches connecting external
Ethernet adapters. Moreover, the Ethernet adapter marked in blue in Figure 3-12 must be enabled
with the STP function to prevent network storms.
After the OMU version upgrade, the standby workspaces of the active and standby OMUs store
the files of the old version. In this case, version rollback can be performed as required.
The working principles of the OMU active/standby workspaces in the case of version rollback
are as follows:
1. A switchover is performed between the active and standby workspaces of the active OMU.
The running version of the active OMU is rolled back to the source version.
2. The active OMU runs the source version.
3. A switchover is performed between the active and standby workspaces of the standby OMU
to ensure that the versions of the workspaces are consistent with those of the active OMU.
4. The OMU version rollback is complete.
Heartbeat refers to response messages between active and standby OMUs. In active/standby
OMU mode, active and standby OMUs send heartbeat messages to each other to ensure that they
work properly and the network connection is normal.
The principle of heartbeat detection is: The active and standby OMUs send status messages to
each other and check the messages. Based on the active/standby policy, they determine whether
they are operating as the active or standby OMU. In addition, they decide whether to perform a
switchover after negotiation. If an OMU cannot receive any messages from the other for a period
of time, the uncommunicative OMU is considered faulty. If the active OMU is faulty, a
switchover is triggered.
Data Synchronization
The OMU data is dynamic, which changes when the BSC6900 is working. After the standby
OMU starts, the active OMU data is fully synchronized, and the increments are synchronized.
This ensures that the OMU can work normally after a switchover.
File Synchronization
The synchronization between active OMU files and standby OMU files is mainly applicable to
dynamic files. The dynamic files include the license file, board program, BOOTROM file, DSP
file, patch file, and performance measurement file. The software management module on the
standby OMU regularly checks the active OMU files and synchronizes the dynamic files on the
active OMU with those on the standby OMU. This ensures that the files on the active and standby
OMUs are the same.
Time Synchronization
Time synchronization means that the sntp module on the standby OMU regularly synchronizes
the time with the sntp module on the active OMU. This ensures that the time on the active and
standby OMUs is the same.
NOTE
Operation and maintenance can be performed on the LMT only after a switchover is successfully completed.
Manual Switchover
If OMUs work in active/standby mode and the data synchronization between the active and
standby OMUs is normal, you can manually switch over the OMUs as required. For example,
you need to manually switch over OMUs for software and hardware upgrade or fault
rectification. To manually switch over the OMUs, run the SWP OMU command or use the
LMT. For detailed operations, see Switching Over the BSC Boards in the BSC6900 UMTS LMT
User Guide. After the manual switchover, the original standby OMU becomes the active OMU,
and the original active OMU becomes the standby OMU.
Manual switchover can only be performed when the active and standby OMUs work properly.
In addition, at least one of the following conditions must be met:
l The DSP OMU command output shows that the value for Data-sync state is Data
synchronization is successful.
l The DSP OMU command output shows that the version of the active OMU applications
is different from that of the standby OMU applications.
l The ALM-20701 OMU Failure Switchover persists after a fault-triggered OMU switchover
is performed.
CAUTION
Before performing the manual switchover, do not perform an operation that may change the data
in the database. For example, do not modify configuration data or user information.
Fault-Triggered Switchover
When the active and standby OMUs operate properly, the active OMU maintains the
BSC6900 and the standby OMU monitors the active OMU. If a fault occurs on the active OMU
and persists for more than 5 minutes, the standby OMU automatically becomes active. After the
fault is rectified, the original active OMU becomes standby. If the fault is rectified within 5
minutes, the switchover does not occur.
After the fault-triggered switchover, the OMU automatically reports the alarm ALM-20701
OMU Failure Switchover and initiates a CRC. If the host data is consistent with the OMU data,
the alarm is automatically cleared. If the host data is inconsistent with the OMU data, the alarm
persists.
NOTE
If the DSP OMU command output shows that the values for Internal network link state, External network
state, and Backup network link state are all Breakdown, then the active OMU is faulty.
Failover
When the active OMU runs longer than the failover interval, a failover occurs. To reduce the
impact on the services, the failover usually occurs between 03: 00 and 05: 00.
You can run the SET ASWPARA command to set whether the failover between the active and
standby OMUs is allowed. You can also run this command to set the failover interval.
NOTE
Self-Healing Switchover
Self-healing switchover is a method of self-healing for the OMUs.
The active OMU performs a self-healing switchover when any of the following conditions
occurs:
l The hard disk capacity of the active OMU overflows if the remaining space is smaller than
200 MB.
l An abnormality occurred on the active OMU for 10 times within 30 minutes.
l No Ethernet cable is connected to the external Ethernet ports on the active OMU.
l The virtual internal or external IP address of the active OMU is lost for more than 3 minutes.
l The standby OMU detects that the active OMU is restarted abnormally three times within
24 hours.
l The connection between the active OMU and SCU is interrupted and the connection
between the standby OMU and SCU is normal.
This section describes how to install software and perform operation and maintenance for the
OMU when a BSC6900 is deployed.
NOTE
In the scenario of deploying the BSC6900, the physical entity to carry the OMU is the OMUa or OMUc board
(recommended). For the policy of replacing a faulty OMUa or OMUc board, see Replacing an OMU Board in
the BSC6900 UMTSSite Maintenance Guide.
l Operating System
The DOPRA Linux operating system is used.
l OMU Applications
The OMU applications run on the bottom-level operating system and provide various
service processes.
Scenario Overview
Figure 4-2 shows how to install OMU applications when deploying a BSC6900.
l Commissioning phase
Determine whether to reinstall OMU applications based on the status and version of the
current OMU applications and configure the correct OMU IP address for communication
between the LMT and BSC6900 operation and maintenance network.
l Maintenance phase
If OMU applications cannot work properly during the maintenance phase, select one of the
following ways to reinstall the OMU applications:
1. Use the USB flash drive. With this method, the OMU operating system and
applications will be reinstalled. For details, see 4.2.2 Optional: Installing the
Operating System and OMU Applications.
2. Use the OMU applications installation file in the version package. If this way is used,
only the OMU applications will be reinstalled. For details, see 4.2.3 Optional:
Installing the OMU Applications.
4.1 Installing the OMU Applications in Field Commissioning
The OMU operating system is installed before the OMU is delivered. However, it is uncertain
whether the OMU applications are installed and whether the versions of the OMU applications
are correct. Before you use the OMU for the first time, you need to check whether the OMU
applications are installed as well as their version information and configure the IP addresses,
subnet mask, and OMU name onsite according to the IP address planning principle.
4.2 Reinstalling Software Onsite
If an OMUa/OMUc board is damaged onsite, replace it. If the operating system fails, reinstall
it along with the OMU applications.
4.3 Operating and Maintaining the OMU
This section describes how to perform operation and maintenance on the OMU after OMU
applications are installed. To perform this task, log in to the OMU remotely or run MML
commands.
4.4 Appendix: OMU-Related Software
The OMU-related software, including the psftp software and PuTTY software, is used to install
the OMU applications and perform operation and maintenance on the OMU.
4.5 Appendix: OMU-Related Information Tables
This section describes the tables in which the OMU information is recorded during routine
operation and maintenance on the OMU.
4.1.1 Setting the Link Mode of the External OMU Ethernet Adapter
This section describes how to set the link mode of the external OMU Ethernet adapters so that
it is the same as that of the LAN switch.
Prerequisites
The link mode, duplex mode, and rate of the LAN switch have been acquired.
Context
There are two link modes of the LAN switch: force mode and auto-negotiation mode. The link
mode of the OMU external Ethernet adapter must be consistent with that of the LAN switch.
If the link mode of the external Ethernet adapters of the OMU is inconsistent with that of the
LAN switch, the network may be interrupted. If the link mode of the LAN switch is specified,
the link mode of the external Ethernet adapter of the OMU should also be specified.
If active and standby OMUs are configured, perform the following steps on both the active and
standby OMUs:
NOTE
l The following procedure assumes that the link mode of the external Ethernet adapter is force mode and
the adapter works at 100 Mbit/s in full duplex mode.
l The following procedure assumes that version_a is the active workspace of the OMU. To query the
active workspace of the current OMU, run the LST OMUAREA command.
Procedure
Step 1 Log in to the target OMU by referring to Logging In to the OMU.
Step 2 Enter the /etc/rc.d/omud stop command and press Enter to stop the omud.
Step 3 Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the directory
where the omutool program is saved.
Step 4 Run the ./omutool duplexmode 100 full off command.
NOTE
Querying the link mode of the external OMU network adapters, see 4.3.4 Querying the Link Mode of
the External OMU Network Adapters.
The fields in the ./omutool duplexmode 100 full off command are described as follows:
l 100 indicates that the rate of the Ethernet adapter is 100 Mbit/s. The value of this field can be 10, 100,
or 1000.
l full indicates that the Ethernet adapter works in full duplex mode. The value of this field can be full
or half.
l off indicates that the link mode of the Ethernet adapter is force mode. The value of this field can be off
or on. When the value of this field is on, the link mode is auto-negotiation mode.
Step 5 Enter the /etc/rc.d/omud start command and press Enter to start the omud.
----End
Prerequisites
The OMU is connected to the local PC by using the commissioning Ethernet port.
Context
NOTE
In a newly deployed site, the active workspace of the delivered OMU is version_a.
Procedure
Step 1 Connect the PC to the ETH2 debugging port on the OMU board by using an Ethernet cable.
Step 2 Set the IP address of the PC to be on the same network segment with the ETH2 port. The initial
IP address of the ETH2 port is 192.168.6.50 or 192.168.6.60, the subnet mask is 255.255.255.0.
Step 3 Log in to the OMU by referring to Logging In to the OMU in theBSC6900 UMTS OMU
Administration Guide.
Step 4 Check whether the link mode of the external OMU Ethernet Adapter is consistent with that of
LAN Switch by referring to theBSC6900 UMTS OMU Administration Guide for Setting the
Link Mode of the External OMU Ethernet Adapters about Procedure.
Step 5 Run the /etc/rc.d/omud status command to check the running status of the OMU process.
If... Then...
If... Then...
The information displayed is No such file or 1. Install the OMU application in the active
directory workspace by referring to the BSC6900
UMTS OMU Administration Guide for
Installing the OMU Applications in the
Active Workspace about Procedure.
2. Perform steps Step 7 through Step 10.
3. Perform steps Step 14 through Step 16.
Step 6 Run the cd /mbsc/upgrade command to switch to the OMU installation directory, and then run
the ls command to query the current version of the OMU application.
If... Then...
The version of the OMU application is the Perform steps Step 7 through Step 16.
same as required by the operator
Step 7 Run the cd /mbsc/bam/version_a/bin/bam command to switch to the directory where the
omutool program locates.
NOTE
To view the help information of the omutool, run the ./omutool -h command.
Step 8 Change the external fixed IP address and the subnet mask according to the plan of the operator.
Run the ./omutool extercard The external fixed IP address The subnet mask The gateway IP
address (Optional) command to change the external fixed IP address and the subnet mask. For
example, you can type the following command and then press Enter.
./omutool extercard 10.161.10.100 255.255.255.0
NOTE
l The following two ways show how to change an external fixed IP address if changing a gateway IP
address is required at the same time.
l Method 1: Run the ./omutool extercard The external fixed IP address The subnet mask (The
gateway IP address) command and then click the Enter to change the external fixed IP address
and the gateway IP address at the same time. For example:
./omutool extercard 10.161.10.100 255.255.255.0 10.161.10.1
l Method 2: Run the ./omutool gateway The external IP address command and then press Enter to
change the gateway IP address separately. For example:
./omutool gateway 10.161.10.1
l After the external fixed IP address is changed, the OMU can be connected to the OM network of the
operator by the ETH0 or ETH1 port. In this case, the commissioning task can be performed in a
centralized manner.
Step 9 Change the external virtual IP address and the subnet mask of the active and standby OMUs
according to the plan. Ensure that the external virtual IP address is on the same network segment
as the external fixed IP address.
Run the ./omutool extervip The external virtual IP address The subnet mask command to change
the external virtual IP address and the subnet mask. For example, you can type the following
command and then press Enter.
./omutool extervip 10.161.10.102 255.255.255.0
NOTE
When the external fixed or virtual IP address is being changed, a window is displayed to remind users to
check whether the external virtual or fixed IP address and the gateway IP address need to be changed. In
this way, users can make necessary changes to ensure the three IP addresses are in the same segment.
Step 10 Check whether the internal fixed IP address, internal virtual IP address, backup channel IP
address, and debugging IP address of active and standby OMUs are on the same network segment
as the network of the operator.
If... Then...
If... Then...
All IP addresses are not on the Change the backup channel IP addresses of the standby
same network segment as the OMU.
network of the operator l If OMUa boards are used, run the ./omutool
backupcard The IP address command. For example,
you can type the following command and then press
Enter.
./omutool backupcard 192.168.3.60
Step 11 Run the ./omutool hostname OMU name command to change the name of the OMU.
For example, you can type the following command and then press Enter to change the OMU
name to omu_123: ./omutool hostname omu_123.
NOTE
The OMU name cannot contain control characters, spaces, or any of the following characters: / \ [ ] ( ) ' : | < >
+ = ; , ? , and the length of the OMU name rangs from 1 to 62 characters.
Step 12 Set the working mode of the OMU based on the number of configured OMU boards.
l If only one OMU board is configured, run the ./omutool dualmode single command to set
the working mode to the single-server mode.
l If two OMU boards (active and standby OMU boards) are configured, run the ./omutool
dualmode dual command to set the working mode to the dual-server mode.
Step 13 Run the cd /mbsc/bam/common command to switch to the directory where the reg.ini file
locates.
1. Run the vi reg.ini command to open the reg.ini file.
2. Move the cursor with arrow keys and then set mlangflag to CHS or ENG to change the
language used in the OMU.
3. Move the cursor with arrow keys and then set runmode to UO to change the service mode
of the OMU.
4. Move the cursor with arrow keys and then set officename to change the office name.
5. Press Esc, input : and then wq, and press Enter. The reg.ini file is changed.
NOTE
l To set the preceding information, move the cursor to the beginning character of the information
to be modified, press X to delete the existing information, then press A, and you can input the
new information. After you modify an information item, press Esc and then move the cursor to
modify another information item.
l To quit without saving your modification, perform either of the following operations:
l Operation 1: Press Esc, type : and then q!. Press Enter.
l Operation 2: Directly close the PuTTY window. If you perform this operation, a prompt is
displayed when you edit the reg.ini file using the vi command next time. In this case, type
D and then press Enter to open the reg.ini file.
NOTE
You can also copy the reg.ini file to the local PC to change the previous information by using the psftp
software.
1. Obtain the psftp software and open it locally by double-clicking the application icon.
2. Input cd /mbsc/bam/common in the psftp command line window to switch to the directory where the
reg.ini file locates.
3. Input get reg.ini in the psftp command line window to transfer the reg.ini file from the OMU to the
directory where the psftp software locates.
4. Open the reg.ini file with Notepad, set mlangflag to CHS or ENG, set runmode to UO, and then set
officename.
5. Input put reg.ini in the psftp command line window to upload the modified reg.ini file from the local
PC to the OMU.
Step 14 Run the /etc/rc.d/omud start command to start the OMU application.
Step 15 Run the ps -afx command to check the operating status of the OMU.
The OMU is operating properly if all OMU processes exist in the OMU active workspace
directory/mbsc/bam/version_a/bin/bam/monitor.
NOTE
If some of the processes do not exist, run the /etc/rc.d/omud restart command to restart the OMU server,
and then check again whether the processes exist. If some of them still do not exist, uninstall the OMU
application and then install the OMU application in the active workspace by referring to theBSC6900
UMTS OMU Administration Guide for Uninstalling the OMU Applications and Installing the OMU
Applications in the Active Workspace about Procedure.
Step 16 Run the exit command to terminate the PuTTY software to log out of the OMU.
----End
Hard disk 1 80 GB 10 GB
CD drive 1 - -
USB 1 - -
installati
on drive
Check that Microsoft .NET Framework 2.0 or later has been installed on the portable computer.
NOTE
To check whether Microsoft .NET Framework 2.0 or later has been installed, choose Start > Settings >
Control Panel > Add or Remove Programs to view the components installed on the portable computer.
If Microsoft .NET Framework 2.0 or later has not been installed on the portable computer,
rundotnetfx2.0.exe under software package for preparing a USB storage device used for switching
the OMU operating system to Dopra Linux\tools.
NOTE
Contact Huawei engineers who can obtain the installation package and tool by performing the following
operation:
l Log in to http://support.huawei.com/support/ and choose Software Center > Version Software >
Wireless Product Line > SingleRAN > MBSC > BSC6900 > BSC6900 Product Version > BSC6900
Software Version.
l Click Software Version VER to obtain the BSC6900 version installation package.
l Log in to http://support.huawei.com/support/ and choose Software Center > Version Software >
Wireless Product Line > SingleRAN > SRAN O&M tools to obtain the Dopra_Linux_USB Disks.
Context
l When reinstalling the OMU applications, re-import the OMU configuration data. You must
back up the OMU data before reinstalling the OMU applications and restore the OMU data
after the installation. For details, see Backing Up the System Data and Restoring System
Data.
l If the OMU data cannot be backed up because the OMU applications cannot work properly,
obtain the latest backup data for restoration.
Prerequisites
l The capacity of the USB storage device is at least 2 GB. If the BSC6900 is configured with
active and standby OMUs, two USB storage devices are required.
l The USB storage device is inserted in a functional USB port on the portable PC.
l The portable PC has read and write rights on the USB port.
l You have obtained the planned OMU IP addresses and the OMU name and have recorded
them in Configuration Information for Preparing USB Storage Device.
Context
CAUTION
This function is for quickly restoring data and rectifying faults. During the process, data is
encrypted against the risk of information leakage.
The USB storage device can be used to install the OMU operating system or install both the
OMU operating system and the OMU applications. The installation made depends on whether
the OMU version installation package or patch installation package has been installed when the
USB storage device is prepared.
The USB storage device is used in the following scenarios:
l Initially installing the OMU operating system and applications
l Restoring the corrupted OMU operating system
When the USB storage device is used to perform operations on the OMU, the OMU data is
affected as follows:
l If the Operate Type of the USB storage device is Install, the hard disk drive is formatted
and the OMU data is erased. Therefore, back up the OMU data before installing the OMU
operating system by using the USB storage device.
After the OMU operating system is installed, user security settings (including user
passwords and security policies) are restored to the factory settings.
For details about the password for the root user, see section Checklist for the OMU
Board Software Factory Settings.
For details about security policies for the root user password, see section Dopra Linux
OS Security in the Dopra_Linux_USB Disks software package.
l If the Operate Type of the USB storage device is Recover, then only the OMU operating
system is restored. The OMU applications and data are lost.
NOTE
The modified and deleted system files cannot be restored using the USB storage device. The USB storage device
applies only to the following scenarios:
1. The OMU operating system cannot start.
2. When the OMU operating system starts, a message is displayed that prompts you to restore the file system.
3. After the OMU operating system starts, a Kernel panic error is displayed that indicates a failure in loading
rootfs.
If the OMU operating system cannot be restored using the USB storage device, you are advised to reinstall the
OMU operating system using the USB storage device.
Before preparing a USB storage device, verify the device by referring to DOPRA Linux USB
Disk Certificate Guide in the directory where the Dopra Linux USB storage device is saved. If
the USB storage device is not usable, replace it. The Netac U208 (2 GB), Kingston and Sandisk
USB storage devices are recommended.
The duration for preparing a USB storage device varies based the bandwidth of the network
from the PC to the equipment room, the USB protocol, and the PC performance. The duration
listed in Table 4-2 refers to the duration for preparing a USB storage device in compliance with
the USB2.0 protocol. The duration for preparing a USB storage device in compliance with the
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.
Prepare a USB storage device. The duration varies based on the bandwidth
of the network from the PC to the equipment
room.
l If the network bandwidth is 1 Mbit/s or
higher:
and an independent OMU is
configured, the duration is 15 to 30
minutes.
and active and standby OMUs are
configured, the duration is 30 to 50
minutes.
l If the network bandwidth is 512 kbit/s:
and an independent OMU is
configured, the duration is 25 to 50
minutes.
and active and standby OMUs are
configured, the duration is 50 to 90
minutes.
NOTE
The following operations assume that you are preparing a USB storage device for active and standby OMUs.
Differences are specified for preparing USB storage devices for active and standby OMUs and for an independent
OMU.
Procedure
l Preparing the USB storage device for initially installing the OMU operating system and
applications
1. Double-click U_creator_eng.exe to begin installing a Dopra Linux operating system
on the USB storage device, as shown in Figure 4-3.
2. Right-click NE List in the left pane of the window shown in Figure 4-3 and choose
Add NE from the shortcut menu. A dialog box is displayed, as shown in Figure
4-4.
3. Specify NE Name, set Operate type to Install, and select Install OMU Then click
OK. An NE is added.
NOTE
l To initially install OMU applications, select Install OMU and specify External Virtual IP
Address of the NE to be added.
l The NE name, used to identify an NE, can include only letters, numerals, dashes ("-"), and
underscores ("_").
l The NE name and the virtual external IP address can be changed only after you delete the NE
and then add it again.
l To prepare multiple USB storage devices, you are advised to prepare and label the USB storage
devices one by one.
4. Double-click the added NE in the left pane. The window is refreshed, as shown in
Figure 4-5.
NOTE
l The IP addresses shown in Figure 4-5 are default IP addresses of the Dopra Linux tool. Change
the IP addresses as required. For details about the principles of changing the IP addresses, see
3.2 OMU IP Address Plan.
l Select the link mode for external Ethernet adapters listed in Figure 4-5 as required. Ensure that
the link mode for external Ethernet adapters is consistent with that for the onsite LAN switch.
Table 4-3 lists the mapping between the queried link mode for external Ethernet adapters and
that selected in Figure 4-5.
l If Install OMU is not selected in Step 3, only the names of the active and standby OMUs and
IP addresses are displayed in Figure 4-5.
l In independent OMU mode, only the active OMU configuration is effective, whereas the standby
OMU configuration is ineffective.
5. After all the information is automatically obtained, check whether the information is
correct and enter any missing information.
NOTE
l If a version or baseline patch is to be installed, select the V**R**C** directory for the version
installation package or the V**R**C**SPCX00 directory for the baseline patch installation
package.
l If a non-baseline patch is to be installed, select the V**R**C**SPCXYZ or
V**R**C**SPHXYZ directory for the patch installation package.
6. Check that all the information is correct and click OK. In the displayed dialog box,
check the directory where the USB storage device is located and start preparing a USB
storage device.
7. Perform operations by following the instructions until the system displays a message
that reads Succeed to create USB drive of OMU installation. Click Finish to finish
preparing the USB storage device.
NOTE
l If the system asks for your confirmation during preparation of the USB storage device, insert or
remove the USB storage device.
l If an independent OMU is configured, skip the steps for preparing the standby OMU USB storage
device.
l Preparing the USB storage device for restoring the OMU operating system
1. Double-click U_creator_eng.exe to begin installing a Dopra Linux operating system
on the USB storage device, as shown in Figure 4-3.
2. Right-click NE List in the left pane of the window shown in Figure 4-3 and choose
Add NE. A dialog box is displayed, as shown in Figure 4-6.
3. Specify NE Name, and set Operate type to Restore. Then click OK. An NE is added.
NOTE
l The NE name, used to identify an NE, can include only letters, numerals, dashes ("-"), and
underscores ("_").
l An NE name can be changed only after you delete the NE and then add it again.
l To prepare multiple USB storage devices, you are advised to prepare and label the USB storage
devices one by one.
4. Double-click the added NE in the left pane. The window is refreshed, as shown in
Figure 4-7.
NOTE
l The IP addresses shown in Figure 4-7 are default IP addresses of the Dopra Linux tool. Change
the IP addresses as required. For details about the principles of changing the IP addresses, see
3.2 OMU IP Address Plan.
l Select the link mode for external Ethernet adapters listed in Figure 4-7 as required. Ensure that
the link mode for external Ethernet adapters is consistent with that for the onsite LAN switch.
l In independent OMU mode, only the active OMU configuration is effective, whereas the standby
OMU configuration is ineffective.
5. After all the information is automatically obtained, check whether the information is
correct and type the required information.
6. Check that all the information is correct and click OK. In the displayed dialog box,
check that the directory where the USB storage device is located and start preparing
a USB storage device.
7. Perform operations by following the instructions till the system displays a message
that reads Succeed to create USB drive of OMU installation. Click Finish to finish
preparing the USB storage device.
NOTE
l If the system asks for your confirmation during preparation of the USB storage device, insert or
remove the USB storage device.
l If an independent OMU is configured, skip the steps for preparing the standby OMU USB storage
device.
----End
Prerequisites
l The USB flash drive is prepared. For details, see Preparing a USB Storage Device.
l There are USB ports available on the OMU board panel.
NOTE
The USB flash drive with an indicator is inserted into the USB port. If the indicator is on, then the USB
port is available.
Procedure
Step 1 Insert the USB flash drive into any of the USB ports on the OMUa or OMUc board panel.
Step 2 Remove and then reinstall the OMUa or OMUc board to reset the OMU.
NOTE
Press and hold the two locking buttons, flip the ejector levers out on the OMU board panel to unlock them,
and rotate them outward. The OMU board is separated from the backplane. Remove the OMU board after
the OFFLINE LED flashes fast and then is steady blue.
Step 3 Wait 1 to 2 minutes and then use the USB flash drive to install the OMU operating system. Check
the status of indicators on the OMU board panel to determine whether the OMU operating system
is installed successfully.
l If only the operating system is to be installed on the OMU, check the indicator status. See
Table 4-4.
l If the OMU operating system is to be restored, check the indicator status. See Table 4-5.
l If the operating system and applications are to be installed on the OMU, check the indicator
status. See Table 4-6.
NOTE
If the status of the indicators differs from this, the OMU cannot identify the USB flash drive. When this occurs,
prepare another USB flash drive. Alternatively, copy the data in the original USB flash drive to a new USB flash
drive, and then reinstall the OMU operating system.
For information about how much time will be consumed during the OMU operating system installation, see
Table 4-2 in Preparing a USB Storage Device.
Table 4-4 Status of the indicators on the OMUa or OMUc board panel during the OMU operating
system installation
Board Installation Procedure Successful Failed Installation
Installation
OMUc l The RUN indicator l The RUN indicator l The RUN indicator is
blinks. blinks. off.
l The ALM indicator l The ALM indicator is l The ALM indicator
blinks. off. blinks.
l The ACT indicator l The ACT indicator is l The ACT indicator is
blinks. off. off.
l The OFFLINE l The OFFLINE l The OFFLINE
indicator is off. indicator blinks. indicator blinks.
Table 4-5 Status of the indicators on the OMUa or OMUc board panel during the OMU operating
system restore
Board Installation Procedure Successful Failed Installation
Installation
OMUc l The RUN indicator l The RUN indicator l The RUN indicator
blinks. blinks. blinks.
l The ALM indicator l The ALM indicator is l The ALM indicator
blinks. steady on or off. blinks.
l The ACT indicator l The ACT indicator is l The ACT indicator is
blinks. steady on or off. off.
l The OFFLINE l The OFFLINE l The OFFLINE
indicator blinks. indicator is off. indicator is off.
Table 4-6 Status of indicators on the OMUa or OMUc board panel during the OMU operating
system and OMU applications installation
Board Installation Procedure Successful Failed Installation
Installation
OMUc l The RUN indicator l The RUN indicator l The RUN indicator
blinks. blinks. blinks.
l The ALM indicator l The ALM indicator is l The ALM indicator
blinks. steady on or off. blinks.
l The ACT indicator l The ACT indicator is l The ACT indicator is
blinks. steady on or off. off.
l The OFFLINE l The OFFLINE l The OFFLINE
indicator is off. indicator is off. indicator is off.
CAUTION
l After the OMU operating system is installed successfully, remove the USB flash drive from
the OMU board panel in a timely manner.
l After the OMU operating system is restored using a USB flash drive, the password changes
to the default value.
l If the version of the OMU operating system is V200R003C02SPC090 or later, log in to
the active OMU as the lgnusr user, for whom the initial password is osnormal@123. Do
not log in to the OMU as the root user. After the login succeeds, you can run the su
command to switch to the root user, for whom the initial password is osadmin@123.
l If the version of the OMU operating system is earlier than V200R003C02SPC090, log in
to the active OMU as the root user, for whom the initial password is mbsc@com.
l If you do not know the version of the OMU operating system, try to log in to the active
OMU first as the lgnusr user and then the root user.
----End
Follow-up Procedure
If the OMU operating system fails to be installed, perform the following operations:
1. Prepare a new USB flash drive. For details, see Preparing a USB Storage Device. Then,
reinstall the OMU operating system again.
l If the OMU operating system is installed successfully, no further action is required.
l If the OMU operating system fails to be installed, Contact Huawei Customer Service
Center.
If you use the USB flash drive to restore the OMU operating system, check whether you should
implement the following operations:
l After the OMU operating system is restored, the setting on the original operating system
will become ineffective for the functions of disabling root user remote login. Enable the
function by referring to 6.1 Disabling root user login with SSH.
Context
l When reinstalling the OMU applications, re-import the OMU configuration data. You must
back up the OMU data before reinstalling the OMU applications and restore the OMU data
after the installation. For details, see Backing Up the System Data and Restoring System
Data.
l If the OMU data cannot be backed up because the OMU applications cannot work properly,
obtain the latest backup data for restoration.
l When installing the OMU applications for the first time, the OMU applications can be
installed only on the active workspace of the OMU, and the OMU data does not need to be
backed up.
NOTE
This section uses the version installation package named V900R014C00 as an example to illustrate how to install
the OMU applications.
Procedure
Step 1 Before you install the OMU applications, obtain the following information. For details, see 4.5.1
Information Record Sheet of OMU Software Installation.
l Password of the operating system administrator
l Fixed IP address of the external network, virtual IP address of the external network, and
commissioning IP address of the OMU.
----End
Prerequisites
The PC to be used to log in to the OMU is properly connected.
Procedure
Step 1 Run the SSH terminal, for example, PuTTY, on the PC, and type the IP address of the OMU.
NOTE
l Before starting OMU applications, type the fixed external IP address of the OMU.
l After the OMU applications start, type the fixed or virtual external IP address. The former is preferred.
l If you are performing local commissioning, type the commissioning IP address of the OMU.
l If the PC cannot be connected to the OMU by using either the fixed or virtual external IP address,
connect the PC to the commissioning Ethernet port on the OMU and type the commissioning IP address
of the OMU.
l You are advised to log in to the OMU using the external fixed IP address, external virtual IP
address, and commissioning IP address in sequence.
Step 2 Log in to the OMU as the root user, lgnusr user, or common user.
NOTE
l If the login fails, check whether the Disabling user root remote login function is enabled. If the function
is enabled, log in to the OMU as a common user. For details, see 6.1 Disabling root user login with
SSH.
l Run the LST VER command to query the OMU operating system version and log in to the OMU by using
the corresponding password. For details, see 4.5.2 Checklist for the OMU Software Factory Settings.
l It is recommended that you change the root user password upon your first login and change the password
every three months. If the version of the OMU operating system is
Doprax86DopraLinuxV200R003C02SPC080, change the root user password every 30 days. To query the
OMU operating system version, run the LST VER command.
l If you enter the password incorrectly for three times when logging in to the OMU, the operating system will
be automatically locked for 5 minutes and then unlocked. When the operating system is locked, do not log
in to the OMU.
Step 3 For a common user or lgnusr user, enter su and press Enter. Then, enter the root user password
to switch to a root user account.
----End
Example
The following shows an example of logging in to the OMU as the root user.
omud215 ~ #
The following shows an example of logging in to the OMU as the lgnusr user. The same is for
a common user.
omu ~ $ su
Password:
omu /home/lgnusr #
Prerequisites
l Contact Huawei engineers who can obtain the tool by performing the following operation:
You have obtained the OMU application installation package including the patch
installation package by accessing http://support.huawei.com/support/ and choosing
Software Center > Version Software > Wireless Product Line > Single RAN >
MBSC > BSC6900.
l The psftp has been obtained. For details about the psftp, see 4.4.1 psftp Software.
Context
l The OMU application installation package must be uploaded to the \mbsc\upgrade
directory of the OMU.
l The OMU application installation package must be named after the version number. That
is, after the OMU application installation package is uploaded to the OMU, the directory
of the installation package on OMU is "\mbsc\upgrade\V900R014C00."
l If patches also need to be installed, you must check whether the original patch files exist
in the patch folder in the OMU application installation package before installing the OMU
application. If yes, you must delete the original patch files in the patch folder in the OMU
application installation package and copy the patch installation package (for example, the
V900R01XC0XSPCXXX folder) saved on the local computer.
NOTE
If you need to delete the patch files V900R01XC0XSPCXXX in the patch directory, navigate to the
\mbsc\upgrade\V900R015C00\patch directory and then run rm -r \V900R01XC0XSPCXXX.
l During the uploading process, if the root user cannot log in to the OMU, check with the
equipment room operators to determine whether the 6.1 Disabling root user login with
SSH function has been enabled on the BSC6900. If so, you must log in to the OMU as a
common user, and then continue with the uploading task.
NOTE
As an example, this task uploads the V900R014C00 version installation package to the \mbsc\upgrade directory
of the OMU and downloads version files from http://support.huawei.com/support/ to local drive D.
Procedure
l Logging in to the OMU as a root user and uploading the OMU application installation
package to the OMU
1. Decompress the BSC6900 version installation package to the local D drive.
2. Log in to the OMU as the root user by using the psftp. For details, see 4.4.1 psftp
Software.
3. Run the lcd D:\ command to go to the directory on the local PC where the version
files are saved.
4. Run the ls /mbsc/upgrade command to query whether there is an installation directory
on the OMU.
If the /mbsc/upgrade directory does not exist, go to Step 5.
If the /mbsc/upgrade directory exists, go to Step 6.
5. Run the mkdir /mbsc/upgrade command to create the installation directory on the
OMU.
NOTE
Run the commands mkdir /mbsc and mkdir /mbsc/upgrade in sequence to create the /mbsc/
upgrade directory hierarchically.
6. Run the cd /mbsc/upgrade command to go to the OMU installation directory.
7. Run the put -r V900R014C00 command to upload the OMU application installation
package to the OMU.
NOTE
If the package fails to be uploaded, check whether any file with the same name as the package name
is in use. If there is such a file, release it.
8. After the upload is complete, type the exit command to exist the psftp software.
l Logging in to the OMU as a non-root user and uploading the OMU application installation
package to the OMU
1. Log in to the OMU as a common user and switch to the root user account. For details,
see Logging In to the OMU.
2. Enter the path=`grep xxx /etc/passwd | cut -d:-f 6`; if [ !-d $path ] ; then mkdir -
p $path; chown xxx $path; fi command and press Enter to establish a non-root user
information file directory.
NOTE
Run the commands mkdir /mbsc and mkdir /mbsc/upgrade in sequence to create the /mbsc/
upgrade directory hierarchically.
14. Enter the cp /home/omcuser/V900R014C00 -r /mbsc/upgrade/ command and copy
the version installation package under the /home/omcuser directory to the OMU
installation directory.
15. Enter the exit command and press Enter to log out of PuTTY.
l Log in to the OMU as the lgnusr user and upload the OMU application package to the
OMU.
1. Decompress the BSC6900 version installation package to a local drive D.
2. Log in to the OMU as the lgnusr user by using psftp.
3. Type the lcd D:\ command and press Enter to navigate to the local directory where
version files are saved.
4. Type the cd /home/lgnusr command and press Enter to switch to the directory of the
lgnusr user.
NOTE
The default direcotry of the lgnusr user is /home/lgnusr. The lgnusr user has the read/write
permissions to this directory.
5. Type the put -r commandV900R014C00 and press Enter to upload files.
6. After files are uploaded, enter exit and press Enter to exit psftp.
7. Log in to the OMU as the lgnusr user and switch to the root user account. For details,
see Logging In to the OMU.
8. Type ls /mbsc/upgrade command and press Enter to query whether there is the /
mbsc/upgrade directory on the OMU.
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/V900R014C00-r /mbsc/upgrade/ command to copy the
intallation package under the /home/lgnusr directory to the OMU installation
directory.
11. Enter exit and press Enter to exit PuTTY.
----End
Prerequisites
l Obtained information about OMU software installation.
l Uploaded the OMU application installation package to the OMU.
Context
Run a command to install the install_bam program contained in the BSC6900 version installation
package. Enter the related parameters during the process.
If OMU applications have been pre-installed on active and standby OMU boards, unintall them
before installing the OMU applications of a correct version. To check whether OMU applications
have been pre-installed, do as follows:
1. Log in to the OMU by using the fixed external IP address or commissioning IP address.
For details, see Logging In to the OMU.
2. Enter the cd /etc/rc.d/ command and press Enter to go to the current directory.
3. Enter the ls command and press Enter to check files in the current directory.
l If the omud file is in the directory, OMU applications have been pre-installed. Uninstall
them by following operation steps in Uninstalling the OMU Applications.
l If the omud is not in the directory, OMU applications have not been pre-installed. Install
the OMU applications following the installation procedures.
4. Enter the exit command to close PuTTY.
Procedure
Step 1 Log in to the OMU by using the external fixed IP address or commissioning IP address by
referring to Logging In to the OMU, then navigate to the directory where the OMU application
installation package is saved.
Assume that the OMU application installation package install_bam.sh is saved in /mbsc/
upgrade/V***R***C**/install/setup. Run the following command and press Enter:
cd /mbsc/upgrade/V***R***C**/install/setup
Step 2 Run the chmod +x ./install_bam.sh command to acquire the authority to run the ./
install_bam.sh command.
Step 3 Enter the ./install_bam.sh command and press Enter. The system prompts you to type the
product mode, as shown:
[2011-05-03 10:12:32] software integrality verify begin...
[2011-05-03 10:12:42] software integrality verify end...
NOTE
The software integrity of the OMU applications is checked before they are automatically installed. The OMU
applications can be installed only if the check passes.
Step 4 Enter the product running mode and press Enter. The system prompts you to type the office
name, as shown:
# The name of office
# The name suggest range from 5 to 32 characters.
# The characters suggest be letters, digits, "-"or "_".
Please input a valid office_name :
Step 5 Enter the office name and press Enter. The system prompts you to type the language, as shown:
# The OMU language version. eg: eng/chs
Please input a valid version :
Step 6 Enter the language and press Enter. The system prompts you to type the admin password, as
shown:
# The "admin" user's password of OMU service.
# The password must range from 6 to 32 characters and consist of only letters and
figures.
# Do not forget the password.
# You can change the password later, but this password should be provided first.
Please input a valid admin_password :
NOTE
The admin password is the initial password for the administrator to log in to the LMT.
Step 7 Enter the admin password and press Enter. The system prompts you to type the FTP password,
as shown:
# The ftp user's password of OMU service
# The password must range from 6 to 32(characters) and consist of only letters and
figures.
# Do not forget the password.
# You can change it later, but this password should be provided first.
Please input a valid ftp_password :
NOTE
The FTP password is customized. After the OMU applications are installed, you can access the FTP service
with the FTP password.
Step 8 Enter the FTP password and press Enter. The system prompts you to type the external virtual
IP address, as shown:
NOTE
The external virtual IP address must be located on the same network segment as the external fixed IP
address. The factory setting of the external fixed IP address is 172.121.139.201 (255.255.255.0). After the
OMU applications are installed, you can change the IP addresses and subnet masks of the OMU Ethernet
adapters
Step 9 Enter the external virtual IP address and press Enter. The system prompts you to type the OMU
system type, as shown:
# The OMU system type. eg: Single/Dual
# Single:Install stand-alone system
# Dual:Install dual-OMU system.
The dual-OMU system can effeciently increase the reliability of the OMU system.
Please input a valid install_type :
Step 10 Enter the OMU installation type based on the field configuration and press Enter. Table 4-7
describes the OMU installation types.
Parameter Description
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 Enter Y to install the OMU applications. When the messageInstall OMU succeed! is
displayed, the OMU applications are successfully installed.
Step 13 Record the information about the OMU applications installation in 4.5.1 Information Record
Sheet of OMU Software Installation.
----End
Background
The default installation directory for the OMU applications is /mbsc/bam/. You are not allowed
to change the directory.
Procedure
1. Log in to the OMU by referring to Logging In to the OMU.
2. Type the cd /mbsc/bam command and press Enter to go to the OMU installation directory.
3. Check whether the OMU installation directory is in the same structure as what is shown in
Figure 4-8 and Figure 4-9.
Directory Structure
l Figure 4-8 shows the directory structure of the OMU applications when they are installed
in the active OMU workspace for the first time.
l If the OMU applications are installed on both the active workspace and the standby
workspace, the directory structure is the same as that shown in Figure 4-9. The structures
of the version_a and version_b folders are the same.
NOTE
l Active and standby OMU workspace files are segregated by type into version_a and version_b folders.
l Run the LST OMUAREA command to query the OMU workspaces. If the Workarea flag is
version_a, the version_a folder saves active workspace files.
l Figure 4-8 and Figure 4-9 show the directory structure of the OMU applications.
Figure 4-9 Directory structure of OMU applications on the active and standby workspaces
CAUTION
To prevent a critical impact to the BSC6900, do not delete any files in the installation directory
of the OMU applications.
File Folders
Table 4-8 lists the file folders in the OMU application directory.
common/fam Stores host log files and host files for performance statistics
common/fam/famlogfmt/ Stores files that record basic information about the BTS
btsinfo
common/fam/famlogfmt/ Stores the call history record (CHR) for the packet switched
gphr (PS) domain.
common/log Stores logs of the omud, common logs of the base station,
frequency scanning logs, and site commissioning logs
version_a/bin/bam Stores the program files, configuration files, and patch files
for the OMU. Do not perform any operations on this
directory.
version_a/bin/fam Stores the program files and data files for the host. Do not
perform any operations on this directory.
version_a/ftp/ Stores files about the "configure" process. These files are
ExportCMESyncView used for the synchronization between the NE and the CME
or M2000
version_a/ftp/license Stores the license files that have not been activated
version_a/ftp/oprator_log Stores operation log files and security log files of the
standby OMU
weblmt Stores host files and files recording LMT online help
associated with the LMT
Prerequisites
You have logged in to the OMU by referring to Logging In to the OMU.
Procedure
Step 1 Run the exit command to terminate the PuTTY software.
----End
Prerequisites
The OMU applications are installed. For details, see Installing the OMU Applications in the
Active Workspace.
Procedure
Step 1 Log in to the OMU by referring to Logging In to the OMU.
Step 2 Optional: To query the factory settings of the Ethernet adapters of the OMUa board, type the /
root/eth_alias_omu.sh command and press Enter. The following shows the factory settings of
the Ethernet adapters of the OMUa board.
Step 3 Optional: To query the factory settings of the Ethernet adapters of the OMUc board, type
the ./eth_alias_names.sh command and press Enter. The following shows the factory settings
of the Ethernet adapters of the OMUc board.
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
Procedure
l Method 1
1. Log in to the target OMU by referring to Logging In to the OMU.
2. Enter the /etc/rc.d/omud stop command and press Enter to stop the omud..
3. Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the
directory where the omutool program is saved..
NOTE
[Virtual IP Information]
External virtual ip / mask : 10.141.149.15 / 255.255.254.0
Internal virtual ip / mask : 80.168.3.40 / 255.0.0.0
[Fixed IP Information]
External fixed ip / mask : 10.141.149.14 / 255.255.254.0
Internal fixed ip / mask : 80.168.3.60 / 255.0.0.0
Backup channel ip / mask : 192.168.3.60 / 255.255.255.0
Debugging ip / mask : 192.168.6.60 / 255.255.255.0
[Gateway Information]
Gateway : 10.141.148.1
l Method 2
1. Log in to the target OMU by referring to Logging In to the OMU.
2. Optional: To query the fixed internal IP address, broadcast IP address, and subnet
mask of the OMUa board, type the ifconfig vlan1 command and press Enter. The
following shows an example of the returned information.
NOTE
collisions:0 txqueuelen:0
RX bytes:705095569 (672.4 Mb) TX bytes:16423247 (15.6 Mb)
NOTE
----End
Procedure
Step 1 Log in to the target OMU by referring to Logging In to the OMU.
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.
Information to the right of colon in the Local Address column indicates the occupied OMU port
numbers.
----End
Procedure
Step 1 Logging In to the OMU.
Step 2 Query the logical network adapters corresponding to the external OMU network adapters, as
listed in Table 4-9.
Table 4-9 Querying the logical network adapters corresponding to the external OMU network
adapters
Item Description
NOTE
l The OMUa or OMUb external network adapters are ETH0 and ETH1, respectively. The OMUc external
network adapters are F_ETH0 and F_ETH1, respectively. The objects of this task are the logical
network adapters corresponding to the external OMU network adapters.
l Mapping between physical OMU network adapters and logical network adapters can change. In normal
cases, the logical network adapters corresponding to the external OMUa or OMUb network adapters
are eth4 and eth5, respectively; the logical network adapters corresponding to the external OMUc
network adapters are eth0 and eth1, respectively.
Step 3 Query the effective link mode of the external OMU network adapters. Run the ethtool eth0
command to query the link mode of eth0. Run the ethtool eth1 command to query eth1.
NOTE
l Check Speed, Duplex, and Auto-negotiation. Speed, Duplex, and Auto-negotiation indicate the rate,
duplex mode, and auto-negotiation mode, respectively.
l The following example assumes that the logical network adapters corresponding to the external OMU
network adapters are eth0 and eth1, respectively. The command output is as follows:
----End
Prerequisites
You have logged in to the LMT. For details, see Logging In to and Logging Out of the LMT.
Procedure
Step 1 Run the MML command LST VER to check whether OS type and OS service pack version
are correct.
----End
Context
l It is recommended that you change the root user password upon your first login and change
the password every three months. If the version of the OMU operating system is
Doprax86DopraLinuxV200R003C02SPC080, change the root user password every 30
days. To query the OMU operating system version, run the LST VER command.
l A root user password must contain the combination of the following:
At least one lower-case letter
At least one upper-case letter
At least one digit
At least one special character `~!@#$%^&*()-_=+\|[{}];:'",<.>/? or a space
The root user password must have a minimum length of 8 characters and maximum length
of 127 characters.
Procedure
Step 1 Log in to the OMU by referring to Logging In to the OMU.
Step 2 Run the passwd root command (for example, use root as an example). A message is displayed,
prompting you to type the password, as shown in the:
Changing password for root.
New password:
Step 3 Enter a password and press Enter. The message Retype password: is displayed.
Step 4 Retype the password and press Enter. The message Password changed is displayed, indicating
that the Linux administrator password is successfully changed.
Step 5 Record the new password in the 4.5.1 Information Record Sheet of OMU Software
Installation.
----End
Prerequisites
l The OMU is started normally.
l OMU serial cables are available. For details about the cable information, see OMU serial
cable in BSC6900 UMTS Hardware Description.
l The source and target hard disks are available.
Context
One OMU hard disk serves as the source hard disk, and the other serves as the target hard disk.
Setting RAID 1 on the hard disks synchronizes the data on the source and target hard disks,
improving data security.
l The source hard disk saves backup data and files.
l The target hard disk mirrors the source hard disk.
NOTE
RAID 1 cannot be set on an OMUc board because it is configured with one hard disk.
Procedure
Step 1 Connect the PC to the OMU serial port using the OMU serial port cable.
NOTE
If the OMU serial port cable is not available, the USB and VGA ports of the active OMU can be connected
to an external keyboard and monitor, respectively. Then starts from Step 6 to complete the configuration.
Step 2 On the PC, choose Start > All Programs > Accessories > Communications >
HyperTerminal. The dialog box shown in Figure 4-10 is displayed.
Step 3 Enter the connection name and click OK. The dialog box shown in Figure 4-11 is displayed.
Step 4 Check the connection port and click OK. The dialog box shown in Figure 4-12 is displayed.
NOTE
The parameters for the connection port must be set as shown in Figure 4-12.
Step 5 Check that the parameters for the connection port are set correctly and click OK. The window
shown in Figure 4-13 is displayed.
Option Description
Windows Server 2003 operating system 1. Log in to the target OMU by referring to 5.2.20
Logging In to the OMU.
2. Choose Start > Shutdown, click Restart, and
click OK.
Step 7 After the OMU restarts, press F4 repeatedly until the message "Press Ctrl-C to start
LSI Logic Configuration Utility" is displayed. Then press Ctrl+C. The following
shows examples of the messages displayed.
Step 8 Press Enter. The following shows examples of the messages displayed.
Adapter SAS1064
PCI Slot 00
PCI Address(Bus/Dev/Func) 05:01:00
MPT Firmware Revision 0.11.01.00-IR
SAS Address 500E0FC1:23456775
NVDATA Version 25.09
Status Enabled
Boot Order 0
Boot Support [Enabled Bios & OS]
RAID Properties
SAS Topology
Advanced Adapter Properties
Press the arrow keys to select RAID Properties and press Enter. Check the value of Status to
determine whether the RAID is correct.
l If Status is Optimal, the RAID is working properly.
l If Status is Resyncing, the RAID is synchronizing data.
NOTE
l If this is the first time that the RAID is being set on the OMU, go to Step 13.
l If this is not the first time that the RAID is being set on the OMU, go to Step 9.
Step 9 Select RAID Properties and press Enter. The following shows examples of the results that are
displayed.
Array 1 of 1
Identifier LSILOGICLogical Volume 3000
Type IM
Scan Order 2
Size(MB) 69618
Status Optimal
Manage Array
Slot Device Identifier RAID Hot Drive Pred Size
Num Disk Spr Status Fail (MB)
0 FUJITSU MAY2073rc D109 [Yes] [No] Primary --- 69618
1 FUJITSU MAY2073rc D109 [Yes] [No] Secondary --- 69618
Step 10 Select Manage Array and press Enter. The following shows examples of the results that are
displayed.
Step 11 Select Delete Array and press Enter. The following shows examples of the results that are
displayed.
Step 12 Select Y. The following shows examples of the results that are displayed.
Adapter SAS1064
PCI Slot 00
PCI Address(Bus/Dev/Func) 05:01:00
MPT Firmware Revision 0.11.01.00-IR
SAS Address 500E0FC1:23456775
NVDATA Version 25.09
Status Enabled
Boot Order 0
Boot Support [Enabled Bios & OS]
RAID Properties
SAS Topology
Advanced Adapter Properties
Step 13 Select RAID Properties and press Enter. The following shows examples of the results that are
displayed.
Step 14 Select Create IM Volume and press Enter. The following shows examples of the results that
are displayed.
Array Type:IM
Array Size(MB): -------
CAUTION
Select the source and target hard disks with caution because the data on the source hard disk can
be lost.
Step 15 Set RAID Disk to No, move the cursor to the value for RAID Disk of the source hard disk, and
press Space. The following show examples of the results that are displayed.
l If you press M, the data on the source hard disk is saved. The target hard disk copies the data
from the source disk.
l If you press D, the data is deleted from the source hard disk and a new RAID is created.
The value for RAID Disk is Yes, and the value for Drive Status is Primary.
Step 17 Select the target hard disk and press Space. An alarm is generated, as shown in the following:
WARNING! Data was found on the selected disk,this data will be lost when the array
is created!
Choose Discard configuration or Cancel Exit on the next screen to abort.
The value for RAID Disk is Yes, and the value for Drive Status is Secondary.
Step 19 Press C. The following shows the results that are displayed.
Step 20 Select Save changes then exit this menu and press Enter. The screen is refreshed, as shown
in Step 12.
Step 21 Select RAID Properties shown in Step 12 and press Enter. The following shows examples of
the results that are displayed.
Array 1 of 1
Identifier LSILOGICLogical Volume 3000
Type 1M
Scan Order 0
Size(MB) 69618
Status 2% Syncd
Manager Array
Slot Device Identifier RAID Hot Drive Pred Size
Num Disk Spr Status Fail (MB)
0 FUJITSU MAY2073rc D109 [Yes] [No] Primary --- 69618
1 FUJITSU MAY2073rc D109 [Yes] [No] Secondary --- 69618
Step 22 Check that the RAID 1 is set correctly, and then press Esc repeatedly until the following
messages are displayed:
Step 23 Select Exit the Configuration Utility and Reboot and press Enter. RAID 1 is successfully set
on the OMU hard disks and the OMU restarts.
----End
Prerequisites
You have logged in to the LMT. For details, see Logging In to and Logging Out of the LMT.
Procedure
Step 1 Run the MML command DSP OMUSRV to query the available space of the partitions on the
OMU hard disk.
l If the available space of any partition on the OMU hard disk is less than 20%, perform the
following operations to clean up the disk:
1. Back up the files on the partition that need to be saved to a hard disk by referring to
Transferring OMU Files to a Local PC.
2. Log in to the target OMU by referring to Logging In to the OMU.
3. Run the cd target directory command to navigate to the directory where the files to be
deleted are saved.
4. Run the rm file name or rm -r folder name command to delete the unnecessary files.
l If the available space of each partition is at least 20%, no further action is required.
----End
Prerequisites
l The firewall on the portable PC is disabled.
l OMU applications are started.
Context
There are two methods for transferring files on the OMU:
l Using the file management function on the LMT
l Running commands
get Upload files from the OMU get x (x indicates the file
to a local PC. name)
NOTE
The following steps use downloading the 123.xml file from the OMU to the local D drive as an example.
Procedure
l Downloading the 123.xml file on the OMU to the local D drive using the file management
function on the LMT
1. Enable the file management function on the LMT. For details, see File Manager in
BSC6900 UMTS LMT User Guide.
2. Select the 123.xml file in the target directory and click Download.
l Downloading the 123.xml file on the OMU to the local D drive using commands
1. On the local PC, choose Start > Run, enter cmd, and click OK.
2. Type the d: command and press Enter to go to drive D.
3. Enter the ftp IP address command to connect the local PC to the OMU, where IP
address indicates the virtual external or commissioning IP address of the OMU.
4. Enter the user name and password of the FTP. The connection between the local PC
and the OMU is established after the certification passes.
NOTE
The FTP user name is fixed to be FtpUsr. Its password is mbsc@com or will be set during the OMU
application installation. For details, see Records of the OMU Application Installation
Information.
5. Go to the directory where the 123.xml file is saved by referring to commonly used
FTP commands.
6. Transfer the 123.xml file.
Command Description
Run the get 123.xml command. Upload the 123.xml file from the OMU
to the local D drive.
Run the put 123.xml command. Download the 123.xml file from the
local D drive to the OMU.
7. After the file transfer is complete, run the quit command to disconnect the FTP.
----End
Example
The following is an example for downloading the 123.xml file from the local D drive to the /
mbsc/bam/version_a/bin/bam directory of the OMU:
C:\Documents and Settings>d:
D:\>ftp 10.161.21.3
Connected to 10.161.21.3.
220 ftp server ready.
User (10.161.21.3:(none)): FtpUsr
331 Password required for FtpUsr.
Password:
230 User logged in.
ftp> cd /mbsc/bam/version_a/bin/bam
250 CWD successful.
ftp> put 123.xml
200 PORT command OK.
150 Opening BINARY mode data connection for '/123.xml' (104 bytes)
226 Transfer complete.
ftp> quit
D:\>
Prerequisites
You have logged in to the LMT. For details, see Logging In to and Logging Out of the LMT.
Procedure
l Querying the status of the OMU subsystem
1. Run the MML command DSP OMU. The operating status of the OMU subsystem is
displayed, including the OMU operating status, fixed IP address configuration, virtual
IP address configuration, status of data synchronization, status of the internal and
external networks, and status of the backup channel.
l Querying the status of the service processes when the OMU is operational
1. Run the MML command DSP OMUMODULE. The names and status of the service
processes are displayed.
If the status of the service processes is Started, the OMU service processes are
normal.
If the status of the service processes is Stopped, the OMU service processes are
normal and not started.
If the status of the service processes is Exception, the OMU service processes are
abnormal. When active and standby OMUs are configured, the self-healing
switchover is triggered if the abnormal state persists. When an independent OMU
is configured, the OMU reports the ALM-20707 OMU Process Abort alarm.
l Querying the status of the OMU board
1. Run the MML command DSP OMUSRV. The OMU board information is displayed,
including the CPU usage, memory usage, number of logical CPUs, memory capacity,
total space of logical disks, current available space, and percentage of the available
space.
----End
Prerequisites
You have logged in to the LMT. For details, see Logging In to and Logging Out of the LMT.
Context
If an OMU board becomes faulty, query the information about the OMU board for fault location.
Procedure
l Querying the OMU working environment
1. Run the MML command DSP OMUENV. The CPU inlet temperature, memory inlet
temperature, hard disk temperature, and voltage of chips are displayed.
l Querying the OMU hardware status
1. Run the MML command DSP OMUHW. The subrack number, slot number, operating
status of the hard disk, status of Ethernet adapters and Ethernet adapter teams, and
RAID of the OMU are displayed.
The OMU hardware is normal if the following conditions are met:
Prerequisites
You have logged in to the LMT. For details, see Logging In to and Logging Out of the LMT.
Procedure
Step 1 Run the LST OMUAREA command to query the version of the active and standby OMU
workspaces.
----End
Querying the Status of Data Synchronization Between the Active and Standby
OMUs
This section describes how to query the status of data synchronization between the active and
standby OMUs.
Prerequisites
l You have logged in to the LMT. For details, see Logging In to and Logging Out of the
LMT.
l Active and standby OMUs are configured.
Context
Due to network or database problems, an exception may occur during data synchronization.
When this occurs, the OMUs automatically rectify the faults.
Procedure
Step 1 Run the MML command DSP OMU on the active or standby OMU. The status of data
synchronization between the active and standby OMUs is displayed.
If data synchronization is abnormal, the ALM-20704 OMU Data Synchronization Failure alarm
is reported. Clear the alarm by referring to the alarm handling suggestions.
CAUTION
When Data-sync state is Data synchronization is successful, Data synchronization not built
due to version inconsistency, or Data synchronization cannot built due to OMU failure
switchover, you are allowed to switch over the active and standby OMUs.
----End
Checking the Data Consistency Between the Active OMU and the Standby OMU
This section describes how to check the data consistency between the active OMU and the
standby OMU after a fault-triggered switchover occurs.
Prerequisites
l You have logged in to the LMT. For details, see Logging In to and Logging Out of the
LMT.
l The OMUs work in active/standby mode.
Procedure
Step 1 Run the CMP OMUDATA command to check the consistency of alarm data, performance data,
and configuration data between the active and standby OMUs.
CAUTION
l If the active OMU data is inconsistent with the standby OMU data, run the STR
DATASYNC command to start the data synchronization between the active OMU and the
standby OMU. Wait 5 minutes then run the CMP OMUDATA command.
l If the active OMU is synchronizing the initial data with the standby OMU, the LMT displays
failure information.
Step 2 Run the CMP OMUFILE command to check the consistency of the license file, patch file, and
performance file between the active and standby OMUs.
----End
Prerequisites
l You have logged in to the LMT. For details, see Logging In to and Logging Out of the
LMT.
l You have obtained the time and the time zone.
Context
The OMU time and time zone are set by default before the OMUa/OMUc board is delivered.
The OMU time indicates the time on the OMU operating system, and the OMU time zone
indicates the time zone on the OMU operating system.
Procedure
l Change the OMU time
1. Run the SET TIME command to change the OMU date and time.
l Change the OMU time zone
1. Run the SET TZ command to change the OMU time zone.
----End
Prerequisites
l You have logged in to the LMT. For details, see Logging In to and Logging Out of the
LMT.
l When the OMU works in active/standby mode, the active and standby OMUs work
normally. In addition, no MML commands are executed and no scheduled tasks are
triggered. (You can query the data consistency using the CMP OMUDATA and CMP
OMUFILE commands to ensure that the data on the active OMU is synchronized to the
standby OMU.)
Context
Do not use this command for other scenarios.
Procedure
l Switching over the active/standby OMU workspaces in single-OMU mode
1. Run the SWP OMUAREA command and set Target OMU to ACTIVE (Active
OMU) to switch over the active and standby workspaces on the OMU.
2. Run the RST BSC command to reset the BSC so that the OMU data is consistent with
the host data.
l Switching over the active/standby OMU workspaces in dual-OMU mode
1. Run the SWP OMUAREA command and set Target OMU to STANDBY (Standby
OMU) to switch over the active and standby workspaces on the active OMU.
2. Run the SWP OMUAREA command and set Target OMU to ACTIVE (Active
OMU) to switch over the active and standby workspaces on the active OMU.
3. Run the RST BSC command to reset the BSC so that the OMU data is consistent with
the host data.
NOTE
Switchover of the active and standby OMU workspaces will interrupt the BSC6900 O&M for
3 minutes.
----End
Prerequisites
l You have logged in to the LMT. For details, see Logging In to and Logging Out of the
LMT.
l The OMU works in active/standby mode and the active and standby OMUs work normally
for more than 5 minutes (You can run the CMP OMUDATA and CMP OMUFILE
commands to query whether the active OMU data is consistent with the standby OMU data.
Ensure that the data on the active OMU is synchronized to the standby OMU to avoid data
loss after the switchover.)
Procedure
Step 1 Run the DSP OMU command to query the operating status of the active/standby OMUs.
If... Then...
The active and standby OMUs work properly and the data Go to Step 2.
synchronization is normal,
The active and standby OMUs do not work properly or the data End this task.
synchronization is abnormal,
Step 2 Run the SWP OMU command to manually switch over the OMUs.
Step 3 Run the DSP OMU command to query the operating status of the active OMU after the
switchover. If the active OMU works properly, the switchover is successful.
----End
Prerequisites
You have logged in to the LMT. For details, see Logging In to and Logging Out of the LMT.
Context
l The OMU operating system is restarted after the OMUa board is reset. If the OMUa board
is reset successfully, the faults of the OMU operating system or applications can be rectified.
l All the service processes are disrupted after the OMU applications are reset. If the OMUa
board is reset successfully, the faults of the OMU applications can be rectified.
l Resetting a specified OMU service process interrupts the service of the process for a while.
Procedure
l Reset the OMUa board/OMU applications
1. Run the RST OMU command.
If Reset Type is set to SOFT, only the OMU applications are reset. The OMU
operating system is not restarted.
If Reset Type is set to HARD, the OMU operating system is restarted.
NOTE
l When the OMU works in single-OMU mode, set the Reset Target to ACTIVE.
l When the OMUs work in dual-OMU mode, the active OMU is reset if you set the Reset
Target to ACTIVE.
l When the OMUs work in dual-OMU mode, the standby OMU is reset if you set the Reset
Target to STANDBY.
l Reset a specified service process
1. Run the RST OMUMODULE command and specify Reset Target and Module
Name to reset the specified OMU service process.
----End
Procedure
Step 1 Log in to the OMU by using the external fixed IP address by referring to Logging In to the
OMU.
Step 2 Run the /etc/rc.d/omud status command to query the operating status of the omud.
Option Description
If the operating status of the omud is unused, The OMU stops working.
----End
Procedure
Step 1 Log in to the OMU by using the external fixed IP address by referring to Logging In to the
OMU.
Step 2 Enter the /etc/rc.d/omud start command and press Enter to start the omud.
----End
Context
You need to stop the omud before uninstalling the OMU applications, upgrading the OMU
applications, or restoring the BSC6900 data.
CAUTION
l When the omud is stopped, all the OMU service processes will also stop. In turn, the OMU
stops providing services for the BSC6900. Therefore, perform this task with caution.
l 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 Log in to the OMU by using the external fixed IP address by referring to Logging In to the
OMU.
Step 2 Enter the /etc/rc.d/omud stop command and press Enter to stop the omud.
----End
Prerequisites
l The OMU applications are installed. For details, see Installing the OMU Applications in
the Active Workspace.
Context
l If OMU applications are installed on both the active and standby OMU workspaces,
uninstall the OMU applications on the standby workspace before uninstalling them on the
active workspace.
l When the BSC6900 is configured with active and standby OMUs, uninstall the OMU
applications on both the active and standby OMUs.
l If there is only the active workspace on the OMU, the system will prompt you to uninstall
only the OMU applications on the active workspace.
NOTE
l Uninstalling the OMU applications from an OMU will cause all the data in the OMU to be lost. You are
advised to back up system data on the OMU before the uninstalling by referring to Backing Up the System
Data.
Procedure
Step 1 Log in to the standby OMU by using the fixed external IP address or the commissioning IP
address. For details, see Logging In to the OMU.
Step 2 Enter the /etc/rc.d/omud stop command and press Enter to stop the omud..
Step 3 Enter uninstall_bam in any directory of the OMU and press Enter.
Step 4 The message Uninstall standby area. input Y to continue; input E to exit. is displayed. Enter
Y to uninstall the OMU applications on the standby workspace of the standby OMU.
Step 6 The message Uninstall main area. input Y to continue; input E to exit. is displayed. Enter
Y to uninstall the OMU applications on the active workspace of the standby OMU.
Option Description
Step 8 Log in to the active OMU using the fixed external IP address or commissioning IP address. Then
perform Step 2 through Step 7 again.
----End
Context
The omu_backup_linker tool is used in the following scenarios:
l When an OMUa/OMUc board is damaged, it needs to be replaced with a new one. The data
on the damaged OMUa/OMUc board needs to be backed up and restored on the new OMUa/
OMUc board.
l The OMU data needs to be backed up during routine maintenance.
l The latest OMU data needs to be restored after the OMU database collapses or the OMU
upgrade fails.
Context
l If an independent OMU is configured, log in to the OMU to start the omu_backup_linker
tool.
l If active and standby OMUs are configured, log in to the active OMU to start the
omu_backup_linker tool.
Procedure
Step 1 Log in to the target OMU by referring to Logging In to the OMU.
Step 2 Enter the cd /mbsc/bam/common/services command and press Enter to go to the directory
where the program of the omu_backup_linker tool is saved.
Step 3 Enter the ./omu_backup_linker command and press Enter to start the omu_backup_linker
tool, as shown in the following figure.
# The backup/restore option
# backup :Backup OMU database
# restore :Restore OMU database
# Please select one option to backup or restore OMU database, if you don't know it,
consult the administrator.
Please input a valid bkp_res_type :
----End
Prerequisites
l Prerequisites for performing this task using MML commands:
You have logged in to the LMT. For details, see Logging In to and Logging Out of the
LMT.
l Prerequisites for performing this task using the omu_backup_restore_tool are as follows:
You have logged in to the OMU by referring to Logging In to the OMU.
Context
CAUTION
l When the OMU works in active/standby mode, the system data must be backed up on the
active OMU.
l You must back up the OMU data manually to avoid a system data backup failure before
capacity expansion, upgrade, or a software loading.
Procedure
l Backing up the system data through an MML command
1. Run the BKP DB command to set Path of Backup File and Backup File Name to
back up the data in the specified directory on the OMU hard disk.
2. Obtain the backup data file from the specified directory by referring to Transferring
OMU Files to a Local PC.
l Backing up the data by using the omu_backup_restore_tool
1. Enter the cd /mbsc/bam/common/services command and press Enter to go to the
directory where the program of the omu_backup_linker tool is saved.
----End
Example
Back up the OMU data to /mbsc/bam using the omu_backup_restore_tool and the name the file
as omu.bak. The following shows an example of the results.
omd_test_name /mbsc/bam/common/services # ./omu_backup_linker
Context
Restoring the BSC6900 system data will interrupt services on the BSC6900. After the system
data is restored, the data on the host will be inconsistent with the data on the OMU. As a result,
services will be greatly impacted. Therefore, you are advised to restore the system data in the
early morning hours when traffic volume is low.
This chapter describes how to restore data by using the following methods:
l If an MML command is used to restore data, only the BSC6900 configuration data is
restored.
l If the backup restoration tool is used to restore data, all BSC6900 data is restored, including
configuration data, alarm data, performance data, operating logs, administrator account,
authority information, and product information.
NOTE
This document uses the OMU in active/standby mode as an example. If an OMU is in independent mode, skip
operations on the standby OMU.
Procedure
l Restoring the system data through an MML command
1. Run the LST BKPFILE command to query data backup files saved in the OMU
active workspace installation directory\data\backup directory.
2. Run the RTR DB command to restore configuration data on the OMU.
l Restoring the system data by using the omu_backup_restore_tool
1. Log in to the active and standby OMUs by referring to Logging In to the OMU.
2. Enter the /etc/rc.d/omud stop command and press Enter to stop the omud. on the
active and standby OMUs.
3. Restore data in the original active OMU using the omu_backup_linker tool.
a. Enter the cd /mbsc/bam/common/services command and press Enter to go to
the directory where the program of the omu_backup_linker tool is saved
b. Log in to the OMU by referring to Enter the ./omu_backup_linker command
and press Enter to start the omu_backup_linker tool.
c. Enter backup and press Enter after the Please input a valid
bkp_res_type : message is displayed.
d. Enter the save path and name of the backup file and press Enter when the
Please input a valid backup file pathname : message is
displayed. If the restoration is successful, the Restore OMU database
succeed! message is displayed.
4. Copy and save the backup file to be restored in the standby OMU using the psftp
software. For details, see 4.4.1 psftp Software.
5. Repeat Step 3 to restore data in the original standby OMU using the
omu_backup_linker tool.
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 the
BSC6900 UMTS LMT User Guide.
8. Run the REQ CMCTRL command to obtain the data configuration rights.
9. Check the consistency between the BSC6900 host data and the OMU data.
NOTE
After data restoration, check whether the BSC6900 host data is consistent with the OMU data.
If no, load the restored data to the BSC6900 host boards.
a. Run the ACT CRC command to check whether the host data is consistent with
the OMU data.
If the data is consistent, end this task.
If the data is inconsistent, go to 9.2.
b. Run the FMT DATA command to format the data in the OMU database so that
the data can be loaded into the host.
c. If data inconsistency occurs in only one subrack, run the RST SUBRACK
command with Subrack No. specified to reset this subrack. If data inconsistency
occurs in multiple subracks, run the RST BSC command to reset the BSC.
----End
Example
Restore the OMU data by using the omu.bak file under /mbsc/bam. The following shows an
example of the results:
Prerequisites
The OMU applications are installed. For details, see Installing the OMU Applications in the
Active Workspace.
Context
You can perform tasks by running omutool commands with specified parameters.
NOTE
l You can run the LST OMUAREA command to query the active OMU workspace.
l Assume that the active OMU workspace is installed in /mbsc/bam/version_a.
Procedure
Step 1 Log in to the target OMU by referring to Logging In to the OMU.
Step 2 Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the directory
where the omutool program is saved.
Step 3 Run the ./omutool -h command. The parameter information on the omutool is displayed.
----End
Prerequisites
l You have logged in to the LMT, and queried the slot No. for the OMU by running the LST
BRD command.
l You have logged in to the LMT, and queried whether the OMU is in single-OMU or dual-
OMU mode by running the DSP OMU command.
l You have logged in to the LMT, and queried the OMU version and workspace information
by running the LST OMUAREA command.
l You have logged in to the LMT and queried the OMU service mode by running the LST
MBSCMODE command.
Context
l If the working mode is changed from independent mode to active/standby mode, apply the
settings to both the active and standby OMUs. If the working mode is changed from active/
standby mode to independent mode, apply the settings to only the new active OMU.
l If the working mode of the OMU is changed from independent mode to active/standby
mode, ensure that the operating system, software version, and board type of the active
OMU are the same as those of the standby OMU. In addition, the slot number of the active
OMU and that of the standby OMU have an active/standby relationship.
l If the working mode of the OMU is changed from active/standby mode to independent
mode, you should run the MML command DSP OMU to ensure that the Data-sync
state is Data synchronization is successful and run the MML command
CMP OMUFILE to ensure that Compare result is consistent.
Procedure
l Switching the OMU from the independent mode to the active/standby mode (OMU
applications are not installed on the OMU to be added).
1. Insert an OMUa/OMUc board into the standby slot by referring to Installing the
OMUa/OMUc/SAUa/SAUc Boards or Installing the OMUc Boards in BSC6900
UMTS Installation Guide
2. Connect the PC to the commissioning Ethernet port of the OMU, and log in to the
standby OMU by using the commissioning IP address. For details, see Logging In to
the OMU.
3. Install OMU applications on the standby OMU. For details, see Uploading the OMU
Application Installation Package to the OMU and Installing the OMU
Applications in the Active Workspace.
NOTE
You must select active/standby mode during the process of installing the OMU applications for the
standby OMU.
4. Change the IP addresses and subnet masks of the standby OMU to ensure that the
fixed internal IP addresses, fixed external IP addresses, and IP address of the backup
channel between active and standby of OMUs comply with the planning principle for
the IP addresses and do not conflict with each other. For details about changing IP
WARNING
You should start the standby OMU 5 minutes after the active OMU is started to keep
the two OMUs from competing for the active state. This helps avoid data loss.
10. Change the operating system password on the standby OMU to that of the original
active OMU by referring to 4.3.6 Changing the Administrator Password of the
Operating System.
11. Run the ADD BRD command on the LMT to add an OMU.
12. Run the MML command DSP OMU on the LMT and check whether the value for
Data-sync state is Data synchronization is successful.
13. Connect an Ethernet cable to the Ethernet port on the added OMU.
l Switching the OMU from the independent mode to the active/standby mode. (OMU
applications are installed on the OMU to be added.)
1. Connect the PC to the commissioning Ethernet port of the OMU and log in to the
original active OMU by using the commissioning IP address. For details, see Logging
In to the OMU.
2. Enter the /etc/rc.d/omud stop command and press Enter to stop the omud. on the
original active OMU.
3. Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the
directory where the omutool program is saved. 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. Enter the /etc/rc.d/omud start command and press Enter to start the omud. on the
original active OMU.
6. Insert an OMUa/OMUc board in the standby slot 5 minutes after the original active
OMU starts.
WARNING
Start the standby OMU 5 minutes after the active OMU is started to avoid the two
OMUs from competing for active state, which will avoid data loss.
7. Set the working mode of the standby OMU to active/standby mode by repeating Step
1 through Step 4.
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 the IP address of the
backup channel between active and standby of OMUs comply with the planning
principle for the IP addresses and do not conflict with each other. For details about
changing IP addresses, see Changing IP Addresses of OMU Ethernet Adapters
and Their Subnet Masks.
9. Enter the /etc/rc.d/omud start command and press Enter to start the omud. on the
standby OMU.
10. Change the operating system password on the standby OMU to that of the original
active OMU by referring to 4.3.6 Changing the Administrator Password of the
Operating System.
11. Run the ADD BRD command on the LMT to add an OMU.
12. Run the MML command DSP OMU on the LMT and check whether the value for
Data-sync state is Data synchronization is successful.
13. Connect an Ethernet cable to the Ethernet port on the added OMU.
l Change the working mode of the OMU from active/standby mode to independent mode.
1. Run the RMV BRD command on the LMT to remove an OMU.
2. Log in to the active and standby OMUs by using the fixed external IP address by
referring to Logging In to the OMU.
3. Enter the /etc/rc.d/omud stop command and press Enter to stop the omud. on 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 to be removed by referring to step 2 to step 5 inScenario: Old and
New OMU Boards Running the Same OS.
6. Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the
directory where the omutool program is saved. on the active OMU.
7. Run the ./omutool dualmode single command on the active OMU to set the working
mode of the OMU to independent mode.
8. Enter the /etc/rc.d/omud start command and press Enter to start the omud. on the
active OMU.
----End
Context
If the OMU is in active/standby mode, change the IP addresses and subnet masks of the Ethernet
adapters on both the active and standby OMUs. You are advised to first change the IP addresses
and subnet masks of the Ethernet adapters for the standby OMU before changing those for the
active OMU.
NOTE
This task describes how to change all the IP addresses and subnet masks for the OMU. You can perform required
steps to fit onsite needs.
l Single-OMU mode: Stop the omud before the change and start the omud after the change.
l Dual-OMU mode: Stop the standby omud and then the active omud before the change. Start the active omud
and then the standby omud after the change.
For details about the Ethernet adapter binding relationship, see 3.1 OMU Ethernet Adapter
Configuration.
Procedure
Step 1 Log in to the OMU by referring to Logging In to the OMU.
Step 2 Enter the /etc/rc.d/omud stop command and press Enter to stop the omud..
Step 3 Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the directory
where the omutool program is saved..
Step 4 The command for querying the OMU IP address and subnet mask is ./omutool dispipinfo.
For example, type the following command and press Enter to query the OMU IP address and
subnet mask:
./omutool dispipinfo
Step 5 The ./omutool innercard IP address command is used to change the fixed internal IP address.
For example, type the following command and press Enter to change the fixed internal IP
address:
./omutool innercard 80.168.3.60
Step 6 The ./omutool innervip IP address command is used to change the virtual internal IP address.
For example, type the following command and press Enter to change the virtual internal IP
address:
./omutool innervip 80.168.3.40
NOTE
l The fixed and virtual internal IP addresses must be in the same network segment. If the network segment
of the fixed internal IP address is changed to be different from that of the virtual internal IP address, you are
prompted to change the virtual internal IP address. If the network segment of the internal IP address is
changed to be different from that of the fixed internal IP address, you are prompted to change the fixed
internal IP address.
l When you change the fixed and virtual internal IP addresses, the corresponding subnet masks are created
automatically.
l If you change the fixed and virtual internal IP addresses for the first time, perform the following additional
steps:
1. Run the SET SUBNET command to set the BSC6900 subnet number so that it is consistent with the
number of the network segments on which the fixed internal IP address and virtual internal IP address
are located.
2. Remove the SCUa board and reinstall it in the MPS. Then, reset the MPS to validate the new fixed and
virtual internal IP addresses.
l After these two steps are performed, the OMU can communicate with the BSC6900 host boards normally.
Step 7 The ./omutool extercard IP address mask (gateway) command is used to change the fixed
external IP address and mask.
For example, type the following command and press Enter to change the fixed external IP
address and mask:
./omutool extercard 10.161.10.100 255.255.255.0
CAUTION
Before changing the fixed external IP address, virtual external IP address, and external gateway
IP address, log in to the OMU using the debugging IP address at the local end. Otherwise, remote
login in to the OMU to change the IP addresses may disconnect the OMU from its peer.
Step 8 The ./omutool extervip IP address subnet mask (gateway) command is used to change the virtual
external IP address and subnet mask.
For example, type the following command and press Enter to change the virtual external IP
address and subnet mask:
./omutool extervip 10.161.10.102 255.255.255.0
NOTE
l After the virtual external IP address and mask are changed, run the RMV EMSIP command and then the
ADD EMSIP command to update the virtual external IP address and mask that are recorded in the OMU
database.
l The fixed and virtual internal IP addresses must be in the same network segment. If the network segment
of the fixed external IP address is changed to be different from that of the virtual internal IP address, you
are prompted to change the virtual external IP address. If the network segment of the virtual external IP
address is changed to be different from that of the fixed external IP address, you are prompted to change the
fixed external IP address.
l After the fixed external IP address, virtual external IP address, and gateway IP address are changed, the
communication between the OMU and peripheral equipment is interrupted. You need to use the new fixed
or virtual external IP address to reconnect the OMU and peripheral equipment.
Step 9 The ./omutool gateway gateway IP address is used to change the gateway IP address.
For example, type the following command and press Enter to change the gateway IP address:
./omutool gateway 10.161.10.1
NOTE
You can change the fixed or virtual external IP address simultaneously with changing the gateway IP address.
The following are the related commands:
l ./omutool extercard IP address Subnet mask Gateway IP address for changing the fixed external IP address
and gateway IP address simultaneously
l ./omutool extervip IP address Subnet mask Gateway IP address for changing the virtual external IP address
and gateway IP address simultaneously
Step 10 Change the backup channel IP address of the active and standby OMUs by using commands
listed in the following table.
Option Description
Option Description
Step 11 The ./omutool debugcard IP address is used to change the commissioning IP address.
For example, type the following command and press Enter to change the commissioning IP
address:
./omutool debugcard 192.168.6.60
NOTE
l After you change the backup channel IP address and commissioning IP address of the active and standby
OMUs, the corresponding subnet mask will be created automatically.
l To change the IP addresses of the OMU, you must follow the principle of IP address planning. For
details, see 3.2 OMU IP Address Plan. When entering the command, ensure that there is a space
between the IP address and the subnet mask.
l Record the new IP addresses in 4.5.1 Information Record Sheet of OMU Software Installation.
Step 12 The ./omutool delextercard command is used to delete the fixed external IP address.
For example, type the following command and press Enter to delete the fixed external IP
address:
./omutool delextercard
NOTE
l If the virtual and fixed external IP addresses have been configured and the fixed external IP address is planned
to be deleted, use this command to delete the configured fixed external IP address.
l If ALM-20702 Active and Standby OMU Communication Link Failure is reported before you delete the
fixed external IP address and the alarm cause is the external network, delete the alarm after you delete the
fixed external IP address.
Step 13 Enter the /etc/rc.d/omud start command and press Enter to start the omud..
----End
Context
l admin is the account for logging in to the LMT.
l db_user and root are the accounts for accessing the OMU database.
l FtpUsr is the account for uploading and downloading files to and from the OMU.
If active and standby OMUs are configured on the BSC6900, you must change the passwords
used by the admin, db_user, and root user on both the active and standby OMUs.
NOTE
l It is recommended that you change the password at your first login and then change the password every
three months.
l Users root and db_usr must both contain the combination of the following:
l At least one lower-case letter
l At least one upper-case letter
l At least one digit
l At least one special character -?[]_+{}
The user password must have a minimum length of 8 characters and maximum length of 32 characters.
l The admin and FtpUsr user password must have a minimum length of 6 characters and maximum length
of 32 characters.
Procedure
l Changing the password used by admin
1. Log in to the target OMU by referring to Logging In to the OMU.
2. Enter the /etc/rc.d/omud stop command and press Enter to stop the omud..
3. Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the
directory where the omutool program is saved..
4. Run the ./omutool adminpwd command to change the admin password.
5. Enter the /etc/rc.d/omud start command and press Enter to start the omud..
l Changing the password used by root
1. Log in to the target OMU by referring to Logging In to the OMU.
2. Enter the /etc/rc.d/omud stop command and press Enter to stop the omud..
3. Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the
directory where the omutool program is saved..
4. Run the ./omutool dbrootpwd command to change the root password.
5. Enter the /etc/rc.d/omud start command and press Enter to start the omud..
l Changing the password used by db_user user
1. Log in to the target OMU.
2. Enter the /etc/rc.d/omud stop command and press Enter to stop the omud..
3. Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the
directory where the omutool program is saved..
4. Run the ./omutool dbpwd command to change the password of the db_user user.
5. Enter the /etc/rc.d/omud start command and press Enter to start the omud..
l Changing the password used by FtpUsr user
1. Log in to the LMT by referring to Logging In to and Logging Out of the LMT in the
BSC6900 UMTS LMT User Guide.
2. Run the MML command MOD FTPPWD to change the password used by FtpUsr
user.
----End
Example
The following shows an example for changing the password used by admin:
The following shows an example for changing the password used by root:
The following shows an example for changing the password used by db_user user:
Context
l After installing the OMU applications onsite, you need to change the computer name and
IP addresses according to the plan. For information about how to change the OMU IP
addresses, see Changing IP Addresses of OMU Ethernet Adapters and Their Subnet
Masks.
l If the BSC6900 is configured with active and standby OMUs, name them differently.
Procedure
Step 1 Log in to the target OMU by referring to Logging In to the OMU.
Step 2 Enter the /etc/rc.d/omud stop command and press Enter to stop the omud..
Step 3 Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the directory
where the omutool program is saved..
Step 4 Run the ./omutool 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
BSC6900 UMTS LMT User Guide.
2. Run the DSP OMU command to query the new computer name.
Context
To manage BSCs uniformly on the M2000, you need to modify the NE type of upgraded BSCs.
The following procedure is for active and standby OMUs whose active workspace is
version_a. For a single OMU, ignore the steps for the standby OMU.
Procedure
Step 1 Log in to the standby OMU and stop the omud process on it. Then, log in to the active OMU
and stop the omud process on it. For details, see Logging In to the OMU and Stopping the
omud.
Step 2 Type the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the directory
where the omutool program is saved.
Step 3 Type the ./omutool netype command followed by the new value of the NE type parameter on
the active OMU. Press Enter to modify the NE type.
The prompt set ne type success! indicates that the NE type has been successfully modified.
NOTE
To query the NE type, type the omutool netype command and press Enter.
Step 4 Start the omud process on the active OMU first and then the omud process on the standby OMU.
For details, see Starting the omud.
----End
Example
dopra_linux_up /mbsc/bam/version_a/bin/bam # ./omutool netype
Current ne type is :BSC6***
dopra_linux_up /mbsc/bam/version_a/bin/bam # ./omutool netype BSC6900
set ne type success!
Prerequisites
l The target slots for OMUs are idle and can hold OMUs. Such slots can be slots 0 to 3, slots
20 to 23, or slots 24 to 27.
l The target slots for OMUs are idle and can hold OMUs. Such slots refer to OMUa Board
or OMUc Board.
l The value of Data-sync state is Data synchronization is successful. You can run the DSP
OMU command to view the setting of Data-sync state.
Procedure
Step 1 Perform different operations to shut down the OMUs based on the operating system.
If... Then...
The Suse Linux operating system or Dopra 1. Log in to the active and standby OMUs
Linux operating system is used respectively by referring to Logging In to
the OMU.
2. Run the etc/rc.d/omud stop command to
stop the omud process.
3. Run the poweroff command to shut down
the OMUs.
The Windows operating system is used 1. Log in to the active and standby OMUs
respectively by referring to 5.2.20
Logging In to the OMU.
2. Choose Start > Run. Type cmd in the
Open text box and then press Enter. The
OMU command interface is displayed.
3. Run the net stop omud command to stop
the omud process.
4. Choose Start > Shutdown. Select
Shutdown from the drop-down list box to
shut down the OMU.
Step 2 When the OFFLINE LED on the OMU board panel is on, pull the active and standby OMUs
and insert them into the target slots.
NOTE
Insert active and standby OMUs into the target slots one by one after pulling both of them.
Step 3 Wait about five minutes, log in to the LMT. and then run the DSP OMU command to check
whether the active and standby OMUs operate properly.
Step 4 Run the LST BRD command to query the subrack number and slot numbers of the active and
standby OMUs before the switchover.
Step 5 Run the RMV BRD command to remove the original active and standby OMUs.
Step 6 Run the ADD BRD command to add new active and standby OMUs. In this step, set slot numbers
of the OMUs to the target OMU slot numbers.
Assume that the target OMU slot numbers are 21 and 23. Run the following commands:
ADD BRD: SRN=0, BRDCLASS=OMU, BRDTYPE=OMUa, SN=21;
ADD BRD: SRN=0, BRDCLASS=OMU, BRDTYPE=OMUa, SN=23;
Step 7 Check whether the OMUs are properly displayed on the device panel and whether they are in
normal state.
Step 8 Click Alarm in the home page of the LMT and view current active alarms of the BSC6900 in
the Browse Alarm tab page.
Step 9 Optional: If there is an alarm related to the original OMUs in the list of active alarms, select
the alarm, right-click it, and choose Clear Alarm from the shortcut menu to manually clear the
alarm.
----End
Context
l The psftp software is used to upload files to the OMU hard disk. The OMU applications
can be used only after the psftp software is installed.
l The psftp software is also used to download files from the OMU hard disk to a local PC.
Table 4-11 lists the commands commonly used on the psftp software.
get Transfer files from the To transfer a file, run the get
OMU to the local PC. V900R014C00 command.
To transfer a folder, run the get -r
V900R014C00 command.
put Transfer files from the local To transfer a file, run the put
PC to the OMU. V900R014C00 command.
To transfer a folder, run the put -r
V900R014C00 command.
Procedure
Step 1 Contact Huawei engineers who can obtain the psftp software by performing the following
operation:
Log in to http://support.huawei.com/support/. Choose Software Center > Controlled Tool
> Core Network Product Line > Genex CN Nastar TOOL > Tools for remote login linux
to download the psftp software.
Step 3 Type the open IP address command and press Enter (using 10.161.21.203 as an example).
Step 4 Log in to the OMU as user root user, lgnusr user, or common user to connect to the OMU. The
displayed interface is as follows:
----End
Prerequisites
l The PC is connected to the Internet.
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
Procedure
Step 1 Contact Huawei engineers who can obtain the tool by performing the following operation:
Log in to http://support.huawei.com/support/. Choose Software Center > Controlled Tool
> Core Network Product Line > Genex CN Nastar TOOL > Tools for remote login linux
to download the PuTTY software.
Step 2 Double-click putty.exe. The PuTTY Configuration dialog box is displayed, as shown in
Figure 4-15.
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.
If... Then...
The PC is connected to ETH0 or ETH1 on the The IP address is the fixed external IP address
OMU board panel through a network device, or virtual external IP address of the OMU.
Step 5 Log in to the OMU as the root user, lgnusr user, or common user.
----End
Administrator password
(active OMU)
Administrator password
(standby OMU)
Debugging IP address
(subnet mask) of the standby
OMU
Default gateway
Administrator (admin)
password
Setting OMU BIOS Set the first boot device of the OMU to USB
Item Remarks
Installing the Dopra Linux operating l If the version of the OMU operating system is
system V200R003C02SPC090 or later,
The default root user passwords of the
active and standby OMUs are
osadmin@123.
The default lgnusr user passwords of the
active and standby OMUs are
osnormal@123.
l If the version of the OMU operating system is
earlier than V200R003C02SPC090,
The default root user password of active
and standby OMUs are mbsc@com,
11111111, or huawei.
Teaming the internal Ethernet adapter The default IP address of the internal Ethernet
team adapter team of the active OMU is 80.168.3.50
(255.0.0.0).
The default IP address of the internal Ethernet
adapter team of the standby OMU is 80.168.3.60
(255.0.0.0).
Teaming the external Ethernet adapter The default IP address of the external Ethernet
team adapter team of the active OMU is
172.121.139.201 (255.255.255.0).
The default IP address of the external Ethernet
adapter team of the standby OMU is
172.121.139.202 (255.255.255.0).
Configuring backup channel IP address The default backup channel IP addresses of the
of the active and standby OMUs (for the active OMU is 192.168.3.50 (255.255.255.0).
OMUa board) The default backup channel IP addresses of the
standby OMU is 192.168.3.60 (255.255.255.0).
Setting OMU BIOS Set the first boot device of the OMU to USB
Item Remarks
Installing the Dopra Linux operating l If the version of the OMU operating system is
system V200R003C02SPC090 or later,
The default root user passwords of the
active and standby OMUs are
osadmin@123.
The default lgnusr user passwords of the
active and standby OMUs are
osnormal@123.
l If the version of the OMU operating system is
earlier than V200R003C02SPC090,
The default root user password of active
and standby OMUs are mbsc@com,
11111111, or huawei.
Teaming the internal Ethernet adapter The default IP address of the internal Ethernet
team adapter team of the active OMU is 80.168.3.50
(255.0.0.0).
The default IP address of the internal Ethernet
adapter team of the standby OMU is 80.168.3.60
(255.0.0.0).
Teaming the external Ethernet adapter The default IP address of the external Ethernet
team adapter team of the active OMU is
172.121.139.201 (255.255.255.0).
The default IP address of the external Ethernet
adapter team of the standby OMU is
172.121.139.202 (255.255.255.0).
Item Remarks
For details, see Checklist for the Factory Settings of the OMU Software (Creating
BSC6900).
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.
l (1) indicates the object type corresponding to the operation rights: - represents a file while
d represents a folder.
l (2) indicates the operation rights the current user has over the object: r represents that the
user has the right to read the object, w represents that the user has the right to write into the
object, x represents that the user has the right to execute the object, and- represents that the
user does not have the corresponding right.
l (3) indicates the operation rights users in the current user's group have over the object: r
represents that they have the rights to read the object, w represents that they have the rights
to write into the object, x represents that they have the rights to execute the object, and-
represents that they do not have the corresponding rights.
l (4) indicates the operation rights users who are not in the current user's group have over
the object: r represents that they have the rights to read the object, w represents that they
have the rights to write into the object, x represents that they have the rights to execute the
object, and- represents that they do not have the corresponding rights.
l (5) does not indicate anything.
l (6) indicates the current user.
l (7) indicates the user group the current user belongs to.
l (8) indicates the object.
/mbsc:
drwxrwxrwx 8 root mysql mysql
-rw-r-xr-- 1 root root upsrvcfg.ini
l drwxrwxrwx 8 root mysql mysql indicates that the current user root, the users in the mysql
user group that the user root belongs to, and the users who do not belong to the mysql user
group have the rights to read and write into the /mbsc/mysql folder as well as the rights to
search for files in the folder.
l -rw-r-xr-- 1 root root upsrvcfg.ini indicates that the current user root has the rights to
read and write into the upsrvcfg.ini file in the /mbsc folder; the users in the root user group
that the user root belongs to have the rights to read and execute the upsrvcfg.ini file in
the /mbsc folder, and users who are not in the root use group that the user root belongs to
have the rights to read the upsrvcfg.ini file in the /mbsc folder.
Contents Specifications
Contents Specifications
Contents Specifications
Remark:
Large-capacity hard disk: OMU hard disk space > 73 GB
Small-capacity hard disk: OMU hard disk space = 73 GB
version_x indicates the active workspace of the OMU, which is either version_a or
version_b.
For details about storage space of the OMU common directories, see OMU Folder Size List.
TCP UDP
1024-6553 FTP Server data Port for host loading, and uploading Y -
5 and downloading software and logs
(in passive mode)
TCP UDP
This chapter describes how to install software and perform operation and maintenance for the
OMU when the BSC6810 is upgraded to the BSC6900.
In this scenario, the physical entity to carry the OMU is the OMUa or OMUc board. For the
policy of replacing a faulty OMUb board, see Replacing an OMU Board in the BSC6900
UMTSSite Maintenance Guide.
l Operating System
Windows Server 2003 is used.
l OMU Applications
The OMU applications run on the bottom-level operating system and provide various
service processes.
NOTE
Antivirus software such as Norton, Macfee, and Officescan can be installed on the OMU.
Scenario Overview
When the BSC6810 is upgraded to the BSC6900, the OMU applications are upgraded while the
Windows Server 2003 operating system is retained.
5.1 Reinstalling Software Onsite
This section describes the software installation policies after the BSC6810 is upgraded to the
BSC6900.
5.2 OMU Operation and Maintenance After the Upgrade
This section describes how to perform operation and maintenance on the OMU after OMU
applications are installed. To perform this task, log in to the OMU remotely or run MML
commands.
5.3 Appendix: Antivirus Software
The OMU supports an integrated antivirus solution that uses the OfficeScan software provided
by TrendMicro. For the method of installing the antivirus software, see the antivirus software
installation guide provided by Huawei.
5.4 Appendix: Installing the iPSI SEK SetWin Software
This section describes how to install the iPSI SEK SetWin software and how to roll back the
security enhancement policies.
5.5 Appendix: OMU-Related Information Tables
This section describes the tables in which the OMU information is recorded during routine
operation and maintenance on the OMU.
Context
The operating system of the BSC6810 is Windows Server 2003, and the operating system of the
BSC6900 is Dopra Linux. After the BSC6810 is upgraded to the BSC6900, Windows Server
2003 can be retained or switched to Dopra Linux.
If Windows Server 2003 needs to be retained, Go to 5.1.3 Optional: Installing OMU Applications.
If Windows Server 2003 needs to be reinstalled, Go to 5.1.1 Reinstalling the Windows OS.
If Windows Server 2003 needs to be switched to Dopra Go to 5.1.2 Switching the OMU Operating System.
Linux,
Context
After the BSC6810 is upgraded to the BSC6900, reinstall the Windows Server 2003 OS if it is
retained.
NOTE
The OMUc board supports only the Dopra Linux OS. Therefore, the Windows OS can only be reinstalled on
the OMUa board. Later in the document, the OMU board indicates the OMUa board.
Hard disk 1 80 GB 10 GB
CD drive 1 - -
If the operating system of the PC is Microsoft Windows XP Professional, the Windows firewall
and simple file sharing must be disabled. Otherwise, the EasyInstall software and the installation
of the OMU operating system may be affected.
1. Right-click My Network Places and choose Properties from the shortcut menu. The
Network Connections window is displayed.
2. Right-click the Local Area Connection and choose Properties from the shortcut menu.
The Local Area Connection Properties dialog box is displayed.
3. Click the Advanced tab.
4. Click Settings. A dialog box is displayed. Click the General tab and click Off. Click
OK. The firewall is disabled.
To configure the IP address of the Ethernet adapter of the portable computer to 192.168.0.215,
perform the following steps:
1. Right-click My Network Places and choose Properties from the shortcut menu. The
Network Connections window is displayed.
2. Right-click Local Area Connection and choose Properties from the shortcut menu. The
Local Area Connection Properties dialog box is displayed.
3. Select Internet Protocol (TCP/IP) then click Properties. The Internet Protocol (TCP/
IP) Properties dialog box is displayed.
4. Click Use the following IP address. Configure the IP address to 192.168.0.215 and the
subnet mask to 255.255.255.0.
NOTE
Contact Huawei engineers who can obtain the software by performing the following operation:
To obtain the latest EasyInstall software, log in to http://support.huawei.com/support and choose Software
Center > Version Software > Wireless Product Line > WCDMA-RAN > WRAN OM Tools to download
the autoinst software.
The EasyInstall installation source cannot be prepared on a PC running the Windows XP SP3 operating system.
Context
An installation source server, a portable computer, saves programs such as the operating system.
The EasyInstall software is used to install the OMU operating system.
Procedure
Step 1 Decompress the EasyInstall software package to a portable computer.
NOTE
Unless otherwise specified, the software package is decompressed in the D:\autoinst directory.
Step 4 Select the installation source directory and click OK. The window shown in Figure 5-3 is
displayed. You are advised to select the default installation source directory. If the default
installation source directory does not exist, create one.
Step 5 Click New on the toolbar or choose Source > New. The dialog box shown in Figure 5-4 is
displayed.
If... Then...
Windows Server 2003 R2... is selected, The dialog box shown in Figure 5-5 is displayed.
Step 7 Click Next. The dialog box shown in Figure 5-6 is displayed.
Step 8 Insert CD1 into the CD drive on the portable computer. Click Next. A dialog box is displayed.
Step 9 Click Execute. Files in CD1 start to be copied and the progress is displayed.
Step 10 After all the files in CD1 are copied, a dialog box is displayed, prompting you to insert CD2.
Click OK. Follow the wizard to copy the remaining CDs.
Step 11 After all the CDs of the OMU operating system are copied, click Finish. The installation source
is displayed in the Installation Source Manager window shown in Figure 5-3.
----End
Context
l Contact Huawei engineers to obtain the SetWin software by logging in to http://
support.huawei.com/support and choosing Software Center > Controlled Tool >
Wireless Product Line > Security Tools > public.
NOTE
The version of the SetWin software must be consistant with that described in the Deployment Guide to
WRAN Windows Device Security Policy. To obtain the Deployment Guide to WRAN Windows Device
Security Policy, log in to http://support.huawei.com/support and choose Wireless > WCDMA-RAN
> WCDMA-RNC > Reconstruction Guide.
l Contact Huawei engineers to obtain patches for the Windows SP2 and basic patches for
the Windows 2007 by logging in to http://support.huawei.com/support and choosing
Software Center > Controlled Tool > Wireless Product Line > Universal OS
Patches > public.
Procedure
Step 1 Decompress the SetWin software package.
Step 3 Save the 2700 basic patches and the iPSI SEK Setwin.exe and License.Dat files decompressed
from the SetWin software package to D:\OMU\SRC\pack\ENU\.
The creation of the installation source for the SetWin software and OS patches is complete.
----End
Prerequisites
l The OMU board is powered on and works normally.
l The OMU is connected to the local PC through the commissioning Ethernet port.
l The operating system installation source is created. For details, see Creating the
Operating System Installation Source.
Context
l Other Ethernet adapters are bound before you use the EasyInstall software to install the
OMU operating system. Therefore, you can install the software in network installation
mode by using only the commissioning Ethernet port. Otherwise, the installation fails.
l The time required for the installation depends on the portable computer configuration and
the Ethernet adapter performance. Generally, installing the Windows operating system,
SP2, and SetWin software takes 60 minutes if a 100 Mbit/s Ethernet adapter is used.
Procedure
Step 1 Go to the D:\autoinst path, open the autoinst.conf file using a text processing program, and
configure parameters by changing the default values to the recommended values, as shown in
Table 5-2.
SRC_PATH d:\OMU\SRC Path for saving the Save path of the installation
installation source file source file
as needed (you can use
the default path)
Step 2 Choose Start > Run, and run the cmd command. The cmd window is displayed.
Type the following command and press Enter:
C:\Documents and Settings>cd /d D:\autoinst
Step 3 Type checkout.bat and press Enter. The POMU Easy-Install Check Result dialog box is
displayed. Check whether the ports displayed in the dialog box are used, as shown in Figure
5-7.
NOTE
If the port status is Fail as shown in Figure 5-7, the port is not used. If the port status is OK, the port is
used. To release the port, quit other running programs.
1. Run the netstat -a -n -o command to query the PID of the port.
2. Open the task manager. Click the Processes tab. Choose View > Select Columns. Select PID and click
OK.
3. Query the process mapping the PID and terminate the process.
Step 4 Type install.bat and press Enter. After the DHCP and TFCP services are successfully started,
the command line returns to D:\autoinst, as shown in Figure 5-8.
CAUTION
l Before running the script, ensure that ETH2 is in Link state, that the DHCP Ethernet port on
the installation source server and ETH2 (commissioning Ethernet port) on the OMU board
panel are connected, and that the installation source server is powered on. The DHCP service
cannot be started if ETH2 is in Down state.
l If the system provides a prompt indicating that a service failed to start, run the install.bat
program again until services are successfully started.
Step 5 Enter checkout.bat. If the four Ethernet ports are in OK state, all the services are started
properly.
NOTE
The configuration items in the config.ini file are described as follows:
l ostype: type of the OMU operating system (unchangeable).
l cdkey: serial No. for installing the OMU operating system (unchangeable).
l partitions: partitions of the OMU hard disk. The OMU hard disk is divided into two partitions. For
example, change c:ntfs:15000|d:ntfs:5000|e:fat32:1 to c:ntfs:15000|d:ntfs:1, in which 1 indicates
the remaining capacity of the OMU hard disk. Only the last partition can be set to 1.
l Other configuration items can be changed as required.
NOTE
The configuration items in the deploy-ipconfig.ini file are described as follows:
l The change of the internal and external IP addresses must be based on the live network conditions.
l You should end each line with a semi-colon.
NOTE
l If third-party software is to be installed, add the software name, save path, and commands to be executed
to the third-party.ini file.
l Delete the information about SQL2000 which is marked in red. Otherwise, the installation of the OMU
operating system may fail.
Step 7 Open the relevant file in D:\autoinst\site. Enter only the MAC address of ETH2 and the name
of the configuration file, as shown in Figure 5-12.
NOTE
l By default, there is a # symbol preceding the value of each MAC. This symbol is used to comment out
this statement. Delete # before the installation.
l To learn the MAC address of the ETH2 port, view the bar code of the MAC address on the OMU board,
for example, 0018821D0FE0-E5(6), which indicates that the MAC addresses of the six Ethernet
adapters on the OMU board are 0018821D0FE0, 0018821D0FE1, 0018821D0FE2, 0018821D0FE3,
0018821D0FE4, and 0018821D0FE5. You can write all these addresses in the file named site.
Step 8 Enter config.bat. When the script is successfully executed, all configurations on the server are
complete, as shown in Figure 5-13.
CAUTION
l If the system provides a prompt indicating that a service failed to start, run the config.bat
program again until services are successfully configured.
l After the config.bat program is executed, a symbol # is automatically added in front of the
value of MAC. Delete the symbol # before running the install.bat program again.
Step 9 Turn the ejector levers on the OMU board outwards. After the OFFLINE LED on the OMUa
board is ON, turn the ejector levers inwards until they are in the proper position. The OMU board
automatically restarts on the DHCP server, and the installation of the operating system starts.
CAUTION
l During the installation process, do not connect the keyboard and mouse to the portable
computer to avoid any interruption to the installation.
l The OMU board may automatically restart several times during the installation process.
l During the installation process, do not run the install.bat script. If you run the install.bat
script, the DHCP server and TFTP server will be reconfigured and the network will be
interrupted temporarily, and the installation fails.
l During the installation process, if a message reading PXE-E32:TFTP open timeout
is displayed, disable the DHCP server, TFTP server, and firewall. If the DHCP server is
enabled after you run the install.bat script repeatedly, run the install.bat stop command to
disable the DHCP service, as shown in Figure 5-14. Then, run the install.bat script again
to start the EasyInstall software.
Step 10 Enter checkout.bat to query the status of the OMU board installation.
If STATUS of MAC in the displayed window is OK, the installation of the operating system is
complete. Ten seconds after the installation, the board restarts automatically. You can now
remotely log in to the OMU board.
NOTE
Run the checkout.bat program. The STATUS of MAC in the displayed window indicates the installation
status of the OMU operating system.
l OK: the installation is complete.
l Installing: the installation is in progress.
l Waiting : the client has not sent messages to the server and that the installation is not started. If the
OMUa board is in Waiting state after the board is on for ten minutes, check that the network is connected
and that the client PC is powered on.
l Failed: the installation fails. For details, view the LOG.
----End
Prerequisites
l Before a USB storage device to switch the OMU operating system is prepared, the
communication between the local PC and the OMU must be normal. This ensures that the
Dopra Linux tool can obtain the configuration information of the target OMU.
l The virtual external IP address and external subnet gateway IP address have been obtained.
Context
The operating system of the BSC6810 is Windows Server 2003, and the operating system of the
BSC6900 is Dopra Linux. After the BSC6810 is upgraded to the BSC6900, Windows Server
2003 can be retained or switched to Dopra Linux.
After the OMU operating system is switched using the USB storage device, all the OMU data
is moved to the new operating system, including the OMU database that stores the configuration,
alarm, and platform data; performance configuration files; SSL certificate files; license files. All
the OMU applications are retained. The performance result files and log files need to be backed
up to a local PC before the OMU operating system is switched. For details about the directory
where these files are to be backed up, see table 1 in Checking the Installation Directory of
OMU Applications. You can use a file manager to back up the files. For details about the file
manager, see File Manager.
The OMU is reset when the operating system is switched. In active/standby mode, the OMU
reset interrupts Operation and Maintenance (OM) for 5 minutes. In independent mode, the OMU
reset interrupts OM for 20 minutes. The OMU reset does not affect ongoing services.
The communication between the M2000 and BSC6900 is interrupted when the OMU is reset.
The periodical traffic statistics that are to be reported to the M2000 when the OMU is being
restarted are lost. You are advised to finish preparing a USB storage device for this operation
before 24:00. If the OMU is in active/standby mode, insert the prepared USB storage device to
the standby OMU and restart the standby OMU. Then switch over the active and standby OMUs
between 24:00 and 01:00 when performance counters are not being reported to the M2000. This
prevents the loss of traffic statistics. If the OMU is in independent mode, insert the prepared
USB storage device and restart the OMU between 24:00 and 01:00 for the same purpose.
Before preparing a USB storage device, verify the device by referring to DOPRA Linux USB
Disk Certificate Guide in the directory where the Dopra Linux USB storage device is saved. If
the USB storage device is not usable, replace it. The Netac U208 (2 GB), Kingston and Sandisk
USB storage devices are recommended.
The duration for preparing a USB storage device varies based the bandwidth of the network
from the PC to the equipment room, the USB protocol, and the PC performance. The duration
listed in Table 4-2 refers to the duration for preparing a USB storage device in compliance with
the USB2.0 protocol. The duration for preparing a USB storage device in compliance with the
USB1.1 protocol takes about twice as long as preparing a USB storage device in compliance
with the USB2.0 protocol. If the duration for preparing the device requires much longer than the
listed duration, the performance of the PC in use is poor. If this occurs, restart the PC or use a
PC with a higher level of performance.
Operation Duration
Prepare a USB storage device. The duration varies based on the bandwidth
of the network from the PC to the equipment
room.
l If the network bandwidth is 1 Mbit/s or
higher:
and an independent OMU is
configured, the duration is 15 to 30
minutes.
and active and standby OMUs are
configured, the duration is 30 to 50
minutes.
l If the network bandwidth is 512 kbit/s:
and an independent OMU is
configured, the duration is 25 to 50
minutes.
and active and standby OMUs are
configured, the duration is 50 to 90
minutes.
CAUTION
l The BSC software version cannot be rolled back after the OMU operating system is switched.
l After the USB storage device is prepared, do not modify the OMU data before switching the
OMU operating system. Otherwise, the OMU data will be inconsistent with the host data.
l To ensure data synchronization between the two hard disks of the OMU, the Redundant Array
of Independent Disks (RAID) between them must be normal. If the RAID is abnormal, do
not switch the OMU operating system. To query whether the RAID is normal, run the DSP
OMUHW command.
Procedure
Step 1 Prepare a USB storage device, portable computer, and program files.
1. Prepare a USB storage device.
l The memory of the USB disk is at least 2 GB. If the BSC6900 is configured with active
and standby OMUs, two USB storage devices are required.
l The USB storage device will be formatted when it is prepared. Therefore, before using
the USB storage device, back up the data on it.
2. Prepare a portable computer.
l Check that the portable computer has the permission to read and write the USB storage
device. In addition, check that Microsoft .NET Framework 2.0 or later has been installed
on the portable computer.
NOTE
To check whether Microsoft .NET Framework 2.0 or later has been installed, choose Start >
Settings > Control Panel > Add or Remove Programs to view the components installed on
the portable computer. If Microsoft .NET Framework 2.0 or later has not been installed on the
portable computer, run dotnetfx2.0.exe under software package for preparing a USB storage
device used for switching the OMU operating system to Dopra Linux\tools.
l Table-2 lists the configuration requirements for the portable computer.
Hard 1 80 GB 10 GB
disk
CD 1 - -
drive
USB 1 - -
installat
ion
drive
Contact Huawei engineers who can obtain the installation package or patch installation
package by performing the following operation:
Log in to http://support.huawei.com/support/ and choose Software Center > Version
Software > Wireless > SingleRAN > SRAN O&M tools to download the tool.
4. Download OMU-related software.
The OMU-related software, including the psftp and PuTTY software, is used to install the
OMU applications and perform O&M on the OMU.
Contact Huawei engineers who can obtain the installation package or patch installation
package by performing the following operation:
Log in to http://support.huawei.com/support/. Choose Software Center > Controlled
Tool > Core Network Product Line > Genex CN Nastar TOOL > Tools for remote
login linux to download the psftp and PuTTY software.
5. Download the BSC6900 version installation package or patch installation package.
Contact Huawei engineers who can obtain the installation package or patch installation
package by performing the following operation:
Log in to http://support.huawei.com/support/ and choose Software Center > Version
Software > Wireless > SingleRAN > MBSC > BSC6900 > BSC6900 Product Version
> BSC6900 Software Version. Choose Software VersionVER to download the
BSC6900 version installation package.
6. Prepare the OMU.
l Log in to the LMT using the OMU virtual external IP address by referring to Logging
In to and Logging Out of the LMT. On the LMT, run the BSC6900 MML command
DSP OMUVER to query the currently running OMU BIOS version.
NOTE
If the OMU BIOS version is V013 or V031, prepare a serial cable, monitor, and USB keyboard so that
the OMU can be started from the USB storage device. For details, see Setting the First Boot Device
of the OMU to USB.
7. Check that the host data is consistent with the OMU data.
Before switching the OMU operating system, ensure that the host data is consistent with
the OMU data.
Log in to the LMT using the OMU virtual external IP address and run the BSC6900 MML
command ACT CRC to check whether the host data is consistent with the OMU data. If
they are inconsistent, the alarm ALM-20736 Data Inconsistency Between OMU and Host
is reported. Clear the alarm by referring to ALM-20736 Data Inconsistency Between OMU
and Host.
Step 2 Prepare the USB storage device for switching the OMU operating system.
1. Double-click U_creator_eng.exe to begin installing a Dopra Linux operating system on
the USB storage device, as shown in Figure 5-15.
2. Select NE List in the left pane of the window, right-click the NE list, and choose Add
NE from the shortcut menu. The dialog box shown in Figure 5-16 is displayed.
3. Enter the NE Name, select Switch from the Operate type drop-down list box, specify the
Virtual External IP and Password of Admin, and click OK. An NE is added.
NOTE
l The NE name is used to identify different NEs and only can include letter, numerals, "-", and "_."
l Password of Admin is the password the admin user uses to log in to the LMT. It is configured during
the installation of the OMU applications.
l If you select EMS Proxy IP Address and type the IP address of the EMS proxy server (for example,
M2000), the EMS proxy server will forward messages between the PC and the OMU. The port 31035
of the EMS proxy server must be opened to the PC without being shielded by network devices such
as firewalls.
l If the upgrade is implemented by using the M2000 whose software version is iManager M2000
V200R012C00SPC220 or its later patch versions, the Access Control List (ACL) needs to be
configured for the PortTrunking service on the M2000 as follows:
a. Log in to the LMT and run the MML command DSP OMU to obtain the fixed and virtual external
IP addresses of the active and standby OMUs.
b. Run the MML command LST FTPSSRV to obtain the FTP command port number, the FTP active
mode data port number, and the numerical range of the FTP passive mode data port.
c. Run the ipconfig command on a PC running the M2000 client to obtain the IP address of the M2000
client.
d. Add the M2000 client IP address to the configuration file for source IP address rules and add the
following to the configuration file for destination IP address and port rules: OMU virtual external
IP address, fixed external IP addresses of the active and standby OMUs and the port numbers 6000,
8000, 6088, and 8088 that correspond to those IP addresses as well as the numbers of ports on the
FTP server. For details, see How Do I Configure the ACL for the PortTrunking Service? in
the FAQ part of the M2000 Administrator Guide (Sun, S10). If the software version of the M2000
is iManager M2000 V200R012C00SPC230 or later, click Online Help on the M2000, and choose
Security Management > User Management > Configuration and Management of User
Security > Security Policy Management > Setting the Proxy Service ACL for more information
about adding the M2000 client IP address to the configuration file for source IP address rules.
Log in to http://support.huawei.com/support/ by using the account of a Huawei engineer. Then,
go to Core Network Product Line > Wireless-OSS > iManager M2000-II to obtain the M2000
Administrator Guide (Sun, S10).
l The NE name, external virtual IP address, and the EMS proxy IP address can be changed only after
you delete the NE and then add the NE.
l Run the MML command LST SSLCONF to query the SSL configuration information of the OMU
whose operating system is to be switched.
l In the command output, if Certificate File Name and Private Key File Name are NULL, then
select None-SSL connection in Figure 5-16.
l If Connection Type is ALL Type in the command output, determine whether the SSL connection
is required when preparing the USB flash drive for installing a DOPRA Linux operating system
based on the security requirement. If the SSL connection is not required, select None-SSL
connection as the secure transmission type in Figure 5-16. If the SSL connection is required,
determine whether the certificate file and private key file are required based on the value of
Authentication Mode.
l If Connection Type is Only SSL Connection, determine whether the certificate file and private
key file are required based on the value of Authentication Mode.
l If Authentication Mode is Verify None, select SSL connection without the certificate file and
private key file as the secure transmission type in Figure 5-16. If Authentication Mode is Verify
Peer Certificate, select SSL connection with the certificate file and private key file as the
secure transmission type in Figure 5-16.
l If SSL connection with the certificate file and private key file is selected as the secure
transmission type in Figure 5-16, you need to load the certificate file and private key file. If the
OMU whose operating system is to be switched does not use its own pre-set certificates, download
the certificate file and private key file from the OMU to the local PC by using the FtpUsr user
account. For details, see MML commands in Transferring OMU Files to a Local PC. If the
OMU uses its own pre-set certificates, you do not need to download the certificate file or private
key file. The save path for the certificate file and private key file on the OMU is \bam\version_a
\ftp\cert if the active workspace is version_a. You can run the LST OMUAREA command to
query the active workspace information.
l If you want to prepare multiple USB flash drives, it is recommended that you prepare the USB flash
drives one by one, and make a mark for each one.
4. Double-click the added NE in the left pane of the window. The window is updated, as
shown in Figure 5-17.
5. After all the information is obtained automatically, check the result and select the directory
for the version package. If there is a patch, also select the directory for the patch. Then click
OK to start the preparation for the USB storage device.
NOTE
l If a version or baseline patch is to be installed, select the V**R**C** directory of the version
installation package or the V**R**C**SPCX00 directory of the baseline patch installation
package.
l If a non-baseline patch is to be installed, select the V**R**C**SPCXYZ or
V**R**C**SPHXYZ directory of the patch installation package.
l If the link mode of OMU external Ethernet adapters fails to be obtained, query and set it by
referring to 4.1.1 Setting the Link Mode of the External OMU Ethernet Adapter and 5.2.16
Setting the Link Mode for External OMU Ethernet Adapters. Table 3 lists the mapping
between the queried link mode of OMU external Ethernet adapters and the mode of OMU external
Ethernet adapters selected in Figure 5-17.
CAUTION
l All the IP addresses shown in Figure 5-17 are obtained from the target OMU by the
Dopra Linux tool.
l If any information shown in Figure 5-17 is incorrect, suspend the operations, correct
the information on the working OMU, and continue with the operation. The information
cannot be corrected in online mode on the tool.
l The IP addresses listed in Figure 5-17 must follow the principle of planning OMU IP
addresses. For details, see 3.2 OMU IP Address Plan. Change the commissioning IP
address and commissioning subnet mask according to the real condition.
l The software version and data of only the active OMU workspace are switched when
the OMU operating system is switched. Therefore, the BSC version cannot be rolled
back if the OMU is not upgraded after the OMU operating system is switched. The host
log files, OMU log files, and traffic statistics are not retained after the OMU operating
system is switched.
l In independent mode, focus on configurations for only the active OMU. Configurations
for the standby OMU do not take effect.
l The data to be backed up includes the OMU database (which contains configuration,
alarm, and platform data), performance configuration files, SSL certificate files, and
license files.
l A directory where the tool is saved will be generated when an NE is created. The
directory name is the same as the NE name.
l If NE Name for a newly created NE is a duplicate of an already existing NE, the data
backup file directory of the existing NE will be replaced. Therefore, give each NE a
unique name. Ensure that all the files have been backed up or that the files are no longer
needed if an NE is given a duplicate name.
6. After the data backup is completed, the The data backup is completed. Continue with
preparing the USB device? message is displayed, as shown in Figure 5-18.
l Click Continue with preparing USB device to start preparing the USB storage device.
Then go to Step 2.12.
l Click Save the NE backup data, select the save path for the backup file, and click
Finish. Then go to Step 2.7.
NOTE
l If you just want to back up data or you cannot continue with preparing the USB storage device
because it cannot be identified by the PC, click Save the NE backup data to save the NE backup
data to the PC for future use. Before you click Save the NE backup data, ensure that the relevant
backup file exists in the Dopra Linux\NE Name\bk_pkg directory.
l The backup file created after you click Save the NE backup data is saved in a file folder named
after the OMU virtual external IP address of the NE.
l The backup file created after you click Save the NE backup data can be saved for preparing the
USB storage device before going to the site where the USB storage device cannot be prepared.
CAUTION
l The backup file cannot be modified after being saved on the PC. Otherwise, you cannot
prepare the USB storage device by using the local backup data of the NE.
l The saved NE data backup file does not contain information of the version or patch
installation package.
7. To prepare the USB storage device by using the local backup data, double-click
U_creator_eng.exe to start the USB storage device for installation of the Dopra Linux
operating system.
8. Select NE List in the left pane of the window, right-click the NE list, and choose Add
NE from the shortcut menu. The dialog box shown in Figure 5-19 is displayed.
9. In the dialog box shown in Figure 5-19, type the NE name and set Operate type to Use
the local backup data to create the USB device. Then click OK.
10. Double-click the added NE in the NE list on the left pane of the window, as shown in
Figure 5-20.
11. Select please select the local backup data. Then the USB storage device will automatically
obtain the backup data. After all the data is obtained, select the version package directory
and the patch directory. Then click OK to start the preparation of the USB storage device.
12. Check that the USB storage device is correct. If there is no USB storage device installed,
insert a USB storage device.
NOTE
l If multiple USB storage devices are required for multiple NEs, the USB storage devices are written
to one NE at a time. Remove the USB storage device and click Retry to start the preparation of another
USB storage device.
l After the USB storage device is prepared, remove it from the PC in secure mode to prevent the data
on it from being lost or corrupted.
13. After the preparation of the USB storage device used for switching the operating system
of the active OMU, the tool prompts you to insert another USB storage device for switching
the operating system of the standby OMU.
NOTE
l If only one OMU is configured, the standby OMU USB storage device does not need to be prepared.
l If each NE is configured with a pair of active and standby OMUs and the OMU operating system for
multiple NEs needs to be switched, label USB storage devices with the NE name and OMU slot number
to differentiate them.
14. After the preparation of the USB storage device used for switching the operating system
of the standby OMU, click Finish. The preparation for the USB storage devices is complete.
Step 3 Switch the OMU operating system by using the USB storage device.
NOTE
l Switching the operating system of active and standby OMUs is used as an example. To switch the operating
system of an OMU in independent mode, perform Step 3.1, Step 3.2, Step 3.3, Step 3.4, Step 3.5, Step
3.9 in order. In Step 3.4, you only need to check that the OMU works properly.
l In active/standby mode, the original active OMU becomes a standby OMU and the original standby OMU
becomes an active OMU after the operating systems of the OMUs are switched. This does not affect the
system.
l Check that the USB storage device can be written to before inserting it to a USB port on the OMU panel.
1. Insert the USB storage device into any of the USB ports on the panel of the standby OMU
board.
NOTE
Differentiate the active OMU from the standby OMU by checking the status of the ACT indicator on their
panels. The OMU with the ACT indicator steady on is active, and the OMU with the ACT indicator steady
off is standby.
2. Restart the OMU.
a. Log in to the OMU by using the OMU fixed external IP address. For details, see 5.2.20
Logging In to the OMU.
b. Choose Start > Shutdown > Restart.
3. Log in to the OMU 5 minutes later to determine whether the OMU operating system has
started installing from the USB storage device.
l If you fail to log in to the OMU, the OMU operating system has started to install from
the USB storage device.
l If you log in to the OMU successfully, the OMU operating system has not started
installing from the USB storage device. Prepare another USB storage device.
4. Wait 15 to 25 minutes, check the status of indicators on the OMU board to determine
whether the OMU operating system has been installed successfully (for details about the
indicator status, see step 3 in the Installing the OMU Operating System Using a USB
Flash Drive). After the operating system has been installed, use the virtual external IP
address of the OMU to log in to the LMT. After the OMU works properly (indicated on
the device panel), run the BSC6900 MML command DSP OMU to query Data-sync
state.
Expected result: Data-sync state is Data synchronization is successful.
5. Remove the USB storage device. Then restart the OMU by referring to Step 3.2.
6. Wait about 5 minutes and log in to the LMT using the OMU external virtual IP address.
After the OMU returns to normal (indicated on the device panel), run the BSC6900 MML
command DSP OMU to query Data-sync state.
Expected result: Data-sync state is Data synchronization is successful.
7. Run the BSC6900 MML command SWP OMU to switch over the active and standby
OMUs.
8. Wait about 5 minutes and log in to the LMT using the OMU external virtual IP address.
Check the status of the active and standby OMUs on the device panel.
Expected result: The active and standby OMUs are normal.
9. Run the BSC6900 MML command DSP TIME to check whether the OMU system time
is correct.
Expected result: The OMU system time is correct.
If the OMU system time is incorrect, run the MML command SET TIME to change it.
10. Insert the USB storage device into any of the USB ports on the panel of the original active
OMU board.
11. Repeat Step 3.2, Step 3.3, Step 3.4, Step 3.8 to switch the operating system of the original
active OMU.
Expected result: The active and standby OMUs are normal.
----End
Follow-up Procedure
1. Log in to the LMT. On the LMT, type the user name and password that are used before the
OMU operating system is switched and check that they can still be used for the login.
2. Run the BSC6900 MML command ACT CRC to check whether the host data is consistent
with the OMU data. If they are inconsistent, the alarm ALM-20736 Data Inconsistency
Between OMU and Host is reported. For details about how to clear the alarm, see
ALM-20736 Data Inconsistency Between OMU and Host.
3. Optional: You are advised to change the password for user root of the Dopra Linux
operating system to ensure system security after the OMU operating system is switched.
4. Optional: After the operating system is switched, the setting on the original operating
system for disabling root user remote login and OMU route forwarding will be ineffective.
You need to re-configure those functions on the new operating system by referring to 6.1
Disabling root user login with SSH and 6.2 Disabling OMU route forwarding.
Prerequisites
l The administrator password of the OMU operating system and the external fixed IP
addresses that is planned on site are available.
l You have logged in to the OMU by referring to 5.2.20 Logging In to the OMU.
l You have obtained the OMU version installation package and copied it to the OMU hard
disk through directory sharing of the hard disk by referring to 5.2.19 Uploading Files to
the OMU.
Context
l If the operating system is Dopra Linux after the BSC6810 is upgraded to the BSC6900, see
4.2.3 Optional: Installing the OMU Applications for the method of installing OMU
applications.
l If the operating system is still Windows after the upgrade from the BSC6810> to the
BSC6900, see this section for the installation method of the OMU applications.
WARNING
l After the upgrade and before OMU applications are reinstalled, record the IP addresses of
the live network. After OMU applications are reinstalled, change the IP addresses or restore
them to the historical IP addresses according to onsite requirements.
l If patches have been installed, before installing OMU applications, replace the original patch
files in the patch folder of the OMU application installation package with the patch
installation package (for example, the V900R01XC0XSPCXXX folder) saved on the local
PC.
If OMU applications have been pre-installed on active and standby OMU boards, unintall them
before installing the OMU applications of a correct version. To check whether OMU applications
have been pre-installed, do as follows:
1. Log in to the OMU by using the fixed external IP address or commissioning IP address.
For details, see 5.2.20 Logging In to the OMU.
2. Choose Start > Control Panel > Administrative Tools > Services to check whether the
omud service is available.
l If the omud service is available, OMU applications have been pre-installed. Uninstall
them by following operation steps in Uninstalling the OMU Applications.
l If the omud is service is not available, OMU applications have not been pre-installed.
Install the OMU applications following the installation procedures.
3. Log out of the OMU. For details, see 5.2.21 Logging Out of the OMU.
Procedure
Step 1 Go to the V***R***C**\install\setup directory of the version installation package and double-
click install_bam.bat. The system prompts you to type the product running mode, as shown in
the following:
NOTE
V***R***C** is an example of the version installation package. During installation, see the actual version.
[2011-05-03 10:12:32] software integrality verify begin...
[2011-05-03 10:12:42] software integrality verify end...
NOTE
The software integrity of the OMU applications is checked before they are automatically installed. The OMU
applications can be installed only if the check passes.
Step 2 Enter the product running mode and press Enter. The system prompts you to type the office
name, as shown:
# The name of office
# The name must range from 5 to 32 characters.
# The first character must be a letter and the subsequent characters can be lett
ers, digits, "-"or "_".
Please input a valid office_name :
Step 3 Enter the office name and press Enter. The system prompts you to type the language, as shown:
# The OMU language version. eg: eng/chs
Please input a valid version :
Step 4 Enter the language and press Enter. The system prompts you to type the admin password, as
shown:
# The "admin" user's password of OMU service.
# The password must range from 6 to 32 characters and consist of only letters an
d figures.
# 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 :
Step 5 Enter the admin password and press Enter. The system prompts you to type the FTP password,
as shown:
# The ftp user's password of OMU service
# The password must range from 6 to 32(characters) and consist of only letters a
nd figures.
# 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 :
Step 6 Enter the ftp password and press Enter. The system prompts you to type the external virtual
IP address, as shown:
# The virtual extranet ip.
Please input a valid virtual_extranet_ip :
NOTE
The external virtual IP address must be located on the same network segment as the external fixed IP
address. The factory setting of the external fixed IP address is 172.121.139.201 (255.255.255.0). After the
OMU applications are installed, you can change the IP addresses and subnet masks of the OMU Ethernet
adapters
Step 7 Enter the external virtual IP address and press Enter. The system prompts you to type the
OMU system type, as shown:
# The OMU system type. eg: Single/Dual
# Single : Install stand-alone system
# Dual : Install dual system. The dual-OMU system can effeciently increase the
reliability of the OMU system
Please input a valid install_type :
Step 8 Enter the OMU installation type based on the field configuration and press Enter. Table 5-6
describes the OMU installation types.
Parameter Description
Step 9 The system asks you whether to continue with the installation, as shown:
Step 10 Enter Y to install OMU applications. When the messageInstall OMU succeed! is
displayed, OMU applications are successfully installed.
Step 11 Record the information about the OMU applications installation in 5.5.1 Record Sheet of OMU
Software Installation Information.
----End
Context
After the BSC6810 is upgraded to the BSC6900, the OMU operation and maintenance is
depending on the type of the OMU operating system.
l If the OMU operating system is switched to Dopra Linux, perform maintenance and
operation for the OMU by referring to 4.3 Operating and Maintaining the OMU.
l If the OMU operating system is still Windows Server 2003, perform the steps in this section
for the OMU maintenance and operation.
Procedure
l Method 1
1. Log in to the target OMU by referring to 5.2.20 Logging In to the OMU.
2. Choose Start > Run. Then type the cmd command and press Enter to type the
command mode of the OMU.
3. Type the net stop omud command and press Enter to stop the omud.
4. Type the cd /d d:\mbsc\bam\common\services command and press Enter to
navigate to the directory where the program of the omu_backup_linker tool is saved.
5. Type the omutool dispipinfo command and press Enter. The following shows an
example of the returned information.
[Virtual IP Information]
External virtual ip / mask : 10.141.149.15 / 255.255.254.0
Internal virtual ip / mask : 80.168.3.40 / 255.0.0.0
[Fixed IP Information]
External fixed ip / mask : 10.141.149.14 / 255.255.254.0
Internal fixed ip / mask : 80.168.3.60 / 255.0.0.0
Backup channel ip / mask : 192.168.3.60 / 255.255.255.0
Debugging ip / mask : 192.168.6.60 / 255.255.255.0
[Gateway Information]
Gateway : 10.141.148.1
l Method 2
1. Log in to the active OMU by referring to 5.2.20 Logging In to the OMU.
2. Choose Start > Run. Then type the cmd command and press Enter to type the
command mode of the OMU.
3. Enter the ipconfig /all command and press Enter. The following shows an example
of the returned information.
Windows IP Configuration
4. Log in to the LMT by referring to Logging In to and Logging Out of the LMT.
5. Run the DSP OMU command to query the fixed internal IP address, fixed external
IP address, IP address of the backup channel between active and standby OMU boards,
virtual internal IP address, and virtual external IP address.
NOTE
The results from Step 3 and Step 5 show the information of all the IP addresses and subnet
masks of the OMU.
----End
Prerequisites
You have logged in to the LMT. For details, see Logging In to and Logging Out of the LMT.
Procedure
l Querying the status of the OMU subsystem
1. Run the MML command DSP OMU. The operating status of the OMU subsystem is
displayed, including the OMU operating status, fixed IP address configuration, virtual
IP address configuration, status of data synchronization, status of the internal and
external networks, and status of the backup channel.
l Querying the status of the service processes when the OMU is operational
1. Run the MML command DSP OMUMODULE. The names and status of the service
processes are displayed.
If the status of the service processes is Started, the OMU service processes are
normal.
If the status of the service processes is Stopped, the OMU service processes are
normal and not started.
If the status of the service processes is Exception, the OMU service processes are
abnormal. When active and standby OMUs are configured, the self-healing
switchover is triggered if the abnormal state persists. When an independent OMU
is configured, the OMU reports the ALM-20707 OMU Process Abort alarm.
l Querying the status of the OMU board
1. Run the MML command DSP OMUSRV. The OMU board information is displayed,
including the CPU usage, memory usage, number of logical CPUs, memory capacity,
total space of logical disks, current available space, and percentage of the available
space.
----End
Prerequisites
You have logged in to the LMT. For details, see Logging In to and Logging Out of the LMT.
Context
If an OMU board becomes faulty, query the information about the OMU board for fault location.
Procedure
l Querying the OMU working environment
1. Run the MML command DSP OMUENV. The CPU inlet temperature, memory inlet
temperature, hard disk temperature, and voltage of chips are displayed.
l Querying the OMU hardware status
1. Run the MML command DSP OMUHW. The subrack number, slot number, operating
status of the hard disk, status of Ethernet adapters and Ethernet adapter teams, and
RAID of the OMU are displayed.
----End
Prerequisites
You have logged in to the LMT. For details, see Logging In to and Logging Out of the LMT.
Procedure
Step 1 Run the LST OMUAREA command to query the version of the active and standby OMU
workspaces.
----End
Prerequisites
l You have logged in to the LMT. For details, see Logging In to and Logging Out of the
LMT.
l Active and standby OMUs are configured.
Context
Due to network or database problems, an exception may occur during data synchronization.
When this occurs, the OMUs automatically rectify the faults.
Procedure
Step 1 Run the MML command DSP OMU on the active or standby OMU. The status of data
synchronization between the active and standby OMUs is displayed.
If data synchronization is abnormal, the ALM-20704 OMU Data Synchronization Failure alarm
is reported. Clear the alarm by referring to the alarm handling suggestions.
CAUTION
When Data-sync state is Data synchronization is successful, Data synchronization not built
due to version inconsistency, or Data synchronization cannot built due to OMU failure
switchover, you are allowed to switch over the active and standby OMUs.
----End
Procedure
Step 1 Log in to the target OMU by referring to 5.2.20 Logging In to the OMU.
Step 2 Choose Start > Run. Then type the cmd command and press Enter to type the command mode
of the OMU.
Step 3 Enter the netstat -ano command and press Enter to query the occupied OMU ports. The
following shows an example of the returned information.
Active Connections
Information to the right of colon in the Local Address column indicates the occupied OMU port
numbers.
----End
5.2.7 Checking the Data Consistency Between the Active OMU and
the Standby OMU
This section describes how to check the data consistency between the active OMU and the
standby OMU after a fault-triggered switchover occurs.
Prerequisites
l You have logged in to the LMT. For details, see Logging In to and Logging Out of the
LMT.
l The OMUs work in active/standby mode.
Procedure
Step 1 Run the CMP OMUDATA command to check the consistency of alarm data, performance data,
and configuration data between the active and standby OMUs.
CAUTION
l If the active OMU data is inconsistent with the standby OMU data, run the STR
DATASYNC command to start the data synchronization between the active OMU and the
standby OMU. Wait 5 minutes then run the CMP OMUDATA command.
l If the active OMU is synchronizing the initial data with the standby OMU, the LMT displays
failure information.
Step 2 Run the CMP OMUFILE command to check the consistency of the license file, patch file, and
performance file between the active and standby OMUs.
----End
Prerequisites
You have logged in to the OMU by referring to 5.2.20 Logging In to the OMU.
Context
For the factory setting of the administrator password for Windows Server 2003, see Checklist
for the Factory Settings of the OMU Software.
NOTE
l It is recommended that you change the password at your first login and then change the password every
three months.
l Users root and db_usr must both contain the combination of the following:
l At least one lower-case letter
l At least one upper-case letter
l At least one digit
l At least one special character -?[]_+{}
The user password must have a minimum length of 8 characters and maximum length of 32 characters.
l The admin and FtpUsr user password must have a minimum length of 6 characters and maximum length
of 32 characters.
Procedure
Step 1 Right-click My Computer and choose Manage from the shortcut menu.
Step 2 On the left pane of the window, choose System Tools > Local Users and Groups > Users.
Figure 5-21 shows the interface.
Step 3 On the right pane of Figure 5-21, right-click Administrator and choose Set Password from
the shortcut menu. Figure 5-22 shows the prompted dialog box.
Step 4 Click Proceed in Figure 5-22. Figure 5-23 shows the prompted dialog box.
Step 5 Type the new password and confirm it. Record the password in the Record Sheet of OMU
Software Installation Information.
----End
Prerequisites
l You have logged in to the LMT. For details, see Logging In to and Logging Out of the
LMT.
l The OMU works in active/standby mode and the active and standby OMUs work normally
for more than 5 minutes (You can run the CMP OMUDATA and CMP OMUFILE
commands to query whether the active OMU data is consistent with the standby OMU data.
Ensure that the data on the active OMU is synchronized to the standby OMU to avoid data
loss after the switchover.)
Procedure
Step 1 Run the DSP OMU command to query the operating status of the active/standby OMUs.
If... Then...
The active and standby OMUs work properly and the data Go to Step 2.
synchronization is normal,
The active and standby OMUs do not work properly or the data End this task.
synchronization is abnormal,
Step 2 Run the SWP OMU command to manually switch over the OMUs.
Step 3 Run the DSP OMU command to query the operating status of the active OMU after the
switchover. If the active OMU works properly, the switchover is successful.
----End
Prerequisites
l The OMU is started normally.
l OMU serial cables are available. For details about the cable information, see OMU serial
cable in BSC6900 UMTS Hardware Description.
l The source and target hard disks are available.
Context
One OMU hard disk serves as the source hard disk, and the other serves as the target hard disk.
Setting RAID 1 on the hard disks synchronizes the data on the source and target hard disks,
improving data security.
RAID 1 cannot be set on an OMUc board because it is configured with one hard disk.
Procedure
Step 1 Connect the PC to the OMU serial port using the OMU serial port cable.
NOTE
If the OMU serial port cable is not available, the USB and VGA ports of the active OMU can be connected
to an external keyboard and monitor, respectively. Then starts from Step 6 to complete the configuration.
Step 2 On the PC, choose Start > All Programs > Accessories > Communications >
HyperTerminal. The dialog box shown in Figure 5-24 is displayed.
Step 3 Enter the connection name and click OK. The dialog box shown in Figure 5-25 is displayed.
Step 4 Check the connection port and click OK. The dialog box shown in Figure 5-26 is displayed.
NOTE
The parameters for the connection port must be set as shown in Figure 5-26.
Step 5 Check that the parameters for the connection port are set correctly and click OK. The window
shown in Figure 5-27 is displayed.
Option Description
Windows Server 2003 operating system 1. Log in to the target OMU by referring to 5.2.20
Logging In to the OMU.
2. Choose Start > Shutdown, click Restart, and
click OK.
Step 7 After the OMU restarts, press F4 repeatedly until the message "Press Ctrl-C to start
LSI Logic Configuration Utility" is displayed. Then press Ctrl+C. The following
shows examples of the messages displayed.
Step 8 Press Enter. The following shows examples of the messages displayed.
Adapter SAS1064
PCI Slot 00
PCI Address(Bus/Dev/Func) 05:01:00
MPT Firmware Revision 0.11.01.00-IR
SAS Address 500E0FC1:23456775
NVDATA Version 25.09
Status Enabled
Boot Order 0
Boot Support [Enabled Bios & OS]
RAID Properties
SAS Topology
Advanced Adapter Properties
Press the arrow keys to select RAID Properties and press Enter. Check the value of Status to
determine whether the RAID is correct.
l If Status is Optimal, the RAID is working properly.
l If Status is Resyncing, the RAID is synchronizing data.
NOTE
l If this is the first time that the RAID is being set on the OMU, go to Step 13.
l If this is not the first time that the RAID is being set on the OMU, go to Step 9.
Step 9 Select RAID Properties and press Enter. The following shows examples of the results that are
displayed.
Array 1 of 1
Identifier LSILOGICLogical Volume 3000
Type IM
Scan Order 2
Size(MB) 69618
Status Optimal
Manage Array
Slot Device Identifier RAID Hot Drive Pred Size
Num Disk Spr Status Fail (MB)
0 FUJITSU MAY2073rc D109 [Yes] [No] Primary --- 69618
1 FUJITSU MAY2073rc D109 [Yes] [No] Secondary --- 69618
Step 10 Select Manage Array and press Enter. The following shows examples of the results that are
displayed.
Step 11 Select Delete Array and press Enter. The following shows examples of the results that are
displayed.
Step 12 Select Y. The following shows examples of the results that are displayed.
Adapter SAS1064
PCI Slot 00
PCI Address(Bus/Dev/Func) 05:01:00
MPT Firmware Revision 0.11.01.00-IR
SAS Address 500E0FC1:23456775
NVDATA Version 25.09
Status Enabled
Boot Order 0
Boot Support [Enabled Bios & OS]
RAID Properties
SAS Topology
Advanced Adapter Properties
Step 13 Select RAID Properties and press Enter. The following shows examples of the results that are
displayed.
Step 14 Select Create IM Volume and press Enter. The following shows examples of the results that
are displayed.
Array Type:IM
Array Size(MB): -------
CAUTION
Select the source and target hard disks with caution because the data on the source hard disk can
be lost.
Step 15 Set RAID Disk to No, move the cursor to the value for RAID Disk of the source hard disk, and
press Space. The following show examples of the results that are displayed.
l If you press M, the data on the source hard disk is saved. The target hard disk copies the data
from the source disk.
l If you press D, the data is deleted from the source hard disk and a new RAID is created.
The value for RAID Disk is Yes, and the value for Drive Status is Primary.
Step 17 Select the target hard disk and press Space. An alarm is generated, as shown in the following:
WARNING! Data was found on the selected disk,this data will be lost when the array
is created!
Choose Discard configuration or Cancel Exit on the next screen to abort.
The value for RAID Disk is Yes, and the value for Drive Status is Secondary.
Step 19 Press C. The following shows the results that are displayed.
Step 20 Select Save changes then exit this menu and press Enter. The screen is refreshed, as shown
in Step 12.
Step 21 Select RAID Properties shown in Step 12 and press Enter. The following shows examples of
the results that are displayed.
Array 1 of 1
Identifier LSILOGICLogical Volume 3000
Type 1M
Scan Order 0
Size(MB) 69618
Status 2% Syncd
Manager Array
Slot Device Identifier RAID Hot Drive Pred Size
Num Disk Spr Status Fail (MB)
0 FUJITSU MAY2073rc D109 [Yes] [No] Primary --- 69618
1 FUJITSU MAY2073rc D109 [Yes] [No] Secondary --- 69618
Step 22 Check that the RAID 1 is set correctly, and then press Esc repeatedly until the following
messages are displayed:
Step 23 Select Exit the Configuration Utility and Reboot and press Enter. RAID 1 is successfully set
on the OMU hard disks and the OMU restarts.
----End
Prerequisites
l You have logged in to the LMT. For details, see Logging In to and Logging Out of the
LMT.
l When the OMU works in active/standby mode, the active and standby OMUs work
normally. In addition, no MML commands are executed and no scheduled tasks are
triggered. (You can query the data consistency using the CMP OMUDATA and CMP
OMUFILE commands to ensure that the data on the active OMU is synchronized to the
standby OMU.)
Context
Do not use this command for other scenarios.
Procedure
l Switching over the active/standby OMU workspaces in single-OMU mode
1. Run the SWP OMUAREA command and set Target OMU to ACTIVE (Active
OMU) to switch over the active and standby workspaces on the OMU.
2. Run the RST BSC command to reset the BSC so that the OMU data is consistent with
the host data.
l Switching over the active/standby OMU workspaces in dual-OMU mode
1. Run the SWP OMUAREA command and set Target OMU to STANDBY (Standby
OMU) to switch over the active and standby workspaces on the active OMU.
2. Run the SWP OMUAREA command and set Target OMU to ACTIVE (Active
OMU) to switch over the active and standby workspaces on the active OMU.
3. Run the RST BSC command to reset the BSC so that the OMU data is consistent with
the host data.
NOTE
Switchover of the active and standby OMU workspaces will interrupt the BSC6900 O&M for
3 minutes.
----End
Prerequisites
You have logged in to the OMU by referring to 5.2.20 Logging In to the OMU.
Procedure
Step 1 Choose Start > Settings > Control Panel on the OMU.
Step 2 Double-click System on the pop-up interface.
Step 3 Click the General tab on the pop-up interface.
Step 4 Check whether Microsoft Windows Server 2003, Standard Edition, and Service Pack 2 are
displayed in the System list on the interface.
Option Description
The displayed content is Microsoft Shows that Windows Server 2003 is installed
Windows Server 2003, Standard Edition, successfully and the patch is Windows Server
and Service Pack 2. 2003 Service Pack 2.
The displayed content is not Microsoft Shows that Windows Server 2003 is not
Windows Server 2003, Standard Edition, installed successfully. You need to reinstall the
and Service Pack 2. operating system. For details, see 5.1.2
Switching the OMU Operating System.
----End
Prerequisites
l You have logged in to the LMT. For details, see Logging In to and Logging Out of the
LMT.
l The OMUs work in active/standby mode.
Context
After running the CMP OMUDATA command, you can manually synchronize the data of the
standby OMU with that of the active OMU if the data is inconsistent.
Procedure
Step 1 Run the STR DATASYNC command to start synchronizing the data of the standby OMU with
that of the active OMU.
NOTE
Successful running of the command only indicates a successful start to the data synchronization procedure
between the active and standby OMUs. To check whether the data synchronization succeeds, run the DSP
OMU command and query Data-sync state.
----End
Prerequisites
l You have logged in to the LMT. For details, see Logging In to and Logging Out of the
LMT.
l The OMUs work in active/standby mode.
l The data of the standby OMU is being synchronized with that of the active OMU.
Procedure
Step 1 Run the STP DATASYNC command to stop the data synchronization between the active and
standby OMUs.
NOTE
Running this command leads to asynchronous data between the active and standby OMUs. The data between
the active and standby OMUs can be still asynchronous even after an OMU switchover. You can restart data
synchronization only by running the STR DATASYNC command.
----End
Prerequisites
You have logged in to the OMU by referring to 5.2.20 Logging In to the OMU.
Context
You can use the portable computer to remotely log in to the OMU by connecting the computer
to the ETH2 port on the panel of the OMUa board. The default IP address of the ETH2 port is
192.168.6.50.
Procedure
Step 1 Right-click My Network Places and choose Properties from the shortcut menu. The Network
Connections window is displayed, as shown in Figure 5-28 .
NOTE
The name of the external Ethernet adapter team has been displayed as External Network Team; therefore, it
does not need to be renamed.
Step 2 In the Network Connections window, rename the local area connections with the Device
Name of TEAM: Internal Network Team to Internal Network Team.
Step 3 Double-click the network_identify.js tool for identifying Ethernet adapters in the C:
\DRIVERS path. An Ethernet adapter can also be called a Network Interface Card, or NIC. The
interface shown in Figure 5-29 is displayed.
NOTE
NIC Name in Figure 5-29 indicates the name of each local area connection in the Network
Connections window.
Step 4 Rename the local area connections according to the rules shown in Table 5-7.
ETH1 Eth1(External)
ETH0 Eth0(External)
ETH5-SCU6 Intel0(Internal)
ETH4-SCU7 Intel1(Internal)
ETH3-UPDATE FE(Spare)
ETH2 Eth2(LocalMaintain)
Figure 5-30 shows the Network Connections window after the renaming is complete.
----End
5.2.16 Setting the Link Mode for External OMU Ethernet Adapters
This section describes how to set the link mode of the external OMU Ethernet adapters so that
it is the same as that of the LAN switch.
Prerequisites
The link mode, duplex mode, and rate of the LAN switch have been acquired.
Context
There are two link modes of the LAN switch: force mode and auto-negotiation mode. The link
mode of the OMU external Ethernet adapter must be consistent with that of the LAN switch.
If the link mode of the external Ethernet adapters of the OMU is inconsistent with that of the
LAN switch, the network may be interrupted. If the link mode of the LAN switch is specified,
the link mode of the external Ethernet adapter of the OMU should also be specified.
If active and standby OMUs are configured, perform the following steps on both the active and
standby OMUs:
NOTE
l The following procedure assumes that the link mode of the external Ethernet adapter is force mode and
the adapter works at 100 Mbit/s in full duplex mode.
l The following procedure assumes that version_a is the active workspace of the OMU. To query the
active workspace of the current OMU, run the LST OMUAREA command.
Procedure
Step 1 Connect the PC to the commissioning Ethernet port of the OMU and log in to the OMU by using
the commissioning IP address. For details how to log in to the OMU, see5.2.20 Logging In to
the OMU.
Step 2 Click Start > Settings > Control Panel > Network Connections. The Network
Connections window is displayed.
Step 3 Double-click Eth1(External). The interface shown in Figure 5-31 is displayed.
Step 5 Click Configure in the General tab. The Broadcom NetXtreme Gigabit Ethernet #2
Properties interface is displayed.
Step 6 Click the Advanced tab and choose Property > Speed & Duplex on the left side, as shown in
Figure 5-33.
Step 7 Select the same link mode as that of the LAN switch from the Value list box and click
Confirm to end the setting.
CAUTION
The link mode of a Gigabit Ethernet adapter must be auto-negotiation and it is invalid to set the
link mode to 1000BASE-TX.
Step 8 Perform Step 2 to Step 7 again to configure the link mode of Eth0(External).
NOTE
The value is the link mode for external Ethernet adapters of the OMU, which can be set to Auto, 10 Mb
Full, 10 Mb Half, 100 Mb Full, and 100 Mb Half.
NOTE
The link mode of Eth0(External) and that of Eth1(External) must be the same.
Step 9 Choose Start > Run. Type cmd in the displayed dialog box and press Enter. The Command
Prompt window is displayed.
Prerequisites
l The OMU starts normally.
l The OMU is locally configured with a keyboard and a monitor.
l The OMU serial cable has been obtained. For details about the OMU serial cable, see OMU
serial cable.
l The USB storage device has been inserted to the USB port on the OMUa board.
Context
There are two methods for starting the OMU:
1. Connecting the OMU to a PC by using the HyperTerminal program on the PC.
2. Directly connecting the OMU to the keyboard and monitor.
NOTE
This section is designed for OMUa board and uses the OMUa board as an example. An OMUc board is started
from a USB port by default.
Procedure
l Connecting the OMU to a PC by using the HyperTerminal program on the PC
(recommended)
1. Connect the PC to the OMU serial port by using the OMU serial cable.
2. On the PC, choose Start > All Programs > Accessories > Communications >
HyperTerminal. The dialog box shown in Figure 5-34 is displayed.
3. Enter the connection name and click OK. The dialog box shown in Figure 5-35 is
displayed.
4. Check the connection port and click OK. The dialog box shown in Figure 5-36 is
displayed.
NOTE
The parameters for the connection port must be set as shown in Figure 5-36.
5. Check that the parameters of the connection port are correct and click OK. The
window shown in Figure 5-37 is displayed.
8. Press the arrow keys to select Boot. The window is updated, as shown in Figure
5-39.
9. Press the arrow keys to select Boot Device Priority and press Enter. The window is
updated, as shown in Figure 5-40.
10. Press the arrow keys to select 1st Boot Device and press Enter. The window is
updated, as shown in Figure 5-41.
11. Press Esc, select Exit, and press Enter. The window is updated, as shown in Figure
5-42.
12. Press the arrow keys to select Save Changes and Exit and press Enter. The changes
are saved. Exit the setting.
l Connecting the OMU to the keyboard and monitor directly
1. Directly connect the keyboard to the USB port and the monitor to the VGA port on
the OMU.
2. Log in to the LMT. Run the RST OMU command with Reset Type set to HARD.
Then reset the target OMU. The BIOS Setup screen is displayed on the monitor, as
shown in Figure 5-43.
5. Use the arrow keys on the keyboard to select Boot Device Priority and press Enter.
6. Use the arrow keys on the keyboard to select 1st Boot Device and press Enter. Set
the first boot device of the OMU operating system to USB, as shown in Figure
5-45.
----End
Context
If active and standby OMUs are configured, uninstall the SQL Server 2000 on both active and
standby OMUs.
Exit all the applications including Windows NT event viewer and register editor before
uninstalling the SQL Server 2000. You are advised to perform the operation during off-peak
traffic hours.
Procedure
Step 1 Log in to the target OMU by referring to 5.2.20 Logging In to the OMU.
Step 2 On the OMU, choose Start > Control Panel > Add or Remove Programs, the Add or Remove
Programs window is displayed.
Step 3 Select Microsoft SQL Server 2000 and click Change/Remove to finish the installation, as
shown in Figure 5-46.
----End
Prerequisites
l The OMU is started normally.
l The fixed IP address of the external network, virtual IP address of the external network, or
commissioning IP address of the OMU are available. For the IP addresses of the OMU, see
the Record Sheet of OMU Software Installation Information.
Context
This task uploads the version installation package from a local PC to the OMU.
Procedure
Step 1 5.2.20 Logging In to the OMU.
Step 2 Set up a new folder on the OMU. Right-click the folder and choose Sharing and Security. The
Program Files Properties dialog box is displayed.
Step 3 In the Program Files Properties dialog box, select Share this folder and click OK.
Step 4 Choose StartRun on the local PC. Enter \\IP address of the OMU, input the user name and
password in the displayed dialog box, and click OK.
Step 5 Copy the files to be uploaded to the target OMU directory that holds the files.
----End
Prerequisites
l The OMU is started normally.
l The computer for remote login to the OMU is installed with an operating system of
Windows XP or later versions.
l The computer for remote login to the OMU works normally and is connected to the OMU
external network properly.
l The fixed IP address of the external network, virtual IP address of the external network, or
commissioning IP address of the OMU is obtained. For the IP addresses of the OMU, see
the Record Sheet of OMU Software Installation Information.
l The computer for remote login to the OMU and the IP addresses of OMU external network
are on the same network segment.
Context
l The OMU can be connected to only one computer by using the mstsc.exe program.
l The mstsc.exe program by running which you log in to the OMU should have the console
parameter. Otherwise, you cannot log in to the OMU.
NOTE
If the operating system of the computer for remote login to the OMU is Windows XP SP3, run the mstsc.exe
program with the admin parameter. That is, type mstsc /admin instead of mstsc /console.
Procedure
Step 1 Choose Start > Run on the computer used for remote login to the OMU. The Run dialog box
is displayed.
Step 2 Type mstsc /console and click Confirm. The Remote Desktop Connection dialog box shown
in Figure 5-47 is displayed.
CAUTION
When typing mstsc /console, include a space between mstsc and /console.
l Before starting OMU applications, type the fixed external IP address of the OMU.
l After the OMU applications start, type the fixed or virtual external IP address. The former is preferred.
l If you are performing local commissioning, type the commissioning IP address of the OMU.
l If the PC cannot be connected to the OMU by using either the fixed or virtual external IP address,
connect the PC to the commissioning Ethernet port on the OMU and type the commissioning IP address
of the OMU.
l You are advised to log in to the OMU using the external fixed IP address, external virtual IP
address, and commissioning IP address in sequence.
Step 4 Type the administrator user name and password and click Confirm based on the interface
message. The login is complete.
NOTE
It is recommended that you change the password at your first login and then change the password every three
months.
----End
Prerequisites
You have logged in to the OMU by referring to 5.2.20 Logging In to the OMU.
Context
CAUTION
l Do not log out of the OMU by directly closing the desktop used for the remote login to the
OMU. Otherwise, the OMU operating system resources may not be fully released, and the
use of the OMU can be affected.
l Do not log off from the OMU directly. Otherwise, OMU processes will be abnormal.
l Shutting down the OMU will stop all the OMU services. If this occurs, you must restart the
OMU at the local end.
Procedure
Step 1 Choose Start > Close. The dialog box shown in Figure 5-48 is displayed.
----End
Prerequisites
You have logged in to the LMT. For details, see Logging In to and Logging Out of the LMT.
Context
l The OMU operating system is restarted after the OMUa board is reset. If the OMUa board
is reset successfully, the faults of the OMU operating system or applications can be rectified.
l All the service processes are disrupted after the OMU applications are reset. If the OMUa
board is reset successfully, the faults of the OMU applications can be rectified.
l Resetting a specified OMU service process interrupts the service of the process for a while.
Procedure
l Reset the OMUa board/OMU applications
1. Run the RST OMU command.
If Reset Type is set to SOFT, only the OMU applications are reset. The OMU
operating system is not restarted.
If Reset Type is set to HARD, the OMU operating system is restarted.
NOTE
l When the OMU works in single-OMU mode, set the Reset Target to ACTIVE.
l When the OMUs work in dual-OMU mode, the active OMU is reset if you set the Reset
Target to ACTIVE.
l When the OMUs work in dual-OMU mode, the standby OMU is reset if you set the Reset
Target to STANDBY.
l Reset a specified service process
1. Run the RST OMUMODULE command and specify Reset Target and Module
Name to reset the specified OMU service process.
----End
Prerequisites
You have logged in to the LMT. For details, see Logging In to and Logging Out of the LMT.
Procedure
Step 1 Run the MML command DSP OMUSRV to query the available space of the partitions on the
OMU hard disk.
l If the available space of any partition on the OMU hard disk is less than 20%, perform the
following steps:
1. Back up the files on the partition that need to the saved to a hard disk of a computer by
referring to Transfer OMU Files to a Local Computer.
2. Log in to the target OMU by referring to 5.2.20 Logging In to the OMU.
3. On the local computer, choose Start > Run, enter cmd, and click OK.
4. Run the cd /d Disk:\Target Directory command to navigate to the directory where the
files to be deleted are saved.
5. Run the del File name or rmdir Folder name command to delete the useless files.
l If the available space of each partition is greater than or equal to 20%, this task is complete.
----End
Prerequisites
l The firewall on the portable computer has been disabled.
l The OMU applications are started.
Procedure
Step 1 Start the file manager on the LMT by referring to File Manager in the BSC6900 UMTS LMT
User Guide.
----End
Prerequisites
You have logged in to the OMU by referring to 5.2.20 Logging In to the OMU.
Procedure
Step 1 Click Start > Settings > Control Panel to type the Control Panel interface.
Step 2 Double-click Administrative Tools > Services to type the Services interface.
Step 3 Check the Status of omud to see whether the OMU is providing services.
Option Description
----End
Prerequisites
l You have logged in to the OMU by referring to 5.2.20 Logging In to the OMU.
l OMU applications are installed. For details, see 5.1.3 Optional: Installing OMU
Applications.
Procedure
l To start the omud using commands, perform the following steps:
1. Choose Start > Run. Then type the cmd command and press Enter to type the
command mode of the OMU.
2. Run the net start omud command to start the omud.
l To start the omud using menus, perform the following steps:
1. Choose Start > Settings > Control Panel to type the control panel interface.
2. Double-click Administrative Tools > Services to type the Services interface, as
shown in Figure 5-50.
3. Select omud.
Prerequisites
l You have logged in to the OMU by referring to 5.2.20 Logging In to the OMU.
l OMU applications are installed. For details, see 5.1.3 Optional: Installing OMU
Applications.
Context
CAUTION
l When the omud is stopped, all the OMU service processes will also stop. In turn, the OMU
stops providing services for the BSC6900. Therefore, perform this task with caution.
l If a fixed external IP address is configured for the OMU, stopping the omud will make the
virtual external IP address ineffective. In this situation, a user can log in to the OMU by using
the fixed external IP address if an independent OMU is configured. If the OMUs work in
active/standby mode, the virtual external IP address of the original standby OMU becomes
effective after the active OMU is stopped.
l If no fixed external IP address is configured for the OMU, the virtual external IP address is
still effective after you stop the omud.
Procedure
l To stop the omud through commands, do as follows:
1. Choose Start > Run. Then type the cmd command and press Enter to type the
command mode of the OMU.
2. Type the net stop omud command and press Enter to stop the omud.
l To stop the omud through menus, do as follows:
1. Choose Start > Settings > Control Panel to type the control panel interface.
2. Double-click Administrative Tools > Services to type the Services interface, as
shown in Figure 5-51.
3. Select omud.
----End
Prerequisites
l OMU applications are installed. For details, see 5.1.3 Optional: Installing OMU
Applications.
Context
l If OMU applications are installed on both the active and standby OMU workspaces,
uninstall the OMU applications on the standby workspace before uninstalling them on the
active workspace.
l When the BSC6900 is configured with active and standby OMUs, uninstall the OMU
applications on both the active and standby OMUs.
l If there is only the active workspace on the OMU, the system will prompt you to uninstall
only the OMU applications on the active workspace.
NOTE
Uninstalling the OMU applications from an OMU will cause all the data in the OMU to be lost. You are advised
to back up system data on the OMU before the uninstalling by referring to Backing Up the System Data.
Procedure
Step 1 Log in to the standby OMU by using the fixed external IP address or the commissioning IP
address. For details, see Logging In to the OMU.
Step 2 Choose Start > Run. Then type the cmd command and press Enter to type the command mode
of the OMU..
Step 3 Type the net stop omud command and press Enter to stop the omud..
Step 4 Click Start > Run and the Run interface is displayed.
Step 5 In the Run interface, run the uninstall_bam command and click OK.
If... Then...
The OMU applications are installed in only An interface is displayed, as Figure 5-52
the active workspace shows.
The OMU applications are installed in both An interface is displayed, as Figure 5-53
the active and standby workspaces shows.
Step 6 Type Y, and press Enter until the Uninstall OMU succeed! message is displayed.
If... Then...
The OMU applications are installed only OMU applications are uninstalled. This task is
in the active workspace completed.
The OMU applications are installed in 1. Go to Step 5 after uninstalling the OMU
both the active and standby workspaces applications in the standby workspace.
2. Perform Step 6 to uninstall the OMU
applications in the active workspace. This
task is completed.
Step 7 Log in to the active OMU using the fixed external IP address or commissioning IP address. Then
perform Step 2 through Step 6 again.
----End
Context
The omu_backup_linker tool is used in the following scenarios:
l When an OMUa board is damaged, it needs to be replaced with a new one. The data on the
damaged OMUa board needs to be backed up and restored on the new OMUa board.
l The OMU data needs to be backed up in routine maintenance.
l When the OMU database collapses or an OMU upgrade fails, the latest OMU data is
restored by using the omu_backup_linker tool.
Context
l If an independent OMU is configured, log in to the OMU to start the omu_backup_linker
tool.
l If active and standby OMUs are configured, log in to the active OMU to start the
omu_backup_linker tool.
Procedure
Step 1 Log in to the target OMU by referring to 5.2.20 Logging In to the OMU.
Step 2 Choose Start > Run. Then type the cmd command and press Enter to type the command mode
of the OMU.
Step 3 Type the cd /d d:\mbsc\bam\common\services command and press Enter to navigate to the
directory where the program of the omu_backup_linker tool is saved.
Step 4 Type the omu_backup_linker.exe command and press Enter. An interface is displayed, as
shown in Figure 5-54.
----End
Prerequisites
l Prerequisites for the backup by using MML commands:
You have logged in to the LMT. For details, see Logging In to and Logging Out of the
LMT.
l Prerequisites for the backup by using the omu_backup_linker tool:
You have logged in to the OMU by referring to 5.2.20 Logging In to the OMU.
Context
CAUTION
l When the OMU works in active/standby mode, the system data must be backed up on the
active OMU.
l You must back up the OMU data manually to avoid a system data backup failure before
capacity expansion, upgrade, or a software loading.
Procedure
l Backing up the system data through an MML command
1. Run the BKP DB command with Path of Backup File and Backup File Name set to
appropriate values to back up the data in the specified directory on the OMU hard
disk.
2. Obtain the backup data file from the specified directory by referring to Transferring
OMU Files to a Local PC.
l Backing up the data by using the omu_backup_restore_tool
1. Choose Start > Run. Then type the cmd command and press Enter to type the
command mode of the OMU.
2. Type the cd /d d:\mbsc\bam\common\services command and press Enter to
navigate to the directory where the program of the omu_backup_linker tool is
saved..
3. Type the backup command and press Enter in the interface, as shown in Figure
5-55.
4. Type the save path and names of the backup files, and then press Enter. The system
data starts to be backed up. After the backup is complete, a message is displayed,
indicating whether the backup is successful. If the backup is successful, the message
"Backup OMU database succeed!" is displayed on the interface, as shown
in Figure 5-56.
----End
Context
Restoring the BSC6900 system data will interrupt services on the BSC6900. After the system
data is restored, the data on the host will be inconsistent with the data on the OMU. As a result,
services will be greatly impacted. Therefore, you are advised to restore the system data in the
early morning hours when traffic volume is low.
This chapter describes how to restore data by using the following methods:
l If an MML command is used to restore data, only the BSC6900 configuration data is
restored.
l If the backup restoration tool is used to restore data, all BSC6900 data is restored, including
configuration data, alarm data, performance data, operating logs, administrator account,
authority information, and product information.
NOTE
This document uses the OMU in active/standby mode as an example. If an OMU is in independent mode, skip
operations on the standby OMU.
Procedure
l Restoring the system data through an MML command
1. Run the LST BKPFILE command to query data backup files saved in the OMU
active workspace installation directory\data\backup directory.
2. Run the RTR DB command to restore configuration data on the OMU.
l Restoring the system data by using the omu_backup_restore_tool
1. (Optional) If the OMUs work in active/standby mode, stop the data synchronization
between the active and standby OMUs by referring to 5.2.14 Stopping the
Synchronization of the Data of the Active and Standby OMUs
2. Log in to the active and standby OMUs by referring to 5.2.20 Logging In to the
OMU.
3. Choose Start > Run. Then type the cmd command and press Enter to type the
command mode of the OMU. on the active and standby OMUs.
4. Type the net stop omud command and press Enter to stop the omud. on the active
and standby OMUs.
5. Restore data in the original active OMU using the omu_backup_linker tool.
a. Choose Start > Run. Then type the cmd command and press Enter to type the
command mode of the OMU.
b. Type the cd /d d:\mbsc\bam\common\services command and press Enter to
navigate to the directory where the program of the omu_backup_linker tool is
saved..
e. Enter the save path and names of the backup files and press Enter. The system
data starts to be restored. The interface informs you of the result. If the system
data is restored successfully, the message Restore OMU database
succeed! is displayed on the interface, as shown in Figure 5-58.
After data restoration, check whether the BSC6900 host data is consistent with the OMU data.
If no, load the restored data to the BSC6900 host boards.
a. Run the ACT CRC command to check whether the host data is consistent with
the OMU data.
If the data is consistent, end this task.
If the data is inconsistent, go to 10.2.
b. Run the FMT DATA command to format the data in the OMU database so that
the data can be loaded into the host.
c. If data inconsistency occurs in only one subrack, run the RST SUBRACK
command with Subrack No. specified to reset this subrack. If data inconsistency
occurs in multiple subracks, run the RST BSC command to reset the BSC.
11. (Optional, required only for Step 1) Run the MML command STR DATASYNC to
start data synchronization between the active and standby OMUs.
----End
Prerequisites
l OMU applications are installed. For details, see 5.1.3 Optional: Installing OMU
Applications.
Procedure
Step 1 Log in to the target OMU by referring to 5.2.20 Logging In to the OMU.
Step 2 Choose Start > Run. Then type the cmd command and press Enter to type the command mode
of the OMU.
Step 3 Enter the cd /d d:\mbsc\bam\version_a\bin\bam command and press Enter to navigate to the
directory where the program of the omutool is saved.
Step 4 Type the omutool.exe command and press Enter to start the omutool.
Step 5 Enter the omutool -h command and press Enter to view the help information.
----End
Prerequisites
l You have logged in to the LMT, and queried the slot No. for the OMU by running the LST
BRD command.
l You have logged in to the LMT, and queried whether the OMU is in single-OMU or dual-
OMU mode by running the DSP OMU command.
l You have logged in to the LMT, and queried the OMU version and workspace information
by running the LST OMUAREA command.
l You have logged in to the LMT and queried the OMU service mode by running the LST
MBSCMODE command.
Context
l If the working mode is changed from independent mode to active/standby mode, apply the
settings to both the active and standby OMUs. If the working mode is changed from active/
standby mode to independent mode, apply the settings to only the new active OMU.
l If the working mode of the OMU is changed from independent mode to active/standby
mode, ensure that the operating system, software version, and board type of the active
OMU are the same as those of the standby OMU. In addition, the slot number of the active
OMU and that of the standby OMU have an active/standby relationship.
l If the working mode of the OMU is changed from active/standby mode to independent
mode, you should run the MML command DSP OMU to ensure that the Data-sync
state is Data synchronization is successful and run the MML command
CMP OMUFILE to ensure that Compare result is consistent.
Procedure
l Switching the OMU from the independent mode to the active/standby mode (OMU
applications are not installed on the OMU to be added).
1. Insert an OMUa/OMUc board into the standby slot by referring to Installing the
OMUa/OMUc/SAUa/SAUc Boards or Installing the OMUc Boards in the BSC6900
UMTS Installation Guide.
2. Log in to the standby OMU using the fixed external IP address by referring to 5.2.20
Logging In to the OMU.
3. Install OMU applications on the standby OMU. For details, see 5.1.3 Optional:
Installing OMU Applications.
NOTE
You must select active/standby mode in the process of installing the OMU applications for the
standby OMU.
4. Change the IP addresses and subnet masks of the standby OMU to ensure that the
fixed internal IP addresses, fixed external IP addresses, IP address of the backup
channel between active and standby of OMUs comply with the planning principle for
the IP addresses and do not conflict with each other. For details about changing IP
addresses, see Changing IP Addresses of OMU Ethernet Adapters and Their
Subnet Masks.
5. Choose Start > Run. Then type the cmd command and press Enter to type the
command mode of the OMU. on the original active OMU.
6. Type the net stop omud command and press Enter to stop the omud. on the original
active OMU.
7. Enter the cd /d d:\mbsc\bam\version_a\bin\bam command and press Enter to
navigate to the directory where the program of the omutool is saved on the original
active OMU.
8. Run the omutool dualmode dual command on the original active OMU to set the
working mode of the OMU to active/standby mode.
9. Run the net start omud command to start the omud on the original active OMU.
10. Five minutes after the original active OMU has been started, start the omud on the
standby OMU.
WARNING
You should start the standby OMU 5 minutes after the active OMU is started to keep
the two OMUs from competing for the active state. This helps avoid data loss.
11. Change the operating system password on the standby OMU to that of the original
active OMU by referring to 5.2.8 Changing the Administrator Password for the
Operating System.
12. Run the ADD BRD command on the LMT to add an OMUa or OMUc board.
13. Run the MML command DSP OMU on the LMT and check whether the value for
Data-sync state is Data synchronization is successful.
14. Connect an Ethernet cable to the Ethernet port on the added OMU.
l Switching the OMU from the independent mode to the active/standby mode (OMU
applications are installed on the OMU to be added).
1. Log in to the original active OMU by using the fixed external IP address by referring
to 5.2.20 Logging In to the OMU.
2. Choose Start > Run. Then type the cmd command and press Enter to type the
command mode of the OMU. on the original active OMU.
3. Type the net stop omud command and press Enter to stop the omud. on the original
active OMU.
4. Enter the cd /d d:\mbsc\bam\version_a\bin\bam command and press Enter to
navigate to the directory where the program of the omutool is saved on the original
active OMU.
5. Run the omutool dualmode dual command on the original active OMU to set the
working mode of the OMU to active/standby mode.
6. Run the net start omud command to start the omud on the original active OMU.
7. Insert an OMUa/OMUc board in the standby slot 5 minutes after the original active
OMU is started.
WARNING
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.
8. Set the working mode of the standby OMU to active/standby mode by repeating Step
1 through Step 5.
9. Change the IP addresses and subnet masks of the standby OMU to ensure that the
fixed internal IP addresses, fixed external IP addresses, IP address of the backup
channel between active and standby of OMUs comply with the planning principle for
the IP addresses and do not conflict with each other. For details about changing IP
addresses, see Changing IP Addresses of OMU Ethernet Adapters and Their
Subnet Masks.
10. Start the omud on the standby OMU.
11. Change the operating system password on the standby OMU to that of the original
active OMU by referring to 5.2.8 Changing the Administrator Password for the
Operating System.
12. Run the ADD BRD command on the LMT to add an OMUa or OMUc board.
13. Run the MML command DSP OMU on the LMT and check whether the value for
Data-sync state is Data synchronization is successful.
14. 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 OMUa or OMUc board.
2. Log in to the active and standby OMUs by using the fixed external IP address by
referring to 5.2.20 Logging In to the OMU.
3. Choose Start > Run. Then type the cmd command and press Enter to type the
command mode of the OMU. on the active and standby OMUs.
4. Type the net stop omud command and press Enter to stop the omud. on the active
and standby OMUs.
5. Run the poweroff command on the OMU to be removed to power off the OMU.
6. Remove the OMUa/OMUc board to be removed by referring to step 2 to step 5
inScenario: Old and New OMU Boards Running the Same OS.
7. Enter the cd /d d:\mbsc\bam\version_a\bin\bam command and press Enter to
navigate to the directory where the program of the omutool is saved on the active
OMU.
8. Run the omutool dualmode single command on the working OMU to set the working
mode of the OMU to single-OMU mode.
9. Run the net start omud command to start the omud on the active OMU.
----End
Context
If the OMU is in active/standby mode, change the IP addresses and subnet masks of the Ethernet
adapters on both the active and standby OMUs. You are advised to first change the IP addresses
and subnet masks of the Ethernet adapters for the standby OMU before changing those for the
active OMU.
NOTE
This task describes how to change all the IP addresses and subnet masks for the OMU. You can perform required
steps to fit onsite needs.
l Single-OMU mode: Stop the omud before the change and start the omud after the change.
l Dual-OMU mode: Stop the standby omud and then the active omud before the change. Start the active omud
and then the standby omud after the change.
For details about the Ethernet adapter binding relationship, see 3.1 OMU Ethernet Adapter
Configuration.
Procedure
Step 1 Log in to the OMU by referring to 5.2.20 Logging In to the OMU.
Step 2 Choose Start > Run. Then type the cmd command and press Enter to type the command mode
of the OMU..
Step 3 Type the net stop omud command and press Enter to stop the omud..
Step 4 Enter the cd /d d:\mbsc\bam\version_a\bin\bam command and press Enter to navigate to the
directory where the program of the omutool is saved.
Step 5 The omutool dispipinfo command is used to query the IP address and subnet mask of the OMU.
For example, type the following command and press Enter to query the IP address and subnet
mask of the OMU:
omutool dispipinfo
Step 6 The omutool innercard IP address command is used to change the fixed internal IP address.
For example, type the following command and press Enter to change the fixed internal IP
address:
omutool innercard 80.168.3.60
Step 7 The omutool innervip IP address is used to change the virtual internal IP address.
For example, type the following command and press Enter to change the virtual internal IP
address:
omutool innervip 80.168.3.40
NOTE
l The fixed and virtual internal IP addresses must be in the same network segment. If the network segment
of the fixed internal IP address is changed to be different from that of the virtual internal IP address, you are
prompted to change the virtual internal IP address. If the network segment of the internal IP address is
changed to be different from that of the fixed internal IP address, you are prompted to change the fixed
internal IP address.
l When you change the fixed and virtual internal IP addresses, the corresponding subnet masks are created
automatically.
l If you change the fixed and virtual internal IP addresses for the first time, perform the following additional
steps:
1. Run the SET SUBNET command to set the BSC6900 subnet number so that it is consistent with the
number of the network segments on which the fixed internal IP address and virtual internal IP address
are located.
2. Remove the SCUa board and reinstall it in the MPS. Then, reset the MPS to validate the new fixed and
virtual internal IP addresses.
l After these two steps are performed, the OMU can communicate with the BSC6900 host boards normally.
Step 8 The omutool extercard IP address subnet mask (gateway IP address) command is used to
change the fixed external IP address and subnet mask.
For example, type the following command and press Enter to change the fixed external IP
address and subnet mask:
omutool extercard 10.161.10.100 255.255.255.0
CAUTION
Before changing the fixed external IP address, virtual external IP address, and external gateway
IP address, log in to the OMU using the commissioning IP address.
Step 9 The ./omutool extervip IP address subnet mask (gateway IP address) command is used to
change the virtual external IP address and subnet mask.
For example, type the following command and press Enter to change the virtual external IP
address and subnet mask:
omutool extervip 10.161.10.102 255.255.255.0
NOTE
l After the virtual external IP address and mask are changed, run the RMV EMSIP command and then the
ADD EMSIP command to update the virtual external IP address and mask that are recorded in the OMU
database.
l The fixed and virtual internal IP addresses must be in the same network segment. If the network segment
of the fixed external IP address is changed to be different from that of the virtual internal IP address, you
are prompted to change the virtual external IP address. If the network segment of the virtual external IP
address is changed to be different from that of the fixed external IP address, you are prompted to change the
fixed external IP address.
l After the fixed external IP address, virtual external IP address, and gateway IP address are changed, the
communication between the OMU and peripheral equipment is interrupted. You need to use the new fixed
or virtual external IP address to reconnect the OMU and peripheral equipment.
Step 10 The omutool gateway gateway IP address command is used to change the gateway IP address.
For example, type the following command and press Enter to change the gateway IP address:
omutool gateway 10.161.10.1
NOTE
You can change the fixed or virtual external IP address simultaneously with changing the gateway IP address.
The following are the related commands:
l omutool extercard IP address Subnet mask Gateway IP address for changing the fixed external IP address
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 11 Change the backup channel IP address of the active and standby OMUs by using the commands
listed in the following table:
Option Description
Option Description
Step 12 The omutool debugcard IP address command is used to change the commissioning IP
address.
For example, type the following command and press Enter to change the commissioning IP
address:
omutool debugcard 192.168.6.60
NOTE
l After you change backup channel IP address and commissioning IP address of the active and standby
OMUs, the corresponding subnet mask will be created automatically.
l To change the IP addresses of the OMU, you must follow the principle of IP address planning. For
details, see 3.2 OMU IP Address Plan. When entering the command, leave a space between the IP
address and the subnet mask.
l Record the new IP addresses in 5.5.1 Record Sheet of OMU Software Installation Information.
Step 13 Run the net start omud command to start the omud.
----End
Context
l admin is the account for logging in to the LMT.
l db_user and root are the accounts for accessing the OMU database.
l FtpUsr is the account for uploading and downloading files to and from the OMU.
If active and standby OMUs are configured on the BSC6900, you must change the passwords
used by the admin, db_user, and root user on both the active and standby OMUs.
It is assumed that version_a is the OMU active workspace in this operation.
NOTE
l It is recommended that you change the password at your first login and then change the password every
three months.
l Users root and db_usr must both contain the combination of the following:
l At least one lower-case letter
l At least one upper-case letter
l At least one digit
l At least one special character -?[]_+{}
The user password must have a minimum length of 8 characters and maximum length of 32 characters.
l The admin and FtpUsr user password must have a minimum length of 6 characters and maximum length
of 32 characters.
Procedure
l Changing the password used by admin
1. Log in to the target OMU by referring to 5.2.20 Logging In to the OMU.
2. Choose Start > Run. Then type the cmd command and press Enter to type the
command mode of the OMU..
3. Type the net stop omud command and press Enter to stop the omud..
4. Enter the cd /d d:\mbsc\bam\version_a\bin\bam command and press Enter to
navigate to the directory where the program of the omutool is saved.
5. Run the omutool adminpwd command to change the admin password.
6. Run the net start omud command to start the omud.
l Changing the password used by root
1. Log in to the target OMU by referring to 5.2.20 Logging In to the OMU.
2. Choose Start > Run. Then type the cmd command and press Enter to type the
command mode of the OMU..
3. Type the net stop omud command and press Enter to stop the omud..
4. Enter the cd /d d:\mbsc\bam\version_a\bin\bam command and press Enter to
navigate to the directory where the program of the omutool is saved.
5. Run the omutool dbrootpwd command to change the root password.
6. Run the net start omud command to start the omud.
l Changing the password used by db_user user
1. Log in to the target OMU.
2. Choose Start > Run. Then type the cmd command and press Enter to type the
command mode of the OMU..
3. Type the net stop omud command and press Enter to stop the omud..
4. Enter the cd /d d:\mbsc\bam\version_a\bin\bam command and press Enter to
navigate to the directory where the program of the omutool is saved.
5. Run the omutool dbpwd command to change the password of the db_user user.
6. Run the net start omud command to start the omud.
l Changing the password used by FtpUsr user
1. Log in to the LMT by referring to Logging In to and Logging Out of the LMT in the
BSC6900 UMTS LMT User Guide.
2. Run the MML command MOD FTPPWD to change the password used by FtpUsr
user.
----End
Example
The following shows an example for changing the password used by admin:
D:\mbsc\bam\version_a\bin\bam>omutool adminpwd
Enter a password or press Ctrl+Break to quit:
Re-enter password or press Ctrl+Break to quit:
Successfully set the admin user's password!
The following shows an example for changing the password used by root:
D:\mbsc\bam\version_a\bin\bam>omutool dbrootpwd
Enter a password or press Ctrl+Break to quit:
Re-enter password or press Ctrl+Break to quit:
Successfully set the root's password of the database!
The following shows an example for changing the password used by db_user user:
D:\mbsc\bam\version_a\bin\bam>omutool dbpwd
Enter a password or press Ctrl+Break to quit:
Re-enter password or press Ctrl+Break to quit:
Successfully set the db_user's password of the database!
Context
l Generally, the computer name and IP addresses are planned by the operator. You need to
change the computer name and IP addresses by using the omutool after installing the OMU
applications onsite. For information about how to change the OMU IP addresses, see
Changing IP Addresses of OMU Ethernet Adapters and Their Subnet Masks.
l If the BSC6900 is configured with active and standby OMUs, name them differently.
Procedure
Step 1 Log in to the target OMU by referring to 5.2.20 Logging In to the OMU.
Step 2 Choose Start > Run. Then type the cmd command and press Enter to type the command mode
of the OMU..
Step 3 Type the net stop omud command and press Enter to stop the omud..
Step 4 Enter the cd /d d:\mbsc\bam\version_a\bin\bam command and press Enter to navigate to the
directory where the program of the omutool is saved.
Step 5 Run the omutool hostname Computer name command to change the computer name.
For example, to change the computer name to omu_123, type the omutool hostname
omu_123 command and press Enter.
Step 6 Run the net start omud command to start the omud.
----End
Follow-up Procedure
1. Log in to the LMT by referring to Logging In to and Logging Out of the LMT in the
BSC6900 UMTS LMT User Guide.
2. Run the DSP OMU command to query the new computer name.
Context
To manage BSCs uniformly on the M2000, you need to modify the NE type of upgraded BSCs.
The following procedure is for active and standby OMUs whose active workspace is
version_a. For a single OMU, ignore the steps for the standby OMU.
Procedure
Step 1 Log in to the standby OMU first and stop the omud process on it. Then, log in to the active OMU
and stop the omud process on it. For details, see 5.2.20 Logging In to the OMU and Stopping
the omud.
Step 2 Choose Start> > Run on the active OMU. Type the cmd command and press Enter to type the
command mode of the OMU.
Step 3 Type the cd /d d:\mbsc\bam\version_a\bin\bam command and press Enter to navigate to the
directory where the omutool program is saved.
Step 4 Type the omutool netype command followed by the new value of the NE type parameter on
the active OMU. Press Enter to modify the NE type.
The prompt set ne type success! indicates that the NE type has been successfully modified.
NOTE
Type the omutool netype command and press Enter to query the NE type.
Step 5 Start the omud process on the active and standby OMUs separately. For details, see Starting
the omud.
----End
Example
D:\mbsc\bam\version_b\bin\bam>omutool netype
Current ne type is : BSC6***
D:\mbsc\bam\version_b\bin\bam>omutool netype BSC6900
set ne type success!
Prerequisites
l The target slots for OMUs are idle and can hold OMUs. Such slots can be slots 0 to 3, slots
20 to 23, or slots 24 to 27.
l The target slots for OMUs are idle and can hold OMUs. Such slots refer to OMUa Board
or OMUc Board.
l The value of Data-sync state is Data synchronization is successful. You can run the DSP
OMU command to view the setting of Data-sync state.
Procedure
Step 1 Perform different operations to shut down the OMUs based on the operating system.
If... Then...
The Suse Linux operating system or Dopra 1. Log in to the active and standby OMUs
Linux operating system is used respectively by referring to Logging In to
the OMU.
2. Run the etc/rc.d/omud stop command to
stop the omud process.
3. Run the poweroff command to shut down
the OMUs.
The Windows operating system is used 1. Log in to the active and standby OMUs
respectively by referring to 5.2.20
Logging In to the OMU.
2. Choose Start > Run. Type cmd in the
Open text box and then press Enter. The
OMU command interface is displayed.
3. Run the net stop omud command to stop
the omud process.
4. Choose Start > Shutdown. Select
Shutdown from the drop-down list box to
shut down the OMU.
Step 2 When the OFFLINE LED on the OMU board panel is on, pull the active and standby OMUs
and insert them into the target slots.
NOTE
Insert active and standby OMUs into the target slots one by one after pulling both of them.
Step 3 Wait about five minutes, log in to the LMT. and then run the DSP OMU command to check
whether the active and standby OMUs operate properly.
Step 4 Run the LST BRD command to query the subrack number and slot numbers of the active and
standby OMUs before the switchover.
Step 5 Run the RMV BRD command to remove the original active and standby OMUs.
Step 6 Run the ADD BRD command to add new active and standby OMUs. In this step, set slot numbers
of the OMUs to the target OMU slot numbers.
Assume that the target OMU slot numbers are 21 and 23. Run the following commands:
ADD BRD: SRN=0, BRDCLASS=OMU, BRDTYPE=OMUa, SN=21;
ADD BRD: SRN=0, BRDCLASS=OMU, BRDTYPE=OMUa, SN=23;
Step 7 Check whether the OMUs are properly displayed on the device panel and whether they are in
normal state.
Step 8 Click Alarm in the home page of the LMT and view current active alarms of the BSC6900 in
the Browse Alarm tab page.
Step 9 Optional: If there is an alarm related to the original OMUs in the list of active alarms, select
the alarm, right-click it, and choose Clear Alarm from the shortcut menu to manually clear the
alarm.
----End
An antivirus server is deployed independently in the Demilitary Zone (DMZ) of the OM network.
The server obtains the latest virus code or upgrade package from the Internet. The antivirus
server (for example, OfficeScan Server) on the current network is upgraded by an antivirus
upgrade server in the DMZ instead of being directly connected to the Internet. After the antivirus
server is upgraded, the virus code and upgrade package of the equipment on the entire network
are upgraded automatically.
OfficeScan
OfficeScan is a web-based integrated product and it provides comprehensive security protection
for the corporate desktops. It has passed strict compatibility tests of Huawei and is compatible
with OMUs provided by Huawei.
NOTE
Context
The iPSI SEK SetWin software is a security enhancement tool for a server's operating system
(OS). This software applies to Windows Server 2003.
NOTE
The software cannot be used if the OS is switched to Dopra Linux after the BSC6810 is upgraded to the
BSC6900.
Prerequisites
l The OMU applications have been installed.
l The Deployment Guide to WRAN Windows Device Security Policy has been obtained from
http://support.huawei.com/support/ by choosing Wireless > WCDMA-RAN > WCDMA-
RNC > Reconstruction Guide.
Context
In command line mode, the iPSI SEK SetWin software is executed using the SetWinCmd
command. The SetWinCmd command can be executed in the following ways:
l If a parameters is attached to the SetWinCmd command, perform a specified task by loading
the parameter.
l If no parameter is attached to the SetWinCmd command, select a specified task by using
the menu.
CAUTION
When you run a customized policy, ensure that the imported policy is the tested customized files
and versions of the policy files, the OMU, and SetWin are compatible. If an incorrect policy or
the default system policy is imported, security problems may occur on the OMU or the OMU
becomes inaccessible.
Procedure
l If a parameter is attached to the SetWinCmd command
1. Log in to the target OMU by referring to 5.2.20 Logging In to the OMU.
2. Choose Start > Run. Then type the cmd command and press Enter to type the
command mode of the OMU..
3. Type the net stop omud command and press Enter to stop the omud..
4. Go to the directory for the SetWin program.
Assume that the SetWin program is installed in the default path, C:\Program Files
\SetWin. Type the following command and press Enter.
cd /d C:\Program Files\SetWin
6. Type the SetWinCmd /B=C:\backup.bak command and press Enter to back up the
system policies.
CAUTION
If there is no special requirement, the backup file is saved in the default directory. The
backup file is used for rollback if the operation fails. Reserve the backup file with
caution.
7. Type the SetWinCmd /X command and press Enter to execute all the policies.
NOTE
The SetWinCmd command handles the parameter items in the sequence of command input.
For details about the parameters of the SetWinCmd command, see Table 5-8.
8. When the customization is completed, restart the operating system.
l If no parameter is attached to the SetWinCmd command
1. Log in to the target OMU by referring to 5.2.20 Logging In to the OMU.
2. Choose Start > Run. Then type the cmd command and press Enter to type the
command mode of the OMU..
3. Type the net stop omud command and press Enter to stop the omud..
4. Go to the directory for the SetWin program.
Assume that the SetWin program is installed in the default path, C:\Program Files
\SetWin. Type the following command and press Enter.
cd /d C:\Program Files\SetWin
5. Type the SetWinCmd command and press Enter. The system backup window is
displayed. Enter y in the window.
6. The system indicates a message asking you whether to enter a name for the backup
file. Enter y.
7. Type the name of the backup file and press Enter. The system starts the initial backup,
as shown in Figure 5-60. After the initial system backup is completed, an interface is
displayed, as shown in Figure 5-61. Table 5-8 shows task descriptions of the
command lines.
CAUTION
The configuration file must pass the product test. The name of the configuration file
is in the form of setwin plus operating system type, for example, setwin2003.inf.
----End
Procedure
Step 1 Log in to the OMU by referring to 5.2.20 Logging In to the OMU. Click Start > Run and the
Run interface is displayed.
Step 2 Type cmd in the Open area and click Confirm. The cmd command line interface (CLI) is
displayed.
Step 4 Run the rollback command. Assume that the backup file is saved in the C:\SetWin\config
directory and its file name is 1.bak. Type the SetWinCmd /R=C:\SetWin\config\1.bak
command and press Enter.
----End
Administrator password
(active OMU)
Administrator password
(standby OMU)
For details, see Record Sheet of OMU Operating System Installation Information (Upgrade
from BSC6810 to BSC6900).
Debugging IP address
(subnet mask) of the active
OMU
Debugging IP address
(subnet mask) of the standby
OMU
Default gateway
For details, see Records of IP Addresses of the OMU Ethernet Adapter Teams (Upgrade
from BSC6810 to BSC6900).
Administrator (admin)
password
For details, see Records of the OMU Application Installation Information (Upgrade from
BSC6810 to BSC6900).
Routing and Remote Access service Started with Start Type set to Automatic.
The processes DHCP Relay Agent and
NAT/Basic Firewall are removed by default
before the OMU is delivered. If the processes
are started during the OMU maintenance,
they must be removed after choosing Start >
All Programs > Administrative tools >
Routing and Remote Access.
Item Status
For details, see Checklist for Factory Settings of the OMU Software (Upgrade from
BSC6810 to BSC6900).
20 FTP server data Port for host loading, and uploading and
downloading software and logs (in active mode)
21 FTP server control Port for host loading, and uploading and
downloading software and logs
1024-65535 FTP server data Port for host loading, and uploading and
downloading software and logs (in passive
mode)
6088 Remote upgrade tool Port for the remote upgrade tool
8088 Remote upgrade tool Port for the remote upgrade tool (SSL
encryption)
8200 ems_gate Port for the Vendor Network Probe (VNP) (SSL
encryption)
For details, see Enabled Ports on the OMU (Upgrade from BSC6810 to BSC6900).
TCP 135 Port 135 is used for services that comply with the
Remote Procedure Call (RPC) protocol and for
the Distributed Components Object Mode
(DCOM) services.
Prerequisites
l The currently-running software version is BSC6900V900R013C00SPH529 or later.
l The OMU is running properly.
Context
This operation only applies to Dopra Linux V2.
version_a as the OMU active workspace is used as an example in this operation. To query the
current OMU active workspace, run the LST OMUAREA command.
Procedure
l Disabling root user login with SSH
NOTE
l Ensure that a new non-root user account has been created before disabling root userlogin with SSH.
Otherwise, the operation fails.
l After root user login with SSH is disabled, the current user will not be logged off automatically. A
new login will be disabled.
l If the OMU operating system version is V200R003C02SPC090 or later, the root user is forbidden by
default while the lgnusr user is added as the default account. To query the OMU operating system
version, run the LST VER command.
1. Log in to the OMU as a root user. For details, see Logging In to the OMU.
2. Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the
directory where the root_login.sh script is saved.
3. Enter the chmod +x root_login.sh command and press Enter to make the
root_login.sh script executable.
4. Enter the ./root_login.sh disable command and press Enter. The message Disable
root user login, are you sure? [y/n]: is displayed. Enter y and press Enter to disable
root user login.
l Adding a common user account
1. Log in to the OMU as a root user.
2. Enter the useradd -m User Name command and press Enter to add a non-root user
account.
3. Enter the passwd Password command and press Enter to set the password.
4. Confirm the password. The non-root user account is added.
WARNING
Save information about the added non-root user account promptly for future use. If
this information is lost and the root user login with SSH has been disabled, you cannot
log in to the OMU remotely. In this situation, you must connect a keyboard with a
USB port to the USB port of the OMU and log in to the OMU as the root user to add
a common user, or use a USB flash drive to reinstall the operating system.
l To delete a non-root user account, you must have a root user account.
l A non-root user account cannot be deleted while in use.
l If there is not any common user who is allowed for login with SSH, the lgnusr user is not allowed to
be deleted.
1. Log in to the OMU as a common, lgnusr user or root user.
NOTE
If you have logged in as a non-root user, re-log in as a root user before deleting a non-root user
account.
2. Enter the userdel -r User Name command and press Enter to delete the account.
l Enabling root user login with SSH
1. Log in to the OMU as a common user or lgnusr user.
2. Switch the account of a common user or lgnusr user to that of a root user.
3. Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the
directory where the root_login.sh script is saved.
4. Enter the chmod +x root_login.sh command and press Enter to make the
root_login.sh script executable.
5. Enter the ./root_login.sh enable command and press Enter. The message Enable
root user login, are you sure? [y/n]: is displayed. Enter y and press Enter to enable
root user login.
l Querying the status of the root user login
1. Log in to the OMU as a root user.
2. Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to switch the
current directory to the directory where the root_login.sh script is saved.
3. Enter the chmod +x root_login.sh command and press Enter to make the
root_login.sh script executable.
4. Enter the ./root_login.sh status command and press Enter to query the status of the
root user login with SSH.
NOTE
Parameter description
l Configuration status indicates the root user status to be configured.
l Actual status indicates the current root user status.
l enabled indicates that the root user login with SSH is enabled. disabled indicates that the root
user login with SSH is disabled.
----End
Example
The following is used as an example for disabling root user login with SSH to the OMU.
omucc_68 / # cd /mbsc/bam/version_a/bin/bam
omucc_68 /mbsc/bam/version_a/bin/bam # chmod +x root_login.sh
omucc_68 /mbsc/bam/version_a/bin/bam # ./root_login.sh disable
Disable root user login, are you sure? [y/n]:y
Disabling root user login done
The following is used as an example for creating a non-root user omu123 account.
The following is used as an example for changing password for common user or lgnusr user.
omucc_68 / # passwd
Changing password for eric.
Old Password:
New Password:
Reenter New Password:
Password changed.
The following is used as an example for switching an account from common user or lgnusr user
to root user.
omucc_68 / $ su
Password:
omucc_68 / #
The following is used as an example for querying user information on the OMU.
The following is used as an example for enabling root user login with SSH to the OMU.
omucc_68 / $ su
Password:
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 enable
Enable root user login, are you sure? [y/n]:y
Enabling root user login done
omucc_68 /mbsc/bam/version_a/bin/bam #
The following is used as an example for querying the status of the root user login with SSH.
omucc_68 / # 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 status
Configuration status: enabled Actual status: enabled
Follow-up Procedure
1. Record the information of the new non-root user and the status of the root user login with
SSH.
Prerequisites
l The currently-running software version is BSC6900V900R013C00SPH529 or later.
l The OMU is running properly.
Context
This operation only applies to Dopra Linux V2.
version_a as the OMU active workspace is used as an example in this operation. To query the
current OMU active workspace, run the LST OMUAREA command.
Procedure
l Disabling OMU route forwarding
NOTE
l If NodeBs are maintained by using the M2000 remotely in the live network, do not disable the OMU
route forwarding. Otherwise, the remote operation and maintenance (O&M) channels for NodeBs fail.
l The OMU route forwarding is enabled by default.
1. Log in to the OMU. For details, see Logging In to the OMU.
2. Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the
directory where the ip_forward.sh script is saved.
3. Enter the chmod +x root_login.sh command and press Enter to make the
ip_forward.sh script executable.
4. Enter the ./ip_forward.sh disable command and press Enter to disable the OMU
route forwarding.
l Enable OMU route forwarding.
1. Log in to the OMU.
2. Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the
directory where the ip_forward.sh script is saved.
3. Enter the chmod +x root_login.sh command and press Enter to make the
ip_forward.sh script executable.
4. Enter the ./ip_forward.sh enable command and press Enter to enable the OMU route
forwarding.
l Querying the status of OMU route forwarding
1. Log in to the OMU.
2. Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the
directory where the ip_forward.sh script is saved.
3. Enter the chmod +x root_login.sh command and press Enter to make the
ip_forward.sh script executable.
4. Enter the ./ip_forward.sh status command and press Enter to query the status of
OMU route forwarding.
NOTE
Parameter description
l Configuration status indicates the status of OMU route forwarding to be configured.
l Actual status indicates the current status of OMU route forwarding.
l enabled indicates that OMU route forwarding is enabled. disabled indicates that OMU route
forwarding is disabled.
----End
Example
The following is used as an example for disabling OMU route forwarding.
omucc_68 ~ # cd /mbsc/bam/version_a/bin/bam
omucc_68 /mbsc/bam/version_a/bin/bam # chmod +x ip_forward.sh
omucc_68 /mbsc/bam/version_a/bin/bam # ./ip_forward.sh disable
Disabling ip forward done
omucc_68 ~ # cd /mbsc/bam/version_a/bin/bam
omucc_68 /mbsc/bam/version_a/bin/bam # chmod +x ip_forward.sh
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.
Prerequisites
l The peer equipment supports NTP and NTP message authentication.
l The IP address, NTP server port number, and key index of the peer equipment have been
obtained.
Context
Before sending a synchronization request to an NTP server, the OMU, as an NTP client, encrypts
the request and attaches a key index and encryption information to the request. The NTP server
decrypts the request and sends a synchronization response to the NTP client. After receiving the
response, the NTP client checks whether the encryption information in the response is consistent
with that calculated locally. If yes, the time synchronization between the NTP client and server
starts.
If multiple NTP servers are configured for the time synchronization with the OMU (NTP client),
the OMU automatically selects the best NTP server as the clock source.
When OMU of the BSC6900 is used as an NTP client, the OMU supports the NTP-based time
synchronization in plaintext or in cipher.
When OMU of the BSC6900 is used as an NTP server, the OMU only provides NTP plaintext
in internal network.
Procedure
Step 1 Log in to the LMT by referring to Logging In to and Logging Out of the LMT.
Step 2 To add the information of an NTP server connected to the OMU, run the ADD
SNTPSRVINFO command and set the following parameters as required: IP Address, Port,
NTP Authentication Mode, Key ID, Encryption Algorithm, Key, Confirmation Key.
NOTE
Repeat Step 2 to configure multiple NTP servers available for the time synchronization with the OMU.
----End
Prerequisites
l The OMU OS is Dopra Linux.
l The peer equipment OS is Linux or Unix.
Context
With this function, the OMU automatically records a user's information and reports the
information to the peer equipment by using the syslog service when the user logs in to or out of
the OMU OS. The reported user information includes the user name, user IP address, and the
number of the port through which the user accesses the OMU.
Multiple OMUs can be enabled with this function. Once enabled, they report their users'
information to the peer equipment simultaneously.
NOTE
For example, the version information for the active OMU workspace is version_a. You can run the LST
OMUAREA command to query the version information for the current active OMU workspace.
Procedure
l Enabling the function of recording OMU OS accessing information in real time
1. Log in to the target OMU. For details, see Logging In to the OMU.
2. Run the cd /mbsc/bam/version_a/bin/bam command to switch the directory where
the syslog_config.sh script is saved.
3. Run the ./syslog_config.sh IP address PORT command to enable the function of
recording OMU OS accessing information in real time.
NOTE
----End
Prerequisites
The OMU OS File Integrity Checklist is available.
Context
l The OMU OS File Integrity Checklist is used to specify the OS files to be checked. This
list must be in .txt format and file path information for a maximum of 5000 files can be
provided in the list. File path information for each file occupies one line and must include
the file name. The following are two examples of file path information corresponding to
Linux and Window, respectively: /etc/sysctl.conf and C:\WINDOWS\explorer.exe.
l After the function is enabled, the OMU checks the integrity of specified files every 12
hours. If the check fails, the ALM-20723 File Loss or Damage is reported. In the scenarios
of version upgrade, driver upgrade, and OS upgrade, if the ALM-20723 File Loss or
Damage is reported after a monitored file is changed, clear the alarm by following the alarm
handling procedures.
l After an OS switch, this function will be automatically disabled and the OMU OS File
Integrity Checklist will be deleted. To enable this function, the OMU OS File Integrity
Checklist must be created and loaded again.
l It is recommended that the files to be checked must be important and will not be changed
by the NE automatically. If the OMU is using Linux, files in the following directories are
recommended to be checked: /bin, /boot, /etc, /sbin, and /sys
NOTE
If the OMU is in active/standby mode, enable or disable this function on both active and standby OMUs.
Procedure
l Enabling this function
1. Upload the OMU OS File Integrity Checklist into the ftp/integrity_cfg directory in
the OMU active workspace. For details, see 4.4.1 psftp Software.
2. Run the ACT FILEINTEGRITYPRO command to enable this function.
l Disabling this function
1. Run the DEA FILEINTEGRITYPRO command to disable this function.
l Querying the function status
1. Run the LST FILEINTEGRITYPRO command to query the status of this function.
----End