[j-nsp] Which Router

[Campbell, Alex]

We have J4350s taking several full tables each.  Traffic peaks at about
100mbps and CPU sits constantly at about 10%.  I'm not sure how much
slower the CPU on the J2320 is but I would be surprised if it couldn't
comfortably handle our traffic loads with full tables.


-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Justin Sharp
Sent: Wednesday, 14 May 2008 10:24 AM
To: justin at sharpone.net
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] Which Router



Justin Sharp wrote:
> Lee Hetherington wrote:
>   
>> Hi List,
>>
>> Forgive me if I am asking stupid questions, but I am new to BGP.
>>
>> We are looking to empower our networks with BGP.  We have 3 pops and
3 different providers.  Currently we have various staticly routed
connections, which is bad for a hosting co.
>>
>> POP A:  100Meg to Abovenet and 1000Meg to A smaller uk isp
>> POP B:   100Meg to Abovenet and 1000Meg to A smaller uk isp
>> Corp HQ:  10meg to POP A and 1x 2meg to Telia and 1x 2meg to Telstra
>>
>> We have a peak at Christmas of around 60mbits/sec across all links.
>>
>> I am looking at the Juniper J series of routers, as our requirements
at the moment are pretty small.  Speaking to my hardware vendors has not
filled me with confidence and they do not seem to know what i need in
terms of the routers.  Our switches are all already speaking OSPF etc.
>>
>> In each location we will have 3 bgp sessions this I know.  2x eBgp
and 1x iBgp.  
>>     
> I'm not sure how you are calculating the number of sessions required, 
> keep in mind that your iBGP peers need to be full meshed unless you
are 
> running route reflection (which is an separate license in the 2350 as
is 
> my understanding).
>   
>> Will a J2320 with 1Gb Ram be enough to hold the routing tables
required and run?  Since we take full transit from all ISPs I am
guessing this is going to be ok, but will not allow much growth.  My
suggestion internally for kit would be the J4350 with 1Gb Ram to start,
then upgrading to 2Gb in the future as we perhaps take transits from
others or peer publically.
>>
>>   
>>     
> As for router size, if you are taking only default or customer routes,
J 
> series might be fine. Our sales engineer recommends the J6350 at a 
> minimum for full routes, and really suggests that we be at the M
series 
> (M7i, M10i for in chassis redundancy).
>
> YMMV, IMHO, etc etc..
>
>
>   
Sorry for replying to myself, but wanted to also add.. You will not see 
your 1000Mb of throughput on the lower end J's. So you pay for 1000Mb 
but you won't ever get it unless you step up the router. Also, the M 
series is a whole different ball of wax when it comes to cost :) Now you

get to pay for each and every interface, and in some cases, interfaces 
to perform other services (like vpn, mlppp, etc). Lastly, those PICs 
aint cheap.. a good deal of them cost more than the router (I think list

price on an 2xOC3 is like 35k, not sure what a gige port costs).
> --Justin
>
> _______________________________________________
> 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

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________