Changes between Version 15 and Version 16 of Internal/ImageInstall

Timestamp:

Aug 31, 2006, 11:22:11 PM (18 years ago)

Author:

ssugrim

Comment:

—

Internal/ImageInstall

@@ -33 +33 @@
 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 search 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, by naming the file something "smaller" in bits. 
 
-{{{
-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.)
+Some snags I've run into: [[BR]]
 
-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:DHCP "next-server" point to the wrong machine [[BR]]'''
+''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: No BIF get loaded by the client, and the machine moves to other boot media
-S: Make sure the file is named appropriately. When the pxe clinet searches for the BIF, it list (and displays on screen) 
-the names it tires. If you don't see this list of attempts, the client hasn't found / communicated with the tftp server. 
-If you see the list, a clever use of the Pause/Break key will help you find what its looking for. 
+'''P: TFPTD dosen't respond''' [[BR]]
+''S: Restart TFTPD on the next-server. In our current setup this is repository2 and the server name is AFTPD. ''
 
-}}}
+'''P: No BIF get loaded by the client, and the machine moves to other boot media''' [[BR]] 
+''S: Make sure the file is named appropriately. When the pxe clinet searches for the BIF,it list (and displays on screen) the names it tires. If you don't see this list of attempts, the client hasn't found / communicated with the tftp server. If you see the list, a clever use of the Pause/Break key will help you find what its looking for.''
+
+----
 
 once at the console, the resting place of the image was mounted.
@@ -68 +65 @@
 
 {{{
-Note: NFS is not particularly fourth coming with information. For instance if you type the name of the share point incorrectly, 
-you get a permission denied error. Some what misleading
+Note: NFS is not particularly fourth coming with information. For instance if you type the 
+name of the share point incorrectly, you get a permission denied error. Some 
+what misleading.
 }}}