You upgrade each product in one of three ways: CLI mode, Unattended mode, and Wizard mode only for SAM Console.

Perform the following tasks:

  1. Review the important release issues found in your product-specific release notes.
  2. On the host where the target existing installation resides, log in as superuser (User ID 0) or administrator.
  3. Choose CLI mode (UNIX only), or Unattended mode. The setup commands for invoking CLI mode and Unattended mode are listed in Table 2-1 "Setup command syntax for CLI mode" in the section Setup command syntax for CLI mode" and in Table 2-2 "Setup command syntax for Unattended mode" in the section Setup command syntax for Unattended mode".
    Note: Before upgrading your product, you must stop all the VMware Smart Assurance services. Also, stop the ic-serviced daemon Smart service, using command /etc/init.d/ic-serviced stop.
    • In CLI mode, make the following additional selections:

      • In the Upgrade or Install screen, select Upgrade existing suite and press Enter.

        • In the Target Installation Selection screen (in which an existing product is selected unless the product was previously installed to more than one directory, in which case you will see multiple choices), select a target installation directory and press Enter.

        • In the Choose Products screen, all of the existing products are selected to be upgraded. You can select additional products to add to the installation.

        • Specify any additional local directories created using SM_SITEMOD. Press Enter.

      • In Unattended mode, specify the following additional options in the response file (<product>-response.txt). All previously installed products must have their product options set to “true” in the response file.

        • Uncomment the -INSTALL_TYPE.INSTALL_CHOICE option.

        • Uncomment the -SITEMOD_BEAN.SITEMODS_VAR option, and provide one or more directory locations to perform an upgrade. You can provide the name of the directories, or the directory name with absolute path.

          For example, on Linux:

          SITEMOD_BEAN.SITEMODS_VAR=local-1:/opt/InCharge/SAM/smarts/Local-2

          :local-3

          Note: For specifying directory separators, use : on Linux.
        • Uncomment the MERGE_OPTION_UPGRADE.MERGE_CHOICE=MERGE option to perform the merge.

        • Uncomment the < product >.installLocation option and set its property value to the installation directory of the target installation.

      • In Wizard and CLI mode for SAM Console Windows , make the following additional selections:

        • In the Upgrade screen, select Upgrade existing suite and click Next or press Enter.

          • In the Target Installation Selection screen provide the old installation directory and click Next or press Enter.

            For example: If older selection is present at C:\InCharge\Console path, then provide directory as C:\InCharge. Also, user needs to manually provide the directory path.

          • Specify any additional local directories created using SM_SITEMOD. Click Next or press Enter.

          • In the Broker Specification screen, specify the VMware Smart Assurance Broker.

            • If you are installing the Broker, specify the port and hostname.

              • If the Broker is already running on this host, keep the default values.

              • If the Broker is running on another host, specify the hostname of that system and the port that the Broker uses.

                Click Next to continue.

      Note: Security configuration file (i.e runcmd_env.sh) will not be merged automatically and needs to be merged as explained under section, Migration of security configuration files.
  4. The installation program displays the Directories created using SM_SITEMOD screen which allows you to back up local directories that were created with SM_SITEMOD. If you used SM_SITEMOD to create local directories, enter a list of local directories. Click Next or press Enter.

    The installation program then runs the sm_migrate utility to create a backup file of the user-customized files and base files in the existing installation. The backup file, named .migrate.bkp.<version>, is saved to the BASEDIR/smarts directory.

  5. The installation program removes the patch, if any, from the existing installation and installs the software.

  6. After the installation, the installation program shows the Restore User Configurations Instructions screen, which presents the sm_migrate command for restoring the old user-customizations in the .migrate.bkp.<version> backup file to the BASEDIR/smarts/local directory. The screen provides two options:

    1. Yes, merge the files - Select this option if you want the utility to automatically merge the files modified by you.

    2. No, I will merge them later - Select this option if you want to manually merge the files modified by you.

      Click Next or press Enter to view the Installation Summary.

      Note: For Service Assurance Manager, the upgrade process inserts the _edaa user entry into the security configuration file serverConnect.conf and the runcmd_env.sh file. The upgrade process does not modify the clientConnect.conf, brokerConnect.conf, and imk.dat files. The upgrade process does not insert the _edaa user entry into the files of Domain Managers.

      For Domain Managers, copying the security configuration files clientConnect.conf, serverConnect.conf, brokerConnect.conf, runcmd_env.sh, and imk.dat is not supported in an upgrade installation. You can manually copy the security configuration files using sm_migrate utility as described in “Restoring customizations after an upgrade installation” on page 89.

  7. The Installation Summary shows informational messages such as successful confirmations, error messages, and warnings. Investigate any errors or warnings.

    If Next appears, your system needs to be rebooted because one or both of the following tasks are pending on the system:

    • A system-protected file was replaced during the installation and requires a restart.

      • A pending restart was triggered by another application or by an operating system patch installation.

        Click Next or press Enter and then reboot your system. Otherwise, click Finish or press Enter to exit the installation.

        The installation program writes an install log file to the BASEDIR/smarts/setup/logs directory, unless the installation fails at the very start, in which case the installation program writes the log file to the /tmp directory. The log file is a text file with the naming convention Install.<product>.<productversionNumber>.log.

  8. Evaluate your custom code. Review the “Custom file migration use cases” on page 91. The sm_migrate utility migrated all user-customized files from the existing installation to the BASEDIR/smarts/local directory in the 10.1.5 installation. Review the output of the sm_migrate utility and evaluate if you would like to keep the user-customized files in the new installation.

    Configuration migration process logs on page 95 provides more information on the log files that are created after the migration of user-customized files.

  9. Depending on your deployment, ensure that the BASEDIR/smarts/local/conf/runcmd_env.sh file includes the environment variables, SM_TLS_PROTOCOLS and SM_ALLOW_LEGACY_CRYPTO.

    Use SM_TLS_PROTOCOLS set to the +TLSv1.1 value only if you need to interoperate with Smarts products based on Foundation 9.0.0.0 Build 1345 through 9.2.x.

    Use SM_ALLOW_LEGACY_CRYPTO set to TRUE only if you need to interoperate with Smarts products based on Foundation versions prior to 9.0.0.0 Build 1345.

    Check the version number on page 102 provides the sm_server --version command to determine the Foundation (DMT) version.

    To ensure that the runcmd_env.sh file includes the environment variables:

    1. Go to the BASEDIR/smarts/bin directory and enter this command to open the runcmd_env.sh file:

      sm_edit conf/runcmd_env.sh
      
    2. Search for the environment variables. If they do not exist, add one or both depending on your deployment:

      SM_TLS_PROTOCOLS=+TLSv1.1
      SM_ALLOW_LEGACY_CRYPTO=TRUE
      
    3. Save and close the file.

  10. Optional for IP Manager, run the repository file migration utility (sm_migraterps) to make the repository file compatible with the newer 10.1.5 version of the software as described in “Automatically migrate topology for IP Manager using RPS utility” on page 96.

  11. If your product is part of a deployment that requires the Federal Information Processing Standard (FIPS) Publication 140-2, a U.S. government computer security standard governing cryptographic modules, follow the instructions in “Upgrading 9.5.1 products in FIPS mode” on page 60.

  12. If you installed the products as services, start the services. Starting services on UNIX on page 105 provides more information.

  13. Verify the current state of the products and Broker. “Verify the product status” on page 110 provides more information.

  14. Initiate a discovery. Consult the discovery guide or user guide for your product for more information on this procedure.

  15. For Server Manager,

    1. In the Domain Manager Administration Console, right-click on the ESM server (INCHARGE-ESM, by default) in the left pane and select the Load All ESM Host monitoring data from Backup option.

    2. Perform a discovery (Topology > Discover All) from the ESM server.

      All of the applications that were configured prior to the upgrade are restored and Server Manager starts to monitor those applications.

    Note: After performing an upgrade, you need to restart the ic-serviced process using the following command: /etc/init.d/ic-serviced start and start all the services.