Discovery failed due to IRE Engine error.

[venkram]

we are facing an issue during Discovery where the IRE fails, and the discovered data is not processed into the CMDB.

Has anyone faced similar issue before? Any guidance from the community would be appreciated.

@Ankur Bawiskar ,

@Dr Atul G- LNG ,

@asajay011 

[Dr Atul G- LNG]

I am not sure mate this. Log a Now support case.

[DaveHertel]

I agree with Dr. Atul G.  --- this error is very unusual.  This is way beyond the norm for Discovery error/troubleshooting.   Your best bet is to engage ServiceNow via HI ticket on this.. IMHO

Dave

[Vishnu-K · Accepted solution]

Hi @venkram ,
In the all navigator type Metadata Editor and open it.

then there search for the class name in containment rules and hosting rules tab with either cmdb_ci_hardware or dscy_route_interface, you would see some thing there like the example i have taken the oracle.

so if you see there that in the logs that is mentioned that the containment rule is missing , so you have to configure that containment rule or hosting rule mapping in the pattern itself, below is an example of how to do it in the pattern.

In the above example it shows creation of relation between the "cmdb_ci_db_ora_instance" and "cmdb_ci_rubrik_cluster" with relation Managed by ::Manages, like wise you have to do which relation is missing (i.e "Used by::Uses") between the dscy_route_interface and cmdb_ci_hardware

Hope this helps you, Please do mark it as helpful . And accept the solution.

[Vijaya_Mnpram]

@venkram are you getting these errors while trying to enter the data using a playload in the background script as well. Something like this:

{
  "items": [
    {
      "className": "cmdb_ci_win_server",
      "lookup": [],
      "values": {
        "name": "Server-03"
       }
    }
  ],
  "relations": []
}