Hi Viral, do you think the logic would depend on the application you have in 
mind? For example, on this class project I am doing for distributed ethernet 
monitoring, http://blog.pythonicneteng.com/, all I need is to specify a pair of 
incoming / outgoing port for a specific duration of time. I don't even need a 
'controller', just a few dpctrl commands. 

One thing that I think might help is to use a linear topology from Mininet's 
documentation, http://mininet.org/walkthrough/, such as:

mininet@mininet-vm:~$ sudo mn --topo linear,3 --mac --switch ovsk --controller 
remote
<skip>
mininet> net
c0
s1 lo:  s1-eth1:h1-eth0 s1-eth2:s2-eth2
s2 lo:  s2-eth1:h2-eth0 s2-eth2:s1-eth2 s2-eth3:s3-eth2
s3 lo:  s3-eth1:h3-eth0 s3-eth2:s2-eth3
h1 h1-eth0:s1-eth1
h2 h2-eth0:s2-eth1
h3 h3-eth0:s3-eth1
mininet> 

Each switch has one host connection and one inter-switch connection. Then you 
can start playing with your multi-switch application. All the switch can 
register with the same controller and the controller would identify each switch 
via DPID. It is not different than having each switch has a topological view 
contracted via, say, spanning-tree or any routing protocol, except now it is in 
a centralize controller. :)

Hope it helps, 

Eric

On Apr 14, 2013, at 4:46 AM, viral parmar <viral_par...@outlook.com> wrote:

> Hello,
> I want to program the basic functionality of the controller. I found out many 
> articles on this , but none of them are unable to clear my concept. The 
> Article i saw up till now is having only 1 switch connected to 1 controller 
> instead i want to analyze the controller behavior with 2 or more switches 
> connected to 1 controller.
> 
> What happens when a packet arrive a switch 1 and having the destination 
> address of a node that is connected to switch 2 ? So basically i am wanted to 
> know the basic functionality (basic logic), so that on the basis of that i 
> can prepared my own program.
> 
> Thank you,
> 
> Regards
> Viral Parmar
> _______________________________________________
> openflow-discuss mailing list
> openflow-discuss@lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss

_______________________________________________
openflow-discuss mailing list
openflow-discuss@lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss

Reply via email to