Msoftx3000 v200r009c02sph131 Patch Update Guide

MSOFTX3000 V200R008C03SPH203 Patch Operation Guide

About This DocumentHUAWEI MSOFTX3000 Mobile SoftSwitch Center Patch Update Guide

HUAWEI MSOFTX3000 Mobile SoftSwitch CenterV200R009C02SPH131Patch Update Guide

Issue01

Date2015-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:[email protected]

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 engineersChange HistoryIssueRelease DateDescription

012015-02-15This issue is the first official release.

Contents

iiAbout This Document

11 Patch Installation

11.1 Precautions

11.1.1 Checking Whether Lawful Interception Measurement Tasks Exist

61.1.2 Checking the Operating Environment of the Internet Explorer

91.1.3 Disabling Relevant Services

101.1.4 Operations Prohibited During Patch Installation

111.1.5 Impact of Patch Installation

111.2 Installation Process

111.2.1 Pre-installation Check

121.2.2 Install Patch

131.3 Preparations

131.3.1 Confirming the Version Configuration Information

141.3.2 Checking the Compatibility of the Patch Package

151.3.3 Obtaining the Patch Package

161.3.4 Checking the Integrity of the Downloaded Software Packages

171.3.5 Checking the M2000 Common Version and Mediation Version

181.3.6 Checking the Baseline Patch Versions of the Target MEs

201.3.7 Checking the OMU Board Status

201.3.8 Checking Whether Reserved MML Command Options Put into Use in the Patch Are Set to Default Values

221.3.9 Checking Whether the Software Parameters Added in the Patch Are Set to the Default Values

371.3.10 Performing a CRC

371.3.11 Performing Pre-Patching Check

421.3.12 Checking the Connection to the SOSM XPTU by Using NetMeeting (Optional)

431.3.13 Updating SFU on the SOSM XPTU Server (Optional)

441.3.14 Checking the Impact of the Mediation Version Installation on the NMS

451.4 Installing Patches

451.4.1 Loading the M2000 Mediation Version

451.4.2 Uploading the CGP Patch Package

461.4.3 Uploading the MSOFTX3000 Patch Package

471.4.4 Installing the Patch Using the WebUI

561.4.5 Correcting Patch Installation Errors

591.4.6 Loading the Client Patch

601.4.7 Loading the XPTU Patch

631.4.8 Configuring Data

641.5 Verifying Patch Installation

641.5.1 Verifying the Patch Version

651.5.2 Verifying the Basic Functions

661.5.3 Verifying Patch Functions

672 Patch Rollback

672.1 Precautions

672.2 Rolling Back Patches

762.3 Verifying Patch Rollback

783 Troubleshooting

783.1 What to Do If the Target Patch Versions Are not Available for Selection?

793.2 How to View and Save the Patch Installation Report?

793.3 How to Correct Internet Explorer Errors During Patch Installation?

803.4 Why Fail to send command or Connect to MML Server failed Is Displayed After the OMU Is Restarted During Patch Installation or Rollback?

803.5 Are There Any Limitations on the Patch Rollback?

803.6 Why WebUI Returns to the First Check Item If Retry Is Clicked During Pre-Installation Check?

813.7 How to Set Remote Desktop Sharing on the SOSM XPTU?

833.8 How to Assign Permissions Required for Patch Installation?

853.9 What to do If Interruptions Occur During Patch Installation?

873.10 What to Do If the "ALM-3807 Program Check Failure Between OMU and TDM" Is Generated?

883.11 Hardware status indicators are steady in gray on the device panel of client

893.12 "Load the cold patch for OMU fail: Patch Install fail!" Is Displayed During Patch Installation

903.13 Determining Whether a Board Runs a Compact or Standard OS

91A Acronyms and Abbreviations

1 Patch Installation1.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. 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*/ 2013-10-21 02:46:38+00:00

O&M #57

%%LST TTSYS:;%%

