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

sam_andares's profile - activity

2015-04-28 11:53:18 -0700 received badge  Famous Question (source)
2015-03-05 04:30:43 -0700 received badge  Famous Question (source)
2014-11-06 15:37:26 -0700 received badge  Taxonomist
2014-10-24 09:55:57 -0700 received badge  Notable Question (source)
2014-10-23 11:28:19 -0700 received badge  Notable Question (source)
2014-10-17 11:47:32 -0700 received badge  Popular Question (source)
2014-10-03 07:29:17 -0700 asked a question was something screwed up in the compile using MAVEN

Hi all,

I have had a project open for few weeks now and i've been changing stuff here and there... but yesterday i tried to compile (using the mvn command) and the controller is now not behaving properly at all. Flows cannot be added from the controller GUI to each OVS node. Can someone tell me if something changed and if so, what should i do not to be affected by that anymore or to protect myself against bad merges in the project. I manage to make it work right now by using and old executable and just replacing the jar files that i modified. By doing so.. i can move forward, but i feel this shows a huge vulnerability in terms of stability of the project.

Please comment.

2014-09-30 05:26:20 -0700 received badge  Famous Question (source)
2014-09-25 00:23:32 -0700 received badge  Popular Question (source)
2014-09-16 06:30:58 -0700 asked a question actions=normal supported by GUI??

Hi all,

I am trying to go out of the OVS bridge to reach the default forwarding table (basically going out of a non OVS bridged port). I think using the actions=NORMAL will allow me to do that.... but is it possible to do that while using the Opendaylight GUI to add a flow... I cannot find the normal action in there... what is the equivalent in the drop down menu?

thanks,

samantha

2014-07-25 17:06:36 -0700 received badge  Popular Question (source)
2014-07-25 17:06:36 -0700 received badge  Notable Question (source)
2014-07-25 17:06:36 -0700 received badge  Famous Question (source)
2014-07-17 11:17:14 -0700 received badge  Famous Question (source)
2014-07-17 11:16:32 -0700 asked a question opendaylight bug when connecting through layer2 switch?

Hi all,

I am having 5 different nodes with OVS installed that are linked to an ODL controller through a L2 switch. My objective is eventually be able to design a network on-the-fly by putting these nodes in different network.... does anyone know how to do this?

I am not far right now... and since i connected everything thorugh a L2 switch.. i would expect every node to see everyone and that it should show as is in the GUI but it is not like this at all... it's like if only one LLDP per node can made it through... so that every time i restart the controller... the network seem different with one node link to another one but not all to all... Can anyone point out if this is an ODL bug or if something should be done in the configuration for that?

thanks,

sam

2014-06-16 14:31:44 -0700 received badge  Notable Question (source)
2014-06-13 13:40:41 -0700 received badge  Notable Question (source)
2014-06-13 10:03:19 -0700 received badge  Popular Question (source)
2014-06-12 08:23:36 -0700 received badge  Popular Question (source)
2014-06-11 12:01:16 -0700 asked a question how opendaylight determines 2 nodes are connected to each other?

So, basically, i have such a configuration:

-------- --------- ---------------- | A | -eth0--> eth0 -| B | -eth4 ----- LAN ------eth4 | Controller | -------- --------- -----------------

node A and B are 2 ovs-switch.... I can get both A and B to connect to the controller, but the controller, in my case OpenDaylight, does not draw a line between A and B in the GUI... meaning it doens't know they are connected together, right?.... how can we have both connected? If i had a br0:1 interface on A with the LAN subnet that is between B and the controller, it shows that br0:1 address as a host connected to B for that address.

Anyone knows why it doesn't see a link between A and B or why it sees br0:1 as a host? Does anyone know how the controller determines if 2 nodes are connected to each other (in my case I would expect it to see that eth0 in br0 of A is connected to eth0 in br0 of B)... maybe by knowing that i could fix that up ...

thanks,

sam

2014-06-11 12:00:20 -0700 asked a question how opendaylight determines 2 nodes are connected

I understand that might be a question more related to the controller, but at this point, i am not sure.

So, basically, i have such a configuration:

-------- --------- ---------------- | A | -eth0--> eth0 -| B | -eth4 ----- LAN ------eth4 | Controller | -------- --------- -----------------

node A and B are 2 ovs-switch.... I can get both A and B to connect to the controller, but the controller, in my case OpenDaylight, does not draw a line between A and B in the GUI... meaning it doens't know they are connected together, right?.... how can we have both connected? If i had a br0:1 interface on A with the LAN subnet that is between B and the controller, it shows that br0:1 address as a host connected to B for that address.

Anyone knows why it doesn't see a link between A and B or why it sees br0:1 as a host? Does anyone know how the controller determines if 2 nodes are connected to each other (in my case I would expect it to see that eth0 in br0 of A is connected to eth0 in br0 of B)... maybe by knowing that i could fix that up ...

thanks,

sorry to ask anonymously, but i was not able to register... i have to give it a try again... but i didn't want to wait before posting my question.

sam