About This DocumentBSC6900 V900R012C01 Upgrade Guide

BSC6900V900R012C01Upgrade Guide

Issue02

Date2010-07-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2009. 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

About This DocumentAuthor

Prepared byXu QiangDate2010-02-05

Approved byFu Xuedong, Li Guangfeng, Wu Jinkun, Wei Lei, Zhang Yabin, Jiang QiuxiaDate2010-02-08

Tested byMiao Jiongkai, Zhang MinDate2010-3-15

Issued byDong QingyangDate2010-07-30

OrganizationChapterDescription

1

REF _Ref261253139 \h Reading Before UpgradeDescribes the upgrade requirements for this version, compared with the earlier versions.

2

REF _Ref121803041 \h Upgrade ProcessDescribes the process of upgrading the earlier version to this version.

3

REF _Ref219299703 \h Preparations for UpgradeDescribes the preparations that need to be made before the upgrade.

4

REF _Ref261253176 \h Upgrade OperationsDescribes the procedures of upgrade operations.

5

REF _Ref238620167 \h Post-Upgrade VerificationDescribes how to verify the upgrade.

6

REF _Ref261253207 \h Version RollbackDescribes the process of version rollback in the case of upgrade failure.

HistoryIssueDescriptionDatePrepared byApproved by

02Second issue2010-07-30 Xu QiangDong Qingyang

01First issue2010-06-21 Xu QiangDong Qingyang

Changes in Issue 02

TypeDescription

ModificationThe operation steps of starting the upgrade client through the M2000 are optimized. For details, see section 4.1.1 "Starting the Upgrade Client Through the M2000."

AdditionThe following description is added:In the case of upgrade from BSC6810V200R011C00SPC100 or its patch, you need to set the RNC as an FTP server on the M2000 when uploading the installation package through the M2000 to the NE. For details, see 4.1.1 Step 2.

AdditionThe following description is added:In the case of upgrade from the V900R012C01SPC200 to the V900R012C01SPH202, you need to turn off the switch of the blind detection function if the switch is turned on before the upgrade, to ensure that the BSC6900 functions after the upgrade are the same as those before the upgrade. For details, see section 4.5 "Post-Upgrade Special Processing(Only for BSC6900 UO or GU Mode)."

Contents

1-11 Reading Before Upgrade

1-11.1 Choosing an Upgrade Guide

1-11.2 Version Requirements for Upgrade

1-21.3 Impacts of the Upgrade on the Existing System

1-21.4 Notes and Cautions for Upgrade

1-51.5 Terms

2-12 Upgrade Process

3-13 Preparations for Upgrade

3-33.1 Installing the M2000 Adapation Layer

3-33.2 Performing the NE Health Check

3-33.2.1 Creating a Task for Checking the NE Health

3-43.2.2 Checking the Reports

3-53.3 Starting the NE Transfer Tool

3-53.4 Preparing Files for the Upgrade

4-14 Upgrade Operations

4-14.1 Starting the Upgrade Client

4-24.1.1 Starting the Upgrade Client Through the M2000

4-44.1.2 Starting the Upgrade Client Through the Client

4-54.2 Configuring the Basic Information About the Upgrade

4-84.3 Performing Pre-Upgrade

4-94.4 Performing Upgrade

4-124.5 Post-Upgrade Special Processing(Only for BSC6900 UO or GU Mode)

5-15 Post-Upgrade Verification

5-15.1 Post-Upgrade NE Health Check

5-15.1.1 Performing the Post-Ugrade NE Health Check

5-15.1.2 Comparing the Report of the Post-Upgrade Health Check with That of the Pre-Upgrade Health Check

5-15.2 Post-Upgrade Service Verification

5-25.2.1 Verifying Services Manually

5-25.2.2 Verifying Services Through the M2000

6-16 Version Rollback

6-16.1 Process of Version Rollback

6-16.2 Rollback Operations

6-46.3 Post-Rollback Processing

7-17 Appendix

7-17.1 Upgrade Records

7-17.2 Backup Files Involved in the Upgrade

7-27.3 Items of the Automatic Check

7-37.4 List of BSC6900 OMU Ports that Are Not Enabled on the BSC6000 or BSC6810 OMU

1 Reading Before Upgrade1.1 Choosing an Upgrade GuideThis document, a general guide for V900R012C01 version upgrade, applies to all the upgrades to the V900R012C01SPCX00 or V900R012C01SPCXYZ or V900R012C01SPHXYZ.

X, Y, and Z indicate version number. Where, X indicates baseline version number, and both Y and Z indicate patch version number.

The baseline version is numbered according to the C version number. X ranges from 1 to 9, and YZ equals 00. For example, SPC100, SPC200, , and SPC900.1.2 Version Requirements for UpgradeTable 1-1 Version requirements for upgradeVersion Before the UpgradeDescription

V900R012C01 baseline versions and its patch versionsV900R012C00SPC100 and its patch versionsV900R011C00SPC700 and its patch versionsBSC6810V200R011C00SPC100 and its patch versionsBSC6000V900R008C01B051 and its patch versionsBSC6000V900R008C12B195 and its patch versionsThey can be upgraded to the V900R012C01SPCX00 or V900R012C01SPCXYZ or V900R012C01SPHXYZ directly.

BSC6810V200R010C01B061 and its patch versionsThey can be upgraded to the V900R012C01SPCX00 or V900R012C01SPCXYZ or V900R012C01SPHXYZ through an intermediate version "BSC6810V200R011C00SPC100."

If no upgrade rule is defined for the upgrade from an earlier version to the target version, then a VERSION is required for the upgrade. The version before the upgrade is upgraded to the VERSION, and then to the target version. This VERSION is named an "intermediate version."

1.3 Impacts of the Upgrade on the Existing SystemImpacts on Services

In the case of upgrade from BSC6810 to target version, services are disrupted for less than seven minutes. In the case of upgrade from BSC6000 to target version, services are disrupted for less than 16 minutes. In the case of upgrade from V900R011C00SPC700 and its patch versions, or V900R012C00SPC100 and its patch versions, to target version, or in the case of upgrade from V900R012C01 to a later V900R012C01, services are disrupted for two to seven minutes. In the case of cold patch installation, services are disrupted for less than seven minutes.

In the case of hot patch installation, services are not disrupted.Impacts on Network Communications

Communications with M2000 are disrupted for 10-30 minutes when installing the M2000 adapation layer.1.4 Notes and Cautions for Upgrade The pre-upgrade must be performed at least three days before the upgrade execution, and any fault that surfaces in the pre-upgrade check report must be rectified before the upgrade execution.

In the case of an upgrade from the BSC6810V200R010C01B061 or its patch versions to current version, please handle with the following problem according to corresponding avoidance measures described in Table 1-2.Table 1-2 Item list of problem and corresponding avoidance measures before upgradeProblem DescriptionAvoidance Measures

Compared with earlier versions, the mapping between PHB and DSCP is updated from the BSC6810V200R011 version. Please check the mapping between the PHB and DSCP before upgrade.You should ensure that the mapping between the PHB and DSCP value in all TRMMAP tables is on one-to-one basis.1. Before upgrading the BSC6810V200R010C01B061 or its patch versions to current version, run the MML command LST IPPATH to check whether the IP paths of HQ_QOSPATH or LQ_QOSPATH exist. If they exist, you should check the mapping between the PHB and the DSCP value. If they do not exist, skip the following operations.

2. Before the upgrade, ensure that the mapping between the PHB and the DSCP is unique. Run the LST TRMMAP to check if the transport resource mapping is set. If not, skip the following operations. If yes, run the LST TRMMAP and LST DEFAULTTRMMAP commands separately to check the mapping between the PHB and the DSCP in the TRM mapping (TRMMAP) or default TRM mapping (DEFAULTTRMMAP). The PHB (value range: BE, AF11-AF43, EF) and DSCP (value range: 0-63) should be strictly and correctly mapped.

If the DSCP value corresponding to some PHBs in some TRMMAP tables is inconsistent with that corresponding to the PHBs in other TRMMAP tables, run the MML command MOD TRMMAP to change the DSCP value according to the least modification principle. The least modification principle indicates that the data should be modified as little as possible to meet the requirement for the upgrade. For example, if the DSCP value corresponding to EF in most TRMMAP tables is 46 but that in some TRMMAP tables is 47, you should change the DSCP value from 47 to 46. If the DSCP value corresponding to some PHBs in some DEFAULTTRMMAP tables is inconsistent with that corresponding to PHBs in other DEFAULTTRMMAP tables, run the MML command SET DEFAULTTRMMAP or MOD TRMMAP to change the DSCP value accordingly. For example, besides the DEFAULTTRMMMAP, two TRMMAPs are configured: TRMMAP1 and TRMMAP2. In TRMMAP1, the DSCP value corresponding to EF is 46, which is the same as the DSCP value corresponding to EF in the DEFAULTTRMMMAP. The DSCP value corresponding to EF in TRMMAP2, however, is 47. In this situation, the DSCP value corresponding to EF in TRMMAP2 should be changed to 46.

Compared with earlier versions, the mapping between IP path and DSCP is updated from the BSC6810V200R011 version. Please check the mapping between the IP Path and DSCP before the upgrade.1. Before the upgrade, ensure that the DSCP values of one-type IP paths of are the same.Before the upgrade, ensure that the IP path and the DSCP are strictly and correctly mapped. Run the MML command LST IPPATH to check the mapping between the IP path and DSCP. If the DSCP value corresponding to some IP paths is inconsistent with that corresponding to other IP paths of the same type, run the MML command MOD IPPATH to change the DSCP value according to the least modification principle.

2. If the DSCP value corresponding to the IP path over the Iub interface at the RNC is changed, you should run the MML commands RMV IPPATH and ADD IPPATH to make the corresponding change on the NodeB.

For example, there are three IP paths of the XXX type, namely, IPPATH 1, IPPATH 2, and IPPATH 3. The DSCP value of IPPATH 1 and IPPATH 2 is 46, but the DSCP value of IPPATH 3 is 47. You should change the DSCP value from 47 to 46 in IPPATH 3, and run the MML commands RMV IPPATH and ADD IPPATH to make change in the NodeB.

Compared with earlier versions, the bandwidth of AAL2 path and VP is updated from the BSC6810V200R011 version. Please check the bandwidth of AAL2 paths and VP before upgrade.1. Run the MML command LST AAL2PATH to check whether there are AAL2 paths in VP bearer mode. If there are ALL2 paths in VP bearer mode, go to the next step.

2. Check whether the service type of the transmission traffic index and reception traffic index of the AAL2 Path is CBR/RT VBR/NRT VBR. If yes, go to the next step.

3. Check whether the peak cell throughput of index of the AAL2 path is greater than the forward bandwidth and backward bandwidth of the VP. If yes, go to the next step.

4. Run the MML command ADD ATMTRF to add a new traffic index. The service type of the new traffic index should be the same as that of the transmission traffic index and reception traffic index of the AAL2 path. The peak cell throughput of the index should not be greater than that of the VP.

5. Run the MML command MOD AAL2PATH to change the transmission traffic index and reception traffic index of the AAL2 path to the new traffic index to ensure that the transmission traffic index and reception traffic index are not greater than the bandwidth of the VP.

During the process the RNC is upgraded, the M2000 automatically deletes the EMS IP address, and fails to add it. Thus, the EMS IP address may be lost after the upgrade, and the NodeB fails to be maintained on the M2000 client.To avoid the possible loss of the EMS IP address, do as follows:1. Before the upgrade, log in to the RNC through the LMT, run the MML command LST EMSIP, and then record the displayed EMS IP address.

2. After the upgrade is completed, log in to the RNC through the LMT, run the MML command LST EMSIP to query whether the EMS IP address exists. If the EMS IP address does not exist, run the MML command ADD EMSIP to add the recorded EMS IP address manually.

1.5 TermsTable 1-3 lists the common terms used in this guide.

Table 1-3 Common termsTermDescriptionExample

New VersionNumber of the version after the upgradeV900R012C01SPCX00 or V900R012C01SPCXYZ or V900R012C01SPHXYZ

OMU_AActive OMU before the upgrade-

OMU_BStandby OMU before the upgrade-

OMU_RootPathInstallation path of the OMUIf the upgrade from the BSC6000V900R008 to the V900R012C01 has been performed, the OMU_RootPath is /BSC6000/data/mbsc.

Otherwise, if the OMU operating system is Windows, the OMU_RootPath is D:\mbsc; if the OMU operating system is Linux, the OMU_RootPath is /mbsc

External virtual IP addressThe external virtual IP address, which is set when the OMU applications are installed, is used for the communication between the OMU and the LMT or M2000, and is included in the external Ethernet adapter team of the active OMU.-

Version installation packageA version installation package is the software package decompressed from the V900R012C01SPCX00 VER.rar file that is obtained from http://support.huawei.com/. If the V900R012C01SPCX00 is the target version, then the V900R012C01SPCX00 package is also called target version installation package.V900R012C01SPCX00

Patch installation packageA patch installation package is the software package decompressed from the V900R012C01SPCXYZ VER.rar or V900R012C01SPHXYZ VER.rar file that is obtained from http://support.huawei.com/. If the V900R012C01SPCXYZ or V900R012C01SPHXYZ is the target version, then the V900R012C01SPCXYZ or V900R012C01SPHXYZ package is also named target patch installation package.V900R012C01SPCXYZ or V900R012C01SPHXYZ

Installation packageAn installation package refers to a version installation package or a patch installation package.V900R012C01SPCX00 or V900R012C01SPCXYZ or V900R012C01SPHXYZ

2 Upgrade ProcessFigure 2-1 shows the upgrade process.

Figure 2-2 Upgrade process

3 Preparations for UpgradeThis chapter describes the preparations to be made for the upgrade. Prepare properly in advance to ensure that the upgrade is completed on time.Table 3-1 lists the items that need to be checked before the upgrade.

The directory and the data files under the directory before the upgrade will not be deleted in the upgrade process. You need not back up the data manually.

Table 3-4 Checklist before upgradeNo.ItemDescription

1Check that all the BSC6900 OMU ports that are not enabled on the BSC6000 or BSC6810 OMU are enabled.In the case of upgrade from the BSC6000 or BSC6810 to the V900R012C01, the OMU ports that are added on the BSC6900 compared with BSC6000 or BSC6810 need to be opened. Ensure that the customer checks if the OMU ports are shielded with a firewall. If not, skip this step. If yes, ask the operator to check that the firewall has not blocked the OMU ports. For details about the OMU ports that are added on the BSC6900 compared with BSC6000 or BSC6810, see section 7.4 "List of BSC6900 OMU Ports that Are Not Enabled on the BSC6000 or BSC6810 OMU."

2Confirm that the firewall has not blocked the external fixed IP addresses of the active and standby OMUs.1. If the version before the upgrade is BSC6810, run the DSP BAM command to query the external fixed IP addresses. If the version before the upgrade is BSC6900, run the DSP OMU command to query the external fixed IP addresses.2. If the external fixed IP addresses do not exist, skip this step.3. If the external fixed IP addresses exist, check if there is a firewall in the network between the upgrade client and the OMU. If not, skip this step. If yes, ask the operator to check that the firewall has not blocked the external fixed IP addresses of the active and standby OMUs.

3Make ready the security patches KB944338 and KB960714 of Microsoft Windows XP Professional SP02 or Microsoft Windows 2003.The security patches KB944338 and KB960714 of Microsoft Windows XP Professional SP02 or Microsoft Windows 2003 must be installed before you log in to the Web LMT through an IE browser on the operating system. Visit the website http://www.microsoft.com/downloads to download security patches KB944338 and KB960714, and then install them by referring to the FAQ "Installing OS Patches" in the BSC6900 LMT User Guide.

4Check the version mapping between related products in the existing networkIn the case of upgrade from the BSC6000/BSC6810, check whether the versions of the related products in the existing network map V900R012C01. For details on the version mapping between the related products, see section 1.3 "Related Product Versions" in the Release Notes.

5Obtain the new license fileIn the case of upgrade from the BSC6000/BSC6810, V900R011C00 or V900R012C00 to the V900R012C01 versions, applying for a new license is required. Ensure to apply for the license file by using the template that matches V900R012C01 and that the ESN is consistent with the NE to be upgraded.

6Collect the information about the site1. Obtain the password for user admin and the virtual external IP address relevant to each network element (NE) to be upgraded.

2. Obtain the password for user root of the active OMU operating system of the NE to be upgraded in the case of an upgrade from the BSC6000 to the V900R012C01.

7Install the M2000 adaptation layerInstall the M2000 adaptation layer by referring to section3.1 "Installing the M2000 Adapation Layer".

8Perform the NE health check before the upgradePerform the health check on the network before upgrade by referring to section 3.2 "Performing the NE Health Check".

9Start the NE transfer toolIn the case of upgrade from the BSC6000/BSC6810 to the V900R012C01, start the NE transfer tool to upgrade the M2000 data by referring to section 3.3 "Starting the NE Transfer Tool".

10Prepare files for the upgradePrepare files for the upgrade by referring to section 3.4 "Preparing Files for the Upgrade".

11Perform the pre-upgradePerform the pre-upgrade before the upgrade execution to locate and solve the problems that surface during the pre-upgrade by referring to sections 4.1 "Starting the Upgrade Client", 4.2 "Configuring the Basic Information About the Upgrade", and 4.3 "Performing Pre-Upgrade".

12Check whether the OMUa or OMUb board driver needs to be upgradedIf the upgrade client prompts that the version of the OMU driver is too early, obtain the OMU driver upgrade tool, and then upgrade the OMU driver by referring to the OMU Suse Linux 9.3 Operating System Driver Upgrade Guide. Otherwise the stability of operating system will be affected.

3.2 Installing the M2000 Adapation LayerPerform the following steps to determine whether the M2000 adaptation layer needs to be installed.Step 2 Start the M2000 client. Choose Software > Software Browser. A window is displayed. In the navigation pane, click the OMC Server tab, expand the OMC > Mediation, and then select an NE type. View the version of the M2000 adaptation layer in the right pane of the window.Step 3 View the version of the M2000 adaptation layer by referring to section 1.2 "Software Versions" in the Release Notes of target version.Step 4 Check whether the version of the M2000 adaptation layer obtained in Step 1 is consistent with that of the M2000 adaptation layer obtained in Step 2. If yes, end this task. If not, proceed with the next step.Step 5 Read through the Warning for Mediation Installation Essentials that matches the M2000 adaptation layer, choose the Operation Guide for Mediation (Only for M2000 Common Version is V200R006 or Later) that matches the upgrade, and then install the M2000 adaptation layer.3.3 Performing the NE Health Check

The function of NE health check is supported when the current version is V900R011C00 or later versions.

This section describes how to perform the health check on the NE before the upgrade when the traffic is not busy so that you can determine whether the NE can be upgraded based on the operating status of the NE and the network..3.3.1 Creating a Task for Checking the NE Health

Step 6 Start the M2000 client, and then choose Maintenance > NE Health Check.

Step 7 On the displayed tab page, click New to configure the information on the check task.

1. Select Upgrade Check from the Scenario drop-down list.

2. M2000 automatically obtains one name of the task in the Name text box. The user can modify the name.3. In the displayed NE dialog box, select the NE to be checked from the Unselected NEs navigation tree on the left, and then click to move the NE to the Selected NEs navigation tree on the right. Alternatively, you can click to move all the NEs from the Unselected NEs navigation tree on the left to the Selected NEs navigation tree on the right.

4. In the Time Setting frame, select Instant.

Step 8 Click Next.

Retain the default value of Health Check Period.

Step 9 Click Finish to finish creating the task of the NE health check. When the task of health check on the network is finished, it will be displayed under the Finished Tasks node in the navigation tree on the left panel of the NE Health Check tab page.----End

3.3.2 Checking the Reports

To check the NE health reports, do as follows:

Step 10 Under the Finished Tasks node in the navigation tree, select a task, and then choose View Report from the right-click shortcut menu under main window. The Health Check Report dialog box is displayed.

Step 11 Select the expected report from the report list, and then click Open to check whether all the items are normal.

If...Then...

There are items displayed in red,Check if there is a fault. You are advised to handle with the fault by referring the reports before upgrade.

There are no items displayed in red,The running NE works properly and you can upgrade it immediately.

Step 12 Click Save as On the displayed Save dialog box, select a save path for the report. The report on the health check is saved as a .zip file. You can double-click the .zip file to browse the compressed files, and then double-click the report to open it.

The report on the health check can be saved as an .html file or .doc file.

In the case of the health check is saved as .doc file, decompress the zip file first, and then open the .doc file. In the case of the health check is saved as .html file, choose index.html file.----End

3.4 Starting the NE Transfer ToolIn the case of upgrade from the BSC6000/BSC6810 to the V900R012C01, you should start the NE transfer tool before the upgrade. For details, see section 2.1"Starting the Relocation Tool" in the BSC6900 V900R012C01 Data Relocation Guide(Only for M2000 Common Version is V200R010).3.5 Preparing Files for the UpgradeDownload an installation package from http://support.huawei.com/ to a PC. For details on the required installation package, see Table 3-2.

If the upgrade is performed through the M2000, the PC refers to the one where the M2000 client is running.

If the upgrade is performed through the upgrade client, the PC refers to the one where the upgrade client is running. In order to make sure the following upgrade can be processed normally, the free space of the PC should be more than 1 GB before upgrade.Table 3-5 Installation package for different upgrade scenariosVersion Before the UpgradeTarget VersionRequired Installation Package

V900R012C01 baseline version and its patch versionsV900R012C01SPCX00Target version installation package: V900R012C01SPCX00

V900R012C01SPCXYZ or V900R012C01SPHXYZIf the baseline version number of the target version is the same as the baseline version number of the version before the upgrade, the target patch installation package V900R012C01SPCXYZ or V900R012C01SPHXYZ is required.

If the baseline version number of the target version is different from the baseline version number of the version before the upgrade, the baseline version installation package of the target version V900R012C01SPCX00 and the target patch installation package V900R012C01SPHXYZ are required.

V900R012C00SPC100 and its patch versionsV900R011C00SPC700 and its patch versionsBSC6810V200R011C00SPC100 and its patch versionsBSC6000V900R008C01B051 and its patch versionsBSC6000V900R008C12B195 and its patch versionsV900R012C01SPCX00Target version installation package: V900R012C01SPCX00

V900R012C01SPCXYZ or V900R012C01SPHXYZVersion installation package: V900R012C01SPCX00Target patch installation package: V900R012C01SPCXYZ or V900R012C01SPHXYZ

BSC6810V200R010C01B061 and its patch versionsV900R012C01SPCX00Target version installation package: V900R012C01SPCX00Intermediate version installation package: BSC6810V200R011C00SPC100

V900R012C01SPCX00V900R012C01SPCXYZV900R012C01SPHXYZVersion installation package: V900R012C01SPCX00Target patch installation package: V900R012C01SPCXYZ or V900R012C01SPHXYZ

Intermediate version installation package:

BSC6810V200R011C00SPC100

Step 13 To obtain a patch installation package or version installation package, do as follows:

1. Log in to http://support.huawei.com/. Choose Software Center > Version Software > Wireless Product Line > SingleRAN > MBSC > BSC6900 to obtain the V900R012C01SPCX00 VER.rar or V900R012C01SPCXYZ VER.rar or V900R012C01SPHXYZ VER.rar files.

2. Decompress the files to obtain the version installation package V900R012C01SPCX00 or patch installation package V900R012C01SPCXYZ or V900R012C01SPHXYZ. Figure 3-1 shows the directory structure of the version installation package V900R012C01SPCX00, and Figure 3-2 shows the directory structure of the patch installation package V900R012C01SPCXYZ or V900R012C01SPHXYZ.

Figure 3-3 Directory structure of the version installation package

Figure 3-4 Directory structure of the patch installation package

Step 14 To obtain an intermediate version installation package, do as follows:

1. Choose Software Center> Version Software > Wireless Product Line > WCDMA RAN > WCDMA RNC > BSC6810 > HUAWEI BSC6810V200R011C00SPC100 to obtain the BSC6810V200R011C00SPC100 version installation package.Figure 3-3 shows the directory structure of BSC6810V200R011C00SPC100.Figure 3-5 Directory structure of BSC6810V200R011C00SPC100

2. Choose Software Center > Version Software > Wireless Product Line > WCDMA RAN > WCDMA RNC > BSC6810 > BSC6810V200R011 to find the latest patch version. Then, obtain Upgrade Guide Attachment file from the latest patch version mapping documentation and decompress the file. The UPD_PREDATACHECK_V200R010C01B061_V200R011C00SPC100_COMMON.sql and UPD_RULE_V200R010C01B061_V200R011C00SPC100_COMMON.xml files are extracted.

3. Copy the DataMan_FOR_EXP_MML.exe and library.zip files to [V200R011C00SPC100]\upgrade directory as shown in Figure 3-3 and overwrite the existing files. Copy the UPD_RULE_V200R010C01B061_V200R011C00SPC100_COMMON.xml and UPD_PREDATACHECK_V200R010C01B061_V200R011C00SPC100_COMMON.sql files to [V200R011C00SPC100]\upgraderule\common directory as shown in Figure 3-3 and overwrite the existing files.

The Upgrade Guide Attachment and the Upgrade Guide files are saved in the same directory.----End

4 Upgrade OperationsTable 4-1 lists the tasks involved in the upgrade process. Before you perform the upgrade operations, ensure that the preparation for the upgrade is complete.Table 4-6 Upgrade tasks

TaskDuration (min)

Starting the upgrade clientIf the upgrade client is started through the M2000, this task takes less than 10 minutes.

If the upgrade client is started through the client, this task takes less than one minute.

Configuring basic information about upgradeIf the upgrade client is started through the M2000, this task takes less one minute.

If the upgrade client is started through the client, this task takes less seven minutes.

Performing the pre-upgrade20-80

Performing the upgrade20-60

This guide takes the upgrade in dual-OMU mode as an example. The upgrade in single-OMU mode is similar to that in dual-OMU mode.

The duration of uploading the version files varies according to the bandwidth of sites. Estimate the duration according to the bandwidth of the sites. For detailed avoidance measures of abnormity, see the upgrade client on-line FAQ.4.2 Starting the Upgrade Client

This document provides two upgrade methods: through the M2000 and through the upgrade client. You are advised to perform the upgrade operations through the M2000. You can also perform the upgrade operations through the upgrade client when the M2000 does not work normally. The differences between the two methods are described as follows:

When the NE is upgraded through the M2000, the required files are uploaded through the M2000, and then the upgrade client is started.

When the NE is upgraded through the upgrade client, the BSC to be upgraded is added to the upgrade client, and the required files are uploaded to the BSC through the upgrade client.

4.2.1 Starting the Upgrade Client Through the M2000

If upgrade from the BSC6000 to the V900R012C01, start the upgrade client through the M2000 and then upload the installation package to the NE through the upgrade client. Otherwise, you need to upload the installation package to the M2000 server and download the installation package from the M2000 server to the NE before starting the upgrade client through the M2000. The versions earlier than the BSC6000V900R008C01B051SP24 do not support upgrade through the M2000.Step 15 Start the M2000 client.

Step 16 In the case of upgrade from BSC6810V200R011C00SPC100 or its patch, you need to set the RNC as an FTP server on the M2000.

1. Choose Software > File Server Setting. The File Server Setting dialog box is displayed, as shown in Figure 4-1.

2. Click RNC on the navigation tree in the left pane, select a designated RNC in the left pane, and then change the name under the File Server Name area to that of the current RNC.

Figure 4-6 File server setting

Step 17 In the case of the NE type to be upgraded is RNC or BSC6900, you need to upload the installation package through the M2000. In the case of the NE type to be upgraded is BSC6000, skip this step and go to Step 4.1. Choose Software > Software Browser. A window is displayed. Select an NE type to be upgraded from the OMC Server tab on the left navigation tree.2. On the Upgrade Software Package tab page, click Transfer, and then choose From OMC Client to OMC Server. A dialog box is displayed, as shown in Figure 4-2.

Figure 4-7 Selecting upgrade software package

3. Click Select. A dialog box is displayed. Select an installation package to be uploaded to the M2000 server and click OK. For details on the required installation package, see Table 3-2.

4. Click Confirm in the dialog box shown in Figure 4-2 to start uploading the installation package to the M2000 server.

5. From the list on the Upgrade Software Package tab page, select the installation package, click Transfer, and choose From OMC Server to NE to download the installation package to the NE. A dialog box is displayed.

6. Select an NE and click OK. The installation package starts to be downloaded from the M2000 server to the NE.

Step 18 Start the upgrade client. Choose Software > Software Browser. A window is displayed. Select an NE type to be upgraded from the OMC Server tab on the left navigation tree. Click Upgrade Software Package in the right pane.If...Then...

The BSC6000 is to be upgraded to the V900R012C01 or the later versions,Click Upgrade. Select the NE to be upgraded in the displayed dialog box, select the directory where the upgrade client program is saved: [V900R012C01SPCXYZ]\remoteclient or [V900R012C01SPHXYZ]\remoteclient. Click OK and then go to 4.2 "Configuring the Basic Information About the Upgrade."

The upgrade is not from the BSC6000 to the V900R012C01 or the later versions,Choose the target installation package and then click Upgrade. Select the NE to be upgraded in the displayed dialog box.and click OK. The Download Upgrade Tool dialog box is displayed, showing the download progress. Click OK and the upgrade client starts automatically. Proceed with the operations described in section 4.2 "Configuring the Basic Information About the Upgrade."

----End

4.2.2 Starting the Upgrade Client Through the Client

Step 19 Run RemoteClient_eng.exe in the directory [New Version]\remoteclient. A window is displayed. Step 20 Right-click NE List on the left pane of the window, and then choose Add NE from the shortcut menu. A dialog box is displayed, as shown in Figure 4-3.

Figure 4-8 Adding an NE

Step 21 Enter NE Name, External Virtual IP Address of the NE to be upgraded. If the NE cannot communicate with the client directly, an EMS proxy server is required for the upgrade. Select EMS Proxy IP Address, and enter the IP address of the EMS proxy server. An NE is added successfully.

NE Name is used to identify an NE. It consists of only letters, numerals, "-", and "_" characters.

In the case of upgrade from the BSC6000 to the V900R012C01, External Virtual IP Address refers to the External IP Address.Step 22 Repeat from Step 2 to Step 3 to add multiple NEs.

After an NE is added, the relevant NE Name, External Virtual IP Address, and EMS Proxy IP Address cannot be modified. To modify the NE name or the IP address of an NE, delete the NE and then add it again.

If multiple NEs are added, they can be upgraded at the same time. You can double-click an NE in the navigation tree on the left or select an NE in the information page of the NE to switch between NEs. Sections 4.2 "Configuring the Basic Information About the Upgrade", 4.3 "Performing Pre-Upgrade", and 4.4 "Performing Upgrade" describe the upgrade of an NE. The following describes the procedure for upgrading one NE.----End

4.3 Configuring the Basic Information About the UpgradeThis section describes how to configure the basic information about the upgrade.

Step 23 Double-click the NE to be upgraded in NE List in the left pane. A window is displayed, as shown in Figure 4-4.

Figure 4-9 Input Step 1

Step 24 Enter the Password of Admin User. Select Upgrade and click Next. The system automatically obtains the version information, as shown in Figure 4-5.

If the user Admin is online, exit the LMT that is connected to the OMU, and then restart the LMT.Figure 4-10 Input Step 2

Step 25 (Perform this step only in the case of an upgrade from the BSC6000 to the V900R012C01) Enter the Password for user root of the active in Figure 4-5.Step 26 (For upgrade from the BSC6810V200R010C01B061 or its patch versions to the V900R012C01 only) Select Intermediate Version and enter BSC6810V200R011C00SPC100 in Figure 4-5.Step 27 Click Next in Figure 4-5. A window is displayed, as shown in Figure 4-6. The system automatically obtains the information of OMU. Figure 4-11 Input Step 3

