OptiX RTN 900 Radio Transmission System

V100R008C10SPH301
Patch Upgrade Guide

Issue 01

Date 2017-07-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2017. 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 contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.

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
1 
 Change History

Issue  Date  Author  Description 

01 2017-07-30 Zhang Qifu This is the first official release.
2 
 Contents

Change History ii
1 Before You Start 1
1.1 Upgrade Notes for Versions 1
1.2 Upgrade Method Introduction 1
1.3 Precautions 1

2 Upgrade Process Overview 3

2.1 Upgrade Flowchart 3

3 Preparing for the Upgrade 5

3.1 Pre-upgrade Checklist 5
3.2 Obtaining Upgrade Reference Documents 6
3.3 Obtaining Upgrade Tools 7
3.4 Obtaining the Required Software 7
3.5 Querying Version Information 8
3.6 Checking the Running Status of an NE 10
3.7 Backing Up NE Data 10
3.8 Configuring a DC Login User 13
3.9 Setting FTP/SFTP Parameters on the NMS Integrated with the DC 16

4 Performing the Upgrade 20

4.1 Creating a Hot Patch Package Loading Task 20
4.2 Running the Hot Patch Package Loading Task 26

5 Verifying the Upgrade 29

5.1 Verification Checklist 29
5.2 Checking Software Versions 29
5.3 Checking the Status of Services 30

6 Rolling Back to the Source Version 31

6.1 Rollback Process 31
6.2 Rolling Back to the Source Version 32
6.3 Verifying the Version Rollback 33
6.3.1 Checking Patch Information 34
6.3.2 Verifying Services on the NE 34

7 Deleting a Patch 36
7.1 Patch Deletion Process 36
7.2 Deleting a Patch 37
7.3 Verifying the Patch Deletion 38
7.3.1 Checking Patch Information 38
7.3.2 Verifying Services on the NE 40

8 FAQs 41
8.1 Failure to Load a Hot Patch Package 41

A Upgrade Record 42
B Product Feature 43
C Acronyms and Abbreviations 44
 3  Before You Start 

3.1  Upgrade Notes for Versions 

Table 3-1 Upgrade paths
Upgrade from…  To… 
V100R008C10SPC300 V100R008C10SPH301

 
An NE whose version is earlier than V100R008C10SPC300 must be upgraded to V100R008C10SPC300 and then to V100R008C10SPH301.
For details, see ​OptiX RTN 900 V100R008C10SPC300 Upgrade Guide​.

3.2  Upgrade Method Introduction 

This document describes the hot patch loading method for an upgrade.
A hot patch upgrade is an efficient software upgrade method. With this method, you can replace the running software with the proper
software without interrupting services.
Hot patches are available in board-level hot patches and hot patch packages. A board-level hot patch applies to a system control board or a
service board. A hot patch package, as a logical package composed of board-level hot patches and the patch package
description file (​*.pkg​​ file), applies to all boards on an NE.
OptiX RTN 900 V100R008C10SPC300 supports hot patch package loading.

3.3  Precautions 
Before you install the patch, read the ​OptiX RTN 905 V100R008C10SPH301 Patch Release Notes,​ ​OptiX RTN 910A V100R008C10SPH301
Patch Release Notes,​ ​OptiX RTN 950 V100R008C10SPH301 Patch Release Notes​, ​OptiX RTN 950A
V100R008C10SPH301 Patch Release Note​s, ​OptiX RTN 980 V100R008C10SPH301 Patch Release Notes​ , and​ OptiX
RTN 980L V100R008C10SPH301 Patch Release Notes​ to know the basic patch information, impact of the installation,
and updates on version mappings.
 4  Upgrade Process Overview

4.1  Upgrade Flowchart 

This section provides an upgrade flowchart.

Figure 4-1 Upgrade flowchart

Table 2-1 provides the upgrade schedule in the form of a table.

Table 4-1 Upgrade schedule

No.  Step  Impact  Time  Mandatory 
Required  or Optional 
1 Prepare for the upgrade. None 30–60 minutes Mandatory
2 Perform the Create a hot None 1–3 minutes Mandatory
upgrade. patch
package
loading task.
Run the hot None 3–5 minutes Mandatory
 patch
