OID reference

receivedCoordinatesTable

1.3.6.1.4.1.3181.10.6.2.43.101

Description

Detailed GPS information about the pysical location of the attached device for each port are visible here if provided through the LLDP-MED protocol.

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.3181.10.6.2.43 (lldp)
Node code
101
Node name
receivedCoordinatesTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.3181.10.6.2.43.101
URN notation
urn:oid:1.3.6.1.4.1.3181.10.6.2.43.101
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 3181 10 6 2 43 101}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) microsens(3181) managedSwitches(10) g6(6) protocol(2) lldp(43) receivedCoordinatesTable(101)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) microsens(3181) managedSwitches(10) g6(6) protocol(2) lldp(43) receivedCoordinatesTable(101)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) microsens(3181) managedSwitches(10) g6(6) protocol(2) lldp(43) receivedCoordinatesTable(101)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) microsens(3181) managedSwitches(10) g6(6) protocol(2) lldp(43) receivedCoordinatesTable(101)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) microsens(3181) managedSwitches(10) g6(6) protocol(2) lldp(43) receivedCoordinatesTable(101)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) microsens(3181) managedSwitches(10) g6(6) protocol(2) lldp(43) receivedCoordinatesTable(101)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) microsens(3181) managedSwitches(10) g6(6) protocol(2) lldp(43) receivedCoordinatesTable(101)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) microsens(3181) managedSwitches(10) g6(6) protocol(2) lldp(43) receivedCoordinatesTable(101)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) microsens(3181) managedSwitches(10) g6(6) protocol(2) lldp(43) receivedCoordinatesTable(101)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) microsens(3181) managedSwitches(10) g6(6) protocol(2) lldp(43) receivedCoordinatesTable(101)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) microsens(3181) managedSwitches(10) g6(6) protocol(2) lldp(43) receivedCoordinatesTable(101)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) microsens(3181) managedSwitches(10) g6(6) protocol(2) lldp(43) receivedCoordinatesTable(101)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) microsens(3181) managedSwitches(10) g6(6) protocol(2) lldp(43) receivedCoordinatesTable(101)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) microsens(3181) managedSwitches(10) g6(6) protocol(2) lldp(43) receivedCoordinatesTable(101)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) microsens(3181) managedSwitches(10) g6(6) protocol(2) lldp(43) receivedCoordinatesTable(101)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) microsens(3181) managedSwitches(10) g6(6) protocol(2) lldp(43) receivedCoordinatesTable(101)}
OID-IRI notation
  • /1/3/6/1/4/1/3181/10/6/2/43/101
  • /ISO/Identified-Organization/6/1/4/1/3181/10/6/2/43/101
  • /ISO/3/6/1/4/1/3181/10/6/2/43/101
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/microsens/managedSwitches/g6/protocol/lldp/receivedCoordinatesTable
  • /iso/identified-organization/dod/internet/private/enterprises/microsens/managedSwitches/g6/protocol/lldp/receivedCoordinatesTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/microsens/managedSwitches/g6/protocol/lldp/receivedCoordinatesTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/microsens/managedSwitches/g6/protocol/lldp/receivedCoordinatesTable
  • /iso/org/dod/internet/private/enterprise/microsens/managedSwitches/g6/protocol/lldp/receivedCoordinatesTable
  • /iso/org/dod/internet/private/enterprises/microsens/managedSwitches/g6/protocol/lldp/receivedCoordinatesTable
  • /iso/org/dod/internet/private/ldap-enterprise/microsens/managedSwitches/g6/protocol/lldp/receivedCoordinatesTable
  • /iso/org/dod/internet/private/vendor-objects/microsens/managedSwitches/g6/protocol/lldp/receivedCoordinatesTable
  • /iso/iso-identified-organization/dod/internet/private/enterprise/microsens/managedSwitches/g6/protocol/lldp/receivedCoordinatesTable
  • /iso/iso-identified-organization/dod/internet/private/enterprises/microsens/managedSwitches/g6/protocol/lldp/receivedCoordinatesTable
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/microsens/managedSwitches/g6/protocol/lldp/receivedCoordinatesTable
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/microsens/managedSwitches/g6/protocol/lldp/receivedCoordinatesTable
  • /iso/iso-organization/dod/internet/private/enterprise/microsens/managedSwitches/g6/protocol/lldp/receivedCoordinatesTable
  • /iso/iso-organization/dod/internet/private/enterprises/microsens/managedSwitches/g6/protocol/lldp/receivedCoordinatesTable
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/microsens/managedSwitches/g6/protocol/lldp/receivedCoordinatesTable
  • /iso/iso-organization/dod/internet/private/vendor-objects/microsens/managedSwitches/g6/protocol/lldp/receivedCoordinatesTable

SNMP properties

Value type
SEQUENCE OF ReceivedCoordinatesEntry
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.

The displayed source records contain one distinct definition. Compare its source records.

receivedCoordinatesTable	OBJECT-TYPE
	SYNTAX SEQUENCE OF ReceivedCoordinatesEntry
	MAX-ACCESS not-accessible
	STATUS current
	DESCRIPTION
		"Detailed GPS information about the pysical location of the attached device for each port are visible here if provided through the LLDP-MED protocol. "
	::= { lldp 101 }

Meaning

Descriptions

1 unique

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

Detailed GPS information about the pysical location of the attached device for each port are visible here if provided through the LLDP-MED protocol.

Sources for this description

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

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), Netdisco MIB archive copies1 record · 2 sources

Description 1

receivedCoordinatesTable · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies2 sources

Status in source: current.

Names: receivedCoordinatesTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "receivedCoordinatesTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "ReceivedCoordinatesEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Detailed GPS information about the pysical location of the attached device for each port are visible here if provided through the LLDP-MED protocol. \"",
    "::=",
    "{",
    "lldp",
    "101",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "ReceivedCoordinatesEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Detailed GPS information about the pysical location of the attached device for each port are visible here if provided through the LLDP-MED protocol."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.3181)

Hannes Bauer

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.3181.10.6.2.43.101.1 receivedCoordinatesEntry99

Siblings (9)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.3181.10.6.2.43.1 configTable120
1.3.6.1.4.1.3181.10.6.2.43.2 localCoordinatesTable110
1.3.6.1.4.1.3181.10.6.2.43.3 localCivicLocationTable126
1.3.6.1.4.1.3181.10.6.2.43.100 receivedOverviewTable115
1.3.6.1.4.1.3181.10.6.2.43.102 receivedCivicLocationsTable126
1.3.6.1.4.1.3181.10.6.2.43.103 receivedPoliciesTable18
1.3.6.1.4.1.3181.10.6.2.43.104 receivedInventoryInfosTable19
1.3.6.1.4.1.3181.10.6.2.43.105 receivedPoeInfosTable16
1.3.6.1.4.1.3181.10.6.2.43.106 receivedPoeControlTable113