Satellite installation requirements

Before you install a Satellite, verify that you meet following requirements.

• If you plan to install the SA Provisioning Boot Server and Media Server components in the Satellite, you must adhere to the requirements in SA Provisioning: DHCP proxying.
• The SA Core that will provide core component services to the Satellite must be running and accessible during Satellite installation and the Satellite server must have network connectivity to that Core’s Management Gateway.
• You must be a member of the System Administrators group as well as a member of any user group that has Manage Gateway permissions.
• You must have a root access to parent Core’s Model Repository host from which you can copy the cryptographic material and security configuration file to the Satellite server.
• The Satellite server uses UTC, as described in Check the Core host(s) time and locale requirements. The Satellite server’s system time must be synchronized with the Primary Core host.
• If you plan to locate the Satellite’s Software Repository Cache on a network storage device, the network storage configuration must allow root write access over NFS to the directories in which the Software Repository Cache will be installed.
• If you already have an SA Server Agent installed on a server you plan to use for a new Satellite, you must uninstall it before running the Satellite Installer.
• Make note that after the installation process completes, the new Satellite server is owned by the customer “Opsware”. You should take into account any effects this may have on access rights before beginning the installation.

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 (dependant on caching plans and the core cache size)
/osmedia	15 GB (dependant on SA Provisioning needs)

Required open ports

The ports listed in the following table must be open for use by the Satellite’s Gateway. 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, 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 the SA Remote Communications Administration section in the SA 10.50 Administration Guide.

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