HP StorageWorks 2/16V Brocade Fabric OS MIB Reference - Supporting Fabric OS 5 - Page 122

4 entPhysicalFirmwareRev 1.3.6.1.2.1.47.1.1.1.1.9 entPhysicalFirmwareRev 1.3.6.1.2.1.47.1.1.1.1.9 The vendor-specific firmware revision string for the physical entity. 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. If no specific firmware programs are associated with the physical component, or if this information is unknown to the agent, then this object will contain a zero-length string. Set to an empty string. entPhysicalSoftwareRev 1.3.6.1.2.1.47.1.1.1.1.10 The vendor-specific software revision string for the physical entity. 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. If no specific software programs are associated with the physical component, or if this information is unknown to the agent, then this object will contain a zero-length string. Set to empty string. entPhysicalSerialNum 1.3.6.1.2.1.47.1.1.1.1.11 The vendor-specific serial number string for the physical entity. The preferred value is the serial number actually printed on the component (if present). On the first instantiation of a 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 nonexistent, the entPhysicalSerialNum is set to a zero-length string instead. Note that implementations that can correctly identify the serial numbers of all installed physical entities do not need to provide write access to the entPhysicalSerialNum object. Agents that cannot provide nonvolatile storage for the entPhysicalSerialNum strings are not required to implement write access for this object. Not every physical component has a serial number or even needs one. Physical entities for which the associated value of the entPhysicalIsFRU object is equal to "false(2)" (for example, the repeater ports within a repeater module), 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 reinitializations/reboots of the network management system, including those that result in a change of the physical entity's entPhysicalIndex value. 106 Fabric OS MIB Reference 53-1000439-01