Guys, Wchich Jinja version / features are used by Cisco DNAC in templates? I've tried some commands, like 'regex_search' filters, and it does not work or cause errors. thanks,robert
Hi,How could we get backpointers for the configuration of the device over RESTCONF?For example:rslaski@ncs# show running-config devices device AR_DCI230 config dcs:interface Vxlan 1 | display service-meta-data
devices device AR_DCI230
config
! Ref...
Guys,In case where YANG model changes, so that necessary service template adjustments are necessary, is there any way for the service to use both old and new NED models in the template? For example, old NED uses leaf-list: <ip xmlns="http://ta...
It would be appreciated if someone explained the NSO behavior described below to me. I am deploying a service instance which enables interface SVI on Cisco Neuxs, which causes the device to enable 'Vlan 1' SVI - this one is, however, not explicitly c...
Hello wise guys, When learning to code with NSO, I move three steps forward, just to realize I did not understand the thing, so I have to go two steps back. The same story I had with basic YANG, callbacks, XML context, and a number of topics, so now ...
@Gabriel Zapodeanu I am aware of this and I am using 1 as parallelism parameter. Some resources can be created (ex. site), others (ex. SDA) fail with 429. There's something seriously broken in 2.3.7.4 or the provider.
@bigevilbeard @Gabriel Zapodeanu I am facing exactly the same issue but with DNAC Terraform provider, so I have no control over how it sends API calls internally. Sorry to say, but the DNAC API quality is totally crappy in all aspects (bugs, performa...
Thanks @vleijon for the hint, it works now. The fun fact in this case was the YANG model has changed, however the resulting XML did not, but even then I had to distinguish both versions to avoid package load error <interface xmlns="http://tail...
Yes, I did today. I can send the TAC a sample final and complete configuration, as advised, but certainly it will not pass the test (I know there are other, less important issues in both NEDs that I am using). This will in turn open a thread of quest...
Ok, I think I've found the issue, and it has nothing to do with service code. The problem is with faulty NED YANG model of the device - it specifies the VRF inside 'Vxlan1' as container: container interface {
// interface Vxlan *
list Vxla...
