payload missing criterion attributes (cmdb_ci_outofband_devices)

[PhilomanR]

I am trying to discover the Cisco UCS 220 M5SX series ILOs, however after the quick discovery we could see the error " payload missing minimum set of input values for criterion (matching) attributes from identify rule for table [cmdb_ci_outofband_devices]. I have added the required attributes in the CI Class Manager and loaded the related MIB files. Upon running the quick discovery again, we could see it loads only 10 SNMP OIDs, and the identification error logs displays the Manufacturer and Model ID in Short Description field, but Manufacturer displays alphanumerical value and Model ID does not appear anywhere in the logs. 

Can anyone help me understand what reason for it could be. Your input will be highly appreciated

[Abbas_5 · Accepted solution]

Hello @PhilomanR,

The error "payload missing criterion attributes" when discovering CMDB CI Outage devices, often referred to as cmdb_ci_outage devices, indicates that the Identification and Reconciliation Engine (IRE) is unable to uniquely identify the device based on the data provided. This typically happens because the payload (data sent from the discovery engine) lacks the necessary attributes specified in the IRE's identification rules for that CI class. 

Here's a breakdown of why this error occurs and how to troubleshoot it:

Causes:

• Missing or incomplete data:

  The payload might not contain the required fields needed for matching or identifying the device, such as name, serial number, or other unique identifiers. 
• Customized or incorrect identification rules:

  If the IRE's identification rules have been modified and are not configured correctly, or if they don't align with the discovered data, the error can occur. 
• Uniqueness issues:

  The IRE needs to determine how to uniquely identify the device to prevent duplicate entries. If the data doesn't allow for a clear distinction, the error is returned. 

Troubleshooting Steps:

1. 1. Review the Identification Engine's (IRE) Identification Rules:

   Examine the identification rules for cmdb_ci_outage devices (or the relevant CI class) in the Discovery configuration to identify which attributes are required for matching. 
2. 2. Check the Discovery Payload:

   Inspect the actual payload received during discovery, looking for the missing attributes. Use the ECC Queue to examine the payload for a specific discovery run. 
3. 3. Verify Data Sources:

   Ensure that the discovery engine is collecting the correct data from the target device and that the data is being sent in the expected format. 
4. 4. Test Credential:

   If using CIM credentials, ensure that the credentials are working and that the "Test Credential" function is successful. 
5. 5. Address Uniqueness Issues:

   If the discovered data is not unique enough to be identified, consider adding more attributes to the payload or modifying the identification rules to accommodate the available data. 
6. 6. Review Discovery Patterns:

   The Discovery Pattern Log can provide valuable insights into the discovery process and help identify the root cause of the error. 
7. 7. Check System Properties:

   Certain system properties related to CMDB Identification and Reconciliation can enforce mandatory fields. Ensure that these properties are configured correctly and that they are not preventing discovery updates. 
8. 8. Consult the ServiceNow Knowledge Base for Specific Errors:

   The ServiceNow Knowledge Base often provides detailed troubleshooting information for specific identification errors. 
9. 9. Test Credential:

   If using CIM credentials, ensure that the credentials are working and that the "Test Credential" function is successful. 

   If this is helpful, please hit the thumbs up button and accept the correct solution by referring to this solution in future it will be helpful to them.

   Thanks & Regards,

   Abbas Shaik