NE8000 M V800R022SPH180 Patch Release Notes

NetEngine 8000 M
V800R022SPH180
Patch Release Notes
Issue 01
Date 2023-08-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2023. 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 01 (2023-08-3030) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd..
NetEngine 8000 M
Patch Release Notes Contents
Contents
1 Patch Package Information ..................................................................................................... 1

1.1 Product Name ............................................................................................................................................ 1
1.2 Product Model ........................................................................................................................................... 1
1.3 Patch Number ............................................................................................................................................ 1
1.4 Release Date.............................................................................................................................................. 1
1.5 Patch File Description................................................................................................................................ 2
1.6 Product Version and Required Patches........................................................................................................ 2
1.7 Relationship Between Patches.................................................................................................................... 3
1.7.1 NetEngine8000 M4&M8&M8K&M14&M14K V800R022C00SPC600 ............................................ 4
1.7.2 NetEngine8000 M4&M8&M8K&M14&M14K V800R022C10SPC500 ............................................ 4
1.8 Impact of Patch Installation........................................................................................................................ 5
1.9 Precautions ................................................................................................................................................ 5
1.10 Naming Rules for Patches ........................................................................................................................ 6
2 Resolved Issues ........................................................................................................................ 7

2.1 How to Obtain Issues Resolved .................................................................................................................. 7
3 Installing the Patch .................................................................................................................... 9

3.1 Tool-based Patch Upgrade (Recommended) ............................................................................................... 9
3.2 iMaster NCE-IP Patch Upgrade.................................................................................................................. 9
3.3 Installing the Patch ...................................................................................................................................10
3.3.1 Preparing to Install...........................................................................................................................10
3.3.2 Installing the Patch .......................................................................................................................... 11
3.4 Verifying Patch Installation ....................................................................................................................... 11
3.4.1 NetEngine8000 M4&M8&M8K&M14&M14K V800R022C00SPC600 ...........................................12
3.4.2 NetEngine8000 M4&M8&M8K&M14&M14K V800R022C10SPC500 ...........................................12
3.5 Follow-up Procedures After Patch Installation ...........................................................................................12
4 Rollback Procedure .................................................................................................................. 13

4.1 How to Roll Back to the Previous State .....................................................................................................13
5 Solutions to Common Problems During Patch Installation .................................................... 14

5.1 A Message "Error: The system file should be in root directory." Is Displayed After the patch load all run
Command Is Run to Load a Patch File. ...........................................................................................................14
5.2 A Message "Error: The command is invalid in the current patch status." Is Displayed After the patch load all
run Command Is Run to Load a Patch File. .....................................................................................................14
Issue 01 (2023-08-3030) Huawei Proprietary and Confidential ii

NetEngine 8000 M
Patch Release Notes Contents
5.3 A Message "Error: The patch is incompatible with the existing patch." Is Displayed After the patch load all
run Command Is Run to Load a Patch File. .....................................................................................................15
5.4 The Message "Error: The target patch does not support the hardware." Is Displayed After the patch load all
Command Is Run to Load a Patch ...................................................................................................................15
5.5 The Message "Error: The target patch does not support the current main control board." Is Displayed After
the patch load all Command Is Run to Load a Patch ........................................................................................16
5.6 The Message "Error: slot X is not ready, please try later when the system is stable." Is Displayed After the
patch load all Command Is Run to Load a Patch..............................................................................................16
5.7 The Message "Error: The next startup patch is required for the next startup of the system software." Is
Displayed After the reset patch-configure next-startup Command Is Run to Delete the Next-Startup Patch.......16
5.8 The Message "Error: Failed to clear the board configuration." Is Displayed After the patch delete all
Command Is Run to Uninstall a Patch .............................................................................................................17
5.9 How Can I Set a Patch as That to Be Loaded at the Next Startup? ..............................................................17
A Third-Party Software Vulnerabilities Fixed ...................................................................... 19
Issue 01 (2023-08-3030) Huawei Proprietary and Confidential iii

NetEngine 8000 M
Patch Release Notes 1 Patch Package Information
1 Patch Package Information
1.1 Product Name

HUAWEI NetEngine 8000 M8&M14 series routers
HUAWEI NetEngine 8000 M1A&M1C&M1D&M6 Multi-service Access Device
1.2 Product Model

