Novell LINUX ENTERPRISE 10 SP1 - LINUX AUDIT, Specification

Page 1: ...SUSE Linux Enterprise Server www novell com 10 SP1 March 15 2007 Architecture Specific Information ...

Page 2: ...es 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 For Novell trademarks see the Novell Trademark and Service Mark list http www novell com company legal trademarks tmlist html Linux is a registered trademark of Linus Torvald...

Page 3: ...e 11 2 2 Installation Types 15 2 3 Preparing the IPL of the SUSE Linux Enterprise Server Installation System 16 2 4 IPLing the SUSE Linux Enterprise Server Installation System 19 2 5 Network Configuration 23 2 6 Connecting to the SUSE Linux Enterprise Server Installation System 26 A Appendix 29 A 1 Network Connection Types 29 A 2 The parmfile Automating the System Configuration 32 A 3 Using the vt...

Page 4: ......

Page 5: ... basic preparations need to be per formed on the LPAR and z VM side It guides you to the point where YaST the SUSE Linux Enterprise Server installation and configuration tool takes over Additionally the appendix contains a chapter featuring an overview of possible network connection types The second chapter in the appendix focuses on automated system configuration using the parmfile TIP Further In...

Page 6: ...tions are used in this manual etc passwd filenames and directory names placeholder replace placeholder with the actual value PATH the environment variable PATH ls help commands options and parameters user users or groups Alt Alt F1 a key to press or a key combination keys are shown in uppercase as on a keyboard File File Save As menu items buttons This paragraph is only relevant for the specified ...

Page 7: ...Series 990 Technical Introduction SG24 6863 IBM eServer zSeries 900 Technical Guide SG24 5975 Technical Introduction IBM eServer zSeries 800 SG24 6515 Linux on zSeries Fibre Channel Protocol Implementation Guide SG24 6344 4 2 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 a...

Page 8: ...9 Technical Introduction SG26 6669 There also is a Redbook for Linux application development on http www redbooks ibm com Linux on IBM eServer zSeries and S 390 Application Development SG24 6807 4 4 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 Dep...

Page 9: ...eloperworks linux linux390 index html 5 Acknowledgments The history of Linux is a success story about countless developers all around the world contributing to what originally started as a one man show by Linus Torvalds Thanks to all of them for their tremendous efforts Especially we would like to thank all the people involved in the Linux for IBM System z project at IBM and SUSE Thanks to the inf...

Page 10: ......

Page 11: ... z supported by SUSE Linux Enterprise Server Next the level of the MicroCode MCL used in your IBM System z system which is very important for the installation is covered Additional software to install and use for installation is mentioned at the end of this section 1 1 1 Hardware SUSE Linux Enterprise Server has run successfully on the following platforms IBM eServer zSeries 800 z800 2066 IBM eSer...

Page 12: ...rary disk space in memory RAM disk during the package transfers Disk Space Requirements 1 6 GB disk space is required for the installation of SUSE Linux Enterprise Server Network Connection A network connection is needed to communicate with your SUSE Linux Enterprise Server system This can be one or more of the following connections or network cards OSA 2 Token Ring and Ethernet only available on ...

Page 13: ... requirements listed at the Web site also apply for this release of SUSE Linux Enterprise Server except where stated differently in this manual It is recommended always to use the highest service level available For installation under VM you need at least z VM 4 2 with service level 0103 To use HiperSockets under VM on z900 2064 you need MicroCode EC E26949 level 013 or higher For an IPL from SCSI...

Page 14: ...ode levels 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 To connect to the SUSE Linux Enterprise Server installation system one of the following methods is required SSH wit...

Page 15: ...es X Server can be obtained at http www microimages com mix TIP Additional Information Consult the README located in the highest directory of CD 1 of your SUSE Linux Enterprise Server before installing SUSE Linux Enterprise Server on IBM System z This file completes the documentation presented in this book 1 2 Installation Types This section gives an overview of the different types of installation...

Page 16: ...d or remove hardware to and from Linux guests Creating additional SUSE Linux Enter prise Server guests is simple and you are able to run hundreds of Linux instances simul taneously 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 f...

Page 17: ...m the Support Element s SE CD ROM device It also allows you to IPL via FTP from a server holding the SUSE Linux Enterprise Server for IBM System z files Find this button near the LOAD button if you have upgraded to the latest MCL see Chapter 1 General Information and Requirements page 1 Figure 1 1 HMC CPC Group Work Area This function can be performed from the HMC Do this by accessing the Defined ...

