vSphere 4.1 introduces a load-based teaming (LBT) policy that ensures vDS dvUplink capacity is optimized. LBT avoids the situation of other teaming policies in which some of the dvUplinks in a DV Port Group’s team were idle while others were completely saturated just because the teaming policy used is statically determined. LBT reshuffles port binding dynamically based on load and dvUplinks usage to make an efficient use of the bandwidth available. LBT only moves ports to dvUplinks configured for the corresponding DV Port Group’s team. Note that LBT does not use shares or limits to make its judgment while rebinding ports from one dvUplink to another. LBT is not the default teaming policy in a DV Port Group so it is up to the user to configure it as the active policy.
LBT will only move a flow when the mean send or receive utilization on an uplink exceeds 75 percent of capacity over a 30-second period. LBT will not move flows more often than every 30 seconds. This video will show Load-Based Teaming (LBT) in action.
Monday, 16 August 2010
Video - Load-Based Teaming (LBT) in action
Comments
Display comments as
(Linear | Threaded)
Nicely done Eric. This feature is going to make a lot of people happy and your demo really proves the technology works.
#1
Bill Griffith
on
2010-08-16 01:15
(Reply)
Goed gedaan! 
#2
Viktor
(Homepage)
on
2010-08-17 22:43
(Reply)
Eric Siebert over at vSphere-land has put together a new top blogger voting survey. Your votes will decide the winners and help decide the Top 25 VMware bloggers. So why should you vote for me? During the last contest which was held back in January 2010,
Tracked: Sep 14, 08:34