NETSCREEN-VPN-MON-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › NETSCREEN-VPN-MON-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2004-05-03

Category: IPSec/VPN

Description: Monitors VPN tunnel liveness, rekey events, and SA lifetime counters on Juniper NetScreen ScreenOS firewalls.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is NETSCREEN-VPN-MON-MIB?

NETSCREEN-VPN-MON-MIB monitors VPN tunnel status on Juniper NetScreen ScreenOS firewalls, tracking tunnel liveness, rekey activity, and security-association (SA) parameters such as encryption/authentication algorithms and key type. It exposes per-tunnel status and configuration data, including inbound/outbound SPI (security parameter index) values, tunnel type, VPN and virtual-system name, and the negotiated ESP/AH algorithms, giving visibility into whether a VPN tunnel is correctly established and using the expected cryptographic parameters. This MIB is used heavily for software-status monitoring of the VPN subsystem: administrators poll it to detect tunnels that have dropped, failed to rekey, or negotiated unexpected (weaker) algorithms, which directly affects both connectivity and security posture. It complements NETSCREEN-ZONE-MIB and NETSCREEN-INTERFACE-MIB since VPN tunnels are bound to specific zones/vsys and interfaces on the firewall. It is deployed wherever NetScreen firewalls terminate site-to-site or remote-access IPsec VPNs, such as branch-to-headquarters links or partner extranet connections. Engineers can download the NETSCREEN-VPN-MON-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in NETSCREEN-VPN-MON-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • Juniper NetScreen (ScreenOS) firewall

Monitoring Examples

An operator polls nsVpnMonTable/nsVpnMonEntry by nsVpnMonIndex to check nsVpnMonInPlyId and nsVpnMonOutPlyId (inbound/outbound SPIs) for a given nsVpnMonVpnName, confirming the tunnel has valid, matching security associations on both directions. If nsVpnMonEspEncAlg or nsVpnMonEspAuthAlg reports an unexpected algorithm (e.g., a weaker cipher than configured), that would flag a policy or negotiation problem worth investigating. Missing or stale entries in nsVpnMonTable for a tunnel that should be up would indicate the VPN has dropped, prompting the admin to check nsVpnMonTunnelType and nsVpnMonVsysName to isolate which vsys/tunnel type is affected.

What Can Be Monitored

  • VPN tunnel up/down status
  • inbound/outbound SPI values
  • ESP encryption algorithm in use
  • ESP/AH authentication algorithm
  • VPN tunnel type and key type
  • tunnel-to-vsys/VPN name mapping
Imported Objects

From NETSCREEN-SMI

netscreenVpnOBJECT-IDENTITY
netscreenVpnMibModuleOBJECT-IDENTITY

From SNMPv2-SMI

Counter32
Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE
TimeTicks

From SNMPv2-TC

DisplayString

How to Use in IPNetwork Monitor

Example using nsVpnMonBytesIn OID:

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.
OIDs

RFC description

Monitors VPN tunnel status, encryption algorithms, and connection statistics for Juniper NetScreen devices.

Start monitoring Juniper NetScreen firewalls with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download NETSCREEN-VPN-MON-MIB