[j-nsp] Running OSPF with the customer inside VRF
David Ball
davidtball at gmail.com
Sat Jul 12 09:25:49 EDT 2008
I believe OSPF sham-links are what you're looking for:
http://www.juniper.net/techpubs/software/junos/junos91/swconfig-routing/configuring-a-sham-link.html#id-11767296
It would look similar to the following, inside your VRF
routing-instance. The 'sham-link-remote' statements represent the
loopback IPs of the other PEs in the VRF, and sham-link-local
indicates what the local is. The VRF then builds 'tunnels', for lack
of better term, to the far-end PEs (the sham-link-local IPs) so that
the OSPF->BGP->OSPF translations (across your VRF) don't break your
LSA types. I'm sure someone else could provide a more comprehensive
description of exactly what goes on, but that's my simplistic way of
thinking of it.
protocols {
ospf {
sham-link local 10.1.0.1;
area 0.0.0.0 {
sham-link-remote 10.5.0.1;
sham-link-remote 10.22.0.1;
sham-link-remote 10.34.0.1;
sham-link-remote 10.43.0.1;
interface ge-7/3/0.0;
}
}
}
2008/7/12 Junaid <junaid.x86 at gmail.com>:
> Hi,
>
> I am trying to run OSPF on PE-CE links. I was going through JNCIS
> study guide and found the following:
>
> "When the received route has an internal route type and a domain ID
> value equal to the
> locally configured domain ID, it is advertised as a Type 3 Summary LSA."
>
> Does this mean that Type 1 and 2 advertisements from customer's site A
> will always get translated into Type 3 when site B will receive them?
> I believe that Cisco offers transparency (i mean that it preserves
> Type 1, 2 and 3) when the domain ID matches. Doesn't Juniper support
> this or am I missing something?
>
> Secondly, can anyone share his experience of running OSPF with the
> customer's multiple sites inside VRF. Any things that should be
> carefully sought or avoided? My PE routers are Juniper M10i/M7i.
>
> Thanks.
>
>
> Junaid
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
More information about the juniper-nsp
mailing list