[j-nsp] SRX for access/core routing/MPLS duties?

[Scott T. Cameron]

BGP is slow.  Painfully so.

I have 2x SRX3400 in a chassis cluster config getting 2 full BGP tables.  I
would say it takes at least 5 minutes for the BGP updates to complete and
for the device to be usable.

IPv6 support will be in 10.2 for SRX3400 and higher.  10.2R1 exists today
but has a number of interesting bugs.

I wouldn't really recommend this device as a router.  I just purchased some
MX240s to take over the routing role from my SRX3400s.

Scott

On Wed, Jul 28, 2010 at 10:05 AM, TCIS List Acct
<listacct at tulsaconnect.com>wrote:

> I've been reading past threads on the SRX line with interest.  It seems
> this box can do many of the things we are looking for (at a low price
> point), which include:
>
> - MPLS
> - IPv4 routing (OSPF, BGP)
> - Runs JunOS
> - Could be used at the access layer
> - Future IPv6 support
> - If required, could be used as an edge device holding a full IPv4 table
> (at least, the SRX650 and above)
>
> Can anyone comment on experiences with these devices, such as:
>
> - Wire rate?  yea/nay?
> - Anyone ever tried to use one as an edge router w/a full BGP feed?
> - MPLS -- mainly EoMPLS type stuff, esp. at the access layer
> - Stability (we understand that this is highly specific to the JunOS
> release)
>
> TIA.
>
> --Mike
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>