Starting the Install



Are we ready?

At this point, you should have started inetd, tftp, nfs, and either bootp OR dhcp. You should have created a kernel resource, map resource, typically 5 file system resources, and a disk partition resource. (The 5 file system resources represent /usr, /home, /var, /boot and root (/). If you are installing from rpm, you should have created an rpm resource. If you are installing from tarball, when you created your file system resources, you should not have used the -c option, forcing LUI to create tarballs of your local server file systems. If you are installing from rpm, it is recommended that you create a source resource for the /etc/shadow file, otherwise you will not be able to log in.

You can verify your definitions/resources with the LUI lslimm, lslimr, lslimg [-n] commands.

Boot the Node

With all the services in place, and all the resources created and allocated, you are ready to install a node using LUI. Power on the node to be installed. It should broadcast its MAC address looking for a server. The server should respond with the client's IP information, and tell it to use the PXE method or non-PXE method of install. The kernel will get transferred over the network, and attempt to NFS mount the remote root file system (/tftpboot/client-ip-address) and /usr from the server. If all goes well, you will shortly start to hear the node harddrive start to grind as it creates the disk partitions and the local file systems. The clone script gets control, and either tranfers the tar files (for a tarball install) or starts installing the node from a list of rpms (for rpm install). When the node is completely done installing, check the client log in /tftpboot/lim/log/(clientname).log. If installation completely successfully, the last message you will see is that it's time to reboot the client node. So, if you installed using diskette, pop the diskette out before rebooting the client. If you installed without using diskettes, you will have to either a) change the bootlist or b) remove the entry for the client from the /etc/dhcpd.conf file before rebooting.