<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.lapierre.us/index.php?action=history&amp;feed=atom&amp;title=Frame_Relay</id>
	<title>Frame Relay - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.lapierre.us/index.php?action=history&amp;feed=atom&amp;title=Frame_Relay"/>
	<link rel="alternate" type="text/html" href="https://wiki.lapierre.us/index.php?title=Frame_Relay&amp;action=history"/>
	<updated>2026-11-16T12:26:23Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.33.0</generator>
	<entry>
		<id>https://wiki.lapierre.us/index.php?title=Frame_Relay&amp;diff=53&amp;oldid=prev</id>
		<title>Bill: Created page with &quot;CIR (committed access rate) - Guaranteed bandwidth from the ISP LAR (local access rate) - What your equipment can actually handle LMI - language between your routers and frame...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki.lapierre.us/index.php?title=Frame_Relay&amp;diff=53&amp;oldid=prev"/>
		<updated>2012-12-08T18:29:34Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;CIR (committed access rate) - Guaranteed bandwidth from the ISP LAR (local access rate) - What your equipment can actually handle LMI - language between your routers and frame...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;CIR (committed access rate) - Guaranteed bandwidth from the ISP&lt;br /&gt;
LAR (local access rate) - What your equipment can actually handle&lt;br /&gt;
LMI - language between your routers and frame relay switches&lt;br /&gt;
DLCI - MAC Address is to Ethernet as DLCI is to Frame Relay. Leave on a local DLCI number, travel through the &lt;br /&gt;
cloud, and exit on the other end&amp;#039;s DLCI. Just like at an airport gate. DLCIs are locally significant.&lt;br /&gt;
PVC - a virtual dedicated link through the cloud between locations that has its own CIR&lt;br /&gt;
&lt;br /&gt;
Multipoint design: all routers are on one subnet&lt;br /&gt;
Point-to-Point design: all pairs of routers are on different subnet (no split horizon issues) //broadcast is enabled by default&lt;br /&gt;
In a multipoint design, all routers are on the same subnet, you have to statically map every connection between all of the routers, much like configuring a static route&lt;br /&gt;
There are two frame-relay encapsulation standards: IETF and cisco, make sure both routers are using the same&lt;br /&gt;
Modern routers auto-detect the LMI type. If the data-link layer is down, then there may be a LMI type mismatch.&lt;br /&gt;
#show frame-relay lmi&lt;br /&gt;
&lt;br /&gt;
Frame-relay switch (DCE switch):&lt;br /&gt;
(config)frame-relay switching //makes the device a frame-relay switch&lt;br /&gt;
(config-if)no ip address //frame relay switches operate at layer 2, so they don&amp;#039;t need an IP address&lt;br /&gt;
(config-if)encapsulation frame-relay [MFR | ietf] //enables frame relay on that interface, and optionally specify the encapsulation standard&lt;br /&gt;
(config-if)clockrate &amp;lt;#&amp;gt; //provides clocking signals to the connected Frame Relay routers, which are set up as DTE devices&lt;br /&gt;
(config-if)frame-relay intf-type dce //make it a DCE interface&lt;br /&gt;
(config-if)frame-relay route &amp;lt;incoming DLCI #&amp;gt; interface &amp;lt;outgoing interface&amp;gt; &amp;lt;outgoing DLCI #&amp;gt;&lt;br /&gt;
The frame relay switch does not have DLCIs of its own.&lt;br /&gt;
#show frame-relay route&lt;br /&gt;
&lt;br /&gt;
Communication between two Frame Relay switches:&lt;br /&gt;
Exactly the same as above, except:&lt;br /&gt;
(config-if)frame-relay intf-type nni&lt;br /&gt;
Equal clocks must be set on both ends&lt;br /&gt;
Frame relay switching is also to be configured&lt;br /&gt;
&lt;br /&gt;
DTE switches: by default a router is considered to be a DTE device&lt;br /&gt;
Point-to-Multipoint:&lt;br /&gt;
(config-if)encapsulation frame-relay &lt;br /&gt;
(config-if)frame-relay map ip &amp;lt;remote ip address&amp;gt; &amp;lt;local dlci number to get there&amp;gt; [broadcast] //similar to configuring a static route&lt;br /&gt;
IARP: does the above mapping so you don&amp;#039;t have to (obtain L3 from L2)&lt;br /&gt;
&lt;br /&gt;
Point-to-Point:&lt;br /&gt;
(config-if)encapsulation frame-relay&lt;br /&gt;
(config-subif)frame-relay interface-dlci &amp;lt;#&amp;gt; //no map statement required, because it&amp;#039;s a point-to-point&lt;br /&gt;
Sub-interfaces: a single physical interface but multiple sub-interfaces to represent the multiple PVC’s (Permanent Virtual Circuits)&lt;br /&gt;
Encapsulation and no shut is set on the physical interface, not subinterfaces&lt;br /&gt;
(config)int s0/1/0.102 point-to-point&lt;br /&gt;
(config-subif)frame-relay interface-dlci &amp;lt;#&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#show frame-relay map&lt;br /&gt;
#show frame-relay pvc //more detailed version of map&lt;/div&gt;</summary>
		<author><name>Bill</name></author>
		
	</entry>
</feed>