VMWARE ESXi 5.0

Creation of New -VM Files in ESX i 5.0
Files:
.hlog                           vMotion log file
.lck-XXX                    Locking file on NFS datastore
file.log                        VM activity log
file-#.log                     Old VM log
.nvram                        BIOS or EFI settings
file.rdm                       RDM in Virtual Compatibility mode
team.rdmp                 RDM in Physical Compatibility mode
memory.vmdk           Disk descriptor (also raw virtual disk for hosted products

-flat.vmdk                   Raw pre-allocated virtual disk
 -00000#.vmdk-         Snapshot child disk
 -ctk.vmdk                  Changed Block Tracking file 
-00000#-delta.vmdk Snapshot differential file
file.vmsd                    Snapshot metadata
vmsn                          Snapshot state file
.vmss                         Suspended state file
log.vmss                   Suspended state file
.vmtx                          Template header
.vmx                           Primary configuration file
.vmxf                          Extra configuration file for VMs in a team
.vswp                         Swap file for over committed memory

As simple questions for Vmware administrator?

1) How to find the log of ESX Server when Esx server is down?

2) How to get the  log information of HBA ?

3) I had upgraded the bios version  after that esx server is not running , how to find the log?

4)what is vilogger?

5) How to check the network information of esx server from a centralized place?

Use VMA server for all this solutions 

Create a snapshot but do not have enough space on the VMFS volume

Power on a virtual machine but there is not enough space to create a swap file on the VMFS volume

To change the default location:

Power off the virtual machine.

Add the following line to the VMX configuration file for the virtual machine:

workingDir=""

For example:

workingDir="/vmfs/volumes/46f1225f-552b0069-e03b-00145e808070/vm-snapshots"

To reload virtual machine configuration, run the command:

# vimsh -ne "vmsvc/reload "

When you power on the virtual machine, snapshot files and VSWP files are created in the new location.

Note: If you do not want to redirect the virtual machine’s swap file, add the following line to the VMX configuration file, then reload the configuration:

sched.swap.dir=""



When you power on the virtual machine, the swap file is created in the same directory as virtual machine.

Choosing a block size when creating VMFS datastores

When you create a VMFS datastore on your VMware ESX servers many administrators select the default 1MB block size without knowing when or why to change it. The block size determines the minimum amount of disk space that any file will take up on VMFS datastores. So an 18KB log file will actually take up 1MB of disk space (1 block) and a 1.3MB file will take up 2MB of disk space (2 blocks). But the block size also determines the maximum size that any file can be, if you select a 1MB block size on your data store the maximum file size is limited to 256GB. So when you create a VM you cannot assign it a single virtual disk greater then 256GB. There is also no way to change the block size after you set it without deleting the datastore and re-creating it, which will wipe out any data on the datastore.

Because of this you should choose your block size carefully when creating VMFS datastores. The VMFS datastores mainly contain larger virtual disk files so increasing the block size will not use all that much more disk space over the default 1MB size. You have the following choices when creating a datastore:


• 1MB block size – 256GB maximum file size

• 2MB block size – 512GB maximum file size

• 4MB block size – 1024GB maximum file size

• 8MB block size – 2048GB maximum file size


Besides having smaller files use slightly more disk space on your datastore there are no other downsides to using larger block sizes. There is no noticeable I/O performance difference by using a larger block size. When you create your datastore, make sure you choose your block size carefully. 1MB should be fine if you have a smaller datastore (less than 500GB) and never plan on using virtual disks greater then 256GB. If you have a medium (500GB – 1TB) datastore and there is a chance that you may need a VM with a larger disk then go with a 2MB or 4MB block size. For larger datastores (1TB – 2TB) go with a 4MB or 8MB block size. In most cases you will not be creating virtual disks equal to the maximum size of your datastore (2TB) so you will usually not need a 8MB block size.

 

