Extending MPLS VPN from one service provider to another through CE router ?

[diptishdoshi]

hi friends ,

A query about MPLS service provider peering .

Below mention is the design issue im facing ...

Consider a scenario in which a customer router CE has 2 links connected to 2 PE of 2 different MPLS service provider ( say Service provider A and Service provider B ) . Some of my sites are connected to service provider A and some are connected to service provider B . I want site in service provider A to be able to reach to site in service provider B and viceversa . BGP is used as CE-PE routing protocol .

What will be the best solution for this scenario ???

I dont have required resources to try and confirm but what i feel is ... the above scenario wont be any problem because CE router will act as a normal transit path between the 2 service provider network . Please correct me if im wrong ?????

What i'm not very sure is ... What will happen if there are multiple VPN of one client is both the service provider network and a continuity is required for that VPN across both the service provider network . That is , all the VPN's in service provider A's network should be reachable to VPN's of service provider B's network and Viceversa.The twist in this case , is we will also have to pass on the VPN information across the CE router .

what all will be an issue ??? how can i resolve it ?? Any document on this .. ??? Any pointers ???

[didyap]

For MPLS VPN to work properly, the VPN label must be allocated by the router. This router is indicated by the next-hop attribute of a route. In BGP, the next-hop attribute of a prefix is changed by a router when it advertises to a neighbor using eBGP. With the Inter-AS MPLS VPN feature, the next-hop address of a VPN route is changed by the AS border router. This occurs when the VPNv4 address is advertised to the border router of the neighboring AS. This is done through multiprotocol eBGP, along with a new label for the route.