Dell EMC & Powermax Storage Servers Discovery errors

SuvethaS
Tera Contributor

‎08-23-2024 09:15 AM

Hi All,

 

We are trying to discover Dell EMC Scv3020  servers through Data Collector servers and facing errors in Discovery as Classified Not Identified. The WBEM service is getting discovered successfully but somehow Servers are failing during Identification.

CMDB Identification Error: In payload missing minimum set of input values for criterion (matching) attributes from identify rule for table [cmdb_ci_storage_server]. Add these input values in payload 

 

The same error is occurring for the Dell Powermax servers as well. Has anyone faced the similar issue? Any work around for the above error? Please advice. 

 

I verified the CIM classify probe and the value is set as "Modern"- I found this solution in another post but we already have that set up. 

 

0 Helpfuls
  • 678 Views
1 REPLY 1

Selva Arun
Mega Sage
Mega Sage

‎08-26-2024 10:32 AM

Hi,

 

Did you try to determine the identifier used:

 

  1. Navigate to Configuration > Identification/Reconciliation and click Identification Simulation.
  2. Click Start in the Start with Existing Payload tile.
  3. In the Source field, select the data source that is associated with this class update (ServiceNow for example).
  4. Paste the JSON payload into the empty canvas. Use the JSON payload returned in the error. Example payload:
    • {"items": [{"className":"cmdb_ci_computer","values":{"discovery_source":"Manual Entry","name":"computerName","serial_number":"ABCXYZ123789"}}]}
  5. Click Execute to simulate processing of the payload by the identification engine.
  6. Review the output.

Update identifier:

  1. Navigate to Configuration > Identification/Reconciliation > CI Identifiers
  2. Search for the identifier used which returned the error.
  3. Update identifier to contain one identifier entry for one of the fields returned in the payload.
 Note: It is possible that the discovery or data source did not contain enough values. For such cases, the payload will need to be corrected. This could be caused by permission issues when discovering the device, discovery errors, missing data on the source import table, amongst others. Further investigation will be required for such scenarios.
 
The above data has been copied from the below article:
 
We faced similar issue and followed the above resolution steps for different set of Device.

If you believe the solution provided has adequately addressed your query, could you please **mark it as 'Helpful'** and **'Accept it as a Solution'**? This will help other community members who might have the same question find the answer more easily.

 

Thank you for your consideration.

Selva