Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

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 and hardware requirements

Software

Hardware

Permissions

  • Red Hat Enterprise Linux 5.x (64-bit)
  • Red Hat Enterprise Linux 6.x (64-bit)
  • Oracle JRE 1.7 (64-bit)
  • Minimum 1 GB free hard-disk space for the installation directory
  • Minimum 30 GB free hard-disk space for storing installation applications
  • 2 CPUs (3-GHz dual processor)
  • Minimum 1 GB RAM during installation

You need root user credentials to perform all the installation

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

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 AR System Server - Cloud Portal and Database - Primary

0 (default value)

Cloud Portal and Database server, AR System server postinstallation, 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 postinstallation 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.

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.

The installer also let you select Enable sub product remote staging directory option to enter an alternative staging area that you can use for all product installations if the /tmp directory on the remote hosts does not have sufficient space.
image2014-2-18 16:32:32.png 

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.

Click here to review the steps.
  1. Ensure that you can contact all target hosts (on which you want to install BMC products) from the installer host (for example, ping <hostName> -c 5).
  2. Run the ifconfig eth0 command on the target host, and verify that the IP address returned in the preceding step matches the target computer's IP address returned in this step.
Recommendation

Use tools such as Xmanager, Xming, or VConsole for connecting to the Linux computer and running the installer. With Xmanager and Xming, X applications installed on remote UNIX based computers run seamlessly with Windows applications side by side.

To update BMC Server Automation RSCD Agent and NSH to the required version

Notes

  • Domain credentials (even though they have admin permissions) are not supported during the RSCD installation using the BMC Cloud Lifecycle Management installer.
  • This task is not required for upgrades.

For new installations, the BMC Cloud Lifecycle Management installer installs version 8.5 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, uninstall the RSCD agent and NSH:

Click here to review the steps.
  1. Go to /opt/bmc/BladeLogic/NSH/NSH. or /opt/bmc/Planner/NSH.
  2. Type the command ./Uninstall and follow the uninstallation process.
  3. Go to /opt/bmc/bladelogic directory and delete the RSCD folder (if it exists).
  4. Manually delete the /usr/lib/rsc folder and the /etc/rsc folder (if it exists).
  5. Reboot the machine after you have completed the cleanup.

For more information, see the Uninstalling other components on UNIX and Linux topic in the BMC Server Automation online technical documentation..

To install packages on Linux 5.x computers

Specific packages are required to access the graphical user interface (GUI) on Red Hat Linux 5.x computers.

Note

Contact your Linux system administrator to check for these packages.

Click here for a list of packages to install on the installer host.
  • libXi-1.0.1-4.el5_4
  • libX11-1.0.3-11.el5
  • libXau-1.0.1-3.1
  • libICE-1.0.1-2.1
  • libSM-1.0.1-3.1
  • libXtst-1.0.1-3.1
  • libXtst-1.0.1-3.1.i386
  • libXext-1.0.1-2.1
  • compat-libstdc++-33-3.2.3-61.i386
  • compat-libtermcap-2.0.8-49.el6.x86_64
  • libXi.i386
  • xorg-x11-server-Xorg
  • xorg-x11-utils
  • xorg-x11-xauth

To verify whether the RPM is installed and to determine its current version, enter the following command:

yum list package
yum list compat-libstdc++-33

To install packages on Linux 6.x computers

The following video presentation (4:05) shows you how to subscribe to the Red Hat Network. 

Note

The following video was created for version 4.6 of BMC Cloud Lifecycle Management. But its content is still applicable to version 4.1. 

 

icon-play.png https://youtu.be/cCBUd3eQhIk

The following video presentation (8:38) shows you how to use yum and rpm to install Linux packages on your Linux host. 

Note

The following video was created for version 4.6 of BMC Cloud Lifecycle Management. But its content is still applicable to version 4.1. 

icon-play.png https://youtu.be/o_xPqITchyc

Specific packages are required to access the graphical user interface (GUI) on Red Hat Linux 6.2 computers.

Note

Contact your Linux system administrator to check for these packages.

Click here to review the steps.
  1. Install the following 32-bit RPM packages:
    • unixODBC-devel-2.2.14-12.el6_3.i686.rpm
    • unixODBC-2.2.14-12.el6_3.i686.rpm
    • libX11-1.5.0-4.el6.i686.rpm
    • libXau-1.0.5-1.el6.i686.rpm
    • libxcb-1.8.1-1.el6.i686.rpm
    • libXext-1.3.1-2.el6.i686.rpm
    • libXi-1.3-3.el6.i686.rpm
    • libXtst-1.0.99.2-3.el6.i686.rpm
    • libXp-1.0.0-15.1.el6.i686.rpm
    • openssl-1.0.0-20.el6_2.5.i686.rpm
    • libgssglue-0.1-11.el6.i686.rpm
    • krb5-libs-1.10.3-10.el6_4.2.i686.rpm
    • libcom_err-1.41.12-14.el6.i686.rpm
    • keyutils-libs-1.4-4.el6.i686.rpm
    • libselinux-2.0.94-5.3.el6.i686.rpm
    • zlib-1.2.3-29.el6.i686.rpm
    • libidn-1.18-2.el6.i686.rpm
    • libcap-2.16-5.5.el6.i686.rpm
    • libattr-2.4.44-7.el6.i686.rpm
    • libstdc++-4.4.4-13.el6.i686.rpm
    • elfutils-libelf-devel-0.152-1.el6.i686.rpm
    • elfutils-libelf-devel-static-0.152-1.el6.i686.rpm
    • libaio-devel-0.3.107-10.el6.i686.rpm
    • libgcc-4.4.7-3.el6.i686.rpm
    • libstdc++-devel-4.4.6-4.el6.i686.rpm
    • glibc-devel-2.12-1.107.el6.i686.rpm
    • glibc-2.12-1.107.el6.i686.rpm
    • compat-libstdc++-33-3.2.3-69.el6.i686.rpm
    • compat-libtermcap-2.0.8-49.el6.i686.rpm
    • pam.i686 – Linux-PAM (Pluggable Authentication Modules for Linux) RPM
  2. Install the following 64-bit RPM packages:
    • unixODBC-devel-2.2.14-12.el6_3.x86_64.rpm
    • unixODBC-2.2.14-12.el6_3.x86_64.rpm
    • libX11-1.5.0-4.el6.x86_64.rpm
    • libXau-1.0.5-1.el6.x86_64.rpm
    • libxcb-1.8.1-1.el6.x86_64.rpm
    • libXext-1.3.1-2.el6.x86_64.rpm
    • libXi-1.3-3.el6.x86_64.rpm
    • libXtst-1.0.99.2-3.el6.x86_64.rpm
    • libXp-1.0.0-15.1.el6.x86_64.rpm
    • openssl-1.0.0-20.el6_2.5.x86_64.rpm
    • libgssglue-0.1-11.el6.x86_64.rpm
    • krb5-libs-1.10.3-10.el6_4.2.x86_64.rpm
    • libcom_err-1.41.12-14.el6.x86_64.rpm
    • keyutils-libs-1.4-4.el6.x86_64.rpm
    • libselinux-2.0.94-5.3.el6.x86_64.rpm
    • zlib-1.2.3-29.el6.x86_64.rpm
    • libidn-1.18-2.el6.x86_64.rpm
    • libcap-2.16-5.5.el6.x86_64.rpm
    • libattr-2.4.44-7.el6.x86_64.rpm
    • libstdc++-4.4.4-13.el6.x86_64.rpm
    • elfutils-libelf-devel-0.152-1.el6.x86_64.rpm
    • elfutils-libelf-devel-static-0.152-1.el6.x86_64.rpm
    • libaio-devel-0.3.107-10.el6.x86_64.rpm
    • libgcc-4.4.7-3.el6.x86_64.rpm
    • libstdc++-devel-4.4.6-4.el6.x86_64.rpm
    • gcc-4.4.6-4.el6.x86_64.rpm
    • glibc-devel-2.12-1.107.el6.x86_64.rpm
    • glibc-headers-2.12-1.107.el6.x86_64.rpm
    • kernel-headers-2.6.32-279.el6.x86_64.rpm
    • glibc-2.12-1.107.el6.x86_64.rpm
    • glibc-common-2.12-1.107.el6.x86_64.rpm
    • gcc-c++-4.4.6-4.el6.x86_64.rpm
    • sysstat-9.0.4-20.el6.x86_64.rpm
    • compat-libstdc++-33-3.2.3-69.el6.x86_64.rpm
    • compat-libtermcap-2.0.8-49.el6.x86_64.rpm
    • pam.x86_64 – Linux-PAM (Pluggable Authentication Modules for Linux) RPM

  3. To verify whether an RPM is installed and to determine its current version, enter the following command:

    yum list package
    yum list compat-libstdc++-33
  4. To ensure that the BMC Remedy AR System services start, install the compat-libstdc++-33-3.2.3-69.el6.i686 package.
  5. To ensure that the RSCD Agent installs properly, install the compat-libtermcap-2.0.8-49.el6.x86_64 package.
  6. From the /usr/lib folder, verify that the libstdc++.so.5 library exists. Install the library if it does not exist.

  7. Start the rpcbind process with the -i option on Cloud Portal and Database host before installing to avoid install failures:

    # service rpcbind stop
    # rpcbind -i
    # service rpcbind status

To set the minimum JVM heap size

For optimal performance, set the minimum JVM heap size to 1024 MB. Otherwise, the install planner might hang.

Related topics

Preparing-to-run-the-installer-on-a-Linux-computer

Installation-order-and-product-dependencies

Installing BMC Cloud Lifecycle Management

Base-product-versions-and-compatibility-for-upgrade

Port-mappings

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*