RETCODE = 0 Operation succeeded 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*/ 2013-10-21 02:47:03+00:00

O&M #60

%%LST TTSYS:;%%

RETCODE = 483005 User authentication failed--- END

Step 2 Start Internet Explorer, type http://, 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-2.

Figure 1-2 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-3 illustrates a common measurement task.Figure 1-3 Common measurement task

Figure 1-4 illustrates a monitoring task.Figure 1-4 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-5 illustrates a common measurement task.

Figure 1-5 Common measurement task

Figure 1-6 illustrates a monitoring task.Figure 1-6 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

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 9 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 1-7 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 10 Exit the applications except WebUI and HUAWEI Operation & Maintenance System.

Step 11 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 1-8.

4. Click the add-ons whose type is Toolbar, and select Disable in the Settings area.Figure 1-8 Disabling third-party add-ons in Internet Explorer 6.0 or 7.0

In Internet Explorer 7.0, proceed as follows:5. Start Internet Explorer.6. Choose Tools > Manage Add-ons > Enable or Disable Add-ons.

7. 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 1-8.

8. Click the add-ons whose type is Toolbar, and select Disable in the Settings area.In Internet Explorer 8.0, proceed as follows:9. Start Internet Explorer.10. Choose Tools > Manage Add-ons.

11. In the Manage Add-ons dialog box, select Currently loaded add-ons from the Show drop-down list box, as shown in Figure 1-9.

12. Select add-ons whose type is Toolbar, and click Disable.Figure 1-9 Disabling third-party add-ons in Internet Explorer 8.0

Step 12 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 1-10.

Figure 1-10 Internet Options

----End1.1.3 Disabling Relevant Services

Before installing MSOFTX3000 V200R009C02SPH131, disable the relevant services as follows:Step 13 Choose Start > Settings > Control Panel > Administrative Tools > Services.

Step 14 Check whether Check Point SecuRemote Service and Check Point SecuRemote WatchDog are displayed in the service list.

Yes => Step 3 No => End

Step 15 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 4Step 16 Set Startup type of Check Point SecuRemote Service and Check Point SecuRemote WatchDog to Disabled. Then, restart your PC.

Figure 1-11 Disabling Check Point SecuRemote Service

----End1.1.4 Operations Prohibited During Patch Installation

Table 1-1 lists the commands and operations prohibited during patch installation.

Table 1-1 Commands and operations prohibited during patch installationCommandOperation

ADD ME

RMV ME

BKP SYS

EXP MES

IMP MES LOD PKG

RMV PKGModifying the login password of WebUI on the MSOFTX3000 MML command interface of the HUAWEI Operation & Maintenance System (also called OMU client)

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 Process1.2.1 Pre-installation CheckTable 1-2 Preparation checklist

No.Check ItemCheck TimeDurationReference

1Status of relevant portsOne week before patch installation30 minutesContact 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.

2Version configuration informationOne week before patch installation30 minutesSee1.3.1 "Confirming the Version Configuration Information"

3Compatibility of the patch packages to be installedOne week before patch installation30 minutesSee 1.3.2 "Checking the Compatibility of the Patch Package."

4MSOFTX3000 V200R009C02SPH131 patch packageOne week before patch installation120 minutesSee 1.3.3 "Obtaining the Patch Package."

5Checking the Integrity of the Downloaded Software PackagesOne week before patch installation5 minutesSee 1.3.4

REF _Ref328060732 \h Checking the Integrity of the Downloaded Software Packages

6M2000 common version and mediation versionOne week before patch installation30 minutesSee 1.3.5

REF _Ref328837525 \h Checking the M2000 Common Version and Mediation Version

7Baseline patch versions of the target MEsOne day before patch installation10 minutesSee 1.3.6

REF _Ref254617228 \h Checking the Baseline Patch Versions of the Target MEs

8Status of OMU boardsOne day before patch installation10 minutesSee 1.3.7 "Checking the OMU Board Status."

9Reserved MML Command OptionsOne day before patch installation10 minutesSee 1.3.8 "Checking Whether Reserved MML Command Options Put into Use in the Patch Are Set to Default Values"

10Software Parameters One day before patch installation10 minutesSee 1.3.9 "Checking Whether the Software Parameters Added in the Patch Are Set to the Default Values"

11Data consistency between the host and the OMUOne day before patch installation15 minutesSee 1.3.10 "Performing a CRC"

12Performing Pre-Patching CheckOne day before patch installation10 minutesSee 1.3.11 "Performing Pre-Patching Check"

1.2.2 Install Patch

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. 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.Table 1-3 Schedule for patch installation

OperationRecommended Start TimeDurationReference

Loading the M2000 mediation version00:00601.4.1 "Loading the M2000 Mediation Version"

Upload the CGP patch package01:00101.4.2 "Uploading the CGP Patch Package"

Upload the MSOFTX3000 patch package01:10101.4.3 "Uploading the MSOFTX3000 Patch Package"

Installing the patch using the WebUI tool01:20301.4.4 "Installing the Patch Using the WebUI"

Loading the OMU client patch01:50101.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 InformationTo confirm the version configuration information, perform the following steps:Step 17 Log in to HUAWEI Operation & Maintenance System, and run LST ME on the CGP MML command interface.

Figure 1-12 Output of the LST ME command

Step 18 Check whether the output of the LST ME command complies with Table 1-4. 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.

Table 1-4 Version configuration information

MECompatible Version

CGPV100R006C02SPC500

MSOFTX3000V200R009C02SPC100

----End1.3.2 Checking the Compatibility of the Patch Package

Table 1-5 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.

Table 1-5 Compatible patch packages to be installed

SNMECompatible Patch Package

1CGPV100R006C02SPC527

2MSOFTX3000V200R009C02SPH131

3iGWBV500R006C02SPC211

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 19 Log in to http://support.huawei.com using a valid username and password.

Step 20 Choose Software Center > Version Software > Core Network Product Line > WCDMA-CS > WCDMA MSOFTX3000 > MSOFTX3000 > MSOFTX3000 V200R009 > MSOFTX3000 V200R009C02SPH131.

Step 21 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.docStep 22 Download the MSOFTX3000 V200R009C02SPH131_Software (version software). Then, extract the patch package from the version software.

Step 23 Check whether the information about patch package complies with Table 1-6. If no, download the correct patch package.

Table 1-6 Information about patch packageFile NameSize (Byte)

MSOFTX3000 V200R009C02SPH131 Patch.zip1,612,866,699

MSOFTX3000 V200R009C02SPH131_iManager Adapter.zip287,034,914

MSOFTX3000V200R009C02SPH131_XPTU_SOSM.exe3,701,106

Step 24 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.

Table 1-7 describes the patch files included in the patch package.

Table 1-7 List of patch files

MEPatch FolderPatch FileDescription

CGPCGP_V100R006C02SPC527CGP_V100R006C02SPC527.tarCGP patch package, including the CGP hot patch and cold patch

CGP_V100R006C02SPC527.sgnDigital signature file, used for remote patch installation

upgradecfg.xmlProcedural file for the network management system, used for remote patch installation

upgradecfg.sgnDigital signature file, used for remote patch installation

Vercfg.xmlVersion description file, used for remote patch installation

vercfg.sgnDigital signature file, used for remote patch installation

MSOFTX3000MSOFTX_V200R009C02SPH131MSOFTX_V200R009C02SPH131.tarMSOFTX3000 patch package, including the MSOFTX3000 hot patch and cold patch

MSOFTX_V200R009C02SPH131.sgnDigital signature file, used for remote patch installation

upgradecfg.xmlProcedural file for the network management system, used for remote patch installation

upgradecfg.sgnDigital signature file, used for remote patch installation

Vercfg.xmlVersion description file, used for remote patch installation

