• Tag : 4.20.1F

 
 

Traffic Steering using User-Defined Fields

This article describes the TAP Aggregation User-Defined Fields feature. The purpose of the User-Defined Fields feature is to provide custom offset pattern matching to be used in TAP Aggregation Traffic Steering. This allows for deeper packet inspection of up to 128 bytes. User-Defined Fields, or UDFs, are defined as part of an access-list filter and are comprised of an offset, length and pattern match. This describes a single portion of any incoming packet to match the provided value upon. Access-list filters containing a UDF are then applied as usual as part of a TAP Aggregation Traffic Steering policy. UDFs may also be...
Continue reading →

TapAgg truncation

EOS-4.18.1F added truncation capability for Tap Aggregation, which allows tapped traffic to be truncated to a smaller size before being transmitted. It can be used to reduce the amount of traffic received by analysis devices, if only the headers are to be analyzed while the payload of the packets is irrelevant or unwanted for practical or legal reasons. An example could be the analysis of packets in a video streaming network where packets would typically have large payloads that are not necessarily useful for the analyzers. Packet truncation can be configured on tap or tool ports: Truncation configured on a...
Continue reading →

SNMP MIB support for “show hardware capacity”

Hardware Table Capacity Monitoring is an existing feature to keep track of the capacity and utilization of various hardware forwarding resources and generate alerts/syslogs when the utilization exceeds a threshold value. With SNMP MIB support, Users can use SNMP server to monitor hardware utilization. Whenever utilization exceeds threshold value, Switch sends SNMP traps in addition to alerts/syslogs. The Main use-case would be for troubleshooting in overflow situations and avoid overflows altogether by taking corrective actions on high utilization. Platform compatibility DCS-7280E DCS-7500E DCS-7050SX DCS-7050TX DCS-7050QX DCS-7260CX DCS-7260QX DCS-7160-32CQ DCS-7160-48YC6 DCS-7160-48TC6 Configuration SNMP Configuration EOS supports a growing number of both...
Continue reading →

Packet Time Stamping on the 7500R/7280R/7500E/7280E

Time stamping is an important tool for network engineering and performance analysis. EOS-4.18.1F added header time stamping of all packets received on any tap interface in Tap Aggregation mode at line rate (only supported on the 7500R/7280R/7500E/7280E series). A timestamp is taken on ingress and then inserted in packet headers on egress. Time Synchronization and Time Keeping In order to have accurate time stamps, the system must be set up to synchronize its time keeping engine on the data plane to a master clock. Prior to 4.20.5F, the clocks used for time stamping are not synchronized with external sources. Beginning...
Continue reading →

EVPN extension to BGP using VXLAN

Ethernet VPN (EVPN) is an extension of the BGP protocol introducing a new address family: L2VPN (address family number 25) / EVPN (subsequent address family number 70). It is used to exchange overlay MAC and IP address reachability information between BGP peers within a tunnel [1]. In EOS 4.18.1F VXLAN tunnel support was introduced [2]. The available features are: Single-homing L2 routes (EVPN type 2 and type 3), with MLAG used as the L2 multi-homing solution. Multi-homing L2 routes (EVPN type 1 and type 2) are received and installed, with up to two all-active remote paths per destination (additional paths...
Continue reading →

BFD RFC7130

This document describes about RFC7130 on EOS. RFC7130 defines a mechanism to run BFD protocol on LAG with an independent asynchronous BFD session on every LAG member link. With the support of RFC7130, any broken or erroneous member link of the LAG is cleared out with up BFD session flap on the member link. Configuration The following configuration example enables this feature under a routed or switchport port-channel. Arista(config-if-po1)#bfd per-link rfc-7130 Arista(config-if-po1)#[ no | default ] bfd neighbor 10.0.0.4 This enables or disables BFD RFC7130 on that port-channel. It is disabled by default. Please note that both the above configurations...
Continue reading →

LDP Pseudowire

The LDP pseudowire feature provides support for emulating Ethernet connections over a Multiprotocol Label Switching (MPLS) network using the extension of the MPLS Label Distribution Protocol (LDP) specified in RFC4447. The patch panel configuration mode allows “patching” a local interface “connector” to an LDP pseudowire “connector” terminating on the local switch. The LDP pseudowire itself is defined under the pseudowires configuration mode, under the mpls ldp configuration mode. This feature also supports locally patching traffic between two interfaces or subinterfaces and is again configured under the patch panel configuration mode. Both these features support tagged (type 4) and raw (type...
Continue reading →

RFC 3107 – BGP Labeled Unicast and Recursive route resolution of IPV4 BGP Routes using tunnels

The BGP labeled-unicast (LU) RFC is used to advertise BGP routes with a stack of MPLS labels, thereby allowing distribution of MPLS tunnel paths through BGP.  The BGP peers that have negotiated labeled unicast capability can carry one or more labels as part of the network layer reachability information (NLRI) in the route advertisement. Recursive route resolution of IPv4 BGP routes using tunnels allows for BGP route nexthops to be resolved through tunnel paths received from BGP or other protocols. Platform Compatibility DCS-7500R series DCS-7500E series Configuration The following configuration commands have been added to supported this functionality. Configuration for labeled-unicast capability The following command submode...
Continue reading →

L3 Interface Ingress Counters

L3 interface ingress counters can be used to count routable traffic coming into the box on sub-interfaces and vlan interfaces with L3 address (IPv4 and/or IPv6 address) configured. Such traffic will get accounted irrespective of routing decision. L3 interface counters are not supported on routed ports. Platform compatibility DCS-7050X DCS-7250X DCS-7300X series Configuration L3 interface ingress counters for subinterfaces can be enabled using the following configuration: 7050(config)#[no] hardware counter feature subinterface in L3 interface ingress counters for vlan-interfaces can be enabled using the following configuration: 7050(config)#[no] hardware counter feature vlan-interface in Note that L3 interface ingress counters are not enabled...
Continue reading →

Hardware Table Capacity Monitoring

Hardware Table Capacity Monitoring is a new feature to keep track of the capacity and utilization of various hardware forwarding resources and generate alerts/syslogs when the utilization exceeds a threshold value. Users can keep track of the current usage statistics using a single show command, and also configure thresholds on a per-resource basis, to be notified about any high-utilization upfront, before reaching any resource limits. The Main use-case would be for troubleshooting in overflow situations and avoid overflows altogether by taking corrective actions on high utilization. Platform compatibility DCS-7280E DCS-7500E DCS-7160-32CQ DCS-7160-48YC6 DCS-7160-48TC6 Configuration The concept of threshold is used...
Continue reading →

Automatic MLAG ISSU Compatibility Detection

This feature detects whether a given EOS image is MLAG ISSU compatible with the currently running version on a switch. If the given new image is found to be incompatible then all EOS versions which are potentially compatible to both the given EOS image and the currently running image are listed. Also this adds support to generate additional Mlag ISSU compatibility warnings while reloading the switch or while issuing ‘show mlag issu warning’ command. All the EOS images has an Mlag ISSU Compatibility matrix published as part of the Release Notes. This matrix shows which images are compatible to a...
Continue reading →

MPLS encapsulation

EOS 4.15.0F adds support for MPLS encapsulation of IP packets in EOS. The functionality is exposed through two mechanism(s): 1) We can have static IP routes which have a label associated with it, all IP packets hitting this route will get encapsulated with the MPLS label specified and sent out. This is supported for both V4 and V6 static IP routes 2) We can also program a NexthopGroup of type MPLS. For releases before 4.20, each NexthopGroup can have up to 4 MPLS label(s) associated with it.  Release 4.20 onwards, this maximum label stack size is different for different chip types....
Continue reading →

Follow

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

Join other followers: