• Tag : jericho

 
 

Egress MAC ACLs

Description Security MAC ACLs can be used to permit and/or deny ethernet packets on the egress port by matching on the following fields: Source MAC address Destination MAC address Platform compatibility DCS-7020 DCS-7280R, DCS-7280R2, DCS-7280R3 DCS-7500R, DCS-7500R2, DCS-7500R3 DCS-7800R3 The egress MAC ACL feature on DCS-7500R is supported only if all the linecards are either -R or -R2 series cards The feature is supported only on a device running with the access-list mechanism as TCAM. Configuration To enable the feature, it is required to add its support directly to the current tcam profile or create a new tcam profile based...
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 →

Segment Routing Traffic Engineering Policy (SR-TE) multi-agent routing model TOI

Description Segment Routing Traffic Engineering Policy (SR-TE) aka SR Policy makes use of Segment Routing (SR) to allow a headend to steer traffic along any path without maintaining per flow state in every node. A headend steers traffic into an “SR Policy”.    EOS 4.21.0F added support for SR Policy for the MPLS dataplane (SR-MPLS) for Type-1 SR Policy segments in single agent routing model. EOS 4.22.1F adds support for SR-TE in multi-agent routing model.    For a detailed description of the functional behavior please refer to the “Description” section of EOS 4.21.0F TOI for SR-TE in single agent routing...
Continue reading →

Segment Routing Traffic Engineering Policy (SR-TE) multi-agent routing model TOI

Description Segment Routing Traffic Engineering Policy (SR-TE) aka SR Policy makes use of Segment Routing (SR) to allow a headend to steer traffic along any path without maintaining per flow state in every node. A headend steers traffic into an “SR Policy”. EOS 4.21.0F added support for SR Policy for the MPLS dataplane (SR-MPLS) for Type-1 SR Policy segments in single agent routing model. EOS 4.22.1F adds support for SR-TE in multi-agent routing model. For a detailed description of the functional behavior please refer to the “Description” section of EOS 4.21.0F TOI for SR-TE in single agent routing model. Platform...
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.

Follow

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

Join other followers: