Upgrade Guide (CLI) : Issue 15 Date 2020-11-20

MA5800
Upgrade Guide (CLI)
Issue 15
Date 2020-11-20
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. 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: https://www.huawei.com
Email: support@huawei.com
Issue 15 (2020-11-20) Copyright © Huawei Technologies i

Co., Ltd.
MA5800
Upgrade Guide (CLI) Error! The style is not specified.
About This Document
Purpose
This document describes how to upgrade the software of the MA5800 series
in terms of the following aspects: upgrade precautions, upgrade process,
preparations, pre-upgrade check, upgrade operations, rollback, upgrade
verification, and common troubleshooting.
Related Versions
The following table lists the product versions related to this document.
Product Name Version

MA5800 series The target version is V100R016C00 and
later versions
Intended Audience
This document is intended for:
 Technical support engineers
 Maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk which, if not
avoided, will result in death or serious injury.
Indicates a hazard with a medium level of risk which, if not

avoided, could result in death or serious injury.
Issue 15 (2020-11-20) Copyright © Huawei Technologies ii

Co., Ltd.
MA5800
Symbol Description
Indicates a hazard with a low level of risk which, if not
avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation which, if not

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to
personal injury.
Supplements the important information in the main text.

NOTE is used to address information not related to
personal injury, equipment damage, and environment
deterioration.
Change History
Issue Date Description
15 2020-11-2  Update the target version description.
0  Update 5.1 Verifying the Device Status, add the
Version Information Example.
 Update 6.2 Verifying the Downgrade, add the
note of check the version information.
 Updated 4.3 Example and added the description.
14 2020-07-1  Updated section 1.1.1 Source OLT Version and

0 Upgrade Method Description.
 Updated section 1.3 Upgrade in the Centralized
Management Scenario.
 Updated section1.4 Upgrade Impact, added the
impact of cable-related operations during the
upgrade to V100R020C00.
 Updated section Table 3-1, add the file name for
V100R020C00.
 Updated section Table 3-2.
 Updated section 3.3.2 Check Using Smartkit
Inspector Tool.
 Updated section 6 Downgrade to the Source
Version, add the description of downgrade from
V100R020C00.
 Updated section 8 Appendix, delete the
introduction about file tranfer tool.
13 2020-04-0  Updated section 3.3.2 "Check Using Smartkit

9 Inspector" .
Issue 15 (2020-11-20) Copyright © Huawei Technologies iii

Co., Ltd.
MA5800
Issue Date Description

 Updated section 5.2 "Using Smartkit Inspector to
Check After the Upgrade" .
12 2019-11-1 Updated the Downgrade Process in section 6.1

8 Downgrade Process and the description step of
Verifying the Downgrade in section 6.2 Verifying
the Downgrade.
11 2019-07-2 Updated the source OLT version and upgrade

0 method description and section 1.1.1.
10 2019-03-2 Updated the source OLT Version.

5
09 2018-08-2  Updated the OLT source version requirements in

0 section 1.1.1 Source OLT Version.
 Added precautions for the upgrade with service
interruption and upgrade without service
interruption (ISSU) in section 1.2 Scenarios
Introduction.
 Updated the inspection tool version and software
scope in section in section 3.3.2 Check Using
SmartKit Inspector.
 Added precautions in section 8.1 Unpacking and
Packing.
08 2017-08-1 Changed the downgrade reset system command

1 from upgrade to restart system.
07 2016-12-3 The structure of the document are optimize.

0
06 2016-08-1 Updated the source OLT Version.

1
05 2016-07-2  Updated the matched terminal version.

0  Updated the upgrade impact.
04 2016-04-2  Added the description of hitless upgrade.

3  Added the impact on the system during the
hitless upgrade for large-capacity MSO services,
and updated the requirements for upgrading
basic versions.
03 2015-08-2 The name of combined package file is updated.

7
02 2015-07-2 Modified content in 1.3 Upgrade in the Centralized

8 Management Scenario.
01 2015-04-2 This issue is the first official release.

8
Issue 15 (2020-11-20) Copyright © Huawei Technologies iv

Co., Ltd.
MA5800
Upgrade Guide (CLI) Contents
Contents
About This Document........................................................................................................................ ii

1 Before You Start...............................................................................................................................1
1.1 Upgrade Paths.........................................................................................................................................................1
1.1.1 Source OLT Version and Upgrade Method Description........................................................................ 1
1.1.2 Matched Terminal Versions.............................................................................................................................1
1.2 Scenarios Introduction......................................................................................................................................... 2
1.3 Upgrade in the Centralized Management Scenario..................................................................................3
1.4 Upgrade Impact......................................................................................................................................................3
2 Upgrade Process.............................................................................................................................. 6
3 Preparing for the Upgrade............................................................................................................. 8
3.1 Preparing Files and Materials Required for the Upgrade........................................................................ 8
3.2 Configuring the File Transfer Service........................................................................................................... 10
3.3 Pre-Upgrade Check.............................................................................................................................................11
3.3.1 Check the Device Version............................................................................................................................ 11
3.3.2 Check Using Smartkit Inspector Tool....................................................................................................... 12
4 Performing the Upgrade............................................................................................................... 19

4.1 Saving and Backing Up the System Configuration Data...................................................................... 19
4.2 Stopping the Automatic Saving Function...................................................................................................20
4.3 Loading Package Files........................................................................................................................................20
4.4 Activating Package File..................................................................................................................................... 21
4.5 Starting the Automatic Saving Function.....................................................................................................22
5 Verifying the Upgrade................................................................................................................... 23

