Switching Fabric Loop Prevention via Distributed Role Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional switching fabric configuration techniques are complex, costly, and require external devices for management and control, leading to high operational overhead and long deployment times, with a specific challenge being the prevention of communication loops.
Innovation Solution
An Information Handling System (IHS) with a processing system and memory that includes a switching fabric loop prevention engine, which automatically determines device roles and configures the switching fabric to prevent communication loops by receiving identification information from connected devices and implementing a loop prevention configuration to prevent specific communication types from being forwarded between slave switch devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional switching fabric configuration techniques are used, then communication loop prevention can be achieved, but device complexity and operational overhead increase due to external management devices and complex configuration operations
Solution Approach 1:
The patent extracts the loop prevention functionality from external SDN controllers and embeds it directly into the switching fabric through distributed loop detection modules in each switch device. This eliminates the need for external management devices and reduces configuration complexity while maintaining loop prevention capability.
Solution Approach 2:
Each switch device in the switching fabric autonomously performs loop detection and prevention operations using its own processing capabilities. The switches self-configure by exchanging identification information and automatically determining loop prevention configurations without requiring external controllers or manual configuration, thereby reducing operational overhead.
2Ease of operation
If SDN techniques are used to manage switching fabric, then some management and control issues are alleviated, but configuration complexity and deployment time remain high due to external device requirements
Solution Approach 1:
The patent implements preliminary loop prevention configurations by having each switch device pre-load loop detection algorithms and identification information exchange protocols. When switches are added to the fabric, they automatically execute pre-programmed discovery and configuration routines, eliminating the need for time-consuming manual configuration or external controller intervention.
Solution Approach 2:
Switch devices autonomously perform self-configuration by exchanging identification information with directly connected devices, automatically determining their roles in the fabric, and configuring loop prevention parameters without external assistance. This self-service capability dramatically reduces deployment time and configuration complexity.
3Reliability
If external devices are used to provide management and control of switching fabric, then loop prevention can be achieved, but cost increases due to additional hardware requirements
Solution Approach 1:
The patent extracts the management and control functionality from external SDN controller devices and relocates it to the switching fabric itself through distributed loop detection modules in each switch. This eliminates the need for separate external management hardware, reducing the total number of devices required while maintaining loop prevention reliability.
Solution Approach 2:
Each switch device in the fabric is designed to perform multiple functions: data forwarding, loop detection, identification information exchange, and automatic configuration. This multi-functionality eliminates the need for dedicated external management devices, as each switch serves both as a network element and a control element, thereby reducing the quantity of devices needed.
Data Source
AI summary
A switching fabric loop prevention system includes first slave switch devices in a switching fabric that each automatically determine a first slave switch device role for themselves based on first directly connected device identification information received from a first directly connected device, and second slave switch devices in the switching fabric that each automatically determine a second slave switch device role for themselves based on second directly connected device identification information received from a second directly connected device. A master switch device in the switching fabric then configures each of the first slave switch devices having the first slave switch device role to prevent first type communications that have been received from one of the second slave switch devices having the second slave switch device role from being forwarded to another of the second slave switch devices having the second slave switch device role.