Public Cloud Router for Hybrid Network Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In hybrid cloud environments, routing data through an enterprise router located in a private cloud is inefficient when data must travel over the internet, as it requires traffic to return to the private cloud before reaching the router, leading to inefficiencies and the need for manual gateway reconfiguration during workload migrations between public and private clouds.
Innovation Solution
A router is placed in the public cloud that replicates the functionality of the enterprise router by intercepting ARP requests and fabricating responses containing the MAC address of the public cloud router, allowing seamless routing and automatic gateway configuration through a Layer 2 secure tunnel and Default Gateway Extension Module.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is routed through an enterprise router in a private cloud, then network security and enterprise network policies are maintained, but routing efficiency deteriorates because traffic must return to the private cloud before reaching the router
Solution Approach 1:
A router is placed in the public cloud that replicates the functionality of the enterprise router. This intermediary router intercepts ARP requests and fabricates responses containing its own MAC address, allowing traffic to be routed through the public cloud router instead of returning to the private cloud, thus maintaining security policies while improving routing efficiency
Solution Approach 2:
The public cloud router replicates the enterprise router's functionality by intercepting ARP requests and fabricating responses with the public cloud router's MAC address. This creates a copy of the routing function in the public cloud, eliminating the need for traffic to return to the private cloud while maintaining network policies
2Adaptability or versatility
If workloads are migrated between public and private clouds, then cloud elasticity and scalability are improved, but manual gateway reconfiguration is required which increases operational complexity
Solution Approach 1:
The system automatically handles gateway configuration through ARP request interception and response fabrication. When workloads are migrated between clouds, the Default Gateway Extension Module automatically updates ARP caches with the appropriate router MAC address, eliminating the need for manual gateway reconfiguration and reducing operational complexity
Data Source
AI summary
Many hybrid cloud topologies require virtual machines in a public cloud to use a router in a private cloud, even when the virtual machine is transmitting to another virtual machine in the public cloud. Routing data through an enterprise router on the private cloud via the internet is generally inefficient. This problem can be overcome by placing a router within the public cloud that mirrors much of the routing functionality of the enterprise router. A switch configured to intercept address resolution protocol (ARP) request for the enterprise router's address and fabricate a response using the MAC address of the router in the public cloud.


