Arista Portal

  • Tag : multi-agent

 
 

Route Map – Match Resolved Nexthop Support in Multi-Agent

Posted on August 20, 2020 by   |   38 Views

Description This feature adds support for ‘match ip(v6) resolved-next-hop’ clause under route-map config for BGP policy application in multi-agent model. This feature may be used when a policy to filter routes on the basis of the resolved nexthop of a route is desired. A route map can be used at various application points to filter routes based on the policy but ‘match ip(v6) resolved-next-hop’ is supported only for specific application points. For such applications when a route map with ‘match ip(v6) resolved-next-hop’ clause is applied, the ip address of the resolved nexthop of each route is matched against the ip-prefixes...
Continue reading →

BGP UCMP

Posted on June 22, 2020 by   |   134 Views

Description This feature adds support for BGP UCMP in the multi-agent routing protocol model. The TOI for BGP UCMP in the ribd routing protocol model can be found here. Unequal Cost Multi Path (UCMP) for BGP is a mechanism for forwarding traffic from a device for an ECMP route in the ratio of the weights with which the next hops of that route are programmed in the FIB. This is done for BGP by disseminating BGP link bandwidth extended community attribute information with BGP paths such that the receiver device of all such paths for a route programs next hops...
Continue reading →

Routing control functions

Posted on June 18, 2020 by   |   322 Views

Description Routing control functions (RCF) is a new language that can be used to express BGP route filtering and attribute modification logic in a powerful and programmatic fashion. It supports a new set of workflows to define and apply these functions in EOS. The broader feature set includes: the base RCF language framework support for RCF function application to BGP neighbors support for matching and modifying BGP protocol attributes workflows to define and apply routing control functions CLI commands to provide visibility into operational status As of EOS-4.24.2F release, the following points of application are supported: Point of application Supported...
Continue reading →

Support for showing last update timestamp in show rib route 

Posted on June 10, 2020 by   |   45 Views

