cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
124
Views
0
Helpful
0
Replies
Beginner

Possible to augment yang beyond config path

I'm trying to work through augmenting a NED yang beyond the config namespace to include "metadata" if you will when viewed through NSO.  When trying to commit, however, I'm getting an "element not found" which means that the yang model I've created is attempting to be pushed down to the device, which is not the intent. 

 

This leads me to question if it is even possible to do such a thing.  If I move the augment back in the path to /ncs:devices/ncs:device it commits fine - which I guess makes sense since this information is not propagated down through the NED. 

 

Is there a way to augment information on, say interfaces, without pushing those configurations down to the device level and without having to define a whole service that just really maintains some metadata about said interface?  I've tried tailf:cdb-oper { tailf:persistent true } but no joy there ...

 

My very simple yang is attached.