Loop Prevention Engine for Layer Two Network Redundancy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Logical loops in information handling systems, caused by malfunctioning Spanning Tree Protocol (STP), lead to frame flooding and network failures, disrupting entire layer-2 domains despite redundancy benefits of physical loops.

Innovation Solution

Implementing a loop prevention engine that designates networking devices as loop breaker nodes, tagging data frames with a unique identifier to drop frames within logical loops and notify administrators, preventing network downtime until STP issues are resolved.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If physical loops are configured for redundancy, then network reliability is improved, but logical loops cause frame flooding and network failures

Engineering Contradiction:
Improvenetwork reliabilityVSAvoidframe flooding
Core Design Contradiction:
ReliabilityVSObject-generated harmful factors

Solution Approach 1:

The patent introduces loop breaker nodes as intermediary devices that receive tagged data frames, identify logical loops through tag comparison, and drop frames that would cause flooding. These intermediaries prevent the harmful effect of frame flooding while maintaining the redundant physical loop configuration for reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system uses tagged data frames that carry loop detection information as feedback. When a data frame returns to its source node with matching tags, it provides feedback indicating a logical loop. This feedback mechanism enables automatic loop detection and prevention without disrupting the redundant physical topology.

Inventive Principle:
Principle #23Feedback

2Object-generated harmful factors

If STP is used to prevent logical loops, then frame flooding is reduced, but STP malfunction causes complete network failure

Engineering Contradiction:
Improveframe floodingVSAvoidnetwork functionality
Core Design Contradiction:
Object-generated harmful factorsVSReliability

Solution Approach 1:

The patent segments the network into regular nodes and specialized loop breaker nodes. This segmentation allows the loop prevention function to be distributed across multiple independent nodes rather than relying on a single centralized STP protocol. If one loop breaker node malfunctions, others continue to provide loop prevention, preventing complete network failure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system pre-configures multiple loop breaker nodes throughout the network topology before any failure occurs. This prior cushioning ensures that if STP or any single loop breaker node malfunctions, redundant loop breaker nodes are already in place to maintain loop prevention functionality and prevent total network collapse.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Object-generated harmful factors

If loop breaker nodes are deployed, then logical loops are prevented, but device complexity increases

Engineering Contradiction:
Improvelogical loopsVSAvoidnetwork device complexity
Core Design Contradiction:
Object-generated harmful factorsVSDevice complexity

Solution Approach 1:

Instead of implementing complex loop detection algorithms in every network node, the patent applies partial action by deploying loop breaker functionality only at selected strategic nodes. This reduces overall device complexity while maintaining effective loop prevention, as not all nodes need the full loop breaker capability.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11658897B2Loop prevention system
Publication Date: 2023.05.23 DELL PROD LP
  • US11658897B2 patent drawing
  • US11658897B2 patent drawing
  • US11658897B2 patent drawing

AI summary

A loop prevention system includes a plurality of networking devices that are coupled together to form a Layer Two (L2) domain and at least a portion of the plurality of networking devices are coupled together in a physical loop configuration. A networking device included in the plurality of networking devices may include at least one L2 domain connection that couples the networking device to at least one of the plurality of networking devices in the L2 domain, and an edge connection that connects the networking device to a computing device that is outside of the L2 domain. The networking device may receive a data frame via the edge connection. The networking device then generates a loop breaker data frame by tagging the data frame with a loop breaker tag and forwards the loop breaker data frame via the at least one L2 domain connection.