Hi, On Thu, Sep 20, 2012 at 12:13:22AM +0200, Peter Rathlev wrote: > You might not need MLAGs though. We run many stand-alone trunks from > 3750 and 3560 switches to VMware ESX hosts and let the vSwitch on the > host spread out the guests between these links and take care of > failover.
Since there seems to be more knowledge about vSwitch here than in
"vmware admin" circles... is there documentation on how vSwitch chooses
which link to activate?
It's easy if one of the physical links goes down ("do not use that!"),
but I'm thinking more about the uplink network getting partitioned, or
one of the uplink switches failing in interesting ways (link still up,
but no packets get forwarded anymore). In Linux bonding, I can do that
by having the bonding driver send out ARP requests & monitor incoming
responses...
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany [email protected]
fax: +49-89-35655025 [email protected]
pgpGNy95qSm3J.pgp
Description: PGP signature
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
