Distributed Virtual Gateway Appliance for NVO3 Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network virtualization technologies, such as VRRP, utilize only 50% of available resources and do not support multi-node configurations, leading to limitations in fail-safe gateway services and network bandwidth processing.
Innovation Solution
A distributed virtual gateway system is formed with a master, backup, and multiple slave nodes using a gateway stack protocol, where all nodes in the system are utilized to provide fail-safe Layer 2 or Layer 3 gateway services by evenly distributing inbound data packets through a static trunk interface.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If VRRP is used to provide redundant gateway services, then gateway fail-safe capability is improved, but resource utilization deteriorates (only 50% of available resources are utilized)
Solution Approach 1:
The gateway system is segmented into multiple independent nodes (master node, backup node, and slave nodes) that can independently process traffic. Each node has its own network interface and processing capability, allowing the system to divide and distribute workloads across multiple segments rather than having a single active gateway and idle backup.
Solution Approach 2:
Multiple gateway nodes are merged into a unified gateway stack that presents a single logical gateway interface to the network. The nodes are combined through a stacking protocol that allows them to function as a coordinated group, sharing a common management interface while maintaining independent data plane capabilities for parallel traffic processing.
2Reliability
If VRRP is used for gateway redundancy, then fail-safe capability is improved, but device complexity and scalability deteriorate (does not support multi-node configurations)
Solution Approach 1:
The gateway stack protocol provides universal functionality that enables any number of gateway nodes to participate in the stack. The protocol handles node identification, role assignment, and coordination in a way that is independent of the specific number of nodes, allowing the system to scale from 2 nodes to many nodes without requiring different protocols or configurations.
Solution Approach 2:
The gateway stack is designed to be dynamic, allowing nodes to be added or removed from the stack without disrupting overall gateway functionality. The stacking protocol dynamically adjusts to changes in stack composition, automatically reassigning roles and redistributing traffic paths to maintain system operation and fail-safe capabilities.
3Ease of operation
If a single master gateway handles all traffic, then gateway service simplicity is maintained, but network bandwidth processing and productivity deteriorate
Solution Approach 1:
Multiple slave nodes continuously process traffic in parallel with the master node, eliminating idle capacity. While the master node maintains control plane functions, the slave nodes continuously handle data plane traffic, ensuring that useful action (traffic processing) continues across all available hardware resources rather than being concentrated in a single bottleneck.
Solution Approach 2:
The system adds a new dimension to gateway operation by introducing hierarchical roles (master and slave) within the gateway stack. This dimensional change allows the system to separate control plane functions (master) from data plane functions (all nodes), enabling parallel traffic processing across multiple nodes while maintaining centralized management simplicity.
Data Source
AI summary
Methods, computer program products, and systems are presented. The methods include, for instance: a gateway stack that includes a master, a backup, and at least one slave amongst nodes of the GS based on an election pursuant to a gateway stack protocol. The gateway stack provides gateway services for a Network Virtualization over Layer 3 (NVO3) network in a fail-safe manner by utilizing all of the nodes in the gateway stack. A data interface between the gateway stack and a switch is aggregated to evenly distribute inbound packets amongst the nodes of the gateway stack.