PRVT-L2TUNNELING-MIB :: l2TunnSapRxPackets

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › PRVT-L2TUNNELING-MIB › l2TunnSapRxPackets

l2TunnSapRxPackets

Module: PRVT-L2TUNNELING-MIB

OID (symbolic): PRVT-L2TUNNELING-MIB::l2TunnSapRxPackets

OID (numeric): 1.3.6.1.4.1.738.1.7.3.1.8.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of SAP Rx L2Tunneling packets

What is l2TunnSapRxPackets?

This read-only Counter32 value counts L2 tunneling packets received at a SAP for a specific protocol. An admin monitors this per-protocol, per-SAP counter to confirm that expected tunneled control traffic (like customer BPDUs) is actually arriving at that access point. A steadily increasing l2TunnSapRxPackets count for the xSTP protocol on a given SAP confirms customer spanning-tree BPDUs are being received and tunneled at that access point.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.738.1.7.3.1.8.1.1
snmpwalk -v2c -c public <target> PRVT-L2TUNNELING-MIB::l2TunnSapRxPackets

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.738.1.7.3.1.8.1.1.1
snmpget -v2c -c public <target> PRVT-L2TUNNELING-MIB::l2TunnSapRxPackets.1

Start monitoring BATM Advanced Communication carrier Ethernet switch (Layer 2 protocol tunneling) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the PRVT-L2TUNNELING-MIB::l2TunnSapRxPackets OID value, configure state conditions and alerts, and monitor any BATM Advanced Communication carrier Ethernet switch (Layer 2 protocol tunneling) from a single console.

How to Use in IPNetwork Monitor

Select a BATM Advanced Communication carrier Ethernet switch (Layer 2 protocol tunneling) 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 l2TunnSapRxPackets 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 SAP Rx L2Tunneling packets. 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 Counter32-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.

OID Breakdown

Upper-level ancestors (9 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.738privateVendorOIDPRIV-VENDORDEF-MIB
1.3.6.1.4.1.738.1prvt_productsPRVT-SWITCH-MIB
1.3.6.1.4.1.738.1.7serviceAccessSwitchPRVT-QOS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.738.1.7.3prvtL2TunnelingMIBPRVT-L2TUNNELING-MIB
1.3.6.1.4.1.738.1.7.3.1prvtL2TunnObjectsPRVT-L2TUNNELING-MIB
1.3.6.1.4.1.738.1.7.3.1.8prvtL2TunnSapStatisticsTablePRVT-L2TUNNELING-MIB
1.3.6.1.4.1.738.1.7.3.1.8.1prvtL2TunnSapStatisticsEntryPRVT-L2TUNNELING-MIB
1.3.6.1.4.1.738.1.7.3.1.8.1.1l2TunnSapRxPacketsPRVT-L2TUNNELING-MIB