25.1 Upgrading the Appliance by Using zypper

To upgrade the appliance by using the zypper patch:

  1. Back up your configuration, then create an ESM export.

    For more information, see Backing Up and Restoring Data in the NetIQ Sentinel Administration Guide.

  2. (Conditional) If you have customized the configuration settings in the server.xml, collector_mgr.xml, or correlation_engine.xml files, ensure that you have created appropriate properties files named with the obj-component id to ensure that the customizations are retained after the upgrade. For more information, see Maintaining Custom Settings in XML Files in the NetIQ Sentinel Administration Guide.

  3. Log in to the appliance console as the root user.

  4. Run the following command:

    /usr/bin/zypper patch

  5. (Conditional) If you are upgrading Sentinel 7.0.1 or earlier, enter 1 to accept the vendor change from Novell to NetIQ.

  6. (Conditional) If you are upgrading Sentinel versions prior to 7.2, the installer displays a message that indicates to resolve dependency for some appliance packages. Enter 1 for deinstallation of dependent packages.

  7. (Conditional) If you are upgrading Sentinel 7.2 or later, the installer displays an option that indicates change in the ncgOverlay architecture. Enter the appropriate option to accept the architecture change.

  8. Enter Y to proceed.

  9. Enter yes to accept the license agreement.

  10. Restart the Sentinel appliance.

  11. (Conditional) If Sentinel is installed on a custom port or if the Collector Manager or the Correlation Engine is in FIPS mode, run the following command:

    /opt/novell/sentinel/setup/configure.sh

  12. Clear your Web browser cache to view the latest Sentinel version.

  13. Clear the Java Web Start cache on the client computers to use the latest version of Sentinel applications.

    You can clear the Java Web Start cache by either using the javaws -clearcache command or by using Java Control Center. For more information, see http://www.java.com/en/download/help/plugin_cache.xml.

  14. (Conditional) If the PostgreSQL database has been upgraded to a major version (for example, 8.0 to 9.0 or 9.0 to 9.1), clear the old PostgreSQL files from the PostgreSQL database. For information about whether the PostgreSQL database was upgraded, see the Sentinel Release Notes.

    1. Switch to novell user.

      su novell

    2. Browse to the bin folder:

      cd /opt/novell/sentinel/3rdparty/postgresql/bin

    3. Delete all the old postgreSQL files by using the following command:

      ./delete_old_cluster.sh

  15. (Conditional) If you are upgrading from Sentinel 7.1.1 or earlier, the installer does not migrate the security intelligence (SI) data by default. To migrate SI data from Sentinel 7.1.1 or earlier, manually enable SI data migration as follows:

    1. Switch to novell user.

      su novell

    2. Open the /etc/opt/novell/sentinel/config/server.xml file.

    3. Add the following property in the BaseliningRuntime component section:

      <property name="baselining.migration.check">true</property>

    4. Restart the Sentinel server.

  16. (Conditional) To upgrade the Collector Manager or the Correlation Engine, follow Step 3 through Step 11.