1 / 4

Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG) Interfaces Interfaces

Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG) Interfaces Interfaces. Draft-mmm-bfd-on-lag-05. Authors: Manav Bhatia Mach Chen Sami Boutros Marc Binderberger Jeff Haas. Presenter: Sami Boutros IETF84, July 2012. Changes from 03  05 (Dedicated MAC).

terri
Download Presentation

Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG) Interfaces Interfaces

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG) Interfaces Interfaces Draft-mmm-bfd-on-lag-05 Authors: Manav Bhatia Mach Chen Sami Boutros Marc Binderberger Jeff Haas Presenter: Sami Boutros IETF84, July 2012

  2. Changes from 03  05 (Dedicated MAC) • Dedicated MAC address MUST be used for the immediate next hop when micro BFD session is in the Down/AdminDown and Init state. • In the Up state, the MAC address from the received BFD packets for the session MUST be used. • Micro BFD packets MUST always be sent untagged. • When operating in the context of IEEE 802.1q or IEEE 802.qinq, the micro BFD packets should either be untagged or sent with a vlan tag of Zero (802.1p priority tagged).  • Implementations compliant to this standard MUST be able to receive both untagged and 802.1p priority tagged micro BFD packets.

  3. Changes from 03  05(LACP interaction) • Addressed IEEE Liaison, no LACP interaction !!! • The LMM uses the status of the BFD session to determine whether the member link should be included in the LAG L2 load balance table.  • Prior to LACP coming up, the micro BFD session is Passive and does not send BFD control packets. • Even when LACP is used and considers the member link to be ready to forward traffic, the member link is only used by the traffic load balancer when the micro BFD session is Up. 

  4. Next steps • Any more comments are appreciated. • Ready for WG adoption. Thank you

More Related