Network Device Configuration Management via Segmented Databases

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Network administrators face challenges in managing network devices, particularly in maintaining synchronized configuration information across devices and a central management system, leading to duplicate configuration objects with different values and increased management time, especially when dealing with expanded or modified networks.

Innovation Solution

A central management system and network devices implement a method to store shared and device-specific configuration objects in local and central databases, allowing for synchronized updates and prioritization of configuration processing, while rejecting unauthorized changes to shared configuration objects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If configuration information is maintained at both network devices and central management system, then accessibility and quick problem-solving at field level is improved, but duplicate configuration objects with different values may occur increasing management complexity

Engineering Contradiction:
Improvequick problem-solving at field levelVSAvoidmanagement complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments configuration objects into two types: shared configuration objects stored in the central configuration database and device-specific configuration objects stored only in the network device's local configuration database. This segmentation allows field personnel to access and modify device-specific configurations quickly while shared configurations maintain centralized control, thus resolving the contradiction between local accessibility and centralized management consistency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a priority list as an intermediary mechanism that mediates between shared and device-specific configuration objects. The priority list specifies the processing order, ensuring that when both types of configurations exist, the system knows which to apply first. This intermediary structure prevents conflicts and duplicate management issues while maintaining both local and central configuration capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Extent of automation

If configuration updates are pushed from central database to network devices, then centralized control is improved, but time required for propagation across all devices increases

Engineering Contradiction:
Improvecentralized controlVSAvoidconfiguration propagation time
Core Design Contradiction:
Extent of automationVSLoss of time

Solution Approach 1:

By segmenting configuration objects into shared and device-specific categories, the system can push updates selectively. When a shared configuration object is updated, only network devices that have this specific configuration object in their priority list receive the update, rather than pushing to all devices. This targeted approach reduces propagation time while maintaining centralized control over shared configurations.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If device-specific configuration objects are allowed, then flexibility and customization per device is improved, but synchronization and consistency across the network becomes more difficult

Engineering Contradiction:
Improvedevice customization flexibilityVSAvoidconfiguration consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The priority list acts as an intermediary that ensures consistent and predictable configuration application across the network. By specifying the processing order of configuration objects, the system guarantees that shared configurations and device-specific configurations are applied in a deterministic sequence, maintaining network-wide consistency while allowing device-level customization.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent applies local quality by allowing device-specific configuration objects to exist only at individual network devices, while shared configuration objects exist centrally. This enables each device to have customized configurations where needed (local quality) while maintaining overall network consistency through shared configurations, thus resolving the contradiction between flexibility and consistency.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9491047B2Managing network devices
Publication Date: 2016.11.08 PALO ALTO NETWORKS INC
  • US9491047B2 patent drawing
  • US9491047B2 patent drawing
  • US9491047B2 patent drawing

AI summary

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for managing network devices. A central management system stores shared configuration objects in a central configuration database. A network device stores shared configuration objects and device-specific configuration objects in a local configuration database. The local configuration database's shared configuration objects correspond to shared configuration objects in the central configuration database. The network device can be configured locally or using the central management system.