Location Identifier Forwarding for Data Center Routing Scalability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Data centers face an explosion in the number of routes, overwhelming routers between VLAN segments as they store routes to machines and VTEPs, leading to resource constraints in data planes, which struggle to implement forwarding rules for every machine or VTEP on every VLAN.
Innovation Solution
Location identifier-based forwarding reduces the forwarding data required in data planes by using a single forwarding rule based on location identifiers and VNIDs, allowing local routers to encapsulate and forward packets efficiently without needing extensive routing information for remote VTEPs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If routers store routes to every machine and VTEP on every VLAN, then complete routing information is available, but router resource constraints are overwhelmed
Solution Approach 1:
The patent segments routing information by introducing location identifiers that group multiple VTEPs under a single location. Instead of storing individual routes to every VTEP, routers store routes to locations, and each location maintains a mapping of VTEPs to the location identifier. This segmentation reduces the routing table size while preserving complete routing capability through the location identifier intermediary.
Solution Approach 2:
The patent introduces location identifiers as an intermediary between VTEPs and router routing tables. The location identifier acts as a mediator that aggregates multiple VTEP routes into a single routing entry. Routers use the location identifier to reach remote locations, and the actual VTEP mapping is maintained at the location level, reducing the burden on router data planes.
2Manufacturing precision
If forwarding rules are implemented for every machine and VTEP, then precise packet forwarding is achieved, but data plane resources are exhausted
Solution Approach 1:
The patent merges multiple forwarding rules into a single location-based forwarding rule. Instead of creating individual forwarding entries for each VTEP or machine, the system creates a single forwarding rule that uses the location identifier to route packets to the remote location. The precise VTEP mapping is reconstructed at the destination location, maintaining forwarding precision while reducing data plane resource consumption.
Solution Approach 2:
The patent adds a new dimension to packet forwarding by introducing location identifiers as an additional routing dimension. Instead of relying solely on VTEP addresses for forwarding decisions, the system uses location identifiers to determine the destination location, then uses the original VTEP address for final delivery. This dimensional approach separates location routing from VTEP-specific forwarding, reducing the complexity of data plane rules.
3Reliability
If extensive routing information is stored for remote VTEPs, then accurate packet delivery is ensured, but scalability is reduced
Solution Approach 1:
The patent segments routing information storage between routers and locations. Routers store only location identifier mappings, while locations store the detailed VTEP-to-location mappings. This segmentation allows the system to scale because routers don't need to maintain extensive VTEP routing information, and locations can independently manage their own VTEP mappings without affecting other locations.
Solution Approach 2:
The patent changes the routing parameter from VTEP addresses to location identifiers. By using location identifiers as the primary routing parameter, the system achieves better scalability because location identifiers are more aggregated and fewer in number compared to individual VTEP addresses. The original VTEP address is preserved in the packet for final delivery, ensuring delivery accuracy while using the location identifier for scalable routing decisions.
Data Source
AI summary
A packet can be sent on a VLAN from a first machine that has a first address on the VLAN to a second machine that has a second address on the VLAN and that is located at a remote location associated with a remote location identifier. A network appliance can use the second address to determine the remote location identifier, can encapsulate the packet in a local segment packet that includes a local VNID and the remote location identifier; and can send the local segment packet to a local router. The local router can use the remote location identifier and the local VNID to determine a remote router and a remote VNID, can encapsulate the packet in an outer packet, which can be a VxLAN packet, that includes the remote VNID, and can send the outer packet to the remote router.