NetEngine 8000 M4,NetEngine 8000 M8,NetEngine 8000 M8K, NetEngine 8000
M14,NetEngine 8000 M14K,
NetEngine 8000 M1A,NetEngine 8000 M1C,NetEngine 8000 M1D,NetEngine 8000 M1D-B
NetEngine 8000 M6, NetEngine 8000 M6K
1.3 Patch Number

NetEngine 8000 M V800R022SPH180
1.4 Release Date

Released Patch Version Patch Release Date
V800R022SPH180 2023-08-30
V800R022HP1521 2023-07-31
V800R022SPH152 2023-07-04
V800R022SPH150 2023-05-30
V800R022SPH122 2023-05-05
V800R022SPH120 2023-02-28
Issue 01 (2023-08-3030) Huawei Proprietary and Confidential 1

NetEngine 8000 M
Released Patch Version Patch Release Date

V800R022SPH006 2023-01-09
V800R022SPH003 2022-12-20
1.5 Patch File Description

Table 1-1 Patch file description
File Name File Description File Size

NE8000-M4M8M14V800R022SPH180-C00SPC600.P V800R022SPH180 289,034,836 bytes
AT patch file
NE8000-M1A-V800R022SPH180-C00SPC600.PAT V800R022SPH180 17,702,377 bytes
patch file
NE8000-M1CD-V800R022SPH180-C00SPC600.PAT V800R022SPH180 121,204,201 bytes
patch file
NE8000-M6-V800R022SPH180-C00SPC600.PAT V800R022SPH180 121,204,201 bytes
patch file
NE8000-M4M8M14V800R022SPH180-C10SPC500.P V800R022SPH180 166,880,371 bytes
AT patch file
NE8000-M1A-V800R022SPH180-C10SPC500.PAT V800R022SPH180 257,557 bytes
patch file
NE8000-M1CD-V800R022SPH180-C10SPC500.PAT V800R022SPH180 11,812,373 bytes
patch file
NE8000-M6-V800R022SPH180-C10SPC500.PAT V800R022SPH180 11,812,373 bytes
patch file
NE8000-M8M14V800R022SPH180-C00SPC200.PAT V800R022SPH180 97,266,049 bytes

patch file
1.6 Product Version and Required Patches

Product Version Latest Patch Version
NetEngine 8000 NE8000-M4M8M14V800R022SPH180-C10SPC500.PAT

M4/M8/M8K/M14/M14K
V800R022C10SPC500

NetEngine 8000 M
Product Version Latest Patch Version

NetEngine 8000 NE8000-M4M8M14V800R022SPH180-C00SPC600.PAT
M4/M8/M8K/M14/M14K
V800R022C00SPC600
NetEngine 8000 M1A NE8000-M1A-V800R022SPH180-C00SPC600.PAT
V800R022C00SPC600
NetEngine 8000 M1C/M1D NE8000-M1CD-V800R022SPH180-C00SPC600.PAT
V800R022C00SPC600
NetEngine 8000 M6 NE8000-M6-V800R022SPH180-C00SPC600.PAT
V800R022C00SPC600
NetEngine 8000 M8/M14 NE8000-M8M14V800R022SPH180-C00SPC200.PAT
V800R022C00SPC200
NetEngine 8000 M1A NE8000-M1A-V800R022SPH180-C10SPC500.PAT
V800R022C10SPC500
NetEngine 8000 M1C/M1D NE8000-M1CD-V800R022SPH180- C10SPC500.PAT
V800R022C10SPC500
NetEngine 8000 M6 NE8000-M6-V800R022SPH180- C10SPC500.PAT

V800R022C10SPC500
1.7 Relationship Between Patches

Relationships between patches are classified as function inheritance or incremental
relationships.
 Function inheritance relationship: If the latest patch resolves all issues that have been
resolved in earlier patches, functions are inherited. Otherwise, functions are not
inherited.
 Incremental relationship: If the latest patch can be directly installed on a device with
earlier patches installed, the relationship between patches is considered an incremental
relationship. Otherwise, the relationship between patches is considered a
non-incremental relationship.
Before installing an incremental patch, doe not remove the existing historical patch on a
device, which prevents triggering problems that have been resolved using the historical patch.
Before installation a non-incremental patch, note the following issues:
 If a device needs to be restarted or a software package needs to be upgraded, do not
