Upgrade > Upgrade > Upgrading a single-host Core

Upgrading a single-host Core

If you are upgrading a Multimaster Mesh, use the instructions shown in Upgrading a multimaster mesh.

Ensure that all CORD patches have been uninstalled, see Uninstalling All CORD patches.

To exemplify the steps listed below, a core with the following layout is used:

Server Core Components installed
192.168.100.1
  • SA-installed Oracle database and Model Repository
  • Core Infrastructure Components
  • Slice
  • OS Provisioning Components

  1. On the core host, invoke the SA upgrade script as a user with root privileges:

    /<distro>/opsware_installer/hpsa_upgrade.sh –c <CDF_full_path>

    where <distro> is the full path to the distribution media. For example:

    /<mountpoint>/hpsa-primary/disk001

    If for security reasons, you have stored your response files in a location other than the default location on the host being upgraded, you can copy the files to the /var/opt/opsware/install_opsware/resp directory on the core to be upgraded. You must also provide the CDF file with the –c option (by default, it is saved in the /var/opt/opsware/install_opsware/cdf directory).

  1. The SA upgrade script determines the component layout of your core and the Specify Hosts to Upgrade screen displays. It will look similar to the following:

    Specify Hosts to Upgrade

    ========================

    Currently specified hosts:

    192.168.100.1

    Please select one of the following options:

    1. Add/edit host(s)

    2. Delete host(s)

    Enter the option number or one of the following directives

    (<c>ontinue, <p>revious, <h>elp, <q>uit):

    Since this is a single core upgrade (all components to be upgraded are installed on the same host, enter c and Enter to continue.

  1. The prompt to select the cryptographic protocol is displayed.

    Cryptographic Protocol Selection for the Server Automation Components
    [WARNING] Please make sure that all the cores and satellites from the mesh are at the same TLS level.
    ========================================================================
    1. TLSv1
    2. TLSv1.1
    3. TLSv1.2
    Enter the option number or one of the following directives
    (<p>revious, <h>elp, <q>uit)[1]:

    See the SA 10.51 upgrade section for details.

  1. A parameter confirmation interview is displayed:

    Interview Parameters
    ====================
    Navigation keys:
    Use <ctrl>p to go to the previous parameter.
    Use <ctrl>n to go the next parameter.
    Use <tab> to view help on the current parameter.
    Use <ctrl>c to abort the interview.
    Parameter 1 of 5 (windows_util_loc)
    Please enter the directory path containing the Microsoft patching utilities. Press Control-I for a list of required files or enter "none" if you do not wish to upload the utilities at this time [none]:
    Parameter 2 of 5 (truth.servicename)
    Please enter the service name of the Model Repository instance in the facility where Opsware Installer is being run [truth.Core1]:
    Parameter 3 of 5 (db.sid)
    Please enter the SID of the Oracle instance containing the Model Repository [truth]:
    Parameter 4 of 5 (db.port)
    Please enter the port on which the database is listening. [1521]:
    Parameter 5 of 5 (db.orahome)
    Please enter the path of the ORACLE_HOME directory of your Model Repository (truth) server. [/u01/app/oracle/product/12.1.0.2/db_2]:
    All values are entered.  Do you wish to continue? (Y/N) [Y]:

  1. The Host Component Layout screen displays again. 

    Upgrade components
    ==================
    Components to be Upgraded
    -------------------------
    Model Repository, First Core
    Core Infrastructure Components
    Slice
    OS Provisioning Components
    Software Repository - Content (install once per mesh)
    Up-to-date Components (will not upgrade)
    ----------------------------------------
    Oracle RDBMS for SAS

    Press c to continue.

  1. At this point, a prerequisite check is performed to ensure the host meets certain basic SA requirements. You may see a display similar to the following:

    Prerequisite Checks
    ===================
    Results for <IP_address>
    WARNING Insufficient swap space (2 GBytes).
    4 GBytes is the recommended for core_inst.
    File system '/' has XXXXX Mbytes available and XXXXXX is         recommended.
    Enter one of the following directives
    (<c>continue, <p>revious, <h>elp, <q>uit):

    You should attempt to meet the requirements specified in these warnings, however, you may be able to continue the upgrade if you are unable to meet the recommended settings. Press c to continue.

    Note For a Core upgrade with underlying database as Oracle 11g, if the upgrade fails after performing the Model Repository upgrade, the pre-check will prompt the following errors when you restart the upgrade process:

    FAILURE Oracle optimizer_index_caching = 0 ; required to be = 80
    FAILURE Oracle optimizer_index_cost_adj = 100 ; required to be = 20

    These errors are the result of changes that were performed when you upgrade the Model Repository successfully. You can ignore this error and continue the upgrade process.

  1. At this point the upgrade begins and you will see a series of informational messages displayed on the screen as the upgrade progresses. On completion of the upgrade, a success message displays.

  2. You should now upgrade the SA Agents installed on managed servers. See Post-upgrade tasks for details.

.

Send Help Center feedback