As you say you have 4x MXs, I assume there are two at site "A" and the other 2 sites have one each.
Your networks would be something like: 10.a.0.0/16 10.b.0.0/16 10.c.0.0/16 10.a .0.0 and 10.b.0.0 both have a couple of subnets which are being used for storage systems... let us assume - 10.a.255.0/24 and 10.b.255.0/24. As site A has two routers - your probably don't want to static route, so I see two possible solutions: 1) Use one routing protocol for 10.a.255.0/24 and 10.b.255.0/24 (IS-IS perhaps) and run ospf for all your other networks (Pretty horrible hack!) 2) set ACLS on the outbound interface on Site "A" going to site "C" and another set on Site "B" going to site "C" (deny probably wiser than drop).... But this has all said by other posters... On 25/09/2013, at 7:42 PM, R S <[email protected]> wrote: > indeed I make it simpler.... > > - network is already running with ospf (very sensite traffic) > - the concept is A-C-B-A as you correctly understood, but there are between A > and B 4 links with 4 big MXs on each side and on C there are two different > big SRX, hence topology is not so easier > - traffic is OSPF over IPSEC on each link > - the idea is to find a solution under the current config/topology/routing > domain, otherwise if I was enabled to rebuild everything I'd do in different > way... > > Subject: Re: [j-nsp] Junos ospf question > From: [email protected] > Date: Wed, 25 Sep 2013 11:32:01 +0200 > CC: [email protected]; [email protected] > To: [email protected] > > First let me see if I understand you correctly by rephrasing. > - Three sites A, B och C all connected with direct links- Link A-B has high > capacity- Links A-C and B-C has lower capacity- High volume storage traffic > traverses link A-B and must not use links A-C or B-C, even if link A-B goes > down- There is also other low-volume traffic between all sites that should be > routed around possible broken links. > Why not first try to solve it the easy way instead of using routing magic? > - If the high-volume storage traffic has static addressing that is unique, > you can use static routes that are NOT exported into OSPF. > If the easy way does not apply, there is a slightly more complex way to do it: > - If you can classify storage traffic statically with a filter, use FBF to > direct that traffic to a static default route in another routing instance. > I don't really recommend it, but there are high-tech alternatives that do > about the same as FBF in this case, but in a more "interesting" way. Usually > you should always think KISS in production, but I must mention it: > Multitopology routing. > With MT routing one OSPF instance can have more than one topology active, in > this case one with only A and B present, and another where all of A, B and C > are present. You then classify the ingress traffic and assign it to one of > the topologies (by using their specific routing/forwarding table). > Here is a link to where you can get started: > http://www.juniper.net/techpubs/en_US/junos12.1/topics/usage-guidelines/routing-configuring-multitopology-routing-in-ospf.html > . > Remember: I don't recommend it! > /Per > 25 sep 2013 kl. 10:39 skrev R S <[email protected]>: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 > > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