package
loading task.
3 Verify the upgrade. Verify whether 10–20 minutes Mandatory
the upgrade is
successful.
 5  Preparing for the Upgrade 

5.1  Pre-upgrade Checklist 

Table 3-1 lists the items to be verified before you start patch installation.

Table 5-1 Pre-upgrade checklist

Start  Item  Check Criteria  Expected  Time 
Time  Result  Required 
One Obtaining upgrade For details, see section 3.2 24 hours
week reference "Obtaining Upgrade
before documents Reference Documents."
the Obtaining upgrade For details, see section3.3 3 hours
upgrade tools Obtaining Upgrade Tools."
Obtaining the For details, see section 3.4 12 minutes
required software "Obtaining the Required
Software."
Three Querying version For details, see section 3.5 24 hours
days information "Querying Version
before Information."
the Checking the For details, see section 3.6 24 hours
upgrade running status of an "Checking the Running
NE Status of an NE."
Backing up NE data For details, see section 3.7 24 hours
"Backing Up NE Data."
Configuring a DC For details, see section 3.8 10 minutes
login user "Configuring a DC Login
User."
Setting FTP/SFTP For details, see section 3.9 10 minutes
parameter on the "Setting FTP/SFTP
NMS integrated Parameters on the NMS
with the DC Integrated with the DC."

5.2  Obtaining Upgrade Reference Documents 

Description 
This section describes how to obtain the reference documents for the upgrade.

Table 5-1 Reference documents

NE to Be Upgraded  Reference Document 

RTN 905 OptiX RTN 905 V100R008C10SPH301 Patch Release Notes

 OptiX RTN 905 Version Mapping Table_V100R008C10SPH301

RTN 910A OptiX RTN 910A V100R008C10SPH301 Patch Release Notes

OptiX RTN 910A Version Mapping

Table_V100R008C10SPH301

RTN 950 OptiX RTN 950 V100R008C10SPH301 Patch Release Notes

OptiX RTN 950 Version Mapping Table_V100R008C10SPH301

RTN 950A OptiX RTN 950A V100R008C10SPH301 Patch Release Notes

OptiX RTN 950A Version Mapping

Table_V100R008C10SPH301

RTN 980 OptiX RTN 980 V100R008C10SPH301 Patch Release Notes

OptiX RTN 980 Version Mapping Table_V100R008C10SPH301

RTN 980L OptiX RTN 980L V100R008C10SPH301 Patch Release Notes

OptiX RTN 980L Version Mapping

Table_V100R008C10SPH301

Precautions 
Ensure that the correct versions of reference documents listed in Table 3-2 are obtained.

Procedure 
Contact Huawei technical support engineers to obtain the above-mentioned documents.

Result Verification 
The version specified in the documents is the same as the target version for the upgrade.

5.3  Obtaining Upgrade Tools 

Description 
Obtain the necessary tools for the upgrade.

Precautions 
Ensure that the upgrade tool listed in Table 3-3 is available.

Table 5-1 Upgrade tool

Software  Version  Remarks 

iManager U2000 V200R015C60 or later None

Procedure 
Step 1 Prepare standard network cables.
Step 2 Set the IP address of the PC where the hot patch package is stored. It is recommended that the IP address of the PC be
unique and on the same network segment as the NE to be upgraded.
Step 3 Apply for and download the desired upgrade tool.
----End

Result Verification 
The required tool is available.

1.2  Obtaining the Required Software 

Description 
Obtain the software package of the target version.

Precautions 
If the U2000 server uses the Solaris operating system, upload the software package to the server in binary mode. Otherwise, the software
package may fail to be loaded. If the U2000 server uses another type of operating system, this issue does not exist.

Procedure 
Contact Huawei technical support engineers to obtain the software package for the target version. Ensure that the upgrade software version is
consistent with that in the release notes and version mapping table.

Result Verification 
The version of the hot patch package is the same as the target version for the upgrade.

1.3  Querying Version Information 

Description 
Verify that the version information about each board is correct.

Precautions 
None

Procedure 
Query the detailed information about each board on the NE by using the NMS.
Step 1 Choose ​Inventory > Physical Inventory​​ from the Main Menu.
 Step 2 In the ​Physical Inventory​​ window, select ​Board​​ from the P​hysical Inventory Type​​. On the ​Board List​​ tab page, select
All Records​​ from the drop-down list. Then, all the board records are displayed.

Step 3 Select the required board and click ​Query​​.

Step 4 Check the query result and verify that the software of each board to be upgraded is of the correct version.
----End

6  Result Verification 
The versions of the board software, FPGA file, and extended BIOS of all boards on the NE to be upgraded are the same as those specified in
Table 3-2 Reference documents.
1.4  Checking the Running Status of an NE 
Description 
Fully check the status of the NE to be upgraded and ensure that the NE runs properly.

Precautions 
During an upgrade, do not delete any files related to the hot patch package loading on the NE. Any deletion may cause unpredictable
abnormality.

Procedure 
Step 1 Select the required NE, right-click and choose ​Browse Current Alarms​​ from the shortcut menu. Ensure that current
alarms that will affect the upgrade are cleared.

----End

Result Verification 
The NE does not report a PATCH_PKGERR alarm.

1.5  Backing Up NE Data 

Description 
Back up data before the upgrade.
  
Without data backup, the configuration data of the NE may be lost if a cold reset or power failure occurs on the NE within 30 minutes after
the upgrade.

Procedure 
Step 1 Choose ​Configuration > NE Configuration Data Management​​ from the Main Menu.

Step 2 In the​ NE Configuration Data Management​​ window, select the NE that requires data backup and click .
 Step 3 Click ​Back Up NE Data​​ at the bottom and choose ​Back Up Database to SCC​​ from the drop-down list.

Step 4 After the​ Confirm​​ dialog box is displayed, click ​OK​​.​ ​Then, the system starts backing up the NE data.

Step 5 In the​ Result​​ dialog box that is displayed, click ​Close​​.

Data backup will be finished about 5 minutes later.
----End

Result Verification 
NE data is backed up successfully, and no exception occurs.

1.6  Configuring a DC Login User 

Description 
Configure a DC login user, which is used to log in to NEs from the DC and to upgrade the NEs.

Precautions 
A DC login user must have the system-level right or higher.

Procedure 
Step 1 Choose ​Administration​​ > ​NE Security Management​​ > ​NE Login Management​​ from the main menu.
Step 2 On the ​DC Login User Management ​page that is displayed, click the ​DC Login User Management​​ tab. If ​DC Login
User Management Table ​displays no NEs to be upgraded, add the NE to be upgraded by selecting it from ​Physical

Root​​ and click .

On the ​DC Login User Management​​ tab page, click ​Switch NE User​​.
 Step 3 In the ​Switch DC User​​ dialog box that is displayed, enter the user name and password of the NE in the ​User​​ and
Password​​ text boxes and click ​OK​​.

For a successful upgrade, the user must have the system-level right or higher.

Step 4 In the ​Result​​ dialog box that is displayed, click ​Close​​.

----End

Result Verification 
Step 1 Choose ​Administration​​ > ​NE Security Management​​ > ​NE User Management​​ from the main menu.

Step 2 Select the NE to be queried and click .

Step 3 In the ​Result​​ dialog box that is displayed, click ​Close​​.

 Step 4 On the ​NE User Management​​ page, click ​Query​​ to query the user levels of the NE.

The user level of the newly configured DC login user is ​Debug Level​​, a level higher than the system level
----End

1.2  Setting FTP/SFTP Parameters on the NMS Integrated with the DC 
Description 
Set FTP/SFTP parameters on the NMS integrated with the DC.

Precautions 
The FTP/SFTP service on the NMS server must be started.

Procedure 
Step 1 Log in to the NMS and choose ​Administration​​ > ​NE Software Management​​ > ​FTP Settings​​ from the main menu.
Step 2 In the ​FTP Settings​​ dialog box, click the ​System Information​​ tab.
● If only one NIC is configured on the NMS server, click ​Single NIC Configuration​​, set ​System IP Address​​ and
NAT IP​​, and then click ​Apply​​.
 ● If more than one NIC is configured on the NMS server, click ​Multiple NIC Configuration​​ and click ​Add​​. In the
Add System IP​​ dialog box that is displayed, set ​System IP Address​​ and ​NAT IP/Segment​​ and click ​OK​​. Verify
that the configured data is displayed in the list in the lower left of the ​System Information​​ tab page. Then, click
Apply​​.

Step 3 Click ​OK​​.

----End

Result Verification 
Step 1 Choose ​Administration​​ > ​Settings​​ > ​Load xFtp Settings​​ from the main menu.
Step 2 Check whether the FTP/SFTP service is available.
● If FTP is used, click ​Test FTP​​.
● If SFTP is used, click ​Test SFTP​​.
  

Ensure that ​Home Directory​​ is set to ​D:​​ and all software required for the upgrade is copied to the directory.

Step 3 The following message is displayed in the ​Information​​ dialog box, indicating that the FTP/SFTP service is available.

Step 4 In the ​Information​​ dialog box, click ​OK​​. Then, click ​OK​​ in the ​Load xFTP Information​​ dialog box.
----End
 2  Performing the Upgrade

 
● Before an upgrade, wait at least 30 minutes after the last configuration command is issued. Otherwise, you must back
up the NE data before an upgrade. For details, see section 3.7 Backing Up NE Data."
● During an upgrade, do not reset or reseat a board and do not perform any operations related to database restoration.
Otherwise, exceptions may occur on the NE and the upgrade will fail.
● Before upgrading an NE configured with active and standby system control boards, ensure that the NE software
versions of the active and standby system control boards are the same. If the NE software versions of the active and
standby system control boards are different, the databases of the active and standby system control boards cannot be
synchronized and services are delivered incorrectly during package loading. As a result, the upgrade will fail.
● Before upgrading an NE, ensure that the NE runs properly.
● Upgrade operations for NEs configured with active and standby system control boards are the same as those for NEs
configured with one system control board.

2.1  Creating a Hot Patch Package Loading Task 

Procedure 
Step 1 Choose ​Administration > NE Software Management > NE Upgrade Task Management ​from the Main Menu.

Step 2 In the ​NE Upgrade Task Management​​ window, click ​New Task​​ and choose ​Patch Update Task​​ from the drop-down
list.
Step 3 In the ​Create Task [Patch Update]​​ dialog box, set ​NE Type​​ and ​NE Version​​.
● NE Type​​: indicates the type of NE.
● NE Version:​​ indicates the version of NE. Select the version of the NE to be upgraded.

Step 4 Select the NE to be upgraded (checked in the following figure). Then, ​NE Table​​ in the right pane lists the NE to be
upgraded. Click ​Next​​.
 Step 5 (Optional) Configure operations that require your manual confirmation.

 
If you select ​Pause Before Current Operation​​ for an operation, the upgrade task pauses before the operation and requires your permission
to proceed. If you do not select ​Pause Before Current Operation​​ for any operation, the task proceeds automatically
until it is completed.

Step 6 (Mandatory) Configure the patches to be loaded.

1. In the ​Operation Configuration [Patch Update]​​ dialog box, select ​Load Patch​​ and then click ​Select Patches To
Load​​.
 Step 7 (Mandatory) Configure the patch activation operation.
In the ​Operation Configuration [Patch Update] ​dialog box, select ​Activate Patch​​.

Step 8 (Optional) Configure the confirm operation.

In the ​Operation Configuration [Patch Update] ​dialog box, select ​Confirm​​.
  
It is recommended that you confirm the patches immediately after activating them. If you do not confirm the patches and the NE is reset
within 24 hours after the patches are activated, the patches will not take effect. In this case, patches may fail to be
re-activated, and you need to re-try patch activation. If the NE works properly within 24 hours after the patches are
activated, the patches will be confirmed and take effect automatically.

Step 9 In the ​Operation Configuration [Patch Update]​​ dialog box, click ​Next.

