Download

Title	Size	Downloads
SECPATH5080L-CMW710-R9900P33_IPE.zip	126.79 MB
SECPATH5080L-CMW710-R9900P33_BIN.zip	120.56 MB
H3C_SECPATH5080L-CMW710-R9900P33_Release_Notes.pdf	313.28 KB
H3C_SECPATH5080L-CMW710-R9900P33_Release_Notes_(Software_Feature_Changes).pdf	210.36 KB

H3C SECPATH5080L-CMW710-R9900P33 Release Notes

Contents

Version information· 1

Version number 1

Supported browsers· 1

Version compatibility matrix· 1

Upgrade restrictions and guidelines· 3

Hardware feature updates· 3

Software feature and command updates· 3

MIB updates· 3

Operation changes· 4

Restrictions and cautions· 4

Registering and installing licenses· 4

Open problems and workarounds· 5

List of resolved problems· 5

Resolved problems in R9900P33· 5

Resolved problems in R9900P30· 5

Resolved problems in R9900P2701· 5

Resolved problems in R9900P24· 6

Version information

Version number

Version number: H3C Comware Software, Version 7.1.064, Release 9900P33

You can see the version number with the display version command in any view.

Table 1 Version history

Version number	Last version	Release date	Version type	Remarks
R9900P33	R9900P30	2025-12-22	Release	Annual version
R9900P30	R9900P2701	2025-09-23	Release	Annual version
R9900P2701	R9900P24	2025-06-30	Release	Released for Technical Support.
R9900P24		2025-03-17	Release	Released for Technical Support.

Supported browsers

As a best practice, use the following browsers:

· IE 10 or higher

· Firefox 19 or higher

· Chrome 31 and later versions

· Safari 5 and later versions

Version compatibility matrix

CAUTION:

To avoid an upgrade failure, use the following table to verify the hardware and software compatibility before performing an upgrade.

Table 2 Version compatibility matrix

Product series	Product model
Model	L5030	L5060	L5080
Memory	16 GB	32 GB	64 GB
Flash	EMMC Flash: 8GB Nand Flash: None
Boot ROM version	Shipped with the device (You can see the version number with the display version command in any view.)
Software image file and MD5 checksum	SECPATH5080L-CMW710-R9900P33.ipe: 1ab99ec6b752bb2eeec2ae872b958ce5 L5080ADE-CMW710-BOOT-R9900P33.bin: a003ad7c9c2630865547f6b17ac7676c L5080ADE-CMW710-SYSTEM-R9900P33.bin: cfa347b19eed130f7ae884252b7806b4 L5080ADE-CMW710-SYSTEM-R9900P33.xsd.tar.bz2: 05c34e5d9d3da76ef62a8cc0a7c25abb
IMC version	iMC-ACLM 7.3 (E0710P06) iMC-DM 7.3 (E0710P06) iMC EIA 7.3 (TAM) (E0633H01) iMC-iCC 7.3 (E0710P06) iMC PLAT 7.3 (E0710P06) iMC SHM 7.3 (E0707L06) iMC SSM 7.3 (LBM) (E0505P03) iMC SSM 7.3 (SSM) (E0506H01) iMC-VLAN 7.3 (E0710P06)
iNode version	iNode PC 7.3 (E0644)
ADDC version	E7105P01
ADNET-FCAPS version	E0709
AOM version	E0706P01
Remarks	N/A

Example: To display the host software and BootWare version of L5080, perform the following:

<H3C>dis version

H3C Comware Software, Version 7.1.064, Feature 9900P1304

H3C SecPath L5030 uptime is 0 weeks, 0 days, 0 hours, 1 minute

Last reboot reason: Warm reboot

Boot image: sda0:/L5080ADE-CMW710-BOOT-F9900P1304.bin

Boot image version: 7.1.064, Feature 9900P1304

Compiled Aug 09 2023 14:00:00

System image: sda0:/L5080ADE-CMW710-SYSTEM-F9900P1304.bin

System image version: 7.1.064, Feature 9900P1304

Compiled Aug 09 2023 14:00:00

Feature image(s) list:

sda0:/L5080ADE-CMW710-SECESCAN-F9900P1304.bin, version: 7.1.064

Compiled Aug 09 2023 14:00:00

SLOT 1

Uptime is 0 weeks, 3 days, 4 hours, 47 minutes

CPU type: Multi-core CPU

DDR3 SDRAM Memory: 65520M bytes

SD0: 3728M bytes

NSQ1MPBHA PCB Version: Ver.B

NSQ1MPBBHB PCB Version: Ver.A

NSQ1MPHDBHA PCB Version: Ver.A

NSQ1MPGC4BHA PCB Version: Ver.A

NSQ1MPLEDBHA PCB Version: Ver.A

CPLD_A Version: 2.0

CPLD_B Version: 2.0

Release Version:H3C SecPath L5000-9900P1304

Basic BootWare Version:1.09

Extend BootWare Version:1.09

[SUBCARD 0] NSQ1MPBHA(Hardware)Ver.B, (Driver)1.0, (Cpld)2.0

[SUBCARD 1] NSQM1TG8A(Hardware)Ver.A, (Driver)1.0, (Cpld)1.0

[SUBCARD 6] NSQM1GT8A(Hardware)Ver.B, (Driver)1.0, (Cpld)1.0

Upgrade restrictions and guidelines

· After major version upgrades or downgrades, the Web menu paths might change. If you have created custom user roles using the role command and custom rules for those roles using the rule command for RBAC services in the previous version, you must update the rule commands based on the new Web menu paths after the version change. Otherwise, existing configurations that do not match the current menu paths will no longer take effect.

· F9900P19 and later versions do not support IRF. To upgrade to this version, you must change the network mode to RBM.

