Professional Documents
Culture Documents
V100R007C00
Upgrade Guide
Issue
05
Date
2013-08-20
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.
Website:
http://www.huawei.com
Email:
support@huawei.com
Date
Author
Details
01
2012-07-30
First release
02
2012-09-20
Ran Yu
03
2012-12-15
Ran Yu
04
2013-3-29
Ran Yu
05
2013-8-20
Liu Haihan,
Cai Shanbao,
Li Qin
GUI Conventions
This document uses the following conventions listed in Table 2:
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
>
Courier New
Contents
Contents
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
Contents
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
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.
Concept
Comparison
Applicable
Scope
Software
Package
Loading
Mode
Upgra
de
Mode
Concept
Comparison
Applicable
Scope
Software
Package
Diffusion
Mode
Upgrade Mode
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.
Upgrade Mode
Source Version
Upgrade Mode
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.
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
Optical-Layer ASON
Separated
Optical and
Electrical NEs
OpticalElectrical
Integrated NEs
Electrical-Layer
ASON
There is no restriction
on the NE upgrade
sequence.
OptiX OSN
8800/6800
V100R005C00
There is no restriction
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.
There is no restriction
on the NE upgrade
sequence.
OptiX OSN
8800/6800
V100R006C00
There is no restriction
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.
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
There is no restriction
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.
There is no restriction
on the NE upgrade
sequence.
OptiX OSN
8800/6800
V100R006C03
There is no restriction on
the NE upgrade
sequence.
There is no restriction
on the NE upgrade
sequence.
There is no restriction
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.
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.
System boards
Optical-layer boards
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:
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:
Group 5 to Group N: created based on board protection configurations to ensure that the
working and protection boards are in different groups.
Target Version
Impact
Cause
OptiX OSN
6800_3800
V100R004C04SPC80
0
OptiX OSN
8800/6800/3800
V100R007C00SPC100/
SPC200/SPC300
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
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
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
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
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
Source Version
Target Version
Impact
Cause
OptiX OSN
8800/6800/3800
V100R006C00SPC20
0
OptiX OSN
8800/6800/3800
V100R007C00SPC100/
SPC200
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
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
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
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
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
Source Version
Target Version
Impact
Cause
OptiX OSN
8800/6800/3800
V100R006C00SPC50
0
OptiX OSN
8800/6800/3800
V100R007C00SPC300
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
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
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
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
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
Source Version
Target Version
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,
SSN1SF64A, SSN4SLO16,
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,
SSN1SF64, SSN1SF64A,
SSN4SLO16, SSN4SLQ16
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
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
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
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
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
Source Version
Target Version
Impact
Cause
OptiX OSN
8800/6800/3800
V100R006C03SPC30
0
OptiX OSN
8800/6800/3800
V100R007C00SPC300
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
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
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
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
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
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
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
Services
on the
boards are
interrupted
.
The logic
of the
boards is
upgraded
.
Source Version
Target Version
Impact
Cause
OptiX OSN
8800/6800/3800
V100R007C00SPC10
0
OptiX OSN
8800/6800/3800
V100R007C00SPC300
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.
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.
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.
----End
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
CPW_ODUk_TEL_DOWN
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
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.
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.
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."
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.
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
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 upgrade
environment
Impact
Level
Time
Required
(approximate)
Mandatory
or
Optional
High
23 days
Mandatory
High
Pre-upgrade check
2
Copying files:
70 minutes
Mandatory
Dispensing:
15 minutes
Activation:
60 minutes
Committing:
15 minutes
Medium
30 minutes
Mandatory
Perform version
rollback
Rollback before
activation
Low
40 minutes
Optional
Rollback after
activation
High
60 minutes
Task Description
1.
If the upgrade tool DC is integrated in the U2000, ensure that the U2000 version is
iManager U2000 V100R006C02.
2.
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
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 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.
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.
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
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.
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.
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.
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.
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
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.
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
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
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
Precautions
None
Procedure
Step 1 Choose Configuration > WDM/OTN ASON > TE Link Management from the main menu.
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
Precautions
None
Procedure
Step 1 Choose Configuration > WDM/OTN ASON > ASON Trail Management from the main
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
Precautions
None.
Procedure
Step 1 Choose Configuration > WDM/OTN ASON > ASON Trail Management from the main
menu.
Step 3 In the Set Routing Attributes dialog box, select Locked for the Reroute Lockout text box.
Then click OK.
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
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 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 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
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
Step 1 From the main menu of the U2000, choose Configuration > WDM/OTN ASON > ASON
Trail Management.
Step 2 Right-click an ASON trail and choose Disable Optical Parameter Constraints.
----End
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 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 7 Click Query to verify that the setting has been successfully applied.
----End
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.
2.
group.
3.
. 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
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.
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
This chapter describes how to verify the Current Software Version and Equipment Operating
Status after the upgrade.
Item
Expected Result
Software version
Equipment operating
status
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.
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.
Unlock the rerouting function of NEs every time the NEs are upgraded, and lock the function
again before upgrading them the next time.
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.
Step 3 If alarms have occurred in the ongoing services, handle the alarms first.
----End
Precautions
None.
Procedure
Step 1 Choose Configuration > WDM/OTN ASON > ASON Trail Management from the main
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.
----End
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.
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
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.
Step 4 From the main menu of the U2000, choose Configuration > WDM/OTN ASON > ASON
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
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
Step 1 From the main menu of the U2000, choose Configuration > WDM/OTN ASON > ASON
Trail Management.
Right-click an ASON trail and choose Enable Optical Parameter Constraints from the
shortcut menu.
----End
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,
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.
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 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.
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.
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.
In any of these cases, resolve the problem before resuming the upgrade.
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.
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.
State
After
Rollback
Corrective Measures
Manual
Normal
Auto
CPY_FILE
_END
----End
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.
If the retry operation is successful, ignore the subsequent contents of this chapter. Wait until the upgrade
is complete.
----End
Item
Expected Result
Software
version
Actual
Result
Equipment
operating status
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
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 > 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
Precautions
None
Applicable Versions
The source version is OptiX OSN 8800/6800 V100R005C00SPC800.
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 > Clock > PTP Clock > Clock
Synchronization Attribute. Then in the right side of the window, click Port Status.
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
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.
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.
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 NE Explorer, choose Clock > Physical Clock > Clock Source Priority from the
navigation tree.
2.
3.
In the Add Clock Source dialog box, select the desired port and click OK.
A clock source is added.
In the NE Explorer, choose Clock > PTP Clock > Clock Synchronization Attribute
from the navigation tree.
2.
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
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.
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.
Site Name
Upgrade Date
Operator
Customer Personnel:
Huawei Personnel:
Upgrade Successful?
Check Items for the Upgrade
Check Before the Upgrade
Conclusion
Troubleshooting
B
Item
Pre-upgrade Checklist
Impact on the
Upgrade
(If the
Preparations Are
Not Performed)
Impact on Services
Expected Result
Completed [ ]
3.6 Checking NE
Versions
None.
None.
Completed [ ]
Affected stage:
activation
None.
Completed [ ]
Completed [ ]
Completed [ ]
None.
Completed [ ]
No error occurs and no
extra action is required.
[]
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
Yes[ ]/No[ ]
Define the
task name.
4.1.1 IStep 3
None.
Yes[ ]/No[ ]
Configure
the
operations.
4.1.1 IStep 4
Yes[ ]/No[ ]
Select the
target
version.
4.1.1 IStep 5
Yes[ ]/No[ ]
Configure
Activation
(optional)
4.1.1 IStep 6
Yes[ ]/No[ ]
Confirmatio
n the
information
of Package
Upgrade
4.1.1 IStep 7
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[ ]
D
DC
data center
F
FPGA
ID
identification
I
IP
Internet Protocol
N
NE
network element
O
OSN
P
PC
personal computer
S
SCC