<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16890" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=611222917-12102009><FONT face="Trebuchet MS"
color=#000080 size=2>Another thought too is do you want to make sure your
day2day traffic does not impact your default class (meaning your DR
traffic)? If yes, I would add police statements to
your policy-map to keep traffic at 8Mbps, 89Mbps, etc. CBWFQ
will only really kick in when there is congestion on your interface. So
your day-to-day traffic could kick it up to 100Mbps if there is no traffic for
the other classes at that time. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=611222917-12102009><FONT face="Trebuchet MS"
color=#000080 size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=611222917-12102009><FONT face="Trebuchet MS"
color=#000080 size=2>If you want to make sure DR traffic always stays at 89%,
etc, etc,. I would modify your policy-map to the
following:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=611222917-12102009><FONT face="Trebuchet MS"
color=#000080 size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=611222917-12102009><FONT face="Trebuchet MS"
color=#000080 size=2> </FONT></DIV>
<DIV class=im dir=ltr align=left><FONT size=2><FONT color=#000080><FONT
face="Trebuchet MS"><STRONG>policy-map
DRandVoice</STRONG><BR> <STRONG>class voice</STRONG><BR> priority
percent <SPAN class=611222917-12102009>3</SPAN></FONT></FONT></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#000080
size=2> <STRONG>class day2day<BR></STRONG> bandwidth percent
8</FONT></DIV>
<DIV dir=ltr align=left></SPAN><SPAN class=611222917-12102009><FONT
face="Trebuchet MS" color=#000080 size=2> police rate percent
8</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN
class=611222917-12102009> <FONT face="Trebuchet MS"
color=#000080><FONT size=2>conform-action transmit<BR>
exceed-action drop<BR> violate-action
drop</FONT></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=611222917-12102009><FONT face="Trebuchet MS"
color=#000080><FONT size=2> <STRONG>class
class-default</STRONG></FONT></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=611222917-12102009><FONT face="Trebuchet MS"
color=#000080> <FONT size=2>police rate percent 89</FONT>
<DIV dir=ltr align=left><SPAN
class=611222917-12102009> <FONT size=2>
</FONT><FONT face="Trebuchet MS" color=#000080><FONT size=2>conform-action
transmit<BR> exceed-action
drop<BR> violate-action
drop</FONT></FONT></SPAN></DIV><BR><FONT size=2>priority queueing will
automatically police at 3%.</FONT></DIV></FONT></SPAN><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Kevin Dunn [mailto:cheesevoice@gmail.com]
<BR><B>Sent:</B> Monday, October 12, 2009 12:15 PM<BR><B>To:</B> Brantley
Richbourg<BR><B>Cc:</B> Cisco Voice<BR><B>Subject:</B> Re: [cisco-voip] QoS for
Day to Day traffic<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>AHHHHHHH (light bulb moment)</DIV>
<DIV> </DIV>
<DIV>by matching ACL 101 I am putting everything BUT 10.31.0.0 traffic in the
day2day class, and then everythign else would be in default class... very
awesome.</DIV>
<DIV> </DIV>
<DIV>and THAT is why I ask, because sometimes, you just don't think the way
everyone else does.</DIV>
<DIV> </DIV>
<DIV>Thank you all very much.</DIV>
<DIV> </DIV>
<DIV>Kevin<BR><BR></DIV>
<DIV class=gmail_quote>On Mon, Oct 12, 2009 at 11:05 AM, Brantley Richbourg
<SPAN dir=ltr><<A
href="mailto:Brantley.Richbourg@mmicnc.com">Brantley.Richbourg@mmicnc.com</A>></SPAN>
wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#000080
size=2><SPAN>Hello,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#000080
size=2><SPAN></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#000080 size=2><SPAN>I
have some thoughts on your policy-map.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#000080
size=2><SPAN></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#000080
size=2><SPAN>You are not going to get 8 Mbps on your day2day class.
First off, you give 3% priority to voice, which leaves 97Mbps remaining.
The next class in your policy-map (DR) is saying to use 89% of the
<EM>remaining</EM> 97Mbps (84.39Mbps), and finally you have day2day traffic
can have 8% of the <EM>remaining</EM> BW. So your DR replication I
assume will be using a good bit of bandwidth all day long, so you are only
going to get 157Kbps for DR traffic (if DR and Voice are using 100% of what
they can get), because the "remaining" keyword tells the IOS to allocate that
percentage of bandwidth that has <EM>not</EM> been allocated to other
classes. I would do this:</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#000080
size=2><SPAN></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS"><SPAN>
<DIV><FONT face=Arial color=#000080 size=2>
<DIV class=im>policy-map DRandVoice<BR> class voice<BR> priority
percent 3<BR></DIV> class day2day<BR> bandwidth percent
8</FONT></DIV>
<DIV><FONT face=Arial color=#000080 size=2></FONT> </DIV>
<DIV><SPAN><FONT color=#000080 size=2>Your DR traffic will hit the
"class-default" will be get the rest of the pipe if both classes are being
matched on. That will give you 89% for DR, 8% for day2day and 3% for
voice (LLQ).</FONT></SPAN></DIV>
<DIV><SPAN><FONT color=#000080 size=2></FONT></SPAN> </DIV>
<DIV><SPAN><FONT color=#000080 size=2>More information here: <A
href="http://www.cisco.com/en/US/tech/tk543/tk757/technologies_tech_note09186a0080103eae.shtml#summaryofdifferences"
target=_blank>http://www.cisco.com/en/US/tech/tk543/tk757/technologies_tech_note09186a0080103eae.shtml#summaryofdifferences</A></FONT></SPAN></DIV>
<DIV><SPAN><FONT color=#000080 size=2></FONT></SPAN> </DIV>
<DIV><SPAN><FONT color=#000080 size=2>Thanks,</FONT></SPAN></DIV>
<DIV><SPAN><FONT color=#000080 size=2></FONT></SPAN> </DIV>
<DIV><SPAN><FONT color=#000080 size=2>Brantley</FONT></SPAN></DIV>
<DIV><SPAN><FONT color=#000080 size=2></FONT></SPAN> </DIV>
<DIV><SPAN>
<DIV align=left>
<DIV dir=ltr>
<DIV align=left><FONT face=Calibri color=#1e66b7 size=2><STRONG>Brantley
Richbourg, MCSE, CCNAS, VCP</STRONG></FONT></DIV>
<DIV align=left><FONT face=Calibri color=#1e66b7 size=2>Network
Engineer</FONT></DIV>
<DIV><FONT face=Calibri color=#1e66b7 size=2>Medical Mutual Insurance Company
of North Carolina</FONT></DIV>
<DIV><FONT face=Calibri color=#1e66b7 size=2>919.878.7564 </FONT></DIV>
<DIV><FONT face=Calibri color=#1e66b7 size=2>919.878.7550 (F)</FONT></DIV>
<DIV><FONT face=Calibri color=#1e66b7 size=2><A
href="mailto:Brantley.Richbourg@mmicnc.com"
target=_blank>Brantley.Richbourg@mmicnc.com</A></FONT></DIV>
<DIV><FONT face=Calibri color=#1e66b7 size=2><A
href="http://www.medicalmutualgroup.com/"
target=_blank>www.medicalmutualgroup.com</A></FONT></DIV></DIV></DIV></SPAN></DIV></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#000080
size=2><SPAN> </SPAN></FONT></DIV><BR>
<DIV lang=en-us dir=ltr align=left>
<HR>
<FONT face=Tahoma size=2><B>From:</B> <A
href="mailto:cisco-voip-bounces@puck.nether.net"
target=_blank>cisco-voip-bounces@puck.nether.net</A> [mailto:<A
href="mailto:cisco-voip-bounces@puck.nether.net"
target=_blank>cisco-voip-bounces@puck.nether.net</A>] <B>On Behalf Of
</B>Kevin Dunn<BR><B>Sent:</B> Monday, October 12, 2009 10:41 AM<BR><B>To:</B>
Cisco Voice
<DIV class=im><BR><B>Subject:</B> [cisco-voip] QoS for Day to Day
traffic<BR></DIV></FONT><BR></DIV>
<DIV>
<DIV></DIV>
<DIV class=h5>
<DIV></DIV>
<DIV class=gmail_quote>
<DIV>
<DIV>Hello my Pundits</DIV>
<DIV><SPAN><FONT face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN><FONT face=Arial>I have a 100Meg Ethernet WAN connection between
two towns for DR purposes, and we are going to run "day to day" traffic (voice
and data) over this circuit as well, now when replication and SAN to SAN
traffic hits I don't want it to mess with the "day to day"
traffic. The DR traffic will either source or destination to
10.31.0.0. So I made a couple of ACL's to match that IP to. The
end result is I want to voice traffic to have priority and 3Megs of bandwidth,
Day to Day traffic around 8 Megs of traffic and DR (San to San) the remaining
89%.... </FONT></SPAN></DIV>
<DIV><SPAN><FONT face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN><FONT face=Arial>1. Do you think this will
work?</FONT></SPAN></DIV>
<DIV><SPAN><FONT face=Arial>2. Do you think it is set up
right?</FONT></SPAN></DIV>
<DIV><SPAN><FONT face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN><FONT face=Arial></FONT></SPAN> </DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>class-map match-any voice<BR> match dscp ef
<BR> match protocol rtp audio <BR>class-map match-any DR<BR> match
access-group 100<BR>class-map match-any day2day<BR> match access-group
101</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial>policy-map DRandVoice<BR> class voice<BR>
priority percent 3<BR> class DR<BR> bandwidth remaining percent
89<BR> class day2day<BR> bandwidth remaining percent 8</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial>access-list 100 permit ip 10.31.0.0
0.0.255.255<BR>access-list 101 deny ip 10.31.0.0 0.0.255.255<BR>access-list
101 permit ip any any<BR></FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV align=left><FONT face="Monotype Corsiva" color=#145040
size=6><STRONG>Kevin Dunn</STRONG></FONT></DIV>
<DIV align=left><STRONG><FONT face="Monotype Corsiva" color=#145040
size=6>Marathon Cheese Corporation</FONT></STRONG></DIV>
<DIV> </DIV></DIV></DIV><BR></DIV></DIV></DIV><PRE></PRE>
<P>Confidentiality: The information in this electronic mail may contain
confidential, sensitive and/or protected health information intended only for
the addressee(s). Any other person, including anyone who believes he/she might
have received it due to an addressing error, is requested to notify this
sender immediately by return e-mail, and shall delete it without further
reading and retention. The information shall not be forwarded or shared unless
in compliance with MMIC policies on confidentiality, and/or the written
permission of this sender. </P></BLOCKQUOTE></DIV><BR></BODY></HTML>
<pre></PRE><P>Confidentiality: The information in this electronic mail may contain confidential, sensitive and/or protected health information intended only for the addressee(s). Any other person, including anyone who believes he/she might have received it due to an addressing error, is requested to notify this sender immediately by return e-mail, and shall delete it without further reading and retention. The information shall not be forwarded or shared unless in compliance with MMIC policies on confidentiality, and/or the written permission of this sender.
</P>