NETCONF Configuration Lock Handling for Multi-Device Conflicts
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network management systems face issues when multiple devices attempt to operate the same configuration data set, leading to conflicts that disrupt service processing due to forced session disconnections or prolonged waiting times.
Innovation Solution
A network management method that involves a first device notifying a second device of a conflicting lock request from a third device, allowing the second device to release the lock promptly, thereby enabling the third device to use the configuration data set without disruption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a configuration data set is locked by one client to ensure exclusive operation, then data consistency is improved, but service processing efficiency deteriorates due to forced disconnections or long waiting times
Solution Approach 1:
The system performs preliminary actions by notifying waiting clients of upcoming lock releases before the lock is actually released. When client A releases the lock on the configuration data set, the system proactively sends a notification message to client B (which is waiting) before client B can attempt to acquire the lock. This preliminary notification allows client B to prepare for lock acquisition, reducing the waiting time and improving service processing efficiency while maintaining data consistency through the exclusive lock mechanism.
2Reliability
If a client waits for a locked configuration data set to be released, then data consistency is maintained, but service processing time increases due to prolonged waiting
Solution Approach 1:
The system implements a feedback mechanism where the network management device actively monitors lock status and sends notification messages to waiting clients. When client A releases the lock, the system detects this change and immediately sends a feedback notification to client B. This feedback loop eliminates the need for client B to continuously poll or wait passively, significantly reducing the service processing time while maintaining data consistency through the structured lock-release-notification sequence.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
Embodiments of this application relate to the communications field, and provide a network management method and an apparatus, to reduce impact on a service of a user that is caused when a conflict occurs between operations performed by a plurality of devices on a configuration data set. The method includes: receiving, by a first device, a first request message sent by a second device according to NETCONF, and locking a configuration data set of the first device based on the first request message; receiving, by the first device, a second request message sent by a third device according to NETCONF, where the second request message is used to request to modify or lock the configuration data set; and sending, by the first device, a first response message to the second device, where the first response message is used to notify that the third device requests to modify or lock the configuration data set. The embodiments of this application are used in a scenario in which a conflict occurs when a plurality of devices use a same configuration data set according to NETCONF.