Update core modules using the script.

During this step, you will update the core modules on all of the servers. Core modules must be updated prior to any others, and they must be updated from the command line using the launch-update script.

Procedure

  1. The launch-update script is delivered through the module-manager, so update the module-manager module by typing the following command from the /opt/APG/bin directory:
    ./manage-modules.sh update module-manager
  2. Navigate to the <install directory>/Tools/Module-Manager/<version no.>/bin directory.
    For example, the Module Manager version can be <install directory>/Tools/Module-Manager/1.16u3/bin.
  3. Change the permissions for the launch-update.sh script:
    chmod u+x launch-update.sh
  4. Run ./launch-update.sh
    You can run this script on multiple servers at the same time.
    On the frontend server, you may see a message about frontend search being deprecated. VMware Smart Assurance recommends that you select, "yes."
    Note: Upgrade from 6.8u5 and 7.0u8 to 7.2.0.1 does not need event migration, as both of these have Elastic Search database. Also, running the event migration task throws an exception, which can be ignored.
  5. Review the modules that will be updated and the SolutionPacks that will be reconfigured. At the Proceed? prompt, press Enter to launch the update.
    The script starts updating modules. Let the script run uninterrupted. Once completed, the script lists which modules and SolutionPacks were updated and reconfigured successfully.
    All modules except block-type modules are updated by the script. Block-type modules are updated later through the UI.
    Note: It is normal for the Topology-Mapping Service on the primary backend, the frontend, or the additional backend to remain stopped at this point. The service will start automatically when the SolutionPack for VMware Smart Assurance M&R Health is upgraded on these systems.