Book Image

vSphere High Performance Cookbook - Second Edition - Second Edition

By : Kevin Elder, Christopher Kusek, Prasenjit Sarkar
Book Image

vSphere High Performance Cookbook - Second Edition - Second Edition

By: Kevin Elder, Christopher Kusek, Prasenjit Sarkar

Overview of this book

vSphere is a mission-critical piece of software for many businesses. It is a complex tool, and incorrect design and deployment can create performance related issues that can negatively affect the business. This book is focused on solving these problems as well as providing best practices and performance-enhancing techniques. This edition is fully updated to include all the new features in version 6.5 as well as the latest tools and techniques to keep vSphere performing at its best. This book starts with interesting recipes, such as the interaction of vSphere 6.5 components with physical layers such as CPU, memory, and networking. Then we focus on DRS, resource control design, and vSphere cluster design. Next, you’ll learn about storage performance design and how it works with VMware vSphere 6.5. Moving on, you will learn about the two types of vCenter installation and the benefits of each. Lastly, the book covers performance tools that help you get the most out of your vSphere installation. By the end of this book, you will be able to identify, diagnose, and troubleshoot operational faults and critical performance issues in vSphere 6.5.
Table of Contents (17 chapters)
Title Page
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Using VM Monitoring


The VM Monitoring service, which is serviced by VMware Tools, evaluates whether each VM in the cluster is running or not. Regular heartbeats and I/O activity from the VMware Tools process will be checked by the VM Monitoring service to determine the running guest.

Sometimes, VM heartbeats or I/O activity is not received by the VM Monitoring service because the guest operating system fails or VMware Tools is not being allocated time to complete its tasks. If the VM Monitoring service does not hear those heartbeats, then it declares that the VM has failed and the VM is rebooted to restore service.

The VM Monitoring service also monitors a VM's I/O activity just to avoid unnecessary resets. If there are no heartbeats received within the failure interval, the I/O stats interval (a cluster-level attribute) is checked. The I/O stats interval (by default, 120 seconds) determines whether any disk or network activity has occurred for the VM during the previous 2 minutes. If not...