[j-nsp] Adaptive services(1)

[David Williamson]

You'll find there's a lot of mystery around AS PICs.  Our recent (and
mildly painful) experience is that a standard FPC will recognize the
PIC, but you can't do anything productive with it.  You'll need an
FPC-E, definitely.  (Our experiment wsa with a set of M5s, for what
that's worth.)

We haven't yet tested the I/O rate, but I thought the higher rate was
the quoted statistic for the AS2.  The docs may have some confusion
about AS1 vs. AS2, and may just refer to both generically as "AS"
PICs.  Be careful, and good luck!

-David

On Mon, Sep 25, 2006 at 02:08:59AM +0200, Jonas Frey wrote:
> Hi,
> 
> According to:
> http://www.juniper.net/techpubs/software/junos/junos74/swconfig74-services/html/adaptive-services-overview.html
> The AS PIC needs a FPC-E to support *all* features. That sounds to me
> like it will work in a normal FPC but with limited functionality. Can
> anyone clarify what does/doesnt work if its placed in a regular FPC?
> 
> 
> It seems theres a docbug on the documentation on M20 pics:
> http://www.juniper.net/techpubs/hardware/m20/m20-pic/frameset.html
> 
> says that AS (1) PIC supports 250Mbps bi- and 500Mbps unidirectional
> traffic as well as 250k pps. While
> http://www.juniper.net/products/junos/105021.html
> says that it now does 400Mbps bi- and 800Mbps unidirectional as well as
> 400k pps.
> 
> And according to http://www.juniper.net/support/eol/mseries_hw.html the
> AS (1) PIC is EOL but it can still be found under the non-EOL module
> list of M20 pics.
> 
> 
> Regards,
> Jonas
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp