Linux installer host requirements
Before you launch the BMC Cloud Lifecycle Management installer, ensure that the installer host meets the requirements described in the following sections. An installer host is the physical or VM host on which you run the installer. This topic discusses the Linux installer host requirements.
Operating-system requirements
- Red Hat Enterprise Linux 5.5 (64-bit)
- Red Hat Linux 6.2 (64-bit)
Hardware requirements
- Minimum 1 GB free hard-disk space for the installation directory and minimum 30 GB free hard-disk space for storing installation applications
- 2 CPUs (3-GHz dual processor)
- Minimum 1 GB RAM during installation
Permissions
You need root user credentials to perform all the installations.
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.
Component | Port number | Description |
---|---|---|
BMC Cloud Lifecycle Management installation program | 12333, 9998 | Installer ports On the BMC Cloud Lifecycle Management installer host, ensure that port 12433 is free. 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 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. |
BMC Remedy AR System server and BMC Remedy IT Service Management Suite | 0 (default value) | Enterprise AR System server, AR System server post-installation, Distributed Server Option (DSO), and Cloud Portal AR Extensions port The default port on which Enterprise AR System 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 and DSO 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) | 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 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) | Cloud AR System server, AR System server post-installation, DSO, and Cloud Extensions port The default port on which the AR System Cloud Database server is installed by the BMC Cloud Lifecycle Management installer is port 0. The BMC Cloud Lifecycle Management installer queries above port over the network during the AR System server post-installation and DSO installation to check whether the AR System server is running. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked. |
| 1521 (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 | 1521 (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 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 During the BMC Network 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. |
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 if 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) | 1521 (default value) | Requires the BMC Server Automation database port for PXE provisioning During the PXE 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. |
For more information about the ports used by BMC Cloud Lifecycle Management, see Port mappings.
Preparing the installation planner host
Ensure that your installer host is correctly configured before you launch the installer, as described in the following sections:
To install from the tmp directory
If you want to install the BMC Cloud Lifecycle Management solution from the /tmp directory, ensure that you update the /etc/fstab filesystem with the correct mount property for the installationPath/tmp directory. Set the default value of the fourth column of the filesystem to exec. For more information, see Updating the fstab filesystem in Linux.
To set the screen resolution
Set your computer screen to the recommended resolution of 1280 x 800 or greater.
To verify product host connectivity
Ensure that you can successfully launch the installation on a product host.
To update BMC Server Automation RSCD Agent and NSH to the required version
For new installations, the BMC Cloud Lifecycle Management installer installs version 8.3 of the BMC Server Automation Remote Server Call Daemon (RSCD) Agent and BMC Network Shell (NSH). The installer uses NSH to execute silent installation commands, which are accepted by the RSCD agent installed on the target hosts. The RSCD agent executes the commands so that the installer can remotely install the supporting BMC products.
If an existing RSCD Agent and NSH are installed, perform one of the following actions:
- Upgrade to version 8.3.
- Uninstall the agent and NSH if you are unable to upgrade them as described in the following procedure:
To install Package Managers on Linux 5.5 computers
Specific Package Managers are required to access the graphical user interface (GUI) on Red Hat Linux 5.5 computers.
To install Package Managers on Linux 6.2 computers
Specific Package Managers are required to access the graphical user interface (GUI) on Red Hat Linux 6.2 computers.
Related topics
Preparing-to-run-the-installer-on-a-Linux-computer
Prerequisites-for-installation-installation-order-and-product-dependencies
Installing BMC Cloud Lifecycle Management