Install SA first (primary) core with a secondary Core (multimaster mesh)

This section provides an installation summary for a Single Host SA First (Primary) Core with a secondary Core (Multimaster Mesh). The cores in a mesh can be installed with any of the configurations described in the samples above.

Phase 1: Installing the SA first (primary) Core

Decide the configuration you will use and follow the instructions described in the configuration samples.

After the first (primary) Core installation is complete, you can install secondary Cores for your Multimaster Mesh.

Overview of the secondary Core installation process

The following are the typical phases of installing a secondary Core:

1. Prepare for Installation: Ensure that all installation prerequisites have been met, that you have the information needed to complete the Installer interview, that you have all necessary permissions to complete the installation, and that you have the SA installation media. For more information, see System requirements for installation

2. On the first core infrastructure host, define a new facility and export first Core Model Repository content: During this phase you define the facility in which the new secondary Core is to be installed, export the First Core's Model Repository content, and copy the resulting export files to the new secondary Core host.

3. On the server that will host the new secondary Core, install the Oracle database and install the secondary Core Components: During this phase you can install the SA-supplied Oracle database for the secondary Core(s) Model Repository. This database is automatically configured to work with the SA Model Repository. See Oracle setup for the Model Repository for information about the SA Oracle database configuration differs from a default Oracle configuration.

   Alternatively, you can install a database using the Oracle Universal Installer or use an existing Oracle 12c database installation (Oracle 10 and 9i are not supported) and select to use an existing database during installation. However, there are database configuration requirements that must be met in order for such databases to be compatible with the SA Model Repository.

   See Oracle setup for the Model Repository.

   You will also install the secondary Core's components and import the Model Repository content that was exported from the First Core into the database.

4. Post Installation Tasks: During this phase you must perform various post-installation tasks to complete the configuration of the new secondary Core.

Phase 2: Prepare to add the secondary Core

This section describes adding secondary Cores that, with an existing first Core, create a Multimaster Mesh of SA Cores that can coordinate server management. The cores in a mesh can be installed with the same configurations as the primary cores. See the sample configurations described in the section above.

To prepare to add a secondary Core, perform the following tasks:

1. Locate the SA Product Software (primary) and, if you will install the SA-supplied Oracle database used by the SA Model Repository, the Oracle_SA media.
2. On the First Core’s Infrastructure Component server and on the server that will host the new secondary Cores Model Repository, mount the SAProduct Software (primary) and Oracle_SA media or NFS-mount the directory that contains a copy of the media.

Prepare the environment

1. Ensure that the following folders have enough free space for the database export:
   • Database server path - <DATA_PUMP_DIR>
   • Database server path - /var/tmp
   • Model Repository server path - /var/tmp
   • Model Repository server path specified by installer parameter - <truth.dest>

   To estimate the export size, run the following command:

   <install_media>-primary/disk001/opsware_installer/tools/calculate_export_size.sh <ORACLE_HOME> <sid> <oracle_admin_password> <service_name>

   You can find the values for the required parameters in the CDF file of the primary core.

   Example: calculate_export_size.sh /u01/app/oracle/product/12.1.0/db_1 truth password truth.PrimaryCore

2. Before starting the primary database export, ensure that the COMPATIBLE parameters in the primary and secondary database init.ora file are set correctly. SA recommends setting the COMPATIBLE parameter to the Oracle RDBMS software version. Refer to the Oracle documentation for information on how the COMPATIBLE parameter affects the Data Pump Export-Import process.
3. The Oracle Data Pump Export-Import process also depends on the Oracle Client version (expdp and impdp). For remote database installations, SA strongly recommends the Oracle Full Client be the same version as the Oracle RDBMS software. Refer to the Oracle documentation for information about how the Oracle Client version affects the Data Pump Export-Import process.

Phase 3: Export first core files to a TAR.GZ file and copy to the new secondary Core host

In this phase, you export First Core files (CDF, cryptographic material) into a TAR.GZ file that must be copied to the new secondary Core.

