Tag : 4.21.3F

Description Subinterfaces divide a single ethernet or port channel interface into multiple logical L3 interfaces based on the 802.1q tag (VLAN ID) of incoming traffic. Subinterfaces are commonly used in the L2/L3 boundary device, but they can also be used to isolate traffic with 802.1q tags between L3 peers by assigning each subinterface to a different VRF. L3 subinterface shaping + VRF is also supported. Platform compatibility DCS-7280R Series DCS-7280R2 Series DCS-7500R Series DCS-7500R2 Series DCS-7280R3 Series (as of 4.25.1F) DCS-7500R3 Series (as of 4.25.1F) DCS-7800R3 Series (as of 4.25.1F) Configuring shaping on Subinterface To configure shaping on subinterface: Step...
Continue reading →

Description ContainerTracer provides a composite view of the physical network topology and Kubernetes. Kubernetes and CVX must be installed before configuring ContainerTracer.  It is expected that all Kubernetes nodes exist in the physical topology known to CVX (show network physical-topology hosts). Configuration Creating Kubernetes ContainerTracer Role ContainerTracer requires a Kubernetes service account that has read permissions for Nodes and Pods.  It is recommended that a least privilege read-only user be created within Kubernetes.  The user and role can be created with the sample Kubernetes config below: File: containertracer_user.yml --- kind: ClusterRole apiVersion: rbac.authorization.k8s.io/v1 metadata:   name: containertracer-view rules:   -...
Continue reading →

Description Many Layer 2 VXLAN deployments span more than one physical data center (DC) location. Typically, each DC has several (10’s to 100’s) VTEPs. Each VTEP typically connects a number of servers/hosts. When using VCS, each VTEP also connects to a network controller (CVX), and shares with it the L2 reachability information about its locally attached hosts. VXLAN control service (VCS), running on the CVX is used to distribute L2 reachability information (MAC-VTEP bindings) amongst all the VTEPs. This is used to orchestrate a L2 overlay network in the DC. Typically, each DC functions as a separate island with its...
Continue reading →

Description FIB compression allows us to program routes into the hardware more efficiently. Routes are programmed in the route table of ASIC in switches to do L3 packet forwarding, and the ASIC route table is a precious HW resource. It would be preferable to many users  if the switch can install more routes. FIB compression introduces optimizations that can make use of HW resources more efficiently, and achieve the same result of a larger HW route table size. This feature is especially helpful when there are only a few distinct adjacencies on the switch, and more routes than HW route table can install to...
Continue reading →

Description This is an addendum to the “IP in IP decapsulation” document https://eos.arista.com/eos-4-15-0f/ipinip-decapsulation. The Decap Group counters feature allows the device to count packets and octets that are decapsulated at the termination of the Decap Group. Platform compatibility DCS-7500E DCS-7280E DCS-7500R DCS-7280R DCS-7500R2 DCS-7280R2 Configuration The decap group counter feature can be configured with the command: switch(config)# [ no | default ] hardware counter feature decap-group Show Commands The counter features that are enabled can be displayed using the command:    switch# show hardware counter feature    Feature             Direction         Counter...
Continue reading →

Description BGP Large Communities, as defined in RFC8092, is now supported within EOS. Both standard (4 octets) and extended (8 octets) BGP communities are unsuitable for 4-octet ASN values due to length restrictions. Large Communities (12 octets)  are a set of values each consisting of a 4-octet ASN value plus two 4-octet local-administrator defined values. Large communities are an optional transitive attribute of variable length. There are no predefined large-community types or values. Large communities may be configured alongside standard and extended communities within route-maps using additional configuration commands. This feature is available with the multi-agent routing protocol model and...
Continue reading →

Description This feature enables support for hardware-accelerated sFlow while running in Tap Aggregation exclusive mode. This article will describe how to setup accelerated sFlow, for more information please view the hardware-accelerated sFlow article. Platform Compatibility Fixed platforms 7280SR2A-48YC6 7280CR2-60 7280CR2A-60 7280CR2K-60 7280CR2-30 7280CR2A-30 7280SRAM-48C6 7280SR2K-48C6 Modular platforms 7500R2A-36CQ-LC 7500R2AK-36CQ-LC 7500R2AM-36CQ-LC 7500R2AK-48YCQ-LC Configuration Follow the standard configuration for Tap Aggregation (using exclusive mode). To configure accelerated sFlow, configure the following: (config)# ip routing (config)# sflow run (config)# sflow hardware acceleration (config)# sflow destination 10.0.0.10 (config)# sflow hardware acceleration sample 1024 To verify accelerated sFlow is functional, run the show command: (config)# show...
Continue reading →

Description This feature implements RFC 5310 that allows IS-IS PDUs to be authenticated using following secure hash algorithms (SHA): SHA-1, SHA-224, SHA-256, SHA-384 and SHA-512. The feature is supported in both default and non-default vrf. Unlike the existing authentication scheme based on MD5 and ClearText, with this feature two IS-IS nodes can be configured with different SHA algorithm and secret-key and can still exchange IS-IS PDUs. A IS node has to be configured with one or more key-id mapping that maps a integer to a security association. Security association consists of the secret-key and algorithm to be used. The IS...
Continue reading →

If a network uses deep packet inspection for its ECMP, RFC7432 recommends deployments to use a control word in L2 EVPN MPLS encapsulated packets in the data plane to ensure frame ordering. For interoperability purposes, if there are edge devices in the topology which doesn't support control word, the control word can be optionally disabled. Platform compatibility DCS-7500R DCS-7280R DCS-7500R2 DCS-7280R2 Configuration Disable the Control Word: switch(config)#mpls evpn switch(config-mpls-evpn)#no label-stack control-word switch(config-mpls-evpn)#exit Enable the Control Word: switch(config)#mpls evpn switch(config-mpls-evpn)#label-stack control-word switch(config-mpls-evpn)#exit By default the Control Word knob is enabled. Show commands In case Control Word is disabled we can see...
Continue reading →