OptiX RTN 900 V100R003C03SPC201 Upgrade Guide-Package Loading Method

OptiX RTN 900 Radio Transmission System
V100R003C03SPC201
Upgrade Guide-Package
Loading Method
Issue
01
Date
2012-08-06
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2012. 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
Issue 01 2012-08-06
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd

Upgrade Guide-Package Loading Method
GUI Conventions
The general conventions that may be found in this document are defined as follows:
Conventio
n
Description
Boldface
Window, dialog box, tab names, menu, buttons, icons, and parameters are
in boldface. For example, the New User window is displayed. Click the
OK button.
Boldface Italic
The boldface italic words used in this document refer to the commands
that should be entered by the user during the upgrade.
>
Menus are separated by the ">" sign. For example, choose File > Create
> Folder.
Courier New
The displayed information and sessions are in Courier New.
Change History
Issue 01 2012-08-06
Issu
e
Details
Date
Prepared by
Approved by
01
Completed the initial

draft.
2012-05-15
Li Yong
Tao Yin

ii

1 Before You Start
Contents
1 Before You Start...........................................................................3
1.1 Method Introduction..........................................................................................................................................3
1.2 Package Loading Method..................................................................................................................................3
1.3 Upgrade Path......................................................................................................................................................4
1.4 Impact of the Upgrade.......................................................................................................................................6
1.4.1 Impact on the System During the Upgrade..............................................................................................6
1.4.2 Impact on the System After the Upgrade..................................................................................................6
2 Upgrade Process Overview............................................................7

2.1 Upgrade Flowchart............................................................................................................................................7
2.2 Upgrade Schedule..............................................................................................................................................8
3 Preparing for the Upgrade...........................................................10

3.1 Environment Preparations................................................................................................................................10
3.1.1 Obtaining Upgrade Tools........................................................................................................................10
3.1.2 Obtaining Upgrade Reference Documents.............................................................................................11
3.1.3 Obtaining the Required Software...........................................................................................................11
3.2 Manual Check Before an Upgrade...................................................................................................................12
3.2.1 Querying the Hardware/Software Version..............................................................................................12
3.2.2 Backing Up the NE Data........................................................................................................................14
3.2.3 Checking the Running Status of an NE..................................................................................................17
3.2.4 Configuring a DC Login User................................................................................................................19
3.3 Checking Service Protection............................................................................................................................24
3.4 Setting FTP/SFTP Parameters on the NMS Integrated with the DC...............................................................24
4 Performing the Upgrade..............................................................27

4.1 Creating an Upgrade Task................................................................................................................................27
4.1.1 Creating a Package Upgrade Task..........................................................................................................27
4.1.2 Creating a Package Diffusion Upgrade Task..........................................................................................40
4.2 Running the Package Loading Task.................................................................................................................53
5 Verifying the Upgrade.................................................................60

5.1 Verification Checklist.......................................................................................................................................60
5.2 Checking Software Versions............................................................................................................................60
5.3 Checking the Status of Services.......................................................................................................................61
Issue 01 2012-08-06


1 Before You Start
5.4 Checking Licenses...........................................................................................................................................61
6 Rolling Back to the Source Version...............................................62

6.1 Version Rollback Flowchart.............................................................................................................................62
6.2 Rollback Procedure..........................................................................................................................................62
6.3 Verifying a Version Rollback...........................................................................................................................64
7 Troubleshooting..........................................................................65
7.1 Exception 1......................................................................................................................................................65
7.2 Exception 2......................................................................................................................................................65
7.3 Exception 3......................................................................................................................................................66
7.4 Exception 4......................................................................................................................................................66
7.5 Exception 5......................................................................................................................................................66
7.6 Exception 6......................................................................................................................................................66
7.7 Exception 7......................................................................................................................................................67
7.8 Exception 8......................................................................................................................................................67
7.9 Exception 9......................................................................................................................................................68
7.10 Exception 10..................................................................................................................................................68
7.11 Exception 11...................................................................................................................................................68
7.12 Exception 12..................................................................................................................................................69
7.13 Exception 13..................................................................................................................................................69
7.14 Exception 14..................................................................................................................................................69
7.15 Exception 15..................................................................................................................................................70
7.16 Exception 16..................................................................................................................................................70
A Upgrade Record..........................................................................71
B Product Features........................................................................72
C Acronyms and Abbreviations.......................................................73
D Glossary..................................................................................... 74
Issue 01 2012-08-06


1 Before You Start
Before You Start
1.1 Method Introduction

This document describes how to upgrade the OptiX RTN 900 by using the package loading
method.
The package loading method is available in two modes: package upgrade mode and package
diffusion upgrade mode. Choose either mode according to network conditions. Figure 1.1
compares the two modes.
Figure 1.1 Comparison of package upgrade and package diffusion upgrade
Concept
Comparison
Applicable
Scope
Upgrade mode 1
Package upgrade
Higher reliability,
lower efficiency
Upgrade of a single
NE or multiple NEs
Upgrade mode 2
Package diffusion
upgrade
Higher efficiency,
lower reliability
Upgrade of multiple
NEs
1.2 Package Loading Method

The package loading method allows all the software of an NE to be upgraded using one
software package. In practice, you only need to load the software package to an NE and do
not need to consider the individual boards or specific software that needs to be upgraded.
After you install a board on an NE, the corresponding software files in the software package
are automatically distributed to the board.
Issue 01 2012-08-06


1 Before You Start
1.3 Upgrade Path

This document applies only to the upgrade of the OptiX RTN 900 toV100R003C03SPC201.
If an upgrade from V100R002C00SPC100 to V100R003C03SPC201 fails, you can roll

back the software version to V100R002C00SPC100. If the V100R003C03SPC201 version
needs to be downgraded, however, it cannot be downgraded to V100R002C00SPC100.
When the V100R003C03SPC201 is separately downgraded to the V100R003C00SPC100
or an earlier version, a cold reset on the NE needs to be performed on the NE.
If an NE fails to be upgraded from a source version listed in the following table to

V100R003C03SPC201, roll back the NE to the source version. After the version rollback,
perform operations in 7.15"Exception 15". For an NE that houses two SCC boards,
manually cold reset the NE after you downgrade the NE from V100R003C03SPC201 to a
source version (except for V100R003C02 and V100R003C02SPC100) listed in the
following table.
An OptiX RTN 900 V100R003C03SPC201 NE that is connected to the DC through

microwave links cannot be downgraded remotely using the DC.
Source Version
Target
Version
Upgrade Method
V100R002C00SPC100
V100R003C03SPC
201
Package loading upgrade
V100R003C03SPC
201
V100R003C03SPC
201
V100R003C03SPC
201
V100R003C03SPC
201
V100R003C03SPC
201
V100R003C03SPC
201
V100R003C03SPC
201
V100R002C00SPC200
V100R002C00SPH101
V100R002C00SPH102
V100R002C00SPH103
V100R002C00SPH201
V100R002C01
V100R002C02SPC100
Issue 01 2012-08-06
Package diffusion upgrade



V100R002C02SPC200
V100R003C00SPC100
V100R003C02
V100R003C02SPC100
V100R003C03SPC100
V100R003C03SPC200
1 Before You Start
V100R003C03SPC
201
V100R003C03SPC
201
V100R003C03SPC
201
V100R003C03SPC
201
V100R003C03SPC
201
V100R003C03SPC
201

A proper upgrade method can be selected from the preceding methods according to the source
software version of the NE.
Issue 01 2012-08-06


1 Before You Start
1.4 Impact of the Upgrade

To upgrade an earlier software version to V100R003C03SPC201, read this chapter carefully
to understand the possible impact of the upgrade on the system.
1.4.1 Impact on the System During the Upgrade

Impact on Services
For upgrading the NE software, the NE needs to be warm reset. During the resetting,
DCN communication is interrupted but services are available. If LAG is configured,
however, the services will be interrupted.
For upgrading the board software on a data board, the data board needs to be warm reset.
During the resetting, DCN communication is interrupted but services are available.
For upgrading the IF board ISU2 or ISX2, the IF board needs to be warm reset. During
the resetting, DCN communication is interrupted but services are available.
For upgrading the FPGA on the SCC board, the NE needs to be cold reset. During the
resetting, DCN communication is interrupted and services are unavailable.
For upgrading the FPGA on other boards, the corresponding boards need to be cold reset.
During the resetting, DCN communication is interrupted and services on the boards are
unavailable.
Impact on Network Communications

For details about the impact of updated files on DCN communications in the activation
period, see "Impact on Services" in section 1.4.1"Impact on the System During the Upgrade."
1.4.2 Impact on the System After the Upgrade

None
Issue 01 2012-08-06


2 Upgrade Process Overview
Upgrade Process Overview
2.1 Upgrade Flowchart

Figure 1.1 Upgrade flowchart
Issue 01 2012-08-06


2.2 Upgrade Schedule

Figure 1.1 Upgrade schedule
No.
Procedure
Impact
Time
Required
Mandatory
or Optional
Preparing for the upgrade
None
30 to 60 minutes
Mandatory
Performing
the upgrade
Selecting package upgrade or

package diffusion upgrade
None
1 to 2 minutes
Mandatory
Total duration of upgrade

process
30 to 65 minutes
Creating a
package
loading task
Pre-upgrade
check
None
5 to 10 seconds
Optional
Backing up
the data
None
1 to 5 seconds
Optional
Loading the
software
None
30 to 60 seconds
Mandatory
Distributing
the software
None
1 to 5 seconds
Mandatory
Activating
the software
See section
1.4.1"Impact
on the
System
During the
Upgrade."
5 to 10 seconds
Mandatory
Post-upgrade
check
None
5 to 10 seconds
Optional
Committing
the software
None
1 to 5 seconds
Mandatory
Pre-upgrade
check
None
10 seconds to 1
minute
Optional
Backing up
the data
None
Within 1 minute
Optional
Loading the
software
None
12 to 17 minutes
Mandatory
Distributing
the software
None
5 seconds to 10
minutes
Mandatory
Activating
the software
See section
1.4.1"Impact
on the
System
During the
Upgrade."
7 to 20 minutes
Mandatory
Running the
package
loading task
Issue 01 2012-08-06


No.
Procedure
Impact
Time
Required
Mandatory
or Optional
Post-upgrade
check
None
Within 1 minute
Optional
Committing
the software
None
3 to 7 minutes
Mandatory
Upgrade verification
None
10 to 20 minutes
Mandatory
Version rollback upon an upgrade failure
Same as the
impact of an
upgrade
30 to 65 minutes
Optional
Issue 01 2012-08-06


3 Preparing for the Upgrade
Preparing for the Upgrade
3.1 Environment Preparations

3.1.1 Obtaining Upgrade Tools
Description
Obtain the necessary tools for the upgrade.
Precautions
Ensure that the upgrade tools listed in Figure 1.1 are available.
Figure 1.1 Upgrade tools
Software
Version
Remarks
iManager U2000
V100R006C00SPC300 and later versions
None
License tool
RTN License Tool V1.1.0
None
Procedure
Step 1 Prepare standard network cables.
Step 2 Set the IP address of the PC where the software package is stored. If the PC and the to-beupgraded NE are not connected by a router, ensure that the IP address of the PC is unique and
on the same network segment as the to-be-upgraded NE.
Step 3 Apply for and download the required upgrade tools.
----End
Verification Result
All the required tools are available.
Issue 01 2012-08-06

10

3.1.2 Obtaining Upgrade Reference Documents

