Book Image

Mastering VMware vSphere 6.5

Book Image

Mastering VMware vSphere 6.5

Overview of this book

VMware vSphere 6.5 provides a powerful, flexible and secure foundation for next-generation applications which helps you create an effective digital transformation. This book will be based on VMware vSphere 6.5 which empowers you to virtualize any complex application with ease. You’ll begin by getting an overview of all the products, solutions and features of the vSphere 6.5 suite, comparing the evolutions with the previous releases. Next ,you’ll design and plan a virtualization infrastructure to drive planning and performance analysis. Following this , you will be proceeding with workflow and installation of components. New network trends are also covered which will help you in optimally designing the vSphere environment. You will also learn the practices and procedures involved in configuring and managing virtual machines in a vSphere infrastructure. With vSphere 6.5, you’ll make use of significantly more powerful capabilities for patching, upgrading, and managing the configuration of the virtual environment. Next we’ll focus on specific availability and resiliency solutions in vSphere. Towards the end of the book you will get information on how to save your configuration, data and workload from your virtual infrastructure. By the end of the book you’ll learn about VMware vSphere 6.5 right from design to deployment and management.
Table of Contents (15 chapters)

What is troubleshooting?

Troubleshooting (TRBL) is a complete process where you (with the role of VMware administrator) identify an issue, try to find the origin of the problem, and define the way to resolve it.

The main steps involved during the troubleshooting process are therefore the following:

  1. Defining the problem
  2. Identifying the cause of the problem
  3. Resolving the problem

The complexity of VMware environments is that different layers are involved and the problem could impact any of the sources due to different reasons:

  • Hardware failures
  • Software problems
  • Network problems
  • Resources contention
  • Mistakes in configuration

A big mistake that occurs quite often, is considering TRBL only when your environment has totally failed, for example, with a Purple Screen of the Death (PSOD) error. NO! TRBL is about all problems and you should start troubleshooting when there is a problem...