JUNIPER-JS-IPSEC-VPN-MIB
- Registered at
- 1.3.6.1.4.1.2636.3.39.1.5.1
- Last updated
- 2007-05-11 21:53
- Organization
- Juniper Networks, Inc.
- Revisions
- 2007-04-27 00:00
- Namespace
- juniper
- Source file
JUNIPER-JS-IPSEC-VPN-MIB- Digest
sha256:73bf36d294373faf87dc80ab98152893fc62d3c000458623588d318f2da905a7
Description
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
Contact
Juniper Technical Assistance Center Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, CA 94089 E-mail: support@juniper.net
Imports
| From | Symbols |
|---|---|
| JUNIPER-IPSEC-FLOW-MON-MIB | jnxIpSecTunnelMonEntry |
| JUNIPER-JS-SMI | jnxJsIPSecVpn |
| SNMPv2-CONF | MODULE-COMPLIANCE, NOTIFICATION-GROUP |
| SNMPv2-SMI | MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, iso |
| SNMPv2-TC | DisplayString, TEXTUAL-CONVENTION |
Imported by
Nothing in this corpus imports this module.
Load order
Every file a consumer needs in order to load this module, dependencies first.
INET-ADDRESS-MIB JUNIPER-IPSEC-FLOW-MON-MIB JUNIPER-JS-IPSEC-VPN-MIB JUNIPER-JS-SMI JUNIPER-SMI SNMPv2-CONF SNMPv2-SMI SNMPv2-TC
Textual conventions
| Name | OID | Syntax | Access | Status |
|---|---|---|---|---|
| JnxJsIpSecVpnType TEXTUAL-CONVENTION 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. | current |
Objects
| Name | OID | Syntax | Access | Status |
|---|---|---|---|---|
| jnxJsIpSecVpnNotifications OBJECT-IDENTITY | 1.3.6.1.4.1.2636.3.39.1.5.1.0 | |||
| jnxJsIpSecVpnPhaseOne OBJECT-IDENTITY | 1.3.6.1.4.1.2636.3.39.1.5.1.1 | |||
| jnxJsIpSecVpnPhaseTwo OBJECT-IDENTITY | 1.3.6.1.4.1.2636.3.39.1.5.1.2 | |||
| jnxJsIpSecTunnelTable OBJECT-TYPE 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.39.1.5.1.2.1 | not-accessible | current | |
| jnxJsIpSecTunnelEntry OBJECT-TYPE Each entry contains the attributes associated with an active IPsec Phase-2 Tunnel. | 1.3.6.1.4.1.2636.3.39.1.5.1.2.1.1 | not-accessible | current | |
| jnxJsIpSecTunPolicyName OBJECT-TYPE The policy name assoicated with this tunnel if the this IPSEC VPN is policy based. Otherwise, this attribute is not applicable. | 1.3.6.1.4.1.2636.3.39.1.5.1.2.1.1.1 | DisplayString (SIZE(0..80)) | read-only | current |
| jnxJsIpSecVpnTunType OBJECT-TYPE This attribute indicates the IPSEC VPN tunnel is policy based or route based. | 1.3.6.1.4.1.2636.3.39.1.5.1.2.1.1.2 | JnxJsIpSecVpnType | read-only | current |
| jnxJsIpSecTunCfgMonState OBJECT-TYPE The user configuration states whether to monitor the IPSec tunnel to be alive or not. | 1.3.6.1.4.1.2636.3.39.1.5.1.2.1.1.3 | INTEGER {disable(1), enable(2)} | read-only | current |
| jnxJsIpSecTunState OBJECT-TYPE 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. | 1.3.6.1.4.1.2636.3.39.1.5.1.2.1.1.4 | INTEGER {up(1), down(2), vpnMonitoringDisabled(3)} | read-only | current |