Sles9 sp2 installation
From Linux on Power wiki
liletoelttr
Contents |
Setup of network install server
What components are used for network installation
- First we need a dhcpd or bootp server to answer the boot request. As SLES9 does not include bootpd by default we are going to use dhcpd. Openfirmware will boot the network card and issue a dhcp request. The answer should include the IP address assigned and the name of the boot file.
- Second we need a tftp (Trivial File Transfer Protocol) to provide a boot file to the openfirmware. This is usually located in /tftpboot directory. TFTP uses no authentication at all.
SLES9 includes tftp and atftp packages. We are going to use atftp (Advanced Trivial File Transfer Protocol)
- Third we need an installation source, a directory containing all the files from CDs in the manner SUSE can understand it. Our directory should include the same service pack level like the kernel placed in /tftpboot. This directory can be exported by NFS or HTTP or FTP. After kernel boots on the client the installation procedure will mount the source directory.
Creating network installation source
If you are using SUSE as a network installation server, creating the source is easy, as you can use YAST. Select YAST -> Mixed -> Installation Server and create a NFS installation source. You can use ISO-images instead of CDs, so in most cases it is better to copy the iso images to the server. We will need the 6 base CDs and the 3 service pack 2 CDs. The ISO-Images need to be on the local file system, as loop mounting from NFS is not possible. After selecting all the GA CDs save your configuration. Go to the installation server again and select change-edit-prompt for additional CDs. Supply your SP2 CDs.
op720-2-lpar1:/export/sles9 # ls -al total 0 drwxr-xr-x 6 root root 368 Jul 22 12:02 . drwxr-xr-x 9 root root 400 Jul 22 09:48 .. drwxr-xr-x 7 root root 168 Jul 22 10:08 SUSE-CORE-Version-9 drwxr-xr-x 5 root root 120 Jul 22 12:03 SUSE-SLES-9-Service-Pack-Version-2 drwxr-xr-x 3 root root 72 Jul 22 09:48 SUSE-SLES-Version-9 lrwxrwxrwx 1 root root 28 Jul 22 09:48 boot -> SUSE-SLES-Version-9/CD1/boot lrwxrwxrwx 1 root root 31 Jul 22 09:48 content -> SUSE-SLES-Version-9/CD1/content lrwxrwxrwx 1 root root 35 Jul 22 09:48 control.xml -> SUSE-SLES-Version-9/CD1/control.xml lrwxrwxrwx 1 root root 51 Jul 22 12:02 driverupdate -> SUSE-SLES-9-Service-Pack-Version-2/CD1/driverupdate lrwxrwxrwx 1 root root 44 Jul 22 12:02 linux -> SUSE-SLES-9-Service-Pack-Version-2/CD1/linux lrwxrwxrwx 1 root root 31 Jul 22 09:48 media.1 -> SUSE-SLES-Version-9/CD1/media.1 drwxr-xr-x 2 root root 104 Jul 22 10:09 yast
DHCP Configuration
Install dhcpd and dhcp packages through yast.
For network installation to succeed first thing we need is a DHCP or BOOTP server. After activating the client LPAR and selecting network card as a boot media it will do a bootp request. We are going to use a DHCP server to assign the IP Adress an provide the boot file name, thats why we should make sure that all IP settings in the "Remote IPL" screen are set to 0.0.0.0. This is default, but if you have used this LPAR with a bootp installation server before, you may have server and client ip addresses entered here. Set those to 0.0.0.0 otherwise you will not be able to boot, as DHCP is not going to answer a directed bootp request. Before you install you may use the IPL Settings to set the IP address and ping a server, just for network connectivity test. Remembe to zero all addresses before proceeding to network boot.
Our dhcpd.conf:
option domain-name "www.domain.net";
option domain-name-servers 192.168.1.10;
option routers 192.168.1.254;
option ntp-servers 192.168.1.11;
ddns-update-style none;
ignore unknown-clients;
not authoritative;
log-facility local7;
allow bootp;
allow booting;
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.110 192.168.1.120
}
host lpar1.domain.net {
hardware ethernet 2E:D7:90:00:60:B4;
filename "/tftpboot/install";
# for redhat tftp: filename install;
fixed-address 192.168.1.111;
next-server 192.168.1.1;
}
- After editing /etc/dhcpd.conf file you can check syntax using /etc/init.d/dhcpd check-syntax
- Also create a lease file:
touch /var/lib/dhcp/db/dhcpd.leases;
- And add your active interface to DHCP_INTERFACE in /etc/sysconfig/dhcpd
TFTP Server installation
Install atftp package using yast. Create a /tftpboot directory.
Preparing kernel
Copy the kernel to the /tftpboot.
cp /export/sles9/SUSE-SLES-9-Service-Pack-Version-2/CD1/install /tftpboot/
Create a kernel copy for VNC-Installation:
cp install install.vnc ./mkzimage_cmdline -a 1 -c -s "vnc=1 vncpassword=abc123" install.vnc
