SA Core with a Remote Model Repository and Remote SA-supplied Database

This section describes installing SA components on one host and the Model Repository and an SA-supplied Oracle database on a second host. You can use the right-hand column to indicate that a phase is completed:

Core installation phases

Phase	Complete
Phase 1: Preparing to install the SA Core
Phase 2: Run the SA installer
Phase 3: Specify the Core Component hosts
Phase 4: Select the installation type
Phase 5: Select the interview type and provide SA parameter values
Phase 6: Install the SA components

Phase 1: Preparing to install the SA Core

1. You will need the following media: SA Product Software (primary), Agent and Utilities media and the Oracle_SA installation media.
2. The servers on which the SA Core Components and the Oracle Database are to be installed must be running a supported Red Hat Enterprise Linux or SUSE Enterprise Server Linux operating system. See the SA 10.50 Support and Compatibility Matrix.
3. On the server where you will install the SA, mount the Product Software (primary), Agent and Utilities media and the Oracle_SA media, or NFS-mount a directory that contains a copy of the media:
   1. Open a terminal window and log in as a user with root privileges.
   2. Change to the root directory:

      cd /

Phase 2: Run the SA installer

On the server on which you plan to install SA and the Oracle database, run the install script:

/<distro>/opsware_installer/hpsa_install.sh

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

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

Logs for the installation are automatically stored. See Installer logs.

Phase 3: Specify the Core Component hosts

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

Core component layout

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

1. You see this screen:

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

   Currently specified hosts:

   192.168.136.36 (this is the IP address of the host on which the installer is invoked)

   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 number of hosts to add:

   At this point, the host on which the install script was invoked should be listed by default.

2. 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 two hosts, the default host and one we add:

   Enter number of hosts to add: 1

3. The following screen appears:

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

   Parameter 1 of 1
   Hostname/IP []:

   Enter the hostname or IP address of the server that will host the Model Repository and Oracle database and press Enter.

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

   • 192.168.136.39
4. A screen similar to the following appears:

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

   Currently specified hosts:

           192.168.136.36
        192.168.136.39

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

   Note that 192.168.136.39 is now listed.

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, press C to continue.

6. You are asked to provide the root passwords for each added host:

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

   Parameter 1 of 1

   192.168.136.39 password []:

   Type the password (which is obfuscated) and press Enter. SA validates the password. After you provide all required passwords, you see the message:

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

   Enter Y and press Enter to continue.

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

Phase 4: Select the installation type

1. After the SA Installation media is mounted for all servers, the following menu appears:

   Install Type
============
1. Typical Primary Core
2. Custom Primary Core
3. Typical Secondary Core
4. Custom Secondary Core

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

   Enter 2 (Custom Primary Core) and Enter to continue.

2. The following menu appears:

   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)

   Enter 1 (Install Oracle with SA) and Enter to continue.

3. The following is displayed:

   Host/Component Layout
=====================

   1. Oracle Database and Model Repository, First Core
2. Multimaster Infrastructure Components
3. Software Repository Storage and Content
4. Slice
5. OS Provisioning Media Server
6. OS Provisioning Boot Server, Slice version

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

   Note that no host (IP address) is associated with the components.

   You now must associate the core components with the servers (IP addresses) they are to be installed on. To do so, you enter the component’s number at the prompt. For example, enter 1 to add the host for the Model Repository, enter 2 for the Multimaster Infrastructure Components, and so on.

4. Screens similar to the following display as you assign component hosts:

   Host Assignment for Model Repository, First Core
===========================================================

   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, <h>elp, <q>uit): 1

   Enter 1 to specify 192.168.136.36 for the Model Repository and database. You are returned to the Host Component Layout screen and can select the next component and assign its host. Do the same for all remaining components.

   When you have assigned hosts for all components, you see a screen similar to this:

   Host/Component Layout
=====================

   1. Oracle Database and Model Repository [192.168.136.36]
