When you register SUSE Linux Enterprise Desktop or SUSE Linux Enterprise Server you automatically set nu.novell.com as an update source. Many enterprise customers prefer to setup their own local update servers which mirror nu.novell.com. The utility available to do this is called YUP, Yum Update Proxy.

YUP is not included in SUSE Linux Enterprise and can be downloaded from here (you must use the newest version of YUP if you want to mirror SP1 updates):


After installation, the configuration file resides in /etc/sysconfig/yup. You can either edit this file by hand or use the /etc/sysconfig YaST module.

Let’s take a look at some of the important parameters.

  • YUP_DEST_DIR=”/path/to/directory”
    • Specify the directory on your server where you want to save the updates.
    • Make sure you have a fair amount of disk space.
    • Yup will automatically setup the directory structure underneath this for all the different architectures and products you’re mirroring.
    • Configure your server to share these directories to clients. I use the “installation server” module to setup an http share.
  • YUP_ID=”blablabla1234″ and YUP_PASS=”password”
    • Your ID and Password can be found in 2 places:
      • Novell Customer Center. (This is the preferred method) In the Novell Customer Center (http://www.novell.com/center) click on the “Products and Subscriptions” tab, then select a relevant subscription (SLED or SLES), next double click on a subscription (you may have several). You’ll see a link to generate mirror credentials down at the bottom of the new page. This page will create credentials that you can use to access any and all catalogs that you own a subscription for.
      • /etz/zmd/secret and deviceid on a machine that has been registered with the Novell Customer Center. If you use userid/secret from /etc/zmd you can only download updates for the architecture you registered with.
  • YUP_SERVER=”nu.novell.com”
    • “nu.novell.com” is the new name of the update server at novell.
    • I just copy the ID and Password that we discussed above
  • YUP_ARCH=”i586″
    • Pick the architecture(s) that you want to mirror.
    • Multiple architectures are delimited by a spaces
    • Valid options: i586,ppc,s390x,ia64,x86_64
    • Pick whether you want to mirror SLES or SLED
    • Multiple architectures are delimited by a spaces
    • Valid options SLES10 and/or SLED10
    • Pick the subversion(s) you want to mirror
    • Multiple architectures are delimited by a spaces
    • Valid options: “GA”,”SP1″

Once you have finished configuring, simply run the command “YUP” to pull down the updates. This process can take a long time depending on the speed of your connection and the number of products and architectures you want to pull down. You can create a cron job to update your mirror. After it is run once, yup will only pull down updates that you don’t already have.

After setting up the YUP server you have to configure clients to point to your server for updates.

From the command line use the rug command:

#assuming you’re using http, use this command to add the service.
rug sa --type=YUM http://ipaddress/install/sledyup/i586 repodata
#subscribe to the service
rug sub -a
# update your server
rug up

You can also use the ZMD applet

  • Right click on the ZMD applet
  • Choose configure
  • Add service
  • Choose ZYPP
  • Enter the URI and Service Name (repodata is the default name)