linux on ibm system z: rhel 4.0 and sles 9 installation ... · emc corporation corporate...

Linux on IBM System z:RHEL 4.0 and SLES 9

Installation and Configuration GuideP/N 300-004-689

REV A01

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

2

Copyright © 2007 EMC Corporation. All rights reserved.

Published March, 2007

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

Linux on IBM System z: RHEL 4.0 and SLES 9 Installation and Configuration Guide

Contents

Chapter 1 IntroductionOverview.............................................................................................. 6EMC Symmetrix storage array specific settings............................. 7Preparing the LPAR for FCP connectivity....................................... 8

Fibre Channel zoning...................................................................9DM-MPIO .......................................................................................... 11

Chapter 2 Installation of the SLES 9 operating systemPreparing for a network installation of the SLES 9...................... 14Installing SLES 9 as a guest under z/VM...................................... 15Installing SLES 9 on an LPAR ......................................................... 19Completing the installation of SLES 9 on the LPAR .................... 36IPL of the Linux LPAR instance and z/VM final step................. 61

Linux LPAR .................................................................................61Add FCP devices using the Yast tools .....................................77Add more FCP devices using command line .........................80

SLES 9 DM-MPIO installation and configuration........................ 83

Chapter 3 Installation of the RHEL 4.0 operating systemPreparing for a network installation of the RHEL 4.0 ................. 86Installing RHEL 4.0 as a guest under z/VM................................. 88Installing RHEL 4.0 on an LPAR..................................................... 92Completing the installation of RHEL 4.0..................................... 103Adding FCP devices during installation of RHEL 4.0............... 108Partition DASD devices during the installation of RHEL 4.0 .. 112IPL of the Linux LPAR instance and z/VM final step............... 117

Linux LPAR ...............................................................................117

Linux on IBM System z: RHEL 4.0 and SLES 9 Installation and Configuration Guide 3

Contents

FCP connectivity ............................................................................. 123Composition of the /etc/zfcp.conf file ................................. 123System configuration for FCP attach ..................................... 124Add FCP devices using the command line........................... 128

RHEL 4.0 DM-MPIO installation and configuration................. 131

Linux on IBM System z: RHEL 4.0 and SLES 9 Installation and Configuration Guide4

1

This chapter provides information needed before installing the SLES 9 or RHEL 4.0 operating system.

◆ Overview............................................................................................... 6◆ EMC Symmetrix storage array specific settings.............................. 7◆ Preparing the LPAR for FCP connectivity........................................ 8◆ DM-MPIO............................................................................................ 11

Introduction

Introduction 5

6

Introduction

OverviewThis document assists in the installation and configuration of:

◆ SLES 9 in an LPAR on the IBM zSeries

Refer to Chapter 2, ”Installation of the SLES 9 operating system.”

◆ RHEL 4.0 in an LPAR on the IBM zSeries

Refer to Chapter 3, ”Installation of the RHEL 4.0 operating system.”

Requirements ◆ LUN 000 is required for DM-MPIO configurations.

Unsupported features ◆ PowerPath® is not available for Linux on the IBM zSeries.

◆ EMC does not support device multipathing for /boot, /, or swap.


Introduction

EMC Symmetrix storage array specific settingsEMC® Symmetrix® storage arrays must be configured for Linux connectivity. Follow the guidelines in this section.

When attaching to the Symmetrix, the default FA settings should be used, as shown in the table below:

When attaching to a Symmetrix storage array and using DM-MPIO, EMC recommends that customers use a Symmetrix 6 running 5671 microcode or a Symmetrix 7 running 5771 or 5772 microcode.

Director bit Default setting

PP Point-to-Point

SPC2 SCSI Primary

EAN Enable Auto Negotiation

C Common Serial Number

EMC Symmetrix storage array specific settings 7

8

Introduction

Preparing the LPAR for FCP connectivityOn the mainframe, the IOCDS (Input Output Configuration Data Set) must be created to include the device information for the LPAR (IBM iSeries Logical Partitioning) where the Linux operating system will be installed. On mainframes, one defines the I/O to the hardware in an IOCDS which is stored in the processor controller on a hard drive.

The following hardware information is needed for the IOCDS:

◆ CHPID (Channel Path Identifier Information)

◆ CNTLUNIT (Control Unit Information)

◆ IODEVICE (Device Information)

The following example shows how to define FCP devices for two Linux LPARs:

CHPID,PATH=(CSS(1),50),SHARED, *

PARTITION=((LINUX01,LINUX02),(=)),PCHID=1B2,TYPE=FCP

CNTLUNIT,CUNUMBR=a000,PATH=((CSS(1),50)),UNIT=FCP

IODEVICE ADDRESS=(a000,024),CUNUMBR=(a000), * PARTITION=((CSS(1),LINUX01)),UNIT=FCP IODEVICE ADDRESS=(a070,032),CUNUMBR=(a000), * PARTITION=((CSS(1),LINUX02)),UNIT=FCP

In order for Linux to access the zSeries I/O channels, the IOCDS must exist to map the DASD device driver to the standard Linux names for DASD devices (i.e., /dev/dasda). The IOCDS is also required to provide FCP I/O access through the standard zSeries architecture. The FCP mapping allows logical FCP devices to be reported as standard Linux SCSI devices (i.e., /dev/sda).

zSeries FCP channels require a FICON card. Any port on a particular FICON card can be configured as either FICON or FCP in the IOCDS.

The mainframe administrator assigns the necessary channels, control unit, and devices to the Linux LPAR(s). Once the mainframe administrator has generated an LPAR configuration, the FCP channels need to be attached to the Fibre Channel fabric. Run the Fibre Channel cables for the previously assigned channel(s) to a Fibre Channel switch.

If the channels on the zSeries host are single mode, then the GBICs/SFPs within the switch must also be single mode.


Introduction

Alternatively, if the channels on the zSeries host are multimode, then the GBICs/SFPs on the switch must be multimode as well.

IMPORTANT!Multimode and single-mode cables and GBICs/SFPs are not interchangeable.

Once the cables have been attached, the channels should log into the switch and the WWPNs (World Wide Port Names) of the channel IDs should be reported.

An example of the correlation of the switch ports to the CHPIDs and the CHPIDs’ WWPNs follows:

An example of the WWPNs for the Symmetrix FA ports follows:

Fibre Channel zoning

At the switch level, zones must be created in order to associate the CHPID WWPNs to the Symmetrix FA WWPNs.

The following is an example of zones to be created for the zSeries host and added to the zone set:

s390_sles9_chpid50:50:05:07:64:01:80:93:1E

50:06:04:82:D5:2E:69:0250:06:04:82:D5:2E:69:0D

s390_sles9_chipd51:50:05:07:64:01:40:93:4150:06:04:82:D5:2E:69:0250:06:04:82:D5:2E:69:0D

Switch port CHPID# WWPN of CHPID

1/15 50 50:05:07:64:01:80:93:1E

1/16 51 50:05:07:64:01:80:93:41

Symmetrix FA port Symmetrix FA WWPN

FA03A0 50:06:04:82:D5:2E:69:02

FA14A0 50:06:04:82:D5:2E:69:0D

Preparing the LPAR for FCP connectivity 9

10

Introduction

Once the zones are created, they must be added to the active zone set and the zone set must be activated.

Once the LPAR has been configured appropriately for Symmetrix attach, the installation of the operating system may begin.

◆ For installation of SLES 9 in an LPAR on the IBM zSeries, refer to Chapter 2, ”Installation of the SLES 9 operating system.”

◆ For installation of RHEL 4.0 in an LPAR on the IBM zSeries, refer to Chapter 3, ”Installation of the RHEL 4.0 operating system.”


Introduction

DM-MPIOWhen using DASD devices via ESCON or FICON attach, multipathing is available via the zSeries microcode. The multipathing is transparent to the operating system and is handled solely by the zSeries I/O subsystem. Multipathing for FCP devices is not native to the zSeries subsystem and is handled by the Linux v2.6.x kernel multipathing solution.

DM-MPIO is the native multipathing functionality that is included in the Linux v2.6.x kernel. DM-MPIO requires the device-mapper, udev, hotplug, and device-mapper-multipath packages.

◆ For installation and configuration of DM-MPIO for the SLES operating system, refer to “SLES 9 DM-MPIO installation and configuration” on page 83.

◆ For installation and configuration of DM-MPIO for the RHEL 4.0 operating system, refer to “RHEL 4.0 DM-MPIO installation and configuration” on page 131.

DM-MPIO 11

12

Introduction


2

This chapter provides the following information to install the SLES 9 operating system.

◆ Preparing for a network installation of the SLES 9 ....................... 14◆ Installing SLES 9 as a guest under z/VM....................................... 15◆ Installing SLES 9 on an LPAR........................................................... 19◆ Completing the installation of SLES 9 on the LPAR ..................... 36◆ IPL of the Linux LPAR instance and z/VM final step.................. 61◆ SLES 9 DM-MPIO installation and configuration ......................... 83

Installation of the SLES9 operating system

Installation of the SLES 9 operating system 13

14

Installation of the SLES 9 operating system

Preparing for a network installation of the SLES 9Before installing the SLES 9 operating system, you must select and prepare for the method to be used. The SuSE Linux Enterprise Server installation media must be made available for a network installation via FTP, HTTP, and NFS or via local storage.

The FTP, HTTP, or NFS server used for the installation must be a separate server and must provide the entire contents of the ISO images for the initial release of SLES 9 and the subsequent quarterly update.

To preprare for a network installation of SLES 9:

1. Download the ISO images for the 31-bit S390 or 64-bit S390x SLES 9 installation from Novell/SuSE’s website at http://dowload.novell.com.

2. Create a mount point to which the contents of the ISO images will be exported.

For example:

mkdir /export/s390_sles9

3. Create a directory for the Core kernel, and the SLES 9 installer CDs.

Please refer to the Novell documentation, available at http://novell.com/documentation/ for the NFS Severs.

The host to be used for the network installation should now have the necessary files exported for the installation.



Installing SLES 9 as a guest under z/VM Log on to z/VM as the Linux guest account. You can use x3270 or Integrated 3270 console.

To install the SLES 9 as a guest under z/VM:

1. Obtain the SuSE Linux boot files via ftp.

The following example illustrates the procedure. In the example, the commands you would issue are bolded.

If you are not in CMS mode, enter it now.

i cms z/VM V5.2.0 2006-03-28 14:44 DMSACP723I Z (592) R/O Ready; T=0.01/0.01 22:55:27

If necessary, add the device containing z/VM's TCP/IP tools to your CMS disk list. For example:

vmlink tcpmaint 592 592 DMSVML2060I TCPMAINT 592 linked as 0592 file mode Z DMSVML2069E No NAMES file(s) found to search for nickname (592) Ready(00028); T=0.01/0.01 22:56:47

If using any of the qdio/qeth based network connection types (such as OSA express or hipersockets), set the VM guest qioassist parameter off:

set qioassist offReady; T=0.01/0.01 22:58:15

Query the guest for devices:

q disk LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTALLIN191 191 A R/W 5 3390 4096 1 8-01 892 900LIN192 192 D R/W 50 3390 4096 3 3968-44 5032 9000MNT190 190 S R/O 100 3390 4096 687 14513-81 3487 18000MNT19E 19E Y/S R/O 250 3390 4096 1010 26714-59 18286 45000TCM592 592 Z R/O 67 3390 4096 884 8523-71 3537 12060Ready; T=0.01/0.01 23:00:45

access 192 a DMSACC724I 192 replaces A (191) DMSACP726I 192 D released Ready; T=0.01/0.01 23:01:23

ftp 172.23.189.135

Installing SLES 9 as a guest under z/VM 15

16


VM TCP/IP FTP Level 520 Connecting to 172.23.189.135, port 21 220 (vsFTPd 1.2.1) USER (identify yourself to the host):

root >>>USER root 331 Please specify the password.

Password: xxxxxxx >>>PASS ******** 230 Login successful. Command:

bin >>>TYPE i 200 Type set to I.

locsite fix 80 Command:

cd <the NFS install directory/boot/>Command:

get vmrdr.ikr >>>PORT 9,185,246,26,4,5 200 PORT command successful. >>>RETR /sues/images/vmrdr.ikr 150 Opening BINARY mode data connection for vmrdr.ikr (1511884 bytes). 226 Transfer complete. 1511920 bytes transferred in 1.972 seconds. Transfer rate 766.69 Kbytes/sec. Command:

get initrd suse.initrd >>>PORT 9,185,246,26,4,7 200 PORT command successful. >>>RETR /suse/images/initrd 150 Opening BINARY mode data connection for initrd (9862505 bytes). 8299680 bytes transferred. 226 Transfer complete. 9862560 bytes transferred in 12.366 seconds. Transfer rate 797.55 Kbytes/sec. Command:

ascii >>>TYPE a 200 Type set to A. Command:

get parmfile parm.file >>>PORT 9,185,246,26,4,8 200 PORT command successful. >>>RETR parmfile



150 Opening ASCII mode data connection for parmfile (38 bytes). 226 Transfer complete. 40 bytes transferred in 0.081 seconds. Transfer rate 0.49 Kbytes/sec. Command:

quit

2. Punch the Linux boot files to the virtual machine reader. The example below illustrates the procedure. This example shows commands used to punch Linux boot files to the virtual machine reader. When you punch files to the reader, note the spool identifiers (0126, 0127, and 0128 in the example–yours will differ) so if there are other reader files preent you can queue (ORDER) the reader files in the proper order.

spool punch * close Ready;

punch vmrdr ikr a (noh RDR FILE 0126 SENT FROM LINMSTR PUN WAS 0126 RECS 3129 CPY 001 A NOHOLD NOKEEP Ready; punch parm file a (noh RDR FILE 0127 SENT FROM LINMSTR PUN WAS 0127 RECS 3129 CPY 001 A NOHOLD NOKEEP Ready;punch suse initrd a (noh RDR FILE 0128 SENT FROM LINMSTR PUN WAS 0128 RECS 3129 CPY 001 A NOHOLD NOKEEP Ready; order reader 126 127 128 0000003 FILES ORDERED Ready;

Note: If you forget the spool file identifiers, issue QUERY RDR ALL.

3. Boot (IPL) Linux from the virtual machine reader. The example below shows how you get the Linux installation and configuration started by booting (IPL) the virtual machine reader.

ipl 00c clear ...

Installing SLES 9 as a guest under z/VM 17

18


For instructions to successfully complete the installation of the operating system go to “Please select the type of network device:” on page 25.

Examples:

0) no network1) OSA Token Ring (LCS)2) OSA Ethernet (LCS)3) OSA-Gigabit Ethernet or OSA-Express Fast Ethernet

(QDIO)4) Channel to Channel5) Escon6) IUCV7) Hipersockets8) OSA High speed Token Ring (QDIO)9) Show subchannels and deteceted devices

Enter your choice (0-10):

# 3

For guest under z/VM, refer to continue with “Loading qeth....” on page 26".



Installing SLES 9 on an LPARThis section provides the steps required to install SLES 9 on an LPAR. Specifically, it explains the steps taken at the HMC (Hardware Management Console) prior to the installation and then explains the installation steps. For further information refer to the chapter entitled, "Booting from HMC CD-ROM or FTP server" in the Linux for IBM e-server zSeries and S/390: Distributions Manual.

Note: An LPAR should already be created and resources allocated to it prior to the SLES Linux installation.

At least one FCP channel must be allocated to the target LPAR configuration for FCP device connectivity. The FICON channels in FCP mode provide full fabric support so that the IBM zSeries and S/390 systems have access to standard FCP and SCSI devices. Refer to the IBM zSeries documentation for further information.

Once the LPAR and its resources have been generated in a configuration, the target LPAR must be configured for the installation.

To configure the LPAR for the SLES 9 installation:

1. Log on to the HMC (Hardware Management Console).

2. Select Groups from the Views menu on the left-hand side of the window. The Recovery menu displays on the right-hand side of the window.

Installing SLES 9 on an LPAR 19

20


3. Double-click on the Defined CPCs icon in the Groups Work Area. The Defined CPCs Work Area displays.

4. Highlight the target CPC in the Defined CPCs Work Area and double-click the Single Object Operation icon from the CPC Recovery menu.



5. Once selected, the Single Object Operation window provides a list of object names from which to choose. Select the proper Object Name assigned to the LPAR targeted for the Linux installation and click Yes.


22


6. The Groups Work Area window displays. Double-click Images. The Images Work Area window shows all of the LPARs defined for this CPC.



7. Click on the LPAR targeted for the Linux installation. To initiate the installation process, double-click the Load from CD-ROM or Server icon from the CPC Recovery menu.

8. Confirmation is requested to continue with the load from the CD-ROM. Click OK if the correct target LPAR object name is displayed in the window.


24


9. Following this confirmation, the user is prompted to select the installation source. Select the source of the software, Hardware Management Console CD-ROM, and click OK to proceed.

10. When prompted to select the software to load, select: suse.ins Linux for S/390 Installation/Rescue System (Default).

11. Click OK to continue.



By selecting the suse.ins software, the necessary installation code is retrieved from the source CD-ROM. A Reset Clear is automatically performed on the target LPAR and then the installation load for the LPAR begins.

12. Once the installation method is selected, you are prompted with the questions listed below. Double-click on the Operation System Messages icon.

The device addresses and portname for the ethernet module must be entered. In this example, the OSA Gigabit Ethernet device is allocated to the target LPAR. Therefore, the qeth network module will be used.

Please select the type of network device:0) no network1) OSA Token Ring (LCS)2) OSA Ethernet (LCS)3) OSA-Gigabit Ethernet or OSA-Express Fast Ethernet (QDIO)4) Channel to Channel5) Escon6) IUCV7) Hipersockets8) OSA High speed Token Ring (QDIO)9) Show subchannels and deteceted devicesEnter your choice (0-10):

# 3


26


The appropriate driver for the OSA-Gigabit Ethernet or OSA-Express Fast Ethernet network board is the qeth module. It now loads.

Loading qeth....Detecting available channels ...qdio: loading QDIO base support version 2 ($Revision: 1.79.2.8 $/$Revision: 1.57 $/$Revision: 1.23.2.2 $)qeth: loading qeth S/390 OSA-Express driver ($Revision: 1.77.2.47 $/$Revision: 1.98.2.24 $/$Revision: 1.27.2.8 $/$Revision: 1.8.2.2 $/$Revision: 1.7.2.2 $/$Revision: 1.5.2.6 $/$Revision: 1.19.2.15 $ : Ipv6 :VLAN)Done

32 OSA Express, Gigabit Ethernet or High Speed Token Ring Channels were detected

Summary of all OSA Express, Gigabit Ethernet or High Speed Token Ring channels detected

Device Addresses CHPID(s)0200 010210 02



13. Enter the appropriate information for the target LPAR for your environment when prompted.

First OSA Express, Gigabit Ethernet or High Speed Token Ring channels that were detected:Device Addresses CHPID(s)0200 010201 010202 010203 010204 010205 010206 010207 010208 010209 01020a 01020b 01020c 01020d 01020e 01020f 01Format for OSA Express configuration: Read Channel, Write Channel, Data ChannelThe Read Channel must be an even device address,The Write Channel must be the Read Channel address plus 1,The Data Channel must be the Read Channel address plus 2.Possible configuration: read: 0x0200, write: 0x0201, data: 0x0202Enter the device addresses for the qeth module, e.g. '0.0.0200,0.0.0201,0.0.0202'# 0.0.0200,0.0.0201,0.0.0202


28


14. Enter the portname for the network board.

Please enter the portname (case sensitive) to use():# osa0200

Device 0.0.0200 configuredqeth: Device 0.0.0200/0.0.0201/0.0.0202 is a OSD Express card (level: 0627)With link type OSD_100 (portname: osa0100_qeth: Hardware IP fragmentation not suipported on eth0qeth: VLAN enabledqeth: Multicasst enabledqeth: IPV6 enabledqeth: Broadcast enabledqeth: Using SW checksumming on eth0qeth: Outbound TS0 not supported on eth0eth0 deteceted!eth0Link encap: Ethernet Hwaddr 00:09:6B:1A:5F:00

BROADCAST MULTICAST MTU:1492 Metric:1RX packets:0 errors:0 dropped:0 overruns:0 frame:0TX packets:0 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:1000RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth0 is available, continuing with network setup.



15. Depending upon the information provided by the network administrator, enter the necessary networking information for the Linux LPAR when prompted.

For example:

Please enter your full host name, e.g. 'linux.example.com' (linux.example.com):# sles9_s390x.lss.emc.comPlease enter your IP address, e.g. '192.168.0.1' (192.168.0.1):# 172.23.174.176Please enter the net mask, e.g. '255.255.255.0' (255.255.255.0):# 255.255.255.0Please enter the broadcast address if different from (172.23.174.255):# 172.23.174.255Please enter the gateway's IP address, e.g. '192.168.0.254' (192.168.0.254):# 172.23.174.2Please enter the IP address of the DNS server or 'none' for no DNS (none):# 168.159.48.49Please enter the DNS search domain, e.g. 'example.com' (lss.emc.com):# lss.emc.com


30


16. Enter the MTU value when prompted.

Please enter the MTU (Maximum Transfer Unit),leave blank for default: (1500):# <hit return>

17. The networking information entered displays. This provides an opportunity to correct any errors that may have been made.

Configuration for eth0 will be:Full host name: sles9_s390x.lss.emc.comIP address: 172.23.174.176Net mask: 255.255.255.0Broadcast address: 172.23.174.255Gateway address: 172.23.174.2DNS IP address: 168.159.48.49DNS search domain: lss.emc.comMTU size: 1500Is this correct (Yes/No)?

# Yes



18. The SuSE installation prompts the user to enter a temporary password. Follow the instructions and provide a password.

For security reasons you have to set a temporary installation system password for the user 'root'.

You'll be asked for it only when you telnet into this installation system to limit the access to it and it will be cleared as soon as you shut down or reset the installation system.

Please enter the temporary installation password:

# suse

At this point, the networking stack is loaded and tested with pings. Assuming the network configuration finishes successfully, the telnetd and ssh dameons start.

For example:

ifconfig eth0 172.23.174.176 netmask 255.255.255.0 broadcast 172.23.174.255 mtu 1500/sbin/ifconfig eth0:eth0Link encap: Ethernet Hwaddr 00:09:6B:1A:5F:00


32


inet add: 172.23.174.176 Bcast: 172.23.174.255 Mask: 255.255.255.0inet6 addr: fe80::9:6b00:111a:5f00/64 Scope: Link UPBROADCAST MULTICAST MTU:1500 Metric:1RX packets:0 errors:0 dropped:0 overruns:0 frame:0TX packets:2 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:1000RX bytes:0 (0.0 b) TX bytes:236 (236.0 b)

Trying to ping my IP address:PING 172.23.174.176 (172.23.174.176) 56(84) bytes of data.Trying to ping the IP address of the GatewayPING 172.23.174.2 (172.23.174.2) 56(84) bytes of data.Trying to ping the IP address of the DNS Server:PING 168.159.48.49 (168.159.48.49) 56(84) bytes of data.

Network Setup finished, running inetd ...You should be able to login via telnet now, for ssh wait a few seconds,Temporary host keys (only for installation) are being generated now:Generating /etc/ssh/ssh_host_key.Generating public/private rsa1 key pair.Your identification has been saved in /etc/ssh/ssh_host_key.

Your public key has been saved in /etc/ssh/ssh_host_key.pub

The key fingerprint is:35:bf:98:9e:b4:23:82:91:80:3f:47:02:49:a9:04:fd root@s390Generating /etc/ssh/ssh_host_dsa_key.Generating public/private dsa key pair.

The key fingerprint is:7e:a5:b2:ee:5b:dc:5c:fe:de:04:d3:a2:74:0c:c0:6f root@s390

Starting SSH daemonOct 6 18:45:22 suse sshd[3580]: Server listening on :: port 22...doneGeneration of temporary installation host keys finished.After installation, new, different SSH keys will be generated.

19. Select the method to be used for the installation.

In this example, NFS is selected.

Please specify the installation Source:1) NFS2) SAMBA3) FTP0) AbortChoice:1# 1



20. Enter the IP address of the NFS host.

Please enter the IP-Number of the host providing the installation media:# 172.23.189.135

21. Enter the path of the directory that contains the installation media.

Please enter the directory of the installation media:/wide_open/sles-iso/sles9/s390x/sp3

Is the following correct?Installation Source: nfsIP-Address: 172.23.189.135Directory: /wide_open/sles-iso/sles9/s390x/sp3Yes/No# Yes

Warning can't open /etc/fstab: No such file or directory


34


22. When prompted, select the mode in which the installation will proceed.

In this example, the XServer was unable to start so the options provided are text mode and VNC. VNC is selected for this installation.

Which terminal do want to use?1) X-Window2) VNC (VNC-Client or Java enabled Browser)3) sshChoice:2Please enter the Password for VNC-Access (6-8 characters):# dangerous>>> SUSE LINUX Enterprise Server 9 installation program v1.6.48 © 1996-2004 SUSE LINUX AG <<<<SCSI subsystem initializedSt: Version 20040318, fixed bufsize 32768, s/g segs 256Starting hardware detection....Searching for info file....



Driver Update: Service Pack 2Loading data into RAM disk... (53490 kB)...

Loading data into RAM disk... (6240 kB)...

Creating device nodes... doneintegrating the shared obhects of the installation system....integrating kernel modules of the installation system...starting slpd to announce VNC...starting yast...unpacked extension disk...OKstarting VNC servera log can be found in /tmp/vncserver.log....******You can connect to 172.23.178.222, display :1 now with vncviewer***Or use a Java capable browser on http://172.23.178.222:5801/***

For instructions to successfully complete the installation of the operating system, proceed to the next section, “Completing the installation of SLES 9 on the LPAR” on page 36.


36


Completing the installation of SLES 9 on the LPARThe LPAR has been prepared and configured for the installation of SLES 9. To perform the operating system installation, follow the steps outlined in this section.

Open a VNC Viewer to continue the install. The Linux install takes you through the following steps:

1. You are prompted to accept the license agreement.



2. Choose the language.

3. If you are attached to

• DASD devices select Configure DASD Disks.

• FCP devices select Configure ZFCP Disks.

• Both types of devices do both steps.

The next few screens describe the configuration of both DASD and FCP devices.

Completing the installation of SLES 9 on the LPAR 37

38




4. For DASD device configuration:

a. When you select the DASD button in the previous screen, the list of all attached DASD devices is displayed.

b. Select the DASD devices you will be using one by one and from the pull-down menu select Activate. The disks are activated.


40


c. Select the disks you have activated and from the Perform Action pull-down menu select Format. Press OK in the pop-up window.



d. Enter the number devices you want to format:


42


e. Confirm that you want to format the disks.

The disks are formatted.

f. When the formatting is completed, click Next.



The DASD Disk Management screen shows a checkmark beside the DASDs which have been configured.

5. Press Next to return to the s/390 Disk Controller Configuration screen.


44


6. Select Configure FCP Devices.



a. Select Add.


46


b. In the screen that follows, give FCP device information for each disk.



Once you have configured all FCP devices, they are all be listed as follows:

c. Click Next.


48


d. Select New Installation in the Installation Settings screen drop-down menu.



e. Click OK. The Installation setting screen displays the mode, partitioning, and software information.


50


f. Select Change, and from the drop-down menu select Partitioning. The Expert Partitioner screen displays. It shows all DASD and FCP devices available to install Linux LPAR.



g. Select Create. You are prompted to select the disk you want to create the partition(s) on.

The following example shows Linux being installed on the DASD devices.


52


