OID reference

lldpXMedLocLocationTable

1.0.8802.1.1.2.1.5.1.1.2.9

Description

This table contains Location information as advertised by the local system. The information may be configured per port by a Location Information Server (LIS) or other management application. Multiple Location TLVs of different subtypes may be transmitted in the same PDU. The information in this table MUST be stored in…

Full description and source information

Identification

Identifier and names

Parent
1.0.8802.1.1.2.1.5.1.1.2 (lldpXMedLocalData)
Node code
9
Node name
lldpXMedLocLocationTable
Category
SNMP management object
Numeric OID
1.0.8802.1.1.2.1.5.1.1.2.9
URN notation
urn:oid:1.0.8802.1.1.2.1.5.1.1.2.9
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 0 8802 1 1 2 1 5 1 1 2 9}

  • {iso(1) standard(0) iso8802(8802) ieee802dot1(1) ieee802dot1mibs(1) ieee8021lldp(2) lldpObjects(1) lldpExtensions(5) lldpXMedMIB(1) lldpXMedObjects(1) lldpXMedLocalData(2) lldpXMedLocLocationTable(9)}
  • {iso(1) standard(0) iso8802(8802) ieee802dot1(1) ieee802dot1mibs(1) lldpMIB(2) lldpObjects(1) lldpExtensions(5) lldpXMedMIB(1) lldpXMedObjects(1) lldpXMedLocalData(2) lldpXMedLocLocationTable(9)}
  • {iso(1) std(0) iso8802(8802) ieee802dot1(1) ieee802dot1mibs(1) ieee8021lldp(2) lldpObjects(1) lldpExtensions(5) lldpXMedMIB(1) lldpXMedObjects(1) lldpXMedLocalData(2) lldpXMedLocLocationTable(9)}
  • {iso(1) std(0) iso8802(8802) ieee802dot1(1) ieee802dot1mibs(1) lldpMIB(2) lldpObjects(1) lldpExtensions(5) lldpXMedMIB(1) lldpXMedObjects(1) lldpXMedLocalData(2) lldpXMedLocLocationTable(9)}
  • {iso(1) iso-standard(0) iso8802(8802) ieee802dot1(1) ieee802dot1mibs(1) ieee8021lldp(2) lldpObjects(1) lldpExtensions(5) lldpXMedMIB(1) lldpXMedObjects(1) lldpXMedLocalData(2) lldpXMedLocLocationTable(9)}
  • {iso(1) iso-standard(0) iso8802(8802) ieee802dot1(1) ieee802dot1mibs(1) lldpMIB(2) lldpObjects(1) lldpExtensions(5) lldpXMedMIB(1) lldpXMedObjects(1) lldpXMedLocalData(2) lldpXMedLocLocationTable(9)}
  • {iso(1) oidISO(0) iso8802(8802) ieee802dot1(1) ieee802dot1mibs(1) ieee8021lldp(2) lldpObjects(1) lldpExtensions(5) lldpXMedMIB(1) lldpXMedObjects(1) lldpXMedLocalData(2) lldpXMedLocLocationTable(9)}
  • {iso(1) oidISO(0) iso8802(8802) ieee802dot1(1) ieee802dot1mibs(1) lldpMIB(2) lldpObjects(1) lldpExtensions(5) lldpXMedMIB(1) lldpXMedObjects(1) lldpXMedLocalData(2) lldpXMedLocLocationTable(9)}
OID-IRI notation
  • /1/0/8802/1/1/2/1/5/1/1/2/9
  • /ISO/Standard/8802/1/1/2/1/5/1/1/2/9
  • /ISO/0/8802/1/1/2/1/5/1/1/2/9
Named path variants
  • /iso/standard/iso8802/ieee802dot1/ieee802dot1mibs/ieee8021lldp/lldpObjects/lldpExtensions/lldpXMedMIB/lldpXMedObjects/lldpXMedLocalData/lldpXMedLocLocationTable
  • /iso/standard/iso8802/ieee802dot1/ieee802dot1mibs/lldpMIB/lldpObjects/lldpExtensions/lldpXMedMIB/lldpXMedObjects/lldpXMedLocalData/lldpXMedLocLocationTable
  • /iso/std/iso8802/ieee802dot1/ieee802dot1mibs/ieee8021lldp/lldpObjects/lldpExtensions/lldpXMedMIB/lldpXMedObjects/lldpXMedLocalData/lldpXMedLocLocationTable
  • /iso/std/iso8802/ieee802dot1/ieee802dot1mibs/lldpMIB/lldpObjects/lldpExtensions/lldpXMedMIB/lldpXMedObjects/lldpXMedLocalData/lldpXMedLocLocationTable
  • /iso/iso-standard/iso8802/ieee802dot1/ieee802dot1mibs/ieee8021lldp/lldpObjects/lldpExtensions/lldpXMedMIB/lldpXMedObjects/lldpXMedLocalData/lldpXMedLocLocationTable
  • /iso/iso-standard/iso8802/ieee802dot1/ieee802dot1mibs/lldpMIB/lldpObjects/lldpExtensions/lldpXMedMIB/lldpXMedObjects/lldpXMedLocalData/lldpXMedLocLocationTable
  • /iso/oidISO/iso8802/ieee802dot1/ieee802dot1mibs/ieee8021lldp/lldpObjects/lldpExtensions/lldpXMedMIB/lldpXMedObjects/lldpXMedLocalData/lldpXMedLocLocationTable
  • /iso/oidISO/iso8802/ieee802dot1/ieee802dot1mibs/lldpMIB/lldpObjects/lldpExtensions/lldpXMedMIB/lldpXMedObjects/lldpXMedLocalData/lldpXMedLocLocationTable

