Hi Ben,

I tried in vain to replicate your success with ovs-controller.  My
ovs-openflowd  is showing the following warnings.  Not sure what it
means

Feb 17 11:31:39|00060|dpif|WARN|system@dp0: failed to flow_get (No
such file or directory)
in_port(2),eth(src=00:14:22:72:38:d1,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=172.27.74.160,tip=172.27.74.205,op=1,sha=00:14:22:72:38:d1,tha=00:00:00:00:00:00),
packets:0, bytes:0, used:never
Feb 17 11:31:39|00061|dpif|WARN|system@dp0: failed to flow_get (No
such file or directory)
in_port(1),eth(src=00:d0:05:5d:24:00,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=171.67.74.2,tip=171.67.75.3,op=1,sha=00:d0:05:5d:24:00,tha=00:00:00:00:00:00),
packets:0, bytes:0, used:never
Feb 17 11:31:39|00062|dpif|WARN|system@dp0: failed to flow_get (No
such file or directory)
in_port(2),eth(src=00:d0:05:5d:24:00,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=171.67.74.2,tip=171.67.75.3,op=1,sha=00:d0:05:5d:24:00,tha=00:00:00:00:00:00),
packets:0, bytes:0, used:never
Feb 17 11:31:39|00063|dpif|WARN|system@dp0: failed to flow_get (No
such file or directory)
in_port(1),eth(src=00:14:22:72:38:d1,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=172.27.74.160,tip=172.27.74.205,op=1,sha=00:14:22:72:38:d1,tha=00:00:00:00:00:00),
packets:0, bytes:0, used:never
Feb 17 11:31:39|00064|dpif|WARN|system@dp0: failed to flow_get (No
such file or directory)
in_port(2),eth(src=00:d0:05:5d:24:00,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=171.67.74.2,tip=171.67.75.5,op=1,sha=00:d0:05:5d:24:00,tha=00:00:00:00:00:00),
packets:0, bytes:0, used:never
Feb 17 11:31:40|00065|dpif|WARN|Dropped 5 log messages in last 1
seconds due to excessive rate
Feb 17 11:31:40|00066|dpif|WARN|system@dp0: failed to flow_get (No
such file or directory)
in_port(2),eth(src=00:14:22:72:38:d1,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=172.27.74.160,tip=172.27.74.205,op=1,sha=00:14:22:72:38:d1,tha=00:00:00:00:00:00),
packets:0, bytes:0, used:never
Feb 17 11:31:40|00067|dpif|WARN|Dropped 11 log messages in last 1
seconds due to excessive rate
Feb 17 11:31:40|00068|dpif|WARN|system@dp0: failed to flow_get (No
such file or directory)
in_port(2),eth(src=00:14:22:72:38:d1,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=172.27.74.160,tip=172.27.74.205,op=1,sha=00:14:22:72:38:d1,tha=00:00:00:00:00:00),
packets:0, bytes:0, used:never
Feb 17 11:31:41|00069|dpif|WARN|Dropped 23 log messages in last 1
seconds due to excessive rate
Feb 17 11:31:41|00070|dpif|WARN|system@dp0: failed to flow_get (No
such file or directory)
in_port(2),eth(src=00:14:22:72:38:d1,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=172.27.74.160,tip=172.27.74.205,op=1,sha=00:14:22:72:38:d1,tha=00:00:00:00:00:00),
packets:0, bytes:0, used:never
Feb 17 11:31:42|00071|dpif|WARN|Dropped 11 log messages in last 1
seconds due to excessive rate
Feb 17 11:31:42|00072|dpif|WARN|system@dp0: failed to flow_get (No
such file or directory)
in_port(2),eth(src=00:14:22:72:38:d1,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=172.27.74.160,tip=172.27.74.205,op=1,sha=00:14:22:72:38:d1,tha=00:00:00:00:00:00),
packets:0, bytes:0, used:never
Feb 17 11:31:43|00073|dpif|WARN|Dropped 21 log messages in last 1
seconds due to excessive rate
Feb 17 11:31:43|00074|dpif|WARN|system@dp0: failed to flow_get (No
such file or directory)
in_port(2),eth(src=00:14:22:72:38:d1,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=172.27.74.160,tip=172.27.74.205,op=1,sha=00:14:22:72:38:d1,tha=00:00:00:00:00:00),
packets:0, bytes:0, used:never
Feb 17 11:31:44|00075|dpif|WARN|Dropped 9 log messages in last 1
seconds due to excessive rate
Feb 17 11:31:44|00076|dpif|WARN|system@dp0: failed to flow_get (No
such file or directory)
in_port(2),eth(src=00:0d:93:8a:a2:89,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0800),ipv4(src=172.27.75.110,dst=172.27.75.255,proto=17,tos=0),udp(src=17500,dst=17500),
packets:0, bytes:0, used:never
Feb 17 11:31:45|00077|dpif|WARN|Dropped 25 log messages in last 1
seconds due to excessive rate
Feb 17 11:31:45|00078|dpif|WARN|system@dp0: failed to flow_get (No
such file or directory)
in_port(2),eth(src=00:0d:93:8a:a2:89,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0800),ipv4(src=172.27.75.110,dst=172.27.75.255,proto=17,tos=0),udp(src=17500,dst=17500),
packets:0, bytes:0, used:never

Also the flow entries are:
cookie=0x0, duration=164.486s, table_id=0, n_packets=149,
n_bytes=23869, priority=20000,ip actions=CONTROLLER:65535,NORMAL
 cookie=0x0, duration=164.485s, table_id=0, n_packets=926,
n_bytes=55560, priority=0 actions=NORMAL

I have changed the first entries slightly 'cos I would not have
192.168.0.1 on those ports.  The counters does increment for that
entry nonetheless.

Seems like this can be system specific.  I am using Ubuntu 10.04.
More specifically.  I can throw out the config.log for OVS if that is
useful.
Linux coin 2.6.32-28-generic-pae #55-Ubuntu SMP Mon Jan 10 22:34:08
UTC 2011 i686 GNU/Linux

Not sure what to do here to narrow down the bug.  Any advice is appreciated.

Thanks.

Regards
KK

On 17 February 2011 09:47, Ben Pfaff <b...@nicira.com> wrote:
> On Wed, Feb 16, 2011 at 05:31:48PM -0800, kk yap wrote:
>> I am OVS kernel datapath with ovs-openflowd.  I have installed the
>> following flow entries.
>>
>>  cookie=0x0, duration=292.116s, table_id=0, n_packets=0, n_bytes=0,
>> priority=24576,icmp actions=CONTROLLER:1500
>>  cookie=0x0, duration=292.116s, table_id=0, n_packets=189,
>> n_bytes=36725, priority=24576,udp actions=CONTROLLER:1500
>>  cookie=0x0, duration=292.116s, table_id=0, n_packets=0, n_bytes=0,
>> priority=24576,tcp actions=CONTROLLER:1500
>>  cookie=0x0, duration=292.155s, table_id=0, n_packets=897,
>> n_bytes=53820, priority=0 actions=drop
>>
>> I see that the second entry (i.e., match on UDP packet with dl_type
>> and ip_proto set) is incrementing the counters for n_packets and
>> n_bytes.  But there is no packet-ins received by the controller!  This
>> is with OVS (at head of master branch).
>
> This is quite odd.  I started a controller like this:
>
> ovs-controller --pidfile --max-idle=5 ptcp: --with-flows=flows -vvconn
>
> with the following in the 'flow' file:
>
> priority=20000,ip,nw_dst=192.168.0.1,actions=controller,normal
> priority=0,actions=normal
>
> and then ran a "ping" from 192.168.0.1 to 192.168.0.2.  I saw many
> messages like this in the ovs-controller output:
>
> Feb 17 09:42:15|00122|vconn|DBG|tcp:192.168.0.20:39099: received: 
> OFPT_PACKET_IN (xid=0x0): total_len=98 in_port=1 (via action) data_len=98 
> (unbuffered)
> tunnel0:in_port0001:tci(0) mac50:54:00:00:00:07->50:54:00:00:00:05 type0800 
> proto1 tos0 ip192.168.0.2->192.168.0.1
>
> So the problem is not obvious to me.
>

_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Reply via email to