Install > Preinstallation tasks > Preparing the environment > Configuration of additional components

Configuration of additional components

This section provides information about configuring the following additional components:

FIPS compliance options

HPE Server Automation (SA) complies with the Federal Information Processing Standards publication 140-2, a security standard that enables government entities to procure equipment that uses validated cryptographic modules. During installation you can choose to enable FIPS by setting the fips.mode parameter to enabled.

You will be prompted during the installation to specify whether FIPS should be enabled or not.

Under normal security conditions, HPE recommends using SHA256 with a key length of 2048. Higher security requirements could require FIPS with a key length of 4096 or other hash functions from SHA-2 family. Note that use of FIPS or other hash functions from SHA-2 family can impact core performance. Contact your Security Administrator for more information.

See FIPS 140-2 compliance.

Note In FIPS mode, sufficient entropy stemming from the character device /dev/random must be available on the core servers, to ensure proper startup and functionality of SA components.

Enabling IPv6 networking

To enable IPv6 networking, run the enable_ipv6.sh script as a post-installation or upgrade step. This enables IPv6 on the SA core and satellite gateways and OS provisioning components on SA 10.2 or later releases. The script is available on all infrastructure, slices, boot servers, and satellite systems. For more information, see Enabling IPv6 networking post installation.

For further information about IPv6 and the enable_ipv6.sh script, see “SA Remote Communications Administration” in the SA 10.51 Administer section.

For information about running the enable_ipv6.sh script post-installation, see Enabling IPv6 networking post installation.

Cryptographic material options

SA cryptographic material enables encrypted communications between SA Core Components. SA installs its own cryptographic material. Simply allow SA to generate its own material when prompted during installation.

As of this release, if you want to use cryptographic material from a previous SA installation (SA 10.0 or earlier), you can no longer simply copy the existing crypto file due to enhancements to the way SA handles encryption.

You can, however, copy the crypto file from an existing SA 10.1 or later SA Core. You can do so by copying the crypto file /var/opt/opsware/crypto/cadb/realm/opsware-crypto.db.e and the /etc/opt/opsware/crypto/security.conf file to the same locations on the server that will host the SA Core or First Core (Multimaster Mesh) before beginning the installation. During installation, do not have the installer generate cryptographic material and when you are prompted, provide the password for this cryptographic material.

Mounting the SA ISO media

The SA installation/upgrade media is organized into separate categories in the downloaded file structure, for example:

  • oracle_sas (HPE Server Automation Database)

    The media used to install the Oracle database

  • primary (HPE Server Automation Product Software)

    The media used to install the SA Core Components

  • upload (HPE Server Automation Agents and Utilities)

    The media used to upload and install SA Core content and tools

  • sat_base (HPE Server Automation Satellite Base)

    The media used to install the SA Satellite components, it does not include the OS Provisioning components and is therefore smaller and can be helpful when you are transferring the media over the network.

  • sat_osprov (HPE Server Automation Satellite Base including OS Provisioning)

    The media used to install the SA Satellite and the Satellite’s OS Provisioning components.

Initial invocation of the hpsa* scripts for core install/upgrade for SA Cores must be from the primary media, Satellites from the sat_base or sat_osprov media.

The SA Installer requires that the media directory structure be maintained, for example:

<mountpoint>/<user_defined_prefix>-<media_name>/disk001/opsware_installer/hpsa*.sh

where <user_defined_prefix>-<media_name> is, for example, hpsa-primary, hpsa-sat_base, etc. HPE recommends the prefix hpsa and the media category identifiers shown above (sat_base,primary, etc.). The hyphen after hpsa is required even if you do not append a prefix.

SA is delivered as media that can be copied to a local disk or mounted as an NFS mount point. You must mount all media on a host where install script will be invoked. If media is mounted as follows the SA installer will auto mount it on local or remote core host(s) as needed. For example:

oracle_sas

mount oracle_sas.iso /<mountpoint>/hpsa-oracle_sas/

primary

mount primary.iso /<mountpoint>/hpsa-primary/

upload

mount upload.iso /<mountpoint>/hpsa-upload/

sat_base

mount upload.iso /<mountpoint>/hpsa-sat_base/

sat_osprov

mount upload.iso /<mountpoint>/hpsa-sat_osprov/

Where <mountpoint> is a media mount location of your choosing, for example /mnt.

If you use a different directory structure, the SA Installer will prompt you for the path each time it needs to access the media.

Send Help Center feedback