OID reference

interfaceReference

1.3.6.1.4.1.5504.2.5.42.1.11.1.3

Description

This table should contain a single entry for each available LAN and WAN interface. For a WAN interface, this parameter is the full hierarchical parameter name of a particular WANConnectionDevice. A WANConnectionDevice is considered available (included in this table) only if it supports layer-2 bridged traffic. That is…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.5504.2.5.42.1.11.1 (availableInterfaceEntry)
Node code
3
Node name
interfaceReference
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.5504.2.5.42.1.11.1.3
URN notation
urn:oid:1.3.6.1.4.1.5504.2.5.42.1.11.1.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 5504 2 5 42 1 11 1 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneProduct(2) zhoneWtn(5) zhnLayer2Bridging(42) layer2BridgingObjects(1) availableInterfaceTable(11) availableInterfaceEntry(1) interfaceReference(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneProduct(2) zhoneWtn(5) zhnLayer2Bridging(42) layer2BridgingObjects(1) availableInterfaceTable(11) availableInterfaceEntry(1) interfaceReference(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneProduct(2) zhoneWtn(5) zhnLayer2Bridging(42) layer2BridgingObjects(1) availableInterfaceTable(11) availableInterfaceEntry(1) interfaceReference(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneProduct(2) zhoneWtn(5) zhnLayer2Bridging(42) layer2BridgingObjects(1) availableInterfaceTable(11) availableInterfaceEntry(1) interfaceReference(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneProduct(2) zhoneWtn(5) zhnLayer2Bridging(42) layer2BridgingObjects(1) availableInterfaceTable(11) availableInterfaceEntry(1) interfaceReference(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneProduct(2) zhoneWtn(5) zhnLayer2Bridging(42) layer2BridgingObjects(1) availableInterfaceTable(11) availableInterfaceEntry(1) interfaceReference(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneProduct(2) zhoneWtn(5) zhnLayer2Bridging(42) layer2BridgingObjects(1) availableInterfaceTable(11) availableInterfaceEntry(1) interfaceReference(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneProduct(2) zhoneWtn(5) zhnLayer2Bridging(42) layer2BridgingObjects(1) availableInterfaceTable(11) availableInterfaceEntry(1) interfaceReference(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneProduct(2) zhoneWtn(5) zhnLayer2Bridging(42) layer2BridgingObjects(1) availableInterfaceTable(11) availableInterfaceEntry(1) interfaceReference(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneProduct(2) zhoneWtn(5) zhnLayer2Bridging(42) layer2BridgingObjects(1) availableInterfaceTable(11) availableInterfaceEntry(1) interfaceReference(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneProduct(2) zhoneWtn(5) zhnLayer2Bridging(42) layer2BridgingObjects(1) availableInterfaceTable(11) availableInterfaceEntry(1) interfaceReference(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneProduct(2) zhoneWtn(5) zhnLayer2Bridging(42) layer2BridgingObjects(1) availableInterfaceTable(11) availableInterfaceEntry(1) interfaceReference(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneProduct(2) zhoneWtn(5) zhnLayer2Bridging(42) layer2BridgingObjects(1) availableInterfaceTable(11) availableInterfaceEntry(1) interfaceReference(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneProduct(2) zhoneWtn(5) zhnLayer2Bridging(42) layer2BridgingObjects(1) availableInterfaceTable(11) availableInterfaceEntry(1) interfaceReference(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneProduct(2) zhoneWtn(5) zhnLayer2Bridging(42) layer2BridgingObjects(1) availableInterfaceTable(11) availableInterfaceEntry(1) interfaceReference(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneProduct(2) zhoneWtn(5) zhnLayer2Bridging(42) layer2BridgingObjects(1) availableInterfaceTable(11) availableInterfaceEntry(1) interfaceReference(3)}
OID-IRI notation
  • /1/3/6/1/4/1/5504/2/5/42/1/11/1/3
  • /ISO/Identified-Organization/6/1/4/1/5504/2/5/42/1/11/1/3
  • /ISO/3/6/1/4/1/5504/2/5/42/1/11/1/3
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/5504/zhoneProduct/zhoneWtn/zhnLayer2Bridging/layer2BridgingObjects/availableInterfaceTable/availableInterfaceEntry/interfaceReference
  • /iso/identified-organization/dod/internet/private/enterprise/zhone/zhoneProduct/zhoneWtn/zhnLayer2Bridging/layer2BridgingObjects/availableInterfaceTable/availableInterfaceEntry/interfaceReference
  • /iso/identified-organization/dod/internet/private/enterprise/Zhone/zhoneProduct/zhoneWtn/zhnLayer2Bridging/layer2BridgingObjects/availableInterfaceTable/availableInterfaceEntry/interfaceReference
  • /iso/identified-organization/dod/internet/private/enterprises/5504/zhoneProduct/zhoneWtn/zhnLayer2Bridging/layer2BridgingObjects/availableInterfaceTable/availableInterfaceEntry/interfaceReference
  • /iso/identified-organization/dod/internet/private/enterprises/zhone/zhoneProduct/zhoneWtn/zhnLayer2Bridging/layer2BridgingObjects/availableInterfaceTable/availableInterfaceEntry/interfaceReference
  • /iso/identified-organization/dod/internet/private/enterprises/Zhone/zhoneProduct/zhoneWtn/zhnLayer2Bridging/layer2BridgingObjects/availableInterfaceTable/availableInterfaceEntry/interfaceReference
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/5504/zhoneProduct/zhoneWtn/zhnLayer2Bridging/layer2BridgingObjects/availableInterfaceTable/availableInterfaceEntry/interfaceReference
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/zhone/zhoneProduct/zhoneWtn/zhnLayer2Bridging/layer2BridgingObjects/availableInterfaceTable/availableInterfaceEntry/interfaceReference
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/Zhone/zhoneProduct/zhoneWtn/zhnLayer2Bridging/layer2BridgingObjects/availableInterfaceTable/availableInterfaceEntry/interfaceReference
  • /iso/identified-organization/dod/internet/private/vendor-objects/5504/zhoneProduct/zhoneWtn/zhnLayer2Bridging/layer2BridgingObjects/availableInterfaceTable/availableInterfaceEntry/interfaceReference
  • /iso/identified-organization/dod/internet/private/vendor-objects/zhone/zhoneProduct/zhoneWtn/zhnLayer2Bridging/layer2BridgingObjects/availableInterfaceTable/availableInterfaceEntry/interfaceReference
  • /iso/identified-organization/dod/internet/private/vendor-objects/Zhone/zhoneProduct/zhoneWtn/zhnLayer2Bridging/layer2BridgingObjects/availableInterfaceTable/availableInterfaceEntry/interfaceReference
  • /iso/org/dod/internet/private/enterprise/5504/zhoneProduct/zhoneWtn/zhnLayer2Bridging/layer2BridgingObjects/availableInterfaceTable/availableInterfaceEntry/interfaceReference
  • /iso/org/dod/internet/private/enterprise/zhone/zhoneProduct/zhoneWtn/zhnLayer2Bridging/layer2BridgingObjects/availableInterfaceTable/availableInterfaceEntry/interfaceReference
  • /iso/org/dod/internet/private/enterprise/Zhone/zhoneProduct/zhoneWtn/zhnLayer2Bridging/layer2BridgingObjects/availableInterfaceTable/availableInterfaceEntry/interfaceReference
  • /iso/org/dod/internet/private/enterprises/5504/zhoneProduct/zhoneWtn/zhnLayer2Bridging/layer2BridgingObjects/availableInterfaceTable/availableInterfaceEntry/interfaceReference
  • Additional combinations skipped.

SNMP properties

Value type
OCTET STRING
Maximum access defined by MIB
read-only
Status in MIB
current

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. The index encoding is not inferred here.

Published row index: availableInterfaceKey.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.5504.2.5.42.1.11.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.

interfaceReference OBJECT-TYPE
  SYNTAX        OCTET STRING
  MAX-ACCESS    read-only
  STATUS        current
  DESCRIPTION
    "This table should contain a single entry for each available LAN 
     and WAN interface. For a WAN interface, this parameter is the full 
     hierarchical parameter name of a particular WANConnectionDevice. 
     A WANConnectionDevice is considered available (included in this 
     table) only if it supports layer-2 bridged traffic. That is, this 
     table MUST include only WANConnectionDevices that contain either 
     a WANEthernetLinkConfig object, or that contain a WANDSLLinkConfig 
     object for which the LinkType is EoA (Ethernet over ATM). For example: 
         InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2

     For a LAN interface, this parameter is the full hierarchical parameter
     name of a particular LAN InterfaceConfig object, or a WLANConfiguration 
     object.  This table SHOULD include one entry for each such object. For 
     example:
         InternetGatewayDevice.LANDevice.1.LANEthernetInterfaceConfig.2
	 
     For a WAN-side connection to the Gateway's IP router, this parameter 
     is the full hierarchical parameter name of a particular WANConnection
     service. This table SHOULD include an entry for each layer-3 WAN 
     connection.  For example: 
         InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2.WANPPPConnection.1
	 
     For a LAN-side connection to the Gateway's IP router, this parameter 
     is the full hierarchical parameter name of a particular LANDevice. This
     table SHOULD include an entry for each LANDevice, each of which is 
     associated with a LAN-side layer-3 connection to the Gateway's IP 
     router. For example:
         InternetGatewayDevice.LANDevice.2
    "
  ::= { availableInterfaceEntry 3}

Meaning

Descriptions

1 unique

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

This table should contain a single entry for each available LAN and WAN interface. For a WAN interface, this parameter is the full hierarchical parameter name of a particular WANConnectionDevice. A WANConnectionDevice is considered available (included in this table) only if it supports layer-2 bridged traffic. That is, this table MUST include only WANConnectionDevices that contain either a WANEthernetLinkConfig object, or that contain a WANDSLLinkConfig object for which the LinkType is EoA (Ethernet over ATM). For example: InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2 For a LAN interface, this parameter is the full hierarchical parameter name of a particular LAN InterfaceConfig object, or a WLANConfiguration object. This table SHOULD include one entry for each such object. For example: InternetGatewayDevice.LANDevice.1.LANEthernetInterfaceConfig.2 For a WAN-side connection to the Gateway's IP router, this parameter is the full hierarchical parameter name of a particular WANConnection service. This table SHOULD include an entry for each layer-3 WAN connection. For example: InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2.WANPPPConnection.1 For a LAN-side connection to the Gateway's IP router, this parameter is the full hierarchical parameter name of a particular LANDevice. This table SHOULD include an entry for each LANDevice, each of which is associated with a LAN-side layer-3 connection to the Gateway's IP router. For example: InternetGatewayDevice.LANDevice.2

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

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

Status in source: current.

Names: interfaceReference

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "interfaceReference",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This table should contain a single entry for each available LAN and WAN interface. For a WAN interface, this parameter is the full hierarchical parameter name of a particular WANConnectionDevice. A WANConnectionDevice is considered available (included in this table) only if it supports layer-2 bridged traffic. That is, this table MUST include only WANConnectionDevices that contain either a WANEthernetLinkConfig object, or that contain a WANDSLLinkConfig object for which the LinkType is EoA (Ethernet over ATM). For example: InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2 For a LAN interface, this parameter is the full hierarchical parameter name of a particular LAN InterfaceConfig object, or a WLANConfiguration object. This table SHOULD include one entry for each such object. For example: InternetGatewayDevice.LANDevice.1.LANEthernetInterfaceConfig.2 For a WAN-side connection to the Gateway's IP router, this parameter is the full hierarchical parameter name of a particular WANConnection service. This table SHOULD include an entry for each layer-3 WAN connection. For example: InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2.WANPPPConnection.1 For a LAN-side connection to the Gateway's IP router, this parameter is the full hierarchical parameter name of a particular LANDevice. This table SHOULD include an entry for each LANDevice, each of which is associated with a LAN-side layer-3 connection to the Gateway's IP router. For example: InternetGatewayDevice.LANDevice.2 \"",
    "::=",
    "{",
    "availableInterfaceEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This table should contain a single entry for each available LAN and WAN interface. For a WAN interface, this parameter is the full hierarchical parameter name of a particular WANConnectionDevice. A WANConnectionDevice is considered available (included in this table) only if it supports layer-2 bridged traffic. That is, this table MUST include only WANConnectionDevices that contain either a WANEthernetLinkConfig object, or that contain a WANDSLLinkConfig object for which the LinkType is EoA (Ethernet over ATM). For example: InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2 For a LAN interface, this parameter is the full hierarchical parameter name of a particular LAN InterfaceConfig object, or a WLANConfiguration object. This table SHOULD include one entry for each such object. For example: InternetGatewayDevice.LANDevice.1.LANEthernetInterfaceConfig.2 For a WAN-side connection to the Gateway's IP router, this parameter is the full hierarchical parameter name of a particular WANConnection service. This table SHOULD include an entry for each layer-3 WAN connection. For example: InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2.WANPPPConnection.1 For a LAN-side connection to the Gateway's IP router, this parameter is the full hierarchical parameter name of a particular LANDevice. This table SHOULD include an entry for each LANDevice, each of which is associated with a LAN-side layer-3 connection to the Gateway's IP router. For example: InternetGatewayDevice.LANDevice.2"
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.5504)

Goldberg Allen

Siblings (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.5504.2.5.42.1.11.1.1 availableInterfaceKey00
1.3.6.1.4.1.5504.2.5.42.1.11.1.2 interfaceType00
1.3.6.1.4.1.5504.2.5.42.1.11.1.4 availableInterfaceRowStatus00