[c-nsp] A compromise between traffic from 2 links to one

Rodney Dunn rodunn at cisco.com
Thu Oct 21 22:37:26 EDT 2004

If you can identify the traffic that was going over
the T3 previously you can just do QOS to
guarantee the original traffic gets the
required % of BW.

Now getting fancy QOS at an OC3 rate will
be a bit tricky unless it's a hardware forwarding

You could just police the traffic that was going
down the T3 before to some value (say 5 Mbps or so)
but the drawback there is if you don't have 146 Mbps
of high priority traffic you will still not let
the low priority traffic through at a higher rate.

That's the major difference between policing
and queueing.

What platform is terminating your OC3?


On Sun, Oct 03, 2004 at 10:37:25AM +0200, Karim Adel wrote:
> Dear NSP
> We have 2 links on different routers, an OC3 and a T3.
> The T3 are used to carry a small amount of traffic, at most (24 Mbps)
> and the OC3 carries at most (146Mbps),
> We have to remove the T3 for a week or so, and of course let the T3
> traffic flow through the OC3, but obviously adding the traffic on both
> links sums up to (146+24 = 170 Mbps),
> You will notice that with this calculation, we exceeded the OC3
> physical bandwidth,
> The traffic over the T3 has less priority for my business, I am sure
> there will be dropping, and that would be the T3 traffic, thinking out
> of the box, I had a couple of nice ideas, but they all needed code,
> which isn't something we have available right now, can I reach a fair
> compromise using rate limiting, BGP, QoS, Any ideas ?
> Kind Regards,
> _______________________________________________
> 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/

More information about the cisco-nsp mailing list