Login
| Title | Size | Downloads |
|---|---|---|
| S9855_9825-CMW910-R9130.zip | 270.32 MB | |
| S9855_9825-CMW910-R9130_md5.rar | 359 bytes | |
| H3C S9855_9825-CMW910-R9130 Release Notes.docx | 168.75 KB | |
| H3C S9855_9825-CMW910-R9130 Release Notes (Software Feature Changes).pdf | 730.38 KB | |
| H3C S9855_9825-CMW910-R9130 Release Notes.pdf | 665.05 KB |
H3C S9855_9825-CMW910-R9130 Release Notes
Copyright © 2024 New H3C Technologies Co., Ltd. All rights reserved. No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd. Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are the property of their respective owners. The information in this document is subject to change without notice. |
|
Contents
Hardware and software compatibility· 4
Upgrade restrictions and guidelines· 6
Hardware feature updates in R9130· 6
Hardware feature updates in E9129P02· 6
Hardware feature updates in E9129P01· 6
Hardware feature updates in E9129· 6
Hardware feature updates in E9128· 7
Hardware feature updates in F9126P02· 7
Hardware feature updates in R9126· 7
Hardware feature updates in E9125· 7
Hardware feature updates in E9124P02· 7
Hardware feature updates in E9124P01· 7
Hardware feature updates in E9124· 7
Software feature and command updates· 7
Operation changes in E9129P02· 8
Operation changes in E9129P01· 9
Operation changes in F9126P02· 9
Operation changes in E9124P02· 9
Operation changes in E9124P01· 9
Registering and installing licenses· 11
Obtaining license server software and documentation· 11
Open problems and workarounds· 11
Resolved problems in R9130· 12
Resolved problems in E9129P02· 13
Resolved problems in E9129P01· 14
Resolved problems in E9129· 14
Resolved problems in E9128· 15
Resolved problems in F9126P02· 15
Resolved problems in R9126· 18
Resolved problems in E9125· 19
Resolved problems in E9124P02· 20
Resolved problems in E9124P01· 21
Resolved problems in E9124· 22
Appendix B Fixed security vulnerabilities· 27
Fixed security vulnerabilities in R9130· 27
Fixed security vulnerabilities in E9129P02· 27
Fixed security vulnerabilities in E9129P01· 27
Fixed security vulnerabilities in E9129· 27
Fixed security vulnerabilities in E9128· 27
Fixed security vulnerabilities in F9126P02· 27
Fixed security vulnerabilities in R9126· 28
Appendix C Upgrading software· 28
About startup software images· 28
Upgrading the startup software image from the CLI 29
Using TFTP to upgrade the startup software image· 29
Using FTP to upgrade the startup software image· 32
Upgrading the startup software image from the BootWare menu· 35
Accessing the BootWare main menu· 35
Using the network management interface to upgrade the startup software image through TFTP/ FTP· 36
List of tables
Table 1 Version history......................................................................................................... 1
Table 2 Hardware and software compatibility......................................................... 4
Table 3 MIB updates.............................................................................................................. 7
Table 4 Hardware features............................................................................................... 23
Table 5 Software features................................................................................................. 24
Table 6 Upgrade methods............................................................................................... 29
Table 7 BootWare menu options.................................................................................. 36
This document describes the features, restrictions and guidelines, open problems, and workarounds for version S9855_9825-CMW910-R9130. 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 S9855_9825-CMW910-R9130 Release Notes (Software Feature Changes) and the documents listed in "Related documentation."
Version information
Version number
H3C Comware Software, Version 9.1.043, Release 9130
You can view the version number by using the display version command in any view. See Note①.
Last version | Release date | Release type | Remarks | |
S9855_9825-CMW910-R9130 | S9855_9825-CMW910-E9129P02 | 2024-03-30 | Release | Resolved problems. Added features. Modified features. |
S9855_9825-CMW910-E9129P02 | S9855_9825-CMW910-E9129P01 | 2024-01-30 | ESS | Resolved problems New features: · Enabling per-packet forwarding for the specified queue · LBN · NetStream |
S9855_9825-CMW910-E9129P01 | S9855_9825-CMW910-E9129 | 2023-11-17 | ESS | Resolved problems New features: · Large MAC address tables · VLAN name TLV advertisement · RIP/RIPng · DLB · Per-packet forwarding |
S9855_9825-CMW910-E9129 | S9855_9825-CMW910-E9128 | 2023-10-29 | ESS | Resolved problems New features: · VXLAN on the S9825 device · VXLAN-based RoCE on the S9825 device |
S9855_9825-CMW910-E9128 | S9855_9825-CMW910-R9126 | 2023-07-29 | ESS | Resolved problems New features: · M-LAG · QinQ · VRRP · DHCP server · DHCPv6 server · AI ECN · PFC deadlock prevention · NetAnalysis for RoCEv2 traffic · OpenFlow · Splitting a 200G interface on the S9855-24B8D device into four 25G interfaces · License control for the lossless feature |
S9855_9825-CMW910-F9126P02 | S9855_9825-CMW910-R9126 | 2023-04-24 | Feature | Resolved problems New features: · GRE tunnel · IP tunnel · Configuring a source-destination address pair for IPv4-in-IPv4 packet decapsulation · Configuring a source-destination address pair for IPv6-in-IPv6 packet decapsulation · Enabling per-packet load sharing on an interface · Configuring the sampling direction for flow sampling · Transceiver module performance sampling · Using reserved ACL resources for the device IP statistics feature · BGP-related features: ¡ Configuring the BGP session state to collaborate with the monitor link downlink interfaces ¡ Enabling neighbor address unreachability detection ¡ Configuring the link bandwidth attributes for BGP paths |
S9855_9825-CMW910-R9126 | S9855_9825-CMW910-E9125 | 2022-10-26 | Release | Resolved problems New features: · Configuring the switch ID in ERSPANv3 mirrored packets on the S9855 device |
S9855_9825-CMW910-E9125 | S9855_9825-CMW910-E9124P02 | 2022-06-30 | ESS | Resolved problems New hardware: · S9855-24B8D New features: · BFD · INT · MOD · Telemetry stream · Resource monitoring · Flow mirroring support for ERSPANv3 · Configuring FEC on Ethernet interfaces · Splitting and combing Ethernet interfaces · Enabling split horizon for forwarding on Ethernet interfaces · QoS and ACL resources support for the sharing mode · Applying QoS policies to a control plane · Apply QoS policies to VLANs · Support for third-party ZR transceiver modules and the open-config YANG model · Viewing the interface flap count · Enabling unsolicited NA learning · Enabling the management interface to carry a vendor ID when obtaining an IPv6 address through DHCPv6 · Aggregation and ECMP support for hash outgoing interface pre-query · Aggregation and ECMP support for configuring flow labels to participate in hashing · Configuring the delay time for converting ARP and ND entries to routes |
S9855_9825-CMW910-E9124P02 | S9855_9825-CMW910-E9124P01 | 2021-09-14 | ESS | Resolved problems New features: · Setting the MAC address for an interface · Adjusting the hash for link aggregation load sharing · Configuring per-flow load sharing based on inner tunnel information on the S9855 device |
S9855_9825-CMW910-E9124P01 | S9800X-CMW910-E9124 | 2021-06-29 | ESS | Resolved problems New features: · IP statistics on a Layer 3 aggregate interface |
S9800X-CMW910-E9124 | First Release | 2021-06-01 | ESS | First release. |
Hardware and software compatibility
| IMPORTANT: To avoid an upgrade failure, use the following table to verify the hardware and software compatibility before performing an upgrade. |
Table 2 Hardware and software compatibility
Product series | S9855&S9825 series switches |
Model | S9855-48CD8D, S9855-24B8D, S9825-64D, S9825-64D-H1 |
Memory | 16G |
FLASH | 240G SSD M.2 SATA |
USB drive | Support USB 2.0 drives |
Boot ROM version | Come with the switch. (Note: You can view the version number by using the display version command in any view. See Note②.) |
Image file name and MD5 checksum | S9855_9825-CMW910-R9130.ipe: 7a7e66567d4ded0a8bf4d01fcc3209fc S9855_9825-CMW910-PACKET-CAPTURE-R9130.bin: 27a42e008d5bb7773494827ee9e3bed7 |
IMC versions | iMC PLAT 7.3 (E0705P12) iMC BIMS 7.3 (E0506H01) iMC EIA 7.3 (E0611P13) iMC NTA 7.3 (E0707L06) iMC QoSM 7.3 (E0505P01) iMC SHM 7.3 (E0707L06) iMC UBA 7.3 (E070903) |
iNode version | iNode PC 7.3 (E0585) |
Remarks | N/A |
Sample: Display the software version and BootWare version of the S9855&S9825 switch series.
H3C Comware Software, Version 9.1.043, Release 9130 ------Note①
Copyright (c) 2004-2024 New H3C Technologies Co., Ltd. All rights reserved.
H3C S9825-64D uptime is 0 weeks, 0 days, 0 hours, 47 minutes
Last reboot reason : USER reboot
Boot image: flash:/S9855_9825-CMW910-BOOT-R9130.bin
Boot image version: 9.1.043, Release 9130
Compiled Mar 26 2024 15:16:46, DEBUG SOFTWARE
System image: flash:/S9855_9825-CMW910-SYSTEM-R9130.bin
System image version: 9.1.043, Release 9130
Compiled Mar 26 2024 15:16:46, DEBUG SOFTWARE
Slot 1:
Uptime is 0 weeks,0 days,0 hours,47 minutes
H3C S9825-64D MPU(M) with 1 Processor
BOARD TYPE: S9825-64D
DRAM: 16384M bytes
FLASH: 228784M bytes
PCB 1 Version: VER.A
PCB 2 Version: VER.A
PCB 3 Version: VER.A
Release Version: S9825-64D-9130
CPLD 1 Version: 002C
CPLD 2 Version: 002C
CPLD 3 Version: 002C
CPLD 4 Version: 002C
CPLD 5 Version: 002C
Patch Version : None
PowChip 1 Version: 002C
PowChip 2 Version: 001B
PowChip 3 Version: 001B
PowChip 4 Version: 001B
PowChip 5 Version: 001B
PowChip 6 Version: 002C
PowChip 7 Version: 001B
Power CPLD Version: None
FPGA DOM Version: 00c80714
FPGA DOM Compile Date: 20230801
CpuCard
BuckleType: LSW1BPCX1600NSCOME
BucklePcb Version: VER.A
BuckleCPLD 1 Version: 001E
BuckleBootrom Version: 108 ------Note②
BucklePowChip 1 Version: 001B
BucklePowChip 2 Version: 001B
BuckleBom Version: 000
Reboot Cause: UserReboot
Upgrade restrictions and guidelines
The shipping software of the S9855-48CD8D, S9855-24B8D, S9825-64D, and S9825-64D-H1 switches support automatically upgrading the BootWare and DOM firmware. If the new shipping software includes upgraded BootWare and DOM firmware, the initial boot of the shipping software after the upgrade takes a long time. However, this does not occur on subsequent boots.
Hardware feature updates
Hardware feature updates in R9130
N/A
Hardware feature updates in E9129P02
The H3C S9825-64D-H1 L3 Ethernet switch is supported, which supports sixty-four 400G QSFP-DD ports.
On the S9825-64D-H1 switch, ports 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, and 61 support ZR transceiver modules. When the switch is installed with eight fan trays, ports 3, 4, 7, 8, 11, 12, 15, 16, 19, 20, 23, 24, 27, 28, 31, 32, 35, 36, 39, 40, 43, 44, 47, 48, 51, 52, 55, 56, 59, 60, 63, and 64 support both ZR and ZR+ transceiver modules.
Hardware feature updates in E9129P01
N/A
Hardware feature updates in E9129
The S9855-24B8D also supports 40G transceiver modules.
Hardware feature updates in E9128
The QSFP56-200G-SR4-MM850 module is supported.
Hardware feature updates in F9126P02
N/A
Hardware feature updates in R9126
N/A
Hardware feature updates in E9125
On the S9825-64D switch, ports 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, and 61 support ZR transceiver modules.
The H3C S9855-24B8D L3 Ethernet switch is supported, which supports twenty-four 200G QSFP56 ports and eight 400G QSFP-DD ports.
Hardware feature updates in E9124P02
N/A
Hardware feature updates in E9124P01
N/A
Hardware feature updates in E9124
First release.
Software feature and command updates
See H3C S9855_S9825 Series Ethernet Switches Command Reference and H3C S9855_S9825 Series Ethernet Switches Configuration Guide.
MIB updates
Version number | Item | MIB file | Module name | Remarks |
S9855_9825-CMW910-R9130 | New | None | None | None |
Modified | None | None | None | |
S9855_9825-CMW910-E9129P02 | New | None | None | None |
Modified | None | None | None | |
S9855_9825-CMW910-E9129P01 | New | None | None | None |
Modified | None | None | None | |
S9855_9825-CMW910-E9129 | New | None | None | None |
Modified | None | None | None | |
S9855_9825-CMW910-E9128 | New | None | None | None |
Modified | None | None | None | |
S9855_9825-CMW910-F9126P02 | New | None | None | None |
Modified | None | None | None | |
S9855_9825-CMW910-R9126 | New | None | None | None |
Modified | None | None | None | |
S9855_9825-CMW910-E9125 | New | None | None | None |
Modified | hh3c-entity-vendortype-oid.mib | None | New devices are supported | |
S9855_9825-CMW910-E9124P02 | New | None | None | None |
Modified | None | None | None | |
S9855_9825-CMW910-E9124P01 | New | None | None | None |
Modified | None | None | None | |
S9800X-CMW910-E9124 | New | None | None | First release |
Modified | None | None | First release |
Operation changes
Operation changes in R9130
As from version R9130, you can use the AI ECN feature without installing a license. After downgrading the software from version R9130 to an earlier version, you must re-install and activate the license. If you have uninstalled the license in the earlier version, the license uninstallation information still exists but you can still use the AI ECN feature after you upgrade the software to version R9130.
As from version R9130, you do not need to install a license to use the lossless features.
As from this version, the rail-group keyword in the LBN-related commands is changed to lbn-group. The old and new command syntaxes have the same service configuration method, function, and command output, and differ only in command keywords. For more information, see H3C S9855_9825-CMW910-R9130 Release Notes (Software Feature Changes).
Operation changes in E9129P02
N/A
Operation changes in E9129P01
N/A
Operation changes in E9129
N/A
Operation changes in E9128
N/A
Operation changes in F9126P02
N/A
Operation changes in R9126
N/A
Operation changes in E9125
N/A
Operation changes in E9124P02
N/A
Operation changes in E9124P01
The name of the IPE version file changes from S9800X to S9855_9825.
Operation changes in E9124
Restrictions and cautions
Restrictions
Hardware
· On the S9825-64D switch, only ports 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, and 61 support ZR transceiver modules.
· On the S9825-64D-H1 switch, ports 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, and 61 support ZR transceiver modules. To have ports 3, 4, 7, 8, 11, 12, 15, 16, 19, 20, 23, 24, 27, 28, 31, 32, 35, 36, 39, 40, 43, 44, 47, 48, 51, 52, 55, 56, 59, 60, 63, and 64 support both ZR and ZR+ transceiver modules, install eight fan trays on the switch.
Software
· When you configure mirroring inbound traffic on an aggregation member port of the S9855 switch, the inbound traffic of all member ports in the aggregation group is mirrored to the destination port.
· Before you configure PFC for 802.1p priorities, you cannot disable or enable PFC deadlock detection.
· The M-LAG aggregate interface does not support the arp max-learning-num or nd max-learning-num command.
· Ports on the S9855 switch series are grouped. Make sure each group has up to 18 ports in total after interface splitting.
· Ports on the S9855-24B8D switch are grouped as follows:
¡ Group 1—Ports 1, 2, 3, 4, 5, 7, 26, and 28.
¡ Group 2—Ports 6, 8, 13, 15, 17, 19, 30, and 32.
¡ Group 3—Ports 9, 11, 18, 20, 21, 23, 27, and 29.
¡ Group 4—Ports 10, 12, 14, 16, 22, 24, 25, and 31.
Network configuration
N/A
Cautions
Hardware
N/A
Software
· Enabling IP statistics on an aggregate interface consumes user ACL resources. As a best practice, do not configure IP statistics on an aggregate interface when you have requirements for the user ACL resource usage.
· Before you enable AI ECN, enable gRPC.
· After the S9825 switch series supports VXLAN, the hardware resources of the ARP or ND table in routing mode are halved compared to the earlier versions.
Network configuration
N/A
Licensing
About licensing
H3C offers licensing options for you to deploy features and expand resource capacity on an as needed basis. To use license-based features, purchase licenses from H3C and install the licenses.
For license-based features and attributes of licenses, see H3C Switches License Matrixes.
Registering and installing licenses
H3C License Management Platform provides product licensing services for H3C customers. You can access http://www.h3c.com/en/License to obtain an activation file or transfer licenses.
For information about registering licenses, installing activation files, and transferring licenses, see H3C Switches & Routers Licensing Guide.
Obtaining license server software and documentation
To perform remote licensing, first download and install the H3C license server software.
· To obtain the H3C license server software package, click H3C license server software package
· To obtain H3C license server documentation, click H3C license server documentation
Open problems and workarounds
202402070548
· Symptom: After a device is configured as an INT exit node, the CAR rate limit is inaccurate on the device, and the interfaces might flap.
· Condition: This symptom occurs if a device is configured as an INT exit node and the device receives a large number of INT packets.
· Workaround: Sample INT packets on the INT entry node to reduce the INT packet rate.
202402271891
· Symptom: On an EVPN M-LAG network, the undo mac-address static source-check enable command configuration might be lost for some Layer 3 aggregate interfaces on the S9825 switch. As a result, some VXLAN Layer 3 unicast traffic is dropped.
· Condition: This symptom occurs if the MAC address entries learned by the S9825 switch on the EVPN M-LAG network reach the specifications, and interfaces and routes flap repeatedly.
· Workaround: Execute the mac-address static source-check enable command and then remove this configuration.
List of resolved problems
Resolved problems in R9130
202309261396
· Symptom: The electronic labels for fans 7 and 8 of the S9825-64D-H1 switch fail to be read.
· Condition: This symptom occurs if the S9825-64D-H1 switch is restarted without fans 1 and 2 in place and the system reads the electronic labels of fans.
· Remarks: None.
202403120502
· Symptom: The ifmonitor crc-error command does not take effect on aggregation member ports.
· Condition: This symptom occurs if you assign interfaces to an aggregation group after executing the ifmonitor crc-error command in system view.
· Remarks None.
202402220927
· Symptom: In an M-LAG network, the non-dual-active gateway M-LAG interface on a device cannot establish OSPF sessions with attached devices.
· Condition: This symptom occurs if sFlow is enabled and the ip ttl-expires enable command is executed on the M-LAG aggregate interface on the device.
· Remarks None.
202402200053
· Symptom: Routing protocols do not take effect on a device.
· Condition: This symptom occurs if you configure and activate a global OpenFlow instance.
· Remarks None.
202402180567
· Symptom: The routing service of the S9825 switch is abnormal.
· Condition: This symptom occurs if port 31 of the S9825 switch is split and then the breakout interfaces are combined.
· Remarks: None.
202402291186
· Symptom: In an M-LAG network, the keepalive link might flap.
· Condition: This symptom occurs if the following operations are performed:
a. A device receives a large amount of traffic with unknown sources.
b. Flap the peer-link repeatedly.
· Remarks None.
202402191091
· Symptom: In an EVPN M-LAG network, local EVPN ARP entries remain after the reset arp command is executed.
· Condition: This symptom occurs if traffic triggers ARP entries to migrate from AC interfaces to tunnels.
· Remarks None.
202402261537
· Symptom: A VSI interface forwards traffic abnormally.
· Condition: This symptom occurs if the VSI interface is configured with a learned MAC address.
· Remarks None.
202401031481
· Symptom: When the CfgSessionGroups table is issued by using the edit-config:create operation of NETCONF, the system prompts that the operation failed.
· Condition: This symptom occurs if you use the edit-config:create operation of NETCONF to deploy the CfgSessionGroups table.
· Remarks None.
202403141599
· Symptom: The device might reboot unexpectedly with a low probability.
· Condition: None.
· Remarks None.
Resolved problems in E9129P02
202312010053
· Symptom: Unable to retrieve the complete machine serial number for some sub-nodes of entPhysicalSerialNum (1.3.6.1.2.1.47.1.1.1.1.11).
· Condition: None.
· Remarks None.
202311302015
· Symptom: SNMP pass-through packets are rate-limited when forwarded by switches.
· Condition: The device enables SNMP.
· Remarks None.
202306292104
· Symptom: The CLI gets stuck.
· Condition: The device's port has a damaged optical module inserted.
· Remarks None.
202310231098
· Symptom: Packet priority mappings are incorrect on the S9825 switch.
· Condition: This symptom occurs if a Layer 3 Ethernet interface on the S9825 switch is configured to trust the DSCP values carried in IP packets and the packets are forwarded out that interface.
· Remarks: None.
202312110604
· Symptom: Under VXLAN networking, the encapsulated packets cannot map the values of the inner DSCP and ECN fields to the outer layer.
· Condition: The packets are forwarded through the device from the VXLAN tunnel.
· Remarks None.
202401130257
· Symptom: A BFD session in echo packet mode cannot come up.
· Condition: This symptom occurs if you split the interfaces of two devices, connect them, and configure a BFD session in echo packet mode.
· Remarks None.
Resolved problems in E9129P01
202311071942
· Symptom: Traffic interruption might occur on a Layer 3 Ethernet subinterface.
· Condition: This symptom occurs if you configure both a VLAN interface and a Layer 3 Ethernet subinterface with the same ID as the VLAN interface.
· Remarks None.
202311022024
· Symptom: The congestion notification flag in the packets is modified when no congestion occurs on the device.
· Condition: This symptom occurs if an intermediate device transparently forwards packets at Layer 3 in a VXLAN network.
· Remarks None.
Resolved problems in E9129
202309060951
· Symptom: To have the data compression method for packets of a subscription take effect, you must remove all sensor groups or destination groups from the subscription and then reconfigure the data compression method for packets of the subscription.
· Condition: This symptom occurs if you use the protocol grpc command to change the data compression method for packets of a subscription.
· Remarks None.
202309011856
· Symptom: The next hop state is incorrect for BGP ECMP routes. As a result, traffic forwarding fails.
· Condition: This symptom occurs if the following conditions exist:
¡ On an S-MLAG network, devices in the same S-MLAG group have different AS numbers.
¡ One of the S-MLAG devices experiences repeated uplink or downlink flapping.
· Remarks None.
202309191734
· Symptom: Interfaces on the S9825-64D switch might flap.
· Condition: This symptom occurs if you use the H3C 400G SR8 modules with the S9825-64D switch for interconnect in a rapid temperature change environment.
· Remarks: None.
202310192192
· Symptom: The two breakout links cannot be used separately and must be used together for proper operation.
· Condition: This symptom occurs if a 400G SR8 module is used to split a 400G interface into two 200G interfaces.
· Remarks None.
202310091790
· Symptom: Interfaces on the S9825-64D switch might flap.
· Condition: This symptom occurs if you use the H3C 400G SR8 modules with the S9825-64D switch for interconnect in a rapid temperature change environment.
· Remarks: None.
Resolved problems in E9128
202307270374
· Symptom: After the incorrect cable connection for a port is restored, the peer aggregation member port might flap repeatedly.
· Condition: This symptom occurs if the member port of a dynamic aggregation group is incorrectly connected, which causes the aggregate interface to go down and come up.
· Remarks: None.
202307220335
· Condition: This symptom occurs if SNMP obtains information from the hh3cEntityExtCurrentPower MIB node.
· Remarks: None.
202304122103
· Symptom: The load sharing paths for raw data packets on the device are different from those for packets sampled by INT.
· Condition: This symptom occurs if the following operations are performed on the S9855 switch:
a. Globally enable per-flow load sharing based on IP protocol types.
b. Configure INT on the switch and configure the switch as a transit node.
· Remarks: None.
· Remarks: None.
202303130152
· Symptom: An S9855 switch experiences LLDP neighbor flapping and cannot ping the directly connected device.
· Condition: This symptom occurs if loops exist and a broadcast storm is created.
· Remarks: None
Resolved problems in F9126P02
202303222032
· Symptom: An interface cannot come up after it is split into two breakout interfaces.
· Condition: This symptom occurs if a third-party 200G transceiver module compatible with CMIS is inserted into the interface.
· Remarks: None.
202303310110
· Symptom: A 400G SR8 transceiver module cannot interoperate with 200G SR4 transceiver modules after the interface installed with the 400G SR8 transceiver module is split into two breakout interfaces.
· Condition: This symptom occurs if the 400G SR8 transceiver module is a third-party transceiver module.
· Remarks: None.
202303161054
· Symptom: The CLI is stuck after an aggregate interface-related command is executed.
· Condition: This symptom occurs if a member port changes between the Selected and Unselected states repeatedly.
· Remarks: None.
202303270706
· Symptom: An interface flaps once after you set its FEC mode to autonegotiation.
· Condition: This symptom occurs if you insert a 400G transceiver module into the interface before setting the FEC mode.
· Remarks: None.
202303061910
· Symptom: Repeated NTP server time flapping results in exceptional device reboots.
· Condition: This symptom occurs when the device is enabled with NTP, and repeated NTP server time flapping occurs.
· Remarks: None.
202303061911
· Symptom: Newly added rules cannot take effect after you apply ACL packet filter to an interface.
· Condition: This symptom occurs if you apply QoS and ACL packet filter in resource sharing mode to an interface, and then add new ACL rules.
· Remarks: None.
202303061909
· Symptom: You cannot complete authentication and log in through SSH.
· Condition: This symptom occurs if one of the following situations exists:
¡ For HWTACACS authentication through SSH, the TACACS authentication, authorization, and accounting server uses an IPv6 address. However, the ipv6 keyword is not specified in the configuration at the CLI.
¡ For HWTACACS authentication through SSH, First, the host name and the associated host address are configured with the ip host or ipv6 host command. Then, the username is configured for the HWTACACS authentication, authorization, and accounting server in the HWTACACS scheme.
· Remarks: None.
202303040308
· Symptom: The patch version number obtained through the MIB node does not match the actual patch version installed on the device.
· Condition: This symptom occurs when you obtain the patch version number through MIB node hh3cSysPackageVersion.
· Remarks: None.
202303210152
· Symptom: The server installation through PXE fails.
· Condition: This symptom occurs with a certain probability upon installation through PXE for a server attached to an aggregate edge port on an S9855-48CD8D switch.
· Remarks: None.
202303231647
· Symptom: The device periodically logs insufficient Layer 3 Ethernet interface resources every 24 hours.
· Condition: This symptom occurs when all Ethernet interfaces on the device are configured in Layer 3 mode.
· Remarks: None.
202303210158
· Symptom: Some Layer 3 ports on the device experience forwarding failure.
· Condition: This symptom occurs if both IPv4 and IPv6 addresses are configured on the ports and the ARP/ND entries have changed, which might result in a deadloop or anomaly of the associated threads with a low probability.
· Remarks: None.
202303210154
· Symptom: The HWTACACS authorization command does not include the client's IP address.
· Condition: This symptom occurs when you capture TACACS packets on the IMC server after an HWTACACS user comes online.
· Remarks: None.
202303210155
· Symptom: The initial data return time is 1.x to 2.x times the set subscription interval.
· Condition: This symptom occurs if you configure gRPC dial-in mode and run the gnmi dial-in subscribe tool for xpath subscription.
· Remarks: None.
202303210153
· Symptom: Capture outbound packets on the transit node, and the control latency in INT packets is more than tripled.
· Condition: This symptom occurs when INT is enabled on the S9825-64D device.
· Remarks: None.
202303210160
· Symptom: The device's downlink interface is down, resulting in excessively long convergence time.
· Condition: This symptom occurs if a delay time is configured for generating ARP or ND direct routes on the device.
· Remarks: None.
202303210156
· Symptom: The device does not support splitting a DR4 module to operate with a DR1.
· Condition: None.
· Remarks: None.
202303270707
· Symptom: The DR1/FR1 module occasionally exhibits poor forwarding performance.
· Condition: None.
· Remarks: None.
Resolved problems in R9126
202207070725
· Symptom: When the S9855-48CD8D device receives a pause frame, it will pass it through transparently.
· Condition: None.
· Remarks: None.
202207190943
· Symptom: The device occasionally exhibits data exceptions in port traffic statistics, exceeding the port bandwidth by more than 50 times.
· Condition: This symptom might occur if the device's port is sending and receiving high traffic.
· Remarks: None.
202209211458
· Symptom: Configuration deployment is very slow.
· Condition: This symptom occurs when you set the working frequency for the ZR transceiver module.
· Remarks: None.
202209150200
· Symptom: The sample path data associated with a gRPC subscription is pushed to the collector by other subscriptions.
· Condition: This symptom occurs if multiple gRPC subscriptions are configured each associated with several sample paths.
· Remarks: None.
202207270097
· Symptom: The device reboots unexpectedly in rare cases.
· Condition: This symptom might occur if an anomalous transceiver module is in place, and when the host accesses module register address 0x71-0x7f, the transceiver module abnormally responds with a NACK.
· Remarks: None.
202208010350
· Symptom: The device occasionally fails to start and stops at the boot stage.
· Condition: This symptom occurs if you immediately reboot the device after upgrading its version with the boot-loader command.
· Remarks: None.
202208221066
· Symptom: A PBR policy cannot take effect, because traffic that should match the rules is determined not matching.
· Condition: This symptom might occur if PBR is enabled on an interface of the S9855 switch series.
· Remarks: None.
202210241605
· Symptom: The device sends a DHCPv6 request with incorrect Option 1 information. The DUID in Option 1 contains the DUID type and the MAC address. The DUID type should be 3.
· Condition: This symptom might occur if the device attempts to obtain an IPv6 address through DHCPv6.
· Remarks: None.
202209131249
· Symptom: Some protocols flap, such as BFD.
· Condition: This symptom might occur if PBR is enabled on an interface of the device.
· Remarks: None.
202209140903
· Symptom: An iOptic switch reboots when multiple fiber ports report a large number of interrupt events at the same time.
· Condition: This symptom might occur if a large number of gRPC sampling paths are configured to collect device information.
· Remarks: None.
202209030417
· Symptom: A Layer 3 aggregate interface might not be able to communicate with directly connected interfaces.
· Condition: This symptom might occur if the following operations are performed in sequence on the Layer 3 aggregate interface:
a. Create Layer 3 aggregate subinterfaces.
b. Perform link mode switchover on a member port of the Layer 3 aggregate interface.
· Remarks: None.
Resolved problems in E9125
202108270036
· Symptom: A QoS policy does not mark the DSCP value as 0 for matching packets.
· Condition: This symptom might occur if you apply a QoS policy with an action of marking DSCP value 0 in the outbound direction of the S9825 switch series.
· Remarks: None.
202111110114
· Symptom: The maximum queue length supported by WRED has increased from 16383 to 257862.
· Condition: None.
· Remarks: None.
202201140609
· Symptom: On the S9825-64D switch, when both ECMP hash factors and a hash algorithm are configured, the hash algorithm configuration does not take effect.
· Condition: This symptom might occur if ECMP load sharing has both hash factor settings and hash algorithm settings.
· Remarks: None.
202112170074
· Symptom: On the S9855-48CD8D switch, when link aggregation and ECMP use the ip-pro setting for hash calculation, the Option field of TCP packets is incorrectly included in the hash calculation.
· Condition: This symptom might occur if the ip-pro keyword is specified for hash calculation.
· Remarks: None.
202201070143
· Symptom: The configuration method for shift entries has been optimized for chips.
· Condition: None.
· Remarks: None.
202112300706
· Symptom: The buffer apply command fails to apply manually configured data buffer settings.
· Condition: This symptom might occur if the buffer resource limit set by the priority-flow-control poolid headroom command is too high.
· Remarks: None.
202203110256
· Symptom: When the S9825-64D switch works conjunction with a Hisense 400G SR8 transceiver module, the device might keep generating alarm messages about the transceiver module.
· Condition: This symptom might occur if the S9825-64D switch works conjunction with a Hisense 400G SR8 transceiver module
· Remarks: None.
202203160006
· Symptom: The S9825-64D device experiences occasional direct connection ping failures, with protocol packet forwarding being rate limited when passing through.
· Condition: This symptom might occur if the passthrough protocol packets use ECMP index 1 for forwarding, and the total number of passthrough protocol packets and the protocol packets sent to the local CPU exceeds the rate limit for packet delivery to the CPU.
· Remarks: None.
202203301352
· Symptom: The command output fails if you use the display packet-drop interface command to view packet drop information on an interface.
· Condition: None.
· Remarks: None.
Resolved problems in E9124P02
202107120746
· Symptom: When the device receives PFC packets for a queue where the no-drop feature is not enabled, the traffic for that queue will also be rate limited.
· Condition: This symptom might occur when the device receives PFC packets for a queue where the no-drop feature is not enabled.
· Remarks: None.
Resolved problems in E9124P01
202106071334
· Symptom: In packet filtering, ACL rule matching for packet statistics is abnormal.
· Condition: This symptom might occur if the interface is configured with more than 128 rules enabled with the software statistics feature for rule matching.
· Remarks: None.
202106071336
· Symptom: The maximum allowed packet length for jumbo frames outgoing from the device is 9216 bytes, including the VLAN tag.
· Condition: This symptom might occur because the incoming packets do not contain VLAN tags and the outgoing packets contain VLAN tags and the incoming direction supports packets of a maximum of 9212 bytes.
· Remarks: None.
202106071350
· Symptom: The network management software fails to parse sFlow packets, preventing network traffic monitoring via sFlow.
· Condition: This symptom might occur if sFlow is configured and sFlow packets are sent to the network management software for parsing.
· Remarks: None.
202106091531
· Symptom: The device freezes when you view the current configuration, and connections to NMS or SNMP to retrieve MIB node information also result in timeouts.
· Condition: This symptom might occur if you configure two gRPC target groups and two gRPC subscriptions on the device.
· Remarks: None.
202106160738
· Symptom: DHCPv6 automatic configuration through HTTP failed.
· Condition: None.
· Remarks: None.
202106170683
· Symptom: When the device starts up and attempts to obtain configurations automatically through DHCPv4, it gets stuck and the system prompts "Automatic configuration is executing the configuration file. Please wait..."
· Condition: This symptom might occur during the automatic configuration process if a network disconnection occurs with the configuration server.
· Remarks: None.
Resolved problems in E9124
First release.
Troubleshooting resources
Access https://www.h3c.com/en/Support/Resource_Center/Technical_Documents/, select the device category and model, and search for troubleshooting guide in the Maintain section.
Related documentation
Related documents
· H3C S9855&S9825 Switch Series Installation Guide
· H3C S9825&S9855 Switch Series Hardware Information and Specifications
· H3C S9855&S9825 Switch Series Installation Quick Start
· H3C S9855&S9825 Switch Series Command References
· H3C S9855&S9825 Switch Series Configuration Guides
Obtaining documentation
To obtain the latest documents, go to the H3C website www.h3c.com\en.
1. Access https://www.h3c.com/en/Support/Resource_Center/Technical_Documents/
2. Select the product category and product model. Then, you can search for and download documents related to the product.
Technical support
Email: [email protected]
Website: http://www.h3c.com\en
Item | Description |
Dimensions (H × W × D) | S9855-48CD8D: 44 × 440 × 660 mm (1.73 × 17.32 × 25.98 in) S9855-24B8D: 44 × 440 × 660 mm (1.73 × 17.32 × 25.98 in) S9825-64D: 175 × 440 × 760 mm (6.89 × 17.32 × 29.92 in) S9825-64D-H1: 175 × 440 × 760 mm (6.89 × 17.32 × 29.92 in) |
Weight (fully configured) | S9855-48CD8D: 12.2 kg (26.90 lb) S9855-24B8D: 12.2 kg (26.90 lb) S9825-64D: 37 kg (81.57 lb) S9825-64D-H1: 38.4 kg (84.66 lb) |
Console ports | 1 |
Management Ethernet ports | 1 |
USB ports | 1 |
Pluggable power supplies | S9855-48CD8D: 2 S9855-24B8D: 2 S9825-64D: 4 S9825-64D-H1: 4 |
Pluggable fans | S9855-48CD8D: 6 (air outlet at the fan panel side) S9855-24B8D: 6 (air outlet at the fan panel side) S9825-64D: 6 (air inlet at the port side and air outlet at the fan panel side) S9825-64D-H1: 8 (air inlet at the port side and air outlet at the fan panel side) |
Supported pluggable power supply models | PSR1600C-12A-B |
Supported pluggable fan models | S9855-48CD8D: FAN-40B-1-C S9855-24B8D: FAN-40B-1-C S9825-64D: FAN-80B-1-B S9825-64D-H1: FAN-80B-1-B |
Interface cable media and maximum transmission distance | QSFPDD-400G-SR8-MM850: 100 m (328.08 ft) QSFPDD-400G-FR4-WDM1300: 2 km (1.24 miles) CAB-400G-QSFP-DD-2m: 2 m (6.56 ft) QSFP56-200G-SR4-MM850: 100 m (328.08 ft) QSFP-100G-SR4-MM850: 100 m (328.08 ft) QSFP-100G-eSR4-MM850: 300 m (984.25 ft) QSFP-100G-PSM4-SM1310: 500 m (1640.42 ft) QSFP-100G-SWDM4-MM850: 100 m (328.08 ft) QSFP-100G-LR4L-WDM1300: 2 km (1.24 miles) QSFP-100G-LR4-WDM1300: 10 km (6.21 miles) QSFP-100G-D-CAB-1M: 1 m (3.28 ft) QSFP-100G-D-CAB-3M: 3 m (9.84 ft) QSFP-100G-D-CAB-5M: 5 m (16.40 ft) QSFP-100G-D-AOC-7M: 7 m (22.97 ft) QSFP-100G-D-AOC-10M: 10 m (32.81 ft) QSFP-100G-D-AOC-20M: 20 m (65.62 ft) QSFP-100G-4SFP-25G-CAB-1M: 1 m (3.28 ft) QSFP-100G-4SFP-25G-CAB-3M: 3 m (9.84 ft) QSFP-100G-4SFP-25G-CAB-5M: 5 m (16.40 ft) SFP-25G-SR-MM850: 100 m (328.08 ft) SFP-25G-LR-SM1310: 10 km (6.21 miles) SFP-25G-D-CAB-1M: 1 m (3.28 ft) SFP-25G-D-CAB-3M: 3 m (9.84 ft) SFP-25G-D-CAB-5M: 5 m (16.40 ft) SFP-25G-D-AOC-3M: 3 m (9.84 ft) SFP-25G-D-AOC-5M: 5 m (16.40 ft) SFP-25G-D-AOC-7M: 7 m (22.97 ft) SFP-25G-D-AOC-10M: 10 m (32.81 ft) SFP-25G-D-AOC-20M: 20 m (65.62 ft) QSFP-40G-LR4-WDM1300 QSFP-40G-CSR4-MM850: 300 m (984.25 ft) QSFP-40G-SR4-MM850: 100 m (328.08 ft) QSFP-40G-BIDI-SR-MM850: 100 m (328.08 ft) QSFP-40G-LR4L-WDM1300: 2 km (1.24 miles) QSFP-40G-ER4-WDM1300: 40 km (24.86 miles) QSFP-40G-D-AOC-7M: 7 m (22.97 ft) QSFP-40G-D-AOC-10M: 10 m (32.81 ft) QSFP-40G-D-AOC-20M: 20 m (65.62 ft) QSFPDD-400G-SR4-MM850 |
Input voltage | 100 to 240 VAC at 50/60Hz 180 to 320 VDC |
Power consumption (typical) | S9855-48CD8D: 329 W S9855-24B8D: 263 W S9825-64D: 734 W S9825-64D-H1: 564 W |
Operating temperature | 0°C to 40°C (32°F to 104°F) |
5 to 95% RH, noncondensing |
Category | Features |
Fundamentals | · CLI · RBAC · Login Management · FTP and TFTP · File System Management · Configuration File Management · Software Upgrade · Automatic Configuration |
License | · License |
System Management | · Basic Device Management · Device Hardening · Hardware Resource Management · Process Monitoring and Maintenance · Information Center |
Interface | · Bulk interface · Ethernet interface · Loopback, Null, and Inloopback Interfaces · Tunnel interface |
Layer 2—LAN Switching | · MAC Address Table · Ethernet Link Aggregation · M-LAG · Port isolation · VLAN · QinQ · Spanning Tree · LLDP · Loop Detection · PFC · Service Loopback Group |
Layer 3—IP Services | · ARP · IP Addressing · DHCP · IP Forwarding Basics · IP Performance Optimization · IPv6 Basics · IPv6 Neighbor Discovery · DHCPv6 · IPv6 transition technologies |
Layer 3—IP Routing | · IP Routing Basics · Static Routing · RIP · OSPF · IS-IS · Basic BGP · Advanced BGP · Policy-Based Routing · IPv6 Static Routing · RIPng · OSPFv3 · IPv6 Policy-Based Routing · Routing Policy · DCN |
MCE | · MCE |
ACL and QoS | · ACL · QoS · Time Range · Data Buffer |
IP Tunneling | · GRE · IPv4 over IPv4 tunneling · IPv6 over IPv6 tunneling |
User Access and Authentication | · AAA · Password control |
Security | · SSH · Packet Filter · DHCP Snooping · ARP Attack Protection · ND Attack Defense · IP-Based Attack Prevention |
High Availability | · Monitor Link · BFD · VRRP |
Network Management and Monitoring | · Ping and Tracert · System Debugging · NQA · NTP · SNMP · Sampler · Mirroring · NetStream · IPv6 NetStream · sFlow · NetAnalysis · Packet Capture |
Telemetry | · gRPC · INT · Flow Group · MOD · Telemetry Stream |
Network Programmability | · RESTful · Tcl · Python · NETCONF |
VXLAN | · Basic VXLAN · VXLAN IP gateway · VXLAN DCI |
EVPN | · Basic EVPN · EVPN VXLAN · EVPN-DCI |
OpenFlow | · OpenFlow |
| NOTE: Version S9855_S9825 supports the following proprietary protocols: NQA (udp-jitter, udp-echo, and voice). For more information, see the command references and configuration guides. |
Appendix B Fixed security vulnerabilities
Fixed security vulnerabilities in R9130
None.
Fixed security vulnerabilities in E9129P02
None.
Fixed security vulnerabilities in E9129P01
None.
Fixed security vulnerabilities in E9129
None.
Fixed security vulnerabilities in E9128
None.
Fixed security vulnerabilities in F9126P02
CVE-2022-2153
A flaw was found in the Linux kernel KVM when attempting to set a SynIC IRQ. This issue makes it possible for a misbehaving VMM to write to SYNIC/STIMER MSRs, causing a NULL pointer dereference. This flaw allows an unprivileged local attacker on the host to issue specific ioctl calls, causing a kernel oops condition that results in a denial of service.
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.
CVE-2020-8231
Due to use of a dangling pointer, libcurl 7.29.0 through 7.71.1 can use the wrong connection when sending data.
Fixed security vulnerabilities in R9126
CVE-2022-0435
A stack overflow flaw was found in the Linux kernel's TIPC protocol functionality in the way a user sends a packet with malicious content where the number of domain member nodes is higher than the 64 allowed. This flaw allows a remote user to crash the system or possibly escalate their privileges if they have access to the TIPC network.
CVE-2001-0554
Buffer overflow in BSD-based telnetd telnet daemon on various operating systems allows remote attackers to execute arbitrary commands via a set of options including AYT (Are You There), which is not properly handled by the telrcv function.
CVE-2003-1069
The Telnet daemon (in.telnetd) for Solaris 2.6 through 9 allows remote attackers to cause a denial of service (CPU consumption by infinite loop).
CVE-2022-25375
An issue was discovered in drivers/usb/gadget/function/rndis.c in the Linux kernel before 5.16.10. The RNDIS USB gadget lacks validation of the size of the RNDIS_MSG_SET command. Attackers can obtain sensitive information from kernel memory.
CVE-2022-0322
A flaw was found in the sctp_make_strreset_req function in net/sctp/sm_make_chunk.c in the SCTP network protocol in the Linux kernel with a local user privilege access. In this flaw, an attempt to use more buffer than is allocated triggers a BUG_ON issue, leading to a denial of service (DOS).
CVE-2021-3772
A flaw was found in the Linux SCTP stack. A blind attacker may be able to kill an existing SCTP association through invalid chunks if the attacker knows the IP-addresses and port numbers being used and the attacker can send packets with spoofed IP addresses.
CVE-2022-1055
A use-after-free exists in the Linux Kernel in tc_new_tfilter that could allow a local attacker to gain privilege escalation. The exploit requires unprivileged user namespaces.
CVE-2021-4203
A use-after-free read flaw was found in sock_getsockopt() in net/core/sock.c due to SO_PEERCRED and SO_PEERGROUPS race with listen() (and connect()) in the Linux kernel. In this flaw, an attacker with a user privileges may crash the system or leak internal kernel information.
CVE-2022-25636
net/netfilter/nf_dup_netdev.c in the Linux kernel 5.4 through 5.6.10 allows local users to gain privileges because of a heap out-of-bounds write. This is related to nf_tables_offload.
A startup software image is a program file used to boot the device. The S9855&S9825 switch series supports the following startup software images:
· Main startup image—By default, a device uses the main startup image to boot the device.
· Backup startup image—When the main startup image is not available, the device uses the backup startup image to boot the device.
Typically, a startup software image is a .bin file, for example, main.bin.
Upgrade method | Remarks |
Upgrading the startup software image from the CLI | You must reboot the device to complete the upgrade. This method interrupts switch services. |
Upgrading the startup software image from the BootWare menu | Use this method when the device cannot start up correctly. |
| IMPORTANT: You must reboot the switch after upgrading its startup image. During the reboot, the switch cannot provide any services. |
Before you upgrade the startup software image, complete the following tasks:
· Configure routes to make sure that the switch and the file server can reach each other.
· Enable the TFTP or FTP server on the file server.
· Log in to the CLI through a configuration terminal.
· Copy the target startup software image for upgrade to the file server and correctly set the access path of the TFTP or FTP server.
Upgrading the startup software image from the CLI
Using TFTP to upgrade the startup software image
The switch acts as the TFTP client to access the specified path on the TFTP server and complete the backup and upgrade operations for the startup software image. Perform the following tasks:
Backing up the current startup image and configuration file
1. Execute the save command in any view to save the running configuration of the switch.
<Sysname> save
The current configuration will be written to the device. Are you sure? [Y/N]:y
Please input the file name(*.cfg)[flash:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):
flash:/startup.cfg exists, overwrite? [Y/N]:y
Validating file. Please wait...
Saved the current configuration to mainboard device successfully.
<Sysname>
2. Execute the dir command in user view to display the startup image name, configuration file name, and the free space size of the flash memory. Make sure the flash memory has sufficient space for the new startup image.
<Sysname> dir
Directory of flash: (VFAT)
0 -rw- 249275392 May 26 2021 06:06:18 main.bin
1 drw- - May 18 2021 06:37:08 diagfile
2 -rw- 5506 May 17 2021 08:27:36 ifindex.dat
3 drw- - May 10 2021 02:37:00 logfile
4 drw- - Mar 19 2021 11:23:02 seclog
5 -rw- 5221 Mar 30 2021 19:18:48 startup.cfg
6 -rw- 87646 Mar 30 2021 19:18:48 startup.mdb
7 drw- - Apr 09 2021 16:00:20 third-party
8 drw- - Apr 15 2021 12:35:52 versionInfo
234275200 KB total (233932544 KB free)
<Sysname>
3. Execute the tftp put command in user view to back up startup image main.bin to the TFTP file server.
<Sysname> tftp 192.168.1.1 put main.bin
Press CTRL+C to abort.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 237M 0 0 100 237M 0 422k --:--:-- --:--:-- --:--:-- 426k
<Sysname>
4. Execute the tftp put command in user view to back up configuration file startup.cfg to the TFTP file server.
<Sysname> tftp 192.168.1.1 put startup.cfg
Press CTRL+C to abort.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 5221 0 0 100 5221 0 270k --:--:-- --:--:-- --:--:-- 319k
<Sysname>
Upgrading the startup software image
1. Execute the tftp get command in user view to import startup image S9855_9825.ipe to the flash memory of the switch.
<Sysname> tftp 192.168.1.1 get S9855_9825.ipe
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 237.1M 100 237.1M 0 0 1193k 0 0:00:50 0:00:50 --:--:-- 1127k
<Sysname>
2. Execute the boot-loader command in user view to specify file S9855_9825.ipe as the main next-startup image.
<Sysname> boot-loader file flash:/S9855_9825.ipe slot 1 main
Verifying the file flash:/S9855_9825.ipe on slot 1...Done.
H3C S9855-48CD8D images in IPE:
S9855_9825-CMW910-BOOT-test.bin
S9855_9825-CMW910-SYSTEM-test.bin
This command will set the main startup software images. Continue? [Y/N]:y
Add images to slot 1.
Decompressing file S9855_9825-CMW910-BOOT-test.bin to
flash:/S9855_9825-CMW910-BOOT-test.bin...Done.
Decompressing file S9855_9825-CMW910-SYSTEM-test.bin to
flash:/S9855_9825-CMW910-SYSTEM-test.bin...Done.
Verifying the file flash:/S9855_9825-CMW910-BOOT-test.bin on slot 1...Done.
Verifying the file flash:/S9855_9825-CMW910-SYSTEM-test.bin on slot 1...Done.
The images that have passed all examinations will be used as the main startup so
ftware images at the next reboot on slot 1.
Decompression completed.
You are recommended to delete the .ipe file after you set startup software image
s for all slots.
Do you want to delete flash:/S9855_9825.ipe now? [Y/N]:y
<Sysname>
3. Execute the display boot-loader command in user view to display startup software images.
<Sysname> display boot-loader
Software images on slot 1:
Current software images:
flash:/S9855_9825-CMW910-boot-test.bin
flash:/S9855_9825-CMW910-system-test.bin
Main startup software images:
flash:/S9855_9825-CMW910-boot-test.bin
flash:/S9855_9825-CMW910-system-test.bin
Backup startup software images:
None
<Sysname>
The output shows that the next-startup software images are S9855_9825-CMW910-boot-test.bin and S9855_9825-CMW910-system-test.bin.
4. Execute the reboot command in user view to reboot the switch.
<Sysname> reboot
Start to check configuration with next startup configuration file, please wait..
.......DONE!
Current configuration may be lost after the reboot, save current configuration?
[Y/N]:y
Please input the file name(*.cfg)[flash:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):
flash:/startup.cfg exists, overwrite? [Y/N]:y
Validating file. Please wait...
Saved the current configuration to mainboard device successfully.
This command will reboot the device. Continue? [Y/N]:y
Now rebooting, please wait...
.
System is Starting...
5. After the switch reboots, execute the display version command to verify that the startup software images have been upgraded to the target version.
Using FTP to upgrade the startup software image
The switch acts as the FTP client to access the specified path on the FTP server and complete the backup and upgrade operations for the startup software image. Perform the following tasks:
Backing up the current startup image and configuration file
1. Execute the save command in any view to save the running configuration of the switch.
<Sysname> save
The current configuration will be written to the device. Are you sure? [Y/N]:y
Please input the file name(*.cfg)[flash:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):
flash:/startup.cfg exists, overwrite? [Y/N]:y
Validating file. Please wait...
Saved the current configuration to mainboard device successfully.
<Sysname>
2. Execute the dir command in user view to display the startup image name, configuration file name, and the free space size of the flash memory. Make sure the flash memory has sufficient space for the new startup image.
<Sysname> dir
Directory of flash: (VFAT)
0 -rw- 249275392 May 26 2021 06:06:18 main.bin
1 drw- - May 18 2021 06:37:08 diagfile
2 -rw- 5506 May 17 2021 08:27:36 ifindex.dat
3 drw- - May 10 2021 02:37:00 logfile
4 drw- - Mar 19 2021 11:23:02 seclog
5 -rw- 5221 Mar 30 2021 19:18:48 startup.cfg
6 -rw- 87646 Mar 30 2021 19:18:48 startup.mdb
7 drw- - Apr 09 2021 16:00:20 third-party
8 drw- - Apr 15 2021 12:35:52 versionInfo
234275200 KB total (233932544 KB free)
<Sysname>
3. Execute the ftp command in user view to log in to the FTP server. Enter the username and password upon prompt.
<Sysname> ftp 192.168.1.1
Press CTRL+C to abort.
Connected to 192.168.1.1 (192.168.1.1).
220 WFTPD 2.0 service (by Texas Imperial Software) ready for new user
User (192.168.1.1:(none)): zhangsan
331 Give me your password, please
Password:
230 Logged in successfully
Remote system type is MSDOS.
ftp>
4. Execute the put command in FTP client view to back up startup image main.bin to the FTP server.
ftp> binary
200 Type is Image (Binary)
ftp> put main.bin
227 Entering Passive Mode (192,168,1,1,194,82)
150 "E:\main.bin " file ready to receive in IMAGE / Binary mode
226 Transfer finished successfully.
148144128 bytes sent in 43.119 seconds (3.27 Mbytes/s)
ftp>
5. Execute the put command in FTP client view to back up configuration file startup.cfg to the FTP server.
ftp> put startup.cfg
227 Entering Passive Mode (192,168,2,79,194,99)
150 "E:\startup.cfg" file ready to receive in IMAGE / Binary mode
226 Transfer finished successfully.
5221 bytes sent in 0.001 seconds (9.46 Mbytes/s)
ftp>
Upgrading the startup software image
1. Execute the get command in FTP client view to import startup image S9855_9825.ipe to the flash memory of the switch.
ftp> get S9855_9825.ipe
227 Entering Passive Mode (192,168,1,1,223,253)
150 "E:\S9855_9825.ipe" file ready to send (249275392 bytes) in IMAGE / Binary mode
...........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
226 Transfer finished successfully.
249275392 bytes received in 9.203 seconds (25.83 Mbytes/s)
ftp>
2. Execute the quit command in FTP client view to return to user view.
ftp> quit
221 Windows FTP Server (WFTPD, by Texas Imperial Software) says goodbye
<Sysname>
3. Execute the boot-loader command in user view to specify file S9855_9825.ipe as the main next-startup image.
<Sysname> boot-loader file flash:/S9855_9825.ipe slot 1 main
Verifying the file flash:/S9855_9825.ipe on slot 1...Done.
H3C S9855-48CD8D images in IPE:
S9855_9825-CMW910-BOOT-test.bin
S9855_9825-CMW910-SYSTEM-test.bin
This command will set the main startup software images. Continue? [Y/N]:y
Add images to slot 1.
Decompressing file S9855_9825-CMW910-BOOT-test.bin to
flash:/S9855_9825-CMW910-BOOT-test.bin...Done.
Decompressing file S9855_9825-CMW910-SYSTEM-test.bin to
flash:/S9855_9825-CMW910-SYSTEM-test.bin...Done.
Verifying the file flash:/S9855_9825-CMW910-BOOT-test.bin on slot 1...Done.
Verifying the file flash:/S9855_9825-CMW910-SYSTEM-test.bin on slot 1...Done.
The images that have passed all examinations will be used as the main startup so
ftware images at the next reboot on slot 1.
Decompression completed.
You are recommended to delete the .ipe file after you set startup software image
s for all slots.
Do you want to delete flash:/S9855_9825.ipe now? [Y/N]:y
<Sysname>
4. Execute the display boot-loader command in user view to display startup software images.
<Sysname> display boot-loader
Software images on slot 1:
Current software images:
flash:/S9855_9825-CMW910-boot-test.bin
flash:/S9855_9825-CMW910-system-test.bin
Main startup software images:
flash:/S9855_9825-CMW910-boot-test.bin
flash:/S9855_9825-CMW910-system-test.bin
Backup startup software images:
None
<Sysname>
The output shows that the next-startup software images are S9855_9825-CMW910-boot-test.bin and S9855_9825-CMW910-system-test.bin.
5. Execute the reboot command in user view to reboot the switch.
<Sysname> reboot
Start to check configuration with next startup configuration file, please wait..
.......DONE!
Current configuration may be lost after the reboot, save current configuration?
[Y/N]:y
Please input the file name(*.cfg)[flash:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):
flash:/startup.cfg exists, overwrite? [Y/N]:y
Validating file. Please wait...
Saved the current configuration to mainboard device successfully.
This command will reboot the device. Continue? [Y/N]:y
Now rebooting, please wait...
.
System is Starting...
6. After the switch reboots, execute the display version command to verify that the startup software images have been upgraded to the target version.
Upgrading the startup software image from the BootWare menu
Accessing the BootWare main menu
BootWare main menu
When the switch starts up or reboots, the configuration terminal displays the following information:
System is Starting...
BIOS Version : 1.04
Press Ctrl+D to access BIOS MENU
Press Ctrl+T to access BOOTWARE DIAG-TEST MENU
BIOS Boot H3C System
Loading ... OK
********************************************************************************
* *
* BOOTROM, Version 104 *
* *
********************************************************************************
Creation Date : Jun 21 2021
Memory Type : DDR4 SDRAM
Memory Size : 16384MB
Memory Speed : 2133MHz
usba0 Size : 7388MB
flash Size : 228936MB
CPLD 1 Version : 001
CPLD 2 Version : 001
CPLD 3 Version : 001
CPLD 4 Version : 001
PCB 1 Version : Ver.A
PCB 2 Version : Ver.B
Mac Address : 000000000000
BootRom Validating...
Press Ctrl+B to access EXTENDED BOOT MENU...
| NOTE: · For readability and ease of understanding, unless otherwise indicated, this menu is referred to as the BootWare main menu. · The output information might vary by device. |
Press Ctrl+B when the "Press Ctrl+B to access EXTENDED BOOT MENU..." prompt message appears to access the BootWare main menu.
EXTENDED BOOT MENU
1. Download image to flash
2. Select image to boot
3. Display all files in flash
4. Delete file from flash
5. Restore to factory default configuration
6. Enter BootRom upgrade menu
7. Skip current system configuration
8. Set switch startup mode
9. Set default boot storage medium
0. Reboot
Ctrl+F: Format file system
Ctrl+P: Change authentication for console login
Ctrl+R: Download image to SDRAM and run
Ctrl+C: Display Copyright
Enter your choice(0-9):
Option | Description |
1. Download image to flash | Download files to the flash memory. |
2. Select image to boot | Select startup images. |
3. Display all files in flash | Display all files on the flash memory. |
4. Delete file from flash | Delete files on the flash memory. |
5. Restore to factory default configuration | Restore factory defaults. |
6. Enter BootRom upgrade menu | Access the BootROM upgrade submenu. |
7. Skip current system configuration | Skip the current configuration file. This option is not available if password recovery is disabled. |
8. Set switch startup mode | Set the BootROM startup wait time. |
9. Set default boot storage medium | Configure the default storage medium. |
0. Reboot | Reboot the device. |
Using the network management interface to upgrade the startup software image through TFTP/ FTP
1. Configure file downloading parameters.
Press 1 in the BootWare main menu to configure the file downloading option.
1. Set TFTP protocol parameters
2. Set FTP protocol parameters
3. Set XMODEM protocol parameters
0. Return to boot menu
Enter your choice(0-3):
Select a downloading mode. In this example, FTP is selected.
Load File Name :S9855_9825-CMW910-test.ipe
:
Server IP Address :192.168.1.100
Local IP Address :192.168.1.66
Subnet Mask :0.0.0.0
Gateway IP Address :0.0.0.0
FTP User Name :user
FTP User Password :******
Table 8 File downloading parameters
Field | Description |
Load File Name | Name of the file to be downloaded. |
Server IP Address | IP address of the TFTP or FTP server. |
Local IP Address | Local IP address, which is the IP address of the TFTP/FTP client. |
Gateway IP Address | Gateway IP address. You must configure a gateway address if the device and the server do not belong to the same subnet. |
FTP User Name | FTP username. This field is not displayed for TFTP. |
FTP User Password | FTP password. This field is not displayed for TFTP. |
2. After configuring the parameters, select Y to start transmission.
Are you sure to download file to flash? Yes or No (Y/N):Y
Loading........................................................................
.................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................Done.
Please input the file attribute (Main/Backup/None) m
Image file S9855_9825-CMW910-BOOT-test.bin is self-decompressing...
Free space: 239878340608 bytes
Writing flash...................................................................
................................................................Done.
Image file S9855_9825-CMW910-SYSTEM-test.bin is self-decompressing...
Free space: 239744253952 bytes
Writing flash...................................................................
................................................................................
...............................................................................
Done.
3. After the file is downloaded, the system opens BootWare main menu. Select 0 to boot the system with the new image.
Performing file management from the BootWare menu
Displaying all files
Press 3 in the BootWare main menu to select the file display option.
Display all file(s) in flash:
File Number File Size(bytes) File Name
================================================================================
1(*) 134064128 flash:/s9855_9825-cmw910-boot-test.bin
2(*) 232133632 flash:/s9855_9825-cmw910-system-test.bin
3 336600 flash:/logfile/logfile1.log
4 1194 flash:/diagfile/diagfile1.log
5 16 flash:/versioninfo/versionctl.dat
6 1056 flash:/versioninfo/version0.dat
7 536 flash:/versioninfo/version1.dat
8 796 flash:/versioninfo/version2.dat
9 536 flash:/versioninfo/version3.dat
10 1056 flash:/versioninfo/version4.dat
11 9562 flash:/ifindex.dat
12 14528 flash:/startup.cfg
13 312394 flash:/startup.mdb
14 18 flash:/.privatedata.main
Free space: 239529885696 bytes
The current image is S9855_9825-CMW910-BOOT-test.bin
(*)-with main attribute
(b)-with backup attribute
(*b)-with both main and backup attribute
Configuring the file type
A file acting as both the main and backup images is a *b file. You can edit the *, b, or *b file type in the BootWare menu. For the * and b file types, only one file is supported on a device. For example, if a boot software package file of the *b type exists in the flash memory, the flash memory does not support any other boot software package files of the * or b type. If you change the file type of another boot software package file to b, the previous *b type boot software package file becomes a * type file.
On the startup file selection submenu, press 2 to configure the startup image type.
File Number File Size(bytes) File Name
================================================================================
1(*) 140948480 flash:/s9855_9825-cmw910-boot-test.bin
2(*) 108319744 flash:/s9855_9825-cmw910-system-test.bin
Free space: 239546073088 bytes
(*)-with main attribute
(b)-with backup attribute
(*b)-with both main and backup attribute
Note:Select .bin files. One but only one boot image and system image must be
included.
Enter file No.(Allows multiple selection):
Enter the number of the file to be edited, and then press Enter. Then, you can edit the file type.
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:
flash:/s9855_9825-cmw910-boot-test.bin
flash:/s9855_9825-cmw910-system-test.bin
Please input the file attribute (Main/Backup)m
This operation may take several minutes. Please wait....
Next time, s9855_9825-cmw910-boot-test.bin will become default boot file!
Next time, s9855_9825-cmw910-system-test.bin will become default boot file!
After you configure the file type successfully, the system displays the following information:
Set the file attribute success!
Deleting files
Press 4 in the BootWare main menu to select the file deletion option.
Deleting the file in flash:
File Number File Size(bytes) File Name
================================================================================
1(*) 134064128 flash:/s9855_9825-cmw910-boot-test.bin
2(*) 232133632 flash:/s9855_9825-cmw910-system-test.bin
3 336600 flash:/logfile/logfile1.log
4 1194 flash:/diagfile/diagfile1.log
5 16 flash:/versioninfo/versionctl.dat
6 1056 flash:/versioninfo/version0.dat
7 536 flash:/versioninfo/version1.dat
8 796 flash:/versioninfo/version2.dat
9 536 flash:/versioninfo/version3.dat
10 1056 flash:/versioninfo/version4.dat
11 9562 flash:/ifindex.dat
12 14528 flash:/startup.cfg
13 312394 flash:/startup.mdb
14 18 flash:/.privatedata.main
Free space: 239529885696 bytes
The current image is S9855_9825-CMW910-BOOT-test.bin
(*)-with main attribute
(b)-with backup attribute
(*b)-with both main and backup attribute
Please input the file number to change:
Enter the number of the file to be deleted, and then press Enter. The system displays the following information if the file is deleted successfully:
Please input the file number to change: 3
The file you selected is logfile/logfile1.log,Delete it? (Y/N):Y
Deleting....Done.
Handling software upgrade failures
If a software upgrade fails, the system runs the old software version. To handle a software failure:
1. Check the physical ports for a loose or incorrect connection.
2. If you are using the console port for file transfer, check the HyperTerminal settings (including the baud rate and data bits) for any wrong setting.
3. Check the file transfer settings:
¡ If XMODEM is used, you must set the same baud rate for the terminal as for the console port.
¡ 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.
4. Check the FTP or TFTP server for any incorrect setting.
5. Check that the storage device has sufficient space for the upgrade file.
6. If the message “Something is wrong with the file” appears, check the file for file corruption.
