Network Path Validation via User-Specified Traffic Criteria
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network adapter failover technologies are limited by their inability to adapt to user-defined traffic patterns, leading to failure to switch to a secondary pathway when specific types of traffic are absent, causing connectivity issues in scenarios where multiple servers are connected to the same switch.
Innovation Solution
A method that allows users to specify user-defined traffic criteria for failover, enabling the system to monitor for the absence of specific frame types and switch to a secondary pathway that continues to communicate the desired traffic type, thereby maintaining connectivity based on user-specified packet criteria.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional heartbeat-based failover is used, then the system maintains simple operation, but it cannot adapt to user-defined traffic patterns causing failure to switch when specific traffic types are absent
Solution Approach 1:
The failover mechanism transitions from a static heartbeat-based system to a dynamic system that adapts to user-defined traffic patterns. The system now monitors for specific frame types (such as IGMP, ARP, or custom traffic patterns) that users configure, allowing the failover behavior to dynamically respond to the actual traffic requirements rather than relying on generic heartbeats.
Solution Approach 2:
The system allows users to define custom parameters for traffic pattern recognition, including frame type filters, source/destination MAC addresses, and protocol-specific criteria. This parameter customization enables the failover mechanism to adapt to diverse traffic patterns while maintaining a unified underlying architecture.
2Reliability
If generic heartbeat monitoring is used, then the system operates with low complexity, but it fails to detect absence of specific traffic types leading to connectivity issues
Solution Approach 1:
The system implements feedback mechanisms where the network interface continuously monitors incoming traffic patterns against user-defined criteria and provides feedback to the failover decision logic. When the monitored traffic pattern (such as absence of IGMP queries or specific ARP requests) indicates a problem, the system triggers appropriate failover actions.
Solution Approach 2:
The patent introduces an intermediary layer (such as a switch or network device) that can generate synthetic traffic patterns or respond to monitoring queries. This intermediary helps validate the health of network paths by responding to specific probe traffic, enabling more accurate detection of connectivity issues without requiring complex end-to-end monitoring.
3Measurement precision
If the system monitors for absence of specific frame types, then it can accurately detect path failures, but it requires user configuration of traffic criteria increasing operational complexity
Solution Approach 1:
The system provides pre-configured templates for common traffic patterns (such as standard IGMP, ARP, DNS queries) that can be quickly deployed without extensive customization. These template-based solutions allow users to implement precise path validation for common scenarios with minimal configuration effort, while still maintaining the capability for custom patterns when needed.
4Reliability
If failover is based on generic traffic absence, then the system operates simply, but it cannot ensure continuity of specific application traffic
Solution Approach 1:
The monitoring function is segmented into protocol-specific or traffic-type-specific modules. Each module can independently monitor for its designated traffic pattern (IGMP, ARP, DNS, or custom protocols) and report status to the central failover decision logic. This segmentation allows precise monitoring of application-specific traffic while maintaining modular, manageable system complexity.
Data Source
AI summary
A method of operating a network computer system to manage failover in the network computer system comprising communicating traffic via the plurality of network resources, and failing over from a primary pathway to a secondary pathway of the pathway plurality based on failure to receive the user-specified traffic defined by the failover criteria in the primary pathway in combination with availability of the user-specified traffic via the secondary pathway.