Mininet and OpenFlow1.3 bandwidth on link

asked 2016-07-26 04:54:42 -0700

Mr_Happy gravatar image

Hello,

i have in mininet a topology of a triangle with three switches the conection between S1 and S2 has a high BW and between S1 and S3 has a low BW, between S2 and S3 is also high BW. Each Switch has its connected host to perform measurements.

The problem i have is that after instantiating the network S1 has to all other switches a high BW, instead of the specified BW limitation of the link.

Questions: Is this a problem of ODL not implementing the feature of limiting the BW on the link? Or is this a problem of Mininet? (i did use the official Mininet and the ODL mininet with OF1.3 and both gave me the same result)

Information:

Measurement between:

  • S1 and S2 = 10 Mbits/sec
  • S1 and S3 = 10 Mbits/sec // is wrong should be 1 Mbits/sec
  • S2 and S3 = 10 Mbits/sec
  • S2 and S1 =10 Mbits/sec // is wrong should be 1 Mbits/sec
  • S3 and S2 = 10 Mbits/sec
  • S3 and S1 = 10 Mbits/sec // is wrong should be 1 Mbits/sec

Here is a Code snippet: Mininet

    Control0 = 'ip adress'
    OVSSwitch13 = partial(OVSSwitch, protocols='OpenFlow13')
    net = Mininet(topo=None, switch=OVSSwitch13, build=False, link=TCLink)
    #Setup Control
    c0 = net.addController('c0', controller=RemoteController, ip=Control0, port=6633)

    lowBW = dict(
            bw=1,
            delay='0ms',
            loss=0,
            max_queue_size=1000,
            use_htp=False)

    highBW = dict(
            bw=10,
            delay='0ms',
            loss=0,
            max_queue_size=1000,
            use_htp=False)

    net.addLink(s1,s2,**highBW)
    net.addLink(s2,s3,**highBW)
    net.addLink(s1,s3,**lowBW)

Mininet tells me the following at the instantiating process, s1 (10.00Mbit 0ms delay 0% loss) (1.00Mbit 0ms delay 0% loss) s2 (10.00Mbit 0ms delay 0% loss) (10.00Mbit 0ms delay 0% loss) s3 (10.00Mbit 0ms delay 0% loss) (1.00Mbit 0ms delay 0% loss)

Software Version: Mininet 2.2.1 ODL 3.0.3

additionally i have the following error messages from ODL,

Exception in thread "Thread-233" java.util.concurrent.RejectedExecutionException: Task org.opendaylight.openflowplugin.openflow.md.core.HandshakeStepWrapper@2e14c62e rejected from org.opendaylight.openflowplugin.openflow.md.core.ThreadPoolLoggingExecutor@2a2b4734[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0] at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1369) at org.opendaylight.openflowplugin.openflow.md.core.ConnectionConductorImpl.onConnectionReady(ConnectionConductorImpl.java:451) at org.opendaylight.openflowjava.protocol.impl.core.connection.ConnectionAdapterImpl$1.run(ConnectionAdapterImpl.java:185) at java.lang.Thread.run(Thread.java:745)

Exception in thread "Thread-237" java.util.concurrent.RejectedExecutionException: Task org.opendaylight.openflowplugin.openflow.md.core.HandshakeStepWrapper@201b82bf rejected from org.opendaylight.openflowplugin.openflow.md.core.ThreadPoolLoggingExecutor@24240264[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0] at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1369) at org.opendaylight.openflowplugin.openflow.md ... (more)

edit retag flag offensive close merge delete