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

451 Sign Ups in the last 30 days

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

Forum Replies

  1. Hi Rene,

    I’ve been waiting for your debugging, Thank you very much about this, that’s was very Interesting to me.
    Can you also do debugging about Flash Update Threshhold timer and Sleep Timer, please?

  2. If I have some spare time I’ll see if I can debug these two.

    The flash update threshold timer is apparently used to suppress the flash update (triggered update) when it’s X seconds within the scheduled routing update (which is sent every 30 seconds).

    The sleeptime is a funny one…it sets the delay in milliseconds how long we wait to send the scheduled routing update when a flash update is sent. I looked around for this and even though the RIP command supports it, it doesn’t seem to work.


  3. Brilliant as always, the Cisco docs are just confusing, thanks for this clarification.

  4. Awesome article. I have a question though: what happens if you change the timer for a router and not for others? While it’s better to have same timers; still, since no adjacency is needed to form, is it recommended if you change timer on one device only? I had seen such case where you have linux (unmanaged) router on one end and CISCO router at other and update timer being shortened in CISCO router only. Not sure about the consequences, then. Any thoughts?


  5. By unmanaged, I meant Linux router running RIP v2 but timers not changeable, at least on operational level.

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