Tag :: EOS 4.29.1F

The L2 EVPN MPLS feature is available when configuring BGP in the multi-agent routing protocol model. Ethernet VPN (EVPN) is an extension of the BGP protocol introducing a new address family: L2VPN (address family number 25) / EVPN (subsequent address family number 70). It is used to exchange overlay MAC and IP address reachability information between BGP peers.

Filtered Mirroring allows certain packets to be selected for mirroring, rather than all packets ingressing or egressing a particular port.

Hold Time is a field in OPEN BGP Message. If a BGP speaker doesn’t receive any keepalive or update messages from the other side for the duration of the hold time then it will declare the other side ‘dead’ and it will tear down the BGP session.

This feature monitors the BGP session status. When a BGP session goes down, traffic originally forwarded to the next hops learned from the downed BGP peer is quickly diverted to a backup path if any, or in the case of ECMP, remaining ECMP members.

Network Address Translation (NAT) is a feature used to obfuscate private internal addresses to the external world. The feature makes sure that private internal addresses are translated into a publicly visible address which is used by all external hosts and it also does the reverse translation of the public address to the private internal address.

As Ethernet technologies made their way into the Metropolitan Area Networks (MAN) and the Wide Area Networks (WAN), from the conventional enterprise level usage, they are now widely being used by service providers to provide end-to-end connectivity to customers. Such service provider networks are typically spread across large geographical areas. Additionally, the service providers themselves may be relying on certain internet backbone providers, referred to as “operators”, to provide connectivity in case the geographical area to be covered is too huge. This mode of operation makes the task of Operations, Administration and Maintenance (OAM) of such networks to be far more challenging, and the ability of service providers to respond to such network faults swiftly directly impacts their competitiveness.

This feature introduces the show bgp evpn sanity ( brief | detail )command. This command displays which EVPN configuration attributes are inconsistent as well as potential errors in the EVPN operational state.

EOS currently supports EVPN Multicast by setting up PIM tunnels in the underlay with VXLAN as the transport. While this is an efficient delivery mechanism, it requires PIM to be deployed in the underlay. In certain cases, the overheads of provisioning/maintaining the multicast routers and the multicast routing state in the underlay may be significant. To support such scenarios, Ingress Replication (IR) or Head-End Replication (HER) can be used in the underlay to distribute overlay multicast traffic.

Multihoming in EVPN allows a single customer edge (CE) to connect to multiple provider edges (PE or tunnel endpoint).

Ethernet VPN (EVPN) networks normally require some measure of redundancy to reduce or eliminate the impact of outages and maintenance. RFC7432 describes four types of route to be exchanged through EVPN, with a built-in multihoming mechanism for redundancy. Prior to EOS 4.22.0F, MLAG was available as a redundancy option for EVPN with VXLAN, but not multihoming. EVPN multihoming is a multi-vendor standards-based redundancy solution that does not require a dedicated peer link and allows for more flexible configurations than MLAG, supporting peering on a per interface level rather than a per device level. It also supports a mass withdrawal mechanism to minimize traffic loss when a link goes down.

The FEC (Forward Error Correction) traffic analyzer is designed to estimate the performance of the FEC layer, identify error statistics, and the source of correlated errors on physical interfaces.

Forwarding destination prediction enables visibility into how a packet is forwarded through the switch, allowing you to determine which interfaces a packet would egress out of. Typical use cases include, but are not limited to, determining egress members for Port-Channels and ECMPs.

Prior to release EOS 4.29.1, a statically configured BGP neighbor, listen range or interface peer could reference a single peer group for inheriting configuration parameters. EOS 4.29.1 adds the ability for that peer group to inherit configuration from up to 8 additional “ancestor” peer groups. The term “leaf peer group” is given to the peer group which is directly referenced by the BGP neighbor, listen range or interface peer.

This feature optimizes the utilization of hardware resources by sharing the hardware resources between different VLAN interfaces when they have the same ACL attached in the ingress direction. This is particularly useful for larger deployments where the ACL is applied to multiple VLANs and with the RACL sharing capability, lesser hardware resources are used irrespective of the number of VLANs

sFlow is a sampling technique which monitors the incoming traffic on all the interfaces without affecting the network performance.

Several customers have expressed interest in using IPv6 addresses for VXLAN underlay in their Data Centers (DC). Prior to 4.24.1F, EOS only supported IPv4 addresses for VXLAN underlay, i.e., VTEPs were reachable via IPv4 addresses only.

ISIS Leaked Route Summarization is a feature which summarizes all the L1 leaked routes in L2 routers. With the help of this L2 LSP size reduces (smaller no of routes in L2 LSP). 

Segment Routing provides mechanism to define end-to-end paths within a topology by encoding paths as sequences of sub-paths or instructions. These sub-paths or instructions are referred to as “segments”. IS-IS Segment Routing (henceforth referred to as IS-IS SR) provides means to advertise such segments through IS-IS protocol.

This feature will allow the user to select whether port mirror destinations of type GRE tunnel include the optional “key” field in the GRE header on certain platforms. The key field allows the user to uniquely identify a particular packet flow. The feature also allows the user to specify the value of the 32 bit key field.

Normally, a switch traps L2 protocol frames to the CPU. However, certain use-cases may require these frames to be forwarded or dropped. And in cases where the L2 protocol frames are forwarded (eg: Pseudowire), we may require the frames to be trapped to the CPU or dropped. The L2 Protocol Forwarding feature provides a mechanism to control the behavior of L2 protocol frames received on a port or subinterface.

4.29.1F adds Latency Analyzer (LANZ) support to the Arista SwitchApp on 7130 series. LANZ monitors SwitchApp internal buffer congestion. When the number of bytes in a buffer is over a high threshold, a congestion start event is created. When the number of bytes in a buffer is below a low threshold, a congestion end event occurs. LANZ on SwitchApp does not report any congestion update as the buffer sizes are too small for it to be meaningful. As SwitchApp comes in different profiles, each profile has a different hardware behavior due to the underlying architectural difference.

Loop protection is a loop detection and prevention method which is independent of Spanning Tree Protocol (STP) and is not disabled when the switch is in switchport backup mode or port is in discarding state. The LoopProtect agent has a method to detect loops and take action based on the configuration by the user. In order to find loops in the system, a loop detection frame is sent out periodically on each interface that loop protection is enabled on. The frame carries broadcast destination MAC address, bridge MAC source address, OUI Extended EtherType 0x88b7 as well as information to specify the origins of the packet.

Media Access Control Security (MACsec) is an industry standard encryption mechanism that protects all traffic

MetaWatch is an FPGA-based feature available for Arista 7130 Series platforms. It provides precise timestamping of packets, aggregation and deep buffering for Ethernet links. Timestamp information and other metadata such as device and port identifiers are appended to the end of the packet as a trailer.

Mirroring to a GRE tunnel allows mirrored packets to transit to a L3 network using GRE encapsulation.

For packets received on the front-panel interfaces and delivered to the CPU interface, this feature allows creation of a profile to configure buffer reservations for the egress CPU queues in the MMU (MMU = Memory Management Unit which manages how the on-chip packet buffers are organized).

MRU (maximum receive unit) enforcement provides the ability to drop frames that exceed a configured threshold on the ingress interface.

Multicast EVPN IRB solution allows for the delivery of customer BUM (Broadcast, Unknown unicast and Multicast) traffic in L3VPNs using multicast in the underlay network. This document contains only partial information that is new or different for the Multicast EVPN Multiple Underlay Groups solution.

Before 4.29.0F, the next hop self option could only be configured for a neighbor in global router mode and would apply to all address families. Attempting to configure next-hop-self in address family mode would silently move the configuration to global mode (for the specified neighbor).

The nexthop group feature allows users to manually configure a set of tunnels. Nexthop group counters provide the ability to count packets and bytes associated with each tunnel nexthop, irrespective of the number of times it appears in one or more nexthop groups. In other words, if a nexthop group entry shares a tunnel resource with another entry, they will also share the same counter.

This feature adds streaming support for the BGP RIB OpenConfig model via gNMI. The current implementation supports streaming of locRib for IPv4 and IPv6 unicast address families.

This article is intended to discuss how to configure the Phone VLAN on an Arista switch.

This document describes a new CLI command to help debug how and why policy permits and denies paths. The aim of this CLI command is for the user to debug a route map or RCF (Routing Control Functions) function by specifying as input a prefix for which BGP has reachability for, either via a BGP peer or a redistribute source.

This feature is a CLI show command which displays the history of system power consumption after the system boots up.

This feature is used to save power by turning off front panel LEDs when they are not needed. After this feature is enabled, LEDs will be turned off after 1 hour from the time of system boots up or feature enabled. Transceiver insertion/removal or USB insertion will cause the LEDs to turn on for 1 hour.

PTP 1-step Boundary Clock (or 1-step BC) is similar to 2-step BC in function but doesn’t send the PTP Follow_Up message. The timestamp present in the PTP Follow_Up message’s preciseOriginTimestamp field is sent in the PTP Sync message’s originTimestamp field along with a non-zero correctionField. This allows us to support more PTP master ports because the control plane does not need to generate PTP Follow_Up messages anymore. PTP 1-step BC supports all the existing features supported by 2-step BC like G8275.1 profile, G8275.2 profile, etc unless otherwise specified in the limitations.

RADIUS over TLS provides secure and reliable transport for RADIUS clients. RADIUS over TLS allows RADIUS

The SFP-10G-RA-1G-LX and SFP-10G-RA-1G-SX transceivers are rate adapting SFP+ transceivers with internal clause 37 auto-negotiation (AN) support. The transceiver host interface is 10G XFI and the module rate adapts in the egress direction from 10G to 1G before transmitting data on the attached fiber. In the ingress direction it rate adapts the received 1G data to 10G before sending to the host switch. This allows 1000BASE-LX and 1000BASE-SX support on switches which do not natively support 1G operation.

Routing Control Functions (RCF) is a language that can express route filtering and attribute modification logic in a powerful and programmatic fashion.The document covers: Configurations of a RCF function for BGP points of application

Routing Control Functions (RCF) is a language that can be used to express route filtering and attribute modification logic in a powerful and programmatic fashion.

Routing control functions (RCF) is a language that can be used to express route filtering and attribute modification logic in a powerful and programmatic fashion.

Routing control functions (RCF) is a language that can be used to express route filtering and attribute modification logic in a powerful and programmatic fashion. 

SR P2MP ( Segment Routing Point to Multipoint ) is a protocol that can be used to steer multicast traffic across a network. This provides a better way to instantiate MVPN Provider tunnel in service provider network over traditional way of using RSVP P2MP.

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.

The feature allows egress sFlow sampling to be enabled per a subinterface. The egress sFlow sampling per a subinterface configuration will only have effect when egress sFlow sampling is disabled on the parent interface as egress sFlow sampling on the parent interface includes traffic on all subinterfaces.

This document describes the prefix counter feature and is intended for customers who are familiar with and are using VRF selection policies (see linked TOI for details). In short, the prefix counter feature enables traffic matching a VRF selection policy to be counted on a per-prefix/per-route basis. This is limited to IPv4 traffic and prefixes of length 32.

Private VLAN is a feature that segregates a regular VLAN broadcast domain while maintaining all ports in the same IP subnet. There are three types of VLAN within a private VLAN

A fundamental business requirement for any network operator is to reduce costs where possible. For network operators, deploying devices to many locations can be a significant cost as sending trained specialists to each site for installations is both time-consuming and expensive.

A L2 sub-interface is a logical bridging endpoint associated with traffic on an interface distinguished by 802.1Q tags, where each <interface, 802.1Q tag> tuple is treated as a first-class bridging interface. 

This feature enables Tap Aggregation generic header removal on a tap port.