Step 28 Enter the basic configuration information for the upgrade in the window shown in Figure 4-6.

If the new license is needed, you must upload the license file here.

You must choose Upload the version file if the version files are not downloaded to the NE through the M2000 and the version files are not uploaded to the OMU through the upgrade client.

1. Select the New license file check box, and then click Browse to select the license file. Click Open. The upgrade client automatically uploads the new license file to the OMU, and the new license is activated automatically.

2. If the target version is V900R012C01SPCXYZ or V900R012C01SPHXYZ and a version installation package is required (for details, see Table 3-2), select the Browse version installation package and select a version installation package to be uploaded in the displayed dialog box.

3. Click Upload installation package files. The target installation package starts to be uploaded. In the case of upgrade from the BSC6810V200R010C01B061 or its patch versions to the V900R012C01, select the intermediate version installation package BSC6810V200R011C00SPC100 in the displayed dialog box. The upgrade client automatically uploads the intermediate version installation package to the OMU.4. Click Pre-upgrade to proceed with the operations described in section 4.3 "Performing Pre-Upgrade."----End

4.4 Performing Pre-UpgradeThe upgrade tool automatically performs pre-upgrade operations after you click Pre-upgrade.

This section describes the check before the upgrade and the pre-upgrade of the OMU software and data.

When upgrading multiple NEs, you can monitor the connections of all NEs through the monitoring dialog box. If any exception occurs, double-click the message in red to directly skip to the relevant NE monitor page for confirmation.

When upgrading multiple NEs, you can monitor the connections of all NEs through the monitoring dialog box. If any exception occurs, double-click the message in red to directly go to the relevant NE monitoring page for confirmation.

For details on the backup files, see section 7.2 "Backup Files Involved in the Upgrade".

For details on the upgrade check items, see section 7.3 "Items of the Automatic Check ".

Step 29 After the pre-upgrade is complete, a window is displayed, as shown in Figure 4-7.

Figure 4-12 Checking report after the pre-upgrade

Step 30 Click Check Report to view the pre-upgrade result. If the pre-upgrade fails, correct the erroneous data according to the prompted messages. Click Back to return to the previous step, and then perform the pre-upgrade again.

If the pre-upgrade is successful, click Next to proceed with the upgrade execution.

If the upgrade execution is not required at the moment, click Finish to end the pre-upgrade and exit the upgrade client.----End

4.5 Performing Upgrade

This section describes how to upgrade the OMU to the latest version and restart the host. The system automatically performs the upgrade.Step 31 The system automatically performs the upgrade. A window is displayed, asking you whether to upgrade the OMU to the latest version, as shown in Figure 4-8.

Figure 4-13 Confirmation window

Step 32 Click OK in the dialog box shown in Figure 4-8 to upgrade the OMU to the latest version. A dialog box is displayed for confirmation. Click Yes. In the case of upgrade from the BSC6000/BSC6810 to the V900R012C01, the M2000 detects that the NE type is changed to BSC6900 and switches to the limited mode automatically. Then, the M2000 starts to transfer the NE data automatically.

If the M2000 client is connected during the upgrade process, a dialog box is displayed, prompting that the M2000 automatically switches to the limited mode. You can infer that the M2000 starts to transfer the NE data.

Step 33 After the swapping, the confirmation window displays updated information, as shown in Figure 4-9. Click OK to reset the host. A dialog box is displayed for your confirmation. Click Yes.Figure 4-14 Confirmation window with updated information

Step 34 After the reset, the confirmation window displays updated information, as shown in Figure 4-10. Proceed with the service verification.

If multiple NEs controlled by one MSC are upgraded at the same time, the hosts of each NE cannot be reset at the same time. The interval between the resets of hosts should be at least five minutes. Otherwise, the MSC may be congested for a short time. In batch upgrade in TC convergence network, reset the slave BSC, and then reset the master BSC 30 minutes after the slave BSC is reset (the upgrade of the slave BSC is completed). For details on what TC convergence network is, see FAQ in the upgrade tool.Figure 4-15 Confirmation box before verifying the services

Step 35 In the case of upgrade from the BSC6000/BSC6810 to the V900R012C01, check that the data transfer on the M2000 side is successful by referring to section 2.3 "Querying the Statuses of Upgrade Tasks" in the BSC6900 V900R012C01 Data Relocation Guide(Only for M2000 Common Version is V200R010).

If the M2000 client is connected during the upgrade process, a dialog box is displayed, prompting that the M2000 switches to the multi-user mode automatically. You can infer that the M2000 has transferred the NE data successfully.Step 36 Verify the service. For the service verification methods, see section 5 "Post-Upgrade Verification".

If...Then...

The verification is successful, Click Yes to proceed with the upgrade. A dialog box is displayed for your confirmation. Click Yes. A dialog box is displayed, as shown in Figure 4-11.

The verification fails, Click No to check the report, the then click Next to roll back the version. The rollback is automatically executed.

Figure 4-16 Checking the report

Step 37 Click Check Report in the dialog box to check the upgrade report. Click Finish to end the upgrade. A dialog box is displayed for your confirmation. Click Yes.

The reports and logs generated by the upgrade client are saved in the directory remoteclient\Report. It is recommended that they be archived for future use. Do not delete the upgrade files saved in [OMU_RootPath]\mbsc\upgrade\ on the OMU after the upgrade.

Step 38 If the NE transfer tool is started on the M2000 side before the upgrade, stop the NE transfer tool after the upgrade is complete. For details, see section 2.4 "Stopping the Relocation Tool" in the BSC6900 V900R012C01 Data Relocation Guide (Only for M2000 Common Version is V200R010).----End4.6 Post-Upgrade Special Processing(Only for BSC6900 UO or GU Mode)In V900R012C01SPC200 version, the function of blind detection does not take effect. For example, even if CFG_DL_BLIND_DETECTION_SWITCH is set to ON by running the SET UCORRMALGOSWITCH command, the function of blind detection is unavailable. If CFG_DL_BLIND_DETECTION_SWITCH is set to ON for these versions before they are upgraded to V900R012C01SPH202, run the following command to ensure that the function of blind detection is disabled and to prevent KPI deterioration after the upgrade is complete:SET UCORRMALGOSWITCH: CfgSwitch=CFG_DL_BLIND_DETECTION_SWITCH-0;5 Post-Upgrade VerificationPost-upgrade verification involves the NE health check and service verification. The NE health check detects the radio resources and operating status of the NE system, and the service verification checks whether NE services are provided properly after the upgrade.5.1 Post-Upgrade NE Health CheckThe post-upgrade health check on the network is used to determine whether the upgrade succeeds. The report of the post-upgrade health check is compared with that of the pre-upgrade health check to indicate the difference between the operating status of the upgraded NE and its original status.

