Contents

Introduction· 1

Version information· 1

Version number 1

Version history· 1

Hardware and software compatibility matrix· 6

ISSU upgrade type matrix· 8

Upgrade advice· 8

Upgrade restrictions and guidelines· 8

Hardware feature updates· 8

R6652P07· 8

R6652P06~R1110· 8

E1109· 8

E1108· 8

Software feature and command updates· 9

MIB updates· 9

Operation changes· 9

Operation changes in R6652P07~R6628P40· 9

Operation changes in R6628P35· 9

Operation changes in R6628P30· 9

Operation changes in R6615P08· 10

Operation changes in R6615P07· 10

Operation changes in R6615P05· 10

Operation changes in R6615P03· 10

Operation changes in R6515P06· 10

Operation changes in R6510P02· 10

Operation changes in R6510· 10

Operation changes in F6510· 10

Operation changes in F6509L01· 10

Operation changes in F6508· 10

Operation changes in R6308· 11

Operation changes in F6306· 11

Operation changes in F6305· 11

Operation changes in F1502· 11

Operation changes in R1113· 11

Operation changes in R1112· 11

Operation changes in R1111· 11

Operation changes in R1110P06· 11

Operation changes in R1110P05· 11

Operation changes in R1110· 11

Operation changes in E1109· 11

Operation changes in E1108· 12

Restrictions and cautions· 12

Restrictions· 12

Hardware· 12

Software· 12

Configuring Networking· 12

Cautions· 13

Hardware· 13

Software· 13

Configuring Networking· 13

Licensing· 13

About licensing· 13

Registering and installing licenses· 13

Obtaining license server software and documentation· 13

Obtaining license server software and documentation· 14

Open problems and workarounds· 14

List of resolved problems· 14

Resolved problems in R6652P07· 14

Resolved problems in R6652P06· 16

Resolved problems in R6652P05· 16

Resolved problems in R6652P02· 19

Resolved problems in R6628P40· 21

Resolved problems in R6628P35· 26

Resolved problems in R6628P30· 29

Resolved problems in R6615P08· 31

Resolved problems in R6615P07· 34

Resolved problems in R6615P05· 36

Resolved problems in R6615P03· 37

Resolved problems in R6515P06· 44

Resolved problems in R6510P02· 50

Resolved problems in R6510· 51

Resolved problems in F6510· 51

Resolved problems in F6509L01· 54

Resolved problems in F6508· 55

Resolved problems in R6308· 61

Resolved problems in F6306· 63

Resolved problems in F6305· 65

Resolved problems in F1502· 67

Resolved problems in R1113· 68

Resolved problems in R1112· 69

Resolved problems in R1111· 71

Resolved problems in R1110P06· 73

Resolved problems in R1110P05· 74

Resolved problems in R1110· 74

Resolved problems in E1109· 75

Resolved problems in E1108· 77

Troubleshooting resources· 77

Related documentation· 77

Technical support 77

Appendix A Feature list 78

Hardware features· 78

Software features· 78

Appendix B Fixed security vulnerabilities· 82

Fixed security vulnerabilities in R6652P05· 82

Fixed security vulnerabilities in R6652P02· 84

Fixed security vulnerabilities in R6628P35· 88

Fixed security vulnerabilities in R6628P30· 88

Fixed security vulnerabilities in R6615P08· 89

Appendix C Upgrading software· 90

System software file types· 90

System startup process· 90

Upgrade methods· 91

Upgrading from the CLI 92

Preparing for the upgrade· 92

Downloading software images to the master switch· 93

Upgrading from the Boot menu· 97

Prerequisites· 97

Accessing the Boot menu· 98

Accessing the basic Boot menu· 99

Accessing the extended Boot menu· 100

Upgrading Comware images from the Boot menu· 101

Upgrading Boot ROM from the Boot menu· 109

Managing files from the Boot menu· 116

List of tables

Table 1 Version history· 1

Table 2 Hardware and software compatibility matrix· 6

Table 3 ISSU version compatibility matrix· 8

Table 4 MIB updates· 9

Table 5 Software features· 78

Table 6 Minimum free storage space requirements· 97

Table 7 Shortcut keys· 98

Table 8 Basic Boot ROM menu options· 99

Table 9 BASIC ASSISTANT menu options· 100

Table 10 Extended Boot ROM menu options· 100

Table 11 EXTENDED ASSISTANT menu options· 101

Table 12 TFTP parameter description· 102

Table 13 FTP parameter description· 104

Table 14 TFTP parameter description· 110

Table 15 FTP parameter description· 111

Introduction

This document describes the features, restrictions and guidelines, open problems, and workarounds for version S6520X-CMW710-R6652P07. 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 S6520X-CMW710-R6652P07 Release Notes (Software Feature Changes) and the documents listed in "Troubleshooting resources ."

Version information

Version number

H3C Comware Software, Version 7.1.070, Release 6652P07

Version history

Table 1 Version history

Hardware and software compatibility matrix

Table 2 Hardware and software compatibility matrix

H3C Comware Software, Version 7.1.070, Release 6615P08     ------- Note①          

Copyright © 2004-2020 New H3C Technologies Co., Ltd. All rights reserved.    

H3C S6520X-30HC-EI uptime is 0 weeks, 0 days, 0 hours, 5 minutes               

Last reboot reason : User reboot                                               

Boot image: flash:/s6520x-cmw710-boot-r6615p08.bin                             

Boot image version: 7.1.070, Release 6615P08                                   

  Compiled Jun 03 2020 11:00:00                                                

System image: flash:/s6520x-cmw710-system-r6615p08.bin                         

System image version: 7.1.070, Release 6615P08                                 

  Compiled Jun 03 2020 11:00:00                                                

Feature image(s) list:                                                          

  flash:/s6520x-cmw710-freeradius-r6615p08.bin, version: 7.1.070, Release 6615P08

Compiled Jun 03 2020 11:00:00                                              

  flash:/s6520x-cmw710-escan-r6615p08.bin, version: 7.1.070, Release 6615P08   

Compiled Jun 03 2020 11:00:00                                              

Slot 1:                                                                        

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

S6520X-30HC-EI with 2 Processors                                               

BOARD TYPE:         S6520X-30HC-EI                                             

DRAM:               2048M bytes                                                

FLASH:              1024M bytes                                                

PCB 1 Version:      VER.A                                                       

Bootrom Version:    117            ------Note②                                     

CPLD 1 Version:     001                                                        

CPLD 2 Version:     001                                                         

Release Version:    H3C S6520X-30HC-EI-6615P08                                    

Patch Version  :    None                                                       

Reboot Cause  :     UserReboot                                                  

[SubSlot 0] 24SFP Plus + 2QSFP28

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

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.

Hardware feature updates

R6652P07

Added support for the QSFP-40G-LX4-WDM1300 transceiver module.

R6652P06~R1110

None.

E1109

S6520X-30HC-EI, S6520X-30HC-HI, S6520X-54HC-EI, S6520X-54HC-HI, LSWM2ZSP8P, and LSWM2ZQP2P are supported.

E1108

First release.

Software feature and command updates

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

MIB updates

Table 4 MIB updates

Operation changes

Operation changes in R6652P07~R6628P40

None.

Operation changes in R6628P35

Changed the default of the port-security m-lag load-sharing-mode command from distributed local to centralized.

The default value of the Restore delay field in the display m-lag system command output changes from 30s to 300s.

Operation changes in R6628P30

The default setting of the stp port-log command is changed as follows:

¡   If the device starts with the initial configuration, the default setting of this command applies. Output of port state transition information is disabled.

¡   If the device starts with the factory defaults, the factory default setting of this command applies. Output of port state transition information is enabled.

Operation changes in R6615P08

The maximum MTU was increased from 1560 bytes to 9000 bytes for Layer 3 aggregate interfaces and their subinterfaces.

Operation changes in R6615P07

None.

Operation changes in R6615P05

None.

Operation changes in R6615P03

None.

Operation changes in R6515P06

None.

Operation changes in R6510P02

As from this version, the device will output the following information when the MAC learning limit is configured on an interface and the number of MAC address entries learned on the interface has reached the limit:

%Mar  2 21:36:03:196 2013 PE2 MAC/5/MAC_TABLE_FULL_PORT: The number of MAC address entries exceeded the maximum number 2 for interface GigabitEthernet1/0/4. 

Operation changes in R6510

None.

Operation changes in F6510

None.

Operation changes in F6509L01

None.

Operation changes in F6508

None.

Operation changes in R6308

None.

Operation changes in F6306

None.

Operation changes in F6305

None.

Operation changes in F1502

None.

Operation changes in R1113

None.

Operation changes in R1112

None.

Operation changes in R1111

None.

Operation changes in R1110P06

None.

Operation changes in R1110P05

None.

Operation changes in R1110

None.

Operation changes in E1109

None.

Operation changes in E1108

First release.

Restrictions and cautions

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.

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

Restrictions

Hardware

None

Software

VLAN configuration priority restriction

If both MAC-based VLAN and IP subnet-based VLAN are configured on an interface, MAC-based VLAN configuration takes effect.

Restrictions for password settings

The new version enforces a stricter password control policy, which will examine whether the passwords meet the following requirements:

¡  Password composition restriction.

¡  Minimum password length requirement.

¡  The password cannot contain the username or the reverse letters of the username.

When you enter your password to log in, you are prompted to change the password that does not meet the above requirements.

Configuring Networking

Restrictions for aggregate CAR

A QoS policy that contains an aggregate CAR action cannot be applied to outgoing packets on an interface.

Cautions

Hardware

The data buffer of the interface configuration priority Cautions

·          By default, the Burst feature is disabled. An interface can use up to 33% of the shared buffer, and each queue on the interface can use up to 70% of the data buffer of the interface.

·         When the Burst feature is enabled, an interface can use up to 90% of the shared buffer, and each queue on the interface can use up to 70% of the data buffer of the interface.

Software

Rate of ARP packets delivered to the CPU

The maximum rate of ARP packets delivered to the CPU was changed from 500 pps to 800 pps to improve the ARP processing performance.

Configuring Networking

Compatible Aps reference to H3C UWW-CMW710-R5456P05 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.

Obtaining license server software and documentation

To perform remote licensing, first download and install the H3C license server software.

·         To obtain the H3C license server software package, click

H3C license server software package

·         To obtain H3C license server documentation, click

H3C license server documentation

Obtaining license server software and documentation

To perform remote licensing, first download and install the H3C license server software.

·         To obtain the H3C license server software package, click

H3C license server software package

·         To obtain H3C license server documentation, click

H3C license server documentation

Open problems and workarounds

202311210102

·         Symptom: On an M-LAG network, STP convergence might be slow.

·         Condition: This symptom occurs if you use the m-lag standalone enable command to enable the M-LAG standalone mode and then power-cycle the primary M-LAG member device.

·         Workaround: Set the delay that the device must wait before changing to M-LAG standalone mode.

List of resolved problems

Resolved problems in R6652P07

202402051337

·         Symptom: IRF fabric setup fails.

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

¡  Use 100G interfaces on the related devices as IRF physical ports.

¡  Configure the devices as an IRF fabric through NETCONF on the controller side.

202403180668

·         Symptom: An M-LAG system records STP dispute logs, leading to traffic interruption. The symptom occurs because of a logic mistake in processing a specific situation.

·         Condition: This symptom occurs if the reliability settings are different between the old and the new software versions when the software is upgraded, especially in STP protocol processing.

202406150478

·         Symptom: MAC address authentication fails.

·         Condition: This symptom occurs when users perform MAC authentication after both EAD assistant and MAC authentication are configured.

202406030333

·         Symptom: After a period of time, the server automatically switches to active state.

·         Condition: This symptom might occur after you manually set the server to block state when the server is unreachable, and authentication or accounting packets have been sent and not yet timed out.

202406150501

·         Symptom: H.323 packets are looped between devices after H.323-based SQA is enabled.

·         Condition: This symptom occurs if you enable H.323-based SQA on two or more devices in the same VLAN.

202406071539

·         Symptom: After service packets are decapsulated in a tunnel, the service packets are mistakenly matched to a private network, where the service packets are incorrectly processed. As a result, the VXLAN tunnel traffic is interrupted and the function is abnormal.

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

¡  Port A matches the ePort index assigned by VXLAN tunnel decapsulation (the lower 12 bits of the ePort index matches the physical port number of port A). For example, the ePort index is 12292, which is 0x3004 in hexadecimal.

¡  The lower 12 bits are 004 and correspond to physical port number 4 of port A. Port A is bound to a private network, and the network where the actual VXLAN service resides is different from this private network.

202406110434

·         Symptom: The device failed to obtain the fan speed information.

·         Condition: This symptom might occur if you obtain fan status information via IMC

202404290270

·         Symptom: In a BIDIR-PIM network, the RP fails to forward traffic.

·         Condition: This symptom occurs if a loopback interface acts as the RP and the output interface is a Layer 3 interface.

202405310239

·         Symptom: Only the ping operation initiated by the peer end can succeed. The ping operation initiated by the local end fails.

·         Condition: This symptom occurs if an interface with physical index 0 on the device is used to form the IRF fabric, a manual VXLAN tunnel is established with the peer end, and no ARP entries exist for IP address on the same subnet.

202405131121

·         Symptom: No information might be displayed in the output from the display poe command. In addition, when you execute the poe enable command, the system prompts that the execution failed.

·         Condition: This symptom might occur if the device is operating.

202406052409

·         Symptom: The count for the IPv4 route resources is incorrect.

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

¡  In an MPLS L3VPN, the local device establishes multiple peers with multiple devices at the remote end.

¡  When the local device's eport hardware resources are insufficient, the peer devices perform route migration for the same prefix.

Resolved problems in R6652P06

202404171222

·         Symptom: After MAC address learning is disabled on a port, the port still learns MAC addresses.

·         Condition: This symptom occurs if you disable MAC address learning after configuring MAC authentication.

202404101064

·         Symptom: When a BFD session for BGP is created, the ping delay is long or packet loss occurs.

·         Condition: This symptom occurs if a large number of BFD sessions for BGP have been created and BFD is enabled and disabled repeatedly.

202403270216

·         Symptom: A tunnel cannot forward traffic properly.

·         Condition: This symptom occurs if you configure a PBR policy, configure the outgoing interface as a tunnel, delete that tunnel, and then re-create that tunnel.

202404101092

·         Symptom: A large number of ICMP destination unreachable messages are sent to the CPU.

·         Condition: This symptom occurs if a Layer 3 aggregate interface is associated with a VPN instance and the index of the Layer 3 aggregate interface the same as the index of the Layer 3 Ethernet interface that receive ICMP destination unreachable messages.

202404160893

·         Symptom: A packet filter does not take effect in the inbound direction of a VLAN interface.

·         Condition: This symptom occurs if a PBR policy is applied to the VLAN interface and the ACL used in the PBR policy contains a rule with the established keyword specified.

Resolved problems in R6652P05

202403040340

·         Symptom: Packet loss continues for more than 60 seconds after a master/subordinate switchover is performed on an IRF fabric.

·         Condition: This symptom occurs if multicast traffic is transmitted over the RPT path and the output interface of the optimal route is on the master device.

202401291764

·         Symptom: An authenticated user is online simultaneously on both M-LAG member devices.

·         Condition: This symptom occurs if the following operations are performed on an M-LAG network:
A user first comes online through authentication on a single-homing interface of  M-LAG 1.
The user comes online through authentication on a single-homing interface of M-LAG 2 and triggers a migration.

202403060066

·         Symptom: BFD flapping occurs.

·         Condition: This symptom occurs if the deny-mode ACL rule used to match IPv4 packets configured on VLAN-interface 200 matches BFD packets by mistake, resulting in BFD packet loss and BFD flapping.

202402291384

·         Symptom: Tunnel traffic received on a non-aggregate interface matches an ACL configured for an aggregate interface by mistake.

·         Condition: This symptom occurs if the ACL configured on an aggregate interface incorrectly matches the specific traffic characteristics. When an extension port is allocated to tunnel traffic, the lowest 8 bits coincide with the SRC TRUNK (source port aggregation) match criterion defined in the aggregate interface ACL.

202402040334

·         Symptom: The MAC address is not deleted after a static AC on an interface is deleted.

·         Condition: This symptom occurs if 802.1x authentication is performed before the static AC is deleted.

202401090475

·         Symptom: The keepalive link flaps due to timeout.

·         Condition: This symptom occurs if a large number of ARP packets are sent to the CPU.

202401230378

·         Symptom: On an IRF fabric, the number of available ARP resources is incorrect.

·         Condition: This symptom occurs if the ARP packets move between the member leaf devices repeatedly.

202312041570

·         Symptom: The packets are dropped by the device cannot be forwarded normally.

·         Condition: This symptom occurs if the device has received packets with the last three bytes of the source MAC addresses set to 0.

·         Impact: The packets with the last three bytes of the source MAC addresses set to 0.

·         Workaround: None.

·         Severity: Medium

202312040067

·         Symptom: The ping operation fails.

·         Condition: This symptom occurs if a Layer 3 subinterface is configured as the tunnel outgoing interface and connected to a spine device and the ping command is executed.

202307130972

·         Symptom: After the m-lag extra-vlan command is executed, the M-LAG member devices cannot synchronize ARP or ND entries for the extra VLANs through the peer-link interface.

·         Condition: This symptom might occur if some M-LAG interfaces are not assigned to the extra VLANs, and the device is rebooted or the peer-link interface flaps.

202311150214

·         Symptom: On an M-LAG network, the peer link cannot transmit traffic.

·         Condition: This symptom occurs if the following operations are performed on an M-LAG network:

a.    Enable automatic setup of a VXLAN tunnel between M-LAG member devices.

b.    Shut down the M-LAG interface on one member device.

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.

202310090404

·         Symptom: An OSPF route anomaly occurs.

·         Condition: This symptom occurs if you shut down the BFD MAD detection interfaces on IRF devices by shutting down the downlink interface and then the uplink interface.

202307051264

·         Symptom: The device does not display logs for adding MAC address entries and displays logs only for deleting MAC address entries.

·         Condition: This symptom occurs if you configure port security settings on a port and connect the port to the peer end.

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.

202310240098

·         Symptom: After patch installation and device restart, slow device startup and the EVENT_TIMEOUT log might occur.

·         Condition: This symptom might occur if DRNI and monitor link are configured together and the device reboots after installation of a patch with the drnid process included.

202308091835

·         Symptom: The xmlcfgd process has exceptions in the next installation of a patch after the patch is loaded, because a subprocess has residues.

·         Condition: This symptom might occur if a patch is loaded on the controller connected to the device.

202309260374

·         Symptom: The ovsdb-server process occasionally terminates abnormally on the device.

·         Condition: This symptom might occur when the controller deploys the configuration to the device.

202308291580

·         Symptom: Packet loss occurs during the bulk addition or deletion of M-LAG interfaces on an EVPN M-LAG system.

·         Condition: This symptom might occur if singlehoming AC-attached interfaces exist on the EVPN M-LAG system, and bulk addition or deletion of M-LAG interfaces is performed during traffic transmission between remote leaf devices and local ACs.

202309182105

·         Symptom: The switch sends 802.1X authentication packets and accounting packets to different RADIUS servers because the state of the port security process is incorrect.

·         Condition: This symptom occurs if a master/subordinate switchover is performed on an IRF fabric.

Resolved problems in R6652P02

202309090594

·         Symptom: Residual dynamic ACL entries exist on subordinate devices in an IRF fabric.

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

¡  The IRF fabric has aggregate interfaces that contain member ports from multiple member devices.

¡  MAC authentication users are assigned authorization VSIs after they pass MAC authentication and come online.

¡  The MAC authentication users are frequently moving among the aggregate interfaces in different VLANs.

202309220595

·         Symptom: If you configure the bfd min-transmit-interval 1000 command for hardware BFD, but the actual packet sending rate on the device interface is inconsistent with the configuration, BFD session establishment fails.

·         Condition: This symptom occurs if you configure the bfd min-transmit-interval 1000 command for hardware BFD.

202309121745

·         Symptom: On an IRF fabric, multicast forwarding is abnormal after a master/subordinate switchover.

·         This symptom occurs after a master/subordinate switchover if you have configured Layer 3 interfaces before setting up the IRF fabric.

202308310672

·         Symptom: The device reboots abnormally.

·         Condition: This symptom might occur if a single port on an IRF member device is added to an aggregation group when a static AC has been specified for the single port.

202308292319

·         Symptom: Authentication MAC information and some ACL information remain.

·         Condition: This symptom might occur if VXLAN static ACs are configured, normal ports perform URL authentication on users, and the users are logged off.

202308120522

·         Symptom: The device reboots abnormally.

·         Condition: This symptom might occur if a user that comes online via a cross-card aggregated interface on an IRF device repeatedly manually create and delete ACs.

202308241645

·         Symptom: Dynamic MAC addresses learned on a Layer 2 aggregate interface do not age out.

·         Condition: This symptom might occur if the member ID of the device is not 1.

202308111721

·         Symptom: A core dump file is generated after the portsecd process repeatedly restarts.

·         Condition: This symptom occurs if the portsecd process repeatedly restarts when the following conditions exist:

¡  The device is an IRF fabric.

¡  Temporary MAC authentication users come online on a port operating in mac-else-userlogin-secure-ext port security mode.

202309040482

·         Symptom: Traffic is forwarded out from an incorrect egress port.

·         Condition: This symptom might occur if the port is first added to the VLAN of a VLAN interface with a MAC address and then added to an aggregation group in this VLAN.

202308161652

·         Symptom: Failed to synchronize the configuration from the controller to the switch during software upgrade, and an unsupported command (dci switch-delay) exists on the switch after the synchronization.

·         Condition: This symptom occurs if the switch does not support Layer 3 multicast in DCI scenarios.

202308250625

·         Symptom: After a default route is redistributed into an OSPF area, other devices do not learn the type-5 default route.

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

¡  The routing loop detection feature is disabled for the private OSPF process by executing the vpn-instance-capability simple command.

¡  The OSPF process is not enabled to redistribute routes from other routing protocols. (The import-route command is not executed.)

¡  No NSSA area is configured. (The nssa command is not executed.)

¡  The whole device is restarted and starts up with a binary configuration file.

202308160716

·         Symptom: A user obtains an authorization ACL after it passes authentication and comes online. However, the port ranges in the ACL rules cannot take effect.

·         Condition: This symptom occurs if the ACL number is not 2304 and the device is operating in switch mode.

202308111636

·         Symptom: Service failure causes packet forwarding failure.

·         Condition: This symptom might occur when the device receives a large number of HTTP or HTTPS attack defense packets destined for the device.

202305080149

·         Symptom: On an EVPN M-LAG network, packet loss occurs when a device single-homed to a leaf device pings other devices.

·         Condition: This symptom occurs if a device single-homed to a leaf device broadcasts the received RARP packets on an EVPN+M-LAG network. As a result, ARP entries and ARP suppression entries become incorrect on other devices.

202306240066

·         Symptom: ARP entries are learned on the IPP incorrectly. As a result, remote IP addresses on the same subnet might fail to be accessed.

·         Condition: This symptom occurs if proxy ARP is configured for the DRNI dual-active VLAN gateways or VRRP and periodic automatic ARP scanning is enabled by using the arp scan auto enable command.

202306290442

·         Symptom: CAR rate limit failed to be deployed.

·         Condition: This symptom might occur if you execute the authorization-attribute command in ISP domain view with the car parameters specified, but the CAR rate limit settings do not meet the granularity range requirements.

Resolved problems in R6628P40

202305151137

·         Symptom: The device reboots abnormally with a low probability.

·         Condition: This symptom occurs if you execute the display diagnostic-information command to display or save running status data after you remove and install subcards.

202306270487

·         Symptom: A packet filter cannot drop the TCP packets with port 639.

·         Condition: This symptom occurs when you configure a packet filter to drop TCP packets with port 639.

202305251379

·         Symptom: The CPU usage is high on the leaf devices in an EVPN network.

·         Condition: This symptom occurs if ARP flood suppression works in response mode and the devices attached to the leaf devices migrate frequently, which causes IP address conflicts.

202305290972

·         Symptom: After a service card is restarted or removed, IKE negotiation fails, resulting in interruption of the IPsec service.

·         Condition: This symptom occurs if the device has multiple MPUs and a primary/backup switchover occurs.

202306301119

·         Symptom: On an RRPP ring, multicast traffic fails to be forwarded after a link switchover is performed.

·         Condition: This symptom occurs if you have enabled dropping unknown multicast data packets globally.

202305250569

·         Symptom: Residual IPv6SG bindings exist after you clear ND snooping entries in a VLAN.

·         Condition: This symptom might occur if you configure the device to create both ND snooping entries and IPv6SG bindings for a VLAN. An endpoint migrates frequently within the VLAN and sends NS packets to the device.

202306130155

·         Symptom: After a user goes offline, its IPv6 address binding entries are not deleted.

·         Condition: This symptom occurs if ND snooping is configured for a VSI and a large number of endpoints migrate between ACs of the VSI frequently and send ND packets.

202305251218

·         Symptom: The device outputs free memory early-warning notifications every hour if you edit the configured free-memory thresholds by adding the early-warning threshold and sufficient-memory threshold after a free-memory alarm has been triggered.

