eigrp lab help
Hi guys,
I"m working on an eigrp lab and has left me scratching my head.
Here's the scenario: eigrp hub and spoke over frame relay
I have no problems with route being advertised etc...
my problem is even wth the route showing up n all the routers R1
is the only router that can ping r2 route and r3 routes
r2 cannot get to r3 and vice-versa....can someone shed some light
i know it has to be something i'm missing or not understanding correctly
TIA
172.16.124.0/29 ,r2
r1
(frame)---<
`r3
172.16.124.x (connected to frame)
R1:
loopbacks
10.1.x.x /19
...
...
s0/0
ip summ-add 10.1.0.0 255.255.0.0
net 10.0.0.0
net 172.16.0.0
no-auto
neigh r2
neigh r3
R2:
loopbacks
10.2.x.x /19
...
...
s0/3
ip summ-add 10.2.0.0 255.255.0.0
net 10.0.0.0
net 172.16.0.0
no-auto
neigh r1
R3:
loopbacks
10.3.x.x /19
...
...
s0/0
ip summ-add 10.3.0.0 255.255.0.0
net 10.0.0.0
net 172.16.0.0
no auto
neigh r1
I"m working on an eigrp lab and has left me scratching my head.
Here's the scenario: eigrp hub and spoke over frame relay
I have no problems with route being advertised etc...
my problem is even wth the route showing up n all the routers R1
is the only router that can ping r2 route and r3 routes
r2 cannot get to r3 and vice-versa....can someone shed some light
i know it has to be something i'm missing or not understanding correctly
TIA
172.16.124.0/29 ,r2
r1
(frame)---<
`r3
172.16.124.x (connected to frame)
R1:
loopbacks
10.1.x.x /19
...
...
s0/0
ip summ-add 10.1.0.0 255.255.0.0
net 10.0.0.0
net 172.16.0.0
no-auto
neigh r2
neigh r3
R2:
loopbacks
10.2.x.x /19
...
...
s0/3
ip summ-add 10.2.0.0 255.255.0.0
net 10.0.0.0
net 172.16.0.0
no-auto
neigh r1
R3:
loopbacks
10.3.x.x /19
...
...
s0/0
ip summ-add 10.3.0.0 255.255.0.0
net 10.0.0.0
net 172.16.0.0
no auto
neigh r1
If you cannot express in a sentence or two what
you intend to get across, then it is not focused
well enough.
—Charles Osgood, TV commentator
you intend to get across, then it is not focused
well enough.
—Charles Osgood, TV commentator
Comments
-
networker050184 Mod Posts: 11,962 ModCheck your next hop addresses.An expert is a man who has made all the mistakes which can be made.
-
mikej412 Member Posts: 10,086 ■■■■■■■■■■What's your frame relay configuration?
What are your frame relay mappings?:mike: Cisco Certifications -- Collect the Entire Set! -
qplayed Member Posts: 303
interface Serial0 description Connected to R1 no ip address no ip directed-broadcast encapsulation frame-relay no ip mroute-cache no fair-queue clockrate 64000 frame-relay intf-type dce frame-relay route 102 interface Serial1 201 ... .... frame-relay route 811 interface Serial8 800 interface Serial1 description Connected to R3 no ip address no ip directed-broadcast encapsulation frame-relay clockrate 64000 frame-relay intf-type dce frame-relay route 201 interface Serial0 102 ... ... interface Serial8 description Connected to R2(Serial0/3) no ip address no ip directed-broadcast encapsulation frame-relay clockrate 64000 frame-relay intf-type dce frame-relay route 800 interface Serial0 811
172.16.0.0/29 is subnetted, 1 subnets C 172.16.124.0 is directly connected, Serial0/0 10.0.0.0/8 is variably subnetted, 9 subnets, 2 masks D 10.2.0.0/16 [90/20640000] via 172.16.124.2, 02:33:42, Serial0/0 D 10.3.0.0/16 [90/20640000] via 172.16.124.3, 03:03:16, Serial0/0 C 10.1.0.0/19 is directly connected, Loopback1 D 10.1.0.0/16 is a summary, 03:03:35, Null0 C 10.1.32.0/19 is directly connected, Loopback33 C 10.1.64.0/19 is directly connected, Loopback65 C 10.1.96.0/19 is directly connected, Loopback97 C 10.1.128.0/19 is directly connected, Loopback129 C 10.1.160.0/19 is directly connected, Loopback161 3640-R1_HQ#
172.16.0.0/29 is subnetted, 1 subnets C 172.16.124.0 is directly connected, Serial0/3 10.0.0.0/8 is variably subnetted, 9 subnets, 2 masks C 10.2.0.0/19 is directly connected, Loopback1 D 10.2.0.0/16 is a summary, 02:34:51, Null0 D 10.3.0.0/16 [90/41152000] via 172.16.124.1, 02:34:51, Serial0/3 D 10.1.0.0/16 [90/40640000] via 172.16.124.1, 02:34:51, Serial0/3 C 10.2.32.0/19 is directly connected, Loopback33 C 10.2.64.0/19 is directly connected, Loopback65 C 10.2.96.0/19 is directly connected, Loopback97 C 10.2.128.0/19 is directly connected, Loopback129 C 10.2.160.0/19 is directly connected, Loopback161 3640-R2_EAST#
172.16.0.0/29 is subnetted, 1 subnets C 172.16.124.0 is directly connected, Serial0/0 10.0.0.0/8 is variably subnetted, 9 subnets, 2 masks D 10.2.0.0/16 [90/41152000] via 172.16.124.1, 02:35:06, Serial0/0 C 10.3.0.0/19 is directly connected, Loopback1 D 10.3.0.0/16 is a summary, 03:04:40, Null0 D 10.1.0.0/16 [90/40640000] via 172.16.124.1, 03:04:40, Serial0/0 C 10.3.32.0/19 is directly connected, Loopback33 C 10.3.64.0/19 is directly connected, Loopback65 C 10.3.96.0/19 is directly connected, Loopback97 C 10.3.128.0/19 is directly connected, Loopback129 C 10.3.160.0/19 is directly connected, Loopback161 3640-R3_WEST#
If you cannot express in a sentence or two what
you intend to get across, then it is not focused
well enough.
—Charles Osgood, TV commentator -
dtlokee Member Posts: 2,378 ■■■■□□□□□□on R1's serial interface connected to the frame cloud disable split horizion for eigrp "no ip split-horizion eigrp <as#>"The only easy day was yesterday!
-
qplayed Member Posts: 303split horizon is already disabled, it was part of the lab excerciseIf you cannot express in a sentence or two what
you intend to get across, then it is not focused
well enough.
—Charles Osgood, TV commentator -
qplayed Member Posts: 303this will have to go to the back burner for now..i have a ton more labs t do...thanks guys for triyng....but if anyone does figure this one out....don't hesitate to chime inIf you cannot express in a sentence or two what
you intend to get across, then it is not focused
well enough.
—Charles Osgood, TV commentator -
mikej412 Member Posts: 10,086 ■■■■■■■■■■qplayed wrote:but if anyone does figure this one out....don't hesitate to chime in
Physical interfaces? Sub Interfaces? Inverse Arp? Inverse Arp disabled? Looks like a single subnet from the routing table output. I guessed you may have disabled split horizon since you said you had the routes in the routing table.
But if you're on the same subnet and the next hop is on your "local network" -- it doesn't matter what the routing table says if you can't reach that next hop.
Do a debug IP Packet and ping from one hub to another and see if you see an encapsulation failed message in the debug output, then you have a layer 2 to layer 3 mapping issue.:mike: Cisco Certifications -- Collect the Entire Set! -
qplayed Member Posts: 303
R1 interface Serial0/0 bandwidth 128 ip address 172.16.124.1 255.255.255.248 ip bandwidth-percent eigrp 1 40 ip hello-interval eigrp 1 5 ip hold-time eigrp 1 15 encapsulation frame-relay no ip split-horizon eigrp 1 ip summary-address eigrp 1 10.1.0.0 255.255.0.0 5 r2 interface Serial0/3 bandwidth 64 ip address 172.16.124.2 255.255.255.248 encapsulation frame-relay ip summary-address eigrp 1 10.2.0.0 255.255.0.0 5 r3 interface Serial0/0 bandwidth 64 ip address 172.16.124.3 255.255.255.248 encapsulation frame-relay ip summary-address eigrp 1 10.3.0.0 255.255.0.0 5
3640-R1_HQ#sh frame map Serial0/0 (up): ip 172.16.124.2 dlci 811(0x32B,0xC8B0), dynamic, broadcast,, status defined, active Serial0/0 (up): ip 172.16.124.3 dlci 102(0x66,0x1860), dynamic, broadcast,, status defined, active 3640-R2_EAST#sh fram map Serial0/3 (up): ip 172.16.124.1 dlci 800(0x320,0xC800), dynamic, broadcast,, status defined, active 3640-R3_WEST#sh frame map Serial0/0 (up): ip 172.16.124.1 dlci 201(0xC9,0x3090), dynamic, broadcast,, status defined, active
If you cannot express in a sentence or two what
you intend to get across, then it is not focused
well enough.
—Charles Osgood, TV commentator -
qplayed Member Posts: 303debug ip packet
does show an encapsulation failed messageMar 3 00:49:59.455: IP: tableid=0, s=172.16.124.3 (local), d=172.16.124.2 (Serial0/0), routed via RIB *Mar 3 00:49:59.459: IP: s=172.16.124.3 (local), d=172.16.124.2 (Serial0/0), len 100, sending *Mar 3 00:49:59.459: IP: s=172.16.124.3 (local), d=172.16.124.2 (Serial0/0), len 100, encapsulation failed *Mar 3 00:49:59.543: IP: s=10.3.1.1 (local), d=224.0.0.10 (Loopback1), len 60, sending broad/multicast *Mar 3 00:49:59.543: IP: s=10.3.1.1 (Loopback1), d=224.0.0.10, len 60, rcvd 2. *Mar 3 00:50:01.055: IP: s=10.3.33.1 (local), d=224.0.0.10 (Loopback33), len 60, sending broad/multicast *Mar 3 00:50:01.055: IP: s=10.3.33.1 (Loopback33), d=224.0.0.10, len 60, rcvd 2 *Mar 3 00:50:01.455: IP: tableid=0, s=172.16.124.3 (local), d=172.16.124.2 (Serial0/0), routed via RIB *Mar 3 00:50:01.455: IP: s=172.16.124.3 (local), d=172.16.124.2 (Serial0/0), len 100, sending *Mar 3 00:50:01.455: IP: s=172.16.124.3 (local), d=172.16.124.2 (Serial0/0), len 100, encapsulation failed
If you cannot express in a sentence or two what
you intend to get across, then it is not focused
well enough.
—Charles Osgood, TV commentator -
dtlokee Member Posts: 2,378 ■■■■□□□□□□Since you are using a hub and spoke network you will need to add static frame relay maps on the spoke routers since inverse arp cannot create a mapping to the remote spoke.The only easy day was yesterday!
-
qplayed Member Posts: 303dtlokee wrote:Since you are using a hub and spoke network you will need to add static frame relay maps on the spoke routers since inverse arp cannot create a mapping to the remote spoke.
thank you soo much!
i love this board!
this board will have my first child!If you cannot express in a sentence or two what
you intend to get across, then it is not focused
well enough.
—Charles Osgood, TV commentator -
qplayed Member Posts: 303ok...last question
was this something I should have known? if so, any suggested reading material?
or was this a simple oversight/mistake in my part?
thanks againIf you cannot express in a sentence or two what
you intend to get across, then it is not focused
well enough.
—Charles Osgood, TV commentator -
dtlokee Member Posts: 2,378 ■■■■□□□□□□It's covered in the CCNA to a degree, but it is not something most CCNA's would know to look at. When you were debugging and getting an "encapsulation failed" message that should lead you in the direction of a L2 framing issue possibly due to not having L2 information for the next hop. Also you should now realize that inverse arp only works when you have a fully meshed network. In other cases you will need to create static mappings on your multioint interfaces or create point to point interfaces as seperate subnets.The only easy day was yesterday!