Firewall Discovery Fails with "Missing Mandatory Fields" During CMDB Identificatio

akashdeshmu
Tera Contributor

3 weeks ago

Hi All,

I have run Discovery on a set of IP addresses, and the devices are successfully classified as Firewall . However, the CI creation fails during the Identification and Reconciliation (IRE) process with the following error:

CMDB Identification Error:
Missing mandatory field(s)
[u_status_name, support_group, u_sub_status1, subcategory, company, category]
in table [cmdb_ci_ip_firewall]

The identification log shows that Discovery and Classification complete successfully, but IRE is unable to create the CI because the above fields are marked as mandatory and are not present in the Discovery payload. We have (before insert) business rule  to populate  above fields status, substatus, category and subcategory. 

I am considering the following options to resolve the issue:

  1. Make these fields non-mandatory on the cmdb_ci_ip_firewall table.
  2. Set the property "Enforce required attributes during CMDB Identification and Reconciliation" to false.

I would like to understand which approach is considered a best practice from a CMDB/Discovery perspective.

Also, if anyone has encountered a similar issue, please suggest any alternative solutions or recommended workarounds.

Thanks in advance for your help.

Regards,
Akash Deshmukh

 
0 Helpfuls
  • 250 Views
1 REPLY 1

pavani_paluri
Kilo Sage

3 weeks ago

Hi @akashdeshmu ,

 

The issue is happening because IRE checks mandatory fields before the CI is inserted into the CMDB. Since the record is rejected during identification, your Before Insert Business Rule never gets executed, so it cannot populate those fields.

 

From a CMDB/Discovery best practice perspective, I would recommend not disabling IRE validation globally unless absolutely necessary. The cleaner approach is to review whether these fields really need to be mandatory at the CMDB class level.

For fields such as:

Status
Sub Status
Category
Subcategory
Support Group
Company

 

if they are being populated through business rules or operational processes, it is generally better to make them non-mandatory on the CMDB class and populate them after CI creation. This allows Discovery and IRE to create the CI successfully while still maintaining your data quality process.

 

Recommended approach:

Make these business-specific fields non-mandatory on cmdb_ci_ip_firewall.
Continue populating them through your Business Rule or another enrichment process.
Keep "Enforce required attributes during CMDB Identification and Reconciliation" enabled (glide.required.attribute.enabled = true) to avoid impacting all CMDB classes and data sources.

 

Option 1 is the preferred CMDB/Discovery best practice, while Option 2 should be considered only as a last resort because it affects IRE validation globally.

 

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for
Kind Regards,
Pavani P
0 Helpfuls