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 check for existing installer
- To install from the tmp directory
- To set the screen resolution
- To install packages on Linux 6.5 computers
- To install packages on Linux 7.6 computers
- To uninstall TrueSight Server Automation (formerly called 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, listed at System-requirements-for-Linux.
To check for existing installer
Check if there is an existing installer from a previous installation on the host. If there is, back up and delete the previous /opt/bmc/Planner installation folder. Also, back up and delete the /opt/bmc/ProductRegistry.xml file.
To install 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 in the Linux documentation.
To set the screen resolution
Set your computer screen to the recommended resolution of 1280 x 800 or greater.
To install packages on Linux 6.5 computers
The following video presentation (4:05) shows you how to subscribe to the Red Hat Network.
The following video presentation (8:38) shows you how to use yum and rpm to install Linux packages on your Linux host.
You can also use the following .txt file to create a script for easy installation.
Specific packages are required to access the graphical user interface (GUI) on Red Hat Linux 6.5 computers.
- Install the following minimum versions of the 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
- libICE-1.0.6-1.el6.i686
- libSM-1.1.0-7.1.el6.i686
- 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
- xorg-x11-xauth-1.0.2-7.1.el6.i686
- pam.i686 – Linux-PAM (Pluggable Authentication Modules for Linux) RPM
- libstdc++-4.4.6-4.el6.i686
- libgcc-4.4.6-4.el6.i686
- Install the following minimum versions of the 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
- libICE-1.0.6-1.el6.x86_64
- libSM-1.1.0-7.1.el6.x86_64
- 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
- Linux-PAM (Pluggable Authentication Modules for Linux) RPM
- bc-1.06.95-1.el6.x86_64
- libstdc++-4.4.6-4.el6.x86_64
- libgcc-4.4.6-4.el6.x86_64
- 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 compat-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.
To verify whether 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 7.6 computers
libXi-1.7.4-2.el7.x86_64
libX11-1.6.3-3.el7.i686
libX11-1.6.3-3.el7.x86_64
libXau-1.0.8-2.1.el7.i686
libXau-1.0.8-2.1.el7.x86_64
libICE-1.0.9-2.el7.i686
libICE-1.0.9-2.el7.x86_64
libSM-1.2.2-2.el7.i686
libSM-1.2.2-2.el7.x86_64
libXtst-1.2.2-2.1.el7.i686
libXtst-1.2.2-2.1.el7.x86_64
libXext-1.3.3-3.el7.i686
libXext-1.3.3-3.el7.x86_64
libxcb-1.11-4.el7.i686
libxcb-1.11-4.el7.x86_64
compat-libstdc++-33-3.2.3-72.el7.i686
compat-libstdc++-33-3.2.3-72.el7.x86_64
xorg-x11-server-Xorg-1.17.2-22.el7.x86_64
xorg-x11-utils-7.5-14.el7.x86_64
xorg-x11-xauth-1.0.9-1.el7.x86_64
bc-1.06.95-13.el7.x86_64
libstdc++-4.8.5-39.el7.x86_64
libstdc++-4.8.5-39.el7.i686
libgcc-4.8.5-39.el7.x86_64
libgcc-4.8.5-39.el7.i686
To verify whether the RPM is installed, enter the following command:
rpm -ql package
To uninstall TrueSight Server Automation (formerly called BMC Server Automation) RSCD Agent and NSH
For new installations, if you have an existing TrueSight 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.
- Stop the RSCD agent if it is running:
/etc/init.d/rscd stop - Go to /opt/bmc/NSH.
- Type the command ./Uninstall and follow the uninstallation process.
- Go to /opt/bmc/rscd directory and delete the rscd folder (if it exists).
- Manually delete the /usr/lib/rsc folder, the /usr/nsh folder, and the /etc/rsc folder (if it exists).
- Manually delete the /etc/init.d/rscd file.
- Manually delete the /usr/lib/rsc/HOME file.
- To ensure there are no remaining artifacts (for example, if the RSCD agent was installed via rpm):
- Verify that the RSCD agent rpm has been removed:
rpm -qa | grep rscd - If the agent rpm is detected, delete it. For example:
rpm -e BladeLogic_RSCD_Agent-8.8.00-303.x86_64
- Verify that the RSCD agent rpm has been removed:
- Reboot the machine after you have completed the cleanup.
For more information, see the Uninstalling-other-components-on-UNIX-and-Linux topic in the TrueSight 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.
Related topics
Preparing-to-run-the-installer-on-a-Windows-computer
Installation-order-and-product-dependencies
Installing-BMC-Cloud-Lifecycle-Management