Applying feature packs or fix packs on Infrastructure Management in high availability cluster mode

To migrate the configuration of Infrastructure Management cells

Your existing KB might contain customizations, such as class definitions and rules that are unique to your environment, so you must migrate and merge these customizations with the new 10.7 standard KB. After you merge your KB, it contains the following components:

• Definitions from your existing KB
• New definitions from the latest KB

You must do this merger before you start the server upgrade because the upgrade process requires the KB to be current. You must migrate every KB in your Infrastructure Management implementation. The migration process is a combination of several configuration steps:

1. Validate the KB.

2. Add the clone cell KB directory to the unique file path for merged KBs.

3. Use the mmigrate utility to migrate the cell configuration.

To install the Fix Pack on the Infrastructure Management server in HA mode

When installing the Fix Pack in a high availability cluster environment, install the Fix Pack only on the primary (active) cluster node.

You do not require to install the Fix Pack on the secondary (standby) cluster node. After the Fix Pack installation completes on the primary cluster node, the appropriate files are updated on the secondary cluster node.

Microsoft Windows

1. Stop the secondary cluster node before you install the Fix Pack on the primary cluster node.
   1. Go to Start > All Programs > Administrative Tools > Failover Cluster Manager.
   2. Right-click the secondary node and under More Actions, select Stop Cluster Service.
2. From a command prompt window, access the extracted installation files in the Windows\TSIMServer\Disk1 directory.
3. Run the following command to start the Fix Pack installation on the primary cluster node:
   install.cmd -J INSTALL_TYPE=PRIMARY
4. The installation screens are similar to a stand-alone installation. For more information, see Applying feature packs or fix packs on the Infrastructure Management server.
5. After the Fix Pack installation completes on the primary cluster node, run the following command from the pw command prompt window to manually restart the Infrastructure Management server processes:
   pw system start
6. Start the secondary cluster node:
   1. Go to Start > All Programs > Administrative Tools > Failover Cluster Manager.
   2. Right-click the secondary node and under More Actions, select Start Cluster Service.
7. Scroll down to Cluster Core Resources and ensure that PnService is running.

Linux

1. Change the host name of the primary node to the logical host name configured for the cluster by running the following command:
   hostname <logicalHostName> 
2. Install the Fix Pack on the primary cluster node. For more information, see Applying feature packs or fix packs on the Infrastructure Management server.
3. After the Fix Pack installation completes on the primary cluster node, change the logical host name back to the host name of the primary node by running the following command: 
   hostname <primaryHostName> 
4. On the secondary cluster node, copy the installedDirectory/TrueSight/pw/patrol/pis/security/bppmpis.plc file to the /etc/patrol.d/<underscore separated install folder> folder.
   For example, if the installation directory is /sharedfs/TrueSight/pw, copy the bppmpis.plc file to /etc/patrol.d/_sharedfs_TrueSight_pw/security_policy_v3.0.
5. On the secondary cluster node, copy the installedDirectory/TrueSight/pw/patrol/pis/security/patrol.conf file to the /etc/patrol.d/<underscore separated install folder> folder.
   For example, if the installation directory is /sharedfs/TrueSight/pw, copy the patrol.conf file to /etc/patrol.d/_sharedfs_TrueSight_pw.

To install the Fix Pack on the remote cells in HA mode

1. Before you install the Fix Pack on HA-enabled remote cells, stop both the primary and secondary cells. For more information, see Starting or stopping the cell.
2. Install the Fix Pack on the secondary cell. For more information, see Installing or upgrading the remote Integration Service and remote cell.
3. After installation, stop the secondary cell.
4. Install the Fix Pack on the primary cell. For more information, see Installing or upgrading the remote Integration Service and remote cell.
5. Manually start the secondary cell. For more information, see Starting or stopping the cell.
6. Run the following command from a pw command prompt window to verify that both the primary and secondary cells are running:
   mgetinfo -n <cell name> -v activity
   The primary cell should be in Full Activity mode and the secondary cell should be in Standby mode.