Tag :: EOS 4.36.2F

This feature adds support to configure the following QoS OpenConfig models via gNMI maximum queue length of a queue on a port within a given polling interval, average queue length of a queue on a port within a given polling interval

Segment Routing over IPv6 (SRv6) Micro Segment (uSID) is a high-efficiency architecture that drastically reduces packet header overhead by compressing and packing multiple routing instructions into a single 128-bit IPv6 address. To ensure robust operational visibility, this feature integrates native endpoint counters that track real-time packet and byte volumes for every endpoint operation (such as uN processing), providing network operators with granular telemetry for streamlined debuggability, path verification, and traffic analysis.

SRv6 is the segment routing using IPv6 Data plane. The segment ID is encoded as an IPv6 address. The Micro-Segment extension to SRv6 has representation of SIDs to enable compressing multiple of them into a single IPv6 address. 

In Segment Routing, Adjacency Segment (Adj-SID) directs a node to forward the packet over a specific link or a set of links to the remote node. This feature adds support for statically configured SRv6 Adj-SIDs using micro-SIDs, also referred to as uA. This feature builds on the base SRv6 support described in SRv6 uN Support TOI.

Access Control Lists (ACL) use packet classification to mark certain packets going through the packet processor pipeline and then take configured action against them. Rules are defined based on various fields of packets and usually TCAM is used to match packets to rules. For example, there can be a rule to match the packet source IP address against a list of IP addresses, and drop the packet if there is a match. This will be expressed in TCAM with multiple entries matching the list of IP addresses. The number of entries is reduced by masking off bits, if possible. TCAM is a limited resource, so with classifiers having a large number of rules and a big field list, TCAM runs out of resources.

This TOI supplements the Ingress Traffic Policy applied on ingress port interfaces. Please refer to that document for a description of Traffic Policies and field-sets. This TOI explains the Traffic Policies as applied in the ingress direction on VLAN interfaces. For Traffic Policies on the egress direction of VLAN interfaces, see the Egress Traffic Policy TOI.

This feature introduces the ability to define matching rules to configure transceiver tuning on a switch. This is useful when a particular collection of transceivers are known to require tuning values which differ from EOS defaults.

This feature enables support for applying policy maps to Switch Virtual Interfaces (SVI) in the egress direction. A policy map is a Quality of Service (QoS) feature comprising multiple class maps, each with defined match criteria and actions. Class maps evaluate traffic against these criteria, and configured actions are applied to matching traffic. While these policy maps can be applied to interfaces in both input and output directions to match ingress and egress traffic respectively, this feature specifically adds support for applying output policy maps to SVIs.

SWitch Aggregation Group (SWAG) is a feature in EOS that supports combining multiple physical switches into a single logical system with shared control plane and distributed data plane, simplifying network management and increasing scalability. This document describes how to configure and troubleshoot a SWAG.

Synchronous Ethernet (SyncE) provides support for frequency synchronization over Ethernet between devices traceable to an external frequency reference, like a primary reference clock, as specified in ITU G.8261.

The Timing Regeneration Filter (TRF) is a part of the Clock and Data Recovery component of the CRT50216 external PHY from Credo. It has a parameter, known as the bandwidth, which adjusts how the CRT50216 adjusts to frequency changes in the incoming signal from the peer.

Historically EOS transceiver-related configurations have been applied on a per-interface or per-slot basis, however this approach is inefficient in applying a configuration that is relevant to a group of transceiver modules determined by certain criteria.

To address such use cases, the concept of “transceiver matching rules” is being introduced.

Two rate three-color marker (TrTCM) meters an incoming packet stream and marks the packets based on two rates, PIR (Peak Information Rate) and CIR (Committed Information Rate), and their associated burst-sizes.

User-defined TPIDs allow an arbitrary TPID (Tag Protocol Identifier) to be used with a FlexEncap specification. A TPID is used in Ethernet frames to identify the encapsulation protocol, where standard values like 0x8100 (for IEEE 802.1q VLAN tagging) and 0x88a8 (for IEEE 802.1ad Q-in-Q) are commonly used. However, some network equipment may use non-standard or legacy values such as 0x9100. This feature allows FlexEncap subinterfaces to be configured with an arbitrary TPID to allow interfacing with networking equipment that uses values besides 0x8100 and 0x88a8.

VLAN tagged MACsec refers to frames that have a VLAN tag between the MAC source address and the MACsec ethertype.  This VLAN tag is unencrypted (in the clear) so that intermediate devices between the MACsec endpoints can forward the MACsec frames based on this unencrypted VLAN tag.

Previously, when both “ipv6 nd proxy prefix connected” and VXLAN is configured for a VLAN interface, and the router received a Neighbor solicitation (NS) with an IPv6 address within the connected prefix of the router, the router replied with the interface physical (or virtual-router if VARP is configured) mac address as long as the NS is received on a local (front-panel) port. This feature extends the behavior to also include the NS received from the VXLAN tunnel.

This feature is used to add VXLAN support for local-proxy-arp, Previously, when both “ip local-proxy-arp” and VXLAN is configured for a VLAN interface, and the router received an ARP request with an IP address within the same subnet as the router, the router replied with the interface physical (or virtual-router if VARP is configured) mac address for requests that are received on a local (front-panel) port. This feature extends the behavior to include the VXLAN tunneled ARP requests.

Wildcard-AS route target import for MAC VRFs enables simplified route target configuration in EVPN VXLAN deployments. When importing routes into MAC VRFs (VLAN-based or VLAN-aware-bundle), the Autonomous System (AS) portion of the route target can be replaced with a wildcard, so that only the Local Administrator value is compared during route target matching.

WRED ( Weighted Random Early Detection ) is one of the congestion management techniques. It works at queue level to drop packets randomly after crossing the given queue threshold even before the queue is full. Without WRED, all newly arriving packets get tail dropped once the queue is full, which creates TCP global synchronization issues. WRED helps to avoid TCP global synchronization.