ARISTA-TAPAGG-MIB

All MIBs › ARISTA-TAPAGG-MIB

Organization: Arista Networks, Inc.

Last Updated: 2021-04-23

Category: Vendor: Arista

Description: Arista EOS tap aggregation port and traffic steering policy configuration management.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is ARISTA-TAPAGG-MIB?

ARISTA-TAPAGG-MIB is an Arista Networks EOS module for the TAP aggregation (tapagg) feature, used to aggregate and steer mirrored/tapped traffic for network performance monitoring. It exposes policy configuration, a policy table and per-policy traffic-class table, alongside traffic statistics of packets and bytes matched per classification rule. Its monitoring emphasis is on software/traffic-plane counters, letting operators verify that tap aggregation policies are correctly classifying and forwarding monitored traffic to downstream monitoring tools. It is a standalone Arista enterprise MIB tied to switch hardware capable of packet classification in hardware, as noted in its module description. It is deployed on Arista switches acting as tap/SPAN aggregation devices feeding network performance monitoring, IDS/IPS, or packet-capture tools in data centers. Engineers can download the ARISTA-TAPAGG-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in ARISTA-TAPAGG-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Arista EOS switch used for TAP aggregation

Monitoring Examples

aristaTapaggPolicyTable/aristaTapaggPolicyEntry (keyed by aristaTapaggPolicyId, named via aristaTapaggPolicyName) defines traffic-steering policies, while the nested aristaTapaggPolicyClassTable/aristaTapaggPolicyClassEntry tracks per-class counters aristaTapaggPolicyPktsMatched and aristaTapaggPolicyBytesMatched. An admin would poll these counters to confirm a classification rule, such as matching a specific VLAN or protocol, is actively matching traffic, and a sudden drop to zero matched packets/bytes would indicate a misconfigured tap policy or a traffic source that has stopped sending.

What Can Be Monitored

tap aggregation policy configuration
per-class packets matched
per-class bytes matched
policy/class naming and identifiers

Imported Objects

From ARISTA-QOS-MIB

AristaQosShortId

From ARISTA-SMI-MIB

aristaMibs

OBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter64
Integer32
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString

How to Use in IPNetwork Monitor

Example using aristaTapaggPolicyPktsMatched OID:

Select an Arista Networks EOS switch as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type aristaTapaggPolicyPktsMatched into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of packets that matched the specific packet classification criteria that corresponds to this conceptual row. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter64-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
aristaTapaggMIB	1.3.6.1.4.1.30065.3.31			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.
aristaTapaggMibObjects	1.3.6.1.4.1.30065.3.31.1
aristaTapaggPolicyTable	1.3.6.1.4.1.30065.3.31.1.1		not-accessible	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.
aristaTapaggPolicyEntry	1.3.6.1.4.1.30065.3.31.1.1.1		not-accessible	A single conceptual row containing information about a tapagg policy. A conceptual row is identified by a bounded-length identifier that corresponds to the name of the policy.
ARI aristaTapaggPolicyId	1.3.6.1.4.1.30065.3.31.1.1.1.1	AristaQosShortId	not-accessible	A bounded-length identifier that is mapped from the tapagg policy name.
STR aristaTapaggPolicyName	1.3.6.1.4.1.30065.3.31.1.1.1.2	DisplayString	read-only	The full name of the tapagg policy-map.
aristaTapaggPolicyClassTable	1.3.6.1.4.1.30065.3.31.1.2		not-accessible	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.
aristaTapaggPolicyClassEntry	1.3.6.1.4.1.30065.3.31.1.2.1		not-accessible	A single conceptual row containing information about a specific class-map within a policy. A conceptual row is identified by the following components: 1. A bounded-length identifier that corresponds to the name of the policy. 2. An index that identifies the sequence in which match criteria are evaluated at run time. The index values may not be consecutive.
I32 aristaTapaggPolicyClassIndex	1.3.6.1.4.1.30065.3.31.1.2.1.1	Integer32	not-accessible	An index that identifies the sequence in which match criteria are evaluated in the device hardware. An index with a smaller value will be evaluated first. The index values themselves may not be consecutive.
STR aristaTapaggPolicyClassName	1.3.6.1.4.1.30065.3.31.1.2.1.2	DisplayString	read-only	The name of the class-map within the policy that corresponds to this conceptual row. As described earlier, a simple match/set configuration is possible without creating a class-map construct. In that the case, the device manages relevant state by maintaining an internal/unique class-map name.
C64 aristaTapaggPolicyPktsMatchedEx	1.3.6.1.4.1.30065.3.31.1.2.1.3	Counter64	read-only	The number of packets that matched the specific packet classification criteria that corresponds to this conceptual row.
C64 aristaTapaggPolicyBytesMatched	1.3.6.1.4.1.30065.3.31.1.2.1.4	Counter64	read-only	The number of bytes that matched the specific packet classification criteria that corresponds to this conceptual row.
aristaTapaggMibConformance	1.3.6.1.4.1.30065.3.31.2
aristaTapaggMibCompliances	1.3.6.1.4.1.30065.3.31.2.1
aristaTapaggMibCompliance	1.3.6.1.4.1.30065.3.31.2.1.1			The compliance statement for Arista switches that implement the ARISTA-TAPAGG-MIB.
aristaTapaggMibGroups	1.3.6.1.4.1.30065.3.31.2.2
aristaTapaggPolicyGroup	1.3.6.1.4.1.30065.3.31.2.2.1			The collection of objects that provide tapagg policy information in the system.

RFC description

Tap aggregation feature on Arista switches for network performance monitoring and packet replication.

Start monitoring Arista Networks EOS switches with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download ARISTA-TAPAGG-MIB