Changes between Version 11 and Version 12 of Internal/ImageInstall

Timestamp:

Aug 31, 2006, 7:03:38 PM (18 years ago)

Author:

ssugrim

Comment:

Clean up, Tip additions

Internal/ImageInstall

@@ -6 +6 @@
 PXE: This is a concerted effort between the dhcp server and the tftp server. In the dhcpd.conf file in the parameter "nextserver" is interpreted by the pxe booting clinet as "where to look" for the boot img (and associated directive files). The booting clinet then initiates a tftp session with the "next-server" and downloads an directive file that tells it what image to copy, uncompress, and boot. 
 
+{{{
+Our current setup:
+DHCPD runs on dhcp1.orbit-lab.org
+AFTPD runs on repository2.orbit-lab.org (10.0.50.40, this is "next-server") 
+}}}
 
 step 2 --
@@ -11 +16 @@
 Getting the boot image: 
 
-On the tftp server a boot menu file (I'm going to call it that for lack of something better to call it) is stored in /tfptboot/pexlinux.cfg/ . It contains information on what image to download, and what boot flags to apply to the kernel.
+On the tftp server a boot instructions file '''(BIF)''' is stored in /tfptboot/pexlinux.cfg/ . It contains information on what image to download, and what boot flags to apply to the kernel.
 
-When the booting client wakes up, and establishes a tftp session with "next-server", it looks for a file in the /tftpboot/pxelinux.cfg directory that has it's '''IP ADDRESS''' as the name of the file ('''IN HEX, with no field delimiters'''). 
+When the booting client wakes up, and establishes a tftp session with "next-server", it looks for BIF in the /tftpboot/pxelinux.cfg directory that has it's '''IP ADDRESS''' as the name of the file ('''IN HEX, with no field delimiters'''). 
 
 {{{
@@ -21 +26 @@
 0A00FAF6
 
-NOTE: The link should point to the boot menu file NOT the image.
+NOTE: The link should point to the BIF NOT the image.
 }}}
 
-Assuming that the image file and boot menu file are valid, the booting client will boot and eventually put you at a console.
+Assuming that the image file and BIF are valid, the booting client will boot and eventually put you at a console. If the file of apprioate name isn't there, the client will strip off the last bit and seach for a file of that name (In our example the next would be 0A00FAF), and proceed until there are not bits left. This can be used to get a collection of clients in a range of address to boot from the same image. 
+
+{{{
+TIP:
+Some snags I've run into:
+
+P:DHCP "next-server" point to the wrong machine
+S: Edit the dhcpd.conf file on the dhcp server and adjust the next-server paramenter for the appropriate group. (Make sure your adjusting the next-server for the group for which you belong. You can watch the boot messages on the pxe-client to figure out what group dhcp is putting you in.)
+
+P: TFPTD dosen't respond 
+S: Restart TFTPD on the next-server. In our current setup this is repository2 and the server name is AFTPD. 
+
+P:
+
+
+}}}
+
+
 
 once at the console, the resting place of the image was mounted.