5.1 Verifying the Device Status............................................................................................................................. 23
5.2 Using Smartkit Inspector to Check After the Upgrade.......................................................................... 25
6 Downgrade to the Source Version................................................................................................ 29

6.1 Downgrade Process............................................................................................................................................ 29
6.2 Verifying the Downgrade..................................................................................................................................30
7 Common Troubleshooting............................................................................................................ 32
8 Appendix.........................................................................................................................................34
8.1 Unpacking and Packing.....................................................................................................................................34
Issue 15 (2020-11-20) Copyright © Huawei Technologies v

Co., Ltd.
MA5800
Upgrade Guide (CLI) Contents
8.2 Upgrade Checklist...............................................................................................................................................35

8.3 Alarms and Events..............................................................................................................................................36
Issue 15 (2020-11-20) Copyright © Huawei Technologies vi

Co., Ltd.
MA5800
Upgrade Guide (CLI) 1 Before You Start
1 Before You Start
1.1 Upgrade Paths

1.1.1 Source OLT Version and Upgrade Method Description
If the target version is V100R020C00 and later versions, we need to

upgrade to an intermediate version and then to V100R020C00.
Paths of the Upgrade Method Description documents:

For Carrier:
https://support.huawei.com/carrier/docview!docview?nid=DOC110053721
6&path=PBI1-7275726/PBI1-7275738/PBI1-7275777/PBI1-19904180/PBI1-
21484577
1.1.2 Matched Terminal Versions

See “Supporting xPON Terminals” published with Release Notes of the
target version.
In the XGS-PON scenario where H901XSED or H901TWED is installed, you

must use a matched MxU. Before the upgrade, check the MxU version,
including MA5821A, MA5878, and MA5616 (CCUE). You can only use version
MxU V800R18C00 and later for an upgrade. Otherwise, the MxU cannot go
online after the upgrade.
Issue 15 (2020-11-20) Copyright © Huawei Technologies 1

Co., Ltd.
MA5800
1.2 Scenarios Introduction

This topic describes the upgrade ways and upgrade modes. You can select
an appropriate upgrade scenario and upgrade mode based on actual
network conditions.
Upgrade Way
You can upgrade the device software using the NMS or command line
interface (CLI). The following table lists the differences between the two
scenarios.
Scenario Characteristics Maximum Upgrade

Efficiency
Upgrade using the Supports remote upgrade 200 devices/day
NMS of devices in batches.
Upgrade through CLI Supports remote upgrade 40 devices/day

of a single device.
This document describes how to remotely upgrade software of devices

through CLI.
Upgrade Modes
There are two upgrade modes: the upgrade with service interruption and
upgrade without service interruption (ISSU).
 Upgrade without Service Interruption only to cross-R version or cross-C

version upgrade.
 If the Upgrade without Service Interruption is used, contact Huawei R&D
engineers for technical support to ensure a smooth upgrade.
The differences of the two upgrade modes are as follows. For the operation
differences between the two upgrade modes, see "4.4 Activating Package
File".
Item Upgrade with Service Upgrade Without Service

Interruption Interruption
Environmental Single control board or Active and standby
requirements active and standby control control boards
boards
Version All version. The source version is

requirements V100R017C00 or a later
version.

Co., Ltd.
MA5800
Item Upgrade with Service Upgrade Without Service

Interruption Interruption
Upgrade Both the active and standby The standby control
process control boards are board is upgraded, and
upgraded simultaneously. then the active/ standby
switchover is performed.
In the end, the active
control board is
upgraded.
1.3 Upgrade in the Centralized Management Scenario

In the centralized management scenario, the coaxial media converter (CMC)
functions as the OLT board software.
 The CMC software is contained in the OLT software package.
 During an upgrade, the CMC software is distributed by the OLT
automatically and it does not need to be loaded separately.
V100R020C00 and later versions do not support Cable.
1.4 Upgrade Impact

Knowing the upgrade impact helps you plan an upgrade appropriately.
V100R020C00 and later versions do not support Cable. Delete cable

configurations before the upgrade.
Impact on the System During the Common Upgrade

 Impact on Services
Services will be interrupted during the necessary system restart after an
upgrade. The service interruption lasts 35 minutes, depending on the
original system configurations.
The time required from the system restart to the recovery of control boards, service
boards, and services is related to the configured data volume.
Table 1-1 Time required for each upgrade step
Procedure Time Required (Unit: Minute)

Co., Ltd.
MA5800
Procedure Time Required (Unit: Minute)

Load the combined package The time required for loading the
file. combined package file depends on the
device environment and size of the
package file.
 Single control board: It takes about 4
minutes for loading a combined
package file of 100 MB at a rate of 25
MB/min.
 Dual control boards: It takes about 4
minutes for loading a combined
package file of 100 MB at a rate of 25
MB/min.
Restart the system and wait 13 minutes

until the control board
recovers.

until the service boards
recover.

until the services recover.
 Impact on NE management
The NE will fail to connect to the NMS during the system restart after an
upgrade from an earlier version. After the system is restarted, the NMS
needs to synchronize data with the NE.
Impact on the System During the Hitless Upgrade (ISSU)
Table 1-2 Time required for each upgrade step
Upgrade Process Consumed Time

Load the combined The time required for loading the combined package
package file. file depends on the device environment and size of
the package file.
 Dual control boards: It takes about 4 minutes to
