Re: EIGRP problem

From: Atlanta CCIE (atlantaccie@gmail.com)
Date: Tue Sep 02 2008 - 07:09:19 ART


Your frame-relay map statements don't look right. Have you confirmed layer2
connectivity? According to R1's config it appears that R2 is the hub router
on this frame-relay network however looking at R3's config it's showing
totally different DLCIs.
****R1****R1****R1****R1

interface Loopback2
 ip address 150.101.1.1 255.255.255.0
!
interface Serial0/1/0
 bandwidth 1544
 ip address 120.100.123.1 255.255.255.0
 ip hold-time eigrp 1 200
 encapsulation frame-relay
 frame-relay map ip 120.100.123.2 102 broadcast
 frame-relay map ip 120.100.123.3 102 broadcast
 no frame-relay inverse-arp
 frame-relay lmi-type cisco

****R3****R3****R3****R3

interface Serial1/3
 bandwidth 1544
 ip address 120.100.123.3 255.255.255.0
 ip hold-time eigrp 1 200
 encapsulation frame-relay
 frame-relay map ip 120.100.123.1 201 broadcast
 frame-relay map ip 120.100.123.2 203 broadcast
 no frame-relay inverse-arp

On Mon, Sep 1, 2008 at 12:16 PM, CCIE3000 <ccie3000@googlemail.com> wrote:

> Hi Guys,
>
> Okay, where am I going wrong as this one is driving me nuts!!
>
> Loopback on R1 redistributed into eigrp 1.
> R1 and R3 are eigrp neighbours across the frame-relay.
>
> From debugs I can see that 150.101.1.0/24 gets sent to R3 and R3 receives
> it
> but it doesn't get put into the
> routing table??? Why?? R3 doesn't have any other routes for
> 150.101.1.0coming in from anywhere else.
>
> I'm getting the following from debug ip eigrp on R3
>
> *Sep 1 15:59:58.287: IP-EIGRP(Default-IP-Routing-Table:1): ExtS
> 150.101.1.0/24 M 2560512256 - 2560000000 512256 SM 2560000256 - 2560000000
> 256
>
> Any ideas why R3 doesn't install the route??
>
> ****R1****R1****R1****R1
>
> interface Loopback2
> ip address 150.101.1.1 255.255.255.0
> !
> interface Serial0/1/0
> bandwidth 1544
> ip address 120.100.123.1 255.255.255.0
> ip hold-time eigrp 1 200
> encapsulation frame-relay
> frame-relay map ip 120.100.123.2 102 broadcast
> frame-relay map ip 120.100.123.3 102 broadcast
> no frame-relay inverse-arp
> frame-relay lmi-type cisco
> !
> router eigrp 1
> redistribute connected metric 1 1 1 1 1 route-map EIGRP>CON
> network 120.100.1.1 0.0.0.0
> network 120.100.100.1 0.0.0.0
> network 120.100.123.1 0.0.0.0
> no auto-summary
> !
> route-map EIGRP>CON permit 10
> match interface Loopback2
>
>
> ****R3****R3****R3****R3
>
> interface Serial1/3
> bandwidth 1544
> ip address 120.100.123.3 255.255.255.0
> ip hold-time eigrp 1 200
> encapsulation frame-relay
> frame-relay map ip 120.100.123.1 201 broadcast
> frame-relay map ip 120.100.123.2 203 broadcast
> no frame-relay inverse-arp
> !
> router eigrp 1
> network 120.100.3.1 0.0.0.0
> network 120.100.34.3 0.0.0.0
> network 120.100.123.3 0.0.0.0
> no auto-summary
>
> Routing table of R3
>
> Gateway of last resort is not set
> C 200.200.200.0/24 is directly connected, Loopback255
> D 204.12.1.0/24 [90/2172416] via 120.100.123.2, 00:13:00, Serial1/3
> 120.0.0.0/24 is subnetted, 8 subnets
> D 120.100.4.0 [90/156160] via 120.100.34.4, 00:13:04,
> FastEthernet0/0
> D 120.100.5.0 [90/156160] via 120.100.34.5, 00:13:06,
> FastEthernet0/0
> D 120.100.1.0 [90/2297856] via 120.100.123.1, 00:13:00, Serial1/3
> D 120.100.2.0 [90/2297856] via 120.100.123.2, 00:13:00, Serial1/3
> C 120.100.3.0 is directly connected, Loopback0
> C 120.100.34.0 is directly connected, FastEthernet0/0
> C 120.100.123.0 is directly connected, Serial1/3
> D 120.100.100.0 [90/2172416] via 120.100.123.1, 00:13:01, Serial1/3
>
> Many Thanks,
>
> Si
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net



This archive was generated by hypermail 2.1.4 : Sat Oct 04 2008 - 09:26:17 ART