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
Step | Task |
---|---|
1 | Prepare to apply the feature pack or fix pack |
2 | Apply the feature pack or fix pack on the TrueSight Presentation Server |
3 | Apply the feature pack or fix pack on Infrastructure Management — Phase A |
Apply the feature pack or fix pack on Infrastructure Management — Phase B (You are here) | |
Apply the feature pack or fix pack on Infrastructure Management — Phase C | |
4 | Apply the feature pack or fix pack on App Visibility Manager |
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
- Stop the secondary cluster node before you install the feature pack or fix pack on the primary cluster node.
- Go to Start > All Programs > Administrative Tools > Failover Cluster Manager.
- Right-click the secondary node and under More Actions, select Stop Cluster Service.
- From a command prompt window, access the extracted installation files in the Windows\TSIMServer\Disk1 directory.
- Run the following command to start the installation on the primary cluster node:
install.cmd -J INSTALL_TYPE=PRIMARY
- The installation screens are similar to a standalone installation. For more information, see Applying feature packs or fix packs on the Infrastructure Management server in the standalone mode using the wizard.
- After the 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
- Start the secondary cluster node:
- Go to Start > All Programs > Administrative Tools > Failover Cluster Manager.
- Right-click the secondary node and under More Actions, select Start Cluster Service.
- 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
- Change the host name of the primary node to the logical host name configured for the cluster by running the following command:
hostname <logicalHostName>
- 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.
- 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>
- 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. - 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 download and install the administrator console on remote computers.
Comments
Log in or register to comment.