Load Balancer Prerequisites for PMC

PMC supports two load balancer configurations:

  • External load balancer
  • External and internal load balancer

You will be prompted to choose if you want to configure an internal load balancer in addition to the default external load balancer in the deployment script. If you want to configure an internal load balancer, and you'd like to use your existing IP ranges from a peered network, modify this parameter file before you start the deployment.

If you configure an internal load balancer, all traffic for PMC will be routed through it. The external load balancer is only used for Microsoft requirements, such as Service Fabric and SQL Server updates.

The addressPrefix and the subnet0Prefix are CIDR notation, which is used to specify the IP range for a VNet. The subnet has to be within the range of the address. If you do add the prefix parameters manually, 10.1.1.0/27 is used for both. If you add these values, you must update the load balancer address in the PMCMPAARMTemplate_InternalExternalLB.json template, otherwise you will receive an error stating that the default load balancer address is not within the subnet range you specified.

The clientIP is the public IP address of the machine you are deploying from. You enter this as part of the deployment. The address is used to set the firewall rules, allowing access to SQL Server databases.

  1. Locate and open the PMCMPAARMTemplateParameterValues.json file.

Other values in this template must not be edited.

  1. Go to the bottom of the file and locate the following lines:
"clientIP":  {
   "value":  "193.240.178.130"
}
  1. Duplicate them twice, so that you have three instances of ClientIP.
  2. Change the two new instances of ClientIP to addressPrefix and subnet0Prefix:
"addressPrefix":  {
   "value":  "193.240.178.130"

}

"subnet0Prefix":  {
   "value":  "193.240.178.130"
}
  1. Change the IP address to match the range for your network and save the file.