Multiple TCP/IP Stack Processors for Network Traffic Segregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data center systems face challenges in managing network traffic segregation and resource allocation due to the reliance on a single TCP/IP stack processor, leading to issues with routing, resource competition, and security gaps, especially in multi-tenant environments and long-distance network topologies.
Innovation Solution
Implementing multiple TCP/IP stack processors on a host, each with its own dedicated default gateway and resource pool, allowing for independent operation and isolation of processes, thereby enabling efficient communication across subnets and improving security and resource management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single TCP/IP stack processor is used to manage all network traffic, then device complexity is reduced, but routing efficiency and security are worsened due to inability to provide dedicated gateways for different traffic types
Solution Approach 1:
The patent divides the single TCP/IP stack processor into multiple independent stack processors, each dedicated to specific traffic types (management traffic, VM traffic, storage traffic, etc.). This segmentation allows each stack processor to have its own default gateway and routing table, eliminating routing conflicts and improving routing efficiency for different traffic types while maintaining manageable complexity through modular design.
2Reliability
If multiple VLAN interfaces are maintained for traffic segregation, then security and quality of service are improved, but application complexity increases as intelligence for interface selection must be built into each application
Solution Approach 1:
The patent introduces TCP/IP stack processors as intermediary components between applications and the network infrastructure. These stack processors automatically perform interface selection and packet routing based on traffic type and destination, eliminating the need for applications to contain intelligence for interface selection. The stack processors act as mediators that handle the complexity of VLAN interface management while presenting a simplified interface to applications.
3Device complexity
If a single default gateway is supported, then device complexity is reduced, but adaptability is worsened as other flows cannot reach their gateway address if it is on a different subnet/VLAN
Solution Approach 1:
The patent segments the single default gateway into multiple dedicated default gateways, with each TCP/IP stack processor having its own default gateway configured for its specific traffic type. This allows management traffic to use one gateway, storage traffic to use another gateway on a different subnet, and VM traffic to use yet another gateway, thereby achieving multi-subnet and multi-VLAN reachability without increasing configuration complexity at the application level.
4Adaptability or versatility
If static routes are used to add non-default gateways, then network reachability is improved, but ease of operation is worsened as it is cumbersome and error prone
Solution Approach 1:
The patent uses TCP/IP stack processors as intermediaries that automatically manage route configuration for different traffic types. Instead of requiring manual static route configuration, the stack processors dynamically handle route selection and gateway assignment based on traffic classification and destination address, eliminating the cumbersome and error-prone manual route configuration process while maintaining comprehensive network reachability.
Data Source
AI summary
Multiple TCP/IP stack processors on a host. The multiple TCP/IP stack processors are provided independently of TCP/IP stack processors implemented by virtual machines on the host. The TCP/IP stack processors provide multiple different default gateway addresses for use with multiple processes. The default gateway addresses allow a service to communicate across an L3 network. Processes outside of virtual machines that utilize the TCP/IP stack processor on a first host can benefit from using their own gateway, and communicate with their peer process on a second host, regardless of whether the second host is located within the same subnet or a different subnet. The multiple TCP/IP stack processors can use separately allocated resources. Separate TCP/IP stack processors can be provided for each of multiple tenants on the host. Separate loopback interfaces of multiple TCP/IP stack processors can be used to create separate containment for separate sets of processes on a host.