Upgrading the Infrastructure Management server in the high-availability cluster mode using the wizard

The page .Installing the Infrastructure Management server in the standalone mode using the wizard v11.3.04 was not found  -- Please check/update the page name used in the MultiExcerpt-Include macro

Where you are in the Upgrade process

You need to perform the following tasks to install the Infrastructure Management server in the high-availability cluster mode using the wizard:

Step A: To upgrade the Infrastructure Management Server on the primary computer

Upgrading on Windows

1. Stop the cluster service for the secondary computer. 

2. Log in to the host computer on which the cluster is installed. Ensure that the cluster is pointing to the host computer on which you plan to upgrade the primary Infrastructure Management server.

3. Delete all the files from the temporary directory:

   • (Windows) %temp%
   • (Linux) /tmp
4. Extract the downloaded zip files (the installer) to a temporary location outside the following location to avoid any file sharing conflicts:
   S:\Program Files

5. Ensure that the following system requirements are met. If your target computer does not meet these requirements, you cannot proceed with the installation. However, in a test environment, you can skip the system requirements validation and run the installer by using the -J MINIMAL=true argument.

   • Total RAM (in MB): 32,000
     
   • Available RAM (in MB): 25,000
   • Total swap space / page file (in MB): 8,000
   • Available swap space / page file (in MB): 8,000

6. 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

7. On the Welcome page, click Next.

8. On the license agreement page, select I agree to the terms of the license agreement, and click Next.

9. On the Upgrade Confirmation page, click Yes, and click Next. The upgrade routine checks the system to see that it meets the upgrade prerequisites. It mentions that you must install TrueSight Presentation Server before installing TrueSight Infrastructure Management. It displays any errors that it discovers. You can correct them and then return to the upgrade sequence.

10. (Applicable only if you are upgrading from Infrastructure Management 10.7) On the Listening Address Configuration page, confirm the Fully Qualified Domain Name (FQDN). 

    Note

    Ensure that the TrueSight Infrastructure Management server FQDN is reachable from other BMC products.

11. In the Cloud-vista enabled environment, the Configuring TrueSight Infrastructure Management environment deployment information screen is displayed. Provide the following details, and click Next.

    Select any one of the following options based on your TrueSight Infrastructure Management environment.

    • Single Server Environment Installation: Upgrades the TrueSight Infrastructure Management server as a standalone server.

    • Multiple Server Environment Installation: Upgrades the TrueSight Infrastructure Managementserver as following:

      • BMC TrueSight Infrastructure Management Central Server: Upgrades this instance as a central server.

      • BMC TrueSight Infrastructure Management Child Server: Enter the following Server Router details:

    Field	Description
    Host Name/IP Address	FQDN name and IP address of the Central Server Router. FQDN name comprises the host name and the domain name.
    Protocol	Protocol with which to communicate to the Central Server Router. It can be either HTTP or HTTPS protocol.
    Port	Port number with which to communicate to the Central Server Router. The default HTTP ports are 80 (Windows) and 8080 (Linux). The default HTTPS ports are 443 (Windows) and 8043 (Linux).

12. On the Configuring KB Migration Path page, if you have already migrated customized KB definitions to the new standard 11.3.04 KB, select Yes, and browse to the path of the customized KB directory.

    The file path should follow this hierarchy structure:
    \topLevelDirectory\mergedKB\server\etc\cellName , where \server\etc\cellName  is the standard subdirectory

    If you have KBs to migrate but have not done so, pause the upgrade process and migrate them before proceeding. See  Migrating the configuration of cells .

    During the upgrade, the routine copies the KB under the \mergedKB\server\etc\cellName  path and overwrites the KB in the default  installationDirectory \pw\server\etc\cellName  path.

13. On the Installation Preview page, click Install.

    Click Next.

14. On the Installation Summary window, select View Logs to open the installation logs, or click Done.

    After you successfully upgrade the TrueSight Infrastructure Management server, the following folder is created under the installation directory, in the BMC Software folder. You can manually delete the files if you do not want them.

    Folder name	Description
    <installationDirectory>11.x  (where  x  is the version that you are upgrading from)	Contains backup files of the earlier TrueSight Infrastructure Management installation.

Upgrading on Linux

1. Log in to the host computer on which the cluster is installed. Ensure that the cluster is pointing to the host computer on which you plan to upgrade the primary Infrastructure Management server.
2. Delete all the files from the temporary directory (/tmp).
3. Extract the downloaded zip files (the installer) to a temporary location outside the following location to avoid any file sharing conflicts:
   S:\Program Files
4. Apply executable rights to all the installation files by running the following command: 
   chmod -R 755 installationDirectoryFolderName 
   installationDirectoryFolderName is the name of the folder that contains all the installation files.
   For example, chmod -R 755 Disk1

5. Set the DISPLAY environment variable to ensure that the wizard-based installer launches the screens appropriately.
   export DISPLAY=<IP address of the host computer>:0.0

6. Archive the old installation files including the user apps, Perl libraries, and any other customizations.
   1. Run the pw system stop command to stop the TrueSight Infrastructure Management Server.
   2. Tar the <InfrastructureManagement-Installation-Directory>/pw and place the resulting file in a secure location such as on another server, another file partition, or a directory that lies above <InfrastructureManagement-Installation-Directory>/pw.

   3. Save the Crontab entries (especially the database archive entry) related to the TrueSight Infrastructure Management Server.

   4. Restart the TrueSight Infrastructure Management Server by using the pw system start command.
      The page .Installing the Infrastructure Management server in the standalone mode using the wizard v11.3.04 was not found  -- Please check/update the page name used in the MultiExcerpt-Include macro
   5. Save any custom Apache settings.

7. Change the host name of the primary computer to the logical host name configured for the cluster by entering hostname logicalHostName. For example, hostname bmccluster.bmc.com.

8. Ensure that the following system requirements are met. If your target computer does not meet these requirements, you cannot proceed with the installation. However, in a test environment, you can skip the system requirements validation and run the installer by using the -J MINIMAL=true argument.

   • Total RAM (in MB): 32,000
     
   • Available RAM (in MB): 25,000
   • Total swap space / page file (in MB): 8,000
   • Available swap space / page file (in MB): 8,000
9. Upgrade the TrueSight Infrastructure Management Server on the primary node.
10. After successful upgrade of the TrueSight Infrastructure Management Server, change the logical host name back to the host name of the primary node by entering hostname  
    primaryHostName.  

11. On the primary node, remove the following files so that the TrueSight Infrastructure Management application does not start:

    • /etc/rc3.d/S81BMCTrueSight
    • /etc/rc0.d/K09BMCTrueSight
    • /etc/rc1.d/K09BMCTrueSight

Step B: To perform post-upgrade tasks after installing on the primary computer

Post-upgrade tasks on Windows

1. Stop the TrueSight Infrastructure Management server on the primary server.
2. Move the cluster control to the secondary server.

Post-upgrade tasks on Linux

1. Stop all processes on the primary computer by running the following command:
   pw sys stop.

2. Move the shared disk from the primary computer to the secondary computer by running the following commands on the primary computer:
   (For RHEL 6.x) clusvcadm -r logicalhostname -n Standbymodehostname
(For RHEL 7.x) pcs resource move <resource group name> Standbymodehostname
Do not execute the above commands on the shared disk. 

   Note

   You can use the pcs status command to find the resource group name on the primary host computer.

Post-upgrade tasks on Windows and Linux

If you have customized service management data in the di_models.baroc file present in the <Infrastructure Management Server Install Directory>\pw\server\etc directory, copy the publishing server kb from the backup directory to the <Infrastructure Management Server Install Directory>\pw\server\etc\<psname> directory.

Step C: To upgrade the Infrastructure Management Server on the secondary computer

