Details
-
Bug
-
Status: Resolved
-
Resolution: Duplicate
-
None
-
None
-
None
-
Operating System: Linux
Platform: PC
-
384
Description
I used the the base edition of the release artifact for Hydrogen.
I run a controller with -of13 option, and run a Mininet OF 1.0.
mininet@mininet-vm:~$ sudo mn --controller=remote,ip=192.168.60.180 --topo tree,2
I executed ping command from h1 to h3, but all packets does not reach to h3.
mininet> h1 ping h3
^CPING 10.0.0.3 (10.0.0.3) 56(84) bytes of data.
— 10.0.0.3 ping statistics —
3008 packets transmitted, 0 received, 100% packet loss, time 3031057ms
At the time, I saw an ERROR message on the OSGi console.
2014-01-28 20:55:35.835 EST [pool-26-thread-4] ERROR o.o.o.o.m.c.t.PortStatusMessageToNodeConnectorUpdatedTranslator - PortStatusMessage: version 1 dataPathId 2 portNo 1
2014-01-28 20:55:40.127 EST [md-sal-binding-commit-14] WARN o.o.c.t.internal.TopologyManagerImpl - Ignore edge that contains invalid node connector: (MD_SAL|openflow:1:2@MD_SAL|openflow:1->MD_SAL|openflow:3:3@MD_SAL|openflow:3)
2014-01-28 20:55:45.121 EST [md-sal-binding-commit-5] WARN o.o.c.t.internal.TopologyManagerImpl - Ignore edge that contains invalid node connector: (MD_SAL|openflow:1:2@MD_SAL|openflow:1->MD_SAL|openflow:3:3@MD_SAL|openflow:3)
On the other hand ping between h1 and h2 worked well.
mininet> h1 ping h2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.0.0.2: icmp_req=2 ttl=64 time=0.156 ms
64 bytes from 10.0.0.2: icmp_req=3 ttl=64 time=0.037 ms
I think this issues is related to the following issue.
Attachments
Issue Links
- blocks
-
OPNFLWPLUG-67 OpenFlow 1.3 plugin does not discover topology with mininet 2.0 on Ubuntu Precise
- Resolved
- duplicates
-
CONTROLLER-232 Packet loss on first time ping test
- Resolved