h. As best practice, create /boot, / , swap, and /extra partitions. The /extra partition is be used to store IO and other useful user applications.



i. The screen below shows all the partitions created and their sizes. Click Next.


54


j. In the Installation Settings page, select Change and from the drop-down menu select Software.



k. The Software Selection screen displays. Select Detailed Selection.

l. The Package Selection screen displays. Make sure to select device-mapper, multipath-tools, udev, and gcc compiler packages. If any of these packages have dependencies, and other packages are selected along with these packages, accept them.


56


m. In the Installation Settings screen, select Accept to progress to the next step.



n. Confirm the start of installation by clicking Yes, install.

The installation begins.


58


o. Select the defaults in the next two screens.


60


p. In the Finishing Basic Installation window, click OK.

At this point the VNC disconnects. After the VNC is disconnected, log back in the HMC to LOAD the Linux LPAR. (Refer to “Linux LPAR” on page 61.)



IPL of the Linux LPAR instance and z/VM final stepOnce the installation has completed, the Linux instance and z/VM guest needs to be rebooted. In order for the instance to boot successfully, the image needs to be loaded. This is performed from the CPC Recovery menu on the HMC. For Linux LPAR, proceed to Step 1 on page 61.

From the CPC Images Working Area, for z/VM guest log onto integrated 3270 Console and booting (IPL) the virtual system. Issue the following commands:



For example: (150 is the DASD )

ipl 150 clear..

At this point the z/VM guest is booting (IPL). To complete the final steps proceed to Step 8 on page 65.

Linux LPAR

For Linux LPAR continue with the following steps:

1. Return to the HMC (Hardware Management Console).

2. Select Groups from the Views menu on the left-hand side of the window and select the CPC Recovery menu on the right-hand side of the window.

IPL of the Linux LPAR instance and z/VM final step 61

62


3. The LPAR images display in the Groups Work Area. Double-click Images.

The Images Work Area window displays and shows all of the LPARs defined for this CPC.



4. Highlight the LPAR on which Linux was installed and select the Load option from the CPC Recovery menu.

The Load window diplays.


64


5. Fill in the information in the Load window, including the proper DASD device address for the boot device.

For example:

CPC: PCT3CImage: Linux02Load Type: Normal X ClearStore Status:<Place a check in the check box here for Yes.>Load address:f834Load parameter:CKDTime-out value: 060

6. Once this information is submitted, the Load Task Confirmation window prompts the user to confirm the settings.

For example:

Load will cause jobs to be cancelled.CPC: PCT3CImage: Linux02Load Type: Normal Store Status:YesLoad address:147ELoad parameter:Time-out value:60

Click Yes to continue.



7. Confirm that the information is correct and load the Linux instance on the LPAR.

8. At this point, open a VNC Viewer to continue the install.

The Linux install takes you through the following steps.


66


a. Provide a password for the root user.



b. Enable remote administration for VNC.


68


c. Select appropriate options in the next few screens and complete the installation.



d. Select Skip Configuration and click next.


70


e. Select Local and click Next.



f. Click Next.


72


The Writing the system configuration window displays the progress.



g. At the Release Notes window, click Next.


74


h. At the Hardware Configuration window select Skip Configuration and click Next.



i. Click Finish.

At this point, the installation and configuration procedures are completed.


76


Use Putty tools from windows or Telnet/ssh on UNIX system to connect to the NEW LINUX LPAR:

Symmetrix storage array

sles9_s390x:~ # cat /proc/scsi/scsiAttached devices:Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: EMC Model: SYMMETRIX Rev: 5771 Type: Direct-Access ANSI SCSI revision: 04Host: scsi0 Channel: 00 Id: 02 Lun: 00 Vendor: EMC Model: SYMMETRIX Rev: 5771 Type: Direct-Access ANSI SCSI revision: 04Host: scsi1 Channel: 00 Id: 01 Lun: 00 Vendor: EMC Model: SYMMETRIX Rev: 5771 Type: Direct-Access ANSI SCSI revision: 04Host: scsi1 Channel: 00 Id: 02 Lun: 00 Vendor: EMC Model: SYMMETRIX Rev: 5771 Type: Direct-Access ANSI SCSI revision: 04sles9_s390x:~ #



Add FCP devices using the Yast tools To add FCP devices using the Yast tools:

1. Select Hardware and ZFCP.

2. Press Enter.


78


The Configured ZFCP Disks window displays.

3. Tab to Add and press Enter to go the next screen.

4. Select the next FCP device that you want to add (0.0.a072).



5. Enter the WWPN and FCP LUN for new device.

6. Tab to Next and press Enter.

When you finish, the Configured ZFCP Disks window displays.


80


7. Tab to Next and press Enter to exit the YAST tool:

8. To verify the new devices, issue the following command:

Example:

sles9_s390x:~ # cat /proc/scsi/scsiAttached devices:Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: EMC Model: SYMMETRIX Rev: 5771 Type: Direct-Access ANSI SCSI revision: 04Host: scsi0 Channel: 00 Id: 02 Lun: 00 Vendor: EMC Model: SYMMETRIX Rev: 5771 Type: Direct-Access ANSI SCSI revision: 04Host: scsi1 Channel: 00 Id: 01 Lun: 00 Vendor: EMC Model: SYMMETRIX Rev: 5771 Type: Direct-Access ANSI SCSI revision: 04Host: scsi1 Channel: 00 Id: 02 Lun: 00 Vendor: EMC Model: SYMMETRIX Rev: 5771 Type: Direct-Access ANSI SCSI revision: 04Host: scsi2 Channel: 00 Id: 01 Lun: 00 Vendor: EMC Model: SYMMETRIX Rev: 5771 Type: Direct-Access ANSI SCSI revision: 04Host: scsi2 Channel: 00 Id: 02 Lun: 00 Vendor: EMC Model: SYMMETRIX Rev: 5771 Type: Direct-Access ANSI SCSI revision: 04

Add more FCP devices using command line

To add more FCP devices using command line:

1. Bring the device online to the channel.

sles9_s390x:/sys/bus/ccw/drivers/zfcp # cat 0.0.a073/online0sles9_s390x:/sys/bus/ccw/drivers/zfcp # echo 1 > 0.0.a073/onlinesles9_s390x:/sys/bus/ccw/drivers/zfcp # cat 0.0.a073/online1

2. Add Symmetrix WWPN device 0.0.a070.

sles9_s390x:/sys/bus/ccw/drivers/zfcp # echo 0x50060482d52e6902 > 0.0.a073/port_addsles9_s390x:/sys/bus/ccw/drivers/zfcp # echo 0x50060482d52e690d > 0.0.a073/port_add

3. Add LUN to FCP manually.

sles9_s390x:/sys/bus/ccw/drivers/zfcp # echo 0x0073000000000000 > 0.0.a073/0x50060482d52e 6902/unit_addsles9_s390x:/sys/bus/ccw/drivers/zfcp # echo 0x0073000000000000 > 0.0.a073/0x50060482d52e 690d/unit_add

4. Create a new ramdisk.



For example:

sles9_s390x:/boot # mkinitrd -k image-2.6.5-7.244-s390x -i initrd-2.6.5-7.244-s390xRoot device: /dev/dasda2 (mounted on / as reiserfs)Module list: reiserfs dasd_eckd_mod sd_mod zfcpKernel image: /boot/image-2.6.5-7.244-s390xInitrd image: /boot/initrd-2.6.5-7.244-s390xShared libs: lib64/ld-2.3.3.so lib64/libblkid.so.1.0 lib64/libc.so.6 lib64/libselinux.so.1 lib64/libuuid.so.1.2Modules: kernel/fs/reiserfs/reiserfs.ko kernel/drivers/s390/block/dasd_mod.ko kernel/drivers/s390/block/dasd_eckd_mod.ko kernel/drivers/scsi/scsi_mod.ko kernel/drivers/scsi/sd_mod.ko kernel/drivers/s390/cio/qdio.ko kernel/drivers/s390/scsi/zfcp.koDASDs: 0.0.f834(ECKD) 0.0.f835(ECKD)zfcp HBAs: 0.0.a070 0.0.a071 0.0.a072 0.0.a073zfcp disks: 0.0.a070:0x50060482d52e6902:0x0070000000000000 0.0.a070:0x50060482d52e690d:0x0070000000000000 0.0.a071:0x50060482d52e6902:0x0071000000000000 0.0.a071:0x50060482d52e690d:0x0071000000000000 0.0.a072:0x50060482d52e6902:0x0072000000000000 0.0.a072:0x50060482d52e690d:0x0072000000000000 0.0.a073:0x50060482d52e6902:0x0073000000000000 0.0.a073:0x50060482d52e690d:0x0073000000000000Including: udevinitrd updated, zipl needs to update the IPL record before IPL!

5. Execute the zipl command to pick up the new initial ramdisk.

sles9_s390x:/boot # zipl -VUsing config file '/etc/zipl.conf'Target device information Device..........................: 5e:00 Partition.......................: 5e:01 Device name.....................: dasda DASD device number..............: f834 Type............................: disk partition Disk layout.....................: ECKD/compatible disk layout Geometry - heads................: 15 Geometry - sectors..............: 12 Geometry - cylinders............: 10017 Geometry - start................: 24 File system block size..........: 4096 Physical block size.............: 4096 Device size in physical blocks..: 51276Building bootmap in '/boot/zipl'Adding IPL section 'ipl' (default) kernel image......: /boot/image at 0x10000 kernel parmline...: 'root=/dev/dasda2 selinux=0 TERM=dumb elevator=cfq' at 0x1000 initial ramdisk...: /boot/initrd at 0x1000000


82


Preparing boot device: dasda (f834).Syncing disks...Done.

6. Reboot the system.

sles9_s390x:/boot # reboot

Broadcast message from root (pts/0) (Wed Jan 17 20:09:52 2007):

The system is going down for reboot NOW!

7. Log back in the system and verify the new FCP devices.

sles9_s390x:~ # cat /proc/scsi/scsiAttached devices:Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: EMC Model: SYMMETRIX Rev: 5771 Type: Direct-Access ANSI SCSI revision: 04Host: scsi0 Channel: 00 Id: 02 Lun: 00 Vendor: EMC Model: SYMMETRIX Rev: 5771 Type: Direct-Access ANSI SCSI revision: 04Host: scsi1 Channel: 00 Id: 01 Lun: 00 Vendor: EMC Model: SYMMETRIX Rev: 5771 Type: Direct-Access ANSI SCSI revision: 04Host: scsi1 Channel: 00 Id: 02 Lun: 00 Vendor: EMC Model: SYMMETRIX Rev: 5771 Type: Direct-Access ANSI SCSI revision: 04Host: scsi2 Channel: 00 Id: 01 Lun: 00 Vendor: EMC Model: SYMMETRIX Rev: 5771 Type: Direct-Access ANSI SCSI revision: 04Host: scsi2 Channel: 00 Id: 02 Lun: 00 Vendor: EMC Model: SYMMETRIX Rev: 5771 Type: Direct-Access ANSI SCSI revision: 04Host: scsi3 Channel: 00 Id: 01 Lun: 00 Vendor: EMC Model: SYMMETRIX Rev: 5771 Type: Direct-Access ANSI SCSI revision: 04Host: scsi3 Channel: 00 Id: 02 Lun: 00 Vendor: EMC Model: SYMMETRIX Rev: 5771 Type: Direct-Access ANSI SCSI revision: 04



SLES 9 DM-MPIO installation and configurationThe multipath-tools package provides the tools to manage multipath devices using device-mapper.

The multipath-tools package may be installed during the initial SLES 9 SP2 installation. If it is not, it can be found on CD2 of SLES 9 Service Pack 3 and can be manually installed.

For more information, refer to Native Multipath Failover Based on DM-MPIO for v2.6x Linux Kernel and EMC Storage Arrays, Red Hat Enterprise Linux 4 - U3 and SuSE Linux Enterprise Server 9 - SP3, Configuration Guide on http://Powerlink.EMC.com.

SLES 9 DM-MPIO installation and configuration 83

http://powerlink.emc.com

84



3

This chapter provides the following information to install the RHEL 4.0 operating system.

◆ Preparing for a network installation of the RHEL 4.0 .................. 86◆ Installing RHEL 4.0 as a guest under z/VM.................................. 88◆ Installing RHEL 4.0 on an LPAR...................................................... 92◆ Completing the installation of RHEL 4.0...................................... 103◆ Adding FCP devices during installation of RHEL 4.0................ 108◆ Partition DASD devices during the installation of RHEL 4.0.... 112◆ IPL of the Linux LPAR instance and z/VM final step................ 117◆ FCP connectivity .............................................................................. 123◆ RHEL 4.0 DM-MPIO installation and configuration .................. 131

Installation of the RHEL4.0 operating system

Installation of the RHEL 4.0 operating system 85

86

Installation of the RHEL 4.0 operating system

Preparing for a network installation of the RHEL 4.0Before installing the RHEL 4.0 operating system, you must select and prepare for the method to be used. The Red Hat Enterprise Linux installation media must be available for a network installation via FTP, HTTP, and NFS or via local storage.

The FTP, HTTP, or NFS server to be used for the installation must be a separate server and must provide the entire contents of the RedHat/ directory.

To create an NFS server, please follow the steps below:

1. Download the ISO images for the 31-bit s390 or 64-bit s390x RHEL 4.0 installation from RHN (Red Hat Network).

The installation procedure is the same for both 31-bit and 64-bit RHEL 4.0.

2. Create a mount point to which the contents of the ISO images will be exported.

For example:

mkdir /wide_open/export/s390_rhel4_u2

Each ISO image must be mounted and the contents of the RedHat/ directory copied to a mount point which is to be exported via NFS, FTP, or HTTP.

The following is an example using the 31-bit ISO images.

cd /wide_open/rhel-iso/iso-images/rhel4/s390/u2mount -o loop RHEL4-U1-s390-AS-disc1.iso /s390/cd1cp -var /s390/cd1/RedHat /wide_open/export/s390_rhel4_u2umount /s390/cd1mount -o loop RHEL4-U1-s390-AS-disc2.iso /s390/cd2 cp -var /s390/cd2/RedHat /wide_open/export/s390_rhel4_u2umount /s390/cd2mount -o loop RHEL4-U1-s390-AS-disc3.iso /s390/cd3cp -var /s390/cd3/RedHat /wide_open/export/s390_rhel4_u2umount /s390/cd3mount -o loop RHEL4-U1-s390-AS-disc4.iso /s390/cd4cp -var /s390/cd4/RedHat /wide_open/export/s390_rhel4_u2umount /s390/cd4

The host to be used for the network installation should now have the necessary files copied for the installation.



3. Add the subnet information for the Linux instance to the /etc/exports file and ensure that the NFS service is running.

For example:

[root@l82bi135 /]# cat /etc/exports/wide_open 172.23.189.0/255.255.255.0(ro) 172.23.188.0/255.255.255.0(ro) 172.23.192.188/255.255.255.0 (ro)/wide_open 172.23.178.0/255.255.255.0 *(ro,no_root_squash)

[root@l82bi135 /]# /etc/init.d/nfs statusrpc.mountd (pid 10650) is running...nfsd (pid 10644 10643 10642 10641 10640 10639 10638 10637) is running...rpc.rquotad (pid 10633) is running...

[root@l82bi135 /]# /etc/init.d/nfs restartShutting down NFS mountd: [ OK ]Shutting down NFS daemon: [ OK ]Shutting down NFS quotas: [ OK ]Shutting down NFS services: [ OK ]Starting NFS services: [ OK ]Starting NFS quotas: [ OK ]Starting NFS daemon: [ OK ]Starting NFS mountd: [ OK ]

Preparing for a network installation of the RHEL 4.0 87

88


Installing RHEL 4.0 as a guest under z/VM Log on to z/VM as the Linux guest account. You can use x3270 or Integrated 3270 console.

To install the RHEL 4.0 as a guest under z/VM:

1. Obtain the SuSE Linux boot files via ftp.

The following example illustrates the procedure. In the example, the commands you would issue are bolded.



If necessary, add the device containing z/VM's TCP/IP tools to your CMS disk list.

For example:

vmlink tcpmaint 592 592 DMSVML2060I TCPMAINT 592 linked as 0592 file mode Z DMSVML2069E No NAMES file(s) found to search for nickname (592) Ready(00028); T=0.01/0.01 22:56:47

If using any of the qdio/qeth based network connection types (such as OSA express or hipersockets), set the VM guest qioassist parameter off:

set qioassist offReady; T=0.01/0.01 22:58:15

Query the guest for devices:

q disk

LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTALLIN191 191 A R/W 5 3390 4096 1 8-01 892 900LIN192 192 D R/W 50 3390 4096 3 3968-44 5032 9000MNT190 190 S R/O 100 3390 4096 687 14513-81 3487 18000MNT19E 19E Y/S R/O 250 3390 4096 1010 26714-59 18286 45000TCM592 592 Z R/O 67 3390 4096 884 8523-71 3537 12060Ready; T=0.01/0.01 23:00:45



access 192 a DMSACC724I 192 replaces A (191) DMSACP726I 192 D released Ready; T=0.01/0.01 23:01:23

ftp 172.23.189.135 VM TCP/IP FTP Level 520 Connecting to 172.23.189.135, port 21 220 (vsFTPd 1.2.1) USER (identify yourself to the host):

root >>>USER root 331 Please specify the password.

Password: xxxxxxx >>>PASS ******** 230 Login successful. Command:

bin >>>TYPE i 200 Type set to I.

locsite fix 80 Command:

cd <the NFS install directory/images/>

Command:

