VM Instances discovered via cloud discovery are not populated with Private IP Address.

[svichare]

I am in process of discovering AWS Cloud. Done the following.

1. Created Service Account (with credentials).

2. Created "Cloud Resource" schedule via Service account.

3. It also created a Discovery Schedule to run after Cloud Resources discovery, 

4. My  Discovery schedule fails as my VM Instances are not populated with Private IP Address.

What am I missing here?

[Ashutosh Munot1]

HI,

VM will be discovered as part of cloud discovery. But to discover more details of this VM like Software on that VM extra information of that VM we need to discover then using IP and what we call it as OS discovery.

You need credentials for that with proper rights on those VMs.

Thanks,
Ashutosh

[BhupeshG]

@Ashutosh Munot1 can you please confirm this is not the case now.

There is child  discover vm schedule which is created which does the OS discovery?

If yes, the in my case the additional vm schedule is always cancelled as it is unable to pick up address.

I am Vancouver 

[chuckm]

As Ashutosh Munot mentioned, the Virtual Machine Instance [cmdb_ci_vm_instance] is discovered as part of Cloud Discovery.  More details are discovered using Horizontal Discovery and stored in a separate class (Windows [cmdb_ci_win_server], Linux [cmdb_ci_linux_server], etc.).

Additionally, the AWS Public IP address is assigned to the Virtual Machine Instance during Cloud Discovery.  The AWS Private IP address is assigned to the Operating System class during Horizontal Discovery.

For example, in AWS I created an Instance with Windows 2016 Datacenter installed.  The AWS Instance ID is i-079215be6775e1ecc with the Public IP 13.58.152.10 and Private IP 172.31.47.131 as shown.

The Dependency View of this example is as follows:

Community articles that provide more details on Cloud Discovery and Horizontal Discovery:

AWS Host Based Discovery

AWS Discovery

[guillaumeh]

Hi, did you manage to solve this issue ?

In fact, I have the same behaviour where the IP discovery launched after cloud discovery is using the public IP and not the private IP of the virtual instances.