frametheory1.htm

BOSON NETSIM是目前最好的路由器模拟软件

    <td width="295" valign="top" style="width:221.4pt;border-top:none;border-left:
  none;border-bottom:solid windowtext .5pt;border-right:solid windowtext .5pt;
  mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt;
  padding:0in 5.4pt 0in 5.4pt">
      <p class="MsoNormal">Number of expected inquiries which define a window
      for alarm declaration<o:p>
      </o:p>
      </p>
    </td>
  </tr>
</table>
<p>&nbsp;</p>
<p>&nbsp;</p>
<table border="0" cellSpacing="0" width="100%">
  <tbody>
    <tr vAlign="center">
      <th align="left"><font size="4" color="#008000">IOS Router Frame Relay Command Glossary</font></th>
    </tr>
  </tbody>
</table><hr><table bgColor="#d7d7d7" border="2" cellSpacing="0" width="100%">
  <tbody>
    <tr align="left" vAlign="top">
      <th>&nbsp;</th>
    </tr>
  </tbody>
</table>
<a name="description"></a>
<hr><table border="0" cellSpacing="0" width="100%">
  <tbody>
    <tr align="left" vAlign="top">
      <td><b>description</b><i> descriptive-string</i></td>
      <th align="right" width="230"></th>
    </tr>
  </tbody>
</table>
<blockquote>
  <p>A description can be added to an interface to help keep track of PVCs (e.g.
  Frame Relay to Boston) </p>
</blockquote>
<a name="enable secret"></a>
<hr><table border="0" cellSpacing="0" width="100%">
  <tbody>
  </tbody>
</table>
<a name="encapsulation frame-relay"></a>
<hr><table border="0" cellSpacing="0" width="100%">
  <tbody>
    <tr align="left" vAlign="top">
      <td><b>encapsulation frame-relay [</b>cisco | ietf<b>]</b></td>
      <th align="right" width="230"></th>
    </tr>
  </tbody>
</table>
<blockquote>
  <p>This command specifies frame relay encapsulation.</p>
  <p><i><b><font size="2">Note: IETF frame-relay encapsulation is necessary when
  connecting to non-Cisco routers. The router defaults to Cisco frame-relay
  encapsulation if IETF is not specified. To configure IETF frame-relay
  encapsulation, use the &quot;encapsulation frame-relay IETF&quot; form of this
  command. Encapsulation types must match on both routers.</font></b></i></p>
</blockquote>
<a name="frame-relay interface-dlci"></a>
<hr><table border="0" cellSpacing="0" width="100%">
  <tbody>
    <tr align="left" vAlign="top">
      <td><b>frame-relay interface-dlci </b><i>dlci</i> <b>[</b>broadcast<b>]</b></td>
      <th align="right" width="230"></th>
    </tr>
  </tbody>
</table>
<blockquote>
  <p>This command assigns a Data Link Connection Identifier (DLCI) number to the
  corresponding frame-relay subinterface. A DLCI is assigned by the local frame
  relay provider for every Permanent Virtual Circuit (PVC) connected to the
  router. DLCI numbers are NOT exchanged between routers. DLCI numbering at one
  frame relay site is mutually exclusive from DLCI numbering at another site.
  This concept is illustrated in the examples. DLCI numbers for Atlanta (16 and
  17) need not match DLCI numbers for Boston (16) and Chicago (16). By the same
  token, it is OK for Boston and Chicago to both use DLCI 16.</p>
  <p>The broadcast keyword is optional and should only be included if broadcast
  packets (e.g. IP RIP or IPX RIP/SAP updates) need to be forwarded out of the
  subinterface. In static routing examples, routing updates are not required and
  the keyword is omitted.</p>
  <p><i><b><font size="2">Note: In IOS versions later than 11.1(5), all
  point-to-point subinterfaces will forward broadcast packets by default and the
  option cannot be disabled. In static routing examples, even though broadcast
  traffic is enabled, operation is not affected as other precautions are taken
  to prevent the forwarding of broadcast traffic out of the subinterface (e.g.
  routing protocols are disabled for the subinterface).</font></b></i></p>
</blockquote>
<a name="frame-relay lmi-type"></a>
<hr><table border="0" cellSpacing="0" width="100%">
  <tbody>
    <tr align="left" vAlign="top">
      <td><b>frame-relay lmi-type {</b>ansi | cisco | q933a<b>}</b></td>
      <th align="right" width="230"></th>
    </tr>
  </tbody>
</table>
<blockquote>
  <p>This command configures the router with which frame-relay Local Management
  Interface (LMI) type to expect from the Frame Relay provider. LMI is a frame
  relay control protocol sent to the router from the frame relay switch at the
  service provider and is not exchanged between routers. The LMI type at one
  location does NOT have to match the LMI type at other locations. To illustrate
  this point, the examples have Boston (Cisco LMI) using a different LMI type
  than Atlanta (ANSI Annex D LMI).</p>
  <table bgColor="#d7d7d7" border="1" cellSpacing="0">
    <tbody>
    </font><caption><b>Supported LMI Types</b></caption>
    <tbody>
      <tr>
        <th>cisco</th>
        <th>Generic &quot;gang of four&quot; LMI (default)</th>
      </tr>
      <tr align="left" vAlign="top">
        <th>ansi</th>
        <th>ANSI Annex D</th>
      </tr>
      <tr align="left" vAlign="top">
        <th>q933a</th>
        <th>CCITT Q933a</th>
      </tr>
    </tbody>
  </table>
  <p><i><b><font size="2">Note: When the LMI type is set for &quot;cisco&quot;,
  the command will not appear in the configuration since this is the default
  value.</font></b></i></p>
</blockquote>
<a name="frame-relay map"></a>
<hr><table border="0" cellSpacing="0" width="100%">
  <tbody>
    <tr align="left" vAlign="top">
      <td><font face="Arial"><b>frame-relay map ip </b><i>ip-address dlci </i><b>[</b>broadcast<b>]</b></font></td>
      <th align="right" width="230"></th>
    </tr>
  </tbody>
</table>
<blockquote>
  <p><font face="Arial">This command is used in multipoint frame-relay examples and defines a
  static mapping between a protocol address and a frame-relay Data Link
  Connection Identifier (DLCI). A DLCI is assigned by the local frame relay
  provider for every Permanent Virtual Circuit (PVC) connected to the router.
  DLCI numbers are NOT exchanged between routers. DLCI numbering at one frame
  relay site is mutually exclusive from DLCI numbering at another site. This
  concept is illustrated in the examples. DLCI numbers for Atlanta (16 and 17)
  need not match DLCI numbers for Boston (16) and Chicago (16). By the same
  token, it is OK for Boston and Chicago to both use DLCI 16.</font></p>
  <p><font face="Arial">The broadcast keyword is optional and should only be included if broadcast
  packets (e.g. IP RIP or IPX RIP/SAP updates) need to be forwarded out of the
  subinterface. In static routing examples, routing updates are not required and
  the keyword is omitted.</font></p>
  <p><font face="Arial">In multipoint frame-relay examples, Atlanta uses DLCI 16 to reach Boston
  (IP address 172.16.1.2). Therefore, Atlanta defines a static frame relay map
  with the command &quot;frame-relay map IP 172.16.1.2 16&quot;. Also, Boston
  contains static frame-relay maps to use DLCI 16 for both Atlanta and Chicago
  because traffic destined to Chicago must first be sent over the PVC to
  Atlanta. Atlanta will then redirect the packet out its PVC to Chicago.</font></p>
</blockquote>
<a name="hostname"></a>
<hr><table border="0" cellSpacing="0" width="100%">
  <tbody>
  </tbody>
</table>
<a name="interface Serial0.16"></a>
<hr><table border="0" cellSpacing="0" width="100%">
  <tbody>
    <tr align="left" vAlign="top">
      <td><font face="Arial"><b>interface Serial0.</b><i>subinterface#</i> <b>[</b>point-to-point |
        multipoint<b>]</b></font></td>
      <th align="right" width="230"></th>
    </tr>
  </tbody>
</table>
<blockquote>
  <p><font face="Arial">This command creates a logical frame-relay subinterface and defines it as a
  point-to-point or multipoint connection. A subinterface is treated as if it
  where a separate interface dedicated for a PVC to a remote site.
  &quot;Serial0&quot; indicates that the subinterface belongs to the physical
  serial0 interface and &quot;16&quot; is the unique subinterface ID number. The
  subinterface ID number can be any unique value between zero and 4,294,967,295
  and does not have to be in any particular order (i.e. it is not necessary to
  begin with 1 and sequentially progress with 2,3,卐tc.). In fact, to reduce
  confusion, it is good practice to identify a subinterface with the same number
  as the DLCI used on that subinterface.</font></p>
</blockquote>
<hr><table border="0" cellSpacing="0" width="100%">
  <tbody>
    <tr align="left" vAlign="top">
      <td><font face="Arial"><b>ip address </b><i>ip-address subnet-mask</i></font></td>
      <th align="right" width="230"></th>
    </tr>
  </tbody>
</table>
<blockquote>
  <p><font face="Arial">This command configures an interface with an IP address and subnet mask. In
  IP routing examples, 10.1.1.1 is the IP address of the Ethernet interface in
  Atlanta and 255.0.0.0 is the corresponding subnet mask. For examples in which
  IP is bridged, all interfaces on the router are configured with the same IP
  address because the router is reduced to a simple node on an IP network with
  only one IP address.</font></p>
</blockquote>
<p>&nbsp;</p>
</font>

<p><font face="Arial" size="2"><span class="724482219-24092001">Copyright (c) 
1998-2003 Boson Software, Inc.&nbsp; All Rights Reserved.</span></font></p>

</body>

</html>