Ask is moving to Stack Overflow and Serverfault.com! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode

balakrishnan's profile - activity

2016-07-10 23:25:04 -0700 answered a question when I use feature:install <feature1> commands, it gives me an error.

Hi, No need to install all the features. if you install "odl-ovsdb-openstack" feature this will automatically install dependent feature. except Dlux and apidocs. There are many projects in ODL supports ODL and openstack integration. VTN project: https://wiki.opendaylight.org/view/VT...Guide:OpenStackPackStack_Support

Netvirt project: https://wiki.opendaylight.org/view/Op...andOpenDaylight#ConfiguringOpenvSwitchtobemanagedby_OpenDaylight

2016-03-01 22:36:18 -0700 answered a question question about 405 error code after created a controller

HI, The roll of "type" is to specify which controller your going to connect with Vtncoordinator. Vtncoodinator can handle multiple type of controller.current VtnCoordinator only includes odcdriver component to handle ODL controller. pfcdriver component is not included in VtnCoordinator source. it will not support type "pfc". could you elaborate the scenario your trying so that we can provide better solution.

2015-08-27 03:13:19 -0700 answered a question VTN - mininet not creating switches

please check the controller IP's are changed in the multitree.py script before creating topology. we have tested the multicontroller tutorial for VTN it was working fine in our environment. could you please tell me which karaf distribution your using. after creating mininet topology please execute below command in both controller see your able to get topology information curl -v --user "admin":"admin" -H "Accept: application/json" -H "Content-type: application/json" -X GET http://10.106.138.249:8282/restconf/operational/vtn-topology:vtn-topology { "vtn-topology": { "vtn-link": [ { "destination": "openflow:1:1", "link-id": "openflow:2:3", "source": "openflow:2:3" }, { "destination": "openflow:1:2", "link-id": "openflow:3:3", "source": "openflow:3:3" }, { "destination": "openflow:3:3", "link-id": "openflow:1:2", "source": "openflow:1:2" }, { "destination": "openflow:2:3", "link-id": "openflow:1:1", "source": "openflow:1:1" } ] } } "sudo ovs-vsctl show" will list the switches connected to the controller as below you are getting only mininet version could be mininet issue. mininet@mininet-only:~$ sudo ovs-vsctl show [sudo] password for mininet: dedcbf5a-b730-4937-b453-6a36246917ae Bridge "s2" Controller "tcp:10.106.138.249:6633" is connected: true Controller "ptcp:6635" failmode: secure Port "s2-eth2" Interface "s2-eth2" Port "s2-eth3" Interface "s2-eth3" Port "s2" Interface "s2" type: internal Port "s2-eth1" Interface "s2-eth1" ...

2015-08-26 23:11:10 -0700 commented answer VTN - L2 network multi-controller not working

did you changed the both controller IP in the multitree.py script. initially VBR,VBRIF status will be unknown when you map the correct port to the VBRIF using port map the status became UP.

2015-08-26 06:08:20 -0700 received badge  Editor (source)
2015-08-26 06:04:51 -0700 answered a question VTN - L2 network multi-controller not working

we have tested the multicontroller tutorial for VTN it was working fine in our environment. could you please tell me which karaf distribution your using. after creating mininet topology please execute below command in both controller see your able to get topology information curl -v --user "admin":"admin" -H "Accept: application/json" -H "Content-type: application/json" -X GET http://10.106.138.249:8282/restconf/operational/vtn-topology:vtn-topology { "vtn-topology": { "vtn-link": [ { "destination": "openflow:1:1", "link-id": "openflow:2:3", "source": "openflow:2:3" }, { "destination": "openflow:1:2", "link-id": "openflow:3:3", "source": "openflow:3:3" }, { "destination": "openflow:3:3", "link-id": "openflow:1:2", "source": "openflow:1:2" }, { "destination": "openflow:2:3", "link-id": "openflow:1:1", "source": "openflow:1:1" } ] } } "sudo ovs-vsctl show" will list the switches connected to the controller as below you are getting only mininet version could be mininet issue. mininet@mininet-only:~$ sudo ovs-vsctl show [sudo] password for mininet: dedcbf5a-b730-4937-b453-6a36246917ae Bridge "s2" Controller "tcp:10.106.138.249:6633" is connected: true Controller "ptcp:6635" failmode: secure Port "s2-eth2" Interface "s2-eth2" Port "s2-eth3" Interface "s2-eth3" Port "s2" Interface "s2" type: internal Port "s2-eth1" Interface "s2-eth1" ...

2015-06-03 06:04:28 -0700 answered a question How can virtual topology isolated in one controller

Hi,

Network Isolation is achieved by creating vbridges in a VTN. vBridge is a L2 broadcast domain. VLAN is used for network isolation across multiple vBridges in a VTN. Path policy function in VTN decides the network path taken by the packets based on the path policy applied to the VTN.

Thanks, Bala

2015-06-03 05:58:11 -0700 answered a question VTN how to ensure virtual network topology isolation?

Hi,

This topic has been discussed in detail in the below mail thread. https://lists.opendaylight.org/pipermail/vtn-dev/2015-April/001014.html

Request you to go through the thread and let us know if you need additional clarifications.

Thanks, Bala