Red Hat NETWORK SATELLITE 5.2 Installation Manual page 15

Port
4545
5222
5269
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 be
linked to a working DNS server in the customer environment.
•
An Entitlement Certificate
The customer will receive, via email from the sales representative, a signed Entitlement Certificate
explaining the services provided by Red Hat through RHN Satellite Server. This certificate will be
required during the installation process.
• A Red Hat Network Account
Direction
Outbound
Inbound
Inbound
Additional Requirements
Reason
satellite.rhn.redhat.com
a disconnected mode for Satellite)
RHN Satellite Server 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
6
(unless running in
11