Symptoms

The Vcenter discovery executes successfully and populates the VM information to "cmdb_ci_vm_instance", but fails to populate the "VM Instance ID", "Location" and "IP Address" fields.

Release

London P*  Madrid P *

Steps to Reproduce

• Log in to the instance 
• Navigator >> Service Accounts >> Choose the Vcenter Account and execute Discovery 
• Wait for the Successful completion of the Discovery
• Notice the Pattern "list_vminstances" is completed successfully.
• Navigator >> cmdb_ci_vm_instance_list.do 
• Verify the "Location" VM Instance ID" and "Location" are not populated for Vcenter VMs

Cause

• VM Instance ID: 
  
  
  • For vCenter Discovery we do not use the "VM Instance ID" and we don't populate. But instead, we use the "VM Instance UUID" to identify. Instead, this might be used for the Cloud related discovery AWS and/or Azure.
    • Schemas of Cloud Management tables
      
      
•  IP Address & Location 
  
  
  • We see that OOB till New York release we do not populate the IP Address and Location for the "VMware Virtual Machine Instances". Please see below:
    • Please look for the section "VMware Virtual Machine Instance [cmdb_ci_vmware_instance]"  Data collected for VMware vCenter Server

Resolution

• "IP Address"
  
  
  • Servicenow discovery is providing OOB functionality to populate the IP Address from Newyork release, for Madrid P* and London P* instances have a workaround as below.
    • Download and import the XML Fix for IP Address 
      
      
• "VM Instance ID" 
  
  
  • 1) Modify the Script include  "VMWarevCenterVMsProbe" add below line at 192 (Under function fixupVM(vm))

vm.vm_instance_uuid = config.vm_instance_uuid;

• • 2) Modify the Scriptinclude "VCenterVMsSensor" add below line at 163 (Under function fixupVM(vm))

vm.vm_inst_id = vm.vm_instace_uuid;

• "Location"
  
  
  • Servicenow discovery is providing OOB functionality to populate the IP Address from Newyork release, no Workaround yet.