Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

VMware vCenter Update Manager network port requirements (1004543)

Last Updated: 4/5/2021Categories: Best PracticesTotal Views: 187260Language:
Chinese (Simplified)JapaneseEnglish

9 like this article

Subscribe to get an email
newsletter with new updates

9 people found this helpful Please provide article feedback:

Details

vCenter Update Manager is installed as part of the installation process for vCenter Server. If you have an established VMware Infrastructure environment, you can use the same installer to add vCenter Update Manager functionality.

You can install vCenter Update Manager on the same machine as vCenter Server or on a different machine. Before you install vCenter Update Manager, gather the networking information (including the IP address and port number) about vCenter Server that vCenter Update Manager will use.

vCenter Update Manager 4.x/5.x/6.x

After the installation:

vCenter Update Manager connects to vCenter Server on TCP port 80.

ESXi/ESX hosts connect to the Update Manager Web Server listening on HTTP port 9084 for host patch downloads.

vSphere Client initialization of the vCenter Update Manager plugin uses TCP port 9084 between the client and the vCenter Update Manager server.

vCenter Update Manager connects to ESXi/ESX hosts on TCP port 80 and 902 for pushing virtual machine patches and host upgrade files.

Note: vCenter Update Manager 5.0.x no longer supports patching virtual machines.

The vCenter Update Manager Client plug-in connects to the vCenter Update Manager SOAP server listening on port 8084. It connects to the vCenter Update Manager Web server on HTTP (SSL) port 9087 for uploading the host upgrade files.

To obtain metadata, vCenter Update Manager must be able to connect to http://www.vmware.com/, and requires outbound ports 80 and 443.

If the default ports 80 and 443 are already in use by another application, the alternate port numbers used by vCenter Update Manager should be within the range 9000-9100. VMware vCenter Update Manager automatically opens these ports for ESX host scanning and remediation.

vCenter Update Manager 1.0.x

After the installation:

The vCenter Update Manager Web server listens on 9084 TCP if the default is not changed during the installation.

The vCenter Update Manager SOAP server listens on 8084 TCP if the default is not changed during the installation.

Both are accessed through a reverse proxy that listens on the standard ports 80 and 443, but there is a slight difference depending on the installation:

When vCenter Update Manager and vCenter Server are installed on the same machine:

All incoming connections to vCenter Update Manager are accessed through a reverse proxy provided by vCenter Server.

ESX hosts connect to port 80, and vCenter Server forwards the request to the vCenter Update Manager Web server listening on 9084 for host patch downloads.

vCenter Server directly connects to vCenter Update Manager on 8084 because they are on the same machine.

When Update Manager and vCenter Server are installed on two different machines:

vCenter Update Manager has a reverse proxy listening on ports 80 and 443 if the default is not changed during the installation.

vCenter Server connects to vCenter Update Manager through port 443. The reverse proxy forwards the request to 8084.

The ESXi/ESX host connects to vCenter Update Manager through port 80. The reverse proxy forwards the request to 9084.

To obtain metadata, vCenter Update Manager must be able to connect to http://www.vmware.com, and requires outbound ports 80 and 443.

For binary data, the outbound ports are 80 and 443.

For ESXi/ESX host scanning and remediation, vCenter Update Manager requires that port 80 be open on the ESX host.

For vCenter Update Manager to push patches to ESXi/ESX host, port 902 is required.

vSphere Client initialization of the vCenter Update Manager plugin uses TCP port 9084 between the client and the vCenter Update Manager server.

Note: After the release of VMware vSphere Update Manager 6.0 Update 3, the java process for the update manager service is via the port 8080.

Solution

Note: For more information on vCenter Update Manager, see the VMware Update Manager Administration Guide at the VMware Documentation Site.

For more information on ports used by VMware products, see TCP and UDP Ports required to access vCenter Server, ESXi/ESX hosts, and other network components (1012382).

Additionally, while the Update Manager server may be able to connect to vmware.com, it is possible that the downloads are failing due to internet filters that can deny access to sub-domains of vmware.com.

This is the default list of download sources for Update Manager:

https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

https://hostupdate.vmware.com/software/VUM/PRODUCTION/csco-main/csco-depot-index.xml

http://vapp-updates.vmware.com/vai-catalog/index.xml

Note: If any of these addresses fail to display an XML page, the download for Update Manager patches will fail.

Additional Information

For translated versions of this article, see:

日本語: VMware vCenter Update Manager ネットワーク ポート要件 (2080177)

简体中文: VMware vCenter Update Manager 网络端口要求 (2086576)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere Update Manager

VMware vSphere

Related Versions:

VMware vSphere Update Manager 6.7.x

VMware vSphere Update Manager 6.5.x

VMware vSphere Update Manager 6.0.x

VMware vSphere Update Manager 5.5.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant