OID reference

oemArchIfaceL2Tunneling

1.3.6.1.4.1.13464.1.2.2.3.1.1.1.17

Description

When l2 entities (such as STP bridges) conneted across a VPN network, l2 PDUs need delivering through VPN without being processed.To achieve this, users need enbling l2- tunneling on VPN's edge ports, i.e. ports connected to customer bridges. One 32bits width integer variable is used for each port to represent what ki…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.13464.1.2.2.3.1.1.1 (oemArchIfaceEntry)
Node code
17
Node name
oemArchIfaceL2Tunneling
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.13464.1.2.2.3.1.1.1.17
URN notation
urn:oid:1.3.6.1.4.1.13464.1.2.2.3.1.1.1.17
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 13464 1 2 2 3 1 1 1 17}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) admin(13464) dataCom(1) gbn(2) gbnDevice(2) bcm5600(3) oemArchIface(1) oemArchIfaceTable(1) oemArchIfaceEntry(1) oemArchIfaceL2Tunneling(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) admin(13464) datacom(1) gbn(2) gbnDevice(2) bcm5600(3) oemArchIface(1) oemArchIfaceTable(1) oemArchIfaceEntry(1) oemArchIfaceL2Tunneling(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) greentech(13464) dataCom(1) gbn(2) gbnDevice(2) bcm5600(3) oemArchIface(1) oemArchIfaceTable(1) oemArchIfaceEntry(1) oemArchIfaceL2Tunneling(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) greentech(13464) datacom(1) gbn(2) gbnDevice(2) bcm5600(3) oemArchIface(1) oemArchIfaceTable(1) oemArchIfaceEntry(1) oemArchIfaceL2Tunneling(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) admin(13464) dataCom(1) gbn(2) gbnDevice(2) bcm5600(3) oemArchIface(1) oemArchIfaceTable(1) oemArchIfaceEntry(1) oemArchIfaceL2Tunneling(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) admin(13464) datacom(1) gbn(2) gbnDevice(2) bcm5600(3) oemArchIface(1) oemArchIfaceTable(1) oemArchIfaceEntry(1) oemArchIfaceL2Tunneling(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) greentech(13464) dataCom(1) gbn(2) gbnDevice(2) bcm5600(3) oemArchIface(1) oemArchIfaceTable(1) oemArchIfaceEntry(1) oemArchIfaceL2Tunneling(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) greentech(13464) datacom(1) gbn(2) gbnDevice(2) bcm5600(3) oemArchIface(1) oemArchIfaceTable(1) oemArchIfaceEntry(1) oemArchIfaceL2Tunneling(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) admin(13464) dataCom(1) gbn(2) gbnDevice(2) bcm5600(3) oemArchIface(1) oemArchIfaceTable(1) oemArchIfaceEntry(1) oemArchIfaceL2Tunneling(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) admin(13464) datacom(1) gbn(2) gbnDevice(2) bcm5600(3) oemArchIface(1) oemArchIfaceTable(1) oemArchIfaceEntry(1) oemArchIfaceL2Tunneling(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) greentech(13464) dataCom(1) gbn(2) gbnDevice(2) bcm5600(3) oemArchIface(1) oemArchIfaceTable(1) oemArchIfaceEntry(1) oemArchIfaceL2Tunneling(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) greentech(13464) datacom(1) gbn(2) gbnDevice(2) bcm5600(3) oemArchIface(1) oemArchIfaceTable(1) oemArchIfaceEntry(1) oemArchIfaceL2Tunneling(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) admin(13464) dataCom(1) gbn(2) gbnDevice(2) bcm5600(3) oemArchIface(1) oemArchIfaceTable(1) oemArchIfaceEntry(1) oemArchIfaceL2Tunneling(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) admin(13464) datacom(1) gbn(2) gbnDevice(2) bcm5600(3) oemArchIface(1) oemArchIfaceTable(1) oemArchIfaceEntry(1) oemArchIfaceL2Tunneling(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) greentech(13464) dataCom(1) gbn(2) gbnDevice(2) bcm5600(3) oemArchIface(1) oemArchIfaceTable(1) oemArchIfaceEntry(1) oemArchIfaceL2Tunneling(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) greentech(13464) datacom(1) gbn(2) gbnDevice(2) bcm5600(3) oemArchIface(1) oemArchIfaceTable(1) oemArchIfaceEntry(1) oemArchIfaceL2Tunneling(17)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/13464/1/2/2/3/1/1/1/17
  • /ISO/Identified-Organization/6/1/4/1/13464/1/2/2/3/1/1/1/17
  • /ISO/3/6/1/4/1/13464/1/2/2/3/1/1/1/17
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/13464/dataCom/gbn/gbnDevice/bcm5600/oemArchIface/oemArchIfaceTable/oemArchIfaceEntry/oemArchIfaceL2Tunneling
  • /iso/identified-organization/dod/internet/private/enterprise/13464/datacom/gbn/gbnDevice/bcm5600/oemArchIface/oemArchIfaceTable/oemArchIfaceEntry/oemArchIfaceL2Tunneling
  • /iso/identified-organization/dod/internet/private/enterprise/admin/dataCom/gbn/gbnDevice/bcm5600/oemArchIface/oemArchIfaceTable/oemArchIfaceEntry/oemArchIfaceL2Tunneling
  • /iso/identified-organization/dod/internet/private/enterprise/admin/datacom/gbn/gbnDevice/bcm5600/oemArchIface/oemArchIfaceTable/oemArchIfaceEntry/oemArchIfaceL2Tunneling
  • /iso/identified-organization/dod/internet/private/enterprise/greentech/dataCom/gbn/gbnDevice/bcm5600/oemArchIface/oemArchIfaceTable/oemArchIfaceEntry/oemArchIfaceL2Tunneling
  • /iso/identified-organization/dod/internet/private/enterprise/greentech/datacom/gbn/gbnDevice/bcm5600/oemArchIface/oemArchIfaceTable/oemArchIfaceEntry/oemArchIfaceL2Tunneling
  • /iso/identified-organization/dod/internet/private/enterprises/13464/dataCom/gbn/gbnDevice/bcm5600/oemArchIface/oemArchIfaceTable/oemArchIfaceEntry/oemArchIfaceL2Tunneling
  • /iso/identified-organization/dod/internet/private/enterprises/13464/datacom/gbn/gbnDevice/bcm5600/oemArchIface/oemArchIfaceTable/oemArchIfaceEntry/oemArchIfaceL2Tunneling
  • /iso/identified-organization/dod/internet/private/enterprises/admin/dataCom/gbn/gbnDevice/bcm5600/oemArchIface/oemArchIfaceTable/oemArchIfaceEntry/oemArchIfaceL2Tunneling
  • /iso/identified-organization/dod/internet/private/enterprises/admin/datacom/gbn/gbnDevice/bcm5600/oemArchIface/oemArchIfaceTable/oemArchIfaceEntry/oemArchIfaceL2Tunneling
  • /iso/identified-organization/dod/internet/private/enterprises/greentech/dataCom/gbn/gbnDevice/bcm5600/oemArchIface/oemArchIfaceTable/oemArchIfaceEntry/oemArchIfaceL2Tunneling
  • /iso/identified-organization/dod/internet/private/enterprises/greentech/datacom/gbn/gbnDevice/bcm5600/oemArchIface/oemArchIfaceTable/oemArchIfaceEntry/oemArchIfaceL2Tunneling
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/13464/dataCom/gbn/gbnDevice/bcm5600/oemArchIface/oemArchIfaceTable/oemArchIfaceEntry/oemArchIfaceL2Tunneling
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/13464/datacom/gbn/gbnDevice/bcm5600/oemArchIface/oemArchIfaceTable/oemArchIfaceEntry/oemArchIfaceL2Tunneling
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/admin/dataCom/gbn/gbnDevice/bcm5600/oemArchIface/oemArchIfaceTable/oemArchIfaceEntry/oemArchIfaceL2Tunneling
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/admin/datacom/gbn/gbnDevice/bcm5600/oemArchIface/oemArchIfaceTable/oemArchIfaceEntry/oemArchIfaceL2Tunneling
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current
Allowed ranges
1–63

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 GBNDeviceOEM-MIB, the row index consists of these components in order:

  1. oemArchIfaceUnit (Integer32): one numeric subidentifier for the non-negative value.
  2. oemArchIfacePort (Integer32): one numeric subidentifier for the non-negative value.

An instance has the form .1.3.6.1.4.1.13464.1.2.2.3.1.1.1.17.<oemArchIfaceUnit>.<oemArchIfacePort>. Use values present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.13464.1.2.2.3.1.1.1.17

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.

Available source records contain 3 distinct definitions; some records may not include a definition.

Show 3 published definitions

oemArchIfaceL2Tunneling · current

oemArchIfaceL2Tunneling    OBJECT-TYPE
    	SYNTAX  INTEGER(1..63)
        MAX-ACCESS read-write
        STATUS current
        DESCRIPTION
            "When l2 entities (such as STP bridges) conneted across a VPN network, l2 PDUs need
            delivering through VPN without being processed.To achieve this, users need enbling l2-
            tunneling on VPN's edge ports, i.e. ports connected to customer bridges. One 32bits 
            width integer variable is used for each port to represent what kind of PDUs need tunneling 
            when coming in this ports.Notes, only the six least-significant bits are used here ,each 
            bit corresponds to one protocol, following is the detail:
            	bit0 <----> CDP
            	bit1 <----> LACP
            	bit2 <----> PAGP
            	bit3 <----> STP
            	bit4 <----> UDLD
            	bit5 <----> VTP
            	bit6-bit31 <--> reserved.
            when set one, corresponding PDU tunneling is asserted, deasserted otherwise."
      ::= { oemArchIfaceEntry 17 }

oemArchIfaceL2Tunneling · current

oemArchIfaceL2Tunneling    OBJECT-TYPE
    	SYNTAX  INTEGER(1..63)
        MAX-ACCESS read-write
        STATUS current
        DESCRIPTION
            "When l2 entities (such as STP bridges) conneted across a VPN network, l2 PDUs need
            delivering through VPN without being processed.To achieve this, users need enbling l2-
            tunneling on VPN's edge ports, i.e. ports connected to customer bridges. One 32bits 
            width integer variable is used for each port to represent what kind of PDUs need tunneling 
            when coming in this ports.Notes, only the six least-significant bits are used here ,each 
            bit corresponds to one protocol, following is the detail:
            	bit0 <----> CDP
            	bit1 <----> LACP
            	bit2 <----> PAGP
            	bit3 <----> STP
            	bit4 <----> UDLD
            	bit5 <----> VTP
            	bit6-bit31 <--> reserved.
            when set one, corresponding PDU tunneling is asserted, deasserted otherwise."
            --µ±¶þ²ãЭÒéʵÌåͨ¹ýVPNÍøÂçÏàÁ¬Ê±£¬ÕâЩʵÌåµÄ¶þ²ãЭÒ鱨ÎÄÐèÒªÎÞ¸Ä±äµØ¾­ÓÉVPN͸´«£¬
            --ΪÁËʵÏÖ´ËÄ¿µÄ£¬¾Í±ØÐëÔÚVPNµÄ±ß½ç¶Ë¿Ú¿ªÆô¶þ²ãЭÒéËíµÀ£¬Ã¿¸ö¶Ë¿ÚʹÓÃÒ»¸ö32λµÄÕû
            --ÊýÀ´ÃèÊö¶ÔºÎÖÖЭÒ鿪ÆôËíµÀ¹¦ÄÜ£¬Ä¿Ç°ÎÒÃÇֻʹÓÃ×îµÍµÄ6¸öbit£¬Ã¿¸öbit´ú±íÒ»¸öЭÒé
            --¾ßÌåÈçÏ£ºbit0´ú±íCDPЭÒ飬bit1´ú±íLACPЭÒ飬bit2´ú±íPAGPЭÒ飬bit3´ú±íSTPЭÒ飬
            --bit´ú±íUDLDЭÒ飬bit5´ú±íVTPЭÒ飬bit6~bit31±£Áô²»Ó㬵±¶ÔÓ¦µÄbitÖÃλµÄʱºò£¬±í
            --ʾ¶Ô´ËЭÒ鿪ÆôÁËËíµÀ¹¦ÄÜ
      ::= { oemArchIfaceEntry 17 }

