[j-nsp] Juniper MX5 vs Brocade CER

[Doug Hanks]

These numbers will change with every hardware release and software
release. I used a generic number with the MX book.

The idea is that as soon as the book hits the shelf, the testing numbers
would have been obsolete anyway (it took Harry and I about 14 months to
write).


Your SE should be more than happy to give you the current scaling results
with the hardware + software combinations.

On 10/22/12 8:24 AM, "Saku Ytti" <saku at ytti.fi> wrote:

>On (2012-10-22 13:21 +0100), Darren O'Connor wrote:
>
>> It was Doug Hanks that said it. And he wrote the new MX book
>
>I've not read this book. But I find it really shame if book presents
>simplified marketing numbers instead of giving reader understanding of the
>platform.
>Juniper seems much more hesitant than Cisco to provider gritty
>architecture
>details. Maybe they think it's not relevant to operators, but it is
>
>Knowing how box works helps lot with troubleshooting software defects. It
>also helps with defining new products, as it helps deciding when there are
>many ways to configure it, which configuration is best fit for the
>limitations you have in HW.
>
>-- 
>  ++ytti
>_______________________________________________
>juniper-nsp mailing list juniper-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/juniper-nsp
>