RE: ip rip triggered

From: Brian Dennis (bdennis@internetworkexpert.com)
Date: Tue Mar 08 2005 - 01:07:58 GMT-3


If RIP triggered is not configured on both sides, how would the other
side (without the command applied) know that it should suppress periodic
updates?

Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)

bdennis@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
ccie2be
Sent: Monday, March 07, 2005 7:19 PM
To: 'Matt White'; 'Group Study'
Subject: RE: ip rip triggered

Matt,

You should think of ip rip triggered as rip's version of ospf's demand
circuit.

It's designed to keep traffic off of wan circuits unless there's a
topology
change.

I think it should be configured on both sides of a link, but I'm not
100%
sure about that.

HTH, Tim

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Matt
White
Sent: Monday, March 07, 2005 10:09 PM
To: Group Study
Subject: ip rip triggered

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