Discovery Identification & re-classification

[now123]

As per our requirement whenever we receive servers from a vendor (DELL/HP/IBM), We have to import them into server class(cmdb_ci_server) with serial number and asset tag, later the build team will install Linux/windows OS into those servers.

If discovery finds the machine it's creating as linux/windows server, still, the cmdb_ci_server table contains the record.   its leads duplicate records.

how the re-classify work in discovery?

[Sashi K1]

Hi Ravi

to avoid duplication try using new CMDB Identifiers that comes with Geneva version. CMDB Identifiers and Reconciliation greatly benefits in defining a centralized control on CI data. New engine has many capabilities to manage CMDB data which are maintained by means of various data sources like Webservices, Rest Calls, Import Sets, User inputs, Orchestration etc. New framework allows us defining a centralized control on how a CI to be created/updated. In your requirement creating Server CIs using bulk update and later Discovery to auto manage them instead of creating duplicates, this framework addresses your problem.

For more information

CMDB Identification and Reconciliation

Try reviewing above framework which could be triggered by changing a property of your current Discovery. In later run, ServiceWatch would be using same CMDB Identifiers.

[cyked]

Hi Sashi, can you be more specific?   I don't see that the new CI Identifiers under identification and reconciliation are all that different than the discovery identifiers prior to geneva.   It seems that the new methods consolidate the mechanisms of identification.   That is, "legacy" ID has entries like serial number table and class, serial number and table, class and name, etc.   Whereas the "new" CI Identifiers consolidate these items under a "class" grouping like Hardware and other CMDB Classes.

This does not appear to address the issue Ravi has called out where a SERVER exists and a duplicate LINUX server is created because identification happens at the extended table level rather than "root" server table.   Doing so would create its own issue.   If you don't have the correct model categories on your product model, reclassing a server to linux server or windows server could create problems