<?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>Henry&#039;s Points &#187; QOS</title>
	<atom:link href="http://henrydu.com/blog/category/networks/qos/feed" rel="self" type="application/rss+xml" />
	<link>http://henrydu.com/blog</link>
	<description>Think analog, act digital</description>
	<lastBuildDate>Mon, 14 Nov 2011 18:32:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Three Ways to Implement Traffic Shapping</title>
		<link>http://henrydu.com/blog/networks/three-ways-to-implement-traffic-shapping-251.html</link>
		<comments>http://henrydu.com/blog/networks/three-ways-to-implement-traffic-shapping-251.html#comments</comments>
		<pubDate>Tue, 14 Jul 2009 20:41:54 +0000</pubDate>
		<dc:creator>hengdu</dc:creator>
				<category><![CDATA[Networks]]></category>
		<category><![CDATA[QOS]]></category>

		<guid isPermaLink="false">http://henrydu.com/blog/?p=251</guid>
		<description><![CDATA[There are three ways to implement traffic shaping. Generic Traffic Shapping (GTS) Frame Relay Traffic Shapping (FRTS) Class-based Traffic Shapping (MQC-S) Generic Traffic Shaping (GTS) was the first feature to limit the outbound traffic rate of an interface introduced into IOS. With GTS all traffic leaving an interface/subinterface can be shaped, or a subset of [...]]]></description>
			<content:encoded><![CDATA[<p>There are three ways to implement traffic shaping.</p>
<ul>
<li>Generic Traffic Shapping (GTS)</li>
<li>Frame Relay Traffic Shapping (FRTS)</li>
<li>Class-based Traffic Shapping (MQC-S)</li>
</ul>
<p><strong>Generic Traffic Shaping (GTS)</strong> was the first feature to limit the outbound traffic rate of an interface introduced into IOS. With GTS all traffic leaving an interface/subinterface can be shaped, or a subset of traffic can be classified using an access-list. The syntax is as follows.</p>
<p><strong>traffic-shape rate &lt;CIR&gt; &lt;Bc&gt; &lt;Be&gt; &lt;QueueLimit&gt;<br />
traffic-shape group &lt;ACL&gt; &lt;CIR&gt; &lt;Bc&gt; &lt;Be&gt; &lt;QueueLimit&gt;</strong></p>
<blockquote><p>access-list 101 permit tcp any any eq www<br />
!<br />
interface fa0/0<br />
traffic-shap group 101 10000000</p></blockquote>
<p><strong>FRTS</strong> supports four types of adaptive shaping, 1) BECN adapt, 2) FECN reflection, 3) queue depth monitoring, and 4) a proprietary method called ForeSight.</p>
<blockquote><p>map-class frame-relay TO-&gt;R1<br />
frame-relay cir 512000<br />
frame-relay mincir 256000<br />
frame-relay bc 5120<br />
frame-relay be 0<br />
frame-relay adaptive-shaping becn<br />
frame-relay adaptive-shaping interface-congestion 10<br />
!</p>
<p>interface s0/0<br />
frame-relay traffic-shapping       //Switch on FRTS<br />
frame-relay class TO-&gt;R1</p></blockquote>
<p><strong>MQC based traffic-shaping</strong> allows Generic Traffic Shaping to be applied to any traffic class. This makes traffic-shaping’s configuration modular and unified, without special variants for encapsulations like Frame Relay. Class-based GTS is similar to legacy GTS, but allows shaping based on class-maps, as opposed to access-list classification with legacy GTS, thus allowing any MQC classification options, such as NBAR, to define shaped traffic. Additionally MQC based shaping allows the shaping queue to be tuned, while legacy GTS supports just simple WFQ with no option to tune it.</p>
<blockquote><p>policy-map SHAPE<br />
class class-default<br />
shape average 384000 7680<br />
!<br />
interface fa0/0<br />
service-policy output SHAPE</p></blockquote>
<p class="facebook"><a href="http://www.facebook.com/share.php?u=http://henrydu.com/blog/networks/three-ways-to-implement-traffic-shapping-251.html" target="_blank" title="Share on Facebook">Share on Facebook</a></p>]]></content:encoded>
			<wfw:commentRss>http://henrydu.com/blog/networks/three-ways-to-implement-traffic-shapping-251.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Two Ways of Frame Relay DE Set</title>
		<link>http://henrydu.com/blog/networks/two-ways-of-frame-relay-de-set-249.html</link>
		<comments>http://henrydu.com/blog/networks/two-ways-of-frame-relay-de-set-249.html#comments</comments>
		<pubDate>Mon, 13 Jul 2009 20:47:20 +0000</pubDate>
		<dc:creator>hengdu</dc:creator>
				<category><![CDATA[Networks]]></category>
		<category><![CDATA[QOS]]></category>

		<guid isPermaLink="false">http://henrydu.com/blog/?p=249</guid>
		<description><![CDATA[DE bit set means Eligible for Discarding during periods of traffic congestion of frame relay network. It is congestion avoidance mechanism in FR. Obviously, DE bit set is for out-bound traffic of a router to FR switch. There are three ways to set DE bit. 1. FR DE List Step 1: Classifier traffic by ACL [...]]]></description>
			<content:encoded><![CDATA[<p>DE bit set means Eligible for Discarding during periods of traffic congestion of frame relay network. It is congestion avoidance mechanism in FR. Obviously, DE bit set is for out-bound traffic of a router to FR switch. There are three ways to set DE bit.</p>
<p><em><strong>1. FR DE List</strong></em></p>
<p>Step 1: Classifier traffic by ACL</p>
<p>Step 2: Apply DE List</p>
<p>Step 3: Map DE List to DLCI</p>
<blockquote><p>! Classifier<br />
access-list 101 permit tcp any any eq www<br />
! Mark<br />
<strong>frame-relay de-list 1 protocol ip list 101</strong><br />
! Mapping<br />
interface s0/0<br />
<strong>frame-realy de-group 1 101</strong></p></blockquote>
<p><em><strong>2. MQC</strong></em></p>
<p>Step 1: Define Class-map</p>
<p>Step 2: Define Policy-map</p>
<p>Step 3: Apply to out-bound traffic</p>
<blockquote><p>class-map WWW<br />
match ip address 101<br />
!<br />
policy-map WWW_PO<br />
class WWW<br />
<strong>set fr-de</strong><br />
!<br />
interface s0/0<br />
service-policy output WWW_PO<br />
!<br />
access-list 101 permit tcp any any eq www<br />
!<br />
ip cef</p></blockquote>
<p><strong>3. FRTS</strong></p>
<p>Step 1: Switch on Frame Relay Traffic Shapping on the interface level. Then, DE is set automatically.</p>
<blockquote><p>interface s0/0<br />
frame-relay traffic-shapping</p></blockquote>
<p class="facebook"><a href="http://www.facebook.com/share.php?u=http://henrydu.com/blog/networks/two-ways-of-frame-relay-de-set-249.html" target="_blank" title="Share on Facebook">Share on Facebook</a></p>]]></content:encoded>
			<wfw:commentRss>http://henrydu.com/blog/networks/two-ways-of-frame-relay-de-set-249.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

