Msoftx3000 v200r009c02sph131 Patch Update Guide

HUAWEI MSOFTX3000 Mobile SoftSwitch Center
V200R009C02SPH131
Patch Update Guide
Issue
01
Date
2015-02-15
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.

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

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the commercial contract made between
Huawei and the customer. All or partial products, services and features described in this document may
not be within the purchased scope or the usage scope. Unless otherwise agreed by 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 the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 01 (2015-02-15)
Huawei Proprietary and Confidential

Copyright
Huawei Technologies Co., Ltd

Patch Update Guide
About This Document
About This Document

Overview
This document is applicable to MSOFTX3000 V200R009C02SPH131. It describes how to
install and roll back the patch and provides information about the troubleshooting and
common operations associated with the patch.
Intended Audience
This document is intended for:
Technical support engineers
Maintenance engineers
Change History
Issue
Release
Date
Description
01
2015-02-15
This issue is the first official release.
Issue 01 (2015-02-15)

Copyright
ii

Patch Update Guide
Contents
Contents
About This Document.......................................................................ii
1 Patch Installation.......................................................................... 1
1.1 Precautions.........................................................................................................................................................1
1.1.1 Checking Whether Lawful Interception Measurement Tasks Exist.........................................................1
1.1.2 Checking the Operating Environment of the Internet Explorer...............................................................6
1.1.3 Disabling Relevant Services.....................................................................................................................9
1.1.4 Operations Prohibited During Patch Installation....................................................................................10
1.1.5 Impact of Patch Installation....................................................................................................................11
1.2 Installation Process..........................................................................................................................................11
1.2.1 Pre-installation Check.............................................................................................................................11
1.2.2 Install Patch............................................................................................................................................12
1.3 Preparations.....................................................................................................................................................13
1.3.1 Confirming the Version Configuration Information...............................................................................13
1.3.2 Checking the Compatibility of the Patch Package.................................................................................14
1.3.3 Obtaining the Patch Package..................................................................................................................15
1.3.4 Checking the Integrity of the Downloaded Software Packages.............................................................16
1.3.5 Checking the M2000 Common Version and Mediation Version............................................................17
1.3.6 Checking the Baseline Patch Versions of the Target MEs......................................................................18
1.3.7 Checking the OMU Board Status...........................................................................................................20
1.3.8 Checking Whether Reserved MML Command Options Put into Use in the Patch Are Set to Default
Values...............................................................................................................................................................20
1.3.9 Checking Whether the Software Parameters Added in the Patch Are Set to the Default Values...........22
1.3.10 Performing a CRC................................................................................................................................37
1.3.11 Performing Pre-Patching Check...........................................................................................................37
1.3.12 Checking the Connection to the SOSM XPTU by Using NetMeeting (Optional)...............................42
1.3.13 Updating SFU on the SOSM XPTU Server (Optional)........................................................................43
1.3.14 Checking the Impact of the Mediation Version Installation on the NMS.............................................44
1.4 Installing Patches.............................................................................................................................................45
1.4.1 Loading the M2000 Mediation Version..................................................................................................45
1.4.2 Uploading the CGP Patch Package.........................................................................................................45
1.4.3 Uploading the MSOFTX3000 Patch Package........................................................................................46
1.4.4 Installing the Patch Using the WebUI....................................................................................................47
Issue 01 (2015-02-15)

Copyright
iii

Patch Update Guide
Contents
1.4.5 Correcting Patch Installation Errors.......................................................................................................56

1.4.6 Loading the Client Patch........................................................................................................................59
1.4.7 Loading the XPTU Patch........................................................................................................................60
1.4.8 Configuring Data....................................................................................................................................63
1.5 Verifying Patch Installation..............................................................................................................................64
1.5.1 Verifying the Patch Version....................................................................................................................64
1.5.2 Verifying the Basic Functions.................................................................................................................65
1.5.3 Verifying Patch Functions......................................................................................................................66
2 Patch Rollback............................................................................67
2.1 Precautions.......................................................................................................................................................67
2.2 Rolling Back Patches.......................................................................................................................................67
2.3 Verifying Patch Rollback.................................................................................................................................76
3 Troubleshooting..........................................................................78
3.1 What to Do If the Target Patch Versions Are not Available for Selection?.....................................................78
3.2 How to View and Save the Patch Installation Report?....................................................................................79
3.3 How to Correct Internet Explorer Errors During Patch Installation?..............................................................79
3.4 Why Fail to send command or Connect to MML Server failed Is Displayed After the OMU Is Restarted
During Patch Installation or Rollback?..................................................................................................................80
3.5 Are There Any Limitations on the Patch Rollback?........................................................................................80
3.6 Why WebUI Returns to the First Check Item If Retry Is Clicked During Pre-Installation Check?................80
3.7 How to Set Remote Desktop Sharing on the SOSM XPTU?..........................................................................81
3.8 How to Assign Permissions Required for Patch Installation?.........................................................................83
3.9 What to do If Interruptions Occur During Patch Installation?.........................................................................85
3.10 What to Do If the "ALM-3807 Program Check Failure Between OMU and TDM" Is Generated?.............87
3.11 Hardware status indicators are steady in gray on the device panel of client.................................................88
3.12 "Load the cold patch for OMU fail: Patch Install fail!" Is Displayed During Patch Installation..................89
3.13 Determining Whether a Board Runs a Compact or Standard OS..................................................................90
A Acronyms and Abbreviations.......................................................91
Issue 01 (2015-02-15)

Copyright
iv

Patch Update Guide
1 Patch Installation
Patch Installation
1.1 Precautions
All the figures in this document are for your reference only. They may differ according to the actual
configuration.
This operation guide describes how to install MSOFTX3000 V200R009C02SPH131 locally

using the WebUI.
Before installing the patch, read the MSOFTX3000 V200R009C02SPH131 Patch Release
Notes to familiarize yourself with the basic information about the patch, impact of the patch
on the system, and version configuration associated with the patch. If you have any doubt
about the patch installation, contact your local Huawei technical support center.
1.1.1 Checking Whether Lawful Interception

Measurement Tasks Exist
Skip this section if the V200R009C02SPH118 or a later patch has been installed at your site.
In the V200R009C02SPH118 patch, measurement objects related to the following

measurement units are changed to lawful interception center (LIC)-related objects:
Traffic for BICC Outgoing Office in X3 channel
Traffic for ISUP Outgoing Office in X3 Channel
Therefore, the measurement tasks of these two measurement units must be removed before
patch installation or rollback and then be created again after patch installation or rollback.
Only user tt\admin can perform these measurement units.
Before patch installation or rollback, to determine whether the measurement tasks of these
two measurement units exist, perform the following operations:
Step 1 Check whether the tt\admin user account is enabled.
1.
Log in to Huawei Operation & Maintenance System.
2.
In the MML Command CGP window, run LST TTSYS to check the command
output.
Issue 01 (2015-02-15)

Copyright

Patch Update Guide
If Operation succeeded is displayed in the output, go to section 1.1.2"Checking the

Operating Environment of the Internet Explorer".
The example command output is as follows:
+++
CGP/*MEID:0 MENAME:Site Management*/
O&M
#57
%%LST TTSYS:;%%
RETCODE = 0 Operation succeeded
2013-10-21 02:46:38+00:00
If User authentication failed is displayed in the output, go to Step 2.

The example command output is as follows:
+++
CGP/*MEID:0 MENAME:Site Management*/
O&M
#60
%%LST TTSYS:;%%
RETCODE = 483005 User authentication failed
---
2013-10-21 02:47:03+00:00
END
Step 2 Start Internet Explorer, type http://<IP address of the CGP>, for example, (for example,
http://10.85.129.38).
A security alert, as shown in Figure 1.1, may be displayed prior to the login dialog box. Click Yes to
switch to the login dialog box.
Figure 1.1 Security alert
Step 3 Enter the password of user tt\admin to log in to the WebUI.

Step 4 In the WebUI, choose Performance Management System, as shown in Figure 1.1.
Issue 01 (2015-02-15)

Copyright

Patch Update Guide
Figure 1.1 Choosing Performance Management System
Step 5 In Function Subset navigation tree, choose Site > MSOFTX3000[msx] > LI switch Traffic
> Traffic for BICC Outgoing Office in X3 channel to check whether a measurement task
(including common measurement and monitoring tasks) with the measurement object as
BICC Office Direction is available.
The icon for the measurement unit node is not dimmed, indicating that a measurement task is available.
Figure 1.1 illustrates a common measurement task.

Figure 1.1 Common measurement task
Figure 1.2 illustrates a monitoring task.
Issue 01 (2015-02-15)

Copyright

Patch Update Guide
Figure 1.2 Monitoring task
No: Go to Step 6.
Yes: Go to Step 7.
Step 6 Under the LI Switch Traffic node in the Function Subset navigation tree, click Traffic for
ISUP Outgoing Office in X3 Channel to check whether a measurement task (including
common measurement and monitoring tasks) with the measurement object as Certain
outgoing or bidirection circuit group is available.
The icon for the measurement unit node is not dimmed, indicating that a measurement task is available.
Figure 1.1 illustrates a common measurement task.

Figure 1.1 Common measurement task
Issue 01 (2015-02-15)

Copyright

Patch Update Guide
Figure 1.2 illustrates a monitoring task.

Figure 1.2 Monitoring task
No: Go to 1.1.2"Checking the Operating Environment of the Internet Explorer".
Yes: Go to Step 7.
Step 7 Delete the available common measurement task and monitoring tasks for Traffic for BICC
Outgoing Office in X3 channel and Traffic for ISUP Outgoing Office in X3 Channel.
For details about how to delete a common measurement task, see Routine Maintenance
> Operation Management > Performance Management > Measurement
Management > Deleting a Measurement Task.
For details about how to delete a monitoring task, see Routine Maintenance >
Operation Management > Performance Management > Monitoring Management >
Deleting a Monitoring Task.
Step 8 After patch installation or rollback, create measurement tasks for Traffic for BICC Outgoing
Office in X3 channel and Traffic for ISUP Outgoing Office in X3 Channel again.
For details how to create a common measurement task, see Routine Maintenance >
Operation Management > Performance Management > Measurement Management
> Creating a Measurement Task.
For details about how to delete a monitoring task, see Routine Maintenance >
Operation Management > Performance Management > Monitoring Management >
Creating a Monitoring Task.
----End
Issue 01 (2015-02-15)

Copyright

Patch Update Guide
1.1.2 Checking the Operating Environment of the

Internet Explorer
Before you install MSOFTX3000 V200R009C02SPH131 using WebUI, check whether
Internet Explorer supports WebUI as follows:
Step 1 Check that the version of the Internet Explorer.
1.
Start the Internet Explorer, and choose Help > About Internet Explorer.
2.
In the displayed About Internet Explorer dialog box, check whether the version of the
Internet Explorer is 6.0, 7.0 or 8.0. Versions earlier than 6.0 do not support WebUI.
Figure 2.1 Checking the version of the Internet Explorer
WebUI works on Internet Explorer 6.0, 7.0 and 8.0. It cannot work on the Firefox.
Step 2 Exit the applications except WebUI and HUAWEI Operation & Maintenance System.
Step 3 Ensure that no third-party add-on is enabled in the Internet Explorer.
In Internet Explorer 6.0, proceed as follows:
1.
Start Internet Explorer.
2.
Choose Tools > Manage Add-ons.
3.
In the Manage Add-ons dialog box, select Add-ons currently loaded in Internet
Explorer from the Show drop-down list box, as shown in Figure 4.1.
4.
Click the add-ons whose type is Toolbar, and select Disable in the Settings area.
Issue 01 (2015-02-15)

Copyright

Patch Update Guide
Figure 4.1 Disabling third-party add-ons in Internet Explorer 6.0 or 7.0

1.
2.
Choose Tools > Manage Add-ons > Enable or Disable Add-ons.
3.
In the Manage Add-ons dialog box, select Add-ons currently loaded in Internet
Explorer from the Show drop-down list box, as shown in Figure 4.1.
4.
Click the add-ons whose type is Toolbar, and select Disable in the Settings area.

1.
2.
Choose Tools > Manage Add-ons.
3.
In the Manage Add-ons dialog box, select Currently loaded add-ons from the Show
drop-down list box, as shown in Figure 4.1.
4.
Select add-ons whose type is Toolbar, and click Disable.
Issue 01 (2015-02-15)

Copyright

Patch Update Guide
Figure 4.1 Disabling third-party add-ons in Internet Explorer 8.0
Step 4 Before a patch update or after completing a patch update or a rollback, you must clear the
buffer of Internet Explorer. To clear the buffer of Internet Explorer, perform the following
steps:
1.
Choose Tools > Internet Options from the menu bar of Internet Explorer.
2.
On the General tab page, click Delete Files. A dialog box is displayed, asking whether
to delete files.
3.
Select Delete all offline content and click OK, as shown in Figure 3.1.
Issue 01 (2015-02-15)

Copyright

Patch Update Guide
Figure 3.1 Internet Options
----End
1.1.3 Disabling Relevant Services

Before installing MSOFTX3000 V200R009C02SPH131, disable the relevant services as
follows:
Step 1 Choose Start > Settings > Control Panel > Administrative Tools > Services.
Step 2 Check whether Check Point SecuRemote Service and Check Point SecuRemote
WatchDog are displayed in the service list.
Yes => Step 3
No => End
Step 3 Double-click Check Point SecuRemote Service. In the displayed Properties dialog box,
check whether Startup type is Disabled. Repeat the same step for Check Point SecuRemote
WatchDog.
Yes => End
No => Step 4
Issue 01 (2015-02-15)

Copyright

Patch Update Guide
Step 4 Set Startup type of Check Point SecuRemote Service and Check Point SecuRemote
WatchDog to Disabled. Then, restart your PC.
Figure 1.1 Disabling Check Point SecuRemote Service
----End
1.1.4 Operations Prohibited During Patch Installation

Figure 1.1 lists the commands and operations prohibited during patch installation.
Figure 1.1 Commands and operations prohibited during patch installation
Command
ADD ME
RMV ME
BKP SYS
EXP MES
IMP MES
LOD PKG
RMV PKG
Issue 01 (2015-02-15)
Operation
Modifying the login password of WebUI on the
MSOFTX3000 MML command interface of the
HUAWEI Operation & Maintenance System (also
called OMU client)

Copyright
10

Patch Update Guide
1.1.5 Impact of Patch Installation

The patch installation has the following impacts:
If the target OMU patch contains the host/OMU process files different from those in the
baseline OMU patch, the OMU process is restarted and the OMU board is reset during
installation of the target OMU patch. This may cause temporary interruption of OMU
services.
During patch installation and rollback, the performance measurement results may be lost
or inaccurate.
Restarting of the OMU services may result in loss of performance measurement results. To
minimize the impact of patch installation on performance measurement, you are advised not
to install MSOFTX3000 V200R009C02SPH131 on the full hour.
If the OMU client patch is included in the MSOFTX3000 V200R009C02SPH131 patch

package, after patch installation is complete, you need to exit the HUAWEI Operation &
Maintenance System (by choosing System > Exit on HUAWEI Operation &
Maintenance System) and then log in again for the OMU client patch to take effect.
The OMU's cold patch in the MSOFTX3000 V200R009C02SPH112 patch package uses
a reserved measurement unit. If the SPH112 patch is not installed before, the system will
load NE files again after the OMU installation During this patch installation. The loading
process is complete within 15 minutes. In this loading process, the performance
measurement service is interrupted and the measurement statistics may be lost. After the
NE files are loaded, the performance measurement service is recovered.
1.2 Installation Process

1.2.1 Pre-installation Check
Figure 1.1 Preparation checklist
No
.
Check Item
Check Time
Duration
Reference
Status of relevant ports
One week
before patch
installation
30 minutes
Contact the maintenance engineers of the

carrier to check whether ports 6000, 6088,
and 8088 are enabled on the active OMU
server. In addition, ensure that these ports
are not used or shielded by third-party
software, for example, firewall.
Version configuration
information
One week
before patch
installation
30 minutes
See1.3.1"Confirming the Version

Configuration Information"
Issue 01 (2015-02-15)

Copyright
11

Patch Update Guide
No
.
Check Item
Check Time
Duration
Reference
Compatibility of the
patch packages to be
installed
One week
before patch
installation
30 minutes
See 1.3.2"Checking the Compatibility of the

Patch Package."
MSOFTX3000
V200R009C02SPH131
patch package
One week
before patch
installation
120 minutes
See 1.3.3"Obtaining the Patch Package."
Checking the Integrity

of the Downloaded
Software Packages
One week
before patch
installation
5 minutes
See 1.3.4Checking the Integrity of the

Downloaded Software Packages
M2000 common
version and mediation
version
One week
before patch
installation
30 minutes
See 1.3.5Checking the M2000 Common

Version and Mediation Version
Baseline patch
versions of the target
MEs
One day before

patch
installation
10 minutes
See 1.3.6Checking the Baseline Patch

Versions of the Target MEs
Status of OMU boards
One day before

patch
installation
10 minutes
See 1.3.7"Checking the OMU Board

Status."
Reserved MML
Command Options
One day before

patch
installation
10 minutes
See 1.3.8"Checking Whether Reserved

MML Command Options Put into Use in the
Patch Are Set to Default Values"
10
Software Parameters
One day before

patch
installation
10 minutes
See 1.3.9"Checking Whether the Software

Parameters Added in the Patch Are Set to
the Default Values"
11
Data consistency
between the host and
the OMU
One day before

patch
installation
15 minutes
See 1.3.10"Performing a CRC"
12
Performing PrePatching Check
One day before

patch
installation
10 minutes
See 1.3.11"Performing Pre-Patching Check"
1.2.2 Install Patch
Issue 01 (2015-02-15)
ALM-8503 Connection Failure in the OMU HA System and ALM-8504 Communication

Failure in the OMU HA System may be reported on the alarm console during the patch
uploading, and will be automatically cleared after the patch uploading is complete.

Copyright
12

Patch Update Guide
ALM-8600 Abnormal OMU Resources may be reported on the alarm console, Because
OMU services need to restart when update the patch, and will be automatically cleared
after the patch update is complete.
ALM-2001 Board Fault alarm may be reported with the alarm cause Board
communication lost during the patch installation, because the BMC is reset when the patch
updates the BMC on a board. This alarm will be automatically cleared and does not affect
services.
Figure 1.1 Schedule for patch installation

Operation
Recommen
ded Start
Time
Duration
Reference
Loading the
M2000 mediation
version
00:00
60
1.4.1"Loading the M2000

Mediation Version"
Upload the CGP

patch package
01:00
10
1.4.2"Uploading the CGP Patch

Package"
Upload the
MSOFTX3000
patch package
01:10
10
1.4.3"Uploading the
MSOFTX3000 Patch Package"
Installing the patch

using the WebUI
tool
01:20
30
1.4.4"Installing the Patch Using

the WebUI"
Loading the OMU

client patch
01:50
10
1.4.6"Loading the Client Patch"
It is recommended that you perform patch operations (including downloading the patch package) as user
admin. Otherwise, ensure that you are using an account that has at least the permission to run the G_1
command group against the CGP. For details on permission assignment, see 3.8"How to Assign
Permissions Required for Patch Installation?".
1.3 Preparations
1.3.1 Confirming the Version Configuration
Information
To confirm the version configuration information, perform the following steps:
Step 1 Log in to HUAWEI Operation & Maintenance System, and run LST ME on the CGP MML
command interface.
Issue 01 (2015-02-15)

Copyright
13

Patch Update Guide
Figure 1.1 Output of the LST ME command
Step 2 Check whether the output of the LST ME command complies with Figure 1.1. If no, stop the
patch installation until you verify that the correct version of patch package is downloaded and
versions of the relevant MEs are correct.
Figure 1.1 Version configuration information
ME
Compatible Version
CGP
V100R006C02SPC500
MSOFTX3000
V200R009C02SPC100
----End
1.3.2 Checking the Compatibility of the Patch

Package
Figure 1.1 lists the compatible patch packages of the MEs involved in the current installation.
MSOFTX3000 V200R009C02SPH131 takes effect only when the correct patch packages are
installed on the target MEs.
Figure 1.1 Compatible patch packages to be installed
S
N
ME
Compatible Patch Package
CGP
V100R006C02SPC527
MSOFTX3000
V200R009C02SPH131
iGWB
V500R006C02SPC211
Issue 01 (2015-02-15)

Copyright
14

Patch Update Guide
For details on how to install the iGWB patch package, see the patch update guide released with the
iGWB patch package.
For details on how to install the CGP and MSOFTX3000 patch packages, see relevant sections in
this operation guide.
1.3.3 Obtaining the Patch Package

One week before patch installation, perform the following steps to obtain the MSOFTX3000
V200R009C02SPH131 patch package (including patch software and reference documents):
Step 1 Log in to http://support.huawei.com using a valid username and password.
Step 2 Choose Software Center > Version Software > Core Network Product Line > WCDMACS > WCDMA MSOFTX3000 > MSOFTX3000 > MSOFTX3000 V200R009 >
MSOFTX3000 V200R009C02SPH131.
Step 3 Download MSOFTX3000 V200R009C02SPH131_ReleaseDoc_EN (version
documentation), which consists of the following documents:
MSOFTX3000 V200R009C02SPH131 Patch Notes.doc
MSOFTX3000 V200R009C02SPH131 Patch Update Guide.doc
MSOFTX3000 V200R009C02SPH131 Remote Patch Update Guide.doc
MSOFTX3000 V200R009C02SPH131 Patch Documentation Usage Guide.doc
Step 4 Download the MSOFTX3000 V200R009C02SPH131_Software (version software). Then,

extract the patch package from the version software.
Step 5 Check whether the information about patch package complies with Figure 1.1. If no,
download the correct patch package.
Figure 1.1 Information about patch package
File Name
Size (Byte)
MSOFTX3000 V200R009C02SPH131 Patch.zip
1,612,866,699
MSOFTX3000 V200R009C02SPH131_iManager Adapter.zip
287,034,914
MSOFTX3000V200R009C02SPH131_XPTU_SOSM.exe
3,701,106
Step 6 Decompress the patch package on the PC that runs the HUAWEI Operation & Maintenance
System. It is recommended that you decompress the patch package to E:\ MSOFTX3000
V200R009C02SPH131 Patch.
Figure 1.1 describes the patch files included in the patch package.
Figure 1.1 List of patch files
ME
Patch
Folder
Patch File
Description
CGP
CGP_V100R0
06C02SPC527
CGP_V100R006C02S
PC527.tar
CGP patch package, including the

CGP hot patch and cold patch
Issue 01 (2015-02-15)

Copyright
15

Patch Update Guide
ME
MSOFTX
3000
Patch
Folder
MSOFTX_V2
00R009C02SP
H131
Patch File
Description
CGP_V100R006C02S
PC527.sgn
Digital signature file, used for

remote patch installation
upgradecfg.xml
Procedural file for the network

management system, used for
upgradecfg.sgn

Vercfg.xml
Version description file, used for

vercfg.sgn

MSOFTX_V200R009
C02SPH131.tar
MSOFTX3000 patch package,

