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:

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

ComponentServiceDefault port numberProtocolFlowFunctionDefault statePort configurable
HTTPHTTP

8080

Remedy SSO for TrueSight

  • 88 (Windows)
  • 8088 (Linux)
TCPInbound

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

DisabledYes

HTTPS

HTTPS

8443

Remedy SSO for TrueSight

  • 448 (Windows)
  • 8048 (Linux)
TCPInbound

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

EnabledYes

Shutdown port

HTTPS8005TCPInboundShutdown port for the Tomcat web serverEnabledYes

Network ports for Presentation Server

ComponentServiceDefault port numberProtocolFlowFunctionDefault statePort configurable

High Availability

Cache Replication PortHTTPS7800TCPInboundCache replication from primary to secondary Presentation Server, used for high availabilityEnabledYes
Control PortHTTPS8800TCPInboundCommunication between the primary and secondary Presentation Server, used for high availabilityEnabledYes
Secondary Server Database PortHTTPS5432TCPInboundCommunication between the PostgreSQL datastore and the secondary Presentation Server coreEnabledYes
Secondary Cache Replication PortHTTPS7800TCPInboundCache replication from secondary to primary Presentation Server, used for high availabilityEnabledYes
Secondary Control PortHTTPS8800TCPInboundCommunication between the primary and secondary Presentation Server, used for high availabilityEnabledYes

Tomcat Apache server

HTTP connector port

HTTP

(Windows) 80

(Linux) 8080

TCPInboundHTTP communication to the Presentation Server from the TrueSight console or web servicesEnabledYes

HTTPS connector port

HTTPS

(Windows) 443

(Linux) 8043

TCPInbound

HTTPS communication to the 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.

EnabledYes

Elasticsearch

Representational State Transfer (REST)

HTTPS9200TCPInboundCommunication to the Presentation Server from Elasticsearch pluginEnabledYes

Java/Node Client

HTTPS9300TCPInboundCommunication between the Elasticsearch datastore and the Presentation Server coreEnabledYes

Cell Gateway

Event Ingress (TrueSight Infrastructure Management)HTTPS1900TCPInboundCommunication to the Presentation Server gateway from Infrastructure ManagementEnabledYes

PostgreSQL

PostgreSQLHTTPS5432TCPInboundCommunication between the PostgreSQL datastore and the Presentation Server coreEnabledYes

Network ports for Infrastructure Management

Ports for Infrastructure Management Server

ComponentDefault port numberProtocolFunctionDefault statePort configurable

JNDI

1100TCPJBoss JNDIEnabled After installation
Event cell1828TCPPATROL data collectionEnabledYes
JMS8093TCPJBoss JMS ServerEnabled

After installation

Agent Controller12123TCPAgent Controller listens to the JServer on this portEnabledAfter installation
Web Services

80
443
TCP EnabledYes
Database server2638 Used for SAP SQL Anywhere database communication After installation
Rate15000TCPConnects 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 Server9149   After installation

Open Port 2100

If you are using an Infrastructure Management server version 10.5 connected to the Presentation Sever version 11.0, then you must open port 2100 for the connection to be successful. For more information on ports for version 10.5, see Network ports for Infrastructure Management and Setting RMI port.

Ports for Integration Service host

ComponentDefault port numberProtocolFunctionDefault statePort configurable
Integration Service12124TCPUsed by the Integration Service to listen to communication from the Agent Controller.EnabledAfter installation
Integration Service

3183

TCP

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

EnabledAfter installation
Event Cell1828TCP

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

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

For more details on port schematics, see Network port schematics for Infrastructure Management.

Ports for managed host

ComponentDefault port numberProtocolFunctionDefault statePort configurable
PATROL Agent

3181

TCP

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

EnabledYes
      

Ports for PATROL 7 components

ComponentDefault port numberProtocolFunctionDefault statePort configurable
RT Server

2059

TCP

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

EnabledYes

Ports for Java-based administrator console

ComponentDefault port numberProtocolFunctionDefault statePort configurable
Integration Service host
BEM Cell1828TCP EnabledNo
Infrastructure Management Server
RMI Registry1099TCP

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

EnabledDuring installation
Jserver12128TCP

Jserver RMI port 

EnabledDuring installation
IAS3084TCP

Enables Impact Administration Server actions to be triggered from the cell

EnabledDuring installation
BEM Cell1828TCP EnabledNo

Ports to enable Infrastructure Management and Reporting database integration

ComponentDefault port numberProtocolFunctionDefault statePort configurable
Infrastructure Management Server
Agent Controller12123
12126 
TCP

Agent Controller listens for JServer on this port.

EnabledDuring installation
Event Cell1828TCP EnabledNo
      
Report Engine server
Report Engine server3783TCP EnabledNo
Infrastructure Management Database Server
Database listenerOracle: 1521TCP Enabled 
SAP SQL Anywhere: 2638TCP Enabled 
TrueSight Operations Management Reporting Database Server
Database listenerOracle: 1521TCP Enabled 
 SAP SQL Anywhere: 2638 TCP Enabled 
BMC Server Automation port       
BMC Server Automation port9843 

BMC Server Automation port

EnabledDuring installation

Ports to enable integration with Atrium CMDB

ComponentDefault port numberProtocolNotesPort configurable
Infrastructure Management Server
pncell1828TCP  
gateway.imcomm1839TCP  
gateway.ibrsd3115TCP

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

During installation
JNDI1100TCP  
smmgr TCPTo configure smmgr, configure the ServerPort parameter inmcellHome/etc/cellName/smmgr.confYes
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. 
Cell1828TCP  
UDDI7777 

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:

  • Protocol is TCP
  • 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 App Visibility proxy settings
  • Changing settings of the App Visibility agent for Java
  • Changing settings of the App Visibility agent for .NET

ComponentServiceDefault port numberFunction

App Visibility portal

App Visibility portalHTTPS8100

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 supportabilityHTTPS8101Communication to an App Visibility portal supportability console by BMC Customer Support, accessed via a browser
App Visibility portal control portHTTPS8102Communication with the paired portal node for HA
App Visibility portal databaseHTTPS8800

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 collectorHTTPS8200

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 supportabilityHTTPS8201

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

App Visibility collector control portHTTPS8202Communication with the paired collector node for HA
App Visibility collector databaseHTTPS8800

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 proxyHTTPS8300Communication to an App Visibility proxy from an App Visibility portal
App Visibility proxy supportabilityHTTPS8301Communication to an App Visibility proxy for supportability
Beacon receiver, HTTPHTTP880For HTTP pages, receives beacons from the end-user's browsers
Beacon receiver, HTTPSHTTPS8444For HTTPS pages, receives beacons from the end-user's browsers

App Visibility agent for Java

App Visibility agent for Java supportabilityHTTPS50000-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 .NETNot applicableNot applicableNot applicable

Synthetic TEA Agent

Synthetic Transaction Execution Adapter (TEA) AgentNot applicableNot applicableNot 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.
SourceDestination

Service

Default Port

Protocol

Function

Default state

Port configurable

Notes

AnalyzerCollector(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)CollectorHTTPS443TCPCollector receives data from the Cloud Probe(s)EnabledYes
TrueSight ConsoleAnalyzer(s)HTTPS443TCP

TrueSight console retrieves data from the Analyzer

EnabledYes
EUEM user interfaceAnalyzer/CollectorHTTP,
HTTPS
80
443
TCPWeb user interfaceEnabledYes
Optional integrations

Analyzer

APM CentralHTTPS443TCPIntegration between the Analyzer and APM CentralEnabledYes
AnalyzerOrganization LDAP systemLDAP389TCPNon-Secure or LDAPS (Secure LDAP, also known as LDAP over SSL)DisabledYes

PATROL Agent

(running the BMC PATROL Knowledge Module for Application Management)

AnalyzerHTTPS443TCPPATROL Agent retrieves data from the Analyzer so it can be used by TrueSight Infrastructure ManagementEnabledYes

Third party tools

Analyzer/Collector Rest APIHTTPS443TCP

Third party tool retrieves data from the Analyzer

EnabledYes
Analyzer/CollectorSNMP Enterprise Management SystemSNMP162UDPSNMP traps (including communication from the Analyzer to trap-based event integrations with TrueSight Infrastructure Management)DisabledYes
SNMP Enterprise Management SystemAnalyzer/CollectorSNMP161UDPSNMP pollingDisabledYes

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

Comments

  1. John Clitheroe

    Surely this page should also include, in the first table, the Windows and Linux RSSO ports 448/88 and 8088/8048, as used by the TrueSight installer for RSSO. The ones on the current page are for the separate Tomcat installation using the RSSO installer.

    Feb 18, 2019 06:26
    1. Harihara Subramanian

      Hi John Clitheroe

      Updating the doc. Will let you know once I publish the changes.


      Feb 19, 2019 02:19
  2. John Clitheroe

    Hi Harihara. The first table is still slightly wrong. The HTTP/HTTPS ports for Windows are 88/448 and those for Linux are 8088/8048. Apologies if my original comment was confusing. The diagram on the 'Network Port schematics for Infrastructure Management' page has the correct ports listed.

    Apr 09, 2019 06:00
    1. Harihara Subramanian

      Hi John Clitheroe,

      Updated. Please check.

      Apr 09, 2019 06:17