An indication of the relative position of this 'child'
component among all its 'sibling' components. Sibling
components are defined as hpEntPhysicalEntries which share the
same instance values of each of the hpEntPhysicalContainedIn
and hpEntPhysicalClass objects.
An NMS can use this object to identify the relative ordering
for all sibling components of a particular parent
(identified by the hpEntPhysicalContainedIn 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', hpEntPhysicalParentRelPos 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
hpEntPhysicalContainedIn 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
hpEntPhysicalParentRelPos 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.
Parsed from file hpEntMib.mib.txt
Company: None
Module: HP-ENTITY-MIB
An indication of the relative position of this 'child'
component among all its 'sibling' components. Sibling
components are defined as hpEntPhysicalEntries which share the
same instance values of each of the hpEntPhysicalContainedIn
and hpEntPhysicalClass objects.
An NMS can use this object to identify the relative ordering
for all sibling components of a particular parent
(identified by the hpEntPhysicalContainedIn 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', hpEntPhysicalParentRelPos 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
hpEntPhysicalContainedIn 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
hpEntPhysicalParentRelPos 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.
Parsed from file HP-ENTITY-MIB.mib
Module: HP-ENTITY-MIB
Vendor: Hewlett-Packard
Module: HP-ENTITY-MIB
[Automatically extracted from oidview.com]
hpEntPhysicalParentRelPos OBJECT-TYPE SYNTAX INTEGER (-1..2147483647) MAX-ACCESS read-only STATUS obsolete DESCRIPTION "An indication of the relative position of this 'child' component among all its 'sibling' components. Sibling components are defined as hpEntPhysicalEntries which share the same instance values of each of the hpEntPhysicalContainedIn and hpEntPhysicalClass objects. An NMS can use this object to identify the relative ordering for all sibling components of a particular parent (identified by the hpEntPhysicalContainedIn 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', hpEntPhysicalParentRelPos 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 hpEntPhysicalContainedIn 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 hpEntPhysicalParentRelPos 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." ::= { hpEntPhysicalEntry 6 }
hpEntPhysicalParentRelPos OBJECT-TYPE SYNTAX INTEGER (-1..2147483647) MAX-ACCESS read-only STATUS obsolete DESCRIPTION "An indication of the relative position of this 'child' component among all its 'sibling' components. Sibling components are defined as hpEntPhysicalEntries which share the same instance values of each of the hpEntPhysicalContainedIn and hpEntPhysicalClass objects. An NMS can use this object to identify the relative ordering for all sibling components of a particular parent (identified by the hpEntPhysicalContainedIn 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', hpEntPhysicalParentRelPos 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 hpEntPhysicalContainedIn 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 hpEntPhysicalParentRelPos 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." ::= { hpEntPhysicalEntry 6 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.11.2.14.9.1.1.1.1.1 | hpEntPhysicalIndex | 0 | 0 | The index for this entry. |
| 1.3.6.1.4.1.11.2.14.9.1.1.1.1.2 | hpEntPhysicalDescr | 0 | 0 | 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.11.2.14.9.1.1.1.1.3 | hpEntPhysicalVendorType | 0 | 0 | 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.11.2.14.9.1.1.1.1.4 | hpEntPhysicalContainedIn | 0 | 0 | The value of hpEntPhysicalIndex for the physical entity which 'contains' this physical entity. A value of zero indicates this ph… |
| 1.3.6.1.4.1.11.2.14.9.1.1.1.1.5 | hpEntPhysicalClass | 0 | 0 | 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.11.2.14.9.1.1.1.1.7 | hpEntPhysicalName | 0 | 0 | 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… |