OptiX OSN 8800 6800 3800 V100R007C00 Upgrade Guide

OptiX OSN 8800_6800_3800
V100R007C00
Upgrade Guide
Issue
05
Date
2013-08-20
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
OptiX OSN 8800_6800_3800

Upgrade Guide
About This Document
About This Document

Change History
Table 1 describes the change history about this document.
Table 1 Change History
Issu
e
Date
Author
Details
01
2012-07-30
Ran Yu, Shi Hao
First release
02
2012-09-20
Ran Yu
Added the impact on services of the upgrade to

V100R007C00SPC100.
03
2012-12-15
Ran Yu
Added the following information:
Impact caused by an upgrade to V100R007C00SPC200
Sections 3.9.73.9.8, 5.4.55.4.8, and 5.5
04
2013-3-29
Ran Yu
A caution in attachment 1, requesting the user to check whether

the DC user is MD5-encypted
Section 1.3 "Uploading NE Configurations" in attachment 2
Precautions for Upgrading the OptiX OSN 3800 Equipment
Updated the database check tool and usage descriptions.
Added the impact on services of the upgrade to

V100R007C00SPC300.
Added Attachment 9 Guide to Remotely Upgrading the CPLD of
the TN52AUX Board.doc
05
2013-8-20
Liu Haihan,
Added the following contents:
Cai Shanbao,
Li Qin
Description of the sequence for upgrading optical-layer ASON

NEs in section 1.3
Precaution for not applying DAS1 boards to OLA sites in section
1.6
Precaution for the software library in section 1.6
GUI Conventions
This document uses the following conventions listed in Table 2:
OptiX OSN 8800_6800_3800

Upgrade Guide
About This Document
Table 2 GUI Conventions

GUI
Convention
Description
Boldface
Window, dialog box, and tab names; menu options, buttons, icons
and parameters; as well as commands that need to be entered
manually during the upgrade are in boldface.
Example:
The New User window is displayed. Click the OK button.
Boldface italic
Command parameters of a command that are variables and must be

entered by users during the upgrade are in boldface italic.
>
Menu items are separated by the ">" sign.

Example: choose File > Create > Folder.
Courier New
Information displayed on the screen is displayed in Courier New.
OptiX OSN 8800_6800_3800

Upgrade Guide
Contents
Contents
About This Document.......................................................................ii

1 Before You Start...........................................................................1
1.1 Upgrade Mode...................................................................................................................................................1
1.2 Upgrade Paths for NEs with Traditional Services.............................................................................................2
1.3 Upgrade Paths for NEs with ASON Services....................................................................................................3
1.4 Methods for Assigning NEs to an Upgrade Task...............................................................................................5
1.5 Upgrade Impact..................................................................................................................................................7
1.5.1 Impact on the System During the Upgrade..............................................................................................7
1.5.2 Impact on the System After the Upgrade................................................................................................14
1.6 Precautions.......................................................................................................................................................16
2 Upgrade Flowchart......................................................................19
3 Preparing for the Upgrade...........................................................21
3.1 Preparing the Upgrade Checklists....................................................................................................................21
3.2 Preparing the Upgrade Tool.............................................................................................................................21
3.3 Obtaining Target Upgrade Software................................................................................................................25
3.4 Creating a User for the DC to Log In to the Target NE...................................................................................27
3.5 Checking NE Health Before Upgrading (U2000 or Standalone DC)..............................................................31
3.6 Checking NE Versions.....................................................................................................................................37
3.7 Checking Status of the NE Database...............................................................................................................38
3.8 Checking the Status of the ODUk SPRing Protection Group..........................................................................41
3.9 Checking System Settings...............................................................................................................................43
3.10 Pre-upgrade Check for ASON NEs...............................................................................................................44
3.10.1 Checking Consistency Between NMS Data and NE Data...................................................................44
3.10.2 Checking ASON Trail Status................................................................................................................45
3.10.3 Checking for Interrupted or Downgraded TE Links............................................................................46
3.10.4 Backing Up ASON Trail Information on the NMS..............................................................................48
3.10.5 Locking the Rerouting Function for Network-wide ASON Trails.......................................................49
3.10.6 Downgrading ASON Trails to Traditional Trails..................................................................................50
OptiX OSN 8800_6800_3800

Upgrade Guide
Contents
3.10.7 Disabling Optical Parameter Constraints for Optical-Layer ASON Trails...........................................59

3.11 Adjusting the OA Gain...................................................................................................................................60
4 Performing the Upgrade..............................................................64

4.1 Creating Upgrade Tasks...................................................................................................................................64
4.2 Starting Upgrade Tasks....................................................................................................................................70
5 Verifying the Upgrade.................................................................73

5.1 Verification Checklist.......................................................................................................................................73
5.2 Verification of the Current Software Version...................................................................................................73
5.3 Verification of the Equipment Operating Status..............................................................................................74
5.4 Verifying ASON NE Upgrade Result..............................................................................................................76
5.4.1 Checking ASON Trail Status..................................................................................................................76
5.4.2 Unlocking the Rerouting Function for ASON Trails..............................................................................77
5.4.3 Changing Flooding Modes for Electrical-Layer Links (Electrical-Layer ASON Network)..................79
5.4.4 Upgrading Traditional Trails to ASON Trails.........................................................................................80
5.4.5 Enabling Optical Parameter Constraints for Optical-Layer ASON Trails..............................................83
5.4.6 Changing Flooding Modes for Optical-Layer Links (Optical-Layer ASON Network).........................84
6 Troubleshooting..........................................................................87
6.1 Version Rollback..............................................................................................................................................87
6.1.1 Common Causes of Rollback.................................................................................................................87
6.1.2 Manual Rollback.....................................................................................................................................91
6.1.3 Version Rollback Verification.................................................................................................................92
6.2 Performing the Downgrade..............................................................................................................................93
6.3 NE Database Backup and Restoration.............................................................................................................93
6.4 Disabling and Enabling IEEE 1588v2 Time Synchronization on TN11ST2 Boards......................................93
6.4.1 Disabling IEEE 1588v2 Time Synchronization on TN11ST2 Boards...................................................93
6.4.2 Enabling IEEE 1588v2 Time Synchronization on TN11ST2 Boards.....................................................97
6.5 Upgrading NEs Enabled with Synchronous Ethernet and IEEE 1588v2 Functions in Software Package
Loading Mode......................................................................................................................................................100
6.6 Board Isolation...............................................................................................................................................105
6.7 Checking Whether Package Loading Needs to Be Performed for a Second Time........................................105
A Upgrade Record Table...............................................................107

B Pre-upgrade Checklist...............................................................108
C Upgrade Checklist.....................................................................109
D Abbreviations and Acronyms.....................................................111
OptiX OSN 8800_6800_3800

Upgrade Guide
1 Before You Start
Before You Start
Before performing a software upgrade, read this chapter to learn how to select the upgrade
mode, create an upgrade task, and determine the upgrade path. In addition, this chapter
contains useful information about group activation strategies, upgrade flow, and upgrade
impacts, which can help perform the upgrade more efficiently and also improve the reliability
and efficiency of the upgrade.
1.1 Upgrade Mode

This section describes how to select a proper upgrade mode. The OptiX OSN 8800, 6800, and
3800 support two upgrade modes: software package loading mode and software package
diffusion mode. Each mode applies to a different networking scenario. Selecting the proper
upgrade mode ensures optimal upgrade performance.
Table 1.1.1.I.1.1.1.1 Upgrade Mode
Upgra
de
Mode
Concept
Comparison
Applicable
Scope
Software
Package
Loading
Mode
The DC tool loads the new

software package to each
NE.
If one gateway NE (GNE) has multiple

subtending NEs, this mode is used to upgrade
all the NEs in batches. The GNE forwards the
software package to all the subtending NEs.
This mode is used

to upgrade single
NEs or to upgrade
multiple GNEs
simultaneously.
The GNE and its subtending NEs should be in

the same task.
OptiX OSN 8800_6800_3800

Upgrade Guide
1 Before You Start
Upgra
de
Mode
Concept
Comparison
Applicable
Scope
Software
Package
Diffusion
Mode
The DC tool automatically

computes the diffusion map
for the NEs in an upgrade
task. The DC tool first
loads the required software
package to an NE that is
directly reachable through
a DCN. Then this NE
diffuses the software
package to its downstream
NEs level by level.
If an upgrade task includes a GNE, the GNE is

upgraded first and then the software package
is diffused by the GNE to its subtending NEs.
If the upgrade task does not include a GNE,
the NE closest to a GNE is upgraded first and
then the software package is diffused to its
downstream NEs level by level.
This mode is used

to upgrade one
GNE and its
subtending NEs in
batches.
During the upgrade, you do not need to load

the software package to all of the NEs you
want to upgrade. This mode is used to share
the load on a GNE while evenly using the
DCN bandwidth, ultimately improving the
software upload performance and efficiency.
1.2 Upgrade Paths for NEs with Traditional

Services
This section helps you determine the upgrade path and the corresponding upgrade mode.
Determine whether the source version can be directly upgraded to the target version based on
Table 1.2.1.I.1.1.1.1. If not, then upgrade the source version to an intermediate version and
then to the target version as specified in the table 1-2.
When an NE of a version earlier than OptiX OSN 6800_3800 V100R004C04SPC800 or OptiX OSN
8800 V100R002C02SPC800 needs to be upgraded to OptiX OSN 8800/6800/3800
V100R007C00SPC100/SPC200/SPC300, first upgrade it to OptiX OSN 6800_3800
V100R004C04SPC800 or OptiX OSN 8800 V100R002C02SPC800, and then to the target version. For
the detailed upgrade procedure, see the OptiX OSN 8800
V100R002C02&8800V100R002C00&6800_3800 V100R004C04 Upgrade Guide.
OptiX OSN 8800_6800_3800

Upgrade Guide
1 Before You Start
Table 1.2.1.I.1.1.1.1 Upgrade paths

Source Version
Upgrade Mode
OptiX OSN 8800 V100R002C02SPC800
Software Package Loading:
OptiX OSN 6800/3800 V100R004C04SPC800
These source versions can be

upgraded directly to OptiX OSN
8800/6800/3800
V100R007C00SPC100/SPC200
/SPC300.
OptiX OSN 8800/6800/3800 V100R005C00SPC700

OptiX OSN 8800/6800/3800 V100R005C00SPC800
OptiX OSN 8800/6800/3800 V100R005C00SPC900
OptiX OSN 8800/6800/3800 V100R006C00SPC100
OptiX OSN 8800/6800/3800 V100R006C00SPC200
OptiX OSN 8800/6800/3800 V100R006C00SPC300
OptiX OSN 8800/6800/3800 V100R006C00SPC500
OptiX OSN 8800/6800/3800 V100R006C01SPC100
OptiX OSN 8800/6800/3800 V100R006C01SPC200
OptiX OSN 8800/6800/3800 V100R006C01SPC300
OptiX OSN 8800/6800/3800 V100R006C01SPC500
OptiX OSN 8800/6800/3800 V100R006C03SPC200
OptiX OSN 8800/6800/3800 V100R006C03SPC300
OptiX OSN 8800/6800/3800 V100R006C03SPC500
OptiX OSN 8800/6800/3800 V100R007C00
OptiX OSN 8800/6800/3800 V100R007C00SPC100
OptiX OSN 8800/6800/3800 V100R007C00SPC200
Software Package Loading and

Software Package Diffusion
Mode:
These source versions can be
upgraded directly to OptiX OSN
8800/6800/3800
V100R007C00SPC100/SPC200
/SPC300.
OptiX OSN 6800/3800 V100R001
Software package loading:
OptiX OSN 6800/3800 V100R003C02
These source versions must first

be upgraded to OptiX OSN
6800_3800
V100R004C04SPC800 and then
to OptiX OSN 8800/6800/3800
V100R007C00SPC100/SPC200
/SPC300.
OptiX OSN 6800/3800 V100R004C01

OptiX OSN 6800/3800 V100R004C02
OptiX OSN 6800/3800 V100R004C03
OptiX OSN 6800/3800 V100R004C04SPC200
OptiX OSN 6800/3800 V100R004C04SPC400
OptiX OSN 6800/3800 V100R004C04SPC510
OptiX OSN 8800 V100R001C01
These source versions must first

be upgraded to OptiX OSN
8800 V100R002C02SPC800
and then to OptiX OSN
8800/6800/3800
V100R007C00SPC100/SPC200
/SPC300.

OptiX OSN 8800_6800_3800