·         Condition: This symptom might occur if a free-memory alarm has been triggered without the early-warning threshold and the sufficient-memory threshold configured.

202306301160

·         Symptom: After a Layer 3 aggregate interface bound to a VPN instance is deleted, relevant ACL resources remain.

·         Condition: This symptom occurs if you bind a Layer 3 aggregate interface to a VPN instance, and then delete the Layer 3 aggregate interface directly.

202305251252

·         Symptom: A user fails HWTACACS authorization and accounting.

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

a.    Use the ip host or ipv6 host command to configure the host name of an HWTACACS server.

b.    In HWTACACS scheme view, specify the HWTACACS server by its host name and use it as the authentication, authorization, and accounting servers.

202306130886

·         Symptom: The SNMP collected traffic statistics is not consistent with the actual statistics.

·         Condition: This symptom occurs if the inbound or outbound accumulated traffic statistics on the network management port exceeds 4294967295.

202306150365

·         Symptom: The device cannot ping the PCs attached to access ports, and the PCs attached to trunk ports can be pinged.

·         Condition: This symptom occurs if ports join an aggregation group, a VPN instance is bound to the related Layer 3 aggregate interface, and ACL configuration is issued to the ports.

202305251257

·         Symptom: An M-LAG peer-link interface cannot forward packets of 1859 bytes or larger.

·         Condition: This symptom occurs if an M-LAG peer-link interface forwards traffic.

202306250055

·         Symptom: A VRRP network cannot be established.

·         Condition: This symptom occurs if the intermediate device is not configured with VRRP and is enabled with dropping unknown multicast data packets for a VLAN.

202306250483

·         Symptom: You cannot use SSH or Telnet to log in to the local device from another directly connected device.

·         Condition: This symptom occurs if the following Web authentication-free subnets exist on the local device:

¡  Web authentication-free subnet that contains the IP address for SSH or Telnet login.

¡  Web authentication-free subnet that has a mask shorter than the mask of the IP address for SSH or Telnet login.

202306061815

·         Symptom: The switch generates a core file for the PIM module.

·         Condition: This symptom occurs if the next hop of the optimal route to the source in an SSM multicast forwarding entry is a secondary IP address and route flapping occurs.

202305181213

·         Symptom: The switch reboots due to KernelAbnormalReboot.

·         Condition: This symptom occurs when multicast settings are configured on an IRF fabric.

202305291037

·         Symptom: An ucmd exception occurs when you enter a command.

·         Condition: This symptom occurs when HWTACACS command accounting is configured and the server changes from unreachable to reachable.

202306122053

·         Symptom: When all online users that are assigned the same authorization ACL go offline, the device fails to delete the authorization ACL information. Residual authorization ACL information exists on the device. As a result, the ACL resources are insufficient.

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

a.    Assign the authorization ACL to multiple BYOD online users in the same VSI.

b.    Log off all the users. The first online user assigned the authorization ACL is not the last one to go offline.

202305290786

·         Symptom: When conversational learning is enabled for forwarding entries of an AC, the device cannot issue AC forwarding entries to the hardware upon receiving traffic on the AC.

·         Condition: This symptom occurs if the AC is continuously receiving known unicast packets when you enable conversational learning for forwarding entries of the AC.

202306201965

·         Symptom: A MAC authenticated user cannot obtain an IP address after it is assigned to the BYOD authorization VSI.

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

¡  AD-Campus 6.3 solution.

¡  IRF and EVPN VXLAN network.

¡  MAC-based traffic match mode is disabled for dynamic Ethernet service instances on the interface on which the user is authenticated. This mode is configured by using the mac-based ac command.

¡  The user must pass MAC portal authentication on the leaf device, and it has passed MAC authentication.

202305300747

·         Symptom: Known unicast traffic is not isolated between VXLAN tunnels of different VXLANs.

·         Condition: This symptom occurs if packets are forwarded between two VXLAN tunnel interfaces.

202305251496

·         Symptom: The undo telnet server enable command cannot take effect.

·         Condition: This symptom occurs if you execute this command when the device acts as the Telnet server and the third-party Telnet client does not support option negotiation.

202307010424

·         Symptom: If the physical interface on which a PW resides receives more than 500 DHCP Discover messages per second, services (such as OSPF) running on that interface will be interrupted.

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

a.    The device is on the MPLS L2VPN network and is enabled with the DHCP service.

b.    The PW interface receives more than 500 DHCP Discover messages per second.

202305290977

·         Symptom: NAT port blocks for users run out easily, which causes insufficient port blocks and affects user services.

·         Condition: This symptom might occur when you configure DNS disabled with ALG in a NAT scenario. Five-tuple entries are generated and the aging timer for the entries is prolonged.

202305290958

·         Symptom: A user fails HWTACACS authentication and cannot log in to the Web interface of the device.

·         Condition: This symptom occurs if HWTACACS authentication is configured for login and the user attempts to log in to the Web interface of the device.

202305290894

·         Symptom: A SmartMC member repeatedly prints the following login failure log after it reboots: Feb 24 14:41:31:3042023 H3C NETCONF/6/SOAP_XML_LOGIN: admin from 127.0.0.1 loginfailed

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

a.    Modify the password for the default user (admin) on members.

b.    Save the member configuration and reboot the command.

202305290914

·         Symptom: In a DR system, the outgoing interface for traffic is incorrect after ND entries migrate.

·         Condition: This symptom occurs if a DR member device reboots and synchronizes ND entries with the DR peer, ND entries migrate on the DR member device, and the outgoing interface for traffic changes.

202305260074

·         Symptom: The output from the display lldp neighbor-information list command is displayed in garbled characters when LLDP is enabled on the device.

·         Condition: This symptom occurs if LLDP is enabled on the device and you execute display lldp neighbor-information list to display brief LLDP information that all LLDP agents received from the neighboring devices in a list.

202305251384

·         Symptom: Command execution fails. The CLI gets stuck.

·         Condition: This symptom occurs if you execute the default command, MAC authentication commands, or port security commands on a port during optimized automated deployment of the AD-Campus 6.3 solution.

202305251188

·         Symptom: Some DDNS features are unavailable.

·         Condition: This symptom might occur when you send packets to the DDNS server in which the Host field is an IP address instead of its corresponding domain name.

202305251147

·         Symptom: The IKED process on the MPU experienced an exception, which triggered the device to reboot abnormally.

·         Condition: This symptom occurs if IPsec and DPD are deployed, the device acts as the headquarters device, has a large number of IKE packets to handle, and has run for a long time.

202305251580

·         Symptom: The output from the display resource-monitor command shows that the VSI resource specification is 2K, which does not match the specification list.

·         Condition: This symptom occurs if you execute the display resource-monitor command to view VSI resource information.

202305260606

·         Symptom: IRF physical interfaces on the device cannot come up after the device reboots. As a result, the device cannot form an IRF fabric with other devices.

·         Condition: This symptom occurs if you use 100-GE/40-GE ports as IRF physical interfaces.

202305130310

·         Symptom: The following CAR-exceeded packet loss log is mistakenly reported:

¡  %Apr 18 04:49:15:237 2023 zubojieru-sw DRVPLAT/4/SOFTCAR DROP: -Slot=2;

¡   PktType=UNKNOWN_IPV4MCiptAKNOWN_IPV4MC , SrcMAC=642f-c7aa-d401, Dropped at Stage=0, StageCnt=0, TotalCnt=1.

·         Condition: This symptom occurs after the switch receives an unknown multicast packet and creates a drop-unknown entry.

202305051250

·         Symptom: A port on an LSWM2XMGT8P interface module fails to come up.

·         Condition: This symptom occurs if a port on an LSWM2XMGT8P interface module connects to a non-10G port.

202305200041

·         Symptom: The ACL resources are insufficient because the ACL resource occupation mode of voice VLAN is still the port mode after it is configured as the global mode.

·         Condition: This symptom occurs if IP phones are automatically discovered through LLDP.

202305230595

·         Symptom: A device cannot access the local device by using SSH through an aggregate interface. However, that device can ping the local device.

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

a.    Configure remote Web authentication.

b.    Use the web-auth free-ip command to specify Web authentication-free subnets.

c.    Enable Web authentication on the aggregate interface and an Ethernet interface.

d.    Remove the Web authentication-free subnets.

e.    Reconfigure the Web authentication-free subnets.

202306070855

·         Symptom: Packets carry incorrect source MAC addresses after being forwarded by an EVPN M-LAG system.

·         Condition: This symptom might occur if packets received on a tunnel interface are forwarded at Layer 3 over the peer-link to a singlehomed M-LAG interface on the M-LAG peer.

Resolved problems in R6628P35

202303280502

·         Symptom: The display interface brief command displays a nonexistent management port (MGE0/0/2) when it is executed on an IRF fabric.

·         Condition: This symptom might occur when you execute the display interface brief command on an IRF fabric.

202303130130

·         Symptom: Traffic coming into an AC interface is sent out of that AC interface, forming a loop.

·         Condition: This symptom occurs when the AC interface receives traffic whose source MAC address is the same as its destination MAC address.

202303101546

·         Symptom: After obtaining an IPv6 address through DHCPv6, the device fails to add the default route to its routing table.

·         Condition: This symptom might occur if a device uses DHCPv6 for IPv6 address acquisition.

202303280505

·         Symptom: The device cannot communicate with the directly connected peer device through IPv6, and the packet loss ratio approaches 100%.

·         Condition: This symptom occurs if a large number of unknown multicast packets exist between the devices and therefore ICMPv6 packets are abnormally dropped.

202303101686

·         Symptom: Enable the DHCP snooping entry auto backup feature, and back up the DHCP snooping entries for one time. When you use the dhcp snooping binding database update now command to manually save DHCP snooping entries to the backup file again, the backup fails. In this case, the Status field displays writing in the command output from the display dhcp snooping binding database command.

·         Condition: This symptom occurs if the TFTP server does not support the protocol length feature. 

202303031164

·         Symptom: After a SmartMC member device restarts, the device keeps reporting log messages for local login failures. The log content is "Feb 24 14:41:31:3042023 H3C NETCONF/6/SOAP_XML_LOGIN: admin from 127.0.0.1 loginfailed."

·         Condition: This symptom might occur if you use smartmc tc password on the commander to edit the password of default user admin for members, save member configurations, and then restart members.

202303101381

·         Symptom: The IRF fabric reboots because the memory is exhausted.

·         Condition: This symptom occurs if a master/subordinate switchover is performed or a DHCP client requests multiple addresses from the IRF fabric acting as a DHCP relay.

202304101304

·         Symptom: An AP attached to an M-LAG system cannot obtain an IP address.

·         Condition: This symptom occurs if the M-LAG member devices act as management gateways and ARP snooping is enabled on them.

202303141487

·         Symptom: The DHCP process exits unexpectedly and then recovers after DHCP relay entries are aged out.

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

¡  The switch acts as a DHCP relay.

¡  A DHCP client obtains two IP addresses on an interface and then obtained one of the two addresses on anther interface.

¡  The DHCP relay entries are aged out.

202303240777

·         Symptom: When the device is automatically deployed, some ports fail to be assigned to an aggregation group.

·         Condition: This symptom occurs if the device is automatically deployed and multiple ports are assigned to the same aggregation group.

202303220706

·         Symptom: When the RADIUS authentication server for 802.1X authentication is unreachable, users cannot bypass authentication through the none authentication method.

·         Condition: This symptom occurs if the RADIUS authentication server is unreachable and the none authentication method is used.

·         Workaround: Execute the dot1x critical eapol command.

202303100258

·         Symptom: A server attached to an EVPN M-LAG system cannot ping an external network.

·         Condition: This symptom might occur if an M-LAG interface with the lacp edge-port setting configured flaps repeatedly.

202302270531

·         Symptom: After an IRF fabric splits, the subordinate device cannot detect loops.

·         Condition: This symptom might occur if an IRF fabric splits.

202303030899

·         Symptom: BGP sessions flap.

·         Condition: This symptom might occur if the device receives a large number of packets that do not match any routes.

202302201089

·         Symptom: The device does not support collecting packet statistics on Layer 3 aggregate subinterfaces.

·         Condition: This symptom might occur if the traffic-statistic enable command is executed on Layer 3 aggregate subinterfaces.

202302170758

·         Symptom: Track is associated with EAA. When the state of a track entry changes from negative to positive, the monitoring policy action is not executed.

·         Condition: This symptom might occur if a track monitoring event is associated with multiple track entries and one of the track entries changes from not ready state to positive state.

202303090021

·         Symptom: On an IRF fabric, traffic received on a Layer 3 aggregate interface cannot be forwarded between the IRF member devices.

·         Condition: This symptom might occur if a Layer 3 aggregation group is created before IRF physical interfaces are bound to IRF ports.

202302240358

·         Symptom: The device reboots unexpectedly because of a kernel exception.

·         Condition: This symptom might occur if the display diagnostic-information command is executed.

202301092178

·         Symptom: When a TFTP server is used to save auto backup DHCP snooping entries, only one entry can be stored.

·         Condition: This symptom occurs if a TFTP server is used to save auto backup DHCP snooping entries.

202302160003

·         Symptom: Static EVPN MAC address entries synchronized from the remote VTEP to the local VTEP are deleted. 

·         Condition: This symptom occurs if only static EVPN MAC address entries are synchronized from the remote VTEP to the local VTEP. The synchronized EVPN MAC address entries are deleted after an aging period.

202302101133

·         Symptom: When a VXLAN tunnel is used as a peer link on an EVPN M-LAG network, the broadcast packets received on the peer link are incorrectly forwarded to the local M-LAG interface.

·         Condition: This symptom occurs if broadcast packets are received on the peer link.

202302101493

·         Symptom: On an IRF fabric, the SNMP server does not receive link-down alarms from IRF physical interfaces.

·         Condition: This symptom occurs if a service interface of the subordinate IRF member device is connected to the SNMP server and the IRF physical interfaces go down.

202212300039

·         Symptom: The device reboots unexpectedly.

·         Condition: This symptom occurs if MQC configuration matches both IPv4/IPv6 packets and packets with multiple outer VLAN tags.

202302021438

·         Symptom: The switch prints an error message when a DHCPv6 client requests an IPv6 prefix from the DHCPv6 server through the switch.

·         Condition: This symptom occurs if the switch acts as a DHCP snooping device and you have executed the ipv6 dhcp snooping pd binding record and ipv6 verify source ip-address mac-address commands on the switch.

202303090071

·         Symptom: Alarm log messages show that available AC resources exist when underlying hardware resources are exhausted.

·         Condition: This symptom might occur if AC resources are exhausted by a large amount of configuration.

Resolved problems in R6628P30

202212240006

·         Symptom: The device reboots unexpectedly or fails to set up NAT sessions.

·         Condition: This symptom occurs if the display nat session command is executed during execution of the nat static outbound command.

202301110093

·         Symptom: On an M-LAG system, ARP entries and MAC address entries are incorrect, and the peer link cannot be used to forward traffic.

·         Condition: This symptom occurs if the M-LAG system is automatically deployed by using devices that start up with initial configuration.

202301111261

·         Symptom: On an EVPN VXLAN M-LAG system formed by two leaf devices, reboot of one M-LAG member device results in reboot of the other M-LAG member device. The M-LAG system resumes operation after multiple automatic reboots.

·         Condition: This symptom occurs if 1500 MAC authentication users access the network through ARP learning and the primary member device is rebooted.

202212300039

·         Symptom: The device reboots unexpectedly.

·         Condition: This symptom occurs if MQC configuration matches both IPv4/IPv6 packets and packets with multiple outer VLAN tags.

202301060304

·         Symptom: A delay exists when MAC authentication users access the network.

·         Condition: This symptom occurs if MAC authentication users go offline after successful authentication and MAC authentication is triggered again.

202212081055

·         Symptom: The device cannot come online because the ipv6 address dhcp-alloc command on VLAN interface 1 is lost.

·         Condition: This symptom occurs if the automatic configuration process ends or you manually terminate the automatic configuration process during an IPv6 automatic deployment.

202212080022

·         Symptom: The device reboots when a large number of MAC authentication users come online and go offline on an aggregate interface and ACLs and URLs are authorized to the users.

·         Condition: This symptom occurs might if a large number of MAC authentication users come online and go offline on an aggregate interface and ACLs and URLs are authorized to the users.

202208301357

·         Symptom: An endpoint cannot pass Web authentication in an M-LAG system.

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

¡  The distributed even-/odd-MAC mode is configured for authentication load sharing.

¡  The MAC address of the endpoint is an odd MAC address.

¡  The authentication packets are sent to the M-LAG member device in distributed even-MAC mode.

202211280698

·         Symptom: When a route server reflects an EBGP route, it mistakenly modifies the router MAC address in the route as its own router MAC address.

·         Condition: This symptom occurs if you have executed both the peer route-server-client and peer router-mac-local dci commands on the route server.

202211240773

·         Symptom: A clients reports two different XPATH messages, and another client reports no messages.

·         Condition: This symptom occurs if you configure gNMI subscriptions and concurrent sessions exist.

202301040135

·         Symptom: The subscribed IP-SGT information is deleted one hour after the WebSocket connection between the device and the controller is disconnected.

·         Condition: This symptom occurs after the WebSocket connection between the device and the controller is disconnected.

202301040134

·         Symptom: An error occurs during device startup.

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

202301040841

·         Symptom: After you execute the display mad verbose command on an IRF member device, the command output displays both VLAN interfaces and excluded ports while only VLAN interfaces should be displayed.

·         Condition: This symptom occurs if an IRF fabric is split and then established.

202207050531

·         Symptom: After you delete an interface, the resources allocated to the interface cannot be released. As a result, the system cannot allocate these resources to other functions.

·         Condition: This symptom occurs if you delete the source interface specified for VXLAN default decapsulation.

202212280017

·         Symptom: In an EVPN multicast network, the multicast traffic is mistakenly forwarded.

·         Condition: This symptom occurs if the device forwards multicast traffic.

202212280016

·         Symptom: A QoS policy on an M-LAG member device fails to match with the packets sent from the peer.

·         Condition: This symptom occurs if an M-LAG member device configured with a QoS policy receives packets from the peer through the peer link in an M-LAG system.

202301051651

·         Symptom: Failed to restore the default settings for a Smartrate-Ethernet interface by executing the default command.

·         Condition: This symptom occurs if you have executed the stp instance 0 port priority 16 command on a Smartrate-Ethernet interface.

202301040139

·         Symptom: In an M-LAG system, the interfaces in M-LAG MAD DOWN state fail to restore to normal after an M-LAG member device restarts.

·         Condition: This symptom occurs if the member port rates of the peer link interface are inconsistent.

202212220265

·         Symptom: The device fails to issue the m-lag extra-vlan command through NETCONF for the first time.

·         Condition: This symptom occurs if the device issues the m-lag extra-vlan command through NETCONF for the first time after device startup.

202212281015

·         Symptom: In a VXLAN network configured with M-LAG, the device acting as a leaf node drops multicast packets from the spine.

·         Condition: This symptom occurs when the leaf node receives multicast packets from the spine in a VXLAN network configured with M-LAG.

202212260304

·         Symptom: The OSPF neighbors and PIM neighbors flap.

·         Condition: This symptom occurs if the device receives a large number of multicast packets with TTL 1.

202212191223

·         Symptom: On an MPLS network, the VSI TTI configuration is not cleared after you configure AC settings and then restore the device to empty configuration.

·         Condition: This symptom occurs if you configure AC on the device and then restore the empty configuration for the device.

202212060168

·         Symptom: No output is displayed upon execution of the display kernel reboot command.

·         Condition: This symptom might occur when you execute the display kernel reboot command to view information about device reboot events.

202211181050

·         Symptom: In an M-LAG network, online 802.1X user go offline and new users cannot come online after one member device (leaf device) is upgraded.

·         Condition: This symptom occurs if you form an M-LAG network by using two leaf devices and upgrade one leaf device

202212200312

·         Symptom: 40-GE IRF physical interfaces might fail to come up with a low probability.

·         Condition: This symptom occurs if 40-GE cables are used to set up an IRF fabric and one IRF member device is rebooted.

Resolved problems in R6615P08

202207111528

·         Symptom: No commands can be entered after the dmesg command is executed.

·         Condition: This symptom occurs if you enter the dmesg command in kdb view after the device is power cycled.

202208051014

·         Symptom: In a VPLS network, the packets of a PW have inner encapsulation errors.

·         Condition: This symptom occurs if you flap the PW-side interface repeatedly.

202208040950

·         Symptom: VPLS packets fail to be forwarded in an MPLS network with P devices.

·         Condition: This symptom occurs if the outgoing label on the public network PE is the same as the incoming label on the P device.

202207220046

·         Symptom: Endpoints fail to be obtain IP addresses from the IRF fabric acting as a DHCP server.

·         Condition: This symptom occurs if the IRF fabric connects to the AC interface and experiences a master/subordinate switchover.

202206020061

·         Symptom: Cross-subnet packets cannot be forwarded in hardware.

·         Condition: This symptom occurs if the peer device is enabled with source MAC check.

202208041205

·         Symptom: The HardwareRev information about a subcard read through NETCONF is wrong.

·         Condition: This symptom occurs if you read the HardwareRev information about a subcard through NETCONF.

202206161204

·         Symptom: A user fails to obtain an IP address and fails to come online after the user.

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

¡  Policy check is enabled on the server.

¡  The user comes online from the isolation security group and passes security checks.

¡  The user is switched to the service security group.

202206210576

·         Symptom: The configuration fails to take effect because the free memory is insufficient.

·         Condition: This symptom occurs if a physical interface goes down and comes up frequently.

202206250439

·         Symptom: The VPN instance associated with interface does not take effect after the device reboots

·         Condition: This symptom occurs if you associate the same VPN instance with a Layer 3 Ethernet subinterface and a VLAN interface that have the same interface number.

202202150772

·         Symptom: IRF physical interfaces cannot come up.

·         Condition: This symptom occurs if a 100-Gbps expansion interface card is installed in the device, interfaces on subcards are installed with 40-Gbps transceiver modules or cables, and these interfaces can configured as IRF physical interfaces.

202112271474

·         Symptom: Member devices in a VXLAN DR system might reboot unexpectedly.

·         Condition: This symptom might occur if a certain script is executed.

202109060975

·         Symptom: PIM DM is disabled on a VLAN interface, Layer 2 multicast entries are not established on the subordinate IRF member device, and multicast traffic is broadcast within the VLAN.

·         Condition: This symptom occurs if both Layer 2 multicast and Layer 3 multicast are configured for the same VLAN, traffic is received on the subordinate IRF member device, and IGMP snooping is configured for the VLAN on an IRF fabric.

202205270372

·         Symptom: Outgoing packets carry an incorrect source MAC address.

·         Condition: This symptom occurs if the following operations have been performed:

¡  Configure a MAC address on a VLAN interface.

¡  Delete the VLAN interface and re-create it.

202205240571

·         Symptom: Threads of OSPFv3 access invalid pointers and are hanged, the core is abnormal, and routes are not updated.

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

a.    Configure a VPN instance that has no OSPFv3 instances.

b.    Associate the VPN instance with an interface and execute the ipv6 address command on the interface.

c.    Execute OSPFv3 preconfigured commands but not OSPFv3 enable commands. The ospfv3 1 area 0 command is an example of OSPFv3 enable commands. OSPFv3 preconfigured commands refer to commands other than enable commands, such as ospfv3 timer hello, ospfv3 network-type, and ospfv3 cost.

d.    Remove the VPN instance-interface association or delete the VPN instance.

202204110848

·         Symptom: Source ports in a local mirroring group fail to be configured after the source ports in another local mirroring group are configured.

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

¡  Configure the monitor port as the same port for seven local mirroring groups.

¡  Configure the source ports for the seventh local mirroring group.

¡  Configure the source ports for another local mirroring group among the remaining local mirroring groups.

202110261296

·         Symptom: In an inter-VPN forwarding scenario, multicast traffic cannot be forwarded to the public network.

·         Condition: This symptom occurs if a member port is repeatedly added to and removed from the aggregate interface for the tunnel and the private route flaps.

202112310599

·         Symptom: The device issues Layer 3 IPv4 multicast entries successfully and might fail to issue some Layer 3 IPv6 multicast entries, which causes multicast forwarding errors.

·         Condition: This symptom might occur if the device issues 3000 IPv4 IPMC multicast entries and then 250 IPv6 IPMC multicast entries and the number of multicast entries reaches the upper limit.

Resolved problems in R6615P07

202110191417

·         Symptom: Once removed from a monitoring group, an interface cannot be assigned to monitoring groups again.

·         Condition: This symptom might occur if traffic is mirrored to a monitoring group through local mirroring and flow mirroring.

202112250446

·         Symptom: EVPN and Layer 2 multicast are configured on the device, and the igmp-snooping drop-unknown setting does not take effect.

·         Condition: This symptom might occur if a VXLAN ID is deleted and recreated on a VSI.

202111260029

·         Symptom: MAC address entries created for MAC authentication users are not deleted after MAC authentication is disabled on DR interfaces.

·         Condition: This symptom might occur if MAC authentication is disabled on DR interfaces of a DR system that uses an Ethernet aggregate link as the IPL.

202112081609

·         Symptom: On an EVPN DR system, a BGP task is abnormal and creates a core file.

