ENTITY-MIB provides OIDs for multiple logical and physical components. Use this MIB to determine what physical components are loaded on a system (for example, fans and temperature sensors) and see related information such as models and serial numbers. You can also use the index numbers for these components to determine their operational status in the ENTITY-SENSOR-MIB and ENTITY-STATE-MIB.
Palo Alto Networks firewalls, Panorama, and WF-500 appliances support only portions of the entPhysicalTable group:
A single namespace that includes disk slots and disk drives.
The component description.
The value of entPhysicalIndex for the component that contains this component.
Chassis (3), container (5) for a slot, power supply (6), fan (7), sensor (8) for each temperature or other environmental, and module (9) for each line card.
The relative position of this
childcomponent among its
siblingcomponents. Sibling components are defined as entPhysicalEntry components that share the same instance values of each of the entPhysicalContainedIn and entPhysicalClass objects.
Supported only if the management (MGT) interface allows for naming the line card.
The vendor-specific hardware revision of the component.
The vendor-specific firmware revision of the component.
The vendor-specific software revision of the component.
The vendor-specific serial number of the component.
The name of the manufacturer of the component.
The date when the component was manufactured.
The disk model number.
An alias that the network manager specified for the component.
A user-assigned asset tracking identifier that the network manager specified for the component.
Indicates whether the component is a field replaceable unit (FRU).
The Common Language Equipment Identifier (CLEI) number of the component (for example, URN:CLEI:CNME120ARA).
RFC 4133 defines this MIB.