JUNIPER-IPSEC-FLOW-MON-MIB: View SNMP OID List / Download MIB
VENDOR: JUNIPER
Home | MIB: JUNIPER-IPSEC-FLOW-MON-MIB | |||
---|---|---|---|---|
Download as: |
Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
|
|||
Object Name | OID | Type | Access | Info |
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 | |||
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 | no-access |
The IPsec Phase-1 Internet Key Exchange Tunnel Table. There is one entry in this table for each active IPsec Phase-1 IKE Tunnel. |
|
1.3.6.1.4.1.2636.3.52.1.1.2.1 | no-access |
Each entry contains the attributes associated with an active IPsec Phase-1 IKE Tunnel. |
||
jnxIkeTunMonRemoteGwAddrType | 1.3.6.1.4.1.2636.3.52.1.1.2.1.1 | inetaddresstype | no-access |
The IP address type of the remote gateway (endpoint) for the IPsec Phase-1 IKE Tunnel. |
jnxIkeTunMonRemoteGwAddr | 1.3.6.1.4.1.2636.3.52.1.1.2.1.2 | inetaddress | no-access |
The IP address of the remote gateway (endpoint) for the IPsec Phase-1 IKE Tunnel. |
jnxIkeTunMonIndex | 1.3.6.1.4.1.2636.3.52.1.1.2.1.3 | integer32 | no-access |
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. |
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. |
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. |
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 |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
jnxIkeTunMonInOctets | 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. |
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. |
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. |
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. |
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. |
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 | |||
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 | no-access |
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. |
|
1.3.6.1.4.1.2636.3.52.1.2.2.1 | no-access |
Each entry contains the attributes associated with an active IPsec Phase-2 Tunnel. |
||
jnxIpSecTunMonRemoteGwAddrType | 1.3.6.1.4.1.2636.3.52.1.2.2.1.1 | inetaddresstype | no-access |
The IP address type of the remote gateway (endpoint) for the IPsec Phase-2 Tunnel. |
jnxIpSecTunMonRemoteGwAddr | 1.3.6.1.4.1.2636.3.52.1.2.2.1.2 | inetaddress | no-access |
The IP address of the remote gateway (endpoint) for the IPsec Phase-2 Tunnel. |
jnxIpSecTunMonIndex | 1.3.6.1.4.1.2636.3.52.1.2.2.1.3 | integer32 | no-access |
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. |
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. |
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. |
jnxIpSecTunMonLocalProxyId | 1.3.6.1.4.1.2636.3.52.1.2.2.1.6 | displaystring | read-only |
Identifier for the local end. |
jnxIpSecTunMonRemoteProxyId | 1.3.6.1.4.1.2636.3.52.1.2.2.1.7 | displaystring | read-only |
Identifier for the remote end. |
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 |
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) |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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 | no-access |
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. |
|
1.3.6.1.4.1.2636.3.52.1.2.3.1 | no-access |
Each entry contains the attributes associated with active and expiring IPsec Phase-2 security associations. |
||
jnxIpSecSaMonIndex | 1.3.6.1.4.1.2636.3.52.1.2.3.1.1 | integer32 | no-access |
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. |
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. Enumeration: 'ah': 1, 'esp': 2. |
jnxIpSecSaMonInSpi | 1.3.6.1.4.1.2636.3.52.1.2.3.1.3 | jnxspitype | read-only |
The value of the incoming SPI. |
jnxIpSecSaMonOutSpi | 1.3.6.1.4.1.2636.3.52.1.2.3.1.4 | jnxspitype | read-only |
The value of the outgoing SPI. |
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 |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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 |
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. Enumeration: 'active': 1, 'unknown': 0, 'expiring': 2. |