cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
236
Views
0
Helpful
1
Replies

about 4500 and QoS

ariela
Level 4
Level 4

Hi folks,

I've a topology like that:

customer: 3550

aggregator: 4500

backbone: 6500

on 3550 and 6500 I work with DSCP values. Between 3550 and 4500, and 4500-6500, I've trunks. Normally the 4000 family creates the "internal DSCP" value for egress policies using DSCP for IP-traffic, and using CoS for non-IP and for traffic from trunks. That is packets have my DSCP value in ingress, but a DSCP-to-CoS in egress.

Question: there's a way to have the same DSCP value in ingress and egress on 4500 for traffic trunked?

<edit> better:

1- after internal DSCP egress policies, the packet has a CoS-to-DSCP value, or the original DSCP value?

2- if Cos-to-DSCP value:

http://www.cisco.com/en/US/products/hw/switches/ps663/products_tech_note09186a00800946e9.shtml

"Egress policy cannot match new QoS levels that are changed by ingress marking."

If I remark the ingress traffic with a service-policy in input, I see that DSCP value after egress policies?

</edit>

Any advice will be appreciated

Best Regards

Andrea

1 Reply 1

ariela
Level 4
Level 4

maybe 'no qos rewrite ip dscp' does the trick?

thanks

Andrea