- Written by Graeme Rennie
- Posted on March 31, 2017
- Updated on April 18, 2022
- 2505 Views
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.
- Written by Bidong Chen
- Posted on October 20, 2022
- Updated on January 17, 2023
- 1201 Views
This feature enables Tap Aggregation generic header removal on a tap port.
- Written by Shyam Kota
- Posted on February 23, 2021
- Updated on March 29, 2023
- 3508 Views
This feature terminates GRE packets on a TapAgg switch by stripping the GRE header and then letting the decapped packets go through the normal TapAgg path. With this feature, we can use an L3 GRE tunnel to transit tapped traffic to the TapAgg switch over an L3 network. That would widely extend the available use cases for TapAgg.
- Written by Shyam Kota
- Posted on September 7, 2021
- Updated on November 2, 2021
- 2919 Views
This feature extends the capabilities of Tap Aggregation traffic steering to allow for using traffic policies.
- Written by Charlotte Fedderly
- Posted on January 21, 2019
- Updated on April 6, 2022
- 2271 Views
This article describes the TAP Aggregation 802.1Q (VLAN) tag stripping feature. This feature allows up to two of the outermost incoming 802.1Q tags to be stripped, and can be configured on a traffic steering policy or a tool port.
- Written by Graeme Rennie
- Posted on February 15, 2022
- Updated on May 11, 2022
- 2268 Views
This article describes the Tap Aggregation MAC Address Replacement feature. This feature provides the ability to configure user-specific values to replace the destination and source MAC addresses of packets forwarded by Tap Aggregation.
- Written by Stefan Kheraj
- Posted on March 3, 2023
- Updated on March 30, 2023
- 405 Views
Support for independently editing packets copied to multiple tool interfaces
- Written by Tegar Wicaksono
- Posted on June 20, 2022
- Updated on June 24, 2022
- 1363 Views
This feature provides support for packet counters for Tap Aggregation on default forwarding, traffic steering based on policy map and traffic steering based on traffic policy (Aegis). For brevity, counters for policy-map traffic steering will be referred to as policy-map counters, and counters for traffic-policy traffic steering will be referred to as traffic-policy counters.
- Written by Graeme Rennie
- Posted on February 22, 2021
- Updated on April 18, 2022
- 2324 Views
As of EOS-4.25.2F some advanced Tap Aggregation features require the hardware forwarding profile to be set. On EOS-4.25.2F these features are MPLS Pop and 802.1br-E/VN Tag Stripping.
- Written by Travis Hammond
- Posted on September 21, 2021
- Updated on July 26, 2022
- 3486 Views
Timestamping is an important tool for network engineering and performance analysis. The timestamp can be applied to
- Written by Ritika Adlakha
- Posted on August 16, 2018
- Updated on October 8, 2018
- 2113 Views
This article describes how QoS attributes are handled on tap ports as of EOS 4.20.5F. Prior to EOS 4.20.5F, QoS
- Written by Sneha Janardhan Nayak
- Posted on August 16, 2018
- Updated on September 24, 2018
- 2240 Views
As of EOS 4.21.0F, CLI commands can specify different TCAM profiles for different linecards in Tap Aggregation mixed
- Written by Anais Taing
- Posted on March 13, 2020
- Updated on February 5, 2022
- 2795 Views
The Tap Aggregation timestamping feature supports both timestamping packets in TAI (International Atomic Time)
- Written by Graeme Rennie
- Posted on October 20, 2022
- Updated on October 25, 2022
- 1115 Views
Internal recirculation interfaces, IR interfaces, can be used to internally loop-back packets for a second pass through the packet forwarding pipeline. This is particularly useful with Tap Aggregation because some combinations of advanced Tap Aggregation features cannot be simultaneously applied to a packet. Using an IR interface however, a user can apply multiple Tap Aggregation egress editing features, overcoming previous limitations.
- Written by Anais Taing
- Posted on June 5, 2020
- Updated on April 18, 2022
- 2353 Views
In TAP Aggregation mode, when receiving a packet whose Frame Check Sequence (FCS) is corrupted, the default behavior is to replace the bad FCS with the correct value and forward it.
- Written by Robert Cartelli
- Posted on August 16, 2018
- Updated on June 28, 2021
- 2706 Views
While in Tap Aggregation mode, we support traffic only in one direction through either Tap ports receiving packets