CI Reclassification refers to updating a Configuration Item’s class (for example, from Server to Windows Server) so that it accurately reflects its actual type. IRE plays a huge role in CI Reclassification.
Example 1 :
Let's consider a Windows Server which is wrongly classified as Linux Server.
Here Windows server uses Hardware (class) Rule. Since Hardware class is also a parent to Linux Server it contains Linux Server records.
Whenever the above CI re-discovered as Windows Server, the Hardware Identification rule checks the CIs in Hardware class (including child classes), finds the CI and reclassifies it from Linux Server to Windows Server.
Example 2:
Let's again consider Windows Server wrongly classified as Linux Server.
Here Windows Server has a class specific Identification Rule.
Whenever the CI is re-discovered, the IRE only checks in Windows Server class, finds no match and creates record.
It essentially creates a duplicate record.
Notes :
- From above examples we can see that IRE plays a huge role, if we configure an improper IRE instead of reclassifying, it creates a duplicate record.
- If we don't have a unique identifier value for CIs, IRE may unnecessarily reclassify a CI.
- Having a proper IRE and Unique identifiers not in a particular class, but across CMDB is important for a Healthy CMDB.
