Red Hat NETWORK SATELLITE 5.3.0 Installation Manual page 16

Chapter 2. Requirements
Port
80
443
443
4545
5222
5269
Table 2.4. Ports to open on the Satellite
•
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 reasonably 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 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 will be installed must resolve its own FQDN properly. If
this is not the case, cookies will not work properly on the website.
Note
It is important that the hostname of a Satellite contains no uppercase letters. A
hostname that includes uppercase letters can cause jabberd to fail.
Changing your hostname after installing Satellite is a complex process that is not
recommended.
•
Functioning Domain Name Service (DNS)
12
Direction
Inbound
Inbound
Outbound
Outbound
Inbound
Inbound
Reason
satellite.rhn.redhat.com
and
running in a disconnected mode for
Satellite)
WebUI and client requests come in via
either http or https
WebUI and client requests come in via
either http or https
rhn.redhat.com
To reach
xmlrpc.rhn.redhat.com
satellite.rhn.redhat.com
a disconnected mode for Satellite)
RHN Satellite Monitoring makes
connections to rhnmd running on client
systems, if Monitoring is enabled and
probes are configured for registered
systems.
If you plan to push actions to client
systems
If you push actions to an RHN Proxy
Server
3
(unless
4
,
5
and
6
(unless running in