When switching was introduced in Hypervisor Layer, inter VM switching started happening locally and there was no visibility from external network. Now let me introduce two very basic concepts and those are Access port and Trunk port in a Switch. Access Continue reading Design Considerations – Virtualized Datacenter Networking
LACP is a channel having two physical switches with a single link between. But hey what happens if we add a second physical link there? Oh yes, you will get a bridging loop. However switches have inbuilt mechanisms, which is Continue reading LACP Primer – vSphere 5.5
In vSphere 5.1, LACP implementation has some constraints and those were: Supports only one LAG per VDS per host. All uplinks in the dvuplink port group are included in this LAG. Only the IP hash load balancing algorithm is supported. Continue reading Much awaited LACP enhancement – vSphere 5.5
Let me ask you this question. How many of you have seen LBT and IP Hash working together in a single VMware vDS? Interestingly enough one of my friend was working on a project that has decided to Continue reading Load Based Teaming & IP Hash – Both Together Huh !!
We are now already moving into scalable and elastic Cloud Datacenter where scalability is our main lookout and that was enough to move our self from VLAN based data center networking to VXLAN based data center networking. I will not Continue reading VXLAN Teaming Policy Trade-Off – How are you Interacting with Upstream Network
A resilient and highly available Blade design with VC and Network uplink is always desirable. Yesterday we were discussing about two design scenario. First one use the very simple network topology and rescued us from SPOF (Single Point of Failure) Continue reading N+2 Failover for a Blade Design with Upstream Switches