10.2.3. Client-Side Application Functionality with a Self-Subscribed Satellite
rhnmdclient-side monitoring package onto a self-subscribed Satellite as this will break Monitoring.
- If a client-side application is not listed here it has not been tested.
- Red Hat recommends that Administrators lock the registered Self-Subscribed Satellite within the Satellite web interface. This prevents any scheduled event from executing. Before unlocking the Satellite review the pending events and delete those you do not want to run.
- Red Hat recommends Administrators entitle the Self-Subscribed Satellite to the Management level but with no Provisioning or Monitoring entitlements. This helps to avoid possible harmful or accidental changes to the Satellite server.
- If the self-subscribed Satellite has been granted a Provisioning entitlement do not attempt to use the Satellite to re-provision itself. The Satellite will attempt to perform the re-installation of the Red Hat Enterprise Linux operating system but on reboot the Red Hat installation program will be unable to download the necessary packages from the Satellite to perform the installation. There is a high risk of data loss and service interruption for your Satellite, especially if external kickstart trees are used.
- Red Hat Update Agent ToolsThe
yumpackages will all function normally on a self-subscribed Satellite.
osadpackage will not install. The
osadpackage is used to push packages to client systems but it conflicts with the server-side
osa-dispatcherpackage. Do not attempt to force the installation of
osadon a self-subscribed Satellite.
- AppletBoth the
rhn-applet-tuipackage and the
rhn-applet-guipackage will function normally. Installation and configuration of the
rhn-applet-guipackages will complete normally. These packages allow client systems to communicate with the Satellite.
rhn-applet-guirequires packages that are not installed by default.
- Configuration Client ToolThe
rhncfg-clientpackage will function normally after a change to the configuration file. Edit the
/etc/sysconfig/rhn/rhncfg-client.conffile and change the
systemIdPathoption to match the path to
systemid.up2datecreated in Procedure 10.3, “Installing and Configuring a Self-Subscribed Satellite”.
- Configuration Management ToolThe
rhncfg-managerpackage will function normally.
- Custom InfoThe
rhn-custom-infopackage will function normally.
- Client MonitoringThe
rhnmdpackage will not install. The
rhnmdpackage conflicts with the server-side monitoring packages. Do not attempt to force the installation of
rhnmdas this will break Monitoring on the Satellite.