LACP Member Interface Removal Without Traffic Draining
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for gracefully removing LACP member interfaces in port-channels or virtual port-channels during maintenance or software upgrades cause traffic loss and inefficiencies, especially in high-speed networking environments, as they require data draining and buffer generation, which become impractical with increasing networking speeds.
Innovation Solution
Implementing graceful insertion and removal (GIR) at the Layer 2 level using Link Aggregation Control Protocol (LACP) by sending LACP PDUs to clear the 'collection' and 'distribution' bits, allowing the partner device to remove the port from the transmit path without disrupting traffic, enabling seamless hardware and software upgrades.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional data draining and buffer generation methods are used to take down a port channel, then traffic can be preserved during maintenance, but the procedure becomes increasingly difficult and impractical as networking speeds increase, requiring more hardware and cost
Solution Approach 1:
The patent extracts the LACP member interface from the port-channel by clearing the collection and distribution bits in LACP PDUs, allowing the interface to be removed from the transmit path without requiring data draining or buffer generation. This eliminates the complex hardware requirements associated with traditional take-down procedures while maintaining traffic preservation.
Solution Approach 2:
The patent changes the state parameters of the LACP interface by clearing specific bits (collection and distribution bits) in the LACP PDUs. This parameter change allows the interface to transition from an active state to a removed state without disrupting traffic flow, avoiding the need for complex buffer management hardware.
2Reliability
If traditional data draining is performed to remove a port channel, then traffic loss can be minimized, but the time required for removal increases due to data drainage and buffer generation
Solution Approach 1:
The patent performs preliminary action by clearing the collection and distribution bits in LACP PDUs before actually removing the interface. This preliminary bit-clearing action prepares the partner device to stop sending traffic to the removing device, allowing the interface to be removed immediately without requiring time-consuming data drainage procedures.
Solution Approach 2:
The patent uses LACP PDUs as an intermediary mechanism to communicate the removal intent between devices. By clearing specific bits in these protocol messages, the patent enables coordinated traffic redirection without requiring direct data drainage or buffer management, significantly reducing removal time while preventing traffic loss.
3Ease of operation
If LACP collection and distribution bits are cleared to remove a port, then the port can be removed from transmit path without disrupting traffic, but traffic must be redirected through remaining ports which requires coordination
Solution Approach 1:
The patent enables self-service by allowing the LACP protocol itself to handle the traffic redirection coordination. When collection and distribution bits are cleared in the LACP PDUs, the partner device automatically stops sending traffic to the removing device and redirects it through remaining active ports, eliminating the need for external coordination mechanisms.
Data Source
AI summary
Methods and systems are described herein for graceful insertion and removal of at a data link layer of an open systems interconnection model (OSI Model). In one aspect, the method comprises: establishing connections to at least two ports on a first side of a link to create a link aggregation group managed using link aggregation control protocol (LACP), wherein the link aggregation group constitutes a transmit path from the first side of the link to the second side of the link. A partner device may receive, from a first port of the at least two ports, a first message, wherein the first message indicates that the first port will become unavailable to receive traffic.