1. On the First Core host, create a directory in which the TAR.GZ file will be saved. You can specify a custom location or accept the default:

   /var/opt/opsware/truth

   cd /

2. On the server that hosts the First Core’s Infrastructure Component host, invoke the Add Datacenter to Mesh script (hpsa_add_dc_to_mesh.sh).

   Specify the full path to the Facility definition script.

   For example:

   /<distro>/opsware_installer/hpsa_add_dc_to_mesh.sh

   where <distro> is the full path to the Product Software (primary) media.

   
   A screen similar to the following appears:

   ---------------------------------------

   add_dc_to_mesh will be performed on the following identified core host(s). If there is any inconsistency then try again with the correct CDF.

   16.77.42.65  (oracle_sas, truth_mm_overlay)

   16.77.41.24  (infrastructure, word_uploads)

   16.77.43.252  (slice, osprov)

   ---------------------------------------

   Do you want to continue (Y/N) [Y]:

   Type Y and press Enter to continue.

3. Provide the OS credentials for each host in the list shown below:

   Host Passwords
==============

   Parameter 1 of 2

   <ip_address> user [root]:

   Parameter 2 of 2

   <ip_address> password []:******

   You are prompted for the credentials for each specified host. SA validates each credential. After you provide all required credentials, you see the following message:

   All values are entered. Do you wish to continue? (Y/N) [Y]:

   Enter Y to continue.

   After you provide all required credentials, the SA Installer attempts to set up NFS mounts to the installation media and prepares each specified server for the installation.

   For the next step, the secondary Core will use the FIPS compliance settings you specified during the installation of the Primary Core. You will not be prompted for FIPS enablement during the secondary Core installation.

4. Select the type of Oracle installation for the secondary Core.
   secondary Core Oracle installation
==================================

1. Install Oracle with SA
2. Use existing Oracle database
Enter the option number or one of the following directives
(<p>revious, <h>elp, <q>uit): 2

   Note If you chose to use an existing Oracle database (remote customer-supplied database) for the secondary Core install, ensure that the secondary Core’s Oracle database has already been installed and configured before running the add_dc_to_mesh process. The remote Oracle database must have been configured as described in Non-SA-supplied Oracle software and database setup.

5. Provide values for the following Interview parameters:

   Note You must provide the value of newCore.dcDispNm parameter within double quotes.

   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 11 (truth.dest)

   Please enter the full path to the directory where the export file will be saved [/var/opt/opsware/truth/]:

   Parameter 2 of 11 (newCore.dcNm)

   Please enter the short name of the new facility you would like to define (no spaces) []: SLAVE

   Parameter 3 of 11 (newCore.dcDispNm)

   Please enter the long name for the facility that you are adding to the mesh. [SLAVE]:

   Parameter 4 of 11 (newCore.dbHost)

   Please enter the hostname/IPaddress of the server where you are planning to install the Oracle database in the new facility. []: 16.77.1.191

   Parameter 5 of 11 (newCore.dbPort)

   Please enter the port on which the database is listening for the new facility [1521]:

   Parameter 6 of 11 (newCore.dbSid)

   Please enter the SID of the Oracle instance containing the Model Repository for the new facility [truth]:

   Parameters 5 and 6 are only displayed if you chose to use an existing (non-SA supplied) Oracle database for the secondary Core.

   Parameter 7 of 11 (newCore.mgwIP)

   Please enter the IP address of the server where you are planning to install the Infrastructure component in the new facility (or where the management gateway will be installed). []: 16.77.1.192

   Parameter 8 of 11 (newCore.dcSubDom)

   Please enter the subdomain for the facility you are about to create (lowercase, no spaces) [slave.com]:

   Parameter 9 of 11 (newCore.servicename)

   Please enter the tnsname of the Model Repository instance that you will be installing in the new facility [truth.SLAVE]:

   Parameter 10 of 11 (db.port)

   Please enter the port on which the database is listening. [1521]: 1521

   Parameter 11 of 11 (db.orahome)

   Please enter the path of the ORACLE_HOME directory of your Model Repository (truth) server. [/u01/app/oracle/product/12.1.0/client_1]:

   Parameters 10 and 11 refer to the port and ORACLE_HOME directory for the Primary Core Model Repository.

   You are asked to re-enter any required passwords for confirmation.

   After you have entered or accepted all required values, you see this prompt:

   All values are entered. Do you wish to continue? (Y/N) [Y]:

   End of interview.

   Type Y to continue. If you need to re-enter a value, type N.

6. Specify the way in which the file transfer between the cores will be done:

   File transfer mode

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

   Do you want to manually transfer files from the primary to the secondary Core? [N]:

   For manual file transfer, manually copy all necessary files from the primary core to the secondary Core servers once the add_dc_to_mesh process is complete. With an auto file transfer, all files will be transferred automatically between cores.

   If you choose to manually transfer files, a message containing instructions on how to perform this will be printed. After the add_dc_to_mesh process is complete, you can still find this message in the log files. The instructions will be similar to the following:

   When running the manual add_dc process, you will need to manually copy the files necessary for the secondary Core install from the primary core servers to the secondary Core servers.
   The list of files that need to be copied is:
   1.Truth files
    Truth files need to be copied from the primary core’s truth server on the server on which the secondary Core install will run.
    These files are:
           - truth.SLAVE.tar.gz
           - cdf.SLAVE.xml
    They can be found on the primary core’s truth in the /var/opt/opsware/truth/ directory.
   
   2.Database export
    The db export files (*.dmp) need to be copied from the primary core’s database server on the secondary Core’s database server.
    If you choose to install the secondary DB server with SA, you will need to copy these *.dmp files in a temporary directory on the server, eg. /var/tmp/dbExport.
    If you will use an existing Oracle server for the secondary Core, you will need to copy these files in the datapump directory.
    To determine the datapump directory path, run the following query on the secondary Core’s Oracle server:
           select DIRECTORY_PATH from dba_directories where DIRECTORY_NAME=’DATA_PUMP_DIR’;
   

   Note If you choose to automatically transfer files, you will need to supply the credentials for the secondary Core’s Oracle server and Infrastructure server in the next steps. If, for some reasons, the add_dc_to_mesh process fails after exporting the Model Repository, you will need to manually copy the files specified above on the secondary Core servers and restart the primary core’s services if necessary.

7. The following prompts (up until prompt 12) will be displayed only if you have selected the automatic file transfer mode:

   Primary core database is on <dbserver_ip_address>. Credentials are needed.
   ==============================================================
   
   Parameter 1 of 2
   <dbserver_ip_address> username [root]:
   
   Parameter 2 of 2
   <dbserver_ip_address> password []:****
   Re-enter the password to confirm:
   

   Supply the OS credentials for the primary core’s database server if you are using a remote database. Re-enter the password for confirmation.

8. Specify the OS credentials for the secondary Core’s database server.

   secondary Core database is on 16.77.1.191. Credentials are needed.
   =====================================================================
   
   Parameter 1 of 2
   16.77.1.191 user []: root
   
   Parameter 2 of 2
   16.77.1.191 password []: *******
   
   All values are entered.  Do you wish to continue? (Y/N) [Y]:

9. Provide the path on the secondary Core’s Oracle server where you want the DB export to be copied to.

   Specify the path on the secondary Core's oracle server where to copy the DB export
   ====================================================================
   Specify the path on the secondary Core's oracle server where to copy the DB export [/var/tmp/dbDump]:

   If you choose to install the secondary DB server with SA, copy these *.dmp files in a temporary directory on the server, example, /var/tmp/dbDump.

   If you will use an existing Oracle server for the secondary Core, copy these files in the datapump directory. To determine the datapump directory path, run the following query on the secondary Core's Oracle server:

   "select DIRECTORY_PATH from dba_directories where, DIRECTORY_NAME='DATA_PUMP_DIR';"

