[c-nsp] [j-nsp] juniper trinity

[Marlon Duksa]

It looks like you're right. This Trio chipset is a 30G chipset (full duplex)
and they have 4 of them per a 120G line card.

It makes sense, they have a 50G (full duplex) chipset on the T1600 core box
and then the 30G one for the MX. Of course they are totally different
chipsets, the former being not programmable and the latter being
programmable.

But I was hoping that Juniper would come up with something better than just
a 30G chipset. EZChip NP4 will have better throughput than this.

Marlon


On Fri, Oct 30, 2009 at 5:35 PM, Judah Scott <judah.scott.iam at gmail.com>wrote:

> The datasheet for the new MX 3D line cards is a little strange.  Assuming
> that a find-and-replace of "KB" to "K" will make it more coherent, this is
> an awesome amount of queues when comparing to competitors.  However, the
> new
> FPC/PIC-like card strategy is in 30Gb/s and 60Gb/s flavors.  Given that the
> 16x10GE card is oversubscribed this looks like the old DPC 4x10Gb/s stacked
> complex design (except now it is 4x30Gb/s?).  I guess this because the
> numbering is much like the DPC in that they are 0/0-3 1/0-3 2/0-3 3/0-3.
> Would Juniper really come out with a 30Gb/s (full duplex) chipset?  With no
> 40GE announcement I can only assume this chipset is going to be damn hard
> (or expensive) to do 40GE interfaces.
>
> Am I just missing something?
>
> -J Scott
>
>
>
>
> On Mon, Oct 26, 2009 at 12:16 AM, magno <massimo.magnani at gmail.com> wrote:
>
> > I agree, and I am pretty sure the new chipset will encompass and
> > largely extend all the qos functionalities provided today by ez-chip
> > chip.
> >
> > Cheers.
> >
> > Max
> >
> >
> > On 24/10/2009, Richard A Steenbergen <ras at e-gerbil.net> wrote:
> > > On Sat, Oct 24, 2009 at 06:38:53PM +0200, magno wrote:
> > >> I repeat, Trinity has nothing to do with ez-chip. My advice is to stop
> > >> elucubrating around any ez-chip whatever.
> > >>
> > >> Ez-chip proved to be quite limited for some qos functions, so I really
> > >> don't think juniper wants to be qos feature limited by a third-party
> > >> chip anymore.
> > >
> > > I believe the original question was "do the new asics integrate the
> > > functionality of ezchip, thus eliminating the need for it", and from
> > > what I've heard I believe the answer is yes. That is why we're talking
> > > about the ezchip in the first place.
> > >
> > > --
> > > Richard A Steenbergen <ras at e-gerbil.net>
> > http://www.e-gerbil.net/ras
> > > GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1
> > 2CBC)
> > >
> > _______________________________________________
> > 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
>