Discovery VMs by IP address as a part of Cloud discovery using Discovery Manager - Support and Troubleshooting

Discovery VMs by IP address as a part of Cloud discovery using Discovery Manager Summary This article explains the implementation logic on how the Discover VMS by IP address option in Cloud discovery triggers IP discovery of the Virtual machines.

Release New York or later

Instructions 1. Prerequisites for Discovery VMs by IP Addresses :

a) MID Server should be in the network where all these VM's are in to be able to discover them.

b) No need to define any IP ranges for this schedule, as this will be determined based on the VM information found from running the previous main Cloud Discovery schedule.

c) The discovery for VM discovery with IP Addresses should always run after the Cloud discovery schedule

2. The IP List for triggering against in these VM Schedule patterns starts from the "DiscoverySchedule" Script Include and this snippet below in the "initialize" function.

======================================================================================== //For VM Schedules which runs after Cloud Schedules, we will not be having the IP ranges populated in the schedule table. //So, Bypassing the range check for VM schedule if it has a parent cloud schedule. var dr;

if (gr.discover.equals('CIs') && new CloudResourceDiscoveryUtil().hasParentCloudSchedule(this.sysID)) { var ipList = new CloudDiscoveryScheduleConfig().getListofIPAddressesForVMSchedule(this.sysID); dr = SNC.DiscoveryRanges.getByScheduleID(this.sysID, ipList); } ========================================================================================

3. This calls another Script Include "CloudDiscoveryScheduleConfig" and as you look in this "getListofIPAddressesForVMSchedule" function, how this calls other functions (ex. fetchIPByLDC(), populateIPAddressList()) where it basically queries against the Datacenters from the parent schedule, and then we query against the VM's and NIC's (cmdb_ci_nic) that belong to those data centers to get IP's to use for the VM Schedule.

Now, if in this parent schedule we are not populating any VM's and/or NIC records here, then the discovery will not populate ranges for VM discovery