OID reference

entLPMappingTable

1.3.6.1.4.1.2745.1.5.1.3.1

Description

This table contains zero or more rows of logical entity to physical equipment associations. For each logical entity known by this agent, there are zero or more mappings to the physical resources which are used to realize that logical entity. An agent should limit the number and nature of entries in this table such tha…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2745.1.5.1.3 (entityMapping)
Node code
1
Node name
entLPMappingTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2745.1.5.1.3.1
URN notation
urn:oid:1.3.6.1.4.1.2745.1.5.1.3.1
Type
OBJECT-TYPE
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2745 1 5 1 3 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) lancast(2745) lancastMibModulesA(1) entityMIB(5) entityMIBObjects(1) entityMapping(3) entLPMappingTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) lancast(2745) lancastMibModulesA(1) entityMIB(5) entityMIBObjects(1) entityMapping(3) entLPMappingTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) lancast(2745) lancastMibModulesA(1) entityMIB(5) entityMIBObjects(1) entityMapping(3) entLPMappingTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) lancast(2745) lancastMibModulesA(1) entityMIB(5) entityMIBObjects(1) entityMapping(3) entLPMappingTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) lancast(2745) lancastMibModulesA(1) entityMIB(5) entityMIBObjects(1) entityMapping(3) entLPMappingTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) lancast(2745) lancastMibModulesA(1) entityMIB(5) entityMIBObjects(1) entityMapping(3) entLPMappingTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) lancast(2745) lancastMibModulesA(1) entityMIB(5) entityMIBObjects(1) entityMapping(3) entLPMappingTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) lancast(2745) lancastMibModulesA(1) entityMIB(5) entityMIBObjects(1) entityMapping(3) entLPMappingTable(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) lancast(2745) lancastMibModulesA(1) entityMIB(5) entityMIBObjects(1) entityMapping(3) entLPMappingTable(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) lancast(2745) lancastMibModulesA(1) entityMIB(5) entityMIBObjects(1) entityMapping(3) entLPMappingTable(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) lancast(2745) lancastMibModulesA(1) entityMIB(5) entityMIBObjects(1) entityMapping(3) entLPMappingTable(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) lancast(2745) lancastMibModulesA(1) entityMIB(5) entityMIBObjects(1) entityMapping(3) entLPMappingTable(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) lancast(2745) lancastMibModulesA(1) entityMIB(5) entityMIBObjects(1) entityMapping(3) entLPMappingTable(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) lancast(2745) lancastMibModulesA(1) entityMIB(5) entityMIBObjects(1) entityMapping(3) entLPMappingTable(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) lancast(2745) lancastMibModulesA(1) entityMIB(5) entityMIBObjects(1) entityMapping(3) entLPMappingTable(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) lancast(2745) lancastMibModulesA(1) entityMIB(5) entityMIBObjects(1) entityMapping(3) entLPMappingTable(1)}
OID-IRI notation
  • /1/3/6/1/4/1/2745/1/5/1/3/1
  • /ISO/Identified-Organization/6/1/4/1/2745/1/5/1/3/1
  • /ISO/3/6/1/4/1/2745/1/5/1/3/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/lancast/lancastMibModulesA/entityMIB/entityMIBObjects/entityMapping/entLPMappingTable
  • /iso/identified-organization/dod/internet/private/enterprises/lancast/lancastMibModulesA/entityMIB/entityMIBObjects/entityMapping/entLPMappingTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/lancast/lancastMibModulesA/entityMIB/entityMIBObjects/entityMapping/entLPMappingTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/lancast/lancastMibModulesA/entityMIB/entityMIBObjects/entityMapping/entLPMappingTable
  • /iso/org/dod/internet/private/enterprise/lancast/lancastMibModulesA/entityMIB/entityMIBObjects/entityMapping/entLPMappingTable
  • /iso/org/dod/internet/private/enterprises/lancast/lancastMibModulesA/entityMIB/entityMIBObjects/entityMapping/entLPMappingTable
  • /iso/org/dod/internet/private/ldap-enterprise/lancast/lancastMibModulesA/entityMIB/entityMIBObjects/entityMapping/entLPMappingTable
  • /iso/org/dod/internet/private/vendor-objects/lancast/lancastMibModulesA/entityMIB/entityMIBObjects/entityMapping/entLPMappingTable
  • /iso/iso-identified-organization/dod/internet/private/enterprise/lancast/lancastMibModulesA/entityMIB/entityMIBObjects/entityMapping/entLPMappingTable
  • /iso/iso-identified-organization/dod/internet/private/enterprises/lancast/lancastMibModulesA/entityMIB/entityMIBObjects/entityMapping/entLPMappingTable
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/lancast/lancastMibModulesA/entityMIB/entityMIBObjects/entityMapping/entLPMappingTable
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/lancast/lancastMibModulesA/entityMIB/entityMIBObjects/entityMapping/entLPMappingTable
  • /iso/iso-organization/dod/internet/private/enterprise/lancast/lancastMibModulesA/entityMIB/entityMIBObjects/entityMapping/entLPMappingTable
  • /iso/iso-organization/dod/internet/private/enterprises/lancast/lancastMibModulesA/entityMIB/entityMIBObjects/entityMapping/entLPMappingTable
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/lancast/lancastMibModulesA/entityMIB/entityMIBObjects/entityMapping/entLPMappingTable
  • /iso/iso-organization/dod/internet/private/vendor-objects/lancast/lancastMibModulesA/entityMIB/entityMIBObjects/entityMapping/entLPMappingTable

