User manual NOVELL LINUX ENTERPRISE SERVER 10 ARCHITECTURE-SPECIFIC INFORMATION 08-04-2006

[. . . ] SUSE Linux Enterprise Server 10 August 04, 2006 www. novell. com Architecture-Specific Information Architecture-Specific Information List of Authors: Wolfgang Engel, Berthold Gunreben, Ulrich Hecht, Jana Jaeger, Bernhard Kaindl, Ihno Krumreich, Susanne Oberhauser, Hannes Reinecke, Jörg Reuter, Tanja Roth, Thomas Rölz, Thomas Schraitle, Frank Sundermeyer, Rebecca Walter This publication is intellectual property of Novell Inc. Its contents can be duplicated, either in part or in whole, provided that a copyright label is visibly located on each copy. All information found in this book has been compiled with utmost attention to detail. Neither SUSE LINUX GmbH, the authors, nor the translators shall be held liable for possible errors or the consequences thereof. [. . . ] For further information about how to set up the IOCDS for Linux, refer to IBM hardware documentation of your machine (http://www . s390. ibm. com/linux/press. html). 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 29). 26 Architecture-Specific Information 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. The example shows the directory for a user LINUX1 with the password LINPWD, 256 MB of memory (extendable up to 512 MB), 32 MB of expanded RAM (XSTORE), some minidisks (MDISK), two CPUs and an OSA QDIO device. TIP: Assigning Memory to z/VM guests When assigning memory to a z/VM guest, make sure that the memory size suits the needs of your preferred installation type. See Section "Memory Requirements" (page 12). Preparing for Installation 27 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 SHARE RELATIVE 2000 XSTORE 32M CONSOLE 01C0 3270 A SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 3203 A * OSA QDIO DEVICE DEFINITIONS DEDICATE 9A0 9A0 DEDICATE 9A1 9A1 DEDICATE 9A2 9A2 * LINK MAINT 0190 0190 RR LINK MAINT 019E 019E RR LINK MAINT 019D 019D RR * MINIDISK DEFINITIONS MDISK 201 3390 0001 0050 DASD40 MR ONE4ME TWO4ME THR4ME MDISK 150 3390 0052 0200 DASD40 MR ONE4ME TWO4ME THR4ME MDISK 151 3390 0253 2800 DASD40 MR ONE4ME TWO4ME THR4ME This example uses minidisk 201 as the guest's home disk. Now add (as the user MAINT) the guest to the user directory with DIRM FOR LINUX1 ADD. Set up the environment of the user with: DIRM DIRECT DIRM USER WITHPASS The last command returns a reader file number. This number is needed for the next command: RECEIVE <number> USER DIRECT A (REPL) 28 Architecture-Specific Information Assign the directories to the guest with DIRMAP USER DIRECT A. 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. The preferred way is to use the Load from CD-ROM or server feature of the SE or HMC. IPL from CD-ROM Mark the LPAR to install and select Load from CD-ROM or server. Leave the field for the file location blank or enter the path to the root directory of the first CD-ROM then select continue. Operating system messages should now show the kernel boot messages. 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 Enterprise Server installation system. One is to copy the files: /boot/tapeipl. ikr /boot/parmfile /boot/initrd as binary files from CD 1 (for example, using FTP from a Linux workstation). Name them Preparing for Installation 29 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. Example 2. 3 REXX Script to Create an IPLable Tape 'REWIND 181' 'FILEDEF IN1 DISK' SLES10 IMAGE A 'FILEDEF IN2 DISK' SLES10 PARM A 'FILEDEF IN3 DISK' SLES10 INITRD A 'FILEDEF OUT TAP1 (RECFM F BLOCK 1024 LRECL 1024 PERM' say 'Writing: ' left(file1, 23) 'MOVEFILE IN1 OUT' say 'Writing: ' left(file2, 23) 'MOVEFILE IN2 OUT' say 'Writing: ' left(file3, 23) 'MOVEFILE IN3 OUT' say 'Done. ' 'REWIND 181' exit The tape in this script is attached as 181. Adjust the script to your needs. 2. 4. 2 z/VM Installation This section is about IPLing the installation system to install SUSE Linux Enterprise Server for IBM System z on a z/VM system. 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. Refer to the appropriate IBM documentation. 30 Architecture-Specific Information 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. 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. [. . . ] HostIP=192. 168. 55. 23 Enter the IP address of the interface to configure. Nameserver=192. 168. 123. 123 Specify the DNS server in charge. Appendix 43 InstNetDev=osa Enter the type of interface to configure. 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 For the interfaces of type ctc, escon, and iucv (CTC, ESCON, and IUCV are no longer officially supported), enter the IP address of the peer: Pointopoint=192. 168. 55. 20 OsaInterface=<eth|tr> OsaMedium=<lcs|qdio> For osa network devices, specify the physical medium (eth for ethernet or tr for token ring) and the host interface (qdio or lcs). Layer2=<0|1> For osa QDIO Ethernet devices, specify whether to enable OSI Layer 2 support. [. . . ]