Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering VMware vSphere 6.5

You're reading from   Mastering VMware vSphere 6.5 Leverage the power of vSphere for effective virtualization, administration, management and monitoring of data centers

Arrow left icon
Product type Paperback
Published in Dec 2017
Publisher Packt
ISBN-13 9781787286016
Length 598 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Authors (3):
Arrow left icon
Karel Novak Karel Novak
Author Profile Icon Karel Novak
Karel Novak
Paolo Valsecchi Paolo Valsecchi
Author Profile Icon Paolo Valsecchi
Paolo Valsecchi
Andrea Mauro Andrea Mauro
Author Profile Icon Andrea Mauro
Andrea Mauro
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Evolution of VMware vSphere Suite FREE CHAPTER 2. Design and Plan a Virtualization Infrastructure 3. Analysis and Assessment of an Existing Environment 4. Deployment Workflow and Component Installation 5. Configuring and Managing vSphere 6.5 6. Advanced Network Management 7. Advanced Storage Management 8. Advanced VM and Resource Management 9. Monitoring, Optimizing, and Troubleshooting 10. Securing and Protecting Your Environment 11. Lifecycle Management, Patching, and Upgrading 12. Business Continuity and Disaster Recovery 13. Advanced Availability in vSphere 6.5 14. Data and Workloads Protection

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

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime