Notifications

24 views

Overview

The CI record of a virtual machine does not have "Is Virtual" flag set.

Troubleshooting

1- First, check if the VM should have the flag set. Out of the box, we only set "Is Virtual" flag for the following types:

  • Amazon AWS VM: This is set through the AWS Cloud Management discovery and the population of the relationships
  • Azure VM: This is set through Azure Cloud Management discovery and the population of the relationships
  • SolarisZone: Through 'Virtual Computer Check' Business Rule
  • HyperV: Through 'Virtual Computer Check' Business Rule
  • VMware: Through 'Virtual Computer Check' Business Rule

Business rule (BR):
https://<instance-name>.service-now.com/nav_to.do?uri=sys_script.do?sys_id=dd6ea51f0a0a0b7800561c3567d869bf

Therefore, if the VM is not virtualized by one of the above 5 virtualizations then it is not supported.

 

2- Now, if the VM is one of the types checked by the BR:

  • Make sure that the conditions for running the BR are met. It is triggered if:
current.serial_number.changes() || current.serial_number.hasValue() || current.correlation_id.changes() || current.correlation_id.hasValue()
  • If the above conditions are met, then check the conditions for setting each VM type to virtual as follows:
    • For SolarisZone: The CI needs to have a serial_number that starts with "zone-"
    • For VMware: The CI needs to have a serial_number that starts with "vmware-"
    • For HyperV: The serial number/s of the VM must match the serial number/s of the discovered HyperV instance/s

Article Information

Last Updated:2019-06-06 06:42:16
Published:2019-06-06