Description
Obtain the reference documents listed in Figure 1.1.
Figure 1.1 Reference documents
NE to Be
Upgraded
Reference Document
RTN 910
OptiX RTN 910 V100R003C03SPC201 Release Notes

OptiX RTN 910 Version Mapping Table_V100R003C03SPC201
RTN 950

RTN 980

Precautions
The reference documents must be available.
Procedure
Obtain the required release documents by doing as follows:
Step 1 Log in to the website http://support.huawei.com by using your user name and password.
Step 2 Choose Support > Product catalog > Optical Network > Microwave, and then select
OptiX RTN 910, OptiX RTN 950, or OptiX RTN 980.
Step 3 Select the Release Documentation tab page, and download the required release documents.
----End
Verification Result
The version specified in the documents is the same as the target version for the upgrade.
3.1.3 Obtaining the Required Software

Description
Obtain the software package of the target version.
Issue 01 2012-08-06

11

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 operation system, this issue does not exist.
Procedure
Obtain the software package by doing as follows:
Step 1 Log in to the website http://support.huawei.com by using your user name and password.
Step 2 Choose Support > Software Center > Version Software > Optical Network Product Line
> Microwave, and then select OptiX RTN 910, OptiX RTN 950, or OptiX RTN 980.
Step 3 Download the software package of V100R003C03SPC201 and the desired license tool.
----End
Verification Result
The version of the software package is the same as the version specified in the version
mapping table.
3.2 Manual Check Before an Upgrade

Note that a manual check before an upgrade differs from a pre-upgrade check during upgrade
task creation, because the latter one is automatically run by the NE.
3.2.1 Querying the Hardware/Software Version

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.
Issue 01 2012-08-06

12

Step 2 In the Physical Inventory window, select Board from the Physical Inventory Type. In the
Board List tab, select All Records from the drop-down list. Then, all the board records are
displayed.
Issue 01 2012-08-06

13

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
Verification Result
The versions of the board software, FPGA file, and extended BIOS of the NE to be upgraded
are consistent.
3.2.2 Backing Up the NE Data
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.
Step 1 Choose Configuration > NE Configuration Data Management from the Main Menu.
Issue 01 2012-08-06

14

Step 2 In the NE Configuration Data Management window, select the NE that requires data
backup and click the red double arrow button
.
Step 3 Click Back Up NE Data at the bottom and choose Back Up Database to SCC from the
drop-down list.
Issue 01 2012-08-06

15

Step 4 After the Confirm dialog box is displayed, click OK. Then, the system starts backing up the
NE data.
Step 5 In the Operation Result dialog box that is displayed, click Close. Data backup will be
finished about 5 minutes later.
Issue 01 2012-08-06

16

----End
3.2.3 Checking the Running Status of an NE

Description
Fully check the running status of the NE to be upgraded and ensure that the NE runs in the
normal state.
Precautions
During an upgrade, do not delete any files related to the package loading or package
diffusion on the NE. Any deletion may cause unpredictable abnormality.
A cold reset on the SCC board causes service interruptions on all service boards; loading
an FPGA file onto a service board interrupts the services on the board. In such cases,
notify the customer of possible service interruptions ahead of the upgrade. Field
engineers are required to work out a detailed upgrade solution based on network
conditions to avoid service interruptions. Protection schemes can be configured to
minimize the impacts of an upgrade on services.
Before upgrading an NE to V100R003C03SPC201, ensure that the NE does not house

boards that are only supported by the V100R003C03SPC201 (such as EMS6 and SL1DA
boards).
Before upgrading an NE to V100R003C03SPC201, check whether ports of an

EM4T/EM4F/EM6X/EG2D board and those of an EM6T/EM6F/EM6FA/EM6TA board
are in the same LAG. If they are in the same LAG, delete the LAG. This will cause a
transient service interruption. If the LAG is in load-sharing mode, the link bandwidth
may be decreased due to the deletion. LAGs can be configured for ports on an
Issue 01 2012-08-06

17

EM4T/EM4F/EM6X/EG2D board or those on an EM6T/EM6F/EM6FA/EM6TA board

to reduce the impact of an upgrade on services.
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.
In order to avoid an upgrade failure, it is important to clear the following alarms (if they exist)
before an upgrade: COMMUN_FAIL, BUS_ERR, DBMS_ERROR,
DBMS_PROTECT_MODE, SYNC_FAIL, SYNC_DISABLE, MW_CFG_MISMATCH,
CFCARD_OFFLINE, CFCARD_FAILED, HARD_BAD, SWDL_AUTOMATCH_INH, and
BOOTROM_BAD. If certain alarms cannot be cleared, evaluate the impact of each alarm.
Step 2 Ensure that the DCN communication on the NE is normal. Especially, avoid any loop of DCN
communication.
Step 3 If the NE attributes are modified on the NMS side, click the Refresh button in the Main
Topology. After the NE attributes are updated, you can configure and execute an upgrade
task.
Issue 01 2012-08-06

18

----End
Verification Result
The NE does not report any alarm that will affect the upgrade; the DCN communication on
the NE is normal.
3.2.4 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
None
Procedure
Step 1 Choose Administration > NE Security Management > NE Login Management from the
main menu.
Issue 01 2012-08-06

19

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.
Issue 01 2012-08-06

20

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.
Issue 01 2012-08-06

21

Step 4 In the Result dialog box that is displayed, click Close.
----End
Result Verification
To verify that the configured DC login user has the system-level right or higher, perform the
following steps:
Step 1 Choose Administration > NE Security Management > NE User Management from the
main menu.
Issue 01 2012-08-06

22

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.
Issue 01 2012-08-06

23

The user level of the newly configured DC login user is Debug Level, a level higher than the
system level
----End
3.3 Checking Service Protection
For an OptiX RTN 910 NE or for an OptiX RTN 950 NE on which only one system control board is
configured, a cold reset of the system control board may cause an automatic cold reset of all the
service boards. As a result, the services are interrupted. Therefore, prepare a spare system control
board to provide board protection during the upgrade or inform the customer of the service
interruption in advance.
Unless otherwise specified, if a board is loaded with the FPGA file (.pga), the board is reset (cold)
when the FPGA file is activated.
In the case of an OptiX RTN 950 NE configured with two system control boards, the services are not
interrupted during the package loading if the .pga files of service boards are not updated. In this
case, if the .pga file of a service board is updated, the services on the service board are interrupted.
The most important part in an upgrade solution is protection schemes, which provide
protection for existing services during the upgrade. Conduct an analysis and determine the
protection scheme based on the specific network.
3.4 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.
Issue 01 2012-08-06
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.

24

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 In the FTP Settings dialog box, click the File Transfer Service Setting tab.
Step 2 Check whether the FTP/SFTP service is available.
Issue 01 2012-08-06

25

If FTP is used, click Test FTP.
If SFTP is used, click Test SFTP.
Ensure that File Transfer Service Root Directory is set to D: and all software required for the upgrade
is copied to the directory.
The following message is displayed in the Operation Result dialog box, indicating that the
FTP/SFTP service is available.
Step 3 In the Operation Result dialog box, click OK. Then, click OK in the FTP Settings dialog
box.
----End
Issue 01 2012-08-06

26

Issue 01 2012-08-06
4 Performing the Upgrade
Performing the Upgrade

27

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.2.2"Backing Up the NE Data."
During an upgrade, do not reset or reseat a board and do not perform any database
restoration operations. Otherwise, exceptions may occur on the NE and the upgrade will
fail.
During software activation, do not modify any configuration because the synchronization
between the active and standby system control boards is disabled automatically. If you
modify any configuration, a rollback will occur or the modifications will be lost.
Do not activate the NEs of a protection group at the same time; otherwise, the services
involved will be interrupted.
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.
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.
Perform a warm reset on the active SCC board after downgrading an NE with two SCC
boards. Otherwise, alarms that are not supposed to be reported may be reported.
Do not power off or remove the system control board within 10 minutes after the upgrade.
Otherwise, the DBMS_ERROR alarm may be reported.
4.1 Creating an Upgrade Task

4.1.1 Creating a Package Upgrade Task
Step 1 Choose Administration > NE Software Management > NE Upgrade Task Management
from the Main Menu.
If the NE attributes are modified on the NMS side, ensure that the DC-side data is updated
before configuring and executing an upgrade task.
Issue 01 2012-08-06

28

Step 2 In the NE Upgrade Task Management window, click New Task and choose Package
Upgrade/Downgrade Task from the drop-down list.
Step 3 In the Create Task [Package Upgrade] dialog box, set Task Type, NE Type, and NE
Version.
Issue 01 2012-08-06

29

Task Type: indicates an upgrade task or a downgrade task. When the target version is
later than the source version, you can only select Upgrade.
NE Type: indicates the type of the NE. You can select OptiX RTN 910, OptiX RTN
950, OptiX RTN 980, or All Type.
NE Version: indicates the version of the NE. Select the version of the NE to be
upgraded.
Step 4 Select the NE to be upgraded and click Query. After the selected NE is displayed in NE
Table, click Next.
Issue 01 2012-08-06

30

Step 5 (Optional) Configure the operations that require your manual confirmation.
For a complete upgrade task, it is recommended that the operations adopt the default settings of Pause
Before Current Operation. If Pause Before Current Operation is selected for an operation, the
system will require your manual confirmation before performing the operation.
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.
The OptiX RTN 900 V100R003C03SPC201 does not support customized packages, so do
not select Custom package.
In the Operation Configuration [Package Upgrade] dialog box, select Pause Before
Current Operation for the operations as required. It is recommended that you select Pause
Before Current Operation for the Activate and Commit operations.
Issue 01 2012-08-06

31

Step 6 (Optional) Configure the upgrade precheck.

1.
In the Operation Configuration [Package Upgrade] dialog box, select the Precheck
check box and click Configure Precheck Items.
2.
In the Configure Precheck Operation dialog box, select Alarm Check, Health Check,
and Extended Check according to specific needs. Then, click OK.
Issue 01 2012-08-06

32

If Extended Check is selected, you need to import the check items.
Step 7 (Optional) Configure the data backup operation.

1.
In the Operation Configuration [Package Upgrade] dialog box, select the Backup
check box, and click Configure Backup Information.
2.
In the Configure Backup Operation dialog box, ensure that the default value of
Content Type is Data File. Click OK.
Issue 01 2012-08-06

33

Step 8 (Mandatory) Configure the software files to be loaded.

1.
In the Operation Configuration [Package Upgrade] dialog box, select the Load
Package check box and click Configure Package.
The OptiX RTN 910 and RTN 950 products use the same software package, so either the OptiX RTN
910 software package or the OptiX RTN 950 software package can be selected.
2.
Issue 01 2012-08-06
In the Select Package File(s) dialog box, click

be loaded. Then, click OK.

to select the software package to
34

Issue 01 2012-08-06

35

By performing this step, you can copy the software package from the server to the NE, or more
specifically, to the CF card and the flash memory of the system control board.
After software loading is started, the SWDL_INPROCESS alarm is reported on the U2000. This
alarm clears after the software is committed.
Step 9 (Mandatory) Configure the software dispense operation.

In the Operation Configuration [Package Upgrade] dialog box, select the Dispense check
box.
Step 10 (Mandatory) Configure the software activation operation.
The software activation operation is to trigger a warm or cold reset on the system control
board or other boards. A cold reset will cause service interruptions.
You can configure activation groups based on network conditions to improve upgrade
efficiency. It is recommended that you configure one NE as an activation group.
If NEs that have service associations are configured as a protection group and are activated
at the same time, the related services will be interrupted. Therefore, you need to divide
such NEs in a protection group into different activation groups.
1.
Issue 01 2012-08-06
In the Operation Configuration [Package Upgrade] dialog box, select the Activate
check box and click Configure Activation.

