I have the following scenario going on for an MPLS Lab. The diagram below shows the topology:
R1 through R6 are an MPLS core. R1 and R6 are PE routers, R2, R3, R4 and R5 are P routers. Each Frame relay network is a separate subnet.
The core is running OSPF and MPLS is enabled on all interfaces.
My problem has to do with the FR between R1, R2 and R3. In this Configuration, R3 is a spoke, and R1 and R2 are hubs that do not have a direct circuit between them. There is an FR map pointing to R3 for each router to reach the other.
With the OSPF core converged, the I've noticed that the R1 decides to reach R6 through R2 to R5, despite that they are not OSPF neighbors as they do not have a direct FR circuit. When this happens, the CE devices cannot ping each other across the MPLS VPN, and even R1 cannot ping the vrf routes received from R6 and vice versa.
When I take that R2 interface so that it does not neighbor with R3, R1 will then decide to reach R6 thorugh R3 to R4. In this case CE devices can ping each other and R1 can also ping vrf routes received from R6 and vice versa.
I'm not sure what the issue is here. Is the problem related to MPLS switching, with Frame Relay routing, or is this not even a valid scenario to begin with and the FR between R1, R2 and R3 have to be fully meshed?
Also good to note that I've seen it happen that when R3 and R2 have already neighbored, and then I get R1 to neighbor with R3, R1 does not receive any OSPF routes from R3 at all. I had to take down R2 in order for R1 to receive routes.
Hmmm, isn't there somethig missing in your config? The default ospf network type is nonbroadcast on a serial link - and without configureing neighbor statements under the OSPF process on R3 OSPF won't establish any neighborships...
So there are two options:
1) On R3 configure neighbors:
router ospf 1
2) Change the network type to broadcast and make sure R3 will be the DR
I have tried both methods and neither are working. I am completely baffled and have no idea what the issue could be. It is either something with MPLS switching or frame relay.
Having R3 as a hub is definitely causing an issue. If R1's routing table has R2 as the next hop and both R1 and R2 have a direct connection between them everything works. If I take R2 out then R1's routing table shows R3 as the next hop everything also works fine. The problem lies when R1's routing table shows R12as the next hop to R6, but it has to go through R3 as a frame relay hub, vrf routes cannot be pinged any more.
I have tried all sorts of debugs I can think of but cannot get the information I need to see how the packet is flowing. Do you at least know what debugs I can use to troubleshoot?
MPLS VPN over frame-relay appeared to have a hitch...at least with what I was doing.
The problem appeared to be with MP-BGP...the packets do not get tagged with the LDP header in a broadcast or non-broadcast OSPF network. On your Frame-Relay interfaces, use the network type of point-to-multipoint so that a full adjacency is created and the specific /32's are injected.
Additionally, within BGP, you may have to use the command:
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...