Standard view Table view

ONEACCESS-IPSEC-MIB

        Contact updated
Source file
ONEACCESS-IPSEC-MIB
Last revised
Identity
oacNatMIBModule
Base OID
1.3.6.1.4.1.13191.1.100.675
Imported Objects
IF-MIB ifIndex
ONEACCESS-GLOBAL-REG oacExpIMIp oacExpIMIPSec oacMIBModules
SNMPv2-CONF MODULE-COMPLIANCE OBJECT-GROUP
SNMPv2-SMI Counter32 Integer32 IpAddress MODULE-IDENTITY NOTIFICATION-TYPE OBJECT-TYPE Unsigned32
SNMPv2-TC TimeInterval
Net-SNMP examples using the oneaccess MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'ONEACCESS-IPSEC-MIB' -M '/opt/observium/mibs/oneaccess:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ONEACCESS-IPSEC-MIB::oacNatMIBModule'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'ONEACCESS-IPSEC-MIB' -M '/opt/observium/mibs/oneaccess:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ONEACCESS-IPSEC-MIB::oacNatMIBModule'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (3)
oacNatMIBModule
.1.3.6.1.4.1.13191.1.100.675
oacIPSecNotifications
.1.3.6.1.4.1.13191.10.3.1.4.1
oacIsakmpNotifications
.1.3.6.1.4.1.13191.10.3.1.4.2
Dependencies (7) 5 direct · 2 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. SNMPv2-TCrfc
  3. IANAifType-MIBrfc
  4. SNMPv2-CONFrfc
  5. SNMPv2-MIBrfc
  6. IF-MIBrfc
  7. ONEACCESS-GLOBAL-REGoneaccess
  8. ONEACCESS-IPSEC-MIBoneaccessselected
Notifications / Traps (17)
NameOIDDescription
oacIPSecSAcreated
.1.3.6.1.4.1.13191.10.3.1.4.1.1
An IPSec SA created notification signifies that the
device created an IPSec security association.
oacIPSecSAremoved
.1.3.6.1.4.1.13191.10.3.1.4.1.2
An IPSec SA removed notification signifies that the
device removed an IPSec security association.
oacIPSecCmapEnabled
.1.3.6.1.4.1.13191.10.3.1.4.1.3
An IPSec crypto map enabled notification signifies that the
device validated the crypto map attached to an interface
and the crypto map becomes valid on this interface.
oacIPSecCmapDisabled
.1.3.6.1.4.1.13191.10.3.1.4.1.4
An IPSec crypto map disabled notification signifies that the
device did not validate the crypto map attached to an interface
and the crypto map becomes invalid on this interface.
oacIPSecCpolEnabled
.1.3.6.1.4.1.13191.10.3.1.4.1.5
An IPSec crypto map policy enabled notification signifies that the
device validated the crypto map policy. configuration is considered
as active and can be used by Isakmp daemon, or IPSec manual keying.
oacIPSecCpolDisabled
.1.3.6.1.4.1.13191.10.3.1.4.1.6
An IPSec crypto map policy disabled notification signifies that the
device did not validate the crypto map policy. Configuration is considered
as inactive and can not be used by Isakmp or manual IPSec manual keying.
oacIPSecHwModuleDown
.1.3.6.1.4.1.13191.10.3.1.4.1.7
An IPSec hardware module down notification signifies that the
device can not use any hardware encryption module, because it is
not activated, or it is not present on the device.
oacISAKMPBadProposal
.1.3.6.1.4.1.13191.10.3.1.4.2.1
An ISAKMP bad proposal notification signifies that the device
did not validate proposal for IPSec phase 1 with a remote peer.
oacISAKMPDeadPeerDetected
.1.3.6.1.4.1.13191.10.3.1.4.2.10
An ISAKMP Dead Peer detection signifies that the device
detected a DPD when using ISAKMP keepalive.
oacISAKMPNoResponse
.1.3.6.1.4.1.13191.10.3.1.4.2.2
An ISAKMP No Response notification signifies that the device
was exchanging ISAKMP information with a remote ISAKMP peer,
and the peer did not give any answer to the device.
oacISAKMPConnectionEstablished
.1.3.6.1.4.1.13191.10.3.1.4.2.3
An ISAKMP Connection established notification signifies
that the device established an ISAKMP connection with
a remote ISAKMP device.
oacISAKMPConnectionRemoved
.1.3.6.1.4.1.13191.10.3.1.4.2.4
An ISAKMP Connection removed notification signifies
that the device removed an ISAKMP connection with
a remote ISAKMP device, because the lifetime of the connection
reached the limit, or a reset has been carried out on the device,
either by using clear crypto isakmp sa, or by shutting down the
IPSec working interface.
oacISAMPIPSecConnectionEstablished
.1.3.6.1.4.1.13191.10.3.1.4.2.5
An ISAKMP IPSec Connection established notification signifies that
the ISAKMP daemon of the device successfully created an IPSec tunnel between
two ISAKMP peers.
oacISAKMPIPSecConnectionRemoved
.1.3.6.1.4.1.13191.10.3.1.4.2.6
An ISAKMP IPSec Connection removed notification signifies that
the ISAKMP daemon of the device removed an IPSec connection, either because
the lifetime of the IPSec session reached the limit, or because
a reset has been carried out on the IPSec working interface of
the device.
oacISAKMPUnknownPeer
.1.3.6.1.4.1.13191.10.3.1.4.2.7
An ISAKMP unknown peer notification signifies that the device
received an unknown isakmp request and did not process it.
oacISAKMPNotificationMsgReceived
.1.3.6.1.4.1.13191.10.3.1.4.2.8
An ISAKMP notification message received notification signifies
that the device received a notification from a known ISAKMP peer.
oacISAKMPNotificationMsgSent
.1.3.6.1.4.1.13191.10.3.1.4.2.9
An ISAKMP notification message sent notification signifies
that the device sent a notification to a known ISAKMP peer.
Generally, a sent notification is due to a problem on the
ISAKMP connection between two ISAKMP peers. For example,
if received packet is malformed, a notification message is
sent.