JunosE 11.3.x IP, IPv6, and IGP Configuration Guide
32
routing table even if the specified BFD operation is currently unreachable, provided
that no other static route to the same network prefix is available.
Change 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 BFD peer.
Example 1—Next hop address and last resort
host1(config)#ip route 192.56.15.23 255.255.255.0 192.66.0.1 verify
bfd-liveness-detection minimum-interval 800 multiplier 2 last-resort
Example 2—Next hop address and interface
host1(config)#ip route 192.56.15.24 255.255.255.0 192.66.0.2 fast 6/0 verify
bfd-liveness-detection
Example 3—Next hop address with different receive and transmit intervals
host1(config)#ip route 192.56.15.23 255.255.255.0 192.66.0.1 verify
bfd-liveness-detection minimum-receive-interval 800 minimum-transmit-interval
300 multiplier 2 last-resort
Use the no version to remove the static route from the routing table and thereby remove
BFD from that static route.
See ip route
How RTR Next-Hop Verification Works
Static routes on E Series routers can use Response Time Reporter (RTR) probes configured
as echo (ping) types to verify the availability of the next hop and obtain the state of the
IP service. For more information about using RTR, see "Response Time Reporter" on
page 62.
If you specify the verify rtr keywords with an RTR operation number when you issue the
ip route command to establish a static route, the router verifies the next-hop status and
installs the static route in the routing table only if both of the following conditions are
met:
The next hop to the specified IP destination address is resolved.
The specified RTR operation is currently reachable.
You can further control the installation of static routes by specifying the last-resort
keyword, which is valid only when you use the verify rtr keywords in the ip route command.
The last-resort keyword instructs the router to install the static route in the routing table
even if the specified RTR operation is unreachable, provided that no other static route
to the same network prefix is available.
Although the configuration example in the next section uses Fast Ethernet interfaces,
E Series routers support next-hop verification on any type of lower-layer interface.
RTR Configuration Example
Figure 12 on page 33 shows a sample configuration that illustrates the next-hop verification
feature. In this example, two Fast Ethernet interfaces are configured between a remote
Copyright © 2010, Juniper Networks, Inc.