31
To do…
Use the command…
Remarks
Step 3
Configure the
source address of
echo packets
bfd echo-source-ip
ip-address
Required
Not configured by
default
Step 4
Bind a static route
with the track entry
ip
route-static
dest-address
{
mask
|
mask-length
}
next-hop-address
[
track
track-entry-number
] [
preference
preference-value
] [
tag
tag-value
] [
description
description-text
]
Required
•
If route flaps occur, enabling BFD may worsen the route flaps; therefore, enable BFD with care in such
cases.
•
The source address of echo packets must be configured if the BFD session operates in echo mode.
•
BFD cannot be used for a static route when the outbound interface has the spoofing attribute.
•
BFD can be used for static routes with direct next hops rather than non-direct next hops.
•
For the BFD echo function, a BFD session is established at only one end when the echo mode is used.
•
For the echo and control mode, the switch currently does not support BFD detection on tunnel interfaces.
Configuring static route FRR
When a link or a router fails, the packets on the path are discarded or a routing loop occurs. To
avoid such problems, enable static route FRR.
Figure 2
Network diagram for static route FRR
Router A
Router B
Router E
Backup nexthop: Router C
Nexthop: Router D
As shown in Figure 2, upon a link failure, FRR designates a backup next hop by using a routing
policy for routes matching the specified criteria. Packets are directed to the backup next hop to
avoid traffic interruption.
Prerequisites
Configuring static route FRR must reference a routing policy. Use the
apply fast-reroute
backup-interface
command to specify a backup next hop in a routing policy. For more
information about the command and routing policy configurations, see
Routing Policy
in the
Layer
3 – IP Routing Configuration Guide
.
Summary of Contents for S9500E Series
Page 435: ...435 ...