Network ports

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

The port numbers are specified while installing the following products and components:

Related topics

Basic deployment options for TrueSight Operations Management

Network port schematics for Infrastructure Management

Network port schematics for App Visibility

Integrating with IT Data Analytics

Data security for Real End User Experience Monitoring Software Edition

Tip

Press F to view the table in full-screen mode. 

Note

Ensure that you open ports in your firewall to enable communication between the components.

Network ports for Remedy Single Sign-On

Component Service Default port number Protocol Flow Function Default state Port configurable
HTTP HTTP 8080 TCP Inbound

Communication to the TrueSight Presentation Server and TrueSight Infrastructure Management from the Remedy SSO for authentication and authorization (non-secure mode)

Disabled Yes

HTTPS

HTTPS 8443 TCP Inbound

Communication to the TrueSight Presentation Server and TrueSight Infrastructure Management from the Remedy SSO for authentication and authorization (secure mode)

Enabled Yes

Shutdown port

HTTPS 8005 TCP Inbound Shutdown port for the Tomcat web server Enabled Yes

Network ports for Presentation Server

Component Service Default port number Protocol Flow Function Default state Port configurable

High Availability

Cache Replication Port HTTPS 7800 TCP Inbound

Cache replication from primary to secondary TrueSight Presentation Server, used for high availability

Enabled Yes
Control Port HTTPS 8800 TCP Inbound

Communication between the primary and secondary TrueSight Presentation Server, used for high availability

Enabled Yes
Secondary Server Database Port HTTPS 5432 TCP Inbound

Communication between the PostgreSQL datastore and the secondary TrueSight Presentation Server core

Enabled Yes
Secondary Cache Replication Port HTTPS 7800 TCP Inbound

Cache replication from secondary to primary TrueSight Presentation Server, used for high availability

Enabled Yes
Secondary Control Port HTTPS 8800 TCP Inbound

Communication between the primary and secondary TrueSight Presentation Server, used for high availability

Enabled Yes
HTTP connector port HTTP

(Windows) 80
(Linux) 8080

TCP Inbound

HTTP communication between the primary and secondary TrueSight Presentation Server, used for high availability

Enabled Yes
HTTPS connector port HTTPS

(Windows) 443
(Linux) 8043

TCP Inbound

HTTPS communication between the primary and secondary TrueSight Presentation Server, used for high availability

Enabled Yes

Tomcat Apache server

HTTP connector port

HTTP

(Windows) 80

(Linux) 8080

TCP Inbound

HTTP communication to the TrueSight Presentation Server from the TrueSight console or web services

Enabled Yes

HTTPS connector port

HTTPS

(Windows) 443

(Linux) 8043

TCP Inbound

HTTPS communication to the TrueSight Presentation Server from the TrueSight console or web services.

Requirement for deploying packages through the TrueSight console

The KM deployment feature through the TrueSight console uses the HTTPS connector port. Ensure this port is accessible from the Integration Service.

Enabled Yes

Elasticsearch

Java/Node Client

HTTPS 9300 TCP Inbound Communication between the Elasticsearch datastore and the Presentation Server core Enabled Yes

Cell Gateway

Event Ingress (TrueSight Infrastructure Management) HTTPS 1900 TCP Inbound

Communication to the TrueSight Presentation Server gateway from Infrastructure Management

Enabled Yes

PostgreSQL

PostgreSQL HTTPS 5432 TCP Inbound

Communication between the PostgreSQL datastore and the TrueSight Presentation Server core

Enabled Yes

Network ports for Infrastructure Management

Ports for Infrastructure Management Server

Component Default port number Protocol Function Default state Port configurable

JNDI

1100 TCP JBoss JNDI Enabled

After installation

Event cell 1828 TCP PATROL data collection Enabled Yes
JMS 8093 TCP JBoss JMS Server Enabled

After installation

Agent Controller 12123 TCP Agent Controller listens to the JServer on this port Enabled After installation
Web Services

80
443
TCP   Enabled Yes
Database server 2638   Used for SAP SQL Anywhere database communication   After installation
Rate 15000 TCP Connects the Agent Controller to the Rate process. 
The Rate process passively listens on port 15000 until the Agent Controller initiates contact.
  After installation
Jserver Event Server 9149       After installation

Ports for Integration Service host

Component Default port number Protocol Function Default state Port configurable
Integration Service 12124 TCP Used by the Integration Service to listen to communication from the Agent Controller. Enabled After installation
Integration Service

3183

TCP

Used by the Integration Service to listen to communication from the PATROL Agent.

Enabled After installation
Event Cell 1828 TCP

Used by the BEM Cell to listen to communication from the PATROL Agent/Remote cells.

Enabled No

Note: The KM deployment feature through the TrueSight console uses the HTTPS connector port. Ensure this port on the Presentation Server is accessible from the Integration Service.

Ports for managed host

Component Default port number Protocol Function Default state Port configurable
PATROL Agent

3181

TCP

Used by the PATROL Agent to listen to communication from the PATROL3 consoles.

Enabled Yes
           

Ports for PATROL 7 components

Component Default port number Protocol Function Default state Port configurable
RT Server

2059

TCP

Used by the RT Server to listen to communication from the PATROL 7 consoles, and PATROL Agent

Enabled Yes

Ports for Java-based administrator console

Component Default port number Protocol Function Default state Port configurable
Integration Service host
BEM Cell 1828 TCP   Enabled No
Infrastructure Management Server
RMI Registry 1099 TCP

Used by the administrator console to connect to the Infrastructure Management Server

Enabled During installation
Jserver 12128 TCP

Jserver RMI port 

Enabled During installation
IAS 3084 TCP

Enables Impact Administration Server actions to be triggered from the cell

Enabled During installation
BEM Cell 1828 TCP   Enabled No

Ports to enable Infrastructure Management and Reporting database integration

Component Default port number Protocol Function Default state Port configurable
Infrastructure Management Server
Agent Controller 12123
12126 
TCP

Agent Controller listens for JServer on this port.

Enabled During installation
Event Cell 1828 TCP   Enabled No
           
Report Engine server
Report Engine server 3783 TCP   Enabled No
Infrastructure Management Database Server
Database listener Oracle: 1521 TCP   Enabled  
SAP SQL Anywhere: 2638 TCP   Enabled  
TrueSight Operations Management Reporting Database Server
Database listener Oracle: 1521 TCP   Enabled  
  SAP SQL Anywhere: 2638  TCP   Enabled  
BMC Server Automation port       
BMC Server Automation port 9843  

BMC Server Automation port

Enabled During installation

Ports to enable integration with Atrium CMDB

Component Default port number Protocol Notes Port configurable
Infrastructure Management Server
pncell 1828 TCP    
gateway.imcomm 1839 TCP    
gateway.ibrsd 3115 TCP

Used as a gateway from the cell to the Service Desk Integration Gateway

During installation
JNDI 1100 TCP    
smmgr   TCP To configure smmgr, configure the ServerPort parameter inmcellHome/etc/cellName/smmgr.conf Yes
BMC Atrium CMDB
TCD specific port     To configure the TCD specific port, configure the C:\Program Files\BMC Software\ARSystem\Conf\ar.conf file.  
Plugin port     To configure the plugin port, configure the C:\Program Files\BMC Software\ARSystem\Conf\ar.conf file.  
Cell 1828 TCP    
UDDI 7777  

BMC Atrium CMBD port

 

During installation
TCP (Notify plug-in) 1840      
BMC Atrium Web Services
UDDI     To configure the UDDI port, C:\Program Files\BMC Software\AtriumCore\shared\tomcat\conf\server.xml  

Network ports for App Visibility Manager

Notes

  • Ensure that you open ports in your firewall to enable communication between the components.
  • If a network port is occupied, the App Visibility server component stops, as reflected in the component log, but the log message does not give the reason.

The following properties apply to all App Visibility Manager ports:

  • Flow is inbound
  • Default state is enabled

You can configure most port numbers during installation. You can configure all port numbers postinstallation:

  • Changing App Visibility portal settings
  • Changing App Visibility collector settings
  • Changing settings of the App Visibility agent for Java
  • Changing settings of the App Visibility agent for .NET
Component Protocol Default port number Function

App Visibility portal

App Visibility portal HTTPS 8100

