
|
Problem Statement No standard method to monitor NETCONF protocol, including session information lock information As NETCONF adds increasing capabilities which can impact configuration management, monitoring becomes increasingly important Examples: Fine-grain locking Impacts/Shortcomings Certain configuration is ‘best-effort’ with failures detected during transactions pessimistic locking is acceptable workaround in some cases Interoperability and Tools development is complicated Multi-vendor, large scale networks require vendor specific monitoring This draft provides basic monitoring for base NETCONF, sessions and notifications intended to alleviate the specific shortcomings above |