Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Upgrading the PSM Server

 

This procedure describes how to upgrade the PSM server to Release 7.7 using an installation DVD or ISO image.

  • Obtain the PSM DVD or ISO image.

Note

Do not use this procedure if you are upgrading from Release 5.2 or earlier. Follow the procedure in Upgrading the PSM Server instead.

Note

Before starting this procedure, consult the proNX Service Manager Release Notes for this release. The proNX Service Manager Release Notes contains important information relating to installing and upgrading software for this release, and might require you to take additional steps prior to or after executing this procedure.

Note

The proNX Service Manager Release Notes specifies the allowed upgrade paths for this release. Contact Juniper Networks Support when upgrading from releases that are not explicitly specified.

  1. Log in to the PSM server.
  2. Ensure the current PSM server version is one of the releases from which upgrade to this release is supported. For example:
  3. Optionally, save any configuration that will be overwritten.
    1. If you have made any changes to the property values in the workers.xml file, save that file so that they do not get overwritten during the server upgrade.

      Locate the workers.xml file in directory /usr/local/ems9001/resources/serverConfigurations/ and copy it to a location where it will not be overwritten during the server upgrade, preferably onto another machine.

    2. If you have developed any custom server scripts, save those files so that they do not get overwritten during the server upgrade.

      Locate the scripts in the directory /usr/local/ems9001/conf/serverScripts and copy them to a location in which they will not be overwritten during the server upgrade, preferably onto another machine.

    3. Scheduled discoveries are also lost during the upgrade. If you have any scheduled discoveries, ensure you have the information to reschedule those discoveries so that you can restore them when you launch the new client.

  4. Generate a backup of the existing PSM server database as follows:
    1. Stop the server by entering the following command:

      The stop command is successful when the 'Ems-' processes all change to 'not monitored' state. Type <ctrl> c to exit the Linux watch command window.

    2. Export the PSM server database. For example:

      The database backup file is stored in the /tmp directory.

      Note

      If a problem occurs during the upgrade that prevents the database from being automatically imported, import the database manually after you have finished upgrading. For example:

      For information on how to restore the database from a backup, see Restoring the PSM Server Database from a Backup .

  5. Insert the PSM DVD into the DVD drive of the server or copy the PSM ISO image onto the server.
  6. Mount the DVD or the ISO. The mount directory (/media) in the following commands can be changed.

    To mount the DVD:

    To mount the ISO:

    where PSM-xxx.iso is the name of the ISO file (for example, PSM-7.7.0.iso).

  7. Copy the RPM file from the mounted DVD or ISO to any location on the server workstation. For example:
  8. Upgrade to the new PSM server.
    1. To reduce the risk of database corruption while installing, execute the installation within the Linux screen terminal. Commands launched within the screen terminal continue to run even if your connection to the server is lost.

      The screen terminal is launched.

    2. In the screen terminal, navigate to the location where the RPM file was copied, and start the installation. For example:

      Note

      If your connection to the server is lost during this step, log back in from any machine and type screen -r to reattach the screen.

      Tip

      If you do not want to wait around for the installation to finish executing, you can detach the screen and reattach it at a later time. To detach the screen, type <ctrl> a then d. The screen is detached and the installation command executes in the background. To reattach the screen, type screen -r.

      The following is an example of the upgrade output. Your output might differ depending on release and configuration:

      The output indicates that the following events occurred:

      • The PSM server is stopped and the software is uninstalled.

      • The new RPM package is expanded

      • The operating system firewall is updated with new rules for PSM

      • The MySQL database is dropped and reinitialized with new schemas

      • The Monit process manager is re-initialized to start managing the PSM

      • Other necessary third-party or open source software packages start

      The following directory is created:

      Note

      The proNX Service Manager files are installed in the above directory. A softlink is created to this directory at:

    3. Exit the screen terminal.

      This closes the Linux screen terminal and returns you to the original shell.

  9. Unmount the DVD or ISO. Enter:
  10. Reboot the server.
  11. After the server machine has rebooted, log back in and confirm that the PSM server is up and running.

    The 'Ems-' processes should all be in the "Running" state. You might need to wait a few minutes before the 'Ems-' processes all change to the "Running" state. Type <ctrl> c to exit the Linux watch command window.

  12. To confirm that the new version of the server is installed, check the version information:

    Look for the 'ems9001-' entry and confirm that the version is indeed the correct release.

    If you do not have any configuration you need to restore from 3, then you have completed the server installation. Otherwise, proceed to the next step.

  13. If you have to restore changes to the property values in the workers.xml file, do the following:

    Reapply the changes from the old workers.xml file that you saved in 3. Do not simply overwrite the new file with the old ones, as there might be new properties defined in the new file that are required in the new software release. Instead, edit the file, identify the changes in the old file that you want to keep, and make those changes in the new workers.xml file. When you are done, save and close the new workers.xml file.

  14. If you have to restore custom server scripts, copy the scripts back to the /usr/local/ems9001/conf/serverScripts directory.
  15. To activate these changes, restart the PSM server.

    The restart command successfully completes when the 'Ems-' processes all change to the "Running" state. Type <ctrl> c to exit the Linux watch command window.

You have successfully upgraded the PSM server.