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

Failing heartbeat datastores


What do humans usually do if they find an irregular or missing heartbeat? They consult with the doctor to cure it. When a vSphere cluster misses a heartbeat, you are required to troubleshoot it before it leads to the disaster of a failing cluster.

A vSphere host's HA management traffic is usually separated from other networks by using a dedicated management network. In a vSphere cluster, the master vSphere host uses the management network to interconnect with a slave vSphere host. The datastore heartbeat is used when a slave vSphere host fails to respond to the calls of its master host. The master host tries to establish communication using a datastore network partition and tries to find the slave host's heart beating in it. When a master vSphere host is unable to find the slave host's heart beating, it declares it to be in a failed state. Then, the master vSphere host tries to find other available slave host that can host the virtual machines of the failed slave...