As I go forward and deploy I noticed a few settings in the Security Configuration area of vSphere for these servers that looks like:
You may notice a few additions like Direct Console UI (which can bite you severely if you turn it off and need access to your console locally to reconfigure or restart networking), and the Tech Support Options are somewhat self explanatory (since VMware took their unsupported mode and made it a legit feature), however what are I/O Redirector (Active Directory Service) and LBTD...
Well I asked one of my friends and one of the most highly experienced VMware gurus that I know, SBeaver (as many of you know him www.beaverdam.net/blog) for a rundown. He had the following to say on those two items:
- I/O Redirector (Active Directory Service) - is or is related to the iSCSI Initiator
- LBTD - is part of the Host Profile Enhancements for 4.1 and is the Load Balanced Teaming Daemon
- Route based on the originating virtual Port ID
- Route based on IP hash
- Route based on source MAC hash
It appears there can still exist a condition that would result in two heavy loaded VMs congesting a physical adapter while other adapters are relatively free, and that by using the Load Balanced Teaming you can relieve this issue and also gain:
- Dynamic adjustments to load
- Different NIC speeds are taken into account. You can have a mix of 1Gbit, 10Gbit, and even 100Mbit NICs.
As for I/O Redirector (Active Directory Service) I am not finding a lot about it, so I will keep poking and divulge what I can.
On the top of the virtual mountain searching for the root of the world to see if its been /jail-ed,
-Virt