36

2.
In the Configure Activation dialog box that is displayed, click Get Default Activation
and configure the activation operation based on the displayed default activation
information.
Activation Time: indicates the time to activate the software. The activation time for the first
activation group is configurable. Select the Activate Time check box, click
the activation time to a time later than the software loading time.
, and then set
: indicates creating an activation group. By default, one NE forms one activation group.
The NE in a group is activated only after the NE in the previous group is activated.
: indicates moving an NE to the next group. To move an NE, select the NE first.
: indicates moving an NE to the previous group. To move an NE, select the NE first.
: indicates expanding the current view.
: indicates collapsing the current view.
: indicates deleting an activation group. To delete a group, select the group first.
Step 11 (Optional) Configure the upgrade postcheck.
1.
Issue 01 2012-08-06
In the Operation Configuration [Package Upgrade] dialog box, select the Postcheck
check box and click Configure Postcheck Items.

37

2.
In the Configure Postcheck Operation dialog box, select Alarm Check and Health
Check according to specific needs. Then, click OK.
Step 12 (Mandatory) Configure the software commit operation.

In the Operation Configuration [Package Upgrade] dialog box, select the Commit check
box.
Issue 01 2012-08-06

38

If the commit operation fails to be performed within 30 minutes after the activation operation, the
SWDL_ACTIVATED_TIMEOUT alarm occurs. This alarm clears after the commit operation is
performed.
After the commit operation, check the current alarms. If the SWDL_COMMIT_FAIL alarm is
reported, the commit operation fails. Otherwise, the commit operation is successful.
Step 13 In the Operation Configuration [Package Upgrade] dialog box, click Next to complete the
configuration operations.
Issue 01 2012-08-06

39

Step 14 In the Confirmation [Package Upgrade] dialog box, click OK. The NE Upgrade Task
Management window is displayed.
Issue 01 2012-08-06

40

Step 15 In the NE Upgrade Task Management window, run the package upgrade task. For details,
see section 4.2"Running the Package Loading Task."
----End
4.1.2 Creating a Package Diffusion Upgrade Task
Create a gateway NE (GNE) before creating a package diffusion upgrade task.
If multiple NEs need to be activated at the same time, configure an activation group for the
NEs when you are creating a package diffusion upgrade task.
The OSI and L2DCN protocols do not support package diffusion, but the HWECC and IP
protocols do.
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 Package
Diffusion Upgrade/Downgrade Task from the drop-down list.
Issue 01 2012-08-06

41

Step 3 In the Create Task [Package Diffusion Upgrade] dialog box, set Task Type, NE Type and
NE Version. At least two NEs must be selected for a package diffusion upgrade task.
Task Type: indicates an upgrade task or a downgrade task. When the target version is
later than the source version, you can only select Upgrade.
NE Type: indicates the type of the NE. You can select OptiX RTN 910, OptiX RTN
950, OptiX RTN 980, or All Type.
NE Version: indicates the version of the NE. Select the version of the NE to be
upgraded.
Issue 01 2012-08-06

42

Step 4 Select the NEs to be upgraded. After the selected NEs are displayed in NE Table, click
Query.
Issue 01 2012-08-06

43

Step 5 Select Activation Level and click Next. (Network Element: a conventional upgrade method,
indicating that activation is performed on the NE level; Board Level: indicates that activation
is performed on the board level. The OptiX RTN products support Network Element only.)
Step 6 (Optional) Configure the 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.
The OptiX RTN 900 V100R003C03SPC201 does not support customized packages, so do
not select Custom package.
In the Operation Configuration [Package Diffusion Upgrade] window, select Pause

Before Current Operation for the operations as required. It is recommended that you select
Pause Before Current Operation for the Activate and Commit operations.
Issue 01 2012-08-06

44

Step 7 (Optional) Configure the upgrade precheck.

1.
Issue 01 2012-08-06
In the Operation Configuration [Package Diffusion Upgrade] dialog box, select the
Precheck check box and click Configure Precheck Items.

45

2.
In the Configure Precheck Operation dialog box, select Alarm Check, Health Check,
and Extended Check according to specific needs. Then, click OK.
If Extended Check is selected, you need to import the check items.
Step 8 (Optional) Configure the data backup operation.

1.
Issue 01 2012-08-06
Backup check box, and click Configure Backup Information.

46

2.
In the Configure Backup Operation dialog box, ensure that the default value of
Content Type is Data File. Click OK.
Step 9 (Mandatory) Configure the software files to be loaded.

1.
Load Package check box and click Configure Package.
2.
In the Select Package File(s) dialog box, click

loaded. Then, click OK.
Issue 01 2012-08-06
to select the software package to be

47

By performing this step, you can copy the software package from the server to the NE, or more
specifically, to the CF card and the flash memory of the system control board.
After software loading is started, the SWDL_INPROCESS alarm is reported on the U2000. This
alarm clears after the software is committed.
Step 10 (Mandatory) Configure the software dispense operation.

Dispense check box.
Issue 01 2012-08-06

48

Step 11 (Mandatory) Configure the software activation operation.
The software activation operation is to trigger a warm or cold reset on the system control
board or other boards. A cold reset will cause service interruptions.
You can configure activation groups based on network conditions to improve upgrade
efficiency. It is recommended that you configure one NE as an activation group.
If NEs that have service associations are configured as a protection group and are activated
at the same time, the related services will be interrupted. Therefore, you need to divide
such NEs in a protection group into different activation groups.
1.
Activate check box and click Configure Activation.
Issue 01 2012-08-06

49

2.
Issue 01 2012-08-06
In the Configure Activation dialog box that is displayed, click Get Default Activation
and configure the activation operation based on the displayed default activation
information.

50

Activation Time: indicates the time to activate the software. The activation time for the first
activation group is configurable. Select the Activate Time check box, click
the activation time to a time later than the software loading time.
, and then set
: indicates creating an activation group. By default, one NE forms one activation group.
The NE in a group is activated only after the NE in the previous group is activated.
: indicates moving an NE to the next group. To move an NE, select the NE first.
: indicates moving an NE to the previous group. To move an NE, select the NE first.
: indicates expanding the current view.
: indicates collapsing the current view.
: indicates deleting an activation group. To delete a group, select the group first.
Step 12 (Optional) Configure the upgrade postcheck.
1.
Postcheck check box and click Configure Postcheck Items.
2.
In the Configure Postcheck Operation dialog box, select Alarm Check and Health
Check according to specific needs. Then, click OK.
Issue 01 2012-08-06

51

To load a GNE, select Force to load selected GNE through FTP.
Step 13 (Mandatory) Configure the software commit operation.

Commit check box.
Issue 01 2012-08-06

52

If the commit operation fails to be performed within 30 minutes after the activation operation, the
SWDL_ACTIVATED_TIMEOUT alarm occurs. This alarm clears after the commit operation is
performed.
After the commit operation, check the current alarms. If the SWDL_COMMIT_FAIL alarm is
reported, the commit operation fails. Otherwise, the commit operation is successful.
Step 14 In the Operation Configuration [Package Diffusion Upgrade] dialog box, click Next to
complete the configuration operations.
Step 15 In the Confirmation [Package Diffusion Upgrade] dialog box, click OK. The NE Upgrade
Task Management window is displayed.
Issue 01 2012-08-06

53

Step 16 In the NE Upgrade Task Management window, run the package diffusion upgrade task. For
details, see section 4.2"Running the Package Loading Task."
----End
4.2 Running the Package Loading Task

Step 1 In the NE Upgrade Task Management window, right-click the package upgrade task or
package diffusion upgrade task that is already created. Then, choose Refresh from the
shortcut menu.
Issue 01 2012-08-06

54

Step 2 In the Refresh SWDL Status dialog box, check whether the software loading status of the
NE is Normal. If yes, proceed to the next step; if not, repeat steps 1 and 2 until the status is
Normal.
Step 3 In the NE Upgrade Task Management window, right-click the required upgrade task and
choose Start Task from the shortcut menu. Alternatively, select the required upgrade task and
click the Start Task button.
Issue 01 2012-08-06

55

Step 4 In the Task Start Confirmation dialog box that is displayed, click Yes. The task progress
information of the entire NE is displayed in the Operation Status column. In the lower right
pane, the status and result of each package loading operation are displayed.
Issue 01 2012-08-06

56

Step 5 If an operation pauses during the upgrade, do as follows:

1.
Issue 01 2012-08-06
Check whether the NE works properly. Right-click the upgrade task and choose
Generate Report from the shortcut menu. In the Generate Task(s) Report dialog box,
specify a file path and click OK.

57

2.
Open the report and check the status of package loading.
Step 6 If the status of package loading is normal, right-click the upgrade task and choose Continue
Task from the shortcut menu. Alternatively, select the upgrade task and click the Continue
Task button.
Issue 01 2012-08-06

58

Step 7 If the current status of software loading is abnormal, right-click the NE and choose Rollback
from the shortcut menu.
Issue 01 2012-08-06

59

Step 8 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 5 and check the details of the upgrade task.
----End
Issue 01 2012-08-06

60

5 Verifying the Upgrade
Verifying the Upgrade
5.1 Verification Checklist

Figure 1.1 Verification checklist
No.
Item
Expected Result
Checking the versions of the

NE software and the board
software
The software versions meet the requirements

specified in the version mapping table.
Checking the status of services
All services run properly.
Checking licenses
The NE does not report the LICENSE_LOST

alarm.
The current software versions are consistent

with the target versions.
Print and fill in the form attached in Figure 1.1"Upgrade Record."
5.2 Checking Software Versions

Description
Verify that the software version is correct after the upgrade is completed.
Procedure
Step 1 Download the version mapping table of the current version from http://support.huawei.com.
Note that a manual check after an upgrade differs from a post-upgrade check during upgrade
task creation, because the latter one is automatically run by the NE.
Step 2 Query the versions of the NE software and the board software on the U2000. For details, see
section 3.2.1"Querying the Hardware/Software Version."
Issue 01 2012-08-06

61

5 Verifying the Upgrade
Step 3 Check whether the queried software versions meet the requirements specified in the version
mapping table.
----End
Verification Result
The target software versions meet the requirements specified in the version mapping table.
5.3 Checking the Status of Services

Description
Verify that services run properly after the upgrade.
Procedure
Step 1 Browse the current alarms on the NE and check whether any critical alarms, such as
MW_LOF, R_LOF, R_LOC, and R_LOS, are reported.
Step 2 If the NE does not report any critical alarms, check whether the orderwire phone, ECC
communications, and clock tracing are in the normal state.
----End
Verification Result
None
5.4 Checking Licenses

Description
Check whether the NE reports the LICENSE_LOST alarm.
Procedure
Query current alarms on the NE and check whether the LICENSE_LOST alarm is reported.
If the alarm is reported, use the license tool to generate an NELCS file and load the NE with the
NELCS file to clear the alarm. For details about how to load the NELCS file, see the User
Guide to the License File of the OptiX RTN 900 V1.42.
----End
Verification Result
None
Issue 01 2012-08-06

62

6 Rolling Back to the Source Version
Rolling Back to the Source

Version
Perform a version rollback when an exception occurs during an upgrade. After the rollback,
the software of the original version runs on the NE.
6.1 Version Rollback Flowchart

Figure 1.1 Version rollback flowchart
Start
Perform a rollback
Verify the rollback result
End
6.2 Rollback Procedure

If you find that the software package is incorrect or the system malfunctions after a software
package is loaded, dispensed, or activated, roll back the software version immediately.
Issue 01 2012-08-06

63

If an exception occurs during the upgrade, a version rollback occurs automatically.

Specifically, if an exception occurs after the software is loaded, the software version will be
automatically rolled back to the source version. If an exception occurs after the software is
dispensed or activated, the NE status will be rolled back to the point of software loading
completion; in this case, you need to manually roll back the software version to the source
version.
Precautions
No rollback can be performed after the software files are committed.
Procedure
Step 1 In the NE Upgrade Task Management window, right-click the required NE and choose
Rollback from the shortcut menu.
Step 2 In the Operation Confirmation dialog box, click Yes.
Step 3 After a successful rollback, the Start Time and End Time fields display the start time and
end time of the current rollback operation. The Operation Result field displays a record
indicating that the software is rolled back successfully.
Issue 01 2012-08-06

64

----End
6.3 Verifying a Version Rollback

Figure 1.1 Verification checklist of a version rollback
Issue 01 2012-08-06
No
.
Item
Expected Result
Checking the current

software version
The current software version is the

same as the source version.
Checking the current

configuration on the NE
The current configuration is consistent

with the previous configuration when
the database is backed up.

Actual
Result
65

7 Troubleshooting
Troubleshooting
7.1 Exception 1
Symptom
During an upgrade, exceptions occur when the NE is downloading software from the NMS.
Troubleshooting
Step 1 During a package upgrade task, ensure that no files are deleted from or added to the NE.
Otherwise, reset the NE first.
Step 2 During a package diffusion upgrade task, do as follows:
1.
Check whether the DCN communication is normal and whether the bandwidth is
sufficient. If yes, go to the next step.
2.
Check whether the downloaded software package is correct. If yes, go to the next step.
3.
Change the GNE.
----End
7.2 Exception 2
Symptom
Errors occur during software activation.
Troubleshooting
Step 1 Check whether any board is removed during the upgrade. If not, go to the next step.
Step 2 Check whether DCN communication on the NE is normal.
If no, rectify the fault.
If yes, go to the next step.
Issue 01 2012-08-06

66

7 Troubleshooting
Step 3 Perform the upgrade task again.

----End
7.3 Exception 3
Symptom
Operations are suspended or user interfaces stop responding.
Troubleshooting
Right-click the NE and choose Retry from the shortcut menu.
----End
7.4 Exception 4
Symptom
The software loading fails because during software loading the system displays a message
indicating that the NE is abnormal.
Troubleshooting
Load the software again 10 minutes later.
----End
7.5 Exception 5
Symptom
Backing up data fails.
Troubleshooting
Back up data again 10 minutes later.
----End
7.6 Exception 6
Symptom
During an upgrade, database backup fails.
Issue 01 2012-08-06

67

7 Troubleshooting
Troubleshooting
Upload the NE databases to the U2000 again; create another upgrade task and run the task.
----End
7.7 Exception 7
Symptom
On an OptiX RTN 950 NE with active and standby system control boards, the EM6T/EM6F
board reports the COMMUN_FAIL alarm after the NE is upgraded by using the DC.
Troubleshooting
Step 1 Ensure that the other boards on the NE are upgraded correctly.
Step 2 Ensure that the active and standby system control boards are synchronized.
Step 3 Manually switch over the active and standby system control boards.
Step 4 Query the version information about the EM6T/EM6F board after the COMMUN_FAIL
alarm clears.
Step 5 Perform a cold reset on the EM6T/EM6F board if the version information is incorrect.
Step 6 Verify that the version information is correct after the EM6T/EM6F board starts working.
----End
7.8 Exception 8
Symptom
On an OptiX RTN 950 NE with active and standby system control boards, the query about the
EM6T/EM6F version information times out after the NE is upgraded by using the DC.
Troubleshooting
Step 1 Ensure that the other boards on the NE are upgraded correctly.
Step 2 Ensure that the active and standby system control boards are synchronized.
Step 3 Manually switch over the active and standby system control boards.
Step 4 Query the version information about the EM6T/EM6F board.
Step 5 Perform a cold reset on the EM6T/EM6F board if the version information is incorrect.
Step 6 Verify that the version information is correct after the EM6T/EM6F board starts working.
----End
Issue 01 2012-08-06

68

7 Troubleshooting
7.9 Exception 9
Symptom
After an OptiX RTN 950 is upgraded by using the DC, the historical alarms of the EFP8
contain the HARD_BAD alarm.
Troubleshooting
Step 1 In the OptiX RTN 900 V100R003C03 or a later version, the SCC board enables the phaselocked loop to transmit the telecom clock. The PPL is capable of transmitting the telecom
clock only when the NE software is initiated and exits from its reset state.
Step 2 During the upgrade, the new NE software may coexist with the old board temporarily. The
EFP8 board does not receive the 77 Mbit/s clock from the NE software until the NE software
is initialized. Therefore, the board fails to detect the 77 Mbit/s clock and reports the
HARD_BAD alarm.
Step 3 After the upgrade is complete, the HARD_BAD alarm clears automatically and the EFP8
board is not affected.
----End
7.10 Exception 10
Symptom
An NE with two SCC boards may report alarms that are not supposed to be reported (such as
LAG_MEMBER_DOWN, LAG_DOWN, ETH_EFM_DF, MULTI_RPL_OWNER, and
LPT_CFG_CLOSEPORT) after it is downgraded.
Troubleshooting
Alarms that are not supposed to be reported disappear after you perform a warm reset on the
active SCC board.
----End
7.11 Exception 11
Symptom
When a package diffusion upgrade is performed on a large-scale complicated network using
the DC tool, if the DCN communication is interrupted, the upgrade may be suspended.
Troubleshooting
During a package diffusion upgrade, it is recommended that you do not perform several
upgrade tasks concurrently. Otherwise, DCN communication with far-end NEs is interrupted
due to software activation.
Issue 01 2012-08-06

69

7 Troubleshooting
----End
7.12 Exception 12
Symptom
Before a downgrade, the NE houses boards that are not supported by the target version,
resulting in failure to the downgrade.
Troubleshooting
Before a downgrade, ensure that the NE does not house boards that are not supported by the
target version (such as the EMS6 and SL1DA boards that are only supported on the
V100R003C03SPC201). If a downgrade fails because of unsupported boards, remove the
boards and retry the downgrade.
----End
7.13 Exception 13
Symptom
When L3 protocols (HWECC/IP/OSI) are used for NE management on a DCN and the GNE
manages more than 150 NEs, the GNE reports a DCNSIZE_OVER alarm after it is upgraded
to V100R003C03SPC201.
When L2 protocols are used for NE management on a DCN and this L2DCN consists of more
than 30 NEs, the NE configured with L2DCN reports a DCNSIZE_OVER alarm after it is
upgraded to V100R003C03SPC201.
Troubleshooting
Re-plan subnets to reduce the number of NEs on the DCN.
----End
7.14 Exception 14
Symptom
The LICENSE_LOST alarm is reported after an NE is upgraded from V100R003C00SPC100
or earlier to V100R003C03SPC201.
Troubleshooting
The alarm is reported because the V100R003C03SPC201 supports the NELCS file, which is a
new license file. After the upgrade, load the target NE with an NELCS file to clear the alarm.
----End
Issue 01 2012-08-06

70

7 Troubleshooting
7.15 Exception 15
Symptom
During an upgrade from V100R003C02SPC100 or an earlier version to
V100R003C03SPC201, data services are interrupted if:
A software version rollback occurs during activation.
The software is manually rolled back to the source version after activation but before
committing.
Troubleshooting
After an NE automatically rolls back, manually roll it back to the Normal state using the DC.
Then, perform the following steps:
If the NE to be upgraded houses one SCC board, manually cold reset the SCC board.
If the NE to be upgraded houses two SCC boards, perform the following operations:
1.
Cold reset the data board SL91EM6F, SL91EM6FA, SL91EM6T, or SL91EM6TA.
2.
After the data board starts working properly, manually cold reset the working SCC
board, triggering a switchover between the working and protection SCC boards.
3.
Wait for at least 5 minutes, and then cold reset the working SCC board.
----End
7.16 Exception 16
Symptom
During a downgrade, if a version rollback is performed on the NE after the NE database is
deleted and before the NE is activated, the rollback will fail.
Troubleshooting
Step 1 If the NE houses only one system control board, cold reset the system control board.
Step 2 If the NE houses two system control boards, cold reset the standby system control board and
then the active system control board. After the NE becomes stable, roll back the NE to the
source version again.
----End
Issue 01 2012-08-06

71

A.1.1Step 1Figure 1.1Upgrade Record
Figure 1.1
Upgrade Record
Site Name
Upgrade Date
Source Version
Target Version
Technician
Customer technician:
Huawei technician:
Was the Upgrade Successful?

Checklist for the Upgrade
Conclusion
Problem Handling
Checklist Before the Upgrade
Checklist During the Upgrade
Checklist After the Upgrade
Issue 01 2012-08-06

72

A.1.1Step 1Figure 1.2Product Features
Figure 1.2
Product Features
See the OptiX RTN 910 V100R003C03SPC201 Release Notes, OptiX RTN 950
V100R003C03SPC201 Release Notes, and OptiX RTN 980 V100R003C03SPC201 Release
Notes.
Issue 01 2012-08-06

73

A.1.1Step 1Figure 1.3Acronyms and Abbreviations
Figure 1.3
Acronyms and
Abbreviations
Acronym/Abbreviation
Full Spelling
DC
Data Center
DCC
Data communication channel
FPGA
Field programmable gate array
GNE
Gateway NE
RTN
Radio transmission node
Issue 01 2012-08-06

74

D Glossary
Figure 1.4
Glossary
None
Issue 01 2012-08-06

75

OptiX RTN 900 V100R003C03SPC201 Upgrade Guide-Package Loading Method

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

OptiX RTN 900 V100R003C03SPC201 Upgrade Guide-Package Loading Method

Enviado por

Direitos autorais:

Formatos disponíveis

OptiX RTN 900 Radio Transmission System

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System

The displayed information and sessions are in Courier New.

Completed the initial

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System

1 Before You Start

2 Upgrade Process Overview............................................................7

3 Preparing for the Upgrade...........................................................10

4 Performing the Upgrade..............................................................27

5 Verifying the Upgrade.................................................................60

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System

1 Before You Start

5.4 Checking Licenses...........................................................................................................................................61

6 Rolling Back to the Source Version...............................................62

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System

1 Before You Start

Before You Start

1.1 Method Introduction

1.2 Package Loading Method

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System

1 Before You Start

1.3 Upgrade Path

If an upgrade from V100R002C00SPC100 to V100R003C03SPC201 fails, you can roll

If an NE fails to be upgraded from a source version listed in the following table to

An OptiX RTN 900 V100R003C03SPC201 NE that is connected to the DC through

Package loading upgrade

Package loading upgrade

Package loading upgrade

Package loading upgrade

Package loading upgrade

Package loading upgrade

Package loading upgrade

Package loading upgrade

Package diffusion upgrade

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System

1 Before You Start

Package loading upgrade

Package loading upgrade

Package loading upgrade

Package loading upgrade

Package loading upgrade

Package loading upgrade

Package diffusion upgrade

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System

1 Before You Start

1.4 Impact of the Upgrade

1.4.1 Impact on the System During the Upgrade

Impact on Network Communications

1.4.2 Impact on the System After the Upgrade

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System

2 Upgrade Process Overview