5.1.1 Performing the Post-Ugrade NE Health Check

For details on how to perform the health check on the network after the upgrade, see section 3.2 "Performing the NE Health Check".

5.1.2 Comparing the Report of the Post-Upgrade Health Check with That of the Pre-Upgrade Health Check

Step 39 Choose Maintenance > NE Health Check from the menu bar on the M2000 client.

Step 40 Click Compare. The Compare Reports dialog box is displayed.Step 41 In the Report1 box, select the task name of the NE health check before the upgrade from the Task drop-down list box. In the Report2 box, select the task name of the NE health check after the upgrade from the Task drop-down list box.Step 42 In the Report1 and Report2 boxes, select Report Generation Time.

Step 43 Click Compare to compare the report on NE health check before the upgrade with that on NE health check after the upgrade.Step 44 After the comparison is complete, the Save dialog box is displayed. Select a path for saving the comparison report on the PC. View the comparison report, and then find out the differences of the NE status before and after the upgrade.----End

5.2 Post-Upgrade Service Verification

After the upgrade is complete, you need to verify the NE services manually and through the M2000 to determine whether the NE services are normal. To test the basic calling procedure, you can verify the NE services manually. To check whether the traffic statistics are normal, you can verify the NE services through the M2000.

5.2.1 Verifying Services Manually

Verify the NE services manually. For details, see the Appendix 6 BSC6900 V900R012C01 Upgrade Acceptance Cases.

5.2.2 Verifying Services Through the M2000

You can verify the NE services through the M2000: compare the values of the KPIs reported by the NE every five minutes with the standard values and the historical values of the KPIs to determine whether the NE services are normal. The operation steps are as follows:

Step 45 On the M2000 client, choose Maintenance > Task Management. A window is displayed. Click New at the right hand bottom corner for the new task. The New Task dialog box is displayed.

Step 46 Enter the task name in the Task Name box, select Upgrade Checking in the Task Type box, and click Next. A dialog box is displayed.

Step 47 Set the Start Time to Run At Once and click Next.

Step 48 Select the NE whose services are to be upgraded, the Object type (You can select counters of different object types. Select the object type in order, and select all the counters of the object type), and Upgrade time (which is used to calculate the history counters), as shown in Figure 5-1. The Upgrade time refers to the time when the upgrade execution is finished. You can find out when the upgrade execution is finished in the report obtained in Step 5 of section 4.4 "Performing Upgrade."Figure 5-17 Selecting KPIs

Step 49 Click Finish. The Task Management window is returned. The M2000 automatically verifies the NE services according to the upgrade time.

The service verification generally takes 30 minutes.

Step 50 The KPIs with optimal values are displayed on the M2000 client. You can select the Object type to view the KPIs of different measurement objects. The result of the NE service verification is displayed in the Counters Info list box, as shown in Figure 5-2.

Figure 5-18 Querying the result of the NE service verification

Step 51 Double-click an Object Name in the Counters Info box. result. The Detail dialog box is displayed. In the Detail dialog box, view the detailed result of the NE service verification, including the current value, the historical value, the standard value, and the result.

Current value: The result of the counter that is reported by the NE.

Historical value: The average value of the counters that are collected in the same period seven days before the upgrade. The period starts from one hour before the service verification starts. For example, the service verification starts from 12:00 2009-2-11, then the historical value is the average value of the counters that are collected from 12:00 to 13:00 each day from 2009-2-4 to 2009-2-10.

Standard value: The reference value according to which the result of the counter is determined correct or not.

If there is any counter that does not meet the standard value, contact Huawei for technical support.

Step 52 After the NE service verification is complete, a message reading "Task run successfully. Please save the report" is displayed in the Summary Info box. Click Save Log to save the result of the service verification to the local PC for future use.

----End

6 Version Rollback

If there are any defects after the upgrade, roll back the version or patch to the original one by following the rollback procedure.

6.1 Process of Version Rollback

Table 6-1 lists the rollback process and time required at each step of the version rollback process.Table 6-7 Time required at each step of the version rollback process

Rollback OperationTime Consumed (Unit: min)Remarks

Start the rollback< 1-

Configure the rollback data< 1-

Perform the rollbackTo roll back to the BSC6000: 15-60.To roll back to the BSC6810, V900R011, V900R012C00SPC100, V900R012C01 or its later versions: 10-20.

Patch rollback: 10-30.-

Verify the upgrade30-60-

6.2 Rollback Operations

To perform rollback, do as follows:Step 53 Start the upgrade client and then add the NEs to be rolled back. For details, see step 4 in section 4.1.1 "Starting the Upgrade Client Through the M2000" or section 4.1.2 "Starting the Upgrade Client Through the Client".

In the case of rolling back to the BSC6810 or BSC6000, if start of the upgrade tool fails, check if there is installation package under the current NE type. If not, upload the installation package of current version to M2000 server. For detailed operation, see section 4.1.1 .Step 54 Double-click the NE to be rolled back in the left pane of the window. The window is refreshed, as shown in Figure 4-4. Enter the Password of Admin and select an operation: Rollback. Click Next. The window is refreshed, as shown in Figure 6-1.

Figure 6-19 Rollback window

Step 55 The upgrade client automatically obtains the Current Version and Target Version. If two target versions displayed in Target Version, choose the target version.

If...Then...

The upgrade is from the BSC6000 to the V900R012C01 or the later versions,Enter the password for user root of the active OMU in the Password for user root of the active box, and click Next. A window is displayed, as shown in Figure 6-2.

The upgrade is not from the BSC6000 to the V900R012C01 or the later versions,Click Next. A window is displayed, as shown in Figure 6-2.

Figure 6-20 Configuration information about version rollback

Step 56 Click Execute. The upgrade tool automatically performs the rollback. After the rollback in the preparation phase is complete, click Check Report. The result of the check report is automatically opened and the Next button is available at the same time. Click Next to proceed with the execution phase. A dialog box is displayed for your confirmation. Click Yes.Step 57 During the version rollback, the upgrade tool prompts you to reset the host, as shown in Figure 4-9. Click OK. A dialog box is displayed for your confirmation. Click Yes. After the rollback, a dialog box is displayed, as shown in Figure 4-11. Check the report and click Finish to finish the rollback. A dialog box is displayed for your confirmation. Click Yes.IfThen

