Azure-docs: Warning about "total of 4,096 IPs per virtual network" outdated?

Created on 13 Feb 2019  Â·  8Comments  Â·  Source: MicrosoftDocs/azure-docs

According to https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits?toc=%2fazure%2fvirtual-network%2ftoc.json#networking-limits, the 4096 IPs limit applied only to the old, classic deployment model, while in the Resource Manager deployment model the limit is documented as 65536.

Please confirm my understanding is correct and the warning at the top of this page is outdated.


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

cxp doc-bug in-progress service-fabrisvc triaged

All 8 comments

Thanks for the feedback! We are currently investigating and will update you shortly.

@jberezanski-mdg - there are several notes at the top of the page. Which one are you referring to, specifically.

@TylerMSFT this one

image

Looks like we need to update it since no one will deploy a SF cluster with Classic resources.

image

I can update the note if needed.

@jberezanski-mdg we are working offline to confirm on this. Will update as soon as I have more info.

@dario-ms could you help on this one please?

@jberezanski-mdg Just an FYI, the limit is in fact 65536 and we will be updating the doc with that new number. Also, as this is the limit, that being said we have not actually tested it with the max number of IPs. Even though that is the hard limit you would likely run into other limitations for example with the load balancer and the number of health probes it can have.

All in all, we generally test this scenario with each node having about 50 IPs each and that has been stable. I will work on updating the doc today.

@jberezanski-mdg I have submitted the PR to update the note :)

[!WARNING]
Azure allows a total of 65,356 IPs per virtual network. The sum of the number of nodes and the number of container service instances (that are using Open mode) can't exceed 65,356 IPs within a virtual network. For high-density scenarios, we recommend nat networking mode. In addition, other dependencies such as the load balancer will have other limitations to consider. Currently up to 50 IPs per node have been tested and proven stable.

I will close this out and one the PR merges the changes will go live a few hours later.

Thank you! I don't expect to ever reach this limit with Service Fabric, I was just wondering, while planning the vnets, subnets and addressing of a broader system, whether this is a restriction I needed to take into account.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Ponant picture Ponant  Â·  3Comments

ianpowell2017 picture ianpowell2017  Â·  3Comments

jharbieh picture jharbieh  Â·  3Comments

AronT-TLV picture AronT-TLV  Â·  3Comments

Favna picture Favna  Â·  3Comments