add-host-intent and wipe-out please

[Mohamed Oualla]

Hi all,

I have 2 question please,

the first question is:  After making my linear topology in mininet (3 switch, each one has 1 host)[sudo mn --mac --controller remote --topo linear,3,1]. Activating the reactive forwarding application to find hosts, after deactivating it [app deactivate fwd], and adding an intent for h1 (10.0.0.1) to h3 (10.0.0.3) [ add-host-intent 00:00:00:00:00:01/None 00:00:00:00:00:03/None]. I can ping between the hosts for the first time,  and running the ping command again, the ping can't happen between the two hosts. I checked the intent in my GUI, i see it in orange path between them, also in [intents] command i see that there is an intent for h1 and h3. Does anyone can explain me this? 

The second: It is about [wipe-out please] command, I enter this command to clean the topology in the GUI when I [quit] mininet and [sudo mn -c]. After that I make a new topology in mininet (or the same later topology in command line), in the GUI i see no links between the switches, also in the CLI, using the [links] command i see no result, I activate the reactive forwarding application, and also no ping happen in mininet. I solved this by relunching onos again and making a new topology but i think this is not good.

Mohamed. 

[0ice...@gmail.com]

1) Did the traffic match the flow rules installed in the devices by the intent?  because, maybe the flow rules  mtched by the ping and installed by the fwd are different from those installed by the intent

2) Did you try to deactivate and activate LLDP application?

Best 

davide

[Mohamed Oualla]

Hi!

Thank you mister david.

1) I don't know if the traffic matches the flowrules installed in the devices by the intent. How can i check it please?

2) I disabled it and enable it again, i created the topology, again i disable it and enable, and as you will see in the screens attached, no links are discovred and also in GUI no link. I will repeat this with lunching onos again with out using the wipe-out please command.

[0ice...@gmail.com]

Hi,

1)based on image onos_scr_1, the devices aren't connected to ONOS, you have to run mininet with this flag --controller=remote,ip=[controller IP],port=[controller listening port],  you have to fill them  whit the proper ip and port.

2) In the CLI you should run the command flows (if i remeber well). You can se the flow rules installed in the devices using the "Description window" that you get when you select the device in the GUI

best

[Mohamed Oualla]

Hi,

1) Thank you, that make sense, how can I get onos listening port?

[Mohamed Oualla]

I tried the port 6653 and 6633 and always i get , unable to connect. Attached you will find the result.

[Mohamed Oualla]

1)I relunched onos again, i found the right port which is 6653, and it connect to it fine, i disconnected and connceted different time and it works fine.

[Mohamed Oualla]

Now for the problem of intent,

I checked the flows, they seem natural for me.

Attached you will find 3 screens, one showing that no ping happens, installing the intent and checking it and the last showing the flows on the three switches.