All MIBs › IPSEC-ISAKMP-IKE-DOI-TC
Organization: Shiva
Last Updated: 1999-07-13
Category: Textual Conventions and Registries, VPN and Security
Description:
Shiva MIB of textual conventions for IPsec/ISAKMP/IKE domain of interpretation (DOI), defining the enumerated types used in IKE negotiation parameters.
Imported Objects
From RFC1213-MIB
| mib-2 |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| Unsigned32 | |
| experimental |
From SNMPv2-TC
| TEXTUAL-CONVENTION |
From WATCHGUARD-MIB
| watchguard | OBJECT-IDENTITY |
What Is IPSEC-ISAKMP-IKE-DOI-TC?
IPSEC-ISAKMP-IKE-DOI-TC is a vendor-specific (Shiva-authored) textual-conventions MIB that defines enumerated types for IPSec Domain of Interpretation, ISAKMP, and IKE protocol parameters as registered by IANA (per RFCs 2407-2409). It belongs to the foundational/infrastructure category of SNMP MIBs supporting IPSec VPN management rather than being a monitoring MIB in its own right. It does not expose any live data tables; instead it supplies shared enumerated textual conventions - encryption algorithm identifiers, authentication method codes, and DOI-specific values - that other IPSec/IKE-related MIBs use for consistent typing of their objects. Consequently, there is no IPSEC-ISAKMP-IKE-DOI-TC OID list of pollable instances to browse, since the module contributes only reusable type definitions rather than object identifiers carrying runtime values. Because it defines no runtime objects, it plays no direct role in monitoring hardware or software status by itself, but it underlies any IPSec/IKE MIB (such as a Security Association monitoring MIB) needing standardized negotiation-parameter values. It is deployed implicitly wherever an SNMP agent implements IPSec/IKE MIBs referencing these IANA-managed conventions, typically on VPN gateways and firewalls.
IPNetwork Monitor allows you to monitor SNMP objects defined in IPSEC-ISAKMP-IKE-DOI-TC. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- vendor-neutral IANA-managed textual conventions, referenced by IPSec/IKE-capable VPN gateways and firewalls
Monitoring Examples
This is a textual-convention module with no runtime data objects of its own, so there is no realistic polling scenario to describe; its enumerated ISAKMP/IKE/DOI type conventions are instead imported by other IPSec-related MIBs (such as a Security Association monitoring MIB) to encode negotiation parameters consistently.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| ipsecIsakmpIkeDoiTC | 1.3.6.1.4.1.3097.100 | The MIB module which defines the textual conventions used in IPSEC MIBs. This includes Internet DOI numbers defined in RFC 2407, ISAKMP numbers defined in RFC 2408, and IKE numbers defined in RFC 2409. These Textual Conventions are defined in a seperate MIB module since they are protocol numbers managed by the IANA. Revision control after publication will be under the authority of the IANA. |
RFC description
Shiva IPsec/ISAKMP/IKE domain of interpretation (DOI) textual conventions MIB defining enumerated types for IKE negotiation parameters.
Start monitoring Vendor-neutral IANA-managed textual conventions (IPsec/IKE VPN gateway or firewall) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.