Aruba JH391A User guide

HPE 5940-CMW710-R2612P11 Usage Guidelines

i

HPE 5940-CMW710-R2612P11

Usage Guidelines

Keywords: Version Information, Version changed, Unresolved Problems and Avoidance Measures, List of

Solved Problems

Abstract: Provide all details about the application version file, include: Version Information, Version

changed, Unresolved Problems and Avoidance Measures, List of Solved Problems

Abbreviations:

Abbreviations

Full spelling

IRF

Intelligent Resilient Framework

AAA

Authentication, Authorization and Accounting

ARP

Address Resolution Protocol

CMW

Comware

DHCP

Dynamic Host Configuration Protocol

LACP

Link Aggregation Control Protocol

MIB

Management Information Base

MSTP

Multiple Spanning Tree Protocol

SNMP

Simple Network Management Protocol

TCP

Transmission Control Protocol

VLAN

Virtual Local Area Network

RIP

Routing Information Protocol

ECN

Explicit Congestion Notification

HPE 5940-CMW710-R2612P11 Usage Guidelines

ii

Contents

Version information ···········································································1

Version number ··························································································································· 1

Version history ···························································································································· 1

Release reason ··························································································································· 2

Restrictions and cautions ···································································2

Open problems and workarounds ························································2

List of solved problems ······································································3

Resolved problems in R2612P11 ···································································································· 3

Resolved problems in R2612P10 ···································································································· 4

Resolved problems in R2612P08 ·································································································· 10

Resolved problems in R2612P06 ·································································································· 11

Resolved problems in R2612P02 ·································································································· 24

Resolved problems in R2612P01 ·································································································· 25

Resolved problems in R2612········································································································ 29

Resolved problems in R2610········································································································ 54

Resolved problems in R2609········································································································ 59

Resolved problems in R2608P02 ·································································································· 68

Resolved problems in F2608 ······································································································ 103

Resolved problems in F2606 ······································································································ 137

Resolved problems in F2605 ······································································································ 140

Resolved problems in F2604 ······································································································ 151

Resolved problems in F2603 ······································································································ 162

Resolved problems in R2509P02 ································································································ 170

Resolved problems in R2509P01 ································································································ 179

Resolved problems in R2509······································································································ 179

Resolved problems in R2508······································································································ 188

Resolved problems in R2507······································································································ 197

Resolved problems in R2506······································································································ 203

Software upgrade guidelines ·························································· 203

HPE 5940-CMW710-R2612P11 Usage Guidelines

1

Version information

Version number

Version number (outer): HPE Comware Software, Version 7.1.070, Release 2612P11

Version number (inner): V300R009B01D024SP26

Version history

Table 1 Version history

Version

number(inner)

Version

Number(outer)

Based Version

Number

Release Date

Remark

V300R009B01D0

24SP26

5940-CMW710-R

2612P11

5940-CMW710-

R2612P10

2022-10-15

None

V300R009B01D0

24SP25

5940-CMW710-R

2612P10

5940-CMW710-

R2612P08

2021-11-15

None

V300R009B01D0

24SP23

5940-CMW710-R

2612P08

5940-CMW710-

R2612P06

2020-02-17

None

V300R009B01D0

24SP20

5940-CMW710-R

2612P06

5940-CMW710-

R2612P02

2019-10-31

None

V300R009B01D0

24SP14

5940-CMW710-R

2612P02

5940-CMW710-

R2612P01

2018-09-27

None

V300R009B01D0

24SP12

5940-CMW710-R

2612P01

5940-CMW710-

R2612

2018-08-24

None

V300R009B01D0

24SP09

5940-CMW710-R

2612

5940-CMW710-

R2610

2018-06-01

None

V300R009B01D0

24SP01

5940-CMW710-R

2610

5940-CMW710-

R2609

2017-11-30

None

V300R009B01D0

24

5940-CMW710-R

2609

5940-CMW710-

R2608P02

2017-11-24

None

V300R009B01D0

23SP02

5940-CMW710-R

2608P02

5940-CMW710-

F2608

2017-10-30

None

V300R009B01D0

21

5940-CMW710-F2

608

5940-CMW710-

F2606

2017-07-12

None

V300R009B01D0

17SP01

5940-CMW710-F2

606

5940-CMW710-

F2605

2017-04-28

None

V300R009B01D0

16SP01

5940-CMW710-F2

605

5940-CMW710-

F2604

2017-04-07

None

V300R009B01D0

15SP01

5940-CMW710-F2

604

5940-CMW710-

F2603

2017-02-28

None

V300R009B01D0

13SP01

5940-CMW710-F2

603

5940-CMW710-R

2509P02

2016-12-19

None

HPE 5940-CMW710-R2612P11 Usage Guidelines

2

Version

number(inner)

Version

Number(outer)

Based Version

Number

Release Date

Remark

V300R009B01D0

10SP03

5940-CMW710-R

2509P02

5940-CMW710-R

2509P01

2016-11-03

None

V300R009B01D0

10

5940-CMW710-R

2509P01

5940-CMW710-R

2509

2016-09-18

None

V300R009B01D0

10

5940-CMW710-R

2509

5940-CMW710-R

2508

2016-09-07

None

V300R009B01D0

08SP01

5940-CMW710-R

2508

5940-CMW710-R

2507

2016-07-29

None

V300R009B01D0

07SP02

5940-CMW710-R

2507

5940-CMW710-R

2506

2016-07-14

None

V300R009B01D0

06SP01

5940-CMW710-R

2506

First release

2016-05-30

None

Release reason

Fix bugs.

Restrictions and cautions

None.

Open problems and workarounds

201612070474

 Symptom: MACsec is enabled on interfaces of an interface card. When the interface card is

removed and re-installed, flapping occurs on other interfaces of the switch that have

established MACsec connections.

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

a. MACsec is enabled on interfaces of an interface card and other interfaces on the switch.

b. The interface card is removed and re-installed.

 Workaround: Use the following procedure to re-install the interface card:

a. Delete all MACsec settings on the interface card.

b. Remove the interface card and re-install it.

 Reconfigure MACsec on the interface card.

202110120988

 Symptom: When a MAC authentication user comes online, the user matches an incorrect ACL.

HPE 5940-CMW710-R2612P11 Usage Guidelines

3

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

a. The device performs remote MAC authentication, and the server issues ACLs.

b. Multiple MAC addresses are issued to a port and they match multiple ACLs separately.

 Workaround: Issue only one ACL to one port.

202111160136

 Symptom: A VXLAN-DCI tunnel cannot forward traffic.

 Condition: This symptom occurs if the device is upgraded from version 25XX to version

R2612P11 through ISSU.

 Workaround: Delete and reconfigure the tunnel and AC.

List of solved problems

Resolved problems in R2612P11

202209291102

 Symptom: The MACsec process is abnormal.

 Condition: This symptom occurs if the server NICs use the jumbo frame mode and the iNode

software with the MACsec function is customized on a client-oriented MACsec network.

202206240060

 Symptom: When you use the display diagnostic-information command to collect diagnostic

information, the information collected is incomplete.

 Condition: This symptom occurs if the display diagnostic-information command is used to

save diagnostic information.

202112240195

 Symptom: All dynamic MAC address entries of the device cannot age out.

 Condition: This symptom occurs if ARP entries with the same MAC address frequently move

between different ports, so the MAC address entry is frequently added and deleted on ports.

202203301472

 Symptom: The subordinate IRF member device reboots unexpectedly.

 Condition: This symptom occurs if the PTP master repeatedly changes the system time and

patches are installed and uninstalled on the subordinate IRF member device.

202112300661

 Symptom: When NETCONF is used to read the /device/base node, an error is returned.

 Condition: This symptom occurs if NETCONF is used to read the /device/base node.

HPE 5940-CMW710-R2612P11 Usage Guidelines

4

202112131411

 Symptom: When NETCONF is used to read the /api/v1/Device/Transceivers node, an error is

returned.

 Condition: This symptom occurs if NETCONF is used to read the /api/v1/Device/Transceivers

node.

Resolved problems in R2612P10

202110271360

 Symptom: CRC packets might be lost.

 Condition: This symptom occurs if 100G IRF physical interfaces are connected through cables.

202109300800

 Symptom: The return packets are not forwarded over the same path as the originating packets.

 Condition: This symptom occurs if the originating packets are MPLS packets and are

decapsulated before being forwarded at Layer 3.

202003020695

 Symptom: The system displays a message that reports incompatibility of two power modules.

 Condition: This symptom occurs if either of the following conditions exists.

 Two power modules of different models are installed on the device.

 The system fails to read information from the EEPROM of a power module.

202109300799

 Symptom: The display transceiver manuinfo command might fail to obtain the transceiver

module information with a low probability.

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

a. Use a 10KM 10-Gbps BIDI transceiver module made by XGIAG.

b. Plug and unplug the transceiver module multiple times.

202109300570

 Symptom: The last six ports of the device fail to forward packets.

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

a. Assign the first 48 10G ports to a VLAN as access ports or trunk ports. Assign one or

multiple of the last six 40G ports to the same VLAN as trunk ports.

b. Save the configuration file and reboot the device.

HPE 5940-CMW710-R2612P11 Usage Guidelines

5

202109300496

 Symptom: The Web interface does not display the interface management panel after the

Network > Interfaces > Panel or Network > Storm Constrain page is accessed.

 Condition: This symptom might occur if the Network > Interfaces > Panel or Network > Storm

Constrain page is accessed.

202109300694/202109300687

 Symptom: A user might fail to remotely log in to the switch.

 Condition: This symptom occurs if the user logs in to the switch by using SSH or Telnet.

202109300560

 Symptom: The device cannot be logged in through the console port or by using Telnet or SSH.

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

a. A non-console user logs in to the device and enters FTP client view. Then, the user exits

from the view and closes the console at the same time. After the operations, the device has

residual FTP processes.

b. Configure AAA commands on the device. AAA processes are stuck.

202109300735

 Symptom: The device reboots unexpectedly.

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

a. Access the device through SSH repeatedly.

b. Configure the device to permit SSH packets and then configure the device to deny SSH

packets repeatedly.

202109300806

 Symptom: The device cannot ping a directly connected device.

 Condition: This symptom occurs if the VXLAN hardware resource mode of the device is l2gw

and the interface connected to the interface on the directly connected device has QinQ settings.

202109300803

 Symptoms:

 No NQA operation result is available if you display the result immediately after the NQA

operation starts.

 The NQA result shows that the delay time is relatively long.

 Conditions:

 The first symptom occurs if you display the result immediately after the NQA operation

starts.

HPE 5940-CMW710-R2612P11 Usage Guidelines

6

 The second symptom occurs when a large number of NQA operations are running

simultaneously.

202109300793

 Symptom: Few MPLS packets are dropped.

 Condition: This symptom occurs if the routes are updated after session protection is enabled in

LDP view.

202109300790

 Symptom: IPC packets cannot be forwarded between IRF master and subordinate devices. The

original master device cannot join the IRF fabric after a reboot. In addition, users cannot log in

to the IRF fabric through the console port.

 Condition: This symptom might occur if the IRF physical interfaces and other common network

interfaces are flapping.

202109300722

 Symptom: The device might reboot unexpectedly.

 Condition: This symptom occurs if multiple task request MBUF resources at the same time.

202109300552

 Symptom: On the Web interface, the available member ports that can be assigned to a Layer 3

aggregation group are Layer 2 physical interfaces.

 Condition: This symptom might occur if a Layer 3 aggregate interface is modified to add

member ports to it on the Web interface.

202109151249

 Symptom: The device mistakenly reports that the memory usage reaches the early warning

threshold.

 Condition: This symptom occurs if you modify the memory alarm threshold multiple times.

202109300755

 Symptom: During cross-chassis VXLAN packet forwarding, IRF physical interfaces discard runt

frames (the packet length is less than 64 bytes), which causes incorrect statistics of runt

frames.

 Condition: This symptom might occur if a subordinate device decapsulates VXLAN packets and

then forwards the packets to the master device during cross-chassis VXLAN packet forwarding.

202110080350/202103241343

 Symptom: A VXLAN tunnel cannot forward traffic.

 Condition: This symptom occurs if the source or destination IP of the VXLAN tunnel is

repeatedly modified.

HPE 5940-CMW710-R2612P11 Usage Guidelines

7

202109300801

 Symptom: Some of the traffic between a spine device and a leaf device might be lost.

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

a. Two leaf devices form an IRF fabric. Two spine devices form an IRF fabric.

b. Connect each leaf device to the two spine devices to form a network with four uplinks and

four downlinks.

c. Execute the shutdown command on the user-side interfaces of the leaf devices.

202109300792

 Symptom: In a VXLAN network, VMs in the same subnet might fail to ping one another after

certain operations are performed.

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

a. Create an Ethernet service instance on an interface, configure the SVLAN ID match

criterion for it, and set the PVID of that interface to be the same as the SVLAN ID in the

match criterion.

b. Delete the Ethernet service instance.

c. Repeat steps a and b.

202109300788

 Symptom: The broadcast or unknown unicast packets forwarded over a VXLAN tunnel are lost.

 Condition: This symptom might occur if the VXLAN tunnel has multiple ECMP routes and the

nexthops for some of the routes flap.

202109300779

 Symptom: The switch is in an EVPN network. When receiving untagged packets from an AC,

the switch fails to send the packets to the controller.

 Condition: This symptom might occur if the VSI interfaces on the switch are assigned IPv6

addresses and the switch receives untagged packets from an AC.

202109300805

 Symptom: The traffic accounting units change from bytes and packets to only bytes in the traffic

accounting action of an applied QoS policy.

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

a. Configure two QoS policies. In the two QoS policies, associate different traffic classes with

the same traffic behavior that is configured with the traffic accounting action. The traffic

accounting action counts packets in both bytes and packets.

b. Apply one QoS policy in the inbound direction of an interface, and apply the other QoS

policy in the outbound direction of the interface.

HPE 5940-CMW710-R2612P11 Usage Guidelines

8

The traffic accounting units of the first applied QoS policy change from bytes and packets to

only bytes.

202109300794

 Symptom: On a distributed EVPN gateway, traffic is not forwarded to the expected next hop

based on a PBR policy.

 Condition: This symptom might occur if VSI interfaces receive continuous ARP request traffic.

202109300789

 Symptom: A PBR policy does not take effect on an aggregate interface after certain operations

are performed.

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

a. Apply a PBR policy to an aggregate interface and its member ports.

b. Delete the PBR policy from the aggregation member ports.

202109300749

 Symptom: Transient packet loss occurs on an interface when the undo packet-filter command

is executed to remove an ACL from the interface.

 Condition: This symptom might occur if the ACL has multiple rules and the action is set to deny

in the last rule.

202109300802

 Symptom: The device has a route, but it does not have an ARP entry for the next hop address in

the route and the device fails to ping the next hop address.

 Condition: This symptom might occur if a route with a reachable next hop address is configured

and then the next hop address is changed to another IP address.

202109300791

 Symptom: On a distributed EVPN gateway, traffic is not forwarded to the expected next hop

based on a PBR policy.

 Condition: This symptom might occur if VSI interfaces receive continuous ARP request traffic.

202109300797

 Symptom: Output from the display l2vpn mac-address command does not contain

information about some VSIs, which does not affect forwarding entry learning or traffic

forwarding.

 Condition: This symptom might occur if SPBM configuration exists.

202109300795

 Symptom: On an IRF fabric deployed with PBR policies, resources on a subordinate device are

insufficient and packet forwarding exceptions occur on the device.

HPE 5940-CMW710-R2612P11 Usage Guidelines

9

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

 Service chain rules are configured in PBR actions.

 The next hops of PBR policies are flapping.

202109300771

 Symptom: The switch cannot ping a server that is connected to an interface AC.

 Condition: This symptom might occur if an interface is removed from an aggregation group and

then configured as an AC.

202111091539

 Symptom: An ACL applied to an aggregate interface for packet filtering does not take effect.

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

 Apply an ACL with many rules to the aggregate interface. This ACL occupies the resources

of slice 6 and slice 7.

 Apply a second ACL to the aggregate interface. This ACL occupies the some resources of

slice 4.

 Delete some rules from the first applied ACL to release some resources of slice 6.

 Apply a third ACL to the aggregate interface. This ACL occupies the remaining resources of

slice 4 and the released resources of slice 6. This ACL does not take effect.

202111091536

 Symptom: uRPF cannot be enabled or disabled on an aggregate interface when the device is

operating in l2gw hardware resource mode.

 Condition: None.

202111091527

 Symptom: For a 40-GE interface manually shut down, a 10-GE transceiver module inserted into

this interface by using a 40-GE to 10-GE adapter can transmit optical signal correctly. After the

transceiver module is removed and reinstalled in the 40-GE interface, the interface comes up.

 Condition: This symptom occurs when the following operations have been performed:

a. Execute the shutdown command on the 40-GE interface.

b. Insert a 40-GE to 10-GE adapter into the 40-GE interface.

c. Insert a 10-GE transceiver module into the adapter and connect the interface to a peer

device.

d. Remove and reinstall the 10-GE transceiver module in the interface.

202111080580

 Symptom: A backup device in a VRRP group mistakenly reserves a VRRP virtual MAC address

as an interface MAC address

HPE 5940-CMW710-R2612P11 Usage Guidelines

10

 Condition: This symptom might occur if VRRP is configured to operate in non-preemptive mode

on the device and the VRRP process is restarted in a specific order.

202111121583

 Symptom: Packet statistics on VSI interfaces cannot be displayed.

 Condition: This symptom occurs if the display interface vsi-interface command is used to

display information about VSI interfaces.

Resolved problems in R2612P08

202001070563

 Symptom: Some of the traffic between a spine device and a leaf device might be lost.

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

a. Two leaf devices form an IRF fabric. Two spine devices form an IRF fabric.

b. Connect each leaf device to the two spine devices to form a network with four uplinks and

four downlinks.

c. Execute the shutdown command on the user-side interfaces of the leaf devices.

202001061065

 Symptom: The configuration file of the subordinate IRF member device is lost. As a result, the

IRF fabric fails to be established.

 Condition: This symptom occurs if one of the following conditions exists:

 Execute the save command on the device. Exit the console before the save operation is

completed.

 Execute the save command through NETCONF. Disconnect the NETCONF session before

the save operation is completed.

201912230025

 Symptom: The packet statistics for VLAN interfaces and VSI interfaces are incorrect.

 Condition: This symptom occurs if packet statistics are collected for VLAN interfaces and VSI

interfaces.

202001100912

 Symptom: Interfaces on an LSWM124XGT2Q expansion module cannot be used.

 Condition: This symptom occurs if an LSWM124XGT2Q expansion module is

unplugged/plugged or restarted.

201908120355

 Symptom: An interface cannot come up after going down.

HPE 5940-CMW710-R2612P11 Usage Guidelines

11

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

a. The interface has MACsec enabled and operates at 1 Gbps.

b. The interface goes down.

201912310648

 Symptom: The dbmd process might exit abnormally with an extremely low probability. As a

result, the configuration of the device might become empty.

 Condition: This symptom occurs if a command is repeatedly executed to view the memory

usage of the dbmd process.

Resolved problems in R2612P06

201910080441

 Symptom: Transient packet loss occurs on an interface when the undo packet-filter command is

executed to remove an ACL from the interface.

 Condition: This symptom might occur if the ACL has multiple rules and the action is set to deny

in the last rule.

201908020287

 Symptom: Some settings of a PBR policy do not take effect after the PBR policy is modified.

 Condition: This symptom might occur if the match criteria of multiple nodes are configured and

new nodes are added for the PBR policy.

201910291002

 Symptom: The vtep access port command configuration is lost on an aggregate interface.

 Condition: This symptom occurs after you modify the system name of the server after the switch

comes online through automatic deployment.

201907011027

 Symptom: After a server migrates from a DR interface to a non-DR interface on the primary

member device of a DR system, the server cannot ping the gateway attached to the DR system.

 Condition: This symptom might occur if a server migrates from a DR interface to a non-DR

interface on the primary member device of a DR system.

201902220722

 Symptom: In a VCF fabric, IP addresses are re-assigned to Loopback 0 interfaces after leaf

nodes automatically form an IRF fabric.

 Condition: This symptom might occur if the switch as a leaf node joins the IRF fabric

automatically formed by other leaf nodes.

HPE 5940-CMW710-R2612P11 Usage Guidelines

12

201909020134

 Symptom: In a VXLAN network, VMs in the same subnet might fail to ping one another after

certain operations are performed.

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

a. Create an Ethernet service instance on an interface, configure the SVLAN ID match

criterion for it, and set the PVID of that interface to be the same as the SVLAN ID in the

match criterion.

b. Delete the Ethernet service instance.

c. Repeat steps a and b.

201908260258

 Symptom: In an EVPN network with distributed gateways configured, when multiple S6800

switches join the network as leaf nodes, the EVPN service on the existing devices might be

affected.

 Condition: This symptom might occur if multiple S6800 switches are configured as leaf nodes of

an EVPN network where distributed gateways are deployed.

201908260088

 Symptom: An NMS cannot access the switch through SNMP after accessing the

hh3cTunnelVxlanIfEntry node.

 Condition: This symptom might occur if the switch has VXLAN-DCI tunnels and an NMS

accesses the hh3cTunnelVxlanIfEntry node.

201908140161

 Symptom: The switch is in an EVPN network. When receiving untagged packets from an AC,

the switch fails to send the packets to the controller.

 Condition: This symptom might occur if the VSI interfaces on the switch are assigned IPv6

addresses and the switch receives untagged packets from an AC.

201908130087

 Symptom: A VXLAN VTEP forwards the ARP packets received from a VXLAN tunnel to other

VXLAN tunnels.

 Condition: This symptom might occur if a VXLAN VTEP receives ARP packets from a VXLAN

tunnel.

201907080547

 Symptom: A peer cannot learn the management IP address of the switch through LLDP after

the LLDP process restarts on the switch.

 Condition: This symptom might occur if the LLDP process restarts on the switch.

HPE 5940-CMW710-R2612P11 Usage Guidelines

13

201907080194

 Symptom: After the qos trust dscp command is executed on an interface, the interface

modifies the 802.1p priority of outgoing packets.

 Condition: This symptom might occur if the qos trust dscp command is executed on an

interface.

201907110305

 Symptom: When MAC authentication is disabled on an interface, the MAC address entries

generated for MAC authentication are not deleted from the interface, but these entries can age

out.

 Condition: This symptom might occur if MAC authentication is disabled on the interface where

MAC authentication has been performed on users.

201907050600

 Symptom: The switch does not respond to commands issued through NETCONF.

 Condition: This symptom occurs if the commands are issued quickly without delays between

them.

201907060001

 Symptom: The switch fails IRF fabric setup when certain conditions exist.

 Condition: This symptom might occur if the following conditions exist on the switch:

 The maximum number of ECMP routes is set to a non-default value.

 When the switch is rebooted without loading a configuration file, the current maximum

number of ECMP routes is inconsistent with the value that will take effect at next startup.

201907050681

 Symptom: After the LLDP process is restarted, the vtep access port configuration on aggregate

interfaces is lost.

 Condition: This symptom occurs if the device is automatically configured and the LLDP process

is restarted.

201907050645

 Symptom: After the IRF fabric is automatically configured and then the subordinate IRF

member device is rebooted, the shutdown configuration of interfaces on the subordinate IRF

member device is lost.

 Condition: This symptom occurs if the IRF fabric is automatically configured and then the

subordinate IRF member device is rebooted.

201907050643

 Symptom: A memory leak occurs on the SNMP process.

HPE 5940-CMW710-R2612P11 Usage Guidelines

14

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

a. SNMP notifications for system logs are disabled.

b. The NMS walks the SYSLOG-MSG-MIB to obtain data.

201908120212

 Symptom: Traffic might fail to be forwarded between VXLANs.

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

c. The VCFC controller deploys configurations to spine and leaf devices.

d. On a leaf device, multiple VXLANs are configured, and a large number of VMs come online.

e. A large number of VMs migrate to other VXLANs.

201907300713

 Symptom: An interface configured with a PBR policy flaps and the PBR policy no longer takes

effect when ECMP is configured on the interface.

 Condition: This symptom might occur if ECMP is configured on an interface where a PBR policy

is applied.

201907190408

 Symptom: On an EVPN VTEP that is a member of a DR system, a MAC address flaps between

an access switch-facing DR interface and a transport-facing interface.

 Condition: This symptom might occur if the following conditions exist on the VTEP:

 The IPL is a VXLAN tunnel.

 An access switch is attached to the DR interface.

 The access switch receives ARP packets from the site attached to it.

201907050725

 Symptom: Interface flapping might cause route refresh failure and forwarding failure.

 Condition: This symptom might occur if interface flapping occurs.

 Remarks: After patch installation, shut down and bring up related interfaces to resolve this

problem.

201907050723

 Symptom: Layer 3 packets of a VSI fail to be forwarded out of a different VSI on another device.

 Condition: This symptom occurs in a distributed VXLAN IP gateway deployment.

201907050651

 Symptom: The BGP process might exit and the service is interrupted at a low probability.

HPE 5940-CMW710-R2612P11 Usage Guidelines

15

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

 ND flood suppression is configured on a VSI.

 The device receives a large number of ND packets on the corresponding AC interface,

generates ND flood suppression entries and synchronizes the entries to the remote end.

The corresponding VXLAN is repeatedly created and deleted on the remote end.

201907020286

 Symptom: A user fails MAC authentication on an interface if its MAC address has been learned

by another interface of the switch.

 Condition: This symptom might occur if a MAC authentication user accesses an interface and

its MAC address has been learned by another interface of the switch.

201908300426

 Symptom: An Ethernet fiber port installed with a transceiver module fails to come up.

 Condition: This symptom occurs with a low probability if the Ethernet fiber port is on the device

or on an interface module and has a transceiver module installed.

201908060024

 Symptom: The status of the interface on the switch becomes inconsistent with that of the peer

interface on the directly connected device after the peer interface goes down and then

immediately comes up.

 Condition: This symptom might occur if the peer interface on the directly connected device goes

down and then immediately comes up.

201907050641

 Symptom: Interface flapping might cause route refresh failure and forwarding failure.

 Condition: This symptom might occur if interface flapping occurs.

 Remarks: After patch installation, shut down and bring up related interfaces to resolve this

problem.

201909100470

 Symptom: Some VMs attached to a DRNI system have traffic loss.

 Condition: This symptom might occur if the RARP protocol packets sent by VMs are forwarded

through the IPL.

201907080567

 Symptom: Multiple Telnet users exist and cannot be deleted after certain operations are

performed.

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

a. Telnet to the switch from multiple terminals.

HPE 5940-CMW710-R2612P11 Usage Guidelines

16

b. On each terminal, execute the telnet 127.0.0.1 command multiple times and press Ctrl + K.

c. Execute the display users command on the switch.

201906280854

 Symptom: Both CLI-configured and controller-issued VSIs exist on the switch. When the

running configuration is saved and then the switch is rebooted, some CLI-configured VSIs are

lost.

 Condition: This symptom might occur if VSIs are configured both at the CLI and from the

controller and the switch is rebooted.

201902220726/201810240573

 Symptom: After the switch restarts up with the factory defaults, the DHCP server assigns the

switch a new IP address instead of the one before the restart.

 Condition: This symptom occurs if the switch restarts up with the factory defaults and acts as a

DHCP client.

201902220813

 Symptom: If VRRP groups with the same ID are configured on different VLAN interfaces, only

one of the VRRP groups takes effect.

 Condition: This symptom might occur if VRRP groups with the same ID are configured on

different VLAN interfaces.