vercfg.sgnDigital signature file, used for remote patch installation

----End1.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 25 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 26 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.----End1.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 27 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 28 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-13.

Figure 1-13 Checking the M2000 common version

Step 29 Check whether the M2000 common version is correct according to Table 1-8. 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.

Table 1-8 M2000 common versionItemVersion

M2000 common versionV200R012C00SPC200

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 Table 1-8.Step 30 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-14.

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

Figure 1-14 Checking the M2000 mediation versions

Step 31 Check whether the M2000 mediation version, which is compatible with MSOFTX3000V200R009C02SPH131, has been installed according to Table 1-9. 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.

Table 1-9 M2000 mediation version compatible with MSOFTX3000V200R009C02SPH131ItemVersion

M2000 mediation version of the CGPiManagerM2000_CGPOMU_MATCH_ENG_V100R006C02SPC527

M2000 mediation version of the MSOFTX3000iManagerM2000_MSOFTX3000_MATCH_ENG_V200R012C02SPC074

----End1.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:

Step 32 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 Table 1-10.

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.

Table 1-10 Cold patch versions

MEDisplayed Patch Version

CGPSPC527 or earlier version

MSOFTX3000SPC131 or earlier version

Step 33 Run DSP PATCH on the CGP MML command interface. Then, check whether the displayed hot patch versions of CGP and MSOFTX3000 comply with Table 1-11.

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.

Table 1-11 Hot patch versions

MEDisplayed Patch Version

CGPSPH527 or earlier version

MSOFTX3000SPH131 or earlier version

Step 34 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 35 The patch version meets the requirement. In such a case, continue with the next check item.

----End1.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 36 Log in to HUAWEI Operation & Maintenance System, and run DSP OMU on the CGP MML command interface.

Step 37 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-15, it indicates that both active and standby OMU boards are operational.

Figure 1-15 Sample output of the DSP OMU command

----End1.3.8 Checking Whether Reserved MML Command Options Put into Use in the Patch Are Set to Default Values

Step 38 Log in to HUAWEI Operation & Maintenance System, and run EXP MML in the MML Command CGP window to export the configuration data files.

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 39 Open the configuration data files and check whether the reserved MML command options listed in Table 1-12 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 Table 1-12, the MSOFTX3000 is not configuration with the related data and the related reserved option is automatically set to the default value.

Table 1-12 MML command options put into usePatch VersionMML CommandParameterOptionDefault Value

SPH131ADD OFCBOFFICEEXTRAPARA2SVR290

SPH128ADD OFCBOFFICEEXTRAPARA2SVR250

SPH127ADD RNCHOPARARSVBIT301

SPH126ADD SIPTGESFPARA4SRV160



SPH110ADD CLDPREANACLISRVCATSERVICE410

ADD CLDPREANACLISRVCATSERVICE310

SPH107ADD RNCCAPABILITYRSVBIT140

ADD CASTGSVRCTRLSVR120

ADD CASTGSVRCTRLSVR130


ADD CALLPRICHKNUMPRESERVE20


ADD SIPTGESFPARA2SRV290

ADD OFCBOFFICEEXTRAPARA2SVR60


ADD SIPTGESFPARA2SRV310

----End1.3.9 Checking Whether the Software Parameters Added in the Patch Are Set to the Default ValuesLog 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.Table 1-13 Software Parameters Added in the PatchPatch VersionSoftware Parameters

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

SPH130N/A

SPH129Bit 14 of P935 (*X** **** **** ****): The default value is 1.

Bit 12 of P420 (***X **** **** ****): The default value is 0.


Bit 9 of P1516 (**** **X* **** ****): The default value is 1.Bits 13-12 of P391 (**XX **** **** ****): The default value is 11.



Bit 15 of P1516 (X*** **** **** ****): The default value is 1.Bit 3 of P846 (**** **** **** X***): The default value is 1.Bit 15 of P1156 (X*** **** **** ****): The default value is 1.


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.





Bit 7 of P1314 (**** **** X*** ****): The default value is 1.


SPH127Bit 10 of P1219 (**** *X** **** ****): The default value is 1.






Bit 11 of P1508 (**** X*** **** ****): The default value is 1.





Bit 0 of P680 (**** **** **** ***X): The default value is 0.Bit 2 of P418 (**** **** **** *X**): The default value is 0.

Bits 6-4 of P1156 (**** **** *XXX ****): The default value is 111.



SPH126Bit 7 of P1220 (**** **** X*** ****): The default value is 1.







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.






Bit 3 of P1512 (**** **** **** X***): The default value is 1.





SPH125Bit 5 of P960 (**** **** **X* ****): The default value is 1.

















SPH124Bit 13 of P1012 (**X* **** **** ****): The default value is 1.


Bits 2-0 of P549 (**** **** **** *XXX): The default value is 111.



Bit 0 of P893 (**** **** **** ***X): The default value is 1.Bit 14 of P1012 (*X** **** **** ****): The default value is 1.




SPH123Bit 2 of P953 (**** **** **** *X**): The default value is 1.










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.


SPH122Bit 8 of P678 (**** ***X **** ****): The default value is 0.


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









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









Bit 8 of P1014 (**** ***X **** ****): The default value is 1.Bit 0 of P955 (**** **** **** ***X): The default value is 1.

SPH121Bit 6 of P954 (**** **** *X** ****): The default value is 1.


Bit 10 of P1508 (**** *X** **** ****): The default value is 1.Bit 4 of P954 (**** **** ***X ****): The default value is 1.




Bit 1 of P419 (**** **** **** **X*): The default value is 0.

Bits 8-6 of P39 (**** ***X XX** ****): The default value is 111.






SPH120Bit 12 of P1014 (***X **** **** ****): The default value is 1.

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







Bit 11 of P1220 (**** X*** **** ****): The default value is 1.Bit 0 of P419 (**** **** **** ***X): The default value is 0.Bit 3 of P678 (**** **** **** X***): The default value is 0.













































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











SPH117Bit 15 of P1521 (X*** **** **** ****): The default value is 1.















































SPH114N/A

SPH113Bit 14 of P1219 (*X** **** **** ****): The default value is 1.


































Bits 7-6 of P845 (**** **** XX** ****): The default value is 11.





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


Bit 3 of P1507 (**** **** **** X***): The default value is 1.Bit 4 of P1507 (**** **** ***X ****): The default value is 1.


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









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









SPH108Bit 2 of P1219 (**** **** **** *X**): The default value is 1.




























SPH106Bits 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.Bit 10 of P675 (**** *X** **** ****): The default value is 0.

Bit 11 of P675 (**** X*** **** ****): The default value is 0.Bit 11 of P462 (**** X*** **** ****): The default value is 1.










Bit 14 of P947 (*X** **** **** ****): The default value is 1.Bit 2 of P675 (**** **** **** *X**): The default value is 0.

Bit 6 of P1102 (**** **** *X** ****): The default value is 1.Bit 3 of P1314 (**** **** **** X***): The default value is 1.Bit 2 of P1314 (**** **** **** *X**): The default value is 1.



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
























SPH103Bit 9 of P947 (**** **X* **** ****): The default value is 1.

Bits 15-0 of P276 (XXXX XXXX XXXX XXXX): The default value is 0xFFFF.




SPH102Bit 0 of P1506 (**** **** **** ***X): The default value is 1.

SPH101Bit 5 of P946 (**** **** **X* ****): The default value is 1.


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 40 Log in to HUAWEI Operation & Maintenance System, and run FMT on both CGP and MSOFTX3000 MML command interfaces to format all the data.

Step 41 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 42 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.

----End1.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 43 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-16.

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.Figure 1-16 WebUI login dialog box

Step 44 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 45 In the Huawei Operation & Maintenance System window displayed, click Patch & Upgrade Tool, as shown in Figure 1-17.

Figure 1-17 Patch & Upgrade Tool

Step 46 In the Patch navigation tree, click Patch Check, as shown in Figure 1-18.

Figure 1-18 Patch Check icon

Step 47 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-19.

Figure 1-19 Select Check ME tab page

If no CGP patch package is uploaded, the target patch version is displayed empty and the pre-patching 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 48 Click the Pre-Patching Check icon above the table. The Confirm dialog box is displayed, as shown in Figure 1-20.

Figure 1-20 Confirm dialog box

Step 49 Click OK. The Pre-Patching Check Control tab page is displayed, as shown inFigure 1-21.Figure 1-21 Pre-Patching Check tab page

Step 50 After the check is complete, the Question dialog box is displayed, as shown in Figure 1-22. 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-23.Figure 1-22 Question dialog box

Figure 1-23 Check completion notification

Step 51 Click View Report from the Patch navigation tree, as shown in Figure 1-24.

Figure 1-24 View Report icon

Step 52 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-25.

Figure 1-25 Select Patch Report ME tab page

Step 53 Click View ME report to open the pre-patching check report.

Step 54 Check whether all MEs pass the pre-patching check, as shown in Figure 1-26 (This document uses CGP Pre-Patching Check Report as an example).

Figure 1-26 Basic information in the pre-patching check report

Yes: No further action is required.

No: Go to Step 13.

Step 55 Click the operation that is marked as Warning or Failed to expand the operation information, as shown in Figure 1-27.

Figure 1-27 Operation details

Step 56 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 57 Repeat the pre-patching check from Step 4.----End1.3.12 Checking the Connection to the SOSM XPTU by Using NetMeeting (Optional)

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 58 On the PC that runs the M2000 client, choose Start > Programs > Accessories > Communications > NetMeeting. Step 59 Choose Call > New Call. The Place a Call dialog box is displayed, as shown in Figure 1-28.Figure 1-28 Making a call

Step 60 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 61 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)

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 62 Obtain SFU.zip in the patch package MSOFTX3000 V200R009C02SPH131_Software.zip.

Step 63 Follow the steps in the MSOFTX3000 V200R009C02 Guide to Updating SFU obtained from the SFU.zip to upgrade the SFU.----End1.3.14 Checking the Impact of the Mediation Version Installation on the NMSTo 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-29 and Figure 1-30. Figure 1-29 Format of a measurement object before the patch mediation installation

Figure 1-30 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----End1.4 Installing Patches1.4.1 Loading the M2000 Mediation Version

Step 64 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.

----End1.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 65 Log in to HUAWEI Operation & Maintenance System as user admin. Then, choose Maintenance > File Transfer Service to launch the File Transfer Service interface.

Step 66 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.Figure 1-31 Loading the CGP patch package

----End1.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 67 Log in to HUAWEI Operation & Maintenance System as user admin. Then, choose Maintenance > File Transfer Service to launch the File Transfer Service interface.

Step 68 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.----End1.4.4 Installing the Patch Using the WebUIThe 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 69 Start the Internet Explorer, type http://, 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-32, may be displayed prior to the login dialog box. Click Yes to switch to the login dialog box.

Figure 1-32 Security alert

Step 70 In the navigation interface of the WebUI shown in Figure 1-33, click Patch & Upgrade Tool.Figure 1-33 Navigation interface of the WebUI

Step 71 In the Welcome interface shown in Figure 1-34, click Patch to switch to the Select Patch ME page.

Figure 1-34 Launching the patch installation interface

Step 72 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.

Figure 1-35 Selecting the desired MEs for patch installation

Step 73 Click Patch in the upper left corner of the Select Patch ME page, as shown in Figure 1-36. The Confirm dialog box is displayed, asking whether to continue with the patch installation.

Figure 1-36 Confirming whether to install the patch

