JUNIPER-JS-IPSEC-VPN-MIB
Updated May 11, 2007The JUNIPER-JS-IPSEC-VPN-MIB enables monitoring of IPsec tunnel states, security association parameters, and traffic flow statistics on Juniper security platforms. It extends the common IPsec flow monitoring infrastructure to expose vendor-specific security features for managing IPsec VPN functionalities.
Imported Objects
Objects
10 total| Object Name |
|---|
jnxJsIpSecVpnMibThis 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 .1.3.6.1.4.1.2636.3.39.1.5.1 |
jnxJsIpSecVpnNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.39.1.5.1.0 |
jnxJsIpSecVpnPhaseOne OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.39.1.5.1.1 |
jnxJsIpSecVpnPhaseTwo OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.39.1.5.1.2 |
jnxJsIpSecTunnelTableThe 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. SEQUENCE OF JnxJsIpSecTunnelEntry .1.3.6.1.4.1.2636.3.39.1.5.1.2.1 |
jnxJsIpSecTunnelEntryEach entry contains the attributes
associated with an active IPsec Phase-2 Tunnel. JnxJsIpSecTunnelEntry .1.3.6.1.4.1.2636.3.39.1.5.1.2.1.1 |
jnxJsIpSecTunPolicyNameThe policy name assoicated with this tunnel if the
this IPSEC VPN is policy based. Otherwise, this attribute
is not applicable.ro DisplayString .1.3.6.1.4.1.2636.3.39.1.5.1.2.1.1.1 |
jnxJsIpSecVpnTunTypeThis attribute indicates the IPSEC VPN tunnel is policy
based or route based.ro JnxJsIpSecVpnType .1.3.6.1.4.1.2636.3.39.1.5.1.2.1.1.2 |
jnxJsIpSecTunCfgMonStateThe user configuration states whether to monitor the
IPSec tunnel to be alive or not.ro Enumeration .1.3.6.1.4.1.2636.3.39.1.5.1.2.1.1.3 |
jnxJsIpSecTunStateThis 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.ro Enumeration .1.3.6.1.4.1.2636.3.39.1.5.1.2.1.1.4 |
More MIBs from Juniper Networks
Browse all Juniper NetworksMIBs →The JUNIPER-CHASSIS-DEFINES-MIB establishes the foundational Object Identifier (OID) namespace and data type definitions required to map and identify specific Juniper chassis hardware platforms and their internal physical components. This module serves as the structural prerequisite for the JUNIPER-CHASSIS-MIB, enabling the retrieval of inventory data, component status, and hardware topology details for Juniper MX, PTX, and EX series devices.
The JUNIPER-MOBILE-GATEWAY-GTP-MIB provides SNMP objects for monitoring GTP (GPRS Tunneling Protocol) session states, tunnel endpoints, and protocol counters on Juniper mobile gateway platforms. It enables administrators to track GTP-C and GTP-U traffic statistics, error conditions, and active tunnel metrics essential for validating mobile core network connectivity.
SNMP MIB module
SNMP MIB module
The JUNIPER-MOBILE-GATEWAY-SGW-GTP-MIB module enables monitoring of GTP (GPRS Tunneling Protocol) session states and traffic counters on Juniper Mobile Gateway Serving Gateways (SGW). It provides specific objects for tracking GTP-C and GTP-U tunnel establishment, teardown, and packet throughput metrics essential for validating mobile core network connectivity.
The JUNIPER-IPSEC-FLOW-MON-MIB monitors Juniper Networks IPsec VPN infrastructure by exposing tables for IKE tunnels, IPSec tunnels, and IPSec security associations to track tunnel states, association parameters, and flow statistics. This module facilitates the management of IPsec security policies and the operational status of encrypted traffic flows within the device's security architecture.