Networking Requirements for NC2 on Azure Deployment

If your using an Azure load balancer - The VMs on NC2 in Azure, you will have to use a NATed connection out to Azure. You can give the VMS a floating IPs from PC, those floating IPs can be used with the load balancer. If it’s internally to NC2, Flow virtual networking has a load balancer you could use.

Thankyou ​@dlink7 

I have one more question-
Q. There are some forbidden IP addresses which we shouldn’t be using to deploy cluster VNets or PC VNets- 10.100.0.0/16, 10.200.0.0/24, 10.200.0.0/22, 192.168.5.0/24
Lets assume Iam migrating my workloads from vmware environment to NC2 on azure and my on-premises workloads have IP addess from this forbidden CIDR range (mentioned above)

Is it possible to migrate the workloads to my overlay subnets created in FVN VPC’s ? or any other approach we should consider ?

You would be able to use those ranges as user VPCs if they were NAT’d. Probably not going to work for most customers though since most what no-NAT. 

I think those workloads will most likely have to be re-ip’d

okay Thanks ​@dlink7 

Hi ​@dlink7 

As we know below are the forbidden IPs and we shouldn’t be using it to create my first cluster Vnet and PC Vnet
10.100.0.0/16, 10.200.0.0/24, 10.200.0.0/22, 192.168.5.0/24

How about I am creating 2nd Cluster? Will these above IPs again be used internally for Prism Central services and internal Cluster management? How it’s managed or above IPs again be considered as forbidden for my 2nd or 3rd cluster?
Can you please explain, if possible, it would really help me to understand the concept.