• Author : Jeevan Kamisetty


Hardware flow tracking with IPFIX export

Description Arista campus switches allow extensive and fine grained hardware based flow tracking and management features. They provide the capability to collect and export flow telemetry to an external observation node (collector), using IPFIX protocol. The below diagram shows how hardware flow tracking engine can be used to perform flow tracking and flow export in a campus network. It can track flows traversing through the given set of interfaces in a switch and send the collected flow information to a collector. The hardware flow tracking engine allows flow tracking and metering functions on upto 32K concurrent flows. Flows are tracked...
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 →

DHCPv6 Snooping Remote-ID (Option-37) Insertion

Description DHCPv6 relay supports Remote-ID option insertion in relay messages providing the Layer-3 interface name on which DHCPv6 relay is configured. However, DHCPv6 relay can’t provide Layer-2 information. This feature implements DHCPv6 snooping functionality to intercept DHCPv6 messages and insert Remote-ID option containing Layer 2 information such as VLAN and interface name. Remote-ID option uses the message format described in RFC4649, remote-id field contains DHCP Unique Identifier with LinkLayerAddress (DUID-LL) to achieve uniqueness and sub-option is a string representation of Layer-2 interface name and VLAN number separated by ‘:’ character. For example, DHCP solicit message received on interface Ethernet3/1 configured...
Continue reading →


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

Join other followers: