Communication ports and protocols

The following table lists the default configurations of protocols and ports for different components and services used by various TrueSight Capacity Optimization components.


Default ports and protocols used by TrueSight Capacity Optimization

The following figure shows the default protocols and ports used by TrueSight Capacity Optimization components.


The following table lists the default ports and protocols used by the TrueSight Capacity Optimization components. 


Type of communication

Default Port

From

To

Protocol

Command line administration

22

CLI

TrueSight Capacity Optimization Application Server

SSH

22

CLI

(Remote) ETL Engine Server

SSH

Web access

8000/8443

Browser, remote ETL Engine Server, Integration Studio

TrueSight Capacity Optimization Application Server

HTTP/HTTPS

443/8043

Browser, Application ServerTrueSight Presentation ServerHTTP/HTTPS
448/8048BrowserRemedy Single Sign-OnHTTP/HTTPS

Access to Data Hub Web services

For internal communication to Data Hub: 8280 (Data Hub) and 8380 (Service Container), used by schedulers on Application Server, Local ETL Engine.

ETL Engine Servers

TrueSight Capacity Optimization Application Server
(Data Hub)

HTTP/HTTPS

For external communication to Data Hub, the following ports are used by Remote ETL Engine:

  • 8000: HTTP
  • 8443: HTTPS

(Remote) ETL Engine Servers

TrueSight Capacity Optimization Application Server
(Data Hub)

HTTP/HTTPS
Internal communication8080 (loopback interface only)

TrueSight Capacity Optimization Application Server (Apache HTTPD Web Server)

Same server - Web TomcatHTTP
8009 (loopback interface only)

TrueSight Capacity Optimization Application Server (Apache HTTPD Web Server)

Same server - Web TomcatAJP
8209 (loopback interface only)

TrueSight Capacity Optimization Application Server (Apache HTTPD Web Server)

Same server - Datahub TomcatAJP
8309 (loopback interface only)

TrueSight Capacity Optimization Application Server (Apache HTTPD Web Server)

Same server - ServiceContainer TomcatAJP
Shutdown port8005 (loopback interface only)

TrueSight Capacity Optimization Application Server (Stop/Restart scripts)

Same server - Web TomcatTCP
8205 (loopback interface only)

TrueSight Capacity Optimization Application Server (Stop/Restart scripts)

Same server - Datahub TomcatTCP
8305 (loopback interface only)

TrueSight Capacity Optimization Application Server (Stop/Restart scripts)

Same server - ServiceContainer TomcatTCP

Database access from TrueSight Capacity Optimization Application Server

  • 1521 for Oracle (configurable)
  • 5432 for PostgreSQL (configurable)

TrueSight Capacity Optimization Application Server (Gateway Server JSP engine, Data Hub, and scheduler)

Database Server

SQL*Net

Database access from ETL Engine Servers

  • 1521 for Oracle (configurable)
  • 5432 for PostgreSQL (configurable)

ETL Engine servers (scheduler)

Database Server

SQL*Net

Notification email

25/465
(configurable)

ETL Engine Server
(Scheduler)

SMTP gateway

SMTP/SSL

TrueSight Capacity Optimization Application Server
(Scheduler)

SMTP

Notification traps

162
(configurable)

ETL Engine Server
(Scheduler)

Trap receiver

SNMP

TrueSight Capacity Optimization Application Server
(Scheduler)

(Optional) User authentication via external LDAP service

389
(configurable)

TrueSight Capacity Optimization Application Server

LDAP service

LDAP/SSL

JDBC

  • 1521 for Oracle (configurable)
  • 5432 for PostgreSQL (configurable)

TrueSight Capacity Optimization Application Server

Database Server

JDBC

Access to data sources

Specific to each connector

(Remote) ETL Engine servers (connectors, Data Accum)

Data source

Specific for each connector

Generic Service Containers

Listen HTTP on TCP 8380

--TCP
Dynservices and registry8999 - 9002

TrueSight Capacity Optimization Application Server

TrueSight Capacity Optimization Application Server

HTTPS

Port requirement summary for Gateway Servers and Agents

Gateway Server comprises of several components that analyze performance, display detailed graphs, report statistics, predict future performance, and enable capacity planning for your database. Gateway Server supports collecting, analyzing, and modeling business-oriented workloads with system data, and requires several TCP ports to be open for the Gateway Server and Capacity Agents to communicate.

For more information, refer to the following sections:

Default port requirements for Gateway Servers and Agents

The following table provides the default ports for the Gateway Server and Agent. Verify that the Gateway Server and Agent use these ports.

Port number

Description

10128

The Gateway Server initiates a connection to port 10128 on the Capacity Agent system for collection start, query, and pull request. Port 10128 is also required for the UDR Collection Manager (UCM). If you are running data collections from the command line.

10129This is the General Manager Server port. The Gateway Manager uses this port to access the Gateway Server.
10130This port is used by the Gateway Server while communicating with the Application Server in the HTTPS mode.

6767

This port is used by the Gateway Server node to communicate with the Capacity Agent. The Gateway Server node initiates this connection, which is used to start the Capacity Agent.

6768Optional and disabled by default. The Capacity Agent connects to the Gateway Server on port 6768 for metric group status messages only.

Configuring the Remote ETL Engine (EE)

You can configure Remote EE in one of the following ways:

  • Use the 8000/8443 ports for both internal communication and for populating data via the data API. This approach is recommended. Apache web server acts as a proxy in this case.
  • Use the internal TCP ports 8280 or 8380 for both internal communication and for populating data via the data API.

Drill down and graph ports

Additional ports are used to activate drill downs within the Gateway Server, for instance, Port 30000 is used by the Windows Gateway Server for drill downs and graphs, Port 4000 is used on UNIX. However, Investigate uses these ports differently on UNIX and Microsoft Windows platforms:

  • On UNIX systems: If multiple drill downs or graphs are created, they still use only one port. However, if a port conflict is detected with either of these ports, the next lower port will be checked for availability until an unused port is found.
  • On Windows systems: One port is opened for each graph or drill down (starting at port 30000 for drill downs and graphs) for Investigate drill down requests and Investigate chart requests. The result is that the Windows Gateway Server requires many more ports to be opened through the firewall to support drill downs and graphs. For example, if you have 10 graphs opened, the Windows Gateway Server requires 10 different ports.

Note

If you are using firewall mode, these ports are not used by the remote computers to send data. However, the Gateway Server computer does bind to these ports.

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Steve Burk

    This documentation page should be updated to indicate port directionality requirements. This URL at https://communities.bmc.com/docs/DOC-54487 contains information, but it is getting rather dated.

    I sense renewed concern around security risks posed by agents installed on edge IPs that can initiate conversations to the mothership (Gateway server). Does BMC share port requirements with vendors of tools like Qualys so that they are aware of expected traffic profiles between the Gateway and Agent.

    Mar 04, 2020 10:50