Tag :: TOI

Multi-link Operation (MLO) is the capability of the client and the AP to connect to more than one band simultaneously, thereby establishing multiple links. The clients that can connect to the Access Point over multiple radio links simultaneously are called Multi-Link Devices (MLD).

DMF version 8.8.0 introduces a redesigned workflow for Interface Groups in the DMF UI. An interface group is a collection of one or more filter or delivery interfaces, making it more convenient to create a policy. Users won't need to specify each individual interface to which the policy will apply.

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

An introduction to Nexthop-groups can be seen in the Nexthop-Group section of EOS. With this feature, IP packets matching a static Nexthop-Group route can be encapsulated with a GRE tunnel and forwarded.

NIM-1QC is a single port OCP 3.0 standard NIM card manufactured by Intel. The AWE-7230R-4TX-4S-F, AWE-5310-F, and AWE-7250R-16S-F, AWE-5510-F devices have 2 and 4 NIM (Network Interface Module) slots respectively. These devices now support NIM-1QC cards.

NIM-4S is a 4 port OCP 3.0 standard NIM card manufactured by Intel. The AWE-7230R-4TX-4S-F, AWE-5310-F, and AWE-7250R-16S-F, AWE-5510-F devices have 2 and 4 NIM (Network Interface Module) slots respectively. These devices now support NIM-4S cards.

Support for matching of DSCP,ECN,VLAN is available under the QOS class-map configuration on Arista switches.

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

EOS 4.35.0F introduces support for Network Time Security (NTS), as defined in RFC8915. NTS provides modern cryptographic security for the client-server mode of the Network Time Protocol (NTP). It separates key establishment from time synchronization by using a TLS-based NTS Key Establishment (NTS-KE) protocol to negotiate symmetric keys and encrypted cookies. These cookies are included in subsequent NTP packets to enable stateless authentication by the server. NTS ensures that time synchronization data is received from a legitimate source and has not been modified in transit.

The Nutanix Prism Central vendor integration enables the DANZ Monitoring Fabric (DMF) to fetch the inventory of the infrastructure and resources managed through Prism Central. This inventory includes information on entities such as virtual machines, virtual NICs, and hosts. The integration also helps to monitor virtual machines by creating network monitoring policies based on virtual machine names.

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.

If a gNMI.Set union_replace operation or gNOI.BootConfig RPC is issued without this configuration, an error is returned to the client.This feature adds support for the following to OpenConfig: gNMI.Set union_replace operation

This feature adds streaming support for the IS-IS Link State Database OpenConfig model via gNMI. The current implementation supports a limited number of IS-IS TLVs and subTLVs.

Priority-flow-control (PFC) buffer and history counters provide information on both present PFC pause conditions and past pause events. These buffer counters (since EOS-4.34.2F) and history counters (since EOS-4.35.0F) are available via OpenConfig in addition to the show commands that have existed in previous versions.

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.

Customers currently leverage the event-handler for automated remediation such as auto-drain of nodes during specific triggers (blackholing scenarios, hardware failures). However, there are scenarios where the automation becomes counterproductive or risky during active incidents or anomalies.

By default, when an SVI is configured on a VXLAN VLAN, then broadcast, unknown unicast, and unknown multicast (BUM) traffic received from the tunnel are copied to CPU. However, sending unknown unicast and unknown multicast traffic to CPU is unnecessary and could have negative side effects. Specifically, these packets take the L2Broadcast CoPP queue to the CPU. When there is a lot of unknown unicast and unknown multicast traffic, important broadcast traffic such as ARP may get dropped in the L2Broadcast CoPP queue. Further, this might also disrupt other control plane protocols such as BFD, BGP, etc.

IPv4 routes of certain prefix lengths can be optimized for enhanced route scale using this feature. This feature is ideally suited to achieve route scale when route distribution has a large number of routes concentrated across the prefix-lengths 24, 23 and 22. EOS 4.27.2F offers 8-to-1 compression of routes as an enhancement.

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 provides isolation and allows segregating/dividing the link state database based on interface. 

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

OSPFv3 distribute-list is a policy construct to filter out routes received from OSPFv3 LSAs so that they will not be installed on the router even though the routes are resolved and are installable. The filtering is performed after SPF calculation and only on routes from received LSAs, not on self-originated LSAs. This feature does not affect the OSPFv3 protocol behavior of the router. LSAs are exchanged, e.g. flooded, even if the routes are not installed locally on the router.

EOS release 4.20.1F adds OSPFv3 flood pacing support that allows configuring the minimum interval between the

In previous releases of EOS, Stub area and NSSA area types were supported for OSPFv3, but without support of the "no