Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
Community Member

QoS service-policy ingress problem

Packets don't get marked when we configure service-policy input qos-map on the interface which traffics comes from (g3/1). If we however configure service-policy output qos-map on our layer 3 vlan interface (vlan 698) we can see the right DSCP marking. (This is verified with Ethereal on a laptop connected to on the downstream C6509 switch)

We want to mark all traffic coming from g3/1 to be distributed downstream on vlan 698. How come it doesn't work on ingress interface? Or is it enough to just have the service-policy output on the egress interface?

This is the working configuration:

mls qos


class-map match-all qos-class

match access-group name qos-acl


policy-map qos-map

class qos-class

set dscp af42


interface GigabitEthernet3/1

ip address

no cdp enable


interface Vlan698

ip address

service-policy output qos-map


interface TenGigabitEthernet4/1


switchport trunk encapsulation dot1q

switchport trunk allowed vlan 600-699

switchport mode trunk

no ip address

mls qos trust dscp


ip access-list extended qos-acl

permit ip


ip route

We are running on WS-C6504-E/WS-SUP720-3B Version 12.2(18)SXF8


Re: QoS service-policy ingress problem

Generally with switching platforms you classify your traffic on ingress ports and then schedule it on egress ports.

For a VLAN-group policy, if a class of a parent policy map specifies the service-policy command, do not configure any other QoS actions for that class.

For more information Please click following URLs:

CreatePlease to create content