From: Shamin (ccie.xpert@gmail.com)
Date: Sun Mar 04 2007 - 12:39:46 ART
Hi,
I tried that. But the point is, If split horizon is acting then R4's
loopback should not be seen by R5 as well. But R5 is able to ping R4's
loopback.
Any other thing that can be a issue?
regards
shamin
On 3/4/07, Darrin K. Pierce <darrin@dkpierce.com> wrote:
>
> Try disabling split-horizon on R3.
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Shamin
> Sent: Sunday, March 04, 2007 9:39 AM
> To: Cisco certification
> Subject: EIGRP over PPP over Frame - Problem
>
> Hi all,
>
> Hope your preparations are going good.
>
> I have a peculiar situation running EIGRP over PPPover Frame.
>
>
> R5 ---------- R3 -------------R4
>
>
> R3 is the hub and R4,R5 are the spokes. R3 & R4 are using main interfaces.
> R5 is using a point -to - point interface.
> The PPPoverFrame seems to be working. I can ping spoke to spoke . Now when
> i
> enable EIGRP , over this there is a problem that
> R4 is not receiving any Eigrp routes from R3 or R5. I configured Loopback
> 100 on R3 with Ip 3.3.3.3 and advertised it into eigrp.
> R5 seems to be receiving this route where as R4 is not.
> R5 is able to receive the Loopback of R4 where as R4 is not receiving the
> R5
> Loopback route.
>
> Can any one help reason why this is happening. The debug commands of eigrp
> is not very helpful in this. I dont think this is a split horizon issue as
> well.
>
> I will post the configuration on each router as below.
>
> ----------------------------------------------------------------------------
> ------------------------
>
> R3#
> username Rack1R4 password 0 CISCO
> username Rack1R5 password 0 CISCO
> !
> !
> !
> !
> interface Loopback100
> ip address 3.3.3.3 255.255.255.0
> !
> interface Serial2/0
> no ip address
> encapsulation frame-relay
> frame-relay interface-dlci 304 ppp Virtual-Template1
> frame-relay interface-dlci 305 ppp Virtual-Template1
>
> !
> interface Virtual-Template1
> ip address 158.1.0.3 255.255.255.0
> ppp authentication pap chap
> !
> router eigrp 10
> network 3.3.3.3 0.0.0.0
> network 158.1.0.3 0.0.0.0
> metric weights 0 1 1 1 0 0
> no auto-summary
> eigrp router-id 150.1.3.3
> !
>
> R3#sh ip route eigrp
> 4.0.0.0/24 is subnetted, 1 subnets
> D 4.4.4.0 [90/2713700] via 158.1.0.4, 00:22:26, Virtual-Access1
> 158.1.0.0/16 is variably subnetted, 11 subnets, 2 masks
> D 158.1.5.0/24 [90/2842603] via 158.1.0.5, 00:22:26, Virtual-Access2
> D 158.1.55.0/24 [90/2842603] via 158.1.0.5, 00:22:26,
> Virtual-Access2
> 150.1.0.0/16 is variably subnetted, 6 subnets, 2 masks
> D 150.1.5.0/24 [90/2713700] via 158.1.0.5, 00:22:26, Virtual-Access2
> D 150.1.4.0/24 [90/2713700] via 158.1.0.4, 00:22:26, Virtual-Access1
>
>
> ----------------------------------------------------------------------------
> --------------------------------------------------------
>
> R4#
> username Rack1R3 password 0 CISCO
> !
> !
> interface Loopback0
> ip address 150.1.4.4 255.255.255.0
> !
> interface Loopback100
> ip address 4.4.4.4 255.255.255.0
> !
> interface Serial0/0
> no ip address
> encapsulation frame-relay
> frame-relay interface-dlci 403 ppp Virtual-Template1
> !
> !
> interface Virtual-Template1
> ip address 158.1.0.4 255.255.255.0
> no peer neighbor-route
> !
> router eigrp 10
> network 4.4.4.4 0.0.0.0
> network 150.1.4.4 0.0.0.0
> network 158.1.0.4 0.0.0.0
> network 158.1.45.4 0.0.0.0
> metric weights 0 1 1 1 0 0
> no auto-summary
> eigrp router-id 150.1.4.4
> !
>
>
> R4#sh ip route
>
> Gateway of last resort is not set
>
> C 204.12.1.0/24 is directly connected, Ethernet0/1
> 4.0.0.0/24 is subnetted, 1 subnets
> C 4.4.4.0 is directly connected, Loopback100
> 158.1.0.0/24 is subnetted, 1 subnets
> C 158.1.0.0 is directly connected, Virtual-Access1
> C 192.10.1.0/24 is directly connected, Ethernet0/0
> 150.1.0.0/24 is subnetted, 1 subnets
> C 150.1.4.0 is directly connected, Loopback0
>
>
>
>
> ----------------------------------------------------------------------------
> ----------------------------------------
>
> R5#
> !
> !
> !
> interface Loopback0
> ip address 150.1.5.5 255.255.255.0
> !
> interface Ethernet0/0
> ip address 158.1.5.5 255.255.255.0
> half-duplex
> !
> interface Serial0/0
> no ip address
> encapsulation frame-relay
> !
> interface Serial0/0.1 point-to-point
> frame-relay interface-dlci 503 ppp Virtual-Template1
> !
> interface Ethernet0/1
> ip address 158.1.55.5 255.255.255.0
> half-duplex
> !
> interface Virtual-Template1
> ip address 158.1.0.5 255.255.255.0
> ppp chap password 0 CISCO
> !
> router eigrp 10
> network 150.1.5.5 0.0.0.0
> network 158.1.0.5 0.0.0.0
> network 158.1.5.5 0.0.0.0
> network 158.1.45.5 0.0.0.0
> network 158.1.55.5 0.0.0.0
> metric weights 0 1 1 1 0 0
> no auto-summary
> eigrp router-id 150.1.5.5
> !
>
> R5#sh ip route eigrp
> 3.0.0.0/24 is subnetted, 1 subnets
> D 3.3.3.0 [90/2713700] via 158.1.0.3, 00:36:01, Virtual-Access1
> 4.0.0.0/24 is subnetted, 1 subnets
> D 4.4.4.0 [90/5273700] via 158.1.0.3, 00:35:31, Virtual-Access1
> 158.1.0.0/16 is variably subnetted, 5 subnets, 2 masks
> D 158.1.0.4/32 [90/5145700] via 158.1.0.3, 00:54:44, Virtual-Access1
> 150.1.0.0/24 is subnetted, 2 subnets
> D 150.1.4.0 [90/5273700] via 158.1.0.3, 00:30:47, Virtual-Access1
>
> ----------------------------------------------------------------------------
> ----------------------------------------------
>
> Your help will be much appreciated. I dont see a reason why after forming
> an
> adjacency between R3 & R4 , the routes are only updated one way i.e from
> R4
> to R3 and R5 but not back.
>
> Regards
> Shameen
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Apr 01 2007 - 06:35:50 ART