including the MSOFTX3000 hot
patch and cold patch
MSOFTX_V200R009
C02SPH131.sgn

upgradecfg.xml
Procedural file for the network

management system, used for
upgradecfg.sgn

Vercfg.xml
Version description file, used for

vercfg.sgn

----End
1.3.4 Checking the Integrity of the Downloaded

Software Packages
To ensure that the obtained patch software is not corrupted, perform the following steps to
check its integrity:
Step 1 Download the OpenPGP tool for software digital signature verification.
Start Internet Explorer, and then enter http://support.huawei.com/carrier/digitalSignatureAction in
the address bar to download the OpenPGP tool.
Step 2 Double-click PGPVerify.exe to use the PGP tool to check the integrity of the patch software
package. For details, see section 4.3.2 "Verifying Through Operations on the UI" in the
OpenPGP Signature Verification Guide.
Issue 01 (2015-02-15)

Copyright
16

Patch Update Guide
----End
1.3.5 Checking the M2000 Common Version and

Mediation Version
Before installing or rolling back MSOFTX3000 V200R009C02SPH131, ensure that you have
installed the M2000 server with the M2000 mediation version compatible with the target
patch. Otherwise, functions of the target patch may become unavailable.
To check the M2000 version, perform the following steps:
Step 1 On the PC that runs the M2000 client, choose Start > Programs > iManager M2000 Client
> M2000 Client. Then, enter your user name and the password to log in to the M2000 client.
Step 2 On the M2000 client, choose Software > Browser to launch the Software Browser window.
In the NM Server tab page, choose Server > OMC. The M2000 common version is
displayed in the right pane, as shown in Figure 1.1.
Figure 1.1 Checking the M2000 common version
Step 3 Check whether the M2000 common version is correct according to Figure 1.1. If the M2000
common version is incorrect, install the M2000 common version by referring to the relevant
operation guide, and then follow this guide to complete the subsequent steps.
Figure 1.1 M2000 common version
Item
Version
M2000 common version
V200R012C00SPC200
Issue 01 (2015-02-15)

Copyright
17

Patch Update Guide
The M2000 common version number is named in the format of VxxxRxxxCxxSPCxxx. When
checking the version number, first check the V version number, and then the R, C, and SPC version
numbers. For example, V200R009ENGC00SPC020 is later than V200R009C00SPC010, because
their V and R and C version numbers are the same but the SPC version number of the former is
greater than that of the latter.
For the M2000 common version mapping the MSOFTX3000 V200R009C02SPH131, refer to Figure
1.1.
Step 4 In the NM Server tab page, choose Server > OMC > Mediation > MSC Server. The M2000
mediation versions are displayed in the right pane, as shown in Figure 1.1.
To check the M2000 mediation versions of the CGP, choose Server > OMC > Mediation >
CGPOMU in the NM Server tab page.
The M2000 mediation versions are displayed in the MatchVersion column, as shown in Figure 1.1.
Figure 1.1 Checking the M2000 mediation versions
Step 5 Check whether the M2000 mediation version, which is compatible with
MSOFTX3000V200R009C02SPH131, has been installed according to Figure 1.1. If the
mapping M2000 mediation version has not been installed, install the M2000 mediation
version by referring to section 1.4.1"Loading the M2000 Mediation Version", and then follow
this guide to complete the subsequent steps.
Figure 1.1 M2000 mediation version compatible with MSOFTX3000V200R009C02SPH131
Item
Version
M2000 mediation version of the

CGP
iManagerM2000_CGPOMU_MATCH_ENG_V100R0
06C02SPC527
M2000 mediation version of the

MSOFTX3000
iManagerM2000_MSOFTX3000_MATCH_ENG_V2
00R012C02SPC074
----End
1.3.6 Checking the Baseline Patch Versions of the

Target MEs
One day before patch installation, perform the following steps to check the baseline patch
versions of the target MEs:
Issue 01 (2015-02-15)

Copyright
18

Patch Update Guide
Step 1 Log in to HUAWEI Operation & Maintenance System, and run DSP CPATCH on the CGP
MML command interface. Then, check whether the cold patch versions of CGP and
MSOFTX3000 comply with Figure 1.1.
Yes => The baseline cold patch versions of CGP and MSOFTX3000 comply with the
target patch. In this case, go to Step 2.
No => The baseline cold patch versions of CGP and MSOFTX3000 do not comply with
the target patch. In this case, go to Step 3.
Figure 1.1 Cold patch versions

ME
Displayed Patch Version
CGP
SPC527 or earlier version
MSOFTX3000
SPC131 or earlier version
Step 2 Run DSP PATCH on the CGP MML command interface. Then, check whether the displayed
hot patch versions of CGP and MSOFTX3000 comply with Figure 1.1.
Yes => The baseline hot patch versions of CGP and MSOFTX3000 comply with the
target patch. In this case, go to Step 4.
No => The baseline hot patch versions of CGP and MSOFTX3000 do not comply with
the target patch. In this case, go to Step 3.
Figure 1.1 Hot patch versions

ME
Displayed Patch Version
CGP
SPH527 or earlier version
MSOFTX3000
SPH131 or earlier version
Step 3 The patch version does not meet the requirement. In such a case, you do not need to perform
subsequent operations. Check whether the obtained patch package and patch update guide are
correct.
Yes => Stop the patch installation and contact Huawei for technical assistance.
No => Download the correct patch package and patch update guide, and then repeat the
preparations according to the patch update guide.
Step 4 The patch version meets the requirement. In such a case, continue with the next check item.
----End
Issue 01 (2015-02-15)

Copyright
19

Patch Update Guide
1.3.7 Checking the OMU Board Status
If OMU boards work in High Availability (HA) mode, install the OMU patch only when both
active and standby OMU boards are operational. Otherwise, installing the OMU patch fails.
The patch installation must be performed after the active OMU board has synchronized with
the standby OMU board. To check whether the active OMU board has synchronized with the
standby OMU board, run LST SYNC.
One day before patch installation, perform the following steps to check the status of OMU
boards:
Step 1 Log in to HUAWEI Operation & Maintenance System, and run DSP OMU on the CGP MML
command interface.
Step 2 Check the displayed output for OMU board status. If OMU State in OMU Base Info is
Active for one OMU board and Standby for the other OMU board, as shown in Figure 1.1, it
indicates that both active and standby OMU boards are operational.
Figure 1.1 Sample output of the DSP OMU command
----End
1.3.8 Checking Whether Reserved MML Command

Options Put into Use in the Patch Are Set to Default
Values
Step 1 Log in to HUAWEI Operation & Maintenance System, and run EXP MML in the MML
Command CGP window to export the configuration data files.
Issue 01 (2015-02-15)

Copyright
20

Patch Update Guide
EXP MML: MEID=5, EXPTYPE=LOCAL;
The exported configuration data files are stored in the directory

/opt/HUAWEI/cgp/workshop/omu/share/export/mit/mml on the OMU. You can download the files
using the file transfer service on HUAWEI Operation & Maintenance System.
Step 2 Open the configuration data files and check whether the reserved MML command options
listed in Figure 1.1 are set to the default values. If they are not set to the default values, refer
to the related configuration in the MSOFTX3000 V200R009C02SPH131 Patch Notes to
determine whether to change them to the default values.
The SVR29 option of the BOFFICEEXTRAPARA2 parameter in the ADD OFC command
is used as an example.
In the configuration data file, find the data record identified by ADD OFC and
BOFFICEEXTRAPARA2. Then, check the value of SVR29. SVR29-0 indicates that the
SVR29 option is set to 0 and SVR29-1 indicates that the SVR29 option is set to 1.
You need not check the options that have taken effect in the currently installed patch. For example, if
the currently installed patch is SPH101 and the options put into use in SPH101 have taken effect,
you need not check them in SPH101; instead, you need to check only the reserved options put into
use in the patches later than SPH101. For details, refer to the MSOFTX3000
V200R009C02SPH131Patch Notes.
If you do not find a matched data record in the configuration data files for the MML command listed
in Figure 1.1, the MSOFTX3000 is not configuration with the related data and the related reserved
option is automatically set to the default value.
Figure 1.1 MML command options put into use

Patch
Versio
n
MML
Command
Parameter
Option
Default
Value
SPH131
ADD OFC
BOFFICEEXTRAPARA2
SVR29
SPH128
ADD OFC
BOFFICEEXTRAPARA2
SVR25
SPH127
ADD RNC
HOPARA
RSVBIT30
SPH126
ADD SIPTG
ESFPARA4
SRV16
SPH123
ADD SIPTG
ESFPARA4
SRV18
SPH119
ADD SIPTG
ESFPARA4
SRV9
SPH110
ADD
CLDPREANA
CLISRVCAT
SERVICE41
ADD
CLDPREANA
CLISRVCAT
SERVICE31
ADD RNC
CAPABILITY
RSVBIT14
ADD CASTG
SVRCTRL
SVR12
ADD CASTG
SVRCTRL
SVR13
ADD SIPTG
ESFPARA3
SRV11
SPH107
SPH106
Issue 01 (2015-02-15)

Copyright
21

Patch Update Guide
Patch
Versio
n
MML
Command
Parameter
Option
Default
Value
NUMP
RESERVE2
ADD SIPTG
ESFPARA2
SRV30
ADD SIPTG
ESFPARA2
SRV29
ADD OFC
BOFFICEEXTRAPARA2
SVR6
ADD SIPTG
ESFPARA2
SRV22
ADD SIPTG
ESFPARA2
SRV31
ADD
CALLPRICHK
SPH105
SPH103
----End
1.3.9 Checking Whether the Software Parameters

Added in the Patch Are Set to the Default Values
Log in to HUAWEI Operation & Maintenance System, and run LST MSFP on the
MSOFTX3000 MML command interface to check whether the software parameters added in
the patches released after the currently installed patch are set to the default values. If they are
not set to the default values, determine whether to change them to the default values. For
details on how to set the software parameters, refer to the configuration description in the
MSOFTX3000 V200R009C02SPH131 Patch Notes.
You need not check the software parameters that have taken effect in the currently installed patch. For
example, if the currently installed patch is SPH101 and the software parameters added in SPH101 have
taken effect, you need not check the software parameters added in SPH101; instead, you need to check
only the software parameters added in the patches later than SPH101. For details, refer to the
MSOFTX3000 V200R009C02SPH131Patch Notes.
Figure 1.1 Software Parameters Added in the Patch

Patch
Version
Software Parameters
SPH131
Bit 11 of P1105 (**** X*** **** ****): The default value is 1.

Bit 10 of P680 (**** *X** **** ****): The default value is 0.
Bit 8 of P1512 (**** ***X **** ****): The default value is 1.
Bit 15 of P1510 (X*** **** **** ****): The default value is 1.
Bit 0 of P957 (**** **** **** ***X): The default value is 1.
Bit 9 of P680 (**** **X* **** ****): The default value is 0.
Bit 14 of P1104 (*X** **** **** ****): The default value is 1.
Bit 4 of P1523 (**** **** ***X ****): The default value is 1.
Issue 01 (2015-02-15)

Copyright
22

Patch Update Guide
Patch
Version
Software Parameters
SPH130
N/A
SPH129

Bit 12 of P420 (***X **** **** ****): The default value is 0.
Bits 13-12 of P391 (**XX **** **** ****): The default value is 11.
Bit 3 of P846 (**** **** **** X***): The default value is 1.
SPH128

Bits 13-12 of P685 (**XX **** **** ****): The default value is 00.
Bit 13 of P956 (**X* **** **** ****): The default value is 1.
Bit 2 of P847 (**** **** **** *X**): The default value is 1.
Bits 15-0 of P1511 (XXXX XXXX XXXX XXXX): The default value is
1111111111111111.
1111111111111111.
1111111111111111.
0000000000000000.
0000000000000000.
Bit 7 of P1314 (**** **** X*** ****): The default value is 1.
Issue 01 (2015-02-15)

