Book Image

VMware vSphere 6.5 Cookbook - Third Edition

By : Abhilash G B, Cedric Rajendran
Book Image

VMware vSphere 6.5 Cookbook - Third Edition

By: Abhilash G B, Cedric Rajendran

Overview of this book

VMware vSphere is a complete and robust virtualization product suite that helps transform data centers into simplified on-premises cloud infrastructures, providing for the automation and orchestration of workload deployment and life cycle management of the infrastructure. This book focuses on the latest release of VMware vSphere and follows a recipe-based approach, giving you hands-on instructions required to deploy and manage a vSphere environment. The book starts with the procedures involved in upgrading your existing vSphere infrastructure to vSphere 6.5, followed by deploying a new vSphere 6.5 environment. Then the book delves further into the procedures involved in managing storage and network access to the ESXi hosts and the virtual machines running on them. Moving on, the book covers high availability and fair distribution/utilization of clustered compute and storage resources. Finally, the book covers patching and upgrading the vSphere infrastructure using VUM, certificate management using VMCA, and finishes with a chapter covering the tools that can be used to monitor the performance of a vSphere infrastructure.
Table of Contents (18 chapters)

Creating a vSphere Standard Switch

A vSphere Standard Switch operates at the VMkernel layer. By default, a vSwitch vSwitch0 is created during ESXi installation. In this section, we will learn how to create a new vSwitch using the vSphere Web Client and also the ESXi command-line interface.

Getting ready

Before you create a Standard Switch, you will need the following details handy:

  • Name of the vSwitch: Most organizations follow a naming standard. It is essential to arrive at an accepted naming format.
  • Physical uplinks: Not all uplinks are configured to pass all traffic. It is important to make sure you identify the correct uplinks. For example, it is possible that only a fixed number of VLANs are trunked to a port the uplink...