From: Matt White (mwhite23@gmail.com)
Date: Tue Mar 08 2005 - 00:08:44 GMT-3
By default, RIP timers are set to 30 180 180 240. However, when using
"ip rip triggered", the timers change to 30 180 0 240.
Cisco states that all routers in a RIP "autonomous system" should have
identical timers configured. Does this mean that if you use IP RIP
TRIGGERED you should hard-code all routers the the former, or all
routers to the latter?
Thank you again for your insight.
!
!Before IP RIP TRIGGERED
!
Routing Protocol is "rip"
Sending updates every 30 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: rip
Default version control: send version 2, receive version 2
Interface Send Recv Triggered RIP Key-chain
Serial0/0.666 2 2
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
192.168.1.0
Passive Interface(s):
VoIP-Null0
Serial0/0
FastEthernet1/0
Serial1/0
FastEthernet1/1
Serial1/1
Virtual-Access1
Ethernet0/0
Routing Information Sources:
Gateway Distance Last Update
Distance: (default is 120)
!
!After IP RIP TRIGGERED
!
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 18 seconds
Invalid after 180 seconds, hold down 0, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: rip
Default version control: send version 2, receive version 2
Interface Send Recv Triggered RIP Key-chain
Serial0/0.666 2 2 Yes
Automatic network summarization is not in effect
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:42 GMT-3