Show Table of Contents
11.2. Configuring the Satellite Capsule Server Discovery Plug-in
Ensure the
foreman_url setting exists in the Satellite Capsule Server configuration file. The setting can appear as follows:
# grep foreman_url /etc/foreman-proxy/settings.yml :foreman_url: https://satellite.example.com
The
satellite-installer command configures this variable automatically, but Red Hat recommends that you check that the host responds correctly and there are no firewall rules blocking communication.
11.2.1. Configuring Discovery Subnets
You need to configure all subnets with discovered hosts to communicate through the Satellite Capsule Server. In the Satellite web UI, navigate to → and select the required Capsule Server for each subnet that needs to perform host discovery and ensure it is connected to the Discovery Capsule Server.
To verify that a Capsule Server has the Discovery plug-in enabled, navigate to → . The Discovery plug-in should appear in the list of features associated with the Capsule Server. Click to ensure that the list is up-to-date.
11.2.2. Using Hammer with the Discovery Plug-in
To use the
hammer command with the Discovery plug-in, you need to enable the Discovery plug-in in /etc/hammer/cli.modules.d/foreman_discovery.yml as follows:
:foreman_discovery: :enable_module: true
See hammer configuration directories[5] for more information about the files and directories that
hammer uses.
11.2.3. Reviewing User Permissions
When it first starts, the Satellite Capsule Server Discovery plug-in creates a role called
Discovery. You can assign this role to non-administrative users to allow them to use the Discovery plug-in. Alternatively, assign the perform_discovery permission to an existing role. For more information on roles and permissions, see Creating and Managing Users in the Server Administration Guide.

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.