Network Engineering Stack Exchange is a question and answer site for network engineers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The DOWN state of an OSPF neighbor is defined as a state when no hellos are seen in the last routerdeadinteraval time. The INIT state of an OSPF neighbor is defined as state attained when the first hellos are heard in interval.

So for the transition from DOWN to INIT, a hello must be heard on the down interface.

But contradicting this, Jeff Doyle insists that hellos are not sent to down interfaces on broadcast networks. The exception is NBMA, which will send hellos in polltimeinteraval.

This is confusing. If down interfaces are not sent a hello, how can they hear hellos and transform to INIT on broadcast multiaccess networks?

share|improve this question

closed as unclear what you're asking by Mike Pennington Mar 18 '14 at 20:48

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question.If this question can be reworded to fit the rules in the help center, please edit the question.

Please give an exact quote including book, chapter and page, because it's impossible to respond to this concern without assuming that you are quoting the source correctly – Mike Pennington Mar 18 '14 at 20:47
@MikePennington The exact quote is "Hellos are not sent to dead neighbors except on NBMA networks, where Hellos are sent to dead neighbors at some rate well below that of the Hello interval." From "OSPF and IS-IS: Choosing an IGP for Large Scale Networks," Doyle, 2006, Ch 6, page 190. – Ron Trunk Mar 19 '14 at 11:55
@Ron thanks much for quotting the text and explanation – Downey_HUff Mar 19 '14 at 14:40
The quote is inadequate. We need paragraphs, not a bare sentence. Downey, this is your question; it's your responsibility to explain what you're asking about. Three paragraphs of relevant context please. – Mike Pennington Mar 20 '14 at 0:02
Sorry mike do you really need more info than @ron gave?? Y this has to be not so user friendly , one of questions marked as locked, user given no option to explain himself. Sorry if i have been harsh..please lock this if you want., if this is not a site for newbies let it be – Downey_HUff Mar 20 '14 at 5:00
up vote 4 down vote accepted

I'm very reluctant to criticize someone like Jeff Doyle, but I'm reading that very same paragraph you mention, and I think he could have chosen his words better.

Remember that an OSPF router maintains the state of each its neighbors from its own point of view. So from R1's point of view, R2 transitions to INIT when R1 hears a hello from R2, not when R1 sends a hello to R2.

Quoting from RFC 2328:

On broadcast networks, each router advertises itself by periodically multicasting Hello Packets. This allows neighbors to be discovered dynamically.

So even if R1's neighbor is down, R1 is still sending hellos on that broadcast network.

Here's an example from GNS3:

*Mar 18 14:36:55.615: %OSPF-5-ADJCHG: Process 1, Nbr on Ethernet1/1 from FULL to DOWN, Neighbor Down: Dead timer expired
R1#debug ip ospf hello
OSPF hello events debugging is on
*Mar 18 14:37:53.255: OSPF: Rcv hello from area 0 from Ethernet1/1
*Mar 18 14:37:53.255: OSPF: Mismatched hello parameters from
*Mar 18 14:37:53.259: OSPF: Dead R 48 C 40, Hello R 12 C 10  Mask R C
*Mar 18 14:37:55.603: OSPF: Send hello to area 0 on Ethernet1/0 from
*Mar 18 14:37:55.607: OSPF: Send hello to area 0 on Ethernet1/1 from
*Mar 18 14:37:55.715: OSPF: Rcv hello from area 0 from Ethernet1/0
*Mar 18 14:37:55.719: OSPF: End of hello processing

As you can see, even though R1's neighbor is down (due to hello timer mismatch), R1 is still sending hellos on that interface.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.