DHCP Server Network-Based IP Configuration Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing DHCP server recovery techniques are cumbersome and resource-intensive, relying heavily on manual backups and static IP configurations, which can lead to stale data and burden customers with complex recovery strategies, especially in large networks with frequent changes and growth.

Innovation Solution

Implementing network-based DHCP server recovery methods that allow failed DHCP servers to directly retrieve current IP configuration information from the network, reducing reliance on backups and enabling automatic, seamless recovery with minimal intervention, even in standalone or redundant configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual backups and static IP configurations are used for DHCP server recovery, then reliability of data recovery is improved, but device complexity and ease of operation deteriorate

Engineering Contradiction:
Improvedata recovery accuracyVSAvoidrecovery strategy complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The DHCP server automatically recovers its own configuration by querying network elements (routers, switches) for their IP address assignments. The server sends queries to network elements, receives responses containing IP configuration data, and repopulates its database without requiring manual intervention or complex backup procedures.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements a feedback mechanism where the DHCP server queries network elements for their current IP configurations and uses this feedback information to reconstruct its database. This continuous feedback loop ensures the server recovers accurate, up-to-date configuration information automatically.

Inventive Principle:
Principle #23Feedback

2Measurement precision

If frequent backups are performed to ensure accurate data, then data accuracy is improved, but loss of time and productivity deteriorate

Engineering Contradiction:
Improvedata accuracyVSAvoidtime for frequent backups
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

Network elements maintain their IP configuration information in advance, and the DHCP server queries this pre-stored information when needed. The preliminary action of network elements retaining configuration data eliminates the need for frequent backups while ensuring data accuracy is maintained.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Instead of creating backup copies of the DHCP database, the system queries network elements for their configuration information. The network elements serve as living copies of the configuration data, providing accurate information on demand without requiring time-consuming backup operations.

Inventive Principle:
Principle #26Copying

3Reliability

If redundant DHCP servers with backup sources are deployed, then reliability is improved, but device complexity and use of energy deteriorate

Engineering Contradiction:
ImproveDHCP server availabilityVSAvoidredundant configuration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Each DHCP server independently recovers its own configuration by querying network elements, eliminating the need for complex redundant backup infrastructure. The servers self-rescue without requiring a dedicated backup server or complex synchronization mechanisms between redundant systems.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10862741B2Network-based IP configuration recovery
Publication Date: 2020.12.08 CIENA CORP
  • US10862741B2 patent drawing
  • US10862741B2 patent drawing
  • US10862741B2 patent drawing

AI summary

A network-based recovery method implemented by one or more nodes configured to manage Internet Protocol (IP) configuration in a network includes during normal operation, discovering clients, providing IP configuration information to each of the clients, and maintaining a list of the clients and a database of the IP configuration information; responsive to a failure of any of the one or more nodes, sending a request to each client in the list for that client's associated IP configuration information; and, responsive to receiving a response from the sending to each client, repopulating the database with the client's associated IP configuration information.