Operating System: Windows
Platform: PC

This bug should be fixed at current master, please verify if the topology is working.

Yes, this has been fixed and working fine now. I am able to see the links.

However, I still having issues with the errors shown in OSGi logs after starting the mininet (of13/of10) simulation. This is reported in OPNFLWPLUG-148 and waiting for the fix status to be merged.

Thanks,
Madhusudhan

Tony,

Topology is not cleared on the GUI now after disconnecting mininet (both of13/of10).

However, when I check at the inventory, it is cleared and working as expected.

GET http://127.0.0.1:8080/controller/nb/v2/connectionmanager/nodes

Thanks,
Tony

Bugfix in https://git.opendaylight.org/gerrit/#/c/6785/1 . Incorrect edge update was sent to topology manager on link removed.

Hi Tony,

Thanks for the fix. Topology is cleared on the GUI after disconnecting mininet (both of13/of10)

I got the following in the topology:

1. When using mininet (of10) simulation: sudo mn --topo tree,2 --controller 'remote,ip=10.125.136.52,port=6633' --switch ovsk,protocols=OpenFlow13

The below stats is correct.

Node ID Ports
MD_SAL|openflow:1 3
MD_SAL|openflow:3 4
MD_SAL|openflow:2 4

2. When using mininet (of13) simulation: sudo mn --topo tree,2 --controller 'remote,ip=10.125.136.52,port=6633' --switch ovsk,protocols=OpenFlow13

Node ID Ports
MD_SAL|openflow:1 2
MD_SAL|openflow:3 3
MD_SAL|openflow:2 3

Shouldn't be the same stats as shown using mininet (of10)?

Sorry for the typo error.

Please assume the below point

1. When using mininet (of10) simulation: sudo mn --topo tree,2 --controller 'remote,ip=10.125.136.52,port=6633' --switch ovsk,protocols=OpenFlow13

as this one.

1. When using mininet (of10) simulation: sudo mn --topo tree,2 --controller 'remote,ip=10.125.136.52,port=6633'

This is working for me now, what about you Madhusudhan?

Luis, Were you able to see the correct ports on the GUI?

Everything works fine except the above thing!

Hi Madhu, I see the same as you but this is totally unrelated issue so please open a new bug for it. For this new bug I already saw it could be because of the internal switch connector type in the AD-SAL switch manager. For the same topology:

Using OF13 simulation, the internal switch connector is type SW and does not show in GUI:

GET http://localhost:8080/controller/nb/v2/switchmanager/default/node/MD_SAL/openflow:1

{
"properties": {
"name":

,
"state":

,
"config":

},
"nodeconnector": {
"node":

,
"id": "0",
"type": "SW"
}
},

Using OF10 simulation, the internal switch connector is type MD_SAL and shows in GUI:

"properties": {
"name":

,
"state":

,
"config":

},
"nodeconnector": {
"node":

,
"id": "openflow:1:65534",
"type": "MD_SAL"
}
},

Thanks Luis. I agree with your logic. The new issue is not related to the title of this bug.

Hence this bug stands resolved!

Madhusudhan - if its resolved - can you mark it fixed?

Hi Abhijit,

This issue is fixed and verified. Moved the status to FIXED.

BR/Madhu

I opened OPNFLWPLUG-178 for the issue that is nothing to do with this bug.