- Written by Mike Nelson
- Posted on October 20, 2021
- Updated on December 20, 2021
- 9291 Views
Tagging traffic with a drop precedence is a method that can be used to differentiate traffic flows over a given
- Written by Edwin Tambi
- Posted on August 19, 2020
- Updated on July 3, 2024
- 22584 Views
EOS supports the ability to match on a single VLAN tag (example: encapsulation dot1q vlan 10) or a VLAN tag pair (example: encapsulation dot1q vlan 10 inner 20) to map matching packets to an interface. In this case, the encapsulation string is considered consumed by the mapped interface before forwarding, which means that the tags are effectively removed from the incoming packet for the purposes of any downstream forwarding.
- Written by Ajay Chhatwal
- Posted on May 15, 2020
- Updated on January 7, 2025
- 9231 Views
L2 protocol packets - LLDP, LACP and STP are trapped to the CPU by default. This feature allows for disabling the per protocol trap on a given set of interfaces.
- Written by Anurag Mishra
- Posted on January 22, 2019
- Updated on December 17, 2024
- 7030 Views
This feature allows a user to configure a mirror session with subinterface sources from the CLI. This feature is only available with ingress mirroring (rx direction)
- Written by Akanksha Gottipati
- Posted on August 23, 2022
- Updated on September 2, 2022
- 7074 Views
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.
- Written by Michael (Mike) Fink
- Posted on August 25, 2019
- Updated on August 25, 2019
- 8138 Views
Packets sampled for sFlow are packaged in a flow sample structure containing, amongst other things, input and output
- Written by Michael (Mike) Fink
- Posted on November 11, 2019
- Updated on November 11, 2019
- 9831 Views
Packets sampled for sFlow are packaged in a flow sample structure containing, amongst other things, input and output
- Written by Pankaj Srivastava
- Posted on October 24, 2024
- Updated on October 24, 2024
- 1684 Views
Storm control enables traffic policing on floods of packets on L2 switching networks. Support for counting dropped packets and bytes on interfaces where storm control metering is provisioned. Both packet and bytes count are supported and will be displayed. Drop logging on storm-control discards is also supported.
- Written by Praveen Kumar Yadav
- Posted on November 16, 2023
- Updated on November 16, 2023
- 5269 Views
Storm control enables traffic policing on floods of packets on L2 switching networks. Support was enabled for Front panel ports and Lag in eos-4-25-2f with storm-control-speed-rate-support. Now, storm control will be supported per subinterfaces( both ethernet and port-channel). Scale of subinterfaces is 4095.
- Written by Anitha Muppalla
- Posted on May 15, 2020
- Updated on September 28, 2023
- 8650 Views
Subinterfaces divide a single ethernet or port channel interface into multiple logical L2 or L3 interfaces based on the 802.1q or 802.1ad tags of incoming traffic. Subinterfaces are commonly used in the L2/L3 boundary device, but they can also be used to isolate traffic with 802.1q tags between L3 peers by assigning subinterfaces to different VRFs or different L2 bridging domains.
- Written by Dhruvalkumar Patel
- Posted on December 17, 2021
- Updated on December 27, 2021
- 7045 Views
L3 subinterface counters do not count GRE terminated (decap) packets and other tunnel types packets such as decap
- Written by Peter Thompson
- Posted on March 21, 2025
- Updated on March 21, 2025
- 128 Views
User-defined TPIDs allows 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.