IBM®
Skip to main content
    Country/region [select]      Terms of use
 
 
    
     Home      Products      Services & solutions      Support & downloads      My account     
 
developerworks > My developerWorks >  Dashboard > Linux for Power Architecture > ... > Red Hat > Network Installation of RHEL
developerWorks
Log In   View a printable version of the current page.
Overview Connect Spaces Forums Wikis
Network Installation of RHEL
Added by pjuerss, last edited by pjuerss on May 15, 2006  (view change)
Labels: 
(None)

Network Installation of Red Hat Enterprise Linux

The network installation of a system or logical partition (LPAR) has advantages over the traditional way using CDs. Especially when you are facing an installation of more than one system, the CD installation can become a nightmare - unless you are planning to improve your quality as DJ.
The other main advantage is that you can provide a configuration file which automates the tasks for a installation which finally means that it becomes very easy and fast to setup a system or LPAR.

Starting the installation

It is assumed that you have setup an installation server as descripted in the section Network Installation in this Wiki.
Hint: Copy the netboot.img to the /tftpboot directory of your installation server. You can find the netboot.img on CD1 of Red Hat Enterprise Linux in the directory images/pseries.

Now start your system and press either 1 to enter the SMS menu or 8 to go to the OpenFirmware prompt, as soon as you can see the following picture and the word Keyboard will be displayed.

IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM

          1 = SMS Menu                          5 = Default Boot List
          8 = Open Firmware Prompt              6 = Stored Boot List


     Memory      Keyboard     Network     SCSI     Speaker 

Example - Startup screen

Comment: Please note that to be able to pass arguments to the installer you must use the OpenFirmware prompt!

The following example shows the way to boot a system or LPAR using the OpenFirmware.

After you've pressed 8 you will enter the OpenFirmware or OK prompt.
First you must find out, which device you want to boot of, using the ls command.

0 > ls
000000c85838: /ibm,serial
000000c86588: /chosen
... (skipped output)
000000d1a5d8: /vdevice
000000d1d040:   /vty@30000000
000000d1df18:   /v-scsi@30000002
000000d27628:     /disk
000000d28900:     /tape
000000d2a068:   /l-lan@30000004
000000d31950:   /IBM,sp@4000
000000d32908:   /rtc@4001
000000d33210:   /nvram@4002
 ok
0 >

Example - Output of the ls command

In our example we are looking for the available network devices because we want to perform a network installation. We will find them under /vdevice named as l-lan@... - in our example /vdevice/l-lan@30000004.

Now the first thing to do is to define an alias otherwise you alway must use the fully qualified OF name of the device. In this example we will create an alias called net using the OF name /vdevice/l-lan@30000004.

0 > devalias net /vdevice/l-lan@30000004

Booting the system is straightforward and you can pass parameters to the kernel.

0 > boot net linux rescue askmethod

Example - Booting a rescue system

To use a Kickstart file you will use the following line.

0 > boot net ks=nfs:9.154.2.86:/export/autoinstall/ks.cfg ksdevice=eth0

Example - Using a Kickstart file

Kickstart file - SW RAID

Below you will find a Kickstart file which includes the setup for SW RAID. Please change as appropriate to suit your environment. By the way...the root pw is abc123

#Kickstart file including SW RAID setup
#System  language
lang en_US
#Language modules to install
langsupport en_US
#System keyboard
keyboard de
#System mouse
mouse
#Sytem timezone
timezone Europe/Berlin
#Root password
rootpw --iscrypted $1$pbiqiFtD$mHTsIuKqtAUT70CPpkdIp/
#Reboot after installation
reboot
#Use text mode install
text
#Install OS instead of upgrade
install
#Use NFS installation Media
nfs --server=9.154.2.86  --dir=/export/rhel4
#System bootloader configuration
bootloader --location=mbr
#Clear the Master Boot Record
zerombr yes
#Partition clearing information
clearpart --all --initlabel
#Disk partitioning information
part None --fstype "PPC PReP Boot" --size 8 --asprimary --ondisk sda
part None --fstype "vfat" --size 8 --asprimary --ondisk sdb
part raid.01 --size 100 --asprimary --ondisk sda
part raid.02 --size 100 --asprimary --ondisk sdb
part raid.03 --size 1 --grow --asprimary --ondisk sda
part raid.04 --size 1 --grow --asprimary --ondisk sdb
#RAID Setup
raid /boot --level=1 --device=md0 --fstype ext3 raid.01 raid.02
raid pv.3 --level=1 --device=md1 --fstype "physical volume (LVM)" raid.03 raid.04
#Logical Volume information
volgroup systemvg --pesize=4096 pv.3
logvol / --fstype ext3 --size=2048 --name=rootlv --vgname=systemvg
logvol /usr --fstype ext3 --size=3072 --name=usrlv --vgname=systemvg
logvol /opt --fstype ext3 --size=2048 --name=optlv --vgname=systemvg
logvol /var --fstype ext3 --size=2048 --name=varlv --vgname=systemvg
logvol /home --fstype ext3 --size=512 --name=homelv --vgname=systemvg
logvol /tmp --fstype ext3 --size=1024 --name=tmplv --vgname=systemvg
logvol swap --fstype swap --size=1024 --name=swap --vgname=systemvg
#Network information
network --bootproto=static --ip=9.154.2.114 --netmask=255.255.255.0 --gateway=9.154.2.1 --nameserver=9.64.163.21 --device=eth0
#System authorization infomation
auth  --useshadow  --enablemd5
#Firewall configuration
firewall --disabled
#Package install information
%packages --resolvedeps
@ base-x
@ gnome-desktop
@ editors
@ development-tools
@ compat-arch-development
@ legacy-software-development
@ admin-tools
@ system-tools
@ printing
@ compat-arch-support

Example - Kickstart file with SW RAID setup

Finally, don't forget to copy the boot partition /dev/sda1 to /dev/sdb1 and make sdb bootable.


 
    About IBM Privacy Contact