PurposeCommand or Action
• count packet-count—Specifies a number of consecutive packets
received with bad latency that will take down a BFD session.
The range is 1 to 10. The default is 1.
commit
Step 4
Delaying BFD Session Startup Until Verification of Echo Path and Latency
Beginning in Cisco IOS XR Release 4.0.1, you can verify that the echo packet path is working and within
configured latency thresholds before starting a BFD session on non-bundle interfaces.
Echo startup validation is not supported on bundle interfaces.Note
To configure BFD echo startup validation, complete the following steps.
Before You Begin
Before you enable echo startup validation, be sure that your BFD configuration supports echo mode.
SUMMARY STEPS
1.
configure
2.
bfd
3.
echo startup validate [force]
4.
commit
DETAILED STEPS
PurposeCommand or Action
configure
Step 1
Enters BFD configuration mode.bfd
Example:
RP/0/0RP0RSP0/CPU0:router(config)# bfd
Step 2
Enables verification of the echo packet path before starting a BFD session,
where an echo packet is periodically transmitted on the link to verify
echo startup validate [force]
Example:
RP/0/0RP0RSP0/CPU0:router(config-bfd)#
echo startup validate
Step 3
successful transmission within the configured latency before allowing the
BFD session to change state.
When the force keyword is not configured, the local system performs echo
startup validation if the following conditions are true:
Cisco ASR 9000 Series Aggregation Services Router Routing Configuration Guide, Release 5.1.x
212 OL-30423-03
Implementing BFD
Delaying BFD Session Startup Until Verification of Echo Path and Latency