
Chapter 2. Requirements
14
Note
Ensure that the NLS/charset setting is set to "UTF8"' when using an external database, not
'AL32UTF8' or other charsets. Using other charsets may lead to problems later.
The disk layout on the database machine is independent of the RHN Satellite and entirely up to the
customer.
2.4. Additional Requirements
The following additional requirements must be met before the RHN Satellite installation:
• Full Access
Client systems need full network access to the RHN Satellite solution's services and ports.
•
Firewall Rules
RHN strongly recommends firewalling the RHN Satellite solution from the Internet. However, various
TCP ports must be opened on the Satellite, depending on your implementation of RHN Satellite:
Table 2.4. Ports to open on the Satellite
Port Direction Reason
67 Inbound Open this port to configure the Satellite
system as a DHCP server for systems
requesting IP addresses.
69 Inbound Open this port to configure Satellite as a
PXE server and allow installation and re-
installation of PXE-boot enabled systems.
80 Outbound Satellite uses this port to reach RHN
1
80 Inbound WebUI and client requests come in via
either http or https
443 Inbound WebUI and client requests come in via
either http or https
443 Outbound RHN Satellite uses this port to reach RHN
1
(unless running in a disconnected mode
for Satellite)
4545 Inbound/Outbound RHN Satellite Monitoring makes
connections to rhnmd running on client
systems, if Monitoring is enabled and
probes are configured for registered
systems.
5222 Inbound If you plan to push actions to client
systems
5269 Inbound/Outbound If you push actions to or via an RHN
Proxy Server
1
RHN's list of hosts are as follows:rhn.redhat.com, xmlrpc.rhn.redhat.com, satellite.rhn.redhat.com, content-
xmlrpc.rhn.redhat.com, content-web.rhn.redhat.com, and content-satellite.rhn.redhat.com
Comentarios a estos manuales