From: Cameron, John (johcamer@cisco.com)
Date: Wed Jun 25 2003 - 18:46:19 GMT-3
James,
Well the VLSM part doesn't matter but you are correct that snapshot
routing is only for DV like protocols - from the config guide:
The following routed protocols support snapshot routing. Note that these are
all distance-vector protocols.
AppleTalk-Routing Table Maintenance Protocol (RTMP)
Banyan VINES-Routing Table Protocol (RTP)
IP-Routing Information Protocol (RIP),
Interior Gateway Routing Protocol (IGRP),
Internet Protocol Exchange (IPX)-RIP,
Service Advertisement Protocol (SAP)
As far as "ip rip triggered" I agree it sounds a bunch like a ospf
demand-circuit - from the config guide:
To overcome these limitations, triggered extensions to RIP cause RIP to send
information on the WAN only when there has been an update to the routing
database. Periodic update packets are suppressed over the interface on which
this feature is enabled. RIP routing traffic is reduced on point-to-point,
serial interfaces. Therefore, you can save money on an on-demand circuit for
which you are charged for usage. Triggered extensions to RIP partially
support RFC 2091, Triggered Extensions to RIP to Support Demand Circuits.
HTH,
JDC
-----Original Message-----
From: James.Jackson@broadwing.com [mailto:James.Jackson@broadwing.com]
Sent: Tuesday, June 24, 2003 3:03 PM
To: ccielab@groupstudy.com
Subject: RIP - triggered updates vs. snapshot routing ?
Is it correct to say that Snapshot Routing would only be used for non-VLSM
DV protocols i.e. RIPv1, IGRP etc ? Also, can RIP triggered updates be used
in a similar fashion as OSPF demand-circuit, but for RIPv1 and RIPv2 ?
Thanks,
James
+++The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and destroy any copies of this
document.+++
This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:11:09 GMT-3