Register on the Command Line (Salt)
In most cases, Salt clients are registered accurately with the default bootstrap methods. However, you can use Salt to register the client to the SUSE Manager Server manually by editing the Salt minion file on the client, and providing the fully qualified domain name (FQDN) of the server. This method uses ports 4505 and 4506 inbound to the server. This method requires no configuration on the SUSE Manager Server aside from ensuring that these ports are open.
Registering on the command line is also possible with traditional clients, but it requires more steps. It is not covered here. Use the bootstrap script procedure to register traditional clients. For more information, see Register Clients with a Bootstrap Script. |
This procedure requires that you have installed the salt-minion
package on the Salt client before registration.
For SLE 12 based clients, you also must have activated the Advanced Systems Management
module.
Bootstrapping this way will only work if you use the |
-
On the Salt client, open the
minion
configuration file. The configuration file is either located at:/etc/salt/minion
or:
/etc/salt/minion.d/NAME.conf
-
In the file add or edit the FQDN of the SUSE Manager Server or Proxy, and the activation key if any. Also add the other configuration parameters listed below.
master: SERVER.EXAMPLE.COM grains: susemanager: activation_key: "<Activation_Key_Name>" server_id_use_crc: adler32 enable_legacy_startup_events: False enable_fqdns_grains: False
-
Restart the
salt-minion
service:systemctl restart salt-minion
-
On the SUSE Manager Server, accept the new client key; replace
<client>
with the name of your client:salt-key -a '<client>'
For more information about the /etc/salt/minion
configuration file, see https://docs.saltstack.com/en/latest/ref/configuration/minion.html.
To register and use CentOS 6, Oracle Linux 6, Red Hat Enterprise Linux 6, or SUSE Linux Enterprise Server with Expanded Support 6 clients, you need to configure the SUSE Manager Server to support older types of SSL encryption.
For more information about how to resolve this error, see |