Ne40e M2kv800r022c00spc600upgradeguideimasternce Ip
Ne40e M2kv800r022c00spc600upgradeguideimasternce Ip
V800R022C00SPC600
Upgrade Guide (iMaster NCE-IP)
Issue 01
Date 2022-10-31
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.
Purpose
This document describes how to upgrade NE40E-M2Ks to V800R022C00SPC600 as well as
how to roll back the upgrade. It also provides answers to frequently asked questions (FAQs)
and troubleshooting information.
Intended Audience
This document is intended for upgrade engineers who are familiar with the following:
Networking and NE versions of the current network
Device O&M operations
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates an imminently hazardous situation which, if
not avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not
avoided, could result in death or serious injury.
Indicates a potentially hazardous situation which, if not
avoided, may 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.
Calls attention to important information, best practices
and tips.
NOTE is used to address information not related to
personal injury, equipment damage, and environment
deterioration.
Change History
Version Description Date Author
01 This is the first official release. 2021-04-30 liuxin
Contents
The information in this document is subject to change without notice. Contact Huawei
technical support to obtain the latest upgrade guide before the upgrade.
The GUIs of iMaster NCE-IP described in this document may differ from the actual GUIs due
to iMaster NCE-IP upgrades.
General Precautions
Before starting the upgrade, contact Huawei technical support to confirm your upgrade
scheme. This helps minimize upgrade risks.
Devise an emergency plan before starting the upgrade, so that you can recover services
as soon as possible if a problem occurs during the upgrade.
If you encounter exceptions or problems you cannot resolve, such as service interruption,
during the upgrade, stop the upgrade procedure immediately and contact Huawei
technical support. Do not continue the upgrade before obtaining guidance from Huawei
engineers.
Do not adjust the network when devices are being upgraded. Do not reset or reseat any
boards or adjust cables during the upgrade.
Manually back up NE data before you start the upgrade, so that NE configurations can be
restored if they are lost during the upgrade.
Do not modify service configurations during the upgrade.
Do not use any fault collection tool or PMI tool during the upgrade. If you use such tools,
users who have logged in to target devices using iMaster NCE-IP will be forcibly logged
out.
Ensure that no power migration operations are performed before upgrade.
The following table lists the comparison between the old and new sampling paths of the router
for reference during the upgrade. For details about the sampling paths supported by the
current product, see the Telemetry-based Performance Indicator List.
1 huawei-devm:devm/cpuInfos/cpuInfo huawei-debug:debug/cpu
-infos/cpu-info
2 huawei-devm:devm/memoryInfos/memoryInfo huawei-debug:debug/me
mory-infos/memory-info
3 huawei-ifm:ifm/interfaces/interface huawei-ifm:ifm/interface
s/interface
4 huawei-devm:devm/fans/fan N/A
Before the upgrade, delete and save the configuration of the existing telemetry sampling
path before the upgrade. For example, the configuration in V800R022C00SPC600 is as
follows :
#
telemetry
#
sensor-group sgroup1
sensor-path huawei-ifm:ifm/interfaces/interface/ifStatistics
sensor-path huawei-ifm:ifm/interfaces/interface/ifStatistics/ethPortErrSts
sensor-path huawei-devm:devm/fans/fan
sensor-path
huawei-devm:devm/powerSupplys/powerSupply/powerEnvironments/powerEnvironment
sensor-path huawei-devm:devm/temperatureInfos/temperatureInfo
sensor-path huawei-ifm:ifm/interfaces/interface
sensor-path huawei-ifm:ifm/interfaces/interface/ifClearedStat
sensor-path huawei-ifm:ifm/interfaces/interface/ifDynamicInfo
sensor-path huawei-devm:devm/ports/port/opticalInfo
sensor-path huawei-devm:devm/cpuInfos/cpuInfo
sensor-path huawei-devm:devm/memoryInfos/memoryInfo
sensor-path huawei-qos:qos/qosBuffers/qosBuffer
sensor-path
huawei-qos:qos/qosIfQoss/qosIfQos/qosPolicyApplys/qosPolicyApply/qosPolicyStats
/qosPolicyStat/qosRuleStats/qosRuleStat
sensor-path huawei-qos:qos/qosPortQueueStatInfos/qosPortQueueStatInfo
#
destination-group dest1
ipv4-address X.X.X.X port 2105 protocol grpc no-tls
#
subscription sub1
sensor-group sgroup1 sample-interval 30000
destination-group dest1
#
Need to enter sensor-group view, Delete all sensor-paths. For example:
<HUAWEI>system-view
[~HUAWEI]telemetry
[~HUAWEI-telemetry] sensor-group sgroup1
[~HUAWEI-telemetry-sensor-group-sgroup1]undo sensor-path
huawei-ifm:ifm/interfaces/interface/ifStatistics
[*HUAWEI-telemetry-sensor-group-sgroup1]undo sensor-path
huawei-ifm:ifm/interfaces/interface/ifStatistics/ethPortErrSts
[*HUAWEI-telemetry-sensor-group-sgroup1]undo sensor-path
huawei-devm:devm/fans/fan
[*HUAWEI-telemetry-sensor-group-sgroup1]undo sensor-path
huawei-devm:devm/powerSupplys/powerSupply/powerEnvironments/powerEnvironment
[*HUAWEI-telemetry-sensor-group-sgroup1]undo sensor-path
huawei-devm:devm/temperatureInfos/temperatureInfo
[*HUAWEI-telemetry-sensor-group-sgroup1]undo sensor-path
huawei-ifm:ifm/interfaces/interface
[*HUAWEI-telemetry-sensor-group-sgroup1]undo sensor-path
huawei-ifm:ifm/interfaces/interface/ifClearedStat
[*HUAWEI-telemetry-sensor-group-sgroup1]undo sensor-path
huawei-ifm:ifm/interfaces/interface/ifDynamicInfo
[*HUAWEI-telemetry-sensor-group-sgroup1]undo sensor-path
huawei-devm:devm/ports/port/opticalInfo
[*HUAWEI-telemetry-sensor-group-sgroup1]undo sensor-path
huawei-devm:devm/cpuInfos/cpuInfo
[*HUAWEI-telemetry-sensor-group-sgroup1]undo sensor-path
huawei-devm:devm/memoryInfos/memoryInfo
[*HUAWEI-telemetry-sensor-group-sgroup1]undo sensor-path
huawei-qos:qos/qosBuffers/qosBuffer
[*HUAWEI-telemetry-sensor-group-sgroup1]undo sensor-path
huawei-qos:qos/qosIfQoss/qosIfQos/qosPolicyApplys/qosPolicyApply/qosPolicyStats
/qosPolicyStat/qosRuleStats/qosRuleStat
[*HUAWEI-telemetry-sensor-group-sgroup1]undo sensor-path
huawei-qos:qos/qosPortQueueStatInfos/qosPortQueueStatInfo
[*HUAWEI-telemetry-sensor-group-sgroup1]commit
[~HUAWEI-telemetry-sensor-group-sgroup1]return
<HUAWEI>save
[*HUAWEI-telemetry-sensor-group-sgroup1]sensor-path
huawei-qos:qos/qosBuffers/qosBuffer
[*HUAWEI-telemetry-sensor-group-sgroup1]sensor-path
huawei-qos:qos/global-query/interface-traffic-policy-statisticss/interface-traf
fic-policy-statistics/rule-based-staticss/rule-based-statics
[*HUAWEI-telemetry-sensor-group-sgroup1]sensor-path
huawei-qos:qos/global-query/default-queue-statisticss/default-queue-statistics
[*HUAWEI-telemetry-sensor-group-sgroup1]commit
[~HUAWEI-telemetry-sensor-group-sgroup1]return
<HUAWEI>save
After the upgrade, the collector re-adapts to the new proto file.
The command output contains the peer configuration, indicating that the IKEv1 configuration
exists. Then go to the next step.
Step 2 Check whether an IKEv1 tunnel is established for each peer.
<HUAWEI> system-view
[~HUAWEI] display ike sa | include v1
current sa Num :2000
Single-homing :2000 Multi-homing M and M|B :0 Multi-homing S and S|B :0
None-backup sa :2000 Backup sa :0
Spu board slot 8, IKE SA Information:
Current IKE SA number: 2
-----------------------------------------------------------------------------
conn-id peer flag phase ext vpn
-----------------------------------------------------------------------------
954 10.0.0.149 RD v1:2 - -
57443 10.0.0.149 RD|ST v1:1 - -
If tunnel information is displayed, IKEv1 tunnel information is in use. In this case, the IKEv1
MOD file needs to be installed.
For details, see the "1.6 Installing the IKEv1 MOD File".
If the IKEv1 MOD file is not installed and an upgrade is performed, the IKEv1 configuration
will be lost, IPSec services will be adversely affected, and no IKEv1 tunnel can be
established.
By default, the IKEv1 function is not supported in the target version. After the upgrade, the IKEv1
configuration will be lost, and IPSec services will be adversely affected.
For the IKEv1 MOD-based upgrade in a dual-system environment, upgrade the backup device and
then the master device. If the IKEv1 MOD file is not installed on the backup device, the device
cannot receive the backup data of IKEv1 tunnels.
If IKEv1 is configured but the IKEv1 MOD file is not specified for the next startup, the IKEv1
configuration will be lost after an upgrade. As a result, the restored configurations become
inconsistent with those on the peer end, and tunnels cannot be established. In this case, check the
IKEv1-related configurations and reconfigure the IPSec and IKE encryption and authentication
algorithms.
----End
If E-Trunk has been deployed before an upgrade, check whether a key has been configured. If
not, configure the same key (different from the default key 00E0FC0000000000) in the
E-Trunk view on both ends of the E-Trunk before the upgrade. The default key cannot be used
for authentication after the upgrade. If you do not perform this configuration, E-Trunk
negotiation will fail after the upgrade, affecting services.
Step 2 In the existing E-Trunk view, check whether an encryption key is configured. If an encryption
key is configured, as shown in the following command output, the upgrade of the E-Trunk is
not affected.
[HUAWEI-e-trunk-1]display this
#
e-trunk 1
security-key simple root@123
authentication-mode enhanced-hmac-sha256
#
return
If an encryption key is not configured in the E-Trunk view, as shown in the following
command output, the upgrade of the E-Trunk will be affected.
[HUAWEI-e-trunk-2]display this
#
e-trunk 2
authentication-mode enhanced-hmac-sha256
#
return
Step 3 Configure an encryption key in the E-Trunk view where an encryption key does not exist.
Note: Configure the same encryption key in the E-Trunk view on both ends of an E-Trunk.
[HUAWEI-e-trunk-2]security-key cipher Root@1234
[HUAWEI-e-trunk-2]disp
[HUAWEI-e-trunk-2]display this
#
e-trunk 2
security-key cipher %^%#e+,;P~l@H9Tk]{%K)b9Ad_ZgS/th}5N"i_>!E&N*%^%#
authentication-mode enhanced-hmac-sha256
#
return
Step 4 After the configuration is complete, run the display e-trunk command to check whether
E-Trunk negotiation works normally. If the State field value is Master or Backup and the
Send and Receive field values increase normally, the E-Trunk function is normal. Otherwise,
check whether the encryption keys configured on both ends of the E-Trunk are the same.
[HUAWEI-e-trunk-1]display e-trunk 1
The E-Trunk information
E-TRUNK-ID : 1 Revert-Delay-Time (s) : 120
Priority : 100 System-ID : 38ba-234a-ed02
VPN-Instance : _public_
Peer-IP : 1.1.1.1 Source-IP : 1.1.1.2
State : Master Causation : PRI
Send-Period (100ms) : 10 Fail-Time (100ms) : 200
Receive : 7 Send : 25
RecDrop : 0 SndDrop : 0
Peer-Priority : 100 Peer-System-ID : 38ba-26be-9a01
Peer-Fail-Time (100ms) : 200 BFD-Session : -
Description : -
Sequence : Disable
Dynamic-BFD : Disabled BFD-State : -
TX (ms) : - RX (ms) : -
Multiplier : -
----End
aaa
local-user root password
irreversible-cipher
$1c$]f(3Q<j7uS$!0!)8@e`\+lj]vQx\2
l&y-$M(|\n_ERFU_BF$!6X$
local-user root service-type ssh
local-user root user-group
manage-ug
#
ssh user root
ssh user root authentication-type
password
ssh user root service-type stelnet
snetconf
ssh user root service-type stelnet
Enabling snmp-agent protocol source undo snmp-agent protocol source
SNMP and all-interface all-interface
SSH on all undo ssh server-source
interfaces all-interface
undo ssh ipv6 server-source
all-interface
ssh server-source -i Ethernet0/0/0
4. If weak algorithms and protocols exist in the system, an alarm is reported to prompt you
to perform rectification.
a. If weak algorithms and protocols exist in the system, the system generates the
following alarm:
<HUAWEI>display alarm active | include secure
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.
1:Critical 2:Major 3:Minor 4:Warning
--------------------------------------------------------------------------
------
Sequence AlarmId Level Date Time Description
--------------------------------------------------------------------------
------
59 0xF10466 2 2021-10-07 11:18:40 With the development of
cryptographic technologies and the improvement of computing capabilities, some
cryptographic algorithm and protocols are deprecated. Please use more secure
algorithms and protocols. (Type=insecure algorithm)
58 0xF10466 2 2021-10-07 11:18:40 With the development of
cryptographic technologies and the improvement of computing capabilities, some
cryptographic algorithm and protocols are deprecated. Please use more secure
algorithms and protocols. (Type=insecure protocol)
--------------------------------------------------------------------------
------
b. You can run the display security risk command to query the weak protocols or
algorithms used in the system. Perform security hardening based on Repair Action
displayed to clear the alarm.
<HUAWEI>display security risk
Risk Level : high
Feature Name : SSH_CLIENT
Risk Type : insecure-algorithm
Risk Information : Insecure key exchange algorithms (dh_group1_sha1,
dh_group_exchange_sha1, dh_group14_sha1, ecdh_sha2_nistp256,
ecdh_sha2_nistp384, ecdh_sha2_nistp521) are enabled in SSH client
Before running the reset saved-configuration command or using the reset button to clear the
configuration, check whether the defcfg file is specified.
If the default behavior of the device needs to be the same as the previous one, you can run the
startup default-configuration configuration-file command to specify the customized defcfg file
during the production of a new device.
You can also customize the defcfg file for a live-network device when it is upgraded to
V800R021C00SPC100 or later If you add the preceding removed configurations to the customized
defcfg, the device retains the same default configuration restoration behavior as that in the earlier
version. For details about how to load the configuration file, see 6 Configuring the Default
Configuration File.
If a device is downgraded to a version earlier than V800R021C00SPC100, delete the default
configuration file or load the defcfg file customized for the source version.
You can disable the weak algorithm in V800R022C00SPC600. If you do not need to disable it,
setting the latest .defcfg file is recommended. This prevents the weak algorithm from becoming
unavailable after the configuration is cleared using the reset saved-configuration command or the
reset button.
Prerequisites
1. The version is upgraded. By default, the new version still uses the license file of the old
version.
2. The license file of the new algorithm is activated.
3. Rollback is performed.
Softwar The software file and its The software package and its CMS signature file are
e PGP signature file are downloaded.
downlo downloaded.
ading
Softwar The software file that Both the software package and its CMS signature file
e has been manually are imported.
import verified is imported.
NE Software files can be Software files to be imported can be selected only
upgrad selected from the from the software library.
e software library or the
FTP directory on the
server.
For details, see 3.1.4 Using the OpenPGP Tool to Verify Integrity of a File.
If the device runs V800R021C00SPC100 or a later version, it checks whether the CRL file is
updated too long ago. If the time during which the CRL file is not updated exceeds the
precaution threshold, the device reports an alarm (SSLCertificateExpiredEarlyWarning)
indicating that the CRL file has expired.
To check the next update time of the CRL, you can download the CRL file to a local PC and
double-click the file to perform the check.
You can run the ssl certificate alarm-threshold early-alarm <time> command in the system
view to set the time threshold for the CRL file. The default time threshold is 90 days.
If you need to use the CRL file, update it periodically to prevent the device from reporting
alarms due to expiration.
This chapter describes the process for upgrading an earlier version to the target version and
lists the estimated time required for each procedure.
Procedure
Step 1 Open the Network Management app and choose Maintenance > NE Software Management >
NE Data Backup/Restoration from the main menu.
Step 2 On the NE View tab page, select one or more NEs and click Update Version.
Step 4 In the Version column, check whether the current NE software version is the same as the
source version.
Step 5 (Optional) Back up the NE data of the current version. If you have backed up NE data earlier,
skip this step.
----End
Operation Result
If the operation is successful, the updated version information is displayed on the NE View
tab page and the NE Type area.
Troubleshooting
If the operation fails, the Update Version dialog box displays the cause in the Operation
Result column. Rectify the fault based on the displayed failure cause. The failure cause may
contain a hyperlink that you can click for more detailed information.
4 Upgrade Process
2. Right-click on the NE Software Library Management page and choose Import from
the shortcut menu.
3. In the Import dialog box, choose NE Series > NE40E(V8) > NE40E-M2K from the
4. Specify the storage path of the target system software, upload the software, and enter
descriptive text in the Description text box.
5. Click OK to import the target system software to the NE software library on iMaster
NCE-IP.
6. (Optional) On the NE Software Management Library page, you can also import patch
packages, PAF files, and License files. To import a Patch Package, set File Type to
Patch Package.
Set Path to the storage path of the patch package, set Version and Description, and click
OK.
The method of importing a PAF file or License file is the same as that of importing a
patch package.
Step 2 Choose Maintenance > NE Software Management > NE Upgrade Task Management
from the main menu.
Step 3 Right-click in the Task View area and choose New Task > Software Upgrade/Downgrade
Task from the shortcut menu.
You need to obtain the version information. If the version information has not been obtained,
perform the operation described in Step 2 in section 3.1.7 Checking NE Software Versions.
2. In the Confirm dialog box, click Yes after confirming that the selected software version
is correct.
3. In the Select Software dialog box, check whether the path, name, and type of the
selected file are correct. If not, delete the file from the right pane and select the file again
in the specified directory in the left pane.
(Optional) Import the patch package and PAF file. Select the desired files on the left and
click xxx[L(1] to move the files to the right.
(Optional) Import the configuration file and license file. Click Select File. In the dialog
box that is displayed, select the desired file on the left, click to move the file to the
right, and click OK.
4. Click Check NE(s) Memory to check whether the available space of the CF card on the
NE is sufficient.
a. If Memory Status is No Need to Clear for the NE, click Close. Then proceed to
Step 1
b. If Memory Status is Need to Clear for the NE, click Need to Clear.
c. Select unneeded files, move them to the right pane, and click Delete.
Exercise caution when deleting files. Ensure that these files will not be used later.
d. In the High Risk dialog box, confirm that the files to be deleted are correct, select
the check box, and click Yes.
e. Check that the files are deleted successfully. Then click Close.
f. Click Close to close the Select NE File(s) dialog box. Then, click Close to close the
Memory Status for NE(s) dialog box.
g. Click Check NE(s) Memory again to check the memory space status. If the
memory space is still insufficient, continue to delete unnecessary files.
h. Click OK.
i. If Configure Operation changes to Select Software to Load for Load Software, as shown
in the following figure, the loading is successful.
6. (Optional) Click Configure Activation.In the Configure Activation dialog box, set
Activation Type and other information according to the upgrade plan.
You can select Pause Before Current Operation for each operation (except Precheck) to delay the
operation as required. If you want each upgrade operation to be performed immediately after the
previous operation is completed, leave Pause Before Current Operation unselected. It is
recommended that you select Pause Before Current Operation for the Activate operation.
If the upgrade time is tight at night, you can load, save, and back up files during the daytime, select
Pause Before Current Operation for the Activate operation, and continue the upgrade task at
night.
8. Click Next.
Step 6 Confirm upgrade task information.
Step 7 Click OK.
----End
Operation Result
After the upgrade task is created, it is displayed on the NE Upgrade Task Management
page.
The procedure for creating a batch upgrade task is the same as that for creating a common upgrade task,
as shown in the following figure.
Follow-up Procedure
After the upgrade task is created, start the task manually if the start time is not specified
during task creation.
----End
Operation Result
If Operation Status is Succeeded after the upgrade task is executed, the upgrade task is
complete. If Operation Status is Failed, check the failure cause by clicking the hyperlink in
the Operation Status column. Then re-create the upgrade task and perform the upgrade
again.
Procedure
Step 1 Check the post-upgrade inspection report.
1. On the NE Upgrade Task Management tab page, click on the left of the upgrade
task and select one or more NEs.
2. After the status of the Postcheck operation is displayed as , learn the execution
status of each check item.
Step 2 Check the upgrade report.
1. Select the upgrade task and click Generate Report. Wait 1 to 3 minutes until the report
is generated.
2. In the report, view the alarms generated before and after the upgrade. The alarm data
highlighted in red indicates that the alarms are generated before the upgrade, and the
alarm data highlighted in blue indicates that the alarms are generated after the upgrade.
----End
5 Post-upgrade Check
To double-check whether services on the network are normal after the upgrade, perform the
following steps:
Step 1 Use iMaster NCE-IP to check whether new fault alarms are generated on NEs.
Step 2 Use iMaster NCE-IP to check whether services are normal based on the service topology and
other information.
----End
To resolve the differences between versions caused by the security hardening of the default
behavior, the function of loading the default configuration file defcfg is provided. You can
save the login user information required for DCN plug-and-play and the default
configurations required by other customers to the defcfg file and load the file to the
device.Activate the pre-configuration file after the upgrade.
Before running the reset saved-configuration command or pressing the reset button to clear
configurations, you are advised to check whether the .defcfg file is configured as required.
Procedure
Step 1 Run the display ha component running-state | include CFG9 command to check the ID of
the process where the CFG component resides. The value in the Process column is the ID of
the process where the CFG component resides.
<HUAWEI> system-view
[~HUAWEI] diagnose
[~HUAWEI-diagnose] display ha component running-state | include CFG9
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.
--------------------------------------------------------------------------------
NAME CID PID Type Version Board
Process State
--------------------------------------------------------------------------------
CFG9 0x80CB000C 0xCB0009 0xCB 1.2.103 17
3 PRIMARY
--------------------------------------------------------------------------------
Step 2 Run the display cmf-info file debug-info process locationId command to check whether the
device has a default configuration file.
In the preceding command, locationId indicates the ID of the process where the CFG
component resides. An example is as follows:
<HUAWEI> system-view
[~HUAWEI] diagnose
[~HUAWEI-diagnose] display cmf-info file debug-info process 3
If the value of Setting state is true, the device has a default configuration file.
If no command output is displayed, the device does not have a default configuration file. In
this case, perform step 3 to set a default configuration file.
Step 3 Set .defcfg file.
1. Create a configuration file with the file name extension .defcfg.
2. The following is an example of the content of the .defcfg file:
!Router function begin
#
undo crypto weak-algorithm disable
#
aaa
local-user root password irreversible-cipher
$1c$]f(3Q<j7uS$!0!)8@e`\+lj]vQx\2l&y-$M(|\n_ERFU_BF$!6X$
local-user root service-type ssh
local-user root user-group manage-ug
local-user root expire 2000-01-01
user-password password-force-change disable
#
snmp-agent protocol source all-interface
#
stelnet server enable
snetconf server enable
ssh user root
ssh user root authentication-type password
ssh user root service-type stelnet snetconf
ssh server-source all-interface
ssh ipv6 server-source all-interface
#
ssh server key-exchange dh_group_exchange_sha256 dh_group_exchange_sha1
dh_group14_sha1 ecdh_sha2_nistp256 ecdh_sha2_nistp384 ecdh_sha2_nistp521
#
ssh server publickey ecc rsa rsa_sha2_256 rsa_sha2_512
#
ssh client key-exchange dh_group_exchange_sha256 dh_group_exchange_sha1
dh_group14_sha1 ecdh_sha2_nistp256 ecdh_sha2_nistp384 ecdh_sha2_nistp521
#
ssh client publickey ecc rsa rsa_sha2_256 rsa_sha2_512
#
return
!Router function end
An NE40E-M2K can be rolled back to the source version using a software downgrade task.
Procedure
The procedure for creating a software downgrade task is similar to that for creating a software
upgrade task. The difference lies in that Task Type is Downgrade for a software downgrade
task. For details, see section "4.1 Creating an Upgrade Task".
Success Criteria
The device version is the source version.
The device runs properly, and all services are normal.
Troubleshooting
None
Step 1 (Optional) To use the IKEv1 function, load the MOD file for the upgrade. Log in to
https://support.huawei.com, apply for the system software package, download the MOD file
with the system software package, and copy the MOD file to the root directory on CF cards or
FLASH.
Before upgrading the device to V800R022C00SPC600, upload MOD to the $_install_mod directory
of the CF cards or FLASH and specify the MOD file to be loaded for the next startup.
In a dual-system scenario, load the MOD file on the backup device first. If the IKEv1 MOD file is
not loaded on the backup device, the device cannot receive IKEv1 backup data.
If the MOD file is not installed, the IKEv1 function is unavailable and related commands cannot be
run.
The configuration information of any other MPU is the same as that of MPU 11.
System will reboot! Continue? [Y/N]:y
4. Run the system-view command to enter the system view. Run the ike v1 enable
command to enable IKEv1 and save the configuration.
<HUAWEI> system-view
[~HUAWEI] ike v1 enable
[*HUAWEI] commit
[~HUAWEI] quit
Repeat the preceding steps to delete all IKEv1 configurations, and then continue the
uninstallation process.
b. Run the system-view command to enter the system view, run the undo ike v1
enable command to disable IKEv1, and save the configuration.
[~HUAWEI] undo ike v1 enable
[*HUAWEI] commit
After IKEv1 is disabled, wait for 240 seconds to ensure that all resources are
released. An attempt made within 240s to uninstall the file fails, and the system
displays a message indicating that the uninstallation cannot be performed.
c. Run the command uninstall-module V800R022C00SPC600_IKE_V1.X.MOD to
uninstall MOD file.
<HUAWEI> uninstall-module V800R022C00SPC600_IKE_V1.X.MOD
This will uninstall the module. Are you sure? [Y/N]:y
Info: Operating, please wait for a moment...
Info: uninstalling V800R022C00SPC600_IKE_V1.X.MOD
.........done.
Info: Succeeded in uninstalling the module.
Before uninstalling the IKEv1 MOD file, you need to disable IKEv1 and wait for 240 seconds.
Before disabling IKEv1, you must delete IKE configurations. Otherwise, an error message is
displayed.
----End