Rollback from the V900R012C01 to the BSC6000/BSC6810Perform the post-upgrade processing by referring to section 6.3 "Post-Rollback Processing".

Other rollback scenarioVerify services by referring to section 5.2 "Post-Upgrade Service Verification."

----End

6.3 Post-Rollback ProcessingStep 58 In the case of rollback from the V900R012C01 to the BSC6000/BSC6810, roll back the NE data on the M2000 side by referring to chapter 3 "Rollback Instruction" in the BSC6900 V900R012C01 Data Relocation Guide(Only for M2000 Common Version is V200R010).

Step 59 Perform post-upgrade service verification. For details, see section 5.2 "Post-Upgrade Service Verification". Ensure that the test cases are the ones of the version before the upgrade.----End

7 Appendix

7.1 Upgrade RecordsFor details, see the Appendix 6 BSC6900 V900R012C01 Upgrade Acceptance Cases.7.2 Backup Files Involved in the Upgrade

Table 7-8 Backup files involved in the upgrade

Backup ItemBackup LocationRemarks

Data script[OMU_RootPath]\upgrade\[New Version]\upgrade\ bsc6000_cfg_bak.dat on the OMU_A in the case of an upgrade from the BSC6000 to the V900R012C01.[OMU_RootPath]\upgrade\[Old Version]\support\ bsc6900_cfg_bak.txt on the OMU_A in the case of other upgradesAutomatically backed up by the upgrade tool.

Current running information, including the CN information, board version information, and cell informationremoteclient\Report\[NE Name]\ Preparation_MMLReport.txt on the upgrade client1. Automatically backed up by the upgrade tool2. The upgrade report displays the progress.

Current routing informationremoteclient\Report\[NE Name]\ Preparation_RouteInfo.txt on the upgrade client1. Automatically backed up by the upgrade tool2. The upgrade report displays the progress.

Certificate files[OMU_RootPath]\upgrade\[New Version]\support\ cert on the OMU_AAutomatically backed up by the upgrade tool

7.3 Items of the Automatic Check

Table 7-9 Items automatically checked during the upgrade

Check ItemCriterionRemarks

Version of the OMU Ethernet adapter driverIf the OMU is installed with the Suse Linux 9.3 operating system, intel e1000 Ethernet adapter 7.2.7-NAPI driver, and SAS hardware 3.02.62 driver, the upgrade client prompts the user to upgrade the OMU Ethernet adapter driver.-

Default gateway configurationThe default gateway configuration is correct.-

Current user authorityOnly user admin or root has the authority for the OMU operating system.-

Computer name of the OMUThe computer name of the OMU collected by the upgrade client is consistent with that of the OMU in use.-

IP address of the OMUThe IP address of OMU collected by the upgrade client is consistent with the one currently being used.-

License filesIf a new license is selected, the new license file must be saved to [OMU_RootPath]\upgrade\[New Version]\upgrade\.Except for patch installation.

File of data upgrade ruleThe file of rule for upgrading the current version to the target version is available.-

BSC network configurationThe internal and external Ethernet adapters are configured correctly.

1. The external Ethernet port is bond1, the OMU internal Ethernet port is bond0.1, and the GBAM internal Ethernet port is bond0. Moreover, the external Ethernet port is connected to the internal Ethernet port properly.

2. The BSC6000 network configuration file is backed up.

3. The network configuration file for the V900R012C01 or later versions is generated.This item should be checked only in the case of upgrade from the BSC6000 to the V900R012C01.

Database synchronizationThe data synchronization is normal in dual-OMU mode.This item need not be checked in the case of upgrade from the BSC6000 to the V900R012C01.

Operating status of boardsNo board is faulty.

If any board is faulty, the upgrade client prompts the user to rectify the fault.This item need not be checked in the case of upgrade from the BSC6000 to the V900R012C01.

Disk space on the OMUThe free disk space takes more than 15% of the total disk space. The free space of the hard disk where the OMU is installed is not less than 2.5 GB, and the free space of the system disk is not less than 2 GB.

7.4 List of BSC6900 OMU Ports that Are Not Enabled on the BSC6000 or BSC6810 OMUTable 7-10 List of BSC6900 OMU ports that are not enabled on the BSC6000 OMUPort No.Service ProcessDescriptionNetwork Protocol TypeNetwork Segment (External Network)

20FTP Server dataHost loading/uploading and downloading of software and logs (in active mode)TCPY

80Web LMTPort for local maintenance and browser connectionThis port is connected to the LMT for maintenance.TCPY

6006ems_gatePort for maintenanceTCPY

8000ems_gatePort for maintenance (SSL encryption)TCPY

8001ems_gatePort for alarm console (SSL encryption)TCPY

8006ems_gatePort for maintenance (SSL encryption)TCPY

8088Tool for remote upgradeTool for remote upgrade (SSL encryption)TCPY

8099ems_gateSynchronizing the OMU data with the M2000 data (SSL encryption)TCPY

8100ems_gateAlarm box (SSL encryption)TCPY

11775monitorDual-OMUUDPY

16002ems_gatePort through which the performance module reports notification messagesTCPY

18002ems_gatePort through which the performance module reports notification messages (SSL encryption)TCPY

Others (reserved)Host loading/uploading and downloading of software and logs (in active mode)--

Table 7-11 List of BSC6900 OMU ports that are not enabled on the BSC6810 OMUPort No.Service ProcessDescriptionNetwork Protocol TypeNetwork Segment (External Network)

22SSHD (operating system service)SSH port for remotely logging in to the OMUa boardTCPY

80Web LMTPort for local maintenance and browser connectionThis port is connected to the LMT for maintenance.TCPY

8088Tool for remote upgradeTool for remote upgrade (SSL encryption)TCPY

Others (reserved)Host loading/uploading and downloading of software and logs (in active mode)--

6-2Huawei Proprietary and Confidential Copyright Huawei Technologies Co., LtdIssue 02 (2010-07-30))

_1338384689.vsdPrepare for upgrade

Start the upgrade client

Configure the basic information about the upgrade

Perform pre-upgrade

Start

End

Perform upgrade

Verify whether the upgrade is successful

Yes

Perform version rollback

No

See section 4.1

Perform post-upgrade processings

See chapter 3

See section 4.2

See section 4.3

See section 4.4

See chapter 5

See chapter 7

See chapter 6