Red Hat NETWORK SATELLITE 5.3.0 - CHANNEL MANAGEMENT, Installation Manual, Page: 20 / 84

Chapter 2. Requirements
16
Subscribing to these channels and updating your Satellite (such as by running
yum
on
Red Hat Enterprise Linux 5 or
up2date
or earlier versions of Red Hat Enterprise Linux)
may install newer, incompatible versions of critical software components, causing the
Satellite to fail.
• Backups of Login Information
It is imperative that customers keep track of all primary login information. For RHN Satellite, this
includes usernames and passwords for the Organization Administrator account on rhn.redhat.com,
the primary administrator account on the Satellite itself, SSL certificate generation, and database
connection (which also requires a SID, or net service name). Red Hat strongly recommends this
information be copied onto two separate floppy disks, printed out on paper, and stored in a fireproof
safe.
In addition to these requirements, it is recommended that the RHN Satellite be configured in the
following manner:
• The entire RHN Satellite solution should be protected by a firewall if the Satellite accesses or is
accessed via the Internet. An Internet connection is not required for RHN Satellites running in
completely disconnected environments. This feature instead uses Channel Content ISOs that can
be downloaded to a separate system to synchronize the Satellite with the central Red Hat Network
Servers. All other RHN Satellites should be synchronized directly over the Internet.
Note
If you are running a disconnected Satellite that is not registered to RHN Hosted the
installation program will note and return a list of any missing additional packages
needed beyond
@base
to be installed, then the installation program will exit. This allows
you to install those packages. You may want to use the installation ISO image or DVD
media to create a repository for those additional packages, and then rerun the Satellite
installer.
• All unnecessary ports should be firewalled off. Client systems connect to RHN Satellite over ports
80, 443, and 4545 (if Monitoring is enabled). In addition, if you plan to enable the pushing of actions
from the Satellite to client systems, as described in
Section 8.10, “Enabling Push to Clients”
, you
must allow inbound connections on port 5222. Finally, if the Satellite will also push to an RHN Proxy
Server, you must also allow inbound connections on port 5269.
• No system components should be directly, publicly available. No user other than the system
administrators should have shell access to these machines.
•
All unnecessary services should be disabled using
ntsysv
or
chkconfig
.
•
The
httpd
service should be enabled.
•
If the Satellite serves Monitoring-entitled systems and you wish to acknowledge via email the
alert notifications you receive, you must configure
sendmail
to properly handle incoming mail as
described in
Section 4.4, “Sendmail Configuration”
.