Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide, Release 15.4(1)S
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
- Updated:
- February 11, 2018
Chapter: Configuring BFD Hardware Offload
Configuring BFD Hardware Offload
Bidirectional Forwarding Detection (BFD) offload support provides the functionality to offload a BFD session to the hardware. BFD is a forwarding path failure detection protocol and reduces the overall network convergence time by sending rapid failure detection packets (messages) to the routing protocols for recalculating the routing table. Previously the performance of BFD was restricted to the capabilities of CPU and IOS on the switch. Effective failure detection requires BFD to run at high frequencies (using aggressive timers as low as 50ms), which was not possible because of CPU and IOS restrictions.
For information on configuring BFD see Configuring BFD section of ME 3800x and ME 3600x Switches Software Configuration Guide.
|
|
|
|
|---|---|---|
Restrictions for BFD Hardware Offload Support
- Only BFD version 1 is supported.
- Only FPGA offloaded BFD sessions are supported on Cisco ME 3600X-24CX-M.
- The switch supports BFD only in Asynchronous mode or no echo mode.
- The switch supports 511 asynchronous BFD sessions.
- BFD hardware offload is supported for IPv4 sessions with non-echo mode only.
- BFD hardware offload is supported on port-channel interfaces.
- BFD hardware offload is supported only for the ethernet interface.
- BFD hardware offload is not supported for IPv6 BFD sessions.
- BFD hardware offload is not supported for BFD with TE/FRR.
- If the no echo command is executed when the session is up, use the shut/no shut command to offload BFD in hardware.
Configuring BFD Hardware Offload Support
By default the Cisco IOS runs in echo mode. Hence, BFD is not offloaded to the hardware until the no bfd echo command is executed. The no bfd echo command changes the mode from "echo" to "Asynchronous".
Note
To enable BFD Hardware Offloading on all interfaces, enable the no bfd echo command on all interfaces.
Verifying BFD Hardware Offload Support
Ensure that the Session host value displays "Hardware". Use the show bfd neighbors detail to verify the configuration of BFD Hardware Offload. Hardware BFD sessions have a LD of 1-511.
Note Sometimes if BFD session is brought up after the registered protocol is up, the session may come up in Software. Shut down the interface and apply the BFD configuration to ensure that session comes back up in Hardware (Session Host: Hardware as shown below).
Feedback