Step 10 In the ​Confirmation [Patch Update]​​ dialog box, confirm the information about the hot patch package loading task and
click ​OK​​.

----End

2.2  Running the Hot Patch Package Loading Task 

Step 1 In the ​NE Upgrade Task Management ​window, right-click the desired upgrade task and choose ​Start Task​​ from the
shortcut menu. Alternatively, select the required upgrade task and click the ​Start Task ​button.
The hot patch package loading task starts.
Step 2 View the operating status and progress of the task in the upper right pane. View the status and result of each package
loading operation in the lower right pane.

Step 3 If an operation pauses during the upgrade, perform the following operations:
1. Check whether the patch package loading task is normal. Right-click the upgrade task and choose ​Generate Report
from the shortcut menu. Alternatively, select the upgrade task and click the ​Generate Report​​ button.

2. In the ​Generate Task(s) Report​​ dialog box, specify a file path for storing the generated report and click ​OK​​.
 3. Open the report and check the status of package loading.

4. If the patch package loading task is normal, right-click the upgrade task and choose ​Continue Task​​ from the
shortcut menu.

5. If the patch package loading task is abnormal, roll back the NE according to chapter 6 "Rolling Back to the Source
Version."

Step 4 Check whether the upgrade is successful. In the ​Operation Status​​ column, you can see whether the upgrade task is
successful. Alternatively, export the task report as described in Step 3 and check the details of the upgrade task.
----End
 3  Verifying the Upgrade 

3.1  Verification Checklist 

This chapter describes how to verify the upgrade.

Table 3-1 Verification checklist

No.  Item   Expected Result  
1 Checking the The software versions meet the requirements specified in
versions of the NE the version mapping table.
software and the The current software versions are consistent with the target
board software versions.
2 Checking the status All services run properly.
of services

Print and fill in the form attached in A "Upgrade Record."

3.2  Checking Software Versions 

Description 
Verify that software versions are correct after the upgrade.

Procedure 
Step 1 Download the version mapping table of the current version from ​http://support.huawei.com​ according to section 3.2
Obtaining Upgrade Reference Documents.
Step 2 Query the versions of the NE software and the board software according to section 3.5 "Querying Version Information."
Step 3 Check whether the queried software versions meet the requirements specified in the version mapping table.
----End

Result Verification 
The target software versions meet the requirements specified in the version mapping table.

3.3  Checking the Status of Services 

Description 
Verify that services run properly after the upgrade.
Procedure 
Step 1 Check the running status of the NE. For details, see section 3.6 "Checking the Running Status of an NE."
Step 2 Check with the customer whether services are running properly after the upgrade.
----End

Result Verification 
None
 4  Rolling Back to the Source Version 

4.1  Rollback Process 

If the patch package upgrade task is abnormal, roll back the NE version.

Figure 4-1 Rollback flowchart

Table 4-1 Rollback procedure

No.  Step  Impact  Time Required  Mandatory or Optional 
1 Roll back to the None 20-120 seconds Mandatory
source version.
2 Verify the rollback. None 1–2 minutes Mandatory

4.2  Rolling Back to the Source Version 

Precautions 
A rollback can be performed only when the hot patch is activated but not committed.
Procedure 
Step 1 On the ​NE Data Backup/Restoration​​ tab page, right-click a desired NE and choose ​Rollback Patch​​ from the shortcut
menu.

Step 2 Click ​Yes​​ in the ​Operation Confirmation​​ dialog box.

Step 3 After the NE version is rolled back, the ​Operation Status​​ of the NE is ​Rollback Patch: Succeeded in rolling back the
patch​​.

Step 4 On the ​NE Upgrade Task Management​​ tab page, right-click the upgrade task for which a version rollback is performed
and choose ​Delete Task​​ from the shortcut menu.

Step 5 Click ​Yes​​ in the ​Delete Confirmation​​ dialog box.

----End

4.3  Verifying the Version Rollback 

