OID reference

l2tpPortEncapType

1.3.6.1.4.1.29601.2.108.1.2.1.1.3

Description

This object specifies the type of the packet to be traversed through the tunnel. Encapsulation type can be (port based / port,vlan / QinQ /QinAny) Port based - All the packet ingressed on this (port, attachment circuit) will be tunneled with L2TPv3 header encapsulation. Port-vlan - The packets ingressed on this port w…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.29601.2.108.1.2.1.1 (l2tpPortEntry)
Node code
3
Node name
l2tpPortEncapType
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.29601.2.108.1.2.1.1.3
URN notation
urn:oid:1.3.6.1.4.1.29601.2.108.1.2.1.1.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 29601 2 108 1 2 1 1 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 futureL2tpMIB(108) l2tp(1) l2tpPort(2) l2tpPortTable(1) l2tpPortEntry(1) l2tpPortEncapType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 futureL2tpMIB(108) l2tp(1) l2tpPort(2) l2tpPortTable(1) l2tpPortEntry(1) l2tpPortEncapType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 futureL2tpMIB(108) l2tp(1) l2tpPort(2) l2tpPortTable(1) l2tpPortEntry(1) l2tpPortEncapType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 futureL2tpMIB(108) l2tp(1) l2tpPort(2) l2tpPortTable(1) l2tpPortEntry(1) l2tpPortEncapType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 futureL2tpMIB(108) l2tp(1) l2tpPort(2) l2tpPortTable(1) l2tpPortEntry(1) l2tpPortEncapType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 futureL2tpMIB(108) l2tp(1) l2tpPort(2) l2tpPortTable(1) l2tpPortEntry(1) l2tpPortEncapType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 futureL2tpMIB(108) l2tp(1) l2tpPort(2) l2tpPortTable(1) l2tpPortEntry(1) l2tpPortEncapType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 futureL2tpMIB(108) l2tp(1) l2tpPort(2) l2tpPortTable(1) l2tpPortEntry(1) l2tpPortEncapType(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 futureL2tpMIB(108) l2tp(1) l2tpPort(2) l2tpPortTable(1) l2tpPortEntry(1) l2tpPortEncapType(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 futureL2tpMIB(108) l2tp(1) l2tpPort(2) l2tpPortTable(1) l2tpPortEntry(1) l2tpPortEncapType(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 futureL2tpMIB(108) l2tp(1) l2tpPort(2) l2tpPortTable(1) l2tpPortEntry(1) l2tpPortEncapType(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 futureL2tpMIB(108) l2tp(1) l2tpPort(2) l2tpPortTable(1) l2tpPortEntry(1) l2tpPortEncapType(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 futureL2tpMIB(108) l2tp(1) l2tpPort(2) l2tpPortTable(1) l2tpPortEntry(1) l2tpPortEncapType(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 futureL2tpMIB(108) l2tp(1) l2tpPort(2) l2tpPortTable(1) l2tpPortEntry(1) l2tpPortEncapType(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 futureL2tpMIB(108) l2tp(1) l2tpPort(2) l2tpPortTable(1) l2tpPortEntry(1) l2tpPortEncapType(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 futureL2tpMIB(108) l2tp(1) l2tpPort(2) l2tpPortTable(1) l2tpPortEntry(1) l2tpPortEncapType(3)}
OID-IRI notation
  • /1/3/6/1/4/1/29601/2/108/1/2/1/1/3
  • /ISO/Identified-Organization/6/1/4/1/29601/2/108/1/2/1/1/3
  • /ISO/3/6/1/4/1/29601/2/108/1/2/1/1/3
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/29601/2/futureL2tpMIB/l2tp/l2tpPort/l2tpPortTable/l2tpPortEntry/l2tpPortEncapType
  • /iso/identified-organization/dod/internet/private/enterprises/29601/2/futureL2tpMIB/l2tp/l2tpPort/l2tpPortTable/l2tpPortEntry/l2tpPortEncapType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/29601/2/futureL2tpMIB/l2tp/l2tpPort/l2tpPortTable/l2tpPortEntry/l2tpPortEncapType
  • /iso/identified-organization/dod/internet/private/vendor-objects/29601/2/futureL2tpMIB/l2tp/l2tpPort/l2tpPortTable/l2tpPortEntry/l2tpPortEncapType
  • /iso/org/dod/internet/private/enterprise/29601/2/futureL2tpMIB/l2tp/l2tpPort/l2tpPortTable/l2tpPortEntry/l2tpPortEncapType
  • /iso/org/dod/internet/private/enterprises/29601/2/futureL2tpMIB/l2tp/l2tpPort/l2tpPortTable/l2tpPortEntry/l2tpPortEncapType
  • /iso/org/dod/internet/private/ldap-enterprise/29601/2/futureL2tpMIB/l2tp/l2tpPort/l2tpPortTable/l2tpPortEntry/l2tpPortEncapType
  • /iso/org/dod/internet/private/vendor-objects/29601/2/futureL2tpMIB/l2tp/l2tpPort/l2tpPortTable/l2tpPortEntry/l2tpPortEncapType
  • /iso/iso-identified-organization/dod/internet/private/enterprise/29601/2/futureL2tpMIB/l2tp/l2tpPort/l2tpPortTable/l2tpPortEntry/l2tpPortEncapType
  • /iso/iso-identified-organization/dod/internet/private/enterprises/29601/2/futureL2tpMIB/l2tp/l2tpPort/l2tpPortTable/l2tpPortEntry/l2tpPortEncapType
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/29601/2/futureL2tpMIB/l2tp/l2tpPort/l2tpPortTable/l2tpPortEntry/l2tpPortEncapType
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/29601/2/futureL2tpMIB/l2tp/l2tpPort/l2tpPortTable/l2tpPortEntry/l2tpPortEncapType
  • /iso/iso-organization/dod/internet/private/enterprise/29601/2/futureL2tpMIB/l2tp/l2tpPort/l2tpPortTable/l2tpPortEntry/l2tpPortEncapType
  • /iso/iso-organization/dod/internet/private/enterprises/29601/2/futureL2tpMIB/l2tp/l2tpPort/l2tpPortTable/l2tpPortEntry/l2tpPortEncapType
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/29601/2/futureL2tpMIB/l2tp/l2tpPort/l2tpPortTable/l2tpPortEntry/l2tpPortEncapType
  • /iso/iso-organization/dod/internet/private/vendor-objects/29601/2/futureL2tpMIB/l2tp/l2tpPort/l2tpPortTable/l2tpPortEntry/l2tpPortEncapType

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-create
Status in MIB
current

Enumerated values

ValueName
1port
2port-vlan
3qinq
4qinAny

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 FutureL2tp-MIB, the row index l2tpPortIfIndex 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.29601.2.108.1.2.1.1.3.<l2tpPortIfIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.29601.2.108.1.2.1.1.3

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.

l2tpPortEncapType OBJECT-TYPE
   SYNTAX         INTEGER {
                            port(1),
                            port-vlan(2),
                            qinq(3),
                            qinAny(4)
                          }
   MAX-ACCESS     read-create
   STATUS         current
   DESCRIPTION
       "This object specifies the type of the packet to be traversed through the tunnel.
    Encapsulation type can be (port based / port,vlan / QinQ /QinAny)

    Port based - All the packet ingressed on this (port, attachment
    circuit) will be tunneled with L2TPv3 header encapsulation.

    Port-vlan - The packets ingressed on this port which matches the
    (outer-vlan, attachment-circuit) will be tunneled with L2TPv3 header encapsulation.

    Qinq - The packets ingressed on this port which matches with 
    (configured inner-vlan, configured outer-vlan, attachment circuit) will be tunneled
    with L2TPv3 header encapsulation. if the EtherType of the VLAN is 8100, this configuration 
    will be used.

    QinAny - The packets ingressed on this port which matches with 
    (configured inner-vlan, configured outer-vlan, attachment circuit) will be tunneled
    with L2TPv3 header encapsulation. if the EtherType of the outer-VLAN is 88a8, and
    the inner-vlan is 8100, then this configuration will be used."
   ::= { l2tpPortEntry 3 }

Meaning

Descriptions

1 unique

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

This object specifies the type of the packet to be traversed through the tunnel. Encapsulation type can be (port based / port,vlan / QinQ /QinAny) Port based - All the packet ingressed on this (port, attachment circuit) will be tunneled with L2TPv3 header encapsulation. Port-vlan - The packets ingressed on this port which matches the (outer-vlan, attachment-circuit) will be tunneled with L2TPv3 header encapsulation. Qinq - The packets ingressed on this port which matches with (configured inner-vlan, configured outer-vlan, attachment circuit) will be tunneled with L2TPv3 header encapsulation. if the EtherType of the VLAN is 8100, this configuration will be used. QinAny - The packets ingressed on this port which matches with (configured inner-vlan, configured outer-vlan, attachment circuit) will be tunneled with L2TPv3 header encapsulation. if the EtherType of the outer-VLAN is 88a8, and the inner-vlan is 8100, then this configuration will be used.

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

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

Status in source: current.

Names: l2tpPortEncapType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "l2tpPortEncapType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "port",
    "(",
    "1",
    ")",
    ",",
    "port-vlan",
    "(",
    "2",
    ")",
    ",",
    "qinq",
    "(",
    "3",
    ")",
    ",",
    "qinAny",
    "(",
    "4",
    ")",
    "}",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object specifies the type of the packet to be traversed through the tunnel. Encapsulation type can be (port based / port,vlan / QinQ /QinAny) Port based - All the packet ingressed on this (port, attachment circuit) will be tunneled with L2TPv3 header encapsulation. Port-vlan - The packets ingressed on this port which matches the (outer-vlan, attachment-circuit) will be tunneled with L2TPv3 header encapsulation. Qinq - The packets ingressed on this port which matches with (configured inner-vlan, configured outer-vlan, attachment circuit) will be tunneled with L2TPv3 header encapsulation. if the EtherType of the VLAN is 8100, this configuration will be used. QinAny - The packets ingressed on this port which matches with (configured inner-vlan, configured outer-vlan, attachment circuit) will be tunneled with L2TPv3 header encapsulation. if the EtherType of the outer-VLAN is 88a8, and the inner-vlan is 8100, then this configuration will be used.\"",
    "::=",
    "{",
    "l2tpPortEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "port",
            1
          ],
          [
            "port-vlan",
            2
          ],
          [
            "qinq",
            3
          ],
          [
            "qinAny",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object specifies the type of the packet to be traversed through the tunnel. Encapsulation type can be (port based / port,vlan / QinQ /QinAny) Port based - All the packet ingressed on this (port, attachment circuit) will be tunneled with L2TPv3 header encapsulation. Port-vlan - The packets ingressed on this port which matches the (outer-vlan, attachment-circuit) will be tunneled with L2TPv3 header encapsulation. Qinq - The packets ingressed on this port which matches with (configured inner-vlan, configured outer-vlan, attachment circuit) will be tunneled with L2TPv3 header encapsulation. if the EtherType of the VLAN is 8100, this configuration will be used. QinAny - The packets ingressed on this port which matches with (configured inner-vlan, configured outer-vlan, attachment circuit) will be tunneled with L2TPv3 header encapsulation. if the EtherType of the outer-VLAN is 88a8, and the inner-vlan is 8100, then this configuration will be used."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.29601)

Arpna Gupta

Siblings (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.29601.2.108.1.2.1.1.1 l2tpPortIfIndex00
1.3.6.1.4.1.29601.2.108.1.2.1.1.2 l2tpEnabledStatus00
1.3.6.1.4.1.29601.2.108.1.2.1.1.4 l2tpPortRowStatus00