disable flow control on VMkernel interfaces tagged for Virtual SAN traffic

iFixedIT
iFixedIT used Ask the Experts™
on
Virtual SAN has built-in congestion management, disabling flow control on VMkernel interfaces tagged for Virtual SAN traffic is recommended. I want to achieve this using ethtool. I know in ethtool, you need to set 3 parameters I,e autonegotiate, RX, TX. I just want to confirm that if I have to disable flow control on VMKernel interfaces tagged for VSAN, do all parameters needs to be set off or what?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2015

Commented:
L2 Network flow control is not L4 TCP congestion management.
To add to the mess - slow disks are called congestion in VSAN.

Unless you find printed material from vmware recommending that, general recomendation is to not change anything ever, and if you are to change - make one change at a time
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
You should have a dedicated VMKernel Portgroup for vSAN.

Author

Commented:
The environment is an POC for VSAN and currently only using 2x10 gb uplinks for management, virtual machine, vMotion and VSAN port groups. if I am not mistaken ethtool can disable flow control on uplinks. but I want to disable flow control only on the VSAN port group.

is there any way, if we can disable flow control on the vmkernel of VSAN.
VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017
Commented:
you can disable to on the network interface uplink, if it's supported by the nic driver (ethtool) otherwise use esxcli

see here

Configuring Flow Control on VMware ESXi and VMware ESX (1013413)

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial