Network Node IP Self-Configuration Without DHCP
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network nodes face challenges in determining an IP configuration when a DHCP server is unavailable or temporarily absent, leading to network connectivity issues and manual configuration difficulties, especially in large-scale deployments.
Innovation Solution
The network node is configured to determine an IP configuration using information elements from OSI-layer-2 messages, such as ARP broadcast messages, by associating these elements with parameters from a lookup table or performing calculations, allowing it to derive necessary configuration parameters like IP address, subnet mask, and sender system address even in the absence of a DHCP server.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If DHCP server is used to assign IP addresses, then IP configuration automation is improved, but system complexity and single point of failure risk increase
Solution Approach 1:
The network node autonomously determines its own IP configuration by extracting information from OSI-layer-2 messages and using local lookup tables, eliminating the need for external DHCP server intervention. The node performs self-configuration by calculating IP addresses from MAC addresses and retrieving subnet masks from pre-stored tables, thereby reducing system complexity while maintaining automation.
Solution Approach 2:
The network node pre-stores lookup tables containing subnet mask information associated with different OSI-layer-2 message types before connecting to the network. This preliminary preparation enables the node to quickly determine its IP configuration without real-time server intervention, reducing both complexity and failure risk while maintaining automated configuration.
2Ease of operation
If DHCP server is deployed in large-scale networks, then centralized management is improved, but deployment cost and scalability issues arise
Solution Approach 1:
The centralized IP management functionality is segmented between the network operator (who defines lookup tables with subnet masks for different message types) and individual network nodes (which store and use these tables locally). This segmentation allows each node to independently determine its configuration based on the message type it receives, enabling scalable deployment across many nodes without requiring a centralized DHCP server for each node.
Solution Approach 2:
The lookup table information is copied from the network operator's configuration to each network node's local storage. This copying mechanism allows nodes to have identical or differentiated configuration data without requiring continuous connection to a central server, enabling deployment in locations where DHCP servers are unavailable and improving scalability to large numbers of nodes.
3Measurement precision
If manual IP configuration is performed, then configuration accuracy is improved, but labor cost and time consumption increase
Solution Approach 1:
The network node automatically determines its own IP configuration by extracting the message type from received OSI-layer-2 messages, calculating the IP address from its MAC address, and retrieving the appropriate subnet mask from locally stored lookup tables. This self-service approach eliminates manual configuration labor while maintaining accuracy through deterministic calculation and pre-stored reference data.
Solution Approach 2:
The system changes the parameter determination method from manual input to automated calculation and table lookup. The IP address is calculated by transforming the MAC address, and the subnet mask is selected by changing parameters based on the OSI-layer-2 message type, thereby achieving accurate configuration automatically without manual intervention.
Data Source
Figure 1~2
Figure 3~4
Figure 5
AI summary
The disclosure pertains to a network node configured to determine an Internet Protocol, IP, configuration, or a part thereof, for an IP network connection. The network node may be configured to receive an Open Systems Interconnection, OSI, -layer-2 message comprising one or more information elements. The OSI-layer-2 message may be multicast message or a broadcast message. The network node may further be configured to run an IP configuration determination process using one or more of the one or more information elements of the OSl-layer-2 message. The one or more information elements from the OSI-layer-2 message serve as input for the IP configuration determination process to determine an IP configuration for the network node to be reachable over the IP network connection. The disclosure also pertains to a network system comprising one or more of such network nodes.