• Tag : 4.22.1F

 
 

Segment Routing Traffic Engineering Policy (SR-TE)

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 adds support for SR Policy for the MPLS dataplane (SR-MPLS) for Type-1 SR Policy segments with BGP and locally configured policies as sources of SR Policies on Arista’s 7500, 7280 families of switches. SR Policy Overview SR Policy identification An SR Policy is identified using a 2-tuple of Endpoint – an IPv4 or IPv6 address which...
Continue reading →

Match COS/Vlan + COS in QoS Policy-Map

Description This feature allows classification of packets based on the COS/Vlan+COS bits in 802.1q header. Platform compatibility DCS-7020R DCS-7020RA DCS-7020SR-24C2 DCS-7020SRG-24C2-F DCS-7280R DCS-7280E DCS-7280R2 DCS-7280SRA DCS-7280SRM-40CX2 DCS-7280TR DCS-7280QR-C36 DCS-7280SRAM-48C6 DCS-7280TRA-48C6 DCS-7280TRA-48C6-M DCS-7500E DCS-7500R DCS-7500R2 DSC-7504 DCS-7508 DCS-7512 DCS-7516 DCS-7280R3 series (since 4.25.2) 7800R3 series linecards (since 4.25.2) 7500R3 series linecards (since 4.25.2) TCAM Profile Configuration A TCAM profile that supports matching on cos / vlan + cos bits is required for this feature to work. An example of such a profile can be found below: hardware tcam profile qos-cos feature acl port ip sequence 45 key size limit 160 key...
Continue reading →

BGP nexthop resolution RIBs

Description This feature adds support for user-configured BGP Nexthop Resolution RIB profiles for various BGP-based services e.g. IP unicast, L3 VPN, EVPN, etc. The feature allows an administrator to customize the next hop resolution semantics of BGP routes with an ordered list, or profile, of resolution RIB domains (i.e., either tunnel or IP domain). This allows EOS to direct specific services over the specified RIB domains, overriding the default behavior. Further, this feature, through the use of user-defined tunnel RIBs, empowers an administrator to further select a subset of tunnelling protocols for specific services. Refer to User-defined tunnel RIBs for...
Continue reading →

ECN Counters per tx-Queue

