Thanks,

I'm not sure if that would solve the problem, as I would like to remove my old routers, and let the new PE's do the peering with my ISP's, but what I could do is running a EoMPLS tunnel from each ISP-interface into my datacentre, and leave a router or two there for Internet-peering.. Will that be a good solution?

L@rs

EomplS was not suggested because the routing in that case wont be optimal. Since its a P2P layer 2 circuit.

But if you want to use it as a intermediate solution till you migrate out you old setup, and also the end points involved are not more than 2 (Old AS peering points) then you can use the L2VPN soln.

For the migrated new setup as well, again the same thing goes, if you have only 2 points (1 upstream ISP peering point and second point is datacenter) then you can use the l2VPN soln, if more than 2 points then if you be worthwhile to invest more time and reosurces in planning/designing BGP Free Core for you Internet PE's.

HTH-Cheers,

Swaroop

An old thread on similar lines, may be of some help.

http://forums.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Service%20Providers&topic=MPLS&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1ddc621e

HTH-Cheers,

Swaroop

Thanks.. That was a interresting discussion..

I will probably go for the EoMPLS solution until AS-migration is done.. We are talking about three ISP's - one of them located in the datacentre, two in a Telco-site, where we will add a PE or two..

Another discussion we've had - Internet Global or VRF?

-We concluded that we'd do this in the global table - as we are peering with another MPLS-network, and would not like to flood the other network with a vrf carrying 235K routes.. We thought that it would be easier to shutdown the other MPLS-network's peers in the ipv4 family, still activated in the vpnv4 family....

L@rs