Book Image

vSphere High Performance Cookbook - Second Edition - Second Edition

By : Kevin Elder, Christopher Kusek, Prasenjit Sarkar
Book Image

vSphere High Performance Cookbook - Second Edition - Second Edition

By: Kevin Elder, Christopher Kusek, Prasenjit Sarkar

Overview of this book

vSphere is a mission-critical piece of software for many businesses. It is a complex tool, and incorrect design and deployment can create performance related issues that can negatively affect the business. This book is focused on solving these problems as well as providing best practices and performance-enhancing techniques. This edition is fully updated to include all the new features in version 6.5 as well as the latest tools and techniques to keep vSphere performing at its best. This book starts with interesting recipes, such as the interaction of vSphere 6.5 components with physical layers such as CPU, memory, and networking. Then we focus on DRS, resource control design, and vSphere cluster design. Next, you’ll learn about storage performance design and how it works with VMware vSphere 6.5. Moving on, you will learn about the two types of vCenter installation and the benefits of each. Lastly, the book covers performance tools that help you get the most out of your vSphere installation. By the end of this book, you will be able to identify, diagnose, and troubleshoot operational faults and critical performance issues in vSphere 6.5.
Table of Contents (17 chapters)
Title Page
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Designing a vSphere Distributed Switch for load balancing and failover


The load balancing and failover policies are chosen so the infrastructure can have an impact on the overall design. Using NIC Teaming, we can group several physical network switches attached to a vSwitch. This grouping enables load balancing between different physical NICs and provides fault tolerance if a card or physical switch failure occurs.

A vSphere Distributed Switch offers a load balancing option that actually takes the network workload into account when choosing the physical uplink. This is route-based on a physical NIC load. This is also called Load Based Teaming (LBT). We recommend this load balancing option over others when using a distributed vSwitch. The benefits of using this load balancing policy are as follows:

  • It is the only load balancing option that actually considers NIC load when choosing uplinks
  • It does not require upstream switch configuration dependencies, like the route based on the IP hash algorithm...