Hi Ali,
I figured how to connect mininet (in VM), FV (in remote pc) and remote
controllers (in remote pc) each other. However I am having some instability
problems. To briefly discuss these errors, my simple scenario;
(i) Two slices by FV are created;
fvctl -f fvpasswd_file add-slice myslice1 tcp:192.168.56.1:8001 mfa
fvctl -f fvpasswd_file add-slice myslice2 tcp:192.168.56.1:8002 mfa
(ii) Then two flowspaces are created;
fvctl -f fvpasswd_file add-flowspace myflowspace1 all 1 any myslice1=7
fvctl -f fvpasswd_file add-flowspace myflowspace2 00:00:00:00:00:01 3
any myslice2=7
fvctl -f fvpasswd_file add-flowspace myflowspace2 00:00:00:00:00:02 3
any myslice2=7
fvctl -f fvpasswd_file add-flowspace myflowspace2 00:00:00:00:00:03 3
any myslice2=7
(Note: I could not find a way to assign multiple dpids to one flowspace
at a time, that is why three flowspaces are entered here)
There are 4 switches in the topology with dpid ::01, ::02, ::03 & ::04.
What I am trying to do here is to slice the network such that all switches
are connected to controller:8001 and 3 of them are connected to the
controller:8002. May be this is not the right way of doing that, not sure.
The problem is, all switches are getting connected to controller:8001
successfully everytime but for myslice2, the instability problem is;
sometimes only the last switch (::03) added is getting connected or
sometimes others are getting connected and then immediately disconnected or
not connecting at all. And sometimes all of them are successfully
connected. I could figure out what causes this problem.
Also, even though the flowspaces of myslice1&2 are successfully created and
all switches are getting connected successfully, FV does not send the
packet_ins to both slice switches but only to one e.g. controller:8001.
Overall, what i am trying to do is to slice the network into virtual
subnets, and here i explained the problems I had during doing that. What I
am doing may not be the best way, I would appreciate any help or comment.
Thanks for the time.
Mehmet Fatih Aktas
On Tue, Feb 26, 2013 at 3:08 PM, Ali Al-Shabibi <ali.al-shab...@stanford.edu
> wrote:
> Hi Mehmet,
>
> FlowVisor can reside anywhere really (within a reasonable latency), so you
> could have it running in the mininet VM or on another machine. Just point
> your mininet network to the FlowVisor.
>
> This can be done by giving the --controller remote option to mininet. That
> said, I'd be interested to know what problems you had installing FlowVisor.
>
> >
> > Is there any simple tutorial or any resource that can help me to get on
> board quickly ?
>
> Unfortunately not yet, but I will be putting the tutorials up online
> officially soon, although they may not be very different to the ones you
> have found yet.
>
> Hope this helps!
>
> > Thanks.
> >
> > Mehmet Fatih Aktas
> > _______________________________________________
> > 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
