Description: An indication of the relative position of this 'child' component among all its 'sibling' components. Sibling components are defined as docsRphyRpdIfPhysEntityEntries that share the same instance values of each of the docsRphyRpdIfPhysEntityContainedIn and docsRphyRpdIfPhysEntityClass objects.

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

If possible, this value should match any external labeling of the physical component. For example, for a container (e.g., card slot) labeled as 'slot #3', docsRphyRpdIfPhysEntityParentRelPos should have the value '3'. Note that the docsRphyRpdIfPhysEntityEntry for the module plugged in slot 3 should have an docsRphyRpdIfPhysEntityParentRelPos value of '1'.

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 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 docsRphyRpdIfPhysEntityContainedIn 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 an docsRphyRpdIfPhysEntityParentRelPos 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.