Configuring The Client Applications; Registering With Activation Keys - Red Hat NETWORK SATELLITE 5.3.0 - CLIENT Configuration Manual

Chapter 2. Client Applications
http://your_proxy_or_sat.your_domain.com/pub/pirut-1.3.28-13.3l5.noarch.rpm
Keep in mind that the architecture (in this case, i386) may need to be altered depending on the
systems to be served.

2.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 (up2date) and possibly the Red
Hat Network Registration Client (rhn_register) to redirect it from Red Hat Network to their RHN
Satellite Server or RHN Proxy Server.
Important
Although this is not configurable, note that the port used by the up2date is 80 for HTTP
and 443 for secure HTTP (HTTPS). By default, yum on Red Hat Enterprise Linux 5 uses
SSL only. For this reason, users should ensure that their firewalls allow connections over
port 443. To bypass SSL, change the protocol for serverURL from https to http in /
etc/sysconfig/rhn/up2date. Similarly, to use RHN's 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 sshd instead).
By default, the rhn_register and up2date 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.
Section 2.2.4, "Implementing Server Failover"
Refer to
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, up2date --configure, and
manually updating the configuration files.( To see how virtually all reconfiguration can be scripted, see
Chapter 6, Manually Scripting the

2.2.1. Registering with Activation Keys

Red Hat recommends using activation keys for registering and configuring client systems that access
RHN Proxy Server or RHN Satellite Server. Activation keys can be used to register, entitle, and
subscribe systems in a batch. Refer to the section "Activation Keys" in the RHN Satellite Server
Reference Guide for more information on activation keys.
Registering with an activation key has four basic steps:
1. Generate an Activation Key.
2. Import custom GPG keys.
3. Download and install the SSL Certificate RPM from the /pub/ directory of the RHN Proxy Server
or RHN Satellite Server. The command for this step could look something like this:
4
for instructions on enabling this feature.
Configuration.)