get kernel.img (repl >>>PORT 172,23,174,181,4,32 200 PORT command successful. Consider using PASV. >>>RETR kernel.img 150 Opening BINARY mode data connection for kernel.img (3178752 bytes). 226 File send OK. 3178800 bytes transferred in 0.454 seconds. Transfer rate 7001.76 Kbytes/sec.

Command:

get initrd.img (repl >>>PORT 172,23,174,181,4,33 200 PORT command successful. Consider using PASV. >>>RETR initrd.img 150 Opening BINARY mode data connection for initrd.img (5906555 bytes). 226 File send OK. 5906560 bytes transferred in 0.852 seconds. Transfer rate 6932.58 Kbytes/sec.

Installing RHEL 4.0 as a guest under z/VM 89

90


Command:

ascii >>>TYPE a 200 Switching to ASCII mode. Command:

get redhat.parm (repl >>>PORT 172,23,174,181,4,34 200 PORT command successful. Consider using PASV. >>>RETR redhat.parm 150 Opening BINARY mode data connection for redhat.parm (80 bytes). 226 File send OK. 82 bytes transferred in 0.006 seconds. Transfer rate 13.67 Kbytes/sec.

Command:

quit >>>QUIT 221 Goodbye. Ready; T=0.08/0.17 00:43:36

Example:

redhat.parmroot=/dev/ram0 ro ip=off ramdisk_size=40000CMSDASD=191 CMSCONFFILE=redhat.conf

2. Punch the Linux boot files to the virtual machine reader.

The following example illustrates the procedure. This example shows commands used to punch Linux boot files to the virtual machine reader.

For example:

cl rdr Ready; T=0.01/0.01 00:44:38

purge rdr all 0000003 FILES PURGED Ready; T=0.01/0.01 00:45:08

spool punch * rdr Ready; T=0.01/0.01 00:46:04

punch kernel img a (noh RDR FILE 0015 SENT FROM LX52CR02 PUN WAS 0015 RECS 040K CPY 001 A NOHOLD NOKEEPReady; T=0.02/0.18 00:46:23



punch redhat parm a (noh RDR FILE 0016 SENT FROM LX52CR02 PUN WAS 0016 RECS 0001 CPY 001 A NOHOLD NOKEEPReady; T=0.01/0.01 00:46:40

punch initrd img a (noh RDR FILE 0017 SENT FROM LX52CR02 PUN WAS 0017 RECS 074K CPY 001 A NOHOLD NOKEEPReady; T=0.05/0.34 00:46:56

ch rdr all keep nohold 0000003 FILES CHANGED Ready; T=0.01/0.01 00:47:10 Ipl 00c . .

For instructions to successfully complete the installation of the operating system go to Step 13 on page 99 through Step 21 on page 102.

For example:

Which kind of network device do you intend to use (e.g. ctc, iucv, qeth, lcs). Enter 'qeth' for OSA-Express Fast Ethernet, Gigabit Ethernet (including 1000Base-T), High Speed Token Ring, and ATM (running Ethernet LAN emulation) features in QDIO mode. Enter 'lcs' for OSA 2 Ethernet/Token Ring, OSA-Express Fast Ethernet in

non-QDIO mode, OSA-Express High Speed Token Ring in non-QDIO and Gigabit Ethernet in non-QDIO mode.

# qeth

Installing RHEL 4.0 as a guest under z/VM 91

92


Installing RHEL 4.0 on an LPARThis section provides the steps required to install RHEL 4.0 on an LPAR. Specifically, it explains the steps taken at the HMC (Hardware Management Console) prior to the installation and then explains the installation steps. For further information refer to the chapter "Booting from HMC CD-ROM or FTP server" in the Linux for IBM e-server zSeries and S/390: Distributions Manual.

An LPAR should have already been created and resources allocated to it prior to the Red Hat Linux installation.

At least one FCP channel must be allocated to the target LPAR configuration for FCP device connectivity. The FICON channels in FCP mode provide full fabric support so that the IBM zSeries and S/390 systems have access to standard FCP and SCSI devices. Refer to the IBM zSeries documentation for further information.

Once the LPAR and its resources have been generated in a configuration, the target LPAR must be configured for the installation.

To configure the LPAR for the RHEL 4.0 installation:

1. Log on to the HMC (Hardware Management Console).

2. Select Groups from the Views menu on the left-hand side of the window. The Recovery menu displays on the right-hand side of the window.



3. Double-click on the Defined CPCs icon in the Groups Work Area. The Defined CPCs Work Area displays.

4. Highlight the target CPC in the Defined CPCs Work Area and double-click the Single Object Operation icon from the CPC Recovery menu.

Installing RHEL 4.0 on an LPAR 93

94


5. Once selected, the Single Object Operation window provides a list of object names from which to choose. Select the proper Object Name assigned to the LPAR targeted for the Linux installation and click Yes.



6. The Groups Work Area window displays. Double-click on the Images icon. The Images Work Area window shows all of the LPARs defined for this CPC.


96


7. Click on the LPAR targeted for the Linux installation. To initiate the installation process, double-click the Load from CD-ROM or Server icon from the CPC Recovery menu.

8. Confirmation is requested to continue with the load from the CD-ROM. Click OK if the correct target LPAR object name is displayed in the window.



9. Following this confirmation, the user is prompted to select the installation source. Select the source of the software, Hardware Management Console CD-ROM, and click OK to proceed.

10. When prompted to select the software to load, select suse.ins Linux for S/390 Installation/Rescue System (Default).

11. Click OK to continue.


98


By selecting the suse.ins software, the necessary installation code is retrieved from the source CD-ROM. A Reset Clear is automatically performed on the target LPAR and then the installation load for the LPAR begins.



12. Double-click on the Operation System Messages icon. The installation begins and prompts the user to select the necessary ethernet module depending upon the hardware in the system.

13. When prompted, select the type of networking device that is allocated to the target LPAR.

For example:

Which kind of network do you intend to use (e.g. ctc, iucv, qeth, lcs)Enter 'qeth' for OSA-Express Fast Ethernet, Gigabit (including 1000Base-T), High Speed Token Ring and ATM (running Ethernet LAN emulation features) in QDIO mode.

Enter 'lcs' for OSA 2 Ethernet/Token Ring, OSA-Express Fast Ethernet in non-QDIO mode, OSA-Express High Speed Token Ring in non-QDIO mode, and Gigabit Ethernet in non-QDIO mode.

# qeth14. Enter the device addresses and portname for the ethernet

module.


100


15. In the example under Step 13 on page 99, the OSA Gigabit Ethernet device is allocated to the target LPAR. Therefore, the qeth network module is used.

16. Enter the appropriate information for the target LPAR for your environment when prompted.

For example:

Enter the bus IS and the device number of your CCW deviceCTC/ESCON and LCS need 2 subchannels (e.g. "0.0.0600,0.0.0601" will configure the CTC or ESCON interface with the subchannels 0600 and 0601.)QETH needs 3 subchannels, e.g. 0.0.0300,0.0.0301,0.0.0302

# 0.0.0200,0.0.0201,0.0.0202

17. Enter the portname for the network board.

For example:

Portname of the OSA-Express feature in QDIO mode and z/VM Guest LAN.This parameter is optional with z/VM 4.4.0 or z/VM 4.3.0 with APARS VM63380 and PQ-73878.Press enter if you don’t want to enter a portname:

# osa0200

18. Depending upon the information provided by the network administrator, enter the necessary networking information for the Linux LPAR when prompted.

For example:

Enter the FQDN of you new Linux guest (e.g. s390.redhat.com):# rhel4s390x.lss.emc.comEnter the IP address of your new Linux guest:# 172.23.174.175Enter the network address of your new Linux guest# 172.23.174.0Enter the netmask of your new Linux guest:# 255.255.255.0Enter the broadcast address of your new Linux guest:# 172.23.174.255Enter your default gateway:# 172.23.174.2

After entering the network information, the networking driver module is loaded by the installation program.



For example, when the qeth module is loaded, the following messages are output to the console:

qeth: Devices 0.0.0200,0.0.0201,0.0.0202 is an OSD Express card (level: 0627) with link type OSD_100 (portname: osa0100)divert: allocating divert_blk for eth0qeth: Hardware IP fragmentation not supported on eth0

VLAN enabledMulticast enabledIPV6 enabledBroadcast enabledUsing software checksumming on eth0

19. If applicable, enter the DNS server information when prompted:

For example:

Enter your DNS server(s), separated by colons:# 168.159.48.49:168.159.48.48

Enter the DNS search domain(s), separated by colons:# lss.emc.com:isus.emc.com:emc.com

Based on the information entered during the installation, the kernel IP routing table displays.

20. When using CKD devices for the installation, enter the DASD device numbers.

For example:

Enter DASD range (e.g. 200-204 or 200,201,202,203)Press <Enter> for autoprobing (not recommended):

# F832,F833

Starting telnetd and sshd to allow log in over the network.Connect now to 172.23.178.217 to start the installation.

sh-3.00#At this point, the telnet and sshd daemons have started.


102


21. Open the Putty tool on the Window or ssh from any UNIX system.

For instructions to complete the operating system installation, proceed to the next section, “Completing the installation of RHEL 4.0.”



Completing the installation of RHEL 4.0The LPAR has been prepared and configured for the installation of RHEL 4.0.

To perform the operating system installation:

1. From another host, telnet or ssh into the LPAR as the root user so the installation continues.

Note: The installation program will not prompt the user for a root password.

2. Select the language when prompted.

3. Select the method to be used for the installation.

Completing the installation of RHEL 4.0 103

104


In this example, NFS is selected.

4. Enter the IP address and network install directory of the NFS server.

5. When prompted, select the mode to be used for the installation, i.e., GUI or text mode.



In this example, the XServer was unable to start so the options provided are text mode and VNC. Start VNC is selected for this installation.

6. As part of the VNC configuration, a password should be allocated to the service. Enter a password when prompted.


106


After a password is entered and confirmed, the VNC service starts on the LPAR. The target LPAR is now accessible via a VNC viewer running on a networked host.



7. If there was a previous installation of Red Hat Enterprise Linux, install or upgrade option is provided. Otherwise, only the installation option is provided.

8. Ordinarily, the operating system searches for devices and defines the devices it finds. In the case of FCP devices, the RHEL 4.0 installation program does not probe for FCP devices. As a result, if there are FCP devices allocated to the target LPAR, they must be added manually to the configuration.

After the installation is complete, additional FCP devices may be added manually to the configuration.


108


Adding FCP devices during installation of RHEL 4.0To add FCP devices to the configuration:

1. Select Add.

The Add FCP device dialog box diplays.



2. The user is prompted to enter the values of the device number (see Step a), the WWPN (see Step b), and the FCP LUN (see Step c). The figure below is an example of a populated Add FCP Device window.

a. The device numbers for the LPAR channel configuration need to be assigned by the mainframe administrator.

For example:

CHIP 50:CHPID FCP Device Numbers50 F060-F07f

b. The WWPN required by the installation program is the WWPN of the storage device port that owns the LUN. In this case, the value would be the WWPN of the Symmetrix FA (Fibre Adapter) that provides access to the LUN.

For example:

Symmetrix FA PortsSymmetrix FA WWPNFA03a0 50:06:04:82:d5:2e:69:02FA14a0 50:06:04:82:d5:2e:69:0d

c. The FCP LUN number is the address of the Symmetrix LUN itself.

Adding FCP devices during installation of RHEL 4.0 109

110


For example:

0x00060000000000000x00061000000000000x0006200000000000, etc.

Note: The hex indicator 0x must precede the Symmetrix WWPN and the FCP LUN.

3. After filling in the information, click OK in the Add FCP device dialog box, then Next.



The figure below is an example showing two added FCP devices.

Adding FCP devices during installation of RHEL 4.0 111

112


Partition DASD devices during the installation of RHEL 4.0At the Disk Partitioning Setup window, the user is prompted to select Automatically partition or Manually partition with Disk Druid.

If the option Automatically partition is selected, then the installer program automatically partitions the devices, establishes mount points, and selects the filesystems to be created.

If the option Manually partition with Disk Druid is selected, then a manual configuration of the boot device is required. To partition the devices as needed, establish the mount points to be created, and select the filesystems to be created, follow these steps:

1. After configuring the partition table and filesystem type, the installation program performs the dasdfmt, fdasd, and mkfs commands on the CKD devices selected for boot. These commands are run by the Disk Druid program.



Once the devices are configured, the installer proceeds. The user must enter the appropriate network configuration information, firewall selection, language, and time zone information.

After submitting the requested information, the Package Installation Defaults window displays.

Partition DASD devices during the installation of RHEL 4.0 113

114


2. The user is prompted to select the default software packages for installation or to customize the software packages installed.

Depending upon the environment, the default software packages may or may not be acceptable. Modify the package list as needed for the target LPAR installation.



After the packages are selected, the installer program proceeds.

Partition DASD devices during the installation of RHEL 4.0 115

116


Once the installation is complete, the following screen displays.

3. Reboot the Linux instance when prompted by the installation program and return to the HMC to perform an IPL (Initial Program Load) on the Linux LPAR.



IPL of the Linux LPAR instance and z/VM final stepOnce the installation has completed, the Linux instance and z/VM guest needs to be rebooted. In order for the instance to boot successfully, the image needs to be loaded. This is performed from the CPC Recovery menu on the HMC. (For Linux LPAR, proceed to Step 1 on page 117.)

1. From the CPC Images Working Area, for z/VM guest log on to integrated 3270 Console and boot (IPL) the virtual system.

2. Issue the following commands:



For example: (f832 is the DASD )

ipl f832 clear..

At this point the z/VM guest completed the installation after the IPL.

Linux LPAR

For Linux LPAR continue with the following steps:

1. Return to the HMC (Hardware Management Console).


118


2. Select Groups from the Views menu on the left-hand side of the window and select the Recovery menu on the right-hand side of the window.

3. The LPAR images display in the Groups Work Area. Double-click Images.



The Images Work Area window displays and shows all of the LPARs defined for this CPC.

4. Highlight the LPAR on which RHEL 4.0 was installed and select the Load option from the CPC Recovery menu.


120


The Load window displays.

5. Fill in the information, including the proper DASD device address for the boot device.

For example:

CPC: PCT3CImage: Linux02Load Type: Normal Store Status:Load address:F832Load parameter:Time-out value: 060

6. Once this information is submitted, the Load Task Confirmation window prompts the user to confirm the settings.

For example:

Load will cause jobs to be cancelled.CPC: PCT3CImage: Linux02Load Type: Normal Store Status:YesLoad address:F832Load parameter:Time-out value:60



Click Yes to continue.

7. Confirm that the information is correct and load the Linux instance on the LPAR.

At this point, the installation and configuration procedures are completed.


122


8. Use Putty tools from windows or Telnet/ssh on Unix system to connect to the NEW LINUX LPAR.



FCP connectivity This section provides FCP connectivity information for the RHEL 4.0 instance attached to a Symmetrix storage array. The FCP device numbers must have been defined in the IOCDS and assigned to the FCP channels. Those channels should have been assigned to the LPAR by the mainframe administrator.

The WWPNs of the CHPIDs and of the Symmetrix FA ports and the FCP device numbers are required for the creation of the /etc/zfcp.conf file and represent the FCP mappings for the Linux guest.

Composition of the /etc/zfcp.conf file

The /etc/zfcp.conf file is composed of five elements. The format of the /etc/zfcp.conf file using those elements is as follows:

FCP Device # Target # Target WWPN LUN # SAN LUN #0.0.f060 0x01 0x50060482d52e6902 0x00 0x0060000000000000

Based on the above format, the following is a representation of an /etc/zfcp.conf file:

0.0.f060 0x01 0x50060482d52e6902 0x00 0x00600000000000000.0.f060 0x01 0x50060482d52e690d 0x00 0x00600000000000000.0.f061 0x01 0x50060482d52e6902 0x00 0x00610000000000000.0.f061 0x01 0x50060482d52e690d 0x00 0x0061000000000000

Note: Each individual LUN assigned to the Linux instance requires a mapping entry in /etc/zfcp.conf.

Table 1 on page 124 describes the five elements.

FCP connectivity 123

124


System configuration for FCP attachNote that any FCP devices added to the system at the time of installation is listed in this file. When additional devices are added after the installation, then the mapping information needs to be added manually to the /etc/zfcp.conf file.

1. When additional devices are allocated to the Linux instance, the /etc/zfcp.conf file needs to be updated to reflect the changes.

Table 1 /etc/zfcp.conf file elements

Element Description

FCP device number As displayed in the example, the FCP devices follow the format of 0.0.xxx where xxx is the device number. In this example, the device number assigned is a000 so the FCP device number must be listed as 0.0.f060. Depending upon the IOCDS configuration and the amount of the device numbers assigned, a single FCP device number may be used for all FCP connections, or multiple FCP device numbers assigned to the FCP channel may be used.

Target number The Target Number is assigned by the Linux administrator and will be used by Linux.The target addresses must begin with 1 and should increment by 1. The target address of 0 is used to address the FCP adapter and may not be used for any other purpose.Target addresses may be reused with different device numbers.

Target WWPN The Target WWPN is the World Wide Port Number of the SAN node. This number is not assigned by the administrator. The Target WWPN number must be in hexadecimal format and must be 16 hexadecimal digits. The Target WWPN should be the same as the WWPN seen by the FC switch..

LUN number The LUN number is assigned by the Linux administrator and is used by Linux. Normally, the LUN numbers will begin with zero and increment by one for each additional LUN.

SAN Node LUN number The SAN Node LUN number is the storage array’s assigned LUN number. This number is not assigned by the administrator. The SAN LUN number must be in hexadecimal format and must be 16 hexadecimal digits. The Symmetrix SAN LUN numbers are listed in the first 4 digits and are followed by twelve zeros.



The following is an example of a /etc/zfcp.conf file where only one device and two targets WWPN with are being used.

[root@rhel4s390x etc]# cat zfcp.conf0.0.f060 0x01 0x50060482d52e6902 0x00 0x00600000000000000.0.f060 0x01 0x50060482d52e690d 0x00 0x00600000000000000.0.f061 0x01 0x50060482d52e6902 0x00 0x00610000000000000.0.f061 0x01 0x50060482d52e690d 0x00 0x00610000000000000.0.f062 0x01 0x50060482d52e6902 0x00 0x00620000000000000.0.f062 0x01 0x50060482d52e690d 0x00 0x0062000000000000

2. The SCSI modules must be loaded in order for the zfcp driver to function. The drivers need to be loaded in the following order, if not yet loaded:

modprobe scsi_modmodprobe sd_modmodprobe sgmodprobe zfcp

3. If FCP devices were added during the OS installation, the alias scsi_hostadapter zfcp line was appended to the /etc/modprobe.conf file.

If FCP devices were added after the installation, the /etc/modprobe.conf file needs to be modified manually.

The zfcp driver must be listed in the /etc/modprobe.conf file so it is included in the ramdisk and loaded at boot time.

For example:

[root@rhel4s390 /]# cat /etc/modprobe.confalias eth0 qethoptions dasd_mod dasd=F832,F833alias scsi_hostadapter zfcp

4. After changing the /etc/modprobe.conf file, create a new ramdisk so the newly added FCP device mappings are recognized at boot time. Use the mkinitrd command to create a new ramdisk.

For example:

[root@rhel4s390x /]# mkinitrd -v -f --with=scsi_mod --with=zfcp --with=sd_mod initrd-2.6.9-39.EL.img 2.6.9-39.ELCreating initramfsLooking for deps of module scsi_modLooking for deps of module sd_mod scsi_modLooking for deps of module scsi_modLooking for deps of module unknown


126


Looking for deps of module zfcp qdio scsi_transport_fc scsi_modLooking for deps of module qdioLooking for deps of module scsi_transport_fc scsi_modLooking for deps of module scsi_modLooking for deps of module scsi_modLooking for deps of module ide-diskLooking for deps of module dasd_modLooking for deps of module dasd_eckd_mod dasd_modLooking for deps of module dasd_modLooking for deps of module dasd_fba_mod dasd_modLooking for deps of module dasd_modLooking for deps of module ext3 jbdLooking for deps of module jbdLooking for deps of module scsi_modLooking for deps of module zfcp qdio scsi_transport_fc scsi_modLooking for deps of module qdioLooking for deps of module scsi_transport_fc scsi_modLooking for deps of module scsi_modLooking for deps of module scsi_modLooking for deps of module sd_mod scsi_modLooking for deps of module scsi_modUsing modules: ./kernel/drivers/scsi/scsi_mod.ko ./kernel/drivers/scsi/sd_mod.ko ./kernel/drivers/s390/cio/qdio.ko ./kernel/drivers/scsi/scsi_transport_fc.ko ./kernel/drivers/s390/scsi/zfcp.ko ./kernel/drivers/s390/block/dasd_mod.ko ./kernel/drivers/s390/block/dasd_eckd_mod.ko ./kernel/drivers/s390/block/dasd_fba_mod.ko ./kernel/fs/jbd/jbd.ko ./kernel/fs/ext3/ext3.ko/sbin/nash -> /tmp/initrd.iu3556/bin/nash/sbin/insmod.static -> /tmp/initrd.iu3556/bin/insmod/sbin/udev.static -> /tmp/initrd.iu3556/sbin/udev/etc/udev/udev.conf -> /tmp/initrd.iu3556/etc/udev/udev.confcopy from /lib/modules/2.6.9-39.EL/./kernel/drivers/scsi/scsi_mod.ko(elf64-s390) to /tmp/initrd.iu3556/lib/scsi_mod.ko(elf64-s390)copy from /lib/modules/2.6.9-39.EL/./kernel/drivers/scsi/sd_mod.ko(elf64-s390) to /tmp/initrd.iu3556/lib/sd_mod.ko(elf64-s390)copy from /lib/modules/2.6.9-39.EL/./kernel/drivers/s390/cio/qdio.ko(elf64-s390) to /tmp/initrd.iu3556/lib/qdio.ko(elf64-s390)copy from /lib/modules/2.6.9-39.EL/./kernel/drivers/scsi/scsi_transport_fc.ko(elf64-s390) to /tmp/initrd.iu3556/lib/scsi_transport_fc.ko(elf64-s390)copy from /lib/modules/2.6.9-39.EL/./kernel/drivers/s390/scsi/zfcp.ko(elf64-s390) to /tmp/initrd.iu3556/lib/zfcp.ko(elf64-s390)copy from /lib/modules/2.6.9-39.EL/./kernel/drivers/s390/block/dasd_mod.ko(elf64-s390) to /tmp/initrd.iu3556/lib/dasd_mod.ko(elf64-s390)copy from /lib/modules/2.6.9-39.EL/./kernel/drivers/s390/block/dasd_eckd_mod.ko(elf64-s390) to /tmp/initrd.iu3556/lib/dasd_eckd_mod.ko(elf64-s390)copy from /lib/modules/2.6.9-39.EL/./kernel/drivers/s390/block/dasd_fba_mod.ko(elf64-s390) to /tmp/initrd.iu3556/lib/dasd_fba_mod.ko(elf64-s390)



copy from /lib/modules/2.6.9-39.EL/./kernel/fs/jbd/jbd.ko(elf64-s390) to /tmp/initrd.iu3556/lib/jbd.ko(elf64-s390)copy from /lib/modules/2.6.9-39.EL/./kernel/fs/ext3/ext3.ko(elf64-s390) to /tmp/initrd.iu3556/lib/ext3.ko(elf64-s390)Loading module scsi_modLoading module sd_modLoading module qdioLoading module scsi_transport_fcLoading module zfcpLoading module dasd_mod with options dasd=f832-f833Loading module dasd_eckd_modLoading module dasd_fba_modLoading module jbdLoading module ext3

[root@rhel4s390x /]# zipl -VUsing config file '/etc/zipl.conf'Target device information Device..........................: 5e:00 Partition.......................: 5e:01 Device name.....................: dasda DASD device number..............: f832 Type............................: disk partition Disk layout.....................: ECKD/compatible disk layout Geometry - heads................: 15 Geometry - sectors..............: 12 Geometry - cylinders............: 10017 Geometry - start................: 24 File system block size..........: 4096 Physical block size.............: 4096 Device size in physical blocks..: 51204Building bootmap '/boot//bootmap'Building menu 'rh-automatic-menu'Adding #1: IPL section 'linux' (default) kernel image......: /boot/vmlinuz-2.6.9-39.EL at 0x10000 kernel parmline...: 'root=LABEL=/' at 0x1000 initial ramdisk...: /boot/initrd-2.6.9-39.EL.img at 0x800000Preparing boot device: dasda (f832).Preparing boot menu Interactive prompt......: enabled Menu timeout............: 15 seconds Default configuration...: 'linux'Syncing disks...Done.

5. Reboot the RHEL 4.0 instance.


128


Add FCP devices using the command lineFCP devices may be added to the Linux instance after the RHEL 4.0 installation is complete. This may be accomplished at the command line using information from sysfs.

1. Verify that the channel is online.

cat /sys/bus/ccw/drivers/zfcp/<dev_no>/online

If the value returned is 0, then the channel is offline. It can be put online by echoing the sysfs. The command to be used is as follows:

echo 1 > /sys/bus/ccw/drivers/zfcp/<dev_no>/online

For example:

echo 1 > /sys/bus/ccw/drivers/zfcp/0.0.f063/online

After verifying that the channel is online, additional Symmetrix FA ports and LUNs can be added to the system.

2. To add more LUNs to a previously existing Symmetrix FA WWPN, issue the unit_add option.

echo 0x<LUN_no> > /sys/bus/ccw/drivers/zfcp/<dev_no>/0x<Symm_WWPN>/unit_add

where:

For example:

echo 0x0064000000000000 > /sys/bus/ccw/drivers/zfcp/0.0.f064/0x50060482d52e6902/unit_add

Note: This command is issued on one line. However, due to the formatting, the command wraps around to the second line.

LUN_no is the new LUN that is being added to the configuration.

dev_no is the channel device number.

Symm_WWPN is a previously existing Symmetrix FA port’s WWPN.



3. To add a new Symmetrix FA WWPN to the configuration, issue the port_add option.

echo 0x<Symm_WWPN> > /sys/bus/ccw/drivers/zfcp/<dev_no>/port_add

where:

For example:

echo 0x50060482d52e6902 > /sys/bus/ccw/drivers/zfcp/0.0.f064/port_add

4. To add LUNs to the new Symmetrix FA port, issue the unit_add option. As demonstrated above, use the following command:

echo 0x<LUN_no> > /sys/bus/ccw/drivers/zfcp/<dev_no>/0x<Symm_WWPN>/unit_add

where:

For example:

echo 0x0064000000000000 > /sys/bus/ccw/drivers/zfcp/0.0.f064/0x50060482d52e6902/unit_add

5. Assuming the device additions are permanent, the new information needs to be added to the /etc/zfcp.conf file. When changes are made to the /etc/zfcp.conf file, create a new ramdisk and run the zipl command prior to rebooting.

a. Use the mkinitrd command to include the newly added FCP device mappings in the ramdisk.

For example:

mkinitrd -v -f --with=scsi_mod --with=zfcp --with=sd_mod initrd-2.6.9-22.0.2.EL.img 2.6.9-22.0.2.EL



LUN_no is the new LUN that is being added to the configuration.




130


b. Run the zipl command to update the boot loader.

For example:

zipl -V

c. Reboot the host.



RHEL 4.0 DM-MPIO installation and configurationWhen using DASD devices via ESCON or FICON attach, multipathing is available via the zSeries microcode. The multipathing is transparent to the operating system and is handled solely by the zSeries I/O subsystem. Multipathing for FCP devices is not native to the zSeries subsystem and is handled by the Linux v2.6.x kernel multipathing solution.

DM-MPIO is the native multipathing functionality that is included in the Linux v2.6.x kernel. DM-MPIO requires the device-mapper, udev, hotplug, and device-mapper-multipath packages.

The device-mapper-multipath package provides the tools to manage multipath devices using device-mapper. Since the package is not automatically selected by the RHEL 4.0 U2 installer, it needs to be selected manually.

Follow the instruction listed in the Native Multipath Failover Based on DM-MPIO for v2.6.x Linux Kernel and EMC Storage Arrays, Red Hat Enterprise Linux 4 - U3, SuSE Linux Enterprise Server 9 - SP3, Configuration Guide, available at http://Powerlink.EMC.com.

RHEL 4.0 DM-MPIO installation and configuration 131

http://Powerlink.EMC.com

132



linux on ibm system z: rhel 4.0 and sles 9 installation ... · emc corporation corporate...

Documents