Juniper-IPsec-Tunnel-MIB :: juniIpsecTunnelStatInbUserRecvPkts

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsJuniper-IPsec-Tunnel-MIBjuniIpsecTunnelStatInbUserRecvPkts

juniIpsecTunnelStatInbUserRecvPkts

Module: Juniper-IPsec-Tunnel-MIB

OID (symbolic): Juniper-IPsec-Tunnel-MIB::juniIpsecTunnelStatInbUserRecvPkts

OID (numeric): 1.3.6.1.4.1.4874.2.2.70.1.1.3.1.2

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: The total number of inbound user packets (non-error) received for this IPsec tunnel.

What is juniIpsecTunnelStatInbUserRecvPkts?

This read-only 64-bit counter tracks the total number of inbound, successfully-decrypted user data packets received on this IPsec tunnel. Admins watch this counter's rate to confirm real traffic is actually flowing through an established tunnel, not just control-plane keepalives.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.70.1.1.3.1.2
snmpwalk -v2c -c public <target> Juniper-IPsec-Tunnel-MIB::juniIpsecTunnelStatInbUserRecvPkts

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.70.1.1.3.1.2.1
snmpget -v2c -c public <target> Juniper-IPsec-Tunnel-MIB::juniIpsecTunnelStatInbUserRecvPkts.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> juniIpsecTunnelStatInbUserRecvPkts.1

Start monitoring Juniper Networks E-series (ERX) edge router (IPsec VPN tunnel interfaces) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Juniper-IPsec-Tunnel-MIB::juniIpsecTunnelStatInbUserRecvPkts OID value, configure state conditions and alerts, and monitor any Juniper Networks E-series (ERX) edge router (IPsec VPN tunnel interfaces) from a single console.

How to Use in IPNetwork Monitor

Select a Juniper Networks E-series (ERX) edge router (IPsec VPN tunnel interfaces) 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 juniIpsecTunnelStatInbUserRecvPkts 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 the total number of inbound user packets received (successfully, with no errors) for this IPsec tunnel. 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 stops increasing while the tunnel is expected to be passing traffic, since a stalled counter often means the tunnel has stopped forwarding. 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.4874juniperUniJuniper-UNI-SMI
1.3.6.1.4.1.4874.2juniperUniMibsJuniper-UNI-SMI
1.3.6.1.4.1.4874.2.2juniMibsJuniper-MIBs
Numeric OIDNameModule
1.3.6.1.4.1.4874.2.2.70juniIpsecTunnelMIBJuniper-IPsec-Tunnel-MIB
1.3.6.1.4.1.4874.2.2.70.1juniIpsecObjectsJuniper-IPsec-Tunnel-MIB
1.3.6.1.4.1.4874.2.2.70.1.1juniIpsecTunnelJuniper-IPsec-Tunnel-MIB
1.3.6.1.4.1.4874.2.2.70.1.1.3juniIpsecTunnelStatTableJuniper-IPsec-Tunnel-MIB
1.3.6.1.4.1.4874.2.2.70.1.1.3.1juniIpsecTunnelStatEntryJuniper-IPsec-Tunnel-MIB
1.3.6.1.4.1.4874.2.2.70.1.1.3.1.2juniIpsecTunnelStatInbUserRecvPktsJuniper-IPsec-Tunnel-MIB