Ask is moving to Stack Overflow and Serverfault.com! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode

0

Ping fails in Mininet topology when using remote controller

asked 2017-02-10 00:58:47 -0800

marievi gravatar image

I am using Mininet to start a topology with an OpenDaylight controller (Boron-SR2 version), like this :

sudo mn --custom topo1.py --topo mytopo --controller=remote,ip=<CONTROLLER_IP>

The messages shown after this command are :

*** Creating network
*** Adding controller
*** Adding hosts:
h1 h2 h3
*** Adding switches:
s1 s2 s3
*** Adding links:
(h1, s1) (h2, s2) (h3, s3) (s2, s1) (s3, s2)
*** Configuring hosts
h1 h2 h3
*** Starting controller
c0
*** Starting 3 switches
s1 s2 s3 ...
*** Starting CLI:
mininet>

File topo1.py is the following :

from mininet.topo import Topo

class MyTopo( Topo ):
    "Simple topology example."

    def __init__( self ):
        "Create custom topo."

        # Initialize topology
        Topo.__init__( self )

        # Add hosts and switches
        host1 = self.addHost( 'h1' )
        host2 = self.addHost( 'h2' )
        switch1 = self.addSwitch( 's1' )
        switch2 = self.addSwitch( 's2' )
        switch3 = self.addSwitch( 's3' )

        # Add links
        self.addLink(switch1, switch2)
        self.addLink(switch1, switch3)
        self.addLink(switch2, switch3)
        self.addLink(host1, switch1)
        self.addLink(host2, switch3)


topos = { 'mytopo': ( lambda: MyTopo() ) }

Everything seems normal, but pingall fails :

mininet> pingall
*** Ping: testing ping reachability
h1 -> X 
h2 -> X 
*** Results: 100% dropped (0/2 received)

This is also depicted in DLUX. In the topology, only the switches are shown, and without any links between them. However if I type the command :

mininet> links

in Mininet, I get :

h1-eth0<->s1-eth3 (OK OK)
h2-eth0<->s3-eth3 (OK OK)
s1-eth1<->s2-eth1 (OK OK)
s1-eth2<->s3-eth1 (OK OK)
s2-eth2<->s3-eth2 (OK OK)

What is going wrong?

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
0

answered 2017-02-13 02:35:22 -0800

90.suman gravatar image

Install feature l2switch . This is required to add flows on ovs which will enable communication between VMs.

edit flag offensive delete publish link more

Comments

I have already installed it.

marievi ( 2017-02-13 02:44:44 -0800 )edit

Can you check if flows corresponding to your topology are there on ovs or not?

90.suman ( 2017-02-13 02:57:12 -0800 )edit
0

answered 2017-05-27 11:59:21 -0800

Sorry not an answer

I see the same pb with Boron-SR3 with default topology. I have mininet and ODL running on Xenial on Vagrant. local controller works fine on mininet

mininet> dump Host h1: h1-eth0:10.10.10.3 pid=9900> Host h2: h2-eth0:10.10.10.2 pid=9903> Host h3: h3-eth0:10.0.0.3 pid=9906> OVSSwitch{'protocols': 'OpenFlow13'} s1: lo:127.0.0.1,s1-eth1:None,s1-eth2:None pid=9912> OVSSwitch{'protocols': 'OpenFlow13'} s2: lo:127.0.0.1,s2-eth1:None,s2-eth2:None,s2-eth3:None pid=9915> OVSSwitch{'protocols': 'OpenFlow13'} s3: lo:127.0.0.1,s3-eth1:None,s3-eth2:None pid=9918> RemoteController{'ip': '192.168.3.240', 'port': 6633} c0: 192.168.3.240:6633 pid=9894>

mininet>

ubuntu@mininet:~$ sudo ovs-ofctl -O Openflow13 dump-flows s1 OFPSTFLOW reply (OF1.3) (xid=0x2): ubuntu@mininet:~$ sudo ovs-ofctl -O Openflow13 dump-flows s2 OFPSTFLOW reply (OF1.3) (xid=0x2): ubuntu@mininet:~$ sudo ovs-ofctl -O Openflow13 dump-flows s3 OFPSTFLOW reply (OF1.3) (xid=0x2): ubuntu@mininet:~$ mininet> pingall * Ping: testing ping reachability h1 -> * h1 : ('ping -c1 10.10.10.2',) PING 10.10.10.2 (10.10.10.2) 56(84) bytes of data. From 10.10.10.3 icmpseq=1 Destination Host Unreachable

--- 10.10.10.2 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

X * h1 : ('ping -c1 10.0.0.3',) connect: Network is unreachable X h2 -> * h2 : ('ping -c1 10.10.10.3',) PING 10.10.10.3 (10.10.10.3) 56(84) bytes of data. From 10.10.10.2 icmp_seq=1 Destination Host Unreachable

--- 10.10.10.3 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

X * h2 : ('ping -c1 10.0.0.3',) connect: Network is unreachable X h3 -> * h3 : ('ping -c1 10.10.10.3',) PING 10.10.10.3 (10.10.10.3) 56(84) bytes of data. From 10.0.0.3 icmp_seq=1 Destination Host Unreachable

--- 10.10.10.3 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

X * h3 : ('ping -c1 10.10.10.2',) PING 10.10.10.2 (10.10.10.2) 56(84) bytes of data. From 10.0.0.3 icmp_seq=1 Destination Host Unreachable

--- 10.10.10.2 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

X * Results: 100% dropped (0/6 received) mininet>

opendaylight-user@root>feature:list -i | more ...... odl-openflowplugin-flow-services | 0.3.3-Boron-SR3 | x | openflowplugin- 0.3.3-Boron-SR3 | OpenDaylight :: Openflow Plugin :: Flow Services
odl-openflowplugin-southbound | 0.3.3-Boron-SR3 | x | openflowplugin- 0.3.3-Boron-SR3 | OpenDaylight :: Openflow Plugin :: Li southbound A odl-openflowplugin-nsf-model | 0.3.3-Boron-SR3 | x | openflowplugin- 0.3.3-Boron-SR3 | OpenDaylight :: OpenflowPlugin :: NSF :: Model
odl-openflowplugin-app-config-pusher | 0.3.3-Boron-SR3 | x | openflowplugin- 0.3.3-Boron-SR3 | OpenDaylight :: Openflow Plugin :: Application - d odl-openflowplugin-app-topology | 0.3.3-Boron-SR3 | x | openflowplugin- 0.3.3-Boron-SR3 | OpenDaylight :: Openflow Plugin :: Application - t odl-openflowplugin-app-forwardingrules-manager | 0.3.3-Boron-SR3 | x | openflowplugin- 0.3.3-Boron-SR3 | OpenDaylight :: Openflow Plugin :: Application ...

(more)

edit flag offensive delete publish link more
Login/Signup to Answer

Stats

Asked: 2017-02-10 00:58:47 -0800

Seen: 504 times

Last updated: May 27