OID reference

entPhysicalParentRelPos

1.3.6.1.4.1.2745.1.5.1.1.1.1.6

Description

An indication of the relative position of this 'child' component among all its 'sibling' components. Sibling components are defined as entPhysicalEntries which share the same instance values of each of the entPhysicalContainedIn and entPhysicalClass objects. An NMS can use this object to identify the relative ordering…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2745.1.5.1.1.1.1 (entPhysicalEntry)
Node code
6
Node name
entPhysicalParentRelPos
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2745.1.5.1.1.1.1.6
URN notation
urn:oid:1.3.6.1.4.1.2745.1.5.1.1.1.1.6
Type
OBJECT-TYPE
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-only
Status in MIB
current
Allowed ranges
-1–2147483647

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: entPhysicalIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.2745.1.5.1.1.1.1.6

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.

Meaning

Descriptions

1 unique

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

An indication of the relative position of this 'child'
component among all its 'sibling' components. Sibling
components are defined as entPhysicalEntries which share the
same instance values of each of the entPhysicalContainedIn
and entPhysicalClass objects.

An NMS can use this object to identify the relative ordering
for all sibling components of a particular parent
(identified by the entPhysicalContainedIn instance in each
sibling entry).

This value should match any external labeling of the
physical component if possible. For example, for a module
labeled as 'card #3', entPhysicalParentRelPos should have
the value '3'.

If the physical position of this component does not match
any external numbering or clearly visible ordering, then
user documentation or other external reference material
should be used to determine the parent-relative position. If
this is not possible, then the the agent should assign a
consistent (but possibly arbitrary) ordering to a given set
of 'sibling' components, perhaps based on internal
representation of the components.

If the agent cannot determine the parent-relative position
for some reason, or if the associated value of
entPhysicalContainedIn is '0', then the value '-1' is
returned. Otherwise a non-negative integer is returned,
indicating the parent-relative position of this physical
entity.

Parent-relative ordering normally starts from '1' and
continues to 'N', where 'N' represents the highest
positioned child entity. However, if the physical entities
(e.g. slots) are labeled from a starting position of zero,
then the first sibling should be associated with a
entPhysicalParentRelPos value of '0'. Note that this
ordering may be sparse or dense, depending on agent
implementation.

The actual values returned are not globally meaningful, as
each 'parent' component may use different numbering
algorithms. The ordering is only meaningful among siblings
of the same parent component.


The agent should retain parent-relative position values
across reboots, either through algorithmic assignment or use
of non-volatile storage.
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
entPhysicalParentRelPos OBJECT-TYPE
    SYNTAX      INTEGER (-1..2147483647)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
            "An indication of the relative position of this 'child'
            component among all its 'sibling' components. Sibling
            components are defined as entPhysicalEntries which share the
            same instance values of each of the entPhysicalContainedIn
            and entPhysicalClass objects.

            An NMS can use this object to identify the relative ordering
            for all sibling components of a particular parent
            (identified by the entPhysicalContainedIn instance in each
            sibling entry).

            This value should match any external labeling of the
            physical component if possible. For example, for a module
            labeled as 'card #3', entPhysicalParentRelPos should have
            the value '3'.

            If the physical position of this component does not match
            any external numbering or clearly visible ordering, then
            user documentation or other external reference material
            should be used to determine the parent-relative position. If
            this is not possible, then the the agent should assign a
            consistent (but possibly arbitrary) ordering to a given set
            of 'sibling' components, perhaps based on internal
            representation of the components.

            If the agent cannot determine the parent-relative position
            for some reason, or if the associated value of
            entPhysicalContainedIn is '0', then the value '-1' is
            returned. Otherwise a non-negative integer is returned,
            indicating the parent-relative position of this physical
            entity.

            Parent-relative ordering normally starts from '1' and
            continues to 'N', where 'N' represents the highest
            positioned child entity.  However, if the physical entities
            (e.g. slots) are labeled from a starting position of zero,
            then the first sibling should be associated with a
            entPhysicalParentRelPos value of '0'.  Note that this
            ordering may be sparse or dense, depending on agent
            implementation.

            The actual values returned are not globally meaningful, as
            each 'parent' component may use different numbering
            algorithms. The ordering is only meaningful among siblings
            of the same parent component.


            The agent should retain parent-relative position values
            across reboots, either through algorithmic assignment or use
            of non-volatile storage."
    ::= { entPhysicalEntry 6 }
Information from Circitor
entPhysicalParentRelPos OBJECT-TYPE
    SYNTAX      INTEGER (-1..2147483647)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
            "An indication of the relative position of this 'child'
            component among all its 'sibling' components. Sibling
            components are defined as entPhysicalEntries which share the
            same instance values of each of the entPhysicalContainedIn
            and entPhysicalClass objects.

            An NMS can use this object to identify the relative ordering
            for all sibling components of a particular parent
            (identified by the entPhysicalContainedIn instance in each
            sibling entry).

            This value should match any external labeling of the
            physical component if possible. For example, for a module
            labeled as 'card #3', entPhysicalParentRelPos should have
            the value '3'.

            If the physical position of this component does not match
            any external numbering or clearly visible ordering, then
            user documentation or other external reference material
            should be used to determine the parent-relative position. If
            this is not possible, then the the agent should assign a
            consistent (but possibly arbitrary) ordering to a given set
            of 'sibling' components, perhaps based on internal
            representation of the components.

            If the agent cannot determine the parent-relative position
            for some reason, or if the associated value of
            entPhysicalContainedIn is '0', then the value '-1' is
            returned. Otherwise a non-negative integer is returned,
            indicating the parent-relative position of this physical
            entity.

            Parent-relative ordering normally starts from '1' and
            continues to 'N', where 'N' represents the highest
            positioned child entity.  However, if the physical entities
            (e.g. slots) are labeled from a starting position of zero,
            then the first sibling should be associated with a
            entPhysicalParentRelPos value of '0'.  Note that this
            ordering may be sparse or dense, depending on agent
            implementation.

            The actual values returned are not globally meaningful, as
            each 'parent' component may use different numbering
            algorithms. The ordering is only meaningful among siblings
            of the same parent component.


            The agent should retain parent-relative position values
            across reboots, either through algorithmic assignment or use
            of non-volatile storage."
    ::= { entPhysicalEntry 6 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2745)

Webber Mark

Siblings (6)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2745.1.5.1.1.1.1.1 entPhysicalIndex00 The index for this entry.
1.3.6.1.4.1.2745.1.5.1.1.1.1.2 entPhysicalDescr00 A textual description of physical entity. This object
should contain a string which identifies the manufacturer's
name for the p…
1.3.6.1.4.1.2745.1.5.1.1.1.1.3 entPhysicalVendorType00 An indication of the vendor-specific hardware type of the


physical entity. Note that this is different from the
definition of MIB…
1.3.6.1.4.1.2745.1.5.1.1.1.1.4 entPhysicalContainedIn00 The value of entPhysicalIndex for the physical entity which
'contains' this physical entity. A value of zero indicates
this phys…
1.3.6.1.4.1.2745.1.5.1.1.1.1.5 entPhysicalClass00 An indication of the general hardware type of the physical
entity.

An agent should set this object to the standard enumeration
val…
1.3.6.1.4.1.2745.1.5.1.1.1.1.7 entPhysicalName00 The textual name of the physical entity. The value of this
object should be the name of the component as assigned by
the local d…