·         Condition: This symptom might occur if the DR system receives ARP packets and 1000 attached hosts migrate from the DR system.

202112081745

·         Symptom: The device generates blackhole MAC address entries and does not forward certain traffic.

·         Condition: This symptom might occur if incoming traffic matches a MAC-based VLAN and an IP subnet-based VLAN simultaneously on the same interface.

202112131788

·         Symptom: EVPN is enabled to forward Layer 2 multicast traffic. After a VXLAN ID is deleted and then created again, the drop-unknown setting does not take effect.

·         Condition: This symptom might occur if a VXLAN ID is deleted and created again with the drop-unknown setting being intact.

202112280428

·         Symptom: MAC address entries are not deleted completely, and the type of the MAC address entries is incorrect.

·         Condition: This symptom might occur if the following events occur on a DR system formed by two devices with different capabilities:

a.    The traffic load reaches the limit of the device with higher capabilities.

b.    The reset l2vpn mac command is executed.

202112280864

·         Symptom: MAC address learning is disabled globally when the device is receiving dense traffic, but dynamic MAC address entries are not deleted.

·         Condition: This symptom might occur if MAC address learning is disabled globally when the device is receiving dense traffic.

202112281596

·         Symptom: An EVPN DR system uses an Ethernet aggregate link as the IPL. After an AC is deleted and recreated, the AC does not take effect.

·         Condition: This symptom might occur if the following events occur:

a.    The maximum number of ACs is reached.

b.    A static AC is deleted and recreated on a non-DR interface or DR interface.

202201040231

·         Symptom: The device fails to forward some multiple packets.

·         Condition: This symptom might occur if BIDIR-PIM is enabled and RPs are configured in BIDIR-PIM domains.

202112291070

·         Symptom: Users fail authentication after the attached IRF fabric reboots.

·         Condition: This symptom might occur if an IRF master/subordinate switchover occurs when the interface used for authentication is down and users are online.

202112291428

·         Symptom: A non-existent VLAN is created on the primary DR device in type 2 configuration consistency check.

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

a.    Two devices are booted with initial configuration, and they are configured to set up a DR system.

b.    The keepalive link comes up.

c.    An IPP is configured on the primary and secondary devices in sequence.

202112301425

·         Symptom: On an EVPN DR system, synchronized MAC addresses are issued to incorrect ACs, and this issue cannot be recovered.

·         Condition: This symptom might occur if ACs match single-tagged packets and the following operations are performed:

a.    ACs matching the same VLAN are mapped to different VSIs.

b.    The ACs are deleted.

c.    The ACs are recreated to match the same VLAN and mapped to the same VSI.

·          

202201041255

·         Symptom: Broadcast/multicast storm suppression does not take effect on a 100G interface. Broadcast/multicast/unknown unicast storm suppression cannot be disabled on a 100G interface.

·         Condition: This symptom occurs if you enable broadcast/multicast/unknown unicast storm suppression on a 100G interface and then disable broadcast/multicast/unknown unicast storm suppression on the 100G interface.

202205111296

·         Symptom: A VSI interface in down state can still act as a gateway interface to forward traffic.

·         Condition: This symptom occurs if the shutdown command is executed on a VSI interface configured as the VXLAN gateway interface.

202205111299

·         Symptom: When a PoE interface fails to supply power, the traps cannot correctly report the failure. 

·         Condition: This symptom occurs if the maximum power configured on the PoE interface cannot meet the power requirements of the attached PDs.

202205111292

·         Symptom: Within 5 minutes after the VCF fabric is automatically deployed. the devices try to obtain the device list file.

·         Condition: This symptom occurs if legacy automated deployment is performed for the devices and the device list is not configured.

202205111301

·         Symptom: After the VCF fabric is automatically deployed, the original PVID settings of interfaces are lost.

·         Condition: This symptom occurs if a device is automatically deployed as an access device, the interfaces have original PVID settings, the interfaces are connected to APs, and then the APs are removed.

202203300334

·         Symptom: The device reboots unexpectedly.

·         Condition: This symptom occurs if an AC is associated with a VSI on the device.

202201200603

·         Symptom: When loop detection is configured on a VSI and ARP packets are injected to a blocked AC, the AC can still respond with ARP replies normally.

·         Condition: This symptom occurs if ARP proxy is configured on the VSI.

202108170529

·         Symptom: The MAC address entries for MAC authentication users and 802.1x users are not deleted after they go offline.

·         Condition: This symptom occurs if MAC authentication users and 802.1x users move between member devices on an IRF fabric.

202203211300

·         Symptom: After a transceiver module is installed into a port, the device reboots unexpectedly.

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

a.    A DR system has peer links.

b.    Configure an AC on the DR interface (an aggregate interface).

c.    On a single-homed interface, configure an AC with the same service instance.

Resolved problems in R6615P05

202202160159

·         Symptom: Errors occur in issuing flow IDs to the driver after BYOD users come online.

·         Condition: This symptom might occur if BYOD users come online on a single interface.

202202150963

·         Symptom: ACLs issued for VXLAN ACs are not deleted after the ACLs age out.

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

¡  Conversational learning is enabled for forwarding entries when ACs are mapped to VSIs.

¡  ACs receive traffic, and then the traffic stops.

202202080204

·         Symptom: An interface with static ACs configured cannot ping the controller.

·         Condition: This symptom might occur if an aggregate interface with static ACs configured flaps and conversational learning is enabled for forwarding entries on the static ACs.

202201050390

·         Symptom: Synchronized MAC address entries do not age out on a distributed EVPN gateway.

·         Condition: This symptom might occur if MAC addresses move between two DR interfaces.

202202080199

·         Symptom: The active MPU and driver do not have AC data.

·         Condition: This symptom might occur if ACs with conversational learning enabled are deleted and then ACs with conversational learning disabled are created.

202202080205

·         Symptom: The device reboots unexpectedly.

·         Condition: This symptom might occur if conversational learning is enabled for ACs and then the interface where the ACs reside flaps.

202112270862

·         Symptom: AC resources for a VSI might not be deleted completely when an authentication user logs off and then logs on again.

·         Condition: This symptom might occur if user MAC addresses move between interfaces and a large number of authentication users exist.

Resolved problems in R6615P03

202012181363

·         Symptom: The interface-up events of 100-GE interfaces on the front panel might not be sent.

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

¡  100-GE interfaces on the front panel are connected with 100-G cables.

¡  A broadcast storm occurs.

¡  One of the interfaces is shut down by using the shutdown command.

202012171705

·         Symptom: When an NMS is used to read the value of the hh3cEntityExtErrorStatus MIB variable for sensor 3 on a device that has two slots, the system returns a value "not supported".

·         Condition: This symptom occurs on a device that has two slots

202012171693

·         Symptom: Some endpoints cannot obtain IP addresses.

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

a.    The device acts as the WLAN gateway and provides DHCP relay and portal authentication services.

b.    The endpoints send DHCP requests towards the device.

202012031187

·         Symptom: The BFD MAD session of an IRF fabric comes up and then goes down after the IRF fabric splits.

·         Condition: This symptom occurs when BFD MAD is used to detect IRF split.

202012030458

·         Symptom: SSH users cannot log in.

·         Condition: This symptom occurs if a large number of SSH users concurrently log in to or log out of the device and meanwhile, AAA settings are added or deleted on the device.

202010130105

·         Symptom: Unknown unicast storm suppression does not take effect if broadcast storm suppression and unknown unicast storm suppression are both configured on an interface of an LSWM2XMGT8P interface module.

·         Condition: This symptom might occur if broadcast storm suppression and unknown unicast storm suppression are both configured on an interface of an LSWM2XMGT8P interface module.

202009251219

·         Symptom: A serial port does not respond to commands when the device is operating in VXLAN mode.

·         Condition: This symptom might occur if routes are added or deleted after the device load digware.

202009120515

·         Symptom: An IRF fabric unexpectedly outputs error messages.

·         Condition: This symptom might occur after a master/subordinate switchover or after a cable is removed and then inserted.

202005251254

·         Symptom: The portsecd process is stuck and it cannot process other services after the device reboots.

·         Condition: This symptom occurs if the device reboots when the following conditions exist:

¡  The IMC server does not support the RESTful server-assisted MAC authentication user recovery feature.

¡  The RESTful server-assisted MAC authentication user recovery feature is enabled on the device.

202005130044

·         Symptom: The entPhysicalDescr MIB node information for an interface card still exists after the interface card is removed.

·         Condition: This symptom occurs if you display MIB node information after an interface card is removed.

202004160007

·         Symptom: When RESTful server-assisted MAC authentication user recovery is configured on an S6520X IRF fabric, some of authenticated dumb terminals cannot reauthenticate to come online after the entire IRF fabric reboots.

·         Condition: This symptom might occur if the following conditions exist on the S6520X IRF fabric:

¡  The IRF fabric is a leaf device.

¡  A large number of MAC authenticated dumb terminals have been online on the IRF fabric before it reboots.

202112020369

·         Symptom: The gRPC server does not generate messages for the LLDP events that occur on the device.

·         Condition: This symptom might occur if the gRPC dial-in mode is enabled for gRPC clients to subscribe to LLDP events on the device.

202112020418

·         Symptom: gPRC cannot collect LLDP information.

·         Condition: This symptom might occur if sensor paths are configured for gRPC.

202112100200

·         Symptom: The memory usage of DBM keeps increasing.

·         Condition: This symptom might occur if DHCP users come online after DHCP snooping is enabled.

202112300693

·         Symptom: The device generates the following log message:

¡  %Sep 16 09:20:04:133 2021 QX-S5324GT-4X1CLIPC/4/LIPC_STCP_CHECK: -Slot=1; Data

¡  stays in the receive buffer for an overlong time. Owner=ifmgr, VRF=0, local add

¡  ress/port=8/23721, remoteaddress/port=48/14610. 

·         Condition: This symptom might occur if the device is in an IRF fabric under stress tests.

202112031013

·         Symptom: The device cannot forward multicast traffic through interfaces on the module that receives the traffic.

·         Condition: This symptom might occur if the module provides member ports for a multislot aggregate interface and the received multicast traffic is forwarded out of other member ports of the aggregate interface.

202112070565

·         Symptom: gRPC cannot be enabled, and core files are created as a result.

·         Condition: This symptom might occur if the grpc enable command is executed.

202112110581

·         Symptom: The device drops the ARP packets synchronized by iBGP, and iBGP flapping occurs as a result.

·         Condition: This symptom might occur if the device receives heavy ARP traffic.

202111011647

·         Symptom: RADIUS packet source IP configuration does not take effect.

·         Condition: This symptom might occur if the source IP address of RADIUS packets is configured in system view while the specified IP address is not configured in the RADIUS scheme.

202112151668

·         Symptom: The display drni consistency type1 global command does not display the configuration consistency check result for STP.

·         Condition: This symptom might occur if spanning tree is enabled before DRNI is configured.

202112021613

·         Symptom: In an MVXLAN network, a spine device forwards only half of the traffic demanded by multicast receivers.

·         Condition: This symptom might occur if the spine device receives multicast traffic from a multislot aggregate interface.

202112200471

·         Symptom: The ssl renegotiation disable command does not take effect.

·         Condition: This symptom might occur if the ssl renegotiation disable command is executed.

202112061020

·         Symptom: If MAC resources are insufficient, an error occurs when a MAC address is assigned to a Layer 3 interface. When the interface is assigned a MAC address again, the device outputs an incorrect message.

·         Condition: This symptom might occur if a MAC address is assigned to a Layer 3 interface when MAC resources are insufficient.

202112211353

·         Symptom: A DR system is formed by two EVPN VXLAN-configured devices. When a DR member device forwards packets received from a VXLAN tunnel interface out of a DR interface, incorrect VLAN tags are added to the packets.

·         Condition: This symptom might occur if the l2vpn drni peer-link ac-match-rule vxlan-mapping command is executed on the DR member devices.

202201040031

·         Symptom: An IRF member device that performs user authentication reboots unexpectedly.

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

a.    Send traffic sourced from 100 different MAC addresses to a subordinate device for MAC authentication.

b.    Execute the undo mac-address vlan x command on the master device to delete the MAC address entries of the VLAN where the source MAC addresses belong.

c.    Repeatedly restart the peer interface connected to the interface with MAC authentication enabled.

202112131083

·         Symptom: A PBR policy cannot match packets on a VSI interface.

·         Condition: This symptom might occur if a PBR policy is applied to a VSI interface.

202112110479

·         Symptom: In an EVPN VXLAN network, a leaf device cannot ping a spine device.

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

¡  A microsegment that does not contain members is bound to an interface with ACs configured on the leaf device.

¡  The microsegment uses a PBR policy as a GBP, and the output interface is null.

202112020366

