OID reference

lcsLLDPMEDMapDatum

1.3.6.1.4.1.2356.14.2.21.2.8

Description

The Map Datum is used for the coordinates given in these options: 1:WGS84 2:NAD83/NAVD88 3:NAD83/MLLW

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.2356.14.2.21.2 (lcsLLDPMEDCoordinatesLocation)
Node code: 8
Node name: lcsLLDPMEDMapDatum
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.2356.14.2.21.2.8
URN notation: urn:oid:1.3.6.1.4.1.2356.14.2.21.2.8

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 4 1 2356 14 2 21 2 8}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) lancom-systems(2356) lcosSX(14) lcsConfiguration(2) lcsLLDP(21) lcsLLDPMEDCoordinatesLocation(2) lcsLLDPMEDMapDatum(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) elsa(2356) lcosSX(14) lcsConfiguration(2) lcsLLDP(21) lcsLLDPMEDCoordinatesLocation(2) lcsLLDPMEDMapDatum(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) lancomSystems(2356) lcosSX(14) lcsConfiguration(2) lcsLLDP(21) lcsLLDPMEDCoordinatesLocation(2) lcsLLDPMEDMapDatum(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) lancom-systems(2356) lcosSX(14) lcsConfiguration(2) lcsLLDP(21) lcsLLDPMEDCoordinatesLocation(2) lcsLLDPMEDMapDatum(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) elsa(2356) lcosSX(14) lcsConfiguration(2) lcsLLDP(21) lcsLLDPMEDCoordinatesLocation(2) lcsLLDPMEDMapDatum(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) lancomSystems(2356) lcosSX(14) lcsConfiguration(2) lcsLLDP(21) lcsLLDPMEDCoordinatesLocation(2) lcsLLDPMEDMapDatum(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) lancom-systems(2356) lcosSX(14) lcsConfiguration(2) lcsLLDP(21) lcsLLDPMEDCoordinatesLocation(2) lcsLLDPMEDMapDatum(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) elsa(2356) lcosSX(14) lcsConfiguration(2) lcsLLDP(21) lcsLLDPMEDCoordinatesLocation(2) lcsLLDPMEDMapDatum(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) lancomSystems(2356) lcosSX(14) lcsConfiguration(2) lcsLLDP(21) lcsLLDPMEDCoordinatesLocation(2) lcsLLDPMEDMapDatum(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) lancom-systems(2356) lcosSX(14) lcsConfiguration(2) lcsLLDP(21) lcsLLDPMEDCoordinatesLocation(2) lcsLLDPMEDMapDatum(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) elsa(2356) lcosSX(14) lcsConfiguration(2) lcsLLDP(21) lcsLLDPMEDCoordinatesLocation(2) lcsLLDPMEDMapDatum(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) lancomSystems(2356) lcosSX(14) lcsConfiguration(2) lcsLLDP(21) lcsLLDPMEDCoordinatesLocation(2) lcsLLDPMEDMapDatum(8)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) lancom-systems(2356) lcosSX(14) lcsConfiguration(2) lcsLLDP(21) lcsLLDPMEDCoordinatesLocation(2) lcsLLDPMEDMapDatum(8)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) elsa(2356) lcosSX(14) lcsConfiguration(2) lcsLLDP(21) lcsLLDPMEDCoordinatesLocation(2) lcsLLDPMEDMapDatum(8)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) lancomSystems(2356) lcosSX(14) lcsConfiguration(2) lcsLLDP(21) lcsLLDPMEDCoordinatesLocation(2) lcsLLDPMEDMapDatum(8)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) lancom-systems(2356) lcosSX(14) lcsConfiguration(2) lcsLLDP(21) lcsLLDPMEDCoordinatesLocation(2) lcsLLDPMEDMapDatum(8)}
Additional combinations skipped.

OID-IRI notation

/1/3/6/1/4/1/2356/14/2/21/2/8
/ISO/Identified-Organization/6/1/4/1/2356/14/2/21/2/8
/ISO/3/6/1/4/1/2356/14/2/21/2/8

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/ELSA/lcosSX/lcsConfiguration/lcsLLDP/lcsLLDPMEDCoordinatesLocation/lcsLLDPMEDMapDatum
/iso/identified-organization/dod/internet/private/enterprise/lancom-systems/lcosSX/lcsConfiguration/lcsLLDP/lcsLLDPMEDCoordinatesLocation/lcsLLDPMEDMapDatum
/iso/identified-organization/dod/internet/private/enterprise/elsa/lcosSX/lcsConfiguration/lcsLLDP/lcsLLDPMEDCoordinatesLocation/lcsLLDPMEDMapDatum
/iso/identified-organization/dod/internet/private/enterprise/lancomSystems/lcosSX/lcsConfiguration/lcsLLDP/lcsLLDPMEDCoordinatesLocation/lcsLLDPMEDMapDatum
/iso/identified-organization/dod/internet/private/enterprises/ELSA/lcosSX/lcsConfiguration/lcsLLDP/lcsLLDPMEDCoordinatesLocation/lcsLLDPMEDMapDatum
/iso/identified-organization/dod/internet/private/enterprises/lancom-systems/lcosSX/lcsConfiguration/lcsLLDP/lcsLLDPMEDCoordinatesLocation/lcsLLDPMEDMapDatum
/iso/identified-organization/dod/internet/private/enterprises/elsa/lcosSX/lcsConfiguration/lcsLLDP/lcsLLDPMEDCoordinatesLocation/lcsLLDPMEDMapDatum
/iso/identified-organization/dod/internet/private/enterprises/lancomSystems/lcosSX/lcsConfiguration/lcsLLDP/lcsLLDPMEDCoordinatesLocation/lcsLLDPMEDMapDatum
/iso/identified-organization/dod/internet/private/ldap-enterprise/ELSA/lcosSX/lcsConfiguration/lcsLLDP/lcsLLDPMEDCoordinatesLocation/lcsLLDPMEDMapDatum
/iso/identified-organization/dod/internet/private/ldap-enterprise/lancom-systems/lcosSX/lcsConfiguration/lcsLLDP/lcsLLDPMEDCoordinatesLocation/lcsLLDPMEDMapDatum
/iso/identified-organization/dod/internet/private/ldap-enterprise/elsa/lcosSX/lcsConfiguration/lcsLLDP/lcsLLDPMEDCoordinatesLocation/lcsLLDPMEDMapDatum
/iso/identified-organization/dod/internet/private/ldap-enterprise/lancomSystems/lcosSX/lcsConfiguration/lcsLLDP/lcsLLDPMEDCoordinatesLocation/lcsLLDPMEDMapDatum
/iso/identified-organization/dod/internet/private/vendor-objects/ELSA/lcosSX/lcsConfiguration/lcsLLDP/lcsLLDPMEDCoordinatesLocation/lcsLLDPMEDMapDatum
/iso/identified-organization/dod/internet/private/vendor-objects/lancom-systems/lcosSX/lcsConfiguration/lcsLLDP/lcsLLDPMEDCoordinatesLocation/lcsLLDPMEDMapDatum
/iso/identified-organization/dod/internet/private/vendor-objects/elsa/lcosSX/lcsConfiguration/lcsLLDP/lcsLLDPMEDCoordinatesLocation/lcsLLDPMEDMapDatum
/iso/identified-organization/dod/internet/private/vendor-objects/lancomSystems/lcosSX/lcsConfiguration/lcsLLDP/lcsLLDPMEDCoordinatesLocation/lcsLLDPMEDMapDatum
Additional combinations skipped.

SNMP properties

Value type: Integer32
Maximum access defined by MIB: read-write
Status in MIB: current

Allowed ranges: 0–2

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.2356.14.2.21.2.8.0

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.

Published definitions

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

Show 2 published definitions

lcsLLDPMEDMapDatum · current

lcsLLDPMEDMapDatum OBJECT-TYPE
   SYNTAX      Integer32(0..2)
   MAX-ACCESS  read-write
   STATUS      current
   DESCRIPTION
       "The Map Datum is used for the coordinates given in these options:
	    1:WGS84
	    2:NAD83/NAVD88 
	    3:NAD83/MLLW
		"
   ::= { lcsLLDPMEDCoordinatesLocation 8 }

lcsLLDPMEDMapDatum · current

lcsLLDPMEDMapDatum OBJECT-TYPE
   SYNTAX      Integer32(0..2)
   MAX-ACCESS  read-write
   STATUS      current
   DESCRIPTION
       "The Map Datum is used for the coordinates given in these options:
        1:WGS84
        2:NAD83/NAVD88 
        3:NAD83/MLLW
        "
   ::= { lcsLLDPMEDCoordinatesLocation 8 }

Meaning

Descriptions

1 unique

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

The Map Datum is used for the coordinates given in these options: 1:WGS84 2:NAD83/NAVD88 3:NAD83/MLLW

Sources for this description

LANCOM official release MIBsLANCOM 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 1LANCOM official release MIBs, LANCOM MIB copies (LibreNMS/Observium Community)1 record · 23 sources

Description 1

lcsLLDPMEDMapDatum · currentLANCOM official release MIBs, LANCOM MIB copies (LibreNMS/Observium Community)23 sources

Status in source: current.

Names: lcsLLDPMEDMapDatum

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "lcsLLDPMEDMapDatum",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "0",
    ".",
    ".",
    "2",
    ")",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The Map Datum is used for the coordinates given in these options: 1:WGS84 2:NAD83/NAVD88 3:NAD83/MLLW \"",
    "::=",
    "{",
    "lcsLLDPMEDCoordinatesLocation",
    "8",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            0,
            2
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The Map Datum is used for the coordinates given in these options: 1:WGS84 2:NAD83/NAVD88 3:NAD83/MLLW"
    ],
    null,
    null,
    null,
    null
  ]
}

LANCOM official release MIBs · Publisher's source file: LC-GS-2412-4.30.0224-RU5.mib

Module: LCOS-SX-MIB

See published definition above

Module imports

{'IF-MIB': ['ifIndex'], 'RMON-MIB': ['OwnerString'], 'SNMPv2-TC': ['DisplayString', 'MacAddress', 'TEXTUAL-CONVENTION', 'RowStatus'], 'SNMPv2-SMI': ['enterprises', 'MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Unsigned32', 'Integer32', 'Counter32', 'Counter64', 'IpAddress'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'Q-BRIDGE-MIB': ['dot1qTpFdbAddress', 'dot1qFdbId', 'dot1qTpFdbPort'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressType', 'InetPortNumber'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}

· Download LC-GS-2412-4.30.0224-RU5.mib

Same file in LC-GS-3152X-4.30.0224-RU5.mib.

Same file in LC-GS-3126X-4.30.0224-RU5.mib.

Same file in LC-GS-3252P-4.30.0224-RU5.mib.

Same file in LC-GS-3652XUP-4.30.0224-RU5.mib.

LANCOM official release MIBs · Publisher's source file: LC-GS-2412-4.30.0302-RU6.mib

Module: LCOS-SX-MIB

Same published definition

Module imports

{'IF-MIB': ['ifIndex'], 'RMON-MIB': ['OwnerString'], 'SNMPv2-TC': ['DisplayString', 'MacAddress', 'TEXTUAL-CONVENTION', 'RowStatus'], 'SNMPv2-SMI': ['enterprises', 'MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Unsigned32', 'Integer32', 'Counter32', 'Counter64', 'IpAddress'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'Q-BRIDGE-MIB': ['dot1qTpFdbAddress', 'dot1qFdbId', 'dot1qTpFdbPort'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressType', 'InetPortNumber'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}

· Download LC-GS-2412-4.30.0302-RU6.mib

Same file in LC-GS-3628X-4.30.0302-RU6.mib.

Same file in LC-GS-2426-4.30.0302-RU6.mib.

Same file in LC-XS-3550YUP-4.30.0302-RU6.mib.

Same file in LC-GS-2412P-4.30.0302-RU6.mib.

LANCOM official release MIBs · Publisher's source file: LC-GS-2412-4.30.0434-RU7.mib

Module: LCOS-SX-MIB

Same published definition

Module imports

{'IF-MIB': ['ifIndex'], 'RMON-MIB': ['OwnerString'], 'SNMPv2-TC': ['DisplayString', 'MacAddress', 'TEXTUAL-CONVENTION', 'RowStatus'], 'SNMPv2-SMI': ['enterprises', 'MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Unsigned32', 'Integer32', 'Counter32', 'Counter64', 'IpAddress'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'Q-BRIDGE-MIB': ['dot1qTpFdbAddress', 'dot1qFdbId', 'dot1qTpFdbPort'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressType', 'InetPortNumber'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}

· Download LC-GS-2412-4.30.0434-RU7.mib

Same file in LC-GS-3510XP-4.30.0438-RU8.mib.

Same file in LC-GS-3628XP-4.30.0434-RU7.mib.

Same file in LC-GS-3126X-4.30.0438-RU8.mib.

Same file in LC-GS-3528X-4.30.0438-RU8.mib.

LANCOM official release MIBs · Publisher's source file: LC-GS-2412-4.30.0502-RU10.mib

Module: LCOS-SX-MIB

Same published definition

Module imports

{'IF-MIB': ['ifIndex'], 'RMON-MIB': ['OwnerString'], 'SNMPv2-TC': ['DisplayString', 'MacAddress', 'TEXTUAL-CONVENTION', 'RowStatus'], 'SNMPv2-SMI': ['enterprises', 'MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Unsigned32', 'Integer32', 'Counter32', 'Counter64', 'IpAddress'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'Q-BRIDGE-MIB': ['dot1qTpFdbAddress', 'dot1qFdbId', 'dot1qTpFdbPort'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressType', 'InetPortNumber'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}

· Download LC-GS-2412-4.30.0502-RU10.mib

Same file in LC-GS-3528X-4.30.0502-RU10.mib.

Same file in LC-XS-3510YUP-4.30.0502-RU10.mib.

Same file in LC-GS-3126X-4.30.0502-RU10.mib.

Same file in LC-GS-3126XP-4.30.0502-RU10.mib.

LANCOM official release MIBs · Publisher's source file: LC-GS-3126X-4.00.0219-SU3.mib
Module: LCOS-SX-MIB

See published definition above
Module imports
```
{'IF-MIB': ['ifIndex'], 'RMON-MIB': ['OwnerString'], 'SNMPv2-TC': ['DisplayString', 'MacAddress', 'TEXTUAL-CONVENTION', 'RowStatus'], 'SNMPv2-SMI': ['enterprises', 'MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Unsigned32', 'Integer32', 'Counter32', 'Counter64', 'IpAddress'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressType'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
```
Source data warning: The publisher uses a lowercase row/type name. Preserve this literal type reference and every numeric OID; do not silently change its spelling.
· Download LC-GS-3126X-4.00.0219-SU3.mib
Same file in LC-GS-3152X-4.00.0212-RU2.mib.
Same file in LC-GS-3528X-4.00.0219-SU3.mib.
Same file in LC-GS-3152XSP-4.00.0212-RU2.mib.
Same file in LC-GS-3528XP-4.00.0212-RU2.mib.

LANCOM official release MIBs · Publisher's source file: LC-GS-3126X-4.00.0261-RU4.mib

Module: LCOS-SX-MIB

Same published definition

Module imports

{'IF-MIB': ['ifIndex'], 'RMON-MIB': ['OwnerString'], 'SNMPv2-TC': ['DisplayString', 'MacAddress', 'TEXTUAL-CONVENTION', 'RowStatus'], 'SNMPv2-SMI': ['enterprises', 'MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Unsigned32', 'Integer32', 'Counter32', 'Counter64', 'IpAddress'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressType'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}

· Download LC-GS-3126X-4.00.0261-RU4.mib

Same file in LC-GS-3528X-4.00.0261-RU4.mib.

Same file in LC-GS-3152X-4.00.0261-RU4.mib.

Same file in LC-GS-3510XP-4.00.0261-RU4.mib.

Same file in LC-GS-3152XP-4.00.0261-RU4.mib.

LANCOM official release MIBs · Publisher's source file: LC-GS-3126X-4.00.0305-RU5.mib

Module: LCOS-SX-MIB

Same published definition

Module imports

{'IF-MIB': ['ifIndex'], 'RMON-MIB': ['OwnerString'], 'SNMPv2-TC': ['DisplayString', 'MacAddress', 'TEXTUAL-CONVENTION', 'RowStatus'], 'SNMPv2-SMI': ['enterprises', 'MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Unsigned32', 'Integer32', 'Counter32', 'Counter64', 'IpAddress'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressType'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}

· Download LC-GS-3126X-4.00.0305-RU5.mib

Same file in LC-GS-3528X-4.00.0333-RU6.mib.

Same file in LC-GS-3152XSP-4.00.0333-RU6.mib.

Same file in LC-GS-3152XP-4.00.0333-RU6.mib.

Same file in LC-GS-3152XSP-4.00.0305-RU5.mib.

LANCOM official release MIBs · Publisher's source file: LC-GS-3126X-4.00.0349-RU7.mib

Module: LCOS-SX-MIB

Same published definition

Module imports

{'IF-MIB': ['ifIndex'], 'RMON-MIB': ['OwnerString'], 'SNMPv2-TC': ['DisplayString', 'MacAddress', 'TEXTUAL-CONVENTION', 'RowStatus'], 'SNMPv2-SMI': ['enterprises', 'MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Unsigned32', 'Integer32', 'Counter32', 'Counter64', 'IpAddress'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressType'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}

· Download LC-GS-3126X-4.00.0349-RU7.mib

Same file in LC-GS-3510XP-4.00.0349-RU7.mib.

Same file in LC-GS-3528X-4.00.0349-RU7.mib.

Same file in LC-GS-3152P-4.00.0349-RU7.mib.

Same file in LC-GS-3152XP-4.00.0349-RU7.mib.

LANCOM official release MIBs · Publisher's source file: LC-GS-3126X-4.00.0414-RU8.mib

Module: LCOS-SX-MIB

Same published definition

Module imports

{'IF-MIB': ['ifIndex'], 'RMON-MIB': ['OwnerString'], 'SNMPv2-TC': ['DisplayString', 'MacAddress', 'TEXTUAL-CONVENTION', 'RowStatus'], 'SNMPv2-SMI': ['enterprises', 'MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Unsigned32', 'Integer32', 'Counter32', 'Counter64', 'IpAddress'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'Q-BRIDGE-MIB': ['dot1qTpFdbAddress', 'dot1qFdbId', 'dot1qTpFdbPort'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressType'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}

· Download LC-GS-3126X-4.00.0414-RU8.mib

Same file in LC-GS-3126XP-4.00.0414-RU8.mib.

Same file in LC-GS-3152P-4.00.0414-RU8.mib.

Same file in LC-GS-3152X-4.00.0414-RU8.mib.

Same file in LC-GS-3152XP-4.00.0414-RU8.mib.

LANCOM official release MIBs · Publisher's source file: LC-GS-3126X-4.00.0501-RU9.mib

Module: LCOS-SX-MIB

Same published definition

Module imports

{'IF-MIB': ['ifIndex'], 'RMON-MIB': ['OwnerString'], 'SNMPv2-TC': ['DisplayString', 'MacAddress', 'TEXTUAL-CONVENTION', 'RowStatus'], 'SNMPv2-SMI': ['enterprises', 'MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Unsigned32', 'Integer32', 'Counter32', 'Counter64', 'IpAddress'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'Q-BRIDGE-MIB': ['dot1qTpFdbAddress', 'dot1qFdbId', 'dot1qTpFdbPort'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressType'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}

· Download LC-GS-3126X-4.00.0501-RU9.mib

Same file in LC-GS-3528XP-4.00.0501-RU9.mib.

Same file in LC-GS-3152XSP-4.00.0501-RU9.mib.

Same file in LC-GS-3152XP-4.00.0501-RU9.mib.

Same file in LC-GS-3152P-4.00.0501-RU9.mib.

Browse all 23 supporting sources

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2356)

Udo Brocker

Siblings (6)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.2356.14.2.21.2.2	lcsLLDPMEDLatitude	0	0
1.3.6.1.4.1.2356.14.2.21.2.3	lcsLLDPMEDLatitudeDirection	0	0
1.3.6.1.4.1.2356.14.2.21.2.4	lcsLLDPMEDLongitude	0	0
1.3.6.1.4.1.2356.14.2.21.2.5	lcsLLDPMEDLongitudeDirection	0	0
1.3.6.1.4.1.2356.14.2.21.2.6	lcsLLDPMEDAltitude	0	0
1.3.6.1.4.1.2356.14.2.21.2.7	lcsLLDPMEDAltitudeType	0	0