subject:"\[Ryu\-devel\] All the links of the topology not getting discovered."

Re: [Ryu-devel] All the links of the topology not getting discovered.

2018-03-26 Thread Taha Khan

Thanks for sharing this link.

On Sun, Mar 25, 2018 at 9:49 PM, Iwase Yusuke 
wrote:

> Hi Taha,
>
> Hmmm... I haven't tried yet though, the following parameters seems to be
> configured. But sorry I don't know those parameters meanings further...
> https://github.com/osrg/ryu/blob/master/ryu/topology/switches.py#L509-L513
>
> Thanks,
> Iwase
>
> On 2018年03月26日 10:45, Taha Khan wrote:
>
>> Well, What I observed is - Number of Nodes: 13, Number of Edges:21.
>> Is there a way this could be increased in terms of number of edges and
>> nodes?
>>
>>
>> Thanks!
>> Taha
>>
>>
>> On Sun, Mar 25, 2018 at 7:33 PM, Iwase Yusuke > > wrote:
>>
>> Hi Taha,
>>
>> > But do you have any rough idea, how many links should a topology
>> have to not
>> > hit performance limit?
>>
>> Sorry, I don't have any idea...
>>
>> Thanks,
>> Iwase
>>
>>
>> On 2018年03月24日 11:07, Taha Khan wrote:
>>
>> Thanks for the reply.
>> But do you have any rough idea, how many links should a topology
>> have to
>> not hit performance limit?
>> This is my systems specs.
>> I need EventLinkAdd and EventLinkDelete to work properly as I am
>> planning to introduce multiple link failures from mininet.
>>
>> I started with 62 nodes, 107 links and trimmed my topology to 30
>> Nodes
>> and 43 Links(86 bi-directional) and found, I was able to discover
>> the
>> full topology but EventLinkDelete wasn't triggering when I tried
>> with mininet (link down command).
>> Now I have 30 Nodes, 32 Links and still EventLinkDelte is not
>> getting
>> triggered though I see the full topology information in my
>> structures
>> storing their information in RYU controller.
>>
>>
>>
>>
>>
>>
>>
>>
>> Thanks!
>> Taha
>>
>>
>> On Fri, Mar 23, 2018 at 3:45 AM, Iwase Yusuke <
>> iwase.yusu...@gmail.com
>>  >
>> >> wrote:
>>
>>  Hi Taha,
>>
>>  IIRC, the similar problems had reported before on this
>> mailing list.
>>  I think you hit the performance limit of "single" controller
>> in
>> order to use
>>  topology discovery feature against such many switches.
>>
>>  For handling such large topology, how about splitting your
>> topology
>> into some
>>  sub-topology and having multiple controllers?
>>
>>  Thanks,
>>  Iwase
>>
>>
>>
>>  On 2018年03月23日 16:07, Taha Khan wrote:
>>
>>  Hi
>>
>>  I am using RYU-4.23 and Mininet OVS.
>>  I have a 62 Node topology. When I run my RYU application
>> I
>> noticed that
>>  RYU is not able to discover all the datapaths and links
>> everytime I run
>>  my code. And also when I run (link down command ) in
>> mininet CLI,
>>  EventLinkDelete is not getting triggered everytime I did
>> it.
>> Few times I
>>  was actually able to discover the full topology and
>> EventLinkDelete was
>>  also getting triggered.
>>  Can you please suggest why is this so. I have attached
>> codes below.
>>
>>
>>  Thanks!
>>  Taha
>>
>>
>> --
>> 
>>  Check out the vibrant tech community on one of the
>> world's most
>>  engaging tech sites, Slashdot.org!
>> http://sdm.link/slashdot
>>
>>
>>
>>  ___
>>  Ryu-devel mailing list
>> Ryu-devel@lists.sourceforge.net > forge.net>
>> > >
>> https://lists.sourceforge.net/lists/listinfo/ryu-devel
>> 
>>  > >
>>
>>
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> ___
>> Ryu-devel mailing list
>> Ryu-devel@lists.sourceforge.net > forge.net>
>> https://lists.sourceforge.net/lists/listinfo/ryu-devel
>> 
>>
>>
>>
>>
>>

