Migrate for Compute Engine UI address clarification

[moneshwari D]

Hello Everyone , 

Migration Manager UI address of velostrata is always internal IP due to that it is not accessible through browser as the source is external . Even it is not accessible ( curl  ) from internal VM which is in same network as velostrata .

But external IP of that velostrata is accessible through https protocol .

Kindly clarify why it is giving internal IP as UI address when we launch ? 

Also correct me if I have misunderstood the concept . 

Thanks ,

Deena 

[kameliay]

Hi,

To help assist you better will need you to elaborate more what you mean by:

“why it is giving internal IP as UI address when we launch ?“

Please send me the screenshot of the Internal IP that you are getting.

Based on this documentation and in the subnetwork section, the Internal IPs are for VM to VM communication.

[moneshwari D]

Hello Kameliay  , 

 Thanks for the reply , I got it . 

[ash k]

Hi Kameliay ,

please let me know how to resloved this ,i am also facing issue 

[pralove]

Hello,

Using their internal IPs, instances in different subnetworks can communicate with each other as long as they are in the same network[1].

Please follow the following documentations to learn more about:

 

Subnets and IP ranges[2]

Working with subnets[3]

Auto mode IP ranges[4]

I hope this helps. 

Thanks.

 

[1] https://cloud.google.com/migrate/compute-engine/docs/4.8/how-to/configure-manager/configuring-on-gcp#deploying

[2] https://cloud.google.com/vpc/docs/vpc#manually_created_subnet_ip_ranges

[3] https://cloud.google.com/vpc/docs/using-vpc#subnet-rules

[4] https://cloud.google.com/vpc/docs/vpc#ip-ranges