remove an existing historical patch from a device. Set the latest patch as the patch to be
loaded at the next startup. After the device is restarted, the patch can take effect.
 If services keep running on a device, remove an existing historical patch from a device and

NetEngine 8000 M
then install the latest patch. During the historical patch removal and latest patch
installation, problems that have been resolved using the historical patch may be triggered.
Evaluate such risk before you operate the patches. Do not perform any operations on the
device between uninstalling the earlier patches and installing the latest patch. Otherwise,
services may be interrupted. For example, saving configurations causes the commands
added in the patches to be lost.
1.7.1 NetEngine8000 M4&M8&M8K&M14&M14K

V800R022C00SPC600
Table 1-2 Relationships between patches
Latest Patch Earlier Patch Function Incremental

Inheritance Relationship
Relationship
V800R022SPH180 V800R022HP1521 Inheritance Incremental

V800R022SPH152 Inheritance Incremental

V800R022C10SPC500
Table 1-3 Relationships between patches
Latest Patch Earlier Patch Function Incremental

Inheritance Relationship
Relationship
V800R022SPH180 V800R022HP1521 Inheritance Incremental

V800R022SPH120 NA NA

NetEngine 8000 M
1.8 Impact of Patch Installation

See the Solution Impact and Precautions for Installing the Patch columns in the NetEngine
8000 M V800R022SPH180 Issues Resolved.
1.9 Precautions
1. It is acceptable if the patch file is loaded to boards asynchronously.
2. During patch installation or uninstallation, ensure that all boards in use have been
registered. If any interface board is starting during patch installation or uninstallation, the
patch installation or uninstallation will probably fail on this interface board.
3. Do not install the patch if the board CPU usage exceeds 70%. Otherwise, patch
installation may fail.
4. Do not install the patch if the board memory usage exceeds 80%. Otherwise, the board
may reset due to a failure to apply for memory. To check the memory and CPU usage,
run the display health command in the system view.
[HUAWEI]display health
-------------------------------------------------------------------------------
Slot CPU Usage Memory Usage(Used/Total)
17 MPU(Master) 5% 20% 1646MB/7929MB
2 LPU 7% 60% 1017MB/16845MB
19 SFU 3% 8% 80MB/980MB
-------------------------------------------------------------------------------
5. It is normal that the board CPU usage temporarily rises during patch installation or
uninstallation. If the device has a large number of configurations, the board CPU usage
may increase to 90% or higher in a short time.
6. The new function provided by the patch cannot be used if the patch is uninstalled.
Therefore, to use the new function, do not uninstall the patch. If the patch needs to be
upgraded, use the incremental patch loading mode.
7. When loading a patch that contains a YANG model change, ensure that no NETCONF
session is in the configuration editing state. Otherwise, an unknown error may occur.
In a scenario in which a user uses Telnet to access a NE8000-M through an interface on an

interface board, if you want to restart the interface or power off and then power on the
interface board or subcard where the interface resides for the installed patch to take effect,
ensure that there is a backup Telnet connection to another interface board. If there is no
backup Telnet connection, do not restart the interface or power off and then power on the
interface board or subcard where the interface resides. Otherwise, the user will fail to access
the NE8000-M.
Some problems covered in this patch can be resolved only by performing the operations
described in Precautions for Installing the Patch after the patch is installed and activated. For
details about operation procedures, see section 3.4.1 .

NetEngine 8000 M
1.10 Naming Rules for Patches

