Compute Node Cluster Routing with Fault-Aware Port Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Data center networks with compute node clusters face challenges in maintaining routing performance due to faults, which can lead to adverse effects on data packet routing, highlighting the need for effective fault detection and management mechanisms to ensure continuous operation.

Innovation Solution

The implementation of a fault detection and routing management system within compute nodes, which includes logic to determine optimal output ports for data packet routing based on destination information and fault status of links, and proactive data packet discard mechanisms to prevent propagation of faults, ensuring data packets are routed around faulty paths.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a cluster of compute nodes is used as a router to provide extensible routing capacity, then routing flexibility and capacity are improved, but the system becomes more susceptible to faults that can adversely affect routing performance

Engineering Contradiction:
Improverouting flexibilityVSAvoidrouting performance
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary fault detection by monitoring data packet counts at input and output ports before routing decisions are made. By detecting faults in advance through conservation of flow verification, the system can proactively adjust routing paths to avoid faulty links, thereby maintaining routing performance while preserving the flexibility of cluster-based routing architecture.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If fault detection and routing management mechanisms are implemented to maintain routing performance, then reliability is improved, but device complexity increases

Engineering Contradiction:
Improverouting performanceVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Each compute node autonomously performs fault detection by comparing its own input and output data packet counts without requiring external monitoring systems. The conservation of flow principle enables self-diagnosis where nodes independently verify their operational status and automatically adjust routing behavior, eliminating the need for complex centralized fault management infrastructure.

Inventive Principle:
Principle #25Self-service

3Reliability

If data packets are routed around faulty paths to maintain continuous operation, then reliability is improved, but loss of time occurs due to adaptive routing decisions

Engineering Contradiction:
Improvecontinuous operationVSAvoidrouting decision time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary fault detection and maintains updated fault status information about links and compute nodes before routing decisions are required. By having fault information pre-available through continuous monitoring of data packet counts, the system can make rapid routing adjustments without time-consuming fault diagnosis delays, thus minimizing loss of time while ensuring continuous operation.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10938712B2Compute node cluster based routing method and apparatus
Publication Date: 2021.03.02 INTEL CORP
  • US10938712B2 patent drawing
  • US10938712B2 patent drawing
  • US10938712B2 patent drawing

AI summary

Apparatus and method to facilitate networked compute node cluster routing are disclosed herein. In some embodiments, a compute node for cluster compute may include one or more input ports to receive data packets from first selected ones of a cluster of compute nodes; one or more output ports to route data packets to second selected ones of the cluster of computer nodes; and one or more processors, wherein the one or more processors includes logic to determine a particular output port, of the one or more output ports, to which a data packet received at the one or more input ports is to be routed, and wherein the logic is to exclude output ports associated with links indicated in fault status information as having a fault status to be the particular output port to which the data packet is to be routed.