|
Depending on the monitored platform, the way the various objects are named in the PATROL Console can vary significantly. There are different IDs and names that are used by Hardware Sentry KM for each monitored object:
| • | The internal PATROL Object ID, used to create the instance of the class; This ID is retrieved in the PATROL events that other event management systems gather (like BMC Enterprise Manager, etc.). It is a concatenation of the corresponding connector file name, the host name and the internal device ID. The internal PATROL Object ID can be seen in the Infobox of the corresponding object. |
| • | The internal Device ID, used by Hardware Sentry KM to uniquely identify the device in the underlying instrumentation layer. Depending on the instrumentation layer, the internal Device ID can take very different forms: a simple number, a dot-separated list of small numbers (0.0 or 1.1.2, for example), an alpha-numeric string (VCC_+12V, for example), or a complex WBEM or PnP ID (IDE\DiskHitachi_HTS721080G9SA00_________________MC4OC10H\5&1f698b3f&0&0.0.0_0 for example). The internal Device ID is often a good way to locate the corresponding device in the real life. When it is not too long, it is displayed in the label of the icon representing that object in the PATROL Console. Otherwise, the internal Device ID is replaced by an arbitrary number in the icon label. In any case, the internal Device ID can be seen in the Infobox of the object. |
| • | The name of the icon representing the monitored component in the PATROL Console includes the aforementioned internal Device ID (when it is not too long) as well as some additional information such as the vendor and the model of the component. In some cases, the location of the device or sensor is clearly mentioned. |
| • | Some additional “identifying information” is also provided when the instrumentation layer is able to do so. The availability of additional identifying information really depends on the type of the monitored component and the underlying instrumentation layer. For example, when monitoring a DELL server, Hardware Sentry KM shows the DIMM slot location of each memory module, and their part number. In case of a memory failure, this greatly helps administrators order a new memory module with the right part number and change the faulty one with no risk of confusion with another working memory slot. Additional “identifying information” can be visualized in the Infobox. It is also reported in the Hardware Inventory and the Hardware Health Report generated when a failure is detected. |
The screenshot below clearly shows the different types of IDs and names for a monitored object in Hardware Sentry KM:
Inventory Report showing different types of monitored objects IDs and names
The Hardware Health Report which is generated upon the detection of a failure shows all of the different IDs: PATROL Object ID, Internal Device ID, Serial Number, Part Number, Location, and icon name.
Instant Hardware Health Report showing monitored object IDs
|
