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:

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
Installer Planner	Installer Port	12333	TCP/UDP
	Installer Port	9998	TCP/UDP
	Installer Port	22	TCP/UDP
Enterprise AR System Server & ITSM Management Suite	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
Cloud Database	AR Port	4000*	TCP/UDP
	AR Plugin Port	4001*	TCP
	AR Plugin Port	9999	TCP/UDP
	CMDB Plugin Port	9556	TCP/UDP
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

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	Enterprise AR System Server & ITSM Management Suite	Cloud Database	Cloud Platform Manager	Atrium Core - Web Registry	Enterprise AR System - Mid Tier	BMC Network Automation	BMC Server Automation	BMC Atrium Orchestrator	BMC ProactiveNet Performance Management	Virtual Center	Clients/ Agents
Mid Tier	4100		8080/9443 (for Service Designer) 9000 (for Quick Start)
Enterprise AR System Server & ITSM Management Suite		4000	8080					28080
Cloud Database	4100
Cloud Platform Manager		4000			8080/9443	8080/9443	10843	28080	80/443
Atrium Core - Web Registry	4100
BMC Network Automation				9090/9443
BMC Server Automation	4100									443	4750
BMC Atrium Orchestrator	4100
BMC ProactiveNet Performance Management							10843
Virtual Center							9443
Clients/Agents					8080/9443

Encryption information

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	Enterprise AR System Server & ITSM Management Suite	Cloud Database	Cloud Platform Manager	Atrium Core - Web Registry	Enterprise AR System - Mid Tier	BMC Network Automation	BMC Server Automation	BMC Atrium Orchestrator	BMC ProactiveNet Performance Management	Virtual Center	Clients/ Agents
Mid Tier	DES
Enterprise AR System Server & ITSM Management Suite		DES	DES					HTTPS
Cloud Database	DES
Cloud Platform Manager		DES			HTTPS	HTTPS	HTTPS	HTTPS	HTTPS
Atrium Core - Web Registry	DES
BMC Network Automation				HTTPS
BMC Server Automation	DES									HTTPS	HTTPS
BMC Atrium Orchestrator	DES
BMC ProactiveNet Performance Management
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
	Enterprise AR 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 enterprise server through Mid Tier.	Mid Tier port – 8080/9443
	Platform Manager creates an entry of POD in BMC.Core:BMC_ConcreteCollection.	Cloud Database Port - 4000
	BMC.Core:BMC_ConcreteCollection form data is DSOed from Cloud DB to Enterprise DB in BMC.IMPORT.CSM dataset.	Enterprise AR Port - 4100
	RE Job is executed and the POD information in BMC.Core:BMC_ConcreteCollection is copied to BMC.Asset dataset.
Onboard Resource - Virtual Cluster
	User logs in as Cloud Admin using Mid Tier.	Mid Tier port – 8080/9443
	Enterprise AR 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 enterprise server through Mid Tier.	Mid Tier port – 8080/9443
	Platform Manager creates an entry of Virtual cluster in BMC.Core:BMC_Cluster.	Cloud Database Port - 4000
	BMC.Core:BMC_Cluster form data is DSOed from Cloud DB to Enterprise AR in BMC.IMPORT.CSM dataset.	Enterprise AR Port - 4100
	RE Job is executed and the POD information in BMC.Core:BMC_Cluster is copied to BMC.Asset dataset on Enterprise AR Server.
Create Network Container
	User logs in as Cloud Admin using Mid Tier.	Mid Tier Port – 8080/9443
	Enterprise AR provides task details to the Platform Manager.	Platform Manager Port - 8080
	Enterprise AR 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 cloud db BMC.ASSET in BMC.Core:BMC_ConcreteCollection.	Cloud Database Port - 4000
	Network container details are DSOed from Cloud DB server to Enterprise AR server in BMC.IMPORT.CSM dataset.	Enterprise AR port- 4100
	RE Job is executed and the Network container details are copied to BMC.ASSET.
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.
	BMC.Core:BMC_Document form data is DSOed from Enterprise AR server to Cloud DB AR server in BMC.Import.Enterprise dataset.	Cloud Database Port - 4000
	RE Job is executed and the blueprint information is move to BMC.Asset dataset in Cloud DB server.
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.
	BMC.Core:BMC_RequestableOffering form data is DSOed from Enterprise AR server to Cloud DB AR server in BMC.Import.Enterprise dataset.	Cloud Database Port - 4000
	RE Job is executed and the requestable offering information is move to BMC.Asset dataset in Cloud DB server.
Create Service Request Instance
	User logs in as Cloud User.	Mid Tier Port – 8080/9443
	User creates a service request instance (SRM) Enterprise.	Enterprise AR port - 4100
	Change is created for the service request (ITSM).
	Cloud Task is created and details are submitted to Platform Manager (Cloud Plugin on the Enterprise AR).	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 DB server BMC.Core:ComputerSystem form in BMC.ASSET.	Cloud Database port - 4000
	BMC.Core:ComputerSystem form data is DSOed from Cloud DB server to Enterprise server. The data would be saved in BMC.IMPORT.CSM.	Enterprise AR port - 4100
	Tasks details are updated in the enterprise 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, 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 number in the table is the default value 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

Enterprise AR System server and cloud AR System server are installed by default on portmapper; the port number assigned in that case is port 0. For the enterprise AR System server, the port number cannot be changed during the install, but it can be changed for the cloud AR System server.

Component	Port number	Description
BMC Cloud Lifecycle Management Install Planner	12333, 9998	Installer ports On the BMC Cloud Lifecycle Management installer host, ensure that port 12433 is free. 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, 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. This requirement is applicable for all product hosts.
BMC Remedy AR System server (AR System server) and IT Management Suite	0 (default value if the portmapper is being used)	Enterprise AR System server, AR System server post-installation, Distributed Server Option (DSO),and Cloud Portal AR Extensions port The default value on which Enterprise AR System 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 and DSO 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)	Enterprise AR System server database port During the Enterprise AR System server installation using the BMC Cloud Lifecycle Management installer, 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.
AR System server - Cloud Database	0 (default value if the portmapper is being used)	Cloud AR System server, AR System server post-install, DSO, and Cloud Extensions port The default value on which the AR System Cloud Database server is installed using the BMC Cloud Lifecycle Management installer is port 0 if the portmapper is being used. The BMC Cloud Lifecycle Management installer queries the port (chosen randomly by the portmapper) over the network during the AR System server post-installation and DSO installation to check whether the AR System server is up and running. Make sure there is no firewall is between the BMC Cloud Lifecycle Management installer host and a target host.
	1433 (default value)	Cloud AR System server database port During the AR System server - Cloud Database installation using the BMC Cloud Lifecycle Management installer, the installer attempts to connect to the database using the user-supplied database port to ensure that the database is 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.
BMC Server Automation	1433 (default value)	BMC Server Automation database port During the BMC Server Automation installation using the BMC Cloud Lifecycle Management installer, the installer attempts to connect to the database using the user-supplied database port to ensure that the database is 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.
	4750	BMC Server Automation RSCD agent port This requirement is applicable for 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 During the BMC Network Automation install using the BMC Cloud Lifecycle Management installer, the installer attempts to connect to the database using the user-supplied database port to ensure that the database is 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.
BMC ProactiveNet Performance Management	10843 (default value)	Requires port for BMC Server Automation web services During the BMC ProactiveNet Performance Management installation using the BMC Cloud Lifecycle Management installer, the installer executes commands over the network to check whether the BMC Server Automation web service is running. The BMC ProactiveNet Performance Management connects to BMC Server Automation using the same port to load BMC Server Automation packages.
Preboot Execution Environment (PXE)	1433 (default value)	During the PXE install using the BMC Cloud Lifecycle Management installer, 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.

For more information about the ports used by BMC Cloud Lifecycle Management, see Port mappings.

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 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 number in the table is the default value 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.