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 581 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

 

295 New Members signed up the last 30 days!

satisfaction-guaranteed

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

Tags: ,


Forum Replies

  1. thanks again for this clarification much appreciated :slight_smile:

    need to look into this as we are getting a lot of MaxAge Lsa approx ever hour or more.

  2. Hi Rene,

    Get it. I try to shutdown the ABR which will advertised the LSA 3 to the neighbor, then the neighbor still have a valid LSA in the database although the route no longer in the RIB.

    So it will auto flood after 30 minutes and and then the not valid LSA will be remove i think.

    Thanks for you explanation

    Davis

  3. Hi Rene,

    Ok. Thanks :slight_smile:

    Davis

  4. Hi Pradeep,

    Without the MTU check, some strange things can happen.

    OSPF hello packets are very small so interfaces with a small MTU don't have any issues receiving it. This allows routers to form an OSPF neighbor adjacency.

    Updates however, can be quite large. It's possible that an OSPF router sends a packet that exceeds the MTU of the interface of the receiving router. The two routers will be neighbors but the update never makes it to the other end.

    To prevent something like this from happening, it's better to check the MTU of two OSPF neighbors.

    Rene

  5. Hi Rene,

    You can see that the LSA has been updated 2 times since the sequence number is 0x80000002.

    Don't you mean that it has been updated only once since we start at 0x80000001 ?
    Correct me if I am wrong !

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