ZXR10-VLANATT-MIB :: zxr10IfVlanTrafficStatInPkts

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › ZXR10-VLANATT-MIB › zxr10IfVlanTrafficStatInPkts

zxr10IfVlanTrafficStatInPkts

Module: ZXR10-VLANATT-MIB

OID (symbolic): ZXR10-VLANATT-MIB::zxr10IfVlanTrafficStatInPkts

OID (numeric): 1.3.6.1.4.1.3902.3.102.52.2.1.5

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: In Packets.

What is zxr10IfVlanTrafficStatInPkts?

Read-only Counter64 counting inbound packets received on this specific interface/inner-VLAN/outer-VLAN QinQ combination -- lets an admin see per-customer (per inner VLAN) traffic volume on a shared trunk port.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3902.3.102.52.2.1.5
snmpwalk -v2c -c public <target> ZXR10-VLANATT-MIB::zxr10IfVlanTrafficStatInPkts

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.3902.3.102.52.2.1.5.1
snmpget -v2c -c public <target> ZXR10-VLANATT-MIB::zxr10IfVlanTrafficStatInPkts.1

Start monitoring ZTE ZXR10 switches with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ZXR10-VLANATT-MIB::zxr10IfVlanTrafficStatInPkts OID value, configure state conditions and alerts, and monitor any ZTE ZXR10 switches from a single console.

How to Use in IPNetwork Monitor

Select a ZTE ZXR10 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 zxr10IfVlanTrafficStatInPkts 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. It reports in 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 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.

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.3902zteDPI-MIB
1.3.6.1.4.1.3902.3zxr10FANS-POWER-MIB
1.3.6.1.4.1.3902.3.102zxr10switchVct-Loopdetect-59-MIB
Numeric OIDNameModule
1.3.6.1.4.1.3902.3.102.52zxr10VlanAttZXR10-VLANATT-MIB
1.3.6.1.4.1.3902.3.102.52.2zxr10IfVlanTrafficStatTableZXR10-VLANATT-MIB
1.3.6.1.4.1.3902.3.102.52.2.1zxr10IfVlanTrafficStatEntryZXR10-VLANATT-MIB
1.3.6.1.4.1.3902.3.102.52.2.1.5zxr10IfVlanTrafficStatInPktsZXR10-VLANATT-MIB