BFD Session Configuration Where Next Hop is a VE Interface

BFD session configurations in the micro controller use only a local port number as the TX port parameter. When the TX port, or next hop, for the BFD session is part of a VE interface with a physical port, the session is configured on one port for the VLAN. ARP resolution for the peer allocates the actual outgoing port to use.

If a change occurs to the Layer 2 state of the VLAN, for example a spanning tree state change, the next-hop port can be brought down, triggering a session down notification to BFD. Applications are then notified to act on the session failure even though the VE is still operational. To delay this, the holdover timer can be set to a higher time interval during which the session can come back up due to the successful movement to another VE member port. Refer to Holdover Timer, and to the RUCKUS FastIron Command Reference, for more information.

Note: Applications running at the remote endpoint of the session also require the exact configuration of the holdover timer.

To view a sample configuration for a BFD single-hop session that is configured for OSPFv2 for a Virtual Ethernet (VE) interface on a LAG, refer to Configuration Example: BFD for OSPF Single-hop Session for a VE Interface.

Parent topic: BFD