I totally agree with Keegan queuing has to be done where the congestion actually occurs. Even if you would queue on the lan interface on output , because you can't queue on the wan interface on input that doesn't have much effect because the congestion has already occured a few hops away from you. I did some tests like this and the priority traffic didn't seem to get prioritized at least this is the conclusion i came up with. The links were mpls links and i was trying to prioritize voip traffic from another site. Do you guys have positive experiences with this method ?
--- On Sat, 9/11/10, Brian Landers <[email protected]> wrote: From: Brian Landers <[email protected]> Subject: Re: [c-nsp] QoS on ingress To: "Heath Jones" <[email protected]> Cc: "cisco-nsp" <[email protected]> Date: Saturday, September 11, 2010, 5:25 AM There was actually a very interesting session at Cisco Live 2010 on inbound QoS for branch offices, using an outbound shaper on the inside interface of the router (e.g. on the gigE interface going to your switches). I don't recall the specifics, but the presenter had quite a bit of concrete data around the effects on latency, jitter, and p.loss. B* -- Brian C Landers http://www.packetslave.com/ CCIE #23115 (R&S + Security) _______________________________________________ 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/