Step 74 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-37.

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-38. This tab page provides information about the step being performed, current progress, and overall progress.Figure 1-37 Performing the pre-installation check

Figure 1-38 Viewing the details about patch installation on a certain ME

Step 75 When the pre-installation check is complete, the WebUI displays "Patch prepare complete. Please click Continue or Rollback", as shown in Figure 1-39. Click Continue to move on to the patch installation phase.

Figure 1-39 Pre-installation check completed

Step 76 When the patch installation is complete, the WebUI displays "All ME patch implementation complete. Please click Continue or Rollback", as shown in Figure 1-40. Click Continue, to move on to the patch confirmation phase.

Figure 1-40 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 77 When the patch confirmation phase is complete, the WebUI displays "All the MEs are successfully upgraded. Please click Continue", as shown in Figure 1-41. Click Continue, to end the patch installation.

Figure 1-41 Patch confirmation completed

Step 78 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-42. Click OK.

Figure 1-42 Patch installation completed

Step 79 If required, obtain the patch installation report.

1. Switch to the WebUI navigation interface, as shown in Figure 1-34. 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 80 Run FMT on the CGP MML command interface to format all the CGP data.

Step 81 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 14Step 82 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 83 Run FMT on the MSOFTX3000 MML command interface to format all the MSOFTX3000 data.

Step 84 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 17Step 85 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 86 Run FMT on the IGWB MML command interface to format all the IGWB data.

Step 87 Run STR CRC on the IGWB MML command interface to check whether data is consistent between the OMU board and service processing boards.

Yes => Step 21 No => Step 20Step 88 Run SND CRCERR on the IGWB MML command interface to synchronize data from the OMU board to service processing boards. Then, repeat Step 19.

Step 89 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 23Step 90 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 91 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. 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. In the MML Command - CGP window on the OMU client, run DSP BRD to query the 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. In the MML Command - CGP window on the OMU client, run DSP BRD to query the status of the SMM board after the switchover.

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.

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

7. Repeat 1 to 6 till all SMM boards are reset.

----End1.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-43.

Figure 1-43 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 92 Click Detail in the Detail column of the corresponding ME. The Patch Detail page similar to Figure 1-44 is displayed.

Figure 1-44 Viewing the Patch Detail page

Step 93 Click View Report. A patch installation report similar to Figure 1-45 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-45 Viewing the CGP patch installation report

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 94 Perform an appropriate operation according to the error correcting result. If the error is corrected, click Retry in the Patch Detail page shown in Figure 1-44 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 Figure 1-44. If the error affects the patch installation, click Rollback in the Patch Detail page shown in Figure 1-44 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.----End1.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 95 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 96 Check whether the prompt shown in Figure 1-46 is displayed.

Yes => Step 3 No => End

Figure 1-46 Prompt for OMU client patch update

Step 97 Click Yes. The system automatically updates the OMU client patch, as shown in Figure 1-47.

Figure 1-47 Updating the OMU client patch

Step 98 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.----End1.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 99 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.Step 100 Run the XPTU patch file, for example, Double-click MSOFTX3000VxxxRxxxCxxSPHxxx_XPTU_SOSM.exe. The dialog box as shown in Figure 1-48 is displayed.Figure 1-48 Starting the XPTU patch tool

Step 101 Click Loading. The window as shown in Figure 1-49 is displayed.Figure 1-49 Preparing for loading of the XPTU patch

Step 102 Click Continue. The system loads the XPTU patch.Step 103 If the loading of the patch is successful, a dialog box as shown Figure 1-50 is displayed. Click Close.Figure 1-50 Loading of the XPTU patch completed

----End1.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 V200R009C02SPH112This section describes how to configure the configuration options introduced to MSOFTX3000 V200R009C02SPH112.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 wi

Msoftx3000 v200r009c02sph131 Patch Update Guide

Documents

patch package

install patch

huawei trademarks

impact of patch installation

baseline patch versions

copyright huawei technologies

installation process

preinstallation check