There is no noticeable I/O performance difference by using a larger block size. When you create your datastore, make sure you choose your block size carefully. 1MB should be fine if you have a smaller datastore (less than 500GB) and never plan on using virtual disks greater then 256GB. If you have a medium (500GB – 1TB) datastore and there is a chance that you may need a VM with a larger disk then go with a 2MB or 4MB block size. For larger datastores (1TB – 2TB) go with a 4MB or 8MB block size. In most cases you will not be creating virtual disks equal to the maximum size of your datastore (2TB) so you will usually not need a 8MB block sizeVMFS Size Limitations

New Partition Tables For VMFS

SOAP

SIMPLE OBJECT ACESS PROTOCOL

The VMware Host Server (SOAP) sensor monitors a VMware host server using Simple Object Access Protocol. It shows CPU (percent) and memory (absolute) usage, disk read and write speed, and network received and transmitted speed of a VMware host server

Add Sensor

The Add Sensor dialog appears when adding a new sensor on a device manually. It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Settings tab later.

VMware Host Server Sensor Settings

On the sensor's detail page, click on the Settings tab to change settings.


Note: If not set explicitly in a sensor's settings, it will connect to the IP address or DNS name defined in the settings of the parent device the sensor is created on.


Basic Sensor Settings

Sensor Name


Enter a meaningful name to identify the sensor. The name will be shown by default in the device tree and in all alarms.

Tags: Enter one or more tags, separated by space or comma. You can use tags to group sensors and use tag-filtered views later on. Tags are not case sensitive. We recommend using the default value. You can add additional tags to it, if you like. Tags are automatically inherited.

Priority

Select a priority for the sensor. This setting determines where the sensor will be placed in sensor lists. Top priority will be at the top of a list. You can choose from one star (low priority) to five stars (top priority).

Sensor Display
Primary Channel: Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel will always be displayed underneath the sensor's name. The available options depend on what channels are available for this sensor.


Chart Type


Define how different channels will be shown for this sensor.


•Show channels independently (default) : Show an own graph for each channel.


•Stack channels on top of each other : Stack channels on top of each other to create a multi-channel graph. This will generate an easy-to-read graph which visualizes the different components of your total traffic.


Stack Unit: This setting is only available if stacked graphs are selected above. Choose a unit from the list. All channels with this unit will be stacked on top of each other. By default, you cannot exclude single channels from stacking, if they use the selected unit. However, there is an advanced procedure to do so.


Inherited Settings:  By default, all following settings are inherited from objects higher in the hierarchy and should be changed there, if necessary. Often, best practice is to change them centrally in the Root group's settings. To change a setting for this object, disable inheritance by clicking on the check mark symbol in front of the respective setting name. You will then see the options described below.


Scanning Interval
Scanning Interval: The scanning interval determines the time the sensor waits between two scans. Select a scanning interval (seconds, minutes, or hours) from the list. You can change the available intervals in the system administration.


Schedules and Dependencies
Schedule:


Select a schedule from the list. Schedules can be used to pause monitoring for a certain time span (days, hours) throughout the week. You can create new schedules and edit existing ones in the account settings. Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active.


Inherit Access Rights
User Group Access
Define which user group(s) will have access to the object you're editing. A table with user groups and right is shown; it contains all user groups from your setup. For each user group you can choose from the following access rights:


•Inherited : Use the settings of the parent object.


•None : Users in this group cannot see or edit the object. The object does not show up in lists and in the sensor tree. Exception: If a child object is visible to the user, the object is visible in the sensor tree, though not accessible.


•Read : Users in this group can see the object and review its monitoring results.


•Write : Users in this group can see the object, review its monitoring results, and edit the object's settings. They cannot edit access rights settings.


•Full : Users in this group can see the object, review its monitoring results, edit the object's settings, and edit access rights settings.


You can create new user groups in the System Administration—User Groups settings. To automatically set all objects further down in the hierarchy to inherit this object's access rights, set a check mark for the Revert children's access rights to inherited option

Types Of VMDK FILES

After a long research from Google , i found the differences of VMDK Files
vmdk files – These are the disk files that are created for each virtual hard drive in your VM. There are 3 different types of files that use the vmdk extension, they are:
*–flat.vmdk file
  *.vmdk file
*–delta.vmdk file
   *–flat.vmdk file - This is the actual raw disk file that is created for each virtual hard drive. Almost all of a .vmdk file's content is the virtual machine's data, with a small portion allotted to virtual machine overhead. This file will be roughly the same size as your virtual hard drive.

*.vmdk file – This isn't the file containing the raw data anymore. Instead it is the disk descriptor file which describes the size and geometry of the virtual disk file. This file is in text format and contains the name of the –flat.vmdk file for which it is associated with and also the hard drive adapter type, drive sectors, heads and cylinders, etc. One of these files will exist for each virtual hard drive that is assigned to your virtual machine. You can tell which –flat.vmdk file it is associated with by opening the file and looking at the Extent Description field.
 

    *–delta.vmdk file - This is the differential file created when you take a snapshot of a VM (also known as REDO log). When you snapshot a VM it stops writing to the base vmdk and starts writing changes to the snapshot delta file. The snapshot delta will initially be small and then start growing as changes are made to the base vmdk file, The delta file is a bitmap of the changes to the base vmdk thus is can never grow larger than the base vmdk. A delta file will be created for each snapshot that you create for a VM. These files are automatically deleted when the snapshot is deleted or reverted in snapshot manager

SnapShot -1

Snap Shot-2

I think it will be very help full for all the viewers............................................................

Esxcfg command help

Jump
To:
Networking: Esxcfg-firewall
Esxcfg-nics Esxcfg-vswitch
Esxcfg-vswif
Esxcfg-route
Esxcfg-vmknic

Storage: Esxcfg-mpath Esxcfg-nas Esxcfg-swisci
Esxcfg-vmhbadevs
General: Esxcfg-advcfg
Esxcfg-auth Esxcfg-info Esxcfg-resgrp Esxcfg-upgrade
Boot/Diagnostic: Esxcfg-boot Esxcfg-dumppart Esxcfg-init
Esxcfg-linuxnet Esxcfg-module
 

Esxcfg-firewall
Description: Configures the service
console firewall ports
Syntax: esxcfg-firewall <options>

Options:

-q	Lists current settings
-q <service>	Lists settings for the specified service
-q incoming|outgoing	Lists settings for non-required incoming/outgoing ports
-s	Lists known services
-l	Loads current settings
-r	Resets all options to defaults
-e <service>	Allows specified service through the firewall (enables)
-d <service>	Blocks specified service (disables)
-o <port, tcp|udp,in|out,name>	Opens a port
-c <port, tcp|udp,in|out>	Closes a port previously opened by –o
-h	Displays command help
-allowincoming	Allow all incoming ports
-allowoutgoing	Allow all outgoing ports
-blockincoming	Block all non-required incoming ports (default value)
-blockoutgoing	Block all non-required outgoing ports (default value)

Default Services:

AAMClient	Added by the vpxa RPM: Traffic between ESX Server hosts for VMware High Availability (HA) and EMC Autostart Manager – inbound and outbound TCP and UDP Ports 2050 – 5000 and 8042 – 8045
activeDirectorKerberos	Active Directory Kerberos - outbound TCPs Port 88 and 464
CIMHttpServer	First-party optional service: CIM HTTP Server - inbound TCP Port 5988
CIMHttpsServer	First-party optional service: CIM HTTPS Server - inbound TCP Port 5989
CIMSLP	First-party optional service: CIM SLP - inbound and outbound TCP and UDP Ports 427
commvaultDynamic	Backup agent: Commvault dynamic – inbound and outbound TCP Ports 8600 – 8619
commvaultStatic	Backup agent: Commvault static – inbound and outbound TCP Ports 8400 – 8403
ftpClient	FTP client - outbound TCP Port 21
ftpServer	FTP server - inbound TCP Port 21
kerberos	Kerberos - outbound TCPs Port 88 and 749
LicenseClient	FlexLM license server client - outbound TCP Ports 27000 and 27010
nfsClient	NFS client - outbound TCP and UDP Ports 111 and 2049 (0 – 65535)
nisClient	NIS client - outbound TCP and UDP Ports 111 (0 – 65535)
ntpClient	NTP client - outbound UDP Port 123
smbClient	SMB client - outbound TCP Ports 137 – 139 and 445
snmpd	SNMP services - inbound TCP Port 161 and outbound TCP Port 162
sshClient	SSH client - outbound TCP Port 22
sshServer	SSH server - inbound TCP Port 22
swISCSIClient	First-party optional service: Software iSCSI client - outbound TCP Port 3260
telnetClient	NTP client - outbound TCP Port 23
TSM	Backup agent: IBM Tivoli Storage Manager – inbound and outbound TCP Ports 1500
veritasBackupExec	Backup agent: Veritas BackupExec – inbound TCP Ports 10000 – 10200
veritasNetBackup	Backup agent: Veritas NetBackup – inbound TCP Ports 13720, 13732, 13734, and 13783
vncServer	VNC server - Allow VNC sessions 0-64: inbound TCP Ports 5900 – 5964
vpxHeartbeats	vpx heartbeats - outbound UDP Port 902

Note: You can configure your own services in the file
/etc/vmware/firewall/services.xml

esxcfg-firewall
examples:
Enable ssh client connections from the
Service Console:
# esxcfg-firewall -e sshClient
Disable the Samba client connections:
# esxcfg-firewall
-d smbClient
Allow syslog outgoing
traffic:
# esxcfg-firewall -o
514,udp,out,syslog
Turn off the
firewall:
# esxcfg-firewall -allowIncoming
#
esxcfg-firewall -allowOutgoing
Re-enable the
firewall:
# esxcfg-firewall -blockIncoming
#
esxcfg-firewall –blockOutgoing


Esxcfg-nics
Description: Prints a list of physical network adapters along with information
on the driver, PCI device, and link state of each NIC. You can also use this
command to control a physical network adapter’s speed and
duplexing.
Syntax:
esxcfg-nics <options> [nic]

Options:

-s <speed>	Set the speed of this NIC to one of 10/100/1000/10000. Requires a NIC parameter.
-d <duplex>	Set the duplex of this NIC to one of 'full' or 'half'. Requires a NIC parameter.
-a	Set speed and duplex automatically. Requires a NIC parameter.
-l	Print the list of NICs and their settings.
-r	Restore the NICs configured speed/duplex settings. (Internal use only)
-h	Displays command help

esxcfg-nics
examples:
Set the speed and duplex of a NIC
(vmnic2) to 100/Full:
esxcfg-nics -s 100 -d full
vmnic2
Set the speed and duplex of a NIC (vmnic2)
to auto-negotiate:
esxcfg-nics -a vmnic2



Esxcfg-vswitch
Description: Creates and updates
virtual machine (vswitch) network settings
Syntax: esxcfg-vswitch <options>
[vswitch[:ports]]

Options:

-a	Add a new virtual switch.
-d	Delete the virtual switch.
-l	List all the virtual switches.
-L <pnic>	Set pnic as an uplink for the vswitch.
-U <pnic>	Remove pnic from the uplinks for the vswitch.
-p <portgroup>	Specify a portgroup for operation. Use ALL for operation to work on all portgroups
-v <vlan id>	Set VLAN ID for portgroup specified by -p. 0 would disable the VLAN.
-c	Check to see if a virtual switch exists. Program outputs a 1 if it exists, 0 otherwise.
-A <name>	Add a new portgroup to the virtual switch.
-D <name>	Delete the portgroup from the virtual switch.
-C <name>	Check to see if a portgroup exists. Program outputs a 1 if it exists, 0 otherwise.
-r	Restore all virtual switches from the configuration file (Internal use only)
-h	Displays command help

esxcfg-vswitch examples:
Add a pnic (vmnic2) to a vswitch (vswitch1):
esxcfg-vswitch -L vmnic2 vswitch1
Remove a pnic (vmnic3) from a vswitch (vswitch0):
esxcfg-vswitch -U vmnic3 vswitch0
Create a portgroup (VM Network3) on a vswitch
(vswitch1):
esxcfg-vswitch -A "VM Network 3"
vSwitch1
Assign a VLAN ID (3) to a portgroup (VM
Network 3) on a vswitch (vswitch1):
esxcfg-vswitch
-v 3 -p "VM Network 3" vSwitch1


Esxcfg-vswif
Description: Creates and updates service console network settings. This
command is used if you cannot manage the ESX Server host through the VI Client
because of network configuration issues.
Syntax: esxcfg-vswif <options>
[vswif]

Options:

-a	Add vswif, requires IP parameters. Automatically enables interface.
-d	Delete vswif.
-l	List configured vswifs.
-e	Enable this vswif interface.
-s	Disable this vswif interface.
-p	Set the portgroup name of the vswif.
-i <x.x.x.x> or DHCP	The IP address for this vswif or specify DHCP to use DHCP for this address.
-n <x.x.x.x>	The IP netmask for this vswif.
-b <x.x.x.x>	The IP broadcast address for this vswif. (not required if netmask and ip are set)
-c	Check to see if a virtual NIC exists. Program outputs a 1 if the given vswif exists, 0 otherwise.
-D	Disable all vswif interfaces. (WARNING: This may result in a loss of network connectivity to the Service Console)
-E	Enable all vswif interfaces and bring them up.
-r	Restore all vswifs from the configuration file. (Internal use only)
-h	Displays command help.

Note: You can set the Service Console
default gateway by editing the /etc/sysconfig/network file or through the VI
Client under Configuration, DNS & Routing.

esxcfg-vswif
examples:
Change your Service Console (vswif0)
IP and Subnet Mask:
esxcfg-vswif -i 172.20.20.5 -n
255.255.255.0 vswif0
Add a Service Console
(vswif0):
esxcfg-vswif -a vswif0 -p "Service
Console" -i 172.20.20.40 -n 255.255.255.0


Esxcfg-route
Description: Sets or retrieves the default VMkernel gateway
route
Syntax:
esxcfg-route <options> [<network> [<netmask>] <gateway>]

<network> can be specified in 2 ways: as a single argument in
<network>/<mask> format or as a <network> <netmask>
pair.
<gateway> is either an IP address or 'default'

Options:

-a	Add route to the VMkernel, requires network address (or 'default') and gateway IP address.
-d	Delete route from the VMkernel, requires network address (or 'default').
-l	List configured routes for the Service Console.
-r	Restore route setting to configured values on system start. (Internal use only)
-h	Displays command help

esxcfg-route examples:
Set the VMkernel default gateway route:
esxcfg-route 172.20.20.1
Add a
route to the VMkernel:
esxcfg-route -a default
255.255.255.0 172.20.20.1


Esxcfg-vmknic
Description: Creates and updates
VMkernel TCP/IP settings for VMotion, NAS, and iSCSI
Syntax: esxcfg-vmknic <options>
[[portgroup]]

Options:

-a	Add a VMkernel NIC to the system, requires IP parameters and portgroup name.
-d	Delete VMkernel NIC on given portgroup.
-e	Enable the given NIC if disabled.
-D	Disable the given NIC if enabled.
-l	List VMkernel NICs.
-i <x.x.x.x>	The IP address for this VMkernel NIC. Setting an IP address requires that the -n option be given in same command.
-n <x.x.x.x>	The IP netmask for this VMkernel NIC. Setting the IP netmask requires that the -i option be given in the same command.
-r	Restore VMkernel TCP/IP interfaces from configuration file. (Internal use only)
-h	Displays command help

esxcfg-vmknic examples:
Add
a VMkernel NIC and set the IP and subnet mask:
esxcfg-vmknic -a "VM Kernel" -i 172.20.20.19 -n 255.255.255.0

Physical to virtual converstion Issues, Virtual to Virtual Conversion

Hi All
Most of the members will facing problem due to VSS writer , This issue will be faced due to volume shadow copy issue
Symptoms

•You cannot convert a virtual machine using VMware vCenter Converter Standalone
•Conversion of a virtual machine fails immediately
•Conversion fails with the error:
Converter unable to create a VSS snapshot of the source volume
Error code 2147754776 (0x80042318)
•On a Windows machine running vCenter Converter Standalone, under Administration Tools > Event Viewer > Application you see the error:
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 5013
Date: 8/19/2005
Time: 10:38:14 PM


User: N/A
Computer: ComputerName
Description: Volume Shadow Copy Service error: Shadow Copy writer ContentIndexingService called routine RegQueryValueExW which failed with status 0x80070002 (converted to 0x800423f4). For more information, see Help and Support Center at http://support.microsoft.com.


Data: 0000: 57 53 48 43 4f 4d 4e 43 WSHCOMNC 0008: 32 32 39 32 00 00 00 00 2292.... 0010: 57 53 48 43 49 43 00 00 WSHCIC.. 0018: 32 38 37 00 00 00 00 00 287.....


Procedure to reolve the issue 

Click Start, click Run, type regedit, and then click OK.

Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentIndex\Catalogs
Click the registry subkey for each program that is listed under the Catalogs registry subkey. For each registry subkey, verify whether the Location registry entry exists.
If the Location registry entry is missing for a selected program, verify whether the program is still installed.
If the program is not installed, right-click the registry subkey for the program under the Catalogs subkey, and then click Delete. If the program is installed, correct the location information.
Restart the computer, and then use Windows Backup Utility to test this problem


Please find more information http://support.microsoft.com/kb/907574

Using the Data Migration Tool to upgrade from vCenter Server 4.0 to vCenter Server 4.1 fails

This known issue occurs when the Data Migration Tool is run against a vCenter Server with MS SQL Express that has been updated (for example, if vCenter Server 4.0 is updated to Update 2 or if vCenter Server 2.5 is updated to vCenter Server 4.0.)


When vCenter Server is upgraded, the value of the following registry keys are switched from Bundled to Custom:


•In Windows 2003 – HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VirtualCenter\DbServerType


•In Windows 2008 – HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware VirtualCenter\DbServerTypeThe database migration tool fails to properly backup the database when this value is set to Custom, even though there are no observable error messages displayed. If the value is manually changed back to Bundled, then the database tool properly backs up and restores the database to the vCenter Server 4.1 machine. The backup part of the script checks if the DSN forwards to a localhost or a remote location to determine if the database is local or not. However, the Custom value is used by the restore part of the script which considers that the database is remote and does not restore the database dump created by the backup part.

Changing the registry value from Custom to Bundled before launching the backup.bat script resolves this issue. If you have already gone through the database migration, you can still resolve this issue by performing these steps after making the registry change.
To change the registry value from Custom to Bundled:


1.On the machine you are trying to perform the backup, go to Start > Run, type regedit, and click OK.


2.For Windows 2003 navigate to the registry key HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VirtualCenter or for Windows 2008 navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware VirtualCenter.


3.Right-click the DbServerType value in the right hand pane, and click Modify.


4.Change the value from Custom to Bundled, and click OK.


5.Launch the backup.bat script as normal.


6.Ensure that vCenter Server is not already installed on the target server. If it is installed, uninstall it. If you do not uninstall it, the installation process fails.


7.Launch install.bat and follow the Installation Wizard.

vSphere Client Error parsing the server “SERVER IP” “clients.xml” file. Login will continue, contact your system administrator

This is solution for xml error
Remove this KB980773 seems to have undesired effect on MS DotNet Framework required by the VMware vSphere client to run. I believe we will have to wait for VMware to fix it or to push Microsoft to fix it
1. Download the file system.dll. This file is typically located in %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\ directory of a non-Windows 7 or Windows 2008 R2 machine with .NET v3.5 SP1 installed.
2. Copy the file to C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\lib.

Note: If the lib directory does not exist, create it.
3. Open VpxClient.exe.config in a text editor. The file is located at C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher.
4. Add the following three lines to VpxClient.exe.config, just before :
5. From Windows 2008 R2 or Windows 7 System Properties, click the Advanced tab > Environment Variables.
6. Create a new System variable called DEVPATH and assign the value:
C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
Note: For 32bit operating systems, replace Program Files (x86)with Program Files.
You can now launch vSphere Client from a Windows 7 or Windows 2008 R2 machine. You may have to right-click on the vSphere Client icon and choose Run as administrator.

Fault issues

Common Fault issues in VMware
Infrastructure

1007819 Dealing with an unresponsive virtual machine	1007802 Confirming a virtual machine is unresponsive 1007808 Ensuring a virtual machine is not inaccessible due to a VMware VirtualCenter issue 1007818 Dealing with unresponsive guest OS issues	1007805 Locating a virtual machine log files on an ESX host 1007813 Troubleshooting a virtual machine that has become unresponsive because of an ESX host	1000674 Can't stop or kill virtual machine 1007813 Troubleshooting a virtual machine that has become unresponsive because of an ESX host	1004344 Identifying causes of not being able to power cycle ESX Server virtual machines 1007814 Troubleshooting a virtual machine that is unresponsive because of configuration issues
1007808 Ensuring a virtual machine is not inaccessible due to a VMware VirtualCenter issue	1003895 Stopping, starting, or restarting the VirtualCenter Server service	1002687 Virtual machine stops responding in a Power On state in VirtualCenter	7114568 Cannot Power on Virtual Machines, "Not enough licenses installed to perform operation" Error Message	1004592 Vmware VirtualCenter console displays handshake error.
1007813 Troubleshooting a virtual machine that has become unresponsive because of an ESX host	1003751 Verifying that ESX virtual machine storage is accessible 1003659 Identifying shared storage issues with ESX 3.x 1004005 [Internal] Third Party System Management agents in the Service Console	1004144 ESX Server virtual machines stop responding due to shared storage connectivity issues 1006791 Server stops responding and shows errors on a purple screen	1003755 Verifying sufficient free disk space for an ESX virtual machine 10051 Virtual machine does not power on because of missing or locked files	1003564 Investigating disk space on an ESX host 1003690 Ensuring your hardware is functioning correctly
1007814 Troubleshooting a virtual machine that is unresponsive because of configuration issues	1005734 Troubleshooting a virtual machine that stops responding or fails when the CD-ROM entry is ATAPI 1003164 Guest stops responding after connecting a USB CD-ROM	1001637 Virtual machine does not power on and there is high CPU reservation	1002025 Virtual machine stops responding during backup	1002836 Why snapshot removal can stop a virtual machine virtual machine for long time
1007818 Dealing with unresponsive guest OS issues	1004007 Investigating operating system disk space	1007577 Do not use guest OS performance tools to monitor virtual machine performance	1007866 Using Windows Event Viewer to identify the cause of an unresponsive or failed virtual machine	1004764 Unable to shutdown Windows using Shutdown Guest option

System Management in VMWare

Common system
management issues in VMware Infrastructure

