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

Where you are in the Applying-feature-packs-or-fix-packs process

To install the feature pack or fix pack on the Infrastructure Management server in HA cluster mode

When installing the feature pack or fix pack in a high-availability cluster environment, install it only on the primary (active) cluster node.

Do not install the feature pack or fix pack on the secondary (standby) cluster node. After the 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 feature pack or 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\TSIMServerFixPack\Disk1 directory.
  3. Run the following command to start the installation on the primary cluster node:
    install.cmd -J INSTALL_TYPE=PRIMARY
  4. Follow the instructions mentioned in Applying-feature-packs-or-fix-packs-on-the-Infrastructure-Management-server-in-the-standalone-mode-using-the-wizard. The installation screens are similar to a standalone installation.
  5. Stop the Infrastructure Management server.
  6. Start the secondary cluster node and do the following:
    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.
    3. Run the <Install_dir>\pw\pronto\bin\updateRegistryForSybase17.bat file to update the Sybase 17 registry settings for Windows.
  7. Start the Infrastructure Management server.
  8. Scroll down to Cluster Core Resources and ensure that PnService is running.

Note

If you are applying feature packs or fix packs on the cluster nodes, after you apply them to the primary cluster node, you do not need to apply them to secondary cluster node.

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 feature pack or fix pack on the primary cluster node. For more information, see Applying-feature-packs-or-fix-packs-on-the-Infrastructure-Management-server-in-the-standalone-mode-using-the-wizard.
  1. After the 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    > 
  2. 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.
  1. 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.

Note

If you are applying feature packs or fix packs on the cluster nodes, after you apply them to the primary cluster node, you do not need to apply them to secondary cluster node.


Where to go from here

Step 3 Phase C — Now that you have successfully installed the feature pack or fix pack on the Infrastructure Management server, you must apply it on the administrator console.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*