1 / 1

Efficient Detection of Link Aggregation Failures | Network Layer Optimization

Learn about the importance of proper failure detection mechanisms in link aggregation, how BFD and LinkAgg differ in purpose, and tips to prevent layer violations. Discover key clues to identify if BFD is at the wrong layer and explore alternative solutions. Dive into practical ways to avoid unnecessary layer violations in networking setups.

naida-oneil
Télécharger la présentation

Efficient Detection of Link Aggregation Failures | Network Layer Optimization

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. BFD to detect LinkAgg link failures • BFD is at the wrong layer. The purpose of Link Aggregation is to hide from upper layers the fact that multiple physical links are present. The purpose of BFD is to verify that the routers are working, and not just the lower layers. • The primary means for LinkAgg failure detection is the bi-directional hardware failure detection mechanisms of 802.3. The secondary means for failure detection is IEEE Std 802.1ag == ITU-T Y.1731 Ethernet OAM, which runs at the right layer to detect failures, i.e., below LinkAgg. An 802.1ag failure disables the link, simulating a hardware failure; it has no “hooks” into LACP. • Clues that BFD is at the wrong layer: • No IP addresses for the individual links. • Hooks are needed to get into LACP to report the failure. • In the typical implementation, the BFD solution will be handled at a low layer, and won’t go near the routing function for scaling reasons. • Three ways to avoid (totally unnecessary) layer violations: • Invent and use a Layer 3 equivalent of LACP that fits routing and BFD. • Use Ether OAM. Work with 802.1 to invent a way to avoid needless configuration. • Encapsulate BFD below LinkAgg thus giving the world two ways to do exactly the same job (aka NIH).

More Related