JUNIPER-JS-IPSEC-VPN-MIB
Juniper Networks, Inc.This module defines the object used to monitor the
entries pertaining to IPSec objects and the management
of the IPSEC VPN functionalities for Juniper security
product lines.
This mib module extend Juniper's common IPSEC flow monitoring
MIB, building on the existing common infrastruature, the
security implementation integrates the value-added
features for the security productssnmptranslate -m JUNIPER-JS-IPSEC-VPN-MIB -Tpsnmpwalk -v2c -c <community> -m JUNIPER-JS-IPSEC-VPN-MIB <host> 1.3.6.1.4.1.2636.3.39.1.5.1Imports
| JUNIPER-IPSEC-FLOW-MON-MIB | jnxIpSecTunnelMonEntry |
|---|---|
| JUNIPER-JS-SMI | jnxJsIPSecVpn |
| SNMPv2-CONF | MODULE-COMPLIANCE, NOTIFICATION-GROUP |
| SNMPv2-SMI | Bits, Integer32, IpAddress, MODULE-IDENTITY, MibIdentifier, OBJECT-IDENTITY, OBJECT-TYPE, TimeTicks, Unsigned32, iso |
| SNMPv2-TC | DisplayString, PhysAddress, TEXTUAL-CONVENTION |
OID tree
| Name | OID | Type | Access | Status |
|---|---|---|---|---|
| IjnxJsIpSecVpnMib | 1.3.6.1.4.1.2636.3.39.1.5.1 | |||
identity This module defines the object used to monitor the
entries pertaining to IPSec objects and the management
of the IPSEC VPN functionalities for Juniper security
product lines.
This mib module extend Juniper's common IPSEC flow monitoring
MIB, building on the existing common infrastruature, the
security implementation integrates the value-added
features for the security products | ||||
| NjnxJsIpSecVpnNotifications | 1.3.6.1.4.1.2636.3.39.1.5.1.0 | |||
| NjnxJsIpSecVpnPhaseOne | 1.3.6.1.4.1.2636.3.39.1.5.1.1 | |||
| NjnxJsIpSecVpnPhaseTwo | 1.3.6.1.4.1.2636.3.39.1.5.1.2 | |||
| TjnxJsIpSecTunnelTable | 1.3.6.1.4.1.2636.3.39.1.5.1.2.1 | NA | ||
table · not-accessible · current 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. | ||||
| RjnxJsIpSecTunnelEntry | 1.3.6.1.4.1.2636.3.39.1.5.1.2.1.1 | NA | ||
row · not-accessible · current Each entry contains the attributes associated with an active IPsec Phase-2 Tunnel.
| ||||
| CjnxJsIpSecTunPolicyName | 1.3.6.1.4.1.2636.3.39.1.5.1.2.1.1.1 | DisplayString (SIZE (0..80)) | RO | |
column · DisplayString (SIZE (0..80)) · read-only · current The policy name assoicated with this tunnel if the this IPSEC VPN is policy based. Otherwise, this attribute is not applicable. | ||||
| CjnxJsIpSecVpnTunType | 1.3.6.1.4.1.2636.3.39.1.5.1.2.1.1.2 | JnxJsIpSecVpnType | RO | |
column · JnxJsIpSecVpnType · read-only · current This attribute indicates the IPSEC VPN tunnel is policy based or route based. | ||||
| CjnxJsIpSecTunCfgMonState | 1.3.6.1.4.1.2636.3.39.1.5.1.2.1.1.3 | INTEGER | RO | |
column · INTEGER · read-only · current The user configuration states whether to monitor the IPSec tunnel to be alive or not.
| ||||
| CjnxJsIpSecTunState | 1.3.6.1.4.1.2636.3.39.1.5.1.2.1.1.4 | INTEGER | RO | |
column · INTEGER · read-only · current This attribute indicates whether the IPSec Tunnel is up or down, determined by icmp ping if the jnxJsIpSecTunCfgMonState is enable. Down: VPN monitor detects the tunnel is down Up: VPN monitor detects the tunnel is up. vpnMonitoringDisabled: user has disabled VPN tunnel monitoring.
| ||||
Textual conventions
JnxJsIpSecVpnTypeINTEGERpolicyBased(1)routeBased(2)The type of the remote peer gateway (endpoint). It can be one of the following two types: - policyBased : tunnels requires a policy with action 'tunnel' to trigger IPSEC VPN. The device receives traffic and matches it with policy that has action 'tunnel', it performs the encryption/decryption and authentication options negotiated for this VPN phase 2 negotiation. - routeBased : requires a tunnel interface a route directing traffic to protected networks to exit the system using that tunnel interface. The tunnel interface is bound to a Phase 2 VPN configuration that specifies all the tunnel parameters.