SUSE Linux Enterprise Server

From MicroFocusInternationalWiki
Revision as of 10:19, 26 September 2006 by Jdebaer (Talk | contribs) (High-Availability Storage Foundation)

Jump to: navigation, search

Welcome to the SUSE Linux Enterprise Server Wiki!!

As already mentioned on the wiki main page, please feel free to join in. You can read anything in here without logging in, but if you feel like commenting on something, or starting a new topic, you'll need to use a Novell Login account (which you'll be prompted to create if you don't already have one). If you are unfamiliar with using Wiki's in general, please visit Novell Wiki or the grandaddy wiki info site for some background info.

Several areas of the Novell webspace provide information regarding the SUSE LINUX Enterprise Server (commonly abbreviated as SLES).

General SLES Information

Some general information on SLES is available at the Novell and Linux page.


SLES 10 is released, and can be downloaded here:

New with SLES 10 is the Novell Customer Center. See Getting to know the Novell Customer Center

High-Availability Storage Foundation

The High-Availability Storage Foundation (HASF) is a combination of several Open Source projects, plus Novell donated source code, integration tested and delivered in SLES 10. The HASF allows for the creation of a server and storage infrastructure that enables service-level availability by running individual services in cluster-managed relocatable virtual machines.

Documentation :

  • Exploring the High-Availability Storage Foundation : download here
    • Known issues regarding this document
      • Initial node2 NTP time grab might fail
        • In the document we ask you to make node1 come up after node2, because node2 is running the iSCSI target. Making the nodes (re)boot in this order makes sure that node1 finds the iSCSI target on node2. However, as a result of this, node2 (NTP client) cannot grab it's initial time from node1 (NTP server). Normally this should not be a problem, since a mere reboot of both systems should not cause a large time drift. However, if the hardware clock of node2 is not ok, then node2 can come up with a time drift. When this time drift is too big, then this will cause the STONITH operation to fail when you perform the final test of killing heartbeat on node1. Solution is to run "/etc/init.d.ntp restart" on node2 right before killing the heartbeat on node1. In "Conquering the High-Availability Storage Foundation" we will probably reverse client and server to resolve this potential issue.
  • Conquering the High-Availability Storage Foundation : to be released.
  • Linux-World demo : four-node Cluster hosting two Virtual Machines.



The current version of SLES9 is SLES9 SP3.

SLES 9 is available for a number of architectures and contains numerous packages (see the package list).

For a current installation, both the general release CDs and the current service pack CDs are needed. There are no overlay images available for SLES9.

Download SLES 9

Links to the unpatched ISOs can be found on the SLES 9 Download page.

SLES 9 Support Packs

Links to the support pack ISOs can also be found on the SLES 9 Download page.



  • Newicon.gif Securing SLES9 - Details some very basic actions you can take to make SLES9 even more secure.
  • Deploying SUSE Linux using autoyast: download here


SLES8 is an older version of SLES which is still supported.

Support for SLES

There are a number of support options for SLES.

Certifications and hardware compatibility

Related products