Upgrading on Windows

1. Ensure that the primary TrueSight Infrastructure Management Server must be upgraded to the latest version.

2. The pnservice cluster resource must be offline.

3. Ensure that the TrueSight Infrastructure Management Server is shut down on the primary node and that cluster control is moved to the secondary node computer.

4. Log on to a virtual node, ensuring that you are on the secondary node.

5. Extract the contents of the zipped distribution file to an appropriate directory on the computer in which the TrueSight Infrastructure Management Server is upgraded. 
6. On the computer hosting the secondary node, 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
7. On the Welcome page, click Next.

8. On the Read the License Agreement and Select the Appropriate Option page, select I agree to the terms of the license agreement, and click Next. The upgrade routine automatically checks for the upgrade requirements. If it finds any errors, it displays them on a separate window. You can quit the upgrade process at this point, correct the indicated discrepancies, and then rerun the upgrade. The upgrade routine automatically detects the installation directory of the TrueSight Infrastructure Management Server.

   Note

   If .NET Framework version 3.0 is not installed, you receive an error message. To install .NET Framework, use the Role Management tool. For more information about how to install the .NET Framework, go to the Microsoft web site. When .NET Framework is installed, the upgrade routine starts to copy the files to the specified directory.

9. On the Installation Summary window, click View Installation Logs to open the installation logs.

10. Click Done to exit the upgrade on the secondary node. 

11. Ensure that dependencies are set for the TrueSight Infrastructure Management Server cluster resource:
    1. Stop the TrueSight Infrastructure Management Server by using the pw system stop command.
    2. Go to Start > All Programs > Administrative Tools > Failover Cluster Manager and select the cluster name.
    3. Scroll down to Cluster Core Resources, right-click PnService, and select Properties.
    4. In the PnService Properties window, on the Dependencies tab, 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, and add other resources (IP address and disk where TrueSight Infrastructure Management is installed) in the same way.
    7. Click Apply, and click OK.
    8. Restart the TrueSight Infrastructure Management Server by using the pw system start command. You can restart the secondary node to verify that the cluster service is running on the primary node.

Upgrading on Linux

1. On the standby node, create the required links for the TrueSight Infrastructure Management Server by entering the following commands:

   • ln -s /serverInstallDirectory/pw /usr/pw

   • ln -s /usr/pw/pronto /usr/pronto

   • ln -s /usr/pw/pronto/bin/pw /bin/pw

2. Start all processes on the secondary computer. Use the following command:
   pw sys start 
   The page .Installing the Infrastructure Management server in the standalone mode using the wizard v11.3.04 was not found  -- Please check/update the page name used in the MultiExcerpt-Include macro
3. On the secondary computer, check for the Infrastructure Management server crontab entries:
   1. Identify the crontab entries by using the crontab -l command and check for all entries between the lines # begin_pronto and # end_pronto. 
   2. If the crontab entries are missing, open the command prompt, navigate to the <installDirectory>\pw\scripts folder, and run the following command:
      
      CreateCrontabEntries.sh linux <Database>

where <Database> can be Oracle or SAP SQL Anywhere
      For example, CreateCrontabEntries.sh linux Oracle

Step D: To perform post-install tasks after installing on the secondary computer

For information about adding a failover domain and other post-installation tasks, see:

• If you have customized service management data in the di_models.baroc file present in the <Infrastructure Management Server Install Directory>\pw\server\etc directory, copy the publishing server kb from the backup directory to the <Infrastructure Management Server Install Directory>\pw\server\etc\<psname> directory.
• Setting up the cluster in Linux 6.x
• Setting up the service to run in high-availability cluster mode in Linux.

Troubleshooting upgrade issues

If you face issues during the upgrade, see  Troubleshooting an Infrastructure Management deployment.

Next step in the Upgrade process

Step 4 Phase B — Now that you have successfully upgraded the Infrastructure Management Server, you must upgrade the Integration Service and remote cells.