RE: RIP v2 SLEEP TIMERS

Hi Shogo,

Thanks for your input.

Kind Regards

Pierre-Alex

From: Shogo Kobayashi [mailto:k.shogo_at_gmail.com]
Sent: Sunday, June 20, 2010 3:04 PM
To: Pierre-Alex GUANEL
Cc: ccielab_at_groupstudy.com
Subject: Re: RIP v2 SLEEP TIMERS

Pierrea,

I labbed it up, and yet same issue happens.

It seems not working at all.
And I searched for IOS Bug, but of course there's no issues like this.

Sleeptimer is mentioned in link below, but there's no posting yet.
http://blog.ine.com/2010/04/15/how-basic-are-rip-timers-test-your-knowledge-
now/

Maybe we have to hope there's no sleeptimer related questions in real lab.

regards,

Shogo Kobayashi

On 2010/06/20 19:03, Pierre-Alex GUANEL wrote:

Just one last thing. I don't think that this timer corresponds to anything
specified in RFC 2453.

See page 29 on the relationship between triggered updates and regular
updates.

http://tools.ietf.org/html/rfc2453#page-29

Could it be that this command is available simply out of programming
"laziness" or practicality ...?

I.e. the command was implemented for IGRP but it was too much work to
re-write for RIP and remove the "sleeptime" option ... ?

That is the best reason I can think of ...

Thanks and Regards

Pierre-Alex

From: Pierre-Alex GUANEL [xxxxxxxx_at_gmail.com]
Sent: Sunday, June 20, 2010 11:46 AM
To: xxxxxxxxx_at_gmail.com'
Cc: 'ccielab_at_groupstudy.com'
Subject: RE: RIP v2 SLEEP TIMERS

Hi Shogo,

I repeated the test after having correcting the configuration.

"timers basic 30 180 240 30000"

The feature still does not seem to be working.

============= Diagram ================

R1-(Eth3/0)---------(Eth3/0)-R2

============ configuration ===========

! R1

router rip

 version 2

 timers basic 30 180 240 30000

 passive-interface default

 no passive-interface Ethernet3/0

 network 10.0.0.0

 no auto-summary

! R2

router rip

 version 2

 timers basic 30 180 240 30000

 passive-interface default

 no passive-interface Ethernet3/0

 network 10.0.0.0

 no auto-summary

============ debug =====================

! Regular update 1

000387: *Jun 20 08:56:29.557: RIP: sending v2 update to 224.0.0.9 via
Ethernet3/0 (10.12.0.1)

000388: *Jun 20 08:56:29.561: RIP: build update entries

000389: *Jun 20 08:56:29.561: 10.255.255.1/32 via 0.0.0.0, metric 1, tag 0

! Flash update

000396: *Jun 20 08:56:49.929: %LINK-3-UPDOWN: Interface Loopback1, changed
state to up

000397: *Jun 20 08:56:49.945: RIP: sending v2 flash update to 224.0.0.9 via
Ethernet3/0 (10.12.0.1)

000398: *Jun 20 08:56:49.945: RIP: build flash update entries

000399: *Jun 20 08:56:49.945: 10.255.255.11/32 via 0.0.0.0, metric 1, tag
0

! Regular update 2

000403: *Jun 20 08:56:56.201: RIP: sending v2 update to 224.0.0.9 via
Ethernet3/0 (10.12.0.1)

000404: *Jun 20 08:56:56.201: RIP: build update entries

000405: *Jun 20 08:56:56.201: 10.255.255.1/32 via 0.0.0.0, metric 1, tag 0

000406: *Jun 20 08:56:56.201: 10.255.255.11/32 via 0.0.0.0, metric 1, tag
0

========= Interpretation ===============

Regular update 2 should have been postponed to about 08:57:09.

Instead it falls within 30 seconds (+- 5 seconds) from Regular update 1

Thanks

Pierre-Alex

Blogs and organic groups at http://www.ccie.net
Received on Sun Jun 20 2010 - 18:53:08 ART