
4
https://rhn.redhat.com
5
http://xmlrpc.rhn.redhat.com
6
http://satellite.rhn.redhat.com
Port Direction Reason
xmlrpc.rhn.redhat.com
5
and
satellite.rhn.redhat.com
6
(unless running
in a disconnected mode for Satellite)
4545 Outbound RHN Satellite Server 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 If you push actions to an RHN Proxy
Server
Table 2.2. 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 Server 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 Server 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.
•
Functioning Domain Name Service (DNS)
For the RHN Satellite Server's domain name to be resolved by its clients, it and they must all
Chapter 2. Requirements
14
Comentários a estes Manuais