ODR and CDP Timers

From: gladston@br.ibm.com
Date: Wed Aug 10 2005 - 10:00:36 GMT-3


Hi,

Trying to understand this statement from Cisco:

===============================
Configuration changes made to either the CDP or ODR timers should be reflected
through changes made to both.
===============================

If I change global CDP timers on R2, it will affect all other interfaces. As it is not desired on this scenario, for a test I just changed CDP timers on spoke - R8 - and changed timers basic under router odr on the hub - R2.

Tests shows it works fine, but I am wondering if there are drawnbacks. What do you think?

Tests Done:

Using default odr/cdr timers it takes almost 2 minutes to flush the route.

R8(config)#int lo 88
R8(config-if)#sh
09:32:20.136 PST Wed Aug 10 2005

Rack2R2
09:34:50: RT: flushed route to 148.5.88.0 via 148.5.28.8 (Serial0/0.28)

Changing the global CDP timers on R2 and timers basic under ODR results in flush within few seconds:

R2

Serial0/0.28 is up, line protocol is up
  Encapsulation FRAME-RELAY
  Sending CDP packets every 60 seconds
  Holdtime is 180 seconds

router odr
 timers basic 5 8 15 20

R8
R8#sh cdp int ser 0.82
Serial0.82 is up, line protocol is up
  Encapsulation FRAME-RELAY
  Sending CDP packets every 5 seconds
  Holdtime is 15 seconds

Rack2R2(config-router)#do sir od
o 148.5.88.0/24 [160/1] via 148.5.28.8, 00:00:02, Serial0/0.28

Rack2R2(config-router)#do sh clock
09:47:54.844 PST Wed Aug 10 2005

R8(config)#int lo 88
R8(config-if)#sh

Rack2R2
Aug 10 09:47:55: RT: flushed route to 148.5.88.0 via 148.5.28.8 (Serial0/0.28)
Aug 10 09:47:55: RT: no routes to 148.5.88.0
Aug 10 09:47:55: RT: NET-RED 148.5.88.0/24



This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:01:19 GMT-3