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
n
To use the flash disk as a virtual flash resource, do not claim this disk for Virtual SAN. If the disk is
claimed by Virtual SAN, remove the disk from Virtual SAN. The flash disk is released from Virtual
SAN and becomes available on the list of disks to use with virtual flash. For information about
removing disks from Virtual SAN, see the Administering VMware Virtual SAN documentation.
n
If you intend to use the flash disk with Virtual SAN, do not use the disk for a virtual flash resource. If
the flash disk is used as the virtual flash resource, remove the virtual flash configuration. The disk
becomes available for Virtual SAN. See the vSphere Storage documentation.
Another reason that makes flash disk unavailable is when ESXi cannot detect the disk. See “Local Flash
Disks Are Undetectable,” on page 71.
Keeping Flash Disks VMFS-Free with Auto-Partitioning
When you use auto-partitioning boot option when installing or auto-deploying ESXi, the auto-partitioning
option creates a VMFS datastore on your host's local storage. You have several options to keep your local
storage flash disks unformatted.
Problem
By default, auto-partitioning deploys VMFS file systems on any unused local storage disks on your host,
including flash disks.
However, a flash disk formatted with VMFS becomes unavailable for such features as virtual flash and
Virtual SAN. Both features require an unformatted flash disk and neither can share the disk with any other
file system.
Solution
To ensure that auto-partitioning does not format the flash disk with VMFS, use the following boot options
when you install ESXi or boot the ESXi host for the first time:
n
autoPartition=TRUE
n
skipPartitioningSsds=TRUE
If you use Auto Deploy, set these parameters on a reference host.
1 In the vSphere Web Client, select the host to use as a reference host and click Manage.
2 Click Settings.
3 Click System to open the system options, and click Advanced System Settings.
4 Scroll to VMkernel.Boot.autoPartition and set the value to true.
5 Scroll to VMkernel.Boot.skipPartitioningSsds and set the value to true.
6 Reboot the host.
If flash disks that you plan to use with Flash Read Cache and Virtual SAN already have VMFS datastores,
remove the datastores.
Local Flash Disks Are Undetectable
If you query for local flash disks during creation of a virtual flash resource or Virtual SAN configuration, the
ESXi host might not return a complete list of the local flash disks.
Problem
ESXi might not be able to automatically detect flash disks, or recognize them as local.
Chapter 7 Troubleshooting Storage
VMware, Inc. 71