Known Issues

The following is a list of general limitations and known issues of the various components of this MLNX-NATIVE-ESX release.

Internal Ref.

Description

3229049

Description: In Enhanced Data Path (EDP/ENS) mode, traffic does not work when using the nmlx5 async driver 4.21.71.101 with NSX Impactor v3.2 and above.

Workaround: Upgrade to 4.22.73.1004 async driver or to ESXi 8.0

Keywords: VMK Ping, NSX impactor

Discovered in Version: 4.19.71.1

2204581

Description: A mismatch between the uplink and the VF MTU values may result in CQE with error.

Workaround: Align the uplink and the VF MTU values.

Keywords: CQE, error, model 2,

Discovered in Version: 4.19.71.1

2639170

Description: Enabling netq_rss_ens module parameter (changing the value to 1) will result in PSOD.

Workaround: Do not change the default value.

Keywords: NetQ RSS for ENS

Discovered in Version: 4.19.71.1

2429623

Description: Enabling sriov_mc_isolation module parameter may result in vmknic and emulated NICs multicast and IPv6 traffic loss.

Workaround: Unset or set the module parameter to 0.

Keywords: Multicast, IPv6, SR-IOV

Discovered in Version: 4.19.71.1

2372060

Description: RDMA is not supported in the Hypervisor with ENS model 2.

Workaround: N/A

Keywords: ENS model 2, RDMA

Discovered in Version: 4.19.71.1

2139469

Description: Setting the "Allow Guest MTU Change" option in vSphere Client is currently not functional. Although guest MTU changes in SR-IOV are allowed, they do not affect the port's MTU and the guest's MTU remains the same as the PF MTU.

Workaround: N/A

Keywords: MTU, SR-IOV

Discovered in Version: 4.19.71.1

1340255

Description: ECN statistic counters accumulatorsPeriod and ecnMarkedRocePackets display wrong values and cannot be cleared.

Workaround: N/A

Keywords: nmlx5 ecn nmlxcli

Discovered in Version: 4.19.71.1

1340275

Description: ECN tunable parameter initialAlphaValue for the Reaction Point protocol cannot be modified.

Workaround: N/A

Keywords: nmlx5 ecn nmlxcli

Discovered in Version: 4.19.71.1

2430662

Description: ConnectX-6 Dx speed remains zero after port goes down and reboot is performed.

Workaround: Turn the down and then up again

Keywords: ConnectX-6 Dx, link speed

Discovered in Version: 4.19.71.1

1514289

Description: RoCE traffic may fail after vMotion when using namespace.

Workaround: N/A

Keywords: Namespace, RoCE, vMotion

Discovered in Version: 4.19.71.1

2334405

Description: Legacy SR-IOV is not supported with Model 1.

Workaround: Unset max_vfs or alternatively move to ENS model 0 or Model 2.

Keywords: SR-IOV, ENS

Discovered in Version: 4.19.71.1

2449578

Description: When in ENS mode, changing the scheduler to HCLK, may cause traffic loss.

Workaround: N/A

Keywords: ENS, HCLK scheduler

Discovered in Version: 4.19.71.1

746100

Description: The 'esxcli mellanox uplink link info -u <vmnic_name>' command reports the 'Auto negotiation' capability always as 'true'.

Workaround: N/A

Keywords: 'Auto negotiation' capability

Discovered in Version: 4.19.71.1

1068621

Description: SMP MADs (ibnetdiscover, sminfo, iblinkinfo, smpdump, ibqueryerr, ibdiagnet and smpquery) are not supported on the VFs.

Workaround: N/A

Keywords: SMP MADs

Discovered in Version: 4.19.70.1

1446060

Description: Although the max_vfs module parameter range is "0-128", due to firmware limitations, the following are the supported VFs per single port devices:

  • ConnectX-4 / ConnectX-5: up to 127

Workaround: N/A

Keywords: SR-IOV, VFs per port

Discovered in Version: 4.19.70.1

852883

Description: In stress condition ‘Watchdog’ may appear, leading to uplink going up and down.

Workaround: N/A

Keywords: uplink, watchdog

© Copyright 2023, NVIDIA. Last updated on May 23, 2023.