Page tree

Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

The following topic describes how to install the Fix Pack in a high availability cluster deployment.

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 Installing the Fix Pack 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 Installing the Fix Pack 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>

To install the Fix Pack on the Integration Service in HA mode

In the OS-level high availability (HA) mode, you must install the Fix Pack for the Infrastructure Management Integration Service on both primary and secondary servers.

Note

The Integration Service cannot be installed in HA mode on UNIX and Linux computers. The Integration Service has an internal failover mechanism. You can install the Integration Service on two UNIX computers separately, and configure the PATROL Agent with the names of both the Integration Services. If one UNIX computer goes down, the PATROL Agent automatically switches to the other computer in which the other Integration Service is installed.

Primary server

  1. Log on to the virtual node (assuming that the cluster service is started on both the primary and secondary servers).

  2. Ensure that you are on the primary server.
  3. Access the TSIMAgent\Windows folder and extract the contents of the TSIMAgent file. From the extracted TSIMAgent folder, access the Disk1 folder.

  4. Run the following command:
    install.cmd -J INSTALL_TYPE=PRIMARY
    The installation will be performed on the shared drive.
  5. Follow the instructions described in Installing or upgrading the remote Integration Service and remote cell.

Secondary server

  1. Log on to the virtual node (assuming that the cluster service is started on both the primary and secondary servers).

  2. Ensure that you are on the secondary server.
  3. Access the TSIMAgent\Windows folder and extract the contents of the TSIMAgent file. From the extracted TSIMAgent folder, access the Disk1 folder.

  4. Generate the options file from the primary server installation log and modify the value of INSTALL_TYPE=PRIMARY to INSTALL_TYPE=SECONDARY.

  5. Run the following command:

    • GUI-based installation:
      install.cmd -DOPTIONS_FILE=<options file generated using primary install log>
      All options provided for the primary server installation automatically get included on all screens. 
    • Silent installation:
      install.cmd -i silent -DOPTIONS_FILE=<options file generated using primary install log>
      You may update the options file, if required.

    The installation is performed on the shared drive.   

  6. Follow the instructions described in Installing or upgrading the remote Integration Service and remote cell.
  7. After the Integration Service is installed on both the primary and secondary servers, a “ProNetAgent” resource is created on the cluster.

    If this resource is not created automatically, you may receive warnings. To create the resource, perform the following steps:

    1. Go to the <installation directory>\Agent directory and execute the following file:
      (Windows Server 2008) GenericService.bat
      (Windows Server 2012) GenericService.ps1

    2. Execute the following command with the Run as administrator option to enable the ProNetAgent cluster resource:
      (Windows Server 2008) cluster.exe resource ProNetAgent /ONLINE /WAIT:500
      (Windows Server 2012) powershell.exe Start-ClusterResource -Name ProNetAgent -Wait 500 

  8. Create dependencies for the Integration Service cluster resources:
    1. Stop the BMC TrueSight Infrastructure Management Integration Service using Services.msc.

    2. Go to Start > All Programs > Administrative Tools > Failover Cluster Manager and click on the cluster name.

    3. Scroll down to Cluster Core Resources section, right-click ProNetAgent, and click Properties.
    4. Click the Dependencies tab in the ProNetAgent Properties window and click Insert to add a resource.

    5. Select the cluster name as a resource and click Insert.
    6. Select the cluster resource with the ‘AND’ option. Similarly, add all the resources.
    7. Click Apply and OK.
    8. Restart the BMC TrueSight Infrastructure Management Integration Service using Services.msc

  9. Restart both the primary and the secondary servers. If the Integration Services do not start, manually bring it up by starting the Integration Service.

To configure the cell to start or stop automatically during failover

Perform the following steps on the secondary node to start or stop the cell automatically during failover:

  1. Go to the <installation directory>\Agent directory and make a copy of the following file:
    (Windows Server 2008) GenericService.bat
    (Windows Server 2012) GenericService.ps1

  2. Edit the copied file:

    1. Replace the cluster resource value from "ProNetAgent" to"ProNetCell".

    2. Modify the ServiceName value from "ProNetAgent" to the Cell service name (you can obtain the cell service name from services.msc). 

  3. Execute the modified file with the Run as administrator option to create the new cluster resource as "ProNetCell".

  4. Create the similar dependencies for ProNetCell as of ProNetAgent

  5. Execute the following command with the Run as administrator option to enable the ProNetCell cluster resource:
    (Windows Server 2008)cluster.exe resource ProNetCell /ONLINE /WAIT:500
    (Windows Server 2012)powershell.exe Start-ClusterResource -Name ProNetCell -Wait 500 

  6. If the cell service is set to Automatic in services.msc, update it to Manual.

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. Install the Fix Pack on the primary cell. For more information, see Installing or upgrading the remote Integration Service and remote cell.
  4. 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
  5. Manually start the cell that is not running. For more information, see Starting or stopping the cell.

Related topics

Preparing to install the Fix Pack

Installing the Fix Pack silently