[ovs-discuss] In 'OVS Faucet Tutorial', router does not work as expected at 'Step 4: Router Broadcasts ARP Request'

2017-12-24 Thread Robin Lee
Hi,

I am new to OVS and just doing 'OVS Faucet Tutorial'.

But everything is OK until 'Step 4: Router Broadcasts ARP Request',
the router does not send ARP broadcast requrest in my environment.

After I run:
ovs-appctl ofproto/trace br0
in_port=p1,dl_src=00:01:02:03:04:05,dl_dst=ff:ff:ff:ff:ff:ff,dl_type=0x806,arp_spa=10.100.0.1,arp_tpa=10.100.0.254,arp_sha=00:01:02:03:04:05,arp_tha=ff:ff:ff:ff:ff:ff,arp_op=1
-generate

ovs-appctl ofproto/trace br0
in_port=p1,dl_src=00:01:02:03:04:05,dl_dst=0e:00:00:00:00:01,udp,nw_src=10.100.0.1,nw_dst=10.200.0.1,nw_ttl=64
-generate

The sandbox/p4.pcap does not received any ARP request broadcast.


My environment is also prepared following the tutorial.

OVS is instalded from Fedora 27 repo:
Step 4: Router Broadcasts ARP Request'
and run with tutorial/ovs-sandbox in the git repo.

Faucet is 1.6.14 and run in docker as instructed.

-robin
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss


Re: [ovs-discuss] VMs can't ping each between two physical hosts within same subnet

2017-12-24 Thread Hui Xiang
Finally found the root cause, for some reason the dpdk device has the same
mac address with the device has the tunnel ip.

 1(dpdk0): addr:90:e2:ba:d8:c9:88
 config: 0
 state:  LIVE
 current:10GB-FD
 speed: 1 Mbps now, 0 Mbps max

 LOCAL(br-prv): addr:90:e2:ba:d8:c9:88
 config: 0
 state:  LIVE
 current:10MB-FD COPPER
 speed: 10 Mbps now, 0 Mbps max


On Sun, Dec 24, 2017 at 9:55 AM, Hui Xiang  wrote:

> My other question is does ovs/ovn support pre-population of tunnel's info
> in the fdb/arp table.
>
> On Sat, Dec 23, 2017 at 11:20 AM, Hui Xiang  wrote:
>
>> Hi folks,
>>
>>
>>   I have a problem on vms spawned between twp physical hosts within same
>> subnet.
>> they are connected with Geneve tunnel based on dpdk.
>>
>>   With tracing and debugging, find that the remote tnl arp request will
>> be dropped by the host having the initailed ping vm.
>>
>>   This problem can be fixed by restarted ovs-vswitchd.
>>
>>
>>   two geneve tunnels:  168.254.100.13  168.254.100.14
>>   two vms: 192.168.10.3192.168.10.2
>>
>>   I have compared the logs with datapath flow:
>>
>>   [Works]
>>   2017-12-22T06:23:54.767Z|00263|dpif_netdev(pmd12)|DBG|ovs-netdev: miss
>> upcall:
>> skb_priority(0),skb_mark(0),ct_state(0),ct_zone(0),ct_mark(
>> 0),ct_label(0),recirc_id(0),dp_hash(0),in_port(2),packet_
>> type(ns=0,id=0),eth(src=3e:65:7c:f5:3e:4a,dst=e2:a6:0b:28:
>> b9:43),eth_type(0x0806),arp(sip=168.254.100.13,tip=168.
>> 254.100.14,op=1,sha=3e:65:7c:f5:3e:4a,tha=00:00:00:00:00:00)
>> arp,vlan_tci=0x,dl_src=3e:65:7c:f5:3e:4a,dl_dst=e2:a6:0b
>> :28:b9:43,arp_spa=168.254.100.13,arp_tpa=168.254.100.14,arp_
>> op=1,arp_sha=3e:65:7c:f5:3e:4a,arp_tha=00:00:00:00:00:00
>> 2017-12-22T06:23:54.767Z|00264|dpif(pmd12)|DBG|netdev@ovs-netdev:
>> get_stats success
>> 2017-12-22T06:23:54.767Z|00265|dpif_netdev(pmd12)|DBG|flow_add:
>> ufid:4ef92ea7-67b0-4bc3-8a0c-a4e379f2fe83 recirc_id(0),in_port(2),packet
>> _type(ns=0,id=0),eth(src=3e:65:7c:f5:3e:4a,dst=e2:a6:0b:
>> 28:b9:43),eth_type(0x0806),arp(op=1/0xff), actions:1
>>
>>  [Bad]
>>  5990 2017-12-22T03:28:28.386Z|00290|dpif_netdev(pmd84)|DBG|flow_add:
>> ufid:7d555719-c5dc-4e1b-bfff-1851f88aabe7 recirc_id(0),in_port(3),packet
>> _type(ns=0,id=0),eth(src=90:e2:ba:dd:fa:60,dst=
>> ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=168.254.100.13,tip=168.254.100.14,op=1/0xff),
>> actions:drop
>>
>> My question is which openflow has translated into above datapath action
>> drop for bad case, and is there any way to check which function/file
>> translate it or responsible of the geneve tunnel arp processing? The only
>> thing I can use is to adding logs to code and rerun so far.  Thank you very
>> much for your help.
>>
>> Hui.
>>
>>
>>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss


Re: [ovs-discuss] lacp to mellanox switch -- "COLLECTING NOT Enabled !! DISCARDING FRAME"

2017-12-24 Thread Amit Nishry
Hi Raymond,

> > Can you open a case at
> > https://mymellanox.force.com/support/SupportLogin  and we will be
> > happy to help you.
> 
> We have case# 00416594
> 
> > Are you running OpenFlow on the switch or only using the switch L2
> > with LAG/bond?

I have reviewed your logs in the case, I'm not sure they are the latest, but 
from the logs it seems that you have mpo3 in shutdown state on both switches.

> The switch is mlnxos.  We are only using switch L2 with LAG/bond.
> 

I have tested MLNX-OS 3.6.5000 with OVS 2.5.0 with the configuration below, 
please review if it's different for yours

=== OVS Config ===
ovs-vsctl add-br br0
ovs-vsctl add-bond br0 bond0 ens1f0 ens1f1
ovs-vsctl set port bond0 lacp=active
ovs-appctl bond/show bond0
ovs-appctl lacp/show bond0
ovs-vsctl list port bond0

=== SW01 ===
   protocol mlag
   interface mlag-port-channel 9
   interface ethernet 1/9 mlag-channel-group 9 mode active
   interface mlag-port-channel 9 no shutdown
   mlag-vip MLNX ip 10.143.34.222 /24 force
no mlag shutdown
   lacp

=== SW02 ===
   protocol mlag
   interface mlag-port-channel 9
   interface ethernet 1/9 mlag-channel-group 9 mode active
   interface mlag-port-channel 9 no shutdown
   mlag-vip MLNX ip 10.143.34.222 /24 force
no mlag shutdown
  lacp




Let continue the discussion in the SF case and if we find an issue with OVS we 
will reply here.

Thanks,
Amit
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss