Automated Recovery from Split Segment Conditions in Layer 2 Network Teams

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network configurations lack automated recovery mechanisms to restore connectivity when a split segment condition occurs due to failures in uplink connections, leading to isolation of clients from the server and potential network disruptions.

Innovation Solution

A method that automatically detects network segment splits and reconfigures team members to operate as primary resources within isolated segments, ensuring continued communication and restoring connectivity by assigning unique MAC addresses as needed, allowing the network to recover without manual intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If network segment splitting is allowed for redundancy, then fault tolerance is improved, but automated recovery capability deteriorates

Engineering Contradiction:
Improvefault toleranceVSAvoidautomated recovery capability
Core Design Contradiction:
ReliabilityVSExtent of automation

Solution Approach 1:

The system implements automated detection of split segment conditions through monitoring mechanisms that provide feedback about network connectivity status. When a split is detected, the system automatically triggers reconfiguration procedures, eliminating the need for manual intervention while maintaining fault tolerance through the redundant path architecture.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The network system performs self-healing by automatically detecting split segment conditions and reconfiguring team members to restore connectivity. The system serves itself by autonomously identifying the problem and executing the recovery procedure without external assistance, thereby improving both automation extent and maintaining reliability.

Inventive Principle:
Principle #25Self-service

2Measurement precision

If manual intervention is required for recovery, then control precision is improved, but loss of time increases

Engineering Contradiction:
Improvecontrol precisionVSAvoidrecovery time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system pre-configures multiple team members with potential primary resource capabilities before a split occurs. When a split segment condition is detected, the system can immediately activate a pre-prepared recovery configuration, eliminating the time required for manual reconfiguration while maintaining precise control over the recovery process through automated execution of predetermined procedures.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If team reconfiguration is automated, then productivity is improved, but device complexity increases

Engineering Contradiction:
Improverecovery efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The recovery system is segmented into distinct functional modules: detection mechanisms that identify split conditions, decision logic that determines reconfiguration actions, and execution components that implement the reconfiguration. This modular segmentation enables automated high-speed recovery while managing complexity through clear separation of concerns, with each module performing a specific function independently.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS7990849B2Automated recovery from a split segment condition in a layer2 network for teamed network resources of a computer system
Publication Date: 2011.08.02 HEWLETT PACKARD ENTERPRISE DEV LP
  • US7990849B2 patent drawing
  • US7990849B2 patent drawing
  • US7990849B2 patent drawing

AI summary

A computer system automatically recovers from a split segment condition in which a contiguous layer 2 network segment, comprising a plurality of contiguous paths each directly coupling one or more members of a team of network resources of the computer system to a core switch of a layer 2 network, is split into two or more noncontiguous segments each comprising a contiguous set of one or more of the plurality of paths. The computer system includes a team of network resources having one or more members that couple it to each one of the plurality of paths. A teaming driver binds the drivers of each member of the team and is coupled to the segment through the members of the team. The teaming driver detects whenever the network segment has been split into two or more noncontiguous segments and then configures the team such that one of the members coupled to a path within each of the noncontiguous segments is designated as a primary resource thereby restoring connectivity of the isolated paths to the computer system.