JNX-IPSEC-MONITOR-MIB

All MIBs › JNX-IPSEC-MONITOR-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2012-02-10

Category: VPN and Security, Vendor: Juniper

Description: Provides monitoring objects for IPsec security associations and tunnel statistics on Juniper Networks devices.

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 JNX-IPSEC-MONITOR-MIB?

JNX-IPSEC-MONITOR-MIB is a Juniper Networks enterprise MIB providing runtime monitoring of IPsec security associations (SAs) and VPN tunnels on Juniper routing/security platforms. It exposes tunnel and SA status, traffic/byte and packet counters, and likely negotiation or failure statistics that indicate whether IPsec tunnels are up and passing traffic correctly. As a software-status MIB it is used to verify VPN health -- confirming SAs are established, tunnels haven't dropped, and no abnormal rekey/negotiation failures are occurring -- rather than reporting chassis hardware sensors. It depends on the underlying IPsec/IKE protocol suite and typically complements standard interface and tunnel MIBs (e.g., IF-MIB) for correlating tunnel state with logical interfaces. It is deployed on Juniper SRX firewalls and routers terminating site-to-site or remote-access IPsec VPNs in enterprise or service-provider networks. Engineers can download the JNX-IPSEC-MONITOR-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in JNX-IPSEC-MONITOR-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 SRX firewall
Juniper router with IPsec VPN termination

Monitoring Examples

An administrator would poll IPsec SA/tunnel status objects to detect a tunnel that has gone down or failed to renegotiate, correlating it with traffic counters that show a sudden drop to zero bytes/packets. No sample objects were extracted for this module, so specific table names cannot be cited, but the MIB's purpose implies an SA table keyed by tunnel/peer identifiers with status and byte-count columns. This is primarily useful for VPN uptime and throughput monitoring rather than general chassis health.

What Can Be Monitored

IPsec tunnel/SA status
tunnel traffic byte/packet counts
SA negotiation failures
VPN peer connectivity

Imported Objects

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From JUNIPER-SMI

jnxMibs

OBJECT-IDENTITY

From JUNIPER-SP-MIB

jnxSpSvcSetName

OBJECT-TYPE

From SNMPv2-SMI

Counter32
Counter64
Integer32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DisplayString
TEXTUAL-CONVENTION
TimeInterval

How to Use in IPNetwork Monitor

Example using jnxIkeTunInOctets OID:

Select a Juniper SRX firewall / router (IPsec VPN tunnel monitoring) 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 jnxIkeTunInOctets 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 total number of octets received by this IPsec Phase-1 IKE security association. 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 (in Octets), 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

OID symbolic	OID numeric	Type	Access	Description
jnxIpSecMonitorMIB	1.3.6.1.4.1.2636.3.22
jnxIpSecMIBObjects	1.3.6.1.4.1.2636.3.22.1
jnxIpSecLevels	1.3.6.1.4.1.2636.3.22.1.1
I32 jnxIpSecMibLevel	1.3.6.1.4.1.2636.3.22.1.1.1	Integer32	read-only	The version of the IPsec MIB.
jnxIpSecPhaseOne	1.3.6.1.4.1.2636.3.22.1.2
jnxIkeTunnelTable	1.3.6.1.4.1.2636.3.22.1.2.1		not-accessible	The IPsec Phase-1 Internet Key Exchange Tunnel Table. There is one entry in this table for each active IPsec Phase-1 IKE Tunnel.
jnxIkeTunnelEntry	1.3.6.1.4.1.2636.3.22.1.2.1.1		not-accessible	Each entry contains the attributes associated with an active IPsec Phase-1 IKE Tunnel.
I32 jnxIkeTunIndex	1.3.6.1.4.1.2636.3.22.1.2.1.1.1	Integer32	not-accessible	The index of the IPsec Phase-1 IKE Tunnel Table. The value of the index is a number which begins at one and is incremented with each tunnel that is created. The value of this object will wrap at 2,147,483,647.
JNX jnxIkeTunLocalRole	1.3.6.1.4.1.2636.3.22.1.2.1.1.2	JnxIkePeerRole	read-only	The role of local peer identity. The Role of the local peer can be: 1. initiator. 2. or responder.
JNX jnxIkeTunNegState	1.3.6.1.4.1.2636.3.22.1.2.1.1.3	JnxIkeNegState	read-only	The state of the current negotiation , It can be 1. matured 2. not matured
STR jnxIkeTunInitiatorCookie	1.3.6.1.4.1.2636.3.22.1.2.1.1.4	DisplayString	read-only	Cookie as generated by the peer that initiated the IKE Phase-1 negotiation. This cookie is carried in the ISAKMP header.
STR jnxIkeTunResponderCookie	1.3.6.1.4.1.2636.3.22.1.2.1.1.5	DisplayString	read-only	Cookie as generated by the peer responding to the IKE Phase-1 negotiation initiated by the remote peer. This cookie is carried in the ISAKMP header.
JNX jnxIkeTunLocalIdType	1.3.6.1.4.1.2636.3.22.1.2.1.1.6	JnxIkePeerType	read-only	The type of local peer identity. The local peer may be identified by: 1. an IP address, or 2. or a fully qualified domain name string. 3. or a distinguished name string.
STR jnxIkeTunLocalIdValue	1.3.6.1.4.1.2636.3.22.1.2.1.1.7	DisplayString	read-only	The value of the local peer identity. If the local peer type is an IP Address, then this is the IP Address used to identify the local peer. If the local peer type is id_fqdn, then this is the FQDN of the remote peer. If the local peer type is a id_dn, then this is the distinguished name string of the local peer.
IPt jnxIkeTunLocalGwAddrType	1.3.6.1.4.1.2636.3.22.1.2.1.1.8	InetAddressType	read-only	The IP address type of the local endpoint (gateway) for the IPsec Phase-1 IKE Tunnel.
IP jnxIkeTunLocalGwAddr	1.3.6.1.4.1.2636.3.22.1.2.1.1.9	InetAddress	read-only	The IP address of the local endpoint (gateway) for the IPsec Phase-1 IKE Tunnel.
STR jnxIkeTunLocalCertName	1.3.6.1.4.1.2636.3.22.1.2.1.1.10	DisplayString	read-only	Name of the certificate used for authentication of the local tunnel endpoint. This object will have some valid value only if negotiated IKE authentication method is other than pre-saherd key. If the IKE negotiation do not use certificate based authentication method, then the value of this object will be a NULL string.
JNX jnxIkeTunRemoteIdType	1.3.6.1.4.1.2636.3.22.1.2.1.1.11	JnxIkePeerType	read-only	The type of remote peer identity. The remote peer may be identified by: 1. an IP address, or 2. or a fully qualified domain name string. 3. or a distinguished name string.
STR jnxIkeTunRemoteIdValue	1.3.6.1.4.1.2636.3.22.1.2.1.1.12	DisplayString	read-only	The value of the remote peer identity. If the remote peer type is an IP Address, then this is the IP Address used to identify the remote peer. If the remote peer type is id_fqdn, then this is the FQDN of the remote peer. If the remote peer type is a id_dn, then this is the distinguished named string of the remote peer.
IPt jnxIkeTunRemoteGwAddrType	1.3.6.1.4.1.2636.3.22.1.2.1.1.13	InetAddressType	read-only	The IP address type of the remote gateway (endpoint) for the IPsec Phase-1 IKE Tunnel.
IP jnxIkeTunRemoteGwAddr	1.3.6.1.4.1.2636.3.22.1.2.1.1.14	InetAddress	read-only	The IP address of the remote gateway (endpoint) for the IPsec Phase-1 IKE Tunnel.
JNX jnxIkeTunNegoMode	1.3.6.1.4.1.2636.3.22.1.2.1.1.15	JnxIkeNegoMode	read-only	The negotiation mode of the IPsec Phase-1 IKE Tunnel.
JNX jnxIkeTunDiffHellmanGrp	1.3.6.1.4.1.2636.3.22.1.2.1.1.16	JnxDiffHellmanGrp	read-only	The Diffie Hellman Group used in IPsec Phase-1 IKE negotiations.
JNX jnxIkeTunEncryptAlgo	1.3.6.1.4.1.2636.3.22.1.2.1.1.17	JnxEncryptAlgo	read-only	The encryption algorithm used in IPsec Phase-1 IKE negotiations.
JNX jnxIkeTunHashAlgo	1.3.6.1.4.1.2636.3.22.1.2.1.1.18	JnxIkeHashAlgo	read-only	The hash algorithm used in IPsec Phase-1 IKE negotiations.
JNX jnxIkeTunAuthMethod	1.3.6.1.4.1.2636.3.22.1.2.1.1.19	JnxIkeAuthMethod	read-only	The authentication method used in IPsec Phase-1 IKE negotiations.
I32 jnxIkeTunLifeTime	1.3.6.1.4.1.2636.3.22.1.2.1.1.20	Integer32	read-only	The negotiated LifeTime of the IPsec Phase-1 IKE Tunnel in seconds.
NUM jnxIkeTunActiveTime	1.3.6.1.4.1.2636.3.22.1.2.1.1.21	TimeInterval	read-only	The length of time the IPsec Phase-1 IKE tunnel has been active in hundredths of seconds.
C64 jnxIkeTunInOctetsEx	1.3.6.1.4.1.2636.3.22.1.2.1.1.22	Counter64	read-only	The total number of octets received by this IPsec Phase-1 IKE security association.
C32 jnxIkeTunInPkts	1.3.6.1.4.1.2636.3.22.1.2.1.1.23	Counter32	read-only	The total number of packets received by this IPsec Phase-1 IKE security association.
C64 jnxIkeTunOutOctets	1.3.6.1.4.1.2636.3.22.1.2.1.1.24	Counter64	read-only	The total number of octets sent by this IPsec Phase-1 IKE security association.
C32 jnxIkeTunOutPkts	1.3.6.1.4.1.2636.3.22.1.2.1.1.25	Counter32	read-only	The total number of packets sent by this IPsec Phase-1 IKE security association.
jnxIpSecPhaseTwo	1.3.6.1.4.1.2636.3.22.1.3
jnxIpSecTunnelTable	1.3.6.1.4.1.2636.3.22.1.3.1		not-accessible	The IPsec Phase-2 Tunnel Table. There is one entry in this table for each active IPsec Phase-2 Tunnel.
jnxIpSecTunnelEntry	1.3.6.1.4.1.2636.3.22.1.3.1.1		not-accessible	Each entry contains the attributes associated with an active IPsec Phase-2 Tunnel.
I32 jnxIpSecTunIndex	1.3.6.1.4.1.2636.3.22.1.3.1.1.1	Integer32	not-accessible	The index of the IPsec Phase-2 Tunnel Table. The value of the index is a number which begins at one and is incremented with each tunnel that is created. The value of this object will wrap at 2,147,483,647.
STR jnxIpSecRuleName	1.3.6.1.4.1.2636.3.22.1.3.1.1.2	DisplayString	read-only	Name of the rule configured in IPSec configuration.
STR jnxIpSecTermName	1.3.6.1.4.1.2636.3.22.1.3.1.1.3	DisplayString	read-only	Name of the term configured under IPSec rule.
IPt jnxIpSecTunLocalGwAddrType	1.3.6.1.4.1.2636.3.22.1.3.1.1.4	InetAddressType	read-only	The IP address type of the local gateway (endpoint) for the IPsec Phase-2 Tunnel.
IP jnxIpSecTunLocalGwAddr	1.3.6.1.4.1.2636.3.22.1.3.1.1.5	InetAddress	read-only	The IP address of the local gateway (endpoint) for the IPsec Phase-2 Tunnel.
IPt jnxIpSecTunRemoteGwAddrType	1.3.6.1.4.1.2636.3.22.1.3.1.1.6	InetAddressType	read-only	The IP address type of the remote gateway (endpoint) for the IPsec Phase-2 Tunnel.
IP jnxIpSecTunRemoteGwAddr	1.3.6.1.4.1.2636.3.22.1.3.1.1.7	InetAddress	read-only	The IP address of the remote gateway (endpoint) for the IPsec Phase-2 Tunnel.
STR jnxIpSecTunLocalProxyId	1.3.6.1.4.1.2636.3.22.1.3.1.1.8	DisplayString	read-only	Identifier for the local end.
STR jnxIpSecTunRemoteProxyId	1.3.6.1.4.1.2636.3.22.1.3.1.1.9	DisplayString	read-only	Identifier for the remote end.
JNX jnxIpSecTunKeyType	1.3.6.1.4.1.2636.3.22.1.3.1.1.10	JnxKeyType	read-only	The type of key used by the IPsec Phase-2 Tunnel. It can be one of the following two types: - IKE negotiated - Manually installed
JNX jnxIpSecRemotePeerType	1.3.6.1.4.1.2636.3.22.1.3.1.1.11	JnxRemotePeerType	read-only	The type of the remote peer gateway (endpoint). It can be one of the following two types: - static (Remote peer whose IP address is known beforehand) - dynamic (Remote peer whose IP address is not known beforehand)
I32 jnxIpSecTunMtu	1.3.6.1.4.1.2636.3.22.1.3.1.1.12	Integer32	read-only	MTU value of this Phase-2 tunnel.
C64 jnxIpSecTunOutEncryptedBytes	1.3.6.1.4.1.2636.3.22.1.3.1.1.13	Counter64	read-only	Number of bytes encrypted by this Phase-2 tunnel.
C64 jnxIpSecTunOutEncryptedPkts	1.3.6.1.4.1.2636.3.22.1.3.1.1.14	Counter64	read-only	Number of packets encrypted by this Phase-2 tunnel.
C64 jnxIpSecTunInDecryptedBytes	1.3.6.1.4.1.2636.3.22.1.3.1.1.15	Counter64	read-only	Number of bytes decrypted by this Phase-2 tunnel.
C64 jnxIpSecTunInDecryptedPkts	1.3.6.1.4.1.2636.3.22.1.3.1.1.16	Counter64	read-only	Number of packets decrypted by this Phase-2 tunnel.
C64 jnxIpsSecTunAHInBytes	1.3.6.1.4.1.2636.3.22.1.3.1.1.17	Counter64	read-only	Number of incoming bytes authenticated using AH by this Phase-2 tunnel.
C64 jnxIpsSecTunAHInPkts	1.3.6.1.4.1.2636.3.22.1.3.1.1.18	Counter64	read-only	Number of incoming packets authenticated using AH by this Phase-2 tunnel.
C64 jnxIpsSecTunAHOutBytes	1.3.6.1.4.1.2636.3.22.1.3.1.1.19	Counter64	read-only	Number of outgoing bytes applied AH by this Phase-2 tunnel.
C64 jnxIpsSecTunAHOutPkts	1.3.6.1.4.1.2636.3.22.1.3.1.1.20	Counter64	read-only	Number of outgoing packets applied AH by this Phase-2 tunnel.
C64 jnxIpSecTunReplayDropPkts	1.3.6.1.4.1.2636.3.22.1.3.1.1.21	Counter64	read-only	Number of packets dropped by this Phase-2 tunnel due to anti replay check failure.
C64 jnxIpSecTunAhAuthFails	1.3.6.1.4.1.2636.3.22.1.3.1.1.22	Counter64	read-only	Number of packets received by this Phase-2 tunnel that failed AH authentication.
C64 jnxIpSecTunEspAuthFails	1.3.6.1.4.1.2636.3.22.1.3.1.1.23	Counter64	read-only	Number of packets received by this Phase-2 tunnel that failed ESP authentication.
C64 jnxIpSecTunDecryptFails	1.3.6.1.4.1.2636.3.22.1.3.1.1.24	Counter64	read-only	Number of packets received by this Phase-2 tunnel that failed decryption.
C64 jnxIpSecTunBadHeaders	1.3.6.1.4.1.2636.3.22.1.3.1.1.25	Counter64	read-only	Number of packets received by this Phase-2 tunnel that failed due to bad headers.
C64 jnxIpSecTunBadTrailers	1.3.6.1.4.1.2636.3.22.1.3.1.1.26	Counter64	read-only	Number of packets received by this Phase-2 tunnel that failed due to bad ESP trailers.
C64 jnxIpSecTunDroppedPkts	1.3.6.1.4.1.2636.3.22.1.3.1.1.27	Counter64	read-only	Total number of dropped packets for this Phase-2 tunnel.
jnxIpSecSaTable	1.3.6.1.4.1.2636.3.22.1.3.2		not-accessible	The IPsec Phase-2 Security Association Table. This table identifies the structure (in terms of component SAs) of each active Phase-2 IPsec tunnel. This table contains an entry for each active and expiring security association and maps each entry in the active Phase-2 tunnel table (ipSecTunTable) into a number of entries in this table. The index of this table reflects the rule for identifying Security Associations.
jnxIpSecSaEntry	1.3.6.1.4.1.2636.3.22.1.3.2.1		not-accessible	Each entry contains the attributes associated with active and expiring IPsec Phase-2 security associations.
INT jnxIpSecSaProtocol	1.3.6.1.4.1.2636.3.22.1.3.2.1.1	INTEGER	not-accessible	The index, represents the security protocol (AH, ESP or IPComp) for which this security association was setup.
I32 jnxIpSecSaIndex	1.3.6.1.4.1.2636.3.22.1.3.2.1.2	Integer32	not-accessible	The index, in the context of the IPsec tunnel ipSecTunIndex, of the security association represented by this table entry. The value of this index is a number which begins at one and is incremented with each SPI associated with an IPsec Phase-2 Tunnel. The value of this object will wrap at 2,147,483,647.
JNX jnxIpSecSaInSpi	1.3.6.1.4.1.2636.3.22.1.3.2.1.3	JnxSpi	read-only	The value of the incoming SPI.
JNX jnxIpSecSaOutSpi	1.3.6.1.4.1.2636.3.22.1.3.2.1.4	JnxSpi	read-only	The value of the outgoing SPI.
JNX jnxIpSecSaInAuxSpi	1.3.6.1.4.1.2636.3.22.1.3.2.1.5	JnxSpi	read-only	The value of the incoming auxiliary SPI. This is valid for AH and ESP bundles.
JNX jnxIpSecSaOutAuxSpi	1.3.6.1.4.1.2636.3.22.1.3.2.1.6	JnxSpi	read-only	The value of the outgoing auxiliary SPI. This is valid for AH and ESP bundles.
JNX jnxIpSecSaType	1.3.6.1.4.1.2636.3.22.1.3.2.1.7	JnxSAType	read-only	This field represents the type of security associations which can be either manual or dynamic
JNX jnxIpSecSaEncapMode	1.3.6.1.4.1.2636.3.22.1.3.2.1.8	JnxEncapMode	read-only	The encapsulation mode used by an IPsec Phase-2 Tunnel.
I32 jnxIpSecSaLifeSize	1.3.6.1.4.1.2636.3.22.1.3.2.1.9	Integer32	read-only	The negotiated LifeSize of the IPsec Phase-2 Tunnel in kilobytes.
I32 jnxIpSecSaLifeTime	1.3.6.1.4.1.2636.3.22.1.3.2.1.10	Integer32	read-only	The negotiated LifeTime of the IPsec Phase-2 Tunnel in seconds.
NUM jnxIpSecSaActiveTime	1.3.6.1.4.1.2636.3.22.1.3.2.1.11	TimeInterval	read-only	The length of time the IPsec Phase-2 Tunnel has been active in seconds.
I32 jnxIpSecSaLifeSizeThreshold	1.3.6.1.4.1.2636.3.22.1.3.2.1.12	Integer32	read-only	The security association LifeSize refresh threshold in kilobytes.
I32 jnxIpSecSaLifeTimeThreshold	1.3.6.1.4.1.2636.3.22.1.3.2.1.13	Integer32	read-only	The security association LifeTime refresh threshold in seconds.
JNX jnxIpSecSaEncryptAlgo	1.3.6.1.4.1.2636.3.22.1.3.2.1.14	JnxEncryptAlgo	read-only	The Encryption algorithm used to encrypt the packets which can be either es-cbc or 3des-cbc.
JNX jnxIpSecSaAuthAlgo	1.3.6.1.4.1.2636.3.22.1.3.2.1.15	JnxAuthAlgo	read-only	The algorithm used for authentication of packets which can be hmac-md5-96 or hmac-sha1-96
INT jnxIpSecSaState	1.3.6.1.4.1.2636.3.22.1.3.2.1.16	INTEGER	read-only	This column represents the status of the security association represented by this table entry. If the status of the SA is 'active', the SA is ready for active use. The status 'expiring' represents any of the various states that the security association transitions through before being purged.

RFC description

Juniper IPsec monitoring MIB for monitoring IPsec Phase-1 and Phase-2 tunnels, security associations, and IKE tunnel status on Juniper devices.

Start monitoring Juniper SRX firewall / router (IPsec VPN tunnel monitoring) 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 JNX-IPSEC-MONITOR-MIB