Tag :: Tap Aggregation

This feature enables Tap Aggregation generic header removal on a tap port. We support the removal of a number of bytes immediately following the ethernet header, including the VLAN tags. The number of bytes to be removed must be an even number less than or equal to 62. The original ethernet header will be removed by default but there is an option in the CLI command to preserve it.

This feature introduces the possibility of creating Tap Aggregation PMF profiles consisting of 80 bit keys, to make a more efficient use of TCAM resources. Previously, we could only have key sizes of 160 or 320 bits. 

Traffic steering is an existing Tap Aggregation feature that supports redirection of traffic based on configurable

Previously, Tap Aggregation and Mirror to GRE timestamping only supported timestamping packets in International

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.

Traffic steering to nexthop groups allows specifying one or more nexthop groups as the destination for a TAP aggregation steering policy. Traffic steering is a TAP aggregation process that uses class maps and policy maps to direct data streams received on TAP ports. 

This document describes the truncation capability for Tap Aggregation, which allows tapped traffic to be truncated to a smaller size before being transmitted.

This article describes the TAP Aggregation User Defined Fields feature. The purpose of the User Defined