Building network automation solutions

9 module online course

Start now!

Redundant Server-to-Network Connectivity

Load-based teaming and other methods of VM-to-uplink pinning used by VMware and other hypervisor vendors might be the best approach in traditional VLAN-based virtual networks. The situation changes drastically in the overlay virtual networking environment where the hypervisor sends all traffic from a single IP address, making multi-chassis link aggregation (MLAG) the best solution.

For more details, read the Redundant Server-to-Network Connectivity Expert Express case study or register for the Building a Small Private Cloud webinar.


  1. In an overlay virtual networking environment, where the hypervisor sends all traffic from a single IP address, why not do L3 all the way through, and treat each server as a router, and use the router loopback address as the endpoint IP for tunnels?
    1. While my inner networking geek agrees with you (and I was proposing this very idea in at least one blog post), the harsh reality disagrees with us:

      A) You'd lose the summarization property of IP subnets, which might haunt you in very large networks;

      B) I don't think the network or server admins would be happy to run a routing protocol (apart from BGP) between servers and routers.

      As for BGP, at least one of my customers runs BGP between server loopback and L3 switches ... have to write about that one day.
Add comment