问题描述
尝试在Azure规模集上手动将实例数增加到10以上时，我收到以下错误消息.
I'm receiving the following error when trying to manually increase the number of instances above 10 on an Azure Scale set.
实例的默认数量是3，并且最多10个实例的数量都可以正常工作.订阅具有大量可用的内核.
The default number of instances is 3 and any number up to 10 works as expected. The subscription has plenty of available cores.
查看Azure门户中引用的负载平衡器，我看不到任何明显链接到此错误消息的设置.LB的设置"SKU"的值为"Basic"，我想可能是个问题?(尽管仔细阅读后会发现上限为100)
Looking at the referenced load balancer in Azure portal, I cannot see any settings that are obviously linked to this error message. The LB has a setting 'SKU' that has a value of 'Basic' which i guess may be an issue? (although reading up on this would indicate the limit there is 100)
对于代码"InboundNatPoolFrontendPortRangeSmallerThanRequestedPorts"，没有Google结果，并且搜索错误消息的任何部分都没有给出有意义的结果.
There are no google results for the code 'InboundNatPoolFrontendPortRangeSmallerThanRequestedPorts' and searching for parts of the error message didn't give any meaningful results.
任何指针表示赞赏
推荐答案
请记住，如果您有过多的配置，您将获得的虚拟机数量将超出您的要求(文档此处).因此，您需要有足够的NAT规则来容纳额外的VM.NAT规则的数量永远不应超过VM的2倍(因此，如果您的VM max为10，则池中的NAT规则绝对不应超过20).
Keep in mind that if you have overprovisioning on, you will temporarily get more VMs than you asked for (documentation here). So you'll need to have enough NAT rules to accomidate the extra VMs. You should never need more than 2 times as many NAT rules as VMs (so if your VM max is 10, you should never need more than 20 NAT rules in the pool).
这篇关于无法更新自动缩放配置.(天蓝色刻度)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！