Samples of secondary Core installations (Phase 5)

This section describes the following samples of secondary Core installations that can be performed in Phase 5:

• Phase 5a: Install all secondary Core components on a single host

  All secondary Core Components and SA-supplied Oracle database on the same host

• Phase 5b: Install all secondary Core Components on a single host, remote Non-SA-supplied Oracle database

  All secondary Core Components installed on a single host, remote Non-SA-supplied Oracle database on a separate host

• Phase 5c: Install the secondary Core components on multiple hosts, remote non SA-supplied database on remote database server

  secondary Core Components distributed to different hosts, non-SA-supplied database on a remote database host

Phase 5a: Install all secondary Core components on a single host

This section describes installing all SA Core Components and the SA-supplied Oracle database on a single host. If you plan to install components on different hosts, see Phase 5b: Install all secondary Core Components on a single host, remote Non-SA-supplied Oracle database.

During this phase, the First Core Model Repository content exported during Step 4 is imported into the secondary Core’s Model Repository, the cryptographic material is extracted to the appropriate location on the host and the SA secondary Core Components installed.

1. Invoke the SA Installer and specify (-c argument) the CDF copied in Phase 4:

   <distro>/opsware_installer/hpsa_install.sh -c /var/tmp/cdf.newCore4.xml

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

2. Press c to continue for the following informational messages displayed:

   Specify Hosts to Install
   ========================
   
   Currently specified hosts:
   
   <newCore4_IP_Address>
   
   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):c.
   
   

   In third-party certificate mode, make sure that all the SA Core and Satellite hosts define the hostnames of all Core or Satellite hosts at the beginning of their /etc/hosts file. Otherwise, the SA installation will fail.
   Listing these hostnames in the /etc/hosts file enables SA to generate correct certificate signing requests (CSRs) for the SA hosts.
   
   Example: to install an SA mesh with the following topology,
   16.77.42.65 (oracle_sas, truth_mm_overlay)
16.77.41.24 (infrastructure, word_uploads)
16.77.43.252 (slice, osprov)
16.77.45.21 (satellite)
   add the following lines at the beginning of the /etc/hosts file for 16.77.42.65, 16.77.41.24 and 16.77.43.252:
   16.77.42.65 hostname1.example.com hostname1
16.77.41.24 hostname2.example.com hostname2
16.77.43.252 hostname3.example.com hostname3
   The 16.77.45.21 (satellite) server does not need to be listed here because this server is part of the mesh and not part of the Core.

3. Enter the credentials for the new secondary Core host and press Enter for the following message displayed:

   Host Passwords

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

   Parameter 1 of 2
   <newCore4_IP_Address> user [root]: 
   Parameter 2 of 2
   <newCore4_IP_Address> password []:**

   The password is validated and a number of informational messages display as the script continues.

   Note This step appears only if you are running the installer on a server that is not the secondary Core server.

4. Select option 1, Typical secondary Core, and press Enter for the following message displayed:

   Install Type
   ============
   
   1. Typical secondary Core
   2. Custom secondary Core

   Enter the option number or one of  the following directives

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

5. Select option 1, Install Oracle with SA for the following message displayed:

   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): 1

   Press c to continue.

6. Select the same TLS version as on the primary core and press Enter to continue.
   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)[2]:
7. Type 1 to select Simple Interview for the following message displayed:

   Interview Type

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

   1. Simple Interview

   2. Advanced Interview

   3. Expert Interview

   Enter the option number or one of the following directives

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

   Press c to continue.

8. Provide values for the following interview parameters:

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

   Please enter the password for the opsware_admin user. This is the password used to connect to the Oracle database. If you are installing Oracle with SA the opsware_admin user will be created with this password. Make sure the password complexity matches the security guidelines in your organization. []: *************

   Parameter 2 of 7 (decrypt_passwd)

   Please enter the password for the cryptographic material [*******]:
   
   

   Parameter 3 of 7 (truth.dcNm)

   Please enter the short name of the facility where Opsware Installer is being run (no spaces) [rose2]:

   Parameter 4 of 7 (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 5 of 7 (word.store.host)

   Please enter the IP address of the NFS server for the Software Repository. For satellite installs, please enter the IP address of the Software Repository Cache. [newCore4_IP_Address]:

   Parameter 6 of 7 (word.store.path)

   Please enter the absolute path on the NFS server for Software Repository 
   [/var/opt/opsware/word]:

   Parameter 7 of 7 (bootagent.host)

   Please enter the OS Provisioning Boot Server ip or hostname [16.77.1.191]:

   Enter the option number or one of the following directives

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

   Since you specified the CDF file from the First Core Model Repository export, you can accept the defaults, enter 2 and press c to continue.

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

   Press c to continue for the following message displayed:

   Install components

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

   Oracle RDBMS for SA

   Model Repository, Additional Core

   Core Infrastructure Components

   Slice

   OS Provisioning Components

   Enter one of the following directives

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

9. The prerequisite check begins.

   If the prerequisite check completes successfully, you may still see some messages similar to the following:

   Prerequisite Checks
==============

   Results for <IP_address>:

          WARNING Insufficient swap space (18 GBytes).
                24 Gbytes is the recommended for Oracle.

        WARNING File system ‘/’ has 29447 MBytes available and 154050 is
             recommended.

        WARNING Nothing listening at db.host:db.port (ip_address).
             Note: Can be ignored if core install will be performed
             using hpsa_install script.

   Enter the option number or one of the following directives:
(<c>ontinue, <p>revious, <h>elp, <q>uit)

   The Prerequisite check identifies WARNINGs and/or FAILUREs. FAILUREs can cause a failed or incomplete installation and must be resolved before continuing the installation. WARNINGs allow you to continue the installation, however, core performance may be negatively affected if you continue without resolving them.

   If your server passes the prerequisite check, enter c and press Enter.

10. Enter the file name and path for the TAR.GZ file you copied on the local server in Phase 4 for the following message displayed:

    Enter the file path to the truth.*.tar.gz package.	

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

    Path to package file truth.SLAVE.tar.gz on the local server [/var/tmp/truthFiles/truth.SLAVE.tar.gz]:

    Press Enter. The content and cryptographic material is extracted to the appropriate directories on the host. The SA installer also performs certain post-Oracle installation tasks and sets required file permissions. When the installation completes, the Core Description File (CDF) is automatically saved.

11. Supply the path to the directory containing the database export files on the core’s Oracle database server.

    Enter the path to the directory containing the database export files.
    ==================================================================
    
    Path to the directory containing the database export files on the secondary Core's Model Repository server [/var/tmp/dbDump]:

12. In third-party certificate mode, SA installs the OCT (Opsware Cert Tool) component on the Model Repository server before the Core installation begins. The OCT component will generate the Certificate Signing Requests (CSRs) for the certificates required for the current installation configuration. After OCT install, follow the following two additional steps before the SA installation begins:
    
    1. Enter the location where you want the OCT component to generate the *.csr files.

       Select path where to generate CSRs

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

       Specify the path on the Model Repository server where SA will generate the CSR files

       [/var/tmp/csrFiles]:

       CSRs were generated in the /var/tmp/csrFiles directory on the server that hosts the Model Repository component [192.168.136.39].

       Please have them signed by your CA. You can resume the install process after all CSRs are signed.

       Make sure you copy all certificates in the same directory on the core's Model Repository server.

       You will be prompted for the path to this directory in the next step of the install process.

       Submit these files to your CA for signing and place the issued certificates in a folder of your choice.
       After generating the cryptographic material, SA places the CSRs created for that instance in a subfolder named by date. For example: csr_2017-05-02.08:21:05 csr_2017-05-02.08:22:10. Any new CSRs are placed in the dedicated folder that you provide during the installer interview.
       When providing the third-party certificates, make sure to follow the certificate format and naming requirements described in the SA certificates format.
       

    2. Provide the location where you have placed the custom certificates signed by your CA. The installer checks that the path is correct and that all required certificates are available.
       Enter the path to the directory containing the custom certificates.
===================================================================

       Path to the directory containing the certificates. [/var/tmp/certificateFiles]:
       SA now generates a new cryptographic material containing your signed certificates. The cryptographic material is then copied it on all hosts in the mesh.

The script displays process messages and a completion message. During this process, the Installer registers the new secondary Core’s Facility with the First Core’s Model Repository, automatically generating a unique ID for the Facility.

Phase 5b: Install all secondary Core Components on a single host, remote Non-SA-supplied Oracle database

Use the following procedure to install all SA secondary Core Components on a single server. The Non-SA-supplied Oracle database is installed on a different host.

During this phase, the First Core Model Repository content exported during Step 4 is imported into the secondary Core’s Model Repository, the cryptographic material is extracted to the appropriate location on the host and the SA secondary Core Components installed.

1. Invoke the SA Installer specifying (-c argument) the CDF copied in Phase 4:

   <distro>/opsware_installer/hpsa_install.sh -c /var/tmp/cdf.newCore4.xml , where <distro> is the full path to the installation media.

   You see messages displayed on screen as the SA Installer loads the required files.

2. The following message is displayed.

   Specify Hosts to Install

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

   Currently specified hosts:

   <newCore4_IP_Address>

   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): c

   Press c to continue.

   In third-party certificate mode, make sure that all the SA Core and Satellite hosts define the hostnames of all Core or Satellite hosts at the beginning of their /etc/hosts file. Otherwise, the SA installation will fail.
   Listing these hostnames in the /etc/hosts file enables SA to generate correct certificate signing requests (CSRs) for the SA hosts.
   
   Example: to install an SA mesh with the following topology,
   16.77.42.65 (oracle_sas, truth_mm_overlay)
16.77.41.24 (infrastructure, word_uploads)
16.77.43.252 (slice, osprov)
16.77.45.21 (satellite)
   add the following lines at the beginning of the /etc/hosts file for 16.77.42.65, 16.77.41.24 and 16.77.43.252:
   16.77.42.65 hostname1.example.com hostname1
16.77.41.24 hostname2.example.com hostname2
16.77.43.252 hostname3.example.com hostname3
   The 16.77.45.21 (satellite) server does not need to be listed here because this server is part of the mesh and not part of the Core.
3. Provide the credentials for the secondary Core host:

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

   Parameter 1 of 2
<IP_address> user [root]:
Parameter 2 of 2
<IP_address> password []: **

   You are prompted for the user and password for the specified host. After you provide all required credentials, the message appears:

   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.

   Note This step appears only if you are running the installer on a server that is not the secondary Core server.

4. After the SA Installation media is mounted for all servers, the following menu displays:

   Install Type

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

   1. Typical secondary Core

   2. Custom secondary Core

   Enter the option number or one of the following directives

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

   Select Option 1, Typical secondary Core and press c to continue.

5. Select 2, Use existing Oracle database for the following screen displayed:

   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

   Press Enter to continue.

6. Select the same TLS version as on the primary core and press Enter to continue.
   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)[2]:
   

7. Select the Interview Type from the following message displayed:

   Interview Type

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

   1. Simple Interview

   2. Advanced Interview

   3. Expert Interview

   Enter the option number or one of the following directives

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

   
   Type 1 for the Simple Interview and press Enter to continue.

