Book Image

Mastering VMware vSphere 6.7, - Second Edition

By : Martin Gavanda, Andrea Mauro, Paolo Valsecchi, Karel Novak
Book Image

Mastering VMware vSphere 6.7, - Second Edition

By: Martin Gavanda, Andrea Mauro, Paolo Valsecchi, Karel Novak

Overview of this book

vSphere 6.7 is the latest release of VMware’s industry-leading, virtual cloud platform. It allows organisations to move to hybrid cloud computing by enabling them to run, manage, connect and secure applications in a common operating environment. This up-to-date, 2nd edition provides complete coverage of vSphere 6.7. Complete with step-by-step explanations of essential concepts, practical examples and self-assessment questions, you will begin with an overview of the products, solutions and features of the vSphere 6.7 suite. You’ll learn how to design and plan a virtual infrastructure and look at the workflow and installation of components. You'll gain insight into best practice configuration, management and security. By the end the book you'll be able to build your own VMware vSphere lab that can run even the most demanding of workloads.
Table of Contents (22 chapters)
Free Chapter
1
Section 1: Getting Started
8
Section 2: Managing Resources
13
Section 3: Advanced Topics
18
Section 4: Building Your Lab Environment

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...