6.5.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 vSphere Auto Deploy
- vSphere Auto Deploy TFTP Timeout Error at Boot Time
- vSphere Auto Deploy Host Boots with Wrong Configuration
- Host Is Not Redirected to vSphere Auto Deploy Server
- Package Warning Message When You Assign an Image Profile to a vSphere Auto Deploy Host
- vSphere Auto Deploy Host with a Built-In USB Flash Drive Does Not Send Coredumps to Local Disk
- vSphere Auto Deploy Host Reboots After Five Minutes
- vSphere Auto Deploy Host Cannot Contact TFTP Server
- vSphere Auto Deploy Host Cannot Retrieve ESXi Image from vSphere Auto Deploy Server
- vSphere Auto Deploy Host Does Not Get a DHCP Assigned Address
- vSphere Auto Deploy Host Does Not Network Boot
- Recovering from Database Corruption on the vSphere Auto Deploy Server
- 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
- Troubleshooting Storage Adapters
- Checking Metadata Consistency with VOMA
- No Failover for Storage Path When TUR Command Is Unsuccessful
- 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
n
Create a port group with identical settings, make it use the valid uplink number for the host, and
migrate the virtual machine networking to the port group.
n
Move the NIC to an uplink that participates in the active failover group.
You can use the vSphere Web Client to move the host physical NIC to another uplink.
n
Use the Add and Manage Hosts wizard on the distributed switch.
a Navigate to the distributed switch in the vSphere Web Client.
b From the Actions menu select Add and Manage Hosts.
c On the Select task page, select the Manage host networking option and select the host.
d To assign the NIC of the host to an active uplink, navigate to the Manage physical network
adapters page and associate the NIC to the switch uplink.
n
Move the NIC at the level of the host.
a Navigate to the host in the vSphere Web Client, and on the Configure tab, expand the
Networking menu.
b Select Virtual Switches and select the distributed proxy switch.
c Click Manage the physical network adapters connected to the selected switch, and
move the NIC to the active uplink
Unable to Add a Physical Adapter to a vSphere
Distributed Switch That Has Network I/O Control Enabled
You might be unable to add a physical adapter with low speed, for example, 1 Gbps, to a vSphere
Distributed Switch that has vSphere Network I/O Control version 3 configured.
Problem
You try to add a physical adapter with low speed, for example, 1 Gbps, to a vSphere Distributed Switch
that is connected to physical adapters with high speed, for example, 10 Gbps. Network I/O Control
version 3 is enabled on the switch and bandwidth reservations exist for one or more system traffic types,
such as vSphere management traffic, vSphere vMotion traffic, vSphere NFS traffic, and so on. The task
for adding the physical adapter fails with a status message that a parameter is incorrect.
A specified parameter was not correct: spec.host[].backing.pnicSpec[]
Cause
Network I/O Control aligns the bandwidth that is available for reservation to the 10-Gbps speed of the
individual physical adapters that are already connected to the distributed switch. After you reserve a part
of this bandwidth, adding a physical adapter whose speed is less than 10 Gbps might not meet the
potential needs of a system traffic type.
For information about Network I/O Control version 3, see the vSphere Networking documentation.
vSphere Troubleshooting
VMware, Inc. 93