• Tag : isis


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 →

IS-IS Purge Originator Identification

Description This feature implements support for RFC6232 that helps a user identify source of an LSP purge packet. It can be enabled on level-1 or level-2 or both. Once enabled, any purge LSP that is originated by the node will be added with a purge originator TLV which will contain its own system-id. Other nodes that receive this purge LSP will process the purge originator TLV and log the system-id of the originator. When a node that is enabled with this feature receives a purge LSP that doesn’t contain a purge originator TLV, it will add the purge originator TLV...
Continue reading →

General Router ID

Description The General Router-ID configuration provides the ability to configure a common Router-ID for all routing protocols configured on the device. This implies that you do not need to configure a Router-ID for each routing protocol individually. Platform compatibility All platforms. Configuration A general router ID can be configured under the “router general” configuration mode for each address family: rtr(config)#router general rtr(config-router-general)#router-id ipv4 <A.B.C.D> rtr(config-router-general)#router-id ipv6 <A:B:C:D:E:F:G:H> For each address family, a per-VRF general router ID can be configured under the VRF submode under the “router general” configuration mode: rtr(config-router-general)#vrf RED rtr(config-router-general-vrf-RED)#router-id ipv4 <A.B.C.D> rtr(config-router-general-vrf-RED)#router-id ipv6 <A:B:C:D:E:F:G:H> Note that to...
Continue reading →


Does Arista EOS suppport ISIS BFD? If not, then are there any plans to support it and when? Thanks, Laszlo

ISIS-SR Global Adj-SID

Introduction This feature allows user to configure adjacency SID of global scope for IS-IS adjacencies. It is an extension to IS-IS Segment Routing static adjacency SID and IS-IS Segment Routing. Global adjacency SID can be configured per address family on any interface. They are configured as index and are advertised as those. This feature is currently supported for P2P interface. Configuration Global adjacency SID can be configured on interface configuration mode with command: [no|default] adjacency-segment <ipv4|ipv6> p2p index <value> global   Arista(config-if-Et1)#adjacency-segment ipv4 p2p ? index  Index to be assigned as Adj-SID for adjacency on this interface label  Label value...
Continue reading →

ISIS between Arista and IOS-XR

Hi I’m trying to establish isis between a cisco router, IOS-XR and 7280CR running 4.20.5F adjacency won’t come up. MTU on cisco side is 9216. on Arista side, IP MTU is configured as 9202. Layer2 MTU cannot be configured on this platform. hello-padding is disabled on both ends. I have 7280SR running an earlier version that works with the same cisco with the same configs. Has anyone had such problems with isis in 4.20.5F?


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

Join other followers: