JUNIPER-IPSEC-FLOW-MON-MIB

All MIBs › JUNIPER-IPSEC-FLOW-MON-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2007-05-11

Category: VPN and Security, Vendor: Juniper

Description: Provides managed objects for IPsec tunnel flow monitoring, including SA statistics, packet counts, and error tracking 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 JUNIPER-IPSEC-FLOW-MON-MIB?

JUNIPER-IPSEC-FLOW-MON-MIB is a Juniper Networks, Inc. proprietary MIB (built on JNX-IPSEC-MONITOR-MIB) monitoring IKE/IPsec tunnels and security associations. Its IKE-tunnel-monitor table, keyed by index, records remote/local gateway address, tunnel state, initiator/responder cookie, local role, local/remote ID type/value, local certificate name, negotiation mode, Diffie-Hellman group, encryption/hash algorithm, auth method, lifetime, active time, and inbound octets, alongside companion IPsec tunnel and security-association tables. As a status/performance MIB it lets an administrator confirm IKE/IPsec tunnel negotiation parameters and traffic volume on a Juniper VPN gateway. It is deployed on Juniper Networks VPN gateway equipment (IPsec flow monitoring). Engineers can download the JUNIPER-IPSEC-FLOW-MON-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in JUNIPER-IPSEC-FLOW-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 Networks VPN gateway equipment (IPsec flow monitoring)

Monitoring Examples

An administrator checks jnxIkeTunMonState and jnxIkeTunMonEncryptAlgo to confirm IKE tunnel negotiation state and cipher on a Juniper VPN gateway.

What Can Be Monitored

IKE/IPsec tunnel negotiation state and traffic volume

Imported Objects

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From JUNIPER-SMI

jnxIpSecMibRoot

OBJECT-IDENTITY

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 jnxIkeTunMonInOctets OID:

Select a Juniper Networks VPN gateway (IKE/IPsec tunnel and SA 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 jnxIkeTunMonInOctets 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
jnxIpSecFlowMonMIB	1.3.6.1.4.1.2636.3.52.1			This module defines the object used to monitor the entries pertaining to IPSec objects and the management of the IPSEC VPN functionalities. tables: - IKE tunnel table - IPSec tunnel table - IPSec security associations table. This mib module is based on JNX-IPSEC-MONITOR-MIB. Building on the existing IKE infrastruature, the security IKE implementation integrates the value-added features for the security products
jnxIpSecFlowMonNotifications	1.3.6.1.4.1.2636.3.52.1.0
jnxIpSecFlowMonPhaseOne	1.3.6.1.4.1.2636.3.52.1.1
INT jnxIkeNumOfTunnels	1.3.6.1.4.1.2636.3.52.1.1.1	INTEGER	read-only	Number of IKE Tunnels (phase-1) actively negotiating between peers. The SA can be in either the up or down state. This attribute should detail the number of IKE tunnels in jnxIkeTunnelMonTable.
jnxIkeTunnelMonTable	1.3.6.1.4.1.2636.3.52.1.1.2		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.
jnxIkeTunnelMonEntry	1.3.6.1.4.1.2636.3.52.1.1.2.1		not-accessible	Each entry contains the attributes associated with an active IPsec Phase-1 IKE Tunnel.
IPt jnxIkeTunMonRemoteGwAddrType	1.3.6.1.4.1.2636.3.52.1.1.2.1.1	InetAddressType	not-accessible	The IP address type of the remote gateway (endpoint) for the IPsec Phase-1 IKE Tunnel.
IP jnxIkeTunMonRemoteGwAddr	1.3.6.1.4.1.2636.3.52.1.1.2.1.2	InetAddress	not-accessible	The IP address of the remote gateway (endpoint) for the IPsec Phase-1 IKE Tunnel.
I32 jnxIkeTunMonIndex	1.3.6.1.4.1.2636.3.52.1.1.2.1.3	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.
IP jnxIkeTunMonLocalGwAddr	1.3.6.1.4.1.2636.3.52.1.1.2.1.4	InetAddress	read-only	The IP address of the local endpoint (gateway) for the IPsec Phase-1 IKE Tunnel.
IPt jnxIkeTunMonLocalGwAddrType	1.3.6.1.4.1.2636.3.52.1.1.2.1.5	InetAddressType	read-only	The IP address type of the local endpoint (gateway) for the IPsec Phase-1 IKE Tunnel.
JNX jnxIkeTunMonState	1.3.6.1.4.1.2636.3.52.1.1.2.1.6	JnxIkeTunStateType	read-only	The state of the IKE tunnel, It can be: 1. up - negotiation completed 2. down- being negotiated
STR jnxIkeTunMonInitiatorCookie	1.3.6.1.4.1.2636.3.52.1.1.2.1.7	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 jnxIkeTunMonResponderCookie	1.3.6.1.4.1.2636.3.52.1.1.2.1.8	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 jnxIkeTunMonLocalRole	1.3.6.1.4.1.2636.3.52.1.1.2.1.9	JnxIkePeerRole	read-only	The role of local peer identity. The Role of the local peer can be: 1. initiator. 2. or responder.
JNX jnxIkeTunMonLocalIdType	1.3.6.1.4.1.2636.3.52.1.1.2.1.10	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 jnxIkeTunMonLocalIdValue	1.3.6.1.4.1.2636.3.52.1.1.2.1.11	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.
STR jnxIkeTunMonLocalCertName	1.3.6.1.4.1.2636.3.52.1.1.2.1.12	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 jnxIkeTunMonRemoteIdType	1.3.6.1.4.1.2636.3.52.1.1.2.1.13	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 jnxIkeTunMonRemoteIdValue	1.3.6.1.4.1.2636.3.52.1.1.2.1.14	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.
JNX jnxIkeTunMonNegoMode	1.3.6.1.4.1.2636.3.52.1.1.2.1.15	JnxIkeNegoMode	read-only	The negotiation mode of the IPsec Phase-1 IKE Tunnel.
JNX jnxIkeTunMonDiffHellmanGrp	1.3.6.1.4.1.2636.3.52.1.1.2.1.16	JnxDiffHellmanGrp	read-only	The Diffie Hellman Group used in IPsec Phase-1 IKE negotiations.
JNX jnxIkeTunMonEncryptAlgo	1.3.6.1.4.1.2636.3.52.1.1.2.1.17	JnxEncryptAlgo	read-only	The encryption algorithm used in IPsec Phase-1 IKE negotiations.
JNX jnxIkeTunMonHashAlgo	1.3.6.1.4.1.2636.3.52.1.1.2.1.18	JnxIkeHashAlgo	read-only	The hash algorithm used in IPsec Phase-1 IKE negotiations.
JNX jnxIkeTunMonAuthMethod	1.3.6.1.4.1.2636.3.52.1.1.2.1.19	JnxIkeAuthMethod	read-only	The authentication method used in IPsec Phase-1 IKE negotiations.
I32 jnxIkeTunMonLifeTime	1.3.6.1.4.1.2636.3.52.1.1.2.1.20	Integer32	read-only	The negotiated LifeTime of the IPsec Phase-1 IKE Tunnel in seconds.
NUM jnxIkeTunMonActiveTime	1.3.6.1.4.1.2636.3.52.1.1.2.1.21	TimeInterval	read-only	The length of time the IPsec Phase-1 IKE tunnel has been active in hundredths of seconds.
C64 jnxIkeTunMonInOctetsEx	1.3.6.1.4.1.2636.3.52.1.1.2.1.22	Counter64	read-only	The total number of octets received by this IPsec Phase-1 IKE security association.
C32 jnxIkeTunMonInPkts	1.3.6.1.4.1.2636.3.52.1.1.2.1.23	Counter32	read-only	The total number of packets received by this IPsec Phase-1 IKE security association.
C64 jnxIkeTunMonOutOctets	1.3.6.1.4.1.2636.3.52.1.1.2.1.24	Counter64	read-only	The total number of octets sent by this IPsec Phase-1 IKE security association.
C32 jnxIkeTunMonOutPkts	1.3.6.1.4.1.2636.3.52.1.1.2.1.25	Counter32	read-only	The total number of packets sent by this IPsec Phase-1 IKE security association.
STR jnxIkeTunMonXAuthUserId	1.3.6.1.4.1.2636.3.52.1.1.2.1.26	DisplayString	read-only	The extended Authentication (XAuth) User Identifier, identifies the user associated with this IPSec Phase negotiation.
C32 jnxIkeTunMonDPDDownCount	1.3.6.1.4.1.2636.3.52.1.1.2.1.27	Counter32	read-only	The number of times that the remote peer is detected in a dead (or down) state. This attribute is obsolete
jnxIpSecFlowMonPhaseTwo	1.3.6.1.4.1.2636.3.52.1.2
INT jnxIpSecNumOfTunnels	1.3.6.1.4.1.2636.3.52.1.2.1	INTEGER	read-only	Number of IPSEC VPN Tunnels. This attribute should detail the number of IPSEC VPN tunnel in jnxIpSecTunnelTable.
jnxIpSecTunnelMonTable	1.3.6.1.4.1.2636.3.52.1.2.2		not-accessible	The IPsec Phase-2 Tunnel Table. There is one entry in this table for each active IPsec Phase-2 Tunnel. If the tunnel is terminated, then the entry is no longer available after the table has been refreshed.
jnxIpSecTunnelMonEntry	1.3.6.1.4.1.2636.3.52.1.2.2.1		not-accessible	Each entry contains the attributes associated with an active IPsec Phase-2 Tunnel.
IPt jnxIpSecTunMonRemoteGwAddrType	1.3.6.1.4.1.2636.3.52.1.2.2.1.1	InetAddressType	not-accessible	The IP address type of the remote gateway (endpoint) for the IPsec Phase-2 Tunnel.
IP jnxIpSecTunMonRemoteGwAddr	1.3.6.1.4.1.2636.3.52.1.2.2.1.2	InetAddress	not-accessible	The IP address of the remote gateway (endpoint) for the IPsec Phase-2 Tunnel.
I32 jnxIpSecTunMonIndex	1.3.6.1.4.1.2636.3.52.1.2.2.1.3	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.
IPt jnxIpSecTunMonLocalGwAddrType	1.3.6.1.4.1.2636.3.52.1.2.2.1.4	InetAddressType	read-only	The IP address type of the local gateway (endpoint) for the IPsec Phase-2 Tunnel.
IP jnxIpSecTunMonLocalGwAddr	1.3.6.1.4.1.2636.3.52.1.2.2.1.5	InetAddress	read-only	The IP address of the local gateway (endpoint) for the IPsec Phase-2 Tunnel.
STR jnxIpSecTunMonLocalProxyId	1.3.6.1.4.1.2636.3.52.1.2.2.1.6	DisplayString	read-only	Identifier for the local end.
STR jnxIpSecTunMonRemoteProxyId	1.3.6.1.4.1.2636.3.52.1.2.2.1.7	DisplayString	read-only	Identifier for the remote end.
JNX jnxIpSecTunMonKeyType	1.3.6.1.4.1.2636.3.52.1.2.2.1.8	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 jnxIpSecTunMonRemotePeerType	1.3.6.1.4.1.2636.3.52.1.2.2.1.9	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)
C64 jnxIpSecTunMonOutEncryptedBytes	1.3.6.1.4.1.2636.3.52.1.2.2.1.10	Counter64	read-only	Number of bytes encrypted by this Phase-2 tunnel.
C64 jnxIpSecTunMonOutEncryptedPkts	1.3.6.1.4.1.2636.3.52.1.2.2.1.11	Counter64	read-only	Number of packets encrypted by this Phase-2 tunnel.
C64 jnxIpSecTunMonInDecryptedBytes	1.3.6.1.4.1.2636.3.52.1.2.2.1.12	Counter64	read-only	Number of bytes decrypted by this Phase-2 tunnel.
C64 jnxIpSecTunMonInDecryptedPkts	1.3.6.1.4.1.2636.3.52.1.2.2.1.13	Counter64	read-only	Number of packets decrypted by this Phase-2 tunnel.
C64 jnxIpSecTunMonAHInBytes	1.3.6.1.4.1.2636.3.52.1.2.2.1.14	Counter64	read-only	Number of incoming bytes authenticated using AH by this Phase-2 tunnel.
C64 jnxIpSecTunMonAHInPkts	1.3.6.1.4.1.2636.3.52.1.2.2.1.15	Counter64	read-only	Number of incoming packets authenticated using AH by this Phase-2 tunnel.
C64 jnxIpSecTunMonAHOutBytes	1.3.6.1.4.1.2636.3.52.1.2.2.1.16	Counter64	read-only	Number of outgoing bytes applied AH by this Phase-2 tunnel.
C64 jnxIpSecTunMonAHOutPkts	1.3.6.1.4.1.2636.3.52.1.2.2.1.17	Counter64	read-only	Number of outgoing packets applied AH by this Phase-2 tunnel.
C64 jnxIpSecTunMonReplayDropPkts	1.3.6.1.4.1.2636.3.52.1.2.2.1.18	Counter64	read-only	Number of packets dropped by this Phase-2 tunnel due to anti replay check failure.
C64 jnxIpSecTunMonAhAuthFails	1.3.6.1.4.1.2636.3.52.1.2.2.1.19	Counter64	read-only	Number of packets received by this Phase-2 tunnel that failed AH authentication.
C64 jnxIpSecTunMonEspAuthFails	1.3.6.1.4.1.2636.3.52.1.2.2.1.20	Counter64	read-only	Number of packets received by this Phase-2 tunnel that failed ESP authentication.
C64 jnxIpSecTunMonDecryptFails	1.3.6.1.4.1.2636.3.52.1.2.2.1.21	Counter64	read-only	Number of packets received by this Phase-2 tunnel that failed decryption.
C64 jnxIpSecTunMonBadHeaders	1.3.6.1.4.1.2636.3.52.1.2.2.1.22	Counter64	read-only	Number of packets received by this Phase-2 tunnel that failed due to bad headers.
C64 jnxIpSecTunMonBadTrailers	1.3.6.1.4.1.2636.3.52.1.2.2.1.23	Counter64	read-only	Number of packets received by this Phase-2 tunnel that failed due to bad ESP trailers.
C64 jnxIpSecTunMonDroppedPkts	1.3.6.1.4.1.2636.3.52.1.2.2.1.26	Counter64	read-only	Total number of dropped packets for this Phase-2 tunnel. This attribute is obsolete.
jnxIpSecSaMonTable	1.3.6.1.4.1.2636.3.52.1.2.3		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. SA contains the information negotiated by IKE. The SA is like a contract laying out the rules of the VPN connection for the duration of the SA. An SA is assigned a 32-bit number that, when used in conjunction with the destination IP address, uniquely identifies the SA. This number is called the Security Parameters Index or SPI. IPSec SAs area unidirectional and they are unique in each security protocol. A set of SAs are needed for a protected data pipe, one per direction per protocol.
jnxIpSecSaMonEntry	1.3.6.1.4.1.2636.3.52.1.2.3.1		not-accessible	Each entry contains the attributes associated with active and expiring IPsec Phase-2 security associations.
I32 jnxIpSecSaMonIndex	1.3.6.1.4.1.2636.3.52.1.2.3.1.1	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 65535.
INT jnxIpSecSaMonProtocol	1.3.6.1.4.1.2636.3.52.1.2.3.1.2	INTEGER	read-only	The index, represents the security protocol (AH, ESP or IPComp) for which this security association was setup.
JNX jnxIpSecSaMonInSpi	1.3.6.1.4.1.2636.3.52.1.2.3.1.3	JnxSpiType	read-only	The value of the incoming SPI.
JNX jnxIpSecSaMonOutSpi	1.3.6.1.4.1.2636.3.52.1.2.3.1.4	JnxSpiType	read-only	The value of the outgoing SPI.
JNX jnxIpSecSaMonType	1.3.6.1.4.1.2636.3.52.1.2.3.1.5	JnxSAType	read-only	This field represents the type of security associations which can be either manual or dynamic
JNX jnxIpSecSaMonEncapMode	1.3.6.1.4.1.2636.3.52.1.2.3.1.6	JnxEncapMode	read-only	The encapsulation mode used by an IPsec Phase-2 Tunnel.
I32 jnxIpSecSaMonLifeSize	1.3.6.1.4.1.2636.3.52.1.2.3.1.7	Integer32	read-only	The negotiated LifeSize of the IPsec Phase-2 Tunnel in kilobytes.
I32 jnxIpSecSaMonLifeTime	1.3.6.1.4.1.2636.3.52.1.2.3.1.8	Integer32	read-only	The negotiated LifeTime of the IPsec Phase-2 Tunnel in seconds.
NUM jnxIpSecSaMonActiveTime	1.3.6.1.4.1.2636.3.52.1.2.3.1.9	TimeInterval	read-only	The length of time the IPsec Phase-2 Tunnel has been active in hundredths of seconds.
I32 jnxIpSecSaMonLifeSizeThreshold	1.3.6.1.4.1.2636.3.52.1.2.3.1.10	Integer32	read-only	The security association LifeSize refresh threshold in kilobytes.
I32 jnxIpSecSaMonLifeTimeThreshold	1.3.6.1.4.1.2636.3.52.1.2.3.1.11	Integer32	read-only	The security association LifeTime refresh threshold in seconds.
JNX jnxIpSecSaMonEncryptAlgo	1.3.6.1.4.1.2636.3.52.1.2.3.1.12	JnxEncryptAlgo	read-only	The Encryption algorithm used to encrypt the packets which can be either es-cbc or 3des-cbc.
JNX jnxIpSecSaMonAuthAlgo	1.3.6.1.4.1.2636.3.52.1.2.3.1.13	JnxAuthAlgo	read-only	The algorithm used for authentication of packets which can be hmac-md5-96 or hmac-sha1-96 or hmac-sha-256-128
INT jnxIpSecSaMonState	1.3.6.1.4.1.2636.3.52.1.2.3.1.14	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

IPSec VPN flow monitoring with IKE tunnels, IPSec tunnels, and security association tracking and statistics.

Start monitoring Juniper Networks VPN gateway (IKE/IPsec tunnel and SA 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 JUNIPER-IPSEC-FLOW-MON-MIB