SUSE Manager/ClientCommunication

From MicroFocusInternationalWiki
Revision as of 15:33, 24 February 2014 by Gameboy974 (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

SUSE Manager Main Page

Client Communication Methods

SUSE Manager provides several ways how managed clients are communicate with the server:

  • Pull (default)
  • Pull with OSAD
  • Push via SSH
  • Push via SSH tunnel

Depending on your environment and requirements you might want to select for specific systems something different than the default.


This is the default behavior of a managed client. Depending on your configuration in /etc/sysconfig/rhn/rhnsd the client will check with SUSE Manager server every 1 to 4 hours.

Pull with OSAD

If the timeframe of 1 hour is to long for clients to pickup the tasks you trigger in SUSE Manager, you can install the osad rpm package on the client. With that the client will ping via Port 5222 the SUSE Manager server every minute. If SUSE Manager sees a pending action for the client it will send back the information to do a full check.

Push via SSH

In contrast to the Pull methods the communication path is the other way around. In this case SUSE Manager will send a trigger to do a full check by an SSH connection to the client. The check then is done as usual.

Configuration of Push via SSH

Note: This part is under construction ATM!

  1. Generate a key "id_susemanager" without passphrase in /root/.ssh/ once.
  2. Add the public key to the /root/.ssh/authorized_keys2 on your clients you want to use with "Push via SSH"
  3. Change existing client configuration or register new systems:
    1. For already registered systems you can change the "Contact Method" in the system properties in SUSE Manager UI to "Push via SSH".
    2. For registering new systems, make sure the activation key you use has set "Push via SSH" as "Contact Method".

Push via SSH tunnel

To have the full communication done over SSH port, you can use this method. SUSE Manager will then initiate from server-side a tunnel, trigger the full check and finally close the tunnel afterwards.

Configuration of Push via SSH

Register a new system with the CLI tool "mgr-push-register <client> <bootstrap-script>". Make sure that the activation key you use has set "Push via SSH tunnel" as "Contact Method".

If you want to change existing systems to the "Push via SSH tunnel" method, you need to do the following steps:

  1. tbd - ATM read /usr/sbin/mgr-push-register is doing ;-)