[j-nsp] redundant scenario

[GIULIANO (UOL)]

You can use an IPSec or a GRE Tunnel.

IPSec will work just fine for that.


> Hi Mathias,
> 
> If your J6350 run JUNOS with enhanced services, you can setup JSRP 
> (Juniper Network Stateful Redudancy Protocol).
> But I'm not really sure if this is the solution you're looking for.
> Still a newbie though >.<
> 
> Regards,
> 
> Stevanus
> 
> Matthias Gelbhardt wrote:
>> Hi!
>>
>> I am hoping you can give me some tips for implementing this scenario.
>>
>> I have two locations each with two J6350 routers. The locations are 
>> connected via a fiber network with each other. On each location the 
>> J's do have at least one eBGP session to different carriers. The boxes 
>> speak iBGP over the fiberlink with each other. We have split our PA 
>> space, so that we can announce different prefixes on each location. 
>> The prefixes which are not originating on one location will be 
>> received through iBGP from the originating one.
>>
>> How could I implement a redundant scenario? At first I had thought 
>> about getting the other prefixes via eBGP, but that is something, 
>> which seams to be no "clean" solution. Furthermore our carriers seam 
>> to be not happy with announcing prefixes with our AS in the path back 
>> to us.
>>
>> The more clean solution could be establishing a tunnel between the 
>> location over the internet and speak iBGP with a low priority over it. 
>> Unfortunatly I am a bit lost, which type of tunnel I should use for 
>> this scenario, as the J's are unable to implement a L2TP tunnel for 
>> example.
>>
>> Would be great to get an idea and help implementing this!
>>
>> Regards,
>>
>> Matthias
>> _______________________________________________
>> 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
> 
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 
> 270.5.6/1574 - Release Date: 25/07/2008 16:27
> 
> 
>