Novell is now a part of Micro Focus

My Favorites


Please to see your favorites.

How to assign Long Term Service Pack Support repositories to installed systems

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


SUSE Linux Enterprise Server 9 Service Pack 4
SUSE Linux Enterprise Server 10 Service Pack 1
SUSE Linux Enterprise Server 10 Service Pack 2
SUSE Linux Enterprise Server 10 Service Pack 3
SUSE Linux Enterprise Server 10 Service Pack 4 (SLES 10 SP4)
SUSE Linux Enterprise Server 11 Service Pack 1
SUSE Linux Enterprise Server 11 Service Pack 2 (SLES 11 SP2)


After a new service pack for SUSE Linux Enterprise based products has been released, SUSE starts a six months dual support phase for both the previous and new version. After these six months,  support for the previous  service pack is stopped and no further recommended or security related updates will be released. If a requirement for a longer transition period persists or 3rd party applications prevent to upgrade to the next service pack a Long Term Service Pack Support (LTSS) contract may be an option to maintain a secure SUSE Linux Enterprise based setup.

This article will explain how LTSS repositories may be added to systems which fetch updates from Novell directly or are connected to a SMT , SUSE Manager or SUSE Studio installation.


Direct connection


In order  to patch a SLES9SP4 with LTSS packages, adjustments in /var/adm/YaST/ProdDB/prod_0000000* need to be made as these files define the directory on the update server where to check for new packages. Change the last line in any prod_* file from e.g.
=YouPath: i386/update/SUSE-SLES/9
=YouPath: i386/update/SUSE-SLES/9-LTSS
Please note: SLES9SP4 systems need to be fully patched to the latest patch level before changing the update source path.

SLES 10 SPx / SLES 11 SPx

When the server is connected directly to the internet, the system needs to be registered using a LTSS activation code which can be located in the Novell Customer Center account. Please note, LTSS  activation codes are product dependent. Registering a SLES11SP1 with an LTSS code for SLES10SP2 will not succeed. Make sure the correct activation code is selected when registering the system.

In this situation the usual procedures for registering a SLES server apply. Please see for details how to register a SLES server using YaST2. If a scripted approach is necessary, the command suse_register might be used to accomplish the registration:
suse_register -a email=EMAILADDR -a regcode-sles=LTSS-ACTIVATIONCODE
While adding the option "-d 3" to the command above, the following output should be seen when the repositories are added:
Adding repository 'SLE11-SDK-SP1-Updates' [......done]
Adding repository 'SLE11-SDK-SP1-Pool' [......done]
Adding repository 'SLES11-SP1-Updates' [......done]
Adding repository 'SLES11-SP1-Pool' [......done]
Adding repository 'SLE11-SP1-Debuginfo-Updates' [......done]
Adding repository 'SLE11-SP1-Debuginfo-Pool' [......done]
Adding repository 'SLES11-Extras' [......done]
Adding repository 'SLE11-WebYaST-SP1-Pool' [......done]
Adding repository 'SLE11-WebYaST-SP1-Updates' [......done]
Adding repository 'SLES11-SP1-LTSS-Updates' [......done]
Please adjust  EMAILADDR and LTSS-ACTIVATIONCODE accordingly. To change the registration on any SUSE Linux Enterprise based  system please follow TID 3303599 - Resetting your ZEN Updater and Novell Customer Center key registration [/support/kb/doc.php?=3303599 - Resetting your ZEN Updater and Novell Customer Center key registration].

Updates via Subscription Management Tool (SMT)

Environments using a SMT server to download and provide updates locally will have to enable the appropriate LTSS channels they are entitled to either by using the YaST2 smt module or the smt-catalogs command:

rizzo:~ # smt-catalogs -e SLES11-SP1-LTSS-Updates
| Mirror? | ID | Type | Name                    | Target        | Description                               | Can be Mirrored | Staging |
| No      |  1 | nu   | SLES11-SP1-LTSS-Updates | sle-11-i586   | SLES11-SP1-LTSS-Updates for sle-11-i586   | Yes             | No      |
| No      |  2 | nu   | SLES11-SP1-LTSS-Updates | sle-11-s390x  | SLES11-SP1-LTSS-Updates for sle-11-s390x  | No              | No      |
| No      |  3 | nu   | SLES11-SP1-LTSS-Updates | sle-11-x86_64 | SLES11-SP1-LTSS-Updates for sle-11-x86_64 | Yes             | No      |
Select repository number (or all) to change,  (1-3,a) :3
1 Repo(s) enabled.

After finishing the repository sync, please re-run suse_register to have the machine fetch the new channels from the SMT server.

Systems maintained via SUSE Manager

For systems operating a SLES11SP1 patch level and connected to SUSE Manager verify first if the Channel sles11-sp1-ltss-updates-<arch> is available and can be mirrored. Run
mgr-ncc-sync -l
and check for the channel availability below sles11-sp1-pool-<arch>. Enable the channel using
mgr-ncc-sync -c sles11-sp1-ltss-updates-x86_64
for the x86_64 architecture, or
mgr-ncc-sync -c sles11-sp1-ltss-updates-i586
for 32bit installations. A repository sync will be triggered automatically. When the sync finished, create a new activation code specifically for SLES11SP1 or adjust any existing one  - just ensure the key that is about to get changed does not contain any SP2 repositories. The SP1 key needs to contain the following child channels:
Save the key and generate a bootstrap file. Adjust this file to your needs and re-register the client using the bootstrap script to enable the LTSS repositories.

SUSE Studio Onsite

  1.    Login to SUSE Studio as admin
  2.    Click Admin user in the upper right corner
  3.    Click Advanced
  4.    Click the Repositories link
  5.    Here you can enter a name and URL to access the LTSS repository
Once the settings are done, you can manually add the LTSS repositories to your appliances as follows:
Login to SUSE Studio with your user account, select an existing SLES 11 SP1 appliance, then go to the "Software Tab", then select "Add repositories". Here you can add the LTSS repository to your appliance. After that, you need to (re-)build the appliance.


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/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.

  • Document ID:7011670
  • Creation Date:22-JAN-13
  • Modified Date:02-APR-15
    • SUSESubscription Management Tool
      SUSE Linux Enterprise Server
      SUSE Manager
      SUSE Studio

Did this document solve your problem? Provide Feedback