Installation guide

Note
Choosing the Sync All Orgs to Slave? option on the Master Setup page will
override any specifically selected organizations in the Local Organization table
below.
e. Click Create.
f. (Optional) Click on any local organization to be exported to the Slave Satellite.
g. Click Allow Orgs.
Note
In Satellite 5.5, the Master Satellite used the iss_slaves parameter in the
/etc/rhn/rhn.conf file to identify which slaves could contact the Master Satellite.
Satellite 5.6 uses the information in the Master Setup page to determine this
information.
2. On the Command Line:
a. Enable the inter-satellite synchronization (ISS) feature in the /etc/rhn/rhn.conf file:
disable_iss=0
b. Save the configuration file, and restart the httpd service:
service httpd restart
Procedure 1.2. Configuring Slave Servers
Slave Satellite servers are the machines that will receive content synchronized from the master server.
1. In order to securely transfer content to the slave servers, the ORG-SSL certificate from the master
server is needed. T he certificate can be downloaded over HTTP from the /pub/ directory of any
satellite. T he file is called RHN-ORG-TRUST ED-SSL-CERT , but can be renamed and placed
anywhere in the local filesystem of the slave, such as the /usr/share/rhn/ directory.
2. Log in to the Slave Satellite as the Satellite Administrator.
3. Click AdminISS Configuration Slave Setup.
4. On the top right-hand corner, click Add New Master.
5. Fill in the following information:
Master Fully-Qualified Domain Name
Default Master?
Filename of this Master's CA Certificate - Use the full path of the CA Certificate downloaded in
the initial step of this procedure.
6. Click Add New Master.
Procedure 1.3. Performing an Inter-Satellite Synchronization
Once the master and slave servers are configured, a synchronization can be performed between them.
Red Hat Satellite 5.6 Reference Guide
36