Upgrading Unified Manager on Red Hat Enterprise Linux or CentOS

You can upgrade from Unified Manager version 7.3 or 9.4 to Unified Manager 9.5 by downloading and running the installation file on the Red Hat platform.

Before you begin

About this task

Note: These steps contain information for systems that are configured for high availability using Veritas Operation Manager. If your system is not configured for high availability, ignore these additional steps.

Steps

  1. Log in to the target Red Hat Enterprise Linux or CentOS server.
  2. Download the Unified Manager bundle to the server.
  3. Navigate to the target directory and expand the Unified Manager bundle: unzip OnCommandUnifiedManager-rhel7-9.5.zip
    The required RPM modules for Unified Manager are unzipped to the target directory.
  4. Confirm the presence of the listed modules: ls *.rpm
    The following RPM modules are listed:
    • ocie-au-<version>.x86_64.rpm
    • ocie-server-<version>.x86_64.rpm
    • ocie-serverbase-<version>.x86_64.rpm
    • netapp-application-server-<version>.x86_64.rpm
    • netapp-platform-base-<version>.x86_64.rpm
    • netapp-ocum-<version>.x86_64.rpm
  5. Optional: For systems that are not connected to the Internet or that are not using the RHEL repositories, perform the following steps to determine whether you are missing any required packages and download those packages:
    1. View the list of available and unavailable packages: yum install *.rpm --assumeno
      The items in the "Installing:" section are the packages that are available in the current directory, and the items in the "Installing for dependencies:" section are the packages that are missing on your system.
    2. Download the missing packages on another system that has Internet access: yum install package_name --downloadonly --downloaddir=.
      Note: Because the plug-in "yum-plugin-downloadonly" is not always enabled on Red Hat Enterprise Linux systems, you might need to enable the functionality to download a package without installing it: yum install yum-plugin-downloadonly
    3. Copy the missing packages from the Internet-connected system to your installation system.
  6. If Unified Manager is configured for high availability, then using Veritas Operation Manager, stop all Unified Manager services on the first node.
  7. Upgrade Unified Manager using the following script: upgrade.sh
    This script automatically executes the RPM modules, upgrading the necessary supporting software and the Unified Manager modules that run on them. Additionally, the upgrade script checks whether there are any system configuration settings or any installed software that will conflict with the upgrade of Unified Manager. If the script identifies any issues, you must fix the issues prior to upgrading Unified Manager.
    Important: Do not attempt to upgrade by using alternative commands (such as rpm -Uvh ...). A successful upgrade requires that all Unified Manager files and related files are upgraded in a specific order to a specific directory structure that are executed and configured automatically by the script.
  8. For high availability installations, stop all Unified Manager services on the second node with Veritas Operation Manager.
  9. For high availability installations, switch the service group to the second node in the high-availability setup and upgrade Unified Manager on the second node.
  10. After the upgrade is complete, scroll back through the messages until you see the message displaying an IP address or URL for the Unified Manager web UI, the maintenance user name (umadmin), and the default password.
    The message is similar to the following:
    OnCommand Unified Manager upgraded successfully.
    Use a web browser and one of the following URLs to access the OnCommand Unified Manager GUI:
    
    https://default_ip_address/    (if using IPv4)
    https://[default_ip_address]/  (if using IPv6)
    https://fully_qualified_domain_name/

After you finish

Enter the specified IP address or URL into a supported web browser to start the Unified Manager web UI, and then log in by using the same maintenance user name (umadmin) and password that you set earlier.