SNMP properties

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

Meaning

Descriptions

1 unique

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

This table contains zero or more rows of logical entity to
physical equipment associations. For each logical entity
known by this agent, there are zero or more mappings to the
physical resources which are used to realize that logical
entity.

An agent should limit the number and nature of entries in
this table such that only meaningful and non-redundant
information is returned. For example, in a system which
contains a single power supply, mappings between logical
entities and the power supply are not useful and should not
be included.

Also, only the most appropriate physical component which is
closest to the root of a particular containment tree should
be identified in an entLPMapping entry.

For example, suppose a bridge is realized on a particular
module, and all ports on that module are ports on this
bridge. A mapping between the bridge and the module would be
useful, but additional mappings between the bridge and each
of the ports on that module would be redundant (since the
entPhysicalContainedIn hierarchy can provide the same
information). If, on the other hand, more than one bridge
was utilizing ports on this module, then mappings between
each bridge and the ports it used would be appropriate.

Also, in the case of a single backplane repeater, a mapping


for the backplane to the single repeater entity is not
necessary.
Sources for this description

Circitor

Parsed from LC-ENTITY-MIB.mib · LC-ENTITY-MIB

Source file: Download LC-ENTITY-MIB.mib

Browse all files from Circitor

Historical records

Additional source information

Information from OID Repository
Vendor: LANCAST, Inc.
Module: LC-ENTITY-MIB

[Automatically extracted from oidview.com]
Information from MIBdepot
entLPMappingTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF EntLPMappingEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
            "This table contains zero or more rows of logical entity to
            physical equipment associations. For each logical entity
            known by this agent, there are zero or more mappings to the
            physical resources which are used to realize that logical
            entity.

            An agent should limit the number and nature of entries in
            this table such that only meaningful and non-redundant
            information is returned. For example, in a system which
            contains a single power supply, mappings between logical
            entities and the power supply are not useful and should not
            be included.

            Also, only the most appropriate physical component which is
            closest to the root of a particular containment tree should
            be identified in an entLPMapping entry.

            For example, suppose a bridge is realized on a particular
            module, and all ports on that module are ports on this
            bridge. A mapping between the bridge and the module would be
            useful, but additional mappings between the bridge and each
            of the ports on that module would be redundant (since the
            entPhysicalContainedIn hierarchy can provide the same
            information). If, on the other hand, more than one bridge
            was utilizing ports on this module, then mappings between
            each bridge and the ports it used would be appropriate.

            Also, in the case of a single backplane repeater, a mapping


            for the backplane to the single repeater entity is not
            necessary."
    ::= { entityMapping 1 }
Information from Circitor
entLPMappingTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF EntLPMappingEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
            "This table contains zero or more rows of logical entity to
            physical equipment associations. For each logical entity
            known by this agent, there are zero or more mappings to the
            physical resources which are used to realize that logical
            entity.

            An agent should limit the number and nature of entries in
            this table such that only meaningful and non-redundant
            information is returned. For example, in a system which
            contains a single power supply, mappings between logical
            entities and the power supply are not useful and should not
            be included.

            Also, only the most appropriate physical component which is
            closest to the root of a particular containment tree should
            be identified in an entLPMapping entry.

            For example, suppose a bridge is realized on a particular
            module, and all ports on that module are ports on this
            bridge. A mapping between the bridge and the module would be
            useful, but additional mappings between the bridge and each
            of the ports on that module would be redundant (since the
            entPhysicalContainedIn hierarchy can provide the same
            information). If, on the other hand, more than one bridge
            was utilizing ports on this module, then mappings between
            each bridge and the ports it used would be appropriate.

            Also, in the case of a single backplane repeater, a mapping


            for the backplane to the single repeater entity is not
            necessary."
    ::= { entityMapping 1 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2745)

Webber Mark

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2745.1.5.1.3.1.1 entLPMappingEntry11 Information about a particular logical entity to physical
equipment association. Note that the nature of the
association is not s…

Siblings (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2745.1.5.1.3.2 entAliasMappingTable13 This table contains zero or more rows, representing
mappings of logical entity and physical component to
external MIB identifiers…
1.3.6.1.4.1.2745.1.5.1.3.3 entPhysicalContainsTable12 A table which exposes the container/containee relationships
between physical entities. This table provides equivalent
information…