Red Hat NETWORK SATELLITE SERVER 4.0 Installation Manual page 19

Chapter 2. Requirements
RHN strongly recommends firewalling the RHN Satellite Server solution from the In-
ternet. However, it must be able to issue outbound connections to rhn.redhat.com, xml-
rpc.rhn.redhat.com and satellite.rhn.redhat.com on ports 80 and 443.
•
Synchronized System Times
There is great time sensitivity when connecting to a Web server running SSL (Secure
Sockets Layer); it is imperative that the time settings on the clients and server be rea-
sonably close together so the SSL certificate does not expire before or during use. For
this reason, Red Hat requires the Satellite and all client systems to use Network Time
Protocol (NTP). This also applies to the separate database machine in RHN Satellite
Server with Stand-Alone Database, which must also be set to the same time zone as the
Satellite.
Fully Qualified Domain Name (FQDN)
•
The system upon which the RHN Satellite Server will be installed must resolve its own
FQDN properly. If this is not the case, cookies will not work properly on the website.
Functioning Domain Name Service (DNS)
•
For the RHN Satellite Server's domain name to be resolved by its clients, it and they
must all be linked to a working DNS server in the customer environment.
•
An Entitlement Certificate
The customer will receive, via email from the sales representative, a signed Entitlement
Certificate explaining the services provided by Red Hat through RHN Satellite Server.
This certificate will be required during the installation process.
A Red Hat Network Account
•
Customers who connect to the central Red Hat Network Servers to receive incremental
updates must have an external account with Red Hat Network. This account should be
set up at the time of purchase with the sales representative.
Backups of Login Information
•
It is imperative that customers keep track of all primary login information. For RHN
Satellite Server, this includes usernames and passwords for the Organization Admin-
istrator 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 Server be
configured in the following manner:
The entire RHN Satellite Server 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
15