The following table lists the default configurations of protocols and ports for different components and services used by various 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 BMC Atrium Single Sign-On

ComponentServiceDefault port numberProtocolFlowFunctionDefault statePort configurable

HTTPS

HTTPS8443TCPInboundCommunication to the Presentation Server from the BMC Atrium SSO for authentication and authorizationEnabledYes

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)

HTTP9200TCPInboundCommunication to the Presentation Server from Elasticsearch pluginEnabledYes

Java/Node Client

HTTP9300TCPInboundCommunication 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 JNDIEnabledAfter installation
Event cell1828TCPPATROL data collectionEnabledYes
RMI12100TCP EnabledNo
JMS8093TCPJBoss JMS ServerEnabled

After installation

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

 

80
443
TCP EnabledYes
Admin Cell1827TCP

PATROL data collection

EnabledNo
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

1 Out-of-the-box dynamic 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.

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
Admin Cell1827TCP EnabledNo
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 Integration for BMC Remedy Service Desk***

 

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 
Integration for BMC Remedy Service Desk**
TCP3115 Must be configured on BMC Remedy AR Server 
TCP1828 Must be configured on BMC Remedy AR Server to communicate with the cell 
Other ports 1828 – 1840   

Network ports for App Visibility Manager

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

Note

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.

ComponentServiceDefault port numberProtocolFlowFunctionDefault statePort configurable

App Visibility portal

App Visibility portalHTTPS8100TCPInboundCommunication to an App Visibility portal from an App Visibility collector, proxy, and agent, and the TrueSight Presentation Server
EnabledYes
App Visibility portal supportabilityHTTPS8101TCPInboundCommunication to an App Visibility portal for supportabilityEnabledYes
App Visibility portal control portHTTPS8102TCPInboundCommunication with the paired portal node for HAEnabledYes

App Visibility collector

App Visibility collectorHTTPS8200TCPInboundCommunication to an App Visibility collector from an App Visibility portal, proxy, and agentEnabledYes
App Visibility collector supportabilityHTTPS8201TCPInboundCommunication to an App Visibility collector for supportabilityEnabledYes
App Visibility collector control portHTTPS8202TCPInboundCommunication with the paired collector node for HAEnabledYes

App Visibility proxy

App Visibility proxyHTTPS8300TCPInboundCommunication to an App Visibility proxy from an App Visibility portal
EnabledYes
App Visibility proxy supportabilityHTTPS8301TCPInboundCommunication to an App Visibility proxy for supportabilityEnabledYes
Beacon receiver, HTTPHTTP880

TCP

InboundFor HTTP pages, receives beacons from the end-user's browsersEnabledYes
Beacon receiver, HTTPSHTTPS8444TCPInboundFor HTTPS pages, receives beacons from the end-user's browsersEnabledYes

App Visibility database

App Visibility databaseHTTPS8800TCPInboundCommunication to the App Visibility database from an App Visibility portal and collectorEnabledYes

App Visibility agent for Java supportability

App Visibility agent for Java supportabilityHTTPS50000-50100 TCPInboundCommunication to an App Visibility agent for supportabilityEnabledYes

App Visibility agent for .NET

App Visibility agent for .NETNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicable

Synthetic TEA Agent

Synthetic Transaction Execution Adapter (TEA) AgentNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicable

Network ports for Real End User Experience Management-Software Edition

Component

Service

Default port number

Protocol

Flow

Function

Default state

Port configurable

Notes

 

HTTPS

443

TCP

Inbound

Management UI

Enabled

Yes

Hardened Apache/Tomcat

Execution logsHTTPS443TCPInboundLog retrievalDisabledYes 

TrueSight Console and Real User Analyzer

Real User Analyzer and Collector

Real User Collector and a Cloud Probe

REST API calls between systems

Analyzer and a PATROL Agent
(Runs the BMC PATROL Knowledge Module for End User Experience Management)

HTTPS443TCPOutbound

Communication between the components and systems

EnabledYes

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.

If the Real User Collector and Analyzer are installed on the same machine, the Collector uses port 8443 for the incoming connections from the Cloud Probes. Be sure to configure port 8443 as the Collector port when installing the Cloud Probe.

 

HTTP

80

TCP

Inbound

Redirect to 443 for UI

Enabled

Yes

Hardened Apache/Tomcat

Execution logsHTTP80TCPInboundLog retrievalDisabledYes 
User account authenticationLDAP389TCPOutboundLDAP user account authenticationDisabledYesNon-Secure or LDAPS (Secure LDAP, also known as LDAP over SSL)
Network traffic collection by the Real User Analyzer

RcSP

 

22031

22032

22033

TCP

Inbound

  • Port 22031 streams Objects
  • Port 22032 streams Pages
  • Port 22033 streams Sessions
EnabledNo

TLS/SSLv3 secure

Record Streaming Protocol (RcSP) is a BMC proprietary protocol.

Note

 For outbound communication, the ports listed are the ports to which a component connects.

 

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

7 Comments

  1.  

  2.  

  3. The 'Function' wording for this SSO port is confusing:

    HTTPS

    HTTPS8443TCPInboundCommunication to the Presentation Server from the BMC Atrium SSO for authentication and authorizationEnabledYes

    Please can we change it to the following:

    ‘Communication from the Presentation Server to the BMC Atrium SSO for authentication and authorization’ 

  4.  

  5.  

  6.  

  7.  

© Copyright 2013-2016 BMC Software, Inc.
© Copyright 2013-2016 BladeLogic, Inc.
Legal notices