NETCONF
Configuration as a transaction instead of CLI keystrokes: XML RPCs over SSH against running and candidate datastores, with YANG defining what is valid. Automation interviews lean on it.
on this pageshowhide
explore
- SSH Transport Layer5 questions
- Datastores5 questions
- RPC Operations6 questions
- Locking and Transactions6 questions
- Model Discovery and Filtering5 questions
- NETCONF vs SNMP5 questions
questions
page 2 of 2Designing a NETCONF change pipeline, when should the source of truth push complete configurations by replace rather than send incremental merge edits?
level: principalimportance: nice to knowfreq 4%
basics
~20 sPush complete configurations by replace only where the pipeline owns everything in scope, since replace deletes whatever its source omits. Elsewhere, send merge edits plus explicit delete or remove; scoped replace on owned subtrees is the usual middle ground.
How would you design YANG model discovery and caching for an automation platform managing thousands of NETCONF devices on differing software releases?
level: principalimportance: nice to knowfreq 4%
basics
~20 sTreat each device's schema as its module set: names, revisions, features and deviations. Cache sources once in a shared store, detect changes per device from the hello's module-set-id or content-id, and fetch missing modules from a URL or <get-schema>.
showing 31–32 of 32