Book Image

The Complete VMware vSphere Guide

By : Mike Brown, Hersey Cartwright, Martin Gavanda, Andrea Mauro, Karel Novak, Paolo Valsecchi
Book Image

The Complete VMware vSphere Guide

By: Mike Brown, Hersey Cartwright, Martin Gavanda, Andrea Mauro, Karel Novak, Paolo Valsecchi

Overview of this book

vSphere 6.7 is the latest release of VMware's industry-leading virtual cloud platform. By understanding how to manage, secure, and scale apps with vSphere 6.7, you can easily run even the most demanding of workloads. This Learning Path begins with an overview of the features of the vSphere 6.7 suite. You'll learn how to plan and design a virtual infrastructure. You'll also gain insights into best practices to efficiently configure, manage, and secure apps. Next, you'll pick up on how to enhance your infrastructure with high-performance storage access, such as remote direct memory access (RDMA) and Persistent memory. The book will even guide you in securing your network with security features, such as encrypted vMotion and VM-level encryption. Finally, by learning how to apply Proactive High Availability and Predictive Distributed Resource Scheduler (DRS), you'll be able to achieve enhanced computing, storage, network, and management capabilities for your virtual data center. By the end of this Learning Path, you'll be able to build your own VMware vSphere lab that can run high workloads. This Learning Path includes content from the following Packt products: VMware vSphere 6.7 Data Center Design Cookbook - Third Edition by Mike Brown and Hersey Cartwright Mastering VMware vSphere 6.7 - Second Edition by Martin Gavanda, Andrea Mauro, Karel Novak, and Paolo Valsecchi
Table of Contents (21 chapters)

What is troubleshooting?

Troubleshooting (TRBL) is a complete process where you (in 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 component for 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 failed, for example, with a Purple Screen of Death (PSOD) error. NO! TRBL is about all problems, and you should start TRBL when there is a problem or when users report...