Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Solaris server Discovery failed with IRE errors - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Solaris server Discovery failed with IRE errors
KB0787427

Solaris server Discovery failed with IRE errors


1053 Views Last updated : Apr 8, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Solaris Server Discovery Pattern fails with below error.

Identification CI Errors:

In payload missing minimum set of input values for criterion (matching) attributes from identify rule for table [cmdb_ci_solaris_instance].Add these input values in payload item '{"className":"cmdb_ci_solaris_instance","values":{"discovery_source":"ServiceNow","name":"am-irisp-d001","state":"off","sys_class_name":"cmdb_ci_solaris_instance"}}',Too many other errors,In payload missing minimum set of input values for criterion
(matching) attributes from identify rule for table [cmdb_ci_solaris_instance]. Add these input values in payload item '{"className":"cmdb_ci_solaris_instance","values":{"discovery_source":"ServiceNow","name":"am-iclimsp-d001","state":"off","sys_class_name":"cmdb_ci_solaris_instance"}}
',Too many other errors,In payload missing minimum set of input values for criterion (matching) attributes from identify rule for table [cmdb_ci_solaris_instance].

Syslogs

{"className":"cmdb_ci_solaris_instance","values":{"discovery_source":"ServiceNow","name":"eagletest","correlation_id":"1ddcf9ae-7b42-c08b-a4d7-a9b2e29332e3","state":"off","sys_class_name":"cmdb_ci_solaris_instance"}},lookup:[],related:[]
{"className":"cmdb_ci_solaris_instance","values":{"discovery_source":"ServiceNow","name":"am-irisp-d001","state":"off","sys_class_name":"cmdb_ci_solaris_instance"}},lookup:[],related:[]
{"className":"cmdb_ci_solaris_instance","values":{"discovery_source":"ServiceNow","name":"am-iclimsp-d001","state":"off","sys_class_name":"cmdb_ci_solaris_instance"}},lookup:[],related:[]
{"className":"cmdb_ci_solaris_instance","values":{"discovery_source":"ServiceNow","name":"am-slimsp-d001","state":"off","sys_class_name":"cmdb_ci_solaris_instance"}},lookup:[],related:[]
{"className":"cmdb_ci_solaris_instance","values":{"discovery_source":"ServiceNow","name":"icolimpacs","state":"off","sys_class_name":"cmdb_ci_solaris_instance"}},lookup:[],related:[]
{"className":"cmdb_ci_solaris_instance","values":{"discovery_source":"ServiceNow","name":"pacs-dev","state":"off","sys_class_name":"cmdb_ci_solaris_instance"}},lookup:[],related:[]

Release

Observed post upgrading to Newyork

Cause

The issue observed because the Solaris Server pattern was unable to populate correlation -id for Solaris instance CI's. Since the Solaris instances are identified by correlation id, the IRE engine threw the error.

Quick verification why the pattern was unable to populate the correlation id for Solaris instances: 

  1. The correlation id is retrieved in step 20.3. get UUID in Solaris - Zones shared the library of the Solaris Server Pattern
  2. The step executes the following command "#zoneadm list -cip"
  3. Manually execute "#zoneadm list -cip" on the Solaris host, should give output as below

    0:global:running:/::native:shared
    1:xxxx:running:/global/zones/xxxx:xxxx-xxxx-xx-ab94-d39101a89ca0:solaris8:shared
    2:xxxx:running:/global/zones/xxxx-xxxx:xxxx-xx-65d9-9xc8664b309fcc:native:shared


  4. The Step configured as it should include the string "global" 
  5. Looking at the above output, each line contains the string "global", the whole data is excluded and therefore we are not able to parse the UUID (Correlation id ) from the result.

Resolution

  1. Log in to the instance 
  2. Navigator >> Pattern Designer >> Discovery Patterns 

    https://<Instancename>.service-now.com/sn_discovery_patterns_list.do


  3. In the Name field, search for the pattern "Solaris Server" and open the record 

    https://<Instancename>.service-now.com/$sn_pattern_designer.do?authoring_mode=modify&sys_id=1826ee364f47e200c7e881c18110c7aa&sysparm_view=&sysparm_record_target=sa_pattern&sysparm_record_row=1&sysparm_record_list=nameCONTAINSSolaris+Se%5EORDERBYname&sysparm_record_rows=1In the Identification section >> Click on "Discovery" to go into Debug mode.
  4. Left side >> Go to Step No 20.3 "get uuid"
  5. In the "Exclude Lines" section modify the default value from "global" to ":global:" 

           

  6. Save the Pattern 
  7. Publish the Pattern  
  8. Execute a Quick Discovery 

 


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

Attachments

Attachments

  • Pasted image.png

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.