Troubleshooting Erratic vCenter Behavior Caused by Storage Issues

Products

• VMware vCenter Server

Issue/Introduction

This article addresses situations where vCenter Server exhibits unstable behavior, such as authentication errors, intermittent connection issues, or frequent restarts. These symptoms may be caused by underlying storage problems, particularly issues with the LUN hosting the vCenter Server VM.

Environment

- VMware vSphere 7.0 and newer
- vCenter Server
- ESXi hosts
- External storage arrays

Cause

Erratic vCenter behavior can sometimes be traced to storage issues, particularly problems with the LUN hosting the vCenter Server VM. Common indicators include high numbers of data write miscompares, frequent I/O errors, or other storage-related issues visible in ESXi host logs.

Resolution

1. 1.  Identify the LUN hosting the vCenter Server VM:
      1. Log into the ESXi host that runs the vCenter Server VM using SSH or the Direct Console User Interface (DCUI).
      2. Use the following command to list all VMs and their datastores:
         
         vim-cmd vmsvc/getallvms
         
         
      3. Identify the datastore where the vCenter Server VM is located.
      4. Use the following command to match the VMFS UUID with the NAA ID:
         
         esxcli storage vmfs extent list
         
         
      5. Note the NAA ID of the LUN hosting the vCenter Server VM.
         

          

   2. Examine the ESXi host logs for storage-related issues:

      1. Check the following log files for errors related to the identified LUN:
         
         /var/log/vobd.log
/var/log/vmkernel.log

      2. Look for repeated error codes, such as "0xe 0x1d 0x0". Hundreds or thousands of these indicate severe storage issues.

      3. Search for ongoing I/O errors related to the LUN.

   3. If severe storage issues are detected:

      1. Open a case with VMware Support for the GS Storage team for further analysis and guidance on interpreting error codes and log entries.

      2. Support may then advise for you to contact your storage array vendor to investigate and resolve the underlying storage problems.

   4. After addressing storage issues, assess vCenter Server health:

      1. Check vCenter Server logs for signs of corruption or data inconsistency.

      2. Look for erratic or inconsistent behaviors, such as:

         • Having to retry the same credentials repeatedly to log in

         • Needing to frequently reboot vCenter to get it to respond

         • Intermittent connection issues between vCenter and ESXi hosts

         • Unexpected service failures or restarts

      3. If these issues persist, consider rebuilding the vCenter Server from scratch.

Additional Information

VMware ESXi SCSI Sense Code Decoder