Date: Wed, 5 Mar 2014 19:27:43 +0000 (UTC) From: Dru Lavigne <dru@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44136 - head/en_US.ISO8859-1/books/handbook/advanced-networking Message-ID: <201403051927.s25JRh3B061563@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: dru Date: Wed Mar 5 19:27:42 2014 New Revision: 44136 URL: http://svnweb.freebsd.org/changeset/doc/44136 Log: Finish editorial review of this chapter. Next commit will close PR62412. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Wed Mar 5 18:57:15 2014 (r44135) +++ head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Wed Mar 5 19:27:42 2014 (r44136) @@ -4290,29 +4290,27 @@ cd /usr/src/etc; make distribution</prog --> <sect2> - <title>Configuring the <acronym>PXE</acronym> Client and - Debugging Connection Problems</title> + <title>Debugging <acronym>PXE</acronym> 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> <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 "just work".</para> - </step> - - <step> <para>Use the <package>net/wireshark</package> package or port to debug the network traffic involved during the - <acronym>PXE</acronym> booting process, as illustrated - in the diagram below. In <xref - 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> + <acronym>PXE</acronym> booting process, which is illustrated + in the diagram below.</para> <figure> <title><acronym>PXE</acronym> Booting Process with @@ -4373,8 +4371,7 @@ cd /usr/src/etc; make distribution</prog </step> <step> - <para>Make sure that the <filename>pxeboot</filename> file - can be retrieved by <acronym>TFTP</acronym>. On the + <para>On the <acronym>TFTP</acronym> server, read <filename>/var/log/xferlog</filename> to ensure that the <filename>pxeboot</filename> file is being retrieved from @@ -4397,21 +4394,6 @@ Received 264951 bytes in 0.1 seconds</sc <screen>&prompt.root; <userinput>mount -t nfs 192.168.0.1:/b/tftpboot/FreeBSD/install /mnt</userinput></screen> </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> </sect2> </sect1>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201403051927.s25JRh3B061563>