cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
603
Views
0
Helpful
1
Replies

Reachability in FR full mesh is not achieved using EIGRP

iuliatanase
Level 1
Level 1

I have worked upon the bellow topology to get a grasp of Frame Relay but I bumped into EIGRP routing, which I don't remember much. It's been 2 years since I went through CCNA3 and haven't been dealing with it since then. I will most likely review it, but for now it has been giving me trouble and I will most appreciate if you could set things clear for me.

My purpose for the bellow topology is to achieve full reachability which I can't obtain due to EIGRP not functioning properly. I believe I set up FR ok in a full mesh flavour.

FR_full mesh_topology.JPG


The config lines related to FR and EIGRP on router Mesh1 are:

interface Loopback1

ip address 192.168.0.1 255.255.255.0

!
interface Serial0/0
ip address 10.0.0.1 255.255.255.0
encapsulation frame-relay
serial restart-delay 0
frame-relay map ip 10.0.0.2 102 broadcast
frame-relay map ip 10.0.0.3 103 broadcast
!
router eigrp 1001
network 10.0.0.0 0.0.0.7
network 192.168.0.0
auto-summary

The config lines related to FR and EIGRP on router Mesh2 are:

interface Loopback1
ip address 192.168.2.1 255.255.255.0
!
interface Serial0/0
ip address 10.0.0.3 255.255.255.0
encapsulation frame-relay
serial restart-delay 0
frame-relay map ip 10.0.0.1 301
frame-relay map ip 10.0.0.2 302
!
router eigrp 1001
network 10.0.0.0 0.0.0.7
network 192.168.2.0
auto-summary

On Mesh3 the config lines are omologous.

The router configured for FR switching contains in the startup-config the lines:

frame-relay switching
!
!
!
!
interface Serial0/0
no ip address
encapsulation frame-relay
serial restart-delay 0
frame-relay lmi-type cisco
frame-relay intf-type dce
frame-relay route 102 interface Serial0/1 201
frame-relay route 103 interface Serial0/2 301
!
interface Serial0/1
no ip address
encapsulation frame-relay
serial restart-delay 0
frame-relay lmi-type cisco
frame-relay intf-type dce
frame-relay route 201 interface Serial0/0 102
frame-relay route 203 interface Serial0/2 302
!
interface Serial0/2
no ip address
encapsulation frame-relay
serial restart-delay 0
frame-relay lmi-type cisco
frame-relay intf-type dce
frame-relay route 301 interface Serial0/0 103
frame-relay route 302 interface Serial0/1 203

The output of sh ip eigrp neighbors command is the following on Mesh2 and Mesh3 routers:

IP-EIGRP neighbors for process 1001
H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq
                                            (sec)         (ms)       Cnt Num
0   10.0.0.1                Se0/0            167 00:01:05    1  5000  2  0

On Mesh1 which is assigned 10.0.0.1 on the serial interface the command returns no neighbor, which I find odd.

My purpose is to be able to ping from one loopback interface on another, but the way I configured EIGRP seems to be very wrong since the

neighbors table doesn't look consistent at all and no entry for 192.168.x.0 network is to be found in the routing tables in any of the routers.

Can you illuminate me please on this matter? If I can give further details, I would be happy to do it, just hoping it's a basic mistake I made or some

FR issue like split-horizon (which I hope I avoided setting up a full mesh).

Thank you,

Iulia

1 Reply 1

Richard Burts
Hall of Fame
Hall of Fame

Lulia

In Frame Relay mesh like this EIGRP enforces its own Split Horizon. You need to disable it with command no ip split-horizon EIGRP 1001.

HTH

Rick

Sent from Cisco Technical Support iPhone App

HTH

Rick
Review Cisco Networking for a $25 gift card