[j-nsp] Routing-instances

[Erdem Sener]

Besides what Sean said, you'll need to make sure that all next-hops
are resolvable as well. So, in your scenario you'll probably need to
configure rib-groups between t1's routing-instance and inet.0

HTH

On 9/20/06, Christian Koch <ckoch at globix.com> wrote:
> That's what I assumed..thanks for your help guys..
>
> Heres another ques..
>
> I had an issue today I'll explain briefly
>
> A customer had t3 and t1..t3 was to be preferred and t1 I set a metric
> of 220 on in case the t3 fails.. (these are on2  diff routers, t3 is on
> the juniper and t1 on the cisco)
>
> Static route for t3 on juniper..but traffic was preferring the t1
> still..
>
> Then I found the routing instance statement at the end of the config,
> but it did look like it was complete
>
> }
> routing-instances {
>    routing-instances {
>        interface t3-5/1/1.0;
>    }
> }
> Now, any clue as why the traffic was preferring the t1 link?
>
> Was it because the routing instance was not configured correctly? (I do
> not know who added it or why it was..)
>
> Thanks!
>
>
>
>
>
> -----Original Message-----
> From: Leigh Porter [mailto:leigh.porter at ukbroadband.com]
> Sent: Wednesday, September 20, 2006 10:46 AM
> To: Erdem Sener
> Cc: Christian Koch; juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] Routing-instances
>
>
> They are also used for filter based forwarding.
> i.e.
>
> You match packets to port 80 and have a routing instance with a default
> route pointing to your transparent WWW cache, when the filter sees a
> datagram matching your filter instead of using the normal inet.0 routing
> table you can tell it to use a different routing table to select a route
> from for that datagram.
>
> Or say you have two upstream ISP connections, you can decide what ISP to
> send traffic to based on a filter and have each ISP with a different
> routing instance, I think this is the example used in the Juniper docs.
>
> Juniper routing instances can have their own routing protocol instances
> also, I believe.
>
> --
> Leigh
>
>
> Erdem Sener wrote:
> > Hello,
> >
> >  Well, basically the routing-instances are routing tables besides the
> > default inet.x and might be used for things like source-based routing,
>
> > MPLS/VPLS configuration etc.
> >
> >  By configuring a routing-instance you might be defining a VRF table,
> > a VPLS domain or just a routing table you can use for source-based
> > routing.
> >
> > HTH
> > --
> > Erdem
> >
> >
> >
> > On 9/20/06, Christian Koch <ckoch at globix.com> wrote:
> >
> >> Can anyone explain to me exactly what "routing-instances" are?
> >>
> >> Thanks!
> >>
> >>
> >>
> >> ______________________________
> >> Globix Network Operations / AS4513
> >> NOC: 212-625-7777 / 800-2-GLOBIX
> >> support at globix.com / www.globix.com
> >>
> >>
> >> _______________________________________________
> >> 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
> >
>
>
>


-- 
Erdem