Preparing to run the installer on a Linux computer
Before you start installing the products in the BMC Cloud Lifecycle Management solution, prepare the Linux computer on which you will run the installer by using the procedures explained in this topic:
- Before you begin
- To install packages required for the Oracle client
- To install packages on Linux 6.x computers
- To install packages on Linux 5.5 computers
- To uninstall BMC Server Automation RSCD Agent and NSH
- To verify product host connectivity
- Related topics
To prepare for installation on a Microsoft Windows computer, see Preparing-to-run-the-installer-on-a-Windows-computer.
Before you begin
Ensure that you review the complete list of requirements. See Linux installer host requirements
To install packages required for the Oracle client
Install these packages for products that require an Oracle client.
Packages required for Red Hat Linux 6.x
- unixODBC-devel-2.2.14-11.el6.x86_64
- unixODBC-devel-2.2.14-11.el6.i686
- unixODBC-2.2.14-11.el6.i686
- unixODBC-2.2.14-11.el6.x86_64
- glibc-devel-2.12-1.47.el6_2.12.x86_64
- glibc-devel-2.12-1.47.el6.i686
- libstdc++.so.5 libgcc_s.so.1
Packages required for Red Hat Linux 5.5
- compat-libstdc++-33-3.2.3-61
- elfutils-libelf-devel-0.137-3.el5
- elfutils-libelf-devel-static-0.137-3.el5
- libaio-devel-0.3.106-5 (64-bit and 32-bit)
- libgcc-4.1.2-50.el5
- libstdc++-devel-4.1.2-50.el5
- unixODBC-2.2.11-7.1 (32-bit)
- unixODBC-devel-2.2.11-7.1 (32-bit)
- gcc-4.1.2-50.el5.x86_64
- glibc-devel-2.5-58.i386
- glibc-devel-2.5-58.x86_64
- glibc-headers-2.5-58.x86_64
- kernel-headers-2.6.18-238.el5.x86_64
- glibc-2.5-58.i686
- glibc-2.5-58.x86_64
- gcc-c++-4.1.2-50.el5.x86_64
- libstdc++.so.5 libgcc_s.so.1
- sysstat-7.0.2
All the packages listed are required for an Oracle client.
To install packages on Linux 6.x computers
The following packages are required to access the graphical user interface (GUI) on RedHat Linux 6.x computers. Install the following packages on your installer host:
Failed to execute the [confluence_note] macro.
- Install the following 32-bit RPM packages:
- unixODBC-devel-2.2.11-7.1
- unixODBC-2.2.11-7.1
- libX11-1.3-2.el6.i686.rpm
- libXau-1.0.5-1.el6.i686.rpm
- libxcb-1.5-1.el6.i686.rpm
- libXext-1.1-3.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
- libstdc++-4.4.4-13.el6.i686.rpm
- openssl-1.0.0-4.el6.i686.rpm
- libgssglue-0.1-8.1.el6.i686.rpm
- krb5-libs-1.8.2-3.el6.i686.rpm
- libcom_err-1.41.12-3.el6.i686.rpm
- keyutils-libs-1.4-1.el6.i686.rpm
- libselinux-2.0.94-2.el6.i686.rpm
- zlib-1.2.3-25.el6.i686.rpm
- libidn-1.18-2.el6.i686.rpm
- libcap-2.16-5.2.el6.i686.rpm
- libattr-2.4.44-4.el6.i686.rpm
- Linux-PAM (Pluggable Authentication Modules for Linux) RPM
- Install the following 64-bit RPM packages:
- elfutils-libelf-devel-0.137-3.el5
- elfutils-libelf-devel-static-0.137-3.el5
- libaio-devel-0.3.106-5
- libgcc-4.1.2-50.el5
- libstdc++-devel-4.1.2-50.el5
- unixODBC-2.2.11-7.1
- unixODBC-devel-2.2.11-7.1
- gcc-4.1.2-50.el5.x86_64
- glibc-devel-2.5-58.i386
- glibc-devel-2.5-58.x86_64
- glibc-headers-2.5-58.x86_64
- kernel-headers-2.6.18-238.el5.x86_64
- glibc-2.5-58.i686
- glibc-2.5-58.x86_64
- glibc-common-2.5-58.x86_64
- gcc-c++-4.1.2-50.el5.x86_64
- sysstat-7.0.2
- compat-libstdc++-33-3.2.3-69.el6.i686.rpm
- libstdc++.so.5 (under /usr/lib)
- libtermcap.so.2
- libstdc++-4.4.4-13.el6.i686.rpm
- openssl-1.0.0-4.el6.i686.rpm
- libgssglue-0.1-8.1.el6.i686.rpm
- krb5-libs-1.8.2-3.el6.i686.rpm
- libcom_err-1.41.12-3.el6.i686.rpm
- keyutils-libs-1.4-1.el6.i686.rpm
- libselinux-2.0.94-2.el6.i686.rpm
- zlib-1.2.3-25.el6.i686.rpm
- libidn-1.18-2.el6.i686.rpm
- libcap-2.16-5.2.el6.i686.rpm
- libattr-2.4.44-4.el6.i686.rpm
- Linux-PAM (Pluggable Authentication Modules for Linux) RPM
- To ensure that the BMC Remedy AR System services start, install the compat-libstdc++-33-3.2.3-69.el6.i686.rpm RPM package.
- To ensure that the RSCD Agent installs properly, install the libtermcap-2.0.8-49.el6.x86_64.rpm package.
- From the /usr/lib folder, verify that the libstdc++.so.5 library exists. Install the library if it does not exist.
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 statusTo verify if the RPM is installed, enter the following command:
rpm -ql package
rpm -ql compat-libstdc++-33-3.2.3-69.el6.i686.rpm
To install packages on Linux 5.5 computers
The following packages are required to access the graphical user interface (GUI) on RedHat Linux 5.5 computers. Install the following packages on your installer host:
Failed to execute the [confluence_note] macro.
- 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 if the RPM is installed, enter the following command:
rpm -ql compat-libstdc++-33-3.2.3-69.el6.i686.rpm
To uninstall BMC Server Automation RSCD Agent and NSH
For new installations, if you have an existing BMC Server Automation Remote Server Call Daemon (RSCD) Agent and BMC Network Shell (NSH) installed on your installer host, you must uninstall them. Because the RSCD agent will be installed with every BMC product and the NSH will be installed on the installer host, you must uninstall any existing versions.
Failed to execute the [confluence_note] macro.
- Go to /opt/bmc/BladeLogic/NSH/NSH. or /opt/bmc/Planner/NSH.
- Type the command ./Uninstall and follow the uninstallation process.
- Go to /opt/bmc/bladelogic directory and delete the RSCD folder (if it exists).
- Manually delete the /usr/lib/rsc folder and the /etc/rsc folder (if it exists).
- 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 verify product host connectivity
Perform the following steps to ensure that you can successfully launch the installation on a product host:
- Ensure that you can contact all target hosts (on which you want to install BMC products) from the installer host (for example, ping <hostName>).
- 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.
Failed to execute the [info] macro.
Related topics
Preparing-to-run-the-installer-on-a-Windows-computer
Prerequisites-for-installation-installation-order-and-product-dependencies
Installing-BMC-Cloud-Lifecycle-Management