Page tree
Skip to end of metadata
Go to start of metadata

This topic contains the following sections: 

Default ports and protocols used by BMC TrueSight Capacity Optimization

The following table lists the default ports and protocols used by BMC TrueSight Capacity Optimization components. These aim to provide you with specific information, and can also help you resolve communication port conflicts and other issues.

BMC TrueSight Capacity Optimization ports and protocols

Type of communication

Default Port

From

To

Protocol

Command line administration

22

CLI

BMC TrueSight Capacity Optimization application server

SSH

Command line administration

22

CLI

(Remote) ETL Engine server

SSH

Web access via Apache web server Note

8443

Browser

BMC TrueSight Capacity Optimization application server

HTTPS

Web access Note

8000

Browser

BMC TrueSight Capacity Optimization application server 

HTTP

Web access

8000/8443

Integration Studio

BMC TrueSight Capacity Optimization application server

HTTP/HTTPS

Access to DataHub Web services

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

ETL Engine servers

BMC TrueSight Capacity Optimization application server
(Data Hub)

HTTP/HTTPS

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

  • 8000: HTTP
  • 8443: HTTPS
(Remote) ETL Engine servers

BMC TrueSight Capacity Optimization application server
(Data Hub)

HTTP/HTTPS

DB access from BMC TrueSight Capacity Optimization application server

1521
(configurable)

BMC TrueSight Capacity Optimization application server (Gateway Server JSP engine, Data Hub, and scheduler)

Database server

SQL*Net

DB access from ETL Engine servers

1521
(configurable)

ETL Engine servers (scheduler)

Database server

SQL*Net

Notification email

25 / 465
(configurable)

ETL Engine server
(Scheduler)

SMTP gateway

SMTP / SSL

Notification email

25 / 465
(configurable)

BMC TrueSight Capacity Optimization application server
(Scheduler)

SMTP gateway

SMTP

Notification traps

162
(configurable)

ETL Engine server
(Scheduler)

Trap receiver

SNMP

Notification traps

162
(configurable)

BMC TrueSight Capacity Optimization application server
(Scheduler)

Trap receiver

SNMP

User authentication via external LDAP service (optional)

389
(configurable)

BMC TrueSight Capacity Optimization application server

LDAP service

LDAP / SSL

JDBC

1521
(configurable)

BMC 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

Note

If the Web server is not configured to listen at the default port 8000, you will need to modify the BMC TrueSight Capacity Optimization URL. To do this, update the Capacity Optimization Console URL field under Administration > SYSTEM > Configuration > General. This ensures that the BPPM integration launch-in-context from events works correctly.

If you do not update the URL, the URL that gets embedded in the event points to the wrong port, causing the cross launch to fail.

Ports required for data collection using Proxy Agent in a firewall environment

If you are behind a firewall environment, and proxy data collection is enabled, the following ports need to be configured on your system:

  • Ports 111135139, and 445 from the proxy host to the agentless computer
  • Open RPC ports for DCOM from the proxy host to the agentless computer. You can allow a large range of ports as defined by the OS (range is 1024 - 65536) or you can limit the range by creating specific registry keys, and restarting the agentless computer.

Note

If you make the range of ports too small, you might run out of available ports.

Port requirements for proxy data collection from Windows systems

Agentless collection, or proxy data collection, allows a specified Windows computer to act as a proxy host and collect data from other Windows computers without installing Perform Agent on those computers. 

A Microsoft Windows computer (Windows 2003, 2008, XP, Vista, or Windows 7) serves as a proxy host for gathering data from the local computer and other "agentless" computers, and stores the data locally. 

The proxy host uses Microsoft Windows Management Instrumentation (WMI) technology to collect data from these agentless computers. WMI is the Microsoft Windows protocol for collecting system data by way of the remote server. If you are using proxy data collection, note that the proxy host requires port 111 for the WMI Remote Procedure Call (RPC) connection to the agentless computer. 

For detailed instructions on proxy data collection configuration and setup, refer to Collecting data using Proxy Agents.

Port requirement summary for Gateway Servers and Agents

Gateway Server for BMC TrueSight Capacity Optimization integrates 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 in order for the Gateway Server and Perform Agents to communicate.

While there are many components of this product, the focus for purposes of configuring a firewall is the BMC TrueSight Capacity Optimization Gateway ServerPerform Agent, and System Collectors. Some of the associated ports can be changed after the product is installed.

For more information, refer to the following sections:

Default port requirements for Gateway Servers and Agents

The following table summarizes the default port requirements for Gateway Server and Agent. Because these values might have been changed by you installing the software, you should verify that these port values are the ones used by the product.

Port number

Description

10128

The Gateway Server initiates a connection to port 10128 on the Perform 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, port 10128 must be bi-directional.

6768

Perform Agent connects to the Gateway Server port 6768, for status and alert messages. Perform Agent must to be able to initiate a connection to Gateway Server port 6768 for collection status messages. Port 6768 is required also for the UDR Collection Manager (UCM).

6767

Port 6767 is used on the Gateway Server node for the Manager component to communicate with Perform Agent. The Gateway Server node initiates this connection which is used to start Perform Agent.

30000 or below as necessary

Port 30000 is used for Investigate drill downs. This port is dynamically allocated on the Gateway Server node. The Gateway Server node determines a free port and passes this information along to the remote node. This port is necessary for graphs. On Microsoft Windows Gateway Servers, port 30000 is used for both chart and drill down requests.

40000 or below as necessary

Port 40000 on UNIX Gateway Servers is used for Investigate graphs. This port is dynamically allocated on the Gateway Server node. The Gateway Server node determines a free port and passes this information along to the Perform Agent node. This port is necessary for drill downs. On UNIX platforms, if multiple drill downs or graphs are created, the product still only uses one port. Multiple ports will not be opened. Optionally, you can change the some of the default ports described in this section if you prefer to use ports other than those listed previously.

Note

If port numbers 40000 or 30000 are not available, then the next lower port is checked for its availability. This process continues until an unused port is found. These ports are dynamically allocated as needed.

25

You must set the SMTP server name and SMTP user address in the Control Panel. You only need an SMTP server and address if you want mail.

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, in that:

  • 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.

When there is a firewall between the proxy host and the agentless computers, you can encounter issues because WMI uses the Distributed Component Object Model (DCOM) protocol and Remote Procedure Call (RPC) routines, both of which make use of random ports.

Related topics

Collecting data using Proxy Agents