cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
180
Views
0
Helpful
1
Replies
Highlighted
Contributor

Check-sync Qualifiers

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?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Contributor

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.

View solution in original post

1 REPLY 1
Highlighted
Contributor

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.

View solution in original post