Page 18: ...s some necessary information about the IOCDS and how to cus tomize some settings for sharing network cards or DASDs among several LPARs In the IOCDS the chpid and types of the devices connected to the IBM System z are defined The resources can be dedicated or shared among LPARs WARNING Sharing Devices DASD Do not share DASD writable among LPARs because this might result in data loss Consider the d...

Page 19: ...e one connection fails Network cards like OSA Express can be used in two different modes These modes are known as QDIO and non QDIO mode Define these modes in the IOCDS by using the TYPE statement QDIO mode is much faster than non QDIO mode but uses three device addresses instead of two in non QDIO Consider the limited number of device addresses when planning the setup of your IBM System z Linux e...

Page 20: ......

Page 21: ...erver IBM System z installation data accessible for installation Depending on your computer and system environment choose between NFS or FTP installation If you are running Microsoft Windows workstations in your environment you can also use the Windows network including the SMB protocol to install SUSE Linux Enterprise Server on your IBM System z system TIP IPL from CD ROM When planning to IPL fro...

Page 22: ... CD ROM you need access to an FCP adapter connected to a CD ROM drive You need values like the WWPN and LUN from the SCSI CD ROM drive IPL from SCSI CD ROM in a LPAR You can use the LOAD procedure by selecting SCSI as Load Type to IPL from SCSI Fill in the WWPN and LUN provided by your SCSI bridge or storage The boot program selector must be 2 Use your FCP adapter as load address and perform an IP...

Page 23: ... The FTP daemon itself does not need to be started by hand It can be started by inetd if an FTP connection is requested To activate the new settings enter rcinetd restart or rcxinetd restart for SUSE Linux 9 0 and later SUSE Linux Enterprise Server on CD CD 1 of the SUSE Linux Enterprise Server for IBM System z contains a bootable Linux image for Intel based workstations Boot from this CD answer t...

Page 24: ...rectory of CD 1 for detailed information 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 The CD ROM drive containing the SUSE Linux Enterprise Server CDs must be in the available NFS path With FTP Refer to the documentation provided with the third party product...

Page 25: ...llation 1 Prepare the devices needed for installation See Section 2 3 1 LPAR Installation page 16 2 IPL the installation system See Section 2 4 1 LPAR Installation page 19 3 Configure the network See Section 2 5 Network Configuration page 23 4 Connect to the SUSE Linux Enterprise Server installation system See Section 2 6 Connecting to the SUSE Linux Enterprise Server Installation System page 26 5...

Page 26: ...va tion profile and IOCDS Consult IBM documentation for more about how to achieve this IOCDS Attaching and Configuring Devices A SUSE Linux Enterprise Server installation needs at least two devices a DASD and a network connection device For an IPL from tape a tape device should also be acces sible Devices are configured and attached to an LPAR in the IOCDS input output configuration data set This ...

Page 27: ...ction 2 4 1 LPAR Installation page 19 2 3 2 z VM Installation Adding a Linux Guest The first step is to attach and format one or multiple DASDs in the system to be used by the Linux guest in z VM Next create a new user in z VM The example shows the directory for a user LINUX1 with the password LINPWD 256 MB of memory extend able up to 512 MB 32 MB of expanded RAM XSTORE some minidisks MDISK two CP...

Page 28: ...ATE 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 Minidisk 150 with 200 cylinders is the Linux swap devi...

Page 29: ...rk 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 In the list of options that appears choose the default selection 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 chann...

Page 30: ...PLable 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 ...

Page 31: ...ntation Log in as the z VM Linux guest to IPL Make the content of the directory boot on CD 1 of the SUSE Linux Enterprise Server for IBM System z available by FTP within your network From this directory get the files vmrdr ikr initrd and parmfile The example shows the steps necessary In this example the required files are accessible from an FTP server at the IP address 192 168 0 3 and the login is...

Page 32: ...6 70 Kbytes sec Command get media cdrom boot initrd sles10 initrd 200 PORT Command successful 150 Opening BINARY mode data connection for initrd 12194534 bytes 226 Transfer complete 12194534 bytes transferred in 15 919 seconds Transfer rate 766 70 Kbytes sec Command asc 200 Type set to A Command get media cdrom boot parmfile sles10 parm 150 Opening BINARY mode data connection for parmfile 38 bytes...

Page 33: ... installation proceed with Section 2 5 1 z VM Installation page 24 IPL from ESCON or FICON Attached tape If you cannot IPL from a z VM reader create a channel attached tape from which to IPL the SUSE Linux Enterprise Server installation image For instructions refer to Section IPL from ESCON or FICON Attached Tape page 19 To continue the installation proceed with Section 2 5 1 z VM Installation pag...