Description The CLI command “show rib route ip[ipv6]” and its sub-commands (e.g. “show rib route ip bgp”) displays information on routes present in the Routing Information Base table for each of the provided routing protocol (e.g. Bgp, OSPF, ISIS, etc.). Additionally to the existing information, the command will now also display the time since a route was last updated in the routing table when in multi-agent mode. This additional information would allow a network operator to check if and when a route was updated in the routing table to correlate possible network issues caused by routing updates (e.g. traffic now...
Continue reading →

Redistribution of leaked routes into IGPs

Posted on June 3, 2020 by   |   103 Views

Description VRF Route leaking can be used when routes from one VRF are required in another VRF (e.g. in case of shared services). If VrfLeak Agent is being used to leak routes, the leaked routes (in destination VRF) can be redistributed into IGPs. This feature adds support for the following: Redistribution of leaked static, connected, Ospf, and IS-IS routes into Ospf Redistribution of leaked static, connected, and Ospf routes into IS-IS Platform compatibility Redistribution of leaked routes is supported on all EOS devices, but only with the routing system in multi-agent mode. Configuration Redistribution of leaked routes into OSPF Redistribution...
Continue reading →

Setting metric on static routes and Eos SDK support

Posted on June 3, 2020 by   |   47 Views

Description This feature introduces a metric for static routes so that the user can configure both administrative distance and metric for a static route. Administrative distance precedes metric when comparing configured routes. Lower metric route will win among routes with the same administrative distance. Winning routes will be programmed to hardware and shown in “show ip route”. It can be configured by CLI or through EosSdk. One use case of static route metric is to impact BGP best path selection. Route Arbitration case 1 — route with lower admin distance wins ip route 10.0.0.0/8 192.168.1.1 10 metric 100   (win)...
Continue reading →

Simultaneous negotiation of IPv6 unicast and 6PE capabilities in BGP

Posted on May 14, 2020 by   |   48 Views

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 →

Support to Restrict the Number of Bgp Ecmp Next Hops in Multi-Agent Protocol Model

Posted on April 21, 2020 by   |   131 Views

Description In the ribd routing protocol model, the “maximum-paths … ecmp …” command allows restricting the number of BGP paths and the number of vias in the ECMP FEC respectively. In the multi-agent protocol model, a “maximum-paths” value of greater than 1 enabled the formation of ECMP. However, the number of BGP paths or the number of vias in the FEC were not constrained by the configured value. With the 4.24.0F EOS release, the multi-agent protocol model supports restricting the number of BGP paths and ECMP FEC size based on the BGP configuration. Platform Compatibility Supported on all platforms. Configuration...
Continue reading →

Redistribution of leaked routes into IGPs

Posted on April 16, 2020 by   |   97 Views

Description When there are multiple VRFs on the device and there is a need to share routes between them, typically for shared services, such routes are called leaked routes. For more info on inter VRF route leaking, please refer to the article in Resources section. Once leaking is done in the destination VRF, these leaked routes can be redistributed into IGPs.  This feature adds support for the following: Redistribution of leaked static, connected, Ospf, and IS-IS routes into Ospf Redistribution of leaked static, connected, and Ospf routes into IS-IS Platform compatibility Redistribution of leaked routes is supported on all EOS...
Continue reading →

Configurations and Optimizations for Internet Edge Routing

Posted on April 14, 2020 by   |   1356 Views

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 →

BGP IPv6 Link Local Peers Discovery

Posted on March 18, 2020 by   |   136 Views

Description This feature adds support for a dynamic configuration model to eliminate the need for the network administrator to assign and configure IPv6 addresses for BGP peering. We leverage the following details to automatically establish BGP adjacency: IPv6 link local addresses can be, and typically are, automatically generated by the system based on MAC addresses. IPv6 router advertisements can be used to communicate these addresses among potential BGP peers. Since this feature uses IPv6 router advertisement to discover the peer’s IPv6 link local address, devices are required to have IPv6 routing enabled, and the interface used for peering should have...
Continue reading →

Route Map – Match Interface Support in Multi-Agent

Posted on March 12, 2020 by   |   95 Views

Description This feature adds support for ‘match interface’ clause under route-map config for Bgp policy application in multi-agent model. This feature may be used when a policy to filter routes on the basis of the resolved interface of a route is desired. A route-map can be used at various application points to filter routes based on the policy but ‘match interface’ is supported  only for specific application points. For such applications when a route-map with ‘match interface’ clause is applied, the interface of the resolved nexthop of each route is matched against the interface specified in route-map and the route...
Continue reading →

BGP sFlow export in multi-agent mode

Posted on March 12, 2020 by   |   109 Views

Description Sflow samples can be augmented with additional Extended gateway data by getting data from BGP in addition to sFlow’s standard IP information. The additional BGP information can be seen in sFlow Version 5 doc under extended_gateway. Extended gateway data was already supported in gated mode. Now it is being supported for multi-agent mode (arBGP). Starting in EOS 4.22.1F v6 non-default vrf traffic is supported Starting in EOS 4.23.2F ECMP traffic is supported Platform compatibility This feature is supported on all platforms. Configuration A BGP instance must be configured on the switch for BGP sFlow export to operate. rtr1(config)#sflow run...
Continue reading →

BGP logical OR of multiple community lists in the same match command

Posted on December 23, 2019 by   |   120 Views

Description In the multi-agent routing protocol model, the Bgp agent now supports matching community lists with a logical OR via the route map “match community or-results <community-list-1> <community-list-2>” command (same applies for extended and large communities with “match extcommunity” and “match large-community”). Without this new “or-results”, the default is to compute the logical AND of all provided community lists. Before this new feature one would need to merge existing community lists into one to do a logical OR: Issue: ip community-list COMMLIST1 permit 1:1 ip community-list COMMLIST2 permit 2:2 ! No way to match "COMMLIST1" or "COMMLIST2" in a singe...
Continue reading →

EVPN VxLAN IPV6 Overlay

Posted on December 20, 2019 by   |   388 Views

Description Starting with EOS release 4.22.0F, the EVPN VXLAN L3 Gateway using EVPN IRB supports routing traffic from one IPV6 host to another IPV6 host on a stretched VXLAN VLAN. This TOI explains the EOS configuration and show commands. Platform Compatibility Platform supporting ND Proxy and ND Suppression DCS-7280R/7280R2 DCS-7050CX3-32S-F DCS-7050SX3-48YC12-F (Starting in 4.22.1F) DCS-7050SX3-48YC8 (Starting in 4.22.1F) DCS-7050/7050X/7050X2 (Starting in 4.22.1F) DCS-7260X/7260X3 (Starting in 4.22.1F) DCS-7060X/7060X2 (Starting in 4.21.1F) DCS-7250 (Starting in 4.22.1F) DCS-7300/DCS-7320 (Starting in 4.22.1F) Platform not supporting ND Proxy, No ND Suppression  DCS-7020R DCS-7160 DCS-7500R/7500R2/7500E Configuration Enable IPv6 Routing Enable global IPv6 unicast routing and IPv6...
Continue reading →

Static inter-VRF route support

Posted on December 19, 2019 by   |   252 Views

Description This feature adds support for static inter-VRF routes. This enables configuration of routes to destinations in one ingress VRF with an ability to specify a next-hop in a different egress VRF through a static configuration. Such static inter-VRF routes can be configured in default and non-default VRFs. A different egress VRF is achieved by “tagging” the “next-hop” or “forwarding via” with a reference to an egress VRF (different from the source VRF) in which that next-hop should be evaluated. Static inter-VRF routes with ECMP next-hop sets in the same egress VRF or heterogenous egress VRFs can be specified This...
Continue reading →

EVPN VxLAN IPV6 Overlay TOI

Posted on November 14, 2019 by   |   266 Views

Description Starting with EOS release 4.22.0F, the EVPN VXLAN L3 Gateway using EVPN IRB supports routing traffic from IPV6 host to another IPV6 host on a stretched Vxlan VLAN. This TOI explains the EOS configuration and show commands. Platform Compatibility Platform supporting ND Proxy and ND Suppression DCS-7280R/7280R2 DCS-7050CX3-32S-F DCS-7050SX3-48YC12-F ( Starting in 4.22.1F ) DCS-7050SX3-48YC8 ( Starting in 4.22.1F ) DCS-7050/7050X/7050X2 ( Starting in 4.22.1F ) DCS-7260X/7260X3 ( Starting in 4.22.1F ) DCS-7060X/7060X2 ( Starting in 4.21.1F ) DCS-7250 ( Starting in 4.22.1F ) DCS-7300/DCS-7320 ( Starting in 4.22.1F ) Platform not supporting ND Proxy, No ND Suppression  DCS-7020R...
Continue reading →

MSDP support for multi-agent model

Posted on November 12, 2019 by   |   85 Views

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 →

Support for UCMP “adjust auto” (multi-agent)

Posted on November 12, 2019 by   |   133 Views

Description Unequal-cost multi-path (UCMP) for BGP is a mechanism for forwarding ECMP route traffic using weights, with which the next hops of those routes are programmed in the FIB. This is done using BGP by disseminating BGP link-bandwidth extended community attribute information with BGP routes, such that the receiver device of all routes programs the next hops in the FIB using the received link-bandwidth values. This feature appends the percentage of interface speed with a route’s received link bandwidth extended community value. The idea is to rebalance the weight ratio of the traffic sent over egress ports, such that we...
Continue reading →

BGP shutdown and reset communication (multi-agent)

Posted on November 12, 2019 by   |   121 Views

Description This feature implements support for RFC8203/BIS so that users can attach the reason of BGP instance or peer session administrative shutdown or hard reset to the BGP Cease Notification sent to the peers. Platform compatibility This feature is platform independent and only available when multi-agent mode is enabled. Configuration Below is a list of all possible configurations under this feature: (config-router-bgp)# shutdown [reason REASON] (config-router-bgp)# neighbor ( addr | peer-group) shutdown [reason REASON] (config-router-bgp)# clear [ip | ipv6] bgp [(neighbor (addr | peer-group)) | * ] [vrf (all | default | VRFNAME)] [reason REASON] Note that attaching ‘reason REASON’...
Continue reading →

« Older posts
Follow

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

Join other followers: