How is sFlow packets routed?

47 views
Skip to first unread message

Jake

unread,
Feb 10, 2016, 9:49:00 AM2/10/16
to sFlow
Hi,
I'm not sure what is the best way to deploy sFlow.
1) Should the sFlow packets be routed on the same links as the data or should I have different links which are used only for the sFlow data (i.e. each switch has different ports for data and for sFlow traffic)?
2) Who is responsible to determine how is the sFlow packets routed from the switch to the collector? If it's an SDN network, I guess the controller should install rules for the forwarding of sFlow packets?

Thanks,
Jake

Peter Phaal

unread,
Feb 10, 2016, 10:24:12 AM2/10/16
to sFlow
By design, the volume of sFlow traffic will be a small fraction of the
total traffic on the network (controlled by the sampling rate). The
sFlow datagram sending process is desynchronized across data sources
and agents and appears as random background traffic. Typically sFlow
will be to a collector on the management network (also used to carry
other control and management traffic - SNMP, ssh, netconf, OpenFlow
etc). In-band, the management traffic is typically tagged with its own
VLAN, or if the switches have capability, the traffic may be carried
on dedicated out of band network.

SDN networks require a way to connect the switch control plane to the
controllers. If you have that connectivity you should also be able to
receive sFlow over the same routed path.
> --
> You received this message because you are subscribed to the Google Groups
> "sFlow" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sflow+un...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Jake

unread,
Feb 11, 2016, 3:43:42 AM2/11/16
to sFlow
Thanks!
Regarding SDN, you assume that the sFlow traffic is routed to the controllers hence it can be router in the same way path that the switches and the controllers communicate.
But what is the sFlow collectors are separated from the controllers? for example, if you have several machines in the network which act as sFlow collectors.

Peter Phaal

unread,
Feb 11, 2016, 9:53:03 AM2/11/16
to sFlow
You would typically want more than one controller for redundancy /
scaleability. The same network setup should allow for multiple sFlow
collectors on the management network.

It is also possible to use OpenFlow to replicate a sFlow streams to
multiple collectors:
http://blog.sflow.com/2013/11/udp-packet-replication-using-open.html
Reply all
Reply to author
Forward
0 new messages