Re: [Ryu-devel] All the links of the topology not getting discovered.

2018-03-25 Thread Iwase Yusuke

Hi Taha,

Hmmm... I haven't tried yet though, the following parameters seems to be
configured. But sorry I don't know those parameters meanings further...
https://github.com/osrg/ryu/blob/master/ryu/topology/switches.py#L509-L513

Thanks,
Iwase

On 2018年03月26日 10:45, Taha Khan wrote:

Well, What I observed is - Number of Nodes: 13, Number of Edges:21.
Is there a way this could be increased in terms of number of edges and nodes?

Thanks!
Taha

On Sun, Mar 25, 2018 at 7:33 PM, Iwase Yusuke > wrote:

Hi Taha,

> But do you have any rough idea, how many links should a topology have to 
not
> hit performance limit?

Sorry, I don't have any idea...

Thanks,
Iwase

On 2018年03月24日 11:07, Taha Khan wrote:

Thanks for the reply.
But do you have any rough idea, how many links should a topology have to
not hit performance limit?
This is my systems specs.
I need EventLinkAdd and EventLinkDelete to work properly as I am
planning to introduce multiple link failures from mininet.

I started with 62 nodes, 107 links and trimmed my topology to 30 Nodes
and 43 Links(86 bi-directional) and found, I was able to discover the
full topology but EventLinkDelete wasn't triggering when I tried
with mininet (link down command).
Now I have 30 Nodes, 32 Links and still EventLinkDelte is not getting
triggered though I see the full topology information in my structures
storing their information in RYU controller.

Thanks!
Taha

On Fri, Mar 23, 2018 at 3:45 AM, Iwase Yusuke  >> wrote:

     Hi Taha,

     IIRC, the similar problems had reported before on this mailing 
list.
     I think you hit the performance limit of "single" controller in
order to use
     topology discovery feature against such many switches.

     For handling such large topology, how about splitting your topology
into some
     sub-topology and having multiple controllers?

     Thanks,
     Iwase

     On 2018年03月23日 16:07, Taha Khan wrote:

         Hi

         I am using RYU-4.23 and Mininet OVS.
         I have a 62 Node topology. When I run my RYU application I
noticed that
         RYU is not able to discover all the datapaths and links
everytime I run
         my code. And also when I run (link down command ) in mininet 
CLI,
         EventLinkDelete is not getting triggered everytime I did it.
Few times I
         was actually able to discover the full topology and
EventLinkDelete was
         also getting triggered.
         Can you please suggest why is this so. I have attached codes 
below.

         Thanks!
         Taha

--

         Check out the vibrant tech community on one of the world's most
         engaging tech sites, Slashdot.org! http://sdm.link/slashdot

         ___
         Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net 
>
https://lists.sourceforge.net/lists/listinfo/ryu-devel

         >

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

___
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/ryu-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

___
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!

Re: [Ryu-devel] All the links of the topology not getting discovered.

2018-03-25 Thread Taha Khan

Well, What I observed is - Number of Nodes: 13, Number of Edges:21.
Is there a way this could be increased in terms of number of edges and
nodes?


Thanks!
Taha


On Sun, Mar 25, 2018 at 7:33 PM, Iwase Yusuke 
wrote:

> Hi Taha,
>
> > But do you have any rough idea, how many links should a topology have to
> not
> > hit performance limit?
>
> Sorry, I don't have any idea...
>
> Thanks,
> Iwase
>
>
> On 2018年03月24日 11:07, Taha Khan wrote:
>
>> Thanks for the reply.
>> But do you have any rough idea, how many links should a topology have to
>> not hit performance limit?
>> This is my systems specs.
>> I need EventLinkAdd and EventLinkDelete to work properly as I am planning
>> to introduce multiple link failures from mininet.
>>
>> I started with 62 nodes, 107 links and trimmed my topology to 30 Nodes
>> and 43 Links(86 bi-directional) and found, I was able to discover the full
>> topology but EventLinkDelete wasn't triggering when I tried
>> with mininet (link down command).
>> Now I have 30 Nodes, 32 Links and still EventLinkDelte is not getting
>> triggered though I see the full topology information in my structures
>> storing their information in RYU controller.
>>
>>
>>
>>
>>
>>
>>
>>
>> Thanks!
>> Taha
>>
>>
>> On Fri, Mar 23, 2018 at 3:45 AM, Iwase Yusuke > > wrote:
>>
>> Hi Taha,
>>
>> IIRC, the similar problems had reported before on this mailing list.
>> I think you hit the performance limit of "single" controller in order
>> to use
>> topology discovery feature against such many switches.
>>
>> For handling such large topology, how about splitting your topology
>> into some
>> sub-topology and having multiple controllers?
>>
>> Thanks,
>> Iwase
>>
>>
>>
>> On 2018年03月23日 16:07, Taha Khan wrote:
>>
>> Hi
>>
>> I am using RYU-4.23 and Mininet OVS.
>> I have a 62 Node topology. When I run my RYU application I
>> noticed that
>> RYU is not able to discover all the datapaths and links everytime
>> I run
>> my code. And also when I run (link down command ) in mininet CLI,
>> EventLinkDelete is not getting triggered everytime I did it. Few
>> times I
>> was actually able to discover the full topology and
>> EventLinkDelete was
>> also getting triggered.
>> Can you please suggest why is this so. I have attached codes
>> below.
>>
>>
>> Thanks!
>> Taha
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> ___
>> Ryu-devel mailing list
>> Ryu-devel@lists.sourceforge.net > forge.net>
>> https://lists.sourceforge.net/lists/listinfo/ryu-devel
>> 
>>
>>
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> ___
>> Ryu-devel mailing list
>> Ryu-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/ryu-devel
>>
>>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel

Re: [Ryu-devel] All the links of the topology not getting discovered.

2018-03-25 Thread Iwase Yusuke

Hi Taha,

> But do you have any rough idea, how many links should a topology have to not
> hit performance limit?

Sorry, I don't have any idea...

Thanks,
Iwase

On 2018年03月24日 11:07, Taha Khan wrote:

Thanks for the reply.
But do you have any rough idea, how many links should a topology have to not hit 
performance limit?

This is my systems specs.
I need EventLinkAdd and EventLinkDelete to work properly as I am planning to 
introduce multiple link failures from mininet.

I started with 62 nodes, 107 links and trimmed my topology to 30 Nodes and 43 
Links(86 bi-directional) and found, I was able to discover the full topology but 
EventLinkDelete wasn't triggering when I tried with mininet (link down command).
Now I have 30 Nodes, 32 Links and still EventLinkDelte is not getting triggered 
though I see the full topology information in my structures storing their 
information in RYU controller.

Thanks!
Taha

On Fri, Mar 23, 2018 at 3:45 AM, Iwase Yusuke > wrote:

Hi Taha,

IIRC, the similar problems had reported before on this mailing list.
I think you hit the performance limit of "single" controller in order to use
topology discovery feature against such many switches.

For handling such large topology, how about splitting your topology into 
some
sub-topology and having multiple controllers?

Thanks,
Iwase

On 2018年03月23日 16:07, Taha Khan wrote:

Hi

I am using RYU-4.23 and Mininet OVS.
I have a 62 Node topology. When I run my RYU application I noticed that
RYU is not able to discover all the datapaths and links everytime I run
my code. And also when I run (link down command ) in mininet CLI,
EventLinkDelete is not getting triggered everytime I did it. Few times I
was actually able to discover the full topology and EventLinkDelete was
also getting triggered.
Can you please suggest why is this so. I have attached codes below.

Thanks!
Taha

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

___
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/ryu-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

___
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel

Re: [Ryu-devel] All the links of the topology not getting discovered.

2018-03-23 Thread Taha Khan

Thanks for the reply.
But do you have any rough idea, how many links should a topology have to
not hit performance limit?
This is my systems specs.
I need EventLinkAdd and  EventLinkDelete to work properly as I am planning
to introduce multiple link failures from mininet.