Copyright
23

Patch Update Guide
Patch
Version
Software Parameters
SPH127

Bits 6-4 of P1156 (**** **** *XXX ****): The default value is 111.
Issue 01 (2015-02-15)

Copyright
24

Patch Update Guide
Patch
Version
Software Parameters
SPH126

Bit 6 of P1538 (**** **** *X** ****): The default value is 1.
Bit 5 of P1370 (**** **** **X* ****): The default value is 1.
Bits 14-13 of P1028 (*XX* **** **** ****): The default value is 11.
Issue 01 (2015-02-15)

Copyright
25

Patch Update Guide
Patch
Version
Software Parameters
SPH125

SPH124

Bits 2-0 of P549 (**** **** **** *XXX): The default value is 111.
Issue 01 (2015-02-15)

Copyright
26

Patch Update Guide
Patch
Version
Software Parameters
SPH123

Bits 14-8 of P419 (*XXX XXXX **** ****): The default value is
0000000.
Bits 1-0 of P420 (**** **** **** **XX): The default value is 00.
Bits 7-6 of P1105 (**** **** XX** ****): The default value is 11.
Issue 01 (2015-02-15)

Copyright
27

Patch Update Guide
Patch
Version
Software Parameters
SPH122

Bits 15-12 of P448 (XXXX **** **** ****): The default value is 1000.
Bits 15-12 of P678 (XXXX **** **** ****): The default value is 0000.
SPH121

Bit 1 of P419 (**** **** **** **X*): The default value is 0.
Bits 8-6 of P39 (**** ***X XX** ****): The default value is 111.
Issue 01 (2015-02-15)

Copyright
28

Patch Update Guide
Patch
Version
Software Parameters
SPH120

Bits 6-0 of P1157 (**** **** *XXX XXXX): The default value is
1110000.
SPH119

1111111111111111.
Issue 01 (2015-02-15)

Copyright
29

Patch Update Guide
Patch
Version
Software Parameters
SPH118

Bits 15-14 of P416 (XX** **** **** ****): The default value is 00.
Issue 01 (2015-02-15)

Copyright
30

Patch Update Guide
Patch
Version
Software Parameters
SPH117

1111111.
1111111.
Issue 01 (2015-02-15)

Copyright
31

Patch Update Guide
Patch
Version
Software Parameters
SPH116

SPH115

SPH114
N/A
SPH113

Issue 01 (2015-02-15)

Copyright
32

Patch Update Guide
Patch
Version
Software Parameters
SPH112

Bits 7-6 of P845 (**** **** XX** ****): The default value is 11.
Issue 01 (2015-02-15)

Copyright
33

Patch Update Guide
Patch
Version
Software Parameters
SPH111

Bit 15 of P671 (X *** **** **** ****): The default value is 0.
Bit 15 of P949 (X *** **** **** ****): The default value is 1.
SPH110

Bits 2-1 of P676 (**** **** **** *XX*): The default value is 00.
SPH109

Issue 01 (2015-02-15)

Copyright
34

Patch Update Guide
Patch
Version
Software Parameters
SPH108

SPH107

Issue 01 (2015-02-15)

Copyright
35

Patch Update Guide
Patch
Version
Software Parameters
SPH106
Bits 15~0 of P417 (XXXX XXXX XXXX XXXX): The default value is
0xFFFF.
Bits 15~8 of P1102 (XXXX XXXX **** ****): The default value is
1111 1111.
Issue 01 (2015-02-15)

Copyright
36

Patch Update Guide
Patch
Version
Software Parameters
SPH105

Bits 7-0 of P393 (**** **** XXXX XXXX): The default value is 0xFF.
SPH103

0xFFFF.
SPH102
SPH101

Issue 01 (2015-02-15)

Copyright
37

Patch Update Guide
1.3.10 Performing a CRC
A cyclic redundancy check (CRC) may consume a great amount of system resources.
Therefore, perform a CRC only when traffic is light.
One day before patch installation, perform the following steps to conduct a CRC:
Step 1 Log in to HUAWEI Operation & Maintenance System, and run FMT on both CGP and
MSOFTX3000 MML command interfaces to format all the data.
Step 2 Run the following command on both CGP and MSOFTX3000 MML command interfaces to
check data consistency between the host and the OMU.
STR CRC: CRCTYPE=ALL, SSR=YES;
Step 3 Check whether the value of CRC check inconsistent is 0 in the CRC results.
Yes => Continue with the next check item.
No => Restore data consistency by referring to the online Help of STR CRC.
----End
1.3.11 Performing Pre-Patching Check

The pre-patching check covers the basic environmental items, such as system configuration, software
running status, and hardware running status.
The pre-patching check was introduced from MSOFTX3000 V200R009C02SPH123. If you never
installed the SPH123 or later before, upload the CGP and MSOFTX3000 patch packages for this patch
and then perform the pre-patching check. For details about how to upload the CGP and MSOFTX3000
patch packages, see 1.4.2"Uploading the CGP Patch Package" and 1.4.3"Uploading the MSOFTX3000
Patch Package."
To ensure the correctness of the check result, do not use the VTS tool or run the GET
SYSINFO or STR OSCRC command during the pre-patching check.
Step 1 Open the Internet Explorer, type http://floating IP address of the OMU (for example,
http://167.1.5.5) in the address bar, and press Enter to switch to the login window of Huawei
Operation & Maintenance System, as shown in Figure 1.1.
You can directly enter the login window for Patch & Upgrade Tool by typing https://floating IP address
of the OMU:7443/upg/ (for example, https://167.1.5.5:7443/upg/) in the address bar and pressing
Enter.
Issue 01 (2015-02-15)

Copyright
38

Patch Update Guide
Figure 1.1 WebUI login dialog box
Step 2 Enter the user name and password (same as the user name and password for logging in to
Huawei Operation & Maintenance System client) and select Local for User type. Click
Login.
Step 3 In the Huawei Operation & Maintenance System window displayed, click Patch &
Upgrade Tool, as shown in Figure 1.1.
Figure 1.1 Patch & Upgrade Tool
Issue 01 (2015-02-15)

Copyright
39

Patch Update Guide
Step 4 In the Patch navigation tree, click Patch Check, as shown in Figure 1.1.
Figure 1.1 Patch Check icon
Step 5 In the Select Check ME tab page displayed, select the required ME and the target patch
version on the Select Check ME page, as shown in Figure 1.1.
Figure 1.1 Select Check ME tab page
If no CGP patch package is uploaded, the target patch version is displayed empty and the prepatching check task cannot be created.
The system displays the default target patch version in the Target patch version column.
Confirm whether the default patch version is correct. If not, click the default patch version
displayed and select the correct target patch version from the drop-down list.
Step 6 Click the Pre-Patching Check icon above the table. The Confirm dialog box is displayed, as
shown in Figure 1.1.
Issue 01 (2015-02-15)

Copyright
40

Patch Update Guide
Figure 1.1 Confirm dialog box
Step 7 Click OK. The Pre-Patching Check Control tab page is displayed, as shown inFigure 1.1.
Figure 1.1 Pre-Patching Check tab page
Step 8 After the check is complete, the Question dialog box is displayed, as shown in Figure 1.1.
Click Continue. After about 10 seconds, the Pre-Patching Check Control tab page will be
refreshed with Upgrade check task is completed displayed, as shown in Figure 1.2.
Figure 1.1 Question dialog box
Figure 1.2 Check completion notification
Issue 01 (2015-02-15)

Copyright
41

Patch Update Guide
Step 9 Click View Report from the Patch navigation tree, as shown in Figure 1.1.
Figure 1.1 View Report icon
Step 10 In the navigation tree of the Select Patch Report ME tab page, select the latest pre-patching
check. Then, select Select all, as shown in Figure 1.1.
Figure 1.1 Select Patch Report ME tab page
Step 11 Click View ME report to open the pre-patching check report.

Step 12 Check whether all MEs pass the pre-patching check, as shown in Figure 1.1 (This document
uses CGP Pre-Patching Check Report as an example).
Figure 1.1 Basic information in the pre-patching check report
Issue 01 (2015-02-15)

Copyright
42

Patch Update Guide
Yes: No further action is required.
No: Go to Step 13.
Step 13 Click the operation that is marked as Warning or Failed to expand the operation information,
as shown in Figure 1.1.
Figure 1.1 Operation details
Step 14 Handle each failed operation according to the procedure provided in Suggestion in operation
information.
If the check result of an operation is Warning due to a known issue, contact technical support to check
whether this issue has impacts on patch installation. No action is required if the known issue has no
impacts on patch installation.
If an operation fails again after the procedure provided in Suggestion has been performed, contact
technical support.
Step 15 Repeat the pre-patching check from Step 4.

----End
1.3.12 Checking the Connection to the SOSM XPTU

by Using NetMeeting (Optional)
Issue 01 (2015-02-15)

Copyright
43

Patch Update Guide
The SOSM XPTU is used in AIS only. If the local MSOFTX3000 does not have a SOSM
XPTU, skip this section.
During the remote patch installation, only the NetMeeting can be used to remotely log in
to the SOSM XPTU server.
The NetMeeting is recommended for remote maintenance if the patch installation fails. If
you are not allowed to log in to the SOSM XPTU server through NetMeeting, skip this
operation.
To set up a NetMeeting connection, perform the following steps:

Step 1 On the PC that runs the M2000 client, choose Start > Programs > Accessories >
Communications > NetMeeting.
Step 2 Choose Call > New Call. The Place a Call dialog box is displayed, as shown in Figure 1.1.
Figure 1.1 Making a call
Step 3 Enter the IP address of the SOSM XPTU server, choose Automatic, select Required security
for this call (data only), and then click Call.
If the PC fails to connect to the SOSM XPTU server through NetMeeting, you can start NetMeeting on
the SOSM XPTU server with permission of the carrier. For details, see 3.7"How to Set Remote Desktop
Sharing."
Step 4 In the Remote Desktop Sharing Password dialog box, enter the correct user name,
password, and domain information required to log in to the SOSM XPTU server, and click
OK.
----End
1.3.13 Updating SFU on the SOSM XPTU Server

(Optional)
Issue 01 (2015-02-15)

Copyright
44

Patch Update Guide
The SOSM XPTU is used in AIS only. If the local MSOFTX3000 does not have a SOSM
XPTU, skip this section.
The SFU.zip file is released in the patch package since V200R009C02SPH120. If you
have updated the SFU before this patch is installed, please skip this section.
Step 1 Obtain SFU.zip in the patch package MSOFTX3000 V200R009C02SPH131_Software.zip.

Step 2 Follow the steps in the MSOFTX3000 V200R009C02 Guide to Updating SFU obtained from
the SFU.zip to upgrade the SFU.
----End
1.3.14 Checking the Impact of the Mediation Version

Installation on the NMS
To address the issue that the M2000 gives no response, the format of the Dest and
Destination and Office measurement objects are changed. As a result, the format of
measurement objects in the exported measurement result files is changed. The M2000 can
export measurement results in the .xml, .csv, and .txt files. For example, the original
destination code format was "DEST=6" and the new format is just "6", as shown in Figure 1.1
and Figure 1.2.
Figure 1.1 Format of a measurement object before the patch mediation installation
Figure 1.2 Format of a measurement object after the patch mediation installation
The format change of Dest may cause the failure of the NMS in parsing the measurement
result files. Therefore, the network management system (NMS) must be adjusted to support
the new identifiers for the following measurement objects:
Call Forwarding Traffic
VP Destination Traffic
Traffic Distribution by Office Destinations
----End
Issue 01 (2015-02-15)

Copyright
45

Patch Update Guide
1.4 Installing Patches

1.4.1 Loading the M2000 Mediation Version
Step 1 Install the M2000 mediation version.
For details about how to install the M2000 mediation version, see the operation guide of the
M2000 mediation version, which is released with MSOFTX3000 V200R009C02SPH131.
----End
1.4.2 Uploading the CGP Patch Package

Skip this section if the CGP patch package has been uploaded for this patch in section 1.3.11"Performing
Pre-Patching Check."
To upload the CGP patch package, perform the following steps:

Step 1 Log in to HUAWEI Operation & Maintenance System as user admin. Then, choose
Maintenance > File Transfer Service to launch the File Transfer Service interface.
Step 2 Upload the CGP patch package using the file transfer service.
1.
Select the directory where the CGP patch package is stored from the Local Directory
drop-down list box. Then, select Software package(auto loading) from the Remote
Directory drop-down list box.
2.
Right-click CGP_V100R006C02SPC527.tar in the Local Files List area and choose

Upload. Wait until the uploading of the CGP patch package is complete. When the
progress bar reaches 100%, it indicates that the CGP patch package has been
successfully uploaded.
Issue 01 (2015-02-15)

Copyright
46

Patch Update Guide
Figure 2.1 Loading the CGP patch package
----End
1.4.3 Uploading the MSOFTX3000 Patch Package

Skip this section if the MSOFTX3000 patch package has been uploaded for this patch in section
1.3.11"Performing Pre-Patching Check."
To upload the MSOFTX3000 patch package, perform the following steps:

Step 1 Log in to HUAWEI Operation & Maintenance System as user admin. Then, choose
Maintenance > File Transfer Service to launch the File Transfer Service interface.
Step 2 Upload the MSOFTX3000 patch package using the file transfer service.
1.
Select the directory where the MSOFTX3000 patch package is stored from the Local
Directory drop-down list box. Then, select Software package(auto loading) from the
Remote Directory drop-down list box.
2.
Right-click MSOFTX_V200R009C02SPH131.tar in the Local Files List area and

choose Upload. Wait until the uploading of the MSOFTX3000 patch package is
complete. When the progress bar reaches 100%, it indicates that the MSOFTX3000
patch package has been successfully uploaded.
Issue 01 (2015-02-15)

Copyright
47

Patch Update Guide
----End
1.4.4 Installing the Patch Using the WebUI

The patch installation procedure provided in this section assumes that no error is encountered
while installing MSOFTX3000 V200R009C02SPH131. If an error is encountered while
installing the patch, correct the error by referring to 1.4.5"Correcting Patch Installation
Errors."
1.
Before you log in to the WebUI, ensure that you have logged in to HUAWEI Operation
& Maintenance System at least once. Otherwise, you will be prompted to modify the
admin password to validate the admin user account.
2.
If patches are available for the CGP and the MSOFTX3000, do not install the
MSOFTX3000 patch before installing the CGP patch.
3.
The OMU's cold patch in the MSOFTX3000 V200R009C02SPH112 patch package uses
a reserved measurement unit. If the SPH112 patch is not installed before, the system will
load NE files again after the OMU installation During this patch installation. The loading
process is complete within 15 minutes. In this loading process, the performance
measurement service is interrupted and the measurement statistics may be lost. After the
NE files are loaded, the performance measurement service is recovered.
4.
Before installing the patch, exit the KVM over IP or serial over LAN (SOL) connection.
Otherwise, the patch installation may fail.
To install MSOFTX3000 V200R009C02SPH131 using the WebUI, perform the following

steps:
Step 1 Start the Internet Explorer, type http://<IP address of the CGP>, for example,
http://10.85.129.38, and then press Enter. A login dialog box is displayed. Enter the admin
password to log in to the WebUI.
A security alert, as shown in Figure 1.1, may be displayed prior to the login dialog box. Click Yes to
switch to the login dialog box.
Issue 01 (2015-02-15)

Copyright
48

Patch Update Guide
Figure 1.1 Security alert
Step 2 In the navigation interface of the WebUI shown in Figure 1.1, click Patch & Upgrade Tool.
Figure 1.1 Navigation interface of the WebUI
Step 3 In the Welcome interface shown in Figure 1.1, click Patch to switch to the Select Patch ME
page.
Issue 01 (2015-02-15)

Copyright
49

Patch Update Guide
Figure 1.1 Launching the patch installation interface
Step 4 Select the relevant MEs and the target patch versions.
By default, Target patch version displays the latest patch version that can be installed. If
multiple patch versions are available for installation, select the desired patch version from
the drop-down list box.
If Target patch version displays --, it indicates that no patch version is available for the
corresponding ME. In this case, you need to quit the patch installation.
If Current patch version displays the patch versions that you want to install, it indicates
that the target patch versions have been installed. In this case, you need to quit the patch
installation.
1.
Select the types of ME for patch installation. In this installation procedure, select both
CGP and MSOFTX3000.
2.
Select the target patch versions, for example, CGP_V100R006C02SPC527 and

MSOFTX_V200R009C02SPH131.
Issue 01 (2015-02-15)

Copyright
50

Patch Update Guide
Figure 2.1 Selecting the desired MEs for patch installation
Step 5 Click Patch in the upper left corner of the Select Patch ME page, as shown in Figure 1.1.
The Confirm dialog box is displayed, asking whether to continue with the patch installation.
Figure 1.1 Confirming whether to install the patch
Issue 01 (2015-02-15)

Copyright
51

Patch Update Guide
Step 6 Click OK to switch to the Patch Control tab page.

The WebUI starts the pre-installation check and displays the checking progress, as shown in
Figure 1.1.
If you want to know more details about patch installation on a certain ME, click Detail in the Detail
column of the ME. The Patch Detail page is displayed, as shown in Figure 1.2. This tab page provides
information about the step being performed, current progress, and overall progress.
Figure 1.1 Performing the pre-installation check
Issue 01 (2015-02-15)

Copyright
52

Patch Update Guide
Figure 1.2 Viewing the details about patch installation on a certain ME
Step 7 When the pre-installation check is complete, the WebUI displays "Patch prepare complete.
Please click Continue or Rollback", as shown in Figure 1.1. Click Continue to move on to the
patch installation phase.
Figure 1.1 Pre-installation check completed
Issue 01 (2015-02-15)

Copyright
53

Patch Update Guide
Step 8 When the patch installation is complete, the WebUI displays "All ME patch implementation
complete. Please click Continue or Rollback", as shown in Figure 1.1. Click Continue, to
move on to the patch confirmation phase.
Figure 1.1 Patch installation completed
If the cold patch of CGP has been installed in the previous step, the OMU process restarts. The
restarting process takes approximately 4.5 minutes.
If the iGWB patch has been installed together with the CGP and MSOFTX3000 patches, the iGWB
process restarts. The restarting process takes approximately 5 minutes.
If the WebUI displays a message indicating that querying the OMU service status fails, log in to the
OMU board using Putty, run startall to restart all the OMU services, and then run omustatus to
check whether the OMU services are running normally. If all the services are running normally, click
Retry on the WebUI.
Step 9 When the patch confirmation phase is complete, the WebUI displays "All the MEs are
successfully upgraded. Please click Continue", as shown in Figure 1.1. Click Continue, to
end the patch installation.
Issue 01 (2015-02-15)

Copyright
54

Patch Update Guide
Figure 1.1 Patch confirmation completed
Step 10 When patch installation is complete, Progress of each ME changes to 100%, and Status
changes to XXX patch succeeded. In addition, the WebUI displays the Patch task is
completed message, as shown in Figure 1.1. Click OK.
Figure 1.1 Patch installation completed
Issue 01 (2015-02-15)

Copyright
55

Patch Update Guide
Step 11 If required, obtain the patch installation report.

1.
Switch to the WebUI navigation interface, as shown in Step 3Figure 1.1. Then, click
View Report to switch to the Select Patch Report ME page.
2.
Select the desired ME, and click View ME report in the upper left corner of the Select
Patch Report ME page. The patch installation report of the selected ME is displayed.
Step 12 Run FMT on the CGP MML command interface to format all the CGP data.
Step 13 Run STR CRC on the CGP MML command interface to check whether data is consistent
between the OMU board and service processing boards.
Yes => Step 15
No => Step 14
Step 14 Run SND CRCERR on the CGP MML command interface to synchronize data from the
OMU board to service processing boards. Then, repeat Step 13.
Step 15 Run FMT on the MSOFTX3000 MML command interface to format all the MSOFTX3000
data.
Step 16 Run STR CRC on the MSOFTX3000 MML command interface to check whether data is
consistent between the OMU board and service processing boards.
Yes => Step 18
No => Step 17
Step 17 Run SND CRCERR on the MSOFTX3000 MML command interface to synchronize data
from the OMU board to service processing boards. Then, repeat Step 16.
Step 18 Run FMT on the IGWB MML command interface to format all the IGWB data.
Step 19 Run STR CRC on the IGWB MML command interface to check whether data is consistent
Yes => Step 21
No => Step 20
Step 20 Run SND CRCERR on the IGWB MML command interface to synchronize data from the
Step 21 In the MML Command CGP window, run CHK FW:; to check whether Result of version
check of the firmware is Mismatch.
Yes: Step 22
No: Step 23
Step 22 Rectify the fault based on the handling procedure in ALM-8309 Board Firmware Version and
OMU Version Mismatch and check whether Result of version check of the firmware is
Consistent.
Yes: Step 23
No:Contact Huawei technical support engineers.
Step 23 Reset the SMM board.

The CGP V100R006C02SPC527 patch includes the firmware file of the SMM board.
Issue 01 (2015-02-15)

Copyright
56

Patch Update Guide
If the source version is earlier than V100R006C02SPC527, reset the SMM board to keep the SMM
board firmware consistent with the OMU firmware file.
Perform the following operations to reset the SMM board:

1.
In the MML Command - CGP window on the OMU client, run DSP BRD to query the
status of SMM boards in slots 14 and 15.
2.
In the MML Command - CGP window on the OMU client, run RST BRD to reset
those SMM boards whose Availability state is Standby. The reset is complete about 10
minutes later.
3.
status of the SMM board after the reset.
The reset is successful if Availability state in the command output is Standby.
If Availability state in the command output is Fault, query the board status 5 minutes later. If
Availability state remains as Fault, contact Huawei technical support.
4.
In the MML Command - CGP window on the OMU client, run SWP BRD to switch
over the SMM board whose Availability state is Active. The switchover is complete
about 10 seconds later.
5.
status of the SMM board after the switchover.
6.
7.
The switchover is successful if Availability state in the command output is Standby.
If Availability state in the command output is Fault or Active, query the board status 5 minutes
later. If Availability state remains as Fault or Active, contact Huawei technical support.
In the MML Command - CGP window on the OMU client, run CHK FW with Show
compatible record set to Yes to query the version of the firmware on reset SMM boards
in slots 14 and 15. Check whether Run version of SMMD_APP or SMME_APP is the
same as Configured version.
When Result of version check in the command output is Consistent, Run version and Configured
version may be different, for example, Run version can be later than Configured version.
If Run version is different from Configured version, contact Huawei technical support.
Repeat 1 to 6 till all SMM boards are reset.
----End
1.4.5 Correcting Patch Installation Errors

Patch installation of the CGP/MSOFTX3000 may be interrupted because of errors. If an error
is encountered during patch installation on a certain ME, for example, the CGP, the patch
control information of the CGP is highlighted in red, yellow, or green, as shown in Figure 1.1.
Issue 01 (2015-02-15)

Copyright
57

Patch Update Guide
Figure 1.1 Errors detected in patch installation on the CGP
If patch control information is highlighted in red, it indicates that the current operation has failed.
If patch control information is highlighted in yellow, it indicates that a warning is generated against
the current operation.
If patch control information is highlighted in green, it indicates that an informative message is

generated while the current operation is being performed.
To correct patch installation errors, perform the following steps:

Step 1 Click Detail in the Detail column of the corresponding ME. The Patch Detail page similar to
Figure 1.1 is displayed.
Issue 01 (2015-02-15)

Copyright
58

Patch Update Guide
Figure 1.1 Viewing the Patch Detail page
Step 2 Click View Report. A patch installation report similar to Figure 1.1 is displayed. View the
report to identify the operation that has failed. Then, rectify the failure according to the
analysis information provided in the report.
Figure 1.1 Viewing the CGP patch installation report
Issue 01 (2015-02-15)

Copyright
59

Patch Update Guide
An operation record in the patch installation report may be highlighted in green, yellow, or red.
Green indicates that the current operation is successful.
Yellow indicates that a warning has been generated against the current operation but it does not
affect subsequent operations. The Skip option is generally provided for you to skip the current
operation. If you click Skip in this step, certain patch functions will be unavailable. Therefore, you
are advised to correct the error according to the suggestion provided in the patch installation report.
Red indicates that the current operation has failed and the failure affects subsequent operations.
Generally, the operation can be skipped.
Step 3 Perform an appropriate operation according to the error correcting result.
If the error is corrected, click Retry in the Patch Detail page shown in Step 1Figure 1.1
to perform the operation again.
If the error cannot be corrected, check whether the error affects patch installation
according to the reason, effect, and suggestion provided in the report. If the error does
not affect patch installation, click Skip in the Patch Detail page, as shown in Step
1Figure 1.1. If the error affects the patch installation, click Rollback in the Patch Detail
page shown in Step 1Figure 1.1 to roll back to the original version.
When the patch rollback is complete, "All ME patch rollback complete. Please click Continue" is
displayed. Click Continue, and "The rollback is complete" is displayed. Click OK and close the Internet
Explorer.
----End
1.4.6 Loading the Client Patch

To load the OMU client patch, perform the following steps:
Before loading the OMU client patch, you must re-log in to HUAWEI Operation &
Maintenance System.
Step 1 On the PC where HUAWEI Operation & Maintenance System is installed, choose Start >
Programs > HUAWEI Operation and Maintenance System > HUAWEI Operation and
Maintenance System. Then, enter your user name and password in the Login dialog box and
click Login.
Step 2 Check whether the prompt shown in Figure 1.1 is displayed.
Yes => Step 3
No => End
Issue 01 (2015-02-15)

Copyright
60

Patch Update Guide
Figure 1.1 Prompt for OMU client patch update
Step 3 Click Yes. The system automatically updates the OMU client patch, as shown in Figure 1.1.
Figure 1.1 Updating the OMU client patch
Step 4 HUAWEI Operation & Maintenance System is automatically restarted after the patch update
is complete. Enter your user name and password in the Login dialog box to re-log in to
HUAWEI Operation & Maintenance System. If re-login to HUAWEI Operation &
Maintenance System is successful, it indicates that the OMU client patch is successfully
installed.
----End
1.4.7 Loading the XPTU Patch

The XPTU patch is installed only on the XPTU server used for SOSM interception.
Install the OS security patch of the Windows 2003 Server on the XPTU server used for SOSM
interception in a timely manner.
To obtain the OS security patch of the Windows 2003 Server, choose Software Center >
Controlled Tool (Mini-tool Software) > Core Network Product Line > Safety Protection >
Windows2003 on the Huawei Support website. The latest OS security patch of the Windows 2003
Server is Win2003_EN[2014Q2].exe.
To load the OS security patch of the Windows 2003 Server, download the installation package to a
root directory of a disk on the XPTU server, double-click the installation package, and then follow
the system prompts to load the OS security patch.
To load the XPTU patch, perform the following steps on the XPTU server:
Step 1 Copy the XPTU patch file specific to the interception protocol used in this office to the
installation path of the XPTU, for example, D:\XPTU.
Issue 01 (2015-02-15)

Copyright
61

Patch Update Guide
Step 2 Run the XPTU patch file, for example, Double-click

MSOFTX3000VxxxRxxxCxxSPHxxx_XPTU_SOSM.exe. The dialog box as shown in Figure
1.1 is displayed.
Figure 1.1 Starting the XPTU patch tool
Step 3 Click Loading. The window as shown in Figure 1.1 is displayed.
Issue 01 (2015-02-15)

Copyright
62

Patch Update Guide
Figure 1.1 Preparing for loading of the XPTU patch
Step 4 Click Continue. The system loads the XPTU patch.

Step 5 If the loading of the patch is successful, a dialog box as shown Figure 1.1 is displayed. Click
Close.
Issue 01 (2015-02-15)

Copyright
63

Patch Update Guide
Figure 1.1 Loading of the XPTU patch completed
----End
1.4.8 Configuring Data

For details about the data configuration related to the problems of the site, see "Configuration
Description" in Chapter 2 "Resolved Issues" in the MSOFTX3000 V200R009C02SPH131
Patch Notes.
Perform the data configuration only when the relevant problem occurs at your site.
Configuration Options Introduced to V200R009C02SPH112

This section describes how to configure the configuration options introduced to
Before installing this patch, run LST CASTG to check whether Connect without valid
caller number is set to False.
LST CASTG: TGN="XXX", QR=LOCAL, SOT=YES;
If Connect without valid caller number is set to False while the customer does not require
the MSOFTX3000 to restrict incoming R2 calls that do not have calling numbers or have
invalid calling number, run MOD CASTG to set Connect without valid caller number to
True.
MOD CASTG: TGN="XXX", NPCLR=YES;
Issue 01 (2015-02-15)

Copyright
64

Patch Update Guide
Configuration Options Introduced to V200R009C02SPH111

This section describes how to configure the configuration options introduced to
Before the patch installation, delete the data records in which Multi-area name is ALL from
the Home PLMN Roaming Prefix Data table, because these data records may be invalid and
cannot be deleted after the patch installation.
After the patch installation, run ADD HPLMNRP to configure data for the called prefix that
does not require the roaming CDRs.
1.5 Verifying Patch Installation

1.5.1 Verifying the Patch Version
To verify the patch version, perform the following steps:
Step 1 Log in to HUAWEI Operation & Maintenance System.
Step 2 Check whether the SOSM XPTU patch is successfully installed.
This step is required only when the SOSM XPTU patch is included in the patch package.
1.
Obtain the MSOFTX3000 patch report and save it to a local directory. For details on how
to view the patch report, see 3.2"How to View and Save the Patch Installation Report?"
2.
View the MSOFTX3000 patch report using the Internet Explorer. Click Patch
installation, as shown in Figure 3.1, to expand the Patch installation node until all the
details about patch installation are displayed.
3.
Check the result of the Load the XPTU patch operation. If the displayed result is
Success, it indicates the SOSM XPTU patch has been successfully installed.
Figure 3.1 Verifying the installation of the SOSM XPTU patch
Issue 01 (2015-02-15)

Copyright
65

Patch Update Guide
Step 3 Run DSP CPATCH on the CGP MML command interface. Then, check whether the
displayed cold patch versions of CGP and MSOFTX3000 comply with Figure 1.1.
Yes => It indicates that the cold patches in the MSOFTX3000 V200R009C02SPH131
patch package have been installed. In this case, go to Step 4.
No => It indicates that the cold patch in the MSOFTX3000 V200R009C02SPH131 patch
package are not installed. In this case, go to Step 5.
Figure 1.1 Cold patch versions displayed after patch installation

ME
Patch Name
Server Patch State
CGP
SPC527
Update
MSOFTX3000
SPC131
Update
If the displayed Server patch state is Update, it indicates that the target cold patches have been
successfully installed and put into service.
hot patch versions of CGP and MSOFTX3000 comply with Figure 1.1.
Yes => It indicates that the hot patches in the MSOFTX3000 V200R009C02SPH131
patch package have been installed. In this case, go to Step 6.
No => It indicates that the hot patches in the MSOFTX3000 V200R009C02SPH131

patch package are not installed. In this case, go to Step 5.
Figure 1.1 Hot patch versions displayed after patch installation

ME ID
Patch Name
State
0(CGP)
SPH527
Running
5(MSOFTX3000)
SPH131
Running
Step 5 Check whether the correct patch package is downloaded. If yes, contact your local technical
support center. If no, roll back to the previous patch version by referring to"2Patch Rollback",
and then download the correct patch package and install it.
Step 6 Move on to the function verification test. For details, see "1.5.2Verifying the Basic Functions"
and "1.5.3Verifying Patch Functions".
----End
1.5.2 Verifying the Basic Functions

To verify the patch loading result, perform the following steps:
Step 1 Check whether any new fault alarm is displayed in the Alarm Browse window. Normally, no
new fault alarms are generated.
Issue 01 (2015-02-15)

Copyright
66

Patch Update Guide
Step 2 Make a basic intra-MSC call and an outgoing call. Normally, the calls are connected
successfully.
Step 3 Create some performance measurement tasks and check the performance measurement result.
1.
Observe the CPU usage. For each module, the CPU usage should be approximately equal
to that measured in the same period of time a week ago.
2.
Observe the 2G or 3G originated call traffic. Normally, the traffic should be

approximately equal to that measured in the same period of time a week ago.
3.
Observe the incoming call traffic. Normally, the traffic should be approximately equal to
that measured in the same period of time a week ago.
----End
1.5.3 Verifying Patch Functions

Check whether the problems of the MSOFTX3000 are solved by MSOFTX3000
V200R009C02SPH131. For details about the function verification, see the MSOFTX3000
V200R009C02SPH131 Patch Release Notes.
Issue 01 (2015-02-15)

Copyright
67

Patch Update Guide
Patch Rollback
2.1 Precautions
Patch rollback is the process of returning the system to state before patch installation. After
patch installation is complete, roll back the patch as described in this section if errors are
detected in patch function verification or patch rollback is required for special purposes. If
patch installation cannot proceed because of errors, roll back the patch as described in
1.4.5Correcting Patch Installation Errors".
Skip this section if the V200R009C02SPH118 or a later patch has been installed at your site.
In the V200R009C02SPH118 patch, two reserved measurement units, "Traffic Measurement

of CSFB Service in Office Direction" and "LAC-Based CSFB Paging Measurement", are
used. Before rollback, run LST TRFCAPA in the MML Command MSOFTX3000
window on the LMT or M2000 clients to check whether measurement tasks for these two
units are available. If they are available, remove these tasks and then roll back the patch. This
operation can avoid CRC errors after rollback.
2.2 Rolling Back Patches

To roll back MSOFTX3000 V200R009C02SPH131, perform the following steps:
Step 1 Log in to WebUI, and switch to the WebUI navigation interface, as shown in Figure 1.1. Then,
click Rollback to switch to the Select Patch Rollback ME page.
Issue 01 (2015-02-15)

Copyright
68

Patch Update Guide
Figure 1.1 Launching the patch rollback interface
Step 2 Select the desired MEs for patch rollback.

Select the types of ME for patch rollback. In this rollback procedure, select both CGP and
MSOFTX3000.
Check whether the current patch version and target patch version are correct. If yes, click
Rollback in the upper left corner of the Select Patch Rollback ME page. The Confirm
dialog box is displayed, as shown in Figure 1.1, asking whether to continue with the patch
rollback.
Issue 01 (2015-02-15)

Copyright
69

Patch Update Guide
Figure 1.1 Selecting the desired MEs for patch rollback
Step 3 Click OK to switch to the Patch Rollback Control page, as shown in Figure 1.1. The target
MEs are automatically rolled back to the state before patch installation.
Figure 1.1 Patch Rollback Control page
Issue 01 (2015-02-15)

Copyright
70

Patch Update Guide
Step 4 Wait until the patch rollback is complete. When patch rollback is complete, the WebUI
displays "All ME patch rollback complete. Please click Continue", as shown in Figure 1.1.
Click Continue to end the rollback task.
Figure 1.1 Ending the rollback task
Step 5 When the rollback task is ended, Progress changes to 100%, and the WebUI displays The
rollback is complete, as shown in Figure 1.1. Click OK.
Issue 01 (2015-02-15)

Copyright
71

Patch Update Guide
Figure 1.1 Rollback completed
Step 6 Run FMT on the CGP MML command interface of HUAWEI Operation & Maintenance
System to format all the CGP data.
Step 7 Run STR CRC on the CGP MML command interface of HUAWEI Operation & Maintenance
System to check whether data is consistent between the OMU board and service processing
boards.
Yes => Step 9
No => Step 8
Step 8 Run SND CRCERR on the CGP MML command interface of HUAWEI Operation &
Maintenance System to synchronize data from the OMU board to service processing boards.
Then, repeat Step 7.
Step 9 Run FMT on the MSOFTX3000 MML command interface of HUAWEI Operation &
Maintenance System to format all the MSOFTX3000 data.
Step 10 Run STR CRC on the MSOFTX3000 MML command interface of HUAWEI Operation &
Maintenance System to check whether data is consistent between the OMU board and service
processing boards.
Yes => Step 12
No => Step 11
Step 11 Run SND CRCERR on the MSOFTX3000 MML command interface of HUAWEI Operation
& Maintenance System to synchronize data from the OMU board to service processing
boards. Then, repeat Step 10.
Step 12 Run FMT on the IGWB MML command interface to format all the IGWB data.
Issue 01 (2015-02-15)

Copyright
72

Patch Update Guide
Step 13 Run STR CRC on the IGWB MML command interface to check whether data is consistent
Yes =>Step 15
No =>Step 14
Step 14 Run SND CRCERR on the IGWB MML command interface to synchronize data from the
Step 15 Run the following command on the CGP MML command interface:
STR OSCRC: CONFIRM=Y;
Step 16 If required, obtain the patch rollback report.

Switch to the WebUI navigation interface, as shown in 1.4.4 IStep 3Figure 1.1. Then, click
View Report to switch to the Select Patch Report ME page.
Select the desired ME, and click View ME report in the upper left corner of the Select Patch
Report ME page. The patch rollback report of the selected ME is displayed.
Step 17 Reset the SMM board.
The CGP V100R006C02SPC527 patch includes the firmware file of the SMM board.
If the source version is earlier than V100R006C02SPC527, reset the SMM board to keep the SMM
board firmware consistent with the OMU firmware file.
Perform the following operations to reset the SMM board:

1.
2.
In the MML Command - CGP window on the OMU client, run RST BRD to reset
those SMM boards whose Availability state is Standby. The reset is complete about 10
minutes later.
3.
4.
In the MML Command - CGP window on the OMU client, run SWP BRD to switch
over the SMM board whose Availability state is Active. The switchover is complete
about 10 seconds later.
5.
6.
Issue 01 (2015-02-15)
If Availability state in the command output is Fault or Active, query the board status 5 minutes
later. If Availability state remains as Fault or Active, contact Huawei technical support.
In the MML Command - CGP window on the OMU client, run CHK FW for the CGP
with Show compatible record set to Yes to query the version of the firmware on reset
SMM boards in slots 14 and 15. Check whether Run version of SMMD_APP or
SMME_APP is the same as Configured version.

Copyright
73

Patch Update Guide
7.
Repeat 1 to 6 till all SMM boards are reset.
Step 18 To roll back the OMU client patch, perform the following steps:
Before rolling back the OMU client patch, you must re-log in to HUAWEI Operation &
Maintenance System.
1.
On the PC where HUAWEI Operation & Maintenance System is installed, choose Start
> Programs > HUAWEI Operation and Maintenance System > HUAWEI Operation
and Maintenance System. Then, enter your user name and password in the Login
dialog box and click Login. Check whether the prompt shown in Figure 1.1 is displayed.
Yes => Substep 2
No => End
Figure 1.1 Prompt for OMU client patch update
2.
Click Yes. The system automatically updates the OMU client patch, as shown in Figure
2.1.
Figure 2.1 Updating the OMU client patch
Issue 01 (2015-02-15)

Copyright
74

Patch Update Guide
HUAWEI Operation & Maintenance System is automatically restarted after the patch update
is complete. Enter your user name and password in the Login dialog box to re-log in to
HUAWEI Operation & Maintenance System. If re-login to HUAWEI Operation &
Maintenance System is successful, it indicates that the OMU client patch is successfully
rolled back.
Step 19 To roll back the XPTU patch, perform the following steps:
1.
Run the XPTU patch file, such as

MSOFTX3000VxxxRxxxCxxSPHxxx_XPTU_SOSM.exe in the XPTU installation
directory, for example, D:\XPTU. The dialog box as shown in Figure 1.1 is displayed.
Figure 1.1 Starting the XPTU patch tool
2.
Issue 01 (2015-02-15)
Click Uninstall. The dialog box as shown in Figure 2.1 is displayed.

Copyright
75

Patch Update Guide
Figure 2.1 Preparing for uninstall of the XPTU patch
3.
Click Continue to uninstall the XPTU patch.
4.
If the uninstall of the patch is successful, a dialog box as shown Figure 4.1 is displayed.
Click Close.
Issue 01 (2015-02-15)

Copyright
76

Patch Update Guide
Figure 4.1 Uninstall of the XPTU patch completed
----End
2.3 Verifying Patch Rollback

You may sometimes want to remove a patch and restore the system to the state before patch installation.
This process is known as patch rollback. For example, if the CGP cold and hot patches are SPC001 and
SPH001 before patch installation, then the CGP patch versions should also be SPC001 and SPH001 after
the rollback.
To verify the patch rollback, perform the following steps:

Step 1 Log in to HUAWEI Operation & Maintenance System.
Step 2 Run DSP CPATCH on the CGP MML command interface. Then, check whether the
displayed cold patch versions of MSOFTX3000 comply with 1.3.6 IStep 1Figure 1.1.
hot patch versions of MSOFTX3000 comply with 1.3.6 IStep 2Figure 1.1.
Step 4 Check whether the SOSM XPTU patch is successfully rolled back.
This step is required only when the SOSM XPTU patch is rolled back.
1.
Issue 01 (2015-02-15)
Obtain the MSOFTX3000 patch report and save it to a local directory. For details on how
to view the patch report, see 3.2"How to View and Save the Patch Installation Report?"

Copyright
77

Patch Update Guide
2.
View the MSOFTX3000 patch report using the Internet Explorer. Click Rollback Patch
Implementation to expand the Rollback Patch Implementation node until all the
details about patch rollback are displayed
3.
Check the result of the Rollback the XPTU patch operation. If the displayed result is
Success, it indicates the SOSM XPTU patch has been successfully rolled back.
----End
Issue 01 (2015-02-15)

Copyright
78

Patch Update Guide
Troubleshooting
3.1 What to Do If the Target Patch Versions Are

not Available for Selection?
Question
During patch installation, the target patch versions are not available in the Target patch
version drop-down list box. What should I do?
Answer
To identify the cause that results missing target patch versions, perform the following steps:
Step 1 Run the following command to check whether the patch packages of the target versions have
been uploaded to the OMU board.
LST PKG: PKGT=PATPKG;
Figure 1.1 Sample output of the LST PKG command
Issue 01 (2015-02-15)

Copyright
79

Patch Update Guide
Step 2 If the patch packages of the target versions are not uploaded to the OMU board, upload them
by referring to "1.4.3Uploading the MSOFTX3000 Patch Package".
----End
3.2 How to View and Save the Patch

Installation Report?
Question
How to view and save the patch installation report after patch installation is complete?
Answer
To view and save the patch installation report, perform the following steps:
Step 1 In the WebUI navigation interface as shown in 1.4.4 IStep 3Figure 1.1, click View Report to
view the patch installation report generated for the ME you have selected.
Only the most recent patch installation report is displayed.
Step 2 Click Save in the upper left corner of the Patch Report Detail page to save the patch
installation report to an *.html file on the local PC.
----End
3.3 How to Correct Internet Explorer Errors

During Patch Installation?
Question
What should I do if the following errors occur during the patch installation:
The Internet Explorer is closed abruptly.
The Internet Explorer does not respond for a long time.
An Internet Explorer window cannot be maximized after it is minimized.
The Internet Explorer changes to a white screen abruptly.
Answer
Close the Internet Explorer used to assess the WebUI. After three minutes, log in to WebUI
again and continue with the previous patch installation task.
Issue 01 (2015-02-15)

Copyright
80

Patch Update Guide
3.4 Why Fail to send command or Connect to

MML Server failed Is Displayed After the OMU
Is Restarted During Patch Installation or
Rollback?
Question
What should I do if Fail to send command or Connect to MML Server failed is displayed
after the OMU is restarted in patch installation or rollback?
Answer
If an MML command is sent to the OMU while OMU services are being restarted during
patch installation or rollback, Fail to send command or Connect to MML Server failed is
displayed. To clear the error message, wait until all the OMU services are restarted
successfully and then click Retry to repeat the operation.
3.5 Are There Any Limitations on the Patch

Rollback?
Question
Are there any limitations on the patch rollback?
Answer
Rollback is the reverse process of upgrade. Assume that the MSOFTX3000 is upgraded from
SPH001 to SPH002 by using the remote patch installation function. If rollback is required, the
remote patch installation function supports only the rollback from SPH002 to SPH001. Other
rollback paths are not supported.
3.6 Why WebUI Returns to the First Check Item

If Retry Is Clicked During Pre-Installation
Check?
Question
Is it normal if WebUI returns to the first pre-installation check item after Retry is clicked in
response to a warning generated during the pre-installation check or failure to pass the preinstallation check?
Answer
After you click Retry, the pre-patching check starts again. Therefore, it is normal for WebUI
to return to the first pre-installation check item.
Issue 01 (2015-02-15)

Copyright
81

Patch Update Guide
3.7 How to Set Remote Desktop Sharing on the

SOSM XPTU?
Question
How to set remote desktop sharing on the SOSM XPTU?
Answer
To set remote desktop sharing on the SOSM XPTU, perform the following steps:
Step 1 On the SOSM XPTU server, choose Start > Programs > Accessories > Communications >
NetMeeting. The NetMeeting dialog box is displayed, as shown in Step 2Figure 1.1.
Step 2 In the NetMeeting dialog box, choose Call > Automatically Accept Calls.
Figure 1.1 Choosing to automatically accept calls
Step 3 Choose Tools > Remote Desktop Sharing. The Remote Desktop Sharing Settings dialog
box is displayed, as shown in Figure 1.1. If Enable Remote Desktop Sharing on this
computer is selected, go to Step 6.
Issue 01 (2015-02-15)

Copyright
82

Patch Update Guide
Figure 1.1 Enabling remote desktop sharing
Step 4 Click Wizard. The Remote Desktop Sharing Wizard dialog box is displayed, as shown in
Figure 1.1. Click Next until you complete the setting.
Figure 1.1 Setting remote desktop sharing
Step 5 Click OK in the Remote Desktop Sharing Settings dialog box, as shown in Figure 1.1.
Then, exit the NetMeeting program,
Issue 01 (2015-02-15)

Copyright
83

Patch Update Guide
Figure 1.1 Completing the setting of remote desktop sharing
Step 6 Right-click
, and choose Activate Remote Desktop Sharing.
----End
3.8 How to Assign Permissions Required for

Patch Installation?
Question
If I do not want to perform patch operations (including downloading of the patch package) as
user admin, then I need to have at least the permission to run the G_1 command group
against the CGP. How do I obtain the permission?
Answer
To obtain the permission required to run the G_1 command group against the CGP, perform
the following steps:
Step 1 Log in to HUAWEI Operation & Maintenance System as admin user. Then, choose System >
Security to launch the Security Management interface.
Step 2 Click User in the navigation tree. A user list is displayed in the right pane.
Step 3 Right-click the user for whom you want to assign permissions, and choose Authorized
Operation from the shortcut menu. The Browse User Authorized Operation dialog box is
displayed, as shown in Figure 1.1.
Issue 01 (2015-02-15)

Copyright
84

Patch Update Guide
Figure 1.1 Browse User Authorized Operation dialog box
Step 4 In the Browse User Authorized Operation dialog box, click Add. The Add Operation
Authority dialog box is displayed, as shown in Figure 1.1. Then, specify the parameters in
the dialog box, and click OK. The Browse User Authorized Operation dialog box is
displayed again. At this time, click Close.
Figure 1.1 Add Operation Authority
Step 5 In the Security Management dialog box, right-click the user for whom you want to assign
permissions, and choose Authorized Directory from the shortcut menu. The Authorized
Directory dialog box is displayed, as shown in Figure 1.1.
Step 6 Specify the parameters in the Authorized Directory dialog box, and click OK.
Issue 01 (2015-02-15)

Copyright
85

Patch Update Guide
Figure 1.1 Authorized Directory dialog box
----End
3.9 What to do If Interruptions Occur During

Patch Installation?
Question
What should I do if any of the following cases occurs during patch installation:
In the pre-patching check phase, an error message is displayed, indicating that some of
the loaded patches are not running.
After the pre-patching check is completed, an interface is displayed, as shown in Figure
1.1.
Issue 01 (2015-02-15)

Copyright
86

Patch Update Guide
Figure 1.1 Pre-patching check interface
After View Report is clicked, the pre-patching check report is displayed. Double-clicking a
red row in the report displays the information marked in blue solid lines, as shown in Figure
1.2.
Figure 1.2 Information displayed when a red row is double-clicked
In the confirmation phase, an error message is displayed, indicating that patch status of
certain modules cannot be queried.
After patch installation is verified, an interface is displayed, as shown in Figure 1.3.
Figure 1.3 Patch installation verification interface
After View Report is clicked, the verification report is displayed. Double-clicking a red row
in the report displays the information marked in blue solid lines, as shown in Figure 1.4.
Issue 01 (2015-02-15)

Copyright
87

Patch Update Guide
Figure 1.4 Information displayed when a red row is double-clicked
Answer
Click Retry until the patch installation process resumes. If the patch installation process does
not resume after several retries, contact Huawei Technical support engineers.
3.10 What to Do If the "ALM-3807 Program

Check Failure Between OMU and TDM" Is
Generated?
Question
What should I do if the "ALM-3807 Program Check Failure Between OMU and TDM" is
generated?
Answer
If the version of the TDM daughter board programs is inconsistent with the version of the
program stored on the OMU, you need to reset the TDM daughter board to avoid ALM-3807
generation. Perform the following steps to reset the TDM daughter board:
Step 1 In the MML Command CGP window, run DSP DBRD: DBRDTYPE=TDM; to query the
TDM daughter board state.
Step 2 In the MML Command CGP window, run RST DBRD with Reset mode set to
SRST(Soft reset) to reset the TDM daughter board whose Daughter board state is Standby.
After about 2 minutes, the TDM daughter board resetting is complete.
state of the TDM daughter board that has been reset.
If Daughter board state is Standby, and BootROM status, Flash status, CPLD status and FPGA
status are Normal, the TDM daughter board resetting is successful.
If Daughter board state is NULL, wait 2 minutes and query the daughter board again. If Daughter
board state remains NULL, contact Huawei technical support engineers.
Issue 01 (2015-02-15)

Copyright
88

Patch Update Guide
Step 4 In the MML Command CGP window, run SWP DBRD to perform a switchover. After 30
seconds, the switchover between the active and standby TDM boards is complete.
state of the original active TDM daughter board.
If Daughter board state is Standby, and BootROM status, Flash status, CPLD status and FPGA
status are Normal, the TDM daughter board switchover is successful.
If Daughter board state is Active, contact Huawei technical support engineers.
Step 6 Repeat Step 1 to Step 3 to reset the TDM daughter board whose Daughter board state is
Standby.
Step 7 Repeat Step 1 to Step 6 to reset all TDM daughter boards in the system.
----End
3.11 Hardware status indicators are steady in

gray on the device panel of client
Question
What should I do if the hardware status indicators are steady in gray on the device panel of
client?
Answer
The firmware of the SMM board can be upgraded only after the SMM board is reset. After the
firmware is upgraded, this problem can be resolved. Perform the following steps to reset the
SMM board:
Step 1 In the MML Command - CGP window on the OMU client, run DSP CPATCH: MEID=0;
to check whether the current cold patch number is later than SPC515.
Yes => End
No => Step 2
Step 2 In the MML Command - CGP window on the OMU client, run DSP BRD to query the
Step 3 In the MML Command - CGP window on the OMU client, run RST BRD to reset those
SMM boards whose Availability state is Standby. The reset is complete about 10 minutes
later.
Issue 01 (2015-02-15)

Copyright
89

Patch Update Guide
Step 5 In the MML Command - CGP window on the OMU client, run SWP BRD to switch over
the SMM board whose Availability state is Active. The switchover is complete about 10
seconds later.
If Availability state in the command output is Fault or Active, query the board status 5 minutes later. If
Availability state remains as Fault or Active, contact Huawei technical support.
Step 7 In the MML Command - CGP window on the OMU client, run CHK FW for the CGP with
Show compatible record set to Yes to query the version of the firmware on reset SMM
boards in slots 14 and 15. Check whether Run version of SMMD_APP or SMME_APP is the
same as Configured version.
Step 8 Repeat Step 2 to Step 7 to reset all SMM boards.

----End
3.12 "Load the cold patch for OMU fail: Patch

Install fail!" Is Displayed During Patch
Installation
Symptom
"Load the cold patch for OMU fail: Patch Install fail!" is displayed during patch installation
on the OMU if the following conditions are true:
The CGP is upgraded to V100R005C01SPC500 or later from V100R005C00SPC600 or

earlier.
Users log in to the OMU board through PuTTY using floating IP addresses of the OMU
and run the following command:
eval "'getOMUName'"
ssh -q $REMOTE_HOST
"grep "monitor_active_db_upg.sh" /etc/crontab"
The command output is as follows:

* * * * * root . /etc/profile;
/opt/HUAWEI/cgp/workshop/omu/upgtools/monitor_active_db_upg.sh >/dev/null
2>&1.
Probable Cause
The database monitor scripts remained in the system sometimes causes failures in
installing database patches.
Issue 01 (2015-02-15)

Copyright
90

Patch Update Guide
Handling Procedure
Step 1 Log in to the OMU board through PuTTY using a floating IP address of the OMU and run the
following command:
eval "'getOMUName'"
sed -i '/\<monitor_active_db_upg.sh\>/d' /etc/crontab
rccron restart
ssh -q $REMOTE_HOST "sed -i '/\<monitor_active_db_upg.sh\>/d' /etc/crontab; rccron
restart"
Check whether command execution succeeds.
Yes => Step 2
No => Step 3
Step 2 Click Retry on the WebUI to continue patch installation. Check whether patch installation
succeeds.
Yes => End
No => Step 3
Step 3 Contact Huawei technical support engineers.

----End
3.13 Determining Whether a Board Runs a

Compact or Standard OS
Question
How to determine whether a board runs a compact or standard OS?
Answer
To determine whether a board runs a compact or standard OS, perform the following steps:
Step 1 Log in to the OMU client as user admin.
Step 2 In the MML Command CGP window, run DSP BRDSFT. Check whether the subrack
number and slot number for the target board are contained in the command output.
If the subrack number and slot number for the board are contained in the command output, the
board runs a standard OS. If the subrack number and slot number for the board are not
contained in the command output, the board runs a compact OS.
----End
Issue 01 (2015-02-15)

Copyright
91

Patch Update Guide
A Acronyms and Abbreviations
Acronyms and Abbreviations
CGP
Carrier Grade Platform
CRC
Cyclic Redundancy Check
LMT
Local Maintenance Terminal
MML
Man-Machine Language
OMU
Operation and Maintenance Unit
WebUI
Web User Interface
XPTU
X Protocol Transfer Unit
Issue 01 (2015-02-15)

Copyright
92

Msoftx3000 v200r009c02sph131 Patch Update Guide

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Msoftx3000 v200r009c02sph131 Patch Update Guide

Încărcat de

Drepturi de autor:

Formate disponibile

HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Patch Update Guide

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

HUAWEI MSOFTX3000 Mobile SoftSwitch Center

About This Document

About This Document

Technical support engineers

This issue is the first official release.

Huawei Proprietary and Confidential

HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Huawei Proprietary and Confidential

HUAWEI MSOFTX3000 Mobile SoftSwitch Center

1.4.5 Correcting Patch Installation Errors.......................................................................................................56

A Acronyms and Abbreviations.......................................................91

Huawei Proprietary and Confidential

HUAWEI MSOFTX3000 Mobile SoftSwitch Center

This operation guide describes how to install MSOFTX3000 V200R009C02SPH131 locally

1.1.1 Checking Whether Lawful Interception

In the V200R009C02SPH118 patch, measurement objects related to the following

Traffic for BICC Outgoing Office in X3 channel

Traffic for ISUP Outgoing Office in X3 Channel

Log in to Huawei Operation & Maintenance System.

Huawei Proprietary and Confidential

HUAWEI MSOFTX3000 Mobile SoftSwitch Center

If Operation succeeded is displayed in the output, go to section 1.1.2"Checking the

If User authentication failed is displayed in the output, go to Step 2.

Figure 1.1 Security alert

Step 3 Enter the password of user tt\admin to log in to the WebUI.

Huawei Proprietary and Confidential

HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Figure 1.1 Choosing Performance Management System

Figure 1.1 illustrates a common measurement task.

Figure 1.2 illustrates a monitoring task.

Huawei Proprietary and Confidential

HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Figure 1.2 Monitoring task

Figure 1.1 illustrates a common measurement task.

Huawei Proprietary and Confidential

HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Figure 1.2 illustrates a monitoring task.

No: Go to 1.1.2"Checking the Operating Environment of the Internet Explorer".

Huawei Proprietary and Confidential

HUAWEI MSOFTX3000 Mobile SoftSwitch Center

1.1.2 Checking the Operating Environment of the

Figure 2.1 Checking the version of the Internet Explorer

Start Internet Explorer.

Choose Tools > Manage Add-ons.

Huawei Proprietary and Confidential

HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Figure 4.1 Disabling third-party add-ons in Internet Explorer 6.0 or 7.0

In Internet Explorer 7.0, proceed as follows:

Start Internet Explorer.

Choose Tools > Manage Add-ons > Enable or Disable Add-ons.

In Internet Explorer 8.0, proceed as follows:

Start Internet Explorer.

Choose Tools > Manage Add-ons.

Select add-ons whose type is Toolbar, and click Disable.

Huawei Proprietary and Confidential

HUAWEI MSOFTX3000 Mobile SoftSwitch Center