· To upgrade the software from a version earlier than F9900P19 to this version, you must disconnect the heartbeat link and disconnect the service interface to completely isolate the device before upgrade. After the upgrade, restore the heartbeat interface and then the service interface.

Hardware feature updates

N/A

Software feature and command updates

For more information about the software feature and command update history, see H3C SECPATH5080L-CMW710-R9900P33 Release Notes (Software Feature Changes).

MIB updates

Table 3 MIB updates

Version number	Item	MIB file	Module name	Remarks
R9900P33	New	/	/	N/A
R9900P33	Modified	/	/	N/A
R9900P30	New	/	/	N/A
R9900P30	Modified	/	/	N/A
R9900P2701	New	/	/	N/A
R9900P2701	Modified	/	/	N/A
R9900P24	New	/	/	N/A
R9900P24	Modified	/	/	N/A

Operation changes

N/A

Restrictions and cautions

Before performing an upgrade, see H3C SECPATH5080L-CMW710-R9900P33 Release Notes (Software Feature Changes) and related documentation to see the software feature changes and evaluate the influence on the service.

Restrictions

· You cannot configure the same feature module both at the CLI and in the Web interface.

· The number of contexts used must strictly follow the specifications.

Cautions

· As a best practice, do not perform operations such as restarting, starting, or stopping contexts when memory is insufficient.

· If multiple virtual servers use the same LB policy, the different real server groups corresponding to the load balancing actions of each virtual server must either all perform source address translation or all not perform source address translation.

· In an N+M cluster scenario, virtual servers of different traffic groups must use different SNAT address pools.

Licensing

About licensing

H3C offers licensing options for you to deploy features and expand resource capacity on an as needed basis. To use license-based features, purchase licenses from H3C and install the licenses.

Registering and installing licenses

H3C License Management Platform provides product licensing services for H3C customers. You can access this system to obtain an activation file or transfer licenses.

H3C License Management Platform is accessible at http://www.h3c.com/en/License/.

For more information about license registration, activation file installation, and license transfer, see H3C Security Products Licensing Configuration Demonstration Video, H3C Security Products Licensing Configuration Demonstration, H3C Security Products Licensing Configuration Examples, and H3C Security Products Licensing Guide.

H3C provides license-related FAQ. For more information, see H3C Security Products Licensing FAQ.

Open problems and workarounds

202504221214

· Symptom: When there is traffic on the VS, editing the IP or VRF of the VS will cause VS flag change, leading to VS packet loss.

· Condition: This symptom might occur if you edit the IP or VRF of the VS while traffic is present.

· Workaround: Do not edit the IP or VRF of the VS while traffic is present.

List of resolved problems

Resolved problems in R9900P33

202509110222

· Symptom: When 6000000 or more users initiate RADIUS requests, if you reset the sessions during the generation of persistent entries, and then reset the persistent entries after traffic stops, residual persistent entries might exist, leading to a memory leak.

· Condition: This symptom might occur if you clear the sessions and persistent entries while traffic is present.

Resolved problems in R9900P30

202508210656

· Symptom: The card reboots if you execute the undo loadbalance ssl performance-optimize cache-value command use the AES128-SHA cipher suite when SSL traffic is present.

· Condition: This symptom occurs if you execute the undo loadbalance ssl performance-optimize cache-value command use the AES128-SHA cipher suite when SSL traffic is present.

Resolved problems in R9900P2701

202506061709

· Symptom: The delay of a ping operation when the device is directly connected to a switch.

· Condition: This symptom might occur when the device is directly connected to a switch.

202503040268

· Symptom: The returned values are null when a MIB browser is used to read nodes of the virtual server name, server farm name, and real server name through SNMP.

· Condition: This symptom occurs if nodes of the virtual server name, server farm name, and real server name are read through SNMP

Resolved problems in R9900P24

202412240191

· Symptom: In an RBM+VRRP network, the states of contexts are active, but the displayed states are inactive.

· Condition: This symptom occurs if you reboot the contexts on the active and backup devices repeatedly.

Technical support

Email: [email protected]

Website: http://www.h3c.com/en

Appendix A Feature list

Hardware features

Table 4 Hardware features

Item	Specifications
Product model	L5030	L5060	L5080
Ports	1 × console port 2 × external USB host ports 4 × GE combo ports Interface modules: · 8-port GE interface module · 8-port SFP+ interface module	1 × console port 2× external USB host ports 4 × GE combo ports Interface modules: · 8-port SFP interface module · 8-port GE interface module · 8-port SFP+ interface module	1 × console port 2× external USB host ports 4 ×GE combo ports Interface modules: · 8-port SFP interface module · 8-port GE interface module · 8-port SFP+ interface module
Memory	16 GB DDR3	32 GB DDR3	64 GB DDR3
Flash	4 GB
Expansion slots	8 × interface module slots, supporting the following interface modules: · 8-port SFP+ interface module · 2-port QSFP+ interface module · 8-port GE interface module · 8-port SFP interface module · 4-port PFC interface module · 4-port SFP&4-port SFP+ interface module
Hard disk slots	2 × hard disk slots, supporting 2 SATA disks. Hot disk swapping is not supported.
Power modules	2 × 650 W AC/DC power modules. Mixed use of AC and DC power modules is not supported.
Dimensions (H × W × D)	88 × 440 × 660 mm (3.46 × 17.32 × 25.98 in)
Temperature	· Operating: ¡ Without disks: 0°C to 45°C (32°F to 113°F) ¡ With disks: 5°C to 40°C (41°F to 104°F) · Storage: –40°C to 70°C (–40°F to 158°F)
Humidity	· Operating: ¡ Without disks: 5% RH to 95% RH ¡ With disks: 10% RH to 80% RH · Storage: ¡ Without disks: 5% RH to 95% RH ¡ With disks: 5% RH to 90% RH

Software features

Table 5 Software features

