Book Image

VMware vSphere Troubleshooting

Book Image

VMware vSphere Troubleshooting

Overview of this book

VMware vSphere is the leading server virtualization platform with consistent management for virtual data centers. It enhances troubleshooting skills to diagnose and resolve day to day problems in your VMware vSphere infrastructure environment. This book will provide you practical hands-on knowledge of using different performance monitoring and troubleshooting tools to manage and troubleshoot the vSphere infrastructure. It begins by introducing systematic approach for troubleshooting different problems and show casing the troubleshooting techniques. You will be able to use the troubleshooting tools to monitor performance, and troubleshoot issues related to Hosts and Virtual Machines. Moving on, you will troubleshoot High Availability, storage I/O control problems, virtual LANS, and iSCSI, NFS, VMFS issues. By the end of this book, you will be able to analyze and solve advanced issues related to vShpere environment such as vcenter certificates, database problems, and different failed state errors.
Table of Contents (16 chapters)
VMware vSphere Troubleshooting
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Installing VMware vRealize Operations Manager
Power CLI - A Basic Reference
Index

Troubleshooting paths


LUNs masking can be used to troubleshoot a storage device. To troubleshoot, you can disable storage paths temporarily for a particular vSphere host. This can save you a lot of time during troubleshooting of storage issues.

A vSphere host can declare two states about a storage device loss: All Paths Down (APD) or Permanent Device Loss (PDL). An APD signal is triggered when a storage device loses communication with a vSphere host. In this case, a vSphere host believes that the path will be restored shortly and the storage device will be reconnected.

A PDL signal is triggered once a vSphere host identifies that the I/O cannot be queued for the storage device anymore. Once the device is declared to be in a state of permanent loss, the vSphere host doesn't expect it to come back. SCSI sense codes are used by storage devices to communicate with a vSphere host so it can declare a storage device in the path's loss state and specify whether the path's losses are in the state...