From: Mike Stout (michaelgstout@gmail.com)
Date: Fri Dec 14 2007 - 14:34:25 ART
the slow link and fast link will establish neighbors, however , the slow
link will only send hello every 60 second.
Cent fast router expects dead time to be fulfilled in 15 seconds, the link
will be down for 45 seconds, and up for 15 seconds every minute.
This is a real world problem seen quite often by me. one router changes
bandwidth to slow link when it should be t1.
Another nice trick you may be able to reproduce is not send multicast on one
side. One side will go eigrp up, and other side will be eigrp neighbor not
up.
On Dec 14, 2007 7:09 AM, Steven Hodgson <steven.hodgson@inxi.com> wrote:
> They aren't required to form a neighbor relationship, but they can cause
> problems in the relationship staying up. If they are different enough,
> one router will be expecting to get hellos and never get them. It will
> think the neighbor is down. Then it will finally get a hello and it
> will bring the relationship back up. This will repeat ad nauseum.
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> vignesh sethuraman
> Sent: Friday, December 14, 2007 1:49 AM
> To: ccielab@groupstudy.com
> Subject: Hello Timers Mismatch
>
> Hello,
>
> I have connected 2 routers R1 and R2 using 2 serial links. I changed
> the default value of hello timers and hold timers in one of the
> interface only at R1 router. I thought neighborship will be down due to
> timers mismatch, but still it is up in both the interfaces.
>
> R1;
> interface Serial1/0
> ip address 155.1.0.5 255.255.255.0
> ip hello-interval eigrp 100 3
> ip hold-time eigrp 100 9
> encapsulation frame-relay
> frame-relay map ip 155.1.0.4 405 broadcast
> no frame-relay inverse-arp
> end
> interface Serial1/2
> ip address 155.1.45.5 255.255.255.0
> router eigrp 100
> network 155.1.0.5 0.0.0.0
> network 155.1.45.5 0.0.0.0
> network 155.2.0.5 0.0.0.0
> no auto-summary
>
>
> R2:
> interface Serial1/0
> ip address 155.1.0.4 255.255.255.0
> encapsulation frame-relay
> frame-relay map ip 155.1.0.5 504 broadcast
> no frame-relay inverse-arp
> end
> interface Serial1/2
> ip address 155.1.45.4 255.255.255.0
>
> router eigrp 100
> network 155.1.0.4 0.0.0.0
> network 155.1.45.4 0.0.0.0
> network 155.2.0.4 0.0.0.0
> no auto-summary
>
> R2#sh ip eigrp neighbors
> IP-EIGRP neighbors for process 100
> H Address Interface Hold Uptime SRTT RTO Q
> Seq
> (sec) (ms) Cnt
> Num
> 2 155.1.0.4 Se1/1 176 00:00:08 36 216 0
> 68
> 1 155.1.45.4 Se1/2 12 00:00:16 22 200 0
> 67
>
> R1#sh ip eigrp neighbors
> IP-EIGRP neighbors for process 100
> H Address Interface Hold Uptime SRTT RTO Q
> Seq
> (sec) (ms) Cnt
> Num
> 0 155.1.0.5 Se1/0 8 00:00:06 1 4500 2
> 0
> 1 155.1.45.5 Se1/2 14 00:00:04 36 1140 0
> 102
>
> Could you please explain why the neighborship is up on the mismatched
> interface.
>
> Thanks,
> Vignesh
>
>
>
> ---------------------------------
> Unlimited freedom, unlimited storage. Get it now
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
> IMPORTANT/CONFIDENTIAL: This message from INX Inc. is intended only for
> the use of the addressees shown above. It contains information that may be
> privileged, confidential and/or exempt from disclosure under applicable law.
> If you are not the intended recipient of this message, you are hereby
> notified that the copying, use or distribution of any information or
> materials transmitted in or with this message is strictly prohibited. If
> you received this message by mistake, please immediately email or call us
> collect at (469) 549-3800 and delete/destroy the original message.
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Tue Jan 01 2008 - 12:04:30 ARST