<?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>Tom&#039;s Notes &#187; svc</title>
	<atom:link href="http://wp.greenwood.net.nz/tag/svc/feed/" rel="self" type="application/rss+xml" />
	<link>http://wp.greenwood.net.nz</link>
	<description>CCNA4 Notes - Term 2, 2009</description>
	<lastBuildDate>Thu, 02 Jul 2009 21:43:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Module 5 &#8211; Frame Relay</title>
		<link>http://wp.greenwood.net.nz/module-5-frame-relay/</link>
		<comments>http://wp.greenwood.net.nz/module-5-frame-relay/#comments</comments>
		<pubDate>Wed, 17 Jun 2009 21:00:08 +0000</pubDate>
		<dc:creator>Tom GT</dc:creator>
				<category><![CDATA[Cisco CCNA4]]></category>
		<category><![CDATA[frame relay]]></category>
		<category><![CDATA[pvc]]></category>
		<category><![CDATA[svc]]></category>

		<guid isPermaLink="false">http://wp.greenwood.net.nz/?p=120</guid>
		<description><![CDATA[Index

Frame Relay Concepts

General Concepts
Bandwidth and Flow
Address Mapping and Topology
LMI


Frame Relay Configuration

Basic Configuration
Static Map
Subinterfaces




Frame Relay Concepts
General Concepts

Customer end is the DTE
Frame Relay switch is the DCE
The connection between two DTEs is called a Virtual Circuit (VC)
Dynamic VCs are known as Switched VCs (SVCs)
Static VCs are known as Permanent VCs (PVCs), which are the most common.
Frame Relay [...]]]></description>
			<content:encoded><![CDATA[<h3>Index</h3>
<ul>
<li><a href="http://wp.greenwood.net.nz/module-5-frame-relay/#concepts">Frame Relay Concepts</a>
<ul>
<li><a href="http://wp.greenwood.net.nz/module-5-frame-relay/#general-concepts">General Concepts</a></li>
<li><a href="http://wp.greenwood.net.nz/module-5-frame-relay/#bandwidth">Bandwidth and Flow</a></li>
<li><a href="http://wp.greenwood.net.nz/module-5-frame-relay/#address-mapping">Address Mapping and Topology</a></li>
<li><a href="http://wp.greenwood.net.nz/module-5-frame-relay/#LMI">LMI</a></li>
</ul>
</li>
<li><a href="http://wp.greenwood.net.nz/module-5-frame-relay/#config">Frame Relay Configuration</a>
<ul>
<li><a href="http://wp.greenwood.net.nz/module-5-frame-relay/#basic-config">Basic Configuration</a></li>
<li><a href="http://wp.greenwood.net.nz/module-5-frame-relay/#static">Static Map</a></li>
<li><a href="http://wp.greenwood.net.nz/module-5-frame-relay/#subinterface">Subinterfaces</a></li>
</ul>
</li>
</ul>
<h3><span id="more-120"></span></h3>
<h3><a style="text-decoration: none; color: #555555;" name="concepts">Frame Relay Concepts</a></h3>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="general-concepts">General Concepts</a></strong></span></p>
<ul>
<li>Customer end is the DTE</li>
<li>Frame Relay switch is the DCE</li>
<li>The connection between two DTEs is called a Virtual Circuit (VC)</li>
<li>Dynamic VCs are known as Switched VCs (SVCs)</li>
<li>Static VCs are known as Permanent VCs (PVCs), which are the most common.</li>
<li>Frame Relay has no error recovery, corrupt frames are discarded without notification. It is up to the upper layers to detect missing frames and request retransmission</li>
<li>Several VCs can operate on one physical link</li>
<li>DLCIs are used locally to identify where a packet is going, and is put in the address field of an outgoing frame.</li>
</ul>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="bandwidth">Bandwidth and flow</a></strong></span></p>
<ul>
<li>Typical port speed is 64kbps to 4Mbps, though some providers offer up to 45Mbps</li>
<li>Each VC has a Commited Information Rate (CIR), which is the guaranteed bandwidth.</li>
<li>As it is unlikely for all VCs to need to transmit at the same time, lines are commonly over-allocated by up to 2-3x the CIR</li>
<li>Packets that are being sent over the CIR are marked as Discard Eligible, and will be discarded should a link become congested.</li>
<li>The difference between the port speed and the CIR is the Excess Information Rate (EIR)</li>
<li>The load average is worked out by dividing the data transferred by the committed time (Tc)</li>
<li>Idle time can not be saved up for use at a later time of load</li>
<li>The FECN bits are set on all frames downstream of a congested link</li>
<li>The BECN bits are set on all frames upstream of a congested link</li>
<li>When a DTE receives a frame with ECN bits set, it is expected to reduce the amount of traffic it creates</li>
</ul>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="address-mapping">Address Mapping and Topology<br />
</a></strong></span></p>
<ul>
<li>DLCIs are mapped to the IP address of the remote router, either with RARP or statically</li>
<li>Frame Relay can be used in a full or partial mesh topology, point to point links are possible, but are usually not cost effective</li>
<li>There can only be &lt;100 VCs per physical interface, so full mesh topologies are not usually cost effective for larger networks</li>
</ul>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="LMI">LMI</a></strong></span></p>
<ul>
<li>Link Management Interface (LMI) is used on Frame Relay to provide status updates</li>
<li>Some DLCIs are reserved for use by LMI</li>
<li>There are three types of LMI supported by Cisco routers:
<ul>
<li>Cisco &#8211; original LMI extensions</li>
<li>ANSI &#8211; ANSI standard T1.617 Annex D</li>
<li>Q933a &#8211; ITU standard Q933 Annex A</li>
</ul>
</li>
</ul>
<h3><a style="text-decoration: none; color: #555555;" name="config">Frame Relay Configuration</a></h3>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="basic-config">Basic Configuration</a></strong></span></p>
<p><em>Router(config)# <strong>interface [interface]</strong></em><br />
<em>Router(config-if)# <strong>ip address [address] [mask]</strong></em><br />
<em>Router(config-if)# <strong>encapsulation frame-relay [cisco | ietf]</strong></em></p>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="static">Static Map</a></strong></span></p>
<p><em>Router(config)# <strong>frame-relay map [protocol] [address] [dlci] ['broadcast']</strong></em></p>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="subinterface">Subinterfaces</a></strong></span></p>
<p><em>Router(config) <strong>interface [interface].[sub-if no.] [point-to-point | multipoint]</strong></em><br />
<em>Router(config-if) <strong>ip address [address] [mask]</strong></em><br />
<em>Router(config-if) <strong>frame-relay interface-dlci [dlci]</strong></em></p>
]]></content:encoded>
			<wfw:commentRss>http://wp.greenwood.net.nz/module-5-frame-relay/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