·         Symptom: The device fails to forward Layer 2 packets destined for a VRRP virtual MAC address.

·         Condition: This symptom might occur if a VRRP virtual MAC address is not deleted after VRRP configuration is deleted.

202112020088

·         Symptom: MLD snooping entries are synchronized to an IPP.

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

¡  Layer 3 multicast is configured on a DR system.

¡  MLD snooping is enabled on one of the DR member devices.

202112020336

·         Symptom: An IRF fabric does not issue microsegments to users immediately after it reboots. The microsegments are issued after users come online again.

·         Condition: This symptom might occur if a master/subordinate switchover occurs when local users are online.

202112220251

·         Symptom: Multicast cannot be enabled on a Layer 3 Ethernet subinterface.

·         Condition: This symptom might occur if multicast is enabled on a Layer 3 Ethernet subinterface.

202112220439

·         Symptom: Multicast traffic forwarding is abnormal in BIDIR-PIM mode.

·         Condition: This symptom might occur if BIDIR-PIM is enabled on interfaces after the device issues PIM SSM entries.

202112081824

·         Symptom: The device creates MAC address entries for the PVID configured for QinQ on an interface with both QinQ and many-to-one VLAN mapping configured.

·         Condition: This symptom might occur if both QinQ and many-to-one VLAN mapping are configured on an interface.

202112081736

·         Symptom: The device drops the broadcast packets received on an interface with both QinQ and VLAN mapping configured.

·         Condition: This symptom might occur if the broadcast packets match only the QinQ configuration.

202112270899

·         Symptom: Memory leakage occurs.

·         Condition: This symptom might occur if the MAC address in an ARP entry changes constantly.

202112090315

·         Symptom: A downlink aggregate interface on a leaf device has one selected member port and one unselected member port, and the unselected member port receives massive gratuitous ARP packets. As this condition persists, the network becomes abnormal.

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

¡  The member ports of the downlink aggregate interface are attached to an IRF master device and an IRF subordinate device, respectively.

¡  The IRF member devices boot with initial configuration.

202112200322

·         Symptom: An EVPN DR system forwards traffic incorrectly.

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

¡  The l2vpn drni peer-link ac-match-rule vxlan-mapping command is executed on the DR member devices.

¡  One DR member device receives gratuitous ARP packets and forwards them over the IPL to the other DR member device.

202112022120

·         Symptom: An error occurred in setting up link aggregations during automatic deployment of a VCF fabric.

·         Condition: This symptom might occur if network cables are replaced when automatic deployment is paused.

202112020363

·         Symptom: In an MPLS VPLS network, two endpoints cannot ping each other over their attached PEs.

·         Condition: This symptom might occur if the mpls ttl propagate vpn command is executed on the PEs.

202112090252

·         Symptom: A primary/secondary device switchover occurs when a DR system is stable.

·         Condition: This symptom might occur if all interfaces on the primary DR device are shut down and the interfaces are brought up when the device role changes to none.

202112020423

·         Symptom: The dhcpc6d process is abnormal, which causes the device to reboot.

·         Condition: This symptom might occur if the DHCPv6 client feature is configured on the automatically deployed device.

202112220442

·         Symptom: An EVPN gateway fails to forward Layer 3 unicast traffic.

·         Condition: This symptom might occur if the underlay network is an IPv6 network and VPN instances are associated with VSI interfaces.

202112270385

·         Symptom: The display vxlan tunnel command does not output VXLAN tunnel information.

·         Condition: This symptom might occur if the device is running a script.

202112271425

·         Symptom: The DHCP client attached to a DR interface receives two identical DHCP ACK packets.

·         Condition: This symptom might occur if EVPN, DRNI, and DHCP relay are configured in conjunction.

202111250623

·         Symptom: An access device attached to an EVPN DR system cannot ping a remote IP address.

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

¡  The DR member devices create frame match criteria based on VXLAN IDs for the dynamic ACs on the Ethernet aggregate link IPL.

¡  A DR interface on one DR member device is disconnected, and the uplink on the other DR member device is disconnected.

202112141808

·         Symptom: An EVPN DR system receives the ARP packets that have been forwarded to a remote device.

·         Condition: This symptom might occur if a DR member device forwards ARP packets over a tunnel.

202112171738

·         Symptom: Users fail authentication after the device reboots.

·         Condition: This symptom might occur if microsegment authentication is enabled and the running configuration is saved before the device is rebooted.

202112100527

·         Symptom: On an EVPN DR system, MAC address entries synchronized from a DR peer are deleted.

·         Condition: This symptom might occur if a VSI has multiple route targets and the ARP and MAC information for an endpoint moves between a DR interface and a single-homed interface.

202112020434

·         Symptom: The MAC address of an aggregate interface changes constantly, which causes 802.1X handshake failure and 802.1X user logoff.

·         Condition: This symptom might occur if an IRF master/subordinate switchover occurs after aggregate interfaces are configured.

202112022115

·         Symptom: The device warns of resource insufficiency when the number of VSIs exceeds half of the upper limit.

·         Condition: This symptom might occur if the number of VSIs exceeds half the upper limit.

202110110734

·         Symptom: IPSG bindings are not deleted completely.

·         Condition: This symptom might occur if the device changes the output interface in an ARP snooping entry after receiving an RARP packet.

·         Remarks: This problem is resolved when you install the patch. However, you must execute the process restart name ipcimd slot 1 command to delete the residual IPSG bindings. If the device does not have enough available memory, it might reboot during patch installation.

202111041425

·         Symptom: A leaf device cannot reach the external networks.

·         Condition: This symptom might occur if the device fails to forward tunneled packets based on ECMP routes with the same destination network and next hop.

202112020347

·         Symptom: The device fails to forward traffic over an EVPN network.

·         Condition: This symptom might occur if VSIs, VPN instances, and VSI interfaces are repeatedly deleted and created.

202111290655

·         Symptom: The MAC-portal user who comes online first can access the external networks without BYOD authentication.

·         Condition: This symptom might occur if a BYOD user accesses an IRF subordinate device for authentication.

202108161213

·         Symptom: The LLDP process restarts unexpectedly.

·         Condition: This symptom might occur if an aggregate interface and its member ports have descriptions configured and the lldpLocManAddrEntry MIB node is read.

·         Workaround: Do not read the lldpLocManAddrEntry MIB node if an aggregate interface and its member ports have descriptions.

202112020345

·         Symptom: In the output from the display power command, the status of a present power module might be absent.

·         Condition: This symptom might occur if the display power command is executed.

202112020081

·         Symptom: Two 100G interfaces are connected to each other. After one interface is shut down, the other interface is still up.

·         Condition: This symptom might occur if two 100G interfaces are connected to each other on an IRF fabric and one of the interfaces is shut down.

202112100319

·         Symptom: NETCONF fails to obtain information from the DevicePortInfo node.

·         Condition: This symptom might occur if NETCONF is used to read the DevicePortInfo node.

Resolved problems in R6515P06

202012150773

·         Symptom: The device reboots unexpectedly.

·         Condition: This symptom occurs if the number of multicast receivers that join a multicast group exceeds the upper limit and the multicast receivers repeatedly perform 802.1X authentication to come online and then go offline.

202012180150

·         Symptom: The device reboots unexpectedly.

·         Condition: This symptom occurs with a low probability if the following conditions exists:

¡  The setting of unknown unicast packet filtering causes an array out of bound exception.

¡  On a device with a slot number other than 1, Layer 3 interfaces are configured and the interfaces in up status are assigned to a VLAN by using the port access vlan command.

202012151121

·         Symptom: On an AD-campus network, MLD packets are flooded .

·         Condition: This symptom occurs if the flooding disable all all-direction command is executed in a VSI after IPv6 addresses are configured on interfaces or IPv6 related features are configured.

202012150852

·         Symptom: On an AD-campus network, configuration on leaf nodes gets lost and the leaf nodes are unmanaged.

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

¡  The devices are brought online by automated VCF fabric deployment.

¡  Spine nodes are upgraded and restarted after leaf nodes are upgraded and restarted.

202012150822

·         Symptom: Packet forwarding delay exists on the device.

·         Condition: This symptom occurs if a single-mode fiber is connected to the transceiver module on the device or the Rx signals are unstable.

202012150828

·         Symptom: Storm control does not take effect when the device receives traffic that exceeds the threshold.

·         Condition: This symptom occurs if storm control is configured on the device and the threshold is set in percentage.

202012150751

·         Symptom: The MAD IP address configuration fails to be deployed to member devices in an IRF fabric.

·         Condition: This symptom occurs if BFD MAD is configured on the IRF fabric.

202012150833

·         Symptom: A delay exists when the device displays logs.

·         Condition: This symptom occurs if you constantly display VSI information or MAC address entries for VSIs and then display logs on the device.

202012150840

·         Symptom: Information about a MIB node with OID 1.3.6.1.4.1.25506.8.3.1.11.1.3 obtained through NMS is incorrect.

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

¡  The device is configured to perform an NQA operation.

¡  NMS is used to obtain information about the MIB node with OID 1.3.6.1.4.1.25506.8.3.1.11.1.3.

202012150849

·         Symptom: The system generates a large number of core files when an EPS scanner module scans devices in the management network.

·         Condition: This symptom might occur when an EPS scanner module scans devices in the management network.

202012150848

·         Symptom: In an IRF fabric, multicast group members cannot receive multicast traffic when a master/subordinate switchover is performed.

·         Condition: This symptom occurs if the members join the multicast group through the master device.

202009120190

·         Symptom: On the Oasis platform, the topology recalculation function fails to work.

·         Condition: This symptom might occur when the Recalculate button is clicked.

202006301536

·         Symptom: The RA guard policy applied to a VLAN does not take effect.

·         Condition: This symptom occurs if an RA guard policy is configured and applied to a VLAN.

202006301448

·         Symptom: Packet filter fails to apply a Layer 2 ACL to the incoming traffic on a port when the table capacity mode is set to 5, the 2304 ingress ACL mode.

·         Condition: This symptom occurs when the table capacity mode is set to 2304 ingress ACL mode by using the switch-mode 5 command.

202004271236

·         Symptom: In a VXLAN network, the device cannot generate complete SIP session entries.

·         Condition: This symptom occurs if you view SIP session entries in a VXLAN network.

202010231016

·         Symptom: Multicast data packets are lost.

·         Condition: This symptom might occur if a large number of receivers exist and some receivers leave the original multicast group and join another multicast group.

202008110678

·         Symptom: When a 10-Gbps fiber port on the device is connected to a third-party DCI device, the peer port cannot come up.

·         Condition: This symptom occurs if a 10-Gbps fiber port on the device is connected to a third-party DCI device.

202005091477

·         Symptom: In a VXLAN network, a MAC address fails to be moved.

·         Condition: This symptom occurs if only one or a small number of packets are sent after the MAC address moves to a new interface.

202004170866

·         Symptom: The CPU usage is high.

·         Condition: This symptom occurs if DRNI and port security are configured.

201803080642

·         Symptom: When the device receives a large amount of Layer 3 traffic destined for an IP address of the device, IPv4 and IPv6 SSH/Telnet connections cannot be established.

·         Condition: This symptom occurs if SSH/Telnet is enabled on the device and the device receives a large amount of Layer 3 traffic destined for an IP address of the device.

202004010169

·         Symptom: Some multicast data packets get lost on a Layer 2 multicast network.

·         Condition: This symptom might occur if an IGMP snooping-enabled Layer 2 device is configured with more than 1530 simulated hosts for different multicast groups.

201901280489

·         Symptom: A tier-2 PEX cannot come online.

·         Condition: This symptom occurs if the following conditions exist in an IRF 3.1 system:

a.    The master device is a multichassis IRF fabric.

b.    The tier-1 PEX is an IRF fabric.

c.    The tier-2 PEX is an S5560X-EI switch.

d.    The parent devices are rebooted to perform a master/subordinate switchover for the master device.

201808240515

·         Symptom: The authentication server is configured to issue an authorization user profile that contains the inbound rate limit to MAC authentication users. The MAC authentication users can come online, but the inbound rate limit does not take effect.

·         Condition: This symptom might occur if the authentication server is configured to issue an authorization user profile that contains the inbound rate limit to MAC authentication users.

202007010328

·         Symptom: When MAC Information is enabled globally, the mac-address information enable added command setting does not take effect on interfaces.

·         Condition: This symptom occurs if MAC Information is enabled both globally and on interfaces and the MAC learning limit is set on MAC Information-enabled interfaces.

202006290368

·         Symptom: The DHCP snooping module does not synchronize its snooping entry information to the IP source guard module after a user comes online.

·         Condition: This symptom occurs when DHCP snooping is enabled and a user comes online.

202006231151

·         Symptom: OSPF sends trap messages. This implementation is not compliant with RFC.

·         Condition: This symptom might occur when the OSPF device receives Type-5 LSAs containing larger router IDs than the local device and the same prefixes as existing Type-5 LSAs.

202006230467

·         Symptom: Idle MAC authentication users are not logged off after MAC authentication offline detection is enabled.

·         Condition: This symptom occurs if MAC authentication offline detection is enabled for users on an aggregate interface and the offline detect timer is set.

202006111432

·         Symptom: The uplink port of a secondary VLAN cannot receive packets after the ports in another secondary VLAN are isolated.

·         Condition: This symptom occurs if the following operations have been performed:

a.    Add a downlink port to a secondary VLAN associated with a primary VLAN, and add another port to a secondary VLAN associated with another primary VLAN.

b.    Configure port isolation at Layer 2 in each secondary VLAN.

c.    Cancel port isolation at Layer 2 for one secondary VLAN.

202006101032

·         Symptom: The device cannot assign users to the 802.1X Auth-Fail VSI on an interface after the users fail 802.1X authentication on the interface.

·         Condition: This symptom occurs if EAD assistant is enabled on the device.

202005120257

·         Symptom: In a VXLAN network with Layer 2 multicast configured, when an AC receives a PIM hello message, the local and remote multicast members each receive two PIM hello messages.

·         Condition: This symptom occurs when an AC in a VXLAN network with Layer 2 multicast configured receives a PIM hello message.

202005120193

·         Symptom: The license for unified wired and wireless access control on the device does not take effect after the device software version is upgraded to F6510.

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

a.    The license for unified wired and wireless access control is installed on a device running F6510.

b.    The software version is reverted to F6509L01.

c.    The software version is upgraded to F6510.

202005110902

·         Symptom: The EXP field in an MPLS packet was lost after the packet was label swapped.

·         Condition: This symptom occurs if MPLS is configured and the device performs a label swap operation for MPLS packets.

202005110834

·          

·         Symptom: The switch does not support critical VLANs or critical VSIs for wireless access after loading the unified wired and wireless access control package.

·         Condition: This symptom might occur after the switch loads the unified wired and wireless access control package.

202005060378

·         Symptom: Port flapping occurs because the device cannot detect the transceiver module of the port.

·         Condition: This symptom might occur if you quickly remove and then insert the transceiver module for the port.

202004281103

·         Symptom: When both MAC authentication and Web authentication are configured, the device cannot trigger Web authentication for a user after the user fails MAC authentication.

·         Condition: This symptom occurs if the user fails MAC authentication because the authentication domain does not exist.

202004231113

·         Symptom: ACL resources are not sufficient for the system to deploy all IP source guard binding entries.

·         Condition: This symptom occurs in the DHCPv6+SLAAC application scenario where IP source guard binding entries are to be deployed.

202004221424

·         Symptom: It takes time for the DHCP and DHCPv6 clients to obtain IP addresses.

·         Condition: This symptom occurs if many-to-one VLAN mappings are configured on the downlink interface of the device.

202004210011

·         Symptom: A DHCPv6 client cannot obtain an IPv6 address.

·         Condition: This symptom occurs if many-to-one VLAN mapping is configured on the downlink port connecting to the DHCPv6 client.

202004150339

·         Symptom: On a DR system, one DR member device cannot ping a device that is attached to the other DR member device through a single-homed AC.

·         Condition: This symptom might occur if IPv6 addresses of the same subnet are assigned to VLAN interfaces on the DR member devices.

202002180815

·         Symptom: Dynamically learned MAC address entries are not removed from a downlink interface on a leaf device when MAC authentication is enabled on the downlink interface.

·         Condition: This symptom occurs if the MAC address entries have been learned on the downlink interface before MAC authentication is enabled and the leaf device belongs to an AD-Campus network.

202002170544

·         Symptom: An interface on an LSWM2ZSP8P interface card might fail to come up.

·         Condition: This symptom occurs if an LSWM2ZSP8P interface card is installed in the device and uses Hisense 25-G optical fibers.

201910310324

·         Symptom: In an EVPN network, an IRF fabric VTEP receives duplicate packets from a multihomed site within 20 seconds after the IRF fabric starts up.

·         Condition: This symptom might occur if a master/subordinate switchover is performed when the IRF fabric is forwarding traffic to the multihomed site.

201910220598

·         Symptom: The hash conflict entries are incorrectly recorded.

·         Condition: This symptom occurs if traffic is received at a low speed.

201910180019

·         Symptom: When a guest user is configured on the device and a description is configured for the user, the guest user description fails to be modified through importing a configuration file. 

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

¡  A guest user is configured on the device.

¡  A description is configured for the user.

¡  The guest user description is modified through importing a configuration file.

201907150221

·         Symptom: On an IRF fabric configured with local port mirroring, the rate of mirrored packets is different from the rate of original packets.

·         Condition: This symptom might occur if multirate cards are installed into the IRF fabric and the source port and the monitor port reside on different slots.

201907030509

·         Symptom: On a multihomed EVPN VXLAN or EVPN VPLS network, the remote VTEP or PE is a two-chassis IRF fabric. After a master/subordinate switchover, the IRF fabric cannot forward known Layer 2 unicast traffic from an AC on the IRF subordinate device.

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

¡  One port on each IRF member device connects to a tester, and both of the ports are added to a static aggregation group and the aggregate interface is used as the AC.

¡  After the master/subordinate switchover, the underlay link for Layer 3 EVPN intercommunication connects to the IRF master device.

201906141063

·         Symptom: The IRF fabric splits.

·         Condition: This symptom might occur after the master device is rebooted.

201901280485

·         Symptom: A tier-1 cascade port flaps after a master/subordinate switchover is performed in the parent fabric.

·         Condition: This symptom occurs if S10500 switches are used as parent devices and the parent fabric connects a large number of PEXs.

201901240569

·         Symptom: The master device is restarted again during the restart process and the IRF fabric might split after the master device restarts.

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

¡  A large number of MAC authentication users and 802.1X users come online.

¡  A large number of global ACLs are configured.

Resolved problems in R6510P02

202010150768

·         Symptom: The device reboots unexpectedly.

·         Condition: This symptom occurs if an ACL contains multiple port range rules and multiple class-behavior associations using the ACL are bulk issued.

202010160355

·         Symptom: When you operate a device, the device gets stuck or its IRF fabric splits.

·         Condition: This symptom occurs if the following conditions exist:
A port that is not up on the device is connected to a Lenovo server of a specific model through a transceiver module.
The connected port on the server side continuously sends instable optical signals.

202009180912

·         Symptom: Traffic sent out of a local AC interface carries two layers of VLAN tags.

·         Condition: This symptom occurs if traffic is sent from an AC interface to another local AC interface and the AC interface is configured to match frames that are tagged with the specified outer 802.1Q VLAN tag.

202010281117

·         Symptom: A VM cannot come online.

·         Condition: This symptom occurs if a switch is attached to the device as a VM and the device receives ARP packets from the VM.

202010150794

·         Symptom: The CPU usage of the SOFT task is high.

·         Condition: This symptom occurs if a transceiver module is inserted into the device after the device is started.

202010220299

·         Symptom: Pass-through RA packets cannot be transparently transmitted.

·         Condition: This symptom occurs if the device acts as an access device and receives pass-through RA packets.

202010281129

·         Symptom: The device reboots unexpectedly repeatedly.

·         Condition: This symptom occurs if the controller fails to deploy the automation configuration and the device cannot recognize the device.csv file in a VCF fabric network.

Resolved problems in R6510

201907220915

·         Symptom: Memory leak might occur with a low probability to the DRMACD module.

·         Condition: This symptom occurs if the device has been running with full load for a long period of time in a DRNI network.

201909300697

·         Symptom: The HA batch backup process takes more than 10 minutes after an IRF fabric merge caused by shutting down and then bringing up the IRF physical interfaces on the master device.

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

a.    The IRF fabric acts as a VTEP in an EVPN+ES network, and the master device has a lower priority than the subordinate device.

b.    The IRF fabric processes a large number of multicast join messages and multicast data messages.

202006220117

·         Symptom: After a DELL server is restarted, the switch's interface connected to the DELL server cannot come up.

·         Condition: This symptom occurs if the DELL server is connected to the switch through a 10-Gbps fiber port, the fiber port comes up, and then the DELL server is restarted.

Resolved problems in F6510

202004130571

·         Symptom: The secure MAC address entries on an interface are not aged as they should be and the entry hit flag bit in the driver is always 1.

·         Condition: This symptom occurs if you enable port security globally and configure the following features on the interface:

¡  Set the port security mode to autolearn.

¡  Convert sticky MAC addresses into dynamic secure MAC addresses.

¡  Configure inactivity aging for the secure MAC addresses.

202004141417

·         Symptom: When a GRE tunnel source interface is flapping, the ecmpEnable bit of the interface's eport is incorrectly set. The ecmpEnable bit error causes traffic forwarding failure.

·         Condition: This symptom might occur if the GRE tunnel interface is used as the output interface of an IPv6 route.

202003201480

·         Symptom: The mirrored packets cannot be sent out of the reflector port.

·         Condition: This symptom occurs if Layer 2 remote port mirroring in reflector port mode is configured and a fiber port with a transceiver module or cable installed is configured as the reflector port.

·          

202003170155

·         Symptom: NetStream does not record any traffic statistics or export the statistics to the NetStream server.

·         Condition: This symptom occurs if you repeatedly execute the session-based netstream enable and undo session-based netstream enable command sequence.

202004131488

·         Symptom: Forwarding errors occur on a VXLAN network.

·         Condition: This symptom might occur if a VM migrates to a VTEP with the ipv6 nd mode uni command executed.

202004210449

·         Symptom: The Ethernet OAM remote loopback or bridging configuration does not take effect on an Ethernet interface.

·         Condition: This symptom occurs if Ethernet OAM remote loopback or bridging is enabled after the Ethernet interface is switched from a Layer 3 port to a Layer 2 port.

202003270783

·         Symptom: The device does not respond when you try to cancel the reflector port configuration.

·         Condition: This symptom occurs if Layer 2 remote port mirroring in reflector port mode is configured and the reflector port configuration is cancelled when traffic exists on the reflector port.

202004031244

·         Symptom: The DSCP value of mirrored packets is incorrect.

·         Condition: This symptom occurs if you configure the source IP address, destination IP address, and DSCP value to be encapsulated in mirrored packets when configuring the action of mirroring traffic to an interface.

202003310402

·         Symptom: The system fails to run either of the ipv6 nd detection enable and ipv6 nd suppression enable commands when underlying resources are insufficient.

·         Condition: This symptom occurs when underlying resources are insufficient and either of the ipv6 nd detection enable and ipv6 nd suppression enable commands are executed.

202003300535

·         Symptom: When an IRF physical interface is shut down by using the shutdown command on one member device, its peer IRF physical interface on the neighboring member device does not go down accordingly. Because of this issue, the IRF fabric is operating incorrectly.

·         Condition: This symptom might occur if the IRF physical interface is shut down in the following conditions:

¡  Two member devices use 100-GE ports as IRF physical interfaces, and loops exist on the IRF fabric.

¡  A broadcast storm has occurred after the member devices receive traffic with the same source MAC addresses.

202004080920

·         Symptom: All packets are counted as error packets when TWAMP is used to measure two-way metrics.

·         Condition: This symptom might occur if an interface is assigned to an aggregation group but PTP is enabled neither globally nor on this interface.

202004081302

·         Symptom: 6to4 tunnels and ISATAP tunnels cannot forward traffic.

·         Condition: This symptom occurs if you create 6to4 tunnels and ISATAP tunnels after you delete a GRE tunnel.

202004080251

·         Symptom: The DHCP clients cannot get online through the device downstream port where a many-to-one VLAN mapping is configured.

·         Condition: This symptom occurs when a many-to-one VLAN mapping is configured on the downstream port of the device.

202004140379

·         Symptom: Exception occurs in the stamgr process and a core file is produced after 802.1X users come online.

·         Condition: This symptom might occur if a large number of APs and clients come online.

202004011195

·         Symptom: An S6520X-SG-XX IRF fabric splits after it receives traffic in multiple queues on the ingress port.

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

¡  The traffic ingress and egress ports are distributed on two member devices.

¡  Rate limiting is configured in the outbound direction of the ingress port.

¡  WRED is configured to rate limit traffic of eight queues.

201901220680

·         Symptom: The information center does not receive a notification about RADIUS server recovery after the RADIUS server recovers.

·         Condition: This symptom occurs when SNMP notifications for RADIUS are enabled by using the snmp-agent trap enable radius command.

201905280859

·         Symptom: After an IRF fabric splits, a member device of an IRF fabric can display the member device information of another IRF fabric, and the interface expansion module on the member device is unstable.

·         Condition: This symptom occurs if the following operations have been performed:

a.    Use three switches to form a daisy-chain IRF fabric through interfaces on interface expansion modules.

b.    Remove and insert an interface expansion module to cause an IRF fabric split.

201908140722

·         Symptom: The maximum shared-area ratio in the display buffer queue command output is incorrect.

·         Condition: This symptom occurs if the display buffer queue command is executed after the burst mode enable command is executed.

202003121045

·         Symptom: The message that "fail to add openflow arp entry" is displayed during the startup process of a subordinate device. After the subordinate device starts up, OpenFlow rolls back the ARP entry and the OpenFlow ARP entry is deleted.

·         Condition: This symptom occurs if the outgoing interface (AC interface) of an ARP entry is on the subordinate device in a basic IPoE network and the subordinate device is rebooted after the ARP entry is successfully issued.

201812240120

·         Symptom: On an IRF fabric formed by two or more S6520X-30QC-HI switches, the CLI responds slowly if a command requires inter-member switch communication.

·         Condition: This symptom might occur if an IRF fabric is formed by two or more S6520X-30QC-HI switches

201901220819

·         Symptom: The IRF fabric cannot be accessed from the subordinate device, and the master device cannot forward packets correctly.

·         Condition: This symptom occurs if the following operations have been performed:

a.    Use multiple switches to form a ring IRF fabric.

b.    Shut down IRF physical interfaces on a member device and activate the IRF port configuration to convert the IRF fabric to a daisy-chain topology.

201908121021

·         Symptom: Red packets are still dropped though an aggregate CAR action is configured to permit red packets to pass through.

·         Condition: This symptom occurs if an aggregate CAR action is configured to permit red packets to pass through.

202002170426

·         Symptom: IPv6 multicast forwarding failed.

·         Condition: This symptom occurs if the uplink interface of the device connecting to a client is a Layer 3 Ethernet interface and configured with IPv6 PIM in an IPv6 Layer 3 multicast network.

201909251035

·         Symptom: The keepalive and IPL links flap.

·         Condition: This symptom occurs if the STP topology changes in a DRNI network that is forwarding traffic.

201812120778

·         Symptom: In an S6520X-30QC-HI IRF fabric, the communication between the master device and the subordinate devices is rather slow.

·         Condition: This symptom might occur if the master device and the subordinate devices communicate with each other.

Resolved problems in F6509L01

201905160120

·         Symptom: Traffic is interrupted for about 15 seconds when a member device in a DR system is rebooted.

·         Condition: This symptom might occur if a member device is rebooted in a DR system that acts as a gateway.

201910210749

·         Symptom: After a master/subordinate switchover, an IRF fabric cannot be re-formed.

·         Condition: This symptom occurs after a master/subordinate switchover.

201909160347

·         Symptom: Packets match only the ACL in a PBR policy, but not IPSG bindings.

·         Condition: This symptom occurs if both PBR and IP source guard are configured on an interface.

202003120622

·         Symptom: The private VLANs cannot communicate with each other.

·         Condition: This symptom occurs if the following conditions exist on an IRF fabric:

¡  Configure a multi-device aggregate interface as a downlink interface.

¡  In each secondary VLAN, enable Layer 2 isolation for ports.

¡  Shut down and bring up the aggregate interface.

202003120319

·         Symptom: The device reboots unexpectedly.

·         Condition: This symptom occurs if the authorization ACL is modified for online 802.1X users.

202003100892

·         Symptom: The packet filtering configuration on a VLAN interface might change from taking effect globally to taking interface on an interface with a low probability.

·         Condition: This symptom occurs if a VLAN interface is configured with packet filtering and the device repeatedly rolls back the configuration.

202003120433

·         Symptom: Ports are isolated at Layer 2 in another VLAN.

·         Condition: This symptom occurs if Layer 2 isolation is configured for a secondary VLAN and ports in the secondary VLAN permit another VLAN.

201910310234

·         Symptom: Transient multicast traffic loss occurs on the EVPN VTEPs at a multihomed site when the DFs for ACs change.

·         Condition: This symptom might occur if the DFs for ACs change at a multihomed site.

201902020121

·         Symptom: In an IRF 3.1 system, the PE CSP connection between a PEX and the parent fabric flaps after a cascade member port of the master device in the parent fabric is shut down and then brought up.

·         Condition: This symptom might occur if the PEX connects to the parent fabric through two links.

Resolved problems in F6508

201909111019

·         Symptom: Packets in the Layer 3 channel might be dropped, which causes Layer 3 forwarding failure.

·         Condition: This symptom occurs if the rate limit value is low for the Layer 3 channel in an IRF 3.1 system.

·         Workaround: This problem has been resolved.

201910291091

·         Symptom: An ACL fails to be issued in the driver and does not take effect.

·         Condition: This symptom occurs if a subnet is configured in an object group and then an ACL referencing the object group is issued.

·         Workaround: None.

201811160304

·         Symptom: Traffic cannot be forwarded from the local end to the remote end.

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

¡  A 10-Gbps interface on an S6520X switch has a 10-Gbps transceiver module installed and is connected to the remote end through a single fiber.

¡  The local end acts as the transmitter, and the remote end acts as the receiver.

¡  Interfaces at both ends are forcibly brought up by using the port up-mode command.

·         Workaround: None.

201812250331

·         Symptom: In an EVPN network, the whole IRF fabric reboots unexpectedly.

·         Condition: This symptom occurs if an IRF fabric formed by S6520X switches acts as a leaf device, and the undo vxlan ip-forwarding command is executed and VSIs and tunnels are configured on the IRF fabric.

·         Workaround: None.

201910310312

·         Symptom: In a multihoming EVPN network, the ARP packets received by a BDF from an AC is forwarded back to the ES through the DF.

·         Condition: This symptom occurs if ARP flood suppression is configured on a VSI.

·         Workaround: None.

201910310420

·         Symptom: After an ARP attack entry ages out, the corresponding blackhole MAC address entry cannot be deleted from the driver.

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

¡  An AC interface configured with a static AC matching untagged packets detects an ARP attack.

¡  The link type of the AC interface is switched between access and trunk with different PVIDs.

¡  After the attack stops, the generated ARP attack entry ages out.

201807270579

·         Symptom: When you execute the issu run switchover command after upgrading a subordinate IRF member device, the system prompts that the operation failed and the software cannot be upgraded successfully.

·         Condition: This symptom occurs if ISSU for multichassis IRF fabrics is not supported.

201811120193

·         Symptom: In an EVPN network, the MAC address entries displayed by using the display l2vpn mac-address and display evpn route mac local commands are inconsistent.

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

a.    An aggregate interface is configured with multiple ACs. The aggregate interface receives traffic continuously for a period of time. The ACs learn MAC address entries.

b.    Use the display l2vpn mac-address and display evpn route mac local commands to display the learned MAC address entries.

201810160530

·         Symptom: When the configured MAC learning limit is reached and the device is disabled from forwarding unknown frames after the MAC learning limit is reached, some unknown frames can still be forwarded.

·         Condition: This symptom occurs if the MAC learning limit is configured and the device is disabled from forwarding unknown frames after the MAC learning limit is reached.

201812030539

·         Symptom: When BFD MAD is configured, packets destined for UDP port 6784 or 4784 match a wrong ACL and thus are sent to the CPU.

·         Condition: This symptom might occur if the switch configured with BFD MAD receives packets with destination UDP port 6784 or 4784.

201906200802

·         Symptom: Traffic cannot be forwarded correctly between member switches of an IRF fabric.

·         Condition: This symptom might occur if the IRF fabric receives single-tagged packets after the TPID value in CVLAN tags is modified on it.

201812240093

·         Symptom: WRR queuing does not take effect on an interface when used together with rate limiting.

·         Condition: This symptom might occur if the qos lr and qos wrr weight commands are used together on an interface:

201906260861

·         Symptom: Two switches enabled with automatic configuration cannot form an IRF fabric.

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

¡  IRF physical interfaces are configured on only one of the switches during automatic configuration.

¡  The switches send LLDP packets to each other.

201905110281

·         Symptom: On an interface, a QoS policy is applied to the outbound direction to change the DSCP value of the outgoing packets, and port mirroring is configured to mirror the outgoing packets. The DSCP value of mirrored packets is not changed.

·         Condition: This symptom might occur if a QoS policy is applied to the outbound direction to change the DSCP value of the outgoing packets, and port mirroring is configured to mirror the outgoing packets on an interface.

201907180670

·         Symptom: The management Ethernet interface of the switch is displayed incorrectly.

·         Condition: This symptom occurs if the panel of the S6520X-54HC-HI or S6520X-54HC-EI switch is opened in IMC.

201907180912

·         Symptom: The IRF links forward a large number of protocol packets.

·         Condition: This symptom occurs if multiple devices form a ring-topology IRF fabric and the IRF physical interface bound to an IRF port on a member device is shut down.

201910120550

·         Symptom: The traffic is not evenly load shared among Selected member ports of an aggregation group.

·         Condition: This symptom occurs if the default load sharing mode or destination port-based load sharing mode is used and the aggregate interface receives packets with varying destination port numbers.

201905310107

·         Symptom: The status of IRF physical interfaces on a subordinate IRF member device is displayed incorrectly.

·         Condition: This symptom occurs if link flapping protection is configured on IRF physical interfaces on a subordinate IRF member device.

201909240598

·         Symptom: When a DR member device role changes to None, the keepalive link cannot come up.

·         Condition: This symptom occurs if the keepalive link is shut down and then brought up when the IPP is down in a DRNI network.

201910220923

·         Symptom: A user cannot obtain an IP address after successfully passing MAC or 802.1X authentication and coming online.

·         Condition: This symptom occurs when a user comes online after passing MAC or 802.1X authentication.

201910310404

·         Symptom: A 100-GE interface might fail to come up after the using twenty-fivegige and using hundredgige commands are repeatedly executed in sequence.

·         Condition: This symptom might occur if the following tasks are repeatedly performed in sequence:

a.    Execute the using twenty-fivegige command on the 100-GE interface.

b.    Execute the using hundredgige command on any of the 25-GE breakout interface.

201907300448

·         Symptom: In a DRNI network, residual DR system MAC address entries exist on the peer DR member device after MAC address entries are deleted on the local DR member device.

·         Condition: This symptom occurs if MAC address entries are deleted after a large number of MAC address are learned.

201910310389

·         Symptom: An access node in a VCF fabric fails to come online during automated VCF fabric deployment.

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

¡  The switch is a leaf node attached to the access node by an aggregate link that is formed by two physical links.

¡  The access node sends DHCP requests in VLAN 1, and the leaf node does not forward the DHCP requests to the upstream spine node.

201910310344

·         Symptom: The data link layer state of a shutdown 100-GE interface changes to up when the speed or duplex command is executed on the interface.

·         Condition: This symptom might occur if the speed or duplex command is executed on the shutdown 100-GE interface.

201910310162

·         Symptom: Traffic forwarding errors occur on an IRF fabric.

·         Condition: This symptom might occur if the IRF fabric adds outer VLAN tags to double-tagged packets based on a QoS policy.

201908120562

·         Symptom: On an IRF fabric, errors occur when traffic received on one IRF member switch is forwarded through another IRF member device.

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

¡  The TPID value in CVLAN tags is set to a value other than 0x8100 on an interface.

¡  The interface permits VLAN 1.

¡  The interface receives traffic with an outermost TPID value the same as the set one.

201906140873

·         Symptom: The status of the authorization ACL for online MAC portal authentication users displayed on the device is incorrect.

·         Condition: This symptom might occur if multiple online MAC portal authentication users exist on an interface and a rule unsupported by the device is added to the authorization ACL of the users.

201905050083

·         Symptom: During a radar ping, probe packets are discarded on the source device.

·         Condition: This symptom might occur if the controller uses 0-0-1 as the source MAC address of probe packets.

201911070038

·         Symptom: ARP broadcast storms occur and the DR keepalive link of a DR system flaps.

·         Condition: This symptom might occur if the destination and source IP addresses of DR keepalive packets are the IP addresses of VLAN interfaces and a Layer 2 loop exists between a DR member device and other devices.

201911060007

·         Symptom: The actual packet rate is slightly lower than the rate limit in traffic policing settings.

·         Condition: This symptom might occur if traffic policing is configured by using the MQC approach.

·         Workaround: Set the rate limit to a value slightly greater than the expected value. For example, to limit the rate to 10 Mbps, set the rate limit to 11 Mbps.

201911050693

·         Symptom: Packets on an aggregate interface are not distributed among Selected member ports of the aggregation group.

·         Condition: This symptom might occur if the aggregate interface is configured to distribute packets based on source MAC addresses and the aggregate interface receives packets from different MAC addresses.

201910310425