|
From: Neil M. <nei...@in...> - 2015-05-27 22:05:42
|
Adam, Try configuring the ULOG feature, as described here: http://blog.sflow.com/2010/12/ulog.html If your OS is a recent one, then this won't work because ULOG was subsumed into netfilter/NFLOG. I am working on adding the NFLOG feature this week, though it's not clear that we will be able to get the kernel-based sampling this way, so there might be a performance hit. For packet-samples you should use the sampling.<speed> settings in hsflowd.conf. Such as: sampling.100M = 500 sampling.1G = 1000 If you run Linux hypervisors, then enabling sFlow in Open vSwitch will also give you the packet-samples (with efficient kernel-based sampling). The easiest way to configure that is just to run the sflowovsd daemon alongside hsflowd on the hypervisor. Neil On Wed, May 27, 2015 at 2:39 PM, Adam Pavlidis <ada...@gm...> wrote: > Hello, > > i am trying to use hsflowd (version is 1.19) to monitor traffic on a linux > server. > After starting the daemon, /var/log/syslog has no errors. > > hsflowd.conf: > > > *sflow {* > > * DNSSD = off* > > * polling = 30* > > > * sampling = 40* > > * collector {* > > * ip = A.B.C.D* > > * udpport = 6343* > > * }* > *}* > > > Then, i started generating some traffic. My collector at IP A.B.C.D never > received flow samples, it receives however counters samples in the > intervals set in the configuration file. (I verified the above using > tcpdump) > > My general goal is to sample traffic passing through a server and send > them to a collector, to substitute sampling performed by switches (i prefer > sflow). > > If i have misunderstood and hsflowd is not meant to sample a host's > received/sent traffic, is there any other way that i can achieve this? > > > Thank you very much in advance > > > ------------------------------------------------------------------------------ > > _______________________________________________ > host-sflow-discuss mailing list > hos...@li... > https://lists.sourceforge.net/lists/listinfo/host-sflow-discuss > > |