Tag :: TOI

EOS supported two routing protocol implementations: multi-agent and ribd. The ribd routing protocol model is removed starting from the EOS-4.32.0F release. Multi-agent will be the only routing protocol model. Both models largely work the same way though there are subtle differences.

This feature provides the ability to interconnect EVPN VXLAN domains. Domains may or may not be within the same data center network, and the decision to stretch/interconnect a subnet between domains is configurable. The following diagram shows a multi-domain deployment using symmetric IRB. Note that two domains are shown for simplicity, but this solution supports any number of domains.

Multi hop BFD  allows for liveness detection between systems whose path may consist of multiple hops. With an

Until now, a multi-band client (for example, a phone with 2.4, 5, and 6 GHz radios) could connect to an AP using only one of the bands. Therefore, only one connection link formed between the client and the AP. Multi-link Operation (MLO) is the capability of the client and the AP to connect to more than one band simultaneously establishing multiple links. The clients that are capable of communicating with each other over multiple radio links at the same time are called Multi-Link Devices (MLD).

This feature adds the support for OSPFv3 multi-site domains (currently this feature is added for IPv6 address family only) described in RFC6565 (OSPFv3 as a Provider to Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs) ) and enables routes BGP VPN routes to retain their original route type if they are in the same OSPFv3 domain. Two sites are considered to be in the same OSPFv3 domain if it is intended that routes from one site to the other be considered intra-network routes.

MultiAccess is an FPGA-based feature available on certain Arista 7130 platforms. It performs low-latency Ethernet multiplexing with optional packet contention queuing, storm control, VLAN tunneling, and packet access control. The interface to interface latency is a function of the selected MultiAccess profile, front panel interfaces, MultiAccess interfaces, configuration settings, and platform being used.

This solution allows delivery of multicast traffic in an IP-VRF using multicast in the underlay network. It builds on top of L2-EVPN, adding support for L3 VPNs and Integrated Routing and Bridging (IRB). The protocol used to build multicast trees in the underlay network is PIM Sparse Mode.

Multicast Only Fast Reroute (MoFRR) is a feature based on PIM sparse mode (PIM SM) protocol to minimize packet loss in a

LANZ adds support for monitoring congestion on backplane (or fabric) ports on DCS 7304, DCS 7308, DCS 7316, DCS

In Tap Aggregation mode, an interface can be configured as tap or tool port. Tap ports are used to 'tap' the traffic and

Multiple VLAN Registration Protocol (MVRP) is a Layer 2 protocol. The protocol allows access points to propagate the VLAN created on CV-CUE to the connected Switches. The real-time propagation of configuration allows you the flexibility of configuring your wired and wireless network in one interface and distributing it to other active interfaces. You do not have to worry about managing and maintaining the configurations in all interfaces.

The NAT Application Gateway (ALG) feature allows FTP connections between client server to be translated using

NAT Peer State Synchronization feature provides redundancy and resiliency for Dynamic NAT across a pair of devices in an attempt to mitigate the risk of single NAT device failure. Each switch advertises connection state updates to its peer.  State update consists of connection creation, connection state change (TCP mostly) or connection tear down

Non default VRF support is now available for Static unicast NAT. Twice NAT. Dynamic NAT. VRF support

While preserving the information from the previous version, the updated DMF Interfaces UI introduces a new layout, design, and enhanced functionalities for improved interface viewing and monitoring for easy troubleshooting.

The new Switches page provides a modernized overview of all switches configured in DMF. A header and tabulated layout allow observation of different aspects of installed switches and provisioning new switches while on the same dashboard.

CloudVision Cognitive Unified Edge (CV-CUE) 18.0 introduces the following new features and enhanced functionalities:

CloudVision Cognitive Unified Edge (CV-CUE) 19.0 introduces the following new features and enhanced functionalities:

DMF 8.7.0 introduces a redesigned Recorder Node configuration workflow, monitoring page, and query workflow. 

In the 13.0 release, CloudVision Cognitive Unified Edge (CV-CUE) adds a new report and also includes some enhancements to existing reports.

Nexthop Group backup-activation events are produced by forwarding agents. Nexthop Groups supports configuring the backup paths through EOS RPC APIs and CLI. Whenever the route or prefix starts pointing to configured backup paths, a backup-activation event will be logged into the event-monitor DB with nexthop-group name, accurate timestamp and other attributes. The event monitoring feature also supports filtering the events based on the nexthop-group name, version etc.

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.

Nexthop Group Event Monitoring in the RPC layer on Arista switches allows for quick and filterable viewing of Nexthop Group events, i.e., addition or deletion or callbacks associated with hardware programming of Nexthop Groups configured through the EosSdkRpc agent.

Nexthop selection using GRE key allows for nexthop routing selection based on the GRE key of a GRE encapsulated IP

Nexthop group match in PBR policy enables the user to match incoming packets being routed to a specified nexthop group

Configuration of arbitrary combinations of speeds on subinterfaces is being restricted on 800G CMIS Arista transceivers. This feature restricts configuring only uniform sets of speeds on applicable transceivers. This affects Arista-branded 800G active optical transceivers.

Vmware NSX Controllers expect Hardware VTEPs to monitor the liveness of the Replication Service Node via BFD.  In

For an octal port such as a QSFPDD or OSFP, this feature renumbers the ports on a system to have 4 configurable

In some situations, packets received by an ASIC need to be redirected to the control plane: packets that have the destination address of the router or packets that need special handling from the CPU for example. The control plane cannot handle as many packets as the ASIC. A system that protects the control plane against DOS and prioritizes packets to send to the CPU is needed.  This is accomplished by CoPP (control-plane policing). CoPP is already functioning, however, the CPU queues are statically allocated to a specific feature. If a feature is not used, the CPU queue statically allocated to the feature is not used either. This is a loss of resources.

The EOS Event Manager feature provides the ability to specify a condition and an action to be carried out when that

With the 18.0 release, you can trigger the Auto-Channel Selection (ACS) Mode and Transmit Power Control (TPC) Mode for a radio on demand. In ACS Mode, the Access Point (AP) scans the network to select the best channel. In Auto-TPC Mode, the AP automatically adjusts its transmit power to minimize interference with neighboring Arista APs.

With the 15.0.1 release, CV-CUE extends the wired configuration and monitoring capabilities. You can now onboard switches (710P, 720XP, 720DP) to CV-CUE. You can also configure switches and manage switch-related settings directly from the UI.

 . These are the release notes and configuration guide for the OpenConfig feature available in the 4.20.1F EOS

These are the release notes and configuration guide for the OpenConfig feature available in the 4.20.2.1F EOS

We now support configuration diffs to be generated and to be streamed via OpenConfig.  Please note that there are limitations to using this feature to obtain the correct configuration diff of consecutive configuration changes.  Subsequent sections will explain:

EOS supports reading and streaming various OpenConfig configuration and state models over gNMI (gRPC Network Management Interface), RESTCONF, and NETCONF transports. A subset of the configuration models may also be modified over these transports, see below.

This feature allows us to obtain system mount points information via OpenConfig.  The information that can be obtained is equivalent to the information that we view by executing the ‘df -k’ linux command.

OpenFlow 1.3 protocol is supported in EOS 4.15.0F on DCS 7050 and DCS 7050X series of switches. The switch and the

A new forwarding pipeline is being introduced in EOS 4.15.0F which allows the traffic entering the switch to be

Action TTL decrement in an OpenFlow flow. OpenFlow 1.3 Group support on DCS 7010 series. Clearing

With the 14.0 release, you can integrate OpenID Connect with a captive portal for authentication. The OpenID Connect integration functionality is available only for captive portals hosted on the Arista Cloud. It is not available if the captive portal is hosted on third-party servers or on the access point.

The OSPF Non Stop Forwarding (NSF) feature adds support for Graceful OSPF Restart (IETF RFC 3623) and Graceful OSPFv3

EOS 4.15.3F adds support for configuring auto cost in OSPFv3 for routed ethernet interfaces and LAG interfaces.

An OSPF router can attract all traffic towards itself from within the OSPF network, by advertising a default route. Often it is desirable to advertise this default route conditionally, for instance, only when there is a connection to an upstream router or when a default route is learnt through other protocols like BGP. OSPF conditional default-originate provides the above functionality.

OSPF distribute list is a policy construct to filter out routes received from OSPF LSAs so that they will not be

The OSPF Max LSA Retransmission Threshold feature adds a configurable limit to the number of LSA update

OSPF Non Stop Forwarding (NSF) adds support for Graceful OSPF Restart, IETF RFC 3623 .  With OSPF Graceful Restart

An OSPF router can attract all traffic towards itself from within the OSPF network, by advertising a default route. Often it is desirable to set a route tag in this default route. This feature will add a CLI parameter to default-information originate that allows an external route tag to be set on the default route for both unconditional and conditional modes.

This feature adds authentication support for OSPFv3. Unlike OSPFv2, OSPFv3 does not have authentication fields

EOS 4.17.0F adds support for BFD in OSPFv3. BFD provides a faster convergence in scaled deployments where using