[CONTROLLER-25] java.lang.ArrayIndexOutOfBoundsException when trying to ping between two nodes in Mininet Created: 22/Jul/13  Updated: 04/May/15  Resolved: 04/May/15

Status: Resolved
Project: controller
Component/s: adsal
Affects Version/s: 0.4.0
Fix Version/s: None

Type: Bug
Reporter: Stace Hipperson Assignee: Venkata Siva Vijayendra Bhamidipati
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Windows
Platform: PC

Attachments: Text File opendaylight-22-07-13.log    
External issue ID: 31

 Description   

I have the OpenDaylight controller running on my PC (native) and am using a VM for mininet. ODP is up and running, I can connect to the UI no problem. After setting a gateway address of 10.0.0.254/8 and trying to ping between two hosts in Mininet I get errors for each ping (log attached)

the switches have registered to the controller ad shown by this output: BST [ControllerI/O Thread] INFO o.o.c.p.o.core.internal.Controller - Switch:1.1.1.102:2063 is connected to the Controller

the following trace statements were applied:
setloglevel org.opendaylight.controller.arphandler TRACE
setloglevel org.opendaylight.controller.sal.packet.Packet TRACE
setloglevel org.opendaylight.controller.sal.packet.BitBufferHelper TRACE

 Comments   
Comment by Stace Hipperson [ 22/Jul/13 ]

Attachment opendaylight-22-07-13.log has been added with description: opendaylight controller log

Comment by Venkata Siva Vijayendra Bhamidipati [ 22/Jan/14 ]

Hi Stace,

I tried to reproduce this bug on my setup, but wasn't able to. I started up the ODL controller on one VM (192.168.52.99). Then installed mininet on a different VM (192.168.52.56), then created a switch topology this way on mininet:

root@controllernode:~# sudo mn --controller=remote,ip=192.168.52.99 --topo tree,3

      • Creating network
      • Adding controller
      • Adding hosts:
        h1 h2 h3 h4 h5 h6 h7 h8
      • Adding switches:
        s1 s2 s3 s4 s5 s6 s7
      • Adding links:
        (h1, s3) (h2, s3) (h3, s4) (h4, s4) (h5, s6) (h6, s6) (h7, s7) (h8, s7) (s1, s2) (s1, s5) (s2, s3) (s2, s4) (s5, s6) (s5, s7)
      • Configuring hosts
        h1 h2 h3 h4 h5 h6 h7 h8
      • Starting controller
      • Starting 7 switches
        s1 s2 s3 s4 s5 s6 s7
      • Starting CLI:
        mininet>

Then went to the ODL controller GUI, the topology showed up fine on ODL. I clicked on "Add Gateway IP address" under "Subnet Gateway Configuration", giving subnet1 and 10.0.0.254/8 as the CIDR. I then set the log level in the OSGI console the same way you did, and did a few pings (h1 ping h7, h2 ping h4 etc), but the trace messages on the OSGI console didn't hit any exceptions.

It looks like this bug has been fixed upstream. I will close this as not reproducible. Please reopen this bug if you still see the bug - please also provide the exact mininet commands you used to set up the topology - this may be dependent on that.

Comment by Carol Sanders [ 04/May/15 ]

This bug is part of the project to Move all ADSAL associated component bugs to ADSAL

Generated at Wed Feb 07 19:51:59 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.