• Author : William Rideout


BFD session telemetry

Description BFD (Bidirectional Forwarding Detection) session telemetry allows for the collection of per-session statistics as well as rbfd kernel module statistics to be automatically collected at a set interval and stored in shared memory where Cloud Vision Portal (CVP) or other applications may gather them.  Previously, this information was only available to the user via execution of several CLI show-commands.  In addition, several new statistics have been added which are updated within the session-stats interval and provide a finer “snapshot” view of session health than the previously-available session lifetime statistics.  This feature supports both hardware-accelerated and software (kernel module) accelerated...
Continue reading →

Modal BFD CLI configuration

Description A new configuration model for the BFD (Bidirectional Forwarding Detection) agent was added in order to more concisely group configuration commands.  In addition to isolating BFD-specific CLI commands from the rest of the system configuration, using a dedicated configuration mode allows for new sub-modes to be added for peer-specific configuration that pertains to either the default VRF or a non-default VRF.  This allows for a finer control of BFD-specific settings.  System-wide BFD configuration exists in three contexts: Interface-level BFD configuration, Global BFD configuration, and Peer-level BFD configuration. Global BFD configuration commands are entered within the scope of the new...
Continue reading →

BFD control-plane-independent interoperability

Description Bidirectional Forwarding Detection (BFD) control packets contain several bit-flags which advertise session-specific details, such as the current session state.  The bit denoted “C” for control-plane-independent, indicates whether or not the peer device uses a BFD implementation which shares fate with the device control plane, as described in [RFC 5880], section 4.1. If incoming BFD control packets are received with this bit set, it indicates that the peer device is using a BFD implementation which is independent of the peer control plane, and therefore, the BFD session will continue to function, despite disruptions to the peer control plane.  If incoming...
Continue reading →


Get every new post on this blog delivered to your Inbox.

Join other followers: