1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. LINUX ENTERPRISE SERVER 10 SP3 -...
  6. Supplementary manual

Novell LINUX ENTERPRISE SERVER 10 SP3 - ARCHITECTURE-SPECIFIC Supplementary Manual

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

Advertisement

Quick Links

Download this manual See also: Administration Manual, Installation Manual
SUSE Linux Enterprise
Server
10 SP3
October 27, 2009
Architecture-Specific Information
www.novell.com

Advertisement

Table of Contents
loading

Related Manuals for Novell LINUX ENTERPRISE SERVER 10 SP3 - ARCHITECTURE-SPECIFIC

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

  • Page 1 SUSE Linux Enterprise Server 10 SP3 www.novell.com Architecture-Specific Information October 27, 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 Introduction 1 General Information and Requirements System Requirements ......Installation Types ......IPL Options .

  • Page 5: Introduction

    Find a short introduction to SUSE Linux Enterprise Server on IBM System z in Start-Up Guide of which you received a printed copy. Find a detailed description of the installation procedure and the administration of SUSE Linux Enterprise http://www Server in Installation and Administration, which you can find at .novell.com/documentation/sles10/.

  • 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 at http://www.redbooks.ibm.com. 4.1 IBM System z with SUSE Linux Enterprise Find additional in-depth technical documentation about the kernel and application topics on IBM System z with SUSE Linux Enterprise Server at the following location: •...
  • Page 8 4.3 General Documents about Linux on IBM System z A general coverage of Linux on IBM System z can be found in the following documents: • Linux on IBM eServer zSeries and S/390: ISP and ASP Solutions (SG24-6299) These documents might not reflect the current state of Linux, but the principles of Linux deployment outlined there remain accurate.
  • Page 9 4.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: • Linux on IBM eServer zSeries and S/390: Large Scale Deployment (SG24-6824) • Linux on IBM eServer zSeries and S/390: Performance Measuring and Tuning (SG24-6926) •...

  • 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-EC) 2094 • IBM eServer 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 13: Ipl Options

    • OSA Express Ethernet (including Fast and Gigabit Ethernet) • OSA Express High-Speed Token Ring (only available on z800, z900, z890, and z990) • HiperSockets or Guest LAN • 10 GBE, VSWITCH The following interfaces are still included, but no longer supported: •...
  • Page 14 For the installation of SUSE Linux Enterprise Server on IBM System z, the MicroCode levels and z/VM APARs outlined in the following are required. OSA-Express QDIO zSeries 990 Driver 52G, EC, J12558 at level 116 or later zSeries 890 Driver 52G, EC, J12558 at level 116 or later zSeries 900 Driver 3G, OSA microcode level 3.0A MCLs: J11204.007 and J11204.008 (available May 3, 2002)
  • Page 15 1.1.3 Software To install SUSE Linux Enterprise Server via non-Linux–based NFS or FTP, you might experience problems with NFS or FTP server software. Especially the Windows standard FTP server can cause errors, so installing via SMB on these machines is generally rec- ommended.

  • Page 16: Installation Types

    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. Basically, these two types are given: LPAR , LPAR Installation of SUSE Linux Enterprise Server using a logical partition (LPAR). VM (z/VM) Installation of SUSE Linux Enterprise Server as as a guest operating system within z/VM.

  • Page 17: Ipl Options

    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 DVD-ROM or server options are discussed. Installing the software packages, which is done over the network, does not require the IPL medium.

  • Page 18: The Iocds

    content area on the right. In the Tasks area, expand Recovery and click Load from CD- ROM or Server. Now either choose Hardware Management Console DVD-ROM or FTP Source. If having chosen the latter option, provide the servers address or name and your credentials. In case the suse.ins file is not located in the root directory of the server, provide the path to this file.
  • Page 19 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. Several Linux systems can use the same network device if you share it among LPARs or z/VM guests.

  • 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 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 23 SUSE Linux Enterprise Server on DVD DVD 1 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 24: Installation Types

    TIP: SMB Installation Path for YaST Consult the README from the highest directory of DVD 1 for detailed informa- tion 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/S390 or LINUX-only mode with an appropriate activation profile and IOCDS. Consult IBM documentation for more on 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 1024 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 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 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 DVD-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 locsite 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 copy vmrdr.ikr (the Linux kernel) and initrd (the installation image) as binary files, so use the binary transfer mode. parmfile and sles10.exec need to be transferred in ASCII mode. 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.
  • Page 33 Example 2.4 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 34 Use the REXX script sles10.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 2.5 SLES10 EXEC /* REXX LOAD EXEC FOR SUSE LINUX S/390 VM GUESTS /* LOADS SUSE LINUX S/390 FILES INTO READER SAY '' SAY 'LOADING SLES10 FILES INTO READER...'...

  • Page 35: Network Configuration

    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 36 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 Express or HiperSockets. In this example installation, OSA Express is used. The system now displays a possible OSA configuration.

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

    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. Example 2.7 Example ifconfig /sbin/ifconfig eth0 : Link encap:Ethernet HWaddr 02:00:01:00:00:27...
  • Page 38 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 39 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 DVD 1 in the directory /dosutils/ putty/.

  • Page 41: 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 42 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 43 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 44 Example A.4 Network Device Driver Parameters Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets -------------------- 3) Channel To Channel (CTC) 4) ESCON 5) Inter-User Communication Vehicle (IUCV) > Please choose the CCW bus interface. 1) QDIO 2) LCS >...

  • Page 45: The Parmfile-Automating The System Configuration

    > Enter the relative port number> 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>...
  • Page 46 The following parameters can be passed to the installation routine, which takes them as default values for installation. All IP addresses, server names, and numerical values are just examples. Replace these values with the ones needed in your installation sce- nario.
  • Page 47 Also other linuxrc specific options such as for debugging have to be specified in the parmfile to be effective. TIP: Creating a File with Autoinstallation Information At the very end of the installation of a system you can check Clone This System for Autoyast.
  • Page 48 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 49 • 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 50 • Interface hsi for HiperSockets and VM guest LANs: ReadChannel=0.0.0624 WriteChannel=0.0.0625 DataChannel=0.0.0626 For ReadChannel, enter the appropriate number for the READ channel. For WriteChannel and DataChannel, enter the WRITE and DATA channel numbers. A.2.3 Specifying the Installation Source and YaST Interface Install=nfs://server/directory/DVD1/ Specify the location of the installation source to use.
  • Page 51 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> with the address of the installing machine on the remote machine. For VNC, specify a password of six to eight characters to use for installation: VNCPassword=<a password>...

  • Page 52: 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-s390x/DVD1/ 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 53 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