[j-nsp] Tunnel hardware redundancy
Chris Evans
chrisccnpspam2 at gmail.com
Tue Aug 17 08:38:43 EDT 2010
I saw this actually but tunnel interfaces are not supported. I tried to
configure it on my device anyways and it confirmed that it is not supported.
It gave me an error message.
> Hi Chris
>
> Maybe you could tie the tunnels to redundant services interfaces. (RSP's)
>
>
http://www.juniper.net/techpubs/software/junos/junos94/swconfig-services/configuring-as-or-multiservices-pic-redundancy.html
>
> Cheers
> //KJ
>
> On 17 August 2010 01:12, Chris Evans <chrisccnpspam2 at gmail.com> wrote:
>
>> Looking for input from folks as I am not able to find an answer via
>> google..
>>
>> I have a question about tunnel interfaces. My question is mainly how do
you
>> have failover/backup hardware within a platform? Prime example is on an
MX
>> or M series. When one creates a tunnel interface you have to specify the
>> FPC/PIC tied to hardware (gr-5/1/0 for example). If this hardware fails
>> there isn't a way for it to failover. As I can specify the
>> source/destination IP within the tunnel interface that piece isn't tied
to
>> hardware. Is there a way to create a redundancy group?
>>
>> I come from a Cisco world and this is something I'm challenged with.
Tunnel
>> interfaces on Cisco devices are completely virtual and isn't tied to any
>> specific piece of hardware, thus modules can fail and the tunnel still
>> functions.
>>
>>
>> Thanks!
>>
>> Chris
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>
>
>
> --
> //kjwilki
More information about the juniper-nsp
mailing list