Table of Contents
Advertisement
Chapter 2. Requirements
CREATE TYPE
•
CREATE SESSION
•
Additional database requirements include:
Security Identifier (SID)
•
Listener Port
•
Username
•
Uniform Extent Size
•
Auto Segment Space Management
•
UTF-8 character set
•
The disk layout on the database machine is independent of the RHN Satellite Server and
entirely up to the customer.
2.4. Additional Requirements
The following additional requirements must be met before the RHN Satellite Server instal-
lation:
Full Access
•
Client systems need full network access to the RHN Satellite Server solution's services
and ports.
•
Firewall Rules
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. Also, if Monitoring
is enabled on your RHN Satellite Server, inbound traffic must be allowed on port 4545.
•
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)
•
13
Advertisement
Table of Contents
