Migrating from Cisco Intersight ITSM Plugin to Service Graph Connector

[AureaLeaC]

Hi everyone,

We are currently encountering an issue with duplicate CIs in our CMDB after migrating from the deprecated Cisco Intersight ITSM Plugin to the Service Graph Connector for Cisco Intersight, and I would like to ask for recommendations on the best remediation approach.

 

Current Situation:

Previously, we were using the Cisco Intersight ITSM Plugin for discovery/integration. Since the plugin is already deprecated, we replaced it with the Service Graph Connector for Cisco Intersight.

After installing and configuring the Service Graph Connector, it imported all Cisco devices from Intersight into the CMDB. However, most of these devices already existed in our CMDB from the previous plugin integration.

Issue

The newly imported CIs were created as new records instead of updating or reconciling with the existing ones, resulting in duplicate CIs.

One thing we noticed is that:

• In the previous plugin, most Cisco devices were classified under generic classes such as Cisco Servers.
• In the Service Graph Connector, devices are now being created under more specific and different CMDB classes.

Because of this class mismatch:

• Identification and Reconciliation Engine (IRE) did not match them correctly.
• No duplicate CI remediation tasks were created.
• Existing CIs and newly imported CIs are now coexisting in different classes.

Questions

1. What is the recommended approach for remediating these duplicate CIs?
2. Has anyone encountered a similar issue when migrating from the legacy Cisco Intersight ITSM Plugin to the Service Graph Connector?
3. Are there any best practices for preserving relationships, history, and dependent records during remediation?

Any recommendations, migration experiences, or best practices would be greatly appreciated.

Thank you!