Category	Features
Server load balancing	Scheduling algorithms	Round-robin Least connections Random Source IP address hash Destination IP address hash Source IP address and port hash
	Session persistence	Source IP address-based session persistence Destination IP address-based session persistence Source IP and source port-based session persistence Destination IP and destination port-based session persistence Source IP, source port, destination IP, destination port-based session persistence HTTP packet header-based session persistence HTTP cookie-based session persistence HTTP content-based session persistence HTTP URL-based session persistence SSL ID-based session persistence
	Health check	ICMP TCP HTTP FTP
	HTTP policy	Match cookie Match header Match URL Match content Insert header action Rewrite header action
Inbound link load balancing	Inbound link load balancing	DNS listener DNS query type Bandwidth busy protection Link health inspection Load sharing algorithms, including least connections, random, and round-robin.
Outbound link load balancing	Outbound link load balancing	Load sharing algorithms, including least connections, random, round-robin, address HASH, and bandwidth. Traffic classification based on source IP, ISP, and ACL. Dynamic proximity Link health inspection ALG Bandwidth busy protection
Management	Management mode	CLI (Telnet/SSH) Serial port SNMPv3, compatible with SNMP v2c and SNMP v1 IMC
Networking	Networking schemes	L4/L7 server load balancing Bypass mode

Appendix B Fixed vulnerabilities

Fixed vulnerabilities in R9900P30

N/A

Appendix C Upgrading software

CAUTION:

Do not power off or reboot the device during the upgrade process.

The software upgrade procedure is the same for all security devices. This chapter describes how to upgrade software from the CLI and Web interface. The default storage medium varies by device model. This chapter uses the flash memory as the default storage medium.

Software images

Software images types

The following software types are available:

· BootWare image—A .btw file that contains a basic segment and an extended segment. The basic segment is the minimum code that bootstraps the system. The extended segment enables hardware initialization and provides system management menus. You can use these menus to load software and the startup configuration file or manage files when the device cannot start up correctly.

· System software image—Includes the following image subcategories:

¡ Boot image—A .bin file that contains the Linux operating system kernel. It provides process management, memory management, file system management, and the emergency shell.

¡ System image—A .bin file that contains the Comware kernel and standard features, including device management, interface management, configuration management, and routing.

¡ Patch image—A .bin file that is released for fixing bugs without rebooting the device. A patch image does not add or remove features.

You can assign the following attributes to a system software image:

¡ Main—The image is the primary image. The system always attempts to load the main image at startup in preference to the backup image.

¡ Backup—The image is the backup image. It is used only if the primary image is corrupt or not available.

Software release forms

Software images are released in one of the following forms:

· Separate .bin files. You must verify compatibility between software images.

· As a whole in one .ipe package file. The images in an .ipe package file are compatible. The system decompresses the file automatically, loads the .bin images and sets them as startup software images.

Configuration files

You can save settings you made to a configuration file so they can survive a reboot.

The device supports .cfg configuration files. The default .cfg configuration file is named startup.cfg.

Upgrade methods

To upgrade system software, use one of the following methods:

· Upgrading system software from the CLI

· Upgrading system software from the Web interface

To upgrade the BootWare, use either of the following methods:

· Upgrading the BootWare from the CLI

· Upgrading the BootWare from an Ethernet interface through TFTP/FTP

You must reboot the device after a system software or BootWare upgrade. A device reboot interrupts services.

Before a software upgrade, read the release notes to identify the command changes. Some commands in the configuration file might not be supported after a software upgrade.

Preparing for the upgrade

The device can function as the TFTP client, FTP client, or FTP server. In the following examples that use TFTP or FTP, the device functions as the TFTP or FTP client.

To use a PC as the TFTP or FTP server, prepare the TFTP or FTP server software by yourself. The device is not shipped with the software.

Before you upgrade system software, complete the following tasks:

· Run a TFTP or FTP server on the file server. (Skip this task if you upgrade software from the Web interface.)

· Assign an IP address to the file server. Make sure the management Ethernet port on the device and the file server can reach each other.

By default, the IP address of the management Ethernet port GigabitEthernet 1/0/0 is 192.168.0.1/24 and the management Ethernet port belongs to the Management security zone. The Management security zone and the Local security zone can communicate with each other.

You can also change the IP address of the management Ethernet port from its default and add it to a security zone other than Management. Then, you configure a zone pair to make sure the security zone and the Local security zone can communicate with each other. For more information about security zones and zone pairs, see the security zone configuration in the fundamentals configuration guide.

· Transfer the software upgrade file to the file server and set the working directory on the TFTP or FTP server.

· Log in to the CLI of the device through the console port. (Skip this task if you upgrade software from the Web interface.)

· Make sure the upgrade has minimal impact on the network services. During the upgrade, the device cannot provide any services.

Upgrading system software

Upgrading system software from the CLI

You can use TFTP or FTP on the device to access the TFTP or FTP server to back up or download software files.

Using TFTP to upgrade system software

2. Back up the running system software image and configuration file:

a. Display current software images and startup software images.

<Sysname> display boot-loader

Software images on slot 1:

Current software images:

cfa0:/main-cmw710-boot-R8513.bin

cfa0:/main-cmw710-system-R8513.bin

Main startup software images:

cfa0:/main-cmw710-boot-R8513.bin

cfa0:/main-cmw710-system-R8513.bin

Backup startup software images:

None

b. Back up the current software images.

<Sysname> copy main-cmw710-boot-R8513.bin boot_backup.bin

<Sysname> copy main-cmw710-system-R8513.bin system_backup.bin

c. Specify boot_backup.bin and system_backup.bin as the backup startup image files.

<Sysname> boot-loader file boot cfa0:/boot_backup.bin system cfa0:/system_backup.bin backup

d. Execute the save command in any view to save the running configuration.

<Sysname> save

