We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 642 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

488 Sign Ups in the last 30 days

100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Tags: ,

Forum Replies

  1. Oliver,
    You are correct. There is an Attempt state, and you would only see it under the following conditions:

      Your router is an NMBA environment
      You have manually configured a neighbor
      The router has sent a unicast Hello to a neighbor
      The dead timer for that neighbor has not yet expired


  2. Kishor,
    I assume you mean the “ExStart” or “Exchange” state, so I will write about those. If OSPF is having an authentication problem, you will not see the routers stuck in ExStart or Exchange. In fact, you won’t see anything at all. The output for “show ip ospf neighbors” will just be blank (if a neighbor relationship hadn’t already formed). If a neighbor relationship already formed, and then an authentication problem is introduced, the neighbors will just drop once the dead interval is reached. The reason, in both cases, is because if there is an authent

    ... Continue reading in our forum

  3. very good explanation thanks!

  4. Hello Laz,

    Well explained, let me do the labbing for the same topology.
    Thanks alot.


55 more replies! Ask a question or join the discussion by visiting our Community Forum