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

I/O control troubleshooting


In vSphere infrastructure storage, I/O usage of virtual machines can be controlled by Storage I/O control (SIOC). SIOC delivers storage I/O performance isolation of virtual machines. You can easily run important workloads using SIOC in virtualized storage infrastructure while it stops heavy I/O used virtual machines from impacting on less I/O used virtual machines. You can also allocate a preferred I/O resource for virtual machines using SIOC during bottlenecks. In addition, SIOC can be used to alleviate the poor performance of critical workloads because of I/O bottlenecks and latency in peak times. Some of the features of SIOC are as follows:

  • SIOC is disabled by default and needs to be enabled for each datastore in your vSphere infrastructure

  • It has a default latency threshold of 30 MS

  • It uses disk shares to allocate I/O queue slots

  • It does not intervene until the congestion latency threshold is reached and a percentage of the peak performance of a datastore is affected...