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
Table 7‑4. VOMA Command Options
Command Option Description
-m | --module
The module to run:
n
vmfs. This is a default option. You can check VMFS3
and VMFS 5 datastores. If you specify this module,
minimal checks are performed for LVM as well.
n
vmfsl. Check file systems that back virtual flash
volumes.
n
lvm. Check logical volumes that back VMFS datastores.
-f | --func
Functions to be performed:
n
query. List functions supported by module.
n
check. Check for errors.
n
fix. Check and fix errors.
-d | --device
Device or disk to be inspected. Make sure to provide the
absolute path to the device partition backing the VMFS
datastore. For example, /vmfs/devices/disks/naa.
00000000000000000000000000:1.
-s | --logfile
Specify the log file to output the results.
-v | --version
Display the version of VOMA.
-h | --help
Display the help message for the VOMA command.
Troubleshooting Flash Devices
vSphere uses flash drives for such storage features as Virtual SAN, host swap cache, and Flash Read Cache.
The troubleshooting topics can help you avoid potential problems and provide solutions for issues that you
might encounter when configuring flash drives.
Local Flash Devices Are Unavailable for Use with Virtual SAN or Virtual Flash
A local flash device becomes unavailable for virtual flash resource or Virtual SAN configuration when it is
formatted with VMFS or any other file system.
Problem
When you attempt to configure either Virtual SAN or virtual flash resource, a local flash disk does not
appear on the list of disks to be used.
Cause
This problem might occur when a local flash intended for use with either feature has been already formatted
with VMFS. Neither Virtual SAN nor virtual flash can share the flash disk with VMFS or any other file
system.
Also, because virtual flash and Virtual SAN are mutually exclusive consumers of flash disks, both features
cannot share the same flash disk. If the flash disk is already claimed by one feature, for example Virtual
SAN, you are not be able to use it for another, such as virtual flash, unless you release the disk.
Solution
Use only unformatted flash disks for virtual flash resource and Virtual SAN configuration.
n
Avoid formatting the flash disks with VMFS during ESXi installation or Auto Deploy.
n
If the flash disk is already formatted with VMFS, remove the VMFS datastore. For information see the
vSphere Storage documentation.
vSphere Troubleshooting
70 VMware, Inc.