Tag :: TOI

This feature adds all-active (A-A) multihoming support on the multi-domain EVPN VXLAN-MPLS gateway. It allows L2 and L3 ECMP to form between the multihoming gateways on the TOR devices inside the site and on the gateways in the remote sites. Therefore, traffic can be load-balanced to the multi-homing gateway and redundancy and fast convergence can be achieved.

Measured boot is a tamper-detection mechanism that records a system's boot process. It calculates cryptographic hashes of system components and configurations, which are then securely stored in the Platform Configuration Registers (PCRs) of a Trusted Platform Module (TPM) chip.

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. The main motivation is that since the NAT state is shared between two switches, the failure of one switch can be tolerated since the other switch will retain the translations.

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:

CloudVision Cognitive Unified Edge (CV-CUE) 20.0 introduces the following new features and enhanced functionalities: CV-CUE introduces longer time intervals for the LED Blink operation. Prior to the 20.0 release, 5,15, and 30 minutes were the available time intervals. From this release onwards, 2,4,8,12, and 24-hour time intervals are added. The longer blink duration is useful in enterprise network deployments to locate far-placed Access Points.

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).

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

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

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.

EOS now exposes ASIC integrated-circuit memory health metrics via gNMI, under the vendor-augmented OpenConfig component tree. Two categories of memory are reported per chip instance: DRAM Bulk Data Block (BDB) free counts and SRAM buffer free counts. Each category provides three views: current value, minimum observed since last reset, and minimum observed in the latest polling interval.

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.