OMU Board

Introduction to OMU
The physical entity of the OMU is the OMUa/OMUb/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.
Position of the OMU in the BSC6900
This section describes the components of the BSC6900 operation and maintenance (OM) subsystem
and the position of the OMU in the OM subsystem.
OMUa and OMUb Board
OMUa is short for Operation and Maintenance Unit REV:a. OMUb is short for Operation and
Maintenance Unit REV:b. One or two OMUa/OMUb boards must be configured in the BSC6900.
One OMUa/OMUb board occupies two slots. The board can be installed in slots 0 to 3, slots 20 to 23, or
slots 24 to 27 in the MPS at the bottom of the MPR. It is recommended that the OMUa/OMUb board be
installed in slots 20 to 23 for inventory sites and in slots 24 to 27 for new sites.
OMUc Board
OMUc refers to Operation and Maintenance Unit REV:c. A pair of active/standby OMUc boards must be
configured in the BSC6900. The OMUc boards can be installed in slots 0 to 3, slots 20 to 23, or slots 24
to 27 in the MPS at the bottom of the MPR. Slots 24 to 25 are recommended.
OMU Software
The OMU software, running on the OMUa board, OMUb board, OMUc board, and GBAM, is responsible
for the operation and maintenance of theBSC6900.
OMU Working Mode
The OMU works in independent or active/standby mode.
OMU OM Methods
This section describes how to perform operation and maintenance (OM) on the OMU in different
scenarios.
OMU Safety Information
This section describes the safety information related to the OMU operation.
Position of the OMU in the BSC6900

This section describes the components of the BSC6900 operation and maintenance (OM) subsystem
and the position of the OMU in the OM subsystem.
The BSC6900 OM subsystem is composed of the OM terminal (LMT/M2000), OMU, SCU, and OM
modules on other boards. In the BSC6900 OM subsystem, the LMT/M2000 communicates
with BSC6900 boards through the OMU.
Figure 1 shows the position of the OMU in the BSC6900 OM subsystem.
Figure 1 Position of the OMU in the BSC6900 OM Subsystem
As shown in Figure 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.
OMUa and OMUb Board

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

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

There are four USB ports, three GE ports, one serial port COM0-ALM/COM1-BMC, and one VGA port on
the OMUa/OMUb board.
Table 1 describes the ports on the OMUa/OMUb board.
Table 1 Ports on the OMUa/OMUb board

Port
Function
Connector
Type
USB0-1 and
USB2-3
Operators can use the USB ports only after logging in to the
USB
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 communication between

the OMU and the LMT/M2000.
RJ45
ETH2
The port does not require a signal cable or connection to other

devices when the system runs properly. Therefore, equipment
security is not affected.
RJ45
COM0ALM/COM1BMC
The port does not require a signal cable or connection to other

devices when the system runs properly. Therefore, equipment
security is not affected.
DB9
VGA
Video port
DB15
Parent topic: OMUa and OMUb Board
Technical Specifications of the OMUa/OMUb Board

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

Table 1 lists the hardware configuration indexes of the OMUa/OMUb board.
Table 1 Hardware configuration indexes
Item
Index of the OMUa board
Index of the OMUb board
Dimensions
248 mm x 64.6 mm x 395.4

mm
248 mm x 64.6 mm x 395.4

mm
Power supply
Two -48 V DC working in

active/standby mode. The
backplane of the subrack is
responsible for the power
supply.
Two -48 V DC working in

active/standby mode. The
backplane of the subrack is
responsible for the power
supply.
Number of CPUs
Power consumption
120 W
90 W
Weight
4.0 kg
3.5 kg
Hard disk capacity
73 GB or above x 2 (RAID 1)
73 GB or above x 2 (RAID 1)
Table 1 Hardware configuration indexes
Item
Index of the OMUa board
Index of the OMUb board
Memory capacity
2G
2G
Temperature required when

working for an extended
period of time
5C to 40C
5C to 40C

working for a short period of
time
0C to 50C
0C to 50C
Relative humidity required

5% to 85%
when working for an extended
period of time
5% to 85%

when working for a short
period of time
5% to 95%
5% to 95%
Performance Counters
Table 2 lists the performance counters of the OMUa/OMUb board.
Table 2 Performance counters
Counter
Number of recorded
alarms
Index of the OMUa/OMUb Board
The maximum number of recorded alarms is 150,000.
Time when the standby

The standby OMU synchronizes its data with that of the active
OMU data is synchronized OMU board every second.
with the active OMU data
Duration of the
synchronization between
the active OMU files and
standby OMU files
Five minutes. The time needed for the synchronization varies

according to the size and quantity of the files to be synchronized.
Duration of the switchover Refers to the time from the request for OMU switchover being
between the active and
accepted to the switchover being finished. The switchover finishes
standby OMUs
in four minutes.
Duration of the OMU

restart
Duration of the OMU restart caused by an OMU fault. This