Page 34: ...ame for OSA ethernet cards Next decide whether to use DHCP autoconfiguration for setting up the network interface parameters Because DHCP only works on a few devices and requires special hardware configuration settings you probably want to say NO here When you do so you are prompted for the networking parameters of your installation network device The IP address of the system to install The corres...

Page 35: ... Using SW checksumming on eth0 qeth Outbound TSO not supported on eth0 Next enter your IP address netmask and default gateway To install over token ring iucv or ctc enter additional information like the the peer address for a point to point adapter or the port name Finally the IP address of the DNS server and the MTU size are requested The MTU size should always match the one used by the network t...

Page 36: ...er IP address and the directory in which the data is located Finally linuxrc wants to know what type of display you want to use to control the in stallation procedure Possible choices are X11 X Window System VNC Virtual Network Computing protocol and SSH text mode or X11 installation via Secure Shell 2 6 1 Initiating the Installation for VNC 1 After the installation option VNC has been chosen the ...

Page 37: ...sm is disabled on current SUSE Linux Enterprise Server versions Installation with SSH or VNC is preferred 1 Make sure that the X server allows the client the system that is installed to connect Set the variable DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN yes in the file etc sysconfig displaymanager Then restart the X server and allow client binding to the server using xhost client IP address 2 When ...

Page 38: ...in with your password Then enter yast2 to start YaST Proceed with the detailed description of the installation procedure that can be found in Chapter 3 Installation with YaST Installation and Administration 28 Architecture Specific Information ...

Page 39: ... WARNING CTC ESCON and IUCV Interfaces No Longer Supported CTC ESCON and IUCV interfaces are no longer officially supported For com patibility reasons they are still usable but with the next release of SUSE Linux Enterprise Server the support of these interfaces will be dropped completely A 1 1 Ethernet and Token Ring with the lcs Module Select 1 from the list of network devices for an OSA network...

Page 40: ... 1 Ethernet 2 Token Ring 1 When prompted enter the network device read channel number such as 0 0 fc20 the write channel number like 0 0 fc21 and the relative port number on this device Example A 2 Network Device Driver Parameters Device address for read channel 0 0 fc20 Device address for write channel 0 0 fc21 Enter the relative port number 2 Next choose manual configuration then enter the IP ad...

Page 41: ...server press ESC 192 168 0 20 192 168 0 2 A 1 2 Gigabit Ethernet with the qeth Module Select 1 from the list of network devices for OSA network adapters then 1 for the QDIO interface then 1 for ethernet When prompted enter the network device s read write and data channel numbers for example 0 0 0808 0 0 0809 and 0 0 080a and the port name if applicable Choose whether to enable OSI Layer 2 support ...

Page 42: ...not use a name server press ESC 192 168 0 20 192 168 0 2 A 2 The parmfile Automating the System Configuration The installation process can be partly automated by specifying the crucial parameters in the parmfile The parmfile contains all the data required for network setup and DASD configuration In addition to that it can be used to set up the connection method to the SUSE Linux Enterprise Server ...

Page 43: ...Set this parameter to 0 if all values should be accepted and no questions asked Setting AutoYaST implies setting Manual to 0 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 This creates a ready to use profile as root autoinst xml that can be used to create clones of this particular installation To cr...

Page 44: ... 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 lcs qdio OsaMedium eth tr For osa network devices specify the host interface qdio or lcs and the phys ical medium eth for ethernet or tr for token ring ...

Page 45: ...y mode with OS 390 and z OS 2 Network device type osa with interface lcs ReadChannel 0 0 0124 Portname 1 ReadChannel stands for the channel number used in this setup A second port number can be derived from this by adding one to ReadChannel Portnumber is used to specify the relative port Interface iucv IUCVPeer PARTNER Enter the name of the peer machine Network device type osa with interface qdio ...

Page 46: ...allation Source and YaST Interface Install nfs server directory CD1 Specify the location of the installation source to use Possible protocols are nfs smb Samba CIFS ftp and http If an ftp or smb URL is given specify the user and password for FTP installation These parameters are optional and anonymous or guest login is assumed if they are not given Username a user name Password a password In case ...

Page 47: ...ween 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 For SSH specify a password of six to eight characters to use for installation SSHPassword a password A 2 4 Example Parmfiles For an automatic installation with AutoYaST in an LPAR...

Page 48: ...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 CD s390x CD1 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 The vt220 terminal is ...

Page 49: ...sible on this system and you will be shown the following message INIT respawning too fast disabled for 5 minutes To redirect the kernel messages at boot time from the system console to the vt220 ter minal add the following entries to the parameters line in etc zipl conf console ttyS0 console ttyS1 The resulting parameters line would look like the following example parameters root dev dasda2 TERM d...

Page 50: ......