Login
| Title | Size | Downloads |
|---|---|---|
| H3C_SECPATH9000AD-BLADEADEM9000AD-CMW710-R9900P33_Release_Notes.pdf | 564.61 KB | |
| SECPATH9000AD-CMW710-R9900P33_IPE.zip | 217.91 MB | |
| SECPATH9000AD-CMW710-R9900P33_BIN.zip | 217.90 MB | |
| H3C_SECPATH9000AD-BLADEADEM9000AD-CMW710-R9900P33_Release_Notes_(Software_Feature_Changes).pdf | 211.28 KB | |
| BLADEADEM9000AD-CMW710-R9900P33_IPE.zip | 261.57 MB | |
| BLADEADEM9000AD-CMW710-R9900P33_BIN.zip | 261.57 MB |
H3C SECPATH9000AD-BLADEADEM9000AD-CMW710-R9900P33 Release Notes
Contents
Version compatibility matrix· 1
Upgrade restrictions and guidelines· 5
Software feature and command updates· 5
Registering and installing licenses· 6
Open problems and workarounds· 7
Resolved problems in R9900P33· 7
Resolved problems in R9900P30· 7
Resolved problems in R9900P29· 7
Resolved problems in R9900P2701· 7
Resolved problems in R9900P21· 8
Appendix B Fixed vulnerabilities· 13
Appendix C Upgrading software· 14
Upgrading system software from the CLI 15
Upgrading system software from the Web interface· 23
Upgrading the BootWare from the CLI 25
Upgrading the BootWare from an Ethernet interface through TFTP/FTP· 26
Performing file management from the BootWare menu· 30
Handling software upgrade failures· 34
List of tables
Table 2 Version compatibility matrix. 2
Table 6 Default login information. 23
Table 11 File control submenu. 30
This document introduces the features, usage restrictions, issues, and workarounds of version R9900P33. Before loading R9900P33, back up the configuration file and perform internal verification to avoid potential risks as a best practice.
Use this document in conjunction with H3C SECPATH9000AD-BLADEADEM9000AD-CMW710-R9900P33 Release Notes (Software Feature Changes) and the documents listed in "Related documentation."
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.
Version number | Last version | Release date | Version type | Remarks |
R9900P33 | R9900P30 | 2025-12-22 | Release | Annual version |
R9900P30 | R9900P29 | 2025-09-23 | Release | Annual version |
R9900P29 | R9900P2701 | 2025-08-18 | Release | Released for Technical Support. |
R9900P2701 | R9900P21 | 2025-06-30 | Release | Released for Technical Support. |
R9900P21 | N/A | 2024-12-30 | 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 model | ||
Model | M9000-AD6 | L5000-AD920 |
Memory | MPU: 8 GB Service module: 32 GB per CPU | |
Flash | MPU: 4 GB Service module: 8 GB per CPU | |
Boot ROM version | Shipped with the device. (You can see the version number with the display version command in any view. See Note ②) | |
Software image file and MD5 checksum | MPU: SECPATH9000AD-CMW710-R9900P33.ipe: e35fc9b6e1a82e466dab61b3c4cc1887 M9000AD-CMW710-BOOT-R9900P33.bin: 03a9bf6e9c3aa06481accf40b559da7a M9000AD-CMW710-SYSTEM-R9900P33.bin: d479452cdfeeec9b473f86df880ff162 M9000AD-CMW710-SYSTEM-R9900P33.xsd.tar.bz2: 573597ad8163fc0a7f20d5a1a959716e Service module: BLADEADEM9000AD-CMW710-R9900P33.ipe: 91944c07514607b3cf2e270745240d15 BLADEADEM9000AD-CMW710-BOOT-R9900P33.bin: b9e23e2ec0d276f835979f444300369d BLADEADEM9000AD-CMW710-SYSTEM-R9900P33.bin: 7f1d199e87d26947eb9881fd4549c933 BLADEADEM9000AD-CMW710-SYSTEM-R9900P33.xsd.tar.bz2: 2bbc3482adcb474f6aed661eaedef0d4 | |
IMC version | iMC-ACLM 7.3 (E0705P12) iMC-DM 7.3 (E0705P12) iMC EIA 7.3 (TAM) (E0611P13) iMC-iCC 7.3 (E0705P12) iMC PLAT 7.3 (E0705P12) iMC SHM 7.3 (E0707L06) iMC SSM 7.3 (LBM) (E0505P03) iMC SSM 7.3 (SSM) (E0506H01) iMC-VLAN 7.3 (E0705P12) | |
iNode version | iNode PC 7.3 (E0585) | |
ADNET-FCAPS version | E0709 | |
AOM version | E0706P01 | |
Remarks | N/A | |
Example: To display the host software and BootWare version of M9000-AD6, perform the following:
[H3C]display version ---- Note②
H3C Comware Software, Version 7.1.064, Release 9900P33
Copyright (c) 2004-2025 New H3C Technologies Co., Ltd. All rights reserved.
H3C SecPath L5000-AD920 uptime is 3 weeks, 0 days, 23 hours, 36 minutes
Last reboot reason : User reboot
Boot image: flash:/M9000AD-CMW710-BOOT-R9900P33.bin
Boot image version: 7.1.064, Release 9900P33
Compiled Aug 14 2025 15:00:00
System image: flash:/M9000AD-CMW710-SYSTEM-R9900P33.bin
System image version: 7.1.064, Release 9900P33
Compiled Aug 14 2025 15:00:00
Feature image(s) list:
flash:/M9000AD-CMW710-DEVKIT-R9900P33.bin, version: 7.1.064
Compiled Aug 14 2025 15:00:00
MPU(M) 0:
Uptime is 3 weeks,0 days,23 hours,36 minutes
H3C SecPath L5000-AD920 MPU(M) with 1 ARM Processor
BOARD TYPE: NSQM6SUP04A0
DRAM: 8192M bytes
FLASH: 4096M bytes
PCB 1 Version: VER.A
PCB 2 Version: VER.A
Bootrom Version: 109
CPLD 1 Version: 005
CPLD 2 Version: 002
Release Version: H3C SecPath L5000-AD920-9900P33
Patch Version: None
Reboot Cause: UserReboot
MPU(S) 1:
Uptime is 3 weeks,0 days,23 hours,36 minutes
H3C SecPath L5000-AD920 MPU(S) with 1 ARM Processor
BOARD TYPE: NSQM6SUP04A0
DRAM: 8192M bytes
FLASH: 4096M bytes
PCB 1 Version: VER.A
PCB 2 Version: VER.A
Bootrom Version: 109
CPLD 1 Version: 005
CPLD 2 Version: 002
Release Version: H3C SecPath L5000-AD920-9900P33
Patch Version: None
Reboot Cause: UserReboot
LPU 2:
Uptime is 3 weeks,0 days,23 hours,29 minutes
H3C SecPath L5000-AD920 LPU with 1 ARM Processor
BOARD TYPE: L5000-AD920
DRAM: 2048M bytes
PCB 1 Version: VER.A
PCB 2 Version: VER.A
SUBCARD 1 PCB Version:VER.B
SUBCARD 2 PCB Version:VER.B
SUBCARD 3 PCB Version:VER.A
SUBCARD 4 PCB Version:VER.A
Bootrom Version: 103
CPLD 1 Version: 002
SUBCARD 1 CPLD Version:001
SUBCARD 2 CPLD Version:001
SUBCARD 3 CPLD Version:002
SUBCARD 4 CPLD Version:002
Release Version: H3C SecPath L5000-AD920-9900P33
Patch Version: None
Reboot Cause: UserReboot
PowChip Version: 000
SLOT 2 CPU 1
CPU type: Multi-core CPU
DDR4: 32752M bytes
FLASH: 7296M bytes
Board PCB Version: Ver.B
CPLD Version: 1.0
Release Version: H3C SecPath M9000-9900P33
Basic BootWare Version:1.06
Extend BootWare Version:1.06
SLOT 2 CPU 2
CPU type: Multi-core CPU
DDR4: 32752M bytes
FLASH: 7296M bytes
Board PCB Version: Ver.B
CPLD Version: 1.0
Release Version: H3C SecPath M9000-9900P33
Basic BootWare Version:1.06
Extend BootWare Version:1.06
SLOT 2 CPU 3
CPU type: Multi-core CPU
DDR4: 32752M bytes
FLASH: 7296M bytes
Board PCB Version: Ver.B
CPLD Version: 1.0
Release Version: H3C SecPath M9000-9900P33
Basic BootWare Version:1.06
Extend BootWare Version:1.06
SLOT 2 CPU 4
CPU type: Multi-core CPU
DDR4: 32752M bytes
FLASH: 7296M bytes
Board PCB Version: Ver.B
CPLD Version: 1.0
Release Version: H3C SecPath M9000-9900P33
Basic BootWare Version:1.06
Extend BootWare Version:1.06
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
Software feature and command updates
For more information about the software feature and command update history, see H3C SECPATH9000AD-BLADEADEM9000AD-CMW710-R9900P33 Release Notes (Software Feature Changes).
MIB updates
Version number | Item | MIB file | Module name | Remarks |
R9900P33 | New | / | / | N/A |
Modified | / | / | N/A | |
R9900P30 | New | / | / | N/A |
Modified | / | / | N/A | |
R9900P29 | New | / | / | N/A |
Modified | / | / | N/A | |
R9900P2701 | New | / | / | N/A |
Modified | / | / | N/A | |
R9900P21 | New | / | / | N/A |
Modified | / | / | N/A |
Operation changes
Restrictions and cautions
Before performing an upgrade, see H3C SECPATH9000AD-BLADEADEM9000AD-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 custom 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.
· Make sure all server farms of the same virtual service have an SNAT address pool specified, or none of them has an SNAT address pool specified. If this condition is not met, traffic issues might occur. Similarly, for the LB actions configured in the LB policy for the virtual service, which correspond to different server farms, make sure SNAT is performed for all of them or none of them.
· 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 R9900P29
202506230457
· Symptom: SSL two-way service with excessively long request headers (total header fields exceeding 17K) triggers device reboot.
· Condition: SSL two-way, HTTP request headers too long.
Resolved problems in R9900P2701
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
202506180165
· Symptom: In dual or cluster setup with traffic on non-management master device and auto synchronization disabled, first configure vs1 and vs2 on the management master, then configure vs2 and vs1 on the other device, trigger batch backup, generate persistent entries after sending 1024k page HTTP traffic, delete virtual service v2's address, and the backup device reboots after prolonged testing.
· Condition: Dual or cluster networking, configuration changes trigger batch backup, occasionally causing reboot.
Resolved problems in R9900P21
N/A.
Related documentation
Documentation set
· H3C SecPath L5000-AD920 Application Delivery Security Gateway Installation Quick Start
· H3C SecPath L5000-AD920[L5000-AD920-G][M9000-AD6] Installation Guide
· H3C SecPath L5000-AD9X0 Series Configuration Guides(V7)(R9900)
· H3C SecPath L5000-AD9X0 Series Configuration Examples(V7)(R9900)
Obtaining documentation
To obtain the latest documents, go to the H3C website at www.h3c.com/en
· To obtain the most recent drive and firmware, access http://www.h3c.com/en/Technical_Documents
· Select the product category and product model. Then, you can search for and download documents related to the product.
Technical support
Email: [email protected]
Website: http://www.h3c.com/en
Item | Specifications | |
Product model | M9000-AD6 | L5000-AD920 |
Memory | MPU: 8 GB Service module: 32 GB per CPU | |
Flash | MPU: 4 GB Service module: 8 GB per CPU | |
MPU slots | 2 Each MPU contains one console port, one USB port, and one 1000Base-T copper port. | |
Service module slots | 2 slots, supporting the following application delivery service modules: · NS-ADEEMPA0, H3C SecPath M9000-AD SecBlade V Application Delivery Engine A Module(MP), dual-CPU service module · NS-ADEEMPB0, H3C SecPath M9000-AD SecBlade V Application Delivery Engine B Module(MP), single-CPUservice module · NS-ADEEMPC0, H3C SecPath M9000-AD SecBlade V Application Delivery Engine C Module (MP), dual-CPU (1.8 GHz) service module · NS-ADEEMPC1, H3C SecPath M9000-AD SecBlade V Application Delivery Engine C1 Module (MP), dual-CPU (1.8 GHz) service module Each MPU contains one console port, one USB port, and one 1000Base-T copper port. | |
Interface module slots | 2 slots, supporting the following interface modules: · NSQM2QG4A0, H3C SecPath M9000 Series 4-Port 40Gb Ethernet Optical Interface Module(QSFP+) · NSQM2TG16A0, H3C SecPath M9000 Series 16-Port 10Gb Ethernet Optical Interface Module(SFP+) · NSQM2QG2TG8A0, H3C SecPath M9000 Series 2-Port 40Gb Ethernet Optical Interface (QSFP+)+8-Port 10Gb Ethernet Optical Interface Module(SFP+) | |
Hard disk slots | 2 slots, supporting 2.5-inch/SATA 480 GB SSDs. Hot swapping is not supported. | |
Power modules | 4 slots, supporting AC/DC power modules. Mixed use of AC and DC power modules is not supported. | |
Fan modules | 2 slots, supporting front-to-rear and rear-to-front fan module. Mixed use of different types of fan modules is not supported. | |
Dimensions (H × W × D) | 88.1 × 440 × 660 mm (3.47 × 17.32 × 25.98 in) | |
Overall power consumption | Up to 1300 W with 2 + 2 redundancy. Up to 2600 W with no redundancy. | |
Temperature | · Operating: 0°C to 40°C (32°F to 104°F) · Storage: –40°C to 70°C (–40°F to 158°F) | |
Humidity | 5% RH to 95% RH, non-condensing | |
Category | Features | |
Server load balancing | Scheduling algorithms | Weighted round-robin algorithm Random Real server-based weighted least connections Dynamic feedback Minimum time Bandwidth Maximum bandwidth Source IP address hash Source IP address CARP hash Source IP address and port hash Source IP address and port CARP hash Destination IP address hash Destination IP address CARP hash HTTP hash HTTP CARP hash Member-based weighted least connections Priority-based scheduling algorithm URL-based 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 Source IP and destination IP-based session persistence HTTP packet header-based session persistence HTTP cookie-based session persistence HTTP content-based session persistence HTTP URL-based session persistence SIP-based session persistence RADIUS attribute-based session persistence DHCP attribute-based session persistence SSL ID-based session persistence | |
Health check | ICMP TCP TcpHalfOpen FTP HTTP HTTPS SSL DNS Radius UDP POP3 RTSP IMAP4 SNMP SIP ARP SMTP snmp-dca WAP Custom Combined health check algorithm | |
HTTP policy | Policy matching elements: · HTTP cookie · HTTP header · HTTP URL · HTTP content · HTTP method · HTTP class: Nested invocation of HTTP classes · generic-class: Using generic classes as matching conditions Actions: · HTTP Header insert · HTTP Header rewrite · HTTP Header delete · SSL URL location rewrite · SSL Client policy set · Real server farm selection | |
Generic policy | Policy matching elements: · Source IP · generic-class: Nested invocation of generic classes Actions: · SSL client policy setting · IP ToS setting · Real server farm selection | |
Protection policy | HTTP protection policy | |
WebSocket | WebSocket | |
HTTP parameter profile | Case sensitivity Maximum HTTP header resolve length Maximum HTTP content resolve length Server connection multiplexing HTTP message modification per request HTTP request distribution Secondary cookie separator Secondary cookie start bit character Handling method for URL or cookie exceeding maximum length | |
TCP parameter profile | Setting the processing method for data segments exceeding MSS: allow or discard Setting the size of the send and receive buffers | |
IP parameter profile | Setting the ToS field of IP packets responded by the real server through the device | |
SSL offloading | SSL offloading: offload SSL-based traffic All SSL server features, including certificate management, and authentication SSL client features, SSL encrypted transmission with backend servers | |
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, bandwidth, and link quality. 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 |
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.
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 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.
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.
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.
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 186.23.0.57/16 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 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.
<Sysname>
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 flash: (VFAT)
0 -rw- 3950 Feb 16 2023 20:37:28 startup.cfg
1 -rw- 125255 Feb 16 2023 20:37:28 startup.mdb
2 -rw- 17276928 Feb 16 2023 20:37:12 M9000AD6-CMW710-BOOT-E9900P33.b
in
3 -rw- 190119936 Feb 16 2023 20:37:14 M9000AD6-CMW710-SYSTEM-E9900P33
.bin
4 -rw- 1537 Jul 28 2022 16:00:04 ca.crt
5 drw- - Feb 08 2023 16:24:22 context
6 -rw- 513751 Feb 16 2023 21:04:34 defaultfile.zip
7 drw- - Jul 29 2022 09:53:56 diagfile
8 -rw- 7724 Aug 18 2022 14:37:56 dut1_back.cfg
9 -rw- 735 Jul 27 2022 14:59:10 hostkey
10 -rw- 1152 Feb 16 2023 20:37:28 ifindex.dat
11 -rw- 17253376 Aug 01 2022 11:57:38 M9000AD6-cmw710-boot-e8371p0901.b
in
12 -rw- 134144 Feb 16 2023 11:11:38 M9000AD6-cmw710-devkit-E9900P33
.bin
13 -rw- 81920 Feb 16 2023 11:11:36 M9000AD6-cmw710-manufacture-a1171
p1513.bin
14 -rw- 241545216 Aug 01 2022 11:57:44 M9000AD6-cmw710-system-e8371p0901
.bin
15 drw- - Jul 27 2022 14:59:10 lb
16 drw- - Jul 27 2022 14:58:58 license
17 drw- - Jul 28 2022 14:54:48 logfile
18 drw- - Jul 28 2022 16:01:38 pkey
19 drw- - Feb 08 2023 16:04:10 pki
20 -rw- 33 Feb 16 2023 21:04:37 raid_manager.log
21 -rw- 80 Jul 29 2022 17:44:46 rbmSwitchInfoFile.dat
22 drw- - Jul 27 2022 14:58:58 seclog
23 -rw- 2581 Jul 28 2022 16:00:08 server.pfx
24 -rw- 591 Jul 27 2022 14:59:10 serverkey
25 -rw- 4807 Feb 16 2023 20:37:28 startup.cfg
26 -rw- 125255 Feb 16 2023 20:37:28 startup.mdb
27 -rw- 37222 Jul 27 2022 15:14:52 sub_arp_nd.cfg
28 -rw- 386484 Jul 27 2022 15:14:52 sub_arp_nd.mdb
29 drw- - Feb 16 2023 11:15:44 versionInfo
30 drw- - Aug 24 2022 15:03:24 vsys
7292988 KB total (6591596 KB free)
<Sysname>
f. Execute the tftp put command in user view to upload the startup.cfg file to the TFTP server.
<Sysname> tftp 186.23.0.57 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
<Sysname>
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 186.23.0.57 get M9000_AD6.ipe
Press CTRL+C to abort.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 197M 100 197M 0 0 2231k 0 0:01:30 0:01:30 --:--:-- 2395k
Writing file...Done.
<Sysname>
b. Execute the boot-loader file command in user view to load the M9000_AD6.ipe file and specify it as the main image file at the next reboot.
<Sysname> boot-loader file flash:/M9000_AD6.ipe all main
Verifying the file flash:/M9000_AD6.ipe on slot 1...Done.
H3C SecPath M9000-AD6 images in IPE:
M9000AD6-CMW710-BOOT-E9900P33.bin
M9000AD6-CMW710-SYSTEM-E9900P33.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 flash:/M9000AD6-CMW710-BOOT-E9900P33.bin already exists on slot 1.
File flash:/M9000AD6-CMW710-SYSTEM-E9900P33.bin already exists on slot 1.
Overwrite the existing files?[Y/N]:y
Decompressing file M9000AD6-CMW710-BOOT-E9900P33.bin to flash:/M9000AD6-CMW710-BOOT-R9900P33.bin...Done.
Decompressing file M9000AD6-CMW710-SYSTEM-R9900P33.bin to flash:/M9000AD6-CMW710-SYSTEM-R9900P33.bin...Done.
Verifying the file flash:/M9000AD6-CMW710-BOOT-R9900P33.bin on slot 1...Done.
Verifying the file flash:/M9000AD6-CMW710-SYSTEM-R9900P33.bin on slot 1...Done.
The images that have passed all examinations will be used as the main startup software images at the next reboot on slot 1.
Decompression completed.
Do you want to delete flash:/M9000_AD6.ipe now? [Y/N]:n
<Sysname>
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:
flash:/M9000AD6-CMW710-BOOT-E9900P33.bin
flash:/M9000AD6-CMW710-SYSTEM-E9900P33.bin
Main startup software images:
flash:/M9000AD6-CMW710-BOOT-E9900P33.bin
flash:/M9000AD6-CMW710-SYSTEM-E9900P33.bin
Backup startup software images:
flash:/M9000AD6-CMW710-BOOT-E9900P33.bin
flash:/M9000AD6-CMW710-SYSTEM-E9900P33.bin
<Sysname>
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!
Start to check configuration with next startup configuration file in Context con
text1, please wait.........DONE!
This command will reboot the device. Continue? [Y/N]:y
Now rebooting, please wait...
…omitted…
e. After the reboot is complete, execute the display version command to verify that the system software image is correct.
<Sysname> dis version
H3C Comware Software, Version 7.1.064, Release 1171P152201
Copyright (c) 2004-2022 New H3C Technologies Co., Ltd. All rights reserved.
H3C SecPath M9000-AD6 uptime is 0 weeks, 0 days, 0 hours, 22 minutes
Last reboot reason: User reboot
Boot image: flash:/M9000AD6-CMW710-BOOT-R9900P33.bin
Boot image version: 7.1.064, Release 1171P152201
Compiled Dec 13 2022 15:00:00
System image: flash:/M9000AD6-CMW710-SYSTEM-R9900P33.bin
System image version: 7.1.064, Release 1171P152201
Compiled Dec 13 2022 15:00:00
SLOT 1 CPU 0
CPU type : Multi-core CPU
DDR4 SDRAM Memory : 196608M bytes
FLASH : 7122M bytes
Board PCB Version : Ver.A
FPGA PCB Version : Ver.A
Hdd PCB Version : Ver.A
Led PCB Version : Ver.A
CPLD_0 Version : 5.0
CPLD_1 Version : 5.0
CPLD_2 Version : 1.0
Release Version : SecPath M9000-AD6-1171P152201
Adm Version : 1.0
FPGA Version : B6001
FPGA Date : 2021.11.15
Basic BootWare Version: 1.06
Extend BootWare Version: 1.06
[SUBCARD 0] Fixed Subcard(Hardware)Ver.A, (Driver)1.0, (Cpld)2.0
<Sysname>
Using FTP to upgrade system software
1. 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
<Sysname>
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.
<Sysname>
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 flash: (VFAT)
0 -rw- 3950 Feb 16 2023 20:37:28 startup.cfg
1 -rw- 125255 Feb 16 2023 20:37:28 startup.mdb
2 -rw- 17276928 Feb 16 2023 20:37:12 M9000AD6-CMW710-BOOT-R9900P33.b
in
3 -rw- 190119936 Feb 16 2023 20:37:14 M9000AD6-CMW710-SYSTEM-R9900P33
.bin
4 -rw- 1537 Jul 28 2022 16:00:04 ca.crt
5 drw- - Feb 08 2023 16:24:22 context
6 -rw- 513751 Feb 16 2023 21:04:34 defaultfile.zip
7 drw- - Jul 29 2022 09:53:56 diagfile
8 -rw- 7724 Aug 18 2022 14:37:56 dut1_back.cfg
9 -rw- 735 Jul 27 2022 14:59:10 hostkey
10 -rw- 1152 Feb 16 2023 20:37:28 ifindex.dat
11 -rw- 17253376 Aug 01 2022 11:57:38 M9000AD6-cmw710-boot-e8371p0901.b
in
12 -rw- 134144 Feb 16 2023 11:11:38 M9000AD6-cmw710-devkit-R9900P33
.bin
13 -rw- 81920 Feb 16 2023 11:11:36 M9000AD6-cmw710-manufacture-a1171
p1513.bin
14 -rw- 241545216 Aug 01 2022 11:57:44 M9000AD6-cmw710-system-e8371p0901
.bin
15 drw- - Jul 27 2022 14:59:10 lb
16 drw- - Jul 27 2022 14:58:58 license
17 drw- - Jul 28 2022 14:54:48 logfile
18 drw- - Jul 28 2022 16:01:38 pkey
19 drw- - Feb 08 2023 16:04:10 pki
20 -rw- 33 Feb 16 2023 21:04:37 raid_manager.log
21 -rw- 80 Jul 29 2022 17:44:46 rbmSwitchInfoFile.dat
22 drw- - Jul 27 2022 14:58:58 seclog
23 -rw- 2581 Jul 28 2022 16:00:08 server.pfx
24 -rw- 591 Jul 27 2022 14:59:10 serverkey
25 -rw- 4807 Feb 16 2023 20:37:28 startup.cfg
26 -rw- 125255 Feb 16 2023 20:37:28 startup.mdb
27 -rw- 37222 Jul 27 2022 15:14:52 sub_arp_nd.cfg
28 -rw- 386484 Jul 27 2022 15:14:52 sub_arp_nd.mdb
29 drw- - Feb 16 2023 11:15:44 versionInfo
30 drw- - Aug 24 2022 15:03:24 vsys
7292988 KB total (6591596 KB free)
<Sysname>
f. Execute the ftp command in user view to access the FTP server.
<Sysname> ftp 186.23.0.57
Press CTRL+C to abort.
Connected to 186.23.0.57 (186.23.0.57).
220 3Com 3CDaemon FTP Server Version 2.0
User (186.23.0.57:(none)): admin
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 (186,23,0,57,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>
2. 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 M9000_AD6.ipe
M9000_AD6.ipe already exists. Overwrite it? [Y/N]:y
227 Entering passive mode (186,23,0,57,220,177)
125 Using existing data connection
................................................................................................................................................................................................................................................................................................................................................................226 Closing data connection; File transfer successful.
207404032 bytes received in 22.808 seconds (8.69 Mbytes/s)
ftp>
b. Execute the quit command in FTP client view to return to user view.
ftp> quit
221 Service closing control connection
<Sysname>
c. Execute the boot-loader file command in user view to load the M9000_AD6.ipe file and specify it as the main image file at the next reboot.
<Sysname> boot-loader file flash:/M9000_AD6.ipe all main
Verifying the file flash:/M9000_AD6.ipe on slot 1...Done.
H3C SecPath M9000_AD6 images in IPE:
M9000AD6-CMW710-BOOT-R9900P33.bin
M9000AD6-CMW710-SYSTEM-R9900P33.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 flash:/M9000AD6-CMW710-BOOT-R9900P33.bin already exists on slot 1.
File flash:/M9000AD6-CMW710-SYSTEM-R9900P33.bin already exists on slot 1.
Overwrite the existing files?[Y/N]:y
Decompressing file M9000AD6-CMW710-BOOT-R9900P33.bin to flash:/M9000AD6-CMW710-BOOT-R9900P33.bin...Done.
Decompressing file M9000AD6-CMW710-SYSTEM-R9900P33.bin to flash:/M9000AD6-CMW710-SYSTEM-R9900P33.bin...Done.
Verifying the file flash:/M9000AD6-CMW710-BOOT-R9900P33.bin on slot 1...Done.
Verifying the file flash:/M9000AD6-CMW710-SYSTEM-R9900P33.bin on slot 1...Done.
The images that have passed all examinations will be used as the main startup software images at the next reboot on slot 1.
Decompression completed.
Do you want to delete flash:/M9000_AD6.ipe now? [Y/N]:n
<Sysname>
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 1:
Current software images:
flash:/M9000AD6-CMW710-BOOT-R9900P33.bin
flash:/M9000AD6-CMW710-SYSTEM-R9900P33.bin
Main startup software images:
flash:/M9000AD6-CMW710-BOOT-R9900P33.bin
flash:/M9000AD6-CMW710-SYSTEM-R9900P33.bin
Backup startup software images:
flash:/M9000AD6-CMW710-BOOT-R9900P33.bin
flash:/M9000AD6-CMW710-SYSTEM-R9900P33.bin
<Sysname>
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!
Start to check configuration with next startup configuration file in Context con
text1, please wait.........DONE!
This command will reboot the device. Continue? [Y/N]:y
Now rebooting, please wait...
…omitted…
f. After the reboot is complete, execute the display version command to verify that the system software image is correct.
<Sysname> dis version
H3C Comware Software, Version 7.1.064, Release 1171P1521
Copyright (c) 2004-2022 New H3C Technologies Co., Ltd. All rights reserved.
H3C SecPath M9000-AD6 uptime is 0 weeks, 0 days, 0 hours, 22 minutes
Last reboot reason: User reboot
Boot image: flash:/M9000AD6-CMW710-BOOT-R9900P33.bin
Boot image version: 7.1.064, Alpha 1171P1521
Compiled Dec 13 2022 15:00:00
System image: flash:/M9000AD6-CMW710-SYSTEM-R9900P33.bin
System image version: 7.1.064, Alpha 1171P1521
Compiled Dec 13 2022 15:00:00
SLOT 1 CPU 0
CPU type : Multi-core CPU
DDR4 SDRAM Memory : 196608M bytes
FLASH : 7122M bytes
Board PCB Version : Ver.A
FPGA PCB Version : Ver.A
Hdd PCB Version : Ver.A
Led PCB Version : Ver.A
CPLD_0 Version : 5.0
CPLD_1 Version : 5.0
CPLD_2 Version : 1.0
Release Version : SecPath M9000-AD6-1171P1521
Adm Version : 1.0
FPGA Version : B6001
FPGA Date : 2021.11.15
Basic BootWare Version: 1.06
Extend BootWare Version: 1.06
[SUBCARD 0] Fixed Subcard(Hardware)Ver.A, (Driver)1.0, (Cpld)2.0 <Sysname>
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 | 186.23.0.57/16 |
| 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:
3. 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.
4. Assign an IP address on the same subnet as the management port GigabitEthernet 1/0/0 to the PC.
In this example, assign 186.23.0.57 to the PC.
5. Launch the Web browser, and enter 186.23.0.57 in the address bar.
The Web login page appears.
6. Type the default username and password, and click Login.
7. Select System > Upgrade Center > Software Upgrade from the navigation tree.
Figure 1 Software upgrade page
8. Click Upgrade immediately on the Software Upgrade page.
9. Select the startup file to be used, and click OK.
Figure 2 Upgrade Immediately page
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:
10. Use FTP or TFTP to download or upload the new BootWare image file to the root directory of the storage medium on the device.
11. Execute the bootrom update command to upgrade the BootWare.
<System> bootrom update flash:/ 8042f109039122_v1.06.btw slot 1
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!
<System>
12. 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. |
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 F5000 BootWare, Version1.06 *
* *
****************************************************************************
Copyright (c) 2004-2023 New H3C Technologies Co., Ltd.
Compiled Date : Feb 16 2023 11:12:13
Memory Type : DDR4 SDRAM
Memory Size : 196608MB
SPI Flash Size : 32MB
EMMC Flash Size : 7296MB
CPLD Version : 5.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 enabled.
Note: The current operating device is flash
Enter < Storage Device Operation > to select device.
==========================<EXTENDED-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 EXTENDED ASSISTANT MENU
Ctrl+F: Format File System
Ctrl+C: Display Copyright
Enter your choice(0-9):
The menu description is as follows:
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. |
14. 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. |
15. 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. |
16. 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) :ftp
Load File Name :M9000-AD6.ipe
:
Target File Name :M9000-AD6.ipe
:
Server IP Address :186.23.0.57
Local IP Address :186.23.57.116
Subnet Mask :255.255.0.0
Gateway IP Address :186.23.0.1
FTP User Name :admin
FTP User Password :******
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 |
|<6> Copy File |
|<0> Exit To Main Menu |
============================================================================
Enter your choice(0-6):
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 |
<6> Copy File | Copy file |
<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 80 Jul/29/2022 17:44:46 N/A flash:/rbmswitchinfofile.dat |
|2 17253376 Aug/01/2022 11:57:38 N/A flash:/M9000AD6-cmw710-boot-e8|
|371p0901.bin |
|3 241545216 Aug/01/2022 11:57:44 N/A flash:/M9000AD6-cmw710-system-|
|e8371p0901.bin |
|4 965 Feb/08/2023 16:03:54 N/A flash:/license/history/deviceid_|
|20230208160355.did |
|5 965 Feb/09/2023 19:23:58 N/A flash:/license/history/deviceid_|
|20230209192359.did |
|6 965 Feb/09/2023 19:23:58 N/A flash:/license/210235a2qbb225000|
|005.did |
|7 10485646 Feb/16/2023 19:55:16 N/A flash:/logfile/logfile.log |
|8 1048573 Feb/16/2023 17:24:24 N/A flash:/logfile/cfglog.log |
|9 353537 Jul/29/2022 15:13:38 N/A flash:/diagfile/diagfile.log |
|10 16 Feb/16/2023 11:15:44 N/A flash:/versioninfo/versionctl.da|
|t |
|11 1795 Jul/28/2022 16:01:24 N/A flash:/pki/5435c69ed3bcc5b2e4d58|
|0e393e373d3.info |
|12 1537 Jul/28/2022 16:01:24 N/A flash:/pki/ca-eca06d36-e91da0ef6|
|9a3306467531d234432936a.cer |
|13 1383 Jul/28/2022 16:01:38 N/A flash:/pki/lo-5435c69ed3bcc5b2e4|
|d580e393e373d3-0.cer |
|14 735 Jul/27/2022 14:59:10 N/A flash:/hostkey |
|15 591 Jul/27/2022 14:59:10 N/A flash:/serverkey |
|16 1152 Feb/16/2023 19:27:50 N/A flash:/ifindex.dat |
|17 3950 Feb/16/2023 19:27:50 M flash:/startup.cfg |
|18 102960 Feb/16/2023 19:27:50 N/A flash:/startup.mdb |
|19 21 Feb/16/2023 11:16:10 N/A flash:/.snmpboots |
|20 9475072 Feb/07/2023 17:58:04 N/A flash:/M9000AD6-cmw710-devkit-|
|e8371p0901.bin |
|21 27627520 Feb/16/2023 11:10:14 M flash:/M9000AD6-cmw710-boot-a1|
|171p1513.bin |
|22 279628800 Feb/16/2023 11:10:24 M flash:/M9000AD6-cmw710-system-|
|R9900P33.bin |
|23 81920 Feb/16/2023 11:11:36 M flash:/M9000AD6-cmw710-manufac|
|ture-R9900P33.bin |
|24 134144 Feb/16/2023 11:11:38 M flash:/M9000AD6-cmw710-devkit-|
|R9900P33.bin |
|25 513751 Feb/16/2023 19:37:14 N/A flash:/defaultfile.zip |
|26 33 Feb/16/2023 19:37:22 N/A flash:/raid_manager.log |
……omitted……
============================================================================
===============================<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 |
|<6> Copy File |
|<0> Exit To Main Menu |
============================================================================
Enter your choice(0-6):
Configuring the .ipe startup file type
17. Press 2 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 207404032 Nov/18/2022 14:14:20 N/A flash:/M9000_AD6.ipe |
|0 Exit |
============================================================================
18. 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):
19. 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 M9000AD6-CMW710-BOOT-R9900P33.bin is self-decompressing...
Saving file flash:/M9000AD6-CMW710-BOOT-R9900P33.bin .....................
......Done.
Image file M9000AD6-CMW710-SYSTEM-R9900P33.bin is self-decompressing...
Saving file flash:/M9000AD6-CMW710-SYSTEM-R9900P33.bin ...................
............................................................................
.........................................Done.
Set the file attribute success!
Configuring the .bin startup file type
'M' = MAIN 'B' = BACKUP 'N/A' = NOT ASSIGNED
============================================================================
|NO. Size(B) Time Type Name |
|1 17276928 Nov/18/2022 14:35:02 M+B flash:/M9000AD6-cmw710-boot-a1|
|171p1513.bin |
|2 190119936 Nov/18/2022 14:35:10 M+B flash:/M9000AD6-cmw710-system-|
|R9900P33.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 //Select 0 to stop file selection
You have selected:
flash:/M9000AD6-CMW710-BOOT-R9900P33.bin
flash:/M9000AD6-CMW710-SYSTEM-R9900P33.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
1. 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 80 Jul/29/2022 17:44:46 N/A flash:/rbmswitchinfofile.dat |
|2 17253376 Aug/01/2022 11:57:38 N/A flash:/M9000AD6-cmw710-boot-e8|
|371p0901.bin |
|3 241545216 Aug/01/2022 11:57:44 N/A flash:/M9000AD6-cmw710-system-|
|e8371p0901.bin |
|4 965 Feb/08/2023 16:03:54 N/A flash:/license/history/deviceid_|
|20230208160355.did |
|5 965 Feb/09/2023 19:23:58 N/A flash:/license/history/deviceid_|
|20230209192359.did |
|6 965 Feb/09/2023 19:23:58 N/A flash:/license/210235a2qbb225000|
|005.did |
|7 10485646 Feb/16/2023 19:55:16 N/A flash:/logfile/logfile.log |
|8 1048573 Feb/16/2023 17:24:24 N/A flash:/logfile/cfglog.log |
|9 353537 Jul/29/2022 15:13:38 N/A flash:/diagfile/diagfile.log |
|10 16 Feb/16/2023 11:15:44 N/A flash:/versioninfo/versionctl.da|
|t |
|11 1795 Jul/28/2022 16:01:24 N/A flash:/pki/5435c69ed3bcc5b2e4d58|
|0e393e373d3.info |
|12 1537 Jul/28/2022 16:01:24 N/A flash:/pki/ca-eca06d36-e91da0ef6|
|9a3306467531d234432936a.cer |
|13 1383 Jul/28/2022 16:01:38 N/A flash:/pki/lo-5435c69ed3bcc5b2e4|
|d580e393e373d3-0.cer |
|14 735 Jul/27/2022 14:59:10 N/A flash:/hostkey |
|15 591 Jul/27/2022 14:59:10 N/A flash:/serverkey |
|16 1152 Feb/16/2023 19:27:50 N/A flash:/ifindex.dat |
|17 3950 Feb/16/2023 19:27:50 M flash:/startup.cfg |
|18 102960 Feb/16/2023 19:27:50 N/A flash:/startup.mdb |
|19 21 Feb/16/2023 11:16:10 N/A flash:/.snmpboots |
|20 9475072 Feb/07/2023 17:58:04 N/A flash:/M9000AD6-cmw710-devkit-|
|e8371p0901.bin |
|21 27627520 Feb/16/2023 11:10:14 M flash:/M9000AD6-cmw710-boot-a1|
|171p1513.bin |
|22 279628800 Feb/16/2023 11:10:24 M flash:/M9000AD6-cmw710-system-|
|R9900P33.bin |
|23 81920 Feb/16/2023 11:11:36 M flash:/M9000AD6-cmw710-manufac|
|ture-R9900P33.bin |
|24 134144 Feb/16/2023 11:11:38 M flash:/M9000AD6-cmw710-devkit-|
|R9900P33.bin |
|25 513751 Feb/16/2023 19:37:14 N/A flash:/defaultfile.zip |
|26 33 Feb/16/2023 19:37:22 N/A flash:/raid_manager.log |
…………
|0 Exit |
============================================================================
Enter file No.:
2. 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:
Enter file No.:3
The file you selected is flash:/raid_manager.log,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.