Upgrade Guide
1 Before You Start
If both package loading and package diffusion are supported, use the network communication quality
and the number of NEs that need to be upgraded to determine the proper upgrade method. If the network
communication quality is not satisfactory and the number of NEs to be upgraded is less than 10, use the
package loading mode for better stability. Otherwise, upgrade the NEs in package diffusion mode, which
is more efficient than the package loading mode.
1.3 Upgrade Paths for NEs with ASON Services
1. This document provides guidance on how to upgrade OptiX OSN 8800/6800

V100R005C00SPC800 or OptiX OSN 8800/6800 V100R006C03 or OptiX OSN 8800/6800
V100R007C00 to OptiX OSN 8800/6800 V100R007C00SPC100/SPC200/SPC300.
2. When an NE of a version earlier than OptiX OSN 8800/6800 V100R005C00SPC800 needs
to be upgraded to OptiX OSN 8800/6800 V100R007C00SPC100/SPC200/SPC300, first
upgrade it to OptiX OSN 8800/6800 V100R005C00SPC800 and then to the target version.
For the detailed upgrade procedure for an upgrade to OptiX OSN 8800/6800
V100R005C00SPC800, see the OptiX OSN 8800/6800/3800 V100R005C00 Upgrade Guide.
Source Version
Upgrade Mode
OptiX OSN 6800

V100R003C02
OptiX OSN 6800

V100R004C01
These source versions must first be upgraded to OptiX

OSN 6800 V100R005C00SPC800 and then to OSN
6800 V100R007C00SPC100/SPC200/SPC300.
OptiX OSN 6800

V100R004C02SPC200
OptiX OSN 6800
V100R004C04SPC510
OptiX OSN 6800
V100R004C04SPC800
OptiX OSN 8800
V100R002C02SPC800
OptiX OSN 8800/6800

V100R005C00SPC800
Software package loading
OptiX OSN 8800/6800

V100R006C03SPC300
Software package loading and Software Package

Diffusion Mode
OptiX OSN 8800/6800

V100R006C03SPC500
These source versions must first be upgraded to OptiX

OSN 8800 V100R005C00SPC800 and then to OSN
8800 V100R007C00SPC100/SPC200/SPC300.
OptiX OSN 8800_6800_3800

Upgrade Guide
1 Before You Start
Source Version
Upgrade Mode
OptiX OSN 8800/6800

V100R007C00
OptiX OSN 8800/6800
V100R007C00SPC100
OptiX OSN 8800/6800
V100R007C00SPC200
The upgrade paths provided in the table above are based on the versions of ASON sites in the
live network. For information about upgrade paths not listed in the table, contact Huawei
engineers to identify upgrade precautions.
1.4 Methods for Assigning NEs to an Upgrade

Task
This section describes methods for assigning NEs to an upgrade task. For a software upgrade,
NEs in an area that have the same properties should be put into the same upgrade task. Each
upgrade task is an independent upgrade unit. Properly assigning NEs to upgrade tasks helps
improve the upgrade efficiency and reduce the upgrade impact on services. When creating
upgrade tasks, observe the following:
For a traditional network, upgrade optical NEs prior to electrical NEs to minimize the
upgrade impact on services. Do not put optical NEs and electrical NEs into the same
task. For an ASON network, create an upgrade task by referring to the table. If your
network scenario is not mentioned in the section or you are not clear about the ASON
network upgrade strategies, contact Huawei engineers.
If a GNE has multiple subtending NEs, the GNE and its subtending NEs should be
preferentially assigned to the same upgrade task.
Source Version
OptiX OSN 6800

V100R004C04
OptiX OSN 8800
V100R002C02
Optical-Layer ASON
Separated
Optical and
Electrical NEs
OpticalElectrical
Integrated NEs
Upgrade sites equipped

with optical regeneration
boards prior to other
sites.
Upgrade sites equipped

with optical
regeneration boards
prior to other sites.
Electrical-Layer
ASON
There is no restriction
on the NE upgrade
sequence.
OptiX OSN 8800_6800_3800

Upgrade Guide
1 Before You Start
OptiX OSN
8800/6800
V100R005C00
Upgrade electrical NEs

in batches first and then
optical NEs.
on the NE upgrade
sequence. If a TE link
degrade alarm caused
by ALC is reported on
an NE after the
upgrade, the alarm
must be cleared before
the ASON service
rerouting is released.
on the NE upgrade
sequence.
OptiX OSN
8800/6800
V100R006C00

optical NEs.
on the NE upgrade
an NE after the
upgrade, the alarm
the ASON service
If the TN54THA or
TN54TOA board is
used to carry ASON
services, upgrade the
NE where the board
functions as the
source prior to other
NEs. If the board
functions as the
source of an ASON
service and also the
sink of another
ASON service, the
board is still
considered as a
source node.
OptiX OSN
8800/6800
V100R006C01

optical NEs.
on the NE upgrade
an NE after the
upgrade, the alarm
the ASON service
on the NE upgrade
sequence.
OptiX OSN
8800/6800
V100R006C03
There is no restriction on
the NE upgrade
sequence.
on the NE upgrade
sequence.
on the NE upgrade
sequence.
NE-Level Activation
In NE-level activation mode, one NE is considered as one group by default. You can reorganize the groups using the U2000 based on the network situations. Each NE divides its
boards into different groups for activation based on the relationship between services. The
board grouping on an NE is implemented automatically and cannot be changed. The NE-level
activation is the default mode and is recommended.
Activating Boards in Groups

During the activation stage, the NE software automatically calculates the optimal activation
groups and sequences to ensure that services are not impacted by the upgrade. Upgrade
OptiX OSN 8800_6800_3800

Upgrade Guide
1 Before You Start
groups are automatically created. The following provides the rules that the NE software
follows to create upgrade groups:
Group 1: contains all of the standby SCC boards of every NE. If there is no standby
SCC, the active SCC is activated. The TN16XCH boards in slave subracks are not
included in this group.
Group 2: contains the following boards of every NE:
Boards on which a warm reset must be performed
SCC boards on which a cold reset must be performed in slave subracks
System boards
Optical-layer boards
Unprotected tributary boards (except TOM boards)
16AUX board in slave subracks
Group 3: contains standby boards, each of which is in a 1+1 backup protection group and
must undergo a cold reset. There are two types of standby boards in this group:
Standby cross-connect board
Standby clock board
In addition to the preceding boards, group 3 may also contain line boards and SDH
service boards that are not participating in any protection.
Group 4: contains active boards, each of which is in a 1+1 backup protection group and
must undergo a cold reset. There are two types of active board in this group:
Active cross-connect board
Active clock board
Group 5 to Group N: created based on board protection configurations to ensure that the
working and protection boards are in different groups.
1.5 Upgrade Impact

This section describes impact on the system during and after the upgrade.
1.5.1 Impact on the System During the Upgrade

Impact on Services
During a board software upgrade, a warm reset must be performed on a board before the
upgrade can take effect. When the field programmable gate array (FPGA) of a board needs to
be upgraded, a cold reset must be performed on the board before the upgrade can take effect.
A cold reset on a service board interrupts services for less than 5 minutes. If cross-connect
boards are configured with 1+1 protection, services will not be interrupted.
The following table lists the service boards whose FPGA needs to be upgraded during an
upgrade.
OptiX OSN 8800_6800_3800

Upgrade Guide
1 Before You Start
Table 1.5.1.I.1.1.1.1 Impact on Services

Source Version
Target Version
Boards Where Services

Are Affected
Impact
Cause
OptiX OSN
6800_3800
V100R004C04SPC80
0
OptiX OSN
8800/6800/3800
V100R007C00SPC100/
SPC200/SPC300
TN13LSX, TN12ND2, TN52TOG,

TN52XCM, TN52XCH,
TNK2SXM, TNK2XCT,
TN12LOM,TN12LSX , SSN1SF64,
SSN1SF64A, SSN4SFD64,
SSN4SF64, SSN4SLO16,
SSN4SLQ16, SSN1EGSH
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R005C00SPC70
0
OptiX OSN
8800/6800/3800
V100R007C00SPC100/
SPC200/SPC300

TN52XCM, TN52XCH,
TNK2SXM, TNK2XCT,
TN12LOM, TN11LEM24,
TN11LEX4, TN12LSX,
SSN1SF64, SSN1SF64A,
SSN4SFD64, SSN4SF64,
SSN4SLO16, SSN4SLQ16,
SSN1EGSH
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R005C00SPC80
0
OptiX OSN
8800/6800/3800
V100R007C00SPC100/
SPC200/SPC300

TN52XCM, TN52XCH,
TNK2SXM, TNK2XCT,
TN12LOM, TN12LSX,
TN11LEM24, TN11LEX4 ,
SN4SFD64, SSN4SF64,
SSN4SLO16, SSN1EGSH,
SSN4SLQ16
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R005C00SPC90
0
OptiX OSN
8800/6800/3800
V100R007C00SPC100/
SPC200/SPC300

TN52XCM, TN52XCH,
TNK2SXM, TNK2XCT,
TN12LOM, TN11LEM24,
TN11LEX4, TN12LSX,
SSN4SFD64, SSN4SLQ16,
SSN4SF64, SSN4SLO16
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R006C00SPC10
0
OptiX OSN
8800/6800/3800
V100R007C00SPC100/
SPC200/SPC300

TN52XCM, TN52XCH,
TNK2SXM, TNK2XCT,
TN55NPO2, TN54THA,
TN54TOA, TN53TQX, TN16XCH,
TN12LSX, TN11LEM24,
TN11LEX4 ,SSN1SF64,
SSN4SLQ16, SSN1EGSH
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN 8800

V100R002C02SPC80
0
OptiX OSN 8800_6800_3800

Upgrade Guide
1 Before You Start
Source Version
Target Version

Are Affected
Impact
Cause
OptiX OSN
8800/6800/3800
V100R006C00SPC20
0
OptiX OSN
8800/6800/3800
V100R007C00SPC100/
SPC200
TN13LSX, TN12ND2, TN52XCM,

TN52XCH, TNK2SXM,
TNK2SXH, TNK2XCT,
TN55NPO2,TN16XCH,
TN12LSX , TN11LEM24,
SSN1EGSH
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R006C00SPC20
0
OptiX OSN
8800/6800/3800
V100R007C00SPC300

TN52XCH, TNK2SXM,
TNK2SXH, TNK2XCT,
TN55NPO2,TN16XCH,
TN11LEX4, SSN1SF64,
SSN4SLQ16, SSN1EGSH
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R006C00SPC30
0
OptiX OSN
8800/6800/3800
V100R007C00SPC100/
SPC200

TN52XCH, TNK2SXM,
TNK2SXH, TNK2XCT,
TN55NPO2, TN16XCH, TN12LSX
, TN11LEM24, SSN1SF64,
SSN4SLQ16, SSN1EGSH
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R006C00SPC30
0
OptiX OSN
8800/6800/3800
V100R007C00SPC300

TN52XCH, TNK2SXM,
TNK2SXH, TNK2XCT,
TN55NPO2, TN16XCH, TN12LSX
, TN11LEM24, TN11LEX4,
SSN1EGSH
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R006C00SPC50
0
OptiX OSN
8800/6800/3800
V100R007C00SPC100/
SPC200

TN52XCH, TNK2SXM,
TNK2SXH, TNK2XCT,
SSN4SLO16, SSN4SLQ16
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN 8800_6800_3800

Upgrade Guide
1 Before You Start
Source Version
Target Version

Are Affected
Impact
Cause
OptiX OSN
8800/6800/3800
V100R006C00SPC50
0
OptiX OSN
8800/6800/3800
V100R007C00SPC300

TN52XCH, TNK2SXM,
TNK2SXH, TNK2XCT,
TN11LEX4, SSN1SF64,
SSN4SLQ16
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R006C01SPC10
0
OptiX OSN
8800/6800/3800
V100R007C00SPC100/
SPC200

TN52XCH, TNK2SXM,
TNK2SXH, TNK2XCT,
TN16XCH, TNK4SXM,
TNK4SXH, TNK4XCT,
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R006C01SPC10
0
OptiX OSN
8800/6800/3800
V100R007C00SPC300

TN52XCH, TNK2SXM,
TNK2SXH, TNK2XCT,
TN16XCH, TNK4SXM,
TNK4SXH, TNK4XCT,
TN11LEX4, SSN1SF64,
SSN4SLQ16
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R006C01SPC20
0
OptiX OSN
8800/6800/3800
V100R007C00SPC100/
SPC200

TN52XCH, TNK2SXM,
TNK2SXH, TNK2XCT,
TN16XCH, TNK4SXM,
TNK4SXH, TNK4XCT,
TN12LSX , SSN1SF64,
SSN1SF64A, SSN4SLO16,
SSN4SLQ16
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R006C01SPC20
0
OptiX OSN
8800/6800/3800
V100R007C00SPC300

TN52XCH, TNK2SXM,
TNK2SXH, TNK2XCT,
TN16XCH, TNK4SXM,
TNK4SXH, TNK4XCT,
TN11LEX4, SSN1SF64,
SSN4SLQ16
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN 8800_6800_3800

Upgrade Guide
1 Before You Start
Source Version
Target Version

Are Affected
Impact
Cause
OptiX OSN
8800/6800/3800
V100R006C01SPC30
0
OptiX OSN
8800/6800/3800
V100R007C00SPC100/
SPC200
TN52XCM, TN52XCH,
TNK2SXM, TNK2SXH,
TNK2XCT, TN16XCH,
TNK4SXM, TNK4SXH,
TNK4XCT, TN12LSX, SSN1SF64,
SSN4SLQ16
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R006C01SPC30
0
OptiX OSN
8800/6800/3800
V100R007C00SPC300
TN52XCM, TN52XCH,
TNK2SXM, TNK2SXH,
TNK2XCT, TN16XCH,
TNK4SXM, TNK4SXH,
TNK4XCT, TN12LSX,
TN11LEM24, TN11LEX4,
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R006C01SPC50
0
OptiX OSN
8800/6800/3800
V100R007C00SPC100/
SPC200
TN16XCH, TN12LSX, TN52XCH,

TN52XCM, TNK2XCT,
TNK2SXM, TNK2SXH,
TNK4XCT,TNK4SXM,
TNK4SXH, SSN4SLO16,
SSN4SLQ16, SSN1SF64,
SSN1SF64A
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R006C01SPC50
0
OptiX OSN
8800/6800/3800
V100R007C00SPC300
TN16XCH, TN12LSX, TN52XCH,

TN52XCM, TNK2XCT,
TNK2SXM, TNK2SXH,
TNK4XCT,TNK4SXM,
TNK4SXH, TN11LEM24,
TN11LEX4, SSN4SLO16,
SSN1SF64A
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R006C03SPC20
0
OptiX OSN
8800/6800/3800
V100R007C00SPC300
TN12LSX, TN13LSX, TN52XCM,

TN52XCH,TNK2SXM,TNK2SXH,
TNK2XCT, TN55NS3,TN15LSXL,
TN12LSC, TN11LTX, TN16XCH,
TNK4SXM,TNK4SXH,TNK4XCT,
TN11ST2,SSN1SF64,SSN1SF64A,
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R006C03SPC30
0
OptiX OSN
8800/6800/3800
V100R007C00SPC100/
SPC200
TN52XCM, TN52XCH, TN12LSC,

TN11LTX, TN16XCH, TNK4SXM,
TNK4SXH, TNK4XCT, TN12LSX,
TN11ST2, SSN1SF64,
SSN4SLQ16
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN 8800_6800_3800

Upgrade Guide
1 Before You Start
Source Version
Target Version

Are Affected
Impact
Cause
OptiX OSN
8800/6800/3800
V100R006C03SPC30
0
OptiX OSN
8800/6800/3800
V100R007C00SPC300
TN52XCM, TN52XCH, TN12LSC,

TN11LTX, TN16XCH, TNK4SXM,
TNK4SXH, TNK4XCT, TN12LSX,
TN11ST2, SSN1SF64,
SSN4SLQ16
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R006C03SPC50
0
OptiX OSN
8800/6800/3800
V100R007C00SPC100
TN12LSX, TN52XCM, TN52XCH,

TN11ST2, TN11LTX, TN12LSC,
TN52XCH02, TN52XCM02,
TN16XCH, SSN4SLQ16,
SSN4SLO16
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R006C03SPC50
0
OptiX OSN
8800/6800/3800
V100R007C00SPC200

TN11ST2, TN52XCH02,
TN52XCM02, TN16XCH ,
SSN1SF64A, SSN4SLO16
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R006C03SPC50
0
OptiX OSN
8800/6800/3800
V100R007C00SPC300

TN11ST2, TN52XCH02,
TN52XCM02, TN16XCH ,
SSN1SF64A, SSN4SLO16
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R007C00
OptiX OSN
8800/6800/3800
V100R007C00SPC100
TN12LSX, TN11ST2, TN11LTX ,

TN12LSC, TN16XCH,
TN16UXCM, TN54NS4
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R007C00
OptiX OSN
8800/6800/3800
V100R007C00SPC200
TN12LSX, TN11ST2, TN11LTX,

TN12LSC, TN55TOX, TN16XCH,
TN52UXCM, TN52UXCH,
TNK2USXH, TNK2UXCT,
TN16UXCM, TN54NS4
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R007C00
OptiX OSN
8800/6800/3800
V100R007C00SSPC30
0
TN12LSX, TN11ST2, TN11LTX,

TN12LSC, TN55TOX, TN16XCH,
TN52UXCM, TN52UXCH,
TNK2USXH, TNK2UXCT,
TN16UXCM, TN54NS4 ,
TN11LEM24, TN11LEX4
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R007C00SPC10
0
OptiX OSN
8800/6800/3800
V100R007C00SPC200
TN11LTX, TN12LSC, TN55TOX,

TN52UXCM, TN52UXCH,
TNK2USXH, TNK2UXCT,
TN54NS4
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN 8800_6800_3800

Upgrade Guide
1 Before You Start
Source Version
Target Version

Are Affected
Impact
Cause
OptiX OSN
8800/6800/3800
V100R007C00SPC10
0
OptiX OSN
8800/6800/3800
V100R007C00SPC300
TN11LTX, TN12LSC, TN55TOX,

TN52UXCM, TN52UXCH,
TNK2USXH, TNK2UXCT,
TN54NS4, TN11LEM24,
TN11LEX4
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
OptiX OSN
8800/6800/3800
V100R007C00SPC20
0
OptiX OSN
8800/6800/3800
V100R007C00SPC300
TN54NS4, TN11LEM24,
TN11LEX4
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
After the upgrade, perform a cold reset on the TN52TOG board if the IEEE 1588v2 or
synchronous Ethernet function must be enabled. Note that a cold reset interrupts services on
the board for less than 5 minutes. If a rollback occurs after the upgrade, the TN52TOG board
will be reset (cold) and services on the board are interrupted for less than 5 minutes.
When the source version is OptiX OSN 8800 V100R002C02SPC800 or OptiX OSN 6800
V100R004C04SPC800 and NEs transmit the synchronous clock signal using their TN52ND2
boards, the transmitting NE will automatically shut down the clock port on its TN52ND2
board after the upgrade, which will lead to a SYNC_C_LOS alarm on the receiving NE. To
clear the alarm, enable the clock port on the TN52ND2 board on the transmitting NE after the
upgrade.
After an upgrade from OptiX OSN 8800/6800 V100R006C00 or earlier to OptiX OSN
8800/6800 V100R007C00, perform a cold reset on TN54TOA and TN54THA boards if the
IEEE 1588v2 function must be enabled. Note that a cold reset interrupts services on the
boards for less than 5 minutes.
If the TN11TBE board has been installed on an NE and the source version of the NE is earlier
than V100R005C00SPC800, perform a cold reset on the board after package distribution is
completed. After the reset, services on the board are interrupted for less than 5 minutes and
the board is put into the isolation room on the U2000.After the upgrade is completed,
manually cancel the isolation of the TN11TBE board in the Isolation Room window on the
U2000.
If the physical-layer clock or PTP clock (IEEE 1588v2) is configured and the current clock
tracing source is configured in an OptiX OSN 8800 T16 subrack, the clock source will
undergo switching or enter the hold-off state. As a result, the performance of the clock source
will deteriorate for less than 5 minutes.
If an NE has the TN55TOX or TN54NS4 board and the source version is OptiX OSN 8800
V100R007C00SPC100, a cold reset on the TN55TOX or TN54NS4 board will cause service
interruption and the BUS_ERR alarm will be reported. After the upgrade is completed, the
BUS_ERR alarm will clear and the services will be restored. If SNCP is configured for the
NE and both the working and protection boards are TN54NS4, a cold reset on the TN54NS4
will make the SNCP switching time exceed the threshold but the service interruption time will
not exceed 5 minutes.
OptiX OSN 8800_6800_3800

Upgrade Guide
1 Before You Start
Impact on Network Communication

The SCC board is reset during an upgrade. Communication between the U2000 and NE is
interrupted for no more than 1 minute if the NE is equipped with two SCC boards and for no
more than 10 minutes if the NE is equipped with only one SCC board.
During the upgrade of service boards, DCN communication may be interrupted in the
following situations:
If the NE uses an electrical supervisory channel (ESC) as its management channel,

communication between the NE and U2000 is interrupted for no more than 3 minutes
when the service boards on the NE are upgraded.
If the NE uses an ESC as its management channel, when the FPGA of a service board on
the NE is upgraded, communication between subtending NEs that achieve
communication through this service board and the U2000 is interrupted for less than 5
minutes.
If the CPLD of the AUX board on the NE is upgraded, communication between the NE
and U2000 is interrupted when the AUX board software is being activated.
During an upgrade, if an automatic level control (ALC) link in automatic adjustment mode is
faulty, the ALC adjustment may fail because communication channels are congested or
communication between NEs has been interrupted.
Impact on Alarm Monitoring

Table 1-4 describes the impact on alarm monitoring during the upgrade.
Table 1.5.1.I.1.1.1.1 Impact on Alarm Monitoring During the Upgrade
Alarm That May Be
Reported
SWDL_INPROCESS
SWDL_ACTIVATED_TIMEOUT
COMMUN_FAIL
BD_STATUS
SCC_LOC
HARD_ERR
SUBRACK_LOOP
CRC4_CROSSTR
ODUKSP_STA_INDI
OPU2_CSF
Impact
During the upgrade, the NE reports an
SWDL_INPROCESS alarm. The NE will report
an SWDL_ACTIVATED_TIMEOUT alarm if the
new software package is not committed 2 minutes
after it is activated.
These alarms do not compromise service
performance and will be cleared after the upgrade
is complete.
OptiX OSN 8800_6800_3800

Upgrade Guide
1 Before You Start
1.5.2 Impact on the System After the Upgrade

Software Library
If new boards must be used on an NE after the NE is upgraded using the custom mode and
software for the new boards is included in the target software package, the software library
enables the new boards to obtain the required new software and the NE reports an
SWDL_PKG_NOBDSOFT alarm. Specifically, the software library automatically creates an
upgrade task after the new boards are inserted. You must manually start the upgrade task to
upgrade the new boards.
Software library has been supported since OptiX OSN 8800/6800/3800 V100R005C00. For
versions earlier than V100R007C00, the CF card on an SCC board can store the entire
software package. However, for V100R007C00, the CF card has only 1G free space, which is
not enough to store the entire V100R007C00 software package. Therefore, use the custom
mode to upgrade an NE to V100R007C00 and use the software library function to upgrade
new boards that are installed after the upgrade.
Upgrade new boards using the software library function using the following procedure:
Step 1 Insert a new board to the NE that has been upgraded using the custom mode. After about 10
minutes, an upgrade task starting with AutoUpgradeSWPKG is automatically created.
To view this task, choose Administration > NE Software Management > NE Upgrade
Task Management from the main menu. The NE Upgrade Task Management window is
displayed.
Step 2 Right-click the upgrade task and choose Start Task.
In the Task Start Confirmation dialog box, click Yes.
OptiX OSN 8800_6800_3800

Upgrade Guide
1 Before You Start
After the task is complete, Operation Succeeded is displayed.
----End
Impact on Alarm Monitoring

Table 1-5 describes the impact on alarm monitoring after the upgrade.
Table 1.5.2.I.1.1.1.1 Impact on Alarm Monitoring after the Upgrade
Alarm That May Be
Reported
IN_PWR_HIGH
IN_PWR_LOW
Impact
Boards that are being upgraded report these two alarms.
These two alarms do not compromise service
performance but you need to reset a threshold for the
input optical power.
ALS_ACTIVE
Boards that are being upgraded report this alarm. This

alarm does not compromise service performance. It
indicates that the ALS shuts down the laser.
CPW_ODUk_TEL_DOWN
NEs with the ASON feature enabled may report TE link

down, TE link degrade, or RSVP neighborhood down
alarms during the restart process after the upgrade.
Usually, these alarms will clear after the NEs restart. If
these alarms persist after the NEs restart, contact the local
Huawei engineers to handle the faults.
CPW_OTUk_TEL_DOWN
CPW_OMS_TEL_DOWN
CP_TEL_DOWN
CPW_ODUk_TEL_DEG
CPW_OTUk_TEL_DEG
CPW_OMS_TEL_DEG
CP_TEL_DEG
CPC_RSVP_NB_DOWN
OptiX OSN 8800_6800_3800

Upgrade Guide
1 Before You Start
1.6 Precautions
The precautions need pay attention to listed as follows:
When upgrading an NE, do not perform the following operations on the NE; otherwise,
the upgrade may fail or the NE configuration may be lost.
Remove and reinsert boards.
Replace the SCC board.
Upload configuration, performance, or alarm data.
During the upgrade, do not modify NE configurations. Configuration changes that are
made within 30 minutes before the Activate operation starts will be lost.
When uploading the upgrade software package to the PC through FTP or SFTP, use the
binary mode to transfer the file.
To upgrade equipment at a maintenance office, load the software package during the day,
and to perform the Dispense, Activate, and Commit operations at night.
Ensure that the source versions of the NEs are the same for the same upgrade task.
When performing the upgrade using the software package diffusion mode, ensure that
one upgrade task contains no more than one GNE and the subtending NEs are all under
the GNE.
Do not perform the Activate operation within 2 hours of when the upgrade time window
is scheduled to close. You may pause the upgrade task and continue it in the next upgrade
time window if necessary or manually roll back the NEs in the upgrade task to the source
version.
For the sake of upgrade stability, each upgrade task of software package loading mode
should contain no more than six NEs.
If the source version is OptiX OSN 8800/6800 V100R005C00SPC800, disable the IEEE
1588 synchronization function for the TN11ST2 board before the upgrade. Doing so
ensures that the time synchronization performance and accuracy are not impacted by the
upgrade. After the upgrade, enable the IEEE 1588 synchronization function for the
TN11ST2 board again. For details, see section 6.4.
If the synchronous Ethernet and IEEE 1588v2 functions are enabled in the current
version, upgrade the working and protection links separately when upgrading an NE in
package loading mode so that the two functions can work correctly. For details, see
section 6.5"Upgrading NEs Enabled with Synchronous Ethernet and IEEE 1588v2
Functions in Software Package Loading Mode."
If OptiX OSN 8800_6800_3800 NEs with 100G boards (TN12LSC or TN11LTX) need
to be upgraded to V100R006C03SPC500 or later, perform an upgrade by referring to
attachment 8 100G Board Upgrade Guide.
If OptiX OSN 3800 NEs are provisioned with TN11RAU2, TN11LEM24, TN12OPM8,
or TN11OMCA boards, or equipped with the SOM-based OSNR detection, replace the
TN22SCC boards with the TN23SCC boards for these NEs by referring to OptiX OSN
8800 6800 3800 V100R007C00 Parts Replacement and then upgrade the NEs. Note that
the TN22SCC board cannot be upgraded to OptiX OSN 8800_6800_3800
V100R007C00 or OSN 8800 6800 3800 V100R007C00SPC100 or OSN 8800 6800
3800 V100R007C00SPC200.
OptiX OSN 8800_6800_3800

Upgrade Guide
1 Before You Start
Before the upgrade, use the U2000 to check the gain of the OA boards on the NEs. If the
gain of an OA board is out of the specified normal range, adjust the gain and VOA
attenuation for the OA board, ensuring that the line power is the same before and after
the upgrade. For details about this procedure, see section 3.11"Adjusting the OA Gain."
If OptiX OSN 8800_6800_3800 V100R007C00SPC300 is upgraded from OptiX OSN

8800_6800_3800 V100R007C00 or OptiX OSN 8800_6800_3800
V100R007C00SPC100 and the IPA that uses auxiliary detection boards has been
configured on the NE, the IPA must be deleted and reconfigured after the upgrade is
completed.
After OptiX OSN 8800_6800_3800 V100R006C03SPC300 is upgraded to OptiX OSN

8800_6800_3800 V100R007C00SPC300, the TN11RAU106 board supports 11 types of
fibers, 6 more than the previously supported fiber types. To support all the 11 types of
fibers, the optical module parameter table of the TN11RAU106 board must be updated.
For information on how to update the parameter table, see Attachment 10 Operation
Guide to the Parameter Table Update Script for the 100G Raman Module.
For the TN53TQX, TN53TDX, TN55TQX, TN57TQX, TN57TDX, TN55TOX,

TN53NQ2, TN53ND2, TN53NS2, TN57NQ2, and TN57ND2 boards, when they are not
provisioned with OTN services, future-deployed services will be unavailable after a
package loading upgrade from OptiX OSN 8800_6800_3800 V100R007C00SPC200 or
an earlier version to OptiX OSN 8800_6800_3800 V100R007C00SPC300. To ensure
that future-deployed services will be available, perform a cold reset on the boards after
the upgrade.
DAS1 boards cannot be configured at OLA sites. If such scenario is present on a live
network, abnormalities may occur during an upgrade. For example, if the DAS1 and
TN13FIU boards are configured at an OLA site, the TN13FIU board may falsely report a
MUT_LOS alarm during an upgrade.
Generally, a MUT_LOS alarm is triggered on the TN13FIU board after the OSC_LOS
and MUT_LOS alarms are respectively reported on the OSC and OA boards. In this
scenario, however, because the DAS1 board is not supported at an OLA site, the
TN13FIU reports MUT_LOS when the OSC board reports OSC_LOS. During the
upgrade, the upstream OSC board undergoes a cold reset and therefore will cause the
local TN13FIU board to falsely report the MUT_LOS alarm.
On an NE that has customized software packages, if a board that is supported by the

current version but whose board software is not included in the customized software
package is inserted, an SWDL_PKG_NOBDSOFT alarm will be reported, and the
software library will automatically create an upgrade task. You can perform the upgrade
task to upgrade the board. For details, see "Software Library" in section 1.5.2 "Impact on
the System After the Upgrade".
Before an upgrade, you must upload the software package to the software library. For
details, see section 3.3 "Obtaining Target Upgrade Software".
Upgrade Flowchart
This chapter describes the upgrade procedure by chart and table.

Figure 2-1 describes the upgrade flow.
Figure 2.1.1.I.1.1.1 Upgrade flowchart
The amount of time spent on preparations for an upgrade and pre-upgrade check depends on the number
of NEs to be upgraded. For a complex network with many NEs, make preparations for the upgrade at
least one week ahead.
The upgrade duration is prolonged if the number of boards to be upgraded increases or the upgrade is
performed on a remote subtending NE.
Table 2-1 describes upgrade procedure, including Impact Level, Time Required and
Mandatory or Optional.
Table 2.1.1.I.1.1.1.1 Upgrade procedure
No.
Procedure
Prepare for the

upgrade
Prepare upgrade
environment
Impact
Level
Time
Required
(approximate)
Mandatory
or
Optional
High
23 days
Mandatory
High
Pre-upgrade check
2
Perform the upgrade
Copying files:
70 minutes
Mandatory
Dispensing:
15 minutes
Activation:
60 minutes
Committing:
15 minutes
Verify upgrade results
Medium
30 minutes
Mandatory
Perform version
rollback
Rollback before
activation
Low
40 minutes
Optional
Rollback after
activation
High
60 minutes
Preparing for the Upgrade
3.1 Preparing the Upgrade Checklists

This section describes which papers need to be printed before upgrade.
Print "Upgrade Record Table" in appendix A, "Pre-upgrade Checklist" in appendix B, and
"Upgrade Checklist " in appendix C.
3.2 Preparing the Upgrade Tool

This section describes how to prepare the upgrade tool DC.
Task Description
1.
If the upgrade tool DC is integrated in the U2000, ensure that the U2000 version is
iManager U2000 V100R006C02.
2.
If a standalone DC is used to perform the upgrade, ensure that the DC is available.
Prerequisites
The operator must have the user account and password for the U2000.
A user account with the super permission must be created prior to an upgrade.
Procedure
Step 1 Obtain the OptiX iManager U2000 V100R006C02 and its Installation Guide from Huawei
technical support engineers or from the CD released with the required version.
Step 2 Install the OptiX iManager U2000 V100R006C02 according to the Installation Guide.
When you use the U2000 for the first time, set the server to be upgraded and the directory to which the
package to be loaded is stored.
1.
Log in to the U2000. Choose Administration > NE Software Management > FTP
Settings from the main menu.
The following dialog box is displayed when you log in to the U2000 for the first time. Click
OK to close the dialog box.
2.
Click the System Information tab, and enter the IP address of the U2000 server in the
System IP Address field, The specified IP address and the NE IP address must belong to
the same network segment; otherwise, backing up the database and even the upgrade will
fail.
The IP address in the figure above is an example. The IP address of the U2000 server must be set based
on actual site information.
3.
Click the File Transfer Service Setting tab, and enter the directory to which the
software package of the target version is stored in the File Transfer Service Root
Directory field. Then click OK.
The values in the figure above are example values. The value of File Transfer Service Root Directory
must be set based on actual site information.
4.
Click the Transfer Protocol tab. On the tab page, select FTP or SFTP for File Transfer
Protocol and click OK.
5.
The Operation Result dialog box is displayed, indicating that the operation was
successful. Click OK.
SFTP server has been supported since OptiX OSN 8800/6800/3800 V100R006C03.
To upgrade only a non-gateway NE, use the Huawei file transport protocol. In this case, you do not need
to configure the FTP/SFTP server.
To upgrade only a gateway NE, use the FTP/SFTP protocol. In this case, you need to configure the
FTP/SFTP server. Keep the default settings for fields on other tab pages.
To upgrade both gateway NEs and non-gateway NEs, you need to configure the FTP/SFTP server.
File Transfer Service Root Directory is the default directory to which the database is backed up. The
backup directory for the database is created automatically.
----End
3.3 Obtaining Target Upgrade Software

This section describes how to obtain the target upgrade software and import it to the NE
Software Library of the U2000.
Task Description
Fill out a software upgrade application at http://support.huawei.com to obtain the target
software. Software obtained any other way is illegal and cannot be used.
Prerequisites
Before an upgrade, read the Release Notes for the target version for information about the
SCC board and the other boards.
Procedure
Step 1 Obtain the required software at http://support.huawei.com. Contact Huawei technical support
engineers for assistance.
Step 2 Save the software package on the U2000 server. (For a standalone DC, save the software
package on the DC server.) Decompress the software package, and save all the files in the
same directory under the root directory.
Step 3 Choose Administration > NE Software Management > NE Software Library
Management from the main menu of the U2000.
Step 4 In the window that is displayed, click Import.
Step 5 In the dialog box that is displayed, set NE Type.
Step 6 Click
next to the Path field. In the Select File dialog box, select the required file.
Step 7 In the Import dialog box, the DC automatically obtains the version of the software package
after the path information is determined. Confirm that the version is the same as the actual
version of the software package.
Step 8 If the version is correct, click OK to import the software package. After performing this step,
you do not need to manually specify the software package. Instead, you can simply select the
target version when you create an upgrade task.
----End
Result Verification
Verify that the name and version of the target software package downloaded by the DC are
correct.
3.4 Creating a User for the DC to Log In to the

Target NE
This section describes how to create a user for the DC to log in to the target NE. The data
center (DC) is a function module used by the U2000 for NE upgrades. Before upgrading an
NE, create a user for the DC to log in to the NE.
Use the szhw account for NE upgrades whenever possible. If the password does not meet requirements,
change the password before performing the upgrade.
Step 1 Create a user using the U2000.

Choose Administration > NE Security Management > NE User Management.
In the displayed window, select the required NE in the navigation tree and click
In the Result dialog box, click Close if "Operation succeeded" is displayed. If the operation
fails, contact Huawei engineers for assistance.
Right-click the NE User Management Table area and choose Add from the shortcut menu.
In the Add NE User window, set NE User, User Level, NE User Flag, New Password, and
Confirm Password, and click Apply. Then click OK to close the window after the user is
successfully added.
Valid values for User Level are Monitor Level, Operation Level, Maintenance Level, System Level,
and Debug Level. Valid values for NE User Flag are LCT NE User, EMS NE User, CMD NE User,
and General NE User. Set the two fields to Debug Level and General NE User, respectively.
Step 2 Assign the created user to the DC.

Choose Administration > NE Security Management > NE Login Management.
In the DC Login User Management window, select the required NE in the navigation tree,
then click the DC Login User Management tab and
.
Right-click the required NE in the DC Login User Management Table area and choose
Switch NE User from the shortcut menu.
Enter the user name and password of the created user in the User and Password fields, and
click OK.
In the Result dialog box, click Close if "Operation succeeded" is displayed. If the operation
fails, contact Huawei engineers for assistance.
----End
3.5 Checking NE Health Before Upgrading

(U2000 or Standalone DC)
Task Description
Use a script to perform a health check on an NE. The health check result shows the problems
(if any) that may affect the upgrade.
Precautions
The NEHealthCheck.zip file must be run on the U2000 or the standalone DC to perform an
extended check only.
The database check script is contained in the NE health check script.
Operation Procedure
Step 1 Save the NEHealthCheck folder in the Attachment 5 Scripts for Pre-Upgrade Check to the
root directory in drive D on a PC that is connected to the NE.
Step 2 Start the U2000 and choose Administration > NE Software Management > NE Data
Backup/Restoration from the main menu.
Step 3 Select the desired NEs, right-click and choose New Task > Package Upgrade/Downgrade
Task.
Step 4 In the Create Task [Package Upgrade] window, specify Task Name and click Query. When
the query is complete, the NE Table area displays the selected NEs. Click Close in the Query
Package Status dialog box. Click Next to proceed to the next step.
Step 5 Select the check box before Precheck only. Click Configure Precheck Items to configure
the Precheck operation.
Step 6 In the Configure Precheck Operation dialog box, select the check box before Extended
Check only. Then click
next to the Clear button and select the NEHealthCheck.zip
compressed file in D:/NEHealthCheck. Click OK.
Step 7 In the Operation Configuration [Package Upgrade] window, click Next. In the displayed
Confirmation [Package Upgrade] dialog box, click OK.
Step 8 The task is successfully created. Then in the NE Upgrade Task Management window, select
the created task, right-click and choose Start Task.
Step 9 After the task is executed, select a desired NE, and click Some Check to view the details in
the health check report.
The U2000 automatically generates the health check report *_out.html and save it to
\server\var\logs\Develop\DCServer\tkdll_log of the U2000 server installation directory after
performing the extended check. Users can view the health check report clearly.
----End
Result Verification
Open the *out.html file to check for the failed items. If the check result is ERROR, identify
the fault cause according to descriptions provided in Handling Suggestion in the *out.html
file and formulate a solution. If you cannot rectify the fault, contact Huawei upgrade
engineers.
If the extended check script fails to run, collect the logs in
\server\var\logs\Develop\DCServer\tkdll_log of the U2000 server installation directory, and
provide them to Huawei engineers for analysis. The following table lists the required logs.
1. Health check record files:

NEID_YYYY-MM-DD_HH-MM-SS_out.html
NEID_YYYY-MM-DD_HH-MM-SS_Err.html
2. Health checklog files:
NEID _ExtendCheckTCL_yyyymmdd_hhmmss.log
NEID_YYYY-MM-DD_HH-MM-SS_mfdb0.txt
NEID_YYYY-MM-DD_HH-MM-SS_mfdb1.txt
NEID_YYYY-MM-DD_HH-MM-SS_mfs.txt
NEID_YYYY-MM-DD_HH-MM-SS_sfdb0.txt
NEID_YYYY-MM-DD_HH-MM-SS_sfdb1.txt
NOTE
NEID indicates ID of an NE, YYYY-MM-DD indicates the date when scripts are run, and HH-MMSS indicates the time when scripts are run.
3.6 Checking NE Versions

This section describes how to check NE versions.
Task Description
Before upgrading NEs, check the NE versions to determine which NEs can be upgraded
directly to the target version and which NEs must be upgraded to an intermediate version first.
For information on the intermediate versions, see 1.2 and 1.3.
Procedure
Step 1 Choose Administration > NE Software Management > NE Data Backup/Restoration
from the main menu of the U2000.
Step 2 On the NE View tab page, click Update Version. This operation ensures that the information
about NEs to be upgraded is the same as the NE information saved on the U2000.
If the required ne not on the NE View tab page, click Refresh button on toolbar:
----End
Result Verification
In NE View, verify that all NE versions are displayed.
3.7 Checking Status of the NE Database

This section describes how to check the status of the NE database and make sure that the NE
works normally after the upgrade.
Task Description
Check the status of the NE database and make sure that the database is ready for storing data.
This is to ensure that the NE works as expected after the upgrade.
Precautions
1.
A database needs to be checked by running the database check scripts and by using the
database check tool. The database check scripts are contained in the health check scripts
and are mainly used to check for residual files in the database. The database check tool is
mainly used to check whether the NE database can be upgraded without affecting the
existing services on the NE.
2.
Obtain the database check tool from Attachment 3 Database Check Tool.
3.
The PC needs these environments: English or Chinese OS (Operating System); OS is

Windows XP; Microsoft Office and ZIP (RAR) tool.
Procedure
Step 1 Copy the CheckDataBase_Tool folder in the Attachment 3 Database Check Tool to the root
directory on drive D on a PC.
Step 2 Back up the NE database using the NE database backup function. For details, see Attachment
2 NE Database Backup, Restoration and Upload.
Step 3 Double-click the dbchkui.exe file in the D:\CheckDataBase_Tool directory to run the
database check tool. Click Browse in the displayed window. Then select the folder where the
backup NE database is stored. The NE database was backed up in Step 2.
Step 4 Select the Check Ver check box, specify Object Version as NGWDM_V1R7, and click
Check to check the NE database.
If the check result is displayed as OK, the database check is successful.
If the check result is displayed as Invalid, the database check failed.
When an error occurs during the database check, contact Huawei engineers. Do not reset or
upgrade anything until the error has been fixed.
----End
Result Verification
After the status of the NE database is checked, the database health check report is
automatically displayed. You can save this report for future data analysis. If an error is found
in the database, click the error code to switch to the error handling window. If the hyperlink
of the error is unavailable, manually obtain the error information in the Database
Check Report in D:\CheckDataBase_Tool.You can quickly handle the error according to
the information displayed in the window.
After the database file is repaired, check the database file again using the check tool. If the
check result is OK in green, the database is repaired. If you cannot repair the database file,
send the database files and the YYYYMMDDHHMMSS.txt file saved in the
D:\CheckDataBase_Tool\ToolResult directory to Huawei upgrade engineers for analysis and
rectification. Proceed with the upgrade only after the data has been rectified.
Figure 3-1 describes the information included in the database health check report.
Figure 3-1 the Database Health Check Report
3.8 Checking the Status of the ODUk SPRing

Protection Group
Task Description
Check the status of the ODUk SPRing protection group before an upgrade. Ensure that the
ODUk SPRing protection group is in the Idle state so that services are not affected during the
upgrade.
Precautions
None.
Procedure
Step 1 Log in to the U2000. On the Main Topology, right-click an NE to be upgraded and choose NE
Explorer.
Step 2 In the navigation tree, choose Configuration > ODUk SPRing. Select Protection Group, then
click Query on the lower right-hand pane. All current ODUk SPRing protection groups of the
NE and their switching statuses are displayed in the upper right-hand pane.
Step 3 If Switching Status of any of the ODUk SPRing protection groups is not Idle, check the
alarm status on the board of the corresponding channel. Address any faults before performing
the upgrade. If any of the faults cannot be fixed, contact Huawei upgrade engineers.
----End
Result Verification
Perform IStep 2 and IStep 3 again to query the switching status of ODUk SPRing protection
groups. Make sure that all ODUk SPRing protection groups are Idle.
3.9 Checking System Settings

If enabled, the automatic database backup and alarm synchronization functions of the U2000
or DC will affect the stability and efficiency of the upgrade (including the Load, Dispense,
Activate, and Commit operations). Therefore, disable these functions before the upgrade and
enable them again after the upgrade. The following procedure describes how to disable the
functions.
Step 1 On the U2000, choose Administration > NE Software Management > NE Backup Policy
Management from the main menu. If Backup Policy Status is set to Enable for the NE,
right-click the record and choose Disable Backup Policy from the shortcut menu.
Step 2 Choose Fault > Settings > Option > Auto Synchronize from the main menu. In the Alarm
Options dialog box, deselect the three check boxes on the right side of the window.
----End
3.10 Pre-upgrade Check for ASON NEs

3.10.1 Checking Consistency Between NMS Data and
NE Data
Task Description
Ensure that the NMS data is consistent with the NE data. If the NMS data is inconsistent with
the NE data, synchronize their data first.
Precautions
None.
Procedure
Step 1 Choose Configuration > NE Configuration Data Management from the main menu.
Step 2 Select all the NEs that need to be upgraded and click Check Consistency.
Step 3 If the data on some NEs is inconsistent with the data on the NMS, select the NEs and click
Synchronize.
Step 4 If the data on these NEs is still inconsistent with the data on the NMS, right-click each of the
NEs and choose Upload to upload their data to the NMS.
----End
3.10.2 Checking ASON Trail Status

Task Description
Ensure that ASON trails are normal. If there are any service alarms, handle the faults
immediately.
Precautions
None.
Procedure
Step 1 Choose Configuration > WDM/OTN ASON > ASON Trail Management from the main
menu.
Step 2 Ensure that Alarm Status for the current trails is No Alarm.
----End
3.10.3 Checking for Interrupted or Downgraded TE

Links
Task Description
Ensure that no TE link is interrupted or downgraded.
Precautions
None
Procedure
Step 1 Choose Configuration > WDM/OTN ASON > TE Link Management from the main menu.
Step 2 Click Synchronize.
Step 3 Check whether alarms are generated on TE links. If yes, confirm the impact of the alarms. If
the alarms are caused by the transport plane alarms and have no impact on the current
services, you can handle the alarms after the upgrade. If the alarms are not caused by the
transport plane alarms or they have affected the current services, you must clear the alarms
before the upgrade.
Step 4 Check whether the number of TE links is correct. If the number of TE links is incorrect,
ensure that the number is correct before the upgrade.
----End
3.10.4 Backing Up ASON Trail Information on the

NMS
Task Description
For the purpose of security, gather all information about ASON trails in a report before
performing the upgrade. If trail attributes change after the upgrade, adjust the trail attributes
based on the report.
Precautions
None
Procedure
menu.
Step 2 Select all the services and click Report to save the information about all the ASON trails in a
report on the NMS computer.
----End
3.10.5 Locking the Rerouting Function for Networkwide ASON Trails

Task Description
Ensure that the ASON trails do not change during the upgrade.
Precautions
None.
Procedure
menu.
Step 2 Right-click a service and choose Set Routing Attributes.
Step 3 In the Set Routing Attributes dialog box, select Locked for the Reroute Lockout text box.
Then click OK.
Step 4 Verify the lockout status of the service.
During the upgrade, interrupted ASON services cannot be restored by means of rerouting,
because the rerouting function is locked for the ASON trails.
Users can lock or unlock the rerouting function for all of the involved ASON trails at one time.
----End
3.10.6 Downgrading ASON Trails to Traditional Trails

Task Description
Downgrade all ASON trails to traditional trails before performing the upgrade. This section
provides an example of describing how to downgrade a WDM ASON trail to a traditional
WDM trail.
Applicable Versions
The source version is OptiX OSN 6800 V100R003C02.
Precautions
None.
Procedure
Step 1 From the main menu of the U2000, choose Configuration > WDM/OTN ASON > ASON
Trail Management.
Step 2 Select the WDM ASON trail that needs to be downgraded to a traditional WDM trail, and
check its management status.
Step 3 If the trail is not managed, right-click it and choose Downgrade to Traditional WDM Trail
from the shortcut menu. When the downgrade is successful, go to Step 7.
Step 4 If the trail is being managed, right-click it and choose Query Relevant Trails from the
shortcut menu.
Step 5 In the Manage WDM Trail window, right-click the desired ASON trail and choose
Downgrade to Traditional WDM Trail.
Step 6 In the Downgrade to Traditional WDM Trail window, click OK.
Step 7 Double-click the source NE in the Main Topology after the ASON trail on the NE has been
downgraded to a traditional WDM trail. In the Running Status window, right-click the NE
and choose NE Explorer.
Step 8 In the navigation tree, choose Configuration > Optical Cross-Connection Management.
Click the NE-Level Optical Cross-Connection tab and click Query.
Step 9 Click the
(Switch NE) button on the menu bar.
Step 10 Sequentially query the cross-connections forming the downgraded ASON trail on other NEs.
Step 11 From the main menu of the U2000, choose Service > WDM Trail > Search for WDM Trail
to search for the downgraded ASON trail.
During the search, the Search for WDM Trail dialog box is displayed, showing the search
progress.
Step 12 When the search is complete, choose Service > WDM Trail > Manage WDM Trail from the
main menu.
Step 13 Verify that the WDM trail downgraded from the ASON trail is displayed in the Manage
WDM Trail window.
If the previously downgraded ASON trail is not displayed in the search result, wait for 5 minutes and
then perform the search again.
----End
3.10.7 Disabling Optical Parameter Constraints for

Optical-Layer ASON Trails
Task Description
Ensure that optical parameter constraints for optical-layer ASON trails are disabled before the
upgrade and are enabled again after network-wide NEs are upgraded. This is because the
optical parameters of the source and target versions are incompatible.
Applicable Versions
The source version is OptiX OSN 6800 V100R004C04SPC800 or OptiX OSN 8800
V100R002C02SPC800 in optical-layer ASON offices with optical parameter constraints
enabled.
Precautions
None.
Procedure
Trail Management.
Step 2 Right-click an ASON trail and choose Disable Optical Parameter Constraints.
----End
3.11 Adjusting the OA Gain

Task Description
Before the upgrade, use the U2000 to check the gain of the OA boards on the NEs. If the gain
of an OA board is out of the specified normal range, adjust the gain and VOA attenuation for
the OA board, ensuring that the line power is the same before and after the upgrade.
Applicable Versions
The source version is earlier than OptiX OSN 8800/6800/3800 V100R007C00.
Precautions
None.
Procedure
Step 1 On the Main Topology of the U2000, double-click the NE that has OA boards using extended
gain.
Step 2 In the window that is displayed, click the Signal Flow Diagram tab.
Step 3 Right-click the OA board on the NE and choose WDM Configuration.
Step 4 In the navigation tree of the window that is displayed, select the OA board, and choose
Configuration > WDM Interface. On the right of the window, click the Basic Attributes tab
and locate the OUT port on the OA board.
Step 5 Set Normal Gain (dB) to a value for the OUT port and ensure that this value is within the
normal gain range for the OA board.
Step 6 Click Apply.
Step 7 Click Query to verify that the setting has been successfully applied.
----End
Performing the Upgrade
This chapter describes how to perform the upgrade.
4.1 Creating Upgrade Tasks

This section describes how to create an upgrade task and configure operations.
Step 1 Choose Administration > NE Software Management > NE Data Backup/Restoration
from the main menu of the U2000.
Step 2 On the NE View tab page, create an upgrade task for the NE to be upgraded. Right-click the
equipment item, and choose New Task from the shortcut menu.
To use the software package loading mode, right-click in the upgrade task table and
choose New Task > Package Upgrade/Downgrade Task from the shortcut menu. Note
that this mode is generally used to upgrade only a few NEs or multiple GNEs in batches.
To use the software package diffusion mode, right-click in the upgrade task table and
choose New Task > Package Diffusion Upgrade Task from the shortcut menu. Note
that this mode is generally used to upgrade NEs on a tree or ring network in batches.
When you use the software package loading mode, each task should contain no more than six NEs to
ensure stable upgrade performance. You can create multiple upgrade tasks to upgrade more than six
NEs in batches.
When using the software package diffusion mode, observe the following requirements:
(1) Each upgrade task should contain no more than 15 NEs.
(2) One upgrade task can contain one GNE or none, and the subtending NEs in the task must be
under the one GNE.
Step 3 In the dialog box that is displayed, define the task name and set NE Type and NE Version. In
the NE Table area, select the check box before the desired NE. Then click Next.
Click Upgrade for Task Type. If you want to downgrade an NE to an earlier version, Click
Downgrade for Task Type. Considering that the downgrade process is complex, contact
Huawei engineers before downgrading the system for guidance.
In a package diffusion upgrade task, an NE can be activated at two levels: NE level and board level. For
details on the two activation levels, see section 1.4"Methods for Assigning NEs to an Upgrade Task."
The NE-level activation is recommended.
Step 4 Configure the operations for the upgrade task. Select all of the operations.
Select Custom package because a 1G CF card is not large enough to store the entire software
package for V100R007C00. OptiX OSN 8800 V100R002C02SPC800 and OptiX OSN
6800/3800 V100R004C04SPC800 do not support the loading of customized software
packages. Therefore, check whether package loading needs to be performed for a second time.
For details, refer to 6.7"Checking Whether Package Loading Needs to Be Performed for a
Second Time."
Select the Pause Before Current Operation check box for the Dispense and Activate
operations. Doing so inserts a pause in the upgrade task before the Dispense and Activate
operations.
Except Precheck, Postcheck, and Backup, all operations are mandatory and must be selected.
Otherwise, the upgrade will fail. After selecting the required operations, click the corresponding
items in the Configure Operation field to proceed with the configuration. For example, click
Configure PreCheck Items. There is no configuration item for Dispense and Commit.
If Pause Before Current Operation is selected, the upgrade pauses before the current operation and
you need to choose Continue Task to proceed with the operation.
The Precheck and Postcheck operations are optional. However, they are recommended, because
they ensure that the upgrade is performed properly and they facilitate querying information in the
event of an exception. The Backup operation is to back up the NE database stored on the NE. To
shorten the duration of upgrade operations performed at night, perform the precheck during the day
whenever possible. After the precheck, you may need to pause the upgrade to review the precheck
result. To insert a pause before the backup operation, select the Pause Before Current Operation
check box for the Backup operation.
If the Force to load selected GNE through FTP/ SFTP check box is selected, configure the local
FTP/SFTP server on the PC. The software package is loaded using the FTP/SFTP for gateway NEs,
which improves the loading speed; however, for non-gateway NEs, the software package is still
loaded using the Huawei file transport protocol. Do not select this option or configure the FTP/SFTP
server on the PC.
When the Custom package: Load the required software packages automatically based on
boards, improving the load efficiency check box is selected, the NE loads software only for the
boards housed on the NE instead of loading the whole software package. This improves the loading
efficiency. In this case, if a new board is inserted into the NE after the upgrade, a software file load
is required. (This function is applicable only when the source version is OptiX OSN 8800/6800/3800
V100R005C00 SPC800 or later.)
If an upgrade task has already been created for the same target software version, users can quickly
select a software package by specifying Target Version in the window above. However, to ensure
that a correct software package is selected, perform Step 5 below in this section. Note that Target
Version in the window can be left unconfigured.
If the start time is not set, you need to start the upgrade task manually after the task is created and
configured.
Step 5 Select the correct version from the Target Version drop-down list. The DC will automatically
select the corresponding software package based on the selected version and automatically
display the file selection dialog box, prompting you to confirm the information. After
confirming the information is correct, click OK.
If you have not imported the required software package to the software library when you prepare for the
upgrade, the target version will not be displayed when you click the Target Version drop-down list. At
this time, you still can click Configure Package to load the required software package. In the dialog box
that is displayed, click
. Then select the .pkg file in the software package saved on the U2000
server and click OK.
Step 6 Click Configure Activation in the Configure Operation field in the Operation
Configuration [Package Upgrade] dialog box to configure the Activate operation.
The purpose of grouped activation is to shorten the activation time without affecting ongoing
services as much as possible.
A gateway NE and a non-gateway NE cannot be allocated to the same group. Otherwise, the
non-gateway NE may be unreachable during the activation process, leading to an upgrade
failure.
For details on how to re-organize groups, see section 1.4.
Pause Before Current Operation in step 4 and Activation Time in step 7 are mutually
exclusive. The upgrade pauses before the Activate operation if Pause Before Current
Operation is selected. Therefore, the activation time that is set in step 7 does not take effect.
To continue with the activation, right-click the desired task and choose Continue Task from
the shortcut menu.
Do not select the Forced and concurrent activation check box, because all groups are
concurrently activated in this activation mode, which interrupts services.
In a package diffusion upgrade task, while the Activation Level is Board Level, the board grouping is
implemented automatically and cannot be changed.
Two or more NEs can be activated in groups. By default, a group contains only one NE. The following
section uses three NEs as an example to describe grouped activation, including creating a group, deleting
a group, moving an NE up, and moving an NE down.
1.
Click the Get Default Activation button.
2.
Move an NE up or down. You can click
to move an NE to the previous group or click
to move an NE to the next
group.
3.
Delete a group. Select the desired group, click
. All NEs in the group are moved to the next group. To enable all the NEs
to activate at the same time, retain only one group and delete the other groups.
Step 7 Click Next in the Operation Configuration [Package Upgrade] dialog box. The
Confirmation [Package Upgrade] dialog box is displayed. Check the configurations of the
upgrade task. If they are correct, click OK. If any of the configurations need to be modified,
click Previous to display the Operation Configuration [Package Upgrade] dialog box
described in Step 4 and modify the configurations. Click OK after you verify that all the
configurations are correct.
The configurations cannot be modified after the upgrade task is started. Therefore, check the
configurations before you click OK.
----End
4.2 Starting Upgrade Tasks

This section describes how to start upgrade task and deal with errors occur during the
upgrade.
If any errors occur during the upgrade, see chapter 6"Troubleshooting."
The OptiX OSN 8800/6800/3800 V100R007C00SPC100/SPC200/SPC300 supports error

tolerance. Therefore, the upgrade task is suspended if one or more boards fail to be activated
during an upgrade to OptiX OSN 8800/6800/3800 V100R007C00 from any of the following
versions:
OSN 8800 V100R002C02SPC800
OSN 6800_3800 V100R004C04SPC800
OSN 8800/6800/3800 V100R005C00
OSN 8800/6800/3800 V100R006C00
OSN 8800/6800/3800 V100R006C01
OSN 8800/6800/3800 V100R006C03
OSN 8800/6800/3800 V100R007C00
The upgrade task is suspended if one or more boards fail to be activated in the activation
process. If this occurs, determine whether to continue the activation or to roll the NE back
based on the impact on services. For details on how to perform the rollback, see 6.1.2"Manual
Rollback."
Step 1 Start an upgrade task. Choose Administration > NE Software Management > NE Upgrade
Task Management from the main menu. Right-click the desired upgrade task and choose
Start Task from the shortcut menu. In the dialog box that is displayed, click Yes.
During the upgrade, the overall upgrade progress is displayed.
After a successful backup, the U2000 creates the backup/NE-ID/ yyyymmddhhmmss/dbf.pkg

directory in the root directory that maps to the value of File Transfer Service Root Directory. In
the directory, NE-ID indicates the ID of the NE, yymmdd indicates the year, month, and day of the
backup, and hhmmss indicates the time the backup file was created.
If the upgrade fails at the Backup phase, ask field engineers to handle exceptions and then perform
the upgrade again.
If the upgrade fails at the Load Software, Dispense, Activate, or Commit phase, see section 6.1.1
"Common Causes of Rollback " and make sure that the target file is correct. Then perform the
upgrade again after the field engineers handle the exceptions.
If the upgrade fails at the Postcheck phase, check whether the connection of the current network is
suitable for upgrades and ask field engineers to handle the exceptions.
Step 2 Confirm that the upgrade is complete. After all the preceding upgrade steps are performed,
check whether the Operation State field for each operation displays Success.
Step 3 Restore the system settings. If you disabled the automatic database backup and alarm
synchronization functions when preparing for the upgrade, enable them again now. Before
performing another upgrade, you must disable the functions again according to section
3.9"Checking System Settings."
----End
Verifying the Upgrade
This chapter describes how to verify the Current Software Version and Equipment Operating
Status after the upgrade.
5.1 Verification Checklist

Verification check items listed in table 5-1:
Table 5.1.1.I.1.1.1.1 Verification checklist
No.
Item
Expected Result
Software version
The NE software version is the target version and the

board software version is the target version after the
upgrade is complete.
Equipment operating
status
The services are normal, no configuration data is

missing, and no unexpected alarms occur.
5.2 Verification of the Current Software

Version
This section describes how to check the Current Software Version.
Task Description
Verify that the software versions of the SCC and other boards are the target versions.
Procedure
Step 1 Check whether the version of the software package is
V100R007C00SPC100/SPC200/SPC300. On the U2000, choose Administration > NE
Software Management > NE Data Backup/Restoration from the main menu. In NE View,
click Update Version.
Step 2 If the version is incorrect, contact Huawei engineers for support.

----End
5.3 Verification of the Equipment Operating

Status
This section describes how to check the Equipment Operating Status.
Task Description
Verify that the equipment functions properly, services are normal, and no unexpected alarms
occur.
Precautions
None
Procedure
Step 1 On the Main Topology on the U2000, right-click the NE to be upgraded and choose Browse
Current Alarms.
Step 2 Check all alarms on the NE. Right-click an alarm and choose Print > Print All Records to
print the alarms.
----End
Result Verification
1.
The services are normal and there are no unexpected alarms (most importantly, no
service-affecting alarms) or performance events.
2.
Ensure that there are no alarms starting with SWDL, COMMUN_FAIL, BD_STATUS,
BD_NOT_INSTALLED, HARD_BAD, BOOTROM_BAD, BIOS_STATUS,
DBMS_PROTECT_MODE, NESTATE_INSTALL, DB_RESTORE_FAIL,
SUBRACK_ID_MISMATCH, SUBRACK_LOOP, or SUBRACK_ID_CONFLICT. For
details on how to clear the alarms, see the Alarms and Performance Events Reference.
5.4 Verifying ASON NE Upgrade Result
Unlock the rerouting function of NEs every time the NEs are upgraded, and lock the function
again before upgrading them the next time.
5.4.1 Checking ASON Trail Status

Task Description
Ensure that ASON trails are normal. If there is a service alarm, handle the fault immediately.
Precautions
None.
Procedure
menu.
Step 2 Ensure that Alarm Status for the current trails is No Alarm.
Step 3 If alarms have occurred in the ongoing services, handle the alarms first.
----End
5.4.2 Unlocking the Rerouting Function for ASON

Trails
Task Description
Unlock the rerouting function for the ASON trails whose rerouting function was locked
during upgrade preparations. After the rerouting function is unlocked, the services over the
trails can be rerouted again.
Precautions
None.
Procedure
menu.
Step 2 Right-click a trail and choose Set Routing Attributes from the shortcut menu.
Step 3 In the Set Routing Attributes dialog box, set Reroute Lockout to Unlocked. Then click
OK.
Step 4 Verify that the trail is unlocked.
----End
5.4.3 Changing Flooding Modes for Electrical-Layer

Links (Electrical-Layer ASON Network)
Task Description
After NEs are upgraded throughout the network, users can specify a mode for flooding link
information at the electrical layer to improve the network capability (especially for a large
network). Two modes are available: flooding that combines all the ODU links into one ODUk
link and flooding that streamlines information about tributary links.
Precautions
The link flooding mode can be set only after the NEs are upgraded throughout the network. In
addition, NEs on the network must use the same link flooding mode. NG WDM NEs of
version V100R006C00 or earlier cannot identify the new link flooding mode. If the first node
of an ASON service is an NE of version V100R006C00 or earlier, the creation, rerouting, and
optimization of the service will not use TE links using the new link flooding mode. If
different NEs have different flooding modes, routing policies cannot be fulfilled correctly.
During the process of switching to a new link flooding mode, the functions of rerouting and
re-creating services must be disabled. If the time for network-wide NEs to complete the
switching is greater than 10 minutes, the function of deleting residual cross-connections must
be disabled for all the NEs. If the function is enabled, residual cross-connections are likely to
be deleted incorrectly. After setting the flooding modes network-wide, re-enable the function
of deleting residual cross-connections.
Procedure
Step 1 Run the :lim-get-otn-flood-type command to query the current link flooding mode.
If "Link-Unit-Flood-Flag" is 1, ODU0 links are combined into ODU1 links for flooding; if the
value is 2, all ODU links are combined into ODUk links for flooding.
If "Link-Flag" is 1, all the tributary links are flooded; if the value is 2, only streamlined
information about tributary links is flooded.
Step 2 Before changing the flooding mode, run the :ion-set-rm-clear-xc:disable command to
disable the function of deleting residual cross-connections for network-wide NEs.
Step 3 Run the :ion-get-rm-clear-xc command to verify that the function for deleting residual crossconnections is disabled.
If "disable" is displayed in the command output, the function is successfully disabled.

Step 4 Run the :lim-get-otn-flood-type command by specifying Link-Unit-Flood-Flag and LinkFlag as 2, as shown in the following figure.
Step 5 Run the :lim-get-otn-flood-type command to verify that the setting is successful.
Step 6 Run the ion-set-rm-clear-xc:enable command to re-enable the function of deleting residual
cross-connections for network-wide NEs.
Step 7 Run the :ion-get-rm-clear-xc command to verify that the function for deleting residual crossconnections is enabled.
If "enable" is displayed in the command output, the function is successfully enabled again.
----End
5.4.4 Upgrading Traditional Trails to ASON Trails

Task Description
Upgrade the traditional trails that are previously downgraded back to ASON trails.
Precautions
The OptiX OSN 6800 V100R003C02 does not support optical parameters. Therefore, before
upgrading traditional trails (downgraded from ASON trails) to ASON trails, set Optical
Parameter Verify to Disabled.
Applicable Versions
The source version is OptiX OSN 6800 V100R003C02.
Procedure
Step 1 From the main menu of the U2000, choose Service > WDM Trail > Manage WDM Trail.
Step 2 Right-click the required traditional WDM trail and choose Upgrade to WDM ASON Trail
from the shortcut menu.
Step 3 In the ASON Trail to Be Upgraded area of the Upgrade to WDM ASON Trail window, set
Class, Lockout, Policy, and CrankBack based on the settings for the original ASON trail.
Particularly, set Verify Optical Parameters to Disabled. Then click OK. After the trail is
upgraded successfully, a message is displayed, asking you whether to view the trail in the
WDM/OTN ASON Trail Management window.
Trail Management.
Step 5 Check whether alarms are reported for the WDM ASON trail that is newly upgraded from a
traditional WDM trail. If alarms are reported, handle the alarms before proceeding to the next
task.
----End
5.4.5 Enabling Optical Parameter Constraints for

Optical-Layer ASON Trails
Task Description
After network-wide NEs are upgraded, enable optical parameter constraints for optical-layer
ASON trails again.
Precautions
None.
Applicable Versions
The source version is OptiX OSN 6800 V100R004C04SPC800 or OptiX OSN 8800
V100R002C02SPC800 in optical-layer ASON offices with optical parameter constraints
enabled.
Procedure
Trail Management.
Right-click an ASON trail and choose Enable Optical Parameter Constraints from the
shortcut menu.
----End
5.4.6 Changing Flooding Modes for Optical-Layer

Links (Optical-Layer ASON Network)
Task Description
After network-wide NEs are upgraded, you can specify a mode for flooding optical-layer link
information to improve the network capability (especially for a large network). Two modes
are available: independent flooding of optical-layer links and universal flooding of opticallayer links through OTU groups.
Precautions
The optical-layer link flooding mode can be set only after NEs are upgraded throughout the
network. In addition, NEs on the network must use the same link flooding mode. NEs of a
version earlier than V100R007C00 cannot identify the new link flooding mode. If the first
node of an optical-layer ASON service is an NE of a version earlier than V100R007C00, the
node cannot identify the new link flooding mode. As a result, the creation, rerouting, and
optimization of the ASON service and the upgrade of static services will not use TE links
using the new link flooding mode. During a switchover between optical-layer link switching
modes, the service rerouting functions must be locked. For the method of locking the
rerouting function, see section 3.10.5 "Locking the Rerouting Function for Network-wide
ASON Trails."
If NEs on the network have different optical-layer link flooding modes, routing policies
cannot be fulfilled correctly. If it takes more than 10 minutes for network-wide NEs to
complete a switchover to the required optical-layer flooding mode, the residual crossconnection clearing function must be locked for all the NEs. If the function is enabled,
required cross-connections may be deleted while residual cross-connections may be retained.

After setting the optical-layer link flooding mode network-wide, unlock the service rerouting
and rebuild functions and enable the residual cross-connection clearing function.
Applicable Versions
The source version is earlier than V100R007C00.
Procedure
Step 1 In the Navigator, run the :lim-get-och-flood-type command to query the current optical-layer
link flooding mode.
If "flood-type" is 1, optical-layer links are flooded independently. If it is 2, optical-layer links

in one OTU group are flooded together.
Step 2 Before changing the optical-layer link flooding mode, run the :ion-set-rm-clear-xc:disable
command to disable the residual cross-connection clearing function for NEs throughout the
network.
Step 3 Run the :ion-get-rm-clear-xc command to verify that the residual cross-connection clearing
function has been disabled.
If "disable" is displayed in the command output, then the function has been disabled.
Step 4 Run the :lim-set-och-flood=type:2 command to universally flood optical-layer links that
belong to the same OTU group.
Step 5 Run the :lim-get-otn-flood-type command to verify that the setting is successful.
Step 6 Run the ion-set-rm-clear-xc:enable command to enable the residual cross-connection

clearing function network-wide.
Step 7 Run the :ion-get-rm-clear-xc command to verify that the residual cross-connection clearing
function has been enabled again.
If "enable" is displayed in the command output, then the function has been enabled
successfully.
----End
Troubleshooting
This chapter describes how to deal with errors occur during the upgrade.
6.1 Version Rollback

This section describes how to deal with version rollback and check software version and
equipment operating status after rollback.
In the upgrade, if a rollback occurs without a clear cause, collect information using the script
provided in the Attachment 4 Scripts for Collecting SCC Data. Then send the collected
information to Huawei engineers.
If a rollback occurs in the process of loading or if the software loading is abnormally stopped,
you can try to perform the failed operation again.
6.1.1 Common Causes of Rollback
After you click Start Task, the file copying process fails because the communication
between the FTP/SFTP server and the NE is abnormal. One cause for this type of
communication failure is that a large number of bit errors occur in the communication
channels on the NE.
During the process of package dispensing or activating files, the communication between
the SCC board and another board stops because the board is removed, the board is reset,
the SCC is reset (not the reset caused by the activation command), or the network cable
between the master and slave subracks is disconnected.
There is insufficient space on the board or the SCC.
The rollback command is issued to perform the rollback manually.
Rollback Applicable Stages

Step 1 A rollback at the file copying stage occurs as follows:
1.
After you click Start Task, the process starts updating the files in the OFS2 of the active
SCC. A rollback in this case neither triggers a reset of the board nor affects services.
Such a rollback is generally caused by the following problems:
Communication fails.
2.
The .pkg file is missing.
The remaining space on the SCC board is insufficient.
In any of these cases, resolve the problem before resuming the upgrade.
Step 2 A rollback occurs at the dispense stage.

The dispense process refers to the process of updating the software of each board in a
specific order, if updating is required. A rollback at the dispense stage may cause a loss
of files and reset of boards.
Step 3 For a rollback at the Unactivated stage
1.
If the Activate or Dispense operation fails at one or more boards on the NE, and the
upgrade task is suspended.
2.
Click Some cards of this NE are isolated. The Isolation Room tab page is displayed.
Determine whether the boards in the list are in the protection groups and whether
services are affected.
3.
If services are affected, click Rollback to roll the NE back to the source version.
4.
In Isolation Room, an NE will pause after each operation is completed.
5.
If the Dispatch operation fails, click Continue. If the Activate operation fails with
Activated and Uncommitted displayed in the Resource State field and this failure does
not affect the upgrade task, click Continue.
6.
If the Activate operation fails with Activated Pended displayed in the Resource State
field and this failure does not affect the upgrade task, click Retry.
7.
After the NE is successfully upgraded, click Free Isolation for each isolated board. Then
the boards with upgrade failures will be matched with software. After the software match
is completed, you can query board version information. Make sure that the current
version information is consistent with the target version information. If the upgrade
cannot be performed on these boards, contact the upgrade contact person in the
maintenance group for help.
Step 4 A rollback at the Activate stage occurs as follows:

The Activate process refers to the process of resetting the boards that are loaded with
software in a specific order. A rollback in this case may cause a loss of files and reset of
boards. The details are as follows:
The rollback of the SCC directly resets and runs the original software. The switchover of the
active and standby SCCs is performed if the FPGA is upgraded.
If a rollback occurs at the Activate stage, take actions according to Table 6.1.1.I.4.1.1.1.
Table 6.1.1.I.4.1.1.1 Corrective measures for handling a rollback at the Activate stage
Rollbac
k
Method
State
After
Rollback
Corrective Measures
Manual
Normal
1. Right-click the upgrade task and choose Delete Task

from the shortcut menu, as shown in Figure 6.1.1.I.4.1.2.
2. Re-create the upgrade task. Then repeat 4.1.1 IStep 4 to
configure the upgrade operations. Specifically, in the
Operation Configuration [Package Upgrade] window,
select all the operations.
Auto
CPY_FILE
_END
1. Attempt to perform the upgrade task again.

2. If the attempt fails, delete the upgrade task. Re-create the
upgrade task and repeat 4.1.1 IStep 4 to configure the
upgrade operations. In this case, select Dispense, Activate,
Postcheck, and Commit in the Operation Configuration
[Package Upgrade] window.
Figure 6-1 describes how to delete an upgrade task of U2000.
Figure 6.1.1.I.4.1.2 Deleting a task
----End
6.1.2 Manual Rollback

Application Scenario
In the following situations, the upgrade must be stopped and you must roll the NEs back to
the source version:
1. The software version is found to be incorrect during the upgrade.
2. The upgrade fails.
3. Insufficient time is left in the upgrade time window after the Dispense operation.
4. Critical errors are found during the postcheck.
A manual rollback can be performed after the Load Package operation but before the Commit
operation. After the Commit operation, a manual rollback is not allowed.
Rollback Operations
Step 1 Right-click the NE and choose Rollback from the shortcut menu.
Step 2 The Operation column should display Rollback.
If the retry operation is successful, ignore the subsequent contents of this chapter. Wait until the upgrade
is complete.
----End
6.1.3 Version Rollback Verification

Check items after version rollback listed in table 6-2:
Table 6.1.3.I.1.1.1.1 Rollback verification checklist
No.
Item
Expected Result
Software
version
The software package version is the same as the

version before the upgrade is performed.
For details, see section 3.6"Checking NE
Versions."
Actual
Result
Equipment
operating status
No abnormal alarms occur, and services are

