Registering With Activation Keys - Red Hat NETWORK SATELLITE 5.1.0 Reference Manual

/etc/sysconfig/rhn/systemid 16. enableProxyAuth No 17. retrieveSource No 18.
versionOverride 19. headerFetchCount 10 20. networkRetries 5 21. enableProxy
No 22. proxyPassword 23. noSSLServerURL http://xmlrpc.rhn.redhat.com/XMLRPC
24. keepAfterInstall No 25. proxyUser 26. removeSkipList ['kernel*'] 27.
useGPG Yes 28. gpgKeyRing /etc/sysconfig/rhn/up2date-keyring.gpg 29.
httpProxy 30. headerCacheSize 40 31. forceInstall No Enter number of item to
edit <return to exit, q to quit without saving>:
Enter the number of the item to modify and enter a new value for the option. When you finish
changing your configuration, press Enter to save your changes and exit. Press q and then
Enter to quit without saving your changes.
Important
Although this is not 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,
ensure that their firewalls allow connections over port 443. To bypass SSL,
change the protocol for serverURL from
/etc/sysconfig/rhn/up2date

5. Registering with Activation Keys

In addition to the standard Red Hat Update Agent interface,
batch processing system registrations: activation keys. Each unique key can be used to register
Red Hat Enterprise Linux systems, entitle them to an RHN service level, and subscribe them to
specific channels and system groups, all in one action. This automation bypasses entitlement
and registration via Red Hat Network Registration Client and Red Hat Update Agent.
Alternatively, both the Red Hat Network Registration Client and Red Hat Update Agent offer the
activation keys utility
rhnreg_ks
Note
Systems running Red Hat Enterprise Linux 2.1 need version 2.9.3-1 or higher of
the
rhn_register
version before using activation keys.
Before using an activation key you must first generate one through the RHN website. Refer to
Section 4.6, "Activation Keys —
To use an activation key, run the following command as root from a shell prompt on the system
uses SSL only. For this reason, users should
up2date
configuration file.
as part of their packages.
package. It is highly recommended that you obtain the latest
" for precise steps.
Registering with Activation Keys
to in the
https http
offers a utility aimed at
up2date
35