Your sampling rate is 1-in-64 packets. A few pings aren’t likely to register.
You should try larger flows with ping -f or iperf. The following article uses iperf to demonstrate how sFlow is used to detect large flows: http://blog.sflow.com/2013/06/large-flow-detection.html The article also shows how to enable sFlow on OVS using ovs-vsctl, it’s not enough to just create an entry in the sFlow table, you also need to apply the sFlow settings to each bridge. On Dec 1, 2013, at 6:40 PM, WEIYU LIU <weiyu....@utah.edu> wrote: > Thanks very much. Guys. > > Yeah, I configured sFlow and attached br0 to it. It information is as follows: > _uuid : 62e112ce-6728-43e0-b6e0-2c490d9c6ab9 > agent : "eth4" > external_ids : {} > header : 128 > polling : 10 > sampling : 64 > targets : ["10.1.2.3:6343"] > > I installed Host sFlow in the same server which OVS is running and started > the service. Then I ping from a virtual machine in the subnet connected by > one port on br0 to the subnet connected by the other port. The sFlow data > that collector received is like this: > > startDatagram ================================= > datagramSourceIP 10.1.2.2 > datagramSize 500 > unixSecondsUTC 1385951399 > datagramVersion 5 > agentSubId 100000 > agent 10.1.1.2 > packetSequenceNo 625 > sysUpTime 6245000 > samplesInPacket 1 > startSample ---------------------- > sampleType_tag 0:2 > sampleType COUNTERSSAMPLE > sampleSequenceNo 625 > sourceId 2:1 > counterBlock_tag 0:2001 > adaptor_0_ifIndex 1 > adaptor_0_MACs 1 > adaptor_0_MAC_0 000000000000 > adaptor_1_ifIndex 4 > adaptor_1_MACs 1 > adaptor_1_MAC_0 0024e877aa79 > adaptor_2_ifIndex 3 > adaptor_2_MACs 1 > adaptor_2_MAC_0 0024e877aa77 > adaptor_3_ifIndex 2 > adaptor_3_MACs 1 > adaptor_3_MAC_0 0024e877aa75 > adaptor_4_ifIndex 6 > adaptor_4_MACs 1 > adaptor_4_MAC_0 0010185690c4 > counterBlock_tag 0:2005 > disk_total 6250827776 > disk_free 3904507904 > disk_partition_max_used 37.53 > disk_reads 45396 > disk_bytes_read 592641024 > disk_read_time 125024 > disk_writes 84358 > disk_bytes_written 1016946688 > disk_write_time 6303800 > counterBlock_tag 0:2004 > mem_total 12453888000 > mem_free 10422276096 > mem_shared 0 > mem_buffers 142540800 > mem_cached 769376256 > swap_total 1075376128 > swap_free 1075376128 > page_in 300466 > page_out 496556 > swap_in 0 > swap_out 0 > counterBlock_tag 0:2003 > cpu_load_one 0.000 > cpu_load_five 0.010 > cpu_load_fifteen 0.050 > cpu_proc_run 0 > cpu_proc_total 137 > cpu_num 8 > cpu_speed 2395 > cpu_uptime 75809 > cpu_user 166330 > cpu_nice 0 > cpu_system 166450 > cpu_idle 602957660 > cpu_wio 2857080 > cpuintr 40 > cpu_sintr 18780 > cpuinterrupts 10014268 > cpu_contexts 11451223 > counterBlock_tag 0:2006 > nio_bytes_in 3377818 > nio_pkts_in 32075 > nio_errs_in 0 > nio_drops_in 0 > nio_bytes_out 1879144 > nio_pkts_out 14825 > nio_errs_out 0 > nio_drops_out 0 > counterBlock_tag 0:2000 > hostname gateway.ciexperiment.cs6480.emulab.net > UUID 4c4c4544004235108036c6c04f534b31 > machine_type 3 > os_name 2 > os_release 3.2.0-56-generic > endSample ---------------------- > endDatagram ================================= > > It seems just contain the sflow data about the server which the Host sFlow > was installed but no data about the network usage. Did I miss something? > > Besides, when I ran "ifconfig br0 10.0.0.1/24", it said that the device br0 > can not be found. Moreover, in hsflowd.auto file, the agentIP and agent is > eth2, which is one port that I connected to br0. Does this make sense in my > case? > > Thanks a lot. > ________________________________________ > From: Justin Pettit [jpet...@nicira.com] > Sent: Sunday, December 01, 2013 7:00 PM > To: WEIYU LIU > Cc: discuss@openvswitch.org discuss > Subject: Re: [ovs-discuss] Using OVS+Host sFlow to monitor network traffic > > Did you actually configure sFlow? The commands you listed below don't > indicate that. You should either look at the example in ovs-vsctl (and read > the ovs-vswitchd.conf.db man page) or follow Peter Phaal's suggestion. > > --Justin > > > On Dec 1, 2013, at 4:55 PM, WEIYU LIU <weiyu....@utah.edu> wrote: > >> Hey, I followed the configuration example and the FAQ. My specific >> configuration is as follows: >> >> sudo ovs-vsctl add-br br0 >> ovs-vsctl add-bond br0 bond0 eth1 eth2 >> >> But the sflow data caught by the host with the collector IP still does not >> have the package through the bridge. What other configuration that I need to >> follow if I want to get the sflow data about the bandwidth usage of the br0 >> and the package through br0? >> >> Thanks a lot. >> >> Weiyu >> ________________________________________ >> From: Justin Pettit [jpet...@nicira.com] >> Sent: Sunday, December 01, 2013 4:38 PM >> To: WEIYU LIU >> Cc: discuss@openvswitch.org discuss >> Subject: Re: [ovs-discuss] Using OVS+Host sFlow to monitor network traffic >> >> Please keep this on the mailing list. The man page should be with your OVS >> distribution ("man ovs-vsctl"). It's also in the Documentation tab of the >> Open vSwitch web site. >> >> --Justin >> >> >> On Dec 1, 2013, at 3:36 PM, WEIYU LIU <weiyu....@utah.edu> wrote: >> >>> Thanks very much for your reply. Not yet. Would you please send me the >>> address of this page? Thanks. >>> >>> Weiyu >>> From: Justin Pettit [jpet...@nicira.com] >>> Sent: Sunday, December 01, 2013 4:31 PM >>> To: WEIYU LIU >>> Subject: Re: [ovs-discuss] Using OVS+Host sFlow to monitor network traffic >>> >>> On Sun, Dec 1, 2013 at 11:24 AM, WEIYU LIU <weiyu....@utah.edu> wrote: >>> I used OVS to create a bridge to connect two subnets. And then I created an >>> sflow and attached it to the bridge. But it does not send sflow data to the >>> collector. I also installed a Host sFlow on that server, but it just >>> monitors the local server's performance. I am wondering how can I let the >>> ovs send sflow data to the configured collector or how can I connect the >>> Host sFlow to OVS to let it monitor the traffic on the virtual bridge. I >>> will really appreciate if you can give me some advice. Thanks a lot. >>> >>> Did you try the example configuration in the ovs-vsctl man page? >>> >>> --Justin >> >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
