Sflow Documentation for Configuration about ixp-manager HOT 9 CLOSED

BTW: I have created a bundle (called "ixpm-sflow-to-rrd") which is all autoconf-ed, automake-d and separately installable. I hadn't got around to posting it yet, but it might be useful - I will do so very soon, and will point you and our INEX friends (@barryo, @nickhilliard, ...) to it. Also, I've written and successfully used a mammoth (~1300 LOC) portable shell-script auto-installer for IXP-Manager which I will finish writing up and uploading either tonight or tomorrow (it works for a minimal hands-off IXP-M install, including downloading/compiling/installing sflowtool, installing/configuring mrtg, rrdcached, smokeping, etc). I have it tuned to run on Debian Wheezy, but have structured it in a way that with a few minimal tweaks it will work for other platforms. For now it installs all on one server, and with other restrictions, but the aim is for those restrictions to be remedied in time, and in the meantime it also acts as a good "documentation by example". I suspect that will help...

from ixp-manager.

OK, I managed to upload the auto-installer. Will try to get to the ixpm-sflow-to-rrd thing later...

from ixp-manager.

Hey @rowanthorpe thanks, for the script, but now have to do much more reverse engineering. Still not know how to configure the sflow integration on ubuntu. E.g. what are the necessary command line options for sflowtool?

https://github.com/inex/IXP-Manager/wiki/Installing-Sflow-Support should be updated.

from ixp-manager.

@bcix sflowtool --help shows the possible flags. For example a basic setup listening on port 807 for sflow traffic arriving as IPv4 (whether or not it is reporting v4 or both v4 and v6) I would use these opts -4 -p 807 -l. If you need sflow to be available to other tools too a common trick is to use another sflowtool instance as a repeater e.g. have one sflowtool -p 807 -4 -f 127.0.0.1/808 -f 127.0.0.1/809 and the IXP-M instance would have sflowtool -p 808 -4 -l, and the one for the other tool would have sflowtool -p 809 .... As I mentioned before I will try to get my little "ixpm-sflow-to-rrd" bundle online soon. No time yet...

from ixp-manager.

At INEX, we have several sflowtool daemons running. The first listens on the sflow socket and fans out to three other daemons:

• ixp manager sflow support sflowtool -4 -p 6343 -f 127.0.0.1/5500 -f 127.0.0.1/5501 -f 193.242.111.xx/6343
• bgp listener for peering matrix sflowtool -4 -p 5501 -l
• ixp manager development environment sflowtool -4 -p 5500 -l

It's important to specify -4 in sflowtool >= 3.23 because otherwise it will listen on both ipv4 and ipv6 sockets. If you have multiple sflow daemons running, they will interfere with each other.

from ixp-manager.

wiki updated.

from ixp-manager.

Can we get some fluff around the application.ini configuration? I am
working through this and am confused on where sflow.rootdir = could or
should be. Was this set in the rrdcached configuration? I might have
missed it.

Thanks,
Cheers,
Brian

On Mon, Sep 23, 2013 at 9:40 AM, Nick Hilliard [email protected]:

wiki updated.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/72#issuecomment-24933942
.

from ixp-manager.

-> [email protected]

from ixp-manager.

(added more wiki updates)

from ixp-manager.