load a combined package file of 100 MB at a rate
of 25 MB/min.
Restart the first 29 minutes

standby control
board and wait
until the second
standby control
board return to
normal.

Co., Ltd.
MA5800
Upgrade Process Consumed Time

Restart the first 50 minutes
standby control
board and wait
until the services
recover.
Service FTTx Services:

interruption Services generated during the upgrade are
duration interrupted for 10s during the upgrade and ONUs
are continuously connected.
D-CCAP Services
5-20 minutes (depending on the original system
configurations.)
NOTE
V100R020C00 do not support Cable.

Co., Ltd.
MA5800
2 Upgrade Process
Adhere to the upgrade process when performing an upgrade. If any

exceptions occur during an upgrade, stop the upgrade and contact Huawei
technical support engineers.
Activating package files may affect services. Therefore, it is advised to

perform the operation in early morning when the device carries minimum
traffic.

Co., Ltd.
MA5800
Figure 2-1 Upgrade process

Co., Ltd.
MA5800
3 Preparing for the Upgrade
3.1 Preparing Files and Materials Required for the Upgrade
 The combined package file includes the control board package file. The
combined package file obtained must match the control board type. Any
mismatch may cause faults to the control board hardware.
 Ensure that the combined package file and the patch file of the source
version are available in case of any necessary system downgrade. For a
source version that does not support a combined package file, ensure
that the control board package file of the source version are available.
 For details about an upgrade within the same R and C version, see Patch
Installation Guide.
Procedure
Step 1 Download the software packages for the source version and target version
from http://support.huawei.com.
Step 2 Authenticate the downloaded software packages by OpenPGP. These
downloaded software packages can be used only when they are
authenticated. To authenticate downloaded software packages, click
Digital Signature Authentication Mode on the upper right corner of the
Software list.
Step 3 Decompress the downloaded software package, and select the files
required for the upgrade.
Table 3-1 Files required for the upgrade
No. File File Name Function

Description

Co., Ltd.
MA5800
No. File File Name Function

Description
1 Combined  V100R020C00 and Differentiated by control
package later versions: board, the combined
file MA5800V100RxxxCxx package file includes
SPCxxx.bin software files of all boards,
internal database upgrade
 Versions earlier tool files, and hot patch
than V100R020C00 : package files. It is used for
V100RxxxCxx[SPxxxx]_w cross-R, cross-C, or
holepackage[(SPCxxx)]_z cross-baseline patch
zzz_yyyy.bin version upgrade or
NOTE downgrade.
Content in the square Cross-baseline patch
brackets [ ] is optional, version upgrade or
V100RxxxCxx[SPxxxx] is downgrade refers to the
the target version number,
scenario when the VRC
SPCxxx is the baseline
version number, and zzzz is version numbers are the
the control board type. For same but the first digits of
http://support.huawei.com, the patch versions are
yyyy is "Carrier"; and for different, for example,
http://support.huawei.com/ upgrading
enterprise, yyyy is
V100RxxxCxxSPx1xx to
"Enterprise".
V100RxxxCxxSPx2xx.
 The name of combined package file may be differences between the different
versions, please refer to the Release Notes to see the detail the Combined
package file name.
 If the current combined package version of the MA5800 is V100R18C00 or lower,
the size of the package file to be loaded needs to be less than 500MB. For
package file larger than 500MB, you need to repack the package file to make it
smaller than 500MB so that it can be loaded correctly. If the current combined
package version of the MA5800 is V100R18C10 or higher, there is no above limit
to the size of the package file to be loaded. How to repack a package file using the
unpacking&packing tool, seeing “8.1 ”.
 V100R019C10SPC200 and later versions don't need to repack the package file.
Step 4 Prepare materials for the upgrade.
Table 3-2 Materials required for the upgrade
No. Item Remarks

1 A PC running Windows XP or -
Windows 7 OS
2 Reference documents for the -

upgrade
3 Unpacking&packing Please obtain the

tool(Optional) unpacking&packing tool contained

Co., Ltd.
MA5800
No. Item Remarks

in the software of the target version.
NOTE
V100R019C10SPC200 and later
versions don't need to repack the
package file.
4 A file transfer tool installed on -

a laptop
5 IP address, user name, and -

password of the device to be
upgraded
6 Telnet tool -
7 Network cable and serial -

cable
8 Board spare parts, Phillips Ensure that, for each board used on
screwdriver (with a 2# head) the network, at least one spare
board is available, so that a board
can be replaced quickly if it fails.
----End
3.2 Configuring the File Transfer Service

This topic describes how to configure the file transfer service between the
device to be upgraded and file server, so that upgrade software package
files can be loaded to the device from the file server.
Prerequisites
Before configuring the file transfer service, ensure that network
communication between the file server and device to be upgraded is
normal.
Context
 This topic uses the SFTP mode as an example to describe how to upload
files required for the upgrade to the device from the file server.
Procedure
Step 1 Install the SFTP tool on the file server.
Step 2 Remotely log in to the device to be upgraded. (The SSH login mode is
recommended.)
Step 3 Use the ssh sftp clear command to clear the SFTP settings in the system.

Co., Ltd.
MA5800
Step 4 Use the ssh sftp set command to set the user name and password for
logging in to the SFTP server.
----End
Example
For example, set the user name and password for logging in to the SFTP
server.
huawei(config)#ssh sftp clear
huawei(config)#ssh sftp set
User Name(<=40 chars):testUser //SFTP server user name
User Password(<=40 chars): //SFTP server password
Listening Port(0--65535):22
3.3 Pre-Upgrade Check

3.3.1 Check the Device Version
Step 1 Run the display version command to query the device version. Ensure
that the device version is the source version to be upgraded.
Step 2 Run the display patch all command to query the current patches. Check
whether the current patches meet the requirements of the source version. If
not, refer to 4 Performing the Upgrade4 Performing the Upgrade.
Step 3 Run the display board command to query the status of boards on the
device to be upgraded. Ensure that the status of all the boards on the device
is normal.
Step 4 Run the display board frameid/slotid command to query the status of the
ONUs connected to the boards on the device. Ensure that the ONU status is
normal.
Step 5 Run the display cpu command to query the CPU usage of the active control
board. Ensure that the CPU usage is below 80%.
Step 6 Run the display port traffic command to query the service traffic volume
of upstream ports. The traffic volume before the upgrade will be compared
with that after the upgrade.
Step 7 Check whether the default BIOS password has been changed. If the
password has not been changed, you are advised to change the password;
otherwise, the system generates an alarm after the version is upgraded to
V100R020C00 or later.
----End
Example
For example, query information about the device to be upgraded, including
the software version, patch version, board status, ONU status, CPU usage,
and service traffic volume at upstream ports. In this example:

Co., Ltd.
MA5800
 The service board is in slot 0/3.

 The active control board is in slot 0/9.
 The upstream port on the control board is 0/9/0.
huawei(config)#display version
huawei(config)#display patch all
huawei(config)#display board 0
huawei(config)#display board 0/3
huawei(config)#display cpu 0/9
huawei(config-if-mpu-0/9)#display port traffic 0
3.3.2 Check Using Smartkit Inspector Tool

Use Smartkit Inspector to check mandatory inspection items before the
upgrade.
 Smartkit Inspector is released independently of the MA5800 series product. For

more information, contact Huawei technical support personnel.
 For detailed usage guide to the Smartkit Inspector, see the Online Help of the tool.
Press "F1" on the tool interface to obtain the Online Help.
 For areas that the Smartkit Inspector tool cannot be used, contact Huawei
technical support engineers for pre-upgrade check.
Check mandatory inspection items according to the following

Configuration Inspection Template. (The following figure uses the
Smartkit V200R012C00SPC308 as an example to illustrate the configuration
of pre-upgrade check items for an upgrade from MA5800V100R015C00 to
MA5800V100R018C10.)
Step 1 Starting the Inspector , Select Project> New Project.

Co., Ltd.
MA5800
Upgrade Guide (CLI) 2 Upgrade Process
Enter the project name and click OK.
The project file can be saved to the default path

(D:\SmartKit\app\Inspector\database\Project) or another path. The default path is
recommended
Step 2 On the Project Management page, right-click a project and choose Add
NE from the shortcut menu. In the displayed dialog box, enter NE
information and click Add.

Co., Ltd.
MA5800
Upgrade Guide (CLI) 2 Upgrade Process

Co., Ltd.
MA5800
Upgrade Guide (CLI) 3 Preparing for the Upgrade
Step 3 Choose Configure > Configure Insepction Template. The Configure

Insepction Template dialog box is displayed.
In the Configure Insepction Template dialog box, Choose Device

Release Template > OLT > Checking the Services Changes >
Insepction template before RFC V1, click Finish.

Co., Ltd.
MA5800
The template is configured for the selected NE.

Step 4 Start the collection task. Select an NE to be inspected and start the
inspection task.

Co., Ltd.
MA5800
Step 5 After the inspection is complete, choose Result > Create Report(E)... to
generate a report.

Co., Ltd.
MA5800
To view the pre-upgrade inspection data of a single NE, select Independent Report
when creating a report.
Step 6 After the report is created, click Open the Directory Holding the
Report… in the Creating report is finished. dialog box.
Step 7 Enter the path containing the report, and open Sum Preventive Maintenance
Report for Engineers to view the report.
If you want to view the pre-upgrade inspection data of a single NE and have selected
Independent Report in step 5, go to the directory containing the IP address of the
target NE and open the Independent Report.xls form to view the report.
----End

Co., Ltd.
MA5800
4 Performing the Upgrade
4.1 Saving and Backing Up the System Configuration Data

Save and back up the system configuration data before loading package
files, so that data can be restored if a software downgrade is required when
exceptions occur during the upgrade.
Procedure
Step 1 Run the save command to save the database and configuration files.
 During a new deployment, the database file must also be saved before
you load the combined package file.
 If the save operation fails, do not forcibly upgrade. Locate and
troubleshoot the fault according to actual conditions. If the save
operation failure persists, contact Huawei engineer for help.
Step 2 Run the backup data command to back up the database file to the file
server.
Step 3 Run the backup configuration command to back up the configuration file
to the file server.
----End
Example
For example, save and back up the database file and configuration file to the
file server. In this example:
 The SFTP file transfer mode is used.
 The IP address of the file transfer server is x.x.x.x.
 The backup database file is named as db_mpl_old.dat.
 The backup configuration file is named as config_old.txt.
huawei(config)#save

Co., Ltd.
MA5800
huawei(config)#backup data Sftp x.x.x.x db_mpl_old.dat

Please save database file before backup, or the database file that is backed u
p may not be the latest one. Are you sure to continue? (y/n)[n]: y
huawei(config)#backup configuration Sftp x.x.x.x config_old.txt
Please save configuration file before backup, or the configuration file that i
s backed up may not be the latest. Are you sure to continue? (y/n)[n]:y
4.2 Stopping the Automatic Saving Function

The automatic saving function needs to be stopped before the upgrade, so
that the upgrade operation will not conflict with the automatic saving
operation.
Procedure
Step 1 Run the autosave interval off command to disable periodic automatic
saving or run the autosave time off command to disable scheduled
automatic saving.
----End
4.3 Loading Package Files

Procedure
Step 1 Copy the combined package file to the SFTP directory.
Step 2 Run the load packetfile command to load the combined package file.
You can run the display progress load command to query the loading progress. In
the SFTP loading mode, the loading progress remains unchanged for a period of time
when it reaches 98%. The period ranges from 30 minutes to 120 minutes, depending
on the file size and the speed of the network.
----End
Example
For example, load the combined package file of the target version
V100RxxxCxxSPCxxx. In this example:
 The SFTP file transfer mode is used.
 The IP address of the file transfer server is x.x.x.x.
 The original combined package file is named as
V100RxxxCxxSPxxxx_wholepackage(SPCxxx)_zzzz_yyyy.bin.
 The new combined package file (generated after unpacking&packing) is
named as
V100RxxxCxxSPxxxx_wholepackage(SPCxxx)_zzzz_new.bin..

Co., Ltd.
MA5800
 V100RxxxCxxSPxxxx is the target version number, SPCxxx is the baseline version

number, and zzzz is the control board type. For http://support.huawei.com, yyyy
is "Carrier"; and for http://support.huawei.com/enterprise, yyyy is "Enterprise".
 The name of combined package file may be differences between the different
versions, please refer to the Release Notes to see the detail the Combined
package file name.
huawei(config)#load packetfile sftp x.x.x.x

V100RxxxCxxSPxxxx_wholepackage(SPCxxx)_zzzz_new.bin
The new packet file will overwrite the old one
Rollback function will be disabled
Be sure that the system needn't this function
Are you sure to load new packet file? (y/n)[n]:y
4.4 Activating Package File

The combined package files need to be activated after being loaded so that
the package files can take effect.
Activating package file may affect services, it is advised to perform the

operation in early morning when the device carries minimum traffic.
If you still fail to log in to the device after 30 minutes, the system may be
abnormal due to an upgrade failure. In this case, connect to the device
through a serial port.
The upgrade with service interruption mode is recommended.
Procedure
 Upgrade with service interruption
Run the upgrade command to reset the system and activate the
combined package file.
 Upgrade without service interruption (ISSU)
Run the upgrade issu command to upgrade the device software and
activate the combined package file.
Example
 Reset the system and activate the combined package file in an upgrade
with service interruption.
huawei(config)#upgrade
Software upgrades will lead to business interruption, continue? (y/n)[n]:y
 Activate the combined package file in an upgrade without service
interruption.
huawei(config)#upgrade issu
Software upgrades will lead to business interruption, continue? (y/n)[n]: y

Co., Ltd.
MA5800
4.5 Starting the Automatic Saving Function

After the upgrade succeeds, start the automatic saving function.
Procedure
Step 1 Run the autosave interval on command to enable periodic automatic
saving or run the autosave time on command to enable scheduled
automatic saving.
----End

Co., Ltd.
MA5800
5 Verifying the Upgrade
5.1 Verifying the Device Status

When the upgrade is complete, verify the upgrade results to ensure that the
device runs normally.
Context
If all items listed in Table 5-1 meet the criteria, the upgrade is successful.
Table 5-1 Post-upgrade verification checklist
No. Check Item Criterion Result

1 Device version and The version
main control board information after
information the upgrade is
correct.
2 IO board package The board software

file versions after the
upgrade are
correct.
3 Board status All the boards are

in normal state.
4 Service port status The

service-provisionin
g ports are
activated.
5 Service traffic The service traffic

volume of volume of
upstream ports upstream ports is
close to that before
the upgrade.

Co., Ltd.
MA5800
Procedure
Step 1 Run the display version command to query version information about the
device software and control board. Ensure that the device version and
control board version are consistent with those in the Release Notes.
The current program area stores the target version after the upgrade and the
standby program area stores the version before the upgrade. Software in the
standby program area will synchronize that in the current program area and will be
the same as the target version 48 hours later.
Step 2 Run the display io-packetfile information command to query

information about the IO board package file. Ensure that the board version
information is consistent with that in the Release Notes.
Step 3 Run the display board command to query the board status. Ensure that
the status of all boards is normal.
Step 4 Run the display board frameid/slotid command to sample-check the port
status. Ensure that the service-provisioning ports are activated.
Step 5 Run the display port traffic command to query the service traffic volume
of upstream ports. Ensure that the service traffic volume of upstream ports
is close to that before the upgrade.
----End
Example
For example, verify the upgrade results after a device is upgraded. In this
example:
 Two control boards are configured in slots 0/9 and 0/10.
 The service board is in slot 0/5.
 The upstream port on the control board is 0/9/0.
huawei(config)#display version
huawei(config)#display version 0/9
huawei(config)#display version 0/10
huawei(config)#display io-packetfile information
huawei(config)#display board 0
huawei(config)#display board 0/5
huawei(config-if-mpu-0/9)#display port traffic 0
Version Information Example

 If the software to be loaded is SPHYxx, SPHYxx_WholePatch, or
SPHYxx_WholePackage, the version is as follows:
huawei (config)#display patch all
Software Version:MA5800V100RxxCxx
SPHYxx
------------------------------------------------------------------------
Current Patch State:
------------------------------------------------------------------------
Patch Name Patch State Delivery Attribute Dependency
------------------------------------------------------------------------

Co., Ltd.
MA5800
SPHYxx running common hot patch NO

------------------------------------------------------------------------
Total:1
Patches in the system cannot be rolled back
 If the software to be loaded is SPCYxx or SPCYxx_WholePackage，the

version is as follows:
SPCYxx
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
SPCYxx running common cold patch NO
------------------------------------------------------------------------
Total:1
 If the software to be loaded is HPzzzz or HPzzzz_WholePackage，the

version is as follows:
Note: In some patch versions, the Dependency query result is different.
SPHYxx
HPzzzz
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
SPHYxx running common hot patch NO
HPzzzz running common hot patch YES
------------------------------------------------------------------------
Total:1
5.2 Using Smartkit Inspector to Check After the Upgrade

Step 1 Start the SmartKit Inspector. On the Project Management page, click a
project task. Choose Configure > Configure Insepction Template. The
Configure Insepction Template dialog box appears.

Co., Ltd.
MA5800
Upgrade Guide (CLI) 4 Performing the Upgrade
Step 2 In the Configure Insepction Template dialog box，choose Device

Release Template > OLT > Checking the Services Changes >
Insepction template after RFC V1, check Finish.

Co., Ltd.
MA5800
The template is configured for the selected NE.

Step 3 Start the collection task, select the NE to be inspected, and start the
inspection task.
Step 4 After the inspection is complete, choose Result > Create Report(E).... in
the Create Report dialog box, choose Saving Path, check OK.

Co., Ltd.
MA5800
To view the pre-upgrade inspection data of a single NE, select Independent Report
when generating a report.
Step 5 After the report is created, click Open the Directory Holding the
Report… in the Creating report is finished. dialog box.
Step 6 Enter the path containing the report, and open Sum Preventive Maintenance
Report for Engineers to view the report.
If you want to view the pre-upgrade inspection data of a single NE and have selected
Independent Report in step 4, go to the directory containing the IP address of the
target NE and open the Independent Report.xls form to view the report.
----End

Co., Ltd.
MA5800
6 Downgrade to the Source Version
6.1 Downgrade Process

After an upgrade, you can upgrade the software to the source version if the
system cannot recover from abnormalities.
Step 1 Obtain the combined package file of the source version, repack the file
using the unpacking&packing tool, and put the file to the SFTP directory.
Step 2 Obtain the database file that has been backed up before the upgrade, and
put it to the SFTP directory.
You must use the database file of the source version that is backed up
before the upgrade. Otherwise, configuration data may be lost or upgrade
fails.
Step 3 If V100R019C10 or a later version is downgraded to a version earlier than

V100R019C10, check whether the master key configuration of the current
system is the default configuration. In other cases, skip this step.
1. Run the display master-key configuration command to query the
master key of the current system.
2. If the master key is set to user-defined, run the clear master-key
command to restore the master key to the default value.
3. Run the display master-key configuration command to check
whether the current system master key is restored to default. If yes, go
to the next step.
Step 4 Load the combined package file and database of the source version.
1. Run the load packetfile command to load the combined package file
of the source version.
 You can run the display progress load command to query the loading progress.
In the SFTP loading mode, the loading progress remains unchanged for a period
of time when it reaches 98%. The period ranges from 30 minutes to 120 minutes,
depending on the file size and the speed of the network.

Co., Ltd.
MA5800
Upgrade Guide (CLI) 5 Verifying the Upgrade
 If the loading fails, refer to 7 Common Troubleshooting for handling.

huawei(config)#load packetfile ftp x.x.x.x
V100RxxxCxx[SPxxxx]_wholepackage[(SPCxxx)]_zzzz_yyyy.bin
The new packet file will overwrite the old one
Are you sure to load new packet file? (y/n)[n]:y
2. Run the load data command to load the backup database of the source
version.
huawei(config)#load data ftp x.x.x.x MA5800.dat all
The new database will overwrite the old one
It's irreversible. Are you sure to load new database? (y/n)[n]:y
3. Run the reboot system command to reset the system.
huawei(config)#reboot system
Please check whether data has saved, the unsaved data will lose if reboot
system, are you sure to reboot system? (y/n)[n]: y
----End
6.2 Verifying the Downgrade

Verify the downgrade results. Ensure that the version information after the
downgrade is consistent with that before the upgrade. Pay attention to the
patch version.
Procedure
Step 1 Run the display language command to check whether the system version
is correct.
Step 2 Run the display version frameid/slotid command to check the version of
the control board.
Step 3 Run the display patch all command to check whether the patch version is
correct.
Step 4 Run the display io-packetfile information command to query the
information about the IO board package file.
Step 5 Run the display board 0 command to check the status of the boards in the
system.
The active control board, standby control board, service boards, and other
boards must be in the normal state.
Step 6 Run the display board frameid/slotid command to check the service port
status.
The service-provisioning ports must be in the activated state.
To verify the downgrade version, see 5.1 Version Information Example.

Co., Ltd.
MA5800
----End

Co., Ltd.
MA5800
7 Common Troubleshooting
This topic provides methods for handling common exceptions that occur
during or after the upgrade.
If a problem cannot be solved using the provided handling methods, record the
operations, collect related error information, and contact Huawei technical support
engineers for help.
1. File loading fails.
No. Error Message Handling Methods

1 Failed to transfer  Check whether the network cable is
the file connected properly. If not, reconnect the
network cable and verify that the SFTP
server can be pinged from the device.
 Check whether the SFTP server directory is
correct. If not, enter a correct directory
and save the file to the directory.
 Check whether the IP address of the SFTP
server is correct. If not, enter a correct IP
address.
 Check whether the file name is correct. If
not, enter a correct file name.
2 The packet file is  If a patch needs to be loaded to the device

incorrect before the upgrade, check whether a
patch has been loaded. If not, load a patch
to the device.
 Check whether the entered file name is
correct. If not, enter a correct file name.
 If the file is correct, contact Huawei
technical support engineers to check
whether the package file is abnormal.
3 User name, The user name and password of the device

password, or are inconsistent with those of the SFTPserver.
configuration of Reconfigure the user name and password of
the file server is the SFTP/server.

Co., Ltd.
MA5800
No. Error Message Handling Methods

incorrect
2. The device fails to start up from a reset.

Obtain a backup control board, back up the software data, and go onsite
to handle the problem. Check the indicators on the board, and reload
the software through a serial port. If the loading fails, perform a version
downgrade. If the downgrade fails, replace the control board and reload
the software.
3. Loading and backup operations fail during an upgrade task.
Record the causes, and check the device version and status. After
verifying that the device version is correct and the device status is
normal, perform the loading and backup operations again.
4. The service board can start normally, but the version fails to be
upgraded.
Check whether the BIOS file of the board matches the software version.
If not, upgrade the BIOS version and then upgrade the device again. If
yes, directly upgrade the device again.
5. The service board fails to start.
Obtain a backup service board, back up the software data, and go onsite
to handle the problem.
6. All or part of service data is lost.
If all service data is lost, reload the database. If part of the service data
is lost, configure it manually to restore the services.
7. Services are unavailable after an upgrade.
Check whether service data is lost, whether the connection to the
upstream device is normal, and whether operations have been
performed on the upstream device. If no exception occurs but the
services cannot recover, perform a version downgrade.

Co., Ltd.
MA5800
8 Appendix
8.1 Unpacking and Packing

Step 1 Decompress the unpacking&packing tool file.
Step 2 Execute the file Pack.exe decompressed.
Step 3 Click the Packet & Unpacket tab.
Step 4 Click the button. In the dialog box that is displayed, select the
package file to be unpacked, and click Open.
Step 5 Deselect unnecessary boards. Reserve the board software that has been
used and will be used.
Deselect unnecessary boards. The following uses H901XGHD used in the
current environment as an example.
When the internal database is used for the upgrade, ensure that
UPDATETOOLS is selected.

Co., Ltd.
MA5800
Step 6 Click Pack. In the dialog box that is displayed, select the directory for saving
the package file to generate a new package file.
Step 7 Click Save. After the new package file is generated, the system displays
"The operation that packing the host package is successful." Click OK.
----End
8.2 Upgrade Checklist

You are advised to record the entire upgrade process using the following
table.
Office Name Upgrade Time

Source Version Target Version
Upgrade Carrier personnel:

Personnel Huawei personnel:
Is the Upgrade
Successful
Upgrade Checklist Conclusion Exception Handling
Pre-upgrade

Co., Ltd.
MA5800
Upgrade Guide (CLI) 6 Downgrade to the Source Version
Check
Upgrade
Procedure Check
Post-upgrade
Verification
8.3 Alarms and Events

During the upgrade, the system generates alarms and events. Some can be
automatically cleared but some cannot.
The following alarms and events generated are lab data and are for reference only.
Alarms
Fault Alarm Quantity Description Supports Clear Alarm
Automatic
Clearance or
Not
The 1 This fault YES The
communicat alarm is communicatio
ion between reported n of the board
the board after the with the
and the active control board
control control board recovers
board fails. starts up. NOTE
NOTE A clear alarm This alarm is
This alarm is is reported generated for
generated after the the standby
for the control board.
active/stand
standby
by bulk
control
board. backup on
the standby

Co., Ltd.
MA5800

Automatic
Clearance or
Not
control board
is complete.
The Depending This fault YES The

communicat on the actual alarm is communicatio
ion between number of reported n of the board
the board boards after the with the
and the active control board
control control board recovers
board fails. starts up. NOTE
NOTE A clear alarm This alarm is
This alarm is is reported generated for
generated after the the service
for the board.
services on
service
the service
board.
boards are
recovered
following a
successful
upgrade.

ion of the reported n of the EMU
EMU with after the with the host
the host is active recovers
abnormal. control board NOTE
NOTE starts up. This alarm is
This alarm is A clear alarm generated for
generated is reported fan monitoring.
for fan after the fans
monitoring.
function
properly
following a
successful
upgrade.

ion of the reported n of the EMU
EMU with after the with the host
the host is active recovers
abnormal. control board NOTE
NOTE starts up. This alarm is
This alarm is A clear alarm generated for
generated is reported power supply
for power monitoring.
after the
supply
power supply
monitoring.
monitoring
functions

Co., Ltd.
MA5800

Automatic
Clearance or
Not
properly
following a
successful
upgrade.
The About 5 If a port on YES -

upstream (depending the
Ethernet on the upstream
port number of board is not
connection upstream connected to
failure ports that a device, a
recovers or are not clear alarm is
the state of connected to reported
it is normal. a device) after the
active
control board
starts up and
then a fault
alarm is
reported.
The About 5 If a port on NO -

upstream (depending the
Ethernet on the upstream
port number of board is not
connection upstream connected to
fails or the ports that a device, a
state of it is are not clear alarm is
abnormal. connected to reported
a device) after the
active
control board
starts up and
then a fault
alarm is
reported.
Events
Event Quantity Description
Backing up 1 This event is generated when the backup
files starts operation starts.
from the
host to the
maintenanc
e terminal

Co., Ltd.
MA5800
Upgrade Guide (CLI) 7 Common Troubleshooting

Backing up 1 This event is generated when the backup
files is operation ends.
successful
from the
host to the
maintenanc
e terminal
The loading 2 This event is generated when the loading

starts operation starts.
The loading 2 This event is generated when the loading

is operation ends.
successful
Auto-load About 10 This event is generated when an

start (depending on automatic upgrade of a board or EMU
the actual starts after the device is successfully
number of upgraded.
boards and
EMUs)
Auto-load About 10 This event is generated when an

Complete (depending on automatic upgrade of a board or EMU ends
the actual after the device is successfully upgraded.
number of
boards and
EMUs)
The Uncertain This event is generated when multiple

managing users log in to or log out of a device
user of the concurrently by using the serial port or
equipment telnet.
logout or
logon
The system 1 This event is generated when the batch

batch hot hot backup between active and standby
backup control boards starts following the
starts standby control board recovery.
The system 1 This event is generated when the batch
batch hot hot backup between active and standby
backup is control boards ends following the standby
complete control board recovery.
Normal 1 This event is generated two minutes after

system the upgraded device starts up.
startup
The Layer 3 About 2 This event is generated when a Layer 3

interface (depending on interface is initialized and its link recovers
link is in the the actual after the device is upgraded.
up state number of
connected

Co., Ltd.
MA5800
Upgrade Guide (CLI) 7 Common Troubleshooting

Layer 3
interfaces)

Co., Ltd.

Upgrade Guide (CLI) : Issue 15 Date 2020-11-20

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Upgrade Guide (CLI) : Issue 15 Date 2020-11-20

Uploaded by

Copyright:

Available Formats

MA5800

Upgrade Guide (CLI)

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 15 (2020-11-20) Copyright © Huawei Technologies i

About This Document

Product Name Version

Indicates a hazard with a medium level of risk which, if not

Issue 15 (2020-11-20) Copyright © Huawei Technologies ii

Indicates a potentially hazardous situation which, if not

Supplements the important information in the main text.

14 2020-07-1  Updated section 1.1.1 Source OLT Version and

13 2020-04-0  Updated section 3.3.2 "Check Using Smartkit

Issue 15 (2020-11-20) Copyright © Huawei Technologies iii

Issue Date Description

12 2019-11-1 Updated the Downgrade Process in section 6.1

11 2019-07-2 Updated the source OLT version and upgrade

10 2019-03-2 Updated the source OLT Version.

09 2018-08-2  Updated the OLT source version requirements in

08 2017-08-1 Changed the downgrade reset system command

07 2016-12-3 The structure of the document are optimize.

06 2016-08-1 Updated the source OLT Version.

05 2016-07-2  Updated the matched terminal version.

04 2016-04-2  Added the description of hitless upgrade.

03 2015-08-2 The name of combined package file is updated.

02 2015-07-2 Modified content in 1.3 Upgrade in the Centralized

01 2015-04-2 This issue is the first official release.

Issue 15 (2020-11-20) Copyright © Huawei Technologies iv

About This Document........................................................................................................................ ii

4 Performing the Upgrade............................................................................................................... 19

5 Verifying the Upgrade................................................................................................................... 23

6 Downgrade to the Source Version................................................................................................ 29

Issue 15 (2020-11-20) Copyright © Huawei Technologies v

8.2 Upgrade Checklist...............................................................................................................................................35

Issue 15 (2020-11-20) Copyright © Huawei Technologies vi

1 Before You Start

1.1 Upgrade Paths

If the target version is V100R020C00 and later versions, we need to

Paths of the Upgrade Method Description documents:

1.1.2 Matched Terminal Versions

In the XGS-PON scenario where H901XSED or H901TWED is installed, you

Issue 15 (2020-11-20) Copyright © Huawei Technologies 1

1.2 Scenarios Introduction

Scenario Characteristics Maximum Upgrade

Upgrade through CLI Supports remote upgrade 40 devices/day

This document describes how to remotely upgrade software of devices

 Upgrade without Service Interruption only to cross-R version or cross-C

Item Upgrade with Service Upgrade Without Service

Version All version. The source version is

Issue 15 (2020-11-20) Copyright © Huawei Technologies 2

Item Upgrade with Service Upgrade Without Service

1.3 Upgrade in the Centralized Management Scenario

V100R020C00 and later versions do not support Cable.

1.4 Upgrade Impact

V100R020C00 and later versions do not support Cable. Delete cable

Impact on the System During the Common Upgrade

Table 1-1 Time required for each upgrade step

Procedure Time Required (Unit: Minute)

Issue 15 (2020-11-20) Copyright © Huawei Technologies 3

Procedure Time Required (Unit: Minute)

Restart the system and wait 13 minutes

Restart the system and wait 20 minutes