User`s guide

XSR User’s Guide 77
Chapter 5 IP Routing Protocols
Configuring IP
 Redistribute static routes into RIP with the redistribute command.
 Split horizon with poisoned reverse enabled with the
ip split-
horizon
command.
 Triggered updates delivered by default or disabled by the
ip rip
disable-triggered-updates
command.
 Clear text authentication enabled by the
ip rip authentication
mode
command.
NOTE
RIP commands configured under Interface mode are independent of
enabling/disabling the RIP protocol.
 RIP is configurable for:
–
Send only is set by issuing the no received interface command
to prevent RIP from receiving update packets on a specified port.
– Receive only is set by issuing the
passive interface command
to prevent RIP from sending update packets on a specified port.
 Offset metric parameters - route metrics via RIP. Adding an offset to
an interface makes it a backup
 Route filtering, in association with access lists, is enabled by the
distribute-list
command.
 A number of statistical display commands revealing RIP counters
including
show ip traffic, show ip route, show ip protocols.
Triggered-on-Demand RIP
Triggered-on-demand RIP (defined in RFC-2091) is available for sending
routing updates on a PPP serial (WAN) port only. This feature updates the
XSR’s RIP routing table only when the topology changes or when a next hop’s
reachability is detected on the WAN side of the link.
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. The following conditions govern the feature’s use:
 RIP must be enabled.