> Anyway to get a VSWITCH to work with Cisco's EtherChannel? Not tested, but you'd certainly need the layer 2 microcode in the OSAs, and probably have to use Linux guests and software bridging to another VSWITCH to get the link aggregation capability for multiple adapters. The CMS-based stack doesn't have the necessary code to deal with the link aggregation necessary to really handle an Etherchannel.
> If not, how > would you go about load balancing a couple of OSAs without running any > routing protocols under VM? Incoming traffic can be balanced using equal-cost routing in the network devices. Outbound load balancing requires a routing daemon, but you could define a null interface and distribute routes only to the null interface and the local stack, which would let you use VIPA but not impact the network at large by sending routing updates. Without link aggregation, you really do need to use a routing daemon to keep everyone's idea of where things go in sync. -- db