SNMP properties

Value type
SEQUENCE OF LldpXMedLocLocationEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Product context

Documented MIB packages

The NETGEAR catalogue lists MIB files containing this definition with these product and release labels:

These are catalogue release labels, not necessarily MIB revisions. A MIB definition does not establish that a device implements it or permits access.

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

Show 2 published definitions

lldpXMedLocLocationTable · current

lldpXMedLocLocationTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF LldpXMedLocLocationEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
            "This table contains Location information as advertised
            by the local system.

            The information may be configured per port by a Location
            Information Server (LIS) or other management application.

            Multiple Location TLVs of different subtypes may be transmitted
            in the same PDU.

            The information in this table MUST be stored in non-volatile-memory
            and persist over restart/reboot sequences."
    ::= { lldpXMedLocalData 9 }

lldpXMedLocLocationTable · current

lldpXMedLocLocationTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF LldpXMedLocLocationEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
            "This table contains Location information as advertised
            by the local system.

            The information may be configured per port by a Location
            Information Server (LIS) or other management application.

            Multiple Location TLVs of different subtypes may be transmitted
            in the same PDU.

            The information in this table MUST be stored in non-volatile-memory
            and persist over restart/reboot sequences."
    ::= { lldpXMedLocalData 9 }

Meaning

Descriptions

1 unique

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

This table contains Location information as advertised by the local system. The information may be configured per port by a Location Information Server (LIS) or other management application. Multiple Location TLVs of different subtypes may be transmitted in the same PDU. The information in this table MUST be stored in non-volatile-memory and persist over restart/reboot sequences.

Sources for this description

D-Link official switch MIBsHPE Instant On official MIBsCommon and standard MIB copies (LibreNMS/Observium Community)NETGEAR official product and EOL MIB downloads

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 1D-Link official switch MIBs, HPE Instant On official MIBs, and others1 record · 4 sources

Description 1

lldpXMedLocLocationTable · currentD-Link official switch MIBs, HPE Instant On official MIBs, and others4 sources

Status in source: current.

Names: lldpXMedLocLocationTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "lldpXMedLocLocationTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "LldpXMedLocLocationEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This table contains Location information as advertised by the local system. The information may be configured per port by a Location Information Server (LIS) or other management application. Multiple Location TLVs of different subtypes may be transmitted in the same PDU. The information in this table MUST be stored in non-volatile-memory and persist over restart/reboot sequences.\"",
    "::=",
    "{",
    "lldpXMedLocalData",
    "9",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "LldpXMedLocLocationEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This table contains Location information as advertised by the local system. The information may be configured per port by a Location Information Server (LIS) or other management application. Multiple Location TLVs of different subtypes may be transmitted in the same PDU. The information in this table MUST be stored in non-volatile-memory and persist over restart/reboot sequences."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

Current Registration Authority (inferred from ancestor 1.0)

ISO and IEC

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.0.8802.1.1.2.1.5.1.1.2.9.1 lldpXMedLocLocationEntry22

Siblings (14)

OIDNameDirect childrenDescendantsDescription
1.0.8802.1.1.2.1.5.1.1.2.1 lldpXMedLocMediaPolicyTable17
1.0.8802.1.1.2.1.5.1.1.2.2 lldpXMedLocHardwareRev00
1.0.8802.1.1.2.1.5.1.1.2.3 lldpXMedLocFirmwareRev00
1.0.8802.1.1.2.1.5.1.1.2.4 lldpXMedLocSoftwareRev00
1.0.8802.1.1.2.1.5.1.1.2.5 lldpXMedLocSerialNum00
1.0.8802.1.1.2.1.5.1.1.2.6 lldpXMedLocMfgName00
1.0.8802.1.1.2.1.5.1.1.2.7 lldpXMedLocModelName00
1.0.8802.1.1.2.1.5.1.1.2.8 lldpXMedLocAssetID00
1.0.8802.1.1.2.1.5.1.1.2.10 lldpXMedLocXPoEDeviceType00
1.0.8802.1.1.2.1.5.1.1.2.11 lldpXMedLocXPoEPSEPortTable13
1.0.8802.1.1.2.1.5.1.1.2.12 lldpXMedLocXPoEPSEPowerSource00
1.0.8802.1.1.2.1.5.1.1.2.13 lldpXMedLocXPoEPDPowerReq00
1.0.8802.1.1.2.1.5.1.1.2.14 lldpXMedLocXPoEPDPowerSource00
1.0.8802.1.1.2.1.5.1.1.2.15 lldpXMedLocXPoEPDPowerPriority00