IP Unnumbered Interface Provisioning via Loopback Relay
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In VXLAN-EVPN based programmable fabric deployments, power-on auto-provisioning (POAP) over in-band interfaces fails due to the absence of DHCP relay functionality when using IP unnumbered interfaces, as there are no regular layer-3 interfaces for configuring DHCP relay, hindering the operation of in-band POAP.
Innovation Solution
Configuring DHCP relay on core-facing interfaces, enabling proxy-ARP, and redistributing routes via BGP to facilitate POAP without manual routes, allowing the new leaf node to obtain a temporary IP address and connect to a file server for configuration files, thereby automating the day-0 bring-up process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If IP unnumbered interfaces are used to simplify IP address management, then IP address management is simplified, but DHCP relay functionality cannot be configured on in-band interfaces
Solution Approach 1:
The patent introduces a loopback interface as an intermediary element that provides a regular layer-3 interface for DHCP relay configuration. This loopback interface acts as a mediator between the IP unnumbered interfaces and the DHCP relay functionality, allowing DHCP relay to be configured on the loopback interface while the core-facing interfaces remain as IP unnumbered interfaces. This resolves the contradiction by providing both the simplified IP address management of unnumbered interfaces and the DHCP relay configuration capability through the intermediary loopback interface.
2Reliability
If traditional provisioning via mgmt0 interface is used, then provisioning works reliably, but in-band POAP preference cannot be satisfied
Solution Approach 1:
The patent makes the loopback interface multi-functional by using it both for DHCP relay configuration and for supporting in-band POAP operations. The loopback interface serves multiple purposes: it provides a layer-3 interface for DHCP relay, maintains routing table state, and enables in-band POAP functionality. This multi-functionality allows the system to satisfy the preference for in-band POAP while maintaining reliable provisioning capabilities.
3Ease of operation
If in-band POAP is enabled without DHCP relay functionality, then in-band interface usage is achieved, but POAP operation fails
Solution Approach 1:
The loopback interface serves as an intermediary that enables DHCP relay functionality to operate on in-band interfaces indirectly. By configuring DHCP relay on the loopback interface rather than directly on the in-band interfaces, the system achieves in-band interface usage while maintaining POAP operation reliability through the intermediary loopback interface that provides the necessary layer-3 routing context.
Data Source
AI summary
In one implementation, a method performed by a first node with interfaces configured as IP unnumbered interfaces sharing a single IP address and to communicate with a DHCP-associated second node includes: obtaining a first message that indicates a configuration status of a third node at a respective interface; obtaining a second message for the third node from the DHCP-associated second node that includes a temporary IP address for the third node and an indicator of a file server; obtaining a third message associated with the third node that includes the temporary IP address, the third message requests address information for the file server; and configuring the third node by establishing a connection between the third node and the file server to transfer at least one configuration file, where configuring the third node includes providing the temporary IP address to the DHCP-associated second node via BGP.