<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>pxe Archives - Vavai&#039;s Personal Notes</title>
	<atom:link href="https://www.vavai.net/tag/pxe/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.vavai.net/tag/pxe/</link>
	<description>Life is our precious gift</description>
	<lastBuildDate>Sat, 17 Jan 2009 03:29:15 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>Tutorial : openSUSE Network Install over PXE-Boot Part II</title>
		<link>https://www.vavai.net/tutorial-opensuse-network-install-over-pxe-boot-part-ii/</link>
					<comments>https://www.vavai.net/tutorial-opensuse-network-install-over-pxe-boot-part-ii/#comments</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Sat, 17 Jan 2009 03:29:15 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[pxe]]></category>
		<category><![CDATA[SUSE Family]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=457</guid>

					<description><![CDATA[<p>/* Note : It&#8217;s the second article regarding PXE Boot Setting. Please refer to Tutorial : openSUSE Network Install over PXE-Boot Part I for beginning configuration and Description about PXE Boot. */ PREPARING DHCP SERVICE DHCP (Dynamic Host Configuration Protocol) needed for supply the correct information for PXE Boot client. Install DHCP Service [code language=&#8217;cpp&#8217;]...</p>
<p>The post <a href="https://www.vavai.net/tutorial-opensuse-network-install-over-pxe-boot-part-ii/">Tutorial : openSUSE Network Install over PXE-Boot Part II</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><em><strong>/* Note : It&#8217;s the second article regarding PXE Boot Setting. Please refer to <a href="http://v2.vavai.net/2009/01/17/tutorial-opensuse-network-install-over-pxe-boot-a-complete-guide-part-i/">Tutorial : openSUSE Network Install over PXE-Boot Part I</a> for beginning configuration and Description about PXE Boot. */<br />
</strong></em><br />
<strong>PREPARING DHCP SERVICE<br />
</strong><br />
DHCP (Dynamic Host Configuration Protocol) needed for supply the correct information for PXE Boot client.</p>
<ol>
<li>Install DHCP Service<br />
[code language=&#8217;cpp&#8217;]<br />
zypper in -t pattern dhcp_dns_server<br />
[/code]</li>
<li>Move the default DHCP configuration. We will used the custom configuration<br />
[code language=&#8217;cpp&#8217;]<br />
mv /etc/dhcpd.conf /etc/dhcpd.conf.original<br />
[/code]</li>
<li>Create a new /etc/dhcpd.conf with text editor and copy-paste the configuration below<br />
[code language=&#8217;cpp&#8217;]<br />
# dhcpd.conf<br />
#<br />
# Sample configuration file for ISC dhcpd<br />
## option definitions common to all supported networks&#8230;<br />
#<br />
# All of this happens behind the firewall, and the whole domain<br />
# is made-up anwyay, so this is mostly fluff.<br />
#<br />
option domain-name &#8220;vavai.net&#8221;;<br />
# We don&#8217;t have Nameservers&#8230; so let&#8217;s just forget this item<br />
#option domain-name-servers ns1.networkboot.org, ns2.networkboot.org;<br />
default-lease-time 600;<br />
max-lease-time 7200;<br />
# if you do not use dynamical DNS updates:<br />
#<br />
# this statement is needed by dhcpd-3 needs at least this statement.<br />
# you have to delete it for dhcpd-2, because it does not know it.<br />
#<br />
# if you want to use dynamical DNS updates, you should first read<br />
# read /usr/share/doc/packages/dhcp-server/DDNS-howto.txt<br />
ddns-update-style none; ddns-updates off;<br />
# If this DHCP server is the official DHCP server for the local<br />
# network, the authoritative directive should be uncommented.<br />
#authoritative;<br />
# Use this to send dhcp log messages to a different log file (you also<br />
# have to hack syslog.conf to complete the redirection).<br />
log-facility local7;<br />
#  We only want to respond to PXE DHCP requests<br />
allow booting;<br />
# define rules to identify DHCP Requests from PXE and Etherboot clients.<br />
class &#8220;pxe&#8221; {<br />
match if substring (option vendor-class-identifier, 0, 9) = &#8220;PXEClient&#8221;;<br />
}<br />
class &#8220;etherboot&#8221; {<br />
match if substring (option vendor-class-identifier, 0, 9) = &#8220;Etherboot&#8221;;<br />
}<br />
# This is our subnet for PXE boot/installation.<br />
subnet 192.168.0.0 netmask 255.255.255.0 {<br />
option broadcast-address 192.168.0.255;<br />
pool {<br />
range 192.168.0.101 192.168.0.150; # only need a few addresses<br />
default-lease-time 180; # no long lease time required for booting<br />
max-lease-time 360;     # booted system does its own dhcp request<br />
server-name &#8220;192.168.0.8&#8221;; # This happens to be the IP of this server too<br />
next-server 192.168.0.8; # Address of the TFTP server<br />
filename &#8220;pxelinux.0&#8221;;<br />
allow members of &#8220;pxe&#8221;; # only respond to PXE requests<br />
allow members of &#8220;etherboot&#8221;; # allow etherboot, too<br />
}<br />
}<br />
[/code]</li>
<li>Make a proper change to /etc/dhcpd.conf, especially the IP Address of DHCP Server. In this scenario, I&#8217;m using address 192.168.0.8. If you used another subnet, change the <strong>subnet, broadcast and range</strong> address.</li>
<li>Edit /etc/sysconfig/dhcpd and activate the ethernet used for listen DHCP request. If you confused which ethernet will be used, try with ANY <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f600.png" alt="😀" class="wp-smiley" style="height: 1em; max-height: 1em;" /> as suggested on the configuration. I&#8217;m using eth0 so part of my configuration look like this :<br />
[code language=&#8217;cpp&#8217;]<br />
# Examples: DHCPD_INTERFACE=&#8221;eth0&#8243;<br />
#           DHCPD_INTERFACE=&#8221;eth0 eth1 eth2 tr0 wlan0&#8243;<br />
#           DHCPD_INTERFACE=&#8221;internal0 internal1&#8243;<br />
#           DHCPD_INTERFACE=&#8221;ANY&#8221;<br />
#<br />
DHCPD_INTERFACE=&#8221;eth0&#8243;<br />
[/code]</li>
<li>Start/Restart DHCP Service<br />
[code language=&#8217;cpp&#8217;]<br />
service dhcpd restart<br />
[/code]</li>
</ol>
<p><strong>PXE BOOT CONFIGURATION<br />
</strong></p>
<ol>
<li>Copy all of these file from [PATH-OF-DVD-CONTENTS]/boot/i386/loader into /srv/tftpboot : message, initrd and linux</li>
<li>Copy file : [PATH-OF-DVD-CONTENTS]/boot/i386/loader/isolinux.cfg into /srv/tftpboot/pxelinux.cfg/. Rename it into <strong>default</strong></li>
<li>Restart the DHCP Service<br />
[code language=&#8217;cpp&#8217;]<br />
service dhcpd restart<br />
[/code]</li>
</ol>
<h3><strong>USING PXE BOOT FOR INSTALLATION</strong></h3>
<ol>
<li>Prepare a PC with attached Network card. This computer will be used as client for PXE Boot Installation</li>
<li>Change BIOS Setting, activating Boot from LAN and switch the Boot Default Priority to boot from LAN</li>
<li>Restart the computer. It will boot from LAN and display the installation option.<br />
`<br />
<a href="http://54.254.121.108/wp-content/uploads/2009/01/tftp-server-21.jpeg"><img fetchpriority="high" decoding="async" class="size-full wp-image-454 alignnone" title="tftp-server-2" src="http://54.254.121.108/wp-content/uploads/2009/01/tftp-server-21.jpeg" alt="tftp-server-2" width="521" height="286" /></a></li>
</ol>
<p>The post <a href="https://www.vavai.net/tutorial-opensuse-network-install-over-pxe-boot-part-ii/">Tutorial : openSUSE Network Install over PXE-Boot Part II</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.vavai.net/tutorial-opensuse-network-install-over-pxe-boot-part-ii/feed/</wfw:commentRss>
			<slash:comments>3</slash:comments>
		
		
			</item>
		<item>
		<title>Tutorial : openSUSE Network Install over PXE-Boot Part I</title>
		<link>https://www.vavai.net/tutorial-opensuse-network-install-over-pxe-boot-a-complete-guide-part-i/</link>
					<comments>https://www.vavai.net/tutorial-opensuse-network-install-over-pxe-boot-a-complete-guide-part-i/#comments</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Sat, 17 Jan 2009 03:19:49 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[pxe]]></category>
		<category><![CDATA[SUSE Family]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=421</guid>

					<description><![CDATA[<p>PROLOGUE I&#8217;ve written a network installation or upgrading guide with a small script called setupgrubfornfsinstall earlier this month. It&#8217;s help a lot on my work : upgrading openSUSE 10.3 and 11.0 workstation into latest version openSUSE 11.1. Although the script quite useful, it&#8217;s not really satisfied either. The main problem is that the script need...</p>
<p>The post <a href="https://www.vavai.net/tutorial-opensuse-network-install-over-pxe-boot-a-complete-guide-part-i/">Tutorial : openSUSE Network Install over PXE-Boot Part I</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h3><img decoding="async" class="size-full wp-image-458 alignnone" title="pxe" src="http://54.254.121.108/wp-content/uploads/2009/01/pxe1.jpg" alt="pxe" width="405" height="261" /></h3>
<h3><strong>PROLOGUE</strong></h3>
<p>I&#8217;ve written a network installation or upgrading guide with a <a href="http://v2.vavai.net/2009/01/04/opensuse-network-installationupgrade-without-cddvd/">small script called setupgrubfornfsinstall</a> earlier this month. It&#8217;s help a lot on my work : upgrading openSUSE 10.3 and 11.0 workstation into latest version openSUSE 11.1.<br />
Although the script quite useful, it&#8217;s not really satisfied either. The main problem is that the script need a running openSUSE or SUSE Linux Enterprise. It can&#8217;t be used to install or upgrade on an empty system or to remove another system.<br />
I catch the problem while installing openSUSE 11.1 on broken Windows system. It has no CD or DVD ROM. I may install the system by borrowed the CD/DVD ROM from another PC or using external CD/DVD ROM or by using <a href="http://v2.vavai.net/2009/01/02/how-to-make-opensuse-111-liveusb/">openSUSE 11.1 LiveUSB</a>, but I think it&#8217;s a good chance to try better method : Installing openSUSE 11.1 over network with PXE Boot.<br />
<strong>WHAT IS THE PXE BOOT INSTALLATION METHOD ?</strong><br />
PXE stand for Preboot Execution Environment. PXE is way to start computers without Floppy/Hard Disk/CD-ROM, that is, the BIOS will start right from the network using the PXE protocol. Of course, in order for PXE to work the server needs OS configuration, and the client side needs a code module that runs PXE for the given LAN card (NIC).<br />
Most newer mainboards that have an on-board LAN port already have the module as part of their BIOS image. It&#8217;s called BOOTROM. You will need to activating the BOOTROM capability within BIOS setup. Setup process may vary depending your mainboard configuration, but occasionally the setup placed on Advanced Setup and Port Setup. The Advanced setup required to make Network or LAN as first choice on boot start up option. The port setup need to activating Boot from LAN by enabling the option.<br />
<strong>WHAT IS THE BENEFIT OF PXE BOOT INSTALLATION ?</strong></p>
<ol>
<li>Do not need CD/DVD ROM, LiveUSB or existing and running system. The one-and-only requirement is Network Card that support Boot from LAN. Most of current motherboard and LAN Card support this<strong>.</strong></li>
<li>Fairly easy to setup</li>
<li>Do not need burn media. Standard Network installation need Net ISO Image for boot the start up installation process but PXE boot won&#8217;t need the ISO.</li>
<li><span class="copy">Reduces staff costs for installation and eliminates human errors</span></li>
<li><span class="copy">Reduces time used for preparing the installation</span></li>
<li><span class="copy">With autoyast capability, the PXE boot </span><span class="copy">can automate software installation and system configuration. The process itself occasionally called &#8216;unattended installation&#8217;. for now, I will keep this post focus on PXE boot, the autoyast will be discussed later. Please refer to <a href="http://en.opensuse.org/YaST_Autoinstallation">this link</a> for <a href="http://en.opensuse.org/Autoyast_installation_using_a_network_installation_source">autoyast documentation</a>.<br />
</span></li>
</ol>
<h3><strong>SERVER CONFIGURATION<br />
</strong></h3>
<p><strong>PREPARING INSTALLATION SOURCE</strong><br />
In this scenario, I will used network installation source using http protocol. You may also used another protocol, ie : smb, nfs, ftp, etc.</p>
<ol>
<li>Install Apache server, make a folder called 11.1 on /srv/www/htdocs<br />
[code language=&#8217;cpp&#8217;]<br />
zypper in -t pattern lamp_server<br />
service apache2 start<br />
mkdir /srv/www/htdocs/11.1<br />
[/code]</li>
<li>Copy openSUSE 11.1 DVD contents into /srv/www/htdocs/11.1.</li>
<li>If you wish to use ISO image instead of DVD, mount the ISO image (<strong>mount -o loop iso-image target-folder</strong>). Mount it into /srv/www/htdocs/11.1 for temporary used or mount it into another folder and then copy the contents into /srv/www/htdocs/11.1. The second choice will make the content permanent</li>
</ol>
<p><strong>PREPARING TFTP SERVER<br />
</strong><br />
TFTP Server stand for <strong>Trivial File Transport Protocol</strong> (<strong>TFTP</strong>), a very simple file transfer <span class="mw-redirect">protocol</span>, with the functionality of a very basic form of FTP. The initial stages of some network based installation systems (such as Solaris Jumpstart, Red Hat Kickstart and openSUSE AutoYAST) use TFTP to load a basic kernel that performs the actual installation.<br />
We will used TFTP Server for preparing resource on initial stage of PXE Boot Installation.</p>
<ol>
<li>Install TFTP Server<br />
[code language=&#8217;cpp&#8217;]<br />
zypper in yast2-tftp-server tftp<br />
[/code]</li>
<li>Configure TFTP Server. Click YAST | Network Services | TFTP Server<br />
`<br />
<a href="http://v2.vavai.net/wp-content/uploads/2009/01/tftp-server-1.jpeg"><img decoding="async" class="size-full wp-image-455 alignnone" title="tftp-server-1" src="http://v2.vavai.net/wp-content/uploads/2009/01/tftp-server-1.jpeg" alt="tftp-server-1" width="354" height="301" /></a></li>
<li>Click Enable, change the <strong>Boot Image Directory</strong> into <strong>/srv/tftpboot</strong>. Don&#8217;t forget to give a thick on <strong>Open Port in Firewall</strong> if you used Firewall. The default image directory is /tftpboot. I&#8217;m using /srv/tftpboot because I&#8217;m not really comfortable to make new folder on root directory. I highly recommended to used this folder to prevent any confused setting. If you wish to used your custom folder, don&#8217;t forget to change the proper setting on /etc/dhcpd.conf on next setting. Please refer to <a href="http://v2.vavai.net/2009/01/13/solved-pxe-boot-failed-pxe-t01-file-not-found/">my post earlier this month about PXE-Boot problem</a>.</li>
<li>Click OK</li>
<li>Check on <strong>/srv/tftpboot</strong> directory, you will see some files and folder needed for PXE Boot has been copied automatically.</li>
</ol>
<p>Continue to : <a href="http://v2.vavai.net/2009/01/17/tutorial-opensuse-network-install-over-pxe-boot-part-ii/">Tutorial : openSUSE Network Install over PXE-Boot Part II</a></p>
<p>The post <a href="https://www.vavai.net/tutorial-opensuse-network-install-over-pxe-boot-a-complete-guide-part-i/">Tutorial : openSUSE Network Install over PXE-Boot Part I</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.vavai.net/tutorial-opensuse-network-install-over-pxe-boot-a-complete-guide-part-i/feed/</wfw:commentRss>
			<slash:comments>8</slash:comments>
		
		
			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Object Caching 8/83 objects using Disk
Page Caching using Disk: Enhanced 
Content Delivery Network via Amazon Web Services: CloudFront: d3b35uem336dgh.cloudfront.net
Lazy Loading (feed)
Minified using Disk
Database Caching using Disk (Request-wide modification query)

Served from: www.vavai.net @ 2026-11-14 16:30:20 by W3 Total Cache
-->