Applying service packs on the Infrastructure Management server in the application high-availability mode

Where you are in the Applying service packs process

The page .Applying service packs on 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

To apply the service pack on the Infrastructure Management server in the application high-availability mode

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

    Note

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

  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. Apply the service pack on the primary server. See:
    (Using the wizardApplying service packs on the Infrastructure Management server in the standalone mode using the wizard
    (SilentlyApplying service packs on the Infrastructure Management server in the standalone mode silently

    If you applied the service pack 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

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

    Note

    After stopping the primary 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\<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.
  7. 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.
  8. Important

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

    Apply the service pack on the secondary server. See:

    (Using the wizardApplying service packs on the Infrastructure Management server in the standalone mode using the wizard
    (SilentlyApplying service packs on the Infrastructure Management server in the standalone mode silently

    If you applied the service pack 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)]}

    Note

    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.

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

    Note

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

  10. 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.
  11. If you changed the publishing server startup mode from automated to manual before applying the service 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.
  12. (Linux) If you applied the service pack as a non-root user, perform the following steps on the primary and secondary servers:
    MultiExcerpt named stepsforstartingTSIMservice was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro
  13. Start the primary server by using the pw sys start command.
  14. 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
  15. Verify that the primary server is the active node by running the pw ha status command.
  16. Start the secondary server by using the pw sys start command.
  17. 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


Was this page helpful? Yes No Submitting... Thank you

Comments