What is really bizarre is that I am down for minutes not seconds and the timers never fire. If I don't manually passive the connection eigrp will for some reason think there is a neighbor even though I am unable to source ping across the WAN. ----- Original Message ---- From: Matthew Huff <mhuff@ox.com> To: Philip Lavine <source_route@yahoo.com>; nanog <nanog@merit.edu> Sent: Tuesday, September 23, 2008 8:59:14 AM Subject: RE: eigrp and managed ethernet Correct. Eigrp neighbor connectivity has a short-cut when L2 connectivity goes down, otherwise it will use the eigrp neighbor hold-down timer. You can decrease that timer: interface fa0/0 ip hello-interval eigrp p x ip hold-time eigrp p y where p is your eigrp as-number, and x is how often you want the hello (in seconds) and y is the max hold-down timer. Generally y is = x * 3 http://www.cisco.com/en/US/docs/ios/12_2/iproute/command/reference/1rfeigrp.... ---- Matthew Huff | One Manhattanville Rd OTA Management LLC | Purchase, NY 10577 www.ox.com | Phone: 914-460-4039 aim: matthewbhuff | Fax: 914-460-4139 -----Original Message----- From: Philip Lavine [mailto:source_route@yahoo.com] Sent: Tuesday, September 23, 2008 11:43 AM To: nanog Subject: eigrp and managed ethernet For some reason when I lose layer 3 connectivity between two managed Ethernet sites EIGRP does not bounce.Is this because the physical interface does not bounce?
Are you 100% positive that the link is really not passing any traffic? Have you looked at interface stats to verify that there are no incoming packets? I'd suggest running some EIGRP debug commands during the outage to verify if you are really not getting any packets.. Philip Lavine <source_route@yahoo.com> 09/23/2008 09:25 AM To nanog <nanog@merit.edu> cc Subject Re: eigrp and managed ethernet What is really bizarre is that I am down for minutes not seconds and the timers never fire. If I don't manually passive the connection eigrp will for some reason think there is a neighbor even though I am unable to source ping across the WAN. ----- Original Message ---- From: Matthew Huff <mhuff@ox.com> To: Philip Lavine <source_route@yahoo.com>; nanog <nanog@merit.edu> Sent: Tuesday, September 23, 2008 8:59:14 AM Subject: RE: eigrp and managed ethernet Correct. Eigrp neighbor connectivity has a short-cut when L2 connectivity goes down, otherwise it will use the eigrp neighbor hold-down timer. You can decrease that timer: interface fa0/0 ip hello-interval eigrp p x ip hold-time eigrp p y where p is your eigrp as-number, and x is how often you want the hello (in seconds) and y is the max hold-down timer. Generally y is = x * 3 http://www.cisco.com/en/US/docs/ios/12_2/iproute/command/reference/1rfeigrp.... ---- Matthew Huff | One Manhattanville Rd OTA Management LLC | Purchase, NY 10577 www.ox.com | Phone: 914-460-4039 aim: matthewbhuff | Fax: 914-460-4139 -----Original Message----- From: Philip Lavine [mailto:source_route@yahoo.com] Sent: Tuesday, September 23, 2008 11:43 AM To: nanog Subject: eigrp and managed ethernet For some reason when I lose layer 3 connectivity between two managed Ethernet sites EIGRP does not bounce.Is this because the physical interface does not bounce?
The issue may be that only one direction of traffic is being impacted. So maybe your A end is receiving all the hellos, while the Z end is not. Therefore A still has Z as a neighbor, but Z doesn't have A as a neighbor. Brian Knoll -----Original Message----- From: Philip Lavine [mailto:source_route@yahoo.com] Sent: Tuesday, September 23, 2008 11:26 AM To: nanog Subject: Re: eigrp and managed ethernet What is really bizarre is that I am down for minutes not seconds and the timers never fire. If I don't manually passive the connection eigrp will for some reason think there is a neighbor even though I am unable to source ping across the WAN. ----- Original Message ---- From: Matthew Huff <mhuff@ox.com> To: Philip Lavine <source_route@yahoo.com>; nanog <nanog@merit.edu> Sent: Tuesday, September 23, 2008 8:59:14 AM Subject: RE: eigrp and managed ethernet Correct. Eigrp neighbor connectivity has a short-cut when L2 connectivity goes down, otherwise it will use the eigrp neighbor hold-down timer. You can decrease that timer: interface fa0/0 ip hello-interval eigrp p x ip hold-time eigrp p y where p is your eigrp as-number, and x is how often you want the hello (in seconds) and y is the max hold-down timer. Generally y is = x * 3 http://www.cisco.com/en/US/docs/ios/12_2/iproute/command/reference/1rfeigrp.... ---- Matthew Huff | One Manhattanville Rd OTA Management LLC | Purchase, NY 10577 www.ox.com | Phone: 914-460-4039 aim: matthewbhuff | Fax: 914-460-4139 -----Original Message----- From: Philip Lavine [mailto:source_route@yahoo.com] Sent: Tuesday, September 23, 2008 11:43 AM To: nanog Subject: eigrp and managed ethernet For some reason when I lose layer 3 connectivity between two managed Ethernet sites EIGRP does not bounce.Is this because the physical interface does not bounce?
Be sure to differentiate between unicast and multicast reachability. Try 'ping 224.0.0.10'. Stephen Kratzer On Tuesday 23 September 2008 12:25:34 Philip Lavine wrote:
What is really bizarre is that I am down for minutes not seconds and the timers never fire. If I don't manually passive the connection eigrp will for some reason think there is a neighbor even though I am unable to source ping across the WAN.
----- Original Message ---- From: Matthew Huff <mhuff@ox.com> To: Philip Lavine <source_route@yahoo.com>; nanog <nanog@merit.edu> Sent: Tuesday, September 23, 2008 8:59:14 AM Subject: RE: eigrp and managed ethernet
Correct. Eigrp neighbor connectivity has a short-cut when L2 connectivity goes down, otherwise it will use the eigrp neighbor hold-down timer. You can decrease that timer:
interface fa0/0 ip hello-interval eigrp p x ip hold-time eigrp p y
where p is your eigrp as-number, and x is how often you want the hello (in seconds) and y is the max hold-down timer. Generally y is = x * 3
http://www.cisco.com/en/US/docs/ios/12_2/iproute/command/reference/1rfeigrp .html
---- Matthew Huff | One Manhattanville Rd OTA Management LLC | Purchase, NY 10577 www.ox.com | Phone: 914-460-4039 aim: matthewbhuff | Fax: 914-460-4139
-----Original Message----- From: Philip Lavine [mailto:source_route@yahoo.com] Sent: Tuesday, September 23, 2008 11:43 AM To: nanog Subject: eigrp and managed ethernet
For some reason when I lose layer 3 connectivity between two managed Ethernet sites EIGRP does not bounce.Is this because the physical interface does not bounce?
You may want to check out BFD for EIGRP, http://www.cisco.com/en/US/technologies/tk648/tk365/tk207/technologies_white... Regards, Kevin On Tue, Sep 23, 2008 at 11:25 AM, Philip Lavine <source_route@yahoo.com> wrote:
What is really bizarre is that I am down for minutes not seconds and the timers never fire. If I don't manually passive the connection eigrp will for some reason think there is a neighbor even though I am unable to source ping across the WAN.
----- Original Message ---- From: Matthew Huff <mhuff@ox.com> To: Philip Lavine <source_route@yahoo.com>; nanog <nanog@merit.edu> Sent: Tuesday, September 23, 2008 8:59:14 AM Subject: RE: eigrp and managed ethernet
Correct. Eigrp neighbor connectivity has a short-cut when L2 connectivity goes down, otherwise it will use the eigrp neighbor hold-down timer. You can decrease that timer:
interface fa0/0 ip hello-interval eigrp p x ip hold-time eigrp p y
where p is your eigrp as-number, and x is how often you want the hello (in seconds) and y is the max hold-down timer. Generally y is = x * 3
http://www.cisco.com/en/US/docs/ios/12_2/iproute/command/reference/1rfeigrp....
---- Matthew Huff | One Manhattanville Rd OTA Management LLC | Purchase, NY 10577 www.ox.com | Phone: 914-460-4039 aim: matthewbhuff | Fax: 914-460-4139
-----Original Message----- From: Philip Lavine [mailto:source_route@yahoo.com] Sent: Tuesday, September 23, 2008 11:43 AM To: nanog Subject: eigrp and managed ethernet
For some reason when I lose layer 3 connectivity between two managed Ethernet sites EIGRP does not bounce.Is this because the physical interface does not bounce?
participants (5)
-
Brian Knoll
-
Jeremy_Lunsford@playstation.sony.com
-
Kevin Hodle
-
Philip Lavine
-
Stephen Kratzer