The current configuration will be written to the device. Are you sure? [Y/N]:y

Please input the file name(*.cfg)[flash:/startup.cfg]

(To leave the existing filename unchanged, press the enter key):

flash:/startup.cfg exists, overwrite? [Y/N]:y

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

e. Execute the dir command in user view to identify the system software image and configuration file names and verify that the flash memory has sufficient space for the new system software image.

<Sysname> dir

Directory of cfa0:

0 drw- - Jul 06 2017 15:04:22 context

1 drw- - Jul 05 2017 10:01:40 diagfile

2 drw- - Jul 05 2017 10:36:20 dpi

3 -rw- 735 Jul 05 2017 10:01:48 hostkey

4 -rw- 735 Jul 05 2017 09:24:34 hostkey_v3

5 -rw- 805 Nov 27 2017 19:50:26 ifindex.dat

6 drw- - Nov 27 2017 19:40:15 license

7 drw- - Jul 06 2017 10:27:44 logfile

8 drw- - Nov 27 2017 19:40:32 pki

9 -rw- 1676 Jul 05 2017 09:40:20 private-data.txt

10 drw- - Jul 05 2017 09:24:26 seclog

11 -rw- 591 Nov 27 2017 19:40:32 serverkey

12 -rw- 3928 Nov 27 2017 19:50:27 startup.cfg

13 -rw- 77641 Nov 27 2017 19:50:27 startup.mdb

14 drw- - Nov 27 2017 19:40:27 versionInfo

252164 KB total (146614 KB free)

f. Execute the tftp put command in user view to upload the startup.cfg file to the TFTP server.

<Sysname> tftp 192.168.0.2 put startup.cfg vpn-instance management

Press CTRL+C to abort.

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

100 3950 0 0 100 3950 0 204k --:--:-- --:--:-- --:--:-- 642k

3. Upgrade the system software:

a. Execute the tftp get command in user view to download the system software image file to the flash memory on the device.

<Sysname> tftp 192.168.100.9 get main.ipe

Press CTRL+C to abort.

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

100 102M 100 102M 0 0 461k 0 0:03:48 0:03:48 --:--:-- 554k

Writing file...Done.

b. Execute the boot-loader file command in user view to load the main.ipe file and specify it as the main image file at the next reboot.

<Sysname> boot-loader file cfa0:/main.ipe all main

Verifying the file cfa0:/main.ipe on slot 1.........Done.

H3C SecPath T5010 images in IPE:

main-cmw710-boot-F9900P1304.bin

main-cmw710-system-F9900P1304.bin

This command will set the main startup software images. Please do not reboot any

MPU during the upgrade. Continue? [Y/N]:y

Add images to slot 1.

File cfa0:/main-cmw710-boot-F9900P1304.bin already exists on slot 1.

File cfa0:/main-cmw710-system-F9900P1304.bin already exists on slot 1.

Overwrite the existing files? [Y/N]:y

Decompressing file main-cmw710-boot-F9900P1304.bin to cfa0:/main-cmw710-bo

ot-F9900P1304.bin..........Done.

Decompressing file main-cmw710-system-F9900P1304.bin to cfa0:/main-cmw710-

system-F9900P1304.bin.............................................................

................................................................................

...............................Done.

Verifying the file cfa0:/main-cmw710-boot-F9900P1304.bin on slot 1...Done.

Verifying the file cfa0:/main-cmw710-system-F9900P1304.bin on slot 1.........D

one.

The images that have passed all examinations will be used as the main startup so

ftware images at the next reboot on slot 1.

Decompression completed.

Do you want to delete cfa0:/main.ipe now? [Y/N]:N

c. Execute the display boot-loader command in user view to verify that the file has been loaded.

<Sysname> display boot-loader

Software images on slot 1:

Current software images:

cfa0:/main-cmw710-boot-F9900P1304.bin

cfa0:/main-cmw710-system-F9900P1304.bin

Main startup software images:

cfa0:/main-cmw710-boot-F9900P1304.bin

cfa0:/main-cmw710-system-F9900P1304.bin

Backup startup software images:

cfa0:/main-cmw710-boot-F9900P1304.bin

cfa0:/main-cmw710-system-F9900P1304.bin

d. Execute the reboot command in user view to reboot the device.

<Sysname> reboot

Start to check configuration with next startup configuration file, please wait.

........DONE!

This command will reboot the device. Continue? [Y/N]:y

System is starting...

…omitted…

e. After the reboot is complete, execute the display version command to verify that the system software image is correct.

<Sysname> display version

H3C Comware Software, Version 7.1.064, Release 9900P1304

H3C SecPath T5010 uptime is 0 weeks, 0 days, 0 hours, 21 minutes

Last reboot reason: Warm reboot

Boot image: cfa0:/main-cmw710-boot-F9900P1304.bin

Boot image version: 7.1.064, Release 9900P1304

Compiled Nov 10 2017 16:00:00

System image: cfa0:/main-cmw710-system-F9900P1304.bin

System image version: 7.1.064, Release 9900P1304

Compiled Nov 10 2017 16:00:00

SLOT 1

CPU type: Multi-core CPU

DDR3 SDRAM Memory 16382M bytes

CF0 Card 247M bytes

Board PCB Version:Ver.A

CPLD_A Version: 1.0

CPLD_B Version: 2.0

Release Version:SecPath T5010-9900P1304

Basic BootWare Version: 2.05

Extend BootWare Version: 2.05

Using FTP to upgrade system software

4. Back up the running system software image and configuration file:

a. Display current software images and startup software images.

<Sysname> display boot-loader

Software images on slot 1:

Current software images:

cfa0:/main-cmw710-boot-R8513.bin

cfa0:/main-cmw710-system-R8513.bin

Main startup software images:

cfa0:/main-cmw710-boot-R8513.bin

