6.0.1
Table Of Contents
- vSphere Troubleshooting
- Contents
- About vSphere Troubleshooting
- Updated Information
- Troubleshooting Overview
- Troubleshooting Virtual Machines
- Troubleshooting Fault Tolerant Virtual Machines
- Hardware Virtualization Not Enabled
- Compatible Hosts Not Available for Secondary VM
- Secondary VM on Overcommitted Host Degrades Performance of Primary VM
- Increased Network Latency Observed in FT Virtual Machines
- Some Hosts Are Overloaded with FT Virtual Machines
- Losing Access to FT Metadata Datastore
- Turning On vSphere FT for Powered-On VM Fails
- FT Virtual Machines not Placed or Evacuated by vSphere DRS
- Fault Tolerant Virtual Machine Failovers
- Troubleshooting USB Passthrough Devices
- Recover Orphaned Virtual Machines
- Virtual Machine Does Not Power On After Cloning or Deploying from Template
- Troubleshooting Fault Tolerant Virtual Machines
- Troubleshooting Hosts
- Troubleshooting vSphere HA Host States
- vSphere HA Agent Is in the Agent Unreachable State
- vSphere HA Agent is in the Uninitialized State
- vSphere HA Agent is in the Initialization Error State
- vSphere HA Agent is in the Uninitialization Error State
- vSphere HA Agent is in the Host Failed State
- vSphere HA Agent is in the Network Partitioned State
- vSphere HA Agent is in the Network Isolated State
- Configuration of vSphere HA on Hosts Times Out
- Troubleshooting Auto Deploy
- Auto Deploy TFTP Timeout Error at Boot Time
- Auto Deploy Host Boots with Wrong Configuration
- Host Is Not Redirected to Auto Deploy Server
- Package Warning Message When You Assign an Image Profile to Auto Deploy Host
- Auto Deploy Host with a Built-In USB Flash Drive Does Not Send Coredumps to Local Disk
- Auto Deploy Host Reboots After Five Minutes
- Auto Deploy Host Cannot Contact TFTP Server
- Auto Deploy Host Cannot Retrieve ESXi Image from Auto Deploy Server
- Auto Deploy Host Does Not Get a DHCP Assigned Address
- Auto Deploy Host Does Not Network Boot
- Authentication Token Manipulation Error
- Active Directory Rule Set Error Causes Host Profile Compliance Failure
- Unable to Download VIBs When Using vCenter Server Reverse Proxy
- Troubleshooting vSphere HA Host States
- Troubleshooting vCenter Server and the vSphere Web Client
- Troubleshooting Availability
- Troubleshooting Resource Management
- Troubleshooting Storage DRS
- Storage DRS is Disabled on a Virtual Disk
- Datastore Cannot Enter Maintenance Mode
- Storage DRS Cannot Operate on a Datastore
- Moving Multiple Virtual Machines into a Datastore Cluster Fails
- Storage DRS Generates Fault During Virtual Machine Creation
- Storage DRS is Enabled on a Virtual Machine Deployed from an OVF Template
- Storage DRS Rule Violation Fault Is Displayed Multiple Times
- Storage DRS Rules Not Deleted from Datastore Cluster
- Alternative Storage DRS Placement Recommendations Are Not Generated
- Applying Storage DRS Recommendations Fails
- Troubleshooting Storage I/O Control
- Troubleshooting Storage DRS
- Troubleshooting Storage
- Resolving SAN Storage Display Problems
- Resolving SAN Performance Problems
- Virtual Machines with RDMs Need to Ignore SCSI INQUIRY Cache
- Software iSCSI Adapter Is Enabled When Not Needed
- Failure to Mount NFS Datastores
- VMkernel Log Files Contain SCSI Sense Codes
- Troubleshooting Storage Adapters
- Checking Metadata Consistency with VOMA
- Troubleshooting Flash Devices
- Troubleshooting Virtual Volumes
- Troubleshooting VAIO Filters
- Troubleshooting Networking
- Troubleshooting MAC Address Allocation
- The Conversion to the Enhanced LACP Support Fails
- Unable to Remove a Host from a vSphere Distributed Switch
- Hosts on a vSphere Distributed Switch 5.1 and Later Lose Connectivity to vCenter Server
- Hosts on vSphere Distributed Switch 5.0 and Earlier Lose Connectivity to vCenter Server
- Alarm for Loss of Network Redundancy on a Host
- Virtual Machines Lose Connectivity After Changing the Uplink Failover Order of a Distributed Port Group
- Unable to Add a Physical Adapter to a vSphere Distributed Switch
- Troubleshooting SR-IOV Enabled Workloads
- A Virtual Machine that Runs a VPN Client Causes Denial of Service for Virtual Machines on the Host or Across a vSphere HA Cluster
- Low Throughput for UDP Workloads on Windows Virtual Machines
- Virtual Machines on the Same Distributed Port Group and on Different Hosts Cannot Communicate with Each Other
- Attempt to Power On a Migrated vApp Fails Because the Associated Protocol Profile Is Missing
- Networking Configuration Operation Is Rolled Back and a Host Is Disconnected from vCenter Server
- Troubleshooting Licensing
- Index
Solution
To fix this condition, check the vSphere HA host states reported by vCenter Server. If hosts are identified as
partitioned, isolated, or unreachable, resolve the problem before proceeding. In some situations, you can
resolve a restart problem by reconfiguring vSphere HA on the host that vCenter Server is reporting as the
master host. However, in most situations, this step is insufficient, and you must resolve all host state
problems.
After you have addressed any host state problems, check if there are any hosts in the cluster other than the
Primary VM's that are compatible with the FT virtual machine pair. You can determine compatibility by
trying to migrate the Primary VM to other hosts. Address any incompatibilities that are discovered.
Role Switch Behavior Problems
vCenter Server can report that the Primary VM of a vSphere Fault Tolerance virtual machine pair is
powered off, but the Secondary VM is powered on.
Problem
After a failover occurs, vCenter Server might incorrectly report that the Primary VM is powered off and
registered to its original host, and that the Secondary VM is powered on and registered to its original host.
Cause
This error occurs when vCenter Server is unable to communicate with the hosts on which the Primary VM
and Secondary VM are actually running. vCenter Server reports these hosts as not responding and the
problem persists until vCenter Server is able to communicate with the hosts.
Solution
To fix this problem, resolve the networking problem that is preventing vCenter Server from communicating
with the hosts in the cluster.
Troubleshooting VM Component Protection
If you enable VM Component Protection (VMCP) for your vSphere HA cluster it provides protection against
datastore accessibility failures that can affect a virtual machine running on one of the cluster's hosts.
If the response that you have configured VMCP to make for such a failure is not executed, you should
troubleshoot to determine the cause.
VM with a Swapfile on a Local Datastore is Not Protected
VMCP might not be able to find a compatible host for a virtual machine if its swapfile is on a local datastore.
Problem
If a virtual machine has its swapfile configured to be on a host-local datastore rather than in the default
directory where the VM's configuration file resides, VMCP might not restart the VM on a healthy host if it is
affected by an All Paths Down (APD) datastore accessibility failure.
Cause
VMCP monitors the list of datastores that a virtual machine depends on, including the datastores where the
VM's configuration file, swapfile and disks reside. When an APD failure is detected on a dependent
datastore, VMCP first determines if there is another host which is compatible and has sufficient capacity to
failover the affected VM to. To determine this compatibility, VMCP considers the dependent datastores
along with other factors such as CPU and memory reservations. If a suitable host is found, VMCP
terminates the VM on the host that experienced the APD failure.
Chapter 5 Troubleshooting Availability
VMware, Inc. 49