Patches are classified as hot patches and cold patches based on the impacts that patches have
on user experience when they are activated and validated.
A hot patch (HP) does not affect user experience because it does not cause service
interruptions when it is activated and validated.
A cold patch (CP) affects user experience because it causes service interruptions when it is
activated and validated.
Naming rules for Accumulated Correction Updates (ACUs) are as follows:
1. For an ACU that is released based on the previous cold ACU, if the current ACU
contains patches that would affect user experience when being activated and validated,
the current ACU is a cold ACU and named SPCyyy.
2. For an ACU that is released based on the previous cold ACU, if the current ACU does
not contain any patches that would affect user experience when being activated and
validated, the current ACU is a hot ACU and named SPHyyy.
Naming rules for Emergency Correction Patches (ECPs) are as follows:
1. For an ECP that is released based on the previous ACU, if activating and validating the
ECP would not affect user experience, the ECP is named as a hot ECP in the format of
HPyyyy; if activating and validating the ECP would affect user experience, the ECP is
named as a cold ECP in the format of CPyyyy.
2. The first y in HPyyyy or CPyyyy is fixed at 0, and the subsequent yyy is the same as yyy
in SPCyyy or SPHyyy of the previous ACU. Therefore, an ECP is named in the format
of HP0yyy or CP0yyy. If a calculated ECP name is the same as that of the previously
released ECP, "yyy" in the newly calculated one increases by 1.
For example, after a cold ACU named SPC011 is released, the first hot ECP is named HP0011,
and the next hot ECP is named HP0012. After a hot ACU named SPH012 is released, the first
cold ECP is named CP0013 because the number 0012 has already been used by HP0012 for
the same ACU.
Activating and validating a hot ACU or an ECP released based on the previous cold ACU and
a later released hot ACU would not affect user experience. However, activating and validating
a hot ACU or an ECP released based on an ACU earlier than the previous cold ACU or on a
device that is not equipped with any patches would affect user experience. Therefore, comply
with the precautions for activating and validating cold ACUs when performing these
operations.

NetEngine 8000 M
Patch Release Notes 2 Resolved Issues
2 Resolved Issues
This section describes the issues that are resolved in V800R022 and precautions for installing
the patch. For detailed information, see the NetEngine 8000 M V800R022SPH180 Issues
Resolved.
Pay attention to the precautions for installing the patch. The possible causes are as follows:
Restart the device, perform an master/slave switchover, power off and then power on the
board or subcard, reset the board or subcard, reconfigure the device, or add
configurations. Exercise caution when performing this operation.
2.1 How to Obtain Issues Resolved

The website does not support online browsing of Excel files. Therefore, you cannot view the Issues
Resolved online. Download and view the list.
Step1 Download the Patch Release Notes Zip package to the local host.
Step2 Decompress the Patch Release Notes and view the Issues Resolved.

NetEngine 8000 M
Patch Release Notes 2 Resolved Issues

NetEngine 8000 M
Patch Release Notes 3 Installing the Patch
3 Installing the Patch
3.1 Tool-based Patch Upgrade (Recommended)

Carriers are advised to use uUpgrade in IP Toolkit for patch installation and upgrade. The
download paths of IP Toolkit and the tool patch are as follows:
https://support.huawei.com/carrier/navi?coltype=software#col=software&path=PBI1-727572
6/PBI1-7275757/PBI1-21039046/PBI1-21621186
Enterprise customers are advised to use uUpgrade in eDesk Pro for patch installation and
upgrade. Download eDesk Pro at:
https://support.huawei.com/enterprise/zh/enterprises-common/edesk-pro-pid-23037235/softw
are
1. Download the latest version and patch of the tool on the linked page.
For details about how to use the tool, see the NE upgrade user guide on the tool download
page.
3.2 iMaster NCE-IP Patch Upgrade

You can also use iMaster NCE-IP to upgrade the patch. For details, see the iMaster NCE
product documentation.
The latest iMaster NCE-IP tool version and patch can be obtained from the following path：
Download Path for Carriers：

https://support.huawei.com/carrier/productNewOffering?col=product&path=PBI1-252291763
/PBI1-252291797/PBI1-252291931/PBI1-250987508/PBI1-250940033&resTab=SW
Download Path for Enterprise Customers：
https://support.huawei.com/enterprise/en/network-management-control-analysis/imaster-nce-i
p-pid-250940033/software

NetEngine 8000 M
3.3 Installing the Patch

3.3.1 Preparing to Install
Perform the following steps to prepare for installation. The patch file patch.PAT is used as an
example.
Step 1 Obtain the NE8000-M patch from https://support.huawei.com.
Step 2 Verify the digital signature of the patch package.
To prevent the software package from being maliciously tampered with during transmission
or storage, download the related digital signature file for integrity verification when
downloading the software package.
After the software package is downloaded, verify the PGP digital signature of the software
package by following the procedure in OpenPGP Signature Verification Guide. If the
verification fails, do not use the software package. Contact Huawei technical support.
Before using the software package for installation or upgrade, verify the digital signature of
the software package to ensure that the software package is not tampered with.
For carrier customers, visit https://support.huawei.com/carrier/digitalSignatureAction.
For enterprise customers, visit
https://support.huawei.com/enterprise/en/tool/pgp-verify-TL1000000054.
Step 3 Run the display version command on the device to check whether the software version
matches the patch version. For details, see section 1.6.
<HUAWEI>display version
Huawei Versatile Routing Platform Software
VRP (R) software, Version 8.xxx (NetEngine 8000 V800R0xxCxxSPCxxx)
Step 4 Upload the patch.PAT file to cfcard:/ using FTP in binary mode, after ensuring that the patch
name does not conflict with any existing file name on the NE8000-M.
Step 5 If the slave MPU or SRU exists, copy the patch to the slave MPU or SRU running the
following command:
<HUAWEI> copy patch.PAT slave#cfcard:/
Step 6 Query the patch unit status. For the NetEngine 8000 M8/M8K/M14/M14K, run the display
patch-information process verbose | include NO | exclude Running command in the
diagnostic view and for the NetEngine 8000 M1A/M1C/M1D/M6/M6K, run the display
patch-information verbose | include NO | exclude Running command in the diagnostic
view. If the following information is displayed, all patch units are running properly. If other
information is displayed, patch units that are not running properly exist. In this case, contact
Huawei R&D engineers.
[~HUAWEI-diagnose]display patch-information process verbose | include NO | exclude
Running
Info: It will take a long time if the content you search is too much or the string you
input is too long, you can press CTRL_C to break.
----------------------------------------------------------------------------------
-----
Slot-id ProcId State PatchType Valid PatchEffectiveTime
PatchFileName
----------------------------------------------------------------------------------
-----
----------------------------------------------------------------------------------
-----

NetEngine 8000 M
The patch is large, and uploading the patch takes some time. If the CF card has sufficient
space, you can upload the patch to the NE8000-M before uninstalling existing patches. If the
patch name conflicts with an existing file name, modify the patch name before uploading the
patch.
----End
3.3.2 Installing the Patch
Use the patch load cfcard:/patch.PAT all run command to install the patch. If you use other
commands, some issues may fail to be resolved.
Run the patch load cfcard:/patch.PAT all run command to load, activate, and run the patch.
The system displays the patch installation results.
For example:
<HUAWEI> patch load cfcard:/patch.PAT all run
Info: Operating, please wait for a moment...done.
Info: Succeeded in running the patch.
After completing the preceding operations, perform an installation check as described in

section 3.4 to verify patch installation. Then perform corresponding operations on
live-network devices as described in section 3.5.
3.4 Verifying Patch Installation

 Query the patch unit status. For the NetEngine 8000 M8/M8K/M14/M14K, run the
display patch-information process verbose | include NO | exclude Running command
in the diagnostic view and for the NetEngine 8000 M1A/M1C/M1D/M6/M6K, run the
display patch-information verbose | include NO | exclude Running command in the
diagnostic view. If the following information is displayed, all patch units are running
properly. If other information is displayed, patch units that are not running properly exist.
In this case, contact Huawei R&D engineers.
[~HUAWEI-diagnose]display patch-information process verbose | include NO | exclude
Running
Info: It will take a long time if the content you search is too much or the string you
input is too long, you can press CTRL_C to break.

NetEngine 8000 M
----------------------------------------------------------------------------------
-----
Slot-id ProcId State PatchType
Valid PatchEffectiveTime PatchFileName
----------------------------------------------------------------------------------
-----
----------------------------------------------------------------------------------
-----

V800R022C00SPC600
<HUAWEI> display patch-information
Patch Package Name :cfcard:/NE8000-M4M8M14V800R022SPH180-C00SPC600.PAT
Patch Package Version :V800R022SPH180
Patch Package State :Running
Patch Package Run Time:2023-08-30 00:57:30

V800R022C10SPC500
<HUAWEI> display patch-information
Patch Package Name :cfcard:/NE8000-M4M8M14V800R022SPH180-C10SPC500.PAT
Patch Package Version :V800R022SPH180
Patch Package State :Running
Patch Package Run Time:2023-08-30 00:57:30
3.5 Follow-up Procedures After Patch Installation

After patch installation, check whether issues described in the NetEngine 8000 M
V800R022SPH180 Issues Resolved.xlsx delivered with the patch release notes exist on the
device. If any issues exist, perform operations listed in the corresponding "Operation Type for
Patch Validation" and "Operation Type for Service Restoration " in the NetEngine 8000 M
V800R022SPH180 Issues Resolved.xlsx. The possible causes are as follows: Restart the
device, perform an master/slave switchover, power off and then power on the board or
subcard, reset the board or subcard, reconfigure the device, or add configurations.
Exercise caution when performing this operation.

NetEngine 8000 M
Patch Release Notes 4 Rollback Procedure
4 Rollback Procedure
4.1 How to Roll Back to the Previous State

If patch installation fails and a rollback is necessary, perform the following steps to roll back
to the previous state.
Step 1 Run the display patch-information command in the user view to check the patch running
status.
Step 2 Run the patch delete all command in the user view to delete all patches.
Step 3 Run the display patch-information command in the user view to check whether the patches
are still running. Ensure that the patches are not running.
----End
When the patch is being uninstalled, do not run any commands. Otherwise, services may
become abnormal or the master main control board may be reset. After the patch is uninstalled,
you are advised to log out all users who logged in through terminal tools.

NetEngine 8000 M
Patch Release Notes 5 Solutions to Common Problems During Patch Installation
5 Solutions to Common Problems During

Patch Installation
5.1 A Message "Error: The system file should be in root

directory." Is Displayed After the patch load all run
Command Is Run to Load a Patch File.
Symptom
<HUAWEI>patch load $_install_mod/patch.PAT all run
Info: Operating, please wait for a moment...
Error: The system file should be in root directory.
Solution
This problem occurs if a patch file to be loaded is not stored in the root directory of the master
MPU. Therefore, to resolve this problem, copy the patch file to the root directory on the CF
card before running the patch load cfcard:/patch.PAT all run command in the user view.
5.2 A Message "Error: The command is invalid in the

current patch status." Is Displayed After the patch load all
run Command Is Run to Load a Patch File.
Symptom
<HUAWEI>patch load cfcard:/patch.PAT all run
Error: The command is invalid in the current patch status.
Solution
This problem occurs if a patch has been installed and the patch is not in the running state.
Therefore, to resolve this problem, run the display patch-information command in the user
view to check whether a patch has been installed and whether the patch is in the running state.
<HUAWEI>display patch-information

NetEngine 8000 M
Patch Package Name :cfcard:/patch.PAT

Patch Package Version :V800R022SPHxxx
Patch Package State :Deactive
In this example, a patch has been loaded and the patch is not in the running state.
In this case, before loading the new patch, run the patch load cfcard:/patch.PAT all run
command in the user view to have the existing patch enter the running state or run the patch
delete all command to delete the existing patch.
5.3 A Message "Error: The patch is incompatible with the

existing patch." Is Displayed After the patch load all run
Command Is Run to Load a Patch File.
Symptom
<HUAWEI>patch load cfcard:/patch.PAT all run
Error: The patch is incompatible with the existing patch.
Solution
This problem occurs if the patch in the file to be loaded is not an incremental one of the
existing patch on the device. Therefore, to resolve this problem, run the patch delete all
command in the user view to delete the existing patch before loading the new patch.
5.4 The Message "Error: The target patch does not support
the hardware." Is Displayed After the patch load all
Command Is Run to Load a Patch
Symptom
<HUAWEI>patch load patch.PAT all run
Error: The target patch does not support the hardware of slot X.
Solution
The target patch version is incompatible with the device hardware. You need to load the latest
patch or power off the boards that are not supported by the patch and then reload the patch.
For details about patch package selection, see section 1.5.

NetEngine 8000 M
5.5 The Message "Error: The target patch does not support
the current main control board." Is Displayed After the
patch load all Command Is Run to Load a Patch
Symptom
Error: The target patch does not support the current main control board.
Solution
The patch package does not match the current device or the main control board. You need to
replace the patch package. For details about patch package selection, see section 1.5.
5.6 The Message "Error: slot X is not ready, please try later
when the system is stable." Is Displayed After the patch load all
Command Is Run to Load a Patch
Symptom
Error: slot 7 is not ready, please try later when the system is stable.
Solution
This message is displayed if board power-on and patch package loading are being performed
at the same time. To resolve this issue, load the patch package after the board is powered off,
and then power on the board after the patch package is loaded successfully.
5.7 The Message "Error: The next startup patch is required

for the next startup of the system software." Is Displayed
After the reset patch-configure next-startup Command Is
Run to Delete the Next-Startup Patch
Symptom
<HUAWEI>reset patch-configure next-startup
Error: The next startup patch is required for the next startup of the system software.

