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.

The following procedures explain how to install the BMC TrueSight Infrastructure Management Server in HA mode on primary and secondary servers:

  1. Check the prerequisites to installing BMC TrueSight Infrastructure Management in HA mode.
  2. Install the BMC TrueSight Infrastructure Management Server on the primary server.

  3. Perform the primary server post-installation steps.
  4. Install the BMC TrueSight Infrastructure Management Server on the secondary server.

Note

Infrastructure Management is not supported on VMware with VMWare Fault Tolerance (FT) as Infrastructure Management high availability support.

Prerequisites to installing Infrastructure Management in HA mode

The following are the prerequisite tasks that you must perform before installing Infrastructure Management in HA mode:

  • Ensure that the cluster configuration is of ‘node and cluster disk majority’ type.
  • Ensure that the cluster name does not contain an underscore (_).

  • Ensure that a visible shared disk is available and you choose the shared drive as the installation directory.
  • Ensure that the HA installer files are not copied to the quorum disk.
  • Ensure that you have the identical operating system version on the primary and the secondary computers.
  • Ensure that you have identical hardware configuration on the primary and the secondary computers.
  • Ensure that the primary and the secondary computers are located in the same domain.
  • Configure the logical IP address.
  • Ensure that the primary and the secondary computers have identical time stamps.
  • Ensure that the Microsoft Clustering software is installed on both the primary and the secondary computers.
  • Ensure that you add the common logical IP address/host name to be allocated to the two computers to the domain name service (DNS).
  • Map the disk to be shared between the two computers with the same directory name and/or directory path on both the computers.
  • The IP address, disk, and network name must be present in the same group.

Installing the Infrastructure Management Server on the primary server

You can manually install the BMC TrueSight Infrastructure Management Server on the primary server. Automatic Failover is handled by the Microsoft Cluster Server software.

To install the BMC TrueSight Infrastructure Management Server on the primary server on Microsoft Windows:

  1. Open the command prompt with the Run as administrator option. Access the <installerLocation>\Windows\TSIMServer\Disk1 directory (where installerLocation is a directory where you have downloaded installer files) and run the following command:

    install.cmd -J INSTALL_TYPE=PRIMARY
  2. Follow the procedure from step 4 to 26 in the To install the BMC TrueSight Infrastructure Management Server on Microsoft Windows section.

Primary server post-installation steps

After installing the BMC TrueSight Infrastructure Management Server on the primary server, perform the following steps:

  1. Stop the BMC TrueSight Infrastructure Management Server on the primary server, see Stopping the BMC TrueSight Infrastructure Management Server.
  2. Move the cluster control to the secondary server.

  Installing the BMC TrueSight Infrastructure Management Server on the secondary server

The following procedure explain how to install the BMC TrueSight Infrastructure Management Server on the secondary server. Automatic Failover is handled by the Microsoft Cluster Server software.

To install the BMC TrueSight Infrastructure Management Server on the secondary server on Microsoft Windows:

  1. Ensure that you perform the steps in Primary Server post-installation steps.
  2. Open the command prompt with the Run as administrator option. Access the <installerLocation>\Windows\TSIMServer\Disk1 directory (where installerLocation is a directory where you have downloaded installer files) and run the following command:

    install.cmd -J INSTALL_TYPE=SECONDARY

  3. On the Welcome screen, click Next.
  4. On the license agreement page, select I agree to the terms of the license agreement, and click Next.
  5. On the Configuring Firewall Rules page, perform one of the following tasks, and click Next. You must configure firewall rules to allow BMC TrueSight Infrastructure Management processes to communicate through the firewall. 

    Note

    If you turn on the firewall when Remote Desktop Protocol is running, the Remote Desktop Protocol session may get disconnected if Remote Desktop Protocol is blocked by the firewall.

    • To automatically configure the Windows Firewall rules, select Automatically configure Windows Firewall Rules

    The Windows Firewall inbound rules are configured. An error message appears if you have not started the Windows Firewall. 

    Note

    Ensure that you start the Windows Firewall before you configure the Windows Firewall rules. For more information about starting the Windows Firewall, see To start Windows Firewall.

    • To manually configure the firewall rules, select I will manually configure Windows Firewall Rules now before proceeding further
      • For more information about creating Windows Firewall inbound rules, see To manually configure Windows Firewall inbound rules.
      • If you prefer to use a third party firewall application, which is installed on your computer, ensure that you manually create the firewall inbound rules. For more information about creating firewall inbound rules, refer to the documentation of the third party firewall application.
  6. On the Directory Selection page, ensure that the directory is the same as the primary server, and click Next.
  7. On the Installation Summary screen, click Done to complete the installation.
  8. When the BMC TrueSight Infrastructure Management Server installation is complete, you can choose View Logs to open the installation logs. The installer creates all BMC TrueSight Infrastructure Management services and registry entries. 

  9. Run the pns.reg file located at installationDirectory\pw\pproxy\PNS\security. If you do not run this file, during a failover, existing policy configurations are not applied on the BMC PATROL Agent and policy creation and update fails.

  10. Create dependencies for the BMC TrueSight Infrastructure Management Server cluster resource.

    1. Stop the BMC TrueSight Infrastructure Management Server using the pw system stop command.
    2. Go to Start > All Programs > Administrative Tools > Failover Cluster Manager and click on the cluster name.

    3. Scroll down to the Cluster Core Resources section, right-click PnService, and click Properties.

    4. In the PnService Properties dialog box, click the Dependencies tab.
    5. Click Insert to add a resource.
    6. From the Resource list, select a cluster name and click Insert.
    7. Select the cluster resource with the ‘AND’ option. Similarly, add all the resources (Name, IP address, and Disk).
    8. Click Apply and OK.
    9. Restart the BMC TrueSight Infrastructure Management Server using the pw system start command.
  11. Restart both the primary and secondary servers.

Notes

  • After the BMC TrueSight Infrastructure Management Server is installed on both the primary and secondary servers, a “PnService” 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 run the following file:
      (Windows Server 2008) GenericService.bat
      (Windows Server 2012) GenericService.ps1
    2. Run the following command to enable the PnService cluster resource:
      (Windows Server 2008) cluster.exe resource PnService /ONLINE /WAIT:500
      (Windows Server 2012) powershell.exe Start-ClusterResource -Name PnService -Wait 500
  • The BMC TrueSight Infrastructure Management Server takes time to come up during failover, as it runs on a Microsoft active/passive cluster. If the BMC TrueSight Infrastructure Management Server (cluster resource) does not come up, select the online option to manually set the status.
  • If the services are not running on the secondary server and the ProServices.log file contains warnings for database connections, perform the following:

    • Navigate to the following registry paths and change the dbservice engine name to storm_<logicalclusterName>

      • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI

      • HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI

    • Open the mcell.dir file located in the installationDirectory\pw\server\etc directory and change the cluster name to storm_<logicalclusterName> for pncell and Admin cell.

Related topics

Installing the BMC TrueSight Infrastructure Management Server in HA mode on Linux/Solaris

Installing the Integration Service in HA mode on Windows