Upgrading Infrastructure Management Server in HA cluster mode on Linux

Before you begin

• Ensure that the HA installer files are not copied to the shared disk.
• Ensure that before you upgrade, you have migrated the customized KBs in your TrueSight Infrastructure Management implementation. Follow the procedure for executing the KB Migration Wizard described in Cell configuration migration. When satisfied that the merged KB is working properly, you can begin the server upgrade procedure. Note the directory path of each migrated KB. The directory path must follow this hierarchy structure: /topLevelDirectory/mergedKB/serve/etc/cellName, where /server/etc/cellName is the standard subdirectory.

Upgrading to TrueSight Infrastructure Management Server in HA cluster mode on Linux systems

The following procedure explains how to upgrade the TrueSight Infrastructure Management Server in HA mode on primary and secondary servers:

1. Archive the old installation files including the user apps, Perl libraries, and any other customizations.
   1. Run the pw system stop command to stop the TrueSight Infrastructure Management Server.
   2. Tar the <InfrastructureManagement-Installation-Directory>/pw and place the resulting file in a secure location such as on another server, another file partition, or a directory that lies above <InfrastructureManagement-Installation-Directory>/pw.
   3. Save the Crontab entries (especially the database archive entry) related to the TrueSight Infrastructure Management Server.
   4. Restart the TrueSight Infrastructure Management Server by using the pw system start command.
   5. Save any custom Apache settings.
2. Change the host name of the primary node to the logical host name configured for the cluster by entering hostname logicalHostName.  
3. Upgrade the TrueSight Infrastructure Management Server on the primary node.
4. After successful upgrade of the TrueSight Infrastructure Management Server, change the logical host name back to the host name of the primary node by entering hostname  
   primaryHostName.  
5. On the primary node, remove the following files so that the TrueSight Infrastructure Management application does not start:
   • /etc/rc3.d/S81BMCTrueSight
   • /etc/rc0.d/K09BMCTrueSight
   • /etc/rc1.d/K09BMCTrueSight
6. 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
7. On the standby node, check for the TrueSight Infrastructure Management Server crontab entries:
   1. Identify the crontab entries by using the crontab -l command and check for all entries between the lines # begin_pronto and # end_pronto. 
   2. 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
      For example, CreateCrontabEntries.sh linux Oracle

For information about adding a failover domain and other post-installation tasks, see Setting-up-the-cluster-in-Linux-6-x and Setting-up-the-service-to-run-in-high-availability-cluster-mode-in-Linux.