1003926 Troubleshooting the VMware VirtualCenter Server service when it does not start or fails	1003895 Stopping, starting, or restarting the VirtualCenter Server service	1003928 Troubleshooting the database data source used by VirtualCenter Server	1003971 Determining if a port is in use	1003979 Investigating the health of a VirtualCenter database server	1003996 Investigating Active Directory when it causes the VirtualCenter Server to stop or fail to start
1003684 Overview of migration compatibility error messages	1003718 Troubleshooting VMotion CPU feature requirement error messages
1004070 Diagnosing why VirtualCenter is not sending email alerts	1003486 Testing network connectivity with the Ping command
1003409 Diagnosing an ESX Server that is Disconnected or Not Responding in VirtualCenter	1003480 Changing an ESX Server's connection status in VirtualCenter 1003490 Restarting the Management agents on an ESX Server	1003486 Testing network connectivity with the Ping command 1003496 Checking for resource starvation of the ESX Server service console	1003487 Testing port connectivity with the Telnet command	1003494 Verifying that the Management Service is running on an ESX host	1003495 Verifying that the VirtualCenter Agent Service is running on an ESX host
1004002 Diagnosing slow deployment of templates or clones from VirtualCenter	1004028 Troubleshooting slow template deployment on a single template	1003496 Checking for resource starvation of the ESX Server service console	1004089 Configuring the speed and duplex of an ESX Server host network adapter
1004050 Troubleshooting template deployment or cloning when it fails	1005593 Determining the correct version of sysprep to use	1005594 Ensuring VirtualCenter Server is the only VMware product installed on host	1005870 Ensuring the guest operating system type is set correctly
1003870 Diagnosing the Virtual Infrastructure Client when it fails to connect to an ESX host	1003486 Testing network connectivity with the Ping command	1003494 Verifying that the Management Service is running on an ESX host	1003487 Testing port connectivity with the Telnet command	1003887 Troubleshooting permissions errors when connecting to an ESX Server host with the Virtual Infrastructure client
1003869 Diagnosing the Virtual Infrastructure Client when it fails to connect to VirtualCenter	1003486 Testing network connectivity with the Ping command	1003895 Stopping, starting, or restarting the VirtualCenter Server service	1003487 Testing port connectivity with the Telnet command
1003561 Troubleshooting the VMware ESX Server Management Service when it will not start	1003631 Restarting the ESX Server Management service	1003564 Investigating disk space on an ESX host	1003634 Troubleshooting the firewall policy on an ESX Server	1003496 Checking for resource starvation of the ESX Server service console
1003807 Unable to connect to an ESX Server host using Secure Shell (SSH)	1003486 Testing network connectivity with the Ping command	1003906 Verifying that the Secure Shell Daemon is running on an ESX Server host	8375637 Enabling Root SSH Logins on ESX Server 3	1003808 Configuring the ESX Server host firewall for SSH	1003487 Testing port connectivity with the Telnet command
1003691 Diagnosing a VMware High Availability cluster configuration failure	1003692 Verifying a feature is licensed	1003735 Identifying issues with and setting up name resolution on ESX Server	1003713 Configuring name resolution for VMware VirtualCenter	1003486 Testing network connectivity with the Ping command	1003714 Verifying and reinstalling the correct version of VMware VirtualCenter Server agent
1003734 Diagnosing VMware VMotion failure at 10%	1002662 Unable to set VMkernel gateway as there are no VMkernel interfaces on the same network 1003791 VMware VMotion fails if target host does not meet reservation requirements	1003728 Testing VMkernel network connectivity with the vmkping command 1003496 Checking for resource starvation of the ESX Server service console	1003486 Testing network connectivity with the Ping command 1003780 Troubleshooting migration compatibility error: Device is a connected device with a remote backing	1003735 Identifying issues with and setting up name resolution on ESX Server	1003736 Verifying time synchronization across environment
1003839 Troubleshooting Virtual Machine loses network connection after VMware VMotion	1003486 Testing network connectivity with the Ping command	1002811 Port security on the physical switch causes a loss of network connectivity
1003792 Diagnosing VMware VMotion failure at 90-95%	1003490 Restarting the Management agents on an ESX Server	1003736 Verifying time synchronization across environment	1003791 VMware VMotion fails if target host does not meet reservation requirements	1003496 Checking for resource starvation of the ESX Server service console	1003659 Identifying shared storage issues with ESX 3.x