39
calculates the shortest path based on the new network topology, and forwards packets over that path
after network convergence.
Configuration restrictions and guidelines
• RIP FRR takes effect only for RIP routes learned from directly connected neighbors.
• Do not use RIP FRR and BFD for RIP at the same time. Otherwise, FRR might fail to work.
• RIP FRR is available only when the state of primary link (with Layer 3 interfaces staying up)
changes from bidirectional to unidirectional or down.
Configuration prerequisites
You must specify a next hop by using the apply fast-reroute backup-interface command in a
routing policy and reference the routing policy for FRR. For more information about routing policy
configuration, see "Configuring routing policies."
Configuration procedure
Configuring RIP FRR
Step Command Remarks
1. Enter system view.
system-view
N/A
2. Configure the source
address of echo packets.
bfd echo-source-ip
ip-address
By default, the source address of
echo packets is not configured.
3. Enter RIP view.
rip
[ process-id ] [
vpn-instance
vpn-instance-name ]
N/A
4. Configure RIP FRR.
fast-reroute route-policy
route-policy-name
By default, RIP FRR is disabled.
Enabling BFD for RIP FRR
By default, RIP FRR does not use BFD to detect primary link failures. To speed up RIP convergence,
enable BFD single-hop echo detection for RIP FRR to detect primary link failures.
To configure BFD for RIP FRR:
Step Command Remarks
1. Enter system view.
system-view
N/A
2. Configure the source IP
address of BFD echo
packets.
bfd echo-source-ip
ip-address
By default, the source IP address
of BFD echo packets is not
configured.
3. Enter interface view.
interface
interface-type
interface-number
N/A
4. Enable BFD for RIP FRR.
rip primary-path-detect bfd
echo
By default, BFD for RIP FRR is
disabled.
Displaying and maintaining RIP
Execute display commands in any view and execute reset commands in user view.
To Next Page
Loading...
Need help?
General