[cisco-voip] QoS for Day to Day traffic
Brantley Richbourg
Brantley.Richbourg at MMICNC.COM
Mon Oct 12 13:40:35 EDT 2009
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.
If you want to make sure DR traffic always stays at 89%, etc, etc,. I
would modify your policy-map to the following:
policy-map DRandVoice
class voice
priority percent 3
class day2day
bandwidth percent 8
police rate percent 8
conform-action transmit
exceed-action drop
violate-action drop
class class-default
police rate percent 89
conform-action transmit
exceed-action drop
violate-action drop
priority queueing will automatically police at 3%.
________________________________
From: Kevin Dunn [mailto:cheesevoice at gmail.com]
Sent: Monday, October 12, 2009 12:15 PM
To: Brantley Richbourg
Cc: Cisco Voice
Subject: Re: [cisco-voip] QoS for Day to Day traffic
AHHHHHHH (light bulb moment)
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.
and THAT is why I ask, because sometimes, you just don't think the way
everyone else does.
Thank you all very much.
Kevin
On Mon, Oct 12, 2009 at 11:05 AM, Brantley Richbourg
<Brantley.Richbourg at mmicnc.com> wrote:
Hello,
I have some thoughts on your policy-map.
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
remaining 97Mbps (84.39Mbps), and finally you have day2day traffic can
have 8% of the remaining 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 not been allocated to other classes. I
would do this:
policy-map DRandVoice
class voice
priority percent 3
class day2day
bandwidth percent 8
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).
More information here:
http://www.cisco.com/en/US/tech/tk543/tk757/technologies_tech_note09186a
0080103eae.shtml#summaryofdifferences
Thanks,
Brantley
Brantley Richbourg, MCSE, CCNAS, VCP
Network Engineer
Medical Mutual Insurance Company of North Carolina
919.878.7564
919.878.7550 (F)
Brantley.Richbourg at mmicnc.com
www.medicalmutualgroup.com <http://www.medicalmutualgroup.com/>
________________________________
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Kevin Dunn
Sent: Monday, October 12, 2009 10:41 AM
To: Cisco Voice
Subject: [cisco-voip] QoS for Day to Day traffic
Hello my Pundits
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%....
1. Do you think this will work?
2. Do you think it is set up right?
class-map match-any voice
match dscp ef
match protocol rtp audio
class-map match-any DR
match access-group 100
class-map match-any day2day
match access-group 101
policy-map DRandVoice
class voice
priority percent 3
class DR
bandwidth remaining percent 89
class day2day
bandwidth remaining percent 8
access-list 100 permit ip 10.31.0.0 0.0.255.255
access-list 101 deny ip 10.31.0.0 0.0.255.255
access-list 101 permit ip any any
Kevin Dunn
Marathon Cheese Corporation
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.
</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>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091012/a51d5b4d/attachment.html>
More information about the cisco-voip
mailing list