Hi Nick,
Thanks for your advice.
>You can isolate them, but perhaps not the way you're doing it.
>Instead of setting Slice: production to have access to "any" DPID, you
>may need to explicitly give it access to only the switches you want.
I haven't tried this before but I guess it may not work. (Anyhow I will try it
later and thanks for the advice again.)
I've thought about why the machines in two slices can connect to each other in
my case and I think the reason is that though the two slices are managed by two
different controllers, the packets can transit smoothly through slices
(switches): when switch A recieves a packet from switch B, the controller
simply decides to forward it for not knowing it's from another dpid. I hope I
explain it clear... If I'm right, your method and mine will lead to the same
result.
Now I can isolate the network only by 'in_port' (switch port). To avoid the
above case, I manually configure the link between switches (one port of each
switch) to be managed by one of the controllers so that switch A's other ports
cannot recieve packets from switch B.
>Sadly this is no longer dynamic, but I'm not sure there's any amount
>of priority munging that you can do to get FlowVisor to exclude
>switches from other slices without explicitly managing the devices in
>every slice.
That's truly a trouble. Luckily the network topology doesn't change frequently
or it may be a disaster ^_^
Hope there'll be an easier way to manage the flowspace.
Best Regards,
Xu Yang
_______________________________________________
openflow-discuss mailing list
[email protected]
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
