Differentiating Discovery Identifiers for Physical vs Virtual Servers

natedickson2
Tera Contributor

‎01-03-2019 09:16 AM

Hi All,

I'm looking to see if anyone has come up with good Discovery identifiers for servers when you have a mix of both a physical and virtual environment.

  1. Scenario 1 - Servers might move from Physical to Virtual. In this scenario, the hostname/IP stay the same but the serial number changes
    • Desired behavior - In the scenario above we want a new CI to be created when a server is moved from physical to virtual so we do not want a match to be on Hostname/IP
  3. Scenario 2 - AIX/Windows/Linux Virtual servers might move around to different hosts or be cloned during backup/upgrades.
    • Desired Behavior - We want discovery to trigger off hostname/IP if a server is virtual so it updates the UUID(SerialNumber) in these situations and keeps a single record migrating between physical hosts
    • Note - We are talking to operations teams to see if there is a way to maintain UUID during Windows/Linux moves but would like to have a solution for discovery as well

As of today since maintaining asset data is a higher priority we have just been matching by Serial Number.  This preservers the asset records and we manually update and delete the Virtual CI duplicates.

Looking for recommendations on either our process or potentially a tool workaround to solve these scenarios.

 

Nate

 

Labels:
0 Helpfuls
  • 2,073 Views
5 REPLIES 5

doug_schulze
ServiceNow Employee
ServiceNow Employee
In response to Santhosh17

‎02-28-2022 10:19 AM

If it doesn't identify any other part of the record with the existing rules, thinking maybe mac address/IP it will overwrite, if it doesn't match well, it will create a new record. Now if you do match on MAC/IP It will, but if  have data precedence rules set up for those attributes it will not overwrite those manipulated values.

0 Helpfuls