cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
456
Views
5
Helpful
3
Replies

Strange QoS problem on 6500 switch

netwrkgod
Level 1
Level 1

Hello

We have a video conf. unit (10.x.x.3) connected to gig9/2 on a 6500 w/ Sup. 720. Connected to gig1/1 is our MPLS router.

If we monitor 9/2 we see the packets being tagged properly with dscp 46 - which is what we expect.

If we monitor gig1/1 we see that packets are now tagged dscp 0 (default). What gives?

Here's the config:

interface GigabitEthernet9/2

description *** Video unit ***

no ip address

logging event link-status

speed 100

duplex full

mls qos trust extend

mls qos trust cos

switchport

switchport access vlan 15

switchport mode access

power inline never

spanning-tree portfast

service-policy input VIDEO

=============================

interface GigabitEthernet1/1

description *** WAN ***

no ip address

logging event link-status

speed 100

duplex full

wrr-queue cos-map 1 2 2

priority-queue cos-map 1 3 5

mls qos trust dscp

switchport

switchport access vlan 6

switchport mode access

power inline never

spanning-tree portfast

===============================

mls qos map cos-dscp 0 8 16 24 32 46 48 56

mls qos

class-map match-any VIDEO

match access-group name VIDEO

policy-map VIDEO

class VIDEO

set dscp ef

ip access-list extended VIDEO

permit ip any host 10.x.x.3

permit ip host 10.x.x.3 any

===============================

I would've expected the QoS marking to be preserved throughout.

Thanks in advance!!

1 Accepted Solution

Accepted Solutions

schmij01
Level 1
Level 1

Your trust statement is screwing up the final DSCP on the packet. Since you are trusting CoS, and it looks like there is no trunking/802.1P value to use, it is setting the internal DSCP to 0. You don't see this until the packet leaves the switch though, since remarking occurs on egress.

See this section and diagram for more info:

http://www.cisco.com/en/US/customer/products/hw/switches/ps700/products_tech_note09186a008014a29f.shtml#summary

So, remove the mls qos trust statements and just let the policy-map do its work and you should see better results.

View solution in original post

3 Replies 3

schmij01
Level 1
Level 1

Your trust statement is screwing up the final DSCP on the packet. Since you are trusting CoS, and it looks like there is no trunking/802.1P value to use, it is setting the internal DSCP to 0. You don't see this until the packet leaves the switch though, since remarking occurs on egress.

See this section and diagram for more info:

http://www.cisco.com/en/US/customer/products/hw/switches/ps700/products_tech_note09186a008014a29f.shtml#summary

So, remove the mls qos trust statements and just let the policy-map do its work and you should see better results.

Thank you very much!

jkeeffe
Level 2
Level 2

I just saw this post - How were you monitoring the links to see that packets were getting marked or not?  Were you spanning a port and doing a packet capture, or is the a 6500 command that allows you to see the markings?

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card