Setup Guide
sFlow
sFlow is a standard-based sampling technology embedded within switches and routers which is used to monitor network trac. It is
designed to provide trac monitoring for high-speed networks with many switches and routers.
Topics:
• Overview
• Implementation Information
• Enabling and Disabling sFlow on an Interface
• Enabling sFlow Max-Header Size Extended
• sFlow Show Commands
• Conguring Specify Collectors
• Changing the Polling Intervals
• Back-O Mechanism
• sFlow on LAG ports
• Enabling Extended sFlow
Overview
The Dell EMC Networking Operating System (OS) supports sFlow version 5.
sFlow is a standard-based sampling technology embedded within switches and routers which is used to monitor network trac. It is
designed to provide trac monitoring for high-speed networks with many switches and routers. sFlow uses two types of sampling:
• Statistical packet-based sampling of switched or routed packet ows.
• Time-based sampling of interface counters.
The sFlow monitoring system consists of an sFlow agent (embedded in the switch/router) and an sFlow collector. The sFlow agent resides
anywhere within the path of the packet and combines the ow samples and interface counters into sFlow datagrams and forwards them to
the sFlow collector at regular intervals. The datagrams consist of information on, but not limited to, packet header, ingress and egress
interfaces, sampling parameters, and interface counters.
Application-specic integrated circuits (ASICs) typically complete packet sampling. sFlow collector analyses the sFlow datagrams received
from dierent devices and produces a network-wide view of trac ows.
Implementation Information
Dell EMC Networking sFlow is designed so that the hardware sampling rate is per line card port-pipe and is decided based on all the ports
in that port-pipe.
If you do not enable sFlow on any port specically, the global sampling rate is downloaded to that port and is to calculate the port-pipe’s
lowest sampling rate. This design supports the possibility that sFlow might be congured on that port in the future. Back-o is triggered
based on the port-pipe’s hardware sampling rate.
For example, if port 1 in the port-pipe has sFlow congured with a 16384 sampling rate while port 2 in the port-pipe has sFlow congured
but no sampling rate set, the system applies a global sampling rate of 512 to port 2. The hardware sampling rate on the port-pipe is then set
at 512 because that is the lowest congured rate on the port-pipe. When a high trac situation occurs, a back-o is triggered and the
hardware sampling rate is backed-o from 512 to 1024. Note that port 1 maintains its sampling rate of 16384; port 1 is unaected because it
maintains its congured sampling rate of 16384.:
50
856 sFlow