Cluster Network Traffic Forwarding via MAC Identifier
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cluster networks, not all nodes are connected to external networks due to asymmetric topologies or switch limitations, leading to inefficiencies in traffic forwarding, particularly in processing and routing packets between internal and external servers and clients.
Innovation Solution
Each cluster node is configured with a predetermined identifier inserted into the MAC ID field of Ethernet headers to distinguish traffic types, allowing for hashing and distribution of data traffic and identification of steered packets for processing, with ARP requests used to determine the destination MAC ID for forwarding processed packets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual routing and encapsulation are used by gateway nodes to forward packets to internal cluster nodes, then traffic can be forwarded to nodes not connected to external networks, but processing overhead increases and efficiency decreases
Solution Approach 1:
The patent introduces a special MAC address prefix (01:00:5E) as an intermediary mechanism to automatically identify cluster-local traffic. This allows switches to automatically forward packets to internal nodes without requiring manual routing configuration or gateway encapsulation, thereby eliminating processing overhead while maintaining the ability to reach nodes not directly connected to external networks
Solution Approach 2:
The system enables self-service by allowing internal cluster nodes to be automatically identified and reached through the special MAC address prefix. The network infrastructure (switches and gateways) automatically recognizes traffic destined for internal nodes through the MAC prefix and forwards it appropriately without requiring manual intervention, routing configuration, or encapsulation processes
2Device complexity
If all cluster nodes are connected to external networks, then traffic forwarding is simplified, but network topology flexibility and security isolation are reduced
Solution Approach 1:
The patent applies local quality by assigning a distinctive MAC address prefix (01:00:5E) specifically to traffic involving internal cluster nodes. This allows the network to treat internal node traffic differently from external traffic, enabling asymmetric topologies where some nodes have external connectivity and others don't, while maintaining simplified forwarding through automatic recognition of the special MAC prefix
3Reliability
If asymmetric network topologies are used with fewer nodes connected to upstream switches, then security and resource management are improved, but traffic routing complexity increases
Solution Approach 1:
The special MAC address prefix (01:00:5E) serves as an intermediary that automatically identifies traffic destined for internal cluster nodes in asymmetric topologies. This eliminates the need for complex manual routing configurations on gateways and switches, as the MAC prefix automatically directs traffic to the appropriate internal nodes without requiring administrators to configure routing rules for each internal node
Data Source
Figure 1A
Figure 1B
Figure 1C
AI summary
The present invention is directed towards systems and methods for forwarding network packets in a cluster network. A predetermined identifier may be inserted into a Media Access Control (MAC) ID field of an Ethernet header of a packet to distinguish various types of traffic. Newly received packets may be identified due to the absence of the identifier. The identifier may be added to the source MAC ID field of the Ethernet header of the packet, and the packet may be distributed to cluster nodes for processing via an inter-node communication bus. Thus, received packets with the identifier in the source MAC ID field may be identified as steered for processing by an internal node of the cluster. After processing the packet, the internal node may transmit the processed packets via the inter-node bus with a destination MAC ID including the identifier. Accordingly, received packets with the identifier in the destination MAC ID field may be identified as processed and ready for forwarding to clients or servers.