cfa0:/main-cmw710-system-R8513.bin

Backup startup software images:

None

b. Back up the current software images.

<Sysname> copy main-cmw710-boot-R8513.bin boot_backup.bin

<Sysname> copy main-cmw710-system-R8513.bin system_backup.bin

c. Specify boot_backup.bin and system_backup.bin as the backup startup image files.

<Sysname> boot-loader file boot cfa0:/boot_backup.bin system cfa0:/system_backup.bin backup

d. Execute the save command in any view to save the running configuration.

<Sysname> save

The current configuration will be written to the device. Are you sure? [Y/N]:y

Please input the file name(*.cfg)[flash:/startup.cfg]

(To leave the existing filename unchanged, press the enter key):

flash:/startup.cfg exists, overwrite? [Y/N]:y

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

e. Execute the dir command in user view to identify the system software image and configuration file names and verify that the flash memory has sufficient space for the new system software image.

<Sysname> dir

Directory of cfa0:

0 drw- - Jul 06 2017 15:04:22 context

1 drw- - Jul 05 2017 10:01:40 diagfile

2 drw- - Jul 05 2017 10:36:20 dpi

3 -rw- 735 Jul 05 2017 10:01:48 hostkey

4 -rw- 735 Jul 05 2017 09:24:34 hostkey_v3

5 -rw- 805 Nov 27 2017 19:50:26 ifindex.dat

6 drw- - Nov 27 2017 19:40:15 license

7 drw- - Jul 06 2017 10:27:44 logfile

8 drw- - Nov 27 2017 19:40:32 pki

9 -rw- 1676 Jul 05 2017 09:40:20 private-data.txt

10 drw- - Jul 05 2017 09:24:26 seclog

11 -rw- 591 Nov 27 2017 19:40:32 serverkey

12 -rw- 3928 Nov 27 2017 19:50:27 startup.cfg

13 -rw- 77641 Nov 27 2017 19:50:27 startup.mdb

14 drw- - Nov 27 2017 19:40:27 versionInfo

252164 KB total (146614 KB free)

f. Execute the ftp command in user view to access the FTP server.

<Sysname> ftp 192.168.0.2

Press CTRL+C to abort.

Connected to 192.168.0.2 (192.168.0.2).

220 3Com 3CDaemon FTP Server Version 2.0

User (192.168.0.2:(none)): user123

331 User name ok, need password

Password:

230 User logged in

Remote system type is UNIX.

Using binary mode to transfer files.

ftp>

g. Execute the put command in FTP client view to upload the startup.cfg file to the FTP server.

ftp> put startup.cfg

227 Entering passive mode (192,168,0,2,26,3)

125 Using existing data connection

226 Closing data connection; File transfer successful.

3950 bytes sent in 0.001 seconds (4.13 Mbytes/s)

ftp>

5. Upgrade the system software:

a. Execute the get command in FTP client view to download the system software image file to the flash memory on the device.

ftp> get main.ipe

227 Entering passive mode (192,168,0,2,8,252)

125 Using existing data connection

226 Closing data connection; File transfer successful.

107934720 bytes received in 187.994 seconds (560.68 Kbytes/s)

ftp>

b. Execute the quit command in FTP client view to return to user view.

ftp> quit

221 Service closing control connection

c. Execute the boot-loader file command in user view to load the main.ipe file and specify it as the main image file at the next reboot.

<Sysname> boot-loader file cfa0:/main.ipe all main

Verifying the file cfa0:/main.ipe on slot 1.........Done.

H3C SecPath T5010 images in IPE:

main-cmw710-boot-F9900P1304.bin

main-cmw710-system-F9900P1304.bin

This command will set the main startup software images. Please do not reboot any

MPU during the upgrade. Continue? [Y/N]:y

Add images to slot 1.

File cfa0:/main-cmw710-boot-F9900P1304.bin already exists on slot 1.

File cfa0:/main-cmw710-system-F9900P1304.bin already exists on slot 1.

Overwrite the existing files? [Y/N]:y

Decompressing file main-cmw710-boot-F9900P1304.bin to cfa0:/main-cmw710-bo

ot-F9900P1304.bin..........Done.

Decompressing file main-cmw710-system-F9900P1304.bin to cfa0:/main-cmw710-

system-F9900P1304.bin.............................................................

................................................................................

...............................Done.

Verifying the file cfa0:/main-cmw710-boot-F9900P1304.bin on slot 1...Done.

Verifying the file cfa0:/main-cmw710-system-F9900P1304.bin on slot 1.........D

one.

The images that have passed all examinations will be used as the main startup so

ftware images at the next reboot on slot 1.

Decompression completed.

Do you want to delete cfa0:/main.ipe now? [Y/N]:N

d. Execute the display boot-loader command in user view to verify that the file has been loaded.

<Sysname> display boot-loader

Software images on slot 2:

Current software images:

flash:/main-cmw710-boot-F9900P1304.bin

flash:/main-cmw710-system-F9900P1304.bin

Main startup software images:

flash:/main-cmw710-boot-F9900P1304.bin

flash:/main-cmw710-system-F9900P1304.bin

Backup startup software images:

cfa0:/main-cmw710-boot-F9900P1304.bin

cfa0:/main-cmw710-system-F9900P1304.bin

e. Execute the reboot command in user view to reboot the device.

<Sysname> reboot

Start to check configuration with next startup configuration file, please wait.

........DONE!

This command will reboot the device. Continue? [Y/N]:y

System is starting...

…omitted…

f. After the reboot is complete, execute the display version command to verify that the system software image is correct.

<Sysname> display version

H3C Comware Software, Version 7.1.064, Release 9900P1304

H3C SecPath T5010 uptime is 0 weeks, 0 days, 0 hours, 21 minutes

Last reboot reason: Warm reboot

Boot image: cfa0:/main-cmw710-boot-F9900P1304.bin

Boot image version: 7.1.064, Release 9900P1304

Compiled Nov 10 2017 16:00:00

System image: cfa0:/main-cmw710-system-F9900P1304.bin

System image version: 7.1.064, Release 9900P1304

Compiled Nov 10 2017 16:00:00

SLOT 1

CPU type: Multi-core CPU

DDR3 SDRAM Memory 16382M bytes

CF0 Card 247M bytes

Board PCB Version:Ver.A

CPLD_A Version: 1.0

CPLD_B Version: 2.0

Release Version:SecPath T5010-9900P1304

Basic BootWare Version: 2.05

Extend BootWare Version: 2.05

Upgrading system software from the Web interface

CAUTION:

· You can use the default account settings or create a new account to log in to the Web interface for the first time. This section uses the default account settings. For security purposes, if you use the default account settings, modify the default password or create a new account and delete the default account after the first login.

· Do not perform any operation on the Web interface while the system is upgrading software.

Table 6 describes the default settings for you to log in to the Web interface.

Table 6 Default login information

Login information	Default setting
Username	admin
Password	admin
IP address of GigabitEthernet 1/0/0	192.168.0.1/24

NOTE:

The default management Ethernet port varies by device model. In this example, the default management Ethernet port is GigabitEthernet 1/0/0.

To upgrade the system software from the Web interface:

6. Use an Ethernet cable to connect the PC to an Ethernet port on the device. As a best practice, connect the PC to the management Ethernet port on the device.

7. Assign an IP address on the same subnet as the management port GigabitEthernet 1/0/0 to the PC.

In this example, assign 192.168.0.2 to the PC.

8. Launch the Web browser, and enter 192.168.0.1 in the address bar.

The Web login page appears.

9. Type the default username and password, and click Login.

10. Select System > Upgrade Center > Software Upgrade from the navigation tree.

Figure 1 Software upgrade page

11. Click Upgrade immediately on the Software Upgrade page.

12. Select the startup file to be used, and click OK.

Figure 2 Upgrade Immediately page

Upgrading the BootWare

You can upgrade the BootWare from the CLI or BootWare menus.

Upgrading the BootWare from the CLI

Whether a .btw file is compressed together with an .ipe file depends on the device model and software release. Please check it with H3C technical support. This section describes only how to upgrade the BootWare from the CLI.

To upgrade the BootWare from the CLI:

13. Use FTP or TFTP to download or upload the new BootWare image file to the root directory of the storage medium on the device.

14. Execute the bootrom update command to upgrade the BootWare.

<System> bootrom update cfa0:/main.btw slot 2

This command will update bootrom file, Continue? [Y/N]:y

Now updating bootrom, please wait...

Updating basic bootrom!

Update basic bootrom success!

Updating extended bootrom!

Update extended bootrom success!

Update bootrom success!

15. Execute the reboot command to reboot the device.

Upgrading the BootWare from an Ethernet interface through TFTP/FTP

NOTE:

· To upgrade the BootWare from an Ethernet interface through TFTP/FTP, make sure the password recovery capability is enabled.

· To enable the password recovery capability, execute the password-recovery enable command. To disable the password recovery capability, execute the undo password-recovery enable command.

16. Access the BootWare menu.

When the device starts up or reboots, the configuration terminal displays the following information:

System is starting...

Press Ctrl+D to access BASIC-BOOTWARE MENU...

Press Ctrl+T to start heavy memory test

Booting Normal Extended BootWare

The Extended BootWare is self-decompressing.......Done.

*****************************************************************

* *

* H3C SecPath BootWare, Version 2.05 *

* *

*****************************************************************

Compiled Date : Feb 25 2016

CPU Type : XXX

CPU Clock Speed : 1400MHz

Memory Type : DDR3 SDRAM

Memory Size : 16384MB

Memory Speed : 1333MHz

BootWare Size : 768KB

Flash Size : 8MB

cfa0 Size : 247MB

CPLD_A Version : 1.0

CPLD_B Version : 2.0

PCB Version : Ver.A

BootWare Validating...

Press Ctrl+B to access EXTENDED-BOOTWARE MENU...

Press Ctrl + B immediately when the Press Ctrl+B to access EXTENDED-BOOTWARE MENU... message is displayed.

You can identify whether the password recovery capability is enabled in the output information.

Password recovery capability is disabled.

Note: The current operating device is cfa0

Enter < Storage Device Operation > to select device.

===========================<EXTEND-BOOTWARE MENU>===========================

|<1> Boot System |

|<2> Enter Serial SubMenu |

|<3> Enter Ethernet SubMenu |

|<4> File Control |

|<5> Restore to Factory Default Configuration |

|<6> Skip Current System Configuration |

|<7> BootWare Operation Menu |

|<8> Skip Authentication for Console Login |

|<9> Storage Device Operation |

|<0> Reboot |

============================================================================

Ctrl+Z: Access EXTEND-ASSISTANT MENU

Ctrl+F: Format File System

Enter your choice(0-9):

The menu description is as follows:

Table 7 BootWare main menu

Option	Description
<1> Boot System	Access the boot file.
<2> Enter Serial SubMenu	Access the serial port submenu.
<3> Enter Ethernet SubMenu	Access the Ethernet interface submenu.
<4> File Control	Access the file control submenu.
<5> Restore to Factory Default Configuration	Restore factory defaults. CAUTION: · For this operation to take effect, make sure the password recovery capability is disabled. · After you restore factory defaults, the system will delete the current configuration file and start with initial configuration. Use this feature with caution.
<6> Skip Current System Configuration	Start the system with the current configuration skipped. This is a one-off operation and is typically used when a user forgets the password. NOTE: For this operation to take effect, make sure the password recovery capability is enabled.
<7> BootWare Operation Menu	Access the BootWare operations submenu.
<8> Skip Authentication for Console Login	Start the system without console port authentication. This is a one-off operation and is typically used when a user forgets the console password. NOTE: For this operation to take effect, make sure the password recovery capability is enabled.
<9> Storage Device Operation	Access the storage control menu.
<0> Reboot	Reboot the device.

17. Press 7 in the BootWare menu to access the BootWare operations menu.

=========================<BootWare Operation Menu>==========================

|Note:the operating device is flash |

|<1> Backup Full BootWare |

|<2> Restore Full BootWare |

|<3> Update BootWare By Serial |

|<4> Update BootWare By Ethernet |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-4):

Table 8 BootWare operations menu

Option	Description
<1> Backup Full BootWare	Back up complete BootWare.
<2> Restore Full BootWare	Restore complete BootWare.
<3> Update BootWare By Serial	Upgrade BootWare through the serial port.
<4> Update BootWare By Ethernet	Upgrade BootWare through the Ethernet port.
<0> Exit To Main Menu	Return to the BootWare main menu.

18. Press 4 to access the BootWare operations Ethernet interface submenu.

===================<BOOTWARE OPERATION ETHERNET SUB-MENU>===================

|<1> Update Full BootWare |

|<2> Update Extend BootWare |

|<3> Update Basic BootWare |

|<4> Modify Ethernet Parameter |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-4):

Table 9 BootWare operations Ethernet submenu

Option	Description
<1> Update Full BootWare	Upgrade complete BootWare.
<2> Update Extend BootWare	Upgrade extended BootWare.
<3> Update Basic BootWare	Upgrade basic BootWare.
<4> Modify Ethernet Parameter	Edit Ethernet interface parameters.
<0> Exit To Main Menu	Return to the BootWare main menu.

19. Press 4 to enter the Ethernet interface configuration menu.

==========================<ETHERNET PARAMETER SET>==========================

|Note: '.' = Clear field. |

| '-' = Go to previous field. |

| Ctrl+D = Quit. |

============================================================================

Protocol (FTP or TFTP) :TFTP

Load File Name :main.btw

Target File Name :main.btw

Server IP Address :192.168.0.2

Local IP Address :192.168.0.1

Gateway IP Address :0.0.0.0

Table 10 Ethernet parameters

Field	Description
'.' = Clear field	Press the dot (.) to clear the setting for a field.
'-' = Go to previous field	Press the hyphen (-) to return to the previous field.
Ctrl+D = Quit	Press Ctrl and D to exit the parameter configuration interface.
Protocol (FTP or TFTP)	Transfer protocol, which can be FTP or TFTP.
Load File Name	Name of the file to be downloaded.
Target File Name	Name of the software image file. By default, the name is consistent with the downloaded file name.
Server IP Address	IP address of the TFTP or FTP server.
Local IP Address	Local IP address, which is the IP address of the Ethernet interface used for upgrade.
Gateway IP Address	Gateway IP address. Configure the gateway IP address if the device and the FTP server do not belong to the same subnet.

For example, to upgrade complete BootWare, press 1 in the BootWare operations Ethernet submenu.

===================<BOOTWARE OPERATION ETHERNET SUB-MENU>===================

|<1> Update Full BootWare |

|<2> Update Extend BootWare |

|<3> Update Basic BootWare |

|<4> Modify Ethernet Parameter |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-4): 1

Loading............Done!

418156 bytes downloaded!

Updating Basic BootWare? [Y/N]Y

Updating Basic BootWare...........Done!

Updating Extend BootWare? [Y/N]Y

Updating Extend BootWare...........Done!

===================<BOOTWARE OPERATION ETHERNET SUB-MENU>===================

|<1> Update Full BootWare |

|<2> Update Extend BootWare |

|<3> Update Basic BootWare |

|<4> Modify Ethernet Parameter |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-4):

After the upgrade completes, return to the BootWare main menu, and then press 0 to reboot the system.

Performing file management from the BootWare menu

Press 4 in the BootWare main menu to access the file control submenu. From this submenu, you can view all files in the flash memory, configure the startup file type, and delete files.

===============================<File CONTROL>===============================

|Note:the operating device is flash |

|<1> Display All File(s) |

|<2> Set Image File type |

|<3> Set Bin File type |

|<4> Set Configuration File type |

|<5> Delete File |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-5):

Table 11 File control submenu

Option	Description
<1> Display All File(s)	Displaying all files
<2> Set Image File type	Configure the .ipe file type
<3> Set Bin File type	Configure the .bin file type NOTE: The .bin file is decompressed from the .ipe file.
<4> Set Configuration File type	Configure the configuration file type
<5> Delete File	Delete files
<0> Exit To Main Menu	Return to the BootWare main menu

Displaying all files

Press 1 in the file control submenu to display all files

Display all file(s) in flash:

'M' = MAIN 'B' = BACKUP 'N/A' = NOT ASSIGNED

============================================================================

|NO. Size(B) Time Type Name |

|1 5069824 Nov/27/2017 20:17:48 M cfa0:/main-cmw710-boot-r8514 |

|p10.bin |

|2 102857728 Nov/27/2017 20:18:00 M cfa0:/main-cmw710-system-r85 |

|14p10.bin |

|3 16 Nov/27/2017 19:40:26 N/A cfa0:/versioninfo/versionctl.dat|

|4 536 Nov/27/2017 19:40:26 N/A cfa0:/versioninfo/version0.dat |

|5 965 Nov/27/2017 19:40:16 N/A cfa0:/license/210235a1rr00000000|

|01.did |

|6 591 Nov/27/2017 19:40:32 N/A cfa0:/serverkey |

|7 805 Nov/28/2017 08:20:28 N/A cfa0:/ifindex.dat |

|8 3945 Nov/28/2017 08:20:28 M cfa0:/startup.cfg |

|9 77671 Nov/28/2017 08:20:28 N/A cfa0:/startup.mdb |

|10 107934720 Nov/27/2017 20:29:08 N/A cfa0:/main.ipe |

|11 8238 Nov/30/2017 16:45:40 N/A cfa0:/logfile/logfile.log |

|12 1566 Nov/27/2017 19:40:32 N/A cfa0:/pki/https-server.p12 |

============================================================================

===============================<File CONTROL>===============================

|Note:the operating device is flash |

|<1> Display All File(s) |

|<2> Set Image File type |

|<3> Set Bin File type |

|<4> Set Configuration File type |

|<5> Delete File |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-5):

Configuring the .ipe startup file type

20. Press 2 in the file control submenu to configure the startup file type:

'M' = MAIN 'B' = BACKUP 'S' = SECURE 'N/A' = NOT ASSIGNED

============================================================================

|NO. Size(B) Time Type Name |

|1 107934720 Nov/27/2017 20:29:08 N/A cfa0:/main.ipe |

|0 Exit |

============================================================================

21. Enter the number of the file to be edited, and then press Enter. Then, you can edit the file type.

Modify the file attribute:

============================================================================

|<1> +Main |

|<2> +Backup |

|<0> Exit |

============================================================================

Enter your choice(0-2):

22. Enter the number of the target file type. For example, to set the file type to main, enter 1.

Enter your choice(0-2):1

This operation may take several minutes. Please wait....

The file is exist,will you overwrite it? [Y/N]Y

Image file main-cmw710-boot-F9900P1304.bin is self-decompressing...

Saving file cfa0:/main-cmw710-boot-F9900P1304.bin .......... ....Done.

Image file main-cmw710-system-F9900P1304.bin is self-decompressing...

Saving file cfa0:/main-cmw710-system-F9900P1304.bin .........................

...............................................Done.

Set the file attribute success!

Configuring the .bin startup file type

Press 3 in the file control submenu to configure the startup file type:

'M' = MAIN 'B' = BACKUP 'N/A' = NOT ASSIGNED

============================================================================

|NO. Size(B) Time Type Name |

|1 5069824 Nov/30/2017 16:53:56 M cfa0:/main-cmw710-boot-r8514 |

|p10.bin |

|2 102857728 Nov/30/2017 16:54:14 M cfa0:/main-cmw710-system-r85 |

|14p10.bin |

|0 Exit |

============================================================================

Note:Select .bin files. One but only one boot image and system image must

be included.

Enter file No.(Allows multiple selection):1

Enter another file No.(0-Finish choice):2

Enter another file No.(0-Finish choice):0 //0 indicates stopping file selection

You have selected:

cfa0:/main-cmw710-boot-F9900P1304.bin

cfa0:/main-cmw710-system-F9900P1304.bin

Modify the file attribute:

============================================================================

|<1>+Main |

|<2>+Backup |

|<0> Exit |

============================================================================

Enter your choice(0-2):1

This operation may take several minutes. Please wait....

Set the file attribute success!

Deleting files

23. Press 5 in the file control submenu to delete file:

Deleting the file in flash:

'M' = MAIN 'B' = BACKUP 'N/A' = NOT ASSIGNED

============================================================================

|NO. Size(B) Time Type Name |

|1 5069824 Nov/30/2017 16:53:56 M cfa0:/main-cmw710-boot-r8514 |

|p10.bin |

|2 102857728 Nov/30/2017 16:54:14 M cfa0:/main-cmw710-system-r85 |

|14p10.bin |

|3 16 Nov/27/2017 19:40:26 N/A cfa0:/versioninfo/versionctl.dat|

|4 536 Nov/27/2017 19:40:26 N/A cfa0:/versioninfo/version0.dat |

|5 965 Nov/27/2017 19:40:16 N/A cfa0:/license/210235a1rr00000000|

|01.did |

|6 591 Nov/27/2017 19:40:32 N/A cfa0:/serverkey |

|7 805 Nov/28/2017 08:20:28 N/A cfa0:/ifindex.dat |

|8 3945 Nov/28/2017 08:20:28 M cfa0:/startup.cfg |

|9 77671 Nov/28/2017 08:20:28 N/A cfa0:/startup.mdb |

|10 107934720 Nov/27/2017 20:29:08 N/A cfa0:/main.ipe |

|11 8238 Nov/30/2017 16:45:40 N/A cfa0:/logfile/logfile.log |

|12 1566 Nov/27/2017 19:40:32 N/A cfa0:/pki/https-server.p12 |

|0 Exit |

============================================================================

Enter file No.:

24. Enter the number of the file to be deleted, and then press Enter. The system displays the following information if the file is deleted successfully:

The file you selected is flash:/NSQ1MPBLA_V2.vme,Delete it? [Y/N]Y

Deleting..............Done!

Handling software upgrade failures

If a software upgrade fails, the system runs the old software version. To handle a software failure:

1. Check the physical ports for a loose or incorrect connection, and verify that the LEDs are reflecting the correct port status.

2. If you are using the console port for file transfer, check the HyperTerminal settings (including the baud rate and data bits) for any wrong setting.

3. Check the file transfer settings:

¡ If Xmodem is used, make sure the HyperTerminal and the console port are consistent in baud rate.

¡ If TFTP is used, you must enter the same TFTP server IP address, file name, and working directory as set on the TFTP server.

¡ If FTP is used, you must enter the same FTP server IP address, file name, working directory, and FTP username and password as set on the FTP server.

4. Check the FTP or TFTP server for incorrect settings.

5. Check that the flash memory has sufficient space for the upgrade file.

6. If the message "Something is wrong with the file" appears, check the file for file corruption.

H3C SecPath L5080 L5060 L5030 Series

Software feature and command updates

MIB updates

202509110222

202508210656

202506061709

202503040268

202412240191

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us