From: Brian Dennis (bdennis@internetworkexpert.com)
Date: Thu Jul 06 2006 - 13:11:49 ART
Think about it like this. If you run RIP triggered across a P2P serial
link and the remote end goes down, your local interface should also go
down. This will allow your local router to detect that the remote
router's routes should be removed from the routing table. Now if it's a
multipoint interface like Ethernet (more than one endpoint possible)
then if the remote router goes down, the Ethernet interface will not
normally go down assuming a hub or switch is being used. This means
that even though the remote router is down, its routes will not be
removed from your local router's routing table since you are not
expecting periodic updates and you can not determine based on the
interface state if the remote router is down.
HTH,
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
Sami
Sent: Thursday, July 06, 2006 4:56 AM
To: ccielab@groupstudy.com
Subject: RIP triggered
Group,
ip rip triggered command is not under ethernet interface ? is there any
speific reason for not having it ?
R4(config)#int fastEthernet 0/0
R4(config-if)#ip rip ?
advertise Specify update interval
authentication Authentication control
receive advertisement reception
send advertisement transmission
v2-broadcast send ip broadcast v2 update
R4(config)#int s0/0/0
R4(config-if)#ip rip ?
advertise Specify update interval
authentication Authentication control
receive advertisement reception
send advertisement transmission
triggered enable rfc2091 triggered rip
v2-broadcast send ip broadcast v2 update
This archive was generated by hypermail 2.1.4 : Tue Aug 01 2006 - 07:13:46 ART