Ncs-netsim list for /home/vagrant/nso-run/netsim er_scripts creating ~$ lsĪdmin connected from 10.0.2.2 using ssh on confĮntering configuration mode # devices ~$ cd ncs-netsim list er_scripts creating /home/vagrant/.virtualenvs/postactivate er_scripts creating /home/vagrant/.virtualenvs/preactivate er_scripts creating /home/vagrant/.virtualenvs/postdeactivate er_scripts creating /home/vagrant/.virtualenvs/predeactivate er_scripts creating /home/vagrant/.virtualenvs/postrmvirtualenv er_scripts creating /home/vagrant/.virtualenvs/prermvirtualenv er_scripts creating /home/vagrant/.virtualenvs/postmkvirtualenv er_scripts creating /home/vagrant/.virtualenvs/premkvirtualenv er_scripts creating /home/vagrant/.virtualenvs/initialize er_scripts creating /home/vagrant/.virtualenvs/postmkproject er_scripts creating /home/vagrant/.virtualenvs/premkproject Memory usage: 26% IP address for eth0: 10.0.2.15 Usage of /: 6.3% of 61.80GB Users logged in: 0 System information as of Fri Jun 28 17:57: If you are using vagrant, check what ports are mapped for the HTTP API (usually 8080) so your REST call path can be correct. See instructions here for changing collection variables.
#Netsim 10 vs 11 update
I used localhost and the vagrant port for my set up, if you are not running on vagrant you should likely update the port to 8080. Once you import the collection, you may want to change the collection variables I made for the NSO IP and Port. The collection is in this repository called NSO RESTCONF NORTHBOUND API.postman_collection.json.
#Netsim 10 vs 11 how to
You can learn how to import the collection here. I created a Postman collection, which is an organized set of RESTCONF API calls to your NSO server. The default port for NSO is 8080, but since I am using vagrant it is saved as 8009 in the collection. You will need to import the collection, and may need to change the NSO IP and Port. I am using Postman Version 6.7.4 on my laptop on the OS X side, running it against the port exposed from the virtual machine.
I will use these NEDs for the example, but remember they should not be used on real devices.
#Netsim 10 vs 11 for free
The Vagrant File sets up a few netsims with the non-production dummy NEDs ( cisco-ios-cli-3.8 rather than cisco-ios) which come for free with the NSO install.
#Netsim 10 vs 11 install
I am using the NSO Vagrant local install NSO, with NSO version 5.1.0.1 on Ubuntu, from my Macbook Pro OS X 10.14.5. They are different northbound APIs, and both still exist (at the time of this writing), but for all intensive purposes, you should be starting your development against the RESTCONF one, not the REST one.įrom the Northbound API Guide: TLDR: The REST API is deprecated and will be removed in NSO 5.3, use the RESTCONF API instead. After the RESTCONF standards were set, the focus and recommendation for using the NSO REST based API is to use the RESTCONF, not the REST API. The NSO application has both, the REST API was created before the RESTCONF industry RFC standards were created.
REST API vs RESTCONF APIįirst off, the NSO BU recommends using the RESTCONF API instead of the REST API. The parlance of network engineers expecting a platform having an API is to look at the REST API first, and having a simple requests demo helps folks getting started.
0 kommentar(er)
