Red Hat NETWORK SATELLITE SERVER 4.1.0, Руководство по установке

Страница: 18 / 80

14 Chapter 2. Requirements
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
Satellite Servers 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 Satellite Servers
should be synchronized directly over the Internet.
•
All unnecessary ports should be firewalled off. Client systems connect to RHN Satel-
lite Server 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.