CMDB Health Dashboard Correctness Remediation

PrithaB
Tera Contributor

an hour ago

I'm working on the CMDB health dashboard correctness at present. I need help in remediating the same.
I've come across majorly 3 error description, which are as follows:

 

Orphan:
1. CI relationships do not satisfy the relationship rule defined for CI type cmdb_ci_esx_server. 
Not sure, where to review the rules and remediate.


2. CI is orphan based on orphan rule condition defined for CI type cmdb_ci_esx_server
Encoded condition: ip_addressISEMPTY^operational_status=1^u_operating_environment=Production

 

Stale:
3. The CI was not updated in 7 Days.

Some help with respect to understanding and reviewing the errors will be highly appreciated.
Thank you. 

0 Helpfuls
  • 100 Views
1 REPLY 1

MC30
Tera Guru

44m ago

Hi @PrithaB ,

 

1. Relationship Rule Violation

Error:
CI relationships do not satisfy the relationship rule defined for CI type cmdb_ci_esx_server

Where to review the rules

Navigate to:

  • CMDB → CI Class Manager
  • Open class: cmdb_ci_esx_server
  • Check the “Relationship Rules” related list

Alternatively:

  • Go to table: cmdb_ci_rel_rule.list

These rules define mandatory relationships (e.g., ESX Server must relate to Cluster / Datacenter).

How to remediate

  • Identify missing or incorrect relationships for affected CIs
  • Add the required relationships using:
    • Relationship Editor
    • Discovery / Service Mapping (preferred)
  • If the rule is not applicable in your environment:
    • Review with stakeholders and modify/deactivate cautiously

2. Orphan Rule Condition

Error:
CI is orphan based on condition:
ip_addressISEMPTY^operational_status=1^u_operating_environment=Production

Where to review

Navigate to:

  • CMDB Health → Rules → Orphan Rules
  • Table: cmdb_health_orphan_rule
  • Filter for class: cmdb_ci_esx_server

What it means

CIs are flagged orphan because:

  • IP Address is empty
  • Status = In Use ( 1 )
  • Environment = Production

This indicates incomplete or invalid CI data.

How to remediate

  • Preferred approach: Fix the data
    • Populate ip_address via Discovery or integration (e.g., vCenter)
  • If CI is no longer valid:
    • Set operational_status = Retired
  • If IP address is not applicable in your design:
    • Adjust the orphan rule condition carefully

3. Stale CI (Not updated in 7 days)

Where to review

Navigate to:

  • CMDB Health → Rules → Staleness Rules
  • Table: cmdb_health_staleness_rule

What it means

The CI has not been updated within the defined threshold (7 days).

How to remediate

  • Ensure Discovery or integrations are updating ESX CIs regularly
  • Validate:
    • Discovery schedules
    • MID Server health
    • VMware vCenter integration
  • If needed, adjust the threshold (e.g., 7 → 14 days)
  • Retire or clean up obsolete CIs

Recommended Approach and Best Practice

  • Treat these issues as data source problems, not just CMDB issues
  • Ensure ESX data is coming from a reliable source (vCenter integration / Discovery)
  • Avoid manual fixes at scale
  • Implement:
    • Regular discovery schedules
    • Data governance (CI ownership, certification)
    • Automated remediation where possible

So in short:

  • Relationship errors → Fix missing required relationships
  • Orphan errors → Populate mandatory attributes or adjust rules
  • Stale errors → Ensure regular CI updates via discovery/integration

This approach ensures you are not just fixing records but improving overall CMDB data quality and sustainability.

 

If my response helped, please mark it as correct or helpful.

Regards,

Madhuri

0 Helpfuls