Registering With Activation Keys; Configure Option - Red Hat NETWORK 3.6 - CLIENT Configuration Manual

4
2.2. Configuring the Client Applications
Not every customer will need to connect securely to an RHN Satellite Server or RHN Proxy Server
within their organization. And not every customer will need to build and deploy a GPG key for custom
packages. (Both of these topics are explained in detail later.) But every customer who uses RHN Satel-
lite Server or RHN Proxy Server will need to reconfigure the Red Hat Update Agent (
possibly the Red Hat Network Registration Client (
or Proxy.
Important
Although this isn't configurable, users should still make note that the port used by the Red Hat Update
Agent is 443 for SSL (HTTPS) and 80 for non-SSL (HTTP). By default,
this reason, users should ensure their firewalls allow connections over port 443. To bypass SSL, in
/etc/sysconfig/rhn/up2date
if you will be using RHN's Monitoring feature and probes requiring the Red Hat Network Monitoring
Daemon, note that client systems will need to allow connections on port 4545 (or port 22, if they will
use instead).
sshd
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 the RHN Satellite
Server or RHN Proxy Server. This can be done in three different ways: using the
tion, updating the configuration file(s) manually, or scripting a change to multiple settings at once. To
see how virtually all reconfiguration can be scripted, see Chapter 6 Manually Scripting the Configu-
ration.

2.2.1. Registering with Activation Keys

Red Hat recommends using activation keys for registering and configuring client systems that will
be using RHN Proxy Server or RHN Satellite Server. Activation keys can be used to register, entitle,
and subscribe systems in a batch. Refer to the Activation Keys section of the Red Hat Update Agent
chapter within the RHN Management Reference Guide for instructions on use.
It is possible to incorporate activation keys into a scripted configuration process, such as the one
described in Chapter 6 Manually Scripting the Configuration. To do this, create a
much like the one described, place it in the Proxy or Satellite's
the rhnreg_ks utility. For example:
wget -O http://your-satellite-FQDN/pub/bootstrap.sh | bash \
&& rhnreg_ks --activation-key b0fa829d751aEXAMPLE6983a72c8346e \
--serverUrl https://your-satellite-FQDN/XMLRPC
Warning
Systems running Red Hat Enterprise Linux 2.1 and versions of Red Hat Linux prior to 8.0 may
experience problems using Activation Keys to migrate SSL certificate settings from
to . All other settings, such as the server URL, will be properly transferred. Therefore, the
up2date
SSL certificate information on those systems will have to be set manually.
rhn_register
change the protocol for
Chapter 2. Client Applications
) to be directed to the Satellite
up2date
from https to http. Similarly,
serverURL
directory and combine it with
/pub
) and
up2date
uses SSL only. For
op-
--configure
file
bootstrap.sh
rhn_register