MIBD, and SNMPD utilize CPU resources for more than the specified The general Routing Engine switchover event, processes such as RPD, This minimum value is required because, during To prevent BFD flapping during the general Routing Engine switchoverĮvent, specify a minimum interval of 5000 milliseconds for RoutingĮngine-based sessions. Specifying a minimum interval for BFD less than 100 millisecondsįor Routing Engine-based sessions and less than 10 millisecondsįor distributed BFD sessions can cause undesired BFD flapping.ĭepending on your network environment, these additional The command does not affect traffic flow on the routing device.īFD is an intensive protocol that consumes system resources. The clear bfd adaptation command is hitless, meaning that You can use the clear bfd adaptation command to return BFD interval timers to their configured values. (Tx) interval is increased by two if the remote BFD instance is the A back-offĪlgorithm increases the receive (Rx) interval by two if the localīFD instance is the reason for the session flap. In a span of 15 seconds (15000 milliseconds). To a higher value when a BFD session flap occurs more than three times Or a neighbor can negotiateĪ higher value for a timer than the configured value. Is, the timer detects failures more slowly). The timers can adapt to a higher value if the adjacency fails (that Value, the faster the failure detection and vice versa. The lower the BFD failure detection timer The BFD failure detection timers can be adjusted 10 inlineīFD sessions are supported and can be configured with a timer of 150
Performance may vary depending on the system load. Support which will enable sessions to be configured at less than 1 Multihop Bidirectional Forwarding Detection (BFD) inline keep alive