Static, RIP, EIGRP, OSPF, BGP, IBGP, IS-IS and any other routing.
1 post • Page 1 of 1
Hi All, I would like to get a clarification from all whether the following topology and my thinking are correct. Currently I am not able to do reproduce in my lab due to lack of hardware so seeking advice here. I am providing Carrier Supporting Carrier MPLS VPN service to one of our customers. He is already running L3 MPLS VPN services over our network. Now he has a requirement of running VPLS connectivity over the existing CSC MPLS VPN. I am sure that this service will also work over CSC VPN as it is transparent to any MPLS services over it. Only thing to make sure is the end to end network should have support for MTU sizes. Apart from that as a CSC provider I do not have any limitations. Only limitation is for the customer implementing VPLS i.e. PE hardwares should support VPLS services. Are there any other limiation on carrying VPLS service as CSC Provider or any points taken into account? Any CSC VPN providers have this kind of customer i.e. VPLS? thanks in advance Arun
Hello Arun,MTU has to be great enough to accomodate the additional label in Carrier Supporting Carrier scenario. Another point of attention with modern VPLS is that if the customer attempts to use point to multipoint LSPs this could be a problem Until the VPLS uses a collection of point to point LSPs to interconnect the L2 PE nodes it should be fine. -Antonio:are you referring to the different options of inter AS scenarios? Hope to helpGiuseppe