Flow Control on VMware NIC Team

I noticed that in our environment, we have an inconsistency. Some of our vSwitches connected to flow-control enabled ports, while other vSwitches connected to flow-control disabled ports on the physical switches.

What is flow-control on ProCurve switches, and should it be enabled or disabled on ports connecting to VMware vSwitches?

Background Details:
Running vSphere 5.0 U1
vSwitch NIC Teaming Policy: based on source Port ID
Who is Participating?
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
It's recommended to have Flow Control Enabled.

see also here

VMware KB: Configuring Flow Control on ESX and ESXi
Nick RhodeConnect With a Mentor IT DirectorCommented:
Depends on how much congestion you have on the network.  Here is a little heads up of understanding with ESXi.

ESXi and Flow Control: http://rickardnobel.se/esxi-and-flow-control/

Its all a matter of whats all in your environment.  Are you having any latency with the VM storage?  It wont hurt to enable it and if the host is default installed you should not have to change the settings on ESXi on it.
pzozulkaAuthor Commented:
We don't think there is any latency in the environment. After reading both articles, I do see that flow-control is recommended for storage networks.

What about for all other networks connecting to the ESXi hosts (ex. vMotion, Management, Production Server VM networks, etc.)
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Always enable Flow Control, it's enabled by Default in ESXi.
Nick RhodeIT DirectorCommented:
Agree with hanccocka.  The only reason you would not want to enable Flow Control is if you had QoS already in place.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.