Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

QoS Marking Question

Status
Not open for further replies.

NetworkJunkie

Technical User
Mar 25, 2013
3
GB
Hi,

I have a small problem and I'm a bit confused, Cisco suggested that you should mark traffic as close to the end devices as possible. So I wanted to try marking the traffic coming from S1 to R1, S2 to R2, and S3 to R3 on Switch 2 (Cisco Catalyst 2960) with the following config:

access-list 101 permit udp any any eq 10101
access-list 102 permit udp any any eq 10102
access-list 103 permit udp any any eq 10103

class-map PHONE
match access-group 101
exit
class-map CAMERA
match access-group 102
exit
class-map WEB
match access-group 103
exit

policy-map MARK
class PHONE
set ip dscp 46
exit
class CAMERA
set ip dscp 32
exit
class WEB
set ip dscp 10
exit
exit

interface fa0/1
service-policy out MARK

I did "service-policy out" to mark the traffic coming out of Switch 2's Fa0/1 going to Router 2's Fa0/0 so they are ready for the queueing mechanism at Router 2's S0/0/0 interface, but after entering the command it says it is not supported. From what I understand I am marking "engress" traffic (traffic from S1 to R1 as an example) thats why I used the command "service-policy out", rather than "ingress" traffic (traffic coming from R1 to S1).

My questions:

1. Have I got the concept of ingress and engress correctly?
2. Is there another way to do it or the only way possible is marking traffic on Router 2's Fa0/0?
3. If I do the marking on Router 2's Fa0/0 is it going to be ingress (service-policy in MARK) or egress (service-policy out MARK)

Thanks,
Unicross


1e86cn.jpg
 
Depending on what your switch is, you may not have the option of marking them "out".
I've usually had to mark it "in" at the access ports.
 
The 2960/3560/3750 switches do not support egress QoS policies. You must do the marking on ingress - which is even closer to the device... On egress you queue the traffic based on its marking by mapping the appropriate DSCP values to one of the three thresholds in one of the four queues - i.e. Q1T2.

Andy
 
Thanks, I'm now marking traffic for each ports connected to the end devices :D using the command service-policy input MARK.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top