NETCONF Server Factory Defaults Restoration via Centralized Datastore
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for restoring network devices to factory defaults using Network Configuration Protocol (NETCONF) are cumbersome, increasing development difficulty and hindering third-party extension due to each service module storing its own factory defaults data and requiring multiple RPC commands from the NETCONF client.
Innovation Solution
Implementing a dedicated factory defaults datastore within the NETCONF server that stores factory defaults data, allowing the NETCONF server to restore the network device to factory defaults without requiring each service module to register its factory defaults processing function, and enabling the NETCONF client to send a single command for restoration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If each service module stores its own factory defaults data and requires separate RPC commands, then the restoration function can be implemented, but the device complexity and development difficulty increase
Solution Approach 1:
The patent merges the factory defaults data storage from multiple service modules into a single centralized datastore within the NETCONF server. This consolidation eliminates the need for each service module to maintain separate factory defaults, thereby reducing development complexity while preserving the restoration function. The centralized approach allows a single RPC command to restore all service modules simultaneously.
Solution Approach 2:
The NETCONF server is enhanced with universal factory defaults management capability that serves all service modules. Instead of each module having specialized restoration logic, the NETCONF server provides a unified restoration mechanism that can restore the entire network device regardless of which service module needs restoration, simplifying the overall system architecture.
2Reliability
If each service module registers its factory defaults processing function, then the restoration can be performed, but third-party extension becomes difficult
Solution Approach 1:
The patent extracts the factory defaults processing function from individual service modules and places it in the NETCONF server. This extraction removes the barrier to third-party extension because new service modules no longer need to register complex restoration functions - they simply inherit the universal restoration capability provided by the NETCONF server, making the system more adaptable and extensible.
3Reliability
If multiple RPC commands are delivered to different service modules, then precise restoration control is achieved, but maintainability deteriorates
Solution Approach 1:
The patent combines multiple service module restoration operations into a single NETCONF server operation. Instead of delivering separate RPC commands to each service module, the system delivers one restoration command to the NETCONF server, which then coordinates the restoration of all service modules. This significantly improves maintainability by reducing the number of command delivery points and simplifying the restoration process.
Data Source
AI summary
Embodiments of the present disclosure disclose a method and an apparatus for restoring a NETCONF server to factory defaults, and relate to the field of configuration management technologies. A NETCONF server receives a command for restoring to factory defaults sent by a NETCONF client, where the command for restoring to factory defaults is a remote procedure call (RPC) command that is based on a Yang model of the NETCONF for restoring the NETCONF server to the factory defaults. The NETCONF server replaces data in the running configuration datastore with factory defaults of the NETCONF server according to the command for restoring to factory defaults.