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.
I've been able to successfully deploy various VMs via REST API on the NFVIS-based ENCS platform. I've not however been able to deploy the VM with a bootstrapped configuration. My python script appears as follows:import requestsfrom requests.auth im...
I've created a service template using REQUESTS as follows:import requestsfrom requests.auth import HTTPBasicAuthurl = ('http://x.x.x.x:8080/api/running/services')headers = {'Content-Type': 'application/vnd.yang.data+xml'}content = open('af.xml', 'rb'...
Is there a way to fetch an individual SSH key via REST API in NSO?For example, the following API call will fetch SSH keys for all discovered devices:http://x.x.x.x:8080/api/operations/devices/fetch-ssh-host-keysIs there an API that will do the same f...
Hello, I've added a device to NSO as follows:address X.X.X.X;port 22;authgroup NSOAUTH;device-type { cli { ned-id cisco-ios-xr; protocol ssh;state { admin-state unlocked;Note that the device is reachable via IP ...
Is there a way to load a device directly into NSO via REST API?For example, a device can be loaded via configuration CLI, such as following example, however is there a way to do so via REST API?devices { device TEXAS { address 1.1.1.1; ...
Question was never answered.Note the following:When creating a VM package to include QCOW2 image and supporting files, there is the option to include a configuration file, with tagged variables seeding the configuration. That particular configuratio...
You are correct! I had a faulty variable in the XML that was slightly mis-named from the variable in the YANG model. Once that was fixed, I note that I have to 1st SYNC with the edge device as a prerequisite to pushing out the Service Template. It...
I believe that the problem is with the NED itself. I believe that you're correct in that it needs to be updated in my environment. Note that when I used the exact same discovery configuration, however the target was a physical device running XR 5.2...
