Download

Title	Size	Downloads
S5590EI-CMW710-R8615P05.rar	1.20 GB
S5590EI-CMW710-R8615P05 MD5.rar	0.85 KB
H3C S5590EI-CMW710-R8615P05 Release Notes.pdf	1.51 MB
H3C S5590EI-CMW710-R8615P05 Release Notes (Software Feature Changes).pdf	3.05 MB

H3C S5590EI-CMW710-R8615P05

Release Notes

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.

The information in this document is subject to change without notice.

Contents

Introduction· 1

Version information· 1

Version number 1

Version history· 1

Hardware and software compatibility matrix· 2

ISSU upgrade type matrix· 3

Upgrade advice· 4

Upgrade restrictions and guidelines· 4

Hardware feature updates· 4

Software feature and command updates· 5

MIB updates· 5

Operation changes· 6

Operation changes in R8615P05· 6

Operation changes in R8615P03· 6

Operation changes in R8336P11· 6

Operation changes in R8336P09~R8336P06· 6

Operation changes in R8336P05· 6

Operation changes in R8307P57~R8307P08· 6

Operation changes in R8307P06· 6

Operation changes in R8108P26· 7

Operation changes in R8108P25~R6010P08· 7

Operation changes in R6010P04· 7

Restrictions and cautions· 7

Registering and installing licenses· 9

Open problems and workarounds· 9

List of resolved problems· 10

Resolved problems in R8615P05· 10

Resolved problems in R8615P03· 13

Resolved problems in R8336P11· 19

Resolved problems in R8336P09· 27

Resolved problems in R8336P06· 30

Resolved problems in R8336P05· 32

Resolved problems in R8307P60· 37

Resolved problems in R8307P57· 40

Resolved problems in R8307P55· 41

Resolved problems in R8307P53· 42

Resolved problems in R8307P10· 44

Resolved problems in R8307P09· 46

Resolved problems in R8307P08· 46

Resolved problems in R8307P06· 48

Resolved problems in R8108P26· 49

Resolved problems in R8108P25· 53

Resolved problems in R8108P22· 56

Resolved problems in R6010P08· 61

Resolved problems in R6010P04· 62

Troubleshooting resources· 62

Introduction

This document describes the features, restrictions and guidelines, open problems, and workarounds for version S5590EI-CMW710-R8615P05. 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 the documents listed in "Related documentation."

Version information

Version number

H3C Comware Software, Version 7.1.070, Release 8615P05.

NOTE:

To identify the version number (see Note①), execute the display version command in any view.

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.

Table 1 Version history

Version number	Last version	Branch version	Release date	Release type	Remarks
R8615P05	R8615P03	B70D064SP	2026-05-31	Release version	None
R8615P03	R8336P11	B70D064SP	2026-03-31	Release version	None
R8336P11	R8336P09	B70D064SP	2026-01-30	Release version	None
R8336P09	R8336P06	B70D064SP	2025-11-30	Release version	None
R8336P06	R8336P05	B70D064SP	2025-07-27	Release version	None
R8336P05	R8307P60	B70D064SP	2025-06-30	Release version	None
R8307P60	R8307P57	B70D064SP	2024-12-27	Release version	None
R8307P57	R8307P55	B70D064SP	2024-10-25	Release version	None
R8307P55	R8307P53	B70D064SP	2024-07-29	Release version	None
R8307P53	R8307P10	B70D064SP	2024-06-26	Release version	None
R8307P10	R8307P09	B70D064SP	2024-02-06	Release version	None
R8307P09	R8307P08	B70D064SP	2023-12-28	Release version	None
R8307P08	R8307P06	B70D064SP	2023-12-08	Release version	None
R8307P06	R8108P26	B70D064SP	2023-10-18	Release version	None
R8108P26	R8108P25	B70D064SP	2023-09-30	Release version	None
R8108P25	R8108P22	B70D064SP	2023-06-30	Release version	None
R8108P22	R6010P08	B70D064SP	2023-04-27	Release version	None
R6010P08	R6010P04	B70D064SP	2023-02-24	Release version	None
R6010P04	First release	B70D064SP	2022-11-07	Release version	None

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
Product family	S5590-48T4XC-EI S5590-28T8XC-EI S5590-28S8XC-EI S5590-48S4XC-EI S5590-28P8XC-EI S5590-48P6XC-EI S5590-24X4YC-EI S5590-48UM4YC-EI S5590-48TS4X2QC-EI S5590-24UXM4YC-EI S5590-48UXM4YC-EI S5590-48UN4Y2CC-EI S5590-32UN4X4Y2CC-EI
Memory	2G
Flash	4G
Boot ROM version	Version 103 or higher (Note: Execute the display version command in any view to view the version information. Please see Note②)
Host software	S5590EI-CMW710-R8615P05.ipe (See the MD5 file.)
iMC version	iMC BIMS 7.3(E0506H01) iMC EAD7.3(E0611P10) iMC EIA 7.3(E0611P13) iMC NTA 7.3(E0707L06) iMC PLAT 7.3(E0705P12) iMC QoSM 7.3(E0505P01) iMC SHM 7.3(E0707L06) iNode PC 7.3(E0585)
WLAN feature image version	S5590EI-CMW710-UWW-R5466P02.bin Compatible Aps reference to H3C UWW-CMW710-R5466P02 Release Notes.
Remark	None

Sample: To display the host software and Boot ROM version of the S5590-EI, perform the following:

<H3C> display version

H3C Comware Software, Version 7.1.070, Release 8108P26 ------- Note①

H3C S5590-48P6XC-EI uptime is 0 weeks, 0 days, 0 hours, 4 minutes

Last reboot reason : Code reboot

Boot image: flash:/s5590ei-cmw710-boot-r8108p26.bin

Boot image version: 7.1.070, Release 8108P26

Compiled Jul 04 2022 11:00:00

System image: flash:/s5590ei-cmw710-system-r8108p26.bin

System image version: 7.1.070, Release 8108P26

Compiled Jul 04 2022 11:00:00

Feature image(s) list:

flash:/s5590ei-cmw710-freeradius-r8108p26.bin, version: 7.1.070, Release 8108P26

Compiled Jul 04 2022 11:00:00

Slot 1:

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

BOARD TYPE: S5590-48P6XC-EI

DRAM: 2048M bytes

FLASH: 3735M bytes

PCB Version: VER.A

Bootrom Version: 103 ------ -Note②

CPLD 1 Version: 001

Power CPLD Version: None

Release Version: S5590EI-8108P26

Patch Version: None

Reboot Cause: WatchDogReboot

[SubSlot 0] 48GE+PoE+6SFP Plus

[SubSlot 1] 8*SFP28

ISSU upgrade type matrix

ISSU provides compatible upgrade and incompatible upgrade, depending on the compatibility between software versions. 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 was performed.

For more information about ISSU, see the fundamentals configuration guide for the device.

Table 3 ISSU version compatibility matrix

Current version	History version	Compatibility
S5590EI-CMW710-R8615P05	S5590EI-CMW710- R8615P03	Incompatibility

Upgrade advice

As a best practice, upgrade to this version as long as possible.

Upgrade restrictions and guidelines

Before performing a software upgrade, it is important to refer to the Software Feature Changes document for any feature changes in the new version. Also check the most recent version of the related documents (see "Related documentation") available on the H3C website for more information about feature configuration and commands.

If you upgrade the S5590-24UXM4YC-EI switch from R8307P60 or an earlier version to this version, to ensure that the PoE function on ports 17 to 24 can operate correctly, power cycle the switch to upgrade its version.

Hardware feature updates

R8615P05

S5590-48UN4Y2CC-EI/S5590-32UN4X4Y2CC-EI execute the command port-speed-mode mode 0 in the device system view to switchover to mode 0. In this state, the port configuration is 25G*4+100G, and the 100G port supports splitting.

R8615P03

None

R8336P11

New deliverable and product codes are as follows:

Model	PID
S5590-48UN4Y2CC-EI	LS-5590-48UN4Y2CC-EI-G1
S5590-32UN4X4Y2CC-EI	LS-5590-32UN4X4Y2CC-EI-G1

R8336P09~R6010P08

None

R6010P04

First release.

Software feature and command updates

For more information about the software feature and command update history, see H3C S5590EI-CMW710-R8615P05 Release Notes (Software Feature Changes) and H3C WLAN Feature Package-CMW710-R5466P02 Release Notes (Software Feature Changes).

MIB updates

Table 4 MIB updates

Item	MIB file	Module	Description
S5590EI-CMW710-R8615P05~S5590EI-CMW710-R6010P08
New	None	None	None
Modified	None	None
S5590EI-CMW710-R6010P04
New	First release	First release	First release
Modified	First release	First release	First release

Operation changes

Operation changes in R8615P05

The HTTPS self-signed certificate algorithm has been changed from SHA1 to SHA256.

Operation changes in R8615P03

Add a record in maintenance information: Abnormal scheduling of processes when VRRP stateful switchover causes flapping.

The device supports configuring the truncation length of mirrored packets, with a configurable range of 64 to 256.

Add alarm functionality for the PTP module.

Operation changes in R8336P11

The force power and detection mode commands are no longer mutually exclusive. You can execute the force power command even if the detection mode command has been executed.

Support the IP packet isolation function between management port and service interface.

Operation changes in R8336P09~R8336P06

None

Operation changes in R8336P05

Output interface information in FIB entries is replaced by VPN name information for cross-VPN routes.

Operation changes in R8307P57~R8307P08

None

Operation changes in R8307P06

Changes to the classification and rate limit for IPv6 NTP multicast packets when they are sent to the NTP module:

· Before modification: When IPv6 NTP multicast protocol packets are sent to the NTP module, they are classified as local-link protocol packets and sent with a rate limit of 600 packets per second (pps).

· After modification: When IPv6 NTP multicast protocol packets are sent to the NTP module, they are was classified as ACL packets because of Reason(349)(ID:349) and sent with a rate limit of 100 pps.

The value range for the interval of sending 1588v2 PTP announce messages changes from 20 to 24 to 2-4 to 26, in seconds. The value range for the interval of sending 1588v2 PTP sync messages changes from 2-1 to 21 to 2-4 to 26, in seconds.

Operation changes in R8108P26

Added support for deleting the default OUI addresses of voice VLAN

Operation changes in R8108P25~R6010P08

None

Operation changes in R6010P04

First release.

Restrictions and cautions

When you use this version of software, make sure you fully understand the restrictions and cautions described in this section.

Restrictions

Hardware

Port Usage Restrictions

Device Name	Port Type	Port Number	Port Supported Speeds	Restrictions
S5590-48UM4YC-EI	25G	49 50 51 52	25G/10G/1G	Can only operate at one speed simultaneously, existing port group prompt.
S5590-48NS6X-EI	10G	49 50 51	10G/2.5G/1G	Can only operate at one speed simultaneously, existing port group prompt.
S5590-48NS6X-EI	10G	52 53 54	10G/2.5G/1G	Can only operate at one speed simultaneously, existing port group prompt.
S55590-8N24NS6X-EI	2.5G Optical	9-12	2.5G	Can only operate at one speed simultaneously, existing port group prompt.
	2.5G Optical	13 14	2.5G	Can only operate at one speed simultaneously, existing port group prompt.
	10G	33-38	10G/2.5G/1G	Can only operate at one speed simultaneously, existing port group prompt.
	2.5G	25 26 27 28	2.5G 1G	Can only operate at one speed simultaneously, existing port group Unable to operate at 100M
	2.5G	29 30 31 32	2.5G 1G	Can only operate at one speed simultaneously, existing port group prompt. Unable to operate at 100M
S5590-16UN16UM4YC-EI	10G	17-32	10G/2.5G/1G	Every 4 ports can operate at up to 2 different speeds simultaneously. Every 8 ports can operate at up to 3 different speeds simultaneously.
S5590-16UN16UM4YC-EI	25G	33 34 35 36	25G/10G 1G	Can only operate at one speed simultaneously, existing port group prompt.
S5590-32UN16UM4YC-EI	10G	33-48	10G/2.5G/1G	Every 4 ports can operate at up to 2 different speeds simultaneously. Every 8 ports can operate at up to 3 different speeds simultaneously.
S5590-32UN16UM4YC-EI	25G	49 50 51 52	25G/10G 1G	Can only operate at one speed simultaneously, existing port group prompt.
S5590-48UN4Y2CC-EI	25G	49 50 51 52	25G/10G 1G	Can only operate at one speed simultaneously, existing port group prompt.
S5590-48UN4Y2CC-EI		card port		8-port daughtercard Up to 2 different rates can operate simultaneously per 4 ports. Up to 3 different rates can operate simultaneously per 8 ports. 4/2-port daughtercard All ports can operate at up to 2 different rates simultaneously.
S5590-32UN4X4Y2CC-EI	25G	37 38 39 40	25G/10G 1G	Can only operate at one speed simultaneously, existing port group prompt.
	10G	33 34 35 36	10G/2.5G/1G	At most, every 4 ports can operate simultaneously at 2 different speeds. At most, they can operate simultaneously at 3 different speeds.
		card port

Software

The device performs Layer 2 transparent transmission and directly connects to the DHCP server and DHCP client. DHCP configuration should be removed.

Starting from this version, the default HTTPS self-signed certificate algorithm has been changed from SHA1 to SHA256. If HTTPS is already enabled, please delete the existing self-signed certificate and re-enable the service for it to take effect.

QoS control-plane logging protocol ttl-expires reports ttl-expires for both IPv4 and IPv6 packets with a TTL of 1, and cannot separately count IPv4 and IPv6.

Network

None

Cautions

Hardware

None

Software

The MAC addresses in incoming untagged packets are learned in both the VLAN and the VXLAN after you configure a mapping between the outer VLAN ID of the AC and the PVID and then modify the PVID.

Network

Compatible Aps reference to H3C UWW-CMW710-R5466P02 Release Notes.

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 more information about the license-based features and licenses available for them, see H3C Switches License Matrixes.

Registering and installing licenses

To register and transfer licenses, access H3C license services at http://www.h3c.com/en/License.

For information about registering licenses, installing activation files, and transferring licenses, see H3C Switches and Routers Licensing Guide.

Some switches support the license for the unified wired and wireless access controller feature. You can purchase licenses to add the number of APs to be managed. For more information, see H3C Comware 7 or 9 Wireless Products Licensing Guide.

Open problems and workarounds

202605261484

· Symptom: MDI mode switchover fails.

· Condition:

¡ Simultaneously configure Layer 3 port mode switchover and MDI mode switchover on the web page;

¡ Configure MDI mode switchover after setting the port as a routing interface on the web page.

· Workaround: Do not perform MDI mode switchover after configuring Layer 3 port mode switchover on the web page.

202510290420

· Symptom: ACL residue may occur after a member port exits an aggregate interface.

· Condition: Configure authentication and authorization URLs on the device's aggregate interface, exceed the specifications for the number of online users, and have users exit the member port from the aggregate interface.

· Workaround: Do not exceed the specifications for the number of online users, and avoid exiting the member port from the aggregate interface during the user login process.

202604221490

· Symptom: During PTP stress testing, serial port logs show announce packet timeout and loss, as well as device roles switching back and forth between slave and master (slave → master → slave).

· Condition: The device is configured with the ST2059 protocol and undergoes prolonged stress testing.

· Workaround:

¡ If continuing to use the ST2059-2 protocol, configure `ptp announce-timeout 10` on the slave side (indicating that timeout and packet loss are determined only after 10 consecutive packet cycles without receiving Announce), and configure `ptp announce-interval 0` on the master side (sending Announce packets once per second);

¡ Switchover to the IEEE 1588v2 protocol.

202604200090

· Symptom: Port flapping occurs on the device.

· Condition: The port is configured with a 1000ms link-delay, and the tester sends jitter at 50ms intervals.

· Workaround: Extend the link-delay configuration from 1000ms to2000ms; the test will pass.

202605280693

· Symptom: During device disconnection and reconnection, configuring an audit for the static route table generates core files related to xmlcfgd.

· Condition: When the controller connects, the hello capability set includes the xml2cli function and Symptoms entries such as static routes.

· Workaround: When the controller connects, do not include the xml2cli capability set in the hello message.

List of resolved problems

Resolved problems in R8615P05

202604270523

· Symptom: After device restart, split ports are up, but port indicators do not light up.

· Condition: Device port mode is 25G*4+100G, split 100G port connects to other 25G ports, restart device.

202605150686

· Symptom: After inserting IMC card into device, front panel 25G ports go down.

· Condition: Front panel 25G ports are normally up, insert IMC daughtercard.

202604200024

· Symptom: After inserting subcard into device, indicator for fixed port 53 on front plate goes out, but port is up.

· Condition: Insert subcard into device.

202604171048

· Symptom: PoE mode indicator should light on COMBO copper port, but COMBO optical port indicator remains lit instead.

· Condition: COMBO optical port is normally up, COMBO copper port connects to PD. Press mode key to switch to PoE mode.

202604151061

· Symptom: When logging into web page and configuring new VLAN, switch slot and port are not displayed.

· Condition: Log into web page, configure new VLAN.

202604090225

· Symptom: After inserting OAP card into device, parameters under SERDES 0 change to 0.

· Condition: Insert OAP card into device.

202604231785

· Symptom: During device startup, message "cpld read write failed p1=0x55 p2=0xFF" is printed.

· Condition: Device starts up, executes CPLD self-test.

202605060401

· Symptom: status field error, displays interface up/down state information instead of whether sFlow is effective on that interface.

· Condition: Obtain SFLOW/sFlowFlowSampler entry information via Netconf.

202604071463

· Symptom: When deploying PBR, prompt indicates insufficient ACL resources.

· Condition:

¡ Deploy PBR on route summarization interface, apply statistics in PBR node;

¡ Apply PBR on route summarization interface, and TM board without member ports of this bundle exists;

¡ When count resource usage exceeds 256, apply PBR under VLAN interface.

202605120657

· Symptom: Querying diagnostic information for third-party 100G ZR4 optical transceiver module prompts unsupported; after installing license, query still prompts unsupported.

· Condition: Query diagnostic information for third-party 100G ZR4 optical transceiver module.

202604230776

· Symptom: Device 25G optical port with 1G copper module inserted does not come up when connecting.

· Condition: Device 25G optical port with 1G copper module inserted connects.

202604212218

· Symptom: Due to TX FAULT detection, device port frequently goes Up/Down, causing large number of port state logs and TX Fault alarm flooding.

· Condition: Device port establishes link connection after inserting Junheng 25G module, and TX FAULT occurs due to module defect.

202605121465

· Symptom: DNS process memory leak.

· Condition: Device enables transparent proxy, client continuously sends identical packets.

202604091106

· Symptom: Device prints PKT2CPU/4/PKT2CPU_FAILED: -Interface=M-GigabitEthernet0/0/0-ProtocolType=21 log at millisecond level, affecting operations.

· Condition: Enable ISIS protocol on device management port.

202603270017

· Symptom: undo tcp timestamps enable configuration is lost.

· Condition: Device configuration undo tcp timestamps enable is lost, save configuration and restart.

202603270224

· Symptom: Device serial port prints 'can't remove /share/python.lock' message.

· Condition: Device starts up and runs normally.

202605060399

· Symptom: The following configurations in the device cannot be deleted using the ‘undo rtm cli-policy’ command:

¡ ‘rtm cli-policy isolate-ecore’`

¡ ‘event cli async skip mode execute pattern isolate-ecore’.

· Condition: The policy name configured by the user is the same as the CLI matching rule, and the rule set by the user is 'skip'.

202605060398

· Symptom: Processes under the user context are occasionally killed incorrectly.

· Condition: All logged-in users have exited.

202604120001

· Symptom: For info-center loghost + TCP + TLS service, TCP TLS establishment fails.

· Condition: For info-center loghost + TCP + TLS service, when network latency is high.

202604221780

· Symptom: The device reboots unexpectedly.

· Condition: When the device is powered by both power supplies simultaneously, the power cord of power supply 1 is unplugged.

202604130185

· Symptom: There is a probability that the Router-MAC address of the MAC/IP route is not refreshed, causing packet transmission failure.

· Condition: In an M-LAG EVPN networking environment, after deleting the evpn global-mac configuration.

202603170913

· Symptom: An M-LAG interface on Device A flaps once.

· Condition: This symptom might occur when Device A is already up and the M-LAG interface is Up, and Device B starts up and brings up the Peer-link to establish M-LAG.

202602110698

· Symptom: During BGP route iterative update, iterative information update fails, causing BGP routes not to be optimally activated.

· Condition: This symptom might occur in a BGP route iteration scenario where multiple iterative changes occur within a short period.

202604130139

· Symptom: The local interface fails to come up after the peer interface frequently changes its speed..

· Condition: This symptom might occur if the peer frequently changes its speed and the local device is any of the following: S5590-24UXM4YC-EI/S5590-48UXM4YC-EI/S5590-24UXM4YC-EI/S5590-48UXM4YC-EI/S5590-24UXMC-EI/S5590-32UN16UM4YC-EI/S5590-16UN16UM4YC-EI/S55590-8N24NS6X-EI/S5590-48NS6X-EI/S5590-48UM4YC-EI

202604131263

· Symptom: High processor usage by PoE-related tasks after device startup.

· Condition: Normal startup of PoE-capable device models.

202601050466

· Symptom: In an M-LAG network, when an M-LAG extra VLAN is configured and allowed, but no M-LAG interface is configured, traffic may fail to pass through with a certain probability.

· Condition: This symptom might occur in an M-LAG network where an M-LAG extra VLAN is configured and allowed, but no M-LAG interface is configured.

Resolved problems in R8615P03

202601140648

· Symptom: The configuration fails to be delivered, and the returned message is "The system does not support this operation."

· Condition: This symptom might occur when the controller delivers the dot1x authentication configuration for an interface.

202602060768

· Symptom: Frequently delivering different port ifmonitor packet-drop enable commands results in the generation of a large number of PORT ACLs.

· Condition: This symptom might occur when different port ifmonitor packet-drop enable commands are frequently delivered.

202601190443

· Symptom: After configuring VLAN-related settings on a device that already has VLAN-MAPPING N:1 configured, the VLAN-MAPPING N:1 function becomes unavailable.

· Condition: This symptom might occur when VLAN-related configuration is performed on a device that already has VLAN-MAPPING N:1 configured.

202602050887

· Symptom: When the rate of a routed interface is 2.5Gbps and its status is UP, executing the display interface command does not show the rate information.

· Condition: This symptom might occur when the routed interface rate is 2.5Gbps and the display interface command is executed.

202603100003

· Symptom: The port status shows as normal, but traffic cannot pass through.

· Condition: This symptom might occur when a 25GE port is connected via a 10G optical transceiver module with link-delay down configured, and the optical transceiver module is unplugged and re-plugged.

202601071964

· Symptom: A terminal that has already been authenticated and is online on one aggregate interface of a device cannot complete authentication and come online on another aggregate interface of the same device before going offline.

· Condition: This symptom might occur when both aggregate interfaces on the device have MAC authentication or 802.1X authentication enabled. When a terminal has already completed authentication and is online on one aggregate interface, it requests authentication to come online on another aggregate interface before going offline.

202603100660

· Symptom: User configuration error: The default ACL 3001 for BYOD authorization was used. Modifying the content of ACL 3001 and delivering it for use by the packet-filter function resulted in deny rules being applied to BYOD authorization, matching packets from other ports and causing packet loss.

· Condition: This symptom might occur when:

¡ BYOD authorization is triggered.

¡ Other functions use and modify ACL 3001.

202601140080

· Symptom: When PBR delivers the service chain function, it triggers repeated next-hop refreshes, causing PBR rules to be repeatedly added and deleted. Simultaneously, the ACL rules matched by PBR repeatedly become empty, resulting in residual ARP/ND entries.

· Condition: This symptom might occur when:

¡ PBR is configured with the service chain function.

¡ The next hop configured in PBR is repeatedly refreshed.

¡ The ACL rules matched by PBR are repeatedly refreshed.

202601190720

· Symptom: The device dial test does not support Layer 3 aggregate subinterfaces, causing packet transmission from such subinterfaces to fail.

· Condition: This symptom might occur when the device performs a dial test to send packets, and the source port of the packet is a Layer 3 aggregate subinterface.

202603041519

· Symptom: In BGP, when RTs from different VPNs are imported into routes, and the source VPN first generates an aggregate route and then imports a static route, the route is deleted from the IP routing table of the destination VPN.

· Condition: This symptom might occur when a route imported by BGP from another protocol and an aggregate route configured in BGP have the same prefix and mask, and both types of routes are imported into another private network or public network, and the preference order of these two types of routes is swapped.

202602040052

· Symptom: The device prints an address conflict message.

· Condition: This symptom might occur when establishing MAD BFD through a Layer 3 aggregate interface, and auxiliary equipment pings the IP address of the standby chassis under the MAD BFD.

202602091065

· Symptom: The device prompts "no such object".

· Condition: This symptom might occur when using SNMP v2c to retrieve device node information for hh3cARPEntryCount / hh3cNDEntryCount / hh3cARPEntryOpenFlowCount.

202602261020

· Symptom: Node information cannot be read.

· Condition: This symptom might occur when reading entity voltage node information, such as InBrdcastPktSpeed, OutBrdcastPktSpeed, InMulticastPktSpeed.

202601131638

· Symptom: After a reboot, some ports may probabilistically fail to have PFC watermarks delivered.

· Condition: This symptom might occur when starting with a subcard, configuring pfc no-drop on all ports, and then rebooting with a binary file.

202601150954

· Symptom: m-lag-B cannot ping an IPv6 standalone device; reachability is restored after configuring an empty M-LAG interface.

· Condition: This symptom might occur in an Underlay M-LAG (non-VLAN active-active) standalone IPv6 scenario where the device has no M-LAG aggregate interface; both ends are configured with extra-vlan to allow the VLAN, and the standalone device is connected to the m-lag-A side.

202602110602

· Symptom: The device has a probabilistic memory leak, triggering a memory alarm.

· Condition: This symptom might occur when a client sends a DHCPv6 Renew message with the length field value of Option 2 set to 0.

202601221250

· Symptom: After removing the card in slot2, all ports on the card in slot1 go LINK DOWN.

· Condition: This symptom might occur when the card in slot2 is removed.

202601151017

· Symptom: The device's outbound ACL cannot match Layer 3 forwarded packets.

· Condition: This symptom might occur when the device receives a Layer 3 unicast packet.

202602041717

· Symptom: The system prompts that the SSL policy does not exist.

· Condition: This symptom might occur when BGP is bound to an existing SSL policy.

202602111552

· Symptom: The device triggers a memory alarm.

· Condition: This symptom might occur when the SSH or Telnet window is closed during a configuration save operation with large-scale configurations being executed.

202602040905

· Symptom: Ports disappear from the query results of display interface brief.

· Condition: This symptom might occur after the device executes the port-speed-mode mode 1 command to switch the port mode to 400G, then issues the using hundredgige command for a specific 400GE port, and executes display interface brief to query interface information.

202603041567

· Symptom: The Keepalive link becomes unilaterally Down or Up.

· Condition: This symptom might occur in an IRF environment where primary/backup Keepalive is configured. After binding the backup Keepalive to a non-existent VPN, setting the primary Keepalive link to Down triggers this.

202602040358

· Symptom: During tunnel encapsulation, if the MTU value of a packet exceeds the MTU configured on the tunnel interface, the MTU check fails and the packet is discarded.

· Condition: This symptom might occur in a tunnel scenario where the MTU value of inbound traffic is higher than the MTU configured on the tunnel interface.

202602110253

· Symptom: The device cannot be logged into via serial port or Telnet.

· Condition: This symptom might occur in an IRF network when the device performs a configuration rollback.

202602111435

· Symptom: The STP alternate port experiences periodic flapping.

· Condition: This symptom might occur in an M-LAG environment where two single-sided aggregate interfaces have the same interface index value.

202602110434

· Symptom: All MAC addresses are cleared.

· Condition: This symptom might occur when the reset mac-authentication xxx command is executed while the MAC address is all zeros.

202502241223

· Symptom: PoE function does not take effect.

· Condition: This symptom might occur when PoE is enabled on ports 17 to 24 of the S5590-24UXM4YC-EI.

202303161543

· Symptom: When two devices are directly connected, the IPv6 packet loss rate is close to 100%.

· Condition: This symptom might occur when the device has a large number of unknown multicast packets, causing abnormal loss of ICMPv6 packets.

202603030235

· Symptom: Traffic is abnormal.

· Condition: This symptom might occur after deleting an AC in the commit view and then executing commit to make the configuration take effect.

202512300805

· Symptom: The configuration of the device's aggregate interface is delivered slowly.

· Condition: This symptom might occur when configuring a large-scale aggregate group in for-pos mode and adding 2 aggregate member ports to the group.

202602060309

· Symptom: Traffic is abnormal.

· Condition: This symptom might occur after deleting an AC in the commit view and then executing commit to make the configuration take effect.

202603030288

· Symptom: BGP peer is disrupted.

· Condition: This symptom might occur when an intra-chassis or inter-chassis (under IRF) active/standby switchover, or a main control board removal/restart happens on the device, and the BGP configured keepalive time is 6 seconds or less (timer keepalive 2 hold 6).

202603090067

· Symptom: In an IRF network, performing an active/standby switchover operation has a low probability of causing an overall system restart.

· Condition: This symptom might occur when performing an active/standby switchover operation in an IRF network.

202504151887

· Symptom: The device might restart abnormally.

· Condition: This symptom might occur if files are written from the USB drive to the flash.

202512151403

· Symptom: Remote MAC entries are missing when viewing MAC entries using display l2vpn mac-address.

· Condition: This symptom might occur in an EVPN network when the address-family l2vpn evpn command is repeatedly configured/removed in BGP view or the BGP process is restarted.

202601230462

· Symptom: Failed to ping the local gateway.

· Condition: This symptom might occur after you configure subnet-based VLAN.

202512151814

· Symptom: display vxlan tunnel shows some tunnels in down state, and ARP forwarding is abnormal.

· Condition: This symptom might occur in an EVPN M-LAG network where 1000 VSIs are configured, EVPN automatically creates tunnels and adds them to all VSIs, and then reset bgp operations are performed continuously.

202601161488

· Symptom: After you execute the undo shutdown command on a newly bound M-LAG interface, the output information from the display interface command shows the interface as up, but the output information from the display mlag summary command shows its state as down.

· Condition: This symptom might occur when both the peer-link interface and the Keepalive link are down, and the undo shutdown command is executed on a newly bound M-LAG interface.

202601211108

· Symptom: Frequent sending of charging update packets (without IP changes) affects performance.

· Condition: This symptom might occur when the following conditions exist:

¡ The DHCP lease time for BYOD users is set to 1 minute. At 30 seconds, lease renewal occurs, notifying IPCIM. IPCIM then notifies MAC authentication users of IP attribute changes. MAC authentication sets the notified IP and Option information into RADIUS attributes and sends them to the RADIUS server through RADIUS charging update packets.

¡ Traffic with the same IP passes through different interfaces. The ARP-learned entries are constantly modified, subsequently notifying IPCIM. IPCIM then notifies port security of the IP change event, triggering the sending of charging update packets.

202601151130

· Symptom: Memory leak in the lauthd process.

· Condition: This symptom might occur when the following conditions exist:

¡ The pwdctrl-control enable command is executed.

¡ Management users are configured, generating data such as login failure records and historical passwords.

¡ Configuration rollback is performed, and the pwdctrl-control switch and related user configurations remain unchanged before and after the rollback.

202512290453

· Symptom: When applying policy-based routing (PBR) on routing interfaces and VSI interfaces, the policy on the first configured interface takes precedence.

· Condition: This symptom might occur when PBR is configured on both routing interfaces and VSI interfaces, and the configuration order differs.

202601100001

· Symptom: Occasional instances of sending 9 Sync packets per second are observed in actual tests.

· Condition: This symptom might occur when the PTP protocol adopts the ST2059-2 standard, with the default configuration set to send 8 Sync packets per second.

202512092331

· Symptom: Randomly causes the other three ports on the card to go DOWN and then UP.

· Condition: Insert the daughtercard LSWM2ZSP4P, then insert or remove a module from any port on the card.

202512310529

· Symptom: After you enable the global unauthorized router detection function, member interfaces of an aggregation group report anomalies. The dis uad detection-results command shows aggregation member ports.

· Condition: This symptom might occur if the uad enable unauthorized-router command is executed.

202505260367

· Symptom: The Telnet process remains.

· Condition: This symptom occurs if you execute configuration synchronization in an M-LAG network.

Resolved problems in R8336P11

202512092331

· Symptom: Randomly causes the other three ports on the card to go DOWN and then UP.

· Condition: Insert the daughtercard LSWM2ZSP4P, then insert or remove a module from any port on the card.

202510090911

· Symptom: The first 2.5G copper interface of the device has a low probability of failing to come UP during connection.

· Condition: On the local device's first 2.5G copper interface, both the speed 100 and duplex full (or duplex half) commands are configured simultaneously, and the peer device also has the same speed and duplex mode forcibly configured.

202511281463

· Symptom: The device sends a DNS packet to the source port as well.

· Condition: This symptom might occur when DNS fast reply is enabled and the device receives a Layer 2 pass-through DNS packet that cannot match any DNS entry.

202512151331

· Symptom: Negotiation failure occurs with a certain probability.

· Condition: This symptom might occur when both ends initiate IKEv2 negotiation simultaneously and the inside-vrf command is configured.

202601150628

· Symptom: The configured session timeout does not take effect after entering the tclsh view from the Telnet window.

· Condition: This symptom might occur when switching the Telnet session to the tclsh view.

202512022118

· Symptom: When performing a get operation through Netconf/YANG, information from other ordinary sensor groups cannot be retrieved.

· Condition: This symptom might occur when gNMI sensor groups are configured on the device.

202512022110

· Symptom: Legitimate traffic is incorrectly denied.

· Condition: This symptom might occur when a global packet filter deny ip time-range rule is applied, and the time-range referenced by the ACL is changed from active to inactive, leading to incorrect denial.

202512310651

· Symptom: Regardless of whether the port down reason is loopback, an alarm clear trap (hh3cLpbkdtTrapActionDownClear) is reported after the port recovers to Up.

· Condition: This symptom might occur when the port state changes from Down to Up on a port supporting LPDT functionality.

202511261603

· Symptom: The peer-link interface negotiation results are inconsistent between the two M-LAG devices.

· Condition: This symptom might occur in an M-LAG network when the jumboframe enable command is issued on the peer-link interfaces in a specific sequence.

202512050863

· Symptom: Fan speed fluctuates with sudden increases or decreases.

· Condition: This symptom might occur when PoE devices are running versions R8336P09 or R8336P10 and start normally.

202512250057

· Symptom: After canceling the congestion contribution flow visualization configuration on a specific port, the function does not take effect on other ports.

· Condition: This symptom might occur when congestion contribution flow visualization is configured on multiple ports and then canceled on one of them.

202512080575

· Symptom: After you execute the reset arp command, the interface cannot learn ARP, causing the service side to fail to ping the gateway.

· Condition: This symptom might occur when a static route and the arp anti-attack entry-fixing all enable command are configured on a device interface. After clearing the ARP entries of that interface through the reset arp command, ARP learning fails even though the static route is reachable.

202512151349

· Symptom: Adding Rule-type ND entries fails after configuring the lldp management-address nd-learning command.

· Condition: This symptom might occur when the number of IPv6 dynamic neighbor entries on a Layer 3 physical interface reaches the configured maximum allowed limit, and the lldp management-address nd-learning command is configured to trigger learning of new Rule-type ND entries.

202512090709

· Symptom: The same MAC address triggers intrusion detection.

· Condition: This symptom might occur when security MAC and intrusion detection are configured under an interface, and only one security MAC is allowed to go online. The device receives two types of packets from the same MAC address: one with an IP address and one without.

202601150638

· Symptom: The device generates a core file during configuration rollback and stress testing operations when static routes with BFD parameters are configured.

· Condition: This symptom might occur when two devices are configured with static routes and BFD parameters. Both devices simultaneously perform addition, deletion, or rollback of static route configurations, along with simultaneous port insertion and removal operations.

202512022109

· Symptom: User login fails, and a configuration inconsistency prompt appears even though the configurations on both M-LAG ends are consistent.

· Condition: This symptom might occur in an M-LAG network when a port security template is bound to an interface that already has MAC address authentication and 802.1x authentication configurations.

202512151297

· Symptom: After users in the escape domain come online, ead-success packets are not sent as configured.

· Condition: This symptom might occur when the dot1x eap-success post-authorization command is configured and users in the escape domain come online.

202601161488

· Condition: This symptom might occur when both the peer-link interface and the Keepalive link are down, and the undo shutdown command is executed on a newly bound M-LAG interface.

202512022116

· Symptom: After downloading files through FTP/SFTP/TFTP as a client, the device does not actively release cache resources.

· Condition: This symptom might occur when the device performs file download operations as a client through FTP/SFTP/TFTP.

202601150644

· Symptom: After an SSH user login fails, the corresponding SSH login exception record is not displayed in display ssh exception-record.

· Condition: This symptom might occur when the following conditions exist:

¡ Only a single stack (either IPv4 or IPv6) has stelnet/SFTP/SCP services enabled.

¡ Users initiate stelnet/SFTP/SCP login through the other protocol stack which is not enabled.

202512180641

· Symptom: Device CPU usage increases after bulk delivery of large-scale ACLs.

· Condition: This symptom might occur during large-scale ACL bulk delivery operations.

202512250941

· Symptom: Interface congestion occurs, leading to packet loss.

· Condition: This symptom might occur when burst traffic exceeds the CBS (Committed Burst Size) configured for interface rate limiting.

202512151325

· Symptom: The parameters of the isis link-delay command do not support out-of-order configuration.

· Condition: This symptom might occur when configuring the isis link-delay command.

202601151130

· Symptom: Memory leak in the lauthd process.

· Condition: This symptom might occur when the following conditions exist:

¡ The pwdctrl-control enable command is executed.

¡ Management users are configured, generating data such as login failure records and historical passwords.

¡ Configuration rollback is performed, and the pwdctrl-control switch and related user configurations remain unchanged before and after the rollback.

202601150619

· Symptom: In an EVPN M-LAG network with MAC regeneration, accessing a null pointer when the local DL MAC is empty, resulting in a core file from bgpvc.

· Condition: This symptom might occur in an EVPN M-LAG network with MAC regeneration.

202601051580

· Symptom: The timestamp of l2vpn record cannot be refreshed.

· Condition: This symptom might occur during normal device operation.

202512102183

· Symptom: When the device has the ip unreachables enable command configured and receives a default route advertised from a remote VPN, and the remote subsequently withdraws that route, residual default routes remain on the local end. After executing undo ip unreachables enable to disable sending ICMP destination unreachable messages, unreachable traffic is still forwarded.

· Condition: This symptom might occur when the ip unreachables enable command is configured, the device receives a default route advertised from a remote VPN, and the remote then withdraws that default route.

202511110501

· Symptom: After enabling the uRPF function that allows source address lookup in the forwarding table to match default route entries, traffic is abnormally allowed even if no default route entry exists on the device.

· Condition: This symptom might occur when the ip unreachables enable or ipv6 unreachables enable command is configured on the device.

202512022124

· Symptom: MPLS BFD session cannot come up.

· Condition: This symptom might occur when the session source address for MPLS BFD is configured as x.x.x.127.

202512151814

· Symptom: display vxlan tunnel shows some tunnels in down state, and ARP forwarding is abnormal.

202512022114

· Symptom: After configuration startup, inconsistencies occur when the local end synchronizes peer MAC additions and deletions, leading to residual MAC entries.

· Condition: This symptom might occur in an M-LAG+VRRP+Private VLAN network where private-vlan secondary is configured on the VLAN interface of an M-LAG VLAN or Extra VLAN.

202512022122

· Symptom: After an M-LAG device starts up, MAC and multi-synchronization occur when creating new Private VLANs and VLAN interfaces. Subsequent MAC address modifications still leave residual entries.

· Condition: This symptom might occur in an M-LAG network where private-vlan secondary is configured on the VLAN interface of an M-LAG VLAN or Extra VLAN.

202511071091

· Symptom: Traffic cannot be forwarded normally.

· Condition: This symptom might occur when loopback internal is configured on a 2.5G copper port.

202512151344

· Symptom: The device experiences a very low probability of hanging.

· Condition: This symptom might occur when BGP-LS and IS-IS neighbors are established between two devices, only the basic IS-IS network-entity command is configured, and then IS-IS configurations are repeatedly modified and flapped.

202512151322

· Symptom: VMware monitoring detects memory leaks in the IS-IS process.

· Condition: This symptom might occur after establishing IS-IS neighbors through tunnel interfaces and repeatedly executing reset isis commands, as well as frequently enabling/disabling router-id.

202512150352

· Symptom: After active/standby switchover, EVPN issues tunnel creation notifications, but the tunnel module considers the interface already exists and intercepts the creation message, preventing automatic tunnel creation.

· Condition: This symptom might occur during active/standby switchover on an IRF device when tunnel interfaces are created and deleted.

202601050466

· Symptom: In an M-LAG network, when an M-LAG extra VLAN is configured and allowed, but no M-LAG interface is configured, traffic may fail to pass through with a certain probability.

· Condition: This symptom might occur in an M-LAG network where an M-LAG extra VLAN is configured and allowed, but no M-LAG interface is configured.

202512050911

· Symptom: The device cannot start normally and restarts repeatedly.

· Condition: This symptom might occur during stepwise power cycling and restart of the device if temporary empty files without the .yang suffix exist in the flash:/.netconf/yang directory.

202512010481

· Symptom: The device hangs.

· Condition: This symptom might occur when configuring a non-existent OID through the rmon alarm command and then executing the display rmon alarm command.

202512290453

· Symptom: When applying policy-based routing (PBR) on routing interfaces and VSI interfaces, the policy on the first configured interface takes precedence.

· Condition: This symptom might occur when PBR is configured on both routing interfaces and VSI interfaces, and the configuration order differs.

202601091348

· Symptom: Router ID conflict logs are printed probabilistically on Leaf devices.

· Condition: This symptom might occur when the controller adds VPN, VSI virtual interfaces, VSI instances, and AC configurations on the Leaf.

202512022072

· Symptom: Broadcast traffic cannot pass through on the standby board.

· Condition: This symptom might occur when VTEP functionality is configured on an IRF device and traffic is forwarded by the standby board.

202511031396

· Symptom: The results of display l2vpn mac-address and display evpn route mac local are inconsistent.

· Condition: This symptom might occur in an EVPN VXLAN network where an IRF device acts as a Leaf, and L2VPN MAC addresses migrate between ports on the master and standby boards.

202601100001

· Symptom: Occasional instances of sending 9 Sync packets per second are observed in actual tests.

· Condition: This symptom might occur when the PTP protocol adopts the ST2059-2 standard, with the default configuration set to send 8 Sync packets per second.

202512151334

· Symptom: SFC forwarding entries are not deleted.

· Condition: This symptom might occur when the SID after endas in the end as cache list is modified to an invalid SID.

202512120663

· Symptom: Configuration delivery fails.

· Condition: This symptom might occur when delivering 802.1x related configurations.

202509231939

· Symptom: Incorrect fan speed control when 10G copper modules are inserted.

· Condition: This symptom might occur on S5590-48UXM4YC-EI/S5590-24X4YC-EI/S5590-48S4XC-HI/S5590-28S8XC-HI devices when 10G copper modules are inserted into optical ports and heated.

202511220043

· Symptom: Incorrect fan speed control.

· Condition: This symptom might occur when the device uses PID fan speed control.

202512301588

· Symptom: The first port type switch fails on a Combo port with force power configured, and the original force power configuration is lost.

· Condition: This symptom might occur on a PoE-capable device when performing a port type switch operation on a Combo port with force power configured.

202511261602

· Symptom: The number of routes activated by the RIB standby process is probabilistically inconsistent with that of the master process.

· Condition: This symptom might occur during active/standby switchover of RIB in a large-scale scenario with equivalent routes having different next hops.

202512022119

· Symptom: Version update fails.

· Condition: This symptom might occur when an IRF device uses the cloud management channel to update its version.

202512230222

· Symptom: When the gRPC server is busy or does not send response packets for a long time, continuous delivery of new probe packets causes the cache chain to accumulate continuously, leading to sustained growth in device memory.

· Condition: This symptom might occur when the gRPC server is in a busy state or does not send response packets to the client for a long time.

202512151403

· Symptom: Remote MAC entries are missing when viewing MAC entries using display l2vpn mac-address.

· Condition: This symptom might occur in an EVPN network when the address-family l2vpn evpn command is repeatedly configured/removed in BGP view or the BGP process is restarted.

202512151295

· Symptom: After configuring static Overlay MAC entries, batch deletion using the undo mac-address static vsi command fails. The previously configured static MAC entries are still displayed in display l2vpn mac-address.

· Condition: This symptom might occur after configuring static Overlay MAC entries and then using the undo mac-address static vsi command for batch deletion.

202601151213

· Symptom: After triggering the turn-off deadlock upper limit action, some PFC functions deadlock.

· Condition: This symptom might occur when the turn-off deadlock upper limit action is triggered.

202512022095

· Symptom: Core file generation due to out-of-bounds when L2VPN configures 32 equivalent cr-lsps.

· Condition: This symptom might occur when L2VPN configures 32 or more equivalent cr-lsps.

202512151354

· Symptom: COA delivery fails.

· Condition: This symptom might occur when users such as 802.1x or MAC address authentication come online, and the RADIUS server has an IPv6 address within a VPN, and COA is delivered.

202512151335

· Symptom: High CPU usage in the rtermcond process.

· Condition: This symptom might occur when the RTA server starts a listening port but cannot receive packets.

202512240968

· Symptom: STP function abnormality on aggregated member ports.

· Condition: This symptom might occur after MACsec is configured on aggregated member ports and they interconnect with devices that do not have CTC chips.

202511261628

· Symptom: M-LAG experiences dual Primary when the Keepalive link is normally UP.

· Condition: This symptom might occur in an M-LAG network when an M-LAG interface is configured as an uplink port and this configuration is deleted while the peer-link is down.

202511261626

· Symptom: Incorrect uplink port state leads to incorrect active/standby switchover mode.

· Condition: This symptom might occur on an IRF device with uplink ports configured during active/standby switchover.

202512111540

· Symptom: Slow delivery of MPLS L3VPN routes.

· Condition: This symptom might occur on an IRF device in an MPLS L3VPN network environment where the public network ISP is equivalent, and the public network link flaps repeatedly after active/standby switchover.

202512110469

· Symptom: Tunnel-encapsulated packets are discarded when detouring through the peer-link.

· Condition: This symptom might occur in an M-LAG VXLAN network where a virtual interface MAC address is configured on the tunnel public network port, and this virtual interface MAC address differs from the device's default MAC address.

202512022078

· Symptom: In an MVPN network, with the private network RP deployed on the PE on the multicast source side, if multicast traffic is first received from an interface not in the same network segment as the multicast source, and then the interface address is changed to be in the same network segment as the multicast source, multicast traffic still fails to pass.

· Condition: This symptom might occur in an MVPN network where the private network RP is on the PE on the multicast source side. Multicast traffic is first received from an interface in a different network segment than the multicast source, and then the interface address is changed to be in the same network segment.

202512310529

· Condition: This symptom might occur if the uad enable unauthorized-router command is executed.

202511191871

· Symptom: In the static aggregation BFD scenario, if the maximum or minimum number of selected member ports is configured, and some member ports are not selected due to this limit, the BFD sessions on these unselected ports will be deleted.

· Condition: This symptom might occur if static aggregation BFD is used with the maximum or minimum number of selected member ports configured.

202512022079

· Symptom: If a TC device has a board with an incorrect sysoid, the device panels for all slots of that TC device cannot be displayed on the SmartMC 1.0 Visualization > Topology page.

· Condition: This symptom might occur if a TC device has a board with an incorrect sysoid.

202512251762

· Symptom: After you log in to the device management interface through a Firefox or IE browser and access the Network > STP > Spanning Tree Instance page, the page displays no data.

· Condition: This symptom might occur when you log in to the device management interface through a Firefox or IE browser and access the Network > STP > Spanning Tree Instance page.

202601211108

· Symptom: Frequent sending of charging update packets (without IP changes) affects performance.

· Condition: This symptom might occur when the following conditions exist:

202601230462

· Symptom: Failed to ping the local gateway.

· Condition: This symptom might occur after you configure subnet-based VLAN.

202505270596

· Symptom: After you execute the info-center trace-logfile quota command, save the configuration, and reboot the device, the corresponding buildrun information is not generated in the configuration file.

· Condition: This symptom might occur after you execute the info-center trace-logfile quota command, save the configuration, and reboot the device.

202511271154

· Symptom: After a 10G multi-rate copper port negotiates its rate to 5G or 2.5G, error packets appear.

· Condition: This symptom might occur when a 10G multi-rate copper port performs multi-rate autosensing negotiation with the peer end, and the rate is negotiated to 5G or 2.5G.

· Remarks: None.

202511060639

· Symptom: Telnet IPv6 connection fails.

· Condition: This symptom might occur if you execute the telnet client source interface command.

202512010774

· Symptom: The switch reboots due to bit flips.

· Condition: This symptom might occur if the switch experiences bit flips.

· Remarks: None.

Resolved problems in R8336P09

202511171944

· Symptom: After you deploy the command of forced PoE power supply to a combo interface, the system prompts command execution failure, but the feature takes effect.

· Condition: This symptom occurs if you deploy the command of forced PoE power supply to a combo interface.

202511100501

· Symptom: The system records the number of CRC errors occurring on a port.

· Condition: This symptom might occur if the device is installed with the LSW2XMGT8P card.

202511061198

· Symptom: After a card is replaced on the host, residual old card configuration prevents the interface on the new card from achieving the maximum rate.

· Condition: This symptom might occur if you replace the LSW2MGT8P card on the host with a new card that provides a higher interface rate.

202510280147

· Symptom: A link is up only on one side of the interface.

· Condition: This symptom might occur if the device is inserted with a fiber-to-copper transceiver module.

202510310706

· Symptom: In an M-LAG environment, traffic forms a loop between peer-link member ports.

· Condition: This symptom occurs if the following conditions exist:

¡ For an IPv6 dual-active gateway (such as VLAN 6), NS packets are sent to a single-homing interface.

¡ The peer link includes at least two member ports.

¡ VLAN 6 is permitted only on the single-homing interface and peer-link interfaces, and does not contain the M-LAG interface.

¡ Another VLAN (dual-active gateway) is permitted on the M-LAG interface, and its MAC address is the same as that of VLAN 6.

202510280191

· Symptom: After you modify the leaf device configuration, the tunnels on the border device are disconnected, preventing BGP neighbor establishment.

· Condition: This symptom occurs if you add a rule to the ACL after you configure local policy-based routing when the fast forwarding table remains active.

202511060639

· Symptom: Telnet IPv6 connection fails.

· Condition: This symptom might occur if you execute the telnet client source interface command.

202511100377

· Symptom: OSPF Type 10 LSAs remains on an interface.

· Condition: This symptom might occur in the following situation:

¡ Multiple OSPF neighbors are established by using the secondary addresses of an interface.

¡ MPLS TE is enabled on the interface.

¡ The undo mpls te command is executed on the interface.

202511100376

· Symptom: The OSPF neighbor established by using the primary interface address is UP.

· Condition: This symptom might occur on an interface if you perform the following operations:

¡ Establish OSPF neighbors by using the primary and secondary addresses of an interface.

¡ Execute the ospf ttl-security hops 11 command on the interface.

¡ After all neighbors of the interface go down, remove the configuration of using secondary addresses for neighboring.

202511100374

· Symptom: OSPF runs incorrectly on an interface.

· Condition: This symptom might occur on an interface if you perform the following operations:

¡ Configure multiple secondary addresses on the interface.

¡ Execute the network command to associate the above secondary addresses to different OSPF areas.

¡ Repeatedly switch the neighboring mode between using secondary addresses for neighboring and using the specified secondary address for neighboring.

202510311128

· Symptom: A class-based accounting action in a QoS policy does not take effect.

· Condition: This symptom occurs if you configure both a class-based accounting action and an aggregate CAR action in a traffic behavior of the QoS policy.

202511100657

· Symptom: After a BGP peer is disconnected, route deletion is blocked, which result in a traffic switchover delay longer than 10 seconds.

· Condition: This symptom might occur if MPLS is not configured, and the service module where the BGP peer resides is restarted.

202510310910

· Symptom: The L2PT for LLDP feature becomes inactive on a physical interface newly added to an aggregation group.

· Condition: This symptom occurs if you enable L2PT for LLDP on both a physical interface and an aggregate interface, and then add the physical interface to the aggregate interface.

202510310897

· Symptom: In a VXLAN network with VLAN mapping configuration, the port corresponding to the deployed EVPN MAC information becomes abnormal after you restart the card that deploys EVPN MAC addresses.

· Condition: This symptom occurs if you restart the card that deploys EVPN MAC addresses in a VXLAN network with VLAN mapping configuration.

202510310858

· Symptom: An interface cannot learn MAC addresses in two-to-one VLAN mapping or zero-to-two VLAN mapping scenarios.

· Condition: This symptom occurs if you configure both many-to-one VLAN mapping and other types of VLAN mapping on the same interface.

202511030680

· Symptom: Executing interface-related commands has significant response delay.

· Condition: This symptom occurs if the following conditions are met:

¡ The device subscribes to a large amount of gRPC XPath data related to buffermonitor and ifmgr.

¡ The data collection interval is set to 1 second.

202511141384

· Symptom: The TPID values for the same VLAN are different in the inbound and outbound directions of an interface, causing communication issues with devices that use specific TPID values.

· Condition: This symptom occurs if you configure both one-to-one VLAN mapping and an outer VLAN tag value on the same interface.

202511040629

· Symptom: Some ARP packets destined for a VLAN interface cannot be sent to the CPU. When you delete the IP address of the VLAN interface, the system generates a log indicating that the IP address does not exist and has failed to be issued to the driver.

· Condition: This symptom might occur if the following conditions are met:

¡ A VLAN interface is configured with an IP address.

¡ After you execute the arp broadcast pass-through enable command on it, the hardware resources of the device is insufficient.

202510310510

· Symptom: The fans operate with the linear speed adjustment strategy rather than the expected PID control strategy.

· Condition: This symptom occurs if the device starts correctly.

Resolved problems in R8336P06

202507161583

· Symptom: An IPv6 BFD session cannot be established.

· Condition: This symptom might occur if the first BFD session to be established for a Layer 3 aggregate interface on a device is an IPv6 BFD session.

202507110803

· Symptom: The VLAN interfaces for the two device ports cannot ping each other.

· Condition: This symptom might occur if the device is enabled with MACsec.

202507222271

· Symptom: A 1G port on the device fails to come up (link inactive) if a 100M transceiver module is installed in the port.

· Condition: This symptom might occur if you insert a 100M transceiver module in a 1G port on the device (for example, 100BASE-FX).

202502081233

· Symptom: If the aggregate interface of a distributed device fast comes up, the static route takes effect with a delay of about 5 seconds.

· Condition: This symptom might occur with a certain probability when the following situations exist:

¡ The next hop output interface for the static route is an aggregate interface.

¡ The aggregate interface has member ports on a specific interface card, and ARP packets are received by the interface card.

202507110925

· Symptom: When a MAC address moves across devices, dynamic ND entries are incorrectly refreshed to a tunnel interface.

· Condition: This symptom occurs when traffic triggers ND entry learning on the remote AC side after the local AC side has already learned the ND entries in an EVPN network.

202507101628

· Symptom: In an M-LAG network, when the secondary device becomes the primary device, it sends ARP probes, causing ARP entry inconsistencies between the primary and secondary devices.

· Condition: This symptom occurs if you move ARP entries with the same IP address but different MAC addresses on an M-LAG interface in an M-LAG network.

202507070867

· Symptom: EVPN routes advertised by BGP lack L3VNI information, causing service traffic interruption.

· Condition: This symptom might occur in the following situation:

¡ BGP NSR is enabled.

¡ The L3VNI attribute is changed for routes.

¡ HA active/standby switchover is triggered.

202507251010

· Symptom: The statistics collection feature for the OFP meter flow table fails to take effect, and cannot correctly collect traffic statistics.

· Condition: This symptom occurs if the device receives traffic that matches the flow entries after the meter flow entries are deployed.

202507222411

· Symptom: The help information is inaccurate. The password length range for product customization differs from the default password length range.

· Condition: None.

202506250686

· Symptom: The type of a transceiver module is mistakenly identified as UNKNOWN.

· Condition: This symptom might occur if you repeatedly remove and install the transceiver module to the device while power cycling the device.

202503111520

· Symptom: After you log in to the SmartMC Web interface of the device and click to view the device topology, the system prompts an error.

· Condition: This symptom might occur after you log in to the SmartMC Web interface of the device and click to view the device topology.

202507180444

· Symptom: In a network where an IRF fabric has VLAN-to-VXLAN mappings configured, some cards might incorrectly broadcast learned MAC addresses.

· Condition: This symptom occurs if some member devices have no VLAN ports configured when you enable the VLAN-VXLAN mapping function on an IRF fabric.

202501162056

· Symptom: When ports are interconnected between LSWM2SP2PB and LSWM2SP4PB interface modules, these ports take about 3 minutes to come up after a device restart.

· Condition: This symptom might occur if you start up the devise after ports are interconnected between LSWM2SP2PB and LSWM2SP4PB interface modules.

202507180156

· Symptom: The device generated an M-LAG-related core file.

· Condition: This symptom occurs if you execute the display mc-configure config-check command in an M-LAG environment.

202507071100

· Symptom: The aaa device-id command does not take effect on SSH users.

· Condition: This symptom might occur after an SSH user comes online through RADIUS when aaa device-id is configured.

202506231268

· Symptom: The switch reboots when sending TCP keepalive packets.

· Condition: This symptom occurs with a low probability if the switch establishes a TCP connection and sends keepalive packets.

202504240442

· Symptom: Panel information is not displayed after the device starts up correctly.

· Condition: This symptom might occur if the S5590-24UXMC-EI starts up correctly.

Resolved problems in R8336P05

202505261660

· Symptom: When the device withdraws source routes, it does not advertise route withdrawal messages to peers. Consequently, EBGP routes fail to be deleted.

· Condition: This symptom might occur in a triangle network topology under the following conditions:

a. Device A is configured with the advertise lowest-priority on-peer-up duration command. It receives a large number of EBGP routes after BGP peer relationships are established.

b. Device A is notified to withdraw source routes when the wait timer specified by using the duration keyword expires.

202505131256

· Symptom: Although a BFD session went down, the device does not disconnect from the related peer.

· Condition: This symptom might occur under the following conditions:

a. BFD is configured for BGP, and the BFD timer is longer than 1 second.

b. BGP has a default backup route and the primary path is shut down.

202504240442

· Symptom: Panel information is not displayed after the device starts up correctly.

· Condition: This symptom might occur if the S5590-24UXMC-EI starts up correctly.

202506181307

· Symptom: Residual service slot x configuration exists under VLAN-interface 1 and cannot be manually deleted.

· Condition: This symptom might occur if you enable SmartMC outbound again under a Layer 3 interface if the feature has been enabled under the interface.

202506191657

· Symptom: Configuration backup fails.

· Condition: This symptom might occur in a SmartMC 1.0 network if you change the TC user password and then perform configuration backup.

202504290148

· Symptom: User data communication fails for a user after the user switches from one port to another.

· Condition: This symptom might occur if a user comes online from one port, and then switches to another port for reconnection without going offline from the original port.

202506181720

· Symptom: The system displays Enabling bridging on an Ethernet interface might cause packets received on that interface to be forwarded from the same interface when you execute the undo port bridge enable command.

· Condition: This symptom might occur if execute the undo port bridge enable command.

202505080213

· Symptom: The device displays error message Operation failed because the interface permits jumbo frames if you execute the undo jumboframe enable command on a breakout interface and then combine the breakout interfaces.

· Condition: This symptom might occur if you execute the undo jumboframe enable command on a breakout interface and then combine the breakout interfaces.

202506181814

· Symptom: The FEC configuration on an interface is lost if you configure the FEC feature on that interface and then change the link type for that interface.

· Condition: This symptom might occur if you configure the FEC feature on an interface and then change the link type for that interface.

202506111262

· Symptom: When port 25, port 26, port 27, and port 28 on the device go down, port 29, port 30, port 31, and port 32 also go down and come up.

· Condition: This symptom might occur if the status of ports 25 through 28 on the device changes from up to down.

202506230628

· Symptom: The device reboots unexpectedly.

· Condition: This symptom occurs if you configure gRPC sensor paths mac/underlaymacevent and mac/overlaymacevent.

202506120579

· Symptom: The device reboots unexpectedly.

· Condition: This symptom occurs if you configure gRPC sensor paths mac/underlaymacevent and mac/overlaymacevent.

202504230976

· Symptom: The port on one end is up but the port on the other end is down.

· Condition: This symptom might occur if you configure a breakout interface as a DPSH monitor port, and then repeatedly shut down and bring up the breakout interface.

202505270051

· Symptom: There are command execution failure logs in the log buffer, but the functions of the device are not affected.

· Condition: This symptom occurs if you enable gRPC and execute the display grpc command on the device.

202506110146

· Symptom: The direct routes generated by ARP are deleted.

· Condition: This symptom occurs if the following conditions are met:

a. Execute the arp route-direct advertise command.

b. ARP entries migrate from port 1 to port 2.

c. Execute the shutdown command to shut down port 1.

202506191291

· Symptom: When no PTP domain is configured, after you configure gRPC sensor path ptp/parent, the system prompts Operation failed but the PTP process still exists.

· Condition: This symptom occurs if you configure a gRPC sensor path related to ptp/parent/clock when the PTP process exists.

202506161465

· Symptom: The value for the ExtConfigBit field changes from 200 to 0.

· Condition: This symptom occurs if you execute the ip forwarding fast-move command on a VLAN interface, and then perform an active/standby MPU switchover.

202506260903

· Symptom: When you delete the PTP configuration of an interface via NETCONF on the controller, the system prompts The value is out of range for the current PTP profile.

· Condition: This symptom occurs if you deploy a remove operation on PTP configuration.

202506181162

· Symptom: The IPv6 BFD session on a Layer 2 aggregate interface is not up, and the interface does not receive BFD packets.

· Condition: This symptom occurs if you execute the link-aggregation bfd ipv6 command on a Layer 2 aggregate interface.

202506181611

· Symptom: In an EVPN M-LAG network, traffic drops persist for over 3 minutes after the headend device resets the multicast forwarding table.

· Condition: This symptom occurs if the headend device resets the multicast forwarding table in an EVPN M-LAG network.

202504031060

· Symptom: The aggregation member port information displays "Forbid jumbo frames to pass."

· Condition: This symptom occurs if you assign a port to an aggregation group and execute the display interface command to view information about the port.

202506121336

· Symptom: In a VXLAN M-LAG network, multicast traffic is abnormal.

· Condition: This symptom occurs if the VXLAN M-LAG network repeatedly flaps.

202506121422

· Symptom: Abnormal line feed occurs in the output IPv6 VRRP status information, causing critical information misalignment.

· Condition: This symptom occurs if the IPv6 link-local address configured for the device is long.

202505300620

· Symptom: No prompt message for unsupported synchronization occurs when configurations such as probe timeout are issued.

· Condition: This symptom occurs if configuration parameters, such as probe timeout, are issued in synchronization view.

202506111700

· Symptom: The BFD session state for a static aggregation group cannot come up.

· Condition: This symptom occurs if the following situations exist:

¡ A static aggregation BFD session is configured on the local end, but not on the peer end.

¡ The session is in down state, and then the BFD session establishment mode is switched from active to passive and back to active.

202506161192

· Symptom: The static aggregation BFD session state cannot come up after the BFD process restarts.

· Condition: This symptom occurs if authentication is configured for the aggregate interface on the local device, and then the BFD process is restarted after a master/subordinate switchover of the IRF fabric.

202504280468

· Symptom: In an M-LAG network, when a tracer operation is executed on the primary device, the operation is also executed on the secondary device, and you cannot abort the operation by pressing CTRL + C.

· Condition: This symptom occurs if a tracert operation is executed on the primary device in an M-LAG network.

202506241448

· Symptom: A device process gets stuck and cannot quit.

· Condition: This symptom might occur if you execute any command in public key view in sync mode.

202506060614

· Symptom: A RAS alarm that reports fans stopped occurs on the device.

· Condition: This symptom might occur if fans operate correctly after the device starts up.

202506181900

· Symptom: Some ports on the device might fail to come up.

· Condition: This symptom might occur if the device restarts after the 10G/25G ports are inserted with transceiver modules.

202506161154

· Symptom: The RAS multicast resource exhaustion alarm occurs when the device still has multicast resources available.

· Condition: This symptom might occur if a hash conflict occurs on multicast entries.

202501211252

· Symptom: Traffic loss occurs on the device.

· Condition: This symptom might occur if the 100G module on the S9820-8C-G device connects to a 40G module or cable for traffic transmission.

202501060371

· Symptom: The forwarded packet's content at bytes 5 and 6 in the UDP message was altered to 0.

· Condition: This symptom might occur if the device forwards non-initial fragments of a UDP fragmented packet.

202501210713

· Symptom: When INT is disabled, packets are identified as INT packets and their payloads are edited.

· Condition: This symptom occurs if the L4 payload header of packets is 0xccccccccdddddddd when INT is disabled.

202502071330

· Symptom: After a user goes offline, the authentication MAC remains in the VLAN.

· Condition: This symptom occurs if you bulk bring users online and reset users.

202502110909

· Symptom: If you configure the PD disconnection detection mode as AC, save the configuration, restart the device, and then execute the undo poe disconnect command, the PD disconnection detection mode is displayed as DC. However, the PD disconnection detection mode should be AC after you perform these steps.

· Condition: This symptom might occur if you configure the PD disconnection detection mode as ac, save the configuration, restart the device, and then execute the undo poe disconnect command.

202408160108

· Symptom: The configuration fails if you configure the device operate at 2.5 Gbps.

· Condition: This symptom might occur if the device is configured to operate at 2.5 Gbps.

202411080350

· Symptom: BFD session flapping might occur on the aggregate interface of a device.

· Condition: This symptom might occur if the last user logs out of the device, or the undo debugging all command is executed on the device.

202411071820

· Symptom: After the peer link of an M-LAG system flaps, the configurations of the two M-LAG member devices become inconsistent.

· Condition: This symptom occurs if the peer link of an M-LAG system flaps.

202411071179

· Symptom: The BGP process generates core files.

· Condition: This symptom occurs if the following operations are performed:

a. Enable ARP flood suppression when a VLAN is associated with a VXLAN.

b. Enable the EVPN address family after the local device obtains ARP information.

202411010642

· Symptom: Core files are generated due to memory leakage or process exceptions on the device.

· Condition: This symptom might occur if you execute the undo shutdown command to shut down interfaces in bulk during the process startup.

202411061710

· Symptom: An interface fails to forward traffic after MACsec is disabled on it.

· Condition: This symptom occurs if MACsec is disabled on an interface.

202411010645

· Symptom: A device prints a log message that "Data stays in the receive buffer for an over long time", and the device does not respond when you execute a display command.

· Condition: This symptom occurs if an M-LAG interface repeatedly flaps.

202411111600

· Symptom: The display packet-drop command cannot display packet drop statistics for a slot.

· Condition: This symptom might occur if the display packet-drop slot command is executed.

202411010644

· Symptom: The memory usage increases on the master device.

· Condition: This symptom occurs if repeated flapping occurs for a large number of VRRP groups.

202502241223

· Symptom: PoE function does not take effect.

· Condition: This symptom might occur when PoE is enabled on ports 17 to 24 of the S5590-24UXM4YC-EI.

Resolved problems in R8307P60

202410301708

· Symptom: The system generates a down alarm for an interface that is shut down in physical layer.

· Condition: This symptom might occur if the received optical power drops below the threshold after the interface is shut down.

202412261877

· Symptom: Traffic cannot be forwarded on the interfaces on a card assigned to an aggregation group.

· Condition: This symptom occurs if the following operations are performed:

a. Start the device without an expansion card.

b. Insert an expansion card.

c. Assign the interfaces on the card to an aggregation group.

202411300170

· Symptom: The device fails to start up when R8307P55 or R8307P57 is loaded.

· Condition: This symptom might occur if you load R8307P55 or R8307P57.

202411300162

· Symptom: The management interface of the device might flap.

· Condition: This symptom might occur if the device starts up with subcards.

202411250248

· Symptom: Outgoing packets dropped by a QoS policy on an interface are also counted.

· Condition: This symptom occurs if you apply a QoS policy containing a deny action to the outbound direction of an interface and enable Layer 3 packet statistics collection on the interface.

202412191959

· Symptom: A DHCP user cannot come online, because the DHCP packets transmitted through a tunnel are encapsulated with two layers of VXLAN tags.

· Condition: This symptom might occur in the following situation:

¡ An EVPN VXLAN distributed gateway and a DHCP relay agent are deployed in the network.

¡ DHCP snooping is enabled.

¡ VXLAN interfaces are used to set up the public network.

202411251614

· Symptom: The MAC address of an interface does not respond to a bridge MAC address change.

· Condition: This symptom might occur when the bridge MAC address of the device changes.

202411250405

· Symptom: ARP replies that pass through the device are not sent to the CPU and the device cannot generate ARP snooping entries.

· Condition: This symptom occurs when the following conditions are met:

¡ Configure ARP snooping in VLAN view.

¡ The device performs Layer 2 unicast forwarding on the received ARP packets.

202412230285

· Symptom: Two devices unexpectedly reboot when they form an IRF fabric.

· Condition: This symptom occurs when the following devices attempt to form an IRF fabric:

¡ S5590-48UXM4YC-EI or S5590-24UXM4YC-EI.

¡ S5590EI switch (with a different switch model) installed with a subcard incompatible with S5590-48UXM4YC-EI or S5590-24UXM4YC-EI.

202412051179

· Symptom: Before a non-direct leaf device transmits packets through a tunnel, it re-encapsulates them incorrectly.

· Condition: This symptom might occur in the following situation:

¡ An EVPN VXLAN distributed gateway acts as a DHCPv6 relay agent.

¡ DHCPv6 server replies are returned to a non-direct leaf device that acts as a DHCPv6 client.

202411282000

· Symptom: The device might reboot unexpectedly.

· Condition: This symptom occurs if you execute the vxlan local-mac report or vtep enable command in system view.

202412040722

· Symptom: Port 80 cannot be disabled.

· Condition: This symptom might occur if you change the HTTP port after enabling SmartMC and then disable SmartMC.

202411261293

· Symptom: After you restore the device to its initial state, an IPv6 static route is not cleared.

· Condition: This symptom might occur under the following conditions:

a. An IPv6 static route is created with a preference value specified.

b. Configuration rollback is performed.

202412131800

· Symptom: A broadcast storm occurs in the network.

· Condition: This symptom occurs if the reply is sent to a non-directly connected leaf node when an IPv6 client releases an address on an EVPN VXLAN network.

202412131493

· Symptom: The system prompts invalid value when you create a service loopback group through NETCONF.

· Condition: This symptom occurs if you create a service loopback group through NETCONF.

202412120860

· Symptom: OSPF flaps after the BFD authentication configuration is deleted at one end.

· Condition: This symptom occurs if you configure software BFD for OSPF and delete the BFD authentication configuration at one end.

202412140098

· Symptom: The MAC authentication offline detection feature does not take effect after the device starts up with the .cfg file.

· Condition: This symptom occurs if you enable MAC authentication offline detection on an aggregate interface and restart the device with a different software version.

202411200781

· Symptom: A subcard fails to be accessed and cannot be identified.

· Condition: This symptom might occur if a subcard is inserted to the device when the device is normal.

202412240904

· Symptom: If you add and delete IP subnet-based VLAN rules in a VLAN in certain conditions, the rules remain after a period of time.

· Condition: This symptom occurs if you issue the IP subnet-based VLAN rules after the IP subnet-based VLAN resources have been exhausted, which triggers a rollback, and the rollback is not complete.

202411191615

· Symptom: The combo interface on the device fails to come up.

· Condition: This symptom might occur if the S5590-28T8XC-EI device restarts.

202410190593

· Symptom: The device reports a management interface up event when the management interface is down and then the issue quickly recovers if subcards are present on the device and the management interface is down.

· Condition: This symptom might occur if subcards are present on the device and the management interface is down.

202412171993

· Symptom: An STP deadlock occurs.

· Condition: This symptom occurs if a comprehensive stress test is performed in an M-LAG+VXLAN network.

202412171996

· Symptom: Residual ARP entries exist in an overlay + M-LAG network.

· Condition: This symptom occurs if the following conditions exist on an overlay + M-LAG network:

¡ A device singled-homed to one M-LAG member device sends ARP packets, and a device single-homed to the other M-LAG member device sends RARP packets.

¡ During this process, the peer-link interface flaps.

202412171992

· Symptom: The L2VPN MAC address entries are also deleted.

· Condition: This symptom occurs if L2VPN MAC address entries exist in the environment, and a single-homed interface is configured as the peer-link interface and then restored to a single-homed interface.

202412171990

· Symptom: After you disable L2TP for DLDP on an interface, the protocol packets are still sent, which affects the sending of LACPDUs and thus impacts the establishment of a dynamic aggregation.

· Condition: This symptom occurs if you enable L2PT for DLDP on an interface and then disable it.

202412171991

· Symptom: The device restarts abnormally.

· Condition: This symptom might occur if the LSWM2SP8P subcard is removed and installed with the user-configured settings.

Resolved problems in R8307P57

202409191231

· Symptom: The S5590-48TS4X2QC-EI device restarts abnormally.

· Condition: This symptom might occur if the logic version is 003 for the S5590-48TS4X2QC-EI device and the optical fibers for ports 49 through 54 are removed.

202409140090

· Symptom: When you configure the jumboframe enable command at the CLI, the system displays a message indicating that the configuration is not supported, but it can be successfully configured from the Web interface.

· Condition: This symptom might occur if you configure an IRF port on the device and then try to configure the jumboframe enable command at the CLI.

202409041378

· Symptom: The device restarts.

· Condition: This symptom might occur if you repeatedly remove and install a subcard with the 10G fiber-to-copper transceiver module on the device.

202408290712

· Symptom: The ntp-service source command cannot be deleted when the configuration is rolled back.

· Condition: This symptom might occur if you roll back the configuration that contains the ntp-service source and ntp-service ipv6 source commands to a configuration file that does not contain NTP settings.

202406121933

· Symptom: OSPF packets between a secondary M-LAG member device and an external device are dropped when they pass through the primary M-LAG member device, preventing the establishment of OSPF neighbors.

· Condition: This symptom occurs if multiple OSPF neighbors are established over the peer link and ECMP routes exist for the M-LAG VLAN in an M-LAG system.

202407260606

· Symptom: Multicast packets are sent to the CPU because dummy entries are not deployed to hardware.

· Condition: This symptom occurs if IGMPv3 is configured and a Layer 3 interface not in a multicast group receives multicast packets destined for multicast address prefixed with 232.

202408221574

· Symptom: M-LAG member devices in an M-LAG system cannot ping each other.

· Condition: This symptom occurs if an M-LAG member device in an M-LAG system learns the virtual interface MAC address of the peer device.

202407310008

· Symptom: In an IPv6 M-LAG MVXLAN network, only half of the multicast traffic is forwarded.

· Condition: This symptom occurs if only one M-LAG member device exists, and you reboot the card where the peer-link interface resides.

202401100231

· Symptom: A CFGMAN_CFGCHANGED log is generated when no debugging is configured.

· Condition: This symptom occurs when an SSH user logs out from the device.

Resolved problems in R8307P55

202404030342

· Symptom: Core files are generated on the device when a PTP automation test script is running on the device.

· Condition: This symptom might occur when a PTP automation test script is running on the device.

202406191526

· Symptom: Failed to obtain data from NETCONF node /api/v1/Device/Base.

· Condition: This symptom occurs if you obtain data from node Device/Base through API or use Postman to obtain data from node Device/Base/SystemPower.

202406241465

· Symptom: VXLAN packets received on an AC interface cannot be encapsulated or forwarded with VXLAN again.

· Condition: This symptom occurs if packets have already been encapsulated by VXLAN and entered the device through an AC interface.

202405161262

· Symptom: No information is returned when the hh3cEntityExtMacAddress.1 (MacAddress) MIB node is read.

· Condition: This symptom occurs when you read the hh3cEntityExtMacAddress.1 (MacAddress) MIB node.

202407180756

· Symptom: IGMP report messages and MLD report messages are looped in the network.

· Condition: This symptom occurs if you configure IGMP snooping and MLD snooping but do not configure IGMP snooping proxy or MLD snooping proxy on two interoperating EVPN M-LAG systems.

202407160262

· Symptom: The device might reboot unexpectedly.

· Condition: This symptom occurs if you configure gRPC or other services that frequently send or receive packets on an IRF member device.

202405300639

· Symptom: After the remote device experiences flapping, BFD cannot come up normally.

· Condition: This symptom occurs if the following operations are performed:

a. Split an interface without rebooting the device.

b. Assign the breakout interfaces to a Layer 3 aggregation group.

c. Configure OSPF BFD on the aggregate interface.

202406181604

· Symptom: After the device performs a warm restart, port 1 on the device might fail to start up.

· Condition: This symptom might occur if the device performs a warm restart with a 25G transceiver module in port 1 and a 1G transceiver module in port 5.

Resolved problems in R8307P53

202403060225

· Symptom: The memory usage is high.

· Condition: This symptom might occur if the system operating mode is advance or expert and you enable MPLS.

202405171063

· Symptom: The system prompts that the command is not supported if you configure the diagnostic monitor enable slot 2 test PortMonitor command on the device and then delete this command.

· Condition: This symptom might occur if you configure the diagnostic monitor enable slot 2 test PortMonitor command on the device and then delete this command.

202406220515

· Symptom: A breakpoint occurs if SNMP reads packet counts for routing subinterfaces or routing aggregate subinterfaces.

· Condition: This symptom might occur if SNMP reads packet counts for routing subinterfaces or routing aggregate subinterfaces.

202406240193

· Symptom: The switch, which acts as a TM, cannot establish a SmartMC connection with a TC.

· Condition: This symptom occurs if the TC supports only SOAP.

202402011906

· Symptom: BFD session is not UP.

· Condition: Configure a BFD session with authentication, delete the BFD authentication, immediately remove the BFD configuration, and then configure other BFD sessions.

202312122064

· Symptom: On an IRF fabric that acts as a spine device, unicast packets and multicast packets between leaf devices are dropped for more than 10 seconds.

· Condition: This symptom occurs if the IRF fabric splits and member devices go down due to the MAD mechanism.

202401290654

· Symptom: A BGP interruption issue might occur upon an IRF member switchover. The issue can be recovered in eight minutes.

· Condition: This symptom might occur if you configure BGP on the device in an IRF fabric.

202403052202

· Symptom: A ping packet failure occurs on the device, and the NQA service becomes faulty.

· Condition: This symptom might occur if the CPU receives a large number of ICMP packets that exceed the CPU rate limit.

202402070389

· Symptom: In an M-LAG network, the state of the RADIUS server changes between blocked and active.

· Condition: This symptom occurs if the following conditions exist:

¡ The authentication load sharing mode for users attached to the M-LAG interface is even-mac or odd-mac.

¡ Both 802.1X authentication and MAC authentication are enabled on the M-LAG interface, and the mac-authentication carry user-ip command is executed on the M-LAG interface.

202404190164

· Symptom: Traffic fails to be forwarded at a low probability.

· Condition: This symptom might occur if interfaces on an interface module are up.

202403140268

· Symptom: An aggregation member port cannot learn ARP entries.

· Condition: This symptom occurs if the port is a member of an aggregation group configured with an IP subnet-based VLAN.

202403131137

· Symptom: The switch reboots when receiving multicast packets with destination address 239.255.255.250.

· Condition: This symptom might occur if Layer 3 multicast is enabled and the output interface of the multicast entry is flapped.

202402160037

· Symptom: The Telnet operation failed.

· Condition: This symptom occurs if an IP subnet-based VLAN is configured on a port of the device.

Resolved problems in R8307P10

202301050718

· Symptom: The subordinate device route does not take effect.

· Condition: This symptom might occur in an IRF fabric when the next hop of a route changes or flaps.

202401220378

· Symptom: The device interface panel view cannot be displayed on the Web interface.

· Condition: This symptom occurs if you log in to the Web interface of the device and then view the device interface panel.

202401242141

· Symptom: If you change the detection time from 500 ms to 100 ms, and then switch to hardware BFD, BFD session switchover fails and the software BFD session state still remains.

· Condition: This symptom occurs if you modify BFD parameter settings.

202401190577

· Symptom: After the status of a BFD MAD session is changed, the BFD MAD session starts operating in hardware mode and the BFD MAD function stops taking effect.

· Condition: This symptom might occur if the following conditions exist:

¡ BFD MAD is configured for an IRF fabric.

¡ The initial state of the related BFD session is changed from active to passive and then back to active.

202401151711

· Symptom: PIM register messages are continuously broadcast over the peer link.

· Condition: This symptom occurs if an M-LAG system in an M-LAG network receives multicast packets.

202401050710

· Symptom: After a DHCP lease expires, DNS server address information is repeatedly refreshed.

· Condition: This symptom might occur if the following conditions exist:

¡ No DNS server address is configured on an output interface.

¡ The output interface is enabled to obtain an address through DHCP, and a dynamic DNS server address is obtained.

202310231740

· Symptom: MAC address residues exist on the device.

· Condition: This symptom occurs under the following conditions:

a. Approximately 8000 MAC and 802.1X authentication users log in with authorization VSIs.

b. The users frequently log in and log out.

c. Log out all the users after a period of time.

202401231627

· Symptom: The output power provided by the PSR1300-54D-B DC power supply is insufficient.

· Condition: This symptom might occur if the PSR1300-54D-B DC power supply is used.

202401050702

· Symptom: The memory resources occupied by a BGP process continues to grow.

· Condition: This symptom might occur if the following conditions exist:

a. Frequent route updates occur on the local device.

b. The related BGP peers receive UPDATE messages so slowly that many UPDATE messages queue up on the local device and wait to be advertised.

202312250180

· Symptom: Memory is leaked.

· Condition: This symptom occurs if you execute the undo netanalysis rocev2 mode and netanalysis rocev2 vxlan-ip statistics acl commands repeatedly.

202401060591

· Symptom: RoCEv2 traffic statistics collection and global RoCEv2 packet loss analysis for a VXLAN tunnel do not take effect.

· Condition: This symptom occurs if the specified ACL for RoCEv2 traffic statistics collection contains too many rules.

202401050017

· Symptom: When you run automated scripts, PBR ECMP often fails to execute rules correctly.

· Condition: This symptom occurs when automated scripts are triggered.

202401241282

· Symptom: The controller failed to synchronously deploy the configuration.

· Condition: This symptom occurs if a leaf device comes online and is incorporated in the AD-Campus environment and has the ipv6 forwarding-conversational-learning command executed.

202401050316

· Symptom: The commit process on the master device has a memory leak of 560 bytes.

· Condition: This symptom might occur if a master/subordinate switchover is performed in an IRF fabric where bulk interfaces are configured (such as line or VLAN).

202312190850

· Symptom: An access leaf that does not have a DHCP client discards the DHCP OFFER packets, resulting in address allocation failure.

· Condition: This symptom might occur in a distributed gateway network if an access leaf that does not have a DHCP client receives a response from the DHCP server.

202312212158

· Symptom: Residual BFD session information exists.

· Condition: This symptom occurs if you perform the following operations:

a. Configure BFD for BGP in the BGP instance.

b. Configure static BFD globally.

c. Delete the static BFD configuration.

d. Delete the BFD for BGP configuration.

202311141523

· Symptom: In a VXLAN network, all VTEPs have a large number of unnecessary NS/NA packets on the tunnel side. As a result, the CPU usage is high.

· Condition: This symptom occurs if the centralized gateway device is disabling from learning the ND entries on the tunnel side and configured with local ND proxy.

202310240312

· Symptom: On an EVPN DRNI system with a tunnel peer link, the peer-link tunnel goes up slowly or even cannot go up.

· Condition: This symptom might occur if default VXLAN decapsulation is enabled for the IP address of loopback 0 and the IP address is the source IP addresses of non-peer-link VXLAN tunnels.

202312052029

· Symptom: The gRPC server failed to collect information from the vlan/vlanusernto1mapping sensor path.

· Condition: This symptom occurs when you configure gRPC subscription and the vlan/vlanusernto1mapping sensor path.

202312052019

· Symptom: In an EVPN M-LAG network, when a device is in a stress test and its configuration is repeatedly added and removed, residual EVPN VXLAN tunnels might remain undeleted.

· Condition: The symptom occurs if an M-LAG member device is in a stress test and its configuration is repeatedly added or removed on an EVPN M-LAG network.

202310231471

· Symptom: In an AC hierarchy network, when a unified wired and wireless AC acts as a local AC, APs cannot come online from the AC.

· Condition: This symptom might occur in an AC hierarchy network when a unified wired and wireless AC acts as a local AC.

202312051933

· Symptom: The authentication function of the ipv6 mac portal is not available.

· Condition: Used on the panel port of the SD series interface board.

Resolved problems in R8307P09

None

Resolved problems in R8307P08

202311180022

· Symptom: In an EVPN M-LAG network without peer links (IPv6 underlay), the downlink Layer 3 unicast traffic cannot be forwarded the tunnel-mode peer link.

· Condition: This symptom occurs if you shut down the M-LAG interface on one of the M-LAG member devices.

202312020490

· Symptom: IRF setup failed.

· Condition: This symptom occurs if the switch-mode command is executed to switch the devices to a non-default mode and the devices are used to form an IRF fabric.

202311291417

· Symptom: The The operation is not supported. message is displayed when the active port basic-license command is executed.

· Condition: This symptom occurs when you execute the active port basic-license command.

202311291314

· Symptom: In an M-LAG network, a server's MAC address has not successfully moved.

· Condition: This symptom occurs if a server moves between two M-LAG member devices.

202311241328

· Symptom: The device restarts abnormally.

· Condition: This symptom occurs if the device is installed with a power module that cannot be identified.

202311230575

· Symptom: The device cannot learn ND entries correctly.

· Condition: This symptom occurs when you enable VLAN mapping and enable ARP or ND suppression in a VSI and then disable VLAN mapping on a VXLAN network.

202311221801

· Symptom: The device cannot start up and enter the BootWare menu normally.

· Condition: This symptom occurs if the device restarts repeatedly.

202311220995

· Symptom: The configuration by the transceiver fec mode kp4 command on a port gets lost.

· Condition: This symptom occurs if the following conditions are met:

a. The port is inserted with the 100G BIDI transceiver module and both the speed 40000 and transceiver fec mode kp4 commands are executed.

b. After the configuration is saved, delete the configuration file suffixed with mdb, and then restart the device.

202311201880

· Symptom: A Layer 2 aggregate interface fails to be associated with a subnet-based VLAN.

· Condition: This symptom occurs if you enable BFD on a Layer 2 aggregate interface and associate it with a subnet-based VLAN.

202311170699

· Symptom: The if-match vxlan any command can match common IP packets or VXLAN TCP packets but cannot match VXLAN UDP packets.

· Condition: This symptom occurs if you use the if-match vxlan any command in a QoS policy applied to the inbound direction of an interface.

202311072184

· Symptom: The system displays that the power operating mode of the device is AC mode, but the actual power operating mode is HVDC.

· Condition: This symptom occurs if the device is provided with the high-voltage DC power source.

202311080605

· Symptom: A downlink device has a time deviation of over 128ns from the clock source.

· Condition: This symptom occurs if the device has the SyncE feature enabled and connects to downlink endpoints and the clock source through different cards.

202311141657

· Symptom: LACP BFD cannot be UP after MAD down.

· Condition: M-lag environment configuration static dual stack lacp bfd, oscillating IPL port.

202307010966

· Symptom: Failed to obtain the current values of the digital diagnostic parameters for non-H3C optical modules.

· Condition: This symptom occurs if when the following conditions are met:

¡ After the license that supports the non-H3C 100G/25G transceiver module is installed, you insert a non-H3C 25G transceiver module.

¡ The display transceiver diagnosis interface command is executed.

Resolved problems in R8307P06

202309191845

· Symptom: If the remote VXLAN packet is decapsulated, it cannot be forwarded by the local AC. Instead, it is discarded after being forwarded through the bypass tunnel.

· Condition: This symptom occurs if EVPN VXLAN multihoming is configured, the evpn multihoming vxlan-frr local command is executed, and the bypass links are equal-cost paths.

202309090844

· Symptom: The display mac-address command shows that OUI addresses are deleted. In probe view, the display system internal mac-address protocol command shows that the MAC address entries for voice VLANs are not deleted.

· Condition: This symptom occurs if OUI addresses are configured for voice VLANs and then the addresses are deleted after they are learned by the device.

202309061360

· Symptom: After you enable OSPF BFD for the interfaces on two directly connected devices, the devices cannot ping each other.

· Condition: This symptom occurs if you enable OSPF BFD for the interfaces on two directly connected devices.

202310091480

· Symptom: If you deploy packet filter on a Layer 3 Ethernet interface in the outbound direction, packet filter also takes effect on its subinterfaces.

· Condition: This symptom occurs if you deploy packet filter for the outbound direction of a Layer 3 Ethernet interface that has subinterfaces.

202309221271

· Symptom: DHCPv6 packets cannot trigger MAC authentication after the mac-authentication carry user-ip command is used. As a result, MAC authentication cannot take effect.

· Condition: This symptom occurs if MAC authentication is triggered by DHCPv6 packets after the mac-authentication carry user-ip command is used.

202309181567

· Symptom: In an M-LAG system, some 802.1X users exceptionally go offline.

· Condition: This symptom occurs in an M-LAG system if 802.1X users come online when the peer-link interface is flapping.

202309121593

· Symptom: After you configure VRRP authentication in the VPN environment, the device cannot correctly perform master/backup negotiation.

· Condition: This symptom occurs if you configure VRRP authentication for a Layer 3 interface.

202309211702

· Symptom: The switch does not send a route unreachable ICMPv6 error after receiving an IPv6 packet whose route is unreachable.

· Condition: This symptom occurs when the switch receives an IPv6 packet whose route is unreachable.

202309090197

· Symptom: Commands entered in M-LAG configuration synchronization view cannot be synchronized to the peer.

· Condition: This symptom occurs if strict intrusion detection is enabled on aggregate interfaces after port security intrusion detection mode is configured.

202309141332

· Symptom: The MAC address of the authenticated user is identified as authentication type on one M-LAG member device and as dynamic learning type on the other M-LAG member device.

· Condition: This symptom occurs if M-LAG interfaces are assigned to multiple VLANs in a multi-VLAN scenario with MAC address authentication for M-LAG and an online user accesses the interface in an authorized VLAN.

202309061213

· Symptom: Rate limiting on loopback detection packets fails.

· Condition: This symptom occurs if loop detection and SAVA are enabled.

Resolved problems in R8108P26

202309111777

· Symptom: The obtained physicalIndex information is incorrect.

· Condition: This symptom might occur if you obtain the port information of the device panel.

202309120642

· Symptom: After multiple interfaces borrow the same IP address to establish OSPF BFD sessions, only one session is in up state.

· Condition: This symptom might occur if multiple interfaces borrow the same IP address to establish OSPF BFD sessions.

202303260074

· Symptom: The third-party monitoring platform receives notifications of configuration file changes from the device, even when no changes have been made to the device's configuration.

· Condition: This symptom occurs when the feature to automatically save the running configuration to a configuration file is enabled.

202308081419

· Symptom: When the command to disable EEE is issued on a copper-interface device, the system erroneously interprets the command as enabling EEE.

· Condition: This symptom occurs if the command to disable EEE is issued on a copper-interface device.

202306300659

· Symptom: After the subordinate device in a two-device IRF fabric is MAD down, the interfaces of the uplink and downlink devices that connect the subordinate device do not go down immediately but after a while.

· Condition: This symptom occurs if all interfaces on the subordinate device in a two-device IRF fabric are MAD down.

202307242019

· Symptom: Fail to read the hh3cifPktBufInDrop and hh3cifPktBufEgDrop MIB objects to obtain information about traffic congestion and packet loss.

· Condition: This symptom occurs if an operation is performed to read the values of hh3cifPktBufInDrop and hh3cifPktBufEgDrop MIB objects.

202307261606

· Symptom: In a MAC address move record, the port remains consistent before and after the move.

· Condition: This symptom occurs if the MAC address entry is actively deployed by the device.

202308021663

· Symptom: The device gets stuck or reboots unexpectedly.

· Condition: This symptom occurs if configuration rollback or MDC deletion is performed when the following conditions exist:

¡ Free VLAN is configured on interfaces.

¡ A large number of MAC address exists or MDC is configured.

202308251456

· Symptom: MAD deployment fails for the VRRP group, and network forwarding is abnormal.

· Condition: This symptom occurs if you configure more than seven VRRP groups on an interface in an M-LAG network.

202307252014

· Symptom: In a non-dual-active gateway+VRRP network, the backup device cannot learn the ARP entry.

· Condition: This symptom occurs if a single attached interface of the backup device sends an ARP packet requesting the VRRP group address in an M-LAG non dual-active gateway+VRRP network.

202308291382

· Symptom: Statistics collected from the ifmgr/statistics sensor path does not contain statistics about dropped packets for aggregation groups when you configure gRPC in dial-out mode.

· Condition: This symptom occurs when you configure gRPC in dial-out mode and configure sensor path ifmgr/statistics.

202307261625

· Symptom: The VLAN interface with BFD MAD enabled is repeatedly reporting MAC move events.

· Condition: This symptom occurs if you reboot one of the IRF member devices after a master/subordinate switchover and BFD MAD is enabled on the VLAN interface.

202308100010

· Symptom: The system might fail to obtain temperature information, where the temperature displays as failed.

· Condition: This symptom occurs if you view device temperature information.

202308100592

· Symptom: In an overlay M-LAG network, forwarding of east-west IPv6 traffic might fail.

· Condition: This symptom occurs if an M-LAG interface is shut down in an overlay M-LAG network.

202308161268

· Symptom: The system prompts that a power supply is not supported on some devices.

· Condition: This symptom occurs if the device starts up correctly and some power modules of some models are installed.

202307010966

· Symptom: Failed to obtain the current values of the digital diagnostic parameters for non-H3C optical modules.

· Condition: This symptom occurs if when the following conditions are met:

¡ After the license that supports the non-H3C 100G/25G transceiver module is installed, you insert a non-H3C 25G transceiver module.

¡ The display transceiver diagnosis interface command is executed.

202307181156

· Symptom: In an EVPN M-LAG network, the member devices might not advertise BGP routes, and Layer 3 traffic cannot be forwarded.

· Condition: This symptom occurs if BGP EVPN sessions are set up in an EVPN M-LAG network.

202306091054

· Symptom: When an action is added to an empty behavior in a QoS policy applied to an interface, the error message The behavior is empty is prompted.

· Condition: This symptom occurs if the corresponding class contains an unsupported ACL rule.

202306081926

· Symptom: In the IPv6 scenario, the BFD echo-packet-mode session does not come up.

· Condition: This symptom occurs if you repeatedly bring up and shut down the VLAN interface multiple times, and make sure that no ND entries exist.

202306121865

· Symptom: The maximum number of VLAN interfaces that can be created might differ in resource management before and after VLAN interface creation.

· Condition: This symptom might occur if the following operations are performed:

a. Boot the device with initial configuration.

b. View the vlanintf filed of resource capacity management.

c. Create VLAN interfaces until the limit is reached.

d. View the vlanintf filed of resource capacity management.

202305301349

· Symptom: After you configure command aliases in Tcl configuration view, the aliases do not take effect when you enter system view.

· Condition: This symptom occurs if you configure command aliases in bulk in Tcl configuration view.

202306141399

· Symptom: When you configure the static BFD session in echo packet mode for the first time, the BFD session cannot come up through negotiation.

· Condition: This symptom occurs if you configure only an IP address for the VLAN interface, make sure no ARP entries exist, and then configure a static BFD session in echo packet mode.

202306071246

· Symptom: A member port in an aggregation group cannot be selected on an IRF fabric.

· Condition: This symptom occurs if the following operations are performed on the IRF fabric:

a. Configure S-MLAG settings and set the maximum number of selected ports for the aggregation group.

b. Roll back the configuration to the configuration that does not contain S-MLAG settings or the selected port upper limit.

202306091784

· Symptom: After an accounting action is deleted from a traffic behavior in a QoS policy applied to the control plane, traffic statistics collected for the CAR action in the traffic behavior.

· Condition: This symptom occurs after you delete an accounting action from a traffic behavior in a QoS policy applied to the control plane.

202306021680

· Symptom: A port inserted with a transceiver module cannot come up.

· Condition: This symptom occurs when the following conditions are met:

¡ The 40G cable is first connected to the 100G port and the FEC mode is set to RS-FEC or None when the system prompts that the port does not support the cable.

¡ Then, the FEC mode is changed to auto, the 40G cable is removed, and the 100G transceiver module is installed.

202306011581

· Symptom: The device repeated reboots abnormally.

· Condition: This symptom occurs if you create multiple subbinterfaces on the device, configure PoE settings on these subinterfaces, and then reboot the device after saving the configuration.

202306091059

· Symptom: The switch fails to detect unsupported match criteria in a QoS policy applied to the control plane.

· Condition: This symptom occurs if you configure a control-plane protocol match criterion before the unsupported match criteria.

202307131489

· Symptom: MAC authentication cannot be configured in conjunction with 802.1X EAD assistant.

· Condition: This symptom occurs when the device runs correctly.

202211071059

· Symptom: On an EVPN network, the device drops the requests received from an endpoint or the replied ARP or ND packets and fails to flood them to the remote end.

· Condition: This symptom might occur when you use the arp suppression enable or ipv6 nd suppression enable command to enable ARP or ND suppression on the gateway interface and the VSI gateway interface is down.

Resolved problems in R8108P25

202306150417

· Symptom: PTP messages are incorrectly matched by multicast routes and are not routed to the designated CPU queue, resulting in limited receive speed.

· Condition: This symptom occurs if you configure multicast PTP message transmission over UDP and enable multicast routing.

202306160353

· Symptom: On a port enabled with 802.1X authentication and configured with free VLANs for port security, the free VLANs cannot take effect.

· Condition: This symptom occurs on a port enabled with 802.1X authentication and configured with free VLANs for port security.

202306151297

· Symptom: In an M-LAG VXLAN system, the M-LAG peer does not synchronize ARP entries from the local device.

· Condition: This symptom occurs if the traffic outgoing interfaces change and ARP moves occur on the local device.

202306201165

· Symptom: An exception occurs when the device forwards traffic through Layer 3 routing.

· Condition: This symptom occurs if the following conditions exist:

¡ Multiple routes that match the destination address of the traffic with different mask lengths have been added and then deleted.

¡ The forwarding table still has a route that does not match the destination address of the traffic but has a mask longer than the mask of the routes that the traffic should match.

202305300597

· Symptom: An interface inserted with a 10G copper transceiver module comes up and goes down, or does not come up.

· Condition: This symptom occurs if an interface is inserted with a 10G copper transceiver module on the device.

202304211413

· Symptom: COA authorized a user session timeout, but the session-timeout remaining time attribute is lost after a primary/backup switchover.

· Condition: This symptom might occur if COA only authorizes the session-timeout for a user and a primary/backup switchover occurs before the next accounting update.

202304230939

· Symptom: Failed to issue the dhcp flood-protection enable command on a VSI interface through NETCONF.

· Condition: This symptom might occur if you issue the dhcp flood-protection enable command on a VSI interface through NETCONF.

202305040997

· Symptom: One 10G port is up and the other 10G port is down on the device if a 100M transceiver module is installed in these two ports to connect them.

· Condition: This symptom might occur if a 100M transceiver module is installed in two 10G ports on the device to connect them.

202305251742

· Symptom: A device restarts unexpectedly.

· Condition: This symptom might occur if the following conditions exist:

¡ The DHCP snooping feature is enabled on the device and the client-facing interface is configured with N:1 VLAN mapping.

¡ The remote VLAN interface uses DHCP for IP address acquisition.

202210170316

· Symptom: A DHCP client cannot obtain an IP address.

· Condition: This symptom might occur if the client-facing port is configured with both N:1 VLAN mapping and DHCP snooping.

202304101321

· Symptom: The PIM neighbor goes down when an interface receives a large number of unknown multicast packets.

· Condition: This symptom occurs if an interface receives a large number of unknown multicast packets.

202304171816

· Symptom: Multi-card flow mirroring does not take effect.

· Condition: This symptom occurs if the following operations are performed:

a. Configure multi-card flow mirroring with an action of flow-mirroring traffic to an interface.

b. Change the action to flow-mirror traffic to a monitoring group.

202305170363

· Symptom: If the second-level memory alarm threshold is exceeded on an M-LAG member device in a Layer 2 multicast-supported M-LAG system, and it receives leave and join messages for a multicast group, the Layer 2 multicast forwarding table might not be recovered after the second-level alarm is cleared.

· Condition: This symptom might occur if the following conditions exist:

¡ The second-level memory alarm threshold is exceeded on an M-LAG member device.

¡ The M-LAG member device receives leave and join messages for a multicast group.

202304270443

· Symptom: On an interface enabled with triple authentication (802.1X authentication, MAC authentication, and Web authentication), a Web authentication user fails to come online.

· Condition: This symptom occurs if the Web authentication user has failed MAC authentication.

202305060576

· Symptom: In a VXLAN M-LAG system, an M-LAG member device is configured with a local static MAC address entry for L2VPN, but that entry cannot be found on the peer M-LAG member device. The count of the MAC address entries increase in the output from the display l2vpn mac-address count command.

· Condition: This symptom occurs if an M-LAG member device in a VXLAN M-LAG system is configured with a local static MAC address entry for L2VPN.

202304211453

· Symptom: Invalid addresses can be deployed without address check.

· Condition: This symptom might occur if you specify an invalid IP address as the address of the HWTACACS authorization, authentication, or accounting server.

202304231674

· Symptom: After the packet statistics function for a VXLAN tunnel is enabled, there are no outgoing packet statistics for that tunnel.

· Condition: This symptom occurs if ACs and the associated VXLAN tunnel are located on different modules and the packet statistics function is enabled for the VXLAN tunnel.

202304191416

· Symptom: All VLAN mappings on an interface do not take effect.

· Condition: This symptom occurs if multiple VLAN mappings are configured on an interface.

202304201556

· Symptom: During the online process of a portal user, the deployed display portal user command and display portal user verbose command display inconsistent ACL states for the user.

· Condition: This symptom might occur if an authorization ACL is assigned to the portal user, and you view user information by using the two display commands before the user online state becomes stable.

202304191573

· Symptom: In an M-LAG system with various types of traffic, network flapping causes the member devices to restart unexpectedly.

· Condition: This symptom occurs if network flapping occurs and an M-LAG system receives multiple types of traffic.

202304100973

· Symptom: M-LAG member devices cannot synchronize DHCP snooping entries between them within a period of time.

· Condition: This symptom occurs if DHCP snooping is disabled when the peer link is flapping.

Resolved problems in R8108P22

202303010079

· Symptom: Only an IPv4 entry is created at the lower layer after a non-genetic QoS policy is applied to the outbound direction of an interface. No IPv6 entry is created.

· Condition: This symptom occurs if the traffic class in the QoS policy is configured to match all packets.

202304101234

· Symptom: After you apply a packet filter to the inbound direction of an aggregate interface and then remove all member ports from the aggregate interface, the number of remaining QoS and ACL resources becomes 0, and no other ACL-related functions can be configured.

· Condition: This symptom occurs if you apply a packet filter to the inbound direction of an aggregate interface and then remove all member ports from the aggregate interface.

202304101924

· Symptom: An aggregate interface cannot be configured as a peer-link interface. The system displays that "The interface can't be configured as a peer link interface, because it has port security, 802.1X, MAC authentication, or Web authentication settings."

· Condition: This symptom might occur when you configure an aggregate interface as a peer-link interface after a configuration conflict occurred between port security mode and 802.1X or MAC authentication on the interface.

202303010065

· Symptom: The reboot reason displayed on the device is different from the real reboot reason.

· Condition: This symptom might occur if you reboot a device in an IRF fabric with a ring topology.

202303010113

· Symptom: The service slot setting for VLAN-interface 1 is lost.

· Condition: This symptom occurs if the smartmc outbound command is executed in Layer 3 Ethernet interface view, the running configuration is saved, and then the device is rebooted.

202303151291

· Symptom: Deletion of a MAC-to-VLAN entry fails.

· Condition: This symptom occurs if unambiguous MAC-to-VLAN entries are configured and then a MAC-to-VLAN entry is deleted.

202303010081

· Symptom: An error occurred in deleting a MAC-to-VLAN entry.

· Condition: This symptom occurs if ambiguous MAC-to-VLAN entries are configured and the most recently configured entry is deleted.

202303010080

· Symptom: Traffic is forwarded incorrectly.

· Condition: This symptom occurs if MAC-to-VLAN entries are configured and then the PVID is modified on an interface.

202304111039

· Symptom: The MAC authentication feature fails to take effect on an aggregate interface. Packets with unknown source MAC addresses fail to trigger MAC authentication on the interface.

· Condition: This symptom might occur on aggregate interfaces that perform MAC authentication in either of the following situations:

¡ Master/subordinate switchover upon reboot of the master device in an IRF fabric. In this situation, a packet cannot trigger MAC authentication if it arrives on a link aggregation member interface on the new master device.

¡ Incoming packets cannot trigger MAC authentication on any link aggregation member interfaces after you enable and then disable unknown source MAC-triggered ARP probing or unknown source MAC-triggered ND probing. The two features are configurable by using the arp unknown-source-mac-probing enable and ipv6 nd unknown-source-mac-probing enable commands.

202303010073

· Symptom: Secondary VLANs cannot communicate at Layer 3.

· Condition: This symptom occurs if the specified secondary VLANs of a primary VLAN are configured to communicate at Layer 3.

202303131922

· Symptom: After an H3C device establishes a MACsec session with a device using the chip of another vendor, the devices can exchange traffic, but the H3C device cannot successfully ping the peer IP.

· Condition: This symptom occurs if an H3C device establishes a MACsec session with a device using the chip of another vendor.

202303010106

· Symptom: Unrelated MAC addresses are deleted.

· Condition: This symptom occurs if you configure the OUI addresses that can be recognized by the voice VLAN feature and then delete an OUI address.

202303010094

· Symptom: The unicast packets of a primary VLAN are broadcast.

· Condition: This symptom occurs if you create a primary VLAN and secondary VLANs and transmit traffic between them.

202303010078

· Symptom: The CPU usage is high.

· Condition: This symptom occurs if the following operations are performed:

a. Configure periodical sampling in gRPC dial-out mode.

b. Configure the sensor path as mpls/labelstatuses.

c. The periodical data sampling interval is small (1 second).

d. A large amount of data is collected.

202303010046

· Symptom: The ports on an LSWM2SP2PB or LSWM2SP4PB interface module fail to come up.

· Condition: This symptom might occur if you remove or reinsert an LSWM2SP2PB or LSWM2SP4PB interface module.

202303231747

· Symptom: The undo service command cannot be executed in VLAN interface view.

· Condition: This symptom might occur if you specify a Layer 3 interface as the egress interface of the SmartMC network.

202303010091

· Symptom: The MAC addresses of some users remain.

· Condition: This symptom occurs if 4K MAC authentication users come online on a single-homed interface and repeatedly come online and go offline on an EVPN M-LAG network.

202303010068

· Symptom: If users go offline after master/subordinate switchover, URL resources remain in the hardware of the new master member device.

· Condition: This symptom might occur if MAC authentication users come online with URLs through aggregate interfaces on an IRF fabric and the users go offline after master/subordinate switchover.

202303010115

· Symptom: The portsec process might be abnormal, and core files are generated.

· Condition: This symptom occurs if the following events occur:

a. An EVPN M-LAG system switches from MAC authentication to none authentication when the MAC authentication server is unreachable and a large number of MAC authentication users are accessing the network.

b. The memory alarm threshold is reached, and users go offline.

c. The memory usage drops below the alarm threshold, and the MAC authentication server becomes active after a manual or automatic switchover.

d. The peer-link interfaces are restarted to flap the peer link.

202303010105

· Symptom: A VXLAN M-LAG system forwards duplicate unknown Layer 2 multicast or broadcast traffic.

· Condition: This symptom occurs if the following events occur:

a. An uplink fails.

b. An M-LAG member device receives unknown Layer 2 multicast or broadcast traffic on a VXLAN tunnel interface.

c. The traffic is forwarded over the peer link, and broadcast isolation does not take effect on the traffic.

202303010050

· Symptom: M-LAG member devices do not synchronize DHCP snooping entries between them.

· Condition: This symptom occurs if the peer-link interfaces are restarted to flap the peer link.

202302081392

· Symptom: If BFD MAD is enabled for VLAN interfaces, after the IRF fabric splits and then merges again, BFD MAD interfaces contain an additional port.

· Condition: This symptom occurs if BFD MAD is enabled for VLAN interfaces and the IRF fabric splits and then merges again.

202303170447

· Symptom: If a device is pinged for a long period of time, packets will be randomly dropped.

· Condition: This symptom occurs if a single-homed device sends RARP packets on an EVPN+M-LAG overlay network.

202303010099

· Symptom: In custom profile view, OSPF-related commands cannot be deployed because the ospf command with the vpn-instance or router-id keyword specified cannot be deployed.

· Condition: This issue might occur if the following conditions exist:

a. When you configure GIR, you configure the ospf command with the vpn-instance or router-id keyword specified in custom profile view.

b. After you save the configuration, you restart the device with a .cfg configuration file.

202303310597

· Symptom: After the behavior of a class-behavior association in an applied QoS policy is changed, the old behavior still takes effect and the new behavior does not take effect.

· Condition: This symptom occurs if the following conditions exist:

¡ The two behaviors are configured with actions of mirroring traffic to monitoring groups.

¡ The ACL used in the traffic class contains multiple rules.

202303010092

· Symptom: Failure message was received upon execution of the undo sflow sampling-rate command in interface view.

· Condition: This symptom might occur if you execute the undo sflow sampling-rate command after you have configured flow sampling by using the sflow sampling-rate command on an interface.

202303010057

· Symptom: The system incorrectly displays the Failed to obtain information because the system is synchronizing configuration data message upon execution of the display dot1x command while 802.1X is disabled. In this situation, the system should have displayed the 802.1X is not configured message.

· Condition: This symptom might occur when the following conditions are met:

¡ Port security is enabled, but 802.1X is disabled.

¡ VLAN groups are present.

202302081502

· Symptom: Port mirroring does not take effect.

· Condition: This symptom occurs if the following operations are performed:

a. Configure a port mirroring group. Configure an aggregate interface as the mirroring port, and configure multiple singe interfaces as the monitor ports.

b. Remove a member port from the aggregate interface acting as the mirroring port.

c. Remove a monitor port from the mirroring group.

d. Assign the member port to the aggregate interface acting as the mirroring port again.

202303010074

· Symptom: Configuration rollback failed, and an INQA_FLAG_FAIL message is displayed.

· Condition: This symptom occurs if you configure iNQA for the device, and then perform configuration rollback between two configuration files containing different values for the flag loss-measure tos-bit field.

202304102023

· Symptom: Many packets are lost after a switchback to the primary interface.

· Condition: This symptom occurs if a lot of ACs are created on the device and the interface where the AC resides comes up and goes down frequently.

202302152023

· Symptom: The four lowest-numbered interfaces on a device fails to come up.

· Condition: This symptom occurs if you change the IRF member ID of a device and then reboot the device.

202302061165

· Symptom: An IRF fabric with MVXLAN configured forwards VXLAN Layer 2 multicast traffic incorrectly.

· Condition: This symptom occurs if the IRF fabric is a multicast source, the outgoing interfaces in multicast forwarding entries are VXLAN unicast tunnel interfaces, and an IRF master/subordinate member switchover occurs.

202303010054

· Symptom: A VXLAN VTEP might be unable to learn MAC address entries.

· Condition: This symptom occurs if a VXLAN tunnel flaps and then goes down during MAC address learning on the VXLAN tunnel interface.

202302150749

· Symptom: The static BFD echo session cannot come up correctly upon device reboot.

· Condition: This symptom occurs if you configure a static BFD echo session, set the minimum echo packet receiving interval to 0, and then reboot the device.

202302061345

· Symptom: The ports on a subcard fails to start up when the subcard reboots.

· Condition: This symptom might occur if you the reboot command is executed to reboot a subcard.

202302201775

· Symptom: The switch does not create dropping-unknown entries for incoming double-tagged unknown multicast packets and does not drop them when dropping unknown multicast data packets is enabled.

· Condition: This symptom occurs when the switch is enabled with dropping unknown multicast data packets in IGMP snooping or MLD snooping and receives double-tagged unknown multicast packets.

202302160299

· Symptom: After the behavior of a class-behavior association in an applied QoS policy is changed, the old behavior still takes effect and the new behavior does not take effect.

· Condition: This symptom occurs if you apply a non-genetic QoS policy and then change the traffic behavior.

202302110604

· Symptom: A QoS policy applied to an aggregate interface does not take effect.

· Condition: This symptom occurs if the traffic behavior is configured with an action of marking a local QoS ID.

Resolved problems in R6010P08

202301170683

· Symptom: BFD session flapping occurs, resulting in packet loss.

· Condition: This symptom might occur if you remove the fan tray from the device and then install it again after configuring a large number of BFD sessions on the device.

202302090443

· Symptom: Partitioning a USB disk succeeds at the first time but fails at the second time.

· Condition: This symptom might occur if you execute the fdisk usb command twice to partition a USB disk installed on a device.

202302100481

· Symptom: A MAC address moves between the M-LAG interfaces in an M-LAG group.

· Condition: This symptom might occur if the M-LAG interfaces in an M-LAG group receive packets sourced from the same MAC address.

202302031189

· Symptom: The device restarts abnormally.

· Condition: This symptom might occur if a large number of BFD sessions exist, and the device sends and receives BFD packets very frequently.

202302152023

· Symptom: The four lowest numbered ports on the device failed to start up after you edited the IRF member ID of the device and restarted the device.

· Condition: This symptom might occur if you edit the IRF member ID of the device and restart the device.

202302170327

· Symptom: When the device receives attack packets with TTL 1, the EBGP sessions of the device might flap. The probability of EBGP session flapping depends on the reception rate of attack packets.

· Condition: This symptom might occur if the device receives attack packets with TTL 1 after EBGP session establishment.

202209201309

· Symptom: BFD MAD fails to detect a multi-active collision when an IRF fabric is split.

· Condition: This symptom occurs if the interface used for BFD MAD is bound to a VPN instance.

202211220574

· Symptom: A leaf device might fail to forward traffic in an EVPN VXLAN with asymmetric IRB distributed gateways.

· Condition: This symptom might occur if the leaf device has multiple ECMP routes whose next hops contain both ACs and tunnels.

202210200099

· Symptom: Ethernet service instances cannot be automatically created on a hybrid port.

· Condition: This symptom might occur if Ethernet service instances are automatically created on a hybrid port after VLAN-to-VXLAN mapping is enabled.

202211230586

· Symptom: In an EVPN M-LAG system, a leaf device cannot ping a downstream access device after being rebooted.

· Condition: This symptom might occur if the leaf device reboots with spanning tree configuration.

202210280988

· Symptom: The spanning tree status of an uplink M-LAG interface is abnormal when multiple M-LAG systems are cascaded.

· Condition: This symptom might occur if the following conditions exist:

¡ Spanning is disabled on all M-LAG member devices, and the uplink M-LAG interfaces are root port.

¡ Spanning is disabled on all M-LAG interfaces, and a primary/secondary device switchover is performed when the uplink M-LAG interface on the secondary device is down.

Resolved problems in R6010P04

First release.

Troubleshooting resources

To obtain troubleshooting resources for the product:

1. Access Technical Documents at http://www.h3c.com/en/Technical_Documents.

2. Select the device category and model.

3. Select the Maintain or Maintenance menu.

Technical support

To obtain technical assistance, contact H3C by using one of the following methods:

· Email:

[email protected] (countries and regions except Hong Kong, China)

[email protected] (Hong Kong, China)

· Technical support hotline number. To obtain your local technical support hotline number, go to the H3C Service Hotlines website: https://www.h3c.com/en/Support/Online_Help/Service_Hotlines/

To access documentation, go to the H3C website at http://www.h3c.com/en/.

Appendix A Feature list

Hardware features

· Please refer to H3C S5590-HI[EI]&S5500V3-HI Switch Series Installation Guide

Software features

Table 5 Main Software features of the S5590-EI series

Feature	S5590-48T4XC-EI S5590-28T8XC-EI S5590-28S8XC-EI S5590-48S4XC-EI S5590-28P8XC-EI S5590-48P6XC-EI S5590-24X4YC-EI S5590-48UM4YC-EI S5590-48TS4X2QC-EI S5590-24UXM4YC-EI S5590-48UXM4YC-EI S5590-48UN4Y2CC-EI S5590-32UN4X4Y2CC-EI
Ethernet	802.1Q DLDP LLDP Static MAC address Blackhole MAC address MAC learning limit Port mirroring Flow mirroring Port-isolation 802.1d（STP）/802.1w（RSTP）/802.1s（MSTP） Static aggregation Dynamic aggregation
IP routing	Static routing RIPv1/v2 and RIPng OSPFv1/v2/v3 BGP and BGP4+ for IPv6 Equal-cost multi-path routing (ECMP) and policy routing VRRP/VRRPv3
Multicast	IGMP v1/v2/v3 and MLD v1/v2 IGMP Snooping v1/v2/v3 and MLD Snooping v1/v2 PIM-DM, PIM-SM and PIM-SSM PIM6-DM, PIM6-SM and PIM6-SSM
ACL/QoS	Layer 2 to Layer 4 packet filtering Bi-directional ACLs (inbound and outbound) Traffic classification based on source MAC, destination MAC, source IP, destination IP, TCP/UDP port, and VLAN VLAN-based ACL issuing 802.1p priority and DSCP priority Time range-based ACL Rate limit for receiving and transmitting packets (a minimum CIR of 8 Kbps) Packet redirection Committed Access Rate (CAR) Flexible queue scheduling algorithms based on both port and queue, including SP, WRR, and SP+WRR
SDN/Openflow	OpenFlow 1.3 Multiple controllers (equal/master/slave controller role) Concurrent processing of multiple flow tables Group table Meter
MPLS	Support MCE
IRF2	IRF2 Distributed device management, distributed link aggregation, and distributed resilient routing Stacking through standard Ethernet interfaces Local device stacking and remote device stacking
Security	Hierarchical user management and password protection MAC-based authentication 802.1X Storm constrain Guest VLAN AAA authentication RADIUS authentication HWTACACS SSH 2.0 Port isolation Port security EAD Dynamic ARP detection BPDU guard and root guard uRPF IP/Port/MAC binding Plaintext authentication and MD5 authentication for OSPF and RIPv2 packets Public Key Infrastructure (PKI) IP Source Guard
Management and maintenance	Configuration through CLI, Telnet, and console port SNMP v1/v2/v3 Remote Monitoring (RMON) alarm, event, and history recording IMC network management system System log, alarming based on severity, debugging information output NTP, SNTP Power, fan, and temperature alarming Ping and Tracert Virtual Cable Test (VCT) Device Link Detection Protocol (DLDP) LLDP, LLDP-MED Loopback detection
Reliability	STP, RSTP, MSTP BPDU protection, root protection, loop protection, support PVST LACP DLDP RRPP ERPS (Ethernet Ring Protection Protocol) SmartLink VRRP

Appendix B Fixed security vulnerabilities

Fixed security vulnerabilities in R6010P04

None

Appendix C Upgrading software

The following information describes how to upgrade software while the router is operating normally or when the router cannot correctly start up.

System software file types

System software images are in .bin format (for example, main.bin) and run at startup. You can set a system software image as a main, backup, or secure image.

At startup, the router always attempts to boot first with the main system software image. If the attempt fails, for example, because the image file is corrupted, the router tries to boot with the backup system software image. If the attempt still fails, the router tries to boot with the secure system software image. If all attempts fail, the router displays a failure message.

Upgrade methods

You can upgrade system software by using one of the following methods:

Upgrade method	Remarks
Upgrading from the CLI	· You must reboot the router to complete the upgrade. · This method can interrupt ongoing network services.
Upgrading from the Boot menu	Use this method when the router cannot correctly start up.

Upgrade method

Remarks

Upgrading from the CLI

· You must reboot the router to complete the upgrade.

· This method can interrupt ongoing network services.

Upgrading from the Boot menu

Use this method when the router cannot correctly start up.

Preparing for the upgrade

Verifying device status

Example:

IMPORTANT:

Before you perform an IRF master/subordinate switchover or active/standby MPU switchover, verify that the device is in stable state.

1. Verify that the system state, redundancy state, and state of each slot are stable.

<Sysname> display system stable state

System state :Stable

Redundancy state :Stable

Slot CPU Role State

1 0 Active Stable

2. If the device is unstable, use the following commands to troubleshoot the issue:

¡ Use the display device command to verify that the device is operating correctly.

¡ Use the display ha service-group command to verify that bulk backup has been finished for all modules.

¡ Use the display system internal process state command in probe view to verify that services are running correctly.

3. If a slot persists in unstable state or there are other unrecoverable issues, contact the technical support.

Setting up the upgrade environment

Before you upgrade system software, complete the following tasks:

· Set up the upgrade environment as shown in Figure 1.

· Configure routes to make sure that the router and the file server can reach each other.

· Run a TFTP or FTP server on the file server.

· Log in to the CLI of the router through the console port.

· Copy the upgrade file to the file server and correctly set the working directory on the TFTP or FTP server.

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

Figure 1 Setting up the upgrade environment

Upgrading from the CLI

This section uses a two-member IRF fabric as an example to describe how to upgrade software from the CLI. If you have more than two subordinate switches, repeat the steps for the subordinate switch to upgrade their software. If you are upgrading a standalone switch, ignore the steps for upgrading the subordinate switch. For more information about setting up and configuring an IRF fabric, see the installation guide and Virtual Technologies configuration guide for the H3C S5560X-EI switch series.

Preparing for the upgrade

Before you upgrade software, complete the following tasks:

4. Log in to the IRF fabric through Telnet or the console port. (Details not shown.)

5. Identify the number of IRF members, each member switch's role, and IRF member ID.

<Sysname> display irf

MemberID Role Priority CPU-Mac Description

*+1 Master 2 0023-8927-afdc ---

2 Standby 1 0023-8927-af43 ---

--------------------------------------------------

* indicates the device is the master.

+ indicates the device through which the user logs in.

The Bridge MAC of the IRF is: 0023-8927-afdb

Auto upgrade : no

Mac persistent : 6 min

Domain ID : 0

6. Verify that each IRF member switch has sufficient storage space for the upgrade images.

IMPORTANT:

Each IRF member switch must have free storage space that is at least two times the size of the upgrade image file.

# Identify the free flash space of the master switch.

<Sysname> dir

Directory of flash:

0 -rw- 41424 Aug 23 2013 02:23:44 startup.mdb

1 -rw- 3792 Aug 23 2013 02:23:44 startup.cfg

2 -rw- 53555200 Aug 23 2013 09:53:48 system.bin

3 drw- - Aug 23 2013 00:00:07 seclog

4 drw- - Aug 23 2013 00:00:07 diagfile

5 drw- - Aug 23 2013 00:00:07 logfile

6 -rw- 9959424 Aug 23 2013 09:53:48 boot.bin

7 -rw- 9012224 Aug 23 2013 09:53:48 backup.bin

524288 KB total (453416 KB free)

# Identify the free flash space of each subordinate switch, for example, switch 2.

<Sysname> dir slot2#flash:/

Directory of slot2#flash:/

0 -rw- 41424 Jan 01 2011 02:23:44 startup.mdb

1 -rw- 3792 Jan 01 2011 02:23:44 startup.cfg

2 -rw- 93871104 Aug 23 2013 16:00:08 system.bin

3 drw- - Jan 01 2011 00:00:07 seclog

4 drw- - Jan 01 2011 00:00:07 diagfile

5 drw- - Jan 02 2011 00:00:07 logfile

6 -rw- 13611008 Aug 23 2013 15:59:00 boot.bin

7 -rw- 9012224 Nov 25 2011 09:53:48 backup.bin

524288 KB total (453416 KB free)

7. Compare the free flash space of each member switch with the size of the software file to load. If the space is sufficient, start the upgrade process. If not, go to the next step.

8. Delete unused files in the flash memory to free space:

CAUTION:

· To avoid data loss, do not delete the current configuration file. For information about the current configuration file, use the display startup command.

· The delete /unreserved file-url command deletes a file permanently and the action cannot be undone.

· The delete file-url command moves a file to the recycle bin and the file still occupies storage space. To free the storage space, first execute the undelete command to restore the file, and then execute the delete /unreserved file-url command.

# Delete unused files from the flash memory of the master switch.

<Sysname> delete /unreserved flash:/backup.bin

The file cannot be restored. Delete flash:/backup.bin?[Y/N]:y

Deleting the file permanently will take a long time. Please wait...

Deleting file flash:/backup.bin...Done.

# Delete unused files from the flash memory of the subordinate switch.

<Sysname> delete /unreserved slot2#flash:/backup.bin

The file cannot be restored. Delete slot2#flash:/backup.bin?[Y/N]:y

Deleting the file permanently will take a long time. Please wait...

Deleting file slot2#flash:/backup.bin...Done.

Downloading software images to the master switch

Before you start upgrading software images packages, make sure you have downloaded the upgrading software files to the root directory in flash memory. This section describes downloading an .ipe software file as an example.

The following are ways to download, upload, or copy files to the master switch:

· FTP download from a server

· FTP upload from a client

· TFTP download from a server

Prerequisites

If FTP or TFTP is used, the IRF fabric and the PC working as the FTP/TFTP server or FTP client can reach each other.

Prepare the FTP server or TFTP server program yourself for the PC. The switch series does not come with these software programs.

FTP download from a server

You can use the switch as an FTP client to download files from an FTP server.

To download a file from an FTP server, for example, the server at 10.10.110.1:

9. Run an FTP server program on the server, configure an FTP username and password, specify the working directory and copy the file, for example, newest.ipe, to the directory.

10. Execute the ftp command in user view on the IRF fabric to access the FTP server.

<Sysname> ftp 10.10.110.1

Trying 10.10.110.1...

Press CTRL+C to abort

Connected to 10.10.110.1(10.10.110.1).

220 FTP service ready.

User (10.10.110.1:(none)):username

331 Password required for username.

Password:

230 User logged in.

11. Enable the binary transfer mode.

ftp> binary

200 Type set to I.

12. Execute the get command in FTP client view to download the file from the FTP server.

ftp> get newest.ipe

227 Entering Passive Mode (10,10,110,1,17,97).

125 BINARY mode data connection already open, transfer starting for /newest.ipe

226 Transfer complete.

32133120 bytes received in 35 seconds (896. 0 kbyte/s)

ftp> bye

221 Server closing.

FTP upload from a client

You can use the IRF fabric as an FTP server and upload files from a client to the IRF fabric.

To FTP upload a file from a client:

On the IRF fabric:

13. Enable FTP server.

<Sysname> system-view

[Sysname] ftp server enable

14. Configure a local FTP user account:

# Create the user account.

[Sysname] local-user abc

# Set its password and specify the FTP service.

[Sysname-luser-manage-abc] password simple pwd

[Sysname-luser-manage-abc] service-type ftp

# Assign the network-admin user role to the user account for uploading file to the working directory of the server.

[Sysname-luser-manage-abc] authorization-attribute user-role network-admin

[Sysname-luser-manage-abc] quit

[Sysname] quit

On the PC:

15. Log in to the IRF fabric (the FTP server) in FTP mode.

c:\> ftp 1.1.1.1

Connected to 1.1.1.1.

220 FTP service ready.

User(1.1.1.1:(none)):abc

331 Password required for abc.

Password:

230 User logged in.

16. Enable the binary file transfer mode.

ftp> binary

200 TYPE is now 8-bit binary.

17. Upload the file (for example, newest.ipe) to the root directory of the flash memory on the master switch.

ftp> put newest.ipe

200 PORT command successful

150 Connecting to port 10002

226 File successfully transferred

ftp: 32133120 bytes sent in 64.58 secs (497.60 Kbytes/sec).

TFTP download from a server

To download a file from a TFTP server, for example, the server at 10.10.110.1:

18. Run a TFTP server program on the server, specify the working directory, and copy the file, for example, newest.ipe, to the directory.

19. On the IRF fabric, execute the tftp command in user view to download the file to the root directory of the flash memory on the master switch.

<Sysname> tftp 10.10.110.1 get newest.ipe

Press CTRL+C to abort.

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

Dload Upload Total Spent Left Speed

100 30.6M 0 30.6M 0 0 143k 0 --:--:-- 0:03:38 --:--:-- 142k

Upgrading the software images

To upgrade the software images:

20. Specify the upgrade image file (newest.ipe in this example) used at the next startup for the master switch, and assign the M attribute to the boot and system images in the file.

<Sysname> boot-loader file flash:/newest.ipe slot 1 main

Verifying image file..........Done.

Images in IPE:

boot.bin

system.bin

This command will set the main startup software images. Continue? [Y/N]:y

Add images to target slot.

Decompressing file boot.bin to flash:/boot.bin....................Done.

Decompressing file system.bin to flash:/system.bin................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.

21. Specify the upgrade image file as the main startup image file for each subordinate switch. This example uses IRF member 2. (The subordinate switches will automatically copy the file to the root directory of their flash memories.)

<Sysname> boot-loader file flash:/newest.ipe slot 2 main

Verifying image file..........Done.

Images in IPE:

boot.bin

system.bin

This command will set the main startup software images. Continue? [Y/N]:y

Add images to target slot.

Decompressing file boot.bin to flash:/boot.bin....................Done.

Decompressing file system.bin to flash:/system.bin................Done.

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

ftware images at the next reboot on slot 2.

22. Enable the software auto-update function.

<Sysname> system-view

[Sysname] irf auto-update enable

[Sysname] quit

This function checks the software versions of member switches for inconsistency with the master switch. If a subordinate switch is using a different software version than the master, the function propagates the current software images of the master to the subordinate as main startup images. The function prevents software version inconsistency from causing the IRF setup failure.

23. Save the current configuration in any view to prevent data loss.

<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.

Slot 2:

Save next configuration file successfully.

24. Reboot the IRF fabric to complete the upgrade.

<Sysname> reboot

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

........DONE!

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

Now rebooting, please wait...

The system automatically loads the .bin boot and system images in the .ipe file and sets them as the startup software images.

25. Execute the display version command in any view to verify that the current main software images have been updated (details not shown).

NOTE:

The system automatically checks the compatibility of the Boot ROM image and the boot and system images during the reboot. If you are prompted that the Boot ROM image in the upgrade image file is different than the current Boot ROM image, upgrade both the basic and extended sections of the Boot ROM image for compatibility. If you choose to not upgrade the Boot ROM image, the system will ask for an upgrade at the next reboot performed by powering on the switch or rebooting from the CLI (promptly or as scheduled). If you fail to make any choice in the required time, the system upgrades the entire Boot ROM image.

Upgrading from the Boot menu

In this approach, you must access the Boot menu of each member switch to upgrade their software one by one. If you are upgrading software images for an IRF fabric, using the CLI is a better choice.

TIP:

Upgrading through the Ethernet port is faster than through the console port.

Prerequisites

Make sure the prerequisites are met before you start upgrading software from the Boot menu.

Setting up the upgrade environment

1. Use a console cable to connect the console terminal (for example, a PC) to the console port on the switch.

2. Connect the Ethernet port on the switch to the file server.

NOTE:

The file server and the configuration terminal can be co-located.

3. Run a terminal emulator program on the console terminal and set the following terminal settings:

¡ Bits per second—9,600

¡ Data bits—8

¡ Parity—None

¡ Stop bits—1

¡ Flow control—None

¡ Emulation—VT100

Preparing for the TFTP or FTP transfer

To use TFTP or FTP:

· Run a TFTP or FTP server program on the file server or the console terminal.

· Copy the upgrade file to the file server.

· Correctly set the working directory on the TFTP or FTP server.

· Make sure the file server and the switch can reach each other.

Verifying that sufficient storage space is available

IMPORTANT:

For the switch to start up correctly, do not delete the main startup software images when you free storage space before upgrading Boot ROM. On the Boot menu, the main startup software images are marked with an asterisk (*).

When you upgrade software, make sure each member switch has sufficient free storage space for the upgrade file, as shown in Table 6.

Table 6 Minimum free storage space requirements

Upgraded images	Minimum free storage space requirements
Comware images	Two times the size of the Comware upgrade package file.
Boot ROM	Same size as the Boot ROM upgrade image file.

If no sufficient space is available, delete unused files as described in “Managing files from the Boot menu.”

Scheduling the upgrade time

During the upgrade, the switch cannot provide any services. You must make sure the upgrade has a minimal impact on the network services.

Accessing the Boot menu

Starting......

Press Ctrl+D to access BASIC BOOT MENU

Press Ctrl+E to start flash test

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

* *

* H3C BOOTROM, Version 105 *

* *

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

Creation Date : Aug 9 2016, 11:29:29

CPU Clock Speed : 800MHz

Memory Size : 2048MB

Flash Size : 512MB

CPLD Version : 002

PCB Version : Ver.B

Mac Address : 703d155618b0

Press Ctrl+B to access EXTENDED BOOT MENU...1

Press one of the shortcut key combinations at prompt.

Table 7 Shortcut keys

Shortcut keys	Prompt message	Function	Remarks
Ctrl+B	Press Ctrl+B to enter Extended Boot menu...	Accesses the extended Boot menu.	Press the keys within 1 second (in fast startup mode) or 5 seconds (in full startup mode) after the message appears. You can upgrade and manage system software and Boot ROM from this menu.
Ctrl+D	Press Ctrl+D to access BASIC BOOT MENU	Accesses the basic Boot menu.	Press the keys within 1 seconds after the message appears. You can upgrade Boot ROM or access the extended Boot ROM segment from this menu.

Shortcut keys

Prompt message

Function

Remarks

Ctrl+B

Press Ctrl+B to enter Extended Boot menu...

Accesses the extended Boot menu.

Press the keys within 1 second (in fast startup mode) or 5 seconds (in full startup mode) after the message appears.

You can upgrade and manage system software and Boot ROM from this menu.

Ctrl+D

Press Ctrl+D to access BASIC BOOT MENU

Accesses the basic Boot menu.

Press the keys within 1 seconds after the message appears.

You can upgrade Boot ROM or access the extended Boot ROM segment from this menu.

Accessing the basic Boot menu

If the extended Boot ROM segment has corrupted, you can repair or upgrade it from the basic Boot menu.

Press Ctrl+D within 1 seconds after the "Press Ctrl+D to access BASIC BOOT MENU" prompt message appears. If you fail to do this within the time limit, the system starts to run the extended Boot ROM segment.

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

* *

* H3C BOOTROM, Version 105 *

* *

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

BASIC BOOT MENU

1. Update full BootRom

2. Update extended BootRom

3. Update basic BootRom

4. Boot extended BootRom

0. Reboot

Ctrl+U: Access BASIC ASSISTANT MENU

Enter your choice(0-4):

Table 8 Basic Boot ROM menu options

Option	Task
1. Update full BootRom	Update the entire Boot ROM, including the basic segment and the extended segment. To do so, you must use XMODEM and the console port. For more information, see Using XMODEM to upgrade Boot ROM through the console port.
2. Update extended BootRom	Update the extended Boot ROM segment. To do so, you must use XMODEM and the console port. For more information, see Using XMODEM to upgrade Boot ROM through the console port.
3. Update basic BootRom	Update the basic Boot ROM segment. To do so, you must use XMODEM and the console port. For more information, see Using XMODEM to upgrade Boot ROM through the console port.
4. Boot extended BootRom	Access the extended Boot ROM segment. For more information, see Accessing the extended Boot menu.
0. Reboot	Reboot the switch.
Ctrl+U: Access BASIC ASSISTANT MENU	Press Ctrl + U to access the BASIC ASSISTANT menu (see Table 9).

Table 9 BASIC ASSISTANT menu options

Option	Task
1. RAM Test	Perform a RAM self-test.
0. Return to boot menu	Return to the basic Boot menu.

Accessing the extended Boot menu

Press Ctrl+B within 1 second (in fast startup mode) or 5 seconds (in full startup mode) after the "Press Ctrl-B to enter Extended Boot menu..." prompt message appears. If you fail to do this, the system starts decompressing the system software.

Alternatively, you can enter 4 in the basic Boot menu to access the extended Boot menu.

The "Password recovery capability is enabled." or "Password recovery capability is disabled." message appears, followed by the extended Boot menu. Availability of some menu options depends on the state of password recovery capability (see Table 10). For more information about password recovery capability, see Fundamentals Configuration Guide in H3C S5560X-EI Switch Series Configuration Guides.

Password recovery capability is enabled.

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

0. Reboot

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format file system

Ctrl+P: Change authentication for console login

Ctrl+R: Download image to SDRAM and run

Enter your choice(0-8):

Table 10 Extended Boot ROM menu options

Option	Tasks
1. Download image to flash	Download a software image file to the flash.
2. Select image to boot	· Specify the main and backup software image file for the next startup. · Specify the main and backup configuration files for the next startup. This task can be performed only if password recovery capability is enabled.
3. Display all files in flash	Display files on the flash.
4. Delete file from flash	Delete files to free storage space.
5. Restore to factory default configuration	Delete the current next-startup configuration files and restore the factory-default configuration. This option is available only if password recovery capability is disabled.
6. Enter BootRom upgrade menu	Access the Boot ROM upgrade menu.
7. Skip current system configuration	Start the switch without loading any configuration file. This is a one-time operation and takes effect only for the first system boot or reboot after you choose this option. This option is available only if password recovery capability is enabled.
8. Set switch startup mode	Set the startup mode to fast startup mode or full startup mode.
0. Reboot	Reboot the switch.
Ctrl+F: Format file system	Format the current storage medium.
Ctrl+P: Change authentication for console login	Skip the authentication for console login. This is a one-time operation and takes effect only for the first system boot or reboot after you choose this option. This option is available only if password recovery capability is enabled.
Ctrl+R: Download image to SDRAM and run	Download a system software image and start the switch with the image. This option is available only if password recovery capability is enabled.
Ctrl+Z: Access EXTENDED ASSISTANT MENU	Access the EXTENDED ASSISTANT MENU. For options in the menu, see Table 11.

Table 11 EXTENDED ASSISTANT menu options

Option	Task
1. Display Memory	Display data in the memory.
2. Search Memory	Search the memory for a specific data segment.
0. Return to boot menu	Return to the extended Boot ROM menu.

Upgrading Comware images from the Boot menu

You can use the following methods to upgrade Comware images:

· Using TFTP to upgrade software images through the Ethernet port

· Using FTP to upgrade software images through the Ethernet port

· Using XMODEM to upgrade software through the console port

Using TFTP to upgrade software images through the Ethernet port

1. Enter 1 in the Boot menu to access the file transfer protocol submenu.

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):

2. Enter 1 to set the TFTP parameters.

Load File Name :update.ipe

Server IP Address :192.168.0.3

Local IP Address :192.168.0.2

Subnet Mask :255.255.255.0

Gateway IP Address :0.0.0.0

Table 12 TFTP parameter description

Item	Description
Load File Name	Name of the file to download (for example, update.ipe).
Server IP Address	IP address of the TFTP server (for example, 192.168.0.3).
Local IP Address	IP address of the switch (for example, 192.168.0.2).
Subnet Mask	Subnet mask of the switch (for example, 255.255.255.0).
Gateway IP Address	IP address of the gateway (in this example, no gateway is required because the server and the switch are on the same subnet).

NOTE:

· To use the default setting for a field, press Enter without entering any value.

· If the switch and the server are on different subnets, you must specify a gateway address for the switch.

3. Enter all required parameters, and enter Y to confirm the settings. The following prompt appears:

Are you sure to download file to flash? Yes or No (Y/N):Y

4. Enter Y to start downloading the image file. To return to the Boot menu without downloading the upgrade file, enter N.

Loading.........................................................................

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

................................................................Done!

5. Enter the M (main), B (backup), or N (none) attribute for the images. In this example, assign the main attribute to the images.

Please input the file attribute (Main/Backup/None) M

Image file boot.bin is self-decompressing...

Free space: 534980608 bytes

Writing flash...................................................................

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

...................................................................Done!

Image file system.bin is self-decompressing...

Free space: 525981696 bytes

Writing flash...................................................................

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

.......................................................................Done!

NOTE:

· The switch always attempts to boot with the main images first. If the attempt fails, for example, because the main images are not available, the switch tries to boot with the backup images. An image with the none attribute is only stored in flash memory for backup. To use it at reboot, you must change its attribute to main or backup.

· If an image with the same attribute as the image you are loading is already in the flash memory, the attribute of the old image changes to none after the new image becomes valid.

6. Enter 0 in the Boot menu to reboot the switch with the new software images.

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

0. Reboot

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format file system

Ctrl+P: Change authentication for console login

Ctrl+R: Download image to SDRAM and run

Enter your choice(0-8): 0

Using FTP to upgrade software images through the Ethernet port

1. Enter 1 in the Boot menu to access the file transfer protocol submenu.

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):

2. Enter 2 to set the FTP parameters.

Load File Name :update.ipe

Server IP Address :192.168.0.3

Local IP Address :192.168.0.2

Subnet Mask :255.255.255.0

Gateway IP Address :0.0.0.0

FTP User Name :switch

FTP User Password :***

Table 13 FTP parameter description

Item	Description
Load File Name	Name of the file to download (for example, update.ipe).
Server IP Address	IP address of the FTP server (for example, 192.168.0.3).
Local IP Address	IP address of the switch (for example, 192.168.0.2).
Subnet Mask	Subnet mask of the switch (for example, 255.255.255.0).
Gateway IP Address	IP address of the gateway (in this example, no gateway is required because the server and the switch are on the same subnet).
FTP User Name	Username for accessing the FTP server, which must be the same as configured on the FTP server.
FTP User Password	Password for accessing the FTP server, which must be the same as configured on the FTP server.

NOTE:

· To use the default setting for a field, press Enter without entering any value.

· If the switch and the server are on different subnets, you must specify a gateway address for the switch.

3. Enter all required parameters, and enter Y to confirm the settings. The following prompt appears:

Are you sure to download file to flash? Yes or No (Y/N):Y

4. Enter Y to start downloading the image file. To return to the Boot menu without downloading the upgrade file, enter N.

Loading.........................................................................

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

................................................................Done!

5. Enter the M (main), B (backup), or N (none) attribute for the images. In this example, assign the main attribute to the images.

Please input the file attribute (Main/Backup/None) M

Image file boot.bin is self-decompressing...

Free space: 534980608 bytes

Writing flash...................................................................

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

...................................................................Done!

Image file system.bin is self-decompressing...

Free space: 525981696 bytes

Writing flash...................................................................

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

.......................................................................Done!

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

0. Reboot

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format file system

Ctrl+P: Change authentication for console login

Ctrl+R: Download image to SDRAM and run

Enter your choice(0-8):0

NOTE:

· The switch always attempts to boot with the main images first. If the attempt fails, for example, because the main images not available, the switch tries to boot with the backup images. An image with the none attribute is only stored in flash memory for backup. To use it at reboot, you must change its attribute to main or backup.

· If an image with the same attribute as the image you are loading is already in the flash memory, the attribute of the old image changes to none after the new image becomes valid.

6. Enter 0 in the Boot menu to reboot the switch with the new software images.

Using XMODEM to upgrade software through the console port

XMODEM download through the console port is slower than TFTP or FTP download through the Ethernet port. To save time, use the Ethernet port as long as possible.

1. Enter 1 in the Boot menu to access the file transfer protocol submenu.

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):

2. Enter 3 to set the XMODEM download baud rate.

Please select your download baudrate:

1.* 9600

2. 19200

3. 38400

4. 57600

5. 115200

0. Return to boot menu

Enter your choice(0-5):5

3. Select an appropriate download rate, for example, enter 5 to select 115200 bps.

Download baudrate is 115200 bps

Please change the terminal's baudrate to 115200 bps and select XMODEM protocol

Press enter key when ready

4. Set the serial port on the terminal to use the same baud rate and protocol as the console port. If you select 9600 bps as the download rate for the console port, skip this task.

a. Select Call > Disconnect in the HyperTerminal window to disconnect the terminal from the switch.

Figure 2 Disconnecting the terminal from the switch

b. Select File > Properties, and in the Properties dialog box, click Configure.

Figure 3 Properties dialog box

c. Select 115200 from the Bits per second list and click OK.

Figure 4 Modifying the baud rate

d. Select Call > Call to reestablish the connection.

Figure 5 Reestablishing the connection

5. Press Enter. The following prompt appears:

Are you sure to download file to flash? Yes or No (Y/N):Y

6. Enter Y to start downloading the file. (To return to the Boot menu, enter N.)

Now please start transfer file with XMODEM protocol

If you want to exit, Press <Ctrl+X>

Loading ...CCCCCCCCCCCCCCCCCCCCCCCCC

7. Select Transfer > Send File in the HyperTerminal window.

Figure 6 Transfer menu

8. In the dialog box that appears, click Browse to select the source file, and select Xmodem from the Protocol list.

Figure 7 File transmission dialog box

9. Click Send. The following dialog box appears:

Figure 8 File transfer progress

10. Enter the M (main), B (backup), or N (none) attribute for the images. In this example, assign the main attribute to the images.

Please input the file attribute (Main/Backup/None) m

The boot.bin image is self-decompressing...

# At the Load File name prompt, enter a name for the boot image to be saved to flash memory.

Load File name : default_file boot-update.bin (At the prompt,

Free space: 470519808 bytes

Writing flash...................................................................

.............Done!

The system-update.bin image is self-decompressing...

# At the Load File name prompt, enter a name for the system image to be saved to flash memory.

Load File name : default_file system-update.bin

Free space: 461522944 bytes

Writing flash...................................................................

.............Done!

Your baudrate should be set to 9600 bps again!

Press enter key when ready

NOTE:

· The switch always attempts to boot with the main images first. If the attempt fails, for example, because the main images not available, the switch tries to boot with the backup images. An image with the none attribute is only stored in the flash memory for backup. To use it at reboot, you must change its attribute to main or backup.

· If an image with the same attribute as the image you are loading is already in flash memory, the attribute of the old image changes to none after the new image becomes valid.

11. If the baud rate of the HyperTerminal is not 9600 bps, restore it to 9600 bps as described in step a. If the baud rate is 9600 bps, skip this step.

NOTE:

The console port rate reverts to 9600 bps at a reboot. If you have changed the baud rate, you must perform this step so you can access the switch through the console port after a reboot.

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

0. Reboot

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format file system

Ctrl+P: Change authentication for console login

Ctrl+R: Download image to SDRAM and run

Enter your choice(0-8): 0

12. Enter 0 in the Boot menu to reboot the system with the new software images.

Upgrading Boot ROM from the Boot menu

You can use the following methods to upgrade the Boot ROM image:

· Using TFTP to upgrade Boot ROM through the Ethernet port

· Using FTP to upgrade Boot ROM through the Ethernet port

· Using XMODEM to upgrade Boot ROM through the console port

Using TFTP to upgrade Boot ROM through the Ethernet port

1. Enter 6 in the Boot menu to access the Boot ROM update menu.

1. Update full BootRom

2. Update extended BootRom

3. Update basic BootRom

0. Return to boot menu

Enter your choice(0-3):

2. Enter 1 in the Boot ROM update menu to upgrade the full Boot ROM.

The file transfer protocol submenu appears:

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):

3. Enter 1 to set the TFTP parameters.

Load File Name :update.btm

Server IP Address :192.168.0.3

Local IP Address :192.168.0.2

Subnet Mask :255.255.255.0

Gateway IP Address :0.0.0.0

Table 14 TFTP parameter description

Item	Description
Load File Name	Name of the file to download (for example, update.btm).
Server IP Address	IP address of the TFTP server (for example, 192.168.0.3).
Local IP Address	IP address of the switch (for example, 192.168.0.2).
Subnet Mask	Subnet mask of the switch (for example, 255.255.255.0).
Gateway IP Address	IP address of the gateway (in this example, no gateway is required because the server and the switch are on the same subnet).

NOTE:

· To use the default setting for a field, press Enter without entering any value.

· If the switch and the server are on different subnets, you must specify a gateway address for the switch.

4. Enter all required parameters and press Enter to start downloading the file.

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

5. Enter Y at the prompt to upgrade the basic Boot ROM section.

Will you Update Basic BootRom? (Y/N):Y

Updating Basic BootRom...........Done.

6. Enter Y at the prompt to upgrade the extended Boot ROM section.

Updating extended BootRom? (Y/N):Y

Updating extended BootRom.........Done.

7. Enter 0 in the Boot ROM update menu to return to the Boot menu.

1. Update full BootRom

2. Update extended BootRom

3. Update basic BootRom

0. Return to boot menu

Enter your choice(0-3):

8. Enter 0 in the Boot menu to reboot the switch with the new Boot ROM image.

Using FTP to upgrade Boot ROM through the Ethernet port

1. Enter 6 in the Boot menu to access the Boot ROM update menu.

1. Update full BootRom

2. Update extended BootRom

3. Update basic BootRom

0. Return to boot menu

Enter your choice(0-3):

2. Enter 1 in the Boot ROM update menu to upgrade the full Boot ROM.

The file transfer protocol submenu appears:

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):

3. Enter 2 to set the FTP parameters.

Load File Name :update.btm

Server IP Address :192.168.0.3

Local IP Address :192.168.0.2

Subnet Mask :255.255.255.0

Gateway IP Address :0.0.0.0

FTP User Name :switch

FTP User Password :123

Table 15 FTP parameter description

Item	Description
Load File Name	Name of the file to download (for example, update.btm).
Server IP Address	IP address of the FTP server (for example, 192.168.0.3).
Local IP Address	IP address of the switch (for example, 192.168.0.2).
Subnet Mask	Subnet mask of the switch (for example, 255.255.255.0).
Gateway IP Address	IP address of the gateway (in this example, no gateway is required because the server and the switch are on the same subnet).
FTP User Name	Username for accessing the FTP server, which must be the same as configured on the FTP server.
FTP User Password	Password for accessing the FTP server, which must be the same as configured on the FTP server.

NOTE:

· To use the default setting for a field, press Enter without entering any value.

· If the switch and the server are on different subnets, you must specify a gateway address for the switch.

4. Enter all required parameters and press Enter to start downloading the file.

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

5. Enter Y at the prompt to upgrade the basic Boot ROM section.

Will you Update Basic BootRom? (Y/N):Y

Updating Basic BootRom...........Done.

6. Enter Y at the prompt to upgrade the extended Boot ROM section.

Updating extended BootRom? (Y/N):Y

Updating extended BootRom.........Done.

7. Enter 0 in the Boot ROM update menu to return to the Boot menu.

1. Update full BootRom

2. Update extended BootRom

3. Update basic BootRom

0. Return to boot menu

Enter your choice(0-3):

8. Enter 0 in the Boot menu to reboot the switch with the new Boot ROM image.

Using XMODEM to upgrade Boot ROM through the console port

XMODEM download through the console port is slower than TFTP or FTP download through the Ethernet port. To save time, use the Ethernet port as long as possible.

1. Enter 6 in the Boot menu to access the Boot ROM update menu.

1. Update full BootRom

2. Update extended BootRom

3. Update basic BootRom

0. Return to boot menu

Enter your choice(0-3):

2. Enter 1 in the Boot ROM update menu to upgrade the full Boot ROM.

The file transfer protocol submenu appears:

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):

3. Enter 3 to set the XMODEM download baud rate.

Please select your download baudrate:

1.* 9600

2. 19200

3. 38400

4. 57600

5. 115200

0. Return to boot menu

Enter your choice(0-5):5

4. Select an appropriate download rate, for example, enter 5 to select 115200 bps.

Download baudrate is 115200 bps

Please change the terminal's baudrate to 115200 bps and select XMODEM protocol

Press enter key when ready

5. Set the serial port on the terminal to use the same baud rate and protocol as the console port. If you select 9600 bps as the download rate for the console port, skip this task.

a. Select Call > Disconnect in the HyperTerminal window to disconnect the terminal from the switch.

Figure 9 Disconnecting the terminal from the switch

b. Select File > Properties, and in the Properties dialog box, click Configure.

Figure 10 Properties dialog box

c. Select 115200 from the Bits per second list and click OK.

Figure 11 Modifying the baud rate

d. Select Call > Call to reestablish the connection.

Figure 12 Reestablishing the connection

6. Press Enter to start downloading the file.

Now please start transfer file with XMODEM protocol

If you want to exit, Press <Ctrl+X>

Loading ...CCCCCCCCCCCCCCCCCCCCCCCCC

7. Select Transfer > Send File in the HyperTerminal window.

Figure 13 Transfer menu

8. In the dialog box that appears, click Browse to select the source file, and select Xmodem from the Protocol list.

Figure 14 File transmission dialog box

9. Click Send. The following dialog box appears:

Figure 15 File transfer progress

10. Enter Y at the prompt to upgrade the basic Boot ROM section.

Loading ...CCCCCCCCCCCCCC ...Done!

Will you Update Basic BootRom? (Y/N):Y

Updating Basic BootRom...........Done.

11. Enter Y at the prompt to upgrade the extended Boot ROM section.

Updating extended BootRom? (Y/N):Y

Updating extended BootRom.........Done.

12. If the baud rate of the HyperTerminal is not 9600 bps, restore it to 9600 bps at the prompt, as described in step a. If the baud rate is 9600 bps, skip this step.

Please change the terminal's baudrate to 9600 bps, press ENTER when ready.

NOTE:

The console port rate reverts to 9600 bps at a reboot. If you have changed the baud rate, you must perform this step so you can access the switch through the console port after a reboot.

13. Press Enter to access the Boot ROM update menu.

14. Enter 0 in the Boot ROM update menu to return to the Boot menu.

1. Update full BootRom

2. Update extended BootRom

3. Update basic BootRom

0. Return to boot menu

Enter your choice(0-3):

15. Enter 0 in the Boot menu to reboot the switch with the new Boot ROM image.

Managing files from the Boot menu

From the Boot menu, you can display files in flash memory to check for obsolete files, incorrect files, or space insufficiency, delete files to release storage space, or change the attributes of software images.

Displaying all files

Enter 3 in the Boot menu to display all files in flash memory and identify the free space size.

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

0. Reboot

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format file system

Ctrl+P: Change authentication for console login

Ctrl+R: Download image to SDRAM and run

Enter your choice(0-8): 3

The following is a sample output:

Display all file(s) in flash:

File Number File Size(bytes) File Name

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

1 8177 flash:/testbackup.cfg

2(*) 53555200 flash:/system.bin

3(*) 9959424 flash:/boot.bin

4 3678 flash:/startup.cfg_backup

5 30033 flash:/default.mdb

6 42424 flash:/startup.mdb

7 18 flash:/.pathfile

8 232311 flash:/logfile/logfile.log

9 5981 flash:/startup.cfg_back

10(*) 6098 flash:/startup.cfg

11 20 flash:/.snmpboots

Free space: 464298848 bytes

The current image is boot.bin

(*)-with main attribute

(b)-with backup attribute

(*b)-with both main and backup attribute

Deleting files

If storage space is insufficient, delete obsolete files to free up storage space.

To delete files:

1. Enter 4 in the Boot menu:

Deleting the file in flash:

File Number File Size(bytes) File Name

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

1 8177 flash:/testbackup.cfg

2(*) 53555200 flash:/system.bin

3(*) 9959424 flash:/boot.bin

4 3678 flash:/startup.cfg_backup

5 30033 flash:/default.mdb

6 42424 flash:/startup.mdb

7 18 flash:/.pathfile

8 232311 flash:/logfile/logfile.log

9 5981 flash:/startup.cfg_back

10(*) 6098 flash:/startup.cfg

11 20 flash:/.snmpboots

Free space: 464298848 bytes

The current image is boot.bin

(*)-with main attribute

(b)-with backup attribute

(*b)-with both main and backup attribute

2. Enter the number of the file to delete. For example, enter 1 to select the file testbackup.cfg.

Please input the file number to change: 1

3. Enter Y at the confirmation prompt.

The file you selected is testbackup.cfg,Delete it? (Y/N):Y

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

Changing the attribute of software images

Software image attributes include main (M), backup (B), and none (N). System software and boot software can each have multiple none-attribute images but only one main image and one backup image on the switch. You can assign both the M and B attributes to one image. If the M or B attribute you are assigning has been assigned to another image, the assignment removes the attribute from that image. If the removed attribute is the sole attribute of the image, its attribute changes to N.

For example, the system image system.bin has the M attribute and the system image system-update.bin has the B attribute. After you assign the M attribute to system-update.bin, the attribute of system-update.bin changes to M+B and the attribute of system.bin changes to N.

To change the attribute of a system or boot image:

1. Enter 2 in the Boot 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

0. Reboot

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format file system

Ctrl+P: Change authentication for console login

Ctrl+R: Download image to SDRAM and run

Enter your choice(0-8): 2

2. 1 or 2 at the prompt to set the attribute of a software image. (The following output is based on the option 2. To set the attribute of a configuration file, enter 3.)

1. Set image file

2. Set bin file

3. Set configuration file

0. Return to boot menu

Enter your choice(0-3): 2

File Number File Size(bytes) File Name

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

1(*) 53555200 flash:/system.bin

2(*) 9959424 flash:/boot.bin

3 13105152 flash:/boot-update.bin

4 91273216 flash:/system-update.bin

Free space: 417177920 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.

3. Enter the number of the file you are working with. For example, enter 3 to select the boot image boot-update.bin. and enter 4 to select the system image system-update.bin.

Enter file No.(Allows multiple selection):3

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

4. Enter 0 to finish the selection.

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

You have selected:

flash:/boot-update.bin

flash:/system-update.bin

5. Enter M or B to change its attribute to main or backup. If you change its attribute to M, the attribute of boot.bin changes to none.

Please input the file attribute (Main/Backup) M

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

Next time, boot-update.bin will become default boot file!

Next time, system-update.bin will become default boot file!

Set the file attribute success!

Handling software upgrade failures

If a software upgrade fails, the system runs the old software version.

To handle a software upgrade failure:

1. Verify that the software release is compatible with the switch model and the correct file is used.

2. Verify that the software release and the Boot ROM release are compatible. For software and Boot ROM compatibility, see the hardware and software compatibility matrix in the correct release notes.

3. Check the physical ports for a loose or incorrect connection.

4. 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.

5. 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.

6. Check the FTP or TFTP server for any incorrect setting.

7. Check that the storage device has sufficient space for the upgrade fil e.