NETSCREEN-VPN-MON-MIB :: nsVpnMonBytesIn

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › NETSCREEN-VPN-MON-MIB › nsVpnMonBytesIn

nsVpnMonBytesIn

Module: NETSCREEN-VPN-MON-MIB

OID (symbolic): NETSCREEN-VPN-MON-MIB::nsVpnMonBytesIn

OID (numeric): 1.3.6.1.4.1.3224.4.1.1.1.35

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Incoming bytes through this sa.

What is nsVpnMonBytesIn?

The count of bytes received inbound through this security association, a basic per-tunnel throughput counter for confirming traffic is actually flowing.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3224.4.1.1.1.35
snmpwalk -v2c -c public <target> NETSCREEN-VPN-MON-MIB::nsVpnMonBytesIn

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.3224.4.1.1.1.35.1
snmpget -v2c -c public <target> NETSCREEN-VPN-MON-MIB::nsVpnMonBytesIn.1

SNMPv3 example:

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

Start monitoring Juniper NetScreen firewalls with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the NETSCREEN-VPN-MON-MIB::nsVpnMonBytesIn OID value, configure state conditions and alerts, and monitor any Juniper NetScreen firewalls from a single console.

How to Use in IPNetwork Monitor

Select a Juniper NetScreen firewall 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 nsVpnMonBytesIn 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 incoming bytes through this sa. 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 (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.3224netscreenNETSCREEN-SMI
1.3.6.1.4.1.3224.4netscreenVpnNETSCREEN-SMI
Numeric OIDNameModule
1.3.6.1.4.1.3224.4.1netscreenVpnMonNETSCREEN-VPN-MON-MIB
1.3.6.1.4.1.3224.4.1.1nsVpnMonTableNETSCREEN-VPN-MON-MIB
1.3.6.1.4.1.3224.4.1.1.1nsVpnMonEntryNETSCREEN-VPN-MON-MIB
1.3.6.1.4.1.3224.4.1.1.1.35nsVpnMonBytesInNETSCREEN-VPN-MON-MIB