Hi Sherard,
I think it is probably this error message:
When data comes back in the identification probe results, the sensor then creates a payload to send to the identification engine. The identification engine uses this to attempt to identify the CI in the CMDB. Included in the payload is data for lookup rules. Lookup rules are for tables related to the main CI. A little more information is here:
In short, your hardware identification rule will have a lookup rule for serial number and serial number type on the serial number table. It is a lookup because you are actually attempting to identify a hardware CI (storage server in this case) but the identifier entry is using data in the serial number table. So it is attempting to find serial numbers and serial number types in the serial number table that it can use to identify the main CI. The serial number table has a reference to the hardware CI so once it finds a match, it knows which hardware CI the serial number belongs to and can identify the storage server CI. The specific identifier entry I am referring to will be similar to the following:
I can't be sure with not being able to look at the probe results but in your case, what I think will be happening is that there will be duplicate entries in the identification probe results and you will have multiple entries for the same serial number/serial number type combination. So I think this is the first place to check.
If this is the issue, then ideally you would want to find out why duplicate entries are in there but this could be due to a number of reasons - device reporting multiple entries, sensor creating a duplicate. Probably the most likely is that this is data coming from the device itself but again, I can't be sure. This is an example from the identification sensor for a Windows PC:
<result id="b0fc08860a0a0baa005952556d837e18" name="WMI: Hardware Information" order="1" topic="WMIRunner">
<results probe_time="3515" result_code="0">
<result>
<output>
{"related_data":{"srlArr":[{"serial_number_type":"system","serial_number":"ABC123"},{"serial_number_type":"uuid","serial_number":"DEF456"},
If the data coming from the device can't be fixed, then either a new identifier rule could be created for the storage server which does not have the serial number, serial number type identifier entry (i.e. is exactly the same as the Hardware rule without the serial number/serial number type rule) or perhaps the identification sensor could be changed to filter out duplicates.
However you might first want to raise an incident with support to help investigate further where the issue is.
Regards,
Dave