201902220805

 Symptom: When an aggregate interface with member ports on an LSWM124XGT2Q interface

module is shut down, some interfaces on the module go down unexpectedly.

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

a. Install an LSWM124XGT2Q interface module and assign its interfaces to aggregation

groups.

b. Shut down an aggregate interface.

201902220757

 Symptom: SNMP fails to get the MAC address of an aggregate interface from the

dot1dTpFdbAddress node.

 Condition: This symptom might occur if SNMP reads the dot1dTpFdbAddress node.

201902220753/201810110532

 Symptom: After the aggregate interface of an aggregation group is assigned to an isolation

group and then is removed from it, traffic received on a member port of the aggregation group is

forwarded out of other member ports erroneously.

HPE 5940-CMW710-R2612P11 Usage Guidelines

17

 Condition: This symptom might occur if an aggregate interface is assigned to an isolation group

and then is removed from it.

201902220752/201810170605

 Symptom: In an EVPN network with distributed EVPN gateways, PBR policies do not take

effect on the border gateway.

 Condition: This symptom might occur if PBR is configured on the border gateway.

201902220749

 Symptom: After queue scheduling is configured on an interface, transient traffic loss occurs on

a non-related interface.

 Condition: This symptom might occur if queue scheduling is configured on an interface.

201902220748

 Symptom: The switch might generate dead loop logs when deleting multicast entries.

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

a. A large number of aggregate interfaces are configured, and they receive dense multicast

traffic.

b. Aggregate interfaces are shut down.

201902220745/201809280136

 Symptom: On the border gateway in an EVPN network with distributed EVPN gateways,

VRRP-enabled VLAN interfaces fail to forward untagged traffic through VXLAN tunnels.

 Condition: This symptom might occur if VRRP-enabled VLAN interfaces forward untagged

traffic through VXLAN tunnels on the border gateway.

201902220732

 Symptom: BGP sessions are interrupted.

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

a. A Layer 3 virtual interface is bound to a VPN, and a BGP neighbor relationship is

established.

b. PBR is applied to the Layer 3 virtual interface.

201902220722

 Symptom: In a VCF fabric, IP addresses are re-assigned to Loopback 0 interfaces after leaf

nodes automatically form an IRF fabric.

 Condition: This symptom might occur if the switch as a leaf node joins the IRF fabric

automatically formed by other leaf nodes.

HPE 5940-CMW710-R2612P11 Usage Guidelines

18

201902220721

 Symptom: In an EVPN network, IPv6 packets fail to be forwarded.

 Condition: This symptom occurs if the device operates in border mode (the VXLAN hardware

resource mode is set to border on the device).

201902220710/201812030086

 Symptom: Packet loss might occur.

 Condition: This symptom occurs if link-aggregation traffic redirection is configured and some

slots are rebooted.

201902220704/201812050851

 Symptom: Files in the flash might fail to be deleted at a low probability.

 Condition: This symptom occurs if multiple consoles operate the device simultaneously.

201902220698/201810100090

 Symptom: In an EVPN distributed relay system, ARP information for a user cannot be migrated

between the non-DR interfaces of the DR member devices.

 Condition: This symptom might occur if a user comes online through a non-DR interface on one

DR member device and then fails to come online through a non-DR interface on the other DR

member device.

201903131055/201903131049/201903131051

 Symptom: The PBR function might not take effect on interfaces.

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

a. PBR is configured on multiple interfaces.

b. Route flapping frequently occurs.

201903140301/201903140302/201709130770

 Symptom: Traffic might fail to be forwarded between VXLANs.

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

a. The VCFC controller deploys configurations to spine and leaf devices.

b. On a leaf device, multiple VXLANs are configured, and a large number of VMs come online.

c. A large number of VMs migrate to other VXLANs.

201908270381

 Symptom: After an 802.1X passes authentication, the issued authorization ACL does not take

effect.

 Condition: This symptom occurs if 802.1X authentication is configured and an authorization

ACL is specified.

Page is loading ...

Aruba JH391A User guide

Aruba JH391A User guide

Related papers

Other documents