To explain the cause of the communication issue and provide a workaround.
This issue occurs on the Citrix Netscaler VPX load balancer because the Vmxnet3UseQueueLock is set to 1 on i4i.metal/i3en.metal.
See workaround.
Load balancing operations are interrupted when converting from i3.metal to i4i.metal/i3en.metal. New Citrix Netscaler VPX deployments using Vmxnet3 will fail to operate when deployed on i4i.metal/i3en.metal.