Hi,
OSPF process id by default implies the domain-id.
As was pointed out by Brian and Marko, keeping the domain-id the same, the
PE that redistributes from MB-BGP into OSPF will make the LSAs be type 3
instead of type 5.
If you wanted to have routes between CEs appear in the same area even
though they are connected through the MPLS base VPN, you need to look at
sham-links which are in many ways like a virtual-link. With sham-links,
the domain-id doesn't come into play at all though.
This was my exploration of the subject -
http://noshut.blogspot.com/2011/08/ospf-domain-id-and-sham-links.html
Cheers,
Adam
On Sat, Jan 12, 2013 at 3:08 AM, Tauseef Khan <tasneemjan_at_googlemail.com>wrote:
> Do i need to match domain id on all the PE routers connecting customer
> sites for mbgp routes to correctly redistributed into ospf. OR domain-id
> could be different on PEs as below.
>
>
> Router_A
> ip ospf 10 vrf CUSTOMER_A
> domain-id 1.1.1.1
> !
> ip vrf CUSTOMER_A
> rd 10:10
> route-target both 10:10
>
>
> RouterB
> ip ospf 10 vrf CUSTOMER_A
> domain-id 2.2.2.2
> !
> p vrf CUSTOMER_A
> rd 20:20
> route-target both 10:10
>
> regards
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Sat Jan 12 2013 - 09:33:50 ART
This archive was generated by hypermail 2.2.0 : Sun Feb 03 2013 - 16:27:17 ART