6
Chapter 1. Introduction
3. Your Red Hat contact creates a Satellite-entitled account on the RHN website and
sends you the login information.
4. Log into the RHN website (rhn.redhat.com) and download the distribution ISOs for
Red Hat Enterprise Linux AS 3 or 4 and RHN Satellite Server 4.0.5. These can be
found within the
Downloads
tab of the respective
Channel Details
pages. Refer to
the
RHN Reference Guide
for instructions.
5. While still logged into the RHN website, download the Channel Content ISOs to
be served by your Satellite, also available through the
Downloads
tab of your Satel-
lite’s
Channel Details
page. These Channel Content ISOs differ from the distribution
ISOs previously mentioned in that they contain metadata necessary for parsing and
serving packages by Satellite.
6. If installing a Stand-Alone Database, prepare your database instance using the for-
mula provided in Chapter 2
Requirements
.
7. Install Red Hat Enterprise Linux AS and then RHN Satellite Server 4.0.5 on the
Satellite machine.
8. Create the first user account on the Satellite by opening the Satellite’s hostname in a
Web browser and clicking
Create Account
. This will be the Satellite Administrator’s
(also referred to as the Organization Administrator) account.
9. Use the
RHN Satellite Synchronization Tool
to import the channels and associated
packages into the Satellite.
10. Register a representative machine for each distribution type, or channel (Red Hat
Enterprise Linux AS 2.1, 3, 4), to the Satellite.
11. Copy (using SCP) the
rhn_register
and
up2date
configuration files from the
/etc/sysconfig/rhn/
directory of each machine individually to the
/pub/
di-
rectory on the Satellite. The
rhn-org-trusted-ssl-cert-*.noarch.rpm
will
already be there.
12. Download and install from the Satellite the configuration files and
rhn-org-trusted-ssl-cert-*.noarch.rpm
on the remaining client systems
of the same distribution type. Repeat this and the previous step until all distribution
types are complete.
13. Through the Satellite’s website, create an Activation Key for each distribution
aligned to the appropriate base channel. At this point, system groups and child
channels may also be predefined.
14. Run the Activation Key from the command line (
rhnreg_ks
) of each client system.
Note that this step can be scripted to batch register and reconfigure all remaining
client systems in a distribution.
15. Record all relevant usernames, passwords and other login information and store in
multiple secure places.
16. Now that the Satellite is populated with standard Red Hat channels and packages and
all clients are connected to it, you may begin creating and serving custom channels