OID reference

vpnManualOutboundSpi

1.3.6.1.4.1.3955.2.4.1.1.25

Description

The SPI(Security Parameter Index) is carried in the ESP header. This enables the receiver to select the SA, under which a packet should be processed. The SPI is a 32-bit value. Both decimal and hexadecimal values are acceptable. e.g. [987654321] or [0x3ade68b1]. Each tunnel must have unique an Inbound SPI and Outbound…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.3955.2.4.1.1 (vpnIpsecEntry)
Node code
25
Node name
vpnManualOutboundSpi
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.3955.2.4.1.1.25
URN notation
urn:oid:1.3.6.1.4.1.3955.2.4.1.1.25
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 3955 2 4 1 1 25}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) linksys(3955) products(2) vpnMgt(4) vpnIpsecTable(1) vpnIpsecEntry(1) vpnManualOutboundSpi(25)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) linksys(3955) management(2) vpnMgt(4) vpnIpsecTable(1) vpnIpsecEntry(1) vpnManualOutboundSpi(25)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) linksys(3955) products(2) vpnMgt(4) vpnIpsecTable(1) vpnIpsecEntry(1) vpnManualOutboundSpi(25)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) linksys(3955) management(2) vpnMgt(4) vpnIpsecTable(1) vpnIpsecEntry(1) vpnManualOutboundSpi(25)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) linksys(3955) products(2) vpnMgt(4) vpnIpsecTable(1) vpnIpsecEntry(1) vpnManualOutboundSpi(25)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) linksys(3955) management(2) vpnMgt(4) vpnIpsecTable(1) vpnIpsecEntry(1) vpnManualOutboundSpi(25)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) linksys(3955) products(2) vpnMgt(4) vpnIpsecTable(1) vpnIpsecEntry(1) vpnManualOutboundSpi(25)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) linksys(3955) management(2) vpnMgt(4) vpnIpsecTable(1) vpnIpsecEntry(1) vpnManualOutboundSpi(25)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) linksys(3955) products(2) vpnMgt(4) vpnIpsecTable(1) vpnIpsecEntry(1) vpnManualOutboundSpi(25)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) linksys(3955) management(2) vpnMgt(4) vpnIpsecTable(1) vpnIpsecEntry(1) vpnManualOutboundSpi(25)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) linksys(3955) products(2) vpnMgt(4) vpnIpsecTable(1) vpnIpsecEntry(1) vpnManualOutboundSpi(25)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) linksys(3955) management(2) vpnMgt(4) vpnIpsecTable(1) vpnIpsecEntry(1) vpnManualOutboundSpi(25)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) linksys(3955) products(2) vpnMgt(4) vpnIpsecTable(1) vpnIpsecEntry(1) vpnManualOutboundSpi(25)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) linksys(3955) management(2) vpnMgt(4) vpnIpsecTable(1) vpnIpsecEntry(1) vpnManualOutboundSpi(25)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) linksys(3955) products(2) vpnMgt(4) vpnIpsecTable(1) vpnIpsecEntry(1) vpnManualOutboundSpi(25)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) linksys(3955) management(2) vpnMgt(4) vpnIpsecTable(1) vpnIpsecEntry(1) vpnManualOutboundSpi(25)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/3955/2/4/1/1/25
  • /ISO/Identified-Organization/6/1/4/1/3955/2/4/1/1/25
  • /ISO/3/6/1/4/1/3955/2/4/1/1/25
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/linksys/products/vpnMgt/vpnIpsecTable/vpnIpsecEntry/vpnManualOutboundSpi
  • /iso/identified-organization/dod/internet/private/enterprise/linksys/management/vpnMgt/vpnIpsecTable/vpnIpsecEntry/vpnManualOutboundSpi
  • /iso/identified-organization/dod/internet/private/enterprises/linksys/products/vpnMgt/vpnIpsecTable/vpnIpsecEntry/vpnManualOutboundSpi
  • /iso/identified-organization/dod/internet/private/enterprises/linksys/management/vpnMgt/vpnIpsecTable/vpnIpsecEntry/vpnManualOutboundSpi
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/linksys/products/vpnMgt/vpnIpsecTable/vpnIpsecEntry/vpnManualOutboundSpi
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/linksys/management/vpnMgt/vpnIpsecTable/vpnIpsecEntry/vpnManualOutboundSpi
  • /iso/identified-organization/dod/internet/private/vendor-objects/linksys/products/vpnMgt/vpnIpsecTable/vpnIpsecEntry/vpnManualOutboundSpi
  • /iso/identified-organization/dod/internet/private/vendor-objects/linksys/management/vpnMgt/vpnIpsecTable/vpnIpsecEntry/vpnManualOutboundSpi
  • /iso/org/dod/internet/private/enterprise/linksys/products/vpnMgt/vpnIpsecTable/vpnIpsecEntry/vpnManualOutboundSpi
  • /iso/org/dod/internet/private/enterprise/linksys/management/vpnMgt/vpnIpsecTable/vpnIpsecEntry/vpnManualOutboundSpi
  • /iso/org/dod/internet/private/enterprises/linksys/products/vpnMgt/vpnIpsecTable/vpnIpsecEntry/vpnManualOutboundSpi
  • /iso/org/dod/internet/private/enterprises/linksys/management/vpnMgt/vpnIpsecTable/vpnIpsecEntry/vpnManualOutboundSpi
  • /iso/org/dod/internet/private/ldap-enterprise/linksys/products/vpnMgt/vpnIpsecTable/vpnIpsecEntry/vpnManualOutboundSpi
  • /iso/org/dod/internet/private/ldap-enterprise/linksys/management/vpnMgt/vpnIpsecTable/vpnIpsecEntry/vpnManualOutboundSpi
  • /iso/org/dod/internet/private/vendor-objects/linksys/products/vpnMgt/vpnIpsecTable/vpnIpsecEntry/vpnManualOutboundSpi
  • /iso/org/dod/internet/private/vendor-objects/linksys/management/vpnMgt/vpnIpsecTable/vpnIpsecEntry/vpnManualOutboundSpi
  • Additional combinations skipped.

SNMP properties

Value type
DisplayString
Maximum access defined by MIB
read-write
Status in MIB
mandatory
Allowed size (octets)
0–9

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In LINKSYS-MODEL-MIB, the row index vpnTunnelIndex is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.3955.2.4.1.1.25.<vpnTunnelIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

Published row index: vpnTunnelIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.3955.2.4.1.1.25

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

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.

vpnManualOutboundSpi OBJECT-TYPE
        SYNTAX	DisplayString (SIZE(0..9))
        ACCESS	read-write
        STATUS	mandatory
        DESCRIPTION
                "The SPI(Security Parameter Index) is carried in the ESP
                header. This enables the receiver to select the SA, under
                which a packet should be processed. The SPI is a 32-bit
                value. Both decimal and hexadecimal values are acceptable.
                e.g. [987654321] or [0x3ade68b1]. Each tunnel must have
                unique an Inbound SPI and Outbound SPI. No two tunnels
                share the same SPI. Notice that Inbound SPI must match
                the other router's Outbound SPI, and vice versa."
        ::= { vpnIpsecEntry 25 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

The SPI(Security Parameter Index) is carried in the ESP header. This enables the receiver to select the SA, under which a packet should be processed. The SPI is a 32-bit value. Both decimal and hexadecimal values are acceptable. e.g. [987654321] or [0x3ade68b1]. Each tunnel must have unique an Inbound SPI and Outbound SPI. No two tunnels share the same SPI. Notice that Inbound SPI must match the other router's Outbound SPI, and vice versa.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

vpnManualOutboundSpi · mandatoryMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: mandatory.

Names: vpnManualOutboundSpi

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "vpnManualOutboundSpi",
    "OBJECT-TYPE",
    "SYNTAX",
    "DisplayString",
    "(",
    "SIZE",
    "(",
    "0",
    ".",
    ".",
    "9",
    ")",
    ")",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"The SPI(Security Parameter Index) is carried in the ESP header. This enables the receiver to select the SA, under which a packet should be processed. The SPI is a 32-bit value. Both decimal and hexadecimal values are acceptable. e.g. [987654321] or [0x3ade68b1]. Each tunnel must have unique an Inbound SPI and Outbound SPI. No two tunnels share the same SPI. Notice that Inbound SPI must match the other router's Outbound SPI, and vice versa.\"",
    "::=",
    "{",
    "vpnIpsecEntry",
    "25",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "DisplayString",
      [
        "octetStringSubType",
        [
          [
            0,
            9
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "The SPI(Security Parameter Index) is carried in the ESP header. This enables the receiver to select the SA, under which a packet should be processed. The SPI is a 32-bit value. Both decimal and hexadecimal values are acceptable. e.g. [987654321] or [0x3ade68b1]. Each tunnel must have unique an Inbound SPI and Outbound SPI. No two tunnels share the same SPI. Notice that Inbound SPI must match the other router's Outbound SPI, and vice versa."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.3955)

LaPolla Greg

Siblings (25)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.3955.2.4.1.1.1 vpnTunnelIndex00
1.3.6.1.4.1.3955.2.4.1.1.2 vpnTunnelState00
1.3.6.1.4.1.3955.2.4.1.1.3 vpnTunnelName00
1.3.6.1.4.1.3955.2.4.1.1.4 vpnLocalIdType00
1.3.6.1.4.1.3955.2.4.1.1.5 vpnLocalIp00
1.3.6.1.4.1.3955.2.4.1.1.6 vpnLocalSubnet00
1.3.6.1.4.1.3955.2.4.1.1.7 vpnLocalSubnetMask00
1.3.6.1.4.1.3955.2.4.1.1.8 vpnLocalRangeBeg00
1.3.6.1.4.1.3955.2.4.1.1.9 vpnLocalRangeEnd00
1.3.6.1.4.1.3955.2.4.1.1.10 vpnRemoteIdType00
1.3.6.1.4.1.3955.2.4.1.1.11 vpnRemoteIp00
1.3.6.1.4.1.3955.2.4.1.1.12 vpnRemoteSubnet00
1.3.6.1.4.1.3955.2.4.1.1.13 vpnRemoteSubnetMask00
1.3.6.1.4.1.3955.2.4.1.1.14 vpnRemoteRangeBeg00
1.3.6.1.4.1.3955.2.4.1.1.15 vpnRemoteRangeEnd00
1.3.6.1.4.1.3955.2.4.1.1.16 vpnRemoteSecurityGateway00
1.3.6.1.4.1.3955.2.4.1.1.17 vpnEspEncrypt00
1.3.6.1.4.1.3955.2.4.1.1.18 vpnEspAuth00
1.3.6.1.4.1.3955.2.4.1.1.19 vpnKeyMethod00
1.3.6.1.4.1.3955.2.4.1.1.20 vpnIsakmpPfs00
1.3.6.1.4.1.3955.2.4.1.1.21 vpnIsakmpPreSharedKey00
1.3.6.1.4.1.3955.2.4.1.1.22 vpnManualEncryptKey00
1.3.6.1.4.1.3955.2.4.1.1.23 vpnManualAuthKey00
1.3.6.1.4.1.3955.2.4.1.1.24 vpnManualInboundSpi00
1.3.6.1.4.1.3955.2.4.1.1.26 vpnTunnelStatus00