OID reference
1.3.6.1.4.1.2076.14.1.8
This table gives the IP address and SPI mappings present in the NAT table. This is nothing but the NAT translation table for the IPSec Traffic. Rows are automatically created and deleted by NAT module. User can also delete rows using Rowstatus field.
Identification
{1 3 6 1 4 1 2076 14 1 8}
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
The displayed source records contain one distinct definition. Compare its source records.
natIPSecSessionTable OBJECT-TYPE
SYNTAX SEQUENCE OF NatIPSecSessionEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table gives the IP address and SPI
mappings present in the NAT table. This is nothing but the NAT
translation table for the IPSec Traffic. Rows are automatically
created and deleted by NAT module.
User can also delete rows using Rowstatus field."
::= { nat 8 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
This table gives the IP address and SPI mappings present in the NAT table. This is nothing but the NAT translation table for the IPSec Traffic. Rows are automatically created and deleted by NAT module. User can also delete rows using Rowstatus field.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Belden, GarrettCom and Hirschmann IT official standalone MIBs
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: natIPSecSessionTable
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"natIPSecSessionTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"NatIPSecSessionEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"This table gives the IP address and SPI mappings present in the NAT table. This is nothing but the NAT translation table for the IPSec Traffic. Rows are automatically created and deleted by NAT module. User can also delete rows using Rowstatus field.\"",
"::=",
"{",
"nat",
"8",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"NatIPSecSessionEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This table gives the IP address and SPI mappings present in the NAT table. This is nothing but the NAT translation table for the IPSec Traffic. Rows are automatically created and deleted by NAT module. User can also delete rows using Rowstatus field."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: FutureNat-MIB
See published definition above
{'SNMPv2-TC': ['RowStatus', 'DisplayString', 'TimeStamp', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Counter32', 'enterprises', 'IpAddress']}Related source files and packages:
Module: FutureNat-MIB
{'SNMPv2-TC': ['RowStatus', 'DisplayString', 'TimeStamp', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Counter32', 'enterprises', 'IpAddress']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2076.14.1.8.1 | natIPSecSessionEntry | 8 | 8 |
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2076.14.1.1 | natStatInfo | 19 | 19 | |
| 1.3.6.1.4.1.2076.14.1.2 | natDynamicTransTable | 1 | 9 | |
| 1.3.6.1.4.1.2076.14.1.3 | natGlobalAddressTable | 1 | 5 | |
| 1.3.6.1.4.1.2076.14.1.4 | natLocalAddressTable | 1 | 5 | |
| 1.3.6.1.4.1.2076.14.1.5 | natStaticTable | 1 | 5 | |
| 1.3.6.1.4.1.2076.14.1.6 | natStaticNaptTable | 1 | 10 | |
| 1.3.6.1.4.1.2076.14.1.7 | natIfTable | 1 | 6 | |
| 1.3.6.1.4.1.2076.14.1.9 | natIPSecPendingTable | 1 | 10 | |
| 1.3.6.1.4.1.2076.14.1.10 | natIKESessionTable | 1 | 8 | |
| 1.3.6.1.4.1.2076.14.1.11 | natPortTrigInfoTable | 1 | 6 | |
| 1.3.6.1.4.1.2076.14.1.12 | natPolicyTable | 1 | 6 | |
| 1.3.6.1.4.1.2076.14.1.13 | natRsvdPortTrigInfoTable | 1 | 9 |