1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. LINUX ENTERPRISE 10 SP1 - LINUX AUDIT
  6. Specification

Novell LINUX ENTERPRISE SERVER 10 SP1 - ARCHITECTURE-SPECIFIC INFORMATION Specification

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

Advertisement

Quick Links

Download this manual See also: Manual, Quick Manual
SUSE Linux Enterprise
Server
10 SP1
March 15, 2007
Architecture-Specific Information
www.novell.com

Advertisement

Table of Contents
loading

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

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

  • Page 1 SUSE Linux Enterprise Server 10 SP1 www.novell.com Architecture-Specific Information March 15, 2007...
  • 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 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

    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 or SMB installation sources. 512 MB For installation using VNC.

  • Page 13: Ipl Options

    • 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 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 z/VM 4.4 All necessary fixes and enhancements included.

  • Page 15: Installation Types

    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. Find it in /dosutils/ tightvnc of CD 1.

  • 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 This example shows how to dedicate a DASD to one specific LPAR. This LPAR is referred to as LPAR1. Example 1.1 Dedicating DASD to One LPAR CHPID PATH=FD,TYPE=DSD,SHARED CNTLUNIT CUNUMBR=FD00,PATH=FD,UNITADD=((00,256)),UNIT=3990-2 IODEVICE ADDRESS=(FD03,1),CUNUMBR=FD00,UNIT=3390,PART=LPAR1 To share a DASD among LPARs, delete the PART=LPAR1 part in the IOCDS definition. This might be useful for high availability reasons or for sharing data among LPARs read-only.

  • 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 IMPORTANT: Exporting Mounted Devices with NFS Exporting the file system root (/) does not imply the export of mounted devices, such as CD-ROM. Explicitly name the mount point in /etc/exports: /media/cdrom *(ro) After changing this file, restart the NFS server with the command rcnfsserver restart.
  • Page 24 SMB protocol, already included in the Windows operating system. Be sure to activate SMB over TCP/IP as this enables the encapsulation of SMB packages into TCP/IP packages. Find details in the Windows online help or other Windows-related documen- tation that covers networking. Another option is to use FTP. This also requires some third-party software for Windows.

  • Page 25: Installation Types

    2.2 Installation Types This section provides information about which steps must be performed to install SUSE Linux Enterprise Server for each of the installation modes and where to find the appro- priate information. After the preparations mentioned in the previous chapters have been accomplished, follow the installation overview of the desired installation mode to install SUSE Linux Enterprise Server on your system.

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

    4 Connect to the SUSE Linux Enterprise Server installation system. See Section 2.6, “Connecting to the SUSE Linux Enterprise Server Installation System” (page 26). 5 Start installation using YaST and IPL the installed system. See Chapter 3, Instal- lation with YaST (↑Installation and Administration). 2.3 Preparing the IPL of the SUSE Linux Enterprise Server Installation System...
  • Page 27 Example 2.1 An Example IOCDS CHPID PATH=FD,TYPE=DSD,PART=(Z1) CHPID PATH=FE,TYPE=OSA,PART=(Z1) CHPID PATH=10,TYPE=CNC,PART=(Z1) CNTLUNIT CUNUMBR=FD00,PATH=FD,UNITADD=((00,1)),UNIT=3990-2 IODEVICE ADDRESS=(FD00,1),CUNUMBR=FD00,UNIT=3390 CNTLUNIT CUNUMBR=FE20,PATH=FE,UNIT=OSA,UNITADD=((20,1)) IODEVICE ADDRESS=(FE20,1),CUNUMBR=FE20,UNIT=OSA,PART=Z1 CNTLUNIT CUNUMBR=100A,PATH=10,UNIT=3480,UNITADD=((0A,1)) IODEVICE ADDRESS=100A,CUNUMBR=100A,UNIT=3480,PART=Z1 Proceed with Section 2.4.1, “LPAR Installation” (page 19). 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.
  • 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

    The last command returns a reader file number. This number is needed for the next command: RECEIVE <number> USER DIRECT A (REPL) Assign the directories to the guest with DIRMAP USER DIRECT A. You can now log in on the guest as user LINUX1. Proceed with Section 2.4.2, “z/VM Installation”...
  • Page 30 /boot/parmfile /boot/initrd as binary files from CD 1 (for example, using FTP from a Linux workstation). Name them SLES10 IMAGE SLES10 PARM SLES10 INITRD 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.
  • Page 31 IPL from the z/VM Reader Transferring the Installation System via FTP You need a working TCP/IP connection and an FTP client program within your newly defined z/VM guest. Setting up TCP/IP for z/VM is beyond the scope of this manual. Refer to the appropriate IBM documentation.
  • Page 32 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 220 ftpserver FTP server (Version wu-2.4.2-academ[BETA-18](1) Fri May 07 19:16:59 GMT 2004) ready. USER lininst 331 Password required for lininst PASS ****** 230 User lininst logged in.

  • Page 33: Network Configuration

    Creating a Start Script It is convenient to write a small REXX script to IPL the Linux installation system. This script loads the kernel, parmfile, and the initial RAM disk into the reader for IPL. Example 2.5 SLES10 EXEC XEDIT SLES10 EXEC /**/ 'close rdr' 'purge rdr all'...
  • Page 34 then select the type of network protocol you will be installing over. Section 2.1, “Making the Installation Data Available” (page 11) describes how to make the instal- lation data available for the various types of network connections. Currently, FTP, HTTP, NFS, and SMB/CIFS (Windows file sharing) are supported. Now set up the network device over which to receive the installation data: OSA-2 or OSA Express or HiperSockets.
  • Page 35 OSA control channel (0.0.0702). After entering the channels, insert the name of the port to which the OSA card is connected. SUSE Linux Enterprise Server now tries to load the network module by building a pa- rameter line with the information provided then displays all loaded modules. Loading was successful if you get an output like: Example 2.6 Network Device Driver Parameters qeth: Device 0.0.0700/0.0.0701/0.0.0702 is a Guest LAN QDIO card (level:...

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

    Example 2.7 Example ifconfig /sbin/ifconfig eth0 : Link encap:Ethernet HWaddr 02:00:01:00:00:27 inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::200:100:100:27/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 Mb) TX bytes:0 (0.0 Mb) 2.6 Connecting to the SUSE Linux Enterprise Server Installation...
  • Page 37 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/ 4 After the connection has been established, start installing SUSE Linux Enterprise Server with YaST.
  • Page 38 A login prompt appears. Enter root and log in with your password. Then enter yast2 to start YaST. Proceed with the detailed description of the installation procedure that can be found in Chapter 3, Installation with YaST (↑Installation and Administration). Architecture-Specific Information...

  • 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 nection Manually” (Chapter 30, Basic Networking, ↑Installation and Administra- tion). HostIP=192.168.55.23 Enter the IP address of the interface to configure. Gateway=192.168.55.254 Specify the gateway to use. Nameserver=192.168.123.123 Specify the DNS server in charge. InstNetDev=osa Enter the type of interface to configure. Possible values are osa, hsi. ctc, escon, and iucv.
  • Page 45 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> Valid entries would be: Compatibility mode, also for non-Linux peers other than OS/390 and z/OS (this is the default mode) Extended mode Compatibility mode with OS/390 and z/OS...
  • 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 server on the installing machine, and Display_IP causes the installing system to try to connect to an X server at the given address. Only one of these parameters should be set at any time. IMPORTANT: X Authentication Mechanism The direct installation with the X Window System relies on a primitive au- thentication mechanism based on hostnames.

  • Page 48: Using The Vt220 Terminal Emulator

    Example A.6 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-10-s390x/DVD1 autoyast=http://192.168.0.5/autoinst.xml linuxrcstderr=/dev/console usevnc=1 vncpassword=testing 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...
  • Page 49 As soon as the vt220 emulation is available, an icon for an integrated vt220 ASCII console appears next to the icon for the 3215 console on the HMC/SE. Make sure that you do not apply the changes as described above to a system that does not support vt220 terminal emulators.

Table of Contents