Table 4-1 Version rollback checklist
No.  Item   Check Criteria   Expected Result 
1 Checking patch For details, see section6.3.1 No patch is available.
information Checking Patch Information."
2 Verifying services For details, see section 6.3.2 The NE and services
on the NE "Verifying Services on the NE." are running properly.

1.1.1 Checking Patch Information 

Procedure 
Step 1 On the ​NE Data Backup/Restoration​​ tab page, right-click a desired NE and choose ​Get Patch​​ from the shortcut menu.

Step 2 Wait till the progress in the ​Get Patches​​ dialog box reaches 100% and then click ​Details​​.
The ​Operation Result​​ column shows ​No patch is available for the current equipment​​.
----End

1.1.2 Verifying Services on the NE 

Procedure 
Step 1 Check the NE running status. For details, see section 3.6 "Checking the Running Status of an NE."
Step 2 Check with the customer whether services on the NE are normal after the version rollback.
----End
 2  Deleting a Patch

2.1  Patch Deletion Process 

Figure 2-1 Patch deletion flowchart

Table 2-1
 Procedure for deleting a patch
No.  Step  Impact  Duration  Required 
or 
Optional 
1 Delete a patch. None 20s to 120s Required
2 Verify the patch deletion. None 1 minute to 2 Required
minutes

2.2  Deleting a Patch 

Precautions 
You can delete a hot patch only after it has been committed.

Procedure 
Step 1 On the ​NE Data Backup/Restoration​​ tab page, right-click a desired NE and choose ​Get Patch​​ from the shortcut menu.

Step 2 In ​Patch View​​,​ ​select the patch, right-click, and choose ​Delete​​ from the shortcut menu. In the displayed ​Confirm Patch
Operation​​ dialog box, click ​Yes​​.

----End
2.3  Verifying the Patch Deletion 
Table 2-1 Patch deletion checklist
No.  Item   Check Criteria   Expected Result 
1 Checking patch For details, see section 7.3.1 No patch is available.
information Checking Patch Information
2 Verifying services For details, see section 7.3.2 The NE and services
on the NE Verifying Services on the NE are running properly.

1.1.1 Checking Patch Information 

Procedure 
Step 1 On the ​NE Data Backup/Restoration​​ tab page, right-click a desired NE and choose ​Get Patch​​ from the shortcut menu.

Step 2 Wait till the progress in the ​Get Patches​​ dialog box reaches 100% and then click ​Details​​.
The ​Operation Result​​ column shows ​No patch is available for the current equipment​​.
----End

1.1.2 Verifying Services on the NE 

Procedure 
Step 1 Check the NE running status. For details, see section 3.6 "Checking the Running Status of an NE."
Step 2 Check with the customer whether services on the NE are normal after the patch deletion.
----End
 2  FAQs

2.1  Failure to Load a Hot Patch Package 

Q: If a hot patch package fails to be loaded, what are the possible causes and corresponding handling methods?
A: The possible causes are the source version of the hot patch package is incorrect and the DC version is incorrect and the communication
between the DC and NEs are interrupted. To resolve this issue, verify that the source version of the hot patch package is
correct before an upgrade, use the DC of a matching version or later version for an upgrade or re-try hot patch load.
 A  Upgrade Record

Site Name Upgrade Date

Source Version Target Version
Operator Operator from the customer:
Operator from Huawei:
Whether the Upgrade Is
Successful
Checklist for the Upgrade  Conclusion  Problem Handling 
Checklist Before the
Upgrade

Checklist During the

Upgrade

Checklist After the

Upgrade
 B  Product Feature

For details, see the ​OptiX RTN 905 V100R008C10SPC300 Release Notes,​ ​ OptiX RTN 910A V100R008C10SPC300 Release Notes,​ ​ OptiX
RTN 950 V100R008C10SPC300 Release Notes​, ​OptiX RTN 950A V100R008C10SPC300 Release Notes​, ​OptiX RTN 980
V100R008C10SPC300 Release Notes,​ ​ a​ nd ​OptiX RTN 980L V100R008C10SPC300 Release Notes.
 C  Acronyms and Abbreviations 

Acronym/Abbreviation Full Name

DC Data Center
FPGA field programmable gate array
RTN radio transmission node