Satellite installation requirements

Before you install a Satellite, verify that you meet the following requirements:

• You adhere to the requirements in SA Provisioning: DHCP proxying. This is only required if you plan to install the SA Provisioning Boot Server and Media Server components in the Satellite.
• The SA Core that will provide core component services to the Satellite are running and accessible during Satellite installation.
• The Satellite server has network connectivity to that Core’s Management Gateway.
• You are a member of the System Administrators group and member of all user group with Manage Gateway permissions.
• You have root access to the parent Core’s Model Repository host from where you can copy the files required for installing the Satellite:
  • if working in self-signed certification mode, copy the cryptographic material and the security configuration file.
  • if working in third-party certificate mode, use the prep_satellite.sh script to create a .*tar file with all the files required for the installation.
  Your selected certificate mode applies to all the SA cores and satellites in the SA mesh. This means that you cannot target only specific cores forthird-party certification and keep others under SA certification.
  For information on the SA certificate modes, see Cryptographic material options.
  

• The Satellite server uses UTC, as described in Check the Core host(s) time and locale requirements. The Satellite server’s system time is synchronized with the Primary Core host.
• The network storage configuration allows root Write access over NFS to the directories in which the Software Repository Cache will be installed. This is required if you plan to locate the Satellite’s Software Repository Cache on a network storage device.
• Before running the Satellite Installer, ensure you have uninstalled any SA Server Agent installed on the server you plan to use for a new Satellite.
• After the installation process completes, the new Satellite server is owned by the customer “Opsware”. Before beginning the installation, consider any effects this may have on access rights.

Satellite free disk space requirements

This section describes the free disk space (in addition to the operating files system) requirements for any SA Satellite.

Free disk space required for Satellite component directory

Satellite Component Directory	Recommended Free Disk Space
/opt/opsware	15 GB
/var/log/opsware	10 GB
/var/opt/opsware	20 GB (dependent on caching plans and the core cache size)
/osmedia	15 GB (dependent on SA Provisioning needs)

Required open ports

Ensure the ports listed in the following table are open so that the Satellite’s Gateway can use them. The port numbers listed in the table are default values. You can select other values during the installation.

Open ports for a Satellite

Port	Description
1002	Agent
1003	Wordcache
1006	Wordcache
2001	The port used by a tunnel end-point listener. This port is used when you install other Gateways that tunnel to the Satellite.
3001	The proxy port on which Agents contact the Satellite.
4040	The Gateway ident service port, used by the Software Repository Cache.
8061	The port is used for Software Repository Accelerator (tsunami) component.

IPv6 networking option

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

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

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