針對常見的 Azure Load Balancer 部署錯誤進行疑難排解Troubleshoot common Azure deployment errors with Azure Load Balancer

本文說明一些常見的 Azure Load Balancer 部署錯誤,並提供解決錯誤的資訊。This article describes some common Azure Load Balancer deployment errors and provides information to resolve the errors. 如果您要尋找錯誤碼相關資訊,但本文並未提供該資訊,請讓我們知道。If you're looking for information about an error code and that information isn't provided in this article, let us know. 您可在此頁面底部留下意見反應。At the bottom of this page, you can leave feedback. 意見反應會與 GitHub 問題一併追蹤。The feedback is tracked with GitHub Issues.

錯誤碼Error codes

錯誤碼Error code 詳細資料和緩和措施Details and mitigation
DifferentSkuLoadBalancersAndPublicIPAddressNotAllowedDifferentSkuLoadBalancersAndPublicIPAddressNotAllowed 公用 IP SKU 與 Load Balancer SKU 必須相符。Both Public IP SKU and Load Balancer SKU must match. 確保 Load Balancer 與公用 IP SKU 相符。Ensure Azure Load Balancer and Public IP SKUs match. 建議對生產環境工作負載使用標準 SKU。Standard SKU is recommended for production workloads. 深入了解 SKU 的差異Learn more about the differences in SKUs
DifferentSkuLoadBalancerAndPublicIPAddressNotAllowedInVMSSDifferentSkuLoadBalancerAndPublicIPAddressNotAllowedInVMSS 若未指定 SKU 或未使用標準公用 IP 部署 SKU 時,虛擬機器擴展集會預設為 Basic Load Balancer。Virtual machine scale sets default to Basic Load Balancers when SKU is unspecified or deployed without Standard Public IPs. 在個別執行個體上使用標準公用 IP 重新部署虛擬機器擴展集,確保已選取 Standard Load Balancer,或是從 Azure 入口網站部署虛擬機器擴展集時直接選取 Standard LB。Re-deploy virtual machine scale set with Standard Public IPs on the individual instances to ensure Standard Load Balancer is selected or simply select a Standard LB when deploying virtual machine scale set from the Azure portal.
MaxAvailabilitySetsInLoadBalancerReachedMaxAvailabilitySetsInLoadBalancerReached Load Balancer 的後端集區最多可包含 150 個可用性設定組。The backend pool of a Load Balancer can contain a maximum of 150 availability sets. 如果您沒有針對後端集區中的 VM 明確定義的可用性設定組,則每個單一 VM 都會進入其本身的可用性設定組。If you don't have availability sets explicitly defined for your VMs in the backend pool, each single VM goes into its own Availability Set. 因此,部署 150 部獨立 VM 表示其會有 150 個可用性設定組,因而達到限制。So deploying 150 standalone VMs would imply that it would have 150 Availability sets, thus hitting the limit. 您可以部署可用性設定組,並在其中新增額外的 VM 作為因應措施。You can deploy an availability set and add additional VMs to it as a workaround.
NetworkInterfaceAndLoadBalancerAreInDifferentAvailabilitySetsNetworkInterfaceAndLoadBalancerAreInDifferentAvailabilitySets 針對基本 Sku 負載平衡器,網路介面和負載平衡器必須位於相同的可用性設定組中。For Basic Sku load balancer, network interface and load balancer have to be in the same availability set.
RulesOfSameLoadBalancerTypeUseSameBackendPortProtocolAndIPConfigRulesOfSameLoadBalancerTypeUseSameBackendPortProtocolAndIPConfig 在指定的負載平衡器類型 (內部、公用) 上,不能有一個以上的規則具有相同的後端連接埠,以及相同的虛擬機器擴展集所參考的通訊協定。You cannot have more than one rule on a given load balancer type (internal, public) with same backend port and protocol referenced by same virtual machine scale set. 更新您的規則,以變更此重複規則的建立。Update your rule to change this duplicate rule creation.
RulesOfSameLoadBalancerTypeUseSameBackendPortProtocolAndVmssIPConfigRulesOfSameLoadBalancerTypeUseSameBackendPortProtocolAndVmssIPConfig 在指定的負載平衡器類型 (內部、公用) 上,不能有一個以上的規則具有相同虛擬機器擴展集所參考的相同後端連接埠和通訊協定。You cannot have more than one rule on a given load balancer type (internal, public) with same backend port and protocol referenced by same virtual machine scale set. 更新您的規則參數,以變更此重複規則的建立。Update your rule parameters to change this duplicate rule creation.
AnotherInternalLoadBalancerExistsAnotherInternalLoadBalancerExists 在 Load Balancer 的後端中,您只能有一個內部類型的 Load Balancer 參考相同的 VM/網路介面集。You can have only one Load Balancer of type internal reference the same set of VMs/network interfaces in the backend of the Load Balancer. 更新您的部署,確保您只會建立一個相同類型的 Load Balancer。Update your deployment to ensure you are creating only one Load Balancer of the same type.
CannotUseInactiveHealthProbeCannotUseInactiveHealthProbe 您擁有的探查都是由針對虛擬機器擴展集健康情況所設定的規則使用。You cannot have a probe that's not used by any rule configured for virtual machine scale set health. 確保正積極使用所設定的探查。Ensure that the probe that is set up is being actively used.
VMScaleSetCannotUseMultipleLoadBalancersOfSameTypeVMScaleSetCannotUseMultipleLoadBalancersOfSameType 您不能有多個相同類型 (內部、公用) 的 Load Balancer。You cannot have multiple Load Balancers of the same type (internal, public). 您最多可有一個內部和一個公用 Load Balancer。You can have a maximum of one internal and one public Load Balancer.
VMScaleSetCannotReferenceLoadbalancerWhenLargeScaleOrCrossAZVMScaleSetCannotReferenceLoadbalancerWhenLargeScaleOrCrossAZ 多重放置的群組虛擬機器擴展集或跨可用性區域的虛擬機器擴展集不支援 Basic Load Balancer。Basic Load Balancer is not supported for multiple-placement group virtual machine scale sets or cross-availability zone virtual machine scale set. 請改為使用 Standard Load Balancer。Use Standard Load Balancer instead.
MarketplacePurchaseEligibilityFailedMarketplacePurchaseEligibilityFailed 切換至正確的系統管理帳戶才能購買,因為訂用帳戶是 EA 訂用帳戶。Switch to the correct Administrative account to enable purchases due to subscription being an EA Subscription. 您可以在這裡取得詳細資訊。You can read more here.
ResourceDeploymentFailureResourceDeploymentFailure 如果您的負載平衡器處於失敗狀態,請遵循下列步驟,使其從失敗狀態恢復:If your load balancer is in a failed state, follow these steps to bring it back from the failed state:
  1. 移至 https://resources.azure.com ,並以您的 Azure 入口網站認證登入。Go to https://resources.azure.com, and sign in with your Azure portal credentials.
  2. 選取 [讀取/寫入]。Select Read/Write.
  3. 在左側,展開 [訂用帳戶],然後展開含有要更新之 Load Balancer 的訂用帳戶。On the left, expand Subscriptions, and then expand the Subscription with the Load Balancer to update.
  4. 展開 [ResourceGroups],然後展開含有所要更新 Load Balancer 的資源群組。Expand ResourceGroups, and then expand the resource group with the Load Balancer to update.
  5. 選取 [Microsoft.Network] > [LoadBalancers],然後選取要更新的 Load Balancer (LoadBalancer_1)。Select Microsoft.Network > LoadBalancers, and then select the Load Balancer to update, LoadBalancer_1.
  6. 在 [LoadBalancer_1] 的顯示頁面上,選取 [取得] > [編輯]。On the display page for LoadBalancer_1, select GET > Edit.
  7. 將 [ProvisioningState] 值從 [失敗] 更新為 [成功]。Update the ProvisioningState value from Failed to Succeeded.
  8. 選取 [PUT] 。Select PUT.

後續步驟Next steps