Port mappings
This section covers the information about the ports to map to when working with the BMC products in the BMC Cloud Lifecycle Management solution. The following topics are covered in this section:
Ports diagram
The following diagram illustrates the most common ports used in a standard BMC Cloud Lifecycle Management deployment.
Port information
The following table lists the most commonly used port numbers (0 - 1023) and BMC suggested port numbers. Ports with an asterisk (*) indicate custom definable ports. Ensure that the ports that you select do not conflict with the ports that are currently in use in the installation environment.
| Product | Component/Module | Port # | Protocol |
|---|---|---|---|
| BMC AR System Server (Cloud Portal and Database) | AR Port | 4100* | TCP/UDP |
| AR Plugin Port | 4101* | TCP/UDP | |
| AR Plugin Port | 9999 | TCP | |
| CMDB Plugin Port | 9556* | TCP/UDP | |
| Normalization Engine Plugin Port | 9555* | TCP | |
| Cloud Plugin Port | 9899 | TCP/UDP | |
| Flashboard Server RMI Port | 1099* | TCP | |
Email Engine RMI Port | 1100* | TCP | |
BMC Server Automation | AuthSvcPort (Authentication) Port | 10840 | TCP/UDP |
AppSvcPort (Config) Port | 10841 | TCP/UDP | |
| Mid Tier | HTTP | 8080* | TCP |
HTTPS | 9443* | TCP/UDP | |
Atrium Core - Web Registry | HTTP | 9090* | TCP |
HTTPS | 9443* | TCP/UDP | |
BMC Network Automation | HTTP | 8080* | TCP |
HTTPS | 9443* | TCP/UDP | |
Cloud Platform Manager | API HTTP | 8080 | TCP |
HTTP | 9000 | TCP | |
BMC Atrium Orchestrator | Access Manager (User Defined) | 18080 | TCP |
CDP (User Defined) | 28080 | TCP | |
| CLM Self-Check Monitor | HTTPS | 8443 | TCP/UDP |
| HTTP | 443 | TCP/UDP | |
| RSCD port | 4750 | TCP/UDP | |
| Tomcat Start Port | 8090 | TCP/UDP | |
| Tomcat Stop Port | 8007 | TCP/UDP | |
| Cloud Portal Web Application | HTTPS | 8443 | TCP/UDP |
| HTTP | 443 | TCP/UDP | |
| Tomcat Start Port | 9070 | TCP/UDP | |
| Tomcat Start Port | 9005 | TCP/UDP |
Product integration port information
The following ports are the most commonly used ports for BMC Cloud Lifecycle Management traffic. These port numbers are either the default port number when installing the software or the port number that is most commonly used for the specific type of traffic. You can change most of these port numbers according to individual deployment requirements.
| Destination | |||||||||
|---|---|---|---|---|---|---|---|---|---|
Source | BMC AR System Server (Cloud Portal and Database) | Cloud Platform Manager | Atrium Core Web Registry | Mid Tier | BMC Network Automation | BMC Server Automation | BMC Atrium Orchestrator | Virtual Center | Clients/ Agents |
Mid Tier | 4100 | 8080/9443 (for Service Designer) 9000 (for Quick Start) | |||||||
BMC AR System Server (Cloud Portal and Database) | 8080 | 28080 | |||||||
Cloud Platform Manager | 8080/9443 | 8080/9443 | 10843 | 28080 | |||||
Atrium Core - Web Registry | 4100 | ||||||||
BMC Network Automation | 9090/9443 | ||||||||
BMC Server Automation | 4100 | 443 | 4750 | ||||||
BMC Atrium Orchestrator | 4100 | ||||||||
| CLM Self-Check Monitor | 8443/443 | 4750 (RSCD) | |||||||
| Cloud Portal Web Application | 8443 | ||||||||
Virtual Center | 9443 | ||||||||
Clients/Agents | 8080/9443 | ||||||||
Encryption information
The following graphic shows the secure communication configuration between the CLM components.
The following table shows which communications strings you can encrypt between the various components. HTTPS ports are web-based communications using SSL to encrypt. TCP ports are all other ports, whose port numbers are configurable and use DES encryption out of the box.
You can configure these ports within the AR System server configuration settings on the Encryption tab. You must set the New Encryption Settings - Security Policy to Required and Data Key Details - Algorithm Options to DES.
You can also upgrade the DES encryption to use more advanced encryption algorithms via the Performance and Premium upgrade packages.
| Destination | |||||||||
|---|---|---|---|---|---|---|---|---|---|
Source | BMC AR System Server (Cloud Portal and Database) | Cloud Platform Manager | Atrium Core - Web Registry | Mid Tier | BMC Network Automation | BMC Server Automation | BMC Atrium Orchestrator | Virtual Center | Clients/ Agents |
Mid Tier | DES | ||||||||
BMC AR System Server - Cloud Portal and Database | DES | HTTPS | |||||||
Cloud Platform Manager | HTTPS | HTTPS | HTTPS | HTTPS | |||||
Atrium Core - Web Registry | DES | ||||||||
BMC Network Automation | HTTPS | ||||||||
BMC Server Automation | DES | HTTPS | HTTPS | ||||||
BMC Atrium Orchestrator | DES | ||||||||
| CLM Self-Check Monitor | HTTPS | ||||||||
| Cloud Portal Web Application | HTTPS | ||||||||
Virtual Center | HTTPS | ||||||||
Clients/Agents | HTTPS | ||||||||
Use cases
The following table covers various use cases for the BMC Cloud Lifecyle Management products.
Use Case | Steps | Ports |
|---|---|---|
| Quick Start | Open the AR port to the AR System Server (Cloud Portal and Database) | Mid Tier port – 8080/9443 |
| Open the port to the Platform Manager for Quick Start | Platform Manager Port for Quick Start - 9000 by default | |
Onboard POD | ||
User logs in as Cloud Admin using Mid Tier. | Mid Tier port – 8080/9443 | |
Cloud Portal and Database provides task details to Platform Manager. | Platform Manager Port - 8080 | |
Platform Manager requests for POD details from BMC Network Automation using web service call. | BMC Network Automation Port – 8080/9443 | |
POD details are stored in the cache directory of Platform Manager. | ||
Platform Manager updates the task to the Cloud Portal and Database server through Mid Tier. | Mid Tier port – 8080/9443 | |
Platform Manager creates an entry of POD in BMC.Core:BMC_ConcreteCollection. | Cloud Portal and Database Port - 4000 | |
BMC.Core:BMC_ConcreteCollection form data is added to Cloud Portal and Database DB in BMC.ASSET dataset. | Cloud Portal and Database Port - 4000 | |
Onboard Resource - Virtual Cluster | ||
User logs in as Cloud Admin using Mid Tier. | Mid Tier port – 8080/9443 | |
Cloud Portal and Database provides task details to Platform Manager. | Platform Manager Port - 8080 | |
Platform Manager gets the details of the resource from BMC Server Automation that were cached during caching. | BMC Server Automation Port - 10843 | |
Resource details are stored in the cache directory of Platform Manager during caching. | ||
Platform Manager updates the task to the Cloud Portal and Database server through Mid Tier. | Mid Tier port – 8080/9443 | |
Platform Manager creates an entry of Virtual cluster in BMC.Core:BMC_Cluster. | Cloud Portal and Database Port - 4000 | |
BMC.Core:BMC_Cluster form data is added to Cloud Portal and Database in BMC.ASSET dataset. | Cloud Portal and Database Port - 4000 | |
Create Network Container | ||
User logs in as Cloud Admin using Mid Tier. | Mid Tier Port – 8080/9443 | |
Cloud Portal and Database provides task details to the Platform Manager. | Platform Manager Port - 8080 | |
Cloud Portal and Database creates an entry on the CMF:Network_v. | ||
Platform Manager creates a job in BMC Network Automation for container creation. | BMC Network Automation Port – 8080/9443 | |
BMC Network Automation executes the job and performs all tasks on the devices. | ||
Platform Manager polls the job details from BMC Network Automation. | BMC Network Automation Port – 8080/9443 | |
Platform Manager creates the entry of container in BMC.ASSET in BMC.Core:BMC_ConcreteCollection. | Cloud Portal and Database Port - 4000 | |
Network container details are added to Cloud Portal and Database server in BMC.ASSET dataset. | Cloud Portal and Database Port - 4000 | |
Create Blueprint | ||
User logs in as Cloud Admin using Mid Tier. | Mid Tier port – 8080/9443 | |
Blueprint details are stored in BMC.Core:BMC_Document form in BMC.ASSET dataset. | ||
Create Service Offering | ||
User logs in as Cloud Admin using Mid Tier. | Mid Tier port – 8080/9443 | |
Requestable Offering details are stored in BMC.Core:BMC_requestableoffering form in BMC.ASSET dataset. | ||
Create Service Request Instance | User logs in to the My Cloud Services Console as Cloud User. | My Cloud Services Console port: 8443 |
User logs in to legacy My Cloud Services Console as Cloud User. | Mid Tier Port – 8080/9443 | |
User creates a service request instance (SRM) Enterprise. | Cloud Portal and Database Port - 4000 | |
Change is created for the service request, if Change Management is integrated on a remote ITSM server. | ||
Cloud Task is created and details are submitted to Platform Manager (Cloud Plugin on Cloud Portal and Database). | Platform Manager Port - 8080 | |
BMC Server Automation clones the VM in VC. | vCenter port - 443 | |
After cloning job is executed, BMC Server Automation executes Update Server Properties job to check the status of agent. | RSCD Port - 4750 | |
BMC Server Automation executes the user creation / modification job. | RSCD Port - 4750 | |
Platform Manager creates an entry in Cloud Portal and Database DB server BMC.Core:ComputerSystem form in BMC.ASSET. | Cloud Portal and Database Port - 4000 | |
BMC.Core:ComputerSystem form data is added to Cloud Portal and Database server. The data would be saved in BMC.ASSET. | Cloud Portal and Database Port - 4000 | |
Tasks details are updated in the Cloud Portal and Database server from the Platform Manager using Callback URL. | Mid Tier Port - 9443 |
Installer host port requirements
The installer uses specific ports to connect to the target computers. Ensure that the firewall allows communication from the BMC Cloud Lifecycle Management installer host to the target computers, using the ports listed in the following tables.
Windows port requirements
If a firewall is configured in your environment, ensure that the firewall allows communication from the BMC Cloud Lifecycle Management installer host to the target computers by using the ports listed in the following table. The installer uses these ports to run commands to check application connectivity, database connections, RSCD connectivity, remote installation status, and so on. The port numbers in the table are the default values and might change based on user input or user environment configuration. For example, the database might be installed on port 1522 instead of port 1521. In that case, you must ensure that the port is enabled in the firewall.
Note
| Component | Port number | Description |
|---|---|---|
| BMC Cloud Lifecycle Management Install Planner | 12333, 9998, 22 | Installer ports On the BMC Cloud Lifecycle Management installer host, ensure that port 12333 is free for the install planner. The BMC Cloud Lifecycle Management installer executes product installations remotely using a silent installation. The product installations that are launched on the target hosts use port 12333 or 9998 (for BladeLogic Server Automation), as applicable, during invocation on the target host. The BMC Cloud Lifecycle Management installer queries the ports over the network to check whether the installation launched successfully. If a firewall is between the BMC Cloud Lifecycle Management installer host and a target host, ensure that these ports are not blocked. SSH port 22 is required for the installer to authenticate credentials of target host as well as the SCP connection for RSCD installer copy. This requirement applies to all product hosts. |
| BMC Remedy AR System server (AR System server) and IT Management Suite | 0 (default value if the portmapper is being used) | Cloud Portal and Database server, AR System server post-installation , and Cloud Portal AR Extensions port The default value on which Cloud Portal and Database server is installed by the BMC Cloud Lifecycle Management installer is port 0 if the AR System portmapper is being used. The BMC Cloud Lifecycle Management installer queries the port (chosen randomly by the portmapper) over the network during AR System server post-installation to check whether the AR System server is running. Make sure there is no firewall is between the BMC Cloud Lifecycle Management installer host and a target host. |
| 1433 (default value) | Cloud Portal and Database server database port When the BMC Cloud Lifecycle Management installer installs Cloud Portal and Database, the installer attempts to connect to the database using the user-supplied database port to ensure that the database is up and running. If the target Oracle database is installed using default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked. | |
| BMC Server Automation | 1433 (default value) | BMC Server Automation database port When the BMC Cloud Lifecycle Management installer installs BMC Server Automation installation, the installer attempts to ensure that the database is running by connecting to it through the user-supplied port. If the target Oracle database is installed using the default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked. |
| 4750 | BMC Server Automation RSCD agent port This requirement applies to all hosts (product hosts as well as the BMC Cloud Lifecycle Management installer host). If a firewall is between the BMC Cloud Lifecycle Management installer and a target host, ensure that port 4750 is not blocked, because the BMC Cloud Lifecycle Management installer runs remote commands for target host installations to the RSCD agent on the target host (which uses port 4750). | |
| BMC Network Automation | 1433 (default value) | BMC Network Automation database port When the BMC Cloud Lifecycle Management installer installs the BMC Network Automation, the installer attempts to ensure that the database is running by connecting to it through the user-supplied port. If the target Oracle database is installed using the default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked. |
| Preboot Execution Environment (PXE) | 1433 (default value) | When the BMC Cloud Lifecycle Management installer installs PXE, the installer attempts to connect to the database using the user-supplied database port to ensure that the database is up and running. If the target Oracle database is installed using the default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked. |
Linux port requirements
If a firewall is configured in your environment, ensure that the firewall allows communication from the BMC Cloud Lifecycle Management installer host to the target computers by using the ports listed in The following section. The installer uses these ports to run commands to check application connectivity, database connections, RSCD connectivity, remote installation status, and so on. The port numbers in the table are the default values and might change based on user input or user environment configuration. For example, the database might be installed on port 1522 instead of port 1521. In that case, you must ensure that the correct port is enabled in the firewall.
Note
The Cloud Portal and Database server is installed by default on portmapper; the port number assigned in that case is port 0. For the Cloud Portal and Database server, the port number cannot be changed during the installation.
| Component | Port number | Description |
|---|---|---|
| BMC Cloud Lifecycle Management installation program | 12333, 9998, 22 | Installer ports On the BMC Cloud Lifecycle Management installer host, ensure that port 12433 is free for the install planner. The BMC Cloud Lifecycle Management installer runs product installations remotely, using a silent installation. The product installations that are launched on the target hosts use port 12433 or 9998 (for BladeLogic Server Automation), as applicable, during invocation on the target host. The BMC Cloud Lifecycle Management installer queries the ports over the network to check whether the installation launched successfully. If a firewall is between the BMC Cloud Lifecycle Management installer host and a target host, ensure that these ports are not blocked. SSH port 22 is required for the installer to authenticate credentials of target host as well as the SCP connection for RSCD installer copy. |
| BMC AR System Server - Cloud Portal and Database - Primary | 0 (default value) | Cloud Portal and Database server, AR System server post-installation, and Cloud Portal AR Extensions port The default port on which Cloud Portal and Database server is installed by the BMC Cloud Lifecycle Management installer is port 0. The BMC Cloud Lifecycle Management installer queries the port over the network during AR System server post-installation to check whether the AR System server is running. If a firewall is between the BMC Cloud Lifecycle Management installer host and a target host, ensure that this port is not blocked. |
| 1521 (default value) | Cloud Portal and Database server database port When installing Cloud Portal and Database, the installer attempts to ensure that the database is running by connecting to it through the user-supplied port. If the target Oracle database is installed using default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked. | |
| BMC Server Automation | 1521 (default value) | BMC Server Automation database port When installing BMC Server Automation, the installer attempts to ensure that the database is running by connecting to it through the user-supplied port. If the target Oracle database is installed using the default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked. |
| 4750 | BMC Server Automation RSCD agent port This requirement applies to all hosts (product hosts as well as the BMC Cloud Lifecycle Management installer host). If a firewall is between the BMC Cloud Lifecycle Management installer and a target host, ensure that port 4750 is not blocked, because the BMC Cloud Lifecycle Management installer executes remote commands for target host installations to the RSCD agent on the target host (which uses port 4750). | |
| BMC Network Automation | 1521 (default value) | BMC Network Automation database port When installing BMC Network Automation, the installer attempts to ensure that the database is running by connecting to it through the user-supplied port . If the target Oracle database is installed using the default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked. |
| Preboot Execution Environment (PXE) | 1521 (default value) | Requires the BMC Server Automation database port for PXE provisioning When installing PXE, the installer attempts to ensure that the database is running by connecting to it through the user-supplied port . If the target Oracle database is installed using the default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked. |
Comments
Log in or register to comment.