Red Hat NETWORK SATELLITE SERVER 3.7 Installation Manual

Contents

Red Hat NETWORK SATELLITE SERVER 3.7 Installation Manual Manual pdf 16 page image

12 Chapter 2. Requirements2.4. Additional RequirementsThe following additional requirements must be met before the RHN Satellite Server installation:• Full AccessClient systems need full network access to the RHN Satellite Server solution’s services and ports.• Firewall RulesThe RHN Satellite Server solution can be firewalled from the Internet, but it must be able to issueoutbound connections to rhn.redhat.com and xmlrpc.rhn.redhat.com on ports 80 and 443.• Synchronized System TimesThere is great time sensitivity when connecting to a Web server running SSL (Secure SocketsLayer); it is imperative the time settings on the clients and server be reasonably close together sothe SSL certificate does not expire before or during use. For this reason, Red Hat requires the Satel-lite and all client systems to use Network Time Protocol (NTP). This also applies to the separatedatabase machine in RHN Satellite Server with Stand-Alone Database, which must also be set tothe 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 FQDNproperly. 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 belinked to a working DNS server in the customer environment.• An Entitlement CertificateThe customer will receive, via email from the sales representative, a signed Entitlement Certificateexplaining the services provided by Red Hat through RHN Satellite Server. This certificate will berequired during the installation process.• A Red Hat Network AccountCustomers who will be connecting to the central Red Hat Network Servers to receive incrementalupdates will need an external account with Red Hat Network. This account should be set up at thetime of purchase with the sales representative.• Backups of Login InformationIt is imperative customers keep track of all primary login information. For RHN Satellite Server, thisincludes usernames and passwords for the Organization Administrator account on rhn.redhat.com,the primary administrator account on the Satellite itself, SSL certificate generation, and databaseconnection (which also requires a SID, or net service name). Red Hat strongly recommends thisinformation be copied onto two separate floppy disks, printed out on paper, and stored in a fireproofsafe.In addition to these requirements, it is recommended the RHN Satellite Server be configured in thefollowing manner:• The entire RHN Satellite Server solution should be protected by a firewall if the Satellite will beaccessing, or be accessed via the Internet. An Internet connection is not required for RHN Satel-lite Servers running in completely disconnected environments as this feature instead uses ChannelContent ISOs that can be downloaded to a separate system to synchronize the Satellite with thecentral Red Hat Network Servers. All other RHN Satellite Servers should be synchronized directlyover the Internet.• All unnecessary ports should be firewalled off. Client systems connect to RHN Satellite Server overports 80 and 443 only. In addition, if you plan to enable the pushing of actions from the Satellite