Network Configuration Server Duplicate Address Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing computer network configurations often result in misconfigurations such as duplicate IP and MAC addresses, leading to network failures, even with the use of Dynamic Host Configuration Protocol (DHCP), due to administrative errors or device malfunctions, which can be complex and costly to resolve.

Innovation Solution

A system and method that employs a server-based approach to detect and correct network misconfigurations by broadcasting configuration requests, using identifier key values to uniquely address nodes, and optionally correcting duplicate address issues, ensuring proper network operation without the need for manual administration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual network configuration is used, then network deployment is simple, but misconfigurations such as duplicate IP and MAC addresses occur frequently

Engineering Contradiction:
Improvenetwork configuration accuracyVSAvoidconfiguration system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The network system performs self-configuration through automatic detection and correction mechanisms. The server automatically detects duplicate addresses, identifies misconfigured devices, and guides them through reconfiguration without requiring manual administrator intervention, allowing the system to configure itself while maintaining high accuracy

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements continuous monitoring and feedback loops where the server periodically checks network configuration status, detects misconfigurations, and triggers correction procedures. This feedback mechanism ensures configuration accuracy is maintained over time without increasing operational complexity for users

Inventive Principle:
Principle #23Feedback

2Reliability

If automatic detection and correction mechanisms are implemented, then network misconfigurations are reduced, but system complexity increases

Engineering Contradiction:
Improvenetwork operation reliabilityVSAvoidnetwork management system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

A server acts as an intermediary between network devices and administrators. The server handles the complex tasks of detecting duplicate addresses, identifying misconfigured devices, and coordinating reconfiguration, while administrators only need to initiate simple commands. This intermediary approach maintains high reliability while keeping the user-facing interface simple

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary detection and correction actions automatically before misconfigurations can cause network failures. By proactively identifying and resolving duplicate address issues before they impact network operation, the system maintains high reliability without requiring complex real-time intervention mechanisms

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If simplified networking equipment is used, then network deployment becomes easier, but administrative errors still occur

Engineering Contradiction:
Improvenetwork deployment easeVSAvoidconfiguration accuracy
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The simplified networking equipment incorporates self-configuration capabilities where devices automatically detect and report their configuration status to the server. This allows novice administrators to deploy networks easily while the system automatically ensures configuration accuracy through its detection and correction mechanisms

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system provides continuous feedback to simplified networking equipment about configuration status. When misconfigurations are detected, the server communicates with the affected devices to guide them through automatic reconfiguration, maintaining both ease of operation and configuration accuracy

Inventive Principle:
Principle #23Feedback

4Reliability

If manual configuration verification is performed, then misconfigurations can be detected, but network deployment time increases

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidnetwork deployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs configuration verification as a preliminary automatic action during the network setup process rather than requiring separate manual verification steps. The server automatically checks for duplicate addresses and misconfigurations during deployment, eliminating the need for additional manual verification time while maintaining high accuracy

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The configuration detection and verification processes run continuously in the background without interrupting network deployment operations. The server monitors configuration status throughout the deployment process, allowing verification to occur continuously rather than requiring separate time-consuming manual checks

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS9118552B2System and method for computer network configuration and operation
Publication Date: 2015.08.25 NCOMPUTING GLOBAL INC
  • US9118552B2 patent drawing
  • US9118552B2 patent drawing
  • US9118552B2 patent drawing

AI summary

A system for simplifying the configuration and administration of computer networks. A the server system first sends a broadcast message out to the other network nodes on the computer network to learn configuration of each other network nodes on the local network. Next, network software within each other network node (not shown) responds to the broadcast message with a response containing configuration information and an identifier key value. In one embodiment, the identifier key value may be a randomly generated number. The server system then builds a table of network nodes using the information received in the response messages sent in response to the broadcast message. The server may then communicate with systems having duplicate addresses using the identifier key value. In some embodiments, the server system may send request messages to one or more network nodes specifying a network configuration change.