I cannot ping either of the CE router int. from the PE routers but i can ping the PE router interfaces from CE router. Interface status(PE to CE) on each of the PE routers is UP/UP.
The problem seem to caused by this interface command:
ip vfr forwarding vrf1. Before this command is turned on I can ping the CE routers fine. After I enter this command I have to reenter the ip addresses on the interfaces. Another problem is that the CE2 routes does not show up on the CE1 router and vice versa. However, CE2 routes is shown on the PE1 router and the CE1 routes on the PE2 router(Show ip route vrf vrf1, show ip bgp vpnv4 all).
From the PE, did you do a straight ping or a "ping vrf vrf1".
As far as the routes from CE1 not showing up on CE2 and vice versa, what routing protocol do you run between the PE and the CEs? If you run BGP and that both CEs use the same AS number, you need to configure "neighbor x.x.x.x as-override" for the 2 CEs under address-family vrf vrf1 to override the ASN received from the CE so it will be accepted when readvertised to the other CE.
Hope this helps,
Harold Ritter Sr Technical Leader CCIE 4168 (R&S, SP) email@example.com México móvil: +52 1 55 8312 4915 Cisco México Paseo de la Reforma 222 Piso 19 Cuauhtémoc, Juárez Ciudad de México, 06600 México
I figured out the problem. There was a problem with the label forwarding table at the first PE router. I owe my thanks to Rajiv Asati, excellent MPLS VPN troubleshooting guide. I used OSPF as the IGP protocol and there was no problem with iBGP VRF exchange. I used a straight ping at first between the PE and CE router, after that i figured out that i should use "ping vrf vrf1" and that worked fine for both PE to CE connections, but not across the core so there i had a problem that i was not aware of. The real problem was the PE1 router not exchanging labels with the core router i had set up, this was my first lab with MPLS VPN so i am a litte fresh on the subject.
Below is a link to a video showing how to analyze traceroute output in L3VPN and look up CEF forwarding and MPLS/TE/SR/SR-TE forwarding for labels through a domain. Some basic examples of traffic engineering are used but the concepts lend the...
This document summarises various health checks that can be done on a Cisco VIM pod.
Cloud sanity checks the health status of network, storage and various openstack infrastructure components like mariadb, rabbitmq etc....
The following pre-requisites are necessary for the migration from RSP440 to RSP880-LT to be successful.
Make sure that you have console access to the router.
Verify that the system is running a minimum o...
BGP flowspec in a nutshell is a feature that will allow you to receive IPv4/IPv6 traffic flow specification (source X, destination Y, protocol UDP, source port A .. etc) and actions that need to be taken on that traffic (...
IntroductionWhile gNMI is fairly new, it's becoming more and more powerful. Its abilities to simplify network management by the use of protocol buffer files and standard definitions are enabling our customers to integrate a lot better in multi-vendor envi...