8.7 How to Update Red Hat Enterprise Linux with SMT 11

SMT 11 enables customers that possess the required entitlements to mirror updates for Red Hat Enterprise Linux (RHEL). Refer to http://www.suse.com/products/expandedsupport/ for details on SUSE Linux Enterprise Server Subscription with Expanded Support. This section discusses the actions required to configure the SMT server and clients (RHEL servers) for this solution.

NOTE: SUSE Linux Enterprise Server 10

Configuring RHEL client with Subscription Management Tool for SUSE Linux Enterprise (SMT 1.0) running SUSE Linux Enterprise Server 10 is slightly different. For more information, see How to update Red Hat Enterprise Linux with SMT.

8.7.1 How to Prepare SMT server for mirroring and publishing updates for RHEL

  1. Install SUSE Linux Enterprise Server (SLES) 11 with the SMT 11 add-on product as per the documentation on the respective products.

  2. During SMT setup, use organization credentials that have access to Novell-provided RHEL update catalogs.

  3. Verify that the organization credentials have access to download updates for the Red Hat products with

    smt-repos -m | grep RES
  4. Enable mirroring of the RHEL update catalog(s) for the desired architecture(s):

    smt-repos -e repo-name architecture
  5. Mirror the updates and log verbose output:

    smt-mirror -d -L /var/log/smt/smt-mirror.log

    The updates for RHEL will also be mirrored automatically as part of the default nightly SMT mirroring cron job. When the mirror process of the catalogs for your RHEL products has completed, the updates are available via

    http://smt-server.your-domain.top/repo/$RCE/catalog-name/architecture/
  6. To enable GPG checking of the repositories, the key used to sign the repositories needs to be made available to the RHEL clients. This key is now available in the res-signingkeys package, which is included in the SMT 11 installation source.

    • Install the res-signingkeys package with the command

      zypper in -y res-signingkeys
    • The installation of the package stores the key file as /srv/www/htdocs/repo/keys/res-signingkeys.key.

    • Now the key is available to the clients and can be imported into their RPM database as described later.

8.7.2 How to Configure the YUM client on RHEL 5.2 to receive updates from SMT

  1. Import the repository signing key downloaded above into the local RPM database with

    rpm --import http://smt-server.domain.top/repo/keys/res-signingkeys.key
  2. Create a file in /etc/yum.repos.d/ and name it RES5.repo.

  3. Edit the file and enter the repository data, and point to the catalog on the SMT server as follows:

    [smt]
    name=SMT repository
    baseurl=http://smt-server.domain.top/repo/$RCE/catalog-name/architecture/
    enabled=1
    gpgcheck=1

    Example of base URL:

    http://smt.mycompany.com/repo/$RCE/RES5/i386/
  4. Save the file.

  5. Disable standard Red Hat repositories by setting

    enabled=0

    in the repository entries in other files in /etc/yum.repos.d/ (if any are enabled).

    Both YUM and the update notification applet should work correctly now and notify of available updates when applicable. You may need to restart the applet.

8.7.3 How to Configure the UP2DATE client on RHEL 3.9 and 4.7 to receive updates from SMT

  1. Import the repository signing key downloaded above into the local RPM database with

    rpm --import http://smt-server.domain.top/repo/keys/res-signingkeys.key
  2. Edit the file /etc/sysconfig/rhn/sources and make the following changes:

  3. Comment out any lines starting with up2date.

    Normally, there will be a line that says "up2date default".

  4. Add an entry pointing to the SMT repository (all in one line):

    yum repo-name http://smt-server.domain.top/repo/$RCE/catalog-name/architecture/

    where repo-name should be set to RES3 for 3.9 and RES4 for 4.7.

  5. Save the file.

Both up2date and the update notification applet should work correctly now, pointing to the SMT repository and indicating updates when available. In case of trouble, try to restart the applet.

In order to ensure correct reporting of the Red Hat Enterprise systems in Novell Customer Center or SUSE Customer Center, they need to be be registered against your SMT server. For this a special suseRegisterRES package is provided through the RES* catalogs and it should be installed, configured and executed as described below.

8.7.4 How to Register RHEL 5.2 against SMT

  1. Install the suseRegisterRES package.

    yum install suseRegisterRES

    NOTE: Additional Packages

    You may need to install perl-Crypt-SSLeay and perl-XML-Parser packages from the original RHEL media.

  2. Copy the SMT certificate to the system:

    wget http://smt-server.domain.top/smt.crt
    cat smt.crt >> /etc/pki/tls/cert.pem
  3. Edit /etc/suseRegister.conf to point to SMT by changing the URL value to

    url = https://smt-server.domain.top/center/regsvc/

    or (for SUSE Customer Center)

    url = https://smt-server.domain.top/connect/
  4. Register the system:

    suse_register

8.7.5 How to Register RHEL 4.7 and RHEL 3.9 against SMT

  1. Install the suseRegisterRES package:

    up2date --get suseRegisterRES
    up2date --get perl-XML-Writer
    rpm -ivh /var/spool/up2date/suseRegisterRES*.rpm /var/spool/up2date/perl-XML-Writer-0*.rpm

    NOTE: Additional Packages

    You may need to install perl-Crypt-SSLeay and perl-XML-Parser packages from the original RHEL media.

  2. Copy the SMT certificate to the system:

    wget http://smt-server.domain.top/smt.crt
    cat smt.crt >> /usr/share/ssl/cert.pem
  3. Edit /etc/suseRegister.conf to point to SMT by changing the URL value to

    url = https://smt-server.domain.top/center/regsvc/

    or (for SUSE Customer Center)

    url = https://smt-server.domain.top/connect/
  4. Register the system:

    suse_register