• Tag : sflow

 
 

Support for sFlow sample truncation size

Description By default, sFlow samples that are generated have a fixed size: 128 bytes. This feature adds support for a configurable option to configure software sFlow sample truncation size between the range of [128, 512]. When a sample packet size is less than configured sample truncate size, the sample is not truncated. However, if a sample is bigger than the configured sample truncate size, the sample is truncated to the configured value. Supported platforms All devices supporting software sFlow  Configuration To configure sFlow sample truncation size between [128, 512], the following configuration can be applied. By default, the sFlow sample...
Continue reading →

Sampled Flow Tracking IPv4 Hardware Offload

Description Sampled flow tracking with IPFIX export is supported on most of the Arista platforms. User configured sampling rate is used for sampling in ingress direction on the configured interfaces. An EOS software agent on CPU processes samples received from hardware, samples are used to create flow records that are exported to IPFIX collectors. Refer to Sampled flow tracking TOI for additional details.    The hardware offload feature maintains the IPv4 flow cache in hardware whilst also offloading CPU intensive tasks like packet parsing and counting packets and bytes for flows to the hardware. Both IPv4 and IPv6 flow information...
Continue reading →

Sampled flow tracking with IPFIX export

Description Network administrators require access to flow information that passes through various network elements, for the purpose of analyzing and monitoring their networks. This feature provides access to IP flow information by sampling traffic flows in ingress direction on the interfaces on which it is configured. The samples are then used to create flow records, which are exported to the configured collectors in the IPFIX format. Terminology Flow tracker : Collection of interfaces (observation points) on which samples are collected and flow records are created. It has one or more Exporters. Exporter : Device that sends flow records to one...
Continue reading →

Sampled Flow Tracking with IPFIX Export

Description Network administrators require access to flow information that passes through various network elements, for the purpose of analyzing and monitoring their networks. This feature provides access to IP flow information by sampling traffic flows in ingress direction on the interfaces on which it is configured. The samples are then used to create flow records, which are exported to the configured collectors in the IPFIX format. Terminology Flow tracker : Collection of interfaces (observation points) on which samples are collected and flow records are created. It has one or more Exporters. Exporter : Device that sends flow records to one...
Continue reading →

Support for software egress sFlow

Description This feature adds support for a selected set of configured interfaces to collect egress flow samples. Egress sFlow can be configured on ethernet and port-channel interfaces. Egress samples are taken after the packet has been rewritten by the egress pipeline. As a result, packets that are dropped due to egress ACL deny rules or due to congestion will not be sampled. Hardware acceleration is not currently supported for egress sFlow and all sample processing is performed in software. Supported platforms DCS-7500R DCS-7280R DCS-7500R2 DCS-7280R2 As of 4.25.2F, support for the following platforms were added. DCS-7280R3 DCS-7500R3 DCS-7800R3 Configuration To...
Continue reading →

VxLAN ingress sflow

Hi! I configured sflow, and it works for packet coming from ethernet interfaces, but i didn’t see any packets coming from vxlan tunnels. Is this supported?

Flow Analytics (Beta)

Flow Analytics (Beta) NOTE: This is a beta feature in the 2019.1.0 and 2020.1.0 release and is not enabled by default. In order to enable the Flow Analytics and  feature, it is recommended that the minimum VM resources are configured at the recommended minimum for production deployments : CPUs: 28 cores RAM: Recommended 52 GB Disk: 1 TB This feature is GA in the 2020.2.0 and later releases and is enabled by default.                                       Viewing Traffic Flows         CloudVision’s traffic flows introduced in...
Continue reading →

Configurations and Optimizations for Internet Edge Routing

Introduction For many years, network deployments for enterprise Internet edge environments have consisted of dedicated routing platforms and a switching or aggregation layer to distribute this to various network zones.  With the advances in merchant silicon forwarding engines and the software expertise put into Arista’s Extensible Operating System (EOS), we can now fully replace this legacy architecture with a collapsed routing and switching layer using Arista R Series platforms.  Arista R Series platforms allow for holding a full copy of the Internet routing table for both IPv4 and IPv6 in hardware (the Forwarding Information Base, or FIB) with plenty of...
Continue reading →

Configuring Traffic Flows using sFlow in CVP (Cloudvision Portal) 2019.1.x

Introduction Many users rely on 3rd party flow tools to enable greater visibility into the network and generate alerts when irregular flows have been detected.  However, with the growing number of tools being used to provide this visibility, each with their own strengths, the user may experience tool sprawl.   In order to ease the number of tools required within an environment and move towards the goal of a “Single Pane of Glass” to manage our networks, Cloudvision Portal 2019.1.x provides a built-in IPFIX/sFlow collector that will show the top flows within a network.  Once these flows are collected, they can...
Continue reading →

BGP sFlow export in multi-agent mode

Description Sflow samples can be augmented with additional Extended gateway data by getting data from BGP in addition to sFlow’s standard IP information. The additional BGP information can be seen in sFlow Version 5 doc under extended_gateway. Extended gateway data was already supported in gated mode. Now it is being supported for multi-agent mode (arBGP). Starting in EOS 4.22.1F v6 non-default vrf traffic is supported Starting in EOS 4.23.2F ECMP traffic is supported Platform compatibility This feature is supported on all platforms. Configuration A BGP instance must be configured on the switch for BGP sFlow export to operate. rtr1(config)#sflow run...
Continue reading →

Sflow Subinterfaces

Description Packets sampled for sFlow are packaged in a flow sample structure containing, amongst other things, input and output port information. For single interfaces, port information is represented by the ifIndex of the interface. This feature allows for subinterface input and output port ifIndex values to be included in a sample, in place of parent interface ifIndexes. Samples in sFlow may be encoded in two formats: compact or expanded. The format  used depends on how ifIndex values are used on the device in question. If an sFlow agent will never use ifIndex values >= 2^24, then it must use compact...
Continue reading →

Failed samples – Does the sflow agent detect drops?

We would like to use as high sampling frequency as possible, i.e. going below the dangerous sampling rate limit of 16384. If the switch fails to sample a packet the sFlow protocol contains a counter for that, named drops. See struct flow_sample in https://sflow.org/sflow_version_5.txt Does the sflow agent detect drops?

Sflow Output Subinterfaces

Sflow Output Subinterfaces Packets sampled for sFlow are packaged in a flow sample structure containing, amongst other things, input and output port information. For single interfaces, port information is represented by the ifIndex of the interface. This feature allows for subinterface output port ifIndex values to be included in a sample, in place of parent interface ifIndexes. Samples in sFlow may be encoded in two formats: compact or expanded. The format  used depends on how ifIndex values are used on the device in question. If an sFlow agent will never use ifIndex values >= 2^24, then it must use compact...
Continue reading →

Arista 7280SR BGP sflow on vlan interfaces

Hello, I am using BGP on Arista 7280SR, and the ip are on vlan interfaces (not sub-interfaces). I’d like to enable sflow and its BGP extension to see the traffic per-AS with AS-stats / elastiflow, although I cannot enter the following command, which is not available in interface vlan configuration mode. sflow enable Is it a limitation of the Jericho chip, EOS, or did I misunderstand the way I’m supposed to get BGP extension informations via sflow in my setup ? Thank you.

Sampled Flow Tracking with IPFIX export

Description Network administrators require access to flow information that passes through various network elements, for the purpose of analyzing and monitoring their networks. This feature provides access to IP flow information by sampling traffic flows in ingress direction on the interfaces on which it is configured. The samples are then used to create flow records, which are exported to the configured collectors in the IPFIX format. Terminology Flow tracker: Collection of interfaces (observation points) on which samples are collected and flow records are created. It has one or more Exporters. Exporter: Device that sends flow records to one or more...
Continue reading →

Sflow IPv4 Tunnel Extension

When packets are encapsulated in tunnels via protocols such as GRE, sFlow samples with version 5 default extensions do not contain some important information about the packet including the IP address of the tunnel destination. Several additional, optional, tunnel extensions are defined in sFlow Tunnel Structure. The sFlow IPv4 tunnel extension feature provides the ability to add the extended_ipv4_tunnel_egress structure to packets forwarded via GRE next-hop groups. Platform Compatibility DCS-7280R DCS-7280R2 Configuration The tunnel extension is added to compatible samples by configuring sFlow on a device and then adding the desired tunnel extension sample configuration. For example: Arista(config)#sflow run Arista(config)#sflow...
Continue reading →

sFlow extension BGP in multi-agent

Description Sflow samples can be augmented with additional Extended gateway data by getting data from BGP in addition to sFlow’s standard IP information. The additional BGP information can be seen in sFlow Version 5 doc under extended_gateway. Extended gateway data was already supported in gated mode. Now it is being supported for multi-agent mode (arBGP). Platform compatibility This feature is supported on all platforms. Configuration A BGP instance must be configured on the switch for BGP sFlow export to operate. rtr1(config)#sflow run rtr1(config)#sflow extension bgp Show Commands bgprtr1(config)#show sflow sFlow Configuration ------------------- Destination(s):   127.0.0.1:54855 (VRF: default) Source(s):   10.10.10.10 (VRF: default)...
Continue reading →

Impact of CU/Performance when increasing sFlow sampling rate

Hi everyone, We looks to increase the sFlow sampling rate to 100 (1 sample per 100 packets). The document states that it is possible with “dangerous” option but it doesn’t state the impact on CPU and the switch performance. Is there anyone who has the same deployment? Can you advise or point to the document that explains the impact of such change in the configuration? Thanks

Follow

Get every new post on this blog delivered to your Inbox.

Join other followers: