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

1671303

Description: A PSOD may occur during vMotion over ENS VMK. This issue is pending VMWare investigation.

Workaround: N/A

Keywords: ENS, vMotion

Discovered in Version: 4.17.15.16

1668029

Description: There is no Geneve traffic on NSX-T 2.3 when DVS is in standard (non- ENS) mode.

Workaround: Use NSX-T 2.2 for this scenario or use DVS in ENS mode with NSX-T 2.3

Keywords: ENS, Geneve

Discovered in Version: 4.17.15.16

1677627

Description: IPv6 as inner packet is not supported by VMWare yet. This capability will be added in next NSX-T release.

Workaround: N/A

Keywords: ENS, IPv6, Geneve

Discovered in Version: 4.17.15.16

1682956

Description: During ENS uplink detachment from the ENS DVS, the below error message regarding the queue still being allocated or that the requested queue is not in use may appear.

“Driver covers for OS issue and the messages are for information only.”

Workaround: N/A

Keywords: ENS, queue

Discovered in Version: 4.17.15.16

1712298

Description: Live unload of the driver is not supported. Doing so may cause a PSOD if the max_vfs parameter is set.

Workaround: N/A

Keywords: Driver load

Discovered in Version: 4.17.15.16

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: up to 127

  • ConnectX-5: up to 63

Workaround: N/A

Keywords: SR-IOV, VFs per port

Discovered in Version: 4.17.14.2

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.17.13.8

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.17.13.8

-

Description: The hardware can offload only up to 256B of headers.

Workaround: N/A

Keywords: Hardware offload

Discovered in Version: 4.17.13.8

781277

Description: The "esxcli network sriovnic vf stats" command is not supported.

When running this command on a vmknic, a failure message is displayed.

Workaround: N/A

Keywords: esxcli SR-IOV

Discovered in Version: 4.17.13.8

858972

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

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

1068621

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

Workaround: N/A

Keywords: SMP MADs

778371

Description: Wake-on-LAN does not notify when invalid parameters are provided.

Workaround: N/A

Keywords: WoL

778572

Description: Nested ESXi might not function properly.

Workaround: N/A

Keywords: Nested ESXi

765008

Description: Device RSS fails to hash traffic to sufficient RX rings with Broadcast traffic.

Workaround: N/A

Keywords: RSS, RX rings

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 Sep 8, 2023.