Scenario: Old and New OMUs Running the Same Operating System

This section describes how to replace the standby OMU on BSC6900 configured with two OMUs when
the OMU to be replaced and the new OMU have the same operating system.

Prerequisites

A new OMU board is ready, and it is of the same type as the board to be replaced.

NOTE:
The OMUc board only runs the Dopra Linux OS.

Context

CAUTION:
To protect the OMU board from the Electrostatic Discharge (ESD), wear an ESD wrist strap and
insert its connector into the ESD socket on the cabinet before replacing the board. For detailed
operations, see Wearing an ESD Wrist Strap. If an ESD wrist strap or ground point is
unavailable, wear a pair of ESD gloves instead.

Procedure

1. Run the MML command STP DATASYNC to stop the synchronization between the active OMU
and the standby one.
2. Run the MML command DSP OMU to check the status to make sure the synchronization
between the active OMU and the standby one is stopped.
3. Go to standby OMU, choose Start > Run, type cmd and press Enter to enter the command
mode. Run net stop omud to stop the omud serviece.
4. Remove the OMU board to be replaced and insert the new one. For detailed operations, see
Replacing an OMU board that is configured with new ejector levers or Replacing an OMU
board that is configured with old ejector levers.
5. Perform operations in Table 1 based on the operating system.

Table 1 Criteria for operations (1)

If... Then...

The OMU operating system
is Dopra Linux or Suse
Linux
a. Optional: Uninstall the OMU applications on the new
OMU board.
NOTE:
If OMU applications have been installed on the new OMU board,
perform this step to uninstall the OMU applications of an earlier
version.
If no OMU application is installed on the new OMU board, skip this
step and proceed to b.
Table 1 Criteria for operations (1)

If... Then...

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.
2. Enter the /etc/rc.d/omud stop command and
press Enter to stop the omud.
3. Enter uninstall_bam in any directory of the OMU
and press Enter.
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.
5. Enter the uninstall_bam command and press
Enter.
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.
b. Install OMU applications. For details, see Install OMU
applications. in Scenario: Old OMU Running Suse Linux and New
OMU Running Dopra Linux.
c. Change the IP addresses of the new OMU.
1. The OMU operating system is Suse Linux, refer
to Change the IP addresses of the new OMU to those of the
OMU to be replaced.
2. The OMU operating system is Dopra Linux
1. Enter the cd
/mbsc/bam/version_a/bin/bam command and press
Enter to go to the directory where the omutool program
is saved.
2. Change the OMU IP addresses by
referring to the IP addresses of the replaced OMU
board.
The ./omutool innercard IP
address command is used to change the fixed
internal IP address.
The ./omutool innervip IP
address command is used to change the virtual
internal IP address.
The ./omutool extercard IP
address mask (gateway) command is used to
change the fixed external IP address and mask.
The ./omutool extervip IP
address subnet mask (gateway) command is
used to change the virtual external IP address
Table 1 Criteria for operations (1)

If... Then...

and subnet mask.

Use the command ./omutool
backupcard IP address to change the backup
channel IP address of the active and standby
OMUs of the ETH3-UPDATE Ethernet adapter on
an OMUa/OMUb board.
The ./omutool debugcard IP
address is used to change the commissioning IP
address.
NOTE:
Changing the debugging IP address immediately
disconnects the LMT PC from the OMU board.
Use the new debugging IP address to connect the
LMT PC to the OMU board again.

Optional: Only when BSC6900

is configured with the GBFD-511701 Radio
Measurement Data Interface for Navigation
feature and the BSC local IP address is used for
communication between the OMU and VNP, you
need to reconfigure the BSC local IP address,
VLAN IDs for communication between the OMU
and VNP, and VLAN IDs for communication
between the OMU and EMS/LMT based on "OMU
Ethernet Adapter Team IP Address Installation
Information." For details, see Configuring Radio
Measurement Data Interface for Navigation in
GBSS Feature Activation Guide.
b. Install the operating system patch and upgrade Ethernet
adapter driver when the operating system is Suse Linux. Log in to
http://support.huawei.com/support/ and choose Software Center >
Version Software > Wireless Product Line > SingleRAN >
SRAN O&M tools to download the OMU Driver Upgrade CHS
***.rar and get Upgrade Guide to OMU Linux Ethernet Adapter
Driver and OMU driver upgrade tool. Please refer to BSC6900
Upgrade Guide to OMU O&M Panel Adapter Driver to upgrade the
OMU adapter driver.
NOTE:
Suse Linux Operating System has no patch.

The OMU operating system
is Windows
c. Optional: Uninstall the OMU applications on the new
OMU board.
NOTE:
If OMU applications have been installed on the new OMU board,
perform this step to uninstall the OMU applications of an earlier
Table 1 Criteria for operations (1)

If... Then...

version.
If no OMU application is installed on the new OMU board, skip this
step and proceed to b.

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.
2. Type the net stop omud command and press
Enter to stop the omud.
3. Click Start > Run and the Run interface is
displayed.
4. In the Run interface, run the uninstall_bam
command and click OK.
5. Type Y, and press Enter until the Uninstall OMU
succeed! message is displayed.
6. Go to 4 after uninstalling the OMU applications in
the standby workspace. Perform to 5 to uninstall the OMU
applications in the active workspace. This task is completed.
b. Install OMU applications. For details, see Install OMU
applications in Scenario: Old OMU Running Windows and New
OMU Running Dopra Linux.
c. Change the IP addresses of the new OMU board. For
details, see Change the IP addresses of the new OMU to those of
the OMU to be replaced in Scenario: Old OMU Running Windows
and New OMU Running Dopra Linux.
d. Download and decpmpress the Upgrade Guide to OMU
Windows Operating System and Ethernet Adapter Driver. rarfile
from the release document. Decompress the package and obtain
the Upgrade Guide to OMU Windows Operating System and
Ethernet Adapter Driver.

2. Go to Common Operation for Replacing OMU Board.

Finish
 Procedure as per Different Links in above Guide

Replacing an OMU board that is configured with new ejector

levers
1. Unscrew the captive screws on the OMU board counterclockwise, as shown in part A of
Figure 1.
Figure 1 Removing an OMU board that is configured with new ejector levers
 NOTE:
The preceding figure takes an OMUa/OMUb board as an example. The procedure for an
OMUc board is similar.

2. Optional: If the board is an OMUc board, gently press the PWRBTN button.
3. Press and hold the two locking buttons, flip outward the ejector levers on the OMU board
panel to unlock them, as shown in part B of Figure 1.
4. Remove the Ethernet cable, mouse cable, keyboard cable, and monitor cable (if
configured) from the OMU board after the OFFLINE LED flashes fast and then is steady
blue.
5. Fully rotate the ejector levers outwards of the OMU board to separate it from the
backplane. Remove the OMU board along the guide rails, as shown in part C of Figure 1.
6. Press and hold the two locking buttons of the new board, flip outward the ejector levers to
separate them from the self-locking latch, and rotate them until they cannot be rotated, as
shown in part A of Figure 2.
7. Slide the new board along the guide rails into the subrack, as shown in part B of Figure 2.
Figure 2 Installing an OMU board that is configured with new ejector levers

NOTE:
The preceding figure takes an OMUa/OMUb board as an example. The
procedure for an OMUc board is similar.
 The OMUa/OMUb 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. Slots 20 to 23 are recommended.
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.

8. Flip inward the ejector levers of the OMU board until they are in position, as shown in part
C of Figure 2.
9. Secure the screws on the OMU board, as shown in part D of Figure 2.
The new board automatically loads software and configuration data, and the RUN LED
blinks 0.125 second on and 0.125 second off.
10. Connect the cables by referring to the labels.

Replacing an OMU board that is configured with old ejector

levers
11. Unscrew the captive screws on the OMU board counterclockwise, as shown in part A of
Figure 3.
 Figure 3 Removing an OMU board that is configured with old ejector levers

NOTE:
The preceding figure takes an OMUa/OMUb board as an example. The procedure for an
OMUc board is similar.

12. Optional: If the board is an OMUc board, gently press the PWRBTN button.
13. Flip outward the ejector levers of the OMU board, as shown in part B of Figure 3.
14. Remove the Ethernet cable, mouse cable, keyboard cable, and monitor cable (if
configured) from the OMU board after the OFFLINE LED flashes fast and then is steady
blue.
15. Fully rotate the ejector levers outwards of the OMU board to separate it from the
backplane. Remove the OMU board along the guide rails, as shown in part C of Figure 3.
16. Flip outward the ejector levers of the new OMU board, as shown in part A of Figure 4.
17. Slide the new board along the guide rails into the subrack, as shown in part B of Figure 4.
Figure 4 Installing an OMU board that is configured with old ejector levers

NOTE:
The preceding figure takes an OMUa/OMUb board as an example. The
procedure for an OMUc board is similar.
The OMUa/OMUb 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. Slots 20 to 23 are recommended.
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.

18. Flip inward the ejector levers of the OMU board until they are in position, as shown in part
C of Figure 4.
19. Secure the screws on the OMU board, as shown in part D of Figure 4.
The new board automatically loads software and configuration data, and the RUN LED
blinks 0.125 second on and 0.125 second off.
20. Connect the cables by referring to the labels.
Logging In to the OMU
You can run the Secure Shell (SSH) terminal, for example, the PuTTY software, to log in to the OMU and
perform operation and maintenance (OM) on the OMU.

Prerequisites

The PC to be used to log in to the OMU is properly connected.

Procedure

1. Run the SSH terminal, for example, PuTTY, on the PC, and type the IP address of the OMU.

NOTE:
Before starting OMU applications, type the fixed external IP address of the OMU.
After the OMU applications start, type the fixed or virtual external IP address. The former
is preferred.
If you are performing local commissioning, type the commissioning IP address of the
OMU.
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.
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.

2. Log in to the OMU as the root user, lgnusr user, or common user.

NOTE:
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
Disabling root user login with SSH.
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 Checklist for the OMU
Software Factory Settings.
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.
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.

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

The following shows an example of logging in to the OMU as the root user.
login as: root
 You are trying to access a restricted zone. Only Authorized Users
allowed.
Using keyboard-interactive authentication.
Password:
Last login: Fri Jul 13 12:14:11 2012 from 10.142.36.219

Hello! Welcome to DOPRALINUX!

omud215 ~ #
The following shows an example of logging in to the OMU as the lgnusr user. The same is for a common
user.
login as: lgnusr
You are trying to access a restricted zone. Only Authorized Users
allowed.
Using keyboard-interactive authentication.
Password:
Last login: Mon Feb 4 09:58:11 2013 from 10.142.36.219

Hello! Welcome to DOPRALINUX!

omu ~ $ su
Password:
omu /home/lgnusr #

Install OMU applications.

1. Set the IP address of the local computer to the same network segment as the
commissioning IP address of the OMU.
2. Connect to the debugging port of the OMU, and log in to the OMU through the
commissioning IP address. For details, see Uploading the OMU Application Installation
Package to the OMU. (The file upload path is /BSC6000/data/mbsc/upgrade.)
3. Use the commissioning IP address to switch to the directory where the installation
package is saved. For details, see Logging In to the OMU.
If the operating system is Dopra Linux, assume that OMU applications installation
package install_bam.sh is saved in
/mbsc/upgrade/VXXXRXXXCXX/install/setup. Enter the following command and
press Enter.
cd /mbsc/upgrade/VXXXRXXXCXX/install/setup
If the operating system is Suse Linux, assume that OMU applications installation
package install_bam.sh is saved in
/BSC6000/data/mbsc/upgrade/VXXXRXXXCXX/install/setup. Enter the following
command and press Enter.
cd /BSC6000/data/mbsc/upgrade/VXXXRXXXCXX/install/setup
4. Run the chmod +x ./install_bam.sh command to acquire the authority to run the
./install_bam.sh command.
5. Enter the ./install_bam.sh command and press Enter. The system prompts you to type
the product mode, as shown:
6. [2011-05-03 10:12:32] software integrality verify begin...
7. [2011-05-03 10:12:42] software integrality verify end...
8.
9. # The run mode of the product
10. # GO:GSM only
11. # UO:UMTS only
12. # GU:GSM and UMTS
13. # Please select one mode to install.
Please input a valid run_mode :

NOTE:
The software integrity of the OMU applications is checked before they are automatically
installed. The OMU applications can be installed only if the check passes.

14. Enter the product running mode and press Enter. The system prompts you to type the
office name, as shown:
15. # The name of office
16. # The name suggest range from 5 to 32 characters.
17. # The characters suggest be letters, digits, "-"or "_".
Please input a valid office_name :
18. Enter the office name and press Enter. The system prompts you to type the language, as
shown:
19. # The OMU language version. eg: eng/chs
Please input a valid version :
20. Enter the language and press Enter. The system prompts you to type the admin
password, as shown:
21. # The "admin" user's password of OMU service.
22. # The password must range from 6 to 32 characters and consist of
only letters and figures.
23. # Do not forget the password.
24. # You can change the password later, but this password should be
provided first.
25. Please input a valid admin_password :
NOTE:
The admin password is the initial password for the administrator to log in to the LMT.

26. Enter the admin password and press Enter. The system prompts you to type the FTP
password, as shown:
27. # The ftp user's password of OMU service
28. # The password must range from 6 to 32(characters) and consist of
only letters and figures.
29. # Do not forget the password.
 30. # You can change it later, but this password should be provided
first.
31. 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.

32. Enter the FTP password and press Enter. The system prompts you to type the external
virtual IP address, as shown:
33. # The extranet IP address, subnet mask, and default gateway.
34. # example: 192.168.1.9/255.255.255.0;192.168.1.1
Please input a valid virtual_extranet_config :

NOTE:
If a fixed external network IP address has been configured for the OMU to be
replaced, the entered external network virtual IP address must be in the same
network segment as the fixed external network IP address for the OMU to be
replaced.
If a fixed external network IP address has not been configured for the OMU to be
replaced, the entered external network virtual IP address can be set based on the
actual plan.

35. Enter the external virtual IP address and press Enter. The system prompts you to type
the OMU system type, as shown:
36. # The OMU system type. eg: Single/Dual
37. # Single:Install stand-alone system
38. # Dual:Install dual-OMU system.
39. The dual-OMU system can effeciently increase the reliability of
the OMU system.
Please input a valid install_type :
40. Enter the OMU installation type based on the field configuration and press Enter. Table 1
describes the OMU installation types.

Table 1 Description

Parameter Description

Single When the BSC6900 is configured with one OMU

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

Dual When the BSC6900 is configured with two OMU

boards, install OMU applications on the board in
dual-OMU mode.

41. The system asks you whether to continue with the installation, as shown:
Please affirm input information. input Y to continue; input E to
exit. ->
 42. Enter Y to install the OMU applications. When the messageInstall OMU succeed! is
displayed, the OMU applications are successfully installed.

Uploading the OMU Application Installation Package to the OMU

Before installing the OMU applications, upload the OMU application package to the specified directory of
the OMU.

Prerequisites

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.
The psftp has been obtained. For details about the psftp, see psftp Software.

Context

The OMU application installation package must be uploaded to the \mbsc\upgrade directory of
the OMU.
The OMU application installation package must be named after the version number. That is, after
the OMU application installation package is uploaded to the OMU, the directory of the
installation package on OMU is "\mbsc\upgrade\V900R014C00."
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.

During the uploading process, if the root user cannot log in to the OMU, check with the equipment
room operators to determine whether the 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
 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 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 5.
If the /mbsc/upgrade directory exists, go to 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.

Change the IP addresses of the new OMUs to those of the replaced

OMUs.

1. Type the command cd /BSC6000/data/mbsc/bam/version_a/bin/bam and press Enter

to navigate to the directory containing omutool.
2. Change the OMU IP addresses by referring to the IP addresses of the replaced OMU
board.
The ./omutool innercard IP address command is used to change the fixed
internal IP address.
The ./omutool innervip IP address command is used to change the virtual
internal IP address.
The ./omutool extercard IP address mask (gateway) command is used to
change the fixed external IP address and mask.
The ./omutool extervip IP address subnet mask (gateway) command is used to
change the virtual external IP address and subnet mask.
 Use the command ./omutool backupcard IP address to change the backup
channel IP address of the active and standby OMUs of the ETH3-UPDATE Ethernet
adapter on an OMUa/OMUb board.
The ./omutool debugcard IP address is used to change the commissioning IP
address.

NOTE:
Changing the debugging IP address immediately disconnects the LMT PC from the
OMU board. Use the new debugging IP address to connect the LMT PC to the OMU
board again.

Optional: Only when BSC6900 is configured with the GBFD-511701 Radio

Measurement Data Interface for Navigation feature and the BSC local IP address
is used for communication between the OMU and VNP, you need to reconfigure the
BSC local IP address, VLAN IDs for communication between the OMU and VNP,
and VLAN IDs for communication between the OMU and EMS/LMT based on "OMU
Ethernet Adapter Team IP Address Installation Information." For details, see
Configuring Radio Measurement Data Interface for Navigation in GBSS Feature
Activation Guide.
3. Type the command /etc/rc.d/omud start and press Enter to start the omud process.
4. Remove the debugging Ethernet cable from the OMU board panel.

Common Operation for Replacing OMU Board

This section describes the common operation after replacing OMU board, including querying the OMU
working status, modifying the name of the OMU, setting the time information of the OMU, and setting the
mode of the network adapter.

Procedure

1. Optional: When the OMU runs the Dopra Linux operating system, set the OMU status to the
same status as that before the replacement based on the result recorded in 1 and 2. For
details, see Disabling OMU route forwarding and Disabling root user login with SSH.
2. Log in to the LMT by referring to Log in to the LMT.
3. Run the MML command DSP OMU to query such information as OMU running status, fixed IP
addresses, virtual IP addresses, data synchronization state, internal network connection state,
external network connection state, and backup channel connection state.

If... Then...

One OMU board is Perform operations described in 4.

configured and its
Operational state is Normal
Two OMU boards
are configured and their
Operational state is Active
If... Then...

normal and Standby normal

respectively

Operational state is Fault Contact Huawei technical support.

4. Based on Data-sync state queried in 3, do as follows:

If... Then...

Data-sync state is not Data synchronization is Clear alarms by referring to ALM-20701

successful OMU Failure Switchover and ALM-20704
OMU Data Synchronization Failure. Go to
5 after the alarms are cleared.

Data-sync state is Data synchronization is Perform operations described in 5.

successful

5. Run the MML commands LST VER and LST PATCHVER to query whether the OMU software
version and patch version are correct.

If... Then...

They are correct Perform operations described in 6.

They are incorrect Obtain the OMU version software and patch software again and
install them.

6. Run the MML command DSP OMUMODULE to query the status of the OMU processes.

If... Then...

State is Active or Stopped In dual-OMU mode, go to 7.

In single-OMU mode, go to 8.

State is Abnormal Contact Huawei technical support.

7. (For OMU boards in dual-OMU mode only) Run the MML command CMP OMUDATA to
compare data about active and standby OMU boards. Check whether alarm data, performance
data, and configuration data are consistent between the active and standby OMU boards.

If... Then...

The data is inconsistent Run the MML command STR DATASYNC to

start data synchronization.
Perform operations described in 8.
If... Then...

The data is consistent Perform operations described in 8.

b. Run the MML command CMP LICENSE to check whether the running license on host boards is
consistent with that on the OMU board.

If... Then...

The licenses are inconsistent Resolve the problem by referring to ALM-20734

License Inconsistency Between OMU and Host.
Perform operations described in 9.

The licenses are consistent Perform operations described in 9.

c. Run the MML command CMP BRDVER to check whether the running version on host boards is
consistent with that on the OMU board.

If... Then...

The software versions are Resolve the problem by referring to ALM-20733

inconsistent Software Version Inconsistency Between OMU and
Host.
Perform operations described in 10.

The software versions are Perform operations described in 10.

consistent

d. Run the MML command ACT CRC to check whether the configuration data on host boards is
consistent with that on the OMU board.

If... Then...

The configuration data is Resolve the problem by referring to ALM-20736

inconsistent Data Inconsistency Between OMU and Host.
Perform operations described in 11.

The configuration data is Perform operations described in 11.

consistent

e. Run the MML command LST BRD to query Slot No. and Board Type of the OMU board.

If... Then...

The board type is inconsistent Run the MML command RMV BRD to remove
before and after the OMU board configurations of the replaced OMU board.
replacement Run the MML command ADD BRD to add
If... Then...

configurations of the new OMU board.

Perform operations described in 12.

The board type is consistent Perform operations described in 12.

before and after the OMU board
replacement

f. Enter the command omutool hostname OMU name to modify the name of the OMU.
g. Run the MML command LST TZ to query time zone and daylight saving time of the OMU
board.

If... Then...

The time zone and daylight saving Run the MML command SET TZ to set the time
time of the OMU is inconsistent information of the OMU.
with the local time Perform operations described in 14.

The time zone and daylight saving Perform operations described in 14.
time of the OMU is consistent with
the local time

h. Run the MML command DSP TIME to query Time of the OMU board.

If... Then...

The time of the OMU is Run the MML command SET TIME to set the
inconsistent with the local time time information of the OMU.
Perform operations described in 15.

The time of the OMU is consistent Perform operations described in 15.

with the local time

i. Set the mode of the network adapter according to the router combined with OMU. For the
detailed setting method, please refer to Setting the Link Mode of the External OMU Ethernet
Adapter when the OS is Dopra. Refer toSetting the Link Mode for External OMU Ethernet
Adapters when the OS is Suse.Normally the default value is self-adaption. Set the OMU port as
100Mb/ Full Duplex only when the switchboard is forced to be 100Mb/full duplex.
j. View the device panel on the LMT and check the status of all devices.

If... Then...

No abnormal device state is The replacement is complete.

introduced by the replacement

An abnormal device state is Contact Huawei technical support.

 If... Then...

introduced by the replacement

Follow-up Procedure

Record the name and the bar code of the replaced board. Check whether there are obvious physical
damages, such as the distorted pin, broken pin, or burnt board. If there is any damage, fill in BSC6900
Site Maintenance Record Form and pack the replaced board. When packing a board, pay attention to
the following points:
Wear an ESD wrist strap or a pair of ESD gloves.
Ensure that each ESD bag or case holds only one board.
When packing multiple boards, isolate them with ESD materials.
Contact the local Huawei office to dispose of the replaced board.

NOTE:
You may obtain the name and the PCB version from the panel or bottom of the faulty board.

Setting the Link Mode of the External OMU Ethernet Adapter(For

Dopra Linux)
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:
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.
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
 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 duplexmode 100 full off command.

NOTE:
Querying the link mode of the external OMU network adapters, see Querying the Link Mode of
the External OMU Network Adapters.
The fields in the ./omutool duplexmode 100 full off command are described as follows:
100 indicates that the rate of the Ethernet adapter is 100 Mbit/s. The value of this field
can be 10, 100, or 1000.
full indicates that the Ethernet adapter works in full duplex mode. The value of this field
can be full or half.
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.

5. Enter the /etc/rc.d/omud start command and press Enter to start the omud.

Setting the Link Mode for External OMU Ethernet Adapters (For Suse
Linux)
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:
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.
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

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 /BSC6000/data/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 duplexmode 100 full off command.

NOTE:
Querying the link mode of the external OMU network adapters, see Querying the Link Mode of
the External OMU Network Adapters.
The fields in the ./omutool duplexmode 100 full off command are described as follows:
100 indicates that the rate of the Ethernet adapter is 100 Mbit/s. The value of this field
can be 10, 100, or 1000.
full indicates that the Ethernet adapter works in full duplex mode. The value of this field
can be full or half.
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.

5. Enter the /etc/rc.d/omud start command and press Enter to start the omud.

Querying the Link Mode of the External OMU Network Adapters

This section describes how to query the link mode of the external OMU network adapters: duplex mode
and adaptive mode.

Procedure

1. Logging In to the OMU.

2. Query the logical network adapters corresponding to the external OMU network adapters, as
listed in Table 1.

Table 1 Querying the logical network adapters corresponding to the external OMU network adapters

Item Description

OMUa/OMUb Board Type /root/eth_alias_omu.sh and press Enter.

OMUc Board Run the chmod +x ./eth_alias_names.sh

command to obtain the permission to run the
./eth_alias_names.sh command. Type
./eth_alias_names.sh and press Enter.

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

4. Query the effective link mode of the external OMU network adapters. Run the ethtool eth4
command to query the link mode of eth4. Run the ethtool eth5 command to query eth5.

NOTE:
Check Speed, Duplex, and Auto-negotiation. Speed, Duplex, and Auto-negotiation
indicate the rate, duplex mode, and auto-negotiation mode, respectively.
The following example assumes that the logical network adapters corresponding to the
external OMU network adapters are eth4 and eth5, respectively. The command output is
as follows:
Settings for eth4:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Current message level: 0x000000ff (255)
Link detected: yes