Tag :: QoS

Ingress policing provides the ability to monitor the data rates for a particular class of traffic and perform action when traffic exceeds user-configured values. This allows users to control ingress bandwidth based on packet classification.  Ingress policing is done by a policing meter which marks incoming traffic and performs actions based on the results of policing meters. 

This feature is an extension to the Explicit Congestion Notification (ECN) functionality for non ECN Capable

This feature introduces a new CLI command which disables the above-mentioned propagation of DSCP and ECN bits from the outer IP header. 

By default, the DSCP and ECN bits of VXLAN bridged packets are not rewritten. Currently, for bridged packets undergoing VXLAN encapsulation, the DSCP in the outer IP header is derived from TC and the ECN bits are set to zero. The desired behavior is that the outer IP header should be remarked with ingress packet DSCP and ingress packet ECN. Also, local congestion should be handled correctly.

This feature allows the user to match the 20 bit IPV6 flow label using the Qos Policy Map and allows to classify the flow-label controlled traffic.

The flow-label match for QoS policy map can be achieved by using the TCAM profile “qos-match-ipv6-flow-label” which is available from EOS 4.27.2F onwards. 

This feature allows classification of packets on QoS policy-maps based on the Class of Service (CoS), VLAN, Drop Eligible Indicator (DEI) in the 802.1q header of the packet. CoS (Class of Service) corresponds to the Priority code point (PCP) bits in the 802.1q header.

This feature allows classification of packets based on the inner VLAN value along with the VLAN and CoS bits in a double tagged packet.

With the use of MAC ACL configuration, match on ethertype can be programmed under QoS class-map configuration which will help customers to classify the control traffic based on ethertype (e.g. PPPoE discovery (0x8863) / session (0x8864) stage ) along with match on sub protocol (LCP/IPCP/PAP/CHAP) which is present in the payload.

Enhancement of QOS class maps to match on nexthop groups along with dscp (dscp being optional) to set any QOS actions

This feature adds support to configure and apply different COS to TC profiles on Front Panel Ports and Port Channel

Configure trust mode for trusting traffic from phone’s, but not any other traffic coming from the same interface.

This feature is an extension of Qos Policy. It allows the user to configure Qos Policy Map counters. If a class map is

This feature is an extension of Qos Policy. It allows the user to configure Qos Policy Map counters. If a class map is

This feature enables Qos policy-maps to match on IPv4/IPv6 fields for L3VPN & 6PE services on the LER device core facing interface, assuming all labels are popped and packets are sent to the customer as IP.

Since, now there can be multiple inputs, conflicts may arise. Non conflicting configurations are when non default

Allows the user to configure explicit QoS trust settings viz. trust mode, default cos and default dscp on subinterfaces, which may or may not be the same as the parent interface.

This feature allows the user to configure upto 1023 unique QoS Policy-maps per chip.

This feature adds a SNMP CLI knob to allow an interface’s speed, as shown in IF MIB, to reflect its shaped bandwidth.

ACL based QoS programmed on SVIs can share hardware resources starting from EOS 4.17.0F. This results in

The show command 'show qos interface fabric' was introduced for DCS 7250QX and DCS 7300X series starting EOS

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

The feature allows the user to determine the rate of ingress packets on a class-map over a span of a specified interval. This specified interval is the global load-interval (default value is 5 minutes).