I think best practices recommend the use of EBGP at PE-CE level . Doing this will avoid mutual redistribution between MBGP (in the mpls core). So may be migrating from OSPF to EBGP will be a good idea later on . Which IGP are you using in your Core ?
Rgds David Internet [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 29/03/2007 09:07 To kwbales cc cisco-nsp Subject Re: [c-nsp] OSPF Router ID Kurt Bales wrote: > Hey Guys, > > We are migrating our services to a MPLS VPN (on our providers network). We > are using OSPF to route between the remote sites and the providers VRF. We > can only seem to get the OSPF sessions to establish if we use the same OSPF > process ID as our provider, but all the docs I can find suggest that the > process ID only has context within the local router, and does not propogate > outside of the router? > > Does anybody have any suggestions as to why this might be? > you are right, as far as I can recall, the RFC specs say it is local only, but I seem to remember that in a MPLS context Cisco do use it. I can't seem to find why at the moment, but >From http://www.ciscopress.com/articles/article.asp?p=391649&seqNum=2&rl=1 NOTE If you want all the sites in the VPN to be in the same OSPF autonomous system, the process ID configured for the VRF on all PE routers must be the same. Alternatively, use the domain-id command to configure a consistent domain ID number (by default, the domain ID corresponds to the OSPF process ID). -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. Any offers or quotation of service are subject to formal specification. Errors and omissions excepted. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Lumison, nplusone or lightershade ltd. Finally, the recipient should check this email and any attachments for the presence of viruses. Lumison, nplusone and lightershade ltd accepts no liability for any damage caused by any virus transmitted by this email. -- -- Virus scanned by Lumison. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. ********************************************************************************************** BNP Paribas Private Bank London Branch is authorised by CECEI & AMF and is regulated by the Financial Services Authority for the conduct of its investment business in the United Kingdom. BNP Paribas Securities Services London Branch is authorised by CECEI & AMF and is regulated by the Financial Services Authority for the conduct of its investment business in the United Kingdom. BNP Paribas Fund Services UK Limited is authorised and regulated by the Financial Services Authority _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
