Finish editorial review of this chapter.

Next commit will close PR62412.

Sponsored by: iXsystems
This commit is contained in:
Dru Lavigne 2014-03-05 19:27:42 +00:00
parent ba74cf0ffc
commit e4bbb2ce58
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=44136

View file

@ -4290,29 +4290,27 @@ cd /usr/src/etc; make distribution</programlisting>
--> -->
<sect2> <sect2>
<title>Configuring the <acronym>PXE</acronym> Client and <title>Debugging <acronym>PXE</acronym> Problems</title>
Debugging Connection Problems</title>
<para>Once all of the services are configured and started,
<acronym>PXE</acronym> clients should be able to
automatically load &os; over the network. If a particular
client is unable to connect,
when that client machine boots up, enter the
<acronym>BIOS</acronym> configuration menu and confirm
that it is set to boot from the network.</para>
<para>This section describes some troubleshooting tips
for isolating the source of the configuration problem should no
clients be able to <acronym>PXE</acronym> boot.</para>
<procedure> <procedure>
<step>
<para>When the client machine boots up, enter the
<acronym>BIOS</acronym> configuration menu. Configure the
<acronym>BIOS</acronym> to boot from the network. If all
previous configuration steps are correct, everything
should &quot;just work&quot;.</para>
</step>
<step> <step>
<para>Use the <package>net/wireshark</package> package or <para>Use the <package>net/wireshark</package> package or
port to debug the network traffic involved during the port to debug the network traffic involved during the
<acronym>PXE</acronym> booting process, as illustrated <acronym>PXE</acronym> booting process, which is illustrated
in the diagram below. In <xref in the diagram below.</para>
linkend="network-pxe-setting-up-dhcp"/>, an example
configuration is shown where the <acronym>DHCP</acronym>,
<acronym>TFTP</acronym>, and <acronym>NFS</acronym>
servers are on the same machine. However, these
servers can be on separate machines.</para>
<figure> <figure>
<title><acronym>PXE</acronym> Booting Process with <title><acronym>PXE</acronym> Booting Process with
@ -4373,8 +4371,7 @@ cd /usr/src/etc; make distribution</programlisting>
</step> </step>
<step> <step>
<para>Make sure that the <filename>pxeboot</filename> file <para>On the
can be retrieved by <acronym>TFTP</acronym>. On the
<acronym>TFTP</acronym> server, read <acronym>TFTP</acronym> server, read
<filename>/var/log/xferlog</filename> to ensure that the <filename>/var/log/xferlog</filename> to ensure that the
<filename>pxeboot</filename> file is being retrieved from <filename>pxeboot</filename> file is being retrieved from
@ -4397,21 +4394,6 @@ Received 264951 bytes in 0.1 seconds</screen>
<screen>&prompt.root; <userinput>mount -t nfs 192.168.0.1:/b/tftpboot/FreeBSD/install /mnt</userinput></screen> <screen>&prompt.root; <userinput>mount -t nfs 192.168.0.1:/b/tftpboot/FreeBSD/install /mnt</userinput></screen>
</step> </step>
<step>
<para>Read the code in
<filename>src/sys/boot/i386/libi386/pxe.c</filename> to
understand how the <filename>pxeboot</filename> loader
sets variables like <literal>boot.nfsroot.server</literal>
and <literal>boot.nfsroot.path</literal>. These variables
are then used in the <acronym>NFS</acronym> diskless root
mount code in
<filename>src/sys/nfsclient/nfs_diskless.c</filename>.</para>
</step>
<step>
<para>Read &man.pxeboot.8; and &man.loader.8;.</para>
</step>
</procedure> </procedure>
</sect2> </sect2>
</sect1> </sect1>