1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. LINUX ENTERPRISE SERVER 11 - DEPLOYMENT
  6. Deployment manual

Novell LINUX ENTERPRISE SERVER 11 - DEPLOYMENT Deployment Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
SUSE Linux Enterprise
Server
11
March 23, 2009
Deployment Guide
www.novell.com

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the LINUX ENTERPRISE SERVER 11 - DEPLOYMENT and is the answer not in the manual?

Questions and answers

Related Manuals for Novell LINUX ENTERPRISE SERVER 11 - DEPLOYMENT

Summary of Contents for Novell LINUX ENTERPRISE SERVER 11 - DEPLOYMENT

  • Page 1 SUSE Linux Enterprise Server www.novell.com Deployment Guide March 23, 2009...
  • Page 2 That this manual, specifically for the printed format, is reproduced and/or distributed for noncommercial use only. The express authorization of Novell, Inc must be obtained prior to any other use of any manual or part thereof. http://www.novell For Novell trademarks, see the Novell Trademark and Service Mark list .com/company/legal/trademarks/tmlist.html.

  • Page 3: Table Of Contents

    Contents About This Guide 1 Planning for SUSE Linux Enterprise Server Considerations for Deployment of a SUSE Linux Enterprise Server ..Deployment of SUSE Linux Enterprise Server ....Running SUSE Linux Enterprise Server .
  • Page 4 The parmfile—Automating the System Configuration ..Using the vt220 Terminal Emulator ....Further In-Depth Information about IBM System z ... Part II Manual Deployment 5 Deployment Strategies Deploying up to 10 Workstations .
  • Page 5 9 Installing or Removing Software Definition of Terms ......Using the Qt Interface ..... . Managing Software Repositories and Services .
  • Page 6 15.3 Soft RAID Configuration ..... 1 6 Subscription Management 16.1 Using Kernel Parameters to Access an SMT Server ... 16.2 Configuring Clients Using AutoYaST Profile .
  • Page 7 21.3 For More Information ..... . 2 2 Automated Deployment of Preload Images 22.1 Deploying system manually from rescue image ... . 22.2 Automated Deployment with PXE Boot .

  • Page 9: About This Guide

    Internet. For an overview of the documentation available for your product and the latest docu- http://www.novell.com/documentation mentation updates, refer to or to the following section.
  • Page 10 Introduces basic concepts of system security, covering both local and network se- curity aspects. Shows how to make use of the product inherent security software like Novell AppArmor (which lets you specify per program which files the program may read, write, and execute) or the auditing system that reliably collects informa- tion about any security-relevant events.
  • Page 11 • To report bugs for a product component or to submit enhancements requests, please use https://bugzilla.novell.com/. If you are new to Bugzilla, you might find the Bug Writing FAQs helpful, available from the Novell Bugzilla home page. • We want to hear your comments and suggestions about this manual and the other documentation included with this product.
  • Page 12 • ls, --help: commands, options, and parameters • user: users or groups • Alt , Alt + F1 : a key to press or a key combination; keys are shown in uppercase as on a keyboard • File, File > Save As: menu items, buttons •...

  • Page 13: Planning For Suse Linux Enterprise Server

    Planning for SUSE Linux Enterprise Server The implementation of an operating system either in an existing IT environment or as a completely new rollout must be carefully prepared. SUSE Linux Enterprise Server 11 provides a variety of new features. It is impossible to describe all the new features here.

  • Page 14: Considerations For Deployment Of A Suse Linux Enterprise Server

    Novell AppArmor Harden your System with the Novell AppArmor technology. This service is de- scribed in depth in Part “Confining Privileges with Novell AppArmor” (↑Security Guide). AIDE This is an intrusion detection system that can be setup to detect unauthorized changes to the system.

  • Page 15: Deployment Of Suse Linux Enterprise Server

    Find the registration and patch support database at .com/linux/suse/portal/index.html. • Do you need help for your local installation? Novell provides training, support, and consulting for all topics around SUSE Linux Enterprise Server. Find more in- formation about this at http://www.novell.com/products/server/.

  • Page 16: Running Suse Linux Enterprise Server

    In addition to the plain software installation, you should consider training the end users of the systems as well as help desk staff. 1.3 Running SUSE Linux Enterprise Server The SUSE Linux Enterprise Server operating system is a well-tested and stable system. Unfortunately, this does not prevent hardware failures or other causes for downtime or data loss.

  • Page 17: Part I Architecture Specific Installation Considerations

    Part I. Architecture Specific Installation Considerations...

  • Page 19: Installation On X86, Amd64, Intel 64, And Itanium

    • You are familiar with the documentation for your system and the network on which it runs. • You have a basic understanding of Linux systems. For an overview of the documentation available for your product and the latest docu- mentation updates, refer to http://www.novell.com/documentation. Installation on x86, AMD64, Intel 64, and Itanium...

  • Page 20: System Requirements For Operating Linux

    If you want to be sure that a given computer configuration will work, find out which http:// computers have been certified by SUSE. Find a list of these computers at developer.novell.com/yessearch/Search.jsp. 2.2.1 Hardware for x86 Computers based on x86 constitute a cost-effective way of building high-performance systems.

  • Page 21: Hardware For Itanium

    Hard Disk Requirements The disk requirements depend largely on the installation. Commonly, you need more space than the installation software itself needs to have a system that works properly. Minimal requirements for different selections are: System Hard Disk Requirements Minimal X Window System 1.2 GB GNOME Desktop 3.2 GB...
  • Page 22 Memory A minimum of 1GB RAM per CPU socket is recommended. Hard Disk Requirements The disk requirements depend largely on the installation selected. Commonly, you need more space than the installed software itself needs to have a system that works properly.

  • Page 23: Installation Considerations

    Hard Disk Requirements The disk requirements depend largely on the installation selected. The required space for this architecture is similar to x86 but you should plan some space for compatibility libraries. Minimum requirements for different selections are: System Hard Disk Requirements Minimal X Window System 1.4 GB GNOME Desktop...

  • Page 24: Boot Methods

    2.3.2 Boot Methods Depending on the hardware used, the following boot methods are available for the first boot procedure prior to the installation of SUSE Linux Enterprise Server: Table 2.2 Boot Options Boot Option CD or DVD drive The simplest booting method. The system requires a locally- available CD-ROM or DVD-ROM drive for this.

  • Page 25: Installation Target

    The installation source is particularly easy to select if you configure an SLP server in the local network. For more information, see Section 14.2, “Setting Up the Server Holding the Installation Sources” (page 198). 2.3.4 Installation Target Most installations are to a local hard disk. Therefore, it is necessary for the hard disk controllers to be available to the installation system.

  • Page 26: Boot And Installation Media

    for autoyast2 in (page 285) and KIWI in Chapter 21, Automated Installation Chap- ter 17, KIWI (page 255). 2.4 Boot and Installation Media When installing the system, the media for booting and for installing the system may be different. All combinations of supported media for booting and installing may be used. 2.4.1 Boot Media Booting a computer depends on the capabilities of the hardware used and the availabil- ity of media for the respective boot option.

  • Page 27: Installation Procedure

    installation system after booting for installation. Several possibilities to provide the installation media to the system are available with SUSE Linux Enterprise Server. Installation from DVD All necessary data is delivered on the boot media. Depending on the selected instal- lation, a network connection or add on media may be necessary.

  • Page 28: Controlling The Installation

    2.5.2 Installing over the Network An installation server is required to perform the installation by using a network source. The procedure for installing this server is outlined in Section 14.2, “Setting Up the Server Holding the Installation Sources” (page 198). If you have an SLP server, select SLP as the installation source in the first boot screen.

  • Page 29: Installation Using A Serial Console

    2.6.2 Installation Using a Serial Console For this installation method, you need a second computer that is connected by a null modem cable to the computer on which to install SUSE Linux Enterprise Server. De- pending on the hardware, even the firmware or BIOS of the computer may already be accessible to the serial console.

  • Page 30: Dealing With Boot And Installation Problems

    2.6.4 Installation over VNC If you do not have direct access to the system, but want a graphical installation, install SUSE Linux Enterprise Server over VNC. This method is described in detail in Sec- tion 14.5.1, “VNC Installation” (page 222). As suitable VNC clients are also available for other operating systems, such as Microsoft Windows and MacOS, the installation can also be controlled from computers running those operating systems.

  • Page 31: Problems Installing

    The Computer Hangs Change the console on your computer so that the kernel outputs are visible. Be sure to check the last outputs. This is normally done by pressing Ctrl + Alt + F10 . If you are unable to resolve the problem, consult the SUSE Linux Enterprise Server support staff.
  • Page 32 • Check the system messages on a console in the installation system by entering the command dmesg. 2.7.3 Redirecting the Boot Source to the Boot DVD To facilitate the installation process and avoid accidental installations, the default setting on the installation DVD for SUSE Linux Enterprise Server is that your system is booted from the first hard disk.

  • Page 33: Installation On Ibm Power

    If you want to be sure that a given computer configuration will work, find out which http:// computers have been certified by SUSE. Find a list of these computers at developer.novell.com/yessearch/Search.jsp. pSeries and System p Models These systems are operated with a PPC64 kernel.

  • Page 34: Software Requirements

    eServer p5, System p, OpenPower, and 505, 510, 520, 550, 560Q, 570, 570+, 575, ATX Server models 575+, 590, 595, 710, 720, 185 ATX Workstation All POWER3 and RS64–based models that were supported by SUSE Linux Enterprise Server 9 are no longer supported. A standard installation requires at least 256 MB of RAM.

  • Page 35: Preparation

    The following links are interesting for the maintenance of an installation: • http://www.novell.com/suselinuxportal is an effective help tool for assisting customers in solving problems. A corresponding article is published whenever SUSE discover that a special case could lead to serious problems. Search the portal using keywords like PPC or POWER.
  • Page 36 • suse-security-announce — The SUSE mailing list exclusively for secu- rity alerts. 3.2.1 Preparing for Installation on IBM eServer p5, System p, and OpenPower Models This section covers the preparatory steps for installing SUSE® Linux Enterprise Server on IBM eServer p5 systems. It explains the installation from a built-in CD-ROM drive and over the network.
  • Page 37 Assigning an Installation Device to an LPAR SUSE Linux Enterprise Server can be installed from a CD-ROM or DVD drive or using a network installation source. Make the CD-ROM, DVD drive, or network device available to the LPAR to install. Figure 3.1 HMC: Server Management—Properties Procedure 3.1 Assigning a CD-ROM or DVD Drive to an LPAR 1 Open the HMC application and go to Server and Partition >...
  • Page 38 Figure 3.2 HMC: Managed System I/O Devices Now insert the SUSE Linux Enterprise Server CD1 or DVD1 in the drive. Procedure 3.2 Assigning a Network Device to an LPAR 1 Open the HMC application and go to Server and Partition > Server Management. 2 From the available servers, open the server and partition to install.

  • Page 39: Starting The Installation

    Create a network installation source if SUSE Linux Enterprise Server should be installed on a number of partitions. This eliminates the need to change CDs during installation. The same source can also be used for concurrent installation of various systems. The configuration of the network installation source is described in Section 14.2.1, “Setting Up an Installation Server Using YaST”...
  • Page 40 Select Console Select Boot Options --------------------------------------------------------------------- Navigation Keys: X = eXit System Management Services --------------------------------------------------------------------- Type the number of the menu item and press Enter or select Navigation Key:5 Select 1. Select Install/Boot Device to set the Install Device. Go to 7. List all Devices to see the list of available devices: Version SF220_011 SMS 1.5 (c) Copyright IBM Corp.
  • Page 41 Information Normal Mode Boot Service Mode Boot -------------------------------------------------------------------------- Navigation keys: M = return to Main Menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------- Type the number of the menu item and press Enter or select Navigation Key: Choose 2.

  • Page 42: Additional Steps

    Additional Steps Proceed as described in Chapter 6, Installation with YaST (page 89) to begin installing the software with linuxrc and YaST. 3.2.2 Preparing for Installation on IBM pSeries Models This section covers the preparatory steps for installing SUSE® Linux Enterprise Server on pSeries systems.
  • Page 43 • The HMC terminal used for the input during the installation is a VT320 emulation. This emulation can lead to strange effects with some applications. If possible, use an XTerm for communicating with the LPAR. Hard Disk Space Make sure that you have sufficient hard disk space for installing SUSE Linux Enterprise Server.
  • Page 44 Figure 3.3 Entering the System Firmware 1 = SMS Menu 5 = Default Boot List 8 = Open Firmware Prompt 6 = Stored Boot List memory keyboard network scsi speaker Press F1 or 1 while the SCSI devices are checked. Select 6 MultiBoot to enter the Multiboot dialog.
  • Page 45 Select 3 to set the install device. A list of available devices is displayed. See Figure 3.5, “Installing the Operating System” (page 33). Figure 3.5 Installing the Operating System Install Operating System Device Device Number Name Diskette SCSI Tape id=0 ( slot=50322f5a ) SCSI CD-ROM id=1 ( slot=50322f5a ) Ethernet ( Integrated )
  • Page 46 To install from a network source (see Section “Setting Up the Installation Source” (page 31)), append manual to the kernel to install. For an installation over VNC, append the parameters vnc=1 and vncpassword=password to install. Read more about VNC in Section 14.1.1, “Simple Remote Installation via VNC—Static Network Configuration”...
  • Page 47 Notes and Information Introductory Information: • JSxx Blades Site: https://www-304.ibm.com/systems/support/ supportsite.wss/brandmain?brandind=5000020 Preparing the System for Boot Preparing to Boot from the CD-ROM Drive Perform the steps described in this section if an installation from CD-ROM is desired. Assign the CD-ROM drive to the Blade chosen for installation by connecting with a Web browser to a BladeCenter Management Module then logging in.
  • Page 48 Rebooting and Connecting to the Console of the JSxx Blade Reboot the JSxx Blade from the item Power/Restart of the Blade Tasks menu in the BladeCenter Management Module. A table appears, showing the power status of the blades in the Pwr column. Mark the check box of the desired blade and restart it with Power On Blade.
  • Page 49 blade[11] blade[13] system> The command target is then determined. To work, for example, with blade number 9, enter env -T system:blade[9]. Connect with the console of the JSxx Blade over Serial over LAN (SOL) with the command console. system> env -T system:blade[9] system:blade[9]>...

  • Page 51: Installation On Ibm System Z

    Installation on IBM System z This chapter describes the procedure for preparing the installation of SUSE® Linux Enterprise Server on IBM System z systems. It provides all information needed to prepare the installation on the LPAR and z/VM side. 4.1 General Information and Requirements This section gives basic information about the system requirements, like supported hardware, level of MicroCode, and software.

  • Page 52: Memory Requirements

    • IBM Series z9 (z9-BC) 2096 • IBM Series z10 (z10-EC) 2097 • IBM Series z10 (z10-BC) 2098 Memory Requirements Different installation methods have different memory requirements during installation. After installation is completed, the system administrator may reduce memory to the desired size.
  • Page 53 Network Connection A network connection is needed to communicate with your SUSE Linux Enterprise Server system. This can be one or more of the following connections or network cards: • OSA Express Ethernet (including Fast and Gigabit Ethernet) • HiperSockets or Guest LAN •...
  • Page 54 VM/ESA and z/VM z/VM 5.2 z/VM 5.3 z/VM 5.4 Negotiate the order of installation with your IBM support, because it might be necessary to activate the VM APARs before installing the new MicroCode levels. Software To install SUSE Linux Enterprise Server via non-Linux–based NFS or FTP, you might experience problems with NFS or FTP server software.

  • Page 55: Installation Types

    TIP: Additional Information Consult the README located in the highest directory of DVD 1 of your SUSE Linux Enterprise Server before installing SUSE Linux Enterprise Server on IBM System z. This file completes the documentation presented in this book. 4.1.2 Installation Types This section gives an overview of the different types of installation possible with SUSE Linux Enterprise Server for IBM System z.

  • Page 56: Ipl Options

    4.1.3 IPL Options This section provides the information needed to do an IPL for the first installation. Depending on the type of installation, different options need to be used. The channel- attached tape, VM reader, and load from CD-ROM or server options are discussed. Installing the software packages, which is done over the network, does not require the IPL medium.

  • Page 57: The Iocds

    CD ROM or Server from the action menu. Provide information as requested on subse- quent windows. Load from SCSI-Attached DVD To IPL from a SCSI DVD, you need access to an FCP adapter connected to a DVD drive. You need values like the WWPN and LUN from the SCSI drive. For details, see Section “IPL from FCP-Attached SCSI DVD”...

  • Page 58: Preparing For Installation

    Network cards like OSA-Express can be used in two different modes. These modes are known as QDIO and non-QDIO mode. Define these modes in the IOCDS by using the TYPE statement. QDIO mode is much faster than non-QDIO mode, but uses three device addresses instead of two in non-QDIO.
  • Page 59 conveniant if you have restrictions setting up an installation server providing installation media over your network. The prerequisite is an FCP-attached SCSI DVD Drive. Using a Linux Workstation or SUSE Linux Enterprise Server DVD If you have a Linux workstation running in your computer environment, use the work- station to provide the installation data to the IBM System z installation process by NFS or FTP.
  • Page 60 SUSE Linux Enterprise Server on DVD DVD1 of the SUSE Linux Enterprise Server for IBM System z contains a bootable Linux image for Intel-based workstations as well as an image for System z. For Intel-based workstations, boot from this DVD, answer the questions regarding your language and keyboard layout, and select Start rescue system.
  • Page 61 With NFS Refer to the documentation provided with the third party product that enables NFS server services for your Windows workstation. The DVD-ROM drive containing the SUSE Linux Enterprise Server DVDs must be in the available NFS path. With FTP Refer to the documentation provided with the third party product that is enabling FTP server services on your Windows workstation.
  • Page 62 • z/VM Installation Procedure 4.1 Installation Overview of LPAR Installation 1 Prepare the devices needed for installation. See Section “LPAR Installation” (page 51). 2 IPL the installation system. See Section “LPAR Installation” (page 54). 3 Configure the network. See Section 4.2.5, “Network Configuration” (page 59).

  • Page 63: Lpar Installation

    4.2.3 Preparing the IPL of the SUSE Linux Enterprise Server Installation System LPAR Installation Configure your IBM System z system to start in ESA/S390 or LINUX only mode with an appropriate activation profile and IOCDS. Consult IBM documentation for more about how to achieve this.
  • Page 64 z/VM Installation Adding a Linux Guest The first step is to attach and format one or multiple DASDs in the system to be used by the Linux guest in z/VM. Next, create a new user in z/VM. The example shows the directory for a user LINUX1 with the password LINPWD, 256 MB of memory (extend- able up to 1024 MB), 32 MB of expanded RAM (XSTORE), some minidisks (MDISK), two CPUs and an OSA QDIO device.
  • Page 65 Example 4.5 Configuration of a z/VM Directory USER LINUX1 LINPWD 256M 1024M G *____________________________________________ * LINUX1 *____________________________________________ * This VM Linux guest has two CPUs defined. CPU 01 CPUID 111111 CPU 02 CPUID 111222 IPL CMS PARM AUTOCR IUCV ANY IUCV ALLOW MACH ESA 10 OPTION MAINTCCW RMCHINFO...
  • Page 66 Assign the directories to the guest with DISKMAP USER DIRECT A. You can now log in on the guest as user LINUX1. If you do not have the dirmaint option available, refer to the IBM documentation to set up this user. Proceed with Section “z/VM Installation”...
  • Page 67 There are many ways to create an IPLable tape. One is to copy the files: /boot/s390x/tapeipl.ikr /boot/s390x/parmfile /boot/s390x/initrd as binary files from DVD 1 (for example, using FTP from a Linux workstation). Name them SLES11 IMAGE SLES11 PARM SLES11 INITRD and write them onto a tape with the REXX from the example.
  • Page 68 IPL from the z/VM Reader You need a working TCP/IP connection and an FTP client program within your newly defined z/VM guest to transfer the installation system via FTP. Setting up TCP/IP for z/VM is beyond the scope of this manual. Refer to the appropriate IBM documentation. Log in as the z/VM Linux guest to IPL.
  • Page 69 Example 4.7 Transferring the Binaries via FTP FTP 192.168.0.3 VM TCP/IP FTP Level 530 Connecting to 192.168.0.3, port 21 220 ftpserver FTP server (Version wu-2.4.2-academ[BETA-18](1) Fri Jan 30 14:58:32 GMT 2009) ready. USER lininst 331 Password required for lininst PASS ****** 230 User lininst logged in.
  • Page 70 Use the REXX script sles11.exec you just downloaded to IPL the Linux installation system. This script loads the kernel, parmfile, and the initial RAM disk into the reader for IPL. Example 4.8 SLES11 EXEC /* REXX LOAD EXEC FOR SUSE LINUX S/390 VM GUESTS /* LOADS SUSE LINUX S/390 FILES INTO READER SAY '' SAY 'LOADING SLES11 FILES INTO READER...'...

  • Page 71: Network Configuration

    4.2.5 Network Configuration Wait until the kernel has completed its start-up routines. If you are installing in basic mode or in an LPAR, open the Operating System Messages on the HMC or SE. First, choose Start Installation or System in the linuxrc main menu then Start Installation or Update to start the installation process.
  • Page 72 common “layer 3” mode. The card mode affects all systems that share the device includ- ing systems on other LPARs. If in doubt, please specify 2 for compatibility with the default mode used by other operating systems such as z/VM and z/OS. Consult with your hardware administrator for further information on these options.
  • Page 73 Now a summary is displayed. Confirm whether your input is correct. Before the network is started, enter a password that is valid only during the installation. After having IPLed the installed system, enter the real root password. With all basic parameters set up, the network is started. Check the output of ifconfig, which should contain two entries: a loopback (lo) connection and one connection (eth0, ctc0, escon0, iucv0, or hsi0) with correct settings.
  • Page 74 2 Start a VNC client application on your client system. Either use vncviewer or the VNC Java client and a Java-enabled Web browser. 3 Enter the IP address and the display number of the SUSE Linux Enterprise Server installation system when prompted to do so. If you connect via a Java-enabled browser, enter a URL containing the IP address of the installation system and the appropriate port number in the format: http://<IP address of installation system>:5801/...

  • Page 75: Network Connection Types

    Initiating the Installation for SSH To connect to an installation system with the name earth using SSH, execute ssh -X earth. If your workstation runs on Microsoft Windows, use the ssh and telnet client http://www.chiark and terminal emulator putty, which is available from .greenend.org.uk/~sgtatham/putty/.
  • Page 76 Example 4.11 Supported Network Connection Types and Driver Parameters Choose the network device. 1) IBM parallel CTC Adapter (0.0.0600) 2) IBM parallel CTC Adapter (0.0.0602) 3) IBM parallel CTC Adapter (0.0.0604) 4) IBM Hipersocket (0.0.0700) 5) IBM Hipersocket (0.0.0701) 6) IBM Hipersocket (0.0.0702) 7) IBM OSA Express Network card (0.0.050c) 8) IBM OSA Express Network card (0.0.050d) 9) IBM OSA Express Network card (0.0.050e)
  • Page 77 Example 4.12 Network Device Name Automatic configuration via DHCP? 1) Yes 2) No > 2 Enter your IP address > 192.168.0.20 Enter your netmask. For a normal class C network, this is usually 255.255.255.0 [255.255.255.0] > 255.255.255.0 Enter the IP address of the gateway. Leave empty if you don't need one >...
  • Page 78 Example 4.13 Network Device Driver Parameters Detecting and loading network drivers netiucv.8db02b: driver initialized Choose the network device. 1) IBM OSA Express Network card (0.0.09a0) 2) IBM OSA Express Network card (0.0.09a1) 3) IBM OSA Express Network card (0.0.09a2) 4) IBM OSA Express Network card (0.0.0600) 5) IBM OSA Express Network card (0.0.0601) 6) IBM OSA Express Network card (0.0.0602) 7) IBM IUCV...

  • Page 79: The Parmfile-Automating The System Configuration

    Example 4.14 Network Device Name Fully qualified hostname> earth.cosmos.com Automatic configuration via DHCP? 1) Yes 2) No > 2 Enter your IP address> 192.168.0.20 Enter your netmask. For a normal class C network, this is usually 255.255.255.0 [255.255.255.0]> 255.255.255.0 If you need a gateway to reach the server, enter the IP address of the gateway.

  • Page 80: General Parameters

    Hostname=s390zvm01.suse.de HostIP=10.11.134.65 TIP: Using IPv6 during the Installation By default you can only assign IPv4 network addresses to your machine. To enable IPv6 during installation, enter one of the following parameters at the bootprompt: ipv6=1 (accept IPv4 and IPv6) or ipv6only=1 (accept IPv6 only).

  • Page 81: Configuring The Network Interface

    Autoinstallation. For more information about AutoYaST, refer to Chapter 21, Automated Installation (page 285). 4.4.2 Configuring the Network Interface IMPORTANT: Configuring the Network Interface All settings discussed here only apply to the network interface used during in- stallation. Configure additional network interfaces in the installed system by following the instructions given in Section “Configuring a Network Connection Manually”...
  • Page 82 Pointopoint=192.168.55.20 OsaInterface=<lcs|qdio> OsaMedium=<eth|tr> For osa network devices, specify the host interface (qdio or lcs) and the phys- ical medium (eth for ethernet or tr for token ring). Layer2=<0|1> For osa QDIO ethernet devices, specify whether to enable OSI Layer 2 support. PortNo=<0|1>...
  • Page 83 ReadChannel stands for the channel number used in this setup. A second port number can be derived from this by adding one to ReadChannel. Portnumber is used to specify the relative port. • Interface iucv: IUCVPeer=PARTNER Enter the name of the peer machine. •...
  • Page 84 If an ftp or smb URL is given, specify the username and password with the URL. These parameters are optional and anonymous or guest login is assumed if they are not given. Install=ftp://user:password@server/directory/DVD1/ In case of a Samba or CIFS installation, you can also specify the domain that should be used: Install=smb://workdomain;user:password@server/directory/DVD1/ UseSSH=1 UseVNC=1 Display_IP=192.168.42.42...

  • Page 85: Using The Vt220 Terminal Emulator

    To receive potential error messages on the console, use linuxrclog=/dev/console Example 4.15 Parmfile for Installation with NFS, VNC, and IUCV and AutoYaST with HTTP ramdisk_size=131072 root=/dev/ram1 ro init=/linuxrc TERM=dumb instnetdev=iucv iucvpeer=ROUTER01 pointopoint=192.168.0.1 hostip=192.168.0.2 nameserver=192.168.0.3 install=nfs://192.168.0.4/SLES/SLES-11-s390x/DVD1 autoyast=http://192.168.0.5/autoinst.xml linuxrclog=/dev/console usevnc=1 vncpassword=testin Example 4.16 Parmfile for Installation with NFS, SSH, and HSI and AutoYaST with ramdisk_size=131072 root=/dev/ram1 ro init=/linuxrc TERM=dumb AutoYast=nfs://192.168.1.1/autoinst/s390.xml Hostname=zseries.example.com HostIP=192.168.1.2...

  • Page 86: Further In-Depth Information About Ibm System Z

    Save the file and run telinit q to pass the changes in /etc/inittab to init. The vt220 terminal should then be ready to use. If not, try hitting Enter at the terminal until the login prompt appears. Make sure that you do not apply the changes as described above to a system that does not support vt220 terminal emulators.
  • Page 87 4.6.2 Hardware For a first glance at the technical details of some systems, refer to: • IBM System z10 Enterprise Class Technical Introduction (SG24-7515) • IBM System z9 Business Class Technical Introduction (SG24-7241) • IBM eServer zSeries 990 Technical Introduction (SG24-6863) •...
  • Page 88 • IBM System z9-109 Technical Introduction (SG26-6669) • IBM System z10 Enterprise Class Technical Guide (SG24-7516) http://www There also is a Redbook for Linux application development on .redbooks.ibm.com: • Linux on IBM eServer zSeries and S/390: Application Development (SG24-6807) 4.6.5 Advanced Configurations for Linux on IBM System z Refer to the following Redbooks, Redpapers, and links for some more complex IBM System z scenarios:...

  • Page 89: Part Ii Manual Deployment

    Part II. Manual Deployment...

  • Page 91: Deployment Strategies

    Deployment Strategies There are several different ways to deploy SUSE Linux Enterprise Server. Choose from various approaches ranging from a local installation using physical media or a network installation server to a mass deployment using a remote-controlled, highly-customized, and automated installation technique. Select the method that best matches your require- ments.
  • Page 92 Table 5.1 Installing from the SUSE Linux Enterprise Server Media Installation Source SUSE Linux Enterprise Server media kit Tasks Requiring Manual Inter- • Inserting the installation media action • Booting the installation target • Changing media • Determining the YaST installation scope •...

  • Page 93: Deploying Up To 100 Workstations

    Table 5.3 Installing from a Network Server Installation Source Network installation server holding the SUSE Linux Enterprise Server installation media Tasks Requiring Manual • Inserting the boot disk Interaction • Providing boot options • Booting the installation target • Determining the YaST installation scope •...
  • Page 94 Simple Remote Installation via VNC—Dynamic Network Configuration (page 83) Consider this approach in a small to medium scenario with dynamic network setup through DHCP. A network, network installation server, and VNC viewer application are required. Remote Installation via VNC—PXE Boot and Wake on LAN (page 84) Consider this approach in a small to medium scenario that should be installed via network and without physical interaction with the installation targets.
  • Page 95 Table 5.4 Simple Remote Installation via VNC—Static Network Configuration Installation Source Network Preparations • Setting up an installation source • Booting from the installation media Control and Monitoring Remote: VNC Best Suited For small to medium scenarios with varying hardware Drawbacks •...
  • Page 96 Details Section 14.1.2, “Simple Remote Installation via VNC—Dynamic Network Configuration” (page 191) Table 5.6 Remote Installation via VNC—PXE Boot and Wake on LAN Installation Source Network Preparations • Setting up the installation source • Configuring DHCP, TFTP, PXE boot, and WOL •...
  • Page 97 • Low bandwidth connections to target Drawbacks • Each machine must be set up individually • Physical access is needed for booting Details Section 14.1.4, “Simple Remote Installation via SSH—Static Network Configuration” (page 194) Table 5.8 Remote Installation via SSH—Dynamic Network Configuration Installation Source Network Preparations...
  • Page 98 • Configuring DHCP, TFTP, PXE boot, and WOL • Booting from the network Control and Monitoring Remote: SSH Best Suited For • Small to medium scenarios with varying hardware • Completely remote installs; cross-site deployment • Low bandwidth connections to target Drawbacks Each machine must be set up individually Details...
  • Page 99 Best Suited For • Large scenarios • Identical hardware • No access to system (network boot) Drawbacks Applies only to machines with identical hardware Details Section 21.1, “Simple Mass Installation” (page 285) Table 5.11 Rule-Based Autoinstallation Installation Source Preferably network Preparations •...

  • Page 100: Deploying More Than 100 Workstations

    Details Section 21.2, “Rule-Based Autoinstallation” (page 297) 5.3 Deploying More than 100 Workstations Most of the considerations brought up for medium installation scenarios in Section 5.1, “Deploying up to 10 Workstations” (page 79) still hold true for large scale deployments. However, with a growing number of installation targets, the benefits of a fully automated installation method outweigh its disadvantages.

  • Page 101: Installation With Yast

    Installation with YaST After your hardware has been prepared for the installation of SUSE® Linux Enterprise Server as described in the Part I, “Architecture Specific Installation Considerations” (page 5) and after the connection with the installation system has been established, you are presented with the interface of SUSE Linux Enterprise Server's system assistant YaST.
  • Page 102 SUSE Linux Enterprise Server supports several different boot options from which you can choose depending on the hardware available and on the installation scenario you prefer. Booting from the SUSE Linux Enterprise Server media is the most straightforward option, but special requirements might call for special setups: Table 6.1 Boot Options Boot Option...

  • Page 103: The Installation Workflow

    6.1.1 Installing from a Network Server Using If your network setup supports OpenSLP and your network installation source has been configured to announce itself via SLP (described in Section 14.2, “Setting Up the Server Holding the Installation Sources” (page 198)), boot the system, press F4 in the boot screen and select SLP from the menu.

  • Page 104: Ibm Power: System Start-Up For Network Installation

    installation scope. In the non-interactive installation phase the software is installed and the system is prepared for the first boot. Upon finishing the installation the machine reboots into the newly installed system and starts the final system configuration. In this stage, network and Internet access, as well as hardware components such as printers, are set up.

  • Page 105: System Start-Up For Installation

    TIP: IBM System z: The Next Steps To install, follow the description of the installation procedure with YaST starting from Section 6.7, “Welcome” (page 98). 6.5 System Start-Up for Installation You can install SUSE Linux Enterprise Server from local installation sources, such as the SUSE Linux Enterprise Server CDs or DVD, or from network source of an FTP, HTTP, NFS, or SMB server.
  • Page 106 Firmware Test Starts a BIOS checker that validates ACPI and other parts of your BIOS. Memory Test Tests your system RAM using repeated read and write cycles. Terminate the test by rebooting. For more information, see Section “Fails to Boot” (Chapter 7, Common Problems and Their Solutions, ↑System Analysis and Tuning Guide).
  • Page 107 F3 Video Mode Select various graphical display modes for the installation. Select Text Mode if the graphical installation causes problems. F4 Source Normally, the installation is performed from the inserted installation medium. Here, select other sources, like FTP or NFS servers. If the installation is carried out in a network with an SLP server, select an installation source available on the server with this option.
  • Page 108 6.6.1 Providing Data to Access an SMT Server By default updates for SUSE Linux Enterprise Server are delivered by the Novell Customer Center. If your network provides a so called SMT server to provide a local update source, you need to equip the client with the server's URL. Client and server communicate solely via HTTPS protocol, therefore you also need to enter a path to the server's certificate if the certificate was not issued by a certificate authority.
  • Page 109 The data supportconfig (see Chapter 2, Gathering System Information for Support (↑Administration Guide) for more information) gathers is sent to the Novell Customer Center by default. It is also possible to set up a local server collecting this data. If such...

  • Page 110: Welcome

    a server is available on your network, you need to equip the client with the server's URL. This information has to be entered at the boot prompt. supporturl URL of the server. The URL has the format http://FQN/Path/ FQN has to be full qualified hostname of the server, Path has to be replaced with the location on the server.

  • Page 111: Ibm System Z: Hard Disk Configuration

    Figure 6.2 Welcome 6.8 IBM System z: Hard Disk Configuration When installing on IBM System z platforms, the language selection dialog is followed by a dialog to configure the attached hard disks. Select DASD, Fibre Channel Attached SCSI Disks (ZFCP), or iSCSI for installation of SUSE Linux Enterprise Server. After selecting Configure DASD Disks, an overview lists all available DASDs.
  • Page 112 Figure 6.3 IBM System z: Selecting a DASD Now specify the DASDs to use for the installation by selecting the corresponding entries in the list then clicking Select or Deselect. After that, activate and make the DASDs available for the installation by selecting Perform Action > Activate. See Figure 6.4, “IBM System z: Activating a DASD”...

  • Page 113: Installation Mode

    available on the system. In this dialog, select Add to open another dialog in which to enter ZFCP parameters. To make a ZFCP disk available for the SUSE Linux Enterprise Server installation, choose an available Channel Number from the drop-down list. Get WWPNs (World Wide Port Number) and Get LUNs (Logical Unit Number) return lists with available WWPNs and FCP-LUNs, respectively, to choose from.
  • Page 114 Figure 6.5 Installation Mode This screen also offers to include add-on products during the installation. To include such products, check Include Add-On Products from Separate Media. An add-on product can include extensions, third-party products or additional software for your system. Click Next to proceed.

  • Page 115: Clock And Time Zone

    configured. If the add-on product is available on removable media, the system automat- ically mounts the media and reads it's contents. If the add-on product is available on hard disk, choose Hard Disk to install from an unmounted hard drive, or Local Direc- tory/Local ISO Image if it is located in the file system.
  • Page 116 the drop down lists for Region and Time Zone. When using the map, point the cursor at the rough direction of your region and left-click to zoom. Now choose your country or region by left-clicking. Right-click to return to the world map. Figure 6.6 Clock and Time Zone To set up the clock, choose whether the Hardware Clock is Set to UTC.

  • Page 117: Server Base Scenario

    6.11 Server Base Scenario In SUSE Linux Enterprise Server, you can choose from three base scenarios. The se- lected scenario affects the package selection. Physical Machine Choose this scenario when installing on a “real” machine without XEN. Virtual Machine Choose this scenario when installing in a virtual machine, such as XEN. XEN Virtualization Host Choose this scenario when installing on a machine, that should serve as a XEN host.
  • Page 118 changed in the Overview tab, advanced options are available on the Experts tab. To modify the suggestions, either click Change and select the category to change or click on one of the headlines. After configuring any of the items presented in these dialogs, you are always returned to the Installation Settings window, which is updated accord- ingly.
  • Page 119 6.12.2 Booting (Expert) ►zseries: This module cannot be used to configure the boot loader (zipl) on the IBM System z platforms. ◄ YaST proposes a boot configuration for your system. Other operating systems found on your computer, such as Microsoft Windows or other Linux installations, will auto- matically be detected and added to the boot loader.
  • Page 120 Figure 6.9 Software Selection and System Tasks NOTE: Default Desktop The default desktop of SUSE Linux Enterprise Server is GNOME. To install KDE, click Software and select KDE Desktop Environment from Graphical Environment. 6.12.4 Language (Overview) Here you can change the system Language you defined in the first step of the installation. It is also possible to add additional languages.
  • Page 121 6.12.5 Add-On Products (Expert) If you added a source for an add-on media earlier, it appears here. Add, remove, or modify add-on products here if needed.This is the same configuration dialog as discussed earlier in Section 6.9.1, “Add-On Products” (page 102). 6.12.6 Keyboard Layout (Expert) To change the keyboard layout, select Keyboard Layout.

  • Page 122: Performing The Installation

    this may take some time. Select any item in the list and click Details to see detailed information about the selected item. Use Save to File to save a detailed list to either the local file system or a floppy. Advanced users can also change the PCI ID setup and Kernel Settings by choosing System Settings.
  • Page 123 6.13.1 IBM System z: IPLing the Installed System In most cases, YaST automatically reboots into the installed system on the IBM System z platform. Known exceptions to this are installations, where the bootloader resides on an FCP device in environments with LPAR on a machine older than z9 or with z/VM older than release 5.3.

  • Page 124: Installed System

    FC00 is an example address of the ZFCP adapter, replace this value with the correct address. 6.13.2 IBM System z: Connecting to the Installed System After IPLing the installed system, establish a connection with it to complete the instal- lation. The steps involved in this vary depending on the type of connection used at the outset.

  • Page 125: Configuration Of The Installed System

    A message in the 3270 terminal asks you to connect to the Linux system with an SSH client. This message is easily missed, however, because it is mixed with kernel messages and the terminal process might quit before you become aware of the message. Once the message appears, use SSH to log in to the Linux system as root.
  • Page 126 For verification purposes, the password for root must be entered twice. Do not forget the root password. Once entered, this password cannot be retrieved. When typing passwords, the characters are replaced by dots, so you do not see the string you are typing.
  • Page 127 Ethernet, OSA Gigabit Ethernet, OSA Express Fast Ethernet, Escon, and IUCV). The YaST dialog simply displays the interface with its settings as already config- ured. Just confirm this dialog to continue. By default, Traditional Method without NetworkManager Applet is enabled. If desired, you can also use NetworkManager to manage all your network devices.
  • Page 128 DSL Connections, ISDN Adapters, and Modems If your computer is equipped with an internal DSL modem, an internal ADSL Fritz Card, an ISDN card or a modem, clicking on the respective headline opens the configuration dialog. Refer to Chapter 11, Accessing the Internet (page 159) for further information.
  • Page 129 Novell server will be connected. Upon this initial connect no data other than the ID of your product will be send to the Novell servers. In order to become entitled for support, make sure to check Registration Code. You will be prompted to enter the code when proceeding with Next.
  • Page 130 This option checks your repositories and adds newly available catalogs or removes obsolete ones. It does not touch manually added repositories. Proceed with Next. A connection with the Novell server is established. Follow the on- screen instructions to finish the registration.

  • Page 131: Online Update

    Interactive Use ask to open a pop-up menu where you can specify the path to the certifi- cate. Do not use this option with AutoYaST. Example Deactivate certificate installation Use done if either the certificate will be installed by an add-on product, or if you are using a certificate issued by an official certificate authority.
  • Page 132 DNS data. By default, an LDAP server is set up during the installation. If you decide against the use of an LDAP server, the YaST mail server module does not work because it depends on LDAP functionality. However, you can still set up a mail server on your system with the help of the Mail Transfer Agent module.
  • Page 133 Passwords are case-sensitive. Special characters (7-bit ASCII) and the digits 0 to 9 are allowed. Other special characters like umlauts or accented characters are not allowed. Passwords you enter are checked for weakness. When entering a password that is easy to guess, such as a dictionary word or a name, you will see a warning.

  • Page 134: Release Notes

    LDAP Users are administered centrally on an LDAP server for all systems in the network. More information is available in Section “Configuring an LDAP Client with YaST” (Chapter 4, LDAP—A Directory Service, ↑Security Guide). Users are administered centrally on a NIS server for all systems in the network. See Section “Configuring NIS Clients”...
  • Page 135 TIP: IBM System z: Hardware Configuration On the IBM System z, there is no display that would be supported by XFree. Accordingly, you do not find a Graphics Cards entry on these systems. You can skip any peripheral devices and configure them later, as described in Chapter 8, Setting Up Hardware Components with YaST (page 129).

  • Page 136: Graphical Login

    6.15 Graphical Login TIP: IBM System z: No Graphical Login The graphical login is not available on IBM System z platforms. SUSE Linux Enterprise Server is now fully installed and configured. Unless you enabled the automatic login function or customized the default runlevel, you should see the graphical login on your screen in which to enter a username and password to log in to the system.

  • Page 137: Updating Suse Linux Enterprise

    Updating SUSE Linux Enterprise SUSE® Linux Enterprise provides the option of updating an existing system to the new version without completely reinstalling it. No new installation is needed. Old data, such as home directories and system configuration, is kept intact. During the life cycle of the product, you can apply Service Packs to increase system security and correct software defects.

  • Page 138: Possible Problems

    /opt. You may also want to write the user data in /home (the HOME directories) to a backup medium. Back up this data as root. Only root has read permission for all local files. Before starting your update, make note of the root partition. The command df / lists Example 7.1, “List with df -h”...
  • Page 139 7.1.3 Updating with YaST Following the preparation procedure outlined in Section 7.1.1, “Preparations” (page 125), you can now update your system: 1 Optionally, prepare an installation server. For background information, see Sec- tion 14.2.1, “Setting Up an Installation Server Using YaST” (page 198).

  • Page 140: Installing Service Packs

    7.2 Installing Service Packs Use Service Packs to update a SUSE Linux Enterprise installation. There are several different ways in which you can apply a Service Pack. You can either update the existing installation or start a whole new installation using the Service Pack media. Possible scenarios for updating the system and setting up a central network installation source are described here.

  • Page 141: Setting Up Hardware Components With Yast

    Setting Up Hardware Components with YaST YaST allows you to configure hardware items at installation time as well as in the in- stalled system. Configure additional graphics cards and monitors, adjust mouse and keyboard settings and configure sound hardware. If you need printer or scanner support, use the appropriate YaST modules to configure these hardware items.

  • Page 142: Setting Up Graphics Card And Monitor

    8.2 Setting Up Graphics Card and Monitor After the installation you can change the configuration of your graphics system (graphics card and monitor) according to your needs. Such a change can be necessary because of accessibility issues or hardware upgrades. WARNING: Changing Monitor Frequencies Although there are safety mechanisms, you should still be very careful when manually changing the allowed monitor frequencies.

  • Page 143: Setting Up Keyboard And Mouse

    4 Test the new configuration before it is applied to the system. Click Ok to decide what to do with your configuration (Test, Save, or Cancel.) To activate a second monitor, proceed as follows: 1 In YaST, click Hardware > Graphics Card and Monitor. SaX2 checks the system resources and displays the Card and Monitor Properties dialog.
  • Page 144 1 In YaST, click Hardware > Keyboard Layout. The SaX2 configuration tool reads the system resources and displays the Keyboard Properties dialog. 2 Select your keyboard model from the Type list. 3 Select the country in the Layout list. 4 Depending on the country layout, you can choose a certain Variant. The selections are applied immediately for testing.
  • Page 145 NOTE: Configuring Console Keyboard Layout By clicking the Save button as described in Step 7 (page 132) the setup of the console keyboard layout takes place at the same time. If you want to change the console keyboard layout, either call yast keyboard (the text mode in- terface) or check the KEYTABLE and YAST_KEYBOARD settings in /etc/ sysconfig/keyboard.

  • Page 146: Setting Up Sound Cards

    Emulate Wheel with Mouse Button If your mouse does not have a scroll wheel but you want to use a similar function- ality, you can assign an additional button for this. Select the button to use. While pressing this button, any movement of the mouse is translated into scroll wheel commands.
  • Page 147 Advanced setup with possibility to change options Customize all settings manually. Click Next to continue. 3 In Sound Card Volume, test your sound configuration and make adjustments to the volume. You should start at about ten percent to avoid damage to your hearing or the speakers.

  • Page 148: Setting Up A Printer

    8.5 Setting Up a Printer YaST can be used to configure a local printer that is directly connected to your machine (normally with USB or parallel port) and to set up printing with network printers. It is also possible to share printers over the network and to add 3rd party “drivers” (PostScript Printer Description (PPD) files).
  • Page 149 to specify how the printer is connected to the machine. Then choose a suitable driver and specify a unique name for the printer queue in the Set Name field. A printer is never used directly, but always through a printer queue. This ensures that simultaneous jobs can be queued and processed one after the other.
  • Page 150 find PPD files at http://www.linuxfoundation.org/en/OpenPrinting/, the “OpenPrinting.org printer database”. When downloading PPD files from OpenPrint- ing.org, keep in mind that it always shows the latest Linux support status, which is not necessarily met by SUSE Linux Enterprise Server. Fine-tuning a Local Printer Configuration In order to adjust the default settings for paper size, resolution, media source and others, choose a printer from the list in the Printer Configurations view and click Configure.
  • Page 151 Using CUPS In a Linux environment CUPS is usually used to print via the network. The simplest setup is to only print via a single CUPS server which can directly be accessed by all clients. Check Do All Your Printing Directly via One Remote CUPS Server and specify the name or IP address of the server.

  • Page 153: Installing Or Removing Software

    Installing or Removing Software Change the software collection of your system using YaST. This YaST module is available in two toolkit flavors: Qt and ncurses; the Qt flavor is described here. In YaST's software management tool search for software components you want to add or remove.

  • Page 154: Using The Qt Interface

    Pattern A pattern is an installable list of packages needed for a special purpose. Examples are Base System, providing the openSUSE basic system, or GNOME Base System, containing all packages needed to run the GNOME Desktop environment. Package A package is a compressed file in rpm format that contains the files for a particular program.
  • Page 155 1 Click Software > Software Management to start the YaST package manager. 2 In the search field enter the name of the software you want to install (for example, xpdf, a lightweight PDF viewer) and press Enter . 3 The package is listed in the right frame. Select it for installation. Once done, you can search for more packages and select them for installation in one go.
  • Page 156 2 From the patterns select one or more patterns you are interested in. If you click on the name of a pattern, for example on Base Development, you see the packages it contains, in the right frame. If you activate it, the status markers at the beginning of the line will change: all packages get marked either with the status Keep or Install.
  • Page 157 Using the installation summary filter you see an overview of the packages you have scheduled for installation. It is convenient for double-checking if many packages are pending for installation. 9.2.2 Checking Software Dependencies The software of one package might only work properly if the required package is also installed.
  • Page 158 WARNING: Handling Package Conflicts Unless you are very experienced, follow the suggestions of YaST when handling package conflicts, because otherwise the stability and functionality of your system could be endangered by the existing conflict. Figure 9.1 Conflict Management of the Package Manager 9.2.3 Packages and Software Repositories If you want to search for packages originating from one particular software repository, use the Repositories filter.

  • Page 159: Managing Software Repositories And Services

    9.2.4 Removing Software If you want to remove software from the system, proceed as follows: 1 Make use of a search strategy explained in Section 9.2.1, “Installing Software” (page 142). 2 Depending on the search strategy, you can either select a complete set or single packages one by one.
  • Page 160 detect a key change, something could be wrong with the repository and you should better disable it as an installation source until you know the cause of the key change. To add product repositories either click Software Repositories directly in the Software pane of the YaST control center, or from within the Software Management, proceed as follows: 1 In the Software Management start screen, select Repositories from the upper left...

  • Page 161: Keeping The System Up-To-Date

    9.4 Keeping the System Up-to-date Novell offers a continuous stream of software security patches for your product. The updater applet informs you about the availability of patches and lets you easily install them with just a few clicks. 9.4.1 Using the KDE Updater Applet...

  • Page 162: Installing Patches

    Installing Patches Whenever the updater icon shows the availability of patches, left-click to open the software installation window. It lists the number of Security and Recommended patches available. While the security patches are installed by default, you can choose whether to install the recommended ones as well. Some patches, such as new kernel versions, require to restart your computer.
  • Page 163 Figure 9.3 KDE Updater Applet: Detailed Update View You will be prompted for the root password after having proceeded with Install. The updater performs the installation of the patches. See the system tray (KDE) or the noti- fication area (GNOME) for status messages and a progress meter. The YaST Online Update offers advanced features to customize the patch installation.
  • Page 164 sible for any potential problems arising from software installed from third party software repositories. The updater applet does not monitor repositories for new software versions by default. To enable this feature, open the configuration window as described in Section “Config- uring the Updater Applet”...
  • Page 165 The configuration dialog also offers to change the following settings: Back-End Choose between different back-ends. The Package Kit Plugin is used by default. If you prefer the ZYpp Plugin, make sure the package kde4-kupdateapplet-zypp is installed. Always Show Detailed View Activate this option when you prefer the detailed patch view that lists all patches available with short summaries rather than the simple view.
  • Page 166 Security patches are displayed first, trivial patches last. Click on a patch to see details, such as a description, version number, repository, and—if available—a link to bugzilla, the Novell bug tracking system. By default all patches are marked for installation. Uncheck the checkbox in front of a patch to prevent a patch from being installed.
  • Page 167 Figure 9.5 GNOME Software Update Viewer: Detailed Update View You will be prompted for the root password after having proceeded with Apply Updates or Update System. The updater performs the installation of the patches. After having finished the installation, choose whether to Install More Updates or whether to Close the Software Update Viewer.
  • Page 168 Figure 9.6 GNOME Updater Applet: Configuration The configuration dialog offers to change the following settings: Check for Updates Choose how often a check for updates is performed: Hourly, Daily, Weekly, or Never. Automatic Install Configure whether patches are installed automatically or not (default). Automatic installation can be chosen for either security patches only or for all patches.

  • Page 169: 0 Installing Add-On Products

    Installing Add-On Products Add-on products are system extensions. You can install a third-party add-on product or a special system extension of SUSE Linux Enterprise, for example, the SDK add-on or a CD with binary drivers. To install a new add-on, use Software > Add-On Products. You can select various types of product media, like CD, FTP, USB mass storage devices (such as USB flash drives or disks) or a local directory.

  • Page 170: Binary Drivers

    C, C++, Java, and most scripting languages. For your con- venience, SUSE Software Development Kit includes multiple Perl packages that are not included in SUSE Linux Enterprise. http://developer.novell.com/ndk/ For detailed information, refer to susesdk.htm. Use the YaST add-on installer and package manager to install SUSE Software Development Kit 10.

  • Page 171: 1 Accessing The Internet

    Accessing the Internet If you have chosen not to configure Internet access during the installation, you can perform this task at any time using YaST. How to configure your computer to access the Internet depends on your environment. If the computer you are installing is part of a network which already is connected to the Internet, the only thing to do is to link your machine into the network.
  • Page 172 11.1.1 Checklist DSL There are different types of DSL devices available that use different point-to-point protocol (PPP) methods: • a regular ethernet card connected to the external DSL modem uses PPP over Ethernet (PPPoE). In Austria the Point-to-Point Tunneling Protocol (PPTP) is used. With PPTP the external modem also has a static IP address.
  • Page 173 • Interface type (SyncPPP or RawIP). If unsure, select SyncPPP, because RawIP is only used in connection with certain telephone systems. • In case you got a static IP-address from your provider: local and remote IP-addresses for the dial-in server and the gateway. •...

  • Page 174: Internet Connection Via Network

    11.2 Internet Connection Via Network If your machine is part of a network which is already connected to the Internet, it is very easy to gain Internet access—just configure your network card and connect your machine to the existing network and you are done. This not only applies to large com- pany networks, but to small home networks as well.

  • Page 175: 2 Managing Users With Yast

    Managing Users with YaST During installation, you have chosen a method for user authentication . This method is either local (via /etc/passwd) or, if a network connection is established, via NIS, LDAP, Kerberos or Samba (see Section “User Authentication Method” (page 120).
  • Page 176 Figure 12.1 YaST User and Group Administration Depending on the set of users you choose to view and modify with the dialog (local users, network users, system users), the main window shows several tabs. These allow you to execute the following tasks: Managing User Accounts From the Users tab, create, modify, delete or temporarily disable user accounts as described in...

  • Page 177: Managing User Accounts

    path and access permissions for home directories in Section 12.4, “Changing Default Settings for Local Users” (page 175). Assigning Users to Groups Learn how to change the group assignment for individual users in Section 12.5, “Assigning Users to Groups” (page 176). Managing Groups From the Groups tab, you can add, modify or delete existing groups.
  • Page 178 NOTE: Changing User IDs of Existing Users File ownership is bound to the user ID, not to the user name. After a user ID change, the files in the user's home directory are automatically adjusted to reflect this change. However, after an ID change, the user does no longer own the files he created elsewhere in the file system unless you manually change the file ownership for those files.

  • Page 179: Additional Options For User Accounts

    8 Click Expert Options > Write Changes Now to save all changes without exiting the User and Group Administration dialog. Or click Finish to close the adminis- tration dialog and to save the changes. A newly added user can now log in to the system using the login name and password you created.
  • Page 180 12.3.1 Automatic Login and Passwordless Login If you use KDE or GNOME desktop environment you can configure Auto Login for a certain user as well as Passwordless Login for all users. Auto login causes a user to become automatically logged in to the desktop environment on boot. This functionality can only be activated for one user at a time.
  • Page 181 5 To enforce password rotation, set a Maximum Number of Days for the Same Password and a Minimum Number of Days for the Same Password. 6 To remind the user to change his password before it expires, set a number of Days before Password Expiration to Issue Warning.
  • Page 182 WARNING: Security Restrictions Encrypting a user's home directory does not provide strong security from other users. If strong security is required, the system should not be physically shared. Find background information about encrypted home directories and which actions to take for stronger security in Section “Using Encrypted Home Directories” (Chapter 11, Encrypting Partitions and Files, ↑Security Guide).
  • Page 183 4 Apply your settings with OK. 5 Enter the user's current login password to proceed if YaST prompts for it. 6 Click Expert Options > Write Changes Now to save all changes without exiting the administration dialog. Or click Finish to close the administration dialog and to save the changes.

  • Page 184: Managing Quotas

    Procedure 12.5 Modifying or Disabling Encrypted Home Directories Of course, you can also disable the encryption of a home directory or change the size of the image file at any time. 1 Open the YaST User and Group Administration dialog in the Users view. 2 Select a user from the list and click Edit.
  • Page 185 file systems and restrict the amount of disk space that can be used and the number of inodes (index notes) that can be created there. Inodes are data structures on a file system that store basic information about a regular file, directory, or other file system object. They store all attributes of a file system object (like user and group ownership, read, write, or execute permissions), except file name and contents.
  • Page 186 4 Below Size Limits, restrict the amount of disk space. Enter the number of 1 KB blocks the user or group may have on this partition. Specify a Soft Limit and a Hard Limit value. 5 Additionally, you can restrict the number of inodes the user or group may have on the partition.

  • Page 187: Changing Default Settings For Local Users

    mail notifications to users exceeding their quota. With quota_nld, administrators can also forward kernel messages about exceeded quotas to D-BUS. For more informa- tion, refer to the repquota, the warnquota and the quota_nld man page (root password needed). 12.4 Changing Default Settings for Local Users When creating new local users, several defaults settings are used by YaST.

  • Page 188: Assigning Users To Groups

    12.5 Assigning Users to Groups Local users are assigned to several groups according to the default settings which you can access from the User and Group Administration dialog on the Defaults for New Users tab. In the following, learn how to modify an individual user's group assignment. If you need to change the default group assignments for new users, refer to Section 12.4, “Changing Default Settings for Local Users”...
  • Page 189 3 To create a new group, click Add. 4 To modify an existing group, select the group and click Edit. 5 In the following dialog, enter or change the data. The list on the right shows an overview of all available users and system users which can be members of the group.

  • Page 190: Changing The User Authentication Method

    SMB authentication is often used in mixed Linux and Windows networks. For de- tails, see Chapter 24, Samba (↑Administration Guide). eDirectory LDAP eDirectory authentication is used in Novell networks. To change the authentication method, proceed as follows: 1 Open the User and Group Administration dialog in YaST.
  • Page 191 2 Click the Authentication Settings tab to show an overview of the available authen- tication methods and the current settings. 3 To change the authentication method, click Configure and select the authentication method you want to modify. This takes you directly to the client configuration modules in YaST.

  • Page 193: 3 Changing Language And Country Settings With Yast

    Changing Language and Country Settings with YaST Working in different countries or having to work in a multilingual environment requires your computer to be set up to support this. Use the YaST language and timezone modules to install additional system languages and adjust the country and timezone settings ac- cordingly.
  • Page 194 of your desktop using the desktop's control center. After X has been restarted, your entire desktop reflects your new choice of language. Applications not belonging to your desktop framework are not affected by this change and may still appear in the language that was set in YaST.
  • Page 195 Figure 13.1 Setting the Language To install an additional language, proceed as follows: 1 As root, start YaST. 2 Select System > Language. 3 Select the desired languages from the list of languages offered in Secondary Languages. When you leave this dialog with Ok, YaST installs the additional localized software packages.
  • Page 196 4a Adapt the keyboard to the new primary language and adjust the time zone, if appropriate. For advanced keyboard or time zone settings, open the Hardware > Keyboard Layout (Section 8.3.1, “Keyboard Layout” (page 131)) or System > Date and Time dialog (Section 13.2, “Changing the Country and Time Settings”...

  • Page 197: Changing The Country And Time Settings

    13.2 Changing the Country and Time Settings Using the YaST date and time module, adjust your system date, clock and time zone information to the area you are working in. First, select a general region, such as Europe, for example. Choose an appropriate time zone that matches the one you are working in, for example, Germany.
  • Page 198 Figure 13.2 Setting Country and Time 1 Click Change to set date and time. 2 Select Manually and enter date and time values. 3 Confirm with Accept. If you want to make use of an NTP server: Deployment Guide...
  • Page 199 Figure 13.3 Setting Date and Time With NTP Server 1 Click Change to set date and time. 2 Select Synchronize with NTP Server. 3 Enter the address of an NTP server, if not prefilled. 4 Press Synchronize Now, to get your system time set correctly. If you want to make use of NTP permanently, enable Save NTP Configuration.

  • Page 201: 4 Remote Installation

    Remote Installation SUSE® Linux Enterprise Server can be installed in several different ways. As well as the usual media installation covered in Chapter 6, Installation with YaST (page 89), you can choose from various network-based approaches or even take a completely hands-off approach to the installation of SUSE Linux Enterprise Server.
  • Page 202 IMPORTANT The configuration of the X Window System is not part of any remote installation process. After the installation has finished, log in to the target system as root, enter telinit 3, and start SaX2 to configure the graphics hardware. 14.1.1 Simple Remote Installation via VNC—Static Network Configuration This type of installation still requires some degree of physical access to the target system...
  • Page 203 2 Boot the target system using the first CD or DVD of the SUSE Linux Enterprise Server media kit. 3 When the boot screen of the target system appears, use the boot options prompt to set the appropriate VNC options and the address of the installation source. This is described in detail in Section 14.4, “Booting the Target System for Instal- lation”...
  • Page 204 • Target system with working network connection. • Controlling system with working network connection and VNC viewer software or Java-enabled browser (Firefox, Konqueror, Internet Explorer, or Opera). • Physical boot medium (CD, DVD, or custom boot disk) for booting the target sys- tem.
  • Page 205 14.1.3 Remote Installation via VNC—PXE Boot and Wake on LAN This type of installation is completely hands-off. The target machine is started and booted remotely. User interaction is only needed for the actual installation. This approach is suitable for cross-site deployments. To perform this type of installation, make sure that the following requirements are met: •...
  • Page 206 5 Initiate the boot process of the target system using Wake on LAN. This is de- scribed in Section 14.3.7, “Wake on LAN” (page 218). 6 On the controlling workstation, open a VNC viewing application or Web browser and connect to the target system as described in Section 14.5.1, “VNC Installation”...
  • Page 207 To perform this kind of installation, proceed as follows: 1 Set up the installation source as described in Section 14.2, “Setting Up the Server Holding the Installation Sources” (page 198). Choose an NFS, HTTP, or FTP network server. For an SMB installation source, refer to Section 14.2.5, “Managing an SMB Installation Source”...
  • Page 208 For this type of installation, make sure that the following requirements are met: • Remote installation source: NFS, HTTP, FTP, or SMB with working network connection. • Target system with working network connection. • Controlling system with working network connection and working SSH client software.
  • Page 209 14.1.6 Remote Installation via SSH—PXE Boot and Wake on LAN This type of installation is completely hands-off. The target machine is started and booted remotely. To perform this type of installation, make sure that the following requirements are met: • Remote installation source: NFS, HTTP, FTP, or SMB with working network connection.

  • Page 210: Setting Up The Server Holding The Installation Sources

    6 On the controlling workstation, start an SSH client and connect to the target system as described in Section 14.5.2, “SSH Installation” (page 224). 7 Perform the installation as described in Chapter 6, Installation with YaST (page 89). Reconnect to the target system after it reboots for the final part of the installation.
  • Page 211 type is already running on your system and you want to configure it manually for the server, deactivate the automatic configuration of the server service with Do Not Configure Any Network Services. In both cases, define the directory in which the installation data should be made available on the server. 4 Configure the required server type.
  • Page 212 Consider announcing your installation source via OpenSLP if your network setup supports this option. This saves you from entering the network in- stallation path on every target machine. The target systems are just booted using the SLP boot option and find the network installation source without any further configuration.
  • Page 213 To create a directory holding the installation data, proceed as follows: 1 Log in as root. 2 Create a directory that should later hold all installation data and change into this directory. For example: mkdir install/product/productversion cd install/product/productversion Replace product with an abbreviation of the product name and productversion with a string that contains the product name and version.
  • Page 214 5 Select Add Host and enter the hostnames of the machines to which to export the installation data. Instead of specifying hostnames here, you could also use wild cards, ranges of network addresses, or just the domain name of your network. Enter the appropriate export options or leave the default, which works fine in most setups.
  • Page 215 3 Create a configuration file called install.suse.nfs.reg containing the following lines: # Register the NFS Installation Server service:install.suse:nfs://$HOSTNAME/path_to_instsource/CD1,en,65535 description=NFS Installation Source Replace path_to_instsource with the actual path to the installation source on your server. 4 Save this configuration file and start the OpenSLP daemon with rcslpd start. For more information about OpenSLP, refer to the package documentation located under /usr/share/doc/packages/openslp/ or refer to Chapter 19, SLP Services in the Network (↑Administration Guide).
  • Page 216 Replace instsource with the product name. 2d Mount the contents of the installation repository into the change root envi- ronment of the FTP server: mount --bind path_to_instsource /srv/ftp/instsource Replace path_to_instsource and instsource with values matching your setup. If you need to make this permanent, add it to /etc/fstab. 2e Start vsftpd with vsftpd.
  • Page 217 14.2.4 Setting Up an HTTP Installation Source Manually Creating an HTTP installation source is very similar to creating an NFS installation source. HTTP installation sources can be announced over the network using OpenSLP as well. 1 Create a directory holding the installation sources as described in Section 14.2.2, “Setting Up an NFS Installation Source Manually”...
  • Page 218 3 Announce the installation source via OpenSLP, if this is supported by your net- work setup: 3a Create a configuration file called install.suse.http.reg under /etc/slp.reg.d/ that contains the following lines: # Register the HTTP Installation Server service:install.suse:http://$HOSTNAME/srv/www/htdocs/instsource/CD1/,en,65535 description=HTTP Installation Source Replace instsource with the actual path to the installation source on your server.
  • Page 219 To use a SMB mounted share as installation source, proceed as follows: 1 Boot the installation target. 2 Select Installation. 3 Press F4 for a selection of installation sources. 4 Choose SMB and enter the Windows machine's name or IP address, the share name (INSTALL/product/CD1, in this example), username, and password.

  • Page 220: Preparing The Boot Of The Target System

    Replace path_to_iso with the path to your local copy of the ISO image, path_to_instsource with the source directory of your server, product with the product name, and mediumx with the type (CD or DVD) and number of media you are using. 6 Repeat the previous step to mount all ISO images needed for your product.
  • Page 221 Setting Up a DHCP Server with YaST To announce the TFTP server's location to the network clients and specify the boot image file the installation target should use, add two declarations to your DHCP server configuration. 1 Log in as root to the machine hosting the DHCP server. 2 Start YaST >...
  • Page 222 1 Log in as root to the machine hosting the DHCP server. 2 Append the following lines to a subnet configuration of your DHCP server's configuration file located under /etc/dhcpd.conf: subnet 192.168.1.0 netmask 255.255.255.0 { range dynamic-bootp 192.168.1.200 192.168.1.228; # PXE related stuff # "next-server"...

  • Page 223: Setting Up A Tftp Server

    After restarting the DHCP server, it provides a static IP to the host specified, enabling you to connect to the system via SSH. 14.3.2 Setting Up a TFTP Server Set up a TFTP server with YaST on SUSE Linux Enterprise Server and SUSE Linux Enterprise Server or set it up manually on any other Linux operating system that supports xinetd and tftp.
  • Page 224 4 Modify the configuration of xinetd located under /etc/xinetd.d/ to make sure that the TFTP server is started on boot: 4a If it does not exist, create a file called tftp under this directory with touch tftp. Then run chmod 755 tftp. 4b Open the file tftp and add the following lines: service tftp socket_type...
  • Page 225 4 Change to the directory of your installation repository and copy the isolinux .cfg file to /srv/tftpboot/pxelinux.cfg/default by entering the following: cp -a boot/<architecture>/loader/isolinux.cfg /srv/tftpboot/pxelinux.cfg/default 5 Edit the /srv/tftpboot/pxelinux.cfg/default file and remove the lines beginning with gfxboot, readinfo, and framebuffer. 6 Insert the following entries in the append lines of the default failsafe and apic labels: insmod=kernel module...
  • Page 226 TIP: Changing Kernel and Initrd Filenames It is possible to use different filenames for kernel and initrd images. This is useful if you want to provide different operating systems from the same boot server. However, you should be aware, that only one dot is permitted in the filenames that are provided by tftp for the pxe boot.
  • Page 227 prompt timeout Replace ip_instserver and path_instsource with the values used in your setup. The following section serves as a short reference to the PXELINUX options used in this setup. Find more information about the options available in the documen- tation of the syslinux package located under /usr/share/doc/ packages/syslinux/.
  • Page 228 title mytitle kernel my_kernel my_kernel_options initrd myinitrd PXELINUX uses the following syntax: label mylabel kernel mykernel append myoptions Labels are mangled as if they were filenames and they must be unique after man- gling. For example, the two labels “v2.1.30” and “v2.1.31” would not be distin- guishable under PXELINUX because both mangle to the same DOS filename.

  • Page 229: Wake On Lan

    keyboard, assuming the user will complete the command begun. A time-out of zero disables the time-out completely (this is also the default). The maximum possible time-out value is 35996 (just less than one hour). PROMPT flag_val If flag_val is 0, displays the boot prompt only if Shift or Alt is pressed or Caps Lock or Scroll Lock is set (this is the default).

  • Page 230: Booting The Target System For Installation

    14.3.7 Wake on LAN Wake on LAN allows a machine to be turned on by a special network packet containing the machine's MAC address. Because every machine in the world has a unique MAC identifier, you do not need to worry about accidentally turning on the wrong machine. IMPORTANT: Wake on LAN across Different Network Segments If the controlling machine is not located in the same network segment as the installation target that should be awakened, either configure the WOL requests...
  • Page 231 14.4.1 Using the Default Boot Options The boot options are described in detail in Chapter 6, Installation with YaST (page 89). Generally, just selecting Installation starts the installation boot process. If problems occur, use Installation—ACPI Disabled or Installation—Safe Settings. For more information about troubleshooting the installation process, refer to Section “In- stallation Problems”...
  • Page 232 Table 14.1 Installation (Boot) Scenarios Used in This Chapter Installation Scenario Parameters Needed for Boot Options Booting Chapter 6, Installation None: system boots auto- None needed with YaST (page 89) matically Section 14.1.1, “Simple • Location of the in- • install=(nfs,http, Remote Installation via stallation server ftp,smb):///path...
  • Page 233 Installation Scenario Parameters Needed for Boot Options Booting Section 14.1.4, “Simple • Location of the in- • install=(nfs,http, Remote Installation via stallation server ftp,smb):///path SSH—Static Network • Network device _to_instmedia Configuration” • IP address • netdevice=some (page 194) • Netmask _netdevice (only need- •...

  • Page 234: Monitoring The Installation Process

    TIP: More Information about linuxrc Boot Options Find more information about the linuxrc boot options used for booting a Linux system at http://en.opensuse.org/Linuxrc. 14.5 Monitoring the Installation Process There are several options for remotely monitoring the installation process. If the proper boot options have been specified while booting for installation, either VNC or SSH can be used to control the installation and system configuration from a remote workstation.
  • Page 235 1 Start the KDE file and Web browser Konqueror. 2 Enter service://yast.installation.suse in the location bar. The target system then appears as an icon in the Konqueror screen. Clicking this icon launches the KDE VNC viewer in which to perform the installation. Alternatively, run your VNC viewer software with the IP address provided and add :1 at the end of the IP address for the display the installation is running on.
  • Page 236 1 Launch your preferred Web browser. 2 Enter the following at the address prompt: http://ip_address_of_target:5801 3 Enter your VNC password when prompted to do so. The browser window now displays the YaST screens as in a normal local installation. 14.5.2 SSH Installation Using SSH, you can remotely control the installation of your Linux machine using any SSH client software.
  • Page 237 4 When prompted for the password, enter the password that has been set with the SSH boot option. After you have successfully authenticated, a command line prompt for the installation target appears. 5 Enter yast to launch the installation program. A window opens showing the normal YaST screens as described in Chapter 6, Installation with YaST (page 89).

  • Page 239: 5 Advanced Disk Setup

    Advanced Disk Setup Sophisticated system configurations require particular disk setups. All common parti- tioning tasks can be done with YaST. To get persistent device naming with block devices, use the block devices below /dev/disk/by-id or /dev/disk/by-uuid. Logical Volume Management (LVM) is a disk partitioning scheme that is designed to be much more flexible than the physical partitioning used in standard setups.
  • Page 240 Figure 15.1 The YaST Partitioner TIP: IBM System z: Device Names IBM System z recognize only DASD and SCSI hard disks. IDE hard disks are not supported. This is why these devices appear in the partition table as dasda or sda for the first recognized device.
  • Page 241 Server, free the needed space starting from the bottom toward the top of the list (starting from the last partition of a hard disk toward the first). For example, if you have three partitions, you cannot use the second exclusively for SUSE Linux Enterprise Server and retain the third and first for other operating systems.

  • Page 242: Creating A Partition

    15.1.2 Creating a Partition To create a partition from scratch select Hard Disks and then a hard disk with free space. The actual modification can be done in the Partitions tab: 1 Select Add. If several hard disks are connected, a selection dialog appears in which to select a hard disk for the new partition.
  • Page 243 File System ID Even if you do not want to format the partition at this stage, assign it a file system ID to ensure that the partition is registered correctly. Possible values include Linux, Linux swap, Linux LVM, and Linux RAID. File System Change the file system or format the partition here.
  • Page 244 When using the mount option LABEL to mount a partition, define an appro- priate label for the selected partition. For example, you could use the partition label HOME for a partition intended to mount to /home. If you intend to use quota on the file system, use the mount option Enable Quota Support.
  • Page 245 the size of your ram in swap, the performance of the system suffered. This does not hold true anymore as these limitations no longer exist. Linux uses a page called “Least Recently Used” (LRU) to select pages that might be moved from memory to disk.
  • Page 246 compared to physical ram, both are extremely slow and the actual speed difference is not as important as one would think in the first place. Procedure 15.1 Adding a Swap File Manually To add a swap file in the running system, proceed as follows: 1 Create an empty file in your system.

  • Page 247: Lvm Configuration

    table of a hard disk when any partition on this disk is in use. However, if you already have a functioning LVM configuration on your system, physical repartitioning should not be necessary. Instead, change the configuration of the logical volumes. At the beginning of the physical volumes (PVs), information about the volume is written to the partition.
  • Page 248 can be created as needed. The operating system accesses these LVs instead of the physical partitions. Volume groups can span more than only one disk so that several disks or parts of them may constitute one single VG. This way, LVM provides a kind of abstraction from the physical disk space that allows its segmentation to be changed in a much easier and safer way than physical repartitioning does.
  • Page 249 • Using LVM, it is possible to add hard disks or LVs in a running system. However, this requires hot-swappable hardware that is capable of such actions. • It is possible to activate a "striping mode" that distributes the data stream of a LV over several PVs.

  • Page 250: Creating Volume Groups

    4 Use Do not Format the Partition and change the File System ID to 0x8E Linux LVM. Do not mount this partition. 5 Repeat this procedure until you defined all the desired physical volumes on the available disks. Creating Volume Groups If no volume group exists on your system yet, you have to add one (see Figure 15.3, “Creating a Volume Group”...
  • Page 251 Figure 15.3 Creating a Volume Group If you have multiple volume groups defined, and want to add or remove PVs, select the volume group in Volume Management. Then change to the Overview tab and select Resize. In the following menu, you can add or remove PVs to the selected volume group.
  • Page 252 Figure 15.4 Logical Volume Management Click Add and go through the wizard-like popup that opens: 1. Enter the name of the LV. For a partition that should be mounted to /home, a selfexplaining name like HOME could be used. 2. Select the size and the number of stripes of the LV. If you have only one PV, se- lecting more than one stripes is not useful.

  • Page 253: Soft Raid Configuration

    WARNING: Striping YaST has no chance at this point to verify the correctness of your entries con- cerning striping. Any mistake made here is apparent only later when the LVM is implemented on disk. If you have already configured LVM on your system, the existing logical volumes can also be used.
  • Page 254 RAID 1 This level provides adequate security for your data, because the data is copied to another hard disk 1:1. This is known as hard disk mirroring. If a disk is destroyed, a copy of its contents is available on another one. All of them except one could be damaged without endangering your data.
  • Page 255 15.3.1 Soft RAID Configuration with YaST The YaST RAID configuration can be reached from the YaST Expert Partitioner, de- scribed in Section 15.1, “Using the YaST Partitioner” (page 227). This partitioning tool enables you to edit and delete existing partitions and create new ones that should be used with soft RAID.

  • Page 256: Troubleshooting

    Figure 15.5 RAID Partitions To add a previously unassigned partition to the selected RAID volume, first click the partition then Add. Assign all partitions reserved for RAID. Otherwise, the space on the partition remains unused. After assigning all partitions, click Next to select the available RAID Options.

  • Page 257: For More Information

    15.3.3 For More Information Configuration instructions and more details for soft RAID can be found in the HOWTOs • /usr/share/doc/packages/mdadm/Software-RAID.HOWTO.html • http://en.tldp.org/HOWTO/Software-RAID-HOWTO.html http://marc.theaimsgroup Linux RAID mailing lists are also available, such as .com/?l=linux-raid. Advanced Disk Setup...

  • Page 259: 6 Subscription Management

    Novell Customer Center and the NU servers. To use an SMT server for client registration and as a local update source, you must configure the SMT server in your network first.

  • Page 260: Using Kernel Parameters To Access An Smt Server

    There are several ways to provide this information and to configure the client machine to use SMT. The first way is to provide the needed information via kernel parameters at boot time. The second way is to configure clients using an AutoYaST profile. There is also a script distributed with Subscription Management Tool, clientSetup4SMT.sh, which can be run on a client to make it register against a specified SMT server.

  • Page 261: Configuring Clients Using Autoyast Profile

    regcert=/data/inst/smt/smt-ca.cert Interactive Use ask to open a pop-up menu during installation where you can specify the path to the certificate. Do not use this option with AutoYaST. Example: regcert=ask Deactivate Certificate Installation Use done if either the certificate will be installed by an add-on product, or if you are using a certificate issued by an official certificate authority.
  • Page 262 2 Open an existing profile using File > Open, create a profile based on the current system's configuration using Tools > Create Reference Profile, or just work with an empty profile. 3 Select Support > Novell Customer Center Configuration. An overview of the current configuration is shown. 4 Click Edit.

  • Page 263: Configuring Clients Using The Clientsetup4Smt.sh Script

    16.3 Configuring Clients Using the clientSetup4SMT.sh Script The /usr/share/doc/packages/smt/clientSetup4SMT.sh script is provided with SMT. This script allows to configure a client machine to use a SMT server or to reconfigure it to use a different SMT server. To configure a client machine to use SMT with the clientSetup4SMT.sh script, follow these steps: 1 Copy the /usr/share/doc/packages/smt/clientSetup4SMT.sh script from your SMT server to the client machine.
  • Page 264 register = command=register&testenv=1 For more information about using SMT with a test environment, refer to the Subscription Management Tool Guide. Deployment Guide...

  • Page 265: Part Iii Imaging And Creating Products

    Part III. Imaging and Creating Products...

  • Page 267: 7 Kiwi

    KIWI KIWI is a system for creating operating system images. An image is a directory with a file containing the operating system, its applications and configurations, the filesystem structure of the OS, possible additional metadata, and depending on the image type, also disk geometry and partition table data.

  • Page 268: Knowing Kiwi's Build Process

    Image Type Package Name USB Sticks kiwi-desc-usbboot Network Client kiwi-desc-netboot 3. Install the kiwi-doc package. You can find some example configurations to get an idea about the structure and its content. 4. Know the KIWI configuration file and its structure. It is based on a RELAX NG schema and documented in the kiwi package under /usr/share/doc/ packages/kiwi/kiwi.html.
  • Page 269 17.3.1 Contents of Image Description The following table contains additional optional information. However, most of infor- mation is mandatory for the functionality of the later operating system: Table 17.1 Additional Files and Directories For Image Description File/Directory Description config/ optional subdirectory. Contains Bash scripts which are executed after the installation of all the image packages.
  • Page 270 17.3.2 The config.xml File All information about an image description is stored in the central configuration XML file config.xml. Each time KIWI is executed, config.xml is validated against http://www.relaxng.org an RELAX NG schema (see for more information about this schema language). Therefor it is recommended, to use a decent XML editor with RELAX NG support or to use the documentation about the schema in the HTML file /usr/share/doc/packages/kiwi/schema/kiwi.xsd.html.
  • Page 271 Example 17.1 KIWI Configuration File <image schemeversion="2.0" name="..."> <description type="system"> <author>...</author> <contact>...</contact> <specification>...</specification> </description> <preferences> <type primary="true" boot="..." flags="...">iso</type> <type boot="..." filesystem="ext3" format="vmdk">vmx</type> <type boot="..." filesystem="ext3">xen</type> <type boot="..." filesystem="squashfs" flags="unified">oem</type> <version>2.7.0</version> <size unit="M">780</size> <packagemanager>zypper</packagemanager> <rpm-check-signatures>False</rpm-check-signatures> <rpm-force>False</rpm-force> <locale>en_US.UTF-8</locale> <oem-swap>no</oem-swap> <oem-boot-title>USB</oem-boot-title> </preferences> <users group="users">...

  • Page 272: Creating Appliances With Kiwi

    Contains a mandatory list of packages which are included into the image. More details about the configuration file is shown in the HTML page above. 17.4 Creating Appliances with KIWI This section describes how to create appliances with KIWI. An appliance is a special designed operating system for a specific task.
  • Page 273 <repository type="..."> <!-- Remove the comment markers in the next line --> <!-- <source path="/image/CDs/full-VERSION-ARCH" --> <source path="opensuse://openSUSE:11.0/standard"/> </repository> 17.4.2 Creating an Image An image is a virtual disk image containing all partitions, boot loader information, and packages as it resides on a real disk. To create an ISO image, proceed as follows: 1 Install the packages kiwi and kiwi-doc and resolve any dependencies.

  • Page 274: For More Information

    3 Open the file suse-oem-preload/config.xml and locate the packages element with the attribute type="image". 4 Insert the following line between <packages type="image"> and </packages> and save the file: <package name="nfs-client"/> 5 Rebuild the image as described in Step 5 (page 261). 17.5 For More Information Find more information about KIWI in the following documents: •...

  • Page 275: 8 Creating Add-On Products With Add-On Creator

    Creating Add-On Products With Add-on Creator An Add-On is a special designed media, usually a CD or DVD, to extend your product. The Add-on Creator was developed to support our customers and partners and simplify third-party software distribution for all SUSE products. 18.1 Creating Images To create a Add-On CD, proceed as follows: 1 Start YaST and open the Add-On Creator module.

  • Page 276: Add-On Structure

    4 Correct the product definition and enter a vendor name. Disable Show Only Required Keywords to display more keywords. 5 Optionally change the package descriptions. Use Add Language to insert a new language and add translated descriptions. 6 Optionally add new patterns. With patterns you can group your RPM packages. Use New to add a new pattern name and change the respective attributes in the list below.

  • Page 277: For More Information

    ARCHIVES.gz Contains the gzipped contents of all RPM files. It is actually a listing of the rpm command with the options -qil for each RPM file. Changelog Contains all the changes of the RPM files. content Contains information about your Add-On product. content.asc Contains the signature file from GnuPG.
  • Page 278 • http://en.opensuse.org/Creating_YaST_Installation _Sources—YaST installation source creation • http://en.opensuse.org/Libzypp/Metadata/YaST—YaST metadata description • http://developer.novell.com/wiki/index.php/Creating _Add-ons— Deployment Guide...

  • Page 279: 9 Creating Images With Yast Product Creator

    Creating Images with YaST Product Creator The YaST Product Creator is a unified graphical front-end for KIWI and Add-on Creator. It was developed to provide image creation functionality in one place. All tools integrated in the YaST Product Creator are still available as separate YaST modules or applications. 19.1 Prerequisites for Product Creator Before you can create images with the YaST Product Creator, make sure you meet the following prerequisites:...
  • Page 280 If you have been used the Product Creator already before, select Add to create a new product definition and enter the configuration name and choose the method. 2 Select or deselect package sources. To select a source, select it from the table and click Select.

  • Page 281: For More Information

    • Create Image with KIWI... Use the pull-down menu to choose from different target formats, such as Live media or Xen images. 19.3 For More Information Find more information about creating system images and related topics in the following documents: •...

  • Page 283: 0 Deploying Customized Preinstallations

    Deploying Customized Preinstallations Rolling out customized preinstallations of SUSE Linux Enterprise Server to a large number of identical machines spares you from installing each one of them separately and provides a standardized installation experience for the end users. With YaST first- boot, create customized preinstallation images and determine the workflow for the final personalization steps that involve end user interaction.

  • Page 284: Preparing The Master Machine

    20.1 Preparing the Master Machine To prepare a master machine for a firstboot workflow, proceed as follows: 1 Insert the installation media into the master machine. 2 Boot the machine. 3 Perform a normal installation including all necessary configuration steps and wait for the installed machine to boot.
  • Page 285 • Customizing licenses and license actions as described in Section 20.2.2, “Customiz- ing the License Action” (page 274). • Customizing the release notes to display as described in Section 20.2.3, “Customiz- ing the Release Notes” (page 275). • Customizing the order and number of components involved in the installation as described in Section 20.2.4, “Customizing the Workflow”...
  • Page 286 FIRSTBOOT_WELCOME_DIR="/usr/share/firstboot/" 2b If your welcome message has filenames other than welcome.txt and welcome_locale.txt (where locale matches the ISO 639 language codes such as “cs” or “de”), specify the filename pattern in FIRSTBOOT_WELCOME_PATTERNS. For example: FIRSTBOOT_WELCOME_PATTERNS="mywelcome.txt" If unset, the default value of welcome.txt is assumed. 3 Create the welcome file and the localized versions and place them in the directory specified in the /etc/sysconfig/firstboot configuration file.
  • Page 287 20.2.3 Customizing the Release Notes Depending on whether you have changed the instance of SUSE Linux Enterprise Server you are deploying with firstboot, you probably need to educate the end users about important aspects of their new operating system. A standard installation uses re- lease notes, displayed during one of the final stages of the installation, to provide im- portant information to the users.
  • Page 288 • root Password • User Authentication Method • User Management • Hardware Configuration • Finish Setup This standard layout of a firstboot installation workflow is not mandatory. You can enable or disable certain components or hook your own modules into the workflow. To modify the firstboot workflow, manually edit the firstboot configuration file /etc/ YaST2/firstboot.xml.
  • Page 289 The mode of this proposal. Do not make any changes here. For a firstboot instal- lation, this must be set to installation. The stage of the installation process at which this proposal is invoked. Do not make any changes here. For a firstboot installation, this must be set to firstboot.
  • Page 290 enable_next Include the Next button in all dialogs. archs Specify the hardware architectures on which this workflow should be used. Example 20.3 Configuring the List of Workflow Components <modules config:type="list"> <module> <label>Language</label> <enabled config:type="boolean">false</enabled> <name>firstboot_language</name> </module> <modules> The container for all components of the workflow. The module definition.
  • Page 291 • To change the order of proposals, move the respective module elements containing the proposal screens around in the workflow. Note that there may be dependencies to other installation steps that require a certain order of proposals and workflow components. 3 Apply your changes and close the configuration file.
  • Page 292 .ycp suffix. 5 Apply your settings and close the configuration file. TIP: For More Information http://developer For more information about YaST development, refer to .novell.com/wiki/index.php/YaST. Detailed information about YaST http://forgeftp.novell.com/yast/doc/ firstboot can be found at SL11.1/tdg/inst_in_general_chap.html. 20.2.5 Configuring Additional Scripts firstboot can be configured to execute additional scripts after the firstboot workflow has been completed.

  • Page 293: Cloning The Master Installation

    20.3 Cloning the Master Installation Clone the master machine's disk using any of the imaging mechanisms available to you and roll these images out to the target machines. For more information about imaging Chapter 17, KIWI (page 255). 20.4 Personalizing the Installation As soon as the cloned disk image is booted, firstboot starts and the installation proceeds exactly as laid out in Section 20.2.4, “Customizing the Workflow”...

  • Page 295: Part Iv Automated Installations

    Part IV. Automated Installations...

  • Page 297: 1 Automated Installation

    Automated Installation AutoYaST allows you to install SUSE® Linux Enterprise on a large number of machines in parallel. The AutoYaST technology offers great flexibility to adjust deployments to heterogeneous hardware. This chapter tells you how to prepare a simple automated in- stallation and lay out an advanced scenario involving different hardware types and in- stallation purposes.
  • Page 298 4 Determine and set up the boot scenario for autoinstallation as described in Sec- tion 21.1.4, “Setting Up the Boot Scenario” (page 291). 5 Pass the command line to the installation routines by adding the parameters manually or by creating an info file as described in Section 21.1.5, “Creating the info File”...
  • Page 299 3 Select Tools > Create Reference Control File to prepare AutoYaST to mirror the current system configuration into an AutoYaST profile. 4 As well as the default resources, like boot loader, partitioning, and software se- lection, you can add various other aspects of your system to the profile by checking the items in the list in Create a Reference Control File.
  • Page 300 Figure 21.1 Editing an AutoYaST Profile with the AutoYaST Front-End 21.1.2 Distributing the Profile and Determining the autoyast Parameter The AutoYaST profile can be distributed in several different ways. Depending on the protocol used to distribute the profile data, different AutoYaST parameters are used to make the profile location known to the installation routines on the client.
  • Page 301 Profile Lo- Parameter Description cation Device autoyast=device:// Makes the installation routines look for the control file on a storage device. Only /path the device name is needed—/dev/sda1 is wrong, use sda1 instead. Floppy autoyast=floppy:// Makes the installation routines look for the control file on a floppy in the floppy /path drive.
  • Page 302 2 Omit the exact path including the filename when creating the autoyast= pa- rameter, for example: autoyast=tftp://192.168.1.115/ 3 Start the autoinstallation. YaST tries to determine the location of the profile in the following way: 1. YaST searches for the profile using its own IP address in uppercase hexadecimal, for example, 192.0.2.91 is C000025B.
  • Page 303 To provide the installation sources over the network, set up a network installation server (HTTP, NFS, FTP) as described in Section 14.2.1, “Setting Up an Installation (page 198). Use an info file to pass the server's location to the Server Using YaST” installation routines.
  • Page 304 The same example for autoinstallation looks like this: default linux # default label linux kernel linux append initrd=initrd install=http://192.168.1.115/install/suse-enterprise/ autoyast=nfs://192.168.1.110/profiles/autoyast.xml Replace the example IP addresses and paths with the data used in your setup. Preparing to Boot from CD-ROM There are several ways in which booting from CD-ROM can come into play in Auto- YaST installations.
  • Page 305 In both cases, you may also need to change media depending on the scope of instal- lation. You need: • The SUSE Linux Enterprise media • A floppy holding both the profile and the info file Access to the boot prompt of the target to enter the autoyast= parameter Boot and Install from Custom Media, Get the Profile from the Media If you just need to install a limited number of software packages and the number of targets is relatively low, creating your own custom CD holding both the installa-...
  • Page 306 IMPORTANT: Separating Parameters and Values When passing parameters to linuxrc at the boot prompt, use = to separate parameter and value. When using an info file, separate parameter and value with :. Keyword Value netdevice The network device to use for network setup (for BOOTP/DHCP requests).
  • Page 307 autoyast:profile_source install:install_source vnc:1 vncpassword:some_password If you prefer a static network setup at installation time, your info file would look like the following: autoyast:profile_source \ install:install_source \ hostip:some_ip \ netmask:some_netmask \ gateway:some_gateway The \ indicate that the line breaks have only been added for the sake of readability. All options must be entered as one continuous string.
  • Page 308 vnc: 1 vncpassword: test autoyast: file:///info # end_linuxrc_conf # Do not remove the above comment ]]> </info_file> </init> ..</install> ..linuxrc loads the profile containing the boot parameters instead of the traditional info file. The install: parameter points to the location of the installation sources. vnc and vncpassword indicate the use of VNC for installation monitoring.

  • Page 309: Rule-Based Autoinstallation

    21.2 Rule-Based Autoinstallation The following sections introduce the basic concept of rule-based installation using AutoYaST and provide an example scenario that enables you to create your own custom autoinstallation setup. 21.2.1 Understanding Rule-Based Autoinstallation Rule-based AutoYaST installation allows you to cope with heterogeneous hardware environments: •...
  • Page 310 • Create custom rules by running shell scripts and passing their output to the Auto- YaST framework. The number of custom rules is limited to five. NOTE For more information about rule creation and usage with AutoYaST, refer to the package's documentation under /usr/share/doc/packages/ autoyast2/html/index.html, Chapter Rules and Classes.
  • Page 311 21.2.2 Example Scenario for Rule-Based Autoinstallation To get a basic understanding of how rules are created, think of the following example, depicted in Figure 21.2, “AutoYaST Rules” (page 300). One run of AutoYaST installs the following setup: A Print Server This machine just needs a minimal installation without a desktop environment and a limited set of software packages.
  • Page 312 Figure 21.2 AutoYaST Rules AutoYaST Directory Enigineering Department Computers rules.xml File Rule 1 Eng. Profile Rule 2 Rule 3 Sales Profile Sales Department Laptops Merge Process Print Server Profile Print Server In a first step, use one of the methods outlined in Section 21.1.1, “Creating an AutoYaST Profile”...
  • Page 313 In the second step, create rules to distinguish the three hardware types from one another and to tell AutoYaST which profile to use. Use an algorithm similar to the following to set up the rules: 1. Does the machine have an IP of 192.168.2.253? Then make it the print server. 2.
  • Page 314 <operator>and</operator> </rule> <rule> <haspcmcia> <match>0</match> <match_type>exact</match_type> </haspcmcia> <result> <profile>engineering.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> When distributing the rules file, make sure that the rules directory resides under the profiles directory specified in the autoyast=protocol:serverip/ profiles/ URL. AutoYaST looks for a rules subdirectory containing a file named rules.xml first then loads and merges the profiles specified in the rules file.
  • Page 315 Automated Deployment of Preload Images With KIWI you are able to create operating system images. This chapter handles the process of deploying an system image to an empty machine. For this, you have to create a preload image which contains a bootable RAW image. This file contains two important parts: a partition table and the actual operating system.
  • Page 316 22.1 Deploying system manually from rescue image Deploying with generated ISO file from KIWI: 1. Burn the ISO image you get from the KIWI building process, see Section 17.4.2, “Creating an Image” (page 261) on CD/DVD 2. Boot from this medium on the machine you want to install the system. 3.
  • Page 317 22.2 Automated Deployment with PXE Boot When doing many installations of a operating system on similar hardware, it is useful to put some effort into preparing a mass deployment of the operating system and to minimize the time needed for the actual deployment. This is what this chapter is about. The goal is to just attach a computer to power and network, start a network boot, and wait until it switches off again.
  • Page 318 22.2.1 Setup a Boot and Install Server There are four steps to accomplish to perform this task after you installed a SUSE Linux Enterprise Server: To perform this type of installation, proceed as follows: 1 Set up the installation source as described in Section 14.2, “Setting Up the Server Holding the Installation Sources”...
  • Page 319 • Depending on the desired usage of the preload, some effort should be invested in configuring firstboot. Find more details about firstboot in Chapter 20, Deploying Customized Preinstallations (page 271). With this method you can also require the user to do initial configurations at the first bootup of the system. •...
  • Page 320 mkinitrd -f busybox -D eth0 Note that eth0 represents the ethernet device where your network cable is at- tached to. The parameter -f busybox adds the multi call binary busybox to the ram filesystem. After doing this, many standard unix commands are available inside this system.
  • Page 321 rawimage=$(get_param rawimage) [ "$(get_param rawdevice)" ]; then rawdevice=$(get_param rawdevice) echo "wget -O ${rawdevice} ${rawimage}" wget -O ${rawdevice} ${rawimage} sync sleep 5 echo "DONE" # /bin/bash /bin/poweroff -f 12 If you want to have a debug shell before the computer switches off, remove the comment sign before /bin/bash.
  • Page 322 • Setup a dhcp server. The subnet where the machines are installed needs the addi- tional lines: filename "pxelinux.0"; next-server 192.168.1.115; In this example, 192.168.1.115 is the ip address of the PXE server pxe.example.com. • Configure a PXE server as described in Section 14.3.3, “Using PXE Boot”...

This manual is also suitable for:

Suse linux enterprise server 11

Table of Contents