8. Provide values for the following interview parameters:

   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 12 (truth.oaPwd)
   Please enter the password for the opsware_admin user. This is the password used to connect to the Oracle database. If you are installing Oracle with SA the opsware_admin user will be created with this password. Make sure the password complexity matches the security guidelines in your organization. []: ************* *************
   Re-enter the password to confirm: *************
   
   Parameter 2 of 12 (decrypt_passwd)
   Please enter the password for the cryptographic material [*************]:

   Parameter 3 of 12 (truth.dcNm)
   Please enter the short name of the facility where Opsware Installer is being run (no spaces) [SLAVE]:
   
   Parameter 4 of 12 (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 5 of 12 (db.host)
   Please enter the hostname/IPaddress of the Oracle database server. [192.168.136.39]:
   
   Parameter 6 of 12 (truth.servicename)
   Please enter the service name of the Model Repository instance in the facility where Opsware Installer is being run [truth.SLAVE]:
   
   Parameter 7 of 12 (db.sid)
   Please enter the SID of the Oracle instance containing the Model Repository [truth]:
   
   Parameter 8 of 12 (db.port)
   Please enter the port on which the database is listening. [1521]:
   
   Parameter 9 of 12 (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]: 
   
   Parameter 10 of 12 (word.store.host)
   Please enter the IP address of the NFS server for the Software Repository. For satellite installs, please enter the IP address of the Software Repository Cache. [192.168.136.38]:
   
   Parameter 11 of 12 (word.store.path)
   Please enter the absolute path on the NFS server for Software Repository [/var/opt/opsware/word]:
   
   Parameter 12 of 12 (bootagent.host)
   Please enter the OS Provisioning Boot Server ip or hostname [192.168.136.40]:
   

   Enter the option number or one of the following directives

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

   Since you specified the CDF file from the First Core Model Repository export, you can accept the defaults and press c to continue.

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

   When you have supplied values for all parameters, the following message displays:

   All parameters have values. Do you wish to finish the interview? (y/n):

   Enter y and press Enter to continue. If you enter n, you are presented with each parameter again with the value you entered as the default. You can then change the value or accept the default. If you need to exit the installation, press Ctrl-C.

   1. A screen similar to the following displays:

      Install components

      ==================
Model Repository, Additional
Core Core Infrastructure
Components Slice
OS Provisioning Components

      Enter one of the following directives
(<c>ontinue, <p>revious, <h>elp, <q>uit): c

      Enter c and press Enter to begin the prerequisite checks.

      If the server that will host your Slice Component bundle has more than one network interface installed, SA will detect the presence of two NICs and display a screen similar to the following:
      
      
      Slice Network Interface Configuration
=====================================

Parameter 1 of 2 (Slice: 192.168.136.38)

Please select the interface to use for 192.168.136.38

1) eth2 -- 192.168.136.55
2) eth1 -- 192.168.136.77
3) eth0 -- 192.168.136.38 (default)
[3]:

Select the appropriate network interface for each host by entering the associated number from the list.
      
      When you have configured all interfaces, you see the message:
      
      All values are entered. Do you wish to continue? (Y/N) [Y]:

      Enter y and press Enter to continue. You can edit the list again by pressing n and Enter.
9. The prerequisite check begins.
   Before SA begins the installation, it performs prerequisite checks that validate that the host on which you are installing SA meets the minimum requirements for the installation (see SA Installer Prerequisite Checker). The check ensures that required packages are installed, required environment variables are set, sufficient disk space is available, and so on.
   
   If your host fails the prerequisite check, the installation will fail with an error message that describes the problem. If your host fails the prerequisite check, correct the problem and retry the installation or, if you are unable to resolve the problem, contact HPE Support.
10. If the prerequisite check completes successfully, you may still see some messages similar to the following:

    Prerequisite Checks
==============

    Results for <IP_address>:

           WARNING Insufficient swap space (18 GBytes).
                24 Gbytes is the recommended for Oracle.

         WARNING File system ‘/’ has 29447 MBytes available and 154050 is
             recommended.

         WARNING Nothing listening at db.host:db.port (ip_address).
             Note: Can be ignored if core install will be performed
             using hpsa_install script.

    Enter the option number or one of the following directives:
(<c>ontinue, <p>revious, <h>elp, <q>uit)

    The Prerequisite check identifies WARNINGs and/or FAILUREs. FAILUREs can cause a failed or incomplete installation and must be resolved before continuing the installation. WARNINGs allow you to continue the installation, however, core performance may be negatively affected if you continue without resolving them.

    If your server passes the prerequisite check, enter c and press Enter to begin the installation.

11. Enter the file name and path for the TAR.GZ file you copied on the local server in Phase 4 for the following message displayed:

    Enter the file path to the truth.*.tar.gz package.

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

    Path to package file truth.SLAVE.tar.gz on the local server [/var/tmp/truthFiles/truth.SLAVE.tar.gz]

    Press Enter. The content and cryptographic material is extracted to the appropriate directories on the host. The SA installer also performs certain post-Oracle installation tasks and sets required file permissions. After the extraction complete, the SA Installer begins the secondary Core installation.

12. A confirmation screen is displayed, similar to the one below. Make sure that all the presented requirements are met.

    Make sure you copied the database dump files on the secondary Core's Oracle server.
Please check that the files are in the following directory:
/u01/app/oracle/admin/truth/dpdump/
Please also make sure that the oracle user has read permissions for the database dump files and write permissions on the folder.
Enter one of the following directives
(<c>ontinue, <p>revious, <h>elp, <q>uit): c

13. You see many messages displayed as the installation progresses, unless the installation fails, these messages are purely informational. The installation can take several hours based on the performance of your server. When the installation completes, the Core Description File (CDF) is automatically saved.
14. In third-party certificate mode, SA installs the OCT (Opsware Cert Tool) component on the Model Repository server before the Core installation begins. The OCT component will generate the Certificate Signing Requests (CSRs) for the certificates required for the current installation configuration. After OCT install, follow the following two additional steps before the SA installation begins:
    
    1. Enter the location where you want the OCT component to generate the *.csr files.

       Select path where to generate CSRs

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

       Specify the path on the Model Repository server where SA will generate the CSR files

       [/var/tmp/csrFiles]:

       CSRs were generated in the /var/tmp/csrFiles directory on the server that hosts the Model Repository component [192.168.136.39].

       Please have them signed by your CA. You can resume the install process after all CSRs are signed.

       Make sure you copy all certificates in the same directory on the core's Model Repository server.

       You will be prompted for the path to this directory in the next step of the install process.

       Submit these files to your CA for signing and place the issued certificates in a folder of your choice.
       After generating the cryptographic material, SA places the CSRs created for that instance in a subfolder named by date. For example: csr_2017-05-02.08:21:05 csr_2017-05-02.08:22:10. Any new CSRs are placed in the dedicated folder that you provide during the installer interview.
       When providing the third-party certificates, make sure to follow the certificate format and naming requirements described in the SA certificates format.
       

    2. Provide the location where you have placed the custom certificates signed by your CA. The installer checks that the path is correct and that all required certificates are available.
       Enter the path to the directory containing the custom certificates.
===================================================================

       Path to the directory containing the certificates. [/var/tmp/certificateFiles]:
       SA now generates a new cryptographic material containing your signed certificates. The cryptographic material is then copied it on all hosts in the mesh.

Upon completion, a message displays indicating successful installation.

Phase 5c: Install the secondary Core components on multiple hosts, remote non SA-supplied database on remote database server

Use the following procedure to install all SA Core Components on different host servers, for example, Slice Component bundle and/or Model Repository on different servers than the infrastructure components. It also uses an existing remote non-SA-supplied Oracle database. For information about configuring a non-SA-supplied Oracle database for use with SA, see Non-SA-Supplied Oracle Software and Database Setup.

During this phase, the First Core Model Repository content exported during Step 4 is imported into the secondary Core’s Model Repository, the cryptographic material is extracted to the appropriate location on the host and the SA secondary Core Components installed.

1. Invoke the SA Installer specifying the CDF (-c argument) copied in Phase 4:

   <distro>/opsware_installer/hpsa_install.sh -c /var/tmp/cdf.newCore4.xml

   where <distro> is the full path to the installation media.

   You see messages displayed on screen as the SA Installer loads the required files.

   For this example installation, we’ll use six remote servers for the core component installation. You will, of course, modify this for your particular system requirements. Components will be installed as follows:

Core component layout

Server	Core Component to be Installed
192.168.136.36	Model Repository
192.168.136.39	Multimaster Infrastructure Components
192.168.136.39	Software Repository Storage and Content
192.168.136.38, 192.168.136.41, 192.168.136.42	Slice
192.168.136.40	SA Provisioning Media Server
192.168.136.40	SA Provisioning Boot Server, Slice version

2. After a few informational messages display, a screen similar to the following displays:

   Specify Hosts to Install

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

   Currently specified hosts:

   <newCore4_IP_Address>

   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):1

   Enter 1 and press Enter to continue.

3. You are asked to specify the number of hosts that will be involved in the installation:

   Enter number of hosts to add:

   Enter the appropriate number. For this example, we use six hosts:

   Enter number of hosts to add: 5

4. Enter the hostname or IP address of the first server that will host an SA Core Component(s):

   Adding Hosts
   ============

   Parameter 1 of 5
   Hostname/IP []:

    Press Enter.

   Do the same for all remaining servers. You see this message:

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

   Enter Y to continue.

   For this example, we add the hosts:

   192.168.136.36

   192.168.136.38

   192.168.136.39

   192.168.136.40

   192.168.136.41

   192.168.136.42

   A screen similar to the following displays:

   Specify Hosts to Install
========================

   Currently specified hosts:

          192.168.136.36
        192.168.136.38
        192.168.136.39
        192.168.136.40
        192.168.136.41
        192.168.136.42

   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):
   

   In third-party certificate mode, make sure that all the SA Core and Satellite hosts define the hostnames of all Core or Satellite hosts at the beginning of their /etc/hosts file. Otherwise, the SA installation will fail.
   Listing these hostnames in the /etc/hosts file enables SA to generate correct certificate signing requests (CSRs) for the SA hosts.
   
   Example: to install an SA mesh with the following topology,
   16.77.42.65 (oracle_sas, truth_mm_overlay)
16.77.41.24 (infrastructure, word_uploads)
16.77.43.252 (slice, osprov)
16.77.45.21 (satellite)
   add the following lines at the beginning of the /etc/hosts file for 16.77.42.65, 16.77.41.24 and 16.77.43.252:
   16.77.42.65 hostname1.example.com hostname1
16.77.41.24 hostname2.example.com hostname2
16.77.43.252 hostname3.example.com hostname3
   The 16.77.45.21 (satellite) server does not need to be listed here because this server is part of the mesh and not part of the Core.
5. At this point you can press 2 to delete a host or 1 to add/edit a hostname/IP address. When you choose 1 for an existing list of hosts, you see this prompt:

   Enter number of hosts to add (or enter "0" to edit the list):

   When you are satisfied with the entries, type C and press Enter to continue.

6. Provide the credentials for each host in the list shown in Step 4:

   Host Passwords
   ==============
   Parameter 1 of 10
   <IP_address> user [root]: 
   Parameter 2 of 10
   <IP_address> password []: *******
   

   You are prompted for the user ID and password for each specified host. Type the password (which will be obfuscated) and press Enter. 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.

7. After the host preparation completes, the following menu displays:

   Install Type

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

   1. Typical secondary Core

   2. Custom secondary Core

   Enter the option number or one of the following directives

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

   Select Option 1, Typical secondary Core and press Enter to continue.

8. Select 2, Use existing Oracle database for the Oracle installation type:

   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

   Press Enter to continue.

9. Enter the associated number of the following component:

   Host/Component Layout

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

   1. Model Repository, Additional Core

   2. Core Infrastructure Components

   3. Slice

   4. OS Provisioning Components

   Enter the number of the component or one of the following directives

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

   You use this menu to assign the host on which the SA Core Components are to be installed.

   Press the associated number for the component (for example, 1 for the Model Repository). You will see a menu that lists the available hosts and the name of the component to be assigned. It will look similar to this:

   Host Assignment for Model Repository, Additional Core

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

   1. 192.168.136.36
   2. 192.168.136.38
   3. 192.168.136.39
   4. 192.168.136.40
   5. 192.168.136.41
   6. 192.168.136.42

   Enter the number of the host or one of the following directives

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

10. Type the number associated with the hostname/IP address of the server you want to host the current SA Core Component and press enter.

    Selecting 1 assigns the Model Repository to the IP address, 192.168.136.36. You will be returned to the Host Component Layout menu. Note that the Model Repository displays the hostname/IP address it was assigned to:

    Host/Component Layout

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

    1. Model Repository, Additional Core   :192.168.136.36

    2. Core Infrastructure Components      :192.168.136.39

    3. Slice                               :192.168.136.38, 192.168.136.41,                                        :192.168.136.42

    4. OS Provisioning Components          :192.168.136.40

    Enter the number of the component or one of the following directives

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

    Repeat this step for each component listed on the Host Component Layout menu.

    You can assign multiple Slice Component bundles to the same host or to different hosts (you must assign at least one):

    Host Assignment for Slice

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

    1 ( ) 192.168.136.36

    2 ( ) 192.168.136.39

    Enter the number of the host or one of the following directives

    (<c>ontinue, <p>revious, <a>ll, <u>nselect all, <h>elp, <q>uit):

    After you have assigned a Slice Component bundle to a host, an asterisk is displayed next to the hostname/IP address:

    2 (*) 192.168.136.39

    After you have assigned a hostname/IP address for all components, enter c at the prompt and press Enter to continue.

