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.
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
- Configuring the Remote ETL Engine (EE)
- Drill down and graph ports
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.
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. Though this was the default setup when upgrading from previous the TrueSight Capacity Optimization releases to TrueSight Capacity Optimization 10.0, it is recommended that you use the above approach.
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 40000 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.