[j-nsp] Floating default routes on M-series

[Junaid]

Hi,

Thanks for the input David. Let me clarify; I am getting default route
from my upstreams via BGP. But as I mentioned, I want to uplink the
traffic of some specific customers via one upstream and in case that
upstream goes down, I want the traffic to take an alternate path. In
Cisco we used to do it with route-maps and we had to manually change
the next-hop IP address when the upstream became inaccessible. Now, we
have implemented this Policy Based Routing in Junos using forwarding
instance (config pasted in my last email) but the implementation does
not cater for the case when the next-hop IP becomes unreachable. I am
looking for a solution to uplink traffic via a particular upstream/ISP
but the traffic should follow an alternate path (e.g. follow the
default routing table) when the upstream is inaccessible keeping in
mind that in my particular case my ISP is connected to me on an
Ethernet sub-interface. So the interface never goes down.

Any help will be highly appreciated.

Thanks.

Regards,

Junaid


On Thu, May 22, 2008 at 7:15 PM, David Ball <davidtball at gmail.com> wrote:
>  Is there a specific reason for not having made use of BGP to handle
> the failover to your upstream provider(s)?  Depending on how you
> connect to them, you may or may not require a /24 and your own ASN to
> provide proper redundancy.  You could even get by with only receiving
> a default route from them (eliminating the need for lots of memory).
> Anyhow, not sure how many upstreams you have, how you connect to them,
> or whether they can do BGP or not, so I'll leave it at that for now.
> Might be worth talking to them about it though, to see if it's an
> option.
>
> David
>
>
> On 22/05/2008, Junaid <junaid.x86 at gmail.com> wrote:
>> Hi,
>>
>> I am trying to uplink traffic for some of my customers via ISP-1 using
>> routing-instance on an M-series route (relevant config snippet
>> attached).
>>
>> routing-instances {
>>     uplink-to-ISP1-ri {
>>         instance-type forwarding;
>>         routing-options {
>>             static {
>>                 route 0.0.0.0/0 next-hop a.b.c.d;
>>             }
>>         }
>> }
>>
>> My problem is that the next-hop ip a.b.c.d is on an Ethernet
>> sub-interface on the same router that does not go down. Hence when I
>> lose connectivity to my ISP-1, the traffic uplinked via this routing
>> instance is dropped. Can I configure floating static routes using
>> 'qualified-next-hop' within this routing-instance - will this help
>> considering that fact that my next-hop IP address in this case is
>> assigned on an Ethernet sub-interface? Or can we have another solution
>> to the problem like some method to detect that the next-hop IP is
>> unreachable so that a different next-hop can kick in?
>>
>>
>> Regards,
>>
>> Junaid
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>