DHCP Relay in Multipod VxLAN Fabric
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Multipod networks face challenges in routing DHCP messages due to overlapping infrastructure identifiers and addresses across separate management domains, leading to ambiguity in traffic routing within a combined tenant space.
Innovation Solution
Incorporating a pod identifier and the originating TEP ID in the DHCP option 82 field of DHCP request and response messages to uniquely identify the source and destination TOR switches, ensuring accurate routing across overlapping underlay TEP IP addresses.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate pods are configured independently with their own infrastructure identifiers, then each pod can be managed separately, but overlapping addresses and identifiers occur when pods are combined into a multipod network
Solution Approach 1:
The patent segments the identifier space by introducing a pod-specific identifier (pod ID) that divides the network addressing into hierarchical levels. Each pod maintains its own independent identifier space, and the pod ID acts as a segmentation key that prevents identifier collisions when pods are combined. This allows separate pod management while ensuring global address uniqueness through the segmented identifier structure.
Solution Approach 2:
The patent adds an additional dimension to the addressing scheme by incorporating pod IDs as a new layer in the identifier hierarchy. Instead of relying solely on flat infrastructure identifiers that may overlap, the solution introduces a vertical dimension (pod ID) that stacks above the horizontal identifier space, creating a multi-dimensional addressing framework that resolves conflicts without restricting independent pod configuration.
2Ease of operation
If DHCP relay is implemented in multipod networks with overlapping addresses, then DHCP functionality can be provided across pods, but routing ambiguity occurs due to overlapping infrastructure identifiers
Solution Approach 1:
The patent introduces pod IDs as intermediary elements that mediate between DHCP messages and the underlying overlapping infrastructure identifiers. When DHCP messages are relayed across pod boundaries, the pod ID acts as a mediator that carries routing information through the overlapping address space, allowing DHCP service availability while preventing routing ambiguity by explicitly tagging messages with their originating pod's identifier.
3Adaptability or versatility
If pervasive SVI with anycast gateway is used across the fabric, then gateway services are universally accessible, but routing precision is lost when addresses overlap between pods
Solution Approach 1:
The patent applies local quality by making the gateway service universally accessible through pervasive SVI while simultaneously applying pod-specific routing precision through pod ID tagging. The anycast gateway provides universal accessibility across the fabric, but the pod ID embedded in DHCP messages provides local routing precision that directs traffic to the correct pod despite address overlaps, allowing both gateway accessibility and routing precision to coexist at different levels of the network hierarchy.
Data Source
AI summary
A packet is generated at a first network connected device for transmission to a destination network device through a network comprising a plurality of pods. At least two of the plurality of pods are within separate management domains, and generating the packet comprises generating the packet with a first identifier and a second identifier. The first identifier indicates a pod of the plurality of pods in which the destination network connected device is located, and the second identifier indicates an identity of the destination network connected device within the pod of the plurality of pods. The packet is transmitted from the first network connected device to the destination network connected device.