oemArchIfaceL2Tunneling · current

oemArchIfaceL2Tunneling    OBJECT-TYPE
        SYNTAX  INTEGER(1..63)
        MAX-ACCESS read-write
        STATUS current
        DESCRIPTION
            "When l2 entities (such as STP bridges) conneted across a VPN network, l2 PDUs need
            delivering through VPN without being processed.To achieve this, users need enbling l2-
            tunneling on VPN's edge ports, i.e. ports connected to customer bridges. One 32bits
            width integer variable is used for each port to represent what kind of PDUs need tunneling
            when coming in this ports.Notes, only the six least-significant bits are used here ,each
            bit corresponds to one protocol, following is the detail:
                bit0 <----> CDP
                bit1 <----> LACP
                bit2 <----> PAGP
                bit3 <----> STP
                bit4 <----> UDLD
                bit5 <----> VTP
                bit6-bit31 <--> reserved.
            when set one, corresponding PDU tunneling is asserted, deasserted otherwise."
            --µ±¶þ²ãЭÒéʵÌåͨ¹ýVPNÍøÂçÏàÁ¬Ê±£¬ÕâЩʵÌåµÄ¶þ²ãЭÒ鱨ÎÄÐèÒªÎÞ¸Ä±äµØ¾­ÓÉVPN͸´«£¬
            --ΪÁËʵÏÖ´ËÄ¿µÄ£¬¾Í±ØÐëÔÚVPNµÄ±ß½ç¶Ë¿Ú¿ªÆô¶þ²ãЭÒéËíµÀ£¬Ã¿¸ö¶Ë¿ÚʹÓÃÒ»¸ö32λµÄÕû
            --ÊýÀ´ÃèÊö¶ÔºÎÖÖЭÒ鿪ÆôËíµÀ¹¦ÄÜ£¬Ä¿Ç°ÎÒÃÇֻʹÓÃ×îµÍµÄ6¸öbit£¬Ã¿¸öbit´ú±íÒ»¸öЭÒé
            --¾ßÌåÈçÏ£ºbit0´ú±íCDPЭÒ飬bit1´ú±íLACPЭÒ飬bit2´ú±íPAGPЭÒ飬bit3´ú±íSTPЭÒ飬
            --bit´ú±íUDLDЭÒ飬bit5´ú±íVTPЭÒ飬bit6~bit31±£Áô²»Ó㬵±¶ÔÓ¦µÄbitÖÃλµÄʱºò£¬±í
            --ʾ¶Ô´ËЭÒ鿪ÆôÁËËíµÀ¹¦ÄÜ
      ::= { oemArchIfaceEntry 17 }

Meaning

Descriptions

1 unique

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

When l2 entities (such as STP bridges) conneted across a VPN network, l2 PDUs need delivering through VPN without being processed.To achieve this, users need enbling l2- tunneling on VPN's edge ports, i.e. ports connected to customer bridges. One 32bits width integer variable is used for each port to represent what kind of PDUs need tunneling when coming in this ports.Notes, only the six least-significant bits are used here ,each bit corresponds to one protocol, following is the detail: bit0 <----> CDP bit1 <----> LACP bit2 <----> PAGP bit3 <----> STP bit4 <----> UDLD bit5 <----> VTP bit6-bit31 <--> reserved. when set one, corresponding PDU tunneling is asserted, deasserted otherwise.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)FS.COM 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), FS.COM MIB copies (LibreNMS/Observium Community)1 record · 3 sources

Description 1

oemArchIfaceL2Tunneling · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), FS.COM MIB copies (LibreNMS/Observium Community)3 sources

Status in source: current.

Names: oemArchIfaceL2Tunneling

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "oemArchIfaceL2Tunneling",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "1",
    ".",
    ".",
    "63",
    ")",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"When l2 entities (such as STP bridges) conneted across a VPN network, l2 PDUs need delivering through VPN without being processed.To achieve this, users need enbling l2- tunneling on VPN's edge ports, i.e. ports connected to customer bridges. One 32bits width integer variable is used for each port to represent what kind of PDUs need tunneling when coming in this ports.Notes, only the six least-significant bits are used here ,each bit corresponds to one protocol, following is the detail: bit0 <----> CDP bit1 <----> LACP bit2 <----> PAGP bit3 <----> STP bit4 <----> UDLD bit5 <----> VTP bit6-bit31 <--> reserved. when set one, corresponding PDU tunneling is asserted, deasserted otherwise.\"",
    "::=",
    "{",
    "oemArchIfaceEntry",
    "17",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            1,
            63
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "When l2 entities (such as STP bridges) conneted across a VPN network, l2 PDUs need delivering through VPN without being processed.To achieve this, users need enbling l2- tunneling on VPN's edge ports, i.e. ports connected to customer bridges. One 32bits width integer variable is used for each port to represent what kind of PDUs need tunneling when coming in this ports.Notes, only the six least-significant bits are used here ,each bit corresponds to one protocol, following is the detail: bit0 <----> CDP bit1 <----> LACP bit2 <----> PAGP bit3 <----> STP bit4 <----> UDLD bit5 <----> VTP bit6-bit31 <--> reserved. when set one, corresponding PDU tunneling is asserted, deasserted otherwise."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.13464)

Ke Qin

Siblings (18)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.13464.1.2.2.3.1.1.1.1 oemArchIfaceUnit00
1.3.6.1.4.1.13464.1.2.2.3.1.1.1.2 oemArchIfacePort00
1.3.6.1.4.1.13464.1.2.2.3.1.1.1.3 oemArchIfaceLLWHPort00
1.3.6.1.4.1.13464.1.2.2.3.1.1.1.4 oemArchIfaceIfIndex00
1.3.6.1.4.1.13464.1.2.2.3.1.1.1.5 oemArchIfaceName00
1.3.6.1.4.1.13464.1.2.2.3.1.1.1.6 oemArchIfaceEnable00
1.3.6.1.4.1.13464.1.2.2.3.1.1.1.7 oemArchIfaceSTPEnable00
1.3.6.1.4.1.13464.1.2.2.3.1.1.1.8 oemArchIfaceLink00
1.3.6.1.4.1.13464.1.2.2.3.1.1.1.9 oemArchIfaceDuplexSpeedSet00
1.3.6.1.4.1.13464.1.2.2.3.1.1.1.10 oemArchIfaceDuplexSpeedGet00
1.3.6.1.4.1.13464.1.2.2.3.1.1.1.11 oemArchIfacePortLoop00
1.3.6.1.4.1.13464.1.2.2.3.1.1.1.12 oemArchIfaceFlowControl00
1.3.6.1.4.1.13464.1.2.2.3.1.1.1.13 oemArchIfaceTxVlanTagPkts00
1.3.6.1.4.1.13464.1.2.2.3.1.1.1.14 oemArchIfaceTxL3Pkts00
1.3.6.1.4.1.13464.1.2.2.3.1.1.1.15 oemArchIfaceTxL3AbortedPkts00
1.3.6.1.4.1.13464.1.2.2.3.1.1.1.16 oemArchIfaceRxIpInHdrErrors00
1.3.6.1.4.1.13464.1.2.2.3.1.1.1.18 oemArchIfaceLinkUpTime00
1.3.6.1.4.1.13464.1.2.2.3.1.1.1.19 oemArchIfaceMasterMode00