[L2SWITCH-82] arphandler unable to flood arp packet Created: 07/Sep/16  Updated: 19/Oct/17  Resolved: 05/Oct/16

Status: Resolved
Project: l2switch
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Xu Ye Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 6655
Priority: Normal

 Description   

To reproduce:
1)bring mininet with three switch and 3 hosts,like:
sudo mn --topo=linear,3 --mac --switch ovs --controller=remote,192.168.0.1

2) h1 ping h2 quickly enough before loopremover module to process the topology .
Now The StpStatus of nodeconnectors in network hasn't be fixed.

3) h1 ping h2 will always fail,because the controller doesn't packetout the arp-request packet.
The reason is: At this time, in function dispatchPacket(), inventoryReader.getControllerSwitchConnectors().get(nodeId) is not null;
inventoryReader.getSwitchNodeConnectors().get(nodeId) also is not null,but has no
member in the list.

In the other hand, if the network topology changed which will change the StpStatus of the nodeconnectors ,arphandler module inventoryReader has no way to process this situation.



 Comments   
Comment by Geng Xingyuan [ 09/Sep/16 ]

https://git.opendaylight.org/gerrit/#/c/45369/1

Comment by Xu Ye [ 27/Sep/16 ]

Another situation to reproduce this bug:
1)bring mininet with one switch and 2 hosts,like:
sudo mn --topo=single,2 --mac --switch ovs --controller=remote,192.168.0.1

2) h1 ping h2 ,ok;

3) quit mininet,then bring mininet with one switch and 4 hosts,like:
sudo mn --topo=single,4 --mac --switch ovs --controller=remote,192.168.0.1

4) h1 ping h4 or h1 ping h3 will always fail;

Because the nodeconnector info of the node(openflow:1) in buffer inventoryReader.SwitchNodeConnectors() only contains connectors connected to h1 and h2. So when h1 ping h4,the arp-request can not flood to h4.
There need some way to refresh the nodeConnector info when network topo changed.

Generated at Wed Feb 07 20:05:52 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.