[j-nsp] Junos ospf question

[Andrew Miehs]

Don't include the storage networks in ospf - and the static route those networks on a to b and on b to a...



Sent from a mobile device

> On 25 Sep 2013, at 19:11, R S <dim0sal at hotmail.com> wrote:
> 
> There is no default route
> 
> could you paste a config example explaining in simple words what you mean ?
> 
> I need that same native OSPF of A and B do not transit to C if link A-B goes down
> 
> 
> 
>> Date: Wed, 25 Sep 2013 01:51:31 -0700
>> Subject: Re: [j-nsp] Junos ospf question
>> From: jof at thejof.com
>> To: dim0sal at hotmail.com
>> CC: p1 at westerlund.se; ipv6freely at gmail.com; juniper-nsp at puck.nether.net
>> 
>> Seems doable to me, so long as there are prefixes for both the storage
>> gear hanging off of router "A" and "B". If, for example, your storage
>> gear hanging off of "B" is using a default route to reach the gear off
>> of "A", then you can't do it.
>> 
>> Add a term to your applicable OSPF import policy on all three routers
>> that matches the next-hops of the low-speed GigE paths, and the
>> prefixes applicable for your storage application. Then, reject the
>> route.
>> 
>>> On Wed, Sep 25, 2013 at 1:39 AM, R S <dim0sal at hotmail.com> wrote:
>>> basically I've a triangulation A - B - C - A
>>> 
>>> single area 0
>>> 
>>> A-B link is 10Gbs
>>> A-C and B-C is 1 Gbs
>>> 
>>> since in A-B run a very high volume of traffic (storage), I do not want if A-B fails this traffic goes through C
>>> 
>>> C redistribute as well statics into OSPF
>>> 
>>> Hope it clear now
>>> 
>>> Subject: Re: [j-nsp] Junos ospf question
>>> From: p1 at westerlund.se
>>> Date: Wed, 25 Sep 2013 10:23:39 +0200
>>> CC: ipv6freely at gmail.com; juniper-nsp at puck.nether.net
>>> To: dim0sal at hotmail.com
>>> 
>>> Can you give some more details? I'm not sure I understand all of your requirements.
>>> Are you trying to influence something native to OSPF, or are you talking about setting metrics for routes redistributed (Cisco-speak) from another protocol?
>>> /Per
>>> 25 sep 2013 kl. 10:09 skrev R S <dim0sal at hotmail.com>:I understood the same and I need to be able to drop network announcement in a very granular way...
>>> 
>>> _______________________________________________
>>> 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