NetEngine 8000 M
Solution
Select the correct patch package by referring to section 1.7.
5.8 The Message "Error: Failed to clear the board

configuration." Is Displayed After the patch delete all
Command Is Run to Uninstall a Patch
Symptom
<HUAWEI>patch delete all
This will delete the patch. Are you sure? [Y/N]:y
Error: This access interface can not be deleted because there are online users on the
interfaceError: Failed to clear the board configuration.
Solution
Refer to upgrade operations in RUI scenarios. Specifically, shut down the RBS, enable users
to log out, uninstall the patch, and then restore the RBS.
1. Run the shutdown command in the RBS view to shut down the RBS.
Command examples:
[~HUAWEI] remote-backup-service rbs
[*HUAWEI-rm-backup-service-rbs] shutdown
[*HUAWEI-rm-backup-service-rbs]commit
2. Shut down the BRAS user access interface.

3. Run the cut command to enable users to log out.
Command examples:
cut access-user domain domain-name
4. Run the patch delete all command to delete the patch.

5. Run the undo shutdown command in the RBS view to restore the RBS.
Command examples:
[~HUAWEI] remote-backup-service rbs
[*HUAWEI-rm-backup-service-rbs] undo shutdown
[*HUAWEI-rm-backup-service-rbs]commit
6. Restore the shutdown interface.
5.9 How Can I Set a Patch as That to Be Loaded at the Next

Startup?
A: Run the following commands on the master and slave main control boards:

NetEngine 8000 M
<HUAWEI> startup patch cfcard:/patch.PAT all

Info: Operating, please wait for a moment.....done.
Info: Succeeded in setting startup the patch.

NetEngine 8000 M
Patch Release Notes A Third-Party Software Vulnerabilities Fixed
A Third-Party Software Vulnerabilities

Fixed
You can query vulnerabilities at the National Vulnerability Database (NVD) website
(https://web.nvd.nist.gov/view/vuln/search) by CVE ID.

NetEngine 8000 M
A.1 V800R022C00SPC600
Table A-1: Fixed vulnerabilities in Huawei-developed code (including products and integrated
platforms/components/libraries)
Vulnerability ID CVE ID Actual Vulnerability Solution Version

CVSS Description
score
HWPSIRT-2023- CVE-20 7.5 Processing some V800R022SPH180
33676 23-2650 specially crafted ASN.1
object identifiers or data
containing them may be
very slow. An OBJECT
IDENTIFIER is
composed of a series of
numbers -
sub-identifiers - most of
which have no size
limit. When one of the
sub-identifiers in the
OBJECT IDENTIFIER
is very large (these are
sizes that are seen as
absurdly large, taking
up tens or hundreds of
KiBs), the translation to
a decimal number in
text may take a very
long time. The time
complexity is O(n^2)
with 'n' being the size of
the sub-identifiers in
bytes (*). It would
cause a Denial of
Service.

NetEngine 8000 M

CVSS Description
score
HWPSIRT-2023- CVE-20 5.9 A timing based side V800R022SPH180
25691 22-4304 channel exists in the
OpenSSL RSA
Decryption
implementation which
could be sufficient to
recover a plaintext
across a network in a
Bleichenbacher style
attack. To achieve a
successful decryption
an attacker would have
to be able to send a very
large number of trial
messages for
decryption. The
vulnerability affects all
RSA padding modes:
PKCS#1 v1.5,
RSA-OEAP and
RSASVE.

NetEngine 8000 M
Softwa CVE ID CVSS Vulnerability Solution Version

Software re Score Description
Name Versio
n
OpenSSL 1.1.1- CVE-20 7.4 During certificate V800R022SPH120
1.1.1n 23-0286 verification, the
logic for obtaining a
1 valid CRL calls the
1 ASN1_TYPE_cmp
function to check
whether the
x400Address field in
the distribution point
field of the X509
certificate is the
same as that in the
distribution point
field of the CRL.
However, the
x400Address field is
incorrectly parsed as
the ASN1_STRING
* type, memory
overwriting or even
denial of service
may occur.

NetEngine 8000 M
A.2 V800R022C10SPC500
Table A-1: Fixed vulnerabilities in Huawei-developed code (including products and integrated
platforms/components/libraries)

CVSS Description
score
HWPSIRT-2023- CVE-20 7.5 Processing some V800R022SPH180
33676 23-2650 specially crafted ASN.1
object identifiers or data
containing them may be
very slow. An OBJECT
IDENTIFIER is
composed of a series of
numbers -
sub-identifiers - most of
which have no size
limit. When one of the
sub-identifiers in the
OBJECT IDENTIFIER
is very large (these are
sizes that are seen as
absurdly large, taking
up tens or hundreds of
KiBs), the translation to
a decimal number in
text may take a very
long time. The time
complexity is O(n^2)
with 'n' being the size of
the sub-identifiers in
bytes (*). It would
cause a Denial of
Service.


NE8000 M V800R022SPH180 Patch Release Notes

Uploaded by

Copyright:

Available Formats

NE8000 M V800R022SPH180 Patch Release Notes

Uploaded by

Document Information

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

NE8000 M V800R022SPH180 Patch Release Notes

Uploaded by

Copyright:

Available Formats

NetEngine 8000 M

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2023-08-3030) Huawei Proprietary and Confidential i

1 Patch Package Information ..................................................................................................... 1

2 Resolved Issues ........................................................................................................................ 7

3 Installing the Patch .................................................................................................................... 9

4 Rollback Procedure .................................................................................................................. 13

5 Solutions to Common Problems During Patch Installation .................................................... 14

Issue 01 (2023-08-3030) Huawei Proprietary and Confidential ii

A Third-Party Software Vulnerabilities Fixed ...................................................................... 19

Issue 01 (2023-08-3030) Huawei Proprietary and Confidential iii

1 Patch Package Information

1.1 Product Name

1.2 Product Model

1.3 Patch Number

1.4 Release Date

Issue 01 (2023-08-3030) Huawei Proprietary and Confidential 1

Released Patch Version Patch Release Date

1.5 Patch File Description

File Name File Description File Size

NE8000-M8M14V800R022SPH180-C00SPC200.PAT V800R022SPH180 97,266,049 bytes

1.6 Product Version and Required Patches

NetEngine 8000 NE8000-M4M8M14V800R022SPH180-C10SPC500.PAT

Issue 01 (2023-08-3030) Huawei Proprietary and Confidential 2

Product Version Latest Patch Version

NetEngine 8000 M6 NE8000-M6-V800R022SPH180- C10SPC500.PAT

1.7 Relationship Between Patches

Issue 01 (2023-08-3030) Huawei Proprietary and Confidential 3

1.7.1 NetEngine8000 M4&M8&M8K&M14&M14K

Latest Patch Earlier Patch Function Incremental

V800R022SPH180 V800R022HP1521 Inheritance Incremental

1.7.2 NetEngine8000 M4&M8&M8K&M14&M14K

Latest Patch Earlier Patch Function Incremental

V800R022SPH180 V800R022HP1521 Inheritance Incremental

Issue 01 (2023-08-3030) Huawei Proprietary and Confidential 4

1.8 Impact of Patch Installation

In a scenario in which a user uses Telnet to access a NE8000-M through an interface on an

Issue 01 (2023-08-3030) Huawei Proprietary and Confidential 5

1.10 Naming Rules for Patches

Issue 01 (2023-08-3030) Huawei Proprietary and Confidential 6

2.1 How to Obtain Issues Resolved

Issue 01 (2023-08-3030) Huawei Proprietary and Confidential 7

Issue 01 (2023-08-3030) Huawei Proprietary and Confidential 8

3 Installing the Patch

3.1 Tool-based Patch Upgrade (Recommended)

3.2 iMaster NCE-IP Patch Upgrade

Download Path for Carriers：

Issue 01 (2023-08-3030) Huawei Proprietary and Confidential 9

3.3 Installing the Patch

Issue 01 (2023-08-3030) Huawei Proprietary and Confidential 10

3.3.2 Installing the Patch

After completing the preceding operations, perform an installation check as described in

3.4 Verifying Patch Installation

Issue 01 (2023-08-3030) Huawei Proprietary and Confidential 11

3.4.1 NetEngine8000 M4&M8&M8K&M14&M14K

3.4.2 NetEngine8000 M4&M8&M8K&M14&M14K

3.5 Follow-up Procedures After Patch Installation

Issue 01 (2023-08-3030) Huawei Proprietary and Confidential 12