command line add-host-intent not working

1,498 views
Skip to first unread message

Ali Kheradmand

unread,
May 26, 2016, 5:13:54 PM5/26/16
to onos...@onosproject.org
Hi 

I have a simple topology created using mininet which is connected to a single onos instance as controller:
h1 <-> s1 <-> h2

I try to add a host to host intent between h1 and h2 using command line:

onos> add-host-intent 2A:34:D1:AF:0F:55/None 56:7E:FB:CE:91:17/None 
Host to Host intent submitted:
HostToHostIntent{id=0x0, key=0x0, appId=DefaultApplicationId{id=18, name=org.onosproject.cli}, priority=100, resources=[2A:34:D1:AF:0F:55/None, 56:7E:FB:CE:91:17/None], selector=DefaultTrafficSelector{criteria=[]}, treatment=DefaultTrafficTreatment{immediate=[NOACTION], deferred=[], transition=None, meter=None, cleared=false, metadata=null}, constraints=[LinkTypeConstraint{inclusive=false, types=[OPTICAL]}], one=2A:34:D1:AF:0F:55/None, two=56:7E:FB:CE:91:17/None}

The intent installs two flow rules:
onos> flows -n 
deviceId=of:0000000000000001, flowRuleCount=2
    id=450000513d18c0, state=ADDED, bytes=0, packets=0, duration=87, priority=100, tableId=0, appId=org.onosproject.net.intent, payLoad=null, selector=[IN_PORT:2, ETH_DST:56:7E:FB:CE:91:17, ETH_SRC:2A:34:D1:AF:0F:55], treatment=DefaultTrafficTreatment{immediate=[OUTPUT:1], deferred=[], transition=None, meter=None, cleared=false, metadata=null}
    id=450000cfcf651f, state=ADDED, bytes=0, packets=0, duration=87, priority=100, tableId=0, appId=org.onosproject.net.intent, payLoad=null, selector=[IN_PORT:1, ETH_DST:2A:34:D1:AF:0F:55, ETH_SRC:56:7E:FB:CE:91:17], treatment=DefaultTrafficTreatment{immediate=[OUTPUT:2], deferred=[], transition=None, meter=None, cleared=false, metadata=null}

But I can not ping h1 from h2 or h2 from h1:
mininet> h2 ping h1
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
From 10.0.0.2 icmp_seq=1 Destination Host Unreachable

mininet> h1 ping h2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
From 10.0.0.1 icmp_seq=1 Destination Host Unreachable

However, if I activate "fwd" app:
onos> app activate org.onosproject.fwd

Even though it installs the exact the same flow rules:
onos> flows -n
deviceId=of:0000000000000001, flowRuleCount=2
    id=450000513d18c0, state=ADDED, bytes=882, packets=9, duration=347, priority=100, tableId=0, appId=org.onosproject.net.intent, payLoad=null, selector=[IN_PORT:2, ETH_DST:56:7E:FB:CE:91:17, ETH_SRC:2A:34:D1:AF:0F:55], treatment=DefaultTrafficTreatment{immediate=[OUTPUT:1], deferred=[], transition=None, meter=None, cleared=false, metadata=null}
    id=450000cfcf651f, state=ADDED, bytes=882, packets=9, duration=347, priority=100, tableId=0, appId=org.onosproject.net.intent, payLoad=null, selector=[IN_PORT:1, ETH_DST:2A:34:D1:AF:0F:55, ETH_SRC:56:7E:FB:CE:91:17], treatment=DefaultTrafficTreatment{immediate=[OUTPUT:2], deferred=[], transition=None, meter=None, cleared=false, metadata=null}

Ping works:
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_seq=1 ttl=64 time=0.060 ms

After deactivating "fwd" ping fails again. I was wondering what the problems may be. 

I built onos commit 80244e5424663c4b85df95f221761947a92ee63b and installed it on Ubuntu version 16.04. 

Jonathan Hart

unread,
Jun 3, 2016, 12:19:33 AM6/3/16
to Ali Kheradmand, onos...@onosproject.org
I think the reason the host-to-host intent doesn't seem to be working is because ARPs are not resolved. You can check this by running 'h1 arp -an' in the mininet console, and it should say 'incomplete'.

Try running the 'org.onosproject.proxyarp' app to let ONOS forward ARP packets for you. The fwd app will forward ARP packets as well as ICMP, so that is why that works.

Thanks,

Jono

--
You received this message because you are subscribed to the Google Groups "ONOS Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to onos-dev+u...@onosproject.org.
To post to this group, send email to onos...@onosproject.org.
Visit this group at https://groups.google.com/a/onosproject.org/group/onos-dev/.
To view this discussion on the web visit https://groups.google.com/a/onosproject.org/d/msgid/onos-dev/CAAOQ%3DW0RStfQideTO3nDRLXYFaAVgnyDW_3brrKZOUcP%3DJYpDg%40mail.gmail.com.

abdulha...@gmail.com

unread,
Jun 24, 2020, 1:08:42 AM6/24/20
to ONOS Developers, a.i.khe...@gmail.com, jo...@onlab.us
Thank you so much for the valuable comment. You really saved my day!

Regards. 


On Thursday, June 2, 2016 at 9:19:33 PM UTC-7, Jonathan Hart wrote:
I think the reason the host-to-host intent doesn't seem to be working is because ARPs are not resolved. You can check this by running 'h1 arp -an' in the mininet console, and it should say 'incomplete'.

Try running the 'org.onosproject.proxyarp' app to let ONOS forward ARP packets for you. The fwd app will forward ARP packets as well as ICMP, so that is why that works.

Thanks,

Jono

To unsubscribe from this group and stop receiving emails from it, send an email to onos...@onosproject.org.

Osama Abu Hamdan

unread,
Oct 19, 2021, 2:04:49 PM10/19/21
to ONOS Developers, Jonathan Hart
Saved my day!
Thanks!

Franco Jaraba

unread,
May 25, 2022, 11:55:29 AM5/25/22
to ONOS Developers, oabuh...@nevada.unr.edu, Jonathan Hart
In 2022 this response still useful! Thanks! 

Mohamed Oualla

unread,
Jun 27, 2022, 4:41:08 PM6/27/22
to ONOS Developers, Franco Jaraba, oabuh...@nevada.unr.edu, Jonathan Hart
SUMMER OF 2K22 Still useful! Thank you Jono !
Reply all
Reply to author
Forward
0 new messages