14.3. Registration
14.3.1. Registering a Host
Prerequisites
- Ensure that all steps in Section 14.2, “Configuring a Host for Registration” have been completed.
- Make sure there is a pre-existing activation key for the system or create an activation key for the system. See Section 11.1, “Creating an Activation Key” for instructions on creating an activation key.
Procedure 14.3. To Register Systems:
- Open a terminal console and login as the
rootuser on the command line. - Clear old system data in preparation for registering. This makes sure that your updated system data is uploaded correctly.
# subscription-manager clean
- Register the system using the Red Hat Subscription Manager (RHSM):
# subscription-manager register --org your_org_name --activationkey your_activation_key
Note
Activation keys will allow you to add environments, provisioning templates and dictate what subscriptions are available and should be applied to the registering system.There are various options that may be added. For more information, use the commandman subscription-manager.
# subscription-manager register --org MyOrg --activationkey TestKey-1 The system has been registered with id: 62edc0f8-855b-4184-b1b8-72a9dc793b96
Note
- On Red Hat Satellite, select → .
- Click on the tab.
- Click the name of the host that needs to be changed.
- In the Content Host Content section click the edit icon to the right of Release Version.
- Select '6.3' from the drop-down menu.
- Click .
14.3.2. Installing the Katello Agent
goferd service. This service must be enabled so that the Red Hat Satellite Server or Capsule Server can provide information about errata that are applicable for content hosts.
Prerequisites
Satellite Tools repository. The Red Hat Common repositories are no longer used and are not compatible with Satellite version 6.1 and later.
Procedure 14.4. Verify the Satellite Tools Repository is Enabled
Satellite Tools repository must be enabled, synchronized to the Red Hat Satellite server and made available to your hosts as it provides the required packages.
- Open the Satellite web UI, navigate to → and click on the RPMs tab.
- Find and expand the Red Hat Enterprise Linux Server item.
- Find and expand the Red Hat Satellite Tools 6.1 (for RHEL VERSION Server) (RPMs) item.If the Red Hat Satellite Tools 6.1 items are not visible, it may be because they are not included in the subscription manifest obtained from the Customer Portal. To correct that, log in to the Customer Portal, add these repositories, download the subscription manifest and import it into Satellite.
- Ensure the Enabled check box beside the repository's name is selected. If not, select it.
Satellite Tools repository for every supported major version of Red Hat Enterprise Linux running on your hosts.
Procedure 14.5. To Install Katello Agent:
- On the host, open a terminal console and log in as the
rootuser. - Verify that the
satellite-toolsrepository is enabled, using the following command:# yum repolist enabled | grep -i satellite-tools
If thesatellite-toolsis not enabled, enable it using the following command:# subscription-manager repos --enable satellite-tools
- Install the
katello-agentRPM package using the following command:# yum install katello-agent
goferd service is started and enabled automatically after successful installation of katello-agent.
14.3.3. Installing and Configuring the Puppet Agent
Prerequisites
Satellite Tools repository. The Red Hat Common repositories are no longer used and are not compatible with Satellite version 6.1 and later.
Procedure 14.6. Verify the Satellite Tools Repository is Enabled
Satellite Tools repository must be enabled, synchronized to the Red Hat Satellite server and made available to your hosts as it provides the required packages.
- Open the Satellite web UI, navigate to → and click on the RPMs tab.
- Find and expand the Red Hat Enterprise Linux Server item.
- Find and expand the Red Hat Satellite Tools 6.1 (for RHEL VERSION Server) (RPMs) item.If the Red Hat Satellite Tools 6.1 items are not visible, it may be because they are not included in the subscription manifest obtained from the Customer Portal. To correct that, log in to the Customer Portal, add these repositories, download the subscription manifest and import it into Satellite.
- Ensure the Enabled check box beside the repository's name is selected. If not, select it.
Procedure 14.7. To Install and Enable the Puppet Agent:
- On the host, open a terminal console and log in as the
rootuser. - Verify that the
satellite-toolsrepository is enabled, using the following command:# yum repolist enabled | grep -i satellite-tools
If thesatellite-toolsis not enabled, enable it using the following command:# subscription-manager repos --enable satellite-tools
- Install the Puppet agent RPM package using the following command:
# yum install puppet
- Configure the puppet agent to start at boot:
- On Red Hat Enterprise Linux 6:
# chkconfig puppet on
- On Red Hat Enterprise Linux 7:
# systemctl enable puppet
Procedure 14.8. Configuring the Puppet Agent
You must meet the following conditions before continuing with this task:
- The host must be registered to the Red Hat Satellite Server.
- The Satellite Tools repository must be enabled.
- Puppet packages must be installed on the host.
- Configure the Puppet agent by changing the
/etc/puppet/puppet.conffile:# vi /etc/puppet/puppet.conf
[main] # The Puppet log directory. # The default value is '$vardir/log'. logdir = /var/log/puppet # Where Puppet PID files are kept. # The default value is '$vardir/run'. rundir = /var/run/puppet # Where SSL certificates are kept. # The default value is '$confdir/ssl'. ssldir = $vardir/ssl [agent] # The file in which puppetd stores a list of the classes # associated with the retrieved configuratiion. Can be loaded in # the separate ``puppet`` executable using the ``--loadclasses`` # option. # The default value is '$confdir/classes.txt'. classfile = $vardir/classes.txt pluginsync = true report = true ignoreschedules = true daemon = false ca_server = satellite.example.com server = satellite.example.com environment = KT_Example_Org_Library_RHEL6Server_3 # Where puppetd caches the local configuration. An # extension indicating the cache format is added automatically. # The default value is '$confdir/localconfig'. localconfig = $vardir/localconfigImportant
Set theenvironmentparameter to the host's Puppet environment from the Satellite server. The Puppet environment label contains the organization label, lifecycle environment, content view name, and the content view ID. To see a list of Puppet environments in the Satellite 6 web UI, navigate to → . - Run the Puppet agent on the host:
# puppet agent -t --server satellite.example.com
- Sign the SSL certificate for the puppet client through the Satellite Server web interface:
- Log in to the Satellite Server through the web interface.
- Select → .
- Click to the right of the required host.
- Click .
- Rerun the
puppet agentcommand:# puppet agent -t --server satellite.example.com
Note

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.