Everton, Unfortunately, it would not work like you have described... The policing is done before the egress queuing, which means that the policer would be dropping traffic for all the classes equally, as it has no way to know which traffic belongs to which queue. This means that your priority traffic would be handled in the same way as the best effort traffic on the policer.
You could have a separate class per traffic class, and use a separate policer per class. Still, this would not have an effect on the egress queuing in the sense of setting the bandwidth budget. If you need to have a proper hierarchical policy, with a shaper and some child classes, you would need to use a SIP module (or ES20 on 7600) Arie -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Everton da Silva Marques Sent: Wednesday, February 18, 2009 20:54 To: [email protected] Subject: [c-nsp] Mixing WRR with policing under PFC3BXL + CFC +WS-X6748-GE-TX Hi, Can anyone please point any reference about how WRR interacts with a policer under 7609 + PFC3BXL + CFC + WS-X6748-GE-TX ? For instance, given the sample configuration below, will the policer drop packets which violate the policer's parameters (thus preventing WRR from taking effect) ? policy-map LAB_OUT class class-default police cir 1000000 ! interface GigabitEthernet1/5 speed 1000 wrr-queue bandwidth 1 2 7 service-policy output LAB_OUT end If so, is there a way of instructing WRR to serve queues at the policer's CIR (as opposed to the physical link rate) ? Thanks, Everton _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
