Upgrading the Infrastructure Management server for application high-availability


Where you are in the Upgrade process

You need to perform the following tasks to upgrade the Infrastructure Management server for application high-availability:

Application high-availability is supported only with the Oracle database. 

Best practice
BMC recommends that you deploy the Oracle database and TrueSight Infrastructure Management Server on separate servers.

Note

The Load Balancer Health Check URL formats have changed between TrueSight Operations Management versions 10.x and 11.x. For more information, see Guidelines-for-load-balancers.

  1. Stop the secondary server by using the pw sys stop command. For more information, see Starting and stopping the TrueSight Operations Management components.

    • After stopping the secondary server, ensure that all internal processes are stopped by using the pw process list command.
    • BMCTrueSight.service (Applicable only to version 11.3.04 and later on Linux)You can use the systemd service BMCTrueSight.service located in the /etc/systemd/system directory to start and stop the Infrastructure Management server on Linux. For more information, see Starting and stopping the TrueSight Operations Management components.
  2. On the primary server, change the publishing server startup mode from automated to manual. Ignore this step if the startup mode is already set to manual.
    1. Edit the pserver.conf file located in the installationDirectory/pw/server/etc folder and change the value of the parameter AutomatedStartMode to Manual.
    2. Run the command pscontrol manual

  3. Upgrade the primary server. See:
    (Using the wizard) Upgrading-the-Infrastructure-Management-server-in-the-standalone-mode-using-the-wizard
    (Silently) Upgrading-the-Infrastructure-Management-Server-in-the-standalone-mode-silently
    If you upgraded as a non-root user, then after the installation is complete, you might see the following warning in the tsim_servicepack_log.txt file located at installedDirectory\pw\pronto\logs. You can ignore this warning.

    LOG EVENT {Description=[Error while updating BMCTrueSight],Detail=[/etc/init.d/BMCTrueSight (Permission denied)]}
  4. Ensure that the primary server has successfully started by running the pw license list command. The output should display a valid license expiration date, as in the following example:
    Feature : Server, Expiration : Thu Dec 31 00:00:00 IST 2099, NodeLocked : false

    Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.
  5. On the primary Infrastructure Management server, 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.
  1. On the primary Infrastructure Management server, if you changed the publishing server startup mode from automated to manual before upgrading, change it back to automated. 
    Edit the pserver.conf file located in the installationDirectory/pw/server/etc folder and change the value of the parameter AutomatedStartMode to Automated.

  1. Stop the primary server by using the pw sys stop command. For more information, see Starting and stopping the TrueSight Operations Management components.

    • After stopping the primary server, ensure that all internal processes are stopped by using the pw process list command.
    • BMCTrueSight.service (Applicable only to version 11.3.04 and later on Linux)You can use the systemd service BMCTrueSight.service located in the /etc/systemd/system directory to start and stop the Infrastructure Management server on Linux. For more information, see Starting and stopping the TrueSight Operations Management components.
  2. Synchronize the cell database (MCDB) on the primary and secondary servers:
    1. Back up the installedDirectory\TrueSight\pw\server\var\<secondary_cell_name> folder (for example, pncell_<host name>#2) of the secondary server.
    2. Delete all content in the installedDirectory\TrueSight\pw\server\var\<secondary_cell_name> folder (for example, pncell_<host name>#2) of the secondary server.
    3. Copy all content from the installedDirectory\TrueSight\pw\server\var\<primary_cell_name> folder (for example, pncell_<host name>#1) of the primary server to the above location on the secondary server.
  3. On the secondary server, change the publishing server startup mode from automated to manual. Ignore this step if the startup mode is already set to manual.
    Edit the pserver.conf file located in the installationDirectory/pw/server/etc folder and change the value of the parameter AutomatedStartMode to Manual.

  4. Upgrade the secondary server. See:
    (Using the wizard) Upgrading-the-Infrastructure-Management-server-in-the-standalone-mode-using-the-wizard
    (Silently) Upgrading-the-Infrastructure-Management-Server-in-the-standalone-mode-silently

    Important

    When upgrading on the secondary server, do not use the KB folder migrated from the primary server. Use the migrated KB folder from the secondary server.

    If you upgraded as a non-root user, then after the installation is complete, you might see the following warning in the tsim_servicepack_log.txt file located at installedDirectory\pw\pronto\logs. You can ignore this warning.

    LOG EVENT {Description=[Error while updating BMCTrueSight],Detail=[/etc/init.d/BMCTrueSight (Permission denied)]}

    The secondary server is not yet in a usable state. Do not check for connectivity with the TrueSight Presentation Server until you perform the rest of the instructions in this section.

  5. Stop the secondary server by using the pw sys stop command. 

    After stopping the secondary server, ensure that all internal processes are stopped by using the pw process list command.

  6. Synchronize the cell database (MCDB) on the primary and secondary servers:
    1. Back up the installedDirectory\TrueSight\pw\server\var\<primary_cell_name> folder (for example, pncell_<host name>#1) of the primary server.
    2. Delete all content in the installedDirectory\TrueSight\pw\server\var\<primary_cell_name> folder (for example, pncell_<host name>#1) of the primary server.
    3. Copy all content from the installedDirectory\TrueSight\pw\server\var\<secondary_cell_name> folder (for example, pncell_<host name>#2) of the secondary server to the above location on the primary server.
  7. If you changed the publishing server startup mode from automated to manual before applying the feature pack or fix pack, change it back to automated. Do this on both servers.
    Edit the pserver.conf file located in the installationDirectory/pw/server/etc folder and change the value of the parameter AutomatedStartMode to Automated.
  8. (Linux) If you performed the upgrade as a non-root user, do the following on the primary and secondary servers:
    1. Log on as a root user.
    2. Run the <InstallationDirectory>/pw/scripts/create_startup_script script.
      This will enable the BMCTrueSight.service service creation.
  9. Start the primary server by using the pw sys start skipHAcheckNoValidate command.
  10. Ensure that the primary server has successfully started by running the pw license list command. The output should display a valid license expiration date, as in the following example:
    Feature : Server, Expiration : Thu Dec 31 00:00:00 IST 2099, NodeLocked : false
  11. Verify that the primary server is the active node by running the pw ha status command.
  12. Start the secondary server by using the pw sys start command.
  13. Ensure that the secondary server has successfully started by running the pw license list command. The output should display a valid license expiration date, as in the following example:
    Feature : Server, Expiration : Thu Dec 31 00:00:00 IST 2099, NodeLocked : false
  1. In the secondary Infrastructure Management server, 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.
  1. Verify that the secondary server is the standby node by running the pw ha status command.
    Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.
  2. After the TrueSight Infrastructure Management server upgraded successfully, if you observe any self monitoring events are open when the primary server is running in active mode and secondary serve is running in standby mode, close it manually.

Post-upgrade task

  • Ensure that you review the information in the Troubleshooting-version-11-3-04-upgrade-and-post-upgrade-issues topic after you upgrade.

  • If you have customized the password for the bppmws_internal user account before the TrueSight Infrastructure Management Server upgrade, use one of the following options to sync the password after the upgrade. In a HA environment, ensure that you run these steps on both the HA nodes.

    • Option 1:Update the properties file manually
    1. On the Infrastructure Management server, go to the following backup file location:
      <InstallationDirectory><OLD_VERSION>/pw/pronto/conf/bppmws_internal.properties
      <OLD_VERSION> is the version that you are upgrading from.
    2. Copy the value for the property bppmws_internal_key from the preceding properties backup file and replace the value in the following file:
      <InstallationDirectory>/pw/pronto/conf/bppmws_internal.properties
    3. Restart theTrueSight Infrastructure Management server.
    • Option 2:Update the properties file using CLI command
    1. Open a command prompt on the Infrastructure Management server and run the following command:
      pw internaluser change_passwd
    2. Enter the new password.
      The new password is validated with Remedy SSO and then updated.
    3. Restart the Infrastructure Management server.

  • Due to security reasons, the following property is set to false during the upgrade.
http.enabled:false

If you want to monitor the Elasticsearch, set the above property to true in the elasticsearch.yml file at the following directory path after the upgrade as applicable:

  • (On Linux)<TRUESIGHTPSERVER_HOME>/truesightpserver/modules/elasticsearch/config/
  • (On Windows) <TRUESIGHTPSERVER_HOME>\truesightpserver\modules\elasticsearch\config\

Note

On a high-availability environment, perform the preceding steps on both the primary and secondary servers.

Troubleshooting upgrade issues

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

Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.

 

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