Highlighted
Honored Contributor.
Honored Contributor.
580 views

How to identify if a server / host is physical?

Hi,

Is there another way to identify if a server is physical in addition to the option or the field nodeisvirtual = false?

Thanks in advance,

0 Likes
8 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: How to identify if a server / host is physical?

Hello Marsella,

AFAIK, the VMware machines have a particular serial number or BIOS version. This can be used as an identifier for virtual VMs. It may be valid for other virtualization technologies.

 

Kind regards,
Bogdan Mureșan

EMEA Technical Success
0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: How to identify if a server / host is physical?

Discovery is famous with not being able to detect always serial number or bios version. Even you, marsella, wrote recently that the serial number is not coming properly in MAC computers.

I consider the best method to detect if a machine is virtual or physical  is through the MAC address. All the vendors put their vendor specific prefix on the MAC address of the network interface. VMWare, Azure, etc use their own prefixes as well.  Just take a sample mac address and check it through a vendor database as https://macvendors.com/. 

 

Regards,

Petko

Likes are appreciated!
0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: How to identify if a server / host is physical?

The modeling of virtual machines based on the MAC prefix would be usable. We already have a job which does something similar

https://docs.microfocus.com/itom/Universal_Discovery_Content_Pack:28/Thin_clients_MAC_based_detection_jb

It will use the first half of the MAC address to model the Wyse thin clients.

Kind regards,
Bogdan Mureșan

EMEA Technical Success
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: How to identify if a server / host is physical?

HI Bogdan,

in fact the R&D has always used the mac address vendor identification to define the interface's isvirtual attribute for the Host discoveries. If they didn't, they would have a ton of problems to reconciliate nodes because of duplication in interface addresses:

virtualmac.PNG

 

Likes are appreciated!
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: How to identify if a server / host is physical?

Hello Petko,

I was proposing a new discovery adapter which can use the data in the Probe DB to populate that attribute. Most of the time host_isvirtual comes empty and in the classModel it doesn't have a default value. The probe data can be used to normalize this attribute based on vendor specific rules.

Actually, such rules could be used with the current normalization capabilities like we do for the Interface CIT with the attribute is_system_internal for the Juniper switches.

Maintaining such a normalization list would be interesting.

Kind regards,
Bogdan Mureșan

EMEA Technical Success
0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Re: How to identify if a server / host is physical?

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: How to identify if a server / host is physical?

Hi Bogdan,

The attribute isvirtual is not only used for nodes, but also it is defined on interfaces

Normalization Rules can be nice way to identify if not what is physical, at least what is virtual. But I suppose there is some specific reason why they are used only for identifying SNMP NetDevices and Scanner jobs and not the other adapter jobs. I just have never found what. 

Cheers

Likes are appreciated!
0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: How to identify if a server / host is physical?

The attribute isvirtual was mentioned as it could help the requestor and it's used in 2 different sceanrios (node and interface) with normalization rules. It's a good starting point.

Normalization is used on every DataIn flow that comes through the probe and only on the probe. It's efficient as it distributes the load on each probe and there's no server side load. The CIs come to the server in the desired form and no enrichments are needed. It applies even on the population flow.

Normalization is not restricted to certain discovery jobs, the correct explanation is that only certain discovery jobs bring data that can be used in the normalization rules. For example, Host Connection by Shell won't bring an OID to identify the node or intreface as virtual. Host Connection by SNMP can bring that OID hence a normalization rule can alter that OSHV on probe due to the HCbySNMP discovery job.

Kind regards,
Bogdan Mureșan

EMEA Technical Success
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.