Configuring The Client Applications - Red Hat NETWORK SATELLITE 5.1.0 - CLIENT Configuration Manual

Chapter 2. Client Applications
rpm -Uvh \
http://your_proxy_or_sat.your_domain.com/pub/rhn_register-2.9.12-1.2.1AS.i386.rpm
\
http://your_proxy_or_sat.your_domain.com/pub/rhn_register-gnome-2.9.12-1.2.1AS.i386.rpm
\
http://your_proxy_or_sat.your_domain.com/pub/up2date-2.9.14-1.2.1AS.i386.rpm
\
http://your_proxy_or_sat.your_domain.com/pub/up2date-gnome-2.9.14-1.2.1AS.i386.rpm
Note the inclusion of the associated gnome RPMs. Keep in mind, the architecture (in this case,
i386) may need to be altered depending on the systems to be served.

2. Configuring the Client Applications

Not every customer must connect securely to a RHN Satellite Server or RHN Proxy Server
within their organization. Not every customer needs to build and deploy a GPG key for custom
packages. (Both of these topics are explained in detail later.) Every customer who uses RHN
Satellite Server or RHN Proxy Server must reconfigure the Red Hat Update Agent (
and possibly the Red Hat Network Registration Client (
Hat Network to their RHN Satellite Server or RHN Proxy Server.
Important
Although this is not configurable, note that the port used by the Red Hat Update
Agent is 443 for SSL (HTTPS) and 80 for non-SSL (HTTP). By default,
uses SSL only. For this reason, users should ensure that their firewalls allow
connections over port 443. To bypass SSL, change the protocol for
from
https
Monitoring feature and probes requiring the Red Hat Network Monitoring
Daemon, note that client systems must allow connections on port 4545 (or port
22, if using
By default, the Red Hat Network Registration Client and the Red Hat Update Agent refer to
the main Red Hat Network Servers. Users must reconfigure client systems to refer to their RHN
Satellite Server or RHN Proxy Server.
Note that the latest versions of the Red Hat Update Agent can be configured to accommodate
several RHN Servers, thereby providing failover protection in case the primary server is
inaccessible. Refer to Section 2.4, "Implementing Server Failover"
this feature.
The next sections describe three methods of configuring the client systems to access your RHN
Satellite Server or RHN Proxy Server: using an Activation Key,
manually updating the configuration files.( To see how virtually all reconfiguration can be
scripted, see Chapter 6, Manually Scripting the
4
to in
http /etc/sysconfig/rhn/up2date
instead).
sshd
Configuration.)
) to redirect it from Red
rhn_register
. Similarly, to use RHN's
for instructions on enabling
up2date --configure
)
up2date
up2date
serverURL
, and