11. Select the same TLS version as on the primary core and press Enter to continue.
    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)[2]:
    

12. Select the Interview Type from the following message displayed:

    Interview Type

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

    1. Simple Interview

    2. Advanced Interview

    3. Expert Interview

    Enter the option number or one of the following directives

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

    Type 1 for the Simple Interview and press Enter to continue.

13. Provide values for the following interview parameters:

    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 12 (truth.oaPwd)

    Please enter the password for the opsware_admin user. This is the password used to connect to the Oracle database. If you are installing Oracle with SA the opsware_admin user will be created with this password. Make sure the password complexity matches the security guidelines in your organization. []: *************

    Parameter 2 of 12 (decrypt_passwd)

    Please enter the password for the cryptographic material [*******]:

    Parameter 3 of 12 (truth.dcNm)

    Please enter the short name of the facility where Opsware Installer is being run (no spaces) [SLAVE]:

    Parameter 4 of 12 (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 5 of 12 (db.host)

    Please enter the hostname/IPaddress of the Oracle database server. [192.168.136.37]:

     

    Parameter 6 of 12 (truth.servicename)

    Please enter the service name of the Model Repository instance in the facility where Opsware Installer is being run [truth.SLAVE]:

    Parameter 7 of 12 (db.sid)

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

    Parameter 8 of 12 (db.port)

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

    Parameter 9 of 12 (db.orahome)

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

    Parameter 10 of 12 (word.store.host)

    Please enter the IP address of the NFS server for the Software Repository. For satellite installs, please enter the IP address of the Software Repository Cache. [192.168.136.39]:

    Parameter 11 of 12 (word.store.path)

    Please enter the absolute path on the NFS server for Software Repository 
    [/var/opt/opsware/word]:

    Parameter 12 of 12 (bootagent.host)

    Please enter the OS Provisioning Boot Server ip or hostname [192.168.136.40]:

     

    Enter the option number or one of the following directives

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

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

    Since you provided the CDF you created when you installed the Primary SA Core, SA uses the default core configuration parameter values from that CDF as the default for this interview.

    When you have supplied all required values, you see this prompt:

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

    Enter Y and press Enter to continue.

    A screen similar to the following displays:

    Install components

    ==================
Model Repository, First Core : 192.168.136.36
Multimaster Infrastructure Components : 192.168.136.39
Software Repository Storage : 192.168.136.39
Slice : 192.168.136.38, 192.168.136.41, 192.168.136.42
OS Provisioning Media Server : 192.168.136.40
OS Provisioning Boot Server, Slice version : 192.168.136.40
Software Repository - Content (install once per mesh): 192.168.136.39

    Enter one of the following directives
(<c>ontinue, <p>revious, <h>elp, <q>uit): c

    Type c and press Enter to begin the prerequisite checks.

14. The prerequisite check begins.

15. If the prerequisite check completes successfully, you may still see some messages similar to the following:

    Prerequisite Checks
==============

    Results for <IP_address>:

           WARNING Insufficient swap space (18 GBytes).
                24 Gbytes is the recommended for Oracle.

         WARNING File system ‘/’ has 29447 MBytes available and 154050 is
             recommended.

         WARNING Nothing listening at db.host:db.port (ip_address).
             Note: Can be ignored if core install will be performed
             using hpsa_install script.

    Enter the option number or one of the following directives:
(<c>ontinue, <p>revious, <h>elp, <q>uit)

    The Prerequisite check identifies WARNINGs and/or FAILUREs. FAILUREs can cause a failed or incomplete installation and must be resolved before continuing the installation. WARNINGs allow you to continue the installation, however, core performance may be negatively affected if you continue without resolving them.

    If your server passes the prerequisite check, enter c and press Enter to begin the installation.

16. Enter the file name and path for the TAR.GZ file you copied on the local server in Phase 4 for the following message displayed:

    
    Enter the file path to the truth.*.tar.gz package.

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

    Path to package file truth.SLAVE.tar.gz on the local server [/var/tmp/truthFiles/truth.SLAVE.tar.gz]:

     

    Enter the file name and path for the TAR.GZ file you copied on the local server in Phase 4 and press Enter. The content and cryptographic material is extracted to the appropriate directories on the host. The SA installer also performs certain post-Oracle installation tasks and sets required file permissions. After the extraction complete, the SA Installer begins the secondary Core installation.

17. A confirmation screen is displayed, similar to the one below. Make sure that all the presented requirements are met.
    Make sure you copied the database dump files on the secondary Core's Oracle server.
Please check that the files are in the following directory:
/u01/app/oracle/admin/truth/dpdump/
Please also make sure that the oracle user has read permissions for the database dump files and write permissions on the folder.
Enter one of the following directives
(<c>ontinue, <p>revious, <h>elp, <q>uit): c
18. In third-party certificate mode, SA installs the OCT (Opsware Cert Tool) component on the Model Repository server before the Core installation begins. The OCT component will generate the Certificate Signing Requests (CSRs) for the certificates required for the current installation configuration. After the OCT install, follow the following two additional steps before the SA installation begins:
    
    1. Enter the location where you want the OCT component to generate the *.csr files.

       Select path where to generate CSRs

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

       Specify the path on the Model Repository server where SA will generate the CSR files

       [/var/tmp/csrFiles]:

       CSRs were generated in the /var/tmp/csrFiles directory on the server that hosts the Model Repository component [192.168.136.39].

       Please have them signed by your CA. You can resume the install process after all CSRs are signed.

       Make sure you copy all certificates in the same directory on the core's Model Repository server.

       You will be prompted for the path to this directory in the next step of the install process.

       Submit these files to your CA for signing and place the issued certificates in a folder of your choice.
       After generating the cryptographic material, SA places the CSRs created for that instance in a subfolder named by date. For example: csr_2017-05-02.08:21:05 csr_2017-05-02.08:22:10. Any new CSRs are placed in the dedicated folder that you provide during the installer interview.
       When providing the third-party certificates, make sure to follow the certificate format and naming requirements described in the SA certificates format.
       

    2. Provide the location where you have placed the custom certificates signed by your CA. The installer checks that the path is correct and that all required certificates are available.
       Enter the path to the directory containing the custom certificates.
===================================================================

       Path to the directory containing the certificates. [/var/tmp/certificateFiles]:
       SA now generates a new cryptographic material containing your signed certificates. The cryptographic material is then copied it on all hosts in the mesh.

You see many messages displayed as the installation progresses, unless the installation fails, these messages are purely informational. The installation can take several hours based on the performance of your server. When the installation completes, the Core Description File (CDF) is automatically saved. Upon completion, a message displays indicating successful installation.

Secondary Core post-installation tasks

After you have added a new core to a Multimaster Mesh, you must perform the tasks described in this section.

Associate customers with the new facility

Associate the appropriate customers with each new Facility so that servers managed at that Facility are associated with the correct customer accounts. For more information, see the "Customer Account Administration" section in the SA 10.60Administer section.

Update permissions for the new facility

After you have added a new Facility to your Multimaster Mesh, your SA users will not yet have the required permissions to access the new Facility. You must assign the required permissions to the user groups. For more information, see the "User Group and Setup" section in the SA 10.60Administer section.

Verify multimaster transaction traffic

To verify Multimaster transaction traffic with the target facility:

1. Log in to the SA Client as any user who belongs to the Opsware System Administrators group.
2. From the Navigation panel, expand Multimaster Tools under Administration.
3. In the State View Window, note the status box for each facility's transaction.

   A transaction is a unit of change to a Model Repository database that consists of one or more updates to rows and has a globally unique transaction ID. If the number of Not Received transactions is not continually growing, the new SA Core is integrated into the Multimaster Mesh.

4. Click Refresh to refresh the cached data until all transactions display green.

For more information, see the Multimaster Mesh Administration section in Administer.