Related Manuals for Novell LINUX ENTERPRISE SERVER 10 - ARCHITECTURE-SPECIFIC INFORMATION 08-04-2006
Summary of Contents for Novell LINUX ENTERPRISE SERVER 10 - ARCHITECTURE-SPECIFIC INFORMATION 08-04-2006
- Page 1 SUSE Linux Enterprise Server www.novell.com Architecture-Specific Information August 04, 2006...
- Page 2 Novell, the Novell logo, the N logo and SUSE are registered trademarks of Novell, Inc. in the United States and other countries. * Linux is a registered trademark of Linus Torvalds. All other third party...
-
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 http://www.vm.ibm.com/pubs/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: Installation Types
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. With SMB To make the installation media available with SMB, just insert the SUSE Linux Enter- prise Server CD 1 into the CD drive of the Windows workstation. - Page 25 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. As described in Section 2.1, “Making the Installation Data Available” (page 21), 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 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). 2.4 IPLing the SUSE Linux Enterprise Server Installation System 2.4.1 LPAR Installation There are different ways to IPL SUSE Linux Enterprise Server into an LPAR. - Page 30 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. 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...
- Page 31 Log in as the z/VM Linux guest to IPL. Make the content of the directory /boot on CD 1 of the SUSE Linux Enterprise Server for IBM System z available by FTP within your network. From this directory, get the files vmrdr.ikr, initrd, and parmfile. The example shows the steps necessary.
- 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 “Making the Installation Data Available” (page 21) 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 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: V448) with link type GuestLAN QDIO (portname: VSW1) qeth: Hardware IP fragmentation not supported on eth0...
-
Page 36: Connecting To The Suse Linux Enterprise Server Installation System
2.6 Connecting to the SUSE Linux Enterprise Server Installation System After setting up your network connection, linuxrc prompts for the details of the instal- lation source chosen earlier in the process, for example, the server IP address and the directory in which the data is located. Finally, linuxrc wants to know what type of display you want to use to control the in- stallation procedure. - Page 37 2.6.2 Initiating the Installation for the X Window System IMPORTANT: X Authentication Mechanism The direct installation with the X Window System relies on a primitive authen- tication mechanism based on hostnames. This mechanism is disabled on current SUSE Linux Enterprise Server versions. Installation with SSH or VNC is preferred. 1 Make sure that the X server allows the client (the system that is installed) to connect.
-
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 InstNetDev=osa Enter the type of interface to configure. Possible values are osa, hsi. ctc, escon, and iucv. (CTC, ESCON, and IUCV are no longer officially supported). For the interfaces of type hsi and osa, specify an appropriate netmask and an optional broadcast address: Netmask=255.255.255.0 Broadcast=192.168.255.255...
- Page 45 Compatibility mode with OS/390 and z/OS • Network device type osa with interface lcs: ReadChannel=0.0.0124 Portname=1 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.
- Page 46 A.2.3 Specifying the Installation Source and YaST Interface Install=nfs://server/directory/CD1/ Specify the location of the installation source to use. Possible protocols are nfs, smb (Samba/CIFS), ftp, and http. If an ftp or smb URL is given, specify the user and password for FTP installation. These parameters are optional and anonymous or guest login is assumed if they are not given.
-
Page 47: Using The Vt220 Terminal Emulator
SSHPassword=<a password> 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. The vt220 terminal is connected to /dev/ ttyS1. The line mode terminal is connected to /dev/ttyS0. To activate vt220 support on your machine, edit /etc/inittab as user root.