normal.
6.2 Performing the Downgrade

Performing the downgrade, see "Attachment 1 Performing the Downgrade".
6.3 NE Database Backup and Restoration

Performing the NE database backup, restoration and upload, see "Attachment 2 NE Database
Backup, Restoration and Upload".
6.4 Disabling and Enabling IEEE 1588v2 Time

Synchronization on TN11ST2 Boards
6.4.1 Disabling IEEE 1588v2 Time Synchronization on
TN11ST2 Boards
Task Description
Before performing the upgrade, disable IEEE 1588v2 time synchronization on TN11ST2
boards of all NEs to be upgraded by deleting the time synchronization ports (PTP ports) on
the TN11ST2 boards. This ensures that the upgrade does not affect the time synchronization
performance and accuracy on the network.
Precautions
1.
This operation applies only to scenarios in which physical clock and IEEE 1588v2 time
synchronization is configured. This operation does not apply to scenarios in which PTP
clock and IEEE 1588v2 time synchronization is configured. For the latter situation, no
workaround is available.
2.
This operation is required only when the equipment is upgraded from V100R005SPC800
to a later version.
3.
If a GPS backup is used for the base station or PTN equipment, it is recommended that
you enable the base station or PTN equipment to trace the GPS before you perform the
upgrade, and not to disable IEEE 1588v2 time synchronization. After performing the
upgrade, enable IEEE 1588v2 time synchronization on the TN11ST2 boards again and
re-enable IEEE 1588v2 time synchronization throughout the network.
Applicable Versions
The source version is OptiX OSN 8800/6800 V100R005C00SPC800.
Procedure
Explorer.
Step 2 In the navigation tree, choose Configuration > Clock > PTP Clock > Clock
Synchronization Attribute. Then in the right side of the window, click Port Status.
Step 3 Click Query. Record the port data, such as the data in the red circles in the following figure.
Step 4 Delete all PTP ports with IEEE 1588v2 enabled on the RX2/TX2 boards of the NEs
connecting to PTN equipment.
In the NE Explorer of each NE connected to PTN equipment, select the port that needs to be
deleted and click Delete.
In the dialog box that is displayed, click OK to delete the selected port.
Step 5 Click Query to confirm that the selected PTP port has been deleted.
----End
6.4.2 Enabling IEEE 1588v2 Time Synchronization on

TN11ST2 Boards
Task Description
After performing the upgrade, enable IEEE 1588v2 time synchronization on the TN11ST2
boards of the upgraded NEs by adding the PTP ports that were deleted before the upgrade.
This ensures proper time synchronization throughout the network.
Precautions
None
Applicable Versions
The source version is OptiX OSN 8800/6800 V100R005C00SPC800.
Procedure
Explorer.
Step 2 In the navigation tree, choose Configuration > Clock > PTP Clock > Clock
Synchronization Attribute. Then in the right side of the window, click Port Status.
Step 3 Click New.
In the dialog box that is displayed, select the required board from the Board drop-down list.
Select the ports where IEEE 1588v2 needs to be enabled in the Available Port area and click
to add the ports to the Selected Port area. Then click Apply.
Step 4 Click Query to confirm that the selected port is successfully added and the port data is the
same as that configured before the upgrade.
----End
6.5 Upgrading NEs Enabled with Synchronous

Ethernet and IEEE 1588v2 Functions in
Software Package Loading Mode
Task Description
This task is to upgrade the working and protection links separately on ring networks that are
enabled with the synchronous Ethernet and IEEE 1588v2 functions. This task ensures that the
synchronous Ethernet and IEEE 1588v2 functions can work correctly.
Precautions
This operation applies to ring networks that are enabled with the synchronous Ethernet and
IEEE 1588v2 functions, and it does not apply to chain networks that are not configured with
protection trails. When chain networks are upgraded in package loading mode, the
downstream clock and time sources may switch and the clock and time performance may
deteriorate.
Applicable Versions
Versions in which the synchronous Ethernet and IEEE 1588v2 functions are enabled
Procedure
Step 1 Obtain the diagram of the network that is enabled with the synchronous Ethernet and IEEE
1588v2 functions.
The following figure shows an example of the network diagram for the synchronous Ethernet
and IEEE 1588v2 functions.
If an NE needs to be upgraded, delete the tracing relationship between the NE and

downstream NEs first. Then, the clock and time sources traced by the downstream NEs are
switched.
Step 2 For example, if the working link NE7->NE6->NE5 needs to be upgraded, switch synchronous
Ethernet and IEEE 1588v2 clock sources traced by NE4 to the protection link NE1->NE2>NE3 first. Perform the following operations to switch the synchronous Ethernet clock
source:
1.
In the NE Explorer, choose Clock > Physical Clock > Clock Source Priority from the
navigation tree.
2.
On the System Clock Source Priority List tab, select the desired clock source and click
Delete.
3.
Click Apply.
Step 3 Switch the IEEE 1588v2 clock source.

If the clock source traced by the NE to be upgraded is sent from a line board or ST2 board,
disable the slave port on the NE directly to switch the clock source. If the clock source traced
by the NE to be upgraded is sent from a tributary board, disable the upstream port
interconnected with the slave port on the NE first and then disable the slave port to switch the
clock source.
Perform the following operations to disable a port:
1.
In the NE Explorer, choose Clock > PTP Clock > Clock Synchronization Attribute
from the navigation tree.
2.
On the Port Status tab, select the desired port and click Delete.
3.
In the dialog box that is displayed, click OK.
Step 4 Upgrade the NE7->NE6->NE5 link in package loading mode.

Step 5 After the NE7->NE6->NE5 link is upgraded, switch synchronous Ethernet and IEEE 1588v2
clock sources from the NE1->NE2->NE3 link to the NE7->NE6->NE5 link and then upgrade
the NE1->NE2->NE3 link.
Step 6 Add the synchronous Ethernet clock source to NE7.
1.
In the NE Explorer, choose Clock > Physical Clock > Clock Source Priority from the
navigation tree.
2.
On the System Clock Source Priority List tab, click Create.
3.
In the Add Clock Source dialog box, select the desired port and click OK.
A clock source is added.
Step 7 Add the IEEE 1588v2 clock source to NE7.

If the clock source originally traced by the NE that has been upgraded is sent from a line
board or ST2 board, enable the slave port on the NE to add the clock source. If the clock
source originally traced by this NE is sent from a tributary board, enable the slave port on the
NE first and then enable the upstream port interconnected with the slave port to add the clock
source.
Perform the following operations to add the IEEE 1588v2 clock source:
1.
In the NE Explorer, choose Clock > PTP Clock > Clock Synchronization Attribute
from the navigation tree.
2.
On the Port Status tab, click New.
3.
In the Create PTP Clock Port dialog box, add the desired port to the Selected Port area
and click OK.
Step 8 After clock tracing becomes stable, upgrade the NE1->NE2->NE3 link.
----End
6.6 Board Isolation

For information about Board Isolation, see Attachment 7 Board Isolation Guide.
6.7 Checking Whether Package Loading Needs

to Be Performed for a Second Time
Task Description
A 1 GB CF card is insufficient to store the full software package for OptiX OSN
8800/6800/3800 V100R007C00SPC100/SPC200/SPC300. Therefore, you must use the
customized package instead to ensure that there is sufficient space for storing database and log
files.
Package loading committing may fail or database and log files may fail to be backed up to the
CF card due to the following causes:
OptiX OSN 8800 V100R002C02SPC800 and OptiX OSN 6800/3800

V100R004C04SPC800 do not support loading of customized software packages.
During an upgrade from OptiX OSN 8800/6800/3800 V100R005C00SPC800 or later to

OptiX OSN 8800/6800/3800 V100R007C00SPC100/SPC200/SPC300, customized
package loading is not selected and full package loading is performed. If the failure is
caused by insufficient space of the CF card, perform the package loading for a second
time.
This section describes how to check whether the CF card has sufficient remaining space and
the handling procedure when the CF card remaining space is insufficient.
Precautions
None
Procedure
Step 1 See section 3.6"Checking NE Versions" to check whether the current version of the NE is
OptiX OSN 8800/6800/3800 V100R007C00SPC100/SPC200/SPC300.
Step 2 Check whether the CFCARD_FAILED alarm is reported. If the CFCARD_FAILED alarm is
reported and there is no free space of the CF card, proceed to step 4.
Step 3 Query the type of the software package.
If PKG CUSTOMIZE Type is whole, the entire package is loaded and proceed to step 4.
Step 4 Perform package loading for a second time. During the second package loading, only the
software package on the SCC board is updated. Services are not affected.
----End
Result Verification
The loaded package is a customized package and no CFCARD_FAILED alarm is reported.
OptiX OSN 8800_6800_3800

Upgrade Guide
D Abbreviations and Acronyms
Upgrade Record Table
Site Name
Upgrade Date
Version Number Before

the Upgrade
Version Number After

the Upgrade
Operator
Customer Personnel:
Huawei Personnel:
Upgrade Successful?
Check Items for the Upgrade
Check Before the Upgrade
Check During the Upgrade
Check After the Upgrade
Conclusion
Troubleshooting
B
Item
Pre-upgrade Checklist
Impact on the
Upgrade
(If the
Preparations Are
Not Performed)
Impact on Services
Expected Result
(If the Preparations

Are Not Performed)
3.3 Obtaining Target

Upgrade Software
The upgrade cannot

proceed.
Services on the NEs that

need to be upgraded are
affected.
Completed [ ]
3.6 Checking NE
Versions
None.
None.
Completed [ ]
3.7 Checking Status of

the NE Database
Affected stage:
activation
No error occurs and no

extra action is required.
[]
[]
Details: The SCC board

on the NE fails to be
activated and a rollback
occurs on the NE.
3.8 Checking the Status
of the ODUk SPRing
Protection Group
None.
3.8 Checking System

Settings
The upgrade cannot

proceed.
If the database is damaged

after the upgrade, service
configuration cannot be
delivered to service boards
and as a result, services will
be interrupted.
Completed [ ]
If a cold reset must be

performed on the SCC
board during the upgrade,
services on the NE will be
interrupted.
Completed [ ]

affected.
Completed [ ]

[]

[]

[]
3.9 Pre-upgrade Check

for ASON NEs
None.

affected.
Completed [ ]
[]
Upgrade Checklist
Proced
ure
Step
Step Link
Precautions
Complete
or Not
Creating
Upgrade
Tasks
Obtain the
NE list.
4.1.1 IStep 1
None.
Yes[ ]/No[ ]
Create an
upgrade task.
4.1.1 IStep 2
Determine the upgrade mode. For example, to

use the software package loading mode,
choose New Task > Package
Upgrade/Downgrade Task from the shortcut
menu. To use the package diffusion mode,
choose New Task > Package Diffusion
Upgrade Task from the shortcut menu.
Yes[ ]/No[ ]
Define the
task name.
4.1.1 IStep 3
None.
Yes[ ]/No[ ]
Configure
the
operations.
4.1.1 IStep 4
Select the Pause Before Current Operation

check box for the Dispense and Activate
operations so that the U2000 will insert a
pause before the two operations.
Yes[ ]/No[ ]
Select the
target
version.
4.1.1 IStep 5
Ensure that the software package has been

imported to the software library during the
preparations.
Yes[ ]/No[ ]
Configure
Activation
(optional)
4.1.1 IStep 6
A gateway NE and its subtending NEs cannot

be allocated to the same activation group.
Otherwise, the subtending NEs may be
unreachable by the U2000 during the
activation.
Yes[ ]/No[ ]
Confirmatio
n the
information
of Package
Upgrade
4.1.1 IStep 7
You cannot modify the configuration once the

task is started. Therefore, before clicking OK
in the Operation Configuration [Package
Downgrade] window, ensure that parameters
have been correctly set for each item.
Yes[ ]/No[ ]
Start Task
4.2.1 IStep 1
None.
Yes[ ]/No[ ]
Starting
Proced
ure
Step
Step Link
Precautions
Complete
or Not
Upgrade
Tasks
Confirm that
the upgrade
is complete.
4.2.1 IStep 2
None.
Yes[ ]/No[ ]
Restore the
system
settings.
4.2.1 IStep 3
None.
Yes[ ]/No[ ]
Abbreviations and Acronyms
D
DC
data center
F
FPGA
field programmable gate array
ID
identification
I
IP
Internet Protocol
N
NE
network element
O
OSN
optical switch node
P
PC
personal computer
S
SCC
system control & communication

OptiX OSN 8800 6800 3800 V100R007C00 Upgrade Guide

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

OptiX OSN 8800 6800 3800 V100R007C00 Upgrade Guide

Hochgeladen von

Copyright:

Verfügbare Formate

OptiX OSN 8800_6800_3800

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base