2. Multimaster Infrastructure Components [192.168.136.39]
3. Software Repository Storage and Content [192.168.136.39]
4. Slice [192.168.136.39]
5. OS Provisioning Media Server [192.168.136.39]
6. OS Provisioning Boot Server, Slice version [192.168.136.39]

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

   Note that the Slice Component bundle (option 4) can have multiple host IP addresses as the Slice components can have multiple instances to improve performance.

   Enter c and press Enter to continue.

Phase 5: Select the interview type and provide SA parameter values

1. The following menu appears:

   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)

   Enter 1 (Simple Interview) and Enter to continue.

2. You are prompted to supply values for the following SA parameters:

   • opsware_admin user (truth.oaPwd): an SA administrator password (the default username is admin).
   • crypto.hash_algorithm: The hashing algorithm for SA cryptographic module
   • crypto.key_length: the key length [2048 or 4096] used for hashing algorithm of SA cryptographic module.

• decrypt_passwd: A password for the SA cryptographic material.

• truth.dcNm: A name for your SA facility.
• word.store.host: The IP address of the NFS server for the Software Repository.
• word.store.path: The absolute path on the NFS server for Software Repository
  (/var/opt/opsware/word)

  For more information about these parameters, see the SA Core parameter reference.

  You see these prompts (the prompts display one at a time; after you provide a value and press enter you see a message, Validating..., and if the value is acceptable, the next prompt displays:

  Interview Parameters
====================

  Navigation Keys:
Use <Ctrl>P to go to the previous parameter.
Use <Ctrl>N to go to the next parameter.
Use >Tab> to view help on the current parameter.
Use <Ctrl>C to interrupt the interview.

  Parameter 1 of 9 (truth.oaPwd)
Please enter the password for the opsware_admin user. This is the password used to connect to the Oracle database.: []

  Parameter 2 of 9 (fips.mode)
  Do you want SA to be in FIPS mode? (y/n) [n]: n

  Parameter 3 of 9: (crypto.hash_algorithm)
  Please enter the hashing algorithm for SA cryptographic module. Press TAB for a list of possible values. [SHA256]:

  Parameter 4 of 9: (crypto.key_length)
  Please enter the key length [2048 or 4096] used for hashing algorithm of SA cryptographic module. [2048]: 

  Parameter 5 of 9 (decrypt_passwd)
Please enter the password for the cryptographic material.: []

  Note: You will see this prompt only if you are using your own crypto file and not allowing SA to automatically generate the crypto file.

  Parameter 6 of 9 (truth.dcNm)
Please enter the short name of the facility where the Opsware Installer is being run (no spaces).: []

  Parameter 7 of 9 (windows_util_loc)
  Please enter the directory path containing the Microsoft patching utilities. Press Ctrl-I for a list of required files or enter “none” if you do not wish to upload the utilities at this time (none).: []

  Parameter 8 of 9 (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 9 of 9 (word.store.path)
  Please enter the absolute path on the NFS server for Software Repository 
  [/var/opt/opsware/word]: 

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

  Note: Uploading the Microsoft patching utilities is optional, however, if you expect to have Windows-based managed servers, you should follow the instructions for obtaining these files as described in System requirements for installation .

  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.

4. You are now ready to begin the database and SA Component installation.

Phase 6: Install the SA components

1. A screen similar to the following appears:

   Install components

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

   Oracle RDBMS for SA : 192.168.136.36
Model Repository, First Core : 192.168.136.36
Core Infrastructure Components : 192.168.136.39
Slice : 192.168.136.39
OS Provisioning Components : 192.168.136.39
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

   Enter c and press Enter to begin the prerequisite checks.

   Note: 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]:

Parameter 2 of 2 (Slice: 192.168.136.41)

Please select the interface to use for 192.168.136.41

1) eth0 -- 192.168.136.41 (default)
2) eth2 -- 192.168.136.54
3) eth1 -- 192.168.136.76
[1]:

   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.

2. The prerequisite check begins.

3. 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.

4. 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, you the Core Description File (CDF) is automatically saved.

   Upon completion, a message displays indicating successful installation.

Post-installation tasks

You must now complete the tasks described in SA Core post-installation tasks