Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi
Is there any way to define custom error-message for data types in yang? For example:
type inet:ipv4-address { error-message "Invalid IPv4 address for loopback0"; }
PS - the above produces an error: unexpected keyword 'error-message'
I'm trying to build netconf NED for Nokia (ALU) device. Following the Pioneer approach I encounter an Internal compiler error (please see below). I'm going to guess it's due to problems in Nokia's yang but my question is how can I go about troublesho...
HiBuilt the netconf NED for latest SROS 15.0R4 using yang models provided by Nokia. Attempting to sync-from the device gives an error, but using Pioneer get-config works. I investigated the raw netconf traces, and the issue seems to be due to followi...
Sorry there are probably multiple questions below, I try to follow them in a logical order. The main problem/question is that Pioneer cannot fetch/download the yang modules from the device, however there are other anomalies seen too as I mention belo...
yeah good find... I'm not sure how errcode.xml is imported and used inside ncs. If someone could shed more light on it, that would be great... I wish there was some documentation around it (maybe there is?)...
The use-case is simple... we don't nec...
Here's a sample of error-message NSO would return to NB API by default:
"error-message": "invalid value for: loopback0v4 in /myservice:myservice[myservice:device='Router24']/myservice:loopbacks/myservice:loopback0v4: \"10.10.10.1000\" is not a vali...
Thanks, yes I have seen that part of RFC but it seems in all the examples error-message is applicable when a condition is evaluated on datatype (for example: range, pattern, etc.). I'm not trying to impose further conditions on "inet:ipv4-address", r...
Given that to fully add the device to NSO, the ssh key of the device needs to be fetched too, has anyone figured out how to handle that part as well via REST API?
admin@ncs> request devices device R02 ssh fetch-host-keys
the key fetched from ab...
