The default time-outs in VMware Infrastructure (VI) Client may not be
long enough for certain long operations, such as deleting snapshots.
This article provides information on how to prevent these timeouts.
vCenter
Server has a default 15 minute timeout for any task. Starting with the
vCenter 2.5 Update 4 release, to prevent vSphere Client from displaying
unnecessary timeout error messages, you can configure the timeout values
by editing the vpxd.cfg file and the vpxa.cfg file of the source and destination ESXi/ESX host.
Note: If you are using VCB and your backup failed
due to a timeout, check your virtual machine for a backup snapshot that
has been left behind.
Lengthy Tasks which Time Out
When a task is reported to timeout within vCenter, the task may
continue to run in the ESXi/ESX host level. Certain tasks (such as a
snapshot consolidation) may take a long time to complete and should not
be interrupted.
Note: In the case of snapshot consolidation, even
though the vSphere Client timeout occurs, the operation on the ESXi/ESX
host is still running. You can verify by observing the .vmdk file for the virtual machine. It is updated every minute which means the delta files are being committed to the .vmdk file.
vCenter Server Timeout Settings
To change the timeout value in the vCenter Server, update vpxd.cfg on vCenter and vpxa.cfg on the ESXi/ESX:- Log in to the vCenter Server with the appropriate permissions.
- Open the vpxd.cfg file in a text editor. The default location for the file is:
C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\vpxd.cfg - For Windows 7 and Windows 2008, the default location for the file is:
C:\ProgramData\VMware\VMware VirtualCenter\vpxd.cfg - To increase the timeout values for the virtual machine migration task, add the following timeout parameter in the vpxd.cfg file:
<config>
...
<task>
<timeout>10800</timeout>
</task>
...
</config>
Note: The value 10800 can be changed based on your requirements. This example uses 10800 seconds, or 3 hours. - To increase the SOAP layer blocking call timeout, add the following values in the vpxd.cfg file:
<config>
...
<vmomi>
<soapStubAdapter>
<blockingTimeoutSeconds>10800</blockingTimeoutSeconds>
</soapStubAdapter>
</vmomi>
...
</config>Note: The value 10800 can be changed based on your requirements. This example uses 10800 seconds, or 3 hours. This line may not be present in ESX 4.0. - Restart the vCenter Server service.
ESXi/ESX timeout settings
- Log in to the ESXi/ESX host as root via the console or an SSH session.
- Open the vpxa.cfg file in a text editor.
By default, this file is located at:- ESX - /etc/opt/vmware/vpxa/vpxa.cfg
- ESXi - /etc/vmware/vpxa/vpxa.cfg
- To increase the timeout values for the virtual machine
migration task (both source and destination hosts), add the following
timeout parameter in the vpxa.cfg file:
<config>
...
<task>
<timeout>10800</timeout>
</task>
...
</config> -
To increase the SOAP layer blocking call timeout, add these values in the vpxa.cfg file :
<config>
...
<vmomi>
<soapStubAdapter>
<blockingTimeoutSeconds>10800</blockingTimeoutSeconds>
</soapStubAdapter>
</vmomi>
...
</config>Note: The value 10800 can be changed based on your requirements. This example uses 10800 seconds or 3 hours. -
Configure the timeout value for the time that vCenter Server waits to capture the virtual machine's ID at ESX/ESXi destination. Add a new configurable parameter in the vpxa.cfg file:
<config>
...
<vpxa>
...
<vmotion>
<vmIdAcquireTimeout>600</vmIdAcquireTimeout>
</vmotion>
...
</vpxa>
...
</config>Note: The value 600 can be changed based on your requirements. This example uses 600 seconds or 10 minutes. -
Restart the vmware-vpxa service on the ESXi/ESX host.
No comments:
Post a Comment