1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. LINUX ENTERPRISE DESKTOP 10 SP2
  6. Supplementary manual

Novell LINUX ENTERPRISE SERVER 10 SP2 - ARCHITECTURE-SPECIFIC INFORMATION Supplementary Manual

Architecture-specific information
Hide thumbs Also See for LINUX ENTERPRISE SERVER 10 SP2 - ARCHITECTURE-SPECIFIC INFORMATION:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Administration Manual, Installation
SUSE Linux Enterprise
Server
10 SP2
May 08, 2008
Architecture-Specific Information
www.novell.com

Advertisement

Table of Contents
loading

Related Manuals for Novell LINUX ENTERPRISE SERVER 10 SP2 - ARCHITECTURE-SPECIFIC INFORMATION

Summary of Contents for Novell LINUX ENTERPRISE SERVER 10 SP2 - ARCHITECTURE-SPECIFIC INFORMATION

  • Page 1 SUSE Linux Enterprise Server 10 SP2 www.novell.com Architecture-Specific Information May 08, 2008...
  • Page 2 The express authorization of Novell, Inc must be obtained prior to any other use of any manual or part thereof. For Novell trademarks, see the Novell Trademark and Service Mark list http://www.novell...

  • Page 3: Table Of Contents

    Contents Introduction 1 General Information and Requirements System Requirements ......Installation Types ......IPL Options .

  • Page 5: Introduction

    Introduction This book describes the procedure for preparing the installation of SUSE® Linux En- terprise Server on IBM System z systems. It provides all information needed to prepare the installation on the LPAR and z/VM side. 1 Structure Basically, this manual is divided in two parts. General Information and Requirements This part provides information about the requirements both on the hardware and the software side that need to be met to install SUSE Linux Enterprise Server suc-...

  • Page 6: Required Background

    2 Required Background Several assumptions have been made concerning your background knowledge when writing this document. • You are familiar with IBM System z terminology. • You have a good knowledge of the IBM System z devices attached to your system, especially its network environment.
  • Page 7 4 Further In-Depth Information about IBM System z IBM has published a number of very interesting documents about their System z plat- form. Find them either on the Internet (http://www.redbooks.ibm.com) or in your installed system (package redbook) under /usr/share/doc/packages/ redbook. 4.1 Hardware For a first glance at the technical details of some systems, refer to: •...
  • Page 8 4.3 Technical Issues of Linux on IBM System z Refer to the following documents to get in-depth technical information about Linux kernel and application topics. Refer to the Internet for up-to-date versions of these documents for the most recent code drop (http://www.ibm.com/ developerworks/linux/linux390/index.html).
  • Page 9 • Linux on IBM zSeries and S/390: High Availability for z/VM and Linux (REDP- 0220) • Saved Segments Planning and Administration publibz.boulder.ibm.com/epubs/pdf/hcsg4a00.pdf • Linux for zSeries and S/390: How to Improve Performance with PAV http://www.ibm.com/developerworks/linux/linux390/index .html • How to Improve the Performance of Linux on z/VM with Execute-in-Place Tech- nology http://www.ibm.com/developerworks/linux/linux390/index .html...

  • Page 11: General Information And Requirements

    General Information and Requirements This chapter gives basic information about the system requirements, like supported hardware, level of MicroCode, and software. It also covers the different installation types, how to do an IPL for the first installation, and information about the IOCDS. 1.1 System Requirements This section provides a list of hardware for IBM System z supported by SUSE®...

  • Page 12: Memory Requirements

    • IBM eServer Series z9 (z9-BC) 2096 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. SUSE recommends using: 512 MB For installation from NFS, FTP, or SMB installation sources or whenever VNC is used.

  • Page 13: Ipl Options

    • ESCON • IP network interface for IUCV IPL Options For an LPAR installation, the Load from CD-ROM or Server option is the preferred way to IPL the installation kernel and initrd (initial RAM disk). If this option is not available and you cannot use z/VM for installing the system, you need to IPL from a channel attached tape with the tapeipl kernel, the parmfile, and the initrd.
  • Page 14 MCLs: J11204.007 and J11204.008 (available May 3, 2002) zSeries 900 Driver 3C, OSA microcode level 2.26 MCLs: J10630.013 and J10630.014 (available May 20, 2002) zSeries 800 Driver 3G, OSA microcode level 3.0A MCLs: J11204.007 and J11204.008 (available May 3, 2002) VM/ESA and z/VM z/VM 5.2 z/VM 5.1...

  • Page 15: Installation Types

    on CD 1 in the directory /dosutils/putty. Get more information about Putty at http://www.chiark.greenend.org.uk/~sgtatham/putty/. VNC Client For Linux, a VNC client called vncviewer is included in SUSE Linux Enterprise Server as part of the XFree86-Xvnc package. For Windows, a VNC client is included in the present SUSE Linux Enterprise Server.

  • Page 16: Ipl Options

    1.2.1 LPAR If you install SUSE Linux Enterprise Server for IBM System z into a separate logical partition (LPAR), allow SUSE Linux Enterprise Server to use a special part of physical memory in your system. Also decide how many processors are used by SUSE Linux Enterprise Server.
  • Page 17 1.3.2 VM Reader To IPL from a VM reader, transfer the necessary files into the reader first. Then multiple IPLs are easily done. This is the preferred way on z/VM. For comfortable administration, it is recommended to create a user linuxmnt that owns a minidisk with the files and scripts needed for IPL.

  • Page 18: The Iocds

    Figure 1.2 Specifying the Load Option on the SE's Groups Work Area Access the service element's Groups Work Area. Select the LPAR to perform the load from CD-ROM or server and initiate CPC recovery for that LPAR. Start Load from CD ROM or Server from the action menu.
  • Page 19 WARNING: Sharing Devices (DASD) Do not share DASD writable among LPARs because this might result in data loss. Consider the definition of the necessary resources in advance when plan- ning the setup for SUSE Linux Enterprise Server on IBM System z. This example shows how to dedicate a DASD to one specific LPAR.

  • Page 21: Preparing For Installation

    Preparing for Installation In this chapter, learn how to make the data accessible for installation, install SUSE® Linux Enterprise Server using different methods, and prepare and use the IPL of the SUSE Linux Enterprise Server installation system. Also find out about network confi- guration and network installation.
  • Page 22 2.1.1 Using a Linux Workstation or SUSE Linux Enterprise Server CD 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 23 SUSE Linux Enterprise Server on CD or DVD CD 1 and the DVD of the SUSE Linux Enterprise Server for IBM System z contain a bootable Linux image for Intel-based workstations as well as an image for System z. For Intel-based workstations, boot from this CD, answer the questions regarding your language and keyboard layout, and select Start rescue system.

  • Page 24: Installation Types

    TIP: SMB Installation Path for YaST Consult the README from the highest directory of CD 1 for detailed information about the syntax of the installation path for YaST. With NFS Refer to the documentation provided with the third party product that enables NFS server services for your Windows workstation.
  • Page 25 accomplished, follow the installation overview of the desired installation mode to install SUSE Linux Enterprise Server on your system. As described in Section 2.1, “Making the Installation Data Available” (page 11), there are two different installation modes for Linux on IBM System z: •...

  • Page 26: Preparing The Ipl Of The Suse Linux Enterprise Server Installation System

    2.3 Preparing the IPL of the SUSE Linux Enterprise Server Installation System 2.3.1 LPAR Installation Configure your IBM System z system to start in ESA mode with an appropriate activa- tion profile and IOCDS. Consult IBM documentation for more about how to achieve this.
  • Page 27 2.3.2 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 512 MB), 32 MB of expanded RAM (XSTORE), some minidisks (MDISK), two CPUs and an OSA QDIO device.
  • Page 28 Example 2.2 Configuration of a z/VM Directory USER LINUX1 LINPWD 256M 512M 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 29: Ipling The Suse Linux Enterprise Server Installation System

    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 2.4.2, “z/VM Installation”...
  • Page 30 Figure 2.1 Example: IPL from ESCON or FICON Attached Tape If you cannot IPL from CD-ROM, create a channel attached tape from which to IPL the SUSE Linux Enterprise Server installation image. Use the LOAD button in the SE or HMC with the tape device address as the load address to IPL the SUSE Linux Enter- prise Server installation system.
  • Page 31 and write them onto a tape with the REXX from the example. IMPORTANT: Transferring Binaries using FTP Do not upload the files as fixed 80. Store them as fixed 1024. Use the FTP command loc site fix 1024. Example 2.3 REXX Script to Create an IPLable Tape 'REWIND 181' 'FILEDEF IN1 DISK' SLES10 IMAGE A 'FILEDEF IN2 DISK' SLES10 PARM A...
  • Page 32 The example shows the steps necessary. In this example, the required files are accessible from an FTP server at the IP address 192.168.0.3 and the login is lininst. It may differ for your network. Example 2.4 Transferring the Binaries via FTP FTP 192.168.0.3 VM TCP/IP FTP Level 320 Connecting to 192.168.0.3, port 21...
  • Page 33 Transfer the files with a fixed block size of 80 characters. Specify it with the FTP command locsite fix 80. It is important to copy VMRDR.IKR (the Linux kernel) and INITRD (the installation image) as binary files, so use the binary transfer mode. Creating a Start Script It is convenient to write a small REXX script to IPL the Linux installation system.

  • Page 34: Network Configuration

    IPL from ESCON or FICON Attached tape If you cannot IPL from a z/VM reader, create a channel attached tape from which to IPL the SUSE Linux Enterprise Server installation image. For instructions, refer to Section “IPL from ESCON or FICON Attached Tape” (page 20).
  • Page 35 • The IP address of a gateway to reach the server • The IP address of your domain name server (DNS) 2.5.1 z/VM Installation After the kernel has completed its start-up routines, answer a few questions regarding the network setup. First, select the type of network connection to use: OSA-2, OSA Express, or HiperSockets.

  • Page 36: Connecting To The Suse Linux Enterprise Server Installation System

    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 (tr0, eth0, ctc0, escon0, iucv0, or hsi0) with correct settings.
  • Page 37 is given here for entry into your Java-enabled browser to connect to the installation system. 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.
  • Page 38 2.6.3 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 and terminal emulator putty, which is available on CD 1 in the directory /dosutils/ putty/.

  • Page 39: A Appendix

    Appendix A.1 Network Connection Types SUSE® Linux Enterprise Server for IBM System z includes network drivers for OSA devices (token ring, ethernet, and gigabit ethernet) and HiperSockets. This chapter de- scribes the configuration within the SUSE Linux Enterprise Server installation system. WARNING: CTC, ESCON, and IUCV Interfaces No Longer Supported CTC, ESCON, and IUCV interfaces are no longer officially supported.
  • Page 40 Example A.1 Supported Network Connection Types Please select the type of your network device. 1) OSA-2 or OSA Express 2) HiperSockets 3) Channel To Channel (CTC) [unsupported] 4) ESCON [unsupported] 5) Inter-User Communication Vehicle (IUCV) [unsupported] > 1 Please choose the CCW bus interface. 1) QDIO 2) LCS >...
  • Page 41 Example A.3 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 If you need a gateway to reach the server, enter the IP address of the gateway.

  • Page 42: The Parmfile-Automating The System Configuration

    Next, enter the full hostname. Then choose manual configuration and enter the IP ad- dress, netmask, broadcast address, IP address of the gateway, and IP address of the DNS server. Example A.5 Network Device Name Fully qualified hostname> earth.cosmos.com Automatic configuration via DHCP? 1) Yes 2) No >...
  • Page 43 The number of lines in the parmfile is limited to 10. Specify more than one parameter on a line. Parameter names are not case-sensitive. Separate the parameters by spaces. You may specify the parameters in any order. Always keep the PARAMETER=value string together in one line.
  • Page 44 A.2.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 45 • Interfaces ctc and escon (CTC and ESCON are no longer officially supported): ReadChannel=0.0.0424 WriteChannel=0.0.0425 ReadChannel specifies the READ channel to use. WriteChannel is the WRITE channel. • For the ctc interface (no longer officially supported), specify the protocol that should be used for this interface: CTCProtocol=<0/1/2>...
  • Page 46 For ReadChannel, enter the number of the READ channel. For WriteChannel, enter the number of the WRITE channel. DataChannel specifies the DATA channel. For Portname, enter an appropriate port name. Make sure that the READ channel carries an even device number. •...
  • Page 47 IMPORTANT: X Authentication Mechanism The direct installation with the X Window System relies on a primitive au- thentication mechanism based on hostnames. This mechanism is disabled on current SUSE Linux Enterprise Server versions. Installation with SSH or VNC is preferred. To allow a connection between YaST and the remote X server, run xhost <IP address>...

  • Page 48: Using The Vt220 Terminal Emulator

    Example A.7 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 Gateway=192.168.1.3 Nameserver=192.168.1.4 InstNetDev=hsi layer2=0 Netmask=255.255.255.128 Broadcast=192.168.1..255 readchannel=0.0.702c writechannel=0.0.702d datachannel=0.0.702e install=nfs://192.168.1.5/SLES-10-CD-s390x/CD1/ UseSSH=1 SSHPassword=testing linuxrcstderr=/dev/console A.3 Using the vt220 Terminal Emulator Recent MicroCode Levels allow the use of an integrated vt220 terminal emulator in addition to the standard line mode terminal.
  • Page 49 The resulting parameters line would look like the following example: parameters = "root=/dev/dasda2 TERM=dumb console=ttyS0 console=ttyS1" Save the changes in /etc/zipl.conf, run zipl, and reboot the system. Appendix...

Table of Contents