[j-nsp] RE-S-2000-4096

[Hugo Slabbert]

Anecdotally, we have an MX480 with RE-2000 in a very similar space as 
you're describing: taking in 4x full v4 tables, 3x full v6 tables, and a 
chunk of v4 and v6 peering routes at a couple of exchanges.  No issues.

-- 
Hugo

hugo at slabnet.com: email, xmpp/jabber
PGP fingerprint (B178313E):
CF18 15FA 9FE4 0CD1 2319 1D77 9AB1 0FFD B178 313E

(also on textsecure & redphone)

On Tue 2015-Oct-20 13:44:54 +0800, Chen Jiang <ilovebgp4 at gmail.com> wrote:

>RE-2000 could support about 10M route in RIB.
>
>RE-2000 is X86 based RE and MX80/MX104 is PPC based RE.
>
>From raw evaluation, in JUNOS PPC RE is about 1/3 performance vs. X86 RE
>for same frequency,
>
>On Wed, Oct 14, 2015 at 9:16 PM, Colton Conor <colton.conor at gmail.com>
>wrote:
>
>> How many full routes can two RE-S-2000-4096 in a MX480 support? How limited
>> is this older card? How does it compare to the RE found in the MX104 or
>> built into the MX80?
>>
>> On the MX480, when do most make the decision to upgrade from the
>> RE-S-2000-4096
>> to a RE-S-1800X4-16G? What does the extra processing and ram enabled on
>> this newer card?
>>
>> Application would be peering on an internet exchange with content
>> providers, and 4 connections to Tier one networks.
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>
>
>
>-- 
>BR!
>
>
>
>           James Chen
>_______________________________________________
>juniper-nsp mailing list juniper-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/juniper-nsp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20151020/bad3b06d/attachment.sig>