duration lasts for about three minutes.
The OMUa/OMUb board contains mechanical hard disk. Adverse environments, such as high
temperature and high altitude, shorten board lifespan.
To extend the lifespan of the OMUa/OMUb board, protect it from vibration, shock, and abnormal
shutdowns.
OMUc Board
OMUc refers to Operation and Maintenance Unit REV:c. A pair of active/standby OMUc boards must be
configured in the BSC6900. The OMUc boards can be installed in slots 0 to 3, slots 20 to 23, or slots 24
to 27 in the MPS at the bottom of the MPR. Slots 24 to 25 are recommended.
NOTE:
This document describes the installation of other boards on the basis that the OMUc boards are
installed in slots 24 and 25.
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 anOMUa/OMUb board, the OMUc board and
the OMUa/OMUb 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/OMUb board to the OMUc board.
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.
Panel of the OMUc Board
There are LEDs, ports, and buttons on the panel of the OMUc board.
Figure 1 shows the panel of the OMUc board.
Ports on the OMUc Board
There are four USB ports, three GE ports, one serial port COM0, and one VGA port on the OMUc
board.
Table 1 describes the ports on the OMUc board.
Table 1 Ports on the OMUc board

Port
Function
Connector Type
USB0-1 and USB2-3
Operators can use the USB ports

USB
only after logging in to the operating
system (OS) running on the board.
The hardware ports need no cables
or connecting to other equipments
and thus do not affect the equipment
safety.
ETH0 to ETH1
The hardware ports are used for the

communication between the OMU
and the LMT/M2000.
ETH2

RJ45
safety.
COM

RJ45
DB9
Table 1 Ports on the OMUc board

Port
Function
Connector Type

safety.
VGA
Port for the video.
DB15
Technical Specifications of the OMUc Board

The technical specifications of the OMUc board include hardware configuration indexes and performance
counters. The hardware configuration indexes refer to the dimensions, power supply, number of CPUs,
power consumption, weight, operating temperature, and relative humidity.
Figure 1 Panel of the OMUc board
(1) Captive screw
(2) Ejector lever
(3) Self-locking latch
(4) RUN LED
(5) ALM LED
(6) ACT LED
(7) POWER Button
(8) HDD LED
(9) OFL LED
(10) COM port
(13) VGA port
(14) USB port
Hardware Configuration Indexes

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

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

working for an extended
period of time
5C to 40C
Table 1 Hardware configuration indexes of the OMUc board
Item

working for a short period of
time
0C to 50C

5% to 85%
when working for an extended
period of time

when working for a short
period of time
5% to 95%
Performance Counters
Table 2 describes the performance counters of the OMUc board.
Table 2 Performance counters of the OMUc board
Item
Number of recorded
alarms
The maximum number of recorded alarms is 150,000.
Table 2 Performance counters of the OMUc board
Item
Time when the standby

The standby OMU synchronizes its data with that of the active
OMU data is synchronized OMU board every second.
with the active OMU data
Duration of the
synchronization between
the active OMU files and
standby OMU files
Five minutes. The time needed for the synchronization varies

according to the size and quantity of the files to be synchronized.
Duration of the switchover Refers to the time from the request for OMU switchover being
between the active and
accepted to the switchover being finished. The switchover finishes
standby OMUs
in four minutes.
Duration of the OMU

restart
Duration of the OMU restart caused by an OMU fault. This

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.
OMU Software
The OMU software, running on the OMUa board, OMUb board, OMUc board, and GBAM, is responsible
for the operation and maintenance of the BSC6900.
The OMU software consists of the operating system and OMU applications, as shown in Figure 1.
Figure 1 OMU structure
OMU operating system

The OMU operating system, installed on the boards, can be the Dopra Linux, SUSE Linux, or
Windows Server 2003.
OMU Application Software
The OMU application software runs on the bottom-level operating system and provides various
service processes.
OMU Software Monitoring
The OMU hardware is monitoring its software in real time to avoid suspension of OMU applications.
OMU Application Structure
The OMU applications used for operation and maintenance consist of multi-level service monitoring
entities and service processes.
OMU Service Monitoring Entities
The OMU applications perform monitoring at three levels: Level 1 is the hardware-level monitoring in
which the watchdog monitors the omud. Level 2 is the system-level monitoring in which the omud
monitors the monitor. Level 3 is the application-level monitoring in which the monitor monitors service
processes. When a service process, the monitor, or the omud is faulty, three-level monitoring
mechanism ensures that the faulty service process, monitor, or omud can be restarted.
OMU Service Processes
The OMU is managed by OMU services processes.
OMU Software Monitoring

The OMU hardware is monitoring its software in real time to avoid suspension of OMU applications.
Figure 1 shows how OMU hardware monitors OMU software.
Figure 1 Monitoring of the OMU hardware on its software
The omud process periodically clears the watchdog timer. If the omud process is abnormal and
causes the watchdog timer to overflow, the OMU will be reset automatically.
OMU Application Structure

The OMU applications used for operation and maintenance consist of multi-level service monitoring
entities and service processes.
Figure 1 shows the structure of the OMU applications.
Figure 1 OMU Application Structure
OMU Service Monitoring Entities

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

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

The six Ethernet adapters on an OMUa board are:
ETH0 and ETH1: These two Ethernet adapters are bound as an external Ethernet adapter team,
that is, bond1/bond1:0. This Ethernet adapter team is used for communication in the external
network. That is, the communication between the OMU and the LMT/M2000.
ETH2 OMUa (192.168.6.50 or 60 (255.255.255.0) OMUb (192.168.1.1 and

255.255.255.0): This Ethernet adapter is used to commission the OMU. It is connected to a portable
PC, if required. This Ethernet adapter is also called bond2.
ETH3-UPDATE: This is an backup Ethernet adapter used for the dedicated backup channel
between the active and standby OMUs when the BSC6900 is configured with two OMUa boards.
This backup Ethernet adapter is also called bond3.
ETH4-SCU7 and ETH5-SCU6: The two Ethernet adapters are bound as an internal Ethernet
adapter team, that is, bond0 (vlan1/vlan1:0). This Ethernet adapter team is used for communication
in the internal network. That is, the communication between the OMU and BSC6900 host boards.
Figure 1 shows the binding relationship between Ethernet adapters on the OMUa board.
Figure 1 Binding relationship between Ethernet adapters on the OMUa board
NOTE:
ETH0, ETH1, and ETH2 are connected to the external network through the Ethernet ports on the
panel of the OMUa board. ETH4-SCU7, ETH5-SCU6, and ETH3-UPDATE are connected to the
backplane of the MPS and invisible on the panel of the OMUa board.
Either bond1 or bond1:0 is reserved for the fixed external IP address, and the other is reserved
for the virtual external IP address.
ETH4-SCU7 and ETH5-SCU6 are bound as an internal Ethernet adapter team, that is, bond0. To
enable communication between the OMU and the SCU, a VLAN whose ID is 1 needs to be
established on bond0. vlan1 and vlan1:0 are used for the fixed internal IP address and the virtual
internal IP address, respectively.
Configuration of Ethernet Adapters on an OMUb Board

The six Ethernet adapters on an OMUb board are:
ETH0 and ETH1: These two Ethernet adapters are bound as an external Ethernet adapter team,
that is, bond1. This Ethernet adapter team is used for communication in the external network. That
is, the communication between the OMU and the LMT/M2000.
ETH2: This Ethernet adapter is used to commission the OMU. It is connected to a portable PC, if
required. This Ethernet adapter is a commissioning Ethernet adapter. It is connected to a portable
PC for OMU commissioning if required. The default IP address for ETH2 and its default subnet mask
are 192.168.1.1 and 255.255.255.0, respectively.
ETH3-UPDATE: This backup Ethernet adapter is used for the dedicated backup channel between
the active and standby OMUs when the BSC6900 is configured with two OMUb boards.
ETH4-SCU7 and ETH5-SCU6: The two Ethernet adapters are bound as an internal Ethernet
adapter team, that is, bond0. This Ethernet adapter team is used for the communication in the
internal network. That is, the communication between the OMU and BSC6900 host boards.
Figure 2 shows the binding relationship between Ethernet adapters on the OMUb board.
Figure 2 Binding relationship between Ethernet adapters on the OMUb board
NOTE:
ETH0, ETH1, and ETH2 are connected to the external network through the Ethernet ports on the panel of
the OMUb board. ETH4-SCU7, ETH5-SCU6, and ETH3-UPDATE are connected to the backplane of the
MPS, and you cannot see them on the panel of the OMUb board.
Configuration of Ethernet Adapters on an OMUc Board

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

The OMU Ethernet adapters must follow the IP address planning principles to meet the communication
requirements of the operation and maintenance (O&M) network.
NOTE:
The OMUs in the existing network are classified into the OMUa board, OMUb board, OMUc
board, and GBAM. The OMUb board and GBAM are inventory materials, and therefore their IP
addresses do not need to be planned for site deployment. The original IP addresses of the OMUb
and GBAM can be reserved for the upgrade scenario.
For details about the Ethernet adapter configuration of the OMUb board and GBAM, see OMU
Ethernet Adapter Configuration.
The following section explains the IP address plan required when OMUa and OMUc boards are
used.
Definitions of OMU IP Addresses

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

devices (for example, a PC) and the OMU.
The fixed external IP address is automatically
configured on the OMU external Ethernet adapter
team when the OMU operating system is being
installed.
Virtual external IP address for the communication between peripheral

IP address
devices (for example, LMT or M2000) and the OMU.
The virtual external IP address is configured on the
Ethernet adapter team of the active OMU when the
OMU applications are installed. It takes effect after
the OMU applications are started.
Used for the communication

between peripheral devices (for
example, a PC) and the OMU.
A user can log in to the LMT by
using the fixed external IP address
on a PC.

between peripheral devices (for
example, LMT or M2000) and the
active OMU.
If active and standby OMUs are
switched over when a peripheral
device communicates with the
OMUs using the virtual external IP
address, the communication
between the peripheral device and
IP Address
Definition
Function
the OMU will be interrupted for a

while and then be recovered.
During this process, the virtual
external IP address of the original
standby OMU becomes effective,
and the virtual external IP address
of the original active OMU
becomes ineffective.
A user can log in to the LMT by
using the fixed external IP address
on a PC.
Fixed internal
IP address
IP address for the communication between the active

and standby OMUs on the internal network segment
(network on which information is exchanged by using
the SCUa or SCUb board).

between the active and standby
OMUs in the internal network
segment.
The fixed internal IP address is automatically

configured on the OMU internal Ethernet adapter
team when the OMU operating system is installed.
The fixed internal IP address is not

used for the communication
between the OMU and
the BSC6900 host boards.
Virtual internal IP address for the communication between the active

IP address
OMU and the BSC6900 host boards.
The virtual internal IP address is configured on the
internal Ethernet adapter team of the active OMU. It

between the active OMU and
theBSC6900 host boards.
IP Address
Definition
Function
takes effect after the OMU applications are started.
The communication between

theBSC6900 host boards and the
OMU are not interrupted even
during the switchover of the active
and standby OMUs.
IP address of
the backup
channel
between the
active and
standby OMUs
IP address for the communication between the active

and standby OMUs on the backup channel network
segment (network on which information is exchanged
using an Ethernet cable).

between the active and standby
OMUs on the backup channel
network segment.
Debugging IP
address
IP address for operating and maintaining the OMU

when a PC is connected to the commissioning
Ethernet port of the OMU using an Ethernet cable at
IP address used for connecting to

the OMU commissioning Ethernet
The IP address of the backup channel between the

active and standby OMUs is automatically configured
on the standby OMU Ethernet adapter when the OMU
operating system is being installed.
IP Address
Definition
Function
the local end.
port.
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.
Definition of Onsite Network

The network connecting the OMU external Ethernet adapters and the LMT or M2000 is defined as an
external network or an onsite network. If the OMU external Ethernet adapters are connected to the LMT
or M2000 routers, then the network connecting the OMU external Ethernet adapters and the first router
(gateway) is defined as an onsite network. Figure 1 shows an onsite network.
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.
The network between the OMU external Ethernet adapters and the LMT or M2000 is defined as
an external network. The OMU is connected to the LMT or M2000 either directly or through multiple
routers (gateways).
Figure 1 Onsite network
Consider the following principles when configuring IP addresses on site:
If IP routes to the OMU are configured by running the ADD OMUIPRT command, ensure
that Forward Route Address and Destination Network Address to the LMT or M2000 are not
located in the same network segment as the virtual internal IP address, fixed internal IP address, IP
address of the backup channel between the active and standby OMUs, or commissioning IP
address.
IP Addresses to Be Changed on Site

IP addresses are configured before an OMU is delivered. For more information, see Checklist for the
OMU Software Factory Settings. The default IP addresses may fail to meet the requirements of onsite
network planning. Therefore, you are required to reconfigure some of the OMU IP addresses.
Generally, the fixed and virtual external IP addresses need to be reconfigured according to the customer
network planning.
If one OMU is configured, fixed and virtual external IP addresses of the OMU must be in the
same network segment.
If active and standby OMUs are configured, the fixed external IP addresses of the active and
standby OMUs, the virtual external IP address of the active and standby OMUs (the virtual external
IP address of the active OMU and that of the standby OMU are the same) must be configured in the
same network segment.
Table 2 describes the planning principles of OMU IP addresses.
Table 2 Onsite planning of OMU IP addresses
IP Address
Planning Principle
Fixed external IP The default fixed external IP address of the active OMU is 172.121.139.201
address
(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
Table 2 Onsite planning of OMU IP addresses
IP Address
Planning Principle
address. In addition, the IP address of the external gateway cannot

conflict with the fixed external IP address.
Virtual 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.
1.
Change the virtual external IP address as required. Ensure that the

virtual external IP address and the fixed external IP address are in the
same network segment (This network segment is called the OMU
external network segment). In addition, the virtual external IP address
cannot conflict with other IP addresses in the network segment.
For example, if active and standby OMUs are configured, the fixed
external IP address of the active OMU is 172.121.139.201, and that of
the standby OMU is 172.121.139.202, the virtual external IP address
can be configured as 172.121.139.200.
2.
For example, if an independent OMU is configured and the

fixed external IP address of the OMU is 172.121.139.201, the
virtual external IP address can be configured as
172.121.139.200.
IP Addresses to Be Checked on Site

Review OMU IP addresses on site. If the IP addresses are located in the same network segment as the
onsite network IP address, they should be reconfigured.Table 3 describes the principles of configuring the
IP addresses.
Table 3 Onsite checking of OMU IP addresses
IP Address
Fixed internal IP
address
Checking Principle
The default fixed internal IP address of the active OMU is 80.168.3.50

(255.0.0.0).
The default fixed internal IP address of the active OMU is 80.168.3.50
(255.0.0.0).
Checking principle:
Virtual internal IP
address
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.50can 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.
1.
The virtual internal IP address must be located in the same subnet as

the fixed internal IP addresses of the active and standby OMUs. This
subnet is called the OMU internal network segment. In addition, the
virtual internal IP address cannot be identical with other IP addresses
in the subnet and it should be configured as X.168.3.40 in which X
must be the same as the network segment where the fixed internal IP
IP Address
Checking Principle
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.
3.
Debugging IP
address
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.
The subnet mask of the virtual internal IP address must be 255.0.0.0.
The default commissioning IP address of the active OMU is 192.168.6.50

(255.255.255.0).
The default commissioning IP address of the standby OMU is 192.168.6.60
(255.255.255.0).
Checking principle:
1.
The commissioning IP addresses of the active and standby OMUs

cannot be identical with other IP addresses on the live network. If
they are identical, you must change the commissioning IP address.
2.
If active and standby OMUs are configured, the commissioning IP

addresses of the active and standby OMUs must be different and in
the same network segment.
For example, the commissioning IP address of the active OMU is
192.168.6.50 (255.255.255.0) and the commissioning IP address of
the standby OMU can be 192.168.6.60 (255.255.255.0).
IP Address
Checking Principle
3.
IP address of the
backup channel
between the
active and
standby OMUs

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.
For an active OMUa 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 is 192.168.3.50 (255.255.255.0).
For a standby OMUa board, the IP address of the backup channel between
address is 192.168.3.60 (255.255.255.0).
For an active OMUc board, the IP address of the backup channel between
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
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
IP Address
Checking Principle
standby OMUs must be different and in the same network segment.

3.

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.
Impact of OMU IP Address Changes

Changing IP addresses for the OMU routine maintenance impacts the working of the BSC6900, as
described in Table 4.
Table 4 Impact of OMU IP address changes
IP Address
Change Impact
Fixed external IP After the fixed external IP address is changed, the device connected to the
address
external Ethernet port can access the OMU only by using the new fixed
external IP address.
The fixed external IP address can be changed remotely and takes effect
immediately after it is changed.
IP Address
Virtual external
IP address
Change Impact
After the virtual external IP address is changed, the device connected to the
OMU by using the original IP address can access the OMU only by using
the new virtual external IP address.
The virtual external IP address can be changed remotely and takes effect
immediately after it is changed.
Fixed internal IP
address
The internal fixed IP address and the IP addresses of the BSC6900 host
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 IP The virtual and fixed internal IP addresses must be changed at the same
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.
IP Address
Change Impact
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
backup channel
between the
active and
standby OMUs
After the IP address of the backup channel between the active and standby
OMUs is changed, reset the OMUs so that the communication between the
active and standby OMUs can be re-established.
Debugging IP
address
After the commissioning IP address is changed, the device connected to the

commissioning Ethernet port cannot access the OMU. The OMU can be
accessed only by using the new commissioning IP address.
The IP address of the backup channel between the active and standby
OMUs can be changed remotely and takes effect immediately after it is
changed.
The commissioning IP address must be changed by connecting the

commissioning Ethernet port. The new IP address takes effect immediately
after the change.
OMU Networking Principle

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

Figure 1, Figure 2, Figure 3, and Figure 4 show the networking topology in singleOMUa/OMUb/OMUc mode.
Figure 1 Single-OMUa/OMUb networking topology (with a single LAN switch)
Figure 2 Single-OMUc networking topology (with a single LAN switch)
Figure 3 Single-OMUa/OMUb networking topology (with two LAN switches)
The two internal Ethernet adapters ETH4-SCU7 and ETH5-SCU6 of the OMUa/OMUb board are
connected to the SCUs in slots 7 and 6 of the MPS through the backplane, respectively.
The two external Ethernet adapters ETH0 and ETH 1 of the OMUa/OMUb board are connected to the OM
terminals through network equipment such as 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, the two external Ethernet ports of the OMUa/OMUb 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 must be enabled with the Spanning Tree Protocol (STP) function to prevent network storms.
Figure 4 Single-OMUc networking topology (with two LAN switches)
The two internal Ethernet adapters B_ETH1 and B_ETH0 are connected to the SCUs in slots 6 and 7 in
the MPS respectively through the backplane.
The two external Ethernet adapters F_ETH1 and F_ETH0 of the OMUc board are connected to the OM
As shown in Figure 4, 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 4 must be enabled with the Spanning Tree Protocol (STP) function to prevent network storms.
Dual-OMUa/OMUb/OMUc Networking Principle

Figure 5, Figure 6, Figure 7, Figure 8, Figure 9, and Figure 10 show the networking topology in dualOMUa/OMUb/OMUc mode.
Figure 5 Dual-OMUa/OMUb networking topology (with a single LAN switch)
Figure 6 Dual-OMUc networking topology (with a single LAN switch)
Figure 7 Dual-OMUa/OMUc networking topology (with a single LAN switch)
Figure 8 Dual-OMUa/OMUb networking topology (with two LAN switches)
The two internal Ethernet adapters ETH4-SCU7 and ETH5-SCU6 of the OMUa/OMUb board are
connected to the SCUs in slots 7 and 6 of the MPS respectively through the backplane.
The two external Ethernet adapters ETH0 and ETH 1 of the OMUa/OMUb board are connected to the OM
The ETH3-UPDATE of the active OMUa/OMUb board is connected to the ETH3-UPDATE of the
standby OMUa/OMUb board through the backplane to fulfill the data synchronization and the update of
OMU software between the active and standby OMUs.
As shown in Figure 8, 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 8 must be enabled with the STP function to prevent network storms.
Figure 9 Dual-OMUc networking topology (with two LAN switches)
The two internal Ethernet adapters B_ETH0 and B_ETH1 of the OMUc board are connected to the SCUs
in slots 7 and 6 in the MPS respectively through the backplane.
The two external Ethernet adapters F_ETH0 and F_ETH1 of the OMUc board are connected to the OM
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.
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 9 must be enabled with the STP function to prevent network storms.
Figure 10 Single-OMUc/OMUa networking topology (with two LAN switches)
The two internal Ethernet adapters of the OMU are connected to the SCUs in slots 7 and 6 in the MPS
respectively through the backplane.
The two external Ethernet adapters of the OMU are connected to the OM terminals through network
equipment such as a hub, LAN switch, or router. In this way, the OMU fulfills the communication between
the BSC6900 and the OM terminals.
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.
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 9 must be enabled with the STP function to prevent network
storms.
GBAM Networking Principle

Figure 11 and Figure 12 show the networking topology for the GBAM and LAN switch.
Figure 11 GBAM networking topology (with a single LAN switch)
Figure 12 GBAM networking topology (with two LAN switches)
As shown in Figure 11 and Figure 12, eth0 and eth1 are internal Ethernet adapters, and eth2 and eth3 are
external Ethernet adapters. The HUAWEI C5210 GBAM has only one external Ethernet adapter, that is,
the HUAWEI C5210 GBAM does not have eth3. This figure takes two external Ethernet adapters of the
GBAM as an example.
The two internal Ethernet adapters of the GBAM are connected to ports 10 on the active and standby
SCUa boards in the MPS, respectively. In the MPS, port 10 on the active SCUa board and port 10 on the
standby SCUa board form a trunk group. This ensures that the communication between the GBAM and
the SCUa board is normal even if the Ethernet port on the GBAM or SCUa board fails. There are twelve
10/100/1000 Mbit/s Ethernet ports on the panel of each SCUa board. Port 10 is used to connect the
SCUa board to the GBAM, and other ports are used to connect the SCUa board to other boards in the
MPS in star network topology.
NOTE:
Trunk group is a function based on which multiple physical ports are bound to serve as a logical port, so
that load can be shared among multiple links.
As shown in Figure 12, the two external Ethernet ports of the GBAM are connected to the two LAN
switches respectively, which improves network reliability. In this network topology, the Ethernet ports
connecting the eth2, eth3, and LAN switches must be in the same Intranet as the two Ethernet ports on
the LAN switches connecting eth2 and eth3. Moreover, the Ethernet adapter marked in blue in Figure
12 must be enabled with the STP function to prevent network storms
Querying the Mapping Between Ethernet Adapters

This section describes the mapping between the physical and logical Ethernet adapters.
Prerequisites
The OMU applications are installed. For details, see Installing the OMU Applications in the Active
Workspace.
Procedure
1.
2.
Log in to the OMU by referring to Logging In to the OMU.
3.
4.
5.
6.
7.
8.
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.
9.
eth0
eth1
eth2
eth3
eth4
eth5
06,0,0
06,0,1
04,4,0
04,4,1
08,4,0
08,4,1
ETH4-SCU7
ETH5-SCU6
ETH2
ETH3-UPDATE
ETH0
ETH1
10.
11.
12.
13.
14.
15.
16.
Optional: To query the factory settings of the Ethernet adapters of the OMUc board, type
the ./eth_alias_names.sh command and press Enter. The following shows the factory settings of
the Ethernet adapters of the OMUc board.
eth0
eth1
eth2
eth3
eth4
eth5
eth6
02,0,0
01,0,0
07,0,0
05,0,0
06,0,0
03,0,0
03,0,1
NOTE:
F_ETH0
F_ETH1
F_DBG
B_UPDATE0
B_UPDATE1
B_ETH0
B_ETH1
The three columns in the figure for the configuration of OMU Ethernet adapters contain the
following information:
The first column lists the logical OMU Ethernet adapters for software identification.
The second column lists the Peripheral Component Identity (PCI) of the Ethernet
adapters for hardware identification.
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.
Querying the Configuration of the OMU Ethernet Adapters

This section describes how to query the configuration information of the OMU Ethernet adapters. The
information includes IP addresses, their subnet masks, and broadcast IP addresses.
Procedure
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:
version_a as the main workspace of the OMU is used as an example.
4.
Enter the ./omutool dispipinfo command and press Enter. The following shows an
example of the returned information.
5.
[Virtual IP Information]
6.
External virtual
ip / mask : 10.141.149.15 / 255.255.254.0
7.
Internal virtual
ip / mask : 80.168.3.40 / 255.0.0.0
8.
9.
[Fixed IP Information]
10.
External fixed
ip / mask : 10.141.149.14 / 255.255.254.0
11.
Internal fixed
ip / mask : 80.168.3.60 / 255.0.0.0
12.
Backup channel
ip / mask : 192.168.3.60 / 255.255.255.0
13.
Debugging
ip / mask : 192.168.6.60 / 255.255.255.0
14.
15.
[Gateway Information]
16.
Gateway : 10.141.148.1
Method 2
1.
2.
3.
4.
5.
6.
7.
8.
9.
Optional: To query the fixed internal IP address, broadcast IP address, and subnet mask
of the OMUa board, type the ifconfig vlan1command and press Enter. The following shows
an example of the returned information.
vlan1
Link encap:Ethernet HWaddr 00:18:82:68:4D:0E
inet addr:80.168.3.60 Bcast:80.255.255.255
Mask:255.0.0.0
inet6 addr: fe80::218:82ff:fe68:4d0e/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500
Metric:1
RX packets:638957 errors:0 dropped:0 overruns:0 frame:0
TX packets:256271 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:0
RX bytes:705095569 (672.4 Mb) TX bytes:16423247 (15.6 Mb)
NOTE:
To query the OMU IP addresses and subnet masks, do as follows:
Run the ifconfig bond1 command to query the fixed external IP address, its
subnet mask, and broadcast IP address.
Run the ifconfig bond1:0 command to query the virtual external IP address, its
Run the ifconfig vlan1 command to query the fixed internal IP address, its
Run the ifconfig vlan1:0 command to query the internal virtual IP address, its
Run the ifconfig bond2 command to query the commissioning IP address, its
Run the ifconfig bond3 command to query the IP address of the backup channel
between the active and standby OMUa boards, the subnet mask of that IP address, and
broadcast IP address.
If the OMU is connected to the VNP in the live network and the local BSC IP address has
been configured, refer to Scenario of Connecting the OMU and VNP for the mapping between
Ethernet adapters and IP addresses.
10.
Optional: To query the fixed internal IP address, its subnet mask, and broadcast IP
address of the OMUc board, type the ifconfig vlan1command and press Enter. The following
shows an example of the returned information.
11.
vlan1
Link encap:Ethernet HWaddr 00:18:82:68:4D:0E
12.
inet addr:80.168.3.60 Bcast:80.255.255.255
Mask:255.0.0.0
13.
inet6 addr: fe80::218:82ff:fe68:4d0e/64 Scope:Link
14.
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500
Metric:1
15.
RX packets:638957 errors:0 dropped:0 overruns:0 frame:0
16.
TX packets:256271 errors:0 dropped:0 overruns:0
carrier:0
17.
collisions:0 txqueuelen:0
RX bytes:705095569 (672.4 Mb)
TX bytes:16423247 (15.6 Mb)
NOTE:
To query the OMU IP addresses and subnet masks, do as follows:
Run the ifconfig bond1 command to query the fixed external IP address, its
Run the ifconfig bond1:0 command to query the virtual external IP address, its
Run the ifconfig vlan1 command to query the fixed internal IP address, its
Run the ifconfig vlan1:0 command to query the internal virtual IP address, its
Run the ifconfig bond2 command to query the commissioning IP address, its
Run the ifconfig bond3 command to query the IP address of the channel
between the active and standby OMUc boards, its subnet mask, and broadcast IP
address.
Run the ifconfig bond4 command to query the IP address of the channel
between the OMUc board and OMUa or OMUb board, its subnet mask, and broadcast
IP address.
If the OMU is connected to the VNP in the live network and the local BSC IP address has
been configured, refer to Scenario of Connecting the OMU and VNP for the mapping between
Ethernet adapters and IP addresses.
Querying Occupied OMU Ports

This section describes how to query occupied OMU ports.
Procedure
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
Enter the netstat -tuan command and press Enter to query the occupied OMU ports. The
following shows an example of the returned information.
omu_136 ~ # netstat -tuan
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address
Foreign Address
tcp
0
0 10.0.0.1:8000
0.0.0.0:*
tcp
0
0 10.0.0.1:8001
0.0.0.0:*
tcp
0
0 10.0.0.1:16002
0.0.0.0:*
tcp
0
0 10.0.0.1:16002
0.0.0.0:*
tcp
0
0 10.0.0.1:8099
0.0.0.0:*
tcp
0
0 10.0.0.1:8100
0.0.0.0:*
tcp
0
0 10.0.0.1:8006
0.0.0.0:*
State
LISTEN
LISTEN
LISTEN
LISTEN
LISTEN
LISTEN
LISTEN
tcp
0 10.0.0.1:8200
0.0.0.0:*
LISTEN
Information to the right of colon in the Local Address column indicates the occupied OMU port
numbers.
Starting the omutool

This section describes how to start the omutool on the OMU. When the OMU works in active/standby
mode, you should log in to the active or standby OMU, and start the omu_backup_linker tool.
Prerequisites
The OMU applications are installed. For details, see Installing the OMU Applications in the Active
Workspace.
Context
You can perform tasks by running omutool commands with specified parameters.
NOTE:
You can run the LST OMUAREA command to query the active OMU workspace.
Assume that the active OMU workspace is installed in /mbsc/bam/version_a.
Procedure
1.
2.
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.
Run the ./omutool -h command. The parameter information on the omutool is displayed.
Changing IP Addresses of OMU Ethernet Adapters and Their Subnet

Masks
This section describes how to change IP addresses and subnet masks of the OMU Ethernet adapters
using omutool.
Context
If the OMU is in active/standby mode, change the IP addresses and subnet masks of the Ethernet
adapters on both the active and standby OMUs. You are advised to first change the IP addresses and
subnet masks of the Ethernet adapters for the standby OMU before changing those for the active OMU.
NOTE:
This task describes how to change all the IP addresses and subnet masks for the OMU. You can perform
required steps to fit onsite needs.
Single-OMU mode: Stop the omud before the change and start the omud after the change.
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 OMU Ethernet Adapter Configuration.
Procedure
1.
Log in to the OMU by referring to Logging In to the OMU.
2.
3.
4.
Enter the cd /mbsc/bam/version_a/bin/bam command and press Enter to go to the directory

where the omutool program is saved..
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
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
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:
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.
When you change the fixed and virtual internal IP addresses, the corresponding subnet
masks are created automatically.
If you change the fixed and virtual internal IP addresses for the first time, perform the
following additional steps:
a.
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.
b.
Remove the SCUa board and reinstall it in the MPS. Then, reset the MPS to
validate the new fixed and virtual internal IP addresses.
7.
After these two steps are performed, the OMU can communicate with the BSC6900 host
boards normally.
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 commissioning IP address.
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:
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.
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.
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.
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
Changing the admin Password

This section describes how to change the passwords used by admin, root, and account db_user by using
the omutool, and how to change the password used by FtpUsr by using the MML command.
Context
admin is the account used by the administrator to log in to the LMT.
du_user and root are the accounts used by the OMU applications to access the OMU database.
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:
It is recommended that you change the password at your first login and change the password every three
months.
Procedure
Changing the password used by admin

1.
2.
3.

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

1.
2.
3.
4.
Run the ./omutool dbrootpwd command to change the root password.
5.
Changing the password used by db_user user

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


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

1.
2.
Log in to the LMT by referring to Logging In to and Logging Out of the LMT in
the BSC6900 GSM LMT User Guide.
Run the MML command MOD FTPPWD to change the password used by FtpUsr user.
Example
The following shows an example for changing the password used by admin:
Dopra_136 /mbsc/bam/version_a/bin/bam # ./omutool adminpwd
Enter a password or press Ctrl+C to quit:
Re-enter password or press Ctrl+C to quit:
Successfully set the admin user's password!
The following shows an example for changing the password used by root:
Dopra_136 /mbsc/bam/version_a/bin/bam # ./omutool dbrootpwd
Successfully set the root's password of the database!
The following shows an example for changing the password used by db_user user:
Dopra_136 /mbsc/bam/version_a/bin/bam # ./omutool dbpwd
Successfully set the db_user's password of the database!
Resetting the OMU

This section describes how to reset the OMUa board, OMU applications, and OMU service processes.
Prerequisites
You have logged in to the LMT. For details, see Logging In to and Logging Out of the LMT.
Context
The OMU operating system is restarted after the OMUa board is reset. If the OMUa board is reset
successfully, the faults of the OMU operating system or applications can be rectified.
All the service processes are disrupted after the OMU applications are reset. If the OMUa board
is reset successfully, the faults of the OMU applications can be rectified.
Resetting a specified OMU service process interrupts the service of the process for a while.
Procedure
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:
When the OMU works in single-OMU mode, set the Reset Target to ACTIVE.
When the OMUs work in dual-OMU mode, the active OMU is reset if you set
the Reset Target to ACTIVE.
When the OMUs work in dual-OMU mode, the standby OMU is reset if you set
the Reset Target to STANDBY.
Reset a specified service process

1.
Run the RST OMUMODULE command and specify Reset Target and Module Name to
reset the specified OMU service process.

OMU Board

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OMU Board

Uploaded by

Copyright:

Available Formats

Introduction to OMU

Position of the OMU in the BSC6900

Figure 1 Position of the OMU in the BSC6900 OM Subsystem

OMUa and OMUb Board

Panel of the OMUa/OMUb Board

Figure 1 Panel of the OMUa/OMUb board

(1) Captive screw

(2) Ejector lever

(3) Self-locking latch

(5) ALM LED

(6) ACT LED

(7) RESET button

(9) USB port

(10) ETH0 Ethernet port

(11) ETH1 Ethernet port

(13) COM port

(14) VGA port

(17) Hard disks

(18) Screws for securing the hard disk

Ports on the OMUa/OMUb Board

Table 1 Ports on the OMUa/OMUb board

The hardware ports are used for the communication between

The port does not require a signal cable or connection to other

The port does not require a signal cable or connection to other

Parent topic: OMUa and OMUb Board

Technical Specifications of the OMUa/OMUb Board

Hardware Configuration Indexes

Table 1 Hardware configuration indexes

Index of the OMUa board

Index of the OMUb board

248 mm x 64.6 mm x 395.4

248 mm x 64.6 mm x 395.4

Two -48 V DC working in

Two -48 V DC working in

Hard disk capacity

Table 1 Hardware configuration indexes

Index of the OMUa board

Index of the OMUb board

Temperature required when

Temperature required when

Relative humidity required

Relative humidity required

Table 2 Performance counters

Index of the OMUa/OMUb Board

The maximum number of recorded alarms is 150,000.

Time when the standby

Five minutes. The time needed for the synchronization varies

Duration of the OMU

Duration of the OMU restart caused by an OMU fault. This

Panel of the OMUc Board

Ports on the OMUc Board

Table 1 Ports on the OMUc board

USB0-1 and USB2-3

Operators can use the USB ports

The hardware ports are used for the

The hardware ports need no cables

The hardware ports need no cables

Table 1 Ports on the OMUc board

and thus do not affect the equipment

Port for the video.

Technical Specifications of the OMUc Board

Figure 1 Panel of the OMUc board

(1) Captive screw