JUNIPER-VPN-MIB :: jnxVpnPwPacketsSent

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsJUNIPER-VPN-MIBjnxVpnPwPacketsSent

jnxVpnPwPacketsSent

Module: JUNIPER-VPN-MIB

OID (symbolic): JUNIPER-VPN-MIB::jnxVpnPwPacketsSent

OID (numeric): 1.3.6.1.4.1.2636.3.26.1.4.1.21

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: The number of packets that have been sent over this Pseudo-Wire.

What is jnxVpnPwPacketsSent?

64-bit count of packets sent over this pseudowire, used for throughput and traffic-volume monitoring on higher-speed pseudowires where a 32-bit counter would wrap too quickly.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2636.3.26.1.4.1.21
snmpwalk -v2c -c public <target> JUNIPER-VPN-MIB::jnxVpnPwPacketsSent

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2636.3.26.1.4.1.21.1
snmpget -v2c -c public <target> JUNIPER-VPN-MIB::jnxVpnPwPacketsSent.1

Start monitoring Juniper MX/PE router (L2VPN/L3VPN service instances) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the JUNIPER-VPN-MIB::jnxVpnPwPacketsSent OID value, configure state conditions and alerts, and monitor any Juniper MX/PE router (L2VPN/L3VPN service instances) from a single console.

How to Use in IPNetwork Monitor

Select a Juniper MX/PE router (L2VPN/L3VPN service instances) 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 jnxVpnPwPacketsSent 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 have been sent over this Pseudo-Wire. 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 (8 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.2636juniperMIBJUNIPER-SMI
1.3.6.1.4.1.2636.3jnxMibsJUNIPER-SMI
Numeric OIDNameModule
1.3.6.1.4.1.2636.3.26jnxVpnMIBJUNIPER-VPN-MIB
1.3.6.1.4.1.2636.3.26.1jnxVpnMibObjectsJUNIPER-VPN-MIB
1.3.6.1.4.1.2636.3.26.1.4jnxVpnPwTableJUNIPER-VPN-MIB
1.3.6.1.4.1.2636.3.26.1.4.1jnxVpnPwEntryJUNIPER-VPN-MIB
1.3.6.1.4.1.2636.3.26.1.4.1.21jnxVpnPwPacketsSentJUNIPER-VPN-MIB