Jay, the Frame-relay interface of R2 interface and one of R5 or R6 fastethernet's goes down, you should have full connectivity.
From: mohd-mousa_at_hotmail.com
To: jay.mcmickle_at_yahoo.com
CC: ccielab_at_groupstudy.com
Subject: RE:
Date: Thu, 5 Jul 2012 15:18:46 +0000
Hi Jay,
EIGRP
Topology is R1-------------R2 --------------------------------R4,R5,R6
ospf | full meshed frame-relay
| | RIP |-------here is back2back point-to-point | R5-----------------R6 \ / \ / ---------------------here between R5,R6,R7 fastethernet running ospf R7 / | |-----------here another ospf R8 This is the topology, its from IPexpert WB2 VOL2, the question said even if the interface serial is down (FRAM interface),and one of R5 or R6 fastethernets's goes down, you should have full connectivity!!! Jay, I used debug ip routing on Router2,R5,R6 while i did the redistribution but, didn't find anything wro!
ng. Sorry, for this ugly drawing :oo)) Any feedback from you, it will be helpful for me ! Thanks alot > CC: ccielab_at_groupstudy.com
> From: jay.mcmickle_at_yahoo.com
> Subject: Re:
> Date: Thu, 5 Jul 2012 07:29:41 -0500
> To: mohd-mousa_at_hotmail.com
>
> We need long and boring to understand, or at least a topology.
>
> Debug ip routing only works and helpful with dynamic protocols and sometimes provides helpful output but mostly during a clear ip route *.
>
> There are too any factors here like static routing, ZBFW, QoS, etc.
>
> My suggestion without what is between R4 and R2 is to source a ping in the direction it's not working, to each hop and see where it stops. Maybe I e way it's following a default route, but the opposite way it doesn't have a return route.
>
> Regards,
> Jay McMickle- CCIE #35355 (R&S)
> Sent from iJay
>
> On Jul 5, 2012, at 7:03 AM, <mohd-mousa_at_hotmail.com> wrote:
>
> > Hi Folks.
> >
> > I have strange behaivor while I was labbing today,when i tried to ping
> > from R2 lo0 to router R4 fas0/0 ( there is multiple redis between them )
> > the ping doesn't happen, but when i did the ping from f0/0 of R4 to R2 lo0
> > the pinging was fine..
> >
> >
> > I tried to trace and debug ip icmp, the result showed that R4 received the
> > packet and stopped there,
> >
> > This is the output :
> >
> > ICMP: time exceeded (time to live) sent to 10.10.10.5 (dest was 10.10.10.6)
> > time exceeded (time to live) sent to 10.10.10.5 (dest was 10.10.10.6)
> > time exceeded (time to live) sent to 10.10.10.2 (dest was 216.100.1.6)
> > ICMP: time exceeded (time to live) sent to 10.10.10.2 (dest was 216.100.1.6)
> > ICMP: time exceeded (time to live) sent to 10.10.10.4 (dest was 10.10.10.6)
> > ICMP: time exceeded (time to live) sent to 10.10.10.2 (dest was 216.30.100.5)
> > ICMP: time exceeded (time to live) sent to 10.10.10.2 (dest was 216.30.100.5)
> > ICMP: time exceeded (time to live) sent to 10.10.10.2 (dest was 216.30.100.5)
> >
> > Guys,my console was hangging from the output, could any one tell me
> > whats the meaning of this output ?
> >
> > could this relate to routing loops, i turned debug ip routing but didn't see
> > route flapping ?
> >
> >
> > I made multiple redistribution but not on this router!!!
> > any additional configration will be happy to provide, but i don't want to make
> > my post long and boring.
> >
> >
> >
> > Thanks in advance.
> >
> >
> > 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
Received on Thu Jul 05 2012 - 15:21:00 ART
This archive was generated by hypermail 2.2.0 : Wed Aug 01 2012 - 15:55:23 ART