Eigrp over FR
I have a partial mesh topology.
RTA is the hub, RTD and RTF are the spokes.
All 3 routers are using multipoint interfaces.
RTA ip 100.1.1.1/29
RTD ip 100.1.1.2/29
RTF ip 100.1.1.3/29
My Fr pvc on RTA goes to RTD and RTF on bidir dlci's 100 and 400 respectfully.
I have left everything default so the mapping is automatic between ip and dlci, it is broadcast by default.
RTA forms an adjacency with RTD and RTF.RTD and RTF form an adjaceny with RTA only due to partial mesh.
My layer 2 is working fine.
If i create a loopback interface on a spoke and advertise it into eigrp via network command it will appear on the hub but it will not appear in the other spokes routing or topology table .I have disabled split horizon on the hub RTA.
I've also adjusted the metrics to take only delay into account.
If i do a debug on the spoke i can see the route advertisment arriving with a delay metric of infinity i.e. unreachable.
Any idea what i'm missing? If i disable eigrp and run rip it works perfectly!
RTA is the hub, RTD and RTF are the spokes.
All 3 routers are using multipoint interfaces.
RTA ip 100.1.1.1/29
RTD ip 100.1.1.2/29
RTF ip 100.1.1.3/29
My Fr pvc on RTA goes to RTD and RTF on bidir dlci's 100 and 400 respectfully.
I have left everything default so the mapping is automatic between ip and dlci, it is broadcast by default.
RTA forms an adjacency with RTD and RTF.RTD and RTF form an adjaceny with RTA only due to partial mesh.
My layer 2 is working fine.
If i create a loopback interface on a spoke and advertise it into eigrp via network command it will appear on the hub but it will not appear in the other spokes routing or topology table .I have disabled split horizon on the hub RTA.
I've also adjusted the metrics to take only delay into account.
If i do a debug on the spoke i can see the route advertisment arriving with a delay metric of infinity i.e. unreachable.
Any idea what i'm missing? If i disable eigrp and run rip it works perfectly!
Networking, sometimes i love it, mostly i hate it.Its all about the $$$$
Comments
-
EdTheLad
Member Posts: 2,111 ■■■■□□□□□□
OK, found the problem.
Split horizon for eigrp has a seperate command.
no ip split-horizon eigrp 1 instead of no ip split-horizon.
Cisco developers are crazy!! I wasted afew hours checking on this.Networking, sometimes i love it, mostly i hate it.Its all about the $$$$ -
Yankee
Member Posts: 157
Disabling split horizon on the hub should have been the key. There is a hidden eigrp command, sh ip eigrp event that lists the last 500 eigrp events that is difficult to decipher but may give you a hint. I would restore metrics to default and ensure your neighbor relationships stay solid (over 3 minutes or so).
The real world doesn't use multi-point, so I haven't played with that in years, but I expect the issue to be there.
Yankee