This MIB contains information related to the tapagg feature
that is implemented on specific Arista switches running EOS.

On specific Arista devices, EOS offers a powerful solution for
network performance monitoring. These devices have significant
bandwidth capacity and different port or interface speed options
for a non-blocking monitoring solution. This specific EOS
feature is called 'TAP aggregation' or 'tapagg'. These devices are
typically capable of performing packet classification in
hardware as well, and that can be used to steer the monitored
traffic as desired, directly to the right set of external tools.

With the tapagg feature, the Arista switching device is first
put into an exclusive mode to do the desired packet replication.
In this mode, normal switching functions like bridging, routing
etc. are disabled.

Interfaces are categorized into 'tap' (they receive the traffic
that is required to be replicated) and 'tool' (they transmit the
replicated packet out and are in the path towards the monitoring
tool).

Furthermore, the tapagg feature allows users to configure
classification rules via the policy-map construct so that the
mirrored traffic can be steered appropriately.

Another layer of indirection that is provided is called
aggregation-groups. Tap and tool interfaces can be part of a
specific aggregation group, and that allows for a powerful way
to express replication or mirroring rules. Policies can change
the aggregation group for specific set of packets, and that can
be used to steer traffic out of desired tool interfaces as
appropriate.

This MIB provides information related to the tapagg feature.