Technical data

Fabric OS MIB Reference Manual 4-9
Publication Number: 53-0000521-08
Entity MIB Objects
4
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 (for example,
slots) are labeled from a starting position of zero, then the first sibling should be
associated with an entPhysicalParentRelPos value of 0. Note that this ordering might
be sparse or dense, depending on agent implementation.
The actual values returned are not globally meaningful, as each parent component
might use different numbering algorithms. The ordering is meaningful only among
siblings of the same parent component.
The agent should retain parent-relative position values across reboots, either through
algorithmic assignment or use of nonvolatile storage.
entPhysicalName
OID 1.3.6.1.2.1.47.1.1.1.1.7
Status Current
Description The textual name of the physical entity (physical name of the entity such as chassis,
blade, port, and so on). The value of this object should be the name of the component
as assigned by the local device and should be suitable for use in commands entered at
the device’s “console.” This might be a text name, such as “console,” or a simple
component number (for example, port or module number) such as 1, depending on the
physical component naming syntax of the device.
If there is no local name, or this object is otherwise not applicable, then this object
contains a zero-length string.
Note that the value of entPhysicalName for two physical entities is the same in the
event that the console interface does not distinguish between them (for example, slot-
1 and the card in slot-1).
Note The name provides the type of the entry and its number (for example, slot 1, power
supply, and so on). The description gives the textual description of the type of the
entry (for example, power supply, module, and so on)
entPhysicalHardwareRev
OID 1.3.6.1.2.1.47.1.1.1.1.8
Status Current
Description The vendor-specific hardware revision string for the physical entity. The preferred
value is the hardware revision identifier actually printed on the component itself (if
present).
Note that if revision information is stored internally in a nonprintable (for example,
binary) format, then the agent must convert such information to a printable format, in
an implementation-specific manner.