[c-nsp] DSCP QoS through QinQ tunnel

[Arie Vayner (avayner)]

Tony and Tim,

Make sure that on all the switches in the path you either turn off mls
qos remarking "mls qos queuing-only", disable "mls qos", or make sure
you trust the marking on the ingress direction...

If you just enable "mls qos" and do nothing else, the default behavior
would be to reset any COS markings.

QOS on 3550:
http://www.cisco.com/en/US/docs/switches/lan/catalyst3550/software/relea
se/12.2_44_se/configuration/guide/swqos.html

Qos on 6500:
http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/con
figuration/guide/qos.html

Arie

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Tony Baade
Sent: Wednesday, March 17, 2010 23:38
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] DSCP QoS through QinQ tunnel

All,

We have a client who is using DSCP to tag VOIP traffic through a QinQ
tunnel we built for them on our network.  The client is reporting their
traffic is being tagged when leaving their LAN on one side of the
tunnel, but when arriving on the other side the tag has been stripped.
Is there any thing we need to do w/ the QinQ tunnel to ensure their QoS
tags are not stripped?

We are using cisco 3550s to terminate each end of the QinQ and the
tunnel is being trunked over a backbone consisting of 6524s and 6503s.

Any help is greatly appreciated.

Thanks

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/