Warning message
This translation is outdated. For the most up-to-date information, please refer to the English version.
Show Table of Contents
5.3.2. Activating the Satellite
You should use the options in Table 5.1, “RHN Entitlement Certificate Options” to accomplish the following tasks in this order:
- Validate the RHN Entitlement Certificate's sanity (or usefulness).
- Activate the Satellite locally by inserting the RHN Entitlement Certificate into the local database.
- Activate the Satellite remotely by inserting the RHN Entitlement Certificate into the central RHN (remote) database. This is typically accomplished during local activation but may require a second step if you chose the
--disconnectedoption.
Here are some examples depicting use of the tool and these options.
To validate an RHN Entitlement Certificate's sanity only:
rhn-satellite-activate --sanity-only --rhn-cert=/path/to/demo.cert
To validate an RHN Entitlement Certificate and populate the local database:
rhn-satellite-activate --disconnected --rhn-cert=/path/to/demo.cert
To validate an RHN Entitlement Certificate and populate both the local and the RHN database:
rhn-satellite-activate --rhn-cert=/path/to/demo.cert
Once you run this final command, the Satellite is running and able to serve packages locally and synchronize with the central RHN Servers. Refer to Chapter 6, Importing and Synchronizing.
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.