Error creating ip range for Azure NetApp Files SMB Volume

Jamiell 1 Reputation point
2021-11-09T15:02:13.167+00:00

I am trying to create an Azure NetApp Files SMB volume, but the provisioning fails with the below error:

{
"status": "Failed",
"error": {
"code": "InternalServerError",
"message": "Error creating ip range - Specified IP range clashes with an existing IP range",
"details": [
{
"code": "ErrorFromNFSaaSErrorState",
"message": "Error creating ip range - Specified IP range clashes with an existing IP range"
}
]
}
}

I made sure that the subnet and its address range does not conflict with the other subnets within the VNet. Therefore, I am not entirely sure why I keep getting the above error. If anyone has any suggestions, please let me know. Thank you.

Azure NetApp Files
Azure NetApp Files
An Azure service that provides enterprise-grade file shares powered by NetApp.
83 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. deherman-MSFT 33,626 Reputation points Microsoft Employee
    2021-11-09T22:48:15.167+00:00

    @Jamiell
    Is it possible that you have already delegated a subnet in your VNet for ANF?

    See the following information from the documentation:
    Create an SMB volume for Azure NetApp Files

    The subnet you specify must be delegated to Azure NetApp Files.
    If you haven't delegated a subnet, you can click Create new on the Create a Volume page. Then in the Create Subnet page, specify the subnet information, and select Microsoft.NetApp/volumes to delegate the subnet for Azure NetApp Files. In each VNet, only one subnet can be delegated to Azure NetApp Files.

    Hope this helps! If you are still facing issues please let me know and we can work with you directly to resolve your error.

    -------------------------------

    Please don’t forget to "Accept the answer" and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.


  2. Tong Zhou 1 Reputation point Microsoft Employee
    2021-11-10T09:13:33.267+00:00

    This could be caused from the backend, please open a support ticket to us


  3. Jamiell 1 Reputation point
    2021-11-15T17:00:28.76+00:00

    It appears that the issue might have been on my end, due to one of our vendors. I was able to deploy the volume this morning. Thank you both for your help. Please mark as resolved.