📄 c-booting5.html
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"><html><head><link rel="STYLESHEET" type="text/css" href="wrs.css"><title> Booting over the Network </title></head><body bgcolor="FFFFFF"><p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a><a href="c-booting.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="c-booting.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="c-booting4.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-booting6.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p><font face="Helvetica, sans-serif" class="sans"><h3 class="H2"><i><a name="84862">13.5 Booting from the Shared-Memory Network </a></i></h3></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84864"> </a>Targets on the shared-memory network can boot using BOOTP only if proxy ARP is enabled (see <a href="c-network.html#"><i class="title">Proxy ARP Overview</i></a>). A target on the shared-memory network keys its entry in the BOOTP database by its IP address. A shared-memory network target's entry in the BOOTP database looks something like:</p><dl class="margin"><dd><pre class="Code2"><b><a name="84868">vx232:ip=150.12.1.232:tc=global.dummy</a></b></pre></dl><dd><p class="Body"><a name="84869"> </a>A shared-memory network's master entry in the BOOTP database looks like:</p><dl class="margin"><dd><pre class="Code2"><b><a name="84870">vx230:ht=ethernet:ha=0000530e0018:ip=150.12.1.230:tc=global.dummy</a></b></pre></dl><dd><p class="Body"><a name="84871"> </a>The following example is a master processor using a combination of BOOTP, TFTP, proxy ARP, sequential addressing, and proxy default addressing for booting:<sup><a href="#foot"><b class="FootnoteMarker">1</b></a></sup> </p></dl><dl class="margin"><dd><pre class="Code"><b><a name="85691"></b><tt class="output"> [VxWorks Boot]:</tt><b> @ </b><tt class="output"> boot device : ln processor number : 0 flags (f) : 0xc0 Attaching network interface ln0... done. Getting boot parameters via network interface ln0. Bootp Server:150.12.1.159 </tt><b>[1]</b><tt class="output"> Boot file: /usr/wind/target/vxBoot/vxWorks.vx230 </tt><b>[1]</b><tt class="output"> Boot host: 150.12.1.159 </tt><b>[1]</b><tt class="output"> Boot device Addr (ln0): 150.12.1.230 </tt><b>[1]</b><tt class="output"> Subnet mask: 0xffffff00 Attaching network interface lo0... done. Loading... 370356 + 28040 + 20196 Starting at 0x1000...</tt><b></a></b><dd> <b><a name="84891">[2]</b><tt class="output"> Host Name: bootHost </tt><b>[2]</b><tt class="output"> Target Name: vxTarget </tt><b>[2]</b><tt class="output"> User: target Attaching network interface ln0... done. Initializing backplane net with anchor at 0x800000... done. Backplane anchor at 0x800000... Attaching network interface sm0... done.</tt><b></a></b><dd> <b><a name="84898">[3]</b><tt class="output"> Backplane address: 150.12.1.231 Creating proxy network: 150.12.1.231 Attaching network interface lo0... done.</tt><b></a></b></pre></dl><dl class="margin"><dd><p class="Body"><a name="84901"> </a>The parameters from the preceding output came from the following sources:</p><dl class="margin"><dd><p class="ListV"><a name="84902"> </a>[1] These lines all display information retrieved from the BOOTP database. </p><dd><p class="ListV"><a name="84903"> </a>[2] These lines display information you set during configuration (defaults). </p><dd><p class="ListV"><a name="84904"> </a>[3] These lines appear because you have configured VxWorks with "proxy arp server," "auto address setup," and "default address for bp" (the configuration macros <b class="symbol_UC">INCLUDE_PROXY_SERVER</b>, <b class="symbol_UC">INCLUDE_SM_SEQ_ADDR</b>, and <b class="symbol_UC">INCLUDE_PROXY_DEFAULT_ADDR</b>). (Note that the address is one more than that of parameter <b class="symbol_lc">inet on ethernet</b>, in this case 150.12.1.230.)</p></dl><dd><p class="Body"><a name="84905"> </a>The following example shows booting a slave processor using a combination of BOOTP, TFTP, and sequential addressing:</p></dl><dl class="margin"><dd><pre class="Code"><b><a name="84906"></b><tt class="output"> [VxWorks Boot]:</tt><b> @ </b><tt class="output"> boot device : sm=0x800000 processor number : 1 flags (f) : 0x1c0 Backplane anchor at 0x800000... Attaching network interface sm0... done.</tt><b></a></b><dd> <b><a name="84912">[1]</b><tt class="output"> Backplane inet address: 150.12.1.232 registering proxy client: 150.12.1.232.done. Getting boot parameters via network interface sm0. Bootp Server:150.12.1.159 </tt><b>[2]</b><tt class="output"> Boot file: /usr/wind/target/vxBoot/vxWorks.vx232 </tt><b>[2]</b><tt class="output"> Boot host: 150.12.1.159 </tt><b>[2]</b><tt class="output"> Subnet mask: 0xffffff00 Attaching network interface lo0... done. Loading... 370356 + 28040 + 20196 Starting at 0x1000... </tt><b>[3]</b><tt class="output"> Host Name: bootHost </tt><b>[3]</b><tt class="output"> Target Name: vxTarget </tt><b>[3]</b><tt class="output"> User: target Backplane anchor at 0x800000... Attaching network interface sm0... done. Attaching network interface lo0... done.</tt><b></a></b></pre></dl><dl class="margin"><dd><p class="Body"><a name="84927"> </a>The parameters from the preceding output came from the following sources:</p><dl class="margin"><dd><p class="ListV"><a name="84928"> </a>[1] These lines appear because you have configured VxWorks with "proxy arp client" and "auto address setup" (the configuration constants <b class="symbol_UC">INCLUDE_PROXY_CLIENT</b> and <b class="symbol_UC">INCLUDE_SM_SEQ_ADDR</b>)<b class="symbol_UC"><sup><a href="#foot"><b class="FootnoteMarker">2</b></a></sup></b>. (Note that the address is equal to the master CPU's backplane address plus the client's processor number.)</p><dd><p class="ListV"><a name="84932"> </a>[2] These lines all display information retrieved from the BOOTP database.</p><dd><p class="ListV"><a name="84934"> </a>[3] These lines display information you set during configuration(defaults).</p></dl></dl></dl><a name="foot"><hr></a><p class="FootnoteNumberMarker">1: <span class="Footnote"><a name="84874"> </a>The use of sequential addressing can make it difficult to use DHCP. </span><p class="FootnoteNumberMarker">2: <span class="Footnote"><a name="84931"> </a>The use of sequential IP addressing makes this procedure incompatible with DHCP. </span><p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a><a href="c-booting.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="c-booting.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="c-booting4.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-booting6.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p></body></html><!---by WRS Documentation (), Wind River Systems, Inc. conversion tool: Quadralay WebWorks Publisher 4.0.11 template: CSS Template, Jan 1998 - Jefro --->⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -