05-10-2017 02:50 AM - edited 03-01-2019 03:50 AM
The VMS YANG models allow us to define a configuration where some of the device configuration can be captured in a custom template while the remainder is part of a service definition. The customer can populate the custom template with anything. The customer has asked if the check-sync can distinguished between a "protected" part of the configuration verses a device CLI change that is benign and can be accepted as part of the custom template.
Seems the device NED can only distinguish between what is in CDB relative to the device configuration but it can"t distinguish between important and unimportant configuration deltas.
Would each configuration element need to be marked in the YANG service model as protected or unprotected?
Solved! Go to Solution.
05-10-2017 02:50 AM
Don’t think we have a notion of protected/unprotected. For some of the NEDs we actually just hash the entire config to be able compare and compute the check-sync.
The APIC NED comes to mind. It sort of has the notion of protected/unprotected. Basically with the APIC NED, one can spell out the sections of the device tree that is to be managed by NSO (sync’ed into CDB) and the rest is left out.
05-10-2017 02:50 AM
Don’t think we have a notion of protected/unprotected. For some of the NEDs we actually just hash the entire config to be able compare and compute the check-sync.
The APIC NED comes to mind. It sort of has the notion of protected/unprotected. Basically with the APIC NED, one can spell out the sections of the device tree that is to be managed by NSO (sync’ed into CDB) and the rest is left out.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide