
JUNIPER-JS-IPSEC-VPN-MIB
File:
JUNIPER-JS-IPSEC-VPN-MIB.mib (7037 bytes)
Imported modules
Imported symbols
Defined Objects
| jnxJsIpSecVpnMib |
1.3.6.1.4.1.2636.3.39.1.5.1 |
| 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 |
| MODULE-IDENTITY |
|
|
|
| jnxJsIpSecTunnelTable |
1.3.6.1.4.1.2636.3.39.1.5.1.2.1 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
JnxJsIpSecTunnelEntry |
|
| jnxJsIpSecTunnelEntry |
1.3.6.1.4.1.2636.3.39.1.5.1.2.1.1 |
| Each entry contains the attributes associated with an active IPsec Phase-2 Tunnel. |
| OBJECT-TYPE |
|
|
|
| |
JnxJsIpSecTunnelEntry |
|
|
| jnxJsIpSecTunCfgMonState |
1.3.6.1.4.1.2636.3.39.1.5.1.2.1.1.3 |
| The user configuration states whether to monitor the IPSec tunnel to be alive or not. |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
disable(1), enable(2) |
|
| jnxJsIpSecTunState |
1.3.6.1.4.1.2636.3.39.1.5.1.2.1.1.4 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
up(1), down(2), vpnMonitoringDisabled(3) |
|
Defined Objects
| JnxJsIpSecVpnType |
|
| 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. |
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
policyBased(1), routeBased(2) |
|
| JnxJsIpSecTunnelEntry |
|
| SEQUENCE |
|
|
|
| |
DisplayString as jnxJsIpSecTunPolicyName |
|
|
| |
JnxJsIpSecVpnType as jnxJsIpSecVpnTunType |
|
|
| |
INTEGER as jnxJsIpSecTunCfgMonState |
|
|
| |
INTEGER as jnxJsIpSecTunState |
|
|