Tags
This is my hobby, one that I am paid handsomely. I design and automate networks, write software, support applications, and learn all I can to be successful in that regard for my customers benefit. You should read LACP and vSphere ESXi hosts: not a very good marriage first. Dennis Lefeber does a really wonderful job of providing the. VMware viewpoint. I agree with a lot of his rationale, however, I think his argument lacks some depth I would like to provide and in doing so may change your perspective on how your build data centers. As a part of this discussion, we will together dig into the specific benefits interface bonding provides both from a technical and business-case standpoint.
But first, for those with short attention spans who only came here for the short on LACP and LBT specific to the implementation with VMware:
- Increase application performance by decreasing application latency with high-speed (line-rate) interfaces at the switch-server interconnect.
- Use LBT or LACP for it’s true business use-case: rapid failover during a failure or maintenance activities, increasing the headroom for a given interface, and decreasing transmit time between the server and switch.
- Maximize your value to your customer (the company, application and other infrastructure groups, your peers, by knowing how to turn business-cases into technical implementations.
- Remember, one-size-fits-all results in big shirts on little people or big people in little shirts. Don’t be a hardline proponent or opponent of any technology, vendor, or view. Always seek to understand the opposing viewpoint as there is probably a use-case where that fits as well.
Best of luck to the channel changers. I appreciate the click and read. For the rest of you knowledge seekers, lets dig in.
Continue reading
protocolSyntax 