I found a bug while implementing the Link aggregation using ryu controller.The
source code and the topology are already explained in the ryu book OpenFlow V1.3
Assume that i have 1 switch and 4 hosts (h1, h2, h3, h4). I make link
aggregation on h1 interfaces >> h1-eth0 and h1-eth1
when i ping from (h2, h3, h4) to h1
the hosts are distributed in the flow table like following:
h2 use h1-eth0 to communicate with h1 (two way communication)
h3 use h1-eth1 to communicate with h1 (two way communication)h4 use h1-eth0 to
communicate with h1 (two way communication)
>>The Flow Table will have 6 entries (3 hosts two way communication) + 1 table
>>miss entry + 2 entries for the h1 interfaces.
when i close the port h1-eth1, after the time out a new packet in is done and
the path of h3 will be now :
h3 use h1-eth0 instead of h1-eth1 to communicate with h1
but the problem is when interface h1-eth1 is on again , h3 will take 2 pathes
to communicate with h1 (h1-eth0, h1-eth1) ?!!
, can any one help me to solve this problem ? i want to make h3 return back to
its original path when the interface is on again and not to duplicate the path.
>>The Flow Table will have 7 entries + 1 table miss entry + 2 entries for the
>>h1 interfaces.
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Ryu-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ryu-devel
