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

Storage log files


We will again start with the logging files as we we did in the previous chapters. The log files always provide a distinctive and systematized way of beginning troubleshooting. For storage issues, the most important vSphere host log files are hostd.log, storageRM.log, and vmkernel.log. We briefly reviewed vSphere hosts and vCenter Server log files in Chapter 1, The Methodology of Problem Solving.

The hostd.log file

The hostd.log files contain the logs of virtual machines, different events and tasks of vSphere hosts, vpxa agent, vCenter Server, and vSphere client logs. Logs related to SDK connections are also logged in these files.

The storageRM.log file

Storage I/O Control (SIOC) related problems are logged into /var/log/storagerm.log. You can check this file if SIOC is not working normally or I/O prioritization is not working for virtual machines, as expected in bottlenecks or otherwise. Sometimes you see a message stating Storage I/O control: connection with vobd failed in...