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
Enforce MAC address regeneration when transferring a virtual machine between vCenter Server
instances by using the virtual machine files from a datastore.
a Power off a virtual machine, remove it from the inventory, and in its configuration file (.vmx), set
the ethernetX.addressType parameter to generated.
X next to ethernet stands for the sequence number of the virtual NIC in the virtual machine.
b Import the virtual machine from one vCenter Server system to another by registering the virtual
machine from a datastore in the target vCenter Server.
The virtual machine files can reside in a datastore that is shared between the two vCenter Server
instances or can be uploaded to a datastore that is accessible only from the target vCenter Server
system.
For information about registering a virtual machine from a datastore, see vSphere Virtual Machine
Administration.
c Power on the virtual machines for the first time.
While the virtual machine is starting up, an information icon appears on the virtual machine in the
vSphere Web Client.
d Right-click the virtual machine and select Guest OS > Answer Question.
e Select the I Copied It option.
The target vCenter Server re-generates the MAC address of the virtual machine. The new MAC address
starts with the VMware OUI 00:0c:29 and is based on the BIOS UUID of the virtual machine. The BIOS
UUID of the virtual machine is calculated from the BIOS UUID of the host.
n
If the vCenter Server and hosts are version 6.0 and later and the vCenter Server instances are connected
in Enhanced Linked Mode, migrate virtual machines by using vMotion across vCenter Server systems.
When a virtual machine is migrated across vCenter Server systems, the source vCenter Server adds the
MAC address of the virtual machine to a blacklist and does not assign them to other virtual machines.
Attempt to Power On a Virtual Machine Fails Due to a MAC Address Conflict
After you set a certain static MAC address to a virtual machine adapter you cannot power on the virtual
machine.
Problem
In the vSphere Web Client, after you assign a MAC address within the range 00:50:56:40:YY:ZZ –
00:50:56:7F:YY:ZZ to a virtual machine, attempts to power the virtual machine on fail with a status message
that the MAC address is in conflict.
00:50:56:XX:YY:ZZ is not a valid static Ethernet address. It
conflicts with VMware reserved MACs for other usage.
Cause
You attempt to assign a MAC address which starts with the VMware OUI 00:50:56 and is within the
address range allocated for host VMkernel adapters on the vCenter Server system.
Solution
If you want to preserve the VMware OUI prefix, set a static MAC address within the range
00:50:56:00:00:00 – 00:50:56:3F:FF:FF. Otherwise, set an arbitrary MAC address whose prefix is different
from the VMware OUI one. For information about the ranges available for static MAC addresses that have
the VMware OUI prefix, see the vSphere Networking documentation.
vSphere Troubleshooting
80 VMware, Inc.