Why does Discovery not set virtual flag correctly?

[jimmillet]

We are seeing issues with the setting of the "Is Virtual" flag for discovered servers.  We have a lot of Windows/Linux servers that Discovery reports the VMware SerialNumber string, but yet the "Is Virtual" flag is FALSE! We also have IBM AIX LPARs that are also reporting Virtual=FALSE, and by definition an LPAR is virtual (LPAR = logical partition). What puzzled us, was that we looked at the discovery code and could not see any mention of the virtual flag. So unless we were looking wrong, it does not look like this is a field that servicenow discovery detects/sets, which is very odd for a discovery tool. I was going to open a HI ticket, but checking here first.

[doug_schulze]

To set that flag we have to discover both sides of the virtualization meaning we must discover the host and the virtual environment such as vCenter.  We then use the serial number (UUID) to match the two together and mark the 'is virtual' flag.

For IBM we do not do that OOB so you would want to set up discovery to discover and outline your virtual environment.  I did an update set that can help with just that

https://community.servicenow.com/community?id=community_question&sys_id=3553c325dbd8dbc01dcaf3231f9619b3&view_source=searchResult

[chandra_ym]

Thanks Doug.

How does this flag work for AWS servers? 

Isn't this flag set to Yes (selected) when the AWS server is discovered?

[doug_schulze]

Yes, I believe it works the same, once you discover the AWS cloud environment then a 'normal' discovery of the hosts they should match up and set the virtual flag for the server classes.