I started with 62 nodes, 107 links and trimmed my topology to 30 Nodes and
43 Links(86 bi-directional) and found, I was able to discover the full
topology but EventLinkDelete wasn't triggering when I tried
with mininet (link down command).
Now I have 30 Nodes, 32 Links and still EventLinkDelte is not getting
triggered though I see the full topology information in my structures
storing their information in RYU controller.

Thanks!
Taha

On Fri, Mar 23, 2018 at 3:45 AM, Iwase Yusuke 
wrote:

> Hi Taha,
>
> IIRC, the similar problems had reported before on this mailing list.
> I think you hit the performance limit of "single" controller in order to
> use
> topology discovery feature against such many switches.
>
> For handling such large topology, how about splitting your topology into
> some
> sub-topology and having multiple controllers?
>
> Thanks,
> Iwase
>
>
>
> On 2018年03月23日 16:07, Taha Khan wrote:
>
>> Hi
>>
>> I am using RYU-4.23 and Mininet OVS.
>> I have a 62 Node topology. When I run my RYU application I noticed that
>> RYU is not able to discover all the datapaths and links everytime I run my
>> code. And also when I run (link down command ) in mininet CLI,
>> EventLinkDelete is not getting triggered everytime I did it. Few times I
>> was actually able to discover the full topology and EventLinkDelete was
>> also getting triggered.
>> Can you please suggest why is this so. I have attached codes below.
>>
>>
>> Thanks!
>> Taha
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> ___
>> Ryu-devel mailing list
>> Ryu-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/ryu-devel
>>
>>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel

Re: [Ryu-devel] All the links of the topology not getting discovered.

2018-03-23 Thread Iwase Yusuke


Hi Taha,

IIRC, the similar problems had reported before on this mailing list.
I think you hit the performance limit of "single" controller in order to use
topology discovery feature against such many switches.

For handling such large topology, how about splitting your topology into some
sub-topology and having multiple controllers?

Thanks,
Iwase


On 2018年03月23日 16:07, Taha Khan wrote:

Hi

I am using RYU-4.23 and Mininet OVS.
I have a 62 Node topology. When I run my RYU application I noticed that RYU is 
not able to discover all the datapaths and links everytime I run my code. And 
also when I run (link down command ) in mininet CLI, EventLinkDelete is not 
getting triggered everytime I did it. Few times I was actually able to discover 
the full topology and EventLinkDelete was also getting triggered.

Can you please suggest why is this so. I have attached codes below.


Thanks!
Taha


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot



___
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel

[Ryu-devel] All the links of the topology not getting discovered.

2018-03-23 Thread Taha Khan

Hi

I am using RYU-4.23 and Mininet OVS.
I have a 62 Node topology. When I run my RYU application I noticed that RYU
is not able to discover all the datapaths and links everytime I run my
code. And also when I run (link down command ) in mininet CLI,
EventLinkDelete is not getting triggered everytime I did it. Few times I
was actually able to discover the full topology and EventLinkDelete was
also getting triggered.
Can you please suggest why is this so. I have attached codes below.


Thanks!
Taha
from mininet.net import Mininet
from mininet.node import Controller, RemoteController
from mininet.cli import CLI
from mininet.log import setLogLevel, info
from time import sleep

Nodes=[1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16,
   17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29,
   30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44,
   45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62]

Links=[[1, 2], [1, 3], [3, 4], [3, 5], [6, 7], [6, 8], [4, 9], [10, 9], [10, 11],
   [5, 12], [5, 7], [5, 11], [5, 9], [5, 13], [9, 14], [9, 15],
   [9, 16], [9, 17], [15, 18], [19, 20], [19, 21], [19, 22],
   [23, 24], [23, 25], [25, 26], [25, 20], [25, 27], [28, 29],
   [28, 30], [29, 31], [29, 32], [29, 33], [29, 30], [29, 34],
   [35, 36], [35, 37], [37, 38], [37, 30], [38, 39], [39, 25],
   [25, 30], [30, 40], [30, 26], [30, 33], [30, 41], [30, 42],
   [30, 43], [30, 44], [45, 46], [45, 47], [45, 41], [45, 44],
   [27, 40], [27, 20], [27, 48], [27, 21], [48, 49], [48, 50],
   [32, 26], [41, 47], [16, 33], [16, 51], [16, 52], [16, 21],
   [49, 40], [22, 20], [53, 24], [53, 54], [24, 26], [43, 40],
   [31, 54], [42, 40], [40, 46], [40, 33], [40, 50], [55, 56],
   [55, 21], [34, 33], [51, 57], [51, 21], [56, 33], [21, 57],
   [21, 26], [21, 33], [21, 20], [54, 26], [36, 46], [7, 33],
   [7, 58], [12, 52], [12, 8], [13, 17], [46, 33], [46, 59],
   [46, 58], [59, 58], [58, 33], [33, 60], [33, 8], [8, 61],
   [8, 2], [52, 14], [52, 18], [52, 62], [62, 14], [14, 18], [60, 61]]



def emptyNet():
"Create an empty network and add nodes to it."

net = Mininet(controller=RemoteController)

info('*** Adding controller\n')
net.addController('c0', controller=RemoteController, ip='127.0.0.1', port=6633)


info('*** Adding hosts\n')
h = []
for i in Nodes:
host = 'h' + str(i)
h.append(net.addHost(host))

info('*** Adding switch\n')
s = []
for j in Nodes:
switch = 's' + str(j)
s.append(net.addSwitch(switch))
"""print(s)"""

info('*** Creating links\n')
## One host at each switch
for index in range(0,len(Nodes)):
net.addLink(s[index], h[index])

i=0;

for link_pair in Links:
i=i+1;
net.addLink('s'+str(link_pair[0]), 's'+str(link_pair[1]))
print('s'+str(link_pair[0]), 's'+str(link_pair[1]), i)


info('*** Starting network\n')
net.start()

for i in s:
	i.cmd('ovs-vsctl set bridge', i ,'protocols=OpenFlow13')

info('*** Running CLI\n')
CLI(net)
#sleep(2)
#net.pingAll()

info('*** Stopping network')
net.stop()


if __name__ == '__main__':
setLogLevel('info')
emptyNet()



# Copyright (C) 2011 Nippon Telegraph and Telephone Corporation.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
# implied.
# See the License for the specific language governing permissions and
# limitations under the License.

from ryu.base import app_manager
from ryu.controller import ofp_event
from ryu.controller.handler import set_ev_cls
from ryu.ofproto import ofproto_v1_3
from ryu.lib.packet import packet
from ryu.lib.packet import ethernet
from ryu.lib.packet import ether_types
import logging
import struct
from ryu.controller.handler import MAIN_DISPATCHER, DEAD_DISPATCHER, CONFIG_DISPATCHER
from ryu.lib.packet import ipv4
from ryu.lib import mac
from ryu.lib.packet import arp
from ryu.topology import event, switches
from ryu.topology.api import get_switch, get_link
from ryu.controller import dpset
from ryu.lib import dpid
from ryu.controller import handler
from threading import Timer


class SimpleSwitch14(app_manager.RyuApp):
OFP_VERSIONS = [ofproto_v1_3.OFP_VERSION]
_CONTEXTS = {'dpset': dpset.DPSet}

def __init__(self, *args, **kwargs):
super(SimpleSwitch14, self).__init__(*args, **kwargs)
self.topology_api_app = self
self.mac_to_port = {}
self.switch_port_table = {}
self.link_to_port = {}
self.interior_ports = {}

Re: [Ryu-devel] All the links of the topology not getting discovered.

Re: [Ryu-devel] All the links of the topology not getting discovered.

Re: [Ryu-devel] All the links of the topology not getting discovered.

Re: [Ryu-devel] All the links of the topology not getting discovered.

Re: [Ryu-devel] All the links of the topology not getting discovered.

Re: [Ryu-devel] All the links of the topology not getting discovered.

[Ryu-devel] All the links of the topology not getting discovered.

7 matches

Site Navigation

Mail list logo

Footer information