Installing the Infrastructure Management Server in HA OS cluster mode on Linux
This topic provides instructions to install the TrueSight Infrastructure Management Server in high availability cluster mode on Linux operating systems.
Red Hat Availability add-on for Linux (with Resilient Storage add-on if GFS2 is required) is required to control high-availability for Infrastructure Management on Linux operating systems
Infrastructure Management is not supported on VMware with VMWare Fault Tolerance (FT) as Infrastructure Management high availability support.
Prerequisites to installing Infrastructure Management in HA OS cluster mode
Ensure that the following prerequisite tasks are performed or checked before installing Infrastructure Management in HA OS cluster mode:
- A visible shared disk should be available and you choose the shared drive as the installation directory.
- The operating system version must be identical on the primary and the secondary computers.
- The hardware configuration must be identical on the primary and the secondary computers.
- The primary and the secondary computers must be located in the same domain.
- Configure the logical IP address.
- The primary and the secondary computers must have identical time stamps.
- Ensure that you add the common logical IP address/host name to be allocated to the two computers to the domain name service (DNS).
- Mount the disk to be shared between the two computers with the same directory name and/or directory path on both the computers.
To install the Infrastructure Management Server in HA OS cluster mode on Linux systems
The following procedure explains how to install the BMC TrueSight Infrastructure Management Server in HA OS cluster mode on primary and secondary servers:
- Change the host name of the primary node to the logical host name configured for the cluster by entering hostname logicalHostName.
For example, hostname bmccluster.bmc.com.
Install TrueSight Infrastructure Management Server on the primary node.
During the installation, choose the cluster file system (/global) that is shared on both nodes as the installation location.
The installation is completed successfully.
- After successful installation of the TrueSight Infrastructure Management Server, change the logical host name back to the host name of the primary node by entering hostname
On the primary node, remove the following files so that the Infrastructure Management application does not start:
- Add the TrueSight Infrastructure Management Server component (logical host name) with TrueSight Presentation Server. Make sure that the status of all TrueSight Infrastructure Management Server component is Connected.
Stop all processes on the primary node. Use the following command:
pw sys stop.
Move the shared disk from primary node to the standby node. Use one of the following commands:
(For RHEL 6.x)
clusvcadm -r logicalhostname -n Standbymodehostname(For RHEL 7.x)
pcs resource move <resource group name> StandbymodehostnameDo not execute the above commands on the shared disk.
You can use the following command to find the resource group name on the primary host:
- Copy the /etc/patrol.d folder from the primary node to the standby node (in the same location).
This step is needed to enable the PATROL Agent to connect to the Integration Service.
On the primary node, from the user's home directory, copy the bmc_profile and the bmc_cshrc files to the standby node (in the same location).
On the standby node, perform the following steps to create environment variables:
In the <User-Home-Directory>/.bash_profile file, add the following entry, and save the file.
In the <User-Home-Directory>/.bashrc file, add the following entry, and save the file.
- Log out and then log on to the secondary node so that the changes made in the preceding steps are applied.
- On the standby node, create the required links for the TrueSight Infrastructure Management Server by entering the following commands:
ln -s /serverInstallDirectory/pw /usr/pw
ln -s /usr/pw/pronto /usr/pronto
ln -s /usr/pw/pronto/bin/pw /bin/pw
- Start all processes on the standby host. Use the following command:
pw sys start
- On the standby node, check for the Infrastructure Management Server crontab entries:
- Identify the crontab entries by using the
crontab -lcommand and check for all entries between the lines
- If the crontab entries are missing, open the command prompt, navigate to the <installDirectory>\pw\scripts folder, and run the following command:
CreateCrontabEntries.sh linux <Database>where <Database> can be Oracle or SAP SQL Anywhere
CreateCrontabEntries.sh linux Oracle
- Identify the crontab entries by using the
After moving the shared disk from the primary node to the standby node, the status of all TrueSight Infrastructure Management Server components must be Connected on the TrueSight Infrastructure Management Server Registration page.
The TrueSight Infrastructure Management Server must successfully connect to Integration Service and PATROL Agent.
For information about adding a failover domain and other post-installation tasks, see Setting up the cluster in Linux 6.x, Setting up the cluster in Linux 7.x, and Setting up the service to run in high-availability cluster mode in Linux.
Post-installation task for non-root users
After you install TrueSight Infrastructure Management as a non-root user, configure the TrueSight Infrastructure Management process to automatically start, each time the TrueSight Infrastructure Management server is restarted. To do this, register the TrueSight Infrastructure Management process as a service by running the script described in the following procedure. Running this script also results in copying the Integration Service security files required by the PATROL Agent to connect with the Integration Service.
- Locate the script at <Infrastructure-Management-Installation-Directory>/pw/scripts.
- Run the script in the following format:
In the preceding script syntax,
<Non-root-User-Name>refers to the non-root user name with which the process must be registered as a service.
Providing the non-root user name is optional. If you do not provide the non-root user name, by default, the script uses the non-root user name used for installing TrueSight Infrastructure Management for registering the service.