VM Instance Identifier Question

Todd_Goodhew · ‎07-10-2019

When running Cloud Discovery on AWS, I've noticed something I'm not understanding when it comes to VM Instances.

This problem occurs out-of-the-box. Yes, I know this OOTB as I can reproduce in my Personal Developer Instance that is clean.

The Identifier for VM Instance shows ONLY Object ID.

If we have a record in the VM Instance table already and that record only has a value in the Object ID field or the VM Instance ID field, then Cloud Discovery creates a new record.

If we have a record in the VM Instance table and that record has BOTH Object ID and VM Instance ID field completed, then Cloud Discovery updates the record.

This is where I am confused. The identifier for the table only requires Object ID, but when Cloud Discovery is running it is matching both Object ID and VM Instance ID.

Why is this occurring?

Jayant Kaushal · ‎07-10-2019

Todd,

the reason is,

Due to legacy reasons, the Provisioning and discovery go through different paths,

The VMWare discovery goes through Probe and Sensor which which are not very strict about Identification rules, thats why you have to populate VM Inst Id too so that discovery can identify right VM,

In case of Provisioning and Day2 operations, all persistance call go through Response Processor which strictly adheres IRE, IRE it not only considers the uniqueness of object_id in a VM but also considers the Hosting relationships with LDC.

Simply saying , Provisioning calls will identify a VM based on the VM(object_id) + LDC(object_id) + SA(object_id) identification.

View solution in original post

Todd_Goodhew · ‎07-12-2019

The LDC/locations were not created manually. We discovered the LDCs per the documentation. Fun part is I can reproduce this in my Personal Developer Instance against my personal AWS account.

I'm working with HI on a different issue with Cloud Discovery (we use AWS GovCloud and CMP is erroring on LDS discovery). They informed us yesterday that at least one of our patterns is out of date and they are having trouble getting it to upgrade. So I'm wondering if this is all related.

Very odd that I can produce this issue in a clean PDI environment.

I'm happy to share logs...let me know what you would want to see.

Ganesh Bhat · ‎07-14-2019

Hi Todd,

We would like to inspect the instance as there are modification done to it.

Please log a case for the same, we will post the solution once we have full end to end flow working for you.

Todd_Goodhew · ‎07-17-2019

I have a ticket open with HI on this issue. As soon as I get resolution, I'll post the answer.

Todd_Goodhew · ‎08-01-2019

Closing out this last question. The problem went away on its own while HI was investigating. Don't know the root cause or the fix. I know we did have some trouble with getting some patterns to upgrade and HI had to force them. I still can reproduce the issue in my Personal Developer Instance and since I cannot apply the latest patterns from the NOW Store, I'm guessing this is related. All I know is it is working in our corporate instance, which is all I needed.

Thanks to Ganesh and Jayant for all your help.