From version 12 SP1 onward, SMT is included in SUSE Linux Enterprise Server. To install it, start SUSE Linux Enterprise Server installation, and click on the screen. Then select the pattern on the screen, and confirm with .
If you already have SUSE Linux Enterprise Server installed and want to install SMT additionally, follow the same procedure, but instead of including the SMT pattern from the installation screen, simply run › › , select › and select the pattern there.
Because SMT depends on other software products, such as Maria DB database engine or Apache Web server, several packages are automatically selected for installation.
It is recommended to check for SMT updates available immediately after
installing SUSE Linux Enterprise Server. SUSE continuously releases maintenance updates for
SMT, and newer packages are likely to be available compared to those
installed from media, for example using the zypper
patch command.
After the system is installed and updated, do a first-time SMT configuration with › › .
The two-step helps you configure SMT after SUSE Linux Enterprise Server installation is finished. You can then change the configuration later using the YaST SMT Server Configuration module—see Chapter 2, SMT Server Configuration.
The option is checked by default. Uncheck it only if you want to disable the SMT product.
If the firewall is enabled, check to allow access to the SMT service from remote computers.
Enter your SUSE Customer Center organization credentials in and . If you do not know your SUSE Customer Center credentials, refer to Section 3.1, “Mirroring Credentials”. Test the entered credentials by clicking the button. SMT will connect to the Customer Center server using the provided credentials and download some testing data.
Enter the e-mail address you used for the SUSE Customer Center registration into .
should contain the URL of the SMT server being configured. It is populated automatically.
Press to continue to the second configuration step.
For security reasons, SMT requires a separate user to connect to the database. With the widget set the database password for that user. Confirm it in the following field.
Enter all e-mail addresses that SMT should send reports to using the button. You are also able to or any incorrect or obsolete addresses.
Then click .
If the current database root password is empty—as in any freshly installed system—you will be asked to enter it.
SMT defaults to communicate with the client hosts via a secure
protocol. To use the secured https protocol,
the SMT server needs to have a server SSL certificate. If it is not
created yet, the wizard warns you and offers its creation with
. Refer to
Section 17.2, “YaST Modules for CA Management” for detailed information
to manage certificates with YaST.
This section contains information about upgrading SMT from the previous versions.
Direct upgrade path from SMT prior to version 11 SP3 is not supported. You need to upgrade the operating system to SUSE Linux Enterprise Server 11 SP3 or SP4 as described in https://www.suse.com/documentation/sles11/book_sle_deployment/data/cha_update_sle.html, and at the same time upgrade SMT to version 11 SP3 as described in https://www.suse.com/documentation/smt11/book_yep/data/smt_installation_upgrade.html. Then follow the steps described in Section 1.2.2, “Upgrade from SMT 11 SP3”.
Upgrade from SMT 12 SP1 happens automatically during the SUSE Linux Enterprise Server upgrade, and needs no further manual steps. For more information on SUSE Linux Enterprise Server upgrade, see Chapter 14, Upgrading SUSE Linux Enterprise.
To upgrade SMT from version 11 SP3 to 12 SP2, follow these steps:
If you have not already done so, migrate from Novell Customer Center to SUSE Customer Center as described in Section 1.2.2.1, “Migration to SUSE Customer Center on SMT 11 SP3”.
Back up and migrate the database. See the general procedure in Section 14.1.4, “Migrate your MySQL Database”.
Upgrade to SUSE Linux Enterprise Server 12 SP2 as described in Chapter 14, Upgrading SUSE Linux Enterprise.
Look if the new /etc/my.cnf.rpmnew
exists and update it with any custom changes you need. Then
copy it over the existing /etc/my.cnf:
cp /etc/my.cnf.rpmnew /etc/my.cnf
Enable the smt target to start at
the system boot:
systemctl enable smt.target
and optionally start it now:
systemctl start smt.target
SMT now registers against SUSE Customer Center instead of Novell Customer Center. Therefore you need to switch the registration center on SUSE Linux Enterprise Server 11 before upgrading to SUSE Linux Enterprise Server 12. You can switch to SUSE Customer Center either via a YaST module or command line tools.
Before performing the switch between customer centers, make sure that the target customer center serves all products that are registered against SMT. Both YaST and the command line tools perform a check to find out whether all products can be served with the new registration server.
To perform the migration to SUSE Customer Center via command line, use:
smt ncc-scc-migration
The migration itself is time-consuming and during the migration process the SMT server may not be able to serve clients that are already registered.
The migration process itself changes the registration server and the proper type of API in the configuration files. No further (configuration) changes are needed on the SMT.
To migrate from Novell Customer Center to SUSE Customer Center via YaST, use the YaST smt-server module.
After migration is done, it is necessary to re-synchronize SMT with the customer center. It is recommended to ensure that the repositories are up to date. This can be done using the following commands:
smt sync smt mirror
SMT already includes the SLP service description file
(/etc/slp.reg.d/smt.reg). To enable SLP
announcements of the SMT service, open respective ports in your
firewall and enable the SLP service.
sysconf_addword /etc/sysconfig/SuSEfirewall2 FW_SERVICES_EXT_TCP "427" sysconf_addword /etc/sysconfig/SuSEfirewall2 FW_SERVICES_EXT_UDP "427" insserv slpd rcslpd start