Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

My Subscriptions

Loading

Knowledge Base

TCP and UDP ports required to access VMware vRealize Orchestrator (52961)

Last Updated: 3/29/2018Categories: InformationalTotal Views: 5303Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

This article lists the TCP and UDP ports for VMware vRealize Orchestrator

Resolution

TCP and UDP ports for VMware vRealize Orchestrator:

Product

Port

Protocol

Source

Target

Purpose

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

25

TCP

vRealize Orchestrator Server (formerly known as VMware vCenter Orchestrator)

SMTP Server

Email notifications

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

80

TCP

vRealize Orchestrator Server (formerly known as VMware vCenter Orchestrator)

vCenter Server

Used to obtain virtual infrastructure and virtual machine information from orchestrated vCenter Server(s) through the vCenter API (Shared sessions)

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

389

TCP/UDP

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Server

LDAP Server

LDAP Authentication

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

443

TCP

vRealize Orchestrator Server (formerly known as VMware vCenter Orchestrator)

vCenter Server

Used to obtain virtual infrastructure and virtual machine information from orchestrated vCenter Server(s) through the vCenter API

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

636

TCP

vRealize Orchestrator Server (formerly known as VMware vCenter Orchestrator)

LDAP Server

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) uses LDAP authentication and group membership to determine role authorization in LCM and access to VMs/requests. This is the SSL secured LDAP protocol LDAPS (the SSL pendent of 389). This is used for secured LDAP authentication

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

1433

TCP

vRealize Orchestartor Server

Microsoft SQL Server

vRealize Orchestrator Server to Microsoft SQL Server for vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Database

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

1521

TCP

vRealize Orchestrator Server

Oracle Database Server

vRealize Orchestrator Server to Oracle for vRealize Orchestrator Database

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

3306

TCP

vRealize Orchestrator Server

MySQL Server

vRealize Orchestrator Server to MySQL Server for vRealize Orchestrator Database

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

5432

TCP

vRealize Orchestrator Server

PostgresSQL Server

vRealize Orchestrator Server to PostgresSQL Server for vRealize Orchestrator Database

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

8230

TCP

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Client

vRealize Orchestrator Server

Lookup port – The main port to communicate with vRealize Orchestrator Configurator server (JNDI port). All other ports communicate with the vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Configurator smart client through this one. It is part of the JBoss Application server infrastructure

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

8240

TCP

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Client

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Server

Command port – The application communication port (RMI container port), it is used for remote invocations. It is part of the JBoss Application server infrastructure.

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

8244

TCP

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Client

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Server

Data port used to access all vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) data models, such as workflows and policies. It is part of the JBoss application server infrastructure.

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

8250

TCP

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Client

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Server

Messaging port – The Java messaging port used to dispatch events. It is part of the JBoss Application server infrastructure

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

8280

TCP

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Server

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Server

Port used by vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Server to connect to the Web front-end via HTTP

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

8281

TCP

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Server

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Server

Port used by vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Server to connect to the Web front-end via HTTPS

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

8281

TCP

vCenter Server

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Server

Port used by vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Server to connect to vCenter Server to communicate with the vCenter API

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

8282

TCP

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Client PC

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Server

HTTP server port – Port used by the HTTP connector to connect to the Web frontend.

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

8283

TCP

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Client PC

vRealize Orchestrator Server

HTTPS server port – Port used by HTTP connector to connect to the Web frontend. Requires Jetty to be configured for SSL.

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

8286

TCP

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Client PC

vRealize Orchestrator Server

Java messaging port used for dispatching events.

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator)

8287

TCP

vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Client PC

vRealize Orchestrator Server

SSL secured Java messaging port used for dispatching events.

Realize Business Advanced/Enterprise

80/8080

TCP

Web Browser

vRealize Business Advanced/Enterprise

Port used to login (HTTP) to the vRealize Business UI.

vRealize Business Advanced/Enterprise

443

TCP

Web Browser

vRealize Business Advanced/Enterprise

Port used to login (HTTPS) to the vRealize Business UI.

vRealize Business Advanced/Enterprise

1521

TCP

vRealize Business Advanced/Enterprise

Oracle RDBMS

Port used by vRealize Business to connect to Oracle DB

vRealize Business Advanced/Enterprise

389/3268

TCP

vRealize Business Advanced/Enterprise

LDAP Server

Listen port in the LDAP/AD server that vRealize Business connects to for synchronizing users.

vRealize Business Advanced/Enterprise

32xx range

TCP

vRealize Business Advanced/Enterprise

Oracle DB

When a firewall is present between vRealize Business and Oracle DB servers, the 3200 range ports need to be opened on the firewall. Calls from vRealize Business to Oracle DB server originate on port 1521, but DB server uses a variety of random ephemeral ports in the 3200 range for return calls. If these are not opened, calls between vRealize Business and Oracle DB will hang. Use network monitoring applications such as Wireshark to verify these ephemeral ports.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
在 vRealize Operations Manager 6.x 及高级版本中，“数据存储群集摘要”显示“已打开电源的虚拟机”数量为问号 (53124)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Aria Automation Orchestrator

Related Versions:

Take Our Survey

Support Assistant