Description This feature supports counting ECN-marked packets (ECN = Explicit Congestion Notification) on a per egress port per tx-queue basis.   The feature can be used to gather these packet counts via CLI or SNMP.   There are two cases when an ECN-marked (congestion) packet is counted on the egress port/queue: ECN-marked packet ingresses on a certain port and egresses to a port/queue; i.e., the ECN bit is preserved from ingress to egress. Non ECN-marked ingress packets that are ECN-marked due to congestion. On DCS-7260X, DCS-7250X, DCS-7060X, DCS-7050X, DCS-7010, and DCS-7300X, the packet is also a switch-marked packet (i.e., the...
Continue reading →

OSPF routes over GRE tunnels

Description This feature introduces the support for OSPF routes over GRE tunnels under default as well as non-default VRFs. The feature is disabled by default. Platform compatibility DCS-7050X DCS-7050X2 DCS-7250X DCS-7300 DCS-7060X DCS-7060X2 DCS-7260X3 CCS-720XP (Starting in EOS 4.22.1F) DCS-7050SX3 (Starting in EOS 4.22.1F) DCS-7010T (Starting in EOS 4.23.0F) 7368 (Starting in EOS 4.23.1F) vEOS router DPDK mode (MODE=sfe in /mnt/flash/veos-config) Starting 4.24.1F DCS-7020 Not supported on DCS-7020SRG DCS-7280R DCS-7280R2 DCS-7500R Linecards DCS-7500R2 Linecards Starting 4.25.1F DCS-7280R3 Not supported on DCS-7280CR3MK DCS-7500R3 Linecards DCS-7800R3 Linecards Starting 4.25.2F OSPFV3 over GRE Not supported on DCS-7250X, DCS7010T, DCS-7280 Configuration The OSPF ‘tunnel...
Continue reading →

Support for TI-LFA FRR using IS-IS Segment Routing

Description Topology Independent Fast Reroute, or TI-LFA, uses IS-IS SR to build loop-free alternate paths along the post-convergence path. These loop-free alternates provide fast convergence in the range of sub-50 ms. The PLR ( point of local repair – the router where TI-LFA is configured ) switches to these loop-free alternate backup paths in the event of a link down ( link-protection ) or BFD neighbor down (node-protection) event, protecting traffic destined to IS-IS SR node segments, adjacency segments, and anycast segments while the IGP converges and the post-convergence paths are computed. Anycast segment protection is restricted to those segments...
Continue reading →

Simultaneous negotiation of IPv6 unicast and 6PE capabilities in BGP

Support for negotiating and receiving IPv6 unicast and IPv6 labeled-unicast (6PE) updates from a BGP peer. Description Some deployments require IPv6 unicast and 6PE capabilities to be negotiated. An example of one such deployment involves learning routes from a route reflector which itself is getting both 6PE and IPv6 unicast routes. The goal of this feature is to add support for configuring both 6PE and IPv6 unicast on a single peer, which were previously mutually exclusive. Platform compatibility This feature would work on all platforms supporting 6PE. Configuration A new command is now available to configure both 6PE and ipv6-unicast:...
Continue reading →

Chip level next-hop backup failover support

Description This feature allows failover to backup path to occur in constant time per interface going down for features such as RSVP link protection, RSVP node protection, TI-LFA link protection, and BGP PIC. Without this feature enabled, it would take time proportional to the number of paths going over the interface experiencing the link down event to failover to the backup path. With this feature enabled, the failover time would be constant regardless of the number of paths. For example, if a given link has 1000 LSPs going over it that are all protected with a backup next-hop, the convergence...
Continue reading →

Configuration Lock

Description This mechanism allows a session to lock the configuration of the switch to prevent any other session from altering the configuration. The configuration lock is intended to be short-lived and allows a client to make a change without fear of interaction with other clients, eAPI, OpenConfig, CLI scripts, human users, etc. In order to acquire the configuration lock, a privileged user must use configure lock [ REASON ] command. Care must be taken, because if this CLI session cannot acquire the lock then an error will be issued, and the client must handle this error correctly. When the configuration...
Continue reading →

RFC 5549: IPv4 unicast NLRI with IPv6 next-hop support

Description This feature provides support for advertising IPv4 unicast Network Layer Reachability Information (NLRI) with IPv6 next-hops over IPv6 peering sessions described as the Extended Next Hop Encoding capability in RFC5549. Extended Next Hop Encoding capability can be supported for IPv4 unicast, IPv4 Labeled Unicast, and IPv4 VPN address and sub-address families (1/1, 1/4, 1/128 respectively). The feature enables: Negotiating Extended Next Hop Encoding capability for IPv4 unicast NLRI advertisements over IPv6 BGP sessions. In multi-agent mode IPv4 iBGP sessions are also supported. Encoding of the next-hop in the UPDATE message that allows determination of the next-hop’s address family. This...
Continue reading →

Route Map Debugging CLI 

Description This document describes a new CLI command to help debug how and why route maps permit and deny paths. The aim of this CLI command is for the user to debug a route map by specifying as input a prefix for which BGP has reachability for, either via a BGP peer or a redistribe source. The path information for this prefix is then used in the evaluation of a route map. The route map can be specified by the user, but if none is specified the route map applied to the peer is used. Any route map configured can...
Continue reading →

Tunnel Preferences and Related Enhancements

Description Configuring the IGP cost for tunnels is a feature that allows influencing the BGP best path selection for routes resolving over MPLS tunnels. It works by overriding the existing preference (which is inherited from the underlying IGP) with the user defined preference. Platform compatibility This feature is supported on all Arista devices. Configuration Tunnel preferences can be statically configured by going under the tunnel-ribs mode, selecting the tunnel rib (system or custom) and setting it for a specific protocol. bgprtr1(config)#tunnel-ribs bgprtr1(config-tunnel-ribs)#tunnel-rib custom2 bgprtr1(config-tunnel-rib-custom2)#source-protocol ldp igp-cost preference 20 Show Commands If IGP preferences for tunnels are configured, ‘show running config’...
Continue reading →

OSPFv2 Multiple Instances Support

Description EOS 4.22.1F added support for multiple OSPFv2 instances to be configured in the default VRF.  This feature provides isolation and allows segregating/dividing the link state database based on interface.  Basic OSPFv2 functionality along with redistribution of OSPFv2 routes (all instances) into BGP and default information originate always is available since 4.22.1F release. Support for graceful restart and BFD with multiple OSPFv2 instances is added in 4.23.1 release. Platform compatibility This feature is supported on all platforms. Configuration The existing OSPFv2 configuration commands remain unchanged and are used for configuring multiple OSPFv2 instances. Each OSPFv2 instance in the default VRF...
Continue reading →

Mirroring to Multiple Destinations

Description This feature adds support for allowing multiple destinations in a single monitor session. Reference TOI for support of advanced mirroring features is available here. Platform compatibility DCS-7280SE, DCS-7500E, DCS-7280R, DCS-7280R2, DCS-7500R, and DCS-7500R2 (as of EOS-4.22.1F) DCS-7280R3 and DCS-7800R3 (as of EOS-4.23.1F) Configuration The following section describes how to configure a monitor session with multiple destinations. lf121(config)#monitor session s1 source ethernet 7 lf121(config)#monitor session s1 destination ethernet 23,24,25 lf121(config)#show monitor session Session s1 ------------------------ Source Ports: Both: Et7 Destination Ports: Et23 : active Et24 : active Et25 : active lf121(config)#monitor session s1 destination ethernet 26 lf121(config)#monitor session s1 destination...
Continue reading →

High Availability for DCI solution on CVX Cluster

Description This solution builds upon the feature developed in previous releases for federating multiple instances of VCS running on CVX node using  BGP-EVPN. However one of the limitations of the DCI solution was that it did not support high availability in the CVX cluster. In case of failure of the leader node in the CVX cluster, the VTEPs would observe a traffic loss.  The high availability for DCI addresses this problem and ensures that there is no traffic loss observed by VTEPs in case of leader failure in CVX cluster. The CVX cluster is composed of an odd number of...
Continue reading →

DHCP Server on EOS

Description Support for DHCPv4 (RFC 2131)  and DHCPv6 Server (RFC 8415) was added to EOS-4.22.1 and EOS-4.23.0 respectively. The feature is based on ISC Kea. The router with DHCP Server enabled acts as a server that allocates and delivers network addresses with desired configuration parameters to its hosts.  Supported DHCP Server Features Since EOS-4.22.1: DHCPv4 support Configurable on different interfaces: Routed, Vlan, LAG, Sub-interface, and LAG Sub-interface. Configurable lease time for allocated network addresses. Configurable DNS domain. Configurable DNS servers. Configurable subnets with parameters: Default gateway. DNS servers. Ranges. Lease time. Since EOS-4.23.0: DHCPv6 support for all features in EOS-4.22.1...
Continue reading →

MSDP support for multi-agent model

Description The Multicast Source Discovery Protocol (MSDP) provides a mechanism to connect together multiple PIM Sparse-Mode (PIM-SM) domains. Through peering relationships with MSDP-speaking routers in other PIM-SM domains, an MSDP speaker can learn of multicast sources in these domains, and interested receivers in its own can then be delivered multicast data from these over an inter-domain distribution tree. Existing support is in place for MSDP with the ribd routing protocol model. EOS-4.22.1F introduces support for MSDP with the multi-agent routing protocol model. Platform compatibility This feature is platform-independent. SA Messages and RPF-Peer Selection In both the ribd and multi-agent models,...
Continue reading →

Arista Macro Segmentation Service (MSS) integration with Check Point Software Technologies Firewalls

Description This document explains how to configure and deploy Arista MSS with Check Point Software Technologies firewalls (henceforth will be referenced as just Check Point). The feature requires the use of Check Point Management Server (Gaia), a security management platform by Check Point, which allows central management of Check Point gateway security devices. Platform Compatibility The feature has been tested with the following Management Server and Gateway versions: Management Server Versions Version R80.30 with API version 1.5 (and above). In addition to this Management Server version, Check Point is provided a “hot fix” that provides a “Proxy API” ability which...
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 →

ECMP Load Balance Profile Support

Description As of 4.22.1F Load Balance Profiles can be used to explicitly configure ECMP Load Balance parameters. In addition, users can choose from up to 8 hash polynomials instead of the usual 3 for ECMP and LAG (see Limitations). Platform compatibility DCS-7280E DCS-7280R DCS-7280R2 DCS-7280R3 DCS-7020R DCS-7500E DCS-7500R DCS-7500R2 DCS-7500R3 DCS-7800R3 Configuration Load Balance Profile mode This feature extends existing Load Balance Profiles configuration (see https://eos.arista.com/eos-4-15-0f/lag-hashing/ for more information on how to configure load-balance profiles). The user can choose to modify the default profile or create a custom one.  To enter the profile mode issue the following commands. Arista(config)#load-balance policies...
Continue reading →

Follow

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

Join other followers: