- Purple, 4500 points or more
I've attached a gns lab that I created and need help with. What I've got is the following:
Customer A and B connect to ISP_PE1 and ISP_PE2.
ISP_PE1, ISP_P, and ISP_PE2 run eigrp in AS100.
ISP_PE1 and ISP_PE2 are running BGP in AS200 and peer with each of the customer routers, and run vpnv4 peer between ISP_PE1 and ISP_PE2.
On every customer router (CustomerA on ISP_PE1 for instance), I have the routes from the other CustomerA router on the ISP_PE2 side of the mpls network. I can't ping the CustomerA router from the other CustomerA router even though I see the routes. I also show the routes on ISP_PE1 and ISP_PE2 under the respective vrf.
I've attached the zip file should anyone want to take a look at it because I'm stumped.
Glad you got it working.
MPLS tags are only used within the MPLS cloud ie. between the PE & P routers. They are stripped at the egress of the MPLS clouhd and become normal IP packets. So the CE routers do not see any MPLS tags.
Actually to be more specific if you have enabled Penultimate Hop Popping the top tag is actually stripped before the packet reaches the egress PE so the egress PE actually receives the packet with only the VPN tag ie.
with MPLS VPN's the packets have 2 tags as they traverse the MPLS cloud.
So at the ingress PE a VPN tag is added. This VPN tag is only relevant to the egress PE ie. the intermediate P routers don't care about it.
Then the ingress PE adds another tag and this tag is used to label switch the packet to the next hop ie. the first P router. This P router then strips the top tag only and adds another tag to switch to to the next P router. The last P router removes the top tag and simply forwards the packet to the egress PE router without adding another tag. So when the PE router receives the packet it only has the VPN tag to process.
Apologies if you already knew all this.