• Tag : Telemetry

 
 

Inband Telemetry

Description For network monitoring and troubleshooting flow related issues, it is desirable to know the path, latency, queue and congestion information for flows at different times. The inband telemetry feature(INT) is used to gather per flow telemetry information like path, per hop latency and congestion. For enabling inband telemetry, inband telemetry domain should be created using switches which support inband telemetry. Interfaces on the edge of the domain should be configured as edge ports and interfaces inside the domain as core ports. On edge ports, sampling of packets is done at ingress and INT flows are terminated at egress. INT...
Continue reading →

Inband Network Telemetry (INT) Support on 7170

Description The  Inband Network Telemetry – eXport Data (INT-XD) feature is used to gather flow, queue, drop telemetry information like network path, hop latency, queue congestion, drop reasons etc which are used for network monitoring and troubleshooting. INT-XD supports flow, queue and drop telemetry reports. Flow telemetry report is generated from flow events. Flow events include new flows, change in the attributes of flow like ingress/egress port or latency. Flow reports include information about the path that packets traverse as well as other telemetry metadata such as hop latency and queue occupancy. Drop reports provide visibility into the impact of...
Continue reading →

InfluxDB telemetry streaming

Description InfluxDB telemetry streaming feature enables telemetry data collection with Telegraf on-box, and allows streaming of telemetry to an off-box InfluxDB instance. Platform compatibility All platforms support this feature. Configuration InfluxDB telemetry streaming has its dedicated CLI at: switch(config)#monitor telemetry influx switch(config-monitor-telemetry-influx)#? destination Configure telemetry output destinations source Configure telemetry input paths tag Add extra tags to the telemetry output ---------------------------------------- comment Up to 240 characters, comment for this mode default Set a command to its defaults exit Leave mon-telemetry-influx mode no Disable the command that follows show Display details of switch operation !! Append to comment Destination Configuration Destination...
Continue reading →

Postcard Telemetry

Description The postcard telemetry feature is used to gather per flow telemetry information like path and per hop latency. For network monitoring and troubleshooting flow related issues, it is desirable to know the path, latency and congestion information for flows at different times. Postcard telemetry samples flows at every switch, aggregates them and sends the samples to a collector with path and latency information using GRE encapsulation. For calculating latency information, switches in the network need to be in PTP sync. This information is processed by the collector and may be stored in a time series database for providing per...
Continue reading →

CVP Telemetry for non-Arista devices

Hi All, Quick question on Telemtry part, I understand CVP uses Telemetry protocol and gets data stored in Sysdb of Arista switches. Wondering, can Telemetry be supported for non-Arista devices which support gRPC protocol. If it is supported, what kind of licenses to be purchased If not supported, what functionalities that CVP can offer to non-Arista devices and what license to be procured for this   Thanks in advance

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 →

BFD session telemetry

Description BFD (Bidirectional Forwarding Detection) session telemetry allows for the collection of per-session statistics as well as rbfd kernel module statistics to be automatically collected at a set interval and stored in shared memory where Cloud Vision Portal (CVP) or other applications may gather them.  Previously, this information was only available to the user via execution of several CLI show-commands.  In addition, several new statistics have been added which are updated within the session-stats interval and provide a finer “snapshot” view of session health than the previously-available session lifetime statistics.  This feature supports both hardware-accelerated and software (kernel module) accelerated...
Continue reading →

TerminAttr most commonly used flags and sample configurations

Introduction TerminAttr is the EOS state streaming telemetry agent running as a single binary that can stream to both CloudVision and 3rd party applications using gNMI. It has been bundled with every EOS release from 4.17.0F and above and it’s also available as a SWIX extension which can be used to upgrade TerminAttr to the latest version. It is recommended to check the release notes for the latest recommended stable version and compatibility between EOS releases. How to check which version of TerminAttr is running on EOS As the release notes say, the minimum supported TerminAttr version on each EOS...
Continue reading →

gNMIReverse Examples

Introduction gNMIReverse is a Dial-Out gRPC service (available on our Github page) that reverses the direction of the dial for gNMI Subscriptions, where the gNMIReverse client (running along with gNMI target) on the switch sends data to the gNMIReverse Server. This article contains steps on how to build the gNMIReverse client and server binaries and examples on how to configure the daemon to run the gNMIReverse client on EOS. Prerequisite The following tools are required to proceed with this setup including cloning the repository and compiling client binary for EOS. Go Git Installing and configuring gNMIReverse client Building the client...
Continue reading →

CloudVision Event Guide

Contents Overview CloudVision Portal Events Streaming Analytics Error CVE Bug Exposed Change Control Failed Change Control Running Change Control Succeeded Clock Not Synchronized Anomaly in CloudTracer Latency CVX Disconnection Low Disk Partition Space Available Disk Partition Usage Approaching Threshold Packet Loss Detected for CloudTracer Host High CPU Load High CPU Utilization High QSFP DOM Temperature High QSFP DOM Voltage High SFP DOM Temperature High SFP DOM Voltage Interface Went Down Unexpectedly Interface Went Down Expectedly Unexpected Link Change Expected Link Change Tunnel Interface Went Down EOS Version Change High Interface Alignment Errors Abnormally Large Frames Abnormally Small Frames High Interface...
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 →

Sending Telemetry Data from TerminAttr to Multiple CVP instances

Sending Telemetry Data from TerminAttr to Multiple CVP instances Overview This article will explore the ability of the CloudVision Telemetry agent to send data to more than one CloudVision Portal (CVP) instance or CloudVision and a third party application.     The configuration used in this lab was also used as part of the “Synchronising CloudVision Portal Configlets with Ansible” POC lab to enable both CloudVision instances to receive Telemetry data from all the switches. The article for “Synchronising CloudVision Portal Configlets with Ansible” can be found here : https://eos.arista.com/synchronising-cloudvision-portal-configlets-with-ansible/   Introduction The Proof of Concept Lab created to demonstrate...
Continue reading →

How to you gather non snmp Telemetry Data

Hi I’m trying to get used to get CLI values to influxdb. I’ve setuped telegraf on EOS, it works perfect for snmp. Arista have interesting trending data which are not available via snmp, like: * show storm-control * show interface transceiver csv I’ve written python scripts, which uses FastCli -T 5 -p2 -c "" The scripts works perfect if i execute them in bash. If i’m running it as telegraf.exec, the system user get’s the error “Cannot connect to ConfigAgent”. Im using: 4.21.8M on Arista DCS-7050SX3-48YC8-F How do you gather such Cli-only data for your trending platforms? Did you have...
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 or more...
Continue reading →

CloudVision Portal 2017.2.0 – TOI

CloudVision Portal release 2017.2.0 introduces support for the network-wide Telemetry framework consisting of the following components: NetDB based State Streaming CloudVision Analytics Engine CloudVision Telemetry Application Deployment and Configuration State Streaming deployment details: Minimum supported EOS version for state streaming is 4.17.3F EOS version 4.19 and later are not supported in this release but will be supported in the next release The latest version of state streaming (v0.19.5) is bundled with CVP 2017.2.0 as an extension that can be deployed on supported EOS versions Configuration required to enable state streaming on EOS devices is packaged in this release as a...
Continue reading →

Follow

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

Join other followers: