Remote Neighbors - Juniper IGP - CONFIGURATION GUIDE V11.1.X Configuration Manual

JUNOSe 11.0.x IP, IPv6, and IGP Configuration Guide

Remote Neighbors

You can create RIP remote neighbors to enable the router to establish neighbor
adjacencies through unidirectional interfaces, such as MPLS tunnels, rather than the
standard practice of using the same interface for receipt and transmission of RIP
packets. The remote neighbor can be more than one hop away through intermediate
routes that are not running RIP. RIP uses the interface associated with the best route
to the remote neighbor to reach the neighbor. A best route to the neighbor must
exist in the IP routing table.
You must explicitly configure remote neighbors on the RIP routers to specify the
remote neighbor with which the router will form an adjacency and the source IP
address the router will use for RIP packets destined to its peer remote neighbor.
To form an adjacency with its remote neighbor, the router sends all RIP packets to
the remote neighbor as unicast packets with the destination IP address equal to the
source IP address of the remote neighbor. The loopback interface associated with
the source IP address for the remote neighbor acts as a logical RIP interface for the
neighbor.
To prevent routing loops, you can disable split horizon and enable poison reverse
routing updates.
The remote-neighbor command to specify the remote neighbors is mandatory.
Configuration of all other remote-neighbor attributes is optional.
226
Remote Neighbors
You can use the minimum-interval keyword to specify the same value for
both of those intervals. Configuring a minimum interval has the same effect
as configuring the minimum receive interval and the minimum transmit
interval to the same value. The default value is 300 milliseconds.
You can use the multiplier keyword to specify the detection multiplier value.
The calculated BFD liveness detection interval can be different on each peer.
The multiplier value is roughly equivalent to the number of packets that can be
missed before the BFD session is declared to be down. The default value is 3.
For details on liveness detection negotiation, see JUNOSe IP Services Configuration
Guide .
You can change the BFD liveness detection parameters at any time without
stopping or restarting the existing session; BFD automatically adjusts to the new
parameter value. However, no changes to BFD parameters take place until the
values resynchronize with each peer.
Example
host1(config-if)#ip rip bfd-liveness-detection minimum-interval 800
or
host1(config-router)#address bfd-liveness-detection minimum-interval 800
Use the no version to disable BFD on the RIP interface.
See address bfd-liveness-detection
See ip rip bfd-liveness-detection