Red Hat NETWORK SATELLITE 5.3.0 - CHANNEL MANAGEMENT, Installation Manual, Page: 78 / 84

Chapter 8. Maintenance
74
the typical delay between scheduling an action and the client system checking in with RHN to retrieve
it.
Important
SSL must be employed between the Satellite and its clients systems for this feature to
work. If the SSL certificates are not available, the daemon on the client system fails to
connect.
To take advantage of this feature, you must first configure your firewall rules to allow connections on
the required port(s), as described in
Section 2.4, “Additional Requirements”
.
Then you must install the
osa-dispatcher
package, which can be found in the RHN Satellite
software channel for the Satellite within the central RHN website. Once installed, start the service on
the Satellite as root using the command:
service osa-dispatcher start
Finally, install the
osad
package on all client systems to receive pushed actions. The package can be
found within the RHN Tools child channel for the systems on the RHN Satellite.
Warning
Do
not
install the
osad
package on the Satellite server, as it will conflict with the
osa-
dispatcher
package installed on the Satellite.
Once installed, start the service on the client systems as root using the command:
service osad start
Like other services,
osa-dispatcher
and
osad
accept
stop
,
restart
, and
status
commands,
as well.
Keep in mind, this feature depends on the client system recognizing the fully qualified domain
name (FQDN) of the Satellite. This name and not the IP address of the server must be used when
configuring the
Red Hat Update Agent
. Refer to the
RHN Client Configuration Guide
for details.
Now when you schedule actions from the Satellite on any of the push-enabled systems, the task will
begin immediately rather than wait for the system to check in.