[ovs-discuss] Flow Expiration returning zeros for byte/packet counts

David Erickson derickso at stanford.edu
Fri Nov 13 21:25:45 UTC 2009


Jesse Gross wrote:
> 
> 
> Jesse Gross wrote:
>>
>>
>> David Erickson wrote:
>>> I've attached the packet dump of the netflow message from the switch 
>>> causing the problems. Also as an aside, I was only able to get it to 
>>> send one netflow message because my machine returned an icmp error 
>>> back to ovs since I am not listening on that port.. is there a way to 
>>> disregard those errors and keep sending netflow messages?
>>
>> Can you also send the flow expiration messages from the 3 switches 
>> like you did in your first email?  It's hard to tell if there is a 
>> problem without something to compare it to.
> 
> And please send the log file as well (/var/log/ovs-vswitchd.log) for the 
> run of NetFlow + expiration messages.
> 

Nov 13 13:21:50 epic nox: 30509|Flow_tracker:DBG Flow expiration from 
dpid: 002320e86a21 duration: 10 pkts: 173679 bytes: 262253537 flow: 
port0001:vlanffff mac22:db:ed:04:cb:a4->7a:4a:0f:e9:1b:bd proto0800 
ip10.79.2.13->10.79.2.12 port80->39761
Nov 13 13:21:50 epic nox: 30510|Flow_tracker:DBG Flow expiration from 
dpid: 002320e86a21 duration: 10 pkts: 20473 bytes: 1357163 flow: 
port0000:vlanffff mac7a:4a:0f:e9:1b:bd->22:db:ed:04:cb:a4 proto0800 
ip10.79.2.12->10.79.2.13 port39761->80

Nov 13 13:21:51 epic nox: 30514|Flow_tracker:DBG Flow expiration from 
dpid: 00304897ffef duration: 10 pkts: 173679 bytes: 262253537 flow: 
port0001:vlanffff mac22:db:ed:04:cb:a4->7a:4a:0f:e9:1b:bd proto0800 
ip10.79.2.13->10.79.2.12 port80->39761
Nov 13 13:21:51 epic nox: 30515|Flow_tracker:DBG Flow expiration from 
dpid: 00304897ffef duration: 10 pkts: 20472 bytes: 1357089 flow: 
port0002:vlanffff mac7a:4a:0f:e9:1b:bd->22:db:ed:04:cb:a4 proto0800 
ip10.79.2.12->10.79.2.13 port39761->80


Nov 13 13:21:51 epic nox: 30518|Flow_tracker:DBG Flow expiration from 
dpid: 003048b06117 duration: 11 pkts: 20473 bytes: 1357163 flow: 
port0001:vlanffff mac7a:4a:0f:e9:1b:bd->22:db:ed:04:cb:a4 proto0800 
ip10.79.2.12->10.79.2.13 port39761->80
Nov 13 13:21:51 epic nox: 30519|Flow_tracker:DBG Flow expiration from 
dpid: 003048b06117 duration: 11 pkts: 24184 bytes: 252386859 flow: 
port0002:vlanffff mac22:db:ed:04:cb:a4->7a:4a:0f:e9:1b:bd proto0800 
ip10.79.2.13->10.79.2.12 port80->39761

The crux is the netflow message is matching the flow expiration.  There 
was nothing in the ovs-vswitchd.log file other than messages about 
connecting to NOX and exiting fail-open mode, which was well before this 
test was performed.

-David
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ovs_netflow.log
Type: text/x-log
Size: 202 bytes
Desc: not available
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20091113/9ede2684/attachment-0004.bin>


More information about the discuss mailing list