Route Reflector VPN Mapping via Host Hop Address Association
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for determining which virtual private network (VPN) a customer edge (CE) host belongs to in a data center are complex and costly, affecting throughput performance and fault-free operation in server and network virtualization.
Innovation Solution
A communication method where a route reflector directly connected to hosts stores an identifier of the private network with a host's hardware address, receiving notifications and advertisements to simplify the process of identifying VPN membership, using a multiprotocol virtual switching proxy and eliminating the need for PE router-dependent switching tables.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If PE routers are used to propagate routing information through switching tables, then routing information can be propagated between CE hosts, but the system complexity increases and implementation cost rises
Solution Approach 1:
The patent extracts the route reflection function from the PE router and implements it directly in the CE host. This removes the need for complex switching tables in PE routers, as the route advertisement and VPN identification are handled autonomously by each CE host through BGP route reflection mechanisms.
Solution Approach 2:
Each CE host autonomously identifies its own VPN membership and advertises routes with appropriate VPN identifiers without requiring external PE router intervention. The host self-manages its routing information and VPN association, eliminating the need for centralized switching table management.
2Reliability
If PE routers maintain switching tables for traffic forwarding, then traffic can be forwarded between CE hosts, but throughput performance cannot be guaranteed
Solution Approach 1:
The patent removes the traffic forwarding decision logic from PE routers and implements it directly in CE hosts. Each host determines the destination PE router based on its own routing table and VPN identifier, enabling direct traffic forwarding without PE router intervention and thus guaranteeing throughput performance.
Solution Approach 2:
CE hosts pre-populate their routing tables with destination PE router identifiers and VPN associations through route advertisement. This preliminary setup enables direct traffic forwarding without real-time lookup in PE router switching tables, ensuring guaranteed throughput performance.
3Reliability
If complex switching tables are implemented in PE routers, then routing information can be managed, but implementation cost increases
Solution Approach 1:
The patent extracts the routing information management function from PE routers and implements it in CE hosts using standard BGP route reflection. This eliminates the need for proprietary switching table implementations in PE routers, reducing hardware costs and simplifying the overall system architecture.
Solution Approach 2:
The patent uses standard BGP route reflection mechanisms that can be implemented on general-purpose hardware, replacing specialized switching table infrastructure. This universal approach reduces implementation costs while maintaining routing information management capabilities through software-based solutions.
Data Source
Figure 1~4
Figure 5
Figure 6~7
AI summary
The invention relates to a communication method implemented by a route reflector (RR) belonging to a computer system (SI) comprising at least one server (SERV-1, SERV-2) in which a virtual proxy (PR-S, PR-D) and a host (CE-S, CE-D) are connected. Said method comprises, for each host, a set of steps of: - storing (E40) an identifier of a private network of the source and destination hosts, - receiving (E120), from the proxy connected to said host, a notification comprising a hardware address (CE-S MAC@, CE-D MAC@) and an IP address of the host, referred to as "hop address" (CE-S NH@, CE-D NH@), - verifying (E140) a match between said hop address and one or more other IP addresses, - if the match verification is negative, storing (E150) said hop address, - receiving (E170), from the host, an announcement message comprising the routes accessible via said hop address, - storing (180) said announced routes.