10. Provide the OS credentials for the secondary Core’s Infrastructure server

    Secondary Management Gateway Server is on 16.77.1.192. Credentials are needed.
    =====================================================================
    Parameter 1 of 2
    16.77.1.192 user []: root
    
    Parameter 2 of 2
    16.77.1.192 password []: *******
    
    All values are entered.  Do you wish to continue? (Y/N) [Y]: Y
    

    If you entered the same IP/hostname for both the secondary Oracle and Infrastructure servers, this step (10) will be skipped.

11. Specify the path on the secondary Core’s Infrastructure server where the installer will copy the First Core files (the tar.gz archive).

    Specify the path on the secondary Core's Management Gateway Server where to copy the truth files
    =====================================================================
    Specify the path on the secondary Core's Management Gateway Server where to copy the truth files [/var/tmp/truthFiles]:
    

    These files need to be copied on the server on which the secondary Core install will run. If you do not want to run the secondary Core install on the Infrastructure server, you will then need to manually copy these on the server on which you want to run the installer after the add_dc_to_mesh process finishes.

12. The following screen is displayed:

    Ready to perform add DC to mesh
    ===============================
    
    Actions that will be performed:
    -------------------------
      Define New Facility, Update Gateway Config
      Export Model Repository (truth)
    
    Enter one of the following directives
    (<c>ontinue, <p>revious, <h>elp, <q>uit):
    

    Type c to continue or press Enter to continue.

    A number of informational messages are displayed as the process continues.

    [INFO] ******************************************************************
    
    [INFO] Database export files *.dmp and *.log will be available on database server
    
    [INFO] under directory: /u01/app/oracle/admin/truth/dpdump/
    
    [INFO] File source_db_charset.txt is now available on this server in: [INFO] /var/opt/opsware/truth/
    [INFO] The Database export *.dmp files
    
    [INFO] (truth*_exp.dmp, aaa*_exp.dmp, gcadmin*_exp.dmp, lcrep*_exp.dmp,lcrep_tables*_exp.dmp)
    [INFO] and *.log files are now available on the Primary database server. [INFO] ******************************************************************
    

    After completion, the script places a truth.SLAVE.tar.gz file in the /var/opt/opsware/truth the directory (or the custom location you specified for the export file path (truth.dest)). If you chose to manually copy this TAR.GZ file, you will need to copy it on the server on which you plan to run the secondary Core install. Otherwise, the installer copies it automatically on the secondary Core’s Infrastructure server, in the path that you provided during the interview.

13. Continue to Phase 4.

Phase 4: Prepare the files necessary for the secondary Core installation

If you choose to manually transfer files in the interview from the previous phase, you must copy the First Core Files tar.gz archive and the secondary Core’s CDF file from the primary core’s Model Repository server on the server on which you will run the secondary Core installation. You will use this CDF file during the secondary Core install.

You must also copy the database export files (*.dmp files) from the primary core’s database server (these files can be found in the datapump directory) to the secondary Core’s Oracle database server. If you choose to install the secondary database server with SA, you will need to copy these *.dmp files in a temporary directory on the server. For example: /var/tmp/dbExport.

If you are using an existing Oracle server for the secondary Core, you must copy these files in the datapump directory. To determine the datapump directory path, run the following query on the secondary Core's Oracle server:

"select DIRECTORY_PATH from dba_directories where DIRECTORY_NAME='DATA_PUMP_DIR';".

If you choose to automatically transfer files in the interview from the previous phase, the installer copies the files in the appropriate locations. For the First Core Files tar.gz archive, this location is on the secondary Core’s Management Gateway server. If you do not plan on running the secondary Core install from the secondary Core’s Management Gateway server, you will have to manually copy the TAR.GZ file on the server on which the installer will run.

The steps in Samples of secondary Core installations (Phase 5) assume you have already mounted the SA primary distribution for the secondary Core.