Page History

...

• Start the Mininet machine with of-config installed under Virtual-Box

• [Optional] Set a controller with the set controller command. For Example, you will have a different IP for your ONOS instance.

  Code Block
  mininet-vm:~$ sudo ovs-vsctl set-controller ofc-bridge tcp:10.128.12.1:6653

• Start the ofc-server in the Mininet machine

  Code Block
  mininet-vm:~$ sudo ofc-server -v 3 -f

• start ONOS

• activate the netconf app :

  Code Block
  onos> app activate org.onosproject.netconf

• give ONOS the information to connect to the device and which driver to use for it in the $ONOS_ROOT/tools/test/configs/netconf-cfg.json file.

• upload the configuration you just modified to the instance of ONOS you are running, in our case localhost:

  Code Block
  <your_machine>~$ curl -X POST -H "content-type:application/json" http://localhost:8181/onos/v1/network/configuration -d @$ONOS_ROOT/tools/test/configs/netconf-cfg.json --user onos:rocks

  or 

  Code Block
  <your_machine>~$ onos-netcfg localhost $ONOS_ROOT/tools/test/configs/netconf-cfg.json

• open the onos logs 

  for localhost logs

  Code Block
  <your_machine>~$ tl

  or for remote logs

  Code Block
  <your_machine>~$ ol

• verify that the logs don't contain NETCONF related exceptions and this warning is not in the logsdeos not appear:

  Code Block
  | WARN | event-dispatch-0 | NetconfDeviceProvider | 186 - org.onosproject.onos-netconf-provider-device - 1.4.0.SNAPSHOT | Can't connect to NETCONF device on <ip>:<port>

  In case the log is preset it means that the device was not able to reply on the given IP and Port. Verify Ip and Port in the Json file you posted and retry.

• Call the command or run the app you have written. For example:

  Code Block
  onos> device-controllers netconf:mininet@10.1.9.24:1830

...