[j-nsp] How to CoS on M-series Fe interface but connected to Fe/E3converter ?
Rafał Szarecki
rszarecki at gmail.com
Tue Jan 16 12:08:37 EST 2007
Hi,
Generally Michaell is right. To have logical interface cos-aware shaper
on M/T, you need IQ PIC. And there is no FE IQ PIC.
The E-series and J-series can do this.
Also new generation of J-series is much more powerfull. But as we talk about
34Mbps, this should be not a broblem also for oldest J-series.
If you are not interesting in delay reduction but only want to differentiate
2 class of traffic by low-loss vs. best-effort. (e.g. Business Web-base
application vs. Internet) you can put all traffic to common queue with 2
different drop-profiles. And then shape queue. But this is applicable only
if you have 2 traffic classes and both of them are not sensitive for time
paramenters (delay and jitter).
--
Rafał Szarecki JNCIE
+48602418971
2007/1/16, michael.firth at bt.com <michael.firth at bt.com>:
>
> We recently hit a similar problem, and the answer from Juniper was 'you
> can't', at least for M series routers.
>
> The J series boxes have a facility called 'virtual-channels' which
> achieves this, but their performance is obviously not the same as an M
> series box. That said, the new J6x50 boxes are a lot better than the
> older J series boxes, and are capable enough for many applications.
>
> Hope this helps
>
> Michael
>
>
>
> > -----Original Message-----
> > From: juniper-nsp-bounces at puck.nether.net
> > [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Dang at onsite
> > Sent: 16 January 2007 04:27
> > To: juniper-nsp at puck.nether.net
> > Subject: [j-nsp] How to CoS on M-series Fe interface but
> > connected to Fe/E3converter ?
> >
> >
> > Hi,
> >
> > I have this topo:
> >
> > multi-ingress_FE------------>M7i-FE---------->Fe/E3_converter-
> > ---------------------->
> >
> > I need to CoS on FE interface but do not know how to let this
> > M7i know about "the real bw" 34Mbps of the Fe/E3 converter .
> > Congestion can happen on egress link of M7i to converter.
> >
> > You can policer each forwarding class, but then can not reuse
> > the vacant bw of other classes.
> >
> > You can policer the egress traffic to max value of 34M, but
> > you can not maintain the scheduler rate ratio.
> >
> > Is there any way to maintain the same scheduler rate ratio
> > for E3 rate as well as bandwidth re-utilization between all
> > forwarding classes ?
> >
> > BR,
> >
> > Dang
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
More information about the juniper-nsp
mailing list