Multi-VRF Edge Gateway Packet Redirection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing edge gateway configurations face challenges in redirecting packets to multiple services using the same IP address pairs, especially when these services belong to different gateways in a datacenter, as it complicates packet routing and increases bandwidth requirements.

Innovation Solution

Implementing multi-VRF (Virtual Routing and Forwarding) and multi-service insertion techniques on edge gateways, which involve creating rule and policy tables based on configuration data to manage packet redirection, using VRF identifiers to segment traffic, and BFD (Bidirectional Forwarding Detection) for determining service machine reachability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple services are inserted using the same IP address pairs on different gateways, then service consolidation and resource utilization are improved, but packet routing complexity and configuration difficulty increase

Engineering Contradiction:
Improveservice consolidationVSAvoidrouting complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the routing functionality by introducing VRF (Virtual Routing and Forwarding) instances that create separate routing tables and forwarding policies for different services. Each service is assigned to a specific VRF instance, allowing multiple services to share the same physical gateway infrastructure while maintaining distinct routing paths and IP address pairs, thereby reducing routing complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a service insertion component as an intermediary layer between the edge gateway and service virtual machines. This component maintains policy tables that map services to specific VRF instances and IP address pairs, automatically determining the correct routing path without requiring complex manual configuration, thus simplifying the overall system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of energy

If multiple services are inserted on edge gateways with same IP address pairs, then bandwidth requirements are reduced, but packet redirection accuracy and service differentiation become difficult

Engineering Contradiction:
Improvebandwidth requirementsVSAvoidpacket redirection accuracy
Core Design Contradiction:
Loss of energyVSMeasurement precision

Solution Approach 1:

The patent applies local quality by assigning unique IP address pairs to each service within its specific VRF context. While services may share the same physical gateway and potentially overlap in IP space across different VRFs, each service maintains its own localized IP addressing scheme and routing policy, ensuring accurate packet redirection to the correct service virtual machine without confusion.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent adds a new dimension to packet routing by introducing VRF instance identifiers as an additional layer of differentiation. Instead of relying solely on IP address pairs, the system uses a tuple combination of VRF instance ID, service identifier, and IP address pair to uniquely identify routing paths. This multi-dimensional approach enables accurate service differentiation while allowing IP address reuse across different VRFs, thereby reducing bandwidth requirements.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS12088493B2Multi-VRF and multi-service insertion on edge gateway virtual machines
Publication Date: 2024.09.10 VMWARE INC
  • US12088493B2 patent drawing
  • US12088493B2 patent drawing
  • US12088493B2 patent drawing

AI summary

In an embodiment, a method for a VRF and multi-service insertion on edge gateways is described. In an embodiment, the method comprises obtaining a rule configuration. Based on, at least in part, the rule configuration, a rule table is created. The rule table comprises rule data records, wherein a rule data record comprises packet attributes and a redirection identifier. A policy configuration comprising policy records is obtained. Each policy record comprises a redirection identifier, a next_hop, and an address pair for interfaces. A mapping between VRF identifiers and address pairs is generated. Based on, at least in part, the mapping and the policy configuration, a policy table is generated. The policy table comprises table records, wherein a table record comprises a redirection identifier, a next_hop, and an address pair. The rule and policy tables are used to redirect a packet from an edge gateway to a service virtual machine.