|
| |
H3C SECPATH1020F-1030F-1050F-1060F-1070F-1080F-100FAG2-1000FCG2-CMW710-R9360P27 |
| |
Release Notes |
| |
|
| |
Hardware and software compatibility matrix· 2
Upgrade restrictions and guidelines· 5
Hardware feature updates in F9345P11· 6
Hardware feature updates in E9345P05· 6
Software feature and command updates· 6
License registration and installation· 10
Open problems and workarounds· 10
Resolved problems in R9360P27· 11
Resolved problems in R9360P22· 11
Resolved problems in R9360P21· 12
Resolved problems in R9360P19· 13
Resolved problems in F9360P17· 14
Resolved problems in F9360P1212· 14
Resolved problems in F9360P10· 15
Resolved problems in F9360P07· 15
Resolved problems in F9360P05· 15
Resolved problems in F9360P0301· 15
Resolved problems in F9345P18· 15
Resolved problems in F9345P16· 15
Resolved problems in R9345P14· 15
Resolved problems in F9345P11· 16
Resolved problems in E9345P08· 16
Resolved problems in E9345P05· 16
Resolved problems in E9345P02· 16
Resolved problems in E9340· 17
Resolved problems in E9333P10· 17
Appendix B List of severe vulnerabilities· 6
Severe vulnerabilities in R9360P27 and earlier versions· 6
Appendix C Upgrading software· 8
Upgrading system software from the CLI 10
Upgrading system software from the Web interface· 17
Upgrading system software from BootWare menus· 18
Upgrading the BootWare from the CLI 22
Upgrading BootWare from BootWare menus· 23
Handling software upgrade failures· 26
Appendix D Using BootWare menus· 27
Using the BASIC-BOOTWARE menu· 28
Accessing the BASIC-BOOTWARE menu· 28
Modifying serial port parameters· 29
Upgrading the extended BootWare segment 29
Upgrading the entire BootWare· 29
Running the primary extended BootWare segment 30
Running the backup extended BootWare segment 30
Accessing the BASIC ASSISTANT menu· 31
Using the EXTENDED-BOOTWARE menu· 31
Accessing the EXTENDED-BOOTWARE menu· 31
Controlling the password recovery capability· 33
Accessing the Serial submenu· 34
Accessing the Ethernet submenu· 35
Restoring the factory-default configuration· 48
Skipping the configuration file· 49
Accessing the BootWare Operation submenu· 49
Skipping console login authentication· 49
Accessing the EXTEND ASSISTANT submenu· 50
Formatting the file system·· 51
List of tables
Table 1 Version history............................................................................................................................................................. 1
Table 2 Hardware and software compatibility matrix..................................................................................................... 3
Table 3 ISSU version compatibility matrix.......................................................................................................................... 4
Table 4 ISSU compatibility list................................................................................................................................................ 5
Table 5 MIB updates................................................................................................................................................................. 7
Table 6 Hardware specifications for F1020/F1030/F1050/F1060/F100-A-G2/F1000-C-G2/F1000-AK130/F1000-AK140/F1000-AK150/F1000-AK160/F1000-AK170/F100-E-EI/F100-A-EI/F1000-C8160/F1000-C8170/F1020-GM/F1030-GM.................................................................................................................................................................. 1
Table 7 Hardware specifications for F1070/F1080/F1000-AK180/F1000-C8180/F1070-GM/F1070-GM-L.. 1
Table 8 Hardware specifications for F1000-AI-50/F1000-AI-30/F1000-AI-20........................................................ 2
Table 9 Hardware specifications for F1000-990-AI/F1000-980-AI/F1000-970-AI/F1000-960-AI/F1000-950-AI/F1000-930-AI/F1000-920-AI...................................................................................................................................................... 3
Table 10 Firewall software features...................................................................................................................................... 3
Table 11 Default login information.................................................................................................................................... 17
Table 14 BootWare menus.................................................................................................................................................... 27
Table 15 BootWare shortcut keys....................................................................................................................................... 27
Table 17 BASIC ASSISTANT menu options...................................................................................................................... 31
Table 19 Serial submenu options....................................................................................................................................... 35
Table 22 File Control submenu options........................................................................................................................... 37
Table 23 BootWare Operation submenu options......................................................................................................... 49
Table 24 DEVICE CONTROL menu options...................................................................................................................... 50
Table 25 EXTEND ASSISTANT submenu options........................................................................................................... 50
Introduction
This document describes the features, restrictions and guidelines, open problems, and workarounds for version R9360P27. Before you use this version on a live network, back up the configuration and test the version to avoid software upgrade affecting your live network.
Use this document in conjunction with H3C SECPATH1020F-1030F-1050F-1060F-1070F-1080F-100FAG2-1000FCG2-CMW710-R9360P27 Release Notes (Software Feature Changes) and the documents listed in "Related documentation."
Version information
Version number
Comware software, Version 7.1.064, Release 9360P27
Note: You can see the version number with the display version command in any view. Please see Note①.
Version history
IMPORTANT: The software feature changes listed in the version history table for each version are not complete. To obtain complete information about all software feature changes in each version, see the Software Feature Changes document for this release notes. |
Version number | Last version | Release date | Release type | Remarks |
R9360P27 | R9360P22 | 2022-08-29 | Release version | Solved problems, restricted to the use of Technical Support. |
R9360P22 | R9360P21 | 2022-03-28 | Release version | Solved problems, restricted to the use of Technical Support. |
R9360P21 | R9360P19 | 2022-02-27 | Release version | Solved problems, restricted to the use of Technical Support. |
R9360P19 | F9360P17 | 2021-12-28 | Release version | Solved problems, restricted to the use of Technical Support. |
F9360P17 | F9360P1212 | 2021-10-30 | Feature version | Solved problems, restricted to the use of Technical Support. |
F9360P1212 | F9360P10 | 2021-08-28 | Feature version | Solved problems, restricted to the use of Technical Support. |
F9360P10 | F9360P07 | 2021-04-13 | Feature version | This version has solved problems and is restricted to the use of Technical Support. |
F9360P07 | F9360P05 | 2020-12-27 | Feature version | This version has added new features and is restricted to the use of Technical Support. |
F9360P05 | F9360P0301 | 2020-11-11 | Feature version | This version has added new features and is restricted to the use of Technical Support. |
F9360P0301 | F9345P18 | 2020-09-11 | Feature version | This version has added new features and is restricted to the use of Technical Support. |
F9345P18 | F9345P16 | 2020-08-30 | Feature version | This version has solved problems and is restricted to the use of Technical Support. |
F9345P16 | R9345P14 | 2020-06-28 | Feature version | This version has solved problems and is restricted to the use of Technical Support. |
R9345P14 | F9345P11 | 2020-04-14 | Release version | This version has solved problems and is released for the use of Technical Support. |
F9345P11 | E9345P08 | 2019-12-30 | Feature version | This version has solved problems and is restricted to the use of Technical Support. |
E9345P08 | E9345P05 | 2019-09-26 | ESS version | Released for the use of Technical Support |
E9345P05 | E9345P02 | 2019-06-26 | ESS version | Restricted to the use of technical support. |
E9345P02 | E9340 | 2019-03-27 | ESS version | Restricted to the use of technical support. |
E9340 | E9333P10 | 2018-09-30 | ESS version | First release for the overseas market. Restricted to the use of technical support. |
E9333P10 | First release | 2018-08-30 | ESS version | First release for the overseas market. Restricted to the use of technical support. |
Hardware and software compatibility matrix
CAUTION: To avoid an upgrade failure, use Table 2 to verify the hardware and software compatibility before performing an upgrade. |
Table 2 Hardware and software compatibility matrix
Item | Specifications | ||||
Hardware platform | F1020/F100-A-G2/F1000-AK130/F100-A-EI/F1000-AI-20/F1000-920-AI/F1020-GM/F100-A-HI | F1030/F1050/F1000-AK140/F1000-AK150/F100-E-EI/F100-E-G2/F1000-C8160/F1000-AI-50/F1000-AI-30/F1000-930-AI/F1000-950-AI/F1000-960-AI/F1030-GM/F1000-C-HI | F1000-C-G2/F1060/F1000-S-G2/F1000-AK160/F1000-AK170/F1000-C8170/F1000-970-AI | F1070/F1000-A-G2/F1000-AK180/F1070-GM/F1070-GM-L/F1000-980-AI | F1080/F1000-E-G2/F1000-C8180/F1000-990-AI |
Memory | 2 GB | 4 GB | 8 GB | 8 GB | 16 GB |
Flash | NOR flash: 8 GB NAND flash: 1 GB | ||||
BootWare version | 2.06 (Note: Execute the display version command in any view to view the version information. Please see Note②) | ||||
Host software (MD5 checksum) | SECPATH1020F_1080F-CMW710-R9360P27.ipe (159c0b503ec58eb2c9aeb30b96bd9603) f1000fw-cmw710-boot-R9360P27.bin (1142dd7d68ab0089063746dd74932e27) f1000fw-cmw710-system-R9360P27.bin (8a4d51f3e84d23761524aeefbcdd27ce) | ||||
iMC version | iMC PLAT 7.3 (E0705P12) iMC UBA 7.3 (E0707L06) iMC IVM 7.3 (E0506) iMC EIA 7.3 (E0611P13) iMC SHM 7.3 (E0707L06) iMC-DM PLAT 7.3 (E0705P12) iMC-iCC PLAT 7.3 (E0705P12) iMC-ACLM PLAT 7.3 (E0705P12) iMC-VLAN iMC PLAT 7.3 (E0705P12) | ||||
H3C SecCenter CSAP-S version | E1143P0601 | ||||
H3C SMP version | E1112P02 | ||||
H3C SecCloud OMP version | E1301P01 | ||||
ADWAN | Incompatible | ||||
ADDC | Incompatible | ||||
ADcampus | Incompatible | ||||
iNode version | iNode PC 7.3 (E0585) (non-GM) iNode PC 7.3 (C0565) (GM) | ||||
Remarks | 1. The time on the iMC server must be consistent with the time on the device. 2. As a best practice, do not use the wildcard subnet address type when you configure address groups on the device management page of security services on iMC. · Enable action parameters before you configure them on the device management page of security services on iMC. |
Sample: To display the host software and BootWare version of F1070, perform the following:
<H3C> display version
H3C Comware Software, Version 7.1.064, Release 9360P27 ------NOTE①
Copyright (c) 2004-2022 New H3C Technologies Co., Ltd. All rights reserved.
H3C SecPath F1070 uptime is 0 weeks, 3 days, 22 hours, 0 minutes
Last reboot reason: User reboot
Boot image: flash:/f1000fw-cmw710-boot-R9360P27.bin
Boot image version: 7.1.064, Release 9360P27
Compiled Mar 15 2022 14:00:00
System image: flash:/f1000fw-cmw710-system-R9360P27.bin
System image version: 7.1.064, Release 9360P27
Compiled Mar 15 2022 14:00:00
SLOT 1
CPU type: Multi-core CPU
DDR3 SDRAM Memory 8190M bytes
Board PCB Version:Ver.A
CPLD_A Version: 1.0
CPLD_B Version: 1.0
Basic BootWare Version: 2.06 ---NOTE②
Extend BootWare Version: 2.06
Board PFC Version:Ver.A
NandFlash PCB Version:Ver.A
HD PCB Version:Ver.A
[SubSlot 0]16GE+8SFP+2XGE (Hardware)Ver.A, (Driver)1.0, (Cpld)1.0
[SubSlot 1]4GE (Hardware)Ver.A, (Driver)1.0, (Cpld)1.0
[SubSlot 2]4GE (Hardware)Ver.A, (Driver)1.0, (Cpld)1.0
ISSU upgrade type matrix
ISSU provides two upgrade types: compatible upgrade and incompatible upgrade. Table 3 provides the approved ISSU upgrade types only between the current version and the history versions within the past 18 months. This matrix does not include history versions that are 18 months earlier than the current version, for which, no ISSU upgrade verification is performed.
For more information about ISSU, see the fundamental configuration guide for the device.
Table 3 ISSU version compatibility matrix
Current version | History version | ISSU upgrade method |
SECPATH1020F_1080F-CMW710-R9360P27 | SECPATH1020F_1080F-CMW710-R9360P22 | Compatible |
SECPATH1020F_1080F-CMW710-R9360P21 | Compatible | |
SECPATH1020F_1080F-CMW710-F9345P19 | Compatible | |
SECPATH1020F_1080F-CMW710-F9345P17 | Incompatible | |
SECPATH1020F_1080F-CMW710-F9345P1212 | Incompatible | |
SECPATH1020F_1080F-CMW710-F9345P10 | Incompatible | |
SECPATH1020F_1080F-CMW710-F9345P07 | Incompatible | |
SECPATH1020F_1080F-CMW710-F9345P05 | Incompatible | |
SECPATH1020F_1080F-CMW710-F9345P0301 | Incompatible | |
SECPATH1020F_1080F-CMW710-F9345P18 | Incompatible | |
SECPATH1020F_1080F-CMW710-F9345P16 | Incompatible | |
S5820V2_5830V2-CMW710-R9345P14 | Incompatible | |
S5820V2_5830V2-CMW710-F9345P11 | Incompatible | |
S5820V2_5830V2-CMW710-E9345P08 | Incompatible | |
S5820V2_5830V2-CMW710-E9345P05 | Incompatible | |
S5820V2_5830V2-CMW710-E9345P02 | Incompatible | |
S5820V2_5830V2-CMW710-E9340 | Incompatible | |
S5820V2_5830V2-CMW710-E9333P10 | Incompatible |
Upgrade restrictions and guidelines
To ensure hardware compatibility, do not downgrade the factory software version.
For the signature databases for anti-virus and URL filtering, the official website provides two sizes for different device storage spaces. The letter H in the name indicates a large signature database. For example, the V7-AV-H-1.0.68.dat is a large signature database and the V7-AV-1.0.68.dat is a small one. When you perform a manual update, examine your device storage capacity to determine which signature database should be downloaded. The large signature databases are supported when the memory is larger than 8 GB, and the capacity of the storage medium (flash memory, SD card, or CF card) is larger than 1 GB. Otherwise, only the small signature databases are supported.
You can upgrade an IRF fabric from a security policy-incapable version to a security-policy-capable version through an ISSU. To use security policies after the upgrade, you must reboot the IRF fabric.
To ensure a successful upgrade, make sure the current Boot ROM version is consistent with the system version before an ISSU.
After an ISSU, clear the browser cache for the Web interface to correctly display the configuration information of modified features.
You can check the Upgrade Way field in the output from the display version comp-matrix command for recommended ISSU methods.
ISSU is not supported for an upgrade from an earlier version to E9628P05.
F9660P14 and later versions are incompatible with versions earlier than F9660P14 and F9660P12XX exception versions in compatible ISSU upgrade. Therefore, version F9660P14 is the baseline version for ISSU.
Table 4 ISSU compatibility list
Version description | Version identifier | Version number | ISSU compatibility |
Baseline version | V0 | F9345P11 | Compatible |
Last software version | Vn-1 | R9360P22 | / |
Last Release version | Vk | R9360P22 | / |
In the RBM dual-host mode, versions earlier than F9660P10 do not support compatible upgrade. For the upgrade procedure, see the upgrade guide in the H3C technical document center.
After the vulnerability caused by weak password algorithms is resolved, the iNode client (TLS 1.0 is used for negotiation by default) carried in the earlier version cannot log in to the SSL VPN gateway. You must use a new iNode client (E0582 or later).
Hardware feature updates
Hardware feature updates in F9345P11
The hardware platform F1070-GM-L was added.
For more information about the hardware features, see "Hardware features" in the appendix.
Hardware feature updates in E9345P05
The following hardware platforms were added:
· F1000-AI-50
· F1000-AI-30
· F1000-AI-20
· F1000-990-AI
· F1000-980-AI
· F1000-970-AI
· F1000-960-AI
· F1000-950-AI
· F1000-930-AI
· F1000-920-AI
For more information about the hardware features, see "Hardware features" in the appendix.
Software feature and command updates
This version has the following changes.
New feature: NAT64-type rules
· New feature: NAT66-type rules
· New feature: Enabling preferential processing of RADIUS authentication requests
· Modified feature: Changing the tunnel ID range
· New feature: Configuring security log output limit
· New feature: Configuring a description for an object
For more information about the software feature and command update history, see H3C SECPATH1020F-1030F-1050F-1060F-1070F-1080F-100FAG2-1000FCG2-CMW710-R9360P27 Release Notes (Software Feature Changes).
MIB updates
Item | MIB file | Module | Description |
R9360P27 | |||
New | None | None | None |
Modified | None | None | None |
R9360P22 | |||
New | None | None | None |
Modified | None | None | None |
R9360P21 | |||
New | None | None | None |
Modified | None | None | None |
R9360P19 | |||
New | None | None | None |
Modified | None | None | None |
F9360P17 | |||
New | None | None | None |
Modified | None | None | None |
F9360P1212 | |||
New | None | None | None |
Modified | None | None | None |
F9360P10 | |||
New | None | None | None |
Modified | None | None | None |
F9360P07 | |||
New | None | None | None |
Modified | None | None | None |
F9360P05 | |||
New | None | None | None |
Modified | None | None | None |
F9360P0301 | |||
New | None | None | None |
Modified | None | None | None |
F9345P18 | |||
New | None | None | None |
Modified | None | None | None |
F9345P16 | |||
New | None | None | None |
Modified | None | None | None |
R9345P14 | |||
New | None | None | None |
Modified | None | None | None |
F9345P11 | |||
New | None | None | None |
Modified | None | None | None |
E9345P08 | |||
New | None | None | None |
Modified | None | None | None |
E9345P05 | |||
New | None | None | None |
Modified | None | None | None |
E9345P02 | |||
New | None | None | None |
Modified | None | None | None |
E9340 | |||
New | None | None | None |
Modified | None | None | None |
E9333P10 | |||
New | None | None | None |
Modified | None | None | None |
Operation changes
None.
Restrictions and cautions
Before performing an upgrade, see H3C SECPATH1020F_1080F-100FAG2-1000FCG2-CMW710-R9360P27 Release Notes (Software Feature Changes) and related documentation to see the software feature changes and evaluate the influence on the service.
To avoid abnormality and configuration failure, follow these restrictions:
· Use the following browsers:
¡ Chrome 40 or higher.
¡ Firefox 19 or higher.
¡ Internet Explorer 910 or higher.
· The encoding format of the CLI must be GB18030. Otherwise, the Web interface displays garbled characters.
· Support for security policies was added in F9323P01. The interzone policies you have configured in an earlier version still take effect, but you cannot configure or display interzone policies through the Web interface. Once you configure security policies, the interzone policies no longer take effect. You can use commands to convert interzone polices into security policies. For more information the security policy feature, see the configuration guide and command reference for this feature.
· The Web interface and CLI cannot be used together. Do not configure a feature through both the Web interface and CLI.
· SSL VPN Web access to WeChat, Alipay, and hao123 webpages might fail because of missing URL rewriting for some of the contents to be accessed.
· Only devices of the same model can form an IRF fabric.
· IRF physical interfaces must be the same type.
· Interface modules do not support IRF, and they are not hot swappable. If you install or uninstall interface modules when the device is running, the device will be damaged.
· Fiber ports on interface modules do not support autonegotiation mode.
· 10-GE fiber ports do not support 1000-Mbps transceiver modules.
· As from F9360P1212, the device supports global NAT. However, VPN and DNS mapping are to be supported yet.
· Because global NAT determines the destination security zone according to the FIB table, a destination security zone cannot be used by global NAT to match traffic that has been permitted by PBR or LLB. If a destination security zone is not used by a global NAT rule, packets to the destination security zone cannot match the global NAT rule, or services will be interrupted if application changes or configuration changes occur.
· Use fixed ports of the device as long as possible. Use expansion interface modules only when fixed ports are not sufficient. Expansion slots 1 and 2 are low-speed slots and provide 1 Gbps bandwidth.
· As from F9360P1212, the device supports configuring remote backup management (RBM), but it is configurable only in the default context. As from R9360P19, RBM is configurable in non-default contexts.
· As from R9360P21, the IP address of an email server supporting the report subscription page can be an IP address or a host name.
· The standby device in RBM cannot process SSL VPN dialup traffic.
· The MAC addresses of a main interface and its subinterfaces must be the same.
· When domain name-based address object groups are used:
¡ If the local DNS server for the terminal is the device, the device acts as the DNS proxy, and you do not need to enable DNS snooping.
¡ If the local DNS server for the terminal is a DNS server on the external network, the device transmits packets for the terminal transparently. To avoid service interruption, you must enable DNS snooping after upgrading to R9360P27.
· After the vulnerability caused by weak password algorithms is resolved, the iNode client (TLS 1.0 is used for negotiation by default) carried in the earlier version cannot log in to the SSL VPN gateway. You must use a new iNode client (E0582 or later).
License management
About licenses
To use license-based features, you must purchase licenses from H3C and install the licenses.
For more information about license-based features and supported licenses, see H3C SecPath F1000 & F5000 Firewall Series License Matrixes.
License registration and installation
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 (Comware 7), H3C Security Products Licensing Configuration Demonstration (Comware 7), H3C Security Products Licensing Configuration Examples (Comware 7), and H3C Security Products Licensing Guide (Comware 7).
H3C provides license-related FAQ. For more information, see H3C Security Products Licensing FAQ (Comware 7).
Open problems and workarounds
201907040959
· Symptom: Traffic fails to be forwarded.
· Condition: This symptom occurs if the following operations are performed:
a. Configure two output interfaces.
b. Configure last hop holding and IPsec on one output interface.
c. Send traffic to the device after the session ages out.
· Workaround: None.
202201200448
· Symptom: The size of the physical memory used for caches is large.
· Condition: This symptom occurs after the device is upgraded to D060SP.
· Workaround: None.
202201051477
· Symptom: The number of available paths for the sensor path command is small.
· Condition: This symptom occurs when you execute the sensor path command.
· Workaround: None.
202203221131
· Symptom: The device fails to startup when loading D060SP.
· Condition: This symptom occurs if the device has a small amount of memory.
· Workaround: Do not start up the device with a large amount of configuration.
List of resolved problems
Resolved problems in R9360P27
202201171756
· Symptom: The value of the hh3cCfgRunModifiedLast node is modified when no configuration change is performed.
· Condition: This symptom occurs if you reference a time range in a security policy.
202203011175
· Symptom: The modification to a security policy cannot take effect.
· Condition: This symptom occurs if you reference an object group containing a large number of domain names in the security policy and configure a DNS server.
202208090039
· Symptom: In an RBM network, the master device reboots.
· Condition: This symptom occurs if the following operations are performed:
a. Enable fast drop on the Web interface.
b. Restart a non-default context on the master device repeatedly while traffic is present.
202207180312
· Symptom: In an IPv4 VRRP+RBM environment, both devices become backup devices.
· Condition: This symptom occurs if you restart the VRRP and RBM processes repeatedly after the memory usage reaches the threshold.
202207121157
· Symptom: The first ping packet is lost when the device pings a directly connected next hop.
· Condition: This symptom occurs if the ping packet matches an outbound NAT rule and has the VRRP virtual address as the source IP address.
202206281707
· Symptom: In an RBM network, it takes 10 minute for the backup device to become the master device.
· Condition: This symptom occurs if the original master device is power cycled.
202205180548
· Symptom: Two identical rules exist in a security policy.
· Condition: This symptom occurs if the following operations are performed:
a. Reference an nonexistent DPI application profile in the rule, and create the DPI application profile.
b. Delete the rule.
· Recreate the rule.
Resolved problems in R9360P22
202111120378
· Symptom: A mobile phone with more than 11 digits cannot be entered for SMS authentication.
· Condition: This symptom occurs if the device is managed by an SDWAN controller.
202202250905
· Symptom: Only four users come online.
· Condition: This symptom occurs if the following operations are performed:
a. Enable and disable MAC authentication repeatedly.
b. Configure a RADIUS scheme with the maximum amount of configuration.
c. Send traffic with unknown source MAC addresses of 4000 users.
202112161429
· Symptom: Failed to send emails.
· Condition: This symptom occurs if the mail server address is configured as a domain name.
202202210546
· Symptom: The memory usage is high for the ntopd process.
· Condition: This symptom occurs if the following operations are performed:
a. Insert a hard disk.
b. Send many flows with different source and destination IP addresses.
c. Enable traffic logging and session statistics collection.
202201280915
· Symptom: The CLI PlugIn license Register Cmd Failed error message is displayed during an ISSU on an IRF active/standby fabric.
· Condition: This symptom occurs if the following operations are performed:
a. Perform an ISSU from D060SP18 to D060SP20.
b. Execute the issu run switchover command on the master device after the subordinate device is upgraded.
202112220320
· Symptom: The RBM connection fails to be established.
· Condition: This symptom occurs if you configure the dual-active mode for RBM and use an IPv6 address for the control channel.
202201050830
· Symptom: Hot backup is not supported for AFT.
· Condition: None.
Resolved problems in R9360P21
202110291292
· Symptom: The device reboots when it processes an abnormal IPv4 packet.
· Condition: This symptom might occur when the device processes abnormal IPv4 packets.
202111110695
· Symptom: The SSL VPN service with the 0x81d0049 memory tag leaks memory during SSL VPN login.
· Condition: This symptom occurs if you obtain verification codes repeatedly but do not log in.
202112310557
· Symptom: Core files are generated because the SSH process experiences exceptions.
· Condition: This symptom occurs when a system vulnerability scan is performed on the device.
202201040413
· Symptom: Nessus found the FTP Privileged Port Bounce Scan high-risk vulnerability.
· Condition: This symptom might occur if you use Nessus to scan the system for vulnerabilities when multiple protocols are enabled.
202201181541
· Symptom: IPsec traffic triggers the update of the input interface information of the session, and subsequent negotiation packets are dropped by ASPF.
· Condition: This symptom occurs if the following conditions exist:
¡ The IPsec tunnel is an IPsec NAT traversal tunnel.
¡ An interzone policy is configured allow traffic from the Untrust security zone to the Local security zone.
¡ No interzone policy is configured allow traffic from the Any security zone to the Local security zone.
¡ Inner IP addresses ping each other.
202201190694
· Symptom: NTP clock synchronization fails.
· Condition: This symptom occurs if NTP clock synchronization is configured.
Resolved problems in R9360P19
202107281498
· Symptom: Security policies containing object groups cannot work correctly after an IRF fabric is rebooted.
· Condition: This symptom occurs if the object groups contain domain names.
202105060373
· Symptom: In an IRF fabric, memory leaks occur on the subordinate device after the input interface of the forward flow is changed.
· Condition: This symptom occurs if you have enabled last hop holding and last hop backup.
202106211421
· Symptom: In an IRF fabric, IPsec SAs fail to be negotiated when there is a large number of IPsec SAs.
· Condition: This symptom occurs if a master/subordinate switchover is performed when there is traffic being forwarded.
202111251814
· Symptom: LDAP users and user groups failed to be imported.
· Condition: This symptom occurs if the SSL VPN function interoperates with LDAP.
202112010908
· Symptom: Duplicate excluded addresses exist.
· Condition: This symptom occurs if the following operations are performed:
a. Exclude an IPv4 address from an object group.
b. Rename the object group and remove the excluded IPv4 address from the object group.
c. Reconfigure the excluded IPv4 address.
Resolved problems in F9360P17
202108280160
· Symptom: The device reboots.
· Condition: This symptom occurs when the packet accessing the SSL VPN gateway carries the svnp_rewrite_code field.
202107220778
· Symptom: Memory leaks occur.
· Condition: This symptom occurs if you enable auto refresh and real-time traffic data collection for the Real-time user ranking and Real-time application ranking widgets from the Web interface.
202107151060
· Symptom: Memory leaks occur for ntopd.
· Condition: This symptom occurs if log aggregation is enabled from the Web interface and the device receives traffic.
202109020467
· Symptom: The device reboots after you execute the session persistent acl 3000 aging-time 0 command and its undo form repeatedly.
· Condition: This symptom occurs if you execute the session persistent acl 3000 aging-time 0 command and its undo form repeatedly.
202109220429
· Symptom: A security policy cannot be moved after another security policy.
· Condition: None.
202110080402
· Symptom: Traffic rate statistics about IPsec tunnels are not supported.
· Condition: None.
Resolved problems in F9360P1212
202107090909
· Symptom: The web https-authorization username command is lost after the binary configuration file recovers, and the Web interface cannot be accessed.
· Condition: This symptom occurs if a certificate is used to log in to the Web interface.
202107220895
· Symptom: Memory leaks occur.
· Condition: This symptom occurs if you enable auto refresh and real-time traffic data collection for the Real-time user ranking and Real-time application ranking widgets from the Web interface.
202107151103
· Symptom: Memory leaks occur for ntopd.
· Condition: This symptom occurs if log aggregation is enabled from the Web interface and the device receives traffic.
Resolved problems in F9360P10
None.
Resolved problems in F9360P07
None.
Resolved problems in F9360P05
None.
Resolved problems in F9360P0301
None.
Resolved problems in F9345P18
202008040820
· Symptom: The iNode can be connected. However, the iNode has no address or mask assigned and cannot access resources.
· Condition: This symptom occurs if the fixed IP address assigned by iMC is a broadcast address and the device does not check it.
Resolved problems in F9345P16
202006041012
· Symptom: The object groups are hung, and the device gets stuck when performing object group-related operations.
· Condition: This symptom occurs if you configure object groups with the same fuzzy domain name and delete the first object group.
Resolved problems in R9345P14
202003230027
· Symptom: A GE fiber port cannot be autosensed to a 100 Mbps port.
· Condition: This symptom occurs when a 100 Mbps transceiver module is installed in the GE fiber port.
202003030643
· Symptom: The device reboots unexpectedly.
· Condition: This symptom occurs when the DPI module processes abnormal SIP packets.
201911160236
· Symptom: An error message appears, asking you to examine the email server configuration when Set random password is selected for a local user account.
· Condition: This symptom occurs if the following conditions are met:
a. smtp.163.com or smtp.mxhichina.com is specified as the email server address.
b. Set random password is selected on the local user account configuration page.
c. The recipient mail address is specified and OK is clicked.
202003170454
· Symptom: A GE fiber port cannot autosense to operate at 100 Mbps.
· Condition: This symptom occurs if an FE transceiver module is inserted to a GE fiber port.
Resolved problems in F9345P11
201912040612
· Symptom: License registration fails when the F1030/F1050 registers a license of a high-end firewall.
· Condition: This symptom occurs when the F1030/F1050 registers a license of a high-end firewall.
Resolved problems in E9345P08
Resolved problems in E9345P05
None.
Resolved problems in E9345P02
201903020216
· Symptom: SCTP traffic cannot be forwarded in an IRF fabric.
· Condition: This symptom might occur if original packets and the return packets are processed by different member devices in the IRF fabric.
201809180736
· Symptom: The device that acts as an SSL proxy might reboot unexpectedly when processing multiple types of traffic.
· Condition: This symptom might occur if the device acts as an SSL proxy and processes multiple types of traffic.
Resolved problems in E9340
None.
Resolved problems in E9333P10
None.
Related documentation
· H3C SecPath F10X0 Firewall Series Installation Quick Start
· H3C SecPath F10X0 Firewall Series Installation Guide
· H3C SecPath F1020[F1030][F1050][F1060][F1070][F1080] Firewall Compliance and Safety Manual-6PW100
· H3C SecPath Firewall Command References(V7)-6W600
· H3C SecPath Firewall Configuration Guides(V7)-6W600
Technical support
To obtain the related documents from the H3C website at http://www.h3c.com/en/:
1. Click http://www.h3c.com/en/Support/.
2. Choose the desired product category and model.
Technical support
http://www.h3c.com/en/
Item | Specifications |
Ports | · 1 × console port · 2 × USB host ports · 16 × GE copper ports · 8 × GE fiber ports |
Expansion slots | · F1020/F1000-AK130/F1020-GM: One expansion slot, supporting 4SFP and 4PFC modules · F100-A-G2/F100-A-EI: One expansion slot, supporting 4SFP and 4PFC modules · F1030/F1050/F1000-AK150/F1000-AK140/F1060/F1000-AK160/F1000-AK170//F1030-GM: Two expansion slots, supporting 4SFP and 4PFC modules · F100-E-EI/F100-E-G2/F1000-C-G2/F1000-C8160/F1000-C8170: Two expansion slots, supporting 4SFP and 4PFC modules |
Hard disk slots | One hard disk slot that supports a SATA hard disk. |
Memory | · F1020/F100-A-G2/F1000-AK130/F100-A-EI/F1020-GM: 2GB DDR3 SDRAM · F1030/F1050/F1000-AK150/F1000-AK140/F100-E-EI/F100-E-G2/F1000-C8160/F1030-GM: 4GB DDR3 SDRAM · F1060/F1000-C-G2/F1000-AK160/F1000-AK170/F1000-C8170: 8GB DDR3 SDRAM |
Flash | · NOR flash: 8 MB · NAND flash: 1 GB |
Power modules | One built-in power module for F100-A-G2. Two built-in 100W AC power modules for other models. |
Dimensions (H × W × D) | 44.2 × 440 × 435 mm (1.74 × 17.32 × 17.13 in) |
Operating temperature | · Operating: 0°C to 45°C (32°F to 113°F) · Storage: –40°C to 70°C (–40°F to 158°F) |
Relative humidity | · Operating: ¡ Without hard disks: 5% RH to 95% RH, noncondensing ¡ With hard disks: 10% RH to 90% RH, noncondensing · Storage: 5% RH to 95% RH, noncondensing |
Table 7 Hardware specifications for F1070/F1080/F1000-AK180/F1000-C8180/F1070-GM/F1070-GM-L
Item | Specifications |
Ports | · 1 × console port · 2 × USB host ports · 16 × GE copper ports · 8 × GE fiber ports · 2 × 10-GE fiber ports |
Expansion slots | · F1070/F1080/F1000-AK-180/F1070-GM/F1070-GM-L: Two expansion slots, supporting 4SFP and 4PFC modules · F1000-C8180: Two expansion slots, supporting 4SFP and 4PFC modules |
Network data encryption module | · F1070-GM: Provided with one NSQM1F1KGM0 · F1070-GM-L: Provided with one NSQM1F1KGMC |
Hard disk slots | Two hard disk slots that support SATA hard disks. |
Memory | · F1070/F1070-GM/F1070-GM-L: 8GB DDR3 VLP RDIMM · F1080/F1000-C8180: 16GB DDR3 VLP RDIMM |
Flash | · NOR flash: 8 MB · NAND flash: 1 GB |
Power module slots | 2, supporting AC and DC power modules |
Dimensions (H × W × D) | 44.2 × 440 × 435 mm (1.74 × 17.32 × 17.13 in) |
Operating temperature | · Operating: 0°C to 45°C (32°F to 113°F) · Storage: –40°C to 70°C (–40°F to 158°F) |
Relative humidity | · Operating: ¡ Without hard disks: 5% RH to 95% RH, noncondensing ¡ With hard disks: 10% RH to 90% RH, noncondensing · Storage: 5% RH to 95% RH, noncondensing |
Table 8 Hardware specifications for F1000-AI-50/F1000-AI-30/F1000-AI-20
Item | Specifications |
Ports | · 1 × console port · 2 × USB host ports · 16 × GE copper ports (including one management Ethernet port) · 15 × GE copper ports · 8 × GE fiber ports |
Expansion slots | Two expansion slots, supporting 4SFP and 4PFC modules |
Hard disk slots | Two hard disk slots that support SATA hard disks |
Memory | · F1000-AI-50/F1000-AI-30: 4GB DDR3 VLP RDIMM · F1000-AI-20: 2GB DDR3 VLP RDIMM |
Flash | · NOR flash: 8 MB · Nand flash: 1 GB |
Power module slots | 2, supporting AC and DC power modules |
Dimensions (H × W × D) | 44.2 × 440 × 435 mm (1.74 × 17.32 × 17.13 in) |
Operating temperature | · Operating: 0°C to 45°C (32°F to 113°F) · Storage: –40°C to 70°C (–40°F to 158°F) |
Relative humidity | · Operating: ¡ Without hard disks: 5% RH to 95% RH, noncondensing ¡ With hard disks: 10% RH to 90% RH, noncondensing · Storage: 5% RH to 95% RH, noncondensing |
Table 9 Hardware specifications for F1000-990-AI/F1000-980-AI/F1000-970-AI/F1000-960-AI/F1000-950-AI/F1000-930-AI/F1000-920-AI
Item | Specifications |
Ports | · 1 × console port · 2 × USB host ports · 16 × GE copper ports (including one management Ethernet port) · 8 × GE fiber ports · 2 × 10-GE ports (available only on the F1000-990-AI/F1000-980-AI) |
Expansion slots | · F1000-920-AI: One expansion slot, supporting 4SFP and 4PFC modules · F1000-990-AI/F1000-980-AI/F1000-970-AI/F1000-960-AI/F1000-950-AI/F1000-930-AI: Two expansion slots, supporting 4SFP and 4PFC modules |
Hard disk slots | · F1000-970-AI/F1000-960-AI/F1000-950-AI/F1000-930-AI/F1000-920-AI: One hard disk slot, supporting SATA hard disks · F1000-990-AI/F1000-980-AI: Two hard disk slots, supporting SATA hard disks |
Memory | · F1000-920-AI: 2GB DDR3 SDRAM · F1000-930-AI/ F1000-950-AI/ F1000-960-AI: 4GB DDR3 SDRAM · F1000-970-AI/ F1000-980-AI: 8GB DDR3 SDRAM · F1000-990-AI: 16GB DDR3 SDRAM |
Flash | · NOR flash: 8 MB · Nand flash: 1 GB |
Power module slots | · F1000-970-AI/F1000-960-AI/F1000-950-AI/F1000-930-AI/F1000-920-AI: Two built-in 100W AC power modules · F1000-990-AI/F1000-980-AI: Two power modules slots, supporting AC and DC power modules |
Dimensions (H × W × D) | 44.2 × 440 × 435 mm (1.74 × 17.32 × 17.13 in) |
Operating temperature | · Operating: 0°C to 45°C (32°F to 113°F) · Storage: –40°C to 70°C (–40°F to 158°F) |
Relative humidity | · Operating: ¡ Without hard disks: 5% RH to 95% RH, noncondensing ¡ With hard disks: 10% RH to 90% RH, noncondensing · Storage: 5% RH to 95% RH, noncondensing |
Table 10 Firewall software features
Category | Features | |
AAA | RADIUS/HWTACACS+ authentication. CHAP authentication. PAP authentication. Domain authentication. | |
Firewall | Packet filtering. Security zone-based access control. Time-based access control. ASPF. Control of ICMP redirection and destination unreachable messages. Tracert message control. Control of IP packets with the RR option. | |
Security management | Real-time attack protection logs. Blacklist logs. Session logs. Binary logs. Traffic statistic collection and analysis. Security event statistics. | |
NAT | NAT support for address pools. Easy IP. NAT server. Effective period of NAT. NAT ALGs, including FTP, DNS, QQ, MSN, H323, NBT, ILS, RTSP, SQLNET, SIP, RSH, and MGCP. NAT444. | |
Application recognition | APR signature library. PBAR. NBAR. Application group. | |
Bandwidth management | Traffic profile. Traffic policy. Interface bandwidth limit. Reports and logs. | |
IPS | IPS policy. IPS working mode. IPS signature. IPS signature action. Reports and logs. | |
IPSec/IKE | AH and ESP. Manual SA setup and IKE SA setup. ESP support for DES, 3DES, and AES encryption algorithms. Support for MD5 and SHA-1 authentication algorithms. Support for IKE main mode and aggressive mode. DPD. NAT traversal. | |
L2TP | L2TP. | |
GRE | GRE tunnel. | |
SSL VPN | IP access. TCP access. Smart terminal access. User authentication. | |
LAN | Ethernet_II. VLAN. | |
IP services | ARP. Static domain name resolution. IP address borrowing. DHCP relay. DHCP server. DHCP client. | |
IP routing | Static route management. RIP-1/RIP-2. OSPF. BGP. Routing policy. PBR. | |
Basic IPv6 protocols. | Protocol processing. Ethernet link layer. ICMPv6. IPv6 address management. PMTU. Socket. TCP6. UDP6. RAWIP6. Ping6. DNS6. Tracert6. Telnet6. FIB6. DHCPv6 client. DHCPv6 relay. | |
IPv6 routing and multicast | RIPng. OSPFv3. BGP4+. Static routes. PBR. PIM-SM. PIM-DM. | |
IPv6 security | NAT-PT. IPv6 packet filtering. RADIUS. | |
VRRP | VRRP. | |
Hot backup | Session hot backup for asymmetric traffic. | |
IRF | Unified IRF management. | |
Hot backup | Session hot backup. Configuration synchronization. | |
CLI | Local configuration through a console port. Local or remote configuration through Telnet or SSH. Control of user access to commands. Debugging. Network diagnostic tools, including tracert and ping. Telnetting from the device to other devices. FTP server/client, and file and application upload and download. TFTP file transmission. Logging. File system management. User line configuration. | |
Network management | Support for SNMPv3 and compatibility with SNMPv2C and SNMPv1. NTP time synchronization. | |
Appendix B List of severe vulnerabilities
Severe vulnerabilities in R9360P27 and earlier versions
[HSVD-201709-002] CVE-2017-3735
An attacker can exploit this vulnerability to bypass security protections and execute unauthorized operations.
[HSVD-201903-017] CVE-2019-3855
An integer overflow flaw which could lead to an out of bounds write was discovered in libssh2 in the way packets are read from the server. libssh2 is a client-side C library implementing the SSH2 protocol. A remote attacker who compromises an SSH server may be able to execute code on the client system when a user connects to the server.
HSVD-201904-001
TCP/IP SYN + FIN packet filtering vulnerability: A remote host does not discard TCP SYN packets with the FIN flag set. An attacker might bypass the firewall, depending on the type of firewall used.
HSVD-201902-001
A remote host can exploit the TCP timestamp vulnerability to obtain the online time.
[HSVD-201901-016] CVE-2019-0548
A Linux kernel vulnerability that can cause information revealing.
JavaScript library vulnerability
Internal IP addresses in destination URLs might be revealed.
CVE-2020-10188
utility.c in telnetd in netkit telnet through 0.17 allows remote attackers to execute arbitrary code via short writes or urgent data, because of a buffer overflow involving the netclear and nextitem functions.
Web JavaScript vulnerability
A medium-risk vulnerability found during Web vulnerability scanning.
Web CSRF vulnerability
An CSRF vulnerability was found on the SSL VPN Web login interface.
HTTP method vulnerability
An attacker can use the OPTIONS method to determine the HTTP methods allowed by each directory.
CRLF injection vulnerability
This vulnerability can be exploited when an HTTP request contains a user-configured domain in the cookies or the request is GET /enterdomain.cgi?domain=%0d%0aSomeCustomInjectedHeader:%0d%0aset-cookie:iamyy HTTP1/1.
[CNVD-2019-38485] CVE-2019-1547
An attacker can exploit this vulnerability to obtain sensitive information.
[CNVD-2019-38486] CVE-2019-1563
An attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key
[CNVD-2017-00450] CVE-2016-7056
A timing attack flaw was found in OpenSSL 1.0.1u and before that could allow a malicious user with local access to recover ECDSA P-256 private keys.
[CNVD-2018-06539] CVE-2018-0739
Constructed ASN.1 types with a recursive definition (such as can be found in PKCS7) could eventually exceed the stack given malicious input with excessive recursion. This could result in a Denial Of Service attack.
[CNVD-2019-05906] CVE-2019-1559
An attacker can exploit this vulnerability to bypass access controls and obtain sensitive information.
[CNVD-2018-09649] CVE-2018-0737
An attacker with sufficient access to mount cache timing attacks during the RSA key generation process could recover the private key.
[CNVD-2018-12153] CVE-2018-0732
An attacker can exploit this vulnerability to launch a DoS attack.
[CNVD-2019-27331] CVE-2019-1552
This vulnerability is related to OpenSSL. An attacker can exploit this vulnerability to bypass security controls.
[CNVD-2019-38486] CVE-2019-1563
An attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key.
CVE-2018-5407
This vulnerability is related to OpenSSL. An attacker can exploit this vulnerability to obtain sensitive information and launch more attacks.
X-Frame-Options vulnerability
A missing X-Frame-Options header can cause a clickjacking attack.
CVE-2011-1473
SSL in the kernel does not process the field for disabling SSL renegotiation. As a result, an SSL client can renegotiate successfully.
CVE-2021-23841/CVE-2021-23840/CVE-2020-1971
This vulnerability is related to OpenSSL. The X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp that compares different instances of a GENERAL_NAME to see if they are equal or not. This function behaves incorrectly and NULL pointer dereference might occur when both GENERAL_NAMEs contain an EDIPARTYNAME.
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, Web interface, and BootWare menus. The default storage medium varies by device model. This chapter uses the CF card 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
· Upgrading system software from BootWare menus
To upgrade the BootWare, use either of the following methods:
· Upgrading the BootWare from the CLI
· Upgrading BootWare from BootWare menus
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:
· Set up the upgrade environment as shown in Figure 1. The IP address and subnet mask of the PC are 192.168.0.2 and 255.255.255.0, respectively.
· 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.
Figure 1 Setting up the upgrade environment
This configuration example upgrades system software from R8513 to R8514. The system software image file name is main.ipe.
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
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
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)[cfa0:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):
cfa0:/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 CF card has sufficient space for the new system software image.
<Sysname> dir
Directory of cfa0:
0 -rw- 4269 Jul 12 2018 13:34:36 + attachmentname + .ak
1 -rw- 5723136 Oct 24 2018 13:03:16 boot_backup.bin
2 drw- - Sep 26 2018 15:21:36 diagfile
3 drw- - Sep 14 2018 08:04:50 dpi
4 -rw- 5723136 Oct 23 2018 16:52:51 main-cmw710-boot-R8513.bin
5 -rw- 137090048 Oct 23 2018 16:58:19 main-cmw710-system-R8513.bin
6 -rw- 735 Sep 13 2018 19:16:22 hostkey
7 -rw- 730 Oct 23 2018 16:58:50 ifindex.dat
8 drw- - Jul 12 2018 13:34:36 license
9 drw- - Sep 13 2018 18:29:20 logfile
10 drw- - Sep 13 2018 19:16:24 pki
11 drw- - Sep 13 2018 18:33:24 seclog
12 -rw- 591 Sep 13 2018 19:16:24 serverkey
13 -rw- 5109 Oct 23 2018 16:58:50 startup.cfg
14 -rw- 134782 Oct 23 2018 16:58:51 startup.mdb
15 -rw- 137090048 Oct 24 2018 13:11:57 system_backup.bin
16 drw- - Oct 23 2018 17:04:21 versionInfo
4088468 KB total (3972960 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
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
2. Upgrade the system software:
a. Execute the tftp get command in user view to download the system software image file to the CF card on the device.
<Sysname> tftp 192.168.0.2 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.
<Sysname>
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 T5020 images in IPE:
main-cmw710-boot-R8514.bin
main-cmw710-system-R8514.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-R8514.bin already exists on slot 1.
File cfa0:/main-cmw710-system-R8514.bin already exists on slot 1.
Overwrite the existing files? [Y/N]:y
Decompressing file main-cmw710-boot-R8514.bin to cfa0:/main-cmw710-boot-R8514.bin..........Done.
Decompressing file main-cmw710-system-R8514.bin to cfa0:/main-cmw710-system-R8514.bin............................................................................................................................................................................Done.
Verifying the file cfa0:/main-cmw710-boot-R8514.bin on slot 1...Done.
Verifying the file cfa0:/main-cmw710-system-R8514.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 cfa0:/main.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:
cfa0:/main-cmw710-boot-R8513.bin
cfa0:/main-cmw710-system-R8513.bin
Main startup software images:
cfa0:/main-cmw710-boot-R8514.bin
cfa0:/main-cmw710-system-R8514.bin
Backup startup software images:
cfa0:/boot_backup.bin
cfa0:/system_backup.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!
This command will reboot the device. Continue? [Y/N]:y
System is starting...
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 8514
Copyright (c) 2004-2018 New H3C Technologies Co., Ltd. All rights reserved.
H3C SecPath T5020 uptime is 0 weeks, 2 days, 5 hours, 53 minutes
Last reboot reason: User reboot
Boot image: cfa0:/main-cmw710-boot-R8514.bin
Boot image version: 7.1.064, Release 8514
Compiled Sep 18 2018 15:00:00
System image: cfa0:/main-cmw710-system-R8514.bin
System image version: 7.1.064, Release 8514
Compiled Sep 18 2018 15:00:00
SLOT 1
Uptime is 0 weeks, 2 days, 5 hours, 53 minutes
CPU type: Multi-core CPU
DDR3 SDRAM Memory 32766M bytes
CF0 Card 4002M bytes
Board PCB Version:Ver.A
CPLD_A Version: 1.0
CPLD_B Version: 2.0
Release Version:SecPath T5020-8514
Basic BootWare Version: 2.04
Extend BootWare Version: 2.04
<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)[cfa0:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):
cfa0:/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 CF card has sufficient space for the new system software image.
<Sysname> dir
Directory of cfa0:
0 -rw- 4269 Jul 12 2018 13:34:36 + attachmentname + .ak
1 -rw- 5723136 Oct 24 2018 13:03:16 boot_backup.bin
2 drw- - Sep 26 2018 15:21:36 diagfile
3 drw- - Sep 14 2018 08:04:50 dpi
4 -rw- 5723136 Oct 23 2018 16:52:51 main-cmw710-boot-R8513.bin
5 -rw- 137090048 Oct 23 2018 16:58:19 main-cmw710-system-R8513.bin
6 -rw- 735 Sep 13 2018 19:16:22 hostkey
7 -rw- 730 Oct 23 2018 16:58:50 ifindex.dat
8 drw- - Jul 12 2018 13:34:36 license
9 drw- - Sep 13 2018 18:29:20 logfile
10 drw- - Sep 13 2018 19:16:24 pki
11 drw- - Sep 13 2018 18:33:24 seclog
12 -rw- 591 Sep 13 2018 19:16:24 serverkey
13 -rw- 5109 Oct 23 2018 16:58:50 startup.cfg
14 -rw- 134782 Oct 23 2018 16:58:51 startup.mdb
15 -rw- 137090048 Oct 24 2018 13:11:57 system_backup.bin
16 drw- - Oct 23 2018 17:04:21 versionInfo
4088468 KB total (3972960 KB free)
<Sysname>
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>
2. Upgrade the system software:
a. Execute the get command in FTP client view to download the system software image file to the CF card 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
<Sysname>
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 T5020 images in IPE:
main-cmw710-boot-R8514.bin
main-cmw710-system-R8514.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-R8514.bin already exists on slot 1.
File cfa0:/main-cmw710-system-R8514.bin already exists on slot 1.
Overwrite the existing files? [Y/N]:y
Decompressing file main-cmw710-boot-R8514.bin to cfa0:/main-cmw710-boot-R8514.bin..........Done.
Decompressing file main-cmw710-system-R8514.bin to cfa0:/main-cmw710-system-R8514.bin............................................................................................................................................................................Done.
Verifying the file cfa0:/main-cmw710-boot-R8514.bin on slot 1...Done.
Verifying the file cfa0:/main-cmw710-system-R8514.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 cfa0:/main.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 2:
Current software images:
cfa0:/main-cmw710-boot-R8513.bin
cfa0:/main-cmw710-system-R8513.bin
Main startup software images:
cfa0:/main-cmw710-boot-R8514.bin
cfa0:/main-cmw710-system-R8514.bin
Backup startup software images:
cfa0:/boot_backup.bin
cfa0:/system_backup.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!
This command will reboot the device. Continue? [Y/N]:y
System is starting...
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 8514
Copyright (c) 2004-2018 New H3C Technologies Co., Ltd. All rights reserved.
H3C SecPath T5020 uptime is 0 weeks, 2 days, 5 hours, 53 minutes
Last reboot reason: User reboot
Boot image: cfa0:/main-cmw710-boot-R8514.bin
Boot image version: 7.1.064, Release 8514
Compiled Sep 18 2018 15:00:00
System image: cfa0:/main-cmw710-system-R8514.bin
System image version: 7.1.064, Release 8514
Compiled Sep 18 2018 15:00:00
SLOT 1
Uptime is 0 weeks, 2 days, 5 hours, 53 minutes
CPU type: Multi-core CPU
DDR3 SDRAM Memory 32766M bytes
CF0 Card 4002M bytes
Board PCB Version:Ver.A
CPLD_A Version: 1.0
CPLD_B Version: 2.0
Release Version:SecPath T5020-8514
Basic BootWare Version: 2.04
Extend BootWare Version: 2.04
<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 11 describes the default settings for you to log in to the Web interface.
Table 11 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:
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 192.168.0.2 to the PC.
5. Launch the Web browser, and enter 192.168.0.1 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.
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
Upgrading system software from BootWare menus
To upgrade Comware images from BootWare menus, use one of the following methods:
· Using TFTP to upgrade system software through the management Ethernet port
· Using FTP to upgrade system software through the management Ethernet port
Preparing for the upgrade
1. Connect the configuration terminal to the MPU's console port.
2. Connect the MPU's management Ethernet port to the TFTP or FTP file server.
The TFTP or FTP server can be co-located with the configuration terminal (typically, a PC).
3. Prepare the upgrade file:
¡ If you are using TFTP, store the upgrade file on the TFTP server, and specify the directory.
¡ If you are using FTP, store the upgrade file on the FTP server, and specify the directory, FTP username, and password.
4. Run the terminal emulation program on the configuration terminal.
5. Power on the device, and then press Ctrl+B within 5 seconds at prompt to access the EXTEND-BOOTWARE menu (see "Using the EXTENDED-BOOTWARE menu").
Using TFTP to upgrade system software through the management Ethernet port
1. Enter 3 in the EXTEND-BOOTWARE menu to access the Ethernet submenu.
==========================<Enter Ethernet SubMenu>==========================
|Note:the operating device is sda0 |
|<1> Download Image Program To SDRAM And Run |
|<2> Update Main Image File |
|<3> Update Backup Image File |
|<4> Download Files(*.*) |
|<5> Modify Ethernet Parameter |
|<0> Exit To Main Menu |
|<Ensure The Parameter Be Modified Before Downloading!> |
============================================================================
Enter your choice(0-5):
2. Enter 5 in the Ethernet submenu to configure the network settings.
| NOTE: To use the existing setting for a field, press Enter without modifying the setting. |
======================<ETHERNET PARAMETER SET>==============================
|Note: '.' = Clear field. |
| '-' = Go to previous field. |
| Ctrl+D = Quit. |
============================================================================
Protocol (FTP or TFTP):tftp
Load File Name :main.ipe
Target File Name :main.ipe
Server IP Address :192.168.0.2
Local IP Address :192.168.0.1
Subnet Mask :255.255.255.0
Gateway IP Address :0.0.0.0
Table 12 Network parameter fields and shortcut keys
Field | Description |
'.' = Clear field | Press a dot (.) and then press Enter to clear the setting for a field. |
'-' = Go to previous field | Press a hyphen (-) and then press Enter to return to the previous field. |
Ctrl+D = Quit | Press Ctrl+D to exit the ETHERNET PARAMETER SET menu. |
Protocol (FTP or TFTP) | Set the file transfer protocol to TFTP. |
Load File Name | Set the name of the file to be downloaded. |
Target File Name | Set a file name for saving the file on the device. The target file name must have the same extension as the source file. By default, the target file name is the same as the source file name. |
Server IP Address | Set the IP address of the TFTP server. |
Local IP Address | Set the IP address of the Ethernet interface that connects to the TFTP server. |
Subnet Mask | Set the IP address mask. |
Gateway IP Address | Set a gateway IP address if the device is on a different network than the server. |
After you finish setting the TFTP parameters, the system returns to the Ethernet submenu.
==========================<Enter Ethernet SubMenu>==========================
|Note:the operating device is sda0 |
|<1> Download Image Program To SDRAM And Run |
|<2> Update Main Image File |
|<3> Update Backup Image File |
|<4> Download Files(*.*) |
|<5> Modify Ethernet Parameter |
|<0> Exit To Main Menu |
|<Ensure The Parameter Be Modified Before Downloading!> |
============================================================================
Enter your choice(0-5):
3. Enter 2 or 3 in the Ethernet submenu to upgrade the main or backup software images. For example, enter 2 to upgrade the main software images.
Loading.....................................................................
............................................................................
.........................Done!
94786560 bytes downloaded!
Image file main-cmw710-boot-A9615.bin is self-decompressing...
Saving file sda0:/main-cmw710-boot-A9615.bin ......Done.
Image file main-cmw710-system-A9615.bin is self-decompressing...
Saving file sda0:/main-cmw710-system-A9615.bin .......................
............................................................................
..................Done. .
==========================<Enter Ethernet SubMenu>==========================
|Note:the operating device is sda0 |
|<1> Download Image Program To SDRAM And Run |
|<2> Update Main Image File |
|<3> Update Backup Image File |
|<4> Download Files(*.*) |
|<5> Modify Ethernet Parameter |
|<0> Exit To Main Menu |
|<Ensure The Parameter Be Modified Before Downloading!> |
============================================================================
Enter your choice(0-5):
4. Enter 0 in the Ethernet submenu to return to the EXTEND-BOOTWARE menu.
5. Enter 1 in the EXTEND-BOOTWARE menu to run the new Comware images.
Using FTP to upgrade system software through the management Ethernet port
1. Enter 3 in the EXTEND-BOOTWARE menu to access the Ethernet submenu.
==========================<Enter Ethernet SubMenu>==========================
|Note:the operating device is sda0 |
|<1> Download Image Program To SDRAM And Run |
|<2> Update Main Image File |
|<3> Update Backup Image File |
|<4> Download Files(*.*) |
|<5> Modify Ethernet Parameter |
|<0> Exit To Main Menu |
|<Ensure The Parameter Be Modified Before Downloading!> |
============================================================================
Enter your choice(0-5):
2. Enter 5 in the Ethernet submenu to configure the network settings.
| NOTE: To use the existing setting for a field, press Enter without modifying the setting. |
======================<ETHERNET PARAMETER SET>==============================
|Note: '.' = Clear field. |
| '-' = Go to previous field. |
| Ctrl+D = Quit. |
============================================================================
Protocol (FTP or TFTP):ftp
Load File Name :main.ipe
Target File Name :main.ipe
Server IP Address :192.168.0.2
Local IP Address :192.168.0.1
Subnet Mask :255.255.255.0
Gateway IP Address :0.0.0.0
FTP User Name :admin
FTP User Password :******
Table 13 Network parameter fields and shortcut keys
Field | Description |
'.' = Clear field | Press a dot (.) and then press Enter to clear the setting for a field. |
'-' = Go to previous field | Press a hyphen (-) and then press Enter to return to the previous field. |
Ctrl+D = Quit | Press Ctrl+D to exit the ETHERNET PARAMETER SET menu. |
Protocol (FTP or TFTP) | Set the file transfer protocol to FTP. |
Load File Name | Set the name of the file to be downloaded. |
Target File Name | Set a file name for saving the file on the device. The target file name must have the same extension as the source file. By default, the target file name is the same as the source file name. |
Server IP Address | Set the IP address of the FTP or TFTP server. |
Local IP Address | Set the IP address of the Ethernet interface that connects to the TFTP or FTP server. |
Subnet Mask | Set the IP address mask. |
Gateway IP Address | Set a gateway IP address if the device is on a different network than the server. |
FTP User Name | Set the username for accessing the FTP server. This username must be the same as the username configured on the FTP server. |
FTP User Password | Set the password for accessing the FTP server. This password must be the same as the password configured on the FTP server. |
After you finish setting the FTP parameters, the system returns to the Ethernet submenu.
==========================<Enter Ethernet SubMenu>==========================
|Note:the operating device is sda0 |
|<1> Download Image Program To SDRAM And Run |
|<2> Update Main Image File |
|<3> Update Backup Image File |
|<4> Download Files(*.*) |
|<5> Modify Ethernet Parameter |
|<0> Exit To Main Menu |
|<Ensure The Parameter Be Modified Before Downloading!> |
============================================================================
Enter your choice(0-5):
3. Enter 2 or 3 in the Ethernet submenu to upgrade the main or backup software images. For example, enter 2 to upgrade the main software images.
Loading.....................................................................
............................................................................
.........................Done!
94786560 bytes downloaded!
Image file main-cmw710-boot-A9615.bin is self-decompressing...
Saving file sda0:/main-cmw710-boot-A9615.bin ......Done.
Image file main-cmw710-system-A9615.bin is self-decompressing...
Saving file sda0:/main-cmw710-system-A9615.bin .......................
............................................................................
..................Done.
==========================<Enter Ethernet SubMenu>==========================
|Note:the operating device is sda0 |
|<1> Download Image Program To SDRAM And Run |
|<2> Update Main Image File |
|<3> Update Backup Image File |
|<4> Download Files(*.*) |
|<5> Modify Ethernet Parameter |
|<0> Exit To Main Menu |
|<Ensure The Parameter Be Modified Before Downloading!> |
============================================================================
Enter your choice(0-5):
4. Enter 0 in the Ethernet submenu to return to the EXTEND-BOOTWARE menu.
5. Enter 1 in the EXTEND-BOOTWARE menu to run the new system software.
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:
6. Use FTP or TFTP to download or upload the new BootWare image file to the root directory of the storage medium on the device.
7. Execute the bootrom update command to upgrade the BootWare.
<System> bootrom update file 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!
<System>
8. Execute the reboot command to reboot the device.
Upgrading BootWare from BootWare menus
To upgrade the BootWare image from BootWare menus, use one of the following methods:
· Using TFTP to upgrade BootWare through the management Ethernet port
· Using FTP to upgrade BootWare through the management Ethernet port
For more information about BootWare menus, see "Using BootWare menus."
| NOTE: This section uses the MPU as an example to describe how to upgrade BootWare. |
Preparing for the upgrade
1. Connect the MPU's console port to the configuration terminal.
2. Connect the MPU's management Ethernet port to the TFTP or FTP file server.
The TFTP or FTP server can be co-located with the configuration terminal (typically, a PC).
3. Prepare the upgrade file:
¡ If you are using TFTP, store the upgrade file on the TFTP server, and specify the file directory.
¡ If you are using FTP, store the upgrade file on the FTP server, and specify the file directory, FTP username, and password.
4. Run the terminal emulation program on the configuration terminal.
5. Power on the device, and then press Ctrl+B within 5 seconds at prompt to access the EXTEND-BOOTWARE menu (see "Using the EXTENDED-BOOTWARE menu").
Using TFTP to upgrade BootWare through the management Ethernet port
1. Enter 7 in the BootWare menu to access the BootWare Operation submenu.
=========================<BootWare Operation Menu>==========================
|Note:the operating device is sda0 |
|<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):
2. Enter 4 in the BootWare Operation submenu to enter the Ethernet submenu.
===================<BOOTWARE OPERATION ETHERNET SUB-MENU>===================
|<1> Update Full BootWare |
|<2> Update Extended BootWare |
|<3> Update Basic BootWare |
|<4> Modify Ethernet Parameter |
|<0> Exit To Main Menu |
============================================================================
Enter your choice(0-4):
3. Enter 4 in the Ethernet submenu to configure the network settings.
| NOTE: To use the existing setting for a field, press Enter without modifying the setting. |
==========================<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
Subnet Mask :255.255.255.0
Gateway IP Address :0.0.0.0
For more information about the fields, see Table 12.
After you finish setting the TFTP parameters, the system returns to the BOOTWARE OPERATION ETHERNET submenu.
===================<BOOTWARE OPERATION ETHERNET SUB-MENU>===================
|<1> Update Full BootWare |
|<2> Update Extended BootWare |
|<3> Update Basic BootWare |
|<4> Modify Ethernet Parameter |
|<0> Exit To Main Menu |
============================================================================
Enter your choice(0-4):
4. Choose an option from options 1 to 3. For example, enter 1 to upgrade the entire BootWare image.
Loading..............Done.
64245 bytes downloaded!
Updating Basic BootWare? [Y/N]
5. Enter Y to upgrade the basic BootWare segment.
Updating Basic BootWare........Done.
Updating Extended BootWare? [Y/N]
6. Enter Y to upgrade the extended BootWare segment.
Updating Extended BootWare.........Done!
===================<BOOTWARE OPERATION ETHERNET SUB-MENU>===================
|<1> Update Full BootWare |
|<2> Update Extended BootWare |
|<3> Update Basic BootWare |
|<4> Modify Ethernet Parameter |
|<0> Exit To Main Menu |
============================================================================
Enter your choice(0-4):
7. Enter 0 to return to the BootWare Operation menu.
8. Enter 0 in the BootWare Operation menu to return to the EXTEND-BOOTWARE menu.
9. Enter 0 in the EXTEND-BOOTWARE menu to reboot the system.
Using FTP to upgrade BootWare through the management Ethernet port
1. Enter 7 in the BootWare menu to access the BootWare Operation submenu.
=========================<BootWare Operation Menu>==========================
|Note:the operating device is sda0 |
|<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):
2. Enter 4 in the BootWare Operation submenu to enter the Ethernet submenu.
===================<BOOTWARE OPERATION ETHERNET SUB-MENU>===================
|<1> Update Full BootWare |
|<2> Update Extended BootWare |
|<3> Update Basic BootWare |
|<4> Modify Ethernet Parameter |
|<0> Exit To Main Menu |
============================================================================
Enter your choice(0-4):
3. Enter 4 in the Ethernet submenu to configure the network settings.
| NOTE: To use the existing setting for a field, press Enter without modifying the setting. |
==========================<ETHERNET PARAMETER SET>==========================
|Note: '.' = Clear field. |
| '-' = Go to previous field. |
| Ctrl+D = Quit. |
============================================================================
Protocol (FTP or TFTP) :ftp
Load File Name :Main.btw
:
Target File Name :Main.btw
:
Server IP Address :192.168.0.2
Local IP Address :192.168.0.1
Subnet Mask :255.255.255.0
Gateway IP Address :0.0.0.0
FTP User Name :admin
FTP User Password :******
For more information about the fields, see Table 13.
After you finish setting the FTP parameters, the system returns to the BOOTWARE OPERATION ETHERNET submenu.
===================<BOOTWARE OPERATION ETHERNET SUB-MENU>===================
|<1> Update Full BootWare |
|<2> Update Extended BootWare |
|<3> Update Basic BootWare |
|<4> Modify Ethernet Parameter |
|<0> Exit To Main Menu |
============================================================================
Enter your choice(0-4):
4. Choose an option from options 1 to 3. For example, enter 1 to upgrade the entire BootWare image.
Loading.......Done.
64245 bytes downloaded!
Updating Basic BootWare? [Y/N]
5. Enter Y to upgrade the basic BootWare segment.
Updating Basic BootWare........Done.
Updating Extended BootWare? [Y/N]
6. Enter Y to upgrade the extended BootWare segment.
Updating Extended BootWare.........Done.
===================<BOOTWARE OPERATION ETHERNET SUB-MENU>===================
|<1> Update Full BootWare |
|<2> Update Extended BootWare |
|<3> Update Basic BootWare |
|<4> Modify Ethernet Parameter |
|<0> Exit To Main Menu |
============================================================================
Enter your choice(0-4):
7. Enter 0 to return to the BootWare Operation menu.
8. Enter 0 in the BootWare Operation menu to return to the EXTEND-BOOTWARE menu.
9. Enter 0 in the EXTEND-BOOTWARE menu to reboot the system.
Handling software upgrade failures
If a software upgrade fails, the system runs the old software version. To handle a software failure:
10. Check the physical ports for a loose or incorrect connection, and verify that the LEDs are reflecting the correct port status.
11. 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.
12. Check the file transfer settings:
¡ If TFTP is used, you must enter the same server IP addresses, file name, and working directory as set on the TFTP server.
¡ If FTP is used, you must enter the same FTP server IP address, source file name, working directory, and FTP username and password as set on the FTP server.
13. Check the FTP or TFTP server for incorrect settings.
14. Check that the CF card has sufficient space for the upgrade file.
15. If the message "Something is wrong with the file" appears, check the file for file corruption.
Appendix D Using BootWare menus
BootWare provides a menu method to perform basic file operations, software upgrade, and system management when the Comware CLI is inaccessible because of image corruption.
BootWare is stored in each MPU's built-in the SD card. It has one basic segment and one extended segment. The basic segment enables the system to complete basic initialization, and the extended segment bootstraps the Comware images.
Table 14 lists the menus that each segment provides and the major tasks you can perform using these menus. You can access these menus only during system startup.
BootWare segment | Menu | Tasks | Reference |
Basic | BASIC-BOOTWARE | · Modify serial port parameters. · Upgrade BootWare. · Start the primary or backup BootWare extended segment. | Using the BASIC-BOOTWARE menu |
Basic | BASIC ASSISTANT | Perform RAM test. | Accessing the BASIC-BOOTWARE menu |
Extended | EXTEND-BOOTWARE | · Upgrade Comware software. · Manage files. · Access the system when the console login password is lost. · Clear user privilege passwords. | Using the EXTENDED-BOOTWARE menu |
Extended | EXTEND-ASSISTANT | · Examine system memory. · Search system memory. | Accessing the EXTEND ASSISTANT submenu |
BootWare provides the shortcut keys listed in Table 15.
Table 15 BootWare shortcut keys
Shortcut keys | Prompt message | Function |
Ctrl+B | access EXTENDED-BOOTWARE MENU | Accesses the EXTENDED-BOOTWARE menu while the device is starting up. |
Ctrl+C | Please Start To Transfer File, Press <Ctrl+C> To Exit. | Stops the ongoing file transfer and exits the current operation interface. |
Info: Press Ctrl+C to abort or return to EXTENDED ASSISTANT MENU. | Returns to the EXTENDED ASSISTANT menu. If the system is outputting the result of an operation, this shortcut key combination aborts the display first. | |
Ctrl+D | Press Ctrl+D to access BASIC-BOOTWARE MENU | Accesses the BASIC-BOOTWARE menu while the device is starting up. |
Ctrl+D = Quit | Exits the parameter settings menu. | |
Ctrl+E | Memory Test(press Ctrl+C to skip it,press Ctrl+E to ECHO INFO) | Prints information during the memory test. |
Ctrl+F | Ctrl+F: Format File System | Formats the current storage medium. |
Ctrl+T | Press Ctrl+T to start memory test | Performs a memory test. |
Ctrl+U | Access BASIC ASSISTANT MENU | Accesses the BASIC ASSISTANT menu from the BASIC-BOOTWARE menu. |
Ctrl+Z | Ctrl+Z: Access EXTENDED ASSISTANT MENU | Accesses the EXTENDED ASSISTANT menu from the EXTENDED-BOOTWARE menu. |
Accessing the BASIC-BOOTWARE menu
16. Power on the device.
17. Press Ctrl+D within 4 seconds after the "Press Ctrl+D to access BASIC-BOOTWARE MENU" prompt message appears. If you fail to do this within the time limit, the system starts to run the extended BootWare segment.
======================<BASIC-BOOTWARE MENU(Ver 1.19)>=======================
|<1> Modify Serial Interface Parameter |
|<2> Update Extended BootWare |
|<3> Update Full BootWare |
|<4> Boot Extended BootWare |
|<5> Boot Backup Extended BootWare |
|<0> Reboot |
============================================================================
Ctrl+U: Access BASIC ASSISTANT MENU
Enter your choice(0-5):
Table 16 BASIC-BOOTWARE menu options
Option | Task | Reference |
<1> Modify Serial Interface Parameter | Change the baud rate of the console port. Perform this task before downloading an image through the console port for software upgrade. | Modifying serial port parameters |
<2> Update Extended BootWare | Upgrade the extended BootWare segment. If the extended segment is corrupt, choose this option to repair it. | Upgrading the extended BootWare segment |
<3> Update Full BootWare | Upgrade the entire BootWare, including the basic segment and the extended segment. | Upgrading the entire BootWare |
<4> Boot Extended BootWare | Run the primary extended BootWare segment. | Running the primary extended BootWare segment |
<5> Boot Backup Extend BootWare | Run the backup extended BootWare segment. | Running the backup extended BootWare segment |
<0> Reboot | Reboot the device. | N/A |
Ctrl+U: Access BASIC ASSISTANT MENU | Press Ctrl+U to access the BASIC ASSISTANT menu. | Accessing the BASIC ASSISTANT menu |
Modifying serial port parameters
To change the baud rate of the console port:
18. Enter 1 in the BASIC-BOOTWARE menu.
Enter your choice(0-5): 1
===============================<BAUDRATE SET>===============================
|Note:'*'indicates the current baudrate |
| Change The HyperTerminal's Baudrate Accordingly |
|---------------------------<Baudrate Available>---------------- ----------|
|<1> 9600(Default)* |
|<2> 19200 |
|<3> 38400 |
|<4> 57600 |
|<5> 115200 |
|<0> Exit |
============================================================================
Enter your choice(0-5):
19. Enter the number that represents the baud rate you want to choose. For example, enter 5 to set the baud rate to 115200 bps.
| NOTE: Baud rate change is a one-time operation. The baud rate will restore to the default (9600 bps) at reboot. To set up a console session with the device after a reboot, you must change the baud rate of the configuration terminal back to 9600 bps. |
Upgrading the extended BootWare segment
Enter 2 in the BASIC-BOOTWARE menu.
Enter your choice(0-5): 2
Please Start To Transfer File, Press <Ctrl+C> To Exit.
Waiting ...CCC
Enter 3 in the BASIC-BOOTWARE menu.
Enter your choice(0-5): 3
Please Start To Transfer File, Press <Ctrl+C> To Exit.
Waiting ...CCC
Running the primary extended BootWare segment
Enter 4 in the BASIC-BOOTWARE menu.
Enter your choice(0-5): 4
Booting Normal Extended BootWare.
The Extended BootWare is self-decompressing....Done.
****************************************************************************
* *
* H3C SecPath BootWare, Version 1.05 *
* *
****************************************************************************
Copyright (c) 2004-2017 New H3C Technologies Co., Ltd.
Compiled Date : Aug 31 2017
Memory Type : DDR3 SDRAM
Memory Size : 16384MB
Sda0 Size : 8MB
sda0 Size : 3728MB
CPLD Version : 1.0
PCB Version : Ver.B
BootWare Validating...
Press Ctrl+B to access EXTENDED-BOOTWARE MENU...
Loading the main image files...
Loading file sda0:/Main-CMW710-SYSTEM-A9615.bin. ......................
............................................................................
...........................Done.
Image file sda0:/Main-CMW710-BOOT-A9615.bin is self-decompressing......
.................................................Done.
System image is starting...
Running the backup extended BootWare segment
Enter 5 in the BASIC-BOOTWARE menu.
For information about backing up the extended BootWare segment, see "Accessing the BootWare Operation submenu."
Enter your choice(0-5): 5
Booting Backup Extended BootWare.
The Extended BootWare is self-decompressing............................Done!
| NOTE: This option is not supported if the password recovery capability is enabled. For more information about configuring the password recovery capability at the CLI, see "Controlling the password recovery capability." |
Accessing the BASIC ASSISTANT menu
Press Ctrl+U in the BASIC-BOOTWARE menu.
===========================<BASIC-ASSISTANT MENU>===========================
|<1> RAM Test |
|<0> Exit To Main Menu |
============================================================================
Enter your choice(0-1):
Table 17 BASIC ASSISTANT menu options
Option | Description |
<1> RAM Test | Test the memory. |
<2> Exit To Main Menu | Return to the BASIC-BOOTWARE menu. |
IMPORTANT: To avoid unexpected exceptions, perform this task under the guidance of H3C Support. |
To test the memory, use one of the following methods:
· In the BASIC-BOOTWARE menu, press Ctrl+T within 4 seconds after the "Press Ctrl+T to start memory test" prompt message appears.
· In the BASIC-BOOTWARE menu, press Ctrl+U to access the BASIC ASSISTANT menu.
Using the EXTENDED-BOOTWARE menu
Accessing the EXTENDED-BOOTWARE menu
20. Power on the device.
21. Press Ctrl+B within 5 seconds after the "Press Ctrl+B to access EXTENDED-BOOTWARE MENU..." prompt message appears. If you fail to do this within the time limit, the system starts up.
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 1.05 *
* *
****************************************************************************
Copyright (c) 2004-2017 New H3C Technologies Co., Ltd.
Compiled Date : Aug 31 2017
Memory Type : DDR3 SDRAM
Memory Size : 16384MB
Sda0 Size : 8MB
sda0 Size : 3728MB
CPLD Version : 1.0
PCB Version : Ver.B
BootWare Validating...
Press Ctrl+B to access EXTENDED-BOOTWARE MENU...
Password recovery capability is enabled.
Note: The current operating device is sda0
Enter < Storage Device Operation > to select device.
22. Press Enter to access the EXTENDED-BOOTWARE menu.
===========================<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
Enter your choice(0-9):
Availability of some options in this menu depends on the password recovery capability state (displayed on top of the EXTEND-BOOTWARE menu). For more information about the feature, see "Controlling the password recovery capability."
Table 18 EXTENDED-BOOTWARE menu options
Option | Tasks | Reference |
<1> Boot System | Run the Comware software without rebooting the device. Choose this option after completing operations in the EXTENDED-BOOTWARE menu. | N/A |
<2> Enter Serial SubMenu | Accessing the Serial submenu. | |
<3> Enter Ethernet SubMenu | Use FTP or TFTP to upgrade Comware images through the management Ethernet port. | |
<4> File Control | · Display files on the current storage medium. · Set a Comware image file as the main or backup startup software image file. · Delete files to release storage space. | |
<5> Restore to Factory Default Configuration | Restore the factory-default configuration. This option is available only if password recovery capability is disabled. | |
<6> Skip Current System Configuration | Start the device with the factory-default configuration without loading any configuration file. This option is available only if password recovery capability is enabled. | |
<7> BootWare Operation Menu | Back up, recover, and upgrade the BootWare image. | |
<8> Skip Authentication for Console Login | Skip console login authentication. This option is available only if password recovery capability is enabled. This is a one-time operation and takes effect only for the first system boot or reboot after you choose this option. | |
<9> Storage Device Operation | Set the storage medium from which the device will start up. Set the storage medium where file operations are performed. This storage medium is referred to as the "current storage medium." | |
Ctrl+F: Format File System | Format the file system. | |
Ctrl+Z: Access EXTENDED ASSISTANT MENU | Access the EXTENDED ASSISTANT menu. | Accessing the EXTEND ASSISTANT submenu |
<0> Reboot | Reboot the device. | N/A |
Controlling the password recovery capability
Password recovery capability controls console user access to the device configuration from BootWare menus. This feature decides the method to handle a password loss situation.
· If password recovery capability is enabled, a console user can handle a password loss situation as follows:
¡ If the console login password is lost, the user can skip console login authentication, and then access the CLI to configure a new password.
¡ If a user role password is lost, the user can skip the configuration file, and then access the CLI to configure a new password.
· If password recovery capability is disabled, console users must restore the factory-default configuration before they can configure new passwords.
To enhance system security, disable password recovery capability.
To enable or disable password recovery capability:
Step | Command | Remarks |
3. Enter system view. | system-view | N/A |
4. Enable or disabled password recovery capability. | · Enable the feature: · Disable the feature: | By default, password recovery capability is enabled. |
Enter 1 in the EXTEND-BOOTWARE menu.
Enter your choice(0-9): 1
Loading the main image files...
Loading file cfa0:/main-cmw710-system-e8526.bin.........................
............................................................................
.....................................................Done.
Loading file cfa0:/main-cmw710-boot-e8526.bin...........................
...................................Done.
Image file cfa0:/main-cmw710-boot-e8526.bin is self-decompressing.......
............................................................................
........Done.
System image is starting...
Enter 2 in the EXTEND-BOOTWARE menu.
Enter your choice(0-9): 2
===========================<Enter Serial SubMenu>===========================
|Note:the operating device is sda0 |
|<1> Download Image Program To SDRAM And Run |
|<2> Update Main Image File |
|<3> Update Backup Image File |
|<4> Download Files(*.*) |
|<5> Modify Serial Interface Parameter |
|<0> Exit To Main Menu |
============================================================================
Enter your choice(0-5):
Table 19 Serial submenu options
Option | Tasks |
<1> Download Image Program To SDRAM And Run | Load and run Comware images in SDRAM. This option is available only if password recovery capability is enabled. |
<2> Update Main Image File | Download Comware images to the current storage medium as the main images (the file attribute is set to M). As a result, the M file attribute of the original main images is removed. |
<3> Update Backup Image File | Download Comware images to the current storage medium as backup images (the file attribute is set to B). As a result, the B file attribute of the original backup images is removed. |
<4> Download Files(*.*) | Download files from the server to the device. |
<5> Modify Serial Interface Parameter | Change the baud rate of the console port. The baud rate change is a one-time operation. The baud rate will restore to the default (9600 bps) at reboot. To set up a console session with the device after a reboot, you must change the baud rate setting on the configuration terminal to 9600 bps. |
<0> Exit To Main Menu | Return to the EXTENDED-BOOTWARE menu. |
| NOTE: To set the current storage medium, see "Managing storage media." |
Accessing the Ethernet submenu
You can upgrade the Comware software through the management Ethernet port from the Ethernet submenu and configure file transfer settings.
23. Enter 3 in the EXTENDED-BOOTWARE menu and press Enter to access the Ethernet submenu.
Enter your choice(0-9):3
==========================<Enter Ethernet SubMenu>==========================
|Note:the operating device is sda0 |
|<1> Download Image Program To SDRAM And Run |
|<2> Update Main Image File |
|<3> Update Backup Image File |
|<4> Download Files(*.*) |
|<5> Modify Ethernet Parameter |
|<0> Exit To Main Menu |
|<Ensure The Parameter Be Modified Before Downloading!> |
============================================================================
Enter your choice(0-5):
Table 20 Ethernet submenu options
Option | Description |
<1> Download Image Program To SDRAM And Run | Load and run software images in SDRAM. If password recovery capability is enabled, this option is not available. |
<2> Update Main Image File | Download software images to the current storage medium as main images (the file attribute is set to M). As a result, the M file attribute of the original main images is removed. |
<3> Update Backup Image File | Download software images to the current storage medium as backup images (the file attribute is set to B). As a result, the B file attribute of the original backup images is removed. |
<4> Download Files(*.*) | Download files from the server to the device. |
<5> Modify Ethernet Parameter | Configure FTP or TFTP file transfer settings. |
<0> Exit To Main Menu | Return to the EXTENDED-BOOTWARE menu. |
24. Enter 4 in the Ethernet submenu to configure file transfer settings on the MPU.
Enter your choice(0-4):4
======================<ETHERNET PARAMETER SET>=============================
|Note: '.' = Clear field. |
| '-' = Go to previous field. |
| Ctrl+D = Quit. |
===========================================================================
Protocol (FTP or TFTP) :ftp
Load File Name :main.ipe
:
Target File Name :main.ipe
:
Server IP Address :192.168.0.2
Local IP Address :192.168.0.1
Subnet Mask :255.255.255.0
Gateway IP Address :0.0.0.0
FTP User Name :admin
FTP User Password :******
Table 21 Setting Ethernet parameters for file transfer
Field | Description |
'.' = Clear field | Press the dot (.), and then press Enter to clear the setting for a field. |
'-' = Go to previous field | Press the hyphen (-), and then press Enter to return to the previous field. |
Ctrl+D = Quit | Press Ctrl + D to exit the Ethernet parameter settings menu. |
Protocol (FTP or TFTP) | Set the file transfer protocol to FTP or TFTP. |
Load File Name | Set the name of the file to be downloaded. |
Target File Name | Set a file name for saving the file in the current storage medium on the device. By default, the target file name is the same as the source file name. |
Server IP Address | Set the IP address of the FTP or TFTP server. |
Local IP Address | Set the IP address of the device. |
Subnet Mask | Set the IP address mask. |
Gateway IP Address | Set a gateway IP address if the device is on a different network than the server. |
FTP User Name | Set the username for accessing the FTP server. This username must be the same as configured on the FTP server. This field is not available for TFTP. |
FTP User Password | Set the password for accessing the FTP server. This password must be the same as configured on the FTP server. This field is not available for TFTP. |
You can display all files, set the attribute for a file, and delete a file from the File Control submenu.
Enter 4 in the EXTEND-BOOTWARE menu and then press Enter to access the File Control submenu.
Enter your choice(0-9):4
===============================<File CONTROL>===============================
|Note:the operating device is cfa0 |
|<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 22 File Control submenu options
Option | Description |
<1> Display All File(s) | Display all files. |
<2> Set Image File type | Set the attribute for a software image file. |
<3> Set Bin File type | Set the attribute for a .bin file. |
<4> Set Configuration File type | Set the type for a configuration file. |
<5> Delete File | Delete a file. |
<0> Exit To Main Menu | Return to the EXTEND-BOOTWARE menu. |
Displaying all files
Enter 1 in the File Control submenu.
Enter your choice(0-5): 1
Display all file(s) in cfa0:
'M' = MAIN 'B' = BACKUP 'N/A' = NOT ASSIGNED
============================================================================
|NO. Size(B) Time Type Name |
|1 956 Jan/21/2019 17:59:34 N/A cfa0:/ifindex.dat |
|2 24671 Mar/28/2018 09:08:56 N/A cfa0:/wdydiudie.cfg |
|3 735 Mar/28/2018 09:18:22 N/A cfa0:/hostkey |
|4 116549 Oct/09/2017 13:51:02 N/A cfa0:/lwb-t5k.cfg |
|5 963 Mar/27/2018 15:24:12 N/A cfa0:/license/history/deviceid_2|
|0180327152412.did |
|6 965 Mar/27/2018 15:24:12 N/A cfa0:/license/210235a1rsh1640000|
|06.did |
|7 3237 Dec/25/2017 15:14:54 N/A cfa0:/license/ngips2017122515235|
|923325.ak |
|8 3249 Apr/16/2018 16:40:28 N/A cfa0:/license/ngips2018041616523|
|608292.ak |
|9 1611429 Jan/22/2019 14:14:22 N/A cfa0:/logfile/logfile.log |
|10 1048575 Apr/16/2018 17:57:26 N/A cfa0:/logfile/ips.log |
|11 5230 Mar/19/2018 14:40:30 N/A cfa0:/logfile/uflt.log |
|12 1048405 Apr/16/2018 17:57:26 N/A cfa0:/logfile/anti-vir.log |
|13 44840 Aug/10/2017 15:25:46 N/A cfa0:/logfile/dfilter.log |
|14 14195 Jan/21/2019 16:47:54 N/A cfa0:/logfile/cfglog.log |
|15 251751 Jan/03/2019 09:09:56 N/A cfa0:/diagfile/diagfile.log |
|16 69784 Mar/28/2018 09:18:28 N/A cfa0:/dpi/ips/predefined/ips_sig|
|pack_curr.dat |
|17 2373992 Mar/28/2018 09:18:28 N/A cfa0:/dpi/ips/predefined/ips_sig|
|pack_back.dat |
|18 32027352 Apr/16/2018 16:56:28 N/A cfa0:/dpi/av/predefined/av_sigpa|
|ck_curr.dat |
|19 9574536 Apr/16/2018 16:48:00 N/A cfa0:/dpi/av/predefined/av_sigpa|
|ck_back.dat |
|20 68040 Mar/28/2018 09:18:28 N/A cfa0:/dpi/uflt/predefined/uflt_s|
|igpack_curr.dat |
|21 10330760 Mar/28/2018 09:18:36 N/A cfa0:/dpi/uflt/predefined/uflt_s|
|igpack_back.dat |
|22 342232 Mar/28/2018 09:18:24 N/A cfa0:/dpi/apr/predefined/apr_sig|
|pack_curr.dat |
|23 979448 Mar/28/2018 09:18:24 N/A cfa0:/dpi/apr/predefined/apr_sig|
|pack_back.dat |
|24 2840 Jan/22/2019 14:12:46 N/A cfa0:/dpi/filereg/predefined/fil|
|ereg_sigpack_curr.dat |
|25 30 Jan/21/2019 16:53:16 N/A cfa0:/dpi/dpi_sigpack.log |
|26 1566 Mar/28/2018 09:18:20 N/A cfa0:/pki/https-server.p12 |
|27 591 Mar/28/2018 09:18:22 N/A cfa0:/serverkey |
|28 259308 Mar/28/2018 09:08:58 N/A cfa0:/wdydiudie.mdb |
|29 723419 Oct/09/2017 13:51:04 N/A cfa0:/lwb-t5k.mdb |
|30 22692 Jan/21/2019 17:59:36 M cfa0:/startup.cfg |
|31 686202 May/20/2017 19:15:56 N/A cfa0:/pn.cfg |
|32 9275 Oct/28/2017 13:50:12 N/A cfa0:/zp.cfg |
|33 807 Oct/09/2017 15:59:54 N/A cfa0:/.trash/.trashinfo |
|34 5327872 Aug/15/2017 13:06:42 N/A cfa0:/.trash/main-cmw710-boo|
|t-e8518.bin_0001 |
|35 5331968 Aug/15/2017 10:30:04 N/A cfa0:/.trash/main-cmw710-boo|
|t-e8519.bin_0001 |
|36 9048064 Aug/21/2017 13:54:12 N/A cfa0:/.trash/main-cmw710-boo|
|t-e8520.bin_0001 |
|37 2056192 Aug/12/2017 18:05:54 N/A cfa0:/.trash/main-cmw710-dev|
|kit-e8518.bin_0001 |
|38 163840 Aug/14/2017 16:57:06 N/A cfa0:/.trash/main-cmw710-dev|
|kit-e8519.bin_0001 |
|39 163840 Aug/21/2017 14:07:26 N/A cfa0:/.trash/main-cmw710-dev|
|kit-e8520.bin_0001 |
|40 103891968 Aug/15/2017 13:07:04 N/A cfa0:/.trash/main-cmw710-sys|
|tem-e8518.bin_0001 |
|41 107120640 Aug/15/2017 10:30:58 N/A cfa0:/.trash/main-cmw710-sys|
|tem-e8519.bin_0001 |
|42 171900928 Aug/21/2017 14:07:02 N/A cfa0:/.trash/main-cmw710-sys|
|tem-e8520.bin_0001 |
|43 2238 Jan/22/2019 14:14:22 N/A cfa0:/context/context3/logfile/l|
|ogfile.log |
|44 24 Jan/21/2019 17:59:50 N/A cfa0:/context/context3/ifindex.d|
|at |
|45 1192 Jan/21/2019 17:59:50 N/A cfa0:/context/context3/startup.c|
|fg |
|46 34023 Jan/21/2019 17:59:50 N/A cfa0:/context/context3/startup.m|
|db |
|47 18468 Jan/22/2019 14:14:22 N/A cfa0:/context/context4/logfile/l|
|ogfile.log |
|48 1566 Mar/28/2018 09:19:08 N/A cfa0:/context/context4/pki/https|
|-server.p12 |
|49 1671 Jan/22/2019 09:27:00 N/A cfa0:/context/context4/startup.c|
|fg |
|50 37050 Jan/22/2019 09:27:00 N/A cfa0:/context/context4/startup.m|
|db |
|51 52 Jan/22/2019 09:27:00 N/A cfa0:/context/context4/ifindex.d|
|at |
|52 9054208 Apr/20/2018 13:27:02 N/A cfa0:/main-cmw710-boot-e8526|
|.bin |
|53 227919 Jan/21/2019 17:59:36 N/A cfa0:/startup.mdb |
|54 186294272 Apr/20/2018 13:27:30 N/A cfa0:/main-cmw710-system-e85|
|26.bin |
|55 123384832 Jan/21/2019 17:20:04 N/A cfa0:/main.ipe |
|56 3920 Jul/19/2017 18:32:04 N/A cfa0:/86.raw |
|57 3242 Jul/07/2017 09:36:50 N/A cfa0:/ngips2017070709142354252.a|
|k |
|58 120804 Jun/17/2017 17:00:30 N/A cfa0:/1.cfg |
|59 822025 Jun/17/2017 17:00:34 N/A cfa0:/1.mdb |
|60 120727 Jun/17/2017 17:01:02 N/A cfa0:/2.cfg |
|61 821866 Jun/17/2017 17:01:06 N/A cfa0:/2.mdb |
|62 16 Jan/21/2019 17:48:10 N/A cfa0:/versioninfo/versionctl.dat|
|63 536 Jan/21/2019 17:48:10 N/A cfa0:/versioninfo/version0.dat |
|64 796 Mar/20/2018 16:23:44 N/A cfa0:/versioninfo/version1.dat |
|65 796 Mar/20/2018 16:30:22 N/A cfa0:/versioninfo/version2.dat |
|66 796 Mar/20/2018 16:32:22 N/A cfa0:/versioninfo/version3.dat |
|67 796 Mar/20/2018 16:39:04 N/A cfa0:/versioninfo/version4.dat |
|68 536 Mar/27/2018 12:36:40 N/A cfa0:/versioninfo/version5.dat |
|69 796 Mar/27/2018 14:23:12 N/A cfa0:/versioninfo/version6.dat |
|70 536 Mar/28/2018 09:18:16 N/A cfa0:/versioninfo/version7.dat |
|71 796 Apr/16/2018 18:06:04 N/A cfa0:/versioninfo/version8.dat |
|72 536 Jul/24/2018 11:50:02 N/A cfa0:/versioninfo/version9.dat |
|73 9696 Sep/11/2017 17:41:56 N/A cfa0:/libpty.so |
|74 500446 Jul/29/2017 17:59:46 N/A cfa0:/ips.rules |
|75 19586056 Oct/16/2017 17:58:08 N/A cfa0:/50w-2.dat |
|76 117405304 Oct/16/2017 15:38:20 N/A cfa0:/500w-2.dat |
|77 7125 Sep/11/2017 19:43:30 N/A cfa0:/new1.rules |
|78 963 Oct/16/2017 17:12:58 N/A cfa0:/210235a1rsh164000006.did |
|79 9172 Oct/26/2017 11:30:30 N/A cfa0:/uzi.cfg |
|80 792001 May/20/2017 19:15:58 N/A cfa0:/pn.mdb |
|81 554834 May/18/2017 15:40:52 N/A cfa0:/fullconfig.cfg |
|82 684919 May/19/2017 13:50:20 N/A cfa0:/fullconfig2.cfg |
|83 554834 May/18/2017 16:20:36 N/A cfa0:/fullconfig1.cfg |
|84 788347 May/19/2017 13:50:22 N/A cfa0:/fullconfig2.mdb |
|85 154433 Oct/26/2017 11:30:30 N/A cfa0:/uzi.mdb |
|86 685411 May/23/2017 14:08:56 N/A cfa0:/wdy0523.cfg |
|87 791322 May/23/2017 14:08:58 N/A cfa0:/wdy0523.mdb |
|88 3246 Oct/16/2017 17:38:58 N/A cfa0:/ngips2017101617275868747.a|
|k |
|89 164864 Apr/20/2018 13:36:44 N/A cfa0:/main-cmw710-devkit-e85|
|26.bin |
|90 582397 Dec/25/2017 16:17:00 N/A cfa0:/1024.rules |
|91 93544 Dec/25/2017 16:17:30 N/A cfa0:/url.dat |
|92 5684224 Jul/24/2018 11:39:04 N/A cfa0:/main-cmw710-boot-e8530|
|.bin |
|93 154961 Oct/28/2017 13:50:14 N/A cfa0:/zp.mdb |
|94 504464 Oct/28/2017 19:22:12 N/A cfa0:/5e9dd320d3c7fd6fbec3a81a85|
|788002.6d9ada99 |
|95 2491008 Oct/29/2017 15:57:14 N/A cfa0:/8ac3b6bff681d9be6a20f865ac|
|e15a14 |
|96 20 Jan/31/2018 14:20:10 N/A cfa0:/.snmpboots |
|97 2216 Apr/16/2018 18:05:22 N/A cfa0:/pcap/excpt-currentcpu11-20|
|180117140659.cap |
|98 128016 Jan/17/2018 14:29:32 N/A cfa0:/firewall.exp |
|99 2812 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/cn/subthreatrep|
|ort.html |
|100 1139 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/cn/threatid.htm|
|l |
|101 2148 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/cn/threatlog.ht|
|ml |
|102 2370 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/cn/threatrank.h|
|tml |
|103 2067 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/cn/threatrankdl|
|g.html |
|104 4122 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/cn/threatreport|
|.html |
|105 3571 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/cn/threattrend.|
|html |
|106 2857 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/en/subthreatrep|
|ort.html |
|107 1429 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/en/threatlog.ht|
|ml |
|108 2651 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/en/threatrank.h|
|tml |
|109 2419 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/en/threatrankdl|
|g.html |
|110 4213 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/en/threatreport|
|.html |
|111 2721 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/en/threattrend.|
|html |
|112 14068 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/nc.js |
|113 36539 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/netconf.rbac |
|114 19541 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/subthreatreport|
|.js |
|115 13032 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/threatid.js |
|116 98591 Jan/17/2018 20:10:04 N/A cfa0:/web/threat/threatlog.js |
|117 55749 Jan/17/2018 20:07:30 N/A cfa0:/web/threat/threatrank.js |
|118 37582 Jan/17/2018 20:07:30 N/A cfa0:/web/threat/threatrankdlg.j|
|s |
|119 31328 Jan/17/2018 20:07:30 N/A cfa0:/web/threat/threatreport.js|
|120 133659 Jan/17/2018 20:07:30 N/A cfa0:/web/threat/threattrend.js |
|121 106004480 Jul/24/2018 11:39:24 N/A cfa0:/main-cmw710-system-e85|
|30.bin |
|122 5692416 Jan/21/2019 17:29:52 M cfa0:/main-cmw710-boot-e8524|
|p15.bin |
|123 117685248 Jan/21/2019 17:30:12 M cfa0:/main-cmw710-system-e85|
|24p15.bin |
|124 7300 Jan/24/2018 08:53:08 N/A cfa0:/0a704f6998e9602ac5203b1306|
|7b2317 |
|125 151348 Jun/05/2017 16:40:44 N/A cfa0:/o.mdb |
|126 17704 Jan/31/2018 09:44:08 N/A cfa0:/dpi.cfg |
|127 235207 Jan/31/2018 09:44:10 N/A cfa0:/dpi.mdb |
|128 17659 Jan/31/2018 10:53:24 N/A cfa0:/dpi1.cfg |
|129 231817 Jan/31/2018 10:53:26 N/A cfa0:/dpi1.mdb |
|130 110592 Jan/31/2018 14:31:18 N/A cfa0:/core/node16_dpid_202565_11|
|_20180131-143118_1517409078.core |
|131 118784 Jul/24/2018 11:51:10 N/A cfa0:/core/node16_ntopd_820_11_2|
|0180724-115110_1532433070.core |
|132 118784 Dec/17/2018 08:32:20 N/A cfa0:/core/node16_ntopd_803_11_2|
|0181217-083220_1545035540.core |
|133 3249 Apr/16/2018 16:40:28 N/A cfa0:/ngips2018041616523608292.a|
|k |
============================================================================
Setting the attribute for software images
1. Enter 2 in the File Control submenu.
===============================<File CONTROL>===============================
|Note:the operating device is cfa0 |
|<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): 2
'M' = MAIN 'B' = BACKUP 'N/A' = NOT ASSIGNED
============================================================================
|NO. Size(B) Time Type Name |
|1 123384832 Jan/21/2019 17:20:04 N/A cfa0:/main.ipe |
|0 Exit |
============================================================================
2. Enter the numbers of the files you are working with. For example, enter 1.
Enter file No.:1
Modify the file attribute:
============================================================================
|<1>+Main |
|<2>+Backup |
|<0> Exit |
============================================================================
Enter your choice(0-2):
3. Enter a number in the range of 0 to 2 to add or delete a file attribute for the files. For example, enter 1 to assign the M attribute to the files.
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-E8524P15.bin is self-decompressing...
Saving file cfa0:/main-cmw710-boot-E8524P15.bin ........................
............................................................................
.................Done.
Image file main-cmw710-system-E8524P15.bin is self-decompressing...
Saving file cfa0:/main-cmw710-system-E8524P15.bin ......................
............................................................................
............................................................................
.....................................................................Done.
Set the file attribute success!
Setting the attribute for .bin files
Enter 3 in the File Control submenu.
Enter your choice(0-5): 3
'M' = MAIN 'B' = BACKUP 'N/A' = NOT ASSIGNED
============================================================================
|NO. Size(B) Time Type Name |
|1 9054208 Apr/20/2018 13:27:02 N/A cfa0:/main-cmw710-boot-e8526|
|.bin |
|2 186294272 Apr/20/2018 13:27:30 N/A cfa0:/main-cmw710-system-e85|
|26.bin |
|3 164864 Apr/20/2018 13:36:44 N/A cfa0:/main-cmw710-devkit-e85|
|26.bin |
|4 5684224 Jul/24/2018 11:39:04 N/A cfa0:/main-cmw710-boot-e8530|
|.bin |
|5 106004480 Jul/24/2018 11:39:24 N/A cfa0:/main-cmw710-system-e85|
|30.bin |
|6 5692416 Jan/22/2019 14:47:32 M cfa0:/main-cmw710-boot-e8524|
|p15.bin |
|7 117685248 Jan/22/2019 14:47:50 M cfa0:/main-cmw710-system-e85|
|24p15.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
You have selected:
cfa0:/main-cmw710-boot-e8526.bin
cfa0:/main-cmw710-system-e8526.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 a file
1. Enter 5 in the File Control submenu.
Enter your choice(0-5): 5
Deleting the file in cfa0:
'M' = MAIN 'B' = BACKUP 'N/A' = NOT ASSIGNED
============================================================================
|NO. Size(B) Time Type Name |
|1 956 Jan/21/2019 17:59:34 N/A cfa0:/ifindex.dat |
|2 24671 Mar/28/2018 09:08:56 N/A cfa0:/wdydiudie.cfg |
|3 735 Mar/28/2018 09:18:22 N/A cfa0:/hostkey |
|4 116549 Oct/09/2017 13:51:02 N/A cfa0:/lwb-t5k.cfg |
|5 963 Mar/27/2018 15:24:12 N/A cfa0:/license/history/deviceid_2|
|0180327152412.did |
|6 965 Mar/27/2018 15:24:12 N/A cfa0:/license/210235a1rsh1640000|
|06.did |
|7 3237 Dec/25/2017 15:14:54 N/A cfa0:/license/ngips2017122515235|
|923325.ak |
|8 3249 Apr/16/2018 16:40:28 N/A cfa0:/license/ngips2018041616523|
|608292.ak |
|9 1611429 Jan/22/2019 14:14:22 N/A cfa0:/logfile/logfile.log |
|10 1048575 Apr/16/2018 17:57:26 N/A cfa0:/logfile/ips.log |
|11 5230 Mar/19/2018 14:40:30 N/A cfa0:/logfile/uflt.log |
|12 1048405 Apr/16/2018 17:57:26 N/A cfa0:/logfile/anti-vir.log |
|13 44840 Aug/10/2017 15:25:46 N/A cfa0:/logfile/dfilter.log |
|14 14195 Jan/21/2019 16:47:54 N/A cfa0:/logfile/cfglog.log |
|15 251751 Jan/03/2019 09:09:56 N/A cfa0:/diagfile/diagfile.log |
|16 69784 Mar/28/2018 09:18:28 N/A cfa0:/dpi/ips/predefined/ips_sig|
|pack_curr.dat |
|17 2373992 Mar/28/2018 09:18:28 N/A cfa0:/dpi/ips/predefined/ips_sig|
|pack_back.dat |
|18 32027352 Apr/16/2018 16:56:28 N/A cfa0:/dpi/av/predefined/av_sigpa|
|ck_curr.dat |
|19 9574536 Apr/16/2018 16:48:00 N/A cfa0:/dpi/av/predefined/av_sigpa|
|ck_back.dat |
|20 68040 Mar/28/2018 09:18:28 N/A cfa0:/dpi/uflt/predefined/uflt_s|
|igpack_curr.dat |
|21 10330760 Mar/28/2018 09:18:36 N/A cfa0:/dpi/uflt/predefined/uflt_s|
|igpack_back.dat |
|22 342232 Mar/28/2018 09:18:24 N/A cfa0:/dpi/apr/predefined/apr_sig|
|pack_curr.dat |
|23 979448 Mar/28/2018 09:18:24 N/A cfa0:/dpi/apr/predefined/apr_sig|
|pack_back.dat |
|24 2840 Jan/22/2019 14:12:46 N/A cfa0:/dpi/filereg/predefined/fil|
|ereg_sigpack_curr.dat |
|25 30 Jan/21/2019 16:53:16 N/A cfa0:/dpi/dpi_sigpack.log |
|26 1566 Mar/28/2018 09:18:20 N/A cfa0:/pki/https-server.p12 |
|27 591 Mar/28/2018 09:18:22 N/A cfa0:/serverkey |
|28 259308 Mar/28/2018 09:08:58 N/A cfa0:/wdydiudie.mdb |
|29 723419 Oct/09/2017 13:51:04 N/A cfa0:/lwb-t5k.mdb |
|30 22692 Jan/21/2019 17:59:36 M cfa0:/startup.cfg |
|31 686202 May/20/2017 19:15:56 N/A cfa0:/pn.cfg |
|32 9275 Oct/28/2017 13:50:12 N/A cfa0:/zp.cfg |
|33 807 Oct/09/2017 15:59:54 N/A cfa0:/.trash/.trashinfo |
|34 5327872 Aug/15/2017 13:06:42 N/A cfa0:/.trash/main-cmw710-boo|
|t-e8518.bin_0001 |
|35 5331968 Aug/15/2017 10:30:04 N/A cfa0:/.trash/main-cmw710-boo|
|t-e8519.bin_0001 |
|36 9048064 Aug/21/2017 13:54:12 N/A cfa0:/.trash/main-cmw710-boo|
|t-e8520.bin_0001 |
|37 2056192 Aug/12/2017 18:05:54 N/A cfa0:/.trash/main-cmw710-dev|
|kit-e8518.bin_0001 |
|38 163840 Aug/14/2017 16:57:06 N/A cfa0:/.trash/main-cmw710-dev|
|kit-e8519.bin_0001 |
|39 163840 Aug/21/2017 14:07:26 N/A cfa0:/.trash/main-cmw710-dev|
|kit-e8520.bin_0001 |
|40 103891968 Aug/15/2017 13:07:04 N/A cfa0:/.trash/main-cmw710-sys|
|tem-e8518.bin_0001 |
|41 107120640 Aug/15/2017 10:30:58 N/A cfa0:/.trash/main-cmw710-sys|
|tem-e8519.bin_0001 |
|42 171900928 Aug/21/2017 14:07:02 N/A cfa0:/.trash/main-cmw710-sys|
|tem-e8520.bin_0001 |
|43 2238 Jan/22/2019 14:14:22 N/A cfa0:/context/context3/logfile/l|
|ogfile.log |
|44 24 Jan/21/2019 17:59:50 N/A cfa0:/context/context3/ifindex.d|
|at |
|45 1192 Jan/21/2019 17:59:50 N/A cfa0:/context/context3/startup.c|
|fg |
|46 34023 Jan/21/2019 17:59:50 N/A cfa0:/context/context3/startup.m|
|db |
|47 18468 Jan/22/2019 14:14:22 N/A cfa0:/context/context4/logfile/l|
|ogfile.log |
|48 1566 Mar/28/2018 09:19:08 N/A cfa0:/context/context4/pki/https|
|-server.p12 |
|49 1671 Jan/22/2019 09:27:00 N/A cfa0:/context/context4/startup.c|
|fg |
|50 37050 Jan/22/2019 09:27:00 N/A cfa0:/context/context4/startup.m|
|db |
|51 52 Jan/22/2019 09:27:00 N/A cfa0:/context/context4/ifindex.d|
|at |
|52 9054208 Apr/20/2018 13:27:02 M cfa0:/main-cmw710-boot-e8526|
|.bin |
|53 227919 Jan/21/2019 17:59:36 N/A cfa0:/startup.mdb |
|54 186294272 Apr/20/2018 13:27:30 M cfa0:/main-cmw710-system-e85|
|26.bin |
|55 123384832 Jan/21/2019 17:20:04 N/A cfa0:/main.ipe |
|56 3920 Jul/19/2017 18:32:04 N/A cfa0:/86.raw |
|57 3242 Jul/07/2017 09:36:50 N/A cfa0:/ngips2017070709142354252.a|
|k |
|58 120804 Jun/17/2017 17:00:30 N/A cfa0:/1.cfg |
|59 822025 Jun/17/2017 17:00:34 N/A cfa0:/1.mdb |
|60 120727 Jun/17/2017 17:01:02 N/A cfa0:/2.cfg |
|61 821866 Jun/17/2017 17:01:06 N/A cfa0:/2.mdb |
|62 16 Jan/21/2019 17:48:10 N/A cfa0:/versioninfo/versionctl.dat|
|63 536 Jan/21/2019 17:48:10 N/A cfa0:/versioninfo/version0.dat |
|64 796 Mar/20/2018 16:23:44 N/A cfa0:/versioninfo/version1.dat |
|65 796 Mar/20/2018 16:30:22 N/A cfa0:/versioninfo/version2.dat |
|66 796 Mar/20/2018 16:32:22 N/A cfa0:/versioninfo/version3.dat |
|67 796 Mar/20/2018 16:39:04 N/A cfa0:/versioninfo/version4.dat |
|68 536 Mar/27/2018 12:36:40 N/A cfa0:/versioninfo/version5.dat |
|69 796 Mar/27/2018 14:23:12 N/A cfa0:/versioninfo/version6.dat |
|70 536 Mar/28/2018 09:18:16 N/A cfa0:/versioninfo/version7.dat |
|71 796 Apr/16/2018 18:06:04 N/A cfa0:/versioninfo/version8.dat |
|72 536 Jul/24/2018 11:50:02 N/A cfa0:/versioninfo/version9.dat |
|73 9696 Sep/11/2017 17:41:56 N/A cfa0:/libpty.so |
|74 500446 Jul/29/2017 17:59:46 N/A cfa0:/ips.rules |
|75 19586056 Oct/16/2017 17:58:08 N/A cfa0:/50w-2.dat |
|76 117405304 Oct/16/2017 15:38:20 N/A cfa0:/500w-2.dat |
|77 7125 Sep/11/2017 19:43:30 N/A cfa0:/new1.rules |
|78 963 Oct/16/2017 17:12:58 N/A cfa0:/210235a1rsh164000006.did |
|79 9172 Oct/26/2017 11:30:30 N/A cfa0:/uzi.cfg |
|80 792001 May/20/2017 19:15:58 N/A cfa0:/pn.mdb |
|81 554834 May/18/2017 15:40:52 N/A cfa0:/fullconfig.cfg |
|82 684919 May/19/2017 13:50:20 N/A cfa0:/fullconfig2.cfg |
|83 554834 May/18/2017 16:20:36 N/A cfa0:/fullconfig1.cfg |
|84 788347 May/19/2017 13:50:22 N/A cfa0:/fullconfig2.mdb |
|85 154433 Oct/26/2017 11:30:30 N/A cfa0:/uzi.mdb |
|86 685411 May/23/2017 14:08:56 N/A cfa0:/wdy0523.cfg |
|87 791322 May/23/2017 14:08:58 N/A cfa0:/wdy0523.mdb |
|88 3246 Oct/16/2017 17:38:58 N/A cfa0:/ngips2017101617275868747.a|
|k |
|89 164864 Apr/20/2018 13:36:44 N/A cfa0:/main-cmw710-devkit-e85|
|26.bin |
|90 582397 Dec/25/2017 16:17:00 N/A cfa0:/1024.rules |
|91 93544 Dec/25/2017 16:17:30 N/A cfa0:/url.dat |
|92 5684224 Jul/24/2018 11:39:04 N/A cfa0:/main-cmw710-boot-e8530|
|.bin |
|93 154961 Oct/28/2017 13:50:14 N/A cfa0:/zp.mdb |
|94 504464 Oct/28/2017 19:22:12 N/A cfa0:/5e9dd320d3c7fd6fbec3a81a85|
|788002.6d9ada99 |
|95 2491008 Oct/29/2017 15:57:14 N/A cfa0:/8ac3b6bff681d9be6a20f865ac|
|e15a14 |
|96 20 Jan/31/2018 14:20:10 N/A cfa0:/.snmpboots |
|97 2216 Apr/16/2018 18:05:22 N/A cfa0:/pcap/excpt-currentcpu11-20|
|180117140659.cap |
|98 128016 Jan/17/2018 14:29:32 N/A cfa0:/firewall.exp |
|99 2812 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/cn/subthreatrep|
|ort.html |
|100 1139 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/cn/threatid.htm|
|l |
|101 2148 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/cn/threatlog.ht|
|ml |
|102 2370 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/cn/threatrank.h|
|tml |
|103 2067 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/cn/threatrankdl|
|g.html |
|104 4122 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/cn/threatreport|
|.html |
|105 3571 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/cn/threattrend.|
|html |
|106 2857 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/en/subthreatrep|
|ort.html |
|107 1429 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/en/threatlog.ht|
|ml |
|108 2651 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/en/threatrank.h|
|tml |
|109 2419 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/en/threatrankdl|
|g.html |
|110 4213 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/en/threatreport|
|.html |
|111 2721 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/en/threattrend.|
|html |
|112 14068 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/nc.js |
|113 36539 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/netconf.rbac |
|114 19541 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/subthreatreport|
|.js |
|115 13032 Jan/17/2018 20:07:28 N/A cfa0:/web/threat/threatid.js |
|116 98591 Jan/17/2018 20:10:04 N/A cfa0:/web/threat/threatlog.js |
|117 55749 Jan/17/2018 20:07:30 N/A cfa0:/web/threat/threatrank.js |
|118 37582 Jan/17/2018 20:07:30 N/A cfa0:/web/threat/threatrankdlg.j|
|s |
|119 31328 Jan/17/2018 20:07:30 N/A cfa0:/web/threat/threatreport.js|
|120 133659 Jan/17/2018 20:07:30 N/A cfa0:/web/threat/threattrend.js |
|121 106004480 Jul/24/2018 11:39:24 N/A cfa0:/main-cmw710-system-e85|
|30.bin |
|122 5692416 Jan/22/2019 14:47:32 N/A cfa0:/main-cmw710-boot-e8524|
|p15.bin |
|123 117685248 Jan/22/2019 14:47:50 N/A cfa0:/main-cmw710-system-e85|
|24p15.bin |
|124 7300 Jan/24/2018 08:53:08 N/A cfa0:/0a704f6998e9602ac5203b1306|
|7b2317 |
|125 151348 Jun/05/2017 16:40:44 N/A cfa0:/o.mdb |
|126 17704 Jan/31/2018 09:44:08 N/A cfa0:/dpi.cfg |
|127 235207 Jan/31/2018 09:44:10 N/A cfa0:/dpi.mdb |
|128 17659 Jan/31/2018 10:53:24 N/A cfa0:/dpi1.cfg |
|129 231817 Jan/31/2018 10:53:26 N/A cfa0:/dpi1.mdb |
|130 110592 Jan/31/2018 14:31:18 N/A cfa0:/core/node16_dpid_202565_11|
|_20180131-143118_1517409078.core |
|131 118784 Jul/24/2018 11:51:10 N/A cfa0:/core/node16_ntopd_820_11_2|
|0180724-115110_1532433070.core |
|132 118784 Dec/17/2018 08:32:20 N/A cfa0:/core/node16_ntopd_803_11_2|
|0181217-083220_1545035540.core |
|133 3249 Apr/16/2018 16:40:28 N/A cfa0:/ngips2018041616523608292.a|
|k |
|0 Exit |
============================================================================
Enter file No.:
2. Enter the number of the file to delete. For example, enter 13 to delete the sda0:/test.cfg file.
3. When the following message appears, enter Y.
The file you selected is sda0:/test.cfg,Delete it? [Y/N]
If the following message appears, the file is successfully deleted.
Deleting.....Done!
Restoring the factory-default configuration
CAUTION: Restoring the factory-default configuration will permanently delete startup configuration files and backup configuration files in the current storage medium. |
To restore the factory-default configuration from the EXTENDED-BOOTWARE menu, make sure password recovery capability is disabled. If the capability is enabled, you cannot perform the task.
After you perform this task, the device uses the factory-default configuration instead of the configuration file for the next startup.
To enhance system security, disable password recovery capability.
To restore the factory-default configuration:
4. Enter 5 in the EXTEND-BOOTWARE menu and then press Enter.
Enter your choice(0-9): 5
5. Follow the system instruction to complete the task.
¡ If password recovery capability is enabled, first disable the capability from the CLI, and then reboot the device to access the EXTENDED-BOOTWARE menu.
Password recovery capability is enabled. To perform this operation, first disable the password recovery capability using the undo password-recovery enable command in CLI.
¡ If password recovery capability is disabled, enter Y at the prompt to complete the task.
Because the password recovery capability is disabled, this operation can cause the configuration files to be deleted, and the system will start up with factory defaults. Are you sure to continue?[Y/N]Y
Setting...Done.
Skipping the configuration file
To perform this task, make sure password recovery capability is enabled. If the capability is disabled, you cannot perform the task.
To start the device with the factory-default configuration:
6. Enter 6 in the EXTEND-BOOTWARE menu and press Enter.
Enter your choice(0-9): 6
Flag Set Success.
7. Follow the system instruction to complete the task.
¡ If password recovery capability is enabled, the device uses the factory-default configuration instead of the configuration file for the next startup.
¡ If password recovery capability is disabled, first enable the capability from the CLI, and then reboot the device to access the EXTENDED-BOOTWARE menu.
Password recovery capability is disabled. To perform this operation, first enable the password recovery capability using the password-recovery enable command in CLI.
Accessing the BootWare Operation submenu
Enter 7 in the EXTEND-BOOTWARE menu and press Enter.
Enter your choice(0-9): 7
=========================<BootWare Operation Menu>==========================
|Note:the operating device is sda0 |
|<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 23 BootWare Operation submenu options
Option | Description |
<1> Backup Full BootWare | Back up the entire BootWare image. |
<2> Restore Full BootWare | Recover the entire BootWare image. |
<3> Update BootWare By Serial | Upgrade the BootWare image through the serial port. |
<4> Update BootWare By Ethernet | Upgrade BootWare through the management Ethernet port. |
<0> Exit To Main Menu | Return to the EXTEND-BOOTWARE menu. |
Skipping console login authentication
To perform this task, make sure password recovery capability is enabled. If the capability is disabled, you cannot perform this task.
This is a one-time operation and takes effect only for the reboot after you perform this task.
To enable the device to load the next-startup configuration file with the console login password ignored:
8. Enter 8 in the EXTEND-BOOTWARE menu and press Enter.
Enter your choice(0-9): 8
9. Follow the system instruction to complete the task.
¡ If password recovery capability is enabled, the device clears the password for user privilege change.
Clear Image Password Success!
¡ If password recovery capability is disabled, first enable the capability from the CLI, and then reboot the device to access the EXTENDED-BOOTWARE menu.
Password recovery capability is disabled. To perform this operation, first enable the password recovery capability using the password-recovery enable command in CLI.
Enter 9 in the EXTEND-BOOTWARE menu and press Enter.
Enter your choice(0-9):9
==============================<DEVICE CONTROL>==============================
|<1> Display All Available Nonvolatile Storage Device(s) |
|<2> Set The Operating Device |
|<3> Set The Default Boot Device |
|<0> Exit To Main Menu |
============================================================================
Enter your choice(0-3):
Table 24 DEVICE CONTROL menu options
Option | Description |
<1> Display All Available Nonvolatile Storage Device(s) | Display all storage media on the MPU you are working with. |
<2> Set The Operating Device | Set the current storage medium. All file operations in BootWare menus are performed on the current storage medium. |
<3> Set The Default Boot Device | Set the default storage medium from which the system will start up. |
<0> Exit To Main Menu | Return to the EXTENDED-BOOTWARE menu. |
Accessing the EXTEND ASSISTANT submenu
Press Ctrl+Z in the EXTEND-BOOTWARE menu.
==========================<EXTENDED ASSISTANT MENU>=========================
|<1> Display Memory |
|<2> Search Memory |
|<0> Exit To Main Menu |
============================================================================
Enter your choice(0-2):
Table 25 EXTEND ASSISTANT submenu options
Option | Description |
<1> Display Memory | View memory information that meets certain requirements. |
<2> Search Memory | Search memory for data that meets certain requirements. |
<0> Exit To Main Menu | Return to the EXTEND-BOOTWARE menu. |
CAUTION: Formatting the file system clears all files and directories in a storage medium permanently. The cleared files and directories cannot be recovered. |
Press Ctrl+F in the EXTEND-BOOTWARE menu.
Warning:All files on sda0 will be lost! Are you sure to format? [Y/N]