<div>The DHCP, RTCP, TFTP traffic can all be lumped into the Day2Day class, as that 8 Megs should be reserved.</div>
<div>That is traffic that is NOT part of the 10.31.0.0 subnet. The remaining 89 Megs will then carry DR traffic only.</div>
<div> </div>
<div>Does that make sense?</div>
<div> </div>
<div>Kevin</div>
<div> </div>
<div><br><br> </div>
<div class="gmail_quote">On Mon, Oct 12, 2009 at 9:51 AM, Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div>
<div style="FONT-FAMILY: Verdana; COLOR: #000000; FONT-SIZE: 10pt">I don't know your network, and my network hat has some dust on it, but according to your match statements, it looks like you're matching actual voice traffic only. Do the phones not also have traffic that is not marked as voice traffic such as DHCP, TFTP, signalling, etc? Isn't that reguarl IP traffic?<br>
<br>Also, how many phones at the remote site? We have a remote site with a hundred meg link as well, and we asked to get the maximum number of calls reserved. We're not even close to utilization, but I imagine, if we were, we would go with a mechanism like yours where it's reserved but shared.<br>
<br>Just some thoughts.<br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
"Bad grammar makes me [sic]" - Tshirt
<div>
<div></div>
<div class="h5"><br><br><br>----- Original Message -----<br>From: "Kevin Dunn" <<a href="mailto:cheesevoice@gmail.com" target="_blank">cheesevoice@gmail.com</a>><br>To: "Cisco Voice" <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>><br>
Sent: Monday, October 12, 2009 10:41:19 AM GMT -05:00 US/Canada Eastern<br>Subject: [cisco-voip] QoS for Day to Day traffic<br><br>
<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 color="#145040" size="6" face="Monotype Corsiva"><strong>Kevin Dunn</strong></font></div>
<div align="left"><strong><font color="#145040" size="6" face="Monotype Corsiva">Marathon Cheese Corporation</font></strong></div>
<div> </div></div></div><br><br></div></div>_______________________________________________ cisco-voip mailing list <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a> </div>
</div></blockquote></div><br>