vSphere Troubleshooting - VMware vSphere 6

1 vSphere TroubleshootingUpdate 1 VMware vSphere ESXi Server can find the most up-to-date technical documentation on the VMware website at: , Hillview Alto, CA 2010-2017 VMware , Inc. All rights reserved. Copyright and trademark TroubleshootingVMware, vSphere Troubleshooting 7 Updated Information81 Troubleshooting Overview9 Guidelines for Troubleshooting9 Identifying Symptoms10 Defining the Problem Space10 Testing Possible Solutions10 Troubleshooting with Logs112 Troubleshooting Virtual Machines 14 Troubleshooting Fault Tolerant Virtual Machines14 Hardware Virtualization Not Enabled14 Compatible Hosts Not Available for Secondary VM15 Secondary VM on Overcommitted Host Degrades Performance of Primary VM15 Increased Network Latency Observed in FT Virtual Machines16 Some Hosts Are Overloaded with FT Virtual Machines17 Losing Access to FT Metadata Datastore 17 Turning On vSphere FT for Powered-On VM Fails18FT Virtual Machines not Placed or Evacuated by vSphere DRS18 Fault Tolerant Virtual Machine Failovers19 Troubleshooting USB Passthrough Devices20 Error Message When You Try to Migrate Virtual Machine with USB Devices

2 Attached20 USB Passthrough Device Is Nonresponsive Troubleshooting 21 Cannot Copy Data From an ESXi Host to a USB Device That Is Connected to the Host21 Recover Orphaned Virtual Machines22 Virtual Machine Does Not Power On After Cloning or Deploying from Template233 Troubleshooting Hosts 25 Troubleshooting vSphere HA Host States 25vSphere HA Agent Is in the Agent Unreachable State25vSphere HA Agent is in the Uninitialized State26vSphere HA Agent is in the Initialization Error State27vSphere HA Agent is in the Uninitialization Error State28vSphere HA Agent is in the Host Failed State28vSphere HA Agent is in the Network Partitioned State 29vSphere HA Agent is in the Network Isolated State29 VMware , of vSphere HA on Hosts Times Out 30 Troubleshooting Auto Deploy31 Auto Deploy TFTP Timeout Error at Boot Time31 Auto Deploy Host Boots with Wrong Configuration31 Host Is Not Redirected to Auto Deploy Server32 Package Warning Message When You Assign an Image Profile to Auto Deploy Host32 Auto Deploy Host with a Built-In USB Flash Drive Does Not Send Coredumps to Local Disk33 Auto Deploy Host Reboots After Five Minutes33 Auto Deploy Host Cannot Contact TFTP Server34 Auto Deploy Host Cannot Retrieve ESXi Image from Auto Deploy Server34 Auto Deploy Host Does Not Get a DHCP Assigned Address35 Auto Deploy Host Does Not Network Boot36 Authentication Token Manipulation Error37 Active Directory Rule Set Error Causes Host Profile Compliance Failure 37 Unable to Download VIBs When Using vCenter Server Reverse Proxy384 Troubleshooting vCenter Server and the vSphere Web Client41

3 Troubleshooting vCenter Server41vCenter Server Upgrade Fails When Unable to Stop Tomcat Service41 Microsoft SQL Database Set to Unsupported Compatibility Mode Causes vCenter Server Installation or Upgrade to Fail42 Troubleshooting the vSphere Web Client42vCenter Server System Does Not Appear in vSphere Web Client Inventory42 Unable to Start the Virtual Machine Console 43 Unable to View the Alarm Definitions Tab of a Data Center44 Troubleshooting vCenter Server and ESXi Host Certificates44vCenter Server Cannot Connect to the Database44vCenter Server Cannot Connect to Managed Hosts45 New vCenter Server Certificate Does Not Appear to Load45 Cannot Configure vSphere HA When Using Custom SSL Certificates45 Troubleshooting vCenter Server Plug-Ins465 Troubleshooting Availability47 Troubleshooting vSphere HA Admission Control 47 Red Cluster Due to Insufficient Failover Resources 47 Unable to Power On Virtual Machine Due to Insufficient Failover Resources48 Fewer Available Slots Shown Than Expected 49 Troubleshooting Heartbeat Datastores 50 User-Preferred Datastore is Not Chosen 50 Unmounting or Removing Datastore Fails 51 Troubleshooting vSphere HA Failure Response 51vSphere TroubleshootingVMware.

4 Virtual Machine Protection State 52 Virtual Machine Restart Fails 53 Troubleshooting vSphere Fault Tolerance in Network Partitions 53 Primary VM Remains in the Need Secondary State 54 Role Switch Behavior Problems 54 Troubleshooting VM Component Protection55VM with a Swapfile on a Local Datastore is Not Protected55 Datastore Inaccessibility Is Not Resolved for a VM566 Troubleshooting Resource Management58 Troubleshooting Storage DRS 58 Storage DRS is Disabled on a Virtual Disk58 Datastore Cannot Enter Maintenance Mode 59 Storage DRS Cannot Operate on a Datastore60 Moving Multiple Virtual Machines into a Datastore Cluster Fails61 Storage DRS Generates Fault During Virtual Machine Creation61 Storage DRS is Enabled on a Virtual Machine Deployed from an OVF Template62 Storage DRS Rule Violation Fault Is Displayed Multiple Times62 Storage DRS Rules Not Deleted from Datastore Cluster 63 Alternative Storage DRS Placement Recommendations Are Not Generated63 Applying Storage DRS Recommendations Fails64 Troubleshooting Storage I/O Control64 Unsupported Host Connected to Datastore64 Unmanaged Workload Detected on Datastore65 Unable to View Performance Charts for Datastore65 Cannot Enable Storage I/O Control on Datastore657 Troubleshooting Storage 67 Resolving SAN Storage Display Problems67 Resolving Fibre Channel Storage Display Problems67 Resolving iSCSI Storage Display Problems68 Resolving SAN Performance Problems69 Excessive SCSI Reservations Cause Slow Host Performance69 Path Thrashing Causes Slow LUN Access70 Increased Latency for I/O Requests Slows Virtual Machine Performance71 Virtual Machines with RDMs Need to Ignore SCSI INQUIRY Cache75 Software iSCSI Adapter Is Enabled When Not Needed75 Failure to Mount NFS Datastores76 VMkernel Log Files

5 Contain SCSI Sense Codes76 Troubleshooting Storage Adapters77 Checking Metadata Consistency with VOMA78vSphere TroubleshootingVMware, Flash Devices80 Local Flash Devices Are Unavailable for Use with Virtual SAN or Virtual Flash80 Local Flash Disks Are Undetectable 82 Troubleshooting Virtual Volumes83 Virtual Volumes and esxcli Commands84 Virtual Datastore Is Inaccessible84 Failures When Migrating VMs or Deploying VM OVFs to Virtual Volumes Datastores84 Failed Attempts to Migrate VMs with Memory Snapshots to and from Virtual Datastores85 Troubleshooting VAIO Filters86 Handling I/O Filter Installation Failures878 Troubleshooting Networking 89 Troubleshooting MAC Address Allocation90 Duplicate MAC Addresses of Virtual Machines on the Same Network90 Attempt to Power On a Virtual Machine Fails Due to a MAC Address Conflict92 The Conversion to the Enhanced LACP Support Fails93 Unable to Remove a Host from a vSphere Distributed Switch94 Hosts on a vSphere Distributed Switch and Later Lose Connectivity to

6 VCenter Server 95 Hosts on vSphere Distributed Switch and Earlier Lose Connectivity to vCenter Server97 Alarm for Loss of Network Redundancy on a Host98 Virtual Machines Lose Connectivity After Changing the Uplink Failover Order of a Distributed Port Group99 Unable to Add a Physical Adapter to a vSphere Distributed Switch100 Troubleshooting SR-IOV Enabled Workloads101 Virtual Machine That Uses an SR-IOV Virtual Function Fails to Power On Because the Host Is Out of Interrupt Vectors101SR-IOV Enabled Workload Cannot Communicate After You Change Its MAC Address102A Virtual Machine that Runs a VPN Client Causes Denial of Service for Virtual Machines on the Host or Across a vSphere HA Cluster103 Low Throughput for UDP Workloads on Windows Virtual Machines105 Virtual Machines on the Same Distributed Port Group and on Different Hosts Cannot Communicate with Each Other107 Attempt to Power On a Migrated vApp Fails Because the Associated Protocol Profile Is Missing108 Networking Configuration Operation Is Rolled Back and a Host Is Disconnected from vCenter Server1099 Troubleshooting Licensing111 Troubleshooting Host Licensing111 Unable to Assign a License to an ESXi Host111 ESXi Host Disconnects from vCenter Server112 Unable to Power On a Virtual Machine112 Unable to Configure or Use a Feature113vSphere TroubleshootingVMware, vSphere TroubleshootingvSphere Troubleshooting describes Troubleshooting issues and procedures for vCenter Server implementations and related AudienceThis information is for anyone who wants to troubleshoot virtual machines, ESXi hosts, clusters, and related storage solutions.

7 The information in this book is for experienced Windows or Linux system administrators who are familiar with virtual machine technology and data center , InformationThis vSphere Troubleshooting is updated with each release of the product or when table provides the update history of the vSphere AUG 2020At VMware , we value inclusion. To foster this principle within our customer, partner, and internal community, we are replacing some of the terminology in our content. We have updated this guide to remove instances of non-inclusive embedded video titled " Troubleshooting Basics". See Guidelines for a new topic about Troubleshooting VIB downloads while using a custom vCenter Server reverse proxy port. See Unable to Download VIBs When Using vCenter Server Reverse , Overview1vSphere Troubleshooting contains common Troubleshooting scenarios and provides solutions for each of these problems.

8 You can also find guidance here for resolving problems that have similar origins. For unique problems, consider developing and adopting a Troubleshooting following approach for effective Troubleshooting elaborates on how to gather Troubleshooting information, such as identifying symptoms and defining the problem space. Troubleshooting with log files is also chapter includes the following topics:nGuidelines for TroubleshootingnTroubleshooting with LogsGuidelines for TroubleshootingTo troubleshoot your implementation of vSphere , identify the symptoms of the problem, determine which of the components are affected, and test possible SymptomsA number of potential causes might lead to the under-performance or nonperformance of your implementation. The first step in efficient Troubleshooting is to identify exactly what is going the Problem SpaceAfter you have isolated the symptoms of the problem, you must define the problem space.

9 Identify the software or hardware components that are affected and might be causing the problem and those components that are not Possible SolutionsWhen you know what the symptoms of the problem are and which components are involved, test the solutions systematically until the problem is Basics ( :video_vsphere_troubleshooting) VMware , SymptomsBefore you attempt to resolve a problem in your implementation, you must identify precisely how it is first step in the Troubleshooting process is to gather information that defines the specific symptoms of what is happening. You might ask these questions when gathering this information:nWhat is the task or expected behavior that is not occurring?nCan the affected task be divided into subtasks that you can evaluate separately?nIs the task ending in an error? Is an error message associated with it?nIs the task completing but in an unacceptably long time?

10 NIs the failure consistent or sporadic?nWhat has changed recently in the software or hardware that might be related to the failure?Defining the Problem SpaceAfter you identify the symptoms of the problem, determine which components in your setup are affected, which components might be causing the problem, and which components are not define the problem space in an implementation of vSphere , be aware of the components present. In addition to VMware software, consider third-party software in use and which hardware is being used with the VMware virtual the characteristics of the software and hardware elements and how they can impact the problem, you can explore general problems that might be causing the of software settingsnFailure of physical hardwarenIncompatibility of componentsBreak down the process and consider each piece and the likelihood of its involvement separately.