ARISTA-TAPAGG-MIB Table View

This table contains information about the tapagg policies
configured in the system.
          
The configuration construct 'policy-map type tapagg' is used
to create and maintain these policies. Once a policy is defined it
can be applied against the appropriate interfaces. The basic idea
behind these policies is to classify packets (IP or IPv6 packet
information or L2 packet information etc.) and on relevant matches
take specific actions. One example of an action is to set
the aggregation-group for the matched traffic.
          
This table provides a simple list of tapagg policies, and a
subsequent table provides additional details for each policy.

This table contains additional details about the tapagg policies
configured in the system.
          
Within a policy the packet match criteria and set action are
provided using 'class-maps'. Internally the device maintains
useful state, including counters, for each class-map.
          
However, a simple match criteria along with a set
action can be provided without the class-map construct as well. In
this case, the device will automatically construct an internal/unique
class-map for this specific match/set configuration.
          
As mentioned above, counters are maintained for matched packets.
However, this requires explicit configuration so that the counter
resources in the hardware can be enabled.
          
There will be a conceptual row in this table for every class-map
configured inside a policy.