Replacement Guide
Issue
Date
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Change History
Contents
1 Overview.........................................................................................................................................1
2 Check Before the Operation........................................................................................................2
2.1 Checking the Running Status of a Board...........................................................................................................2
2.2 Checking alarms................................................................................................................................................2
3 Preparation......................................................................................................................................3
3.1 Preparing the Required Hardware......................................................................................................................3
3.2 Preparing the Software Required for the Replacement......................................................................................3
3.3 Planning the Slots of the OMU Board...............................................................................................................3
3.4 Backing Up Data Before the Replacement........................................................................................................3
3.4.1 Online Data Backup..................................................................................................................................4
3.4.2 Preparing Offline Data..............................................................................................................................7
4 Procedure.........................................................................................................................................8
4.1 Stopping the GBAM..........................................................................................................................................8
4.2 Installing the GOMU.........................................................................................................................................8
4.2.1 Installing the Hardware of the GOMU.....................................................................................................8
4.2.2 Installing the Software of the GOMU......................................................................................................8
4.2.3 Recovering Data.....................................................................................................................................14
4.2.4 Installing the Standby OMU...................................................................................................................16
7 Appendix.......................................................................................................................................19
7.1 Common Commands of the psftp Software.....................................................................................................19
1 Overview
This guide helps you to replace the GBAM server with the GOMU and is applicable to the
following two scenarios:
The GBAM is not fully damaged and you can back up data on line.
The GBAM is fully damaged and you cannot back up data on line (there must be backup
database files).
If the GBAM is damaged and you cannot check on line, skip the operation described in this section.
Before the operation, check the running status of the board. The procedure is as follows:
1. Log in to the Web LMT on line.
2. Click the Device Maintenance tab on the main interface of the LMT.
3. Check the running status of the board in each subrack. If the board is abnormal, stop the
operation, and then contact Huawei technical engineers.
3 Preparation
If the GBAM is not fully damaged and O&M operations can be performed, online data
backup is recommended.
If the GBAM is damaged and you cannot maintain data, prepare data offline.
If the external network fixed IP address is not configured, the system displays NULL. In this case,
Huawei engineers need to apply for an IP address from the customer, and this IP address is in the same
network segment as the external network virtual IP address for the fixed IP address of the external
network.
b. Log in to the PuTTY, and then run the route command of the Linux operating system.
The default gateway address of the GBAM server are obtained.
c. Planning the IP Address for GOMU board.
Plan the IP address of the OMU according to the IP address of the GBAM and the planning
rules of each IP address (see Table 1.1).
External fixed IP The external fixed IP address and the external virtual IP address of
address the OMU must be in the same network segment.
The external fixed IP address of the OMU must not conflict with
the IP addresses of other devices.
Internal fixed IP The internal fixed IP addresses of the active and standby OMUs
address must be in the same network segment and different from each other.
The internal fixed IP addresses of the active and standby OMUs
must be XY.168.3.50 and XY.168.3.60 respectively. The mask must
be 255.0.0.0.
The default XY network segment is 80. This network segment can
be changed but must be consistent with that of the internal virtual IP
address. After changing the network segment, you must reset the
BSC. Other network segments must not be changed.
Two IP addresses can be flexibly allocated to the active and standby
OMUs.
Internal virtual IP The internal virtual IP addresses of the active and standby OMUs
address must be XY.168.3.40. The mask must be 255.0.0.0.
The default XY network segment is 80. This network segment can
be changed but must be consistent with that of the internal fixed IP
address. After changing the network segment, you must reset the
BSC. Other network segments must not be changed.
Backup path IP The backup path IP addresses of the active and standby OMUs must
address be in the same network segment and different from each other.
The default backup path IP addresses of the active and standby
OMUs are XY.168.3.50 and XY.168.3.60 respectively. The mask is
255.255.255.0.
During an upgrade from the BSC6000, the backup path IP addresses
before and after the upgrade must be consistent. The default backup
path IP address is XY.168.10.XXX. The mask is 255.255.255.0.
The default XY network segment is 192. This network segment can
be changed. Other network segments must not be changed.
2. Click Download.
4 Procedure
V900R011 version
Copy the .PAT and Patchcfg.xml files (if available) in the patch package to the patch
folder under the directory for storing the installation package on the local PC. If the .PAT
file name does not match the actual internal version, change the .PAT file name to be the
same as the version.
For example, to upload V900R011C00SPH732, do as follows: Decompress the
V900R011C00SPC700 installation package to the local PC, find the installation folder
V900R011C00SPC700, and then decompress the V900R011C00SPH732 patch package
to obtain the V900R011C00SPH728_1.PAT file. Then, copy the file to the patch folder
under the V900R011C00SPC700 directory and change the file name to
V900R011C00SPH728.PAT.
b. Locally connect to the ETH2 debugging network port of the GOMU, and then run the
psftp. Log in to the GOMU by using the debugging IP address.
Run the psftp, run the open login IP address command, and then log in by using the
user root. For example, run the open 192.168.6.50 command.
For the OMU that is newly delivered, the default debugging IP address of the OMUa is 192.168.6.50 or
192.168.6.60, and the default debugging IP address of the OMUb is 192.168.1.1.
For the common commands of the psftp, see Appendix 1.
c. Switch to the local directory for uploading
To switch over to the local PC directory of the version installation package, run the lcd
local directory command in the login window of the psftp. For example, run the lcd D:\
command if the installation package is stored in the D disk root directory, as shown in
Figure c.1.
To ensure the normal running of the software, the OMU must be installed in the area with the largest
space. The default partitions of the OMUa and OMUb are different. Therefore, determine the
installation partition of the OMU first.
For the OMUa, the area with the largest space is in the /mbsc directory. For the OMUb, the area
with the largest space is in the /BSC6000/data directory.
e. Create the software installation directory of the GOMU.
To create the software installation directory of the GOMU, do as follows:
Check whether the OMU software installation directory mbsc/upgrade exists on the
GOMU.
Then run the ls /mbsc/upgrade command in the login window of the psftp.
If a message saying “no such file or directory” is displayed, the directory does not exist,
as shown in Figure e.1.
If the directory with the largest free space of the GOMU is the /BSC6000/data directory, the directory to
be checked is /BSC6000/data/mbsc/upgrade.Run the ls /BSC6000/data/mbsc/upgrade command.
Then you need to create a corresponding directory manually. Run the mkdir directory
name command. When you create a directory, create a parent directory when the parent
directory does not exist. Then create a child directory. For example, to create a
/mbsc/upgrade directory, do as follows:
Run the mkdir /mbsc command. The parent directory /mbsc is created.
Then run the mkdir /mbsc/upgrade command. The child directory /mbsc/upgrade is
created, as shown in Figure e.2.
If the directory with the largest free space of the GOMU is /BSC6000/data, you need to create the
mbsc/data directory in the /BSC6000/data/ directory.
Run the mkdir /BSC6000/data/mbsc command. The parent directory /BSC6000/data /mbsc/ is
created.
Run the mkdir /BSC6000/data/mbsc/upgrade command. The child directory /BSC6000/data
/mbsc/upgrade is created.
f. Switch to the OMU directory.
To switch to the directory of the OMU to the /mbsc/upgrade directory of the OMU
software installation directory.
Run the cd /mbsc/upgrade command in the login window of the psftp, as shown in
Figure f.1.
Figure f.1 Switching over to the /mbsc/upgrade directory of the OMU software installation
directory
a. Log in to the GOMU by using the PuTTY, switch the directory to the path of the
installation program, that is, /mbsc/upgrade/V900R011C00SPC700/install/setup, and
then run the cd /mbsc/upgrade/V900R011C00SPC700/install/setup command.
Computer name
# The name of office
# The name suggest range from 5 to 32 characters.
# The characters suggest be letters, digits, "-"or "_".
Please input a valid office_name :
Language information
# The OMU language version. eg: eng/chs
Please input a valid version :
Administrator’s password
# The "admin" user's password of OMU service.
# The password must range from 6 to 32 characters and consist of only letters
and figures.
# Do not forget the password.
# You can change the password later, but this password should be provided
first.
Please input a valid admin_password :
The administrator’s password is the initial password when the administrator log in to the LMT.
FTP password
# The ftp user's password of OMU service
# The password must range from 6 to 32(characters) and consist of only letters
and figures.
# Do not forget the password.
# You can change it later, but this password should be provided first.
Please input a valid ftp_password:
Users customize the FTP password. After the OMU application is installed, use the FTP password to
access the FTP service of the OMU.
If the existing external fixed IP address and the planned IP address are not in the same network
segment, the verification of the external virtual IP address configured during the OMU
software installation process may fail. If the verification fails, configure an external virtual IP
address in the same network segment as the existing external fixed IP address. After the installation,
run omutool to change the external fixed IP address and external virtual IP address to correct values.
The existing external fixed IP address can be queried by running ifconfig bond1 in PuTTY.
Input external virtual IP /netmask;gateway IP when the external fixed IP address not exist”
OMU installation type: Enter single.
# The OMU system type. eg: Single/Dual
# Single:Install stand-alone system
# Dual:Install dual-OMU system.
The dual-OMU system can efficiently increase the reliability of the OMU
system.
Please input a valid install_type:
The subnet masks of both the internal fixed IP address and internal virtual IP address must be 255.0.0.0.
If the subnet mask is not 255.0.0.0, the internal network address of the OMU may conflict with the IP
address of the host board.
For V900R013C00SPH532 and later version,can not set the subnetmask of inner IP address and bakup
network IP address.
To configure the backup network IP address, run the ./omutool backupcard backup
network IP address subnet mask command on the PuTTY, for example, the ./omutool
backupcard 192.168.3.50 255.255.255.0 command.
d. Start the OMU.
To start the OMU, run the command /etc/rc.d/omud start on the PuTTY.
e. If the OMU version is a patch version, log in to the OMU by using the Web LMT, and
then run the INS PATCH command. If a message saying "No new patch packet was
found." or saying "Execute Succeeded." is displayed, it is normal.
If the data is prepared offline, you must upload the database file. You may not upload the following data
files that are not backed up.
a. Log in to the GOMU by using the Web LMT, and then start the file manager.
b. Recover the license file.
Upload all files in the backup/license directory of the PC to the
bam/version_a/ftp/license directory of the GOMU by using the file manager.
c. Recover the performance task file.
Upload all files in the backup/DefaultMeas directory of the PC to the
bam/version_a/ftp/DefaultMeas directory of the GOMU. If a massage indicating that
the file exists, delete the file with the same name on the GOMU first.
d. Recover the certificate file.
Upload all files in the backup/cert directory of the PC to the bam/version_a/ftp/cert
directory of the OMU by using the file manager.
e. Upload the database file.
Upload the backup database file in the backup/data directory of the PC to the bam
directory.
14. Recover the database file.
To recover the database file, do as follows:
a. Stop the OMU.
To stop the OMU, log in to the PuTTY, and then run the /etc/rc.d/omud stop command.
b. Recover the database file.
To recover the database file, log in to the PuTTY, switch to the
mbsc/bam/common/services directory, and then run the cd
/mbsc/bam/common/services command.
If the OMU software is installed in the /BSC6000/data directory, you must run the cd
/BSC6000/data/mbsc/bam/common/services command to switch to the
/BSC6000/data/mbsc/bam/common/services directory.
To recover the data of the OMU by using the omu_backup_linker tool, run the
/omu_backup_linker command.
A massage saying "Please input a valid bkp_res_type" is displayed on the interface. Type
restore, and then press Enter, as shown in Figure b.1.
A massage saying "Please input a valid backup file pathname:" is displayed on the interface.
Type the path and name of the backup database file, and then press Enter, as shown in Figure
b.2.
Database files are uploaded to the Bam directory through the file manager. The absolute path of the
corresponding operating system is /mbsc/bam. If the OMU software is installed in the /BSC6000/data
directory, the absolute path of the corresponding operating system is /BSC6000/data/mbsc/bam.
Figure b.2 Typing the path and name of the backup database file
The system recovers its data and displays the success or failure of the data recovery on the
screen. When the data is recovered successfully, a message saying "Restore OMU database
succeed!" is displayed, as shown in Figure b.3.
d. Run the DSP BRD command. Check whether the status of the OMU is normal.
e. When the OMU operates normally, run the ADD BRD command. Add the configuration
information of the GOMU.
f. Run the SET SCUPORT command. The port 10 and port 11 of the SCUa in the subrack
0 is disabled.
16. Activate the license.
To activate the license, do as follows:
a. Log in to the Web LMT.
b. Run the LST LICENSE command. Check whether the license exists. If the license does
not exist, run the DLD LICENSE command to download the license file again.
c. Run the ACT LICENSE command. The license is activated.
Check according to the following items (if any abnormal situation is detected, record the
details):
17. Check the version data.
To check the version data after the replacement, do as follows:
Log in to the GOMU by using the Web LMT (the administrator’s name and password are
consistent with that before the replacement).
Run the CMP BRDVER command. Verify the version consistency between the BAM
and FAM.
Run the ACT CRC command. Verify the consistency of the BAM and FAM data.
18. Check the running status of network elements (NEs)
Check whether the LMT can be used normally.
Check whether the alarms and traffic statistics can be viewed normally on the M2000
(the performance result file is correctly reported to the M2000).
Check whether the configuration data is consistent with that before the replacement.
Check whether the BSC board is in the normal status.
Check whether the base transceiver station (BTS) board is in the normal status.
Check whether an alarm exists.
19. Verify the service.
The service dialing test is normal.
Each key performance index (KPI) is normal.
6 GBAM Rollback
7 Appendix