Communication to an App Visibility portal from the following components:

  • App Visibility collectors
  • App Visibility proxies
  • App Visibility agents for Java and .NET
  • TEA Agents
  • TrueSight Presentation Server
App Visibility portal supportability HTTPS 8101 Communication to an App Visibility portal supportability console by BMC Customer Support, accessed via a browser
App Visibility portal node synchronization port HTTPS 5701 Communication with the paired portal node for HA
App Visibility portal database HTTPS 8800

Communication to the database from the App Visibility portal

Communication is local; you do not need to open a firewall for external communication.

App Visibility collector

App Visibility collector HTTPS 8200

Communication to an App Visibility collector from the following components:

  • App Visibility portal
  • App Visibility proxy
  • App Visibility agents for Java and .NET
  • TEA Agents
App Visibility collector supportability HTTPS 8201

Communication to an App Visibility collector supportability console by BMC Customer Support, accessed via a browser

App Visibility collector node synchronization port HTTPS 5702 Communication with the paired collector node for HA
App Visibility collector database HTTPS 8800

Communication to the database from the App Visibility collector

Communication is local; you do not need to open a firewall for external communication.

App Visibility proxy

App Visibility proxy HTTPS 8300 Communication to an App Visibility proxy from an App Visibility portal
App Visibility proxy supportability HTTPS 8301 Communication to an App Visibility proxy for supportability
Beacon receiver, HTTP HTTP 8304 For HTTP pages, receives beacons from the end-user's browsers
Beacon receiver, HTTPS HTTPS 8305 For HTTPS pages, receives beacons from the end-user's browsers
Storage HTTP HTTP 8302

Communication to the storage engine from the App Visibility proxy

Communication is local; you do not need to open a firewall for external communication.

Storage TCP TCP 8303

Communication between App Visibility proxy storage engine nodes in a cluster

Communication between the nodes is secured using SSL/TLS.

App Visibility agent for Java

App Visibility agent for Java supportability HTTPS 50000-50100  Communication to an App Visibility agent for Java supportability console by BMC Customer Support, accessed via a browser

App Visibility agent for .NET

App Visibility agent for .NET Not applicable Not applicable Not applicable

Synthetic TEA Agent

Synthetic Transaction Execution Adapter (TEA) Agent Not applicable Not applicable Not applicable

Network ports for Real End User Experience Management Software Edition

Note

If you change the Analyzer-to-Collector port, the BMC Real End User Experience Monitoring Software Edition user interface port also changes for users. The user interface works with the same default HTTPS port number 443 as the Real User Analyzer-to-Collector connection.
Source Destination

Service

Default Port

Protocol

Function

Default state

Port configurable

Notes

Analyzer Collector(s)

HTTPS

443

TCP

Analyzer retrieves data from the Collector(s)

Enabled

Yes

If the two components using this port are on different sides of a firewall, make sure to allow traffic through the port on your firewall.



Cloud Probe(s) Collector HTTPS 443 TCP Collector receives data from the Cloud Probe(s) Enabled Yes
TrueSight Console Analyzer(s) HTTPS 443 TCP

TrueSight console retrieves data from the Analyzer

Enabled Yes
EUEM user interface Analyzer/Collector HTTP,
HTTPS
80
443
TCP Web user interface Enabled Yes
Optional integrations

Analyzer

APM Central HTTPS 443 TCP Integration between the Analyzer and APM Central Enabled Yes
Analyzer Organization LDAP system LDAP 389 TCP Non-Secure or LDAPS (Secure LDAP, also known as LDAP over SSL) Disabled Yes

PATROL Agent

(running the BMC PATROL Knowledge Module for Application Management)

Analyzer HTTPS 443 TCP PATROL Agent retrieves data from the Analyzer so it can be used by TrueSight Infrastructure Management Enabled Yes

Third party tools

Analyzer/Collector Rest API HTTPS 443 TCP

Third party tool retrieves data from the Analyzer

Enabled Yes
Analyzer/Collector SNMP Enterprise Management System SNMP 162 UDP SNMP traps (including communication from the Analyzer to trap-based event integrations with TrueSight Infrastructure Management) Disabled Yes
SNMP Enterprise Management System Analyzer/Collector SNMP 161 UDP SNMP polling Disabled Yes

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

Comments