Tag :: TOI

For a pair of QSFP100 ports grouped together on a gearbox, it is possible to enable a 10G or 25G link on the first primary port while maintaining the usage of the secondary port at any speed. For two QSFP100 ports on a gearbox, the primary port allows for breakout speeds 4x10G and 4x25G, while the secondary does not. The configuration of the primary port determines whether the secondary port can be used since in a full breakout mode such as 4x10G the secondary port is forced inactive.

In EOS 4.18.1, support for 25G/50G is added on 7500R, 7280R, 7500R2 and 7280R2 series. This feature provides forced

The BGP extended communities support within EOS has been enhanced to include support for 4 octet AS Extended BGP

Starting EOS release 4.15.2F, the ability to re number front panel ports of 7050QX 32S is supported.

The 7500E 6CFPX LC linecard with ACO CFP2 optics provides connectivity over DWDM systems and links. 7500E 6CFPX LC

The 802.11be standards build on 802.11ax by providing ultra-high throughput, improved resource utilization, and interference mitigation. The 320 MHz support increases the throughput and performance in the 6GHz band. The improved resource utilization is attributed to the introduction of Multiple Resource Units (MRU) in Orthogonal Frequency Division Multiple Access (OFDMA) transmission and Multi-Link Operation (MLO).

This article describes a feature for Tap Aggregation mode, which strips IEEE 802.1BR E-Tag and Cisco VN-Tag headers from all tagged packets received on tap interface before delivering them out of tool interfaces.

802.1X is an IEEE standard protocol that prevents unauthorized devices from gaining access to the network.

802.1X port security controls who can send traffic through and receive traffic from the individual switch ports. A

Measured boot is an anti-tamper mechanism. It calculates the cryptographic signatures for software system components and extends the signatures into the Trusted Platform Module (TPM) security chip. Upon startup, with the feature turned on, the Aboot bootloader and EOS calculate the hash of various system components and extend the hashes into the Platform Configuration Registers (PCRs), which is one of the resources of the Trusted Platform Module (TPM) security chip. The calculation and extension event is called the measured boot event, which is associated with a revision number to help the user identify changes to the event.

Measured boot is an anti-tamper mechanism. It calculates the cryptographic signatures for software system components and extends the signatures into the Trusted Platform Module (TPM) security chip. Upon startup, with the feature turned on, the Aboot bootloader and EOS calculate the hash of various system components and extend the hashes into the Platform Configuration Registers (PCRs), which is one of the resources of the Trusted Platform Module (TPM) security chip. The calculation and extension event is called the measured boot event, which is associated with a revision number to help the user identify changes to the event.

Measured boot is an anti-tamper mechanism. It calculates the cryptographic signatures for software system components and extends the signatures into the Trusted Platform Module (TPM) security chip. Upon startup, with the feature turned on, the Aboot bootloader and EOS calculate the hash of various system components and extend the hashes into the Platform Configuration Registers (PCRs), which is one of the resources of the Trusted Platform Module (TPM) security chip. The calculation and extension event is called the measured boot event, which is associated with a revision number to help the user identify changes to the event.

Measured boot is an anti-tamper mechanism. It calculates the cryptographic signatures for software system components and extends the signatures into the Trusted Platform Module (TPM) security chip. Upon startup, with the feature turned on, the Aboot bootloader and EOS calculate the hash of various system components and extend the hashes into the Platform Configuration Registers (PCRs), which is one of the resources of the Trusted Platform Module (TPM) security chip. The calculation and extension event is called the measured boot event, which is associated with a revision number to help the user identify changes to the event.

Measured boot is an anti-tamper mechanism. It calculates the cryptographic signatures for software system components and extends the signatures into the Trusted Platform Module (TPM) security chip. Upon startup, with the feature turned on, the Aboot bootloader and EOS calculate the hash of various system components and extend the hashes into the Platform Configuration Registers (PCRs), which is one of the resources of the Trusted Platform Module (TPM) security chip. The calculation and extension event is called the measured boot event, which is associated with a revision number to help the user identify changes to the event.

Measured boot is an anti-tamper mechanism. It calculates the cryptographic signatures for software system components and extends the signatures into the Trusted Platform Module (TPM) security chip. Upon startup, with the feature turned on, the Aboot bootloader and EOS calculate the hash of various system components and extend the hashes into the Platform Configuration Registers (PCRs), which is one of the resources of the Trusted Platform Module (TPM) security chip. The calculation and extension event is called the measured boot event, which is associated with a revision number to help the user identify changes to the event.

Measured boot is an anti-tamper mechanism. It calculates the cryptographic signatures for software system components and extends the signatures into the Trusted Platform Module (TPM) security chip. Upon startup, with the feature turned on, the Aboot bootloader and EOS calculate the hash of various system components and extend the hashes into the Platform Configuration Registers (PCRs), which is one of the resources of the Trusted Platform Module (TPM) security chip. The calculation and extension event is called the measured boot event, which is associated with a revision number to help the user identify changes to the event.

Measured boot is an anti-tamper mechanism. It calculates the cryptographic signatures for software system components and extends the signatures into the Trusted Platform Module (TPM) security chip. Upon startup, with the feature turned on, the Aboot bootloader and EOS calculate the hash of various system components and extend the hashes into the Platform Configuration Registers (PCRs), which is one of the resources of the Trusted Platform Module (TPM) security chip. The calculation and extension event is called the measured boot event, which is associated with a revision number to help the user identify changes to the event.

Measured boot is an anti-tamper mechanism. It calculates the cryptographic signatures for software system components and extends the signatures into the Trusted Platform Module (TPM) security chip. Upon startup, with the feature turned on, the Aboot bootloader and EOS calculate the hash of various system components and extend the hashes into the Platform Configuration Registers (PCRs), which is one of the resources of the Trusted Platform Module (TPM) security chip. The calculation and extension event is called the measured boot event, which is associated with a revision number to help the user identify changes to the event.

You can now enable CloudVision to combine the authentication and authorization requests that it sends to a RADIUS server into a single request. When RADIUS is configured as the AAA provider, CloudVision will send separate authentication and authorization requests by default. This can cause issues with One-Time Password (OTP) users, as issued passwords are only valid for one request. Note: Non-OTP RADIUS systems will be unaffected by the change. To combine authentication and authorization requests, navigate to Settings > Access Control and enable the Combine Login Auth Requests checkbox.

This studio enables you to quickly configure access interfaces towards endpoint devices in your campus network. This configuration relates to the devices in Access Pods deployed using the Campus Fabric (L2/L3/EVPN) Studio.

This studio enables you to quickly configure access interfaces towards endpoint devices in your campus network. This configuration relates to the devices in Access Pods deployed using the Campus Fabric (L2/L3/EVPN) Studio. The studio consists of port profiles and campus networks. You can create port profiles, which contain configuration for attributes like speed and MTU, which you can then assign to device interfaces in a campus fabric. Editing the profile will then affect all interfaces that the profile has been assigned to. You can also configure individual interfaces.

With the 12.0 release, CloudVision Cognitive Unified Edge (CV-CUE) introduces Access Points (AP) Explorer. AP Explorer helps you view the distribution of APs by various attributes such as Model, Software Version, Status, and so on.

This feature enables user to modify QoS parameters for SVI traffic (L3 VLAN) based on ACL classification. The QoS

Ingress policing provides the ability to monitor the data rates for a particular class of traffic and perform action

A new role permission, Action Execution, has been introduced to control the execution of custom actions when they are run in isolation, such as via Studio Autofill actions and standalone executions in the Action editor. A custom action is a user-created action that has either been installed via a package or has been created using python script and arguments.

The active active neutron controller support in CVX enables the deployment of highly available neutron service with

Starting EOS 4.15.0F, users can configure NAT at IP address level with dynamically assigned one to one mapping

The following table describes the advanced mirroring features that are currently supported with links to their respective TOIs.

The DANZ Monitoring Fabric (DMF) Aggregate Arista GRE TAP action receives GRE-encapsulated packet samples from EOS switches, and generates an IPFIX report containing the flow 5-tuple, metadata, and timestamps from switches that the packet passed through.  Use the IPFIX report to determine the flows in a data fabric, monitor server session initialization delays, estimate the bandwidth of flows, and learn the path of packets through the fabric.

The AGM for ECMP feature allows monitoring the number of packets and bytes going through each members of the configured ECMP groups on the system, with a high time resolution. Once enabled, the feature will collect data for the specified duration, write it to the specified files on the system’s storage, then stop.

The DANZ Monitoring Fabric (DMF) Aggregate sFlow takes sFlow packet samples and generates an IPFIX report containing the flow 5-tuple, metadata, and timestamps from switches that the packet passed through.

Aggregate storm control with traffic class option provides the capability to rate limit BUM(Broadcast, Unknown

This article describes changes to the platform command 'show platform fm6000 agileports'. Earlier this command was

Agile ports allow users to connect 40G interfaces on 7130 products utilizing multiple SFP ports per 40G capable interface. This enables 40G capable applications, such as MetaConnect and MetaWatch, to operate at that speed.

The 40G only ports on Trident 2 switches may now be configured as 1 lane of 10G, 1G, or 100M*. This

With the 15.0 release, CloudVision Cognitive Unified Edge (CV-CUE) introduces API Sandbox that allows you to try out API flows.

This features enables ARPs learnt on an SVI interface to be converted into Host routes which can further be

The "set as path prepend" clause in the config route map mode is enhanced to accept the "auto" keyword. The "auto"

This feature is provided on all platforms. The BGP listen range command has been modified to optionally allow

Support for asset tagging aids hardware identification by the use of user supplied strings. Fixed

This feature adds support for associating a WAN interface with multiple Dynamic Path Selection (DPS) path groups to allow paths originating from the same interface to have different priorities.

AVB technology allows transporting time sensitive professional grade audio and video streams over a switched ethernet network while providing deterministic latency and bandwidth guarantees. Supporting protocols include:

With the 13.0.1 release, you can authenticate wired hosts connected to the LAN ports of access points (W-118 and W-318) using 802.1X or MAC-based authentication. You can configure the authentication parameters for each downlink port on the access point (AP) using a LAN Port profile in CV-CUE. The communication happens either through a bridged network or transferred using L2 Tunnels.

Use the Authentication Studio to configure RADIUS servers for user authentication and 802.1X authentication and accounting. The 802.1X authentication protocol is a port-based network access control that provides an extra layer of security for both wired and wireless networks.  

Automatic certificate management provides support for retrieving signed x509v3 certificates from a server under the Enrollment over Secure Transport (EST) protocol, described in RFC 7030. The feature provides only EST client capabilities.

This feature detects whether a given EOS image is MLAG ISSU compatible with the currently running version on a switch.

CloudVision Cognitive Unified Edge (CV-CUE) dynamically computes and updates a baseline for normal performance and connectivity of the network. The baseline adjusts as the network behavior changes, eliminating the false positive and false negative alerts associated with thresholds.

Use bearer tokens to provide custom applications or third-party applications, like Ansible, login access to CloudVision. Doing so will allow the application to make configuration changes to EOS devices. Bearer token login can be used with identity providers that issue bearer tokens and have an introspection endpoint. Okta and PingIdentity have been tested for use with CloudVision.

As of EOS 4.17.0F, BFD support has been enhanced with support for configuring BFD within VRFs, improved scalability

BFD for static routes enables monitoring of directly connected next hop reachability using a BFD session. This is