From: Michael Snyder (msnyder@revolutioncomputer.com)
Date: Sun Nov 16 2003 - 17:33:30 GMT-3
Well, on page 194 of Cisco Press DQOS book,
Quote "You can also use car just to mark the traffic"
Which made me think, rather than using cpu intensive car, could I use a
route-map?
The answer seems to be yes.
I'm not positive of my bit math, but the following table seems correct.
af11 assured forwarding (af11) bit pattern 001 010 = P1 T4
af12 assured forwarding (af12) bit pattern 001 100 = P1 T8
af13 assured forwarding (af13) bit pattern 001 110 = P1 T12
af21 assured forwarding (af21) bit pattern 010 010 = P2 T4
af22 assured forwarding (af22) bit pattern 010 100 = P2 T8
af23 assured forwarding (af23) bit pattern 010 110 = P2 T12
af31 assured forwarding (af31) bit pattern 011 010 = P3 T4
af32 assured forwarding (af32) bit pattern 011 100 = P3 T8
af33 assured forwarding (af33) bit pattern 011 110 = P3 T12
af41 assured forwarding (af41) bit pattern 100 010 = P4 T4
af42 assured forwarding (af42) bit pattern 100 100 = P4 T8
af43 assured forwarding (af43) bit pattern 100 110 = P4 T12
cs1 class selector codepoint 1 (precedence 1) 001 = P1 T0
cs2 class selector codepoint 2 (precedence 2) 010 = P2 T0
cs3 class selector codepoint 3 (precedence 3) 011 = P3 T0
cs4 class selector codepoint 4 (precedence 4) 100 = P4 T0
cs5 class selector codepoint 5 (precedence 5) 101 = P5 T0
cs6 class selector codepoint 6 (precedence 6) 110 = P6 T0
cs7 class selector codepoint 7 (precedence 7) 111 = P7 T0
default default bit pattern of 000000
ef expedited forwarding bit pattern 101 110 = P 5 T 12
Where AF(x)(y) = DCSP (8x+2y) = Precedence (x) TOS (4y)
Example
AF13 = DCSP 14 = Precedence 1 TOS 12
Will lab this out to verify my results.
-----Original Message-----
From: Scott Morris [mailto:swm@emanon.com]
Sent: Sunday, November 16, 2003 1:59 PM
To: 'Michael Snyder'; ccielab@groupstudy.com
Subject: RE: routemap to set dcsp
Ok, that would likely to something there, but why not just set ip dscp?
You can't do this in a route-map, but in the policy-map you could do
that.
But otherwise, yet... 101 and 1100 would suffice to set the appropriate
bits.
For others wondering where the heck that all came from, RFC 1349 breaks
things down a little differently for the 8-bit ToS field where the first
three bits are still IP Precedence, then the next four bits are called
tos bits and the last bit is called MBZ (Must Be Zero). Who ever said
engineers didn't have a sense of humor? :)
As for viewing them, not really... Other than setting up an access-list
that permits things with a dscp value of EF and looking at the number of
matches.
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713,
CISSP, JNCIS, et al.
IPExpert CCIE Program Manager
IPExpert Sr. Technical Instructor
swm@emanon.com/smorris@ipexpert.net
http://www.ipexpert.net
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Michael Snyder
Sent: Sunday, November 16, 2003 2:32 PM
To: ccielab@groupstudy.com
Cc: 'Scott Morris'
Subject: RE: routemap to set dcsp
I'm guessing that the following route-map will set all packets to
dcsp(ef).
route-map setdcspef permit 10
set ip precedence critical
set ip tos 12
Any easy way of viewing the dcsp value of incoming packets?
Thinking I'm going to have to use car to detect my route-map changed
packets on another router.
Will try it out this afternoon.
-----Original Message-----
From: Scott Morris [mailto:swm@emanon.com]
Sent: Sunday, November 16, 2003 12:14 PM
To: 'Brian McGahan'; 'Michael Snyder'; ccielab@groupstudy.com
Subject: RE: Does Precedence 5 always equal DCSP CS5?
You have to look back at the details within RFC791 to get a true feeling
for why DSCP 46 is more appropriate for voice traffic. Those other
three bits, while not part of IP Precedence, still had value...
IP Prec 5 by itself translates to DSCP 40, plain and simple.
However:
Type of Service: 8 bits
The Type of Service provides an indication of the abstract
parameters of the quality of service desired. These parameters are
to be used to guide the selection of the actual service parameters
when transmitting a datagram through a particular network. Several
networks offer service precedence, which somehow treats high
precedence traffic as more important than other traffic (generally
by accepting only traffic above a certain precedence at time of high
load). The major choice is a three way tradeoff between low-delay,
high-reliability, and high-throughput.
Bits 0-2: Precedence.
Bit 3: 0 = Normal Delay, 1 = Low Delay.
Bits 4: 0 = Normal Throughput, 1 = High Throughput.
Bits 5: 0 = Normal Relibility, 1 = High Relibility.
Bit 6-7: Reserved for Future Use.
So Voice traffic should not only be classified as IP Prec 5, but also
Low Delay (bit 4 = 1) and High Throughput (bit 5 = 1) giving us the
total package of 101110 or 46 in DSCP terms.
So it really isn't so much that anything is changing other than the
perspective of what bits we are measuring where. The bits should really
still be the same regardless of whether our router is DSCP-capable or
not, but we then have more granularity to play with in order to make
this wonderful pain-in-the-rear technology of voice play nicely on the
networks!
Cheers,
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713,
CISSP, JNCIS, et al. IPExpert CCIE Program Manager IPExpert Sr.
Technical Instructor swm@emanon.com/smorris@ipexpert.net
http://www.ipexpert.net
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Brian McGahan
Sent: Saturday, November 15, 2003 7:52 PM
To: 'Michael Snyder'; ccielab@groupstudy.com
Subject: RE: Does Precedence 5 always equal DCSP CS5?
Michael,
As a side note, setting IP precedence on a local POTS peer is no
longer supported. However you can still set it using the appropriate
DSCP -> IP Prec mappings. Since DSCP implicitly overlaps IP precedence,
DSCP is the preferred way to color traffic.
Router(config-dial-peer)#ip prec?
% Unrecognized command
Router(config-dial-peer)#ip qos dscp ?
<0-63> DSCP value
af11 assured forwarding (af11) bit pattern 001010
af12 assured forwarding (af12) bit pattern 001100
af13 assured forwarding (af13) bit pattern 001110
af21 assured forwarding (af21) bit pattern 010010
af22 assured forwarding (af22) bit pattern 010100
af23 assured forwarding (af23) bit pattern 010110
af31 assured forwarding (af31) bit pattern 011010
af32 assured forwarding (af32) bit pattern 011100
af33 assured forwarding (af33) bit pattern 011110
af41 assured forwarding (af41) bit pattern 100010
af42 assured forwarding (af42) bit pattern 100100
af43 assured forwarding (af43) bit pattern 100110
cs1 class selector codepoint 1 (precedence 1)
cs2 class selector codepoint 2 (precedence 2)
cs3 class selector codepoint 3 (precedence 3)
cs4 class selector codepoint 4 (precedence 4)
cs5 class selector codepoint 5 (precedence 5)
cs6 class selector codepoint 6 (precedence 6)
cs7 class selector codepoint 7 (precedence 7)
default default bit pattern of 000000
ef expedited forwarding bit pattern 101110
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 708-362-1418 (Outside the US and Canada)
This archive was generated by hypermail 2.1.4 : Fri Dec 12 2003 - 12:29:12 GMT-3