Knowledge Base
vCenter Update Manager host tasks might fail in slow networks (1021050)
Solution
Troubleshoot network timeouts in vCenter Update Manager 4.0 Update 1 and earlier versions
The default timeout period for vCenter Update Manager 4.0 Update 1 and earlier versions is two hours (7,200 seconds) and cannot be changed.The default timeout period for vCenter Server tasks is 15 minutes. To increase the vCenter Server timeout, perform the following steps:
- Log in as an administrator to the machine on which vCenter Server is installed.
- Open the vpxd.cfg file in a text editor.
The default location is C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\vpxd.cfg.
- Include these lines before the </config> tag:
<task>
<timeout>7200</timeout>
</task>
<vmomi>
<soapStubAdapter>
<blockingTimeoutSeconds>7200</blockingTimeoutSeconds>
</soapStubAdapter>
</vmomi>
If the <task> tag already exists in the file, add the timeout (<timeout>7200</timeout>) in the existing tag, rather than create a new <task> tag.
- Restart the vCenter Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895).
- Log in to the ESX/ESXi host with root privileges using the console or an SSH session.
For more information about troubleshooting SSH connections to ESX hosts, see Unable to connect to an ESX host using Secure Shell (SSH) (1003807).
For more information about troubleshooting ESXi hosts, see Tech Support Mode for Emergency Support (1003677) for 4.x and below. For ESXi 4.1 and above see Using Tech Support Mode in ESXi 4.1 and ESXi 5.x (1017910).
- On the ESX/ESXi host, open the /etc/opt/vmware/vpxa/vpxa.cfg in a text editor.
- Include the following lines before the </config> tag:
<task>
<timeout>7200</timeout>
</task>
<vmomi>
<soapStubAdapter>
<blockingTimeoutSeconds>7200</blockingTimeoutSeconds>
</soapStubAdapter>
</vmomi>
If the <task> tag already exists in the file, add the timeout (<timeout>7200</timeout>) in the existing tag, rather than create a new <task> tag.
Troubleshoot slow network issues in vCenter Update Manager 4.0 Update 2, vCenter Update Manager 4.1 and later
For vCenter Update Manager 4.0 Update 2, vCenter Update Manager 4.1 and later, no action is required and all host operations complete without any errors. In vCenter Update Manager 4.0 Update 2, vCenter Update Manager 4.1 and later, you can change the default timeout for vCenter Update Manager by using the <PatchTaskTimeoutSeconds> tag in the vci-integrity.xml file. For more information, see Extend the default timeout periods for vCenter Server, ESX/ESXi hosts, and vCenter Update Manager (1017253).The time for host operations varies from several minutes (in LAN environments) to several hours (in WAN environments). You can estimate staging or remediation periods in various WAN environments.
Table 1 lists typical WAN environments, such as dial-up, DSL, and satellite, with varying bandwidth, latency, and so on.
| Network |
Bandwidth |
Latency |
Error rate |
| Dial-up 1 |
64Kbps |
250ms |
0.05% |
| Dial-up 2 |
256Kbps |
250ms |
0.05% |
| DSL |
512Kbps |
100ms |
0.05% |
| Satellite |
1.5Mbps |
500ms |
0.10% |
| T1 |
1.5Mbps |
100ms |
0.05% |
The maximum durations of the longest host operations for ESX/ESXi hosts in various network environments are illustrated in Figure 1.
Figure 1. Maximum host operation time for ESX/ESXi hosts.
Update History
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
|
|
