SUSE Conversations


Sneakernetting SLES10 SP2 Updates using the Subscription Management Tool (SMT)



By: mfriesenegger

October 31, 2008 2:17 pm

Reads:527

Comments:1

Rating:0

An installation server can be added if there are a number of servers in the secured location that can be updated over the secured network. Look at the “Using an Installation server in the secured location” section. Otherwise, the updates will need to be local to each SLES server that is updated.

Here is a simple diagram how this will work:

Sneakernetting_SLES_Updates_using_SMT.jpg (29.32 KB)
Sneakernetting_SLES_Updates_using_SMT_0.jpg

Prep work on a SLES server that is connected to the Internet

  1. Download the SMT iso from http://download.novell.com/Download?buildid=5YxjWD8_ZZk
  2. Install SMT using the following instructions http://www.novell.com/documentation/sles10/esd/ii_smt.html
  3. Use the SMT documentation to configure and begin the mirroring of updates from Novell. The documentation is located in /usr/share/doc/manual/sle-smt_en after the SMT installation.

Sneakernetting the updates from the SMT server

  1. On the SMT server, the default location of the mirror is /srv/www/htdocs on the SMT server. To verify, type “grep MirrorTo /etc/smt.conf”
  2. SMT builds a directory structure under the default location which is repo/$RCE/SLES10-SP2-Updates. Use the CLI or a GUI file browser to look at this directory. You should see directories like sles-10-architecture
  3. The Updates directory structure may be larger than can fit on one DVD. Use the –multi-volume and –tape-length options with tar to create multiple tar files that can fit on several DVDs. Example: “tar -c -ML 4718592 -vf disk1.tar SLES10-SP2-Updates/*” assumes approximately 4.5GB in a single tar file. NOTE: When prompted “Prepare volume #2 for disk1.tar and hit return:” type “n disk2.tar” and <Enter> to write to the next tar file. Repeat until all tar files have been created. Great resource – http://www.base64.co.uk/splitting-large-files/
  4. Burn to a DVD (use Nautilus > Go > CD/DVD Creator) or copy to USB storage the entire SLES10-SP2-Updates directory, specific SLES10-SP2-Updates/sles-10-<architecture> directories or the tar files that need to be sneakernetted to the server not connected to the internet
  5. Sneakernet the DVD or USB media to the secure location.
  6. Extract or copy SLES10-SP2-Updates or create a symlink (ln -s <mounted DVD or USB media>/SLES10-SP2-Updates /SLES10-SP2-Updates) to /SLES10-SP2-Updates

Updating the server(s) in the secure network

  1. Use rug to add a local installation source

    FILE: “rug sa -t zypp /SLES10-SP2-Updates/sles-10-architecture Updates”
  2. Use “rug sub Updates” to subscribe to the Updates channel
  3. Use “rug lu” to list the available updates
  4. Use “rug up” to install the available updates

Using an Installation server in the secured location

Follow the Prep work on a SLES server that is connected to the Internet section above.

Prep work on SLES server that is not connected to the Internet

  1. Create an installation server (HTTP, FTP or NFS) using YAST | Miscellaneous | Installation Server – http://www.novell.com/documentation/sles10/sles_admin/data/sec_deployment_remoteinst_instserver.html

Follow the Sneakernetting the updates from SMT section above and add the following steps.

  1. On the server not connected to the Internet, the root of the installation server can be determined by typing “grep ‘<directory>’ /etc/YaST2/instserver/instserver.xml”. The location is information between the directory tags
  2. Create a symbolic link from /SLES10-SP2-Updates to the root of the installation server.

Updating the server(s) in the secure network

  1. Use rug to add an installation source to the installation server

    HTTP: “rug sa -t zypp http:<installation server ip address>/<alias>/SLES10-SP2-Updates/sles-10-architecture Updates”

    FTP: “rug sa -t zypp ftp:<installation server ip address>/<alias>/SLES10-SP2-Updates/sles-10-architecture Updates”

    NFS: “rug sa -t zypp nfs:<installation server ip address>/<nfs export path>/SLES10-SP2-Updates/sles-10-architecture Updates”
  2. Use “rug sub Updates” to subscribe to the Updates channel
  3. Use “rug lu” to list the available updates
  4. Use “rug up” to install the available updates

If you are using zypper instead of rug to perform the updates

Replace the Updating the server(s) in the secure network sections above with the following steps.

  1. Use zypper to add an installation source to the installation server

    FILE: “zypper sa file://SLES10-SP2-Updates/sles-10-architecture

    HTTP: “zypper sa http:<installation server ip address>/<alias>/SLES10-SP2-Updates/sles-10-architecture

    FTP: “zypper sa ftp:<installation server ip address>/<alias>/SLES10-SP2-Updates/sles-10-architecture

    NFS: “zypper sa nfs:<installation server ip address>/<nfs export path>/SLES10-SP2-Updates/sles-10-architecture
  2. Use “zypper lu” to list the available updates
  3. Use “zypper up” to install the available updates
VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Tags:
Categories: SUSE Linux Enterprise Server, Technical Solutions

Disclaimer: As with everything else at SUSE Conversations, this content is definitely not supported by SUSE (so don't even think of calling Support if you try something and it blows up).  It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.

1 Comment

  1. By:jalmda

    I was happy to see this, until I tried it. –multi-volume on tar files are limited to shorter file names, and so for SLES10 SP3 we find

    tar -c -ML 4718592 -vf disk1.tar /mnt/repo
    Prepare volume #2 for `disk1.tar’ and hit return: n disk2.tar
    Prepare volume #2 for `disk2.tar’ and hit return:
    tar: mnt/repo/$RCE/SLE10-SDK-SP3-Updates/sles-10-x86_64/rpm/src/mozilla-xulrunner190-1.9.0.18-0.4.1.src.rpm: file name too long to be stored in a GNU multivolume header
    tar: Error is not recoverable: exiting now

    Need to use star, as in

    star -c -C=/path/to/repo -multivol -tsize=4450M f=repo1.tar f=repo2.tar f=repo3.tar f=repo4.tar f=repo5.tar repo

Comment

RSS