Share via

Azure Infrastructure - No automated NAT rule creation for deploying VMSS behind existing Load Balancer

Anonymous_17 21 Reputation points
2021-02-26T15:11:21.45+00:00

Hi, Everyone,

So, we have an existing VM behind the load-balancer & now we deployed a customized scale set & chose existing LB (& existing pool) while deployment of VMSS - Deployment succeeded with backend pool having vmss instances & site functioning. However, no inbound NAT rules got created which happens automatically when creating new load balancer while VMSS deploment.

Any root cause for no automated inbound rules creation when using existing Load Balancer? How to resolve or any work around for the same.

Regards,
Anonymous

Azure Virtual Machine Scale Sets
Azure Virtual Machine Scale Sets
Azure compute resources that are used to create and manage groups of heterogeneous load-balanced virtual machines.
364 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. vipullag-MSFT 26,016 Reputation points
    2021-03-02T15:24:28.377+00:00

    @Anonymous_17

    Apologies in delayed response.

    As you have an existing LB, you need to create an inbound NAT pool configuration for a load balancer use Add-AzureRmLoadBalancerInboundNatPoolConfig cmdlet and then configure the LB with the nat pool and update the LB. After this you can set the LB.

    Please check the details in this stackoverflow thread.

    Also, you can look at this thread for details on Adding Inbound nat pool to existing scale set and this.

    Hope this helps.

    Please 'Accept as answer' if the provided information is helpful, so that it can help others in the community looking for help on similar topics.

    0 comments