📄 x-vxsim5.html
字号:
<td colspan=1 rowspan=1><p class="BodyLeft"><a name="84859"> </a>Networking UUCP Utilities, (Root)</p></td></tr><tr valign="top"><td colspan=1 rowspan=1><p class="BodyLeft"><a name="84861"> </a><b class="keyword">SUNWbnuu</b></p></td><td colspan=1 rowspan=1><p class="BodyLeft"><a name="84863"> </a>Networking UUCP Utilities, (Usr)</p></td></tr><tr valign="middle"><td colspan="20"></td></tr></table></p></p><dd><p class="Body"><a name="84864"> </a>For example:</p><dl class="margin"><dd><pre class="Code2"><b><a name="84865"></b><tt class="output">% </tt><b>pkginfo | egrep 'ppp|bnu' </b><tt class="output">system SUNWapppr PPP/IP Asynchronous PPP daemon configuration files system SUNWapppu PPP/IP Asynchronous PPP daemon and PPP login service system SUNWpppk PPP/IP and IPdialup Device Drivers system SUNWbnur Networking UUCP Utilities, (Root) system SUNWbnuu Networking UUCP Utilities, (Usr) % </tt><b></a></b></pre></dl><dd><p class="Body"><a name="84872"> </a>If they are not already installed, mount the Solaris installation disk and change your working directory to the location of these packages (for example, on a Solaris 2.5.1 CD-ROM they can be found in <b class="file">/cdrom/solaris_2_5_1_sparc/s0/Solaris_2.5.1</b>) and install them with the following commands:</p><dl class="margin"><dd><pre class="Code2"><b><a name="84873"></b><tt class="output">%</tt><b> su root </b><tt class="output">Password: # </tt><b>pkgadd -d `pwd` SUNWbnur SUNWbnuu SUNWpppk SUNWapppr SUNWapppu</a></b></pre></dl><dd><p class="Body"><a name="84874"> </a>Next, as <b>root</b>, copy <i class="textVariable">installDir</i><b class="file">/target/config/solaris/asppp.cf</b> to the <b class="file">/etc</b> directory as follows (replace the leading path segment <i class="textVariable">installDir</i><b class="file">/target/ </b>with the path to your installed Tornado tree):</p><dl class="margin"><dd><pre class="Code2"><b><a name="84884"></b><tt class="output"># </tt><b>cp <i class="textVariable">installDir</i>/target/config/solaris/asppp.cf /etc</a></b></pre></dl></dl><dd><p class="table" callout><table border="0" cellpadding="0" cellspacing="0"><tr valign="top"><td valign="top" width="40"><br><img border="0" alt="*" src="icons/caution.gif"></td><td><hr><div class="CalloutCell"><a name="84879"><b class="symbol_UC"><font face="Helvetica, sans-serif" size="-1" class="sans">CAUTION: </font></b></a>If you already have <b class="command">aspppd</b> running, stop it with <b class="command">asppp stop</b> before proceeding.</div></td></tr><tr valign="top"><td></td><td><hr></td></tr><tr valign="middle"><td colspan="20"></td></tr></table></p callout><dl class="margin"><dd><p class="Body"><a name="84885"> </a>Finally, start the PPP daemon <b class="command">aspppd</b> by typing the following as <b>root</b>: </p><dl class="margin"><dd><pre class="Code2"><b><a name="84886"></b><tt class="output"># </tt><b>/etc/init.d/asppp start</a></b></pre></dl><dd><p class="Body"><a name="84887"> </a>The PPP driver is now installed and running on your Solaris system, and will be restarted automatically when Solaris reboots.</p><dd><p class="Body"><a name="84888"> </a>The PPP configuration assigns IP addresses 127.0.1.0 through 127.0.1.15 to sixteen devices, and associates with them the peer system names <b class="file">vxsim0</b> through <b class="file">vxsim15</b>, respectively.</p><dd><p class="Body"><a name="84889"> </a>You can also use the following commands to start or stop the Solaris PPP driver after the driver has been installed (you must have <b>root</b> privileges):</p><dl class="margin"><dd><pre class="Code2"><b><a name="86326"></b><tt class="output"># </tt><b>/etc/init.d/asppp start</a></b><dd> <b><a name="86327"></b><tt class="output"># </tt><b>/etc/init.d/asppp stop</a></b></pre></dl></dl></dl><dl class="margin"><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="86329">Loading SLIP on a HP-UX Host</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="85952"> </a>Some additional configuration of your system is required to complete the connection. Perform the following steps to configure SLIP:</p></dl><dl class="margin"><p><ol class="List"><li value="1."><a name="84895"> </a>Update your <b class="file">ppl.remotes</b> file.</li></ol></p><dl class="margin"><dd><div class="Indent"><a name="84896"> </a>HP-UX uses <b class="command">ppl</b> to configure <b class="file">pty</b> lines for SLIP (see the HP-UX man page for <b class="command">ppl</b>). Each SLIP line requires a <b class="command">ppl</b> process. When a <b class="command">ppl</b> process is initiated, its configuration parameters are read from the configuration file <b class="file">/etc/ppl/ppl.remotes</b>.</div><br></dl><dl class="margin"><p><ol class="List2"><li value="1" type="a"><a name="84897"> </a>If you use none of your SLIP lines for other applications, you may replace <b class="file">/etc/ppl/ppl.remotes</b> with the provided configuration file <i class="textVariable">installDir</i><b class="file">/target/config/hpux/ppl.remotes.hpux10</b>:</li></ol></p><dl class="margin"><dd><pre class="Code3"><b><a name="84898"></b><tt class="output">% </tt><b>su </b><tt class="output"># </tt><b>cd /etc/ppl </b><tt class="output"># </tt><b>mv ppl.remotes ppl.remotes.bak </b><tt class="output"># </tt><b>cp <i class="textVariable">installDir</i>/target/config/hpux/ppl.remotes.hpux10 ppl.remotes</a></b></pre></dl><p><ol class="List2"><li value="2" type="a"><a name="84899"> </a>If your system is already using SLIP, <b class="file">/etc/ppl/ppl.remotes</b> contains working data, not just comments and a template for future additions.</li></ol></p><dl class="margin"><dd><div class="Indent2"><a name="84900"> </a>Edit <b class="file">/etc/ppl/ppl.remotes</b> and import the entries from <i class="textVariable">installDir</i><b class="file">/target/config/hpux/ppl.remotes.hpux10</b>. Be sure to adhere to the format restrictions of the <b class="file">ppl.remotes</b> file, or the PPL software can not parse the entries.</div><br></dl></dl><dl class="margin"><dd><div class="Indent"><a name="84901"> </a>See your system administrator with any concerns.</div><br></dl><p><ol class="List"><li value="2."><a name="84902"> </a>Start the <b class="command">ppl</b> process.</li></ol></p><dl class="margin"><dl class="margin"><dd><pre class="Code3"><b><a name="84903"></b><tt class="output">% </tt><b>su </b><tt class="output"># </tt><b>ppl -o -t /dev/ptym/ptyr<i class="textVariable">n</i> 192.168.1.<i class="textVariable">n</i> </a></b></pre></dl></dl><dl class="margin"><dd><div class="Indent"><a name="84904"> </a>Each simulator should have a unique pseudo-terminal device, the second argument of the <b class="command">ppl</b> command, in the range <b class="symbol_lc">ptyr0</b> to <b class="symbol_lc">ptyr9</b>. If one of these pseudo-terminals is already in use, choose another set of pseudo-terminals to use, such as <b class="symbol_lc">ptyq0</b> to <b class="symbol_lc">ptyq9</b>. (Examine the directory <b class="file">/dev/ptym</b> for the complete collection of pseudo-terminal devices.)</div><br></dl></dl></dl><dl class="margin"><dd><p class="table" callout><table border="0" cellpadding="0" cellspacing="0"><tr valign="top"><td valign="top" width="40"><br><img border="0" alt="*" src="icons/note.gif"></td><td><hr><div class="CalloutCell"><a name="84909"><b class="symbol_UC"><font face="Helvetica, sans-serif" size="-1" class="sans">NOTE: </font></b></a>If you use a <b class="file">pty</b> group other than the default, you must redefine <b class="symbol_UC">SLIP_PSEUDO_TTY_PATH</b> in <b class="file">config.h</b>. This macro can not be configured using the project facility. For this reason, while you must configure it manually, doing so does not prevent you from using the project facility to configure the rest of your project. </div></td></tr><tr valign="top"><td></td><td><hr></td></tr><tr valign="middle"><td colspan="20"></td></tr></table></p callout><dl class="margin"><dl class="margin"><dd><div class="Indent"><a name="84914"> </a>The last argument to <b class="command">ppl</b> is the IP address of the VxWorks target. In the case shown above, <i class="textVariable">n</i> corresponds to the VxWorks processor number. Each simulator must have its own <b class="command">ppl</b> process. For example, to add a PPL connection for VxWorks processor number 5, use the following command:</div><br><dl class="margin"><dd><pre class="Code3"><b><a name="84924"></b><tt class="output"># </tt><b>ppl -o -t /dev/ptym/ptyr5 192.168.1.5 </a></b></pre></dl></dl></dl><dd><p class="table" callout><table border="0" cellpadding="0" cellspacing="0"><tr valign="top"><td valign="top" width="40"><br><img border="0" alt="*" src="icons/caution.gif"></td><td><hr><div class="CalloutCell"><a name="84919"><b class="symbol_UC"><font face="Helvetica, sans-serif" size="-1" class="sans">CAUTION: </font></b></a>HP-UX kernels allow only two SLIP network interfaces to operate at one time. If you want to run more than two simulators, you must rebuild your HP-UX kernel. The parameter that sets the number of interfaces is <b class="keyword">NNI</b> in <b class="file">/usr/conf/master.d/net</b>. Do not configure more than 10 network interfaces, as this is the maximum number allowed according to the file <b class="file">/usr/conf/net/if_ni.h</b>.</div></td></tr><tr valign="top"><td></td><td><hr></td></tr><tr valign="middle"><td colspan="20"></td></tr></table></p callout><dl class="margin"><p><ol class="List"><li value="3."><a name="86014"> </a>Enable IP packet forwarding.</li></ol></p><dl class="margin"><dd><div class="Indent"><a name="86015"> </a>By default, the VxSim BSP is built to use SLIP over the network on an HP-UX host. To <b class="routine"><i class="routine">ping</i></b><b>( )</b> two VxSim targets, IP packet forwarding must be enabled.</div><br><dd><div class="Indent"><a name="86016"> </a>To view the current <b class="symbol_lc">ip_forwarding</b> flag status, use the following command:</div><br><dl class="margin"><dd><pre class="Code3"><b><a name="86017"></b><tt class="output">%</tt><b> ndd /dev/ip ip_forwarding</a></b></pre></dl><dd><div class="Indent"><a name="86018"> </a>To enable IP packet forwarding, set the parameter <b class="symbol_lc">ip_forwarding</b> in the IP driver to one:</div><br><dl class="margin"><dd><pre class="Code3"><b><a name="86019"></b><tt class="output">%</tt><b> ndd -set /dev/ip ip_forwarding 1</a></b></pre></dl></dl></dl><dd><p class="table" callout><table border="0" cellpadding="0" cellspacing="0"><tr valign="top"><td valign="top" width="40"><br><img border="0" alt="*" src="icons/note.gif"></td><td><hr><div class="CalloutCell"><a name="86024"><b class="symbol_UC"><font face="Helvetica, sans-serif" size="-1" class="sans">NOTE: </font></b></a>You have to be 'root' to use <b class="symbol_lc">ndd</b>.</div></td></tr><tr valign="top"><td></td><td><hr></td></tr><tr valign="middle"><td colspan="20"></td></tr></table></p callout><dl class="margin"><p><ol class="List"><li value="4."><a name="84925"> </a>Check your network interface.</li></ol></p><dl class="margin"><dl class="margin"><dd><pre class="Code3"><b><a name="84926"># netstat -i</a></b></pre></dl></dl><dl class="margin"><dd><div class="Indent"><a name="84927"> </a>For example, if you started two SLIP connections (0 and 1), you would see the following lines in the network interface table: </div><br><dl class="margin"><dd><pre class="Code3"><b><a name="86338">Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ni0 1006 192 192.168.2.0 0 0 0 0 0 ni1 1006 192 192.168.2.1 0 0 0 0 0</a></b></pre></dl></dl></dl></dl><dl class="margin"><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="86339">Installing ULIP on a Windows NT Host</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="84930"> </a>For Windows hosts, the VxSim BSP includes an NDIS driver called the ULIP driver. Follow these steps to add the ULIP driver to your Windows host.</p><dd><p class="Body"><a name="84931"> </a>From the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Start</font></b> menu select <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Settings>Control Panel>Network</font></b>. Click the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Adapters</font></b> tab in the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Network</font></b> window, click the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Add</font></b> button, and click <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Have Disk</font></b> in the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Select Network Adaptor</font></b> window. Enter the path to the installation file, for example, <b class="file">C:\Tornado\host\x86-win32\bin</b> and click OK. Click on <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Ulip Virtual Adapter</font></b> and click OK (see <a href="x-vxsim5.html#84938">Figure H-1</a>). ULIP is added to the Network Adapters list.<div class="frame"><h4 class="EntityTitle"><a name="84938"><font face="Helvetica, sans-serif" size="-1" class="sans">Figure H-1: Installing the Ulip Virtual Adapter</font></a></h4>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -