Red Hat NETWORK SATELLITE 5.3.0 - CHANNEL MANAGEMENT, Reference Manual

Page: 59 / 318

Registering with Activation Keys
47
In addition, Provisioning-entitled systems may use multiple activation keys at once, either at the
command line or within kickstart profiles. This allows Administrators to include a variety of values
without creating a special key for the desired results. To do this, specify the keys separated by
commas, like this:
rhnreg_ks --activationkey=7202f3b7d218cf59b764f9f6e9fa281b,\
39f41081f0329c20798876f37cb9p6a3
Note
The trailing backslash (
\
) in this command example is a continuation character; it may
safely be omitted.
Refer to
Section 7.4.6.2, “Using Multiple Activation Keys at Once —
”
to understand how differences in activation keys are handled.
The above command performs all the actions of the
Red Hat Network Registration Client
and
the registration function of the
Red Hat Update Agent
. Do not run either of these applications for
registration after running
rhnreg_ks
.
A System Profile, including software and hardware information, is created for the system and sent
to the RHN Servers along with the unique activation key. The system is registered with RHN under
the account used to generate the key, entitled to an RHN service offering, and subscribed to the
RHN channels and system groups selected during key generation. The system is not subscribed to
channels that contain packages unsuitable for the system. For example, a Red Hat Enterprise Linux
2.1 system cannot be subscribed to the Red Hat Enterprise Linux 3 channel.
The unique Digital Certificate for the system is generated on the system in the file
/etc/sysconfig/
rhn/systemid
.
When using activation keys to assign channels, consider these rules:
• A key may specify either zero or one base channel. If specified, it must be a custom base channel.
If not, the base channel corresponding to the system's Red Hat distribution is chosen. For instance,
you may not subscribe a Red Hat Enterprise Linux 2.1 system to the Red Hat Enterprise Linux 3
channel.
• A key may specify any number of child channels. For each child channel, subscription is attempted.
If the child channel matches the system's base channel, subscription succeeds. If it does not, the
subscription fails silently. Refer to
Section 7.6, “Channels”
for more information.
• Keys may be modified by any user with the role of Activation Key
Administrator or Satellite Administrator (or both). These permissions are set
through the
Users
tab of the RHN website. Refer to
Section 7.9, “Users —
”
for details.