[j-nsp] source-based routing/vrf

[Erdem Sener]

Hi,

 You might configure a routing-instance (forwarding type) for each
carrier first, meaning that under routing-instance A, carrier A will
always be preffered and so on.

 After that, once your setup is complete along with local-prefence
values and rib-groups, you can use firewall filters with 'then
routing-instance <instance-name>" statement to redirect the traffic
based on source prefixes.

 For validation on multiple boxes, instance-type vrf and tagging
routes learned from each carrier should be considered as well.

 HTH

and then using rib-groups (and policy-statements) play with
local-preference values

On 6/28/06, Jonas Frey <jf at probe-networks.de> wrote:
> Hello,
>
> i've got the following setup:
>
> 3 Carriers: A, B, C
> 2 Prefixes: 10.0.0.0/24, 10.0.1.0/24
>
> What should be accomplished:
> Carrier A should be always prefered (via local-pref etc.)
>
> If the source is prefix 10.0.0.0/24 then Carrier B (after Carrier A)
> should be used, however in case Carrier B is dead, Carrier C should be
> used.
> Same goes for prefix 10.0.1.0/24 but in the other direction:
> Carrier C should used by default (after Carrier A), however if Carrier C
> goes down, Carrier B should be used.
>
> Not sure how to get this going, probably via vrf/rib-groups? Could
> someone shed some light on this? Thanks.
>
> Regards,
> Jonas Frey
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>


-- 
Erdem