10.2. Setting Up a Self-Subscribed Red Hat Satellite
satellite-synccommand get new packages and content from the Red Hat Network Classic Hosted servers.
- A self-subscribed Satellite cannot be used as means to monitor itself. Installing the client side
rhnmdpackage will break the monitoring of the Satellite. Red Hat Network Classic Hosted provides custom monitoring probes that can be configured to monitor a self-subscribed Satellite.
- A self-subscribed Satellite treats the self-registration as it does any other client system registration. To prevent accidental changes to your self-subscribed Satellite lock the self-subscribed Satellite's system profile using Lock system in the system profile.
- A self-subscribed Satellite cannot use
osad. Installing the client-side
osadpackage will break the provisioning feature of Satellite.
10.2.1. Installing and Configuring a Self-Subscribed Satellite
Procedure 10.3. Installing and Configuring a Self-Subscribed Satellite
- Install Red Hat Enterprise Linux following the instructions provided in Scenario 1: Installing Satellite with Embedded Database in the Red Hat Satellite 5 Installation Guide.
- Install Red Hat Satellite 5 following the instructions provided in Scenario 1: Installing Satellite with Embedded Database in the Red Hat Satellite 5 Installation Guide. Allow the Satellite to register and activate the Satellite subscription to Red Hat Network Classic Hosted.
- Use the
satellite-synccommand to download and import the base channel that matches the version of Red Hat Enterprise Linux installed on the Satellite server in Step 1. The
satellite-synccommand can import the necessary files either from the Red Hat Network Classic Hosted servers or the base channel content ISOs available for download.
- Use the Satellite 5 web interface to create a cloned channel of the imported base channel. See Chapter 5, Cloning Software Channels and Errata for more information.
- Use the following command to rename the
systemidfile. This file allows communication between the Satellite and the Red Hat Network Classic Hosted servers.
# mv /etc/sysconfig/rhn/systemid /etc/sysconfig/rhn/systemid.sat
- Install the client side Satellite SSL certificate onto the Satellite using the following command.
# rpm -Uvh /var/www/html/pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm
Red Hat Update Agentto use the Satellite hostname and SSL certificate by editing the
/etc/sysconfig/rhn/up2date. Change the following options:The
/etc/sysconfig/rhn/up2dateoptions will be set
sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT noSSLServerURL=http://satellite-server-hostname/XMLRPC serverURL=https://satellite-server-hostname/XMLRPC
NoteThe HTTP proxy information that allows the Satellite access to the Red Hat Network Classic Hosted server must be removed from the configuration settings. This will permit the Update Agent to communicate with the Satellite.Depending on network settings it may be necessary to use the main IP address associated with the default network card to communicate with the Satellite rather than the hostname or localhost.
- Register the Satellite server using one of the following commands:
- Red Hat Enterprise Linux 5, 6, and 7:
rhnreg_ks --username satellite_username --password satellite_passwordcommand.
- Red Hat Enterprise Linux 3 and 4:
- Once registration is complete rename the
systemid.up2dateand rename the
systemid.satfile back to
systemidusing the following commands.
# mv /etc/sysconfig/rhn/systemid /etc/sysconfig/rhn/systemid.up2date # mv /etc/sysconfig/rhn/systemid.sat /etc/sysconfig/rhn/systemid
- Change the
up2dateto the path of the
- Log into the Satellite web interface. Go to the→ then select the cloned base channel from the drop-down menu. Click .