Activating the Satellite35Option Description-h, --help Display the help screen with a list of options.--sanity-only Confirm certificate sanity. Does not activate theSatellite locally or remotely.--disconnected Activates locally but not on remote RHN Servers.--rhn-cert=/PATH/TO/CERT Uploads new certificate and activates the Satellitebased upon the other options passed (if any).--systemid=/PATH/TO/SYSTEMID For testing only - Provides an alternative system IDby path and file. The system default is used if notspecified.--no-ssl For testing only - Disable SSL.Table 5.1. RHN Entitlement Certificate OptionsTo use these options, insert the option and the appropriate value, if needed, after the rhn-satellite-activate command. Refer to Section 5.3.2, “Activating the Satellite”.5.3.2. Activating the SatelliteYou should use the options in Table 5.1, “RHN Entitlement Certificate Options” to accomplish thefollowing tasks in this order:1. Validate the RHN Entitlement Certificate's sanity (or usefulness).2. Activate the Satellite locally by inserting the RHN Entitlement Certificate into the local database.3. 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 secondstep if you chose the --disconnected option.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.certTo validate an RHN Entitlement Certificate and populate the local database:rhn-satellite-activate --disconnected --rhn-cert=/path/to/demo.certTo validate an RHN Entitlement Certificate and populate both the local and the RHN database:rhn-satellite-activate --rhn-cert=/path/to/demo.certOnce you run this final command, the Satellite is running and able to serve packages locally andsynchronize with the central RHN Servers. Refer to Chapter 6, Importing and Synchronizing.