Physical Entity Table
Oracle Communications Session Border Controller implements the Physical Entity table from the Entity MIB (RFC 2737). The following table describes the standard SNMP Get support for the Entity group, which is a collection of multiple logical entities supported by a single SNMP agent.
| MIB Object | Object ID: 1.3.6.1.2.1.47.1.1.1.1 + | Description |
|---|---|---|
| entPhysicalIndex | .1 | The index for this entry. |
| entPhysicalDescr | .2 | Textual description of the physical entity. A string that identifies the manufacturer's name; which should be set to a distinct value for each version or model of the physical entity. |
| entPhysicalVendorType | .3 | Indication of the vendor-specific hardware type of the physical entity. (This is different from the definition of MIB-II's sysObjectID). An agent should set this object to a enterprise-specific registration identifier value indicating the specific equipment type in detail. The associated instance of entPhysicalClass is used to indicate the general type of hardware device. If no vendor-specific registration identifier exists for this physical entity, or the value is unknown by this agent, then the value { 0 0 } is returned. |
| entPhysicalContainedIn | .4 | Value of entPhysicalIndex for the physical entity which contains this physical entity. A value of zero indicates this physical entity is not contained in any other physical entity. The set of containment relationships define a strict hierarchy; that is, recursion is not allowed. In the event a physical entity is contained by more than one physical entity (for example, double-wide modules), this object should identify the containing entity with the lowest value of entPhysicalIndex. |
| entPhysicalClass | .5 | Indication of the general hardware type of the physical entity. An agent should set this object to the standard enumeration value that most accurately indicates the general class of the physical entity, or the primary class if there is more than one. If no appropriate standard registration identifier exists for this physical entity, then the value other(1) is returned. If the value is unknown by this agent, then the value unknown(2) is returned |
| entPhysicalParentRelPos | .6 |
An indication of the relative position of this child component among all its sibling components. Sibling components are defined as entPhysicalEntries that 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 container (such as card slot) labeled as slot #3, entPhysicalParentRelPos should have the value 3. The entPhysicalEntry for the module plugged in slot 3 should have an entPhysicalParentRelPos value of 1. If the physical position of this component does not match any external numbering or clearly visible ordering, use external reference material to determine the parent-relative position. If this is not possible, 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 (for example, slots) are labeled from a starting position of zero, the first sibling should be associated with a entPhysicalParentRelPos value of 0. This ordering might 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 |
| entPhysicalName | .7 | Textual name of the physical entity. 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, this object contains a zero-length string. The value of entPhysicalName for two physical entities will be the same in the event that the console interface does not distinguish between them, for example, slot-1 and the card in slot-1. |
| entPhysicalHardwareRev | .8 | 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). If revision information is stored internally in a non-printable (for example, binary) format, the agent must convert such information to a printable format, in an implementation-specific manner. If no specific hardware revision string is associated with the physical component, or this information is unknown to the agent, this object contains a zero-length string. |
| entPhysicalFirmwareRev | .9 | Vendor-specific firmware revision string for the physical entity. If revision information is stored internally in a non-printable (for example, binary) format, the agent must convert such information to a printable format, in an implementation-specific manner. If no specific firmware programs are associated with the physical component, or this information is unknown to the agent, this object contains a zero-length string. |
| entPhysicalSoftwareRev | .10 | Vendor-specific software revision string for the physical entity. If revision information is stored internally in a non-printable (for example, binary) format, the agent must convert such information to a printable format, in an implementation-specific manner. If no specific software programs are associated with the physical component, or this information is unknown to the agent, this object contains a zero-length string. |
| entPhysicalSerialNum | .11 | Vendor-specific serial number string for the
physical entity. The preferred value is the serial number string actually
printed on the component itself (if present). On the first instantiation of an
physical entity, the value of entPhysicalSerialNum associated with that entity
is set to the correct vendor-assigned serial number, if this information is
available to the agent. If a serial number is unknown or non-existent, the
entPhysicalSerialNum will be set to a zero-length string instead.
Implementations which can correctly identify the serial numbers of all installed physical entities do not need to provide write access to the entPhysicalSerialNum object.) Agents which cannot provide non-volatile storage for the entPhysicalSerialNum strings are not required to implement write access for this object. Not every physical component will have, or need, a serial number. Physical entities for which the associated value of the entPhysicalIsFRU object is equal to false(2) do not need their own unique serial number. An agent does not have to provide write access for such entities, and might return a zero-length string. If write access is implemented for an instance of entPhysicalSerialNum, and a value is written into the instance, the agent must retain the supplied value in the entPhysicalSerialNum instance associated with the same physical entity for as long as that entity remains instantiated. This includes instantiations across all re- initializations/reboots of the network management system, including those which result in a change of the physical entity's entPhysicalIndex value. |
| entPhysicalMfgName | .12 | Name of the manufacturer of this physical component. The preferred value is the manufacturer name string actually printed on the component itself (if present). (Note that comparisons between instances of the entPhysicalModelName, entPhysicalFirmwareRev, entPhysicalSoftwareRev, and the entPhysicalSerialNum objects, are only meaningful amongst entPhysicalEntries with the same value of entPhysicalMfgName.) If the manufacturer name string associated with the physical component is unknown to the agent, then this object will contain a zero-length string. |
| entPhysicalModeName | .13 | Vendor-specific model name identifier string associated with this physical component. The preferred value is the customer-visible part number, which may be printed on the component itself. If the model name string associated with the physical component is unknown to the agent, then this object will contain a zero-length string. |
| entPhysicalAlias | .14 | Alias name for the physical entity as
specified by a network manager, it provides a non-volatile handle for the
physical entity.
On the first instantiation of an physical entity, the value of entPhysicalAlias associated with that entity is set to the zero-length string. However, an agent might set the value to a locally unique default value, instead of a zero-length string. If write access is implemented for an instance of entPhysicalAlias, and a value is written into the instance, the agent must retain the supplied value in the entPhysicalAlias instance associated with the same physical entity for as long as that entity remains instantiated. This includes instantiations across all re- initializations/reboots of the network management system, including those which result in a change of the physical entity's entPhysicalIndex value. |
| entPhysicalAssetID | .15 | User-assigned asset tracking identifier for
the physical entity as specified by a network manager, which provides
non-volatile storage of this information. On the first instantiation of an
physical entity, the value of entPhysicalAssetID associated with that entity is
set to the zero-length string.
Not every physical component will have a asset tracking identifier, or even need one. Physical entities for which the associated value of the entPhysicalIsFRU object is equal to false(2), do not need their own unique asset tracking identifier. An agent does not have to provide write access for such entities, and might instead return a zero-length string. If write access is implemented for an instance of entPhysicalAssetID, and a value is written into the instance, the agent must retain the supplied value in the entPhysicalAssetID instance associated with the same physical entity for as long as that entity remains instantiated. This includes instantiations across all re- initializations/reboots of the network management system, including those which result in a change of the physical entity's entPhysicalIndex value. If no asset tracking information is associated with the physical component, then this object will contain a zero- length string |
| entPhysicalIsFRU | .16 | Whether this physical entity is considered a
field replaceable unit by the vendor.
|