Router Configuration Policy Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional routers lack effective mechanisms to detect and prevent configuration errors that are semantically and syntactically correct but violate implementation-specific policies, leading to potential network instability or suboptimal performance.

Innovation Solution

Implementing automated application of implementation-specific configuration policies, such as XSLT scripts or Perl scripts, to validate and alter configuration data before committing changes, ensuring compliance with defined policies and correcting errors proactively.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional commit-based verification process is used, then syntactical and semantic correctness is ensured, but implementation-specific configuration policies are not detected

Engineering Contradiction:
Improveconfiguration correctnessVSAvoidpolicy compliance detection
Core Design Contradiction:
ReliabilityVSMeasurement precision

Solution Approach 1:

The patent applies implementation-specific configuration policies to the candidate configuration data before the commit operation is finalized. This preliminary application of policies detects and corrects configuration errors that violate network-specific requirements, preventing unstable states before they occur. The system validates the configuration against custom rules, service level agreements, and network policies during the commit process, not just for syntactical correctness.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary validation layer between the conventional syntactical/semantic verification and the final commit operation. This intermediary process applies implementation-specific configuration policies as an additional verification step, acting as a mediator that checks both standard correctness and policy compliance before allowing the configuration to be committed to the operational state.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If automated policy application is implemented, then configuration compliance is enhanced, but device complexity increases

Engineering Contradiction:
Improvepolicy complianceVSAvoidconfiguration system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent makes the commit-based configuration system multi-functional by enabling it to perform both conventional syntactical/semantic verification and implementation-specific policy validation through a single integrated mechanism. The same commit infrastructure that validates basic configuration correctness is extended to also apply custom network policies, service level agreements, and implementation-specific rules, eliminating the need for separate verification systems.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system applies configuration policies automatically during the commit process without requiring external intervention or separate validation steps. The router itself performs the policy application and validation, correcting configuration errors proactively before they result in unstable operational states. This self-service approach reduces the need for external configuration management complexity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7376719B1Automatic generation of configuration data using implementation-specific configuration policies
Publication Date: 2008.05.20 JUNIPER NETWORKS INC
  • US7376719B1 patent drawing
  • US7376719B1 patent drawing
  • US7376719B1 patent drawing

AI summary

Techniques are described for application of implementation-specific configuration policies within a network device to generate configuration data. For example, a device, such as a router, may comprise memory to store operational configuration data and candidate configuration data. The device further includes a control unit to apply an implementation-specific configuration policy to alter changes to the candidate configuration data, and commit the altered candidate configuration data to the operational configuration data. In applying the implementation-specific configuration policy, the control unit may insert additional configuration data or replace portions of the candidate configuration data with additional configuration data. In this manner, the device may detect misconfiguration and make changes to the candidate configuration data, thereby performing proactive error correction.