Good morning,
In Utah release, we have several Linux Servers that because of infrasctructure reasons have the same Serial Number. Modifying these Serial Numbers is not an option right now because it would be too impacting.
When Discovery runs, it is overwriting these servers in the same record. Everytime the discovery is executed, the servers are updated several times, leaving finally the name (and other fields) of the last server it discovered.
Let's say we have:
| Name | Serial number |
| example111 | sn123 |
| example222 | sn123 |
| example333 | sn123 |
I put a screenshot to show an example of the overwrite:
We have gone through other community articles such as Discover multiple CIs with the same serial number - Part I but we don't get the clue here. We have tried:
- Modifying identifiers: Inside the hardware identifier, we created a new Identifier entry on the Linux Server table with order 50 that should match with these servers using the Name as criteria and with the condition that 'name starts with example'. In the rest of the ootb we added the condition that the 'name does not contain example'.
- Creating a new identifier on the Linux Server table, with two entries, one with name as criteria and condition 'name starts by example' and another with serial number as criteria and condition 'name does not contain example'.
- Creating manually the host example222 and a record on serial number table relating ns123 with the CI, but discovery continue working in the same way, not considering it.
Maybe we are missing something or not taking the proper perspective. Can you please give us a hand on this?
Thank you in advance!
#Discovery #CMDB
