Table of Contents
Advertisement
Triggered on Demand RIP Commands
Syntax of the "no" Form
The no command resets maximum retransmissions to the default:
no ip rip polling interval
Mode
Interface configuration:
Default
30 seconds
Example
The following example sets the polling interval to 120 seconds:
XSR(config)#interface serial 1/0
XSR(config-if<S1/0>)#ip address 1.0.0.0 255.0.0.0
XSR(config-if<S1/0>)#no shutdown
XSR(config-if<S1/0>)#ip rip triggered-on-demand
XSR(config-if<S1/0>)#ip rip polling-interval 120
XSR(config)#router rip
XSR(config-router)#network 1.0.0.0
ip rip triggered-on-demand
This command enables triggered‐on‐demand RIP on the specified interface. It is available on a
point‐to‐point Serial (WAN) interface only.
On‐demand RIP permits the update of an XSR's RIP routing table only when the database changes
or when a next hop's reachability is detected on the WAN side of the connection. This
functionality reduces the on‐demand WAN circuit's routing traffic and allows the link to be
brought down when application traffic ceases. Regular RIP updates would prevent the connection
from being torn down when application use ends.
On‐demand RIP is available under conditions where the route is learned through a dialer or dialer
backup connection and a dial on demand link.
The following conditions govern the command's use:
•
RIP must be enabled.
•
IP split horizon must be enabled (default). Whether poison is enabled or not, triggered on
demand will still send its updates with poison.
Another command
updates enabled), invokes triggered updates in a timely fashion as described by RFCs‐1058 and
2453 (RIP and RIPv2 protocol) and does not tear down the connection. The two features work
independent of each other.
Syntax
ip rip triggered-on-demand
5-144 Configuring the Internet Protocol
XSR(config-if<xx>)#
, ip rip disable-triggered-updates
, with the default enforced (triggered
Advertisement
Table of Contents
