MCLAG Traffic Redirection Sequencing for Controlled Switch Unavailability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing technologies fail to efficiently manage traffic redirection in multi-chassis link aggregation groups (MCLAGs) during controlled unavailability events, leading to unsynchronized daemon and hardware states, traffic loss, and network interruptions due to uncoordinated configuration applications.

Innovation Solution

Implementing an orchestrated sequence of traffic forwarding configurations that dictate the order of execution for daemons and hardware, ensuring synchronized states and graceful traffic redirection by waiting for acknowledgments before proceeding to the next step, thereby facilitating a 'make before break' model.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traffic redirection configurations are applied without coordination between daemons and hardware, then configuration application speed is improved, but daemon and hardware states become unsynchronized causing traffic loss

Engineering Contradiction:
Improveconfiguration application speedVSAvoiddaemon and hardware state synchronization
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the daemon waits for acknowledgment from the hardware that the configuration has been successfully applied before proceeding to the next configuration step. This ensures that the daemon and hardware states remain synchronized, preventing traffic loss while maintaining efficient configuration application.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent applies traffic redirection configurations in a predetermined sequence before actual traffic redirection is needed. By preparing the configuration steps in advance and executing them systematically with proper synchronization, the system ensures that when traffic redirection occurs, both daemon and hardware are in the correct synchronized state.

Inventive Principle:
Principle #10Preliminary action

2Loss of time

If configurations are applied in parallel without sequencing, then configuration time is reduced, but traffic loss and network interruptions increase

Engineering Contradiction:
Improveconfiguration timeVSAvoidtraffic loss and network interruptions
Core Design Contradiction:
Loss of timeVSObject-generated harmful factors

Solution Approach 1:

The patent divides the traffic redirection configuration process into multiple discrete steps or segments, where each step applies a specific configuration change. By segmenting the configuration process and applying steps in sequence with proper synchronization, the system minimizes traffic loss while maintaining efficient configuration time.

Inventive Principle:
Principle #1Segmentation

3Reliability

If coordinated configuration application is implemented with acknowledgments, then state synchronization is improved, but configuration application complexity increases

Engineering Contradiction:
Improvestate synchronizationVSAvoidconfiguration coordination complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The hardware component automatically generates and sends acknowledgment signals to the daemon when configuration changes are successfully applied. This self-service mechanism simplifies the coordination complexity by eliminating the need for complex polling or status checking logic in the daemon, while still ensuring reliable state synchronization.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12368666B2Efficient traffic redirection for an MCLAG for controlled unavailability events
Publication Date: 2025.07.22 HEWLETT PACKARD ENTERPRISE DEV LP
  • US12368666B2 patent drawing
  • US12368666B2 patent drawing
  • US12368666B2 patent drawing

AI summary

A system for facilitating traffic redirection for a multi-chassis link aggregation group (MCLAG) is provided. During operation, the system can participate in an MCLAG using a first interface of a first switch. The MCLAG can also include a second interface of a second switch. Based on predetermined unavailability for the first switch, the system can determine a sequence of applications for a plurality of traffic forwarding configurations. A respective configuration can facilitate loop prevention for traffic forwarded via the MCLAG. The system can then apply the plurality of configurations to the first switch based on the sequence of applications to redirect unicast traffic from the first switch to the second switch. Here, applying a respective configuration can include programming corresponding switch hardware with the configuration. Subsequently, the system can perform a set of operations on the first switch that triggers the predetermined unavailability.