Failed Exploring CI Pattern in Discovery

[AhmedOutlaw1]

Hello all,

***DISCLAIMER***

I am truly willing to learn not just asking for a quick fix

We implemented Discovery a few months back and brought CIs into our CMDB. However, in attempt to implement service mapping I found the following errors in the discovery logs:

Failed Exploring CI Pattern, Pattern name: Credentialless Discovery Network Device

Failed Exploring CI Pattern, Pattern name: F5REST

Failed Exploring CI Pattern, Pattern name: IIS

Failed Exploring CI Pattern, Pattern name: Microsoft SharePoint

Failed Exploring CI Pattern, Pattern name: MSSql DB On Windows

Failed Exploring CI Pattern, Pattern name: Network Routing Device - Light

Failed Exploring CI Pattern, Pattern name: SSAS

Failed Exploring CI Pattern, Pattern name: Tomcat

Failed Exploring CI Pattern, Pattern name: Windows OS – Servers

Each error has a Process ID attached to it and I've used the forum to troubleshoot these errors. However, I am stumped. For example: 

Identifier: Identification CI Errors:
In payload no relations defined for dependent class [cmdb_ci_iisdirectory] that matches any containment/hosting rules: [cmdb_ci_microsoft_iis_web_server <- Runs <- cmdb_ci_iisdirectory,cmdb_ci_appl >> Runs on >> cmdb_ci_hardware]

I go in check the containment rule(s) and they seem to be correct but it is not correct (Don't know what Im doing wrong). Can anyone guide me to a resolving some of these errors?

[Vivektietsood]

Have you completed horizontal discovery if not I would start by addressing them one by one that it pick one CI, easiest one is windows - OS Servers. 

Two things to address are:

- Have you configured credentials, access required is admin level.

- Please also double check that the classifier rules, these are the rules which tell discovery which patterns to run

https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/concept/dis...

Next one is IIS /SSAS/SharePoint/MS SQL - I would imagine that with the above mentioned access you would start seeing IIS In installed software related list in discovery if you need specific details on MSSQL then you would need to configure access for it

https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/reference/m... 

Now for Network Routing Device - Light and F 5 these are network devices, have you configured SNMP credentials and similarly check classifiers for them 

https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/concept/dis...

Please mark helpful or accept solution so that it helps others with a similar question.

[AhmedOutlaw1]

Vivektietsood,

Thanks for the quick response! I am double checking permission now and will report back if this resolves my issues.

[Vivektietsood]

Can you please accept solution if this question is answered, so that it helps others with a similar question. Thanks 

[Akshatha Ballal · Accepted solution]

No relations defined for dependent class that matches any hosting/containment rule usually means the associated dependent class data is not present/captured in the pattern to successfully create the CI.

In payload no relations defined for dependent class [cmdb_ci_iisdirectory] that matches 
any containment/hosting rules:[cmdb_ci_microsoft_iis_web_server <- Runs <- cmdb_ci_iisdirectory,
cmdb_ci_appl >> Runs on >> cmdb_ci_hardware]



In the CI class manager for the table IIS Virtual Directory(cmdb_ci_iisdirectory), you can see it has a dependent
relationship on Microsoft IIS web server. This means that in order to populate the IIS virtual directory,
there should already be a IIS web server populated in the cmdb with a contains connection/relation to 
IIS virtual directory, then only the pattern would be successfully executed. 

So, in your pattern see the step and check if Microsoft IIS connection/creation is getting captured correctly.