H3C Technologies H3C S10500 Series Switches - Manual (Page 26)

11
Figure 1 Network diagram for static route FRR
As shown in Figure 1 , 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.
Configuration prerequisites
Configuring static route FRR needs to reference a routing policy. You can specify a backup next hop in
a routing policy by using the apply fast-reroute backup-interface command. For more information about
the command and routing policy configurations, see the chapter “Routing policy configuration.”
Configuration procedure
Follow these steps to configure static route FRR:
To do… Use the command… Remarks
Enter system view system-view —
Configure the source address of
echo packets
bfd echo-source-ip ip-address
Required
Not configured by default.
Configure static route FRR
ip route-static [ vpn-instance
vpn-instance-name ] fast-reroute
route-policy route-policy-name
Required
Not configured by default.
NOTE:
Static route FRR takes effect only for static routes that have both the outbound interface and next hop
specified.
Do not use FRR and BFD at the same time.
Displaying and maintaining static routes
To do… Use the command… Remarks
Display information of static routes
display ip routing-table protocol static [ inactive |
verbose ] [ | { begin | exclude | include }
regular-expression ]
Available in any
view
Delete all the static routes
delete [ vpn-instance vpn-instance-name ]
static-routes all Available in
system view
NOTE:
For more information about the display ip routing-table protocol static [ inactive | verbose ] [ | { begin
| exclude | include } regular-expression ] command, see Layer 3—IP Routing Command Reference.