How to register a SLE system against a SMT server.

This document (7023679) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 11
SUSE Linux Enterprise Server 12
SUSE Linux Enterprise Server 15
Subscription Management Tool 11
Subscription Management Tool 12

Situation

In order to get the latest updates and patches, a SLE (SUSE Linux Enterprise) system needs to be registered as a Client against a SMT (Subscription Management Tool) server.

This document does not apply for registrations against a RMT (Repository Mirroring Tool) server.

Resolution

Before attempting any operations on the Client or the SMT server, carefully read the SMT for SLES 11 and SMT for SLES 12 documentation.

The first step is to clean up all previous registration attempts, information, files, services and repositories, including the default services and repositories added after a fresh installation of a SLE system (usually the ones pointing to DVD installation media).

IMPORTANT: If the system was registered to a SMT server in the past then the clean up will require some additional steps, please follow the instructions from TID 7022119 - De-register a SLE client from a SMT server.

NOTE: It is possible that some of the commands will return an error as it may be that not all of the below listed files will be present on all systems. If custom repositories were created manually, a backup copy of the files should be created before continuing.

- For SLE 11 based clients run the following commands as root:

# suse_register -E
# rm -f /etc/SUSEConnect
# rm -rf /etc/zypp/credentials.d/*
# rm -rf /etc/zypp/repos.d/*
# rm -f /etc/zypp/services.d/*
# rm -f /var/cache/SuseRegister/*
# rm -f /etc/suseRegister*
# rm -f /var/cache/SuseRegister/lastzmdconfig.cache
# rm -f /etc/zmd/deviceid
# rm -f /etc/zmd/secret

- For SLE 12 or SLE 15 based clients run the following commands as root:

# SUSEConnect --de-register
# SUSEConnect --cleanup
# rm -f /etc/SUSEConnect
# rm -rf /etc/zypp/credentials.d/*
# rm -rf /etc/zypp/repos.d/*
# rm -f /etc/zypp/services.d/*

Now get the registration script provided by the SMT server:

# wget http://SMT-FQDN-HERE/repo/tools/clientSetup4SMT.sh

or

# curl -O http://SMT-FQDN-HERE/repo/tools/clientSetup4SMT.sh

Assign appropriate permissions:

# chmod 755 clientSetup4SMT.sh

Run the registration script and follow the on screen instructions:

NOTE: Use the SMT's FQDN (Fully Qualified Domain Name) and it is not needed to add "http://" or "https://" , the protocol will be resolved automatically based on the SMT configuration.

# ./clientSetup4SMT.sh --host SMT-FQDN-HERE

When the registration is done, refresh the services and repositories, and check if all the expected repositories for the system provided by the SMT server are present:

# zypper ref -s
# zypper ls
# zypper lr -U

If the registration should fail, open a Service Request with SUSE Support and attach the output of the above registration commands and additionally also the log file created when running the following command:

- For SLE 11 based clients run:

# suse_register -r -d 3 --no-hw-data -L /tmp/suseregisterd3.txt

- For SLE 12 or SLE 15 based clients run:

# SUSEConnect --debug > /tmp/suseconnectd3.txt 2>&1

Cause

Additional Information

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.